From: Sigrid Kronenberger <skronenberger@web.de>
To: Marcel Holtmann <marcel@holtmann.org>
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:03:46 +0200 [thread overview]
Message-ID: <20040813210346.6c40aed3@localhost> (raw)
In-Reply-To: <1092336801.28711.172.camel@pegasus>
On Thu, 12 Aug 2004 20:53:21 +0200
Marcel Holtmann <marcel@holtmann.org> wrote:
Hi Marcel,
> Hi Sigrid,
>
> > Bluetooth: Core ver 2.3
> > 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
> > drivers/usb/core/usb.c: registered new driver bfusb
> > Unable to handle kernel NULL pointer dereference at virtual address
> > 00000028
> > printing eip:
> > c016b532
> > *pde = 00000000
> > Oops: 0000 [#1]
> > CPU: 0
[...]
>
> 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... ;))
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
Adding 506008k swap on /dev/hda5. Priority:-1 extents:1
Adding 511520k swap on /dev/hde1. Priority:-2 extents:1
Adding 818960k swap on /dev/hdg7. Priority:-3 extents:1
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected VIA Twister-K/KT133x/KM133 chipset
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: AGP aperture is 32M @ 0xd8000000
No kernel-oops :)
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.
Regards
Sigrid
next prev parent reply other threads:[~2004-08-13 19:03 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 [this message]
2004-08-13 19:10 ` Marcel Holtmann
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=20040813210346.6c40aed3@localhost \
--to=skronenberger@web.de \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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).