WARNING: if you have problem with nvidia or ati binary drivers

[namehbar]

if you have problem with your graphic card
please refer to this page
https://www.redhat.com/archives/fedora-test-list/2006-February/msg01565.html

Permanent Fedora Project page (copy of original mailing-list post above): https://fedoraproject.org/wiki/Xorg/3rd_Party_Video_Drivers

SUMMARY: 3rd-party video driver binary installer "blobs" over-write critical system graphics library(ies), and may, in some cases (depending on your usage, software selection, and/or any subsequent hardware changes) result in failure of X11 (the GUI). It is strongly recommended that you use the equivalent video driver RPMs (which are based on, and include the exact same video drivers, but are custom-built to integrate with maximum compatibility with your Fedora OS) provided by known and competent Repos (e.g.: RPMFusion). Please refer to the above link(s) for details. Please refer to one of the Guides and Solutions (http://forums.fedoraforum.org/forumdisplay.php?f=12) tutorials to install 3rd-party video driver RPMs.

[bob]

Moved to Hardware and made 'sticky'. Thank you for finding and posting this important explanation. Hopefully members will discover it before they have problems.

[Frost_Aus]

When I boot my FC5 server, most times out of 10 the server dosnt load into KNOME but the server is still running because I can ssh into it, does anyone know what the issue might be

Cheers

[steve941]

thanks btw, i upgraded to kernel.org 2.6.18 today, i got rid fglrx from ati, i successfully configured my kernel so drm[i] loads and i noticed that 3d support is lacking .. like slow FPS on 3D game and unresponsiveness but i ill give a try to reinstalling libgl / Xorg. or most likely ill be lazy and wait till FC6. with less than a month, i can wait. plus 3d support wouldnt help now as i have sound issue .. well nice for posting that

[Pietri85]

thanks for this posting! Next week fedora 6 comes out, I will download and install it with the knowledge of your posting => no drivers from www.ati.com, thanks, I hope this works.

greetings, Pietri85

[Gortok]

Gents (and Ladies!),

I am reviewing Cedega for an article, and I ran into this issue when I tried to Update ATi's drivers in preparation for installing Cedega. Now, FC6 sees my Video Hardware as a Mesa... instead of an ATI Radeon X850XT. My question is, how do I get from where I'm at now to it actually seeing the Ati for what it is? I didn't see those steps in the post, and am wondering if they are the same as the steps for updating the 3rd party driver?

[Dan]

Hi Gortok

Please read this thread.

http://www.fedoraforum.org/forum/showthread.php?t=127305

[Gortok]

Yup, I found that soon after I made my post. It worked. :-)

Thanks again.

[Dan]

......Anytime!

[mwette]

thanks btw, i upgraded to kernel.org 2.6.18 today, i got rid fglrx from ati, i successfully configured my kernel so drm[i] loads and i noticed that 3d support is lacking .. like slow FPS on 3D game and unresponsiveness but i ill give a try to reinstalling libgl / Xorg. or most likely ill be lazy and wait till FC6. with less than a month, i can wait. plus 3d support wouldnt help now as i have sound issue .. well nice for posting that

I have same issue. I read the article. I found that I needed to do a lot from the
list of "rpm -qa", "rpm -e", "rpm -Va", "rpm -e", "yum install". The xorg.conf file
got hosed but I got it fixed (aticonfig generated some duplicate entries). I find
now that fglrxinfo returns "Mesa" as the OpenGL implementation. "ldd" shows that
/usr/lib/ati-fglrx/libOpenGL is being used.

Attached is Xorg.0.log. I don't see anything problematic there...

[fozner]

Also, please note that the nVidia Geforce 440MX is currently not supported on Fedora Core 6. nVidia has no stable driver for it. Although the current kmod-nvidia rpm does "work" (even compiz!) it is not supported on this card, and it doesn't work with wine games; there is/are the problem/problems of thread locking, missing textures and critical section timeouts... The kmod-nvidia-legacy won't even load GLX! Please don't report bugs with this card-driver-kernel combo until they come out with a "supported" driver. :rolleyes:

Edit: Legacy driver needs Option Composite "Disable" in xorg.conf which Fedora enables by default. That's why it wouldn't load GLX. The card still generates errors on the latest games due to being an old card running with old driver.

[Spontan]

I switched from Nvidia card to a Radeon card. Since I am somewhat a n00b and i can't seem to google the info. Can anyone give me somewhat exact intructions on removing the nvidia drivers. Thanks

[fozner]

Assuming you use Fedora and you installed the driver through rpm or yum, rpm will remove the driver. If you used the NVIDIA installer, run that with --remove option.

Failing that, I'm told you can always remove the OpenGL files manually and install mesa. Refer to http://fedorasolved.org/

[Spontan]

Thanks, I actually eventually figured it out. did the -remove kmod-nvidia or whatever it was now. Got the ATI installed. Thank you for your help!

[h*klown]

i have a nividia 7600 geforce go.. and my desktop effects wont run, nor will beryl manger open..? i didnt install any gpu drivers...???but fedora see its a 7600 go? might my video card be related to desktop themes (effects,tranparncies,cubeetc) be to balme??

FOUND THIS
http://www.nvidia.com/object/linux_display_ia32_1.0-8756.html
http://www.nvnews.net/vbulletin/showthread.php?t=72490-
---=--=---=--Fedora Core 5/6 & RHEL5

If you wish to install the NVIDIA Linux graphics driver on a Fedora Core 5/6 or RHEL5 system, please ensure that your system meets the following requirements:

* the latest update kernel is installed and in use
* a kernel-devel RPM is installed that corresponds to the kernel that is in use. Note, FC6 has a known bug which occasionally installs a kernel-devel RPM that is a different arch than the kernel (i586 & i686 mixed). See: https://bugzilla.redhat.com/bugzilla....cgi?id=211941
* the pkgconfig and xorg-x11-server-sdk RPMs are installed (only applies to FC)
* Xen kernels are not currently supported
* the SELinux environment allows the NVIDIA Linux graphics driver to work (only for drivers older than 1.0-9631 and 1.0-7184 (legacy), respectively)

The first three items above can be addressed with the following commands (they need to be run as root):
# yum install kernel-devel xorg-x11-server-sdk pkgconfig
# yum update
# reboot

If you are using an SMP (multi-CPU and/or multi-core) enabled system in FC5(only), please replace kernel-devel with kernel-smp-devel in the command above.

The SELinux requirement can be addressed via two mechanisms after the NVIDIA Linux graphics driver has been installed:

1) If you do not wish to use SELinux enforcement, you can disable it by running the `setenforce 0` command before starting X, or by adding selinux=0 to the end of the kernel line in /etc/grub.conf and rebooting.

2) If you wish to use SELinux enforcement, you will need to change the security context of the NVIDIA X driver module and of the server-side NVIDIA GLX extension module. To achieve this, please run the commands listed for your platform below:

Linux/x86 (32-bit):
# chcon -t texrel_shlib_t /usr/lib/xorg/modules/drivers/nvidia_drv.so
# chcon -t texrel_shlib_t /usr/lib/xorg/modules/extensions/libglx.so.1.0.9631
# chcon -t texrel_shlib_t /usr/lib/tls/libnvidia-tls.so.1
# chcon -t texrel_shlib_t /usr/lib/libGLcore.so.1.0.9631

[Kre]

Ok, hello all and here's my problem. I'm on a Duron, 850 Mhz and a Nvidia Geforce 2 Ti graphic card, using FC6 (last complete update using << yum update >> was made Thursday, 28.03.2007):

kernel-2.6.18-1.2798.fc6.i686
kernel-2.6.20-1.2933.fc6.i686
kernel-devel-2.6.18-1.2798.fc6.i686
kernel-devel-2.6.20-1.2933.fc6.i686
kernel-headers-2.6.20-1.2933.fc6.i386

The problem is that when trying to get the nvidia driver through livna repository using
yum install kmod-nvidia xorg-x11-drv-nvidia
I get
Running Transaction
Installing: kmod-nvidia ######################### [1/2]
Installing: xorg-x11-drv-nvidia ######################### [2/2]
FATAL: Error inserting nvidia (/lib/modules/2.6.20-1.2933.fc6/extra/nvidia/nvidia.ko): No such device
Installed: kmod-nvidia.i686 0:1.0.9755-2.2.6.20_1.2933.fc6 xorg-x11-drv-nvidia.i386 0:1.0.9755-3.lvn6
Complete!

The problem is that after rebooting (although in the startup sequence the drivers are loading well) the X server crashes and it needs reinitalization and replacing the old conf. file with a new one (it's doing the same thing everytime i boot, even if i'm not changing anything in display's settings). After that it's asking me to accept the new settings (800x600, billions of colors) and the gnome deskiop environment is loading. Maybe it's not an important thing, but I got an obsession with making the beryl working, and I read i need to update the video drivers for that. I think maybe those drivers in the livna repo are not good for my GF2 Ti, but i did not find others.

Thank you and say if you need to see the log that the X server makes everytime i boot. (i think maybe it a more common problem and you heard about it)

[TriBooter]

Thanks...

I appreciate the link to that info.
Looks like I screwed up I guess.

I installed ATI's driver for my Radeon X1300 Pro.

I found out pretty quick it is CRAP on Fedora...

The only thing I gained by installing it was a 'proper' ratio screen resolution of 1680x1050 for my widescreen monitor. The desktop looks great, but otherwise, I think the display is crap and I don't even game. Even just text in programs and web browsers looks rough.

Ironically their controll center looks the worst of all....

[TriBooter]

Anyways, furthering my post....

I'm pretty tired now with trying to get everything working properly and maybe I missed something.
BUT HERE'S MY GRIPE ON THE DRIVER ISSUE....

In my case, my display was "working" with a driver at first boot.
But I have a widescreen digital flat panel (Dell E207WFP)

At first boot it was using some generic driver for the ATI card and the monitor.
It was using a resolution of 1450x???? which was not the right ratio for my widescreen.

None of the available resolutions were the right ratio, so I started looking at other provided drivers. I tried changing to the provided Radeon driver and so forth, but the change would not take and it would go back to defaults.

That's when I got aggrivated and went to ATI's site seeking a linux driver.

So what did I miss? What else was I supposed to do?

[iwasapenguin]

Would any one know if the FC5 kernel (as initially installed) would stuff up installation of the nvidia Vatnta LT card?
I have the official .run package from nvidia but each time I run it it says it can't compile a kernel module because there is some thing wrong with my kernel or a file someplace (taht I doubt I have is blocking it).
If any one can help that would be great

[TriBooter]

I don't know man... I have no faith left in the 2.6.20 kernel

I went from the teens to a 20 my first kernel update and it fell flat after the first boot.
Another kernel update I did the other night of a latter version of 20 did the same thing.

Crap part is that I forgot I needed to change that setting to increase the number of old kernels it keeps to boot. So I lost the one that did halfway operate.

I'm going to wipe the whole dang thing out and start over.
Maybe with another flavor of Linux. A friend of mine did this and solved all his woes.

[iwasapenguin]

Actually this is the best support for my obscure card I've seen yet. Other systems (I collect them) won't let me go past 1024x768 graphics. the problem is when ever I try using something with 3d graphics the frame rate drops and that's without OpenGL. Then the effects are on par with windows crashing.

[TriBooter]

Well, when I did ATI's crap from their site, I gained a useable screen ratio.

Lucky for me it was my monitor's native resolution.
1680x1050

So it will go that far and into widescreen.

The trouble is that it doesn't matter... as the quality is crap.
Makes my eyes and head hurt to read dang text... even with increased DPI and font size.

I'd be happy if it just looked as good as it did generically, and had a resolution the right ratio.
I don't think reading text is much to ask.

Like now, I'm in Vista on the same machine.
The Vista version for it has two proper ratios for my display.
1680x1050 and 1280x800.
Both look great, and it looks extra good in 1680x1050.
But I use 1280x800 because the text is larger and it looks more normal to me.

I'm not sure what to do.
I guess I could start over with Fedora Core 6.
Then get an open source driver for my X1300 Pro.
But then I'd have to pray for a proper widescreen aspect ratio...
And I'd have to do without any updates.

Doesn't sound enthusing.

[iwasapenguin]

Mmm... the prob is that most of these people are used to writing drivers in windows I expect.
Bad habbits, bad sys, bad drivers (I beleave that half of Windows problems is that the people who code it learnt in windows).

[TriBooter]

Mmm... the prob is that most of these people are used to writing drivers in windows I expect.
Bad habbits, bad sys, bad drivers (I beleave that half of Windows problems is that the people who code it learnt in windows).

Could be.

I myself don't have much trust in, or respect for Windows operating systems.
Well... other than I marvel at what they can do that I can't yet...

I like Linux better overall, but here in the real world, Windows is sorta shoved down your throat rather you like it or not. I myself stayed with windows 98 for nine years. It took me until 2005 to start using XP some. And during that time, I kept one single installation of Windows 98 up and running. To this day, it's never been wiped out and reinstalled. But it took a lot of wrenching and tweaking on my part to get it stabilized... and some help from "free" applications.... and I think it probably helped too that new versions of windows released and I got off the bleeding edge and left way behind. Out of sight, out of mind, out of focus of viruses, hackers, ect.

When I started trying to learn a little about application programming... well then I had to move to the NT family. After working with some of their languages, etc, I'm left with one basic thought... it's no wonder most things Microsoft are the way they are... shesh!!!

After using Fedora a while, I'm sorta left with the basic thought... there's gotta be a less complicated way.... I know a lot of it is the hardware MFG's, but at the same time since I have not tinkered with any other distributions, I have to wonder if the grass is greener?

[martinellison]

See http://www.linuxquestions.org/questions/showthread.php?p=2780981 for a fix if your NVIDIA driver fails to load on F7. Note that the fix is different for the x86_64 architecture.

[zx5000]

(II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
compiled for 7.1.0, module version = 8.36.5
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 1.0
[atiddxSetup] X version mismatch - detected X.org 1.3.0.0, required X.org 7.1.0.0
(II) UnloadModule: "fglrx"
(II) Unloading /usr/lib/xorg/modules/drivers//fglrx_drv.so
(EE) Failed to load module "fglrx" (module requirement mismatch, 0)

[stuffdone]

When I did the fresh install on new system everything went great. Then after the install when I reboot I get no video...Acer monitor displays error "Video Input Not Supported"

Several searches seem to point to settings for the monitor but each offers solutions that look different to me. I am a novice with Linux so any advice with that in mind is most appreciated.

Building dual boot. Fedora 64 bit and Win2K. MoBo M2NBP-VM with AMD 64 Dual Core and 3 GB Ram. Nvida Gforce6 dual head card. Using analog only. No DVI monitor available.

Thanks ! :)

[judgeoz]

I am having difficulty installing Fedora Ver 7 from CD

From the start the installation falls over when checking system...

At the point when recognising the two Nvidia cards they are 6600 GT extreme cards SLI connected. The screen turns to hash and install stops at that point.

The hardrive currently has Xandros version 3 installed

Any assistance or suggestions would be greatly appreciated.

[slovey]

Thank you very much!

[rxmccaf]

This appears to be correct. Fedora 7 installs Kernel 2.6.22.X. But of course it soon tries to upgrade you to 2.6.23.X.
I have an ATI Radeon X1950 PCIe on a AMD x86_64
Even after adding the dev packages( gcc, etc...), kernel source packages, dkms, libdrm, rpm-build, etc... I was unable to run
the ati install program. (8.42.4) or even the older ones (8.40.4 & 8.38.6) under any of the 2.6.23.X Kernels. However it works great under the 2.6.22.X Kernels. Even 8.42.4 seems to work fine on the 2.6.22 Kernels. However I did notice, if I try to set up a dual boot using both kernels, it pixelizes everything back on the 2.6.22 kernel. For now, it seems the best thing to do, is not upgrade your kernel. GL games such as PPracer, SuperTux, Arena, TuxKartRacer, etc... work great. GLX/Compiz cube and wobble effects also work great. With the 8.42.4 installer, I was able to leave the Composite Option under Extensions set to True. With older versions I've always had to set this to false.

Ray

[rxmccaf]

OK. Here is how I got my ATI Radeon X1950 to work under Fedora 8 on an AMD x86_64 system.
It's not trivial, but not super difficult either. This worked with kernel 2.6.23.1-42.fc8
There are really two problems - This should fix both of them.

1. Download the driver from http://ati.amd.com/support/drivers/linux64/linux64-radeon.html

2. It will most likely put this in your /home/username/Desktop directory. (where username is the name you used to login). So cd /home/username/Desktop

3. chmod 744 ati-driver-installer-8.42.3-x86.x86_64.run

4. Go ahead and try to install it. ./ati-driver-installer-8.42.3-x86.x86_64.run
If you are running Gnome or KDE it will look like it worked, you won't see any errors. But it really didn't work.
It will fail and you will get all kinds of errors. But thats OK - it made a directory for us that we will need later.
If you really want to see the errors - try this.. ./ati-driver-installer-8.42.3-x86.x86_64.run --buildpkg Fedora/F8

6. ./ati-driver-installer-8.42.3-x86.x86_64.run --extract fglrx_8_42
This will create a directory called fglrx_8_42

7. download this as a text file and name it ati-fix-tmp. http://docs.google.com/View?docid=ddbph2tz_16hfmq4q

8. mv fglrx_8_42/packages/Fedora/ati-packager.sh fglrx_8_42/packages/Fedora/ati-packager.sh.orig
This backs up the original file to a new name.

9. cp ati-fix-tmp fglrx_8_42/packages/Fedora/ati-packager.sh
This replaces the original file, with the file you just made.

10. chmod 755 fglrx_8_42/packages/Fedora/ati-packager.sh
This makes the file executable so the script will run.

11. cd fglrx_8_42

12. ./ati-installer.sh 8.42.3 --buildpkg Fedora/F8
# NOTE: you must put in the "8.42.3" above.

13. This will still fail, but we fixed the first problem, which was creating the /tmp directory with the wrong name.
For the second problem - this is from http://wiki.cchtml.com/index.php/Fedora_8_Installation_Guide

14. cd /lib/modules/fglrx/build_mod/

15, cp firegl_public.c firegl_public.c.orig

16. with your favorite text editor create this file. Name it firegl.patch (I know it says 2.6.22, but it
works with 2.6.23 also)
## ========= Copy and paste =============
8.43.3 for 2.6.23 compatibility

--- firegl_public.c.orig 2007-10-23 19:31:26.000000000 +0200
+++ firegl_public.c 2007-10-23 19:32:07.000000000 +0200
@@ -217,6 +217,56 @@
#define preempt_enable()
#endif

+#if LINUX_VERSION_CODE > KERNEL_VERSION(2,6,22)
+#if defined(__i386__)
+#define ptep_test_and_clear_dirty(vma, addr, ptep) ({ \
+ int __ret = 0; \
+ if (pte_dirty(*(ptep))) \
+ __ret = test_and_clear_bit(_PAGE_BIT_DIRTY, \
+ &(ptep)->pte_low); \
+ if (__ret) \
+ pte_update((vma)->vm_mm, addr, ptep); \
+ __ret; \
+})
+
+static inline int pte_read(pte_t pte) { return (pte).pte_low & _PAGE_USER; }
+static inline int pte_user(pte_t pte) { return (pte).pte_low & _PAGE_USER; }
+#ifdef CONFIG_X86_PAE
+/*
+ * Is the pte executable?
+ */
+static inline int pte_x(pte_t pte)
+{
+ return !(pte_val(pte) & _PAGE_NX);
+}
+
+/*
+ * All present user-pages with !NX bit are user-executable:
+ */
+static inline int pte_exec(pte_t pte)
+{
+ return pte_user(pte) && pte_x(pte);
+}
+#else
+static inline int pte_exec(pte_t pte)
+{
+ return pte_user(pte);
+}
+#endif /* PAE */
+
+#elif defined(__x86_64__)
+static inline int ptep_test_and_clear_dirty(struct vm_area_struct *vma,
+ unsigned long addr, pte_t *ptep)
+{
+ if (!pte_dirty(*ptep))
+ return 0;
+ return test_and_clear_bit(_PAGE_BIT_DIRTY, &ptep->pte);
+}
+static inline int pte_read(pte_t pte) { return pte_val(pte) & _PAGE_USER; }
+static inline int pte_exec(pte_t pte) { return !(pte_val(pte) & _PAGE_NX); }
+#endif
+#endif
+
// ================================================== ==========
/* globals */

@@ -2489,7 +2539,7 @@ void ATI_API_CALL __ke_put_vm_page_table
#ifndef ptep_clear_flush_dirty
#define ptep_clear_flush_dirty(__vma, __address, __ptep) \
({ \
- int __dirty = ptep_test_and_clear_dirty(__ptep); \
+ int __dirty = ptep_test_and_clear_dirty(__vma, __address, __ptep); \
if (__dirty) \
flush_tlb_page(__vma, __address); \
__dirty; \
@@ -2936,7 +2986,7 @@ int ATI_API_CALL __ke_request_irq(unsign
{
return request_irq(irq,
(void(*)(int, void *, struct pt_regs *))handler,
- SA_SHIRQ, dev_name, dev_id);
+ IRQF_SHARED, dev_name, dev_id);
}

void ATI_API_CALL __ke_free_irq(unsigned int irq, void *dev_id)
@@ -2959,7 +3009,7 @@ int ATI_API_CALL __ke_request_irq(unsign
irq_handler_func = handler;
return request_irq(irq,
ke_irq_handler_wrap,
- SA_SHIRQ, dev_name, dev_id);
+ IRQF_SHARED, dev_name, dev_id);
}

void ATI_API_CALL __ke_free_irq(unsigned int irq, void *dev_id)
@@ -5436,7 +5486,7 @@ unsigned int ATI_API_CALL KAS_Spinlock_R
/** \brief Type definition of the structure describing Slab Cache object */
typedef struct tag_kasSlabCache_t
{
- kmem_cache_t* cache; /* OS slab cache object */
+ struct kmem_cache *cache; /* OS slab cache object */
spinlock_t lock; /* OS spinlock object protecting the cache */
unsigned int routine_type; /* Type of routine the cache might be accessed from */
char name[14]; /* Cache object name (kernel 2.4 restricts its length to 19 chars) */
@@ -5482,7 +5532,7 @@ unsigned int ATI_API_CALL KAS_SlabCache_
DBG_TRACE("creating slab object '%s'", slabcache_obj->name);

if ((slabcache_obj->cache =
- kmem_cache_create(slabcache_obj->name, iEntrySize, 0, 0, NULL, NULL)))
+ kmem_cache_create(slabcache_obj->name, iEntrySize, 0, 0, NULL)))
{
ret = 1;
}
## =========== End - copy and paste ============

17. patch -p0 < firegl.patch

18. ./make.sh
You may see some warnings - but it will compile.

19 . cd ..

20. ./make_install.sh
You may see some warnings - but it will compile.

21. aticonfig --initial -f

22. modprobe fglrx

23. ldconfig

24. Use cntrl-alt-backspace (hold down all 3 at the same time) to restart your Xwindows server.

25. Log back in. Open a command line terminal.

26. su - (it will ask for the root password)

27. glxinfo | grep direct
you should see... direct rendering: Yes

* This is optional - but perhaps helpful.

28. cd /etc/X11

29. Use your favorite text editor to edit xorg.conf
at the very bottom add this...

Section "DRI"
Mode 0666
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection

30. You may also want to edit the "device" section like this.

Section "Device"
Identifier "aticonfig-Device[0]" # this line is already there
Driver "fglrx" # this line is already there
Option "UseFastTLS" "0" #add this line
Option "BlockSignalsOnLock" "on" #add this line
Option "ForceGenericCPU" "off" #add this line
Option "KernelModuleParm" "locked-userpages=0" #add this line
BusID "PCI:7:0:0" # This line is useful for PCIe (PCI Express) cards ONLY!!
EndSection

31. from the command line as root try the following commands.
glxgears - after a few minutes you can close the window
fgl_glxgears - after a few minutes you can close the window

32. At this point if everything works, I would reboot the computer. Congradulations!!!

[mdb]

This worked perfectly for me last night in installing this for my ATI Radeon X1300 Pro card (AGP bus). There is one small glitch--if you copy/paste the long patch as shown here, it will complain about a problem around line 7 when you run the patch -p0 in the next step. I found it was better to follow the link just before the patch and do the wget to download the patch listing into the file, firegl.patch. Otherwise, if you follow every step just as outlined here, it worked perfectly, and I've got the driver running under Fedora Core 8 now.

[screwballl]

I got all the way to step 17 and got this error:

[root@localhost build_mod]# patch -p0 < firegl.patch
patching file firegl_public.c
patch: **** malformed patch at line 6: #define preempt_enable()

and it will not let me go any further.

I tried it 2 ways, in step 16 i saved it to the last folder being used which was /lib/modules/fglrx/build_mod/ and this is when I get this error.
If I save it to the Desktop then I get it asking "File to patch:"

[root@localhost Desktop]# patch -p0 < firegl.patch
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|8.43.3 for 2.6.23 compatibility
|
|--- firegl_public.c.orig 2007-10-23 19:31:26.000000000 +0200
|+++ firegl_public.c 2007-10-23 19:32:07.000000000 +0200
--------------------------
File to patch: ^C
[root@localhost Desktop]#


At this point nothing beyond it works


edit: I will follow what mdb stated here and report back as to my success

[rxmccaf]

Make sure the patch file is in the same directory as firegl_public.c
which should be /lib/modules/fglrx/build_mod/

if you do an ls you should see both firegl.patch and firegl_public.c

[screwballl]

already tried that
did not work for me

but something else did work for me, on the other website you mentioned in step 13 gave an alternative method which did work for me
http://wiki.cchtml.com/index.php/Fedora_8_Installation_Guide


Installation from Livna repository

rpm -ivh http://rpm.livna.org/livna-release-8.rpm
yum install -y kmod-fglrx

and restart X

At this point I typed in "glxinfo | grep direct" and it said "direct rendering: Yes"

wow that would have saved a whole lot of time.. plus when I restarted X it went straight to my 1440x900 on the primary monitor... now need to get the dual head working as the secondary monitor is also showing a mirrored 1440x900 but as it is a 17" CRT, it "scrolls" to the different areas. Any changes to the xorg.conf just completely mess up X so I will need somxe further digging to get that working properly. Primary is 19" widescreen LCD at 1440x900 and secondary is 17" CRT native at 1280x1024.

[dibl]

Brand new to Fedora, not so new to Linux -- searched and didn't find anything helpful on this. Forgive me if I missed the obvious answer, please.

I installed/enabled the Livna repo and followed the drill to install the newest available Nvidia driver on my F8 (64-bit) system. It appeared to install correctly. Ran "nvidia-settings" in root mode and set my default resolution, detected my display, and saved to the /etc/X11/xorg.conf file. Verified my xorg.conf file against (a) the one that works great in Ubuntu and (b) the many examples around this forum, and on firewing1's site. Added the "Coolbits" option for fun. Ran "nvidia-settings" as a user and it looks right.

Opened the terminal and entered "glxgears". The X server restarted. Hmmmmmmmm! Logged back in, opened "nvidia-settings" and clicked the "OpenGL/GLX Information" item. The X server restarted.

Logged back in, searched for anything, came up empty.

I noticed this error in the terminal window after running "nvidia-settings" again:

Xlib: extension "XVideo" missing on display ":0.0".

Anyone got a clue?

Here's my xorg.conf file:

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder26) Wed Sep 12 14:29:17 PDT 2007

# Xorg configuration created by livna-config-display

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
ModulePath "/usr/lib64/xorg/modules"
EndSection

Section "Module"
Load "glx"
EndSection

Section "ServerFlags"
Option "AIGLX" "on"
Option "Xinerama" "0"
EndSection

Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us+inet"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Samsung SyncMaster"
HorizSync 30.0 - 130.0
VertRefresh 50.0 - 160.0
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 7900 GS"
Option "AddARGBGLXVisuals" "True"
Option "DisableGLXRootClipping" "True"
Option "Coolbits" "1"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "1600x1200 +0+0"

SubSection "Display"
Depth 24
EndSubSection
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection

[rogster]

The guide worked VERY well at the end I saw the gears and the gears in the cube, and the direct rendering was a big YES, but upon reboot X couldn't load with the new config and reverted to the old where my redering is a big NO now.

I'm still new to fedora so help is appreciated

What steps can I take now to get the old config back now (in addition to fixing the X problem)

[RossClement]

The guide worked VERY well at the end I saw the gears and the gears in the cube, and the direct rendering was a big YES, but upon reboot X couldn't load with the new config and reverted to the old where my redering is a big NO now.

I'm still new to fedora so help is appreciated

What steps can I take now to get the old config back now (in addition to fixing the X problem)

I'm having a similar problem. I installed the nvidia modules from livna, and rebooted. But on reboot I got the famous "can't start X server", and it goes through the whole process, ending up with the old non-3d drivers installed and working. This now happens every time I reboot.

I didn't run "nvidia-settings" (or whatever it's called), could this be the problem.

I include the output of glxinfo (showing that the mesa driver is running) and also a .png of my nvidia rpms installed.

My card is an old GeForce 2 card.

Any hints as to what might be wrong?

[zx5000]

nvidia-settings doesn't really do much.

try this first /usr/bin/nvidia-xconfig this will create a nvidia specific xorg.conf file.
backup your xorg.conf to a safe name you'll remember.
try to start your x server
if it fails don't go through the config process
save the Xorg.0.log
to get x working again you should be able to just replace the nvida with nv in the device section and restart X.
examine your saved Xorg.0.log and it should give you some hints.

[RossClement]

I finally got to try this. The Xorg.0.log file said that my card isn't supported by the nvidia drivers and that I should use nvidia-legacy. I uninstalled the nvidia driver and kernel module,and installed the corresponding nvidia-legacy ones. Note that all installation and uninstallation I've done has been through yum (specifically yumex) using livna packages.

This time the computer goes boot, and X comes up. But when I try to use opengl (e.g. when I run glxgears, 3D doesn't work. Also, when it boots it only gives me the option of 800x600 and 640x480 (I think, in any case, no 1024x768) screens.

nvidia settings does work, and I can adjust things such as gamma. But when I try to adjust openGl/GLX settings, I get:


The OpenGL extension 'GLX' is not supported by
the X server or there was a problem retrieving
GLX information from the X server.


I attach here my Xorg.0.log file, and also my /etc/X11/xorg.conf file, and also the output of glxinfo.

[karlpiuemeno]

Installing the fglrx drivers from livna repo, black screen at reboot.... or better: displays shuts down on gnome loading / login....

mine is an x1050 AGP

[TriBooter]

I have much respect for the Fedora Project and I am very thankful for the learning I was able to do in the environment...... and for this reason I am likely to try to "keep up" with what's going on and what is new.....................................

But sadly, frustration got the best of me back in 6.
I jumped ship to Ubuntu and I'm not having near the difficulty anymore.
I am however still stuck with 1680x1050 (native resolution for my monitor).
But it looks very good in Ubuntu.... I'd just rather have a 1280x800 option.



Anyways, my contribution to this is that ATI released a new Catalyst Control Center version.
It's much better than previous versions and I'm using it with no problem in Ubuntu.

I don't like the idea of this really, all things considered.
But I thought I'd share the info to see what you guys have to say about it....

[RossClement]

I finally got to try this. The Xorg.0.log file said that my card isn't supported by the nvidia drivers and that I should use nvidia-legacy. I uninstalled the nvidia driver and kernel module,and installed the corresponding nvidia-legacy ones. Note that all installation and uninstallation I've done has been through yum (specifically yumex) using livna packages.


I finally solved my problems. Partially at least.

Even though the error message in the xorg log file said to use the legacy drivers, my card wouldn't work property with the kmod-legacy drivers. It's the 96xx drivers I needed, not the straight legacy ones.

And, when I installed the modules, it didn't modify my xorg.conf file. So I had to go through that and add bits, changing the driver to "nvidia" and loading various glx and extmod (?) extensions to get it to work. It does now work, including the aiglx (?) extensions rather than xgl, allowing me wobbly windows and the like. The number I get out of glxgears does seem suspiciously low, bug glxinfo reports that nvidia is running. There may be some more refinement to go.

[jmuirhead]

Problem is: how do you know which rpm package to install? kmod-nvidia, the 96xx one, or the legacy one? Which nVidia card goes with which package?

[Reindeer]

Problem is: how do you know which rpm package to install? kmod-nvidia, the 96xx one, or the legacy one? Which nVidia card goes with which package?

I have the very same question.
Yum is giving me an error when I try to install the latest round of nVidia drivers:


--> Running transaction check
---> Package kmod-nvidia-96xx.x86_64 0:96.43.01-1.2.6.23.8_34.fc7 set to be updated
--> Processing Conflict: xorg-x11-drv-nvidia-96xx conflicts xorg-x11-drv-nvidia
--> Processing Conflict: xorg-x11-drv-nvidia conflicts xorg-x11-drv-nvidia-96xx
--> Restarting Dependency Resolution with new changes.
---> Loop Number: 2
--> Running transaction check
--> Finished Dependency Resolution
Error: xorg-x11-drv-nvidia-96xx conflicts with xorg-x11-drv-nvidia

Looking at some of the troubles that others are having installing the latest nVidia drivers,
I am loathe to upset my working system.
Does anyone know which drivers are the right ones for 64bit Fedora 7 ?

I'm currently using 100.14.19 on Xorg version 1.3.0 with a GeForce 7600 GT

[RossClement]

I have the very same question.
Yum is giving me an error when I try to install the latest round of nVidia drivers:


--> Running transaction check
---> Package kmod-nvidia-96xx.x86_64 0:96.43.01-1.2.6.23.8_34.fc7 set to be updated
--> Processing Conflict: xorg-x11-drv-nvidia-96xx conflicts xorg-x11-drv-nvidia
--> Processing Conflict: xorg-x11-drv-nvidia conflicts xorg-x11-drv-nvidia-96xx
--> Restarting Dependency Resolution with new changes.
---> Loop Number: 2
--> Running transaction check
--> Finished Dependency Resolution
Error: xorg-x11-drv-nvidia-96xx conflicts with xorg-x11-drv-nvidia

Looking at some of the troubles that others are having installing the latest nVidia drivers,
I am loathe to upset my working system.
Does anyone know which drivers are the right ones for 64bit Fedora 7 ?

I'm currently using 100.14.19 on Xorg version 1.3.0 with a GeForce 7600 GT

From experience it seems to me that if you want to switch from one flavour (kmod-nvidia, kmod-nvidia-96xx, kmod-nvidia-legacy) of driver to another, that you have to remove the old drivers first, then install. That worked for me.

Also, while I do not claim to be expert on this, if I was choosing drivers for another nvidia card, I'd start with the newest ones and move to older ones until I found one that worked. There are only three choices really.

[nestle]

wtf is a cc tool?
i've tryed to install nvidia driver and it gives me a error: cannotfind cc tool (or smth)

[imperial_auriga]

I don't know if this was previously talked about, but I noticed that my fedora 8 server wasn't booting up without a monitor screen attached to it. I googled around and found out that Apple Computers (makes sense since they are also Unix Based) have the same "problem". The solution: install an external video card. I used an ATI Rage 128 and it seems that even if I turn off the computer, without a screen and even cutting power to power supply and then restart the whole thing: the x-server still boots to login screen perfectly.
Please bear in mind that the PC boots automaticaly to a user, with remote desktop running. From there I control it through a VNC viewer. The problem I had resulted in x-server saying my resolution wasn't ok, and hung at that point. I couldn't never connect in such condition and it was not feasible to leave a monitor with the PC for the sole purpose of allowing the boot.

[kbryan]

ok, i am brand new to linux, so barney style answers and tips will be great, but at this point i will take anything.

i have read everything i can find on problems with the nvidia graphics cards, i have tried everything i have read but i am still having no luck.

Nvidia GeForce Go 7900 GS is the make and model, fedora core 7 gnome is the version of linux, on an alienware m9750 laptop.

just to clarify.... the "yum -y install kmod-nvidia glx-utils" didnt work
"yum install kmod-nvidia-96xx" didnt work

and the driver downloaded from nvidia with the "/sbin/telinit 3" ......ect didnt work either (and i have done a yum install of kernel-devel)

i tried reading all i can and searching for the answer so i wouldnt have do put another nvidia graphics card post up but i dont know what else to do at this point. please help
:confused:

[Hlingler]

Hello:

First, if you have tried to install the binary driver provided by nvidia from their website, you have probably screwed up your install - see the link in the very first post of this thread. If true, you will probably need to re-install all the OpenGL-type stuff. Sad, but true.

Second, please clarify "...didn't work..." Did kmod-nvidia and/or glx-utils fail to install? If so, why, failed dependencies? Or were the packages not found (you must first install the Livna repo). BTW, your card is supported by the latest driver, so don't use the kmod-nvidia-96xx legacy driver.

Last, you may need to read a little more: http://forums.fedoraforum.org/showthread.php?t=99285.
See also: http://www.mjmwired.net/resources/mjm-fedora-f7.html#nvidia.

Regards,
V

[kbryan]

so i tried the first link Hlingler gave me and this is exactly what the outcome was, i do not know where to go from here. this is the same end result i recieved when i attempted the kmod-nvidia glx-utils install.

[kbryan@localhost ~]$ su -
Password:
[root@localhost ~]# rpm -Uhv http://rpm.livna.org/livna-release-7.rpm
Retrieving http://rpm.livna.org/livna-release-7.rpm
warning: /var/tmp/rpm-xfer.RDtAq6: Header V3 DSA signature: NOKEY, key ID a109b1ec
Preparing... ########################################### [100%]
1:livna-release ########################################### [100%]
[root@localhost ~]# yum install kmod-nvidia xorg-x11-drv-nvidia xorg-x11-drv-nvidia-libs-32bit
Loading "installonlyn" plugin
Setting up Install Process
Parsing package install arguments
livna 100% |=========================| 2.1 kB 00:00
primary.sqlite.bz2 100% |=========================| 190 kB 00:52
Resolving Dependencies
--> Running transaction check
---> Package xorg-x11-drv-nvidia-libs.i386 0:169.09-3.lvn7 set to be updated
---> Package xorg-x11-drv-nvidia.i386 0:169.09-3.lvn7 set to be updated
Importing additional filelist information
filelists.sqlite.bz2 100% |=========================| 1.1 MB 07:18
http://ftp.gts.lug.ro/fedora/linux/releases/7/Everything/i386/os/repodata/filelists.sqlite.bz2: [Errno 4] Socket Error: timed out
Trying other mirror.
filelists.sqlite.bz2 100% |=========================| 344 kB 05:55
http://mirror.lib.ucdavis.edu/fedora/linux/releases/7/Everything/i386/os/repodata/filelists.sqlite.bz2: [Errno 4] Socket Error: timed out
Trying other mirror.
filelists.sqlite.bz2 100% |=========================| 6.4 MB 37:50
filelists.sqlite.bz2 100% |=========================| 268 kB 01:53
filelists.sqlite.bz2 100% |=========================| 1.9 MB 11:13
http://ftp.uni-bayreuth.de/linux/fedora/linux/updates/7/i386/repodata/filelists.sqlite.bz2: [Errno 4] Socket Error: timed out
Trying other mirror.
filelists.sqlite.bz2 100% |=========================| 5.0 MB 39:39
---> Package kmod-nvidia.i686 0:169.09-3.2.6.23.14_64.fc7 set to be updated
--> Processing Dependency: kernel-i686 = 2.6.23.14-64.fc7 for package: kmod-nvidia
--> Processing Dependency: livna-config-display for package: xorg-x11-drv-nvidia
--> Restarting Dependency Resolution with new changes.
--> Running transaction check
---> Package kernel.i686 0:2.6.23.14-64.fc7 set to be updated
---> Package livna-config-display.noarch 0:0.0.20-1.lvn7 set to be updated
--> Processing Dependency: mkinitrd >= 6.0.9-7.1 for package: kernel
--> Restarting Dependency Resolution with new changes.
--> Running transaction check
---> Package mkinitrd.i386 0:6.0.9-7.1 set to be updated
--> Processing Dependency: nash = 6.0.9-7.1 for package: mkinitrd
--> Restarting Dependency Resolution with new changes.
--> Running transaction check
---> Package nash.i386 0:6.0.9-7.1 set to be updated

Dependencies Resolved

================================================== ===========================
Package Arch Version Repository Size
================================================== ===========================
Installing:
kmod-nvidia i686 169.09-3.2.6.23.14_64.fc7 livna 2.6 M
xorg-x11-drv-nvidia i386 169.09-3.lvn7 livna 1.9 M
xorg-x11-drv-nvidia-libs i386 169.09-3.lvn7 livna 5.0 M
Installing for dependencies:
kernel i686 2.6.23.14-64.fc7 updates 16 M
livna-config-display noarch 0.0.20-1.lvn7 livna 65 k
Updating for dependencies:
mkinitrd i386 6.0.9-7.1 updates 91 k
nash i386 6.0.9-7.1 updates 158 k

Transaction Summary
================================================== ===========================
Install 5 Package(s)
Update 2 Package(s)
Remove 0 Package(s)

Total download size: 26 M
Is this ok [y/N]: y
Downloading Packages:
(1/7): livna-config-displ 100% |=========================| 65 kB 00:30
(2/7): xorg-x11-drv-nvidi 100% |=========================| 312 kB 03:21
http://rpm.livna.org/fedora/7/i386/xorg-x11-drv-nvidia-libs-169.09-3.lvn7.i386.rpm: [Errno 4] Socket Error: timed out
Trying other mirror.
(2/7): xorg-x11-drv-nvidi 100% |=========================| 5.0 MB 37:37
(3/7): kernel-2.6.23.14-6 100% |=========================| 16 MB 91:26
(4/7): mkinitrd-6.0.9-7.1 100% |=========================| 91 kB 00:44
(5/7): kmod-nvidia-169.09 100% |=========================| 2.6 MB 16:54
(6/7): nash-6.0.9-7.1.i38 100% |=========================| 158 kB 00:58
(7/7): xorg-x11-drv-nvidi 100% |=========================| 1.9 MB 10:33
warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID a109b1ec
Importing GPG key 0xA109B1EC "Livna.org rpms <rpm-key@livna.org>" from /etc/pki/rpm-gpg/RPM-GPG-KEY-livna
Is this ok [y/N]: y
warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2
Importing GPG key 0x4F2A6FD2 "Fedora Project <fedora@redhat.com>" from /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
Is this ok [y/N]: y
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Updating : nash ######################### [1/9]
Updating : mkinitrd ######################### [2/9]
Installing: kernel ######################### [3/9]
Installing: livna-config-display ######################### [4/9]
Installing: xorg-x11-drv-nvidia-libs ######################### [5/9]
Installing: kmod-nvidia ######################### [6/9]
Installing: xorg-x11-drv-nvidia ######################### [7/9]
Cleanup : nash ######################### [8/9]
Cleanup : mkinitrd ######################### [9/9]

Installed: kmod-nvidia.i686 0:169.09-3.2.6.23.14_64.fc7 xorg-x11-drv-nvidia.i386 0:169.09-3.lvn7 xorg-x11-drv-nvidia-libs.i386 0:169.09-3.lvn7
Dependency Installed: kernel.i686 0:2.6.23.14-64.fc7 livna-config-display.noarch 0:0.0.20-1.lvn7
Dependency Updated: mkinitrd.i386 0:6.0.9-7.1 nash.i386 0:6.0.9-7.1
Complete!
[root@localhost ~]# yum -y update kmod-nvidia xorg-x11-drv-nvidia xorg-x11-drv-nvidia-libs-32bit
Loading "installonlyn" plugin
Setting up Update Process
fedora 100% |=========================| 2.1 kB 00:00
livna 100% |=========================| 2.1 kB 00:00
primary.sqlite.bz2 100% |=========================| 191 kB 00:46
ftp://mirror.cs.princeton.edu/pub/mirrors/fedora/linux/updates/7/i386/repodata/repomd.xml: [Errno 4] IOError: [Errno ftp error] 421 Sorry, mirror already has 22 users logged on. Try again in 10 minutes.
Trying other mirror.
updates 100% |=========================| 2.3 kB 00:00
Could not find update match for kmod-nvidia
Could not find update match for xorg-x11-drv-nvidia-libs-32bit
Resolving Dependencies
--> Running transaction check
filelists.sqlite.bz2 100% |=========================| 268 kB 01:26
---> Package xorg-x11-drv-nvidia.i386 0:169.09-4.lvn7 set to be updated
--> Processing Dependency: xorg-x11-drv-nvidia = 169.09-3.lvn7 for package: xorg-x11-drv-nvidia-libs
--> Processing Dependency: xorg-x11-drv-nvidia-libs = 169.09-4.lvn7 for package: xorg-x11-drv-nvidia
--> Restarting Dependency Resolution with new changes.
--> Running transaction check
---> Package xorg-x11-drv-nvidia-libs.i386 0:169.09-4.lvn7 set to be updated

Dependencies Resolved

================================================== ===========================
Package Arch Version Repository Size
================================================== ===========================
Updating:
xorg-x11-drv-nvidia i386 169.09-4.lvn7 livna 1.9 M
Updating for dependencies:
xorg-x11-drv-nvidia-libs i386 169.09-4.lvn7 livna 5.0 M

Transaction Summary
================================================== ===========================
Install 0 Package(s)
Update 2 Package(s)
Remove 0 Package(s)

Total download size: 6.9 M
Downloading Packages:
(1/2): xorg-x11-drv-nvidi 100% |=========================| 5.0 MB 24:28
(2/2): xorg-x11-drv-nvidi 100% |=========================| 1.9 MB 08:24
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Updating : xorg-x11-drv-nvidia-libs ######################### [1/4]
Updating : xorg-x11-drv-nvidia ######################### [2/4]
Cleanup : xorg-x11-drv-nvidia ######################### [3/4]
Cleanup : xorg-x11-drv-nvidia-libs ######################### [4/4]

Updated: xorg-x11-drv-nvidia.i386 0:169.09-4.lvn7
Dependency Updated: xorg-x11-drv-nvidia-libs.i386 0:169.09-4.lvn7
Complete!
[root@localhost ~]# service nvidia restart

[root@localhost ~]# service nvidia restart
Checking for module nvidia.ko: [FAILED]
nvidia.ko for kernel 2.6.20-2925.9.fc7xen was not found. [WARNING]
The nvidia driver will not be enabled until one is found. [WARNING]
Driver already disabled.
You have new mail in /var/spool/mail/root

what do i do to fix or undo this?

[Hlingler]

Reboot to the new kernel - your new kmod-nvidia driver module is for that kernel only.

V

[kbryan]

well if thats the case then i would love to give it a shot...... but how exactly do i reboot to the new kernel? dummy steps please, im new at this

[Loki1950]

When you reboot the newest kernel is at the top of the list but that is only if you hit a key to stop the default kernel boot which is the latest one.
Welcome to circleland ;) it should be that simple

Enjoy the Choice :)

[Hlingler]

well if thats the case then i would love to give it a shot...... but how exactly do i reboot to the new kernel? dummy steps please, im new at thisFind the button somewhere on the menu that says "Shutdown", and press it. You should be given a choice to logout, restart, or shutdown. Choose restart. When the computer reboots, you will first see the BIOS loading, followed by GRUB (the bootloader) - it's a very blue background. It lists the available boot choices (different kernels and/or operating systems). You have a few seconds to make a choice before it loads the default item. Make sure that the newest kernel is highlighted, or use the arrow keys to pick the newest kernel. Hit <enter>.

If the latest kernel was not highlighted by default, you can change that behavior, too. Once you're all logged in and back at a running desktop, find on the menus: Bootloader config. It's a very simple GUI - it lists the same choices that you saw when GRUB was loading, and you get to pick the default item and the countdown timer setting. That's all there is to it.

Regards,
V

[snm_cal]

I have a nvidia 4000 mx series card. Installed livna legacy drivers. How to configure xorg.conf? It looks like this now..
# Xorg configuration created by system-config-display

Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
ModulePath "/usr/lib/xorg/modules"
EndSection

Section "ServerFlags"
Option "AIGLX" "off"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us+inet"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "Extensions"
Option "Composite" "Disable"
EndSection

Please Help.

[Hlingler]

I have a nvidia 4000 mx series card. Installed livna legacy drivers. How to configure xorg.conf? It looks like this now..
It usually helps to know what flavor of Fedora you're running, since this can make a difference.

There is an excellent HOWTO by the guy that builds the Livna nvidia drivers (FireWing1) here: http://forums.fedoraforum.org/showthread.php?t=99285. NOTE the first line (in red) redirecting you to his own website for the latest revisions of the HOWTO for F7/8. I strongly recommend that you consult them (they're actually fairly short and simple). If you have problems after that, you can post to that thread, where FireWing1 will see your post and hopefully respond.

Regards,
V

[venumus]

so i have geforce 7150m and im haveing problems hahah i cant get it to work sometimes. i have to reinstalland re configure the driver everytime.. i tried to dl kmod-nvidia

WARNING: /lib/modules/2.6.23.15-137.fc8/kernel/sound/drivers/opl3/snd-opl3-synth.ko needs unknown symbol strlcpy
WARNING: /lib/modules/2.6.23.15-137.fc8/kernel/sound/drivers/opl3/snd-opl3-synth.ko needs unknown symbol param_set_bool
WARNING: /lib/modules/2.6.23.15-137.fc8/kernel/sound/drivers/opl3/snd-opl3-synth.ko needs unknown symbol printk
WARNING: /lib/modules/2.6.23.15-137.fc8/kernel/sound/drivers/opl3/snd-opl3-synth.ko needs unknown symbol memset
WARNING: /lib/modules/2.6.23.15-137.fc8/kernel/sound/drivers/opl3/snd-opl3-synth.ko needs unknown symbol jiffies
WARNING: /lib/modules/2.6.23.15-137.fc8/kernel/sound/drivers/opl3/snd-opl3-synth.ko needs unknown symbol sprintf
WARNING: /lib/modules/2.6.23.15-137.fc8/kernel/sound/drivers/opl3/snd-opl3-synth.ko needs unknown symbol _spin_lock_irqsave
WARNING: /lib/modules/2.6.23.15-137.fc8/kernel/sound/drivers/opl3/snd-opl3-synth.ko needs unknown symbol mutex_unlock
WARNING: /lib/modules/2.6.23.15-137.fc8/kernel/sound/drivers/opl3/snd-opl3-synth.ko needs unknown symbol del_timer
WARNING: /lib/modules/2.6.23.15-137.fc8/kernel/sound/drivers/opl3/snd-opl3-synth.ko needs unknown symbol __mod_timer
WARNING: /lib/modules/2.6.23.15-137.fc8/kernel/sound/drivers/opl3/snd-opl3-synth.ko needs unknown symbol kmalloc_caches
WARNING: /lib/modules/2.6.23.15-137.fc8/kernel/sound/drivers/snd-mtpav.ko needs unknown symbol strcpy
WARNING: /lib/modules/2.6.23.15-137.fc8/kernel/sound/drivers/snd-mtpav.ko needs unknown symbol free_irq

unknown symbol __kmalloc
WARNING: /lib/modules/2.6.23.15-137.fc8/kernel/sound/synth/emux/snd-emux-synth.ko needs unknown symbol kmalloc_caches

a lttle sample of the errors im getting

big old error huh? any one wanna help?

[Hlingler]

Hello:

Much more info is needed. You obviously are running F8 with a geforce 7150m, but what exactly have you done/tried, and what exactly are the problems/results? BTW, is that an on-board chip, or a card? When you say: "i tried to dl kmod-nvidia", do you really mean that you actually downloaded it, or did you try to install it with yum?

The errors that you posted don't make sense - they appear to be sound-related, not video.

I think that your best option is to follow the HOWTO (see link in my previous post), and post any problems/questions to that thread, where they will get the most attention.

Regards,
V

[venumus]

sorry yeah i used yum to install

it is an on board chip

oh ive followed the how to's

my biggest problem i have to reinstall my driver everytime i reboot. it sux.

i tried posting on anohter thread but it died i belive

[Hlingler]

Hello:

Sounds like your /etc/X11/xorg.conf may not be written correctly. What exactly do you mean: "i have to reinstall my driver everytime i reboot"? Or do you really mean "manually load"? More detail, please....

V

[snm_cal]

It usually helps to know what flavor of Fedora you're running, since this can make a difference.

There is an excellent HOWTO by the guy that builds the Livna nvidia drivers (FireWing1) here: http://forums.fedoraforum.org/showthread.php?t=99285. NOTE the first line (in red) redirecting you to his own website for the latest revisions of the HOWTO for F7/8. I strongly recommend that you consult them (they're actually fairly short and simple). If you have problems after that, you can post to that thread, where FireWing1 will see your post and hopefully respond.

Regards,
V


Thanks A Ton. Definitely this is going to help me. Thanks a lot again.

Regards
Suvransu

[p1ngv1n]

i have nvidia geforce fx 5500 256MB graphic card and i want to know if fedora has drivers for it and if it does how can i install them. because i have installed some drivers but they aren't working properly. So if anyone can help me thanks.

[Hlingler]

i have nvidia geforce fx 5500 256MB graphic card and i want to know if fedora has drivers for it and if it does how can i install them.Yes, and No. Fedora ships with an open-source driver for nvidia chipsets/cards, but it does not provide full functionality for all features of those chipsets/cards. Configuration should be automatic. If you want it, you have to fetch the proprietary driver yourself from a 3rd party, either nvidia binary installers (NOT recommended) or one of several 3rd-party repositories that re-package the driver in RPM format for Fedora. See the link referenced above post. The good news is that your card is supported by the latest driver.because i have installed some drivers but they aren't working properly. So if anyone can help me thanks.What have you installed, and where did you get it?

V

[p1ngv1n]

well i remembered that xorg have same drivers for graphic cards so i found some i pirut something like xorg x11 dr nvidia in the description said that it has drivers for the fx series so i install it but its not good. and what link?

[Hlingler]

well i remembered that xorg have same drivers for graphic cards so i found some i pirut something like xorg x11 dr nvidia in the description said that it has drivers for the fx series so i install it but its not good.Yes, that's the proprietary one that comes from the Livna repository: xorg-x11-drv-nvidia. You also should have installed the matching kmod-nvidia for your current kernel (I'm not sure if the kmod is automatically installed). Some manual configuration may be needed.and what link?This link:There is an excellent HOWTO by the guy that builds the Livna nvidia drivers (FireWing1) here: http://forums.fedoraforum.org/showthread.php?t=99285. NOTE the first line (in red) redirecting you to his own website for the latest revisions of the HOWTO for F7/8. I strongly recommend that you consult them (they're actually fairly short and simple). If you have problems after that, you can post to that thread, where FireWing1 will see your post and hopefully respond.

[p1ngv1n]

thanks all done

[thedude165]

it seems to me that you can't upgrade to a new version of Fedora until a couple of weeks after it is initially released. I upgraded to Fedora 9 and I can get nvidia drivers. I am using Fedora 8 for now and will probably stay in 8 until nvidia releases new drivers. It seems that the last three releases of Fedora had major issues during its early release and finally becomes extremely stable just as the 6 month cycle ends. I wish the Fedora programmers would release the next Fedora release with more stability in mind rather than simply thinking about being cutting edge. I understand that Fedora is the guinea pig for Red Hat but we deserve some stability as loyal users. I will probably get some negative feedback from this post. Just venting my frustration. I get excited when there is a new release and to not have it work properly is discouraging.

[zx5000]

I always go get the proprietary driver from nvidia. This is mostly because I have a quad head configuration.

NVidia is pretty good at keeping their drivers up to date with the kernels.

HTH

[Dan]

it seems to me that you can't upgrade to a new version of Fedora until a couple of weeks after it is initially released. I upgraded to Fedora 9 and I can get nvidia drivers. I am using Fedora 8 for now and will probably stay in 8 until nvidia releases new drivers. It seems that the last three releases of Fedora had major issues during its early release and finally becomes extremely stable just as the 6 month cycle ends. I wish the Fedora programmers would release the next Fedora release with more stability in mind rather than simply thinking about being cutting edge. I understand that Fedora is the guinea pig for Red Hat but we deserve some stability as loyal users. I will probably get some negative feedback from this post. Just venting my frustration. I get excited when there is a new release and to not have it work properly is discouraging.
Ayup! Here comes the heat.

http://fedoraproject.org/wiki/LifeCycle?highlight=%28cycle%29%7C%28life%29

http://fedoraproject.org/wiki/Objectives?highlight=%28objectives%29

Now that that's settled ...

Try coming here and joining a constructive conversation about this issue.

http://forums.fedoraforum.org/forum/showthread.php?t=188693


Dan

[doghousedean]

Hello everyone, im new to fedora and linux but need to get stuck in and learn a new platform. Jumped in and installed Fedora 9 on an IBM xseries x335 with build in ATI rage xl (I think) it was stuck at 800 x 600 and doing my head in, i changed the driver to rage 128 and it boots to CLI mode only. 1) how would i boot the GUI and 2) how do i change the driver from CLI?

Thanks gents

[Hlingler]

Hello everyone, im new to fedora and linux but need to get stuck in and learn a new platform. Jumped in and installed Fedora 9 on an IBM xseries x335 with build in ATI rage xl (I think) it was stuck at 800 x 600 and doing my head in, i changed the driver to rage 128 and it boots to CLI mode only. 1) how would i boot the GUI and 2) how do i change the driver from CLI?

Thanks gents(1) See #2, it needs to be fixed first.
(2) Re-boot. Right after the BIOS loads, you'll see a few short messages flash by: "GRUB loading Stage2" or such, then a screen with Blue-ish background - that's the GRUB bootloader screen. STOP the automatic boot loading by pressing any key. You'll see a list come up with your boot options - in your case, probably just one Fedora kernel and maybe one other entry: "Other". Follow the on-screen instructions to "edit" the boot parameters, and "alter" the boot line to add the number 3 to the end on the kernel line, like so:title Fedora (2.6.24.7-92.fc8)
root (hd0,4)
kernel /vmlinuz-2.6.24.7-92.fc8 ro root=/dev/VolGroup00/LogVol00 rhgb selinux=off agp=off apic=debug init=/sbin/bootchartd 3
initrd /initrd-2.6.24.7-92.fc8.img
title Fedora (2.6.24.5-85.fc8)
root (hd0,4)
kernel /vmlinuz-2.6.24.5-85.fc8 ro root=/dev/VolGroup00/LogVol00 rhgb selinux=off agp=off apic=debug init=/sbin/bootchartd
initrd /initrd-2.6.24.5-85.fc8.img
title Windows XP Media Center Edition
rootnoverify (hd0,0)
chainloader +1
Then press enter, then 'b' to boot. You'll get an otherwise normal boot into run-level 3, which is without GUI/X11. You'll be dumped into a full-screen terminal window on Virtual Terminal #1 (VT1, ALT-CTL-F1) where you can fix things. Log into the terminal as root user. You'll have to edit your /etc/X11/xorg.conf file using a text-mode editor such as VI[M], or even create it if it doesn't exist. You can make it easier on yourself: system-config-display can be used from the VT1, just command: system-config-display, and you'll get another screen with the "Display Manager" GUI. Make changes/settings, you'll be dumped back to VT1 when you press "OK/Apply".

Unfortunately, the Rage XL is a mach64-class chipset, and Fedora Project has blocked the driver from inclusion into the OS releases for years due to (long-since closed) "security" concerns. I've got an open Bug Report/Feature Request to get it added in: https://bugzilla.redhat.com/show_bug.cgi?id=448346. Not only that, but for F9, the mach64 driver has been split out from the general ATI driver wrapper into it's own driver package - which doesn't even exist yet in Fedora!

Short story: you're screwed. You can try to tag the driver as 'ati' and see if the generic ati driver will run that chipset. If not (probably not), you're stuck with the uber-generic 'vesa' driver, which will probably not be able to give you much better than what you got: 800x600 resolution. Sorry. Or, forget F9 for now, try F8, see my How-To in the "Guides and How-Tos" froum where you can get the 3D/DRI mach64 driver for F8 - it is well tested and works well.

Available resolution(s) will depend mostly on available VRAM. How much VRAM do you have with that old thing? You can double available resolutions by dropping color depth to 16 bpp, which I find to be adequate (but be aware that many newer games & stuff won't run and/or look good at 16 bpp). My oldest box has ATI Rage Pro Turbo AGP 2X, 4 MB VRAM, 832x624 @ 16 bpp is max resolution, and it's not so bad if you adjust all fonts/icon sizes etc.http://www.fedoraforum.org/gallery/showimage.php?i=4327&catid=member&imageuser=76172&cutoffdate=all http://www.fedoraforum.org/gallery/showimage.php?i=4328&catid=member&imageuser=76172&cutoffdate=all Same chipset with 8 MB VRAM I got 1024x768 @ 16 bpp. Try to set your display settings accordingly, i.e., do NOT select the max resolution of the monitor, but the max you think the chipset an handle with available VRAM. Use 16 bpp color depth for now to get the highest possible resolution.

Good Luck, and Welcome to Fedora!
V

[doghousedean]

WOW!

Thanks for the response, I will go over the details when I get home.

Thanks again.

[Hlingler]

OK, I got the 2D mach64 driver, 3D mesa DRI drivers and kernel modules built for F9-x86 (kernel-2.6.25.3-18.fc9.i686 only so far) and it's working - with a few minor glitches. I think I had a slightly bad build, and there's some minor warnings, and glxinfo says "No" direct rendering, but it's quite obviously working based on glxgears 35-40 FPS >> 125 FPS and also /var/log/Xorg.0.log shows all green flags. See my "How-To" for "Direct Rendering for Older Videocards" in the "Guides and How-Tos" forum. I'll have the RPMs and other files uploaded shortly, and revise the How-To.

V

EDIT: OK, I must have screwed up the build just a little because it was looking in the wrong folder for the driver - a simple sym-link from /usr/local/lib/dri/mach64_dri.so =>> /usr/lib/dri/mach64_dri.so fixed everything (driconf and glxinfo). Will fix this next build.

[Kre]

Hey all. I'm using an IBM T41 with an ATI Radeon RV250 [Mobility FireGL 9000] on it. Now, it's working pretty well, but i prefer using the GPU also, not only my CPU. I found on ati website the drivers i think i need, but when trying to install them i get:

Detected configuration:
Architecture: i686 (32-bit)
which: no XFree86 in (/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lib/ccache:/usr/local/bin:/usr/bin:/bin:/home/adrian/bin)
X Server: unable to detect
Removing temporary directory: fglrx-install

my F9 is up to date and i don't know what to do next.

[Gonche]

Hi all,

I have read all the posts and will describe my situation as it may sound familiar,
At present I am running Fedora 9, X1950Pro Graphics Card, 1212M Sound Card, 3GHZ single core P4..

I cant boot into my box because X crashes, the same problem that you are all experiencing. I boot the box into text mode by editing the GRUB command-line to 3 on the end, and then login as root..

I have edited the xorg.conf and changed the resolution to 1024x768 and have checked that the device description is called 'radeon' so looks like its picked it up and found it.

I reboot and still the same, if i do the system-config-display command it also dosent start up the graphics. I have installed the livna rpms and done an yum update but i cannot see a ati kmod or think of any other way to change the settings to get into X. If i run startx from the cmdline it does the same thing.

Any ideas or help would be greatly appreciated.

[robert-e]

Hi,
I just had a re-read of Leigh's How-To for Ati on F8. Noted to run "glxinfo" to check for DRI, so did that, and yes, got DRI, but at the bottom of the listing output, it says "segmentation fault". That does not look good. I read Leigh's thread again, and also this one, and don't see this mentioned. Yet, everything seems to be working. Any ideas?
Thanks,
Bob

Added: I googled this, and it seems this may be result of the wrong driver; but I think the installed driver is the correct one for this Toshiba laptop 32 bit, with onboard ati 9600 vid.
B

[Hlingler]

Hi,
I just had a re-read of Leigh's How-To for Ati on F8. Noted to run "glxinfo" to check for DRI, so did that, and yes, got DRI, but at the bottom of the listing output, it says "segmentation fault". That does not look good. I read Leigh's thread again, and also this one, and don't see this mentioned. Yet, everything seems to be working. Any ideas?
Thanks,
Bob

Added: I googled this, and it seems this may be result of the wrong driver; but I think the installed driver is the correct one for this Toshiba laptop 32 bit, with onboard ati 9600 vid.
BI don't see that chipset covered by the ATI fglrx driver, assuming it's either Mobility Radeon or integrated/on-board: http://ati.amd.com/support/driver.html
Care to check or give more detailed info on the hardware ?

V

[robert-e]

Hi Hlingler,
Thanks for replying. This laptop is a Tsohiba Satellite with hyperthreading cpu. The video is onboard, not plugin mini pci. I hope this helps; if you need more, let me know what, and I will post it.
Bob

[root@localhost rob]# lspci | grep ati
01:05.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9 600 M10]

[Hlingler]

OK, so a quick check of that ATI automated driver finder says that "Mobility Radeon 9600" is supported by latest fglrx driver (REV. 8.6). Also: "hyperthreading cpu": but only one CPU, correct ? All recent kernels are SMP-aware and capable.

If you installed the ATI proprietary fglrx driver as per Leigh's How-To, and you're runing F8, the seg-fault of glxinfo should not happen. Try the glxgears test and see if it runs OK or gives any problems.

If F9: There was a recent update of the Xorg server, glx-utils (provides the glxinfo and glxgears), and some other X11 stuff. Did you apply all of them? If so, could be a problem in the (still pre-release) X11/Xorg code.

In any case, this may not be any serious problem (or none at all), since glxinfo clearly reports DRI enabled and working before exiting. If you really want a good benchmark of performance, graphical or otherwise, install package 'hardinfo' ("System Profiler and BenchMark") and run the FBENCH (FPU RayTracing) test, then synchronize results with the on-line database to see how your machine stacks up. And/or run some OpenGL apps to test performance.

V

[robert-e]

OK, so a quick check of that ATI automated driver finder says that "Mobility Radeon 9600" is supported by latest fglrx driver (REV. 8.6). Also: "hyperthreading cpu": but only one CPU, correct ? All recent kernels are SMP-aware and capable.
--Yes, only one cpu.

If you installed the ATI proprietary fglrx driver as per Leigh's How-To, and you're runing F8, the seg-fault of glxinfo should not happen. Try the glxgears test and see if it runs OK or gives any problems.
--I used yumex to install the ati fglrx driver. I dont know how the do the glxgears test. I did google that, but I guess it is so elementary, that no one addresses how to.

If F9: There was a recent update of the Xorg server, glx-utils (provides the glxinfo and glxgears), and some other X11 stuff. Did you apply all of them? If so, could be a problem in the (still pre-release) X11/Xorg code.
--No, it is F8. And all the updates are done...Yumex update screen is empty. I think glx-utils is installed, but I will double check that.

In any case, this may not be any serious problem (or none at all), since glxinfo clearly reports DRI enabled and working before exiting. If you really want a good benchmark of performance, graphical or otherwise, install package 'hardinfo' ("System Profiler and BenchMark") and run the FBENCH (FPU RayTracing) test, then synchronize results with the on-line database to see how your machine stacks up. And/or run some OpenGL apps to test performance.
--I will also install "hardinfo" package. I have google earth working, and it seems to work much the same as it did in XP. I think that is an OpenGL app.
--Since the driver seems to be working okay, I am not hung up on this; but am trying to learn. Do you need my xorg.conf?
Regards,
Bob

[robert-e]

Hi Hlingler,
Okay...glx-utils was/is installed. Also installed hardinfo, and ran the Ray Tracing test...reported 25.5 compared to about 40 for a 1.5 gHz Celeron. I also check the "Display" in hardinfo utility, and it also reports OpenGl as running. So I guess it is all normal, except the the Segmentation Fault error. I imagine that is some sort of bad memory write to the agp shared memory? Oh yes, if you want to see the fglrx stuff, I had posted a screen dump of that stuff the other day, under Hardware, in the forum. Thread title was http://forums.fedoraforum.org/showthread.php?t=192446
Thanks,
Bob

[Hlingler]

To run glxgears, same as running glxinfo: open a terminal (as any normal user) and type:
glxgears

Start glxgears with no other load on the system, as it will max out available resources. You'll see a pop-up window appear with three spinning gears. Don't hide/cover/minimize the gearbox nor even put the cursor on it. The output in frames-per-second (FPS) will be shown in 5-second chunks in the parent terminal. Let run 30-60 seconds before closing/killing. Observe and memorize output - there will be a quiz later. :D

However, if GoogleEarth runs, and seems to perform as well as in WinXP, then you're good to go - that thing is a DRI-killer, so if it works, ignore the "errors" for now from glxinfo and enjoy. I see no real point in looking into your Xorg.0.log, xorg.conf or otherwise unless problems surface down the road. You may still wish to install 'hardinfo' and generate a report for later eference.

Enjoy the Show,
V

[robert-e]

Hi again Hlingler,
Geez, do I feel dumb...I was looking all over in the menu for something that would run that. Anyway, it is reporting a number of 2690 +/- 10. I have no idea what that compares to. This is a 3.4 gHz machine, if that helps you make a guesstimate.
However, if you think I am worrying about nothing, we can just leave this. Maybe it is one of those things that just gets fixed with some new update along the way.
Thank you for spending your time on this. I think I will go and pour myself a double Lambs right now.
Regards,
Bob

[Hlingler]

glxgears is a bad bechmark tool, but 2690 +/- sounds pretty damn good to me! I've got an NVidia 6150 LE and the best I ever got was ~3000 FPS. The absolute top-of-the-line cards nowdays may get close to say 30,000 FPS. But your output should be fast enough for almost anything....

Pour your double Lambs, sit down, and enjoy your hardware-accelerated 3D/DRI graphics and PC - if there's any real problem with anything, either an update will fix it, or you'll find out more soon enough....

V

[luiscar2001]

Something pretty strange happens to my fedora 9 installation. I have isntalled the propietary driver from NVIDIA via the LIVNA repository. When booting up and entering the GNOME desktop, the Rendering is not activated.

In order to have it activated, I have to:
1. initiate a sesion in text mode. I go to a console and type sudo /sbin/init 3
2. and then startx.

et voilà when I ask the Livna configaration it answers: Direct Rendering: YES.
Nevertheless, if in that mode I ask from the console glxinfo it says Direct Rendering: NO.

Furthermore, if I stop X again (logout) /sbin/init 5, I ask Livna-settigns and answers Direct Rendering: NO

What is it different from init 5 and startx X that prevents the X server of getting Direct Rendering capability?

By the way, I have already changed the permissions of /dev/nvidia* to 666.

[Yaung64]

Tell me if this should go in the installation forum...

When I try to install FC9, my monitor, right after the verification disk screen, it says that it is out of range.
My monitor is a HP vs17x, so it can only go up to 1280x1024 60hz.
My graphics card is a Nvidia GeForce 8500 GT.
The problem is that the setup immediately goes to 1280x1024 70hz or something. That means that I can't even use the graphical install user interface! I don't think there's any solution for this, but... I really don't want to have to use the command line all the time, since I suck at it (uses windows).

P.S. Yes, I have installed using the text based installer. The problem is that even after I install using the text based version, then the welcome screen immediately goes to the same mode as before.

[wayland]

Anyone having problems with multi-head with multiple video cards, see the whole thread at:

http://lists.freedesktop.org/archives/xorg/2008-December/040961.html

[swatchpuppy]

Hello

I have a sony vaio sz61MN that have two graphic cards, one intel in stamina mode and one nvidia for speed mode. The intel card works fine, but when i install nvidia-kmod some files of the xlg are replaced and the intel card stops working. I can't switch modes that way. How can i solve this?

Thanks in advance,
SwatchPuppy

[wayland]

https://bugs.freedesktop.org/show_bug.cgi?id=18160

I've had no success using the "nvidia" (binary) module with two screen cards. The "nv" (open source) one used to work in Fedora 8 for me, and others report up until Fedora 8. Someone's finally gotten around to doing some debugging on the thing (see bug link above), but unfortunately no resolution yet.

[geribek]

Hello!

I have an ATI HD2400 video card a samsung SyncMaster 2243NW screen. I've used the fglrx driver successfully with the max. resolution of the screen, which is 1680*1050. That was nice and wide and sweet and everything, until I had an update this morning..
I updated the fglrx driver I think, and it ruined my X system.. So I reinstalled every fglrx package, now the 3D and compiz works, but the maximum resolution I can get my screen is 1440*900, which is far away from 1680*1050:(

Has everyone a solution for this kind of problem? Help please, I miss my resolution!!:)

[wesam2004]

hello
i using fedora core 10 but graphics card not working and i can't playing desktop effects

hardware :

laptop HP Pavilion

processor 2000 Core 2 Duo
RAM 3 GB
Graphics Card NIVIDIA 256 MB

Please help

[Quiksilver0A]

Hello, Im a newbie in getting drivers to work. Sorry if I shouldn't be posting in this thread, but I have a problem..

I have fedora 10, with an NVIDIA GeForce Go 6200 TE, Kernel 2.6.27.9-159.fc10.i686, 2.00Ghz processor.

I have searched sooooo many threads and guides its not funny. I have tried to run the NVIDIA 'run' file, which returns an error stating it cannot build the kernel module. (Log file attached).


When I run
glzgears
the gears animation pops up and (when maximised) I get a value of about 20fps. (However, when I try to run games, they seem to be running at 1fps - seriously)


# glxinfo | grep direct -i
direct rendering: Yes
I am assuming this is 2D acceleration?

# glxinfo | grep OpenGL -i
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 7.3-devel
OpenGL shading language version string: 1.10
OpenGL extensions:

Other guides say that my version should return something like 'NVIDIA Corporation' and not the Mesa stuff.

When I try enabling Desktop Effects I get a completely white screen, but after a couple of seconds it exits and allows me to continue (with effects disabled).

Im not sure if this is out of the ordinary, but I do not have a xorg.conf file in /etc/X11 . Hope someone can help me, im almost ready to jump on my computer :o

any help is appreciated! thanks

[agapetos]

Hello,
I have ATI Radeon 3850, and 19'' wide screen ASUS monitor. Since I installed fedora 10 i386, and "yum update"-ed all drivers I still cant get normal picture. My picture is stretched. When I look at a picture of circle, I see it as ellipse. My curent resolution is 1280x1024. Beside this resolution I can choose 1152x864 (and when I choose it, my colors get realy ugly - only 16 colors I think), Also I can choose 1024x768, 800x600, 640x480 and 720x400.
What do I need to do in order that my screen looks normal (like it looked under windows before I installed fedora?

[agapetos]

Here is an update on my situation: I played a movie, and when I put it on a full screen, the movie automaticly recognized the correct resolution and was not stretched.

[agapetos]

ALRIGHT! A friend of mine just helped me fix the problem with screen - He changed the xorg.conf, so that there is a recommended resolution that did not exist before. Problem solved

[cksmuck]

Try to Google "Autoten"! This guy has set up a repository with some much needed Nvidia and Compiz-fusion packages for drivers. I am a complete NOOB and now have OpenGL graphics with the desktop cube and my sound works. I am using a HP Pavilion dv7 1285x with Nvidia 9600m and IDT HD Audio!!!!!:):):):):):)

[amrmesh]

Hi,
I Have a laptop with Nvidia GeForce 9500M (GF 9400MG + GF 9200MGS) GPU, But the fedora don't run in graphic mode.
can anybody help me?

[aryan007d]

if you have problem with your graphic card
please refer to this page
https://www.redhat.com/archives/fedora-test-list/2006-February/msg01565.html


actually i hav the following specifications:
GA-73VM-S2 MOTHERBOARD,nvidia7050/610i,1gb ram,p4 intel,hdd 80Gb

When i tried f10 live cd to boot it boots till the logo of f10 and further proceeds but does not displays anything only the cursor goes on blinking.
What should i do does f11 will solve my problem bcoz i have heard that it has many different things or else a full version f10 may also solve my problem

[saej]

Hi
i installed FC11
my laptop graphic card is ATI and i can't install this driver...
but i update my fedora and update my kernel and i installed kernel-devel and i can't install two package (rpmfusion-nonfree-release-11.90-1.noarch || rpmfusion-free-release-11.90-1.noarch) but when i using yum install kmod-fglrx , it can't install and it have an error!!!

Please help me!!!?

TNX

[windtalker]

There seems to be a problem with the nvidia driver installer for the geforce.
I have a geforce 7300 gt.
I installed Fedora 11 on a box a few weeks ago and the autoten did fine with it.
I install it to an identical box and evidently, according to the verbose login, the kernel module isn't being built.

[MechEng22]

Hi, i have not the same exact problem but similar, My computer has the following specs...

Gigabyte MOBO
AMD Quad Core Black Edition 2.6GHz
4GB Ram
Nvidia GTS 250 OC graphics card
Dual Os: Windows xp 32 bit on one HDD, Linux on a completely Separate HDD. HDD Boot order in Bios is how i determine what i want to boot.

1 Sceptre Monitor (DVI HOOKUP)
1 ACER Monitor (DVI-HOOKUP but through a VGA-DVI adapter, monitor only supports VGA)

This is my issue;

I installed Fedora 11 on my system a few weeks back and to my amazement i didnt even have to configure Fedora for the dual display setup i have it automatically set it up for me when i installed it. Anyways i had to reinstall the Fedora 11 operating system and second time around it only set up my single display the other was not configured.

Now i went ahead and installed the latest Nvidia 64 bit driver for my system and on reboot, only the second monitor showed an image, and the main monitor had no image, but on the second it was obviously configuring it as the second because i saw no login screen (i think would be on the first dispay if it were actually displaying an image). From here i started editing and tweeking my xconfig file to fix the dual display, tried the option twinview, and also the connectedmonitor with my main as a Digital and the other as a CRT. I placed these options under my monitor section of the config file. (also if this is any help; When i move to a shell ctrl-alt-F2 it turns off the second dispay, turns on the first and gives me the shell login there.) Does it revert back to a different config file when in a Shell? why would it switch like this?

Anyways, After those xconfig modifications and rebooting, i get to the Fedora 11 loading screen, then after that it sounds like my graphics card is now stuck in some weird hardware bug loop because i see no image on either screen and i hear my graphics card fan spool up and slow down, spool up and slow down. Also, now i cant get into a shell, when i try crt alt F1 or F2 to get into a shell which usually always works it does nothing. I get some response when i go to shutdown manually as it stops the loop and starts a shell but that doesnt help because then it gives me a shell but shuts off 2 secs later. That is why i can't just post my xconfig file in the forum BTW.

1. Is there anyway to recover or gain access to a shell from my situation, boot from a fedora cd and get into a shell so i can nvidia-xconfig --force-generate a new file?

2. Any advice or help on how to config the dual display setup for my card?

3. I know that Fedora thinks that all VGA hook ups are CRT's, but if i am using a VGA adapter in a dual DVI setup then are they still both considered digital to linux?

4. Do i need to specifiy the PCI address to the Graphics card in the xconfig file?

5. Is there a special section (I.E. "module") that these option commands should be placed.

Anyone with a similar dual display setup please post your xconfig file, i would love to be able to figure this out before i blow my head off with a 12 gauge.

Extremely new to Linux, doing my best to Learn...
Thank you for any Reply's. BEST FEDORA FORUM ON THE NET!

[MechEng22]

I just read up on this Bug, could this be the cause of my problems, as i have seen other xconfig files where under the device section for the graphics card they specify there memory amount this is the bug i am talking about

Xorg fails to start when using the nvidia kernel module
link to this item - Bugzilla: #489078

Some users have reported that when attempting to use the "nvidia" kernel module (either the official installer or kmod-nvidia*) Xorg will fail to start properly. The end result, Fedora 11 boots to a black screen. Inspection of dmesg may reveal many messages similar to:

$ dmesg | grep vmap
vmap allocation for size 4198400 failed: use vmalloc=<size> to increase size.
vmap allocation for size 4198400 failed: use vmalloc=<size> to increase size.

A workaround is to add an entry to your kernel line in /etc/grub.conf that includes the amount of video memory on your nVidia card, for example for a 128 MB Geforce 8400 GS you would append the following:

vmalloc=128MB

[Hlingler]

See: http://forums.fedoraforum.org/showthread.php?t=204752

Note that if you have already installed the NVIDIA binary driver, you would have to remove it before installing any equivalent RPMs, otherwise you'd basically be "double-installing", and Bad Things could happen.

V

[MechEng22]

Okay i don't think i did install that but i know i didnt add the module section to my xorg file so i will reinstall fedora 11 (as i still can't find a solution to fixing my current error) and try to install the drivers again. I will still have the problem with setting up the dual displays though.

If anyone knows what areas i need to modify on the xconfig file please let me know;

as of now i know i have to add the module section with links to the nvidia drivers, also know i have to set up the connectedmonitor option and set up a new monitor section for the second monitor. Do i also have to specify the dual setup in the layout section?

[saej]

Hi

how to resolve ATI driver in FC11???

TNX

[paulkruger]

I am new to this but here is the situation.

I used the Live CD to install F.11 and all went fine. I had a great screen resolution so assume it found and used the proper driver for my ATI Radeon 128 Pro card. Then after screen froze due to Firefox I had to exit to console and reboot. After reboot my resolution has dropped to 800 x 600 and I can't find any way to restore it to the former resolution.

( Side note, I just changed this install from Ubuntu which I did not like but which had exactly the same issue, lost or corrupted driver? )

Any help to restore to high resolution is appreciated.

Thanks.

[paulkruger]

Since the original installation had the correct video and the screen resolution dropped after the first reboot, is there a way to restore the initial video settings as provided on install?

For some reason on reboot F.11 messed up an good configuration.

[Hlingler]

System software fully up-to-date ?

Please upload the following file in entirety to pastebin.com and post the link here, we'll see what's up:
/var/log/Xorg.0.log

V

P.S. Also: post results of command:
uname -a

[paulkruger]

System software fully up-to-date ?

Please upload the following file in entirety to pastebin.com and post the link here, we'll see what's up:
/var/log/Xorg.0.log

V

P.S. Also: post results of command:
uname -a

I just started an update to see if there is anything that needs it. Will report back after that is done.

Thanks:)

[paulkruger]

I just started an update to see if there is anything that needs it. Will report back after that is done.

Thanks:)

Content of log file are split into four posts because of limits imposed by the board:



X.Org X Server 1.6.1.901 (1.6.2 RC 1)
Release Date: 2009-5-8
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.18-128.1.6.el5 i686
Current Operating System: Linux localhost.localdomain 2.6.29.5-191.fc11.i586 #1 SMP Tue Jun 16 23:11:39 EDT 2009 i686
Kernel command line: ro root=/dev/mapper/VolGroup-lv_root rhgb quiet
Build Date: 18 May 2009 02:47:59PM
Build ID: xorg-x11-server 1.6.1.901-1.fc11
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 9 07:11:54 2009
(II) Loader magic: 0x640
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(++) using VT number 1

(--) PCI:*(0@1:0:0) ATI Technologies Inc Rage 128 Pro Ultra TF rev 0, Mem @ 0xf8000000/67108864, 0xff8fc000/16384, I/O @ 0x0000ec00/256, BIOS @ 0x????????/131072
(==) Using default built-in configuration (30 lines)
(==) --- Start of built-in configuration ---
Section "Device"
Identifier "Builtin Default ati Device 0"
Driver "ati"
EndSection
Section "Screen"
Identifier "Builtin Default ati Screen 0"
Device "Builtin Default ati Device 0"
EndSection
Section "Device"
Identifier "Builtin Default vesa Device 0"
Driver "vesa"
EndSection
Section "Screen"
Identifier "Builtin Default vesa Screen 0"
Device "Builtin Default vesa Device 0"
EndSection
Section "Device"
Identifier "Builtin Default fbdev Device 0"
Driver "fbdev"
EndSection
Section "Screen"
Identifier "Builtin Default fbdev Screen 0"
Device "Builtin Default fbdev Device 0"
EndSection
Section "ServerLayout"
Identifier "Builtin Default Layout"
Screen "Builtin Default ati Screen 0"
Screen "Builtin Default vesa Screen 0"
Screen "Builtin Default fbdev Screen 0"
EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default ati Screen 0" (0)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default ati Device 0"
(==) No monitor specified for screen "Builtin Default ati Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (1)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default fbdev Screen 0" (2)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default fbdev Device 0"
(==) No monitor specified for screen "Builtin Default fbdev Screen 0".
Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(==) FontPath set to:
catalogue:/etc/X11/fontpath.d,
built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable AllowEmptyInput.
(II) No APM support in BIOS or kernel
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0

[paulkruger]

Part two:

(II) Loading extension SELinux
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "ati"
(II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
(II) Module ati: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 6.12.2
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "r128"
(II) Loading /usr/lib/xorg/modules/drivers//r128_drv.so
(II) Module r128: vendor="X.Org Foundation"
compiled for 1.6.0, module version = 6.8.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers//vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
compiled for 1.6.0, module version = 2.2.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "fbdev"
(II) Loading /usr/lib/xorg/modules/drivers//fbdev_drv.so
(II) Module fbdev: vendor="X.Org Foundation"
compiled for 1.6.0, module version = 0.4.0
ABI class: X.Org Video Driver, version 5.0
(II) R128: Driver for ATI Rage 128 chipsets:
ATI Rage 128 Mobility M3 LE (PCI), ATI Rage 128 Mobility M3 LF (AGP),
ATI Rage 128 Mobility M4 MF (AGP), ATI Rage 128 Mobility M4 ML (AGP),
ATI Rage 128 Pro GL PA (PCI/AGP), ATI Rage 128 Pro GL PB (PCI/AGP),
ATI Rage 128 Pro GL PC (PCI/AGP), ATI Rage 128 Pro GL PD (PCI),
ATI Rage 128 Pro GL PE (PCI/AGP), ATI Rage 128 Pro GL PF (AGP),
ATI Rage 128 Pro VR PG (PCI/AGP), ATI Rage 128 Pro VR PH (PCI/AGP),
ATI Rage 128 Pro VR PI (PCI/AGP), ATI Rage 128 Pro VR PJ (PCI/AGP),
ATI Rage 128 Pro VR PK (PCI/AGP), ATI Rage 128 Pro VR PL (PCI/AGP),
ATI Rage 128 Pro VR PM (PCI/AGP), ATI Rage 128 Pro VR PN (PCI/AGP),
ATI Rage 128 Pro VR PO (PCI/AGP), ATI Rage 128 Pro VR PP (PCI),
ATI Rage 128 Pro VR PQ (PCI/AGP), ATI Rage 128 Pro VR PR (PCI),
ATI Rage 128 Pro VR PS (PCI/AGP), ATI Rage 128 Pro VR PT (PCI/AGP),
ATI Rage 128 Pro VR PU (PCI/AGP), ATI Rage 128 Pro VR PV (PCI/AGP),
ATI Rage 128 Pro VR PW (PCI/AGP), ATI Rage 128 Pro VR PX (PCI/AGP),
ATI Rage 128 GL RE (PCI), ATI Rage 128 GL RF (AGP),
ATI Rage 128 RG (AGP), ATI Rage 128 VR RK (PCI),
ATI Rage 128 VR RL (AGP), ATI Rage 128 4X SE (PCI/AGP),
ATI Rage 128 4X SF (PCI/AGP), ATI Rage 128 4X SG (PCI/AGP),
ATI Rage 128 4X SH (PCI/AGP), ATI Rage 128 4X SK (PCI/AGP),
ATI Rage 128 4X SL (PCI/AGP), ATI Rage 128 4X SM (AGP),
ATI Rage 128 4X SN (PCI/AGP), ATI Rage 128 Pro ULTRA TF (AGP),
ATI Rage 128 Pro ULTRA TL (AGP), ATI Rage 128 Pro ULTRA TR (AGP),
ATI Rage 128 Pro ULTRA TS (AGP?), ATI Rage 128 Pro ULTRA TT (AGP?),
ATI Rage 128 Pro ULTRA TU (AGP?)
(II) VESA: driver for VESA chipsets: vesa
(II) FBDEV: driver for framebuffer: fbdev
(II) Primary Device is: PCI 01@00:00:0
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(WW) Falling back to old probe method for vesa
(WW) Falling back to old probe method for fbdev
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/lib/xorg/modules/linux//libfbdevhw.so
(II) Module fbdevhw: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 0.0.2
ABI class: X.Org Video Driver, version 5.0
(EE) open /dev/fb0: No such file or directory
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[8] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[10] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) R128(0): PCI bus 1 card 0 func 0
(II) R128(0): Creating default Display subsection in Screen section
"Builtin Default ati Screen 0" for depth/fbbpp 24/32
(==) R128(0): Depth 24, (--) framebuffer bpp 32
(II) R128(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) R128(0): Default visual is TrueColor
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 0.1.0
ABI class: X.Org Video Driver, version 5.0
(II) R128(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(==) R128(0): RGB weight 888
(II) R128(0): Using 8 bits per RGB (8 bit DAC)
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
ABI class: X.Org Video Driver, version 5.0
(II) R128(0): initializing int10
(II) R128(0): Primary V_BIOS segment is: 0xc000
(--) R128(0): Chipset: "ATI Rage 128 Pro ULTRA TF (AGP)" (ChipID = 0x5446)
(--) R128(0): Linear framebuffer at 0xf8000000
(--) R128(0): MMIO registers at 0xff8fc000
(--) R128(0): VideoRAM: 32768 kByte (128-bit SDR SGRAM 1:1)
(**) R128(0): Using external CRT for display
(II) R128(0): Primary Display == Type 3
(WW) R128(0): Can't determine panel dimensions, and none specified.
Disabling programming of FP registers.
(II) R128(0): PLL parameters: rf=2950 rd=65 min=12500 max=35000; xclk=13400
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.1.0
ABI class: X.Org Video Driver, version 5.0

[paulkruger]

Part Three:


(II) R128(0): VESA BIOS detected
(II) R128(0): VESA VBE Version 2.0
(II) R128(0): VESA VBE Total Mem: 32768 kB
(II) R128(0): VESA VBE OEM: ATI RAGE128
(II) R128(0): VESA VBE OEM Software Rev: 1.0
(II) R128(0): VESA VBE OEM Vendor: ATI Technologies Inc.
(II) R128(0): VESA VBE OEM Product: R128
(II) R128(0): VESA VBE OEM Product Rev: 01.00
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) R128(0): VESA VBE DDC supported
(II) R128(0): VESA VBE DDC Level none
(II) R128(0): VESA VBE DDC transfer in appr. 2 sec.
(II) R128(0): VESA VBE DDC read failed
(==) R128(0): Using gamma correction (1.0, 1.0, 1.0)
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Module "i2c" already built-in
(II) R128(0): I2C bus "DDC" initialized.
(II) R128(0): I2C device "DDC:E-EDID segment register" registered at address 0x60.
(II) R128(0): I2C device "DDC:ddc2" registered at address 0xA0.
(EE) R128(0): No DFP detected
(II) R128(0): <default monitor>: Using default hsync range of 31.50-37.90 kHz
(II) R128(0): <default monitor>: Using default vrefresh range of 50.00-70.00 Hz
(WW) R128(0): Unable to estimate virtual size
(II) R128(0): Clock range: 12.50 to 350.00 MHz
(II) R128(0): Not using default mode "640x350" (vrefresh out of range)
(II) R128(0): Not using default mode "320x175" (vrefresh out of range)
(II) R128(0): Not using default mode "640x400" (vrefresh out of range)
(II) R128(0): Not using default mode "320x200" (vrefresh out of range)
(II) R128(0): Not using default mode "720x400" (vrefresh out of range)
(II) R128(0): Not using default mode "360x200" (vrefresh out of range)
(II) R128(0): Not using default mode "640x480" (vrefresh out of range)
(II) R128(0): Not using default mode "320x240" (vrefresh out of range)
(II) R128(0): Not using default mode "640x480" (vrefresh out of range)
(II) R128(0): Not using default mode "320x240" (vrefresh out of range)
(II) R128(0): Not using default mode "640x480" (hsync out of range)
(II) R128(0): Not using default mode "320x240" (hsync out of range)
(II) R128(0): Not using default mode "800x600" (hsync out of range)
(II) R128(0): Not using default mode "400x300" (hsync out of range)
(II) R128(0): Not using default mode "800x600" (hsync out of range)
(II) R128(0): Not using default mode "400x300" (hsync out of range)
(II) R128(0): Not using default mode "800x600" (hsync out of range)
(II) R128(0): Not using default mode "400x300" (hsync out of range)
(II) R128(0): Not using default mode "1024x768" (vrefresh out of range)
(II) R128(0): Not using default mode "512x384" (vrefresh out of range)
(II) R128(0): Not using default mode "1024x768" (hsync out of range)
(II) R128(0): Not using default mode "512x384" (hsync out of range)
(II) R128(0): Not using default mode "1024x768" (hsync out of range)
(II) R128(0): Not using default mode "512x384" (hsync out of range)
(II) R128(0): Not using default mode "1024x768" (hsync out of range)
(II) R128(0): Not using default mode "512x384" (hsync out of range)
(II) R128(0): Not using default mode "1024x768" (hsync out of range)
(II) R128(0): Not using default mode "512x384" (hsync out of range)
(II) R128(0): Not using default mode "1152x864" (hsync out of range)
(II) R128(0): Not using default mode "576x432" (hsync out of range)
(II) R128(0): Not using default mode "1280x960" (hsync out of range)
(II) R128(0): Not using default mode "640x480" (hsync out of range)
(II) R128(0): Not using default mode "1280x960" (hsync out of range)
(II) R128(0): Not using default mode "640x480" (hsync out of range)
(II) R128(0): Not using default mode "1280x1024" (hsync out of range)
(II) R128(0): Not using default mode "640x512" (hsync out of range)
(II) R128(0): Not using default mode "1280x1024" (hsync out of range)
(II) R128(0): Not using default mode "640x512" (hsync out of range)
(II) R128(0): Not using default mode "1280x1024" (hsync out of range)
(II) R128(0): Not using default mode "640x512" (hsync out of range)
(II) R128(0): Not using default mode "1600x1200" (hsync out of range)
(II) R128(0): Not using default mode "800x600" (hsync out of range)
(II) R128(0): Not using default mode "1600x1200" (hsync out of range)
(II) R128(0): Not using default mode "800x600" (hsync out of range)
(II) R128(0): Not using default mode "1600x1200" (hsync out of range)
(II) R128(0): Not using default mode "800x600" (hsync out of range)
(II) R128(0): Not using default mode "1600x1200" (hsync out of range)
(II) R128(0): Not using default mode "800x600" (hsync out of range)
(II) R128(0): Not using default mode "1600x1200" (hsync out of range)
(II) R128(0): Not using default mode "800x600" (hsync out of range)
(II) R128(0): Not using default mode "1792x1344" (hsync out of range)
(II) R128(0): Not using default mode "896x672" (hsync out of range)
(II) R128(0): Not using default mode "1792x1344" (hsync out of range)
(II) R128(0): Not using default mode "896x672" (hsync out of range)
(II) R128(0): Not using default mode "1856x1392" (hsync out of range)
(II) R128(0): Not using default mode "928x696" (hsync out of range)
(II) R128(0): Not using default mode "1856x1392" (hsync out of range)
(II) R128(0): Not using default mode "928x696" (hsync out of range)
(II) R128(0): Not using default mode "1920x1440" (hsync out of range)
(II) R128(0): Not using default mode "960x720" (hsync out of range)
(II) R128(0): Not using default mode "1920x1440" (hsync out of range)
(II) R128(0): Not using default mode "960x720" (hsync out of range)
(II) R128(0): Not using default mode "832x624" (hsync out of range)
(II) R128(0): Not using default mode "416x312" (hsync out of range)
(II) R128(0): Not using default mode "1400x1050" (hsync out of range)
(II) R128(0): Not using default mode "700x525" (hsync out of range)
(II) R128(0): Not using default mode "1400x1050" (hsync out of range)
(II) R128(0): Not using default mode "700x525" (hsync out of range)
(II) R128(0): Not using default mode "1920x1440" (hsync out of range)
(II) R128(0): Not using default mode "960x720" (hsync out of range)
(II) R128(0): Not using default mode "2048x1536" (hsync out of range)
(II) R128(0): Not using default mode "1024x768" (hsync out of range)
(II) R128(0): Not using default mode "2048x1536" (hsync out of range)
(II) R128(0): Not using default mode "1024x768" (hsync out of range)
(II) R128(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) R128(0): Not using default mode "1024x768" (hsync out of range)
(--) R128(0): Virtual size is 800x600 (pitch 800)
(**) R128(0): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) R128(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
(**) R128(0): *Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(II) R128(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
(**) R128(0): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
(II) R128(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
(**) R128(0): *Default mode "400x300": 20.0 MHz, 37.9 kHz, 60.3 Hz (D)
(II) R128(0): Modeline "400x300"x60.3 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (37.9 kHz)
(**) R128(0): *Default mode "400x300": 18.0 MHz, 35.2 kHz, 56.3 Hz (D)
(II) R128(0): Modeline "400x300"x56.3 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (35.2 kHz)
(**) R128(0): *Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D)
(II) R128(0): Modeline "320x240"x60.1 12.59 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (31.5 kHz)
(==) R128(0): DPI set to (96, 96)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/lib/xorg/modules//libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.2.1
ABI class: X.Org Video Driver, version 5.0
(II) Loading sub module "shadowfb"
(II) LoadModule: "shadowfb"
(II) Loading /usr/lib/xorg/modules//libshadowfb.so
(II) Module shadowfb: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) R128(0): Page flipping disabled
(!!) R128(0): For information on using the multimedia capabilities
of this adapter, please see http://gatos.sf.net.
(II) UnloadModule: "vesa"
(II) Unloading /usr/lib/xorg/modules/drivers//vesa_drv.so
(II) UnloadModule: "fbdev"
(II) Unloading /usr/lib/xorg/modules/drivers//fbdev_drv.so
(II) UnloadModule: "fbdevhw"
(II) Unloading /usr/lib/xorg/modules/linux//libfbdevhw.so
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprU)
[5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprU)
[6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprU)
[7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[8] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU)
[10] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU)drmOpenDevice: node name is /dev/dri/card0

[paulkruger]

Part Four:


drmOpenDevice: node name is /dev/dri/card0
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card1
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card2
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card3
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card4
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card5
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card6
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card7
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card8
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card9
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card10
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card11
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card12
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card13
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card14
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmGetBusid returned ''
(II) [drm] loaded kernel module for "r128" driver.
(II) [drm] DRM interface version 1.3
(II) [drm] DRM open master succeeded.
(II) R128(0): [drm] Using the DRM lock SAREA also for drawables.
(II) R128(0): [drm] framebuffer handle = 0x2f000000
(II) R128(0): [drm] added 1 reserved context for kernel
(II) R128(0): X context handle = 0x1
(II) R128(0): [drm] installed DRM signal handler
(II) R128(0): [agp] Mode 0x1f000211 [AGP 0x8086/0x2530; Card 0x1002/0x5446]
(II) R128(0): [agp] 8192 kB allocated with handle 0x00000001
(II) R128(0): [agp] ring handle = 0x2e000000
(II) R128(0): [agp] Ring mapped at 0xb7e2e000
(II) R128(0): [agp] ring read ptr handle = 0x1c020000
(II) R128(0): [agp] Ring read ptr mapped at 0xb7f48000
(II) R128(0): [agp] vertex/indirect buffers handle = 0x2a020000
(II) R128(0): [agp] Vertex/indirect buffers mapped at 0xb5be2000
(II) R128(0): [agp] AGP texture map handle = 0x2a060000
(II) R128(0): [agp] AGP Texture map mapped at 0xb5702000
(II) R128(0): [drm] register handle = 0x17f1f000
(II) R128(0): [dri] Visual configs initialized
(II) R128(0): CCE in BM mode
(II) R128(0): Using 8 MB AGP aperture
(II) R128(0): Using 1 MB for the ring buffer
(II) R128(0): Using 2 MB for vertex/indirect buffers
(II) R128(0): Using 5 MB for AGP textures
(II) R128(0): Memory manager initialized to (0,0) (800,3112)
(II) R128(0): Reserved area from (0,600) to (800,602)
(II) R128(0): Largest offscreen area available: 800 x 2510
(II) R128(0): Reserved back buffer from (0,602) to (800,1202)
(II) R128(0): Reserved depth buffer from (0,1202) to (800,1803)
(II) R128(0): Reserved depth span from (0,1802) offset 0x57fd00
(II) R128(0): Reserved 23040 kb for textures at offset 0x97f400
(II) R128(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Lines
Dashed Lines
Setting up tile and stipple cache:
32 128x128 slots
7 256x256 slots
(II) R128(0): Acceleration enabled
(==) R128(0): Backing store disabled
(==) R128(0): Silken mouse enabled
(II) R128(0): Using hardware cursor (scanline 7212)
(II) R128(0): Largest offscreen area available: 800 x 1306
(II) R128(0): DPMS enabled
(II) R128(0): [DRI] installation complete
(II) R128(0): [drm] Added 128 16384 byte vertex/indirect buffers
(II) R128(0): [drm] Mapped 128 vertex/indirect buffers
(II) R128(0): [drm] dma control initialized, using IRQ 16
(II) R128(0): Direct rendering enabled
(==) RandR enabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) AIGLX: Screen 0 is not DRI2 capable
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: drmOpenMinor returns 11
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
(II) AIGLX: Loaded and initialized /usr/lib/dri/r128_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
(II) config/hal: Adding input device ImExPS/2 Generic Explorer Mouse
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 2.2.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(**) ImExPS/2 Generic Explorer Mouse: always reports core events
(**) ImExPS/2 Generic Explorer Mouse: Device: "/dev/input/event4"
(II) ImExPS/2 Generic Explorer Mouse: Found 5 mouse buttons
(II) ImExPS/2 Generic Explorer Mouse: Found x and y relative axes
(II) ImExPS/2 Generic Explorer Mouse: Found scroll wheel(s)
(II) ImExPS/2 Generic Explorer Mouse: Configuring as mouse
(**) ImExPS/2 Generic Explorer Mouse: YAxisMapping: buttons 4 and 5
(**) ImExPS/2 Generic Explorer Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "ImExPS/2 Generic Explorer Mouse" (type: MOUSE)
(**) ImExPS/2 Generic Explorer Mouse: (accel) keeping acceleration scheme 1
(**) ImExPS/2 Generic Explorer Mouse: (accel) filter chain progression: 2.00
(**) ImExPS/2 Generic Explorer Mouse: (accel) filter stage 0: 20.00 ms
(**) ImExPS/2 Generic Explorer Mouse: (accel) set acceleration profile 0
(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event2"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
(**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
(**) Macintosh mouse button emulation: (accel) set acceleration profile 0
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event3"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105+inet"
(**) Option "xkb_layout" "us"
(**) Option "xkb_options" "terminate:ctrl_alt_bksp"
(II) config/hal: Adding input device Power Button (CM)
(**) Power Button (CM): always reports core events
(**) Power Button (CM): Device: "/dev/input/event1"
(II) Power Button (CM): Found keys
(II) Power Button (CM): Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button (CM)" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Power Button (FF)
(**) Power Button (FF): always reports core events
(**) Power Button (FF): Device: "/dev/input/event0"
(II) Power Button (FF): Found keys
(II) Power Button (FF): Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button (FF)" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"


I am sure not all of this is related but I don't know what is or is not so pasted the entire log.

Thanks for your help guys !

[Hlingler]

Well, there it is:(II) R128(0): <default monitor>: Using default hsync range of 31.50-37.90 kHzThat's absurd! So: all modes higher than the 800x600 have been disallowed as either hsync or vrefresh out-of-range, as you can see in the following numerous lines.

Please search your hardware documentation, or search on-line to find out this monitor's true hsync and vrefresh ranges, post back with the values, and we'll go from there to specify them in the xorg.conf file.

V

P.S. In future, please post large text/log files to pastebin.com (or some other such file-sharing site), then post a link here.

[paulkruger]

I thought I would try to log out and log in as admin. ( can't via Gnome I guess ) But in the process of selecting the Log Out and Switch User, that screen is high resolution as I want. But then I switch back to the original login and the screen goes back to crap ?

Somewhere F.11 knows the correct video settings...how do I find and apply those to users?

:confused:

[paulkruger]

Well, there it is:That's absurd! So: all modes except the 800x600 have been disallowed as either hsync or vrefresh out-of-range, as you can see in the following numerous lines.

Please search your hardware documentation, or search on-line to find out this monitor's true hsync and vrefresh ranges, post back with the values, and we'll go from there to specify them in the xorg.conf file.

V

P.S. In future, please post large text/log files to pastebin.com (or some other such file-sharing site), then post a link here.

Sorry did not know about that. Will remember next time. I'm new here...:eek:

[Hlingler]

I don't know why the software is (apparently) detecting the monitor stuff correctly the first time, then fizzling out on subsequent attempts. We'll try to bludgeon it into submission with forced values specified in a config file - after you find out what those ranges are.

V

[paulkruger]

This is what I can find from ACER'S official site.

AL1916W LCD Monitors
Specifications

Part Number

ET.L5209.005 AL1916W VGA, Black

Size: 19" Wide TFT Color LCD

Display Area: 408 x 255 mm

Input Connector: 15-pin, D-sub

Input Signal: VGA (Analog D-sub)

Supported Resolutions: 1440x900@75Hz

Dimension: (W x H x D) 462 x 385 x 180mm

I can't fine any reference to separate sync rates for H and V but I will keep looking.
More info says: "LCD's don't have refresh rates. They have things called Response times, which is different. Doesn't matter what you set your refresh rate at, you won't notice a difference with an LCD monitor."
:D

[paulkruger]

Technology TFT active matrix
Matrix Type TFT TN
Widescreen Yes
Screen Resolution 1440x900
Color Support 16.7 million colors
Response Time 5 ms
Dot Pitch 0.284 mm
Pixel pitch 0.284 mm
FEATURES
Standarts TCO'03, MPR-II, ISO 13406-2
Brightness 300 cd/m2
Dynamic contrast 2000:1
Max horizontal view angle 160°
Max vertical view angle 160°
Interfaces VGA (D-Sub)
VIDEO
Horizontal Frequency Bandwidth (H-Sync Rate) 24-80 Hz
Vertical Frequency Bandwidth (V-Sync Rate) 56-60 MHz

[Hlingler]

OK, then we'll try "faking" it out. :D

Check with your Nautilus file browser to see if the file exists: /etc/X11/xorg.conf. If it does NOT, generate one as per instructions: http://forums.fedoraforum.org/showpost.php?p=1120206&postcount=2

After you have generated the file and moved it into place (or if it already exists), edit it as root user: open a terminal window and log in as root, the open the file with a text editor:su -
Password: <<== type root user password and press <ENTER> key
gedit /etc/X11/xorg.confFind the "Monitor" section (or create it if needed), and add lines so that it looks like so (your other details will vary of course):Section "Monitor"
[...]
Identifier "Monitor0"
VendorName "Unknown"
ModelName "COMPAQ FS7600"
HorizSync 24.0 - 80.0
VertRefresh 50.0 - 160.0
Option "DPMS"
EndSectionSave the file and exit. Exit the terminal, log out of the desktop, and re-start the X server. Log back in and assess. Post results.

V

[paulkruger]

I don't know why the software is (apparently) detecting the monitor stuff correctly the first time, then fizzling out on subsequent attempts. We'll try to bludgeon it into submission with forced values specified in a config file - after you find out what those ranges are.

V

Thanks....I am learning this Linux stuff ! I really really really want to get rid of Bill Gate's expensive stuff ! :)

[paulkruger]

OK, then we'll try "faking" it out. :D

Check with your Nautilus file browser to see if the file exists: /etc/X11/xorg.conf. If it does NOT, generate one as per instructions: http://forums.fedoraforum.org/showpost.php?p=1120206&postcount=2

After you have generated the file and moved it into place (or if it already exists), edit it as root user: open a terminal window and log in as root, the open the file with a text editor:su -
Password: <<== type root user password and press <ENTER> key
gedit /etc/X11/xorg.confFind the "Monitor" section (or create it if needed), and add lines so that it looks like so (your other details will vary of course):Section "Monitor"
[...]
Identifier "Monitor0"
VendorName "Unknown"
ModelName "COMPAQ FS7600"
HorizSync 24.0 - 80.0
VertRefresh 50.0 - 160.0
Option "DPMS"
EndSectionSave the file and exit. Exit the terminal, log out of the desktop, and re-start the X server. Log back in and assess. Post results.

V
My Version...conf file did not exist. Going to test now. BRB

Section "Monitor"
[...]
Identifier "Monitor0"
VendorName "Acer"
ModelName "AL1916W"
HorizSync 24.0 - 80.0
VertRefresh 56.0 - 60.0
Option "DPMS"
EndSection

[paulkruger]

Problem

After the initial progress bar at boot I get:

eth0: setting full-duplex for the network then a blinking cursor. Anything I type is echo'd on the screen but no GUI shows.

---------

[paulkruger]

When I get back in is there a way to edit Grub to provide me a means to boot directly to terminal mode?

I can't seem to get there from the Grub command line...at least I don't know how to.

[Hlingler]

Sorry, I meant to warn you that could happen. Apparently, it didn't like the edits, and choked on the forced values. <SIGH>

At the command prompt, log in as root user (if you aren't already root), and move the busted file out of the way:
mv /etc/X11/xorg.conf /etc/X11/xorg.conf.busted

Then copy the Xorg log file to a safe place so we can see it later:
cp /var/log/Xorg.0.log /home/<insert-normal-username>/ && chown <insert-normal-username> /home/<insert-normal-sername>/Xorg.0.log

Re-boot. Post entire contents of /etc/X11/xorg.conf. We'll go from there.

V

P.S. If you can't get to a text-mode log-in, see: http://forums.fedoraforum.org/showthread.php?t=197754

[paulkruger]

I booted from the LIVE CD and can access terminal however I can't find my way to edit that file as root. I can use the file browser to view it only.

How can I boot to /root in a terminal? Yes I really am this dumb so far !

[Hlingler]

The HDD file system is probably mounted as read-only when booted into the Live CD. You'd have to re-mount it read-write.

Try the instructions at: http://forums.fedoraforum.org/showthread.php?t=197754

V

[paulkruger]

I tried:
P.S. If you can't get to a text-mode log-in, see: http://forums.fedoraforum.org/showthread.php?t=197754

Boot is same with the edited version per instructions.

Did I mention that when I boot the live CD the resolution if great!

[paulkruger]

The HDD file system is probably mounted as read-only when booted into the Live CD. You'd have to re-mount it read-write.

Try the instructions at: http://forums.fedoraforum.org/showthread.php?t=197754

V

Unless I missed it I could not find an instruction to re-mount the HDD as read-write?

[Hlingler]

Follow the linked rescue instructions without any Live CD in the PC.

V

[paulkruger]

I re-tried the instruction and got a terminal. It won't let me log in. I put in my login, it asked for password which I put in then nothing...just a blinking cursor which echos what I type but does not accept any commands.

[Hlingler]

If you got to a terminal, then log in as root user, using root user password, then perform the rescue as directed in Glennzo's post.

V

EDIT: If you see something like this:localhost.localdomain login: followed by a blinking cursor, then type:
root

and press <ENTER> key, then type root user password when prompted. You will be logged in as root and can then proceed.

[paulkruger]

If you got to a terminal, then log in as root user, using root user password, then perform the rescue as directed in Glennzo's post.

V

EDIT: If you see something like this:localhost.localdomain login: followed by a blinking cursor, then type:
root

and press <ENTER> key, then type root user password when prompted. You will be logged in as root and can then proceed.

I did that...as I said when I type in the password nothing happens...I am not being logged in at all.

[Hlingler]

Hmm... that's odd - and not-so-good.

Boot into the Live CD again, open a terminal window, and command:
su -
fdisk -l
mount

Post results.

V

[paulkruger]

Going back to LiveCD... When I CTR-ALT-DEL I can see the system shutting down so it bust be booting...just without an means to control anything?

[paulkruger]

This is strange...this time LiveCD booted to low resolution? Last time it was high resolution??

[paulkruger]

Sorry can't save a file to the CD boot disk so posting here.
Found out I can save to the HDD from Live CD.

fdisl -l
[code]

[liveuser@localhost ~]$ su -
[root@localhost ~]# fdisk -l

Disk /dev/sda: 40.0 GB, 40000000000 bytes
255 heads, 63 sectors/track, 4863 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xda57da57

Device Boot Start End Blocks Id System
/dev/sda1 * 2777 2802 204800 83 Linux
/dev/sda2 5 2776 22266090 7 HPFS/NTFS
/dev/sda3 2802 4863 16558080 8e Linux LVM

Partition table entries are not in disk order

Disk /dev/dm-0: 3221 MB, 3221225472 bytes
255 heads, 63 sectors/track, 391 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 3221 MB, 3221225472 bytes
255 heads, 63 sectors/track, 391 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/dm-2: 15.8 GB, 15879634944 bytes
255 heads, 63 sectors/track, 1930 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-2 doesn't contain a valid partition table

Disk /dev/dm-3: 1073 MB, 1073741824 bytes
255 heads, 63 sectors/track, 130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-3 doesn't contain a valid partition table


and


[root@localhost ~]# mount
/dev/mapper/live-rw on / type ext4 (rw,noatime)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0")
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
/dev/sr0 on /mnt/live type iso9660 (ro)
varcacheyum on /var/cache/yum type tmpfs (rw,mode=0755,rootcontext="system_u:object_r:var_t:s0")
/tmp on /tmp type tmpfs (rw,rootcontext="system_u:object_r:tmp_t:s0")
vartmp on /var/tmp type tmpfs (rw,rootcontext="system_u:object_r:tmp_t:s0")
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
gvfs-fuse-daemon on /home/liveuser/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=liveuser)

[paulkruger]

Note I can browse the files on the installed system on HDD and saved a text file with the above information. The HDD must be mounted however I don't know how to acceess it as /root to remove the offending config file.

[Hlingler]

OK, the HDD (in this case: sda3, the Linux LVM) is not mounted, so do that first: open a terminal window and command:
su -
mount -t auto -o rw /dev/mapper/VolGroup00-LogVol00 /mnt/

I'm taking a guess as to the LVM name - using default. Assuming that succeeds (no output except a new prompt):
mv -i /mnt/etc/X11/xorg.conf /mnt/etc/X11/xorg.conf.busted

You should then be able to re-boot the PC into the installed OS (without Live CD) as before.

I'm getting a headache. Perhaps we can pick this up again later, or someone else will come along with fresh ideas. But I'll stay around until you're at least back to where you started.

V

[paulkruger]

OK, the HDD (in this case: sda3, the Linux LVM) is not mounted, so do that first: open a terminal window and command:
-

V

I used copy/paste. It says I need to specify a file system type. Where do I do this?

mount -t auto -o rw /dev/mapper/VolGroup00-LogVol00 /mnt/

[Hlingler]

Those are numbers, the number zero '0', not capital letters 'O'. "Vol" is letters as in "Volume".

V

[paulkruger]

I'm getting a headache. Perhaps we can pick this up again later, or someone else will come along with fresh ideas. But I'll stay around until you're at least back to where you started.

V

I appreciate it. I can use a break in a few too... New laptop was just delivered ! That will get a linux partition soon as well.

I would like to get back to square one at least so kids can use the web. I don't let them on Windows any more because of malware etc.:)

[paulkruger]

Those are numbers, the number zero '0', not capital letters 'O'. "Vol" is letters as in "Volume".

V

mount -t auto -o re/dev/mapper/VolGroup00-LogVoIOO/mnt
I got it...but still don't know how to specify the file system as it is asking?

[Hlingler]

It says I need to specify a file system type. Where do I do this?'-t auto' should have auto-detected file system type - but you say it did not, but returned an error instead?

V

[paulkruger]

'-t auto' should have auto-detected file system type - but you say it did not, but returned an error instead?

V

Not so much an error but said I did not specify a file system type.


mount -t auto -o re/dev/mapper/VolGroup00-LogVoIOO/mnt
mount: you must specify the filesystem type

[Hlingler]

Try:
mount -t ext3 -o rw /dev/mapper/VolGroup00-LogVol00 /mnt/

Then proceed (if that succeeds) to move the errant file out of the way.

V

P.S. Either command works here on F10. Hmm...mount -t auto -o re/dev/mapper/VolGroup00-LogVoIOO/mntAre those typos in your command, or your post only?

[paulkruger]

Try:
mount -t ext3 -o rw /dev/mapper/VolGroup00-LogVol00 /mnt/

Then proceed (if that succeeds) to move the errant file out of the way.

V

P.S. Either command works here on F10. Hmm...

mount: special device /dev/mapper/VolGroup00-LogVol00 does not exist

[Hlingler]

OK, please post results:
lvscan

V

[paulkruger]

OK, please post results:
lvscan

V

[root@localhost ~]# lvscan
ACTIVE '/dev/VolGroup/lv_root' [14.79 GB] inherit
ACTIVE '/dev/VolGroup/lv_swap' [1.00 GB] inherit

[paulkruger]

Unrelated. Nice Acer Aspire just arrived from Tiger Direct. Referb $299.00 Vista, AMD 64 CPU. Will make a nice Linux portable with dual boot.- WiFi built in

[Hlingler]

OK, try:
mount -t auto -o rw /dev/VolGroup/lv_root /mnt/

If that barfs, switch 'ext3' for 'auto'.

V

[paulkruger]

I know you would like to take a break. What is your time zone and schedule?

I can leave this booted from CD for kids to browse the internet with high resolution. they don't need to save anything locally anyway. I can take this up later.

I am normally on line from about 10AM EST to about 7PM ( Florida USA )

[paulkruger]

OK, try:
mount -t auto -o rw /dev/VolGroup/lv_root /mnt/

If that barfs, switch 'ext3' for 'auto'.

V

I guess that worked...I got a new command line.

[paulkruger]

mv -i /mnt/etc/X11/xorg.conf /mnt/etc/X11/xorg.conf.busted


New command line so will do the reboot now

[Hlingler]

I guess that worked...I got a new command line.Yes. Proceed to move the borked xorg.conf file out of the way, and then re-boot into the installed HDD OS. You should be (at least) back to where you started.

V

[Hlingler]

I know you would like to take a break. What is your time zone and schedule?

I can leave this booted from CD for kids to browse the internet with high resolution. they don't need to save anything locally anyway. I can take this up later.

I am normally on line from about 10AM EST to about 7PM ( Florida USA )OOPS! Didn't see that post - we're posting too fast, over top of each other!

Location: Connellsville, PA, USAEST. If you haven't re-booted, just leave off, and post back here whenever you want to try again. I should be available most evenings.

V

[paulkruger]

OK, the HDD (in this case: sda3, the Linux LVM) is not mounted, so do that first: open a terminal window and command:
su -
mount -t auto -o rw /dev/mapper/VolGroup00-LogVol00 /mnt/

I'm taking a guess as to the LVM name - using default. Assuming that succeeds (no output except a new prompt):
mv -i /mnt/etc/X11/xorg.conf /mnt/etc/X11/xorg.conf.busted

You should then be able to re-boot the PC into the installed OS (without Live CD) as before.

I'm getting a headache. Perhaps we can pick this up again later, or someone else will come along with fresh ideas. But I'll stay around until you're at least back to where you started.

V

...Sort of...

It rebooted after removing the CD but instead of providing me the users to login it has a screen ( good resolution! ) but says localhost.local domain and to log in as "other" the rest of the buttons are grayed out so I have no option to continue beyond this screen.

After a minute or so it provided me with my login but having entered my password it is just sitting there....I clicked cancel...waiting...waiting. Also on boot there was no Grub.

Going to try to go to terminal CTR-ALT-F2

No luck. same as before. Asks for login then won't accept input for password.

:confused:

[paulkruger]

trying one more login. Grub appeared this time. If this takes me back to start I am going to quit for the time. Play with my new laptop ! Give you a much deserved rest. wish i could buy the beer !

[paulkruger]

Nope. Same login problem but now in low resolution. Perhaps a new install might be in order.

Then perhaps before a re-boot I can locate the correct configuration for video and save that for later.

What do you think?

I am taking a break...you do likewise and many thanks.

[Hlingler]

Can you login as "other" without a password? I.E.: just press <ENTER> key.

V

Perhaps a new install might be in order.Yes, I agree, if there's no valuable data to lose, you're best to start fresh at this point.

[paulkruger]

Can you login as "other" without a password? I.E.: just press <ENTER> key.

V

Yes, I agree, if there's no valuable data to lose, you're best to start fresh at this point.

The {ENTER} did not work and I have no data yet. This was a new install.

Talk to you later...I will probably take this new install up tomorrow. I am tired too! ;)

[paulkruger]

New day...starting a fresh wipe of HDD and a new install. Time 11:30 AM

[paulkruger]

Recent posts with progress on this are not appearing?

[paulkruger]

Progress. FYI

Initial new install high resolution 1440x900 looks great!
after re-boot, resolution held this time.
Now doing an upgrade to new releases and will again reboot.
saved several initial configuration files and info in case of resolution problems returning.

[paulkruger]

Progress. FYI

Initial new install high resolution 1440x900 looks great!
after re-boot, resolution held this time.
Now doing an upgrade to new releases and will again reboot.
saved several initial configuration files and info in case of resolution problems returning.

So far so good. After updates and a couple of reboots the video seems to be locked in.

Thanks much for the help. I will consider this solved as of this time.

Now to finding programs to use !:)

[Hlingler]

So far so good. After updates and a couple of reboots the video seems to be locked in.Go figure. Who knows? It's Friday, the Moon and stars are aligned, and/or your Linux karma is now high enough. Whatever, glad it works (keep fingers crossed).

V

[paulkruger]

OOP....consider UN SOLVED!

This morning I booted and had only the 800x600 screen again !!!


Wish I knew what file(s) F.11 used to set the video resolution.

I kept copy of original boot logs and they show the high resolution. today's boot logs show only the low res options. Why would rebooting change the video settings back to low quality after two good boots?

[paulkruger]

What about removing any video drivers that are not related to the graphics card I have so the only choices are the correct card? ( and perhaps default vga for emergencies )

[paulkruger]

I removed all drivers that I could identify as not relative to my system to a new folder inside /drivers and rebooted.

Still holding good resolution. Not sure this had anything to do with my moving drivers however. Still hoping to find where the settings are loaded from and a way to "lock" in the known good settings.

-- EDIT

Funny thing happened on the way to this post...after posting the above the browser refreshed to show the new post...then everything froze. Could not move mouse and keyboard died!

Had to reboot in order to post this update. ( Resolution still good ).

[paulkruger]

SELinix ? What is it and do I need it?

[ap90033]

Ok I have it working for most part. I have X58 tri sli board with i7 and (2) GTX260's.
They show up but how do i know SLI is working?
also, I have this connected to my HDTV which is a 1080P (1920x1080). In vista 64 after jumping through hoops i found a way to get it working (issue i think was the DVI to HDMI using HDCP and not allowing the GPU to scale, i think) so works great in windows. How do I get it working right in Fedora? right now i cant see any of the corners and cant see the task bar (hard to figure out where it is exactly). Thanks for your help.

[stevetamis]

Hi Bit Of A Start Up Problem, After Booting My Computer, When XP starts also nvidia windows xp setup. I Have Re-Installed The Drivers As Prompted By The Setup Wizard Loading Every Time I Boot Windows But The Problem Still Persists....Can Someone Please Help?

[Demz]

Hi Bit Of A Start Up Problem, After Booting My Computer, When XP starts also nvidia windows xp setup. I Have Re-Installed The Drivers As Prompted By The Setup Wizard Loading Every Time I Boot Windows But The Problem Still Persists....Can Someone Please Help?

this is a linux thread not a Windows one. your best to ask in the nvidia forum

[fidesratioque]

Hi,

I followed Dangermouse's guide on installing the NVIDIA driver as described here:
http://www.dnmouse.org/nvidia.html

However, it still does not work. Here is some potentially relevant info:

[ekravets@HAL-9001 ~]$ glxinfo|grep render
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
OpenGL renderer string: Software Rasterizer
[ekravets@HAL-9001 ~]$ su
Password:
[root@HAL-9001 ekravets]# lspci|grep VGA
02:00.0 VGA compatible controller: nVidia Corporation GeForce 8400 GS (rev a1)
[root@HAL-9001 ekravets]#

I am running Fedora 11. On Ubuntu Jaunty 9.04 I had no problems using desktop effects.

Does anyone know what to do? Thank you in advance.

P.S. This is the error I get when I try to enable desktop effects:

"Failed to activate desktop effects using the given configuration options. Settings will be reverted to their previous values.

Check your X configuration. You may also consider changing advanced options, especially changing the compositing type."

[ap90033]

Any Ideas?

SLI on 1080P screen way to big and how do i know if SLI works?

--------------------------------------------------------------------------------

Ok I have it working for most part. I have X58 tri sli board with i7 and (2) GTX260's.
They show up but how do i know SLI is working?
also, I have this connected to my HDTV which is a 1080P (1920x1080). In vista 64 after jumping through hoops i found a way to get it working (issue i think was the DVI to HDMI using HDCP and not allowing the GPU to scale, i think) so works great in windows. How do I get it working right in Fedora? right now i cant see any of the corners and cant see the task bar (hard to figure out where it is exactly). Thanks for your help.

[Ereos]

Hello,

I posted a message here : http://forums.fedoraforum.org/showthread.php?t=226799 but i haven't an answer so i ask my question in this topic.

I would like to know if the GTX275 (Geforce) works on linux because i want to buy this card.

Thanks

[Hlingler]

I would like to know if the GTX275 (Geforce) works on linux because i want to buy this card.Sadly, checking this out quickly on the NVidia web site, I get a message: "No certified downloads were found for this configuration." This was for GeForce => GeForce 200 Series => GeForce GTX 275 => Linux 32-bit => English (US). You may repeat the search yourself (http://www.nvidia.com/Download/index.aspx?lang=en-us), and/or check for support with Beta drivers, but... don't hold your breath. Sorry.

V

[Demz]

http://us.download.nvidia.com/XFree86/Linux-x86/190.16/README/appendix-a.html http://www.nvidia.com/object/linux_display_ia32_190.16.html an the 64bit driver http://www.nvidia.com/object/linux_display_amd64_190.16.html seems lik the 190.16 driver works which is a beta driver

[Hlingler]

OK, so Demz did the work for you: you may be the "guinea pig" and try the NVIDIA 190.16 Beta driver.

Hold on, it could be a rough ride... or maybe not. Let us know what happens.... Remember to remove all other versions of the proprietary NVidia video drivers - whether from binary or RPMs - first.

Good Luck,
V

[Demz]

makes you wonder why Nvidia release a Graphics card an yet cant have a working driver for linux people that wanna use it

[ap90033]

Ok I have it working for most part. I have X58 tri sli board with i7 and (2) GTX260's.
They show up but how do i know SLI is working?
also, I have this connected to my HDTV which is a 1080P (1920x1080). In vista 64 after jumping through hoops i found a way to get it working (issue i think was the DVI to HDMI using HDCP and not allowing the GPU to scale, i think) so works great in windows. How do I get it working right in Fedora? right now i cant see any of the corners and cant see the task bar (hard to figure out where it is exactly). Thanks for your help

[fidesratioque]

Any thoughts on my conundrum? Thanks folks.

[Hlingler]

Please post results of commands:
uname -a
rpm -qa|grep -i nvid|sort

V

[IICODECll]

Radeon 9.7 drivers released. I wonder if they'll work.

http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx

[Hlingler]

Radeon 9.7 drivers released. I wonder if they'll work.

http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspxNo: http://forums.fedoraforum.org/showthread.php?t=221242
http://forums.fedoraforum.org/showpost.php?p=1245134&postcount=24
http://forums.fedoraforum.org/showpost.php?p=1245240&postcount=27

V

[IICODECll]

Yeah, I just read that on another forum. I should have looked further instead of posting. Thanks Hlingler. Another 30 days. :)

[Demz]

t's a bit late in the month, but AMD has just released the ATI Catalyst 9.7 driver update for Linux. Officially, the only new feature in Catalyst 9.7 is production support for Red Flag DT 7.0, but there are some bug-fixes too. The bug-fixes range from segmentation fault fixes to addressing some monitor / RandR problems. This is not mentioned in the change-log, but there should be some composite support improvements (including video tearing fixes) within the Catalyst Linux release too. Overall though this is just another month with few changes that are visible to the end-user.

Catalyst 9.7 is also still lacking when it comes to supporting the latest Linux kernels, but that should be fixed around in Catalyst 9.8 we are anticipating. AMD also still has yet to release any information regarding the XvBa (http://www.phoronix.com/scan.php?page=search&q=XvBA) video API.



hhhhhhhhhhhhhhhhhhhhhhhh

[ap90033]

Please post results of commands:
uname -a
rpm -qa|grep -i nvid|sort

V

Are you talking to me? If so I will have this shortly.. :)

[alexuk]

I'll be upgrading my Radeon 1950 and in view of the lack of ATI driver in FC11 I was considering Nvidia, eg an 9880 based card. However can anyone confirm whether Nvidia's drivers work well with FC11? I can see nvidia provides linux drivers on the website (also in x64) but there seems to be no reference to the distribution. Many thanks.

[Reindeer]

... However can anyone confirm whether Nvidia's drivers work well with FC11? I can see nvidia provides linux drivers on the website (also in x64) but there seems to be no reference to the distribution. Many thanks.

Yes, the packaged nVidia drivers work quite well. Some caveats:

Do yourself a favor and find _packages_ specifically for Fedora in the RPMFusion repository.
Use yum or yumex and search for "kmod-nvidia", and add the exact match of drivers to your kernel number and x86 or x64 (and PAE as well if you are using that).

As of this writing, the latest and greatest kernel does not yet have packages available, so you may need to use a slightly older kernel to match what is currently available.
If packages become available, use them by all means.

The latest kernel that I am aware of that has a matching kmod-nvidia package is: 2.6.29.6-217.2.3.fc11.*

If you decide to use the scripts and install nVidia's drivers directly, they may not work as well.
I found problems with nVidia's drivers when not specifically packaged for Fedora. YMMV.
Lots of folks have complained of things not working so well after installing nVidia's not RPM packaged drivers.
I was desperate at one point and tried them, but the hassles and the bugs were not worth it.

[alexuk]

Yes, the packaged nVidia drivers work quite well. Some caveats:

Do yourself a favor and find _packages_ specifically for Fedora in the RPMFusion repository.
Use yum or yumex and search for "kmod-nvidia", and add the exact match of drivers to your kernel number and x86 or x64 (and PAE as well if you are using that).

As of this writing, the latest and greatest kernel does not yet have packages available, so you may need to use a slightly older kernel to match what is currently available.
If packages become available, use them by all means.

The latest kernel that I am aware of that has a matching kmod-nvidia package is: 2.6.29.6-217.2.3.fc11.*


Thanks for this. Well, this does seem a much better situation than ATI where we are still waiting for ONE driver for any fc11 kernel. Moving to Nvidia seems like a good idea then. Looking at a few models.

[clueless]

I cant get FC11 to boot up in the gui on my dell 1520 Inspiron. I know its the Nvidian driver but I don't know how to get around it. It worked out the box with FC10 so I have reverted back to FC10 since my skill is very limited (very) I am basically considering waiting till FC12 to see if it just works.
I am dissapointed with Dell since it has a "supposed" alliance with linux via Ubuntu and yet the wireless is another non starter in FC10. I know there are ways around it but they are beyond my scope at present. I had hoped that FC11 the wireless would be fixed in FC11, but I wont know since I have no gui.

Any help would be welcome, baby steps please.

Sean

[LinUsr@Flanders]

Hi,

Big tnx for this warning...I'd better stick to the _supplied_ drivers for F10.

BTW, I found an Asus N6200 in my "left-overs" ( :D yep, I got some of that :p )
Is that an Nvidia 6200 with another jacket?

Thor

[Reindeer]

Thanks for this. Well, this does seem a much better situation than ATI where we are still waiting for ONE driver for any fc11 kernel. Moving to Nvidia seems like a good idea then. Looking at a few models.

nVidia has not opened their source, and they are a bit slow on making their drivers for Linux, but at least packages come out for specific kernels and you don't have to compile them, but according to what you wrote, sounds like ATI has basically given up on supporting Fedora well. That's a shame.
At the current moment, my opinion is that nVidia's high end cards are a good choice, but that being said, I haven't tried ATI on Fedora since version 4, so I can't really comment.
I have the 9600GT and I'm very happy with it. Make sure it stays cool and you will be happy too, as my old 7600GT card fried from overheating, my own fault for not making sure that it was dust free.

[Reindeer]

Hi,

Big tnx for this warning...I'd better stick to the _supplied_ drivers for F10.

BTW, I found an Asus N6200 in my "left-overs" ( :D yep, I got some of that :p )
Is that an Nvidia 6200 with another jacket?

Thor

I would say yes, without seeing it, Sounds like it to me.
If you install it, you should be able to read the information coming from the Kinfocenter program >> PCI

The first line of output should look something like this:
nVidia Corporation G94 [GeForce 9600 GT]

[LinUsr@Flanders]

Big tnx Reindeer!

Thor

[LinUsr@Flanders]

(and now...to the BatMobile!!! for some drivers...)

:D

Thor

[Reindeer]

Big tnx Reindeer!

Thor

You're welcome. Glad that I could help. :D
Usually, I'm the one asking for help, so it's nice to be able to give back.
Good luck. Let us know how it goes.

[Reindeer]

I cant get FC11 to boot up in the gui on my dell 1520 Inspiron. I know its the Nvidian driver but I don't know how to get around it. It worked out the box with FC10 so I have reverted back to FC10 since my skill is very limited (very) I am basically considering waiting till FC12 to see if it just works.
I am dissapointed with Dell since it has a "supposed" alliance with linux via Ubuntu and yet the wireless is another non starter in FC10. I know there are ways around it but they are beyond my scope at present. I had hoped that FC11 the wireless would be fixed in FC11, but I wont know since I have no gui.

Any help would be welcome, baby steps please.

Sean

Cluefull (sorry, but I just can't bring myself to call you Clueless),

I'm guessing that if the card worked under Fedora 10, then the card's hardware is okay, and can be discounted as a problem.

If you are not seeing the nVidia logo appear, and your boot screen does not say that the nVidia driver is loaded, then it's not loading. It might not have gotten installed correctly, or it got munged. Stuff happens. Sometimes the driver version and the kernel version are not matched, and so things don't work right. You will need to ensure that the boot loader ( /boot/grubgrub.conf ) is loading the kernel number that exactly matches your driver's kernel compilation. Otherwise, it won't work and you will be frustrated. I like to edit grub.conf to show which kernel has what nvidia driver. Mine looks like this (excerpted for brevity):
title (default) Fedora (2.6.29.6-217.2.16.fc11.i686.PAE) + kmod-nvidia 185.18.36-1.fc11.2
root (hd0,0)
kernel /vmlinuz-2.6.29.6-217.2.16.fc11.i686.PAE ro root=/dev/mapper/vg_szybki-lv_root rhgb quiet vga=792
initrd /initrd-2.6.29.6-217.2.16.fc11.i686.PAE.imgCan you supply more info?

Do you get a login screen? Can you describe what happens in more detail? What exactly do you see when your system boots up?

What does /var/logboot.log say? You should have something like:
Checking for module nvidia.ko:
Enabling the nvidia driver: Driver already enabled.If not, then something is wrong with how the software got installed most likely.

What does your /var/logXorg.0.log file say?
Look for errors or warnings, and if they appear, post them here.

The log files are your friends. Being a good Linux user means reading log files. ;)

Understand, I'm not an expert like some are here. There are many here that have mad skillz and have saved my bacon on more than one occasion. I've gone through this hell recently, so I'm boned up on it a bit.
I'm just trying to see if it's something obvious and put it in simple language for you.
And don't sweat it. Getting video drivers to work is a pain because it forces you to use the command line and a simple text editor to look for and fix the problem sometimes, but it's so worth it, and once you have solved a problem like that, other stuff becomes easier and your confidence level grows.

Can you use the "nv" or "vesa" drivers in Fedora 11? This might not be what you want ultimately, but it might give you at least a comfort level if you don't need 3D graphics right away while you're waiting for a reply to a post. You can change the driver in /etc/X11/xorg.conf by editing the line that points to the driver. I recommend trying the generic "vesa" first.

The section in xorg.conf should look like this:
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
Option "AddARGBGLXVisuals" "True"
EndSectionJust replace "nvidia" with "vesa" <-- the generic driver that works but doesn't produce stunning graphics (or use "nv")

Hope this helps.
--Reindeer

BTW: I just noticed that this thread if for hardware problem. I strongly suggest posting this in software problems instead.
http://forums.fedoraforum.org/forumdisplay.php?f=9
It's likely that the people best able to help you are not monitoring this thread.

[LinUsr@Flanders]

Just rambling out loud here, if I just slot the card in, start the PC (the BIOS would detect "something new") in mode 3, do

Xorg -configure

to get a new Xorg.conf, would the system automatically get the drivers for me? RPMfusion is working here...so I guess this could be possible?

Just the plug&play thought aching up here :D

Thor

[Reindeer]

Just rambling out loud here, if I just slot the card in, start the PC (the BIOS would detect "something new") in mode 3, do

to get a new Xorg.conf, would the system automatically get the drivers for me? RPMfusion is working here...so I guess this could be possible?

Just the plug&play thought aching up here :D

Thor

The system will not automatically download anything that you didn't tell it to in terms of drivers.
You say that "RPMfusion is working here", so maybe you already have this configured. Do you?
If you do, then use yum or yumex to download it and install the package(s). If not, configure yum.
You will also want to ensure that the driver that you load was compiled for the kernel version that you are currently wanting to use.

[LinUsr@Flanders]

Hmm,

Got it...

Yum install [drivername]

All I have to do is figure out the name and I'm off,, again: TNX, dude!! :-)

Thor

[Reindeer]

Hmm,

Got it...

Yum install [drivername]

All I have to do is figure out the name and I'm off,, again: TNX, dude!! :-)

Thor

Yes. Look at /boot/grub/grub.conf and determine which kernel you are going to use,
and write down the number. Alternately you can run:

[user@hostname ~]$ uname -a
Linux hostname 2.6.29.6-217.2.16.fc11.i686.PAE #1 SMP Mon Aug 24 17:16:21 EDT 2009 i686 i686 i386 GNU/LinuxThis is the info that you want to exactly match the display driver with (in my example):
2.6.29.6-217.2.16.fc11.i686.PAE

..and then insert the words "kmod-nvidia-" in front of this to get the right name.

kmod-nvidia-2.6.29.6-217.2.16.fc11.i686.PAE

The kernel modification or "kmod" will only work if the module is compiled for the same kernel.
And make sure that it is in fact this kernel that gets loaded in grub.conf by default, so that you don't have to think about which kernel you are loading again.
Here is what my grub.conf looks like, with the default highlighted. Notice the numbering starts with zero:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/mapper/vg_szybki-lv_root
# initrd /initrd-version.img
#boot=/dev/sda
default=3
timeout=4
#splashimage=(hd0,0)/grub/Glassified-Splash.tar.gz
splashimage=(hd0,0)/grub/splash.xpm.gz
# hiddenmenu
# vga=792
# nomodeset
title Fedora (2.6.30.8-64.fc11.i686.PAE)
root (hd0,0)
kernel /vmlinuz-2.6.30.8-64.fc11.i686.PAE ro root=/dev/mapper/vg_szybki-lv_root rhgb quiet vga=792
initrd /initrd-2.6.30.8-64.fc11.i686.PAE.img
title Fedora (2.6.30.5-43.fc11.i586)
root (hd0,0)
kernel /vmlinuz-2.6.30.5-43.fc11.i586 ro root=/dev/mapper/vg_szybki-lv_root rhgb quiet vga=792
initrd /initrd-2.6.30.5-43.fc11.i586.img
title Fedora (2.6.30.5-43.fc11.i686.PAE)
root (hd0,0)
kernel /vmlinuz-2.6.30.5-43.fc11.i686.PAE ro root=/dev/mapper/vg_szybki-lv_root rhgb quiet vga=792
initrd /initrd-2.6.30.5-43.fc11.i686.PAE.img
title (default) Fedora (2.6.29.6-217.2.16.fc11.i686.PAE) + kmod-nvidia 185.18.36-1.fc11.2
root (hd0,0)
kernel /vmlinuz-2.6.29.6-217.2.16.fc11.i686.PAE ro root=/dev/mapper/vg_szybki-lv_root rhgb quiet vga=792
initrd /initrd-2.6.29.6-217.2.16.fc11.i686.PAE.img
You already have X.org installed. You may have to tweak your xorg.conf file to make it work if the automated configuration program didn't work so well. Once you have the driver installed, you can test it by editing xorg.conf to include the nvidia driver.

[LinUsr@Flanders]

Aha, more info :-)

Now I know where to find stuff. I did find the proprietary driver, but it doesn't seem to be too reliable, it is recommended to ise an in-repo driver instead...

Tnx

Thor

[pp_muscimol]

dear gentleman ..... I have installed the drivers for an Radeon 2400 Pro card according to the instructions from the vendor ..linux_cat910-inst-1.pdf

in the end it reported that the drivers are installed successfully,
but when I open the Catalyst control center it gives an error saying that no drivers are installed.
and the computers screen still lags a lot.
any suggestions : Thanks in advance

[Hlingler]

@pp_muscimol: Refer: http://forums.fedoraforum.org/showthread.php?t=228689

V

[reeman]

dear gentleman ..... I have installed the drivers for an Radeon 2400 Pro card according to the instructions from the vendor ..linux_cat910-inst-1.pdf

in the end it reported that the drivers are installed successfully,
but when I open the Catalyst control center it gives an error saying that no drivers are installed.
and the computers screen still lags a lot.
any suggestions : Thanks in advance

Try 'aticonfig --initial -f' without the quote of course....here is a link to the wiki for aticonfig (http://wiki.cchtml.com/index.php/Configuring)sponsored by ati. I do not know if Fedora uses an etc/X11/xorg.conf or if the file is linked to some other place so you might have to do some digging to find out how Fedora sets up the xserver the first time I used RedHat was years ago and all the files were easy to find ...now things are getting a little more hairy and I do not even know how to do a init3 and use startx anymore!

[David Batson]

Tip regarding the "radeon" driver...
I discovered that although I could choose a different resolution than native in System > Preferences > Display, I would end up with a black screen. Disabling KMS by adding the nomodeset kernel parameter to /boot/grub/menu.lst solved this problem for me.

[alex4444]

Иногда вылазит �ообщение при загрузки
Графики нет !!! ик�ов также
Мама Asus-P5QC
libdrm x86_64 2.4.15-6.fc12
[root@ss01 log]# uname -a
Linux ss01 2.6.31.6-162.fc12.x86_64 #1 SMP Fri Dec 4 00:06:26 EST 2009 x86_64 x86_64 x86_64 GNU/Linux

Вот �ообщение
[drm] TV1: INTERNAL_DAC2
------------[ cut here ]------------
WARNING: at drivers/gpu/drm/drm_crtc_helper.c:1032 drm_helper_initial_config+0x46/0x61 [drm_kms_helper]() (Not tainted)
Hardware name: System Product Name
No connectors reported connected with modes
Modules linked in: radeon(+) ttm drm_kms_helper drm i2c_algo_bit i2c_core
Pid: 137, comm: work_for_cpu Not tainted 2.6.31.6-162.fc12.x86_64 #1
Call Trace:
[<ffffffff810516f4>] warn_slowpath_common+0x84/0x9c
[<ffffffff81051763>] warn_slowpath_fmt+0x41/0x43
[<ffffffffa0042320>] drm_helper_initial_config+0x46/0x61 [drm_kms_helper]
[<ffffffffa0080eda>] radeon_modeset_init+0x548/0x55a [radeon]
[<ffffffffa008d25b>] ? r300_init+0x1a6/0x229 [radeon]
[<ffffffffa006cbdf>] radeon_driver_load_kms+0x125/0x13a [radeon]
[<ffffffffa0018486>] drm_get_dev+0x36e/0x46f [drm]
[<ffffffff81063b56>] ? do_work_for_cpu+0x0/0x2a
[<ffffffffa00a0818>] radeon_pci_probe+0x15/0x269 [radeon]
[<ffffffff812102f1>] local_pci_probe+0x17/0x1b
[<ffffffff81063b6e>] do_work_for_cpu+0x18/0x2a
[<ffffffff81067781>] kthread+0x91/0x99
[<ffffffff81012daa>] child_rip+0xa/0x20
[<ffffffff810676f0>] ? kthread+0x0/0x99
[<ffffffff81012da0>] ? child_rip+0x0/0x20
---[ end trace 1b4bbd27823b730f ]---

может TV тюнер глючит или еще чтонить
Е�ли да то как его отключить раз и нав�егда

[Hlingler]

@alex4444: Please post in English only. Otherwise: we may simply assume that you are a spammer, delete your post(s), and summarily ban you from the Forum.

From what I can read, however, it looks like you are a legitimate Fedora user. But I can't read Klingon, so I have no idea what's going on.

V

[reeman]

Иногда вылазит �ообщение при загрузки
Графики нет !!! ик�ов также
Мама Asus-P5QC
libdrm x86_64 2.4.15-6.fc12
[root@ss01 log]# uname -a
Linux ss01 2.6.31.6-162.fc12.x86_64 #1 SMP Fri Dec 4 00:06:26 EST 2009 x86_64 x86_64 x86_64 GNU/Linux

Вот �ообщение
[drm] TV1: INTERNAL_DAC2
------------[ cut here ]------------
WARNING: at drivers/gpu/drm/drm_crtc_helper.c:1032 drm_helper_initial_config+0x46/0x61 [drm_kms_helper]() (Not tainted)
Hardware name: System Product Name
No connectors reported connected with modes
Modules linked in: radeon(+) ttm drm_kms_helper drm i2c_algo_bit i2c_core
Pid: 137, comm: work_for_cpu Not tainted 2.6.31.6-162.fc12.x86_64 #1
Call Trace:
[<ffffffff810516f4>] warn_slowpath_common+0x84/0x9c
[<ffffffff81051763>] warn_slowpath_fmt+0x41/0x43
[<ffffffffa0042320>] drm_helper_initial_config+0x46/0x61 [drm_kms_helper]
[<ffffffffa0080eda>] radeon_modeset_init+0x548/0x55a [radeon]
[<ffffffffa008d25b>] ? r300_init+0x1a6/0x229 [radeon]
[<ffffffffa006cbdf>] radeon_driver_load_kms+0x125/0x13a [radeon]
[<ffffffffa0018486>] drm_get_dev+0x36e/0x46f [drm]
[<ffffffff81063b56>] ? do_work_for_cpu+0x0/0x2a
[<ffffffffa00a0818>] radeon_pci_probe+0x15/0x269 [radeon]
[<ffffffff812102f1>] local_pci_probe+0x17/0x1b
[<ffffffff81063b6e>] do_work_for_cpu+0x18/0x2a
[<ffffffff81067781>] kthread+0x91/0x99
[<ffffffff81012daa>] child_rip+0xa/0x20
[<ffffffff810676f0>] ? kthread+0x0/0x99
[<ffffffff81012da0>] ? child_rip+0x0/0x20
---[ end trace 1b4bbd27823b730f ]---

может TV тюнер глючит или еще чтонить
Е�ли да то как его отключить раз и нав�егда

Holy crap Batman, how did you do that!:eek:

[BaldrickinAsia]

Since upgrading my lenovo t61p to fc12 I am unable to to change my video settings from nvidia-settings

Everything else works. I think the cause is related to the driver being unable to read the EDID properly. Attached is my Xorg logfile.

2.6.31.6-166.fc12.i686.PAE

nvidia-xconfig-1.0-1.fc12.i686
nvidia-settings-1.0-3.2.fc12.i686
xorg-x11-drv-nvidia-173xx-173.14.22-3.fc12.i686
kmod-nvidia-173xx-PAE-173.14.22-1.fc12.4.i686
xorg-x11-drv-nvidia-173xx-libs-173.14.22-3.fc12.i686
kmod-nvidia-173xx-2.6.31.6-166.fc12.i686.PAE-173.14.22-1.fc12.4.i686

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (mockbuild@) Sun Nov 22 21:05:17 EST 2009

# Xorg configuration created by livna-config-display

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection

Section "Files"
ModulePath "/usr/lib/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib/xorg/modules/drivers"
ModulePath "/usr/lib/xorg/modules"
EndSection

Section "ServerFlags"
Option "AIGLX" "on"
EndSection

Section "InputDevice"
# generated from data in "/etc/sysconfig/keyboard"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbLayout" "us"
Option "XkbModel" "pc105"
EndSection

Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
Option "AddARGBGLXVisuals" "True"
Option "AddARGBGLXVisuals" "true"
Option "RenderAccel" "true"
Option "Composite" "Enable"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Videocard0"
Option "AddARGBGLXVisuals" "True"
SubSection "Display"
Modes "nvidia-auto-select"
EndSubSection
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection

Section "Module"
Load "extmod"
Load "glx"
Load "dbe"
Load "extmod"
EndSection

[leigh123linux]

Since upgrading my lenovo t61p to fc12 I am unable to to change my video settings from nvidia-settings

Everything else works. I think the cause is related to the driver being unable to read the EDID properly. Attached is my Xorg logfile.

2.6.31.6-166.fc12.i686.PAE

nvidia-xconfig-1.0-1.fc12.i686
nvidia-settings-1.0-3.2.fc12.i686
xorg-x11-drv-nvidia-173xx-173.14.22-3.fc12.i686
kmod-nvidia-173xx-PAE-173.14.22-1.fc12.4.i686
xorg-x11-drv-nvidia-173xx-libs-173.14.22-3.fc12.i686
kmod-nvidia-173xx-2.6.31.6-166.fc12.i686.PAE-173.14.22-1.fc12.4.i686

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (mockbuild@) Sun Nov 22 21:05:17 EST 2009

# Xorg configuration created by livna-config-display

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection

Section "Files"
ModulePath "/usr/lib/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib/xorg/modules/drivers"
ModulePath "/usr/lib/xorg/modules"
EndSection

Section "ServerFlags"
Option "AIGLX" "on"
EndSection

Section "InputDevice"
# generated from data in "/etc/sysconfig/keyboard"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbLayout" "us"
Option "XkbModel" "pc105"
EndSection

Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
Option "AddARGBGLXVisuals" "True"
Option "AddARGBGLXVisuals" "true"
Option "RenderAccel" "true"
Option "Composite" "Enable"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Videocard0"
Option "AddARGBGLXVisuals" "True"
SubSection "Display"
Modes "nvidia-auto-select"
EndSubSection
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection

Section "Module"
Load "extmod"
Load "glx"
Load "dbe"
Load "extmod"
EndSection


Try installing the correct driver!

nVidia Corporation Quadro FX 570M is listed as supported by the latest and greatest :)

http://us.download.nvidia.com/XFree86/Linux-x86_64/190.42/README/appendix-a.html



su
yum erase *nvidia*
yum install kmod-nvidia-PAE
reboot

[BaldrickinAsia]

doh
Thanks a lot. love your work btw

[digester]

Am I correct in assuming that kernel upgrades require removing kmod-nvidia et al and redoing the steps in the nvidia guide?

The above was the only way to get a fully working (i.e. direct rendering as reported by glxinfo | grep direct) composited environment after updating my box after a 2 week absence due to business.

[alexuk]

Oh dear. I spent ages this morning installing fglrx, updating xorg, etc for my X1950 Pro, before discovering it is not supported. :(

I have deinstalled fglrx but now if I run system-config-display I do not get X11 up. I've tried editing by hand trying the radeon and ati drivers but the only thing that seems to work is "vesa".

What's the best driver I should be using for fast and nice 2D and how do I install it? I am on F11 all updated.

TIA. Off to try blacklist radeon and radeonhd in the blacklist to see if it makes any diff

[radepal]

I have problem with geforce 9800 gt 1gb Palit green

It dosen't work with new drivers such 190.42 or 195.30
only work with 173
so i can't use VDPAU or CUDA
[root@Valhalla radepal]# lspci |grep VGA
02:00.0 VGA compatible controller: nVidia Corporation GeForce 9800 GT (rev a2)
[root@Valhalla radepal]# uname -r
2.6.31.6-166.fc12.x86_64
[root@Valhalla radepal]#


I use legith tutorial to run drivers and only work for 173xx
i made rpm for 195 but it also didn't work
on photos is what system write on start when i use new drivers
i can't do nvidia-bug-report bicause system is freez

on nvidia site my card 9800 gt is call 0614 is fully suported teoreticaly

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (mockbuild@) Sun Nov 22 21:04:19 EST 2009

# Xorg configuration created by livna-config-display

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection

Section "Files"
ModulePath "/usr/lib64/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib64/xorg/modules/extensions
ModulePath "/usr/lib64/xorg/modules"
EndSection

Section "ServerFlags"
Option "AIGLX" "on"
EndSection

Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "keyboard"
EndSection

Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Videocard0"
Option "UseEvents" "false"
Option "AddARGBGLXVisuals" "True"
SubSection "Display"
Modes "nvidia-auto-select"
EndSubSection
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection

[nacross]

I am a bit frustrated.

I followed the guide for installing nVidia drivers and it worked... but now I am stuck with resolution 1024x768.
I am able to use desktop effects, and the nouveau modules are gone.

I installed kmod-nvidia-173xx

I tried to edit /etc/X11/xorg.conf to insert some modes higher than 1024x768 but the file was reverted after boot.

$ lspci | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5500] (rev a1)


From nVidia Display Settings, I got that the CTR-0 is Envision CT720g, which is more o less correct as the monitor is AOC but the model is correct (maybe a manufacturer brand instead of the commercial brand)

$ cat /etc/X11/xorg.conf
# Xorg configuration created by livna-config-display

Section "Files"
ModulePath "/usr/lib/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib/xorg/modules"
EndSection

Section "ServerFlags"
Option "AIGLX" "on"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
Option "AddARGBGLXVisuals" "True"
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection


I am not sure what else I should post in order to provide enough information for helping me out.

Thanks in advance

[clueless]

Problem solved thank you FC12 just worked.

[nacross]

I dig a bit where xorg logs are to post them, hope this help.

I feel I am looking at the screen and not really understanding what I am missing :(

# cat Xorg.setup.log

X.Org X Server 1.7.1
Release Date: 2009-10-23
X Protocol Version 11, Revision 0
Build Operating System: 2.6.18-164.2.1.el5
Current Operating System: Linux bones 2.6.31.9-174.fc12.i686 #1 SMP Mon Dec 21 06:24:20 UTC 2009 i686
Kernel command line: ro root=/dev/mapper/vg_bones-lv_root noiswmd LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us-acentos rhgb quiet rdblacklist=nouveau rdblacklist=nouveau
Build Date: 05 November 2009 07:43:20PM
Build ID: xorg-x11-server 1.7.1-7.fc12
Current version of pixman: 0.16.4
Before reporting problems, check http://bodhi.fedoraproject.org/
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/dev/null", Time: Wed Dec 30 21:15:05 2009
(++) Using config file: "/tmp/tmpRvP9w1xorg.config"
The PCI device has a kernel module claiming it.
This driver cannot operate until it has been unloaded
(EE) No devices detected.

Fatal server error:
no screens found

Please consult the The X.Org Foundation support
at http://bodhi.fedoraproject.org/
for help.
Please also check the log file at "/dev/null" for additional information.

a symbols
Errors from xkbcomp are not fatal to the X server


The dump of # cat Xorg.0.log is located at:
http://pastebin.org/70053

because the forum complained that was too long to be posted

[knell]

I have problem with geforce 9800 gt 1gb Palit green

It dosen't work with new drivers such 190.42 or 195.30
only work with 173
so i can't use VDPAU or CUDA
[root@Valhalla radepal]# lspci |grep VGA
02:00.0 VGA compatible controller: nVidia Corporation GeForce 9800 GT (rev a2)
[root@Valhalla radepal]# uname -r
2.6.31.6-166.fc12.x86_64
[root@Valhalla radepal]#



Actually, the same on GF 8600 GT
01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600 GT (rev a1)
with 190.xx drivers.

[nacross]

How can I revert the instalation of the nVidia drivers?

I have followed the guide posted on this forum, but I can not go more that 1024x768 That's not good enough. I was better with no 3D acceleration.

[Cyberhawk]

I run FC12 and use a Radeon X850XT (the R480 chip).
I'd really like to have some games running on this
machine, since I do not have place for Windows on
it any more and it is running linux-only.

The lspci -v gives me this output on the card (it also recognizes it's name correctly):

...
Kernel driver in use: radeon
Kernel modules: radeon
...

the glxinfo | grep direct gives me this:

direct rendering: Yes

However, when trying to start Trackmania Nations
through the playonlinux frontend, the whole systems
hangs so hard, that neither the mouse nor the
keyboard show any response. I can see a new window
opening, where the game tries to connect to a server,
so the application does start.

By the way, that same game with same driver worked
on ubuntu 9.04.

Is there any option for getting this to work with FC12?
Or should I better consider downgrading to FC11 or even
changing back to ubuntu lol

[Aloone]

I have a problem with my ATI rage 128 card with 32MB RAM.

It's not to bad most of the time but the acceleration doesn't seem to be working as watching YouTube videos or BBC iplayer in full screen mode is very jerky. It's not the speed of my Internet connection because pleayback is fine under Windows

Manipulating 3D shapes in OpenOffice.org is very slow, despite the check box saying enable acceleration being enabled which also indicates there's no acceleration also if that were true, I would have expected the check box to be greyed out.

At first thought Fedora was just using a generic VESA driver but I I've discovered the ATI Xorg driver is installed. How do I check it's working correctly?

[Hlingler]

I have a problem with my ATI rage 128 card with 32MB RAM.
... How do I check it's working correctly?Post results of commands:
glxinfo | grep render
xrandr -q

V

[Aloone]

Here's what I've got:

[alun@home ~]$ glxinfo | grep render
glxinfo: ../common/drirenderbuffer.c:69: driNewRenderbuffer: Assertion `format == 0x1908 || format == 0x8050 || format == 0x8058 || format == 0x81A5 || format == 0x81A6 || format == 0x81A7 || format == 0x8D48' failed.
[alun@home ~]$ xrandr -q
Screen 0: minimum 320 x 240, current 1280 x 1024, maximum 1280 x 1024
default connected 1280x1024+0+0 0mm x 0mm
1280x1024 75.0* 60.0
1280x960 60.0
1152x864 75.0
1024x768 75.0 70.0 60.0
832x624 75.0
800x600 75.0 72.0 60.0 56.0
700x525 60.0
640x512 75.0 60.0
640x480 75.0 73.0 67.0 60.0
720x400 70.0
576x432 75.0
512x384 75.0 70.0 60.0
416x312 75.0
400x300 75.0 72.0 60.0 56.0
320x240 75.0 73.0 60.0

[cnapolitano]

I am sure you have answered this question but I am looking for a drivers for:

lexmark x2600 all in one

nvivida geforce 7300 gt

i am running fedora 12 with kernel linux 2.6.31.12-174.2.3.fc12.i686
gnome 2.28.2

I been using fedora for 2 days now and have ordered a book on it but just need help with these 2 pieces of hardware

is there anything you need to know about my system

thanks

charlie

[Hlingler]

@cnapolitano: Refer: http://forums.fedoraforum.org/showthread.php?t=239656
One thread per problem|question per customer, please. :) Thanks.

@Aloone: Hmm... have you attempted (ever) to unstall the proprietary ATI driver ? The glxinfo output shows a [FAIL]. Also, please post:
uname -r

V

[Aloone]

I've not tried to install the proprietary drivers but I have the RPM Fusion non-free repositories installed so they may have been installed via the update system.

Here's the output to the command you told me to run:

2.6.31.12-174.2.3.fc12.i686.PAE

I'll have to Google a bit to learn about the commands tomorrow but it's time for bed now.

[Hlingler]

OK, when you get a chance, post back with results:
rpm -qa | grep -i -e catalyst -e fglrx | sort
rpm -q libdrm mesa-dri-drivers mesa-dri-drivers-experimental mesa-libGL xorg-x11-drv-ati xorg-x11-drv-radeonhd
rpm -V libdrm mesa-dri-drivers mesa-dri-drivers-experimental mesa-libGL xorg-x11-drv-ati xorg-x11-drv-radeonhd

V

[Gooze]

Hiii!!

I'm new to Linux and to this Forum too and I had a similar problem with my video card S3 Prosavage

S3 Inc. VT8375 [ProSavage8 KM266/KL266]

I'm developing some apps in OpenGL and suddenly I couldn't run any of them... an error was displayed:

../common/drirenderbuffer.c:69: driNewRenderbuffer: Assertion `format == 0x1908 || format == 0x8050 || format == 0x8058 || format == 0x81A5 || format == 0x81A6 || format == 0x81A7 || format == 0x8D48' failed.
Aborted (core dumped)

I googled it and I found this thread and another one with a solution which worked for me:

http://bbs.archlinux.org/viewtopic.php?id=88392

The problem seems to be that when I updated the system, Fedora updated to the next packets:

mesa-dri-drivers-7.7-3.fc12
mesa-libGL-7.7-3.fc12

and I don't why this caused that I wasn't able to run my OpenGL apps.

So I had to downgrade that packets to:

mesa-dri-drivers-7.6-0.13.fc12
mesa-libGL-7.6-0.13.fc12

I did this via:

yum downgrade mesa-dri-drivers mesa-libGL

I had do add my Fedora 12 DVD to the repos list in order that yum could made the downgrade.

This worked for me :^) and I hope that it can help you too!!

BTW: Sorry about my English >_<

[badday]

Hi there,
I´ve got a problem with my configuration. I can´t enable destop effects any more since I use 2 monitors and changed the xorg.conf. I just get:
The Composite extension is not available
Here is my /etc/X11/xorg.conf:
Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "1"
EndSection

Section "Files"
ModulePath "/usr/lib64/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib64/xorg/modules"
EndSection

Section "ServerFlags"
Option "AIGLX" "on"
EndSection

Section "InputDevice"

# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

# generated from data in "/etc/sysconfig/keyboard"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "de"
Option "XkbModel" "pc105"
Option "XkbVariant" "nodeadkeys"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "LG M228WA"
HorizSync 28.0 - 83.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection

Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName "LG L227W"
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 75.0
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8800 GTS 512"
Option "AddARGBGLXVisuals" "True"
BusID "PCI:1:0:0"
Screen 0
EndSection

Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8800 GTS 512"
BusID "PCI:1:0:0"
Screen 1
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "DFP-0: 1680x1050 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection

Section "Screen"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "DFP-1: 1680x1050 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection

grep Driver /etc/X11/xorg.conf says:
Driver "mouse"
Driver "kbd"
Driver "nvidia"
Driver "nvidia"

If you need any further information, just tell me about.

Thanks a lot!

badday

[Hlingler]

The Composite extension is not availableTry:Section "Files"
ModulePath "/usr/lib64/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib64/xorg/modules/extensions"
ModulePath "/usr/lib64/xorg/modules"
EndSectionInsert line *exactly* where shown - the order/priority is important! Re-start of X required (or just re-boot the PC).

V

[badday]

Well, I did exactly what you said and restarted, but there is still the same problem.
What else might be the reason?

Thanks.

badday

[Hlingler]

Please post:
uname -r
rpm -qa | grep nvid | sort
su -c 'lsmod | grep nvid'

V

[badday]

uname -r
2.6.31.12-174.2.3.fc12.x86_64
rpm -qa | grep nvid | sort
kmod-nvidia-190.53-1.fc12.1.x86_64
kmod-nvidia-2.6.31.12-174.2.3.fc12.x86_64-190.53-1.fc12.1.x86_64
kmod-nvidia-2.6.31.9-174.fc12.x86_64-190.42-1.fc12.9.x86_64
nvidia-settings-1.0-3.2.fc12.x86_64
nvidia-xconfig-1.0-1.fc12.x86_64
xorg-x11-drv-nvidia-190.53-1.fc12.x86_64
xorg-x11-drv-nvidia-libs-190.53-1.fc12.x86_64

su -c 'lsmod | grep nvid'
nvidia 9624568 38
i2c_core 28976 12 isl6421,cx24116,cx88_vp3054_i2c,tuner,cx8800,nvidi a,cx88xx,i2c_algo_bit,v4l2_common,videodev,tveepro m,i2c_i801


Thanks.

[Hlingler]

OK, I'm stumped. All the pieces-parts seem to be there and in order. The only thing I'm suspicious about is Xinerama: I'm not sure that NVidia driver supports it. Check through your /var/log/Xorg.0.log for clues, and if unsure attach (do NOT post) to a post (or post to pastebin.org or fpaste.org or such and post the link here), so that we can review it.

V

EDIT: OOPS! wait: you have not installed the 32-bit compatibility libs - you should do so:
su
yum install xorg-x11-drv-nvidia-libs.i686

[clavan]

Hi there,
Need help,...I saw a (new) ATI driver for Linux, on the AMD web-site, ...
Anyone experience with this one and Fedora Core 12.... ?

ATI Catalyst™ 9.12 Proprietary Linux x86 Display Driver
81.2 MB
10.1
01/27/2010
Automated installer and Display Drivers for X.Org 6.7, 6.8, 6.9, 7.0, 7.1, 7.2, 7.3, or 7.4

Website:
http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx?type=2.4.1&product=2.4.1.3.15&lang=us&rev=10.1&ostype=Linux%20x86

Regards
clavan

[Hlingler]

No: http://forums.fedoraforum.org/showthread.php?t=155503There is currently no FGLRX support for F12 at the moment, please file your complaints on the ATI website.
[...]
Catalyst 10.1 is also incompatible with Xorg 1.7F12 = X.Org 7.7 (X11R7.7) = X-server 1.7 (confusing, but true).

V

[clavan]

No: http://forums.fedoraforum.org/showthread.php?t=155503F12 = X.Org 7.7 (X11R7.7) = X-server 1.7 (confusing, but true).

V

OK, Thanks for your info

Regards
clavan

[badday]

OOPS! wait: you have not installed the 32-bit compatibility libs - you should do so:
su
yum install xorg-x11-drv-nvidia-libs.i686
I did install them this way:
yum --enablerepo=rpmfusion-nonfree-updates install xorg-x11-drv-nvidia-libs.i686

Anyway, the problem still exists. Any other suggestions?

Thanks.

badday

[Hlingler]

Any other suggestions?See my previous response.

V

[Aloone]

OK, when you get a chance, post back with results:
All right.

rpm -qa | grep -i -e catalyst -e fglrx | sort
That gives me nothing.

rpm -q libdrm mesa-dri-drivers mesa-dri-drivers-experimental mesa-libGL xorg-x11-drv-ati xorg-x11-drv-radeonhd

libdrm-2.4.17-1.fc12.i686
mesa-dri-drivers-7.7-3.fc12.i686
package mesa-dri-drivers-experimental is not installed
mesa-libGL-7.7-3.fc12.i686
xorg-x11-drv-ati-6.13.0-0.20.20091221git4b05c47ac.fc12.i686
package xorg-x11-drv-radeonhd is not installed



rpm -V libdrm mesa-dri-drivers mesa-dri-drivers-experimental mesa-libGL xorg-x11-drv-ati xorg-x11-drv-radeonhd

package mesa-dri-drivers-experimental is not installed
package xorg-x11-drv-radeonhd is not installed
Going from that, it looks like I need to install some of those packages; which ones should I install? I'm using Fedora 12 32-bit .

[Hlingler]

OK, in that case: you may have found a bug in glx-utils (that package is part of the Mesa build, and owns executable glxinfo). If you have a file /etc/X11/xorg.conf, you can post that, as well as /var/log/Xorg.0.log (attach, please do not post), if you want to pursue this. Also: try booting with kernel option nomodeset - see if that helps. Or file a bug report at Fedora/Red Hat Bugzilla.

V

[Demz]

mesa-dri-drivers-experimental is your 3D experimental driver

[badday]

The only thing I'm suspicious about is Xinerama: I'm not sure that NVidia driver supports it.

You seem to be right. I disabled it and now everything works correctly.

Thanks you very much.

badday

[Hlingler]

For the record: Xinerama is deprecated in favor of xrandr, so that's another point that made me suspicious.

REF: http://en.wikipedia.org/wiki/Xinerama#Deprecation_of_XINERAMA :Deprecation of XINERAMA
As of 2008, Xinerama is planned to be deprecated in the future by X.org in favor of XRandR.You seem to be right.Occasionally, much like a broken clock. :rolleyes: BTW: you really should have the 32-bit compatibility libs anyway (for those few 32-bit-only apps that may need them), so I suggest keeping them, always.I disabled it and now everything works correctly.Glad it worked out for you.Thanks you very much.You're welcome.

V

[Artemius]

trying to install nvidia driver.
Donwload it from official web site
GeForce 7400 Go

Got an error. Advice me what to do


-> Kernel module compilation complete.
ERROR: Unable to load the kernel module 'nvidia.ko'. This happens most
frequently when this kernel module was built against the wrong or
improperly configured kernel sources, with a version of gcc that differs
from the one used to build the target kernel, or if a driver such as
rivafb/nvidiafb is present and prevents the NVIDIA kernel module from
obtaining ownership of the NVIDIA graphics device(s), or NVIDIA GPU
installed in this system is not supported by this NVIDIA Linux graphics
driver release.

Please see the log entries 'Kernel module load error' and 'Kernel
messages' at the end of the file '/var/log/nvidia-installer.log' for
more information.
-> Kernel module load error: insmod: error inserting './usr/src/nv/nvidia.ko':
-1 No such device
-> Kernel messages:
usb 2-2: USB disconnect, address 3
udev: starting version 145
SELinux: 8192 avtab hash slots, 150790 rules.
SELinux: 8192 avtab hash slots, 150790 rules.
SELinux: 8 users, 11 roles, 3034 types, 147 bools, 1 sens, 1024 cats
SELinux: 75 classes, 150790 rules
SELinux: Context unconfined_u:unconfined_r:kismet_t:s0-s0:c0.c1023 became
invalid (unmapped).
SELinux: Context unconfined_u:unconfined_r:winbind_helper_t:s0-s0:c0.c1023
became invalid (unmapped).
SELinux: Context unconfined_u:unconfined_r:consoletype_t:s0-s0:c0.c1023
became invalid (unmapped).
SELinux: Context unconfined_u:unconfined_r:loadkeys_t:s0-s0:c0.c1023 became
invalid (unmapped).
SELinux: Context unconfined_u:system_r:gpg_t:s0-s0:c0.c1023 became invalid
(unmapped).
SELinux: Context system_u:system_r:gpg_t:s0-s0:c0.c1023 became invalid
(unmapped).
type=1403 audit(1265669761.449:11857): policy loaded auid=500 ses=1
wlan0: disassociating by local choice (reason=3)
[drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 1
nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as rivafb, nvidiafb or
NVRM: rivatv was loaded and obtained ownership of the NVIDIA
NVRM: device(s).
NVRM: Try unloading the rivafb, nvidiafb or rivatv kernel module
NVRM: (and/or reconfigure your kernel without rivafb/nvidiafb
NVRM: support), then try loading the NVIDIA kernel module again.
NVRM: No NVIDIA graphics adapter probed!
ERROR: Installation has failed. Please see the file
'/var/log/nvidia-installer.log' for details. You may find suggestions
on fixing installation problems in the README available on the Linux
driver download page at www.nvidia.com.

[marcusB]

I am using F12.

I also Just got the same message after trying to use nvidia.ko from kmod-nvidia. When I try an insmod nvidia.ko, the same thing shows up in dmesg:

nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as rivafb, nvidiafb or
NVRM: rivatv was loaded and obtained ownership of the NVIDIA
NVRM: device(s).
NVRM: Try unloading the rivafb, nvidiafb or rivatv kernel module
NVRM: (and/or reconfigure your kernel without rivafb/nvidiafb
NVRM: support), then try loading the NVIDIA kernel module again.
NVRM: No NVIDIA graphics adapter probed!

My card, an ASUS GeForce 9600:

01:00.0 VGA compatible controller: nVidia Corporation GeForce 9600 GSO (rev a2)

I was trying to switch from nouveau to the nvidia driver. The nvidia driver had worked on this card previously.

Could the nouveau driver be getting in the way? I uninstalled xorg-x11-drv-nouveau. Do I also need to blacklist nouveau.ko?