Nvidia failed to load module type1 ubuntu 8.10 after upgrading kernel

Asked by mtn_biker_mike

after reboot Nvidia

EE failed to load module type1 (module does not exist)
EE Nvidia(0) failed to ini the Nvidia Graphics Device PCI 1.00
(NOTE I have a AGP CARD)
EE Nvidia see common Problems
EE screen found none of these usable configurations

Running the Nvidia 96 driver loaded with Package manager
my Nvidia card is a Leadtek winfast A250 TI 4400 Nvidia

01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti 4400] (rev a2)

http://pastebin.com/m490a61a3

keeps loading low graphics

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu xserver-xorg-driver-nv Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:

This question was reopened

Revision history for this message
Buz Cory (buzco) said :
#1

Hello Mountain Biker,

Is that motorbike or pedal bicycle? Either way is good :)

Now to your problem:
"Package manager" would be the synaptic one, I presume and you got the driver out of a .deb.
My first suggestion for any video problem is to make sure you have the latest appropriate driver. Current is now #180, so please upgrade, try it again and let me know what happens. I will generally know in an hour or less when this changes.

BTW, I don't know what you mean by "reboot nVidia" above. After a driver upgrade like this, you have to reboot the whole system.

== Buz :)

Revision history for this message
mtn_biker_mike (mtn-biker-mike) said :
#2

loaded the nvidi driver 180 same prob
Reboot computer

Ubuntu is running in low graphics mode
the following ERR was encountered
You may need to update your configuration file to solve this

EE failed to load module type 1

EE No devices detected

when I go to the Nvidia x server settings I get a err

Revision history for this message
mtn_biker_mike (mtn-biker-mike) said :
#3

when I go to the Nvidia x server settings I get a err

You do not appear to be using the NVIDIA X driver. Please edit your X configuration file (just run `nvidia-xconfig` as root), and restart the X server.

Revision history for this message
Buz Cory (buzco) said :
#4

OK,

First make *_sure_* the proper driver is installed. Try looking in /proc/drivers.
Also a possible source of problems is multiple kernel versions in your grub (boot) menu.

BTW, did you follow the instructions above and run nvidia-config? If so, what happened?

== buz :)

Revision history for this message
mtn_biker_mike (mtn-biker-mike) said :
#5

tryed
       -desktop:~$ sudo nvidia-xconfig

Using X configuration file: "/etc/X11/xorg.conf".

VALIDATION ERROR: Data incomplete in file /etc/X11/xorg.conf.
                  Device section "Configured Video Device" must have a
                  Driver line.

sh: pkg-config: not found
Backed up file '/etc/X11/xorg.conf' as '/etc/X11/xorg.conf.backup'
New X configuration file written to '/etc/X11/xorg.conf'

Revision history for this message
mtn_biker_mike (mtn-biker-mike) said :
#6

tryed
       -desktop:~$ sudo nvidia-xconfig

Using X configuration file: "/etc/X11/xorg.conf".

VALIDATION ERROR: Data incomplete in file /etc/X11/xorg.conf.
                  Device section "Configured Video Device" must have a
                  Driver line.

sh: pkg-config: not found
Backed up file '/etc/X11/xorg.conf' as '/etc/X11/xorg.conf.backup'
New X configuration file written to '/etc/X11/xorg.conf'

Revision history for this message
mtn_biker_mike (mtn-biker-mike) said :
#7

here is what I have done after trying the 180 driver
I think that the 96 driver is the latest one that I can use with my hardware
uninstalled other Nvidia drivers and reboot computer.
installed Nvidia GLX 96 driver Nvidia settings
installed pkg-config
 >>>>>sudo apt-get install pkg-config

ran the nvidia config again sudo nvidia-xconfig
looks like it ran ok
need to restart the x server? Ctrl+Alt+Backspace to restart X server.

Revision history for this message
mtn_biker_mike (mtn-biker-mike) said :
#8

still having trouble, getting err on boot up still
driver s ect
Nvidia_settings 177.78-Ubuntu2.1
                         need to run Sudo nvidia-xconfig for this

Nvidia-96-kernel-source 96.43.09 Ubuntu 1.1
Nvidia_96-modaliases
Nvidia-commom

Have Jockey-gtk .05~Beta3-Ubuntu6.1
Jockey-gtx 05~Beta3-Ubuntu6.1
    If removed also removes mythBuntu_desktop

Smartdimmer 0.1-2Build1
   Change LCD brightness on Geforce 6200Go cards
              If removed also removes mythBuntu_desktop

Revision history for this message
Buz Cory (buzco) said :
#9

As I look over this whole thread I see:

Much earlier mtn_biker_mike reported:

    EE failed to load module type 1
This means the type 1 fonts are not properly installed, you probably want to fix this.

    EE No devices detected

and further:

when I go to the Nvidia x server settings I get a err

    You do not appear to be using the NVIDIA X driver. Please edit your X configuration file (just run `nvidia-xconfig` as root), and restart the X server.

and still more:

    VALIDATION ERROR: Data incomplete in file /etc/X11/xorg.conf.
                  Device section "Configured Video Device" must have a
                  Driver line.

These last are all problems w/ configuring X11.

They _should_ not occur if you are using apt for your installs.

In any future reports please copy/paste the current xorg.config file into the report and all error messages logged. If you can't find the log or there is none, that would be a thing to work on.

At the moment, the entire problem seems to be not which nVidia driver you have installed but the X11 config getting messed up in the process.

== Buz :)

Revision history for this message
izzy200198 (izzy200198) said :
#10

i had this same problem. from the grub menu i booted from the previous kernel and it was perfect, new drivers and all.

But if i reboot into latest kernal, problem remains.

Revision history for this message
bkp (bkp) said :
#11

I'm having the same problem after upgrading my kernel. I had nvidia 177 and it was working fine.

Upgraded kernel: failed to load module "type1"

Used synaptic to upgrade nvidia driver to 180: problem remains.

Sooo... if the problem is related to the fonts, then it stands to reason that maybe some (unknown?) dependency didn't get upgraded with the kernel. The only thing I could find that it might be is xserver-xorg-core. I'm updating it now and will report back the results.

Revision history for this message
bkp (bkp) said :
#12

Nope, it still says module type1 does not exist.

Revision history for this message
bkp (bkp) said :
#13

My woes began when I upgraded the kernel from 2.6.27-7 to 2.6.27-11 and rebooted. (I was using nvidia 177.)

I don't even remember everything I tried, but I did have a good backup of my xorg.conf, but unfortunately that didn't help. I also removed the 2.6.27-11 kernel and still I couldn't get any valid modes to work with either nvidia driver (177 & 180) I tried from the synaptic package manager. Only the VESA driver would work.

For some reason, I had some *180.22* files lying around in various places. So, I executed:
sudo apt-get purge nvidia*

After that, I deleted everything found by:
sudo find /usr |grep -i nvidia |grep -iv src/linux-headers
and
sudo find /usr |grep -i 180.22 |grep -iv src/linux-headers

Finally, that left some orphaned symbolic links, so I did this...
sudo find /usr -type l | while read f; do if [ ! -e "$f" ]; then sudo rm -f "$f"; fi; done

Last, but not least, I used package manager to reinstall...
sudo apt-get install nvidia-settings nvidia-180-kernel-source nvidia-glx-180 nvidia-180-modaliases

But even after that, I still couldn't get 1360x768 to work, which was the only mode I've used for the past few months as it's the native resolution of my Westinghouse SK-32H240S, but I did get 1280x720 to work fairly well.

I then tried
sudo apt-get purge nvidia*
(changed my xorg.conf to use vesa, then rebooted)
sudo apt-get install nvidia-settings nvidia-177-kernel-source nvidia-glx-177 nvidia-177-modaliases
(changed xorg.conf to use nvidia, rebooted)

So, now I'm back to the same kernel and the same nvidia driver, but I still can't get back to my TV's native resolution that I've used for months. Having to settle for 1280*720... CRAZY!!!

Revision history for this message
codywohlers (codywohlers) said :
#14

bkp:

I have a similar situation to you with dual "Venturer" monitors and a GeForce 9400. The problem you might have, might be what I have - that is that my monitors aren't actually monitors, they are TVs with a VGA input, and as such do not have any Extended Display Information Data (EDID). The EDID is what the video card uses to determine max resolution, refresh rate, etc. The problem I found was the nvidia drivers would, with a lack of any EDID, would not load properly.

I got my setup working again (1680(x2) x 1050) on 2.6.27.-11 with the 180.44 drivers from nvidia.com. The trick was to use my old xorg.conf after the setup was complete.

If you don't have your old xorg.conf, I originally fixed this same problem during the original install of intrepid (8.10) by working-around the lack of any EDID in my monitors. I did this by manually editing xorg.conf and extending the maximum range of HorizSync and VertRefresh to a large number like 400.0 Then you will have ALL the resolutions and refresh rates available and you can pick one that YOU know works for your monitor.

If all else fails, check the xorg log (/var/logs/Xorg.0.log) to see if it can provide further insight. That's how I found my EDID problem. One line of my log says "NVIDIA(0): CRT-0: 400MHz maximum pixel clock" - this is my "faked" VertRefresh.

Good luck bkp, hope you get back to 1360x768.

cody.wohlers

Revision history for this message
Buz Cory (buzco) said :
#15

Hello all --

The problem appears not to be with what _display_ hardware u r using, but that Ubuntu puts part of the display driver into the "initrd" image and part onto your hard drive (in /etc/xorg and possibly elsewhere).

This is IMHO a bug in the kernel upgrade packages.

The answer seems to reboot in _recovery_ mode from the last kernel that worked, find the xorg-conf file that mentions nvidia and copy or soft-link it as the one to use, then reboot from the last working kernel.

You may be able to do this using the upgraded kernel, but I wouldn't bet on it.

Other useful steps _may_ be to purge and re-install the restricted nvidia package.

In any event, once you get your display working properly, don't _ever_ do a kernel upgrade again unless you are ready to do display fix-up steps again.

The real fix should probably be to compile the kernel from source to exactly match your system w/ most or all drivers built-in (minimize loading modules) and with _no_ initrd. Unfortunately, this may break the whole install/upgrade process.

Hope this helps,
-- Buz :)

Can you help with this problem?

Provide an answer of your own, or ask mtn_biker_mike for more information if necessary.

To post a message you must log in.