(old)Puppy Linux Discussion Forum

01micko wrote:Netgear dongles are notorious for poor Linux support. It took many years for the kernel developers to get it right for the netgear-wg111-v2, which they eventually did. The symptoms were similar to what you say and the solution for stable connection was to reduce the rate of the thing from full speed to a fraction. I'm not sure what would be optimal for a, IEEE-802.11n dongle though as they ramped up the speed significantly. To change the rate:

Code: Select all

iwconfig wlan0 rate 11M fixed

..and if it works

Code: Select all

echo "iwconfig wlan0 rate 11M fixed" >> /etc/rc.d/rc.local

..and reboot, that will make it permanent.

IIRC, the last time I tried that it didn't make a difference, but I'll have another look. Hopefully I don't have to throttle the machine's network speed to barely faster than my Acorn A7000+ manages!

01micko wrote:Also, post your dmesg output, it may be firmware or similar.

I'll post dmesg in the next few days. Having sorted out a temporary replacement hard drive, I had a go on an old Slacko 5.3.3 save and noticed there was a carl9170 pet installed on it, but I can't remember why - there isn't one on any of my other Slacko 5.3.3 saves and the WN111v2 works perfectly on that.

Searching the forum, I seem to have reported a similar problem on the old Slacko 5.3.3.2 thread, in that case the dongle wasn't seen at all until I installed a pet you provided, which then had the same problems I'm seeing now. I wonder if that save with the pet on had been upgraded to 5.3.3.2 - I really should've kept notes.

As you say, it's probably kernel or firmware, Lupu tended to use an older kernel version than the versions of Slacko that I've used. In the meantime Slacko 5.3.3 will probably remain the main Puppy version on the Pentium D for the time being.

Thanks Jades for the report.

I located our conversation, does the pet from this post make any difference? The firmware is there but where woof wants to put it, I can override that and put it where the pet puts it. It may be found faster.

Hmm.. it's actually a different blob.

The one in this iso: The one in the pet: I don't know the origin of either! Except I found the one in the pet.

In a spare moment yesterday, I also gave the Cohiba/Netgear dongle another outing with rather strange results. I used the SNS and regular connection utilities as I've found this device unresponsive to Frisbee. There is no doubt about the prism054g module being in the kernel and detected - this always happens. Sometimes the dongle lights up, sometimes not. Yesterday being a day of multiple distractions, I didn't complete the connection utility with 'Quit' before answering the phone. When I returned, the connection l.e.d. had lit up. It had successfully scanned, found my station, used the SSSID and adopted my key. Everything was go. Except, it didn't! All the signs are that it's slow to scan, slow to sign on and only after everything appears to be working, it fails to collect, whilst appearing to be connected. Did you look at PCLOS yet, mick? The dongle behaves entirely normally with that distro; the utility Tex provides is absolutely excellent, too, but no idea whether its portable, oversized or in other ways incompatible? PCLOS used to be a Mandarke derivative, ie rpm/Fedora, but the extent of its automony and coding consequences are utterly LOSt on me - over to you.

1 iso is uploaded and there are 2 more to go (plus support files, devx, src etc). It will be a few hours before it's all there but when it is I'll be stacking zzz's. I'll formalise the announcement in a bout 7 or 8 hours.

... iso is uploaded and there are 2 more...

Nice one, mick, and thanks. Apart from the inappropriate connotation one might wish you have some peaceful rest! Sleep well.

Running from live dvd on imac with savefile.

Report Video 1.4 - Tue 16 Oct 2012 on Slacko Puppy 5.3.6.5 - Linux 3.2.31-4g i686

Chip description:
0.0 VGA compatible controller: ATI Technologies Inc Radeon HD 2400 XT
oem: ATI ATOMBIOS
product: M74 01.00

X Server: Xorg Driver used: fglrx

X.Org version: 1.12.3
dimensions: 1680x1050 pixels (444x277 millimeters)
depth of root window: 24 planes

OpenGL
Vendor Advanced Micro Devices, Inc.
Renderer ATI Mobility Radeon HD 2400 XT
Version 3.3.11653 Compatibility Profile Context
Direct Rendering Yes

# glxgears
24014 frames in 5.0 seconds = 4802.796 FPS
24428 frames in 5.0 seconds = 4885.576 FPS
24452 frames in 5.0 seconds = 4890.249 FPS

Computer
Processor 2x Intel(R) Core(TM)2 Duo CPU E8135 @ 2.40GHz
Memory 3095MB (195MB used)

BRCM2046 Hub
Bluetooth USB Host Controller
Sound Blaster X-Fi Go! Pro
EHCI Host Controller
USB2.0 Hub
USB Receiver
Keyboard Hub
Apple Keyboard
DRX-820U
Built-in iSight

It's working well so far.

beta2 is announced.

See main post

Not really an issue with Beta 2 as such, but Java has been updated to version 7 update 9...so java.com complains about the update 7.

I do not believe this is an issue with Beta 2, but opera does not play sounds at shoutcast.com, FireFox 15.xxx does.

Some sfs files are NOT recognized withing the boot manager, but if they are loaded into memory, then they do show up in the boot manager.

Running from live dvd with savefile.
Report Video 1.4 - Tue 16 Oct 2012 on Slacko Puppy 5.3.6.5 - Linux 3.4.14-PAE i686

Chip description:
0.0 VGA compatible controller: nVidia Corporation Device 1082 (rev a1)
oem: NVIDIA
product: GF110 Board - 12630002 Chip Rev

X Server: Xorg Driver used: nouveau

X.Org version: 1.12.3
dimensions: 1920x1080 pixels (507x285 millimeters)
depth of root window: 24 planes

OpenGL
Vendor nouveau
Renderer Gallium 0.4 on NVC8
Version 2.1 Mesa 8.0.4
Direct Rendering Yes
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
5485 frames in 5.0 seconds = 1096.924 FPS
5500 frames in 5.0 seconds = 1099.824 FPS
5509 frames in 5.0 seconds = 1101.692 FPS

Computer
Processor 8x Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Memory 16473MB (322MB used)

I've just begun using this version, I've found a bug where I made a
pet of audacious and I used the default audacious.desktop only
removing the %U but the menu entry showed up in the wrong section of
the menu.

Billtoo

If you make a pet, then it's your responsibility to get the .desktop file correct. This is true of any distro. The code in PPM only runs if a package is installed through PPM.

-

tlchost wrote:Some sfs files are NOT recognized withing the boot manager

. Bootmanager has certain filters in place. Which sfs don't show? Do they show in sfs_load? I'm not going to touch the bootmanager code as it's a bit sensitive, maybe this issue will show up in Precise and Barry can have a look at it.

As for java, when it gets close to release I'll make a pet and sfs of the latest version at the time. I was looking at making an app to do it automatically, I may revisit that.

01micko wrote:Billtoo

If you make a pet, then it's your responsibility to get the .desktop file correct. This is true of any distro. The code in PPM only runs if a package is installed through PPM.

Okay, I found a couple of other small bugs:
I downloaded kdegames and the libdbusqtmenu was shown as missing, I re-installed it and kdegames runs okay.
When I opened the terminal afterwards the two lines were there and I needed to edited the profile.d file to get rid of them.

I'm making another pet a the moment, will use a new desktop file instead of the default

Billtoo wrote:Okay, I found a couple of other small bugs:
I downloaded kdegames and the libdbusqtmenu was shown as missing, I re-installed it and kdegames runs okay.
When I opened the terminal afterwards the two lines were there and I needed to edited the profile.d file to get rid of them.

Curious about the .csh files, I put code in to get rid of them, oh well, I'll try again.

The only way this is likely to get fixed is if it happens in precise (re missing dep). That code is a bit of a nightmare.

full install to ext4 partition on sda2 using non PAE version

ran depmod and rebooted

Sound ok - Auto connected to internet

Removed Opera
Installed Seamonkey 2.13-1

Added several pets and everything working - no problems to report

Slacko 5.3.6.5 FF live pfix=ram. A new experience from Slacko......... booted to a black screen with the dreaded"monitor out of range" message.Used Xorgwizard and was able to get the correct 1366x768 resolution. Internet wasn't automatically connected as is usual.....used SNS to connect. Sound did work out of the box though.

# report-video
Report Video 1.4 - Tue 16 Oct 2012 on Slacko Puppy 5.3.6.5 - Linux 3.2.31-4g i686

Chip description:
d.0 VGA compatible controller: nVidia Corporation C61 [GeForce 7025 / nForce 630a] (rev a2)
oem: NVIDIA
product: MCP61 - mcp61-86 Chip Rev

X Server: Xorg Driver used: nv

X.Org version: 1.12.3
dimensions: 1368x768 pixels (414x232 millimeters)
depth of root window: 24 planes

...the above also recorded in /tmp/root/ as report-video,
and archived with xorg.conf and Xorg.0.log as report-video-full.gz
#
# glxgears
2545 frames in 5.0 seconds = 508.784 FPS
2818 frames in 5.0 seconds = 563.539 FPS
2922 frames in 5.0 seconds = 584.016 FPS
3065 frames in 5.0 seconds = 612.873 FPS
3053 frames in 5.0 seconds = 610.597 FPS

-Computer-
Processor : 4x AMD Athlon(tm) II X4 620 Processor
Memory : 2853MB (201MB used)
Operating System : Unknown distribution
User Name : root (root)
Date/Time : Tue 16 Oct 2012 10:16:28 PM CDT
-Display-
Resolution : 1368x768 pixels
OpenGL Renderer : Gallium 0.4 on llvmpipe (LLVM 0x300)
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : HDA-Intel - HDA NVidia

Booted pfix=nox,ram in an attempt to use the preferred "nouveau" driver as is usual in Slacko......total fail.X wouldn't start.Reverted to "nv" to post this.

01micko wrote:

tlchost wrote:Some sfs files are NOT recognized withing the boot manager

. Bootmanager has certain filters in place. Which sfs don't show? Do they show in sfs_load? I'm not going to touch the bootmanager code as it's a bit sensitive, maybe this issue will show up in Precise and Barry can have a look at it.

I made the sfs file in slacko 533 using dir2sfs....worked fine there. It showed in sfs load, and once it was there, it also showed in the boot manager.

As for java, when it gets close to release I'll make a pet and sfs of the latest version at the time. I was looking at making an app to do it automatically, I may revisit that.

Great.....hopefully the autoapp will work when Slacko lives on a bootable usb formatted in fat32.

thanks

Thom

Slacko 5.3.6.5 (Opera version) live pfix=ram.Booted straight to the correct 1366x768 resolution using "nouveau" as expected with working sound. Used SNS to connect to the internet.

# report-video
Report Video 1.4 - Tue 16 Oct 2012 on Slacko Puppy 5.3.6.5 - Linux 3.2.31-4g i686

Chip description:
d.0 VGA compatible controller: nVidia Corporation C61 [GeForce 7025 / nForce 630a] (rev a2)
oem: NVIDIA
product: MCP61 - mcp61-86 Chip Rev

X Server: Xorg Driver used: nouveau

X.Org version: 1.12.3
dimensions: 1366x768 pixels (361x203 millimeters)
depth of root window: 24 planes

...the above also recorded in /tmp/root/ as report-video,
and archived with xorg.conf and Xorg.0.log as report-video-full.gz
# glxgears
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 55
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 56
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 59
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 58
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
5237 frames in 5.0 seconds = 1047.120 FPS
5505 frames in 5.0 seconds = 1100.806 FPS
5897 frames in 5.0 seconds = 1179.105 FPS
5878 frames in 5.0 seconds = 1175.352 FPS
5918 frames in 5.0 seconds = 1183.373 FPS
5905 frames in 5.0 seconds = 1180.937 FPS
6050 frames in 5.0 seconds = 1209.905 FPS
6010 frames in 5.0 seconds = 1201.710 FP

This version is working well, 5360 does too for that matter.
I found some themes for tint2 on the interweb

Well done, mick! Tested the regular & FF whilst you were sleeping. Both represent substantial improvements, fast smooth and stable. No issues to report across a slew of SktA, 478, 775, 754 and 939 machines with 256Mb or >. Shame that the SP seems to have increased from a comfortable 192Mb, recently, but I'll be twiddling some more buttons with Slacko in the coming weeks to see what the art of the possible might be.
There might be more interest welling up for a revival of your miniSlack? BK has also mentioned a possible cut-down Pup. Certainly, I've always advocated a sub-100Mb .iso, although a sub-50 target seems to have vanished in the wind. John's MeanPup remains in my armoury.
Just the Netgear/Cohiba/Wiston/Prism dongle issue remains, not unique to Slacko or even Puppy. Weirdest device I've ever seen, but would be useful if a guru could crack this problem before I crack its case with a lump hammer. Or worse, decamp to PCLOS! Despite scathing attacks on the Web, there do exist distros that successfully activate it.

I've created the delta file needed to install the Broadcom wl wifi driver onto Slacko 5.3.6.5 with Kernel 3.2.31-4g - it's available from:

http://murga-linux.com/puppy/viewtopic. ... 553#648553

[edit] deleted - see later post [/edit]

I've tested 5.3.6.5-4g-FF with b43, wl, frisbee, firefox and pnethood and all seems as expected.

I'm having problems keeping up with the flood of multiple versions!! So haven't downloaded the PAE version yet.

Cheers
peebee