>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.
-----------------------------------
Here it is. Please note that I am using a live CD:
Linux ubuntu 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686
GNU/Linux
----------------------------------
>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.
------------------------
Sorry, but the task of saving these log files and either setting up an e-mail account to send them or copying them to my other machine where I can send them to you - without the use of a mouse - is a bit beyond this layman's capacity!
Unless you can give me a few magic tips, I will have to give up on these tasks I'm afraid.
Hi Brian,
>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.
------- ------- ------- ------- -------
Here it is. Please note that I am using a live CD:
Linux ubuntu 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686
GNU/Linux
------- ------- ------- ------- ------
>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. ------- ------- ---
-------
Sorry, but the task of saving these log files and either setting up an e-mail account to send them or copying them to my other machine where I can send them to you - without the use of a mouse - is a bit beyond this layman's capacity!
Unless you can give me a few magic tips, I will have to give up on these tasks I'm afraid.
Regards,
Bob