Re: Treo USB no longer creating ttyUSB[01] devices???

On Sun, 24 Feb 2008 20:19:21 -0600
"Mikkel L. Ellertson" <mikkel@xxxxxxxxxxxxxxxx> wrote:

Mark C. Allman wrote:
On Sat, 2008-02-23 at 19:05 -0700, Craig White wrote:
On Sat, 2008-02-23 at 20:52 -0500, Mark C. Allman wrote:
OK, something else that's broken in F8.

At some point in the past when we'd plug in a Treo 700p USB cable
to hotsync (which occasionally actually worked),
devices /dev/ttyUSB0 and /dev/ttyUSB1 were created to access the
phone. Now when I plug it in I only see lines like:
Feb 23 15:35:26 prez kernel: usb 3-1: new full speed USB
device using uhci_hcd and address 3
Feb 23 15:35:26 prez kernel: usb 3-1: configuration #1 chosen
from 1 choice
When I plug in my Verizon broadband wireless USB modem I see
ttyUSB0 and ttyUSB1 created, but no longer for the Treo.

Any ideas/hints on why the tty devices are no longer created?
----
did you...

cp /usr/share/pilot-link/udev/60-libpisock.rules /etc/udev/rules

also note that the actual ports used /dev/ttyUSBx are less
important because it should automatically create a linked
device /dev/pilot and that would be what you want to use

Craig

Both the files 60-libpisock.rules and 60-pilot.rules. Useless.

Also, the file 60-libpisock.rules references the group "dialout"
which doesn't exist. This suggests some install process which
didn't run (and didn't copy files and create the group). I have
the following packages installed:
gnome-pilot-2.0.15-10.fc8
gnome-pilot-devel-2.0.15-10.fc8
pilot-link-0.12.2-17.fc8
pilot-link-devel-0.12.2-17.fc8

Maybe I'll try uninstalling and reinstalling these. I don't have
days and days and days to waste tracking down all these F8
problems, though. Looks like a move back to F7 is in order. The
kernel I'm running is 2.6.23.15-137.fc8.

Dumb question - did you also copy the 60-pilot.perms to
/etc/security/console.perms.d? This controls the
ownership/permissions of the USB port. You will probably have to log
out and back in for the rules to take affect.

Mikkel

Hi Mark
My F8 also had a similar issue, it magically stopped
creating /dev/ttyUSB[01] for my Palm Z22. I found that
in /etc/modprobe.d the visor module had been blacklisted! I removed the
blacklist and everything was gravy again. Why or where the blacklist
came from I have no idea....

Hope this helps
Bill

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages