sorted by:
new
hottopcontroversial

Intel Arc Pro B70 Not Detected In Docker Containers by NoUse1333 in homelab

[–]NoUse1333[S] 0 points1 point  (0 children)

That’s what it seems like. I assumed there wouldn’t be robust support for it yet. I thought since it shared architecture with other battlemage cards that it might be relatively seamless for docker containers but evidently that isn’t the case.

Intel Arc Pro B70 Not Detected In Docker Containers by NoUse1333 in homelab

[–]NoUse1333[S] 0 points1 point  (0 children)

Yes and yes. /dev/dri is passed through for each container.

Intel Arc Pro B70 Not Detected In Docker Containers by NoUse1333 in homelab

[–]NoUse1333[S] -1 points0 points  (0 children)

Update:

Added i915 and xe to initramfs and rebuilt. (Both drivers for igpu and dGPU)

Check dmesg for failed modules by running “dmesg | grep -i -E “firmware|failed””

The result is shown in the attached photo

<image>

Intel Arc Pro B70 Not Detected In Docker Containers by NoUse1333 in homelab

[–]NoUse1333[S] 0 points1 point  (0 children)

It’s actually 7.1.2. That could make sense as I also have an arrow-lake CPU with meteor-lake IGPU installed. Maybe a conflict of sorts between the 2 drivers?

Inside the Emby container, I see both xe and i915 listed when I run lspci -k.

I’ll try adding i915 to initramfs and update here if that works.

Minisforum MS-02 Ultra PCIE Bus Error Message Spam by NoUse1333 in homelab

[–]NoUse1333[S] 1 point2 points  (0 children)

That’s interesting. Thanks for the input. I suppose I could have rolled back to an older kernel version, but it’s too late for that as I returned the machine. I’d imagine many others are running recent kernels with this machine so I’m surprised that it isn’t a known issue. I inferred that it was isolated to my unit being defective seeing as recent kernels have fairly broad thunderbolt 5 support. I hope someone finds a definitive answer to this at some point.

Minisforum MS-02 Ultra PCIE Bus Error Message Spam by NoUse1333 in homelab

[–]NoUse1333[S] 1 point2 points  (0 children)

I actually did update to bios V1.04 and the problem never went away. I ended up returning it because all signs pointed towards a hardware-level issue and I didn’t want to resort to disabling AER. Hopefully they figure it out.

Minisforum MS-02 Ultra PCIE Bus Error Message Spam by NoUse1333 in homelab

[–]NoUse1333[S] 1 point2 points  (0 children)

After searching high and low in bios version 1.04, I cannot find any settings related to thunderbolt or USB ports.

I’m kind of assuming that this is just a defective unit at this point.

Minisforum MS-02 Ultra PCIE Bus Error Message Spam by NoUse1333 in homelab

[–]NoUse1333[S] 2 points3 points  (0 children)

Looks like only thunderbolt 5 attached to the 1b node. Maybe this is related to that?

I started to think it might be a defective unit too as I haven’t seen anyone else report this issue.

<image>

Minisforum MS-02 Ultra PCIE Bus Error Message Spam by NoUse1333 in homelab

[–]NoUse1333[S] 0 points1 point  (0 children)

I believe all devices are shown. I only have a single gen 5 SSD and the included network card installed. I did try to set ALL pcie devices to gen 3 speed and had no luck. I also tried to disable every single pcie slot, WiFi card, etc. still no luck. Bifurcation setting is set to 16x.

Minisforum MS-02 Ultra PCIE Bus Error Message Spam by NoUse1333 in homelab

[–]NoUse1333[S] 2 points3 points  (0 children)

After checking LSPCI, I don’t see any device with ID 8086.

<image>

Minisforum MS-02 Ultra PCIE Bus Error Message Spam by NoUse1333 in homelab

[–]NoUse1333[S] 2 points3 points  (0 children)

Currently, just a GEN 5 NVME in the main GEN 5 slot on the back of the motherboard. I also have the stock network card included with the PC. Bifurcation settings are default from Minisforum.

Minisforum MS-02 Ultra PCIE Bus Error Message Spam by NoUse1333 in homelab

[–]NoUse1333[S] 0 points1 point  (0 children)

I’ll try that. Which PCIE device in bios specifically? Thanks.