Statler on the Asus EEE H1005HA-M

It seems that people are starting threads for Statler in various scenarios, so I hope this is correct--otherwise, moderators, please move it to the proper location

Installing from USB (without doing any reseach) I first ran into the known issue of it not being able to find the installation source.  There's a solution on the wiki, but I was already familiar with adding

cdrom-detect/try-usb=true

and used that.  This is a machine that already has Fedora, Arch, and Ubuntu Lucid on it.

The next issue was with the network.  It detected both cards, but was unable to get a DHCP address from the wired card.  I just continued without network. 

Then it was unable to install grub.  It also, to my annoyance, didn't offer any alternative, just went to install grub in the MBR, which I didn't want.  I was actually glad it failed.  However, it wouldn't give me the option to continue without installing grub.  When I tried, it just went back to the menu, highlighting installing grub.  At this point, I tried again, but it failed again.  I then chose finish the installation, but it refused.  So, I chose abort the installation.

My original plan (I use Fedora's grub on the machine) was to not install grub at all, and just point Fedora's grub.conf to the proper vmlinuz and initrd.img files.  So, even though it had aborted, I went ahead with doing that and tried to boot.  It booted successfully, but wouldn't let me log in as root or as the user I'd created.

So, I rebooted again, and noticed that Fedora, Arch, and Ubuntu were no longer able to see the wired network card.  It was as if, in failing to be able to use it, #!Crunchbang had eliminated it.   

This wasn't a big deal--I'd had the same thing happen with Arch--it's one of those oddities--in both cases, the install recognized the card, tried to assign DHCP, couldn't and then, upon reboot, though the card showed in the BIOS, none of the previously installed systems could see it.  I already knew, from experience with the Arch install, that shutting it down, waiting a minute or so, booting, and then, repeating the process if necessary, would bring the card back, so this was more an annoyance than some sort of Oh nooooooooooo thing. 

I booted into Fedora, mounted the #!Crunchbang partition, and did a chroot into it, which worked.  While chrooted, I reset root's password. I had to re-add the user--although there had been no sign of it failing during the install, apparently, when the install aborted, the user didn't get added.

Once this was done, I booted up (by this time, I'd gotten the wired card working again.)  Everything was then as expected.

Curious about this, I then rebooted, this time choosing live. (Without adding the usb=true parameter.)  It booted without issue, and both wired and wireless worked.

Becoming more curious, I reinstalled--this time, when it wanted to configure the network, I wasn't able to tab over to cancel, but let it try with the wireless, which failed--as expected, I didn't put in the wireless network name or password.  Then, I had the option to cancel, which I did.  I ran into the same issue of grub not installing (nor giving me a real option to not install grub--if one chooses continue without grub, it just kept coming back to the main menu).   So, once again, aborted installation, it booted properly when given vmlinuz and intrd.img paths, and again wouldn't allow me to log in. Once again, fixed with booting into Fedora, mounting and using chroot.   This time, the network card showed up in Fedora--I didn't test this with a reinstall of Arch, but it seems that trying to configure the wired ethernet is what causes the problem with other systems upon reboot.

Once password had been set for root and the user added (both through the chroot), and the lines for it added to Fedora's grub, it booted without problem.  Both wired and wireless ethernet also worked without an issue.

As I don't really consider #!Crunchbang aimed at the Windows refugee type of user, (as, generally speaking, openbox is preferred by more experienced users), I wouldn't call any of these showstoppers for someone with experience.  Seems, once installed, to be very very nice, and congratulations on yet another nice version. 

Needs more packages of course, but I know you're working on that. 

Thank you.