Hello!

I have tried running RC and now today the final release of Intrepid ibex, but it freezes at a module called "starting bluetooth". I don't have bluetooth on this computer, so is there a parameter I could feed the kernel at boot to try if it might work this time?

Thanks!

Is this live mode we are talking about? Will it install directly (select install from the startup menu)?
Or you can try the alternate CD - it doesn't mandate starting any services.

https://bugs.launchpad.net/ubuntu/+s...ux/+bug/262927
http://ubuntuforums.org/showthread.php?t=927293

Hallo,

I deactivated any bluetooth services by unchecking them from the automatic start-up service list: go to System > Preferences > Sessions > and uncheck "bluetooth manager"
then reboot.

Honestly I've also unistalled every bluetooth reference from synaptic but... the problems was solved just deactivating the startup bluetooth services from "Sessions"

Best regasrds

After looking through the threads you gave me, I noticed it was caused by my WINTVPVR2 plugged in... Got it out and everything works wonder!!

This is one thing I hate about linux, it stated that bluetooth service was not correct, but it ended up being a really specific problem with this PVR.

Anyways, with great support, I got it to work!

Thanks!

Well done!You did not mention that linux was "telling you" anything in your original post. System messages are vital to swiftly understanding your problem.

Had you mentioned this earlier, I could have pointed at the correct answer directly rather than employ the shotgun method I did.

If the TV card had disabled bluetooth services in HW, then the message is correct, they are invalid. They have been invalidated by the TV card.

Usually I would suggest filing a bug-report against the error message - but I don't see what to expect maintainers to do about this. If (eg) BIOS says a service is available, but the driver cannot find the hardware, then the service is invalid... how on Earth is the kernel supposed to tell that a specific bit of HW is responsible.

Note: had this issue appeared in a proprietary OS, you would have been unable to fix it... and the error message would have been a number.

As gnu/linux users, we have access to generally excellent service and resources unavailable to proprietary OS users except for a large fee. We get used to the high standards and end up, sometimes unreasonably, demanding even higher standards. That service standards continue to improve is a testament to the raw power of the market-model.

Sit back.
Enjoy.

Thanks my friend for the answer!

I do understand what you say, although the only error message I got was:

And it froze right there. What I meant is that, as a computer user, I know my capture card is not bluetooth so I wouldn't have think of checking this in the first place. If I didn't have access to another computer with internet on it, I probably wouldn't have figured this on my own knowing only this much of information.

BUT, I still love linux more than any other OS, and the community, in part from users like you, is priceless (pun intended)

Take care!