tag:blogger.com,1999:blog-21248318507934354112024-03-05T23:59:08.694+00:00Linux Tipps, Fixes & MoreYour Linux Self-Help Desk. A selection of mostly Linux related tutorials, howtos, fixes, news and more.Unknownnoreply@blogger.comBlogger611125tag:blogger.com,1999:blog-2124831850793435411.post-28122117137772819632019-09-29T13:04:00.000+01:002019-09-29T13:05:15.257+01:00Increasing Network Speed with the example of Raspberry Pi4 and Raspbian<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">I could increase the maximum internet download speed of my Raspberry Pi4 running with the most current Raspbian 64 bit kernel from 60-70 MB/s to a bit over 90 MB/s with the following adjustments. Please note many servers limit downloads e.g. to 400 Mbit/s, even speed test servers.<br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">1. A bash script - you could post this into /etc/rc.local:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_default" style="font-family:verdana,sans-serif"># network speed<br>iface=eth0<br><br># speed up internet - <a href="https://datatag.web.cern.ch/datatag/howto/tcp.html">https://datatag.web.cern.ch/datatag/howto/tcp.html</a><br>/sbin/ifconfig $iface txqueuelen 8000<br>echo 8000 > /proc/sys/net/core/netdev_max_backlog<br>ip link set $iface qlen 20000<br><br># google bbr - <a href="https://www.tecmint.com/increase-linux-server-internet-speed-with-tcp-bbr/">https://www.tecmint.com/increase-linux-server-internet-speed-with-tcp-bbr/</a><br>sysctl -w net.core.default_qdisc=fq<br>sysctl -w net.ipv4.tcp_congestion_control=bbr<br><br># <a href="https://www.cyberciti.biz/faq/rhel-centos-fedora-debian-configure-rx-polling-mode/">https://www.cyberciti.biz/faq/rhel-centos-fedora-debian-configure-rx-polling-mode/</a><br>ethtool -C $iface adaptive-rx on<br><br># <a href="https://cromwell-intl.com/open-source/performance-tuning/ethernet.html">https://cromwell-intl.com/open-source/performance-tuning/ethernet.html</a><br>ethtool -K $iface tx-checksum-ipv4 on<br>ethtool -K $iface tx-checksum-ipv6 on<br><br># not supported <a href="https://cromwell-intl.com/open-source/performance-tuning/ethernet.html">https://cromwell-intl.com/open-source/performance-tuning/ethernet.html</a><br># ethtool -A $iface rx on<br># ethtool -A $iface tx on<br># ethtool -G $iface rx 4096 tx 4096<br></div></blockquote><div><br></div><div style="font-family:verdana,sans-serif" class="gmail_default">Kernel tweaks, you could put this in /etc/sysctl.d/99-netspeed.conf</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="font-family:verdana,sans-serif" class="gmail_default"><br></div><div style="font-family:verdana,sans-serif" class="gmail_default"># <a href="https://serverfault.com/a/758350">https://serverfault.com/a/758350</a><br>kernel.sem = 350 358400 64 1024<br>net.core.rmem_default = 262144<br>net.core.rmem_max = 4194304<br>net.core.wmem_default = 262144<br>net.core.wmem_max = 4194304<br>net.ipv4.tcp_window_scaling = 1<br>net.ipv4.tcp_adv_win_scale = 2<br>net.ipv4.tcp_moderate_rcvbuf = 1<br>net.ipv4.tcp_rmem = 4096 262144 4194304<br>net.ipv4.tcp_wmem = 4096 262144 4194304<br>net.ipv4.tcp_keepalive_time = 900<br>net.ipv4.tcp_keepalive_intvl = 900<br>net.ipv4.tcp_keepalive_probes = 9<br></div></blockquote><div><br></div><div style="font-family:verdana,sans-serif" class="gmail_default">3. Installing irqbalance:</div><div style="font-family:verdana,sans-serif" class="gmail_default">sudo apt install irqbalance</div><div style="font-family:verdana,sans-serif" class="gmail_default"><br></div><div style="font-family:verdana,sans-serif" class="gmail_default">4. Reboot</div><div style="font-family:verdana,sans-serif" class="gmail_default"><br></div><div style="font-family:verdana,sans-serif" class="gmail_default">Enjoy!<br></div></div> <div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-34020982119981989132019-08-05T17:45:00.001+01:002019-08-05T17:45:54.212+01:00Enable fstrim / TRIM / discard support especially for USB SATA disks in Linux<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">If fstrim tells you "discard operation is not supported" on a usb disk then you may want to try this tip. I'm assuming you're using /dev/sdb below, please adjust.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Check if this commands</div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">sg_readcap -l /dev/sdb | grep<span class="gmail_default" style="font-family:verdana,sans-serif"> unmap</span></blockquote><div class="gmail_default" style="font-family:verdana,sans-serif">shows "Unmap command supported (LBPU): <b>1</b>". It must be a 1 at some point or you're out of luck.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">If that works. Try unmounting the drive. Then try this command as root:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><span class="gmail_default" style="font-family:verdana,sans-serif">umount /media/disk</span><br></blockquote><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><span class="gmail_default" style="font-family:verdana,sans-serif">echo </span>unmap > /sys/block/sdb/device/scsi_disk/*/provisioning_mode</blockquote><div><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Now try again to see if it works:</div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">mount /dev/sdb2 /media/disk<br>fstrim -v<span class="gmail_default" style="font-family:verdana,sans-serif"></span> /media/diskidea</blockquote><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">If that works for you, find out the device ID for the usb device with:</div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">lsusb</blockquote><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">and then post the IDs into a udev rule (exampe ID is the StarTech USB 3.0 to 2,5" SATA cable, which I've bought for my Raspberry Pi 4):</div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">echo 'ACTION=="add|change", ATTRS{idVendor}=="174c", ATTRS{idProduct}=="55aa", SUBSYSTEM=="scsi_disk", ATTR{provisioning_mode}="unmap"' > /etc/udev/rules.d/99-trim-ssd-discard.rules</blockquote><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Hope this works for you! Thanks to the <a href="https://bbs.archlinux.org/viewtopic.php?id=236280">original</a> idea!</div></div> <div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-81545270932021933062017-07-26T12:21:00.001+01:002017-07-26T12:21:46.443+01:00Fritz Box VPN mit Cisco und IKE-Fehler<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Hier zeige ich wie man eine Fritz Box mit einen Cisco-VPN verbinden kann. Damit könnte man grds. wohl auch VoIP über VPN bewerkstelligen.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-family:arial,sans-serif">Ich habe folgende Grundkonfiguration für Cisco-VPN genutzt, einfach anpassen und in die Fritz Box importieren:</span><br></div><div class="gmail_default"><br></div><div class="gmail_default"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">vpncfg {<br> connections {<br> enabled = yes;<br> editable = no; // darf nicht an sein, zerschießt sonst die Einstellungen<br> conn_type = conntype_lan;<br> name = "<a href="http://dus.net">dus.net</a>";<br> always_renew = yes;<br> reject_not_encrypted = no;<br> dont_filter_netbios = yes; // muss immer aktiv sein<br> localip = 0.0.0.0;<br> local_virtualip = 0.0.0.0;<br> remoteip = ...;<br> remote_virtualip = 0.0.0.0;<br> localid {<br> key_id = "gruppenname";<br> }<br> mode = phase1_mode_aggressive;<br> phase1ss = "alt/all/all";<br> keytype = connkeytype_pre_shared;<br> key = "gruppenschlüssel";<br> cert_do_server_auth = no;<br> use_nat_t = yes;<br> use_xauth = yes;<br> xauth {<br> valid = yes;<br> username = "";<br> passwd = "";<br> }<br> use_cfgmode = yes; // automatische Einrichtung des remote network<br> phase2localid {<br> ipnet {<br> ipaddr = 192.168.178.0; // Netz der Fritz Box<br> mask = 255.255.255.0;<br> }<br> }<br> phase2ss = "esp-aes256-3des-sha/ah-no/comp-lzs-no/pfs";<br> accesslist =<br> "permit ip any 1.2.3.0 255.255.255.0", // remote network<br> "permit ip any host 3.4.5.6"; // einzelner host<br> }<br> ike_forward_rules = "udp <a href="http://0.0.0.0:500">0.0.0.0:500</a> <a href="http://0.0.0.0:500">0.0.0.0:500</a>",<br> "udp <a href="http://0.0.0.0:4500">0.0.0.0:4500</a> <a href="http://0.0.0.0:4500">0.0.0.0:4500</a>";<br>}</blockquote><div><br></div><div><div class="gmail_default" style="font-family:verdana,sans-serif">AVM hat eine Liste der Bedeutung der diversen IKE-Fehler, aber sie schreiben leider nicht, was man zur Behebung anpassen muss. Ich versuche das stellenweise zu ergänzen. Grundlageninformationen finden sich auch hier:</div><div class="gmail_default"><ul><li><font face="verdana, sans-serif">Einrichtung mit Juniper: <a href="https://blog.webernetz.net/2013/12/02/ipsec-site-to-site-vpn-juniper-screenos-avm-fritzbox/" target="_blank">https://blog.webernetz.net/<wbr>2013/12/02/ipsec-site-to-site-<wbr>vpn-juniper-screenos-avm-<wbr>fritzbox/</a><br></font></li><li><font face="verdana, sans-serif">Liste der IKE-Fehler bei AVM: <a href="https://service.avm.de/help/de/FRITZ-Box-7362-SL-avm/016/hilfe_syslog_122" target="_blank">https://service.avm.de/help/<wbr>de/FRITZ-Box-7362-SL-avm/016/<wbr>hilfe_syslog_122</a><br></font></li><li><font face="verdana, sans-serif">Sicherheitseinstellungen: <a href="https://blog.webernetz.net/2015/03/11/fritzos-ab-06-23-ipsec-p2-proposals-erweitert" target="_blank">http<wbr>s://blog.webernetz.net/2015/<wbr>03/11/fritzos-ab-06-23-ipsec-<wbr>p2-proposals-erweitert</a></font></li><li>Probleme nach dem Update zu Version 6.2 (wohl behoben): <a href="https://blog.webernetz.net/2014/11/25/fritzos-ab-06-20-anderungen-bei-vpns/" target="_blank">https://blog.<wbr>webernetz.net/2014/11/25/<wbr>fritzos-ab-06-20-anderungen-<wbr>bei-vpns/</a></li><li>Weitere Beiträge im Webernetz: <a href="https://blog.webernetz.net/tag/fritzbox/" target="_blank">https://blog.webernetz.net/<wbr>tag/fritzbox/</a><br></li></ul></div><div class="gmail_default" style="font-family:verdana,sans-serif">Typische Fehler</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default"><font face="verdana, sans-serif"><b>IKE-Error 0x2020<span class="gmail-m_-6253445679886094528gmail-Apple-tab-span" style="white-space:pre-wrap"> </span>"hash mismatch in received packet"</b></font><br></div><div class="gmail_default"><br></div><div class="gmail_default"><font face="verdana, sans-serif">Hier gibt es einen Fehler bei den Gewählten <a href="https://blog.webernetz.net/2015/03/11/fritzos-ab-06-23-ipsec-p2-proposals-erweitert/" target="_blank">Algorithmen</a> (vgl. "Tests") wohl in Phase 1 oder das <a href="https://www.vpntracker.com/de/faq/1304/2/Was-ist-ein-Hash-Mismatch?site=vpntracker.com&tab=faq" target="_blank"><b>Passwort stimmt nicht</b></a>. Bei mir hat diese Anpassung geholfen:</font></div><div class="gmail_default"><font face="verdana, sans-serif"><br></font></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><font face="verdana, sans-serif">phase1ss = "alt/all/all";</font></blockquote><div> </div><div><div class="gmail_default" style="font-family:verdana,sans-serif">Probieren kann man diese:</div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-family:arial,sans-serif"> </span></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">dh5/aes/sha<br>dh14/aes/sha<br>dh15/aes/sha<br>def/all/all<br>alt/all/all<br>all/all/all<br>LT8h/all/all/all</blockquote><div class="gmail_default"><br></div><div class="gmail_default">Angeblich kann auch teilweise die MTU schuld sein an diesem Fehler. Sie lässt sich bei der Fritz Box allerdings nicht anpassen. Es kann wohl auch an einem falschen key oder der falschen key_id liegen.<font face="verdana, sans-serif"><b><br></b></font></div><div class="gmail_default"><font face="verdana, sans-serif"><b><br></b></font></div><div class="gmail_default"><font face="verdana, sans-serif"><b>IKE-Error 0x2026<span class="gmail-m_-6253445679886094528gmail-Apple-tab-span" style="white-space:pre-wrap"> </span>"no proposal chosen"<br></b></font></div><div class="gmail_default"><font face="verdana, sans-serif"><b><br></b></font></div><div class="gmail_default"><font face="verdana, sans-serif">Hier handelt es sich wohl um Fehler in <a href="http://richardts.azurewebsites.net/2017/06/26/establishing-a-site2site-vpn-connection-between-avm-fritzbox-7490-or-7580-and-pfsense-azure-vpn-gateway-not-working-well/" target="_blank">Phase 2</a>. </font></div><div class="gmail_default"><br></div><div class="gmail_default">Es stehen u.a. folgende Alternativen zur Verfügung:</div><div class="gmail_default"><br></div><div class="gmail_default"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">esp-3des-sha/ah-no/comp-no/pfs<br>esp-3des-sha/ah-no/comp-no/no-<wbr>pfs<br>esp-aes256-3des-sha/ah-no/<wbr>comp-lzs-no/pfs<br>esp-aes-sha/ah-all/comp-lzjh-<wbr>no/pfs<br>esp-all-all/ah-all/comp-all/<wbr>pfs<br>esp-all-all/ah-all/comp-all/<wbr>no-pfs<br>esp-all-all/ah-none/comp-all/<wbr>pfs<br>esp-all-all/ah-none/comp-all/<wbr>no-pfs<br>LT8h/esp-all-all/ah-none/comp-<wbr>all/pfs<br>LT8h/esp-all-all/ah-none/comp-<wbr>all/no-pfs</blockquote><div><br></div></div></div><div><br></div><div>Noch ein paar Notizen</div></div><div class="gmail_default"><div class="gmail_default"><ul><li>Debugging geht über System -> Ereignisse.</li><li>Die accesslist bestimmt die Routen, die über das VPN gehen: any any heißt von allen Geräten zu allen. Das bedeutet, es wird die default route. Das will man oft nicht.<br></li><li>Wenn die Fritz Box in Ereignisse gar keine Fehler anzeigt, liegt meist ein grober Konfigurationsfehler vor. Die Fritz Box versucht dann gar nicht erst, eine Verbindung herzustellen.<br></li><li>Die Einrichtung des Cisco-Routers wird auch hier beschrieben: <a href="https://blog.webernetz.net/2014/06/25/ipsec-site-to-site-vpn-cisco-router-avm-fritzbox/" target="_blank">https://blog.<wbr>webernetz.net/2014/06/25/<wbr>ipsec-site-to-site-vpn-cisco-<wbr>router-avm-fritzbox/</a><br></li><li>Die Parameter der Konfigurationsdatei werden hier teilweise erläutert: <a href="http://www.wehavemorefun.de/fritzbox/Talk:Versteckte_Features" target="_blank">http://www.<wbr>wehavemorefun.de/fritzbox/<wbr>Talk:Versteckte_Features</a><br></li><li>Das Routing wird hier gut von AVM beschrieben: <a href="https://en.avm.de/service/fritzbox/fritzbox-6840-lte/knowledge-base/publication/show/230_Accessing-multiple-IP-networks-behind-a-FRITZ-Box-over-VPN-connection-between-two-FRITZ-Boxes/" target="_blank">https://en.avm.<wbr>de/service/fritzbox/fritzbox-<wbr>6840-lte/knowledge-base/<wbr>publication/show/230_<wbr>Accessing-multiple-IP-<wbr>networks-behind-a-FRITZ-Box-<wbr>over-VPN-connection-between-<wbr>two-FRITZ-Boxes/</a>. Hier finden sich hilfreiche beispiele (nach "permit" suchen): <a href="http://www.wehavemorefun.de/fritzbox/Ar7.cfg" target="_blank">http://www.<wbr>wehavemorefun.de/fritzbox/Ar7.<wbr>cfg</a><br></li><li>Man darf Netbios nie filtern, sonst verbindet sich die Fritz Box gar nicht erst.<br></li><li>Es kann auch helfen, die Einstellungen der Fritz Box zu exportieren und sich dort Beispielkonfigurationen anzusehen.</li><li>Es gibt auch einen passenden <a href="https://www.heise.de/select/ct/2017/15/1500314446764256" target="_blank">Artikel zu Fritz Box VPNs mit Firewalls</a>in einer aktuellen c't: "In Phase 1 und Phase 2 werden außerdem die Krypto-Protokolle (Proposals) und die Dauer der Schlüsselgültigkeit ausgehandelt (Lifetimes). Dieser Einstellungsbereich gilt als Mutter allen IPsec-Übels – weil es sehr viele Optionen gibt."</li></ul></div></div></div> <div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-32093803841597597932017-07-26T09:02:00.000+01:002017-07-26T09:03:34.287+01:00Samsung Scanner in Your Network Despite Firewall With Manual Setup<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">To manually detect a Samsung network scanner with sane, you can try this method:</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-family:monospace;color:rgb(0,0,0)">echo 'tcp scx' | sudo tee -a </span><span style="color:rgb(0,0,0);font-family:monospace">/etc/sane.d/xerox_mfp.conf</span></blockquote><div class="gmail_default"><span style="color:rgb(0,0,0);font-family:monospace"><br></span></div><div class="gmail_default"><span style="font-family:verdana,sans-serif">Replace "scx" with </span><span style="font-family:verdana,sans-serif">the IP address or resolvable hostname of your scanner. Try to ping the host, e.g. "ping scx" before you enter it here.</span></div><div class="gmail_default"><span style="font-family:verdana,sans-serif"><br></span></div><div class="gmail_default"><span style="font-family:verdana,sans-serif">This assumes using the drivers from </span><font face="verdana, sans-serif"><a href="http://www.bchemnet.com/suldr">www.bchemnet.com/suldr</a>. For some services, you may have to restart the service or your computer. It fixed using the scanner with an active firewall for me.</font></div></div> <div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-35127008912522199122017-07-26T08:53:00.001+01:002017-07-26T08:53:49.619+01:00Diverse Probleme mit der Fritz Box bei fehlerhaften VPN-Einstellungen<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Wenn man die VPN-Funktion der Fritz Box nutzt, sollte man regelmäßig prüfen, ob alle ausgehenden Verbindungen funktionieren.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Denn nicht funktionierende ausgehende VPN-Verbindungen (z.B. Kopplung zwischen zwei Fritz Boxen) können zu diversen Problemen führen, u.a. schlechte Sprachqualität beim VoIP, Paketverluste und langsameres Internet. Wenn man eine aktive VPN-Verbindung hat, die die Default Route setzt (z. B. automatisch via <i>use_cfgmode = no;</i>), kann sogar das Internet insgesamt unterbrochen werden.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Die Lösung ist einfach: Den Haken links neben der VPN-Verbindung abwählen und die Einstellungen übernehmen.</div></div> <div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-4219052956726780162016-07-24T19:43:00.000+01:002016-07-24T19:44:26.144+01:00[Fix] Getting the MSI PE60 6QE (Skylake) to run Linux<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">After lots of experimentation, it turned out that the best boot parameter so far (Ubuntu 16.10 alpha July 2016) is:</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div class="gmail_default" style="font-family:verdana,sans-serif"><b>pci=noacpi</b></div></blockquote><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Otherwise (e.g. with acpi=noirq), there is a crash trying to load the nvidia card and an issue with ACPI trying to load _DSM. If you want to disable the nivida card completely, for 6W or more of power savings, use nouveau.modeset=0. This might need to be in addition to pci=noacpi.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">This might work for lots of other notebooks, especially with Nvidia graphics and a Skylake CPU, e.g. the MSI GE62 6QF series.</div></div> <div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-20434012126832879002016-05-05T12:15:00.000+01:002016-05-06T10:24:43.189+01:00Prioritizing System Services with Systemd - Run a Process Permanently in the Background<div dir="ltr">
<div class="gmail_default" style="font-family: verdana,sans-serif;">
<span style="font-family: "verdana" , sans-serif;">If you simply want to adjust some priorities, here is how to do it in three steps.</span></div>
<div class="gmail_default" style="font-family: verdana,sans-serif;">
<ol>
<li><span style="font-family: "verdana" , sans-serif;">sudo systemctl edit [service]</span></li>
<li><span style="font-family: "verdana" , sans-serif;">sudo systemctl daemon-reload</span></li>
<li><span style="font-family: "verdana" , sans-serif;">sudo systemctl restart [service]</span></li>
</ol>
</div>
<div class="gmail_default" style="font-family: verdana,sans-serif;">
</div></div><a href="http://linux-tipps.blogspot.com/2016/05/prioritizing-system-services-with.html#more">Read more »</a><div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-70427580260982647172016-05-03T12:13:00.001+01:002016-05-03T12:13:40.583+01:00Removing all images with rkt<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Note this will remove all images, not just stale ones. Set rkt to point to your rkt binary.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">#!/bin/sh<br>rkt="./rkt/rkt"<br>images="$(sudo $rkt image list | awk 'NR>1 {print $1}')"<br>set -x<br>sudo $rkt gc --grace-period=1s<br>sleep 1<br>sudo $rkt gc --grace-period=1s<br>sudo $rkt image list<br>sudo $rkt image rm $images</blockquote></div></div> <div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-87423125389019074872016-02-12T11:36:00.001+00:002016-02-12T11:36:59.133+00:00Forward Wake on LAN packages bewteen networks with socat<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">If you have two networks and you want to wake a machine in another from network it can be tricky because you can't always set the destination IP address or network. An easy fix is to use socat to forward the UDP wakeonlan packages to the other network or IP:</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">sudo socat -v UDP4-RECVFROM:9,fork UDP4-SENDTO:<a href="http://192.168.1.255:9">192.168.1.255:9</a></blockquote><div class="gmail_default"><font color="#000000" face="monospace"><br></font></div><div class="gmail_default"><font color="#000000" face="monospace">You can leave out the -v for less verbosity. The target network is 192.168.1.255, you can replace this with a specific IP, which helps with routers not forwarding broadcasts. Usually UDP port 9 is used, but you may change this to port 7 for your setup. You will need to be root because port 9 is generally privileged.</font></div></div> <div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-46188932559752057872015-08-28T15:51:00.001+01:002015-08-28T15:51:41.156+01:00Fscking Precautions: Snapshots and the undo file<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">If you have a badly corrupted filesystem, e.g. because you had back blocks on the hard drive, you have want to take some precautions to make sure fsck doesn't destroy your files. This goes especially for large raids.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Something you can always do is test the fsck operation on a dmsetup snapshot. For this to work you must boot from a different partition and it must have a sparse file enabled filesystem.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex" class="gmail_quote"># The path to your snapshot storage file.<br>INPUT=/dev/sdb4<br><font face="verdana, sans-serif">COW=<div class="gmail_default" style="font-family:verdana,sans-serif;display:inline">/root/sdb4-</div><div class="gmail_default" style="font-family:verdana,sans-serif;display:inline">snapshot</div><br></font><span style="font-family:verdana,sans-serif">#<div class="gmail_default" style="font-family:verdana,sans-serif;display:inline">20</div> Terabytes should be enough for your partition, otherwise increase this number<br></span><span style="font-family:verdana,sans-serif">truncate -s<div class="gmail_default" style="font-family:verdana,sans-serif;display:inline">20</div>000G $COW <br></span><span style="font-family:verdana,sans-serif">#setup a loop for dmsetup snapshots to the COW file.<br></span><span style="font-family:verdana,sans-serif">loop="$(losetup -f)"<br></span><font face="verdana, sans-serif">losetup $loop $COW<br></font><font face="verdana, sans-serif">#setup the snapshot device<br></font><span style="font-family:verdana,sans-serif">echo 0 `blockdev --getsz $INPUT` snapshot $INPUT $loop p 8 | dmsetup create top<br></span><span style="font-family:verdana,sans-serif"># let you know where the snapshot device is.<br></span><span style="font-family:verdana,sans-serif">echo loop: $loop top: /dev/mapper/top<br></span><font face="verdana, sans-serif">dmsetup status</font></blockquote><div class="gmail_default" style=""><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">After this you should be able to fsck /dev/mapper/top. You can see how much space the COW file actually occupies with du -h $COW. You may also want to get the newest fsck version (e.g. with a newer fsck-static package). If you end up with many multiply-claimed blocks, this e2fsck version may help: <a href="http://git.hpdd.intel.com/tools/e2fsprogs.git/">http://git.hpdd.intel.com/tools/e2fsprogs.git/</a> (checkout a -wc branch).</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">Good luck, you might need it!</div></div></div> <div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-30526183239230649132015-08-18T07:57:00.000+01:002015-08-18T07:58:26.663+01:00Linux Raid: ignoring /dev/sdX as it reports /dev/sdY as failed<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">The fix for this problem may be extremely easy. What happened is that some disks of the raid failed. They were ejected. This happens. But the raid won't be assembled anymore if the failed disks are first on the mdadm assemble command line. Because for some reason, mdadm does not check what most disks say, but what the first disks say. So if you have a raid with 10 disks and the first two on the command line are failed, it will reject the remaining 8, because the are not compatible. All you need to do now is to list those two failed disks at the end with --force to activate the raid again:</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Instead of </div><div class="gmail_default" style="font-family:verdana,sans-serif">mdadm /dev/md1 --assemble /dev/sdX,Y /dev/sd[a-f]</div><div class="gmail_default" style="font-family:verdana,sans-serif">try</div><div class="gmail_default" style="font-family:verdana,sans-serif">mdadm /dev/md1 --assemble /dev/sd[a-f] /dev/sdX,Y<br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Note that there's probably still a good reason for those disks to have been marked as failed...</div></div> <div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-69072398911693448772015-06-22T20:05:00.000+01:002015-06-22T20:06:14.359+01:00Windows 7 Detects only Some of the CPUs added in KVM [Fix]<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">If Windows XP, Windows 7, maybe even Windows 8 or later don't detect all your CPUs in KVM, you may need to change the settings. <a href="http://serverfault.com/questions/101434/why-does-my-windows-7-vm-running-under-linux-kvm-not-use-all-the-virtual-proces">Windows often</a> doesn't like if you have too many cpu sockets. Try a configuration with 1 or <a href="http://www.openwebit.com/c/how-to-run-windows-vm-on-more-than-2-cores-under-kvm/">2 sockets</a> and several cores.</div></div> <div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-73570697882220424332015-05-30T17:33:00.000+01:002015-05-30T17:34:17.517+01:00How to Dynamically Switch Between Uniprocessor and SMP during Windows XP boot<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">If you're running Windows XP inside a Virtual Machine such as VirtualBox, Vmware or KVM, you may want to sometimes boot with only one active CPU, other times with several CPUs. If you don't set up windows correctly, it will neither boot normally, nor in safe mode (where it will stop with a blank screen and a blinking cursor).</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">But you can edit your boot.ini to look like this in order to dynamically switch between one and several processors in Windows XP:</div><div class="gmail_default" style><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">[boot loader]<br>timeout=5<br>default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS<br>[operating systems]<br>multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro" /noexecute=optin /fastdetect<br>multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro one processor" /noexecute=optin /fastdetect /kernel=ntoskrnl.exe /HAL=Halaacpi.dll<br>multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro SMP" /noexecute=optin /fastdetect /kernel=ntkrnlmp.exe /hal=halmacpi.dll</blockquote></div></div> <div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-9317051446073125932015-05-16T11:17:00.002+01:002015-05-20T18:49:35.021+01:00The Ultimate Setup Guide for ownCloud on Small Systems such as the Raspberry PiIt took me about a year to collect this information. There are many guides, but all I found are incomplete. Here's the one guide to rule them all - hopefully. The guide works on Ubuntu and Debian without changes. It's optimized for resources, speed, security and ease of use. While this runs well on my old phone (ARMv7; 512 MB; ~1000 BogoMIPS), it should run even better on a Raspberry Pi.<br>
<a href="http://linux-tipps.blogspot.com/2015/05/the-ultimate-setup-guide-for-owncloud.html#more">Read more »</a><div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-79038311433317456302015-05-15T17:19:00.000+01:002015-05-16T11:17:45.550+01:00Accessing Public ownCloud shares via WebDAV<div dir="ltr">
<div class="gmail_default" style="font-family: verdana,sans-serif;">
Since ownCloud supports server to server sharing you can <a href="https://github.com/owncloud/core/pull/8353">access public shares via webdav clients</a>. You simply use the access token (t=...) as user name. If there is a password, use that as password, otherwise leave it blank. As URL you use the owncloud address with /public.php/webdav at the end:</div>
<div class="gmail_default">
<span style="font-family: verdana,sans-serif;"><br /></span></div>
<div class="gmail_default">
<span style="font-family: verdana,sans-serif;"><a href="https://myserver.com/owncloud/public.php?service=files&t=">https://myserver.com/owncloud/public.php?service=files&t=</a><b>12345</b></span></div>
<div class="gmail_default">
<span style="font-family: verdana, sans-serif;">-> </span><span style="font-family: verdana,sans-serif;">webdavs://</span><b style="font-family: verdana,sans-serif;">12345@</b><span style="font-family: verdana,sans-serif;"><a href="http://myserver.com/owncloud/">myserver.com/owncloud/</a></span><b style="font-family: verdana,sans-serif;">public.php/webdav</b></div>
<div class="gmail_default">
<br /></div>
</div>
<div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-72320638705945105282015-05-15T13:30:00.000+01:002015-05-16T11:19:51.778+01:00Speeding up your ownCloud on small systems such as the Raspberry Pi with Sqlite<div dir="ltr">
<div class="gmail_default" style="font-family: verdana,sans-serif;">
<br>
I had seriously considered to use a raspberry pi system for setting up my ownCloud server. But the old pi had pretty much the same capabilities as my old mobile phone with cyanogen. And the phone has Wifi and some flash space already included. So I opted for the phone. As with most pi installations, the performance was not great. But I found some easy tweaks I haven't seen anywhere else to significantly improve the performance. I'm assuming you're already using the <a href="http://linux-tipps.blogspot.com/2015/05/the-ultimate-setup-guide-for-owncloud.html" target="_blank">usual tweaks</a> such as <a href="http://www.hostingadvice.com/how-to/enable-php-5-5-opcache-ubuntu-14-04/" target="_blank">opcache</a>(this will usually help more than the following tweaks!) and using cron.php. <b>Please backup your owncloud.db before you start! </b>You will need the sqlite3 tool (sudo apt-get install sqlite3).</div>
<div class="gmail_default" style="font-family: verdana,sans-serif;">
<br>
</div></div><a href="http://linux-tipps.blogspot.com/2015/05/speeding-up-your-owncloud-on-small.html#more">Read more »</a><div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-68127127084958096702015-05-12T16:26:00.000+01:002015-05-12T16:27:06.201+01:00Two ways to download your pictures from Picasaweb with Linux<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">There is a nerdy and a simple way. The simple way is to use the google <a href="https://www.google.com/settings/takeout/downloads">data export ("takeout")</a> pages. You select your photos, create an archive and download it. You may have to upgrade from Picasaweb to Google+ in order for this to work properly.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">The nerdy way is via googlecl. Unfortunately this option does not currently work properly due to googlecl <a href="https://code.google.com/p/googlecl/issues/detail?id=573">still using oauth version 1</a>. But once that's fixed - or if you're still signed into googecl - you can use these two commands:</div><div class="gmail_default" style><font face="verdana, sans-serif"><br></font></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex" class="gmail_quote"><span style="font-family:verdana,sans-serif">google picasa list-albums > albums.txt<br></span><font face="verdana, sans-serif">parallel -a "albums.txt" -j 3 --eta google picasa get "{,}" .</font></blockquote><div class="gmail_default" style><font face="verdana, sans-serif"><br></font></div><div class="gmail_default" style>Beware of weird folder names including / or other special symbols. Now you can e.g. move your pictures to your ownCloud server. No picasa needed.</div></div> <div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-41487158815277391552015-05-01T09:10:00.001+01:002015-05-01T09:10:17.930+01:00How to change the volume with an active lock screen in android lollipopThis works at least from my Samsung galaxy S4: you press the power button for a few seconds until you see the pop-up to turn off the device, or to go into offline mode. Now you can use the volume buttons to change the ring tone volume.<div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-54277318189751361352015-04-29T13:42:00.000+01:002015-05-15T13:50:48.416+01:00Fixing Netflix Error Code: M7361-1254 on a Linux System<div dir="ltr">
<div class="gmail_default" style="font-family: verdana,sans-serif;">
If you get this error code there is an issue with the sound output. If you use pulse, kill the pulseaudio process. Then close the browser, open it again.</div>
<div class="gmail_default" style="font-family: verdana,sans-serif;">
<br /></div>
<div class="gmail_default" style="font-family: verdana,sans-serif;">
Otherwise remove the kernel driver module for your sound card and insert it again. Then close and open the browser.</div>
</div>
<div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-1862878737100889462015-04-27T10:14:00.001+01:002015-04-27T10:14:40.861+01:00How to Fix a common VirtualBox Segfault<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">If you have a segmentation fault during the start of a VirtualBox machine, you are likely using an old, incompatible version of the VirtualBox Extensions. Simply update or uninstall them and things should work again.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">An example from the dmesg kernel log:</div><div class="gmail_default" style><font face="verdana, sans-serif">EMT-1 [7265]: segfault at 618 ip 00007f0eaacbef31 sp 00007f0ed2afbc70 error 4 in VBoxDD.so [7f0eaac00000+26f000].</font><br></div></div> <div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-2124831850793435411.post-85414483977400646602015-04-19T10:52:00.000+01:002015-04-19T10:56:25.373+01:00Checking S.M.A.R.T. status for USB drive<div dir="ltr">
<div class="gmail_default" style="font-family: verdana,sans-serif;">
Usually smartctl -a works out of the box. But sometimes it doesn't. In that case, try using the option -d sat, e.g. smartctl -d sat -a /dev/sdb. That may solve if a modern external USB drive reports that SMART support is "unavailable" and that the "device lacks SMART capability". Because that a drive actually lacks the capability is extremely unlikely these days. If that doesn't work, you can try -d auto or consult an <a href="https://www.smartmontools.org/wiki/Supported_USB-Devices" target="_blank">extensive list</a> of options of different devices.</div>
</div>
<div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-22078308981504193202015-04-08T11:59:00.000+01:002015-04-08T11:58:45.021+01:00Recording with tape-a-talk to external sd card in KitKatYou can enter a manual storage path. It must be setup like the following path. This path can be adjusted to work with other apps and different devices:
<br>
<br>/storage/extSdCard/Android/data/name.markus.droesser.tapeatalk/files
<br>
<br>If you use the wrong path the app won't be able to write anything. This path works on most Samsung devices.<div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-2124831850793435411.post-59896744387287506632015-03-30T17:48:00.000+01:002015-03-30T17:49:25.102+01:00How to Fix a Broken Sector of Your Hard Drive<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">First you should really backup the whole drive. Because unreadable sectors mean that the drive will fail soon:</div><div class="gmail_default" style="font-family:verdana,sans-serif">(<i>"Add. Sense: Unrecovered read error - auto reallocate failed</i></div><div class="gmail_default" style="font-family:verdana,sans-serif"><i>sd 0:0:0:0: [sda] CDB: </i><i>... </i><i>end_request: I/O error, dev sda, <b>sector 3459933711</b> </i><i>..."</i>).</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">You may be able to solve the issue temporarily but you should expect the drive to fail completely at any moment. So ddrescue to another disk of the same size. First, only rescue good parts:</div><div class="gmail_default" style="font-family:verdana,sans-serif"><u>ddrescue -n olddew newdev ~/logfile</u></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Then try to rescue the rest:</div><div class="gmail_default" style="font-family:verdana,sans-serif"><u>ddrescue olddew newdev ~/logfile</u><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Then try to manually read the sector with hdparm. In your example, the marked sector above. This probably won't work.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><u>hdparm --read-sector 3459933711</u></div><div class="gmail_default" style="font-family:verdana,sans-serif">Then you can overwrite the sector with zeros so it won't cause repeated hangs:</div><div class="gmail_default" style><font face="verdana, sans-serif"><u>hdparm --write-sector 3459933711</u></font><br></div><div class="gmail_default" style><font face="verdana, sans-serif"><br></font></div><div class="gmail_default" style><font face="verdana, sans-serif">And now you order a replacement drive and wait for the drive to fail entirely.</font></div></div> <div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-21737670465614674112015-03-30T17:34:00.000+01:002015-03-30T17:35:24.535+01:00How to Efficiently Replace a Broken Disk from a Linux Software RAID 5<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">1. ddrescue the broken disk to a new, completely empty disc. At least zero the former raid superblock... (<u>ddrescue -n faileddev newdev logfile; ddrescue faileddev newdev logfile</u>)</div><div class="gmail_default" style="font-family:verdana,sans-serif">If successful (if you have bad blocks that couldn't be rescued, you should preferably rebuild the raid.)</div><div class="gmail_default" style="font-family:verdana,sans-serif">2. add the disc to the raid and remove the failed disc from the raid</div><div class="gmail_default" style="font-family:verdana,sans-serif">3. go to the sysfs folder of the raid device, e.g. <u>cd /sys/block/md0/md/</u>.</div><div class="gmail_default" style="font-family:verdana,sans-serif">4. put the new disc into the slot of the failed old disc:, e.g. <u>echo 2 > dev-sdc1/slot.</u></div><div class="gmail_default" style="font-family:verdana,sans-serif">5. check the raid to be sure if all worked out well: <u>echo check > /sys/block/md0/md/sync_action</u>.</div></div> <div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-2124831850793435411.post-29163173617653613522015-03-16T16:25:00.000+00:002015-03-16T16:26:24.478+00:00TVHeadend with Transcode Support in Ubuntu 14.04<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Unfortunately the packages from the repository no longer support transcoding recently. You have to <a href="https://tvheadend.org/boards/4/topics/13635">build your own package</a>.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">sudo apt-get install build-essential pkg-config libssl-dev git libavahi-client-dev libavcodec-dev libavfilter-dev libavformat-dev libavutil-dev libswscale-dev libavcodec-extra-53 liburiparser1 liburiparser-dev debhelper libcurl4-gnutls-dev a52dec</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style><font face="verdana, sans-serif">git clone <a href="https://github.com/tvheadend/tvheadend.git">https://github.com/tvheadend/tvheadend.git</a></font><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style><font face="verdana, sans-serif">AUTOBUILD_CONFIGURE_EXTRA=--enable-libffmpeg_static ./Autobuild.sh -t trusty-i386</font><br></div><div class="gmail_default" style><font face="verdana, sans-serif"><br></font></div><div class="gmail_default" style><font face="verdana, sans-serif"><i>or</i></font></div><div class="gmail_default" style><font face="verdana, sans-serif"><br></font></div><div class="gmail_default" style><font face="verdana, sans-serif">AUTOBUILD_CONFIGURE_EXTRA=--enable-libffmpeg_static ./Autobuild.sh -t trusty-amd64<br></font></div><div class="gmail_default" style><font face="verdana, sans-serif"><br></font></div><div class="gmail_default" style><font face="verdana, sans-serif">Finally, the transcode setting is no longer in the general tab. Rather, you can now enable transcoding by selecting special profiles you can set up under Coniguration, Stream, Stream Profiles. Unfortunately, most the Android apps don't support this at the moment. You may want to try to checkout the version before committ c4089cc7a378abc2d8912d86d6440aab6230967a.</font></div></div> <div class="blogger-post-footer">(...)
-- Click to read the entire post.</div>Unknownnoreply@blogger.com0