Attempted on g1 droid running 2.2.1 (froyo).

Originally I got a menu. Unfortunately it seemed that the only buttons that worked for me were lights on and off. These worked as if the area below them were a big column, so if I hit "tv" or "direct dial" or "sleeping menu" it would turn the lights on. I then made the mistake of multitouch resize, and all went black.

Background and L shaped gradient "button" is all that is now visible. Will attach a screen cap later.

Tried every res/aspect.

I will retry to make work/break again and attach log.

Could it be that the cause of the problem is a not propperly installed bluetooth usb dongle?
I have a Sitecom Micro Adapter Bluetooth 2.1 USB CN-516.
Sometimes the MD does boot up (rarely) and then i notice in the webadmin that the bluetooth dongle did not get configured right and also during bootup i get a black screen indicating that there was a device not installed propperly.

anybody any idea?

br,
Raymond

I would try booting the MD raw, with nothing plugged in... only plugging in devices after the setup wizard had rooms setup... if you have not already done so.

Don't pay attention to me. I drink sometimes. I am the ass, not you sir.

So basically, you try your best to make it work by searching the forum/wiki/chatroom.  If you are still unable to resolve, then create a ticket with what you did and what the result was and hope for the best.

Sounds simple.

:-)

Thanks,

<M>

Odd...

Sounds dismissive to me. Don't get me wrong, I am not involved in the project... I just mean that if it were my work in question... I would take that to mean that I was "doing something fundamentally wrong" without actually having to explain ones area of expertice.

That's awesome.


I wish my dick was that big.

Thanks for your input, i will look into it.
Couldn't it be that the onboard NIC isn't supported?

Br,
Raymond

Yes. Absolutely. I was too lazy to look it up and assumed you had. Disable onboard and plug in one you know works.
Or you can try and fix that one with either sk98lin or skge drivers. It says 3com, but it is actually a Marvell driver written for SysKonnect. Probably just a quick add to a .conf file and rebuild the image...

I am lazy and ignorant though. I would disable it and install a cheapy I know works.


I would think you could CD boot and see how kubuntu handles the NIC, if at all.

I believe that board has wifi on-board. It has caused kernel panic before for me.

The 173 driver is being loaded because you have a pre7xxx series card.

* I see I am mistaken, and it just has a proprietary wifi adapter, and one of the models comes with that installed.

I would still creep around the bios and turn off pretty much anything you know you will not be using (ie, cool and quiet... make sure that the chip which the wifi plugin at the end of the board uses is off etc).

- Setup connected to a Monitor (DVI)

Plug into VGA.

Or, conversely, when you get to black screen, on a keyboard or remote, press the following.
Enter (then brief pause)
down (x2)
right
down (x7)
right
down
enter

This will pipe out through DVI, 1080p, at 60hz.
Good luck.

What video card are you using?

I would also crush the wifi onboard.

I wanted to mention that the remote suicide is my fault. I had 2 different UIRTs attached, so it was hitting multiples on certain buttons... and buttons that repeat, like volume, were arriving in duplicate, eventually crushing something, it seems. The other UIRT is miniature, and forgot it was there.

So... I'm dumb.
Again.

I take it back... not the dumbness, but with a single USBUIRT I have crashed it 3 times today by being to quick on the trigger.

No, no waterproof controller - just use phone and/or webdt

Less than 400. That's how I'd roll... if my life were awesome and I had a pool/spa.

Sorry, I misunderstood... I thought you meant the second UI2 option, not the second of the three options. I see now I misread.

Good luck!

Reboot the machine and hold the shift key down while booting, this will dump you back into the AVWizard.

Try the middle option. I do not believe the 5500 will run full UI2. I do believe it will work without alpha... but no guarantee. You should use the "test" option first while selecting. Worst case scenario UI1 is pleasant enough and fully functional until you can get a better card.

What UI option did you choose?
If you chose UI2, with or without overlays (alpha), and did you run a test first?
If so, describe what did the test looked like.

If you cannot make UI2 work, it is probably from my bad advice on a duct tape nvidia driver. You might just  do a fresh install. I find down the road it is best to get everything working the right way when possible. Everything is connected to something later on.

Good luck.

Yay!

I think everyone has done it at least once... don't kick yourself. Glad you are up and running.

You will want a decent PSU if you do not already have one. 650w or greater.