Re: [arch-general] rEFInd 0.6.4 + linux 3.7.2-1 fail to boot
On 15 Jan 2013 at 18:35:19 -0200, Kazuo Teramoto wrote: I'm having this issue with linux 3.7.2-1 too. I use gummiboot-efi and file from core (5.11-1). Linux 3.7.1-2 boots ok. Linux 3.7.3-1 is booting for me. Regards, Kazuo Teramoto signature.asc Description: signature
Re: [arch-general] I have to switch back to tty1 for systemd to shutdown the pc
On Thu, Jan 17, 2013 at 05:46:48PM +0100, solsTiCe d'Hiver wrote: hi all, Since latest update of gnome 3.4, I can't login through gdm because, then, I have no single glyph or font displayed on my desktop in menu or application (but not the qt ones) So, I found the work around to switch to tty2 and login and run startx and all is fine in my desktop. The fonts are back. No idea what this bug is about ! Anyway, my problem is: When I shutdown the PC from gnome desktop, I end up on tty2 console, and nothing is happening there i.e. no shutdown. I have to switch back manually to tty1 so that the shutdown procedure begins or continues. Any idea why systemd fails like that ? or gnome ? Since you are not using gdm to login anyway, try disabling it from automatically starting (systemctl disable gdm), and login using tty. Then atleast the gdm running on the other tty will not hold the shutdown sequence. -- Srijan Choudhary http://www.srijn.net/ pgpNz0f5_yrPI.pgp Description: PGP signature
[arch-general] Request help with wired network config after initial install and reboot
I did a base install last night on a machine with only a wired connection - using the arch iso from 2013-01-04 - the install seemed to go fine and I had a network connection using dhcp during the install and once chrooted into /mnt everything seemed fine. At that stage I set up a wired static ip connection (following the beginners guide) using ifplugd - but the service does not start from within the chroot during the install - but when I rebooted at the completion of the install I have no network connection and I cannot see any network device (was eth0 during the install) - is it possible this may be due to the systemd-197 package that was installed with the interface naming changed? It seems that the ifconfig command is not available once rebooted into the install and I don't know how to proceed. Can anyone give my any advice on how to get the network up on the newly installed system? I could not find anyone who had the same problem in the forums or searching on the net. Thanks in advance. -- mike c
Re: [arch-general] Request help with wired network config after initial install and reboot
On Fri, Jan 18, 2013 at 09:31:14AM +, Mike Cloaked wrote: I did a base install last night on a machine with only a wired connection - using the arch iso from 2013-01-04 - the install seemed to go fine and I had a network connection using dhcp during the install and once chrooted into /mnt everything seemed fine. At that stage I set up a wired static ip connection (following the beginners guide) using ifplugd - but the service does not start from within the chroot during the install - but when I rebooted at the completion of the install I have no network connection and I cannot see any network device (was eth0 during the install) - is it possible this may be due to the systemd-197 package that was installed with the interface naming changed? Interfaces are, on new installs, not `wlan0` or `eth0`. They are now dictated by udev [1][2]. My wired and wireless devices are now enp0s25 and wlp3s0. It seems that the ifconfig command is not available once rebooted into the install and I don't know how to proceed. Run `ip l`. [1] https://mailman.archlinux.org/pipermail/arch-dev-public/2013-January/024231.html [2] http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames -- William Giokas | KaiSforza GnuPG Key: 0xE99A7F0F Fingerprint: F078 CFF2 45E8 1E72 6D5A 8653 CDF5 E7A5 E99A 7F0F pgpl_YqSpUppA.pgp Description: PGP signature
Re: [arch-general] Request help with wired network config after initial install and reboot
On Fri, Jan 18, 2013 at 9:38 AM, William Giokas 1007...@gmail.com wrote: On Fri, Jan 18, 2013 at 09:31:14AM +, Mike Cloaked wrote: I did a base install last night on a machine with only a wired connection - using the arch iso from 2013-01-04 - the install seemed to go fine and I had a network connection using dhcp during the install and once chrooted into /mnt everything seemed fine. At that stage I set up a wired static ip connection (following the beginners guide) using ifplugd - but the service does not start from within the chroot during the install - but when I rebooted at the completion of the install I have no network connection and I cannot see any network device (was eth0 during the install) - is it possible this may be due to the systemd-197 package that was installed with the interface naming changed? Interfaces are, on new installs, not `wlan0` or `eth0`. They are now dictated by udev [1][2]. My wired and wireless devices are now enp0s25 and wlp3s0. It seems that the ifconfig command is not available once rebooted into the install and I don't know how to proceed. Run `ip l`. [1] https://mailman.archlinux.org/pipermail/arch-dev-public/2013-January/024231.html [2] http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames Thanks William - I have just managed to get the network up using the sequence: ip link - which gave the new interface name. Then using the new name: ip link set enp0s25 up ip addr add 10.0.0.10/24 dev enp0s25 ip route add default via 10.0.0.135 Then edited /etc/resolv.conf to get a working network. However once I have completed the rest of the install and configuration I want to have the network come alive with a static ip address at boot. What is the current recommended best method? Is it netcfg, ifplugd or something else? This will be a desktop that runs on its own in a relative's home where there is only a single wired router. Thanks for any advice. -- mike c
[arch-general] update to calibre-0.9.15-1
during today's update from calibre 0.9.14-1 - 0.9.15-1, pacman complained that all packages under /usr/lib/calibre/calibre were already existing in the filesystem, and therefore the update couldn't be performed. for some reason pacman -Qo claimed that all these files didn't belong to any package. only after moving them from that location somewhere else could the new version of calibre be installed. looks to me as if this is some packaging error. don't know enough about arch packaging though to say what exactly went wrong... -- phani.
Re: [arch-general] update to calibre-0.9.15-1
On Fri, 18 Jan 2013 18:52:08 +0530, Karol Babioch ka...@babioch.de wrote: Looking at the changes done to package, I don't think that this is a packaging error, see [1]. Had you issues with other packages, too? no, everything else went smooth; and after moving those calibre files, so went the calibre update. didn't make any manual changes to files under /usr/lib/~ in a long time, nor did my computer crash recently. don't remember if my internet connection went dead during the first attempt to update, that happens frequently. but i don't see how that would mess up things -- unless everything is downloaded checked, pacman doesn't do anything. weird, but nothing to loose sleep over. some freak accident... -- phani.
Re: [arch-general] rEFInd 0.6.4 + linux 3.7.2-1 fail to boot
Em 17-01-2013 23:49, Kazuo Teramoto escreveu: Linux 3.7.3-1 is booting for me. Regards, [SOLVED] Confirmed working here too, with 3.7.3-1. Thanks all. -- http://www.google.com/profiles/andre.vmatos signature.asc Description: OpenPGP digital signature
Re: [arch-general] Request help with wired network config after initial install and reboot
On Fri, Jan 18, 2013 at 9:38 AM, William Giokas 1007...@gmail.com wrote: On Fri, Jan 18, 2013 at 09:31:14AM +, Mike Cloaked wrote: I did a base install last night on a machine with only a wired connection - using the arch iso from 2013-01-04 - the install seemed to go fine and I had a network connection using dhcp during the install and once chrooted into /mnt everything seemed fine. At that stage I set up a wired static ip connection (following the beginners guide) using ifplugd - but the service does not start from within the chroot during the install - but when I rebooted at the completion of the install I have no network connection and I cannot see any network device (was eth0 during the install) - is it possible this may be due to the systemd-197 package that was installed with the interface naming changed? Interfaces are, on new installs, not `wlan0` or `eth0`. They are now dictated by udev [1][2]. My wired and wireless devices are now enp0s25 and wlp3s0. It seems that the ifconfig command is not available once rebooted into the install and I don't know how to proceed. Run `ip l`. [1] https://mailman.archlinux.org/pipermail/arch-dev-public/2013-January/024231.html [2] http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames I have had a chance to sort this all out now - and it turns out that once the initial install is complete it was necessary for me to do the following: 1) Install both ifplugd and netcfg 2) From within /etc/network.d take the example file ethernet-static and put it in /etc/network.d/ and configure the address parameters for my system 3) Edit /etc/ifplugd/ifplugd.conf as it inherited the interface name eth0 and needs to be changed to the correct enp0s25 name 4) Edit /etc/conf.d/netcfg as it inherited the interface name eth0 and needs to be changed to the correct enp0s25 name Now when doing systemctl restart net-auto-wired it does set up the wired network correctly - and of course systemctl restart net-auto-wired is required for the service to start after the next and subsequent bootups. I presume that the February archiso file will be built with systemd-197 so this problem would not arise once that is released - and the problem I had today is presumably a temporary one due to the interface naming scheme being changed after the January iso was built with the old names but installs the system with new names yet copying configs into the standard files with the previous names. Anyway this is resolved now and I hope this post may help anyone else who finds they end up with the same issue. Of course I have not done an install with a laptop with wireless but I guess there may be corresponding issues with that - and with dhcp assigned networking? Maybe others will report if that is a non-issue for installs done with the January archiso but executed after the systemd-197 release? -- mike c
Re: [arch-general] MBP 8, 2: Screen(s) found, but none have a usable configuration
On Thu, Jan 17, 2013 at 2:03 PM, D. Can Celasun dcela...@gmail.com wrote: Hi, Brainless software engineer here. I'm using Arch on an iMac 27 + 27 Cinema Display at work and I couldn't be happier. Sure, it took an extra 15 minutes to set it up (compared to a PC) A bit OT here. D.: is there any remarkable difference worth noting between running Arch on PC and on a Mac? I'm thinking in something like heat or some part of the HW not being fully supported like the keyboard or anything else. There's no doubt Apple products stands out because the excellent hardware, one of the main reasons one would argue to install GNU/Linux on them, but as I never tried this and I'm a bit reluctant to mess with HW glitches I would love to hear from an archer running his system on Mac. Regards.
Re: [arch-general] MBP 8, 2: Screen(s) found, but none have a usable configuration
On Fri, Jan 18, 2013 at 8:50 PM, Martín Cigorraga m...@archlinux.us wrote: On Thu, Jan 17, 2013 at 2:03 PM, D. Can Celasun dcela...@gmail.com wrote: Hi, Brainless software engineer here. I'm using Arch on an iMac 27 + 27 Cinema Display at work and I couldn't be happier. Sure, it took an extra 15 minutes to set it up (compared to a PC) A bit OT here. D.: is there any remarkable difference worth noting between running Arch on PC and on a Mac? I'm thinking in something like heat or some part of the HW not being fully supported like the keyboard or anything else. There's no doubt Apple products stands out because the excellent hardware, one of the main reasons one would argue to install GNU/Linux on them, but as I never tried this and I'm a bit reluctant to mess with HW glitches I would love to hear from an archer running his system on Mac. Well, the entire office has this exact same hardware setup. Some run stock OS X, some run Windows and I run Arch :) All of our machines seem equally hot (which iMac's tend to do) so I don't think there any power management issues that stand out. One disappointing thing was the Catalyst perfomance. Occasionally, it caused some mouse cursor and compositor corruptions. Though I'm told these happen in a lot of systems using Catalyst, so it's not iMac specific. Switching to xf86-video-ati solved all that What else? Wireless (ath9k) is perfect, so is bluetooth, suspend, hibernate, webcam, microphone. No glitches, crashes, corruptions, nothing. It just works! If you decide on trying it, I'd be glad to help out with any issues. Cheers. Regards.
Re: [arch-general] MBP 8, 2: Screen(s) found, but none have a usable configuration
On 01/18/2013 01:50 PM, Martín Cigorraga wrote: On Thu, Jan 17, 2013 at 2:03 PM, D. Can Celasun dcela...@gmail.com wrote: Hi, Brainless software engineer here. I'm using Arch on an iMac 27 + 27 Cinema Display at work and I couldn't be happier. Sure, it took an extra 15 minutes to set it up (compared to a PC) A bit OT here. D.: is there any remarkable difference worth noting between running Arch on PC and on a Mac? I'm thinking in something like heat or some part of the HW not being fully supported like the keyboard or anything else. There's no doubt Apple products stands out because the excellent hardware, one of the main reasons one would argue to install GNU/Linux on them, but as I never tried this and I'm a bit reluctant to mess with HW glitches I would love to hear from an archer running his system on Mac. Regards. When I first got this one in October 2011 the wireless card wasn't yet supported in the latest kernel, so I tried to keep up with the rc releases for a couple of months. I don't usually have a problem working the processor with kernel compiles and virtual machines, so I have noticed a bit of heat (I actually assume that's what caused a screen problem last week). It seems to be running 10 - 15 C cooler now... I don't know if switching to grub-efi from grub-legacy has anything to do with that. - Bryan
Re: [arch-general] Request help with wired network config after initial install and reboot
On Fri, Jan 18, 2013 at 4:14 PM, Mike Cloaked mike.cloa...@gmail.comwrote: On Fri, Jan 18, 2013 at 9:38 AM, William Giokas 1007...@gmail.com wrote: [...] and of course systemctl restart net-auto-wired is required for the service to start after the next and subsequent bootups. I assume you mean `systemctl enable net-auto-wired`, don't you? -- Rodrigo
Re: [arch-general] update to calibre-0.9.15-1
don't remember if my internet connection went dead during the first attempt to update, that happens frequently. but i don't see how that would mess up things -- unless everything is downloaded checked, pacman doesn't do anything. It is common issue when you run as root python program without precompiled pyc/pyo, now pyc/pyo provided by package and conflict with autogenerated.
Re: [arch-general] update to calibre-0.9.15-1
On Fri, Jan 18, 2013 at 2:22 PM, Karol Babioch ka...@babioch.de wrote: Hi, Am 18.01.2013 13:59, schrieb phani: during today's update from calibre 0.9.14-1 - 0.9.15-1, pacman complained that all packages under /usr/lib/calibre/calibre were already existing in the filesystem, and therefore the update couldn't be performed. Not sure what was going over on your side, however the update went smoothly for me. looks to me as if this is some packaging error. don't know enough about arch packaging though to say what exactly went wrong... Looking at the changes done to package, I don't think that this is a packaging error, see [1]. No one that hasn't touched the calibre software will suffer from the existing files. Python (which creates those files when stuff is used) packages now provide compiled bytecode which also saves the users' power, and I think it's a great feature. The downside is that all the *.pyc/*.pyo stuff is in many cases already on disk and it was actually the third hunk in [1] that brought in the change. Look up the bug report [2] that hunk is referring to, which is relevant in this case. There were other such updates in the past for me - and I believe I used some for/rm loop in bash instead of pacman --force. I think top note in [3] was added at some point, which will both impose further cleanness in python packaging and confusion on not-very-savant users in the future. I also agree with pacman in that it should not handle such cases, because that's what using arch means to me. Alternatively, you could have informed yourself about what *.pyc/*.pyo files are and answered your own question. cheers! mar77i [1] https://projects.archlinux.org/svntogit/community.git/log/trunk?h=packages/calibre [2] https://bugs.archlinux.org/task/33392 [3] https://wiki.archlinux.org/index.php/Python_Package_Guidelines#Notes
Re: [arch-general] powernow-k8 fails to load with linux 3.7.2
On Wed, Jan 16, 2013 at 2:17 PM, Leonid Isaev lis...@umail.iu.edu wrote: Neither acpi_cpufreq nor powernow_k8 is loaded automatically which of course leads to failure of all custom units configuring ondemand governor via sysfs. Manually modprob'ing acpi_cpufreq does work and indeed properly scales down the frequancy, but is accompanied by an info-level kernel message acpi-cpufreq: overriding BIOS provided _PSD data. So, if the cpufreq driver works OK for other AMD users, I'll happily blame asus... I also have a Phenom II, and had to create /etc/modules-load.d/acpi.conf, and add acpi to it.
Re: [arch-general] update to calibre-0.9.15-1
On Fri, 18 Jan 2013 19:48:37 +0530, Martti Kühne mysat...@gmail.com wrote: No one that hasn't touched the calibre software will suffer from the existing files. i haven't touched the calibre software -- if that means done any manual changes to it's files. if you mean used the calibre software, that i did. Python (which creates those files when stuff is used) packages now provide compiled bytecode which also saves the users' power, and I think it's a great feature. The downside is that all the *.pyc/*.pyo stuff is in many cases already on disk and it was actually the third hunk in [1] that brought in the change. Look up the bug report [2] that hunk is referring to, which is relevant in this case. There were other such updates in the past for me - and I believe I used some for/rm loop in bash instead of pacman --force. i just moved the not-owned files somewhere else. wouldn't think of using --force unless i knew exactly what was going on. I think top note in [3] was added at some point, which will both impose further cleanness in python packaging and confusion on not-very-savant users in the future. I also agree with pacman in that it should not handle such cases, because that's what using arch means to me. Alternatively, you could have informed yourself about what *.pyc/*.pyo files are and answered your own question. RTFM makes sense to me. study python packaging before asking the list does not. -- phani.
Re: [arch-general] update to calibre-0.9.15-1
On Fri, 18 Jan 2013 19:14:54 +0530, Alexander Bashmakov alex.teor...@gmail.com wrote: It is common issue when you run as root python program without precompiled pyc/pyo, now pyc/pyo provided by package and conflict with autogenerated. the only thing i ran as root was pacman; certainly not calibre. -- phani.
Re: [arch-general] mkinitcpio/fsck.btrfs
On Thu, Jan 17, 2013 at 1:37 PM, Leonardo Dagnino leodag@gmail.com wrote: 2013/1/16 Arno Gaboury arnaud.gabo...@gmail.com On 16/01/13||11:22, Tom Gundersen wrote: Hi Arno, On Tue, Jan 15, 2013 at 12:34 PM, Arno Gaboury arnaud.gabo...@gmail.com wrote: HOOKS=base udev autodetect block lvm2 filesystems fsck usr usbinput shutdown modconf When # mkinitcpio, I get this error: - Running build hook: [fsck] == ERROR: file not found: `fsck.btrfs' == WARNING: No fsck helpers found. fsck will not be run on boot. The initramfs-linux.img is still correct, but I was wondering why this error. As you correctly observe, there is no fsck.btrfs binary. When reading the /usr/lib/initcpio/install/fsck script, it seems to me fsck will add the filesystem name and run /usr/bin/fsck.filesystemame.This will of course translate to fsck.btrfs, which does not exist. /usr/bin/btrfsck is the correct binary. This is not a mistake; the btrfsck binary is not meant to be run automatically at boot as the other fsck.* helpers, it is only meant to be used manually to fix problems. btrfs is designed not to need fsck'ing at boot, but does integrity checking at run-time instead. According to /usr/lib/initcpio/install/btrfs script, the btrfs hook is not needed when using udev. How can I solve this issue? Shall I add the btrfs hook? You could add the btrfs hook, but it would not make a difference for the automatic fsck. What it would give you is the ability to fsck btrfs manually from the initramfs in case of problems (i.e., in case root can not be mounted at all). HTH, Tom Tom, thank you for your clean answer. I will then let this error, as I understand it is more a Warning with no negative impact. Regards. If you want to stop getting that error/warning, you can create fsck.btrfs as a symlink to /bin/true (I think). Regards -- Leonardo Dagnino Am I mistaken in thinking that if you only have btrfs filesystems on a machine, then the fsck hook serves no purpose? Thanks, =-Jameson
Re: [arch-general] update to calibre-0.9.15-1
On Sat, 19 Jan 2013 03:16:58 +0530, phani listm...@phanisvara.com wrote: Alternatively, you could have informed yourself about what *.pyc/*.pyo files are and answered your own question. RTFM makes sense to me. study python packaging before asking the list does not. that probably came across a bit harsh or ungrateful. i do thank you for pointing me into the right direction to understand what's going on. (i've never used python in my life, so these things are new to me.) -- phani.
Re: [arch-general] mkinitcpio/fsck.btrfs
On Jan 18, 2013 4:52 PM, Jameson imntr...@gmail.com wrote: On Thu, Jan 17, 2013 at 1:37 PM, Leonardo Dagnino leodag@gmail.com wrote: 2013/1/16 Arno Gaboury arnaud.gabo...@gmail.com On 16/01/13||11:22, Tom Gundersen wrote: Hi Arno, On Tue, Jan 15, 2013 at 12:34 PM, Arno Gaboury arnaud.gabo...@gmail.com wrote: HOOKS=base udev autodetect block lvm2 filesystems fsck usr usbinput shutdown modconf When # mkinitcpio, I get this error: - Running build hook: [fsck] == ERROR: file not found: `fsck.btrfs' == WARNING: No fsck helpers found. fsck will not be run on boot. The initramfs-linux.img is still correct, but I was wondering why this error. As you correctly observe, there is no fsck.btrfs binary. When reading the /usr/lib/initcpio/install/fsck script, it seems to me fsck will add the filesystem name and run /usr/bin/fsck.filesystemame.This will of course translate to fsck.btrfs, which does not exist. /usr/bin/btrfsck is the correct binary. This is not a mistake; the btrfsck binary is not meant to be run automatically at boot as the other fsck.* helpers, it is only meant to be used manually to fix problems. btrfs is designed not to need fsck'ing at boot, but does integrity checking at run-time instead. According to /usr/lib/initcpio/install/btrfs script, the btrfs hook is not needed when using udev. How can I solve this issue? Shall I add the btrfs hook? You could add the btrfs hook, but it would not make a difference for the automatic fsck. What it would give you is the ability to fsck btrfs manually from the initramfs in case of problems (i.e., in case root can not be mounted at all). HTH, Tom Tom, thank you for your clean answer. I will then let this error, as I understand it is more a Warning with no negative impact. Regards. If you want to stop getting that error/warning, you can create fsck.btrfs as a symlink to /bin/true (I think). Regards -- Leonardo Dagnino Am I mistaken in thinking that if you only have btrfs filesystems on a machine, then the fsck hook serves no purpose? Thanks, =-Jameson This is correct. People who want to add a symlink to /bin/true aren't solving the right problem and are only potentially causing trouble for themselves down the road.
Re: [arch-general] Request help with wired network config after initial install and reboot
On Fri, Jan 18, 2013 at 7:25 PM, Rodrigo Rivas rodrigorivasco...@gmail.comwrote: On Fri, Jan 18, 2013 at 4:14 PM, Mike Cloaked mike.cloa...@gmail.com wrote: On Fri, Jan 18, 2013 at 9:38 AM, William Giokas 1007...@gmail.com wrote: [...] and of course systemctl restart net-auto-wired is required for the service to start after the next and subsequent bootups. I assume you mean `systemctl enable net-auto-wired`, don't you? -- Rodrigo Actually that enables it for next boot - but if it was supposed to start and the configs were wrong and the network is not working - then after fixing the configs I restarted it and it is then running - next boot it should start on its own. -- mike c
