From: Sebastian Roth <sebiroth@web.de>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Re: Driver version problems..hci_usb & bluetooth parser
Date: Tue, 22 Feb 2005 21:15:39 +0100 [thread overview]
Message-ID: <cvg3ls$t62$1@sea.gmane.org> (raw)
In-Reply-To: <20050222172313.48745.qmail@web26410.mail.ukl.yahoo.com>
Hi!
> hci_usb: no version for "struct_module" found: kernel
> tainted.
> hci_usb: no version magic, tainting kernel.
Try google or some other great magic tool ;-)
Seems to me that the kernel image was not compiled from
exactly the same sources.
IMHO it's better to compile a complete new kernel and not
only some modules and try to load them into the
distribution kernel (this is just my guess about what might
be the problem so please complain if I'm wrong)
Best regards,
Sebastian
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-02-22 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 16:40 [Bluez-users] Driver version problems..hci_usb & bluetooth parser benbouzid imad
2005-02-22 17:15 ` Marcel Holtmann
2005-02-22 17:23 ` benbouzid imad
2005-02-22 18:10 ` Marcel Holtmann
2005-02-22 20:15 ` Sebastian Roth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='cvg3ls$t62$1@sea.gmane.org' \
--to=sebiroth@web.de \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox