Yea.. so originally the idea I suggested earlier was actually to disable it at boot so you could boot into the system and then be able to either load it manually or do something else.. but since the module will auto reload (possibly), you'll need to actually boot into a live cd and manually edit the /etc/rc.conf file as recommended previoualy to stop it from auto loading. Good catch Tomoaki!
Sent from ProtonMail mobile -------- Original Message -------- On May 23, 2022, 17:18, Tomoaki AOKI wrote: > On Tue, 24 May 2022 01:31:31 +0900 (JST) > Yasuhiro Kimura <y...@freebsd.org> wrote: > >> From: Jonathan Vasquez <j...@xyinn.org> >> Subject: Re: Boot hangs up with Alderlake's intel GbE NIC >> Date: Mon, 23 May 2022 11:41:48 +0000 >> >> > Hey yasu, >> > >> > I haven't looked into this but if there is a way you can disable the Intel >> > nic's driver from loading (maybe >> > like this since it's early boot): >> > https://forums.freebsd.org/threads/how-to-boot-with-messed-up-boot-loader-conf.64019/post-371681 >> > >> > That way you can at least get in and do further troubleshooting. You'll >> > need another way to get internet >> > though, or maybe you can load the module manually post boot and see what >> > happens. >> >> On OK prompt I typed 'disable-module em' and them 'boot'. But onboard >> NIS is still ditected as 'em1'. Did I do something wroing? >> >> --- >> Yasuhiro Kimura > > Even if disabling module, possibly automatically re-configured > via /etc/rc.conf using devmatch. Try placing > > devmatch_blocklist="${devmatch_blocklist} if_em" > > line in /etc/rc.conf. > > See `man rc.conf`. > > HTH... > > -- > Tomoaki AOKI <junch...@dec.sakura.ne.jp>
