Page 14 of 15
Posted: Mon 18 May 2009, 17:19
by DaveS
This has me puzzled too. I have tried all 4x versions of Puppy with 1.5 and 1.6 versions of Java, and all currently available CUPS versions with OO2.4 and OO3 sfs, all no problem. What else do you have installed?
sound
Posted: Mon 18 May 2009, 17:57
by vito
Hello all:
Downloaded latest version of deeper thought x2 with bug fixes. The sound does not work on my IBM laptop T22 - sound = cs46xx . The sound does not play however. I think that it may be a kernel loading problem. I as there is sone error that flashes on the screen during alsa config saying that something cs46xx is in use by something else/
I load TMX shard from the CD and the sound works from the boot with no configuration. This is why I'm thinking that it may be a kernel issue.
Thx All,
Vito
sound
Posted: Mon 18 May 2009, 18:17
by vito
Hello All Again:
I fixed the sound by copying the modules folder, modprobe.conf and the modules.conf files to overwrite the deeper thought equivalents, and rebooted; now there is sound again in puppy.
So I guess this is not a kernel problem as I had first thought, but some failure to config on boot and in subsequesnt tries by alsaconf
Thx,
Vito
java kills CUPS printing in 4.2
Posted: Tue 19 May 2009, 10:21
by mafae
Try to manually restart CUPS with the command
Are you accessing CUPS through Menu > System > Manage Printing?
Tnx for the hint! Restarting CUPS manually works. Also I meanwhile experimented a bit, and the effect became more clear:
- Started with new blank 4.2 installation (frugal): CUPS works fine
- Installed "jre1.6.0_11.pet":
- CUPS was killed immediately after JRE-pet installation finished.
- Manual re-start works.
- After installation of JRE, CUPS-script does not start automatically anymore.
Cheers,
Mafae
Posted: Tue 19 May 2009, 10:48
by DaveS
Mafae, try this installer, yours sounds faulty. Either the.pup I posted or the later one from Ttuuxxx. If you use the one from Ttuuxxx, just download the tar.gz, extract it and run the installer. This has been 100% for me............
http://www.murga-linux.com/puppy/viewtopic.php?t=41098
Posted: Tue 19 May 2009, 17:07
by jebaJQ8
@WhoDo：
Thank you for including the JQ8flat icon theme in 4.2.1.
I don't know this should say a bug.
I notice that "mount" icon is not included in the JQ8flat theme.
I made the "mount" icon for the Desktop and also made the "refresh" icon for the menu panel.
If you could, I would like you to include these icons.
Regards,
JebaJQ8
Posted: Tue 19 May 2009, 21:31
by WhoDo
jebaJQ8 wrote:I made the "mount" icon for the Desktop and also made the "refresh" icon for the menu panel.
If you could, I would like you to include these icons.
I'm happy to do that, JebaJQ8. Thank you for the excellent theme!
Posted: Tue 19 May 2009, 22:56
by cthisbear
WhoDo:
m4a Media files work out of the box in RC3.
I PMed coolpup and you as well.
Thanks mate, gonna find something else to whinge about now.
Remind myself....must avoid looking into my mirror.
Chris.
Java kills CUPS
Posted: Wed 20 May 2009, 04:45
by mafae
Hi,
after some further testing, the CUPS-problem became more clear:
It has nothing to do with Java or Openoffice, it is a matter of how CUPS is accessed:
Menu>Setup>CUPS Printer Wizard
Works fine and reliable.
Menu>System>Manage Printing
Kills CUPS nearly always!
After manual restart of CUPS
it works fine again.
So it seems rcrsn51 was on the right way, when he asked
Are you accessing CUPS through Menu > System > Manage Printing?
[/b]
Posted: Wed 20 May 2009, 08:53
by tempestuous
Because I have never bothered to download Puppy 4.2, I only learned about this problem with Broadcom wifi devices recently:
trio wrote:In 4.2 Final..bcm43xx is still being a problem...for those of you who wants a workaround..just edit /etc/rc.d/MODULESCONFIG
Dear oh dear. It seems that the developers of 4.2 included many, if not all, of the extra 4.1.x drivers I posted here
http://www.murga-linux.com/puppy/viewtopic.php?t=34159
This is a major error. If I had been told about this before the decision was made, I would have advised against it.
Quite a number of the extra drivers I provided are alternative drivers, to deal with specialised hardware variations or special situations. They will compete with the standard kernel drivers, so my driver packages include a modules-preference configuration (/etc/rc.d/MODULESCONFIG) which will force Puppy to use the new driver in preference to the standard one.
This will cause problems where the old driver is known to work better than the new one ... as in the case of Broadcom wifi devices in anything other than Dell or HP computers.
trio wrote:In 4.2 Final..bcm43xx is still being a problem...for those of you who wants a workaround..just edit /etc/rc.d/MODULESCONFIG (line 33) delete the red word
PREFLIST=' rt2500usb:rt73usb ath5k:ath_pci orinoco_nortel:hostap_plx orinoco_plx:hostap_plx orinoco_tmd:hostap_plx orinoco_pci:hostap_pci bcm43xx:wl b43:wl b43legacy:wl ssb:wl prism54:p54pci r8169:r8101 rtl8187:r8187 '
Unfortunately, that's only half-correct. As well:
"b43:wl" and "b43legacy:wl" should be deleted.
"bcm43xx:wl" should be changed to "bcm43xx:ssb"
That's because the new Broadcom b43/b43legacy modules, which work in conjunction with the ssb module, should be used in preference to the deprecated bcm43xx module. The firmware in Puppy is compatible with b43/b43legacy, and is NOT compatible with bcm43xx.
The full and correct PREFLIST entry (from Puppy 4.1.2) is
Code: Select all
PREFLIST=' rt2500usb:rt73usb ath5k:ath_pci orinoco_nortel:hostap_plx orinoco_plx:hostap_plx orinoco_tmd:hostap_plx orinoco_pci:hostap_pci martian_dev:ltserial bcm43xx:ssb prism54:p54pci r8169:r8101 '
Unfortunately (groan) there are also reports that Puppy 4.2 fails to automatically uncompress the b43 firmware, but hopefully this may be fixed once the preferences are corrected.
I now attach the correct MODULESCONFIG with PREFLIST entries. This is to replace trio's "No_bcm43xx_patch.pet", which is wrong.
Please use this in the next 4.2 update.
Posted: Wed 20 May 2009, 17:05
by DaveS
Thanks for this T. Works flawlessly...............
Posted: Wed 20 May 2009, 19:32
by rcrsn51
mafae wrote:Menu>System>Manage Printing
Kills CUPS nearly always!
This has been fixed in 4.2.1.
Posted: Thu 21 May 2009, 07:31
by mafae
Many thanks rcrsn51. Looking forward to 4.2.1!
Martin
(Default system Puppy 4.1.2 on Thinkpad R50)
Re: A Bug
Posted: Sun 24 May 2009, 21:34
by mave
floborg wrote:In the lower left-hand corner of the desktop, the drive icons are clustered on top of one another. In the lower right-hand corner, the Lock and Trash icons are clustered on top of one another.
The above happened using an 800x600 resolution, but did not occur in Puppy 4.1.2.
In updated 4.21 again the same problem.
Any help?
Re: A Bug
Posted: Tue 26 May 2009, 05:07
by floborg
mave wrote:floborg wrote:In the lower left-hand corner of the desktop, the drive icons are clustered on top of one another. In the lower right-hand corner, the Lock and Trash icons are clustered on top of one another.
The above happened using an 800x600 resolution, but did not occur in Puppy 4.1.2.
In updated 4.21 again the same problem.
Any help?
I can verify this bug. Again, it does not occur in Barry's latest puppy release (upup).
Also, with an 800x600 resolution and switching to IceWM, the GB or G (can't tell) in the freememapplet is cut off.
Should we report this stuff in separate threads? I get the feeling that single bug reports in long threads like this get overlooked. Of course, the same is probably true of individual threads - depends on who reviews them.
Posted: Wed 27 May 2009, 02:36
by makropo
tempestuous wrote:Because I have never bothered to download Puppy 4.2, I only learned about this problem with Broadcom wifi devices recently:
trio wrote:In 4.2 Final..bcm43xx is still being a problem...for those of you who wants a workaround..just edit /etc/rc.d/MODULESCONFIG
That's because the new Broadcom b43/b43legacy modules, which work in conjunction with the ssb module, should be used in preference to the deprecated bcm43xx module. The firmware in Puppy is compatible with b43/b43legacy, and is NOT compatible with bcm43xx.
Unfortunately (groan) there are also reports that Puppy 4.2 fails to automatically uncompress the b43 firmware, but hopefully this may be fixed once the preferences are corrected.
I now attach the correct MODULESCONFIG with PREFLIST entries. This is to replace trio's "No_bcm43xx_patch.pet", which is wrong.
Please use this in the next 4.2 update.
I believe this has been fixed in 4.2.1
Until 4.2.1 was released I was removing 4.2 and booting 4.1.2 for a wireless connection. Now in 4.2.1 b43 loads and wireless is detected right away.
Oh where oh where has my argument gone?
Posted: Sun 31 May 2009, 06:12
by SilverPuppy
Hey moderators,
Where'd you move the hornets nest I stirred up to? I don't see it, but it's obviously been relocated......
Re: Oh where oh where has my argument gone?
Posted: Sun 31 May 2009, 06:17
by WhoDo
SilverPuppy wrote:Hey moderators,
Where'd you move the hornets nest I stirred up to? I don't see it, but it's obviously been relocated......
It has been placed where it belongs ... here:
http://www.murga-linux.com/puppy/viewtopic.php?t=43030
Posted: Sun 31 May 2009, 06:23
by mcewanw
To thread "Optimising Puppy Performance":
http://www.murga-linux.com/puppy/viewto ... 382#310382
Note: my post that was also moved contained a bug notification:
The only thing I've noticed so far that didn't work out-of-the-box on my system [with Puppy 4.2.1] was sound (never had that problem with any pup before). I haven't checked all the above threads to see if others have had the same problem because I fixed it for myself. However, a new user wouldn't have a clue how to fix it. For me I had to:
open an rxct console and enter:
alsaconf
That program correctly detected my card and on the next boot the until then missing taskbar volume icon appeared and sound worked.
Broadcom wireless still not fixed in 4.2.1
Posted: Tue 16 Jun 2009, 22:31
by stlouisubntu
makropo wrote:tempestuous wrote:Because I have never bothered to download Puppy 4.2, I only learned about this problem with Broadcom wifi devices recently:
trio wrote:In 4.2 Final..bcm43xx is still being a problem...for those of you who wants a workaround..just edit /etc/rc.d/MODULESCONFIG
That's because the new Broadcom b43/b43legacy modules, which work in conjunction with the ssb module, should be used in preference to the deprecated bcm43xx module. The firmware in Puppy is compatible with b43/b43legacy, and is NOT compatible with bcm43xx.
Unfortunately (groan) there are also reports that Puppy 4.2 fails to automatically uncompress the b43 firmware, but hopefully this may be fixed once the preferences are corrected.
I now attach the correct MODULESCONFIG with PREFLIST entries. This is to replace trio's "No_bcm43xx_patch.pet", which is wrong.
Please use this in the next 4.2 update.
I believe this has been fixed in 4.2.1
Until 4.2.1 was released I was removing 4.2 and booting 4.1.2 for a wireless connection. Now in 4.2.1 b43 loads and wireless is detected right away.
First, @ WhoDo,
Well done on Puppy 4.2 and 4.2.1! Overall great update release and great step forward for Puppy Linux!! Thanks so much for your hard work (and for your results) on this release. However, it is understandable how difficult it is to take such a big step forward without sliding back a little (perhaps a regression or two.)
@ WhoDo, and makropo
I have found the Broadcom wireless issue is still not fixed in 4.2.1. In 4.2, I attempted the workaround and downloaded and installed the .pet, but without success.
Further, I chronicled my struggle with this regression in the following blogpost:
http://www.linux.com/community/blogs/Pu ... -saga.html
Please understand that although the wireless regression saga is in the blog entry title, this post is mostly in PRAISE of Puppy Linux (and especially the efforts of BarryK and WhoDo (and the other unnamed devs who also worked on Puppy.)
My wish is for another bugfix update correcting this issue (and the other one described in the blog entry), but I understand and can accept that I can always use 4.1.2 which works fine for me.
Also, BTW, I also say "Well done!" on all the bling you brought 4.2 which can really help to make strides in converting Windows users (your bling surpasses Vista IMHO.)
Again, well done and thanks.