Bug#393523: no eth0, had to choose eth1
reassign 393523 ethdetect
retitle 393523 ethdetect: could firewire become non default
severity 393523 wishlist
tags 393523 moreinfo
thanks bug tracking system
Op 16-10-2006 om 13:48 schreef Scott Fitzgerald:
> Package: installation-reports
>
> Boot method: CD
> Image version: 15-Oct-2006 cdimage.debian.org etch_di_beta3/i386 1st ISO only
> Date: 16-Oct-2006 13:27 EST US
>
> Machine: Tyan Thunder k8 motherboard
> Processor:Opterorn
> Memory:1 GB
> Partitions:
> Filesystem Type 1K-blocks Used Available Use% Mounted on
<snip/>
> 01:06.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
<snip/>
> 01:06.0 0c00: 1106:3044 (rev 80)
> 05:00.0 0300: 10de:01df (rev a1)
>
>
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
>
> Initial boot worked: [O]
> Configure network HW: [E]
> Config network: [O]
[ further all OKs ]
>
> Comments/Problems:
>
> Network Hardware, my motherboard comes in two models, one has both the NV
> Marvell onboard GB lan and the Broadcom GB lan, and one model (the one I
> have) has only the NV lan. The installer "picks up" a non-existent second
> lan on my motherboard, and links it to "eth0."
The kernel sees the firewire interface as "eth0"
> I knew enough to choose "eth1",
Well done!
> but I am concerned that more novice Debian users might have problems here.
Could you please restart the installation (just restart, no need to
write on the disk ) and report which text you see at the menu
that allow to choose between eth0 and eth1
eth0: requested text
eth1: text I can see at computers with ethernet
Cheers
Geert Stappers
Reply to: