[edgers] nvidia-313 issue: (EE) open /dev/dri/card0: No such file or directory

Bug #1106117 reported by dino99
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

Error with the latest kernel & nvidia on RR i386

 (EE) open /dev/dri/card0: No such file or directory

Note: the system seems to work normally (only get some drag & drop mouse issues).

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-2-generic 3.8.0-2.6
ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4
Uname: Linux 3.8.0-2-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: oem 2268 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Sat Jan 26 16:33:01 2013
HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 eth1 no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
MarkForUpload: True
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-2-generic root=UUID=9e61e83e-bca9-43cf-aa90-5a68892213fa ro crashkernel=384M-2G:64M,2G-:128M quiet
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-2-generic N/A
 linux-backports-modules-3.8.0-2-generic N/A
 linux-firmware 1.99
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WpaSupplicantLog:

dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5W DH Deluxe
dmi.product.version: System Version
dmi.sys.vendor: ASUSTEK COMPUTER INC

Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
dino99 (9d9) wrote :
dino99 (9d9)
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
dino99 (9d9)
description: updated
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.8 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc5-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
dino99 (9d9) wrote :

Still get the same issue with rc5 & nvidia
See xorg.0.log above, and these /var/log/upstart/ additional errors

Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
dino99 (9d9) wrote :
tags: added: bot-stop-nagging raringkernel-bug-exists-upstream
removed: raring
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream raring
removed: raringkernel-bug-exists-upstream
Revision history for this message
dino99 (9d9) wrote :

Same error with the latest 3.8.0-4 kernel & nvidia-310

Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
penalvch (penalvch) wrote :

dino99, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, please just make a comment to this.

tags: added: latest-bios-3002
description: updated
Changed in linux (Ubuntu):
importance: Medium → Low
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
Revision history for this message
StoatWblr (stoatwblr) wrote :

It's still an issue in trusty, at least. It may be contributing to being unable to get 4-headed X working properly across 2 GPUs (this is a dual GPU 4-output workstation card)

Xinerama works - badly.

Revision history for this message
penalvch (penalvch) wrote :

StoatWblr, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report by executing the following in a terminal:
ubuntu-bug xorg

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

For more on this, please see the official Ubuntu documentation:
Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report will delay your problem being addressed as quickly as possible.

Thank you for your understanding.

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.