Quote:
Originally Posted by mjolnir
Here is a thread where someone appears to have had some success with a similar problem:....
|
[SOLVED] topic doesn't exist anymore on that sugg-link....
I've look everywhere to only dead-end.... My iso was still on an other machine, so I used IzArc to see what was in its boot-loader file and found something similar to what I've seen AS solution on all sites but to no avail.
If the problem is memory detection, why hasn't anyone that made that boot loader made it so that it would look for more mem than just 256k like their bootloader say to look for? They could have made it so there is already a "swap" partition on the drive which 90% of linux users already have made or windows user will make (if they really willing to try linux)
My solution was this: livecd=livecd initrd=initrd.gz apci=on vga=788 vmalloc=ram splash=verbose
The machine I've put this in is an old 1999 64M 20GB GA-6MWW7 mobo 700MH proc where I've put 512M ram and a slaved 40GB old HDD for a home partition.
I like messing with old machine. VmWare or Vbox will never come close to what a real machine is REALLY able to do/handle

)
I'm a newbe (so much I don't even know how to spell "newbe") But I learn on real turf. Not on virtual machine. The machine is virtual enough without the need to run another one in it ahahahah
vga is not important. But the vmalloc was the key factor for me here. Instead of their standard vmalloc=256M (or whatever other boot file might have in), I decided to use ram which it will make anyway even if no ram partition is there.
I must have thrown dozens of perfectly good livecds to trash because some threads said "bad-burn"
If I ever dare to waste the time, I'll hack that file before the next burn if it needs to. I'll look into a normal no-bug iso that boot to see if the solution I just found is somewhat already in them or even maybe they've simply did leave that "vmalloc" out of the way of their boot file.
Hope this helps a few
Peace
Ghis