Bug 4577 - iPAQ model rx3715 is not recognized
Summary: iPAQ model rx3715 is not recognized
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Greg Kroah-Hartman
Depends on:
Blocks: USB
  Show dependency tree
Reported: 2005-05-03 04:11 UTC by Giuseppe Guarnieri
Modified: 2006-02-27 06:15 UTC (History)
1 user (show)

See Also:
Kernel Version:
Tree: Mainline
Regression: ---


Description Giuseppe Guarnieri 2005-05-03 04:11:10 UTC
Distribution: Debian Testing

Hardware Environment:
Notebook Compaq 2120EA
iPAQ rx3715 (connected via USB)

Software Environment:
Gnu C                  3.3.5
Gnu make               3.80
binutils               2.15
util-linux             2.12
mount                  2.12
module-init-tools      3.2-pre1
e2fsprogs              1.35
reiserfsprogs          line
reiser4progs           line
pcmcia-cs              3.2.5
PPP                    2.4.3
Linux C Library        2.3.2
Dynamic linker (ldd)   2.3.2
Procps                 3.2.3
Net-tools              1.60
Kbd                    [opzione...]
Console-tools          0.2.3
Sh-utils               5.2.1
udev                   056
Modules Loaded         cifs rfcomm l2cap bluetooth pcmcia lp binfmt_misc 8250_pnp parport_pc parport 
iptable_filter ip_tables ppp_async ppp_generic slhc crc_ccitt ipaq usbserial natsemi alim15x3 ohci1394 
ieee1394 yenta_socket rsrc_nonstatic pcmcia_core hsfmc97ali hsfserial hsfengine hsfosspec hsfsoar 
8250_pci 8250 serial_core snd_ali5451 snd_ac97_codec nls_iso8859_1 nls_cp437 vfat fat sg sr_mod 
ide_scsi evdev usbhid

Problem Description:
When I try to connect my iPAQ rx3715 to my PC for synchronization, I obtain the following error from the 
ipaq kernel driver:
usb 1-1: new full speed USB device using ohci_hcd and address 5
ipaq 1-1:2.0: PocketPC PDA converter detected
drivers/usb/serial/ipaq.c: active config #2 != 1 ??
ipaq: probe of 1-1:2.0 failed with error -5

Steps to reproduce:
Just connect an iPAQ rx3715 to a PC via USB cable.
Comment 1 Adrian Bunk 2006-01-23 14:22:00 UTC
Is this issue still present in kernel 2.6.16-rc1?
Comment 2 Giuseppe Guarnieri 2006-01-24 01:47:01 UTC
I don't know, I haven't that kernel version. I'll try and report as soon as 
possible (probably this week-end).
Comment 3 Giuseppe Guarnieri 2006-02-27 05:01:30 UTC
I had problems with my linux box during these days... Now I've compiled that 
kernel version, and seems the problem ah been resolved.

Note You need to log in before you can comment on or make changes to this bug.