LinuxQuestions.org - Loading initial ramdisk freeze

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - Loading initial ramdisk freeze (https://www.linuxquestions.org/questions/debian-26/loading-initial-ramdisk-freeze-935549/)

Loading initial ramdisk freeze

I need some help... i was cruising right along with my new Debian Squeeze installation... I had run through this completely: http://www.howtoforge.com/perfect-se...er-ispconfig-3

I was messing with getting the network setup properly and decided the console resolution was too small so I changed some grub configuration according to this: http://lists.debian.org/debian-user/.../msg00611.html

I had rebooted 3 or 4 times prior to changing the grub config without issue... after rebooting this time, the following happened:

Loading Linux 2.6.32-5-amd64 ...
Loading initial ramdisk ...

And that's it. Nothing else happens...

in Recovery mode, pressing e gets me this...

Code:

set gfxpayload=keep

insmod part_msdos

insmod ext2

set root='(hd0,msdos1)'

search --on-floppy --fs-uuid --set a5551ad8-0223-406b-909e-af3951302129

echo 'Loading Linux 2.6.32-5-amd64 ...'

linux /boot/vmlinuz=-2.6.32-5-amd64 root =UUID=a5551ad8-0223-406b-909e-af3951302129 ro single

echo 'Loading initial ramdisk'

initrd /boot/initrd.img-2.6.32-5-amd64

I am new to Linux, so i am very lost as to what could have happened.

Can anyone help?

Was the console running in frame buffer mode previously? I suspect what is happening when you see nothing happening is that the console and kernel do not agree on what the video mode is. Are you intending to use this in a text console or with X?

The question and answer was worked out here... http://www.linuxforums.org/forum/deb...tml#post885018

Hopefully it will help someone in the future...

Thanks for the response!

Quote:

Originally Posted by cbeyer (Post 4636556)

The question and answer was worked out here... http://www.linuxforums.org/forum/deb...tml#post885018

Hopefully it will help someone in the future...

Thanks for the response!

BAD LINK. You apparently copied an obfuscated URL text rather than the link itself, since the 3 dots that usually are used to do that were in the URL you provided. Using the right click button and selecting [Copy Link Location] usually gets it if the full URL is available.

Yup, sorry about that... it should work now!