Page 4 of 100
Posted: Mon 07 Jun 2010, 01:40
by 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:
Code: Select all
cd /usr/src/linux-2.6.33.2
make prepare
in a terminal window. The source is missing some defining files. Thank you, jemimah, for the kernel configuration file for Fluppy and the tips.
Attached, I hope is the resulting pet for fan and temperature control of the Acer Aspire One. It install the kernel module (/lib/modules/2.6.33.2/kernel/drivers/misc/) acerhdf.ko, a configuration file (/etc/modules.d) acerhdf.conf and a readme file for acerhdf in /root for your information. After installing the pet, one has to add the kernel to the start up. One manual edits /etc/rc.d/rc.local file to add this at the file end:
After rebooting, the tray temperature icon will be shown. Placing the mouse point on the icon will provide to you the temperature of the cpu in Celsius degrees. I hope this helps.
Posted: Mon 07 Jun 2010, 15:12
by aarf
fluppy02: as noted already
Posted: Mon 07 Jun 2010, 16:07
by 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...........
Posted: Mon 07 Jun 2010, 17:07
by 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
Posted: Mon 07 Jun 2010, 17:51
by 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.
Posted: Mon 07 Jun 2010, 18:28
by DaveS
ifconfig wlan0 up returns ifconfig:SIOCSFIFFLAGS : no such file or directory. Sleep makes no difference.
Posted: Mon 07 Jun 2010, 18:35
by 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
Posted: Mon 07 Jun 2010, 18:50
by jemimah
DaveS wrote:ifconfig wlan0 up returns ifconfig:SIOCSFIFFLAGS : no such file or directory. Sleep makes no difference.
Yeah that's the rfkill problem. I have a laptop with this issue. It has a button to turn the wireless on and off, and the kernel seems to be detecting the state correctly, but it still doesn't work for some reason - wheras it works in Quirky as long as you don't press the button.
If I can't figure it out, I'll pull rfkill support out of the kernel.
Posted: Mon 07 Jun 2010, 18:53
by jemimah
Roy wrote: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
What about 'iwconfig'? Ifconfig doesn't show a wireless interface unless it's actually up.
Posted: Mon 07 Jun 2010, 19:04
by 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
Posted: Mon 07 Jun 2010, 19:09
by 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?
Posted: Mon 07 Jun 2010, 19:12
by 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
Posted: Mon 07 Jun 2010, 19:43
by 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.
Posted: Mon 07 Jun 2010, 19:53
by jemimah
Roy wrote: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
The installer only works on FAT formatted drives (for ext2/3 use BootFlash to make the drive bootable, then copy the fluppy files to it). The ldlinux.sys in /boot is a left over - that one is not used for booting. If you run the the linux installer it will create a new one in /.
Posted: Mon 07 Jun 2010, 19:56
by jemimah
You can play with rfkill from the terminal if you want.
The commands are
Code: Select all
rfkill list
rfkill block all
rfkill unblock all
Posted: Mon 07 Jun 2010, 19:58
by Roy
Actually, I might have found a different symptom/cause (referring to the boot issue).
I reaccomplished the boot loading in XP and successfully rebooted the FAT32 thumb drive. Shutdown and created a 218Mb ext3 save file on the thumb drive.....
and "Boot error"
So, is it the presence of an ext3 save file on the FAT32 thumb drive that is killing the boot sequence?
-Roy
Posted: Mon 07 Jun 2010, 20:00
by jemimah
Saving works fine for me with ext2, 3, and 4. Only the Usb drive needs a FAT filesystem.
Posted: Mon 07 Jun 2010, 20:04
by Roy
That doesn't match with what I am seeing on my end. My thumbdrive is a FAT32 filesystem (formatted by XP, not Puppy), but as soon as I create the ext3 save file -- I can't reboot.
There has to be something different that we are doing on our respective ends but -- since you are the developer and I am the dumb end-user -- I humbly defer to your wisdom.
-Roy
EDIT: re-running the XP bootloader again after creating the savefile does restore bootability.
Posted: Mon 07 Jun 2010, 20:23
by jemimah
The XP bootloader works perfectly AFAIK - only the Linux version creates the ldlinux.sys file.
Posted: Mon 07 Jun 2010, 20:29
by Roy
Just tried the rfkill commands you provided earlier...
shows eth0 and bluetooth unblocked (both soft and hard); blocking both of those with the block all command does not bring up wlan0.
Will continue playing with this for a while....
-Roy