usb rtwn not loaded properly at boot
Hi I have (with 12-ALPHA5) /boot/loader.conf rtwn_load="YES" if_urtw_usb_load="YES" /etc/rc.conf wlans_rtwn0="wlan0" ifconfig_wlan0="WPA DHCP" but still after boot only lo0 exists and all modules are loaded. Manually running ifconfig wlan0 create wlandev rtwn0 sets up the interface correctly. In my kernel config I have MODULES_OVERRIDE="usb rtwn_usb rtwn " I'm pretty sure this has worked before... Any clues? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: usb rtwn not loaded properly at boot
Johannes Lundberg wrote: Hi I have (with 12-ALPHA5) /boot/loader.conf rtwn_load="YES" if_urtw_usb_load="YES" rtwn(4) thinks this should be if_rtwn_usb_load="YES". /etc/rc.conf wlans_rtwn0="wlan0" ifconfig_wlan0="WPA DHCP" but still after boot only lo0 exists and all modules are loaded. Manually running ifconfig wlan0 create wlandev rtwn0 sets up the interface correctly. In my kernel config I have MODULES_OVERRIDE="usb rtwn_usb rtwn " I'm pretty sure this has worked before... Any clues? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: usb rtwn not loaded properly at boot
On Tue, Sep 18, 2018 at 9:27 AM Yuri Pankov wrote: > Johannes Lundberg wrote: > > Hi > > > > I have (with 12-ALPHA5) > > > > /boot/loader.conf > > rtwn_load="YES" > > if_urtw_usb_load="YES" > > rtwn(4) thinks this should be if_rtwn_usb_load="YES". > Ah yes. Sorry about that. I still suffer confusion from the rename. Still, it doesn't change anything since if_rtwn_usb was loaded anyway. > > /etc/rc.conf > > wlans_rtwn0="wlan0" > > ifconfig_wlan0="WPA DHCP" > > > > but still after boot only lo0 exists and all modules are loaded. > > > > Manually running > > ifconfig wlan0 create wlandev rtwn0 > > sets up the interface correctly. > > > > In my kernel config I have > > MODULES_OVERRIDE="usb rtwn_usb rtwn " > > > > I'm pretty sure this has worked before... Any clues? > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: usb rtwn not loaded properly at boot
> On 18 Sep 2018, at 10:32, Johannes Lundberg wrote: > > On Tue, Sep 18, 2018 at 9:27 AM Yuri Pankov wrote: > >> Johannes Lundberg wrote: >>> Hi >>> >>> I have (with 12-ALPHA5) >>> >>> /boot/loader.conf >>> rtwn_load="YES" >>> if_urtw_usb_load="YES" >> >> rtwn(4) thinks this should be if_rtwn_usb_load="YES". >> > > Ah yes. Sorry about that. I still suffer confusion from the rename. > Still, it doesn't change anything since if_rtwn_usb was loaded anyway. > > >>> /etc/rc.conf >>> wlans_rtwn0="wlan0" >>> ifconfig_wlan0="WPA DHCP" >>> >>> but still after boot only lo0 exists and all modules are loaded. >>> >>> Manually running >>> ifconfig wlan0 create wlandev rtwn0 >>> sets up the interface correctly. >>> >>> In my kernel config I have >>> MODULES_OVERRIDE="usb rtwn_usb rtwn " >>> >>> I'm pretty sure this has worked before... Any clues? >> devd is not calling netif! try running ’service netif start’ and see what happens. danny > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: usb rtwn not loaded properly at boot
Johannes Lundberg wrote: On Tue, Sep 18, 2018 at 9:27 AM Yuri Pankov wrote: Johannes Lundberg wrote: Hi I have (with 12-ALPHA5) /boot/loader.conf rtwn_load="YES" if_urtw_usb_load="YES" rtwn(4) thinks this should be if_rtwn_usb_load="YES". Ah yes. Sorry about that. I still suffer confusion from the rename. Still, it doesn't change anything since if_rtwn_usb was loaded anyway. OK, just making sure. My guess based on experience with iwm where I need to specify both if_iwm_load="YES" *and* iwm8265fw_load="YES" would be explicitly loading the firmware you need from loader.conf. /etc/rc.conf wlans_rtwn0="wlan0" ifconfig_wlan0="WPA DHCP" but still after boot only lo0 exists and all modules are loaded. Manually running ifconfig wlan0 create wlandev rtwn0 sets up the interface correctly. In my kernel config I have MODULES_OVERRIDE="usb rtwn_usb rtwn " I'm pretty sure this has worked before... Any clues? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: usb rtwn not loaded properly at boot
On Tue, Sep 18, 2018 at 9:39 AM Daniel Braniss wrote: > > > > On 18 Sep 2018, at 10:32, Johannes Lundberg wrote: > > > > On Tue, Sep 18, 2018 at 9:27 AM Yuri Pankov wrote: > > > >> Johannes Lundberg wrote: > >>> Hi > >>> > >>> I have (with 12-ALPHA5) > >>> > >>> /boot/loader.conf > >>> rtwn_load="YES" > >>> if_urtw_usb_load="YES" > >> > >> rtwn(4) thinks this should be if_rtwn_usb_load="YES". > >> > > > > Ah yes. Sorry about that. I still suffer confusion from the rename. > > Still, it doesn't change anything since if_rtwn_usb was loaded anyway. > > > > > >>> /etc/rc.conf > >>> wlans_rtwn0="wlan0" > >>> ifconfig_wlan0="WPA DHCP" > >>> > >>> but still after boot only lo0 exists and all modules are loaded. > >>> > >>> Manually running > >>> ifconfig wlan0 create wlandev rtwn0 > >>> sets up the interface correctly. > >>> > >>> In my kernel config I have > >>> MODULES_OVERRIDE="usb rtwn_usb rtwn " > >>> > >>> I'm pretty sure this has worked before... Any clues? > >> > > > devd is not calling netif! > try running ’service netif start’ and see what happens. > Yep that enables wlan0! > danny > > > ___ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscr...@freebsd.org" > > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: usb rtwn not loaded properly at boot
On Tue, Sep 18, 2018 at 9:43 AM Johannes Lundberg wrote: > > > On Tue, Sep 18, 2018 at 9:39 AM Daniel Braniss > wrote: > >> >> >> > On 18 Sep 2018, at 10:32, Johannes Lundberg wrote: >> > >> > On Tue, Sep 18, 2018 at 9:27 AM Yuri Pankov wrote: >> > >> >> Johannes Lundberg wrote: >> >>> Hi >> >>> >> >>> I have (with 12-ALPHA5) >> >>> >> >>> /boot/loader.conf >> >>> rtwn_load="YES" >> >>> if_urtw_usb_load="YES" >> >> >> >> rtwn(4) thinks this should be if_rtwn_usb_load="YES". >> >> >> > >> > Ah yes. Sorry about that. I still suffer confusion from the rename. >> > Still, it doesn't change anything since if_rtwn_usb was loaded anyway. >> > >> > >> >>> /etc/rc.conf >> >>> wlans_rtwn0="wlan0" >> >>> ifconfig_wlan0="WPA DHCP" >> >>> >> >>> but still after boot only lo0 exists and all modules are loaded. >> >>> >> >>> Manually running >> >>> ifconfig wlan0 create wlandev rtwn0 >> >>> sets up the interface correctly. >> >>> >> >>> In my kernel config I have >> >>> MODULES_OVERRIDE="usb rtwn_usb rtwn " >> >>> >> >>> I'm pretty sure this has worked before... Any clues? >> >> >> >> >> devd is not calling netif! >> try running ’service netif start’ and see what happens. >> > > Yep that enables wlan0! > > With wlan0 up and running, unplug and re-plug the wifi adapter will create rtwn0 device but no wlan0. Firmware was missing so I added rtwnfw to MODULES_OVERRIDE but it makes no difference for this problem. >> danny >> >> > ___ >> > freebsd-current@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to " >> freebsd-current-unsubscr...@freebsd.org" >> >> ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD EFI projects
On Mon, Sep 17, 2018 at 11:09 PM, Konstantin Belousov wrote: That said, making only the loader->kernel transition from EFI 32bit to 64bit kernel should be not too hard, and even significantly simpler than to make 32bit EFI load 32bit kernel. amd64 kernels already aware that there might be no BIOS and they do not try to make vm86 calls into real code, and only read memory map from the loader metadata etc. Besides old Macs, this should also benefit newer Intel embedded-like boards. Hi, I can confirm that the kernel already worked fine when booted from 32-bit EFI. I booted an old Mac into HardenedBSD using a 32-bit-EFI build of GRUB2 :) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: usb rtwn not loaded properly at boot
On Tue, Sep 18, 2018 at 10:03 AM Johannes Lundberg wrote: > > > On Tue, Sep 18, 2018 at 9:43 AM Johannes Lundberg > wrote: > >> >> >> On Tue, Sep 18, 2018 at 9:39 AM Daniel Braniss >> wrote: >> >>> >>> >>> > On 18 Sep 2018, at 10:32, Johannes Lundberg >>> wrote: >>> > >>> > On Tue, Sep 18, 2018 at 9:27 AM Yuri Pankov wrote: >>> > >>> >> Johannes Lundberg wrote: >>> >>> Hi >>> >>> >>> >>> I have (with 12-ALPHA5) >>> >>> >>> >>> /boot/loader.conf >>> >>> rtwn_load="YES" >>> >>> if_urtw_usb_load="YES" >>> >> >>> >> rtwn(4) thinks this should be if_rtwn_usb_load="YES". >>> >> >>> > >>> > Ah yes. Sorry about that. I still suffer confusion from the rename. >>> > Still, it doesn't change anything since if_rtwn_usb was loaded anyway. >>> > >>> > >>> >>> /etc/rc.conf >>> >>> wlans_rtwn0="wlan0" >>> >>> ifconfig_wlan0="WPA DHCP" >>> >>> >>> >>> but still after boot only lo0 exists and all modules are loaded. >>> >>> >>> >>> Manually running >>> >>> ifconfig wlan0 create wlandev rtwn0 >>> >>> sets up the interface correctly. >>> >>> >>> >>> In my kernel config I have >>> >>> MODULES_OVERRIDE="usb rtwn_usb rtwn " >>> >>> >>> >>> I'm pretty sure this has worked before... Any clues? >>> >> >>> >>> >>> devd is not calling netif! >>> try running ’service netif start’ and see what happens. >>> >> >> Yep that enables wlan0! >> >> > With wlan0 up and running, unplug and re-plug the wifi adapter will create > rtwn0 device but no wlan0. > Firmware was missing so I added rtwnfw to MODULES_OVERRIDE but it makes no > difference for this problem. > > (cc: imp) Here's devd output: https://gist.github.com/johalun/c9383ff03cb29e12c3f4978e06ca6413 Not sure how to interpret this but it looks like it fails to match rtwn0 at https://gist.github.com/johalun/c9383ff03cb29e12c3f4978e06ca6413#file-gistfile1-txt-L761 >>> danny >>> >>> > ___ >>> > freebsd-current@freebsd.org mailing list >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> > To unsubscribe, send any mail to " >>> freebsd-current-unsubscr...@freebsd.org" >>> >>> ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Some delete-old detrius
doing a delete-old run: drwxr-xr-x 2 root wheel 25 Sep 18 22:55 usr/lib/debug/usr/lib/i18n rm: usr/bin/indent/tests/nsac.0: Not a directory rm: usr/bin/indent/tests/nsac.0.pro: Not a directory rm: usr/bin/indent/tests/nsac.0.stdout: Not a directory rm: usr/bin/indent/tests/sac.0: Not a directory rm: usr/bin/indent/tests/sac.0.pro: Not a directory rm: usr/bin/indent/tests/sac.0.stdout: Not a directory rm: usr/lib/debug/usr/lib/i18n: is a directory I'm not clear on how long we leave stuff lying around in Obsolete or whatever before we purge them. Is this output with us forever? sean signature.asc Description: OpenPGP digital signature
Re: usb rtwn not loaded properly at boot
I filed a bug about this issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231441 I have encountered it with the run USB wireless driver. I haven't tested it with ethernet. Does this issue only affect wireless devices, only certain drivers, or all network connections? On Tue, Sep 18, 2018 at 6:55 AM Johannes Lundberg wrote: > On Tue, Sep 18, 2018 at 10:03 AM Johannes Lundberg > wrote: > > > > > > > On Tue, Sep 18, 2018 at 9:43 AM Johannes Lundberg > > wrote: > > > >> > >> > >> On Tue, Sep 18, 2018 at 9:39 AM Daniel Braniss > >> wrote: > >> > >>> > >>> > >>> > On 18 Sep 2018, at 10:32, Johannes Lundberg > >>> wrote: > >>> > > >>> > On Tue, Sep 18, 2018 at 9:27 AM Yuri Pankov > wrote: > >>> > > >>> >> Johannes Lundberg wrote: > >>> >>> Hi > >>> >>> > >>> >>> I have (with 12-ALPHA5) > >>> >>> > >>> >>> /boot/loader.conf > >>> >>> rtwn_load="YES" > >>> >>> if_urtw_usb_load="YES" > >>> >> > >>> >> rtwn(4) thinks this should be if_rtwn_usb_load="YES". > >>> >> > >>> > > >>> > Ah yes. Sorry about that. I still suffer confusion from the rename. > >>> > Still, it doesn't change anything since if_rtwn_usb was loaded > anyway. > >>> > > >>> > > >>> >>> /etc/rc.conf > >>> >>> wlans_rtwn0="wlan0" > >>> >>> ifconfig_wlan0="WPA DHCP" > >>> >>> > >>> >>> but still after boot only lo0 exists and all modules are loaded. > >>> >>> > >>> >>> Manually running > >>> >>> ifconfig wlan0 create wlandev rtwn0 > >>> >>> sets up the interface correctly. > >>> >>> > >>> >>> In my kernel config I have > >>> >>> MODULES_OVERRIDE="usb rtwn_usb rtwn " > >>> >>> > >>> >>> I'm pretty sure this has worked before... Any clues? > >>> >> > >>> > >>> > >>> devd is not calling netif! > >>> try running ’service netif start’ and see what happens. > >>> > >> > >> Yep that enables wlan0! > >> > >> > > With wlan0 up and running, unplug and re-plug the wifi adapter will > create > > rtwn0 device but no wlan0. > > Firmware was missing so I added rtwnfw to MODULES_OVERRIDE but it makes > no > > difference for this problem. > > > > > (cc: imp) > > Here's devd output: > > https://gist.github.com/johalun/c9383ff03cb29e12c3f4978e06ca6413 > > Not sure how to interpret this but it looks like it fails to match rtwn0 at > > https://gist.github.com/johalun/c9383ff03cb29e12c3f4978e06ca6413#file-gistfile1-txt-L761 > > > > > >>> danny > >>> > >>> > ___ > >>> > freebsd-current@freebsd.org mailing list > >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-current > >>> > To unsubscribe, send any mail to " > >>> freebsd-current-unsubscr...@freebsd.org" > >>> > >>> > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- Patrick McMunn - Learn more about the Catholic Faith: http://www.catholic.com/ - Pray with the Church: http://www.universalis.com/ ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Some delete-old detrius
A problem here is that the references should be to usr.bin instead of usr/bin . See: https://lists.freebsd.org/pipermail/svn-src-head/2018-September/118426.html which reports for svn commit: r336601 - head: QUOTE Looks like this head/ObsoleteFiles.inc update has a typo in each thing added to OLD_FILES . . . # ls -lTdt /usr/tests/usr.bin/indent/* -r--r--r-- 1 root wheel 121 Sep 13 22:53:30 2018 /usr/tests/usr.bin/indent/Kyuafile . . . -r--r--r-- 1 root wheel 295 Sep 13 22:53:29 2018 /usr/tests/usr.bin/indent/binary.0 -r--r--r-- 1 root wheel92 May 1 19:35:24 2018 /usr/tests/usr.bin/indent/sac.0.pro -r--r--r-- 1 root wheel 130 May 1 19:35:24 2018 /usr/tests/usr.bin/indent/sac.0.stdout -r--r--r-- 1 root wheel 122 May 1 19:35:24 2018 /usr/tests/usr.bin/indent/sac.0 -r--r--r-- 1 root wheel94 May 1 19:35:24 2018 /usr/tests/usr.bin/indent/nsac.0.pro -r--r--r-- 1 root wheel 130 May 1 19:35:24 2018 /usr/tests/usr.bin/indent/nsac.0.stdout -r--r--r-- 1 root wheel 123 May 1 19:35:24 2018 /usr/tests/usr.bin/indent/nsac.0 vs. ( note usr.bin vs. usr/bin ): Modified: head/ObsoleteFiles.inc == --- head/ObsoleteFiles.inc Sun Jul 22 12:04:21 2018(r336600) +++ head/ObsoleteFiles.inc Sun Jul 22 12:45:02 2018(r336601) @@ -38,6 +38,13 @@ # xargs -n1 | sort | uniq -d; # done +# 20180722: indent(1) option renamed, test files follow +OLD_FILES+=usr/bin/indent/tests/nsac.0 +OLD_FILES+=usr/bin/indent/tests/nsac.0.pro +OLD_FILES+=usr/bin/indent/tests/nsac.0.stdout +OLD_FILES+=usr/bin/indent/tests/sac.0 +OLD_FILES+=usr/bin/indent/tests/sac.0.pro +OLD_FILES+=usr/bin/indent/tests/sac.0.stdout # 20180721: move of libmlx5.so.1 and libibverbs.so.1 OLD_LIBS+=usr/lib/libmlx5.so.1 OLD_LIBS+=usr/lib/libibverbs.so.1 END QUOTE This was after having the nsac and sac kyua tests report failures in my environment, long after they should have not existed. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD EFI projects
On 9/18/18 4:11 AM, Greg V wrote: > > I can confirm that the kernel already worked fine when booted from > 32-bit EFI. > > I booted an old Mac into HardenedBSD using a 32-bit-EFI build of GRUB2 :) Was that a 64-bit version of FreeBSD? My understanding is the 32-bit FreeBSD boots fine, but 64-bit needs work. -- Rebecca ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
