Fix MSI mapping quirk on HT-based nVidia platform
Bug #181081 reported by
Stas Sușcov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
Medium
|
|||
linux (Fedora) |
Fix Released
|
High
|
|||
linux (Ubuntu) |
Fix Released
|
Medium
|
Tim Gardner | ||
Hardy |
Fix Released
|
Medium
|
Tim Gardner | ||
Intrepid |
Fix Released
|
Medium
|
Tim Gardner |
Bug Description
Binary package hint: nic-modules-
My network controller can not get an ip from dhcp after installing the 7th December build of Ubuntu Hardy.
First I thought it because of this bug https:/
My network controller after lspci is:
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
The system I own is an Asus A6M laptop, with AMD 64bit CPU on an NForce2 motherboard.
description: | updated |
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | Incomplete → Triaged |
description: | updated |
Changed in linux: | |
status: | Unknown → Confirmed |
Changed in linux: | |
status: | Unknown → Confirmed |
Changed in linux: | |
status: | Confirmed → In Progress |
Changed in linux: | |
status: | Confirmed → Fix Released |
Changed in linux: | |
status: | Confirmed → Triaged |
Changed in linux: | |
milestone: | none → ubuntu-8.04.1 |
Changed in linux: | |
assignee: | nobody → timg-tpi |
importance: | Undecided → Medium |
milestone: | none → ubuntu-8.04.1 |
status: | New → Fix Committed |
Changed in linux: | |
milestone: | ubuntu-8.04.1 → none |
Changed in linux: | |
status: | In Progress → Fix Released |
Changed in linux: | |
importance: | Unknown → Medium |
Changed in linux (Fedora): | |
importance: | Unknown → High |
To post a comment you must log in.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team: /wiki.ubuntu. com/KernelTeamB ugPolicies . Thanks in advance!
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https:/