Puppy Linux Discussion Forum

[shinobar]

@Zigbert
Can be off-topic but may be relating with the '.utf8' or '.UTF-8' issue.

You are the pioneer of NLS on Puppy. So, i'd like you to know this.
We need to make many symbolic links for the NLS of your applications.

I'd like to recommend you shifting to the gettext system.

[zekebaby]

Every so often (once every 4 or 5 boots) I completely lose sound. Rerunning alsaconf reports "No supported PnP or PCI card found". lsmod shows snd_intel8x0 is still loaded. Reboot clean with no warysave and sound is back. A couple of reboots later, it's gone again!!! This did not happen in 096 or 097.

Any ideas on how to get sound back without deleting my warysave? Thanks in advance!

[NinerSevenTango]

md5sum checked the iso after burning slow, it checks out.

Boot pfix=ram with wary-098.

lspci reports Atheros wireless card, same as in Quirky (in which wireless works).

Doesn't matter which network wizard is used. Tried the simple one and the classic one.

Access points are detected. Attempting to connect to an open, unencrypted access point fails. Rebooting, multiple attempts, can not establish connection.

This is a Toshiba Satellite Pro s300-1511 laptop. This is the first time it's failed to work on wireless. Other OS versions that work: 4, Lucid, Quirky, other Linii, XP, Vista.

Any suggestions?

--97T--
The reason the room turns dark when you read my posts is because I have a black cloud that follows me around whenever I play with Linux!

[rerwin]

Wireless modem users,
I have updated the mode switcher to better coordinate with driver module loading. The script may initially find the device not quite ready to be recognized, so quits. Normally, it indicates its completion so that the modem initialization scripts can work reliably. A second execution of it then finds everything ready and proceeds with switching - but that may occur after the scripts have determined the modem to use.

Pusbmodeswitch already does not indicate completion if two particular error messages appear. The fix merely adds about 6 more messages that will delay the indication of completion, improving the dependability of wireless modem detection.

The update package is here: http://www.murga-linux.com/puppy/viewtopic.php?p=467639#467639
Richard

[rerwin]

[Sage]

Yes, I've discovered the strange no-sound features on some boards. Sometimes (rarely) it is accompanied by absence of the help panel and, ipso facto, no barks - even when barks is normally working on other chassis. The muted sound is a real nuisance, too. Everything was just fine up to 098 (except barks switched off in 096). Seems to me that all this juggling to suit one odd report destroys a previously sound and stable OS. Like my weird ATI939 board, I'd recommend folks with one non-standard behaving system to change it! Not as if there aren't boxloads of 1GHz boards available gratis just for the asking - (how many do you need? - ask me!). These are entirely suitable for a compact distro. Unfortunately, there have to be compromises and expedients in a 120Mb .iso. For dissatisfied folks with go-faster systems, I'd recommend Linux Mint.
I guess to a lesser extent, the same comments are true with all this Winmodem business. If you've been unlucky and got a Conexant or whatever, bin it, PM me and I'll send you one that works. Otherwise, a lot of clever guys are wasting their intellectual effort trying to run kit that was intended for the rogue OS.

[Karl Godt]

[zigbert]

[ravensrest]

Below is a complete listing of Karl Godt's modified /usr/local/jwmconfig2/gtk2jwm file. His listing above appears to have a couple errors in it, and does not include the auto jwm restart. This one does. I have checked it on my system which has a modified jwmrc-tray and it works fine, but that is the extent of the testing. Save it as gtk2jwm, make it executable and try it.

Thanks, Karl

[DaveS]

Ravenrest... tried the above and it did not bork the tray, but it did not change the theme either

[bigpup]

ATI is not supporting all video cards with the newest drivers.

ATI web site for what they are calling legacy video drivers.
http://support.amd.com/us/gpudownload/linux/Legacy/Pages/radeon_linux.aspx?type=2.4.1&product=2.4.1.3.12&lang=English
Really old stuff here
http://support.amd.com/us/gpudownload/linux/legacy/previous/Pages/radeon_linux.aspx

[CatDude]

Hi

Is this the 'ROX focus bug' or something else ??

What i am about to describe, i can reproduce over and over again (without fail).

Step 1.

Open a ROX window (i clicked on the desktop 'file' icon)

Now Right-click on the desktop to bring up the main Menu,
followed by either a Left-click or Right-click on the desktop to get rid of the Menu.

Step 2.

Next, Right-click inside of the open ROX window (anywhere below the titlebar, yes, even on the toolbar),
and you should get the main Menu appear and not the ROX menu.

Either Left-click or Right-click anywhere (ROX window, Desktop, wherever) to get rid of the menu,
then go and click on one of the Desktop Icons (it does nothing), the next click does though.

NOTE:
If after doing Step 1.
you go and Right-click on the ROX wiindow titlebar, you get the expected menu,
but if you then continue as in Step 2, the behaviour is still as explained in Step 2.

Whatever it is,
it seems like the fix suggested by upnorth (amongst others) does the trick.
Edit: /usr/local/bin/rox
from this:

[ravensrest]

[rjbrewer]

[rerwin]

zekebaby,
To try to fix your problem with unreliable detection of the sound card. I have updated my fix package (to "-4"), that should avoid having ALSA initialization "jump the gun" in checking for sound drivers. Please install it and try your multiple re-boots, to see if it makes detection reliable. The fix is here: http://www.murga-linux.com/puppy/viewtopic.php?p=467639#467639

If you still see the problem, please run pmodemdiag (in a console) soon after completion of the bootup and as soon as you know there is a problem. Then post or PM-me the pmodemdiag...tar.gz file it generates. That would help me understand the nitty-gritty of what is going on. Thanks.
Richard