lam00028
18-09-2008, 21:54
Na de perikelen van gisteren (http://wl500g.info/showthread.php?t=16092) verder gegaan met de volgende how-to bluetooth in wl500g (http://wl500g.info/showthread.php?t=12762)
De HOW-TO laat in 6 stappen zien hoe het moet.
de eerste 3 stappen ipkg install bluez-* gaan probleemloos
directory aanmaken ook
na uitvoeren opstartscript een aantal fouten :
$ /tmp/harddisk/bluez/start-bluez
rm: cannot remove `/opt/var/run/dbus/pid': No such file or directory
/tmp/harddisk/bluez/start-bluez: /tmp/harddisk/bluez/start-bluez: 11: dbus-daemon: not found
/tmp/harddisk/bluez/start-bluez: /tmp/harddisk/bluez/start-bluez: 12: hcid: not found
/tmp/harddisk/bluez/start-bluez: /tmp/harddisk/bluez/start-bluez: 13: hciconfig: not found
/tmp/harddisk/bluez/start-bluez: /tmp/harddisk/bluez/start-bluez: 14: sdpd: not found
/tmp/harddisk/bluez/start-bluez: /tmp/harddisk/bluez/start-bluez: 15: pand: not found
by het handmatig uitvoeren van het opstart script voldoende fouten
waar deze newby geen kaas van gegeten heeft
Wie wil my a.u.b. helpen ? Foutlog hieronder
Ik gebruik 1.9.2.7-9 firmware
ipkg install bluez-libs
ipkg install bluez-utils
ipkg install bluez-hcidump
stap voor stap de entries in /tmp/harddisk/bluez/start-bluez uitgevoerd.
insmod /tmp/harddisk/bluez/module/bluez.o
result in system log :
Sep 18 21:42:02 kernel: BlueZ Core ver 2.4 Copyright (C) 2000,2001 Qualcomm Inc
Sep 18 21:42:02 kernel: Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
---------------------------------------------------------------------------------------------------------------------
insmod /tmp/harddisk/bluez/module/hci_usb.o
sh error : Segmentation fault
result in system log :
Sep 18 21:43:31 kernel: BlueZ HCI USB driver ver 2.1 Copyright (C) 2000,2001 Qualcomm Inc
Sep 18 21:43:31 kernel: Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
Sep 18 21:43:31 kernel: usb.c: registered new driver hci_usb
Sep 18 21:43:31 kernel: Unhandled kernel unaligned access in unaligned.c::emulate_load_store_insn, line 481:
Sep 18 21:43:31 kernel: $0 : 00000000 1000dc00 02010373 00000000 8096dc00 00000000 c012a1c0 00000070
Sep 18 21:43:31 kernel: $8 : 8096dc00 80852b20 c012a3e0 c012a3c2 c0128000 2abb24a8 00000000 c012a34f
Sep 18 21:43:31 kernel: $16: 00000000 c012a1c0 80852b20 00000001 c012a2e8 00000000 8096dc00 c012a1c0
Sep 18 21:43:31 kernel: $24: 00000000 2ac14e20 8053a000 8053bce0 8096dc00 c00cf3a4
Sep 18 21:43:31 kernel: Hi : 00000000
Sep 18 21:43:31 kernel: Lo : 00000660
Sep 18 21:43:31 kernel: epc : c01294dc Tainted: P
Sep 18 21:43:31 kernel: Status: 1000dc03
Sep 18 21:43:31 kernel: Cause : 80000010
Sep 18 21:43:31 kernel: Process insmod (pid: 154, stackpage=8053a000)
Sep 18 21:43:31 kernel: Stack: 7fff29b8 80275400 803b48a0 00000001 7fff29b8 80757bc0 8053bdf0
Sep 18 21:43:31 kernel: 00000001 803b48bc 800225b4 806cb0c0 00000000 8027b8f8 80275400 80598fc8
Sep 18 21:43:31 kernel: 10008ef0 8053a000 80757bc0 803b48a0 7fff29b8 8000a8fc 80275400 00000000
Sep 18 21:43:31 kernel: 800501c4 00000000 8027b8f8 00000000 00000000 c012a2c8 c012a1c0 80852b20
Sep 18 21:43:31 kernel: 00000001 c012a2e8 00000000 8096dc00 00000000 c00e0900 c00cf3a4 808ed840
Sep 18 21:43:31 kernel: 00000007 ...
Sep 18 21:43:31 kernel: Call Trace: [<800225b4>] [<8000a8fc>] [<800501c4>] [<c012a2c8>] [<c012a1c0>]
Sep 18 21:43:31 kernel: [<c012a2e8>] [<c00e0900>] [<c00cf3a4>] [<c00cf21c>] [<c00cef14>] [<c00cef98>]
Sep 18 21:43:31 kernel: [<80010e64>] [<c00cef14>] [<c00cefd4>] [<800113ec>] [<c00cef14>] [<c00cefd4>]
Sep 18 21:43:31 kernel: [<800111cc>] [<c00e0908>] [<c00cef14>] [<c00e0908>] [<c00ce1a8>] [<80010fd4>]
Sep 18 21:43:31 kernel: [<c012a2c8>] [<80010fd4>] [<c00ce108>] [<c00dd5b4>] [<c012a0c4>] [<c012998c>]
Sep 18 21:43:31 kernel: [<c012a128>] [<8001259c>] [<8001670c>] [<c0128060>] [<800085c4>]
Sep 18 21:43:31 kernel:
Sep 18 21:43:31 kernel: Code: 00a08021 00c0b821 0080f021 <106000e4> 8c45000c 30620001 1440000c 00003021 8fc300e8
De HOW-TO laat in 6 stappen zien hoe het moet.
de eerste 3 stappen ipkg install bluez-* gaan probleemloos
directory aanmaken ook
na uitvoeren opstartscript een aantal fouten :
$ /tmp/harddisk/bluez/start-bluez
rm: cannot remove `/opt/var/run/dbus/pid': No such file or directory
/tmp/harddisk/bluez/start-bluez: /tmp/harddisk/bluez/start-bluez: 11: dbus-daemon: not found
/tmp/harddisk/bluez/start-bluez: /tmp/harddisk/bluez/start-bluez: 12: hcid: not found
/tmp/harddisk/bluez/start-bluez: /tmp/harddisk/bluez/start-bluez: 13: hciconfig: not found
/tmp/harddisk/bluez/start-bluez: /tmp/harddisk/bluez/start-bluez: 14: sdpd: not found
/tmp/harddisk/bluez/start-bluez: /tmp/harddisk/bluez/start-bluez: 15: pand: not found
by het handmatig uitvoeren van het opstart script voldoende fouten
waar deze newby geen kaas van gegeten heeft
Wie wil my a.u.b. helpen ? Foutlog hieronder
Ik gebruik 1.9.2.7-9 firmware
ipkg install bluez-libs
ipkg install bluez-utils
ipkg install bluez-hcidump
stap voor stap de entries in /tmp/harddisk/bluez/start-bluez uitgevoerd.
insmod /tmp/harddisk/bluez/module/bluez.o
result in system log :
Sep 18 21:42:02 kernel: BlueZ Core ver 2.4 Copyright (C) 2000,2001 Qualcomm Inc
Sep 18 21:42:02 kernel: Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
---------------------------------------------------------------------------------------------------------------------
insmod /tmp/harddisk/bluez/module/hci_usb.o
sh error : Segmentation fault
result in system log :
Sep 18 21:43:31 kernel: BlueZ HCI USB driver ver 2.1 Copyright (C) 2000,2001 Qualcomm Inc
Sep 18 21:43:31 kernel: Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
Sep 18 21:43:31 kernel: usb.c: registered new driver hci_usb
Sep 18 21:43:31 kernel: Unhandled kernel unaligned access in unaligned.c::emulate_load_store_insn, line 481:
Sep 18 21:43:31 kernel: $0 : 00000000 1000dc00 02010373 00000000 8096dc00 00000000 c012a1c0 00000070
Sep 18 21:43:31 kernel: $8 : 8096dc00 80852b20 c012a3e0 c012a3c2 c0128000 2abb24a8 00000000 c012a34f
Sep 18 21:43:31 kernel: $16: 00000000 c012a1c0 80852b20 00000001 c012a2e8 00000000 8096dc00 c012a1c0
Sep 18 21:43:31 kernel: $24: 00000000 2ac14e20 8053a000 8053bce0 8096dc00 c00cf3a4
Sep 18 21:43:31 kernel: Hi : 00000000
Sep 18 21:43:31 kernel: Lo : 00000660
Sep 18 21:43:31 kernel: epc : c01294dc Tainted: P
Sep 18 21:43:31 kernel: Status: 1000dc03
Sep 18 21:43:31 kernel: Cause : 80000010
Sep 18 21:43:31 kernel: Process insmod (pid: 154, stackpage=8053a000)
Sep 18 21:43:31 kernel: Stack: 7fff29b8 80275400 803b48a0 00000001 7fff29b8 80757bc0 8053bdf0
Sep 18 21:43:31 kernel: 00000001 803b48bc 800225b4 806cb0c0 00000000 8027b8f8 80275400 80598fc8
Sep 18 21:43:31 kernel: 10008ef0 8053a000 80757bc0 803b48a0 7fff29b8 8000a8fc 80275400 00000000
Sep 18 21:43:31 kernel: 800501c4 00000000 8027b8f8 00000000 00000000 c012a2c8 c012a1c0 80852b20
Sep 18 21:43:31 kernel: 00000001 c012a2e8 00000000 8096dc00 00000000 c00e0900 c00cf3a4 808ed840
Sep 18 21:43:31 kernel: 00000007 ...
Sep 18 21:43:31 kernel: Call Trace: [<800225b4>] [<8000a8fc>] [<800501c4>] [<c012a2c8>] [<c012a1c0>]
Sep 18 21:43:31 kernel: [<c012a2e8>] [<c00e0900>] [<c00cf3a4>] [<c00cf21c>] [<c00cef14>] [<c00cef98>]
Sep 18 21:43:31 kernel: [<80010e64>] [<c00cef14>] [<c00cefd4>] [<800113ec>] [<c00cef14>] [<c00cefd4>]
Sep 18 21:43:31 kernel: [<800111cc>] [<c00e0908>] [<c00cef14>] [<c00e0908>] [<c00ce1a8>] [<80010fd4>]
Sep 18 21:43:31 kernel: [<c012a2c8>] [<80010fd4>] [<c00ce108>] [<c00dd5b4>] [<c012a0c4>] [<c012998c>]
Sep 18 21:43:31 kernel: [<c012a128>] [<8001259c>] [<8001670c>] [<c0128060>] [<800085c4>]
Sep 18 21:43:31 kernel:
Sep 18 21:43:31 kernel: Code: 00a08021 00c0b821 0080f021 <106000e4> 8c45000c 30620001 1440000c 00003021 8fc300e8