On Mon, Jan 19, 2009 at 8:36 PM, Ian Campbell <i...@hellion.org.uk> wrote: > On Mon, 2009-01-19 at 19:46 +0000, Mike Grice wrote: >> On Mon, Jan 19, 2009 at 4:57 PM, Ian Campbell <i...@hellion.org.uk> wrote: >> > On Mon, 2009-01-19 at 16:43 +0000, Mike Grice wrote: >> >> 2009/1/19 Mike Grice <mgr...@plus.net>: >> >> > On Mon, Jan 19, 2009 at 4:10 PM, Ian Campbell <i...@hellion.org.uk> >> >> > wrote: >> >> >> On Mon, 2009-01-19 at 14:12 +0000, Mike Grice wrote: >> >> >>> >> >> >>> Select a language: English >> >> >>> Choose Language: default >> >> >>> Detect Network Hardware: >> >> >>> "No Ethernet card was detected. If you know the name of the driver >> >> >>> │ >> >> >>> │ needed by your Ethernet card, you can select it from the list." >> >> >> >> >> >> Do you have something akin to /sys/bus/sunv/devices/blah? With modalias >> >> >> entries here and in the module the installer should be able to make the >> >> >> connection between one and the other. For example for Xen virtual >> >> >> devices we have: >> >> >> di32:~# cat /sys/bus/xen/devices/vif-0/modalias >> >> >> xen:vif >> >> >> di32:~# modinfo xen-netfront >> >> >> filename: >> >> >> /lib/modules/2.6.26-1-686-bigmem/kernel/drivers/net/xen-netfront.ko >> >> >> alias: xennet >> >> >> alias: xen:vif >> >> >> license: GPL >> >> >> description: Xen virtual network device frontend >> >> >> depends: >> >> >> vermagic: 2.6.26-1-686-bigmem SMP mod_unload modversions >> >> >> 686 >> >> >> >> >> >> So the xen:vif modalias ties into the alias on the module. > >> The main concern I have is the autodetection of the hardware... I >> don't know how the installer works enough to see what bit isn't >> working there, so I'll have to do some digging :-( > > That's what the module alias stuff I describe above is all about, if > this is correct then the installer should Do The Right Thing.
Having had a hunt around the net, and looking at how Ubuntu deal with things, they seem to have a patched udev and then some udev magic to pick these devices up (via VIO). Apparently they are on a list of things that are 'not modalias compatible' so need special treatment (though I lost that page on my hunt). There is some stuff exposed through 'vio' though. hostname:~# modinfo sunvdc filename: /lib/modules/2.6.26-1-sparc64-smp/kernel/drivers/block/sunvdc.ko version: 1.0 license: GPL description: Sun LDOM virtual disk client driver author: David S. Miller (da...@davemloft.net) srcversion: DA09013600C87C20DCD182A alias: vio:Tvdc-portS* depends: vermagic: 2.6.26-1-sparc64-smp SMP mod_unload modversions hostname:~# modinfo sunvnet filename: /lib/modules/2.6.26-1-sparc64-smp/kernel/drivers/net/sunvnet.ko version: 1.0 license: GPL description: Sun LDOM virtual network driver author: David S. Miller (da...@davemloft.net) srcversion: FCB2B4E588A5F07F25D52B5 alias: vio:Tvnet-portS* depends: vermagic: 2.6.26-1-sparc64-smp SMP mod_unload modversions (I don't understand the vio stuff either...) Using this VIO and udev they load a special udev rules file (see attached) that seems to pick these things up. Dont know how that would work in the installer though. I've hit another bug (to do with disk labels, #512740) which I've raised (its fixed in Ubuntu so I provided a patch) but we are getting there. I can work around most of these things now via Preseeding and some early_command / late_command trickery. Of course I'll help any way I can, I'm not a package maintainer or DD (though its something I've had on my todo list for a long time) so if its just some legwork I will see what I can do. Cheers Mike
90-modprobe.rules
Description: Binary data
