I've had a working desktop even running compiz just before I updated today. Anyway, after the reboot which was required after my update, I got a notification in the boot message which says:
Code:
Checking for module nvidia.ko: [FAILED]
nvidia.ko for kernel 2.6.30-9-96.fc11.x86_64 was not found. [WARNING]
The nvidia driver will not be enabled until one is found. [WARNING]
I continued logging in and got a white screen (most likely brought by compiz without the nvidia drivers). I hit terminal and disabled compiz then tried to see how nvidia is doing. Here's what I got from nvidia-xconfig:
Code:
Using X configuration file: "/etc/X11/xorg.conf".
Backed up file '/etc/X11/xorg.conf' as '/etc/X11/xorg.conf.backup'
New X configuration file written to '/etc/X11/xorg.conf'
and finally here's what /etc/X11/xorg.conf contains: .....
One of my machines is a desktop with a WIFI connection. This machine is not configured to use NetworkManager; instead, it still does things the old way via /etc/sysconfig config files.
Problem: this WIFI connection requires wpa_supplicant. By default, F11 brings up the network at priority 10 and wpa_supplicant at priority 23. So dhclient fails its initial attempt to obtain an IP for wlan0 (it will retry and succeed but by then it's too late). This causes other network-related startup tasks to fail. For example, ntpdate fails. This is problematic for systems with faulty CMOS clock batteries since ntpd will reject updates if the clock skew exceeds some threshhold (so ntpdate is usually used to preset the clock).
The workaround is easy enough: add "Required-Start: wpa_supplicant" dependency to the init stanza in /etc/init.d/network and let chkconfig figure out how to rearrange the priorities. This ensures that wlan0 is actually capable of sending a DHCP request when dhclient starts.
This works fine...until yum update decides to replace the scripts in /etc/init.d and, consequently, things go back to the old, broken startup priorities.
So my question: Can yum be told to not change files in /etc/init.d that have been modified by the administrator? Or to at least not overwrite the LSB-style init stanza in those files?
Alternatively, is there a better way to do this that's not vulnerable to updates? I tried playing with the modprobe.conf "install" option to pre-start wpa_supplicant before wlan0 comes up but that has so far been unsuccessful.
I have an HP laptop with both Ubuntu 8.04 and Windows Vista installed on it.
The other day I noticed I was running out of space in the main linux partition (the / partition, not the /home partition), so I decided to move some space from the Windows partition and move it to the linux one. I used a GParted Live CD to do that.
My partitions are ordered as follows: Windows Vista partition (NTFS) Main linux partition / (ext3) Linux home partition /hom (ext3) HP RECOVERY (NTFS - I don't know what it is, it just comes with HP laptops that have Vista on them)
So I shrank partition 1, and then "moved" partition 2 to enlarge it (GParted said everything was alright).
After doing that, I went to my linux and everything seemed to be fine, I'm also quite sure I had access to my Windows partition as always. But today I tried to start my Windows and it just got stuck on the "loading" stage (that screen that says "Microsoft Corporation" and has a green loading bar). So I shut the computer down manually (by holding the power button for a few seconds). After doing that a couple of time, I went to my linux, which worked just fine, but I was not able to go to the Windows partition. You can see how GParted looks now for my computer:[url]
As you can see, the first partition (/dev/sda1), which is supposed to be the Windows partition, is not mounted and the system doesn't seem to be able to read it properly. Here is my attempt to mount it manually:
Code:
Mount is denied because NTFS is marked to be in use. Choose one action:
Choice 1: If you have Windows then disconnect the external devices by clicking on the 'Safely Remove Hardware' icon in the Windows taskbar then shutdown Windows cleanly.
Choice 2: If you don't have Windows then you can use the 'force' option for your own responsibility. For example type on the command line: mount -t ntfs-3g /dev/sda1 /windows/ -o force
Or add the option to the relevant row in the /etc/fstab file: /dev/sda1 /windows/ ntfs-3g force 0 0
I've install F10 to use it as server and router and found a strange problem on my XP machine which is behind the F10. I've tried to update my Lineage2 client from official server but the update crash, tried to open the web page it didn't open. Also tried to open microsoft web it didn't open. When i try to open the same pages on PC with F10 they open with no problem.
i have installed nvidia driver, but after yum update not work anymore
fedora 12, nvidia 6200 output:
Code: MPlayer SVN-r29800-4.4.2 (C) 2000-2009 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control.
I finally got the basic 2D working again on my laptop using the updates-testing stuff. But using 3D (glxgears for example) still make my machine to crash. Also, I get weird kernel panics when trying to configure the nvidia:
I have recently installed Fedora 9 about a dozen times and everytime I apply the recommended system updates, the system crashes upon reboot, leaving me at a dead "GRUB" message (not a prompt). I would love to be able to update my version; suggestions?
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.
will firefox 3.6 be made available as an update? If not is there anything special I need to know before installing it myself i.e. will flash still work?
I have had a good look round the forums but cannot come up with anything quite like this and the problem prevents me from using my NAS box and stuff is starting to stack up on my main PC now...
I have a Dell desktop running Ubuntu 9.04, a Shuttle running Mythbuntu 9.10 and a Netgear ReadyNAS Duo, all of which worked fine until this problem started. I have done nothing to any config files nor have I modified any settings from the outset, as far as I can remember I have just used everything as it came. This problem probably started a month or so back when update manager suggested a Samba update on both PC's which I accepted. I don't fire up my NAS box more than once or twice a month to back all my photos, music, video etc. so it was a while before I did (following the update) I could see the NAS and the Shuttle from the Dell but couldn't browse them I just got the error message 'Unable to mount location. Failed to retrieve share list from server' which I gather is all too common. I have searched around a bit on these forums and have tried a few things in the command line to gather information and I found something that worried me rather a lot. From Dell:
Code: geoff@geoff-dell:~$ findsmb *=DMB +=LMB IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
[Code]...
I haven't done any updates on the NAS box firmware so it can't be that and now I don't even see the shares in filemanager. What on earth is going on??? I know there are many other threads similar to this but but I am hoping that the slight difference might make this more obvious to solve. I forgot to mention that now I don't even see the shares in filedmanager - another thing that happened all by itself!
I have a ton of .avi files. Ever since my last ubuntu online update, they can't play at full screen even though they played fine last week. I tried reinstalling mplayer. No difference. Same problem with xine.
They freeze for about 1/2 second at at time and chop their way along. Not even viewable. But, they look fine in mini-mode.
I have 4 gb ddr3, a quad core, 2.83 gzh intel and an ati 4850 / 512 mb video card. CPU on gkrellm shows < 10%. I think I still have the proprietary ati drivers because I can still move my applications around the screen instantaneously. I have tried xv, gl and gl2 under mplayer -> prefs -> video. All are the same.
Everything works perfectly if I reboot to xp. Where does one begin to debug this?
If I run Fedora as the latest kernel which was updated. My nVidia driver will not load. I log into Gnome or KDE or XFCE all come back with a white screen. Now I have a feeling I need to recompile the nVidia driver for the newly updated kernel. Am I right? If yes how does one do so. If I'm wrong any other ideas.
Just as a note if I boot up into an earlier kernel. My card loads and compiz works and everything is fine.
I tempted those computer gods the other day by saying Fedora 11 was perfect and I was starting to feel at home with it like I used to in Ubuntu. Now I have incurred there wrath.
From time to time an update of F13 will leave me with no Xserver. I CTRL/ALT/F2 log in and Yum Update every day until the needed stuff comes along. This puts me back running. Is there any way to keep a normal 2D display when the updates get out of sync?
Fedora (2.6.34.6-47.fc13.x86_64) I installed that update, during the installation process it said that it had to remove three packages, one of them was kmod nvidia for the old kernel (Fedora (2.6.33.8-149.fc13.x86_64))After the update finished installing the new kernel, I restarted the system and Nvidia did not load. (I assume because Update manager removed the old nvidia? But I also assumed that a new version would be installed automatically?)I received the following Boot messages:
Code:
Entering non-interactive startup Starting monitoring for VG vg_user1: 3 logical volume(s) in volume group "vg_user1" monitored
[code]....
I'm confused, if Update Manager removed kmod nvidia, then why does yum say it is installed? And why doesn't the new kernel update work with that version? Or should I install a driver version for that particular kernel? I've read while searching that I need to install a kmod-nvidia for that particual kernel version and that I should login to my previous kernel until that happens, is that the problem I'm having?
Why don't rpmfusion and fedoraproject release the kmod-nvidia and kernel updates at the same time to avoid problems such as this? Does anyone know how long does it usually take for rpmfusion to release the new kmod-nvidia driver for the latest kernel?
I have Fedora 10 installed. I've just made an update of my system. Things that were updated were a new kernel version with devel and also something with NVIDIA (which is my video card).
After restart of my system, compiz fusion no longer works.
I have a NVIDIA-Linux-x86-177.82-pkg1.run -file to manually install the NVIDIA-driver so the advanced features of Compiz can be utilized.
After install, the bootup screen tells me that loading the NVIDIA driver has failed. I also receive a WARNING-message.
I updated fedora 10 a few days ago, by blindly installing every update available, and when i restarted, my nvidia drivers weren't loading, and I'm having an issue I had before, where the signal being sent to the monitor is out of frequency range. Basically when fedora tries to load its GUI, my monitor just goes blank. Before I could only fix it by plugging in a different (less tempermental) monitor, and messing around with the display driver.
I was wondering if there is a way to mess with the drivers from the command line. I really don't like switching out monitors, and i want to learn the skillz and such.
I just did an update of my Fedora 11 machine, and it required a restart. After restart it will not try to boot up or even show a splash screen. The only thing I see is a black screen with a flashing white cursor.Any ideas on what I can check so I can boot up into Linux again.
I updated my fedora 12 GNOME installation. Now Compiz fusion is not working. It says Accelerated 3D support not found. Though Nvidia drivers are already installed. Now I can't even ALT+TAB between open applications.
I tried "metacity -- replace" but then windows wore a weird look with only a minimize button. No sign of maximise & close buttons.
When I install the most recent Linux Kernel: kernel-2.6.34.6-54.fc13 (i686) The installation process removes: Linux Kernel: kernel-2.6.33.6-147.2.4.fc13 (i686) Plus NVIDIA: kmod-nvidia-2.6.33.6-147.2.4.fc13.i686-1:195.36.31-1.fc13.2 (i686)
This results in Nvidia.ko not being found during the subsequent restart - the remove activity deletes it from the system. Prior to this activity Nvidia.ko is found in: /lib/modules/2.6.33.6-147.2.4.fc13.i696/extra/nvidia. Without Nvidia.ko the display is set to 800x600 resolution. This is the first time I have encountered this problem with a Fedora Linux Kernel update. Will this problem be fixed in a subsequent update, if so when? If not fixed, where do we find the proper Nvidia.ko module? Also, how do you recommend we install it?
I updated FC14 which included the kernel and also the nvidia drivers kmod. Then after a reboot the video driver wouldn't load. From another terminal I tried different things to fix it and didn't managed. I eventually erased all nvidia drivers so that I can get the default one. Now every time it boots I get a really low light. I can login, but can't see. It seems that the whole screens has about 5% light and I can't see to do anything. I managed now to boot into FC live CD for FC15 and I have light. For FC14 live CD it's the same no light problem.
I tried all older kernels to boot but I have the same problem. I am using PAE kernel and that's why I installed the kmod drivers. But now, since they are not anymore and I can't see anything, even though I am logged in I don't know what to do next. Is there something I can do from FC15 live cd? How can I go using the terminal to my harddisk and how to add the driver or any low graphic driver so that I can have light? After I did yum erase *nvidia* the light went almost off.
I did a large update to F15 from an older version of F15. I am using x86_64. I could not reboot (will post separately on that issue). Rebooted the previous kernel in the KDE safe mode, and things look ok, except for NVIDIA CUDA code, which had been working perfectly:
[dtelford@localhost release]$ ./Mandel* [Mandelbrot] starting... [ CUDA Mandelbrot/Julia Set ] Initializing GLUT... X Error of failed request: BadWindow (invalid Window parameter)
When I install the most recent Linux Kernel: kernel-2.6.34.6-54.fc13 (i686) The installation process removes:
Linux Kernel: kernel-2.6.33.6-147.2.4.fc13 (i686) Plus NVIDIA: kmod-nvidia-2.6.33.6-147.2.4.fc13.i686-1:195.36.31-1.fc13.2 (i686)
This results in Nvidia.ko not being found during the subsequent restart - the remove activity deletes it from the system. Prior to this activity Nvidia.ko is found in: /lib/modules/2.6.33.6-147.2.4.fc13.i696/extra/nvidia.Without Nvidia.ko the display is set to 800x600 resolution. This is the first time I have encountered this problem with a Fedora Linux Kernel update.
i ran yum update which updated kernel to 2.6.31.9.174.fc12.i686.PAE. Now after logging in i get a blank white screen. With previous kernel updates i have had no such problem. Anyway, the boot messages are following:
Quote:
checking for module nvidia.ko [FAILED] nvidia.ko for kernel 2.6.31.9-174.fc12.i686.PAE was not found [WARNING] The nvidia driver will not be enabled until one is found [WARNING] Driver already disabled
im having problems with update to new kernels..here is the error info: error is: Multiple packages exist that are not compatible with each other. This is usually due to mixing packages from different software origins. ERROR with rpm_check_debug vs depsolve:
kernel-uname-r = 2.6.30.5-43.fc11.x86_64 is needed by kmod-nvidia-2.6.30.5-43.fc11.x86_64-185.18.36-1.fc11.1.x86_64 kernel-uname-r = 2.6.30.8-64.fc11.x86_64 is needed by kmod-nvidia-2.6.30.8-64.fc11.x86_64-185.18.36-1.fc11.2.x86_64 kernel-uname-r = 2.6.30.9-96.fc11.x86_64 is needed by kmod-nvidia-2.6.30.9-96.fc11.x86_64-190.42- [Code]....
a little while ago the file from nv stopped being able to run.. I cant update the driver and now always get this error
4: warning: comparison between signed and unsigned integer expressions /tmp/selfgz2718/NVIDIA-Linux-x86_64-260.19.12/kernel/nv.c: In function �nv _kern_read_registry�:
Lately I tried to update my nvidia drivers from RPFMFusion repos. There was a new version 275 available, so I installed it. After a reboot I would repeatedly see the Nviia Logo followed by black followed by a glimpse at the CLI with some error message. This process continues over and over again and it is so fast that the only thing I could make out from the error message is the following:
at-spi-bus-laun[some-number] segfault at 980 ... in libx11.so.6.3.0 ...
I tried completely removing the driver then updating my system (there were no updates) then booting with nouveau to see that that actually works. Then I tried reinstalling the nvidia driver following leigh's guide [URL]. Same error.
This is where I'm stuck at the moment. Booting to runlevel 3 I had a look into the messages and Xorg.0.log, but I didn't see anything. Maybe I can get the log files uploaded. I will boot from live media and provide them later on.
Hardware specs:
Samsung P480 Intel corei3 330 nvidia GT330M 1024mb 8gb Ram 120gb SSD OZC Vertex 2 with /tmp mounted as tmpfs
Software specs:
Using F15 x64 kernel 2.6.38.8-32 (from the top of my head, please don't shoot me) added repos: RPMFusion adobe (flash) playonlinux
There is one addition I can make. Before, when I was using the 270 driver, I tried playing some games via wine and that also segfaulted on me (most of the time - 1 worked), so I think there is a general issue with the nvidia drivers on my system. But back then It was only wine, not X.
I have just updated my kernel to version 2.6.38.8-35 in Fedora 15, it now refuses to boot that kernel. I just get a lot of text on the screen and nothing happens. I can ctrl-alt-fn to get to a prompt, but I do not know how to fix the nvidia problem.
When I edit Xorg.conf and replace 'nvidia' with 'nv' the new kernel boots but only to fallback mode, trying to then re-install the nvidia drivers shows them to be already installed and I can get no further.
I have been running F11 for some time now. I install updates regularly and to this time have had no issues. Now it comes up with error.
Code: [root@red 2305 ~] $ yum update Loaded plugins: protectbase, refresh-packagekit 0 packages excluded due to repository protections Setting up Update Process Resolving Dependencies --> Running transaction check ..... --> xorg-x11-drv-nvidia conflicts with xorg-x11-drv-catalyst Error: xorg-x11-drv-nvidia conflicts with xorg-x11-drv-catalyst Error: xorg-x11-drv-catalyst conflicts with xorg-x11-drv-nvidia You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest [root@red 2306 ~]
I do not believe that I even have the 'xorg-x11-drv-catalyst' mentioned here installed: Code: [root@red 2315 ~] $ yum list all | grep installed | grep catalyst [root@red 2316 ~] This returns nothing so why the error?
I'm running Fedora 13 x64 and updated the kernel to the latest version (2.6.34.7-56 to 2.6.34.7-61). I use the proprietary nvidia drivers (currently 260.19.12) so I had to compile the kernel module against the new kernel sources and reinstall the driver. The process was apparently successful, but when I try to start X nothing happens, it's as if the computer had been suspended, my monitor acts like it isn't receiving any input. I have full runlevel 3 access, and the system seems pretty much fine up to that point. Nvidia's own sanity tests which are built into the installer reported no problems with my driver.