Other Help Topics :: boot problem ramdisk

Try booting with mem=16M
however, if you used shared memory i.e. with your video, etc. subtract amount from 16 and use that instead.

Don't worry about the undefined mode # for now, but that's usually fixed by specifying the geometry to fit your monitor (by vga= )

Quote (^thehatsrule^ @ Nov. 01 2006,17:54)

Try booting with mem=16M
however, if you used shared memory i.e. with your video, etc. subtract amount from 16 and use that instead.

boot: dsl mem=16M

I tried this and I still get the same :-(

Quote

Don't worry about the undefined mode # for now, but that's usually fixed by specifying the geometry to fit your monitor (by vga= )

Even if I leave it as is (press space) or choose any of the modes, the result is the same...

Hope you didn't run out of ideas :-)

Are you sure you aren't using shared memory anywhere?
Maybe try booting with mem=12M - try combinations with the superlowram/failsafe/etc. Maybe you should also try booting directly to console first (dsl 2).

Hm, did you try like vga=787 etc? Doesn't matter anyways atm. (maybe you need to use fb modes)

Also, did you check if your DSL media was corrupt, or if it worked on another machine?

I am quite sure there is no shared ram. I mean that there is no audio or network or modem devices on the mainboard. I also have mounted a graphics card, which previoulsy worked with debian and X on this machine.

Is there any way to identify the usage of shared memory?

Also even if I try vga=787 and others I still get the indefined mode number...

I had previously checked the md5sum of both floppy and cd. I now tried the cd on my AMD sempron and it works fine. Now that I have seen DLS running, I must admit it's quite cool! Look what 50M of bytes can do :-)

I just noticed that for hdc "QUANTUM FIREBALL1280A, ATA DISK drive" (my hard drive) dmesg says:

hdc: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: task_no_data_intr: error=0x04 { DriveStatusError }

Could there something be wrong with my hd drive? But then how does it creates /etc/fstab?

"mounted" cards doesn't mean that it doesn't use shared memory afaik...

You can output `lspci -v` maybe.

You'll probably have to manually compute a code for your monitor/video if the general vga or fb codes don't work. What type of monitor are you using?

Hm, `cat /etc/fstab`? Maybe try disabling your hdd in your bios before trying to boot again.

Wonder if all these problems are because of one thing...

Next Page...
original here.