MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Hi, can you explain further, please? I took a look through dmesg while attempting connect and received:
Code:
usb 2-1.2: new full speed USB device using uhci_hcd and address 17
usb 2-1.2: configuration #1 chosen from 1 choice
usb 2-1.2: USB disconnect, address 17
I tried a hack by doing a 'modprobe visor' as suggested on the release page, and it sync'ed one time. However, now every time I try to change kpilot settings it hangs on me and never recovers (and it will not sync again). I hate new releases
Ok hahaha, this is crazy. I can sync, but I cannot get the kpilot interface to come up. If I do try to use the Kpilot GUI interface, it will freeze, and all furthers syncs are impossible (for that invocation). HA, but get this, if I look in the task manager there are 2 kpilot gui processes trying to run, if I cancel one a mess of windows try to pop up (given by the application panel on bottom) and resolve to one that asks me if I would like to cancel the KpilotDaemon. I say no, then I am able to use the original Kpilot gui. This is the craziest bug I have ever seen.
Maybe something to do with the setting I have "start kpilot on login". I will post any findings.
LOL, someone needs to look into this. I am sure KDE has released a fix... (probably anyhow)
Well, thanks for the heads up. My upgrade to 2007 was a mistake, I actually was just doing a urpmi --auto-select from 2006 and POW, I am in BETA hell! lol Oh well, could be worse. When I transitioned to Mandrake 2005 (10.2 I think) I received a semi-cooker release, that was much worse! Would only boot X programs 2/3s of the time.
I think the 'current' link in updates packages should only be relinked to a new release when it is stable. I only care about stable releases. This would avoid about 90% of my issues
BTW, I have heard of a fix in which the kpilot and pilot-link were installed from latest stable sources into Mandriva (manually) and it functioned just fine. This is why I am assuming KDE has already fixed this problem (if it even is on their end, I do not know for sure, however)
I tried kpilot from Mdv-cooker; it's broken too.
Finally, compiling kpilot from svn (and pilot-link 0.12.1 which is required) worked for me.
May I ask, are you using the visor module with the device: /dev/ttyUSB* or are you using the suggested device " USB: " method from mandriva docs? I heard the visor method can cause huge data loss issues when syncing. Please let me know.
BTW, what version off the SVN did you end up getting? I just want to make sure if subversion is updated, that I get the same build you are using.
My Palm is an old Vx with a serial craddle so i hadn't to struggle with usb...
But the experience of many users on the Mdv french forum is that you have to use the visor module (usb: doesn't work) ;
they had to run
Code:
modprobe visor
modprobe usbserial
(or add the modules in /etc/modprobe.preload)
and use /dev/ttyUSB1 (for some people, it was ttyUSB0) as a device, instead of /dev/pilot.
I haven't heard of any data loss with the svn release.
The source code is updated quite often on svn so i don't think you can find the same build i used (rev. 618187). But the changes should be only minor ones.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.