USB Sony Clie

[jsummer]

I am having no luck getting my sony clie to sync with anything. I'm currently running a custom compiled 2.67 kernel on Debian unstable. I have a VIA chipset and dual PIII-800. If you need more hardware info it is in the dmesg log. Here is what I get when I press hotsync on the clie in my kern.log

Jul 13 21:56:29 localhost kernel: usb 1-1: new full speed USB device using addre
ss 2
Jul 13 21:56:34 localhost kernel: usb 1-1: control timeout on ep0out
Jul 13 21:56:34 localhost kernel: uhci_hcd 0000:00:07.2: Unlink after no-IRQ? D
ifferent ACPI or APIC settings may help.

I've included the UHCI usb in the kernel, and the visor and usb-serial as modules that I loaded just before pressing the hotsync on the clie.
I've compiled ACPI as a module and left it out because it was giving me boot problems. I wasn't able to find much out about APIC and how to configure it. I know it has to do with the CPU and I believe SMP. I've attached my dmesg debug and kern.log logs. Sorry I had to zip them up, but they were a little big.

Personally I'm at at a dead end here. I can't think of another way to get this to work. Please don't leave me syncing in Windows.

[Shep]

I pretty much have the same setup. I'm running 2.6.3 kernel with debian sarge. Anyways I also have a clie that I got to work using pilot-link and evolution. I have found that to be the best combo out there. Just apt-get pilot-link and evolution. Then start up Evolution, and go through the pilot settings options. I am using /dev/ttyUSB0 to sync, but you may have to use ttyUSB1, just depends. Make sure that you hit the sync button on the PDA before you try to recognize it though evolution. there is great documentation at www.pilot-link.org. Follow the links to using the clie with Evolution.

[Shep]

Give this a try also, great info: http://howto.pilot-link.org/evosync/

[jsummer]

Unfortunately my problem is a layer below software. You see when I hit the hotsync the palm lets the OS know its there, and the OS offers it an address. But either the palm isn't getting the address or isn't responding when it does. So the OS times out the address because it wasn't confirmed. Since the device has no address it can' t be inspect for its type and therefore can't be assigned to a device in the system.

Now I know that it is related to APCI, IRQ's, and or my VIA chipset. I've tried the 2.6.7, 2.6.6, and 2.4.25 kernel, but I haven't had any of them work. I know that they are testing a patch for an APCI USB problem in the kernel next kernel, but I just started to build my own kernel and I'm not exactly comfortable grabbing an experimental patch. The log files that I attached at the beginning contain the useful information.

Thanks again and as soon as I get past this hardware issue I will be looking a lot closer at what you've posted.

Jared

[eslackey]

What Clie version do you have?

I have a TJ37 and I had to modify the code for the visor driver and the code for gnome-pilot to get it to work.
I also had to use some parameters when loading the visor driver.

[jsummer]

The Clie model is a PEG-SJ30/U.

[jsummer]

Well I got it to sync, but with my laptop from work. I think that my home desktop with the VIA chipset is just screwy. I also know that I can't turn on APCI on my home desktop. I would still like to get it to work. but I'm somewhat relieved.