Re: kernel -current build failures

[Charlie Li]

On 23/05/2018 19:21, Michael Butler wrote:
> On a device with bluetooth (as in GENERIC modules) ..
> 
> --- ng_ether.o ---
> /usr/src/sys/netgraph/ng_ether.c:871:2: error: no member named
> 'tqh_first' in 'struct ifnethead'; did you mean 'stqh_first'?
> TAILQ_FOREACH(ifp, _ifnet, if_link) {
> ^
> /usr/src/sys/sys/queue.h:724:15: note: expanded from macro 'TAILQ_FOREACH'
> for ((var) = TAILQ_FIRST((head));   \
>  ^
> /usr/src/sys/sys/queue.h:721:36: note: expanded from macro 'TAILQ_FIRST'
> #define TAILQ_FIRST(head)   ((head)->tqh_first)
>  ^
> 
Looks like this is fixed in r334123.

-- 
Charlie Li
Can't think of a witty .sigline today…

(This email address is for mailing list use only; replace local-part
with vishwin for off-list communication)



signature.asc
Description: OpenPGP digital signature

Re: pciconf -l doesn't show any devices on Hyper-V VM

[Sepherosa Ziehau]

Gen1 or Gen2?  On Gen2 Hyper-V, there is _no_ pcib0 and pci0 at all;
unless you uses pci-e pass-through or SR-IOV.

Why do you care about the existence of pci bus?

On Thu, May 24, 2018 at 9:33 AM, Yuri Pankov  wrote:
> Hi,
>
> Running FreeBSD-12.0-CURRENT-amd64-20180514-r333606 snapshot as a VM on
> Hyper-V, `pciconf -l` (and `lspci`, expected) doesn't return any
> information.
>
> Hyper-V Version: 10.0.14393 [SP2] (that's Windows 2016 with Hyper-V role).
>
> dmesg.boot is attached in case it's useful.
>
> ___
> 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"
>



-- 
Tomorrow Will Never Die
___
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: gcc/g++ 4.2.1 -r334125 is getting devd related build failures on ci.freebsd.org

[Eitan Adler]

I got this. not marked as spam

On 23 May 2018 at 18:34, Mark Millard  wrote:
> [This submittal is in part an experiment with how Eitan's
> MUA classifies the Email using an alternate yahoo.com
> address. Eitan: the subject and this note are all unique
> to this message.]
>
> I've reported to Eitan that the gcc/g++ 4.2.1 architectures
> are failing for devd build failures.
>
> Examples include:
>
> --- all_subdir_sbin ---
> cc1plus: warnings being treated as errors
> /usr/obj/usr/src/sparc64.sparc64/tmp/usr/include/c++/4.2/bits/basic_string.h: 
> In member function 'std::basic_string<_CharT, _Traits, _Alloc>::_Rep* 
> std::basic_string<_CharT, _Traits, _Alloc>::_M_rep() const [with _CharT = 
> char, _Traits = std::char_traits, _Alloc = std::allocator]':
> /usr/obj/usr/src/sparc64.sparc64/tmp/usr/include/c++/4.2/bits/basic_string.h:493:
>instantiated from 'std::basic_string<_CharT, _Traits, 
> _Alloc>::~basic_string() [with _CharT = char, _Traits = 
> std::char_traits, _Alloc = std::allocator]'
> /usr/src/sbin/devd/devd.hh:149:   instantiated from here
> /usr/obj/usr/src/sparc64.sparc64/tmp/usr/include/c++/4.2/bits/basic_string.h:288:
>  warning: cast from 'char*' to 'std::basic_string std::char_traits, std::allocator >::_Rep*' increases required 
> alignment of target type
>
> mips64 and mips and sparc64 agree, for example.
>
> powerpc and powerpc64 report:
>
> --- all_subdir_sbin ---
> cc1plus: warnings being treated as errors
> /usr/src/sbin/devd/devd.hh: In function 'void __tcf_0(void*)':
> /usr/src/sbin/devd/devd.hh:150: warning: inlining failed in call to 'virtual 
> config::~config()': --param max-inline-insns-single limit reached
> /usr/src/sbin/devd/devd.cc:175: warning: called from here
>
> but I expect the two sets of types of error message are related
> somehow and the "fix" fixes both types.
>
>
> ===
> Mark Millard
> marklmi at yahoo.com
> ( dsl-only.net went
> away in early 2018-Mar)
>



-- 
Eitan Adler
Source, Ports, Doc committer
Bugmeister, Ports Security teams
___
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"

pciconf -l doesn't show any devices on Hyper-V VM

[Yuri Pankov]

Hi,

Running FreeBSD-12.0-CURRENT-amd64-20180514-r333606 snapshot as a VM on 
Hyper-V, `pciconf -l` (and `lspci`, expected) doesn't return any 
information.


Hyper-V Version: 10.0.14393 [SP2] (that's Windows 2016 with Hyper-V role).

dmesg.boot is attached in case it's useful.
Copyright (c) 1992-2018 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.0-CURRENT #0 r333606: Mon May 14 19:59:08 UTC 2018
r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 
6.0.0)
WARNING: WITNESS option enabled, expect reduced performance.
SRAT: Ignoring memory at addr 0x10820
SRAT: Ignoring memory at addr 0x10
SRAT: Ignoring memory at addr 0x120
SRAT: Ignoring memory at addr 0x220
SRAT: Ignoring memory at addr 0x420
SRAT: Ignoring memory at addr 0x820
VT(efifb): resolution 1024x768
Hyper-V Version: 10.0.14393 [SP2]
  
Features=0x2e7f
  PM Features=0x0 [C2]
  Features3=0xed7b2
Timecounter "Hyper-V" frequency 1000 Hz quality 2000
CPU: AMD Opteron(tm) Processor 6262 HE   (1600.01-MHz K8-class CPU)
  Origin="AuthenticAMD"  Id=0x600f12  Family=0x15  Model=0x1  Stepping=2
  
Features=0x1783fbff
  
Features2=0x9e982203
  AMD Features=0x2e500800
  AMD Features2=0x10bf3
Hypervisor: Origin = "Microsoft Hv"
real memory  = 4294967296 (4096 MB)
avail memory = 4100710400 (3910 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
FreeBSD/SMP: 1 package(s) x 8 core(s)
random: unblocking device.
ioapic0  irqs 0-23 on motherboard
Launching APs: 7 2 1 3 6 5 4
random: entropy device external interface
Timecounter "Hyper-V-TSC" frequency 1000 Hz quality 3000
[ath_hal] loaded
kbd0 at kbdmux0
module_register_init: MOD_LOAD (vesa, 0x810b8610, 0) error 19
netmap: loaded module
nexus0
cryptosoft0:  on motherboard
acpi0:  on motherboard
cpu0:  on acpi0
atrtc0:  port 0x70-0x71 irq 8 on acpi0
atrtc0: registered as a time-of-day clock, resolution 1.00s
Event timer "RTC" frequency 32768 Hz quality 0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
acpi_syscontainer0:  iomem 
0xfe000-0xf,0xf800-0xffdf on acpi0
vmbus0:  on acpi_syscontainer0
vmbus_res0:  irq 5 on acpi0
ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present;
to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Timecounters tick every 10.000 msec
usb_needs_explore_all: no devclass
vmbus0: version 3.0
hvet0:  on vmbus0
Event timer "Hyper-V" frequency 1000 Hz quality 1000
hvkbd0:  on vmbus0
hvheartbeat0:  on vmbus0
hvkvp0:  on vmbus0
hvshutdown0:  on vmbus0
hvtimesync0:  on vmbus0
hvtimesync0: RTT
hvvss0:  on vmbus0
hn0:  on vmbus0
hn0: Ethernet address: 00:15:5d:01:04:00
hn0: link state changed to UP
storvsc0:  on vmbus0
hn1:  on vmbus0
da0 at storvsc0 bus 0 scbus0 target 0 lun 0
da0:  Fixed Direct Access SPC-3 SCSI device
da0: 300.000MB/s transfers
da0: Command Queueing enabled
da0: 65536MB (134217728 512 byte sectors)
cd0 at storvsc0 bus 0 scbus0 target 0 lun 1
cd0:  Removable CD-ROM SPC-3 SCSI device
cd0: 300.000MB/s transfers
cd0: 828MB (424033 2048 byte sectors)
hn1: Ethernet address: 00:15:5d:01:04:01
hn1: link state changed to DOWN
Trying to mount root from zfs:zroot/ROOT/default []...
WARNING: WITNESS option enabled, expect reduced performance.
lo0: link state changed to UP
___
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"

kernel -current build failures

[Michael Butler]

On a device with bluetooth (as in GENERIC modules) ..

--- ng_ether.o ---
/usr/src/sys/netgraph/ng_ether.c:871:2: error: no member named
'tqh_first' in 'struct ifnethead'; did you mean 'stqh_first'?
TAILQ_FOREACH(ifp, _ifnet, if_link) {
^
/usr/src/sys/sys/queue.h:724:15: note: expanded from macro 'TAILQ_FOREACH'
for ((var) = TAILQ_FIRST((head));   \
 ^
/usr/src/sys/sys/queue.h:721:36: note: expanded from macro 'TAILQ_FIRST'
#define TAILQ_FIRST(head)   ((head)->tqh_first)
 ^
On a system without IPSEC ..

--- kernel ---
linking kernel
ld: error: undefined symbol: vnet_entry_ipsec4stat
>>> referenced by key.c
>>>   key.o:(key_allocsp)

ld: error: undefined symbol: vnet_entry_ipsec4stat
>>> referenced by key.c
>>>   key.o:(key_allocsp)
*** [kernel] Error code 1

Michael

___
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: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver)

[Philip Homburg]

I tried both FreeBSD-11.2-BETA2-amd64-bootonly.iso.xz and 
FreeBSD-11.2-BETA2-amd64-mini-memstick.img.xz on a Dell PowerEdge 2950 
BIOS version 2.7.0. With both images, the USB stick is not recognized.

For reference I tried an image for a random other OS and in that case the
USB stick is recognized.

I'll try to experiment a bit to see if I can find what causes the issue.
___
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: Intel Corporation Wireless 8265 / 8275 (rev 78) on FreeBSD 12

[Pete Wright]

On 05/23/2018 00:41, David Pan wrote:

Hi:
how config the Intel Corporation Wireless 8265 / 8275 (rev 78) on FreeBSD 12?I 
installed FreeBSD 12 on my thinkpad t470p ,and can not drive the Intel Wireless 
Card.
please help me fix that,


I have this working on my end under both 12-current and 11-stable. 
here's my configuration:


output from "pciconf -lv"
iwm0@pci0:3:0:0:    class=0x028000 card=0x10108086 chip=0x24fd8086 
rev=0x78 hdr=0x00

    vendor = 'Intel Corporation'
    device = 'Wireless 8265 / 8275'
    class  = network


to bring up the card i have added this entry to /etc/rc.conf:

kld_list="if_iwm"

then configuring the interface is the same as any other wifi as per the 
handbook, the device will be available as "iwm0".



hope this helps,
-pete

--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA

___
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: Intel Corporation Wireless 8265 / 8275 (rev 78) on FreeBSD 12

[Sean Bruno]

On 05/23/18 01:41, David Pan wrote:
> Hi:
> how config the Intel Corporation Wireless 8265 / 8275 (rev 78) on FreeBSD 
> 12?I installed FreeBSD 12 on my thinkpad t470p ,and can not drive the Intel 
> Wireless Card.
> please help me fix that,
> 
> thx
> David Pan
> 

This seems to be a "iwm(4)" device.  Try loading this driver in loader.conf.


https://www.freebsd.org/doc/handbook/network-wireless.html

sean



signature.asc
Description: OpenPGP digital signature

Re: [RFC] Deprecation and removal of the drm2 driver

[Glen Barber]

On Wed, May 23, 2018 at 11:48:38AM +0200, Philip Homburg wrote:
> >Also as the Moore's law curve flattens expect the life of these
> >older, but not so old, machines to live quiet some time.  I
> >believe we are talking sandy bridge and earlier?  If that is
> >corret Sandy bridge is still a very viable system.
> 
> I noticed this lack of love for older systems recently. 
> 
> I wanted to use an older Dell server to test the 11.2 BETAs and RCs.
> 
> Turns out, you can't install FreeBSD using a USB stick image because the
> BIOS only support MBR. No idea why MBR support was dropped for the USB images.
> 
> In the end I had to find a CD burner, and after a couple of tries managed to
> install from CD.
> 
> After that, my ansible playbooks started failing because /boot/loader.conf 
> is absent if you boot from zfs in combination with MBR.
> 
> Pity. This older server hardware is great for trying out new releases, play 
> with zfs, etc.

The disc1.iso (as well as bootonly.iso and dvd1.iso) images are now
built as hybrid images, supporting both MBR and GPT, as well as being
written to a flash drive (like memstick.img) as well as a CD.

MBR support was initially removed from the memstick installer, as it is
not compatible with some UEFI implementations.  (Or, at least that is my
understanding, based on my limited intimate knowledge of UEFI.)

Glen



signature.asc
Description: PGP signature

Re: [RFC] Deprecation and removal of the drm2 driver

[Ed Maste]

On 23 May 2018 at 05:48, Philip Homburg  wrote:
>
> Turns out, you can't install FreeBSD using a USB stick image because the
> BIOS only support MBR. No idea why MBR support was dropped for the USB images.

We haven't "dropped" MBR support, and our amd64 memstick images are a
combined hybrid format and do in general boot on legacy systems. That
said, there are a number of firmware implementations that refuse to
boot from the hybrid format - this has been a problem with Lenovo
firmware in particular.

Those of you with a system unable to boot from our MBR images, can you
reply to the "Boot USB memstick with MBR" fork of this thread with
details about the system and firmware version?
___
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"

Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver)

[Johannes Lundberg]

On Wed, May 23, 2018 at 12:41 PM, Philip Homburg 
wrote:

> >It's not that hard create a mbr based usb-stick. Far easier than to find a
> >CD burner.
>
> 'Not hard' means
> - undocumented. Or at least, if you start with release notes and install
>   instructions you won't find it.
> - Probably only works if you already have a FreeBSD system.
>
> And if it is indeed 'not hard', why not just generate such an image as
> part
> of the release build?
>

As someone who burn memsticks weekly and don't own a cd r/w, I agree.
It seems there's no way to download an .iso or .img image that will boot
from usb on legacy bios. This is bad and should be fixed.

We shouldn't expect people that want to experiment with FreeBSD on non-UEFI
hardware to already have a FreeBSD installation where they can prepare boot
media... They shouldn't have to.

File a bug report in bugzilla and try to poke the right people (I don't
know who is working in this area).
I guess the options are, either we make a hybrid .img that'll boot off both
(maybe not that easy if it requires changes to boot assembly code) or just
add a -legacy-bios.img to the image generation scripts.

This is important since it's about lowering the threshold of bringing
people to FreeBSD and giving a good (i.e. working) first impression.


>
> >I believe boot/loader.conf is something you have to create, it is not
> there
> >by default.
>
> That's not the problem. The problem is that it lives on a separate zpool
> that
> is lost at every reboot.
>
>
> ___
> 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"

Intel Corporation Wireless 8265 / 8275 (rev 78) on FreeBSD 12

[David Pan]

Hi:
how config the Intel Corporation Wireless 8265 / 8275 (rev 78) on FreeBSD 12?I 
installed FreeBSD 12 on my thinkpad t470p ,and can not drive the Intel Wireless 
Card.
please help me fix that,

thx
David Pan

___
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: UEFI equivalent of boot.config? (Was: Re: [RFC] Deprecation and removal of the drm2 driver)

[Toomas Soome]

> On 23 May 2018, at 13:29, sth...@nethelp.no wrote:
> 
> Hijacking a thread here,
> 
>> Turns out, you can't install FreeBSD using a USB stick image because the
>> BIOS only support MBR. No idea why MBR support was dropped for the USB 
>> images.
>> 
>> In the end I had to find a CD burner, and after a couple of tries managed to
>> install from CD.
> 
> On a somewhat related note - I recently installed 11.1-STABLE on a box
> with support for both UEFI and "good old fashioned BIOS". I initially
> used UEFI and GPT, but ended up switching to BIOS and MBR because I
> needed boot.config to enable booting from an alternate partition.
> 
> Despite lots of Googling I couldn't find a simple way to do this using
> config stored on the disk itself (e.g. having "0:ad(0,f)/boot/loader"
> in /boot.config) with UEFI.
> 
> Does anybody know if this can be done using UEFI?
> 
> Steinar Haug, Nethelp consulting, sth...@nethelp.no

it can but it a bit different situation there. you can not start bios boot 
loader from UEFI loader or vice versa, you only can use the same platform 
binaries.

for UEFI case, the boot1.efi does not process boot.config, so you have total 3 
options - you switch boot disk in UEFI boot manager, or you use chain command 
to load either bootx64.efi from target disk ESP partition or you use chain 
command to load /boot/loader.efi from target disk freebsd root file system. You 
also can set currdev to point to new root, but usually you want a bit more 
(read in the configuration etc) so the chainload may be a bit easier.

Once you have figured out the proper file name to use with chain command, you 
can set chain_disk to have it as value and you will have chain menu entry… like 
chain_disk=zfs:zroot/ROOT/default:/boot/loader.efi

rgds,
toomas


___
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: [RFC] Deprecation and removal of the drm2 driver

[Philip Homburg]

>It's not that hard create a mbr based usb-stick. Far easier than to find a
>CD burner.

'Not hard' means
- undocumented. Or at least, if you start with release notes and install 
  instructions you won't find it.
- Probably only works if you already have a FreeBSD system.

And if it is indeed 'not hard', why not just generate such an image as part 
of the release build?

>I believe boot/loader.conf is something you have to create, it is not there
>by default.

That's not the problem. The problem is that it lives on a separate zpool that
is lost at every reboot.


___
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: [RFC] Deprecation and removal of the drm2 driver

[Andreas Nilsson]

On Wed, May 23, 2018 at 11:48 AM, Philip Homburg 
wrote:

> >Also as the Moore's law curve flattens expect the life of these
> >older, but not so old, machines to live quiet some time.  I
> >believe we are talking sandy bridge and earlier?  If that is
> >corret Sandy bridge is still a very viable system.
>
> I noticed this lack of love for older systems recently.
>
> I wanted to use an older Dell server to test the 11.2 BETAs and RCs.
>
> Turns out, you can't install FreeBSD using a USB stick image because the
> BIOS only support MBR. No idea why MBR support was dropped for the USB
> images.
>

It's not that hard create a mbr based usb-stick. Far easier than to find a
CD burner.

>
> In the end I had to find a CD burner, and after a couple of tries managed
> to
> install from CD.
>
> After that, my ansible playbooks started failing because /boot/loader.conf
> is absent if you boot from zfs in combination with MBR.
>
I believe boot/loader.conf is something you have to create, it is not there
by default.

>
> Pity. This older server hardware is great for trying out new releases,
> play
> with zfs, etc.
> ___
> 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"

UEFI equivalent of boot.config? (Was: Re: [RFC] Deprecation and removal of the drm2 driver)

[sthaug]

Hijacking a thread here,

> Turns out, you can't install FreeBSD using a USB stick image because the
> BIOS only support MBR. No idea why MBR support was dropped for the USB images.
> 
> In the end I had to find a CD burner, and after a couple of tries managed to
> install from CD.

On a somewhat related note - I recently installed 11.1-STABLE on a box
with support for both UEFI and "good old fashioned BIOS". I initially
used UEFI and GPT, but ended up switching to BIOS and MBR because I
needed boot.config to enable booting from an alternate partition.

Despite lots of Googling I couldn't find a simple way to do this using
config stored on the disk itself (e.g. having "0:ad(0,f)/boot/loader"
in /boot.config) with UEFI.

Does anybody know if this can be done using UEFI?

Steinar Haug, Nethelp consulting, sth...@nethelp.no
___
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: [RFC] Deprecation and removal of the drm2 driver

[Philip Homburg]

>Also as the Moore's law curve flattens expect the life of these
>older, but not so old, machines to live quiet some time.  I
>believe we are talking sandy bridge and earlier?  If that is
>corret Sandy bridge is still a very viable system.

I noticed this lack of love for older systems recently. 

I wanted to use an older Dell server to test the 11.2 BETAs and RCs.

Turns out, you can't install FreeBSD using a USB stick image because the
BIOS only support MBR. No idea why MBR support was dropped for the USB images.

In the end I had to find a CD burner, and after a couple of tries managed to
install from CD.

After that, my ansible playbooks started failing because /boot/loader.conf 
is absent if you boot from zfs in combination with MBR.

Pity. This older server hardware is great for trying out new releases, play 
with zfs, etc.
___
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"