PDA Device Configuration

Thanks for you report. Could you type 'dmesg' in the terminal and see if the
last lines contain anything interesting with regard to yout ipaq? Which version
of Ubuntu do you use?

Sorry for the delay, I was away on a trip.

The livecd I tried is the 5.10 preview for x386 : Ubuntu Linux 5.10: The Breezy
Badger Preview Release

Here is dmesg output:
ubuntu@ubuntu:~$ dmesg
4294669.422000] audit(1129113996.420:0): initialized
[4294669.422000] highmem bounce pool size: 64 pages
[4294669.422000] VFS: Disk quotas dquot_6.5.1
[4294669.422000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[4294669.422000] devfs: 2004-01-31 Richard Gooch (<email address hidden>)
[4294669.422000] devfs: boot_options: 0x0
[4294669.422000] Initializing Cryptographic API
[4294669.423000] isapnp: Scanning for PnP cards...
[4294669.776000] isapnp: No Plug & Play device found
[4294669.791000] PNP: No PS/2 controller found. Probing ports directly.
[4294670.806000] serio: i8042 AUX port at 0x60,0x64 irq 12
[4294670.806000] serio: i8042 KBD port at 0x60,0x64 irq 1
[4294670.806000] Serial: 8250/16550 driver $Revision: 1.90 $ 54 ports, IRQ
sharing enabled
[4294670.807000] ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[4294670.807000] ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[4294670.808000] ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[4294670.809000] ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[4294670.809000] io scheduler noop registered
[4294670.809000] io scheduler anticipatory registered
[4294670.809000] io scheduler deadline registered
[4294670.809000] io scheduler cfq registered
[4294670.809000] RAMDISK driver initialized: 16 RAM disks of 1048576K size 1024
blocksize
[4294670.810000] EISA: Probing bus 0 at eisa.0
[4294670.810000] Cannot allocate resource for EISA slot 4
[4294670.810000] Cannot allocate resource for EISA slot 5
[4294670.810000] EISA: Detected 0 cards.
[4294670.810000] NET: Registered protocol family 2
[4294670.823000] IP: routing cache hash table of 8192 buckets, 64Kbytes
[4294670.823000] TCP established hash table entries: 262144 (order: 9, 2097152
bytes)
[4294670.826000] TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
[4294670.826000] TCP: Hash tables configured (established 262144 bind 65536)
[4294670.826000] NET: Registered protocol family 8
[4294670.826000] NET: Registered protocol family 20
[4294670.826000] ACPI wakeup devices:
[4294670.826000] HUB0 HUB1 USB0 USB1 USB2 F139 MMAC MMCI UAR1
[4294670.826000] ACPI: (supports S0 S1 S4 S4bios S5)
[4294670.827000] RAMDISK: Compressed image found at block 0
[4294671.264000] VFS: Mounted root (ext2 filesystem).
[4294671.265000] VFS: Mounted root (ext2 filesystem).
[4294671.265000] Trying to move old root to /initrd ... okay
[4294671.265000] Freeing unused kernel memory: 224k freed
[4294671.284000] input: AT Translated Set 2 keyboard on isa0060/serio0
[4294671.361000] NET: Registered protocol family 1
[4294672.187000] usbcore: registered new driver usbfs
[4294672.187000] usbcore: registered new driver hub
[4294672.188000] ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI)
Driver (PCI)
[4294672.189000] ACPI: PCI Interrupt Link [APCF] enabled at IRQ 22
[4294672.189000] ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 22
(level, high) -> IRQ 22
[4294672.189000] PCI: Setting latency timer of device 0000:00:02.0 to 64
[4294672.189000] ohci_hcd 0000:00:02.0: nVidia...

what is the output of 'lsusb -v' (instead of lspci) and which usb kernel modules
are loaded (check with 'lsmod|grep usb')? what happens, if you initiate a
hotsync on your device? any difference?

A new version (2.0.14) was uploaded to Edgy. It'd be nice if you had a chance to test this and report back, if the problem still persists.

I haven't used my IPAQ in some time but I will dig it out and give it a test in Edgy. It will probably need to be charged first though.

Thanks for testing it.

Just to keep you updated, I did dig out my IPAQ 2215 and for some odd reason it is stuck in a reboot loop, even after a failed attempt at a soft reset and then a hard reset. Seems also that if I apply pressure at a couple of points it just resets or won't come on. It has been packed in a box since I relocated. I realize this doesn't help you much, but I wanted to let you know what is up so you aren't left hanging like when I originally started this.

The good (and slightly bad) news is that I contacted HP today and while they couldn't help me with their online chat, or again on the phone. They gave me a number to call to see about getting it repaired. It is out of warranty now though so I will call tomorrow and find out the estimate of any repair costs. Hopefully it isn't astronomical. I remember that with some of their printers it was cheaper to buy a new printer then to have an old one serviced (still never figured out the logic in that) :-(

At any rate I will call the repair center tomorrow and I will be sure to let you know the results.

Thanks for all that.

Did you have any luck?

As described in the previous comments, your report lacks the information we need to investigate the problem further. We'll close this report for now - please reopen it if you can give us the missing information.