Bug#411733: fire v100 installation report
Op 20-02-2007 om 18:16 schreef Peter Palfrader:
>
> Initial boot: [O]
> Detect network card: [E]
> the dmfe module was loaded which broke networking completely,
> even tho the tulip module was later loaded too. unloading dmfe
> and loading tulip didn't help either. Blacklisting dmfe helped.
What was the extra boot parameter you used for the blacklisting?
> Configure network: [O]
> Detect CD: [ ]
> Load installer modules: [O]
> Detect hard drives: [O]
> Partition hard drives: [O] no raid1 support? :(
> Install base system: [O]
> Clock/timezone setup: [O]
> User/password setup: [O]
> Install tasks: [O]
> Install boot loader: [O]
> Installed kernel boots: [E]
> The installed kernel (2.6.18-3) didn't boot.
> 2.6.18-4 from unstable did.
What should other people do that find this BR through a search engine?
Please tell what you did to install that extra kernel.
> Overall install: [O] (or E, depending on how you look at things :)
>
> Comments/Problems:
>
> The installer itself worked nicely, but the two kernel issues - combined
> with me not being familiar with sparc at all - made it a bit of a pain.
>
> The network interface selector should show the mac address or at least a
> link active/not active, but that's already reported as #411367.
BR 411367 is indeed about disclosing MAC address.
"link active/not active" is allready available and hidden in the default
interface ( the cursor is at the NIC with "link detect" )
Did it work for your dual ethernet card?
Cheers
Geert Stappers
Reply to: