linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Sigrid Kronenberger <skronenberger@web.de>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] AVM BlueFritz with Linux Kernel 2.6.3-15mdk
Date: Fri, 13 Aug 2004 21:10:07 +0200	[thread overview]
Message-ID: <1092424207.4501.27.camel@pegasus> (raw)
In-Reply-To: <20040813210346.6c40aed3@localhost>

Hi Sigrid,

> > and this is the problem. The firmware loading generates an oops. You
> > must install a newer kernel (at least 2.6.8-rc3) before we can
> > proceed.
> 
> Now, I have updated to 2.6.8-0.rc2.2mdk (sorry, but I'm not used in
> compiling my own kernel, so I prefer rpm-packages, is easier... ;))

this depends on if we get this working without any trouble. Otherwise
you must compile a vanilla kernel, because I don't know what patches
they included.

> Now, it looks a little bit better: 
> 
> /var/log/dmesg (partly)
> 
> uhci_hcd 0000:00:07.3: irq 11, io base 00009800
> uhci_hcd 0000:00:07.3: new USB bus registered, assigned bus number 2
> hub 2-0:1.0: USB hub found
> hub 2-0:1.0: 2 ports detected
> usb 1-2: new full speed USB device using address 2
> usb 1-2: configuration #1 chosen from 2 choices
> Bluetooth: Core ver 2.6
> NET: Registered protocol family 31
> Bluetooth: HCI device and connection manager initialized
> Bluetooth: HCI socket layer initialized
> Bluetooth: BlueFRITZ! USB driver ver 1.1
> bfusb_probe: Firmware request failed
> bfusb: probe of 1-2:1.0 failed with error -5
> usbcore: registered new driver bfusb

But the firmware request still fails. Where do you put your bfubase.frm
file? Is hotplug installed and do you have a firmware.agent script under
/etc/hotplug.

> Should I change the firmware again? Do you know which version of the
> AVM-firmware have problems with the kernel? The first version I've
> tested, was 3-18-39, after that, I've changed to 3-17-53. 

Use the older one, because I don't know if this kernel includes my
workaround.

Regards

Marcel




-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-08-13 19:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 21:12 [Bluez-users] AVM BlueFritz with Linux Kernel 2.6.3-15mdk Sigrid Kronenberger
2004-08-11 22:13 ` Marcel Holtmann
2004-08-12 17:48   ` Sigrid Kronenberger
2004-08-12 18:07     ` Marcel Holtmann
2004-08-12 18:34       ` Sigrid Kronenberger
2004-08-12 18:53         ` Marcel Holtmann
2004-08-13 19:03           ` Sigrid Kronenberger
2004-08-13 19:10             ` Marcel Holtmann [this message]
2004-08-13 19:27               ` Sigrid Kronenberger
2004-08-13 19:32                 ` Marcel Holtmann
2004-08-13 19:47                   ` Sigrid Kronenberger
2004-08-13 19:51                     ` Marcel Holtmann
2004-08-13 20:00                       ` Sigrid Kronenberger

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=1092424207.4501.27.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=skronenberger@web.de \
    /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;
as well as URLs for NNTP newsgroup(s).