Re: Virtualbox on 8.2 64-bit (cont)
On 06/09/2011 15:49, Rob wrote: On 6/6/11 8:39 PM, Mario Lobo wrote: You need to rebuild your kernel with options COMPAT_FREEBSD32 # Compatible with i386 binaries included. I noticed that when I tried to build the ports, but I don't have anything in /usr/src and no information was given as to what packages/src I needed to install. I'd like to avoid diverging from the stock release kernel for upgrade simplicity. What exactly does that do? Will it introduce upgrade complexity (ie will I have to upgrade these libs before I upgrade the kernel or some such)? Needless to say, that option seems to be enabled in GENERIC: [starlight] ~ grep COMPAT_FREEBSD32 /usr/src/sys/amd64/conf/GENERIC options COMPAT_FREEBSD32# Compatible with i386 binaries Also I don't remember having to issue make build32 install32 or anything of that sort. You do need to have the FreeBSD source tree installed on your system, though. Did you try just fetching the source tree without building from it and then trying to build VirtualBox again? ~ Ondra ___ 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: Xorg Problems
On 08/19/2010 15:02, Warren Block wrote: Now I can't remember if it was AllowEmptyInput (no spaces) or Allow Empty Input but would think the former; am in Linux as I type this and didn't need that line in that xorg.conf . Don't need it in FreeBSD, either. In fact, using it in FreeBSD often causes hesitant input characters that only show up when you move the mouse. Or a draggy mouse. Or both. And all these years I've been using AllowEmptyInput with no problems whatsoever. Still good to know it may cause trouble. AllowEmptyInput will borrow your stuff and never return it. AllowEmptyInput will cause trouble and say it was your idea. AllowEmptyInput cheats at cards. On a second thought, it might explain a few things that have been going on in my life lately... ~ Ondra ___ 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: Xorg Problems
On 19-Aug-10 13:20, Rem Roberti wrote: I'm having trouble with xorg on a new 8.1 installation. I haven't installed a wm yet, but when I try to call up the generic x windows by typing startx they do indeed appear, but all three of the x windows are locked up. By that I mean that there is no mouse, and no possibility of entering data in the windows via the keyboard. Totally frozen. And you can't get out of x in the usual manner i.e. ctrl-alt-backspace. The only thing that works is ctrl-alt-del which, of course, reboots the computer. Any ideas are appreciated. New Xorg requires HAL and Dbus to recognize input devices by default. Do you have these enabled? Alternatively, you revert to the old, no-HAL method by adding Option AutoAddDevices False Option AllowEmptyInput False into your ServerFlags in xorg.conf. You might also want to add Option DontZap false into the same section as well to have Ctrl-Alt-Backspace working again. ~ Ondra ___ 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: VirtualBox: no network
Anselm Strauss wrote: I switched to NAT networking for now. It doesn't require any modules to load besides the vboxdrv.ko and runs stable so far. Only strange that ICMP is not working ... NAT networking doesn't work for me. Which Adapter Type are you using? And did you have to do any further configuration or did it jsut work out-of-the-box? ~ Ondra ___ 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: VirtualBox: no network
Ondrej Majerech wrote: Anselm Strauss wrote: I switched to NAT networking for now. It doesn't require any modules to load besides the vboxdrv.ko and runs stable so far. Only strange that ICMP is not working ... NAT networking doesn't work for me. Which Adapter Type are you using? And did you have to do any further configuration or did it jsut work out-of-the-box? ~ Ondra Ah, wait. The connection partly does work with the default settings. ICMP doesn't work for me either, so testing with ping gave me false negative. Also, DHCP-configured DNS resolver doesn't work for me -- I had to type in a DNS server IP address manually. That way, Firefox running on Ubuntu inside VBox can finally load pages. ~ Ondra ___ 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
Eclipse causes segmentation fault in Java
Hey, I have a fresh FBSD 8-Stable/AMD64 installation and I want to run Eclipse. This is what I get: [starlight] ~ eclipse realpath: : No such file or directory # # An unexpected error has been detected by Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x000825d6d985, pid=11170, tid=0xa0ae40 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.6.0_03-p4-root_13_may_2010_21_53-b00 mixed mode) # Problematic frame: # C [libglib-2.0.so.0+0x18985] g_base64_encode_step+0xe5 # # An error report file with more information is saved as hs_err_pid11170.log # # Please submit bug reports to freebsd-j...@freebsd.org # Mentioned file is attached. I'm using jdk16 from ports. I have also tried with diablo-jdk from ports with exactly the same result. java -version realpath: : No such file or directory java version 1.6.0_03-p4 Java(TM) SE Runtime Environment (build 1.6.0_03-p4-root_13_may_2010_21_53-b00) Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_03-p4-root_13_may_2010_21_53-b00, mixed mode) After Eclipse crashes like this, my system becomes unusably slow: in top I can see the java process using 43 GB of memory (the SIZE column) and being in STOP state. Java is then slowly consuming my physical memory until I reboot. It is apparantely trying to dump a core: ls -lh ~/java.core -rw--- 1 oxyd oxyd43G May 13 21:15 /usr/home/oxyd/java.core I need to say this is the largest coredump I've ever seen. Doing sysctl kern.coredump=0 and retrying Eclipse produces the same error but doesn't hang my machine. I'm also unsure about the realpath: : No such file or directory message that appears in the output, but I don't know what it means and Google doesn't help much. I'll be happy to hear any suggestions. ~ Ondra # # An unexpected error has been detected by Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x000825d6d985, pid=11170, tid=0xa0ae40 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.6.0_03-p4-root_13_may_2010_21_53-b00 mixed mode) # Problematic frame: # C [libglib-2.0.so.0+0x18985] g_base64_encode_step+0xe5 # # Please submit bug reports to freebsd-j...@freebsd.org # --- T H R E A D --- Current thread (0x000800a8e000): JavaThread main [_thread_in_native, id=10530368] siginfo:si_signo=11, si_errno=0, si_code=2, si_addr=0x000825a0d000 Registers: RAX=0x, RBX=0x7fbec69c, RCX=0x000825dd1740, RDX=0x RSP=0x7fbec660, RBP=0x00082a00, RSI=0x0007, RDI=0x000825a0d000 R8 =0x00082a70f6a8, R9 =0x7fbec698, R10=0x, R11=0x000825a0cffe R12=0x0010254c2346, R13=0x, R14=0x, R15=0x0008257f1b50 RIP=0x000825d6d985, EFL=0x0001, ERR=0x0004 TRAPNO=0x000c Top of Stack: (sp=0x7fbec660) 0x7fbec660: 7fbec698 00080c48 0x7fbec670: 7fbec69c 00082a00 0x7fbec680: 0008254c1700 000825d6ded3 0x7fbec690: 7fbec774 0x7fbec6a0: 0008009a8c20 00082567d600 0x7fbec6b0: 7fbfd910 0x7fbec6c0: 0008257f1ba0 000829ebca35 0x7fbec6d0: 000829ebb190 000829662280 0x7fbec6e0: 000829662289 0010 0x7fbec6f0: 0x7fbec700: 0x7fbec710: 0008009a8c20 0008007ee3f9 0x7fbec720: 00080c48 0008254c1700 0x7fbec730: 000829662220 0008257b22c0 0x7fbec740: 0008257f7fb0 0008256a1b00 0x7fbec750: 000800a36800 000800ab1880 0x7fbec760: 000800a9b800 000829646ed0 0x7fbec770: ffbfd910 0020 0x7fbec780: 00060020 0008009a8c20 0x7fbec790: 00082567d600 0x7fbec7a0: 7fbfd910 000828306150 0x7fbec7b0: 0x7fbec7c0: 0x7fbec7d0: 0x7fbec7e0: 0x7fbec7f0: 0x7fbec800: 0x7fbec810: 0x7fbec820: 0x7fbec830: 0x7fbec840: 0x7fbec850: Instructions: (pc=0x000825d6d985) 0x000825d6d975: b6 17 48 83 c7 01 44 89 d0 48 8d 0d bb 3d 06 00 0x000825d6d985: 0f b6 37 c1 f8 02 41 83 e2 03 4c 8d 5f 01 48 98 Stack: [0x7faff000,0x7fbff000), sp=0x7fbec660, free space=949k Native frames: (J=compiled Java code,
Re: Eclipse causes segmentation fault in Java
Jonathan Chen wrote: On Thu, May 13, 2010 at 11:10:42PM +0200, Ondrej Majerech wrote: At a guess, you recently upgraded to GNOME 2.30; and since it's been crashing. I just started seeing this myself since I updated yesterday. Cheers. This is a fresh install, so I didn't yet have the chance to upgrade anything -- everything is a fresh, first-time install. But yeah, it appears to be the case. Eclipse pulled libgnome-2.30.0 as a dependency (among others). Perhaps rebuilding Eclipse with WITHOUT_GNOMEVFS=yes is worth a try. I'm not a Gnome user anyway. ~ Ondra ___ 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
