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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Mark C. Allman wrote:
On Sun, 2008-02-24 at 20:19 -0600, Mikkel L. Ellertson 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
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

I didn't copy over the permissions file.  The ttyUSBn devices aren't
being created with the wrong permissions--they're not being created at
all.

I gave up on most of these F8 bugs, to be honest.  I'll go back to
Windows for what doesn't work in F8.

Question about another F8 bug: where does the "Shutdown" applet (menu
System -> Shut down...) get the "You are currently logged in as" value?
It shows on my system as "Unknown."  The "User Switcher" applet knows
who I am, but the "Shut down" applet doesn't.  Just curious, since it
isn't preventing anything from working.


Don't know if these have been suggested but,
Have you also checked  that you have  loaded the visor  module with
this entry in /etc/modprobe.conf :
options visor vendor=0x0830 product=0x0061

then do a modprobe visor



--
Ray Curtis         Unix Programmer/Consultant   Curtis Consulting
mailto:ray@xxxxxxxx                             http://www.ccux.com

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux