Sound was working until I tried to install a rawhide version of Nouveau which hosed my system.Backed out to where I started and the sound is gone.The hardware is not showing up in the System> Preferences> Sound.I reinstalled alsa and pulse audio.
Code:
lspci | grep Audio
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
[code]....
I have a machine running FC 13 and a GeForce 210 Graphics card. I'm running the 2.6.33.3-85 kernel (if I use the newer kernels like 2.6.34.7-61, and 2.6.34.7-56, the X server won't even start; that was the subject of a different thread which didn't get answered). After a few hours, the screen is displayed in a disorganized state: each quadrant is displayed in the wrong space, and the X server won't respond to mouse movements (this isn't a screensaver). This is different from a previous problem where the X server simply hangs after an hour of so when I use GUI programs (that was also the subject of a different thread which didn't get answered). I think I'm running the Noeveau video driver, but not sure.
View 3 Replies View RelatedI am running F12. With prior kernels - 2.6.31.9-174.fc12.i686 or before - I could simply rename the nouveau.ko driver to nouiveau.ko.bad. Then the kernel would load the nv driver instead, and everything worked great. FWIW: adding rdblacklist="nouveau" to the kernel params in grub.conf didn't seem to do anything.
On a recent update, a new kernel was added: 2.6.31.12-174.2.19.fc12.i686. I did the same rename trick as before, but this time the kernel still loaded the nouveau driver, and then X failed to load. So I had to fall back to the older kernel.
Is there a way to keep nouveau from loading with the newest kernel (ie, the one above)? And also, is there a way to keep nouveau from loading for any new kernels?
After updating X-Windows (via yum auto-update) I'm having a serious X-Windows problems when using the nouveau video driver. I had to switch over to the vesa driver to be able to start X-Windows. Below you find the Xorg.log file:
Code:
X.Org X Server 1.7.4.902 (1.7.5 RC 2)
Release Date: 2010-02-05
X Protocol Version 11, Revision 0
Build Operating System: x86-06 2.6.18-164.6.1.el5
Current Operating System: Linux localhost.localdomain 2.6.32.7-37.fc12.i686.PAE #1 SMP Fri Jan 29 14:37:28 UTC 2010 i686
Kernel command line: ro root=/dev/mapper/VolGroup-lv_root LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=be-latin1 rhgb quiet rdblacklist=nouveau vmalloc=512MB .....
Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting
Please consult the Fedora Project support at [URL] for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(II) NOUVEAU(0): NVLeaveVT is called.
I've noticed in many versions of Fedora is that the blue colors don't seem so right. They appear more like violet in comparison to the Nvidia proprietary driver.I've tried playing with the new color profiles in F13 but none of them fixed this particular problem
View 8 Replies View RelatedI have two monitors - one connected to the VGA port and the other to the DVI port. Fedora seems to be detecting both monitors (figured this out because when I rotate the desktop cube, the second screen is also seen.). However, the monitor on the DVI port is blank. This happens even if I use just one monitor with the DVI port. I cannot install the proprietary nvidia drivers because my computer hangs (has been happening since fedora 11 or 10), Is there a way to get both monitors to work with the nouveau driver?
I faced this problem in Fedora 13 as well and was hoping both screens would work out of the box in F14. Is there any way I can do this to make it work like nvidia's TwinView?
Fedora 13, x86_64, up to date. Trying to get nVidia Quadro NVS 140M to display on a projector the same as it does on the laptop screen, which is 1680 x 1050. I failed to do so with the nVidia driver (latest version), so I want to go back to the nouveau driver and try with xrandr. I have always used the nouveau driver with Fedora without an issue, but in my former life in Ubuntu I sometimes switched back and forth between the "nv" driver and the nVidia driver.
Doing so was trivially easy - just edit xorg.conf replacing "nv" with "nvidia" or vice-versa, then restart X. However, after installing the nVidia driver via Yumex and using the nVidia config utility, I find that now I have an xorg.conf file that is loaded with stuff I don't understand, except that at the top it says it was created by nVidia, and there are two places where it says the driver is "nvidia." I have searched and all I can find is instructions for installing the nVidia driver.
Apparently that is meant to be a one-way ticket, because I can't find any instructions for how to return to the nouveau driver. Except stuff that is over a year old, and complaints from users whose systems failed to start X. What would happen if I just replace "nvidia" with "nouveau" in the xorg.conf file and restart X? I know if it won't start X I can boot to rescue mode and re-edit xorg.conf, but I'd rather ask first and do it the right way than have to repair a broken system.
I installed the nvidia driver from the vendors homepage. But since it does not support regulation of brightness (and the display is that bright that I want to downlevel it), I wanted to go back to the default display driver which is the nouveau driver.So I uninstalled the nvidia driver and then I realized that I didn't make any backup of the xorg.conf file prior installing the nvidia driver. Shame on me, yeah.Now when the x-server started, it couldn't find the nvidia driver. Okay, fair as it was removed. Next to that my keyboard becomes unresponsive. That's really aching as I can not switch to a text-based console any longer.I'm able to boot into initmode 3 by editing the kernel parameters in the boatloader. I'm also able to edit the xorg.conf with vi in the shell then and start the xserver to test things by calling xinit.
I already tried to recover a bit from this situation by removing the references to the nvidia driver and replaced it with some information I could find on the nouveau homepage - but no luck so far, keyboard still freezes and login window does not appear. I could take a look into the xorg.0.log which warns me about the keyboard getting disabled but I do not really understand why. Next to that I find some other additional information. My computer experience is quite okay, but I'm somehow new to Fedora, I started half a year ago with Fedora 13 on my other laptop which worked like a breeze.
I wondered where I can find information about how to configure the xserver in the default configuration, if there is some reset functionality or so, that brings me back to installation defaults. Those worked ok for the nouveau driver. Unfourtionatly I was not able to gather the correct package name that would probably had helpded me by removing and installing it again.Next to fixing my setup, I had another idea as this is a quite new install to just re-run the install again on to that machine. Is this possible with keeping the files in my homedir?
I am having a problem with the nouveau driver in Fedora 15 Code: lspci | grep VGA 40:00.0 VGA compatible controller: nVidia Corporation NV41GL [Quadro FX 1400] (rev a2) The problem is that when I boot a Fedora 15 live Cd, either gnome or xfce, the monitors initially seem to work in that they display at the proper resolution, both as the CD boots and as X initially starts. I can see the background and the mouse cursor - it is "busy" ...
As the desktop finishes loading, however, my primary monitor becomes disabled. With gnome the screen goes black, with xfce it goes white. I can still see the mouse on my secondary monitor, but I can not seem to open any applications (such as a terminal) or change to a console (ctrl-alt-F1 or ctrl-alt-F2). I can boot into safe mode. Adding the boot option video=xxx sets the resolution on the console as it boots, but does not help running X.
First some specs:
Fedora 13 (Goddard) 32-bit
NVIDIA GeForce GTX 260
The DVI output on my card works just fine to my monitor, which is what I've been using. I installed no drivers; it just worked. However, now I need a duplicate screen to be given via the s-video output, but it doesn't work. Nothing is being given to the tv and nothing is being detected under monitors. From what I understand, this is because I need to install the appropriate Driver.
I downloaded my driver from the nvidia website, but it won't install. it tells me I need to disable nouveau.
I just installed F12 over a former F9 system. I have a a nvidia TNT2 card. Formerly it was using the nv driver, which I understand has been replaced by the nouveau driver. Specifically this is what is reported in Xorg.0.log
Code:
The install ended up with a xorg.conf setting the driver to vesa. I presume this is because the standard install/upgrade option did not work and I had to install using the "basic video driver". Since I used this system to watch DVDs, the vesa driver does not work for me (too slow). So I tried removing the xorg.conf and followed these instructions for unsupported nvidia cards in order to try to get the nouveau driver working.
This failed. I I got was a black screen with a cursor following the mouse. Checking the Xorg.0.log I see the nouveau crash dump listed below.
I checked for fedora bugs, but I saw nothing like this one. I can't watch DVDs on this system at this point.
Code:
Backtrace:
Fatal server error:
I read that the Nouveau Gallium3D driver will work with Nvidia cards in Fedora 13 (YAY!)What I was wondering is this - will the driver work in 12 or will I need to get 13?
View 14 Replies View RelatedI am using an Nvidia GeForce FX5200 card and nvidia hasn't released a driver that seems to work with it in Fedora 13 yet.. However, I decided to do an install of F13 and use the nouveau drivers until Nvidia updates their drivers, however, the nouveau drivers don't work worth a crap with my card I did a fresh install and then ran a yum update. What I am seeing is after a few minutes, all the icons disappear, no fonts, and nouveau starts throwing errors to my message log. Here are the messages I get:
[Code]...
I wanted to replace the Nouveau with the proprietary Nvidia driver. I removed Nouveau and changed to console mode with "init 1". Realizing that i did not properly save the binary file i switched back to graphic mode with "init 5" only to have the system freeze. I rebooted and chose the usual kernel in the grub menu. The system continued to load but froze right after the Fedora logo (which hides the textual loading details) finished loading. I can not even switch to a console with ctrl-alt-F1.
View 4 Replies View RelatedI'm using a remix of F14 called Fusion Linux. It's all the same as fedora14. It's come preinstalled with xorg x11 nouveau driver. So, i'm not using Nvidia driver. Now, the problem is that the graphics in wine application are really poor. Fonts appear to be really hazy. See this image to get me better: [URL].. In earlier version of fedora and wine, i used nvidia driver. Graphics used to be good at that time.
View 6 Replies View RelatedI had installed my NVIDIA 9500GT driver on my fedora 13 by disabling nouveau, so should i enable it back after installing NVIDIA driver?
View 2 Replies View RelatedCan this be done similar to some other O/Ses so Nouveau doesn't pre-screw up the kernel for 3rd party drivers??? Would be great in F16 if we were given a choice re: wanting nouveau or not. I simply can not get F14 or F15 to work with the 270.xx drivers on recent equipment.
View 10 Replies View RelatedNouveau won't go away.I done the rdblacklist in grub and blacklist in modprobe.d but it still persists.Is there something else I need to for Fedora 15?
View 7 Replies View RelatedThere is one thing missing (I think) a clear guide to clearing out Nvidia and replacing it with nouveau. For all but hardened gamers, nouveau on 11.4 delivers. It also removes one more barrier to what I think is the intended goad of Tumbleweed.The problem IMHO is not that there are no clear guides. The problem is there are too many. No sooner does one person do a guide (that is clear) and someone else who does not like some point writes another guide that they think is more clear (but in fact is less clear in other aspects). And this goes on ad infinitum.IMHO we have too many guides - many of which are sufficient clear ... but the VAST number only serves to confuse users more.
Having typed that, IMHO this is NOT a Tumbleweed specific issue, but its MUCH WIDER in scope and hence does not belong as a discussion in this Tumbleweed thread.
Using Kubuntu 10.04 here
I've been trying to make my microphone work and so I've pretty much messed around with the mixer (KMixer), mainly adding channels to the "equalizer" and checking and clearing "capture" boxes. After I did that my sound "disappeared" - I have no sound whatsoever (not even Kubuntu's initialization sound).
How can I fix this? Is it possible to go back to the "default" configuration?
Slackware 13.1_64, everything works like a charm,BUTevery time my slackware boots up,the sound system changes from one device to another.So if I boot now, sound address is hw:1.0.
then if I reboot, the sound address becomes hw:0.0It's really annoying, because every time I have to re-run xmms and mplayer setup to get any sound!Also, if any program is playing audio (like xmms), other programs cannot play audio at the same time.ie: if I'm listening music with xmms then I try opening some video with mplayer or firefox/flash, I get no audio on this video....What's the deal with kde phonon? I thought it was supposed to be the new global sound system for kde4, like arts was for kde3
My microphone wasn't working so I entered alsamixer to amp up it's volume and see what's wrong.Not sure what I did wrong but now the gnome volume control applet in the Indicator does not affect system volume at all.I can even mute it and it will not mute anything.The volume controls in alsamixer work fine and changing the volume in alsamixer affect system volume immediately.What could I have done? How can I get back volume control inside gnome?
View 2 Replies View RelatedAs I mentioned before, I has having freezes while installing F12 (x86_64) with a GeForce 8600 GT. I was able to complete the installation by doing it with the "basic" video driver. However, I was still getting frequent freezes. I installed the testing Nvidia drivers, and the freezes went away. When it froze, it was a hard freeze -- it wouldn't respond to CTRL-ALT-DEL or SysRq (I did enable SysRq first). I had to do a hard reset.
View 7 Replies View RelatedI installed the nVidia 3rd party driver before removing the Nouveau Driver, this means that when my computer is done booting i'll just have a black screen, being able to do nothing. Can i somehow solve this using a live CD? or is there a simpler way? Ubuntu can't boot in recovery mode neither, so it kinda sucks. Anyway, i'd like someone to tell me how to do this.
View 9 Replies View RelatedI've started playing around with debian 6 stable, and was just wondering if its worth it to go to the trouble of removing nouveau, or if it will handle everything well enough. I use my laptop for a little bit of gaming (older games) under wine, all the basic email/web browsing/writing stuff, some photo editing under gimp, movies/music, and a very little bit of Blender work.Will Nouveau handle all this well enough, or should I use the proprietary nvidia driver?
View 6 Replies View RelatedI have tried everything I can think of to install the nouveau driver, which is the only one I can trust on my system with the Geforce 8800 card I received as a gift. I tried Nvidia direct download drivers before and it was impossible to alter the screen resolution and the "fixes"/patches were not able to correct that fact. And removing it led to my having to reinstall my system both times. So I'm done with those.
I realized that I could use the nouveau driver when I realized that the second OS on my dual boot system worked perfectly with it. It has the nouveau driver onboard. That OS is Ubuntu 10.04, btw. Also the system I want to install this driver on requires a screen resolution of 1280x960. The Ubuntu is at 1280x1024 for some reason, with the same monitor, it works.
How do I get my stable debian system to download the xserver-xorg-video-nouveau and meet all its dependencies without breaking my system? I even tried reloading Synaptic with the highest available software, but I still could not get the driver to install. What am I doing wrong? Is it just impossible to install this particular driver on my system? And if there's an old version of it I am willing to try that too.
I would use the nouveau driver but the color hue seems to be slightly off. Is there any way to adjust the hue for the driver in real time(I don't want to have to change values in Xorg.conf the stop x, restart x and see if it worked). For example the proprietary nvidia drivers have the color settings in nvidia-settings.
View 2 Replies View RelatedI was using an extremely common debian based distro, but I have been rebooting my pc non stop for the last two days trying to get my nvidia fx5200 drivers to work. (it is just IMPOSSIBLE to disable the nouveau driver, i have tried blacklisting it, editing xorg etc, nothing works) I need to know if there are many issues with getting nvidia graphics cards to work in debian. it seems like the last 18 months worth of releases on all the other debian based distros have completely broken all support for any nvidia card made prior to 2011. i know for a fact that in windows xp all my hardware works perfectly, but i really dont want to have to use that, i have been a linux user for more than 5 years now, but all i am really looking for now is reliability. i want to be able to use the nvidia-173 driver, as i know that this allows me to watch the movies i take on my dv camera, and ......
View 7 Replies View RelatedYesterday I installed some updates on my Jessie system (I don't remember if the kernel was also updated). After rebooting the system nothing happens after the "Loading intial ramdisk"-message. If I boot in recovery mode the boot stops at the message:
Code: Select allfb: switching to nouveaufb from simple
If I add "nouveau.modeset=0" temporary to the GRUB-entry for the recovery mode, it will boot up in the console-mode.
I was able to get an ethernet connection with "dhclient eth0" and removed the "xserver-xorg-video-nouveau" package. Then I installed it and the removed gnome-desktop again. Before removing it, aptitude said the following to the package:
Code: Select alli A xserver-xorg-video-nouveau
Now it only says:
Code: Select alli xserver-xorg-video-nouveau
But this didn't change my problem. I found a similar case in the internet, but there were no solutions for it: [URL] ....
The next thing I would do, is to install the proprietary nvidia-drivers, but since I have a GTX 960 video card, I would have to use experimental drivers. So I'm afraid to make it more worse trying to install this drivers.
Also I'm not sure if it really is a driver-specific of kernel-specific problem. My kernel is version 3.16.0-4-amd64.
The enemy territory works with the nouveau driver? I can not start enemy territory using nouveau driver.
View 1 Replies View Related
