| === shokohsc9 is now known as shokohsc | ||
| === chris14_ is now known as chris14 | ||
| === shokohsc9 is now known as shokohsc | ||
| === elastic_dog is now known as Guest6863 | ||
| === JanC_ is now known as JanC | ||
| === JanC is now known as Guest8348 | ||
| === JanC_ is now known as JanC | ||
| === JanC is now known as Guest2977 | ||
| === JanC_ is now known as JanC | ||
| === elastic_dog is now known as Guest2360 | ||
| === JanC_ is now known as JanC | ||
| === shokohsc5 is now known as shokohsc | ||
| === JanC_ is now known as JanC | ||
| jafa | Hi guys, I am seeing a problem where the onboard NIC works perfectly for installing Ubuntu Server 22.04 LTS, works perfectly on boot, but after a few days it reports no link (and no lights). Reinstalling the OS recovers it again and today I discovered manually running dhclient wakes it up and it starts working | 18:38 |
|---|---|---|
| jafa | when I run dhclient dmesg logs "RTL8226B_RTL8221B 2.5Gbps PHY r8169-0-600:00: attached PHY driver (mii_bus:phy_addr=r8169-0-600:00, irq=MAC)" then logs link up | 18:39 |
| jafa | also noticed that Ubuntu isn't doing the usual waiting-for-dhcp delay during bootup | 18:39 |
| jafa | running netplan commands does not make a difference, only running dhclient does | 18:40 |
| jafa | problem may related to adding/removing nvme drives (non OS drive) | 18:41 |
| jafa | huh - I just added the macaddress to the netplan yaml and it came up on boot | 18:47 |
| === tomreyn_ is now known as tomreyn | ||
| === JanC_ is now known as JanC | ||
| === JanC_ is now known as JanC | ||
| NekitaNet | Hi all; Installing ubuntu server 22.04 and am wondering; Why is the AMD64 microcode package available for remove after installing the linux-lowlatency and removing the linux-generic kernel set? | 23:18 |
| === JanC is now known as Guest9625 | ||
| === JanC_ is now known as JanC | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!