Bug 139344 - Live disk wont load with 768mb of ram .
Summary: Live disk wont load with 768mb of ram .
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Other (show other bugs)
Version: Final
Hardware: x86 SuSE Linux 10.0
: P5 - None : Critical
Target Milestone: ---
Assignee: E-mail List
QA Contact: Adrian Schröter
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-15 12:45 UTC by David Bingham
Modified: 2006-01-02 14:36 UTC (History)
0 users

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Bingham 2005-12-15 12:45:38 UTC
As boot process starts it flashes message "......Suse need at least 256mg of main ram reboot" . System details

mobo: Asus A7A
Processer: Athlon 1400
Ram installed: 768 DDR 266
Comment 1 Michael Gross 2005-12-15 12:54:27 UTC
Please be more specific. It would be helpful to see the boot messages (you can make a picture and attach it here). Probably your BIOS reports a wrong amount of memory. Try booting with mem=768M (advanced options in the GRUB menu). 
Comment 2 David Bingham 2005-12-15 22:31:56 UTC
I have just sent you an e mail. To recap all that happens is I load the Suse 10 Live eval disk and reboot there is a pause and then a get a graphical welcome to suse screen. It then jumps to the next graphical screen and immediately I get the message flashed across. The only way to get out of that screen is to hit return and then it reboots and I get to the same point again. I have recently tried loading a Knoppix live cd and that confirmed it had found the 768mg of ram. As for access to Grub, I don't know how to get past these graphical screens to find out the specific loading messages. I have tried hitting f1, f2 and f3 as it loads the graphical screens but it makes no difference. Please let me know if there is a way through this and then I might be able to give you some meaningful information.
Comment 3 Michael Gross 2005-12-19 17:31:07 UTC
Hello David.

Pressing F2 during boot should work, but you can also boot with splash=verbose (get into the advanced options menu in the GRUB bootloader and enter this into the textline, all keys are labeled). This will boot with all boot messages unhidden, there you will see the actual error. Also in this line you can add the option mem=768M which will tell the system how much RAM is installed in the case of a BIOS error, which would work around this problem and should result in a proper boot. And please don't write emails to me but use bugzilla. I will get an email-copy of each comment you write.
Comment 4 Martin Lasarsch 2006-01-02 14:36:32 UTC
i will close the bug now, please reopen if you tried the stuff from comment #3