Bug 228508

Summary: Installation failure on VIA P4M800 Pro
Product: [openSUSE] openSUSE 10.2 Reporter: Jeronimo Martinez <xblackfire>
Component: InstallationAssignee: Steffen Winterfeldt <snwint>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Critical    
Priority: P5 - None CC: xblackfire
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Screenshot boot install dvd failure
oops
boot messages before reboot

Description Jeronimo Martinez 2006-12-14 05:25:19 UTC
kernel oops booting with the DVD SUSE 10.2 GM (final) 

checksum of DVD is OK, tested in other machine with diferent hardware and works sucessfull 

at boot, is showed a box with these values 

data       prog
:           0: ffffffff .5
:           1: 1cd3 .5
:           2: 345c .15
:           3: 3457 .5
:           4: 545b .5
:           5: 52fc .15
:           6: 52ce .15
0: 9c288. a 7: 52cb .5

err f
ip 50c2           55.7

pressing the F2 key allow pass parameters to kernel, enter failsafe, linux and initrd load next the messages is show "checking if image initramfs it isn't (bad gzip magic number) looks like an initrd"  and then machine reebot itsefl

no allways allow to pass parameters to kernel in other boots show the box and a background image of igloo freeze 

Hardware 
Procesador: Intel Pentium 4 HT, 3.0 GHz 
Memory:  512 MB Ram
HD:      Maxtor  6Y080L0  (80 GB, 7200 RPM, Ultra-ATA/133)
         Seagate ST3160812AS  (160 GB, 7200 RPM, SATA-II)
Video:   NVIDIA GeForce4 MX 4000  (128 MB)
Motherboard chipset:  VIA P4M800 Pro / South bridge: VIA VT8237
Sata Raid Controller VT8237

Note: 
Windows XP is installed in the IDE drive
FreeBSD and Fedora6 is installed in the SATA drive
ALL OS works well
Comment 1 Greg Kroah-Hartman 2006-12-14 18:46:08 UTC
Can you type in the oops message that you see?  Or take a picture of it?

Without it, it's going to be very tough to determine what happened here :(
Comment 2 Jeronimo Martinez 2006-12-16 21:56:21 UTC
Created attachment 110018 [details]
Screenshot boot install dvd failure
Comment 3 Jeronimo Martinez 2006-12-16 21:57:30 UTC
Created attachment 110019 [details]
oops
Comment 4 Jeronimo Martinez 2006-12-16 21:58:48 UTC
Created attachment 110020 [details]
boot messages before reboot
Comment 5 Alex Lau 2006-12-19 04:29:59 UTC
GregKH 
China team already work with this mother board before. The problem is vary ... and depend on the installation some hardware work ok and the installation is fine. But not all. We have one board connected to different hardware and have different experience, I can't explain why yet. 
Comment 6 Lars Marowsky-Bree 2007-01-09 17:32:01 UTC
This doesn't make sense.

All suggests this is not a kernel issue, but within the bootloader failing to setup the boot process correctly.

Re-assigning to grub maintainer.
Comment 7 Torsten Duwe 2007-02-02 14:35:24 UTC
Dear bug reporter / screening team,
due to the increasing number of grub "bugs" that are most likely
unrelated to grub's basic functionality but nevertheless assigned to me,
I took the time to write up some explanations for your kind consideration.
Please have a look at http://en.opensuse.org/Bugs/grub
Comment 8 Lars Marowsky-Bree 2007-02-12 11:24:20 UTC
Torsten, the error message in comment #3 and comment #2 comes from grub, so it can't really be a kernel bug (kernel not running yet). So, what's your suggestion about where this bug might linger? I read the link you provided, but I'm still not sure ...
Comment 10 Steffen Winterfeldt 2007-02-19 13:50:02 UTC
Looks like a memory corruption bug. :-(

Jeronimo, if you boot from DVD hold down the SHIFT key while the
bootloader starts.

Answer both questions with 'y'. Then it says:

Initializing gfx code...
     mem area 0: number1 - number2
     mem area 1: ...
     ...

Please tell me those two numbers (or just make a screenshot - whatever is
easier for you).

Does it work if you turn off the display size detection (answer second
question with 'n')?

Does it work if you skip graphics completely (say 'n' to the first question)?
Comment 11 Jeronimo Martinez 2007-02-20 03:40:17 UTC
Results:

Initializing gfx code...
     mem area 0: 0x00053410 - 0x0009f000

Load boot graphics(y/n): n
boot in console mode but the result are the same.

Detect display size(y/n): n
same results 

both intent fails. just as in screenshots attachments
Comment 12 Steffen Winterfeldt 2007-02-20 16:22:24 UTC
If you can't boot even with plain isolinux (I assume 'same results' means
comment 4?) there is likely a bios problem preventing the initrd to
be loaded properly.

Could be the 16MB-hole problem seen in bug 211094. Please check your
bios settings.
Comment 13 Jeronimo Martinez 2007-02-21 02:23:44 UTC
is the same bug(https://bugzilla.novell.com/show_bug.cgi?id=211094) disabling the memory hole in the bios settings allow to boot normaly from the dvd. 

*** This bug has been marked as a duplicate of bug 211094 ***