Re: 12.3: vt driver does not provide virtual console terminals
On Thu, Dec 09, 2021 at 01:29:19PM -0500, Ed Maste wrote: ! On Sat, 4 Dec 2021 at 13:27, Peter wrote: ! > ! > There is also this error reported: ! > > module_register_init: MOD_LOAD (vesa, 0x80e22c00, 0) error 19 ! ! Are you trying to load vesa.ko via /boot/loader.conf or /etc/rc.d ! kld_list, or is this observed without any vesa-specific configuration? I verified now: I can reproduce the message with GENERIC 12.3 (id 70cb68e7a00, local patches removed), and no loader.conf. It appears before filesytems are mounted, so /etc/rc.d is irrelevant. Trying to load vesa.ko from loader.conf or from the loader prompt produces the same error message and then fails to boot with "vesa not found". A kernel with "device vesa" added does boot, but also produces the message. Doing "kldload vesa.ko" in single-user gives the same error message, and additionally: > sysctl_unregister_oid: failed(22) to unregister sysctl(vesa) ! > This one is widely discussed as currently not supported by vt driver, but ! > this should be related to higher resolution screen, and not virtual ! > terminals missing. Or has it something to do with each other, and is ! > it a known problem? ! ! It is not a known problem, and I believe it should be unrelated to the ! MOD_LOAD error. You can try running `pgrep -fl getty` to confirm that ! getty(8) is running on each of the vtys. Yes they are running. I can also redirect output to the ttyv*, and that works, only the output does not appear on the screens. cheerio, PMc
Re: 12.3: igb driver does not receive vlan-tagged packets
Hi Özkan, I want to say a (late) thank-you for this quick and helpful answer! I did now include the change as of https://reviews.freebsd.org/D33154 into my 12.3-RELEASE, and it solves the issue. cheerio, PMc On Sat, Dec 04, 2021 at 02:06:33PM +0300, Özkan KIRIK wrote: ! Hi, ! ! I hit an issue like this. The e1000 & igb driver doesn't reflect hw ! offload capabilities now. ! https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260068 ! And the differential https://reviews.freebsd.org/D33154 was created ! for the bug reported by me. ! I saw that, you need disable "vlanhwfilter" capability. With the same ! differential, it will work for you also. ! ! regards ! Ozkan ! ! On Sat, Dec 4, 2021 at 1:54 PM Peter wrote: ! > ! > Hija, ! > ! > after swapping network interface card (re0) to igb0, my networking ! > failed. ! > ! > I found that igb does send out vlan tagged packets, but not receive ! > any answers, unless a vlan* device was previousely attached with the ! > required vlan number (observed with tcpdump). ! > ! > My current workaround is this hack in rc.conf, which makes things work ! > again for now (I need vlan 7 only for ISP uplink): ! > ! > > cloned_interfaces="vlan0" ! > > ifconfig_vlan0="vlan 7 vlandev igb0" ! > > ifconfig_vlan0_alias0="destroy" ! > ! > That vlan0 device is not needed, but it must have existed once after ! > boot in order to receive the packets at all. This was not the case ! > with the re0 driver. ! > Switching off all hw-offload stuff doesn't seem to change the issue. ! > ! > Is there a rationale for this, or am I missing some neccessary config? ! > (Not seeing any bugreports or otherwise discussion of the matter) ! > ! > ! > cheerio, ! > PMc ! > -- Peter Much * Fichtenstr. 28 * 65527 Niedernhausen home +49-6127-967111 * road +49-151-21416768
Re: 12.3: igb driver does not receive vlan-tagged packets
I'm glad to hear good news from you. On Sun, Dec 12, 2021 at 2:09 PM Peter wrote: > > Hi Özkan, > > I want to say a (late) thank-you for this quick and helpful answer! > I did now include the change as of https://reviews.freebsd.org/D33154 > into my 12.3-RELEASE, and it solves the issue. > > > cheerio, > PMc > > > On Sat, Dec 04, 2021 at 02:06:33PM +0300, Özkan KIRIK wrote: > ! Hi, > ! > ! I hit an issue like this. The e1000 & igb driver doesn't reflect hw > ! offload capabilities now. > ! https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260068 > ! And the differential https://reviews.freebsd.org/D33154 was created > ! for the bug reported by me. > ! I saw that, you need disable "vlanhwfilter" capability. With the same > ! differential, it will work for you also. > ! > ! regards > ! Ozkan > ! > ! On Sat, Dec 4, 2021 at 1:54 PM Peter wrote: > ! > > ! > Hija, > ! > > ! > after swapping network interface card (re0) to igb0, my networking > ! > failed. > ! > > ! > I found that igb does send out vlan tagged packets, but not receive > ! > any answers, unless a vlan* device was previousely attached with the > ! > required vlan number (observed with tcpdump). > ! > > ! > My current workaround is this hack in rc.conf, which makes things work > ! > again for now (I need vlan 7 only for ISP uplink): > ! > > ! > > cloned_interfaces="vlan0" > ! > > ifconfig_vlan0="vlan 7 vlandev igb0" > ! > > ifconfig_vlan0_alias0="destroy" > ! > > ! > That vlan0 device is not needed, but it must have existed once after > ! > boot in order to receive the packets at all. This was not the case > ! > with the re0 driver. > ! > Switching off all hw-offload stuff doesn't seem to change the issue. > ! > > ! > Is there a rationale for this, or am I missing some neccessary config? > ! > (Not seeing any bugreports or otherwise discussion of the matter) > ! > > ! > > ! > cheerio, > ! > PMc > ! > > > -- > Peter Much * Fichtenstr. 28 * 65527 Niedernhausen > home +49-6127-967111 * road +49-151-21416768
Fwd: Poudriere: Can't build a 13-STABLE jail?
Ideas? sudo poudriere jail -j p130-S-amd64 -t stable/13 -v stable/13 -D -m git+https -c Original Message Subject: Poudriere: Can't build a 13-STABLE jail? Date: 12/12/2021 2:39 pm From: Larry Rosenman To: develop...@freebsd.org I tried to upgrade and also rebuild my 13-STABLE jail, and get this: ld: error: undefined symbol: uncompress referenced by libdwarf_elf_init.c:233 (/usr/src/contrib/elftoolchain/libdwarf/libdwarf_elf_init.c:233) libdwarf_elf_init.o:(_dwarf_elf_init) in archive /usr/lib/libdwarf.a cc: error: linker command failed with exit code 1 (use -v to see invocation) *** [nm.full] Error code 1 make[3]: stopped in /usr/local/poudriere/jails/p130-S-amd64/usr/src/usr.bin/nm 1 error make[3]: stopped in /usr/local/poudriere/jails/p130-S-amd64/usr/src/usr.bin/nm make[2]: stopped in /usr/local/poudriere/jails/p130-S-amd64/usr/src make[1]: stopped in /usr/local/poudriere/jails/p130-S-amd64/usr/src make: stopped in /usr/local/poudriere/jails/p130-S-amd64/usr/src [00:06:18] Error: Failed to 'make buildworld' [00:06:18] Error while creating jail, cleaning up. [00:06:18] Removing p130-S-amd64 jail... done [00:06:28] Cleaning p130-S-amd64 data... done ler in borg in ~ on ☁️ (us-east-1) took 6m27s ❯ Ideas? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106
