|
Bugzilla – Full Text Bug Listing |
| Summary: | 10.0 Live DVD doesn't boot with 224Mb RAM | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Andreas Hasenack <andreas> |
| Component: | Kernel | Assignee: | Hubert Mantel <mantel> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Minor | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
cat /proc/cpuinfo
dmesg output free output lspci -v output oom-killer.jpg |
||
|
Description
Andreas Hasenack
2005-10-07 15:09:00 UTC
iirc, the kernel can't automaticall detect shared ram, so you must boot with "mem=224m". -> kernel I'll try that option and report back. Tried with "mem=224m" and "mem=220M" and got the same error. I may post some pictures later. The error is right after the first "cloop" line and starts with "oom-killer". It's difficult to write it down because it keeps happening (for the "cp" process, "rm" and others I couldn't write down). I'll try to deactivate graphical boot now to see how much memory the kernel is recognizing on this machine (it's at the very top of the screen I think and I can't see it because it takes some time to switch to verbose mode). It scrolls off too fast. Anyway, I'm attaching some info about the machine (lspci, cpuinfo, etc) when booted into somewhing else. Created attachment 51824 [details]
cat /proc/cpuinfo
Created attachment 51835 [details]
dmesg output
Created attachment 51836 [details]
free output
Created attachment 51837 [details]
lspci -v output
I also tried with other values lower than 224m (such as 220m), same error. Created attachment 51937 [details]
oom-killer.jpg
dmesg shows: "Linux version 2.6.12-12mdksmp (apatard@n1.mandriva.com) (gcc version 4.0.1 (4.0.1-5mdk for Mandriva Linux release 2006.0))" Please use the SUSE kernel compiled with the SUSE compiler for SUSE bugreports. (In reply to comment #11) > dmesg shows: > "Linux version 2.6.12-12mdksmp (apatard@n1.mandriva.com) (gcc version 4.0.1 > (4.0.1-5mdk for Mandriva Linux release 2006.0))" > > Please use the SUSE kernel compiled with the SUSE compiler for SUSE > bugreports. Did you even look at the fscking screen shot? The fscking suse system won't even boot! 256 MB of RAM is required for the Live CD. So the "fscking suse system" won't work on your "fscking hardware". Thanks for the nice words and the invalid "bug" report. You are welcome. Just don't assume all bug reporters are idiots like was done comment #11. The first sentence of your comment #13 would have settled this nicely (I can live with this restriction: see my last sentence in comment #1), but now I obviously won't care anymore to report bugs. I don't assume all bug reporters are idiots. I did not even write comment #11. I don't care whether you are filing bug reports or not. But I'm sure I won't work on reports that use insulting language. Now go somewhere else and don't waste my time with your whining and your oh-so-cool "fscking" language. I have some babies at home, don't need that at work too. If you cannot hehave, just shut up! |