Re: r6.8 bluez kernel modules broken?
- hm I think best advice is concentrate at the UNSLUNG B.T.-page for
But as said we need someone to really know how to do this help us a
--- In email@example.com, Christoph Simon <ml133@...>
> On Thu, 27 Apr 2006 21:42:56 -0000
> "janne5011" <janne5011@...> wrote:
> > What is tle? <---it was a typo. =tHe
> Oh. I thought it to be an acronym (Three Letter Error) ;-)
> I do think, you are using some different version than, I do, because
> it really looks that some packages are badly broken; just see the
> transcript at the end of this message.
> > I installed this from the SLUG page:
> > ipkg install \
> > kernel-module-bluetooth \
> > kernel-module-l2cap \
> > kernel-module-hci-usb
> Maybe, I missed something. I've installed all these packages but the
> first one:
> # ipkg install kernel-module-bluetooth
> Nothing to be done
> An error ocurred, return value: 4.
> Collected errors:
> Cannot find package kernel-module-bluetooth.
> Check the spelling or perhaps run 'ipkg update'
> Might it be that I have to change some analogue to the apt/sources
> file? I've left everything as by default.
> > and after that all that works at the unslung bluetooth-wiki page
> > after the downloads and ipkg installs I used this from the wiki:bluetooth,
> > insmod bluez
> Or? might it be that, above, you didn't mean kernel-module-
> but kernel-module-bluez? Because that one _is_ installed here, whilein root is up to date.
> it's still not working.
> > insmod hci_usb
> This one doesn't work here.
> # ipkg install kernel-module-hci-usb
> Package kernel-module-hci-usb (2.4.22.l2.3r63-r12) installed
> Nothing to be donebluez
> # insmod hci_usb
> insmod: hci_usb: no module by that name found
> > insmod l2cap
> > # may not be needed
> > insmod rfcomm
> > insmod bnep
> > then this:
> > hcid;sdpd;pand --listen --role NAP --master --persist
> > then this:
> > echo 1 > /proc/sys/net/ipv4/ip_forward
> > then hciconfig hci0 up
> > and hciconfig
> > but now I dont know what to do since this:
> > ifconfig bnep0
> > give this error:
> > bnep0: error fetching interface information: Device not found
> You'll have to listen to this message. try ifconfig without bnep0;
> this will list all, in case it is using the name bnep or bnep1. Look
> at the logfiles in /var/log/ to see if there was some problem
> earlier. Did you do "insmod bnep"? Did you realise that the ifconfig
> line also needs an address to do what the wiki-page suggests?
> > ok first of all make sure you do ipkg update.
> This is a fresh installation, but I did it anyway every once in a
> > I followed this
> > http://www.nslu2-linux.org/wiki/Peripherals/BluetoothUnslung
> I did try to follow this one but:
> - it says to work only on unslung 5.5, and there seem to be many
> differences wrt 6.8
> - it requites the kernel-module-bluetooth, which is not in my
> (updated) list
> - my ipgk doesn't like "-f" which is supposed to be followed by the
> name of some configuration file rather than a package name
> - what bugs me, is that the modules are here but can't be installed
> because insmod consideres them to be the wrong architecture.
> In case the -f in the wiki page is meant to be -force-something, I
> tried this:
> # ipkg install -force-reinstall kernel-module-
> Reinstalling kernel-module-bluez (2.4.22.l2.3r63-r12) on root...linux.org/feeds/unslung/modules/cross/6.8-beta/kernel-module-
> Downloading http://ipkg.nslu2-
> Configuring kernel-module-bluezxfs/modules.dep
> depmod: cannot read ELF header from //opt/lib/modules/2.4.22-
> depmod: cannot read ELF header from //opt/lib/modules/2.4.22-xfs/modules.generic_string
> depmod: //opt/lib/modules/2.4.22-xfs/modules.ieee1394map is not anELF file
> depmod: //opt/lib/modules/2.4.22-xfs/modules.isapnpmap is not anELF file
> depmod: cannot read ELF header from //opt/lib/modules/2.4.22-xfs/modules.parportmap
> depmod: //opt/lib/modules/2.4.22-xfs/modules.pcimap is not an ELFfile
> depmod: cannot read ELF header from //opt/lib/modules/2.4.22-xfs/modules.pnpbiosmap
> depmod: //opt/lib/modules/2.4.22-xfs/modules.usbmap is not an ELFfile
> Doesn't this look as some broken packages? What could I have done
> wrong here?