While I don't have my new hardware yet, I thought I would give the update a try.I did the apt-get update and the apt-get upgrade, reboot, deleted the image for the eee-box and started the box....and got exactly the same resultJust to make sure, I did the fresh install from scratch...but nothing changed. I still get the infamous kernel-panic.I'm still open for suggestionsIn case this is of any interest, here is what lspci says on my core, which is otherwise running 7.10:

Guys, what can I say....break out the champange bottles.but I must also apologize for the confusion I caused. Yesterday I had all my new components together and did a total makeover on my server. Since I also had some strange connectivity issues with my n810 and my accesspoint, I decided to deactivate everything and start from scratch there too.Much to my amazement the eee-box worked nicely, until I switched on my AP. I didn't take long to realize what was up. The eee-box and the AP wanted to use the same IP-address. I didn't have this kind of issue under 7.10, otherwise I would have found out much earlier. I must add, that the ability to see the dhcp-leases in the admin-website helped a lot with this issue. However, I think it would help even more, if we were able to enter static IP's into the dhcp-server, so that problems like that don't occur again. I can imagine several scenarios, where I would need to assign a static IP's, an access-point is only one of them.

The only other issue I have is, that once in a while when booting the eee-box it doesn't start the orbiter, but crashes back to the tty1.

The only other issue I have is, that once in a while when booting the eee-box it doesn't start the orbiter, but crashes back to the tty1.

Did you ever overcome this maverick? I have the exact issue with my eee box running snapshot 23359. eee box is entirely plug and play until it gets to 'Starting Device XX Onscreen Orbiter' where it crashes back to tty1 which reads "moonXX login:"