Re: Q) KLDload error
On 17/11/2012 10:58 AM, ken wrote: I have the following error at booting with current kernel. Were there any changes? Any fixed? I need to run virtualbox. Nov 17 08:32:34 t3 kernel: FreeBSD 10.0-CURRENT #12 r243164M: Sat Nov 17 08:24:30 JST 2012 Nov 17 08:32:34 t3 kernel: k...@tyd3.sub.tydfam.jp:/usr/obj/usr/head/sys/TYD3 amd64 Nov 17 08:32:34 t3 kernel: link_elf_obj: symbol vm_page_lock_queues undefined Nov 17 08:32:34 t3 kernel: KLD file vboxdrv.ko - could not finalize loading You will need to rebuild and install the virtualbox-ose-kmod port. regards, Lucas -- I was going to include a witty saying, but I couldn't think of one. ___ 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: Q) KLDload error
On 17/11/2012 1:04 PM, ken wrote: Lucas Yes, I did and yet I have the following error with kldload vboxdrv. Is vm_page_lock_queues renamed? It is in ./work/VirtualBox-4.1.22/src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c # tail -f /var/log/messages :: : Nov 17 10:53:17 t3 pkg: virtualbox-ose-kmod-4.1.22 installed Nov 17 10:53:55 t3 kernel: link_elf_obj: symbol vm_page_lock_queues undefined Nov 17 10:53:55 t3 kernel: linker_load_file: Unsupported file type :: : ___ 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 Ahh, I see. After little more digging it would appear that alc@ removed vm_page_lock_queues in r242941, as he replaced them with multiple queues. Unfortunately this means VirtualBox will not be able to be run. I suggest submitting a PR. regards, Lucas -- I was going to include a witty saying, but I couldn't think of one. signature.asc Description: OpenPGP digital signature
Re: more panics from current (partII)
On Sun, 28 Sep 2003 08:27 pm, Tomi Vainio - Sun Finland wrote: After adding more disks to this system it dies continously. Last two traces look quite the same. Tomppa It could be a power supply on the way out. I had an old dual P-166 that rebooted misterously until I took out two CD-ROM drives I wanted for another machine. (replaced the power supply, and refitted the CDROMS, and every thing worked ok.) Lucas ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
