Re: /dev/hdb LS120

John Batistic wrote:

> Trying to get things working, I am unable to mount my internal LS120.

I am experiencing no problems whatsoever with my LS120 under Gentoo. Here are a few things to consider, in no particular order ...

I recommend compiling IDE-FLOPPY as a a module, although I realise that this isn't the crux of the problem. I was using vanilla-sources (i.e. a stock 2.4.19 kernel) with a gcc3 compiled system, and I'm now using a custom patched kernel (2.4.19 patched with preemptive support, O1 scheduler and some other niceties) and it still works. I presume you are using gentoo-sources, so it may well be worth trying vanilla-sources. I gave up on gentoo-sources because they are based on 2.4.18 series and I don't believe in using patches unless they are required or desired. Give it a go. If it works but you don't like the idea of losing some of the nifty patches, keep an eye on forums.gentoo.org where I will be posting some patching tips at some point soon(ish).

Also, are you using the latest devfsd? Typing "emerge -s devfsd" should give the answer to that one. In fact, "emerge -u system" should ensure you have the latest system packages and layout and "emerge clean" should clean out the cruft.

If you have ever updated packages in the past, or you have just performed the above, then check /etc for updated config files that have not been integrated:

find /etc -iname "._cfg*"

Any files listed are there because Gentoo will never overwrite your existing /etc entries. It's important that you diff the old and the new to see if anything's changed. I know for a fact that devfsd.conf has gone through several permutations as it has evolved. Maybe these are *important*! You can add

| grep devfs

on the end of that find command to check for that. If there is such a file then simply copy it over the existing devfsd.conf. If there are multiple instances then pick the file that has the highest trailing number on the end. Do check the other files too. Often, it's simply the header that changes but sometimes the changes are very important. Backup your /etc directory first.

The devfsd manual has this to say on how it works:

<quote>
For every entry (device node) in a devfs-based /dev a driver must call devfs_register(). This adds the name of the device entry, the file_operations structure pointer and a few other things to an internal table. Device entries may be added and removed at any time. When a device entry is registered, it automagically appears in any mounted devfs'.
</quote>

Perhaps the registration process is not occuring properly with the IDE-FLOPPY driver in the 2.4.18 kernel? Just a theory. Hopefully some of this will be of help!

--kerframil