Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
On my systems if the i915 kernel module gets loaded, the res gets dropped
from 1600x1200 back to only 1024x768
So, my newkernel.sh which I run upon upgrading the kernel deletes that module.
/sbin/lilo
(sets framebuffer console at res 1600x1200 32bit via vga=858)
(vga=ask shoes that this is indeed the correct setting)
echo rm -r /lib/modules/*.*.*/kernel/drivers/gpu/drm/i915
rm -r /lib/modules/*.*.*/kernel/drivers/gpu/drm/i915
echo rm -r /lib/modules/*.*.*/kernel/drivers/gpu/drm/nouveau
rm -r /lib/modules/*.*.*/kernel/drivers/gpu/drm/nouveau
(lilo sets framebuffer console at res 1600x1200 32bit via vga=858)
(vga=ask shows that this is indeed the correct setting)
I reinstalled the modules and ran lilo by itself.
Am here now in the new system booted to 6.9 and in X & firefox
BUT.... my res is at a max of 1024x768
With all previous setups for the past 15years all the way up to kernel 6.6.30
removing that i915 module works perfectly to allow keeping 1600x1200 res at the cli an in X
Why all of sudden is the 6.9 kernel not allowing X to start
without the i915 module being loaded ?!?!?
Is anyone aware of method of keeping the res at 1600x1200 with the i915 module loaded
(or the nouveau module on my other systems)
Exactly the same just now trying a Radeon video card but even worse.
The moment the radeon kernel module is loaded, res is dropped all the way down to 640x480
With all previous setups for the past 15years all the way up to kernel 6.6.30
removing that i915 module works perfectly to allow keeping 1600x1200 res at the cli an in X
Why all of sudden is the 6.9 kernel not allowing X to start
without the i915 module being loaded ?!?!?
Is it the same system that gave you 1600x1200 with kernel 6.6.30 and not with 6.9? Or did you have a new install of -current to test with kernel 6.9? If the latter option then you had installed package xf86-video-fbdev from extra/ which gave you 1600x1200 but you have not installed it yet on -current.
Is it the same system that gave you 1600x1200 with kernel 6.6.30 and not with 6.9? Or did you have a new install of -current to test with kernel 6.9? If the latter option then you had installed package xf86-video-fbdev from extra/ which gave you 1600x1200 but you have not installed it yet on -current.
The same problem exists in all of these situations...
1) existing system upgraded from 6.6.30 to 6.9.0 (and yesterday to 6.9.1)
2) fresh install of -current with /etc/X11/xorg.conf set to use Driver "vesa"
3) fresh install of -current after installing xf86-video-fbdev with /etc/X11/xorg.conf set to use Driver "fbdev"
In addition, when booted to 6.9.x and the i915 module is not loaded... no audio.
Oh yeah... this not just happening on one particular machine,
it's exactly the same on the i7 and on two different Intel DualCore machines.
All 3 of them have i915 on-board chisets
All 3 of them have the same problem with i915
and with the use of the nouveau module with an Nvidia card
and with the use of the radeon module with a Radeon card.
What happens if you install back the intel driver and remove /etc/X11/xorg.conf. Does it work then? What if you then add this as /etc/X11/xorg.conf.d/90-monitor.conf
What happens if you install back the intel driver and remove /etc/X11/xorg.conf. Does it work then? What if you then add this as /etc/X11/xorg.conf.d/90-monitor.conf
Or, the same except Driver "modesetting" instead of "intel".
Already tried that kind of stuff and it did not work. Still stuck at 1024x768
In addition, even if some settings could work to get the X display fixed...
that does not fix the problem on the framebuffer console which when dropped from 1600x1200
down to 1024x768 still uses the same number of lines of text which scroll-off the bottom of screen so can't be seen.
I did find a way to stop the i915 module from loading without deleting it.
Added "i915.modeset=0" to the lilo boot options.
However.... the same problem still happens in 6.9.x
but works perfectly fine with 6.6.30 and older.
I'd like to know what is special about your configuration that you couldn't previously get native display resolution using i915. I have a multitude of Intel GPUs of various vintages that by default using i915 kernel module, KMS and pure automagic X since server 1.17 (2015) have had no difficulty producing the native resolution of whatever display(s) were attached: 1024x768, 1280x1024, 1440x900, 1600x900, 1680x1050, 1920x1080, 1920x1200, 2560x1440 and 3840x2160. I have no doubt if I fetched my Dell 2000FP 1600x1200 from storage it would be automatically configured to 1600x1200. i915-driven Intel GPUs here in current service: 845, 865, 915, 945, 965, G31, G33, G41, Q43, Q45, Clarkdale, Haswell, Kaby Lake & Rocket Lake. This is with a variety of distros and accompanying default kernels, e.g. Debian, Fedora, Mageia, Mint, openSUSE & *buntu. e.g.:
All three display's resolutions were correctly determined automagically. AMD GPUs can be just as capable, though on this particular installation optional device and display drivers are employed:
I'd like to know what is special about your configuration that you couldn't previously get native display resolution using i915.
I don't know about glennmcc's configuration but I had a similar problem. The system used to use the native resolution 1280x1024 of the Lenovo monitor. I don't remember if something changed (kernel version?) or the monitor just stopped sending valid EDID data but the result is that now it does not set 1280x1024 automatically any more. Lines in dmesg:
I fixed X by adding a modeline in /etc/X11/xorg.conf.d/90-monitor.conf, similar to what I suggested here in post #4. I have not tried if adding video=1280x1024 to the kernel command line works here.
I fixed X by adding a modeline in /etc/X11/xorg.conf.d/90-monitor.conf, similar to what I suggested here in post #4. I have not tried if adding video=1280x1024 to the kernel command line works here.
The Intel DDX display driver is the only FOSS display driver I'm aware of where video= on kernel cmdline is inherited by X. For modesetting, radeon, amgdpu and nouveau driver users, it only applies on the VTs.
I've never required a modeline to solve an EDID problem. X knows perfectly well how to generate modelines when given the data it needs. Whenever an xorg .conf file with proper Horizsync and VertRefresh has failed to do that for me, so did attempts to solve via added modelines. Last needed was long ago, as all my displays with faulty EDID have been disposed of.
Quote:
There is also Option "DRI" "false" because opengl on a pentium4 + 945G graphics is much faster with software rendering.
I have 5 PCs with 945G. 3 have either ATI or NVidia GPUs installed. One of the other two has a Pentium D. The other follows:
This requires no graphics configuration, except when used with two displays and mirroring is undesired, so I use xrandr to move the smaller display to the right of the larger. I don't notice any problem with rendering speed, given the age and character of the GPU, and hadn't tried disabling DRI. With defaults only, glmark2 score is 167. I created /etc/X11/xorg.conf.d/50-device.conf containing Option "DRI" "false", and glmark2 score dropped to 49.
With DRI in use, sddm is slow to react when typing password when logging in, and the display behaves a bit erratically. Google just found "It's not SDDM fault as it's Qt5Gui which needs OpenGL 2+ features. Imho good solution would be if SDDM before starting sddm-greeter checked for OpenGL 2+ and if this is not met then export QT_XCB_FORCE_SOFTWARE_OPENGL=1 to use software rendering." (Tomasz Paweł Gajc )
Your inxi output shows OpenGL v: 4.5 but mine is only OpenGL v: 1.4. This is with DRI on:
On my systems the same thing happens with the on-board i915 (i915.ko module),
and with add-on Nvidia cards (nouveau.ko module),
and with add-on Radeon cards (radeon.ko module).
The only common factor is the use of lilo as boot manager which sets the framebuffer console.
The fix in all cases was to add video=1600x1200 to the append line in /etc/lilo.conf
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
