Puppy Linux Discussion Forum

[JustGreg]

I had success with making the kernel module acerhdf for Linux 2.6.33.2. If you are working with the kernel source for 2.6.33.2, one has to:

[aarf]

fluppy02: as noted already

[DaveS]

Following your invitation on another thread Jemimah, I tried this on my lappy. It set up the USB exactly as it should and booted just fine. Ran very cool, 48 deg, but was unable to get my B43 wifi to connect...........

[Roy]

Testing on a Dell Mini-9 (Inspiron 910):

Formated USB drive as ext3 file system and copied extracted Fluppy files onto USB; clicked on boot.sh and followed prompts; rebooted to thumb drive... 'cannot find linux' or something to that effect.

Took everything to a Windows computer to try again. Used Windows to reformat thumb drive to FAT32 and again copied extracted Fluppy files to USB; selected the .bin file for bootability and (after following prompts) returned thumb drive to Mini-9. Successfully booted to thumb drive while netbook's SDHC was still installed in slot (Puppy 4.2x-based versions will not do this due to kernel compilation).

Nice selection of apps! Intel video looks good and is the correct resolution.

Selected 'connect' icon from ROX desktop pinboard and was pleased to see Pwireless2 as an option, among the other traditional options, so I selected Pwireless2. Unfortunately, Pwireless does not see any of the many connection points available at this location and is now set as a hard default – with no obvious way to select the other connection wizards. 'Connect', 'setup', 'Wizard Wizard'... all return only the failed Pwireless2. The traditional options for connectivity are not presented a second time.

[This netbook uses the Broadcom 4312 (wl.ko) wireless, BTW. Jrb rolled a Special version of Puppy 4.31 for this driver and Barry's Quirky 1.0 had some success using the newest Broadcom b43 driver for connectivity (although I note that rcrsn51 went to Ndiswrapper for stability in the Quirky 1.2 bug thread). Tempestuous had created .pets for the wl.ko driver in Puppy 4.2x, but again, there is something developers have noted about where the modules are located in the kernel which supposedly prevents a .pet from working in Puppy 4.3x – although I have used a .pet that places the wl.ko driver – successfully – in Boxpup 4.31.] Ramble-mode “off”.

Robooted without saving and... only Pwireless is available. Is this a driver issue or an app issue?

-Roy

rcrsn51's ndiswrapper fix: http://www.murga-linux.com/puppy/viewtopic.php?p=424130#424130 is NDISWRAPPER included in Fluppy?

[jemimah]

I was under the impression that the wl driver was fixed in 2.6.33. Are special drivers needed for Quirky?

One thing that's different in Fluppy is that I turned on rfkill support in the kernel. This enables me to have an "airplane mode", but there are some problems with rfkill in some drivers so I may need to turn that off like Barry does. You can see if that is the problem by typing 'ifconfig wlan0 up' in the terminal (replace wlan0 with the name of your wireless interface. If that fails, it is probably an rfkill bug.

There's one more thing that is an issue with networking in Fluppy02. On some machines Pwireless2 tries to start before the network modules are loaded, so it fails. You fix this by editing /etc/rc.d/rc.services and increasing the sleep time by a few seconds. That fix will be in Fluppy03 but you can try it now if your networking is not working.

At the moment, Pwireless2 is the only networking tool in Fluppy. I think I will try to port SNS but I have no intention of including the network wizard.

[DaveS]

ifconfig wlan0 up returns ifconfig:SIOCSFIFFLAGS : no such file or directory. Sleep makes no difference.

[Roy]

jemimah,

'ifconfig' only shows eth0 and lo... no wireless interface mentioned. Is there another command I can issue to see if my wireless card is even being detected?

System information shows that you have the b43 (I assume, ala Quirky) compiled into Fluppy already, so theoretically [emphasis on theoretically] it should connect.....

-Roy

[jemimah]

[jemimah]

[Roy]

Uh, I just loaded rcrsn51's ndiswrapper fix onto my thumbdrive (using Mint on another computer) and now it only gives "Boot error" .... so looks like I have to reload. Don't know what an extra file on the thumb drive has to do with booting what's already there, but apparently something's amiss on my end.

-Roy

[jemimah]

Can you check one thing for me?

When you use the Linux installer, it creates a file called ldlinux.sys on the usb drive. I think what's happening is that is file is getting deleted somehow. Can you check if the file is there?

[Roy]

standby....

ldlinux.sys (using Mint to view contents) is located in the 'boot/syslinux' directory with a padlock on it...

I backed out of the 'syslinux' directory (into the 'boot' directory) and ran 'bootinst.sh'...

ldsyslinux is still there in the boot/syslinux directory.

The root directory contains the following:

/boot directory
/documents directory (added by me for file transfers)
flp-002.sfs
initrd.gz
syslinux.cfg
vmlinuz
zf002332.sfs

the /boot directory contains the following:

/dos directory
/syslinux directory
bootinst.bat
bootinst.sh
chain.c32
fluppy.png
mt86p
vesamenu.c32

/syslinux directory contains:

ldlinux.sys
lilo
linuxinstall.sh
mbr.bin
syslinux
syslinux.com
syslinux.exe

NOTE: My original problem with the ext3 file system said something about not finding 'linux'. Perhaps linuxinstall.sh was not run or was defective?

-Roy

[Roy]

It looks like my only success is after re-initiating the boot sequence from Windows XP.

-Roy

EDIT: For the RFKill issue, my netbook is supposed to use a Fn 2 keyboard combination to enable/disable the wireless, but these are not programmed with Fluppy. I do not have a user-accessible wireless on/off switch.

[jemimah]

[jemimah]

You can play with rfkill from the terminal if you want.

The commands are