Re: Installation disks should be using 2.6.10 kernel

[Per Bojsen <per.bojsen@comcast.net>]

*** Regarding Installation disks should be using 2.6.10 kernel;
    seb@frankengul.org adds:

seb> Second problem, the netboot installer detected first the firewire
seb> port and then the forcedeth (eth1). And then tried get an adress
seb> on the DHCP port. I had to remove the modules and insert both of
seb> them in the correct order (first forcedeth, last ohci1394).  Of
seb> course this has nothing to do with the amd64, it is more a bug
seb> from debian-installer.

I have an Iwill DK8N board (nForce 3 250 based) and experienced
something very similar.  I installed the gcc-3.4 distribution back in
mid-November.  Actually, I think the boot CD didn't see the Ethernet
port so I had to manually insert the forcedeth module.  I have two
firewire ports (one on the motherboard, one on the sound card) so I
ended up with eth0, eth1, eth2. I think I had to remove the eth1394
module to get rid of the firewire Ethernet ports and then insert
forcedeth.

Later, once the system was installed I still had the issue with the
firewire ports being detected before the Ethernet port and DHCP always
running on eth0.  I could change that to eth2 but next thing I new the
interfaces got detected in a different order and eth0 was now the
Ethernet port.  This probably changed as a result to upgrading
packages or possibly when switching kernel versions.  I am not really
sure.  I ended up disabling the eth1394 module in the kernel
configuration so that I now only have eth0 and it is always the
Ethernet port.  This was the easiest workaround for me as I have no
1394 network and do not plan to have one.

However, out of curiosity, I'd still like to know how to set things up
so that eth0 is always the Ethernet port and eth1/eth2 are always the
Ethernet over firewire ports.

Per

-- 
Per Bojsen                                              <per.bojsen@comcast.net>
7 Francis Road
Billerica, MA 01821-3618
USA