[Cooker] [Bug 6184] [drakxtools] New: Drakconnect does not work for dial up connection
http://qa.mandrakesoft.com/show_bug.cgi?id=6184 Product: drakxtools Component: DrakConnect Summary: Drakconnect does not work for dial up connection Product: drakxtools Version: 9.2-17mdk Platform: PC OS/Version: All Status: UNCONFIRMED Severity: major Priority: P2 Component: DrakConnect AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Fire up Drakconnect and select the 'Normal Modem Connection' option only to keep things simple ! Enter all the required details and go all the way to 'Do you want to try the connection'. Select 'Yes' here. At the launching console the following appears : Failed to activate ppp0 with error 8 According to the man page this means : 'The connect script failed (returned a non-zero exit status).' !!! Leave Drakconnect and fire it up again. Again select the modem connection and press 'Next' until the 'Dialup Options' page is displayed. The 'Connection Name' and the 'Domain Name' fields are both now empty. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
[Cooker] [Bug 4118] [kdebase] Connected device icons cover desktop icons
http://qa.mandrakesoft.com/show_bug.cgi?id=4118 --- Additional Comments From [EMAIL PROTECTED] 2003-04-10 22:34 --- Yes, this still appears to be an issue. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Not sure if this is an MDK or a KDE issue. Also, due to limited bandwidth I am not using the latest KDE. When USB or any other removable media / devices are connected their icons cover desktop icons. The media / device icons appear to be placed from the bottom left and go up the screen as more are connected. Eventually the left hand edge of the screen becomes a complete mess and the icons become difficult to see and click on (depending on how many desktop icons were already there).
[Cooker] [Bug 5840] [pcmcia-cs] PCMCIA USB 2.0 cardbus card incorrectly recognised
http://qa.mandrakesoft.com/show_bug.cgi?id=5840 --- Additional Comments From [EMAIL PROTECTED] 2003-19-09 23:53 --- Ah ha ! Could this be because the 2.4 kernel does not understand EHCI ?? -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: I have just purchased a PCMCIA USB 2.0 cardbus card which uses the ALi M5273 chipset. According to ALi's web site this chipset has `One EHCI USB 2.0 and three OHCI USB 1.1'. According to Window$ 2000 and the box it came in this card only exposes the `One EHCI USB 2.0' port. However Mandrake / Linux kernel sees the card as 1 OHCI USB 1.1 port. Moreover lspci reports the chipset as M5237.
[Cooker] [Bug 5841] [XFree86] New: Trust and most Logitec mice do not have wheel support in X
http://qa.mandrakesoft.com/show_bug.cgi?id=5841 Product: XFree86 Component: XFree86 Summary: Trust and most Logitec mice do not have wheel support in X Product: XFree86 Version: 4.3-23mdk Platform: PC OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: XFree86 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Over the years I have gone through several mice. The worst supported for me have always been the Logitec wheel mice. I have just bought a cordless Trust mouse. I didn't realise when I bought it it has `Logitec inside' ! Given the huge number of Logitec / Trust wheel mice out there I am surprised X still doesn't support the wheel. Running xev shows absolutely no signals when the mouse wheel is scrolled. These mice must be outputing some kine of signal when the wheel is scrolled. Surely it must also be decodeable ? -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
[Cooker] [Bug 5840] [pcmcia-cs] New: PCMCIA USB 2.0 cardbus card incorrectly recognised
http://qa.mandrakesoft.com/show_bug.cgi?id=5840 Product: pcmcia-cs Component: pcmcia-cs Summary: PCMCIA USB 2.0 cardbus card incorrectly recognised Product: pcmcia-cs Version: 3.2.4-1mdk Platform: PC OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: pcmcia-cs AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have just purchased a PCMCIA USB 2.0 cardbus card which uses the ALi M5273 chipset. According to ALi's web site this chipset has `One EHCI USB 2.0 and three OHCI USB 1.1'. According to Window$ 2000 and the box it came in this card only exposes the `One EHCI USB 2.0' port. However Mandrake / Linux kernel sees the card as 1 OHCI USB 1.1 port. Moreover lspci reports the chipset as M5237. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
[Cooker] [Bug 5159] [pcmcia-cs-x11] New: PCMCIA hot swapping causes complete system lockup
http://qa.mandrakesoft.com/show_bug.cgi?id=5159 Product: pcmcia-cs-x11 Component: pcmcia-cs-x11 Summary: PCMCIA hot swapping causes complete system lockup Product: pcmcia-cs-x11 Version: 3.2.4-1mdk Platform: Other OS/Version: All Status: UNCONFIRMED Severity: major Priority: P1 Component: pcmcia-cs-x11 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] There is a need to have something like gLaptop in Mandrake (preferably one that works with KDE as well :-) ). Even my PCMCIA modem causes the system to go into complete fits spewing out line after line of text to the console all begining with a hex number inside [] at high speed. cardctl is fine as far as it goes but is not as good as an applet that you can simplt right click on and, for example, select `eject card 1' to make removal safe. Window$ users have had this luxury since Win 95 !! I have suggested a high severity and priority since a complete system lock up results. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
[Cooker] [Bug 3381] [pilot-link] Palm Pilots will not connect to Cooker systems
http://qa.mandrakesoft.com/show_bug.cgi?id=3381 --- Additional Comments From [EMAIL PROTECTED] 2003-02-07 22:10 --- The problem is still valid. If the system knows that a USB device / Palm has attached then ---surely--- it must know which port it has attached to ?!?!? If that really is the case then it would be better if no desktop icon appeared at all ! -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: Having read the pilot-link web pages, how-tos, man pages etc. I was expecting to `lsmod' and see usbcore, usb-uhci, usbserial and visor. All I see is usbcore and usb-uhci. Pressing the Hot Sync button on the Palm produces a KPilot icon on the KDe desktop. Pressing this launches KPilot which reports: 22:11:53 Trying to open device... 22:11:53 Could not open device: /dev/pilot (will retry) `lsmod' output is usbcore and usb-uhci /dev/pilot is a symbolic link to /dev/usb/tts/1 `modprobe'ing usbserial and visor make no difference at all `lsmod' produces the output: visor 10440 0 usbserial 21468 0 [visor] usb-uhci 24652 0 (unused) usbcore72992 1 [usbdnet visor usbserial usb-uhci] The Pilot is connected via the cradle cable into the USB port. It makes no difference if "Cradle/Cable" or "Direct USB/Serial" options are chosen on the Pilot before doing the Hot Sync. Running `addresses' outputs: No $PILOTPORT specified and no -p given. Defaulting to '/dev/pilot' ERROR: No such device (19) Press the HotSync button first and relaunch this conduit.. Unable to bind to port: /dev/pilot None of the pilot-link programs can contact it. How does KDE pick up the fact that there is a Palm attached when none of the USB modules know about it ?!?!
[Cooker] [Bug 4118] [kdebase] New: Connected device icons cover desktop icons
http://qa.mandrakesoft.com/show_bug.cgi?id=4118 Product: kdebase Component: kdebase Summary: Connected device icons cover desktop icons Product: kdebase Version: 3.1.2-3mdk Platform: Other OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P3 Component: kdebase AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Not sure if this is an MDK or a KDE issue. Also, due to limited bandwidth I am not using the latest KDE. When USB or any other removable media / devices are connected their icons cover desktop icons. The media / device icons appear to be placed from the bottom left and go up the screen as more are connected. Eventually the left hand edge of the screen becomes a complete mess and the icons become difficult to see and click on (depending on how many desktop icons were already there). -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
[Cooker] [Bug 3381] [pilot-link] Palm Pilots will not connect to Cooker systems
http://qa.mandrakesoft.com/show_bug.cgi?id=3381 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED --- Additional Comments From [EMAIL PROTECTED] 2003-03-27 21:08 --- /dev/pilot is created and points to /dev/usb/tts/1 (1) every time the HotSync button is pressed. Logging in as root and telling kPilot to use /dev/usb/tts/0 (0) works and the Palm connects. (I've no idea where the data bases I uploaded ended up since kPilot does not tell me and there appears to be nothing in ~ !!! Still that's a kPilot issue :-) ) So, there are two issues here. 1) DevFS creates /dev/pilot to the wrong tts port, and this may be indicated in /var/log/messages: Mar 27 15:03:24 localhost kernel: visor.c: Device lied about number of ports, please use a lower one. 2) Only root appears able to access the Palm device given its current permissions ! Since this is done automagically I can't immediately see a way around this. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Having read the pilot-link web pages, how-tos, man pages etc. I was expecting to `lsmod' and see usbcore, usb-uhci, usbserial and visor. All I see is usbcore and usb-uhci. Pressing the Hot Sync button on the Palm produces a KPilot icon on the KDe desktop. Pressing this launches KPilot which reports: 22:11:53 Trying to open device... 22:11:53 Could not open device: /dev/pilot (will retry) `lsmod' output is usbcore and usb-uhci /dev/pilot is a symbolic link to /dev/usb/tts/1 `modprobe'ing usbserial and visor make no difference at all `lsmod' produces the output: visor 10440 0 usbserial 21468 0 [visor] usb-uhci 24652 0 (unused) usbcore72992 1 [usbdnet visor usbserial usb-uhci] The Pilot is connected via the cradle cable into the USB port. It makes no difference if "Cradle/Cable" or "Direct USB/Serial" options are chosen on the Pilot before doing the Hot Sync. Running `addresses' outputs: No $PILOTPORT specified and no -p given. Defaulting to '/dev/pilot' ERROR: No such device (19) Press the HotSync button first and relaunch this conduit.. Unable to bind to port: /dev/pilot None of the pilot-link programs can contact it. How does KDE pick up the fact that there is a Palm attached when none of the USB modules know about it ?!?!
[Cooker] [Bug 3381] [pilot-link] Palm Pilots will not connect to Cooker systems
http://qa.mandrakesoft.com/show_bug.cgi?id=3381 --- Additional Comments From [EMAIL PROTECTED] 2003-03-26 23:10 --- this is what `grep isor' on /var/log/messages produces: Mar 26 11:32:58 localhost kernel: usbserial.c: USB Serial support registered for Handspring Visor Mar 26 11:32:58 localhost kernel: visor.c: USB HandSpring Visor, Palm m50x, Sony Clié driver v1.5 Mar 26 11:32:47 localhost usb: Loading USB visor succeeded Mar 26 21:04:40 localhost kernel: usbserial.c: USB Serial support registered for Handspring Visor Mar 26 21:04:40 localhost kernel: visor.c: USB HandSpring Visor, Palm m50x, Sony Clié driver v1.5 Mar 26 21:04:29 localhost usb: Loading USB visor succeeded Mar 26 21:41:57 localhost kernel: usbserial.c: USB Serial support registered for Handspring Visor / Palm 4.0 / Clié 4.x Mar 26 21:41:57 localhost kernel: visor.c: USB HandSpring Visor, Palm m50x, Sony Clié driver v1.6 Mar 26 21:45:12 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter detected Mar 26 21:45:12 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: Number of ports: 1 Mar 26 21:45:12 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 1, is for HotSync use and is bound to ttyUSB0 Mar 26 21:45:12 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now attached to ttyUSB0 (or usb/tts/0 for devfs) Mar 26 21:45:12 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now attached to ttyUSB1 (or usb/tts/1 for devfs) Mar 26 21:45:16 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 Mar 26 21:46:15 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now disconnected from ttyUSB0 Mar 26 21:46:15 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now disconnected from ttyUSB1 Mar 26 21:49:42 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter detected Mar 26 21:49:42 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: Number of ports: 1 Mar 26 21:49:42 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 1, is for HotSync use and is bound to ttyUSB0 Mar 26 21:49:42 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now attached to ttyUSB0 (or usb/tts/0 for devfs) Mar 26 21:49:42 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now attached to ttyUSB1 (or usb/tts/1 for devfs) Mar 26 21:49:46 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 Mar 26 21:49:58 localhost kernel: visor.c: Device lied about number of ports, please use a lower one. Mar 26 21:50:09 localhost kernel: visor.c: Device lied about number of ports, please use a lower one. Mar 26 21:50:44 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now disconnected from ttyUSB0 Mar 26 21:50:44 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now disconnected from ttyUSB1 /dev/pilot is created and points to /dev/usb/tts/1 Doing pilot-xfer -l -p /dev/pilot (or /dev/usb/tts/1) produces: No $PILOTPORT specified and no -p given. Defaulting to '/dev/pilot' ERROR: No such device (19) Press the HotSync button first and relaunch this conduit.. Unable to bind to port: /dev/pilot Please use --help for more information Hope this helps, Owen On Wednesday 26 Mar 2003 1:41 pm, fcrozat wrote: --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Having read the pilot-link web pages, how-tos, man pages etc. I was expecting to `lsmod' and see usbcore, usb-uhci, usbserial and visor. All I see is usbcore and usb-uhci. Pressing the Hot Sync button on the Palm produces a KPilot icon on the KDe desktop. Pressing this launches KPilot which reports: 22:11:53 Trying to open device... 22:11:53 Could not open device: /dev/pilot (will retry) `lsmod' output is usbcore and usb-uhci /dev/pilot is a symbolic link to /dev/usb/tts/1 `modprobe'ing usbserial and visor make no difference at all `lsmod' produces the output: visor 10440 0 usbserial 21468 0 [visor] usb-uhci 24652 0 (unused) usbcore72992 1 [usbdnet visor usbserial usb-uhci] The Pilot is connected via the cradle cable into the USB port. It makes no difference if "Cradle/Cable" or "Direct USB/Serial" options are chosen on the Pilot before doing the Hot Sync. Running `addresses' outputs: No $PILOTPORT specified and no -p given. Defaulting to '/dev/pilot' ERROR: No such device (19) Press the HotSync button first and relaunch this conduit.. Unable to bind to port: /dev/p
[Cooker] [Bug 3381] [pilot-link] Palm Pilots will not connect to Cooker systems
http://qa.mandrakesoft.com/show_bug.cgi?id=3381 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED --- Additional Comments From [EMAIL PROTECTED] 2003-03-26 23:07 --- this is what `grep isor' on /var/log/messages produces: Mar 26 11:32:58 localhost kernel: usbserial.c: USB Serial support registered for Handspring Visor Mar 26 11:32:58 localhost kernel: visor.c: USB HandSpring Visor, Palm m50x, Sony Clié driver v1.5 Mar 26 11:32:47 localhost usb: Loading USB visor succeeded Mar 26 21:04:40 localhost kernel: usbserial.c: USB Serial support registered for Handspring Visor Mar 26 21:04:40 localhost kernel: visor.c: USB HandSpring Visor, Palm m50x, Sony Clié driver v1.5 Mar 26 21:04:29 localhost usb: Loading USB visor succeeded Mar 26 21:41:57 localhost kernel: usbserial.c: USB Serial support registered for Handspring Visor / Palm 4.0 / Clié 4.x Mar 26 21:41:57 localhost kernel: visor.c: USB HandSpring Visor, Palm m50x, Sony Clié driver v1.6 Mar 26 21:45:12 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter detected Mar 26 21:45:12 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: Number of ports: 1 Mar 26 21:45:12 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 1, is for HotSync use and is bound to ttyUSB0 Mar 26 21:45:12 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now attached to ttyUSB0 (or usb/tts/0 for devfs) Mar 26 21:45:12 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now attached to ttyUSB1 (or usb/tts/1 for devfs) Mar 26 21:45:16 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 Mar 26 21:46:15 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now disconnected from ttyUSB0 Mar 26 21:46:15 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now disconnected from ttyUSB1 Mar 26 21:49:42 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter detected Mar 26 21:49:42 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: Number of ports: 1 Mar 26 21:49:42 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 1, is for HotSync use and is bound to ttyUSB0 Mar 26 21:49:42 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now attached to ttyUSB0 (or usb/tts/0 for devfs) Mar 26 21:49:42 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now attached to ttyUSB1 (or usb/tts/1 for devfs) Mar 26 21:49:46 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 Mar 26 21:49:58 localhost kernel: visor.c: Device lied about number of ports, please use a lower one. Mar 26 21:50:09 localhost kernel: visor.c: Device lied about number of ports, please use a lower one. Mar 26 21:50:44 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now disconnected from ttyUSB0 Mar 26 21:50:44 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now disconnected from ttyUSB1 /dev/pilot is created and points to /dev/usb/tts/1 Doing pilot-xfer -l -p /dev/pilot (or /dev/usb/tts/1) produces: No $PILOTPORT specified and no -p given. Defaulting to '/dev/pilot' ERROR: No such device (19) Press the HotSync button first and relaunch this conduit.. Unable to bind to port: /dev/pilot Please use --help for more information Hope this helps, Owen --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Having read the pilot-link web pages, how-tos, man pages etc. I was expecting to `lsmod' and see usbcore, usb-uhci, usbserial and visor. All I see is usbcore and usb-uhci. Pressing the Hot Sync button on the Palm produces a KPilot icon on the KDe desktop. Pressing this launches KPilot which reports: 22:11:53 Trying to open device... 22:11:53 Could not open device: /dev/pilot (will retry) `lsmod' output is usbcore and usb-uhci /dev/pilot is a symbolic link to /dev/usb/tts/1 `modprobe'ing usbserial and visor make no difference at all `lsmod' produces the output: visor 10440 0 usbserial 21468 0 [visor] usb-uhci 24652 0 (unused) usbcore72992 1 [usbdnet visor usbserial usb-uhci] The Pilot is connected via the cradle cable into the USB port. It makes no difference if "Cradle/Cable" or "Direct USB/Serial" options are chosen on the Pilot before doing the Hot Sync.
[Cooker] [Bug 3381] [pilot-link] Palm Pilots will not connect to Cooker systems
http://qa.mandrakesoft.com/show_bug.cgi?id=3381 --- Additional Comments From [EMAIL PROTECTED] 2003-03-24 20:50 --- Yes I do - several and varied !! The jist is: Mar 7 19:30:58 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 Mar 7 19:30:58 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: Number of ports: 1 Mar 7 19:30:58 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 1, is for HotSync use and is bound to ttyUSB0 Mar 7 19:30:58 localhost kernel: visor.c: USB HandSpring Visor, Palm m50x, Sony Clié driver v1.6 Mar 7 19:32:21 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: Number of ports: 1 Mar 7 19:32:21 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 1, is for HotSync use and is bound to ttyUSB0 Mar 7 19:32:25 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 Mar 7 19:32:35 localhost kernel: visor.c: Device lied about number of ports, please use a lower one. Mar 7 19:33:17 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: Number of ports: 1 Mar 7 19:33:17 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 1, is for HotSync use and is bound to ttyUSB0 Mar 7 19:33:22 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 Mar 7 19:33:24 localhost kernel: visor.c: Device lied about number of ports, please use a lower one. Mar 7 19:33:55 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: Number of ports: 1 Mar 7 19:33:55 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 1, is for HotSync use and is bound to ttyUSB0 Mar 7 19:33:56 localhost kernel: visor.c: Device lied about number of ports, please use a lower one. Mar 7 19:33:59 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 Mar 7 19:34:00 localhost kernel: visor.c: Device lied about number of ports, please use a lower one. Mar 7 19:44:52 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: Number of ports: 1 Mar 7 19:44:52 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 1, is for HotSync use and is bound to ttyUSB0 Mar 7 19:44:57 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 Mar 7 19:44:57 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 Palm m130. Looking at the Linux Palm web sites this device should work. I have tried the current Mandrake kernel, a home spun 2.4.19 and a home spun 2.5.59. Owen On Sunday 23 Mar 2003 10:32 pm, fcrozat wrote: --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Having read the pilot-link web pages, how-tos, man pages etc. I was expecting to `lsmod' and see usbcore, usb-uhci, usbserial and visor. All I see is usbcore and usb-uhci. Pressing the Hot Sync button on the Palm produces a KPilot icon on the KDe desktop. Pressing this launches KPilot which reports: 22:11:53 Trying to open device... 22:11:53 Could not open device: /dev/pilot (will retry) `lsmod' output is usbcore and usb-uhci /dev/pilot is a symbolic link to /dev/usb/tts/1 `modprobe'ing usbserial and visor make no difference at all `lsmod' produces the output: visor 10440 0 usbserial 21468 0 [visor] usb-uhci 24652 0 (unused) usbcore72992 1 [usbdnet visor usbserial usb-uhci] The Pilot is connected via the cradle cable into the USB port. It makes no difference if "Cradle/Cable" or "Direct USB/Serial" options are chosen on the Pilot before doing the Hot Sync. Running `addresses' outputs: No $PILOTPORT specified and no -p given. Defaulting to '/dev/pilot' ERROR: No such device (19) Press the HotSync button first and relaunch this conduit.. Unable to bind to port: /dev/pilot None of the pilot-link programs can contact it. How does KDE pick up the fact that there is a Palm attached when none of the USB modules know about it ?!?!
[Cooker] [Bug 3381] [pilot-link] Palm Pilots will not connect to Cooker systems
http://qa.mandrakesoft.com/show_bug.cgi?id=3381 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED --- Additional Comments From [EMAIL PROTECTED] 2003-03-24 20:43 --- > When you press hotsync button, do you get visor messages in > /var/log/messages ? Yes I do - several and varied !! The jist is: Mar 7 19:30:58 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 Mar 7 19:30:58 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: Number of ports: 1 Mar 7 19:30:58 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 1, is for HotSync use and is bound to ttyUSB0 Mar 7 19:30:58 localhost kernel: visor.c: USB HandSpring Visor, Palm m50x, Sony Clié driver v1.6 Mar 7 19:32:21 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: Number of ports: 1 Mar 7 19:32:21 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 1, is for HotSync use and is bound to ttyUSB0 Mar 7 19:32:25 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 Mar 7 19:32:35 localhost kernel: visor.c: Device lied about number of ports, please use a lower one. Mar 7 19:33:17 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: Number of ports: 1 Mar 7 19:33:17 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 1, is for HotSync use and is bound to ttyUSB0 Mar 7 19:33:22 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 Mar 7 19:33:24 localhost kernel: visor.c: Device lied about number of ports, please use a lower one. Mar 7 19:33:55 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: Number of ports: 1 Mar 7 19:33:55 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 1, is for HotSync use and is bound to ttyUSB0 Mar 7 19:33:56 localhost kernel: visor.c: Device lied about number of ports, please use a lower one. Mar 7 19:33:59 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 Mar 7 19:34:00 localhost kernel: visor.c: Device lied about number of ports, please use a lower one. Mar 7 19:44:52 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: Number of ports: 1 Mar 7 19:44:52 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 1, is for HotSync use and is bound to ttyUSB0 Mar 7 19:44:57 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 Mar 7 19:44:57 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 > Which palm model are you trying to synchronize BTW ? Palm m130. Looking at the Linux Palm web sites this device should work. I have tried the current Mandrake kernel, a home spun 2.4.19 and a home spun 2.5.59. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Having read the pilot-link web pages, how-tos, man pages etc. I was expecting to `lsmod' and see usbcore, usb-uhci, usbserial and visor. All I see is usbcore and usb-uhci. Pressing the Hot Sync button on the Palm produces a KPilot icon on the KDe desktop. Pressing this launches KPilot which reports: 22:11:53 Trying to open device... 22:11:53 Could not open device: /dev/pilot (will retry) `lsmod' output is usbcore and usb-uhci /dev/pilot is a symbolic link to /dev/usb/tts/1 `modprobe'ing usbserial and visor make no difference at all `lsmod' produces the output: visor 10440 0 usbserial 21468 0 [visor] usb-uhci 24652 0 (unused) usbcore72992 1 [usbdnet visor usbserial usb-uhci] The Pilot is connected via the cradle cable into the USB port. It makes no difference if "Cradle/Cable" or "Direct USB/Serial" options are chosen on the Pilot before doing the Hot Sync. Running `addresses' outputs: No $PILOTPORT specified and no -p given. Defaulting to '/dev/pilot' ERROR: No such device (19) Press the HotSync button first and relaunch this conduit.. Unable to bind to port: /dev/pilot None of the pilot-link programs can contact it. How does KDE pick up the fact that there is a Palm attached when none of the USB modules know about it ?!?!
[Cooker] [Bug 2687] [gnome-pilot] Palm Tungsten T don't work with gpilotd
http://qa.mandrakesoft.com/show_bug.cgi?id=2687 --- Additional Comments From [EMAIL PROTECTED] 2003-03-23 23:20 --- I would be interested to know which logs these entries were in please. There must be something in this since several people seem to be having difficulties. Owen On Sunday 23 Mar 2003 5:29 pm, jmail wrote: --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: I use the Mandrake 9.1 RC 1 and my Palm Tungsten T communic with pilot-link, with the command line "pilot-xfer -p /dev/usb/tts/0 -L", but when I use the gpilotd-applet, nothing appends.
[Cooker] [Bug 2687] [gnome-pilot] Palm Tungsten T don't work with gpilotd
http://qa.mandrakesoft.com/show_bug.cgi?id=2687 --- Additional Comments From [EMAIL PROTECTED] 2003-03-23 22:55 --- I would be interested to know which logs these entries were in please. There must be something in this since several people seem to be having difficulties. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: I use the Mandrake 9.1 RC 1 and my Palm Tungsten T communic with pilot-link, with the command line "pilot-xfer -p /dev/usb/tts/0 -L", but when I use the gpilotd-applet, nothing appends.
[Cooker] [Bug 3381] [pilot-link] Palm Pilots will not connect to Cooker systems
http://qa.mandrakesoft.com/show_bug.cgi?id=3381 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|FIXED | --- Additional Comments From [EMAIL PROTECTED] 2003-03-20 22:35 --- > modify /etc/sysconfig/usb to get > VISOR=yes Did this... > then /etc/init.d/usb restart Did this... (and re-booted) > You'll get usb visor loaded.. Already had `usb visor' loaded... > Then you MUST press hotsync button BEFORE starting pilot-xfer or any other Did this... Absolutely no effect. I have tried building a kernel with the USB / Visor done as modules and one where they weren't. There is no difference if they are modules or not. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Having read the pilot-link web pages, how-tos, man pages etc. I was expecting to `lsmod' and see usbcore, usb-uhci, usbserial and visor. All I see is usbcore and usb-uhci. Pressing the Hot Sync button on the Palm produces a KPilot icon on the KDe desktop. Pressing this launches KPilot which reports: 22:11:53 Trying to open device... 22:11:53 Could not open device: /dev/pilot (will retry) `lsmod' output is usbcore and usb-uhci /dev/pilot is a symbolic link to /dev/usb/tts/1 `modprobe'ing usbserial and visor make no difference at all `lsmod' produces the output: visor 10440 0 usbserial 21468 0 [visor] usb-uhci 24652 0 (unused) usbcore72992 1 [usbdnet visor usbserial usb-uhci] The Pilot is connected via the cradle cable into the USB port. It makes no difference if "Cradle/Cable" or "Direct USB/Serial" options are chosen on the Pilot before doing the Hot Sync. Running `addresses' outputs: No $PILOTPORT specified and no -p given. Defaulting to '/dev/pilot' ERROR: No such device (19) Press the HotSync button first and relaunch this conduit.. Unable to bind to port: /dev/pilot None of the pilot-link programs can contact it. How does KDE pick up the fact that there is a Palm attached when none of the USB modules know about it ?!?!
[Cooker] [Bug 3381] [pilot-link] New: Palm Pilots will not connect to Cooker systems
http://qa.mandrakesoft.com/show_bug.cgi?id=3381 Product: pilot-link Component: pilot-link Summary: Palm Pilots will not connect to Cooker systems Version: 0.11.7-1mdk Platform: PC OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P3 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Having read the pilot-link web pages, how-tos, man pages etc. I was expecting to `lsmod' and see usbcore, usb-uhci, usbserial and visor. All I see is usbcore and usb-uhci. Pressing the Hot Sync button on the Palm produces a KPilot icon on the KDe desktop. Pressing this launches KPilot which reports: 22:11:53 Trying to open device... 22:11:53 Could not open device: /dev/pilot (will retry) `lsmod' output is usbcore and usb-uhci /dev/pilot is a symbolic link to /dev/usb/tts/1 `modprobe'ing usbserial and visor make no difference at all `lsmod' produces the output: visor 10440 0 usbserial 21468 0 [visor] usb-uhci 24652 0 (unused) usbcore72992 1 [usbdnet visor usbserial usb-uhci] The Pilot is connected via the cradle cable into the USB port. It makes no difference if "Cradle/Cable" or "Direct USB/Serial" options are chosen on the Pilot before doing the Hot Sync. Running `addresses' outputs: No $PILOTPORT specified and no -p given. Defaulting to '/dev/pilot' ERROR: No such device (19) Press the HotSync button first and relaunch this conduit.. Unable to bind to port: /dev/pilot None of the pilot-link programs can contact it. How does KDE pick up the fact that there is a Palm attached when none of the USB modules know about it ?!?! --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
