Linux: Systemd ignore console-setup settings

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 -
crontab -e

  • 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“

 

Nvidia: Legacy Driver Debian 9.0 Stretch Kernel 4.9 Bug Interface

Current is a UNFIXED Bug on Debian 9.0 Stretch which makes impossible to easy install DKMS Nvidia-Legacy Drivers 304/340 for older Geforce Cards

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852152

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
$sudo update-grub
$sudo reboot

Remarks:

  • 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

Android: Upgrade Downgrade Kindle Fire Firmware Bug

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.

Amazon Kindle Fire 2015 Ford

  • 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!
  • To be sure prevent the Tablet from reaching the Amazon Update Servers by blocking the Domains on a Blacklist at the Home Router
  • A pulling out the Battery, does often NOT HELP on Tablet! You often don’t need to open the Case for this try!
  • If you can, buy Tablets, without Bloatware, but with SDCARD Connector, with a more basic Android called „Stock“ OS (have seen this on cheap No Name China Tablets)
  • Check the Internet Media for Hardware Infos which Hardware allow easy root access, some Manufacter allow this like Fairphones with special opened OS.
  • For Kids usage purge the Amazon Account on the Tablet, this prevent unallowed Setups
  • Android Firmware EEPROM Chips mostly glued onto the Mainboard, if the Firmware writing fails the device is a toaster.. no normal User can plug out the EEPROM Chips to flash them outside!
  • Opened Tablets can be seen here 

.. never change a running System.. if you MUST not..

Remarks:

  • If someone find a Solution to flash the NAND chips without the Recovery Mode then mail me please!
  • This Firmware Handling is the SAME on all Android or Embedded Devices like Openmips, Openwrt Routers ..

Ubuntu: Deja-Dup Backup Freeze Desktop

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!

Solution:

  • 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.

This should fix the problem.

Ubuntu Debian: Installer Messages during Installation Realtime Debug Installer Mode

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!

Workaround (#comments!):

  • 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!!!
  • Enter there:

$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…

Ubuntu Vivid Debian: Kernel I/O Errors SSD SATA NVIDIA Chipsets

If you use a PC with a SSD Drive and a Motherboard which uses NVIDIA chipsets you may see Errors on boot

Command „dmesg“ Output like..

Buffer I/O error on device sdc, logical block 41
ata5: EH complete
ata5: EH in SWNCQ mode,QC:qc_active 0x1 sactive 0x1
ata5: SWNCQ:qc_active 0x1 defer_bits 0x0 last_issue_tag 0x0
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata5: ATA_REG 0x41 ERR_REG 0x84
ata5: tag : dhfis dmafis sdbfis sactive
ata5: tag 0x0: 1 1 0 1 
ata5.00: exception Emask 0x1 SAct 0x1 SErr 0x300000 action 0x6 frozen
ata5.00: Ata error. fis:0x21
ata5.00: cmd 60/08:00:07:04:00/00:00:00:00:00/40 tag 0 ncq 4096 in
         res 41/84:00:07:04:00/84:00:00:00:00/40 Emask 0x10 (ATA bus error)
ata5: hard resetting link
ata5: nv: skipping hardreset on occupied port
ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata5.00: configured for UDMA/133
sd 4:0:0:0: [sdc] 
Result: hostbyte=0x00 driverbyte=0x08
sd 4:0:0:0: [sdc] 
Sense Key : 0xb [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
        00 00 04 07
sd 4:0:0:0: [sdc] 
ASC=0x47 ASCQ=0x0...

This is a bug by the NVIDIA Manufacterer NOT by LINUX!

The Problem is that the hardware command „swncq“ (DMA-64bit) is set to on by the „default“ Kernels now, but older nvidia chips don’t support it! Only DMA-32bit

sata cable 600 with clip
sata cable 600 with clip

Info found here swnq libsata nvidia kernel (external Link)

Workaround on Gnome Terminal or Console:

  • $sudo echo ‚options sata_nv swncq=0‘ >> /etc/modprobe.d/sata_nv.conf
  • $sudo update-initramfs -u -k all
  • reboot and test with „dmesg“ command on Terminal! there should be NO Error now!
  • If the Problem still exists, then change SATA Cables to SATA-300/600 (II/III) „with Metal Clip on Connectors“ take „shortest length“
  • May be possible that this bug touches other OS like Windows too

 

Ubuntu Vivid: Systemd boot OS into rescue mode with tmpfs

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:
/etc/tmpfiles.d/tmp.conf

# 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
x /tmp/systemd-private-*
x /var/tmp/systemd-private-*
X /tmp/systemd-private-*/tmp
X /var/tmp/systemd-private-*/tmp

Ubuntu 13.04 Bug: gvfs smb Nautilus freeze hangs on copy files from a Samba Share

gvfs-smb Bug #1075923 (seen on Debian+Ubuntu+Centos..more..)

Workaround:

downgrade gvfs-* to Version 1.12 of 12.10 with:

  • add /etc/apt/sources.list

deb http://de.archive.ubuntu.com/ubuntu precise main
deb-src http://de.archive.ubuntu.com/ubuntu precise main

  • run: sudo apt-get update
  • install synaptic: sudo apt-get install synaptic
  • run synaptic: sudo synaptic
  • remove all gvfs-* nautilus with synaptics (REALLY CHECK ALL! see „dpkg -l | grep gvfs“)
  • search gvfs-*, select, press CTRL+E (Force Menu)
  • select: gvfs-* Versions 1.12
  • install by run install button
  • search and install nautilus again..

Voila…Test Nautilus copy 1TB Files without freeze