Update. Sorry for the flurry of posts.
This is the message in DCERouter.log when I attach the device to a MD.
05 03/24/10 18:43:18.519 Socket::ReceiveData 0x8f18dc8 failed, bytes left 0 start: 273170000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 22 Incoming_Conn Socket 22 192.168.80.1 <0xb1a0ab90>
05 03/24/10 18:43:18.520 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 22 192.168.80.1 <0xb1a0ab90>
05 03/24/10 18:43:18.520 TCPIP: Closing connection to -1003 (Router Dev #0) 0x8f18dc8 m_Socket: -1 <0xb1a0ab90>
05 03/24/10 18:43:18.520 Router::RemoveAndDeleteSocket 0x8f18dc8 -1003 <0xb1a0ab90>
I don't even get a chance to select the com port and the web admin stalls out.
Update. CM11a was not working at all even when proper serial port was selected (after having to wait minutes and minutes for web admin to refresh). Plugged in USB-RS232 adapter and (after waiting and waiting again) selected that funny (pci0000:xxxx....) as my serial port. No luck. Hacked the serial port detection script to echo out ttyUSB0, selected it, and like magic the CM11a worked and I could control lights. However, the slow web admin remains but only when selecting the CM11a in the devices tree, otherwise normal.
The CM11a shortly crapped out and doesn't seem to be functioning properly (although LMCE seems to be communicating fine). The lights just dont turn on but I think this problem is unrelated to this post.