Trisquel installation - Checking
Hi,
I tried live trisquel_7.0_amd64.iso on a computer.
A rare noise came from the computer. I think it was a disk creeping or something like that. It was continuous.
(I had sound, monitor and internet connection working)
So, I would like to know all checks or what steps do I have to take, to ensure that the whole computer could work right. (Or other hardware is needed)
Thanks.
I am a translator!
>So, I would like to know all checks or what steps do I have to take, to ensure that the whole computer could work right.
The two components that need to be checked are the GPU and the wifi adapter. If it is an AMD GPU then you are going to be very, very disappointed (without the proprietary firmware you will have no video acceleration, and a furnace, expect temps as high as 100 C now that it is summer, almost).
Intel GPUs other than the new skylake will do their job perfectly fine. Most Nvidias will work fine (at least they did on every PC I installed Debian or Trisquel on for those few relatives and mates that care about free software). Maybe I was lucky though, maybe it is not true that most Nvidias will do.
The wifi adapter must be an Atheros 802.11N chip, series
AR9xxx or AR5xxx.
* GPU - NVIDIA 680 OC
* No wifi adapter
But there must be an "Device Administrator" to check that everything works fine. (Or commands) - A guide that a Trisquel installer should follow to check a successful and flawless installation.
I used 'hardinfo' to generate a report, but it only list and doesn't tell if a device is no compatible or drivers are needed. And synchronization didn't work.
Thanks.
Regarding the "Device Administrator" and how to check if everything
works:
One can do so by using your favorite text editor to open and read these
files:
"/var/log/syslog"
"/var/log/dmesg"
"/var/log/Xorg.0.log"
And, search for "err", "warn", "caut" and "att" to look for errors,
warnings, cautions and attentions, respectfully. Make sure to do the
search without case sensitivity.
You can also open a terminal and do (the "$ " is used just so you know
which lines you must type, it can be ignored when typing):
$ sudo lspci -knn | less
"sudo" will ask for your user's password at first. When typing, it won't
appear at the screen, for safety purposes.
Inside GNU less, use the arrow keys to look for any PCI device that has
no kernel driver or that has "Unassigned" in the name, because these
might be the "bad guys". When done, press Q to close GNU less. If you
want to know the other useful things about GNU less, press H instead of
Q. Be aware that the GNU less search function is case sensitive.
Also, to find any problem with the USB devices, do:
$ sudo lsusb -t | less
$ sudo lsusb | less
You must use both "lsusb" invocations. The first one is used so that you
can see which USB device has a driver in use, those which don't can be
signal of problems (not aways). Then use the second invocation to know
which bus and device refers to which USB, when there is a problem.
>I tried live trisquel_7.0_amd64.iso on a computer.
A rare noise came from the computer. I think it was a disk creeping or something like that. It was continuous.<
A live session doesn't tamper with your hard disk, so the noise can only come from the optical media itself or a cooling fan. Everything else is unrelated.
Try this (lshw must be installed and run as root to get proper results):
lshw -html > myhardware.html
It will print output to a html file so you can browse it in Abrowser.
Maybe Alejandro was reading or writing a file on the disk (otherwise, you are right). Frequently checking the SMART data of the disks always is a good idea. The "Disks" utility in the "System Settings" makes it easy: select the disk on the left, click the button with the "gear" and choose "SMART data & Self-Tests...".
30 sectors with errors... (sdb)
What is the meaning of the red listed devices? (lshw -html)
I think it's the same as "unclaimed" (not recognized or correctly known by kernel) in the normal CLI listing in a terminal window.
https://unix.stackexchange.com/questions/59201/unclaimed-device-in-lshw#60332
" "unclaimed" (not recognized or correctly known by kernel) in the normal CLI listing in a terminal window " = not working with the OS ?
* Most of the red reports came form the Intel Processor: Xeon E5/Core i7
CPU Internal L3
and ohters
thanks.