I also had an issue with sddm not starting on my GeForce GT 730 and downgrading the Nvidia driver resolved it for me. So it appears there may be some sort of issue.
I also had an issue with sddm not starting on my GeForce GT 730 and downgrading the Nvidia driver resolved it for me. So it appears there may be some sort of issue.
Yes… it could be
For first thing i would try with oldest nvidia driver
Back to top
Buffoon Veteran
Joined: 17 Jun 2015 Posts: 1369 Location: EU or US
Posted: Thu Mar 24, 2016 2:27 pm Post subject:
Probably there is some framebuffer enabled in kernel that grabs the device and the nvidia driver is unable to load.
Back to top
Maxxx Guru
Joined: 12 Jan 2016 Posts: 593 Location: Italia
Posted: Thu Mar 24, 2016 2:48 pm Post subject:
Yes, he should enable framebuffer in kernel menu, but not in submenu concerning nvidia framebuffer (these must be removed all).
Intel and nVidia graphics … that’s the Optimus warning sign.
Er… iv just know it ‘probed’ my double graphics, one Intel and one nVidia which both in my PC, is that an Error? and what’s the deeper meaning about it?
And, as everyone said im try install 340.93 version, but unfotunately, a new issue throw… «Unable to build the NVIDIA kernel module.»
and i don’t know what that means. may means this version is not fully compatible with my kernel? anyway im searching it now…
Code:
Kernel source path: ‘/usr/src/linux’
Kernel output path: ‘/usr/src/linux’
Performing rivafb check.
Performing nvidiafb check.
Performing Xen check.
Performing PREEMPT_RT check.
Cleaning kernel module build directory.
Building NVIDIA kernel module:
Building: [##############################] 100%
ERROR: Unable to build the NVIDIA kernel module.
ERROR: Installation has failed. Please see the file
‘/var/log/nvidia-installer.log’ for details. You may find suggestions
on fixing installation problems in the README available on the Linux
In file included from /usr/src/linux-4.5.0-gentoo/include/uapi/linux/stddef.h:1:0,
from /usr/src/linux-4.5.0-gentoo/include/linux/stddef.h:4,
from /usr/src/linux-4.5.0-gentoo/include/uapi/linux/posix_types.h:4,
……
……more and more……
……
/usr/src/linux-4.5.0-gentoo/include/linux/percpu-refcount.h:276:3: note: in expansion of macro ‘this_cpu_sub’
this_cpu_sub(*percpu_count, nr);
^
In file included from /usr/src/linux-4.5.0-gentoo/include/uapi/linux/stddef.h:1:0,
from /usr/src/linux-4.5.0-gentoo/include/linux/stddef.h:4,
from /usr/src/linux-4.5.0-gentoo/include/uapi/linux/posix_types.h:4,
from /usr/src/linux-4.5.0-gentoo/include/uapi/linux/types.h:13,
from /usr/src/linux-4.5.0-gentoo/include/linux/types.h:5,
from /usr/src/linux-4.5.0-gentoo/include/uapi/linux/capability.h:16,
from /usr/src/linux-4.5.0-gentoo/include/linux/capability.h:15,
from /usr/src/linux-4.5.0-gentoo/include/linux/sched.h:15,
from /usr/src/linux-4.5.0-gentoo/include/linux/utsname.h:5,
from /tmp/selfgz3541/NVIDIA-Linux-x86_64-340.93/kernel/nv-linux.h:44,
from /tmp/selfgz3541/NVIDIA-Linux-x86_64-340.93/kernel/nv-procfs.c:15:
/usr/src/linux-4.5.0-gentoo/arch/x86/include/asm/uaccess.h: In function ‘copy_from_user’:
/usr/src/linux-4.5.0-gentoo/arch/x86/include/asm/uaccess.h:734:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
if (likely(sz < 0 || sz >= n))
^
/usr/src/linux-4.5.0-gentoo/include/linux/compiler.h:165:40: note: in definition of macro ‘likely’
# define likely(x) __builtin_expect(!!(x), 1)
^
/usr/src/linux-4.5.0-gentoo/arch/x86/include/asm/uaccess.h: In function ‘copy_to_user’:
/usr/src/linux-4.5.0-gentoo/arch/x86/include/asm/uaccess.h:752:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
if (likely(sz < 0 || sz >= n))
^
/usr/src/linux-4.5.0-gentoo/include/linux/compiler.h:165:40: note: in definition of macro ‘likely’
# define likely(x) __builtin_expect(!!(x), 1)
^
/tmp/selfgz3541/NVIDIA-Linux-x86_64-340.93/kernel/nv-procfs.c: In function ‘nv_procfs_read_registry’:
/tmp/selfgz3541/NVIDIA-Linux-x86_64-340.93/kernel/nv-procfs.c:359:12: error: void value not ignored as it ought to be
Makefile:182: recipe for target ‘nvidia.ko’ failed
make: *** [nvidia.ko] Error 1
-> Error.
ERROR: Unable to build the NVIDIA kernel module.
ERROR: Installation has failed. Please see the file ‘/var/log/nvidia-installer.log’ for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.
Last edited by se ven on Fri Mar 25, 2016 3:58 am; edited 1 time in total
Back to top
Buffoon Veteran
Joined: 17 Jun 2015 Posts: 1369 Location: EU or US
Posted: Fri Mar 25, 2016 3:50 am Post subject:
What are you doing? Are you running nvidia installer? This is not how you install it in Gentoo. Besides, if this is Optimus as Neddy pointed out you need completely different approach.
Back to top
se ven n00b
Joined: 22 Feb 2016 Posts: 18
Posted: Fri Mar 25, 2016 4:55 am Post subject:
Quote:
What are you doing? Are you running nvidia installer? This is not how you install it in Gentoo. Besides, if this is Optimus as Neddy pointed out you need completely different approach.
Sorry, im not sure whats your mean pointed about your solution for my issues.
Of course i need different approach (may not completely…), but i need search other same issues which solved the problems before make my opinions.
and Of course it’s my point. i’ll choise what should i do or how.
and im running nvidia-installer to install it actually(i don’t know why not even now). and im no such care whats the Gentoo’s way in my_gentoo.
thank you for your reply.
bytheway, what’s the Gentoo’s way to install my Graphic s i find the issue in wiki but not fine so im here…
Any help appreciate.
Back to top
Maxxx Guru
Joined: 12 Jan 2016 Posts: 593 Location: Italia
Posted: Fri Mar 25, 2016 9:18 pm Post subject:
If your kernel configuration is ok, you must uninstall current nvidia driver (or even other video driver)…
Then you must install right version of nvidia driver.
To do this, in package.mask file (or if package.mask is a directory you can create file mask) you must insert «>=x11-drivers/nvidia-drivers-340.96» line… in this way you can install only previous version of 340.96, which is 340.93-r1.
Now you can emerge nvidia driver: «emerge —ask x11-drivers/nvidia-drivers» and check that the version is right.
At the end of installation do these commands:
«nvidia-xconfig»
«eselect opengl set nvidia»
and
«gpasswd -a (user) video»
Try like this
Back to top
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 51966 Location: 56N 3W
Posted: Fri Mar 25, 2016 10:01 pm Post subject:
se ven,
Google says that PCI ID 10de:0fd1 belongs to a nVidia GK107M [GeForce GT 650M].
Looking up GeForce GT 650M at the nVidia site says you need 361.28 for an amd64 system.
Later versions may or may not work.
As nvidia-drivers is a binary blob (the source code is not published) its often out of step with the kernel, and you have a very new kernel
/var/log/Xorg.0.log:
[ 2787.186] Build Operating System: Linux 4.5.0-gentoo x86_64 Gentoo
You must not use nvidia-installer yourself. The Gentoo ebuild downloads the nvidia-installer, installs the binary blob and patches and builds the ‘shim’ code. If you run nvidia-installer yourself, you will be missing the shim code patches. Then you get to keep the pieces.
First, run nvidia-installer and tell it to uninstall. It probably has a -h or —help option to give you instructions
It appears that 361.28 is stable so you should get at least that.
If so, emerge it for real. It will install nvidia-drivers the Gentoo way.
Optimus graphics systems are a whole new can of worms. Laptops are very power/space/weight conscious.
Once upon a time, laptop graphics systems were not very good. Then came the idea of having a high performance high power graphics system that could be switched in when needed. The killer here is the switch. It takes up space, weight and power. Such systems are called video multiplexing.
Multiplexing being the technical name for the switching.
The next generation were known as muxless because they don’t have this switch. Optimus is an example of this design. Its typically found in notebooks and laptops that feature both Intel and nVidia graphics.
The upside to removing the switch, in the power/weight/space savings. The down side is that the nVidia graphics chip is not connected to the display ever — at all. This means that if you do have an Optimus system and you succeed is making the nVidia driver run on its own, you will only get a black screen.
Optimus systems always use the Intel chipset to put the picture onto the display surface but they can use either chip set to render the image into the pixel buffer. Its important to know if you have an Optimus system or not before you go much further. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
se ven n00b
Joined: 22 Feb 2016 Posts: 18
Posted: Thu Mar 31, 2016 4:14 am Post subject:
Er…First apologize for my very late reply and thanks for any help.
So, :
NeddySeagoon wrote:
Optimus graphics systems are a whole new can of worms. Laptops are very power/space/weight conscious.
Once upon a time, laptop graphics systems were not very good. Then came the idea of having a high performance high power graphics system that could be switched in when needed. The killer here is the switch. It takes up space, weight and power. Such systems are called video multiplexing.
Multiplexing being the technical name for the switching.
The next generation were known as muxless because they don’t have this switch. Optimus is an example of this design. Its typically found in notebooks and laptops that feature both Intel and nVidia graphics.
The upside to removing the switch, in the power/weight/space savings. The down side is that the nVidia graphics chip is not connected to the display ever — at all. This means that if you do have an Optimus system and you succeed is making the nVidia driver run on its own, you will only get a black screen.
Optimus systems always use the Intel chipset to put the picture onto the display surface but they can use either chip set to render the image into the pixel buffer. Its important to know if you have an Optimus system or not before you go much further.
thanks for your reminding. it may the point of this question.
I check my laptop graphic and search it in nVidia and, my laptop graphics use a Optimus system it is…
Then, as https://wiki.gentoo.org/wiki/NVIDIA/Optimus said,
Double check the kernel .config just like this:
Code:
Direct Rendering Manager —>
Direct Rendering Manager (Xfree86 4.1.0 and higher DRI support) —>
[*] Enable legacy fbdev support for your modesetting driver
<*> Intel 8xx/9xx/G3x/G4x/HD Graphics
[*] Enable preliminary support for prerelease Intel hardware by default
when i `startx` it’s only display a black screen with a cursor without flash on left top of screen. im not sure does the problem fixed, and i can though next step?
with quit the startx manually, The Xorg.0.log looks like this:
Code:
[ 969.856]
X.Org X Server 1.18.2
Release Date: 2016-03-11
[ 969.857] X Protocol Version 11, Revision 0
[ 969.858] Build Operating System: Linux 3.13.0-83-generic x86_64 Gentoo
[ 969.858] Current Operating System: Linux se_ven 4.5.0-gentoo #1 SMP Wed Mar 30 23:07:19 CST 2016 x86_64
[ 970.101] (II) XINPUT: Adding extended input device «Dell WMI hotkeys» (type: KEYBOARD, id 14)
[ 970.101] (**) Option «xkb_rules» «evdev»
[ 1006.126] (II) evdev: Dell WMI hotkeys: Close
[ 1006.126] (II) UnloadModule: «evdev»
[ 1006.126] (II) UnloadModule: «synaptics»
[ 1006.127] (II) evdev: AT Translated Set 2 keyboard: Close
[ 1006.127] (II) UnloadModule: «evdev»
[ 1006.127] (II) evdev: Laptop_Integrated_Webcam_HD: Close
[ 1006.127] (II) UnloadModule: «evdev»
[ 1006.127] (II) evdev: Logitech USB Optical Mouse: Close
[ 1006.127] (II) UnloadModule: «evdev»
[ 1006.127] (II) evdev: Video Bus: Close
[ 1006.127] (II) UnloadModule: «evdev»
[ 1006.127] (II) evdev: Power Button: Close
[ 1006.127] (II) UnloadModule: «evdev»
[ 1006.127] (II) evdev: Video Bus: Close
[ 1006.127] (II) UnloadModule: «evdev»
[ 1006.127] (II) evdev: Power Button: Close
[ 1006.127] (II) UnloadModule: «evdev»
[ 1006.130] (II) NVIDIA(GPU-0): Deleting GPU-0
[ 1006.133] (II) Server terminated successfully (0). Closing log file.
Code:
…
[ 969.874] (II) NVIDIA dlloader X Driver 364.12 Wed Mar 16 20:16:45 PDT 2016
[ 969.874] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 969.874] (—) using VT number 8
…
and there is some problem i can’t understand:
Code:
…
[ 969.879] (EE) Screen 0 deleted because of no matching config section.
…
what is the ‘Screen 0’? is that means i confugure it in somewhere out xorg.conf?
and:
Code:
…
[ 969.883] (WW) NVIDIA(0): Unable to get display device for DPI computation.
…
Back to top
Maxxx Guru
Joined: 12 Jan 2016 Posts: 593 Location: Italia
Posted: Thu Mar 31, 2016 7:44 am Post subject:
In my xorg.conf, at «Screen» section, there is:
Identifier «Screen0»
Device «Device0»
Monitor «Monitor0»
In your xorg.conf there are 2 «screen» sections without Screen0… instead there is «nvidia», but nvidia must be in «Device» section.
In your previous xorg.conf, the one created by nvidia-xconfig, there was «Screen0» correctly.
Screen0 is the default screen for X11 and if you miss it in xorg.conf i think it don’t work.
I think that now your problem is this.
Back to top
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 51966 Location: 56N 3W
Posted: Thu Mar 31, 2016 5:32 pm Post subject:
se ven,
In each section of xorg.conf is a line
Code:
Identifier «[string]»
Often its the only mandatory field in a section.
There are a few rules to follow to keep Xorg happy
All the sections of the same type must have unique
Code:
Identifier «[string]»
entries.
This is how Xorg tells multiple sections of the same type apart.
You can reuse
Code:
Identifier «[string]»
entries in different section types if you like but it will make your head hurt.
For your own sanity make all the
Code:
Identifier «[string]»
entries unique.
Xorg builds your X-server by starting with the
Code:
Section «ServerLayout»
part.
In your case it says to use a Screen section with Identifer «nvidia» and to input devices with section names «Mouse0» and «Keyboard0»
If these section call up other sections the entire list will be traversed.
Code:
Inactive «intel»
look like a bad option.
If your Intel graphics is inactive you will get nothing on the display. Its the only graphics you have that can transfer the image to the screen.
Walk the sections by hand to see what will be used in your X Server. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
Display posts from previous:
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
I’m trying to build the Xorg X Window System Environment as outlined in Beyond Linux From Scratch Version 8.0. My BLFS system resides in a Virtual Machine using VirtualBox Version 5.0.10 r104061.
I followed the steps as outlined in Chapter 24. X Window System Environment. However, when I finished my installation and tried startx, I got the output below:-
Release Date: 2017-01-11
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.9.5 x86_64
Current Operating System: Linux LFS 4.9.5 #1 SMP Thu Feb 23 22:59:41 GMT 2017 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.5-lfs-SVN-20170122 root=/dev/sda1 ro
Build Date: 01 March 2017 10:04:52PM
Current version of pixman: 0.34.0
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 Mar 22 21:42:24 2017
(==) 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
And I see the following log in /var/log/Xorg.0.log
57.972]
X.Org X Server 1.19.1
Release Date: 2017-01-11
[ 57.974] X Protocol Version 11, Revision 0
[ 57.974] Build Operating System: Linux 4.9.5 x86_64
[ 57.975] Current Operating System: Linux LFS 4.9.5 #1 SMP Thu Feb 23 22:59:41 GMT 2017 x86_64
[ 57.975] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.5-lfs-SVN-20170122 root=/dev/sda1 ro
[ 57.975] Build Date: 01 March 2017 10:04:52PM
[ 57.975]
[ 57.975] Current version of pixman: 0.34.0
[ 57.975] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 57.975] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 57.978] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 22 21:42:24 2017
[ 57.990] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 57.992] (==) No Layout section. Using the first Screen section.
[ 57.992] (==) No screen section available. Using defaults.
[ 57.992] (**) |-->Screen "Default Screen Section" (0)
[ 57.992] (**) | |-->Monitor "<default monitor>"
[ 57.992] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 57.992] (**) | |-->Device "radeon"
[ 57.992] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 57.992] (==) Automatically adding devices
[ 57.992] (==) Automatically enabling devices
[ 57.992] (==) Automatically adding GPU devices
[ 57.994] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 57.999] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/X11/misc/".
[ 57.999] Entry deleted from font path.
[ 57.999] (Run 'mkfontdir' on "/usr/share/fonts/X11/misc/").
[ 58.002] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/X11/100dpi/".
[ 58.002] Entry deleted from font path.
[ 58.002] (Run 'mkfontdir' on "/usr/share/fonts/X11/100dpi/").
[ 58.003] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/X11/75dpi/".
[ 58.003] Entry deleted from font path.
[ 58.003] (Run 'mkfontdir' on "/usr/share/fonts/X11/75dpi/").
[ 58.003] (==) FontPath set to:
/usr/share/fonts/X11/TTF/,
/usr/share/fonts/X11/OTF/,
/usr/share/fonts/X11/Type1/
[ 58.003] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 58.003] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 58.003] (II) Loader magic: 0x810c40
[ 58.003] (II) Module ABI versions:
[ 58.003] X.Org ANSI C Emulation: 0.4
[ 58.003] X.Org Video Driver: 23.0
[ 58.003] X.Org XInput driver : 24.1
[ 58.003] X.Org Server Extension : 10.0
[ 58.007] (--) PCI:*(0:0:2:0) 80ee:beef:0000:0000 rev 0, Mem @ 0xe0000000/16777216, BIOS @ 0x????????/131072
[ 58.007] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 58.007] (II) LoadModule: "glx"
[ 58.008] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 58.040] (II) Module glx: vendor="X.Org Foundation"
[ 58.040] compiled for 1.19.1, module version = 1.0.0
[ 58.040] ABI class: X.Org Server Extension, version 10.0
[ 58.040] (II) LoadModule: "ati"
[ 58.041] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[ 58.042] (II) Module ati: vendor="X.Org Foundation"
[ 58.042] compiled for 1.19.1, module version = 7.8.0
[ 58.042] Module class: X.Org Video Driver
[ 58.042] ABI class: X.Org Video Driver, version 23.0
[ 58.042] (EE) No drivers available.
[ 58.042] (EE)
Fatal server error:
[ 58.044] (EE) no screens found(EE)
[ 58.045] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 58.046] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 58.046] (EE)
[ 58.046] (EE) Server terminated with error (1). Closing log file.
I’ve tried rebuilding the kernel with
Device Drivers --->
Graphics support --->
<*> Direct Rendering Manager (XFree86 ... support) ---> [CONFIG_DRM]
<*> DRM driver for VMware Virtual GPU [CONFIG_DRM_VMWGFX]
[*] Enable framebuffer console under vmwgfx by default [CONFIG_DRM_VMWGFX_FBCON]
and
Device Drivers --->
Graphics support --->
<> Direct Rendering Manager (XFree86 ... support) ---> [CONFIG_DRM]
and in both cases got the same error message. This is the output of lspci for the graphics adapter
Hello everyone, and thank you for taking the time to help me. When I delete /etc/X11/xorg.conf then Xorg starts normally. But if I run nvidia-xconfig and it creates a /etc/X11/xorg.conf file then Xorg won’t boot and I get this log file instead. So do I really need the file1 /etc/X11/xorg.conf at all?
[ 9768.914] (--) controlling tty is VT number 1, auto-enabling KeepTty
[ 9768.915] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c3
[ 9768.916] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 9768.916] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0
[ 9768.916] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 9768.916] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 12 paused 0
[ 9768.917] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules"
[ 9768.917] (--) PCI:*(0:0:2:0) 8086:0a16:17aa:3800 rev 11, Mem @ 0xb5000000/4194304, 0xc0000000/268435456, I/O @ 0x00006000/64, BIOS @ 0x????????/131072
[ 9768.917] (--) PCI: (0:9:0:0) 10de:1290:17aa:3800 rev 161, Mem @ 0xb3000000/16777216, 0xa0000000/268435456, 0xb0000000/33554432, I/O @ 0x00003000/128
[ 9768.917] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 9768.917] (II) LoadModule: "glx"
[ 9768.918] (II) Loading /usr/lib/nvidia/xorg/libglx.so
[ 9768.921] (II) Module glx: vendor="NVIDIA Corporation"
[ 9768.921] compiled for 4.0.2, module version = 1.0.0
[ 9768.921] Module class: X.Org Server Extension
[ 9768.921] (II) NVIDIA GLX Module 378.13 Tue Feb 7 18:25:34 PST 2017
[ 9768.921] (II) LoadModule: "nvidia"
[ 9768.921] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 9768.921] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 9768.921] compiled for 4.0.2, module version = 1.0.0
[ 9768.921] Module class: X.Org Video Driver
[ 9768.921] (II) NVIDIA dlloader X Driver 378.13 Tue Feb 7 18:01:51 PST 2017
[ 9768.921] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 9768.921] (II) systemd-logind: releasing fd for 226:1
[ 9768.922] (EE) No devices detected.
[ 9768.922] (EE)
Fatal server error:
[ 9768.922] (EE) no screens found(EE)
[ 9768.922] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 9768.922] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 9768.922] (EE)
[ 9768.941] (EE) Server terminated with error (1). Closing log file.
When I start Xorg with «startx» and everyting works fine like it normally does without the xorg.conf file, then how do I know that Nvidia drivers are actually loaded? This is what «lsmod» returned:
Thanks in advance for helping me resolve this issue. As the title suggest, I’m currently having issues with Xorg not finding my screen/monitor. I just finished installing the base system on an old Toshiba Satellite laptop using an ISO image downloaded from www.freebsd.org. After completing the installation, I proceeded to:
a) Install Xorg
b) Create individual configuration files for the video, monitor and resolution
c)Added my user to the video, wheel group.
d) Installed KDE and SDDM
Immediately after installing Xorg and before downloading KDE, I ran «startx» and got Xterm, which I thought meant I was on the right path. After installing KDE and SDDM, startx would no longer work and I kept getting the «No Screen Found». Here are the specs of the laptop I’m working with:
Toshiba Satellite C655D-S5136
AMD Athlon II P340 — 2.2 Ghz
6GB of Ram
ATI Mobility Radeon HD 4225 (RS880M)
I’ve also installed «drm-fbsd12.0-kmod via pkg install and tried to build it from ports but failed with the following error:
Code:
"drm-fbsd12.0-kmod-4.16.g20200221 requires kernel source files in SRC_BASE-/usr/src"
Any suggestions on how to get around this issue are welcomed.
Thanks.
Last edited by a moderator: Dec 8, 2020
#2
drm-fbsd12.0-kmod-4.16.g20200221 requires kernel source files in SRC_BASE-/usr/src»
You need fetch the FreeBSD source code into /usr/src.
I also noticed that you are using a radeon card. You need add the radeonkms.ko driver; see https://wiki.freebsd.org/Graphics#AMD_Graphics
Lastly, you may find Wayland work as an alternative to Xorg. An you can try a different login manager and desktop environment with it e.g sway, the 3d environment (wayfire),etc.
Thread Starter
#3
Lamia,
Thanks for the suggestions. I went back and reinstalled 12.2, but this time I made sure I selected to check «install src sources» option which addressed the «SRC Missing» error. Installation went smooth. I then proceeded to install Xorg again, and XCFE. Additionally, I was able to compiled the «drm-fbsd12.0-kmod-4.16.g20200221» port without any issues. After rebooting, I saw a flash on the console as it switched over to the new display driver, so I must be heading in the right direction. However, when I run «startx», X server is still complaining about the following:
— «Warning , couldnt open module radeon»
— «Failed to load module «radeon» (module does not exist, 0)
— «No drivers available»
-«No Screens found «
Do I also need to add a «monitor» configuration file in addition to a resolution file? Any suggestions? Thanks in advance.
Last edited by a moderator: Dec 8, 2020
#4
/usr/local/etc/X11/xorg.conf.d/driver-radeon.conf
: try to disable it (remove the file or the «.conf» at the end of the file name). It’s sometimes good to let Xorg choose its drivers.
#5
I did not have much luck with the above suggestions. None worked for me, unlike other people, until I switched to a PCI card. Infact, I had to go buy it — a NVIDIA card. Hopefully, the onboard graphics cards (INTEL XEON) will work again sometime in the future. The alternative desktop environment — Sway — worked though with the onboard card.
You should continue using the amdgpu.ko if your board/card is AMD. Simply add it to the kld_list, which already contains the radeonkms.ko.
You really don’t have to touch the Xorg files as advised by others. You can delete all modifications and let Xorg decide for itself.
You might also need try out an additional/replacement card if that would work. Several people had this problem and won’t go away until sometime in Feb.
Thread Starter
#6
It’s an old laptop, so for my purposes it does not make sense to go out and get a PCI card/find a newer laptop, but I appreciate the recommendation. Is this issue only related to the 12.2 release or the entire 12.xx series and do we know if it will be addressed when they release 13.0? As of right now, I feel like i»m getting closer to solving the problem, but not sure how to go forward. X server still complains that the module radeon couldnt be opened or it doesnt exist and/or no drivers are available. Do I need to install another driver in addition to «drm-fbsd12.0-kmod-4.16.g20200221»? From my understanding, this driver, when compiled from source has everything you need to get X working. The «no screen found»…. is this simply due to not having a «monitor» file in the xorg.conf.d directoy? The handbook goes over how to create a single file for «resolution», however, it does not mention creating a configuration file for a monitor.
#7
Is this issue only related to the 12.2 release or the entire 12.xx series
>Yes, it’s only 12.2.
and do we know if it will be addressed when they release 13.0?
Yes
#8
X server still complains that the module radeon couldnt be opened or it doesnt exist and/or no drivers are available. Do I need to install another driver in addition to «drm-fbsd12.0-kmod-4.16.g20200221»? From my understanding, this driver, when compiled from source has everything you need to get X working.
I am surely no expert when it comes to radeon graphics hardware, but I’d say you are right, that the KMS driver you load via kld_list should be all that is needed. But you are telling Xorg to load an additional radeon driver that doesn’t even seem to exist:
I concur with the advice to remove that configuration file and let Xorg try to autodetect the necessary driver. Or try changing the Driver line in that file to:
Thread Starter
#9
revising the «driver-radeon» config file and replacing «radeon» with «modesetting» seems to have done something….the «missing radeon module» went away, however, I’m not getting the following errors:
Code:
(EE) open /dev/dri/card0: No such file or directory
(WW) Falling back to old probe method for modesetting
(EE) open /dev/dri/card0: No such file or directory
(WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
(EE) Screen 0 deleted because of no matching config section
(II) UnloadModule" "modesetting"
(EE) Device(s) detected, but none match those in the config file
Fatal Server Error:
(EE) no screens found
In reading these errors, the VGA arbiter makes sense as this is an old laptop and the onboard gpu does not support multi-card(s). While I do have a «screen-resolution» config file, it does not specify which monitor to use, so maybe that is the issue here?
Last edited by a moderator: Dec 8, 2020
#10
In reading these errors, the VGA arbiter makes sense as this is an old laptop and the onboard gpu does not support multi-card(s). While I do have a «screen-resolution» config file, it does not specify which monitor to use, so maybe that is the issue here?
First — did you get your drm working? Before starting X, you should get the drm operational. Look into kldstat.
Also grep "[drm]" /var/log/messages.
You can try loading drm manually, but it is good to include kld_list="radeonkms" into the
/etc/rc.conf
.
.
Is it EFI boot or not? Radeons and EFI mismatch. So, in case of EFI, you should have hw.syscons.disable=1 in
/boot/loader.conf
. Not nice, but it works.
With older Radeons, you can try
graphics/drm-legacy-kmod/
.
I have put WITHOUT_MODULES=drm drm2 in the
/etc/make.conf
and rebuilt the kernel before installing the drm.
Last edited by a moderator: Dec 8, 2020
#11
As some of you have already said, what if they let xorg do everything automatically by skipping b) Create individual configuration files for the video, monitor and resolution? I for example only need to install drm-kmod for my AMD card and that’s it, the rest is done by xorg. If you want to activate a function then a config file is handy but otherwise not necessary.
Last edited by a moderator: Dec 8, 2020
#12
If you want to activate a function then a config file is handy but otherwise not necessary.
Also, when the hardware configuration is stable, it may have some benefit to copy the configuration into
/etc/X11/xorg.conf
. Not needed, but makes the Xorg start faster. BTW, Xorg is always restarted when you leave GUI and drop back to login manager.
Last edited by a moderator: Dec 8, 2020
#13
You can try loading drm manually, but it is good to include kld_list="radeonkms" into the /etc/rc.conf.
In order to use the driver built from ports (or installed from pkg for that matter) you need to specify the full path, otherwise you probably end up using the driver included in the base system, i.e. kld_list="/boot/modules/radeonkms.ko"
Last edited by a moderator: Dec 8, 2020
#14
In order to use the driver built from ports (or installed from pkg for that matter) you need to specify the full path, otherwise you probably end up using the driver included in the base system, i.e. kld_list=»/boot/modules/radeonkms.ko»
Base system gives a warning in the logfiles that drm is deprecated and will be removed in the future. I have disabled the base drm by putting WITHOUT_MODULES=drm drm2 in the
/etc/make.conf
and built a custom kernel. After that installed the
graphics/drm-fbsd12.0-kmod
.
Last edited by a moderator: Dec 8, 2020
#15
I have disabled the base drm by putting WITHOUT_MODULES=drm drm2 in the /etc/make.conf and built a custom kernel.
I guess that’s one way to do it
Thread Starter
#16
Thanks for all the suggestions, I tried them all and now I have a working KDE/Gnome environments. Not sure which one did the trick, but below are the steps I took:
— added kld_list="radeonkms to
/etc/rc.conf
-added hw.syscons.disable=1 to
/boot/loader.conf
Laptop seems to work be working now. Thanks again.
Last edited by a moderator: Dec 8, 2020
#17
Just came across this thread. I have the same error with AMD Ryzen 5 3400G & onboard Vega 11 GPU. Installed drm-kmod from «pkg», added kld_list=»/boot/loader/amdgpu.ko». Doesn’t work. Xorg still fails to start with no screens found. I have EFI boot & I’ve tried the «hw.syscons.disable=1» in /boot/loader.conf as well. That doesn’t help either. I’m really not good at setting up UIs & until now, didn’t have the need to worry much as I had nVidia cards & nVidia drivers that always worked. This is a new PC & I cannot get Xorg to start. What am I doing wrong?
#19
Tried this, but still doesn’t work. «startx» gives Xorg error — «Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices».
#20
Post your
/var/log/Xorg.0.log
.
#21
Post your
/var/log/Xorg.0.log
.
Xorg.0.log.txt
5.3 KB
· Views: 73
#22
Your video driver is not being loaded. Assuming an ATI card based on the logs. What card and how are you loading the driver?
#23
Your video driver is not being loaded. Assuming an ATI card based on the logs. What card and how are you loading the driver?
AMD Ryzen 5 3400G processor with onboard VEGA 11 GPU. Installed «amdgpu» from ports. When the OS boots, I get a mouse pointer on my console, but cannot get Xorg to work. And yes, after trying all the recommended things for ‘amdgpu’, the driver just doesn’t load. I have a UEFI system & if you read my post above, disabling the console output on start, which is the recommended UEFI fix with ‘amdgpu’, the driver still doesn’t load.
#24
I have found, on a new T495, that only vesa will work for the AMD GPU. I haven’t found a solution, don’t remember now what I tried. However, FreeBSD-CURRENT does work with drm-kmod for AMD.
Just my experience, for what it’s woth.
#25
Just came across this thread. I have the same error with AMD Ryzen 5 3400G & onboard Vega 11 GPU. Installed drm-kmod from «pkg», added kld_list=»/boot/loader/amdgpu.ko». Doesn’t work. Xorg still fails to start with no screens found. I have EFI boot & I’ve tried the «hw.syscons.disable=1» in /boot/loader.conf as well. That doesn’t help either. I’m really not good at setting up UIs & until now, didn’t have the need to worry much as I had nVidia cards & nVidia drivers that always worked. This is a new PC & I cannot get Xorg to start. What am I doing wrong?
The path /boot/loader/ doesnt exists, please use kld_list=»/boot/modules/amdgpu.ko» or only «amdgpu».
If you’re running off a live USB disk or changing your graphics card the error below might appear when Xorg is looking for the wrong drivers or device. You might also get this error while using the Nvidia drivers, I found however this was caused by some of the extra options added into the xorg.conf file (usually located /etc/X11/xorg.conf). If the case is that it’s a problem with the aditional options I suggest making a backup of the file and attempting to comment out (#) aditional options, this will need a bit more of an expert eye to see what isn’t needed though.. You can also use the following to rollback to a working version when using the Nvidia drivers.
There is a pretty simple fix, if it is caused by broken or changed xorg.conf file:
Fix:
Make a backup of your current Xorg.conf, just in case something goes even more wrong and it can be easily restored:
sudo cp /etc/X11/xorg.conf /etc/X11/xorg.bckup
Now you’ll want to restore the failsafe (sometimes called xorg.conf.backup) config to be used as the default:
Yeah, it was that simple (if this error was caused by a broken or changed xorg.conf anyway. So you can continue and start the x server with:
startx
Error:
X.Org X Server 1.9.0
Release Date: 2010-08-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-27-server i686 Ubuntu
Current Operating System: Linux ubuntu 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:34:50 UTC 2010 i686
Kernel command line: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
Build Date: 16 September 2010 05:39:22PM
xorg-server 2:1.9.0-0ubuntu7 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.18.4
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 Mar 4 11:35:54 2011
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) No devices detected.
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
ddxSigGiveUp: Closing log
giving up.
xinit: No such file or directory (errno 2): unable to connect to X server
xinit: No such process (errno 3): Server error.
Tags
disk, dual, fatal error, fix, gdm, guide, how to, monitor, no screens, nvidia, screens, startx, tutorial, ubunut, usb, where is xorg.conf, x11, xorg
This website uses cookies to improve your experience. We’ll assume you’re ok with this, but you can opt-out if you wish.Accept Read More
