If you work on older Laptops and you use a Console only System Setup like on Debian there is a Bug on systemd and the console-setup package since years. After reboot all Font Settings seems gone. But the Settings are not real gone, cause systemd does not pull the settings on boot!
How to fix?
edit the crontab of root by
sudo su -
insert the /bin/setupcon command on „@reboot“ means on every boot!
@reboot /bin/setupcon > /dev/null 2>&1
save and exit, reboot now
now the PC should echo big Fonts for old eyes „Terminus 20×12 Frambuffermode“
To run nouveau on upgrade 8.0 to 9.0 go to /etc/modprobe.d and remove MANUAL all blacklist configs (*.conf) of nvidia cause some glued on upgrade and are not purged automatic by the upgrade. Cause they will block nouveau load at boot (xserver-xorg-video-nouveau)
Then run on Terminal:
$sudo update-initramfs -u -k all
Older Hardware isn’t supported by Legacy Drivers after Nvidia-375!!
If you not forced to upgrade to 9.0, then WAIT! up to 3 Month! and checkout Bug Lists.
I tried Nvidia Installer Files too (*.run) they don’t work too, seems a API of the Kernel is changed
Nouveau Version on Debian Stretch is able to run Kodi (glx)! seen on Geforce 8400GS 256MB
On Onboard Geforce Chips like older Laptops HOLD Debian 8.0
If you use a Amazon Kindle Fire 2015 (45$) Generation „Ford“ or other Android Tablets,Smartphones you must know some MAJOR Informations about the Firmware Handling.
If you were asked by the Fire OS or Android to „Upgrade“ the Firmware OS, DON’T PUSH YES it without READING DETAILS! I prefer ALWAYS NO FIRST!
Use ALWAYS a SDCARD to hold the MAJOR Data of your Tablet, cause if bricked or damaged you can’t pull off the DATA!!!
Android Firmware Images INCLUDE not only the OS, it includes DRIVERS, and the MAJOR BOOTLOADER!! Cause Android Devices use no real BIOS!!
If you Upgrade, you can RUN into BIG TROUBLE! Broken Drivers like no WIFI connect, freezing Screens on Boot, or BRICKS like the „BLACK SCREEN of DEATH“ which destory the Tablets cause you can’t reach the BOOTLOADER for RECOVERY MODE and SITELOAD the FIRMWARE again!
UPGRADES to bigger Version Releases like 5.1 to 5.3.X CAN’T be DOWNGRADED! Cause the DOWNGRADE don’t force overwrite correctly the BOOTLOADER, or leave the NEW BOOTLOADER untouched which can’t find the old KERNELS Names!
As MAJOR INFO you should know that the „adb shell tool“ is a DEVELOPER TOOL which doesn’t ASK anything to confirm, if the Firmware File is wrong or damaged! It flashes without any testing and any protection check! YOU have to KNOW what you ENTER!
You can’t reach anything, if the Tablet is BRICKED and you can’t reach the RESCUE MENU MODE! Cause NAND Chips need a connect from adb shell tool to USB then to EEPROM Chip!
If you use Ubuntu Desktop 16.10 you will run sometimes into freezes of the Desktop with a Default Setup.
Background: Theres a known Bug of the Deja-Dup Backup Service which is started by Cron. The Service take 100% Ram and 100% CPU usage. This did my PC with 16GB Ram too! Only HARD RESET helps to get back Control!
Purge the deja-dup service with:
$sudo apt purge deja-dup
Use instead the „rsync“ tool by command line with users crontab to Backup your User Homes to external or 2nd. Disk.
If you boot your PC on a Setup CD into „live“ mode after some time the Desktop Unity or Gnome starts. After successful testing the PC with the current Drivers and Kernel you can select „Install“ by pressing the icon left on the desktop. But here the Problem appear that you dont see any informations about bugs, crashes, or other major messages during the setup. Without this you are not able to find any errors later, or you cant tell a supporter what happend!
Always open a gnome-terminal as first step instead of pressing the installer icon!
move the gnome-terminal window on lower screen area to 100% width!!!
$sudo tail -f /var/log/syslog # some Linux uses /var/log/messages!
Now press Installer icon! and view Log in realtime
Hope this help to fix bugs like freezes of often seen SSD Errors I/O…
If you setup a Laptop with 15.XX and a luks encrypted SSD, you did set on older OS „tmpfs“ for /tmp. Now under „systemd“ the the boot hangs cause systemd „automount“ tmpfs to /tmp by default!!! If you enter tmpfs into fstab like on ubuntu 14.10, the OS boots into the „RECOVERY RESCUE MODE“
Here some details, from a forum post:
Disable automatic mount
Under systemd, /tmp may be automatically mounted as a tmpfs even though you have no entry for that in your /etc/fstab.
To disable the automatic mount, run:
# systemctl mask tmp.mount
Files will no longer be stored in a tmpfs, but your block device instead. The /tmp contents will now be preserved between reboots, which you might not want. To regain the previous behavior and clean the /tmp folder automatically when restarting your machine, consider using tmpfiles.d:
# see tmpfiles.d
# always enable /tmp folder cleaning
D! /tmp 1777 root root 0
# remove files in /var/tmp older than 10 days
D /var/tmp 1777 root root 10d
# namespace mountpoints (PrivateTmp=yes) are excluded from removal