Re: Bug#1110749: ee1004: DDR4 SPD cannot be read, decode-dimms fails, “Failed to select page 0 (-6)”

["Uwe Kleine-König" <ukleinek@debian.org>]

[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]

On Fri, Sep 11, 2026 at 10:33:07PM +0200, Al Ma wrote:
> Awesome!
> 
> Below, I'll comment on whatever I can meaningfully comment.
> 
> > * Short term, you want to blacklist the ee1004 driver on your system.
> >    It is not a good idea to load a driver which binds to the wrong
> >    device.
> 
> Here we go, following https://wiki.debian.org/KernelModuleBlacklisting:
> 
> $ echo "blacklist ee1004" | sudo tee /etc/modprobe.d/ee1004.conf
> blacklist ee1004
> $ sudo depmod -ae
> depmod: WARNING: -e needs -E or -F
> $ sudo update-initramfs -u
> update-initramfs: Generating /boot/initrd.img-6.12.107+deb13-amd64
> 
> Can the above warning be ignored?

I think yes. AFAIK that depmod step isn't needed and the wiki should be
fixed.

Does that help?

> > * Still mid term, we probably want to blacklist SPD probing explicitly
> >    for your motherboard (we'll need to know the contents of
> >    /sys/devices/virtual/dmi/id/board_vendor and
> >    /sys/devices/virtual/dmi/id/board_name on your system). Maybe this
> >    can be implemented as an empty entry in mux_dmi_table (as in, we know
> >    the board requires multiplexing, but we don't know yet to implement
> >    it on that board).
> 
> Here we go:
> 
> $ cat /sys/devices/virtual/dmi/id/board_vendor
> ASUSTeK COMPUTER INC.
> $ cat /sys/devices/virtual/dmi/id/board_name
> WS C422 PRO_SE

If the above is confirmed to help, I think we have everything to
implement a quirk with the same effect as blacklisting manually.

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]