Fedora Hardware :: No Kernel Modesetting Driver Detected
Nov 13, 2010Attached is my Xorg.0.log, my modprobe output, and my lspci -v output.Kernel modesetting appears to be enabled. Plymouth splash screen works graphically.
View 1 RepliesAttached is my Xorg.0.log, my modprobe output, and my lspci -v output.Kernel modesetting appears to be enabled. Plymouth splash screen works graphically.
View 1 RepliesI use OpenSuse 11.1. My graphic card is an intel Q43/Q45 chip. I was instructed to update my xorg and mesa packages in order to make on application work (it was crashing my x server). After I did so, x wouldn't start:
intel(0): No kernel modesetting driver detected
Screen(s) found, but none having a usable configuration
Now I am stuck with vesa if I want to have x running at all. I tried reverting to the versions of mesa and xorg I had before, when everything worked, but to no avail.
What can I do? (I am by no means an expert and that I don't know linux very well, and even less openSuse... just has to use it at work....)
I can't seem to get a screen on my Asus Netbook 1005pe. I did install the xf86-video-intel-2.10.0-i486-1.txz & kubdrn-2.4.17-i486-1.txz.I'm also having a Kernel Modesetting issue. Below is my Xorg.conf file & my Xorg.0.log file. Sorry if I am not explaining myself correctly.
View 14 Replies View RelatedI dl the windows installer one and ran it. As it started it went to the Ubuntu logo and then my screen became half full of different colored horizontal lines, so I rebooted and went into the adv boot and ran the install under safe graphics mode. Now when I boot I get options to boot into 2.6.32-25 and also a recovery and also 2.6.32.24 and a recovery. I left the 2.6.32-25 highlighted and it booted but gave me a msg that said:
(EE) VESA: Kernal modesetting driver in use, refusing to load.
(EE) No devices detected.
Then it goes to a screen that allows me to boot in a low graphics mode. It loads and I dl some security updates with the Update Manager. What do I need to do in order to boot w/o any faults and also what is the difference from 2.6.32-25 and 2.6.32-24? Which should I be using? Do I need to modify my graphis somehow?
i just updated my Fedora 14 from Kernel version 2.6.35.11-83 to 2.6.35.11-88 Now the driver for the broadcom wireless ethernet adapter is not detected anymore I installed the driver using
[code]...
The package is still installed but when i but when i use modprobe again the output is "module wl not found" Anybody some ideas? By the way, here is the hardware specification
[code]...
I have Radeon HD 3870, which is limited to 2D purposes I understand...
Will this mean that I cannot use DRI? Will it have a performance impact in 2D applications?
Does DRI make watching movies on PC 'better'? Especially 720p ones.
Enabling kernel modesetting on my computer breaks graphics, but Xorg.log and syslog don't tell me much, because they don't log any error.
The symptoms are the following: boot goes on normally, then the KDM login screen is corrupted. On the login screen there is a big square instead of the cursor, and that square does move as I move the mouse. If I press Ctrl+Alt+F1 I'll get a black screen instead of the terminal, and from there I cannot go back to virtual terminal 7 for login. The only thing I can do is to issue sys-requests for read-only remount and reboot.
Where could I start looking for the problem? What does it seem to be related to, Xorg, kernel, radeon driver?
my problem is on installing nvidia driver on fc12 32bit but, first of all, as i understood the pae kernel requires more than 4gb of ram,i have a 2.2 ghz cpu with 2 gb ram,but when i run command:uname -r it answers: 2.6.31.5-127.PAE [i have fc12 32 bit] when we try to download linux we have a 32bit edition or 64bit edition,do we have an edition which is only for pae? or when we install for example the 32bit edition on a computer with more than 4gb of ram then the kernel automatically will change to be a pae kernel??
View 10 Replies View RelatedI attempted to run amarok from the menu and found it would never start there was no activity, I then tried to start it from the command line and I recieved this error..
Version mismatch detected between the NVIDIA libGL.so
and libGLcore.so shared libraries (libGL.so version:
195.36.31; libGLcore.so version: 195.36.24).
Please try reinstalling the NVIDIA driver.
This is a fresh install of Fedora 13, the kmod-nvidia drivers were just fixed I assume cause I tried to install them for a few days and they would fail. Well I guess they finally fixed the Nvidia drivers for 2.6.33.5-124.fc13.x86_64 but it has broken amarok..
i just installed fedora 14 x86_64 on an external driver now everything works fine except that i don't have any sound comming out of my speakers so i think that my sound cart is not detected or the driver isn't installled (can't find a driver for linux to so i can't confirm)
View 6 Replies View Relatedi want to compile Moxa (5100) driver in Fedora 12 , kernel <= 2.6.30 but now when i run command i see this error :
Code:
ln: creating symbolic link `libssl.so': File exists
make -C /lib/modules/2.6.31.5-127.fc12.i686.PAE/build SUBDIRS=/home/AAA/moxa modules
make[1]: Entering directory `/usr/src/kernels/2.6.31.5-127.fc12.i686.PAE'
CC [M] /home/AAA/moxa/npreal2.o
/home/AAA/moxa/npreal2.c: In function �npreal_open�:
/home/AAA/moxa/npreal2.c:1000: error: implicit declaration of function �task_session_nr
make[2]: *** [/home/AAA/moxa/npreal2.o] Error 1
[Code]...
I have Fedora 12 right now, and I've come to the conclusion that the ATI catalyst drivers version 9.11 aren't going to work at all on that system, so I was going to downgrade to fedora 10 and install 9.8 or so on it. But what I was wondering is if I install Fedora 10 and then upgrade the kernel will that make the ATI drivers not work? Do I need to turn automatic updates off?
View 4 Replies View RelatedHaving just updated various files including the kernel using Package Manager I no longer seem to have the correct version of the Nvidia graphics driver. On previous updates this has been done automatically by the "kmod Nvidia" Metapackage. My last kernel was 2.6.32.19-163 fc12.i686.PAE and the Nvidia driver for that did get downloaded correctly. Looking on Yumex I cannot see a driver for this latest kernel listed.
View 10 Replies View Relatedi got an error this kernel requires an x86-64 CPU,but only detected an i686 CPU� while installing fedora12 in virtual machine..........
View 2 Replies View Relatedi 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
I have a GF 6600 video card.
My GMA500 (poulsbo) driver is not working any more because of the latest update I made using Software Update.
The update was a new kernel:
[omass@omass ~]$ uname -a
Linux omass 2.6.30.10-105.fc11.i586 #1 SMP Thu Dec 24 16:26:26 UTC 2009 i686 i686 i386 GNU/Linux
Now, after this update, when I reboot I get the following error code...
I tried to install the new Vbox 3.2.6 through rpm as a guide told me but I first had errors with the older vbox dependencies, so I uninstalled vbox 3.1.8.2 and now I am with a vbox period. Is there something I can do to fix this I tried this tutorial didn't work for me [URL] and another on the fedora forum (lost the history). error I get is Recompiling VirtualBox kernel module [FAILED] and Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing.
View 5 Replies View RelatedI just responded to a (packagekit?) prompt to update packages, which included new kernel 2.6.35.12-88.fc14.x86_64. I use nVidia on my notebook and usually the new driver is installed automatically. This time, the computer would not boot to the stage that the nVidia logo appears, indicating the driver is not present. I edited grub.conf to take me back a version and I am now running under the previous kernel 2.6.35.11-83.fc14.x86_64. I tried a yum search for kmod-nvidia-2.6.35.12-88.fc14.x86_64 and nothing was found. I have enabled these repos:
[Code]...
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.
View 14 Replies View RelatedI used to have FC11 installed with the nvidia supplied binary driver. Worked fine, very stable. Trying FC12 and FC13 live CDs caused a hang, so I stuck with FC11. FC14 live CD did boot so I backed up my own files and did a clean FC14 install. Upgraded to get kernel 2.6.35.6-48, installed the nvidia driver from RPMFusion (260.19.21) and had a working system! Now, after a cold boot, the kernel always hangs during boot. Tried a number of kernel boot option (apci=off, noapic and a few others too). The hang is not always at the same place. The earliest it has hung is after:Disabling lock debugging due to kernel taint
Sometimes its a few lines later at:NVRM: loading NVIDIA UNIX x86_64 Kernel Module 260.19.12 ...(which would seem to imply that the hang can even occur a step or two before the actual driver is loaded!)
Sometimes it keeps going for a few more seconds and randomly hangs during some other driver load.
Without a specific nvidia driver the system always boots ok, so I'm pretty sure its the nvidia driver but I just can't seem to get a handle on this in a reproducible way. Sometimes, when I have make some other change, it will boot and work ok, but a reboot locks it up again (for example, in case it was SELinux, I disabled it and on the next reboot it booted and worked ok. Then, next boot, it wasn't working again). When I make changes, I reboot using the previous kernel, make the changes and reboot, with an occasional success. Once I start rebooting using the latest kernel, it always hangs.
I'd love to get a solution to this, but even some advice on debugging this would be appreciated!
I'm using 8600GT, 256Mb, PCIe card in a MA69VM motherboard with 3Gb of RAM.
Looking for an option to get Fedora working again, I followed Leighs guide to install the kernel nvidia driver. On Reboot however I am stuck a the Fedora splash.Is there a way when booting to disable splash, or enter in safe mode?I have an nvidia geforce 9 card and I used the non-PAE install.
View 6 Replies View RelatedThe Fedora 14 (and 13) pwc Philips Webcam Driver.is only supporting 160x120 resolution (and nothing higher such as 640x480). Also not supporting some other things correctly, I suspect.I say so having tested multiple web camera software and either they don't work (because they have no setting for low res) or they do work if settable to low res., but not for any higher res.I also have a working setpwc tool which shows the driver does not support framerate resetting.I have a Toucam and Toucam Pro - same for both.Also these units worked fine under Fedora 11, and under earlier versions even Red Hat 4.But I usually got the latest pwc from Saillaird.org and compiled it to get full support but there are no more current sources there anymore, and the older ones don't compile.But as I am saying under F11 it was fully correct, now under F13 and 14 it is broken.
View 14 Replies View RelatedYesterday I updated my F15 x86_64 system from kernel 2.6.38.6-27 to 2.6.38.8-35. After the reboot, my triple-head system complained of not having enough CRTCs and only 2 screens worked. Other components were also updated, including some X11 components, however selecting a fallback kernel at the grub prompt indicates this follows the kernel (fall back to old kernel has all 3 monitors working). xrandr --verbose on the 2.6.38.6-27 kernel shows each of the 3 monitors assigned to separate CRTC entries, with CRTCs 0 thru 5 available.
Same command on the new 2.6.38.8-35 system only shows CRTCs 0 & 1 available. My system using an XFX Radeon HD5450 card, with 3 interfaces: HDMI, DVI, VGA. The default Fedora open source "radeon" driver allows all 3 interfaces to be usable. However, with the new kernel, the loss of several CRTCs prevents the 3rd monitor from working.What are the thoughts from the community? I've searched various forums here and haven't seen similar symptoms reported. I'm looking for any direction/experience/thingsToTry from others before trying to open a bug report. (Attempts to use the Catalyst driver several months ago resulted in only 2 of the 3 connected monitors working.
I had no problems up to the newest kernel version. But for 2.6.40-4 akmods fails to build the kmod with the following error:
Code:
Building RPM using the command '/usr/bin/akmodsbuild --target x86_64 --kernels 2.6.40-4.fc15.x86_64 /usr/src/akmods/VirtualBox-OSE-kmod.latest'
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/akmodsbuild.yob64XwN/BUILD/VirtualBox-OSE-kmod-4.0.4/_kmod_build_2.6.40-4.fc15.x86_64/vboxnetflt/vboxnetflt.mod.o
LD [M] /tmp/akmodsbuild.yob64XwN/BUILD/VirtualBox-OSE-kmod-4.0.4/_kmod_build_2.6.40-
[Code]...
I am trying to install a vendor provided driver in Fedora 9 kernel 2.6.27.25-78.2.56.fc9.x86_64. Apparently the vendor stopped officially supporting Linux a number of years ago, so there were a few things I needed to change in the source code to get it to compile, now I'm trying to install it. Make runs successfully, but when I try to "make install" this happens:
Code:
# make install
Unloading any instances of foo module
Loading new foo into running kernel
insmod: error inserting 'foo.ko': -1 Operation not permitted
make: *** [install] Error 1
I've tried finding a solution via Google but it seems that the majority of people solved this problem using sudo, but I'm using su already and this still happens. I've also gone into make menuconfig and modules are enabled. I have access to the makefile and all the source code, so if something needs to be done there I can do it. If anyone has any ideas, please don't leave out any details; I'm a complete newbie when it comes to Linux
I just built some machines with the Intel 82574L gigabit ethernet chip, loaded Fedora 14, and discovered a problem with the e1000e driver dying after a few minutes. A little time spent perusing the web told me that the same driver had problems in Fedora 12 and Fedora 13 as well. Congrats to Fedora for the hat trick.As of kernel 2.6.35.10-74.fc14.x86_64, e1000e driver 1.0.2-k4 still had bugs.[URL]
View 6 Replies View RelatedI seem unable to get an nvidia driver working properly after upgrading to the latest kernel with Fedora 11.Here is my laptop and its specs: http://h10025.www1.hp.com/ewfrf/wc/d...reg_R1002_USEN[URL]I've tried both the kmod and akmod unsuccessfully. Everytime it gives me a black screen on boot, I can fix the problem by popping in the LiveCD, and changing the xorg.conf file back to the backup.Here are the errors/warnings from my boot.log file:
Code:
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
Checking for module nvidia.ko: [60G[[0;31mFAILED[0;39m]
[code].....
I'm attempting to install the driver for my atheros AR8131 PCI-E Gigabit Ethernet adapter (in my Lenovo laptop) on my newly installed RHEL5 system (it's not currently being recognized).
I tried using: 'make install' but hit an error "Makefile:61: *** Linux kernel source not found."
After this, I tried: 'sudo yum install kernel-devel kernel-headers'
To rectify this, but hit this error "No package kernel-devel available" (and the same for the headers). What should I do?
I write the network driver. Transmission of packets in user space I do through netlink socket`s. In user space there is a handling of packets and their transmission on other device (however, it isn't important).
Problem in that any time, packets through the driver in system, and is reverse, are transferred normally. But then there comes the moment when the kernel crash. If to look in syslog it seems to me that comes deadlock. Also I think that it is related with netlink socket`s.
I can't find the information on that anywhere how correctly to use netlink socket`s in kernel space. Can at you will any a reason into the account of synchronization of sockets and the driver in kernel space?
I can give the driver code if it is necessary.
With the recent upgrade kernel, my ATI driver can no longer work. After upgrading to the new kernel, upon reboot I would get stuck at the "checking battery status" and can't boot into kubuntu.
I'm running Kubuntu 10.10 64 on intel i5 with radeon hd 4870.
So I thought I messed something up since I was fooling around with conky script the day before. I did a clean install of kubuntu 10.10 64 and reset all my settings and my files. At this point, everything works smoothly and I can reboot multiple times without a problem.
I proceeded to install the Radeon catalyst driver following the documentation, which worked perfectly for me on the previous kernel. After rebooting, I can no longer get pass the "checking battery state" black screen. I had to boot into safe book, uninstall all fglrx and also delete xorg.conf to be able to boot back in normally.