[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#588642: marked as done (Debian-Installer Cant find onboard NIC)

Your message dated Sat, 20 Jul 2013 01:07:31 +0200
with message-id <201307200107.51378.holger@layer-acht.org>
and subject line dealing with old installation-reports
has caused the Debian Bug report #588642,
regarding Debian-Installer Cant find onboard NIC
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
588642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588642
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package:Debian Installer 6.0 Alpha1 release
Version:Linux testing "squeeze" - official snapshot i386 NETINST Binary-1 20100217-22:18 
New System:
    Intel DP55KG Extreme Motherboard
    Intel i5-750 Quad Processor (2.65 GHz)
    4 GB 1333Mhz memory
    e1000e internal NIC based on 82578DC Chip set
    PCIe Express bussing

Problem occures in both the Lenny and Sqeeze 6.0 Alpha1 disks.

Steps
1 Select install
2 Select Engish, US etc
3 Loading sequence , detect hardware, cdrom scan
4 Screen saying: No eternet card detected. If you now the name of the driver needed by your ethernet card , you can select it from the list. 
5 Select e1000e driver and hit enter
Program keeps cycling back through the same page.
It appears that the on board NIC is not being detected by the installer.

Gary Roach

--- End Message ---
--- Begin Message --- 
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they have been from a development phase where things were not stable and/or
- they are very old, more than 2.5 years.

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
        Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: