Re: minidisplay-port on T440s working?

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

Many thanks for the suggestion; I will try them, at least to get some
experience with xrandr, which I hadn't used in anger before.

As far as the microcode is concerned, I tried a few hours ago to use
the files which get delivered by 'apt install firmware-misc-nonfree'
on debian-stretch, but the interesting ones were exactly the same as
those I got from the git repository. Perhaps the loading process under
NetBSD itself needs some work; I had a look

As far as the dual card setup is concerned, besides NetBSD and Windows
10 I occasionaly run on the same laptop OpenSUSE tumbleweed, RedHat
7.6 and a few Ubuntu flavours; the mess is more or less the same
everywhere (except Windows 10, in all honesty), and perhaps on the
Ubuntu setup. As you mentioned above regarding the lack of NVidia
hardware recognition, I am also happy that now at least the nouveau
driver doesn't cause a panic any more; looking at some earlier mail
conversations in this space it seems a new version of the dri2 stuff
needs to be ported in order to get the latest nouveau driver to work
under NetBSD, but at least now the system is stable.

On Fri, 25 Jan 2019 at 15:57, Robert Elz <kre%munnari.oz.au@localhost> wrote:
>
>     Date:        Fri, 25 Jan 2019 14:43:59 +0000
>     From:        Chavdar Ivanov <ci4ic4%gmail.com@localhost>
>     Message-ID:  <f45fea4e-0542-6680-e841-4cfab5fe370b%gmail.com@localhost>
>
>   | rather than a mirror, but as I do not intend to actually use it, I
>   | didn't bother to find out how for now, probably another 'Xorg
>   | -configure' with the second monitor and then some tweak).
>
> On another system where I have two more or less permanently
> connected monitors, I have this in xorg.conf
>
> Section "ServerLayout"
>         Identifier     "X.org Configured"
>         Screen      0  "Screen0" 0 0
>         Screen      1  "Screen1" RightOf "Screen0"
>         InputDevice    "Mouse0" "CorePointer"
>         InputDevice    "Keyboard0" "CoreKeyboard"
> EndSection
>
> (along with definitions for Screen0 & Screen1)   I have no idea
> if Xorg --configure can make anything like that, I did it by hand.
>
> But on my laptop, I just use xrandr to move things around.
> Provided the virtual desktop is big enough (mine says:
>
>    Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
>
> and 32Kx32K is plenty, you could have 8 4K monitors side by side with
> that) all it should take is a command like
>
>         xrandr --output HDMI1 --right-of eDP1
>
> though there might need to be additional args to get things "just right",
> and perhaps to pick a resolution, etc.   xrandr has lots of options...
>
> You can also do --left-of --above or --below, and --rotate, --reflect
> and much much more.
>
> The "Screen 0: ..." "current" values will just get bigger as there are
> real screens to cause it.   Note that it is always a rectangle though,
> if the monitors have different resolutions, you tend to end with areas
> of "dead" space, which looks to applications (like window managers)
> like usable screen real estate, but for which there is no monitor
> to display the pixels.   That's unavoidable I think (though playing
> with resolutions and scaling might sometimes help).
>
>   | Where should I get the microcode from?
>
> I got the files I have from some intel site I believe, just from a google
> search for i915 firmware, or the expected filenames, or something
> (it was months ago, when Kaby Lake support got added to NetBSD)
> and then some poking around.
>
> Most of what I have there is irrelevant, I am confident of that,
> I added them just because they were available, and "just in case".
> Two files should be all that is needed.
>
>   | https://github.com/wkennington/linux-firmware/tree/master/i915, wasn't
>   | sure if there is other canonical place to get them from (apparently they
>   | are not in src/sys/dev/microcode).
>
> No, they were not there.
>
> kre
>


-- 
----