Thanks for the reply. I do think I have these latest fixes. I have done updating my raspian wheezy regularly by apt-get update/upgrade and also ran the rpi-update tool. I think this equals the latest image.Genius23008 wrote:Try running XBMC off the new Wheezy image. The Wheezy image now has USB fixes to stop interruptions, so I think that's worth a shot. But before that, are you running the dongle off the Pi or off a hub? You should run it off a hub, since the Pi is unlikely to give enough power to it (I think each port is 120mAH, I dunno).
Thanks. That was a long thread, I dont have time to read the full thread now, but I noticed these three suggestions in some of the later posts.MaxK1 wrote:I posted a possible workaround for this in another thread
http://www.raspberrypi.org/phpBB3/viewt ... 28&t=16307
I don't know if it worked reliably for everyone, but it did for at least a few people.
I did try all three, ut it didnt change anything.MaxK1 wrote:Yep - that's it. Like I said, it worked pretty well for most. Fixing the USB driver _should_ fix it
properly. Good luck!
I'm using the raspian wheezy from 16 aug. And have made updates regularly on this image.MaxK1 wrote:What distro are you using? /etc/rc.local is usually the last startup script that runs before you get
the login prompt. That you don't see a 20 second delay suggests it isn't being executed. How and where do you have it set up to run XBMC?
sorry for the delay, I've been away for a few days.MaxK1 wrote:Not at all... Just trying to figure out where else you could put the rmmod/insmod to be sure it is executed.
From what you have described, it _should_ be running it. Unless rc.local is not executable, I can't think of a reason it wouldn't run. Could you check that?
I did some "stress test" today, I must have restarting the system more than 10 times (plus about 5 times yesterday) and it does work 100% every time.MaxK1 wrote:Blame it on the keyboard....
Glad it worked for you!