Author Topic: <Solved> i915 module fatal error - no such device. nvidia driver problems..  (Read 3872 times)

Offline t20racerman

  • Sr. Member
  • ****
  • Posts: 332
    • My T20 Suzuki website.
Re: i915 module fatal error - no such device
« Reply #30 on: May 06, 2011, 03:20:38 PM »
Phew - glad I have a digital camera to hand....

http://www.t20suzuki.com//cz/P5062741.JPG

Screen pic link above


OK

Now:

# less /etc/X11/xorg.conf

You should be able to scroll the screen with the PageUp/PageDown keys to take as many shots as needed to post the whole thing. Mine would only take two shots, with a lot of overlap



OK, not the best quality pics, but I'm trying to do my best. 4 pictures:
http://www.t20suzuki.com/cz/P100.JPG
http://www.t20suzuki.com/cz/P102.JPG
http://www.t20suzuki.com/cz/P104.JPG
http://www.t20suzuki.com/cz/P106.JPG

Right, I'll try the the command from 'as' next.....
We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true. - Robert Wilensky

Offline t20racerman

  • Sr. Member
  • ****
  • Posts: 332
    • My T20 Suzuki website.
Re: i915 module fatal error - no such device
« Reply #31 on: May 06, 2011, 03:31:40 PM »
"could not open device file /dev/nvidia0"
The above error suggest something is broken before, at kernel/modules level.  t20racerman, please try the following command:

lsmod | grep nvidia

(lsmod = LSMOD lowercase)

Ok, did that. Below is the output, copied as best as I could.

Quote
# lsmod | grep nvidia
nvidia        9238826         0
i2c_core      16500   12   nvidia, dvb_pll, cx22702,cx808_dvb, cx88_vp3054_i2c,cx8800,cx88xx,i2c_algo_bit,tveeprom,v412_common,i2c_i801, videodev
#

I really appreciate all the help guys - thanks.  :)



We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true. - Robert Wilensky

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11541
  • ----IOFLU----
Re: i915 module fatal error - no such device
« Reply #32 on: May 06, 2011, 04:04:27 PM »
t20racerman:

The xorg.conf looks good, but the;

nvidia               9238826     0

shows that the driver, while loaded, is not attached to the device, as the error message noted. Mine looks like this;

nvidia               9601922    74 [permanent]

Boot to your liveCD, log in as root, open a terminal and enter;

[root@localhost ~]# umount -a                              <Enter>

[root@localhost ~]# fsck -f /dev/<whatever>                  <Enter>

Replace <whatever> with the actual partition designation of your / partition. When done, reboot to the installed OS.

Post your results.
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline t20racerman

  • Sr. Member
  • ****
  • Posts: 332
    • My T20 Suzuki website.
Re: i915 module fatal error - no such device
« Reply #33 on: May 06, 2011, 04:37:27 PM »
OK, getting late here in the UK again....

Back tomorrow with results.... So much appreciate the help  ;D
Thanks
We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true. - Robert Wilensky

Offline t20racerman

  • Sr. Member
  • ****
  • Posts: 332
    • My T20 Suzuki website.
Re: i915 module fatal error - no such device
« Reply #34 on: May 07, 2011, 08:29:19 AM »
t20racerman:

The xorg.conf looks good, but the;

nvidia               9238826     0

shows that the driver, while loaded, is not attached to the device, as the error message noted. Mine looks like this;

nvidia               9601922    74 [permanent]

Boot to your liveCD, log in as root, open a terminal and enter;

[root@localhost ~]# umount -a                             <Enter>

[root@localhost ~]# fsck -f /dev/<whatever>                  <Enter>

Replace <whatever> with the actual partition designation of your / partition. When done, reboot to the installed OS.

Post your results.

Ok, here we are:
[root@localhost guest]# fsck -f /dev/sda7
fsck from util-linux-ng 2.18
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda7: 27927/5668864 files (2.3% non-contiguous), 6702391/22657666 blocks
[root@localhost guest]#

I'm posting this here now from my livecd boot-up. If there is no addition to this posting in the next 10 mins or so, then I'm still stuck at text boot and need some more help.!


EDIT: Ok, back on my laptop - the above didn't work. However i noticed that I'd done sda7 (my home partition) rather than sda5 (root partition). I redid this or sda5 and the output ws pretty much the same, as was the result!
« Last Edit: May 07, 2011, 09:06:48 AM by t20racerman »
We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true. - Robert Wilensky

Offline t20racerman

  • Sr. Member
  • ****
  • Posts: 332
    • My T20 Suzuki website.
Re: i915 module fatal error - no such device
« Reply #35 on: May 07, 2011, 10:38:58 AM »
Some success!!!!!

I retried old-polaks suggestion of installing a new kernel, but this time tried a much older one - 2.6.32.24-pclos1.bfs

This installed, rebuilt itself with the nvidia 260.19.44 module and then booted perfectly into graphics mode! Yay!!!

Ok, now what - what can I update, what can I do to keep this running nicely. Shall I uninstall and then reinstall the later kernel - is that worth a try?

Thanks again for all the help - we are getting there!  :) :)
We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true. - Robert Wilensky

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11541
  • ----IOFLU----
Re: i915 module fatal error - no such device
« Reply #36 on: May 07, 2011, 10:53:31 AM »
Some success!!!!!

I retried old-polaks suggestion of installing a new kernel, but this time tried a much older one - 2.6.32.24-pclos1.bfs

This installed, rebuilt itself with the nvidia 260.19.44 module and then booted perfectly into graphics mode! Yay!!!

Ok, now what - what can I update, what can I do to keep this running nicely. Shall I uninstall and then reinstall the later kernel - is that worth a try?

Thanks again for all the help - we are getting there!  :) :)

That would be my next move.
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline t20racerman

  • Sr. Member
  • ****
  • Posts: 332
    • My T20 Suzuki website.
Re: i915 module fatal error - no such device
« Reply #37 on: May 07, 2011, 12:38:36 PM »
Ok, we seem to be getting to the bottom of this problem and I'm beginning to suspect a kernel bug!

With kernel 2.6.32.24-pclos1.bfs and nvidia 260.19.44 module the computer boots up perfectly every time. As I suggested above, I decided to completely uninstall (with synaptic) all the other kernels. I then rebooted (just in case it was necessary - old Windows habits die hard!) and still all worked well.
I then used synaptic to install these later kernels
Quote
kernel-2.6.33.7-pclos6.bfs
kernel-2.6.37.4-pclos1.bfs
kernel-2.6.38.4-pclos1.bfs

I tried the first two out, both built the kernel with the nvidia 260.19.44 module and then both refused to run X and booted to text mode. I haven't bothered with the third kernel as I know what is going to happen!

OK, so where does this point towards the problem being? Clearly it is NOT the later nvidia 270 module causing the problem (unless it damaged something in my card!) as I'm running the 260.19.44 module with all three kernels.
It isn't my graphics card as it worked great before, works with the 2.6.32.24-pclos1.bfs kernel, and works with Windows too.
So, is this a kernel problem conflicting with something???

Any ideas. Also, shall I close this thread as solved (sort of) and start a new one as this is a totally different problem to the earlier one which has now completely disappeared.. (or is it related?).
Is it worth trying the 270 driver with the kernel that works now?

Your thoughts/ideas welcomed
We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true. - Robert Wilensky

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: i915 module fatal error - no such device
« Reply #38 on: May 07, 2011, 01:38:10 PM »
t20racerman,

I would suggest the following test:
download the Sproggy's Phinx-RC1 from here: http://www.pclinuxos.com/forum/index.php/topic,90842.msg761775.html#msg761775,
it is provided with 2.6.38.4 and nvidia-270.. drivers, already builted-in.

Burn the ISO, and boot the liveCD. Let us know the result.  ;)

AS

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11541
  • ----IOFLU----
Re: i915 module fatal error - no such device
« Reply #39 on: May 07, 2011, 02:19:31 PM »
I decided to completely uninstall (with synaptic) all the other kernels. I then rebooted (just in case it was necessary - old Windows habits die hard!) and still all worked well.
I then used synaptic to install these later kernels
Quote
kernel-2.6.33.7-pclos6.bfs
kernel-2.6.37.4-pclos1.bfs
kernel-2.6.38.4-pclos1.bfs

Did you install them all at once, or one at a time, rebooting after each installation?

as:

I like your idea of testing with Phinx-RC1. Good thinking. ;)
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline t20racerman

  • Sr. Member
  • ****
  • Posts: 332
    • My T20 Suzuki website.
Re: i915 module fatal error - no such device
« Reply #40 on: May 07, 2011, 02:50:26 PM »
Hi old-polak - I installed them all at once. Is that a problem?

Re the iso - I'm having problems downloading it. I'll persevere, but I downloaded one version of 348Mb which is less than it said it should be, I tried again twice and was offered files of sizes 290Mb and 248Mb....

What size should it be? Anyway, I'll keep trying. :)
We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true. - Robert Wilensky

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11541
  • ----IOFLU----
Re: i915 module fatal error - no such device
« Reply #41 on: May 07, 2011, 03:36:53 PM »
Hi old-polak - I installed them all at once. Is that a problem?


Kernels should be installed one at a time, then booted to, so that all processes involved can complete in an orderly, focused, manner. Only after the full cycle has completed is it safe to install another kernel.
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline t20racerman

  • Sr. Member
  • ****
  • Posts: 332
    • My T20 Suzuki website.
Re: i915 module fatal error - no such device
« Reply #42 on: May 08, 2011, 05:43:58 AM »
Hi again

I downloaded, burnt and ran Phinx-RC1 as suggested. It works fine. Oddly, on bootup it did drop down to a text only login TWICE, stayed there for 10 seconds or so, then went back to booting normally - is this what you'd expect?

Anyway, clearly that works on my system

Old-polack - I unistalled the kernels, rebooted and have started to install one at a time, with reboot in between, testing the new kernel. I get the same result - a failure and back to text mode. If I logon and type startx I always get an error of 'device not found, no screen present' or something along those lines. Clearly my graphics card is being recognised on boot with new kernels - as it always installs the nvidia 260 driver when being first run - but after that, when X starts, the graphics card can't be seen.  ??? Everything was fine before the last big update, and is still fine with the earlier kernel.

Most odd....
We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true. - Robert Wilensky

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: i915 module fatal error - no such device
« Reply #43 on: May 08, 2011, 06:30:39 AM »
Hi again

I downloaded, burnt and ran Phinx-RC1 as suggested. It works fine. Oddly, on bootup it did drop down to a text only login TWICE, stayed there for 10 seconds or so, then went back to booting normally - is this what you'd expect?
Yes, it's normal that a liveCD/liveUSB is a little slower than a usual HDD installed system.
Interesting that your system works, that means there are no compatibility issue between your HW, the nvidia drivers, the new kernel.

Quote
Anyway, clearly that works on my system

Old-polack - I unistalled the kernels, rebooted and have started to install one at a time, with reboot in between, testing the new kernel. I get the same result - a failure and back to text mode. If I logon and type startx I always get an error of 'device not found, no screen present' or something along those lines. Clearly my graphics card is being recognised on boot with new kernels - as it always installs the nvidia 260 driver when being first run - but after that, when X starts, the graphics card can't be seen.  ??? Everything was fine before the last big update, and is still fine with the earlier kernel.

Most odd....

The nvidia dkms modules is rebuit upon reboot of a new kernel installation when the nvidia-dkms package is installed, this has nothing to do with hardware recognition, anyway, from your previous report about lsmod, the nvidia module exist and it's loaded, therefore your card look like recognized.

When X server is started, a log file is created: /var/log/Xorg.0.log, may be you want to take a look at this file for actually unknown errors (lines marked with EE in the log). Additionally you may want to take a look at the output of dmesg command for others info/errors.

Boot using the "broken" kernel, copy the file /var/log/Xorg.0.log in your home, execute dmesg > ~/dmesg.txt, then reboot to your working kernel and eventually post here both output files.

AS
« Last Edit: May 08, 2011, 06:39:08 AM by as »

Offline t20racerman

  • Sr. Member
  • ****
  • Posts: 332
    • My T20 Suzuki website.
Re: i915 module fatal error - no such device
« Reply #44 on: May 08, 2011, 07:17:31 AM »
Once again, can I thank you guys for your ideas, help and patience  :) :)

Ok, here we go.
/var/log/Xorg.0.log here: http://www.t20suzuki.com/cz/mylog.txt
dmesg.txt here: http://www.t20suzuki.com/cz/dmesg.txt

Lots to read there but the interesting bit is here I think:
Quote
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "AddARGBGLXVisuals"
(**) NVIDIA(0): Option "DynamicTwinView" "false"
(**) May 08 15:00:49 NVIDIA(0): Enabling RENDER acceleration
(II) May 08 15:00:49 NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) May 08 15:00:49 NVIDIA(0):     enabled.
(EE) May 08 15:00:49 NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please
(EE) May 08 15:00:49 NVIDIA(0):     check your system's kernel log for additional error
(EE) May 08 15:00:49 NVIDIA(0):     messages and refer to Chapter 8: Common Problems in the
(EE) May 08 15:00:49 NVIDIA(0):     README for additional information.
(EE) May 08 15:00:49 NVIDIA(0): Failed to initialize the NVIDIA graphics device!
(II) UnloadModule: "nvidia"
(II) UnloadModule: "wfb"
(II) UnloadModule: "fb"
(EE) Screen(s) found, but none have a usable configuration.


That is where it is failing, although WHY it does I have no idea.

This bit of the dmesg is interesting too:
Quote
nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
nvidia 0000:01:00.0: setting latency timer to 64
vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
NVRM: loading NVIDIA UNIX x86 Kernel Module  260.19.44  Sun Feb 27 21:30:31 PST 2011


So, nvidia 'taints' my kernel.  :o
« Last Edit: May 08, 2011, 07:46:58 AM by t20racerman »
We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true. - Robert Wilensky