sync on feisty with Palm m130, 'visor' kernel module not loaded
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-pilot (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Binary package hint: gnome-pilot
This is on a fresh install of the feisty final release. I'm connecting the palm m130 to my computer via cradle and usb.
In edgy the gnome-pilot device settings used /dev/ttyUSB0 and /dev/ttyUSB1.
In feisty I get no connection when I press the sync button on the cradle (although the info appears in System-
"Failed to connect using device `cradle', on port `/dev/ttyUSB0'.
Check your configuration, as you requested old-style usbserial
`ttyUSB' syncing, but do not have the usbserial `visor' kernel
module loaded. You may need to select a `usb:' device."
I can see in gnome-pilot-
My gut feeling is that I'm missing something simple, but I just can't see it.
I also tried "/dev/pilot" with no success. Only "/dev/ttyUSB0" or "/dev/tty/USB1" get any recognition from gnome-pilot that a connection is even being attempted.
Changed in gnome-pilot: | |
assignee: | nobody → ubuntu-pda |
importance: | Undecided → Medium |
status: | Unconfirmed → Confirmed |
Changed in gnome-pilot (Ubuntu): | |
status: | Incomplete → Invalid |
assignee: | Ubuntu PDA team (ubuntu-pda) → nobody |
I think this is caused by the kernel and not by gnome-pilot. At the earlier kernel on feisty and the same kpilot I have now I could get synching to happen fine, and lsmod would show the visor module. Now the device gets detected, but visor module does not get loaded, and so nothing happens with kpilot.