Solved - Failed to start Xorg Server - help understanding the reply on another thread which might solve this PLS.

Bouncypete · July 29, 2018 at 5:48 PM

Hi, I'm having issues which are almost identical to this thread Solved - Failed-to-start-xorg-server

I understand the issue is caused by the LE loading the drivers for the integrated graphics rather than PCI card graphics and the thread suggests a solution by running the command below.

Code

 touch /storage/.config/udev.rules.d/96-nvidia.rules

That's the bit I'm stuck on, I don't know how or where I enter that command. I've tried to search for this myself to no avail. Also, is that a space after the word touch and before the forward slash?

Any help would be much appreciated.

**Iridium** · July 29, 2018 at 6:01 PM Official Post

Firstly access LibreElec via ssh Here. Run the command exactly as it is - so yes there is a space after touch.

Bouncypete · July 29, 2018 at 8:43 PM

Brilliant, I'd read about ssh in that reply but didn't realise it was the method of changing the code. Many thanks for your reply.

**Klojum** · July 29, 2018 at 9:13 PM Official Post

It's not so much about changing the code, but more like giving the code a parameter to which it can react.

BTW, the "code" of LibreELEC sits in a readonly blob file on a separate disk partition.

Bouncypete · July 29, 2018 at 9:35 PM

Hmmm, I thought I understood but now I'm not so sure. Using the HTPC that works flawlessly I can easily access it from my server PC using the Samba/SMB method in your link. I'm not sure which file to edit or add a line of code to.

From this I suspect you can't access the necessary file via Samba/SMB, it has to be via ssh only. - Is this correct?

If the 'code' is on a readonly partition how can it be edited? Is it the case that you can edit it via ssh, it's just the partition is not normally accessible?

When I access the HTPC via ssh, what file do I edit or add the code to?

Code

 touch /storage/.config/udev.rules.d/96-nvidia.rules

**awiouy** · July 29, 2018 at 9:44 PM Official Post

Connect with ssh, authenticate, type the command (copy/paste to avoid typos), then reboot.

The command creates an empty file.

Bouncypete · July 29, 2018 at 9:56 PM

I've just downloaded putty and successfully accessed the flawless HTPC.

However, it's getting a bit late for me so I'll see If I can boot the problematic HTPC tomorrow. If necessary I'll clean install LE to get it up and running then access ssh and type the that command to see if that creates a reliable machine.

Thanks to all for taking the time to reply to what must seem a really basic question.

Bouncypete · July 30, 2018 at 11:58 AM

I've now run the code and it seems to be working flawlessly.

Many thanks to everyone who has helped me.

I'll update the header to read solved.