Puppy Linux Discussion Forum

[rerwin]

EDIT 5/3: Drivers agrserial and agrmodem are in /lib/modules/2.6.25/extra, but not in 4.00-k2.6.21.7.
Richard

[mbe]

Boot from frugal install was fine but I still I needed to modprobe yenta_socket to get the USB2 and wireless interfaces on PCMCIA cards to appear. WPA/TKIP configured perfectly using the wireless wizard with ndiswrapper. I added modprobe yenta_socket to /etc/rc.d/rc.local as a workaround. - Shutdown offered a save file and the interface appeared nicely on a reboot - would it be possible to add the modprobe yent_socket line to one of the startup scripts in initrd for 4.0 final ?

[rerwin]

mbe,
I think the solution is to add an override entry for your cardbus controller into /etc/rc.d/MODULESCONFIG. Insert the following line after line 21, just before the line consisting of a single tick-mark:

[mbe]

Richard

Excellent result - I removed my extra line from /etc/rc.d/rc.local and added your line into /etc/rc.d/MODULESCONFIG then rebooted - the cards came up straight away and the wizard auto-connected via nidiswapper with WPA/TKIP since it was already configured from before.

This is clearly a better fix for me but does it need to be so hardware specific ?

Thanks a lot

Martin

[rerwin]

Martin,
Thanks for trying out the fix. Yes, it does need to be specific to the piece of hardware.

I checked further for the possibility that "0xffffffff" as a device ID might mean "any". I found only a handful of examples in the modules.pcimap file. For O2 Micro, all devices are CardBus controllers; but they might not all use the same driver (yenta-socket). The other examples had a mix of device types for the vendor, so they could not possibly all use the same driver.

I conclude that the f's simply mean a lack of information. So until the pcimap gets generated with individual device IDs for O2 Micro, we need to use the line I provided.

Barry, please consider the above MODULESCONFIG line as a submission for inclusion into Puppy at the next opportunity. Thanks, Martin, for your persistence and assistance.
Richard

[Lobster]

2.6.25 kernel (md5sum check out OK) I got as far as the keyboard locking on the select country - other time it got as far as the desktop and the mouse was frozen.
Not working for me using an Athlon 2000 with 512MB ram

26.1.7 is working OK

[GeorgR]

On MB with chipset AMD 690G and ATI SB600 I got see the same result like Lobster with 25 kernel: no Keyboard reaction at country selection.
But it is still a progress in comparison to the other puppy version, because they only boot with acpi=noirq booting parameter.

On older MB with Intel 865PERLK I had more luck with 25 Kernel - otherwise I would not be able to write this message

[Sage]

Works for me with A2200, A3000 & P IV-2.2

[Kal]

Using the newer kernel 2.6.25 required a "modprobe ohci-hcd" to be placed in /etc/rc.d/rc.local for USB mouse to work.

Good Luck, Kal

[geneven]

I had two problems with the (625?) kernel.

One, the correct module for my BCM43xx wireless didn't load and didn't appear to be available. So my usual tricks for getting on the internet didn't work. This does NOT happen with the other Puppy posted today. (621?)

Two, there is something strange about the combo method for installing on my 2 gig USB stick. This happens with BOTH Puppies posted today.

When I first boot into one of the new Puppies, I have about 500 megs of free space, which is usual. But after I reboot and select the default location for creating a personal storage file, I have about 30 megs. I started with 2 gigs, so it' seems that the wrong partition is being selected for the personal storage file?

Incidentally, another thing is that I don't get any appropriate error messages. When I go to create, say, a 512 meg storage file after being told that I have about 30 megs free, the system lets me ask for 512 megs that don't exist. Then, when I reboot, I don't get an error message even though the 512 meg file can't be created. Seems to me that I should.

[capoverde]

Running Puppy 4 Dingo k2.6.21.7:

surprise, a plugged SD card isn't detected, no matter what way (HotPup, PMount or MUT); no use restarting X or inserting the card before power-up.

?!? - Previous Puppies, including Dingo Alphas &Betas, had no problems at that -- MD5sum checked OK. Will try on other machines, with an external card reader.

[BarryK]

[BarryK]

[twointo1]

In my laptop with a broadcom 4306 network card (eth1 in 2.6.21.7 and wlan0 in 2.6.25, I get 15 networks around me with 2.6.21.7 and 5 with 2.6.25. The same thing happens with my desktop that has a Zydas zd1211rw chip.

Why the difference in eth1 and wlan0 along with the wireless network lack of sensitivity?

Thanks

[BarryK]