hello dear linux-experts,




loading linux 3.12.53-40-desktop
error _ file Boot/vmzlinuz-3.12.53-40-desktop not found
loading initial ramdisk
error you need to load the kernel first
press any key to continue


if i press a key i get the following page -as an overview:

opensuse 12.3 with linux 3.12
opensuse 12.3 with linux 3.12
opensuse 12.3 with linux 3.11
opensuse 12.3 with linux 3.11


but no entry helps here - i am lost since this is a loop!!!!

well i think i need to have the filesave mode.
How to access failsafe mode from bootloader in openseuse 13.2

i need to do some erasings in the log-files since the system does not start correcly. #

Question i need to access the comand line - how to do this!?


btw: need to erase the logfiles:


1. rm -rf /var/log/*
2. dmesg -c
3. reboot Since this works,

this would be possible too. - if logrotate is installed..

sudo /etc/cron.daily/logrotate


- therefore i am in need to get to the commandline

note: the systems does not start regularily

To boot in any mode you need to load a kernel, what bootloader you are using? Grub? You can use Grub search function to locate an existing kernel image. Or, you can boot a live Linux CD/USB to fix your system.

Hello dear Emerson


many thanks for the quick reply.



well i am trying to find out why - i have had the same issues months ago see some interesting insights into the system - here ..


https://www.flickr.com/photos/381729...posted-public/
https://www.flickr.com/photos/381729...posted-public/
https://www.flickr.com/photos/38172986@N05/


note, this sheds a light on the system - and now it is brocken again

the last time i ve had issues with

/var/log files


According to the link above i thought that the deletion of the the files was necessary.

what did i do; i have deleted the files - that are older first.

note; THIS WAS NOT A FRESH INSTALLTION


What helped the last time;: i have had to erase the logfiles:


1. rm -rf /var/log/*
2. dmesg -c
3. reboot Since this works,

this would be possible too. - if logrotate is installed..

sudo /etc/cron.daily/logrotate


but now - i have some more issues;


when i try to get into grub (with F4 while the machine is starting) i get the following

what should i do now?

love to hear from you

Sounds like filesystem corruption, I'd boot from live media and check it out.

1 members found this post helpful.

hello Emerson - many thanks for the quick answer. Will do as adviced.

btw . i cannot do this with GPARTED too !? can i -
i guess that Gparted is a bit easier to handle

and with gparted i also can work with comand-line , can t i?!

love to hear from you...

Doubtful, based on your posting history about this very subject.
Again, as you've been told/asked to MANY TIMES...can you not do any research on your own??? Putting "how to use gparted" into Google pulls up, as the VERY FIRST HIT:
http://gparted.org/display-doc.php%3Fname%3Dhelp-manual

COMPLETE instructions with examples. Why is that so hard for you? Especially considering you posted here:
http://www.linuxquestions.org/questi...6/#post5088460

...that "With Gparted i have many many options of configuring" and "Note - i a m big fan of using Gparted because it has a nice and clear overview on all the partitions."

And for some reason now, you have NO IDEA how to use it? Interesting.

Further, you've been given advice about your system MANY times in the past:
http://www.linuxquestions.org/questi...se-4175489155/
http://www.linuxquestions.org/questi...in-4175488987/
http://www.linuxquestions.org/questi...ne-4175488964/
http://www.linuxquestions.org/questi...ne-4175488860/
http://www.linuxquestions.org/questi...ue-4175489326/
http://www.linuxquestions.org/questi...on-4175490164/
http://www.linuxquestions.org/questi...er-4175523715/

You've been advised many, MANY times by many people to DO A FRESH INSTALL and fix your system properly. You haven't, and still haven't. Not sure why you continue to ask the same questions over and over, and expect the answers to change. If you're not going to bother to take advice given, over the span of YEARS at this point, there really isn't a point in posting. Also, this thread:
http://www.linuxquestions.org/questi...4/#post5500086

...has links to many questions of yours where you claim you were going to go back and post the answers/solutions. Any word on actually doing that yet?

You can enter command mode in grub by pressing "C" at the menu. Although kind of pointless if you don't know the lingo. You can edit boot options by pressing "E" at the menu. Mildly more useful if you're using /dev/ names or forget the initrd line in the grub menu. The "C" mode lets you ls to see what grubs sees, and tab complete an existing kernel. But to be honest, if you're not sure what you're doing and that you can recover fastest this way, then boot another live distro or re-install. It's nice to figure out what you did wrong or what failed. But sometimes it just nice to get on with your day.

1 members found this post helpful.

Good luck. The OP has been given such information many times previously, and (given what's been done to that system in the past), they were advised to do a fresh install. Hasn't ever happened.