Re: Migrating from FreeBSD 9.0-STABLE/amd to 10.0-CURRENT/amd64?
On 03/06/12 20:08, Dimitry Andric wrote: > On 2012-03-06 17:09, O. Hartmann wrote: > ... >> Well, I tried to switch by doing a "svn switch" in /usr/src, building a >> kernel, restarting the kernel in single user mode and then trying to >> build the world. At some point in /usr/src/share (I forgot were exactly, >> it was somewhere with lots of locale stuff), the buildworld process >> fails so I couldn't build a world. > > Try doing a fresh checkout instead. And don't try to build the latest > head with clang, it's unfortunately broken at the moment. Use r232569 > if you want to use clang. Mmmm I still end up here building "buildworld": 5 warnings generated. sed -e '/align/d' -e '/nop/d' < boot2.s.tmp > boot2.s rm -f boot2.s.tmp clang -m32 -c boot2.s clang -Os -fno-guess-branch-probability -fomit-frame-pointer -fno-unit-at-a-time -mno-align-long-strings -mrtd -mregparm=3 -DUSE_XREAD -DUFS1_AND_UFS2 -DFLAGS=0x80 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/boot2/../../common -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -mllvm -stack-alignment=8 -mllvm -inline-threshold=3 -mllvm -enable-load-pre=false -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -march=i386 -std=gnu99 -m32 -c /usr/src/sys/boot/i386/boot2/sio.S clang: warning: the clang compiler does not support '-fno-unit-at-a-time' clang: warning: argument unused during compilation: '-fno-guess-branch-probability' clang: warning: argument unused during compilation: '-mno-align-long-strings' clang: warning: argument unused during compilation: '--param max-inline-insns-single=100' clang: warning: argument unused during compilation: '-mpreferred-stack-boundary=2' ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o sio.o objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x2000 -f bin -b /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin kernel: ver=1.02 size=690 load=9000 entry=9010 map=16M pgctl=1:1 client: fmt=bin size=15a1 text=0 data=0 bss=0 entry=0 output: fmt=bin size=1e31 text=200 data=1c31 org=0 entry=0 -49 bytes available *** Error code 1 Stop in /usr/src/sys/boot/i386/boot2. *** Error code 1 Stop in /usr/src/sys/boot/i386. *** Error code 1 Stop in /usr/src/sys/boot. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. signature.asc Description: OpenPGP digital signature
Re: Migrating from FreeBSD 9.0-STABLE/amd to 10.0-CURRENT/amd64?
On 03/06/12 19:03, Olli Hauer wrote: > On 2012-03-06 17:09, O. Hartmann wrote: >> Hello. >> >> Well, I run on a brand new "luxury" box the newest Intel CPU >> Sandy-Brideg-E in its incarnation of the Core i7-X3930K on a decent ASUS >> workstation motherboard. The box is running FreeBSD 9.0-STABLE/amd64 at >> the moment. >> I discovered some "problems" with the SATA/AHCI interface. Since the >> peripherial hardware didn't change, except mainboard and CPU (and a lot >> of more memory), I guess FreeBSD 9.0-STABLE does have some issues with >> the new hardware. So I'd like to use FreeBSD 10.0-CURRENT/amd64, which I >> use successfully on an oldish two core Core2Duo box. >> >> VirtualBox, for instance, on the FBSD 9.0 box with the new hardware, >> stops working from time to time, the Windows-7 is getting stuck. The >> implication, that FreeBSD 9 can not handle the new hardware is wrong at >> that point, since even the VBox could have it's issues with the new 6 >> core Sandy Bridge-E, but the issues with the SATA 6GB subsystems are >> "real". Sometimes the system gets stuck. >> >> Well, I tried to switch by doing a "svn switch" in /usr/src, building a >> kernel, restarting the kernel in single user mode and then trying to >> build the world. At some point in /usr/src/share (I forgot were exactly, >> it was somewhere with lots of locale stuff), the buildworld process >> fails so I couldn't build a world. >> >> It wouldn't be bad if the "switch" isn't possible at the moment by >> simply switching the sources, but I'm still inclined to give the new >> hardware the propper new OS - hoping, that new driver will pay tribute >> to new hardware ... >> >> >> Thanks for your comments in advance, >> Oliver >> > > > Maybe you can reach your update goal faster... > > From your mails to current I know you already have a box running FBSD 10. > > My way to upgrade machines is to share / rsync /usr/src from a central > machine to all others, same for /usr/obj if the architectur match. > Do not forget to sync also make.conf/src.conf and runing mergemaster. > > If the machine is alive after the fast upgrade you can experiment > with different src.conf / kernel settings. > Well, in my case one box is at home (the FBSD 10.0-CUR/amd64) and switched off ... the box which is supposed to be updated is in my lab and still in front of me and at the moment I see no chance to switch the other box on ;-) Well, I thought I do it the hard way - having a running system and carefully migrate ... The new hardware is trmendously fast, so compiling the whole bunch of ports (~ 1000) will take not that long. But at the moment I get plagued by an error when "make buildworld" ... Regards Oliver P.S. By the way: thanks! signature.asc Description: OpenPGP digital signature
Re: Migrating from FreeBSD 9.0-STABLE/amd to 10.0-CURRENT/amd64?
On 03/06/12 20:08, Dimitry Andric wrote: > On 2012-03-06 17:09, O. Hartmann wrote: > ... >> Well, I tried to switch by doing a "svn switch" in /usr/src, building a >> kernel, restarting the kernel in single user mode and then trying to >> build the world. At some point in /usr/src/share (I forgot were exactly, >> it was somewhere with lots of locale stuff), the buildworld process >> fails so I couldn't build a world. > > Try doing a fresh checkout instead. And don't try to build the latest > head with clang, it's unfortunately broken at the moment. Use r232569 > if you want to use clang. Aha! So I'm about to wait until the sources can be build again from scratch with CLANG ... As I wrote before, I'd like to do it the hard way and assuming the source can be build ... Regards, Oliver signature.asc Description: OpenPGP digital signature
Re: Migrating from FreeBSD 9.0-STABLE/amd to 10.0-CURRENT/amd64?
On 03/06/12 18:33, Tom Evans wrote: > On Tue, Mar 6, 2012 at 4:09 PM, O. Hartmann > wrote: >> Hello. >> […] >> >> Well, I tried to switch by doing a "svn switch" in /usr/src, building a >> kernel, restarting the kernel in single user mode and then trying to >> build the world. At some point in /usr/src/share (I forgot were exactly, >> it was somewhere with lots of locale stuff), the buildworld process >> fails so I couldn't build a world. > > /usr/src/UPDATING says this: > > > To upgrade in-place from 8.x-stable to current > -- > > make buildworld [9] > make kernel KERNCONF=YOUR_KERNEL_HERE [8] > [1] > [3] > mergemaster -p [5] > make installworld > mergemaster -i [4] > make delete-old [6] > > > > Even though it says 8.x, I would start from these instructions. > > Cheers > > Tom Here is what I get on FreeBSD 9.0-STABLE #0 r232611: Tue Mar 6 16:36:33 CET 2012 when trying to compile sources being FreeBSD 10.0-CURRENT/amd64 Revision: 232618: [...] ===> sys/boot/i386/boot2 (all) objcopy -S -O binary boot1.out boot1 dd if=/dev/zero of=boot2.ldr bs=512 count=1 1+0 records in 1+0 records out 512 bytes transferred in 0.18 secs (28256364 bytes/sec) clang -Os -fno-guess-branch-probability -fomit-frame-pointer -fno-unit-at-a-time -mno-align-long-strings -mrtd -mregparm=3 -DUSE_XREAD -DUFS1_AND_UFS2 -DFLAGS=0x80 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/boot2/../../common -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -mllvm -stack-alignment=8 -mllvm -inline-threshold=3 -mllvm -enable-load-pre=false -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -march=i386 -std=gnu99-S -o boot2.s.tmp /usr/src/sys/boot/i386/boot2/boot2.c clang: warning: the clang compiler does not support '-fno-unit-at-a-time' clang: warning: argument unused during compilation: '-fno-guess-branch-probability' clang: warning: argument unused during compilation: '-mno-align-long-strings' clang: warning: argument unused during compilation: '--param max-inline-insns-single=100' clang: warning: argument unused during compilation: '-mpreferred-stack-boundary=2' In file included from /usr/src/sys/boot/i386/boot2/boot2.c:170: /usr/src/sys/boot/i386/boot2/../../common/ufsread.c:232:17: warning: cast from 'char *' to 'struct ufs1_dinode *' increases required alignment from 1 to 4 [-Wcast-align] memcpy(&dp1, (struct ufs1_dinode *)blkbuf + n, ^~~~ /usr/src/sys/boot/i386/boot2/../../common/ufsread.c:235:17: warning: cast from 'char *' to 'struct ufs2_dinode *' increases required alignment from 1 to 4 [-Wcast-align] memcpy(&dp2, (struct ufs2_dinode *)blkbuf + n, ^~~~ /usr/src/sys/boot/i386/boot2/boot2.c:222:1: warning: no previous prototype for function 'main' [-Wmissing-prototypes] main(void) ^ /usr/src/sys/boot/i386/boot2/boot2.c:355:4: warning: cast from 'caddr_t' (aka 'char *') to 'Elf32_Word *' (aka 'unsigned int *') increases required alignment from 1 to 4 [-Wcast-align] *(Elf32_Word *)p = es[i].sh_size; ^~~ /usr/src/sys/boot/i386/boot2/boot2.c:619:8: warning: cast from 'caddr_t' (aka 'char *') to 'uint32_t *' (aka 'unsigned int *') increases required alignment from 1 to 4 [-Wcast-align] t1 = *(uint32_t *)PTOV(0x46c); ^~~ 5 warnings generated. sed -e '/align/d' -e '/nop/d' < boot2.s.tmp > boot2.s rm -f boot2.s.tmp clang -m32 -c boot2.s clang -Os -fno-guess-branch-probability -fomit-frame-pointer -fno-unit-at-a-time -mno-align-long-strings -mrtd -mregparm=3 -DUSE_XREAD -DUFS1_AND_UFS2 -DFLAGS=0x80 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/boot2/../../common -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -mllvm -stack-alignment=8 -mllvm -inline-threshold=3 -mllvm -enable-load-pre=false -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -march=i386 -std=gnu99 -m32 -c /usr/src/sys/boot/i386/boot2/sio.S clang: warning: the clang compiler does not support '-fno-unit-at-a-time' clang: warning: argument unused during compi
Re: Migrating from FreeBSD 9.0-STABLE/amd to 10.0-CURRENT/amd64?
On 2012-03-06 22:23, O. Hartmann wrote: > On 03/06/12 19:03, Olli Hauer wrote: >> On 2012-03-06 17:09, O. Hartmann wrote: >>> Hello. >>> >>> Well, I run on a brand new "luxury" box the newest Intel CPU >>> Sandy-Brideg-E in its incarnation of the Core i7-X3930K on a decent ASUS >>> workstation motherboard. The box is running FreeBSD 9.0-STABLE/amd64 at >>> the moment. >>> I discovered some "problems" with the SATA/AHCI interface. Since the >>> peripherial hardware didn't change, except mainboard and CPU (and a lot >>> of more memory), I guess FreeBSD 9.0-STABLE does have some issues with >>> the new hardware. So I'd like to use FreeBSD 10.0-CURRENT/amd64, which I >>> use successfully on an oldish two core Core2Duo box. >>> >>> VirtualBox, for instance, on the FBSD 9.0 box with the new hardware, >>> stops working from time to time, the Windows-7 is getting stuck. The >>> implication, that FreeBSD 9 can not handle the new hardware is wrong at >>> that point, since even the VBox could have it's issues with the new 6 >>> core Sandy Bridge-E, but the issues with the SATA 6GB subsystems are >>> "real". Sometimes the system gets stuck. >>> >>> Well, I tried to switch by doing a "svn switch" in /usr/src, building a >>> kernel, restarting the kernel in single user mode and then trying to >>> build the world. At some point in /usr/src/share (I forgot were exactly, >>> it was somewhere with lots of locale stuff), the buildworld process >>> fails so I couldn't build a world. >>> >>> It wouldn't be bad if the "switch" isn't possible at the moment by >>> simply switching the sources, but I'm still inclined to give the new >>> hardware the propper new OS - hoping, that new driver will pay tribute >>> to new hardware ... >>> >>> >>> Thanks for your comments in advance, >>> Oliver >>> >> >> >> Maybe you can reach your update goal faster... >> >> From your mails to current I know you already have a box running FBSD 10. >> >> My way to upgrade machines is to share / rsync /usr/src from a central >> machine to all others, same for /usr/obj if the architectur match. >> Do not forget to sync also make.conf/src.conf and runing mergemaster. >> >> If the machine is alive after the fast upgrade you can experiment >> with different src.conf / kernel settings. >> > > > Well, in my case one box is at home (the FBSD 10.0-CUR/amd64) and > switched off ... the box which is supposed to be updated is in my lab > and still in front of me and at the moment I see no chance to switch the > other box on ;-) > > Well, I thought I do it the hard way - having a running system and > carefully migrate ... The new hardware is trmendously fast, so compiling > the whole bunch of ports (~ 1000) will take not that long. > > But at the moment I get plagued by an error when "make buildworld" ... > Maybe someone can help / has an idea if you share the issue ... All we have at the moment is that you tried to switch /usr/src and buildworld fails. If you can remember the svn version you are running at home. If you know time where you have checked out the sources at home http://svnweb.freebsd.org/base/ can help to find the rev. num. -- Regards, olli ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Migrating from FreeBSD 9.0-STABLE/amd to 10.0-CURRENT/amd64?
On 2012-03-06 17:09, O. Hartmann wrote: ... > Well, I tried to switch by doing a "svn switch" in /usr/src, building a > kernel, restarting the kernel in single user mode and then trying to > build the world. At some point in /usr/src/share (I forgot were exactly, > it was somewhere with lots of locale stuff), the buildworld process > fails so I couldn't build a world. Try doing a fresh checkout instead. And don't try to build the latest head with clang, it's unfortunately broken at the moment. Use r232569 if you want to use clang. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Migrating from FreeBSD 9.0-STABLE/amd to 10.0-CURRENT/amd64?
On 03/06/12 18:33, Tom Evans wrote: > On Tue, Mar 6, 2012 at 4:09 PM, O. Hartmann > wrote: >> Hello. >> […] >> >> Well, I tried to switch by doing a "svn switch" in /usr/src, building a >> kernel, restarting the kernel in single user mode and then trying to >> build the world. At some point in /usr/src/share (I forgot were exactly, >> it was somewhere with lots of locale stuff), the buildworld process >> fails so I couldn't build a world. > > /usr/src/UPDATING says this: > > > To upgrade in-place from 8.x-stable to current > -- > > make buildworld [9] > make kernel KERNCONF=YOUR_KERNEL_HERE [8] > [1] > [3] > mergemaster -p [5] > make installworld > mergemaster -i [4] > make delete-old [6] > > > > Even though it says 8.x, I would start from these instructions. > > Cheers > > Tom Hello Tom. I know this instruction, and since I fail in the step "make buildworld" I thought there must be another "trick" to jump from 9.0 to 10.0. Regards, Oliver signature.asc Description: OpenPGP digital signature
Re: Migrating from FreeBSD 9.0-STABLE/amd to 10.0-CURRENT/amd64?
On 2012-03-06 17:09, O. Hartmann wrote: > Hello. > > Well, I run on a brand new "luxury" box the newest Intel CPU > Sandy-Brideg-E in its incarnation of the Core i7-X3930K on a decent ASUS > workstation motherboard. The box is running FreeBSD 9.0-STABLE/amd64 at > the moment. > I discovered some "problems" with the SATA/AHCI interface. Since the > peripherial hardware didn't change, except mainboard and CPU (and a lot > of more memory), I guess FreeBSD 9.0-STABLE does have some issues with > the new hardware. So I'd like to use FreeBSD 10.0-CURRENT/amd64, which I > use successfully on an oldish two core Core2Duo box. > > VirtualBox, for instance, on the FBSD 9.0 box with the new hardware, > stops working from time to time, the Windows-7 is getting stuck. The > implication, that FreeBSD 9 can not handle the new hardware is wrong at > that point, since even the VBox could have it's issues with the new 6 > core Sandy Bridge-E, but the issues with the SATA 6GB subsystems are > "real". Sometimes the system gets stuck. > > Well, I tried to switch by doing a "svn switch" in /usr/src, building a > kernel, restarting the kernel in single user mode and then trying to > build the world. At some point in /usr/src/share (I forgot were exactly, > it was somewhere with lots of locale stuff), the buildworld process > fails so I couldn't build a world. > > It wouldn't be bad if the "switch" isn't possible at the moment by > simply switching the sources, but I'm still inclined to give the new > hardware the propper new OS - hoping, that new driver will pay tribute > to new hardware ... > > > Thanks for your comments in advance, > Oliver > Maybe you can reach your update goal faster... >From your mails to current I know you already have a box running FBSD 10. My way to upgrade machines is to share / rsync /usr/src from a central machine to all others, same for /usr/obj if the architectur match. Do not forget to sync also make.conf/src.conf and runing mergemaster. If the machine is alive after the fast upgrade you can experiment with different src.conf / kernel settings. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Migrating from FreeBSD 9.0-STABLE/amd to 10.0-CURRENT/amd64?
On Tue, Mar 6, 2012 at 4:09 PM, O. Hartmann wrote: > Hello. > […] > > Well, I tried to switch by doing a "svn switch" in /usr/src, building a > kernel, restarting the kernel in single user mode and then trying to > build the world. At some point in /usr/src/share (I forgot were exactly, > it was somewhere with lots of locale stuff), the buildworld process > fails so I couldn't build a world. /usr/src/UPDATING says this: To upgrade in-place from 8.x-stable to current -- make buildworld [9] make kernel KERNCONF=YOUR_KERNEL_HERE [8] [1] [3] mergemaster -p [5] make installworld mergemaster -i [4] make delete-old [6] Even though it says 8.x, I would start from these instructions. Cheers Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Migrating from FreeBSD 9.0-STABLE/amd to 10.0-CURRENT/amd64?
Hello. Well, I run on a brand new "luxury" box the newest Intel CPU Sandy-Brideg-E in its incarnation of the Core i7-X3930K on a decent ASUS workstation motherboard. The box is running FreeBSD 9.0-STABLE/amd64 at the moment. I discovered some "problems" with the SATA/AHCI interface. Since the peripherial hardware didn't change, except mainboard and CPU (and a lot of more memory), I guess FreeBSD 9.0-STABLE does have some issues with the new hardware. So I'd like to use FreeBSD 10.0-CURRENT/amd64, which I use successfully on an oldish two core Core2Duo box. VirtualBox, for instance, on the FBSD 9.0 box with the new hardware, stops working from time to time, the Windows-7 is getting stuck. The implication, that FreeBSD 9 can not handle the new hardware is wrong at that point, since even the VBox could have it's issues with the new 6 core Sandy Bridge-E, but the issues with the SATA 6GB subsystems are "real". Sometimes the system gets stuck. Well, I tried to switch by doing a "svn switch" in /usr/src, building a kernel, restarting the kernel in single user mode and then trying to build the world. At some point in /usr/src/share (I forgot were exactly, it was somewhere with lots of locale stuff), the buildworld process fails so I couldn't build a world. It wouldn't be bad if the "switch" isn't possible at the moment by simply switching the sources, but I'm still inclined to give the new hardware the propper new OS - hoping, that new driver will pay tribute to new hardware ... Thanks for your comments in advance, Oliver signature.asc Description: OpenPGP digital signature
