From: Will Honea on
Taki wrote:

> Baron wrote:
>> Hi Guys,
>>
>> I have just wiped OpenSuse 10.3 and installed 11.1 on my spare machine.
>> But I have a problem with it. At the end of the install when you get
>> to login for the first time, all I get is a "Login" prompt.
> [...]
>> Machine is a "Via chipset" with and AMD Athlon 64-4000, 1GB ram, on
>> board video etc.
> [...]
>
> The most likely culprit is the Via on-board Unichrome chip set and the
> new and improved X System.
>
> I've had a very similar problem. Up to openSUSE 10.3, the X System gave
> me no problem. You skipped 11.0. With this version, X started but its
> configuration was wrong: streaks, etc. I copied the old xorg.conf (maybe
> I re-installed 10.3 and saved its xorg.conf on my /home/taki/
> (partition/directory).
>
> With 11.1, I got the exactly the same symptom like yours. By this time,
> I have copied the old xorg.conf on USB sticks as well as on /home/taki/.
> I may be missing some latest and greatest improvements of the X, but I
> don't care. I log in as 'root':
> #cp /home/taki/xorg.conf /etc/X11/xorg.conf
> overwriting the newly-installed xorg.conf.
>
> Try copying the 10.3 xorg.conf to /etc/X11. (You can rename the
> freshly-minted xorg.conf or save it elsewhere to study.) Or using sax2
> manually, giving options for 'VESA' may work. I have no idea how to do
> this.
>
> ---
> I think that some people have been working on the driver for the S3/Via
> chip set and that the installer detects the Via chip set, with an
> unfortunate result. On my machine, xorg-x11-driver-video-unichrome is
> installed.

I've got a couple of oddball systems that are unhappy with 11.x as well.
What has worked for me has been to be very careful to choose the manual
configuration option when installing and set the desired video mode
manually during the install configuration stage. That's the only way I've
found to get a couple of old Dell systems to come up without a serious
battle. I suspect that this forces the install phase to write the
xorg.conf file with specific lines that are skipped/omitted during auto
configuration of the video but it has worked for 11.0 and 11.1 where
leaving the choices selected by the system resulted in no X. Changing
anything - color depth, screen size, even refresh rate seems to do the
trick.

--
Will Honea

From: J G Miller on
On Sun, 27 Sep 2009 09:50:45 +0200, DenverD wrote:

> because commanding startx as root is the same as logging into X as
> root

By the way, under which user do you think the X server (not the login
session runs)?

> something that should never be done, ever!

Just because something is not a good idea security wise, does not mean
that it should never be done. Why else did SuSe have a specaial
red bombshell wallpaper if it was not intended that root should never login
under X, ever?

It would be better to say that root should never login under X, except
for exceptionally special circumstances.
From: David Bolt on
On Saturday 26 Sep 2009 20:47, Vahis played with alphabet spaghetti and
left this residue on the plate:

> On 2009-09-26, Baron <baron.nospam(a)linuxmaniac.nospam.net> wrote:

>> Putting in the root password and typing "startx" gets me "X server
>> failed to start"

What's the error?

>> ! Non of the terminal (alt+ctrl+Fx) works either.

That's not a good sign.

> Never startx as root! Never!

You don't like the pretty desktop background with those nice little
triangular warning signs and bombs?

Yes, I do know it's certainly not a good idea but I have done it in the
past and will probably do so again sometime in the future. The
important thing to not do, if you're going to use X as root, is to
*keep* *out* *of* *the* *users* *home* *directories* or, if you
manipulate something in a users home directory, use chown to
recursively set the ownership of the users home directory to that user.
That way any changed or incorrectly owned files become owned by that
user and it prevents some of the problems of having root-owned files
cause when trying to start X as the normal user.

> Just log in as root. No x.
> Then command init 3
> Then command sax2
> Then configure your display. Once it's OK leave sax2.

Unless you know the GUI will work with the settings you supplied, make
sure you test them out before leaving sax2.

> Then command init 5 & exit.
>
> You should get the GUI login screen.

And if you don't, post the actual errors produced when using startx as
a user.


Regards,
David Bolt

--
Team Acorn: www.distributed.net OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s
openSUSE 10.3 32b | openSUSE 11.0 32b | |
openSUSE 10.3 64b | openSUSE 11.0 64b | openSUSE 11.1 64b | openSUSE 11.2m6
RISC OS 3.6 | RISC OS 3.11 | openSUSE 11.1 PPC | TOS 4.02
From: David Bolt on
On Saturday 26 Sep 2009 21:25, Baron played with alphabet spaghetti and
left this residue on the plate:

<snip>

> I tried that and I get "Failed to start X server"

What's the error?

> What really annoys me is that I can install 10.3 and it all works as
> expected. I even tried updating from a clean 10.3 install and end up
> the same !

Did the install work using a GUI? If so, what happens when you copy
/etc/X11/xorg.conf.install over the top of /etc/X11/xorg.conf and then
try startx ? Does it start? Does it error? What's the error(s) you're
seeing?


Regards,
David Bolt

--
Team Acorn: www.distributed.net OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s
openSUSE 10.3 32b | openSUSE 11.0 32b | |
openSUSE 10.3 64b | openSUSE 11.0 64b | openSUSE 11.1 64b | openSUSE 11.2m6
RISC OS 3.6 | RISC OS 3.11 | openSUSE 11.1 PPC | TOS 4.02
From: David Bolt on
On Sunday 27 Sep 2009 13:10, David Bolt played with alphabet spaghetti
and left this residue on the plate:

> The
> important thing to not do, if you're going to use X as root, is to
^^^
How did that creep in there?!? It should read:

The important thing to do, if you're going to...


Regards,
David Bolt

--
Team Acorn: www.distributed.net OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s
openSUSE 10.3 32b | openSUSE 11.0 32b | |
openSUSE 10.3 64b | openSUSE 11.0 64b | openSUSE 11.1 64b | openSUSE 11.2m6
RISC OS 3.6 | RISC OS 3.11 | openSUSE 11.1 PPC | TOS 4.02
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5 6 7 8 9 10 11
Prev: useradd issue
Next: ttyUSB0 and ICS