January 2013 - Arch-general - lists.archlinux.org

[arch-general] broken system after today upgrade
by arnaud gaboury 24 Jan '13

24 Jan '13

Dear list, testing repo is enabled on my box. Today upgrade of glibc, filesystem and Linux failed and leaves me with an unbootable machine. I boot with Archiso, then mount /, /boot and /user on /mnt/. From this directory, I then #pacman -Syu linux glibc filesystem with no success. Get excv unfound. I downgraded these 3 packages, then try again. It went with no errors. Booting my box leaves me to a Kernel panic with init not found. My grub config is clean and don't know why I should pass any extra kernel parameter. How can I deal with this issue? Thank you for help as my box is my working tool

11 19

[arch-general] [systemd] udevd and udevadm not found in initramfs when using systemd-git
by William Giokas 24 Jan '13

24 Jan '13

All, I rebooted my computer today to test some boot flags only to be greeted with an unbootable machine. Here is a transcript of the boot messages: /init: line 9: systemd-timestamp: not found :: running early hook [udev] /init: line 21: udevd: not found :: running hook [udev] :: Triggering uevents... /init: line 21: udevadm: not found /init: line 21: udevadm: not found /init: line 21: udevadm: not found Waiting 10 seconds for device /dev/sda2... ERROR: device '/dev/sda2' not found. Skipping fsck. ERROR: Unable to find root device '/dev/sda2'. And then I am dropped to a root shell. Attached is my mkinitcpio.conf[1]. This only happens when using an initramfs generated with systemd-git. I built this this image[1] using mkinitcpio 0.12.0.15.g1fb6722. I am also using linux-mainline, but that does not seem to have any effect when downgrading or using a different kernel. If I downgrade systemd to 197, however, rebuild the image and reboot, it goes smoothly. Shutting down my computer cleanly is also an impossibility, as `systemctl poweroff` just hangs with no messages printed. This does not happen with 197. Also attached are the pacman -Ql outputs of my systemd-git[3] and [core]s systemd[4], as well as the mkinitcpio -v output[5]. [1] http://ix.io/46o [2] http://ompldr.org/vaDdobQ/initramfs-linux-mainline.img [3] http://ix.io/46n [4] http://ix.io/46m [5] http://ix.io/46l Thank you, -- William Giokas | KaiSforza GnuPG Key: 0xE99A7F0F Fingerprint: F078 CFF2 45E8 1E72 6D5A 8653 CDF5 E7A5 E99A 7F0F

2 1

Re: [arch-general] Drop VI from [core] (was Re: Winter Cleanup of [community])
by Greg Bouzakis 24 Jan '13

24 Jan '13

Stéphane Gaudreault wrote: > Le 2013-01-24 07:21, Allan McRae a écrit : >> On 24/01/13 22:08, Alexander Rødseth wrote: >>> === [core] === >>> >>> For [core], there are two uneeded orphans, that also aren't make >>> dependencies for any other [core] packages: >>> >>> openldap >>> vi >>> >>> If I may be so bold, maybe vim or another editor (still providing the >>> "vi" command) could take over for the vi package? >> I agree with just dumping vi and moving [vim] to core... But we can not >> put split packages across repos and gvim and deps are not going there so >> that is a no... > > Moving to another thread for clarity. > > +1 to drop vi. I cannot imagine why someone would want to use this crap > ... > > We already have nano in [core], so I think that vim could stay in > [extra] (do we really need 2 text editors in [core] ?). > FWIW this is the original discussion which brought this crippled vi upon us https://bugs.archlinux.org/task/13109 but more importantly https://bugs.archlinux.org/task/13239 Do vim and gvim really have to share the same PKGBUILD? I would be in favour of having a proper modern vim implementation in core no matter what its name would be. The only downside is that vim would need signoffs. I think that if a different PKGBUILD is used for gvim then gvim wouldn't need those as well. Greg

1 0

Re: [arch-general] [arch-dev-public] Drop VI from [core] (was Re: Winter Cleanup of [community])
by Paul Gideon Dann 24 Jan '13

24 Jan '13

On Thursday 24 Jan 2013 11:05:22 Stéphane Gaudreault wrote: > +1 to drop vi. I cannot imagine why someone would want to use this crap ... > > We already have nano in [core], so I think that vim could stay in > [extra] (do we really need 2 text editors in [core] ?). Vi is the standard UNIX text-editor. Many admins rely on the fact that vi is available everywhere. It really should be in core. Also, I know you might be referring to "plain vi", which is a completely different beast to Vim, but the latter (which provides "vi" too) has a *huge* userbase. Calling it crap is just bizarre... Paul

4 3

Re: [arch-general] Linux-3.7.3-1-i686 blank screen
by Jean-Marie Duprez 24 Jan '13

24 Jan '13

On Tue, 22 Jan 2013 21:07:56 +0000 Whiskers <catwheezel at operamail.com <https://mailman.archlinux.org/mailman/listinfo/arch-general>> wrote: >* On Tue, 22 Jan 2013 19:25:45 +0100 Karol Babioch <karol at babioch.de <https://mailman.archlinux.org/mailman/listinfo/arch-general>> wrote:*>* *>* >Hi,*>* >*>* >Am 22.01.2013 18:34, schrieb Whiskers:*>* >> An 'unconfirmed' bug is listed at <https://bugs.archlinux.org/> but this*>* >> seems to relate to vlc segfaulting with the new kernel, so I don't know*>* >> if that's the same problem affecting me.*>* >*>* >No, that's almost certainly another issue.*>* >*>* >You may want to try 3.7.4-1 from testing. If that doesn't fix your*>* >issue, you are probably best off to contact upstream directly. With*>* >Linux 3.7 there was quite some restructuring of the graphics stack going*>* >on, so it may well be that in some cases it breaks things.*>* >*>* >Best regards,*>* >Karol Babioch*>* >*>* *>* *>* I'm using the Nouveau video driver with an old laptop. As Linux-3.6.11-1*>* seems to be stable for me, I'll wait for the next kernel version to reach*>* the core repository. * If you're talking about 3.7.4, then it's unlikely to fix your issue, because there are only radeon fixes in the changeloghttp://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.7.4. >* *>* I'll also try to work out how to have the previous kernel still available*>* to Grub-legacy after the next kernel upgrade.*>* *>* For the record, this is what my video hardware says it is:*>* *>* $ lspci | grep VGA*>* 01:00.0 VGA compatible controller: NVIDIA Corporation NV31M [GeForce FX*>* Go5600] (rev a1)*>* *Hi, I have exactly the same problem with a DELL LATITUDE D800 (a good old machine of 2004 which accomode very well of ARchlinux !). Until now I had no difficulty with kernels 3.6 or LTS. With the kernel 3.7.4, the system started to boot normally but the display went blank before the login prompt appeared ! By precaution, I always have an installed linus-lts what allowed me to return quickly to the version 3.6. which works correctly. I'm using the Nouveau video driver (last release) and my video harware is : VGA compatible controller: NVIDIA Corporation NV34M [GeForce FX Go5200 64M] (rev a1) Regards ! Jean-Marie Duprez

1 0

Re: [arch-general] failed to set xfermode on multiple disks SOLVED
by Jameson 24 Jan '13

24 Jan '13

On Tue, Jan 22, 2013 at 2:50 PM, Jameson <imntreal(a)gmail.com> wrote: > On Mon, Jan 21, 2013 at 6:11 PM, Jameson <imntreal(a)gmail.com> wrote: >> On Mon, Jan 21, 2013 at 12:38 AM, Martín Cigorraga <msx(a)archlinux.us> wrote: >>> On Mon, Jan 21, 2013 at 12:33 AM, Jameson <imntreal(a)gmail.com> wrote: >>> >>>> I hope someone can help me. I have a server with two SSDs that >>>> contain a mirrored btrfs volume holding /, and multiple HDDs that are >>>> in a btrfs RAID10 array. I updated to linux 3.7.3 in testing, and it >>>> failed to boot. I booted from a USB drive, and reinstalled 3.6.?, and >>>> I still get failed to set xfermode (err_mask=0x40). I don't see >>>> anything in dmesg that makes a difference. The only thing that >>>> changed was the kernels, back and forth. Does anyone have an idea, or >>>> am I going to have to re-install? Thanks. >>>> >>> >>> Hi Jameson, a blind shot here since I'm not familiar yet with SSD setups: >>> did you tried running a fsck? In the past I had a similar situation with >>> conventional hard disks and the problem was some corrupted data in /boot. >>> >>> Hope you have your beast up soon! >> >> Yes. I had actually forgotten that I had a separate ext4 boot >> partition. I've ran fsck on it as well as btrfsck on my mirrored >> root, and my raid10 array. All return fine. During boot, between >> some of the xfermode errors, I can see the message where it is looking >> for btrfs file systems, and then a repair console which says that the >> root filesystem can't be found which doesn't respond for some reason. >> I'll try to find another keyboard to see if it will make a difference. >> I did another install of of the old 3.6 kernel, and noticed that it >> threw an error about not being able to find the root filesystem at >> that point also. Any further diagnostic advice will be appreciated. > > Also, it turns out changing USB keyboards makes no difference. I > don't think I have a PS/2 keyboard, anymore. I've currently copied > all of my data from my SSD array to a HDD, and plan on trying to get > it to boot. I've successfully ran mkinitcpio and grub-mkconfig from a > chroot on the HDD which did not return the error about not finding the > root filesystem, so I'm hopeful it will at least get me back up and > running. I forgot to grub-install, though, so I'll have to wait until > I get home to test it. In case anyone else runs into this, I needed to patch the kernel with the patch provided in this bug: https://bugzilla.kernel.org/show_bug.cgi?id=51881

1 0

[arch-general] vboxnetflt module broken in virtualbox-host-modules-lts?
by David Rosenstrauch 23 Jan '13

23 Jan '13

I'm running the LTS kernel, and VirtualBox has been working fine under it until recently. However sometime in the last few days (after a recent upgrade, I'm guessing), I can no longer launch VM's. Apparently vboxnetflt is never getting loaded. And when I try to load it manually, I get the following error: [darose@daroselin ~]$ sudo modprobe vboxnetflt modprobe: ERROR: could not insert 'vboxnetflt': Invalid argument Anyone know what the problem might be? I didn't see any bug reports about this. Does the virtualbox-host-modules-lts need to be upgraded perhaps? Thanks, DR

3 2

[arch-general] Avermedia Volar Green A835
by Δημήτρης Ζέρβας 22 Jan '13

22 Jan '13

I am trying to make avertv a835 work. I tried this (found in gentoo forums): cd /lib/firmware sudo wget http://xgazza.altervista.org/Linux/DVB/dvb-usb-af9035-01.fw cd ~ mkdir TV cd TV wget http://xgazza.altervista.org/Linux/DVB/Drivers/AF9035_xgaz_3.0.0.tar.bz2 tar -xjf AF9035_xgaz_3.0.0.tar.bz2 cd AF9035_xgaz_3.0.0 make sudo make install I replaced linux-headers with linux in the Makefile, but I can't compile it, I get error in include/dvb_frontend.h

1 0

Re: [arch-general] failed to set xfermode on multiple disks (Was: Busted Server)
by Jameson 22 Jan '13

22 Jan '13

On Mon, Jan 21, 2013 at 12:38 AM, Martín Cigorraga <msx(a)archlinux.us> wrote: > On Mon, Jan 21, 2013 at 12:33 AM, Jameson <imntreal(a)gmail.com> wrote: > >> I hope someone can help me. I have a server with two SSDs that >> contain a mirrored btrfs volume holding /, and multiple HDDs that are >> in a btrfs RAID10 array. I updated to linux 3.7.3 in testing, and it >> failed to boot. I booted from a USB drive, and reinstalled 3.6.?, and >> I still get failed to set xfermode (err_mask=0x40). I don't see >> anything in dmesg that makes a difference. The only thing that >> changed was the kernels, back and forth. Does anyone have an idea, or >> am I going to have to re-install? Thanks. >> > > Hi Jameson, a blind shot here since I'm not familiar yet with SSD setups: > did you tried running a fsck? In the past I had a similar situation with > conventional hard disks and the problem was some corrupted data in /boot. > > Hope you have your beast up soon! Yes. I had actually forgotten that I had a separate ext4 boot partition. I've ran fsck on it as well as btrfsck on my mirrored root, and my raid10 array. All return fine. During boot, between some of the xfermode errors, I can see the message where it is looking for btrfs file systems, and then a repair console which says that the root filesystem can't be found which doesn't respond for some reason. I'll try to find another keyboard to see if it will make a difference. I did another install of of the old 3.6 kernel, and noticed that it threw an error about not being able to find the root filesystem at that point also. Any further diagnostic advice will be appreciated. Thanks, =-Jameson

1 1

[arch-general] Upgrade to linux-3.7.3: system freezes on certain actions in X
by Alain Kalker 22 Jan '13

22 Jan '13

Hardware Info: System: Host: miki-desktop Kernel: 3.6.11-1-ARCH x86_64 (64 bit, gcc: 4.7.2) Desktop: LXDE (Openbox 3.5.0) Distro: Arch Linux Machine: Mobo: FUJITSU SIEMENS model: MS-7504VP version: 1.0 Bios: American Megatrends version: V1.16 date: 08/11/2008 CPU: Dual core Intel Core2 Duo CPU E7500 (-MCP-) cache: 3072 KB flags: (lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 11738.2 Clock Speeds: 1: 1603.00 MHz 2: 1603.00 MHz Graphics: Card: NVIDIA C73 [GeForce 7050 / nForce 630i] bus-ID: 00:10.0 X.Org: 1.13.1 drivers: nouveau (unloaded: fbdev,nv,vesa) Resolution: 1600x900(a)60.0hz GLX Renderer: Gallium 0.4 on NV63 GLX Version: 2.1 Mesa 9.0.1 Direct Rendering: Yes After the upgrade to linux-3.7.3-1, my system began freezing frequently after certain actions (opening a new browser window, switching windows, etc.) The system became totally unresponsive (no Magic SysRq, no response from network). Investigating a little further, I found I could reliably reproduce the freeze by running '$ glxinfo' (occasionally had to repeat it a few times). Downgrading to linux-3.6.11-1 resolved the problem. I'm not reporting this as a bug yet, since linux-3.7.3-1 is marked as out-of-date (linux-3.7.4-1 is in [testing]), this is just a heads-up for other people experiencing the same issue. Regards, Alain

1 0