[Trisquel-users] Re : Syslog and Kern.log

2017-07-20 Thread lcerf 
The kernel messages look more "low-level" to me.  But, again, it is very  
probable that I am wrong!  Over the years, I have been wrong multiple times  
in this forum.  I would first try deactivating the Wifi, as I wrote in the  
message above.

[Trisquel-users] Re : Syslog and Kern.log

2017-07-20 Thread lcerf 
It is very probable that my hypothesis ("*maybe* the hardware is defective")  
is wrong.  Do you have another hypothesis?  Or do you disagree that the  
problem "*apparently* is with the Wifi"?  That is easy to test:


Disconnect the Wifi (with the related Fn key on the keyboard or physically,  
e.g., if it is a USB adapter, maybe deactivating Wifi from NetworkManager is  
enough);
Save some space on the root partition (see  
https://trisquel.info/forum/trisquel-not-detecting-thinkpenguin-wifi-adapter-after-install#comment-118193  
that I have just written);
See if the message keeps on being logged in kern.log, looking at the live  
output of 'tail -F /var/log/kern.log' or with 'less /var/log/kern.log' after  
working a little (using Ethernet if the network is needed) or searching for  
pieces of it with 'grep'.

[Trisquel-users] Re : Syslog and Kern.log

2017-07-19 Thread lcerf 
It apparently is a problem with the Wifi.  You use the firmware that the  
package "open-ath9k-htc-firmware" provides, right?  I use it too but I have  
no problem.  Maybe the hardware is defective...

[Trisquel-users] Re : Syslog and Kern.log

2017-07-18 Thread lcerf 

See if some messages are repeated many times (and show them to us):
$ less /var/log/kern.log

[Trisquel-users] Re : Syslog and Kern.log

2017-07-18 Thread lcerf 
Having five lines (from "Missing Free firmware" to "Could not read microcode:  
-22") logged every 2ms (the numbers between squared brackets are times since  
the last boot) is abnormal... but the logs Davide0 are not like that.  They  
look normal, hence my question: do they still increase until you run out of  
disk space?  The newer version of Linux-libre may have solved the problem but  
the older logs may be still present, taking all the space.  Let us see the  
output of the following command that shows the twenty largest files in  
/var/log:

$ ls -lhS /var/log/ | head -20
If you cannot log into a graphical session (a full root partition does that  
if I remember well), log into a terminal with Ctrl+Alt+F1 (or Ctrl+Alt+F2 or  
... or Ctrl+Alt+F6).

[Trisquel-users] Re : Syslog and Kern.log

2017-07-17 Thread lcerf 
Those logs look normal.  Do they still increase until you run out of disk  
space?

[Trisquel-users] Re : Syslog and Kern.log

2017-07-16 Thread lcerf 
Well, the good solution would be to solve the problem that must be repeatedly  
written in kern.log.  What is it?  Maybe it is a support issue that would be  
solved by the installation of a newer kernel: https://jxself.org/linux-libre/