Date: Sat, 22 Oct 2022 19:11:08 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 230807] if_alc(4): Driver not working for Killer Networking E2200 Message-ID: <bug-230807-7501-ITN31Ysei9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230807-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-230807-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230807 --- Comment #17 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Cheburashka from comment #16) I've seen similar OS context-switching behavior with the ThreadRipper 1950X X399 AORUS gaming 7 I use that has an E2500. Complete power off-then-on is the only solution that I've found. This is not new. It has been a long time since I've booted Linux on this box. So this is more of a note about historical examples. (I still boot both FreeBSD and Windows 10 Pro.) The major point being that E2500 and E2200 both have the type of issue of some form of incomplete reset allowing prior Linux configuration to mess up E2?00 things for FreeBSD. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230807-7501-ITN31Ysei9>