Bug 204749

Summary: Installation locks after loading kernel
Product: [openSUSE] openSUSE 10.2 Reporter: Antoon Tolboom <atolboo>
Component: InstallationAssignee: E-mail List <kernel-maintainers>
Status: RESOLVED INVALID QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: atolboo
Version: Alpha 4   
Target Milestone: ---   
Hardware: i686   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Antoon Tolboom 2006-09-10 10:56:56 UTC
I am trying to install openSUSE 10.2 Alpha 4 but it locks after the Linux Kernel is loaded.
Selecting the F3 800x600 or 1024x768 or 1280x1024 mode results in a black screen after the kernel is loaded.
F3 Text Mode or VESA mode results in a screen with a lot of lines scrolling over the screen after the kernel is loaded and stops with:
NET:Registered protocol family 2.
Perhaps this related to bug 204647.
A check of the CD in SUSE 10.1 Yast>Mediacheck gives the result OK.
Comment 1 Andreas Jaeger 2006-09-12 19:25:12 UTC
Please read: http://en.opensuse.org/Bugs/Kernel
and send us the kernel output.

What kind of system is this?  A VM or real hardware?
Comment 2 Antoon Tolboom 2006-09-13 08:58:46 UTC
As I am not an expert I do not know what VM means.
The Hardware is a normal PC with the following specifications:
694T Pro (MS-6309 v5.X) ATX mainboard with Intel Celeron 1.2GHz CPU
512MB ram
AGP video card: ATI RV280 [Radeon 9200 PRO] 128MB
As the keyboard completely locks (Numlock led is on)(Cntrl+Alt+Delete does not work) I do not know how to produce a kernel output.
The only thing I can do is to push the Reset button on the PC.
The following is the compleet contents of the last screen in Text Mode F3.
------------------------------------------------------------------------
weird, boot CPU (#0) not listed by the BIOS.
Total of 1 processors activated (2420.31 BogoMIPS).
Brought up 1 CPUs
migration_cost=0
NET: Registered protocol family 16
PCI: PCI BIOS reversion 2.10 entry at 0xfd51, last bus=1
PCI:Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter disabled.
Linu Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
PnPBIOS: Scanning system for PnP BIOS support...
PnPBIOS: Found PnP BIOS installation structure at 0xc00f7430
PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0x6474, dseg 0xf000
PnPBIOS: 14 nodes repoted by PNP BIOS; 14 recorded by driver
PCI: Probing PCI hardware
PCI quirk: region 0x00-0c7f claimed by vt82c686 HW-mon
PCI quirk: region 0400-040f claimed by vt82c686 SMB
PCI: Using ITQ router VIA [1106/0686] at 0000:00:07.0
PCI: Bridge: 0000:00:01.0
  IO window: 6000-6fff
  MEM window: dfc00000-dfvfffff
  PREFETCH window: bfa00000-dfafffff
NET: Registered protocol family 2
------------------------------------------------------------------------
I hope this info will help.
Comment 3 Antoon Tolboom 2006-09-20 20:03:14 UTC
In the meantime I know what VM is and I can tell you that it is an installation on real hardware.
I have also done this installation on a old HP Kayak PC and there the problem didnot show.
On the 694T Pro (MSI) PC I have installed SUSE 10.0 and 10.1 and Mandriva and Knoppix and Kanotix and Fedora without any problem but 10.2 Alpha4 gives the above mentioned problem.
Comment 4 Greg Kroah-Hartman 2006-10-03 07:15:09 UTC

*** This bug has been marked as a duplicate of bug 202079 ***
Comment 5 Antoon Tolboom 2006-10-11 08:06:30 UTC
I have tried the installation with openSUSE 10.2 Alpha 5 and it shows the same behaviour as Alpha 4.
This means that the problem is not solved.
Comment 6 Antoon Tolboom 2006-10-15 20:08:15 UTC
Because of Comment #5 Iam reopening this bug.
Comment 7 Antoon Tolboom 2006-10-27 19:19:55 UTC
I have tried the installation with openSUSE 10.2 Beta 1 and it shows the same
behaviour as Alpha 4 and Alpha 5.
This means that the problem is not solved.
Comment 8 Antoon Tolboom 2006-11-13 19:52:29 UTC
I have tried to install Beta 2 and it shows the same problem as Alpha 4/5 and Beta 1.
Comment 9 Jeff Mahoney 2006-11-28 20:22:16 UTC
We've released RC1. Can you try to reproduce with that, and if that also fails, try using the "noacpi" parameter on the kernel command line?
Comment 10 Jeff Mahoney 2006-11-28 21:30:07 UTC
Correction; acpi=off
Comment 11 Antoon Tolboom 2006-11-29 20:07:12 UTC
RC1 gives the same problem.
I have found the source of the problem.
It is a problem in my motherboard.
When I remove one of the two hdd, the problem is gone.
I think it has to do with busdrivers.
I am going to look for a new motherboard now.
Sorry for the inconvenience I caused to you.
Comment 12 Greg Kroah-Hartman 2006-11-30 00:17:07 UTC
No problem, thanks for letting us know.