visor module no works with Palm device after Jaunty to Karmic upgrade on older HW.

[b]

In Jaunty I was able to sync my Clie with jpilot no problem.
The visor module was loaded, and when I pressed the sync button on the clie a new device was created, (tty*USB0) and a link to /dev/pilot.

Now when I load the visor module nothing happens when I press the sync button on the clie.

dmesg reports nothing at all, and no tty*USB* devices in /dev

Worked fine on my eee running the same updated Xubuntu. So it seems to be a hardware incompatibility with the kernel on this machine. The hardware is the same as it was in Jaunty.

Appears similar to Bug #222052, but I'm not seeing any errors from visor.

ProblemType: Bug
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: AudioPCI [Ensoniq AudioPCI], device 0: ES1371/1 [ES1371 DAC2/ADC]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bbogart 1617 F.... xfce4-volumed
                      bbogart 1636 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'AudioPCI'/'Ensoniq AudioPCI ENS1371 at 0xe000, irq 12'
   Mixer name : 'SigmaTel STAC9708,11'
   Components : 'AC97a:83847608'
   Controls : 42
   Simple ctrls : 27
CheckboxSubmission: ff13d4ffbb4aa30d1bf24577e90eced4
CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
Date: Wed Jan 20 20:48:49 2010
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=dff8fd0a-c9f8-483c-8124-068de23caf05
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.2)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 007: ID 046d:c501 Logitech, Inc. Cordless Mouse Receiver
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VIA Technologies, Inc. VT8363
Package: linux-image-2.6.31-17-generic 2.6.31-17.54
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-17-generic root=UUID=3f9e704b-e7f8-40b4-bfa3-1f4499b8f1f6 ro quiet splash
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-17-generic N/A
 linux-firmware 1.25
RfKill:

SourcePackage: linux
Uname: Linux 2.6.31-17-generic i686
dmi.bios.date: 12/15/2000
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: 6.00 PG
dmi.board.name: 8363-686A(KT7,KT7-RAID,KT7A,KT7A-RAID)
dmi.board.vendor: <http://www.abit.com.tw>
dmi.chassis.type: 3
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvr6.00PG:bd12/15/2000:svnVIATechnologies,Inc.:pnVT8363:pvr:rvn<http//www.abit.com.tw>:rn8363-686A(KT7,KT7-RAID,KT7A,KT7A-RAID):rvr:cvn:ct3:cvr:
dmi.product.name: VT8363
dmi.sys.vendor: VIA Technologies, Inc.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bbogart 1431 F.... xfce4-volumed
                      bbogart 1437 F.... pulseaudio
 /dev/snd/controlC1: bbogart 1431 F.... xfce4-volumed
                      bbogart 1437 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'V8237'/'VIA 8237 with ALC850 at 0xe800, irq 22'
   Mixer name : 'Realtek ALC850 rev 0'
   Components : 'AC97a:414c4790'
   Controls : 49
   Simple ctrls : 30
Card1.Amixer.info:
 Card hw:1 'Bt878'/'Brooktree Bt878 at 0xdff00000, irq 19'
   Mixer name : 'Bt87x'
   Components : ''
   Controls : 3
   Simple ctrls : 5
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=13df1544-3ecd-4a0b-bea6-347f3f27871d
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-28-generic root=UUID=0ab4bde0-8376-4cbe-9bc0-af6c3a7936bd ro quiet splash
ProcEnviron:
 LANG=en_CA.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
Regression: No
RelatedPackageVersions: linux-firmware 1.34.3
Reproducible: Yes
RfKill:

Tags: lucid kconfig needs-upstream-testing
Uname: Linux 2.6.32-28-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare users
dmi.bios.date: 08/16/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1018.002
dmi.board.name: A8V Deluxe
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1018.002:bd08/16/2007:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnA8VDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Charlie Kravetz (cjkgeek)]

 Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. It is possible that the kernel team will require some further information from you. Thanks for taking the time to make Ubuntu better!

[Jan-Willem van de Meent (janwillem)]

I have exactly the same problem with a palm m515. I used to be able to sync just fine under Jaunty. Under Karmic, the palm device does not even show up under lsusb when I press the hotsync button, and dmesg shows nothing. I have the visor module loaded.

[b (ben-ekran)]

Due to a filesystem issue (Let this be a lesson to you, don't
fsck.reiserfs a ext3 filesystem, even though it does not seem to know
the difference) I've reinstalled my karmic xubuntu system.

I noticed a few strange things that certainly show there is something
going wrong.

1. The first time I tried to sync jpilot did not complain, but the
attempt crashed my Clie. (hard reset required)

2. Due such an extreme failure I unloaded and reloaded the visor module:
sudo modprobe -r visor && sudo modprobe visor

3. Looking at the visor output I see two bindings, for both USB0 and USB1:

Feb 22 10:39:02 aporia kernel: [48501.368174] usb 2-1: new full speed
USB device using uhci_hcd and address 7
Feb 22 10:39:02 aporia kernel: [48501.534433] usb 2-1: configuration #1
chosen from 1 choice
Feb 22 10:39:02 aporia kernel: [48501.555258] visor 2-1:1.0: Handspring
Visor / Palm OS converter detected
Feb 22 10:39:02 aporia kernel: [48501.555611] usb 2-1: Handspring Visor
/ Palm OS converter now attached to ttyUSB0
Feb 22 10:39:02 aporia kernel: [48501.556302] usb 2-1: Handspring Visor
/ Palm OS converter now attached to ttyUSB1

I noticed that /dev/pilot only points to /dev/ttyUSB0.

4. I changed the jpilot settings to use /dev/ttyUSB0. The result is that
both jpilot and the clie sit there waiting to communicate, but neither
able to do so. Jpilot prints "press hotsync button" (already pressed to
initiate the USB connection), and the clie says waiting to connect.

5. I changed the jpilot settings to /dev/ttyUSB1. And guess what, all
works as it did in Jaunty.

Jan-Willem, can you see if this procedure works for you? (unload,
reload, change settings to use ttyUSB1 (if your /var/log/messages says
its being bound like mine does) and then sync?

It appears to me that there visor should only see one converter
attached, there is only one converter, and only one ttyUSB should be
bound, not two.

.b.

Jan-Willem van de Meent wrote:
> I have exactly the same problem with a palm m515. I used to be able to
> sync just fine under Jaunty. Under Karmic, the palm device does not even
> show up under lsusb when I press the hotsync button, and dmesg shows
> nothing. I have the visor module loaded.
>

[Galen Thurber (godfree2)]

I read a boot message that I can't find now stating that any
modprobe
is now deprecated in kernel 2.6.31-20-generic.
Of course nothing in release notes or solutions provided.
/etc/modules
not longer works

[b (ben-ekran)]

I'm still using modprobe without noticing any issues.

What would it be replaced with?

Anyhow I'm now running lucid, and still have to manually unload and
reload the visor module to keep my Clie from freezing on sync.

.b.

On 10-03-29 05:36 PM, Galen Thurber wrote:
> I read a boot message that I can't find now stating that any
> modprobe
> is now deprecated in kernel 2.6.31-20-generic.
> Of course nothing in release notes or solutions provided.
> /etc/modules
> not longer works
>

[b (ben-ekran)]

apport information

[b (ben-ekran)]

apport information

[b (ben-ekran)]

apport information

[b (ben-ekran)]

apport information

[b (ben-ekran)]

apport information

[b (ben-ekran)]

apport information

[b (ben-ekran)]

apport information

[b (ben-ekran)]

apport information

[b (ben-ekran)]

apport information

[b (ben-ekran)]

apport information

[b (ben-ekran)]

apport information

[b (ben-ekran)]

apport information

[b (ben-ekran)]

apport information

[b (ben-ekran)]

apport information

[b (ben-ekran)]

apport information

[b (ben-ekran)]

apport information

[b (ben-ekran)]

apport information

[b (ben-ekran)]

apport information

[b (ben-ekran)]

Well I lost my old machine, now on an AMD64 running Lucid.

Exact same problem persists, I have to manually unload and reload the
visor module to let my palm sync.

I guess no one else is using a palm w/ linux anymore.

Attaching extra apport stuff since this is a different machine.

On 10-06-15 06:45 PM, b wrote:
> I'm still using modprobe without noticing any issues.
>
> What would it be replaced with?
>
> Anyhow I'm now running lucid, and still have to manually unload and
> reload the visor module to keep my Clie from freezing on sync.
>
> .b.
>
> On 10-03-29 05:36 PM, Galen Thurber wrote:
>> I read a boot message that I can't find now stating that any
>> modprobe
>> is now deprecated in kernel 2.6.31-20-generic.
>> Of course nothing in release notes or solutions provided.
>> /etc/modules
>> not longer works
>>
>

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.