[Bug 70165] Re: Palm/Treo Not Talking to Kernel (2.6.17)

2008-06-05 Thread Chip Rosenthal
With 8.04, I can communicate fine with the Samsung i500 using device usb: -- Palm/Treo Not Talking to Kernel (2.6.17) https://bugs.launchpad.net/bugs/70165 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubun

[Bug 70165] Re: Palm/Treo Not Talking to Kernel (2.6.17)

2008-06-05 Thread Nattgew
Thanks for the update. I'll set this to invalid. Feel free to report any bugs in the future. ** Changed in: linux-source-2.6.17 (Ubuntu) Status: New => Invalid -- Palm/Treo Not Talking to Kernel (2.6.17) https://bugs.launchpad.net/bugs/70165 You received this bug notification because yo

[Bug 70165] Re: Palm/Treo Not Talking to Kernel (2.6.17)

2008-06-05 Thread Nattgew
Can you confirm this bug as still present in the latest kernel version in Hardy? -- Palm/Treo Not Talking to Kernel (2.6.17) https://bugs.launchpad.net/bugs/70165 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing li

[Bug 70165] Re: Palm/Treo Not Talking to Kernel (2.6.17)

2007-04-26 Thread Gregor Rosenauer
same here, Palm Tungsten C stopped working in Feisty but worked fine in Edgy. Also upgrading to Gutsy Gibbon kernel 2.6.22 did not help, but modprobing visor did - thanks for the tip! Added to /etc/modules as a workaround. -- Palm/Treo Not Talking to Kernel (2.6.17) https://bugs.launchpad.net/bu

[Bug 70165] Re: Palm/Treo Not Talking to Kernel (2.6.17)

2007-04-13 Thread Chip Rosenthal
Whups, I just re-read that this bug is issued against Edgy. My problem was with Feisty. -- Palm/Treo Not Talking to Kernel (2.6.17) https://bugs.launchpad.net/bugs/70165 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-b

[Bug 70165] Re: Palm/Treo Not Talking to Kernel (2.6.17)

2007-04-13 Thread Chip Rosenthal
Sync for my Samsung i500 (a USB Palm device) broke sometime in the past couple weeks. (I'm using kpilot.) I found the workaround is to do: modprobe visor Once that module is loaded, the /dev/ttyUSB[01] devices would get created, and then I could sync. You may want to see if "modprobe visor" so