/dev/ttyUSB1 for Palm syncing 1

[wmg]

Hello,

I'm running MDK9.1 and am trying to get my palm m130 syncing.

All the howto docs I've found refer to setting a link to the above device to /dev/pilot.

I don't have that ttyUSB1 device on my system. It appears that MDK91 uses /dev/usb/tts/ and then lists each of the two USB buses of there. If I do a 'lsusb' (after pressing the hotsync button on the cradle) the Palm m130 device appears but the usb device it is connecting on appears to increment by one each time a hotsync is performed - so I can't really link to that either.

It seems to me that, once I can get this small thing sorted, then I'll be up and running. Does anyone have any ideas about that? Or perhaps a link for howto: for MDK91 and a USB palm that I haven't found yet?

Thanks!



We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true. [Robert Wilensky, 1997]

 

[krale]

>>I'm running MDK9.1 and am trying to get my palm m130 syncing.

Good God^H^H^Hluck. You'll need it.

The reason why your doc's are inconstistant is because Mandrake compiled with /dev filesystem on.

Normally, /dev is a jumbled mess of unused device nodes scattered good with bad. What you can do, is easily find or create the required node to the hardware.

/dev fs was made to clean out the cruft from the old messy /dev. They, (back in kernel version 2.3 or 2.1...) added a /dev filesystem, along with a user-space daemon. In doing so, they re-did the whole /dev so most programs that access direct nodes DO NOT WORK. You have to use the automatically made nodes by /dev fs.

I've experimented with /dev fs on a spare box, but didnt like it much. It still felt buggy or unfinished. I have no idea why Mandrake thought it was better than the standard /dev . Anyways, 2.6 is going to AXE /dev fs.

The best/only step you can do first is to go download the full 2.4.20 kernel package from

http://www.kernel.org

and compile it WITHOUT /dev fs. That's the only way you're going to succeed by following those doc's (or you could make a /dev fs doc and send it to the HOWTO people if you can figure it out).

Good luck.

Please let Tek-Tips members know if their posts were helpful.

 

[wmg]

E

http://www -

that's sounds *nasty*.

I'll tinker around with this /dev fs thing and if that don't work, I'll try a kernel transplant.

(Though I have no idea on that, I guess there are plenty of docs around on that topic eh?)

Does Redhat 8 or 9 use /dev fs? ;-)

We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true. [Robert Wilensky, 1997]

 

[krale]

There is ONE other way, but I still dont like it (and it adds yet another program to run). It's called devfsd. It links the /dev fs to the older /dev file nodes, but you have to tell it seperately for each device node you want to create.

EX: Lilo will NOT re-MBR the harddrive because they radically changed the listing of ide drives in /dev fs. You need to make a plain old /dev/hdXX node. When devfsd starts up, it makes those nodes so non-devfs programs can still use hardware.


And to answer your RedHat question, I dont know. Havent used Redhat since the 5.1 years. I use Debian and Slackware now.

Please let Tek-Tips members know if their posts were helpful.