Bug#236487: Debian-installer (sarge) hangs on boot

[stappers@stappers.nl (Geert Stappers)]

On Sat, Mar 06, 2004 at 04:12:01PM +0100, Marcus Jacobs wrote:
 in a private message
> Am Samstag, 6. März 2004 15:09 schrieben Sie:
> > On Sat, Mar 06, 2004 at 02:29:00PM +0100, Marcus Jacobs wrote:
 <snip/>
> > > Kernel 2.2 works fine, so this may be a kernel issue?
> >
> > Could be.
> >
> > Please run
> >  lspci
> > and
> >  lspci -n
> > when the computer is running the 2.2 kernel
> >
> > > Bye, Marcus
> >
> > Geert Stappers
> 
> Well, I already had this issue a few months ago and I did a 2.2 install and 
> then upgraded to 2.4. I just gave it another try today and it still didn't 
> work. So , I can only give you the output with the 2.4 kernel. Maybe this 
> helps as well. 

That does read that you have a running 2.4 kernel on your computer.

> 
> Marcus Jacobs
> 
> 
> 
> Output of lspci:
> 00:00.0 Host bridge: Intel Corp. 82850 850 (Tehama) Chipset Host Bridge (MCH) 
> (rev 04)
> 00:01.0 PCI bridge: Intel Corp. 82850 850 (Tehama) Chipset AGP Bridge (rev 04)
> 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB PCI Bridge (rev 04)
> 00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 04)
> 00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 04)
> 00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 04)
> 01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 420] 
> (rev a3)
> 02:01.0 USB Controller: VIA Technologies, Inc. USB (rev 50)
> 02:01.1 USB Controller: VIA Technologies, Inc. USB (rev 50)
> 02:01.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51)
> 02:02.0 USB Controller: VIA Technologies, Inc. USB (rev 50)
> 02:02.1 USB Controller: VIA Technologies, Inc. USB (rev 50)
> 02:02.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51)
> 02:07.0 PCI bridge: Texas Instruments PCI2050 PCI-to-PCI Bridge (rev 01)
> 02:08.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 04)
> 02:08.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 
> 01)
> 02:0c.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 10)
> 03:05.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 
> Controller (PHY/Link)
> 03:06.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
> 
> 
> Output of lspci -n:
> 00:00.0 Class 0600: 8086:2530 (rev 04)
> 00:01.0 Class 0604: 8086:2532 (rev 04)
> 00:1e.0 Class 0604: 8086:244e (rev 04)
> 00:1f.0 Class 0601: 8086:2440 (rev 04)
> 00:1f.1 Class 0101: 8086:244b (rev 04)
> 00:1f.3 Class 0c05: 8086:2443 (rev 04)
> 01:00.0 Class 0300: 10de:0172 (rev a3)
> 02:01.0 Class 0c03: 1106:3038 (rev 50)
> 02:01.1 Class 0c03: 1106:3038 (rev 50)
> 02:01.2 Class 0c03: 1106:3104 (rev 51)
> 02:02.0 Class 0c03: 1106:3038 (rev 50)
> 02:02.1 Class 0c03: 1106:3038 (rev 50)
> 02:02.2 Class 0c03: 1106:3104 (rev 51)
> 02:07.0 Class 0604: 104c:ac28 (rev 01)
> 02:08.0 Class 0401: 1102:0002 (rev 04)
> 02:08.1 Class 0980: 1102:7002 (rev 01)
> 02:0c.0 Class 0200: 8086:1229 (rev 10)
> 03:05.0 Class 0c00: 104c:8023
> 03:06.0 Class 0480: 1131:7146 (rev 01)
> 

I'm not aware of hardware components that cause d-i hang,
with your information we have a list of possible ones, thanks.

I don't known how to disable the hardware scan.

Try booting with 'expert' as a boot prompt option.


When replying, keep the bugreport number in the headers.


Cheers
Geert Stappers