Gustau Pérez wrote: > Martin Wilke wrote: >> On Tue, May 19, 2009 at 03:28:02PM -0400, Michael Butler wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> Martin Wilke wrote: >>>> http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz >>> With the latest tarball, I still don't see my DVD in the drop-down list >>> even though I have tweaked the devd.conf file such that .. >>> imb_at_toshi:/home/imb> ll /dev/*cd* >>> crw-rw-rw- 1 root operator 0, 97 May 19 10:55 /dev/acd0 >>> crw-rw-rw- 1 root operator 0, 104 May 19 10:55 /dev/cd0 >>> lrwxr-xr-x 1 root wheel 3 May 19 10:55 /dev/cdrom -> cd0 >>> This is on a Toshiba Satellite with today's -current .. >>> imb_at_toshi:/home/imb> uname -a >>> FreeBSD toshi.auburn.protected-networks.net 8.0-CURRENT FreeBSD >>> 8.0-CURRENT #89: Tue May 19 07:29:32 EDT 2009 >>> root_at_toshi.auburn.protected-networks.net:/usr/obj/usr/src/sys/TOSHI >> i386 >> >> at the moment a now issus we will take a look later. >> >> All in one seems that by most peoples now vbox works \o/ >> > > Hi, > > as I reported this morning, for me is not working. My system is a > DELL D630 laptop with 3Gb of RAM. i386/CURRENT update today : > > FreeBSD gusiport 8.0-CURRENT FreeBSD 8.0-CURRENT #41: Tue May 19 > 14:24:05 CEST 2009 > gus_at_gusiport:/usr/obj/usr/src/sys/CUSTOM i386 > > Last version fixed the problem with the kernel module not being > detected the second time vbox is run, but I still have vbox booting the > virtual machine in wit a gray screen. I've observed the machine is > supposed to be running, but making top shows no activity. Also tried > VBoxSDL -startvm win (win is the id given to the vmachine, yes I know, > it took me little time to give it a name :) ) and the virtual machine > shows a black screen. No CPU activity at all. Tried disabling VT-x/AMD-v > extensions (the laptop supports VT-x) still no go. Same problem here FreeBSD chamonix.restart.bel 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon May 18 16:47:40 CEST 2009 root_at_chamonix.restart.bel:/usr/obj/usr/src/sys/CHAMONIX i386 I am using nvidia-driver-180.44 (II) LoadModule: "nvidia" (II) Loading /usr/local/lib/xorg/modules/drivers//nvidia_drv.so (II) Module nvidia: vendor="NVIDIA Corporation" compiled for 4.0.2, module version = 1.0.0 Module class: X.Org Video Driver (II) NVIDIA dlloader X Driver 180.44 Mon Mar 23 05:42:54 PST 2009 (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs <clip> (II) NVIDIA(0): NVIDIA GPU Quadro NVS 285 (NV44GL) at PCI:3:0:0 (GPU-0) (--) NVIDIA(0): Memory: 131072 kBytes (--) NVIDIA(0): VideoBIOS: 05.44.02.64.03 (II) NVIDIA(0): Detected PCI Express Link width: 1X (--) NVIDIA(0): Interlaced video modes are supported on this GPU (--) NVIDIA(0): Connected display device(s) on Quadro NVS 285 at PCI:3:0:0: (--) NVIDIA(0): FUS P22W-5 ECO (CRT-0) (--) NVIDIA(0): FUS P22W-5 ECO (CRT-0): 400.0 MHz maximum pixel clock (II) NVIDIA(0): Assigned Display Device: CRT-0 (II) NVIDIA(0): Validated modes: (II) NVIDIA(0): "1680x1050" (II) NVIDIA(0): Virtual screen size determined to be 1680 x 1050 (--) NVIDIA(0): DPI set to (90, 88); computed from "UseEdidDpi" X config (--) NVIDIA(0): option (==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals. Henri > > Anything I can try ? > > Thanks, > > GusReceived on Wed May 20 2009 - 10:29:44 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:48 UTC