Page 4 of 7

Posted: Sun 07 Oct 2007, 14:28
by linuxcbon
new bug ?
in /var/log/messages

Code: Select all

(none) auth.debug pidgin: looking for plugins in '/usr/lib/sasl2', failed to open directory, error: No such file or directory

Posted: Sun 07 Oct 2007, 20:23
by Jesse
Hello,

I have not been able to get my usb speakers to be retained as the working sound device on reboot. Puppy 3.0.
I've been looking into it, and it is not so straight forward, as on the surface and looking at how things interact, it should have been retained.
When I set the usb speakers as the sound device with the wizard they work great. But they are not a pci sound card, so there is no 'alias snd-card-X' line in /etc/modprobe.conf, only an 'alias sound-slot-0 snd-usb-audio', and the snd-cmipci is omitted from /etc/modprobe.conf.
Then when I reboot, the motherboards snd-cmipci driver gets loaded at 'alias snd-card-0' position in /etc/modprobe.conf, This is done by some automatic hardware detect script? (I have not found this one yet).
Motherboard BIOS does not let me disable the onboard sound card.
When the snd-cmipci gets loaded, the usb audio does not work.
When I blacklist the snd-cmipci it is still loaded.
When I manage to get everything into a non conflicting configuration, and reboot, and settings are retained, snd-usb-audio is still reported as 'default sound device' from "cat /proc/asound/cards", the usb-audio still does not work.

Can someone think of what else i could try?

Jesse

Posted: Sun 07 Oct 2007, 20:41
by linuxcbon
In /tmp/xerrs.log
I got :

Code: Select all

(EE) Failed to load module "glx" (module does not exist, 0)
so I removed glx from xorg.conf

I also got :

Code: Select all

(ROX-Filer:2905): Gtk-WARNING **: Could not find the icon 'mime-application:x-squashfs-image'. The 'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
	http://icon-theme.freedesktop.org/releases
Welcome to Xproc 1.2 (for Linux 2.2.x)... Loading information from your system...

Posted: Sun 07 Oct 2007, 20:57
by PhilCoo
Not sure if you can count as a bug or minor inconvenience ? When exiting from live-cd and saving session to cd,previous versions showed the progress as the data was written,now you just get a warning to make sure the drive tray is closed.

Is there any way to re-start Gxine after using "kill" to close when it stops responding when trying to open internet radio ? I have now installed streamtuner which helps a lot but ended up deleting all the default media marks in Gxine and replacing them with my own choices.

Great work otherwise on ease of use.

Thanks

Phil :)

Re: Favourite Install Goes MIssing with 3.00

Posted: Sun 07 Oct 2007, 22:06
by WhoDo
BarryK wrote:
WhoDo wrote:I have noticed there is no longer an option to install Puppy as Frugal with data saved to the partition rather than a pup_save.2fs file.

That was my preferred install for most machines, as it gave all the benefits of a Frugal install in terms of upgrading, but didn't restrict my data to a single bag file that could become corrupt.

Was this a considered decision, Barry? Or did the option just fall by the wayside? Maybe I missed while I was absent moving house and jobs, or something.
Um, I thought save to full partition is still there.
Nope. I get the option to choose a partition where I want the save file to go, and a choice of private extension for the file name, but no option to just save directly to the partition without creating a pup_save.2fs file. I guess it must have slipped by the wayside in the process of getting customised save files running.

Thanks for taking the time to answer, Barry. Much appreciated.

Cheers

gxine

Posted: Mon 08 Oct 2007, 02:27
by GrumpyWolfe
Hi all

This is what I have done when gxine has failed and I use the kill option. menu/system/KP running processes. Look down the list and find gxine there will be entires kill the one that just says gxine and then you can start as normal.

Posted: Mon 08 Oct 2007, 04:51
by PaulBx1
So that means it is jwm that is at fault? The right click on the taskbar, and selecting "kill" is a jwm thing, right?

Back in my old unix days I would have known how to kill from the command line almost without thinking. The command line was all there was. Mostly gone from my brain now... :(

gsview does not work (solved)

Posted: Mon 08 Oct 2007, 07:18
by andrei
For some reason which I dont understand, gsview refused to show ps files in 3.00 and complained of the wrong version of gs_init.ps
I solved this problem by deleting the folder /usr/share/ghostscript/8.15/lib/ and replacing it with /usr/share/ghostscript/8.15/lib/ from the old pup_221.sfs

Gsview with ghostscript-8.15 is the best available postscript viewer in terms of the quality of text image. For some reason the later versions of ghostscript, for example 8.54 or 8.57 are worse in terms of quality than 8.15. I don't understand why, but I can demonstrate it.

Posted: Mon 08 Oct 2007, 09:02
by BarryK
Jesse wrote:Hello,

I have not been able to get my usb speakers to be retained as the working sound device on reboot. Puppy 3.0.
I've been looking into it, and it is not so straight forward, as on the surface and looking at how things interact, it should have been retained.
When I set the usb speakers as the sound device with the wizard they work great. But they are not a pci sound card, so there is no 'alias snd-card-X' line in /etc/modprobe.conf, only an 'alias sound-slot-0 snd-usb-audio', and the snd-cmipci is omitted from /etc/modprobe.conf.
Then when I reboot, the motherboards snd-cmipci driver gets loaded at 'alias snd-card-0' position in /etc/modprobe.conf, This is done by some automatic hardware detect script? (I have not found this one yet).
Motherboard BIOS does not let me disable the onboard sound card.
When the snd-cmipci gets loaded, the usb audio does not work.
When I blacklist the snd-cmipci it is still loaded.
When I manage to get everything into a non conflicting configuration, and reboot, and settings are retained, snd-usb-audio is still reported as 'default sound device' from "cat /proc/asound/cards", the usb-audio still does not work.

Can someone think of what else i could try?

Jesse
Jesse, maybe these code areas would be helpful to examine:
/etc/rc.d/rc.local0, from line 368
/etc/rc.d/rc.modules, from line 76
/etc/rc.d/rc.modules2 <<<particularly this one.

Note, you can also blacklist any module.

Posted: Mon 08 Oct 2007, 09:05
by BarryK
linuxcbon wrote:In /tmp/xerrs.log
I got :

Code: Select all

(EE) Failed to load module "glx" (module does not exist, 0)
so I removed glx from xorg.conf

I also got :

Code: Select all

(ROX-Filer:2905): Gtk-WARNING **: Could not find the icon 'mime-application:x-squashfs-image'. The 'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
	http://icon-theme.freedesktop.org/releases
Welcome to Xproc 1.2 (for Linux 2.2.x)... Loading information from your system...
These are non-fatal errors.
The glx module is specified in xorg.conf just in case the extra xorg modules package is installed.

MS VIRTUAL PC 2007

Posted: Mon 08 Oct 2007, 12:26
by Redvamp128
Thanks Barry... The 3.00retro worked. It allows me to click in windows to choose the video using xvesa. I guess the new kernal may have something to do with it.

Posted: Mon 08 Oct 2007, 13:12
by laptopnewbee
am i the only one who has gotten the issue i reported in my post http://www.murga-linux.com/puppy/viewto ... 037#145037
or did it just get missed in the rush of other things?

i can't try to get wifi working in 3.00 final unless i can enter commands through xterm (by whatever name it's called) without characters being changed from the ones i input.

Posted: Mon 08 Oct 2007, 14:31
by Flash
PhilCoo wrote:...Is there any way to re-start Gxine after using "kill" to close when it stops responding when trying to open internet radio?...

Thanks

Phil :)
The problem seems to be that the older version of Gxine in 3.00 doesn't actually die when you kill it. I discovered that after I close or kill Gxine from the desktop, I have to open Menu > System > KP manage running processes, find the running instance of gxine, highlight it and then kill it. Then I can restart Gxine.

I also found that the version of Gxine in 3.00 won't play a DVD, at least on the computer I usually use. I haven't tried it on another computer. I only discovered last night that the Gxine in 3.00 freezes after a while when I try to play a DVD, while the Gxine in 2.17 plays the DVD just fine.

I see that Paulbx1 reports the same problems with gxine..

Posted: Mon 08 Oct 2007, 16:44
by linuxcbon
Same happened to me with gxine : hangs very often, quite unstable but didnt find the origin of the bug...
It wont play some commercial dvds ?
And cannot kill it from desktop, must be killed with command line.

Gxine "kill" problem

Posted: Mon 08 Oct 2007, 17:02
by PhilCoo
Hi All, thanks to Grumpy Wolfe & Flash for feedback,will try this later on with internet radio on Gxine.

Phil :wink:

Misleading init message for missing pup_xxx.sfs

Posted: Mon 08 Oct 2007, 22:18
by rerwin
Whenever the pup_xxx.sfs file cannot be found, due to either a "/" in psubdir, a nonexistant psubdir or no such file at the root level, the console output is
Searching for Puppy files in computer disk drives...
/bin/sh: can't access tty; job control turned off
But the init logic (line 365+) below implies that a more appropriate message was intended, but went arwy:

Code: Select all

if [ "$PUPSFS" = "" ];then
 echo -en "\\033[1;31m" >/dev/console #31=red
 echo -n "pup_${PUPPYVERSION}.sfs not found. Dropping out to initial-ramdisk console..."
 /bin/echo -e "\\033[0;39m" >/dev/console
 exec /bin/sh >/dev/console 2>&1
else
However, the line
pup_300.sfs not found. Dropping out to initial-ramdisk console...#
appears in the bootinit.log file. Furthermore, the "exec /bin/sh" line appears to be generating the "/bin/sh:..." error message, instead of restoring a color (I assume).

Correcting that logic to display the "not found" line would save people much frustration when they cannot get Puppy to boot (probably due to a typo in a menu.lst file).
Richard

init script housekeeping nit

Posted: Mon 08 Oct 2007, 22:49
by rerwin
The init script saves a copy of its puppy file locations held in /tmp for CD boots and installs with pup files in a psubdir, but creates no such files when puppy files are at the root level. So, when an empty /tmp directory is copied to /initrd/tmp it leaves residue from a previous boot, such as from CD (or the copy may not even be attempted).

To avoid misinformation to debuggers, /initrd/tmp should be left empty if the init /tmp directory is empty. Seeing the PUPPYFILES as being in hdc after a HD bootup is confusing..
Richard

Re: Misleading init message for missing pup_xxx.sfs

Posted: Tue 09 Oct 2007, 08:14
by BarryK
rerwin wrote:Whenever the pup_xxx.sfs file cannot be found, due to either a "/" in psubdir, a nonexistant psubdir or no such file at the root level, the console output is
Searching for Puppy files in computer disk drives...
/bin/sh: can't access tty; job control turned off
But the init logic (line 365+) below implies that a more appropriate message was intended, but went arwy:

Code: Select all

if [ "$PUPSFS" = "" ];then
 echo -en "\\033[1;31m" >/dev/console #31=red
 echo -n "pup_${PUPPYVERSION}.sfs not found. Dropping out to initial-ramdisk console..."
 /bin/echo -e "\\033[0;39m" >/dev/console
 exec /bin/sh >/dev/console 2>&1
else
However, the line
pup_300.sfs not found. Dropping out to initial-ramdisk console...#
appears in the bootinit.log file. Furthermore, the "exec /bin/sh" line appears to be generating the "/bin/sh:..." error message, instead of restoring a color (I assume).

Correcting that logic to display the "not found" line would save people much frustration when they cannot get Puppy to boot (probably due to a typo in a menu.lst file).
Richard
Thanks for that. The missing line is now not missing.

Posted: Tue 09 Oct 2007, 13:35
by rarsa
Found a problem with my broadcom wireless card.

I opened a new thread:

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

Posted: Tue 09 Oct 2007, 20:22
by Jesse
BarryK wrote:
Jesse wrote:Hello,

I have not been able to get my usb speakers to be retained as the working sound device on reboot. Puppy 3.0.
I've been looking into it, and it is not so straight forward, as on the surface and looking at how things interact, it should have been retained.
When I set the usb speakers as the sound device with the wizard they work great. But they are not a pci sound card, so there is no 'alias snd-card-X' line in /etc/modprobe.conf, only an 'alias sound-slot-0 snd-usb-audio', and the snd-cmipci is omitted from /etc/modprobe.conf.
Then when I reboot, the motherboards snd-cmipci driver gets loaded at 'alias snd-card-0' position in /etc/modprobe.conf, This is done by some automatic hardware detect script? (I have not found this one yet).
Motherboard BIOS does not let me disable the onboard sound card.
When the snd-cmipci gets loaded, the usb audio does not work.
When I blacklist the snd-cmipci it is still loaded.
When I manage to get everything into a non conflicting configuration, and reboot, and settings are retained, snd-usb-audio is still reported as 'default sound device' from "cat /proc/asound/cards", the usb-audio still does not work.

Can someone think of what else i could try?

Jesse
Jesse, maybe these code areas would be helpful to examine:
/etc/rc.d/rc.local0, from line 368
/etc/rc.d/rc.modules, from line 76
/etc/rc.d/rc.modules2 <<<particularly this one.

Note, you can also blacklist any module.
Hi,

I managed to get the computer to boot with USB as the active sound device.
I modified the rc.modules and rc.modules2 so that they did not modify the alsa setup, there are comments in the alsa section of /etc/modprobe.conf file which says 'do not modify', lol.
Ok, so I think what might be happening is "hardware detection" by the rc.modules* scripts, which is what may get the sound card sorted on first boot. But, when I've already set my alsa setup, the scripts shouldn't be forcing me to have the module loaded.
Perhaps there needs to be some setting, with two user options: "automatic sound" and "no automatic, just selected by alsa wizard".

There is a bug in the rc.modules* scripts processing, as they can generate multipe configurations for the same X (card/slot) as they only look for the 'snd-card-' lines. This will undoubtably confuse alsa when the user has USB sound and another sound card which they are not using.

Even when there is no conflicting/double-up settings in /etc/modprobe.conf, and with all sound dirvers specified, the snd-usb-audio driver does not work for me. I have no idea why.
It only works when snd-usb-audio is the only sound card.

Note that blacklisting does not fix this, as the rc.modules* scripts still detect it and enter it with the usual descriptions "alias sound-slot-X ..." lines in /etc/modprobe.conf. i.e. two drivers specified for card 0.
Earlier I claimed that blacklisting snd-cmipci did not prevent it loading, I didn't check that was correct. I think I confused detecting with loading. The snd-cmipci is still detected when it is blacklisted, but presumably cannot be loaded.

Jesse