Fwd: X11 claims my chipset is unknown. Who can fix this?
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 09 Feb 2025 21:34:24 UTC
Here's the off-forum exchange for context...
-------- Forwarded Message --------
Subject: Re: X11 claims my chipset is unknown. Who can fix this?
Date: Sun, 9 Feb 2025 10:55:17 -0500
From: FreeBSD Louisville <FreeBSDLouisville@gmail.com>
To: Paul Procacci <pprocacci@gmail.com>
On 2/9/25 04:17, Paul Procacci wrote:
> On Sun, Feb 9, 2025 at 2:35 AM FreeBSD Louisville
> <freebsdlouisville@gmail.com> wrote:
>>
>> X11 claims my chipset is unknown. Who can fix this?
>>
>> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>> [ 86.903] (WW) Falling back to old probe method for modesetting
>> [ 86.903] (WW) Falling back to old probe method for scfb
>> [ 86.903] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card
>> support
>> [ 86.903] (WW) intel(0): Unknown chipset
>> [ 86.920] (WW) intel(0): cannot enable DRI2 whilst forcing software
>> fallbacks
>> [ 86.921] (WW) intel(0): Disabling Xv because no adaptors could be
>> initialized.
>> [ 86.953] (II) Initializing extension MIT-SCREEN-SAVER
>> [ 87.094] (EE) intel(0): intel_uxa_set_pixmap_bo: size of buffer
>> object does not match constraints: size=41943040, must be greater than
>> 36864000, but less than 4194304
>> [ 87.094] (EE)
>> [ 87.094] (EE) failed to create screen resources(EE)
>> [ 87.094] (EE)
>> [ 87.094] (EE) Please also check the log file at
>> "/var/log/Xorg.0.log" for additional information.
>> [ 87.094] (EE)
>> [ 87.101] (EE) Server terminated with error (1). Closing log file.
>>
>> vgapci0@pci0:0:2:0: class=0x030000 rev=0x0c hdr=0x00 vendor=0x8086
>> device=0x46a6 subvendor=0x1028 subdevice=0x0af3
>> vendor = 'Intel Corporation'
>> device = 'Alder Lake-P GT2 [Iris Xe Graphics]'
>> class = display
>> subclass = VGA
>>
>>
>
> ChatGPT can. What have you tried that it suggested thus far?
>
> ~Paul
>
Ok, I installed ChatGPT app and asked it:
X11 windowing system on FreeBSD doesn't recognize my Alder Lake-P GT2
chipset.
Here's the entire transcript:
X11 windowing system on FreeBSD doesn't recognize my Alder Lake-P GT2
chipset.
ChatGPT said:
It looks like your Intel Alder Lake-P GT2 (integrated GPU) is not being
recognized by the X11 windowing system on FreeBSD. Here are some
troubleshooting steps and possible solutions:
1. Check FreeBSD Version
Ensure you are running FreeBSD 13.1 or later, as Intel GPU support is
improving in newer versions.
sh
Copy code
freebsd-version -kru
If you are on an older version, consider upgrading.
2. Install the Latest DRM-KMOD Drivers
FreeBSD uses drm-kmod to support Intel and AMD GPUs. Install it using:
sh
Copy code
pkg install drm-510-kmod
For FreeBSD 14 and above, you might need drm-54-kmod instead.
3. Enable Kernel Modules
Edit /etc/rc.conf and add:
sh
Copy code
kld_list="i915kms"
Or, manually load the module:
sh
Copy code
kldload i915kms
For newer GPUs (like Alder Lake), you might need kms from
drm-devel-kmod. Install it with:
sh
Copy code
pkg install drm-devel-kmod
4. Ensure Your User is in the Video Group
Check if your user belongs to the video group:
sh
Copy code
pw groupmod video -m yourusername
5. Check Xorg Logs
If Xorg is failing to start, check the logs:
sh
Copy code
cat /var/log/Xorg.0.log | grep EE
If you see errors related to "no screens found" or "device not
detected," your GPU might not be fully supported yet.
6. Use a Custom xorg.conf (if needed)
Try creating /etc/X11/xorg.conf.d/20-intel.conf with:
sh
Copy code
Section "Device"
Identifier "Intel Graphics"X11 windowing system on FreeBSD doesn't
recognize my Alder Lake-P GT2 chipset.
ChatGPT said:
It looks like your Intel Alder Lake-P GT2 (integrated GPU) is not being
recognized by the X11 windowing system on FreeBSD. Here are some
troubleshooting steps and possible solutions:
1. Check FreeBSD Version
Ensure you are running FreeBSD 13.1 or later, as Intel GPU support is
improving in newer versions.
sh
Copy code
freebsd-version -kru
If you are on an older version, consider upgrading.
2. Install the Latest DRM-KMOD Drivers
FreeBSD uses drm-kmod to support Intel and AMD GPUs. Install it using:
sh
Copy code
pkg install drm-510-kmod
For FreeBSD 14 and above, you might need drm-54-kmod instead.
3. Enable Kernel Modules
Edit /etc/rc.conf and add:
sh
Copy code
kld_list="i915kms"
Or, manually load the module:
sh
Copy code
kldload i915kms
For newer GPUs (like Alder Lake), you might need kms from
drm-devel-kmod. Install it with:
sh
Copy code
pkg install drm-devel-kmod
4. Ensure Your User is in the Video Group
Check if your user belongs to the video group:
sh
Copy code
pw groupmod video -m yourusername
5. Check Xorg Logs
If Xorg is failing to start, check the logs:
sh
Copy code
cat /var/log/Xorg.0.log | grep EE
If you see errors related to "no screens found" or "device not
detected," your GPU might not be fully supported yet.
6. Use a Custom xorg.conf (if needed)
Try creating /etc/X11/xorg.conf.d/20-intel.conf with:
sh
Copy code
Section "Device"
Identifier "Intel Graphics"
Driver "modesetting"
Option "AccelMethod" "glamor"
EndSection
Alternatively, you can try Driver "intel" but modesetting is preferred
for newer GPUs.
7. Check for iGPU Support
Alder Lake's GPU support in FreeBSD is still catching up. If
drm-devel-kmod doesn’t work, you might need to:
Wait for an updated driver
Run FreeBSD-CURRENT for newer kernel updates
Consider using a discrete GPU
Let me know what errors you are getting, and I can help troubleshoot
further!
Reason
ChatGPT can make mistakes. Check important info.
Driver "modesetting"
Option "AccelMethod" "glamor"
EndSection
Alternatively, you can try Driver "intel" but modesetting is preferred
for newer GPUs.
7. Check for iGPU Support
Alder Lake's GPU support in FreeBSD is still catching up. If
drm-devel-kmod doesn’t work, you might need to:
Wait for an updated driver
Run FreeBSD-CURRENT for newer kernel updates
Consider using a discrete GPU
Let me know what errors you are getting, and I can help troubleshoot
further!
Reason
ChatGPT can make mistakes. Check important info.
But there isn't a drm-devel-kmod port.