[Bluez-users] IOGear GBU301 and Kernel 2.4.20

[Bluez-users] IOGear GBU301 and Kernel 2.4.20

[Tom Watson]

Well...
I have attempted to get all the modules functional, but appear to have
a problem.  Somehow the driver hci_usb doesn't get connected to the
USB device.  I print out the USB driver info (/proc/bus/usb/devices) and
get ...Cls=e0(Unk.  )... where is should get 'hci_usb' as I see it.

Any other reference to 'hci0' (as in 'hciconfig hco0 up') fails since
it can't find the device.

Is there something in the hotplug configuration that I'm missing, or
something even more obvious (but not to me!).

Any help is nice.  Ask a question, and I should be able to answer
what I've done.

Thanks....
-- 
Tom Watson         Generic short signature
tsw@johana.com     (I'm at home now)


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] IOGear GBU301 and Kernel 2.4.20

[Marcel Holtmann]

Hi Tom,

> I have attempted to get all the modules functional, but appear to have
> a problem.  Somehow the driver hci_usb doesn't get connected to the
> USB device.  I print out the USB driver info (/proc/bus/usb/devices) and
> get ...Cls=e0(Unk.  )... where is should get 'hci_usb' as I see it.
> 
> Any other reference to 'hci0' (as in 'hciconfig hco0 up') fails since
> it can't find the device.
> 
> Is there something in the hotplug configuration that I'm missing, or
> something even more obvious (but not to me!).
> 
> Any help is nice.  Ask a question, and I should be able to answer
> what I've done.

why don't include the content of /proc/bus/usb/devices?

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] IOGear GBU301 and Kernel 2.4.20

[Marcel Holtmann]

Hi Tom,

> > why don't include the content of /proc/bus/usb/devices?
> > 
> Your wish is my command....
> 
> >>>>>
> T:  Bus=03 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#=  5 Spd=12  MxCh= 0
> D:  Ver= 1.01 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
> P:  Vendor=0a5c ProdID=2033 Rev= 0.a0
> C:* #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr=100mA
> I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
> E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
> I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> E:  Ad=83(I) Atr=01(Isoc) MxPS=  16 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=  16 Ivl=1ms
> I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> E:  Ad=83(I) Atr=01(Isoc) MxPS=  32 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=  32 Ivl=1ms
> I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> E:  Ad=83(I) Atr=01(Isoc) MxPS=  32 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=  32 Ivl=1ms
> I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
> E:  Ad=84(I) Atr=02(Bulk) MxPS=  32 Ivl=0ms
> E:  Ad=04(O) Atr=02(Bulk) MxPS=  32 Ivl=0ms
> <<<<<
> 
> The above is just the part that is different between plugging in the IOGear
> adapter and not.  I didn't want to complicate things with too much clutter

this is a Broadcom BCM2033 dongle without firmware loaded. Install the
bluez-firmware package and use the bcm203x kernel driver from a recent
2.6 kernel or compile bluez-utils-2.9 with bcm203x support.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] IOGear GBU301 and Kernel 2.4.20

[Tom Watson]

Hello Marcel...
The saga continues...
--- Marcel Holtmann <marcel@holtmann.org> wrote:

> Hi Tom,
> 
> > > why don't include the content of /proc/bus/usb/devices?
> > > 
> > Your wish is my command....
> > 
> > >>>>>
> > T:  Bus=03 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#=  5 Spd=12  MxCh= 0
> > D:  Ver= 1.01 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
> > P:  Vendor=0a5c ProdID=2033 Rev= 0.a0
> > C:* #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr=100mA
> > I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> > E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
> > E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> > E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> > I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> > E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
> > E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
> > I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> > E:  Ad=83(I) Atr=01(Isoc) MxPS=  16 Ivl=1ms
> > E:  Ad=03(O) Atr=01(Isoc) MxPS=  16 Ivl=1ms
> > I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> > E:  Ad=83(I) Atr=01(Isoc) MxPS=  32 Ivl=1ms
> > E:  Ad=03(O) Atr=01(Isoc) MxPS=  32 Ivl=1ms
> > I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> > E:  Ad=83(I) Atr=01(Isoc) MxPS=  32 Ivl=1ms
> > E:  Ad=03(O) Atr=01(Isoc) MxPS=  32 Ivl=1ms
> > I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> > E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> > E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> > I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> > E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> > E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> > I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
> > E:  Ad=84(I) Atr=02(Bulk) MxPS=  32 Ivl=0ms
> > E:  Ad=04(O) Atr=02(Bulk) MxPS=  32 Ivl=0ms
> > <<<<<
> > 
> > The above is just the part that is different between plugging in the IOGear
> > adapter and not.  I didn't want to complicate things with too much clutter
> 
> this is a Broadcom BCM2033 dongle without firmware loaded. Install the
> bluez-firmware package and use the bcm203x kernel driver from a recent
> 2.6 kernel or compile bluez-utils-2.9 with bcm203x support.
> 
> Regards
> 
> Marcel
> 

OK, This ought to be simple but...
[ bluez-utils-2.9]# ./configure --prefix=/usr --mandir=/usr/share/man
--sysconfdir=/etc --enable-bcm203x

Then...
make clean    {I hadn't done the 'enable-bcm...'}

and then
make

But it goes for a while and I get...
gcc -DHAVE_CONFIG_H -I. -I. -I..    -I/usr/include -Wall -g -O2 -c `test -f
'bcm203x.c' || echo './'`bcm203x.c
cc1: warning: changing search order for system directory "/usr/include"
cc1: warning:   as it has already been specified as a non-system directory
bcm203x.c: In function `load_firmware':
bcm203x.c:118: warning: implicit declaration of function `usb_interrupt_read'
gcc -I/usr/include -Wall -g -O2   -o bcm203x  bcm203x.o -L/usr/lib -lusb
bcm203x.o: In function `load_firmware':
...../bluez-utils-2.9/extra/bcm203x.c:118: undefined reference to
`usb_interrupt_read'
...../bluez-utils-2.9/extra/bcm203x.c:133: undefined reference to
`usb_interrupt_read'

This doesn't look too good.  Am I doing something wrong here??

Thanks.

=====
-- 
Tom Watson
tsw@johana.com


		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 

Re: [Bluez-users] IOGear GBU301 and Kernel 2.4.20

[Marcel Holtmann]

Hi Tom,

> > this is a Broadcom BCM2033 dongle without firmware loaded. Install the
> > bluez-firmware package and use the bcm203x kernel driver from a recent
> > 2.6 kernel or compile bluez-utils-2.9 with bcm203x support.
> > 
> OK, This ought to be simple but...
> [ bluez-utils-2.9]# ./configure --prefix=/usr --mandir=/usr/share/man
> --sysconfdir=/etc --enable-bcm203x
> 
> Then...
> make clean    {I hadn't done the 'enable-bcm...'}
> 
> and then
> make
> 
> But it goes for a while and I get...
> gcc -DHAVE_CONFIG_H -I. -I. -I..    -I/usr/include -Wall -g -O2 -c `test -f
> 'bcm203x.c' || echo './'`bcm203x.c
> cc1: warning: changing search order for system directory "/usr/include"
> cc1: warning:   as it has already been specified as a non-system directory
> bcm203x.c: In function `load_firmware':
> bcm203x.c:118: warning: implicit declaration of function `usb_interrupt_read'
> gcc -I/usr/include -Wall -g -O2   -o bcm203x  bcm203x.o -L/usr/lib -lusb
> bcm203x.o: In function `load_firmware':
> ...../bluez-utils-2.9/extra/bcm203x.c:118: undefined reference to
> `usb_interrupt_read'
> ...../bluez-utils-2.9/extra/bcm203x.c:133: undefined reference to
> `usb_interrupt_read'
> 
> This doesn't look too good.  Am I doing something wrong here??

you must install the development package of the USB library.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] IOGear GBU301 and Kernel 2.4.20

[Bc. Michal Semler]

> you must install the development package of the USB library.

Marcel shouldn't configure script find these missing libs?

M.

>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] IOGear GBU301 and Kernel 2.4.20

[Marcel Holtmann]

Hi Michal,

> > you must install the development package of the USB library.
> 
> Marcel shouldn't configure script find these missing libs?

it does this, but of course you must have installed them. If not it will
disable the compilation of that program.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] IOGear GBU301 and Kernel 2.4.20

[Bc. Michal Semler]

Dne po 9. srpna 2004 08:30 jste napsal(a):
> Hi Michal,
>
> > > you must install the development package of the USB library.
> >
> > Marcel shouldn't configure script find these missing libs?
>
> it does this, but of course you must have installed them. If not it will
> disable the compilation of that program.

He wrote, that he --enable-bcm203x - so configure should fail when by hand 
enabled and libs not available

M.

>
> Regards
>
> Marcel


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] IOGear GBU301 and Kernel 2.4.20

[Marcel Holtmann]

Hi Michal,

> > > > you must install the development package of the USB library.
> > >
> > > Marcel shouldn't configure script find these missing libs?
> >
> > it does this, but of course you must have installed them. If not it will
> > disable the compilation of that program.
> 
> He wrote, that he --enable-bcm203x - so configure should fail when by hand 
> enabled and libs not available

configure will not fail. It only fails when the Bluetooth library is not
present. The point is even if configure won't compile a specific part,
you still can do Makefile tricks to compile it (call "make bcm203x").

On the other hand it can be possible that his USB library is simply too
old. If this is the problem I must adjust the configure check.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] IOGear GBU301 and Kernel 2.4.20

[Marcel Holtmann]

Hi Tom,

> > > > this is a Broadcom BCM2033 dongle without firmware loaded. Install the
> > > > bluez-firmware package and use the bcm203x kernel driver from a recent
> > > > 2.6 kernel or compile bluez-utils-2.9 with bcm203x support.
> > > > 
> > > OK, This ought to be simple but...
> > > [ bluez-utils-2.9]# ./configure --prefix=/usr --mandir=/usr/share/man
> > > --sysconfdir=/etc --enable-bcm203x
> > > 
> > > Then...
> > > make clean    {I hadn't done the 'enable-bcm...'}
> > > 
> > > and then
> > > make
> > > 
> > > But it goes for a while and I get...
> > > gcc -DHAVE_CONFIG_H -I. -I. -I..    -I/usr/include -Wall -g -O2 -c `test -f
> > > 'bcm203x.c' || echo './'`bcm203x.c
> > > cc1: warning: changing search order for system directory "/usr/include"
> > > cc1: warning:   as it has already been specified as a non-system directory
> > > bcm203x.c: In function `load_firmware':
> > > bcm203x.c:118: warning: implicit declaration of function `usb_interrupt_read'
> > > gcc -I/usr/include -Wall -g -O2   -o bcm203x  bcm203x.o -L/usr/lib -lusb
> > > bcm203x.o: In function `load_firmware':
> > > ...../bluez-utils-2.9/extra/bcm203x.c:118: undefined reference to
> > > `usb_interrupt_read'
> > > ...../bluez-utils-2.9/extra/bcm203x.c:133: undefined reference to
> > > `usb_interrupt_read'
> > > 
> > > This doesn't look too good.  Am I doing something wrong here??
> > 
> > you must install the development package of the USB library.
> > 
> 
> Well, I thought I had installed it.  I've got a RedHat system and I
> installed 'libusb-devel-0.1.6-3.i386.rpm' (from RH9.0 CD set).  I then
> again attempted the 'make' to only get the same results (no routine
> 'usb_interrupt_read').
> 
> Hopefully I haven't done anything more silly.
> I looked in /usr/lib and saw 'libusb.a' is this the correct library module?
> 
> If not, where should it be, and its name??

I never checked this before, but it seems that you need at least version
0.1.8 of that library. Prior versions don't have support for reading
from interrupt endpoints.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] IOGear GBU301 and Kernel 2.4.20

[Marcel Holtmann]

Hi Tom,

> > > > this is a Broadcom BCM2033 dongle without firmware loaded. Install the
> > > > bluez-firmware package and use the bcm203x kernel driver from a recent
> > > > 2.6 kernel or compile bluez-utils-2.9 with bcm203x support.
> > > > 
> 
> Well, I did compile bluez-utils (and installed it) as well as bluez-firmware. 
> That now seems to go well.  Now when I plug in the dongle I get the following
> in '/var/log/messages':
> Aug  9 16:00:02 xyzzy kernel: hub.c: new USB device 00:10.1-2, assigned address
> 6
> Aug  9 16:00:02 xyzzy kernel: usb.c: USB device 6 (vend/prod 0xa5c/0x2033) is
> not claimed by any active driver.
> Aug  9 16:00:05 xyzzy /etc/hotplug/usb.agent: Setup hci_usb for USB product
> a5c/2033/a0
> 
> But I still get the following in /proc/bus/usb/devices
> >>>>>
> < T:  Bus=03 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#=  7 Spd=12  MxCh= 0
> < D:  Ver= 1.01 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
> < P:  Vendor=0a5c ProdID=2033 Rev= 0.a0
> < C:* #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr=100mA
> < I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> < E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
> < E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> < E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> < I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> < E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
> < E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
> < I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> < E:  Ad=83(I) Atr=01(Isoc) MxPS=  16 Ivl=1ms
> < E:  Ad=03(O) Atr=01(Isoc) MxPS=  16 Ivl=1ms
> < I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> < E:  Ad=83(I) Atr=01(Isoc) MxPS=  32 Ivl=1ms
> < E:  Ad=03(O) Atr=01(Isoc) MxPS=  32 Ivl=1ms
> < I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> < E:  Ad=83(I) Atr=01(Isoc) MxPS=  32 Ivl=1ms
> < E:  Ad=03(O) Atr=01(Isoc) MxPS=  32 Ivl=1ms
> < I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> < E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> < E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> < I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> < E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> < E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> < I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
> < E:  Ad=84(I) Atr=02(Bulk) MxPS=  32 Ivl=0ms
> < E:  Ad=04(O) Atr=02(Bulk) MxPS=  32 Ivl=0ms
> <<<<<
> 
> Do I need to add something to load the firmware into the dongle??
> It appears that the ...utils... added something to the hotplug stuff for the
> broadcom chipset, and it should work.  Obviously it isn't.

I thought this was already answered. You must use --enable-bcm203x to
compile the firmware loader. After installation you will see

        /etc/hotplug/usb/bcm203x.usermap
        /etc/hotplug/usb/bcm203x

in the hotplug directories. Maybe your hotplug scripts are too old and
they can't work with extra entries under /etc/hotplug/usb/.

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

Re: [Bluez-users] IOGear GBU301 and Kernel 2.4.20

[Marcel Holtmann]

Hi Tom,

> > in the hotplug directories. Maybe your hotplug scripts are too old and
> > they can't work with extra entries under /etc/hotplug/usb/.
> 
> As for the hotplug scripts, the one named 'usb.agent' is at version 1.12
> dated:  2002/4/1.  Is that sufficient.  The other files (usb.rc among
> them) seem to be of similar vintage.  It seems that this version of the
> 'usb.agent' does not check/load from usermap files in the usb directory.
> That appears to be the problem.  I have since upgraded to a later version
> of the script (1.41 dated 2004/04/01) which seems to go into the usb
> directory to get usermap's.  I'll try this to see what happens.

I have these on my Debian Sid machine and everything is working

	$Id: usb.agent,v 1.39 2004/03/26 22:36:38 kroah Exp $
	$Id: usb.rc,v 1.22 2004/03/27 07:44:39 ukai Exp $

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