- Arch-general - lists.archlinux.org

[arch-general] UEFI madness
by David Benfell 08 Mar '13

08 Mar '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, So far, my attempt to install Arch Linux on a UEFI system is a total facepalm moment. The problem is in booting post-install. So, first, does anyone have actual--and successful--experience installing Arch on a UEFI system? Yes, I went to the Arch Wiki, which initially pointed me at GummiBoot. There are actually two sets of instructions, one given where I looked first, for the UEFI entry, and another under the entry for GummiBoot. Neither succeeds, but I wound up following the latter set of instructions (and cleaning up extra entries with efibootmgr, which fortunately makes this relatively easy). GummiBoot says it can't find /vmlinuz-linux. I tried modifying the configuration to say /boot/vmlinuz-linux, but no joy. Apparently, I'm really supposed to copy this file and the initrd image to the EFI partition, but nobody says where in the EFI partition, so I have no idea. I also tried following the instructions for grub-efi. I'm just mystified. I managed to install the right package, but from there I just wasn't understanding a thing. I've been using linux since 1999 so this shouldn't be so completely mystifying. I tried installing rEFInd (from sourceforge). As near as I can tell, it does indeed detect all the possible boot options on the system. But when I try booting the Arch installation, it says it can't find the root partition. It also detects the GummiBoot option, but that leads the same place as before. Finally, it detects the Windows option, which I hope still works (unfortunately I do need this). I guess getting something that just works--like it did with BIOS systems--is not in the cards. What do I do now? Thanks! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJRMZ+5AAoJELJhbl/uPb4SAA4P/3xG4C5viqdgdZhtZ72hFC9v VLBWw9CguzTvqYMydO4TTqwpyObW0iPFMWRzlkMt7YjmC83qgQJDAI1P7KR4fpHE fHjyqS7IKFnLe4ckKnKJIQMGeEbwcsAaF0Loy/22dW+5U10IRy39NIlvUdWQJKtc O7vpch/lZ2DKFd7zmKgKLu2FLuZK0FvwN2cGH91cYP66rloqaXytXWLZ3IIvCtf5 mGJqwx4CjKWf3FefFANXYsPtb4rmfbE1xl/xeIT4OH0F+0H77EFhFTkBsDknYnHM pUg9B5pHmJ+xMiVSDIYYIXpgT/Spk9DWp4+PZN5N8GBE63J8kzWuUqTVV/XVyR1x 0aZCJAo0Ke+swBa6cGZ/WSWRqA4kP9nJBtJ00qX+PE3FFFd8vjYyP7Qz0cmIhfqV VHx3UXzI9Q8EkMzlENWD79M+WHLeUPQopsdfmWOOI1E7N+5seeFRmekmB+jY1NRJ uXNPCq5w0iIaWB4KuAmchbP3qtoGxU5oXJ5IPh3NQOIdbScN0+4l6HtOmnxMQ2H1 HyR/2nV0e5rvuhsuKBn2ZGyLOvYN6I9AjFBPI5VmY2Ansy750AOOBqXIPLlBouqb Oy0h26dfyn8RdlcoYm4QlXzra1p6ZBk5dJ9GxYhVsXxAaUnlrprXtk3HPQcIjpiS I4n74T8MiK5TxjSDJO60 =6UgK -----END PGP SIGNATURE-----

9 19

Re: [arch-general] [wpa_actiond 1.4] slow disconnects
by Thomas Bächler 08 Mar '13

08 Mar '13

Am 05.03.2013 16:44, schrieb Pali Rohár: > Hello, > > On Tuesday 05 March 2013 10:23:24 Thomas Bächler wrote: >> Am 04.03.2013 21:26, schrieb Leonid Isaev: >>> Hi, >>> >>> With testing/wpa_actiond-1.4 I am having a minor problem >>> when shutting down net-auto-wireless.service: 'systemctl >>> stop net-auto-wireless.service' pauses for ~10sec before >>> finally disconnecting. Of course, this also occurs on >>> normal system poweroff (which is usually ~5sec). The wifi >>> network is WPA "enterprise" (important entries in >>> wpa_supplicant.conf: key_mgmt=WPA-EAP; eap=PEAP; >>> phase1="peaplabel=0"; phase2="auth=MSCHAPV2"), and piece of >> >>> daemon.log after the above delay has elapsed: >> I've seen this too, but I didn't determine yet that is was >> wpa_actiond's fault. There are several issues here: >> >> 1) I am unsure what exactly terminates wpa_actiond. > > Before my patches wpa_actiond could be terminated only by > KILL/TERM signals or correct "terminate" event from > wpa_supplicant. wpa_supplicant sending terminate event only if > wpa_supplcant is stopped regulary (when wpa_supplicant is killed > by KILL no terminate event is sent!). With my patches wpa_actiond > is also terminated when wpa_supplicant is KILLed. > >> 2) net-auto-wireless.service is Type=forking, but has no >> proper MainPID detected, so systemd doesn't know what exactly >> to kill. >> >> This change however seems to be related to Pali's changed, so >> I'm CC'ing him to see if he knows what this might be about. > > You can always stop wpa_actiond with KILL or TERM signals. I did > not removed any code which handling stopping wpa_actiond. I only > added another check if wpa_actiond should exit. > > So my patches should not change behaviour of stopping > wpa_actiond. Problem is maybe in blackbox which starting and > stoppping wpa_actiond. I'm not using that systemd and this is > another reason against it. Not easy to understand and debug this > problem. > > I tested my patches on my system without systemd and wpa_actiond > working without problem. Really I cannot help you with blackbox > which I not using... This may even be related to the way netcfg stops wpa_actiond (it doesn't - it only stops wpa_supplicant). One can probably debug this easily by making wpa_actiond more verbose.

2 1

[arch-general] virtualbox-host-dkms
by Ralf Mardorf 08 Mar '13

08 Mar '13

Hi :) dkms can't rebuild deleted vbox modules for the "linux" kernel # dkms install vboxhost/$(pacman -Q virtualbox|awk {'print $2'}|sed 's/\-.\+//') -k $(uname -rm|sed 's/\ /\//') Module vboxhost/4.2.8 already installed on kernel 3.7.10-1-ARCH/x86_64 # ls /usr/lib/modules/extramodules-3.7-ARCH/ version and for linux-rt I get the same error # dkms install vboxhost/$(pacman -Q virtualbox|awk {'print $2'}|sed 's/\-.\+//') -k 3.6.11-rt30-1-rt/x86_64 Module vboxhost/4.2.8 already installed on kernel 3.6.11-rt30-1-rt/x86_64 but there never were modules installed for the kernel-rt. Regards, Ralf

3 4

[arch-general] Weird issue with Google Talk/Hangout plugin
by David Rosenstrauch 08 Mar '13

08 Mar '13

I'm having a weird issue with the Google Talk plugin (https://aur.archlinux.org/packages/google-talkplugin/) distorting all my video images - both the ones of me coming in from my camera, and the ones coming in from others across the Net. See http://www.darose.net/GoogleHangWeirdness.png for an example. Anyone have any idea what's going on here and/or how to fix? This seems to be a recent issue - i.e., probably caused by some package upgrade within the past week or so. I'm running google-talkplugin 3.14.17.0-1 with firefox 19.0-1. But I don't think the issue is caused by the plugin itself. (Or by firefox, since I see the same problem when I use Google chromium browser.) I was running an older version of the plugin - which had been working fine for weeks - when I started experiencing the issue. I upgraded to the latest version in an attempt to work around the problem, but it didn't clear it up. So as I said, I don't think the plugin itself is the cause of the problem - since 2 different versions of the plugin are experiencing the issue, and the issue popped up out of the blue after things had been working fine for quite a while. Any assistance anyone might be able to lend here would be much appreciated! Thanks, DR

1 1

Re: [arch-general] Cannot chroot '/bin/bash': No such file or directory
by David C. Rankin 07 Mar '13

07 Mar '13

On 03/06/2013 08:24 PM, Ross Hamblin wrote: > It's been a while now but ISTR this message when chroot from 32 bit host > and 64 bit target, or maybe it was vice versa. > > HTH > Ross. It does. It has to be something that simple. However, checking, I have booted with the i686 install medium. The box is an older dell P4, so the i686 is correct and matches the system installed. The install disk /bin/bash date is May 7, 2011. The /bin/bash on /dev/sda6 at /mnt/usr/bin/bash (after mount of the system / at /mnt) is January 26, 2013. Attempting the chroot again on fresh reboot gives the same failure: # cd /mnt # chroot /mnt chroot: failed to run command `/bin/bash`: No such file or directory For some reason it is like the system has no ability to find anything. The install cd is a pre /lib change cd, so that may be the issue. I have downloaded the latest install cd and will try again. Thank you again Ross. Any other suggestions welcomed. -- David C. Rankin, J.D.,P.E.

2 1

[arch-general] Cannot chroot '/bin/bash': No such file or directory
by David C. Rankin 07 Mar '13

07 Mar '13

Guys, Attempting to fix the test box that updating left unable to boot, I cannot chroot to fix the system. I've booted from the install medium and done the normal mount of the existing system under /mnt: mount /dev/sda6 /mnt mount /dev/sda5 /mnt/home mount /dev/sda8 /mnt/boot mount -o bind /dev /mnt/dev mount -t proc none /mnt/proc mount -t sysfs none /mnt/sys All files appear in their proper place under /mnt. However, attempting to create the chroot fails: cd /mnt chroot /mnt /bin/bash chroot: failed to run command '/bin/bash': No such file or directory /bin/bash is in the new location /usr/bin/bash (moved from /bin/bash by the update) with with a proper symlink in /mnt/bin/bash pointing to ../usr/bin/bash This if the first time I've ever had difficulty chrooting a system. I suspect that this is caused by the last update that pulled in systemd which left the system unbootable. Anyone know what could be causing the chroot failure? I've tried explicitly pointing the chroot to ./usr/bin/bash, etc... and tried it without any executable specified. Regardless, I get the same "No such file or directory". Thanks in advance for any help or link you can provide. -- David C. Rankin, J.D.,P.E.

3 2

[arch-general] Forced to run fsck manually on unattended system
by edd_smith 07 Mar '13

07 Mar '13

Hi, I run a series of remote boxes running Arch. These boxes are unnattended and are very difficult to access. Due to the nature of their power supply they are often powered down without any warning. A UPS is not an option. I have noticed that over time the boxes are showing file system errors and getting stuck during the boot phase requiring manual intervention (Either press Control-D to continue - resulting in failure or log in to the start up shell using the root password and run fsck manually). I simply answer yes to every prompt from fsck and the errors are resolved, the box reboots and runs fine. I need to be able to force an 'fsck -y' type command at every boot as visiting these boxes manually isn't an option. I have already moved the partitions to ext2 as this seemed to show a mild improvement and also set 0 1 flags in /etc/fstab but still I'm seeing the freezing on boot. First of all should I be re-partitioning my drives to something which can handle these kinds of sudden power outages or removing the swap space or something? Secondly can I have arch run a completely unprompted startup whereby fsck will do its best to repair the system without requiring intervention - for me a blank disk is no worse than a frozen system. Thanks in advance, Edward Smith -- View this message in context: http://archlinux.2023198.n4.nabble.com/Forced-to-run-fsck-manually-on-unatt… Sent from the arch general mailing list archive at Nabble.com.

4 4

[arch-general] [wpa_actiond 1.4] slow disconnects
by Leonid Isaev 06 Mar '13

06 Mar '13

Hi, With testing/wpa_actiond-1.4 I am having a minor problem when shutting down net-auto-wireless.service: 'systemctl stop net-auto-wireless.service' pauses for ~10sec before finally disconnecting. Of course, this also occurs on normal system poweroff (which is usually ~5sec). The wifi network is WPA "enterprise" (important entries in wpa_supplicant.conf: key_mgmt=WPA-EAP; eap=PEAP; phase1="peaplabel=0"; phase2="auth=MSCHAPV2"), and piece of daemon.log after the above delay has elapsed: Mar 3 17:08:39 bluemoon systemd[1]: Stopping Automatic netcfg wireless connection service... Mar 3 17:08:39 bluemoon wpa_actiond[380]: Interface 'wlan0' lost connection to network 'lsusecure' Mar 3 17:08:39 bluemoon netcfg-wpa_actiond[9323]: :: university-wifi down [done] Mar 3 17:08:39 bluemoon wpa_actiond[380]: Interface 'wlan0' disconnected from network 'lsusecure' Mar 3 17:08:39 bluemoon wpa_actiond[380]: Terminating wpa_actiond session for interface 'wlan0' This is not related to wpa_supplicant 2.0. In wpa_actiond git tree, there was only 1 essential commit (baed7cae042ceb50507066f2df85b06414ab2176) which led to v1.4, but I'm not sure what exactly causes this. Since wpa_actiond doesn't have a --debug switch, how do I trace the issue? Thanks, -- Leonid Isaev GnuPG key: 0x164B5A6D Fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D

2 2

[arch-general] Gotta be a stupid gnome-terminal problem
by David Benfell 05 Mar '13

05 Mar '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, All other terminal emulators work. I have checked--thanks to what little I found on the web that seemed apropos--to be sure that /dev/pts is mounted (it is). But when I run gnome-terminal, I get no prompt and typing in commands does not work. This is a brand new installation, so I can't say it worked before some change. All I know is it doesn't work. What did I miss? Thanks! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRMg7tAAoJELJhbl/uPb4SugEP/iQwglQu2HREKC32w31rHZXD dJCsZ5b0Up7cwqj8y4lCfg3cQVwlOVy7gmjjc6LYJylY6lNCuXbMJpi4uFqw1juq ebmjmMs33bVBnnvOyzt4H8T67N9f8vS2iHhsm/5doEhoN/HLhn4Q/9bGnqB1Zmg/ PleJOFAiIjtx3ZMsBmeYzRvssmlAcnBFZKrMAtBz7ajEX8c2v/u3//y/cd9gQdwG WiNpi45U+aId+P+adeqhRf0mHSzU5S1WmAPa8p06g+uVhGfEFva+E8ZNUwYG8z7f L83fbYu97liICNSoaWwb7h/kDDAIqWNr/kXxz8XFccCTlsGkrC9WUoqHrQzjKqsr 8Ok/cvIx7KiMOdnmBA9bRcdeEhxVnodfbIjd1NRXSSb/0JPXspV0QTF7NqYJXbY+ qpMBKFZPAwMFCzFa6brrUHwm5nhNn7SHcdbDveF2Tl1RQTuUdgf9cdSk/Xg7U89a b74xrrNYwr9GYoXiqxkB3KuwjfdI0ksO840iaYGf5ly+TUpABgFY7dBamSqjjZQK Szruq1fEFmun5hDFwwpmGKlhAmU4vln0Tm71xRNr95yPHEV+K8F3ZfoFVQcHd8cx CzPEGqX+g/bSC1iEVspYlCCL+/MfbiNp9JMtYsWW3l9AaATq9aCXaD+2veTCN+S9 vh636DllstMYh4dsSi9U =JOIU -----END PGP SIGNATURE-----

3 5

[arch-general] Sound problems
by Frank Zimmermann 04 Mar '13

04 Mar '13

Good evening, I'm having troubles getting sound to work aftereach reboot. I've followed the instructions from the wiki. But after each reboot I need to run alsamixer -> selct the soundcard by pressing F6 -> and then have to increase the volume of the speaker. When invoking systemctl enable alsa-restore.service and systemctl enable alsa-store.service I do get the following error messsage: The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). ... and it starts from the beginning after the next reboot. BTW it doesn't help when I change the settings in /etc/asound.conf from pulseaudio to the hw device. Thanks for any help Frank

4 10