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

Bug#681734: marked as done (Failed installation at Detect network hardware)

Your message dated Mon, 13 Aug 2012 06:22:46 +0200
with message-id <20120813042246.GC9733@mykerinos.kheops.frmug.org>
and subject line Re: Bug#681734: installation at Detect network hardware
has caused the Debian Bug report #681734,
regarding Failed installation at Detect network hardware
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.)


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

Boot method: USB stick, using Default and Expert install.
Image version:
http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-dvd/debian-wheezy-DI-b1-amd64-DVD-1.iso
Date: 15-Jul-2012

Machine:    Self-built with Biostar TZ68A+ mobo
Processor:  Intel i5-2500K
Memory:     8192MB DDR3 1600
Partitions: (fdisk -l from installed wheezy DI alpha 1)
Disk /dev/sda: 400.1 GB, 400088457216 bytes
255 heads, 63 sectors/track, 48641 cylinders, total 781422768 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0003e751

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048    31250431    15624192   83  Linux
/dev/sda2   *    31250432    31455231      102400    7  HPFS/NTFS/exFAT
/dev/sda3        31457280   124999679    46771200   83  Linux
/dev/sda4       125001726   781416447   328207361    5  Extended
/dev/sda5       125001728   140623871     7811072   82  Linux swap / Solaris
/dev/sda6       140625920   224511999    41943040    7  HPFS/NTFS/exFAT
/dev/sda7       224514048   781416447   278451200    7  HPFS/NTFS/exFAT


Output of lspci -knn (from installed wheezy DI alpha 1):
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor
Family DRAM Controller [8086:0100] (rev 09)
	Subsystem: Biostar Microtech Int'l Corp Device [1565:3108]
	Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller [8086:0112] (rev 09)
	Subsystem: Biostar Microtech Int'l Corp Device [1565:110d]
	Kernel driver in use: i915
00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series
Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
	Subsystem: Biostar Microtech Int'l Corp Device [1565:3108]
00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset
Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05)
	Subsystem: Biostar Microtech Int'l Corp Device [1565:3108]
	Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset
Family High Definition Audio Controller [8086:1c20] (rev 05)
	Subsystem: Biostar Microtech Int'l Corp Device [1565:8225]
	Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family
PCI Express Root Port 1 [8086:1c10] (rev b5)
	Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family
PCI Express Root Port 2 [8086:1c12] (rev b5)
	Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev
b5)
00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset
Family USB Enhanced Host Controller #1 [8086:1c26] (rev 05)
	Subsystem: Biostar Microtech Int'l Corp Device [1565:3108]
	Kernel driver in use: ehci_hcd
00:1f.0 ISA bridge [0601]: Intel Corporation Z68 Express Chipset Family LPC
Controller [8086:1c44] (rev 05)
	Subsystem: Biostar Microtech Int'l Corp Device [1565:3108]
00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 Series Chipset
Family SATA AHCI Controller [8086:1c02] (rev 05)
	Subsystem: Biostar Microtech Int'l Corp Device [1565:5207]
	Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series Chipset Family
SMBus Controller [8086:1c22] (rev 05)
	Subsystem: Biostar Microtech Int'l Corp Device [1565:3108]
	Kernel driver in use: i801_smbus
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)
	Subsystem: Biostar Microtech Int'l Corp Device [1565:230a]
	Kernel driver in use: r8169
02:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1042 SuperSpeed USB
Host Controller [1b21:1042]
	Subsystem: Device [174c:2104]
	Kernel driver in use: xhci_hcd
03:00.0 PCI bridge [0604]: Integrated Technology Express, Inc. Device
[1283:8893] (rev 10)

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

Initial boot:           [O]
Detect network card:    [E]
Configure network:      [ ]
Detect CD:              [O]
Load installer modules: [O]
Detect hard drives:     [ ]
Partition hard drives:  [ ]
Install base system:    [ ]
Clock/timezone setup:   [ ]
User/password setup:    [ ]
Install tasks:          [ ]
Install boot loader:    [ ]
Overall install:        [ ]

Comments/Problems:
The installer hung during the "Detect network hardware" step, as similarly
reported in #681610 and #681656. The "Detecting hardware" progress bar displays
briefly, then clears to an empty blue screen with a single white line at the
bottom. There is no further screen output. Pressing <enter> scrolls white lines
up from the bottom. A tail from an install log follows, as alternate consoles
2,3,4 still work.

This is a regression as this system was successfully installed with D-I alpha
and a later (~June 15) weekly. The Realtek Ethernet controller does not need
firmware to be loaded, although previous installers detected missing firmware
and prompted for it. Telling the installer to continue anyway resulted in a
successful installation. Such a prompt does not appear with the latest
(weekly/beta) test release, and installation cannot continue.

This same installer works fine on a different system, with different network
hardware, where it does not prompt for unnecessary firmware.

The Tail of the Syslog:
Jul 15 18:32:13 main-menu[430]: INFO: Menu item 'ethdetect' selected
Jul 15 18:32:13 net/hw-detect.hotplug: Detected hotpluggable network interface
lo
Jul 15 18:32:13 kernel: [   22.012494] r8169 Gigabit Ethernet driver 2.3LK-NAPI
loaded
Jul 15 18:32:13 kernel: [   22.012509] r8169 0000:01:00.0: PCI INT A -> GSI 16
(level, low) -> IRQ 16
Jul 15 18:32:13 kernel: [   22.012542] r8169 0000:01:00.0: setting latency timer
to 64
Jul 15 18:32:13 kernel: [   22.012618] r8169 0000:01:00.0: irq 46 for MSI/MSI-X
Jul 15 18:32:13 kernel: [   22.012892] r8169 0000:01:00.0: eth0:
RTL8168evl/8111evl at 0xffffc90000c7c000, 00:30:67:cb:4e:c7, XID 0c900800 IRQ 46
Jul 15 18:32:13 kernel: [   22.012894] r8169 0000:01:00.0: eth0: jumbo features
[frames: 9200 bytes, tx checksumming: ko]
Jul 15 18:32:13 net/hw-detect.hotplug: Detected hotpluggable network interface
eth0
Jul 15 18:32:15 check-missing-firmware: /dev/.udev/firmware-missing does not
exist, skipping
Jul 15 18:32:15 check-missing-firmware: /run/udev/firmware-missing does not
exist, skipping
Jul 15 18:32:15 check-missing-firmware: no missing firmware in
/dev/.udev/firmware-missing /run/udev/firmware-missing
Jul 15 18:32:15 kernel: [   23.900013] r8169 0000:01:00.0: eth0: unable to load
firmware patch rtl_nic/rtl8168e-3.fw (-2)
Jul 15 18:32:15 kernel: [   23.915017] r8169 0000:01:00.0: eth0: link down
Jul 15 18:32:15 kernel: [   23.915024] r8169 0000:01:00.0: eth0: link down
Jul 15 18:32:15 kernel: [   23.915411] ADDRCONF(NETDEV_UP): eth0: link is not
ready
Jul 15 18:32:16 check-missing-firmware: /dev/.udev/firmware-missing does not
exist, skipping
Jul 15 18:32:16 check-missing-firmware: missing firmware files
(rtl_nic/rtl8168e-3.fw) for r8169
Jul 15 18:32:16 kernel: [   25.055480] FAT-fs (sda): utf8 is not a recommended
IO charset for FAT filesystems, filesystem will be case sensitive!
Jul 15 18:32:16 kernel: [   25.159239] FAT-fs (sda): utf8 is not a recommended
IO charset for FAT filesystems, filesystem will be case sensitive!
Jul 15 18:32:16 kernel: [   25.255027] FAT-fs (sdb): utf8 is not a recommended
IO charset for FAT filesystems, filesystem will be case sensitive!
Jul 15 18:32:16 kernel: [   25.338836] FAT-fs (sdb): utf8 is not a recommended
IO charset for FAT filesystems, filesystem will be case sensitive!
Jul 15 18:32:16 kernel: [   25.362062] mount: sending ioctl 5310 to a partition!
Jul 15 18:32:16 kernel: [   25.362064] mount: sending ioctl 5310 to a partition!
Jul 15 18:32:16 kernel: [   25.402693] FAT-fs (sda1): utf8 is not a recommended
IO charset for FAT filesystems, filesystem will be case sensitive!
Jul 15 18:32:16 kernel: [   25.455575] mount: sending ioctl 5310 to a partition!
Jul 15 18:32:16 kernel: [   25.455577] mount: sending ioctl 5310 to a partition!
Jul 15 18:32:16 kernel: [   25.514440] FAT-fs (sda1): utf8 is not a recommended
IO charset for FAT filesystems, filesystem will be case sensitive!
Jul 15 18:32:17 kernel: [   25.531508] mount: sending ioctl 5310 to a partition!
Jul 15 18:32:17 kernel: [   25.531510] mount: sending ioctl 5310 to a partition!
Jul 15 18:32:17 kernel: [   25.574310] FAT-fs (sda2): utf8 is not a recommended
IO charset for FAT filesystems, filesystem will be case sensitive!
Jul 15 18:32:17 kernel: [   25.607264] mount: sending ioctl 5310 to a partition!
Jul 15 18:32:17 kernel: [   25.607266] mount: sending ioctl 5310 to a partition!
Jul 15 18:32:17 kernel: [   25.670092] FAT-fs (sda2): utf8 is not a recommended
IO charset for FAT filesystems, filesystem will be case sensitive!
Jul 15 18:32:17 kernel: [   25.727127] mount: sending ioctl 5310 to a partition!
Jul 15 18:32:17 kernel: [   25.727129] mount: sending ioctl 5310 to a partition!
Jul 15 18:32:17 kernel: [   25.773856] FAT-fs (sda3): utf8 is not a recommended
IO charset for FAT filesystems, filesystem will be case sensitive!
Jul 15 18:32:17 kernel: [   25.873642] FAT-fs (sda3): utf8 is not a recommended
IO charset for FAT filesystems, filesystem will be case sensitive!

--- End Message ---
--- Begin Message --- 
Quoting toby cabot (toby@caboteria.org):
> Package: installation-reports
> Severity: normal
> 
> 
> -- Package-specific info:
> 
> Boot method: USB memory stick prepared using the "flexible way"
> Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta1/amd64/iso-cd/debian-wheezy-DI-b1-amd64-netinst.iso
> Date: 2012-08-12
> 
> Machine: whitebox PC, AMD CPU, no floppy drive
> Partitions: <df -Tl will do; the raw partition table is preferred>
> 
> 
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> 
> Initial boot:           [O]
> Detect network card:    [ ]
> Configure network:      [ ]
> Detect CD:              [ ]
> Load installer modules: [ ]
> Detect hard drives:     [ ] 
> Partition hard drives:  [ ]
> Install base system:    [ ]
> Clock/timezone setup:   [ ]
> User/password setup:    [ ]
> Install tasks:          [ ]
> Install boot loader:    [ ]
> Overall install:        [ ]
> 
> Comments/Problems:
> 
> <Description of the install, in prose, and any thoughts, comments
>       and ideas you had during the initial install.>
> 
> I got similar observed behavior to what Don got, but different output
> on the f4 console:


This is a now well-known bug, probably in the Linux kernel, that got
worked around in mountmedia, after beta1 (and therefore in daily
images, too).

Aswe got tons of these bug reports, I'm hereby closing them as they
come now. Thanks for takign care to report and, with details you gave,
to confirm this is indeed this known problem.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: