Forum Home
Press F1
Thread ID: 41005	2003-12-26 19:10:00	Red Hat 9 tweaking, fixing, and making hospitable	Jaguar (4442)	Press F1

Post ID	Timestamp	Content	User
203363	2003-12-30 04:23:00	Right I did all of that (had to redo the XF86Config again in order to get that blue screen and stuffed up-ness (by the way, it no longer hangs on me). The file is right here. (www.angelfire.com)	Jaguar (4442)
203364	2003-12-30 04:49:00	Been doing a bit of reading on the nV Linux forum (www.nvnews.net). Do you have a newish VIA chipset board - like the KT400? The are numerous report of problems like you are experiencing with the newer VIA chipsets and AGP problems in combination with the recent nVidia drivers. Your XFree86.0.log doesn't show any errrors (EE) but you haven't posted all of it, there should be more. Right where your one ends there should be this sort of log: (II) NVIDIA(0): AGP 2X successfully initialized (II) NVIDIA(0): Setting mode "1024x768" (II) Loading extension NV-GLX (II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized (II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture (==) NVIDIA(0): Backing store disabled (==) NVIDIA(0): Silken mouse enabled (**) Option "dpms" (**) NVIDIA(0): DPMS enabled This is been cropped short of the end, as I was using it as an example.	Jen C (20)
203365	2003-12-30 05:59:00	> Do you have a newish VIA chipset board - like the KT400? You mean a newish video card? Yes. Newish mother board? I think so... If you want me to post my computer specs, just give me a holar. That's all that the log had, there was no more, I copied it from that directory straight to the floppy. There was no more...	Jaguar (4442)
203366	2003-12-30 06:24:00	Might as well rule out the VIA chipset/AGP nVidia thingy, so yes, if you could tell us what your motherboard is and whether it has the VIA chipset - thanks :) >That's all that the log had, there was no more, I copied it from that directory straight to the floppy. There was no more... Well that could be significant, as you can see from my example log, that is where the AGP info is logged.	Jen C (20)
203367	2003-12-30 06:59:00	Righteo, this is of the top of my head here: Shuttle AK39 Motherboard (has VIA network card) AMD Athlon XP 2400+ 1GB RAM (DDR 333) 2 x 7200rpm ATA-100 HD (1x Seagate 8MB Cache, 1x Western Digital 2MB Cache) nVidia Geforce 4 Ti4200 w AGP 8x 128MB VRAM (Leadtek Winfast A280 LE TDH My VIVO) AOpen CD-RW (52x24x52x) AOpen DVD-ROM (16x) AOpen 17" F70ES LCD screen You may think this is a fast computer... it is. :)	Jaguar (4442)
203368	2003-12-30 07:03:00	By the way, those hard drives are both 80GB, although that should be of no significance whatsoever. Also note that the screen will struggle to read below 800x600 and above 1280x1024 in resolution, and it runs best with 75Hz as a refresh rate.	Jaguar (4442)
203369	2003-12-30 07:18:00	Bingo! Your motherboard has the VIA KT400 chipset. See the specs here (us.shuttle.com). So, reading previous posts on the VIA new chipsets and the newer nVidia drivers, they were getting the same problem as you. The driver would install with no error messages, the editing of the XF86Config was done correctly, and yet X would not load and they ended up with blank screens. Couple of options here. 1. Try the workaround given on the nV forum which involved disabling the reference to AGP in the XF86Config file. 2. Try a much older nVidia driver which hasn't had problems reported with it (not sure how far back you would need to go). 3. Get to love the standard nv driver that Red Hat installs and do without your full graphic card potential (no 3D games like tuxracer), until someone fixes this problem. 4. There is a 3rd party driver which you could try here (www.minion.de) which has a work around for the VIA chipset problem. If you want to do another round of editing the XF86Config with the possibility of it going pear-shaped again, the option #1 might work for you. Let us know what you want to do from here.	Jen C (20)
203370	2003-12-30 07:21:00	Number 1 and number 4 seem to be the most logical.	Jaguar (4442)
203371	2003-12-30 07:27:00	But I think at this point in time, I need some shut eye tonight, I'll leave it for tomorrow when I have good concentration. Also, it would be easier if we could do it via IM, simply a quicker response time... don't want to lag down the PF1 forums more than they already are! Have a good night, and look forward to hearing from both you and Chill on New Years' Eve!	Jaguar (4442)
203372	2003-12-30 19:58:00	Morning Jaguar :) >You may think this is a fast computer... it is. That is a nice system you have there, Linux will fairly rock along on it :D But, back to the current problem ... In all honesty, since we have moved on from simply installing a nVidia driver and editing a XF86Config and then troubleshooting problems for that, the sort of issues you have now would be best dealt with by the Linux and nVidia forum (www.nvnews.net b&forumid=14) as they specialise with this. You will see from the dates on threads about this problem, that it is a current problem. But anyway, some background info on the nVidia 5328 problem can be found here (www.nvnews.net). You will see they discuss using the minion patched driver (option #4) but you will need your kernel-source rpm's installed to compile the driver with - and even then people report problems using it (for others it worked). But if you want to give the easiests of all your options a whirl .... Option one Well for option number 1, some people have been saying that if you disable the AGP option, X will load. You can read the some of the comments on the Linux vNvidia forum, but this one mentions what disabling the AGP support will mean here (www.nvnews.net). Add this to your XF86Config file under Section "Device" : Option "NvAgp" "0" Section "Device" Identifier "Videocard0" Driver "nvidia" VendorName "Videocard vendor" BoardName "NVIDIA GeForce 4 (generic)" VideoRam 131072 Option "NvAgp" "0" EndSection Don't forget to make the other changes to the XF86Config file for the "nvidia" driver reference and the removal of the Load "dri" line. This will kill X (again!) if it doesn't work, so yeah sorry, not much else I can say here. :( It is also only a work-around and not a solution. Having read quite a lot of posts over the net on this issue, it does sound like a combination of problems, including your current RH 9 kernel not having proper support for the KT400 chipset and the AGP x8 with the nVidia drivers. A newer kernel (2.6) and an official improved/fixed driver could solve this. But as the open-source community is constantly moving forward with improvements/fixes it might be only a matter of time until this is overcome. This must be a horrible experience for you with your first introduction to Linux, so I really hope it doesn't put you off, as Linux has a lot to offer and it is normally a much smoother ride. You ought to treat yourself to a double-expresso as I think you deserve it after all this, and Happy New Years! :)	Jen C (20)
1 2 3 4 5 6 7 8 9 10 11