Author Topic: Bt Initialization Error On Bootup (Read 3266 times)

Antikx · « **on:** February 03, 2006, 11:37:06 am »

I uninstall some applications yesterday and now when I reboot it gets to the point where it starts up the USB modules it gives it a green [ OK ], but gives this error:
Can't open RFCOMM control socket: Address family not supported by protocol.
Now USB host does not seem to work.

I didn't think I had uninstalled anything that had anything to do with USB.
On the first reboot it did complain about a kernel module, but it hasn't complained since.

A search of the forum seems to only talk about Bluetooth issues.

Can anyone offer any tips, please?

Antikx · « **Reply #1 on:** February 03, 2006, 03:58:25 pm »

I just reboot and noticed that it does start to try and initialize the BT but then it disapears and give the above error message. So it does seem to be a problem with BT. I don't understand why it is effecting USB though.
One app I uninstall was Kismet. Anyone had trouble with uninstalling it?

Antikx · « **Reply #2 on:** February 04, 2006, 01:05:17 am »

I gave up and reflashed. I'm ashamed of myself too. I wanted to figure it out, but ran out of time.
Ahhh...fresh ROM flash... like fresh bed linen.

harvell · « **Reply #3 on:** February 23, 2007, 11:45:54 pm »

Like a bad flu I too have caught this bug...

Antikx · « **Reply #4 on:** February 24, 2007, 03:11:46 am »

sorry dude. wish I had found the answer.

Meanie · « **Reply #5 on:** February 24, 2007, 08:12:08 am »

Quote

sorry dude. wish I had found the answer.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=155129\"][{POST_SNAPBACK}][/a][/div]

this is a harmless error though. it doesn't break anything, but it is a bit annoying and scary for some

the latest mini update of pdaXii13 Akita (5.3.1.1.1 which is just being reported as 5.3.1) fixes it, ie pipes this error to /dev/null

Antikx · « **Reply #6 on:** February 24, 2007, 02:23:34 pm »

I must have had two diff things happen at the same time then.

Meanie · « **Reply #7 on:** February 28, 2007, 08:35:10 pm »

Quote

I must have had two diff things happen at the same time then.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=155172\"][{POST_SNAPBACK}][/a][/div]

the usbstorage module is a bit temperamental. if you point it at the sd, it is supposed to unmount the sd ad remount it so that only your pc can see it as a usb storager device until you unplug or eject hardware on your pc. then it gets remounted as a sd for you to use on the zaurus.
however, sometimes, it doesn't do it correctly and you can access the sd from both your pc and the zaurus concurrently. in this case, it it a bit flakey if you change any files, ie copy or remove files since the filesystem on the device is controlled by both your pc and the z, and thus might get out of sync.
sometimes of course, when your sd is being used, it fails to unmount and the pc won't see it as a usbstorage device...

harvell · « **Reply #8 on:** March 04, 2007, 09:28:48 pm »

That's kind of strange on how it affects my bluetooth CF card. When I restart bluetooth it gives me that error. Then I cant launch any bluetooth scanning. I don't have it right in front of me but I'll post the error messages. I also reflashed but didn't seem to fix the issue.

News:

Author Topic: Bt Initialization Error On Bootup (Read 3266 times)