Puppeee 4.3X
I have the atheros wireless card and I used the ath5k driver.
This is the first time for me using puppy so I'm new to it.
I do use ndiswrapper on ubuntu right now with no issues so I may try ndiswrapper.
what speeds do the overclocking set the proc, I have the 900 Mhz Celeron processor so I don't if that makes a difference but deleting those files allows it to work, I still get the warning do not unplug the usb drive but it doesn't crash.
I like the feel of puppy though a lot quicker than ubuntu.
This is the first time for me using puppy so I'm new to it.
I do use ndiswrapper on ubuntu right now with no issues so I may try ndiswrapper.
what speeds do the overclocking set the proc, I have the 900 Mhz Celeron processor so I don't if that makes a difference but deleting those files allows it to work, I still get the warning do not unplug the usb drive but it doesn't crash.
I like the feel of puppy though a lot quicker than ubuntu.
Well the madwifi site seems to be offline. Anybody know if it's gone for good?
I think overclocking the celeron only works on models that run at 630Mz. It bumps them up to 900Mz.
The usb warning is part of puppy, you'll always get it when you boot from usb. Although, I do think it's ok to unmount it from the command line and remove it if you don't have a save file.
Yeah that's why I came over to puppy. Got sick and tired of waiting for ubuntu to boot.
I think overclocking the celeron only works on models that run at 630Mz. It bumps them up to 900Mz.
The usb warning is part of puppy, you'll always get it when you boot from usb. Although, I do think it's ok to unmount it from the command line and remove it if you don't have a save file.
Yeah that's why I came over to puppy. Got sick and tired of waiting for ubuntu to boot.
I was able to connect to my network with wpa_gui, it's working great. Posting from puppeee right now.
I thought the warning was part of my crash because it would crash right after that warning but it looks like power management was the cause.
Is it normal for it to fail when reading the swap partition at boot, not to big of a deal but just wondering if you know.
I thought the warning was part of my crash because it would crash right after that warning but it looks like power management was the cause.
Is it normal for it to fail when reading the swap partition at boot, not to big of a deal but just wondering if you know.
The madwifi I got from sourceforge really doesn't want to compile on 2.6.30.5. I wonder how Tempestuous got it to work.
----
Ok, I managed to track down the version of madwifi Tempestuous posted and built it for this kernel. Tested it on my 701 and it appears to work. Wpa_gui doesn't like it at all so you'll have to use network wizard. I will include it in the new version I post tonight. If you want to use the madwifi driver, you need to blacklist ath5k and whitelist ath-pci so the correct modules will load.
----
Ok, I managed to track down the version of madwifi Tempestuous posted and built it for this kernel. Tested it on my 701 and it appears to work. Wpa_gui doesn't like it at all so you'll have to use network wizard. I will include it in the new version I post tonight. If you want to use the madwifi driver, you need to blacklist ath5k and whitelist ath-pci so the correct modules will load.
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
swap
If your kernels don't handle swap, that would explain why loading the linux driver modules is the last thing that works before a boot fails. I've replicated my problem on several SD cards, and checked that I can boot and run unmodified 4.3.1 on the same SD card. The disk driver must hang when the init scripts try to use swap.jemimah wrote:I'm not sure on the swap space. I have no need for swap on puppy, and have never tried creating a swap space. Hmmm it's possible I disabled swap support in this kernel... I suppose I should turn that back on.
i think it should whitelist ath_pci not ath-pcijemimah wrote:The madwifi I got from sourceforge really doesn't want to compile on 2.6.30.5. I wonder how Tempestuous got it to work.
----
Ok, I managed to track down the version of madwifi Tempestuous posted and built it for this kernel. Tested it on my 701 and it appears to work. Wpa_gui doesn't like it at all so you'll have to use network wizard. I will include it in the new version I post tonight. If you want to use the madwifi driver, you need to blacklist ath5k and whitelist ath-pci so the correct modules will load.
The eee module crashes the kernel on certain models with certain bioses (including my 1005ha) so I'm using a newer module called asus_eee (ubuntu uses this as well) that does the same thing but with more error checking. Eee-control should work. Though you may want to check my post here:
http://www.murga-linux.com/puppy/viewto ... &start=120 which may explain some of your overheating issue.
http://www.murga-linux.com/puppy/viewto ... &start=120 which may explain some of your overheating issue.
Thank you for such fast support. The asus_eee works perfectly for fan control and conky monitoring. I'm set, made the transition completely to your kernel/4.31.sfs.
It can be done with a pre-existing 4.31 puppy save file--mostly entails icon-work, jwm menu reconstruction, and other dressing. But all bluetooth pets work, and the speed of the kernel is just great.
Wifi return remains buggy, but since I have tempestuous' pets already installed, I click on his wlan.sh and I can bring it back.
Thank you again for your hard work and fine support.
Jake
It can be done with a pre-existing 4.31 puppy save file--mostly entails icon-work, jwm menu reconstruction, and other dressing. But all bluetooth pets work, and the speed of the kernel is just great.
Wifi return remains buggy, but since I have tempestuous' pets already installed, I click on his wlan.sh and I can bring it back.
Thank you again for your hard work and fine support.
Jake
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
boot problem still with me
Swap was not the answer. But, I still suspect there is something to do with the type of file system. The full 431 kernel boots without problems, even on the SD card which gave me trouble when your kernel and initrd.gz were used.jemimah wrote:The new version is up. I updated the url in the first post. Fixes include addition of madwifi modules, fixes to networking script, removal of automatic celeron overclocking, and swap support added to the kernel.
My 900A is the Linux version with the Xandros system. This has four partitions on the 16 GB SSD: sda1 ext2, sda2 ext3, sda3 labeled BIOS with type unknown, and sda4 with no label and type unknown. The SD cards I'm using have either FAT16 or FAT32 file systems, (so they can hold files put there by an OS we won't mention. )
If I am wrong about the problem being tied to the type of file system, we may have a case of different machines with the same model number having different parts. (Other people have reported this turning up on the EEE PC.) Whatever the cause, it takes place immediately after the linux kernel modules to access disk drives are loaded. The two files, vmlinuz and initrd.gz, are read, using the BIOS, before these modules are available.
If I am not bothered by the speed of the full kernel, what do I need to support the sfs for your puplet?
Prehistoric, boot regular puppy, then send me a copy of your dmesg and lsmod output. Then I'll be able to tell if you have hardware that's not supported.
Is it still failing to find the sfs? Have you tried a regular usb stick as opposed to SD card? Maybe the card reader needs a kernel module I didn't add...
Puppeee has the normal 4.31 sfs plus only a few utilities that you can get as pets, so there's no compelling reason to use it if the kernel doesn't work for you.
Is it still failing to find the sfs? Have you tried a regular usb stick as opposed to SD card? Maybe the card reader needs a kernel module I didn't add...
Puppeee has the normal 4.31 sfs plus only a few utilities that you can get as pets, so there's no compelling reason to use it if the kernel doesn't work for you.