top | item 5341654

(no title)

alirov | 13 years ago

I haven't delved into the Windows drivers but clearly they're doing something that the Ubuntu ones aren't for this issue to exist. I just noticed it's happening after a "cold boot" of the amBX. I'm just calling it an initialization issue because that's what it seems to me. Just wanted to clear that up first just in case the way I was using "initialization" wasn't clear.

I'm using a combination of boblight, ruby-usb and combustd to get it to work. This isn't my blog but I used this as a guideline to get everything up and running:

http://slickeel.wordpress.com/2011/03/25/philips-ambx-starte...

The tricky thing was realizing I had to have it "initialize" in Windows before this would work.

discuss

order

No comments yet.