I can get it to run under Linux with no problems. I also have/had it working under BeOS and Windows. At one point, it ran under OpenBSD. As of 2.7, though, OpenBSD sees it as two devices at two separate IRQs, and neither device works. My attempt at FreeBSD resulted in similar problems.
Someone who judges another as a worthless piece of shit is a worthless piece of shit:-)
But the original poster criticized linux for not having decent hardware support in another thread and (inaccurately) gave DVD as an example. Does IBM play DVDs in their "Big Iron"?
BTW, FreeBSD sees the card twice, at two different IRQs (as does OpenBSD 2.7). Linux, Windows, and BeOS all work beautifully with the card, so it's not a hardware issue.
I have no doubt... I even ran FreeBSD and OpenBSD with this card for a while. Recently, though, both OSes started having a problem with the card. Linux, Windows, and BeOS are having no problem with it, though.
"As for the NVidia drivers, aren't you in the least bit intrigued that I found out how they optimized the performance without looking through the DRI to ruin the surprise?"
Not sure I follow you...
I have no doubt that nVidia is constantly optimizing their drivers. However, as a consumer in the video card market, I like to know how the drivers are being optimized. I like to be able to look at the source and determine what they're doing to get their speed gains. I like to be sure that if the company decides to abandon linux support, the source code is still available for anyone to download and start working on. I like that if something goes wrong (as happened with a TNT2 of mine under linux) I have immediate access to a bug monitoring system, and a mailing list full of developers.
That is what I consider to be good linux support. Not this close sourced junk that nVidia is putting out.
"...more like pathetic. The drivers for my Voodoo 2 were awful."
You seem to have this tendency to use your experience with three year old technology and drivers as the basis for your assertations.
My Voodoo 5500 consistently gives me over 80 fps under linux, and that is with only one processor in use. The other processor will be coming along shortly.
"One big reason for NVidia's great performance is how they're constantly optimizing the drivers. "
And if you did any research into the DRI, you would see constant messages on their mailing list discussing the work they're doing. In fact, One of the development cvs branches is showing a doubling of speed with GL apps.
"I think you both need to build a bridge and get over it. For all either of you know, ReiserFS and dosfs (or whatever it's called) had an interaction with a third piece of software (a driver, possibly) which took exception to some string in some PROM for a hard disk or similar. "
Thank you. This just goes to show that till these quirks are worked out, reiserfs is not ready for the primetime.
Dude!! It didn't work on my system when the *only* change was the inclusion of reiserfs, giveing a very good indication that the problem was with reiserfs... Claiming otherwise is FUD.
Just because it works for your roommate with one setup does *not* mean it will work for every other setup. It's quite possible he's running an older version, a newer version, or a different test kernel.
It's quite obvious that reiserfs is not ready for inclusion the kernel code.
Wrong... I had been running the test kernel with no problems, and had compiled in dos support. When I recompiled the only thing I changed during make xconfig was reiserfs support. All the other filesystems remained checked.
The module was there. (And the kernel doesn't ooops when trying to load a module that doesn't exist).
Reiserfs does not interact well with VFS. This is a known fact and this is why it won't be included in the kernel source till it's fixed.
No, I didn't... I had been running one of the test kernels with no problem... I downloaded the reiserfs patch and patched the kernel with no problems. I compiled the kernel, modules, and reiserfs utils with no problems.
I rebooted. No problem... I tried to mount a dos partition and it Ooopsed. I reverted to the old kernel and had no problems.
"Bottom line: ReiserFS gets two thumbs up. Highly recommended if you're not afraid of patching your kernel. "
And you don't mind screwing up your support for other filesystems... After I compiled in support for reiserfs (not that long ago, with one of the 2.4.0-test* kernels), I couldn't mount dos partitions anymore... Yea, that sounds really reliable to me.
And when I patched my kernel to support reiserfs recently, I started getting an Ooops every time I tried to mount a dos filesystem... One filesystem should *not* destroy support for another.
Considering that for a long while their original license said nothing about reverse engineering, or using the CueCat for other purposes, you seem to be way off base.
Slashdot Mirror
"They are not benefitting from society."
So without society, they'd still be as rich?
Ranessin
I can get it to run under Linux with no problems. I also have/had it working under BeOS and Windows. At one point, it ran under OpenBSD. As of 2.7, though, OpenBSD sees it as two devices at two separate IRQs, and neither device works. My attempt at FreeBSD resulted in similar problems.
Someone who judges another as a worthless piece of shit is a worthless piece of shit
Ranessin
But the original poster criticized linux for not having decent hardware support in another thread and (inaccurately) gave DVD as an example. Does IBM play DVDs in their "Big Iron"?
BTW, FreeBSD sees the card twice, at two different IRQs (as does OpenBSD 2.7). Linux, Windows, and BeOS all work beautifully with the card, so it's not a hardware issue.
Ranessin
I have no doubt... I even ran FreeBSD and OpenBSD with this card for a while. Recently, though, both OSes started having a problem with the card. Linux, Windows, and BeOS are having no problem with it, though.
Ranessin
"Why not run BSD?"
Because none of them could use my NE2000?
Ranessin
"Please explain how for the benefit of all the others that have been trying to do the same thing."
http://www.linuxvideo.org/oms/
Ranessin
DVD? Just watched The Matrix last night on my linux box at home
Hardware RAID? Have it on a linux server at work.
GPL? At least Big Iron can be sure that any code they might change/add can't be used in a closed source project by another company.
Ranessin
When discussing filesystem performance, I think discussion of any modern filesystem, and the features is contains, is worthy.
"Unfair" to the idiot(s) that moderated your parent post as "Offtopic"
Ranessin
"As for the NVidia drivers, aren't you in the least bit intrigued that I found out how they optimized the performance without looking through the DRI to ruin the surprise?"
Not sure I follow you...
I have no doubt that nVidia is constantly optimizing their drivers. However, as a consumer in the video card market, I like to know how the drivers are being optimized. I like to be able to look at the source and determine what they're doing to get their speed gains. I like to be sure that if the company decides to abandon linux support, the source code is still available for anyone to download and start working on. I like that if something goes wrong (as happened with a TNT2 of mine under linux) I have immediate access to a bug monitoring system, and a mailing list full of developers.
That is what I consider to be good linux support. Not this close sourced junk that nVidia is putting out.
Ranessin
"My Voodoo 5500 consistently gives me over 80 fps under linux..."
in Q3A...
I'm now getting b/w 35-50 fps in UT, depending on the level.
Ranessin
"...more like pathetic. The drivers for my Voodoo 2 were awful."
You seem to have this tendency to use your experience with three year old technology and drivers as the basis for your assertations.
My Voodoo 5500 consistently gives me over 80 fps under linux, and that is with only one processor in use. The other processor will be coming along shortly.
"One big reason for NVidia's great performance is how they're constantly optimizing the drivers. "
And if you did any research into the DRI, you would see constant messages on their mailing list discussing the work they're doing. In fact, One of the development cvs branches is showing a doubling of speed with GL apps.
Ranessin
"I think you both need to build a bridge and get over it. For all either of you know, ReiserFS and dosfs (or whatever it's called) had an interaction with a third piece of software (a driver, possibly) which took exception to some string in some PROM for a hard disk or similar. "
Thank you. This just goes to show that till these quirks are worked out, reiserfs is not ready for the primetime.
Ranessin
Dude!! It didn't work on my system when the *only* change was the inclusion of reiserfs, giveing a very good indication that the problem was with reiserfs... Claiming otherwise is FUD.
Just because it works for your roommate with one setup does *not* mean it will work for every other setup. It's quite possible he's running an older version, a newer version, or a different test kernel.
It's quite obvious that reiserfs is not ready for inclusion the kernel code.
Ranessin
Fine, but they've demonstrated that they aren't ready for 2.4.
Ranessin
Wrong... I had been running the test kernel with no problems, and had compiled in dos support. When I recompiled the only thing I changed during make xconfig was reiserfs support. All the other filesystems remained checked.
The module was there. (And the kernel doesn't ooops when trying to load a module that doesn't exist).
Reiserfs does not interact well with VFS. This is a known fact and this is why it won't be included in the kernel source till it's fixed.
Ranessin
I'm not a moron. The kernel module was present and I was getting an Ooops...
Reiserfs does not interact well with the VFS, hence it has not been added to the kernel source.
Ranessin
No, I didn't... I had been running one of the test kernels with no problem... I downloaded the reiserfs patch and patched the kernel with no problems. I compiled the kernel, modules, and reiserfs utils with no problems.
I rebooted. No problem... I tried to mount a dos partition and it Ooopsed. I reverted to the old kernel and had no problems.
I didn't screw up.
Ranessin
I didn't screw up... It's not that hard to install... Download the patch, patch the kernel, compile... Voila.
And it still ooopsed when mounting dos filesystems.
Ranessin
"Bottom line: ReiserFS gets two thumbs up. Highly recommended if you're not afraid of patching your kernel. "
And you don't mind screwing up your support for other filesystems... After I compiled in support for reiserfs (not that long ago, with one of the 2.4.0-test* kernels), I couldn't mount dos partitions anymore... Yea, that sounds really reliable to me.
Ranessin
And when I patched my kernel to support reiserfs recently, I started getting an Ooops every time I tried to mount a dos filesystem... One filesystem should *not* destroy support for another.
Ranessin
What makes you think it was designed for a woman?
Ranessin
Considering that for a long while their original license said nothing about reverse engineering, or using the CueCat for other purposes, you seem to be way off base.
Ranessin
Posting as an anonymous coward, eh? Weak...
Ranessin
I never got a license forbidding the use of the CueCat for other purposes.
Ranessin
Wrong... We just have to show that it was obvious back when the patent was filed.
Ranessin