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

Bug#352758: marked as done (installation: "etch" installer fails to detect/configure PC card NIC)

Your message dated Wed, 08 Sep 2010 03:58:10 +0000
with message-id <E1OtBnW-00054t-JD@ravel.debian.org>
and subject line Closing old installation report #352758
has caused the Debian Bug report #352758,
regarding installation: "etch" installer fails to detect/configure PC card 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.)


-- 
352758: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=352758
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: installation
Severity: normal


I am trying to do a net install of "etch" - testing - on a Dell Inspiron
7500 via a 3Com Megahertz LAN+56K pc card combo connected to a Motorola
SBV5120 "surfboard" cable modem provided by Optimum Online. The
installer seems to start PC card services successfully but then it does
not recognize my Network Interface Card. As a result the network is not
configured making installation impossible.

-- System Information:
Debian Release: etch -testing
Architecture: i386 (i686)
Kernel: Linux 2.6.12
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

-- Info regarding the hardware obtained from a sarge system running in
another partition:

$ cardctl ident
Socket 0:
  product info: "3Com", "Megahertz 3CCFEM556", "LAN + 56k Modem", ""
  manfid: 0x0101, 0x0556
  function: 0 (multifunction)
Socket 1:
  product info: "KME    ", "SCSI-CARD-001", "1"
  manfid: 0x0032, 0x2604

$ lspci -n
 0000:00:00.0 0600: 8086:7190 (rev 03)
 0000:00:01.0 0604: 8086:7191 (rev 03)
 0000:00:04.0 0607: 104c:ac1c (rev 01)
 0000:00:04.1 0607: 104c:ac1c (rev 01)
 0000:00:07.0 0680: 8086:7110 (rev 02)
 0000:00:07.1 0101: 8086:7111 (rev 01)
 0000:00:07.2 0c03: 8086:7112 (rev 01)
 0000:00:07.3 0680: 8086:7113 (rev 02)
 0000:00:08.0 0401: 125d:1978 (rev 10)
 0000:01:00.0 0300: 1002:4c4d (rev 64)

$ lspci
0000:00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
0000:00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
0000:00:04.0 CardBus bridge: Texas Instruments PCI1225 (rev 01)
0000:00:04.1 CardBus bridge: Texas Instruments PCI1225 (rev 01)
0000:00:07.0 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
0000:00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
0000:00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev01)
0000:00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
0000:00:08.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev 10)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64)

-- Additional remarks:

1. When the installer fails to recognize my NIC it displays a screen
asking me whether I plan to connect via the firewire interface. Probably
irrelevant since this laptop does not have any firewire port or capability

2. I was eventually able to workaround the problem after some
complicated acrobatics that more or less amounted to loading the
3c574_cs module manually.. backing out to the main menu upon reaching
the partitioner step, and running the "configure the network" step
manually. At this point I "executed a shell" and ifconfig  revealed that
my NIC was correctly configured. I verified I was able to access inet
url's by wget-ing a web page.

3. The workaround is not satisfactory since after reboot when I
attempted to complete the installation (base-config program) eth0 was
not configured (although visible when I did an ifconfig -a) and
my attempts to bring it up manually ("ifup eth0"  "ifupdown restart"
"pcmcia restart" "dhclient".. ) were unsuccessful. 

4. On the other hand it would seem that the hardware/pcmcia/cardbus etc.
layer(s) are configured correctly since "cardctl info/ident/status"
displays the usual expected output. 

5. As far as I can tell lsmod reveals that the correct modules for yenta-socket..
pcmcia.. and the NIC itself have been loaded.

6. I have absolutely no clue what is causing this - hotplug maybe..
since I did not have it with the 2.4 kernel.. but since I still have
this interrupted install available I could provide additional info
(logs, config files..) and run tests at short notice.

--- End Message ---
--- Begin Message --- 
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
  Installer.
- indications in the installation report give the feeling that
  the reported problem waslying in another software, unrelated to
  D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
  fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful


The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet. 

In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.

You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.

If some problems are found, please report them with a new bug sent
against installation-reports.

Many thanks for your understanding and your help improving Debian,
past and present.

--- End Message ---
Reply to: