Solved drm User-defined mode not supported

B

bumpyhead

Hi folks,

I have freebsd 14.2 installed on intel alderlake i5-12400 (integrated graphics). Recently I am keeping getting the below messages in dmesg

Code: 
drmn0: [drm] User-defined mode not supported: "1024x768": 75 78750 1024 1040 1136 1312 768 769 772 800 0x60 0x5

I have the below line in my /boot/loader.conf
Code: 
kern.vt.fb.default_mode="1024x768"
I have the below line in my /etc/rc.conf
Code: 
kld_list="i915kms cuse"
I have the below package installed from pkg
Code: 
# pkg info | grep drm
drm-61-kmod-6.1.92.1402000_3   DRM drivers modules
Code: 
# dmesg | grep drmn0 
drmn0: <drmn> on vgapci0
vgapci0: child drmn0 requested pci_enable_io
vgapci0: child drmn0 requested pci_enable_io
lkpi_iic0: <LinuxKPI I2C> on drmn0
lkpi_iic1: <LinuxKPI I2C> on drmn0
lkpi_iic2: <LinuxKPI I2C> on drmn0
lkpi_iic3: <LinuxKPI I2C> on drmn0
lkpi_iic4: <LinuxKPI I2C> on drmn0
lkpi_iic5: <LinuxKPI I2C> on drmn0
lkpi_iic6: <LinuxKPI I2C> on drmn0
lkpi_iic7: <LinuxKPI I2C> on drmn0
lkpi_iic8: <LinuxKPI I2C> on drmn0
drmn0: successfully loaded firmware image 'i915/adls_dmc_ver2_01.bin'
drmn0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1)
[drm] Initialized i915 1.6.0 20201103 for drmn0 on minor 0
name=drmn0 id=i915drmfb flags=0x0 stride=4096
drmn0: [drm] User-defined mode not supported: "1024x768": 75 78750 1024 1040 1136 1312 768 769 772 800 0x60 0x5
Is there an easy fix to get rid of the kernel complain? Thanks very much!
 
Last edited by a moderator:
The problem has been fixed by modifying "1024x768" to a supported mode (in my case "1920x1080"):

Code: 
# cat /boot/loader.conf
kern.vt.fb.default_mode="1920x1080"
 
Last edited by a moderator:
bumpyhead said:
The problem has been fixed by modifying "1024x768" to a supported mode (in my case "1920x1080"):

Code: 
# cat /boot/loader.conf
kern.vt.fb.default_mode="1920x1080"
Click to expand...
This is too good to be true, unfortunately.

After opening the machine for 16 hours, I got the same complaints:
Code: 
drmn0: [drm] User-defined mode not supported: "1920x1080": 60 148500 1920 2008 2052 2200 1080 1084 1089 1125 0x60 0xa
drmn0: [drm] User-defined mode not supported: "1920x1080": 60 148500 1920 2008 2052 2200 1080 1084 1089 1125 0x60 0x5
 
Last edited by a moderator:
I upgraded from FreeBSD 14.2 to 14.3, which required upgrading my kernel driver to graphics/drm-61-kmod and now I have the same problem. First, I had the error from another resolution. Then, when I changed it to your resolution, I got the same error. The terminal console still worked with the changed resolution.

Before trying this, I also removed the resolution setting for XDM in /usr/local/etc/X11/xdm/Xsetup_0, which this isn't why.

Xrandr seems to need X11 to show supported resolutions. I tried
sysutils/dmidecode,
sysutils/sysinfo and pciconf.

How do I find the supported resolutions? In this case, two monitors are being used.

Update:
I installed the xf86 video card drivers for X11, and removed the line from /boot/loader.conf, and this worked. Earlier when I reported and edited, that it wasn't working, I forgot which graphics card I had, as I was used to using AMD, and mine was Intel. It was after loading the video driver that it worked. VESA must have been what didn't support those modes.


bumpyhead said:
This is too good to be true, unfortunately.

After opening the machine for 16 hours, I got the same complaints:
Click to expand...
Probably because the graphics driver for X11 got removed since that time. If this works for you, you can mark it solved.
 
sidetone said:
I installed the xf86 video card drivers for X11, and removed the line from /boot/loader.conf, and this worked. Earlier when I reported and edited, that it wasn't working, I forgot which graphics card I had, as I was used to using AMD, and mine was Intel. It was after loading the video driver that it worked. VESA must have been what didn't support those modes.



Probably because the graphics driver for X11 got removed since that time. If this works for you, you can mark it solved.
Click to expand...
The problem is independent of X (I am using hyprland). I checked today on 14.3 with GENERIC kernel, and the problem still persists.
 
Back to this. I'm having error messages again, but mine is working. You said it's independent of X, but you're using hyprland. Does the error message still pop up when you turn hyprland off? Does hyprland work, but with that error message? Does your console work with this setting?

In my case, when I turned xdm and the Xserver off, that error message went away. I started
Thread setting-console-resolution-gives-error-message-of-mode-not-supported.98608 which is similar and also shows what would be default values for resolution.
 
sidetone said:
Back to this. I'm having error messages again, but mine is working. You said it's independent of X, but you're using hyprland. Does the error message still pop up when you turn hyprland off? Does hyprland work, but with that error message? Does your console work with this setting?

In my case, when I turned xdm and the Xserver off, that error message went away. I started
Thread setting-console-resolution-gives-error-message-of-mode-not-supported.98608 which is similar and also shows what would be default values for resolution.
Click to expand...
Hyrpland works, console works, but the error message shows if I open the BSD box for a few days (while using hyprland).

I have changed my /boot/loader.conf with the below line
Code: 
kern.vt.fb.default_mode="1920x1080x32"
and will report back in a few days whether the error messages have disappeared.
 
Based on your suggestion, I thought it had worked. I found a common resolution for both monitors by using xrandr, and I added the refresh rate that matched what was available of both monitors. In my case, there was one resolution that fit for /boot/loader.conf:
Code: 
kern.vt.fb.default_mode="1024x768x60"

It turns out, that this didn't give the result I wanted, as this whole line was nulled. The error message went away, but the resolution didn't correct.

It might need another loader.conf setting. I'm uncertain if that monitor name is available from dmesg.
 
You must log in or register to reply here.
Back
Top