Bug#454641: more details

2007-12-07 Thread crosvera
Here is more info:

---lsb-release---
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=lenny (installer build 20071125-10:54)
X_INSTALLATION_MEDIUM=cdrom
-

arch= x86_64

now lspcis are from net-install

---lspci -nn
00:00.0 RAM memory [0500]: nVidia Corporation Unknown device [10de:0547] (rev 
a2)
00:01.0 ISA bridge [0601]: nVidia Corporation Unknown device [10de:0548] (rev 
a2)
00:01.1 SMBus [0c05]: nVidia Corporation Unknown device [10de:0542] (rev a2)
00:01.2 RAM memory [0500]: nVidia Corporation Unknown device [10de:0541] (rev 
a2)
00:01.3 Co-processor [0b40]: nVidia Corporation Unknown device [10de:0543] (rev 
a2)
00:02.0 USB Controller [0c03]: nVidia Corporation Unknown device [10de:055e] 
(rev a2)
00:02.1 USB Controller [0c03]: nVidia Corporation Unknown device [10de:055f] 
(rev a2)
00:04.0 USB Controller [0c03]: nVidia Corporation Unknown device [10de:055e] 
(rev a2)
00:04.1 USB Controller [0c03]: nVidia Corporation Unknown device [10de:055f] 
(rev a2)
00:06.0 IDE interface [0101]: nVidia Corporation Unknown device [10de:0560] 
(rev a1)
00:07.0 Audio device [0403]: nVidia Corporation Unknown device [10de:055c] (rev 
a1)
00:08.0 PCI bridge [0604]: nVidia Corporation Unknown device [10de:0561] (rev 
a2)
00:09.0 IDE interface [0101]: nVidia Corporation Unknown device [10de:0550] 
(rev a2)
00:0a.0 Ethernet controller [0200]: nVidia Corporation Unknown device 
[10de:054c] (rev a2)
00:0c.0 PCI bridge [0604]: nVidia Corporation Unknown device [10de:0563] (rev 
a2)
00:0e.0 PCI bridge [0604]: nVidia Corporation Unknown device [10de:0563] (rev 
a2)
00:12.0 VGA compatible controller [0300]: nVidia Corporation Unknown device 
[10de:0533] (rev a2)
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration [1022:1100]
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Address Map [1022:1101]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
DRAM Controller [1022:1102]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control [1022:1103]
01:09.0 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd Unknown device [1180:0832] 
(rev 05)
01:09.1 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 
SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 22)
01:09.2 System peripheral [0880]: Ricoh Co Ltd Unknown device [1180:0843] (rev 
12)
01:09.3 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host 
Adapter [1180:0592] (rev 12)
01:09.4 System peripheral [0880]: Ricoh Co Ltd xD-Picture Card Controller 
[1180:0852] (rev 12)
07:00.0 Ethernet controller [0200]: Atheros Communications, Inc. Unknown device 
[168c:001c] (rev 01)
--

-lspci -nnv--
00:00.0 RAM memory [0500]: nVidia Corporation Unknown device [10de:0547] (rev 
a2)
Subsystem: Acer Incorporated [ALI] Unknown device [1025:0127]
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities: [44] HyperTransport: Slave or Primary Interface
Capabilities: [dc] HyperTransport: MSI Mapping

00:01.0 ISA bridge [0601]: nVidia Corporation Unknown device [10de:0548] (rev 
a2)
Subsystem: Acer Incorporated [ALI] Unknown device [1025:0127]
Flags: bus master, 66MHz, fast devsel, latency 0
I/O ports at 1d00 [size=256]

00:01.1 SMBus [0c05]: nVidia Corporation Unknown device [10de:0542] (rev a2)
Subsystem: Acer Incorporated [ALI] Unknown device [1025:0127]
Flags: 66MHz, fast devsel, IRQ 10
I/O ports at 3080 [size=64]
I/O ports at 3040 [size=64]
I/O ports at 3000 [size=64]
Capabilities: [44] Power Management version 2

00:01.2 RAM memory [0500]: nVidia Corporation Unknown device [10de:0541] (rev 
a2)
Subsystem: nVidia Corporation Unknown device [10de:cb84]
Flags: 66MHz, fast devsel

00:01.3 Co-processor [0b40]: nVidia Corporation Unknown device [10de:0543] (rev 
a2)
Subsystem: Acer Incorporated [ALI] Unknown device [1025:0127]
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 11
Memory at f420 (32-bit, non-prefetchable) [size=512K]

00:02.0 USB Controller [0c03]: nVidia Corporation Unknown device [10de:055e] 
(rev a2) (prog-if 10)
Subsystem: Acer Incorporated [ALI] Unknown device [1025:0127]
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 20
Memory at f4486000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2

00:02.1 USB Controller [0c03]: nVidia Corporation Unknown device [10de:055f] 
(rev a2) (prog-if 20)
Subsystem: Acer Incorporated [ALI] Unknown device [1025:0127]
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 18
Memory at f4489000 

Bug#454641: more details

2007-12-07 Thread Frans Pop
On Friday 07 December 2007, crosvera wrote:
 syslog it's attached

Thanks for the additional info. I think we can now say this is a kernel
problem. The lspci info showed that the IDE controller should be supported
by ahci and your lsmod output shows that that module is loaded.

If I look at your syslog, I see the following:
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 cmd 0xc21ec100 ctl 0x bmdma 
0x irq 1277
ata2: SATA max UDMA/133 cmd 0xc21ec180 ctl 0x bmdma 
0x irq 1277
dma 0x irq 1277
ata4: SATA max UDMA/133 cmd 0xc21ec280 ctl 0x bmdma 
0x irq 1277
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2: SATA link down (SStatus 0 SControl 300)
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)

This shows that the driver is loaded correctly and sees that there is a
something connected to the port ata1.

However, compare that to the dmesg output from my own system (I have 2 SATA
harddisks and a SATA DVD-RW):
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0x903c4100 irq 1274
ata2: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0x903c4180 irq 1274
ata3: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0x903c4200 irq 1274
ata4: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0x903c4280 irq 1274
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-7: HDT722516DLA380, V43OA96A, max UDMA/133
ata1.00: 321672960 sectors, multi 16: LBA48 NCQ (not used)
ata1.00: configured for UDMA/133
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[...]
ata4: SATA link down (SStatus 0 SControl 300)
scsi 0:0:0:0: Direct-Access ATA  HDT722516DLA380  V43O PQ: 0 ANSI: 5
scsi 1:0:0:0: Direct-Access ATA  HDT722516DLA380  V43O PQ: 0 ANSI: 5
scsi 2:0:0:0: CD-ROMOptiarc  DVD RW AD-7170S  1.00 PQ: 0 ANSI: 5

Clearly something is missing in your output: the kernel fails to detect the
harddisk itself.

There is a pretty good chance this has been fixed in later kernels, so
that should be checked first.

There are two things you could try:
- try changing the BIOS setting for your SATA controller and see if you
  can install then; if that works, install the 2.6.23 kernel from unstable,
  change the BIOS settings back and see if the disk is recognized then
- try an installation using this unofficial Etch image, which already has a
  2.6.23 kernel: http://kmuto.jp/debian/d-i/ (etch-custom-1013.iso for amd64)

If the 2.6.23 kernel does not detect the disk either, a mail to the
upstream kernel developers would be the next step.


Did you have to manually load the forcedeth module again? From the syslog
it seems to be loaded correctly automatically:
main-menu[1168]: INFO: Menu item 'ethdetect' selected 
net/hw-detect.hotplug: Detected hotpluggable network interface lo
kernel: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60.
kernel: ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 20
kernel: ACPI: PCI Interrupt :00:0a.0[A] - Link [LMAC] - GSI 20 (level, 
low) - IRQ 20
kernel: PCI: Setting latency timer of device :00:0a.0 to 64
kernel: forcedeth: using HIGHDMA
kernel: :00:0a.0: Invalid Mac address detected: db:88:c2:24:1b:00
kernel: Please complain to your hardware vendor. Switching to a random MAC.
kernel: eth0: forcedeth.c: subsystem: 01025:0127 bound to :00:0a.0
net/hw-detect.hotplug: Detected hotpluggable network interface eth0

Note the line about Invalid Mac address though! The fact that a random
MAC gets assigned could cause problems with udev assigning an interface
name on reboots.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]