On Tue, May 22, 2007 21:49, Blaisorblade wrote:
> On martedì 22 maggio 2007, David Bull wrote:
>> On Tue, May 22, 2007 02:36, Jeff Dike wrote:
>> > On Tue, May 22, 2007 at 12:20:59AM +0100, David Bull wrote:
>> >> The Fedora Core installer appears in one of the xterm's and asks me
>> >> choose a language, a keyboard layout, and an installation method
>> >> hard disk, nfs, ftp, or http). When I attempt to select one of the
>> >> network installation methods I get a message saying "No driver found"
>> >> and it then asks me to select a driver from a list, or use a driver
>> >> disk.
>> > Is it maybe assuming that, in order to get a working network, you need
>> > to tell it what driver runs your card? What's on the list that it
>> > gives you?
>> > Jeff
>> > --
>> > Work email - jdike at linux dot intel dot com
>> Shouldn't it just use the UML tuntap network driver built into the UML
> Yes, but you've hit an installer which is "too" smart and tries to
> detect the card, load the module and configure it. And its list does not
> include any UML driver, obviously. In such situations, you can just try
> faking or modifying the installer someway.
> If it just tries to load a network module and get success from modprobe,
> an alias like
> install ne2000 /bin/true
> in /etc/modprobe.conf (if that's read by the initrd) might help.
>> The drivers list just brings up a long list of network card
>> drivers such as 3com, intel express, ne2000, etc. If I try selecting any
>> of those it says is can't find the module and asks me to select another
>> If I boot the slackware guest using the same kernel then I can bring the
>> networking up simply by logging in as root and doing "ifconfig eth0
>> 172.16.0.101 up".
> Inform me of my mistakes, so I can add them to my list!
> Paolo Giarrusso, aka Blaisorblade
I tried taking the initrd apart and unfortunatly there's no modprobe.conf.
Also modprobe, insmod and rmmod were symlinks to /sbin/installer which I
tried changing to /bin/true but it didn't make any difference.
I also put a copy if ifconfig inside the initrd and got it to start
/bin/sh rather than launch straight into the installer. I managed to use
ifconfig to being eth0 up successfully but the installer still kept asking
me to select a network driver :-(
Guess I'll continue googling for the time being...