Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Martin Wilke 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, May 14, 2009 at 11:06:24PM +0200, Gustau Pérez wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Martin Wilke wrote:
> >
> > Howdy Guys,
> >
> > After the announcement from Alexander Eichner about Virtualbox on
> > FreeBSD, we started the work on a port for FreeBSD. Now we think
> > that we solved the most problems and are ready for the first Call
> > for Testing.
> >
> > Some notes before you can test the port: Make sure you are using
> > RELENG_7 or higher. You have to use a fresh portstree with uptodate
> > ports!! Please read carefully the pkg-messages.
> >
> > Some known issues / Troubleshooting: Sometimes the kernel on HEAD
> > coredumps when loading or unloading the kernel module. A small
> > workaround to prevent the crash is to not start X, mount proc, then
> > load the kernel module and start X from the console. That helped me
> > and some testers, maybe you too. :P AMD64 should be work in
> > general, it builds and start. But not right tested at the moment.
> > We want here also some feedback.
> >
> > Some Thanks: First of all we'd like to say many thanks to _ALL_
> > vbox developers. Next people are Bernhard Froehlich (aka decke),
> > Beat Gaetzi (beat@), Dennis Herrmann (dhn@), Pietro Cerutti
> > (gahr@), myself (*gg*), and _ALL_ who helped and provided feedback.
> >
> >
> > Happy Testing :-)
> >
> > Download:
> >
> > http://people.freebsd.org/~miwi/vbox/vboxport.tgz
> >
> > Wiki Page: http://wiki.freebsd.org/VirtualBox
> 
> 
>I'm testing with i386/HEAD. I have two issues :
> 
>1.- The first time I start a machine. The window stays gray. If
> I pause and resume the window turns to
> black. Virtualbox says it is running, but it is not.
> 
>2.- The second and subsequent times I start a virtual machine,
> virtualbox says that there isn't the kernel driver. The
> error is :
> 
> Result Code: NS_ERROR_FAILURE (0x80004005)
> Component: Machine
> Interface: IMachine {4d1df26d-d9c1-4c7e-b689-15e85ecf8ffc}
> 
>   And :
> 
> Kernel driver not installed (rc=-1908)
> 
> Make sure the kernel module has been loaded successfully.
> 
>   What can be done ?
> 
>Regards,
> 
>   Gustau

Unfortunately, I saw this problem today also, I'll set this to our todo.

Thanks

> 
> >
> > - Martin
> >
> ___
> freebsd-curr...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 
> - --
> PGP KEY : http://www-entel.upc.edu/gus/gus.asc
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.11 (FreeBSD)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iEYEARECAAYFAkoMh9AACgkQAvcpDulVChDtMACdGK3ggUplPWifN4ozP2Ac5fOa
> pjQAn2ErwBcuTAfn/coIaY12J4lGQrUX
> =5myk
> -END PGP SIGNATURE-
> 

- -- 

+---+---+
|  PGP: 0xB1E6FCE9  |  Jabber : miwi(at)BSDCrew.de  |
|  ICQ: 169139903   |  Mail   : miwi(at)FreeBSD.org |
+---+---+
|   Mess with the Best, Die like the Rest!  |
+---+---+
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11 (FreeBSD)

iEYEARECAAYFAkoNHE0ACgkQdLJIhLHm/OnQTACfTk4ohhMGHtxgMjjHuDVRwAmm
Zc0An0cPJxRsElv+cfpO8hjNFF4N7J5W
=iP3/
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Bernhard Fröhlich 
On Thu, May 14, 2009 11:51 pm, Artem Belevich wrote:
> Few more notes from -CURRENT/amd64
>
> [snip]
>
> * Attempt to boot new VM (64-bit FreeBSD) from -current snapshot DVD
> ISO results in an error:
>
> Failed to start the virtual machine FreeBSD.
> Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG).
> Unknown error creating VM (VERR_SYMBOL_VALUE_TOO_BIG).
>
> Result Code: NS_ERROR_FAILURE (0x80004005)
> Component: Console
> Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27}

That is an amd64 problem and it is already being worked on. Sorry no
solution yet.

-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Bernhard Fröhlich 
On Thu, May 14, 2009 11:51 pm, Artem Belevich wrote:
> Few more notes from -CURRENT/amd64
>
> [snip]
>
> * Attempt to boot new VM (64-bit FreeBSD) from -current snapshot DVD
> ISO results in an error:
>
> Failed to start the virtual machine FreeBSD.
> Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG).
> Unknown error creating VM (VERR_SYMBOL_VALUE_TOO_BIG).
>
> Result Code: NS_ERROR_FAILURE (0x80004005)
> Component: Console
> Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27}


I cannot reproduce that anymore (probably hit another problem). Could you
please provide what the vbox-dev people asked for to solve that problem?

VBox.log from ~/.VirtualBox/Machines//Logs/VBox.log

and start with

export VBOX_LOG=+rt_ldr.e.l2.f
VirtualBox -startvm VM_NAME

the resulting .log file (created in the current directory!)

http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001411.html
http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001413.html

Thanks!

-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Martin Wilke 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Benoit,

can you please tell me which FreeBSD Version you use?

On Thu, May 14, 2009 at 11:49:22PM +0200, Benoit Calvez wrote:
> 
> I'm trying to build from amd64, but got the following error. Sorry but I
> didn't look, and it's a fresh paste:
> ===>  Configuring for virtualbox-2.2.2r19673
> Checking for environment: Determined build machine: freebsd.amd64, target
> machine: freebsd.amd64, OK.
> Checking for kBuild: found, OK.
> Checking for gcc: found version 4.2.1, OK.
> Checking for as86: found version 0.16.17, OK.
> Checking for bcc: found version 0.16.17, OK.
> Checking for iasl: found version 20070320, OK.
> Checking for xslt: found, OK.
> Checking for pthread: found, OK.
> Checking for libxml2: found version 2.7.3, OK.
> Checking for libxslt: found version 1.1.24, OK.
> Checking for libIDL: found version 0.8.13, OK.
> Checking for zlib: found version 1.2.3, OK.
> Checking for SDL: found version 1.2.13, OK.
> Checking for X libraries: found, OK.
> Checking for Xcursor: found, OK.
> Checking for Xmu: found, OK.
> Checking for Mesa / GLU: Xlib:  extension "Generic Event Extension" missing
> on display ":0.0".
> Xlib:  extension "Generic Event Extension" missing on display ":0.0".
> found version 1.2, OK.
> Checking for Qt4: found version 4.4.3, OK.
> Checking for Qt4 devtools: found version 4.4.3, OK.
> Checking for python support: found version 2.5.4, OK.
> 
> Successfully generated
> '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/AutoConfig.kmk'
> and '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh'.
> Source '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh'
> once before you start to build VBox:
> 
>   source /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh
>   kmk
> 
> 
>   +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING
> +++
>   Hardening is enabled which means that the VBox binaries will not run from
>   the binary directory. The binaries have to be installed suid root and some
>   more prerequisites have to be fulfilled which is normally done by
> installing
>   the final package. For development, the hardening feature can be disabled
>   by specifying the --disable-hardening parameter. Please never disable that
>   feature for the final distribution!
>   +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING
> +++
> 
> Enjoy!
> ===>  Building for virtualbox-2.2.2r19673
> cd /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673 && /bin/sh
> env.sh && VBOX_LIBPATH_X11=/usr/local
> /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/kBuild/bin/freebsd.amd64/kmk
> Config.kmk:1664:
> /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/GCCConfig.kmk:
> No such file or directory
> Config.kmk:3789:
> /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/revision.kmk:
> No such file or directory
> Fatal error 'kse_create() failed
> ' at line 469 in file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 2)
> *** Error code 1
> 
> 
> 
> 
> -- 
> Benoit C.
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> 

- -- 

+---+---+
|  PGP: 0xB1E6FCE9  |  Jabber : miwi(at)BSDCrew.de  |
|  ICQ: 169139903   |  Mail   : miwi(at)FreeBSD.org |
+---+---+
|   Mess with the Best, Die like the Rest!  |
+---+---+
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11 (FreeBSD)

iEYEARECAAYFAkoNPt8ACgkQdLJIhLHm/OmsIgCgpK7yToOVhb6/uMyJKshD8Zlw
tb4AnAmFSdyxF8NRaC7AxB6Px3oUwwM7
=vUAY
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Martin Wilke 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ok

We uploaded a new tarball what should be fix the build on AMD64.

Small changelog:
- - devel/kbuild is now dependency
- - remove misc/compat6 support

Note:
Use devel/bcc instead of devel/dev86 what means
If you have devel/bcc installed please deinstall

http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz

Please give us feedback :P


- - Martin

- -- 

+---+---+
|  PGP: 0xB1E6FCE9  |  Jabber : miwi(at)BSDCrew.de  |
|  ICQ: 169139903   |  Mail   : miwi(at)FreeBSD.org |
+---+---+
|   Mess with the Best, Die like the Rest!  |
+---+---+
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11 (FreeBSD)

iEYEARECAAYFAkoNQCUACgkQdLJIhLHm/OmgeQCgptEW5FhkmB8huDhs5LL63PhI
+04AoONjytolxD892zcCnlv81MRLceEv
=UJL8
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

finance/aqbanking lost command line tool with update

2009-05-15 Thread Jan Henrik Sylvester 
After ports/129598, finance/aqbanking was recently updated from 2.3.3 to 
3.8.1. This caused a major regression for me, as I was using the command 
line aqbanking-tool (and some shell scripts around it) as the banking 
client. In the 3.X series, that is not included anymore.


There is AqBanking-CLI now, for which a version has been put under GPL 
last week: 
http://sourceforge.net/mailarchive/forum.php?thread_name=200905062348.19839.aquamaniac%40gmx.de&forum_name=aqbanking-devel


It seems to be included in 3.99.12rc6 and 3.99.12rc7 according to the 
version history.


With this loss in functionality, it would have been nicer if the 2.X 
version was kept as finance/aqbanking2 -- at least until 
finance/aqbanking is upgraded to 4.X.


I guess I should try to downgrade the port and hope for 4.X to appear 
soon. I could try to create finance/aqbanking-devel from the rc, but if 
that is nontrivial, I guess I currently do not have the time to do it.


Did I miss something? Any further suggestions? Is anyone else affected? 
Did anyone start to work on the 4.X version?


Cheers,
Jan Henrik
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Masahiko KIMOTO 
I'm testing on today's 8-CURRENT/i386.

When start the virtual machine, kernel got panic with;

May 15 19:31:23 eterna kernel: panic: clone_create() on cdevsw without minor 
numbers
May 15 19:31:23 eterna kernel: cpuid = 0
May 15 19:31:23 eterna kernel: KDB: enter: panic

So I'm looking up the source code of vboxdrv.ko but couldn't find . -name
'vboxdrv.*' or something like.

What should I check out then?

--
Masahiko KIMOTO, Ph. D.
E-mail: kim...@ohnolab.orgURL: http://www.ohnolab.org/~kimoto
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Renato Botelho 
On Thu, May 14, 2009 at 4:12 PM, Martin Wilke  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Howdy Guys,
>
> After the announcement from Alexander Eichner about
> Virtualbox on FreeBSD, we started the work on a port
> for FreeBSD. Now we think that we solved the most
> problems and are ready for the first Call for Testing.
>
> Some notes before you can test the port:
> Make sure you are using RELENG_7 or higher. You have
> to use a fresh portstree with uptodate ports!! Please
> read carefully the pkg-messages.
>
> Some known issues / Troubleshooting:
> Sometimes the kernel on HEAD coredumps when loading
> or unloading the kernel module. A small workaround
> to prevent the crash is to not start X, mount proc,
> then load the kernel module and start X from the
> console. That helped me and some testers, maybe you
> too. :P AMD64 should be work in general, it builds
> and start. But not right tested at the moment. We
> want here also some feedback.
>
> Some Thanks:
> First of all we'd like to say many thanks to _ALL_
> vbox developers. Next people are Bernhard Froehlich
> (aka decke), Beat Gaetzi (beat@), Dennis Herrmann
> (dhn@), Pietro Cerutti (gahr@), myself (*gg*),
> and _ALL_ who helped and provided feedback.
>
> Happy Testing :-)
>
> Download:
>
>  http://people.freebsd.org/~miwi/vbox/vboxport.tgz
>
> Wiki Page:
>  http://wiki.freebsd.org/VirtualBox

Hello Martin

I've built it on i386/CURRENT r191522, but I couldn't load the
module, when i try, i got:

KLD vboxdrv.ko: depends on kernel - not available
kldload: can't load vboxdrv: File exists

It says file exists, but the module is not loaded

r...@botelhor:/home/garga# kldstat
Id Refs AddressSize Name
 1   18 0xc040 b584bc   kernel
 21 0xc0f59000 809c snd_via8233.ko
 32 0xc0f62000 4a438sound.ko
 41 0xc46af000 8000 linprocfs.ko
 51 0xc46c8000 24000linux.ko

Any idea?
-- 
Renato Botelho
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Gustau Pérez 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Renato Botelho wrote:
> On Thu, May 14, 2009 at 4:12 PM, Martin Wilke  wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>> Howdy Guys,
>>
>> After the announcement from Alexander Eichner about
>> Virtualbox on FreeBSD, we started the work on a port
>> for FreeBSD. Now we think that we solved the most
>> problems and are ready for the first Call for Testing.
>>
>> Some notes before you can test the port:
>> Make sure you are using RELENG_7 or higher. You have
>> to use a fresh portstree with uptodate ports!! Please
>> read carefully the pkg-messages.
>>
>> Some known issues / Troubleshooting:
>> Sometimes the kernel on HEAD coredumps when loading
>> or unloading the kernel module. A small workaround
>> to prevent the crash is to not start X, mount proc,
>> then load the kernel module and start X from the
>> console. That helped me and some testers, maybe you
>> too. :P AMD64 should be work in general, it builds
>> and start. But not right tested at the moment. We
>> want here also some feedback.
>>
>> Some Thanks:
>> First of all we'd like to say many thanks to _ALL_
>> vbox developers. Next people are Bernhard Froehlich
>> (aka decke), Beat Gaetzi (beat@), Dennis Herrmann
>> (dhn@), Pietro Cerutti (gahr@), myself (*gg*),
>> and _ALL_ who helped and provided feedback.
>>
>> Happy Testing :-)
>>
>> Download:
>>
>>  http://people.freebsd.org/~miwi/vbox/vboxport.tgz
>>
>> Wiki Page:
>>  http://wiki.freebsd.org/VirtualBox
>
> Hello Martin
>
> I've built it on i386/CURRENT r191522, but I couldn't load the
> module, when i try, i got:
>
> KLD vboxdrv.ko: depends on kernel - not available
> kldload: can't load vboxdrv: File exists
>
> It says file exists, but the module is not loaded
>
> r...@botelhor:/home/garga# kldstat
> Id Refs AddressSize Name
>  1   18 0xc040 b584bc   kernel
>  21 0xc0f59000 809c snd_via8233.ko
>  32 0xc0f62000 4a438sound.ko
>  41 0xc46af000 8000 linprocfs.ko
>  51 0xc46c8000 24000linux.ko
>
> Any idea?
   It seems to me you csup'ed your sources but you are still using the
old kernel. Try make buildkernell && make installkernel and then try
loading the module.

   Gus

PS : as a advice, I would do the installworld with
KODIR=/boot/test && nextboot -k test. If i works, you can reinstall
again the kernel as your default kernel .

- --
PGP KEY : http://www-entel.upc.edu/gus/gus.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkoNUH4ACgkQAvcpDulVChDcwQCfZv8oKZzE37j794kCfNt2Tdqq
z2YAn2BLpbl1Zm9eGRLvF3r2GtYBRSFr
=fXHv
-END PGP SIGNATURE-

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Masahiko KIMOTO 
 > > When start the virtual machine, kernel got panic with;
 > 
 > > May 15 19:31:23 eterna kernel: panic: clone_create() on cdevsw without 
 > > minor numbers
 > > May 15 19:31:23 eterna kernel: cpuid = 0
 > > May 15 19:31:23 eterna kernel: KDB: enter: panic
 > 
 > > So I'm looking up the source code of vboxdrv.ko but couldn't find . -name
 > > 'vboxdrv.*' or something like.
 > 
 > > What should I check out then?
 > 
 > Do you have all kernel modules from ports up to date with world/kernel?

Hmm,
Under /boot/kernel/ is up to date by make build/installkernel.
Under /boot/modules/, only vboxdrv.ko is in it, and is up to date.

--
Masahiko KIMOTO, Ph. D.
E-mail: kim...@ohnolab.orgURL: http://www.ohnolab.org/~kimoto

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Keyboard not working in gnome?

2009-05-15 Thread Christopher Arnold 


Hi again,

some more input on this.

In Xorg.0.log i see:
(II) config/hal: Adding input device USB Receiver
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device AT Keyboard
(EE) config/hal: NewInputDeviceRequest failed (8)
(The at part makes sense, i only have USB on this machine)

So i guess this is the problem and that a rebuild of gnome/X11 did not 
help. It seems fairly close to the issues with hald/xorg.conf that we saw 
the last time upgrading gnome.


What is actually the right config nowdays?

I have the following in xorg.conf:
Section "ServerLayout"
Identifier "Simple Layout"
Screen "Screen 1" 0 0
InputDevice"Mouse1" "CorePointer"
InputDevice"Keyboard1" "CoreKeyboard"
Option "AllowEmptyInput" "off"
Option "AutoAddDevices" "off"
EndSection

And in /etc/rc.conf:
bus_enable="YES"
hald_enable="YES"

Or does anyone have any hints on why a keyboard (that i'm currently 
writing on...) don't work in X11/Gnome?

Any hints on debugging this?

/Chris

On Thu, 14 May 2009, Christopher Arnold wrote:



Hi,

i'm currently debugging why my keyboard is not working in gnome, so i thought 
i might throw out a quick question here if someone else have run into this?


Details:
Im running 7.1-STABLE.

It's a logitech wireless keyboard and mouse (connected with USB) that have 
been woriking for a couple of years. (Actually i'm writing on it now, but in 
a vty) Suddenly in the middle of a session everything hung, so i rebooted.


Now i managed to login (That is it works in gdm!) but when i open a xterm or 
any other program it does not work. (as in no keys work not even caps lock) 
The mouse works perfectly. And since the mouse works i can use the GUI to 
logout and back in gdm keyboard works again...


My first thought was that i might have rebuilt some port affecting this, so 
currently i'm rebuilding X11 and gnome.


Have anyone else run into this?
Any hints on what might be wrong?

/Chris
___
freebsd-questi...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Gorbatovsky Dmitry 

Thanks for grate work!

I install on VirtualBox FreeBSD 7.1, Ubuntu, Windows 7
and it work fine.

%uname -a
FreeBSD user 7.2-RELEASE FreeBSD 7.2-RELEASE #1: Thu May  7 15:46:13 MSD 
2009 r...@user:/usr/obj/usr/src/sys/GENERIC  i386


Dmitry. 



___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Sergey V. Dyatko 
В Fri, 15 May 2009 19:50:26 +0900 (JST)
Masahiko KIMOTO  пишет:

MK> I'm testing on today's 8-CURRENT/i386.
MK> 
MK> When start the virtual machine, kernel got panic with;
MK> 
MK> May 15 19:31:23 eterna kernel: panic: clone_create() on cdevsw
MK> without minor numbers May 15 19:31:23 eterna kernel: cpuid = 0
MK> May 15 19:31:23 eterna kernel: KDB: enter: panic
MK> 
MK> So I'm looking up the source code of vboxdrv.ko but couldn't find .
MK> -name 'vboxdrv.*' or something like.
MK> 
MK> What should I check out then?
MK> 
/boot/modules/vboxdrv.ko ?

MK> --
MK> Masahiko KIMOTO, Ph. D.
MK> E-mail: kim...@ohnolab.orgURL:
MK> http://www.ohnolab.org/~kimoto



--
wbr, tiger
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Rink Springer 
On Fri, May 15, 2009 at 08:17:07AM -0300, Renato Botelho wrote:
> I've built it on i386/CURRENT r191522, but I couldn't load the
> module, when i try, i got:
> 
> KLD vboxdrv.ko: depends on kernel - not available
> kldload: can't load vboxdrv: File exists

This generally means your kernel sources and binary are not in sync.
Just rebuild and reinstall your kernel and all modules and you will be
fine.

Regards,

-- 
Rink P.W. Springer- http://rink.nu
"Talk to me."
- Horatio Caine
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Boris Samorodov 
On Fri, 15 May 2009 19:50:26 +0900 (JST) Masahiko KIMOTO wrote:

> I'm testing on today's 8-CURRENT/i386.

So do I. But virtualbox works here. Until any VM got shutdown -- none
can be started.

> When start the virtual machine, kernel got panic with;

> May 15 19:31:23 eterna kernel: panic: clone_create() on cdevsw without minor 
> numbers
> May 15 19:31:23 eterna kernel: cpuid = 0
> May 15 19:31:23 eterna kernel: KDB: enter: panic

> So I'm looking up the source code of vboxdrv.ko but couldn't find . -name
> 'vboxdrv.*' or something like.

> What should I check out then?

Do you have all kernel modules from ports up to date with world/kernel?


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Boris Samorodov 
On Fri, 15 May 2009 08:17:07 -0300 Renato Botelho wrote:

> I've built it on i386/CURRENT r191522, but I couldn't load the
> module, when i try, i got:

> KLD vboxdrv.ko: depends on kernel - not available

I didn't see that message.

> kldload: can't load vboxdrv: File exists

While this is familiar for me. I've got it when build virtualbox
with newer kernel sources (it so happened that I csuped src but
had no time to rebuild/reinstall) than the installed kernel.

> It says file exists, but the module is not loaded

> r...@botelhor:/home/garga# kldstat
> Id Refs AddressSize Name
>  1   18 0xc040 b584bc   kernel
>  21 0xc0f59000 809c snd_via8233.ko
>  32 0xc0f62000 4a438sound.ko
>  41 0xc46af000 8000 linprocfs.ko
>  51 0xc46c8000 24000linux.ko

> Any idea?


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Amavis::SpamControl->new not found

2009-05-15 Thread Thomas Hummel 
On Tue, May 12, 2009 at 01:53:35PM +0200, Thomas Hummel wrote:

>   # /usr/local/etc/rc.d/amavisd start
>   Starting amavisd.
>   Can't locate object method "new" via package "Amavis::SpamControl" at 
> /usr/local/sbin/amavisd line 13878.
> 
> On this particular server, I don't want spam check at all, so 
> /usr/local/etc/amavisd.conf states :
> 
>   @bypass_spam_checks_maps  = (1);  # controls running of anti-spam code
> 
> which doesn't seem to be overriden anwhere else.
> 
> Line 13878 of /usr/local/sbin/amavisd states :
> 
>   $spamcontrol_obj = Amavis::SpamControl->new  if $extra_code_antispam;
> 
> Considering I don't need spam check at all, I tried commenting this line and
> amavisd-new started and seemed to work.


Today, I tried something different :

  . comment @bypass_spam_checks_maps  = (1); in amavisd.conf, thus getting the
 default as stated in amavid, which is

 @bypass_spam_checks_maps = (
  \%bypass_spam_checks, \...@bypass_spam_checks_acl, 
\$bypass_spam_checks_re);


  . assume that spam checks won't be launched even if I commented
@bypass_spam_checks_maps since my amavisd.conf states

$sa_mail_body_size_limit = 1; # don't waste time on SA if mail is larger
# default: undef, no limitations

Although amavisd launch succeeded then, as a side effet I got many messages
returned with 

  Subject: Considered UNSOLICITED BULK EMAIL, apparently from you
  >From: "Content-filter at [...]

So I reverted to the solution described in my previous message.

Conclusion : 


it seems to me that :

  . amavisd miss somewhere the "import" of the Amavis::SpamControl package (I
don't see such import anywhere)

  . @bypass_spam_checks_maps  = (1); doesn't bypass everything since 

 $spamcontrol_obj = Amavis::SpamControl->new  if $extra_code_antispam;

   is still executed.

  .  $sa_mail_body_size_limit = 1; isn't enough to fully bypass spam engine 
since some
 messages where marked UBE.

Thanks

-- 
Thomas Hummel   | Institut Pasteur
 | Pôle informatique - systèmes et réseau
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Boris Samorodov 
On Fri, 15 May 2009 12:12:54 +0200 Martin Wilke wrote:

> We uploaded a new tarball what should be fix the build on AMD64.

> Small changelog:
> - devel/kbuild is now dependency
> - remove misc/compat6 support

> Note:
> Use devel/bcc instead of devel/dev86 what means
> If you have devel/bcc installed please deinstall

> http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz

> Please give us feedback :P

I've got an error at my 8-CURRENT tinderbox:
-

===>  Building package for virtualbox-2.2.2r19673
tar: lib/virtualbox/VBoxREM32.so: Cannot stat: No such file or directory
tar: lib/virtualbox/VBoxREM64.so: Cannot stat: No such file or directory
tar: Removing leading '/' from member names
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
-

Seems that for 64 bit platform none of VBoxREM[32|64].so are
created.

BTW, those who are interested at the subject from mail lists
ports@, emulation@ and current@ already knows the great news.
May be it's time to move to one list, say, virtualizat...@?


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Martin Wilke 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, May 15, 2009 at 05:23:34PM +0400, Boris Samorodov wrote:
> On Fri, 15 May 2009 12:12:54 +0200 Martin Wilke wrote:
> 
> > We uploaded a new tarball what should be fix the build on AMD64.
> 
> > Small changelog:
> > - devel/kbuild is now dependency
> > - remove misc/compat6 support
> 
> > Note:
> > Use devel/bcc instead of devel/dev86 what means
> > If you have devel/bcc installed please deinstall
> 
> > http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz
> 
> > Please give us feedback :P
> 
> I've got an error at my 8-CURRENT tinderbox:
> -
> 
> ===>  Building package for virtualbox-2.2.2r19673
> tar: lib/virtualbox/VBoxREM32.so: Cannot stat: No such file or directory
> tar: lib/virtualbox/VBoxREM64.so: Cannot stat: No such file or directory
> tar: Removing leading '/' from member names
> tar: Error exit delayed from previous errors.
> pkg_create: make_dist: tar command failed with code 256
> -
> 
> Seems that for 64 bit platform none of VBoxREM[32|64].so are
> created.

Ups :(. Seems we was to fast. I'll fix that soon ;).

> 
> BTW, those who are interested at the subject from mail lists
> ports@, emulation@ and current@ already knows the great news.
> May be it's time to move to one list, say, virtualizat...@?
> 

Maybe :-). But for the moment it's a good place to deal with 
vbox.

> 
> WBR
> -- 
> Boris Samorodov (bsam)
> Research Engineer, http://www.ipt.ru Telephone & Internet SP
> FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
> 

- -- 

+---+---+
|  PGP: 0xB1E6FCE9  |  Jabber : miwi(at)BSDCrew.de  |
|  ICQ: 169139903   |  Mail   : miwi(at)FreeBSD.org |
+---+---+
|   Mess with the Best, Die like the Rest!  |
+---+---+
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11 (FreeBSD)

iEUEARECAAYFAkoNbe8ACgkQdLJIhLHm/OngAwCY2KHMIweS1sARJw/BW2ehMjMr
zgCgy9Kh3bwk9ik4uX6t7slfghIr7u8=
=ohI6
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Keyboard not working in gnome?

2009-05-15 Thread Robert Noland 
On Fri, 2009-05-15 at 13:05 +0200, Christopher Arnold wrote:
> Hi again,
> 
> some more input on this.
> 
> In Xorg.0.log i see:
> (II) config/hal: Adding input device USB Receiver
> (EE) config/hal: NewInputDeviceRequest failed (8)
> (II) config/hal: Adding input device AT Keyboard
> (EE) config/hal: NewInputDeviceRequest failed (8)
> (The at part makes sense, i only have USB on this machine)
> 
> So i guess this is the problem and that a rebuild of gnome/X11 did not 
> help. It seems fairly close to the issues with hald/xorg.conf that we saw 
> the last time upgrading gnome.
> 
> What is actually the right config nowdays?
> 
> I have the following in xorg.conf:
> Section "ServerLayout"
>  Identifier "Simple Layout"
>  Screen "Screen 1" 0 0
>  InputDevice"Mouse1" "CorePointer"
>  InputDevice"Keyboard1" "CoreKeyboard"
>  Option "AllowEmptyInput" "off"
>  Option "AutoAddDevices" "off"
> EndSection

Using the above, you shouldn't need the lines below.  Your devices need
to be statically configured in xorg.conf.  If you are using hald, then
remove both the AllowEmptyInput and AutoAddDevices lines above.  I
currently use moused as well, since there still seems to be some
occasional issue with my mouse if I try and use native psm...

robert.

> And in /etc/rc.conf:
> bus_enable="YES"
> hald_enable="YES"
> 
> Or does anyone have any hints on why a keyboard (that i'm currently 
> writing on...) don't work in X11/Gnome?
> Any hints on debugging this?
> 
>   /Chris
> 
> On Thu, 14 May 2009, Christopher Arnold wrote:
> 
> >
> > Hi,
> >
> > i'm currently debugging why my keyboard is not working in gnome, so i 
> > thought 
> > i might throw out a quick question here if someone else have run into this?
> >
> > Details:
> > Im running 7.1-STABLE.
> >
> > It's a logitech wireless keyboard and mouse (connected with USB) that have 
> > been woriking for a couple of years. (Actually i'm writing on it now, but 
> > in 
> > a vty) Suddenly in the middle of a session everything hung, so i rebooted.
> >
> > Now i managed to login (That is it works in gdm!) but when i open a xterm 
> > or 
> > any other program it does not work. (as in no keys work not even caps lock) 
> > The mouse works perfectly. And since the mouse works i can use the GUI to 
> > logout and back in gdm keyboard works again...
> >
> > My first thought was that i might have rebuilt some port affecting this, so 
> > currently i'm rebuilding X11 and gnome.
> >
> > Have anyone else run into this?
> > Any hints on what might be wrong?
> >
> > /Chris
> > ___
> > freebsd-questi...@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
> >
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
-- 
Robert Noland 
FreeBSD


signature.asc
Description: This is a digitally signed message part

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Paul Wootton 

Martin Wilke wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ok

We uploaded a new tarball what should be fix the build on AMD64.

Small changelog:
- - devel/kbuild is now dependency
- - remove misc/compat6 support

Note:
Use devel/bcc instead of devel/dev86 what means
If you have devel/bcc installed please deinstall

http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz

Please give us feedback :P


- - Martin

- -- 


+---+---+
|  PGP: 0xB1E6FCE9  |  Jabber : miwi(at)BSDCrew.de  |
|  ICQ: 169139903   |  Mail   : miwi(at)FreeBSD.org |
+---+---+
|   Mess with the Best, Die like the Rest!  |
+---+---+
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11 (FreeBSD)

iEYEARECAAYFAkoNQCUACgkQdLJIhLHm/OmgeQCgptEW5FhkmB8huDhs5LL63PhI
+04AoONjytolxD892zcCnlv81MRLceEv
=UJL8
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


  

Hi,
When compiling I get the following error

kBuild: Installing tstUtf8 => 
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/testcase/tstUtf8
kBuild: Installing tstUuid => 
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/testcase/tstUuid
kBuild: Installing tstVMStructGC => 
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/tstVMStructGC
kBuild: Generating tstVMStructSize - 
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/tstVMStructGC: 
1: Syntax error: "(" unexpected
kmk[2]: *** 
[/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h] 
Error 2
kmk[2]: *** Deleting file 
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h'

kmk[2]: *** Waiting for unfinished jobs
awk -f /usr/src/sys/conf/kmod_syms.awk  
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/vboxdrv/vboxdrv.ko  
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.def 
| xargs -J% objcopy % 
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/vboxdrv/vboxdrv.ko
awk: can't open file 
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.def

source line number 10
kmk[2]: Leaving directory 
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673'
kmk[2]: Entering directory 
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673'

kmk[2]: *** Exiting with status 2
kmk[1]: *** [pass_binaries_this] Error 2
kmk[1]: Leaving directory 
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673'

kmk: *** [pass_binaries_order] Error 2
*** Error code 2

Stop in /root/vBox/virtualbox.
demophon#


demophon# uname -a
FreeBSD demophon 8.0-CURRENT FreeBSD 8.0-CURRENT #10: Wed May  6 
09:04:17 UTC 2009 p...@demophon:/usr/obj/usr/src/sys/DEMOPHON  amd64


Any ideas?

Cheers
Paul
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Keyboard not working in gnome?

2009-05-15 Thread Andrew Gould 


>
>
> > And in /etc/rc.conf:
> > bus_enable="YES"


Shouldn't the line above be:

dbus_enable="YES"


>
> > hald_enable="YES"
> >
> > Or does anyone have any hints on why a keyboard (that i'm currently
> > writing on...) don't work in X11/Gnome?
> > Any hints on debugging this?
> >
> >   /Chris
>

Andrew
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Keyboard not working in gnome?

2009-05-15 Thread Robert Noland 
On Fri, 2009-05-15 at 10:09 -0500, Andrew Gould wrote:
>  
> 
> 
> 
> > And in /etc/rc.conf:
> > bus_enable="YES"
> 
> Shouldn't the line above be:
> 
> dbus_enable="YES"

Yes, sorry... typo...

robert.

> 
> 
> > hald_enable="YES"
> >
> > Or does anyone have any hints on why a keyboard (that i'm
> currently
> > writing on...) don't work in X11/Gnome?
> > Any hints on debugging this?
> >
> >   /Chris
> 
> Andrew
-- 
Robert Noland 
FreeBSD


signature.asc
Description: This is a digitally signed message part

OpenSSH 5.2 and PuTTY

2009-05-15 Thread Jan Sebosik 

Hi all

anybody experiences issues connecting to openssh-portable server v5.2 with Putty 
0.6 client ?

Previous version 5.1 worked properly.

FreeBSD is 6-STABLE from april 2009.

Best regards
--
Jan Sebosik, Slovakia
sebo...@demax.sk
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Keyboard not working in gnome?

2009-05-15 Thread Christopher Arnold 



On Fri, 15 May 2009, Robert Noland wrote:


On Fri, 2009-05-15 at 13:05 +0200, Christopher Arnold wrote:

Hi again,

some more input on this.

In Xorg.0.log i see:
(II) config/hal: Adding input device USB Receiver
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device AT Keyboard
(EE) config/hal: NewInputDeviceRequest failed (8)
(The at part makes sense, i only have USB on this machine)

So i guess this is the problem and that a rebuild of gnome/X11 did not
help. It seems fairly close to the issues with hald/xorg.conf that we saw
the last time upgrading gnome.

What is actually the right config nowdays?

I have the following in xorg.conf:
Section "ServerLayout"
 Identifier "Simple Layout"
 Screen "Screen 1" 0 0
 InputDevice"Mouse1" "CorePointer"
 InputDevice"Keyboard1" "CoreKeyboard"
 Option "AllowEmptyInput" "off"
 Option "AutoAddDevices" "off"
EndSection


Using the above, you shouldn't need the lines below.  Your devices need
to be statically configured in xorg.conf.  If you are using hald, then
remove both the AllowEmptyInput and AutoAddDevices lines above.  I

When i commment theese out i get neither keyboard or mouse.
Also i notice in the xorg logfile that my "Keyboard1" gets ignored 
alltogether. That is if i would have got the keyboard to work i would have 
a us one instead of my swedish.



And in /etc/rc.conf:
bus_enable="YES"
hald_enable="YES"

If i comment these out then gdm dosn't even start since gdm requiers them 
i guess.


And yes this is a cutnpaste error...

Btw my config file and the logfiles are here:
http://www.arnold.se/xorg.conf
http://www.arnold.se/Xorg.0.log
http://www.arnold.se/Xorg.0.log.old

I guess i am doing a simple mistake somwhere, just cant figure what...

/Chris


Or does anyone have any hints on why a keyboard (that i'm currently
writing on...) don't work in X11/Gnome?
Any hints on debugging this?

/Chris

On Thu, 14 May 2009, Christopher Arnold wrote:



Hi,

i'm currently debugging why my keyboard is not working in gnome, so i thought
i might throw out a quick question here if someone else have run into this?

Details:
Im running 7.1-STABLE.

It's a logitech wireless keyboard and mouse (connected with USB) that have
been woriking for a couple of years. (Actually i'm writing on it now, but in
a vty) Suddenly in the middle of a session everything hung, so i rebooted.

Now i managed to login (That is it works in gdm!) but when i open a xterm or
any other program it does not work. (as in no keys work not even caps lock)
The mouse works perfectly. And since the mouse works i can use the GUI to
logout and back in gdm keyboard works again...

My first thought was that i might have rebuilt some port affecting this, so
currently i'm rebuilding X11 and gnome.

Have anyone else run into this?
Any hints on what might be wrong?

/Chris
___
freebsd-questi...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

--
Robert Noland 
FreeBSD


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Keyboard not working in gnome?

2009-05-15 Thread Christopher Arnold 

Problem solved, see below..

On Fri, 15 May 2009, Christopher Arnold wrote:


On Fri, 15 May 2009, Robert Noland wrote:


On Fri, 2009-05-15 at 13:05 +0200, Christopher Arnold wrote:

In Xorg.0.log i see:
(II) config/hal: Adding input device USB Receiver
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device AT Keyboard
(EE) config/hal: NewInputDeviceRequest failed (8)
(The at part makes sense, i only have USB on this machine)

So i guess this is the problem and that a rebuild of gnome/X11 did not
help. It seems fairly close to the issues with hald/xorg.conf that we saw
the last time upgrading gnome.

What is actually the right config nowdays?

I have the following in xorg.conf:
Section "ServerLayout"
 Identifier "Simple Layout"
 Screen "Screen 1" 0 0
 InputDevice"Mouse1" "CorePointer"
 InputDevice"Keyboard1" "CoreKeyboard"
 Option "AllowEmptyInput" "off"
 Option "AutoAddDevices" "off"
EndSection


Using the above, you shouldn't need the lines below.  Your devices need
to be statically configured in xorg.conf.  If you are using hald, then
remove both the AllowEmptyInput and AutoAddDevices lines above.  I

When i commment theese out i get neither keyboard or mouse.
Also i notice in the xorg logfile that my "Keyboard1" gets ignored 
alltogether. That is if i would have got the keyboard to work i would have a 
us one instead of my swedish.



And in /etc/rc.conf:
bus_enable="YES"
hald_enable="YES"

If i comment these out then gdm dosn't even start since gdm requiers them i 
guess.


With AllowEmptyInput and AutoAddDevices set to "off" and both dbus and 
hald enabled it now works... Why?


Well i tried and xterm as usual and it didn't work. Decided to check if 
another program accepted input to rule out an error in xterm. So i used 
preferences/keyboard instead. I didn't expect it to work so i just pressed 
a key and kept it down. Klick and then characters!


So in the end i managed to find out that slow keys somehow had become 
enabled in universal access preferences


Embarrasing...

But it is a bit strange that your suggestions did not work.
How come some people need the AllowEmptyInput and AutoAddDevices lines but 
not others?


/Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Keyboard not working in gnome?

2009-05-15 Thread Robert Noland 
On Fri, 2009-05-15 at 18:56 +0200, Christopher Arnold wrote:
> Problem solved, see below..
> 
> On Fri, 15 May 2009, Christopher Arnold wrote:
> 
> > On Fri, 15 May 2009, Robert Noland wrote:
> >
> >> On Fri, 2009-05-15 at 13:05 +0200, Christopher Arnold wrote:
> >>> In Xorg.0.log i see:
> >>> (II) config/hal: Adding input device USB Receiver
> >>> (EE) config/hal: NewInputDeviceRequest failed (8)
> >>> (II) config/hal: Adding input device AT Keyboard
> >>> (EE) config/hal: NewInputDeviceRequest failed (8)
> >>> (The at part makes sense, i only have USB on this machine)
> >>> 
> >>> So i guess this is the problem and that a rebuild of gnome/X11 did not
> >>> help. It seems fairly close to the issues with hald/xorg.conf that we saw
> >>> the last time upgrading gnome.
> >>> 
> >>> What is actually the right config nowdays?
> >>> 
> >>> I have the following in xorg.conf:
> >>> Section "ServerLayout"
> >>>  Identifier "Simple Layout"
> >>>  Screen "Screen 1" 0 0
> >>>  InputDevice"Mouse1" "CorePointer"
> >>>  InputDevice"Keyboard1" "CoreKeyboard"
> >>>  Option "AllowEmptyInput" "off"
> >>>  Option "AutoAddDevices" "off"
> >>> EndSection
> >> 
> >> Using the above, you shouldn't need the lines below.  Your devices need
> >> to be statically configured in xorg.conf.  If you are using hald, then
> >> remove both the AllowEmptyInput and AutoAddDevices lines above.  I
> > When i commment theese out i get neither keyboard or mouse.
> > Also i notice in the xorg logfile that my "Keyboard1" gets ignored 
> > alltogether. That is if i would have got the keyboard to work i would have 
> > a 
> > us one instead of my swedish.
> >
> >>> And in /etc/rc.conf:
> >>> bus_enable="YES"
> >>> hald_enable="YES"
> >>> 
> > If i comment these out then gdm dosn't even start since gdm requiers them i 
> > guess.
> >
> With AllowEmptyInput and AutoAddDevices set to "off" and both dbus and 
> hald enabled it now works... Why?

This means that you are using purely static configured devices from
xorg.conf.

> Well i tried and xterm as usual and it didn't work. Decided to check if 
> another program accepted input to rule out an error in xterm. So i used 
> preferences/keyboard instead. I didn't expect it to work so i just pressed 
> a key and kept it down. Klick and then characters!
> 
> So in the end i managed to find out that slow keys somehow had become 
> enabled in universal access preferences
> 
> Embarrasing...
> 
> But it is a bit strange that your suggestions did not work.
> How come some people need the AllowEmptyInput and AutoAddDevices lines but 
> not others?

It looks like hal is seeing your keyboard, but I don't see it picking up
the mouse.  You would need to look at lshal to figure out what is going
on there.  If you are using hal with a non-us keyboard layout you
probably want to search the archives for the fdi setup to configure your
keyboard layout.

robert.

>   /Chris
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
-- 
Robert Noland 
FreeBSD


signature.asc
Description: This is a digitally signed message part

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Mark Kane 
On Fri, May 15, 2009, at 11:53:39 +0200, Bernhard Fröhlich wrote:
> On Thu, May 14, 2009 11:51 pm, Artem Belevich wrote:
> > Few more notes from -CURRENT/amd64
> >
> > [snip]
> >
> > * Attempt to boot new VM (64-bit FreeBSD) from -current snapshot DVD
> > ISO results in an error:
> >
> > Failed to start the virtual machine FreeBSD.
> > Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG).
> > Unknown error creating VM (VERR_SYMBOL_VALUE_TOO_BIG).
> >
> > Result Code: NS_ERROR_FAILURE (0x80004005)
> > Component: Console
> > Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27}
> 
> 
> I cannot reproduce that anymore (probably hit another problem). Could
> you please provide what the vbox-dev people asked for to solve that
> problem?
> 
> VBox.log from ~/.VirtualBox/Machines//Logs/VBox.log
> 
> and start with
> 
> export VBOX_LOG=+rt_ldr.e.l2.f
> VirtualBox -startvm VM_NAME
> 
> the resulting .log file (created in the current directory!)
> 
> http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001411.html
> http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001413.html
> 
> Thanks!

Hi.

I just wanted to add that the kldload and "VERR_SYMBOL_VALUE_TOO_BIG"
errors that Artem posted also occur on RELENG_7/amd64. I rebuilt with
debug enabled and set the environment variable per the posts on the
VirtualBox mailing list and have included the requested logs below
(along with some additional info from /var/log/messages about the
kernel module).

One note: when running the version with debug I haven't really seen the
original error about "VERR_SYMBOL_VALUE_TOO_BIG" in any of the logs and
it doesn't pop up on screen anymore when the the VM fails to start; the
window just disappears after failing to start.

http://tntpowerhost.com/mixx941/freebsd/virtualbox_logs_20090515.txt

Thanks in advance!

-Mark

-- 
Internet Radio:
Party107 (Trance/Electronic) - http://www.party107.com

IRC:
MIXXnet IRC Network - irc.mixxnet.net (Nick: MarkK)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

fftw3

2009-05-15 Thread ajtiM 

Hi!

I did try to update the syste (FreBSD 7.2) with portmaster and there were 
error 1 with fftw3.
Now is stale dependency: akode-2.0.2,1 --> fftw3-3.1.3
I ran pkgdb -F and I got:

pkgdb -F
--->  Checking the package registry database
Stale dependency: akode-2.0.2,1 -> fftw3-3.1.3 (math/fftw3):
Install stale dependency? ([y]es/[n]o/[a]ll) [yes] yes
[Gathering depends for math/fftw3 .. done]
--->  Installing 'gcc-4.3.4_20090503' from a port (lang/gcc43)
--->  Building '/usr/ports/lang/gcc43'
===>  Cleaning for gcc-4.3.4_20090503
Making GCC 4.3.4 for FreeBSD 7.2  target=i386-portbld-freebsd7.2
You need to increase the datasize limit to at least 70 (and set
kern.maxdsiz="734003200" in /boot/loader.conf) to build with Java
support.
*** Error code 1

Stop in /usr/ports/lang/gcc43.
** Command failed [exit code 
1]: /usr/bin/script -qa /tmp/portinstall20090515-4729-1ghjdqc-0 env make
** Fix the problem and try again.
--->  Skipping 'math/fftw3' because a requisite port 'lang/gcc43' failed 
(specify -k to force)
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! lang/gcc43(unknown build error)
* math/fftw3
Command failed [exit code 1]: /usr/local/sbin/portinstall math/fftw3


Thanks.
 
Mitja
-
http://starikarp.redbubble.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Tim Bishop 
Hi Martin,

On Thu, May 14, 2009 at 09:12:37PM +0200, Martin Wilke wrote:
> After the announcement from Alexander Eichner about
> Virtualbox on FreeBSD, we started the work on a port
> for FreeBSD. Now we think that we solved the most
> problems and are ready for the first Call for Testing.

Is the VRDP stuff meant to work? When following these instructions it
just appears athat it doesn't start it up (nothing is listening on
3389):

http://www.virtualbox.org/manual/UserManual.html#vboxheadless

Thanks for your work making VirtualBox available to us!

Tim.

-- 
Tim Bishop
http://www.bishnet.net/tim/
PGP Key: 0x5AE7D984
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: ghostscript8 port not building

2009-05-15 Thread Josh Rickmar 

On Tue, 5 May 2009, Josh Rickmar wrote:


Hi all.  I've been having this problem for some time, but have just
gotten around to posting it to this list.  Basically, I have
ghostscript8-nox11-8.64 installed and want to upgrade it to 8.64_1.

This is the error that I am getting:

cc  -DHAVE_MKSTEMP -DHAVE_HYPOT   -DHAVE_FONTCONFIG -O2
-fno-strict-aliasing -pipe -march=prescott -fPIC -DUPD_SIGNAL=0 -I.
-I/usr/ports/print/ghostscript8/work/ghostscript-8.64/jasper/src/libjasper/
include -I/usr/local/include/libpng -I/usr/local/include  -Wall
-Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes
-Wwrite-strings -Wno-strict-aliasing -Wdeclaration-after-statem
ent -fno-builtin -fno-common -DHAVE_STDINT_H
-DGX_COLOR_INDEX_TYPE="unsigned long long" -O2 -fno-strict-aliasing
-pipe -march=prescott -DUSE_LIBICONV_GNU -DGS_DEVS_SHARED
-DGS_DEVS_SHARED_DIR=\"/usr/
local/lib/ghostscript/8.64\" -I./psi -I./obj/../soobj -I./obj/../soobj
-I./base  -o ./obj/../soobj/iconfig.o -c ./obj/../soobj/iconfig.c
cc  -DHAVE_MKSTEMP -DHAVE_HYPOT   -DHAVE_FONTCONFIG -O2
-fno-strict-aliasing -pipe -march=prescott -fPIC -DUPD_SIGNAL=0 -I.
-I/usr/ports/print/ghostscript8/work/ghostscript-8.64/jasper/src/libjasper/
include -I/usr/local/include/libpng -I/usr/local/include  -Wall
-Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes
-Wwrite-strings -Wno-strict-aliasing -Wdeclaration-after-statem
ent -fno-builtin -fno-common -DHAVE_STDINT_H
-DGX_COLOR_INDEX_TYPE="unsigned long long" -O2 -fno-strict-aliasing
-pipe -march=prescott -DUSE_LIBICONV_GNU -DGS_DEVS_SHARED
-DGS_DEVS_SHARED_DIR=\"/usr/
local/lib/ghostscript/8.64\" -I./obj/../soobj -I./base  -o
./obj/../soobj/gsromfs0.o -c ./base/gsromfs0.c
./obj/../soobj/echogs -w ./obj/../soobj/ldt.tr -n - cc -L/usr/local/lib
-L/usr/local/lib -shared -Wl,-soname=libgs.so.8 -o
./bin/../sobin/libgs.so.8.64
./obj/../soobj/echogs -a ./obj/../soobj/ldt.tr -n -s
./obj/../soobj/gsromfs0.o ./obj/../soobj/gs.o -s
cat ./obj/../soobj/ld.tr >>./obj/../soobj/ldt.tr
./obj/../soobj/echogs -a ./obj/../soobj/ldt.tr -s - -lm  -liconv
-lstdc++  -L/usr/local/lib -lfontconfig   -Wl,-export-dynamic -lpthread
-lm
if [ x != x ]; then LD_RUN_PATH=; export LD_RUN_PATH; fi; \
   XCFLAGS= XINCLUDE= XLDFLAGS= XLIBDIRS= XLIBS= \
   FEATURE_DEVS= DEVICE_DEVS= DEVICE_DEVS1= DEVICE_DEVS2=
DEVICE_DEVS3= \
   DEVICE_DEVS4= DEVICE_DEVS5= DEVICE_DEVS6= DEVICE_DEVS7=
DEVICE_DEVS8= \
   DEVICE_DEVS9= DEVICE_DEVS10= DEVICE_DEVS11= DEVICE_DEVS12= \
   DEVICE_DEVS13= DEVICE_DEVS14= DEVICE_DEVS15= DEVICE_DEVS16= \
   DEVICE_DEVS17= DEVICE_DEVS18= DEVICE_DEVS19= DEVICE_DEVS20= \
   DEVICE_DEVS_EXTRA= \
   /bin/sh <./obj/../soobj/ldt.tr
./obj/../soobj/gdevl256.o(.text+0x73a): In function `gs_shared_init':
: multiple definition of `gs_shared_init'
./obj/../soobj/gdevxalt.o(.text+0x1759): first defined here
/usr/bin/ld: Warning: size of symbol `gs_shared_init' changed from 150
in ./obj/../soobj/gdevxalt.o to 38 in ./obj/../soobj/gdevl256.o
./obj/../soobj/gdevvglb.o(.text+0x995): In function `gs_shared_init':
: multiple definition of `gs_shared_init'
./obj/../soobj/gdevxalt.o(.text+0x1759): first defined here
gmake[1]: *** [bin/../sobin/libgs.so.8.64] Error 1
gmake[1]: Leaving directory
`/usr/ports/print/ghostscript8/work/ghostscript-8.64'
gmake: *** [so] Error 2
*** Error code 1


Any help?  I am on 7.2-RELEASE now, but I was also getting this error
while still on 7.1.




Well, I finally got frustrated with this problem and blew-away all of my
ports, to see if I had messed up something by accident.  I also removed
/var/db/ports/ghostscript8/options to make sure that that was not
affecting it.

Here is the my new error:

cc  -DHAVE_MKSTEMP -DHAVE_HYPOT   -DHAVE_FONTCONFIG -O2 -fno-strict-aliasing 
-pipe -march
=prescott -fPIC -DUPD_SIGNAL=0 -I. 
-I/usr/ports/print/ghostscript8/work/ghostscript-8.64/
jasper/src/libjasper/include -I/usr/local/include/libpng -I/usr/local/include  
-Wall -Wst
rict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes 
-Wwrite-strings -Wno-
strict-aliasing -Wdeclaration-after-statement -fno-builtin -fno-common 
-DHAVE_STDINT_H -D
GX_COLOR_INDEX_TYPE="unsigned long long" -O2 -fno-strict-aliasing -pipe 
-march=prescott -
DUSE_LIBICONV_GNU -DGS_DEVS_SHARED 
-DGS_DEVS_SHARED_DIR=\"/usr/local/lib/ghostscript/8.64
\" -I./base/rinkj -o ./obj/../soobj/rinkj-screen-eb.o -c ./base/rinkj/rinkj-screen-eb.c 
./base/rinkj/rinkj-screen-eb.c: In function 'rinkj_screen_eb_write': 
./base/rinkj/rinkj-screen-eb.c:176: warning: assignment discards qualifiers from pointer 
target type 
./base/rinkj/rinkj-screen-eb.c:184: warning: passing argument 2 of 'even_better_line' fro
m incompatible pointer type 
./base/rinkj/rinkj-screen-eb.c:184: warning: passing argument 3 of 'even_better_line' fro
m incompatible pointer type 
./base/rinkj/rinkj-screen-eb.c: In function 'rinkj_screen_eb_init': 
./base/rinkj/rinkj-screen-eb.c:84: warning: 'strengths' may be used uninitialized

Re: Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Андрей 
> We uploaded a new tarball what should be fix the build on AMD64.
>
> Small changelog:
> - - devel/kbuild is now dependency
> - - remove misc/compat6 support
>
> Note:
> Use devel/bcc instead of devel/dev86 what means
> If you have devel/bcc installed please deinstall
>
> http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz

>
> Please give us feedback :P

I've got an make error at my 8-CURRENT amd64  Wed Apr 29 20:02:37 MSD 2009


kBuild: Compiling RuntimeR3NoCRTGCC -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/Runtime/common/string/strcmp_alias.c
kBuild: Compiling RuntimeR3NoCRTGCC -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/Runtime/common/string/strlen_alias.c
kmk[2]: *** No rule to make target `/usr/src/sys/kern/bus_if.m', needed by
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/RuntimeR0Drv/bus_if.h'.
 Stop.
kmk[2]: *** Waiting for unfinished jobs
kmk[2]: Leaving directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19673'
kmk[2]: Entering directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19673'
kmk[2]: *** Exiting with status 2
kmk[1]: *** [pass_libraries_this] Error 2
kmk[1]: Leaving directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19673'
kmk: *** [pass_libraries_order] Error 2
*** Error code 2

Stop in /usr/ports/emulators/virtualbox.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: fftw3

2009-05-15 Thread Sahil Tandon 
On Fri, 15 May 2009, ajtiM wrote:

> pkgdb -F
> --->  Checking the package registry database
> Stale dependency: akode-2.0.2,1 -> fftw3-3.1.3 (math/fftw3):
> Install stale dependency? ([y]es/[n]o/[a]ll) [yes] yes
> [Gathering depends for math/fftw3 .. done]
> --->  Installing 'gcc-4.3.4_20090503' from a port (lang/gcc43)
> --->  Building '/usr/ports/lang/gcc43'
> ===>  Cleaning for gcc-4.3.4_20090503
> Making GCC 4.3.4 for FreeBSD 7.2  target=i386-portbld-freebsd7.2
> You need to increase the datasize limit to at least 70 (and set
> kern.maxdsiz="734003200" in /boot/loader.conf) to build with Java
> support.

Did you try increasing the datasize limit?

> *** Error code 1
> 
> Stop in /usr/ports/lang/gcc43.

If you don't need Java:

% grep -C 1 WITHOUT_JAVA lang/gcc43/pkg-descr
(Building the Java frontend and the associated libgcj library will
consume more than 512MB of main memory.  Set WITHOUT_JAVA=yes in 
the environment when building this port to avoid that.)

-- 
Sahil Tandon 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: fftw3

2009-05-15 Thread ajtiM 
On Friday 15 May 2009 19:48:23 you wrote:
> % grep -C 1 WITHOUT_JAVA lang/gcc43/pkg-descr

 grep -C 1 WITHOUT_JAVA lang/gcc43/pkg-descr

grep: lang/gcc43/pkg-descr: No such file or directory

No, I didn't try to increase the datasize limit.

BTW I am about two years FreeBSD user and I never had problem like this. Why I 
need to change my settings if is update or why there were not warning in 
the /usr/port/UPDATE?
-- 
Mitja
-
http://starikarp.redbubble.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: ghostscript8 port not building

2009-05-15 Thread Josh Rickmar 

On Fri, 15 May 2009, Josh Rickmar wrote:



Well, I finally got frustrated with this problem and blew-away all of my
ports, to see if I had messed up something by accident.  I also removed
/var/db/ports/ghostscript8/options to make sure that that was not
affecting it.

Here is the my new error:

[...]

# uname -a
FreeBSD FGD135.localdomain 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Tue May
5 01:52:24 EDT 2009 jos...@fgd135.localdomain:/usr/obj/usr/src/sys/CUSTOM 
i386


I have also CC'd the maintainer since I forgot to do that in my first
email.




It seems that the second build problem I was having is fixed now.
Probably should have updated my ports tree before updating...

I don't get the first error anymore either, so everything seems to be
working fine.

--
IRC nick: jrick
Jabber: jr...@jabber.org
http://identi.ca/jrick

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: fftw3

2009-05-15 Thread Sahil Tandon 
On Fri, 15 May 2009, ajtiM wrote:

> On Friday 15 May 2009 19:48:23 you wrote:
> > % grep -C 1 WITHOUT_JAVA lang/gcc43/pkg-descr
> 
>  grep -C 1 WITHOUT_JAVA lang/gcc43/pkg-descr
> 
> grep: lang/gcc43/pkg-descr: No such file or directory

I thought it would be clear that one needs to be in /usr/ports for the above
grep to work.  The point is that you should read pkg-descr within the gcc43
port directory.

> No, I didn't try to increase the datasize limit.

If you want to compile gcc43 with Java (this is the default on i386 systems),
then you must.  Otherwise, as previously suggested, trying compiling without
Java.
 
-- 
Sahil Tandon 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

2009-05-15 Thread Sam Fourman Jr. 
> I've built it on i386/CURRENT r191522, but I couldn't load the
> module, when i try, i got:
>
> KLD vboxdrv.ko: depends on kernel - not available
> kldload: can't load vboxdrv: File exists
>
> It says file exists, but the module is not loaded
>
> r...@botelhor:/home/garga# kldstat
> Id Refs Address    Size     Name
>  1   18 0xc040 b584bc   kernel
>  2    1 0xc0f59000 809c     snd_via8233.ko
>  3    2 0xc0f62000 4a438    sound.ko
>  4    1 0xc46af000 8000     linprocfs.ko
>  5    1 0xc46c8000 24000    linux.ko
>
> Any idea?

it Probably means that you are running a kernel that is not in sync
with the src in your /usr/src

do csup -g -L 2 -h cvsup15.freebsd.org /usr/share
examples/cvsup/standard-supfile

then build your kernel && install your kernel

uninstall the Virtualbox port and rebuild it. all will work

Sam Fourman Jr.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"