can only boot in safe mode

OK well you have two ways the mv can be done from the terminal after su(login as root) or you should be able to do it from failsafe and a su browser, or su terminal(Have to escalate rights as root owns xorg.conf). Then try running sax2 it should start, if not try sax2 -r -m 0=intel iirc this will reread/probe some stuff, but having removed the xorg.conf I’m hoping it should just do it with sax2.

Afaik you should always get failsafe tbh I still don’t really know where it gets the failsafe xorg.conf from.

Yes I noticed 2 mouses but specifically it says 2 touchpads(Synaptics). mouse [1] is the usb and I suspect mouse [3] should be the touchpad as for 5 and how it got there not sure(Never had anything to do with synaptics and I hate those things the couple of times I’ve encountered them).

Apologies a typo X11 not x11

ok I cured my problem by just reinstalling my nvidia driver
all is well again :slight_smile:

ok thanks try that at root in terminal then run sax2 ok

Yes all we’ve done is move the non-working xorg.conf so we can restore it(Sounds a bit silly now but still).

Fingers crossed that is all you need to do. If you’re doing it from the terminal after running sax2, which hopefully will run, then you should be able to test with startx.

done the mv

run sax2 xc sorry could not start configuration server
xc for details refer to the log file /var/log/Sax.log

the same for the extended version of sax2

Any further advice? Shall i try and find that log file?

Thanks

Yes post that up lets see what that says.

too big - so added it to the others in the pastebin

Thanks

While I look at this do you get the same error if you use

sax2 -r -m 0=intel

try startx to test should one of these actually give you a working xorg.conf.

sax2 -r -m 0=vesa

Also maybe worth doing

zypper up

Just in case you’re not alone and a fix has made it out.

zypper up is upgrading the mesa 32 bit package 17.3 M 1.1M larger

Well that is repeating exactly what we’ve seen with the combined output of various earlier bits.

So my next thing is well lets presume it is the update. So I’ve just had a look, so if you type

rpm -qa --last | head -20

do you get xorg-x11-libxcb included?

Its just it is the only one I can see that is xorg related, if it is then try this.

zypper in xorg-x11-libxcb=7.4-1.24

That should get you back to before it was updated. We may have to lock it and bug report it if this roll back does solve it.

Sorry but where do I type this?

In the text start or a window in failsafe?

You can go back to failsafe, gui is always more friendly.

The only reason for non-failsafe is boot.msg and Xorg.0.log are created on each boot so on successful boots we get logs for successful boots which doesn’t help trouble shooting.

I got a few

but with regards to xorg
xorg-x11-driver-video-radonhd-1.2.4 etc
xorg-x11-fonts-core-7.4-1.66

BTW in YAST a file is highlighted red when search for x11

YAST highlights
xorg-x11-driver-video

installed 7.4.47.4
alternate 7.4.19.5.1

conflict
xorg-x11-server-7.4-17.4.1*64 requires xorg-x11-driver-video but this requirement cannot be provided

it does say conflict resolution install xorg-x11-server-7.4.63.3*86_64 with vendor change.

is this any use?

Mmm red I thought implied a vendor change, but you don’t have any strange repo’s you have a couple of duplicates but I did not think vendor change only thing I can think of is perhaps it is playing part of it.

Post the output of

zypper lr -u

This way we can see the duplicates and url’s perhaps it is having an effect and a mix of vendors is the problem.

Though personally the only one I thought might be problematic was vlc being enabled.

Missed you in cyberspace yes this is the problem I suspected that package :wink:

Edit
Accept the change with vendor change the zypper stuff may be helpful so we can stop future occurences.

—±---------------------±----------------------±--------±--------±------- --------------------------------------------------------
1 | Libdvdcss repository | Libdvdcss repository | Yes | Yes | http:// use.linuxin.dk/repo/11.1/
2 | Packman Repository | Packman Repository | Yes | Yes | http:// tp.skynet.be/pub/packman/suse/11.1/
3 | openSUSE 11.1-0 | openSUSE 11.1-0 | Yes | No | cd:///? evices=/dev/sr0
4 | openSUSE_11.1 | openSUSE_11.1 | Yes | Yes | http:// ownload.opensuse.org/repositories/X11:XOrg/openSUSE_11.1
5 | packman | packman | No | Yes | http:// ackman.jacobs-university.de/suse/11.1/
6 | repo-debug | openSUSE-11.1-Debug | No | Yes | http:// ownload.opensuse.org/debug/distribution/11.1/repo/oss/
7 | repo-non-oss | openSUSE-11.1-Non-Oss | Yes | Yes | http:// ownload.opensuse.org/distribution/11.1/repo/non-oss/
8 | repo-oss | openSUSE-11.1-Oss | Yes | Yes | http:// ownload.opensuse.org/distribution/11.1/repo/oss/
9 | repo-source | openSUSE-11.1-Source | No | Yes | http:// ownload.opensuse.org/source/distribution/11.1/repo/oss/
10 | repo-update | openSUSE-11.1-Update | Yes | Yes | http:// ownload.opensuse.org/update/11.1/
linux-n2vd:~ #

Now that was what I was expecting from lr earlier, number 4 why do you have this do you have a reason? You have enabled X11:XOrg/openSUSE_11.1 though it got hidden under openSUSE_11.1 as an alias.

zypper mr -d 4
zypper dup
sax2

Should have you up and running again.

Well I learnt something and that is don’t trust the output of zypper lr

no i do not know. I am a newbie as you know. I only get help from here from suse 10.2. I did get help to play dvd’s earlier in the year. I will do the above now.