OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: liberated on March 09, 2007, 04:04:05 am
-
My Ambicom BT card (LSE039) won't work. Cardctl identifies the card OK. The problem is with the driver. Here's the errors you get from 'modprobe bluecard_cs':
/lib/modules/2.4.20/kernel/drivers/bluetooth/bluecard_cs.o: /lib/modules/2.4.20/kernel/drivers/bluetooth/bluecard_cs.o: unresolved symbol hci_register_dev
/lib/modules/2.4.20/kernel/drivers/bluetooth/bluecard_cs.o: /lib/modules/2.4.20/kernel/drivers/bluetooth/bluecard_cs.o: unresolved symbol hci_recv_frame
/lib/modules/2.4.20/kernel/drivers/bluetooth/bluecard_cs.o: /lib/modules/2.4.20/kernel/drivers/bluetooth/bluecard_cs.o: unresolved symbol hci_unregister_dev
/lib/modules/2.4.20/kernel/drivers/bluetooth/bluecard_cs.o: insmod /lib/modules/2.4.20/kernel/drivers/bluetooth/bluecard_cs.o failed
/lib/modules/2.4.20/kernel/drivers/bluetooth/bluecard_cs.o: Can't locate module 2
It looks to me like the driver is all broken, is there a fix?
-
Same problem with Billionton CF card on my C1000
In beta 1 was everything OK
Mar 12 13:37:47 cardmgr[531]: socket 0: Billionton Bluetooth Card
Mar 12 13:37:48 insmod: /lib/modules/2.4.20/kernel/drivers/bluetooth/hci_uart.o: insmod tty-ldisc-15 failed
Mar 12 13:37:49 cardmgr[531]: executing: './bluetooth start ttyS3 2>&1'
Mar 12 13:37:49 cardmgr[531]: + Starting Bluetooth... Can't set line discipline: Invalid argument
Mar 12 13:37:49 cardmgr[531]: + Can't initialize device: Invalid argument
Mar 12 13:37:49 cardmgr[531]: + Can't open HCI socket.: Address family not supported by protocol
Mar 12 13:37:49 cardmgr[531]: + Can't open RFCOMM control socket: Address family not supported by protocol
Mar 12 13:37:49 cardmgr[531]: + Can't open RFCOMM control socket: Address family not supported by protocol
Mar 12 13:37:49 cardmgr[531]: + Done.
with manual insmod
root- insmod hci_uart.o
hci_uart.o: hci_uart.o: unresolved symbol hci_register_dev
hci_uart.o: hci_uart.o: unresolved symbol hci_recv_frame
hci_uart.o: hci_uart.o: unresolved symbol hci_unregister_dev
root- insmod tty-ldisc-15
where the problems can be?
thnx for help
-
I found the problem. The kernel is broken. The /lib/modules/2.4.20/kernel/net directory is missing (or if it was empty, without subdirectories like bluetooth) and modules.dep is missing all dependencies for these modules.
Luckily the kernel contained in the hdimage is complete, thus i fixed this by copying the said subfolders and modules.dep from /media/fakeroot/ to the rom root (/).
-
I found the problem. The kernel is broken. The /lib/modules/2.4.20/kernel/net directory is missing (or if it was empty, without subdirectories like bluetooth) and modules.dep is missing all dependencies for these modules.
Luckily the kernel contained in the hdimage is complete, thus i fixed this by copying the said subfolders and modules.dep from /media/fakeroot/ to the rom root (/).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=156018\"][{POST_SNAPBACK}][/a][/div]
this is fixed in the latest pdaXii13 Akita build 5.3.2 which was uploaded about an hour ago
the net directory actually exists, but is in the wrong location under /lib/modules
there are a few enhancements in this new version, the most noticable will be faster rotation and resume....
the spitz version is still being uploaded and once it is done, there will be an announcement...