EFI ng Arch install ??

[securitybreach]

Thinking about permissions I recall that I found this command in the wiki. Something to do with sudo I think but I can not find the page again. The advice was if having problems with permissions do so, so I did.

 

chown -c root:root: /etc/sudoers
chown -c 0440 /etc/sudoers

 

Maybe that has something to do with the gremlins.

 

If I had to guess, that would be the major cause of your issues.

[abarbarian]

Yeah but you shouldn't have to mess with permissions on a fresh install.

 

May be that should read " on a NORMAL fresh install"

 

So what do I replace 0440 with to take it back to as it should be. I can do that right.

 

Bed time for this tired old git. Sees ya.

Edited February 8, 2016 by abarbarian

[securitybreach]

Well the permissions should be as follows:

comhack@Cerberus ~ % ls -la /etc/sudoers
-r--r----- 1 root root 2903 Jan 14  2015 /etc/sudoers

[abarbarian]

Thanks for the info.

 

Yesterday I threw my dummy out of the pram and uninstalled sudo. Today I was looking for a sudoers file with,

 

ls -l /etc

 

and could not find one. So I reinstalled sudo and now I have a sudoers with the same permissions as yours. All well and good as it seems to have fixed some stuff. Yesterday I installed "zim" but could not start it but now I can. Progress----hurray.

An also the "locale" command now produces what looks like a correct output,

 

[root@longship etc]# locale
LANG=en_GB.UTF-8
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=
[root@longship etc]# locale -a
C
en_GB
en_GB.iso88591
en_GB.utf8
POSIX

 

 

I still have some problems though so too early to celebrate

 

Mind you lubrication is always a good thing

[securitybreach]

Great

[abarbarian]

I tried to look at systemd's journal to see what I could see.

 

[root@longship bloodaxe]# journalctl -xe

[color=#800080]Feb 08 16:01:29 longship systemd[1]: display-manager.service: Cannot add dependency job, ignoring: Unit display-manager.service failed to load[/color]

-- The start-up result is done.
Feb 08 16:01:30 longship systemd-udevd[261]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90001, key code 221): Invalid argument
Feb 08 16:01:30 longship systemd-udevd[261]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90002, key code 171): Invalid argument
Feb 08 16:01:30 longship systemd-udevd[261]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90003, key code 219): Invalid argument
Feb 08 16:01:30 longship systemd-udevd[261]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90004, key code 148): Invalid argument
Feb 08 16:01:30 longship systemd-udevd[261]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 149): Invalid argument
Feb 08 16:01:30 longship systemd-udevd[261]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0xc0183, key code 226): Invalid argument
Feb 08 16:01:30 longship systemd[1]: Reached target Basic System.
-- Subject: Unit basic.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel


-- The start-up result is done.
[color=#800080]Feb 08 16:01:30 longship kernel: snd_hda_intel 0000:00:1f.3: failed to add i915 component master (-19)[/color]
Feb 08 16:01:30 longship systemd[1]: Starting Login Service...
-- Subject: Unit systemd-logind.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- The start-up result is done.
Feb 08 16:05:09 longship systemd[490]: Failed to register Released match on system bus: Operation not permitted
Feb 08 16:05:09 longship dbus-daemon[542]: Successfully activated service 'org.freedesktop.systemd1'
Feb 08 16:06:03 longship sudo[559]: bloodaxe : unable to stat /etc/sudoers : Permission denied ; TTY=pts/1 ; PWD=/home/bloodaxe ;
Feb 08 16:08:22 longship sudo[794]: bloodaxe : unable to stat /etc/sudoers : Permission denied ; TTY=pts/1 ; PWD=/tmp/trizen-bloodaxe/rage ;
Feb 08 16:08:40 longship dbus-daemon[542]: Activating service name='org.a11y.Bus'
Feb 08 16:08:40 longship dbus-daemon[542]: Successfully activated service 'org.a11y.Bus'
Feb 08 16:16:30 longship systemd[1]: Starting Cleanup of Temporary Directories...
-- Subject: Unit systemd-tmpfiles-clean.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel


-- The start-up result is done.
Feb 08 16:24:49 longship org.a11y.Bus[542]: Activating service name='org.a11y.atspi.Registry'
Feb 08 16:24:49 longship org.a11y.Bus[542]: Successfully activated service 'org.a11y.atspi.Registry'
Feb 08 16:24:49 longship org.a11y.atspi.Registry[993]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Feb 08 17:38:05 longship su[1030]: (to root) bloodaxe on pts/1
Feb 08 17:38:05 longship su[1030]: pam_unix(su:session): session opened for user root by bloodaxe(uid=1000)
Feb 08 17:53:38 longship dbus-daemon[380]: Unable to reload configuration: Failed to open "/usr/share/dbus-1/system.conf": Permission denied
Feb 08 17:53:38 longship dbus-daemon[380]: Unable to reload configuration: Failed to open "/usr/share/dbus-1/system.conf": Permission denied
Feb 08 17:53:38 longship dbus-daemon[542]: Reloaded configuration
Feb 08 17:53:38 longship dbus-daemon[380]: Unable to reload configuration: Failed to open "/usr/share/dbus-1/system.conf": Permission denied
Feb 08 17:53:38 longship dbus-daemon[380]: Unable to reload configuration: Failed to open "/usr/share/dbus-1/system.conf": Permission denied
Feb 08 17:53:38 longship dbus-daemon[380]: Unable to reload configuration: Failed to open "/usr/share/dbus-1/system.conf": Permission denied
Feb 08 17:53:38 longship dbus-daemon[380]: Unable to reload configuration: Failed to open "/usr/share/dbus-1/system.conf": Permission denied
[color=#800080]Feb 08 17:53:38 longship systemd[1]: Reexecuting.[/color]
Feb 08 17:53:38 longship systemd[1]: systemd 228 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
Feb 08 17:53:38 longship systemd[1]: Detected architecture x86-64.
Feb 08 17:53:38 longship systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.login1': Operation not permitted
Feb 08 17:53:38 longship systemd[1]: Failed to subscribe to activation signal: Operation not permitted
Feb 08 17:53:38 longship systemd[1]: Failed to register name: Operation not permitted
Feb 08 17:53:38 longship systemd[1]: Failed to set up API bus: Operation not permitted
Feb 08 17:53:56 longship sudo[1139]:	 root : unable to stat /etc/sudoers : Permission denied ; TTY=pts/1 ; PWD=/home/bloodaxe ;
Feb 08 18:13:41 longship su[1172]: (to root) bloodaxe on pts/2
Feb 08 18:13:41 longship su[1172]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 08 18:17:58 longship su[1172]: pam_unix(su:session): session closed for user root
Feb 08 18:20:12 longship su[1030]: pam_unix(su:session): session closed for user root
Feb 08 18:20:46 longship su[1225]: (to root) bloodaxe on pts/1
Feb 08 18:20:46 longship su[1225]: pam_unix(su:session): session opened for user root by bloodaxe(uid=1000)


[bloodaxe@longship ~]$ systemctl staus display-manager.service
Unknown operation staus.
[bloodaxe@longship ~]$ systemctl status display-manager.service
Failed to get properties: Access denied
[bloodaxe@longship ~]$ systemctl start display-manager.service
[color=#ff0000]Error getting authority: Error initializing authority: Exhausted all available authentication mechanisms (tried: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS) (available: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS) (g-io-error-quark, 0)
Could not watch jobs: Operation not permitted[/color]

 

I keep getting the warning in red all over the place. Purple highlights are ones I need to look at sometime.

 

Looks to me that display-manager.service is not setting up properly. I'll have a go at re-installing xorg stuff and see awhat happens.

[ebrke]

Whew. I've been following this thread being very grateful it was not me going through this. Glad you've had some success.

[abarbarian]

Whew. I've been following this thread being very grateful it was not me going through this. Glad you've had some success.

 

Yeah I am just about ready to throw in the towel. Seems nobody on the net has any ideas either. I'll just have to do a quick and dirty install of Robolinux or set up the spare pc again. :'(

[securitybreach]

Why not simply install Archlinux again or use an installer if you dont want to take the time? http://sourceforge.n...rchitect-linux/

[abarbarian]

Why not simply install Archlinux again or use an installer if you dont want to take the time? http://sourceforge.n...rchitect-linux/

 

First part of your Q,

 

Is a long tale and I don't have time to answer fully. Lets just say it is complicated and I have been hit by the gremlins that have been haunting me all year.

 

Part two of your Q,

 

Reasons to be cheerfull, one two three,

 

1) Arch should be fixable if it is half running like mine.

 

2) If I could install and fix as I did several years ago I should be able to make this set up work.

 

3) Architect only has grub and syslinux according to the guide I read.

 

4) I need a second pc running to do an install and my second screen is over the other side of the room and I am sick of running across the room to read the wiki.

 

5) I hate to be beaten by inanimate objects, they should do as they are told.

 

[abarbarian]

So here I am on my ninth try of installing Arch and getting really frustrated and ever so slightly angry,despondent with a growing feeling of uselessness.

 

I gave up having root, var and home on different partitions and on my last try used root and home only. Initially things looked better instead of loads of permissions errors when initially installing I now have only one error,

 

[2016-02-13 13:22] [PACMAN] Running 'pacman -r /mnt -Sy --cachedir=/mnt/var/cache/pacman/pkg base base-devel refind-efi'
[2016-02-13 13:22] [PACMAN] synchronizing package lists
[2016-02-13 13:44] [ALPM] transaction started
[2016-02-13 13:44] [ALPM] installed linux-api-headers (4.1.4-1)
[2016-02-13 13:44] [ALPM] installed tzdata (2016a-1)
[2016-02-13 13:44] [ALPM] installed iana-etc (20151016-1)
[2016-02-13 13:44] [ALPM] warning: directory permissions differ on /mnt/home/
filesystem: 700 package: 755
[2016-02-13 13:44] [ALPM] installed filesystem (2015.09-1)
[2016-02-13 13:44] [ALPM] installed glibc (2.22-3)
[2016-02-13 13:44] [ALPM] installed gcc-libs (5.3.0-3)
[2016-02-13 13:44] [ALPM] installed ncurses (6.0-4)
[2016-02-13 13:44] [ALPM] installed readline (6.3.008-3)

 

I installed "tuxcmd" an thought I would post a screeshot of the output but scrot gives me an error.So do several other commands.

 

$ scrot -s
giblib error: Saving to file 2016-02-13-191303_639x339_scrot.png failed

$ localectl status
Could not get properties: Operation not permitted

$ localectl --no-convert set-x11-keymap gb pc104 "" terminate:ctrl_alt_bksp
Error getting authority: Error initializing authority: Exhausted all available authentication mechanisms (tried: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS) (available: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS) (g-io-error-quark, 0)
Failed to set keymap: Access denied

$ git config --global user.name "anarchy"
fatal: failed to stat '.': Permission denied

 

That last git command worked several installs ago :'(

 

Here are my permissions for ~/ an they do not look right to me,

 

[bloodaxe@longship ~]$ ls -l
total 44
drwxrwxrwx 3 bloodaxe bloodaxe 4096 Feb 13 15:41 aurbuilds
drwxr-xr-x 2 bloodaxe bloodaxe 4096 Feb 13 16:06 Desktop
drwxrwxrwx 9 bloodaxe bloodaxe 4096 Nov 1 17:33 Documents
drwxrwxrwx 8 bloodaxe bloodaxe 4096 Feb 13 16:23 Downloads
drwxrwxrwx 6 bloodaxe bloodaxe 4096 Feb 15 2015 GNUstep
drwxrwxrwx 13 bloodaxe bloodaxe 4096 Nov 1 22:24 Linux
drwxrwxrwx 10 bloodaxe bloodaxe 12288 Nov 1 22:21 Mirages
drwxrwxrwx 5 bloodaxe bloodaxe 4096 Feb 13 17:48 Notebooks
drwxrwxrwx 6 bloodaxe bloodaxe 4096 Feb 8 19:03 ZZZ
[bloodaxe@longship ~]$ ls -l ..
total 20
drwx------ 16 bloodaxe bloodaxe 4096 Feb 13 18:07 bloodaxe
drwx------ 2 root	 root	 16384 Feb 13 13:13 lost+found

 

Finding information that a dumb shmuck like me can understand is difficult but I found this,

 

https://bbs.archlinu...c.php?id=122387

 

 

The default permissions for a Home folder (when you create a user) is 700, the content usually is 755, probably because you copied your data from a fat32 drive, or a filesystem without permissions capabilities, so these are the default permissions in this case.

If i were you i would do the following:

 

$ chmod 700 ~ && cd ~ && chmod -R 755 ./*

 

The above looks to me like it will make /home 700 which it already is I think. So as I have no idea what to do I will wait to see if anyone can help me out. :'(

Edited February 13, 2016 by abarbarian

[securitybreach]

How are you trying to install Archlinux? Your getting too many odd errors that should never happen. I literally just went through a reinstall less than a month ago without any issues.

 

Are you following the guides step by step or are you jumping around?

 

You should never have to change permissions on a new installation.

[securitybreach]

 

1) Arch should be fixable if it is half running like mine.

 

2) If I could install and fix as I did several years ago I should be able to make this set up work.

 

3) Architect only has grub and syslinux according to the guide I read.

 

4) I need a second pc running to do an install and my second screen is over the other side of the room and I am sick of running across the room to read the wiki.

 

5) I hate to be beaten by inanimate objects, they should do as they are told.

 

 

1) Your installation is too messed up to fix. I mean it is possible but will cause more aggravations than simply reinstalling.

 

2) Your getting really odd errors for too many common things.

 

3) Personally I love syslinux. It's very easy to configure, very stable and works very well with MBR or UEFI setups.

 

4) Take a picture or pull up the wiki on your phone. That's what I usually do if I do not have a machine handy.

 

How did you setup UEFI? Did you follow the wiki entry full for UEFI? Are your GPT partitions set up correctly?

 

My suggestion...back up data and completely wipe everything.

[abarbarian]

Downloaded iso checked md5. dd to usb stick used Jan iso and Feb iso. Used the Begginers Guide and Swampy's updated for 2016 guide,

 

http://www.linuxveda.com/2016/02/08/the-always-up-to-date-guide-to-install-arch-linux/

 

First three tries notes were a tad messy.

 

For the last six tries I made very clear step by step instructions that were double checked. Apart from the xorg-xinit thing. I am totally lost and bemused, maybe I am getting AltZimerrrs as five years ago,

 

http://forums.scotsnewsletter.com/index.php?showtopic=42155&st=0

 

I'm posting this from my new Arch 64 install with Slim login and E17 desktop and Namoraka browser Ain't I a clever chappy It only took me two full days and nights :hysterical: :hysterical:Would have been quicker but half the symbols have worn of me keyboard and I found it impossible to type with the mouse

 

Not bad I recon for someone who was struggling with "how to run Nano" a week ago.I'm (hooked)

 

:'(

[securitybreach]

Well there ya go... I would of just followed the wiki instead of using Swapnil's guide to setting it up. I have noticed on an occasion or two that he missed steps or skipped them entirely.

 

Personally I would follow the Beginner's Guide and then follow the General recommendations link at the bottom of the Beginner's Guide and went from there.

 

There is no reason to use another guide besides the wiki where things do not get updated or are not fully listed.

[abarbarian]

UEFI works I used rEFind and worked out how to set it up, just a simple file name change. It shows my W7 and it works.

 

I have used parted from the cli. Also a disk program that I think is gnome-disk from a live Robolinux.

 

Oh and I have tried the nuke everything scenario several times, more than several.

 

4) Take a picture or pull up the wiki on your phone.

 

Like I am clever enough to do that even if I had a capable phone I have had a second pc running with the wiki up but it did not help. I am positive my instructions are ok, well pretty positive.

[securitybreach]

I do not know then. I cannot find anything that replicates all of your issues without it simply being a bad installation. Are you trying to copy over old configuration files or something?

[abarbarian]

There is no reason to use another guide besides the wiki where things do not get updated or are not fully listed.

 

Well I made an amalgamation of all the guides and cross referenced them.

 

Swampy's guide does tell you how to use visudo whereas the wiki does not. An I picked up on how to add stuff to files without using nano from him as well.

 

The output I posted a few posts back is from a fresh install not the one I asked about at G+.

 

:'(

 

I do not know then. I cannot find anything that replicates all of your issues without it simply being a bad installation. Are you trying to copy over old configuration files or something?

 

Nope.

[abarbarian]

# journalctl -xe

 

Feb 13 14:38:35 longship systemd[440]: Startup finished in 8ms.

-- Subject: System start-up is now complete

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- All system services necessary queued for starting at boot have been

-- successfully started. Note that this does not mean that the machine is

-- now idle as services might still be busy with completing start-up.

--

-- Kernel start-up required KERNEL_USEC microseconds.

--

-- Initial RAM disk start-up required INITRD_USEC microseconds.

--

-- Userspace start-up required 8135 microseconds.

Feb 13 14:38:35 longship systemd[1]: Started User Manager for UID 0.

-- Subject: Unit user@0.service has finished start-up

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit user@0.service has finished starting up.

--

-- The start-up result is done.

Feb 13 14:38:35 longship login[359]: ROOT LOGIN ON tty1

Feb 13 14:38:38 longship dhcpcd[437]: enp0s31f6: no IPv6 Routers available

Feb 13 14:41:07 longship su[496]: (to bloodaxe) root on tty1

Feb 13 14:41:07 longship su[496]: pam_unix(su:session): session opened for user bloodaxe by root(uid=0)

Feb 13 14:41:12 longship kernel: NVRM: Your system is not currently configured to drive a VGA console

Feb 13 14:41:12 longship kernel: NVRM: on the primary VGA device. The NVIDIA Linux graphics driver

Feb 13 14:41:12 longship kernel: NVRM: requires the use of a text-mode VGA console. Use of other console

Feb 13 14:41:12 longship kernel: NVRM: drivers including, but not limited to, vesafb, may result in

Feb 13 14:41:12 longship kernel: NVRM: corruption and stability problems, and is not supported.

Feb 13 14:58:15 longship dbus-daemon[354]: Unable to reload configuration: Failed to open "/usr/share/dbus-1/system.conf": Permission denied

Feb 13 14:58:15 longship dbus-daemon[354]: Unable to reload configuration: Failed to open "/usr/share/dbus-1/system.conf": Permission denied

Feb 13 14:58:15 longship groupadd[1426]: group added to /etc/group: name=avahi, GID=84

Feb 13 14:58:15 longship groupadd[1426]: group added to /etc/gshadow: name=avahi

Feb 13 14:58:15 longship groupadd[1426]: new group: name=avahi, GID=84

Feb 13 14:58:15 longship useradd[1430]: new user: name=avahi, UID=84, GID=84, home=/, shell=/bin/nologin

Feb 13 14:58:16 longship dbus-daemon[354]: Unable to reload configuration: Failed to open "/usr/share/dbus-1/system.conf": Permission denied

Feb 13 14:58:16 longship dbus-daemon[354]: Unable to reload configuration: Failed to open "/usr/share/dbus-1/system.conf": Permission denied

Feb 13 14:58:16 longship groupadd[1441]: group added to /etc/group: name=polkitd, GID=102

Feb 13 14:58:16 longship groupadd[1441]: group added to /etc/gshadow: name=polkitd

Feb 13 14:58:16 longship groupadd[1441]: new group: name=polkitd, GID=102

Feb 13 14:58:16 longship useradd[1446]: new user: name=polkitd, UID=102, GID=102, home=/, shell=/usr/bin/nologin

Feb 13 14:58:16 longship useradd[1446]: add 'polkitd' to group 'proc'

Feb 13 14:58:16 longship useradd[1446]: add 'polkitd' to shadow group 'proc'

Feb 13 14:58:16 longship passwd[1451]: password for 'polkitd' changed by 'root'

Feb 13 14:58:16 longship dbus-daemon[354]: Unable to reload configuration: Failed to open "/usr/share/dbus-1/system.conf": Permission denied

Feb 13 14:58:16 longship dbus-daemon[354]: Unable to reload configuration: Failed to open "/usr/share/dbus-1/system.conf": Permission denied

Feb 13 14:58:16 longship groupadd[1461]: group added to /etc/group: name=colord, GID=124

Feb 13 14:58:16 longship groupadd[1461]: group added to /etc/gshadow: name=colord

Feb 13 14:58:16 longship groupadd[1461]: new group: name=colord, GID=124

Feb 13 14:58:16 longship useradd[1465]: new user: name=colord, UID=124, GID=124, home=/var/lib/colord, shell=/bin/false

Feb 13 14:58:23 longship dbus-daemon[354]: Unable to reload configuration: Failed to open "/usr/share/dbus-1/system.conf": Permission denied

Feb 13 14:58:23 longship dbus-daemon[354]: Unable to reload configuration: Failed to open "/usr/share/dbus-1/system.conf": Permission denied

Feb 13 15:33:22 longship dbus-daemon[354]: Unable to reload configuration: Failed to open "/usr/share/dbus-1/system.conf": Permission denied

Feb 13 15:33:23 longship dbus-daemon[354]: Unable to reload configuration: Failed to open "/usr/share/dbus-1/system.conf": Permission denied

Feb 13 15:33:23 longship systemd[440]: Started D-Bus User Message Bus.

-- Subject: Unit UNIT has finished start-up

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit UNIT has finished starting up.

--

-- The start-up result is done.

Feb 13 15:33:23 longship systemd[440]: Failed to register Released match on system bus: Operation not permitted

Feb 13 15:34:01 longship su[1693]: (to bloodaxe) root on tty1

Feb 13 15:34:01 longship su[1693]: pam_unix(su:session): session opened for user bloodaxe by root(uid=0)

Feb 13 15:34:10 longship kernel: nvidia-modeset: Allocated GPU:0 (GPU-ca5d1e63-b35d-d567-d522-0521108ac17c) @ PCI:0000:01:00.0

Feb 13 15:34:10 longship kernel: nvidia-modeset: Allocated GPU:1 (GPU-9d9c9d67-6711-4d92-4d0d-4631173a7df5) @ PCI:0000:02:00.0

Feb 13 15:34:30 longship wmaker[1722]: (handle_inotify_events(event.c:361)): warning: Inotify: Reading config files in defaults database.

Feb 13 15:34:50 longship wmaker[1722]: (handle_inotify_events(event.c:361)): warning: Inotify: Reading config files in defaults database.

Feb 13 15:35:13 longship kernel: usb 1-6: new high-speed USB device number 4 using xhci_hcd

Feb 13 15:35:14 longship kernel: hub 1-6:1.0: USB hub found

Feb 13 15:35:14 longship kernel: hub 1-6:1.0: 4 ports detected

Feb 13 15:35:16 longship kernel: usb 1-6.1: new high-speed USB device number 5 using xhci_hcd

Feb 13 15:35:16 longship kernel: usb 1-6.1: UAS is blacklisted for this device, using usb-storage instead

Feb 13 15:35:16 longship kernel: usb-storage 1-6.1:1.0: USB Mass Storage device detected

Feb 13 15:35:16 longship kernel: usb-storage 1-6.1:1.0: Quirks match for vid 174c pid 55aa: 400000

Feb 13 15:35:16 longship kernel: scsi host8: usb-storage 1-6.1:1.0

Feb 13 15:35:16 longship kernel: usbcore: registered new interface driver usb-storage

Feb 13 15:35:16 longship kernel: usbcore: registered new interface driver uas

Feb 13 15:35:17 longship kernel: scsi 8:0:0:0: Direct-Access ASMT 2105 0 PQ: 0 ANSI: 6

Feb 13 15:35:17 longship kernel: sd 8:0:0:0: [sdb] Spinning up disk...

Feb 13 15:35:19 longship kernel: ..ready

Feb 13 15:35:19 longship kernel: sd 8:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)

Feb 13 15:35:19 longship kernel: sd 8:0:0:0: [sdb] Write Protect is off

Feb 13 15:35:19 longship kernel: sd 8:0:0:0: [sdb] Mode Sense: 43 00 00 00

Feb 13 15:35:19 longship kernel: sd 8:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Feb 13 15:35:19 longship kernel: sdb: sdb4

Feb 13 15:35:19 longship kernel: sd 8:0:0:0: [sdb] Attached SCSI disk

Feb 13 15:36:24 longship su[1763]: (to root) bloodaxe on pts/0

Feb 13 15:36:24 longship su[1763]: pam_unix(su:session): session opened for user root by bloodaxe(uid=1000)

[securitybreach]

Any progress as to your permission issues?

[abarbarian]

Any progress as to your permission issues?

 

Nope. :'(

 

I seem to have lost my Windows 7 ESP partition along the way too. Hopefully I will be able to reinstall it fairly easily. I am away from home for a few days so progress has stopped for the time being. maybe the rest will do my grey cell some good

 

When I get back I will painfully (I hate typing ) post all the instructions I am using to do an install an maybees you could peruse em and tell me if they look ok.

 

I did see a note that on some nvme ssd's you may need to add a "nvme" to the MODULES in mkinitcpio.conf, not sure if I need that as stuff seems to be working on mine. I think I have input error not hardware errors.

 

I have a spare ssd so I might if it is possible do an install on that and then clone the set up across to the nvme. Might be worth a try

Edited February 15, 2016 by abarbarian