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

Re: installation report - network setup failed - intel btx system




On Sun, Aug 21, 2005 at 02:47:18PM -0700, Daniel Cardenas wrote:
Debian-installer-version: Aug 19, i386 net installDate: Aug 20Method:
Burned CD disk.  (Would have preferred USB boot)

"hd-media" can be used for USB booting.
[1]

Machine: Homebuilt Intel MicroBTX, Intel 945 chipset, Motherboard
http://www.newegg.com/Product/Product.asp?Item=N82E16813121296, network:
http://www.intel.com/design/network/products/lan/controllers/82573.htm
Processor: Celeron 2.53 GHz
Memory: 2 gigabytes
Root Device: SATA
Root Size/partition table: Couldn't find SATA drives
Output of lspci and lspci -n: Don't know how to do this.

The "installation report template" assumes
that executing the lspci program is possible.

Base System Installation Checklist: Error
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:    [O]
Configure network HW:   [e]
Config network:         [e]
Detect CD:              [o]
Load installer modules: [o]
Detect hard drives:     [e]
Partition hard drives:  [ ]
Create file systems:    [ ]
Mount partitions:       [ ]
Install base system:    [ ]
Install boot loader:    [ ]
Reboot:                 [ ]

Comments/Problems:
Couldn't find network card, I manually specified e1000, then couldn't get
DNS info from DHCP, I manually specified but still didn't work. On Windows
the network card is identified as Intel PRO/1000 PM

Mmm, that needs further investigation. ( on your hardware )

Switch to the second virtual console    ( press ALT-F2 )

`ifconfig eth0 up`
`ifconfig eth0`
and E-mail us the output of those commands
ALT-F1 brings you back to installer


The ethernet configuration now works with the Aug 27 network install CD, although I had to manually select e1000 Intel Gigabit.

Didn't find my SATA drives.  Appreciate any help.
I don't have another linux system right now, only windows.

Have you access to "live CD" like Gnoppix?

"Open a console[2]" and use
 ( lspci ; lspci -n ) | sort | less
to find the (SATA) disc controller[3]



While using the installation cd I did the console[2] I was told lspci couldn't be found.
Gnoppix had the following output:
0000:00:00.0 Host bridge: Intel Corp.: Unknown device 2770 (rev 02)
0000:00:01.0 PCI bridge: Intel Corp.: Unknown device 2771 (rev 02)
0000:00:1b.0 0403: Intel Corp.: Unknown device 27d8 (rev 01)
0000:00:1c.0 PCI bridge: Intel Corp.: Unknown device 27d0 (rev 01)
0000:00:1c.2 PCI bridge: Intel Corp.: Unknown device 27d4 (rev 01)
0000:00:1c.3 PCI bridge: Intel Corp.: Unknown device 27d6 (rev 01)
0000:00:1c.4 PCI bridge: Intel Corp.: Unknown device 27e0 (rev 01)
0000:00:1c.5 PCI bridge: Intel Corp.: Unknown device 27e2 (rev 01)
0000:00:1d.0 USB Controller: Intel Corp.: Unknown device 27c8 (rev 01)
0000:00:1d.1 USB Controller: Intel Corp.: Unknown device 27c9 (rev 01)
0000:00:1d.2 USB Controller: Intel Corp.: Unknown device 27ca (rev 01)
0000:00:1d.3 USB Controller: Intel Corp.: Unknown device 27cb (rev 01)
0000:00:1d.7 USB Controller: Intel Corp.: Unknown device 27cc (rev 01)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev e1)
0000:00:1f.0 ISA bridge: Intel Corp.: Unknown device 27b8 (rev 01)
0000:00:1f.1 IDE interface: Intel Corp.: Unknown device 27df (rev 01)
0000:00:1f.2 IDE interface: Intel Corp.: Unknown device 27c0 (rev 01)
0000:00:1f.3 SMBus: Intel Corp.: Unknown device 27da (rev 01)
0000:01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0141 (rev a2)
0000:02:00.0 Ethernet controller: Intel Corp.: Unknown device 108c (rev 03)
0000:02:00.2 IDE interface: Intel Corp.: Unknown device 108d (rev 03)
0000:02:00.3 Serial controller: Intel Corp.: Unknown device 108f (rev 03)
0000:02:00.4 0c07: Intel Corp.: Unknown device 108e (rev 03)
0000:07:05.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)


Gnoppix couldn't configure the network  either:
eth0: error fetching interface information: Device not found

I'm curious how you use the lspci output to resolve issues like this.

Thanks,
Daniel


Reply to: