Re: [gentoo-user] Codeblocks Fails to Exit Cleanly in Awesome WM
On Tue, Aug 15, 2017 at 10:28 AM, Dutch Ingraham wrote: > Specifically, when exiting in any manner, the GUI will disappear, > but the Codeblocks process continues to run. > Maybe related to https://github.com/awesomeWM/awesome/issues/1193?
Re: [gentoo-user] Install on ZFS
>>I'm trying to get started on my first Gentoo install on ZFS. My >>remote server is booted to a Gentoo LiveCD and I've SSH'ed in but it >>looks like the CD doesn't have ZFS tools: >> >>livecd ~ # zpool status >>-bash: zpool: command not found >> >>Can I pull this off from here or do I need to mail a different CD to my >>host? >> >>This server has 6 SSDs and I'm planning to set up a 2-way stripe and >>3-way mirror. Any tips that might help me pull this off? >> >>- Grant > > I did this not too long ago, using the boot disc and howto from FearedBliss: > https://wiki.gentoo.org/wiki/User:Fearedbliss This looks like a great guide. Are there instructions for extracting a portage archive over my running LiveCD OS so I can then emerge zfs and execute this guide without mailing another CD-R to my host? - Grant
Re: [gentoo-user] zfs emerge failure
On Tue, Aug 15, 2017 at 6:51 PM, Rich Freeman wrote: > > Yes, and in fact it is in the output when emerge fails: > /var/tmp/portage/sys-kernel/spl-0.7.1/work/spl-0.7.1/config.log Ah-ha! I see it now. That['s valuable, and I'll take a closer look. Thanks! John
Re: [gentoo-user] zfs emerge failure
On Tue, Aug 15, 2017 at 6:54 PM, John Covici wrote: > What is your umask? I had troubles like this when I had too > aggressive umask of I think 027 rather than 022. It is indeed 027, and I wondered whether that might have been what was behind the error, hence I tried chmod -R 777 the entire kernel tree. But maybe that mask is doing something nasty during the actual config step apart from the kernel tree. I'll try backing off the umask. Thanks! John
Re: [gentoo-user] zfs emerge failure
On Tue, 15 Aug 2017 18:46:59 -0400, John Blinka wrote: > > On Tue, Aug 15, 2017 at 6:04 PM, Rich Freeman wrote: > > First, I appreciate your thoughts and comments. > > > > > I suspect your sources have gotten messed up in some way. I've run > > into issues like this when I do something like build a kernel with an > > odd umask so that the portage user can't read the files it needs to > > build a module. Your chmod should have fixed that but there could be > > something else going on. It might just be that you didn't prepare the > > sources? > > Same thought occurred to me, hence the chmod. Not sure what "prepare > the sources" is all about; not a step I've ever used with kernels. > But see below. > > > > > I actually do all my kernel builds in a tmpfs under /var/tmp these > > days which keeps my /usr/src/linux pristine. (make O=/var/tmp/linux > > modules_install and so on) It does involve more building during > > upgrades but I know everything is clean, and I prefer no-issues to > > faster-builds. > > I have the same preference. Will have to take a look at following > your example.. > > > > > In theory that isn't essential, but I would definitely just wipe out > > /usr/src/linux and unpack clean kernel sources. If you're using the > > gentoo-sources package you can just rm -rf the symlink and the actual > > tree, and just re-emerge the package and it will set up both. If > > you're using git then I'd probably wipe it and re-pull as I'm not sure > > if a clean/reset will actually take care of all the permissions. > > > > Then you need to run at least make oldconfig and make modules_prepare > > before you can build a module against it. Doing a full kernel build > > is also fine. > > I think I've done that (multiple times over the past 8 months). When > a new kernel shows up as stable in the tree, I do (as root) > > emerge -DuNv gentoo-sources > set up symlink > cd into usr/src/linux > zcat /proc/config.gz > .config > make olddefconfig > make menu_config (as a sanity check) > make > make modules_install > make install > > I don't know what could have messed up the kernel tree other than > whatever magic happens behind the scenes in the various make commands. > > Just now tried a make modules_prepare followed by an emerge -1 spl. Same > error. > > Started again from scratch. Moved the kernel tree I've been working > with (building kernel, modules, etc.) aside, then re-emerged > gentoo-sources. Kernel tree should be pristine now, right? Then > copied the config from my running kernel (same version 4.12.5) into > /usr/src/linux. Then did a make modules_prepare. Finally did an > emerge -1 spl. Same error as always. So, as attractive as the idea > of a messed up kernel tree is to me, I don't think that's the source > of the problem. > > I think it would be informative if I could somehow see exactly what > commands are being run when the error occurs. Is there a way of doing > that? What is your umask? I had troubles like this when I had too aggressive umask of I think 027 rather than 022. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] zfs emerge failure
On Tue, Aug 15, 2017 at 3:46 PM, John Blinka wrote: > > I think it would be informative if I could somehow see exactly what > commands are being run when the error occurs. Is there a way of doing > that? > Yes, and in fact it is in the output when emerge fails: /var/tmp/portage/sys-kernel/spl-0.7.1/work/spl-0.7.1/config.log -- Rich
Re: [gentoo-user] zfs emerge failure
On Tue, Aug 15, 2017 at 6:04 PM, Rich Freeman wrote: First, I appreciate your thoughts and comments. > > I suspect your sources have gotten messed up in some way. I've run > into issues like this when I do something like build a kernel with an > odd umask so that the portage user can't read the files it needs to > build a module. Your chmod should have fixed that but there could be > something else going on. It might just be that you didn't prepare the > sources? Same thought occurred to me, hence the chmod. Not sure what "prepare the sources" is all about; not a step I've ever used with kernels. But see below. > > I actually do all my kernel builds in a tmpfs under /var/tmp these > days which keeps my /usr/src/linux pristine. (make O=/var/tmp/linux > modules_install and so on) It does involve more building during > upgrades but I know everything is clean, and I prefer no-issues to > faster-builds. I have the same preference. Will have to take a look at following your example.. > > In theory that isn't essential, but I would definitely just wipe out > /usr/src/linux and unpack clean kernel sources. If you're using the > gentoo-sources package you can just rm -rf the symlink and the actual > tree, and just re-emerge the package and it will set up both. If > you're using git then I'd probably wipe it and re-pull as I'm not sure > if a clean/reset will actually take care of all the permissions. > > Then you need to run at least make oldconfig and make modules_prepare > before you can build a module against it. Doing a full kernel build > is also fine. I think I've done that (multiple times over the past 8 months). When a new kernel shows up as stable in the tree, I do (as root) emerge -DuNv gentoo-sources set up symlink cd into usr/src/linux zcat /proc/config.gz > .config make olddefconfig make menu_config (as a sanity check) make make modules_install make install I don't know what could have messed up the kernel tree other than whatever magic happens behind the scenes in the various make commands. Just now tried a make modules_prepare followed by an emerge -1 spl. Same error. Started again from scratch. Moved the kernel tree I've been working with (building kernel, modules, etc.) aside, then re-emerged gentoo-sources. Kernel tree should be pristine now, right? Then copied the config from my running kernel (same version 4.12.5) into /usr/src/linux. Then did a make modules_prepare. Finally did an emerge -1 spl. Same error as always. So, as attractive as the idea of a messed up kernel tree is to me, I don't think that's the source of the problem. I think it would be informative if I could somehow see exactly what commands are being run when the error occurs. Is there a way of doing that? John
Re: [gentoo-user] zfs emerge failure
On Tue, Aug 15, 2017 at 5:19 PM, John Blinka wrote: > > Hope someone can shed some light on continuing emerge failures for zfs > since gnetoo-sources-4.4.39 and zfs-0.6.5.8. I was able to install > that version of zfs with that kernel last November on one of my > machines, but have been unable to upgrade zfs since then, or to > install it in any newer kernel, or even to re-install the same version > on the same kernel. I've been running various zfs+4.4.y versions without issue on a stable amd64 config (using upstream kernels). Currently I'm on 0.7.1+4.4.82. > checking kernel source version... Not found > configure: error: *** Cannot find UTS_RELEASE definition. > ... > > Googling around for the "Cannot find UTS_RELEASE" complaint reveals > that a few people have encountered this problem over the years. It > appeared in those cases to be attributable to the user running the > configuration script not having sufficient authority to read > ./include/generated/utsrelease.h in the kernel tree. I suspect your sources have gotten messed up in some way. I've run into issues like this when I do something like build a kernel with an odd umask so that the portage user can't read the files it needs to build a module. Your chmod should have fixed that but there could be something else going on. It might just be that you didn't prepare the sources? I actually do all my kernel builds in a tmpfs under /var/tmp these days which keeps my /usr/src/linux pristine. (make O=/var/tmp/linux modules_install and so on) It does involve more building during upgrades but I know everything is clean, and I prefer no-issues to faster-builds. In theory that isn't essential, but I would definitely just wipe out /usr/src/linux and unpack clean kernel sources. If you're using the gentoo-sources package you can just rm -rf the symlink and the actual tree, and just re-emerge the package and it will set up both. If you're using git then I'd probably wipe it and re-pull as I'm not sure if a clean/reset will actually take care of all the permissions. Then you need to run at least make oldconfig and make modules_prepare before you can build a module against it. Doing a full kernel build is also fine. -- Rich
[gentoo-user] zfs emerge failure
Hi, Gentoo, Hope someone can shed some light on continuing emerge failures for zfs since gnetoo-sources-4.4.39 and zfs-0.6.5.8. I was able to install that version of zfs with that kernel last November on one of my machines, but have been unable to upgrade zfs since then, or to install it in any newer kernel, or even to re-install the same version on the same kernel. Emerge fails consistently in the configuration phase for spl with the following snippet in the log: checking kernel source directory... /usr/src/linux checking kernel build directory... /lib/modules/4.12.5-gentoo/build checking kernel source version... Not found configure: error: *** Cannot find UTS_RELEASE definition. !!! Please attach the following file when seeking support: !!! /var/tmp/portage/sys-kernel/spl-0.7.1/work/spl-0.7.1/config.log * ERROR: sys-kernel/spl-0.7.1::gentoo failed (configure phase): * econf failed * * Call stack: * ebuild.sh, line 115: Called src_configure * environment, line 3831: Called autotools-utils_src_configure * environment, line 614: Called econf '--docdir=/usr/share/doc/spl-0.7.1' '--bindir=/bin' '--sbindir=/sbin' '--with-config=all' '--with-linux=/usr/src/linux' '--with-linux-obj=/lib/modules/4.12.5-gentoo/build' '--disable-debug' *phase-helpers.sh, line 665: Called __helpers_die 'econf failed' * isolated-functions.sh, line 117: Called die * The specific snippet of code: * die "$@" Googling around for the "Cannot find UTS_RELEASE" complaint reveals that a few people have encountered this problem over the years. It appeared in those cases to be attributable to the user running the configuration script not having sufficient authority to read ./include/generated/utsrelease.h in the kernel tree. As far as I can tell, I think I ought to have sufficient permission to read that file. I've gone so far as to chmod 777 the entire kernel tree to ensure sufficient access. No luck with that "solution": same error. I've tried strace on emerge to see if I could figure out what it's doing when it's looking for UTS_RELEASE, but no luck with that either. Nothing that I can find in Bugzilla, either, although that could be due to inexperience in using it. Any idea what could be going on, or how I could go about debugging it more effectively? Thanks, John Blinka
Re: [gentoo-user] efibootmgr "Could not prepare Boot variable: Read-only file system"
On Tuesday 15 Aug 2017 16:02:19 Mike Gilbert wrote: > On Tue, Aug 15, 2017 at 2:17 PM, Rich Freeman wrote: > > On Tue, Aug 15, 2017 at 11:04 AM, Mick wrote: > >> I can't recall if I did this myself in a moment of security induced > >> inspiration. I doubt I did. So how did this happen? What is > >> responsible for mounting this fs? > > > > It looks like this never did turn into a news item: > > https://archives.gentoo.org/gentoo-dev/message/35304b0db4de9e06fea32227537 > > 9fa81 > > > > You can remount it as rw if your tools don't do it automatically. It > > might not hurt to file a bug if one doesn't already exist for the tool > > that isn't remounting it. > > Please bother efibootmgr upstream about it, or bother the OpenRC > maintainer who decided to break things. Thank you Rich, I suspected it was an intentional change and from a security perspective it is to be commended. However, it could cause uninformed users like myself some lost time, thinking something may have gone wrong on our system. I submitted bug #627964: https://bugs.gentoo.org/show_bug.cgi?id=627964 I think a news item although useful, on its own is not sufficient. If remounting 'rw' and back again to 'ro' is not performed by the legit commands which touch efivars (e.g. efibootmgr, GRUB, et al), the HandBook should also be amended if it hasn't been already, because newbies will have one more excuse to pack it in and go back to *buntu. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: kernel linux-4.12.5-gentoo & virtualbox-modules-5.0.40
On Tuesday 15 Aug 2017 16:14:21 Rich Freeman wrote: > On Tue, Aug 15, 2017 at 4:08 PM, R0b0t1 wrote: > > On Tue, Aug 15, 2017 at 2:10 PM, Rich Freeman wrote: > >> I do suggest using libvirt, and found that > >> app-emulation/virt-manager gives you a lot of the benefits of > >> something with a pretty GUI like Virtualbox, but it is 100% FOSS > >> underneath and you can run it all from the command line too. It is > >> just a front-end to libvirt. There are no issues with running these > >> VMs as services also, and I believe that you can connect to their > >> consoles at any time with virt-manager. > > > > My only issue is that when I used libvirt I had to edit the produced > > configurations by hand, and the settings wouldn't always take. Certain > > hardware configurations were also hard to set up. > > This is why I use virt-manager. Granted, like most GUI tools there > are probably some settings you can only get at in the config files, > but it seems at least as capable as Virtualbox. You can always > hand-edit configs but you probably won't bother. > > > However, should everything work it is very nice, and can do things > > like start your VMs on boot and create tap devices on demand, etc. > > And that is what I like about it. Since virt-manager is just a GUI on > top of libvirt you can set up VMs and edit them with the GUI, but > still do all this kind of stuff from the command line when you want > to, or from a service/etc. > > And if you use systemd I'm pretty sure there are units for all of that > stuff, and it interacts with machinectl, but that is just an > integration and you don't need systemd to use libvirt. Systemd itself > is mostly just a front-end to libvirt when doing this stuff, and that > is the power behind the concept - one API for a bunch of tools. I've been using QEMU on my laptop which has KVM capability and it's performance is impressive. QEMU without KVM is rather pedestrian, but the same applies to VirtualBox. I have not yet compared QEMU Vs VirtualBox on the same machine to know how they fare. I do not use libirt or virt-manager, but I installed AQEMU for a GUI front end and it seems to work quite satisfactorily when creating VMs, editing their settings, etc. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: kernel linux-4.12.5-gentoo & virtualbox-modules-5.0.40
On Tue, Aug 15, 2017 at 4:08 PM, R0b0t1 wrote: > On Tue, Aug 15, 2017 at 2:10 PM, Rich Freeman wrote: > >> I do suggest using libvirt, and found that >> app-emulation/virt-manager gives you a lot of the benefits of >> something with a pretty GUI like Virtualbox, but it is 100% FOSS >> underneath and you can run it all from the command line too. It is >> just a front-end to libvirt. There are no issues with running these >> VMs as services also, and I believe that you can connect to their >> consoles at any time with virt-manager. >> > > My only issue is that when I used libvirt I had to edit the produced > configurations by hand, and the settings wouldn't always take. Certain > hardware configurations were also hard to set up. > This is why I use virt-manager. Granted, like most GUI tools there are probably some settings you can only get at in the config files, but it seems at least as capable as Virtualbox. You can always hand-edit configs but you probably won't bother. > However, should everything work it is very nice, and can do things > like start your VMs on boot and create tap devices on demand, etc. > And that is what I like about it. Since virt-manager is just a GUI on top of libvirt you can set up VMs and edit them with the GUI, but still do all this kind of stuff from the command line when you want to, or from a service/etc. And if you use systemd I'm pretty sure there are units for all of that stuff, and it interacts with machinectl, but that is just an integration and you don't need systemd to use libvirt. Systemd itself is mostly just a front-end to libvirt when doing this stuff, and that is the power behind the concept - one API for a bunch of tools. -- Rich
Re: [gentoo-user] Re: kernel linux-4.12.5-gentoo & virtualbox-modules-5.0.40
On Tue, Aug 15, 2017 at 2:10 PM, Rich Freeman wrote: > On Tue, Aug 15, 2017 at 3:02 PM, R0b0t1 wrote: >> On Tue, Aug 15, 2017 at 12:00 PM, Hartmut Figge wrote: >>> Helmut Jarausch: >>> I'm running linux-4.12.7-gentoo with Virtualbox BUT you need app-emulation/virtualbox and Co in version 5.1.26 >>> >>> Hm. My Gentoo is mostly stable. That would mean to add virtualbox to the >>> unstable part. Hm. >>> >> >> On Gentoo I have found it fairly normal to switch to unstable (or >> unkeyworded) packages to fix issues. >> >> I don't want to change the subject too much, but I've fond QEMU a >> decent replacement for VirtualBox. It takes some set up at first but >> is fairly rewarding and easy to manage. I don't suggest using libvirt >> on Gentoo, but some people do. The main difference with not using >> libvirt, besides managing QEMU flags and VM startup yourself, is that >> spice doesn't work (the non-libvirt spice viewer has longstanding >> bugs, namely a particularly annoying one related to being unable to >> exit out of fullscreen mode). Depending on your usecase setting up >> remote access from within the OS of your VM might give you a better >> experience - you might even try that if you continue using VirtualBox. >> > > Another option is KVM. I'd like to interject for a moment. What you're referring to as KVM, is, in fact, QEMU/KVM, or as I've recently taken to calling it, QEMU plus KVM. KVM is not a virtualization solution unto itself, but rather another free component of a fully functioning FOSS virtualization system made useful by a hypervisor, interface, and device emulation components comprising a full virtualization system as defined by nobody.[1] Admittedly I referred to only QEMU above. > I do suggest using libvirt, and found that > app-emulation/virt-manager gives you a lot of the benefits of > something with a pretty GUI like Virtualbox, but it is 100% FOSS > underneath and you can run it all from the command line too. It is > just a front-end to libvirt. There are no issues with running these > VMs as services also, and I believe that you can connect to their > consoles at any time with virt-manager. > My only issue is that when I used libvirt I had to edit the produced configurations by hand, and the settings wouldn't always take. Certain hardware configurations were also hard to set up. However, should everything work it is very nice, and can do things like start your VMs on boot and create tap devices on demand, etc. R0b0t1. [1] https://www.gnu.org/gnu/linux-and-gnu.html
Re: [gentoo-user] efibootmgr "Could not prepare Boot variable: Read-only file system"
On Tue, Aug 15, 2017 at 2:17 PM, Rich Freeman wrote: > On Tue, Aug 15, 2017 at 11:04 AM, Mick wrote: >> >> I can't recall if I did this myself in a moment of security induced >> inspiration. I doubt I did. So how did this happen? What is responsible >> for >> mounting this fs? >> > > It looks like this never did turn into a news item: > https://archives.gentoo.org/gentoo-dev/message/35304b0db4de9e06fea322275379fa81 > > You can remount it as rw if your tools don't do it automatically. It > might not hurt to file a bug if one doesn't already exist for the tool > that isn't remounting it. Please bother efibootmgr upstream about it, or bother the OpenRC maintainer who decided to break things.
Re: [gentoo-user] Re: kernel linux-4.12.5-gentoo & virtualbox-modules-5.0.40
On Tue, Aug 15, 2017 at 3:02 PM, R0b0t1 wrote: > On Tue, Aug 15, 2017 at 12:00 PM, Hartmut Figge wrote: >> Helmut Jarausch: >> >>>I'm running linux-4.12.7-gentoo with Virtualbox >>>BUT you need app-emulation/virtualbox and Co in version 5.1.26 >> >> Hm. My Gentoo is mostly stable. That would mean to add virtualbox to the >> unstable part. Hm. >> > > On Gentoo I have found it fairly normal to switch to unstable (or > unkeyworded) packages to fix issues. > > I don't want to change the subject too much, but I've fond QEMU a > decent replacement for VirtualBox. It takes some set up at first but > is fairly rewarding and easy to manage. I don't suggest using libvirt > on Gentoo, but some people do. The main difference with not using > libvirt, besides managing QEMU flags and VM startup yourself, is that > spice doesn't work (the non-libvirt spice viewer has longstanding > bugs, namely a particularly annoying one related to being unable to > exit out of fullscreen mode). Depending on your usecase setting up > remote access from within the OS of your VM might give you a better > experience - you might even try that if you continue using VirtualBox. > Another option is KVM. I do suggest using libvirt, and found that app-emulation/virt-manager gives you a lot of the benefits of something with a pretty GUI like Virtualbox, but it is 100% FOSS underneath and you can run it all from the command line too. It is just a front-end to libvirt. There are no issues with running these VMs as services also, and I believe that you can connect to their consoles at any time with virt-manager. I can't really compare it in detail to qemu as I've barely used the latter, and mainly for emulation. Honestly, I rarely even use KVM these days as I've almost entirely moved to containers. -- Rich
Re: [gentoo-user] Re: kernel linux-4.12.5-gentoo & virtualbox-modules-5.0.40
On Tue, Aug 15, 2017 at 12:00 PM, Hartmut Figge wrote: > Helmut Jarausch: > >>I'm running linux-4.12.7-gentoo with Virtualbox >>BUT you need app-emulation/virtualbox and Co in version 5.1.26 > > Hm. My Gentoo is mostly stable. That would mean to add virtualbox to the > unstable part. Hm. > On Gentoo I have found it fairly normal to switch to unstable (or unkeyworded) packages to fix issues. I don't want to change the subject too much, but I've fond QEMU a decent replacement for VirtualBox. It takes some set up at first but is fairly rewarding and easy to manage. I don't suggest using libvirt on Gentoo, but some people do. The main difference with not using libvirt, besides managing QEMU flags and VM startup yourself, is that spice doesn't work (the non-libvirt spice viewer has longstanding bugs, namely a particularly annoying one related to being unable to exit out of fullscreen mode). Depending on your usecase setting up remote access from within the OS of your VM might give you a better experience - you might even try that if you continue using VirtualBox. R0b0t1.
Re: [gentoo-user] efibootmgr "Could not prepare Boot variable: Read-only file system"
On 15 August 2017 20:17:20 GMT+02:00, Rich Freeman wrote: >On Tue, Aug 15, 2017 at 11:04 AM, Mick >wrote: >> >> I can't recall if I did this myself in a moment of security induced >> inspiration. I doubt I did. So how did this happen? What is >responsible for >> mounting this fs? >> > >It looks like this never did turn into a news item: >https://archives.gentoo.org/gentoo-dev/message/35304b0db4de9e06fea322275379fa81 > >You can remount it as rw if your tools don't do it automatically. It >might not hurt to file a bug if one doesn't already exist for the tool >that isn't remounting it. I think mounting it as RO makes sense. Similarly to mounting /boot as RO. Difference is, and this is why a newsitem would have been useful, /boot is in your fstab and you (should) know you set it to not automount and/or RO. The efi mount is done automagically and any flags are usually not set by the user/admin. At least I now know this to be the case when I end up updating the few machines I set up to boot directly using EFI without a bootloader. -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [gentoo-user] efibootmgr "Could not prepare Boot variable: Read-only file system"
On Tue, Aug 15, 2017 at 11:04 AM, Mick wrote: > > I can't recall if I did this myself in a moment of security induced > inspiration. I doubt I did. So how did this happen? What is responsible for > mounting this fs? > It looks like this never did turn into a news item: https://archives.gentoo.org/gentoo-dev/message/35304b0db4de9e06fea322275379fa81 You can remount it as rw if your tools don't do it automatically. It might not hurt to file a bug if one doesn't already exist for the tool that isn't remounting it. -- Rich
[gentoo-user] efibootmgr "Could not prepare Boot variable: Read-only file system"
After some years of trouble free UEFI use on a PC with a Kaveri APU, I've suddenly come across a problem of incorrectly mounted efivarfs. I realised something was amiss when I tried to set up a new kernel I had just copied into /boot/EFI/BOOT/ # tree /boot /boot ├── 42GHz2400MHz.CMO └── EFI └── BOOT ├── A88XM-PLUS-ASUS-3004.CAP ├── System.map-4.12.5-gentoo ├── System.map-4.9.34-gentoo ├── bootx64-4.12.5-gentoo.efi ├── bootx64-4.9.34-gentoo.efi <==This one ├── config-4.12.5-gentoo └── config-4.9.34-gentoo 2 directories, 8 files The error is generated whenever I try to create a new boot entry: # efibootmgr --create --disk /dev/sda --part 1 --label "gentoo-4.12.5-15_Aug" --loader "\EFI\BOOT\bootx64-4.12.5-gentoo.efi" Could not prepare Boot variable: Read-only file system Hmm ... looking more closely it seems /sys/firmware/efi/efivars was mounted as 'ro': # mount | grep efi efivarfs on /sys/firmware/efi/efivars type efivarfs (ro,relatime) I can't recall if I did this myself in a moment of security induced inspiration. I doubt I did. So how did this happen? What is responsible for mounting this fs? Should I remount it as 'rw' so I can set up the new kernel in the EFI stub, or does this problem need further investigation? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: kernel linux-4.12.5-gentoo & virtualbox-modules-5.0.40
On Tue, Aug 15, 2017 at 10:00 AM, Hartmut Figge wrote: > Helmut Jarausch: > >>I'm running linux-4.12.7-gentoo with Virtualbox >>BUT you need app-emulation/virtualbox and Co in version 5.1.26 > > Hm. My Gentoo is mostly stable. That would mean to add virtualbox to the > unstable part. Hm. > Ideally virtualbox should at least have a dependency to address this, and I suspect one would be added if you file a bug (or the problem would be fixed). This is one of the reasons I tend to stick to longterm kernels that I choose. It sounds like the stable kernel team is going to start moving in this direction which should result in more timely updates but less breakage. I believe you'd be on 4.9 if they stuck to longterm. -- Rich
Re: [gentoo-user] Re: kernel linux-4.12.5-gentoo & virtualbox-modules-5.0.40
On Tuesday 15 Aug 2017 19:01:02 Hartmut Figge wrote: > Alan McKinnon: > >Wait one day, try again. > >Wait another day, try again. > >Repeat. > > *g* > > I'm currently doing that for a new bug of SeaMonkey-Trunk. Maybe I will > determine the responsible checkin later. > > But waiting a little is a good advice. :) > > Hartmut You are not alone, I had the same problem. I will wait, rinse, repeat or keyword the latest testing version if this takes forever to catch up, but this is the least of my problems at present. I can't even set up the latest kernel to boot, because efibootmgr suddenly started complaining that it "Could not prepare Boot variable: Read-only file system" ... but this merits another thread. -- Regards, Mick
[gentoo-user] Re: kernel linux-4.12.5-gentoo & virtualbox-modules-5.0.40
Alan McKinnon: >Wait one day, try again. >Wait another day, try again. >Repeat. *g* I'm currently doing that for a new bug of SeaMonkey-Trunk. Maybe I will determine the responsible checkin later. But waiting a little is a good advice. :) Hartmut
[gentoo-user] Re: kernel linux-4.12.5-gentoo & virtualbox-modules-5.0.40
Helmut Jarausch: >I'm running linux-4.12.7-gentoo with Virtualbox >BUT you need app-emulation/virtualbox and Co in version 5.1.26 Hm. My Gentoo is mostly stable. That would mean to add virtualbox to the unstable part. Hm. Hartmut
Re: [gentoo-user] kernel linux-4.12.5-gentoo & virtualbox-modules-5.0.40
On 15/08/2017 18:14, Hartmut Figge wrote: > Greeting, > > todays update brought me a new kernel, kernel linux-4.12.5-gentoo, which > required me to recompile virtualbox-modules-5.0.40. That failed. > > Searching in build.log for error 1 gives > > /usr/src/linux-4.12.5-gentoo/arch/x86/include/asm/atomic64_64.h:182:2: > error: undefined named operand ‘new’ > /usr/src/linux-4.12.5-gentoo/arch/x86/include/asm/atomic64_64.h:182:2: > error: undefined named operand ‘new’ > /usr/src/linux-4.12.5-gentoo/arch/x86/include/asm/atomic64_64.h:182:2: > error: undefined named operand ‘new’ > make[4]: *** [/usr/src/linux-4.12.5-gentoo/scripts/Makefile.build:302: > /var/tmp/portage/app-emulation/virtualbox-modules-5.0.40/work/vboxdrv/SUPDrvSem.o] > Error 1 > > Any ideas? > > Hartmut > > Wait one day, try again. Wait another day, try again. Repeat. It can take a sort wait between a change to the kernel and when the virtualbox fellows notice the change and fix it. nvidia drivers and most other out-of-tree drivers are all in the same boat. -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] kernel linux-4.12.5-gentoo & virtualbox-modules-5.0.40
On 08/15/2017 06:14:21 PM, Hartmut Figge wrote: Greeting, todays update brought me a new kernel, kernel linux-4.12.5-gentoo, which required me to recompile virtualbox-modules-5.0.40. That failed. Searching in build.log for error 1 gives /usr/src/linux-4.12.5-gentoo/arch/x86/include/asm/atomic64_64.h:182:2: error: undefined named operand ‘new’ /usr/src/linux-4.12.5-gentoo/arch/x86/include/asm/atomic64_64.h:182:2: error: undefined named operand ‘new’ /usr/src/linux-4.12.5-gentoo/arch/x86/include/asm/atomic64_64.h:182:2: error: undefined named operand ‘new’ make[4]: *** [/usr/src/linux-4.12.5-gentoo/scripts/Makefile.build:302: /var/tmp/portage/app-emulation/virtualbox-modules-5.0.40/work/vboxdrv/SUPDrvSem.o] Error 1 Any ideas? I'm running linux-4.12.7-gentoo with Virtualbox BUT you need app-emulation/virtualbox and Co in version 5.1.26 Helmut
Re: [gentoo-user] Codeblocks Fails to Exit Cleanly in Awesome WM
On Tue, Aug 15, 2017 at 9:28 AM, Dutch Ingraham wrote:
> Hi all:
>
> I'm having a problem with Codeblocks not exiting cleanly when using the
> Awesome WM. I've filed a bug report[1] but the wrangler closed it almost
> immediately without any testing or attempt to confirm, so I'm asking for
> your help here.
>
I don't necessarily agree with the closure of the bug report. I
suspect such closures happen because the first responder does not know
how to troubleshoot the issue. However, the Gentoo developers care a
lot more than, say, the Mozilla developers. Every bug report I have
sent to Mozilla trackers has been ignored.
It seems like a tossup: Awesome might be launching Code::Blocks in a
way that leaves the process unable to close itself, but seeing as I
don't actually know how that would happen, you might have better luck
asking the Code::Blocks developers as they will know how to
troubleshoot their project. They then might be able to figure out that
it is something else's fault.
> I am using Codeblocks-16.01 (the only unmasked version, which is keyworded
> unstable) on both a full-unstable installation and on a mostly-stable
> installation, both with only the 'contrib' use flag set. On both
> installations,
> Codeblocks, when started from a menu in the Awesome WM, will not exit
> cleanly. Specifically, when exiting in any manner, the GUI will disappear,
> but the Codeblocks process continues to run.
>
> However, when started from a terminal, Codeblocks does not show this behavior,
> i.e., it does shut down completely and cleanly.
>
> Additionally, this behavior does not present when using either the Plasma
> desktop or the Fluxbox WM, i.e., Codeblocks will shutdown cleanly whether
> started from a menu or from a terminal.
>
> This is likely not strictly an upstream issue. This is almost certainly a
> Gentoo
> issue, as issue I presented does not appear in Arch, Debian, or Fedora.
> All three have the exact same version of Codeblocks as Gentoo; all three have
> similar versions of Awesome (all in the 4.x branch) and Arch is using the
> exact same version of Awesome (4.2) that I am using on both Gentoo
> installations noted above.
>
> Any help or other insights in debugging this issue are appreciated.
>
When I encounter issues like this I try to find the newest version of
the project. In this case, it looks like 16.01 is the latest release
of Code::Blocks. You might try building from their repository. It will
take time to become acquainted with the different build systems
(automake, CMake, ...) but you can generally specify a custom
installation directory -- ~/.local is a good place. Add the binary
paths inside of that directory to your PATH.
You can also run a command to kill Code::Blocks after you exit, or use
another IDE (like Geany). Some example commands:
ps | awk '/codeblocks/ { print $1; }' | xargs kill
kill `pgrep codeblocks`
pkill codeblocks
Be careful that you don't kill processes that contain the name you
give but aren't the one you mean. The regex in the first command will
be easier to customize. Pkill and pgrep are nonstandard.
R0b0t1.
[gentoo-user] kernel linux-4.12.5-gentoo & virtualbox-modules-5.0.40
Greeting, todays update brought me a new kernel, kernel linux-4.12.5-gentoo, which required me to recompile virtualbox-modules-5.0.40. That failed. Searching in build.log for error 1 gives /usr/src/linux-4.12.5-gentoo/arch/x86/include/asm/atomic64_64.h:182:2: error: undefined named operand ‘new’ /usr/src/linux-4.12.5-gentoo/arch/x86/include/asm/atomic64_64.h:182:2: error: undefined named operand ‘new’ /usr/src/linux-4.12.5-gentoo/arch/x86/include/asm/atomic64_64.h:182:2: error: undefined named operand ‘new’ make[4]: *** [/usr/src/linux-4.12.5-gentoo/scripts/Makefile.build:302: /var/tmp/portage/app-emulation/virtualbox-modules-5.0.40/work/vboxdrv/SUPDrvSem.o] Error 1 Any ideas? Hartmut
Re: [gentoo-user] Install on ZFS
On 15 August 2017 16:13:37 GMT+02:00, "C." wrote: >Rich Freeman writes: >> Is this your first Gentoo install, or your first Gentoo+ZFS install? >> If the former, you're definitely not doing this the easy way... > >Not easy, no. But definitely possible. I managed to do so. > >One thing to keep in mind, though, is that it might be best to _not_ >put >"/boot" on ZFS. I did and can't upgrade my zpool just yet, because - as >far as I know (please corret me if I am wrong)- Grub ain't able to boot >from a zpool that has been upgraded to latest ZoL (> 0.7). It works >just >fine with 0.6.5.11 though. > >Kind regards >Christian. That's why the one I linked to actually tells you to create 2 zpools. 1 for /boot and 1 for the rest. -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [gentoo-user] Install on ZFS
On 15 August 2017 15:44:21 GMT+02:00, Dale wrote: >John Covici wrote: >> On Tue, 15 Aug 2017 08:52:45 -0400, >> Alan McKinnon wrote: >>> On 15/08/2017 14:49, Grant wrote: I'm trying to get started on my first Gentoo install on ZFS. My remote server is booted to a Gentoo LiveCD and I've SSH'ed in but >it looks like the CD doesn't have ZFS tools: livecd ~ # zpool status -bash: zpool: command not found Can I pull this off from here or do I need to mail a different CD >to my host? This server has 6 SSDs and I'm planning to set up a 2-way stripe >and 3-way mirror. Any tips that might help me pull this off? - Grant >>> >>> The Gentoo LiveCD is really nothing more than a feel-nice tool for >>> people who want to install Gentoo from a Gentoo tool; it is very >much >>> completely not required. >>> >>> Do your install from any medium you feel like as long as it has all >the >>> tools you need. >>> >>> I suppose you *could* emerge the zfs tools on the running LiveCD >system >>> if it supports fs merging but it's probably easier to use a medium >that >>> already has everything you want >> >> I would like to know which cd has zfs support. I could not find one, >> so I wrote some catalyst stuff to make an install cd with zfs >support, >> but it would be nice if I would not have to do that, a fair bit of >> work. >> > >Just for giggles, SystemRescueCd maybe?? Gentoo based and it has a lot >of tools just not sure on that one. > >Dale > >:-) :-) Not systemresccd. But the one I linked to is a rebuild of that with zfs and multipathing added. -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [gentoo-user] Install on ZFS
On 15 August 2017 14:49:43 GMT+02:00, Grant wrote: >I'm trying to get started on my first Gentoo install on ZFS. My >remote server is booted to a Gentoo LiveCD and I've SSH'ed in but it >looks like the CD doesn't have ZFS tools: > >livecd ~ # zpool status >-bash: zpool: command not found > >Can I pull this off from here or do I need to mail a different CD to my >host? > >This server has 6 SSDs and I'm planning to set up a 2-way stripe and >3-way mirror. Any tips that might help me pull this off? > >- Grant I did this not too long ago, using the boot disc and howto from FearedBliss: https://wiki.gentoo.org/wiki/User:Fearedbliss -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
[gentoo-user] Codeblocks Fails to Exit Cleanly in Awesome WM
Hi all: I'm having a problem with Codeblocks not exiting cleanly when using the Awesome WM. I've filed a bug report[1] but the wrangler closed it almost immediately without any testing or attempt to confirm, so I'm asking for your help here. I am using Codeblocks-16.01 (the only unmasked version, which is keyworded unstable) on both a full-unstable installation and on a mostly-stable installation, both with only the 'contrib' use flag set. On both installations, Codeblocks, when started from a menu in the Awesome WM, will not exit cleanly. Specifically, when exiting in any manner, the GUI will disappear, but the Codeblocks process continues to run. However, when started from a terminal, Codeblocks does not show this behavior, i.e., it does shut down completely and cleanly. Additionally, this behavior does not present when using either the Plasma desktop or the Fluxbox WM, i.e., Codeblocks will shutdown cleanly whether started from a menu or from a terminal. This is likely not strictly an upstream issue. This is almost certainly a Gentoo issue, as issue I presented does not appear in Arch, Debian, or Fedora. All three have the exact same version of Codeblocks as Gentoo; all three have similar versions of Awesome (all in the 4.x branch) and Arch is using the exact same version of Awesome (4.2) that I am using on both Gentoo installations noted above. Any help or other insights in debugging this issue are appreciated. [1] https://bugs.gentoo.org/show_bug.cgi?id=627430
Re: [gentoo-user] Install on ZFS
Rich Freeman writes: > Is this your first Gentoo install, or your first Gentoo+ZFS install? > If the former, you're definitely not doing this the easy way... Not easy, no. But definitely possible. I managed to do so. One thing to keep in mind, though, is that it might be best to _not_ put "/boot" on ZFS. I did and can't upgrade my zpool just yet, because - as far as I know (please corret me if I am wrong)- Grub ain't able to boot from a zpool that has been upgraded to latest ZoL (> 0.7). It works just fine with 0.6.5.11 though. Kind regards Christian. -- [ Insert favourite quote here. ]
[gentoo-user] Re: No beep.
On 14/08/17 21:22, Alan Mackenzie wrote: However, during the building, I discovered to my disgust that there was no loudspeaker in my new case. You sure? These days, it's not shaped like a speaker anymore, but more like... a clip-on microphone? Not sure how to describe it. It's really small and easy to overlook in the mainboard's package along the other cables and connectors. It's this one: https://www.newegg.com/Product/Product.aspx?Item=9SIA2RP0YW4962
Re: [gentoo-user] Install on ZFS
On Tue, Aug 15, 2017 at 6:31 AM, John Covici wrote: > > I would like to know which cd has zfs support. I could not find one, > so I wrote some catalyst stuff to make an install cd with zfs support, > but it would be nice if I would not have to do that, a fair bit of > work. > IMO this is the easiest option out there: http://www.funtoo.org/ZFS_Install_Guide (Just the parts about loading the zfs module.) It uses an Ubuntu 16.04 boot USB, and installs the packaged zfs modules/etc. You could certainly add them to a Gentoo or systemrescuecd boot disk, but Ubuntu should work just as well. All you need is something you can boot with that can create filesystems, mount them, expand tarballs, and run chroot. A lot of rescue CDs lack zfs support due to the whole GPL linking non-GPL concern, which many believe is illegal. If you're not putting root/usr on zfs then it is pretty easy to get zfs running on Gentoo (though in this case you probably don't even need a zfs-capable boot cd to start it). If you want to put root on zfs it gets trickier, and if you want to put boot on zfs it gets trickier still. There are docs for both, but I've never actually done them. If you want boot on zfs then your bootloader needs to support it and there are limitations on what features you can enable on your pool. I think that if boot is non-zfs then there are fewer restrictions on root, but you need some scripts to unmount it cleanly when shutting down (unless using systemd+dracut where you can pivot back to the initramfs for this - which apparently hasn't actually been tested on Gentoo). Is this your first Gentoo install, or your first Gentoo+ZFS install? If the former, you're definitely not doing this the easy way... -- Rich
Re: [gentoo-user] Install on ZFS
John Covici wrote: > On Tue, 15 Aug 2017 08:52:45 -0400, > Alan McKinnon wrote: >> On 15/08/2017 14:49, Grant wrote: >>> I'm trying to get started on my first Gentoo install on ZFS. My >>> remote server is booted to a Gentoo LiveCD and I've SSH'ed in but it >>> looks like the CD doesn't have ZFS tools: >>> >>> livecd ~ # zpool status >>> -bash: zpool: command not found >>> >>> Can I pull this off from here or do I need to mail a different CD to my >>> host? >>> >>> This server has 6 SSDs and I'm planning to set up a 2-way stripe and >>> 3-way mirror. Any tips that might help me pull this off? >>> >>> - Grant >>> >> >> The Gentoo LiveCD is really nothing more than a feel-nice tool for >> people who want to install Gentoo from a Gentoo tool; it is very much >> completely not required. >> >> Do your install from any medium you feel like as long as it has all the >> tools you need. >> >> I suppose you *could* emerge the zfs tools on the running LiveCD system >> if it supports fs merging but it's probably easier to use a medium that >> already has everything you want > > I would like to know which cd has zfs support. I could not find one, > so I wrote some catalyst stuff to make an install cd with zfs support, > but it would be nice if I would not have to do that, a fair bit of > work. > Just for giggles, SystemRescueCd maybe?? Gentoo based and it has a lot of tools just not sure on that one. Dale :-) :-)
Re: [gentoo-user] Install on ZFS
On Tue, 15 Aug 2017 08:52:45 -0400, Alan McKinnon wrote: > > On 15/08/2017 14:49, Grant wrote: > > I'm trying to get started on my first Gentoo install on ZFS. My > > remote server is booted to a Gentoo LiveCD and I've SSH'ed in but it > > looks like the CD doesn't have ZFS tools: > > > > livecd ~ # zpool status > > -bash: zpool: command not found > > > > Can I pull this off from here or do I need to mail a different CD to my > > host? > > > > This server has 6 SSDs and I'm planning to set up a 2-way stripe and > > 3-way mirror. Any tips that might help me pull this off? > > > > - Grant > > > > > The Gentoo LiveCD is really nothing more than a feel-nice tool for > people who want to install Gentoo from a Gentoo tool; it is very much > completely not required. > > Do your install from any medium you feel like as long as it has all the > tools you need. > > I suppose you *could* emerge the zfs tools on the running LiveCD system > if it supports fs merging but it's probably easier to use a medium that > already has everything you want I would like to know which cd has zfs support. I could not find one, so I wrote some catalyst stuff to make an install cd with zfs support, but it would be nice if I would not have to do that, a fair bit of work. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] Install on ZFS
On 15/08/2017 14:49, Grant wrote: > I'm trying to get started on my first Gentoo install on ZFS. My > remote server is booted to a Gentoo LiveCD and I've SSH'ed in but it > looks like the CD doesn't have ZFS tools: > > livecd ~ # zpool status > -bash: zpool: command not found > > Can I pull this off from here or do I need to mail a different CD to my host? > > This server has 6 SSDs and I'm planning to set up a 2-way stripe and > 3-way mirror. Any tips that might help me pull this off? > > - Grant > The Gentoo LiveCD is really nothing more than a feel-nice tool for people who want to install Gentoo from a Gentoo tool; it is very much completely not required. Do your install from any medium you feel like as long as it has all the tools you need. I suppose you *could* emerge the zfs tools on the running LiveCD system if it supports fs merging but it's probably easier to use a medium that already has everything you want -- Alan McKinnon alan.mckin...@gmail.com
[gentoo-user] Install on ZFS
I'm trying to get started on my first Gentoo install on ZFS. My remote server is booted to a Gentoo LiveCD and I've SSH'ed in but it looks like the CD doesn't have ZFS tools: livecd ~ # zpool status -bash: zpool: command not found Can I pull this off from here or do I need to mail a different CD to my host? This server has 6 SSDs and I'm planning to set up a 2-way stripe and 3-way mirror. Any tips that might help me pull this off? - Grant
[gentoo-user] Warnings on shutting down bcache: WARNING: CPU: 1 PID: 4378 at lib/idr.c:383
I'm getting some noise in my logs when shutting down bcache. My system: Linux gentoo 4.12.7-gentoo #1 SMP Sun Aug 13 22:56:20 CEST 2017 x86_64 Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz GenuineIntel GNU/Linux Running as dom0 under Xen-4.9.0 My shutdown script loops over the bcache devices like so: --- for f in /sys/fs/bcache/854fc80e-5499-413f-b90b-87a803eaca7e/bdev*; do bdev=$(basename $f ) if [ -e $f/stop ]; then logger -t "init.d/probe-home-partition" -p daemon.warning\ "Stopping $bdev" einfo "Stopping $bdev" if ! echo 1 > $f/stop ; then ewarn "Could not stop $bdev" logger -t "init.d/probe-home-partition" -p daemon.warning\ "Could not stop $bdev" fi usleep 300 sleep 1 else einfo "$bdev not cached?" logger -t "init.d/probe-home-partition" -p daemon.warning \ "$bdev not cached ?" fi done - This gives me in daemon.log: - Aug 14 09:31:21 gentoo init.d/probe-home-partition: Stopping bdev15 Aug 14 09:31:22 gentoo init.d/probe-home-partition: Stopping bdev16 Aug 14 09:31:23 gentoo init.d/probe-home-partition: Stopping bdev17 Aug 14 09:31:24 gentoo init.d/probe-home-partition: Stopping bdev18 Aug 14 09:31:25 gentoo init.d/probe-home-partition: Stopping bdev19 Aug 14 09:31:26 gentoo init.d/probe-home-partition: Stopping cache set - But it seems bcache is doing something weird, stopping a device called bcache0, which I do not have, before stopping the first of my bcache devices. ALL runs of "echo 1 > $device/stop" provoke a warning in lib/idr.c on that same line. It may be that my stopping of the bcache devices is wrong, un-necessary and misguided, but it should still work the way I am doing it, should it not? ---kern.log:--- ... [140395.421994] nfsd: last server has exited, flushing export cache [140397.011932] XFS (bcache16): Unmounting Filesystem [140397.248911] bcache: bcache_device_free() bcache0 stopped [140398.300187] bcache: bcache_device_free() bcache16 stopped [140398.381951] ida_remove called for id=16 which is not allocated. [140398.381975] [ cut here ] [140398.381985] WARNING: CPU: 1 PID: 4378 at lib/idr.c:383 ida_remove+0xde/0xef [140398.381987] Modules linked in: xt_physdev iptable_filter ip_tables x_tables nfsd auth_rpcgss oid_registry nfsv4 dns_resolver nfsv3 nfs_acl iTCO_wdt iTCO_vendor_support binfmt_misc tun usbip_host usbip_core pktcdvd xen_wdt xen_blkback intel_rapl amdgpu intel_powerclamp crc32c_intel serio_raw drm_kms_helper pcspkr syscopyarea sysfillrect sysimgblt fb_sys_fops ttm lpc_ich i2c_i801 snd_hda_codec_realtek drm snd_hda_codec_generic bcache snd_usb_audio snd_usbmidi_lib snd_hda_intel snd_rawmidi snd_hda_codec snd_seq_device snd_hwdep snd_hda_core snd_pcm snd_timer snd cp210x usbserial nct6775 input_leds hwmon_vid shpchp ipmi_ssif wmi acpi_power_meter dm_zero dm_thin_pool dm_persistent_data dm_bio_prison dm_service_time dm_round_robin dm_queue_length dm_multipath dm_log_userspace cn virtio_pci virtio_scsi [140398.382056] virtio_blk virtio_console virtio_balloon xts aes_x86_64 cbc sha512_generic sha1_generic libiscsi scsi_transport_iscsi macvlan virtio_net virtio_ring virtio e1000 fuse overlay nfs lockd grace sunrpc fscache jfs multipath linear raid10 raid1 raid0 dm_raid raid456 async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq dm_snapshot dm_bufio dm_crypt dm_mirror dm_region_hash dm_log dm_mod dax hid_sunplus hid_sony hid_samsung hid_pl hid_petalynx hid_monterey hid_microsoft hid_logitech ff_memless hid_gyration hid_ezkey hid_cypress hid_chicony hid_cherry hid_a4tech sl811_hcd xhci_plat_hcd ohci_pci ohci_hcd uhci_hcd aic94xx lpfc qla2xxx aacraid sx8 DAC960 hpsa cciss 3w_9xxx 3w_ mptsas mptfc scsi_transport_fc mptspi mptscsih mptbase atp870u dc395x qla1280 imm parport dmx3191d [140398.382139] sym53c8xx gdth initio BusLogic arcmsr aic7xxx aic79xx sg pdc_adma sata_inic162x sata_mv sata_qstor sata_vsc sata_uli sata_sis sata_sx4 sata_nv sata_via sata_svw sata_sil24 sata_sil sata_promise pata_sis usbhid led_class igb ptp dca i2c_algo_bit ehci_pci ehci_hcd xhci_pci megaraid_sas xhci_hcd [140398.382175] CPU: 1 PID: 4378 Comm: kworker/1:2 Not tainted 4.12.6-gentoo #1 [140398.382177] Hardware name: ASUSTeK COMPUTER INC. Z10PE-D8 WS/Z10PE-D8 WS, BIOS 3407 03/10/2017 [140398.382190] Workqueue: events cached_dev_free [bcache] [140398.382193] task: 880216b24240 task.stack: c900431e4000 [140398.382197] RIP: e030:ida_remove+0xde/0xef [140398.382199] RSP: e02b:c900431e7db0 EFLAGS: 00010082 [140398.382202] RAX: 0033 RBX: 0012 RCX: [140398.382204] RDX: 880249654450 RSI: 88024964dc08 RDI: 88024964dc08 [140398.382205] RBP: c900431e7e10 R08: R09: 000448da [140398.382207] R10: 1668 R11: 81f1dad0 R12: c08114c8 [140398.382209] R13: c08114c0 R14: 00fa R15: 0010 [140398.382223] FS: 00
Re: [gentoo-user] mount: Permission Denied in CHROOT
On 15 August 2017 05:32:48 GMT+02:00, symack wrote: >Hello Everyone, > >New installation on an older x346 system that has a HW raid >serveraid7k. I >have the appropriate kernel driver compiled `aic79xx`. > >lscpi: > >00:00.0 Host bridge: Intel Corporation E7520 Memory Controller Hub (rev >0c) >00:00.1 Unassigned class [ff00]: Intel Corporation E7525/E7520 Error >Reporting Registers (rev 0c) >00:02.0 PCI bridge: Intel Corporation E7525/E7520/E7320 PCI Express >Port A >(rev 0c) >00:04.0 PCI bridge: Intel Corporation E7525/E7520 PCI Express Port B >(rev >0c) >00:05.0 PCI bridge: Intel Corporation E7520 PCI Express Port B1 (rev >0c) >00:06.0 PCI bridge: Intel Corporation E7520 PCI Express Port C (rev 0c) >00:08.0 System peripheral: Intel Corporation E7525/E7520/E7320 Extended >Configuration Registers (rev 0c) >00:1d.0 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB >UHCI >Controller #1 (rev 02) >00:1d.1 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB >UHCI >Controller #2 (rev 02) >00:1d.7 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 >EHCI >Controller (rev 02) >00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2) >00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC >Interface >Bridge (rev 02) >00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE >Controller (rev 02) >00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus >Controller >(rev 02) >01:06.0 VGA compatible controller: Advanced Micro Devices, Inc. >[AMD/ATI] >RV100 [Radeon 7000 / Radeon VE] >02:00.0 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge >A >(rev 09) >02:00.2 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge >B >(rev 09) >03:03.0 Network controller: MYRICOM Inc. Myrinet 2000 Scalable Cluster >Interconnect (rev 06) >05:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5721 Gigabit >Ethernet PCI Express (rev 11) >06:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5721 Gigabit >Ethernet PCI Express (rev 11) >07:00.0 PCI bridge: Intel Corporation 80332 [Dobson] I/O processor >(A-Segment Bridge) (rev 07) >07:00.2 PCI bridge: Intel Corporation 80332 [Dobson] I/O processor >(B-Segment Bridge) (rev 07) >08:0e.0 RAID bus controller: Adaptec ServeRAID Controller (rev 07) > > > >emerge --info > > >Portage 2.3.6 (python 3.4.5-final-0, hardened/linux/amd64, gcc-5.4.0, >glibc-2.23-r4, 4.8.17-hardened-r2 x86_64) >= >System uname: >Linux-4.8.17-hardened-r2-x86_64-Intel-R-_Xeon-TM-_CPU_3.60GHz-with-gentoo-2.3 >KiB Mem: 8061620 total, 6539044 free >KiB Swap: 0 total, 0 free >Timestamp of repository gentoo: Mon, 07 Aug 2017 15:30:01 + >sh bash 4.3_p48-r1 >ld GNU ld (Gentoo 2.28 p1.2) 2.28 >app-shells/bash: 4.3_p48-r1::gentoo >dev-lang/perl:5.24.1-r2::gentoo >dev-lang/python: 2.7.12::gentoo, 3.4.5::gentoo >dev-util/pkgconfig: 0.28-r2::gentoo >sys-apps/baselayout: 2.3::gentoo >sys-apps/openrc: 0.28::gentoo >sys-apps/sandbox: 2.10-r3::gentoo >sys-devel/autoconf: 2.69::gentoo >sys-devel/automake: 1.15-r2::gentoo >sys-devel/binutils: 2.28-r2::gentoo >sys-devel/gcc:5.4.0-r3::gentoo >sys-devel/gcc-config: 1.7.3::gentoo >sys-devel/libtool:2.4.6-r3::gentoo >sys-devel/make: 4.2.1::gentoo >sys-kernel/linux-headers: 4.4::gentoo (virtual/os-headers) >sys-libs/glibc: 2.23-r4::gentoo >Repositories: > >gentoo >location: /usr/portage >sync-type: rsync >sync-uri: rsync://rsync.gentoo.org/gentoo-portage >priority: -1000 > >ACCEPT_KEYWORDS="amd64" >ACCEPT_LICENSE="* -@EULA" >CBUILD="x86_64-pc-linux-gnu" >CFLAGS="-march=core2 -msse4.1 -msse4.2 -mtune=generic -O2 -pipe" >CHOST="x86_64-pc-linux-gnu" >CONFIG_PROTECT="/etc /usr/lib64/libreoffice/program/sofficerc >/usr/share/gnupg/qualified.txt" >CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/gconf >/etc/gentoo-release /etc/sandbox.d /etc/terminfo" >CXXFLAGS="-march=core2 -msse4.1 -msse4.2 -mtune=generic -O2 -pipe" >DISTDIR="/usr/portage/distfiles" >FCFLAGS="-O2 -pipe" >FEATURES="assume-digests binpkg-logs config-protect-if-modified >distlocks >ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs >protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs >unmerge-orphans userfetch userpriv usersandbox usersync xattr" >FFLAGS="-O2 -pipe" >GENTOO_MIRRORS="http://mirror.csclub.uwaterloo.ca/gentoo-distfiles/ >ftp://mirror.csclub.uwaterloo.ca/gentoo-distfiles/"; >LANG="en_US.utf8" >LDFLAGS="-Wl,-O1 -Wl,--as-needed" >MAKEOPTS="-j2" >PKGDIR="/usr/portage/packages" >PORTAGE_CONFIGROOT="/" >PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times >--omit-dir-times --compress --force --whole-file --delete --stats >--human-readable --timeout=180 --exclude=/distfiles --exclude=/local >--exclude=/packages --exclude=/.git" >PORTAGE_T
