SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I cannot believe it! No ATI proprietary binaries needed for me now. The opensource radeon drivers are now able to play Unreal Tournment 2004. If they could get me 10 more FPS or so it'd be great. I'd say I'm getting about 30 FPS less than if I play the game in Windows. Considering how *new* these drivers are and the constant flux of all the underlying stuff on a GNU system lately, I'm shocked, just ...shocked. Only caveat, and this is for nexuiz too, I get in 'dmesg' for any 3d game: freeing invalid memtype d0192000-d01a2000 over and over, but the numbers change. I've read that adding 'nopat' is the fix, but that just disables, hardly sounds like a fix, but like I said, I'm shocked these drivers work. Prior to the updates of 3/1 on --current, UT would just dead lock up the PC. Anyway nice job Slackware!
I cannot believe it! No ATI proprietary binaries needed for me now. The opensource radeon drivers are now able to play Unreal Tournment 2004. If they could get me 10 more FPS or so it'd be great. I'd say I'm getting about 30 FPS less than if I play the game in Windows. Considering how *new* these drivers are and the constant flux of all the underlying stuff on a GNU system lately, I'm shocked, just ...shocked. Only caveat, and this is for nexuiz too, I get in 'dmesg' for any 3d game: freeing invalid memtype d0192000-d01a2000 over and over, but the numbers change. I've read that adding 'nopat' is the fix, but that just disables, hardly sounds like a fix, but like I said, I'm shocked these drivers work. Prior to the updates of 3/1 on --current, UT would just dead lock up the PC. Anyway nice job Slackware!
You must have a newer card than I had. I had UT2004 working on the radeon (r200/dri) driver back in 2004. Granted it was slow, but not 10 FPS slow. Since that was a high end game back then, I had to set it to 800x600, and it was fully playable without any slow down.
I have now bought an RV740 now, and I can tell you that I am impressed with the driver progress these days too. I am on a newer driver than what is on current (2.13-rc).
@the3dfxdude . My video card is an ati radeon 9600xt / agp. . The box I'm testing on is an amd 2500+. . So far so good. Not one crash on it. I even played for about 45 minutes or so. .
@rworkman: One thing I did notice, and perhaps this may/might be needed in changes & hints, is I had to go into my bios and turn the AGP aperture down to 32 MB. That is obviously card dependant, but in Windows I'm supposed to use 64 MB . The guides on the internets recommend that to be 1/2 the ram on the video card. I also turned video-cache off in the bios too. .
edit(add) rob, the reason I did that was I was getting a horrible pause/freeze in audio of all things, in the game UT2004 and Nexuiz. A couple minutes on google advised me on them bios settings and voila. As to why video settings affected sound, I have _no_ idea.
If I only had about 15 FPS more, this would be heaven. I venture to guess the dev's will get that performance up in time. I can't wait to see how this turns out. .
The only thing that stinks about this card is when using xrandr, using the gtk-recordmydesktop I got that black bar on the far right monitor, but as someone pointed out to me in another thread, that's due to a limitation of the card itself. Tho, on my screen I actually can see everything fine. A game can play in that zone, and tvtime too will run as well.
Last edited by Old_Fogie; 03-08-2010 at 10:45 PM.
Reason: this site needs js running or borks return key, wth!
Please explain exactly what you mean by that, and also explain why you are the only person who's experienced this so-called breakage.
__________________
I pretty much know Slackware inside and out. I really think I caught the mirror with mistakes.
I like the fast mirror though.
I have one system that is only for slackware64 current. I keep this pristine with the http://slackware.mirrors.tds.net/pub...are64-current/
and one system pristine with no kde.
the one with no kde failed only with the kernel could not set up xorg. it failed to compile or compile the kernel . reinstall last mirror do a upgrade (with out) any of the new kernel all is ok.
The full install kde
the problem is. after doing the upgrade as usual
the system would not set up the xorg. It complained wrong module.ko .
so I tried building the module nvidia. no go complained not link to build or source but there was.
then the kernel would not compile. nothing would compile.
Ok bad up grade (found NO errors) no big deal. I have a mirror of the last up grade reinstall system do all the up grade same thing.
I notice this pkg kernel-headers not x86_64. thought weird.
the pkg is not there in (a) anymore. Strange clueless
so I thought may be with my multi systems the grub may be goofing it up.
so full install last mirror again use lilo.
upgrade same thing.
This time
now I m confused this time I am able to compile the kernel but that still did not help
the package I found theses pkgs broke my system
etc-13.013-x86_64-1.txz
kernel-huge-2.6.33-x86_64
kernel-modules-2.6.3.
coreutils-8.4-x86_64
aaa_elflibs-13.013-x
module-init-tools-3
sysvinit-scripts-1.2.
aaa_base-13.0-x86_64.
aaa_elflibs-13.013-x
no init for windowmanager set it up with pkgtool. no go.
build the module for nvidia for the last kernel 2.6.32.7
try to insmod complains wrong format .ko.
I did a full up grade with the kernel it failed to bring up the xorgserver.
so I did a up grade left out (a) (k) and all was well.
then I narrowed it down to the theses pkgs.
I believe we may have had a mirror problem. this Sunday.
the only thing I could do to make this happen out side of the mirror and slackware was to
install 32 bit pkgs
Do you think we have a mirror problem?.
I will try again when I find I have a spare 16 hours to play.
the last up grade trial was around 22:30 central time. I started working on this problem around 05:30 central time.
This is a pre-release for the upcoming 6.13 release of the X.org ati/radeon
driver.
Major highlights:
KMS/DRI2 support for all families r100->r700 for KMS driver in Linux 2.6.33.
Initial evergreen KMS support for planned 2.6.34 driver.
Userspace modesetting support for r600/r700 families
experimental userspace modesetting support for evergreen families
r600/r700 acceleration support.
Userspace modesetting basic power management controls
textured Xv controls (brightness, contrast, etc.)
Displayport support.
Improved Zaphod support - per-screen output assignment.
CustomEDID option - force the driver to use EDID from a file
and lots of quirks and fixes and optimisations.
This xorg problem has been around so long with nvida cards and now the new nauve what ever open nvida. we should be able to have people type xorgsetup and have it work. this has failed
all the way back slack13. this is a xorg problem.
Here is the thing we decided to go with kde we based Slackware 13 around it. I really do not want to spend so many hours a day telling people how to rebuild the kernel use nvida patches etc. or use the bata patch that will not build on are stock huge.s
Nvidia has been good to me through the years. But are nvidiafb driver has been broken a long time with slackware. You can disagree but I know. This is not KISS
we can fix it or push it around. Linus and his kernel it will work out.
But as long as we Base are system around kde we should keep all aspects functional.
all ati cards have come a long way. But nvidia has spent millions on linux. I know I talk to the guys down the street using there grant money to develop for use.
yes xfce4 is ok.
so be fore we see Slackware 14 I think together we can put this simple xorgconfig problem together.
I am not that smart Just a sub genius. I do know I have been silent along time about the new xorg and are xorgsetup scripts. witch xorg is supposed to do for us.
I have rolled up my sleeves and left the 64 bit puppy linux to tackle the KISS again.
your packages are not broken they just brake the old and make the new hard.
I know the pay is cheap. But look at all the girls and glitter LOL
. Thank you for you Hard work I do appreciate it and I am a big fan of you and Eric
But nvidia has spent millions on linux. I know I talk to the guys down the street using there grant money to develop for use.
What are the guys down the street working on?
nVidia may have spent millions on Linux (I'm not debating it, as I have no idea whether they did or not) but their proprietary 'nvidia' driver evidently isn't getting it's share of that development/money. It's one of the few closed-sourse video drivers left, and it STILL cannot do things that it should be able to, and which other companies open-source drivers are getting done. It's xrandr support doesn't work or is not implemented fully, and the ongoing Xinerama+composite issue continues to irk me (for one) and they blame *that* on the Xorg server (maybe it IS Xorg, I'm not enough of a programmer to be able to determine for myself). TwinView only works properly when the monitors are connected to the SAME card, otherwise clients can't be moved from one screen to the other, and WM data/events are not reported correctly for the second screen. For a proprietary driver, it leaves a lot to be desired, that IMHO would perhaps be fixed by now, had they opened the source..
I dunno.. I don't mean to rant (which I am doing), and am done ranting about nvidia -- I don't want to get this thread off topic, and that's where I'm taking it (since nothing I've written here has to do with the ATI driver, OR Slackware)..
Urbana Il Big Blue all open source. plus the nvidia future
Quote:
Grapefruit girl thank I you love your scripts
You are right you are right. But how many teams go out of there way to write drivers for
new kernels. and I think the new open Nvida will do great in the future.
I do not want to steal another man intellectual property if they want to open it to use fine.
TRUST ME OVER 100,000 YES 100,000 CORE nvidia opened up to be part of it, this is old news. around here.
So how do you control the daemons for this you open it up to GCC so people can write it.
sorry that it is owned still a slave to money.
Well the Linux kernel cluster and the open Nvidia had to happen for this and it happened 2 years ago.
It is in the kernel for a reason.
Quote:
GrapefruiTgirl again thank you for your wonderful work I use it every day. Big fan of yours
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.