On Mon, 2009-01-19 at 19:46 +0000, Mike Grice wrote: > On Mon, Jan 19, 2009 at 4:57 PM, Ian Campbell <ijc@hellion.org.uk> wrote: > > On Mon, 2009-01-19 at 16:43 +0000, Mike Grice wrote: > >> 2009/1/19 Mike Grice <mgrice@plus.net>: > >> > On Mon, Jan 19, 2009 at 4:10 PM, Ian Campbell <ijc@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. -- Ian Campbell BOFH excuse #244: Your cat tried to eat the mouse.
Attachment:
signature.asc
Description: This is a digitally signed message part