hello
i made an kernelupdate 2.2.16 to 2.4.2 and i am using RH 7.0
with the 2.2.16 kernel the usb-visor communication works perfekt.
now with the 2.4.2 kernel my usb does want to connect to my handspring-visor
#dmesg
...
usb.c: registered new driver hub
uhci.c: USB UHCI at I/O 0xd400, IRQ 9
uhci.c: detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
uhci: host controller process error. something bad happened
uhci: host controller halted. very bad
hub.c: USB hub found
hub.c: 2 ports detected
uhci.c: USB UHCI at I/O 0xd800, IRQ 9
uhci.c: detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
uhci: host controller halted. very bad
uhci: host controller process error. something bad happened
uhci: host controller halted. very bad
hub.c: USB hub found
hub.c: 2 ports detected
mice: PS/2 mouse device common for all mice
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 16384)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 216k freed
uhci.c: root-hub INT complete: port1: 58a port2: 58a data: 6
uhci.c: root-hub INT complete: port1: 58a port2: 58a data: 6
uhci.c: root-hub INT complete: port1: 588 port2: 588 data: 6
uhci.c: root-hub INT complete: port1: 588 port2: 588 data: 6
Adding Swap: 136512k swap-space (priority -1)
#
this sounds a little strange to me.
next thing:
#/sbin/modprobe visor
# /sbin/lsmod
Module Size Used by
visor 4784 0 (unused)
usbserial 12896 0 [visor]
#
# tail -f /var/log/messages
...
Apr 8 23:24:57 horus kernel: usbserial.c: USB Serial support registered
for Generic
Apr 8 23:24:57 horus kernel: usb.c: registered new driver serial
Apr 8 23:24:57 horus kernel: usbserial.c: USB Serial support registered
for Handspring Visor
now i want to sync an i pressed the sync button (2 times):
#tail -f /var/log/message
...Apr 8 23:24:57 horus kernel: usbserial.c: USB Serial support registered
for Generic
Apr 8 23:24:57 horus kernel: usb.c: registered new driver serial
Apr 8 23:24:57 horus kernel: usbserial.c: USB Serial support registered
for Handspring Visor
Apr 8 23:25:30 horus kernel: hub.c: USB new device connect on bus1/1,
assigned device number 3
Apr 8 23:25:33 horus kernel: usb_control/bulk_msg: timeout
Apr 8 23:25:33 horus kernel: usb.c: USB device not accepting new
address=3 (error=-110)
Apr 8 23:25:33 horus kernel: hub.c: USB new device connect on bus1/1,
assigned device number 4
Apr 8 23:25:36 horus kernel: usb_control/bulk_msg: timeout
Apr 8 23:25:36 horus kernel: usb.c: USB device not accepting new
address=4 (error=-110)
Apr 8 23:26:25 horus PAM_unix[909]: (system-auth) session opened for
user root by (uid=500)
Apr 8 23:33:09 horus kernel: hub.c: USB new device connect on bus1/1,
assigned device number 5
Apr 8 23:33:12 horus kernel: usb_control/bulk_msg: timeout
Apr 8 23:33:12 horus kernel: usb.c: USB device not accepting new
address=5 (error=-110)
Apr 8 23:33:13 horus kernel: hub.c: USB new device connect on bus1/1,
assigned device number 6
Apr 8 23:33:16 horus kernel: usb_control/bulk_msg: timeout
Apr 8 23:33:16 horus kernel: usb.c: USB device not accepting new
address=6 (error=-110)
#cat /proc/interrupts
CPU0
0: 23126 XT-PIC timer
1: 468 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 7624 XT-PIC es1371
7: 0 XT-PIC parport0
9: 2 XT-PIC usb-uhci, usb-uhci
11: 0 XT-PIC eth0
12: 8030 XT-PIC PS/2 Mouse
14: 9979 XT-PIC ide0
15: 9 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
#
# /sbin/lspci -v
...
00:07.2 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 10)
(prog-if 00 [UHCI])
Subsystem: Unknown device 0925:1234
Flags: bus master, medium devsel, latency 32, IRQ 9
I/O ports at d400 [size=32]
Capabilities: [80] Power Management version 2
00:07.3 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 10)
(prog-if 00 [UHCI])
Subsystem: Unknown device 0925:1234
Flags: bus master, medium devsel, latency 32, IRQ 9
I/O ports at d800 [size=32]
Capabilities: [80] Power Management version 2
...
thanks for any help
juergen
> Apr 8 23:33:09 horus kernel: hub.c: USB new device connect on bus1/1,
> assigned device number 5
> Apr 8 23:33:12 horus kernel: usb_control/bulk_msg: timeout
> Apr 8 23:33:12 horus kernel: usb.c: USB device not accepting new
> address=5 (error=-110)
Funny, I've been getting the same messages (on 2.4.0 and now 2.4.3) for a
while now, and I thought the problem was with my Visor. (...I haven't
been able to sync for months...)
John
--
# John Madden [email protected] ICQ: 2EB9EA
# FreeLists, Free mailing lists for all: http://www.freelists.org
# UNIX Systems Engineer, Ivy Tech State College: http://www.ivy.tec.in.us
# Linux, Apache, Perl and C: All the best things in life are free!
On Wed, Apr 11, 2001 at 08:52:30AM -0500, John Madden wrote:
> > Apr 8 23:33:09 horus kernel: hub.c: USB new device connect on bus1/1,
> > assigned device number 5
> > Apr 8 23:33:12 horus kernel: usb_control/bulk_msg: timeout
> > Apr 8 23:33:12 horus kernel: usb.c: USB device not accepting new
> > address=5 (error=-110)
>
> Funny, I've been getting the same messages (on 2.4.0 and now 2.4.3) for a
> while now, and I thought the problem was with my Visor. (...I haven't
> been able to sync for months...)
Have you tried using the normal UHCI driver, instead of the UHCI
Alternate Driver (JE)? I know the "alternate" one is default from
Linus, but it's incompatible with the usb-visor driver. The
maintainer said he'd patch the docs to clear up the confusion, but it
hasn't shown up in the mainstream kernels yet.
In my case, trying to use the visor would actually lock up the
machine, requiring a cold boot. Switched to the other UHCI driver
and it works fine.
Erik
Erik DeBill [[email protected]] wrote:
> On Wed, Apr 11, 2001 at 08:52:30AM -0500, John Madden wrote:
> > > Apr 8 23:33:09 horus kernel: hub.c: USB new device connect on bus1/1,
> > > assigned device number 5
> > > Apr 8 23:33:12 horus kernel: usb_control/bulk_msg: timeout
> > > Apr 8 23:33:12 horus kernel: usb.c: USB device not accepting new
> > > address=5 (error=-110)
> >
> > Funny, I've been getting the same messages (on 2.4.0 and now 2.4.3) for a
> > while now, and I thought the problem was with my Visor. (...I haven't
> > been able to sync for months...)
>
> Have you tried using the normal UHCI driver, instead of the UHCI
> Alternate Driver (JE)? I know the "alternate" one is default from
> Linus, but it's incompatible with the usb-visor driver. The
> maintainer said he'd patch the docs to clear up the confusion, but it
> hasn't shown up in the mainstream kernels yet.
I've also been seeing these messages (for a very, very long time), with
both the uhci and usb-uhci drivers, with many different devices (not
just visor). Usually the only way to fix it is to have the usb stuff
compiled as modules, remove it all, and the re-insmod it all. Then it
works again for a little while...
There really needs to be only one driver. It's just confusing.
> In my case, trying to use the visor would actually lock up the
> machine, requiring a cold boot. Switched to the other UHCI driver
> and it works fine.
Never had to reboot though...on either x86 or alpha with UHCI...
Cheers,
-- Bob
Bob McElrath ([email protected])
Univ. of Wisconsin at Madison, Department of Physics
> Have you tried using the normal UHCI driver, instead of the UHCI
> Alternate Driver (JE)? I know the "alternate" one is default from
> Linus, but it's incompatible with the usb-visor driver. The
> maintainer said he'd patch the docs to clear up the confusion, but it
> hasn't shown up in the mainstream kernels yet.
I've only used the UHCI, actually.
Given that I've had syncing problems on and off since I was running
2.2.16, I think that this is a defective unit, and not the kernel's fault.
John
--
# John Madden [email protected] ICQ: 2EB9EA
# FreeLists, Free mailing lists for all: http://www.freelists.org
# UNIX Systems Engineer, Ivy Tech State College: http://www.ivy.tec.in.us
# Linux, Apache, Perl and C: All the best things in life are free!