Code: Select all
sp5100_tco: I/O address 0x0cd6 already in use
Code: Select all
sp5100_tco: I/O address 0x0cd6 already in use
Motherboard: MSI X370 Gaming Pro Carbonbw123 wrote:There could be several reasons for the hang, if you post more info about your hardware it will help eliminate some of them.
http://forums.debian.net/viewtopic.php?f=30&t=47078
http://forums.debian.net/viewtopic.php?f=30&t=10653
I upgraded to the newest BIOS - which is 7A32v19 as of current - then tried messing around with c-state and nothing changed.bw123 wrote:Did you try any suggestions after websearch for 'debian AMD Ryzen 7' ? I saw a couple posts about c-state setting and/or updating the bios.
Single user mode should work. I don't use encryption, it could be an issue there, or maybe it's video related. I think the installer still uses vga=789, what if you add that to the boot line for recovery mode, where it says 'single' that's real disappointing, sounds like a heck of a setup.GarethH wrote: In recovery mode it just hangs shortly after unencrypting, during which it appears to be loading Linux modules.
It hangs before I can even get into the recovery menu. Tried adding 'vga=789' to 'Debian GNU/Linux, with Linux 4.9.0-4-amd64 (recovery mode)' before 'load_video' and nothing changed.bw123 wrote:Single user mode should work. I don't use encryption, it could be an issue there, or maybe it's video related. I think the installer still uses vga=789, what if you add that to the boot line for recovery mode, where it says 'single' that's real disappointing, sounds like a heck of a setup.
and> On the AMD Turion N40L and other related SoCs, the i2c-piix4 driver
> now claims the 0xcd6 ioport, preventing the sp5100_tco watchdog
> driver from loading:
Here is the search I did: link> Perhaps a fix is to switch both drivers from static to dynamic
> allocation of the IO ports in question, since the watchdog driver
> only accesses the port during initialisation (with backoff/retry
> maybe to avoid races?).