3.8 release plans

[Sascha Wildner]

On Tue, 27 May 2014 10:00:15 +0200, karu.pruun <karu.pruun at gmail.com>  
wrote:

> On Tue, May 27, 2014 at 3:38 PM, Sascha Wildner wrote:
>> On Tue, 27 May 2014 05:19:03 +0200, karu.pruun wrote:
>>> Something I noticed at 3.8.0RC: at boot, the kernel complains that it
>>> cannot find
>>>
>>> /boot/kernel/acpi
>>> /boot/kernel/ehci
>>>
>>> and they are not loaded.
>>
>>
>> On which box is this? Is it an upgraded system. If not, which ISO/IMG  
>> was
>> used? Any idea when it started?
>
>
> I have not seen it with 3.6.x on Virtualbox. I did a fresh install
> with dfly-x86_64-3.8.0RC.iso.bz2 on Virtualbox this morning, uname -a
>
> DragonFly dflybox 3.8-RELEASE DragonFly v3.8.0rc-RELEASE #12: Sun May
> 25 23:15:08 PDT 2014
> root at pkgbox64.dragonflybsd.org:/usr/obj/build/home/justin/src/sys/X86_64_GENERIC
>  x86_64
>
> and noticed the message when booting the installed system from hdd
> (the install cd loaded both modules fine). After the kernel loads from
> hdd, it says:
>
> --
> Unable to load /boot/kernel/acpi
> Unable to load /boot/kernel/ehci
> ACPI autoload failed - inappropriate file type or format
> EHCI autoload failed - inappropriate file type or format

It must be a new issue specific to VirtualBox. I just tried

http://avalon.dragonflybsd.org/iso-images/dfly-x86_64-3.8.0RC.iso.bz2

in Microsoft's Hyper-V and it _does_ load the acpi and ehci modules when  
booting from the ISO itself and also when booting a system which was  
installed from this ISO.

I also now remember a guy in the #dragonflybsd IRC channel who had the  
same issue (also on VirtualBox) some weeks ago. I'll look a bit further  
tonight if I can find something.

Sascha