Re: 9.1-RELEASE slow boot
On Fri, Jun 7, 2013 at 11:04 PM, Polytropon free...@edvax.de wrote: On Fri, 7 Jun 2013 19:38:34 +0200, Fernando Apesteguía wrote: Since I updated to 9.1-RELEASE my boot process seems to stall for a while. Booting in verbose mode shows messages like these ones: Opening device da0 - 6 (repeated like 30 times or so) Opening device da1 - 6 (repeated like 30 times or so) Opening device da2 - 6 (repeated like 30 times or so) Opening device da3 - 6 (repeated like 30 times or so) Those devices correspond to my internal SD card reader that doesn't work on FreeBSD anyway. This seems some kind of probing right? I don't want to wait for those devices. What can I do to speed up booting? I didn't change my system settings either. Did anything related change in the kernel about probing these type of devices? For comparable reasons in the past, I added the following setting to my kernel configuration: options SCSI_DELAY=100 The default value is 5000. It's the delay in milliseconds for the SCSI probe. Hi, Sorry for my late response (sometimes real life comes first). SCSI_DELAY in the code didn't change between 9.1[1] and 9.0[2] neither did it in the configuration for the GENERIC kernels[3][4]. On both occasions (9.0 and 9.1) I used the GENERIC kernels and I didn't change this setting. I will give it a try as soon as I can, but it still seems a little strange to me that this process takes longer in 9.1 for no apparent reason Thanks. [1] http://fxr.watson.org/fxr/source/cam/scsi/scsi_all.c?v=FREEBSD91#L76 [2] http://fxr.watson.org/fxr/source/cam/scsi/scsi_all.c?v=FREEBSD90#L76 [3] http://svn.freebsd.org/base/releng/9.1/sys/amd64/conf/GENERIC [4] http://svn.freebsd.org/base/releng/9.0/sys/amd64/conf/GENERIC -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: How to switch Datgram/Connected mtu modes?
Hi. Yes. There is no such entry. The only way I found is to compile inside the kernel options IPOIB_CM . Can I do it manually without compiling the kernel each time I want to switch between the modes? Maybe add it somehow to sysctl or loader.conf? Regards, Alex Liptsin Software Quality Assurance Engineer | Mellanox Technologies Ltd. Office: +972 (74) 7236141 Mobile: +972(54) 7833986 Fax: +972(74) 7236161 Email: al...@mellanox.com Mellanox, Tel-Hai Industrial Park. Building 7, M.P. Upper Galilee 12100 Israel -Original Message- From: John Baldwin [mailto:j...@freebsd.org] Sent: Wednesday, May 29, 2013 9:17 PM To: freebsd-...@freebsd.org Cc: Alex Liptsin; freebsd-questions@freebsd.org Subject: Re: How to switch Datgram/Connected mtu modes? On Sunday, May 26, 2013 7:43:29 am Alex Liptsin wrote: Hello. I work with FreeBSD 9.1 and Mellanox devices. How can I configure MTU in connected mode on FreeBSD 9.1? In Linux to enable connected mode for interface ib0, I enter: echo connected /sys/class/net/ib0/mode Switching between CM and UD mode can be done in run time: echo datagram /sys/class/net/ib0/mode sets the mode of ib0 to UD echo connected /sys/class/net/ib0/mode sets the mode ib0 to CM There is no such directories at FreeBSD. Wat shall I do? Have you tried looking for dev.ib.0 sysctls? It looks like the OFED bits in FreeBSD map Linux sysfs entries to sysctl nodes, but I don't have a box with IB handy to see what it looks like at runtime. -- John Baldwin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Bourne shell if syntax
On 10.06.2013 20:53, lcon...@go2france.com wrote: script fragment: PTR=`dig @some.dns +short +norec -x a.b.c.d` echo $PTR if [ $PTR ==] ; then Use something like (== is wrong, btw.) #!/bin/sh if [ X$1 = X ] ; then echo foo fi -- Christoph echo $PTR /path/to/PTR_absent.txt fi === output for an IP: a-b-c-d.domain.net. [: a-b-c-d.domain.net.: unexpected operator thanks Len ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mail/claws-mail: exporting mail filters?
On Sat, 08 Jun 2013 10:11:52 +0200 Herbert J. Skuhra hsku...@eumx.net wrote: On Sat, 8 Jun 2013 09:04:12 +0200 O. Hartmann ohart...@zedat.fu-berlin.de wrote: Since I use on several boxes private and in the deprtment the same email accounts, I'd like to export the mail filters I created and import them to other boxes. I didn't figure out yet how to perform this task on claws-mail. I realized that this is still a point still under construction on close to every platform I used for mailing. Does anyone has an idea? 1. Ask on the claws mailing list? 2. Use a search engine? 3. Search the claws mailing list archive on gmane? 4. Read the claws-mail man page? 5. Copy ~/.claws-mail/matcherrc? Thanks. O. signature.asc Description: PGP signature
Cannot make open-vm-tools on 9.1
Hi, I have a strange thin happening to me. I upgraded two machines from 8.3 to 9.1: FreeBSD sysl2.cs.ait.ac.th 9.1-RELEASE-p3 FreeBSD 9.1-RELEASE-p3 #3: Fri May 31 14:59:20 ICT 2013 root@fbsd63:/usr/obj/usr/src/sys/GENERIC i386 I did both upgrade in parallel. On the first machine, I managed to intall open-vm-tools-nox11: open-vm-tools-nox11-425873_3,1 Open VMware tools for FreeBSD VMware guests but when I try to install it on the second machine, I have a compile error (see below). Now I try to rebuild open-vm-tools on the first machine and I get the same compile error. I am at lost at what is happening and what I should try. On a side note, I noticed that /usr/include/sys/types.h and /usr/src/sys/sys/include/types.h are different; the first one appearing to be quite older (older version number). I did the system upgrade in a very standard way (cvsup, make buildworld, make kernel, make installworld, mergemaster, etc.). Why the discrepancies? Help is needed... TIA, Olivier The failling compile of open-vm-tools Making all in modules make VM_UNAME=9.1-RELEASE-p3 MV=mv RM=rm OVT_SOURCE_DIR=/usr/ports/emulators/open-vm-tools-nox11/work/open-vm-tools-8.6.0-425873 MODULEBUILDDIR=/usr/ports/emulators/open-vm-tools-nox11/work/open-vm-tools-8.6.0-425873/modules/freebsd -C /usr/ports/emulators/open-vm-tools-nox11/work/open-vm-tools-8.6.0-425873/modules/freebsd/vmmemctl cc1: warnings being treated as errors In file included from @/sys/types.h:44, from @/sys/param.h:86, from /usr/ports/emulators/open-vm-tools-nox11/work/open-vm-tools-8.6.0-425873/lib/include/vm_basic_types.h:225, from os.c:36: ./machine/endian.h: In function '__bswap64': ./machine/endian.h:123: warning: right shift count = width of type ./machine/endian.h:123: warning: right shift count = width of type ./machine/endian.h:123: warning: left shift count = width of type ./machine/endian.h:123: warning: left shift count = width of type ./machine/endian.h:123: warning: left shift count = width of type ./machine/endian.h:123: warning: left shift count = width of type ./machine/endian.h:123: warning: left shift count = width of type In file included from @/sys/param.h:86, from /usr/ports/emulators/open-vm-tools-nox11/work/open-vm-tools-8.6.0-425873/lib/include/vm_basic_types.h:225, from os.c:36: @/sys/types.h: At top level: @/sys/types.h:92: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cap_rights_t' In file included from @/sys/param.h:114, from /usr/ports/emulators/open-vm-tools-nox11/work/open-vm-tools-8.6.0-425873/lib/include/vm_basic_types.h:225, from os.c:36: @/sys/time.h: In function 'bintime2timespec': @/sys/time.h:112: warning: right shift count = width of type @/sys/time.h:112: warning: right shift count = width of type @/sys/time.h: In function 'bintime2timeval': @/sys/time.h:129: warning: right shift count = width of type @/sys/time.h:129: warning: right shift count = width of type In file included from @/sys/systm.h:42, from os.c:38: ./machine/cpufunc.h: In function 'rdmsr': ./machine/cpufunc.h:311: warning: left shift count = width of type ./machine/cpufunc.h: In function 'rdpmc': ./machine/cpufunc.h:320: warning: left shift count = width of type ./machine/cpufunc.h: In function 'rdtsc': ./machine/cpufunc.h:329: warning: left shift count = width of type ./machine/cpufunc.h: In function 'wrmsr': ./machine/cpufunc.h:350: warning: right shift count = width of type In file included from @/sys/mutex.h:41, from @/sys/eventhandler.h:34, from @/sys/conf.h:44, from os.c:42: @/sys/pcpu.h: At top level: @/sys/pcpu.h:156: error: expected specifier-qualifier-list before 'cpumask_t' In file included from @/vm/pmap.h:89, from os.c:48: ./machine/pmap.h:247: error: expected specifier-qualifier-list before 'cpumask_t' os.c: In function 'os_balloonobject_create': os.c:416: warning: left shift count = width of type os.c:416: warning: left shift count = width of type os.c:416: warning: left shift count = width of type os.c:416: warning: left shift count = width of type *** [os.o] Error code 1 Stop in /usr/ports/emulators/open-vm-tools-nox11/work/open-vm-tools-8.6.0-425873/modules/freebsd/vmmemctl. *** [vmmemctl] Error code 1 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Bourne shell if syntax
On 06/10/2013 21:10, dte...@freebsd.org wrote: Character sentinels are not required. FreeBSD's sh(1) knows (because [ is a built-in) that when you quote a parameter, that it is not (even if the value begins with -) not an operator. What you are saying here is at least misleading. I just started up sh on 9.1 RELEASE and tried: $ A=-z $ if [ $A ] ; then echo z ; fi z $ if [ $A 1 ] ; then echo z ; fi $ if /bin/[ $A ] ; then echo z ; fi z $ if /bin/[ $A 1 ] ; then echo z ; fi $ Although -z is quoted, it is seen as an operator. It does not seem to have anything to do with whether the build-in or external [ is used. Cheers, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: I'm having big problems with Broadcom NIC (gbe0) on HP ProLiant DL380p 128GB Ram, NIC model HP Ethernet 1Gb 4-port 331FLR, after installed it cannot use a ping command, sometime it can do that but
On Tue, Jun 11, 2013 at 8:08 PM, Surat Sodchuen carbopol...@gmail.comwrote: thank for your kindness i tired that your suggestion but cannot resolve problem. for more information ... FreeBSD 9.1-Release on HP ProLiant DL380p Gen8 128GB of Ram every time when booting process it seem freezing about 15 seconds dmesg look like this . . . ACPI Warning: invalid length for Pm1aControlBlock: 32, using default 16 (20110527/tbfadt-638) ACPI Warning: invalid length for Pm1aControlBlock: 32, using default 16 (20110527/tbfadt-638) . . . pci0:3:0:0: failed to read VPD data. bge0: Broadcom unknown BCM5719, ASIC rev. 0x5719001 mem 0xfabf-0xfabf, . . . bge0: link state changed to DOWN bge0: link state changed to UP bge0: link state changed to DOWN bge0: link state changed to UP bge0: link state changed to DOWN bge0: link state changed to UP bge0: link state changed to DOWN bge0: link state changed to UP bge0: link state changed to DOWN bge0: link state changed to UP bge0: link state changed to DOWN bge0: link state changed to UP bge0: link state changed to DOWN bge0: link state changed to UP bge0: link state changed to DOWN bge0: link state changed to UP bge0: link state changed to DOWN bge0: link state changed to UP - when i use a ping command it seem freezing, then after press Enter it show -- bge0 watchdog timeout -- resetting i think what happen!!! i use FreeBSD on every 4 of DL380 Gen5, but they are OK. on screen now .. showing message bge0: 2 link states coalesced bge0: 2 link states coalesced bge0: 2 link states coalesced bge0: 2 link states coalesced bge0: 2 link states coalesced bge0: 2 link states coalesced bge0: 2 link states coalesced Forwarding to mailing list to keep it in the loop. It looks like others have run into this issue, and there is an associated bug report: http://www.freebsd.org/cgi/query-pr.cgi?pr=171121 That link contains an explanation of why my suggestion did not help, and a suggestion to check the firmware of the controllers.. It also looks like there's a later version of the bge driver by Pyun YongHyeon that didn't make it into 9.1-RELEASE that might resolve your issue, were you to compile it yourself. Regards, JB ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
information about configurable load-time parameters
Hi, I'm using FreeBSD 9.1 and looking for a way to pass a module parameters on load time. I came across the 'TUNABLE' macros which provided a decent solution. The question that remains is how to notify the user about those configurable load-time parameters ? I guess I'm looking for some kind of 'modinfo' which describes those parameters among other things. Thanks, Meny Yossefi | SW Engineer | FreeBSD team Mellanox Technologies Ltd Work: +972-74-7129121, Cell: +972-52-8379557 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Bourne shell if syntax
On Jun 11, 2013, at 2:56 AM, Jan Henrik Sylvester wrote: On 06/10/2013 21:10, dte...@freebsd.org wrote: Character sentinels are not required. FreeBSD's sh(1) knows (because [ is a built-in) that when you quote a parameter, that it is not (even if the value begins with -) not an operator. Appears I was wrong (and I can admit that). Further testing/investigation shows that it's not based on double-quoting (although this DOES play a role -- but only in the fact that you're ensuring that the program -- [ -- only gets one argument -- sans trailing square-bracket). It appears that the divide is the number of arguments. For example, compare: if [ -gt 1 ]; then # arg1 treated as a string; returns success to if [ -gt 1 ]; then # arg1 treated as an operator; syntax error to if [ -gt ]; then # arg1 treated as a string; returns success Or compare the equally divided: A=-gt if [ $A 1 ]; then # arg1 treated as a string; returns success to if [ $A 1 ]; then # arg1 treated as an operator; syntax error to if [ $A ]; then # arg1 treated as a string; returns success When the program -- [ -- (regardless of built-in or external) sees only one argument in it's ARGV array, it will *not* treat the argument as a flag but instead return true if it's non-NULL or return false if NULL. What you are saying here is at least misleading. I just started up sh on 9.1 RELEASE and tried: $ A=-z $ if [ $A ] ; then echo z ; fi z $ if [ $A 1 ] ; then echo z ; fi $ if /bin/[ $A ] ; then echo z ; fi z $ if /bin/[ $A 1 ] ; then echo z ; fi $ Interesting that I do not get the same results on 9.0-R for the external usage. de...@mick.vicor.com ~ $ if /bin/[ $A ] ; then echo z ; fi [: ]: unknown operand de...@mick.vicor.com ~ $ if /bin/[ $A 1 ] ; then echo z ; fi [: ]: unknown operand Must be a bug in 9.0-R with the ending square-bracket (`]'). If I remove the ending square-bracket it runs… de...@mick.vicor.com ~ $ if /bin/[ $A ; then echo z ; fi z de...@mick.vicor.com ~ $ if /bin/[ $A 1 ; then echo z ; fi Although -z is quoted, it is seen as an operator. It does not seem to have anything to do with whether the build-in or external [ is used. You're at least partially right… number of arguments makes a difference. A=-gt if [ $A ]; then echo z; fi sh: line 0: [: -gt: unary operator expected === Meanwhile, it knows to treat it as a string when it's the only argument… A=-gt if [ $A ]; then echo z; fi z -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Fatal trap 12: page fault while in kernel mode in FreeBSD 9.1
Hi, I recently upgraded from 9.0 to 9.1 and have scince been seeing a lot of system freezes. The system will sometimes freeze when I launch an application soon after startup. If it does not freeze soon after startup it tends to run fine for the rest of the day. Full copy of core.txt @ http://pastebin.com/ezfAGGFL --core.txt.0--- FreeBSD quadcore 9.1-RELEASE-p3 FreeBSD 9.1-RELEASE-p3 #0: Mon Apr 29 18:27:25 UTC 2013 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 panic: page fault GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x8008 fault code = supervisor read data, page not present instruction pointer = 0x20:0x80976e19 stack pointer = 0x28:0xff8235870630 frame pointer = 0x28:0xff8235870660 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 1720 (mount_fusefs) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0x809208d6 at kdb_backtrace+0x66 #1 0x808ea8ee at panic+0x1ce #2 0x80bd8270 at trap_fatal+0x290 #3 0x80bd85ad at trap_pfault+0x1ed #4 0x80bd8bce at trap+0x3ce #5 0x80bc318f at calltrap+0x8 #6 0x8261a2f4 at fuse_mount+0x94 #7 0x80979371 at vfs_donmount+0x1081 #8 0x80979ad6 at sys_nmount+0x66 #9 0x80bd7b16 at amd64_syscall+0x546 #10 0x80bc3477 at Xfast_syscall+0xf7 Uptime: 4m32s Dumping 545 out of 8156 MB:..3%..12%..21%..33%..42%..53%..62%..71%..83%..91% ... (kgdb) #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 #1 0x808ea3d1 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:448 #2 0x808ea8c7 in panic (fmt=0x1 Address 0x1 out of bounds) at /usr/src/sys/kern/kern_shutdown.c:636 #3 0x80bd8270 in trap_fatal (frame=0xc, eva=Variable eva is not available. ) at /usr/src/sys/amd64/amd64/trap.c:857 #4 0x80bd85ad in trap_pfault (frame=0xff8235870580, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:773 #5 0x80bd8bce in trap (frame=0xff8235870580) at /usr/src/sys/amd64/amd64/trap.c:456 #6 0x80bc318f in calltrap () at /usr/src/sys/amd64/amd64/exception.S:228 #7 0x80976e19 in vfs_getopts (opts=0x8008, name=0x82621368 fspath, error=0xff82358707ac) at /usr/src/sys/kern/vfs_mount.c:1516 #8 0x8261a2f4 in fuse_mount () from /usr/local/modules/fuse.ko #9 0xfe000c6678e0 in ?? () #10 0xfe000c6678e0 in ?? () #11 0x00020202 in ?? () #12 0xfe022ffebaa8 in ?? () #13 0xfe000c6678e0 in ?? () #14 0x01020c6678e0 in ?? () #15 0x in ?? () #16 0xfe022ffea3a8 in ?? () #17 0x8119cb80 in see_other_uids () #18 0xff8235870700 in ?? () #19 0x808d598b in malloc_type_zone_allocated (mtp=0xfe000c6678e0, size=18446741874894338272, zindx=32776) at /usr/src/sys/kern/kern_malloc.c:368 Previous frame inner to this frame (corrupt stack?) (kgdb) Any ideas? thx ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
pkg-devel problem with incremental update
Installed pkg-devel 1.1.0.b3 and get the following message about incremental update whenever update is called. sudo pkg update Updating repository catalogue pkg: incremental update is not possible as repo format is inappropriate, trying full upgrade packagesite repository catalogue is up-to-date, no need to fetch fresh copy What should I do to make incremental updates possible? -- Michael Gass mg...@csbsju.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
libchk issue
On my system (9.1-RELEASE-p3 on amd64), libchk reports: Unresolvable link(s) found in: /usr/local/lib/liblangtag-gobject.so.2 liblangtag.so.1 'pkg which' informs me that: /usr/local/lib/liblangtag-gobject.so.2 was not found in the database How can I fix the problem? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.1-RELEASE slow boot
On Tue, Jun 11, 2013 at 8:19 AM, Fernando Apesteguía fernando.apesteg...@gmail.com wrote: On Fri, Jun 7, 2013 at 11:04 PM, Polytropon free...@edvax.de wrote: On Fri, 7 Jun 2013 19:38:34 +0200, Fernando Apesteguía wrote: Since I updated to 9.1-RELEASE my boot process seems to stall for a while. Booting in verbose mode shows messages like these ones: Opening device da0 - 6 (repeated like 30 times or so) Opening device da1 - 6 (repeated like 30 times or so) Opening device da2 - 6 (repeated like 30 times or so) Opening device da3 - 6 (repeated like 30 times or so) Those devices correspond to my internal SD card reader that doesn't work on FreeBSD anyway. This seems some kind of probing right? I don't want to wait for those devices. What can I do to speed up booting? I didn't change my system settings either. Did anything related change in the kernel about probing these type of devices? For comparable reasons in the past, I added the following setting to my kernel configuration: options SCSI_DELAY=100 The default value is 5000. It's the delay in milliseconds for the SCSI probe. Hi, Sorry for my late response (sometimes real life comes first). SCSI_DELAY in the code didn't change between 9.1[1] and 9.0[2] neither did it in the configuration for the GENERIC kernels[3][4]. On both occasions (9.0 and 9.1) I used the GENERIC kernels and I didn't change this setting. I will give it a try as soon as I can, but it still seems a little strange to me that this process takes longer in 9.1 for no apparent reason Thanks. [1] http://fxr.watson.org/fxr/source/cam/scsi/scsi_all.c?v=FREEBSD91#L76 [2] http://fxr.watson.org/fxr/source/cam/scsi/scsi_all.c?v=FREEBSD90#L76 [3] http://svn.freebsd.org/base/releng/9.1/sys/amd64/conf/GENERIC [4] http://svn.freebsd.org/base/releng/9.0/sys/amd64/conf/GENERIC I recompiled the GENERIC kernel and changed SCSI_DELAY to 2000 instead the default 5000. Still no luck. It doesn't make any difference so I suppose something else changed. Any ideas? Thanks in advance. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
incomplete PLIST for devel/liblangtag [WAS Re: libchk issue]
On my system (9.1-RELEASE-p3 on amd64), libchk reports: Unresolvable link(s) found in: /usr/local/lib/liblangtag-gobject.so.2 liblangtag.so.1 'pkg which' informs me that: /usr/local/lib/liblangtag-gobject.so.2 was not found in the database How can I fix the problem? I confirm this, devel/liblangtag does not register gobj* files with pkgng. Neither 0.5 nor 0.4 port versions do this. I didn't go any earlier than that. The 0.5 version has CONFIGURE_ARGS= --disable-introspection but the older gobj* files are not removed prior to build/install. I think the port maintainer needs to look at this. Anton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.1-RELEASE slow boot
On Tue, Jun 11, 2013 at 4:43 PM, Fernando Apesteguía fernando.apesteg...@gmail.com wrote: I recompiled the GENERIC kernel and changed SCSI_DELAY to 2000 instead the default 5000. Still no luck. It doesn't make any difference so I suppose something else changed. Any ideas? Thanks in advance. Try setting hw.usb.no_boot_wait=1 -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
