Quirky 018 feedback

[BarryK]

Some printing issues:

The file /etc/cups/snmp.conf has the odd ownership root:[7]. This prevents CUPS from detecting network printers. I changed it to root:nobody and did a CUPS restart.

The symlink /usr/lib/cups/backend/smb to /opt/samba/bin/smbspool is missing. This prevents access to Windows shared printers.

The file /etc/opt/samba/smb.conf needs to be world-readable.

Fixed:
http://bkhome.org/blog/?viewDetailed=01496

[BarryK]

One problem, the 4fs save file doesn't work. Using a frugal installation on an ext4 partition, entered system values, rebooted, created a 4fs save file, however it was not recognized on the next reboot.

As a workaround for now, I have restricted the shutdown script to only offer ext2 and ext3. That's good enough, those who want a journal in their pupsave file can get it with ext3.

One day in the future I'll figure out why it won't boot with a ext4 pupsave file.

[BarryK]

RT73usb WLAN interface detected OK but doesn't connect using either of the wizards. Module may need re-compiling for this latest kernel.

The rt73usb module is the one that comes with the 2.6.33.2 kernel source package.

I have a usb wireless unit that uses the rt73usb module, and it works fine.

Would you mind examining /var/log/messages, see if there is anything related to rt73usb that might give a clue what is wrong in your case.

[nooby]

Barry, you are right, I did remember that there was something with the spaces but then had forgotten what it was all about.

now when I change from this Folding Mobility Scooter - TravelScoot - Assembly1.flv
to this FoldingMobilityScooter-TravelScoot-Assembly1.flv

then it plays both flv and mp4.

Do I remember correctly that they can play with space in the name if one change something in the libs? somethign with " " added?

Sorry me have forgotten. But how would a newbie using puppy know about such things?

I mean now I know but all the other that dl the iso and try it out for first time?

Not me criticising only trying to be practical.

I maybe misunderstand this post?

http://www.murga-linux.com/puppy//viewt ... 147#409147

bash-3.00# ffmpeg -i "/root/Yngwie Malmsteen.mp3" -f au - | aplay -D plughw
ffmpeg: error while loading shared libraries: libfaad.so.0: cannot open shared object file: No such file or directory
aplay: playback read error


fix

Code:
bash-3.00# ln -s /usr/lib/libfaad.so.2.0.0 /usr/lib/libfaad.so.0

01micko says "Um, that bug is still there!"

I saw that the file name is Yngwie Malmsteen.mp3 with a space between first and second name.

Could that be related then maybe?

[capoverde]

Testing Quirky 018 further: the background image and the GTK theme are back in the next session, not so the number of desktops (I had made 4) - probably this was reported already.

The drive capacity for a USB flash card is stated correctly in Pmount after inserting successive different devices, whereas the popup message appearing when hovering the mouse cursor on the drive icon always reports the capacity of the first device that was inserted, no use refreshing nor restarting X.

[Tui]

I have just d/loaded this latest version, and tested on a couple
of machines.

First machine a Dell GX100 and have noticed that this version
won't detect my wifi card. Previous versions of Puppy, such as
up to v4.2, kernel 2.6.25.16 see this card as ACX_PCI Texas Instruments,
111 54mbs Wireless Interface, but none of the QUIRKY series
find this card !!

I reported this fault with Quirky 13

So what script do I need to change to get it working? From
memory I don't think any of Puppy v4.3.1 series work.

So what do I need to change here in Quirky 18 to get it working ?


Cheers Tui

[Sage]

Glad to see that all chipsets shutdown correctly, again. BK managed it for the first time (since series 1 with k 2.4) back around Q6, even with troublesome SiS ones, then there was an hiatus around Q10. Somebody somewhere seems to know what's been the problem.
Otherwise, Q18 is impressive, even though I cannot get streaming radio to give any sound output. [Tried all the usual expedients.]

[JustGreg]

I have been using Quirky 018 frugal USB (VFAT) Hard Drive installation with my Aspire Revo. I have noticed that connecting to my WPA2 wireless network takes longer. With Puppy 4.3.1 and its WPA supplicant program, it normally takes about 1.5 to 2 seconds to connect. With Quirky 018, it takes 8 seconds to connect. This is not a major problem. (new) I found the source of the problem. It is on the router side. If I connect right after a cold start of the router, the time is the normal 1.5 to 2 seconds. If I connect and reboot without restarting the router then I get the longer 8 second time.

I tried using the mplayer_codecs_full-20071007.pet to see if I could get Gnome Mplayer to play MMS streams. It would connect to the stream and download data, but, no audio was played. Probably another kernel update issue.

(new) With Puppy 4.3.1, I use the NVIDIA-190.53-k2.6.30.5.pet driver for the Aspire Revo. It works fine.

Thanks again for all the work on Quirky.

[Sage]

...streams. It would connect to the stream and download data, but, no audio was played.

Yup, exactly what I found.

[EdV]

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

[rjbrewer]

...streams. It would connect to the stream and download data, but, no audio was played.

Yup, exactly what I found.

I usually use "about:config" in seamonkey to enable mms streams
with various media players, when watching "Delicast.com".

It's not working now; even with a different mplayer.

Maybe a problem with new kernel or new seamonkey?

[tronkel]

@Barry

here is the relevant output from /var/log/messages regarding the Ralink RT73usb module.

As you can see, it seems to be an authentication problem.

Apr 11 18:04:03 puppypc user.info kernel: Registered led device: rt73usb-phy0::radio
Apr 11 18:04:03 puppypc user.info kernel: Registered led device: rt73usb-phy0::assoc
Apr 11 18:04:03 puppypc user.info kernel: Registered led device: rt73usb-phy0::quality
Apr 11 18:04:03 puppypc user.info kernel: usbcore: registered new interface driver rt73usb
Apr 11 18:04:21 puppypc user.info kernel: rt73usb 2-6:1.0: firmware: requesting rt73.bin
Apr 11 18:04:45 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f (try 1)
Apr 11 18:04:45 puppypc user.debug kernel: wlan0: direct probe responded
Apr 11 18:04:45 puppypc user.debug kernel: wlan0: authenticate with AP 00:24:17:b8:06:3f (try 1)
Apr 11 18:04:45 puppypc user.debug kernel: wlan0: authenticate with AP 00:24:17:b8:06:3f (try 2)
Apr 11 18:04:45 puppypc user.debug kernel: wlan0: authenticate with AP 00:24:17:b8:06:3f (try 3)
Apr 11 18:04:46 puppypc user.debug kernel: wlan0: authentication with AP 00:24:17:b8:06:3f timed out
Apr 11 18:05:07 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f (try 1)
Apr 11 18:05:07 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f (try 2)
Apr 11 18:05:08 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f (try 3)
Apr 11 18:05:08 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f timed out
Apr 11 18:05:18 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f (try 1)
Apr 11 18:05:19 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f (try 2)
Apr 11 18:05:19 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f (try 3)
Apr 11 18:05:19 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f timed out
Apr 11 18:05:28 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f (try 1)
Apr 11 18:05:28 puppypc user.debug kernel: wlan0: direct probe responded
Apr 11 18:05:28 puppypc user.debug kernel: wlan0: authenticate with AP 00:24:17:b8:06:3f (try 1)
Apr 11 18:05:28 puppypc user.debug kernel: wlan0: authenticate with AP 00:24:17:b8:06:3f (try 2)
Apr 11 18:05:28 puppypc user.debug kernel: wlan0: authenticate with AP 00:24:17:b8:06:3f (try 3)
Apr 11 18:05:28 puppypc user.debug kernel: wlan0: authentication with AP 00:24:17:b8:06:3f timed out
Apr 11 18:05:39 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f (try 1)
Apr 11 18:05:39 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f (try 2)
Apr 11 18:05:39 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f (try 3)
Apr 11 18:05:39 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f timed out
Apr 11 18:06:03 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f (try 1)
Apr 11 18:06:03 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f (try 2)
Apr 11 18:06:03 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f (try 3)
Apr 11 18:06:03 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f timed out
Apr 11 18:06:10 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f (try 1)
Apr 11 18:06:11 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f (try 2)
Apr 11 18:06:11 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f (try 3)
Apr 11 18:06:11 puppypc user.debug kernel: wlan0: direct probe to AP 00:24:17:b8:06:3f timed out
Apr 11 18:06:32 puppypc user.debug kernel: wlan0: direct probe responded
Apr 11 18:06:32 puppypc user.debug kernel: wlan0: authenticate with AP 00:24:17:b8:06:3f (try 1)
Apr 11 18:06:32 puppypc user.debug kernel: wlan0: authenticate with AP 00:24:17:b8:06:3f (try 2)
Apr 11 18:06:32 puppypc user.debug kernel: wlan0: authenticate with AP 00:24:17:b8:06:3f (try 3)
Apr 11 18:06:32 puppypc user.debug kernel: wlan0: authentication with AP 00:24:17:b8:06:3f timed out

[broomdodger]

Glad to see that all chipsets shutdown correctly, again. BK managed it for the first time (since series 1 with k 2.4) back around Q6, even with troublesome SiS ones, then there was an hiatus around Q10.

Sharp PC-PJ2-S2 300MHz Celeron

restarts ok
--but--
will NOT shutdown, need to press power button

How do I find the "chipset"?

[TmartinT]

Hi ,

@broomdodger

I would try a boot kernel argument : acpi=off

ad this in your grub.conf or menu.lst after the others (if present)

eg : kernel /puppy018/vmlinuz pmedia=atahd pdev1=sda6

psubdir=puppy018 acpi=off

your machine probably doesn't support acpi , so the halt command

goes in a black hole.

[TmartinT]

Hi ,

@Sage & rjbrewer

Sage wrote:
Quote:
--------------------------------
...streams. It would connect to the stream and download data, but, no audio was played.
---------------------------------

Have you tried to start from a shell ?

That should produce some error messages in it .

Regards

TmartinT

[GrumpyWolfe]

Hi Barry

Not sure if this is a bug or just my hardware I have a Acer Aspire one net book and when I first booted I thought that my sound card was not going to work ran sound card set up and all then open the Retrovol mixer controller and found that the speaker was check but turned all the way down. Other than that things are great.

[BarryK]

There are a couple of tweeks that can be added to /etc/fonts:

In the fonts.conf file, if one adds DejaVu Sans entry right above both ocurances of Bitstream Vera Sans in both <alias> lists, then Nimbus Sans L won't have deference over DejaVu Sans in some interface elements. - looks much better, scales better, easier on the eyes.

In q18, I did this, but needed to reboot. Upon reboot, all looked fine.

In the local.conf file, if one adds the code:

Code: Select all

<!-- Reject bitmap fonts -->
 <selectfont>
  <rejectfont>
   <pattern>
     <patelt name="scalable"><bool>false</bool></patelt>
   </pattern>
  </rejectfont>
 </selectfont>

This will prevent the old X11 bitmap fonts from having deference over DejaVu Sans in dillo and opera.

The other alternative that works for me in all recent puppies 431+ is to simply replace the /etc/fonts folder with one from any other distribution or the default one from a fontconfig package. But, this is only tested at 800x600x24 crt 14". It seems to provide better overall font behaviour but adds a small amount of heft.

Thanks for that info. These fixes will be in future builds from Woof, but I left the modification in local.conf commented-out for now, so users can uncomment it to try it -- just wanted to get feedback on that one first.

[BarryK]

Hardinfo not showing kernel modules ? and - is it DMF (bios info)
maybe a later version of Hardinfo if and when time allows.

Quirky 018 accidentally got built with an older hardinfo. Next build will have latest Hardinfo, which works.

[BarryK]

.config/.fbpanel:

AUTOEXPANDNO=flase <<not sure about this

Everything else working fine with low resource use. Openbox is great!

Heh heh, yeah a typo. That is fixed for the next build of Quirky.

[BarryK]

Solved rjbrewer post had fix
exec gnome-mplayer "$@"

Thanks, fixed.