Jump to content

Palm Tungsten T3 Not Seen


Padma
 Share

Recommended Posts

Okay. I had this working in MDK 10.0. I needed to re-partion/reformat my HD due to a Windows problem, so I figured I would install a clean 10.1 system rather than upgrade, while I was at it. I installed 10.1 CE, pointed urpmi to the 10.1 OE mirrors, and went to town. Everything works! :D

 

Except my Palm.

 

I no longer have a "/dev/pilot" file, and I haven't been able to figure out which device it is really using (USB cradle).

 

WHen I start KPilot, and press the Hotsync button on the cradle, I get the following in /var/log/messages:

Message from syslogd@localhost at Thu Nov 11 16:33:07 2004 ...
localhost kernel: Disabling IRQ #21
Nov 11 16:33:07 localhost kernel: irq 21: nobody cared!
Nov 11 16:33:07 localhost kernel:  [dump_stack+30/32] dump_stack+0x1e/0x20
Nov 11 16:33:07 localhost kernel:  [<c0107bfe>] dump_stack+0x1e/0x20
Nov 11 16:33:07 localhost kernel:  [__report_bad_irq+43/144] __report_bad_irq+0x2b/0x90
Nov 11 16:33:07 localhost kernel:  [<c01090ab>] __report_bad_irq+0x2b/0x90
Nov 11 16:33:07 localhost kernel:  [note_interrupt+144/176] note_interrupt+0x90/0xb0
Nov 11 16:33:07 localhost kernel:  [<c01091c0>] note_interrupt+0x90/0xb0
Nov 11 16:33:07 localhost kernel:  [do_IRQ+224/256] do_IRQ+0xe0/0x100
Nov 11 16:33:07 localhost kernel:  [<c0109430>] do_IRQ+0xe0/0x100
Nov 11 16:33:07 localhost kernel:  [common_interrupt+24/32] common_interrupt+0x18/0x20
Nov 11 16:33:07 localhost kernel:  [<c010778c>] common_interrupt+0x18/0x20
Nov 11 16:33:07 localhost kernel:  [cpu_idle+45/64] cpu_idle+0x2d/0x40
Nov 11 16:33:07 localhost kernel:  [<c01050ed>] cpu_idle+0x2d/0x40
Nov 11 16:33:07 localhost kernel:  [start_kernel+388/448] start_kernel+0x184/0x1c0
Nov 11 16:33:07 localhost kernel:  [<c0364824>] start_kernel+0x184/0x1c0
Nov 11 16:33:07 localhost kernel:  [L6+0/2] 0xc010019f
Nov 11 16:33:07 localhost kernel:  [<c010019f>] 0xc010019f
Nov 11 16:33:07 localhost kernel: handlers:
Nov 11 16:33:07 localhost kernel: [pg0+543649664/1069613056] (usb_hcd_irq+0x0/0x70 [usbcore])
Nov 11 16:33:07 localhost kernel: [<e0a64f80>] (usb_hcd_irq+0x0/0x70 [usbcore])
Nov 11 16:33:07 localhost kernel: [pg0+543649664/1069613056] (usb_hcd_irq+0x0/0x70 [usbcore])
Nov 11 16:33:07 localhost kernel: [<e0a64f80>] (usb_hcd_irq+0x0/0x70 [usbcore])
Nov 11 16:33:07 localhost kernel: [pg0+543649664/1069613056] (usb_hcd_irq+0x0/0x70 [usbcore])
Nov 11 16:33:07 localhost kernel: [<e0a64f80>] (usb_hcd_irq+0x0/0x70 [usbcore])
Nov 11 16:33:07 localhost kernel: Disabling IRQ #21
Nov 11 16:33:07 localhost kernel: usb 3-2: new full speed USB device using address 2
Nov 11 16:33:12 localhost kernel: usb 3-2: control timeout on ep0out
Nov 11 16:33:17 localhost kernel: usb 3-2: control timeout on ep0out
Nov 11 16:33:18 localhost kernel: usb 3-2: device not accepting address 2, error -110
Nov 11 16:33:18 localhost kernel: usb 3-2: new full speed USB device using address 3
Nov 11 16:33:23 localhost kernel: usb 3-2: control timeout on ep0out
Nov 11 16:33:28 localhost kernel: usb 3-2: control timeout on ep0out
Nov 11 16:33:28 localhost kernel: usb 3-2: device not accepting address 3, error -110
Nov 11 16:34:24 localhost kernel: usb 3-2: new full speed USB device using address 4
Nov 11 16:34:29 localhost kernel: usb 3-2: control timeout on ep0out

ANybody have any ideas?

 

[moved from Hardware by spinynorman]

Edited by Padma
Link to comment
Share on other sites

Thanks, Gowator. :)

 

Unfortunately, it didn't work. (And I swear! I did a 'modprobe visor' earlier. But I had to do it again.)

 

I have a 'tail -f /var/log/messages' running, but I don't see any sign that it is trying to work. :confused:

Link to comment
Share on other sites

Im struggling with my Zire72 but that's becuase its not supported in the module and I need to edit and recompile and haven't got round to it but it is being recognised I just can't synch it....

 

I tail -f the dmesg and it shows when its plugged in.....it assigns it 2x ttyUSB and indeed keeps assigning new ones the more I try and synch....

 

pressing the synch with it connected though does cause a response just not a useful one for me?

Link to comment
Share on other sites

...it assigns it 2x ttyUSB....

And there is the hub of my problem - under 10.0, I had a ttyUSB0 that it connected through. Now, in 10.1, I can't find what it is using. :wall:

 

(I'll have to try doing a 'tail -f dmesg'.)

Link to comment
Share on other sites

  • 5 weeks later...

It's been a month, so I'm bumping this. I am running 10.1 Official.

 

I rebooted, and unplugged my Palm cradle from the USB port before I booted up. Once it was up, I plugged in my cradle, and tried to connect via kpilot/hotsync. Here is the relevent portion of dmesg output:

 

usb 3-1: new full speed USB device using address 2

irq 21: nobody cared!

[<c0107bfe>] dump_stack+0x1e/0x20

[<c01090ab>] __report_bad_irq+0x2b/0x90

[<c01091c0>] note_interrupt+0x90/0xb0

[<c0109430>] do_IRQ+0xe0/0x100

[<c010778c>] common_interrupt+0x18/0x20

handlers:

[<e0a65f80>] (usb_hcd_irq+0x0/0x70 [usbcore])

[<e0a65f80>] (usb_hcd_irq+0x0/0x70 [usbcore])

[<e0a65f80>] (usb_hcd_irq+0x0/0x70 [usbcore])

Disabling IRQ #21

drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic

usbcore: registered new driver usbserial_generic

usbcore: registered new driver usbserial

drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0

drivers/usb/serial/usb-serial.c: USB Serial support registered for Handspring Visor / Palm OS

drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 3.5

drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 5.0

usb 3-1: control timeout on ep0in

usb 3-1: palm_os_4_probe - error -110 getting connection info

visor 3-1:1.0: Handspring Visor / Palm OS converter detected

usb 3-1: Handspring Visor / Palm OS converter now attached to ttyUSB0

usb 3-1: Handspring Visor / Palm OS converter now attached to ttyUSB1

usbcore: registered new driver visor

drivers/usb/serial/visor.c: USB HandSpring Visor / Palm OS driver v2.1

usb 3-1: control timeout on ep0in

usb 3-1: control timeout on ep0in

usb 3-1: string descriptor 0 read error: -110

usb 3-1: control timeout on ep0in

usb 3-1: control timeout on ep0in

usb 3-1: string descriptor 0 read error: -110

usb 3-1: control timeout on ep0in

usb 3-1: control timeout on ep0in

usb 3-1: control timeout on ep0in

usb 3-1: string descriptor 0 read error: -110

usb 3-1: control timeout on ep0in

usb 3-1: control timeout on ep0in

usb 3-1: control timeout on ep0in

usb 3-1: string descriptor 0 read error: -110

usb 3-1: control timeout on ep0in

usb 3-1: control timeout on ep0in

usb 3-1: control timeout on ep0in

usb 3-1: string descriptor 0 read error: -110

usb 3-1: control timeout on ep0in

usb 3-1: control timeout on ep0in

usb 3-1: control timeout on ep0in

usb 3-1: string descriptor 0 read error: -110

usb 3-1: USB disconnect, address 2

visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0

visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1

visor 3-1:1.0: device disconnected

 

Kpilot never saw it to connect. I never saw /dev/ttyUSBx in /dev. I think it would be stupid to have to reinstall Windows just to be able to hotsync my Palm. Anybody have any ideas?

Link to comment
Share on other sites

Guest contemplativery

Padma, I have an issue open at mandrakeexperts.com on this and hopefully somebody will get back with me. If they do, I'll post any information I find here.

 

I agree with you that it's absurd to switch back to windows just to be able sync my palm, but I can't live with out being able to use my pda. It's very frustrating, especially knowing now that it was working under 10.0. These things are supposed to get better not worse with each version. Oh well.

Edited by contemplativery
Link to comment
Share on other sites

Guest contemplativery

My problem, very similar to this, was solved by turning on ACPI in the bootloader (LILO) settings in Mandrake 10.1. ACPI has to do with power management on laptops (I'm using an Averatec 3200).

 

For some reason, ACPI being turned off was keeping all USB devices from being recognized.

 

Once I fixed this, the Tungsten C was immediately recognized and synced easily with KPilot.

Link to comment
Share on other sites

Guest fredgoya
My problem, very similar to this, was solved by turning on ACPI in the bootloader (LILO) settings in Mandrake 10.1.  ACPI has to do with power management on laptops (I'm using an Averatec 3200).

 

Actually, I think you mean 'APIC', which is what I was going to post this morning. I had the exact same problem and fixed it last night by checking the "force no APIC" setting for the default boot.

 

APIC, I believe, stands for "Advanced Programmable Interrupt Controller", and has something to do with the auto-allocation of IRQs to events and/or hardware. Maybe linux and/or Mandrakelinux's implementation of the APIC handling code doesn't play nice with some USB chipsets?

 

FYI, checking that setting also fixed my SD/CF card reader/writer, which wasn't working under 10.1 either.

Link to comment
Share on other sites

Thenks, contemplativery and fredgoya, :D

 

I will try the "force no APIC" first when I get home. It sounds more likely to me (since I am not on a laptop). If it doesn't help, I'll give the ACPI a try. :)

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...