[SOLVED- at last]eee-box 202 and lmce 8.10

[maverick0815]

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 result
Just 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 suggestions
In case this is of any interest, here is what lspci says on my core, which is otherwise running 7.10:

00:00.0 Host bridge: VIA Technologies, Inc. VT8385 [K8T800 AGP] Host Bridge (rev 01)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
00:05.0 RAID bus controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02)
00:06.0 RAID bus controller: American Megatrends Inc. MegaRAID (rev 02)
00:08.0 Multimedia video controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder (rev 05)
00:08.1 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05)
00:08.2 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05)
00:08.4 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [IR Port] (rev 05)
00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
00:0f.0 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)

interestingly I can ping the md from the core....

[maverick0815]

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.

[alx9r]

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:"

[maverick0815]

its been quite a while with this one...I eventually got a asrock330 -ion based. I think however in the end I did get it running...like I said, it's been a while since then.