Puppy Linux Discussion Forum

[nooby]

Here I am in 104 or rc1.

# VIDEO REPORT: Quirky, version 104
bash: VIDEO: command not found
#
# Chip description:
bash: Chip: command not found
# oem: NVIDIA
bash: oem:: command not found
# product: G98 Board - 5610001u Chip Rev

But ok I try to do full install as you told me just in case.

after installing it from PPM# report-video
VIDEO REPORT: Quirky, version 104

Chip description:
oem: NVIDIA
product: G98 Board - 5610001u Chip Rev

Driver used by Xorg:
nvidia

Video mode used by Xorg:
Resolution: Depth 16 Depth: "Display"
Yes that looks better indeed. I test spotify now

Edit after test

Nope it did not help. I go test qrky110 now

Edit Q110 one crashed too when loading spotify in wine. Reported about it in proper place I hope.

Back in Q.1.00 and that one survive and just works. Very pleased about Q1

[`f00]

Mainly simply a run-through of xorgwizard to get to a desktop..
1) using the choose branch (nice having a fair-sized list) and entering "ati" gave not much in the way of results (xorg reported x pixels and no h&v refresh rates, no card or display if I recall)
2) probe and edit worked as usual (mp is a lovely thing if you have a 'known-good' cribsheet), xorg got the main display id'd and I filled in and tweaked h&v refresh and such

..then went a bit crazy and did a fair amount of 'damage' playing monkey-with-a-mouse - surprising how many things still work, even as the triangles dominated the d'n'd desktop (squiggles looks good tiled with the citrus-cut jwm and gtk) and panels. Jwm cascades windows nicely, btw. Not too crazy, I removed driveicons so the madness was confined-to-RAM

____________
vidcard0 - RV280 (aka ATI Radeon 9200), AGP
vidcard1 - not used, but also RV280 (switched off in BIOS - aka Radeon 9200SE), PCI (old-style)

[alec78]

Hi all,
@BarryK
Barry,
I have a problem with qrky-110.
I did a fresh pfix=ram boot from the CD, had to select the vesa driver at the graphics stage, graphics came up after the usual blocky flash.
Copied the qrky-110.sfs file to an USB dongle and saved the qrkysave file to the same dongle selecting ext3 file system.
Powered off and then re-powered up. The Samsung failed to boot with the following text.

"Loading personal file /qrkysave 3fs(sdb1)
EXT-fs error (device loop1): ext3-lookup: deleted inode referenced: 24618
# this text was repeated twice then
Loading the 'qrky-110.sfs' main file
EXT3-fs error (device loop1): ext3_lookup: deleted inode reference: 24618
# this text was repeated three times then
Kernel panic not syncing:Attempted to kill init !"

I'm posting this from my Dell Latitude LS using lupu-500.
By the way touchpad tapping works on the Samsung when using lupu-500 and the vesa driver.
Cheers

[BarryK]

Please provide feedback for Quirky 1.1 on the "Quirky 1.1 feedback" forum thread:

http://murga-linux.com/puppy/viewtopic.php?t=55406

[Sylvander]

Re: qret-104.iso
Also has some of same effects within Lighthouse-4.43f

1.
(a) See this and...
(b) also this.

2.
(a) After applying 1a & 1b above...
Lets say I manually save during the session...
And then reboot...
And at shut-down choose not to save...
At reload of the Puppy [Quirky or Lighthouse]...
There is a warning given of an unclean exit at the previous shut-down.

(b) However...
If I choose to save_the_session during shut-down...
The next startup/reload of the Puppy gives no warning.

3. Background:
(a) Using an 8GB Flash Drive, with 6-off 1.3GB ext3 partitions.
So far there's a different Puppy on each of 5 of these.
e.g.
Lighthouse-4.43f
Teenpup Mini 2010 beta
Quirky-1.1 [qret-104.iso]
Lupu-501
Puppy-431-boxpup.iso

(b) Having various strange problems.
e.g.
(b1) GParted cannot see Flash Drive sdd in qret-104 [only sometimes, seeing it now], yet all other Puppies see it OK.
(b2) Some Puppies don't show drive/partition icons on desktop correctly/reliably.
1GB Flash Drive lone partition sdc1 shows mounted when it isn't, or doesn't show at all when connected.
Must be unplugged/replugged to show correctly.
(b3) Puppy loads to black screen with cursor.
(b4) Keyboard won't work until Puppy is rebooted.

[Karl Godt]

[Sylvander]

1. "Changing the POWER-SUPPLY from 300 W to 350 W seems to help"
(a) Motivated by the fact the PC was intermittently failing to complete POST...
And prior to your answer...
I'd changed the both the CMOS battery [no fix produced]...
And swapped in a new [400 watt?] PSU [produced a fix = POST completes reliably].

(b) Most of the strange effects are cured/gone, except:
Not all puppies show ALL partitions on the desktop.
e.g. First partition on 8GB Flash Drive [and/or the only partition on an external USB HDD, with its own power unit] doesn't show in some Puppies.

2. Now at Qrky-120 rather than qret-104.