On Sun, 2008-02-24 at 15:28 -0500, 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.

I'm running F7 and it has the same problem with the dialout group. I have just been ignoring it, but it should be cleaned up.

Regards, Les H

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@redhat.com 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.

-- Mark C. Allman, PMP -- Allman Professional Consulting, Inc. -- www.allmanpc.com, 617-947-4263

BusinessMsg -- the secure, managed, J2EE/AJAX Enterprise IM/IC solution

On Tue, 2008-02-26 at 08:11 -0500, Ray Curtis wrote:

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@redhat.com 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@ccux.com http://www.ccux.com

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

I seem to recall sometime in the distant past that I set up modprobe options on one of my systems. What may have happened is that I set it up when I was using F7, then when I updated to F8 the update process blew away my settings. I know that many other settings (e.g., power management) were reset when I updated. I see that the visor module is loaded ("modprobe -l | grep visor") but I know I don't have any special options set in modprobe.conf.

I'll try it this evening and see what happens.

-- Mark C. Allman, PMP -- Allman Professional Consulting, Inc. -- www.allmanpc.com, 617-947-4263

BusinessMsg -- the secure, managed, J2EE/AJAX Enterprise IM/IC solution

On Wed, 2008-02-27 at 13:20 -0500, David Hollis wrote:

On Tue, 2008-02-26 at 08:11 -0500, Ray Curtis wrote:

...

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

All,

pilot-link is undergoing some tweaks and fixes and such and the currently released packages pretty much have everything broken. If you want to make some headway, do this:

Forget all about visor.ko. It's old-hat. Snag the latest pilot-link from Koji (http://koji.fedoraproject.org/koji/buildinfo?buildID=35760) and upgrade your installation (you may also need pilot-link-devel). Remove any udev hacks that you have put in place (60-libpisock.rules or whatever) you won't need it.

After pilot-link is updated, plug in your Palm and initiate a hotsync. The first time around, HAL is likely to segfault (check /var/log/messages). Restart HAL with /etc/init.d/haldaemon restart. Now, execute: pilot-xfer -p usb: -l and initiate a hotsync when prompted. You should get a dump from the phone.

If all is well, change your Palm sync app to use the 'usb:' device instead of /dev/ttyUSBx and you should be in good shape.

Is there going to be a rebuild of this package for FC7? I could sure use it. I wuz about to complain to the vendor that sold me a data cable for my Verizon LG, which almost kinda sorta might work.

Bitpim auto retries connection for about 10-15 minutes, then finally hits on a connection reporting success, but nothing happens. The phone makes a zinging sound, and thats all I got for my efforts. :) It would be mo betta to try something better than what I've got so far. Thanks! Ric

On Thu, 2008-02-28 at 11:18 -0500, David Hollis wrote:

On Wed, 2008-02-27 at 15:26 -0500, Ric Moore wrote:

...

Is there going to be a rebuild of this package for FC7? I could sure use it. I wuz about to complain to the vendor that sold me a data cable for my Verizon LG, which almost kinda sorta might work.

I don't think it will be. IIRC, F7 doesn't have PolicyKit so there would be other things to do to enable the security on the USB device.

Huh, lsusb shows the usb-serial cable hooked up. cat /proc/bus/usb/devices shows this

T: Bus=02 Lev=01 Prnt=01 Port=02 Cnt=02 Dev#= 4 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=067b ProdID=2303 Rev= 3.00 S: Manufacturer=Prolific Technology Inc. S: Product=USB-Serial Controller C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=pl2303 E: Ad=81(I) Atr=03(Int.) MxPS= 10 Ivl=1ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms

So, I tried modprobe usbserial vendor=0x067b product=0x2303 which happened without an error message. But,using BitPim it sees the cable but cannot access the phone. Here's the rub, if I hotplug the cable in, X freezes up and I have to hard-reboot via shiny red button. Then I plug the phone in, switched off, and no detect. Powered up the phone, still no detect. I went into the phone setup and made sure it was selected as a serial connection, that is correct?? It also had USB connection, which I may have to try. But the serial section lists 3 speeds: 19200, 115200, 230408 for the phone (Verizon LG XV4650) So, I have to dig for that. Is there a usb-serial module specific to cell-phones or does anyone have a clue where I should start? Ric

On Sun, 24 Feb 2008 20:19:21 -0600 "Mikkel L. Ellertson" mikkel@infinity-ltd.com 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