** Changed in: linux-oem-5.17 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950062
Title:
Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
I've requested it to stable for 5.15.y and 5.17.y. If accepted I
believe this should solve all the tasks on this bug report eventually on
a future stable update in Ubuntu too.
https://lore.kernel.org/stable/mn0pr12mb610150ac5f1e15d6a67ac352e2...@mn0pr12mb6101.namprd12.prod.outlook.com/T/#u
**
** Changed in: amd
Status: New => Triaged
** Changed in: amd
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950062
Title:
Unable to access CPU i2c interfaces
Now that the beta is out for Jammy, I installed it to a SSD and added
the PPA posted in #12 but I could not get the SMBus access to work. I
think this is because the one shipping with the beta is newer than the
one in the PPA.
--
You received this bug notification because you are a member of
> Is this Linux patch series back-ported to older kernels, like the 5.13
kernel that came with my Ubuntu 20.04 installation, or any LTS kernel?
I'm not fully familiar with the Linux kernel release behaviour.
The patches were accepted upstream for kernel 5.18. Right now it's not been
added to
Is this Linux patch series back-ported to older kernels, like the 5.13
kernel that came with my Ubuntu 20.04 installation, or any LTS kernel?
I'm not fully familiar with the Linux kernel release behaviour.
I'm asking this because I'm looking for the best way to apply this patch
on an older kernel
I just verified the patch in Ubuntu 20.04 under kernel version 5.13. All
of my components now show up in open RGB. I compiled the kernel myself
using the steps provided in
https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/1984#note_872699651.
As mentioned above, I was not able to verify the PPA
I am now building the kernel from source using the following steps
https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/1984#note_872699651
to verify whether the patch solves my problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ah yea, that's a type. I used `sudo reboot now`. For me, after those
steps the ram still didn't show up, so there might be another problem on
my system. I also tried manually building the kernel with the patch, but
I run into some unrelated issues. I think I will wait till the patch
hits the
All steps look right. `sudo apt reboot` won't work though, its either
`reboot` or `systemctl reboot`.
After that you need to pick the correct kernel. You can do that during
boot time, on Ubuntu its grub so maybe try `sudo update-grub`(I think,
if not try grub-update). Then just pick the correct
I tried the PPA from @vicamo on Ubuntu 20.04 with kernel 5.14, but It
does not seem to work for me. I installed the PPA using the following
commands:
sudo add-apt-repository ppa:vicamo/ppa-1950062
sudo update`
sudo install linux-oem-5.14-headers-5.14.0-2023
linux-oem-5.14-tools-5.14.0-2023
I am affected by this issue on my Ubuntu 20.04 system that is running
kernel a 5.13 kernel. I have a ASUS rog stix b550-E gaming motherboard,
an AMD 5600G CPU and use crucial ballistix ram.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Didn't expect to see this fixed that soon. Amazing to see that, very
happy AMD getting onboard. Vicamo can confirm it works on Focal Fossa
with AMD 5700G. No more i2c errors and OpenRGB program just works now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Do you have a PPA for impish?
> E: The repository 'http://ppa.launchpad.net/vicamo/ppa-1950062/ubuntu
impish Release' does not have a Release file.
From memory, I could not boot the OS with Focal and needed to use
hirsute after I upgraded the CPU.
I will try the latest Jammy live CD shortly.
Jammy appears to have failed to build. Trying it on oem-5.14 on a
machine with the failing symptom it seems to fail on the machine I
tested unfortunately.
When loading the i2c-piix4 module I see the following:
[ 97.103748] ACPI Warning: SystemIO range
0x0B00-0x0B08
I created a PPA with prebuilt kernels for Jammy & Focal oem in
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1950062. Could you
help verify them?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: Confirmed
** Also affects: linux-oem-5.14 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu
The patch series was just accepted into the maintainer's i2c-next tree.
It should be in for 5.18.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950062
Title:
Unable to access CPU i2c interfaces
I'm having the same issue. ASUS Tuf B550-Plus motherboard, with an AMD-
Ryzen-5600G.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950062
Title:
Unable to access CPU i2c interfaces with AMD
> [0.699857] piix4_smbus :00:14.0: SMBus Host Controller at 0xff00,
> revision 15
> [0.699861] piix4_smbus :00:14.0: Using register 0x02 for SMBus port
> selection
> [0.700103] piix4_smbus :00:14.0: Auxiliary SMBus Host Controller at
> 0xff20
This bug will be fixed by
To those who are seeing this I suggest selecting the option at the top
left that says "This affects me too." That will help accurately track
how many users are affected by this and hopefully get more attention on
this issue.
--
You received this bug notification because you are a member of
I have the same problem with 5600G
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950062
Title:
Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
To manage notifications about this bug
Have exactly the same issue.CPU-Ryzen: 5700G Motherboard: Asus X470-i
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950062
Title:
Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
To
I am also having the same issue with a Ryzen 7 5700G
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950062
Title:
Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
To manage
** Also affects: archlinux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950062
Title:
Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
To
I have had another user run into the issue in the OpenRGB bug tracker:
https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/1984#note_749829340
** Bug watch added: gitlab.com/CalcProgrammer1/OpenRGB/-/issues #1984
https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/1984
--
You received this
Results of i2cdetect showing i2c-0 to i2c-2 are the pixx4 interfaces
from the CPU:
i2cdetect -l
i2c-3 i2c AMDGPU DM i2c hw bus 0 I2C adapter
i2c-1 smbus SMBus PIIX4 adapter port 2 at ff00 SMBus adapter
i2c-6 i2c AMDGPU DM i2c hw bus 3
28 matches
Mail list logo
