Quirky 018 feedback

[BarryK]

anyone here play music with quirky ? i cant control the volume with retrovol,

retrovol work on 431 but not on quirky 1.8 or 431 build with last woof.

Right-click the retrovol icon to bring up the mixer, see if there is another level adjustment that will work.

[broomdodger]

Many moons ago, we (Dougal) established that:
acpi=force
was the standard workaround for misbehaving Puppy shutdowns. It happens with SiS 735 & 748 as well as a plethora of laptops. However, it is a just a workaround not a solution.

I missed this post, but now changed to acpi=force... and it shutdown!

ok, a workaround... any solution in sight?

What date does the BIOS have? You should see that during bootup, or run the BIOS setup. Puppy does have a utility that will display all sorts of info about the BIOS -- but I can't recall its name right now.

The kernel is configured not to use acpi for any BIOS dated prior to January 2001. Which might account for your problem.

1998
Is there any way to pause the display to read all.

[pri]

retrovol still not work mybe just for me

[bigpup]

PupRadio works fine for me running Quirky 018 off CD.

I did have to play with settings in gnome-mplayer to get it to work for PupRadio.

The main problem was the cache size was too high and it would take a long time for the cache to fill before gnome-mplayer would output sound.
I set cache to 32K and at start, instant sound.

[James C]

PupRadio works fine for me here on my full install of Quirky 018.Using onboard Intel 82801-AA audio, by the way.

Retrovol is working correctly as well.

[tiangeng]

Browser can not view any Chinese website, for example news.sina.com.cn

[Sage]

...can you guys who have the problem please run 'pupradio' from a terminal and post the messages?

See your blog.

The kernel is configured not to use acpi for any BIOS dated prior to January 2001.

I was told by one of the developers of a major distro (so long ago I forget who/which) that Linux ignores all BIOS instructions after boot up. Notwithstanding, as an arch-fiddler, I am in the habit of regular BIOS updating, even on dinosaur boards if the files are still available.

[BarryK]

Touchpad problems. Slow movements is easily fixed by tweaking xorg.conf but to enable touchpad tabbing I havent found any solution. Clicking enabled from mouse config does not have any effect. I have tried adding rows to xorg.conf suggested by google searching but no effect. Does anybody have working solution ?

Touchpad tabbing. I got it working. I have included my working xorg.conf attachment.

I made changes to Section "ServerLayout":

Code: Select all

InputDevice "Synaptics Mouse" "SendCoreEvents"

And to Section "InputDevice", Identifier "Synaptics Mouse" I added two rows:

Code: Select all

Option "SendCoreEvents" "true"
Option "TapButton1" "1"

If you need to use modified xorg.conf, backup it, because you lose changes if you run xorgwizard.

What is "touchpad tabbing"? You don't mean "touchpad tapping"?

Those fixes shown above, do you think it would do any harm if I made Xorg Wizard automatically insert them for every case? Even for people who don't have a synaptics touchpad?

[BarryK]

Touchpad tabbing. I got it working. I have included my working xorg.conf attachment.

I made changes to Section "ServerLayout":

Code: Select all

InputDevice "Synaptics Mouse" "SendCoreEvents"

And to Section "InputDevice", Identifier "Synaptics Mouse" I added two rows:

Code: Select all

Option "SendCoreEvents" "true"
Option "TapButton1" "1"

If you need to use modified xorg.conf, backup it, because you lose changes if you run xorgwizard.

Did you have the same problem with no scolling on the touchpad aswell?

I didn't need to add "SendCoreEvents" just adding below to Section "InputDevice" works to get both double tap and scroll working for me.

Code: Select all

    Option "TapButton1" "1"
    Option "SpecialScrollAreaRight" "true"
    Option "VertEdgeScroll" "true"
    Option "VertTwoFingerScroll" "true" 

Well, it would be pretty easy to get the Xorg Wizard to automatically insert that every time. Any reason why it shouldn't be done for every case? ...the less question boxes that popup in Xorg Wizard, the better.

[BarryK]

Went to /tmp/versioncleanup, as suggested at boot time, to see if anything could be taken back -- well, either I'm getting duller than I thought or there's really no such directory, even Pfind couldn't spot it. No big loss for me (had just been playing around a bit with Quirky), but possibly worth reporting: guess this directory should exist anyway, even if empty.

Yeah, there is something wrong there. tmp/versioncleanup does appear somewhere I think, try looking in /initrd

I need to examine the 'init' script, try and figure out where that is going wrong.

[pri]

Browser can not view any Chinese website, for example news.sina.com.cn

you need to insert chinese font or complex font.

try this :
http://www.silverdollarsolutions.com/Pu ... -Asian.pet

[BarryK]

Greetings folks!

I had a problem with the puppyinstaller script failing on my "unique" partitioned hard drives. Many debugging statements later, I was able to isolate the issue: identifying partition filesystem types and determining if an older version of puppy was installed on it.

I provided more detailed information to Barry along with the offer to provide my solution and debug output. He requested I post my script changes here as he is montoring this thread more closely...

1. On line 41 starts the function fsfunc() which takes the extracted filesystem type and changes it to a different character case if recognized (maybe for presentation but not really sure why). I changed this function to return the character case change if recognized (current behavior) and return null/empty string if unrecognized (new behavior).

OLD CODE:
fsfunc() #f.s. type param passed in
{
FSTYPE="$1"
[ "$FSTYPE" = "Ext2" ] && FSTYPE="ext2"
[ "$FSTYPE" = "ReiserFS" ] && FSTYPE="reiserfs"
[ "$FSTYPE" = "Ext3" ] && FSTYPE="ext3"
[ "$FSTYPE" = "Ext4" ] && FSTYPE="ext4" #v423 kirk: ext4 support.
[ "$FSTYPE" = "FAT16" ] && FSTYPE="vfat"
[ "$FSTYPE" = "FAT32" ] && FSTYPE="vfat"
[ "$FSTYPE" = "NTFS" ] && FSTYPE="ntfs"
[ "$FSTYPE" = "ISO9660" ] && FSTYPE="iso9660"
[ "$FSTYPE" = "JFS" ] && FSTYPE="jfs"
[ "$FSTYPE" = "XFS" ] && FSTYPE="xfs"
}

NEW CODE:
fsfunc() { #f.s. type param passed in
# 100320 EdV: changed func to provide FSTYPE only when recognized
# - but is it really needed just to change the case?
case $1 in
"Ext2" ) FSTYPE="ext2";;
"ReiserFS" ) FSTYPE="reiserfs";;
"Ext3" ) FSTYPE="ext3";;
"Ext4" ) FSTYPE="ext4";; #v423 kirk: ext4 support.
"FAT16" ) FSTYPE="vfat";;
"FAT32" ) FSTYPE="vfat";;
"NTFS" ) FSTYPE="ntfs";;
"ISO9660" ) FSTYPE="iso9660";;
"JFS" )FSTYPE="jfs";;
"XFS" ) FSTYPE="xfs";;
* ) FSTYPE="";;
esac
}

2. At line 388, I inserted a simple if-then check for the filesystem type, which prevents the script from checking for an older version of Puppy on unrecognized filesystem type partions.

OLD CODE:
if [ "$PARTITIONFS" ];then
fsfunc $PARTITIONFS #sets FSTYPE.
#find out if partition has puppy, or has ${DISTRO_FILE_PREFIX}-xxx.sfs file...
PUPINST=""
ispupfunc $FSTYPE ${DRVSEL}${PARTNUM} #returns PUPVEROLD
[ $? -ne 0 ] && PUPINST=", Puppy version $PUPVEROLD installed"
echo "${DRVSEL}${PARTNUM}: ${FSTYPE}, size ${PARTSIZE}${PUPINST}" >> /tmp/pidrvmsg.txt
fi

NEW CODE:
if [ "$PARTITIONFS" ];then
fsfunc $PARTITIONFS #sets FSTYPE.
#find out if partition has puppy, or has ${DISTRO_FILE_PREFIX}-xxx.sfs file...
if [ "$FSTYPE" ]; then
# 100320 EdV: added FSTYPE test before bothering with checking for installed puppy
PUPINST=""
ispupfunc $FSTYPE ${DRVSEL}${PARTNUM} #returns PUPVEROLD
[ $? -ne 0 ] && PUPINST=", Puppy version $PUPVEROLD installed"
echo "${DRVSEL}${PARTNUM}: ${FSTYPE}, size ${PARTSIZE}${PUPINST}" >> /tmp/pidrvmsg.txt
fi
fi

These two changes allowed me to use the puppyinstaller script on all my "unique" partition systems without problem

EdV

Ok, I have put those changes into 'puppyinstaller' script.

[pemasu]

Code: Select all

Option "TapButton1" "1"
Option "SpecialScrollAreaRight" "true"
Option "VertEdgeScroll" "true"
Option "VertTwoFingerScroll" "true" 

BarryK: Yeah, I meant touchpad tapping And I can confirm that it does not need

Code: Select all

InputDevice "Synaptics Mouse" "SendCoreEvents"

or
And to Section "InputDevice", Identifier "Synaptics Mouse" I added two rows:

Option "SendCoreEvents" "true"

It worked without those addings.

These addings to xorg.conf would be helpful. People have asked same questions at Lucid Puppy thread also.

Code: Select all

Option "TapButton1" "1"
Option "SpecialScrollAreaRight" "true"
Option "VertEdgeScroll" "true"
Option "VertTwoFingerScroll" "true" 

[divisionmd]

Hello,

Testing out Quircky 18.

Found this:

1. Wanted to set a resolution of 1360x768 which i know the screen + the graphics card supports.

but that option was not available in the xorgwizard.

its a manual hack to fix in the xorg.conf i guess?


2. Also tested to turn the screen to portait mode (9:16) but that did turn the screen black..


Anyone got a clue to the above.. ?


Best regards,
JOHan

[jemimah]

Barry,
I think you should consider adding Flsynclient for touchpad configuration. It's a GUI that supports the majority of options that the synaptics driver has. It doesn't mess with your xorg.conf either, it just adds a script to your startup that configures your touchpad settings.

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

It's just a frontend for the synclient that comes with Xorg. Probably something smaller could be written that doesn't link against FLTK.

[Béèm]

Altho I did a first boot with pfix=ram and selected to save to 3fs, IMHO, this stil doesn't work at the next boot.

Code: Select all

# cat /etc/rc.d/PUPSTATE
PUPMODE=12
PDEV1=''
DEV1FS=''
PUPSFS='sdb7,ext2,/quirky-018.sfs'
PUPSAVE='sdb7,ext2,/quirkysave-R40_quirky_18.3fs'
PMEDIA=''
#v3.97: kernel with libata pata has both sata and pata drives in ATADRIVES...
ATADRIVES='sda '
#these directories are unionfs layers in /initrd...
SAVE_LAYER='/pup_rw'
PUP_LAYER='/pup_ro2'
#The partition that has the quirkysave file is mounted here...
PUP_HOME='/mnt/dev_save'
#(in /initrd) ...note, /mnt/home is a link to it.
#this file has extra kernel drivers and firmware...
ZDRV=''
#complete set of modules in the initrd (moved to main f.s.)...
ZDRVINIT='no'
PSWAPFILE=''
PSAVEMARK=''
FASTPARTS='sda1|ntfs sda2|vfat '
# 

as it is mounted as ext2 in my case.

I still think the init script in initrd.gz has to be adapted as well.
Three statements to change from ext2 to ext3.

[Jim1911]

Hi Béèm,
It appears to me that the PUPSTATE is indicating is that your installation is on an ext2 partition. This is what my PUPSTATE indicates for an installation on an ext4 partition.

Code: Select all

PUPMODE=12
PDEV1='sdb6'
DEV1FS='ext4'
PUPSFS='sdb6,ext4,/quirky/quirky-018.sfs'
PUPSAVE='sdb6,ext4,/quirky/quirkysave-018.3fs'
PMEDIA='atahd'
#v3.97: kernel with libata pata has both sata and pata drives in ATADRIVES...
ATADRIVES='sda sdb '
#these directories are unionfs layers in /initrd...
SAVE_LAYER='/pup_rw'
PUP_LAYER='/pup_ro2'
#The partition that has the quirkysave file is mounted here...
PUP_HOME='/mnt/dev_save'
#(in /initrd) ...note, /mnt/home is a link to it.
#this file has extra kernel drivers and firmware...
ZDRV=''
#complete set of modules in the initrd (moved to main f.s.)...
ZDRVINIT='no'
PSWAPFILE=''
PSAVEMARK=''
FASTPARTS='sda1|ntfs sda2|ext3 sda3|ext4 sda4|ext4 sdb1|ext3 sdb3|ext4 sdb4|vfat sdb6|ext4 sdb7|ext3 sdb8|ext4 '

Console output for "mount" command is:

Code: Select all

# mount
rootfs on / type rootfs (rw,relatime)
/dev/sdb6 on /initrd/mnt/dev_save type ext4 (rw,noatime,barrier=1,data=ordered)
/dev/loop1 on /initrd/pup_rw type ext3 (rw,noatime,errors=continue,data=ordered)
tmpfs on /initrd/mnt/tmpfs type tmpfs (rw,relatime,size=101920k)
/dev/loop0 on /initrd/pup_ro2 type squashfs (ro,noatime)
/dev/loop4 on /initrd/pup_ro4 type squashfs (ro,noatime)
/dev/loop5 on /initrd/pup_ro5 type squashfs (ro,noatime)
/dev/loop6 on /initrd/pup_ro6 type squashfs (ro,noatime)
unionfs on / type aufs (rw,relatime,si=7a1229e)
tmpfs on /tmp type tmpfs (rw,relatime,size=3053648k)
none on /proc type proc (rw,relatime)
none on /dev/pts type devpts (rw,relatime,gid=2,mode=620)
none on /sys type sysfs (rw,relatime)
shmfs on /dev/shm type tmpfs (rw,relatime,size=712452k)
none on /proc/bus/usb type usbfs (rw,relatime)
# 

What state does the "mount" command show?

Jim

[alec78]

Hi all,
Whilst waiting for Wary (I thought I would have xorg problems with Quirky 018/Samsung x05 laptop ) I downloaded the Q013_Q018 diff file and made an Q018 iso. Needless to say I was very pleasantly surprised to see the desktop come up. I thought I had selected the i810 driver during set up but report-video say that I have the VESA driver?
VIDEO REPORT: Quirky, version 018

Chip description:
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

Driver used by Xorg:
vesa

Video mode used by Xorg:
Resolution: 1024x768 Depth: 24

Cheers

[broomdodger]

menu > utility > cpu frequency scaling tool

typo "OUIT"

should be "Quit"

[Béèm]

Hi Béèm,
It appears to me that the PUPSTATE is indicating is that your installation is on an ext2 partition. This is what my PUPSTATE indicates for an installation on an ext4 partition.
What state does the "mount" command show?

Jim

Hi Jim, I have to blush
I realize that even after a short 10 days holidays I forgot a lot.
You are right, it's in the mount that it can be seen.

Code: Select all

# mount
rootfs on / type rootfs (rw,relatime)
/dev/sdb7 on /initrd/mnt/dev_save type ext2 (rw,noatime,errors=continue)
/dev/loop1 on /initrd/pup_rw type ext3 (rw,noatime,errors=continue,data=ordered)
/dev/loop0 on /initrd/pup_ro2 type squashfs (ro,noatime)
/dev/loop4 on /initrd/pup_ro4 type squashfs (ro,noatime)
/dev/loop5 on /initrd/pup_ro5 type squashfs (ro,noatime)
unionfs on / type aufs (rw,relatime,si=f935561c)
tmpfs on /tmp type tmpfs (rw,relatime,size=63656k)
none on /proc type proc (rw,relatime)
none on /dev/pts type devpts (rw,relatime,gid=2,mode=620)
none on /sys type sysfs (rw,relatime)
shmfs on /dev/shm type tmpfs (rw,relatime,size=58344k)
none on /proc/bus/usb type usbfs (rw,relatime)
/dev/sdb1 on /mnt/sdb1 type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=cp850,iocharset=iso8859-1,shortname=mixed,quiet,errors=remount-ro)
# 

Si it's ok.
Good work of Barry.