GENERICSD snapshot on a BBB has issues with loading the if_rtwn_usb module

Mon Jan 25 23:40:24 UTC 2021

Am 25.01.2021 um 19:57 schrieb Warner Losh <imp at bsdimp.com>:
> On Mon, Jan 25, 2021 at 5:33 AM Dr. Rolf Jansen <freebsd-rj at obsigna.com <mailto:freebsd-rj at obsigna.com>> wrote:
> > Am 18.01.2021 um 18:20 schrieb Emmanuel Vadot <manu at bidouilliste.com <mailto:manu at bidouilliste.com>>:
> > 
> >> On Mon, 18 Jan 2021 16:07:38 -0300
> >> "Dr. Rolf Jansen" <freebsd-rj at obsigna.com <mailto:freebsd-rj at obsigna.com>> wrote:
> >> 
> >> While loading of kernel modules do work with the newly build loader_lua.efi, a regression emerged. In /boot/loader.conf I have for some time now the directive loader_color="NO" in order to prevent the serial console changes from my default scheme black text on white background to white on black. Since today, the serial console shows again everything white on black. Is this directive not functional anymore? How can I force the serial console keep on showing black text on white background?
> >> 
> >> Best regards
> >> 
> >> Rolf
> > 
> > Yes we compile with TERM_EMU now so you might need to adjust
> > teken.bg_color and teken.bg_color in loader.conf I think
> 
> That does nothing. The color inversion of the serial console window happens already before loader.conf would be read. The first message that I see in white on black is that efi/freebsd/loader.env was consulted. However, I cannot find that loader.env file. Perhaps, I need to add the teken.fg_color and teken.bg_color directive to this one.
> 
> For the time being, I added echo -e "\e[0m" to /etc/rc.local and this command switches the serial console back to normal after stating-up has been finished.
> 
> I think that the UEFI BIOS is resetting the colors. We've had issues with that on some, but not all, of our servers. I thought they'd been ironed out though.  I'm kinda surprised the teken settings didn't take.
> 
> Can you capture the end of the reboot, start of the next boot?
> 
> Warner

We are talking about a serial console of a BeagleBone Black, which is connected via J1 over FTDI232/USB to a macOS computer. In the Mac Terminal I have running:
sudo cu -s 115200 --nostop -l /dev/tty.usbserial-00000000

Below comes a copy of the console messages between the end of reboot until Loading the kernel (s below). My original e-mail comes in formatted text, so you would see when the terminal color is switched from black on white (the default of the Mac Terminal since 20++ years) to white on black (the default of MS-DOS in the 80ths :-). The color switch happens together with the following output:

Consoles: EFI console  
    Reading loader env vars from /efi/freebsd/loader.env

The actual capture comes below, and as you can see, loader.conf is loaded afterwards.

Thank you very much for looking into this.

Best regards

Rolf

All buffers synced.
Uptime: 5h15m47s
Rebooting...

U-Boot SPL 2020.10 (Jan 22 2021 - 04:24:22 +0000)
Trying to boot from MMC1

U-Boot 2020.10 (Jan 22 2021 - 04:24:22 +0000)

CPU  : AM335X-GP rev 2.1
Model: TI AM335x BeagleBone Black
DRAM:  512 MiB
WDT:   Started with servicing (60s timeout)
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from FAT... OK
Net:   eth2: ethernet at 4a100000, eth3: usb_ether
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
88690 bytes read in 9 ms (9.4 MiB/s)
Found EFI removable media binary efi/boot/bootarm.efi
Scanning disk mmc at 48060000.blk...
** Unrecognized filesystem type **
Scanning disk mmc at 481d8000.blk...
** Unrecognized filesystem type **
Found 6 disks
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
1402608 bytes read in 92 ms (14.5 MiB/s)
Booting /efi\boot\bootarm.efi
...
77 blank lines
...
Consoles: EFI console  
    Reading loader env vars from /efi/freebsd/loader.env
Setting currdev to disk0p1:
FreeBSD/arm EFI loader, Revision 1.1

   Command line arguments: l
   Image base: 0x9cddc000
   EFI version: 2.80
   EFI Firmware: Das U-Boot (rev 8224.4096)
   Console: comconsole (0)
   Load Path: /efi\boot\bootarm.efi
   Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x400,0x3c00)
Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x400,0x3c00)
Setting currdev to disk0p1:
Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(2,0x01,0,0x4000,0x1da8c00)
Setting currdev to disk0p2:
Loading /boot/defaults/loader.conf
Loading /boot/defaults/loader.conf
Loading /boot/device.hints
Loading /boot/loader.conf
Loading /boot/loader.conf.local
/
...
54 blank lines
...
cLoading kernel...
/boot/kernel/kernel text=0x1b4 text=0x6f0394 text=0x182990 data=0xafc70 data=0x0+0x1e8000 syms=[0x4+0x9e3e0+0x4+0x10f605]
Loading configured modules...
/boot/kernel/ipfw_nat.ko text=0x1552 text=0x25bc data=0x2f0+0x4 syms=[0x4+0x1270+0x4+0xc7d]
loading required module 'ipfw'
/boot/kernel/ipfw.ko text=0x855c text=0x24514 data=0x1568+0x8c syms=[0x4+0x6410+0x4+0x4349]
loading required module 'libalias'
/boot/kernel/libalias.ko text=0x2ae0 text=0xac60 data=0x5e8+0x46 syms=[0x4+0x1e50+0x4+0x15e9]
/boot/kernel/if_rtwn_usb.ko text=0xb600 text=0x68b0 data=0x2c4+0x3b syms=[0x4+0x34d0+0x4+0x291e]
loading required module 'rtwn'
/boot/kernel/rtwn.ko text=0x51e0 text=0x18220 data=0x244 syms=[0x4+0x32f0+0x4+0x19e2]
loading required module 'wlan'
/boot/kernel/wlan.ko text=0xdaa0 text=0x3b280 data=0x64f8+0x1c0 syms=[0x4+0x94d0+0x4+0x6e59]
/boot/kernel/if_bridge.ko text=0x2a60 text=0x6e50 data=0x5dc+0x4 syms=[0x4+0x2380+0x4+0x1776]
loading required module 'bridgestp'
/boot/kernel/bridgestp.ko text=0xe60 text=0x4e20 data=0x140+0x18 syms=[0x4+0xe50+0x4+0x840]
/boot/kernel/accf_http.ko text=0x62a text=0x6d4 data=0x19c syms=[0x4+0x430+0x4+0x404]
/boot/kernel/rtwn-rtl8188eufw.ko text=0x3ad1 text=0xbc data=0x118 syms=[0x4+0x3b0+0x4+0x3f7]
/boot/kernel/accf_data.ko text=0x3ad text=0x38 data=0xe8 syms=[0x4+0x280+0x4+0x26d]
/etc/hostid size=0x25
/boot/entropy size=0x1000