Author Archives: Stevepedwards@gmail.com

Post Install Mint Sonya 18.2 Additions

Mint 18.3 is now a lot more stable than when I last looked 1 yr back

2 sudo apt update
3 sudo apt upgrade
4 sudo locale-gen --purge --no-archive
7 sudo apt-get install k3b
8 sudo vi /etc/nsswitch.conf
9 sudo smbpasswd -a stevee
10 sudo vi /etc/samba/smb.conf
11 ssh-keygen
12 nbtscan 192.168.1.0/24
13 ssh-copy-id -i ~/.ssh/id_rsa.pub PIQUADRA
16 sudo vi /etc/default/grub
17 sudo update-grub2
18 inxi -Fxz
19 sudo passwd root
20 sudo sensors-detect
21 cat /proc/cpuinfo
22 sudo apt-get remove thunderbird* --purge
23 sudo apt-get install ssh nmap vim automake autoconf module-assistant nbtscan locate libnss-winbind winbind g++ libcurl3 gparted testdisk hardinfo
24 sudo reboot

vi .bash_aliases

alias BIGducks='du -cBG * | sort -nr | head -11'
alias duse='for i in G M K; do du -hsx * | grep "[0-9]$i\b" | sort -nr; done'
alias ducks='du -cks * | sort -rn | head -11'
alias bupiquadra='rsync -e ssh --progress /home/stevee/* stevee@bupiquadra:/home/stevee/Quadra/stevee/ --exclude='.' --exclude='Videos' -vah'

 

HP AMDA8 1.0 TB Hard Disk Benchmark Reference

Partition 1 of 250 GB Hard Disk — Memorex Ultra TD v1.0

Partition 1 of 160 GB Hard Disk — Ext Iomega Hard Disk

Partition 1 of Integral 7.8 GB Drive — USB DISK 3.0 [PMAP]

Sandisk SSD:

Bus 004 Device 002: ID 152d:0567 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge:

Hitachi 160 Ext USB (2007)

SanDisk Ultra Fit #1 (eh???? too hot? ):

SanDisk Ultra Fit#2 (USB3) eh??? again!

Correct SanDisk Ultra Fit [1.00] USB3, later date - more like it!

Partition 1 of 16 GB Thumb Drive — Kingston DataTraveler 2.0 (suspect system issue these dates as with first Ultra Fit readings same time above...?)

 

Pi3 – Can’t Log In To Desktop Except User Pi

Setting to Desktop login for user stevee via raspi-conf then rebooting I cannot login.

The default pi user can though...

Looking at:

sudo vi .Xauthority

It retains the old hostname in MIT magic cookie. Seems there are a few issues with the latest Raspbian Lite eh?

This may also explain the inability to highlight/copy/paste text via SSH also.

Let's delete it, set auto Dtop login via raspi-config, then see if a new one is created on reboot and try again...

Nope - didn't autologin and I still can't login...

sudo vi .xsession-errors

No win managers? That explains a lot!

stevee@pi3:~ $ sudo apt install lightdm

[sudo] password for stevee:
Reading package lists... Done
Building dependency tree
Reading state information... Done
lightdm is already the newest version (1.18.3-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Already installed - just not working? Already latest dist:

stevee@pi3:~ $ sudo apt dist-upgrade

Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

stevee@pi3:~ $ sudo dpkg-reconfigure lightdm

stevee@pi3:~ $ sudo apt install desktop-base
Reading package lists... Done
Building dependency tree
Reading state information... Done
desktop-base is already the newest version (9.0.2+deb9u1).
desktop-base set to manually installed.

Fuck's sake - this Raspbian Lite - just that! Very Lite on function! But it's still 1.9GB large - same size as Mint install that HAS Cinnamon...what App crap have they filled it with I wonder - over the basics?

They've even removed Ctrl-Alt-Backspace for Xserver respawn! No startx either?? try another DM:

stevee@pi3:~ $ sudo apt install lxde

Just in case it still requires what it said was missing above after...

stevee@pi3:~ $ touch .xsession

stevee@pi3:~ $ sudo reboot

Nope - same...

Let's remove and re-install lightdm:

stevee@pi3:~ $ sudo apt remove lightdm* --purge

stevee@pi3:~ $ sudo apt install light-locker lightdm lightdm-gtk-greeter

stevee@pi3:~ $ sudo raspi-config (Set dtop auto login)
stevee@pi3:~ $ sudo reboot

Nope! As there is a login issue - check security related logs...?

stevee@pi3:~ $ sudo cat /var/log/auth.log | grep fail
Oct 4 23:15:14 piinteg3 login[555]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=stevee
Oct 5 16:40:30 piinteg3 login[555]: FAILED LOGIN (1) on '/dev/tty1' FOR 'stevee', Authentication failure

There is the retention of the old device name again as was in /etc/hosts for the wifi Post!

As it's PAM db related I'll add my user using:

stevee@pi3:~ $ sudo pdbedit -a stevee
new password:
retype new password:
Unix username: stevee
NT username:
Account Flags: [U ]
User SID: S-1-5-21-4262368663-1680611761-3889941877-1000
Primary Group SID: S-1-5-21-4262368663-1680611761-3889941877-513
Full Name:
Home Directory: \\pi3\stevee
HomeDir Drive:
Logon Script:
Profile Path: \\pi3\stevee\profile
Domain: PI3
Account desc:
Workstations:
Munged dial:
Logon time: 0
Logoff time: never
Kickoff time: never
Password last set: Sun, 08 Oct 2017 23:30:24 BST
Password can change: Sun, 08 Oct 2017 23:30:24 BST
Password must change: never
Last bad password : 0
Bad password count : 0
Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

stevee@pi3:~ $ sudo reboot

Looking at tail syslog via SSH while logging in locally all I see of possible relevance is:

Oct 8 23:34:16 pi3 systemd[1]: Created slice User Slice of lightdm.
Oct 8 23:34:16 pi3 systemd[1]: Starting User Manager for UID 109...
Oct 8 23:34:16 pi3 systemd[1]: Started Session c9 of user lightdm.
Oct 8 23:34:16 pi3 systemd[1278]: Starting D-Bus User Message Bus Socket.
Oct 8 23:34:16 pi3 systemd[1278]: Reached target Paths.
Oct 8 23:34:16 pi3 systemd[1278]: Listening on GnuPG cryptographic agent and passphrase cache.
Oct 8 23:34:16 pi3 systemd[1278]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Oct 8 23:34:16 pi3 systemd[1278]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Oct 8 23:34:16 pi3 systemd[1278]: Reached target Timers.
Oct 8 23:34:16 pi3 systemd[1278]: Listening on GnuPG cryptographic agent (access for web browsers).
Oct 8 23:34:16 pi3 systemd[1278]: Listening on D-Bus User Message Bus Socket.
Oct 8 23:34:16 pi3 systemd[1278]: Reached target Sockets.
Oct 8 23:34:16 pi3 systemd[1278]: Reached target Basic System.
Oct 8 23:34:16 pi3 systemd[1278]: Reached target Default.
Oct 8 23:34:16 pi3 systemd[1278]: Startup finished in 80ms.
Oct 8 23:34:16 pi3 systemd[1]: Started User Manager for UID 109.
Oct 8 23:34:16 pi3 systemd[1278]: Started D-Bus User Message Bus.
Oct 8 23:34:16 pi3 org.a11y.atspi.Registry[1295]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Oct 8 23:34:16 pi3 dbus-daemon[1293]: Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
Oct 8 23:34:16 pi3 systemd[1278]: Starting Virtual filesystem service...
Oct 8 23:34:16 pi3 dbus-daemon[1293]: Successfully activated service 'org.gtk.vfs.Daemon'
Oct 8 23:34:16 pi3 systemd[1278]: Started Virtual filesystem service.

It's not an auth/password issue as I get a warning with a login with an incorrect password, so user auth is ok, but next required service for user stevee won't allow access.

Rebooting to user stevee auto console login is ok, and running:

sudo lightdm --test-mode

Warning: Failed...GDBus.Error:org.free.desktop...blah

Try installing MATE...

Fuck this...Make do with pi login for now to view FAware..

 

Pi3 Wifi Setup Problem – RESOLVED; group=netdev Fault?? Eh?

https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md

The Pi3 has wifi built in.

Interfaces:

stevee@pi3:~ $ ifconfig

wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether b8:27:eb:55:ce:f8 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

stevee@PI3:~ $ sudo iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: 00:50:7F:E6:D1:B8
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=70/70 Signal level=-23 dBm
Encryption key:on
ESSID:"DrayTek"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
18 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=0000000000000000
Extra: Last beacon: 90ms ago
IE: Unknown: 00074472617954656B
IE: Unknown: 010882848B961224486C
IE: Unknown: 030101
IE: Unknown: 2A0100
IE: Unknown: 32040C183060
IE: Unknown: 2D1A6E1017FFFFFF0001000000000000000000000000000000000000
IE: Unknown: 3D1601050600000000000000000000000000000000000000
IE: Unknown: 3E0100
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
IE: Unknown: 0B050002117A12
IE: Unknown: 7F0101
IE: Unknown: DD07000C4300000000
IE: Unknown: DD1E00904C336E1017FFFFFF0001000000000000000000000000000000000000
IE: Unknown: DD1A00904C3401050600000000000000000000000000000000000000
IE: Unknown: ......blah

stevee@pi3:~ $ wpa_passphrase "APname" "APs Password"

network={
ssid="APname"
#psk="APs Password"
psk=3b457ebcbf7c012ee3b9d4df783acedaf80565a1f7b131f5944aa3d1505c241e
}

stevee@pi3:~ $ sudo  wpa_passphrase "ap" "apPassword" >> /etc/wpa_supplicant/wpa_supplicant.conf

generates form:

network={
ssid="ap"
#psk="apPassword"
psk=xxxxxxxxxxxxxxxxxxxx
}

Hmm...appends of this form - like echo >> also - are not allowed in Raspbian now it seems, why not? Have to use vi instead - which you also can't copy and paste from now either as sudo over SSH - what are they doing to Linux??!!

What's in it after raspi-config wifi country legalities set?

 sudo vi /etc/wpa_supplicant/wpa_supplicant.conf

Adding

network={
ssid="ap"
#psk="apPassword"
psk=xxxxxxxxxxxxxxxxxxxx
}

should be all that's required for most unhidden WPA based home setups as the defaults for other options should not be required except for specific more secure AP settings!

"At this point, wpa-supplicant will normally notice within a few seconds that a change has occurred, and it will try and connect to the network. If it does not, restart the interface with sudo wpa_cli reconfigure."

stevee@pi3:~ $ sudo wpa_cli reconfigure
Selected interface 'p2p-dev-wlan0'

Hmm...or NOT....!

stevee@pi3:~ $ sudo dhclient -v wlan0
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/b8:27:eb:55:ce:f8
Sending on LPF/wlan0/b8:27:eb:55:ce:f8
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19

Not getting a DHCP offer....

Not a hardware issue because unit can scan the AP ok...

Check for firmware and update wireless-tools...

stevee@PI3:~ $ sudo rpi-update

stevee@PI3:~ $ sudo apt update && sudo apt upgrade
Hit:1 http://mirrordirector.raspbian.org/raspbian stretch InRelease
Hit:2 http://archive.raspberrypi.org/debian stretch InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

All good...the AP just wont hand out a DHCP address to this unit...

stevee@PI3:~ $ sudo wpa_cli reconfigure
Selected interface 'p2p-dev-wlan0'
OK

In term 1:

stevee@PI3:~ $ sudo dhclient wlan0

In term 2:

stevee@PI3:~ $ sudo tail -f /var/log/syslog

Oct 7 00:43:37 PI3 dhclient[1983]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
Oct 7 00:43:39 PI3 dhclient[1983]: No DHCPOFFERS received.
Oct 7 00:43:39 PI3 dhclient[1983]: No working leases in persistent database - sleeping.

Settings in router are all OK as laptop is connected for WPA/WPA2 and same password, and WPS is enabled...(the scanning for client requests)

AP seems unwilling/unable to give DHCP Addr - is laptop wifi interfering? Check with cable and wifi off...

nope, not interference...

Aah..on reboot:

Stopping Bluetooth service...

Is the pissing wifi for BTooth instead ?

stevee@PI3:~ $ sudo apt-get remove bluez

stevee@PI3:~ $ sudo apt autoremove

Nope!

stevee@PI3:~ $ sudo dhclient -v wlan0

Nope!

Add more relevant encryption info from:

stevee@PI3:~ $ sudo iwlist wlan0 scan

stevee@pi3:~ $ sudo vi /etc/wpa_supplicant/wpa_supplicant.conf

network={
ssid="ap"
#psk="apPassword"
psk=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

pairwise=TKIP CCMP

key_mgmt=WPA-PSK

proto=WPA

}

stevee@PI3:~ $ sudo dhclient -v wlan0

Nope!

Double check AP/password values:

stevee@PI3:~ $ sudo wpa_passphrase "DrayTek" "my_password"

Yep - correct.

WTF!!?

https://www.freebsd.org/cgi/man.cgi?wpa_supplicant.conf(5)

network={
parameter=value
...
}

ssid (required)
Network name (as announced by the access point). An ASCII or hex
string enclosed in quotation marks.

ssid="DrayTek"

Check!

psk WPA preshared key used in WPA-PSK mode. The key is specified as 64 hex digits or as an 8-63 character ASCII passphrase. ASCII passphrases are dynamically converted to a 256-bit key at runtime using the network SSID, or they can be statically converted at configuration time using the wpa_passphrase(8) utility.

psk=xxxxxxxxxxxx

Check!

scan_ssid
SSID scan technique; 0 (default) or 1. Technique 0 scans for the
SSID using a broadcast Probe Request frame while 1 uses a
directed Probe Request frame. Access points that cloak them-
selves by not broadcasting their SSID require technique 1, but
beware that this scheme can cause scanning to take longer to com-
plete.

scan_ssid=0

Check!

proto List of acceptable protocols; one or more of: WPA (IEEE
802.11i/D3.0) and RSN (IEEE 802.11i). WPA2 is another name for
RSN. If not set this defaults to "WPA RSN".

proto=WPA RSN

Check!

key_mgmt
List of acceptable key management protocols; one or more of:
WPA-PSK (WPA pre-shared key), WPA-EAP (WPA using EAP authentica-
tion), IEEE8021X (IEEE 802.1x using EAP authentication and,
optionally, dynamically generated WEP keys), NONE (plaintext or
static WEP keys). If not set this defaults to "WPA-PSK WPA-EAP".

key-mgmt=WPA-PSK

Check!

auth_alg List of allowed IEEE 802.11 authentication algorithms; one or more of: OPEN (Open System authentication, required for WPA/WPA2), SHARED (Shared Key authentication), LEAP (LEAP/Network EAP). If not set automatic selection is used (Open System with LEAP enabled if LEAP is allowed as one of the EAP methods).

Check!

EXAMPLE:

# allow frontend (e.g., wpa_cli) to be used by all users in 'wheel' group
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
#
# home network; allow all valid ciphers
network={
ssid="home"
scan_ssid=1
key_mgmt=WPA-PSK
psk="very secret passphrase"

}

Has to be another issue - fuck knows!

sudo reboot

stevee@PI3:~ $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.13 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::9cc1:262f:7fa0:eb0f prefixlen 64 scopeid 0x20<link>
ether b8:27:eb:00:9b:ad txqueuelen 1000 (Ethernet)
RX packets 84 bytes 13148 (12.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 93 bytes 14887 (14.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 4 bytes 240 (240.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4 bytes 240 (240.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether b8:27:eb:55:ce:f8 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Found this on the web and got:

stevee@pi3:~ $ sudo wpa_supplicant -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf & dhcpcd wlan0
[1] 1100
control_open: Permission denied
main: pidfile_lock: Permission denied
stevee@pi3:~ $ Successfully initialized wpa_supplicant
CTRL: Invalid group 'netdev update_config=1'
Failed to initialize control interface 'DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

nl80211: deinit ifname=wlan0 disabled_11b_rates=0

Seems the format of the wpa_supplicant.conf is wrong as it sees the group as

netdev update..

unseparated

CTRL: Invalid group 'netdev update_config=1'

stevee@pi3:~ $ sudo vi /etc/wpa_supplicant/wpa_supplicant.conf

#GROUP=netdev

Try only:

stevee@pi3:~ $ sudo wpa_supplicant -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf

Successfully initialized wpa_supplicant
p2p-dev-wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=GB
wlan0: Trying to associate with 00:50:7f:e6:d1:b8 (SSID='DrayTek' freq=2412 MHz)
wlan0: Associated with 00:50:7f:e6:d1:b8
wlan0: WPA: Key negotiation completed with 00:50:7f:e6:d1:b8 [PTK=CCMP GTK=TKIP]
wlan0: CTRL-EVENT-CONNECTED - Connection to 00:50:7f:e6:d1:b8 completed [id=0 id_str=]

Looks like the raspi-config additions for country etc. create invalid "netdev" line??

Just get an DHCP address now in other term...

stevee@pi3:~ $ sudo dhcpcd wlan0

sending commands to master dhcpcd process

stevee@pi3:~ $ ifconfig

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.6 netmask 255.255.255.0 broadcast 192.168.1.255

Fixed It!! RESOLVED!

Later, I also changed to a diff USB key, added minimal "network=" lines of

ssid= and psk=

to a default wpa_supplicant.conf

and did:

stevee@pi3:~ $ sudo wpa_cli reconfigure
Selected interface 'p2p-dev-wlan0'
'RECONFIGURE' command timed out.

Tried again and it connected...it got the IP address:

stevee@pi3:~ $ ifconfig

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.102.113 netmask 255.255.0.0 broadcast 169.254.255.255

seemingly from:

stevee@pi3:~ $ sudo vi /etc/networks

link-local   169.254.0.0

but later, tail showed it dumped it for a DHCP addr:

Oct 7 14:44:08 pi3 avahi-daemon[408]: New relevant interface wlan0.IPv4 for mDNS.

Oct 7 14:44:08 pi3 dhcpcd[612]: wlan0: adding route to 169.254.0.0/16
Oct 7 14:44:08 pi3 avahi-daemon[408]: Registering new address record for 169.254.102.113 on wlan0.IPv4.
Oct 7 14:47:49 pi3 dhcpcd[612]: eth0: Router Advertisement from fe80::250:7fff:fee6:d1b8
Oct 7 14:47:49 pi3 dhcpcd[612]: wlan0: Router Advertisement from fe80::250:7fff:fee6:d1b8
Oct 7 14:50:20 pi3 dhcpcd[612]: wlan0: offered 192.168.1.6 from 192.168.1.1
Oct 7 14:50:20 pi3 dhcpcd[612]: wlan0: probing address 192.168.1.6/24
Oct 7 14:50:26 pi3 dhcpcd[612]: wlan0: leased 192.168.1.6 for 28800 seconds
Oct 7 14:50:26 pi3 avahi-daemon[408]: Registering new address record for 192.168.1.6 on wlan0.IPv4.
Oct 7 14:50:26 pi3 dhcpcd[612]: wlan0: adding route to 192.168.1.0/24
Oct 7 14:50:26 pi3 dhcpcd[612]: wlan0: adding default route via 192.168.1.1
Oct 7 14:50:26 pi3 avahi-daemon[408]: Withdrawing address record for 169.254.102.113 on wlan0.
Oct 7 14:50:26 pi3 avahi-daemon[408]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 169.254.102.113.
Oct 7 14:50:26 pi3 dhcpcd[612]: wlan0: deleting route to 169.254.0.0/16
Oct 7 14:50:26 pi3 avahi-daemon[408]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.6.

stevee@pi3:~ $ ifconfig

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.6 netmask 255.255.255.0 broadcast 192.168.1.255

Conclusion:

Don't use raspi-config to set your country wifi settings! Or just comment out

#Group=netdev

in /etc/wpa_supplicant/wpa_supplicant.conf

For possible corruption, run fsck at reboot (now):

sudo shutdown -r -F now

Hahahahaha...dork!...also check your router doesn't have a limited amount of DHCP addresses for it's pool!! Like 15 in my case, so was on the limit for some requests at times depending on if my 8 hr leases expired in time too! I've got between 10 and 17 addresses used at any time...duh - now I've set pool to 20...dickhead...

See why I don't do IT now in my senility...?

Handy to know if wifi is off in BIOS or Fkey...

rfkill list
0: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no

Pi3 USB Boot Device with Picam Motion

Don't use

auto_brightness on

with the newer Motion! It pulses dark/light like the Pi2s with older motion can.

There are different terms for some of the same parameters in the newer Motion version conf, so older Pi2 conf files won't work and break motion if used. However, once identified by line comparison of the old to new, same settings for these newer terms can be used.

See my old Post:

https://www.stevepedwards.com/DebianAdmin/pi-with-motion-only-minimal-fresh-install-summary/

sudo apt-get install motion

Setting up motion (4.0-1) ...
Adding group `motion' (GID 115) ...
Done.
Warning: The home dir /var/lib/motion you specified already exists.
Adding system user `motion' (UID 109) ...
Adding new user `motion' (UID 109) with group `motion' ...
The home directory `/var/lib/motion' already exists. Not copying from `/etc/skel'.
adduser: Warning: The home directory `/var/lib/motion' does not belong to the user you are currently creating.
Adding user `motion' to group `video' ...
Adding user motion to group video
Done.
Setting up libavdevice57:armhf (7:3.2.5-1) ...
Setting up ffmpeg (7:3.2.5-1) ...
Processing triggers for libc-bin (2.24-11+deb9u1) ...
Processing triggers for systemd (232-25+deb9u1) ...

Note the info above for changes - first add stevee to motion group!

stevee@pi3:~ $ sudo adduser stevee motion
sudo: unable to resolve host pi3
Adding user `stevee' to group `motion' ...
Adding user stevee to group motion
Done.

Just turning the basic defaults on, what happens in the new version?

I enabled the camera in sudo raspi-config.

stevee@pi3:~ $ sudo vi /etc/motion/motion.conf

daemon on

stevee@pi3:~ $ sudo vi /etc/default/motion

start_motion_daemon=yes

stevee@pi3:~ $ sudo motion
sudo: unable to resolve host pi3
[0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion/motion.conf
[0:motion] [NTC] [ALL] motion_startup: Motion 4.0 Started
[0:motion] [NTC] [ALL] create_path: creating directory /var/log/motion
[0:motion] [NTC] [ALL] motion_startup: Logging to file (/var/log/motion/motion.log)

The default port is 8081 so try a browser view:

This site can’t be reached

192.168.1.13 refused to connect

Restrict stream for localhost only needs to be off in motion.conf:

stream_locahost off

stevee@pi3:~ $ sudo service motion restart

Broadcast message from systemd-journald@pi3 (Thu 2017-10-05 18:45:01 BST):

motion[2137]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied

Message from syslogd@pi3 at Oct 5 18:45:01 ...
motion: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied

Check if /var/log/motion/motion.log exists:

stevee@pi3:~ $ ls -l /var/log/motion/motion.log
-rw-r--r-- 1 root root 11839 Oct 5 18:45 /var/log/motion/motion.log

Allow motion ownership of it :

stevee@pi3:~ $ sudo chown motion /var/log/motion/motion.log
sudo: unable to resolve host pi3
stevee@pi3:~ $ ls -l /var/log/motion/motion.log
-rw-r--r-- 1 motion root 11839 Oct 5 18:45 /var/log/motion/motion.log

stevee@pi3:~ $ sudo service motion restart
sudo: unable to resolve host pi3

Root can run motion but user cannot;

stevee@pi3:~ $ motion
[0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion/motion.conf
[0:motion] [NTC] [ALL] motion_startup: Motion 4.0 Started
[0:motion] [ERR] [ALL] myfopen: Error opening file /var/log/motion/motion.log with mode a: Permission denied
[0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied

Broadcast message from systemd-journald@pi3 (Thu 2017-10-05 19:35:41 BST):

motion[2736]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied

stevee@pi3:~ $ ls -l /var/log/motion/motion.log
-rw-r--r-- 1 motion root 13687 Oct 5 19:34 /var/log/motion/motion.log

motion group setting needs 775 for user and group access to write to log:

stevee@pi3:~ $ sudo chmod 775 /var/log/motion/motion.log
sudo: unable to resolve host pi3

Message from syslogd@pi3 at Oct 5 19:35:41 ...
motion: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied

Check camera is working:

stevee@pi3:~ $ sudo raspivid -o test.h264
sudo: unable to resolve host pi3

Camera flashed up on HDMI TV so is ok.

Check playback of file:

stevee@pi3:~ $ sudo apt-get install omxplayer

stevee@pi3:~ $ sudo omxplayer test.h264

Views on TV ok.

BUT user cannot access camera:

stevee@pi3:~ $ raspivid -o test.h264
* failed to open vchiq instance

stevee@pi3:~ $ sudo chmod 777 /dev/vchiq
sudo: unable to resolve host pi3
stevee@pi3:~ $ raspivid -o test.h264
mmal: main: Error opening output file: test.h264
No output file will be generated

That's because it can't overwrite root's prior file - but camera showed on TV so user can use it.

stevee@pi3:~ $ rm test.h264
rm: remove write-protected regular file 'test.h264'?

Now user can make and view test file.

stevee@pi3:~ $ nmap 127.0.0.1

Starting Nmap 7.40 ( https://nmap.org ) at 2017-10-05 19:17 BST
Nmap scan report for localhost (127.0.0.1)
Host is up (0.00031s latency).
Not shown: 997 closed ports
PORT STATE SERVICE
22/tcp open ssh
139/tcp open netbios-ssn
445/tcp open microsoft-ds

8080/tcp open http-proxy
8081/tcp open blackice-icecap

Now the webserver is running but no camera image in browser as driver is not loaded.

stevee@pi3:~ $ sudo modprobe bcm2835-v4l2

stevee@pi3:~ $ lsmod | grep v4l
bcm2835_v4l2 44759 1
videobuf2_vmalloc 5920 1 bcm2835_v4l2
videobuf2_v4l2 17077 1 bcm2835_v4l2
videobuf2_core 34083 2 bcm2835_v4l2,videobuf2_v4l2
v4l2_common 6284 1 bcm2835_v4l2
videodev 184712 5 v4l2_common,videobuf2_core,bcm2835_v4l2,videobuf2_v4l2

Add "bcm2835_v4l2" to modules to load at boot:

sudo vi /etc/modules

stevee@pi3:~ $ sudo service motion restart

Working!

Set to run at boot:

stevee@pi3:~ $ sudo update-rc.d motion enable

Now you can tweak the conf details to suit your view resolution (960,720 etc), net shares, video access, jpg removal as in prior Post etc.

To Compare Old Confs With New

copy the newer tweaked motion.conf to my laptop I need to setup the samba share anyway for video access:

sudo vi /etc/samba/smb.conf (set homes section for shares and access perms; add [Share] section):
[Share]
path = /Share
writable = 1
browsable = 1
sudo mkdir /Share/ (folder for net access and motion vids)
sudo mkdir /Share/motion (folder for motion vid creation set in motion.conf)
sudo chown stevee.motion /Share/ -R (main net access user/owner and group)
sudo chmod 775 -R /Share/ (allows access to user stevee and his group, traversal for others)
sudo service samba restart (get changes read)

sudo smbpasswd -a stevee
New SMB password:
Retype new SMB password:
Added user stevee.

Now I can export the conf file to this directory and copy it to my laptop home dir:

stevee@pi3:~ $ sudo cp -v /etc/motion/motion.conf /Share/
'/etc/motion/motion.conf' -> '/Share/motion.conf'

Diffs between my old motion.conf files compared to the tweaked new Pi3 conf file are:

stevee@AMDA8 ~/Documents $ grep -Ev '^#|^$' motiongate.conf > gate.txt
stevee@AMDA8 ~/Documents $ grep -Ev '^#|^$' motionpi3.conf > pi3.txt
stevee@AMDA8 ~/Documents $ diff gate.txt pi3.txt

The left chevrons are Pi2 and right chevrons are Pi3 lines:
2c2
< process_id_file /var/run/motion/motion.pid
---
> process_id_file /var/run/motion/motion.pid
3a4,6
> logfile /var/log/motion/motion.log
> log_level 6
> log_type all
5c8
< v4l2_palette 8
---
> v4l2_palette 17
7,8c10
< / The video input to be used (default: 8)
< input 8
---
> input -1
10a13
> power_line_frequency -1
15a19,26
> ; netcam_url value
> ; netcam_userpass value
> netcam_keepalive off
> ; netcam_proxy value
> netcam_tolerant_check off
> rtsp_uses_tcp on
> ; mmalcam_name vc.ril.camera
> ; mmalcam_control_params -hf
20a32,34
> roundrobin_frames 1
> roundrobin_skip 1
> switchfilter off
25,26c39,40
< despeckle EedDl
< area_detect 12345679
---
> despeckle_filter EedDl
> ; area_detect value
33,39c47,51
< gap 60
< max_mpeg_time 0
< output_all off
< area_detect 12345679
< ; mask_file value
< output_normal first
< output_motion off
---
> event_gap 60
> max_movie_time 0
> emulate_motion off
> output_pictures on
> output_debug_pictures off
41,43c53,55
< ppm off
< ffmpeg_cap_new on
< ffmpeg_cap_motion off
---
> picture_type jpeg
> ffmpeg_output_movies on
> ffmpeg_output_debug_movies off
46c58
< ffmpeg_bps 500000
---
> ffmpeg_bps 400000
49c61,66
< ffmpeg_deinterlace off
---
> ffmpeg_duplicate_frames true
> use_extpipe off
> ;extpipe mencoder -demuxer rawvideo -rawvideo w=%w:h=%h:i420 -ovc x264 -x264encopts bframes=4:frameref=1:subq=1:scenecut=-1:nob_adapt:threads=1:keyint=1000:8x8dct:vbv_bufsize=4000:crf=24:partitions=i8x8,i4x4:vbv_maxrate=800:no-chroma-me -vf denoise3d=16:12:48:4,pp=lb -of avi -o %f.avi - -fps %fps
> ;extpipe x264 - --input-res %wx%h --fps %fps --bitrate 2000 --preset ultrafast --quiet -o %f.mp4
> ;extpipe mencoder -demuxer rawvideo -rawvideo w=%w:h=%h:fps=%fps -ovc x264 -x264encopts preset=ultrafast -of lavf -o %f.mp4 - -fps %fps
> ;extpipe ffmpeg -y -f rawvideo -pix_fmt yuv420p -video_size %wx%h -framerate %fps -i pipe:0 -vcodec libx264 -preset ultrafast -f mp4 %f.mp4
51c68,69
< locate off
---
> locate_motion_mode off
> locate_motion_style box
53c71
< text_left GATE
---
> text_left PI3
56,60c74,79
< text_double on
< target_dir /Share/motion
< ;snapshot_filename %v-%Y%m%d%H%M%S-snapshot
< ;jpeg_filename %v-%Y%m%d%H%M%S-%q
< movie_filename %v-%Hhr%Mmins_%Ssecs_%d_%m_%Y
---
> text_double off
> ;exif_text %i%J/%K%L
> target_dir /var/lib/motion
> snapshot_filename %v-%Y%m%d%H%M%S-snapshot
> picture_filename %v-%Y%m%d%H%M%S-%q
> movie_filename %v-%Y%m%d%H%M%S
62,71c81,95
< webcam_port 8081
< webcam_quality 50
< webcam_motion on
< webcam_maxrate 5
< webcam_localhost off
< webcam_limit 0
< control_port 8080
< control_localhost off
< control_html_output on
< ; control_authentication username:password
---
> ipv6_enabled off
> stream_port 8081
> stream_quality 50
> stream_motion on
> stream_maxrate 1
> stream_localhost off
> stream_limit 0
> stream_auth_method 0
> ; stream_authentication username:password
> ; stream_preview_scale 25
> ; stream_preview_newline no
> webcontrol_port 8080
> webcontrol_localhost on
> webcontrol_html_output on
> ; webcontrol_authentication username:password
74,78c98,108
< ; track_port value
< track_motorx 0
< track_motory 0
< track_maxx 0
< track_maxy 0
---
> ;track_port /dev/ttyS0
> ;track_motorx 0
> ;track_motorx_reverse 0
> ;track_motory 1
> ;track_motory_reverse 0
> ;track_maxx 200
> ;track_minx 50
> ;track_maxy 200
> ;track_miny 50
> ;track_homex 128
> ;track_homey 128
87c117
< ; on_event_end rm -vr --i=no /Share/motion/*jpg
---
> ; on_event_end value
92,97c122,142
< on_movie_end rm -vr /Share/motion/*jpg --i=no
< on_camera_lost reboot
< ; thread /usr/local/etc/thread1.conf
< ; thread /usr/local/etc/thread2.conf
< ; thread /usr/local/etc/thread3.conf
< ; thread /usr/local/etc/thread4.conf
---
> ; on_movie_end value
> ; on_camera_lost value
> ; sql_log_picture on
> ; sql_log_snapshot on
> ; sql_log_movie off
> ; sql_log_timelapse off
> ; sql_query insert into security(camera, filename, frame, file_type, time_stamp, event_time_stamp) values('%t', '%f', '%q', '%n', '%Y-%m-%d %T', '%C')
> ; database_type value
> ; database_dbname value
> ; database_host value
> ; database_user value
> ; database_password value
> ; database_port value
> ; database_busy_timeout 0
> ; video_pipe value
> ; motion_video_pipe value
> ; camera /etc/motion/camera1.conf
> ; camera /etc/motion/camera2.conf
> ; camera /etc/motion/camera3.conf
> ; camera /etc/motion/camera4.conf
> ; camera_dir /etc/motion/conf.d

Just need to add those BOLD relevant settings from pigate.txt to the pi3 motion.conf, such as:

 on_movie_end rm -vr --i=no /Share/motion/*jpg

to remove the jpgs from the movie folder etc. at movie creation end and change the default target_dir directory to my Share:

target_dir /var/lib/motion

to

target_dir /Share/motion

I already changed the resolution from width/height 320/240 to 960/720...that's about it.

As you can see, most of the steps in my prior Post setup are the same.

The main one disallowed is echoing the driver into /etc/modules - it had to be added by vim for some reason...?

In future, remember that enabling the camera in raspi-conf doesn't load a v4l driver for motion!

If you wish to save the working image to a 2nd USB plugged into the Pi, Raspian dd now has a:

sudo dd if=/dev/sda of=/dev/sdb status=progress

option

My working Pi3 Motion conf is here:

Pi3working.txt

stevee@pi3:~ $ sudo grep -Ev "^[#;]|^$" /etc/motion/motion.conf

daemon on
process_id_file /var/run/motion/motion.pid
setup_mode off
logfile /var/log/motion/motion.log
log_level 6
log_type all
videodevice /dev/video0
v4l2_palette 17
input -1
norm 0
frequency 0
power_line_frequency 1
rotate 0
width 960
height 720
framerate 100
minimum_frame_time 0
netcam_keepalive off
netcam_tolerant_check off
rtsp_uses_tcp on
auto_brightness off
brightness 0
contrast 0
saturation 0
hue 0
roundrobin_frames 1
roundrobin_skip 1
switchfilter off
threshold 10000
threshold_tune off
noise_level 32
noise_tune on
despeckle_filter EedDl
smart_mask_speed 0
lightswitch 0
minimum_motion_frames 5
pre_capture 0
post_capture 10
event_gap 60
max_movie_time 0
emulate_motion off
output_pictures on
output_debug_pictures off
quality 75
picture_type jpeg
ffmpeg_output_movies on
ffmpeg_output_debug_movies off
ffmpeg_timelapse 0
ffmpeg_timelapse_mode daily
ffmpeg_bps 500000
ffmpeg_variable_bitrate 0
ffmpeg_video_codec mpeg4
ffmpeg_duplicate_frames true
use_extpipe off
snapshot_interval 0
locate_motion_mode off
locate_motion_style box
text_right %Y-%m-%d\n%T-%q
text_left PI3
text_changes off
text_event %Y%m%d%H%M%S
text_double on
target_dir /Share/motion
movie_filename %v-%Hhr%Mmins_%Ssecs_%d_%m_%Y
timelapse_filename %Y%m%d-timelapse
ipv6_enabled off
stream_port 8081
stream_quality 50
stream_motion on
stream_maxrate 5
stream_localhost off
stream_limit 0
stream_auth_method 0
webcontrol_port 8080
webcontrol_localhost on
webcontrol_html_output on
track_type 0
track_auto off
track_iomojo_id 0
track_step_angle_x 10
track_step_angle_y 10
track_move_wait 10
track_speed 255
track_stepsize 40
quiet on
on_movie_end rm -vr --i=no /Share/motion/*jpg
on_camera_lost reboot

Also - to get rid of sudo: unable to resolve host PI3

sudo vi /etc/hosts

127.0.1.1 PI3

Booting a Pi3 from USB3 Devices

This process is really easy now with the latest Raspian image - depending if your USB device make/model works:

Raspbian

The two USB3 devices which worked for me are these (Integral 16GB NOT the 8GB! That did not work):

stevee@AMDA8:~ $ lsusb
Bus 001 Device 004: ID 0781:5583 SanDisk Corp. (Sandisk Ultrafit 16GB)

Bus 004 Device 002: ID 26bd:9917  (this 16GB Integral is very fast and cheap!!)

Right click the Raspbian image for the Disk Image Writer in Mint and write to your USB device:

This image should already contain the newer bootcode.bin file in /boot and the Pi3 should already have it's OTP flash burned for USB boot or SD card as shown if already booted to SD card by:

stevee@RASPBERRYPI:~ $ sudo vcgencmd otp_dump | grep 17:
[sudo] password for stevee:
17:3020000a

If this number is different then the OTP is not flashed yet and you can try:

sudo BRANCH=next rpi-update

and/or add the latest bootcode.bin file to /boot:

wget https://github.com/raspberrypi/firmware/raw/next/boot/bootcode.bin

On your laptop, check the boot flag of the boot partition has been set - probably easiest with cfdisk:

stevee@AMDA8 ~ $ sudo cfdisk /dev/sdb

No! It hasn't. Change that with Bootable for VFAT; write; YES.

Check the partition has been resized to full - if not, you can resize it now with Gparted/other or do it later in the Pi with parted:

the other things you may want to do to your USB image is add SSH as raspi-conf does not control this now after first Pi boot up - you add a file called ssh to /boot once your image is burned, and remounted:

or if mounted under your user on your laptop:

stevee@AMDA8 ~ $ touch /media/stevee/boot/ssh

Safely unmount the USB stick and try it in your Pi3, removing any SD card first, and allowing up to 30 secs or more (device dependent) for it to see the device and start booting if it is compatible (e.g. silver Kingston DataTraveler 2.0 (PMAP) is not - or a prior GPT partition on the device is causing problems, say from a prior Mint image install with USB Writer??).

I say that because my Integral 16GB worked fine but the 8GB version did not..?!

It may be better to write a completely new partition table with Gparted and create a full size ext 4 formatted partition on any USB stick first, then write the image.

If you still have problems booting it you can research other issues like USB timeout etc. but I would try different USB devices first for what works.

On the Pi, once logged in as user pi, pw raspberry, get the small font size fixed on HDMI TV:

sudo dpkg-reconfigure console-setup

change the pi pword, then setup your user etc.

sudo adduser stevee

sudo adduser stevee sudo

find it's IP address:

stevee@RASPBERRYPI:~ $ ifconfig

Update the repo info:

stevee@RASPBERRYPI:~ $  sudo apt-get update

USB3 is faster and more durable than SD cards once booted, and can handle re-writes without failure better.

Add any other apps you want for now...or just check ssh is working locally - if so access remotely and do it from there...

stevee@RASPBERRYPI:~ $ ssh 127.0.0.1

The authenticity of host '127.0.0.1 (127.0.0.1)' can't be established.
ECDSA key fingerprint is ....
Are you sure you want to continue connecting (yes/no)?

Yep SSH works so that ssh file in /boot does the trick.

Log in remotely from laptop:

stevee@RASPBERRYPI:~ $ sudo apt-get install nmap samba vim nbtscan winbind

sudo vi /etc/nsswitch.conf

add wins to line as usual.

hosts: files wins

stevee@RASPBERRYPI:~ $ nbtscan 192.168.1.0/24

192.168.1.0 Sendto failed: Permission denied
192.168.1.3 PIROAD <server> PIINTEG3 00:00:00:00:00:00
192.168.1.4 PIGATE <server> PIGATE 00:00:00:00:00:00

Change the hostname if you want and reboot.

stevee@raspberrypi:~ $ sudo vi /etc/hostname

Add passwordless login from your laptop to new Pi3 device name pi3:

stevee@AMDA8 ~ $ ssh-copy-id -i ~/.ssh/id_rsa.pub PI3

The authenticity of host 'pi3 (192.168.1.13)' can't be established.
ECDSA key fingerprint is 58:de:82:aa:b6:20:53:2d:54:8c:46:3c:87:2f:ed:0c.
Are you sure you want to continue connecting (yes/no)?

Log in via SSH.

Check the partition sizes have been expanded fully:

stevee@pi3:~ $ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 15G 1.2G 13G 9% /
devtmpfs 458M 0 458M 0% /dev
tmpfs 462M 0 462M 0% /dev/shm
tmpfs 462M 6.4M 456M 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 462M 0 462M 0% /sys/fs/cgroup
/dev/sda1 42M 21M 21M 51% /boot
tmpfs 93M 0 93M 0% /run/user/1001

Seems so...

stevee@pi3:~ $ sudo cfdisk /dev/sda

Device Boot Start End Sectors Size Id Type
>> Free space 2048 8191 6144 3M
/dev/sda1 * 8192 93813 85622 41.8M c W95 FAT32 (LBA)
/dev/sda2 94208 30031249 29937042 14.3G 83 Linux

If you want a desktop at boot, there is now a better linux one than the old Pi2s.

sudo apt-get install lightdm parted

(ha! well, would be if you could log in to it!)

To setup a Picam there are some changes from my old method here:

https://www.stevepedwards.com/DebianAdmin/pi-with-motion-only-minimal-fresh-install-summary/

but you can follow it and should be able to work out what is required from the screen output, such as permissions, and changes to the newer Motion motion.conf file that is NOT backwards compatible with the Pi2 version, by comparing an older Pi2 conf file with the new default one as some same functions have been renamed for later Motion versions. I got mine working ok, even with rpi-update firmware and apt-get upgrade.

I'll probably do a Post on it next...

WordPress Upload Limit – .user.ini

Using .user.ini

If that method still isn’t working for you, you may have another option. This will only work if you are using a version of PHP 5. Otherwise, you can skip this section.

Create a new file, and this time call it “.user.ini”. In that file, paste the following code:

upload_max_filesize = 64M
post_max_size = 64M
memory_limit = 64M
max_execution_time = 300

You can change the value of 64M to match your new desired upload limit. Save this file, and then drag it into the directory of your WordPress install using FTP. If you have the ability to restart your server, you should do so. The changes may take a bit to take effect, but go to Media -> Add New to confirm.

ripper x

sudo apt install ripperx lame

Final IT Post – I am now out of Pro IT for good

There will be no more Posts for this site (except odd home related stuff) as I am now out of Pro IT as a future job for good, for physical and mental health reasons...

I am now rebuilding myself with what I have left, with Chinese medicine, Qigong and Taiji - 25 years overdue from various back injuries, repetitive strain, eye strain, migraines, lack of exercise, and ridiculous levels of responsibility and knowledge expected for paltry £9/hr IT roles here in Cornwall etc...

If you are in IT or any sedentary office job, get regular exercise or suffer future back problems, stress related or obesity issues - or worse...

 

Microsoft, Not You, Now Owns Your Laptop via W10! Install Mint Anyway Despite the Deliberate W10 Designed Problems

As predicted in the prior w10 rant when w10 blocked my BIOS laptop keys via the soft power off function, (hidden in Power Button options, "other settings usually unavailable" - how deliberately cryptic and misleading is that!?) I said it would eventually remove BIOS and Boot Menu key access completely to stop people booting to any other OS like Linux - and now it has! Saw it last week for the first time.

A client who never uses his £300 Acer V5, because he hates w10 so much he can't face trying to use it, asked me to install Mint on it - but I would not - even by unticking the power button soft power on options, removing the battery, draining the CMOS and rebooting, (without more hassle, like taking the laptop apart to access the hard drive for install on another system, as this locked down Acer shit has no drive access panel - you have to remove the whole back), which I was not prepared to do for his financial sake, so I suggested selling it as a w10 laptop on Ebay, as it is a 2015, vgc laptop that cost £300 new.

I said he would be better off getting £150 or so on Ebay for it (he was prepared to take less to get rid of the shit!!) and buying a cheaper laptop like a nice, fast, ex Vista, HP 7630B with 2GB+ RAM, that runs Mint like lightning, now that his is "owned" by MS.

The problem was that NONE of the BIOS keys - F2, F12 etc. - will allow BIOS access, or if you DO get the boot menu by rapidly running your thumb across all buttons to be sure of hitting something in time before it boots to w10 - it STILL ignored the menu option for the USB boot device for the Linux install and booted w10 anyway!!

I also saw the first "pop up advert" in the OS on this machine taking up about 1/4 of the bottom right of screen!!

Employers will love that eh?? Staff getting distracted from work, on slow enough w10 shit already, without that also...good luck....

You don't own your machine any more! MS do.

Next predictions?

I think they will automatically format any USB stick or folder that contains any linux OS if it is inserted into a w10 machine or downloaded to it, and eventually rootkit your linux based router OS so that access is always available so you cannot firewall Windows data traffic such as NSA/CIA/MS/3rd party IP addresses (if you could even ID them!) that w10 sends data to.

Why do you think they are keen to get into the OSource arena as Platinum partners? They will learn a lot about OS code and pick brains no doubt. If they were genuine about becoming more open about OSource collaboration, why are they locking you out of your own systems to prevent you using anything else or prevent you sticking with w7 or win8 and forcing an upgrade to w10 eventually by over-riding the auto updates?

I warned you "free w10 is not free"...Foolish Mortals...!

Also, bear in mind that if you have web access via a Pay As You Go G4 phone access dongle - YOU are paying for all "behind the scenes" MS download data transfer also - if you were wondering why you have no credit left when you left the dongle in the laptop and had only surfed for 5 mins yourself - even if "shutdown" which it doesn't, as it sleeps only, by default...

It ate all my friend's credit on her 3 network dongle when she said she had hardly used it for herself...not only does it do nothing to help you as a buyer/user by using most of the system resources for its own purposes as a priority (why it's still slow as shit on really high spec kit like i7s), it spends your money also!!

And you think this is not malware????? There have already been law suits for lost data (w10 removing software it doesn't deem ok to share a PC with etc.). This can break businesses for Christ's sake!! What if it removes an App that a biz relies to function??? Unbelievable!

Don't complain to me about having problems if you use this MS shit when you could use Linux instead...

Boycott these in bed manufactures like Acer that comply with MS rules by taking the MS bribe, allowing BIOS to be locked out, and making hard drive access difficult with no access panels - start demanding manufacturers sell hardware with NO OS so YOU can install what YOU want on it, or buy linux machines to force software writers to port code for linux at the same time they write for MS - drivers included.

You are paying extra for w10 on systems also - which pays the manufacturers hardware bribe, to ultimately give MS your machine and have an OS you don't even want or like, that spies on you amongst many other things, and runs like crap - it's madness!

https://www.gnu.org/proprietary/malware-microsoft.en.html

So how DO you install Mint on a w10 laptop that has hidden the w10 drive AND all the other spare drives that you had as backup disks - to make life as difficult as possible to do what YOU want on YOUR PC?

Win10 puts small hidden FAT32 or GPT partitions at the front of the system AND any seperate backup drives now, so that if you start a linux install you won't see the "install Mint alongside w10" option anymore, as if w10 does not exist on the PC OR any of the spare drives as options to install to! Bastards!

You may think this is fine, but if you go ahead with the install by using the "erase disk and install Mint", Mint overwrites the only available, visible (to the Installer) w10 partitions with Mint, but because there is a hidden FAT/GPT partition at the front of the drive which Mint cannot see so cannot delete and format, this remains as the partition that gets booted to on restart, but because w10 is now deleted - that the hidden partition points to - it states that "No Drive Present"!

So now you have neither w10 OR Mint available!!

This is designed to freak people out deliberately and make it seem like the Linux install broke your PC - which it hasn't...

I'll add pics soon to clarify but I don't have a w10 laptop to show you of my own right now (wonder why?).

Grub did not get installed at the MBR because the hidden partition is already there - again - all designed to make your life difficult and think linux is the cause, and you have now irreparably broken your PC and are left with nothing, and panic and probably try to re-install w10 again in illogical desperation...I told you they are devious bastards...

If you start the Mint install boot process again from the USB drive and use Gparted all will become clear: the prior w10 drive will have the small w10 hidden partition at the start, with the linux install after it on ext4 and swap partitions.

As you have now lost w10 anyway as Mint installed over it, it's best to delete all the drive partitions from scratch, recreate a new full drive partition, format it to ext4 - all using Gparted - then Apply Changes and re-run the Mint install again for the Installer to auto partition it for itself.

Grub will now be installed in the MBR as usual and Mint will be available, soon w10 will be a forgotten nightmare and all will be ok in the world...until they hatch their next evil plan at least..

Another thing to be aware of is "special options" for hardware in the BIOS like Mouse Pad complexity - this may make it seem that your mouse pad does not work when testing Mint in live USB test mode before installing fully, but if you set the pad BIOS option back to "legacy" then the generic linux mouse pad driver should work.

Again  - designed to make people think that their hardware won't work with linux, only fully with w10, so put them off installing linux permanently.