indicium - User contributions [en]

Proxmox

2026-01-09T13:12:50Z

Steffe: Created page with "To fix various things (such as enabling the free repository and disable the nag screen): bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/misc/post-pve-install.sh)""

To fix various things (such as enabling the free repository and disable the nag screen):
bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/misc/post-pve-install.sh)"

Main Page

2026-01-09T13:12:12Z

Steffe:

= Indicium - The source of information =

[[Linux kernel]]

[[Linux]]

[[FreeBSD]]

[[Git]]

[[Programming]]

[[Learn programming]]

[[Web]]

[[Pinball]]

[[FreeNAS]]

[[Video Encoding]]

[[Kodi]]

[[Cars]]

[[VmWare]]

[[Windows]]

[[Home Automation]]

[[Raspberry Pi]]

[[Backup]]

[[Boats]]

[[BIOS]]

[[TCPdump]]

[[Printers]]

[[Proxmox]]

Home Assistant

2025-12-16T20:53:58Z

Steffe:

How to officially get SonOff with default firmware into HA: https://sonoff.tech/product-review/tutorial/how-to-add-your-sonoff-devices-on-home-assistant/, https://github.com/CoolKit-Technologies/ha-addon

How to unofficially get SonOff with default firmware into HA via HACS: https://github.com/AlexxIT/SonoffLAN

How to unofficially get SonOff with default firmware into HA via HACS (seems obsolete): https://github.com/peterbuga/HASS-sonoff-ewelink

How to get Tellstick ZNet loaded with "local plugin" to expose all services via MQTT to Home Assistant: https://github.com/quazzie/tellstick-plugin-mqtt-hass

Printers

2025-06-22T13:41:16Z

Steffe:

== Canon TS6351 ==
=== Unable to scan, error code ''Code5,157,69'' ===
I had this printer connected to my Wifi network, and printing was seldom a problem, but when I tried to scan using "IJ Scan Utility" I often got errors such as "Code5,157,69", "Code5,157,200", "Code2,157,50" etc. I tried everything such as reinstalling latest drivers, I allowed the applications through the firewall etc, but it would simply not work. I had no issues reaching the printers IP from a web browser to get information on ink levels etc.

The error does indicate that the Wifi connection is bad. I launched my Unifi center to try and fix this. I realized that the printer was connected to the Wifi access point farthest away from the printer itself which was also the weakest one. I rebooted the printer but it still only connected to the same access point. I tried setting the Unifi center to lock the access point to another one, but then the printer failed to connect to Wifi altogether. I re-eanbled the printer to connect to any access point again in Unifi center and started looking at the printer itself.

I realized that when I choose to connect manually to Wifi, and I selected by SSID, the printer stated "There are multiple access points for this Wifi, do you want to connect to all or only a single one?". I choose to connect to "All" and then the printer AGAIN connected to the weakest access point. There must be some kind of issue in the Wifi roaming implementation of this printer. The solution was to manually check with my phone (using Wifi Analyzer) which access point that had the strongest signal at the location where the printer was, noted down the MAC of that access point, and in the printer Wifi setup, I choose to only connect to one single access point, and choose the MAC for the strongest one. Tada, everything works and I am able to scan without issues again!

Printers

2025-06-22T13:30:44Z

Steffe:

== Canon TS6351 ==
=== Unable to scan, error code ''Code5,157,69'' ===
I had this printer connected to my Wifi network, and printing was seldom a problem, but when I tried to scan using "IJ Scan Utility" I often got errors such as "Code5,157,69", "Code5,157,200" etc. I tried everything such as reinstalling latest drivers, I allowed the applications through the firewall etc, but it would simply not work. I had no issues reaching the printers IP from a web browser to get information on ink levels etc.

The error does indicate that the Wifi connection is bad. I launched my Unifi center to try and fix this. I realized that the printer was connected to the Wifi access point farthest away from the printer itself which was also the weakest one. I rebooted the printer but it still only connected to the same access point. I tried setting the Unifi center to lock the access point to another one, but then the printer failed to connect to Wifi altogether. I re-eanbled the printer to connect to any access point again in Unifi center and started looking at the printer itself.

I realized that when I choose to connect manually to Wifi, and I selected by SSID, the printer stated "There are multiple access points for this Wifi, do you want to connect to all or only a single one?". I choose to connect to "All" and then the printer AGAIN connected to the weakest access point. There must be some kind of issue in the Wifi roaming implementation of this printer. The solution was to manually check with my phone (using Wifi Analyzer) which access point that had the strongest signal at the location where the printer was, noted down the MAC of that access point, and in the printer Wifi setup, I choose to only connect to one single access point, and choose the MAC for the strongest one. Tada, everything works and I am able to scan without issues again!

Printers

2025-06-22T13:30:07Z

Steffe: /* Unable to scan, error code _Code5,157,69_ */

== Canon TS6351 ==
=== Unable to scan, error code 'Code5,157,69' ===
I had this printer connected to my Wifi network, and printing was seldom a problem, but when I tried to scan using "IJ Scan Utility" I often got errors such as "Code5,157,69", "Code5,157,200" etc. I tried everything such as reinstalling latest drivers, I allowed the applications through the firewall etc, but it would simply not work. I had no issues reaching the printers IP from a web browser to get information on ink levels etc.

The error does indicate that the Wifi connection is bad. I launched my Unifi center to try and fix this. I realized that the printer was connected to the Wifi access point farthest away from the printer itself which was also the weakest one. I rebooted the printer but it still only connected to the same access point. I tried setting the Unifi center to lock the access point to another one, but then the printer failed to connect to Wifi altogether. I re-eanbled the printer to connect to any access point again in Unifi center and started looking at the printer itself.

I realized that when I choose to connect manually to Wifi, and I selected by SSID, the printer stated "There are multiple access points for this Wifi, do you want to connect to all or only a single one?". I choose to connect to "All" and then the printer AGAIN connected to the weakest access point. There must be some kind of issue in the Wifi roaming implementation of this printer. The solution was to manually check with my phone (using Wifi Analyzer) which access point that had the strongest signal at the location where the printer was, noted down the MAC of that access point, and in the printer Wifi setup, I choose to only connect to one single access point, and choose the MAC for the strongest one. Tada, everything works and I am able to scan without issues again!

Printers

2025-06-22T13:29:57Z

Steffe:

== Canon TS6351 ==
=== Unable to scan, error code _Code5,157,69_ ===
I had this printer connected to my Wifi network, and printing was seldom a problem, but when I tried to scan using "IJ Scan Utility" I often got errors such as "Code5,157,69", "Code5,157,200" etc. I tried everything such as reinstalling latest drivers, I allowed the applications through the firewall etc, but it would simply not work. I had no issues reaching the printers IP from a web browser to get information on ink levels etc.

The error does indicate that the Wifi connection is bad. I launched my Unifi center to try and fix this. I realized that the printer was connected to the Wifi access point farthest away from the printer itself which was also the weakest one. I rebooted the printer but it still only connected to the same access point. I tried setting the Unifi center to lock the access point to another one, but then the printer failed to connect to Wifi altogether. I re-eanbled the printer to connect to any access point again in Unifi center and started looking at the printer itself.

I realized that when I choose to connect manually to Wifi, and I selected by SSID, the printer stated "There are multiple access points for this Wifi, do you want to connect to all or only a single one?". I choose to connect to "All" and then the printer AGAIN connected to the weakest access point. There must be some kind of issue in the Wifi roaming implementation of this printer. The solution was to manually check with my phone (using Wifi Analyzer) which access point that had the strongest signal at the location where the printer was, noted down the MAC of that access point, and in the printer Wifi setup, I choose to only connect to one single access point, and choose the MAC for the strongest one. Tada, everything works and I am able to scan without issues again!

Printers

2025-06-22T13:29:43Z

Steffe:

== Canon TS6351 ==
=== Unable to scan, error code ode5,157,69 ===
I had this printer connected to my Wifi network, and printing was seldom a problem, but when I tried to scan using "IJ Scan Utility" I often got errors such as "Code5,157,69", "Code5,157,200" etc. I tried everything such as reinstalling latest drivers, I allowed the applications through the firewall etc, but it would simply not work. I had no issues reaching the printers IP from a web browser to get information on ink levels etc.

The error does indicate that the Wifi connection is bad. I launched my Unifi center to try and fix this. I realized that the printer was connected to the Wifi access point farthest away from the printer itself which was also the weakest one. I rebooted the printer but it still only connected to the same access point. I tried setting the Unifi center to lock the access point to another one, but then the printer failed to connect to Wifi altogether. I re-eanbled the printer to connect to any access point again in Unifi center and started looking at the printer itself.

I realized that when I choose to connect manually to Wifi, and I selected by SSID, the printer stated "There are multiple access points for this Wifi, do you want to connect to all or only a single one?". I choose to connect to "All" and then the printer AGAIN connected to the weakest access point. There must be some kind of issue in the Wifi roaming implementation of this printer. The solution was to manually check with my phone (using Wifi Analyzer) which access point that had the strongest signal at the location where the printer was, noted down the MAC of that access point, and in the printer Wifi setup, I choose to only connect to one single access point, and choose the MAC for the strongest one. Tada, everything works and I am able to scan without issues again!

Printers

2025-06-22T13:28:29Z

Steffe: Created page with "Canon TS6351 I had this printer connected to my Wifi network, and printing was seldom a problem, but when I tried to scan using "IJ Scan Utility" I often got errors such as "Code5,157,69", "Code5,157,200" etc. I tried everything such as reinstalling latest drivers, I allowed the applications through the firewall etc, but it would simply not work. I had no issues reaching the printers IP from a web browser to get information on ink levels etc. The error does indicate tha..."

Canon TS6351
I had this printer connected to my Wifi network, and printing was seldom a problem, but when I tried to scan using "IJ Scan Utility" I often got errors such as "Code5,157,69", "Code5,157,200" etc. I tried everything such as reinstalling latest drivers, I allowed the applications through the firewall etc, but it would simply not work. I had no issues reaching the printers IP from a web browser to get information on ink levels etc.

The error does indicate that the Wifi connection is bad. I launched my Unifi center to try and fix this. I realized that the printer was connected to the Wifi access point farthest away from the printer itself which was also the weakest one. I rebooted the printer but it still only connected to the same access point. I tried setting the Unifi center to lock the access point to another one, but then the printer failed to connect to Wifi altogether. I re-eanbled the printer to connect to any access point again in Unifi center and started looking at the printer itself.

I realized that when I choose to connect manually to Wifi, and I selected by SSID, the printer stated "There are multiple access points for this Wifi, do you want to connect to all or only a single one?". I choose to connect to "All" and then the printer AGAIN connected to the weakest access point. There must be some kind of issue in the Wifi roaming implementation of this printer. The solution was to manually check with my phone (using Wifi Analyzer) which access point that had the strongest signal at the location where the printer was, noted down the MAC of that access point, and in the printer Wifi setup, I choose to only connect to one single access point, and choose the MAC for the strongest one. Tada, everything works and I am able to scan without issues again!

Main Page

2025-06-22T13:16:57Z

Steffe:

Windows

2025-05-08T06:08:29Z

Steffe:

= Energy management =

== Why computer was woken from sleep ==
To check why computer was woken from suspend:
powercfg /lastwake
to get more details:
powercfg /systempowerreport

== To disable Windows Update waking up the computer ==
Run as Administrator:
gpedit.msc

Then go to:
Computer Configuration / Administrative Templates / Windows Components / Windows Update / Enabling Windows Update Power Management to automatically wake up the system to install scheduled updates
and set it to "Disabled".

For swedish Windows:
Datorkonfiguration / Administrativa mallar / Windows-komponenter / Windows Update / Aktivera automatisk väckning via Energisparfunktioner för installation av schemalagda uppdateringar
and set it to "Inaktiverad".

== To disable hibernation ==

powercfg.exe /h off

== To uninstall a specific driver ==

In a elevated command prompt:
dism /online /get-drivers /format:table > c:\drivers.txt
Look through the drivers.txt file, and then you can do things like:
pnputil.exe /d oem111.inf

== To enable DHCP ==

Install a simple DHCP server like: https://www.hanewin.net/dhcp-e.htm

== To install Windows 11 on an unsupported CPU ==

Don't know if all of these steps are required, but they worked!

* Download a Windows 11 ISO file.
* Use [https://rufus.ie Rufus] to write the ISO to a USB drive. After hitting "Start", select the tick box to skip TPM/CPU verification.
* In the running Windows x system, add the following register keys:
HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig\BypassCPUCheck=1
HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig\BypassTPMCheck=1
* If you want to install Windows 11 from scratch, boot from the USB drive.
* If you want to upgrade, run setup.exe from the USB drive in the running system.

FreeBSD

2025-04-16T20:41:08Z

Steffe: Created page with "== Enlarging disk space == For full reference: https://docs.freebsd.org/en/books/handbook/disks/#disks-growing Shut down your VM, make a backup of it and then resize the hard disk drive. Then boot up FreeBSD again and do: gpart show It will show one of your partitions as CORRUPT. Fix it with something like: gpart recover vtbd0 gpart show It should now be OK. Note the index number of the partition you want to resize, then do something like: gpart resize -i 2 vtbd0 N..."

== Enlarging disk space ==

For full reference: https://docs.freebsd.org/en/books/handbook/disks/#disks-growing

Shut down your VM, make a backup of it and then resize the hard disk drive. Then boot up FreeBSD again and do:
gpart show
It will show one of your partitions as CORRUPT. Fix it with something like:
gpart recover vtbd0
gpart show
It should now be OK. Note the index number of the partition you want to resize, then do something like:
gpart resize -i 2 vtbd0
Not specifying any size implies growing the partition to fit the physical size.

Now, for the final step to resize the file system, make sure you have a backup in place, check what the partition device name is and then do something like:
sysctl kern.geom.debugflags=16
growfs /dev/vtbd0p2
The first command disables some safety features. This is required to resize a mounted file system "on the fly". Now reboot your system and all should hopefully be OK!

Main Page

2025-04-16T20:32:03Z

Steffe:

TCPdump

2025-02-18T11:55:38Z

Steffe: Created page with "== Basic capture == Typical usage to capture network traffic going to a specific host: sudo tcpdump host xxx.xxx.xxx.xxx -w output.pcap == TLS capture == In case the traffic is encrypted using TLS or similar, you may be able to use the SSLKEYLOGFILE environment variable when running your client (or server) binary: SSLKEYLOGFILE=sslkeylogfile.log ./testapplication.py If this produces a sslkeylogfile.log file, you can use that to decrypt the TLS traffic. Open wireshark..."

== Basic capture ==
Typical usage to capture network traffic going to a specific host:
sudo tcpdump host xxx.xxx.xxx.xxx -w output.pcap

== TLS capture ==
In case the traffic is encrypted using TLS or similar, you may be able to use the SSLKEYLOGFILE environment variable when running your client (or server) binary:
SSLKEYLOGFILE=sslkeylogfile.log ./testapplication.py
If this produces a sslkeylogfile.log file, you can use that to decrypt the TLS traffic. Open wireshark and go to Edit - Preferences - Protocol - TLS - (Pre)-Master-Secret log filename and specify your sslkeylogfile.log file. Then open your package dump and it will be decrypted.

Main Page

2025-02-18T11:39:20Z

Steffe:

= Indicium - The source of information =

[[Linux kernel]]

[[Linux]]

[[Git]]

[[Programming]]

[[Learn programming]]

[[Web]]

[[Pinball]]

[[FreeNAS]]

[[Video Encoding]]

[[Kodi]]

[[Cars]]

[[VmWare]]

[[Windows]]

[[Home Automation]]

[[Raspberry Pi]]

[[Backup]]

[[Boats]]

[[BIOS]]

[[TCPdump]]

Kodi

2025-01-02T13:22:12Z

Steffe:

'''To get both MCE keyboard and MCE remote to work simultaneously:'''

ir-keytable -p mce_kbd -p rc-6

More info here: https://forum.libreelec.tv/thread/12348-mce-keyboard-input-not-detected/

'''To make sure the BACK button stops the video instead of putting it in the background:'''

Add-ons -> Install from Repository -> Kodi Add-on Repository -> Program add-ons -> Keymap Editor -> Install ->Keymap Editor -> Run -> Edit -> Fullscreen Video -> Playback -> Stop - browser_back -> Edit key ->Press the BACK button on your remote

Hit back until you see the SAVE option.

Python

2024-10-14T09:30:35Z

Steffe:

== Threading ==

http://www.tutorialspoint.com/python/python_multithreading.htm

Note however that threading in python is limited due to the GIL. To achieve "true" threading, use the "[https://docs.python.org/2/library/multiprocessing.html multiprocess]" library (which in fact spawns different processes and uses IPC mechanism for communication etc): https://www.quantstart.com/articles/Parallelising-Python-with-Threading-and-Multiprocessing

== Debugging ==

Python can be debugged using rpdb2: https://pypi.org/project/rpdb2/

Since it is not distributed with any major distributions, you have to install it using pip, preferably in a virtual environment:

mkdir ~/pyenv
mkdir ~/pyenv/rpdb2
python -m venv pyenv/rpdb2/
~/pyenv/rpdb2/bin/pip install rpdb2

Now you need to hook into rpdb2 from the python program that you want to debug. Add this line to the python code:

import rpdb2; rpdb2.start_embedded_debugger("pass")

The string "pass" is the password to connect from the debugger. Now start your application (using the same virtual environment so that you can access the rpdb2 library):

~/pyenv/rpdb2/bin/python <yourapplication.py>

It will halt at startup and wait for debugger to connect. In another terminal, launch the debugger:

~/pyenv/rpdb2/bin/python -m rpdb2

Now issue the following commands to attach to your process and run it:

password pass
attach
go

Now you can issue command "help" to get more info. Commands such as "thread" and "stack" might be helpful.

== Tkinter and simple GUI programming ==

#!/usr/bin/env python

from Tkinter import *

def drawframe():
c.delete("all")
c.create_rectangle(0, 0, 150, 75 + c.steffe_i, fill="blue")
c.steffe_i += 1
root.after(10, drawframe)

def mouseclick(event):
print "Mouse click at", event.x, event.y

def keyclick(event):
print "Key click", event.keysym

root = Tk()
c = Canvas(root, width=640, height=480)
c.pack()

root.bind("<Key>", keyclick)
root.bind("<Button-1>", mouseclick)

c.config(borderwidth = 10)
c.config(background = "grey15")
c.steffe_i = 0

root.after(10, drawframe)
mainloop()

== One function proper hexdump ==
The following function will convert a byte array to a format like this:

00000000 69 6d 70 6f 72 74 20 73 74 72 69 6e 67 0d 0a 0d |import.string... |
00000010 0a 64 65 66 20 68 65 78 64 75 6d 70 28 63 76 65 |.def.hexdump(cve |
00000020 63 74 6f 72 2c 20 70 72 65 66 69 78 20 3d 20 22 |ctor,.prefix.=." |
00000030 22 29 3a 0d 0a 09 69 20 3d 20 30 0d 0a 09 73 20 |"):...i.=.0...s. |
00000040 3d 20 22 22 0d 0a 09 61 63 20 3d 20 5b 5d 0d 0a |=.""...ac.=.[].. |
00000050 09 66 6f 72 20 63 20 69 6e 20 63 76 65 63 74 6f |.for.c.in.cvecto |
00000060 72 3a 0d 0a 09 09 69 66 20 6e 6f 74 20 69 20 25 |r:....if.not.i.% |
00000070 20 31 36 3a 0d 0a 09 09 09 69 66 20 69 20 21 3d |.16:.....if.i.!= |

The function is not designed to be memory efficient, fast or good looking, just simple to drop in and get some hex output.

import string

def hexdump(cvector, prefix = ""):
i = 0
s = ""
ac = []
for c in cvector:
if not i % 16:
if i != 0:
s += " |"
for cs in ac:
css = chr(cs)
s += css if css in string.printable and not css in string.whitespace else "."
s += " |"
ac = []
s += "\n%s%s " % (prefix, "%08x " % i)
elif not i % 8:
s += " "
s += "%02x " % c
ac.append(c)
i += 1
if len(ac) > 0:
left = 16 - len(ac)
for k in range(left):
s += " "
if left >= 8:
s += " "
s += " |"
for cs in ac:
css = chr(cs)
s += css if css in string.printable and not css in string.whitespace else "."
for k in range(left):
s += " "
s += " |"

return s

with open("hexdump.py", "rb") as f:
data = f.read()
print(hexdump(data))

Windows

2024-10-11T12:45:00Z

Steffe:

Linux

2024-08-06T12:43:51Z

Steffe: /* Set up public key SSH authentication */

== Debugging Linux applications ==
=== LDD ===
Linux LDD is just a wrapper for:
LD_TRACE_LOADED_OBJECTS=1 <cmd>

=== Core dumps ===
To check core dump handler:
cat /proc/sys/kernel/core_pattern
|/usr/sbin/coredump-handler %h_%t_%p.core

=== Valgrind ===
valgrind --trace-children=yes --leak-check=full --show-leak-kinds=all <binary>

== Dual boot with Windows ==

=== Installation ===

First install Windows as usual, then boot (in UEFI mode) from Debian netinst usb stick and install Debian. Install grub on your primary disk drive.

=== Repair when computer only boots into Windows ===

Download the Debian Live standard ISO from here: https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/

Use Rufus to write it to a bootable USB stick: https://rufus.ie

In Rufus, select your USB drive and the downloaded Debian ISO.

Make sure you select ''Partition schema'' as ''GPT'' and ''Target system'' as ''UEFI (non CSM)''.
Hit "Start" and when prompted choose to write the image in ''DD'' mode!

Now insert the USB stick in your broken computer and boot it while hitting a magic key (such as F12) to enter BIOS boot menu. Select to boot your USB stick in ''UEFI mode''.

Once Debian Live has started up, follow the instructions here: https://wiki.debian.org/GrubEFIReinstall#Using_A_Live_CD.2FUSB_To_Fix_Your_Current_System

In short, first you need to figure out your target system root and EFI partitions:

sudo fdisk -l
...
Device Start End Sectors Size Type
'''/dev/nvme0n1p1 2048 1394687 1392640 680M EFI System'''
/dev/nvme0n1p2 1394688 1656831 262144 128M Microsoft reserved
/dev/nvme0n1p3 1656832 1764220927 1762564096 840.5G Microsoft basic data
/dev/nvme0n1p4 1969020928 1971048447 2027520 990M Windows recovery environment
/dev/nvme0n1p5 1971048448 1997713407 26664960 12.7G Windows recovery environment
/dev/nvme0n1p6 1997715456 2000408575 2693120 1.3G Windows recovery environment
'''/dev/nvme0n1p7 1764220928 1936101375 171880448 82G Linux filesystem'''
/dev/nvme0n1p8 1936101376 1969020927 32919552 15.7G Linux swap

So in this case our EFI partition is ''/dev/nvme0n1p1'' and our rootfs partition is ''/dev/nvme0n1p7''.

Then do something like:
sudo mount /dev/nvme0n1p7 /mnt/
sudo mount /dev/nvme0n1p1 /mnt/boot/efi
for i in /dev /dev/pts /proc /sys /sys/firmware/efi/efivars /run; do sudo mount -B $i /mnt$i; done
sudo chroot /mnt
sudo grub-install /dev/nvme0n1
sudo update-grub

=== Repair when computer only boots into Linux ===

Most probably this is due to that ''os-prober'' was not run during your last ''update-grub'' session.

In Linux, edit the file '''/etc/default/grub''' and add the following line:
GRUB_DISABLE_OS_PROBER=false

Also make sure you have the os-prober command installed:
sudo apt install os-prober
sudo os-prober

Then run:
sudo update-grub

=== Configure grub to always boot into your last selected OS ===

In Linux, edit the file '''/etc/default/grub''' and add the following lines:
GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true

== Configuring Linux ==

=== Users ===
Add user stefan to group sudo:
sudo adduser stefan sudo

=== Change console language to english ===
sudo dpkg-reconfigure locales
Then select en_US.UTF-8 (plus your local language), and then on next screen set the default language.

=== Secure Boot ===

If you want to run Linux, but you also dual boot into Windows and need to have your BIOS set up to boot in Secure Boot (for instance if you play Valorant in Windows), then you have two choices.

# Boot Windows in secure mode but Linux in insecure mode.
# Boot both Windows and Linux in secure mode.

==== Option 1 ====

To get the first option working, you need to install Fedora/Nobara with UEFI enabled, but secure boot disabled in BIOS. If you at this point enable secure boot, Linux will not boot (complain about shim error).

Boot up with secure boot disabled and do:
sudo mokutil --disable-validation
Follow the instructions and then reboot your PC and choose to "Change Secure boot state" as described here: https://wiki.ubuntu.com/UEFI/SecureBoot/DKMS

If you do this, you can install GRUB2 and enable Secure Boot in your BIOS again. If you now boot into GRUB2, you can select to boot Windows (which will then properly boot up in Secure Mode) or you can choose to boot Linux which will then boot up in insecure mode.

==== Option 2 ====

If you want to have also Linux booting up in secure mode, you can do that as well, but it requires a bit more work. There is a good guide here: https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface/Secure_Boot#PreLoader

Basically you need to:

1 Create your own MOK key
openssl req -newkey rsa:4096 -nodes -keyout mok.key -new -x509 -sha256 -days 3650 -subj "/CN=my Machine Owner Key/" -out mok.crt
openssl x509 -outform DER -in mok.crt -out mok.cer
2 Sign the vmlinuz file in your /boot/ folder with this key
sbsign --key mok.key --cert mok.crt --output /boot/vmlinuz-linux /boot/vmlinuz-linux
3 Enroll your key into your BIOS with mokutil
mokutil --import mok.cer

Then Linux will boot up fine in Secure Mode. You will however have 2 issues:

* Whenever a new kernel is installed on your system, you need to sign it with your own MOK key, otherwise it will not boot.
* You can not install third party drivers such as the Nvidia graphics drivers unless you sign also them with your own MOK key.

=== Graphics drivers ===
==== Disable Nvidia drivers and enable Intel embedded HD graphics driver ====
sudo apt-get purge nvidia-*
dpkg --list | grep nvidia
Make sure the list of nvidia packages is empty
sudo apt-get install --reinstall xserver-xorg-video-intel libgl1-mesa-glx libgl1-mesa-dri mesa-utils xserver-xorg-core
sudo dpkg-reconfigure xserver-xorg
sudo update-alternatives --remove gl_conf /usr/lib/nvidia-current/ld.so.conf
reboot
==== Disable Nvidia drivers and enable nouveau drivers ====
sudo apt-get purge nvidia-*
dpkg --list | grep nvidia
Make sure the list of nvidia packages is empty
sudo apt-get install --reinstall xserver-xorg-video-nouveau
==== Disable nouveau drivers and enable Nvidia drivers ====
'''Option 1''', using package manager:
sudo apt-get install --reinstall nvidia-driver
or if your graphics card is not supported by the latest drivers (you can install the nvidia-detect package and run it to get this information):
sudo apt-get install --reinstall nvidia-legacy-390xx-driver

'''Option 2''', using latest official NVidia driver:
* Go to [http://www.geforce.com] and download the latest Linux driver for your system.
* Switch to console mode (Ctrl+Alt+F1), kill any Xorg process (or mask/stop them with systemctl if you run systemd)
* Run the NVidia installer as root
systemctl mask gdm
systemctl stop gdm
killall Xorg
sudo ./NVIDIA-<driver-version-name>.run

==== Display configuration set in nvidia-settings is not retained after boot ====
This is a conflict between nvidia-settings and Debians internal settings application.
* Remove ~/.config/monitors.xml (this is Debians settings)
* Reboot
* Set everything up the way you want with nvidia-settings
* Go to Settings - Display
* Do some minor change that brings up the "Apply" button and press it
* Current settings are now saved to ~/.config/monitors.xml and will be used during next boot.

==== Display configuration for gdm3 ====
After doing the steps above, do:
sudo cp /home/stefan/.config/monitors.xml /var/lib/gdm3/.config

=== Restart Gnome ===

Hit ALT+F2, then you get a "gnome run command" thingy. Enter "r" and hit enter!

=== Switch default compiler ===

(cc --version;c++ --version;gcc --version;g++ --version) | grep Debian
cc (Debian 6.1.1-11) 6.1.1 20160802
c++ (Debian 6.1.1-11) 6.1.1 20160802
gcc (Debian 6.1.1-11) 6.1.1 20160802
g++ (Debian 6.1.1-11) 6.1.1 20160802

sudo apt-get install gcc-4.9 g++-4.9

gcc-4.9 --version
gcc-4.9 (Debian 4.9.3-14) 4.9.3

g++-4.9 --version
g++-4.9 (Debian 4.9.3-14) 4.9.3

gcc-5 --version
gcc-5 (Debian 5.4.1-1) 5.4.1 20160803

g++-5 --version
g++-5 (Debian 5.4.1-1) 5.4.1 20160803

sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-5 10
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.9 20
sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-5 10
sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.9 20
sudo update-alternatives --install /usr/bin/cc cc /usr/bin/gcc 30
sudo update-alternatives --set cc /usr/bin/gcc
sudo update-alternatives --install /usr/bin/c++ c++ /usr/bin/g++ 30
sudo update-alternatives --set c++ /usr/bin/g++

(cc --version;c++ --version;gcc --version;g++ --version) | grep Debian
cc (Debian 4.9.3-14) 4.9.3
c++ (Debian 4.9.3-14) 4.9.3
gcc (Debian 4.9.3-14) 4.9.3
g++ (Debian 4.9.3-14) 4.9.3

To go back:
sudo update-alternatives --config gcc
sudo update-alternatives --config g++

=== Console is not filling the screen completely ===
This may be due to that the console thinks it is connected to a different display device than it actually is. This can be fixed by adding kernel command line parameters to disable that specific video mode.
ls /sys/class/drm
card0@ card0-DisplayPort-1@ card0-DisplayPort-2@ card0-DisplayPort-3@ card0-HDMI Type A-1@ card0-HDMI Type A-2@ card0-LVDS-1@ card0-SVIDEO-1@ card0-VGA-1@ controlD64@ version
Now check the different "modes" and "connected" and "enabled" nodes under each device to figure out which needs to be disabled. Then add to your kernel command line things such as
video=LVDS-1:d video=SVIDEO-1:d video=TV-1:d
More information: https://bbs.archlinux.org/viewtopic.php?id=94990

=== udev ===
==== udev rules ====
Some sample udev rules which might come handy:
KERNEL=="tty*", GROUP="dialout", MODE="0660"
SUBSYSTEM=="gpio", GROUP:="gpio", MODE:="0660"
SUBSYSTEMS=="usb", KERNEL=="ttyUSB*", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="XXXXXXXX", SYMLINK+="ftdiserial2usb"

Use %m for the device number in symlink names.

==== udev info ====
To query a device about its properties (which can be used in udev rules):

udevadm info --path=/sys/class/leds/example --query=all --attribute-walk
udevadm info --name /dev/sda
udevadm info -a /dev/sda

More info: https://linux.die.net/man/7/udev

==== udev debugging ====
Command to reload udev rules:
sudo udevadm control --reload-rules && sudo udevadm trigger

Command to test udev rules:
udevadm test --action=add /class/gpio

=== Screen ===

How to make the scrollback work in screen? Add the following to your .screenrc file:
termcapinfo xterm ti@:te@

=== LVM ===

==== How to extend your LVM disk ====
Investigate your current setup with:
lsblk

Then you can perform operations like these (which reduces size of live-root with 50GB and extends size of live-home with 50GB):
lvreduce -r -L -50G /dev/mapper/nobara_localhost--live-root
lvextend -r -L +50G /dev/mapper/nobara_localhost--live-home

== Linux performance ==
[http://www.brendangregg.com/ http://www.brendangregg.com/]

== Kernel ==
=== Update to newer kernel on Debian ===
Add the backports repository to apt (/etc/apt/sources.list or something similar). Add these as new lines, do not change the existing ones:
deb [arch=amd64] http://debian.lth.se/debian bookworm-backports main contrib non-free non-free-firmware
deb-src [arch=amd64] http://debian.lth.se/debian bookworm-backports main contrib non-free non-free-firmware
Then do:
sudo apt update
Then just install the latest linux-image-amd64, but since backports is lower prioritized, you need to specify that you want the backport version:
sudo apt install linux-image-amd64/bookworm-backports

If you then get messages about missing firmware (due to kernel being newer than linux-firmware-nonfree):
Possible missing firmware /lib/firmware/i915/mtl_gsc_1.bin for module i915
Possible missing firmware /lib/firmware/i915/dg2_huc_gsc.bin for module i915
Possible missing firmware /lib/firmware/i915/mtl_huc_gsc.bin for module i915
Possible missing firmware /lib/firmware/i915/mtl_guc_70.bin for module i915
you can manually:
* Download the missing firmwares from here: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/
* Copy them to /lib/firmware/
* Regenerate initramfs with: ''sudo update-initramfs -u''

=== Update to newer kernel on Ubuntu ===
Simply install the correct version of linux-generic-hwe:
sudo apt install linux-generic-hwe-20.04
or
sudo apt install linux-generic-hwe-22.04

= Clean out journalctl logs =
journalctl --flush --rotate --vacuum-time=30d

= Set up public key SSH authentication =
On your client PC which you want to connect from, run:
ssh-keygen
Accept all the defaults. Use a passphrase if you want to (not for automated setups).

Then send your key to the server for your account:
ssh-copy-id -i .ssh/id_rsa.pub 10.0.0.26

If you can not use ssh-copy-id (such as if adding a key for user root which can not log in using password), then simply cat they key from .ssh/id_rsa.pub on your client to the .ssh/authorized_keys file on your server.

Linux

2024-08-06T12:21:40Z

Steffe: /* Clean out journalctl logs */

Linux

2024-08-06T08:41:57Z

Steffe:

Linux

2024-08-06T08:30:24Z

Steffe: /* Update to newer kernel on Debian */

BIOS

2024-08-06T08:11:32Z

Steffe:

BIOS are generally a bit trickier to configure after the upgrade to DDR5.

= AMD EXPO and Context Memory Restore =

Once a newly installed computer boots up, expect it to stay black for ~1-2 minutes during boot while DDR is trained.

To avoid this, you can enable ''Memory Context Restore'' and ''DDR Power Down'' found here on the ASUS B650E-F:
* Advanced - Ai Tweaker - DRAM Timing Control - Memory Context Restore - Enabled
* Advanced - Ai Tweaker - DRAM Timing Control - Power Down Enable - Enabled
* Advanced - AMD CBS - UMC Common Options - DDR options - DDR memory features - Memory Context Restore - Enabled
* Advanced - AMD CBS - UMC Common Options - DDR options - DDR Controller Configuration - DDR Power Options - Power Down Enabled - Enabled
'''NOTE''' that you '''HAVE''' to change it in '''ALL''' places! I have no idea why ASUS have done it this way. When you save and exit, it will show only 2 changed settings (even though you have changed 4), but if you do not change it in ALL places, your computer WILL not run stable!

By enabling this, the computer will then do one training on the next reboot, and then reuse that data for upcoming boots, giving the same kind of boot behavior as DDR4 and below.

You can also enable AMD EXPO to automatically overclock your DDR based on settings stored in your DDR memories.

= No display =
Sometimes a Displayport connector for the monitor can not be used while configuring BIOS. This is the case on the ASUS B650E-F in conjunction with a RTX 3070 graphics card. You have to connect the HDMI to see the BIOS screen every time.

= Method for BIOS updating for ASUS Rog Strix B650E =
* Connect HDMI to monitor
* Disconnect Displayport to monitor
* Put BIOS CAP file on USB stick and reboot into bios (DEL after DDR5 training)
* Advanced - Tools - EZ Flasher, update BIOS
* After full update, hit F1 to enter BIOS, do a "Load Optimized Defaults" and reboot again
* Go into BIOS and change the following to clock up DDR speed from DDR-4800 to DDR-6000 and boot Windows in proper UEFI mode:
** Advanced - Ai Tweaker - Ai Overclock Tuner: EXPO I
** Advanced - Boot - Secure Boot - OS Type: Windows UEFI Mode
** Advanced - Boot - Secure Boot - Secure Boot Mode: Standard
* Save and reboot, verify that Windows boots and is stable. Verify DDR frequency is 3GHz (DDR-6000).
* Reboot again, hit DEL (after DDR training) to enter BIOS and change ('''MUST set ALL of them''', and they have to be set to ''Enabled'', not ''Auto''!):
** Advanced - Ai Tweaker - DRAM Timing Control - Memory Context Restore: Enabled
** Advanced - Ai Tweaker - DRAM Timing Control - Power Down Enable: Enabled
** Advanced - AMD CBS - UMC Common Options - DDR options - DDR memory features - Memory Context Restore: Enabled
** Advanced - AMD CBS - UMC Common Options - DDR options - DDR Controller Configuration - DDR Power Options - Power Down Enabled: Enabled
* Save and reboot (DDR training will happen one final time)
* Verify that Windows boots and is stable.
* Reboot, DDR training should now be much faster. Verify that Windows is stable. Verify DDR frequency is 3GHz (DDR-6000)
* Finally disconnect HDMI and reconnect Displayport.

BIOS

2024-08-06T08:09:09Z

Steffe:

BIOS are generally a bit trickier to configure after the upgrade to DDR5.

= Context Memory Restore =

Once a newly installed computer boots up, expect it to stay black for ~1-2 minutes during boot while DDR is trained.

To avoid this, you can enable ''Memory Context Restore'' and ''DDR Power Down'' found here on the ASUS B650E-F:
* Advanced - Ai Tweaker - DRAM Timing Control - Memory Context Restore - Enabled
* Advanced - Ai Tweaker - DRAM Timing Control - Power Down Enable - Enabled
* Advanced - AMD CBS - UMC Common Options - DDR options - DDR memory features - Memory Context Restore - Enabled
* Advanced - AMD CBS - UMC Common Options - DDR options - DDR Controller Configuration - DDR Power Options - Power Down Enabled - Enabled
'''NOTE''' that you '''HAVE''' to change it in '''ALL''' places! I have no idea why ASUS have done it this way. When you save and exit, it will show only 2 changed settings (even though you have changed 4), but if you do not change it in ALL places, your computer WILL not run stable!

By enabling this, the computer will then do one training on the next reboot, and then reuse that data for upcoming boots, giving the same kind of boot behavior as DDR4 and below.

= AMD EXPO =

This allows for auto overclocking according to your DDR5 memory. This may increase DDR training time.

Enabling both AMD EXPO and Context Memory Restore should work well, but sometimes it gives stability issues, and you have to refrain from using one of them.

For me, it worked fine with the 1807 BIOS, but not with the 2616 or 3014 BIOS.

= No display =
Sometimes the displayport can not be used while configuring BIOS. This is the case on the ASUS B650E-F in conjunction with a RTX 3070 graphics card. You have to connect the HDMI to see the BIOS screen every time.

= Method for BIOS updating for ASUS Rog Strix B650E =
* Connect HDMI to monitor
* Disconnect Displayport to monitor
* Put BIOS CAP file on USB stick and reboot into bios (DEL after DDR5 training)
* Advanced - Tools - EZ Flasher, update BIOS
* After full update, hit F1 to enter BIOS, do a "Load Optimized Defaults" and reboot again
* Go into BIOS and change the following to clock up DDR speed from DDR-4800 to DDR-6000 and boot Windows in proper UEFI mode:
** Advanced - Ai Tweaker - Ai Overclock Tuner: EXPO I
** Advanced - Boot - Secure Boot - OS Type: Windows UEFI Mode
** Advanced - Boot - Secure Boot - Secure Boot Mode: Standard
* Save and reboot, verify that Windows boots and is stable. Verify DDR frequency is 3GHz (DDR-6000).
* Reboot again, hit DEL (after DDR training) to enter BIOS and change ('''MUST set ALL of them''', and they have to be set to ''Enabled'', not ''Auto''!):
** Advanced - Ai Tweaker - DRAM Timing Control - Memory Context Restore: Enabled
** Advanced - Ai Tweaker - DRAM Timing Control - Power Down Enable: Enabled
** Advanced - AMD CBS - UMC Common Options - DDR options - DDR memory features - Memory Context Restore: Enabled
** Advanced - AMD CBS - UMC Common Options - DDR options - DDR Controller Configuration - DDR Power Options - Power Down Enabled: Enabled
* Save and reboot (DDR training will happen one final time)
* Verify that Windows boots and is stable.
* Reboot, DDR training should now be much faster. Verify that Windows is stable. Verify DDR frequency is 3GHz (DDR-6000)
* Finally disconnect HDMI and reconnect Displayport.

BIOS

2024-08-06T08:08:40Z

Steffe:

BIOS are generally a bit trickier to configure after the upgrade to DDR5.

= Context Memory Restore =

Once a newly installed computer boots up, expect it to stay black for ~1-2 minutes during boot while DDR is trained.

To avoid this, you can enable ''Memory Context Restore'' and ''DDR Power Down'' found here on the ASUS B650E-F:
* Advanced - Ai Tweaker - DRAM Timing Control - Memory Context Restore - Enabled
* Advanced - Ai Tweaker - DRAM Timing Control - Power Down Enable - Enabled
* Advanced - AMD CBS - UMC Common Options - DDR options - DDR memory features - Memory Context Restore - Enabled
* Advanced - AMD CBS - UMC Common Options - DDR options - DDR Controller Configuration - DDR Power Options - Power Down Enabled - Enabled
'''NOTE''' that you '''HAVE''' to change it in '''ALL''' places! I have no idea why ASUS have done it this way. When you save and exit, it will show only 2 changed settings (even though you have changed 4), but if you do not change it in ALL places, your computer WILL not run stable!

By enabling this, the computer will then do one training on the next reboot, and then reuse that data for upcoming boots, giving the same kind of boot behavior as DDR4 and below.

= AMD EXPO =

This allows for auto overclocking according to your DDR5 memory. This may increase DDR training time.

Enabling both AMD EXPO and Context Memory Restore should work well, but sometimes it gives stability issues, and you have to refrain from using one of them.

For me, it worked fine with the 1807 BIOS, but not with the 2616 or 3014 BIOS.

= No display =
Sometimes the displayport can not be used while configuring BIOS. This is the case on the ASUS B650E-F in conjunction with a RTX 3070 graphics card. You have to connect the HDMI to see the BIOS screen every time.

= Method for BIOS updating for ASUS Rog Strix B650E =
* Connect HDMI to monitor
* Disconnect Displayport to monitor
* Put BIOS CAP file on USB stick and reboot into bios (DEL after DDR5 training)
* Advanced - Tools - EZ Flasher, update BIOS
* After full update, hit F1 to enter BIOS, do a "Load Optimized Defaults" and reboot again
* Go into BIOS and change the following to clock up DDR speed from DDR-4800 to DDR-6000 and boot Windows in proper UEFI mode:
** Advanced - Ai Tweaker - Ai Overclock Tuner: EXPO I
** Advanced - Boot - Secure Boot - OS Type: Windows UEFI Mode
** Advanced - Boot - Secure Boot - Secure Boot Mode: Standard
* Save and reboot, verify that Windows boots and is stable. Verify DDR frequency is 3GHz (DDR-6000).
** Reboot again, hit DEL (after DDR training) to enter BIOS and change ('''MUST set ALL of them''', and they have to be set to ''Enabled'', not ''Auto''!):
*** Advanced - Ai Tweaker - DRAM Timing Control - Memory Context Restore: Enabled
*** Advanced - Ai Tweaker - DRAM Timing Control - Power Down Enable: Enabled
*** Advanced - AMD CBS - UMC Common Options - DDR options - DDR memory features - Memory Context Restore: Enabled
*** Advanced - AMD CBS - UMC Common Options - DDR options - DDR Controller Configuration - DDR Power Options - Power Down Enabled: Enabled
** Save and reboot (DDR training will happen one final time)
** Verify that Windows boots and is stable.
** Reboot, DDR training should now be much faster. Verify that Windows is stable. Verify DDR frequency is 3GHz (DDR-6000)
* Finally disconnect HDMI and reconnect Displayport.

Windows

2024-07-23T06:15:38Z

Steffe: /* Why computer was woken from sleep */

BIOS

2024-07-06T17:54:02Z

Steffe:

BIOS

2024-07-06T17:52:40Z

Steffe:

BIOS

2024-07-06T17:50:37Z

Steffe: Created page with "BIOS are generally a bit trickier to configure after the upgrade to DDR5. Context Memory Restore Once a newly installed computer boots up, expect it to stay black for ~1-2 minutes during boot while DDR is trained. To avoid this, you can enable _Memory Context Restore_ found here on the ASUS B650E-F: Advanced - AMD CBS - UMC Common Options - DDR options - DDR memory features - Memory Context Restore By enabling this, the computer will then do one training on the next..."

BIOS are generally a bit trickier to configure after the upgrade to DDR5.

Context Memory Restore

Once a newly installed computer boots up, expect it to stay black for ~1-2 minutes during boot while DDR is trained.

To avoid this, you can enable _Memory Context Restore_ found here on the ASUS B650E-F:
Advanced - AMD CBS - UMC Common Options - DDR options - DDR memory features - Memory Context Restore
By enabling this, the computer will then do one training on the next reboot, and then reuse that data for upcoming boots, giving the same kind of boot behavior as DDR4 and below.

AMD EXPO

This allows for auto overclocking according to your DDR5 memory. This may increase DDR training time.

Enabling both options should work well, but sometimes it gives stability issues, and you have to refrain from using one of them.

Main Page

2024-07-06T17:45:26Z

Steffe:

Touareg

2024-05-15T19:05:38Z

Steffe:

Oil change tradtitional way: https://www.youtube.com/watch?v=MFMzZk-YIt8

Oil change using pump: https://www.youtube.com/watch?v=Nl7EzuL9Ddg

Adaptive Front Light System: https://www.youtube.com/watch?v=-hw2Sb-cb5E

Key battery replacement: https://www.youtube.com/watch?v=GtBVV3zRsOg

Cabin Air filter replacement: https://www.youtube.com/watch?v=M6Xr9-erxJE

Battery: https://www.bildelaronline24.se/varta/7623154#
Battery replacement: https://www.youtube.com/watch?v=THOuw0Lc0po
Battery adaptation: https://forums.ross-tech.com/index.php?threads/14636/

General info: https://www.youtube.com/watch?v=_VVIi56nO_k

ATF fluid change: https://www.clubtouareg.com/threads/diy-transmission-fluid-change-pics-atf.82168/

Good video on ATF fluid change: https://www.youtube.com/watch?v=baEYViOHzAY

ATF fluid change on previous model including flush: https://www.youtube.com/watch?v=FFglJVcmF6o

Interesting idea on ATF flush on T3: https://www.clubtouareg.com/threads/t3-transmission-flush-idea-with-wonderful-drawings.173138/

Overview of parts: https://volkswagen.7zap.com/en/za/touareg/toua/2012-693/

Blauparts tutorials:
* Engine oil change: https://www.blauparts.com/blog/how-to-change-vw-touareg-engine-oil-30l-tdi.html
* ATF fluid change: https://www.blauparts.com/blog/how-to-change-vw-touareg-transmission-fluid-8-speed.html
* Front differential fluid change: https://www.blauparts.com/blog/how-to-change-vw-touareg-front-differential-fluid.html
* Rear differential fluid change: https://www.blauparts.com/blog/how-to-change-vw-touareg-rear-differential-fluid.html
* Transfer case fluid change: https://www.blauparts.com/blog/how-to-change-vw-touareg-transfer-case-fluid.html

Oils from Ravenol for this car: https://oilguide.ravenol.de/?lang=en&selectedType=a2f5270d56e7c629e95c2c9e9ffec442

* Låda: VW G 055 540 A2 https://www.oljemagasinet.se/index.php?route=product/product&product_id=2004 alt https://www.bildelaronline24.se/ravenol/7743948
* Front: G 052 145 S2 https://www.oljemagasinet.se/index.php?route=product/product&product_id=9559 alt https://www.bildelaronline24.se/ravenol/7669060
* Bak: G 052 145 S2 https://www.oljemagasinet.se/index.php?route=product/product&product_id=9559 alt https://www.bildelaronline24.se/ravenol/7669060
* Trans: G 055 515 A2 / G 052 515 A2 / G 052 536 A2 https://www.ravenol.de/en/product-range/atf-transmission-fluids-for-automatic-transmissions-1/ravenol-transfer-fluid-dtf-1/ which is probably this: https://www.bildelaronline24.se/ravenol/12992621

Filter: https://www.bildelaronline24.se/mahle-original/13892265

Alternativ med pluggar: https://www.bildelaronline24.se/meyle/17408386

Fill adapter: https://www.blauparts.com/audi-vw-transmission-fluid-pump-tool-vas-6262-2-vag-1924.html

This seems to be a VAS6262/2 adapter. Seem to be orderable from here: https://www.ebay.ca/sch/i.html?_nkw=vas+6262%2F2

The fill adapter is ATF105 a which can be bought here:
* https://www.amazon.com/HZ-MONSTAR-Transmission-Compatible-VAS6262-2-Automatic/dp/B08Z7565MW/ref=psdc_15719641_t1_B07HB21V75
* https://www.amazon.se/BGS-9992-4-V%C3%A4xell%C3%A5da-oljep%C3%A5fyllningsadaptersats-delar/dp/B07ZS686J3/ref=sr_1_2?dchild=1&keywords=atf105&qid=1632046739&sr=8-2&th=1
* https://www.xxl-automotive.de/spezialwerkzeug/oeldienst/befuellen/getriebeoel/860/adapter-atf105-m10x1-fuer-mini-und-vag-zu-verw.-wie-vag-6262/2
Kan det vara samma som i den här: https://www.biltema.se/bil---mc/bilverktyg/oljeverktyg/adapterset-till-vaxelladspafyllare/adapterset-till-vaxelladspafyllare-3-delar-2000024070 ?

Complete engine service: https://www.youtube.com/watch?v=zUu-k5TTKAA

Diesel injector removal: https://www.youtube.com/watch?v=QDcUt_5Bkec

Diesel injector rebuild: https://www.youtube.com/watch?v=0vM3jNzUPoM

Diesel injector rebuild2: https://www.youtube.com/watch?v=zv_gJzoObxQ

Using VCDS to diagnose fuel leaks: https://www.youtube.com/watch?v=k50Z5JLfuJs

---

Alternator replacement: https://www.youtube.com/watch?v=5pZ2qGftfYU

Alternator rebuild part 1 - brushes: https://www.youtube.com/watch?v=aVvPzwtxdrM

Alternator rebuild part 2 - slip rings: https://www.youtube.com/watch?v=f56-26I6idc

Touareg

2024-05-15T19:05:25Z

Steffe:

Oil change tradtitional way: https://www.youtube.com/watch?v=MFMzZk-YIt8

Oil change using pump: https://www.youtube.com/watch?v=Nl7EzuL9Ddg

Adaptive Front Light System: https://www.youtube.com/watch?v=-hw2Sb-cb5E

Key battery replacement: https://www.youtube.com/watch?v=GtBVV3zRsOg

Cabin Air filter replacement: https://www.youtube.com/watch?v=M6Xr9-erxJE

Battery: https://www.bildelaronline24.se/varta/7623154#
Battery replacement: https://www.youtube.com/watch?v=THOuw0Lc0po
Battery adaptation: https://forums.ross-tech.com/index.php?threads/14636/

General info: https://www.youtube.com/watch?v=_VVIi56nO_k

ATF fluid change: https://www.clubtouareg.com/threads/diy-transmission-fluid-change-pics-atf.82168/

Good video on ATF fluid change: https://www.youtube.com/watch?v=baEYViOHzAY

ATF fluid change on previous model including flush: https://www.youtube.com/watch?v=FFglJVcmF6o

Interesting idea on ATF flush on T3: https://www.clubtouareg.com/threads/t3-transmission-flush-idea-with-wonderful-drawings.173138/

Overview of parts: https://volkswagen.7zap.com/en/za/touareg/toua/2012-693/

Blauparts tutorials:
* Engine oil change: https://www.blauparts.com/blog/how-to-change-vw-touareg-engine-oil-30l-tdi.html
* ATF fluid change: https://www.blauparts.com/blog/how-to-change-vw-touareg-transmission-fluid-8-speed.html
* Front differential fluid change: https://www.blauparts.com/blog/how-to-change-vw-touareg-front-differential-fluid.html
* Rear differential fluid change: https://www.blauparts.com/blog/how-to-change-vw-touareg-rear-differential-fluid.html
* Transfer case fluid change: https://www.blauparts.com/blog/how-to-change-vw-touareg-transfer-case-fluid.html

Oils from Ravenol for this car: https://oilguide.ravenol.de/?lang=en&selectedType=a2f5270d56e7c629e95c2c9e9ffec442

* Låda: VW G 055 540 A2 https://www.oljemagasinet.se/index.php?route=product/product&product_id=2004 alt https://www.bildelaronline24.se/ravenol/7743948
* Front: G 052 145 S2 https://www.oljemagasinet.se/index.php?route=product/product&product_id=9559 alt https://www.bildelaronline24.se/ravenol/7669060
* Bak: G 052 145 S2 https://www.oljemagasinet.se/index.php?route=product/product&product_id=9559 alt https://www.bildelaronline24.se/ravenol/7669060
* Trans: G 055 515 A2 / G 052 515 A2 / G 052 536 A2 https://www.ravenol.de/en/product-range/atf-transmission-fluids-for-automatic-transmissions-1/ravenol-transfer-fluid-dtf-1/ which is probably this: https://www.bildelaronline24.se/ravenol/12992621

Filter: https://www.bildelaronline24.se/mahle-original/13892265

Alternativ med pluggar: https://www.bildelaronline24.se/meyle/17408386

Fill adapter: https://www.blauparts.com/audi-vw-transmission-fluid-pump-tool-vas-6262-2-vag-1924.html

This seems to be a VAS6262/2 adapter. Seem to be orderable from here: https://www.ebay.ca/sch/i.html?_nkw=vas+6262%2F2

The fill adapter is ATF105 a which can be bought here:
* https://www.amazon.com/HZ-MONSTAR-Transmission-Compatible-VAS6262-2-Automatic/dp/B08Z7565MW/ref=psdc_15719641_t1_B07HB21V75
* https://www.amazon.se/BGS-9992-4-V%C3%A4xell%C3%A5da-oljep%C3%A5fyllningsadaptersats-delar/dp/B07ZS686J3/ref=sr_1_2?dchild=1&keywords=atf105&qid=1632046739&sr=8-2&th=1
* https://www.xxl-automotive.de/spezialwerkzeug/oeldienst/befuellen/getriebeoel/860/adapter-atf105-m10x1-fuer-mini-und-vag-zu-verw.-wie-vag-6262/2
Kan det vara samma som i den här: https://www.biltema.se/bil---mc/bilverktyg/oljeverktyg/adapterset-till-vaxelladspafyllare/adapterset-till-vaxelladspafyllare-3-delar-2000024070 ?

Complete engine service: https://www.youtube.com/watch?v=zUu-k5TTKAA

Diesel injector removal: https://www.youtube.com/watch?v=QDcUt_5Bkec

Diesel injector rebuild: https://www.youtube.com/watch?v=0vM3jNzUPoM

Diesel injector rebuild2: https://www.youtube.com/watch?v=zv_gJzoObxQ

Using VCDS to diagnose fuel leaks: https://www.youtube.com/watch?v=k50Z5JLfuJs

---

Alternator replacement: https://www.youtube.com/watch?v=5pZ2qGftfYU

Alternator rebuild part 1 - brushes: https://www.youtube.com/watch?v=aVvPzwtxdrM
Alternator rebuild part 2 - slip rings: https://www.youtube.com/watch?v=f56-26I6idc

Touareg

2024-05-15T18:55:09Z

Steffe:

Touareg

2024-05-14T20:25:25Z

Steffe:

Oil change tradtitional way: https://www.youtube.com/watch?v=MFMzZk-YIt8

Oil change using pump: https://www.youtube.com/watch?v=Nl7EzuL9Ddg

Adaptive Front Light System: https://www.youtube.com/watch?v=-hw2Sb-cb5E

Key battery replacement: https://www.youtube.com/watch?v=GtBVV3zRsOg

Cabin Air filter replacement: https://www.youtube.com/watch?v=M6Xr9-erxJE

Battery: https://www.bildelaronline24.se/varta/7623154#
Battery replacement: https://www.youtube.com/watch?v=THOuw0Lc0po
Battery adaptation: https://forums.ross-tech.com/index.php?threads/14636/

General info: https://www.youtube.com/watch?v=_VVIi56nO_k

ATF fluid change: https://www.clubtouareg.com/threads/diy-transmission-fluid-change-pics-atf.82168/

Good video on ATF fluid change: https://www.youtube.com/watch?v=baEYViOHzAY

ATF fluid change on previous model including flush: https://www.youtube.com/watch?v=FFglJVcmF6o

Interesting idea on ATF flush on T3: https://www.clubtouareg.com/threads/t3-transmission-flush-idea-with-wonderful-drawings.173138/

Overview of parts: https://volkswagen.7zap.com/en/za/touareg/toua/2012-693/

Blauparts tutorials:
* Engine oil change: https://www.blauparts.com/blog/how-to-change-vw-touareg-engine-oil-30l-tdi.html
* ATF fluid change: https://www.blauparts.com/blog/how-to-change-vw-touareg-transmission-fluid-8-speed.html
* Front differential fluid change: https://www.blauparts.com/blog/how-to-change-vw-touareg-front-differential-fluid.html
* Rear differential fluid change: https://www.blauparts.com/blog/how-to-change-vw-touareg-rear-differential-fluid.html
* Transfer case fluid change: https://www.blauparts.com/blog/how-to-change-vw-touareg-transfer-case-fluid.html

Oils from Ravenol for this car: https://oilguide.ravenol.de/?lang=en&selectedType=a2f5270d56e7c629e95c2c9e9ffec442

* Låda: VW G 055 540 A2 https://www.oljemagasinet.se/index.php?route=product/product&product_id=2004 alt https://www.bildelaronline24.se/ravenol/7743948
* Front: G 052 145 S2 https://www.oljemagasinet.se/index.php?route=product/product&product_id=9559 alt https://www.bildelaronline24.se/ravenol/7669060
* Bak: G 052 145 S2 https://www.oljemagasinet.se/index.php?route=product/product&product_id=9559 alt https://www.bildelaronline24.se/ravenol/7669060
* Trans: G 055 515 A2 / G 052 515 A2 / G 052 536 A2 https://www.ravenol.de/en/product-range/atf-transmission-fluids-for-automatic-transmissions-1/ravenol-transfer-fluid-dtf-1/ which is probably this: https://www.bildelaronline24.se/ravenol/12992621

Filter: https://www.bildelaronline24.se/mahle-original/13892265

Alternativ med pluggar: https://www.bildelaronline24.se/meyle/17408386

Fill adapter: https://www.blauparts.com/audi-vw-transmission-fluid-pump-tool-vas-6262-2-vag-1924.html

This seems to be a VAS6262/2 adapter. Seem to be orderable from here: https://www.ebay.ca/sch/i.html?_nkw=vas+6262%2F2

The fill adapter is ATF105 a which can be bought here:
* https://www.amazon.com/HZ-MONSTAR-Transmission-Compatible-VAS6262-2-Automatic/dp/B08Z7565MW/ref=psdc_15719641_t1_B07HB21V75
* https://www.amazon.se/BGS-9992-4-V%C3%A4xell%C3%A5da-oljep%C3%A5fyllningsadaptersats-delar/dp/B07ZS686J3/ref=sr_1_2?dchild=1&keywords=atf105&qid=1632046739&sr=8-2&th=1
* https://www.xxl-automotive.de/spezialwerkzeug/oeldienst/befuellen/getriebeoel/860/adapter-atf105-m10x1-fuer-mini-und-vag-zu-verw.-wie-vag-6262/2
Kan det vara samma som i den här: https://www.biltema.se/bil---mc/bilverktyg/oljeverktyg/adapterset-till-vaxelladspafyllare/adapterset-till-vaxelladspafyllare-3-delar-2000024070 ?

Complete engine service: https://www.youtube.com/watch?v=zUu-k5TTKAA

Diesel injector removal: https://www.youtube.com/watch?v=QDcUt_5Bkec

Diesel injector rebuild: https://www.youtube.com/watch?v=0vM3jNzUPoM

Diesel injector rebuild2: https://www.youtube.com/watch?v=zv_gJzoObxQ

Using VCDS to diagnose fuel leaks: https://www.youtube.com/watch?v=k50Z5JLfuJs

Alternator replacement: https://www.youtube.com/watch?v=5pZ2qGftfYU

Saab

2024-04-29T21:20:37Z

Steffe:

Gråkletig olja: http://forum.saabturboclub.com/showthread.php/129665-Majon%C3%A4s-p%C3%A5-oljesticka-samt-i-oljef%C3%A4llan-p%C3%A5-OG9-5

Byta topplockspackning: https://www.facebook.com/groups/saabtuboclub/posts/10156971846276755/

Efterdra toppen: http://forum.saabturboclub.com/showthread.php/4960-FAQ-Dragning-Efterdragning-av-topplock

Vevhusventilation: https://shop.speedparts.se/sv/prod/saab/9-5-98-10/motor/vevhusventilation/9-5-04-10/

Vevhusventilationssats: https://folkraceshop.se/vevhusventilation-saab-9-5-2004-2010

Rengöra tråg: http://forum.saabturboclub.com/showthread.php/100780-Guide-Reng%C3%B6ra-tr%C3%A5g-OG9-5-(B2X5)-g%C3%A4ller-delvis-%C3%A4ven-OG9-3

Video byta ventilkåpspackning: https://www.youtube.com/watch?v=Kw7Ssyf66Wc

Renovering vevhusventilation: https://www.youtube.com/watch?v=Uk-Vg-szcyc

Byta turbo: https://saabinfo.se/og9-5/gor-det-sjalv/byte-av-turbo/

Byta turbo: https://www.garaget.org/forum/viewtopic.php?id=287480&p=2

Linux

2020-09-08T08:42:12Z

Steffe: /* udev debugging */

== Debugging Linux applications ==
==== LDD ====
Linux LDD is just a wrapper for:
LD_TRACE_LOADED_OBJECTS=1 <cmd>

==== Core dumps ====
To check core dump handler:
cat /proc/sys/kernel/core_pattern
|/usr/sbin/coredump-handler %h_%t_%p.core

==== Valgrind ====
valgrind --trace-children=yes --leak-check=full --show-leak-kinds=all <binary>

== Configuring Linux ==

==== Graphics drivers ====
===== Disable Nvidia drivers and enable Intel embedded HD graphics driver =====
sudo apt-get purge nvidia-*
dpkg --list | grep nvidia
Make sure the list of nvidia packages is empty
sudo apt-get install --reinstall xserver-xorg-video-intel libgl1-mesa-glx libgl1-mesa-dri mesa-utils xserver-xorg-core
sudo dpkg-reconfigure xserver-xorg
sudo update-alternatives --remove gl_conf /usr/lib/nvidia-current/ld.so.conf
reboot
===== Disable Nvidia drivers and enable nouveau drivers =====
sudo apt-get purge nvidia-*
dpkg --list | grep nvidia
Make sure the list of nvidia packages is empty
sudo apt-get install --reinstall xserver-xorg-video-nouveau
===== Disable nouveau drivers and enable Nvidia drivers =====
'''Option 1''', using package manager:
sudo apt-get install --reinstall nvidia-driver
or if your graphics card is not supported by the latest drivers (you can install the nvidia-detect package and run it to get this information):
sudo apt-get install --reinstall nvidia-legacy-390xx-driver

'''Option 2''', using latest official NVidia driver:
* Go to [http://www.geforce.com] and download the latest Linux driver for your system.
* Switch to console mode (Ctrl+Alt+F1), kill any Xorg process (or mask/stop them with systemctl if you run systemd)
* Run the NVidia installer as root
systemctl mask gdm
systemctl stop gdm
killall Xorg
sudo ./NVIDIA-<driver-version-name>.run

==== Switch default compiler ====

(cc --version;c++ --version;gcc --version;g++ --version) | grep Debian
cc (Debian 6.1.1-11) 6.1.1 20160802
c++ (Debian 6.1.1-11) 6.1.1 20160802
gcc (Debian 6.1.1-11) 6.1.1 20160802
g++ (Debian 6.1.1-11) 6.1.1 20160802

sudo apt-get install gcc-4.9 g++-4.9

gcc-4.9 --version
gcc-4.9 (Debian 4.9.3-14) 4.9.3

g++-4.9 --version
g++-4.9 (Debian 4.9.3-14) 4.9.3

gcc-5 --version
gcc-5 (Debian 5.4.1-1) 5.4.1 20160803

g++-5 --version
g++-5 (Debian 5.4.1-1) 5.4.1 20160803

sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-5 10
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.9 20
sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-5 10
sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.9 20
sudo update-alternatives --install /usr/bin/cc cc /usr/bin/gcc 30
sudo update-alternatives --set cc /usr/bin/gcc
sudo update-alternatives --install /usr/bin/c++ c++ /usr/bin/g++ 30
sudo update-alternatives --set c++ /usr/bin/g++

(cc --version;c++ --version;gcc --version;g++ --version) | grep Debian
cc (Debian 4.9.3-14) 4.9.3
c++ (Debian 4.9.3-14) 4.9.3
gcc (Debian 4.9.3-14) 4.9.3
g++ (Debian 4.9.3-14) 4.9.3

To go back:
sudo update-alternatives --config gcc
sudo update-alternatives --config g++

==== Console is not filling the screen completely ====
This may be due to that the console thinks it is connected to a different display device than it actually is. This can be fixed by adding kernel command line parameters to disable that specific video mode.
ls /sys/class/drm
card0@ card0-DisplayPort-1@ card0-DisplayPort-2@ card0-DisplayPort-3@ card0-HDMI Type A-1@ card0-HDMI Type A-2@ card0-LVDS-1@ card0-SVIDEO-1@ card0-VGA-1@ controlD64@ version
Now check the different "modes" and "connected" and "enabled" nodes under each device to figure out which needs to be disabled. Then add to your kernel command line things such as
video=LVDS-1:d video=SVIDEO-1:d video=TV-1:d
More information: https://bbs.archlinux.org/viewtopic.php?id=94990

=== udev ===
==== udev rules ====
Some sample udev rules which might come handy:
KERNEL=="tty*", GROUP="dialout", MODE="0660"
SUBSYSTEM=="gpio", GROUP:="gpio", MODE:="0660"
SUBSYSTEMS=="usb", KERNEL=="ttyUSB*", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="XXXXXXXX", SYMLINK+="ftdiserial2usb"

Use %m for the device number in symlink names.

==== udev info ====
To query a device about its properties (which can be used in udev rules):

udevadm info --path=/sys/class/leds/example --query=all --attribute-walk
udevadm info --name /dev/sda
udevadm info -a /dev/sda

More info: https://linux.die.net/man/7/udev

==== udev debugging ====
Command to reload udev rules:
sudo udevadm control --reload-rules && sudo udevadm trigger

Command to test udev rules:
udevadm test --action=add /class/gpio

=== Screen ===

How to make the scrollback work in screen? Add the following to your .screenrc file:
termcapinfo xterm ti@:te@

=== LVM ===

==== How to extend your LVM disk ====
Investigate your current setup with:
lsblk
sudo vgdisplay
Then do something like:
sudo lvextend -L +10G /dev/vg0/local
sudo resize2fs /dev/vg0/local

== Linux performance ==
[http://www.brendangregg.com/ http://www.brendangregg.com/]

Pinball

2019-09-02T09:39:57Z

Steffe: /* Interesting DMD hacks */

== Williams/Bally WPC ==

PinWiki: http://pinwiki.com/wiki/index.php?title=Williams_WPC

FlipperWinkel pinball repair: http://techniek.flipperwinkel.nl/wpc/ (fixed version at steffes stuff)

Pinball Rehab: http://pinballrehab.com/

=== Interesting DMD hacks ===

https://pinside.com/pinball/forum/topic/de-jurassic-park-with-lcd-dmd-replacement#post-1102230

http://pin2dmd.com/ (http://vpuniverse.com/forums/topic/2219-pin2dmd-color-pindmd-compatible-interface-with-led-rgb-color-dmd/) (https://github.com/lucky01/PIN2DMD)

https://pinside.com/pinball/forum/topic/williamsbally-dmd-to-hdmi-raspberry-pi-b-project-with-source-code#post-2563487

https://pinside.com/pinball/forum/topic/diy-rgb-led-dmd-4-wpc (https://github.com/hawkulous)

http://adampreble.net/blog/2009/12/arduino-pinball-dmd/ (https://gist.github.com/preble/250458)

http://poormanspinball.blogspot.se/

https://github.com/hawkulous/RPI-WPC-RGB-LED-MATRIX-240hz

http://docs.missionpinball.org/en/latest/hardware/rpi_dmd/

=== Interesting Virtual Pinball links ===

It seems like VPX is currently on top: https://vpinball.com/

It now also supports BAM via Kinect: https://www.youtube.com/watch?v=g-EpTp_3wKo&feature=youtu.be&app=desktop https://www.ravarcade.pl/

And has some legendary tables: https://vpinball.com/bb_project/gilligans-island-3d-vpx-wip/

Pinscape controller: https://os.mbed.com/users/mjr/code/Pinscape_Controller_V2/ or http://mjrnet.org/pinscape/

Pinscape controller build guide: http://mjrnet.org/pinscape/BuildGuideV2/BuildGuide.php?custom=EN.SS.CY.NY.PO.PP.PA.PV.PcY.BY.OY.TvW&expver=R3.201602xx&sid=toc

Linux

2019-08-29T12:01:02Z

Steffe: /* Disable nouveau drivers and enable Nvidia drivers */

== Debugging Linux applications ==
==== LDD ====
Linux LDD is just a wrapper for:
LD_TRACE_LOADED_OBJECTS=1 <cmd>

==== Core dumps ====
To check core dump handler:
cat /proc/sys/kernel/core_pattern
|/usr/sbin/coredump-handler %h_%t_%p.core

==== Valgrind ====
valgrind --trace-children=yes --leak-check=full --show-leak-kinds=all <binary>

== Configuring Linux ==

==== Graphics drivers ====
===== Disable Nvidia drivers and enable Intel embedded HD graphics driver =====
sudo apt-get purge nvidia-*
dpkg --list | grep nvidia
Make sure the list of nvidia packages is empty
sudo apt-get install --reinstall xserver-xorg-video-intel libgl1-mesa-glx libgl1-mesa-dri mesa-utils xserver-xorg-core
sudo dpkg-reconfigure xserver-xorg
sudo update-alternatives --remove gl_conf /usr/lib/nvidia-current/ld.so.conf
reboot
===== Disable Nvidia drivers and enable nouveau drivers =====
sudo apt-get purge nvidia-*
dpkg --list | grep nvidia
Make sure the list of nvidia packages is empty
sudo apt-get install --reinstall xserver-xorg-video-nouveau
===== Disable nouveau drivers and enable Nvidia drivers =====
'''Option 1''', using package manager:
sudo apt-get install --reinstall nvidia-driver
or if your graphics card is not supported by the latest drivers (you can install the nvidia-detect package and run it to get this information):
sudo apt-get install --reinstall nvidia-legacy-390xx-driver

'''Option 2''', using latest official NVidia driver:
* Go to [http://www.geforce.com] and download the latest Linux driver for your system.
* Switch to console mode (Ctrl+Alt+F1), kill any Xorg process (or mask/stop them with systemctl if you run systemd)
* Run the NVidia installer as root
systemctl mask gdm
systemctl stop gdm
killall Xorg
sudo ./NVIDIA-<driver-version-name>.run

==== Switch default compiler ====

(cc --version;c++ --version;gcc --version;g++ --version) | grep Debian
cc (Debian 6.1.1-11) 6.1.1 20160802
c++ (Debian 6.1.1-11) 6.1.1 20160802
gcc (Debian 6.1.1-11) 6.1.1 20160802
g++ (Debian 6.1.1-11) 6.1.1 20160802

sudo apt-get install gcc-4.9 g++-4.9

gcc-4.9 --version
gcc-4.9 (Debian 4.9.3-14) 4.9.3

g++-4.9 --version
g++-4.9 (Debian 4.9.3-14) 4.9.3

gcc-5 --version
gcc-5 (Debian 5.4.1-1) 5.4.1 20160803

g++-5 --version
g++-5 (Debian 5.4.1-1) 5.4.1 20160803

sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-5 10
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.9 20
sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-5 10
sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.9 20
sudo update-alternatives --install /usr/bin/cc cc /usr/bin/gcc 30
sudo update-alternatives --set cc /usr/bin/gcc
sudo update-alternatives --install /usr/bin/c++ c++ /usr/bin/g++ 30
sudo update-alternatives --set c++ /usr/bin/g++

(cc --version;c++ --version;gcc --version;g++ --version) | grep Debian
cc (Debian 4.9.3-14) 4.9.3
c++ (Debian 4.9.3-14) 4.9.3
gcc (Debian 4.9.3-14) 4.9.3
g++ (Debian 4.9.3-14) 4.9.3

To go back:
sudo update-alternatives --config gcc
sudo update-alternatives --config g++

==== Console is not filling the screen completely ====
This may be due to that the console thinks it is connected to a different display device than it actually is. This can be fixed by adding kernel command line parameters to disable that specific video mode.
ls /sys/class/drm
card0@ card0-DisplayPort-1@ card0-DisplayPort-2@ card0-DisplayPort-3@ card0-HDMI Type A-1@ card0-HDMI Type A-2@ card0-LVDS-1@ card0-SVIDEO-1@ card0-VGA-1@ controlD64@ version
Now check the different "modes" and "connected" and "enabled" nodes under each device to figure out which needs to be disabled. Then add to your kernel command line things such as
video=LVDS-1:d video=SVIDEO-1:d video=TV-1:d
More information: https://bbs.archlinux.org/viewtopic.php?id=94990

=== udev ===
==== udev rules ====
Some sample udev rules which might come handy:
KERNEL=="tty*", GROUP="dialout", MODE="0660"
SUBSYSTEM=="gpio", GROUP:="gpio", MODE:="0660"
SUBSYSTEMS=="usb", KERNEL=="ttyUSB*", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="XXXXXXXX", SYMLINK+="ftdiserial2usb"

==== udev debugging ====
Command to reload udev rules:
sudo udevadm control --reload-rules && udevadm trigger

Command to test udev rules:
udevadm test --action=add /class/gpio

=== Screen ===

How to make the scrollback work in screen? Add the following to your .screenrc file:
termcapinfo xterm ti@:te@

== Linux performance ==
[http://www.brendangregg.com/ http://www.brendangregg.com/]

Linux

2019-08-29T11:59:14Z

Steffe: /* Disable nouveau drivers and enable Nvidia drivers */

== Debugging Linux applications ==
==== LDD ====
Linux LDD is just a wrapper for:
LD_TRACE_LOADED_OBJECTS=1 <cmd>

==== Core dumps ====
To check core dump handler:
cat /proc/sys/kernel/core_pattern
|/usr/sbin/coredump-handler %h_%t_%p.core

==== Valgrind ====
valgrind --trace-children=yes --leak-check=full --show-leak-kinds=all <binary>

== Configuring Linux ==

==== Graphics drivers ====
===== Disable Nvidia drivers and enable Intel embedded HD graphics driver =====
sudo apt-get purge nvidia-*
dpkg --list | grep nvidia
Make sure the list of nvidia packages is empty
sudo apt-get install --reinstall xserver-xorg-video-intel libgl1-mesa-glx libgl1-mesa-dri mesa-utils xserver-xorg-core
sudo dpkg-reconfigure xserver-xorg
sudo update-alternatives --remove gl_conf /usr/lib/nvidia-current/ld.so.conf
reboot
===== Disable Nvidia drivers and enable nouveau drivers =====
sudo apt-get purge nvidia-*
dpkg --list | grep nvidia
Make sure the list of nvidia packages is empty
sudo apt-get install --reinstall xserver-xorg-video-nouveau
===== Disable nouveau drivers and enable Nvidia drivers =====
'''Option 1''', using package manager:
sudo apt-get install --reinstall nvidia-driver
or if your graphics card is not supported by the latest drivers (they will tell you):
sudo apt-get install --reinstall nvidia-legacy-390xx-driver

'''Option 2''', using latest official NVidia driver:
* Go to [http://www.geforce.com] and download the latest Linux driver for your system.
* Switch to console mode (Ctrl+Alt+F1), kill any Xorg process (or mask/stop them with systemctl if you run systemd)
* Run the NVidia installer as root
systemctl mask gdm
systemctl stop gdm
killall Xorg
sudo ./NVIDIA-<driver-version-name>.run

==== Switch default compiler ====

(cc --version;c++ --version;gcc --version;g++ --version) | grep Debian
cc (Debian 6.1.1-11) 6.1.1 20160802
c++ (Debian 6.1.1-11) 6.1.1 20160802
gcc (Debian 6.1.1-11) 6.1.1 20160802
g++ (Debian 6.1.1-11) 6.1.1 20160802

sudo apt-get install gcc-4.9 g++-4.9

gcc-4.9 --version
gcc-4.9 (Debian 4.9.3-14) 4.9.3

g++-4.9 --version
g++-4.9 (Debian 4.9.3-14) 4.9.3

gcc-5 --version
gcc-5 (Debian 5.4.1-1) 5.4.1 20160803

g++-5 --version
g++-5 (Debian 5.4.1-1) 5.4.1 20160803

sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-5 10
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.9 20
sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-5 10
sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.9 20
sudo update-alternatives --install /usr/bin/cc cc /usr/bin/gcc 30
sudo update-alternatives --set cc /usr/bin/gcc
sudo update-alternatives --install /usr/bin/c++ c++ /usr/bin/g++ 30
sudo update-alternatives --set c++ /usr/bin/g++

(cc --version;c++ --version;gcc --version;g++ --version) | grep Debian
cc (Debian 4.9.3-14) 4.9.3
c++ (Debian 4.9.3-14) 4.9.3
gcc (Debian 4.9.3-14) 4.9.3
g++ (Debian 4.9.3-14) 4.9.3

To go back:
sudo update-alternatives --config gcc
sudo update-alternatives --config g++

==== Console is not filling the screen completely ====
This may be due to that the console thinks it is connected to a different display device than it actually is. This can be fixed by adding kernel command line parameters to disable that specific video mode.
ls /sys/class/drm
card0@ card0-DisplayPort-1@ card0-DisplayPort-2@ card0-DisplayPort-3@ card0-HDMI Type A-1@ card0-HDMI Type A-2@ card0-LVDS-1@ card0-SVIDEO-1@ card0-VGA-1@ controlD64@ version
Now check the different "modes" and "connected" and "enabled" nodes under each device to figure out which needs to be disabled. Then add to your kernel command line things such as
video=LVDS-1:d video=SVIDEO-1:d video=TV-1:d
More information: https://bbs.archlinux.org/viewtopic.php?id=94990

=== udev ===
==== udev rules ====
Some sample udev rules which might come handy:
KERNEL=="tty*", GROUP="dialout", MODE="0660"
SUBSYSTEM=="gpio", GROUP:="gpio", MODE:="0660"
SUBSYSTEMS=="usb", KERNEL=="ttyUSB*", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="XXXXXXXX", SYMLINK+="ftdiserial2usb"

==== udev debugging ====
Command to reload udev rules:
sudo udevadm control --reload-rules && udevadm trigger

Command to test udev rules:
udevadm test --action=add /class/gpio

=== Screen ===

How to make the scrollback work in screen? Add the following to your .screenrc file:
termcapinfo xterm ti@:te@

== Linux performance ==
[http://www.brendangregg.com/ http://www.brendangregg.com/]