After running startx the display shows white and black lines

Message

coffy_mug · Post by **coffy_mug** » Thu Dec 14, 2023 6:13 pm

I installed gentoo on a pretty old laptop. I thought it would be nice to have a graphical environment. I set VIDEO_CARDS to via and emerged x11-libs/libX11, x11-base/xorg-server, x11-apps/xinit, x11-libs/libXrandr, x11-libs/libXft, x11-apps/xrdb, x11-apps/mesa-proogs, x11-apps/xrandr, x11-drivers/xf86-video-openchrome x11-misc/xclip. When I startx the display shows black and white lines that are slowly shifting to black it's hard to describe. I suspect the drivers because the graphics card is not very common it's VIA Chrome9 HC.
Output of

Code: Select all

lspci | grep VGA

Code: Select all

01:00.0 VGA compatible controller: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome9 HC] (rev 01)

alexander-n8hgeg5e · Post by **alexander-n8hgeg5e** » Tue Dec 19, 2023 12:06 pm

You can tell the xserver to print all the available driver options, maybe this helps.
Then I'd start X with verbose debugging output , maybe it tells something.
Does the xserver actually start or does it crash ?

I think stripes do not mean it is not working, I have a system which does produces crazy output, but when
I load a "window-manager" like this one the things go away:

Code: Select all

description="minimal window-manager"                                                                           
command_background=1                                                                                           
pidfile=/var/run/window-manager.pid                                                                            
command=xprop                                                                                                  
output_logger="logger -p syslog.info"                                                                          
error_logger="logger -p syslog.warning"                                                                        
command_args="-display :0 -root -spy"                                                                          
                                                                                                               
depend() {                                                                                                     
    need xserver                                                                                               
}                                                                                                              
                                                                                                               
start(){                                                                                                       
default_start                                                                                                  
#env DISPLAY=:0 xrandr --newmode 1920x1080_60.00 173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync 
#env DISPLAY=:0 xrandr --addmode VGA-1 1920x1080_60.00                                                          
#env DISPLAY=:0 xrandr --output VGA-1 --mode 1920x1080_60.00                                                    
env DISPLAY=:0 xsetroot -name root -solid "#001030"                                                            
#env DISPLAY=:0 xrandr --output VGA-1 --scale 0.537932 --rotate inverted                                        
#env DISPLAY=:0 xset dpms 9000 9000 9000                                                                        
#env DISPLAY=:0 xset s 0 0                                                                                      
}

the xprop in the background and the xsetroot would be what could work for you to make your screen clean

Post by **NeddySeagoon** » Tue Dec 19, 2023 1:58 pm

coffy_mug,

Welcome to Gentoo. It sounds like the display resolution being generated by Xorg is not one that the display can use.
That makes a mess on the display.

Code: Select all

emerge wgetpaste

Share the output of

Code: Select all

lspci -nnk

That fits into a post.
The entire output oy dmesg. That needs wgetpaste.
and the Xorg.0.log file.
Where that is depends on how Xorg was started.

coffy_mug · Post by **coffy_mug** » Fri Dec 22, 2023 3:31 pm

Sory for late reply.

alexander-n8hgeg5e wrote:You can tell the xserver to print all the available driver options, maybe this helps.
Then I'd start X with verbose debugging output , maybe it tells something.

I ran startx --verbose and got

Code: Select all

xauth: file /root/.Xauthority does not exist

xauth: file /root/.Xauthority does not exist

xauth: (argv):1: bad display name "backFromTheDead:0" in "list" command

xauth: (stdin):1: bad display name "backFromTheDead:0" in "add" command

X.Org X Server 1.21.1.10

X Protocol Version 11, Revision 0

Current Operating System: Linux backFromTheDead 6.1.67-gentoo-dist #1 SMP PREEMP

T DYNAMIC Fri Dec 22 06:49:24 CET 2023 1686

Kernel command line: BOOT_IMAGE=/vmlinuz-6.1.67-gentoo-dist root=UUID=e57bc261-0 0a1-4183-a870-00f4941cef48 ro

Current version of pixman: 0.42.2 
Before reporting problems, check http://wiki.x.org to make sure that you have the latest version.

Markers: (-) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. 
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 22 15:51:05 2023 
(==) Using system config directory "/usr/share/X11/xorg.conf.d"

I typed that by hand because copying the output to a file didn't work(I'm probably doing it wrong).

alexander-n8hgeg5e wrote:the xprop in the background and the xsetroot would be what could work for you to make your screen clean

Do they need to be started be openrc and added to the run level or be activated in any other way, because I have emerged them and run startx and it again displays these weird lines exept this time there were some vertical ones but I think it's just random.

coffy_mug · Post by **coffy_mug** » Fri Dec 22, 2023 3:51 pm

output of lspci -nnk

Code: Select all

00:00.0 Host bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge [1106:0364]
	Subsystem: Fujitsu Technology Solutions CN896/VN896/P4M900 Host Bridge [1734:10f7]
	Kernel driver in use: agpgart-via
00:00.1 Host bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge [1106:1364]
	Subsystem: Fujitsu Technology Solutions CN896/VN896/P4M900 Host Bridge [1734:10f7]
00:00.2 Host bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge [1106:2364]
	Subsystem: Fujitsu Technology Solutions CN896/VN896/P4M900 Host Bridge [1734:10f7]
00:00.3 Host bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge [1106:3364]
	Subsystem: Fujitsu Technology Solutions CN896/VN896/P4M900 Host Bridge [1734:10f7]
00:00.4 Host bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge [1106:4364]
	Subsystem: Fujitsu Technology Solutions CN896/VN896/P4M900 Host Bridge [1734:10f7]
00:00.5 PIC [0800]: VIA Technologies, Inc. CN896/VN896/P4M900 I/O APIC Interrupt Controller [1106:5364]
	Subsystem: Fujitsu Technology Solutions CN896/VN896/P4M900 I/O APIC Interrupt Controller [1734:10f7]
00:00.6 Host bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 Security Device [1106:6364]
	Subsystem: Fujitsu Technology Solutions CN896/VN896/P4M900 Security Device [1734:10f7]
00:00.7 Host bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge [1106:7364]
00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237/CX700/VX700-Series PCI to PCI Bridge [1106:b198]
00:02.0 PCI bridge [0604]: VIA Technologies, Inc. CN896/VN896/P4M900 PCI to PCI Bridge Controller [1106:a364] (rev 80)
	Subsystem: VIA Technologies, Inc. CN896/VN896/P4M900 PCI to PCI Bridge Controller [1106:c323]
	Kernel driver in use: pcieport
00:03.0 PCI bridge [0604]: VIA Technologies, Inc. CN896/VN896/P4M900 PCI to PCI Bridge Controller [1106:c364] (rev 80)
	Subsystem: VIA Technologies, Inc. CN896/VN896/P4M900 PCI to PCI Bridge Controller [1106:c323]
	Kernel driver in use: pcieport
00:0f.0 IDE interface [0101]: VIA Technologies, Inc. VT8237A SATA 2-Port Controller [1106:0591] (rev 80)
	Subsystem: Fujitsu Technology Solutions VT8237A SATA 2-Port Controller [1734:10f7]
	Kernel driver in use: sata_via
	Kernel modules: sata_via, pata_acpi, ata_generic
00:0f.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 07)
	Subsystem: Fujitsu Technology Solutions VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1734:10f7]
	Kernel driver in use: pata_via
	Kernel modules: pata_via, pata_acpi, ata_generic
00:10.0 USB controller [0c03]: VIA Technologies, Inc. VT82xx/62xx/VX700/8x0/900 UHCI USB 1.1 Controller [1106:3038] (rev a0)
	Subsystem: Fujitsu Technology Solutions VT82xx/62xx/VX700/8x0/900 UHCI USB 1.1 Controller [1734:10f7]
	Kernel driver in use: uhci_hcd
00:10.1 USB controller [0c03]: VIA Technologies, Inc. VT82xx/62xx/VX700/8x0/900 UHCI USB 1.1 Controller [1106:3038] (rev a0)
	Subsystem: Fujitsu Technology Solutions VT82xx/62xx/VX700/8x0/900 UHCI USB 1.1 Controller [1734:10f7]
	Kernel driver in use: uhci_hcd
00:10.4 USB controller [0c03]: VIA Technologies, Inc. USB 2.0 EHCI-Compliant Host-Controller [1106:3104] (rev 86)
	Subsystem: Fujitsu Technology Solutions USB 2.0 EHCI-Compliant Host-Controller [1734:10f7]
	Kernel driver in use: ehci-pci
00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8237A PCI to ISA Bridge [1106:3337]
	Subsystem: VIA Technologies, Inc. VT8237A PCI to ISA Bridge [1106:3337]
	Kernel modules: i2c_viapro
00:11.7 Host bridge [0600]: VIA Technologies, Inc. VT8237/8251 Ultra VLINK Controller [1106:287e]
	Subsystem: VIA Technologies, Inc. VT8237/8251 Ultra VLINK Controller [1106:337e]
00:12.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6102/VT6103 [Rhine-II] [1106:3065] (rev 7c)
	Subsystem: Fujitsu Technology Solutions VT6102/VT6103 [Rhine-II] [1734:10f7]
	Kernel driver in use: via-rhine
	Kernel modules: via_rhine
00:13.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237A Host Bridge [1106:337b]
	Subsystem: VIA Technologies, Inc. VT8237A Host Bridge [1106:337b]
00:13.1 PCI bridge [0604]: VIA Technologies, Inc. VT8237A PCI to PCI Bridge [1106:337a]
	Subsystem: VIA Technologies, Inc. VT8237A PCI to PCI Bridge [1106:337a]
01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] [1106:3371] (rev 01)
	Subsystem: Fujitsu Technology Solutions CN896/VN896/P4M900 [Chrome 9 HC] [1734:10f7]
04:01.0 Audio device [0403]: VIA Technologies, Inc. VX900/VT8xxx High Definition Audio Controller [1106:3288] (rev 10)
	Subsystem: Fujitsu Technology Solutions VX900/VT8xxx High Definition Audio Controller [1734:10f7]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
05:01.0 Ethernet controller [0200]: Qualcomm Atheros AR2413/AR2414 Wireless Network Adapter [AR5005G(S) 802.11bg] [168c:001a] (rev 01)
	Subsystem: Qualcomm Atheros Compex Wireless 802.11 b/g  MiniPCI Adapter, Rev A1 [WLM54G] [168c:2052]
	Kernel driver in use: ath5k
	Kernel modules: ath5k

output of dmesg
https://pastebin.com/3TUQ0AMp

in the previous reply where i ran startx --verbose it's telling me that the log file is in /var/log/Xorg.0.log but I need to force reboot to be able to display it. After reboot I don't see the file. I'm almost sure there is a way to get this file but I don't know how.

grknight · Post by **grknight** » Fri Dec 22, 2023 4:15 pm

coffy_mug wrote:output of lspci -nnk

Code: Select all

01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] [1106:3371] (rev 01)
	Subsystem: Fujitsu Technology Solutions CN896/VN896/P4M900 [Chrome 9 HC] [1734:10f7]

This video chip has no Linux support at all.
You may get a SIMPLEFB or EFIFB to have a basic framebuffer, but there will be no acceleration at all.

Edit: It seems CONFIG_FB_VIA may still work and pair with the fbdev xorg driver. Although there is no acceleration as mesa has dropped VIA. The OpenChrome DDX is deprecated.
Suggest VIDEO_CARDS="fbdev" in this case. (x11-drivers/xf86-video-openchrome must be removed from the system for this option)

coffy_mug · Post by **coffy_mug** » Fri Dec 22, 2023 8:59 pm

grknight wrote:Suggest VIDEO_CARDS="fbdev" in this case. (x11-drivers/xf86-video-openchrome must be removed from the system for this option)

is anything more needed exept changing VIDEO_CARDS and unmerging x11-drivers/xf86-video-openchrome. Does something need to be recompiled?

EDIT: Earlier I was able to run kali linux on it so I think it's possible.

grknight · Post by **grknight** » Fri Dec 22, 2023 9:48 pm

coffy_mug wrote:
grknight wrote:Suggest VIDEO_CARDS="fbdev" in this case. (x11-drivers/xf86-video-openchrome must be removed from the system for this option)
is anything more needed exept changing VIDEO_CARDS and unmerging x11-drivers/xf86-video-openchrome. Does something need to be recompiled?

EDIT: Earlier I was able to run kali linux on it so I think it's possible.

The kernel needs CONFIG_FB_VIA. Normally we say no FB_* drivers, but this old system has no other option.

coffy_mug · Post by **coffy_mug** » Sat Dec 23, 2023 8:57 am

grknight wrote:The kernel needs CONFIG_FB_VIA. Normally we say no FB_* drivers, but this old system has no other option.

So I'm modyfying the kernel following the Modyfying the kernel section of https://wiki.gentoo.org/wiki/Project:Di ... ion_Kernel. Found the option but after selecting it two other options appear direct hardware accses via procfs (DEPRACETED)(DANGEROUS) and X server compatibility. Maybe it's a stupid question but does any of this options need to be selected and what X server compatibility means? Sorry if I'm asking basic questions just don't want to screw up my kernel.

EDIT: do I need to emerge xf86-video-fbdev

grknight · Post by **grknight** » Sat Dec 23, 2023 2:14 pm

coffy_mug wrote:
grknight wrote:The kernel needs CONFIG_FB_VIA. Normally we say no FB_* drivers, but this old system has no other option.
So I'm modyfying the kernel following the Modyfying the kernel section of https://wiki.gentoo.org/wiki/Project:Di ... ion_Kernel. Found the option but after selecting it two other options appear direct hardware accses via procfs (DEPRACETED)(DANGEROUS) and X server compatibility. Maybe it's a stupid question but does any of this options need to be selected and what X server compatibility means? Sorry if I'm asking basic questions just don't want to screw up my kernel.

EDIT: do I need to emerge xf86-video-fbdev

When using fbdev in Xorg, leave the other kernel options off. The VIDEO_CARDS="fbdev" will pull in what is needed when using 'emerge -avuDU @world'

coffy_mug · Post by **coffy_mug** » Sun Dec 24, 2023 9:11 am

after running startx lines aren't displayed but the graphical environment does not startup just errors are displayed
Xorg.0.log:

Code: Select all

[    89.096] 
X.Org X Server 1.21.1.10
X Protocol Version 11, Revision 0
[    89.097] Current Operating System: Linux backFromTheDead 6.1.67-gentoo-dist #1 SMP PREEMPT_DYNAMIC Sat Dec 23 23:53:33 CET 2023 i686
[    89.097] Kernel command line: BOOT_IMAGE=/vmlinuz-6.1.67-gentoo-dist root=UUID=e57bc261-00a1-4183-a870-00f4941cef48 ro
[    89.098]  
[    89.098] Current version of pixman: 0.42.2
[    89.098] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    89.098] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    89.100] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Dec 24 09:38:45 2023
[    89.155] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    89.222] (==) No Layout section.  Using the first Screen section.
[    89.222] (==) No screen section available. Using defaults.
[    89.222] (**) |-->Screen "Default Screen Section" (0)
[    89.222] (**) |   |-->Monitor "<default monitor>"
[    89.223] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    89.223] (==) Automatically adding devices
[    89.223] (==) Automatically enabling devices
[    89.223] (==) Automatically adding GPU devices
[    89.223] (==) Automatically binding GPU devices
[    89.223] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    89.259] (WW) The directory "/usr/share/fonts/misc" does not exist.
[    89.259] 	Entry deleted from font path.
[    89.259] (WW) The directory "/usr/share/fonts/TTF" does not exist.
[    89.259] 	Entry deleted from font path.
[    89.259] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[    89.259] 	Entry deleted from font path.
[    89.259] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[    89.259] 	Entry deleted from font path.
[    89.259] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[    89.259] 	Entry deleted from font path.
[    89.259] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[    89.259] 	Entry deleted from font path.
[    89.259] (==) FontPath set to:
	
[    89.259] (==) ModulePath set to "/usr/lib/xorg/modules"
[    89.259] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    89.278] (II) Module ABI versions:
[    89.278] 	X.Org ANSI C Emulation: 0.4
[    89.278] 	X.Org Video Driver: 25.2
[    89.278] 	X.Org XInput driver : 24.4
[    89.278] 	X.Org Server Extension : 10.0
[    89.278] (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory)
[    89.278] (--) using VT number 7

[    89.278] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    89.294] (--) PCI:*(1@0:0:0) 1106:3371:1734:10f7 rev 1, Mem @ 0xa0000000/536870912, 0xc8000000/16777216, BIOS @ 0x????????/131072
[    89.294] (II) LoadModule: "glx"
[    89.362] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    89.499] (II) Module glx: vendor="X.Org Foundation"
[    89.500] 	compiled for 1.21.1.10, module version = 1.0.0
[    89.500] 	ABI class: X.Org Server Extension, version 10.0
[    89.500] (==) Matched openchrome as autoconfigured driver 0
[    89.500] (==) Matched modesetting as autoconfigured driver 1
[    89.500] (==) Matched fbdev as autoconfigured driver 2
[    89.500] (==) Matched vesa as autoconfigured driver 3
[    89.500] (==) Assigned the driver to the xf86ConfigLayout
[    89.500] (II) LoadModule: "openchrome"
[    89.501] (WW) Warning, couldn't open module openchrome
[    89.501] (EE) Failed to load module "openchrome" (module does not exist, 0)
[    89.501] (II) LoadModule: "modesetting"
[    89.501] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    89.600] (II) Module modesetting: vendor="X.Org Foundation"
[    89.600] 	compiled for 1.21.1.10, module version = 1.21.1
[    89.600] 	Module class: X.Org Video Driver
[    89.600] 	ABI class: X.Org Video Driver, version 25.2
[    89.600] (II) LoadModule: "fbdev"
[    89.600] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    89.605] (II) Module fbdev: vendor="X.Org Foundation"
[    89.606] 	compiled for 1.21.1.10, module version = 0.5.0
[    89.606] 	Module class: X.Org Video Driver
[    89.606] 	ABI class: X.Org Video Driver, version 25.2
[    89.606] (II) LoadModule: "vesa"
[    89.606] (WW) Warning, couldn't open module vesa
[    89.606] (EE) Failed to load module "vesa" (module does not exist, 0)
[    89.606] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    89.606] (II) FBDEV: driver for framebuffer: fbdev
[    89.609] (EE) open /dev/dri/card0: No such file or directory
[    89.609] (WW) Falling back to old probe method for modesetting
[    89.609] (EE) open /dev/dri/card0: No such file or directory
[    89.609] (II) Loading sub module "fbdevhw"
[    89.609] (II) LoadModule: "fbdevhw"
[    89.609] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    89.638] (II) Module fbdevhw: vendor="X.Org Foundation"
[    89.638] 	compiled for 1.21.1.10, module version = 0.0.2
[    89.638] 	ABI class: X.Org Video Driver, version 25.2
[    89.639] (EE) Unable to find a valid framebuffer device
[    89.639] (WW) Falling back to old probe method for fbdev
[    89.639] (II) Loading sub module "fbdevhw"
[    89.639] (II) LoadModule: "fbdevhw"
[    89.639] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    89.639] (II) Module fbdevhw: vendor="X.Org Foundation"
[    89.639] 	compiled for 1.21.1.10, module version = 0.0.2
[    89.639] 	ABI class: X.Org Video Driver, version 25.2
[    89.639] (EE) open /dev/fb0: No such file or directory
[    89.639] (EE) Screen 0 deleted because of no matching config section.
[    89.639] (II) UnloadModule: "modesetting"
[    89.639] (EE) Screen 0 deleted because of no matching config section.
[    89.639] (II) UnloadModule: "fbdev"
[    89.640] (II) UnloadSubModule: "fbdevhw"
[    89.640] (EE) Device(s) detected, but none match those in the config file.
[    89.640] (EE) 
Fatal server error:
[    89.640] (EE) no screens found(EE) 
[    89.640] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    89.640] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    89.640] (EE) 
[    89.642] (EE) Server terminated with error (1). Closing log file.

coffy_mug · Post by **coffy_mug** » Thu Dec 28, 2023 10:10 am

I searched for similar problems and found out that it could be caused because of wrong /etc/hosts but after fixinig that
a similar error occured.
Output of startx:

Code: Select all

X.Org X Server 1.21.1.10
X Protocol Version 11, Revision 0
Current Operating System: Linux backFromTheDead 6.1.67-gentoo-dist #1 SMP PREEMPT_DYNAMIC Sat Dec 23 23:53:33 CET 2023 i686
Kernel command line: BOOT_IMAGE=/vmlinuz-6.1.67-gentoo-dist root=UUID=e57bc261-00a1-4183-a870-00f4941cef48 ro
 
Current version of pixman: 0.42.2
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec 27 23:03:59 2023
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) 
Fatal server error:
(EE) no screens found(EE) 
(EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE) 
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Xorg.0.log:

Code: Select all

[  1953.865] 
X.Org X Server 1.21.1.10
X Protocol Version 11, Revision 0
[  1953.865] Current Operating System: Linux backFromTheDead 6.1.67-gentoo-dist #1 SMP PREEMPT_DYNAMIC Sat Dec 23 23:53:33 CET 2023 i686
[  1953.865] Kernel command line: BOOT_IMAGE=/vmlinuz-6.1.67-gentoo-dist root=UUID=e57bc261-00a1-4183-a870-00f4941cef48 ro
[  1953.865]  
[  1953.865] Current version of pixman: 0.42.2
[  1953.865] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[  1953.865] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1953.866] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec 27 23:01:52 2023
[  1953.866] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  1953.866] (==) No Layout section.  Using the first Screen section.
[  1953.866] (==) No screen section available. Using defaults.
[  1953.866] (**) |-->Screen "Default Screen Section" (0)
[  1953.867] (**) |   |-->Monitor "<default monitor>"
[  1953.867] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[  1953.867] (==) Automatically adding devices
[  1953.867] (==) Automatically enabling devices
[  1953.867] (==) Automatically adding GPU devices
[  1953.867] (==) Automatically binding GPU devices
[  1953.867] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  1953.867] (WW) The directory "/usr/share/fonts/misc" does not exist.
[  1953.867] 	Entry deleted from font path.
[  1953.867] (WW) The directory "/usr/share/fonts/TTF" does not exist.
[  1953.867] 	Entry deleted from font path.
[  1953.867] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[  1953.867] 	Entry deleted from font path.
[  1953.867] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[  1953.867] 	Entry deleted from font path.
[  1953.867] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[  1953.867] 	Entry deleted from font path.
[  1953.867] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[  1953.867] 	Entry deleted from font path.
[  1953.867] (==) FontPath set to:
	
[  1953.868] (==) ModulePath set to "/usr/lib/xorg/modules"
[  1953.868] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[  1953.868] (II) Module ABI versions:
[  1953.868] 	X.Org ANSI C Emulation: 0.4
[  1953.868] 	X.Org Video Driver: 25.2
[  1953.868] 	X.Org XInput driver : 24.4
[  1953.868] 	X.Org Server Extension : 10.0
[  1953.868] (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory)
[  1953.868] (--) using VT number 7

[  1953.868] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[  1953.880] (--) PCI:*(1@0:0:0) 1106:3371:1734:10f7 rev 1, Mem @ 0xa0000000/536870912, 0xc8000000/16777216, BIOS @ 0x????????/131072
[  1953.880] (II) LoadModule: "glx"
[  1953.881] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  1953.883] (II) Module glx: vendor="X.Org Foundation"
[  1953.884] 	compiled for 1.21.1.10, module version = 1.0.0
[  1953.884] 	ABI class: X.Org Server Extension, version 10.0
[  1953.884] (==) Matched openchrome as autoconfigured driver 0
[  1953.884] (==) Matched modesetting as autoconfigured driver 1
[  1953.884] (==) Matched fbdev as autoconfigured driver 2
[  1953.884] (==) Matched vesa as autoconfigured driver 3
[  1953.884] (==) Assigned the driver to the xf86ConfigLayout
[  1953.884] (II) LoadModule: "openchrome"
[  1953.884] (WW) Warning, couldn't open module openchrome
[  1953.884] (EE) Failed to load module "openchrome" (module does not exist, 0)
[  1953.884] (II) LoadModule: "modesetting"
[  1953.884] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  1953.885] (II) Module modesetting: vendor="X.Org Foundation"
[  1953.885] 	compiled for 1.21.1.10, module version = 1.21.1
[  1953.885] 	Module class: X.Org Video Driver
[  1953.885] 	ABI class: X.Org Video Driver, version 25.2
[  1953.885] (II) LoadModule: "fbdev"
[  1953.885] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[  1953.886] (II) Module fbdev: vendor="X.Org Foundation"
[  1953.886] 	compiled for 1.21.1.10, module version = 0.5.0
[  1953.886] 	Module class: X.Org Video Driver
[  1953.886] 	ABI class: X.Org Video Driver, version 25.2
[  1953.886] (II) LoadModule: "vesa"
[  1953.886] (WW) Warning, couldn't open module vesa
[  1953.886] (EE) Failed to load module "vesa" (module does not exist, 0)
[  1953.886] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  1953.886] (II) FBDEV: driver for framebuffer: fbdev
[  1953.892] (EE) open /dev/dri/card0: No such file or directory
[  1953.892] (WW) Falling back to old probe method for modesetting
[  1953.892] (EE) open /dev/dri/card0: No such file or directory
[  1953.892] (II) Loading sub module "fbdevhw"
[  1953.892] (II) LoadModule: "fbdevhw"
[  1953.893] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[  1953.894] (II) Module fbdevhw: vendor="X.Org Foundation"
[  1953.894] 	compiled for 1.21.1.10, module version = 0.0.2
[  1953.894] 	ABI class: X.Org Video Driver, version 25.2
[  1953.894] (EE) Unable to find a valid framebuffer device
[  1953.894] (WW) Falling back to old probe method for fbdev
[  1953.894] (II) Loading sub module "fbdevhw"
[  1953.894] (II) LoadModule: "fbdevhw"
[  1953.894] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[  1953.894] (II) Module fbdevhw: vendor="X.Org Foundation"
[  1953.894] 	compiled for 1.21.1.10, module version = 0.0.2
[  1953.894] 	ABI class: X.Org Video Driver, version 25.2
[  1953.894] (EE) open /dev/fb0: No such file or directory
[  1953.895] (EE) Screen 0 deleted because of no matching config section.
[  1953.895] (II) UnloadModule: "modesetting"
[  1953.895] (EE) Screen 0 deleted because of no matching config section.
[  1953.895] (II) UnloadModule: "fbdev"
[  1953.895] (II) UnloadSubModule: "fbdevhw"
[  1953.895] (EE) Device(s) detected, but none match those in the config file.
[  1953.895] (EE) 
Fatal server error:
[  1953.895] (EE) no screens found(EE) 
[  1953.895] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[  1953.895] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[  1953.895] (EE) 
[  1953.899] (EE) Server terminated with error (1). Closing log file.

grknight · Post by **grknight** » Thu Dec 28, 2023 1:21 pm

This is showing that there is no kernel support ready yet. Please show the latest dmesg and kernel config on a paste site.

coffy_mug · Post by **coffy_mug** » Thu Dec 28, 2023 3:34 pm

Output of dmesg
https://pastebin.com/H767Fmpr

/usr/src/linux/.config
https://pastebin.com/4Aw7Rwhx

after reading the kernel config it indeed appears that CONFIG_FB_VIA has not been set. After reading the guide once again I saw that in the article the 'savedconfig' USE flag is being set on per package basis but assuming that package.use is a file not a directory, as a result 'savedconfig' flag was not set. I'm sorry for this oversight. Please let me know if anything else is wrong.

grknight · Post by **grknight** » Thu Dec 28, 2023 5:03 pm

coffy_mug wrote:after reading the kernel config it indeed appears that CONFIG_FB_VIA has not been set. After reading the guide once again I saw that in the article the 'savedconfig' USE flag is being set on per package basis but assuming that package.use is a file not a directory, as a result 'savedconfig' flag was not set. I'm sorry for this oversight. Please let me know if anything else is wrong.

Just this. When using gentoo-kernel package, a consistent solution is to put CONFIG_FB_VIA=y into /etc/kernel/config.d/video.conf (make path and file as needed).
Then, rebuild gentoo-kernel to apply it.

alexander-n8hgeg5e · Post by **alexander-n8hgeg5e** » Fri Dec 29, 2023 10:17 am

coffy_mug wrote:Do they need to be started be openrc and added to the runlevel

You could, but it was only meant to show how I use them to clean my screen and add some color.
It was only meant for testing.
You can test a running xserver with these commands.
For testing it is enough to run them in a terminal.
(There may be some access restrictions depending on the user id or host )
But at first the xserver needs to start.

alexander-n8hgeg5e · Post by **alexander-n8hgeg5e** » Fri Dec 29, 2023 10:44 am

coffy_mug wrote:in the previous reply where i ran startx --verbose it's telling me that the log file is in /var/log/Xorg.0.log but I need to force reboot to be able to display it. After reboot I don't see the file.

It depends on the commandline options how much is written in the log file. If a program is done (exited with some exit code) the contents should be in the file in case the program wrote something to this file.
If you can get it to print stuff out to the screen the the reason why you can't feed it in a file can be
that the operator of the shell tries to send stdout into the file but "X" prints to stderr.
If you still can see the output while trying to direct it into a file It is likely that this happened.
Just likely because programs can detect whether a terminal or a file/pipe is attached and even could
duplicate the output to the other filedescriptor upon detection though I think this makes no sense.

In bash to write both stdout and stderr into a file:

Code: Select all

X --help  &> outputfile_with_help

or grep it with:

Code: Select all

X --help |& grep thing

or

Code: Select all

X --help  2>&1 | grep thing

coffy_mug · Post by **coffy_mug** » Fri Dec 29, 2023 6:44 pm

After rebuilding the kernel and running startx the screen does the same maybe in a slightly diffrent pattern but when rebooting it appears that x is being automaticly started which was not happening earlier, as a result every i boot into the new kernel these lines appear. I'm able to boot from the older version of the kernel. After running both configs through text comparison I can see that only CONFIG_FB_VIA has been changed.

alexander-n8hgeg5e wrote: For testing it is enough to run them in a terminal.
(There may be some access restrictions depending on the user id or host )
But at first the xserver needs to start.

From my understanding when xserver is started by running startx. These weird lines are being displayed because of that it's impossible appropriately run these commands.

alexander-n8hgeg5e · Post by **alexander-n8hgeg5e** » Sun Dec 31, 2023 11:10 am

Ah ok, so it starts and then your screen is messed up and it doesn't take you back to some terminal?
You can switch back to the linux terminal by pressing Ctrl-Alt-Fkey. For Fkey you can try all the keys from F1 up.
After you are back in any linux terminal it is enough to press Alt-Fkey to switch through the terminals and back to the xserver in case it is running.(somehow usually F7) If it isn't running then you shouldn't need to press Ctrl-Alt-Fkey to get out.
Is it running? In case it's running then you are a step further.
You also can start X with the command "X" and get help with X -help or X --help. X is somewhat different, all the long args take only one "-" (except --help)

coffy_mug · Post by **coffy_mug** » Mon Jan 01, 2024 1:08 am

ok so can someone expplain me this while looking for supported hardware on fbdev and openchrome i found that my card is supported in both. So a question arises what driver is the right one if not both.
https://cateee.net/lkddb/web-lkddb/FB_VIA.html
https://www.freedesktop.org/wiki/Opench ... dHardware/

grknight · Post by **grknight** » Mon Jan 01, 2024 1:14 am

coffy_mug wrote:ok so can someone expplain me this while looking for supported hardware on fbdev and openchrome i found that my card is supported in both. So a question arises what driver is the right one if not both.
https://cateee.net/lkddb/web-lkddb/FB_VIA.html
https://www.freedesktop.org/wiki/Opench ... dHardware/

I recommended FB_VIA because "Openchrome" DRM is deleted in the latest kernels. In addition, your particular PCI ID was never added to the kernel's Openchrome DRM support.
Spending time getting the VIA framebuffer working is the best use of time.

coffy_mug · Post by **coffy_mug** » Mon Jan 01, 2024 8:30 am

alexander-n8hgeg5e wrote: You can switch back to the linux terminal by pressing Ctrl-Alt-Fkey. For Fkey you can try all the keys from F1 up.

I tried to do that didn't work

alexander-n8hgeg5e · Post by **alexander-n8hgeg5e** » Mon Jan 01, 2024 3:13 pm

Hm,... maybe it needs libinput in the xorg drivers
and it's missing or so... Not sure about this.
The debug output of X should give some hints.

You can select the kernel right? and with the other kernel it
boots into something usable ?
Then I suggest disable the autostart of everything that tries
to start the xserver like xdm (x desktop manager).
Then you can manually start the xserver and, although it maybe will
mess up your screen again it allows
you to run a command in the background that kills it
after some time.
And maybe this helps to get it back to normal after a test.
If you got a serial port or another computer with "ssh"
then the best setup for testing the xserver would be
to log in the system with one of these options.
Because then you don't need a working screen nor a keyboard on
the system, you only need the cable and you can do all the monitor testing
without locking you out.

coffy_mug · Post by **coffy_mug** » Thu Jan 04, 2024 3:13 pm

I'm not able to run commands while in ssh after running startx, Its just like whole computer crashes.

alexander-n8hgeg5e · Post by **alexander-n8hgeg5e** » Sat Feb 24, 2024 9:13 pm

I guess it's the display driver crashing the system.
And you didn't changed runlevels to start the display server? Because if you start the display server by changing runlevels
then maybe it also stops your sshd.