Re: [arch-general] Why does virtualbox-host-dkms have a hard dependency on linux-headers?

Eric Engestrom wrote: > Regarding your log, it looks to me like you have both the default and > LTS kernels installed, but only have the source for the LTS, so you're > only building the module for LTS. Nope. I only have the LTS kernel installed. linux-headers was pulled in this morning as a

Re: [arch-general] Why does virtualbox-host-dkms have a hard dependency on linux-headers?

Hi, It looks like a mistake (on lines 249 and 276 on the PKGBUILD) was introduced in commit b79afc2b72b306753b75ec600e1757e77735abf9: https://projects.archlinux.org/svntogit/community.git/commit/trunk/PKGBUILD?h=packages/virtualbox=b79afc2b72b306753b75ec600e1757e77735abf9 I've CC'ed Seblu on

Re: [arch-general] Why does virtualbox-host-dkms have a hard dependency on linux-headers?

PS: On Sun, 13 Mar 2016 11:01:30 -0700, Kyle Terrien wrote: >Why I guess the maintainer tries to make it as comfortable for us as possible. Now all old modules are removed and the modules for all installed kernels are build automatically. This is new, it didn't happen before. Fortunately I'm

Re: [arch-general] Why does virtualbox-host-dkms have a hard dependency on linux-headers?

[rocketmouse@archlinux ~]$ pacman -Qi virtualbox-host-dkms | grep Depends Depends On : dkms gcc make linux-headers That's bad. Now that you mention it, I guess no pacman.conf workaround or empty dummy package would prevent trying to build the modules, it just would prevent installing the

[arch-general] Why does virtualbox-host-dkms have a hard dependency on linux-headers?

Hello, I upgraded my desktop about 10 minutes ago, and it looks like virtualbox-host-dkms gained a new dependency: linux-headers. On this desktop, I have only the linux-lts kernel and its accompanying linux-lts-headers installed, so why is linux-headers necessary? In the pacman -Syu output, it

Re: [arch-general] mount shows hardcoded stripe=4 mount option for ext* /boot fs

I may be way off on this but I did a grep on /etc for stripe and found the reference was in /etc/lvm/lvm.conf and since you said you had logical volumes I thought perhaps this might help. Google'ng ext4 options returns some useful info as well. Something about allocation of blocks. Regards

Re: [arch-general] mount shows hardcoded stripe=4 mount option for ext* /boot fs

Sun, 13 Mar 2016 15:41:44 +0100 Jens Adam : Can you show the output of 'lvdisplay -v /dev/mapper/boot-arch' and 'tune2fs -l /dev/mapper/boot-arch' ? Sure thing: # lvdisplay -v /dev/mapper/boot-arch --- Logical volume --- LV Path/dev/boot/arch LV Namearch

Re: [arch-general] mount shows hardcoded stripe=4 mount option for ext* /boot fs

Sun, 13 Mar 2016 15:27:39 +0100 Bastien Traverse : > [...] Hm, interesting indeed. Can you show the output of 'lvdisplay -v /dev/mapper/boot-arch' and 'tune2fs -l /dev/mapper/boot-arch' ? --byte

[arch-general] mount shows hardcoded stripe=4 mount option for ext* /boot fs

I first stumbled upon this two years ago and opened a thread in the forum to ask about it [1]. I never got an answer but lived happy and forgetful about it, until some days ago another user PMed me to know if I had ever found out why mount consistently showed `stripe=4` as a mount option for

Re: [arch-general] NOTE: Intel users: don't install lastest Xorg 1.18.2 update. Whole desktop freeze after while of using.

On Saturday, 12 March 2016 20:17:53 CET Tomasz Przybył wrote: > Hello > > I was affected serious issue from lastest Xorg update 1.18.2 (current in > testing). Whole desktop freeze. Keyboard and mouse not working. Only > pressing while power btn shutdown device. > > Reverting to 1.18.1 is safe.