[Lucid] kernel 2.6.32-22 module i2c-core missing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
When trying to further dig into bug #575296 (no module for 2nd i2c-bus on ASUS nForce boards), I had to realize that in Lucid's kernel the module
i2c-core
is missing. So I cannot force to load module i2c-nforce2 at address 0x1c40 (like Hardy does automatically). This results in following error message on boot-up Lucid:
ACPI: resource nForce2_smbus [0x1c40-0x1c7f] conflicts with ACPI region SM00 [0x1c40-0x1c45]
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
While Hardy correctly assignes the i2c-nforce2 to both i2c-busses:
i2c-adapter i2c-0: nForce2 SMBus adapter at 0x1c00
i2c-adapter i2c-1: nForce2 SMBus adapter at 0x1c40
In Hardy module i2c-nforce2 depends on i2c-core, not so in Lucid. Lucid only provides i2c-core for the EC2-kernel:
apt-file search i2c-core
linux-
linux-
As a result I cannot pass any arguments to i2c-core to bind to a certain I/O.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xfe024000 irq 21'
Mixer name : 'Analog Devices AD1988B'
Components : 'HDA:11d4198b,
Controls : 48
Simple ctrls : 26
Card1.Amixer.info:
Card hw:1 'U0x46d0x9a4'/'USB Device 0x46d:0x9a4 at usb-0000:00:02.1-9, high speed'
Mixer name : 'USB Mixer'
Components : 'USB046d:09a4'
Controls : 2
Simple ctrls : 1
Card1.Amixer.
Simple mixer control 'Mic',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
Capture channels: Mono
Limits: Capture 0 - 14
Mono: Capture 0 [0%] [23.75dB] [on]
DistroRelease: Ubuntu 10.04
HibernationDevice: #RESUME=
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelMo
Package: linux (not installed)
ProcCmdLine: root=/dev/sda9 ro splash
ProcEnviron:
LANG=de_DE.utf8
SHELL=/bin/bash
ProcVersionSign
Regression: Yes
RelatedPackageV
Reproducible: Yes
RfKill:
Tags: lucid kconfig regression-release needs-upstream-
Uname: Linux 2.6.32-22-generic x86_64
UserGroups: adm cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 09/25/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2N-E ACPI BIOS Revision 0402
dmi.board.name: M2N-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
Changed in linux (Ubuntu): | |
status: | Incomplete → Triaged |
tags: |
added: kernel-core kernel-needs-review removed: needs-kernel-logs needs-upstream-testing |
tags: | added: bios-outdated-1703 needs-upstream-testing |
Hi ingo,
Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http:// cdimage. ubuntu. com/releases/ . If the issue remains, please 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 597743
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/KernelMainl ineBuilds . 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.]