[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian Installer - boot floppies

On Fri, Mar 03, 2006 at 02:30:36PM -0800, Brad Boyer wrote:
> On Fri, Mar 03, 2006 at 10:04:41PM +0100, Frans Pop wrote:
> > So, my questions would be:
> > - which driver is actually needed in the case of #345467
> swim3.ko
> > - is this driver available on the root floppy (built in or module)
> > - if it's modular, is it being loaded
> No idea. Haven't looked. Based on the email thread, I would say it's
> there one way or another. It sounded like the driver was loaded but
> there wasn't a node in /dev created to be able to use it.

Ah, it is builtin, not modular :


Which is logical, since we want to load the root floppy from it, which
contains the modules, and since we are in a 2 disk solution, not like the x86

> > - if it's loaded, what are the correct device nodes for it and why are
> >   they not being created
> It should be block device 2,0 just like what floppy.ko would do. It should
> show up in devfs as /dev/floppy/0, too. It's possible the swim3 code is
> broken. I'm not sure it has an official maintainer anymore. How are device
> nodes normally getting created? Are we still using devfs, or have we
> moved on to using udev? At one point, the macio bus support wasn't
> entirely patched in for hotplug and probably by extension for udev.

I guess we are using udev, but with a devfs-like naming scheme on top, right ?
I strongly believe that swim3.ko is not hotplug friendly, or that udev has
some trouble with builtin modules, but i would go for the first case.


Sven Luther

Reply to: