OK. I fiddled some more with it (a few hours). None of the parameters you gave me worked. Same problem. With the enterprise kernel there is a small difference which I noticed just now (or at least in the 12mdk enterprise kernel from cooker). It lights Scroll lock and Caps lock but doesn't blink. They just stay on. I tried booting failsafe and what do you know... It booted and reported my memory ok (1.032.900k). Then I tried adjusting the 12mdk parameters one by one to reflect the ones in failsafe and I isolated this one to be causing the kernel panic: vga=788 I switched again all the parameters to the original from the 12mdk enterprise kernel but left this vga=788 out and it booted with no problem. What the heck is/does vga=788 and why does it cause PCs to freeze when 1G memory installed?!? :/
Best regards, Adrian ----- Original Message ----- From: "Todd Lyons" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, March 08, 2003 2:02 AM Subject: Re: [expert] new memory 512MB module (total 1024MB) and linux won't boot and also installer doesn't work anymore > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Adrian Golumbovici wrote on Fri, Mar 07, 2003 at 11:30:00AM +0100 : > > > I just bought another 512MB DDR PC333 module for my PC and now my linux > > won't boot anymore. I tried an update from CD, installer doesn't work > > either. Memory just went through a 3 hours memtest86 and no error found. > > Windows handles it OK (I have a dual boot with Win2k pro). It just loads > > lilo, but when selecting linux it goes into a black screen and doesn't react > > to any commands. The Scroll lock and Caps lock leds are blinking > > continuously. :( > > Probably not a useful question, but is it at the rate of 1/2 second per > blink? > > If you look at the /usr/src/linux/kernel/panic.c file, you'll see that > something failed and called the panic_blink() function. It's a function > that never stops. The panic_blink() function is actually defined in > /usr/src/linux/drivers/char/pc_keyb.c and it just alternates the mode of > the 0x01 and 0x04 bits, which are Scroll Lock and Caps Lock > respectively. > > Now what called that is quite possibly something that is going to be a > lot more difficult to find out. Try passing 'noapic noacpi nodma > ide0=nodma nomce acpi=off pci=biosirq' and see if _something_ happens. > > Basically the linux kernel has a VERY big problem with your motherboard. > > Blue skies... Todd > - -- > Todd Lyons -- MandrakeSoft, Inc. http://www.mandrakesoft.com/ > UNIX was not designed to stop you from doing stupid things, because > that would also stop you from doing clever things. -- Doug Gwyn > Mandrake Cooker Devel Version, Kernel 2.4.21-0.12mdk > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.1 (GNU/Linux) > > iD8DBQE+aUE/lp7v05cW2woRAmrFAJ9rZAwO485Q8Oq1Urt591PsRwpWDwCgxgzG > ih7LRyXknMzxqO0ztJfHdSw= > =N6KH > -----END PGP SIGNATURE----- > > ---------------------------------------------------------------------------- ---- > Want to buy your Pack or Services from MandrakeSoft? > Go to http://www.mandrakestore.com >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
