"modprobe vboxdrv" returns "Invalid argument" (Vitrualbox 1.4.0 on 64-bit Linux)

[Brian Green]

Hi All

Just updated to 1.4.0 ("64-bit Linux ... [now] ... supported") on an
ASUS P5VD2-MX SE motherboard with Pentium Core 2 Duo, OpenSUSE 10.2 -
2.6.18.2-34-default (x86_64). I've run Virtualbox, successfully, on a
number of 32-bit PCs.

All ran smoothly (used zen-updater on unpacked .rpm) until I tried to
start an XP session.

And, /dev/vboxdrv does not exist

So, as su:

"
linux:/home/ein # /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module done
Recompiling VirtualBox kernel module done
Starting VirtualBox kernel module FATAL: Error inserting vboxdrv
(/lib/modules/2.6.18.2-34-default/misc/vboxdrv.ko): Invalid argument
failed (modprobe vboxdrv failed)
linux:/home/ein # modprobe vboxdrv
FATAL: Error inserting vboxdrv
(/lib/modules/2.6.18.2-34-default/misc/vboxdrv.ko): Invalid argument
"
Group, and User checkout OK.

Googling didn't help ... so, any advice?

Brian

[Larry Finger]

Post by Brian Green
Hi All
Just updated to 1.4.0 ("64-bit Linux ... [now] ... supported") on an
ASUS P5VD2-MX SE motherboard with Pentium Core 2 Duo, OpenSUSE 10.2 -
2.6.18.2-34-default (x86_64). I've run Virtualbox, successfully, on a
number of 32-bit PCs.
All ran smoothly (used zen-updater on unpacked .rpm) until I tried to
start an XP session.
And, /dev/vboxdrv does not exist
"
linux:/home/ein # /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module done
Recompiling VirtualBox kernel module done
Starting VirtualBox kernel module FATAL: Error inserting vboxdrv
(/lib/modules/2.6.18.2-34-default/misc/vboxdrv.ko): Invalid argument
failed (modprobe vboxdrv failed)
linux:/home/ein # modprobe vboxdrv
FATAL: Error inserting vboxdrv
(/lib/modules/2.6.18.2-34-default/misc/vboxdrv.ko): Invalid argument
"

Does dmesg show any additional information regarding the error? I have not downloaded 1.4.0, but
have built it from the svn repository on an AMD 64 X2 system with an x86_64 version of openSUSE
10.2. My current kernel is 2.6.22-rc4.

Larry

[Brian Green]

Post by Larry Finger

Post by Brian Green
Hi All
Just updated to 1.4.0 ("64-bit Linux ... [now] ... supported") on an
ASUS P5VD2-MX SE motherboard with Pentium Core 2 Duo, OpenSUSE 10.2 -
2.6.18.2-34-default (x86_64). I've run Virtualbox, successfully, on a
number of 32-bit PCs.
All ran smoothly (used zen-updater on unpacked .rpm) until I tried to
start an XP session.
And, /dev/vboxdrv does not exist
"
linux:/home/ein # /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module done
Recompiling VirtualBox kernel module done
Starting VirtualBox kernel module FATAL: Error inserting vboxdrv
(/lib/modules/2.6.18.2-34-default/misc/vboxdrv.ko): Invalid argument
failed (modprobe vboxdrv failed)
linux:/home/ein # modprobe vboxdrv
FATAL: Error inserting vboxdrv
(/lib/modules/2.6.18.2-34-default/misc/vboxdrv.ko): Invalid argument
"

Does dmesg show any additional information regarding the error? I have not downloaded 1.4.0, but
have built it from the svn repository on an AMD 64 X2 system with an x86_64 version of openSUSE
10.2. My current kernel is 2.6.22-rc4.
Larry

Hi Larry

dmesg is constantly referring to the "NMI watchdog active" (full details
below).

A quick Google indicates line 374 of:

http://www.virtualbox.org/browser/trunk/src/VBox/HostDrivers/Support/linux/SUPDrv-linux.c

Cheers

Brian

"
vboxdrv: NMI watchdog active -- refused to load the kernel module!
Please disabl e
vboxdrv: the NMI watchdog by specifying 'nmi_watchdog=0' at kernel
command line.
vboxdrv: NMI watchdog active -- refused to load the kernel module!
Please disabl e
vboxdrv: the NMI watchdog by specifying 'nmi_watchdog=0' at kernel
command line.
SFW2-OUT-ERROR IN= OUT=eth0 SRC=10.0.0.10 DST=66.54.44.230 LEN=40
TOS=0x00 PREC= 0x00 TTL=64 ID=6522 DF PROTO=TCP
SPT=24707 DPT=80 WINDOW=63248 RES=0x00 ACK FIN
URGP=0
SFW2-OUT-ERROR IN= OUT=eth0 SRC=10.0.0.10 DST=146.101.167.41 LEN=52
TOS=0x00 PRE C=0x00 TTL=64 ID=45597 DF PROTO=TCP
SPT=15609 DPT=80 WINDOW=311 RES=0x00 ACK FIN
URGP=0 OPT (0101080A0001524F0CF98657)
vboxdrv: NMI watchdog active -- refused to load the kernel module!
Please disabl e
vboxdrv: the NMI watchdog by specifying 'nmi_watchdog=0' at kernel
command line.
SFW2-OUT-ERROR IN= OUT=eth0 SRC=10.0.0.10 DST=208.97.132.77 LEN=58
TOS=0x00 PREC =0x00 TTL=64 ID=5422 DF PROTO=TCP
SPT=17069 DPT=143 WINDOW=288 RES=0x00 ACK PSH
FIN URGP=0 OPT (0101080A000D78031979F723)
SFW2-OUT-ERROR IN= OUT=eth0 SRC=10.0.0.10 DST=12.120.1.254 LEN=40
TOS=0x00 PREC= 0x00 TTL=64 ID=11802 DF PROTO=TCP
SPT=10167 DPT=80 WINDOW=160 RES=0x00 ACK FIN U RGP=0
"

[David Baron]

Post by Brian Green

Post by Larry Finger

Post by Brian Green
Hi All
Just updated to 1.4.0 ("64-bit Linux ... [now] ... supported") on an
ASUS P5VD2-MX SE motherboard with Pentium Core 2 Duo, OpenSUSE 10.2 -
2.6.18.2-34-default (x86_64). I've run Virtualbox, successfully, on a
number of 32-bit PCs.
All ran smoothly (used zen-updater on unpacked .rpm) until I tried to
start an XP session.
And, /dev/vboxdrv does not exist
"
linux:/home/ein # /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module
done Recompiling VirtualBox kernel module
done Starting VirtualBox kernel module FATAL: Error inserting vboxdrv
(/lib/modules/2.6.18.2-34-default/misc/vboxdrv.ko): Invalid argument
failed (modprobe vboxdrv failed)
linux:/home/ein # modprobe vboxdrv
FATAL: Error inserting vboxdrv
(/lib/modules/2.6.18.2-34-default/misc/vboxdrv.ko): Invalid argument
"

Does dmesg show any additional information regarding the error? I have
not downloaded 1.4.0, but have built it from the svn repository on an AMD
64 X2 system with an x86_64 version of openSUSE 10.2. My current kernel
is 2.6.22-rc4.
Larry

Hi Larry
dmesg is constantly referring to the "NMI watchdog active" (full details
below).
http://www.virtualbox.org/browser/trunk/src/VBox/HostDrivers/Support/linux/
SUPDrv-linux.c
Cheers
Brian
"
vboxdrv: NMI watchdog active -- refused to load the kernel module!
Please disabl e
vboxdrv: the NMI watchdog by specifying 'nmi_watchdog=0' at kernel
command line.
vboxdrv: NMI watchdog active -- refused to load the kernel module!
Please disabl e
vboxdrv: the NMI watchdog by specifying 'nmi_watchdog=0' at kernel
command line.
SFW2-OUT-ERROR IN= OUT=eth0 SRC=10.0.0.10 DST=66.54.44.230 LEN=40
TOS=0x00 PREC= 0x00 TTL=64 ID=6522 DF PROTO=TCP
SPT=24707 DPT=80 WINDOW=63248 RES=0x00 ACK FIN
URGP=0
SFW2-OUT-ERROR IN= OUT=eth0 SRC=10.0.0.10 DST=146.101.167.41 LEN=52
TOS=0x00 PRE C=0x00 TTL=64 ID=45597 DF PROTO=TCP
SPT=15609 DPT=80 WINDOW=311 RES=0x00 ACK FIN
URGP=0 OPT (0101080A0001524F0CF98657)
vboxdrv: NMI watchdog active -- refused to load the kernel module!
Please disabl e
vboxdrv: the NMI watchdog by specifying 'nmi_watchdog=0' at kernel
command line.
SFW2-OUT-ERROR IN= OUT=eth0 SRC=10.0.0.10 DST=208.97.132.77 LEN=58
TOS=0x00 PREC =0x00 TTL=64 ID=5422 DF PROTO=TCP
SPT=17069 DPT=143 WINDOW=288 RES=0x00 ACK PSH
FIN URGP=0 OPT (0101080A000D78031979F723)
SFW2-OUT-ERROR IN= OUT=eth0 SRC=10.0.0.10 DST=12.120.1.254 LEN=40
TOS=0x00 PREC= 0x00 TTL=64 ID=11802 DF PROTO=TCP
SPT=10167 DPT=80 WINDOW=160 RES=0x00 ACK FIN U RGP=0
"

Use the init.d script. It first disables NMI. I would suppose that if NMI is
active, modprobe alone would fail.

[Frank Mehnert]

Post by David Baron
Use the init.d script. It first disables NMI. I would suppose that if NMI
is active, modprobe alone would fail.

No, it does not. Please add the kernel parameter 'nmi_watchdog=0' (at the
kernel command line when booting the kernel. We will try to disable the
watchdog in from within the module in the next release.

Kind regards,

Frank

[David Baron]

Post by Frank Mehnert

Post by David Baron
Use the init.d script. It first disables NMI. I would suppose that if NMI
is active, modprobe alone would fail.

No, it does not. Please add the kernel parameter 'nmi_watchdog=0' (at the
kernel command line when booting the kernel. We will try to disable the
watchdog in from within the module in the next release.

I get the message,
"Trying to permamently stop nmi watchdog ...."
"successful"
From the init script.

Putting it in the commandline is a good idea. How do I get there from a simple
menu in lilo? options: nmi_watchdog=0 ?

[Brian Green]

Post by David Baron

Post by Frank Mehnert

Post by David Baron
Use the init.d script. It first disables NMI. I would suppose that if NMI
is active, modprobe alone would fail.

No, it does not. Please add the kernel parameter 'nmi_watchdog=0' (at the
kernel command line when booting the kernel. We will try to disable the
watchdog in from within the module in the next release.

I get the message,
"Trying to permamently stop nmi watchdog ...."
"successful"
From the init script.
Putting it in the commandline is a good idea. How do I get there from a simple
menu in lilo? options: nmi_watchdog=0 ?

Yeah - I can confirm that "/etc/init.d/vboxdrv start" {etc} fails.

Similarly, how do I insert the "nmi_watchdog=0" in the command line - I
use grub.

[Michael Thayer]

Post by Brian Green
Yeah - I can confirm that "/etc/init.d/vboxdrv start" {etc} fails.
Similarly, how do I insert the "nmi_watchdog=0" in the command line - I
use grub.

To do it once, use "e" for edit at the Grub boot menu. To always do it,
edit /boot/grub/menu.lst or /boot/grub/grub.conf (or whatever it is
called).

Regards,

Michael

[David Baron]

Post by Brian Green

Post by David Baron

Post by Frank Mehnert

Post by David Baron
Use the init.d script. It first disables NMI. I would suppose that if
NMI is active, modprobe alone would fail.

No, it does not. Please add the kernel parameter 'nmi_watchdog=0' (at
the kernel command line when booting the kernel. We will try to disable
the watchdog in from within the module in the next release.

I get the message,
"Trying to permamently stop nmi watchdog ...."
"successful"
From the init script.
Putting it in the commandline is a good idea. How do I get there from a
simple menu in lilo? options: nmi_watchdog=0 ?

Yeah - I can confirm that "/etc/init.d/vboxdrv start" {etc} fails.

Mine works

Post by Brian Green
Similarly, how do I insert the "nmi_watchdog=0" in the command line - I
use grub.

For lilo, I am trying append="nmi_watchdog=0"

[Brian Green]

Post by David Baron

Post by Brian Green

Post by David Baron

Post by Frank Mehnert

Post by David Baron
Use the init.d script. It first disables NMI. I would suppose that if
NMI is active, modprobe alone would fail.

No, it does not. Please add the kernel parameter 'nmi_watchdog=0' (at
the kernel command line when booting the kernel. We will try to disable
the watchdog in from within the module in the next release.

I get the message,
"Trying to permamently stop nmi watchdog ...."
"successful"
From the init script.
Putting it in the commandline is a good idea. How do I get there from a
simple menu in lilo? options: nmi_watchdog=0 ?

Yeah - I can confirm that "/etc/init.d/vboxdrv start" {etc} fails.

Mine works

Post by Brian Green
Similarly, how do I insert the "nmi_watchdog=0" in the command line - I
use grub.

For lilo, I am trying append="nmi_watchdog=0"

OK. Entered "nmi_watchdog=0" into grub (using YaST).

Apart from (now) getting the old "Could not load the Host USB Proxy
Service" message, starting a session now gives:

"
Unknown error initializing kernel driver (VERR_VM_DRIVER_VERSION_MISMATCH).
VBox status code: -1912 (VERR_VM_DRIVER_VERSION_MISMATCH).

Result Code:
0x80004005
Component:
Console
Interface:
IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}
"

Brian

[Brian Green]

Post by Brian Green

Post by Frank Mehnert

Post by David Baron
Use the init.d script. It first disables NMI. I would suppose that if
NMI is active, modprobe alone would fail.

No, it does not. Please add the kernel parameter 'nmi_watchdog=0' (at
the kernel command line when booting the kernel. We will try to disable
the watchdog in from within the module in the next release.

OK. Entered "nmi_watchdog=0" into grub (using YaST).
Apart from (now) getting the old "Could not load the Host USB Proxy
"
Unknown error initializing kernel driver (VERR_VM_DRIVER_VERSION_MISMATCH).
VBox status code: -1912 (VERR_VM_DRIVER_VERSION_MISMATCH).
0x80004005
Console
IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}
"
Brian

D'oh! dmesg gives:

"
ioctl32(VirtualBox:5175): Unknown cmd fd(3) cmd(c0102201){00}
arg(fff4d408) on / dev/vboxdrv
ioctl32(VirtualBox:5391): Unknown cmd fd(3) cmd(c0102201){00}
arg(ffeddb08) on / dev/vboxdrv
ioctl32(VirtualBox:5406): Unknown cmd fd(29) cmd(c0102201){00}
arg(f40d8058) on /dev/vboxdrv
"

Brian

[Frank Mehnert]

Post by Brian Green
"
ioctl32(VirtualBox:5175): Unknown cmd fd(3) cmd(c0102201){00}
arg(fff4d408) on / dev/vboxdrv
ioctl32(VirtualBox:5391): Unknown cmd fd(3) cmd(c0102201){00}
arg(ffeddb08) on / dev/vboxdrv
ioctl32(VirtualBox:5406): Unknown cmd fd(29) cmd(c0102201){00}
arg(f40d8058) on /dev/vboxdrv
"

Which package did you install on your suse64 system? Seems that you
either installed the i386 package (not sure if this is possible)
or you compiled the vboxdrv module against the wrong Linux kernel
sources.

Kind regards,

Frank

[Brian Green]

Post by Frank Mehnert

Post by Brian Green
"
ioctl32(VirtualBox:5175): Unknown cmd fd(3) cmd(c0102201){00}
arg(fff4d408) on / dev/vboxdrv
ioctl32(VirtualBox:5391): Unknown cmd fd(3) cmd(c0102201){00}
arg(ffeddb08) on / dev/vboxdrv
ioctl32(VirtualBox:5406): Unknown cmd fd(29) cmd(c0102201){00}
arg(f40d8058) on /dev/vboxdrv
"

Which package did you install on your suse64 system? Seems that you
either installed the i386 package (not sure if this is possible)
or you compiled the vboxdrv module against the wrong Linux kernel
sources.
Kind regards,
Frank

Hi Frank

OS: Linux 2.6.18.2-34-default x86_64
System: openSUSE 10.2 (X86-64)

And,

kernel-default version: 2.6.18.2-34
kernel-source version: 2.6.18.2-34
VirtualBox version: 1.4.0_21864_openSUSE102-1

Used ZenInstaller to compile VirtualBox-1.4.0_21864_openSUSE102-1.i586.rpm

??

Cheers

Brian

[Frank Mehnert]

Post by Brian Green

Post by Frank Mehnert

Post by Brian Green
"
ioctl32(VirtualBox:5175): Unknown cmd fd(3) cmd(c0102201){00}
arg(fff4d408) on / dev/vboxdrv
ioctl32(VirtualBox:5391): Unknown cmd fd(3) cmd(c0102201){00}
arg(ffeddb08) on / dev/vboxdrv
ioctl32(VirtualBox:5406): Unknown cmd fd(29) cmd(c0102201){00}
arg(f40d8058) on /dev/vboxdrv
"

Which package did you install on your suse64 system? Seems that you
either installed the i386 package (not sure if this is possible)
or you compiled the vboxdrv module against the wrong Linux kernel
sources.
Kind regards,
Frank

Hi Frank
OS: Linux 2.6.18.2-34-default x86_64
System: openSUSE 10.2 (X86-64)
And,
kernel-default version: 2.6.18.2-34
kernel-source version: 2.6.18.2-34
VirtualBox version: 1.4.0_21864_openSUSE102-1
Used ZenInstaller to compile VirtualBox-1.4.0_21864_openSUSE102-1.i586.rpm

Why don't you use the x86_64 package for openSUSE from our webpage? The
i586 package will _not_ work on x86_64 systems.

Kind regards,

Frank

[Brian Green]

Post by Frank Mehnert
Why don't you use the x86_64 package for openSUSE from our webpage? The
i586 package will _not_ work on x86_64 systems.
Kind regards,
Frank

Hi Frank

OK, I misread the AMDS64 label and thought it only related to an AMD chip.

x86_64 now installed (after a minor hiccup with "...
libxerces-c.so.27()(64bit), but has another architecture" that was
finally resolved with the application of YaST) with an XP guest on
openSUSE 10.2 - currently updating itself. Thank you for your patiences
and support.

As I need XP guest, with some urgency, I have not had a chance to drill
down on a problem I had when I installed Guest Additions (I appear to
irrecoverably lose internet access ...). When I have a chance I'll
install a linux guest and revisit installing Guest Additions ...

Regards

Brian

[David Baron]

Post by Brian Green

Post by David Baron

Post by Brian Green

Post by David Baron

Post by Frank Mehnert

Post by David Baron
Use the init.d script. It first disables NMI. I would suppose that if
NMI is active, modprobe alone would fail.

No, it does not. Please add the kernel parameter 'nmi_watchdog=0' (at
the kernel command line when booting the kernel. We will try to
disable the watchdog in from within the module in the next release.

I get the message,
"Trying to permamently stop nmi watchdog ...."
"successful"
From the init script.
Putting it in the commandline is a good idea. How do I get there from a
simple menu in lilo? options: nmi_watchdog=0 ?

Yeah - I can confirm that "/etc/init.d/vboxdrv start" {etc} fails.

Mine works

Post by Brian Green
Similarly, how do I insert the "nmi_watchdog=0" in the command line - I
use grub.

For lilo, I am trying append="nmi_watchdog=0"

Did it.
Still get the "stopping nmi_watchdog permantently message ... success"
So maybe the command needs be a bit different?

Anyway, mine works in any event.

Post by Brian Green
OK. Entered "nmi_watchdog=0" into grub (using YaST).
Apart from (now) getting the old "Could not load the Host USB Proxy
"
Unknown error initializing kernel driver (VERR_VM_DRIVER_VERSION_MISMATCH).
VBox status code: -1912 (VERR_VM_DRIVER_VERSION_MISMATCH).
0x80004005
Console
IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}
"
Brian
_______________________________________________
vbox-users mailing list
http://vbox.innotek.de/mailman/listinfo/vbox-users

[Frank Mehnert]

Post by David Baron

Post by David Baron

Post by Brian Green

Post by David Baron

Post by Frank Mehnert

Post by David Baron
Use the init.d script. It first disables NMI. I would suppose that
if NMI is active, modprobe alone would fail.

No, it does not. Please add the kernel parameter 'nmi_watchdog=0'
(at the kernel command line when booting the kernel. We will try to
disable the watchdog in from within the module in the next release.

I get the message,
"Trying to permamently stop nmi watchdog ...."
"successful"
From the init script.
Putting it in the commandline is a good idea. How do I get there from
a simple menu in lilo? options: nmi_watchdog=0 ?

Yeah - I can confirm that "/etc/init.d/vboxdrv start" {etc} fails.

Mine works

Post by Brian Green
Similarly, how do I insert the "nmi_watchdog=0" in the command line -
I use grub.

For lilo, I am trying append="nmi_watchdog=0"

Did it.
Still get the "stopping nmi_watchdog permantently message ... success"
So maybe the command needs be a bit different?
Anyway, mine works in any event.

This message is ok. 'nmi_watchodog=0' means that the watchdog is not enabled
during boot. Then the vboxdrv module tries to disable it permanently. This
is not possible if the watchdog was enabled once during boot. So if your
module loads without an error everything should be fine for you.

Kind regards,

Frank

[David Baron]

Post by Frank Mehnert

Post by David Baron

Post by David Baron

Post by Brian Green

Post by David Baron

Post by Frank Mehnert

Post by David Baron
Use the init.d script. It first disables NMI. I would suppose
that if NMI is active, modprobe alone would fail.

No, it does not. Please add the kernel parameter 'nmi_watchdog=0'
(at the kernel command line when booting the kernel. We will try
to disable the watchdog in from within the module in the next
release.

I get the message,
"Trying to permamently stop nmi watchdog ...."
"successful"
From the init script.
Putting it in the commandline is a good idea. How do I get there
from a simple menu in lilo? options: nmi_watchdog=0 ?

Yeah - I can confirm that "/etc/init.d/vboxdrv start" {etc} fails.

Mine works

Post by Brian Green
Similarly, how do I insert the "nmi_watchdog=0" in the command line
- I use grub.

For lilo, I am trying append="nmi_watchdog=0"

Did it.
Still get the "stopping nmi_watchdog permantently message ... success"
So maybe the command needs be a bit different?
Anyway, mine works in any event.

This message is ok. 'nmi_watchodog=0' means that the watchdog is not
enabled during boot. Then the vboxdrv module tries to disable it
permanently. This is not possible if the watchdog was enabled once during
boot. So if your module loads without an error everything should be fine
for you.

Cool. I have three kernels around:
A 2.6.21 and two version of 2.6.21 with real time premption patches.
The plain 2.6.21 .config has no entry for NMI (I unchecked that for the above
reason, I suppose :-) )
The -rt versions have NMI instrumentation support =y.

The vboxdrv startup is the same in all of them.

But as we have seen, this is not the "invalid argument" poster's problem.

[Frank Mehnert]

Post by Frank Mehnert
This message is ok. 'nmi_watchodog=0' means that the watchdog is not
enabled during boot. Then the vboxdrv module tries to disable it
permanently. This is not possible if the watchdog was enabled once during
boot. So if your module loads without an error everything should be fine
for you.

The public svn repository contains an updated version of the vboxdrv module.
This module can be used together with VirtualBox 1.4.0 by executing

src/VBox/HostDrivers/Support/linux/export_module ~/vboxdrv.tar.gz

Extract the module sources from the generated vboxdrv.tar.gz and compile it
with

vboxdrv/build_in_tmp install

(This assumes that /lib/modules/`uname -r`/build exsits and points to the
right kernel source directory).

The module contains some code to disable an enabled NMI watchdog on x86_64
systems. Feedback is welcome.

Kind regards,

Frank

[Larry Finger]

Now that the x86_64 version is supported, I would like to have one of the users run a test for me.

From the VirtualBox main window, click on the CD/DVD-ROM entry. In the Settings box that pops up,
select the "Mount CD/DVD Drive" check box and click on the "ISO Image File" radio button. Next click
on the browser icon at the far right-hand side. The Virtual Disk Manager window should pop up. Next
click the Add button at the top. In the file browser that pops up, please report the contents of the
Filter box. The code says it should be "*.iso", but I get "All Supported Files". It works OK in
1.3.8 on a Windows XP box.

I filed a bug report that has been marked "Fixed in 1.4.0", but I get the old behavior in both the
RPM version, and a copy built from the svn sources.

Thanks,

Larry

[Johann Spies]

now that the x86_64 version is supported,

Good news for me!

I would like to have one of the users run a test for me.

But, when I try it on Debian, I get a "Floating point exception".

Regards
Johann

[Johann Spies]

Post by Johann Spies

now that the x86_64 version is supported,

Good news for me!

I would like to have one of the users run a test for me.

But, when I try it on Debian, I get a "Floating point exception".

Sorry, I solved it. There was more than one version of gcc on my
system and my fglrx-driver was compiled with the wrong one.

Regards
Johann