Red Hat Bugzilla – Bug 170085
Palm PDA device files are not created
Last modified: 2015-01-04 17:22:29 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7 Description of problem: My PDA is a Handspring Visor Platinum running PalmOS 3.5.2 I am syncing it to the computer over a USB cradle. The computer is running FC4 fully updated via yum. When pushing the sync button on the cradle, no PDA device files are created in /dev. There's no /dev/pilot, no /dev/ttyUSB*, nothing. I have to create myself every time these files, which is annoying: crw-rw---- 1 root uucp 188, 0 Oct 2 19:23 ttyUSB0 crw-rw---- 1 root uucp 188, 1 Oct 2 19:23 ttyUSB1 Then I configured JPilot to use /dev/ttyUSB1 and it works fine. What's weird is that, after completing the sync, the ttyUSB* files are deleted! So, obviously "something" is aware of these files, it does not create them, but deletes them every time, therefore making the problem worse. Version-Release number of selected component (if applicable): udev-058-1 How reproducible: Always Steps to Reproduce: 1.see above 2. 3. Actual Results: JPilot fails because there are no /dev entries related to the PDA. Expected Results: /dev entires for the PDA should be created automatically when pushing the sync button on the cradle. It is irrelevant whether they're deleted again after completing the sync. I'd rather not delete them if I could have a choice. Additional info: Just venting: support for external devices got only worse from FC2 to FC4. The PDA, the digital camcorder (FireWire device), everything needs all kinds of hacks in order to work. It was supposed to be plug and play (and it was, with FC2)... OK, the rant is over. If you need more info, let me know. I'll file a separate bug report for the camcorder if I get some more spare time.
hmm, please attach your palm and give me the output of: # find /sys -name dev
I updated to udev-058-1.0.FC4.1 Let me do the test that you requested...
# find /sys -name dev /sys/block/md0/dev /sys/block/fd0/dev /sys/block/hdc/dev /sys/block/hda/hda6/dev /sys/block/hda/hda5/dev /sys/block/hda/hda4/dev /sys/block/hda/hda3/dev /sys/block/hda/hda2/dev /sys/block/hda/hda1/dev /sys/block/hda/dev /sys/block/ram15/dev /sys/block/ram14/dev /sys/block/ram13/dev /sys/block/ram12/dev /sys/block/ram11/dev /sys/block/ram10/dev /sys/block/ram9/dev /sys/block/ram8/dev /sys/block/ram7/dev /sys/block/ram6/dev /sys/block/ram5/dev /sys/block/ram4/dev /sys/block/ram3/dev /sys/block/ram2/dev /sys/block/ram1/dev /sys/block/ram0/dev /sys/class/printer/lp0/dev /sys/class/video4linux/radio0/dev /sys/class/video4linux/vbi0/dev /sys/class/video4linux/video0/dev /sys/class/sound/mixer1/dev /sys/class/sound/controlC1/dev /sys/class/sound/audio1/dev /sys/class/sound/dsp1/dev /sys/class/sound/pcmC1D0c/dev /sys/class/sound/adsp1/dev /sys/class/sound/pcmC1D1c/dev /sys/class/sound/mixer/dev /sys/class/sound/controlC0/dev /sys/class/sound/audio/dev /sys/class/sound/dsp/dev /sys/class/sound/pcmC0D0c/dev /sys/class/sound/pcmC0D0p/dev /sys/class/sound/dmmidi/dev /sys/class/sound/midi/dev /sys/class/sound/midiC0D0/dev /sys/class/sound/sequencer2/dev /sys/class/sound/sequencer/dev /sys/class/sound/seq/dev /sys/class/sound/timer/dev /sys/class/vc/vcsa7/dev /sys/class/vc/vcs7/dev /sys/class/vc/vcsa2/dev /sys/class/vc/vcs2/dev /sys/class/vc/vcsa4/dev /sys/class/vc/vcs4/dev /sys/class/vc/vcsa5/dev /sys/class/vc/vcs5/dev /sys/class/vc/vcsa6/dev /sys/class/vc/vcs6/dev /sys/class/vc/vcsa3/dev /sys/class/vc/vcs3/dev /sys/class/vc/vcsa12/dev /sys/class/vc/vcs12/dev /sys/class/vc/vcsa1/dev /sys/class/vc/vcs1/dev /sys/class/vc/vcsa/dev /sys/class/vc/vcs/dev /sys/class/mem/kmsg/dev /sys/class/mem/urandom/dev /sys/class/mem/random/dev /sys/class/mem/full/dev /sys/class/mem/zero/dev /sys/class/mem/port/dev /sys/class/mem/null/dev /sys/class/mem/mem/dev /sys/class/input/event2/dev /sys/class/input/event1/dev /sys/class/input/mouse0/dev /sys/class/input/event0/dev /sys/class/input/mice/dev /sys/class/misc/device-mapper/dev /sys/class/misc/agpgart/dev /sys/class/misc/hpet/dev /sys/class/misc/rtc/dev /sys/class/graphics/fb0/dev /sys/class/tty/ttyUSB1/dev /sys/class/tty/ttyUSB0/dev /sys/class/tty/ttyS0/dev /sys/class/tty/ttyS31/dev /sys/class/tty/ttyS30/dev /sys/class/tty/ttyS29/dev /sys/class/tty/ttyS28/dev /sys/class/tty/ttyS27/dev /sys/class/tty/ttyS26/dev /sys/class/tty/ttyS25/dev /sys/class/tty/ttyS24/dev /sys/class/tty/ttyS23/dev /sys/class/tty/ttyS22/dev /sys/class/tty/ttyS21/dev /sys/class/tty/ttyS20/dev /sys/class/tty/ttyS19/dev /sys/class/tty/ttyS18/dev /sys/class/tty/ttyS17/dev /sys/class/tty/ttyS16/dev /sys/class/tty/ttyS15/dev /sys/class/tty/ttyS14/dev /sys/class/tty/ttyS13/dev /sys/class/tty/ttyS12/dev /sys/class/tty/ttyS11/dev /sys/class/tty/ttyS10/dev /sys/class/tty/ttyS9/dev /sys/class/tty/ttyS8/dev /sys/class/tty/ttyS7/dev /sys/class/tty/ttyS6/dev /sys/class/tty/ttyS5/dev /sys/class/tty/ttyS4/dev /sys/class/tty/ttyS3/dev /sys/class/tty/ttyS2/dev /sys/class/tty/ttyS1/dev /sys/class/tty/tty63/dev /sys/class/tty/tty62/dev /sys/class/tty/tty61/dev /sys/class/tty/tty60/dev /sys/class/tty/tty59/dev /sys/class/tty/tty58/dev /sys/class/tty/tty57/dev /sys/class/tty/tty56/dev /sys/class/tty/tty55/dev /sys/class/tty/tty54/dev /sys/class/tty/tty53/dev /sys/class/tty/tty52/dev /sys/class/tty/tty51/dev /sys/class/tty/tty50/dev /sys/class/tty/tty49/dev /sys/class/tty/tty48/dev /sys/class/tty/tty47/dev /sys/class/tty/tty46/dev /sys/class/tty/tty45/dev /sys/class/tty/tty44/dev /sys/class/tty/tty43/dev /sys/class/tty/tty42/dev /sys/class/tty/tty41/dev /sys/class/tty/tty40/dev /sys/class/tty/tty39/dev /sys/class/tty/tty38/dev /sys/class/tty/tty37/dev /sys/class/tty/tty36/dev /sys/class/tty/tty35/dev /sys/class/tty/tty34/dev /sys/class/tty/tty33/dev /sys/class/tty/tty32/dev /sys/class/tty/tty31/dev /sys/class/tty/tty30/dev /sys/class/tty/tty29/dev /sys/class/tty/tty28/dev /sys/class/tty/tty27/dev /sys/class/tty/tty26/dev /sys/class/tty/tty25/dev /sys/class/tty/tty24/dev /sys/class/tty/tty23/dev /sys/class/tty/tty22/dev /sys/class/tty/tty21/dev /sys/class/tty/tty20/dev /sys/class/tty/tty19/dev /sys/class/tty/tty18/dev /sys/class/tty/tty17/dev /sys/class/tty/tty16/dev /sys/class/tty/tty15/dev /sys/class/tty/tty14/dev /sys/class/tty/tty13/dev /sys/class/tty/tty12/dev /sys/class/tty/tty11/dev /sys/class/tty/tty10/dev /sys/class/tty/tty9/dev /sys/class/tty/tty8/dev /sys/class/tty/tty7/dev /sys/class/tty/tty6/dev /sys/class/tty/tty5/dev /sys/class/tty/tty4/dev /sys/class/tty/tty3/dev /sys/class/tty/tty2/dev /sys/class/tty/tty1/dev /sys/class/tty/tty0/dev /sys/class/tty/ptmx/dev /sys/class/tty/console/dev /sys/class/tty/tty/dev
Hmm, then there has to be a /dev/ttyUSB0 and /dev/ttyUSB1 device. This works for other people also. But if you press the "sync" button, the Palm reconnects to the USB Bus, the kernel sends a "remove" event and the devices are deleted by udev. Works as expected, from the udev view.
2.6.14-1.1637_FC4 has been released as an update for FC4. Please retest with this update, as a large amount of code has been changed in this release, which may have fixed your problem. Thank you.
This is a mass-update to all currently open kernel bugs. A new kernel update has been released (Version: 2.6.15-1.1830_FC4) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO_REPORTER state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. Thank you.
Closing per previous comment.