Date: Mon, 25 Jan 2021 20:40:12 -0300 From: "Dr. Rolf Jansen" <freebsd-rj@obsigna.com> To: Warner Losh <imp@bsdimp.com> Cc: Emmanuel Vadot <manu@bidouilliste.com>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: GENERICSD snapshot on a BBB has issues with loading the if_rtwn_usb module Message-ID: <74F08A29-B203-4130-AF75-B70CC2B92979@obsigna.com> In-Reply-To: <CANCZdfqVw8Pypr4=HXxWT5KQ_BnuiPWrNmmEMuYNsLQNDA4mng@mail.gmail.com> References: <47700631-2D94-4BA8-9707-9ADD70C99600@obsigna.com> <20210116184333.f91594f9c3505d2c588d9634@bidouilliste.com> <20210116184833.1a3182a20a2b6c727b64bb59@bidouilliste.com> <06F689CA-B781-4CEB-8F8A-B00FAC684DD3@obsigna.com> <20210117174539.43b55379e6a37881589616a8@bidouilliste.com> <DFBF17C9-935B-48E5-AD20-2F8265780FCD@obsigna.com> <20210117225539.c113796159735c5a3950c774@bidouilliste.com> <03F9A3D3-0A2B-4B09-9C8D-AAAF761C0F4C@obsigna.com> <20210118094510.48eee03d502ea25ab7d09938@bidouilliste.com> <9F0684B2-02EA-4647-BA02-8C6F80C421F7@obsigna.com> <9C2425C5-ABF2-4A3B-8C93-C20554A59000@obsigna.com> <20210118222052.2e0d6c824f0685be8199ad03@bidouilliste.com> <2EC45258-B2DF-4433-95AD-CF2C5245135E@obsigna.com> <CANCZdfqVw8Pypr4=HXxWT5KQ_BnuiPWrNmmEMuYNsLQNDA4mng@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 25.01.2021 um 19:57 schrieb Warner Losh <imp@bsdimp.com>:
> On Mon, Jan 25, 2021 at 5:33 AM Dr. Rolf Jansen =
<freebsd-rj@obsigna.com <mailto:freebsd-rj@obsigna.com>> wrote:
> > Am 18.01.2021 um 18:20 schrieb Emmanuel Vadot <manu@bidouilliste.com =
<mailto:manu@bidouilliste.com>>:
> >=20
> >> On Mon, 18 Jan 2021 16:07:38 -0300
> >> "Dr. Rolf Jansen" <freebsd-rj@obsigna.com =
<mailto:freebsd-rj@obsigna.com>> wrote:
> >>=20
> >> 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=3D"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?
> >>=20
> >> Best regards
> >>=20
> >> Rolf
> >=20
> > 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
>=20
> 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.
>=20
> 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.
>=20
> 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.
>=20
> Can you capture the end of the reboot, start of the next boot?
>=20
> 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 =20
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@4a100000, eth3: usb_ether
Hit any key to stop autoboot: 0=20
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@48060000.blk...
** Unrecognized filesystem type **
Scanning disk mmc@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 =20
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,0x400=
0,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=3D0x1b4 text=3D0x6f0394 text=3D0x182990 =
data=3D0xafc70 data=3D0x0+0x1e8000 syms=3D[0x4+0x9e3e0+0x4+0x10f605]
Loading configured modules...
/boot/kernel/ipfw_nat.ko text=3D0x1552 text=3D0x25bc data=3D0x2f0+0x4 =
syms=3D[0x4+0x1270+0x4+0xc7d]
loading required module 'ipfw'
/boot/kernel/ipfw.ko text=3D0x855c text=3D0x24514 data=3D0x1568+0x8c =
syms=3D[0x4+0x6410+0x4+0x4349]
loading required module 'libalias'
/boot/kernel/libalias.ko text=3D0x2ae0 text=3D0xac60 data=3D0x5e8+0x46 =
syms=3D[0x4+0x1e50+0x4+0x15e9]
/boot/kernel/if_rtwn_usb.ko text=3D0xb600 text=3D0x68b0 data=3D0x2c4+0x3b =
syms=3D[0x4+0x34d0+0x4+0x291e]
loading required module 'rtwn'
/boot/kernel/rtwn.ko text=3D0x51e0 text=3D0x18220 data=3D0x244 =
syms=3D[0x4+0x32f0+0x4+0x19e2]
loading required module 'wlan'
/boot/kernel/wlan.ko text=3D0xdaa0 text=3D0x3b280 data=3D0x64f8+0x1c0 =
syms=3D[0x4+0x94d0+0x4+0x6e59]
/boot/kernel/if_bridge.ko text=3D0x2a60 text=3D0x6e50 data=3D0x5dc+0x4 =
syms=3D[0x4+0x2380+0x4+0x1776]
loading required module 'bridgestp'
/boot/kernel/bridgestp.ko text=3D0xe60 text=3D0x4e20 data=3D0x140+0x18 =
syms=3D[0x4+0xe50+0x4+0x840]
/boot/kernel/accf_http.ko text=3D0x62a text=3D0x6d4 data=3D0x19c =
syms=3D[0x4+0x430+0x4+0x404]
/boot/kernel/rtwn-rtl8188eufw.ko text=3D0x3ad1 text=3D0xbc data=3D0x118 =
syms=3D[0x4+0x3b0+0x4+0x3f7]
/boot/kernel/accf_data.ko text=3D0x3ad text=3D0x38 data=3D0xe8 =
syms=3D[0x4+0x280+0x4+0x26d]
/etc/hostid size=3D0x25
/boot/entropy size=3D0x1000
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?74F08A29-B203-4130-AF75-B70CC2B92979>