- Arch-general - lists.archlinux.org

[arch-general] systemd-networkd 226 in virtual machines
by Damjan Georgievski 09 Sep '15

09 Sep '15

in 226, systemd-networkd now supports predictable interface names for virtio devices.[1] For people running Arch in KVM with virtio-net (as I do), that means the network interface name will change from eth0 to - in my case - ens5. That, for me also meant no ip address after reboot. Make sure to set [Match]Name=en* or some such before rebooting. [1] https://github.com/systemd/systemd/blob/23d08d1b2bfd7f4b3c0a9408c9ccd65c3fb… -- damjan

2 1

[arch-general] Any ETA on the Tex Live 2015 update?
by Mohammad_AlSaleh 07 Sep '15

07 Sep '15

Hello. Tex Live 2015 was released on June 11. The Arch packages were flagged out-of-date on June 13. I'm wondering if there is any reason for the hold-up. Other than the maintainers(s) being busy of course.

7 9

[arch-general] ca-certificates update
by mick 07 Sep '15

07 Sep '15

After re-installing in july I'm having problems with certificates and was pointed to https://www.archlinux.org/news/ca-certificates-update/ ca-certificates update 2014-12-11 - Jan Steffens The way local CA certificates are handled has changed. If you have added any locally trusted certificates: 1 Move /usr/local/share/ca-certificates/*.crt to /etc/ca-certificates/trust-source/anchors/ 2 Do the same with all manually-added /etc/ssl/certs/*.pem files and rename them to *.crt 3 Instead of update-ca-certificates, run trust extract-compat Also see man 8 update-ca-trust and trust --help. when I tried step 2: move /etc/ssl/certs/*.pem to /etc/ca-certificates/trust-source/anchors/ and rename them to *.crt I found 1 the mv command seems to have lost the ablity to rename files as they are moved. 2 moving or copying the *.pem file results in adirectory full of broken links. I think the solution might be to create symlinks to the real files, located at /etc/ca-certificates/extracted/cadir instead of linking to link to the files but before I try that I want to be sure I wont break anything. mick

1 0

[arch-general] systemd 215 breaks machinectl login
by arnaud gaboury 05 Sep '15

05 Sep '15

I just upgraded to systemd 215, and connaction to my container is broken. # machinectl login MyMachine Connected to machine MyMachine. Press ^] three times within 1s to exit session. Then it hangs here indefinitely. No login shell. -- google.com/+arnaudgabourygabx

1 0

[arch-general] Update problems
by edson duarte 02 Sep '15

02 Sep '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 hi! pacman reports that the repositories are up to date for a couple of weeks now with no errors or warnings and this had never happened, i've tried looking in the forums and the news on the website but found nothin g. anyone knows why this is happening? thanks! - -- edson duarte https://emailselfdefense.fsf.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJV5vmTAAoJEEuaWOJw2A3L0HIP/3hK2qGN8mvismCbOBiIf+9k 7il7ROwjRkd1NadoHXawMkgDu6ywLYVCiSy5K5nR6+Jz4opAE9xoWKdyJ5b6sWNp tEwKu73JWlEV7Wrnl7aEZcj6U/QW6yRdQic+9eQABBL3HEilScgloYsvS1ZrhON5 1spLWWEbQi6XwNgKqoRFkewybUFMfJXd+zWNdlVSKuBi1Repr+JsRnfStzHuLBKQ MptNCC+ybJTmJ/KFvw7dDjObb1tDXNjEzLpdNok1RFLcrMeYCrmBM3soOsn6EGuf vFyRXZuMKxI+y4DdlFCeIkBhw/XPd7c48bkkw/tj1RpYl9OCKAbpVK79J3p7r25k jTZLbsqE+D2R8aT4i9Ji3f/Se6tWvUuwhxKaxhY4RshpMdPo311Eiz+8OO8aMz3+ iwxfxHDzcgUhrAtGU6LWlEnUjgoDa1oBa+uvXpEgBcmJsKay5ueM06WDAxXu31Vg 89RY3+pD7hbjNidiKdZFfF4IvNTsokFFHGaCh/ui51ceRcXjfCePJLBftc21R/2a ak2PKsBsJYxIgLL4z3l6heulmqiOmpOnDzUgrfna05q+0jDfhS1Fis3suyV31dzZ 5oi5+tWl+Nkp80h/XbRUGHYjkMt/gJ14Kr/Bu0WYx01urd16SpbvUEyMq28utdyP ZKhyX2tOnApKKo/giWze =rBdK -----END PGP SIGNATURE-----

2 2

[arch-general] Strange mdadm fail to activate root raid1 array - resulting in loss of libraries and pacman data?
by David C. Rankin 01 Sep '15

01 Sep '15

All, I saw TB's patch posts to the kernel-raid mailing list. I believe I experienced the same systemd-mdadm error which resulted in ~440 libraries being left as 0-byte files and pacman losing all reference to what files where owned by what packages. In my case dmesg showed the system never made any attempt to activate sda7 as part of the root array (md1) on boot. Following a --fail, --remove and --add to re-add sda7 worked as advertised. However, on next reboot, grub was found and launched the kernel, only to have the system crash due to /usr/lib/libkmod.so "file too short" (0-byte). Attempting to re-install the kernel to attempt to address the issue resulted in: [2015-08-31 15:58] [ALPM-SCRIPTLET] ==> WARNING: No modules were added to the image. This is probably not what you want. [2015-08-31 15:58] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img [2015-08-31 15:58] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete. [2015-08-31 15:58] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback' [2015-08-31 15:58] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect [2015-08-31 15:58] [ALPM-SCRIPTLET] ==> Starting build: 4.1.6-1-ARCH [2015-08-31 15:58] [ALPM-SCRIPTLET] -> Running build hook: [base] [2015-08-31 15:58] [ALPM-SCRIPTLET] -> Running build hook: [udev] [2015-08-31 15:58] [ALPM-SCRIPTLET] -> Running build hook: [modconf] [2015-08-31 15:58] [ALPM-SCRIPTLET] -> Running build hook: [block] [2015-08-31 15:58] [ALPM-SCRIPTLET] ==> ERROR: module not found: `eata' [2015-08-31 15:58] [ALPM-SCRIPTLET] ==> ERROR: module not found: `a100u2w' [2015-08-31 15:58] [ALPM-SCRIPTLET] ==> ERROR: module not found: `3w_sas' [2015-08-31 15:58] [ALPM-SCRIPTLET] ==> ERROR: module not found: `bnx2fc' <snip> lots of modules not found Booting the install media, chrooting and investigating revealed some 440 libraries in /usr/lib that were 0-byte. pacman had also lost its package-file database. E.g. # pacman -Ql unixodbc # (showed no files) all of this occurred with mdadm 3.3.2-2, which is still the current package. TB's original post at the kernel raid list regarding the patch is: [PATCH 0/2] mdadm: Fix udev rule interaction with systemd, http://www.spinics.net/lists/raid/msg49678.html The explanation of the losses on my system posted to the list are: Re-add of raid1 drive resulted in strange loss of data on Archlinux? http://www.spinics.net/lists/raid/msg49704.html Are these the symptoms (or related symptoms) that the TB's patch is intended to address? This has only occurred once since the current mdadm was installed back on 2015-05-26. What is the recommended work-around until a fix is in place? (validate all arrays with /proc/mdstat) But then how to handle a degraded boot? I did --fail, --remove --add, and ended up with a mess. Is there some other suggested way to handle this? -- David C. Rankin, J.D.,P.E.

1 0

[arch-general] GA-990FX - on boot I get IO_PAGE_FAULT & AMD-Vi: Event logged??
by David C. Rankin 31 Aug '15

31 Aug '15

All, Installed arch on a new gigabyte GA-990FX-UD3 board with a AMD FX-8350. This is the board I had to enable IOMMU in the BIOS to get the Realtek 8111/8168/8411 onboard NIC to work. Ever since enabling IOMMU, I get kernel messages regarding Page_Faults and AMD Vi Events. Enabling the kernel parameter amd_iommu=on seems to have stopped some of the xhci-hcd messages printed to the screen, but they are still in dmesg. I need to know if anyone has seen this and if there is a fix. Everything works fine after it boots, but it is horrible looking at the errors on boot. Specifically, here is what is logged: [ 1.663291] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.663401] ehci-pci: EHCI PCI platform driver [ 1.663545] QUIRK: Enable AMD PLL fix [ 1.663575] ehci-pci 0000:00:12.2: EHCI Host Controller [ 1.663581] ehci-pci 0000:00:12.2: new USB bus registered, assigned bus number 1 [ 1.663586] ehci-pci 0000:00:12.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround [ 1.663596] ehci-pci 0000:00:12.2: debug port 1 [ 1.663634] ehci-pci 0000:00:12.2: irq 17, io mem 0xfe509000 [ 1.663730] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 1.664080] ohci-pci: OHCI PCI platform driver [ 1.674434] ehci-pci 0000:00:12.2: USB 2.0 started, EHCI 1.00 [ 1.674667] hub 1-0:1.0: USB hub found [ 1.674681] hub 1-0:1.0: 5 ports detected [ 1.674861] xhci_hcd 0000:02:00.0: xHCI Host Controller [ 1.674868] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2 [ 1.698638] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 [ 1.744500] firewire_ohci 0000:04:0e.0: added OHCI v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x11 [ 2.244836] firewire_core 0000:04:0e.0: created device fw0: GUID 0014aafc64aa2c00, S400 [ 2.424912] tsc: Refined TSC clocksource calibration: 4018.296 MHz [ 19.310338] xhci_hcd 0000:02:00.0: can't setup: -110 [ 19.310768] xhci_hcd 0000:02:00.0: USB bus 2 deregistered [ 19.310811] xhci_hcd 0000:02:00.0: init 0000:02:00.0 fail, -110 [ 19.311341] xhci_hcd: probe of 0000:02:00.0 failed with error -110 [ 19.311385] AMD-Vi: Event logged [ [ 19.311394] Switched to clocksource tsc [ 19.311406] ehci-pci 0000:00:13.2: EHCI Host Controller [ 19.311412] ehci-pci 0000:00:13.2: new USB bus registered, assigned bus number 2 [ 19.311415] ehci-pci 0000:00:13.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround [ 19.311443] ehci-pci 0000:00:13.2: debug port 1 [ 19.311500] ehci-pci 0000:00:13.2: irq 17, io mem 0xfe507000 [ 19.311678] IO_PAGE_FAULT device=02:00.0 domain=0x0016 address=0x00000000ce9f9880 flags=0x0010] [ 19.311689] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0016 address=0x00000000ce9f9880 flags=0x0010] [ 19.312650] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0016 address=0x00000000ce9f9880 flags=0x0010] [ 19.313611] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0016 address=0x00000000ce9f9880 flags=0x0010] <snip many more AMD-Vi Events> [ 19.335619] AMD-Vi: Event logged [ [ 19.335918] ehci-pci 0000:00:13.2: USB 2.0 started, EHCI 1.00 [ 19.335924] IO_PAGE_FAULT device=02:00.0 domain=0x0016 address=0x00000000ce9f9880 flags=0x0010] [ 19.335925] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0016 address=0x00000000ce9f9880 flags=0x0010] [ 19.335926] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0016 address=0x00000000ce9f9880 flags=0x0010] [ 19.335926] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0016 address=0x00000000ce9f9880 flags=0x0010] <snip ~480 more AMD-Vi Events (same event)> [ 19.336291] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0016 address=0x00000000ce9f9880 flags=0x0010] [ 20.581330] hub 2-0:1.0: USB hub found [ 20.581343] hub 2-0:1.0: 5 ports detected [ 20.581604] ehci-pci 0000:00:16.2: EHCI Host Controller [ 20.581608] ehci-pci 0000:00:16.2: new USB bus registered, assigned bus number 3 [ 20.581611] ehci-pci 0000:00:16.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround [ 20.581619] ehci-pci 0000:00:16.2: debug port 1 [ 20.581641] ehci-pci 0000:00:16.2: irq 17, io mem 0xfe504000 [ 20.596725] ehci-pci 0000:00:16.2: USB 2.0 started, EHCI 1.00 [ 20.596913] hub 3-0:1.0: USB hub found [ 20.596925] hub 3-0:1.0: 4 ports detected ... continues normally Anybody have any idea how to fix this? -- David C. Rankin, J.D.,P.E.

5 11

[arch-general] Extremely slow battery status on MBP
by Emanuel Evans 31 Aug '15

31 Aug '15

Apologies for the repeat posting--I think my previous posting ended up bouncing due to some misconfigured dmarc settings. Anyways, I have kind of a weird issue that I'm having trouble debugging. On my MacBook Pro (11,1), checking battery status (through acpi or the /sys filesystem) becomes extremely slow after the computer's been on for a while. Here's an example: $ time cat /sys/class/power_supply/BAT0/status Charging real 0m54.519s user 0m0.000s sys 0m4.663s dmesg and journalctl aren't outputting anything during the call, and I tried strace during the command and there was no output during the blocked time. It's highly intermittent--acpi can take anywhere from 0-60 seconds with no discernible pattern, except that it doesn't happen when the battery is plugged in and charged. Any ideas for how to debug this further, or possible solutions? Thanks so much!

4 5

[arch-general] Having trouble understanding UEFI booting
by mick 29 Aug '15

29 Aug '15

I've been trying to install archlinux on my Lenovo B50-70 laptop and got stuck installing grub boot loader inconjunction with UEFI. Either I'm miss understanding the wiki pages on the subject and/or the wiki pages could do with a bit more clarity. I'm dual booting arch and windows 8.1, previously I had ubuntu 14.04 but when I upgraded to 15.04 it got too messed up so I decided to bite the bullet and go with arch. The disk is currently split into 11 partitions part size code name 1 1 gb 2700 Basic data partion windows or lenovo 2 260mb EF00 EFI system partition 3 1 gb ED01 Basic data partion windows or lenovo 4 128mb 0C01 Microsoft reserved 5 71gb 0700 Basic data partion windows system 6 25gb 0700 Basic data partion windows or lenovo 7 14gb 2700 Basic data partion windows or lenovo 8 153gb 0700 shared NTFS data partition 9 78gb 8304 Linux / 'root' partition 10 9 gb 8200 swap 11 108gb 8302 /home when installing I have only used partitions 9, 10 & 11. partitions 1 - 8 were on the disc from the windows pre-install and shrunk to make way for linux. A recent operation is affecting my concentration and comprehension so be kind please. mick

5 6

[arch-general] Weird glitch with X keymap
by Mauro Santos 28 Aug '15

28 Aug '15

Like the subject says I have stumbled upon a weird glitch with X keymap. The TL;DR version is the keymap on a usb keyboard that I have connected to my laptop is wrong until I press any key on my laptop's keyboard. I have a workaround in place but I would like to fix this properly. Now the long version. I am configuring X's keymap with /etc/X11/xorg.conf.d/00-keymap.conf, which contains: Section "InputClass" Identifier "Keyboard Defaults" MatchIsKeyboard "yes" Option "XkbLayout" "pt" Option "XkbOptions" "terminate:ctrl_alt_bksp" EndSection I'm using XFCE and it should not be messing with the keyboard configuration, the keyboard configuration utility is set to "Use system defaults". If I'm using only my laptop's built-in keyboard this works as expected and the pt keymap is (or seems to be) properly set as soon as XFCE starts. Now I have a usb mouse/keyboard combo (Logitech MK520) connected to the laptop, as I have put the laptop to the side to use a larger monitor. The weird problem manifests itself when starting XFCE either if starting XFCE with the keyboard already plugged in or if I plug the keyboard after start XFCE. If I start XFCE and use the laptop's keyboard first, the keymap is correct. If I start XFCE and use the usb keyboard first, the keymap is wrong, as far as I can tell it seems to be using the us keymap. If I start XFCE and press any key on laptop's keyboard before using the usb keyboard, then the keymap on the usb keyboard is correct. I have looked through X's logs and nothing seems to be out of place and the pt layout is the only thing that is present in the logs, there is no mention to the us layout. The output of 'setxkbmap -query -v' is the same before and after pressing any key on the laptop's keyboard to "fix" the problem with the usb keyboard. There is nothing on the journal or dmesg that might point to the problem. The workaround I have in place is using running 'setxkbmap pt' automatically (via autostart) after I start XFCE, in this case things work as they should. Google did not help with this and the is nothing on the wiki about this weird problem. Has anyone seen this behavior before? Any ideas on how I can properly fix this? -- Mauro Santos

4 7