Tuesday, July 09, 2024

Re: "intel(0): switch to mode 640x400" on Thinkpad T410

On Tue, 9 Jul 2024 21:24:01 +1000 Jonathan Gray wrote:
> On Tue, Jul 09, 2024 at 10:02:40AM -0000, Stuart Henderson wrote:
> > On 2024-07-08, Jan Stary <hans@stare.cz> wrote:
> > > This is current/amd64 on a Thinkpad T410 (full dmesg below).
> > > Strangely, upon booting, xenodm sets the resolution to 640x480:
> > >
> > > [ 974.100] (II) intel(0): Modeline "1440x900"x0.0 96.10 1440 1488 1552 1728 900 903 909 926 -hsync -vsync (55.6 kHz eP)
> > > [ 974.100] (II) intel(0): Modeline "1440x900"x0.0 80.30 1440 1488 1552 1728 900 903 909 926 -hsync -vsync (46.5 kHz e)
> > > [ 994.984] (II) intel(0): switch to mode 640x400@60.0 on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
> >
> > shouldn't that be using modesetting rather than intel? or is the machine too old?
>
> > > inteldrm0: msi, IRONLAKE, gen 5
>
> xserver/hw/xfree86/common/xf86pciBus.c
>
> ----------------------------
> revision 1.14
> date: 2017/09/25 15:05:57; author: matthieu; state: Exp; lines: +2 -0; commitid: wvjaQqtz2qvU9jZw;
> Force Intel Ironlake chipsets to use the xf86-video-intel driver.
> stsp@ reported that modesetting(4) has been reported unreliable
> on his laptop, while intel(4) works.
>
> XXXX to be removed after 6.2 to figure out and fix the issue.
>
> ok kettenis@, also discussed briefly with deraadt@ during EuroBSDCon.
> ----------------------------
>
> the intel driver requires pci access so won't work with
> startx as we stopped installing Xorg setuid
>

I remember many years ago modesetting wasn't reliable in this machine.
I also had issues with intel SNA acceleration (I had to use UXA).
Currently seems to work fine. But, I can't tell for sure, I'm not using
this machine every day.

No comments:

Post a Comment