I was building and testing custom kernels and somehow I managed to get the display configuration messed up so that when the computer boots up gets to starting the nouveau driver it displays garbage on the display. The boot up continues and I can login from another computer using ssh.
How do I reset the display configuration (or fix this problem)?
I have added nomodeset to the kernel parameters and the vesa drivers do work but I want the hi-res nouveau back without having to re-install f-14.
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'm unable to reset using either the reset option in gnome shell or the command using a terminal. When I select it the shell exits and displays the graphic "exploding" and then it just sits there. Shutdown works fine; just no reset. Any ideas? I've installed from the DVD. I booted the live CD and it resets just fine so I know it's no my hardware
Yesterday 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.
Motherboard: M2N-MX with Athlon X2 3600 from 2006 onwards 00:0d.0 VGA compatible controller: nVidia Corporation C61 [GeForce 6150SE nForce 430] (rev a2) Kernel: Debian Sid with 2.6.32-5-amd64 and custom 2.6.36-rc7 Monitor: Samsung 712N, 17inch, with native 1280x1024 resolution
Everything was fine with both kernels with custom 1280x1024 resolution upto yesterday. But when I rebooted today, first I noticed that X stopped working. After updating xorg.conf to 1024x768, it started working . After going through the kernel log in /var/log/messages, I noticed the following differences
Yesterdays log:
nouveau 0000:00:0d.0: Detected 64MiB VRAM nouveau 0000:00:0d.0: 64 MiB GART (aperture) nouveau 0000:00:0d.0: Saving VGA fonts
[code]....
There is an extra "Load detected" line and the resolution got reduced from 1280x1024 to 1024x768.
Built a machine w/ i5-4440 & gtx 960. I installed xserver-xorg-video-intel & xserver-xorg-video-nouveau. Xorg -configure fails, so I added xorg.conf I found online, makes no difference. xrandr can't open display. startx of course fails.
Backstory: My plan was to dual boot sid + stable as fallback with shared partition. First installed stable and whether connected to mobo or gfx card, I couldn't get login on tty, it would just hang on errors. So I installed sid (this time using lvm to hopefully make partitioning easier) and while I get the "failed to load nouveau" errors on mobo, gfx card gives me a login screen.
How do I set my centos system to the configuration it had directly after the installation? Because there are so many messed up tings on here right now, firefox will only work with my proxy server if I put its IP directly into firefox but not if I put its IP into the system proxy settings and then point firefox at that. httpd refuses to serve up any kind of documen apart from the test page randomly and even then I sometimes get a 403 error. Seriously is this the normal practice for setting up a LAMP server???
I have been doing some customization to my ubuntu Box related to font settings. Now all the font settings for whole system have been badly scrambled. I am feeling it very hard to reset all the settings too default again.I have been modifying system---> Preference ---> Appearance. if there exists any way to reset my font configuration to default.
I'm running Debian server 5.0.6 and the latest stable version of Apache. I am hosting a website and it will stop responding after an unknown amount of time. In order to make the website work again I have to run /etc/init.d/networking restart. The server is running a static IP address and is not resetting when the website goes down. I don't know where to start looking.
I've got a strage problem with openssh-server on debian lenny. I've done setup of sshd and basically everything works fine. I can check the fingerprint of the ssh-keys on the server and it matches with the fingerprint shown on the client for the first connection. so the key is stored in the known-hosts-file on the client.
The problem occurs after a "connection reset by peer" (i guess when the connected client goes to sleep or a timeout occures)!
After such a reset, when I try to connect to the server, the banner "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!" appears and the shown fingerprint of the server-key is totally wrong (it differs from the one on the server, BUT it is everytime when this problem occurs the same fingerprint). If I nevertheless remove the correct key from the known-host-file and accept the new key, I still can't login (permission denied).
To fix this situation temporarily I just need to restart the networking on the server. After the network-restart I get (again) the correct fingerprint of the server-key and can login without problems. Until the next connection reset.
The other day I was using BitTornado and it was running so slow it was almost unholy. After some research I found out that if the yellow light was on it means I couldn't receive any incoming connections and had to open some ports on the firewall. That, my friends, is not the problem. I tried to manually open up the bittorrent port and did some other things that I can't quite remember but eventually I accidentally killed all bittorrent functionality on my laptop.
Is there any way I can reset my network and ports back to the default settings or am I utterly screwed? I'd really prefer not to have to reinstall my whole OS just to fix my bittorrent or worse, have to download on Vista *shudders*. I'd rather go back to my uber-slow bittorrent than none at all. I've tried everything I can think of, even the godlike might of Google couldn't get me out of this one. Now I am forced to bother you, all because I wanted to see a damn sci-fi film from Switzerland (Cargo[2009]).
this may be asking too much (especially from leigh123, 'cause i know you're working hard), but i've lost track of the current status of the great nvidia driver vs. nouveau driver debate, and what we can hope to see in f13 in about 20 days. could you provide or point us to a layman's summary of what graphics capabilities we can expect with a "default" configuration when we bring up f13?
in particular, can we expect nouveau to provide 3-d for f13 (or in the near future)? nvidia install guides, leigh123, but despite your best efforts, the procedures seem to be getting more involved as time goes on, not less (and not noticably more reliable, either). between graphics card drivers and flash plugins fighting firefox (not to mention adobe fighting videos and hulu) it's discouraging to actually lose capabilities that were once available when upgrades are made.
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.
During boot I get a message along the lines of "nouveau 0000:00:0d.0 misaligned reg 0x0060081D". I then get dumped into emergency mode. This has happened before on this box, then went away with one of the F-15 upgrades, and has now returned.
What's frustrating is that I tested F15 at both the Alpha and Beta stages and didn't have this issue with the install, only after updating.. And the KDE Live spin loads w/o major issue suggesting that it is a software issue. I've tried two earlier kernels to no avail and don't know what to try next.
The problem with X not starting up started after I upgraded kernel from 2.6.38.6-26.rc1.fc15.i686 which is what the FC15 came with. Before that I had X, without installing the nvidia.com driver (whatever came with the stock FC15-XFCE spin).I tried booting the old kernel and at first it worked but X again would not run. Now, after, above operations (reinstall of kernel-devel + kernel headers and all dependencies like glibc-common, glibcs-headers, dkms, gcc..) booting the old kernel does not work anymore: the framebuffer animation of the Fedora logo fillingup freezes at some point almost at the end; HD LED blinking hard. Maybe this means fsck is running and I need to give it more time..? I'll leave it booting when I go for lunch and see how it goes...
I just wanted to check, I'm using nouveau on Fedora 12 with the latest updates and each time I wake the machine from suspend, the fan on my XFX 8800GT goes to full speed and stays there. I've read some nouveau stuff and they say that nouveau doesn't control the fan speed, so I think the card is running in a safety mode after wake up where it runs the fan at full speed to be safe. The only suggestion I saw for fan speed and nouveau was to use nvclock to manually adjust the fan but that sounds dangerous to me. I think I'll just go to the closed rpmfusion driver then if this is the case.
I 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?
In the past I've played around with OpenGL development using the Mesa library. I have F13 installed now and would like to further explore OpenGL, but am trying out the default Nouveau/Gallium3d setup. As I understand Gallium3d is intended to replace Mesa3d so I'm at a loss as to what packages need installing to provide the header files and such needed to build OpenGL applications as a search for Gallium turns up nothing in the repos.
While it does mention nouveau, and I do use Nvidia graphics (PCIe GT 240) I believe the cause may be something else. Googling around leads me to a couple of forum threads that seem to relate to the core series of Intel processors, but I'm at a loss. I've also searched this forum however the search seems to either bring up every result under the sun and non seem to apply or no results at all. I know the card's supported as Ubuntu works flawlessly. I also tried booting in safe graphics mode, however the exact same thing happens.
I doubt using a USB stick in this manor would cause this problem, but if you suggest it i'll install from physical media.
I would post logs, however the shell it drops to seems to be severly limited (lacking reboot, even).
I have Fedora 15 installed in my PC and I use it both for gaming and work. Now the open source nouveau driver was working fine, until I had to install the nvidia driver so that I could play torcs, as I was unable to get good graphics in nouveau. Now, when using the nvidia driver, the gnome shell has become too slow and sometimes unworkable, though games run good. Is there any way so that I can use both the drivers and switch between them when needed (say use nvidia when gaming and nouveau while at work) without uninstalling and reinstalling them?
PS: when I boot up, the grub shows two options, one is the fedora with latest kernel and other is the old kernel. Is there a possible way that I use nouveau with old kernel and nvidia in the new kernel? This will really help in switching games and work.
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
I have just upgraded from Fedora 11 to Fedora 13 and now can't get my two monitors working as a single "screen" (it worked under F11). I have a GeForce video card with two monitor outputs
I then edit the xorg.conf to change the driver from nouveau to nv and I can start X and the LCD displays the desktop at a resolution of 1680x1050 (good) but the CRT just displays random blocks of colour. At this point I also get a kernel crash - see dmesg output attached, but the system is then OK to use. I have tried editing the xorg.conf to add a second monitor and a virtual screen resolution to match the two monitors (1024x768 + 1680x1050) combined (2704x1050) but still only the LCD monitor works, but with the virtual desktop that can be nudged around with the mouse. I would like to get back to using both monitors with a virtual screen across the two monitors.
On my HP i7 based laptop the latest kernel 2.6.33-147 and possibly Nouveau/X.org seems to have broken suspend. ie If the laptop is suspended then when woke, the screen is dead and networking does not work and I cannot change to a different console.If I boot the previous kernel this behaviour does not occur.
I 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 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.
