compiling FreeBSD to test a netbook (was: Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver)
On Fri, 26 Feb 2010 16:21:06 -0800 Xin LI wrote: > I've asked him to try a > 9-CURRENT kernel but the Atom based netbook would take some while to > compile the code =-) It's very easy/quick to (cross) compile world at a beafy machine and install the system to an USB stick. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: gptboot rewrite, bootonce, etc.
Hi! On Sat, 18 Sep 2010 01:45:42 +0200 Pawel Jakub Dawidek wrote: > My company was in need for functionality similar to nextboot(8), but on > boot loader level, so we can have two partitions we boot from where one > is known to be good and the other is used for upgrades. We upgrade by > dd(1)ing entire partition image onto unused partition, we mark it as > try-to-boot-from-it-but-only-once, reboot and if we fail to boot from > the new partition, we fall back to the old, good partition. If we > succeed on the other hand, we mark the new partition as our boot > partition and mark the other one as unused. > Well, how hard can it be? > After around two weeks of work, I ended up rewriting gptboot in large > parts, reorganizing a lot of code, improving and extending gpart a bit > and implementing desire functionality. > Here is the patch for review and test: > http://people.freebsd.org/~pjd/patches/gptboot.patch Great! Since I need to have both i386 and amd64 at my box here are my test results: - [~]b...@alya% uname -a FreeBSD alya 9.0-CURRENT FreeBSD 9.0-CURRENT #1 r212758M: Sat Sep 18 16:13:38 MSD 2010 b...@alya:/space/FreeBSD/base/head/obj/space/FreeBSD/base/head/src/sys/ALYA amd64 [~]b...@alya% glabel status Name Status Components gptid/c6053c9b-abcc-11df-b740-00251124aff4 N/A ad4p1 label/9-amd64 N/A ad4p2 label/swap N/A ad4p3 label/space N/A ad4p4 label/9-i386 N/A ad4p5 [~]b...@alya% mount /dev/label/9-amd64 on / (ufs, local) devfs on /dev (devfs, local, multilabel) /dev/label/space on /space (ufs, local) /dev/md0 on /tmp (ufs, local, nosuid, soft-updates) procfs on /proc (procfs, local) linprocfs on /compat/linux/proc (linprocfs, local) linsysfs on /compat/linux/sys (linsysfs, local) fdescfs on /dev/fd (fdescfs) [~]b...@alya% gpart show => 34 490234685 ad4 GPT (234G) 341281 freebsd-boot (64K) 162 419430402 freebsd-ufs (20G) 4194320283886083 freebsd-swap (4.0G) 50331810 2097152004 freebsd-ufs (100G) 260047010 419430405 freebsd-ufs (20G) 301990050 188244669 - free - (90G) [~]b...@alya% gpart set -a bootme -i 2 ad4 bootme set on ad4p2 [~]b...@alya% gpart set -a bootonce -i 5 ad4 bootonce set on ad4p5 [~]b...@alya% gpart show => 34 490234685 ad4 GPT (234G) 341281 freebsd-boot (64K) 162 419430402 freebsd-ufs [bootme] (20G) 4194320283886083 freebsd-swap (4.0G) 50331810 2097152004 freebsd-ufs (100G) 260047010 419430405 freebsd-ufs [bootonce,bootme] (20G) 301990050 188244669 - free - (90G) - Install i386 kernel/world to ad4p5, successful reboot, get i386 system. Next reboot (get amd64 system back): - [~]b...@alya% gpart show => 34 490234685 ad4 GPT (234G) 341281 freebsd-boot (64K) 162 419430402 freebsd-ufs [bootme] (20G) 4194320283886083 freebsd-swap (4.0G) 50331810 2097152004 freebsd-ufs (100G) 260047010 419430405 freebsd-ufs (20G) 301990050 188244669 - free - (90G) - All seems to work fine. > Any comments or suggestions? Only one for now. With current default syslog configuration logging to local0.warning and local0.info goes nowhere. It will be good if those messages have traces at the default system. Thank you! That's really great. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: Null modem to USB wire not working
On Sun, 19 Sep 2010 21:25:36 +0200 David DEMELIER wrote: > I just bought a null modem to USB from Profilic and it isn't > recognized by FreeBSD. > It's a chipset Prolific Technology Inc. > Sep 19 21:19:15 Melon root: Unknown USB device: vendor 0x067b product > 0x2303 bus uhub6 > Sep 19 21:19:15 Melon kernel: ugen6.2: at usbus6 > Is there any driver I can use or I need to buy another one? alya% apropos prolific uplcom(4)- USB support for Prolific PL-2303/2303X/2303HX serial adapters driver -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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"
groff build failure (me too, but i386)
Hi! Since nobody seems to get the error it may be my fault. Please, help if you can. Thanks! Here are some details: - [~]b...@bb% uname -a FreeBSD bb.ipt.ru 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r214737: Wed Nov 3 18:48:54 MSK 2010 r...@bb.ipt.ru:/usr/obj/usr/src/sys/GENERIC i386 [~]b...@bb% svn info /usr/src Path: /usr/src URL: svn://svn.freebsd.org/base/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 215798 Node Kind: directory Schedule: normal Last Changed Author: kib Last Changed Rev: 215798 Last Changed Date: 2010-11-24 15:34:25 +0300 (ср, 24 ноя 2010) [~]b...@bb% svn status /usr/src [~]b...@bb% make -C /usr/src buildworld ... c++ -O2 -pipe -I/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../../../../contrib/groff/src/preproc/eqn -I. -DHAVE_CONFIG_H -I/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../../../../contrib/groff/src/include -I/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../src/include -fstack-protector -fno-rtti -fno-exceptions -c eqn.cpp y.tab.c: In function 'int yygrowstack()': y.tab.c:703: error: invalid conversion from 'void*' to 'short int*' y.tab.c:709: error: invalid conversion from 'void*' to 'YYSTYPE*' *** Error code 1 Stop in /usr/src/gnu/usr.bin/groff/src/preproc/eqn. ... - -- WBR, bsam ___ 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: groff build failure (me too, but i386)
Hi Matthew, On Wed, 24 Nov 2010 07:49:08 -0800 Matthew Jacob wrote: > Update your tree. This was broken in fixed within the last week or so Hm, I'm not sure what did you mean, since [1] and [2]. > > Since nobody seems to get the error it may be my fault. Please, help > > if you can. Thanks! > > > > Here are some details: > > - > > [~]b...@bb% uname -a > > FreeBSD bb.ipt.ru 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r214737: Wed Nov 3 > > 18:48:54 MSK 2010 r...@bb.ipt.ru:/usr/obj/usr/src/sys/GENERIC i386 > > [~]b...@bb% svn info /usr/src > > Path: /usr/src > > URL: svn://svn.freebsd.org/base/head > > Repository Root: svn://svn.freebsd.org/base > > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > > Revision: 215798 > > Node Kind: directory > > Schedule: normal > > Last Changed Author: kib > > Last Changed Rev: 215798 > > Last Changed Date: 2010-11-24 15:34:25 +0300 (ср, 24 ноя 2010) [1] > > [~]b...@bb% svn status /usr/src [2] > > [~]b...@bb% make -C /usr/src buildworld > > ... > > c++ -O2 -pipe > > -I/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../../../../contrib/groff/src/preproc/eqn > > -I. -DHAVE_CONFIG_H > > -I/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../../../../contrib/groff/src/include > > -I/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../src/include > > -fstack-protector -fno-rtti -fno-exceptions -c eqn.cpp > > y.tab.c: In function 'int yygrowstack()': > > y.tab.c:703: error: invalid conversion from 'void*' to 'short int*' > > y.tab.c:709: error: invalid conversion from 'void*' to 'YYSTYPE*' > > *** Error code 1 > > > > Stop in /usr/src/gnu/usr.bin/groff/src/preproc/eqn. > > ... > > - -- WBR, bsam ___ 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"
[solved] Re: groff build failure (me too, but i386)
On Wed, 24 Nov 2010 18:08:48 +0300 Boris Samorodov wrote: > Since nobody seems to get the error it may be my fault. Please, help > if you can. Thanks! > Here are some details: > - > [~]b...@bb% uname -a > FreeBSD bb.ipt.ru 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r214737: Wed Nov 3 > 18:48:54 MSK 2010 r...@bb.ipt.ru:/usr/obj/usr/src/sys/GENERIC i386 > [~]b...@bb% svn info /usr/src > Path: /usr/src > URL: svn://svn.freebsd.org/base/head > Repository Root: svn://svn.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 215798 > Node Kind: directory > Schedule: normal > Last Changed Author: kib > Last Changed Rev: 215798 > Last Changed Date: 2010-11-24 15:34:25 +0300 (ср, 24 ноя 2010) > [~]b...@bb% svn status /usr/src > [~]b...@bb% make -C /usr/src buildworld > ... > c++ -O2 -pipe > -I/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../../../../contrib/groff/src/preproc/eqn > -I. -DHAVE_CONFIG_H > -I/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../../../../contrib/groff/src/include > -I/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../src/include > -fstack-protector -fno-rtti -fno-exceptions -c eqn.cpp > y.tab.c: In function 'int yygrowstack()': > y.tab.c:703: error: invalid conversion from 'void*' to 'short int*' > y.tab.c:709: error: invalid conversion from 'void*' to 'YYSTYPE*' > *** Error code 1 > Stop in /usr/src/gnu/usr.bin/groff/src/preproc/eqn. > ... > - Jos Backus helped offline to find the cure: # cd /usr/src/gnu/usr.bin/groff; make cleandir; make cleandir; make clean -- WBR, bsam ___ 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: groff build failure (me too, but i386)
Hi Matthew, thanks for your attention. On Wed, 24 Nov 2010 22:43:56 +0100 Ulrich Spörlein wrote: > On Wed, 24.11.2010 at 19:24:48 +0300, Boris Samorodov wrote: > > > > On Wed, 24 Nov 2010 07:49:08 -0800 Matthew Jacob wrote: > > > > > Update your tree. This was broken in fixed within the last week or so > > > > Hm, I'm not sure what did you mean, since [1] and [2]. > Please try: > # cd /usr/src/usr.bin/lex I've just responded to current@ that cleaning of /usr/src/gnu/usr.bin/groff helped here. > # make clean; make cleandir; make obj > # make && make install > Then run buildworld again. -- WBR, bsam ___ 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: groff build failure (me too, but i386)
On Thu, 25 Nov 2010 00:52:19 +0300 Boris Samorodov wrote: > Hi Matthew, Matthew, Ulrich, sorry! Sure I ment Ulrich here. > thanks for your attention. > On Wed, 24 Nov 2010 22:43:56 +0100 Ulrich Spörlein wrote: > > On Wed, 24.11.2010 at 19:24:48 +0300, Boris Samorodov wrote: > > > > > > On Wed, 24 Nov 2010 07:49:08 -0800 Matthew Jacob wrote: > > > > > > > Update your tree. This was broken in fixed within the last week or so > > > > > > Hm, I'm not sure what did you mean, since [1] and [2]. > > Please try: > > # cd /usr/src/usr.bin/lex > I've just responded to current@ that cleaning of > /usr/src/gnu/usr.bin/groff helped here. > > # make clean; make cleandir; make obj > > # make && make install > > Then run buildworld again. -- WBR, bsam ___ 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"
[clang] regression: tmpfs is not mounted from fstab
Hi! I can't mount tmpfs from fstab if world/kernel are build by clang, however just making world with gcc works fine. The last revision I've tested: - % uname -a FreeBSD h30.sp.ipt.ru 9.0-CURRENT FreeBSD 9.0-CURRENT #1 r219024: Fri Feb 25 13:17:07 MSK 2011 b...@h30.sp.ipt.ru:/usr/obj/usr/src/sys/BB i386 - The previos clang kernel at r218879 works. Mounting from rc.conf works as well. -- WBR, bsam ___ 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: [clang] regression: tmpfs is not mounted from fstab
On Fri, 25 Feb 2011 15:36:46 +0300 Boris Samorodov wrote: > I can't mount tmpfs from fstab if world/kernel are build by clang, Sorry, should have mentioned earlier, tmpfs module is loaded. The diagnostic message is: - mount: tmpfs: Operation not supported by device - -- WBR, bsam ___ 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: [clang] regression: tmpfs is not mounted from fstab
On Fri, 25 Feb 2011 14:33:38 +0100 Dimitry Andric wrote: > On 2011-02-25 13:36, Boris Samorodov wrote: > > I can't mount tmpfs from fstab if world/kernel are build by clang, > > however just making world with gcc works fine. > The cause of this issue is a problem with the way clang's integrated > assembler handles global symbols that are not referenced. > This problem has been submitted upstream, and it is fixed meanwhile, so > I will import a new clang snapshot soon. > For now, please build kernels with "-no-integrated-as" added to > COPTFLAGS, that should fix it. FYI unfortunately this does not help. Full build log is here: ftp://ftp.bsam.ru/pub/tmp/bk.log.bz2 -- WBR, bsam ___ 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: [clang] regression: tmpfs is not mounted from fstab
В вс, 27/02/2011 в 02:43 +0100, Dimitry Andric пишет: > On 2011-02-25 16:58, Boris Samorodov wrote: > > On Fri, 25 Feb 2011 14:33:38 +0100 Dimitry Andric wrote: > >> For now, please build kernels with "-no-integrated-as" added to > >> COPTFLAGS, that should fix it. > > > > FYI unfortunately this does not help. Full build log is here: > > ftp://ftp.bsam.ru/pub/tmp/bk.log.bz2 > > Hm, I was wrong, COPTFLAGS is used for the kernel itself, but CFLAGS for > the modules. So you had to add -no-integrated-as to both CFLAGS and > COPTFLAGS for it to work... > > In any case, in r219077 I imported a new drop of llvm/clang that should > fix the problem without adding those flags. Can you please try it with > this new version? Thanks, works fine at: - % uname -a FreeBSD h30.sp.ipt.ru 9.0-CURRENT FreeBSD 9.0-CURRENT #3 r219085: Sun Feb 27 20:57:30 MSK 2011 b...@h30.sp.ipt.ru:/usr/obj/usr/src/sys/BB i386 - -- WBR, bsam ___ 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: Can't update CLang-based system
On Sun, 27 Feb 2011 23:55:34 -0800 Doug Barton wrote: > On 02/27/2011 19:30, Tim Kientzle wrote: > > I have a FreeBSD-CURRENT AMD64 system here that was last updated at r215029. > > > > I'm trying to update it to r219079, but the build fails in lib/libz > > when it tries to compile gvmat64.S. It looks like the Makefile here > > has a workaround for clang on AMD64, but it doesn't seem to actually > > be working in this case. > I have a different problem on r219092. Everything builds find, but > "linking kernel.debug" hangs forever. It can't even be killed with > ^C. I had the same problem with kernel.debug hanging (top showed ctfconvert sitting at umtx state) with a custom kernel. I tried many things (tmpfs, sound and linux loadable modules were broken as well) and can't say for sure what helped me but seems that GENERIC kernel was built successfully. > My existing system is r218985M, which was built with clang. This > is my first time trying to build a system with clang ON a system that > was itself built with clang (if that makes sense). -- WBR, bsam ___ 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"
weekly whatis database and readonly /usr mount
Hello List, I've installed a testing system with readonly /usr filesystem. And I was surprised by following weekly report (BTW locate database rebuilded just fine): - Rebuilding whatis database: makewhatis: /usr/share/man/whatis.tmp: Read-only file system makewhatis: /usr/share/openssl/man/whatis.tmp: Read-only file system - Is there any reason for using /usr filesystem istead of /tmp, /var/tmp? -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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"
MAKEOBJDIRPREFIX and installkernel
Hi List, here is something strange with current CURRENT: - [~]b...@izar% LANG=C svn info FreeBSD/base/head/src Path: FreeBSD/base/head/src URL: svn+ssh://svn.freebsd.org/base/head Repository Root: svn+ssh://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 208354 Node Kind: directory Schedule: normal Last Changed Author: jkim Last Changed Rev: 208353 Last Changed Date: 2010-05-20 20:24:12 +0400 (Thu, 20 May 2010) [~]b...@izar% echo $MAKEOBJDIRPREFIX /home/bsam/FreeBSD/base/head/obj [~]b...@izar% sudo make -C FreeBSD/base/head/src installkernel -- >>> Installing kernel -- cd /usr/obj/usr/home/bsam/FreeBSD/base/head/src/sys/IZAR; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 CPUTYPE= GROFF_BIN_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/bin GROFF_FONT_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/share/tmac PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/sbin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/bin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/games:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/sbin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/bin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make KERNEL=kernel install cd: can't cd to /usr/obj/usr/home/bsam/FreeBSD/base/head/src/sys/IZAR *** Error code 2 Stop in /usr/home/bsam/FreeBSD/base/head/src. *** Error code 1 Stop in /usr/home/bsam/FreeBSD/base/head/src. [~]b...@izar% - That command used to work fine for years... -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: MAKEOBJDIRPREFIX and installkernel
On Thu, 20 May 2010 22:58:00 +0400 Yuri Pankov wrote: > On Thu, May 20, 2010 at 09:59:25PM +0400, Boris Samorodov wrote: > > Hi List, > > > > here is something strange with current CURRENT: > > - > > [~]b...@izar% LANG=C svn info FreeBSD/base/head/src > > Path: FreeBSD/base/head/src > > URL: svn+ssh://svn.freebsd.org/base/head > > Repository Root: svn+ssh://svn.freebsd.org/base > > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > > Revision: 208354 > > Node Kind: directory > > Schedule: normal > > Last Changed Author: jkim > > Last Changed Rev: 208353 > > Last Changed Date: 2010-05-20 20:24:12 +0400 (Thu, 20 May 2010) > > > > [~]b...@izar% echo $MAKEOBJDIRPREFIX > > /home/bsam/FreeBSD/base/head/obj > > > > [~]b...@izar% sudo make -C FreeBSD/base/head/src installkernel > > -- > > >>> Installing kernel > > -- > > cd /usr/obj/usr/home/bsam/FreeBSD/base/head/src/sys/IZAR; > > MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 CPUTYPE= > > GROFF_BIN_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/bin > > > > GROFF_FONT_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/share/groff_font > > > > GROFF_TMAC_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/share/tmac > > > > PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/sbin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/bin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/games:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/sbin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/bin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin > > make KERNEL=kernel install > > cd: can't cd to /usr/obj/usr/home/bsam/FreeBSD/base/head/src/sys/IZAR > > *** Error code 2 > > > > Stop in /usr/home/bsam/FreeBSD/base/head/src. > > *** Error code 1 > > > > Stop in /usr/home/bsam/FreeBSD/base/head/src. > > [~]b...@izar% > > - > > > > That command used to work fine for years... > Works here. May you've recently changed your sudoers to not keep env > variables? Hm. I've upgraded ports recently. However sudoers is the same. Thanks for the tip. I'll try to find out what has changed at my system. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: Importing clang/LLVM into FreeBSD HEAD
On Tue, 01 Jun 2010 23:36:25 +0200 Dag-Erling Smørgrav wrote: > Roman Divacky writes: > > I would like to propose to integrate clang/LLVM into FreeBSD HEAD > > in the near future (days, not weeks). > +1 +1 -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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"
[bsdtar] strange compression with ^T command
Hi! - % uname -a FreeBSD host.ipt.ru 9.0-CURRENT FreeBSD 9.0-CURRENT #4 r208799: Fri Jun 4 13:58:47 MSD 2010 b...@host.ipt.ru:/storage/obj/storage/src/sys/HOST i386 % make extract ===> Vulnerability check disabled, database not found ===> License check disabled, port has not defined LICENSE ===> Extracting for eric5-5.0.0 => No checksum file (/m/home/bsam/shared/FreeBSD/exp/eric5/devel/eric5/distinfo). load: 6.85 cmd: bsdtar 68052 [runnable] 131.55r 0.03u 0.30s 0% 2044k In: 17512980 bytes, compression 1290122025%; Out: 1502 files, 17509012 bytes Current: eric5-5.0.0-RC1/eric/icons/default/drawEraser.png (1172 bytes) load: 6.96 cmd: gzip 68051 [pipdwt] 150.90r 0.16u 0.00s 0% 1052k In: 24466168 bytes, compression -1782936608%; Out: 1821 files, 24460918 bytes Current: eric5-5.0.0-RC1/eric/E5Gui/E5SingleApplication.py (4726 bytes) % - One can get the file to experiment: - % fetch http://heanet.dl.sourceforge.net/project/eric-ide/eric5/stable/5.0.0-RC1/eric5-5.0.0-RC1.tar.gz - Extracted files seems to be OK. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: [bsdtar] strange compression with ^T command
On Sun, 13 Jun 2010 19:58:51 -0700 Tim Kientzle wrote: > Thanks for the report! This was caused by an > overflow in the compression calculation when the "in" > bytes was larger than the "out" bytes. > I just committed a fix as r209152. Yep, it works. Thanks for the quick fix! > Tim > Boris Samorodov wrote: > > Hi! > > > > - > > % uname -a > > FreeBSD host.ipt.ru 9.0-CURRENT FreeBSD 9.0-CURRENT #4 r208799: Fri Jun 4 > > 13:58:47 MSD 2010 b...@host.ipt.ru:/storage/obj/storage/src/sys/HOST > > i386 > > > > % make extract > > ===> Vulnerability check disabled, database not found > > ===> License check disabled, port has not defined LICENSE > > ===> Extracting for eric5-5.0.0 > > => No checksum file > > (/m/home/bsam/shared/FreeBSD/exp/eric5/devel/eric5/distinfo). > > load: 6.85 cmd: bsdtar 68052 [runnable] 131.55r 0.03u 0.30s 0% 2044k > > In: 17512980 bytes, compression 1290122025%; Out: 1502 files, 17509012 > > bytes > > Current: eric5-5.0.0-RC1/eric/icons/default/drawEraser.png (1172 bytes) > > load: 6.96 cmd: gzip 68051 [pipdwt] 150.90r 0.16u 0.00s 0% 1052k > > In: 24466168 bytes, compression -1782936608%; Out: 1821 files, 24460918 > > bytes > > Current: eric5-5.0.0-RC1/eric/E5Gui/E5SingleApplication.py (4726 bytes) > > % > > - > > > > One can get the file to experiment: > > - > > % fetch > > http://heanet.dl.sourceforge.net/project/eric-ide/eric5/stable/5.0.0-RC1/eric5-5.0.0-RC1.tar.gz > > - > > > > Extracted files seems to be OK. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: make packages fails recent -current
On 11.09.2018 16:20, Andreas Nilsson wrote: On Mon, Sep 10, 2018 at 5:55 PM Mikaël Urankar wrote: 2018-09-10 17:45 GMT+02:00 Andreas Nilsson : Hello, I have for about a week been trying to get new (base)packages built. make buildworld/buildkernel works as expected, however make packages has been failing: ===> Creating FreeBSD-runtime-12.0.s20180910124534 pkg: duplicate directory listing: /boot, ignoring pkg: duplicate directory listing: /etc, ignoring ... pkg: duplicate directory listing: /etc/syslog.d, ignoring pkg: duplicate directory listing: /root, ignoring pkg: duplicate directory listing: /root, ignoring pkg: duplicate directory listing: /root, ignoring pkg: Plist error, @config /root/.cshrc: not a regular file pkg: Plist error, @config /root/.profile: not a regular file pkg: duplicate file listing: /usr/bin/zstdegrep, ignoring pkg: duplicate directory listing: /usr/lib, ignoring pkg: duplicate directory listing: /usr/lib/dtrace, ignoring pkg: duplicate directory listing: /usr/lib/dtrace, ignoring pkg: duplicate directory listing: /usr/lib32, ignoring ... Is anyone else seeing this? This is on git 4e22ee37542 . I use metamode for building. I'm currently building from scratch just to rule out metamode. See https://lists.freebsd.org/pipermail/freebsd-pkgbase/2018-September/000383.html Thanks, that would explain it. Although even after installing pkg-devel-1.10.99.8 it still fails. Guess I'll have to wait for it to trickle into the packages. The rev. 479255 was an update to version 1.10.99.9. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serv ___ 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"
base packages and 12 -> 13 upgrade
Hi All, A have a base package server and upgraded some of my home servers to use base packages. Now when the package builder builds packages for 13-current, what is the procedure to upgrade base packages from 12 to 13? Whenever I try to install/upgrade packages I get: --- pkg-static: wrong architecture: FreeBSD:13:amd64 instead of FreeBSD:12:amd64 pkg-static: repository FreeBSD-base contains packages with wrong ABI: FreeBSD:13:amd64 --- -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: base packages and 12 -> 13 upgrade
On 03.11.2018 18:05, Mikaël Urankar wrote: Le sam. 3 nov. 2018 à 15:45, Boris Samorodov a écrit : Hi All, A have a base package server and upgraded some of my home servers to use base packages. Now when the package builder builds packages for 13-current, what is the procedure to upgrade base packages from 12 to 13? Whenever I try to install/upgrade packages I get: --- pkg-static: wrong architecture: FreeBSD:13:amd64 instead of FreeBSD:12:amd64 pkg-static: repository FreeBSD-base contains packages with wrong ABI: FreeBSD:13:amd64 I think you need to do something like that: env ABI=FreeBSD:13:amd64 pkg update env ABI=FreeBSD:13:amd64 pkg upgrade Yep! That was it. Thank you. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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 13.0-CURRENT r346362 + webcamd -- no /dev/video*
Hi All, I use a fresh FreeBSD-current system and webcamd but get no /dev/video* device: - %uname -a FreeBSD latt.bsnet 13.0-CURRENT FreeBSD 13.0-CURRENT r346362 PKG64X amd64 % ls -l /dev/cuse crw-rw 1 root operator 0x77 21 апр. 18:04 /dev/cuse % pkg info -x webcamd webcamd-4.20.0.1_2 % ps auwx | grep webcamd root833 0,0 0,0 20560 8108 - Shttps://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD 13.0-CURRENT r346362 + webcamd -- no /dev/video*
Hi Damjan and aLL! 21.04.2019 19:54, Damjan Jovanovic пишет: > On Sun, Apr 21, 2019 at 5:51 PM Boris Samorodov wrote: > >> Hi All, >> >> I use a fresh FreeBSD-current system and webcamd but get no /dev/video* >> device: >> - >> %uname -a >> FreeBSD latt.bsnet 13.0-CURRENT FreeBSD 13.0-CURRENT r346362 PKG64X amd64 >> >> % ls -l /dev/cuse >> crw-rw 1 root operator 0x77 21 апр. 18:04 /dev/cuse >> >> % pkg info -x webcamd >> webcamd-4.20.0.1_2 >> >> % ps auwx | grep webcamd >> root833 0,0 0,0 20560 8108 - S> /usr/local/sbin/webcamd -i 0 -d ugen0.5 -H -B -U webcamd -G webcamd >> >> % webcamd >> [...] >> webcamd [-d ugen0.5] -N >> GenesysLogic-Technology-Co---Ltd--USB2-0-UVC-PC-Camera -S unknown -M 0 >> >> % ls -l /dev/video* >> ls: /dev/video: No such file or directory >> >> % pwcview >> Failed to access webcam: No such file or directory >> *** >> Make sure you have connected your webcam to the root hub >> or to a USB 1.1 hub, also check your dmesg for any errors. >> *** >> >> >> Any help is appreciated. Thank you. >> >> -- >> >> > I was doing some webcamd development just a few days ago and might be able > to help. > > Does your camera work in Linux? If so, on what version? Interesting question! I've just tried lubuntu 18.04.2 and it works fine. -- WBR, bsam ___ 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"
[RESOLVED] Re: FreeBSD 13.0-CURRENT r346362 + webcamd -- no /dev/video*
Hi All, The problem is resolved with the help of Tom Rushworth (via private emails) by starting hald. I had not run it and this dependency is noted at WEBCAMD(8) neither. Hope this info may be helpful. 21.04.2019 18:48, Boris Samorodov пишет: > Hi All, > > I use a fresh FreeBSD-current system and webcamd but get no /dev/video* > device: > - > %uname -a > FreeBSD latt.bsnet 13.0-CURRENT FreeBSD 13.0-CURRENT r346362 PKG64X amd64 > > % ls -l /dev/cuse > crw-rw 1 root operator 0x77 21 апр. 18:04 /dev/cuse > > % pkg info -x webcamd > webcamd-4.20.0.1_2 > > % ps auwx | grep webcamd > root833 0,0 0,0 20560 8108 - S /usr/local/sbin/webcamd -i 0 -d ugen0.5 -H -B -U webcamd -G webcamd > > % webcamd > [...] > webcamd [-d ugen0.5] -N > GenesysLogic-Technology-Co---Ltd--USB2-0-UVC-PC-Camera -S unknown -M 0 > > % ls -l /dev/video* > ls: /dev/video: No such file or directory > > % pwcview > Failed to access webcam: No such file or directory > *** > Make sure you have connected your webcam to the root hub > or to a USB 1.1 hub, also check your dmesg for any errors. > *** > > > Any help is appreciated. Thank you. > ___ 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: upgrading current -> graphics bug
07.03.2015 19:07, David S пишет: >> FWIW the nVidia driver docs indicate that you should >> comment, or remove the reference to dri in xorg.conf >> #Load "dri" >> but that dri2 is fine. Don't know that that has anything to >> do with your issue. But thought I'd mention it FWIW. > > thanks, i missed that part. i took it out of xorg.conf and will see > next time i upgrade if it helps. I'm not sure why this step is recommended, because dri is auto-loaded anyway: - [41.540] (II) LoadModule: "dri" [41.541] (II) Loading /usr/local/lib/xorg/modules/extensions/libdri.so [41.569] (II) Module dri: vendor="X.Org Foundation" [41.569]compiled for 1.12.4, module version = 1.0.0 [41.569]ABI class: X.Org Server Extension, version 6.0 [41.569] (II) Loading extension XFree86-DRI [41.569] (II) LoadModule: "dri2" [41.570] (II) Loading /usr/local/lib/xorg/modules/extensions/libdri2.so [41.582] (II) Module dri2: vendor="X.Org Foundation" [41.582]compiled for 1.12.4, module version = 1.2.0 [41.582]ABI class: X.Org Server Extension, version 6.0 [41.582] (II) Loading extension DRI2 [41.582] (II) LoadModule: "nvidia" [41.582] (II) Loading /usr/local/lib/xorg/modules/drivers/nvidia_drv.so [41.720] (II) Module nvidia: vendor="NVIDIA Corporation" [41.720]compiled for 4.0.2, module version = 1.0.0 [41.720]Module class: X.Org Video Driver [41.818] (II) NVIDIA dlloader X Driver 304.123 Wed Jul 2 10:50:21 PDT 2014 - -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: [HEADSUP] OpenSSL updated to 1.0.2d
30.10.2015 23:57, Jung-uk Kim пишет: > OpenSSL on head has been updated to 1.0.2d. Please make sure to > recompile all binaries depending on libcrypto.so.7 or libssl.so.7. Great, thanks! How do those who use FreeBSD official packages supposed to upgrade packages? -- WBR, bsam ___ 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: [HEADSUP] OpenSSL updated to 1.0.2d
02.11.2015 06:05, Jason Unovitch пишет: > On Nov 1, 2015 10:06 AM, "Boris Samorodov" wrote: >> 30.10.2015 23:57, Jung-uk Kim пишет: >> >>> OpenSSL on head has been updated to 1.0.2d. Please make sure to >>> recompile all binaries depending on libcrypto.so.7 or libssl.so.7. >> >> Great, thanks! >> >> How do those who use FreeBSD official packages supposed to upgrade >> packages? > > This is on head so it should be the same process as any other source based > upgrade per the handbook. > > https:// <https://www.freebsd.org/doc/handbook/makeworld.html> > www.freebsd.org <https://www.freebsd.org/doc/handbook/makeworld.html> > /doc/handbook/ <https://www.freebsd.org/doc/handbook/makeworld.html> > makeworld.html <https://www.freebsd.org/doc/handbook/makeworld.html> > > The 'make delete-old-libs' step would have to wait until after the official > 11-CURRENT package builders have been updated to a revision after this > change and a 'pkg upgrade' installs everything from that build. Jason, thanks. Seems that "pkg upgrade -f" should DTRT. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: 11.0-CURRENT r290273: installer fails with "out of swap space" error
03.11.2015 23:50, Maxim Pugachev пишет: > I tried to install r29273 into Parallels VM, but got an error on > "distextract" stage. Here is the last messages from bsdinstall_log: > > DEBUG: f_debug_init: ARGV=[distextract] GETOPTS_STDARGS=[dD:] > DEBUG: f_debug_init: debug=[1] debugFile=[/tmp/bsdinstall_log] > DEBUG: Running installation step: distextract > Killed > > Last message from /var/log/messages: > > Nov 3 20:02:9 kernel: pid 967 (distextract), uid 0, was killed: out > of swap space > > My VM has 2 gigs of memory, vmstat tells that I have ~537M free > (swapinfo tells nothing). I dunno is it a bug or I'm doing something > wrong. I've also come across with this recently. Don't remember all the details, something like this: . install CURRENT to bhyve using 1G memory, get out of swap error; . set 2G memory, got the same error, didn't try more memory (seemed not sane to). Took a look at the boot environment and found out that something was wrong (with the filesystem). Unfortunately, I do not recall now what was it. :-( Something like too small /tmp, no /tmp at all, something else... But definitely the error message was misleading and not the case of the failure. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: Panic while waiting on wlan0
22.11.15 22:54, Sergey Manucharian пишет: >> On 22 November 2015 at 04:31, Florian Limberger >> wrote: >>> On 17.11.15 17:42, Adrian Chadd wrote: try updating to head as of today. Some callout issues were fixed. >>> >>> The crashes are fixed alright, thank you. I still have a rather difficult >>> to reproduce issue, where the wpa_supplicant hangs in SCANNING state >>> indefinitely, even if the Notebook is very near to the AP. I’ve had this >>> issue occasionally before, but since the crashes started it has become more >>> frequent. Is there anything I can do to debug the behaviour? Until now I >>> have only observed it in wpa_supplicant and have no idea how I might >>> proceed. >>> >> Excerpts from Adrian Chadd's message from Sun 22-Nov-15 08:52: >> >> Do this: >> >> * compile in IEEE80211_DEBUG; >> * do "wlandebug +scan" >> >> That way we can see if net80211 is refusing to continue scanning. > > I have a similar well-reproducable crash on my ThinkPad with "iwn" > driver and "iwn6000fw" when I try to restart wlan: > > # service netif restart > > Otherwise it works fine, no problem at all. After upgrade from FreeBSD-amd64-HEAD-r290730 to r291148 I've got a panic with wlan0 (iwm though): ftp://ftp.wart.ru/pub/misc/panic-iwn-1.jpg ftp://ftp.wart.ru/pub/misc/panic-iwn-2.jpg % kldstat | grep iwm 121 0x822c5000 21a18if_iwm.ko 131 0x822e7000 ab9e0iwm7265fw.ko -- WBR, bsam ___ 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: Panic while waiting on wlan0
Hi!, 23.11.15 01:38, Adrian Chadd пишет: > hi, > > iwm needs a maintainer and a lot of work. :) Agreed. :-) WTB, I've just upgraded to r291221 and this seems to fix those problems. > On 22 November 2015 at 13:46, Boris Samorodov wrote: >> 22.11.15 22:54, Sergey Manucharian пишет: >>>> On 22 November 2015 at 04:31, Florian Limberger >>>> wrote: >>>>> On 17.11.15 17:42, Adrian Chadd wrote: >>>>>> >>>>>> try updating to head as of today. Some callout issues were fixed. >>>>> >>>>> The crashes are fixed alright, thank you. I still have a rather difficult >>>>> to reproduce issue, where the wpa_supplicant hangs in SCANNING state >>>>> indefinitely, even if the Notebook is very near to the AP. I’ve had this >>>>> issue occasionally before, but since the crashes started it has become >>>>> more >>>>> frequent. Is there anything I can do to debug the behaviour? Until now I >>>>> have only observed it in wpa_supplicant and have no idea how I might >>>>> proceed. >>>>> >>>> Excerpts from Adrian Chadd's message from Sun 22-Nov-15 08:52: >>>> >>>> Do this: >>>> >>>> * compile in IEEE80211_DEBUG; >>>> * do "wlandebug +scan" >>>> >>>> That way we can see if net80211 is refusing to continue scanning. >>> >>> I have a similar well-reproducable crash on my ThinkPad with "iwn" >>> driver and "iwn6000fw" when I try to restart wlan: >>> >>> # service netif restart >>> >>> Otherwise it works fine, no problem at all. >> >> After upgrade from FreeBSD-amd64-HEAD-r290730 to r291148 I've got a >> panic with wlan0 (iwm though): >> ftp://ftp.wart.ru/pub/misc/panic-iwn-1.jpg >> ftp://ftp.wart.ru/pub/misc/panic-iwn-2.jpg >> >> % kldstat | grep iwm >> 121 0x822c5000 21a18if_iwm.ko >> 131 0x822e7000 ab9e0iwm7265fw.ko -- WBR, bsam ___ 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"
11.0-CURRENT-amd64 r293444: bhyveload => Segmentation fault
Hi All, Bhyve works with virtual machines which have already been created, but can not create new ones: - # bhyveload -m 4G -d /vm/.iso/FreeBSD-11.0-CURRENT-amd64-20151130-r291495-disc1.iso test Consoles: userboot FreeBSD/amd64 User boot, Revision 1.1 (bsam@sm.bsnet, Sat Jan 9 02:04:09 MSK 2016) Segmentation fault (core dumped) - Any help is appreciated. Thank you. -- WBR, bsam ___ 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: 11.0-CURRENT-amd64 r293444: bhyveload => Segmentation fault
09.01.16 23:51, Allan Jude пишет: > On 2016-01-09 15:48, Boris Samorodov wrote: >> Hi All, >> >> Bhyve works with virtual machines which have already been created, >> but can not create new ones: >> - >> # bhyveload -m 4G -d >> /vm/.iso/FreeBSD-11.0-CURRENT-amd64-20151130-r291495-disc1.iso test >> >> >> Consoles: userboot >> >> FreeBSD/amd64 User boot, Revision 1.1 >> (bsam@sm.bsnet, Sat Jan 9 02:04:09 MSK 2016) >> Segmentation fault (core dumped) >> - >> >> Any help is appreciated. >> Thank you. >> > > This was a but I accidentally introduced during the ZFS boot environment > work. It has been fixed in head already, just update and rebuild > sys/boot/userboot Great, thank you! Quick "svn up /usr/src && cd /sys/boot/userboot && make && sudo make install" didn't help, but backtrace of core has changed. I'll try a full rebuild. -- WBR, bsam ___ 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: 11.0-CURRENT-amd64 r293444: bhyveload => Segmentation fault
10.01.16 00:39, Allan Jude пишет: > On 2016-01-09 16:20, Boris Samorodov wrote: >> 09.01.16 23:51, Allan Jude пишет: >>> On 2016-01-09 15:48, Boris Samorodov wrote: >>>> Hi All, >>>> >>>> Bhyve works with virtual machines which have already been created, >>>> but can not create new ones: >>>> - >>>> # bhyveload -m 4G -d >>>> /vm/.iso/FreeBSD-11.0-CURRENT-amd64-20151130-r291495-disc1.iso test >>>> >>>> >>>> Consoles: userboot >>>> >>>> FreeBSD/amd64 User boot, Revision 1.1 >>>> (bsam@sm.bsnet, Sat Jan 9 02:04:09 MSK 2016) >>>> Segmentation fault (core dumped) >>>> - >>>> >>>> Any help is appreciated. >>>> Thank you. >>>> >>> >>> This was a but I accidentally introduced during the ZFS boot environment >>> work. It has been fixed in head already, just update and rebuild >>> sys/boot/userboot >> >> Great, thank you! >> >> Quick "svn up /usr/src && cd /sys/boot/userboot && make && sudo make >> install" didn't help, but backtrace of core has changed. I'll try a >> full rebuild. > > Can you provide the backtrace? I've landed the machine to another person/task. After it finishes it will auto-refresh the world. If core is reproduced, I'll send it to you. Thank you for you help and fast responses! -- WBR, bsam ___ 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: 11.0-CURRENT-amd64 r293444: bhyveload => Segmentation fault
10.01.16 01:07, Boris Samorodov пишет: > 10.01.16 00:39, Allan Jude пишет: >> On 2016-01-09 16:20, Boris Samorodov wrote: >>> 09.01.16 23:51, Allan Jude пишет: >>>> On 2016-01-09 15:48, Boris Samorodov wrote: >>>>> Hi All, >>>>> >>>>> Bhyve works with virtual machines which have already been created, >>>>> but can not create new ones: >>>>> - >>>>> # bhyveload -m 4G -d >>>>> /vm/.iso/FreeBSD-11.0-CURRENT-amd64-20151130-r291495-disc1.iso test >>>>> >>>>> >>>>> Consoles: userboot >>>>> >>>>> FreeBSD/amd64 User boot, Revision 1.1 >>>>> (bsam@sm.bsnet, Sat Jan 9 02:04:09 MSK 2016) >>>>> Segmentation fault (core dumped) >>>>> - >>>>> >>>>> Any help is appreciated. >>>>> Thank you. >>>>> >>>> >>>> This was a but I accidentally introduced during the ZFS boot environment >>>> work. It has been fixed in head already, just update and rebuild >>>> sys/boot/userboot >>> >>> Great, thank you! >>> >>> Quick "svn up /usr/src && cd /sys/boot/userboot && make && sudo make >>> install" didn't help, but backtrace of core has changed. I'll try a >>> full rebuild. >> >> Can you provide the backtrace? > > I've landed the machine to another person/task. After it finishes it > will auto-refresh the world. If core is reproduced, I'll send it to you. OK, I reproduced the core. It was my fault: vm-bhyve install command should be used with just the name of the iso. While I tried to use the absolute path and got a core. > Thank you for you help and fast responses! -- WBR, bsam ___ 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: extremely slow to get to loader
24.04.16 20:46, Larry Rosenman пишет: > On 2016-04-21 20:56, Johannes Dieterich wrote: >> On Thu, Apr 21, 2016 at 12:16 PM, Allan Jude >> wrote: >>> On 2016-04-21 10:46, Johannes Dieterich wrote: >>>> Dear all, >>>> >>>> with r298385, I observe extremely long times from turning on my laptop >>>> to reach loader. This is a regression compared to a roughly 1 week old >>>> CURRENT. >>>> >>>> This is an AMD A12-8800B laptop booting in legacy mode into a >>>> ZFS+GELI setup. >>>> >>>> Please let me know how I can help to solve this issue. >>>> >>>> Thanks, >>>> >>>> Johannes >>>> ___ >>>> 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" >>>> >>> >>> Can you describe where exactly it is slow? >> Yes, it hangs after "BIOS drive C: is disk 0" for a good 3 minutes >> before it eventually continues. >> >>> Once you get to the loader menu (the beastie menu), can you choose the >>> option to go to the loader prompt, and type: >>> bcachestat >>> >>> And provide the output of that. >> Here we go (w/o mistakes I hope...): >> cache blocks: 32768 >> cache blocksz: 572 >> unit cache blocks: 32768 >> cached units: 1 >> 1162 ops 0 bypasses 12109 hits 739 misses >> >> Thanks so much for the response! >> >> Johannes > I'm seeing similar, PLUS the kernel seems(!) to not continue on to the > RC scripts > after mount root. > > (BIOS BOOT). > > I reverted to an older kernel and boot block and zfsloader to get up. > > Seems, I'm at the same boat. The system is a remote Supermicro server: --- ping after reboot --- % ping -i 60 srv PING srv (X.X.X.X): 56 data bytes 64 bytes from X.X.X.X: icmp_seq=0 ttl=59 time=2.526 ms 64 bytes from X.X.X.X: icmp_seq=14 ttl=59 time=2.735 ms --- dmesg messages --- [...] Apr 27 14:59:34 srv shutdown: reboot by bsam: Apr 27 14:59:35 srv kernel: . Apr 27 14:59:56 srv syslogd: exiting on signal 15 Apr 27 15:12:33 srv syslogd: kernel boot file is /boot/kernel/kernel Apr 27 15:12:33 srv kernel: Copyright (c) 1992-2016 The FreeBSD Project. Apr 27 15:12:33 srv kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Apr 27 15:12:33 srv kernel: The Regents of the University of California. All rights reserved. Apr 27 15:12:33 srv kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Apr 27 15:12:33 srv kernel: FreeBSD 11.0-CURRENT #41 r298696: Wed Apr 27 14:50:53 MSK 2016 [...] -- This is a zfs-root system with geli-enabled swap partitions. Other than boot the system seem to be fine. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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"
no smtp service after upgrade
Hi All,
There is no smtp service after recent update:
-
% sockstat -4l
USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN
ADDRESS
root sshd 879 4 tcp4 *:22 *:*
root syslogd663 7 udp4 *:514 *:*
-
I use (almost) default mail configuration.
-
% grep mail /etc/rc.conf{,.local}
%
-
I've notice a huge etc updates at update. Seems they may be related.
--
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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: no smtp service after upgrade
27.04.16 17:08, Chagin Dmitry пишет:
> On Wed, Apr 27, 2016 at 04:34:29PM +0300, Boris Samorodov wrote:
>> Hi All,
>>
>> There is no smtp service after recent update:
>> -
>> % sockstat -4l
>> USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN
>> ADDRESS
>> root sshd 879 4 tcp4 *:22 *:*
>> root syslogd663 7 udp4 *:514 *:*
>> -
>>
>> I use (almost) default mail configuration.
>> -
>> % grep mail /etc/rc.conf{,.local}
>> %
>> -
>>
>> I've notice a huge etc updates at update. Seems they may be related.
>>
> the same here, chmod +x /etc/rc.d/sendmail
Yep. Thanks!
--
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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: extremely slow to get to loader
27.04.16 16:30, Allan Jude пишет: > On April 27, 2016 2:50:13 PM GMT+02:00, Boris Samorodov > wrote: >> 24.04.16 20:46, Larry Rosenman пишет: >>> On 2016-04-21 20:56, Johannes Dieterich wrote: >>>> On Thu, Apr 21, 2016 at 12:16 PM, Allan Jude >>>> wrote: >>>>> On 2016-04-21 10:46, Johannes Dieterich wrote: >>>>>> Dear all, >>>>>> >>>>>> with r298385, I observe extremely long times from turning on my >> laptop >>>>>> to reach loader. This is a regression compared to a roughly 1 week >> old >>>>>> CURRENT. >>>>>> >>>>>> This is an AMD A12-8800B laptop booting in legacy mode into a >>>>>> ZFS+GELI setup. >>>>>> >>>>>> Please let me know how I can help to solve this issue. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Johannes >>>>>> ___ >>>>>> 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" >>>>>> >>>>> >>>>> Can you describe where exactly it is slow? >>>> Yes, it hangs after "BIOS drive C: is disk 0" for a good 3 minutes >>>> before it eventually continues. >>>> >>>>> Once you get to the loader menu (the beastie menu), can you choose >> the >>>>> option to go to the loader prompt, and type: >>>>> bcachestat >>>>> >>>>> And provide the output of that. >>>> Here we go (w/o mistakes I hope...): >>>> cache blocks: 32768 >>>> cache blocksz: 572 >>>> unit cache blocks: 32768 >>>> cached units: 1 >>>> 1162 ops 0 bypasses 12109 hits 739 misses >>>> >>>> Thanks so much for the response! >>>> >>>> Johannes >>> I'm seeing similar, PLUS the kernel seems(!) to not continue on to >> the >>> RC scripts >>> after mount root. >>> >>> (BIOS BOOT). >>> >>> I reverted to an older kernel and boot block and zfsloader to get up. >>> >>> >> Seems, I'm at the same boat. The system is a remote Supermicro server: >> --- ping after reboot --- >> % ping -i 60 srv >> PING srv (X.X.X.X): 56 data bytes >> 64 bytes from X.X.X.X: icmp_seq=0 ttl=59 time=2.526 ms >> 64 bytes from X.X.X.X: icmp_seq=14 ttl=59 time=2.735 ms >> --- dmesg messages --- >> [...] >> Apr 27 14:59:34 srv shutdown: reboot by bsam: >> Apr 27 14:59:35 srv kernel: . >> Apr 27 14:59:56 srv syslogd: exiting on signal 15 >> Apr 27 15:12:33 srv syslogd: kernel boot file is /boot/kernel/kernel >> Apr 27 15:12:33 srv kernel: Copyright (c) 1992-2016 The FreeBSD >> Project. >> Apr 27 15:12:33 srv kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, >> 1989, 1991, 1992, 1993, 1994 >> Apr 27 15:12:33 srv kernel: The Regents of the University of >> California. >> All rights reserved. >> Apr 27 15:12:33 srv kernel: FreeBSD is a registered trademark of The >> FreeBSD Foundation. >> Apr 27 15:12:33 srv kernel: FreeBSD 11.0-CURRENT #41 r298696: Wed Apr >> 27 >> 14:50:53 MSK 2016 >> [...] >> -- >> >> This is a zfs-root system with geli-enabled swap partitions. >> Other than boot the system seem to be fine. > > Please try https://reviews.freebsd.org/D6109 and see if it fixes the problem. Yep, fixed. Thank you! -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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 broken on VMWare somewhere between r300069 and r300176
19.05.16 09:28, K. Macy пишет: > I did an IFC on my drm-next-4.6 branch yesterday at r300069. I just > did an IFC to r300176 and boot will hang right ater printing out > "setting hostid: ". ^T just shows sh [piperd]. ddb just shows the > shell as hanging in piperead. Diffing between those two revisions I > don't see any obvious offenders so I'm hoping that individuals who > have committed in the last 24 hours will have some idea of their > changes having such an impact. For me (BIOS boot at DELL notebook) is broken after jump from r300062 to r300158. CapsLock works, but ^T shows nothing. Here is a photo (sorry for the quality): ftp://ftp.wart.ru/pub/misc/boot_broken.jpg Boot with r300062 works fine. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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 broken on VMWare somewhere between r300069 and r300176
19.05.16 14:05, Konstantin Belousov пишет: > On Thu, May 19, 2016 at 01:50:47PM +0300, Boris Samorodov wrote: >> 19.05.16 09:28, K. Macy пишет: >>> I did an IFC on my drm-next-4.6 branch yesterday at r300069. I just >>> did an IFC to r300176 and boot will hang right ater printing out >>> "setting hostid: ". ^T just shows sh [piperd]. ddb just shows the >>> shell as hanging in piperead. Diffing between those two revisions I >>> don't see any obvious offenders so I'm hoping that individuals who >>> have committed in the last 24 hours will have some idea of their >>> changes having such an impact. >> >> For me (BIOS boot at DELL notebook) is broken after jump >> from r300062 to r300158. CapsLock works, but ^T shows nothing. >> Here is a photo (sorry for the quality): >> ftp://ftp.wart.ru/pub/misc/boot_broken.jpg >> >> Boot with r300062 works fine. > > Break into ddb and show the 'ps' command output. Here are some photoes: ftp://ftp.wart.ru/pub/misc/Boot/ Notes: 1. The third one is none-readable. :-( I'll redo it if needed (but not right now). 2. The last but one screens are nearly identical (modulo integers) and were skipped. BTW, if detach all devices from the notebook (external screen, wired network, usb extentions) the notebook can boot ones out of 10 times. HTH -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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 broken on VMWare somewhere between r300069 and r300176
19.05.16 14:04, Andriy Gapon пишет: > On 19/05/2016 13:50, Boris Samorodov wrote: >> 19.05.16 09:28, K. Macy пишет: >>> I did an IFC on my drm-next-4.6 branch yesterday at r300069. I just >>> did an IFC to r300176 and boot will hang right ater printing out >>> "setting hostid: ". ^T just shows sh [piperd]. ddb just shows the >>> shell as hanging in piperead. Diffing between those two revisions I >>> don't see any obvious offenders so I'm hoping that individuals who >>> have committed in the last 24 hours will have some idea of their >>> changes having such an impact. >> >> For me (BIOS boot at DELL notebook) is broken after jump >> from r300062 to r300158. CapsLock works, but ^T shows nothing. >> Here is a photo (sorry for the quality): >> ftp://ftp.wart.ru/pub/misc/boot_broken.jpg >> >> Boot with r300062 works fine. > > A wild guess (not really), try to revert r300113 Tried that, conflict on reverting this single revision and an error compiling kernel. (No more details, sorry, busy at work for now) -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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 broken on VMWare somewhere between r300069 and r300176
19.05.16 16:43, Andriy Gapon пишет: > On 19/05/2016 16:40, Boris Samorodov wrote: >> 19.05.16 14:04, Andriy Gapon пишет: >>> On 19/05/2016 13:50, Boris Samorodov wrote: >>>> 19.05.16 09:28, K. Macy пишет: >>>>> I did an IFC on my drm-next-4.6 branch yesterday at r300069. I just >>>>> did an IFC to r300176 and boot will hang right ater printing out >>>>> "setting hostid: ". ^T just shows sh [piperd]. ddb just shows the >>>>> shell as hanging in piperead. Diffing between those two revisions I >>>>> don't see any obvious offenders so I'm hoping that individuals who >>>>> have committed in the last 24 hours will have some idea of their >>>>> changes having such an impact. >>>> >>>> For me (BIOS boot at DELL notebook) is broken after jump >>>> from r300062 to r300158. CapsLock works, but ^T shows nothing. >>>> Here is a photo (sorry for the quality): >>>> ftp://ftp.wart.ru/pub/misc/boot_broken.jpg >>>> >>>> Boot with r300062 works fine. >>> >>> A wild guess (not really), try to revert r300113 >> >> Tried that, conflict on reverting this single revision and an error >> compiling kernel. (No more details, sorry, busy at work for now) >> > > Alexander has committed a fix, so upgrading to the latest version can be a > better strategy now. Yep, I've updated the kernel to r300212 and it works. Thanks all! -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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"
should aarch64 cross-build work at amd64?
Hi All! I've just created an armv6 jail by poudriere at FreeBSD-current-amd64. It works fine: --- % poudriere jail -l JAILNAME VERSION ARCH METHOD TIMESTAMP PATH HEAD-armv6 12.0-CURRENT r306267 arm.armv6 svn+https2016-09-23 17:38:10 /poudriere/jails/HEAD-armv6 --- Then I tried to create an aarch64 jail which failed. Should it work? - % uname -a FreeBSD bb055.bsnet 12.0-CURRENT FreeBSD 12.0-CURRENT #19 r306268: Fri Sep 23 20:13:21 MSK 2016 bsam@bb055.bsnet:/usr/obj/usr/src/sys/BB64X amd64 % sudo binmiscctl lookup aarch64 name: aarch64 interpreter: /usr/local/bin/qemu-aarch64-static flags: ENABLED USE_MASK magic size: 20 magic offset: 0 magic: 0x7f 0x45 0x4c 0x46 0x02 0x01 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x02 0x00 0xb7 0x00 mask: 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xfe 0xff 0xff 0xff % sudo poudriere jail -c -j HEAD-aarch64 -a arm.aarch64 -v head -m svn+https -J 8 [00:00:00] >> Cross-building ports for arm.aarch64 on amd64 requires QEMU [00:00:00] >> Creating HEAD-aarch64 fs... done [00:00:00] >> Checking out the sources from svn... done [00:03:32] >> Starting make buildworld with 8 jobs --- buildworld --- make[1]: /poudriere/jails/HEAD-aarch64/usr/src/Makefile.inc1 line 146: SYSTEM_COMPILER: Determined that CC=cc matches the source tree. Not bootstrapping a cross-compiler. make[1]: /poudriere/jails/HEAD-aarch64/usr/src/Makefile.inc1 line 177: In-tree binutils does not support the aarch64 architecture. Install the aarch64-binutils port or package or set CROSS_BINUTILS_PREFIX. *** [buildworld] Error code 1 make: stopped in /poudriere/jails/HEAD-aarch64/usr/src .ERROR_TARGET='buildworld' .ERROR_META_FILE='' .MAKE.LEVEL='0' MAKEFILE='' .MAKE.MODE='normal' .CURDIR='/poudriere/jails/HEAD-aarch64/usr/src' .MAKE='make' .OBJDIR='/poudriere/jails/HEAD-aarch64/usr/src' .TARGETS='buildworld' DESTDIR='' LD_LIBRARY_PATH='' MACHINE='amd64' MACHINE_ARCH='amd64' MAKEOBJDIRPREFIX='/usr/obj' MAKESYSPATH='/poudriere/jails/HEAD-aarch64/usr/src/share/mk' MAKE_VERSION='20160818' PATH='/sbin:/bin:/usr/sbin:/usr/bin' SRCTOP='/poudriere/jails/HEAD-aarch64/usr/src' OBJTOP='/poudriere/jails/HEAD-aarch64/usr/src' 1 error make: stopped in /poudriere/jails/HEAD-aarch64/usr/src .ERROR_TARGET='buildworld' .ERROR_META_FILE='' .MAKE.LEVEL='0' MAKEFILE='' .MAKE.MODE='normal' .CURDIR='/poudriere/jails/HEAD-aarch64/usr/src' .MAKE='make' .OBJDIR='/poudriere/jails/HEAD-aarch64/usr/src' .TARGETS='buildworld' DESTDIR='' LD_LIBRARY_PATH='' MACHINE='amd64' MACHINE_ARCH='amd64' MAKEOBJDIRPREFIX='/usr/obj' MAKESYSPATH='/poudriere/jails/HEAD-aarch64/usr/src/share/mk' MAKE_VERSION='20160818' PATH='/sbin:/bin:/usr/sbin:/usr/bin' SRCTOP='/poudriere/jails/HEAD-aarch64/usr/src' OBJTOP='/poudriere/jails/HEAD-aarch64/usr/src' [00:03:32] >> Error: Failed to 'make buildworld' [00:03:32] >> Error while creating jail, cleaning up. [00:03:32] >> Removing HEAD-aarch64 jail... done % - -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: should aarch64 cross-build work at amd64?
24.09.2016 00:39, Glen Barber пишет: > On Sat, Sep 24, 2016 at 12:35:30AM +0300, Boris Samorodov wrote: >> make[1]: /poudriere/jails/HEAD-aarch64/usr/src/Makefile.inc1 line 177: >> In-tree binutils does not support the aarch64 architecture. Install the >> aarch64-binutils port or package or set CROSS_BINUTILS_PREFIX. > > These lines are relevant. Ops. Thank you. -- WBR, bsam ___ 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: should aarch64 cross-build work at amd64?
24.09.2016 00:44, Boris Samorodov пишет: > 24.09.2016 00:39, Glen Barber пишет: >> On Sat, Sep 24, 2016 at 12:35:30AM +0300, Boris Samorodov wrote: >>> make[1]: /poudriere/jails/HEAD-aarch64/usr/src/Makefile.inc1 line 177: >>> In-tree binutils does not support the aarch64 architecture. Install the >>> aarch64-binutils port or package or set CROSS_BINUTILS_PREFIX. >> >> These lines are relevant. > > Ops. Thank you. The error when aarch64-binutils are installed: - % sudo poudriere jail -c -j HEAD-aarch64 -a arm.aarch64 -v head -m svn+https -J 8 [00:00:00] >> Cross-building ports for arm.aarch64 on amd64 requires QEMU [00:00:00] >> Creating HEAD-aarch64 fs... done [00:00:01] >> Checking out the sources from svn... done [00:03:41] >> Starting make buildworld with 8 jobs --- buildworld --- make[1]: "/poudriere/jails/HEAD-aarch64/usr/src/Makefile.inc1" line 146: SYSTEM_COMPILER: Determined that CC=cc matches the source tree. Not bootstrapping a cross-compiler. make[1]: "/poudriere/jails/HEAD-aarch64/usr/src/Makefile.inc1" line 371: Unknown target aarch64:arm. *** [buildworld] Error code 1 - -- WBR, bsam ___ 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: should aarch64 cross-build work at amd64?
24.09.2016 01:19, Glen Barber пишет: > On Sat, Sep 24, 2016 at 12:54:05AM +0300, Boris Samorodov wrote: >> 24.09.2016 00:44, Boris Samorodov пишет: >>> 24.09.2016 00:39, Glen Barber пишет: >>>> On Sat, Sep 24, 2016 at 12:35:30AM +0300, Boris Samorodov wrote: >>>>> make[1]: /poudriere/jails/HEAD-aarch64/usr/src/Makefile.inc1 line 177: >>>>> In-tree binutils does not support the aarch64 architecture. Install the >>>>> aarch64-binutils port or package or set CROSS_BINUTILS_PREFIX. >>>> >>>> These lines are relevant. >>> >>> Ops. Thank you. >> >> The error when aarch64-binutils are installed: >> - >> % sudo poudriere jail -c -j HEAD-aarch64 -a arm.aarch64 -v head -m >> svn+https -J 8 > > Try with 'arm64.aarch64'. Glen, you've made my day... well, night! It's compiling now. Thank you! -- WBR, bsam ___ 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: should aarch64 cross-build work at amd64?
28.09.2016 07:22, Glen Barber пишет: > On Tue, Sep 27, 2016 at 09:46:29PM -0600, Ross Alexander wrote: >> On Fri, 23 Sep 2016 22:19:15 +, Glenn Barber wrote: >> >>> On Sat, Sep 24, 2016 at 12:54:05AM +0300, Boris Samorodov wrote: >>>> 24.09.2016 00:44, Boris Samorodov ?: >>>>> 24.09.2016 00:39, Glen Barber ?: >>>>>> On Sat, Sep 24, 2016 at 12:35:30AM +0300, Boris Samorodov wrote: >>>>>>> make[1]: /poudriere/jails/HEAD-aarch64/usr/src/Makefile.inc1 line 177: >>>>>>> In-tree binutils does not support the aarch64 architecture. Install the >>>>>>> aarch64-binutils port or package or set CROSS_BINUTILS_PREFIX. >>>>>> >>>>>> These lines are relevant. >>>>> >>>>> Ops. Thank you. >>>> >>>> The error when aarch64-binutils are installed: >>>> - >>>> % sudo poudriere jail -c -j HEAD-aarch64 -a arm.aarch64 -v head -m >>>> svn+https -J 8 >>> >>> Try with 'arm64.aarch64'. >>> Glen >> >> Glen, >> >> The more I read this, the less I understand. I've built and install'd >> aarch64-binutils on my poud box, then created an "-x -a arm64.aarch64 -m svn" >> jail - which worked fine - but that jail won't build anything. No >> /usr/bin/ld, so toolchain is borked, so can't build ports-mgmt/pkg. >> What utterly obvious thing have I missed? I've spent hours trying to >> fake out the nxb-bin stuff, or to find some other point of entry, no >> joy. >> >> FreeBSD aubey2.bogons 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r306286: >> Fri Sep 23 21:32:37 MDT 2016 >> toor@aubey2.bogons:/usr/obj/usr/src/sys/GENERIC amd64 >> >> poudriere-devel-3.1.99.20160624_2 >> >> qemu-user-static-2.6.90.g20160728 >> >> aarch64-binutils-2.25.1_3,1 >> >> # /usr/sbin/binmiscctl lookup aarch64 >> name: aarch64 >> interpreter: /usr/local/bin/qemu-aarch64-static >> flags: ENABLED USE_MASK >> magic size: 20 >> magic offset: 0 >> magic: 0x7f 0x45 0x4c 0x46 0x02 0x01 0x01 0x00 0x00 0x00 0x00 0x00 >>0x00 0x00 0x00 0x00 0x02 0x00 0xb7 0x00 >>mask: 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x00 0xff 0xff 0xff 0xff >> 0xff 0xff 0xff 0xff 0xfe 0xff 0xff 0xff >> >> failing jail is "11-stab-arm64 11.0-PRERELEASE r306344 arm64.aarch64 svn >> 2016-09-26 18:54:15 /usr/local/pd/jails/11-stab-arm64" >> > > You should not need to use binmiscctl and QEMU. Try: > > # poudriere jail -c -j HEAD-aarch64 -a arm.aarch64 -v head -m \ > svn+https Last time I tried the needed option for arch was "-a arm64.aarch64". Glen, it was you who helped me to fugure out the option. :-) -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve signature.asc Description: OpenPGP digital signature
Re: Does someone keep track of how long it takes to buildworld/kernel?
13.01.2017 23:23, Eric Joyner пишет: > ^ Message ^ > > It takes forever, but I keep on forgetting to time how long it takes, so I > don't know how long "forever" is. For me "forever" today was less then 3 minutes. ;-) Here is some stats: --- % cd /usr/obj % grep "World build" bw.amd64.log* bw.amd64.log:>>> World build started on Fri Jan 13 17:42:07 MSK 2017 bw.amd64.log:>>> World build completed on Fri Jan 13 17:44:45 MSK 2017 bw.amd64.log.0:>>> World build started on Thu Jan 12 20:55:07 MSK 2017 bw.amd64.log.0:>>> World build completed on Thu Jan 12 21:00:37 MSK 2017 bw.amd64.log.1:>>> World build started on Thu Jan 12 11:54:28 MSK 2017 bw.amd64.log.1:>>> World build completed on Thu Jan 12 11:59:43 MSK 2017 bw.amd64.log.2:>>> World build started on Wed Jan 11 14:41:59 MSK 2017 bw.amd64.log.2:>>> World build completed on Wed Jan 11 14:46:36 MSK 2017 bw.amd64.log.3:>>> World build started on Wed Jan 11 13:15:03 MSK 2017 bw.amd64.log.3:>>> World build completed on Wed Jan 11 13:59:01 MSK 2017 bw.amd64.log.4:>>> World build started on Sun Jan 8 17:21:15 MSK 2017 bw.amd64.log.4:>>> World build completed on Sun Jan 8 17:30:30 MSK 2017 bw.amd64.log.5:>>> World build started on Sat Jan 7 21:27:06 MSK 2017 bw.amd64.log.5:>>> World build completed on Sat Jan 7 23:37:25 MSK 2017 bw.amd64.log.6:>>> World build started on Thu Dec 22 13:19:08 MSK 2016 bw.amd64.log.6:>>> World build completed on Thu Dec 22 13:40:22 MSK 2016 --- With "WITH_META_MODE=yes" at /etc/src-env.conf it's rather sane time. But not if clang or like changes. :-( The machine is: --- FreeBSD 12.0-CURRENT #39 r312075: Fri Jan 13 17:47:05 MSK 2017 bsam@bb055.bsnet:/usr/obj/usr/src/sys/BB64X amd64 FreeBSD clang version 3.9.1 (tags/RELEASE_391/final 289601) (based on LLVM 3.9.1) VT(vga): resolution 640x480 info: [drm] Initialized drm 1.1.0 20060810 CPU: Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz (3092.27-MHz K8-class CPU) Origin="GenuineIntel" Id=0x206a7 Family=0x6 Model=0x2a Stepping=7 Features=0xbfebfbff Features2=0x1d9ae3bf AMD Features=0x28100800 AMD Features2=0x1 XSAVE Features=0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory = 8589934592 (8192 MB) avail memory = 8136523776 (7759 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 hardware threads [...] ada1 at ahcich4 bus 0 scbus2 target 0 lun 0 ada1: ACS-2 ATA SATA 3.x device ada1: Serial Number Z1D5Y0X8 ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 953869MB (1953525168 512 byte sectors) ada1: quirks=0x1<4K> --- HTH & WBR -- bsam ___ 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"
pkg, base packages and subdirectories
Hi All, I've created my base repo and installed the OS from packages. All in all it all went rather smooth! As for pkg it seems to not pay attention to base library subdirs: - # pkg check -Ba Checking all packages: 3% (FreeBSD-kernel-sm-12.0.s20170128125723) /boot/kernel/kernel - required shared library hack.pico not found Checking all packages: 35% (FreeBSD-runtime-12.0.s20170128125723) /sbin/ping - required shared library libcap_dns.so.0 not found (FreeBSD-runtime-12.0.s20170128125723) /usr/bin/kdump - required shared library libcap_grp.so.0 not found (FreeBSD-runtime-12.0.s20170128125723) /usr/bin/kdump - required shared library libcap_pwd.so.0 not found (FreeBSD-runtime-12.0.s20170128125723) /usr/sbin/tcpdump - required shared library libcap_dns.so.0 not found Checking all packages: 36% (FreeBSD-tests-12.0.s20170128125723) /usr/tests/lib/libcasper/services/cap_dns/dns_test - required shared library libcap_dns.so.0 not found (FreeBSD-tests-12.0.s20170128125723) /usr/tests/lib/libcasper/services/cap_grp/grp_test - required shared library libcap_grp.so.0 not found (FreeBSD-tests-12.0.s20170128125723) /usr/tests/lib/libcasper/services/cap_pwd/pwd_test - required shared library libcap_pwd.so.0 not found (FreeBSD-tests-12.0.s20170128125723) /usr/tests/lib/libcasper/services/cap_sysctl/sysctl_test - required shared library libcap_sysctl.so.0 not found Checking all packages: 100% # ldd `which ping` /sbin/ping: libm.so.5 => /lib/libm.so.5 (0x800828000) libcasper.so.0 => /lib/libcasper.so.0 (0x800a52000) libcap_dns.so.0 => /lib/casper/libcap_dns.so.0 (0x800c57000) libipsec.so.4 => /lib/libipsec.so.4 (0x800e5b000) # ls -l /lib/casper total 51 -r--r--r-- 1 root wheel 16584 28 янв. 15:58 libcap_dns.so.0 -r--r--r-- 1 root wheel 15968 28 янв. 15:58 libcap_grp.so.0 -r--r--r-- 1 root wheel 15872 28 янв. 15:58 libcap_pwd.so.0 -r--r--r-- 1 root wheel 6904 28 янв. 15:58 libcap_random.so.0 -r--r--r-- 1 root wheel 8912 28 янв. 15:58 libcap_sysctl.so.0 ----- -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: r316958: booting a server takes >10 minutes!
15.04.2017 14:53, O. Hartmann пишет: Recent CURRENT running on a server makes the system booting in multiuser mode booting incredibly slow! On a machine, before I interrupted the booting process hanging in starting postgresql 9.6.2 server, it took > 10 minutes. Same here. BTW, the command "service -e" runs forever and eats CPU. I had to kill sendmail and dbus (which were chewing CPU) and then "service -e" run fine. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve "It is not necessary to change. Survival is not mandatory." ___ 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"
misc/mc, diff and compare two files
Hi All, FYI: For those who use FreeBSD-HEAD, misc/mc and it's awesome "compare two files" feature: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219277 HTH -- WBR, bsam ___ 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"
base packages, ino64 and upgrade
Hi All, Does anyone know the procedure to upgrade for those using base packages? -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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"
ERROR: ctfconvert: [...] has too many members: 1911 > 1023 _and_ ERROR: rc = -1 No entry found [dwarf_next_cu_header_c(61)]
Hi All, JFYI: Today I've got a bunch (as much as 63) of cftconvert errors while make buildkernel. There were no such errors tomorrow. The building machine is FreeBSD-amd64-r317665. Errors are not fatal, so the kernel has build successfully. I didn't dare to try to install it yet. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: base packages, ino64 and upgrade
24.05.2017 16:00, Glen Barber пишет: > On Wed, May 24, 2017 at 03:47:47PM +0300, Boris Samorodov wrote: >> Hi All, >> >> Does anyone know the procedure to upgrade for those using base packages? > > 'pkg install FreeBSD-kernel-generic' (or whatever your kernel package is > called), reboot, 'pkg upgrade'. OK, thanks. I'll try in the evening. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve signature.asc Description: OpenPGP digital signature
Re: ERROR: ctfconvert: [...] has too many members: 1911 > 1023 _and_ ERROR: rc = -1 No entry found [dwarf_next_cu_header_c(61)]
24.05.2017 18:09, Dimitry Andric пишет: > On 24 May 2017, at 14:58, Boris Samorodov wrote: >> >> JFYI: Today I've got a bunch (as much as 63) of cftconvert errors >> while make buildkernel. There were no such errors tomorrow. The building >> machine is FreeBSD-amd64-r317665. >> >> Errors are not fatal, so the kernel has build successfully. I didn't >> dare to try to install it yet. > > These messages have been occurring for a long time now (years?), and > can be safely ignored. Hi Dimitry, I suspected something like this. I have WITH_META_MODE defined so it may be why I do see those messages rarely. Thank you. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve signature.asc Description: OpenPGP digital signature
ino64, java and intellij products problem
Hi All, Seems that after ino64 transition some java programs stopped to fully function. I.e. java/intellij (IntellJ IDEA and Co) starts but does not show any files. I'm not sure if it's a java or IntelliJ problem. Any help to diagnose the culprit is welcome. Thanks. -- WBR, bsam ___ 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: ino64, java and intellij products problem
01.06.2017 00:29, Konstantin Belousov пишет: > On Wed, May 31, 2017 at 11:53:39PM +0300, Boris Samorodov wrote: >> Hi All, >> >> Seems that after ino64 transition some java programs stopped >> to fully function. I.e. java/intellij (IntellJ IDEA and Co) >> starts but does not show any files. >> >> I'm not sure if it's a java or IntelliJ problem. Any help to >> diagnose the culprit is welcome. > > Is it after full rebuild of all ports for post-ino64, or with all ports > built on pre-ino64 ? (Mixes are not supported and not supposed to work). Hm. I've rebuild all required ports: --- % pkg info -d intellij-2017.1.3 intellij-2017.1.3: python27-2.7.13_3 openjdk8-8.131.11 intellij-pty4j-0.5_1 intellij-fsnotifier-20160221_2 --- But sure not *all* ports. > Check java programs for JNI calls which return struct stat or struct > dirent to java code, and java code which knows the layout. It is, e.g., > the problem with Firefox and its javascript, but there the recompilation > seems to work. OK, thanks. I'll wait for FreeBSD cluster[*] to build post-ino64 packages, reinstall all of them and see what's next. [*] Seems to occur RSN. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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"
[bsd.linker.mk] line 42: Unable to determine linker type from LD=ld
Hi All, Bryan!
Since bsd.linker.mk introduction I can't manage to create
FreeBSD base packages. The process stops at the very beginning:
-
--- packages ---
--- packages ---
make -C /usr/src PKG_VERSION=12.0.s20170623140202 real-packages
--- real-packages ---
--- stage-packages ---
mkdir -p /tmp/install.DQDhLPed
progs=$(for prog in [ awk cap_mkdb cat chflags chmod chown cmp cp date
echo egrep find grep id install ln make mkdir mtree mv pwd_mkdb rm
sed services_mkdb sh strip sysctl test true uname wc zic tzsetup
makewhatis; do if progpath=
`which $prog`; then echo $progpath; else echo "Required tool $prog
not found in PATH." >&2; exit 1; fi; done); libs=$(ldd -f "%o %p\n"
-f "%o %p\n" $progs 2>/dev/null | sort -u | while read line; do $line;
if [ "$2 $3" != "not
found" ]; then echo $2; else echo "Required library $1 not found."
>&2; exit 1; fi; done); cp $libs $progs /tmp/install.DQDhLPed
cp -R ${PATH_LOCALE:-"/usr/share/locale"} /tmp/install.DQDhLPed/locale
mkdir -p /usr/obj/usr/src/amd64.amd64/worldstage/
echo "#mtree 2.0" > /usr/obj/usr/src/amd64.amd64/worldstage//METALOG
cd /usr/src; COMPILER_VERSION=4 COMPILER_FEATURES=c++11
COMPILER_TYPE=clang COMPILER_FREEBSD_VERSION=126
MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=amd64 MACHINE=amd64 CPUTYPE=
CC="cc -target x86_64-unknown-freebsd12.0 --sysroo
t=/usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/bin" CXX="c++ -target
x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp
-B/usr/obj/usr/src/tmp/usr/bin" CPP="cpp -target
x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tm
p -B/usr/obj/usr/src/tmp/usr/bin" AS="as" AR="ar" LD="ld" LLVM_LINK=""
NM=nm OBJCOPY="objcopy" RANLIB=ranlib STRINGS= SIZE="size"
PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/lega
cy/bin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/tmp/install.DQDhLPed
LD_LIBRARY_PATH=/tmp/install.DQDhLPed
PATH_LOCALE=/tmp/install.DQDhLPed/locale make -f Makefile.inc1
INSTALL="install -U -M /usr/obj/usr/src/amd64
.amd64/worldstage//METALOG -D /usr/obj/usr/src/amd64.amd64/worldstage"
MTREE_CMD="mtree -W" __MAKE_SHELL=/tmp/install.DQDhLPed/sh -DNO_ROOT
METALOG=/usr/obj/usr/src/amd64.amd64/worldstage//METALOG restage;
COMPILER_VERSION=4 COMPIL
ER_FEATURES=c++11 COMPILER_TYPE=clang COMPILER_FREEBSD_VERSION=126
MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=amd64 MACHINE=amd64 CPUTYPE=
CC="cc -target x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp
-B/usr/obj/usr/src/t
mp/usr/bin" CXX="c++ -target x86_64-unknown-freebsd12.0
--sysroot=/usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/bin" CPP="cpp
-target x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp
-B/usr/obj/usr/src/tmp/usr/bin" AS="as"
AR="ar" LD="ld" LLVM_LINK="" NM=nm OBJCOPY="objcopy" RANLIB=ranlib
STRINGS= SIZE="size"
PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/bin:/usr/obj/usr/src/tmp/usr/sbin:/usr/o
bj/usr/src/tmp/usr/bin:/tmp/install.DQDhLPed
LD_LIBRARY_PATH=/tmp/install.DQDhLPed
PATH_LOCALE=/tmp/install.DQDhLPed/locale rm -rf /tmp/install.DQDhLPed
sh: head: not found
make[6]: "/usr/src/share/mk/bsd.linker.mk" line 42: Unable to determine
linker type from LD=ld
*** Error code 1
Stop.
-
--
WBR, bsam
___
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: [bsd.linker.mk] line 42: Unable to determine linker type from LD=ld
23.06.2017 17:19, Boris Samorodov пишет:
> Hi All, Bryan!
>
> Since bsd.linker.mk introduction I can't manage to create
> FreeBSD base packages. The process stops at the very beginning:
> -
> --- packages ---
> --- packages ---
> make -C /usr/src PKG_VERSION=12.0.s20170623140202 real-packages
> --- real-packages ---
> --- stage-packages ---
> mkdir -p /tmp/install.DQDhLPed
> progs=$(for prog in [ awk cap_mkdb cat chflags chmod chown cmp cp date
> echo egrep find grep id install ln make mkdir mtree mv pwd_mkdb rm
> sed services_mkdb sh strip sysctl test true uname wc zic tzsetup
> makewhatis; do if progpath=
> `which $prog`; then echo $progpath; else echo "Required tool $prog
> not found in PATH." >&2; exit 1; fi; done); libs=$(ldd -f "%o %p\n"
> -f "%o %p\n" $progs 2>/dev/null | sort -u | while read line; do $line;
> if [ "$2 $3" != "not
> found" ]; then echo $2; else echo "Required library $1 not found."
>> &2; exit 1; fi; done); cp $libs $progs /tmp/install.DQDhLPed
> cp -R ${PATH_LOCALE:-"/usr/share/locale"} /tmp/install.DQDhLPed/locale
> mkdir -p /usr/obj/usr/src/amd64.amd64/worldstage/
> echo "#mtree 2.0" > /usr/obj/usr/src/amd64.amd64/worldstage//METALOG
> cd /usr/src; COMPILER_VERSION=4 COMPILER_FEATURES=c++11
> COMPILER_TYPE=clang COMPILER_FREEBSD_VERSION=126
> MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=amd64 MACHINE=amd64 CPUTYPE=
> CC="cc -target x86_64-unknown-freebsd12.0 --sysroo
> t=/usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/bin" CXX="c++ -target
> x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp
> -B/usr/obj/usr/src/tmp/usr/bin" CPP="cpp -target
> x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tm
> p -B/usr/obj/usr/src/tmp/usr/bin" AS="as" AR="ar" LD="ld" LLVM_LINK=""
> NM=nm OBJCOPY="objcopy" RANLIB=ranlib STRINGS= SIZE="size"
> PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/lega
> cy/bin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/tmp/install.DQDhLPed
> LD_LIBRARY_PATH=/tmp/install.DQDhLPed
> PATH_LOCALE=/tmp/install.DQDhLPed/locale make -f Makefile.inc1
> INSTALL="install -U -M /usr/obj/usr/src/amd64
> .amd64/worldstage//METALOG -D /usr/obj/usr/src/amd64.amd64/worldstage"
> MTREE_CMD="mtree -W" __MAKE_SHELL=/tmp/install.DQDhLPed/sh -DNO_ROOT
> METALOG=/usr/obj/usr/src/amd64.amd64/worldstage//METALOG restage;
> COMPILER_VERSION=4 COMPIL
> ER_FEATURES=c++11 COMPILER_TYPE=clang COMPILER_FREEBSD_VERSION=126
> MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=amd64 MACHINE=amd64 CPUTYPE=
> CC="cc -target x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp
> -B/usr/obj/usr/src/t
> mp/usr/bin" CXX="c++ -target x86_64-unknown-freebsd12.0
> --sysroot=/usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/bin" CPP="cpp
> -target x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp
> -B/usr/obj/usr/src/tmp/usr/bin" AS="as"
> AR="ar" LD="ld" LLVM_LINK="" NM=nm OBJCOPY="objcopy" RANLIB=ranlib
> STRINGS= SIZE="size"
> PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/bin:/usr/obj/usr/src/tmp/usr/sbin:/usr/o
> bj/usr/src/tmp/usr/bin:/tmp/install.DQDhLPed
> LD_LIBRARY_PATH=/tmp/install.DQDhLPed
> PATH_LOCALE=/tmp/install.DQDhLPed/locale rm -rf /tmp/install.DQDhLPed
> sh: head: not found
> make[6]: "/usr/src/share/mk/bsd.linker.mk" line 42: Unable to determine
> linker type from LD=ld
> *** Error code 1
>
> Stop.
> -
>
Yes! Awesome!! Thank you for quick reaction and the fix.
--
WBR, bsam
___
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"
r320307 -> r320324: kernel does not load
Hi All, I use self-built base packages for system updates. The jump from r320307 to r320324 leads to fatal trap 12 at the very beginning: https://goo.gl/Pgujga (sorry for the poor photo quality) Revert to r320307, and the system boots fine. -- WBR, bsam ___ 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: r320307 -> r320324: kernel does not load
(cc: kib@) Hi Kostik, FYI: I've looked though last source changes and it looks like your commit(s) may be related. 25.06.2017 13:54, Boris Samorodov пишет: > Hi All, > > I use self-built base packages for system updates. The jump from > r320307 to r320324 leads to fatal trap 12 at the very beginning: > https://goo.gl/Pgujga (sorry for the poor photo quality) > > Revert to r320307, and the system boots fine. -- WBR, bsam ___ 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: Insta-panic for amd64 on reboot after upgrade from r320307 -> r320324
25.06.2017 16:21, Konstantin Belousov пишет: > On Sun, Jun 25, 2017 at 06:05:21AM -0700, David Wolfskill wrote: >> On Sun, Jun 25, 2017 at 03:52:23PM +0300, Konstantin Belousov wrote: >>> ... > The layout of the struct vm_map_entry was changed, the faulted address > is somewhat consistent with ABI mismatch. Kinky. :-} >>> Do you use any third-party modules ? >> >> On the laptop, I use x11/nvidia-driver-340; on the build machine, no. >> >> I think we should focus on the build machine -- it runs a GENERIC kernel >> without ports (3rd-party) modules. > Ok. > >> >> #cat /etc/src-env.conf >> WITH_META_MODE=yes > > So can you _remove_ all kernel object files and rebuild anew with the > clean build dir, please ? I also use WITH_META_MODE=yes. And full rebuild helped here too. Thank you. -- WBR, bsam ___ 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"
[base package build] [fail] r320347 -> r320392: install: builddir/Africa/Abidjan: No such file or directory
Hi, I regularly build base packages for FreeBSD-HEAD-amd64. After jump from r320347 to r320392 (build world/kernel are fine) I get an error while package building (make -C /usr/src packages): - --- realinstall_subdir_share --- --- realinstall_subdir_share/zoneinfo --- install: builddir/Africa/Abidjan: No such file or directory *** [install-zoneinfo] Error code 71 - -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: [base package build] [fail] r320347 -> r320392: install: builddir/Africa/Abidjan: No such file or directory
27.06.2017 20:06, Trond Endrestøl пишет: > Try running make installworld without -j N. > Serial installworld was successful at my end. Thank you, that helped. -- WBR, bsam ___ 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: [base package build] [fail] r320347 -> r320392: install: builddir/Africa/Abidjan: No such file or directory
05.07.2017 22:29, Bryan Drewery пишет: > Parallel install should be working just fine. It is a supported feature > of installworld. What was the issue exactly? https://lists.freebsd.org/pipermail/freebsd-current/2017-June/066408.html As I understand, it was an installworld while base packages building. But I suspect that META_MODE may be to blame. I've shitched it off since then. -- WBR, bsam signature.asc Description: OpenPGP digital signature
[memstick install] auto-zfs error
Hi All, I tied to install a new FreeBSD-amd-12 system from official USB installation memstick.img. Auto-UFS (GPT) installs fine and the system boots fine. However, ZFS-Auto install succeeds, but is not loaded. At the very beginning it gives something like "gpt sector error, gpt sector 1 error, can't find zroot..." Is it a known error / should I give more (precise) errors? I tried two recent images with the same result: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170703-r320599-memstick.img ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170626-r320360-memstick.img Thanks all, -- WBR, bsam ___ 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"
pkg, repos and cached certificates
Hi All, I use own pkg base repository. Today I tried to install packages on a new system. However, pkg refused to use my repo, since it's certificate is expired (several days). That's good. However, pkg happily update packages at other systems. So, seems that pkg does not perform checks / validates known certificates. Which seems not as good. Thanks, -- WBR, bsam ___ 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"
[bhyve] FreeBSD guest, Handbook, vmrun.sh
Hi All, I try to create a FreeBSD guest as per TH, section "21.7.2. Creating a FreeBSD Guest". All is good up until the last command at the section. When I try to launch the installed client, I get: - # sh /usr/share/examples/bhyve/vmrun.sh -c 4 -m 1024M -t tap0 -d guest.img guestname Launching virtual machine "guestname" ... Installation CDROM image "./release.iso" is not readable % uname -a FreeBSD latt.bsnet 12.0-CURRENT FreeBSD 12.0-CURRENT #14 r320821: Sun Jul 9 07:10:56 MSK 2017 bsam@builder.bsnet:/usr/obj/usr/src/sys/PKG64X amd64 - Is it a bug at vmrun.sh or documentation? -- WBR, bsam ___ 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: [bhyve] FreeBSD guest, Handbook, vmrun.sh
09.07.2017 18:37, Benjamin Kaduk пишет: > On Sun, Jul 09, 2017 at 01:02:26PM +0300, Boris Samorodov wrote: >> Hi All, >> >> I try to create a FreeBSD guest as per TH, section "21.7.2. Creating >> a FreeBSD Guest". All is good up until the last command at the section. >> When I try to launch the installed client, I get: >> - >> # sh /usr/share/examples/bhyve/vmrun.sh -c 4 -m 1024M -t tap0 -d >> guest.img guestname >> Launching virtual machine "guestname" ... >> Installation CDROM image "./release.iso" is not readable >> >> % uname -a >> FreeBSD latt.bsnet 12.0-CURRENT FreeBSD 12.0-CURRENT #14 r320821: Sun >> Jul 9 07:10:56 MSK 2017 >> bsam@builder.bsnet:/usr/obj/usr/src/sys/PKG64X amd64 >> - >> >> Is it a bug at vmrun.sh or documentation? > > Documentation looks okay, as -I is documented during > the install stage, and is not supposed to be needed during > normal operation. > > The quoted error message from vmrun.sh happens when it thinks you > need to install on the given filesystem image > (if [ $force_install -eq 1 -o $need_install -eq 1 ];) > so it might be worth checking that your guest.img contains a valid > FFS filesystem on it. (Hmm, maybe you used ZFS and vmrun.sh isn't > prepared to handle that?) Yes, I used AutoZFS installer function to install FreeBSD. -- WBR, bsam ___ 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: [bhyve] FreeBSD guest, Handbook, vmrun.sh
09.07.2017 18:48, Boris Samorodov пишет: > 09.07.2017 18:37, Benjamin Kaduk пишет: >> On Sun, Jul 09, 2017 at 01:02:26PM +0300, Boris Samorodov wrote: >>> Hi All, >>> >>> I try to create a FreeBSD guest as per TH, section "21.7.2. Creating >>> a FreeBSD Guest". All is good up until the last command at the section. >>> When I try to launch the installed client, I get: >>> - >>> # sh /usr/share/examples/bhyve/vmrun.sh -c 4 -m 1024M -t tap0 -d >>> guest.img guestname >>> Launching virtual machine "guestname" ... >>> Installation CDROM image "./release.iso" is not readable >>> >>> % uname -a >>> FreeBSD latt.bsnet 12.0-CURRENT FreeBSD 12.0-CURRENT #14 r320821: Sun >>> Jul 9 07:10:56 MSK 2017 >>> bsam@builder.bsnet:/usr/obj/usr/src/sys/PKG64X amd64 >>> - >>> >>> Is it a bug at vmrun.sh or documentation? >> >> Documentation looks okay, as -I is documented during >> the install stage, and is not supposed to be needed during >> normal operation. >> >> The quoted error message from vmrun.sh happens when it thinks you >> need to install on the given filesystem image >> (if [ $force_install -eq 1 -o $need_install -eq 1 ];) >> so it might be worth checking that your guest.img contains a valid >> FFS filesystem on it. (Hmm, maybe you used ZFS and vmrun.sh isn't >> prepared to handle that?) > > Yes, I used AutoZFS installer function to install FreeBSD. - % sudo mdconfig -f quest.img mdo0 % gpart show md0 => 40 16777136 md0 GPT (8.0G) 40 10241 freebsd-boot (512K) 1064 984 - free - (492K) 2048 41943042 freebsd-swap (2.0G) 4196352 125788163 freebsd-zfs (6.0G) 16775168 2008 - free - (1.0M) - So, that seems the same bug as at my previous email: https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066514.html -- WBR, bsam ___ 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: [bhyve] FreeBSD guest, Handbook, vmrun.sh
09.07.2017 19:08, Benjamin Kaduk пишет:
> On Sun, Jul 09, 2017 at 06:58:09PM +0300, Boris Samorodov wrote:
>> 09.07.2017 18:48, Boris Samorodov пишет:
>>> 09.07.2017 18:37, Benjamin Kaduk пишет:
>>>>
>>>> Documentation looks okay, as -I is documented during
>>>> the install stage, and is not supposed to be needed during
>>>> normal operation.
>>>>
>>>> The quoted error message from vmrun.sh happens when it thinks you
>>>> need to install on the given filesystem image
>>>> (if [ $force_install -eq 1 -o $need_install -eq 1 ];)
>>>> so it might be worth checking that your guest.img contains a valid
>>>> FFS filesystem on it. (Hmm, maybe you used ZFS and vmrun.sh isn't
>>>> prepared to handle that?)
>>>
>>> Yes, I used AutoZFS installer function to install FreeBSD.
>>
>> -
>> % sudo mdconfig -f quest.img
>> mdo0
>>
>> % gpart show md0
>> => 40 16777136 md0 GPT (8.0G)
>> 40 10241 freebsd-boot (512K)
>> 1064 984 - free - (492K)
>> 2048 41943042 freebsd-swap (2.0G)
>>4196352 125788163 freebsd-zfs (6.0G)
>> 16775168 2008 - free - (1.0M)
>> -
>>
>> So, that seems the same bug as at my previous email:
>> https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066514.html
>
> Is it? I refer to this part of vmrun.sh:
>
> file -s ${first_diskdev} | grep "boot sector" > /dev/null
> rc=$?
> if [ $rc -ne 0 ]; then
> file -s ${first_diskdev} | grep ": Unix Fast File sys" >
> /dev/null
> rc=$?
> fi
> if [ $rc -ne 0 ]; then
> need_install=1
> else
> need_install=0
> fi
>
> Which is not expected to be particularly robust.
> (BTW, I think there is not agreement as to whether vmrun.sh should
> be used in general use, or alternate solutions for VM managemnet.)
OK, normal bhyveload/bhyve ended up at a successful boot.
Benjamin, thank you for your comments and help!
--
WBR, bsam
___
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"
[SOLVED] [memstick install] auto-zfs error
08.07.2017 18:56, Boris Samorodov пишет: > Hi All, > > I tied to install a new FreeBSD-amd-12 system from official USB > installation memstick.img. Auto-UFS (GPT) installs fine and the system > boots fine. However, ZFS-Auto install succeeds, but is not loaded. > At the very beginning it gives something like "gpt sector error, > gpt sector 1 error, can't find zroot..." > > Is it a known error / should I give more (precise) errors? > > I tried two recent images with the same result: > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170703-r320599-memstick.img > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170626-r320360-memstick.img It turned out GPT and zfs are not usable at this machine. MBR / ZFS works fine. I'll stick with that. -- WBR, bsam ___ 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: [bhyve] FreeBSD guest, Handbook, vmrun.sh
09.07.2017 19:08, Benjamin Kaduk пишет: > (BTW, I think there is not agreement as to whether vmrun.sh should > be used in general use, or alternate solutions for VM managemnet.) As a side note: I used the process written at TH... -- WBR, bsam ___ 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: [SOLVED] [memstick install] auto-zfs error
10.07.2017 21:05, Allan Jude пишет: > On 2017-07-09 14:40, Boris Samorodov wrote: >> 08.07.2017 18:56, Boris Samorodov пишет: >>> Hi All, >>> >>> I tied to install a new FreeBSD-amd-12 system from official USB >>> installation memstick.img. Auto-UFS (GPT) installs fine and the system >>> boots fine. However, ZFS-Auto install succeeds, but is not loaded. >>> At the very beginning it gives something like "gpt sector error, >>> gpt sector 1 error, can't find zroot..." >>> >>> Is it a known error / should I give more (precise) errors? >>> >>> I tried two recent images with the same result: >>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170703-r320599-memstick.img >>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170626-r320360-memstick.img >> >> It turned out GPT and zfs are not usable at this machine. >> MBR / ZFS works fine. >> >> I'll stick with that. > > What type of machine is it? It's a PC circa 2009 with MB ASUS P5QL/EPU: --- CPU: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz (2799.52-MHz K8-class CPU) Origin="GenuineIntel" Id=0x1067a Family=0x6 Model=0x17 Stepping=10 Features=0xbfebfbff Features2=0xc08e3bd AMD Features=0x20100800 AMD Features2=0x1 VT-x: HLT,PAUSE TSC: P-state invariant, performance statistics real memory = 4294967296 (4096 MB) avail memory = 3324891136 (3170 MB) Event timer "LAPIC" quality 100 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) --- -- WBR, bsam signature.asc Description: OpenPGP digital signature
Re: [SOLVED] [memstick install] auto-zfs error
10.07.2017 22:21, Toomas Soome пишет: > >> On 10. juuli 2017, at 21:24, Boris Samorodov wrote: >> >> 10.07.2017 21:05, Allan Jude пишет: >>> On 2017-07-09 14:40, Boris Samorodov wrote: >>>> 08.07.2017 18:56, Boris Samorodov пишет: >>>>> Hi All, >>>>> >>>>> I tied to install a new FreeBSD-amd-12 system from official USB >>>>> installation memstick.img. Auto-UFS (GPT) installs fine and the system >>>>> boots fine. However, ZFS-Auto install succeeds, but is not loaded. >>>>> At the very beginning it gives something like "gpt sector error, >>>>> gpt sector 1 error, can't find zroot..." >>>>> >>>>> Is it a known error / should I give more (precise) errors? >>>>> >>>>> I tried two recent images with the same result: >>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170703-r320599-memstick.img >>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170626-r320360-memstick.img >>>> >>>> It turned out GPT and zfs are not usable at this machine. >>>> MBR / ZFS works fine. >>>> >>>> I'll stick with that. >>> >>> What type of machine is it? >> >> It's a PC circa 2009 with MB ASUS P5QL/EPU: >> --- >> CPU: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz (2799.52-MHz >> K8-class CPU) >> Origin="GenuineIntel" Id=0x1067a Family=0x6 Model=0x17 Stepping=10 >> >> >> Features=0xbfebfbff >> >> >> >> Features2=0xc08e3bd >> >> AMD Features=0x20100800 >> AMD Features2=0x1 >> VT-x: HLT,PAUSE >> TSC: P-state invariant, performance statistics >> real memory = 4294967296 (4096 MB) >> avail memory = 3324891136 (3170 MB) >> Event timer "LAPIC" quality 100 >> ACPI APIC Table: >> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >> FreeBSD/SMP: 1 package(s) x 2 core(s) >> --- >> >> -- >> WBR, bsam > > Of course it really can not be that the BIOS has something against > combination of GPT+ZFS, but this combination may trigger some sort of > bug/misbehavior. I have seen some pretty weird issues and have work in > process to have a bit more fool proof approach, but I haven't had time yet to > finalize it properly. Yep, UFS+GPT works fine here. Just for archieves: errors for ZFS + GPT --- gptzfsboot: error 128 lba 3907027040 gptzfsboot: error 128 lba 1 gptzfsboot: no zfs pools located, can't boot --- The disk is: --- 512 # sectorsize 2000397852160 # mediasize in bytes (1.8T) 3907027055 # mediasize in sectors 0 # stripesize 0 # stripeoffset 3876018 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. WD-WMAUR0112162 # Disk ident. Not_Zoned # Zone Mode --- UEFI is not available at the motherboard. > Namely, what I have found is that in some systems the INT13 ah=08 can result > with unexpected results - error from command reported or disk count not > reported etc - something not really expected. It also may have to do about > what other devices are there. And also if the system has plain BIOS or BIOS > emulated on UEFI. -- WBR, bsam ___ 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: [SOLVED] [memstick install] auto-zfs error
10.07.2017 23:02, Toomas Soome пишет: > >> On 10. juuli 2017, at 22:53, Boris Samorodov wrote: >> >> 10.07.2017 22:21, Toomas Soome пишет: >>> >>>> On 10. juuli 2017, at 21:24, Boris Samorodov wrote: >>>> >>>> 10.07.2017 21:05, Allan Jude пишет: >>>>> On 2017-07-09 14:40, Boris Samorodov wrote: >>>>>> 08.07.2017 18:56, Boris Samorodov пишет: >>>>>>> Hi All, >>>>>>> >>>>>>> I tied to install a new FreeBSD-amd-12 system from official USB >>>>>>> installation memstick.img. Auto-UFS (GPT) installs fine and the system >>>>>>> boots fine. However, ZFS-Auto install succeeds, but is not loaded. >>>>>>> At the very beginning it gives something like "gpt sector error, >>>>>>> gpt sector 1 error, can't find zroot..." >>>>>>> >>>>>>> Is it a known error / should I give more (precise) errors? >>>>>>> >>>>>>> I tried two recent images with the same result: >>>>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170703-r320599-memstick.img >>>>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170626-r320360-memstick.img >>>>>> >>>>>> It turned out GPT and zfs are not usable at this machine. >>>>>> MBR / ZFS works fine. >>>>>> >>>>>> I'll stick with that. >>>>> >>>>> What type of machine is it? >>>> >>>> It's a PC circa 2009 with MB ASUS P5QL/EPU: >>>> --- >>>> CPU: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz (2799.52-MHz >>>> K8-class CPU) >>>> Origin="GenuineIntel" Id=0x1067a Family=0x6 Model=0x17 Stepping=10 >>>> >>>> >>>> Features=0xbfebfbff >>>> >>>> >>>> >>>> Features2=0xc08e3bd >>>> >>>> AMD Features=0x20100800 >>>> AMD Features2=0x1 >>>> VT-x: HLT,PAUSE >>>> TSC: P-state invariant, performance statistics >>>> real memory = 4294967296 (4096 MB) >>>> avail memory = 3324891136 (3170 MB) >>>> Event timer "LAPIC" quality 100 >>>> ACPI APIC Table: >>>> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >>>> FreeBSD/SMP: 1 package(s) x 2 core(s) >>>> --- >>>> >>>> -- >>>> WBR, bsam >>> >>> Of course it really can not be that the BIOS has something against >>> combination of GPT+ZFS, but this combination may trigger some sort of >>> bug/misbehavior. I have seen some pretty weird issues and have work in >>> process to have a bit more fool proof approach, but I haven't had time yet >>> to finalize it properly. >> >> Yep, UFS+GPT works fine here. >> >> Just for archieves: errors for ZFS + GPT >> --- >> gptzfsboot: error 128 lba 3907027040 >> gptzfsboot: error 128 lba 1 > > Hm, 128 is 0x80 == Disk timeout. So it can be result from the missing device > (bad USB connection or missing floppy drive). What our INT13 related code is > currently missing, is the reset on error calls - to try to get the IO system > back to stable state. Or to be exact - the reset is not always used. Actually, it's the same SATA cable/disk which works for UFS/ZFS. > rgds, > toomas > >> gptzfsboot: no zfs pools located, can't boot >> --- >> >> The disk is: >> --- >>512 # sectorsize >>2000397852160 # mediasize in bytes (1.8T) >>3907027055 # mediasize in sectors >>0 # stripesize >>0 # stripeoffset >>3876018 # Cylinders according to firmware. >>16 # Heads according to firmware. >>63 # Sectors according to firmware. >>WD-WMAUR0112162 # Disk ident. >>Not_Zoned # Zone Mode >> --- >> >> UEFI is not available at the motherboard. >> >>> Namely, what I have found is that in some systems the INT13 ah=08 can >>> result with unexpected results - error from command reported or disk count >>> not reported etc - something not really expected. It also may have to do >>> about what other devices are there. And also if the system has plain BIOS >>> or BIOS emulated on UEFI. >> -- WBR, bsam ___ 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: [SOLVED] [memstick install] auto-zfs error
10.07.2017 23:58, Ronald Klop пишет: > On Mon, 10 Jul 2017 21:53:11 +0200, Boris Samorodov wrote: > >> 10.07.2017 22:21, Toomas Soome пишет: >>> >>>> On 10. juuli 2017, at 21:24, Boris Samorodov wrote: >>>> >>>> 10.07.2017 21:05, Allan Jude пишет: >>>>> On 2017-07-09 14:40, Boris Samorodov wrote: >>>>>> 08.07.2017 18:56, Boris Samorodov пишет: >>>>>>> Hi All, >>>>>>> >>>>>>> I tied to install a new FreeBSD-amd-12 system from official USB >>>>>>> installation memstick.img. Auto-UFS (GPT) installs fine and the >>>>>>> system >>>>>>> boots fine. However, ZFS-Auto install succeeds, but is not loaded. >>>>>>> At the very beginning it gives something like "gpt sector >>>>>>> error, >>>>>>> gpt sector 1 error, can't find zroot..." >>>>>>> >>>>>>> Is it a known error / should I give more (precise) errors? >>>>>>> >>>>>>> I tried two recent images with the same result: >>>>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170703-r320599-memstick.img >>>>>>> >>>>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170626-r320360-memstick.img >>>>>>> >>>>>> >>>>>> It turned out GPT and zfs are not usable at this machine. >>>>>> MBR / ZFS works fine. >>>>>> >>>>>> I'll stick with that. >>>>> >>>>> What type of machine is it? >>>> >>>> It's a PC circa 2009 with MB ASUS P5QL/EPU: >>>> --- >>>> CPU: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz (2799.52-MHz >>>> K8-class CPU) >>>> Origin="GenuineIntel" Id=0x1067a Family=0x6 Model=0x17 Stepping=10 >>>> >>>> >>>> Features=0xbfebfbff >>>> >>>> >>>> >>>> >>>> Features2=0xc08e3bd >>>> >>>> >>>> AMD Features=0x20100800 >>>> AMD Features2=0x1 >>>> VT-x: HLT,PAUSE >>>> TSC: P-state invariant, performance statistics >>>> real memory = 4294967296 (4096 MB) >>>> avail memory = 3324891136 (3170 MB) >>>> Event timer "LAPIC" quality 100 >>>> ACPI APIC Table: >>>> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >>>> FreeBSD/SMP: 1 package(s) x 2 core(s) >>>> --- >>>> >>>> -- >>>> WBR, bsam >>> >>> Of course it really can not be that the BIOS has something against >>> combination of GPT+ZFS, but this combination may trigger some sort of >>> bug/misbehavior. I have seen some pretty weird issues and have work >>> in process to have a bit more fool proof approach, but I haven't had >>> time yet to finalize it properly. >> >> Yep, UFS+GPT works fine here. >> >> Just for archieves: errors for ZFS + GPT >> --- >> gptzfsboot: error 128 lba 3907027040 >> gptzfsboot: error 128 lba 1 >> gptzfsboot: no zfs pools located, can't boot >> --- >> >> The disk is: >> --- >> 512 # sectorsize >> 2000397852160 # mediasize in bytes (1.8T) >> 3907027055 # mediasize in sectors >> 0 # stripesize >> 0 # stripeoffset >> 3876018 # Cylinders according to firmware. >> 16 # Heads according to firmware. >> 63 # Sectors according to firmware. >> WD-WMAUR0112162 # Disk ident. >> Not_Zoned # Zone Mode >> --- >> >> UEFI is not available at the motherboard. >> >>> Namely, what I have found is that in some systems the INT13 ah=08 can >>> result with unexpected results - error from command reported or disk >>> count not reported etc - something not really expected. It also may >>> have to do about what other devices are there. And also if the system >>> has plain BIOS or BIOS emulated on UEFI. >> > > This looks similar to: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 > Please add your information if you think it is the same issue. Or try > the workaround and see if it helps. Yes, the problem seems to be the same. A comment is added. Thank you for the link. -- WBR, bsam ___ 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"
[base pkg] update !GENERIC kernel
Hi All, I use self-made base packages for an ARM board. The kernel I use is IMX6 one. While pkg update I get this: --- [271/302] Upgrading FreeBSD-kernel-imx6-debug from 12.0.s20170718113533 to 12.0.s20170719070514... [271/302] Extracting FreeBSD-kernel-imx6-debug-12.0.s20170719070514: 100% kldxref: //boot/kernel: No such file or directory pkg: POST-INSTALL script failed [272/302] Upgrading FreeBSD-kernel-imx6 from 12.0.s20170718113533 to 12.0.s20170719070514... [272/302] Extracting FreeBSD-kernel-imx6-12.0.s20170719070514: 100% kldxref: //boot/kernel: No such file or directory pkg: POST-INSTALL script failed --- All is fine except those messages. There is no /boot/kernel, but there is /boot/kernel.IMX6. The kernel is defined at /boot/loader.conf: --- kernel="kernel.IMX6" --- Seems that for now pkg can't handle non-default kernel. Should I just ignore those messages? Or should I run some post-update commands/scripts by hand? BTW, I did not find any evidence of POST-INSTALL scripts at the .txz file. Are they hard-coded at pkg? -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: [base pkg] update !GENERIC kernel
20.07.2017 02:05, Ben Woods пишет: > On Wed, 19 Jul 2017 at 7:37 pm, Boris Samorodov wrote: > >> Hi All, >> >> I use self-made base packages for an ARM board. The kernel I use >> is IMX6 one. While pkg update I get this: >> --- >> [271/302] Upgrading FreeBSD-kernel-imx6-debug from 12.0.s20170718113533 >> to 12.0.s20170719070514... >> [271/302] Extracting FreeBSD-kernel-imx6-debug-12.0.s20170719070514: >> 100% >> kldxref: //boot/kernel: No such file or directory >> pkg: POST-INSTALL script failed >> [272/302] Upgrading FreeBSD-kernel-imx6 from 12.0.s20170718113533 to >> 12.0.s20170719070514... >> [272/302] Extracting FreeBSD-kernel-imx6-12.0.s20170719070514: 100% >> >> kldxref: //boot/kernel: No such file or directory >> pkg: POST-INSTALL script failed >> --- >> >> All is fine except those messages. >> >> There is no /boot/kernel, but there is /boot/kernel.IMX6. The kernel >> is defined at /boot/loader.conf: >> --- >> kernel="kernel.IMX6" >> --- >> >> Seems that for now pkg can't handle non-default kernel. Should I just >> ignore those messages? Or should I run some post-update commands/scripts >> by hand? > > > I had the same problem on my machine using pkg-base with a non-default > named kernel package. > > As a workaround, I created a symlink at /boot/kernel pointing to the > correct kernel directory. This seemed to fix the problem, but required this > manual intervention. Yep, I've end up doing the same. Thank you. > It would be good if this wasn't required, and the kernel package used the > kernel parameter in loader.conf to determine where to run the post-install > script. -- WBR, bsam ___ 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"
[tzsetup] can't set up local timezone if CMOS is set to UTC
Hi Marius, All, Subj at today's amd64-HEAD. If I use command "sudo tzsetup" and choose YES (CMOS clock is set to UTC), the program just quits. Yea, my clocks are at UTC but I want to get time at local timezone. :-) I've found a recent commit to tzsetup, is it the cause? -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: [tzsetup] can't set up local timezone if CMOS is set to UTC
07.08.2017 09:44, Boris Samorodov пишет: Hi Marius, All, Subj at today's amd64-HEAD. If I use command "sudo tzsetup" and choose YES (CMOS clock is set to UTC), the program just quits. Yea, my clocks are at UTC but I want to get time at local timezone. :-) I've found a recent commit to tzsetup, is it the cause? Hm. There is a log message at r322097: --- - Make the initial UTC dialog actually work by giving the relevant files the necessary treatment and then exit when choosing "Yes" there instead of moving on to the time zone menu regardless. --- I must misunderstand something. So my question is: how to set up local time zone if CMOS is set to UTC? -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: [tzsetup] can't set up local timezone if CMOS is set to UTC
07.08.2017 10:54, Trond Endrestøl пишет: On Mon, 7 Aug 2017 09:51+0300, Boris Samorodov wrote: So my question is: how to set up local time zone if CMOS is set to UTC? My timezone is Europe/Oslo, adjust to fit your timezone: rm -f /etc/wall_cmos_clock cp -p /usr/share/zoneinfo/Europe/Oslo /etc/localtime echo Europe/Oslo > /var/db/zoneinfo Done. Got UTC time marked as local time. (Five minutes later) Ntpdate fixed it, now local time is OK. Thank you, Trond. And (seems to be) the final question: can that be done via tzsetup (as it used to be)? -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: [tzsetup] can't set up local timezone if CMOS is set to UTC
08.08.2017 00:48, Marius Strobl пишет: On Mon, Aug 07, 2017 at 09:51:15AM +0300, Boris Samorodov wrote: 07.08.2017 09:44, Boris Samorodov ?: Hi Marius, All, Subj at today's amd64-HEAD. If I use command "sudo tzsetup" and choose YES (CMOS clock is set to UTC), the program just quits. Yea, my clocks are at UTC but I want to get time at local timezone. :-) I've found a recent commit to tzsetup, is it the cause? Hm. There is a log message at r322097: --- - Make the initial UTC dialog actually work by giving the relevant files the necessary treatment and then exit when choosing "Yes" there instead of moving on to the time zone menu regardless. --- I must misunderstand something. So my question is: how to set up local time zone if CMOS is set to UTC? Yeah, I hadn't thought of the case where one would like to set up a configuration in which the RTC is using UTC but the timezone is not. I've used this configuration, well, almost forever. ;-) As Kevin has already said and my habit is to set a unix machine CMOS to UTC. So I've reverted the corresponding part of r322097 for now Confirmed, tzsetup works as expected (at least for me). Thank you for quick fix and response. as I don't see an obvious way to give /etc/wall_cmos_clock appropriate treatment in all 3 relevant cases (UTC/UTC, !UTC/UTC and !UTC/!UTC regarding RTC/timezone) for all interactive and non-interactive ways of using tzsetup(8). -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: sys/conf/newvers.sh vs. subversion-1.7
22.10.2011 22:12, Doug Barton пишет:
> On 10/22/2011 08:29, Garrett Cooper wrote:
>> $(svn info | awk '/^Revision:/ {print $2}')
>
> 2 subshells and a pipe for this, vs. only 1 subshell for just running
> svnversion.
>
> Anyone else want to propose a more complex solution when a simple and
> more effective one already exists? :)
I'm not an exert here, so I'm not sure which one and why did you call
"simple and more effective":
-
% uname -a
FreeBSD bsam.tel.ru 9.0-BETA2 FreeBSD 9.0-BETA2 #32 r225746: Sat Sep 24
17:00:42 MSK 2011 b...@bsam.tel.ru:/usr/obj/usr/src/sys/BB i386
% time svnversion /usr/src
226160
svnversion /usr/src 8,80s user 7,12s system 16% cpu 1:34,16 total
% time (svn info /usr/src | awk '/^Revision:/ {print $2}')
226160
( svn info /usr/src | awk '/^Revision:/ {print $2}'; ) 0,00s user 0,00s
system 16% cpu 0,013 total
-
--
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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: Cross-architecture compiling
Hi All,
23.11.2011 18:37, Jan Dušátko пишет:
> Hi,
>
> I would like to ask people in this conference for advice regards
> cross-architecture compiling.
> Right now I have 32-bit system, where I need to boot over TFTP/NFS diferrent
> architectures (i386/AMD64). I need to populate appropriate directory
> structure using some "generalized" kernel configuration, each platform have
> thein own kernel.conf.
At my previous $JOB we configured an amd64 system to load i386 diskless
stations.
> I did those steps bellow, but this not work. Can someone help me?
"Not work" is not a diagnostic message. Please, be more specific here.
> Regards
>
> Jan
>
>
> #!bin/sh
> export CC="/usr/cross/usr/bin/gcc"
> export AS="/usr/cross/usr/bin/as"
> export NM="/usr/cross/usr/bin/nm"
> export RANLIB=/usr/cross/usr/bin/ranlib"
> export LD="/usr/cross/usr/bin/ld"
> export OBJCOPY="/usr/cross/usr/bin/objcopy"
> export SIZE="/usr/cross/usr/bin/size"
> export CPUTYPE="native"
I'm not sure if those varialbes are needed.
> export KERNCONF=""
Well, does this really work? Is it the same as KERNCONF=GENERIC?
Not sure.
> for TARGET_ARCH in i386 amd64
> do
> export MACHINE=${TARGET_ARCH}
> export MACHINE_ARCH=${TARGET_ARCH}
> export DESTDIR="/pxeboot/diskless/${TARGET_ARCH}"
> mkdir $DESTDIR
> mkdir -p ${DESTDIR}usr/bin
> mkdir -p ${DESTDIR}usr/lib
> mkdir -p ${DESTDIR}usr/include
> mkdir -p ${DESTDIR}usr/share/man/man1
> mkdir -p ${DESTDIR}usr/share/info
> mkdir -p ${DESTDIR}usr/libdata/ldscripts
> mkdir -p ${DESTDIR}usr/libexec
> cd /usr/obj
> rm -rf usr
> cd /usr/src
> make world TARGET_ARCH=$TARGET_ARCH TOOLS_PREFIX=$DESTDIR
> DESTDIR=$DESTDIR install
> make kernel TARGET_ARCH=$TARGET_ARCH TOOLS_PREFIX=$DESTDIR
> DESTDIR=$DESTDIR install
I'm not sure about TOOLS_PREFIX (do not recall we used it).
> cd etc
I'd say this is not needed.
> make distribution
And that should be "make distribution DESTDIR=$DESTDIR".
> mkdir $DESTDIR/boot
That directory should already present.
And the rest I don't understand (may be OK).
> cp /boot/device.hints $DESTDIR/boot
> done
> mkdir -p /pxeboot/diskless/conf/default/etc
> ln -s /pxeboot/diskless/conf/default /pxeboot/diskless/i386/conf/default
> ln -s /pxeboot/diskless/conf/default /pxeboot/diskless/amd64/conf/default
--
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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: 9.1-RC3 feels okay :-)
07.11.2012 01:14, CeDeROM пишет: > I have also noted that mouse cursor is very often not moving in Xorg > but it works in the console! I need to move cursor while statrx or > restart Xorg for mouse to start moving. Is it a bug or feature? :-) > > In the xorg.conf: > Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" "auto" > Option "Device" "/dev/sysmouse" > Option "ZAxisMapping" "4 5 6 7" > EndSection You may be interested in: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/171433 If the patch from the PR helps you, please submit a follow-up to the PR. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: 9.1-RC3 feels okay :-)
07.11.2012 11:57, Boris Samorodov пишет: > 07.11.2012 01:14, CeDeROM пишет: >> I have also noted that mouse cursor is very often not moving in Xorg >> but it works in the console! I need to move cursor while statrx or >> restart Xorg for mouse to start moving. Is it a bug or feature? :-) >> >> In the xorg.conf: >> Section "InputDevice" >> Identifier "Mouse0" >> Driver "mouse" >> Option "Protocol" "auto" >> Option "Device" "/dev/sysmouse" >> Option "ZAxisMapping" "4 5 6 7" >> EndSection > > You may be interested in: > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/171433 > > If the patch from the PR helps you, please submit a follow-up > to the PR. Well, actually I've just committed an upstream patch to x11-drivers/xf86-input-mouse. Please give it a try. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: 9.1-RC3 feels okay :-)
08.11.2012 12:46, CeDeROM пишет: > With no hald and dbus mouse and keyboard does not work in xorg Do you mean "that if xorg-server is compiled with hal but you do not launch it at startup" mouse and keyboard does not work? If yes, I'd say that this is a bit... expected. ;-) -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: 9.1-RC3 default Linux ALSA configuration
02.12.2012 19:20, CeDeROM пишет:
> On Fri, Nov 30, 2012 at 2:45 PM, CeDeROM wrote:
>> I have installed and started Skype (2.1 and 2.2 devel) with success
>> using Linux binaries provided in port tree. However there is an issue
>> with default ALSA configuration and sound/calls does not work properly
>> off out the box. I suggest to set /dev/dsp0 and /dev/mixer0 as default
>> devices in the alsa configuration, so the sound works on the default
>> audio device. Right now it does not work at all.
>>
>> # pcm-oss plugin configuration
>>
>> pcm.oss {
>> type oss
>> device /dev/dsp0
>> hint {
>> description "Open Sound System"
>> }
>> }
>>
>> ctl.oss {
>> type oss
>> device /dev/mixer0
>> hint {
>> description "Open Sound System"
>> }
>> }
> Or maybe there is another way to set /dev/dsp to be /dev/dsp0 (or
> others) at system level? That would be even better that setting every
> config file by hand, just to point to the default dsp device :-)
I've just committed a fix to linux-f10-alsa-lib port. The port now
creates a soft link to the native FreeBSD configuration file at
LINUXBASE. That may help here.
--
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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: 9.1-RC3 default Linux ALSA configuration
Hi Tomek, 03.12.2012 01:08, CeDeROM пишет: > What is the native configuration file location? I only > have /compat/linux/etc/alsa/pcm/pcm-oss.conf file. It's the configuration file that is installed by audio/alsa-lib: LOCALBASE/etc/asound.conf. As for the rest, I'm not an expert with sound, sorry. :-( Hope somebody else may help you. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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"
The line "World build completed on..." disappeared from the build log
Hi All, not so far (a week or two?) the line with starting date and time of the world build has disappeared. That seems to be unintentional because the corresponding "stop" line is there. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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"
the line moved down (was: The line "World build completed on..." disappeared from the build log)
12.01.2013 16:49, Boris Samorodov пишет: > Hi All, > > not so far (a week or two?) the line with starting date > and time of the world build has disappeared. That seems > to be unintentional because the corresponding "stop" line > is there. Hm, sorry, the line happen to be the first one and now it appears a little bit later. Was this move intentional? -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: 7+ days of dogfood
10.02.2013 04:07, Steve Kargl пишет: As for me I use CURRENT at my JOB for many years now. I used to i386 but switched to amd64 at the end of 2012. The system (both world and kernel) are updated every week or two. I had switched to clang very early. There were problems with ports I used but not now: gimp, inkscape, scribus, texlive, thunderbird, firefox, libreoffice (didn't try the latest version, ENOTIME). One option that I abandoned was WITH_LIBCPLUSPLUS. I tried it last summer but the system went very unstable. Didn't have a chance to test it since then. One option that I use has been already mentioned -- MALLOC_PRODUCTION. > CPUTYPE?=core2 I never use this option. It was very long ago that I was beaten by it, but don't like it since. > FFLAGS = -O2 -pipe -march=native -mtune=native I don't like using "=" for FLAGS at make.conf... > FFLAGS+= -funroll-loops -ftree-vectorize ... as well as defaults overriding. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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"
/usr/bin/strip: File format not recognized
Hi!
I'm not sure but it seems to me that the question is more about
-current that -ports.
While updating devel/nspr I get this:
-
cc -o plgetopt.o -c -fvisibility=hidden-O2 -pipe
-fno-strict-aliasing -ansi -Wall -fPIC -UDEBUG -DNDEBUG=1
-DHAVE_VISIBILITY_HIDDEN_ATTRIBUTE=1 -DHAVE_VISIBILITY_PRAGMA=1
-DXP_UNIX=1 -DFREEBSD=1 -DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1
-DHAVE_LCHOWN=1 -DHAVE_STRERROR=1 -DHAVE_DLADDR=1 -D_REENTRANT=1
-D_THREAD_SAFE=1 -DFORCE_PR_LOG -D_PR_PTHREADS -UHAVE_CVAR_BUILT_ON_SEM
-I../../../dist/include/nspr ../../.././../lib/libc/src/plgetopt.c
rm -f libplc4.a
/usr/bin/ar cr libplc4.a ./plvrsion.o ./strlen.o ./strcpy.o ./strdup.o
./strcase.o ./strcat.o ./strcmp.o ./strchr.o ./strpbrk.o ./strstr.o
./strtok.o ./base64.o ./plerror.o ./plgetopt.o
ranlib libplc4.a
rm -f libplc4.so.1
cc -shared -Wl,-soname -Wl,libplc4.so.1 -o libplc4.so.1 ./plvrsion.o
./strlen.o ./strcpy.o ./strdup.o ./strcase.o ./strcat.o ./strcmp.o
./strchr.o ./strpbrk.o ./strstr.o ./strtok.o ./base64.o ./plerror.o
./plgetopt.o -L../../../dist/lib -lnspr4
../../../config/./nsinstall -R -m 444 ./libplc4.a ./libplc4.so.1
../../../dist/lib
../../../config/./nsinstall -R -m 444 ./libplc4.so.1 ../../../dist/bin
gmake[3]: Выход из каталога
`/usr/ports/devel/nspr/work/nspr-4.9/mozilla/nsprpub/build/lib/libc/src'
gmake[2]: Выход из каталога
`/usr/ports/devel/nspr/work/nspr-4.9/mozilla/nsprpub/build/lib/libc'
gmake[1]: Выход из каталога
`/usr/ports/devel/nspr/work/nspr-4.9/mozilla/nsprpub/build/lib'
#
# Please, consider running ``make test'' to find any
# possible build problems.
#
===> Installing for nspr-4.9
===> Generating temporary packing list
===> Checking if devel/nspr already installed
/bin/mkdir -p /usr/local/include/nspr
/usr/bin/tar -C
/usr/ports/devel/nspr/work/nspr-4.9/mozilla/nsprpub/build/dist/include
--dereference -cf - . | /usr/bin/tar -C /usr/local/include -xof -
/usr/bin/find /usr/local/include/nspr -type d | /usr/bin/xargs
/bin/chmod 0755
/usr/bin/find /usr/local/include/nspr -type f | /usr/bin/xargs
/bin/chmod 444
/usr/bin/tar -C
/usr/ports/devel/nspr/work/nspr-4.9/mozilla/nsprpub/build/dist/lib
--dereference -cf - . | /usr/bin/tar -C /usr/local/lib -xof -
install -o root -g wheel -m 555
/usr/ports/devel/nspr/work/nspr-4.9/mozilla/nsprpub/build/config/nspr-config
/usr/local/bin
/bin/mkdir -p /usr/local/libdata/pkgconfig
install -o root -g wheel -m 444
/usr/ports/devel/nspr/work/nspr-4.9/mozilla/nsprpub/build/config/nspr.pc
/usr/local/libdata/pkgconfig
/usr/bin/strip /usr/local/lib/libnspr4.so.1
/usr/bin/strip: /usr/local/lib/libnspr4.so.1: File format not recognized
*** [do-install] Error code 1
Stop in /usr/ports/devel/nspr.
-
This is current built with clang:
-
% uname -a
FreeBSD bsam.wart.ru 10.0-CURRENT FreeBSD 10.0-CURRENT #1 r232957: Wed
Mar 14 14:14:49 SAMT 2012 b...@bsam.wart.ru:/usr/obj/usr/src/sys/BBX
i386
-
My /etc/make.conf:
-
.if ${.CURDIR:N*usr/src*} == ""
. if !defined(_WITHOUT_SRCCONF)
SRCCONF?=/etc/src.conf
. if exists(${SRCCONF})
. include "${SRCCONF}"
. endif
. endif
.endif
###
### Ports section
###
EXPLICIT_PACKAGE_DEPENDS= YES
WITH_CUPS= YES
WITHOUT_LPR=YES
CUPS_OVERWRITE_BASE=YES
WANT_OPENLDAP_SASL= YES
LOCALIZED_LANG=ru
QT4_OPTIONS=CUPS NAS QGTKSTYLE
WITHOUT_NOUVEAU=YES
THUNDERBIRD_I18N= ru
.if ${.CURDIR:M*/editors/openoffice.org-3}
WITHOUT_MOZILLA=YES
WITH_TTF_BYTECODE_ENABLED=YES
.endif
# added by use.perl 2012-03-12 14:27:00
PERL_VERSION=5.12.4
-
How can I diagnoze/overcome this? Thanks!
--
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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: /usr/bin/strip: File format not recognized
24.03.2012 00:12, Boris Samorodov пишет: > /usr/bin/strip /usr/local/lib/libnspr4.so.1 > /usr/bin/strip: /usr/local/lib/libnspr4.so.1: File format not recognized Actually the file is corrupt: - % file /usr/local/lib/* | grep -A5 -B5 nspr /usr/local/lib/libnettle.so.4.3: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), dynamically linked, not stripped /usr/local/lib/libnotify.a:current ar archive /usr/local/lib/libnotify.la: libtool library file /usr/local/lib/libnotify.so: symbolic link to `libnotify.so.4' /usr/local/lib/libnotify.so.4: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), dynamically linked, not stripped /usr/local/lib/libnspr4.a: data /usr/local/lib/libnspr4.so.1: data /usr/local/lib/libogg.a: current ar archive /usr/local/lib/libogg.la: libtool library file /usr/local/lib/libogg.so: symbolic link to `libogg.so.7' /usr/local/lib/libogg.so.7:ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), dynamically linked, not stripped /usr/local/lib/liboldX.a: current ar archive- -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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"
/usr/bin/tar creates invalid lib file (was: Re: /usr/bin/strip: File format not recognized)
On 24.03.2012 01:29, Dimitry Andric wrote: On 2012-03-23 21:12, Boris Samorodov wrote: I'm not sure but it seems to me that the question is more about -current that -ports. While updating devel/nspr I get this: ... /usr/bin/strip: /usr/local/lib/libnspr4.so.1: File format not recognized It builds and installs fine here, both on i386 and amd64, using both gcc and clang. What is the output of: "file /usr/local/lib/libnspr4.so.1" on your system? I've done some steps to diagnose the case. Seems that /usr/bin/tar does not create correct library: - % file /usr/ports/devel/nspr/work/nspr-4.9/mozilla/nsprpub/build/dist/lib/../../pr/src/./libnspr4.so.1 /usr/ports/devel/nspr/work/nspr-4.9/mozilla/nsprpub/build/dist/lib/../../pr/src/./libnspr4.so.1: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), dynamically linked, not stripped % file /usr/local/lib/libnspr4.so.1 /usr/local/lib/libnspr4.so.1: data % hd -C /usr/local/lib/libnspr4.so.1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * % tar --version bsdtar 3.0.3 - libarchive 3.0.3 - The library (/usr/local/lib/libnspr4.so.1) is created by the command: - /usr/bin/tar -C /usr/ports/devel/nspr/work/nspr-4.9/mozilla/nsprpub/build/dist/lib --dereference -cf - . | /usr/bin/tar -C /usr/local/lib -xof - - -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: /usr/bin/tar creates invalid lib file
24.03.2012 19:04, Garrett Cooper пишет: > On Fri, Mar 23, 2012 at 9:51 PM, Boris Samorodov wrote: >> On 24.03.2012 01:29, Dimitry Andric wrote: >>> >>> On 2012-03-23 21:12, Boris Samorodov wrote: >>>> >>>> I'm not sure but it seems to me that the question is more about >>>> -current that -ports. >>>> >>>> While updating devel/nspr I get this: >>> >>> ... >>>> >>>> /usr/bin/strip: /usr/local/lib/libnspr4.so.1: File format not recognized >>> >>> >>> It builds and installs fine here, both on i386 and amd64, using both gcc >>> and clang. >>> >>> What is the output of: "file /usr/local/lib/libnspr4.so.1" on your >>> system? >> >> >> I've done some steps to diagnose the case. Seems that /usr/bin/tar >> does not create correct library: >> - >> % file >> /usr/ports/devel/nspr/work/nspr-4.9/mozilla/nsprpub/build/dist/lib/../../pr/src/./libnspr4.so.1 >> /usr/ports/devel/nspr/work/nspr-4.9/mozilla/nsprpub/build/dist/lib/../../pr/src/./libnspr4.so.1: >> ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), dynamically >> linked, not stripped >> % file /usr/local/lib/libnspr4.so.1 >> /usr/local/lib/libnspr4.so.1: data >> % hd -C /usr/local/lib/libnspr4.so.1 >> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> || >> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> || >> * >> % tar --version >> bsdtar 3.0.3 - libarchive 3.0.3 >> - >> >> The library (/usr/local/lib/libnspr4.so.1) is created by the command: >> - >> /usr/bin/tar -C >> /usr/ports/devel/nspr/work/nspr-4.9/mozilla/nsprpub/build/dist/lib >> --dereference -cf - . | /usr/bin/tar -C /usr/local/lib -xof - > > All that does is shuffle around files; it doesn't make any libraries. > The question I'd have is are there multiple instances running in > parallel, or not? Since I tried the command by hand and got the same result as while using the port, I assume that the answer is "no, there are not". -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: /usr/bin/tar creates invalid lib file
24.03.2012 21:00, Tim Kientzle пишет: > Can you send me the output of: Sure. I'll do it tomorrow (the machine is at work). -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: /usr/bin/tar creates invalid lib file
On 24.03.2012 21:00, Tim Kientzle wrote: On Mar 23, 2012, at 9:51 PM, Boris Samorodov wrote: On 24.03.2012 01:29, Dimitry Andric wrote: On 2012-03-23 21:12, Boris Samorodov wrote: I'm not sure but it seems to me that the question is more about -current that -ports. While updating devel/nspr I get this: ... /usr/bin/strip: /usr/local/lib/libnspr4.so.1: File format not recognized It builds and installs fine here, both on i386 and amd64, using both gcc and clang. What is the output of: "file /usr/local/lib/libnspr4.so.1" on your system? I've done some steps to diagnose the case. Seems that /usr/bin/tar does not create correct library: - % file /usr/ports/devel/nspr/work/nspr-4.9/mozilla/nsprpub/build/dist/lib/../../pr/src/./libnspr4.so.1 /usr/ports/devel/nspr/work/nspr-4.9/mozilla/nsprpub/build/dist/lib/../../pr/src/./libnspr4.so.1: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), dynamically linked, not stripped % file /usr/local/lib/libnspr4.so.1 /usr/local/lib/libnspr4.so.1: data % hd -C /usr/local/lib/libnspr4.so.1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * % tar --version bsdtar 3.0.3 - libarchive 3.0.3 - The library (/usr/local/lib/libnspr4.so.1) is created by the command: - /usr/bin/tar -C /usr/ports/devel/nspr/work/nspr-4.9/mozilla/nsprpub/build/dist/lib --dereference -cf - . | /usr/bin/tar -C /usr/local/lib -xof - - Can you send me the output of: tar -cvf /tmp/test.tar /usr/ports/devel/nspr/work/nspr-4.9/mozilla/nsprpub/build/dist/lib/../../pr/src/./libnspr4.so.1 (A tar archive containing only that one source file.) This looks similar to a bug that we found in libarchive recently I didn't think that bug impacted FreeBSD, but I may have been wrong…. if it did, it will be obvious from the structure of the created archive. The following file is extracted after tarring: - % hd libnspr4.so.1 32 0a 30 0a 30 0a 32 34 31 39 37 31 0a 30 0a 00 |2.0.0.241971.0..| 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 0200 - The tar file itself attached (3KB in length). -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve test.tar Description: Binary data ___ 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"
