| 2008-12-14 16:31:47 |
Nikolaus Rath |
bug |
|
|
added bug |
| 2008-12-14 17:01:08 |
Jean-Baptiste Lallement |
update-manager: status |
New |
Incomplete |
|
| 2008-12-14 17:01:08 |
Jean-Baptiste Lallement |
update-manager: bugtargetdisplayname |
update-manager (Ubuntu) |
linux (Ubuntu) |
|
| 2008-12-14 17:01:08 |
Jean-Baptiste Lallement |
update-manager: bugtargetname |
update-manager (Ubuntu) |
linux (Ubuntu) |
|
| 2008-12-14 17:01:08 |
Jean-Baptiste Lallement |
update-manager: statusexplanation |
|
Thanks for your report. This is not an update-manager bug affecting to linux.
Unfortunately we can't fix it without more information.
Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
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" after a fresh boot 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://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance! |
|
| 2008-12-14 17:01:08 |
Jean-Baptiste Lallement |
update-manager: title |
Bug #307890 in update-manager (Ubuntu): "Update breaks sound, network, booting. Live CD works fine." |
Bug #307890 in linux (Ubuntu): "Update breaks sound, network, booting. Live CD works fine." |
|
| 2008-12-16 22:14:06 |
Nikolaus Rath |
bug |
|
|
added attachment 'dmesg-broken.txt' (dmesg-broken.txt) |
| 2008-12-16 22:14:17 |
Nikolaus Rath |
linux: status |
Incomplete |
New |
|
| 2008-12-16 22:14:17 |
Nikolaus Rath |
linux: statusexplanation |
Thanks for your report. This is not an update-manager bug affecting to linux.
Unfortunately we can't fix it without more information.
Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
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" after a fresh boot 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://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance! |
|
|
| 2008-12-16 22:14:29 |
Nikolaus Rath |
bug |
|
|
added attachment 'dmesg-working.txt' (dmesg-working.txt) |
| 2008-12-16 22:14:42 |
Nikolaus Rath |
bug |
|
|
added attachment 'lspci-broken.txt' (lspci-broken.txt) |
| 2008-12-16 22:14:51 |
Nikolaus Rath |
bug |
|
|
added attachment 'lspci-working.txt' (lspci-working.txt) |
| 2008-12-16 22:15:02 |
Nikolaus Rath |
bug |
|
|
added attachment 'uname-a-broken.txt' (uname-a-broken.txt) |
| 2008-12-16 22:15:11 |
Nikolaus Rath |
bug |
|
|
added attachment 'uname-working.txt' (uname-working.txt) |
| 2008-12-19 18:31:07 |
Leann Ogasawara |
linux: status |
New |
Incomplete |
|
| 2008-12-19 18:31:07 |
Leann Ogasawara |
linux: statusexplanation |
|
Hi Nikolaus,
I noticed that the the dmesg-working.txt file you attached shows the correct 2.6.27-9 kernel for intrepid. The dmesg-broken.txt file shows a much older 2.6.25 kernel which is only used for the linux-ports project. Which kernel package were you running in Hardy when you updated? |
|
| 2008-12-19 19:12:36 |
Nikolaus Rath |
linux: status |
Incomplete |
New |
|
| 2008-12-19 19:12:36 |
Nikolaus Rath |
linux: statusexplanation |
Hi Nikolaus,
I noticed that the the dmesg-working.txt file you attached shows the correct 2.6.27-9 kernel for intrepid. The dmesg-broken.txt file shows a much older 2.6.25 kernel which is only used for the linux-ports project. Which kernel package were you running in Hardy when you updated? |
|
|
| 2008-12-24 21:03:42 |
Leann Ogasawara |
linux: status |
New |
Won't Fix |
|
| 2008-12-24 21:03:42 |
Leann Ogasawara |
linux: statusexplanation |
|
I'd suggest not using the linux-image-386 image unless you want to run the ports kernel. Instead you should use linux-image-generic. Thanks. |
|
| 2008-12-26 11:56:16 |
Nikolaus Rath |
linux: status |
Won't Fix |
New |
|
| 2008-12-26 11:56:16 |
Nikolaus Rath |
linux: bugtargetdisplayname |
linux (Ubuntu) |
update-manager (Ubuntu) |
|
| 2008-12-26 11:56:16 |
Nikolaus Rath |
linux: bugtargetname |
linux (Ubuntu) |
update-manager (Ubuntu) |
|
| 2008-12-26 11:56:16 |
Nikolaus Rath |
linux: statusexplanation |
I'd suggest not using the linux-image-386 image unless you want to run the ports kernel. Instead you should use linux-image-generic. Thanks. |
That's fine with me. But in that case the hardy -> intrepid update process should make sure that the linux-generic kernel is installed and used, because in Hardy the linux-386 kernels worked fine. |
|
| 2008-12-26 11:56:16 |
Nikolaus Rath |
linux: title |
Bug #307890 in linux (Ubuntu): "Update breaks sound, network, booting. Live CD works fine." |
Bug #307890 in update-manager (Ubuntu): "Update breaks sound, network, booting. Live CD works fine." |
|
| 2009-02-05 11:24:51 |
Michele Mangili |
update-manager: status |
New |
Incomplete |
|
| 2009-02-05 11:24:51 |
Michele Mangili |
update-manager: statusexplanation |
That's fine with me. But in that case the hardy -> intrepid update process should make sure that the linux-generic kernel is installed and used, because in Hardy the linux-386 kernels worked fine. |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please add the log files from '/var/log/dist-upgrade/' to this bug report as separate attachments? Thanks in advance. |
|
| 2009-02-05 23:24:27 |
Nikolaus Rath |
update-manager: status |
Incomplete |
New |
|
| 2009-02-05 23:24:27 |
Nikolaus Rath |
update-manager: statusexplanation |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please add the log files from '/var/log/dist-upgrade/' to this bug report as separate attachments? Thanks in advance. |
Here they come.... |
|
| 2009-02-05 23:24:51 |
Nikolaus Rath |
bug |
|
|
added attachment 'apt.log' (apt.log) |
| 2009-02-05 23:25:30 |
Nikolaus Rath |
bug |
|
|
added attachment 'apt-term.log' (apt-term.log) |
| 2009-02-05 23:25:35 |
Nikolaus Rath |
bug |
|
|
added attachment 'main.log' (main.log) |
| 2009-02-05 23:25:42 |
Nikolaus Rath |
bug |
|
|
added attachment 'xorg_fix_intrepid.log' (xorg_fix_intrepid.log) |
| 2009-02-05 23:25:50 |
Nikolaus Rath |
bug |
|
|
added attachment 'term.log' (term.log) |
| 2009-04-22 12:15:38 |
Michael Vogt |
marked as duplicate |
|
353534 |
|
