had a 13700k build that started acting funny, and I dont have a ton of free time, so after spending 2 days trying to get proxmox to work, and then even just ubuntu to install without proxmox, and I gave up and bought a new computer *based on the new 256K intel CPU. Now, I have no internet because the new realtek ethernet device doesnt have support. When googling here, all I can find are threads about the similar,but different realtek 8125, and one thread for the 8126 where the last post is "I tried this, and it doesnt work". Any help? Or am I doomed to run ubuntu directly?
[SOLVED] Bought a new computer because other one was habing issues, now the computer is "too new" (Realtek 8126 isnt recognized and so I have no internet)
- Thread starter manguy
- Start date
since you have reinstalled I assume you are using proxmox kernel 6.8.12-10 (
If so you could try using the newer proxmox kernel 6.14.0-2 as it may already support the new Realtek chip
You can install it as follows
uname -r)?If so you could try using the newer proxmox kernel 6.14.0-2 as it may already support the new Realtek chip
You can install it as follows
apt install proxmox-kernel-6.14It finally worked after disabling secure boot (ip a wouldnt list the device until I did this)
I was about to post a thread about how this didn't work, turns out it's just the motherboard I was using had a buggy BIOS.
If anyone else encounters this issue and finds that disabling secure boot didn't work, if you are using the Z890I Nova motherboard (or perhaps any Aorus Z890 boards), try enabling secure boot -> set boot mode to custom -> set boot mode to default -> disable secure boot (also make sure you are on proxmox-kernel-6.14, as the thread already mentioned)
I do not know how or why this solved it when just disabling secure boot initially did not work, and yet it did.
I do recall a friend has similar issues with this generation of boards, Windows insisted secure boot was disabled (and so they couldn't run Valorant), that board had a similar set of steps to solve it, so maybe it's just a common issue.
If anyone else encounters this issue and finds that disabling secure boot didn't work, if you are using the Z890I Nova motherboard (or perhaps any Aorus Z890 boards), try enabling secure boot -> set boot mode to custom -> set boot mode to default -> disable secure boot (also make sure you are on proxmox-kernel-6.14, as the thread already mentioned)
I do not know how or why this solved it when just disabling secure boot initially did not work, and yet it did.
I do recall a friend has similar issues with this generation of boards, Windows insisted secure boot was disabled (and so they couldn't run Valorant), that board had a similar set of steps to solve it, so maybe it's just a common issue.