Re: Install 10.0-RC3 on MacBookPro Late 2013
On 01/11/14 05:14, Huang Wen Hui wrote: Hi, I got one problem when I unplug/plug Buffalo WLI-UC-GNM, it is USB WLAN. All USB devices become to disconnected after unplug and plug: Try this: http://svnweb.freebsd.org/changeset/base/260535 --HPS ___ 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
CURRENT: build world failure: /usr/src/usr.sbin/bhyvectl/bhyvectl.c:1466:8: error: use of undeclared identifier 'VMCS_EXIT_INTERRUPTION_ERROR' VMCS_EXIT_INTERRUPTION_ERROR, u64);
Recent sources (revision 260540) fail to build: cc -O2 -pipe -O3 -march=native -I/usr/src/usr.sbin/bhyvectl/../../sys/amd64/vmm -pipe -O3 -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -c /usr/src/usr.sbin/bhyvectl/bhyvectl.c /usr/src/usr.sbin/bhyvectl/bhyvectl.c:1457:8: error: use of undeclared identifier 'VMCS_EXIT_INTERRUPTION_INFO'; did you mean 'SET_VMCS_ENTRY_INTERRUPTION_INFO'? VMCS_EXIT_INTERRUPTION_INFO, u64); ^~~ SET_VMCS_ENTRY_INTERRUPTION_INFO /usr/src/usr.sbin/bhyvectl/bhyvectl.c:382:2: note: 'SET_VMCS_ENTRY_INTERRUPTION_INFO' declared here SET_VMCS_ENTRY_INTERRUPTION_INFO, ^ /usr/src/usr.sbin/bhyvectl/bhyvectl.c:1466:8: error: use of undeclared identifier 'VMCS_EXIT_INTERRUPTION_ERROR' VMCS_EXIT_INTERRUPTION_ERROR, u64); signature.asc Description: PGP signature
Re: CURRENT: build world failure: /usr/src/usr.sbin/bhyvectl/bhyvectl.c:1466:8: error: use of undeclared identifier 'VMCS_EXIT_INTERRUPTION_ERROR' VMCS_EXIT_INTERRUPTION_ERROR, u64);
On Sat, Jan 11, 2014 at 11:32:06AM +0100, O. Hartmann wrote: Recent sources (revision 260540) fail to build: cc -O2 -pipe -O3 -march=native -I/usr/src/usr.sbin/bhyvectl/../../sys/amd64/vmm -pipe -O3 -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -c /usr/src/usr.sbin/bhyvectl/bhyvectl.c /usr/src/usr.sbin/bhyvectl/bhyvectl.c:1457:8: error: use of undeclared identifier 'VMCS_EXIT_INTERRUPTION_INFO'; did you mean 'SET_VMCS_ENTRY_INTERRUPTION_INFO'? VMCS_EXIT_INTERRUPTION_INFO, u64); ^~~ SET_VMCS_ENTRY_INTERRUPTION_INFO /usr/src/usr.sbin/bhyvectl/bhyvectl.c:382:2: note: 'SET_VMCS_ENTRY_INTERRUPTION_INFO' declared here SET_VMCS_ENTRY_INTERRUPTION_INFO, ^ /usr/src/usr.sbin/bhyvectl/bhyvectl.c:1466:8: error: use of undeclared identifier 'VMCS_EXIT_INTERRUPTION_ERROR' VMCS_EXIT_INTERRUPTION_ERROR, u64); I see the same thing. It appears that the definition of VMCS_EXIT_INTERRUPTION_INFO and VMCS_EXIT_INTERRUPTION_ERROR changed in r260531 to VMC_EXIT_INT_INFO and VMCS_EXIT_INTR_ERRCODE respectively. pgpnQS6vMCZ_8.pgp Description: PGP signature
Re: Install 10.0-RC3 on MacBookPro Late 2013
I try many times plug/unplug, this patch basically works, but I still got the previous problem one time. Cheers, Huang Wen Hui 2014/1/11 Hans Petter Selasky h...@bitfrost.no On 01/11/14 05:14, Huang Wen Hui wrote: Hi, I got one problem when I unplug/plug Buffalo WLI-UC-GNM, it is USB WLAN. All USB devices become to disconnected after unplug and plug: Try this: http://svnweb.freebsd.org/changeset/base/260535 --HPS ___ 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: CURRENT: build world failure: /usr/src/usr.sbin/bhyvectl/bhyvectl.c:1466:8: error: use of undeclared identifier 'VMCS_EXIT_INTERRUPTION_ERROR' VMCS_EXIT_INTERRUPTION_ERROR, u64);
On Sat, Jan 11, 2014 at 12:34:44PM +0100, Marcus Karlsson wrote:
On Sat, Jan 11, 2014 at 11:32:06AM +0100, O. Hartmann wrote:
Recent sources (revision 260540) fail to build:
cc -O2 -pipe -O3 -march=native
-I/usr/src/usr.sbin/bhyvectl/../../sys/amd64/vmm -pipe -O3 -std=gnu99
-Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall
-Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Wno-uninitialized
-Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int
-Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality
-Wno-unused-function -Wno-enum-conversion
-c /usr/src/usr.sbin/bhyvectl/bhyvectl.c
/usr/src/usr.sbin/bhyvectl/bhyvectl.c:1457:8:
error: use of undeclared identifier 'VMCS_EXIT_INTERRUPTION_INFO'; did
you mean 'SET_VMCS_ENTRY_INTERRUPTION_INFO'?
VMCS_EXIT_INTERRUPTION_INFO, u64); ^~~
SET_VMCS_ENTRY_INTERRUPTION_INFO
/usr/src/usr.sbin/bhyvectl/bhyvectl.c:382:2:
note: 'SET_VMCS_ENTRY_INTERRUPTION_INFO' declared here
SET_VMCS_ENTRY_INTERRUPTION_INFO,
^ /usr/src/usr.sbin/bhyvectl/bhyvectl.c:1466:8: error: use of
undeclared identifier 'VMCS_EXIT_INTERRUPTION_ERROR'
VMCS_EXIT_INTERRUPTION_ERROR, u64);
I see the same thing. It appears that the definition of
VMCS_EXIT_INTERRUPTION_INFO and VMCS_EXIT_INTERRUPTION_ERROR changed in
r260531 to VMC_EXIT_INT_INFO and VMCS_EXIT_INTR_ERRCODE respectively.
This patch was enough for the build to complete successfully in case
anyone else wants it. The old macros are not used anywhere else in the
source tree apart from bhyvectl.
Index: usr.sbin/bhyvectl/bhyvectl.c
===
--- usr.sbin/bhyvectl/bhyvectl.c(revision 260540)
+++ usr.sbin/bhyvectl/bhyvectl.c(working copy)
@@ -1454,7 +1454,7 @@
if (!error (get_vmcs_exit_interruption_info || get_all)) {
error = vm_get_vmcs_field(ctx, vcpu,
- VMCS_EXIT_INTERRUPTION_INFO, u64);
+ VMCS_EXIT_INTR_INFO, u64);
if (error == 0) {
printf(vmcs_exit_interruption_info[%d]\t0x%08lx\n,
vcpu, u64);
@@ -1463,7 +1463,7 @@
if (!error (get_vmcs_exit_interruption_error || get_all)) {
error = vm_get_vmcs_field(ctx, vcpu,
- VMCS_EXIT_INTERRUPTION_ERROR, u64);
+ VMCS_EXIT_INTR_ERRCODE, u64);
if (error == 0) {
printf(vmcs_exit_interruption_error[%d]\t0x%08lx\n,
vcpu, u64);
___
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
[head tinderbox] failure on amd64/amd64
TB --- 2014-01-11 13:00:17 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2014-01-11 13:00:17 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014-01-11 13:00:17 - starting HEAD tinderbox run for amd64/amd64 TB --- 2014-01-11 13:00:17 - cleaning the object tree TB --- 2014-01-11 13:00:17 - /usr/local/bin/svn stat /src TB --- 2014-01-11 13:00:22 - At svn revision 260540 TB --- 2014-01-11 13:00:23 - building world TB --- 2014-01-11 13:00:23 - CROSS_BUILD_TESTING=YES TB --- 2014-01-11 13:00:23 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-11 13:00:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-11 13:00:23 - SRCCONF=/dev/null TB --- 2014-01-11 13:00:23 - TARGET=amd64 TB --- 2014-01-11 13:00:23 - TARGET_ARCH=amd64 TB --- 2014-01-11 13:00:23 - TZ=UTC TB --- 2014-01-11 13:00:23 - __MAKE_CONF=/dev/null TB --- 2014-01-11 13:00:23 - cd /src TB --- 2014-01-11 13:00:23 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sat Jan 11 13:00:29 UTC 2014 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] SET_VMCS_ENTRY_INTERRUPTION_INFO /src/usr.sbin/bhyvectl/bhyvectl.c:382:2: note: 'SET_VMCS_ENTRY_INTERRUPTION_INFO' declared here SET_VMCS_ENTRY_INTERRUPTION_INFO, ^ /src/usr.sbin/bhyvectl/bhyvectl.c:1466:8: error: use of undeclared identifier 'VMCS_EXIT_INTERRUPTION_ERROR' VMCS_EXIT_INTERRUPTION_ERROR, u64); ^ 2 errors generated. *** Error code 1 Stop. bmake[3]: stopped in /src/usr.sbin/bhyvectl *** Error code 1 Stop. bmake[2]: stopped in /src/usr.sbin *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2014-01-11 16:06:09 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-01-11 16:06:09 - ERROR: failed to build world TB --- 2014-01-11 16:06:09 - 9129.05 user 1558.62 system 11151.55 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-amd64-amd64.full ___ 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: [head tinderbox] failure on amd64/amd64
Sorry, my bad. Fixed in r260550. best Neel On Sat, Jan 11, 2014 at 8:06 AM, FreeBSD Tinderbox tinder...@freebsd.org wrote: TB --- 2014-01-11 13:00:17 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2014-01-11 13:00:17 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014-01-11 13:00:17 - starting HEAD tinderbox run for amd64/amd64 TB --- 2014-01-11 13:00:17 - cleaning the object tree TB --- 2014-01-11 13:00:17 - /usr/local/bin/svn stat /src TB --- 2014-01-11 13:00:22 - At svn revision 260540 TB --- 2014-01-11 13:00:23 - building world TB --- 2014-01-11 13:00:23 - CROSS_BUILD_TESTING=YES TB --- 2014-01-11 13:00:23 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-11 13:00:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-11 13:00:23 - SRCCONF=/dev/null TB --- 2014-01-11 13:00:23 - TARGET=amd64 TB --- 2014-01-11 13:00:23 - TARGET_ARCH=amd64 TB --- 2014-01-11 13:00:23 - TZ=UTC TB --- 2014-01-11 13:00:23 - __MAKE_CONF=/dev/null TB --- 2014-01-11 13:00:23 - cd /src TB --- 2014-01-11 13:00:23 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sat Jan 11 13:00:29 UTC 2014 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] SET_VMCS_ENTRY_INTERRUPTION_INFO /src/usr.sbin/bhyvectl/bhyvectl.c:382:2: note: 'SET_VMCS_ENTRY_INTERRUPTION_INFO' declared here SET_VMCS_ENTRY_INTERRUPTION_INFO, ^ /src/usr.sbin/bhyvectl/bhyvectl.c:1466:8: error: use of undeclared identifier 'VMCS_EXIT_INTERRUPTION_ERROR' VMCS_EXIT_INTERRUPTION_ERROR, u64); ^ 2 errors generated. *** Error code 1 Stop. bmake[3]: stopped in /src/usr.sbin/bhyvectl *** Error code 1 Stop. bmake[2]: stopped in /src/usr.sbin *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2014-01-11 16:06:09 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-01-11 16:06:09 - ERROR: failed to build world TB --- 2014-01-11 16:06:09 - 9129.05 user 1558.62 system 11151.55 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-amd64-amd64.full ___ 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 ___ 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: CURRENT: build world failure: /usr/src/usr.sbin/bhyvectl/bhyvectl.c:1466:8: error: use of undeclared identifier 'VMCS_EXIT_INTERRUPTION_ERROR' VMCS_EXIT_INTERRUPTION_ERROR, u64);
Hi Marcus, On Sat, Jan 11, 2014 at 4:52 AM, Marcus Karlsson m...@acc.umu.se wrote: On Sat, Jan 11, 2014 at 12:34:44PM +0100, Marcus Karlsson wrote: On Sat, Jan 11, 2014 at 11:32:06AM +0100, O. Hartmann wrote: Recent sources (revision 260540) fail to build: cc -O2 -pipe -O3 -march=native -I/usr/src/usr.sbin/bhyvectl/../../sys/amd64/vmm -pipe -O3 -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -c /usr/src/usr.sbin/bhyvectl/bhyvectl.c /usr/src/usr.sbin/bhyvectl/bhyvectl.c:1457:8: error: use of undeclared identifier 'VMCS_EXIT_INTERRUPTION_INFO'; did you mean 'SET_VMCS_ENTRY_INTERRUPTION_INFO'? VMCS_EXIT_INTERRUPTION_INFO, u64); ^~~ SET_VMCS_ENTRY_INTERRUPTION_INFO /usr/src/usr.sbin/bhyvectl/bhyvectl.c:382:2: note: 'SET_VMCS_ENTRY_INTERRUPTION_INFO' declared here SET_VMCS_ENTRY_INTERRUPTION_INFO, ^ /usr/src/usr.sbin/bhyvectl/bhyvectl.c:1466:8: error: use of undeclared identifier 'VMCS_EXIT_INTERRUPTION_ERROR' VMCS_EXIT_INTERRUPTION_ERROR, u64); I see the same thing. It appears that the definition of VMCS_EXIT_INTERRUPTION_INFO and VMCS_EXIT_INTERRUPTION_ERROR changed in r260531 to VMC_EXIT_INT_INFO and VMCS_EXIT_INTR_ERRCODE respectively. This patch was enough for the build to complete successfully in case anyone else wants it. The old macros are not used anywhere else in the source tree apart from bhyvectl. Sorry about the breakage and thanks for the patch. Submitted as r260550. best Neel ___ 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 ___ 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: Move 3G modem from u3g to uhso?
On 10 Jan 2014, at 02:54, Lundberg, Johannes johan...@brilliantservice.co.jp wrote: Ah I see. Of course usb.conf is generated automatically :) I guess it is generated at make buildkernel and the new one can be found in obj folder? It's generated using src/tools/tools/bus_autoconf. -- Rui Paulo ___ 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: FreeBSD 10.0-RC5 Now Available
On Thu, Jan 9, 2014, at 21:41, Erich Dollansky wrote: Hi, I upgraded this morning to FreeBSD X220.alogt.com 10.0-PRERELEASE FreeBSD 10.0-PRERELEASE #7 r260489: Fri Jan 10 08:25:55 WITA 2014 er...@x220.alogt.com:/usr/obj/usr/src/sys/X220 amd64 just to find out that the mouse is not working under X anymore. The ports are from revision 336079. I have an X220. Neither the internal stick nor the external USB connected Logitech Trackman work. Both work outside X. X logs these mouse related messages: [ 315.926] (==) intel(0): Silken mouse enabled [ 316.960] (II) config/hal: Adding input device Trackball [ 316.960] (II) LoadModule: mouse [ 316.961] (II) Loading /usr/local/lib/xorg/modules/input/mouse_drv.so [ 316.977] (II) Module mouse: vendor=X.Org Foundation [ 316.977]compiled for 1.12.4, module version = 1.9.0 [ 316.977]Module class: X.Org XInput Driver [ 316.977]ABI class: X.Org XInput driver, version 16.0 [ 316.977] (II) Using input driver 'mouse' for 'Trackball' [ 316.977] (**) Trackball: always reports core events [ 316.977] (**) Option Device /dev/ums0 [ 316.977] (==) Trackball: Protocol: Auto [ 316.977] (**) Trackball: always reports core events [ 316.977] (EE) xf86OpenSerial: Cannot open device /dev/ums0 Device busy. [ 316.977] (EE) Trackball: cannot open input device [ 316.977] (EE) PreInit returned 2 for Trackball [ 316.977] (II) UnloadModule: mouse [ 316.991] (II) config/hal: Adding input device PS/2 Mouse [ 316.991] (II) Using input driver 'mouse' for 'PS/2 Mouse' [ 316.991] (**) PS/2 Mouse: always reports core events [ 316.991] (**) Option Device /dev/psm0 [ 316.991] (==) PS/2 Mouse: Protocol: Auto [ 316.991] (**) PS/2 Mouse: always reports core events [ 316.991] (EE) xf86OpenSerial: Cannot open device /dev/psm0 Device busy. [ 316.991] (EE) PS/2 Mouse: cannot open input device [ 316.991] (EE) PreInit returned 2 for PS/2 Mouse [ 316.991] (II) UnloadModule: mouse This are the X message I get when running X on an older release candidate: [ 111.171] (II) config/hal: Adding input device PS/2 Mouse [ 111.171] (II) LoadModule: mouse [ 111.171] (II) Loading /usr/local/lib/xorg/modules/input/mouse_drv.so [ 111.181] (II) Module mouse: vendor=X.Org Foundation [ 111.181]compiled for 1.12.4, module version = 1.9.0 [ 111.181]Module class: X.Org XInput Driver [ 111.181]ABI class: X.Org XInput driver, version 16.0 [ 111.181] (II) Using input driver 'mouse' for 'PS/2 Mouse' [ 111.181] (**) PS/2 Mouse: always reports core events [ 111.181] (**) Option Device /dev/sysmouse [ 111.181] (==) PS/2 Mouse: Protocol: Auto [ 111.181] (**) PS/2 Mouse: always reports core events [ 111.181] (==) PS/2 Mouse: Emulate3Buttons, Emulate3Timeout: 50 [ 111.181] (**) PS/2 Mouse: ZAxisMapping: buttons 4 and 5 [ 111.181] (**) PS/2 Mouse: Buttons: 5 [ 111.181] (**) Option config_info hal:/org/freedesktop/Hal/devices/psm_0 [ 111.181] (II) XINPUT: Adding extended input device PS/2 Mouse (type: MOUSE, id 7) [ 111.181] (**) PS/2 Mouse: (accel) keeping acceleration scheme 1 [ 111.181] (**) PS/2 Mouse: (accel) acceleration profile 0 [ 111.181] (**) PS/2 Mouse: (accel) acceleration factor: 2.000 [ 111.181] (**) PS/2 Mouse: (accel) acceleration threshold: 4 [ 111.181] (II) PS/2 Mouse: SetupAuto: hw.iftype is 4, hw.model is 0 [ 111.182] (II) PS/2 Mouse: SetupAuto: protocol is SysMouse The same X worked perfectly with any FreeBSD 10 since BETA1. When I change xorg.conf and disable moused, I am able to get the internal mouse (stick) working but not the external one. The external mouse is recognised by the system when disconnected and reconnected but not by X. It also works outside X. I will update the ports tree tonight or tomorrow morning to see what will happen then. Erich On Thu, 9 Jan 2014 11:18:18 -0500 Glen Barber g...@freebsd.org wrote: Changes between -RC4 and -RC5 include: o Fix an IPv4 multicast regression. o Fixes OpenSSL for CVE-2013-4353, CVE-2013-6449, CVE-2013-6450. o Revert a change to the kinfo_file structure to preserve ABI. o Fix a race condition which could prevent the file descriptor table from being properly updated. Rebuild X with the DEVD option instead of HAL. FreeBSD is the only Xorg consumer that did not write their own input device hot plugging ___ 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: Move 3G modem from u3g to uhso?
Thanks a lot you both. On Sunday, January 12, 2014, Rui Paulo wrote: On 10 Jan 2014, at 02:54, Lundberg, Johannes johan...@brilliantservice.co.jp javascript:; wrote: Ah I see. Of course usb.conf is generated automatically :) I guess it is generated at make buildkernel and the new one can be found in obj folder? It's generated using src/tools/tools/bus_autoconf. -- Rui Paulo -- -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。 もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、 複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. ___ 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
PKGNG: virtualbox-ose wants lang/gcc AND pdftk wants lang/gcc46
Where is the logic?I can not install lang/gcc and lang/gcc46 both at the same time.Any hints? How to use BOTH virtualbox and pdftk using PKGNG?Regards,vermaden# pkg install virtualbox-oseUpdating repository catalogueThe following 50 packages will be installed:nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling mkfontdir-1.0.7 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Upgrading freetype2: 2.5.0.1 -gt; 2.5.2nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Upgrading font-util: 1.3.0 -gt; 1.3.0_1nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Upgrading libffi: 3.0.13 -gt; 3.0.13_1nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling libdrm-2.4.17_1 (direct dependency changed)--gt; nbsp; Installing gcc: 4.6.4nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling curl-7.33.0_2 (options changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Upgrading py27-setuptools: 1.1.7_1 -gt; 2.0.1nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Upgrading fontconfig: 2.10.95,1 -gt; 2.11.0_1,1nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Upgrading font-misc-ethiopic: 1.0.3 -gt; 1.0.3_1nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Upgrading font-bh-ttf: 1.0.3 -gt; 1.0.3_1nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Upgrading encodings: 1.0.4,1 -gt; 1.0.4_1,1nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling dejavu-2.34 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling glib-2.36.3_1 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling libGL-7.6.1_4 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling libXft-2.3.1 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling cairo-1.10.2_7,2 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling shared-mime-info-1.1 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling libGLU-9.0.0 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;n bsp; Reinstalling freeglut-2.8.1 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling atk-2.8.0 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling sdl-1.2.15_2,2 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling gobject-introspection-1.36.0_2 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling libIDL-0.8.14_1 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Upgrading font-misc-meltho: 1.0.3 -gt; 1.0.3_1nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling qt4-corelib-4.8.5 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Upgrading harfbuzz: 0.9.19 -gt; 0.9.25nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling qt4-network-4.8.5 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling tiff-4.0.3 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling qt4-xml-4 .8.5 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling gstreamer-0.10.36 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling qt4-xmlpatterns-4.8.5 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling qt4-script-4.8.5 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling qt4-sql-4.8.5 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling qt4-clucene-4.8.5 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling qt4-sqlite-plugin-4.8.5 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling xorg-fonts-truetype-7.7_1 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling pango-1.34.1_1 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling gdk-pixbuf2-2.28.2 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Re installing gstreamer-plugins-0.10.36_3,3 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling qt4-gui-4.8.5 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling gtk-update-icon-cache-2.24.22 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling qt4-svg-4.8.5 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling qt4-help-4.8.5 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling qt4-opengl-4.8.5 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling qt4-declarative-4.8.5 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling qt4-webkit-4.8.5 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling qt4-assistant-4.8.5 (direct dependency changed)nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Reinstalling qt4-linguist-4.8.5 (direct dependency changed)nbsp;nbsp;n bsp;nbsp;nbsp;nbsp;nbsp; Installing virtualbox-ose: 4.2.20_2The installation will require 745 MB more space0 B to be downloadedProceed with installing packages [y/N]: ^C# pkg install pdftknbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; nbsp;Updating repository catalogueThe following 2
Re: FreeBSD 10.0-RC5 Now Available
On Thu, Jan 9, 2014 at 9:26 PM, john hood cg...@glup.org wrote: On 1/9/14 10:52 PM, Allan Jude wrote: Another user had this problem this morning, try reinstalling or recompiling hald I had this too today. There's an easier, lamer workaround: Put moused_nondefault_enable=NO in your /etc/rc.conf, and unplug/plug your USB mouse (or kill moused), and restart your X server or login manager. This costs you 1 mouse pointer in text mode. I had the same issue when I tried to install FreeBSD 10.0-RC5 on a desktop system with a USB mouse. I installed all the packages via the 'pkg' command. Your workaround worked for me. This seems to be a known issue because it has been mentioned elsewhere: http://lists.freebsd.org/pipermail/freebsd-current/2013-September/044594.html Is this workaround necessary in the future, or is there a newer precompiled hald package which solves this so that you dont need to set moused_nondefault_enable in /etc/rc.conf? -- Craig ___ 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
newcons + splash image
Hi Does newcons yet support splash images the same way syscons do? What is the current plan around this? Will there be any way to easily display image / animation during boot or is one expected to write a separate program for showing alternate boot or splash image? Best regards -- Johannes Lundberg -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。 もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、 複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. ___ 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
