Bug #684083 “Plymouth hangs after installation of nvidia drivers...” : Bugs : plymouth package : Ubuntu

Revision history for this message

Fabio Marconi (fabiomarconi) wrote on 2010-12-02:

#1

BootDmesg.txt Edit (42.1 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.7 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.8 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (13.7 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (579 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.0 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (91.2 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (214.2 KiB, text/plain; charset="utf-8")

summary:	- Plymouth hangs after installation of nvidia drivers on natty + Plymouth hangs after installation of nvidia drivers on natty 20101202
tags:	added: iso-testing

Revision history for this message

Fabio Marconi (fabiomarconi) wrote on 2010-12-02: Re: Plymouth hangs after installation of nvidia drivers on natty 20101202

#2

syslog Edit (699.6 KiB, text/plain)

Revision history for this message

Fabio Marconi (fabiomarconi) wrote on 2010-12-02:

#3

Download full text (9.2 KiB)

Dec 2 11:35:52 localhost gdm-binary[907]: WARNING: Unable to load file '/etc/gdm/custom.conf': Nessun file o directory
Dec 2 11:35:53 localhost gdm-binary[907]: WARNING: Unable to find users: no seat-id found
Dec 2 11:35:53 localhost gdm-simple-slave[988]: WARNING: Unable to load file '/etc/gdm/custom.conf': Nessun file o directory
Dec 2 11:35:53 localhost acpid: client connected from 993[0:0]
Dec 2 11:35:53 localhost acpid: 1 client rule loaded
Dec 2 11:35:54 localhost kernel: [ 33.315524] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0
Dec 2 11:35:56 localhost acpid: client connected from 993[0:0]
Dec 2 11:35:56 localhost acpid: 1 client rule loaded
Dec 2 11:35:56 localhost kernel: [ 35.703679] Xorg:993 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec 2 11:35:56 localhost kernel: [ 35.703687] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec 2 11:35:56 localhost kernel: [ 35.704239] Xorg:993 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec 2 11:35:56 localhost kernel: [ 35.704243] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec 2 11:35:56 localhost gdm-simple-slave[1017]: WARNING: Unable to load file '/etc/gdm/custom.conf': Nessun file o directory
Dec 2 11:35:56 localhost acpid: client 993[0:0] has disconnected
Dec 2 11:35:56 localhost acpid: client 993[0:0] has disconnected
Dec 2 11:35:56 localhost acpid: client connected from 1019[0:0]
Dec 2 11:35:56 localhost acpid: 1 client rule loaded
Dec 2 11:35:57 localhost acpid: client connected from 1019[0:0]
Dec 2 11:35:57 localhost acpid: 1 client rule loaded
Dec 2 11:35:57 localhost kernel: [ 36.675463] Xorg:1019 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec 2 11:35:57 localhost kernel: [ 36.675470] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec 2 11:35:57 localhost kernel: [ 36.676016] Xorg:1019 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec 2 11:35:57 localhost kernel: [ 36.676021] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec 2 11:35:57 localhost gdm-binary[907]: WARNING: GdmDisplay: display lasted 0,946769 seconds
Dec 2 11:35:57 localhost gdm-simple-slave[1023]: WARNING: Unable to load file '/etc/gdm/custom.conf': Nessun file o directory
Dec 2 11:35:57 localhost acpid: client 1019[0:0] has disconnected
Dec 2 11:35:57 localhost acpid: client 1019[0:0] has disconnected
Dec 2 11:35:57 localhost acpid: client connected from 1025[0:0]
Dec 2 11:35:57 localhost acpid: 1 client rule loaded
Dec 2 11:35:58 localhost acpid: client connected from 1025[0:0]
Dec 2 11:35:58 localhost acpid: 1 client rule loaded
Dec 2 11:35:58 localhost kernel: [ 37.614237] Xorg:1025 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec 2 11:35:58 localhost kernel: [ 37.614244] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec 2 11:35:58 localhost kernel: [ 37.614791] Xorg:1025 con...

Dec  2 11:35:52 localhost gdm-binary[907]: WARNING: Unable to load file '/etc/gdm/custom.conf': Nessun file o directory
Dec  2 11:35:53 localhost gdm-binary[907]: WARNING: Unable to find users: no seat-id found
Dec  2 11:35:53 localhost gdm-simple-slave[988]: WARNING: Unable to load file '/etc/gdm/custom.conf': Nessun file o directory
Dec  2 11:35:53 localhost acpid: client connected from 993[0:0]
Dec  2 11:35:53 localhost acpid: 1 client rule loaded
Dec  2 11:35:54 localhost kernel: [   33.315524] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0
Dec  2 11:35:56 localhost acpid: client connected from 993[0:0]
Dec  2 11:35:56 localhost acpid: 1 client rule loaded
Dec  2 11:35:56 localhost kernel: [   35.703679] Xorg:993 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec  2 11:35:56 localhost kernel: [   35.703687] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec  2 11:35:56 localhost kernel: [   35.704239] Xorg:993 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec  2 11:35:56 localhost kernel: [   35.704243] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec  2 11:35:56 localhost gdm-simple-slave[1017]: WARNING: Unable to load file '/etc/gdm/custom.conf': Nessun file o directory
Dec  2 11:35:56 localhost acpid: client 993[0:0] has disconnected
Dec  2 11:35:56 localhost acpid: client 993[0:0] has disconnected
Dec  2 11:35:56 localhost acpid: client connected from 1019[0:0]
Dec  2 11:35:56 localhost acpid: 1 client rule loaded
Dec  2 11:35:57 localhost acpid: client connected from 1019[0:0]
Dec  2 11:35:57 localhost acpid: 1 client rule loaded
Dec  2 11:35:57 localhost kernel: [   36.675463] Xorg:1019 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec  2 11:35:57 localhost kernel: [   36.675470] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec  2 11:35:57 localhost kernel: [   36.676016] Xorg:1019 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec  2 11:35:57 localhost kernel: [   36.676021] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec  2 11:35:57 localhost gdm-binary[907]: WARNING: GdmDisplay: display lasted 0,946769 seconds
Dec  2 11:35:57 localhost gdm-simple-slave[1023]: WARNING: Unable to load file '/etc/gdm/custom.conf': Nessun file o directory
Dec  2 11:35:57 localhost acpid: client 1019[0:0] has disconnected
Dec  2 11:35:57 localhost acpid: client 1019[0:0] has disconnected
Dec  2 11:35:57 localhost acpid: client connected from 1025[0:0]
Dec  2 11:35:57 localhost acpid: 1 client rule loaded
Dec  2 11:35:58 localhost acpid: client connected from 1025[0:0]
Dec  2 11:35:58 localhost acpid: 1 client rule loaded
Dec  2 11:35:58 localhost kernel: [   37.614237] Xorg:1025 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec  2 11:35:58 localhost kernel: [   37.614244] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec  2 11:35:58 localhost kernel: [   37.614791] Xorg:1025 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec  2 11:35:58 localhost kernel: [   37.614795] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec  2 11:35:58 localhost gdm-binary[907]: WARNING: GdmDisplay: display lasted 0,938184 seconds
Dec  2 11:35:58 localhost gdm-simple-slave[1029]: WARNING: Unable to load file '/etc/gdm/custom.conf': Nessun file o directory
Dec  2 11:35:58 localhost acpid: client 1025[0:0] has disconnected
Dec  2 11:35:58 localhost acpid: client 1025[0:0] has disconnected
Dec  2 11:35:58 localhost acpid: client connected from 1031[0:0]
Dec  2 11:35:58 localhost acpid: 1 client rule loaded
Dec  2 11:35:59 localhost acpid: client connected from 1031[0:0]
Dec  2 11:35:59 localhost acpid: 1 client rule loaded
Dec  2 11:35:59 localhost kernel: [   38.568614] Xorg:1031 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec  2 11:35:59 localhost kernel: [   38.568621] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec  2 11:35:59 localhost kernel: [   38.569173] Xorg:1031 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec  2 11:35:59 localhost kernel: [   38.569177] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec  2 11:35:59 localhost gdm-binary[907]: WARNING: GdmDisplay: display lasted 0,952845 seconds
Dec  2 11:35:59 localhost gdm-simple-slave[1035]: WARNING: Unable to load file '/etc/gdm/custom.conf': Nessun file o directory
Dec  2 11:35:59 localhost acpid: client 1031[0:0] has disconnected
Dec  2 11:35:59 localhost acpid: client 1031[0:0] has disconnected
Dec  2 11:35:59 localhost acpid: client connected from 1037[0:0]
Dec  2 11:35:59 localhost acpid: 1 client rule loaded
Dec  2 11:36:00 localhost acpid: client connected from 1037[0:0]
Dec  2 11:36:00 localhost acpid: 1 client rule loaded
Dec  2 11:36:00 localhost kernel: [   39.506821] Xorg:1037 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec  2 11:36:00 localhost kernel: [   39.506828] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec  2 11:36:00 localhost kernel: [   39.507375] Xorg:1037 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec  2 11:36:00 localhost kernel: [   39.507379] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec  2 11:36:00 localhost gdm-binary[907]: WARNING: GdmDisplay: display lasted 0,937490 seconds
Dec  2 11:36:00 localhost gdm-simple-slave[1041]: WARNING: Unable to load file '/etc/gdm/custom.conf': Nessun file o directory
Dec  2 11:36:00 localhost acpid: client 1037[0:0] has disconnected
Dec  2 11:36:00 localhost acpid: client 1037[0:0] has disconnected
Dec  2 11:36:00 localhost acpid: client connected from 1043[0:0]
Dec  2 11:36:00 localhost acpid: 1 client rule loaded
Dec  2 11:36:01 localhost acpid: client connected from 1043[0:0]
Dec  2 11:36:01 localhost acpid: 1 client rule loaded
Dec  2 11:36:01 localhost kernel: [   40.480303] Xorg:1043 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec  2 11:36:01 localhost kernel: [   40.480310] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec  2 11:36:01 localhost kernel: [   40.480864] Xorg:1043 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec  2 11:36:01 localhost kernel: [   40.480868] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec  2 11:36:01 localhost gdm-binary[907]: WARNING: GdmDisplay: display lasted 0,972420 seconds
Dec  2 11:36:01 localhost gdm-simple-slave[1047]: WARNING: Unable to load file '/etc/gdm/custom.conf': Nessun file o directory
Dec  2 11:36:01 localhost acpid: client 1043[0:0] has disconnected
Dec  2 11:36:01 localhost acpid: client 1043[0:0] has disconnected
Dec  2 11:36:01 localhost acpid: client connected from 1049[0:0]
Dec  2 11:36:01 localhost acpid: 1 client rule loaded
Dec  2 11:36:02 localhost acpid: client connected from 1049[0:0]
Dec  2 11:36:02 localhost acpid: 1 client rule loaded
Dec  2 11:36:02 localhost kernel: [   41.419564] Xorg:1049 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec  2 11:36:02 localhost kernel: [   41.419571] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec  2 11:36:02 localhost kernel: [   41.420438] Xorg:1049 conflicting memory types d0000000-d0480000 write-combining<->uncached-minus
Dec  2 11:36:02 localhost kernel: [   41.420443] reserve_memtype failed 0xd0000000-0xd0480000, track write-combining, req write-combining
Dec  2 11:36:02 localhost NetworkManager[475]: <info> (wlan0): preparing device.
Dec  2 11:36:02 localhost NetworkManager[475]: <info> (wlan0): deactivating device (reason: 2).
Dec  2 11:36:02 localhost NetworkManager[475]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:10.0/0000:04:0a.0/net/wlan0, iface: wlan0)
Dec  2 11:36:02 localhost NetworkManager[475]:    SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:10.0/0000:04:0a.0/net/wlan0, iface: wlan0): no ifupdown configuration found.
Dec  2 11:36:02 localhost kernel: [   41.530306] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec  2 11:36:02 localhost NetworkManager[475]: <error> [1291286162.574022] [nm-manager.c:1373] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Dec  2 11:36:02 localhost NetworkManager[475]: <info> (wlan0): supplicant interface state:  starting -> ready
Dec  2 11:36:02 localhost NetworkManager[475]: <info> (wlan0): device state change: 2 -> 3 (reason 42)
Dec  2 11:36:02 localhost gdm-binary[907]: WARNING: GdmDisplay: display lasted 1,020319 seconds
Dec  2 11:36:02 localhost gdm-binary[907]: WARNING: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors
Dec  2 11:36:02 localhost init: plymouth-stop pre-start process (1077) terminated with status 1

Fabio Marconi (fabiomarconi) on 2010-12-04

summary:	- Plymouth hangs after installation of nvidia drivers on natty 20101202 + Plymouth hangs after installation of nvidia drivers on natty alpha1
description:	updated

Revision history for this message

Colin Watson (cjwatson) wrote on 2010-12-10:

#4

Does it make a difference if you set GRUB_GFXPAYLOAD_LINUX=keep in /etc/default/grub and run 'sudo update-grub'?

(Speculation: plymouth has trouble dealing with the framebuffer type changing in mid-flight.)

Changed in plymouth (Ubuntu):
status:	New → Incomplete
importance:	Undecided → High

Revision history for this message

Fabio Marconi (fabiomarconi) wrote on 2010-12-10:

#5

Hello Colin.
The suggested line don't fix this issue, but i've found that this bug is reproducible only if we have one operating system in the disk,becouse if we have two ubuntu (regarding one ubuntu and one windows i don't know) on the same disk , then grub menu appear, this issue don't happen and everythings works.
Tomorrow i'm going to test with two Ubuntu on two disks (one at disk).
This on 20101206 amd64
Thanks
Fabio

Revision history for this message

Fabio Marconi (fabiomarconi) wrote on 2010-12-11:

#6

Update:
Bug is reproducible in this cases:
One ubuntu at disk, if we have two ubuntu on the same disk it don't affect, but if we have two ubuntu on two disk (one at disk) bug appear.
Thanks
Fabio

Revision history for this message

Fabio Marconi (fabiomarconi) wrote on 2010-12-15:

#7

still present in 20101215 amd64

Revision history for this message

Fabio Marconi (fabiomarconi) wrote on 2010-12-16:

#8

Update:
I found a switch, during grub screen if I press a key, bug appear (with two disks), but if I lay pass the delay time byself, system boot correctly.
If I have just one disk with one ubuntu, bug appear because grub delay is set to 0.
Now I dpn't have time to install more systems, tomorrow or saturday i'll do it, can you give me some suggestion to point this pig ?
Thanks
Fabio

Revision history for this message

Colin Watson (cjwatson) wrote on 2010-12-17:

#9

I apologise - I misspoke earlier. Could you please try GRUB_GFXPAYLOAD_LINUX=text (not keep) in /etc/default/grub and run update-grub?

Your comments about this depending on what GRUB does to the display suggest to me that this will probably work.

Changed in plymouth (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Colin Watson (cjwatson) wrote on 2010-12-17:

#10

(I do have a spare nvidia system here, so I'll see what I can reproduce locally.)

Revision history for this message

Fabio Marconi (fabiomarconi) wrote on 2010-12-17:

#11

Hello Colin
This line fix the issue, also plymouth now show right dimension of characters, before they was too big.
Only things that between grub menu and plymouth we have, for some seconds a blinking cursor.
Thanks
Fabio

Revision history for this message

Colin Watson (cjwatson) wrote on 2010-12-18: Re: [Bug 684083] Re: Plymouth hangs after installation of nvidia drivers on natty alpha1

#12

Well, yes, of course, the point of gfxpayload=keep is to eliminate the
phase when the console is in text mode at boot. :-)

Revision history for this message

Colin Watson (cjwatson) wrote on 2011-01-21:

#13

I tried installing the nvidia drivers on an up-to-date natty system, and everything worked more or less perfectly (plymouth wasn't at a particularly great resolution, but it did display fsck output, and X came up fine).

We've been working on a number of graphical boot problems, and it's possible that we managed to fix this one by accident. Can you undo the GRUB_GFXPAYLOAD_LINUX=text workaround, rerun update-grub, upgrade everything (especially grub-pc, the kernel, and plymouth) to current natty, and try again? Feel free to set this bug back to Confirmed if it's still broken, and we can figure out what to investigate next.

Changed in plymouth (Ubuntu Natty):
status:	Confirmed → Incomplete

Revision history for this message

Doug Bates (coloneldare) wrote on 2011-02-08:

#14

Excuse me if not relevant, but I tried Natty for the 1st time today (using daily build), and seemed to work OK until I selected hardware drivers available (Nvidia on AMD64x4 hardware using the 386 iso). On re-boot system hangs at 'Ubuntu (dot-dot-dot' logo).

Couldn't to a error report 'cus no system :-( Sorry

Doug

Revision history for this message

pvdeynse (vandeynse) wrote on 2011-02-08:

#15

@Doug

the "nvidia" driver is currently broken in Natty, see Bug #711409
you should be able to boot in "recovery mode" and rename file "/etc/X11/xorg.conf" (e.g. "/etc/X11/xorg.conf_backup")
this should allow to boot the system using the fallback "nouveau" video driver, at least thats how it worked for me.
we have to wait till bug #711409 is fixed.

Kate Stewart (kate.stewart) on 2011-03-03

Changed in plymouth (Ubuntu Natty):
assignee:	nobody → Canonical Foundations Team (canonical-foundations)
status:	Incomplete → Confirmed

Revision history for this message

Fabio Marconi (fabiomarconi) wrote on 2011-03-19:

#16

[ 1074.272314] nvidia: module license 'NVIDIA' taints kernel.
[ 1074.272322] Disabling lock debugging due to kernel taint
[ 1075.357137] NVRM: The NVIDIA probe routine was not called for 1 device(s).
[ 1075.357146] NVRM: This can occur when a driver such as nouveau, rivafb,
[ 1075.357151] NVRM: nvidiafb, or rivatv was loaded and obtained ownership of
[ 1075.357155] NVRM: the NVIDIA device(s).
[ 1075.357161] NVRM: Try unloading the conflicting kernel module (and/or
[ 1075.357165] NVRM: reconfigure your kernel without the conflicting
[ 1075.357169] NVRM: driver(s)), then try loading the NVIDIA kernel module
[ 1075.357173] NVRM: again.
[ 1075.357177] NVRM: No NVIDIA graphics adapter probed!

Seems related.

Revision history for this message

Robbie Williamson (robbiew) wrote on 2011-03-31:

#17

I have the latest nvidia driver working fine with my amd64 64bit Ubuntu Desktop installation. Can someone please confirm this bug still exists.

Changed in plymouth (Ubuntu Natty):
status:	Confirmed → Incomplete

Revision history for this message

robert marshall (robert-capuchin) wrote on 2011-04-01:

#18

I think I may be seeing this issue - upgraded to 11.04 today have nvidia drivers (MSI 7253 m/board) and can't get it to boot - if I use gfxpayload=text it appears to get further but still doesn't complete boot - stopping after scripts/init-bottom.
I have two ubuntu installations on the same disk
Same prob with both recovery mode and normal mode - or is this diff and need to open new bug?

Revision history for this message

Fabio Marconi (fabiomarconi) wrote on 2011-04-02:

#19

Hello
In Ubuntu 20110402 amd64 the proposed nvidia driver (270.30-0ubuntu3) are working fine.
Is there someone that still affecting ?

Revision history for this message

Erçin EKER (ercineker) wrote on 2011-04-06:

#20

i think its something to do with uvesafb

when i use "video=uvesafb:mode_option=1600x900-24,mtrr=3,scroll=ywrap" in the command live the console isnt shown and when i switch from x to a terminal it locks up when i remove that from boot it words but not pretty with a big screen :(

Revision history for this message

anujahooja (anuj-ahooja) wrote on 2011-04-07:

#21

Hung yesterday after installing the proprietary NVIDIA driver for the GeForce G210M on my Sony Vaio VPCCW17FD.

Driver downloaded here: http://www.nvidia.com/object/linux-display-ia32-260.19.44-driver.html

Side Note: This driver worked properly on Lucid, but had problems in Maverick. In Maverick it never hung, it just didn't configure for 3D graphics; for Natty it hangs completely at the Plymouth bootsplash.

Revision history for this message

Robbie Williamson (robbiew) wrote on 2011-04-08:

#22

@anujahooja

Please use the approved proprietary driver we provide via the "Additional Drivers" application from within the system settings. You can also launch this application from the command line by typing:
sudo jockey-gtk

We cannot be responsible nor effectively debug systems using drivers we have not provided, sorry.

Revision history for this message

anujahooja (anuj-ahooja) wrote on 2011-04-08:

#23

@robbie

Unfortunately my video card isn't compatible with the recommended proprietary driver. It's been an issue since 9.10 for me - I've been using the one I referenced earlier and worked fine for 9.10 and 10.04. I'll try and debug myself, thanks anyways!

Revision history for this message

Erçin EKER (ercineker) wrote on 2011-04-08:

#24

@anujahooja

260 and 270 drivers are compatible with your graphics card according to nvidia :) i have 270.30 installed from ubuntu archive... Suggest that u try what Robbie told :)

Revision history for this message

anujahooja (anuj-ahooja) wrote on 2011-04-08:

#25

@Ercin

I looked into 270 drivers for the G210M and the only one I could find was the 270.18, but it's only for AMD. I'm currently running an x86_64 machine. Is there a compatibility page for the 270.30 I can see?

Thanks for the help! :)

Revision history for this message

Erçin EKER (ercineker) wrote on 2011-04-08:

#26

check it on synaptic :) nvidia-current is the driver

Revision history for this message

anujahooja (anuj-ahooja) wrote on 2011-04-09:

#27

Awesome! Thanks, Ercin! It worked on Natty Beta 1 for you?

Revision history for this message

anujahooja (anuj-ahooja) wrote on 2011-04-09:

#28

Never mind - it worked! Thanks Ercin!

Revision history for this message

german (germandiago) wrote on 2011-04-10:

#29

I keep having the same problem. It hangs when booting. My model of NVIDIA card is a Geforce 7300 GT.

Revision history for this message

madbiologist (me-again) wrote on 2011-04-17:

#30

@german - Are you using the default Nouveau driver or the proprietary NVIDIA driver?

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2011-04-18:

#31

I'm closing this report because the issue is fixed for the original reporter. Other users with different graphics card/hardware/driver may experience all kind of different issues with similar symptoms. Please file a new report instead.

Thanks for your help to make Ubuntu better.

Changed in plymouth (Ubuntu Natty):
status:	Incomplete → Fix Released

Ubuntu
plymouth package

Plymouth hangs after installation of nvidia drivers on natty alpha1

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Affects		Status	Importance	Assigned to	Milestone
	plymouth (Ubuntu)	Fix Released	High	Canonical Foundations Team
	Natty	Fix Released	High	Canonical Foundations Team

Ubuntuplymouth package

Plymouth hangs after installation of nvidia drivers on natty alpha1

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
plymouth package