- Arch-general - lists.archlinux.org

Re: [arch-general] linux-tools-meta, why?
by Sébastien Luttringer 20 Feb '13

20 Feb '13

On Wed, Feb 20, 2013 at 1:31 AM, Brock.Zheng <goodmenzy(a)gmail.com> wrote: > Hi all > > I found that package in community, > The pkg has no content. The only file in it's pkg is > a .PKGINFO file: > > $> tar -tf archlinux/community/os/x86_64/linux-tools-meta-3.8-1-x86_64.pkg.tar.xz > .PKGINFO > > Any on know why? > This share purposes of others meta-packages in our repository and others distro. Shortly, it will allow you to follow new split packages addition from linux-tools group. You can find more complete explanation in our wiki[1]. Cheers, [1] https://wiki.archlinux.org/index.php/KDE_Packages#Using_Meta-Packages -- Sébastien "Seblu" Luttringer https://www.seblu.net GPG: 0x2072D77A

1 0

Re: [arch-general] Linux-3.7.3-1-i686 blank screen
by Brian Wood 19 Feb '13

19 Feb '13

Whiskers: > I have installed xf86-video-vesa 2.3.2-2 but while > xf86-video-nouveau > 1.0.6-1 is also installed that seems to be given preference > in the boot > procedure, so I'll remove it and keep my fingers crossed! I experienced similar problems. I wasn't able to start X without xf86-video-nouveau, but had core dumps with it. Now I'm trying an install on another machine with an Intel video card. So far so good, but it hasn't been long enough to tell. I'm new to Arch and have been using another distro for years. Arch has over 60 fewer processes running and less than half as many files in /etc than my old distro had. These things are helpful for me from a sys admin perspective. Thanks for the work done on Arch so far. -- Brian Wood Ebenezer Enterprises - in G-d we trust. http://webEbenezer.net (651) 251-9384

1 0

[arch-general] Linux-3.7.3-1-i686 blank screen
by Whiskers 19 Feb '13

19 Feb '13

I ran pacmatic -Syu last night, which updated the kernel to the version in the subject. This afternoon, the system started to boot normally but the display went blank before the login prompt appeared (I boot to a text login) so I was unable to use the system. I used my original installation disc to boot, and was able to follow the Wiki instructions (accessed using a different computer) to run chroot and downgrade the kernel to 3.6.11-1, and the system is now running again. 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. -- -- ^^^^^^^^^^ -- Whiskers -- ~~~~~~~~~~

6 12

[arch-general] Default directory for extra modules
by Sergi Pons Freixes 19 Feb '13

19 Feb '13

Hi All, I have the vanilla and the PAE kernels installed, and I use latter as my default for booting. I installed tp_smapi, and the modules are placed on /usr/lib/modules/extramodules-3.7-ARCH/ instead of /usr/lib/modules/extramodules-3.7-pae/, so they are not found. Is there anyway to set where the modules should be installed by default (which should be the current running kernel, resulting from uname). Or do I have to work with the PKGBUILD? Cheers, Sergi

2 1

Re: [arch-general] [arch-dev-public] [RFC] Add Wayland/Weston
by Armin K. 16 Feb '13

16 Feb '13

On 02/12/2013 05:51 PM, Tom Gundersen wrote: > On Tue, Feb 12, 2013 at 5:42 PM, Andreas Radke <andyrtr(a)archlinux.org> wrote: >> Am Sat, 9 Feb 2013 17:35:27 +0100 >> schrieb Andreas Radke <andyrtr(a)archlinux.org>: >> >>> Since cairo will also depend on that libegl then every system will >>> pull in Wayland. Is this really needed? If we can't build it in a >>> different way we directly need to move Wayland to extra. >>> >>> -Andy >> >> Bump. >> >> If we agree that we want to start to support Wayland in Arch we need to >> move Wayland libs to the extra repo. Then I can build Mesa making use >> of it in libegl. This shouldn't harm anything else and wayland libs are >> a pretty small pkg (when we drop the static libs). >> >> So who's going to move it to extra and wants to maintain it there? I >> could build it but will not use it myself anytime soon. > > I'll be happy to maintain Wayland, so I'll take it over and move it to [extra]. > > -t > Hello, and thank you for adding Wayland into Extra. There is now another smaller problem. In order to make use of Wayland with GTK+3, libxkbcommon should be moved into extra first. Can anyone do that? Lot of GTK+3 apps can be ran in Weston using GDK_BACKEND=wayland.

7 8

Re: [arch-general] [arch-dev-public] mesa packaging, libGL handling
by Armin K. 15 Feb '13

15 Feb '13

On 02/15/2013 08:27 PM, Jan Steffens wrote: > On Fri, Feb 15, 2013 at 8:16 PM, Sven-Hendrik Haase <sh(a)lutzhaase.com> wrote: >> Can't you build them with shared llvm libs? > > Nope, we don't have any. > > Building LLVM with cmake instead of autotools creates them, but that > approach has other problems. > Actualy, you can. Archlinux uses llvm-amdgpu-snapshot which is Tom Stellard's snapshot. In 9.1-devel, --with-llvm-shared-libs is turned on by default if you use --enable-opencl. On the other side, LLVM contains a shared library, enabled by --enable-shared, called libLLVM-<version>.so (ie libLLVM-3.2.so) located in llvm libdir (/usr/lib/llvm in Archlinux) which contains ALL of static libraries linked into ONE SHARED library. On the other hand, you can use CMake and build all of static libraries as shared. The first mentioned works for me very well. I am not sure what's the condition of that in Mesa 9.0 world. But 9.1 should be out in no time, so it shouldn't matter. Note, this is not from Archlinux. I use custom built system with custom built packages $ ldd /usr/lib/dri/r600_dri.so linux-vdso.so.1 (0x00007fffd47ff000) libllvmradeon9.2.0.so => /usr/lib/libllvmradeon9.2.0.so (0x00007fd514ba8000) libffi.so.6 => /usr/lib/libffi.so.6 (0x00007fd5149a0000) libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007fd514777000) libpthread.so.0 => /lib/libpthread.so.0 (0x00007fd51455b000) libdl.so.2 => /lib/libdl.so.2 (0x00007fd514357000) libdrm.so.2 => /usr/lib/libdrm.so.2 (0x00007fd51414b000) libdrm_radeon.so.1 => /usr/lib/libdrm_radeon.so.1 (0x00007fd513f41000) libLLVM-3.2.so => /usr/lib/llvm/libLLVM-3.2.so (0x00007fd51274d000) $ du -sh /usr/lib/dri/r600_dri.so 5.7M /usr/lib/dri/r600_dri.so $ du -sh /usr/lib/gallium-pipe/pipe_r600.so 2.4M /usr/lib/gallium-pipe/pipe_r600.so (no /usr/lib/gbm/pipe_whatever.so anymore, since pipes are shared by gbm and opencl) Compared to 20MB Archlinux ones.

1 0

[arch-general] Arch handbook as PDF
by Ralf Mardorf 14 Feb '13

14 Feb '13

Hi :) is there an up to date handbook, beginner's guide or even better the Wiki available as PDF? I already found outdated PDFs. Languages: English and/or German I experienced it as very helpful, when installing a *NIX and having a handbook available on a tablet PC. I don't have Internet access for the tablet PC, I only can transmit a PDF by USB. Regards, Ralf PS: Pardon, by accident I send this message to arch-general-owner(a)archlinux.org first.

6 5

[arch-general] System doesn't load LVM volumes when booting in single user mode
by David Rosenstrauch 13 Feb '13

13 Feb '13

Like the subject says, when I boot directly into single user mode, system doesn't load my LVM volumes. So the only way I can realistically use single user mode (since many of my key files are on LVM volumes) is to boot the system to multi-user mode, and the "telinit s" to drop back down to single user. This seems like an error, and that systemd should be starting LVM volumes even in single user mode. Anyone have any idea what the problem might be and/or a workaround? Thanks, DR

2 8

[arch-general] Audio distro based on Arch Linux
by Ralf Mardorf 13 Feb '13

13 Feb '13

Hi :) is there an audio distro based on Arch Linux, that already is rawly set up for audio studio production. Another requirement for me is, that such a distro shouldn't cause or at least only less inconsistencies, when using the Arch and AUR repositories. I suspect http://didjix.blogspot.com isn't intended for audio studios? Perhaps I missed an audio distro listed at https://wiki.archlinux.org/index.php/Arch_Based_Distributions_%28Active%29 ;) when I searched for "music" and "audio" on this site. If there shouldn't be an audio distro, I'll install a _real_ Arch Linux :(, ;). Resp., is one of the distros that come with Xfce by default uncritical regarding to the used packages (dependency issues)? And will one of those distros install not to much services etc. that I would have to remove for audio work? Regards, Ralf

5 6

[arch-general] Problem with NFS on shutdown
by Paul Marwick 13 Feb '13

13 Feb '13

I've got two machines in my local network that provide NFS shares. One is an old Raidsonic NAS (running a current version of OpenWRT), the other a dedicated server running Slackware). I normally mount the shares manually (the machine that is giving me a problem is a laptop, so its often not connected to my own network). The problem comes when I try to shut the laptop down (or restart it). Unless I've manually unmounted the NFS shares, the machine will hang and fail to shut down. In some instances, I've been able to use CTRL-C to break out of the stall, but frequently, I can only turn the machine off, which is not exactly ideal. I've been playing with the nfs exports, currently have the following: /mnt/sda2/stor 192.168.1.0/255.255.255.0(rw,sync,no_wdelay,nohide,no_root_squash) (this is on the Raidsonic) and /mnt/sda2/stor 192.168.1.0/255.255.255.0(rw,sync,no_wdelay,nohide,no_root_squash) on the Slackware server. The problem is specific to Arch - I've got two other distros installed on the laptop (though Arch is my usual OS). From SalineOS or Salix, the laptop will shut down or restart without having to manually unmount the NFS shares prior to shutdown. I suspect I've not got something set up correctly in systemd, but I'm currently at a loss to work out what. If I manually unmount the shares before shutdown, there is no problem. I've also tried adding the unmount to /etc/rc.local.shutdown, but that doesn't work - the system still hangs during shutdown. I'm sure that rc.local.shutdown is being executed - if I shut down without the shares mounted, I can see messages that they are not mounted. I'm not sure if I should be looking at the NFS export parameters on the hosts, or systemd on the laptop, though I've tried some variations on the exports without changing the behaviour. Does anyone know what I should be looking at to solve this? Paul.

4 5