Kubuntu 10.10 nVidia, cannot start xorg

Bug #658258 reported by dk_zero-cool
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I have a problem after installing Kubuntu 10.10 on my laptop.
I'm currently running a resolution "800x600" because xorg cannot find my nVidia driver, whether I use the open source or nVidia's.

I have tried using the example from (http://rmic.be/ubuntu-maverick-nvidia-x-problem) that had the same problem, but this does not work for me. If I create an xorg file using nvidia-xconfig, xorg will not start at all.

I did not have any problems with neither Ubuntu or Kubuntu before 10.10

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.33
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: daniel 1676 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf4300000 irq 45'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,11700040,00100003 HDA:10573055,10573055,00100700'
   Controls : 22
   Simple ctrls : 14
Date: Mon Oct 11 12:36:22 2010
HibernationDevice: RESUME=UUID=b9d6eb37-313b-4726-bf9f-8559161fa75a
HotplugNewDevices:

HotplugNewMounts:

InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: Zepto Znote
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-22-generic root=UUID=361907fa-8541-4cc4-bb34-239c1bec9782 ro quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
 monitor will print the received events for:
 UDEV - the event which udev sends out after rule processing
UdisksMonitorLog: Monitoring activity from the disks daemon. Press Ctrl+C to cancel.
dmi.bios.date: 09/30/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: Z15N011
dmi.board.name: Znote
dmi.board.vendor: Zepto
dmi.board.version: 6025WD/6625WD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Zepto
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrZ15N011:bd09/30/2007:svnZepto:pnZnote:pvr6625WD:rvnZepto:rnZnote:rvr6025WD/6625WD:cvnZepto:ct1:cvrN/A:
dmi.product.name: Znote
dmi.product.version: 6625WD
dmi.sys.vendor: Zepto

Revision history for this message
dk_zero-cool (dk-zero-cool) wrote :
Revision history for this message
dk_zero-cool (dk-zero-cool) wrote :

It might be worth mention that if I reboot the machine about 10 to 15 times it boots up perfectly. Then if I reboot again it once again can't find the driver (the open source). I have done this tree times now but I can't make it continue to work. I don't do anything differently when I boot successfully.

Revision history for this message
dk_zero-cool (dk-zero-cool) wrote :

The problem is fixed.
Updated the 2.6.35.22 kernel to the 2.6.36.0 from the xorg-edgers repository. This resolved the issue. It would properly be a good idea to put this kernel in the main repository.

Revision history for this message
dk_zero-cool (dk-zero-cool) wrote :

Not fixed anyway apparently. It worked with the nouveau driver, but the nvidia driver ruined it. And now removing the nvidia driver does not fix it back.

Hope all this will help fix it in the future. I'm gonna go back to 10.04 as I need my laptop up and running.

Revision history for this message
Christian González (droetker) wrote :

same here, exactly. after removing the nvidia-glx-185 driver the nouveau can't handle the resolution any more, 1280x1024 is maximum instead if 1680x1050.
The xorg.conf is empty as it should be.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Christian González (droetker) wrote :

Solved the problem:
installed nvidia-current via apt-get.
added the following lines to /etc/modprobe.d/blacklist.conf:

blacklist nouveau
blacklist lbm-nouveau

and the rebooted

Now the X server uses the nvidia driver, and with the correct resolution.
funny, if I enable the desktop effects, they get enabled, but the messagebox says that the effects can't be enabled due to my X ersver settings (but I can see the shadow and transparency of that messagebox... When I click "ok" the effects are disabled again)

Revision history for this message
dk_zero-cool (dk-zero-cool) wrote :

Well, that does not do it for me.
But I did play around a bit more, and perhaps these error logs might help.

I started by installing the nvidia-current package.
Then I made sure that the modules nvidiafb, rivafb and nouveau was not loaded,
and then tried to load the nvidia-current module manually to see what would happen.
This is the output:

# modprobe nvidia-current
FATAL: Inserting nvidia-current (/lib/modules/2.6.35-22-generic/updates/dkms/nvidia-current.ko): No such device

# modprobe --force nvidia-current
FATAL: Inserting nvidia-current (/lib/modules/2.6.35-22-generic/updates/dkms/nvidia-current.ko): Invalid module format

(The /lib/modules/2.6.35-22-generic/updates/dkms/nvidia-current.ko does exist)

I then removed the nvidia-current package and downloaded the newest driver from the nvidia website.
It failed loading the module after build. I have attached the build log.

Revision history for this message
Christian González (droetker) wrote :

Sorry, you're right. It uses still the nouveau driver, the nvidia gets not loaded.
when I insert the nvidia-current module via modprobe, it gets loaded by the kernel (see "uname -a" output) without problems.

Linux aragorn 2.6.35-22-generic #34-Ubuntu SMP Sun Oct 10 09:26:05 UTC 2010 x86_64 GNU/Linux

I deinstalled xserver-xorg-video-nouveau, but X refuses tu use the nvidia driver.
BUT: I uninstalled nvidia-current, reinstalled xserver-xorg-video-nouveau, and now at least X recognizes my correct resolution again: 1680x1050.
But no desktop effects, (cannot be activated, check your config...") despite I see them working until I click ok. - then they get deactivated again - no chance to activate them persistently.

Revision history for this message
dk_zero-cool (dk-zero-cool) wrote :

I can't use any of the drivers. I tried with the 173 version, it loads fine using modprobe but the x server does not use it just like with the nouveau driver.

Revision history for this message
daemonx (perutka-ondrej) wrote :

I have the same problem. The only way I can start the xorg is to remove line Driver from xorg.conf or change the driver to "vesa".

Revision history for this message
shtumf (boris-fonda) wrote :

Same problem, only vesa works.

Revision history for this message
dk_zero-cool (dk-zero-cool) wrote :

I am starting to wonder if this issue is ever going to get fixed?
Or should we just continue running U10.04 for ever?

What I don't get is that some times the X Server registers the Video Card correctly. But only some times.

tags: removed: regression-potential
Revision history for this message
penalvch (penalvch) wrote :

dk_zero-cool, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

tags: added: regression-release
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.