From: Wolfram Sang <wsa@kernel.org>
To: "Jean-François Roy" <jf@devklog.net>, "Jean Delvare" <jdelvare@suse.de>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [ee1004] Failed to select page 0 - G.Skill Trident Z5 NEO DDR5, ASUS X670E board - 6.2.11-arch1-1
Date: Fri, 21 Apr 2023 06:35:34 +0200 [thread overview]
Message-ID: <ZEISllc9y2bot/ZT@ninjato> (raw)
In-Reply-To: <CAE8T=_HGM+gKQguOasGSKi5YXh91S62QYA2=MC45CLJPYxrVAg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2246 bytes --]
CCing Jean Delvare...
On Thu, Apr 20, 2023 at 03:51:38PM -0700, Jean-François Roy wrote:
> Hello,
>
> On a ASUS X670E (AMD AM5 platform) board, I am unable to read the
> eeprom for my memory (through decode-dimms). The SMBus is driven by
> piix4_smbus.
>
> i2cdetect -l lists the following:
>
> i2c-0 i2c Synopsys DesignWare I2C adapter I2C adapter
> i2c-1 i2c NVIDIA i2c adapter 2 at 1:00.0 I2C adapter
> i2c-2 i2c NVIDIA i2c adapter 3 at 1:00.0 I2C adapter
> i2c-3 i2c NVIDIA i2c adapter 4 at 1:00.0 I2C adapter
> i2c-4 i2c NVIDIA i2c adapter 5 at 1:00.0 I2C adapter
> i2c-5 i2c NVIDIA i2c adapter 6 at 1:00.0 I2C adapter
> i2c-6 smbus SMBus PIIX4 adapter port 0 at 0b00 SMBus adapter
> i2c-7 smbus SMBus PIIX4 adapter port 2 at 0b00 SMBus adapter
> i2c-8 smbus SMBus PIIX4 adapter port 1 at 0b20 SMBus adapter
>
> Looking at i2c-6:
>
> i2cdetect -y 6 0x50 0x70
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00:
> 10:
> 20:
> 30:
> 40:
> 50: -- 51 -- 53 -- -- -- -- -- -- -- -- -- -- -- --
> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 70: --
>
> I think those are the memory eeproms. If I bind them to ee1004 as so:
>
> echo ee1004 0x51 >/sys/bus/i2c/devices/i2c-6/new_device
> echo ee1004 0x53 >/sys/bus/i2c/devices/i2c-6/new_device
>
> The kernel prints:
>
> [ 1642.373579] ee1004 6-0051: 512 byte EE1004-compliant SPD EEPROM, read-only
> [ 1642.373588] i2c i2c-6: new_device: Instantiated device ee1004 at 0x51
> [ 1645.328289] ee1004 6-0053: 512 byte EE1004-compliant SPD EEPROM, read-only
> [ 1645.328299] i2c i2c-6: new_device: Instantiated device ee1004 at 0x53
>
> But then when I use decode-dimms, the kernel is unable to select page 0:
>
> [ 1697.112564] ee1004 6-0051: Failed to select page 0 (-6)
> [ 1702.581605] ee1004 6-0051: Failed to select page 0 (-6)
>
> I tried looking for a SPD write enable/disable option in the system
> firmware but didn't see any (I am trying to confirm if that feature
> exists or not).
>
> All this on 6.2.11-arch1-1.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-04-21 4:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 22:51 [ee1004] Failed to select page 0 - G.Skill Trident Z5 NEO DDR5, ASUS X670E board - 6.2.11-arch1-1 Jean-François Roy
2023-04-21 4:35 ` Wolfram Sang [this message]
2023-04-29 15:15 ` Jean Delvare
2023-04-29 16:06 ` Jean Delvare
2023-05-01 16:42 ` Jean-François Roy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZEISllc9y2bot/ZT@ninjato \
--to=wsa@kernel.org \
--cc=jdelvare@suse.de \
--cc=jf@devklog.net \
--cc=linux-i2c@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox