We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
Hardy Heron 8.04 was recently released. It would be helpful if you
could test the new release and verify if this is still an issue -
http://www.ubuntu.com/getubuntu/download . You should be able to test
your bug using the LiveCD. Please let us know your results. Thanks.
** Changed in: linux (U
The 18 month support period for Edgy Eft 6.10 has reached it's end of
life. As a result, we are closing the linux-source-2.6.17 Edgy Eft
kernel task.
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Confirmed => Invalid
** Tags added: edgy-close
** Also affects: linux (Ubuntu)
Impo
** Changed in: linux-meta (Ubuntu)
Sourcepackagename: linux-meta => linux-source-2.6.17
Assignee: Cristian Aravena Romero => Ubuntu Kernel Team
Status: Needs Info => Confirmed
--
wireless not working after kernel update in edgy
https://launchpad.net/bugs/89520
--
ubuntu-bugs mailing
Here is the lspci output
** Attachment added: "lspci output"
http://librarian.launchpad.net/6640157/lspci-vvnn.log
--
wireless not working after kernel update in edgy
https://launchpad.net/bugs/89520
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/l
Hi,
Here are the files you asked.
the output of the uname -a is:
Linux ckg-laptop 2.6.17-11-generic #2 SMP Thu Feb 1 19:52:28 UTC 2007
i686 GNU/Linux
i dont know if it is correct but i tested the new ubuntu feisty and when
booting from cd, my network card is not being detected.
** Attachment
Thanks for taking the time to report this bug. Unfortunately we can't
fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already
done so (please pay attention to lspci's additional options), as required by
th
