On Saturday 08 March 2003 03:03 am, Adrian Golumbovici wrote: > I left it for a couple of minutes, but with no reaction and those lights on > keyboard lighting (which normally don't light) I figured it crashed. > Anyway, if that mode is not supported by my video card, why does that > setting work with 512MB but it freezes as long as it has 1024MB RAM?!? > > Best regards, > Adrian > ----- Original Message ----- > From: "et" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Saturday, March 08, 2003 1:01 PM > Subject: Re: [expert] new memory 512MB module (total 1024MB) and linux > won't boot and also installer doesn't work anymore > > On Saturday 08 March 2003 06:48 am, Adrian Golumbovici wrote: > > 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 > > that number is a video mode, were was it that you changed it (in lilo? > compileing a kernel? how long did you let the "lockup" sit? you may have > just > been booting using a mode your video card could not do, so rather than do a > display that would hurt the card, you got no display, and it "may" have > come back had you let it sit 3 mins with a working X, or at leasta command > prompt > > > > > --------------------------------------------------------------------------- >- ---- > > > Want to buy your Pack or Services from MandrakeSoft? > > Go to http://www.mandrakestore.com
That happens because your BIOS is mapping video framebuffer across your memory.... In other words the BIOS is misreporting the bridge mappings. Civileme
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
