2.6.8-rc2-mm1: bluetooth broken?

DISCUSSION Pavel Machek 6 participants 13 messages Aug 8, 2004 – Aug 9, 2004

Share & tools

Pavel Machek

author

2004-08-08 19:25 UTC #0 lore raw

Hi!

I'm using USB bluetooth dongle for connecting with my cell phone... It works in 2.6.7, but not in -rc2-mm1. Is that known?
Pavel

Signature · 2 lines

People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

Marcel Holtmann

2004-08-08 22:14 UTC #1 lore raw

Hi Pavel,

Quoted 2 lines

I'm using USB bluetooth dongle for connecting with my cell phone... It works in 2.6.7, but not in -rc2-mm1. Is that known?

not that I know of, but I need more details and first you should try the latest 2.6.8-rc3, 2.6.8-rc3-bk3 or 2.6.8-rc3-mm2.

Regards

Marcel

Filip Van Raemdonck

2004-08-09 09:54 UTC #2 lore raw

Quoted 6 lines · Marcel Holtmann

Quoted 3 lines
I'm using USB bluetooth dongle for connecting with my cell phone... It works in 2.6.7, but not in -rc2-mm1. Is that known?
not that I know of, but I need more details and first you should try the latest 2.6.8-rc3

Works here for USB dongle <-> cell phone. Dunno about the others. So, it's not a general breakage (in that kernel version)

Regards,

Filip

Signature · 2 lines

Hardware, n.:
	The parts of a computer system that can be kicked.

Marcel Holtmann

2004-08-09 10:24 UTC #3 lore raw

Hi Filip,

Quoted 8 lines

Quoted 5 lines
Quoted 2 lines
I'm using USB bluetooth dongle for connecting with my cell phone... It works in 2.6.7, but not in -rc2-mm1. Is that known?
not that I know of, but I need more details and first you should try the latest 2.6.8-rc3
Works here for USB dongle <-> cell phone. Dunno about the others. So, it's not a general breakage (in that kernel version)

this is what I was thinking, because I always run the latest stuff from the Bitkeeper repository directly. Seems that there is something in the -mm patches that broke it. Can someone test the latest -mm and report if the Bluetooth subsystem is working or not?

Regards

Marcel

Stephane Jourdois

2004-08-09 12:09 UTC #4 lore raw

Quoted 6 lines · Marcel Holtmann

Quoted 6 lines
Quoted 5 lines
Quoted 2 lines
I'm using USB bluetooth dongle for connecting with my cell phone... It works in 2.6.7, but not in -rc2-mm1. Is that known?
not that I know of, but I need more details and first you should try the latest 2.6.8-rc3

Quoted 7 lines

Quoted 2 lines
Works here for USB dongle <-> cell phone. Dunno about the others. So, it's not a general breakage (in that kernel version)
this is what I was thinking, because I always run the latest stuff from the Bitkeeper repository directly. Seems that there is something in the -mm patches that broke it. Can someone test the latest -mm and report if the Bluetooth subsystem is working or not?

Not working here since 2.6.8-rc2-mm2.
Works in 2.6.8-rc2-mm1.

debian sid up-to-date with latest bluez-utils.

I tried hidp only.

Signature · 4 lines

 ///  Stephane Jourdois         /"\  ASCII RIBBON CAMPAIGN \\\
(((    Ingénieur développement  \ /    AGAINST HTML MAIL    )))
 \\\   24 rue Cauchy             X                         ///
  \\\  75015  Paris             / \    +33 6 8643 3085    ///

Marcel Holtmann

2004-08-09 13:24 UTC #5 lore raw

Hi Stephane,

Quoted 7 lines

Quoted 4 lines
this is what I was thinking, because I always run the latest stuff from the Bitkeeper repository directly. Seems that there is something in the -mm patches that broke it. Can someone test the latest -mm and report if the Bluetooth subsystem is working or not?
Not working here since 2.6.8-rc2-mm2.
Works in 2.6.8-rc2-mm1.

I never used a -mm patch, so you must be a little bit more specific what is not working. What Bluetooth hardware are you using? Do the logfiles or dmesg include anything helpful?

Regards

Marcel

Stephane Jourdois

2004-08-09 13:35 UTC #6 lore raw

Quoted 11 lines · Marcel Holtmann

Quoted 7 lines
Quoted 4 lines
this is what I was thinking, because I always run the latest stuff from the Bitkeeper repository directly. Seems that there is something in the -mm patches that broke it. Can someone test the latest -mm and report if the Bluetooth subsystem is working or not?
Not working here since 2.6.8-rc2-mm2.
Works in 2.6.8-rc2-mm1.
I never used a -mm patch, so you must be a little bit more specific what is not working. What Bluetooth hardware are you using? Do the logfiles or dmesg include anything helpful?

I use a usb dongle, unfortunately included in my laptop, so I can't see any serial number or anything.

lspci -v :
----
[..snip..]
0000:00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02) (prog-if 00 [UHCI])
Subsystem: CLEVO/KAPOK Computer: Unknown device 0500
Flags: bus master, medium devsel, latency 0, IRQ 193
I/O ports at 1cc0 [size=32]

0000:00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 (rev 02) (prog-if 00 [UHCI])
Subsystem: CLEVO/KAPOK Computer: Unknown device 0500
Flags: bus master, medium devsel, latency 0, IRQ 201
I/O ports at 1ce0 [size=32]

0000:00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02) (prog-if 00 [UHCI])
Subsystem: CLEVO/KAPOK Computer: Unknown device 0500
Flags: bus master, medium devsel, latency 0, IRQ 185
I/O ports at 2000 [size=32]

0000:00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 (rev 02) (prog-if 00 [UHCI])
Subsystem: CLEVO/KAPOK Computer: Unknown device 0500
Flags: bus master, medium devsel, latency 0, IRQ 193
I/O ports at 2020 [size=32]

0000:00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) (prog-if 20 [EHCI])
Subsystem: CLEVO/KAPOK Computer: Unknown device 0500
Flags: bus master, medium devsel, latency 0, IRQ 209
Memory at e8000000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] #0a [20a0]
[..snip..]
----

I use it to communicate using HIDP with my Logitech MX900 mouse, which works perfectly under 2.6.8-rc2-mm1, and no more since 2.6.8-rc2-mm2.

strace hidd --search :
----
[..snip..]

socket(PF_BLUETOOTH, SOCK_RAW, 6)       = 3
socket(PF_BLUETOOTH, SOCK_RAW, 1)       = 4
brk(0)                                  = 0x804d000
brk(0x806e000)                          = 0x806e000
brk(0)                                  = 0x806e000
ioctl(4, 0x800448d2, 0x804d008)         = 0
close(4)                                = 0
socket(PF_BLUETOOTH, SOCK_RAW, 1)       = 4
ioctl(4, 0x800448d2, 0x804d008)         = 0
close(4)                                = 0
socket(PF_BLUETOOTH, SOCK_RAW, 1)       = 4
ioctl(4, 0x800448d3, 0xbfffe940)        = -1 ENODEV (No such device)
close(4)                                = 0
fstat64(1, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7ea0000
socket(PF_BLUETOOTH, SOCK_RAW, 1)       = 4
ioctl(4, 0x800448d2, 0x804d008)         = 0
close(4)                                = 0
close(3)                                = 0

write(1, "Searching ...\n", 14Searching ...
) = 14
munmap(0xb7ea0000, 4096) = 0
----

I saw several lines as those in my dmesg :
----
usb 4-2: usbfs: USBDEVFS_CONTROL failed cmd hid2hci rqt 64 rq 0 len 0 ret -32
----

I'll try now to narrow which patch is broking things for me in -mm. I'll post my results to this thread.

Signature · 4 lines

 ///  Stephane Jourdois         /"\  ASCII RIBBON CAMPAIGN \\\
(((    Ingénieur développement  \ /    AGAINST HTML MAIL    )))
 \\\   24 rue Cauchy             X                         ///
  \\\  75015  Paris             / \    +33 6 8643 3085    ///

Marcel Holtmann

2004-08-09 14:23 UTC #7 lore raw

Hi Stephane,

Quoted 6 lines

Quoted 3 lines
I never used a -mm patch, so you must be a little bit more specific what is not working. What Bluetooth hardware are you using? Do the logfiles or dmesg include anything helpful?
I use a usb dongle, unfortunately included in my laptop, so I can't see any serial number or anything.

I installed a 2.6.8-rc3-mm2 on my development machine and everything works like it should. I tried a RFCOMM connection to my mobile, a HCRP connection to my printer and I used a Bluetooth mouse. All stuff worked perfect.

Do "hciconfig -a" show your Bluetooth device? Do "/proc/bus/usb/devices" has an entry for it? Check "dmesg" for any USB related error messages.

Regards

Marcel

Stephane Jourdois

2004-08-09 15:17 UTC #8 lore raw

(Short answer : jump to the end of this mail.)

Quoted 11 lines · Marcel Holtmann

Quoted 6 lines
Quoted 3 lines
I never used a -mm patch, so you must be a little bit more specific what is not working. What Bluetooth hardware are you using? Do the logfiles or dmesg include anything helpful?
I use a usb dongle, unfortunately included in my laptop, so I can't see any serial number or anything.
I installed a 2.6.8-rc3-mm2 on my development machine and everything works like it should. I tried a RFCOMM connection to my mobile, a HCRP connection to my printer and I used a Bluetooth mouse. All stuff worked perfect.

Seems that I'll have to provide more debug info :-)

Quoted 2 lines

Do "hciconfig -a" show your Bluetooth device? Do "/proc/bus/usb/devices" has an entry for it? Check "dmesg" for any USB related error messages.

BTW I tried a vanilla 2.6.8-rc3, and it works.

under 2.6.8-rc3-mm1 and 2.6.8-rc2-mm2 :

hciconfig -a gives nothing.

dmesg -s 1000000 | grep -i usb :
----
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v2.2
uhci_hcd 0000:00:1d.0: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1 hub 1-0:1.0: USB hub found
uhci_hcd 0000:00:1d.1: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
usbcore: registered new driver ub
hub 2-0:1.0: USB hub found
uhci_hcd 0000:00:1d.2: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3 hub 3-0:1.0: USB hub found
uhci_hcd 0000:00:1d.3: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4 hub 4-0:1.0: USB hub found
usb 3-2: new full speed USB device using address 2
usb 4-2: new full speed USB device using address 2
ehci_hcd 0000:00:1d.7: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5 ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10 hub 5-0:1.0: USB hub found
usb 4-2: can't set config #1, error -71
usb 3-2: USB disconnect, address 2
usb 3-2: new full speed USB device using address 3
usb 3-2: not running at top speed; connect to a high speed hub
usb 4-2: new full speed USB device using address 4
Bluetooth: HCI USB driver ver 2.7
usbcore: registered new driver hci_usb
----

under 2.6.8-rc3 :

hciconfig -a :
----
hci0: Type: USB
BD Address: 00:10:60:A2:F9:30 ACL MTU: 192:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN
RX bytes:24159 acl:1576 sco:0 events:160 errors:0
TX bytes:1221 acl:24 sco:0 commands:52 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'diamant-0'
Class: 0x000100
Service Classes: Unspecified
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x33c LMP Ver: 1.1 (0x1) LMP Subver: 0x33c
Manufacturer: Cambridge Silicon Radio (10)
----

Here is relevant part of a
diff -u proc_bus_usb_devices_2.6.8-rc2-mm2 proc_bus_usb_devices_2.6.8-rc3 :
----

-T:  Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  4 Spd=12  MxCh= 0
+T:  Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
 D:  Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
 P:  Vendor=0a12 ProdID=0001 Rev= 8.28
 C:* #Ifs= 3 Cfg#= 1 Atr=c0 MxPwr=  0mA
-I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=ub
+I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
 E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
 E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
 E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
-I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=ub
+I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
 E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
 E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
-I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=ub
+I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
 E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
 E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
-I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=ub
+I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
 E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
 E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
-I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=ub
+I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
 E:  Ad=03(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
 E:  Ad=83(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms
-I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=ub
+I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
 E:  Ad=03(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
 E:  Ad=83(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms
-I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=ub
+I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
 E:  Ad=03(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms
 E:  Ad=83(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms
-I:  If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=ub
+I:  If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)

----

I have quite same diff ("usb-storage" under -rc3, "ub" under -mm) for my flash reader, which I tested under neither (I don't have any CF/SD card here).

It seems that the wrong driver is used under -mm... After reading bk-usb.patch, I see a new driver ub.c, which I enabled. With CONFIG_BLK_DEV_UB disabled, 2.6.8-rc3-mm2 works.

So... my guess is that 2.6.8-rc2-mm* was broken, but as everything works now in 2.6.8-rc3-mm2 it doesn't matter.

As I understand it, there is a bug in BLK_DEV_UB which make it says it can handle hci devices, which is false. I'll leave BLK_DEV_UB disabled for now.

Hope it helps,

Thanks for your help Marcel,
Stephane.

Signature · 4 lines

 ///  Stephane Jourdois         /"\  ASCII RIBBON CAMPAIGN \\\
(((    Ingénieur développement  \ /    AGAINST HTML MAIL    )))
 \\\   24 rue Cauchy             X                         ///
  \\\  75015  Paris             / \    +33 6 8643 3085    ///

Marcel Holtmann

2004-08-09 16:49 UTC #9 lore raw

Hi Stephane,

Quoted 115 lines

Quoted 2 lines
Do "hciconfig -a" show your Bluetooth device? Do "/proc/bus/usb/devices" has an entry for it? Check "dmesg" for any USB related error messages.
BTW I tried a vanilla 2.6.8-rc3, and it works.
under 2.6.8-rc3-mm1 and 2.6.8-rc2-mm2 :
hciconfig -a gives nothing.
dmesg -s 1000000 | grep -i usb :
----
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v2.2
uhci_hcd 0000:00:1d.0: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1 hub 1-0:1.0: USB hub found
uhci_hcd 0000:00:1d.1: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
usbcore: registered new driver ub
hub 2-0:1.0: USB hub found
uhci_hcd 0000:00:1d.2: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3 hub 3-0:1.0: USB hub found
uhci_hcd 0000:00:1d.3: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4 hub 4-0:1.0: USB hub found
usb 3-2: new full speed USB device using address 2
usb 4-2: new full speed USB device using address 2
ehci_hcd 0000:00:1d.7: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5 ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10 hub 5-0:1.0: USB hub found
usb 4-2: can't set config #1, error -71
usb 3-2: USB disconnect, address 2
usb 3-2: new full speed USB device using address 3
usb 3-2: not running at top speed; connect to a high speed hub
usb 4-2: new full speed USB device using address 4
Bluetooth: HCI USB driver ver 2.7
usbcore: registered new driver hci_usb
----
under 2.6.8-rc3 :
hciconfig -a :
----
hci0: Type: USB
BD Address: 00:10:60:A2:F9:30 ACL MTU: 192:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN
RX bytes:24159 acl:1576 sco:0 events:160 errors:0
TX bytes:1221 acl:24 sco:0 commands:52 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'diamant-0'
Class: 0x000100
Service Classes: Unspecified
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x33c LMP Ver: 1.1 (0x1) LMP Subver: 0x33c
Manufacturer: Cambridge Silicon Radio (10)
----
Here is relevant part of a
diff -u proc_bus_usb_devices_2.6.8-rc2-mm2 proc_bus_usb_devices_2.6.8-rc3 :
----
(quoted diff) +9 ~~-10~~
-T:  Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  4 Spd=12  MxCh= 0
+T:  Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
 D:  Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
 P:  Vendor=0a12 ProdID=0001 Rev= 8.28
 C:* #Ifs= 3 Cfg#= 1 Atr=c0 MxPwr=  0mA
-I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=ub
+I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
 E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
 E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
 E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
-I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=ub
+I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
 E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
 E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
-I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=ub
+I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
 E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
 E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
-I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=ub
+I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
 E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
 E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
-I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=ub
+I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
 E:  Ad=03(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
 E:  Ad=83(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms
-I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=ub
+I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
 E:  Ad=03(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
 E:  Ad=83(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms
-I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=ub
+I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
 E:  Ad=03(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms
 E:  Ad=83(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms
-I:  If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=ub
+I:  If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)
----
I have quite same diff ("usb-storage" under -rc3, "ub" under -mm) for my flash reader, which I tested under neither (I don't have any CF/SD card here).
It seems that the wrong driver is used under -mm... After reading bk-usb.patch, I see a new driver ub.c, which I enabled. With CONFIG_BLK_DEV_UB disabled, 2.6.8-rc3-mm2 works.

Quoted 6 lines

So... my guess is that 2.6.8-rc2-mm* was broken, but as everything works now in 2.6.8-rc3-mm2 it doesn't matter.
As I understand it, there is a bug in BLK_DEV_UB which make it says it can handle hci devices, which is false. I'll leave BLK_DEV_UB disabled for now.

that is the real problem. I never compiled in this new driver. After enabling it the machine did some very weird things. It must be somekind of luck that your system was still working. Mine doesn't. The problem is that the ub driver don't contain the terminating braces for the device id entries. You need to apply the following patch to get everything back to normal.

ub.c 2004-08-09 18:24:15.000000000 +0200 renamed from ub.c.orig 2004-08-09 18:40:38.000000000 +0200 +1 -0

@@ -318,6 +318,7 @@
 static struct usb_device_id ub_usb_ids[] = {
        // { USB_DEVICE_VER(0x0781, 0x0002, 0x0009, 0x0009) },  /* SDDR-31 */
        { USB_INTERFACE_INFO(USB_CLASS_MASS_STORAGE, US_SC_SCSI, US_PR_BULK) },
+       { }
 };
 
 MODULE_DEVICE_TABLE(usb, ub_usb_ids);

Regards

Marcel

Stephane Jourdois

2004-08-09 17:01 UTC #10 lore raw

ub.c 2004-08-09 18:24:15.000000000 +0200 line 324

Quoted 10 lines · Marcel Holtmann

ub.c 2004-08-09 18:24:15.000000000 +0200 renamed from ub.c.orig 2004-08-09 18:40:38.000000000 +0200 +1 -0

@@ -318,6 +318,7 @@
 static struct usb_device_id ub_usb_ids[] = {
        // { USB_DEVICE_VER(0x0781, 0x0002, 0x0009, 0x0009) },  /* SDDR-31 */
        { USB_INTERFACE_INFO(USB_CLASS_MASS_STORAGE, US_SC_SCSI, US_PR_BULK) },
+       { }
 };
 
 MODULE_DEVICE_TABLE(usb, ub_usb_ids);

Works perfectly, indeed.
Thanks.

Signature · 4 lines

 ///  Stephane Jourdois         /"\  ASCII RIBBON CAMPAIGN \\\
(((    Ingénieur développement  \ /    AGAINST HTML MAIL    )))
 \\\   24 rue Cauchy             X                         ///
  \\\  75015  Paris             / \    +33 6 8643 3085    ///

Greg KH

2004-08-09 17:16 UTC #11 lore raw

In reply to Marcel Holtmann

Quoted 6 lines · Marcel Holtmann

that is the real problem. I never compiled in this new driver. After enabling it the machine did some very weird things. It must be somekind of luck that your system was still working. Mine doesn't. The problem is that the ub driver don't contain the terminating braces for the device id entries. You need to apply the following patch to get everything back to normal.

Ah, good catch. Sorry I missed that previously. I've applied your patch to my trees.

thanks again.

greg k-h

Pete Zaitcev

2004-08-09 18:01 UTC #12 lore raw

In reply to Stephane Jourdois

ub.c 2004-08-09 18:24:15.000000000 +0200 line 322

Quoted 8 lines · On Mon, 09 Aug 2004 18:49:05 +0200 Marcel Holtmann <[email protected]> wrote:

ub.c 2004-08-09 18:24:15.000000000 +0200 renamed from ub.c.orig 2004-08-09 18:40:38.000000000 +0200 +1 -0

@@ -318,6 +318,7 @@
 static struct usb_device_id ub_usb_ids[] = {
        // { USB_DEVICE_VER(0x0781, 0x0002, 0x0009, 0x0009) },  /* SDDR-31 */
        { USB_INTERFACE_INFO(USB_CLASS_MASS_STORAGE, US_SC_SCSI, US_PR_BULK) },
+       { }
 };

Tsk, tsk, what a dumb bug. Thanks, Marcel.

-- Pete