nForce error on ASUS board disables nouveau graphics fo NVIDIA

Bug #596373 reported by rasos
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

With an "Error probing SMB2" the nouveau nvidia current does not work on ASUS M3N78-VM with a 2.6.32-22 kernel. It had worked with ubuntu 9.10.
At boot we get:
nForce2_smbus : 0000:00:01.1 Error probing SMB2
Even without KMS and using a traditional xorg.conf for nvidia, the nvidia driver setting tool does not work.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.36
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: NVidia [HDA NVidia], device 0: VT1708B Analog [VT1708B Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: alton 1872 F.... xfce4-mixer-plu
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xf8f78000 irq 21'
   Mixer name : 'Nvidia MCP78 HDMI'
   Components : 'HDA:1106e721,10438345,00100100 HDA:10de0002,10de0101,00100000'
   Controls : 38
   Simple ctrls : 19
Date: Sat Jun 19 23:35:02 2010
HibernationDevice: RESUME=UUID=fafbb1b5-7dee-443e-8198-18a38564bd63
InstallationMedia: Mythbuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=bd0e558a-7f6c-4df7-aa6e-2affaf5b6006 ro quiet splash
ProcEnviron:
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:

SourcePackage: linux
dmi.bios.date: 07/28/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1307
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3N78-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1307:bd07/28/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-VM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
rasos (rasos) wrote :
Revision history for this message
rasos (rasos) wrote :

The problem has been also reported elsewhere, however it was considered a minor issue. It was also said that the problem was solved in kernel 2.6.32-19.28, but this does not seem to be true.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/440470/comments/66
I tried the workaround as well, adding "acpi_enforce_resources=lax" as a linux kernel parameter (via grub2), which only suppresses the message.
Still the same boot delay and still no working nouveau.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi rasos,

If you could also please 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.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
rasos (rasos) wrote :

Tried with latest development kernel 2.6.35-999: Yes, the "Error probing SMB2" disappeared on the ASUS M3N78-VM.

cat syslog | grep 'nForce2'
Jun 21 23:08:27 media kernel: [ 0.488975] cpufreq-nforce2: No nForce2 chipset.
Jun 21 23:08:27 media kernel: [ 15.781071] i2c i2c-0: nForce2 SMBus adapter at 0x600
Jun 21 23:08:27 media kernel: [ 15.781080] ACPI: resource nForce2_smbus [io 0x0700-0x073f] conflicts with ACPI region SM00 [??? 0x00000700-0x0000073f flags 0x30]

However, I was not able to get NVIDIA running yet.
So waiting for the next kernel made available with usual lucid update.

tags: removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
rasos (rasos) wrote :

nvidia driver problem solved: it did not have enough memory.

I always got
"Failed to initialize the NVIDIA graphics device PCI:2:0:0. " with falling back to low resolution, no matter which xorg.conf file I used.

vmalloc assigned only 100 mb by default, after updating to kernel 2.6.32-24.

QUICK FIX:
adding vmalloc=192M at the kernel start line

sudo nano /etc/default/grub
add line
GRUB_CMDLINE_LINUX="acpi_enforce_resources=lax vmalloc=192M"
and run
sudo update-grub

This solved all my nvidia problems I had when updating lucid lynx!

credits to:
http://www.pclinuxos.com/forum/index.php?topic=71334.0

Changed in linux (Ubuntu):
status: Triaged → Fix Committed
Changed in linux (Ubuntu):
status: Fix Committed → Triaged
status: Triaged → Fix Released
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.