Solved NanoBSD FreeBSD 10

Ofloo

Ofloo

I get a kernel compile error, when building NanoBSD Alix configuration on FreeBSD10:

Code: 
>>> Kernel build for OFL_DSK started on Sat Oct 25 11:56:35 CEST 2014
--------------------------------------------------------------
===> OFL_DSK
mkdir -p /usr/obj/nanobsd.ofl_dsk//i386.i386/usr/src/sys
--------------------------------------------------------------
>>> stage 1: configuring the kernel
--------------------------------------------------------------
cd /usr/src/sys/i386/conf;  PATH=/usr/obj/nanobsd.ofl_dsk//i386.i386/usr/src/tmp/legacy/usr/sbin:/usr/obj/nanobsd.ofl_dsk//i386.i386/usr/src/tmp/legacy/usr/bin:/usr/obj/nanobsd.ofl_dsk//i386.i386/usr/src/tmp/legacy/usr/games:/usr/obj/nanobsd.ofl_dsk//i386.i386/usr/src/tmp/legacy/bin:/usr/obj/nanobsd.ofl_dsk//i386.i386/usr/src/tmp/usr/sbin:/usr/obj/nanobsd.ofl_dsk//i386.i386/usr/src/tmp/usr/bin:/usr/obj/nanobsd.ofl_dsk//i386.i386/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin  config  -d /usr/obj/nanobsd.ofl_dsk//i386.i386/usr/src/sys/OFL_DSK  /usr/src/tools/tools/nanobsd/pcengines/OFL_DSK
config: Error: device "atadisk" is unknown
config: Error: device "atapicd" is unknown
config: Error: device "atapist" is unknown
config: 3 errors
*** [buildkernel] Error code 1

make[1]: stopped in /usr/src
1 error

make[1]: stopped in /usr/src
*** [buildkernel] Error code 2
 
I'm not entirely sure what it is you're talking about. This is a generic kernel configuration. All I did in the end is make it install extra packages, however the kernel file is just generic.

It doesn't even get to the customized part.
 
Code: 
--------------------------------------------------------------
>>> Kernel build for ALIX_DSK started on Sun Oct 26 10:57:39 CET 2014
--------------------------------------------------------------
===> ALIX_DSK
mkdir -p /usr/obj/nanobsd.alix_dsk//i386.i386/usr/src/sys
--------------------------------------------------------------
>>> stage 1: configuring the kernel
--------------------------------------------------------------
cd /usr/src/sys/i386/conf;  PATH=/usr/obj/nanobsd.alix_dsk//i386.i386/usr/src/tmp/legacy/usr/sbin:/usr/obj/nanobsd.alix_dsk//i386.i386/usr/src/tmp/legacy/usr/bin:/usr/obj/nanobsd.alix_dsk//i386.i386/usr/src/tmp/legacy/usr/games:/usr/obj/nanobsd.alix_dsk//i386.i386/usr/src/tmp/legacy/bin:/usr/obj/nanobsd.alix_dsk//i386.i386/usr/src/tmp/usr/sbin:/usr/obj/nanobsd.alix_dsk//i386.i386/usr/src/tmp/usr/bin:/usr/obj/nanobsd.alix_dsk//i386.i386/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin  config  -d /usr/obj/nanobsd.alix_dsk//i386.i386/usr/src/sys/ALIX_DSK  /usr/src/tools/tools/nanobsd/pcengines/ALIX_DSK
config: Error: device "atadisk" is unknown
config: Error: device "atapicd" is unknown
config: Error: device "atapist" is unknown
config: 3 errors
*** [buildkernel] Error code 1

make[1]: stopped in /usr/src
1 error

make[1]: stopped in /usr/src
*** [buildkernel] Error code 2
 
The kernel you are compiling is in bold below. You are not using GENERIC. It looks like the options that are erroring were removed in the CURRENT branch in r263185. See here for the changes: https://svnweb.freebsd.org/base?view=revision&revision=263185. Those changes were later merged into STABLE here: https://svnweb.freebsd.org/base?view=revision&revision=265166.

So you have two options here. The first would be to look at the "text changed" at the first link and update the changes yourself. The second and likely more ideal option would be to update your source to the latest releng/10.1 branch and start building your images off that were the issue is already fixed and you can benefit from any other issues that have been fixed over the past year.

--------------------------------------------------------------
>>> Kernel build for ALIX_DSK started on Sun Oct 26 10:57:39 CET 2014
...
--------------------------------------------------------------
... /usr/src/tools/tools/nanobsd/pcengines/ALIX_DSK
Click to expand...
 
ALIX_DSK is a generic configuration file, it's included in the source. I compiled NanoBSD several times over on FreeBSD 8 and 9 it worked just fine. The configuration which FreeBSD included in the source by FreeBSD staff is to me GENERIC.

If you check your source directory you'll notice that it is there ls /usr/src/tools/tools/nanobsd/pcengines/ALIX_DSK

Also FreeBSD 10 is a production release, are you telling me that RC upcoming release, is more production environment ready than a production release?

So I've taken your advice and I've downloaded the changes, to see if the compile works, if it does then to me FreeBSD people should wake up and FIX this issue rather then keeping it for the next release.
 
Ofloo said:
ALIX_DSK is a generic configuration file, it's included in the source, ... I compiled NanoBSD several times over on FreeBSD 8 and 9 it worked just fine, .. the configuration which FreeBSD included in the source by FreeBSD staff is to me GENERIC.
Click to expand...
I would suggest a brief reading of the FreeBSD handbook on kernel configuration. I understand what you are saying, you are referring to "generic" more in the dictionary defintion context. However, in the context of FreeBSD development, GENERIC refers to the kernel configuration that would be located under /usr/src/sys/i386/conf/GENERIC where i386 would be the architecture you are looking for. The ALIX_DSK is a provided configuration but not GENERIC.

https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html

Ofloo said:
If you check your source directory you'll notice that it is there ls /usr/src/tools/tools/nanobsd/pcengines/ALIX_DSK
Click to expand...
These are the files I've cited in the SVNWeb link's in my prior posts. You can see the changes in the SVN history.

Ofloo said:
Also FreeBSD 10 is production release, are you telling me that RC upcoming release, is more production env ready then production release?
Click to expand...
Unfortunately when nobody attempts to build an ALIX image before 10.0-RELEASE then nobody would have known anything was wrong. It's a bit of an edge case and there's bound to be little bugs around the stuff that doesn't get used every day. If you look at the schedule for 10.1-RELEASE it's only a couple weeks away. Not much changes between RC's so if you aren't deploying these NanoBSD images today, building them off of the latest release candidate builds today makes sense since you can easily bump to the release for when you actually deploy what you are testing.

https://www.freebsd.org/releases/10.1R/schedule.html
 
It appears that with the differences you've told me about that the file does indeed compile Thank you for your input.
 
You must log in or register to reply here.
Back
Top