Xorg problems: startx fails

anchovy · 2022-03-07 02:24:08

Hi I'm guys trying to install xorg,

I installed the xf86-video-amdgpu driver
I did yay -S Xorg
And I installed xorg-server
And xorg-xinit
And i3-gaps
I copied usr/share/X11/xorg.conf.d to etc/X11/Xorg.conf.d
I created .xinitrc and added exec i3
Running startx gives:
Giving up
Unable to connect to x server
Server error

Idk how to send the log file to u guys but I can take pictures

https://media.discordapp.net/attachment … height=439
https://media.discordapp.net/attachment … height=426
https://media.discordapp.net/attachment … height=417

Edit:
http://ix.io/3Ry7

Last edited by anchovy (2022-03-07 02:54:16)

Scimmia · 2022-03-07 02:31:12

anchovy wrote:

I did yay -S Xorg

That was...not a great idea. It installs a bunch of packages you may not need or want. For one thing, get rid of xf86-video-vesa

anchovy wrote:

I copied usr/share/X11/xorg.conf.d to etc/X11/Xorg.conf.d

This was just flat out wrong. Undo it. Then tell us what other files are in that dir, as well as if you have an /etc/X11/xorg.conf file

anchovy wrote:

I created .xinitrc and added exec i3

Created how?

HalosGhost · 2022-03-07 02:32:10

Hello.

I removed the inline images (because they were beyond the size guidelines of the BBS; please note the “Guidelines” linked from the Code of Conduct (link in my signature for your ease)). As an additional note, images of logs are a very poor option for communication. You have internet access (as evidenced by your use of an AUR helper in your first screenshot)., so you can a pastebin like https://ix.io to share logs in text form easily. That will make your life and our lives a lot easier.

All the best,

-HG

anchovy · 2022-03-07 02:52:50

HalosGhost wrote:

Hello.
I removed the inline images (because they were beyond the size guidelines of the BBS; please note the “Guidelines” linked from the Code of Conduct (link in my signature for your ease)). As an additional note, images of logs are a very poor option for communication. You have internet access (as evidenced by your use of an AUR helper in your first screenshot)., so you can a pastebin like https://ix.io to share logs in text form easily. That will make your life and our lives a lot easier.
All the best,
-HG

omg that's the coolest thing ever thank you so much

anchovy · 2022-03-07 03:19:36

Scimmia wrote:

anchovy wrote:
I did yay -S Xorg
That was...not a great idea. It installs a bunch of packages you may not need or want. For one thing, get rid of xf86-video-vesa
anchovy wrote:
I copied usr/share/X11/xorg.conf.d to etc/X11/Xorg.conf.d
This was just flat out wrong. Undo it. Then tell us what other files are in that dir, as well as if you have an /etc/X11/xorg.conf file
anchovy wrote:
I created .xinitrc and added exec i3
Created how?

Alright thank you for the reply,

I deleted xf86-video-vesa, and undid the copying of usr/share/X11/xorg.conf.d.

At this point I don't have anything in my etc/X11/Xorg.conf.d

I have /etc/X11/xinit which has
xinitrc.d/50-systemd-user.sh
xinitrc
xserverrc

There is no /etc/X11/xorg.conf

I created xinitrc in my home directory, and it's empty asides from exec i3. I just found out there is also an /etc/X11/xinit/xinitrc. Don't know if I should delete one, or which one.

I ran startx again after doing what you told me to(with both xinitrc, the one in my home directory and /etc/X11/xinit/xinitrc), and got this error: http://ix.io/3Ryf

Thank you once again.

Last edited by anchovy (2022-03-07 03:23:51)

seth · 2022-03-07 07:19:33

[   874.817] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=7e8928e2-73d2-49ee-9581-1a111888f838 rw loglevel=3 quiet nomodeset
…
[   874.821] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   874.821] (EE) open /dev/dri/card0: No such file or directory

Remove the "nomodeset" parameter, it'll prevent you from running anything but the VESA driver (what, as Scimmia pointed out, you do not want at all)

Scimmia · 2022-03-07 13:27:54

I think seth nailed the issue. Unrelated, but to avoid future issues, see https://wiki.archlinux.org/title/Xinit#xinitrc

anchovy · 2022-03-07 22:02:50

Remove the "nomodeset" parameter, it'll prevent you from running anything but the VESA driver (what, as Scimmia pointed out, you do not want at all)

I added that parameter myself because the system boots to a black screen without it, and the only thing I can do at that point is turning the computer off. No tty is available.

loqs · 2022-03-07 22:09:31

Please post the system journal from a boot without nomodeset and one from with.

Last edited by loqs (2022-03-07 22:26:44)

anchovy · 2022-03-08 00:31:56

loqs wrote:

Please post the system journal from a boot without nomodeset and one from with.

without nomodeset: http://ix.io/3RE2
nomodeset: http://ix.io/3RE3

Last edited by anchovy (2022-03-08 00:32:17)

loqs · 2022-03-08 01:40:09

Mar 07 19:16:10 alibale123 kernel: pci 0000:01:00.0: [1002:67df] type 00 class 0x030000
Mar 07 19:16:10 alibale123 kernel: pci 0000:01:00.0: reg 0x10: [mem 0x90000000-0x9fffffff 64bit pref]
Mar 07 19:16:10 alibale123 kernel: pci 0000:01:00.0: reg 0x18: [mem 0xa0000000-0xa01fffff 64bit pref]
Mar 07 19:16:10 alibale123 kernel: pci 0000:01:00.0: reg 0x20: [io  0x3000-0x30ff]
Mar 07 19:16:10 alibale123 kernel: pci 0000:01:00.0: reg 0x24: [mem 0xa0300000-0xa033ffff]
Mar 07 19:16:10 alibale123 kernel: pci 0000:01:00.0: reg 0x30: [mem 0xa0340000-0xa035ffff pref]
Mar 07 19:16:10 alibale123 kernel: pci 0000:01:00.0: BAR 0: assigned to efifb
Mar 07 19:16:10 alibale123 kernel: pci 0000:01:00.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Mar 07 19:16:10 alibale123 kernel: pci 0000:01:00.0: supports D1 D2
Mar 07 19:16:10 alibale123 kernel: pci 0000:01:00.0: PME# supported from D1 D2 D3hot D3cold
Mar 07 19:16:10 alibale123 kernel: pci 0000:01:00.1: [1002:aaf0] type 00 class 0x040300
Mar 07 19:16:10 alibale123 kernel: pci 0000:01:00.1: reg 0x10: [mem 0xa0360000-0xa0363fff 64bit]
Mar 07 19:16:10 alibale123 kernel: pci 0000:01:00.1: supports D1 D2
Mar 07 19:16:10 alibale123 kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Mar 07 19:16:10 alibale123 kernel: pci 0000:00:01.0:   bridge window [io  0x3000-0x3fff]
Mar 07 19:16:10 alibale123 kernel: pci 0000:00:01.0:   bridge window [mem 0xa0300000-0xa03fffff]
Mar 07 19:16:10 alibale123 kernel: pci 0000:00:01.0:   bridge window [mem 0x90000000-0xa01fffff 64bit pref]
....
Mar 07 19:16:10 alibale123 kernel: pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=mem,locks=none
Mar 07 19:16:10 alibale123 kernel: pci 0000:01:00.0: vgaarb: bridge control possible
Mar 07 19:16:10 alibale123 kernel: pci 0000:01:00.0: vgaarb: setting as boot device
Mar 07 19:16:10 alibale123 kernel: vgaarb: loaded

vendor: 1002 ("Advanced Micro Devices, Inc. [AMD/ATI]"), device: 67df ("Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]") but nothing from amdgpu.

anchovy · 2022-03-08 02:16:56

loqs wrote:

vendor: 1002 ("Advanced Micro Devices, Inc. [AMD/ATI]"), device: 67df ("Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]") but nothing from amdgpu.

Can you elaborate on what that means?, I definitely have the package installed and the wiki said I don't need any further configuration

https://wiki.archlinux.org/title/AMDGPU#Xorg_configuration wrote:

Xorg will automatically load the driver and it will use your monitor's EDID to set the native resolution. Configuration is only required for tuning the driver.

Last edited by anchovy (2022-03-08 02:19:09)

Scimmia · 2022-03-08 02:24:28

It means it should be loading the amdgpu kernel module, but for some reason it's not. Does it work without nomodeset with the install ISO? Do you have any special configurations in /etc/modules-load.d/? Any customization in /etc/mkinitcpio.conf?

anchovy · 2022-03-08 02:55:01

Scimmia wrote:

It means it should be loading the amdgpu kernel module, but for some reason it's not. Does it work without nomodeset with the install ISO? Do you have any special configurations in /etc/modules-load.d/? Any customization in /etc/mkinitcpio.conf?

It doesn't work without nomodeset in the install ISO either, my /etc/modules-load.d is empty and, I haven't done anything to my /etc/mkinitcpio.conf?

seth · 2022-03-08 07:09:14

Interestingly in the nomodeset boot there's

Mar 07 19:17:13 alibale123 kernel: [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

Since the KMS boot "fails" and results in likely a hard reboot, the journal might just be cut short.

https://bbs.archlinux.org/viewtopic.php … 3#p2025803

Lone_Wolf · 2022-03-08 12:18:40

Mar 07 19:17:13 alibale123 kernel: DMI: Gigabyte Technology Co., Ltd. H310M A/H310M A-CF, BIOS F1 03/02/2018

Gigabyte has several revisions of that motherboard.
The data and version of your bios match with rev 1.0 , https://www.gigabyte.com/Motherboard/H3 … rt-dl-bios
It also looks like you are using the very first bios gigabute rteleased for this board.

Verify this is indeed your exact motherboard and consider updating the bios firmware .

anchovy · 2022-03-11 02:45:20

seth wrote:

https://bbs.archlinux.org/viewtopic.php … 3#p2025803

This didn't work so I

Lone_Wolf wrote:

Verify this is indeed your exact motherboard and consider updating the bios firmware.

decided to update my bios, which was going well until it rebooted and wouldn't stop rebooting. It would reboot before I could open the bios setting, so I decided to reset the bios by removing the CMOS battery and putting it back. Didn't work, so I held the power button until my computer started and shut down again, then I pressed the power button again, and my backup BIOS didn't kick in. Next, I tried holding the power and the reset button for about 10 sec, after releasing it didn't boot into the backup BIOS. My last attempt was too short the CMOS pins with a screwdriver which also did nothing.

Don't know what I should do next might have to buy another mobo.

Thanks for the help guys, hopefully, I can figure something out and I won't have to throw my mobo out!

seth · 2022-03-13 15:53:27

it didn't boot into the backup BIOS. My last attempt was too short the CMOS pins

https://superuser.com/questions/1141050 … ng-pins-on ?

Arch Linux

#1 2022-03-07 02:24:08

Xorg problems: startx fails

#2 2022-03-07 02:31:12

Re: Xorg problems: startx fails

#3 2022-03-07 02:32:10

Re: Xorg problems: startx fails

#4 2022-03-07 02:52:50

Re: Xorg problems: startx fails

#5 2022-03-07 03:19:36

Re: Xorg problems: startx fails

#6 2022-03-07 07:19:33

Re: Xorg problems: startx fails

#7 2022-03-07 13:27:54

Re: Xorg problems: startx fails

#8 2022-03-07 22:02:50

Re: Xorg problems: startx fails

#9 2022-03-07 22:09:31

Re: Xorg problems: startx fails

#10 2022-03-08 00:31:56

Re: Xorg problems: startx fails

#11 2022-03-08 01:40:09

Re: Xorg problems: startx fails

#12 2022-03-08 02:16:56

Re: Xorg problems: startx fails

#13 2022-03-08 02:24:28

Re: Xorg problems: startx fails

#14 2022-03-08 02:55:01

Re: Xorg problems: startx fails

#15 2022-03-08 07:09:14

Re: Xorg problems: startx fails

#16 2022-03-08 12:18:40

Re: Xorg problems: startx fails

#17 2022-03-11 02:45:20

Re: Xorg problems: startx fails

#18 2022-03-13 15:53:27

Re: Xorg problems: startx fails

Board footer