mailman1175
December 27th, 2009, 06:57 PM
First, a little more information:
I have successfully installed Karmic UNR on my Acer Aspire One 110L (ZG5, with the Intel SSD). The /home partition is on an 8GB SD card. I've been looking for a lightweight distro to dual-boot with, something fully functional, but with a small footprint, something I can use as a rescue distro if need be. With that in mind, I had a 2GB partition set aside on the SSD.
I settled on Cruchbang (#!) Lite, largely because I'm now more familiar with Ubuntu variants than with any other Linux distros or their forks. Additionally, Ubuntu's community is far more active and supportive than any other I've encountered.
Anyway, on to the problems:
The latest #! release is based on Jaunty. I wanted to point #! at the same /home partition, and use the same 1GB swap. The installer handled that part well enough, though I wasn't expecting it to append all new home sub-directories to the /home partition. Localization was set to the UK by default, with no option to change that in the installer. Weird, but nothing I couldn't change once it was installed.
Of note here is that I opted NOT to install a bootloader in the #! install, because I was afraid it would have overwritten my Karmic GRUB2 install, and I wanted to let GRUB2 find the #! install with update-grub. This may or may not have anything to do with my problems.
The #! Aspire One wiki page suggests installing the Kuki/sickboy custom kernel for best hardware support (wifi, proper sound, SD cards, fan behavior, etc). I've heard enough about this kernel in AspireOne user circles, I finally decided to give it a shot, understanding the limitations of support for a custom kernel.
That's where I started to run into problems, but it seems to me that my problems weren't specific to the Kuki kernel, since I couldn't apt-get upgrade to new supported kernels/headers, either. This thread (http://www.aspireoneuser.com/forum/viewtopic.php?f=28&t=9608&hilit=kuki+kernel+install#p62018) (on the AspireOneUser forums) has a pretty good run-down of the errors I get when I try to upgrade any of the kernel modules. apt-get upgrade does it; synaptic; .deb installers for the Kuki kernel — they all return the same errors.
It's not as if the kernel install completely fails, though. I boot back into Karmic, update-grub, reboot again, and the grub screen shows different boot options for each of the kernel modules I attempted to install under #!. The machine will boot into each of those kernels just fine. uname -r returns the expected kernel module in each case. But I see those same errors every time I do a package upgrade, and I can't compile madwifi drivers for the machine without kernel headers.
I kind of figure the root of my problem has something to do with GRUB. I just don't know what to do about it. Do I go ahead and let #! create a menu.lst like it wants to? Do I install GRUB2 on the #! partition? Is there something else going on I've missed?
I know just enough to be dangerous, folks. Y'all are lots of help, and I appreciate it. Let me know if you need to see some more detailed info… I'd sure like to figure this out. FWIW, I've posted similar requests for assistance on the AspireOne user forum and the Crunchbang forums, as well as trying Kuki's forums and their IRC channel.
TIA
I have successfully installed Karmic UNR on my Acer Aspire One 110L (ZG5, with the Intel SSD). The /home partition is on an 8GB SD card. I've been looking for a lightweight distro to dual-boot with, something fully functional, but with a small footprint, something I can use as a rescue distro if need be. With that in mind, I had a 2GB partition set aside on the SSD.
I settled on Cruchbang (#!) Lite, largely because I'm now more familiar with Ubuntu variants than with any other Linux distros or their forks. Additionally, Ubuntu's community is far more active and supportive than any other I've encountered.
Anyway, on to the problems:
The latest #! release is based on Jaunty. I wanted to point #! at the same /home partition, and use the same 1GB swap. The installer handled that part well enough, though I wasn't expecting it to append all new home sub-directories to the /home partition. Localization was set to the UK by default, with no option to change that in the installer. Weird, but nothing I couldn't change once it was installed.
Of note here is that I opted NOT to install a bootloader in the #! install, because I was afraid it would have overwritten my Karmic GRUB2 install, and I wanted to let GRUB2 find the #! install with update-grub. This may or may not have anything to do with my problems.
The #! Aspire One wiki page suggests installing the Kuki/sickboy custom kernel for best hardware support (wifi, proper sound, SD cards, fan behavior, etc). I've heard enough about this kernel in AspireOne user circles, I finally decided to give it a shot, understanding the limitations of support for a custom kernel.
That's where I started to run into problems, but it seems to me that my problems weren't specific to the Kuki kernel, since I couldn't apt-get upgrade to new supported kernels/headers, either. This thread (http://www.aspireoneuser.com/forum/viewtopic.php?f=28&t=9608&hilit=kuki+kernel+install#p62018) (on the AspireOneUser forums) has a pretty good run-down of the errors I get when I try to upgrade any of the kernel modules. apt-get upgrade does it; synaptic; .deb installers for the Kuki kernel — they all return the same errors.
It's not as if the kernel install completely fails, though. I boot back into Karmic, update-grub, reboot again, and the grub screen shows different boot options for each of the kernel modules I attempted to install under #!. The machine will boot into each of those kernels just fine. uname -r returns the expected kernel module in each case. But I see those same errors every time I do a package upgrade, and I can't compile madwifi drivers for the machine without kernel headers.
I kind of figure the root of my problem has something to do with GRUB. I just don't know what to do about it. Do I go ahead and let #! create a menu.lst like it wants to? Do I install GRUB2 on the #! partition? Is there something else going on I've missed?
I know just enough to be dangerous, folks. Y'all are lots of help, and I appreciate it. Let me know if you need to see some more detailed info… I'd sure like to figure this out. FWIW, I've posted similar requests for assistance on the AspireOne user forum and the Crunchbang forums, as well as trying Kuki's forums and their IRC channel.
TIA