Problem after last patch update

Hello. I successfully installed OpenSUSE 12.1 in a Desktop PC (mother Asus M2N MX SE Plus, micro AMD 64 bit dual core, 2 GB DDR2 RAM. I have been using it for long time with Gnome3 (KDE had a hang up at installation due to some isue with akonadi, so after several tries I installed Gnome3). However, after the last update I have a hang up at “normal” boot and I can only boot using failsafe. Using this goes back to old desktop and gnome3 doesn’t show up. Worse, NVidia GPU options don’t show up and the screen sets up at 1024x768 without any possibility to change it (my screen is 1280x720). I would appreciate any help. In fact I am trying to search for a .log file that might give me a clue. But can’t find any (boot.log? where is it?). Thank you in advance for your reply. Regards,
Gerardo

On 2012-04-22 17:36, gmirkin wrote:

> In
> fact I am trying to search for a .log file that might give me a clue.
> But can’t find any (boot.log? where is it?).

The messages file.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

On Sun, 22 Apr 2012 21:06:03 +0530, gmirkin
<gmirkin@no-mx.forums.opensuse.org> wrote:

>
> ::Hello. I successfully installed OpenSUSE 12.1 in a Desktop PC (mother
> Asus M2N MX SE Plus, micro AMD 64 bit dual core, 2 GB DDR2 RAM. I have
> been using it for long time with Gnome3 (KDE had a hang up at
> installation due to some isue with akonadi, so after several tries I
> installed Gnome3). However, after the last update I have a hang up at
> “normal” boot and I can only boot using failsafe. Using this goes back
> to old desktop and gnome3 doesn’t show up. Worse, NVidia GPU options
> don’t show up and the screen sets up at 1024x768 without any possibility
> to change it (my screen is 1280x720). I would appreciate any help. In
> fact I am trying to search for a .log file that might give me a clue.
> But can’t find any (boot.log? where is it?). Thank you in advance for
> your reply. Regards,
> Gerardo::
>
>

that’s /var/log/messages.

how did you install your nvidia driver? from the repos, via YAST or
zypper, or from the nvidia website?

one of my last updates included a new kernel, and if you’re using the
nvidia driver from the website, you’ll have to recompile it for a new
kernel.


phani.

Hello phani. Thank you for your reply. In fact I am using the driver from the OpenSUSE repos using YAST (it didn’t give me any problem). I will look for the file in /var/log/messages to see if I have any clue. If I haven’t I will quote the message (I am just a rookie in admin issues). One more thing is that the system continuosly says there are actualizations to be downloaded (like 700 MB or so) but it doesn’t end installing them even if I leave the system on (without energy system shut down) after 8 or more hours (and no net problem). Thank you again. Regards,
Gerardo

Try running zypper up (as root) to update the system.

This is what I find in /var/log/messages after running under failsafe:

Apr 21 19:15:01 Darwin rsyslogd: [origin software=“rsyslogd” swVersion=“5.8.5” x-pid=“741” x-info=“http://www.rsyslog.com”] rsyslogd was HUPed
Apr 21 19:15:12 Darwin dbus-daemon[766]: (process:4935): datetime-plugin-DEBUG: Exiting due to inactivity
Apr 21 19:15:15 Darwin dhcpcd[2241]: eth0: timed out
Apr 21 19:15:15 Darwin dhcpcd[2241]: eth0: trying to use old lease in /var/lib/dhcpcd/dhcpcd-eth0.info' Apr 21 19:15:15 Darwin dhcpcd[2241]: eth0: lease expired 85138 seconds ago Apr 21 19:15:15 Darwin dhcpcd[2241]: eth0: broadcasting for a lease Apr 21 19:15:35 Darwin dhcpcd[2241]: eth0: timed out Apr 21 19:15:35 Darwin dhcpcd[2241]: eth0: trying to use old lease in /var/lib/dhcpcd/dhcpcd-eth0.info’
Apr 21 19:15:35 Darwin dhcpcd[2241]: eth0: lease expired 85158 seconds ago
Apr 21 19:15:35 Darwin dhcpcd[2241]: eth0: broadcasting for a lease
Apr 21 19:15:38 Darwin dhclient[2259]: send_packet6: Network is unreachable
Apr 21 19:15:38 Darwin dhclient[2259]: dhc6: send_packet6() sent -1 of 58 bytes
Apr 21 19:15:55 Darwin dhcpcd[2241]: eth0: timed out
Apr 21 19:15:55 Darwin dhcpcd[2241]: eth0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth0.info’
Apr 21 19:15:55 Darwin dhcpcd[2241]: eth0: lease expired 85178 seconds ago
Apr 21 19:15:55 Darwin dhcpcd[2241]: eth0: broadcasting for a lease
@ @
“messages” 27838L, 2834678C 1,1

If I run under normal conditions a sad face appears and asks to contact the admin saying that a serious problem arised. One more thing: I tried to re-install OpenSUSE 12.1 with the DVD (provided md5sum was ok when copying and that copy velocity was lowest to avoid any copy problem) and system goes directly to HD. I thought it was a DVD reader/writer issue but I can see movies or listen to music using de DVD reader/writer.
Thanks again. Regards,
Gerardo

Is the DVD set to boot in the BIOS??

Hello phani and gogalthorp,
Regarding phani issues I will try zypper up as root to update, although the last update ended successfully and asked to reboot the system. Kernel is apparently 3.1. I’ve read it gives a lot of headaches in many distros. Regarding gogalthorp comment, could the update change BIOS settings? I used to have CD/Diskette/HD priority but when I saw that again the priority was HD/Diskette/CD. I change that already. I will try zypper up anyway. Besides that, do you recommend doing a new installation? In that case, how to avoid installation of kernel 3.1 or 3.2 that are really a mess for the system?
Thanks both a lot for your comments. Regards,
Gerardo

On 2012-04-24 20:16, gmirkin wrote:
> Kernel is apparently 3.1. I’ve read it gives a lot of headaches in many
> distros.

Huh? No idea of that, no problems here out of the normal.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

On Tue, 24 Apr 2012 23:46:03 +0530, gmirkin
<gmirkin@no-mx.forums.opensuse.org> wrote:

>
> Hello phani and gogalthorp,
> Regarding phani issues I will try zypper up as root to update, although
> the last update ended successfully and asked to reboot the system.

this probably means you’ve got the new kernel. it’s 3.1.10-1.9, by the way.

> Kernel is apparently 3.1. I’ve read it gives a lot of headaches in many
> distros.

i didn’t hear that. on the contrary, some problems have been fixed. i’m
not aware that there are major new ones, apart from the usual culprits
probably, like some wifi cards having problems, perhaps also video
configurations, but not re. nvidia.

you could try one thing: after the same kernel update i forgot to include
the “nomodeset” parameter in my kernel line, and the same thing that you
describe happened: instead of logging in to KDE, i was dumped back to the
same login prompt. to try out if that may be the case, you can type
“nomodeset” (w/o quotation marks) at the grub boot screen, choosing the
desktop, not the failsafe boot option.

> Regarding gogalthorp comment, could the update change BIOS
> settings? I used to have CD/Diskette/HD priority but when I saw that
> again the priority was HD/Diskette/CD. I change that already. I will try
> zypper up anyway. Besides that, do you recommend doing a new
> installation? In that case, how to avoid installation of kernel 3.1 or
> 3.2 that are really a mess for the system?
> Thanks both a lot for your comments. Regards,
> Gerardo
>
>


phani.

Hello again,
I updated using zypper up. All packages were updated ok. I restarted the PC. Nothing changed. Regarding the nomodeset command in kernel, I already tried that. Same thing happens.
I think I will try the hard way: re-install the whole system and re-install all the programs I need. Sad but apparently needed. Thanks a lot for your help. I will keep faithful to GNU/Linux anyway (using either OpenSUSE, which I like for my desktop at home and Debian, which I like for my desktop at work and at my netbook.
Thanks a lot again. Regards,
Gerardo