I acidently set time on bootloader to 0, now i canot chose failsafe after reboot
My system (openSUSE 12.2 - Kernel 3.4.11.2.16-desktop) was working fine until till today, now i cannot startx annmore.
Before login screen i see “Started Postfix Mail Transport Agent” and the system hangs…
I can acces terminal but, have no knowledge howto proceed.
So either i get help from annyone to set bootloader to more than 0 or maybe someone experienced same problem??
I i type startx i get:
hostname: name or service not known
xauth: file/home/user/.serverauth.2610 does not exist
fatal server error:
cannot move old log file "/var/log/xorg.0.log! to " /var/log/xorg.0.log.old
xinit: giving up
xinit: unable to connect to x server: connection refused
xinit: server error
xinit failed. /usr/bin/xorg is not setuid, maybe that0s the reason?
if so either use a display mannager (strongly recommended) or adjust /etc/permissions.local
So, reinstalled /root and it was ok, releave for a second… updates installed, system hangs again, i get fatal errors and cannot acces gui neither in normal boot mode or failsafe mode.
is there command for terminal that can exclude, restrict or unninstall last updates?
This could be a problem for me as i need my computer for graphic manipulation daily…
My system (openSUSE 12.2 - Kernel 3.4.11.2.16-desktop) was working fine until till today,
I wonder what changed? And how long had it been running fine…?
You can undo updates by disabling the updated repo and running
my system was working excelent from release of 12.2 till yesterday, first crash… then fresh instal, updates today, reboot and crash again, wait , will type your stuff
Boot continues, NO login prompt, i can acess terminal with ALT+F2 tough.
Hellow, untill i think openSUSE 11.1 i installed drivers from ati regulary and if anny crashes i simply restored with aticonfig --initial -f and it was fine
From 12.1 i use only implemented drivers of openSUSE 12.1 and later on from openSUSE 12.2
Hej everybody! Now the hartest and exiting part is to find out what caused the hang
@ tsu2
“# tail -n 100 /var/log/messages” command didnt realy get all the way back, even if i increased the numbers, so i checked machine log personaly
and copy / pasted it to my web page in one of my indexes for easy viewing.
You can freely check it out, i would apreciate if annyone finds a meaning in that and tells me what went wrong, because i am still learning Linux even after years of use but am still too short to understand this logs
If updates are fault can i find out whic update was the cause of it all?
Greeting, looking forward for some answer, debates