[oi-dev] HCL - Lenovo ThinkCentre Workstations

[Atiq Rahman]

> I'm having a separate issue with a NIC
How's the internal NIC doing? Is there any issue with that?

Since this is a desktop machine I am guessing it doesn't have wifi /
wireless lan.

> I'm not sure that I would expect a desktop environment to run on these
systems.
I am aware of that.

Other than DE/Graphics, everything else is cool?

>> ThinkStation P8         Ryzen Threadripper PRO 7000 WX-SeriesZen 4 (2024)
>> ThinkStation P620     Ryzen Threadripper PRO 5000/3000 WXZen 3/Zen 2

> Hopefully either of those would work too!  If not, I'm sure whatever
> is wrong can be fixed.
Good to know.

Thanks,

Atiq



On Sun, Sep 7, 2025 at 7:15 PM Joshua M. Clulow <josh at sysmgr.org> wrote:

> On Sun, 7 Sept 2025 at 17:58, Atiq Rahman <atiqcx at gmail.com> wrote:
> > Among below which will be good to run illumos OSs after PRs listed above
> are merged?
> >
> > ThinkCentre M75 Gen 5   Ryzen PRO 8000 SeriesZen 4 (2024)
>
> I believe this is roughly the same as the one I qualified when I was
> making the patches.
>
> I want to clarify, again: I am not using DRM/X11 on these systems for
> a graphical environment.  I do not expect that to work at present.
> Someone will need to work on the DRM port, and specifically on
> enabling the "amdgpu" DRM driver.  See below, from my earlier message:
>
> >> I'm not sure that I would expect a desktop environment to run on these
> >> systems.  Our DRM port is relatively ancient, and does not appear to
> >> include the "amdgpu" driver, which is what I would expect to attach to
> >> the onboard graphics device.  The port is here, if you're curious and
> >> would like to work on it:
> >>
> >>     https://github.com/illumos/gfx-drm
> >>
> >> For our purposes (custom software, not X11) the static framebuffer
> >> mapping left in place by the EFI firmware is sufficient, so I'm not
> >> expecting to do any DRM work at this time.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20250907/2c504163/attachment-0001.html>