![]() |
|
|||||||
| FreeBSD Installation and Upgrading Installing and upgrading FreeBSD. |
![]() |
|
|
Thread Tools | Display Modes |
|
|
|
|||
|
I need altq so I compile my own kernel, but there's a patch mismatch. uname -a tells me:
Code:
FreeBSD server 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 17:08:02 CEST 2012 root@server:/usr/obj/usr/src/sys/BTSE-amd64 amd64 Code:
BRANCH="RELEASE-p4" Code:
-------------------------------------------------------------- >>> stage 2.1: cleaning up the object tree -------------------------------------------------------------- ... cd /usr/obj/usr/src/sys/BTSE-amd64.conf; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=amd64 MACHINE=amd64 CPUTYPE= GROFF_BIN_PATH=/usr/obj/usr\ /src/tmp/legacy/usr/bin GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/\ share/tmac _SHLIBDIRPREFIX=/usr/obj/usr/src/tmp VERSION="FreeBSD 9.0-RELEASE-p3 amd64 900044" INSTALL="sh /usr/src/tools/install.sh" ... Last edited by bsdperson; 9th November 2012 at 08:36 AM. |
|
|||
|
Absolutely, but I suspect the problem is prior to that. The -p3 vs -p4 is between the file newvers.sh and the output of make buildkernel ... prior to installkernel
|
|
|||
|
Running strings on /usr/obj/usr/src/sys/BTSE-amd64.conf/kernel gives me (last few lines):
Code:
amd64
v1.16
hptrr
RocketRAID 17xx/2xxx SATA controller driver
v1.2
@(#)FreeBSD 9.0-RELEASE-p4 #4: Wed Nov 7 08:40:03 CET 2012
FreeBSD 9.0-RELEASE-p4 #4: Wed Nov 7 08:40:03 CET 2012
root@server:/usr/obj/usr/src/sys/BTSE-amd64.conf
FreeBSD
9.0-RELEASE-p4
BTSE
Code:
amd64
v1.16
hptrr
RocketRAID 17xx/2xxx SATA controller driver
v1.2
@(#)FreeBSD 9.0-RELEASE-p4 #4: Wed Nov 7 08:40:03 CET 2012
FreeBSD 9.0-RELEASE-p4 #4: Wed Nov 7 08:40:03 CET 2012
root@server:/usr/obj/usr/src/sys/BTSE-amd64.conf
FreeBSD
9.0-RELEASE-p4
BTSE
Code:
FreeBSD server 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 17:08:02 CEST 2012 root@server:/usr/obj/usr/src/sys/BTSE-amd64 amd64 Last edited by bsdperson; 9th November 2012 at 08:35 AM. |
|
|||
|
Solved: installkernel as well as nextboot and others relate to /boot, whereas the actual booting is from /boot-mount/boot/kernel regardless. Very confusing. Up to -p3 this seemed to work as expected. A simple copy of the kernel+modules fixed this. Note to self: after installkernel, cp -r /boot/kernel-btse /boot-mount/boot/kernel, then reboot. Case closed.
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| custom kernel problem | pahel0 | FreeBSD General | 8 | 15th February 2010 10:13 PM |
| kernel version 0?? | Stellar | OpenBSD General | 5 | 30th August 2009 11:07 PM |
| Updating FreeBSD and Building a Custom Kernel | bsdforlife | FreeBSD Installation and Upgrading | 8 | 16th August 2008 02:45 AM |
| Unable to build custom kernel [Wrong configuration?] | jrick | FreeBSD General | 3 | 31st July 2008 01:53 PM |
| gem Collisions, duplex mismatch? | tad1214 | FreeBSD General | 1 | 8th July 2008 02:32 AM |