[gentoo-user] preparing for make menuconfig
I installed lspci and ran the command. On the first line lspci says Unable to load libkmod resources. Lots of information provided after that though. Are libkmod resources used by sound cards? I have sound working on the system to be installed since I'm using espeak to do the installation. Does any way to clear this error exist or it may be a warning let's see, lspci exited with a 0 errorlevel so that must have been a warning.Is it likely be unnecessary to clear this warning? --
Re: [gentoo-user] problems with installing zfs-kmod under new kernel
On Wed, 07 Oct 2020 20:48:29 -0400, Rich Freeman wrote: > > On Wed, Oct 7, 2020 at 10:36 AM John Covici wrote: > > > > I was on 0.8.4 and it upgraded me to 22.0.0_rc1. I have not upgraded > > my pools, so I think I can go back to 0.8.4 or 5. The kernel I am > > upgrading is not the running kernel, so would any of this effect my > > running kernel which is 4.19.144 -- unfortunately on 2.0.0_rc1, but I > > agree maybe I should mask it off and go to 0.8.5. > > Yeah, or just stay on 0.8.4. 0.8.5 was only released upstream this > week. With my root and multiple TB of data on zfs I really don't want > to face a restore situation. I do have backups but it would take days > to restore everything. > > As long as you never ran zpool upgrade you should be able to downgrade > the version you're running. That said, anytime I change kernels I > keep some old ones lying around just in case, including their modules. Yep, not a bid idea at all, I usually do that as well. Thanks. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
Re: [gentoo-user] emerge @world command successful
On Wed, 7 Oct 2020 20:00:29 -0400, Jude DaShiell wrote: > One interesting thing that happened is when I tried doing emerge > --depclean I was told I have no @world file. Once again, please post the exact command you used and the actual output. -- Neil Bothwick All generalizations are false. pgphi4Sl50VOa.pgp Description: OpenPGP digital signature
Re: [gentoo-user] problems with installing zfs-kmod under new kernel
On Wed, Oct 7, 2020 at 10:36 AM John Covici wrote: > > I was on 0.8.4 and it upgraded me to 22.0.0_rc1. I have not upgraded > my pools, so I think I can go back to 0.8.4 or 5. The kernel I am > upgrading is not the running kernel, so would any of this effect my > running kernel which is 4.19.144 -- unfortunately on 2.0.0_rc1, but I > agree maybe I should mask it off and go to 0.8.5. Yeah, or just stay on 0.8.4. 0.8.5 was only released upstream this week. With my root and multiple TB of data on zfs I really don't want to face a restore situation. I do have backups but it would take days to restore everything. As long as you never ran zpool upgrade you should be able to downgrade the version you're running. That said, anytime I change kernels I keep some old ones lying around just in case, including their modules. -- Rich
[gentoo-user] emerge @world command successful
I did the command in the handbook after adding a few accessibility packages for the system and I have -j2 in MAKEJOBS in /etc/portage/make.conf. The older machine doesn't like to do parallel compiles with acpi, but it had no issue doing them with apm on. If you will use linux, you will learn lots about your hardware. The newer machine I have has comparatively small ssd drives 120GB as opposed to the older machine most drives are 2tb and the one gentoo is on is 3tb in size. The new machine has 14GB of memory available older machine much less than that. One interesting thing that happened is when I tried doing emerge --depclean I was told I have no @world file. --
Re: [gentoo-user] Terminus font for X11 : how to?
On 10/06/2020 11:12:02 PM, Jack wrote: On 2020.10.06 16:33, Helmut Jarausch wrote: Hi, I would like to use a Terminus font under X11. I have emerged media-fonts/terminus-font eselect fontconfig list show that 75-yes-terminus.conf is selected. Still xlsfonts doesn't show this font. What am I missing? Many thanks for a hint, Helmut Searching on "enable terminus font in xorg" the third hit is https://bbs.archlinux.org/viewtopic.php?id=164392 and what didn't work for that person (slight variant) did work for me: xset +fp /usr/share/fonts/terminal xset fp rehash Thanks Jack, that did help! But, why on earth isn't that done by Gentoo ? Helmut
Re: [gentoo-user] problems with installing zfs-kmod under new kernel
On Wed, 07 Oct 2020 09:53:42 -0400, Rich Freeman wrote: > > On Wed, Oct 7, 2020 at 9:28 AM John Covici wrote: > > > > Hi. I am having problems installing zfs-kmod on my new kernel > > 5.4.69. Originally I got this: > > > > !!! Multiple package instances within a single package slot have been > > pulled > > !!! into the dependency graph, resulting in a slot conflict: > > > > sys-fs/zfs-kmod:0 > > > > (sys-fs/zfs-kmod-2.0.0_rc3:0/0::gentoo, ebuild scheduled for merge) > > USE="rootfs -custom-cflags -debug" ABI_X86="(64)" pulled in by > > (no parents that aren't satisfied by other packages in this > > slot) > > > > (sys-fs/zfs-kmod-2.0.0_rc1:0/0::gentoo, installed) USE="rootfs > > -custom-cflags -debug" ABI_X86="(64)" pulled in by > > ~sys-fs/zfs-kmod-2.0.0_rc1 required by > > (sys-fs/zfs-2.0.0_rc1-r1:0/0::gentoo, installed) USE="nls pam rootfs > > (split-usr) -custom-cflags -debug (-kernel-builtin) -libressl > > -minimal -python (-static-libs) -test-suite" ABI_X86="(64)" > > PYTHON_TARGETS="python3_7 -python3_6 -python3_8" > > ^^ > > > > This is because you're attempting to upgrade zfs-kmod and not zfs. > You didn't paste your command line but chances are you didn't have > both packages on it. > > > Then I masked off the -rc3 version thinking that would help and I got > > this: > > > > > > > > !!! Multiple package instances within a single package slot have been > > pulled > > !!! into the dependency graph, resulting in a slot conflict: > > > > sys-fs/zfs-kmod:0 > > > > (sys-fs/zfs-kmod-0.8.5:0/0::gentoo, ebuild scheduled for merge) > > USE="rootfs -custom-cflags -debug" ABI_X86="(64)" pulled in by > > (no parents that aren't satisfied by other packages in this > > slot) > > > > (sys-fs/zfs-kmod-2.0.0_rc1:0/0::gentoo, installed) USE="rootfs > > -custom-cflags -debug" ABI_X86="(64)" pulled in by > > ~sys-fs/zfs-kmod-2.0.0_rc1 required by > > (sys-fs/zfs-2.0.0_rc1-r1:0/0::gentoo, installed) USE="nls pam rootfs > > (split-usr) -custom-cflags -debug (-kernel-builtin) -libressl > > -minimal -python (-static-libs) -test-suite" ABI_X86="(64)" > > PYTHON_TARGETS="python3_7 -python3_6 -python3_8" > > ^^ > > > > That is because masking rc3 forces it to downgrade to an older version > of zfs (which may or may not be compatible with what you have on-disk > so you might be in for a surprise when you reboot). But, since you're > only updating one package but not the other you still get the same > error. > > What version of zfs do you WANT to use? Are you already running on > the v2 release candidate? (Probably not what most people should be > doing...) If so you need to figure out if your pools are even > compatible with v0.8.5 (I'm not sure offhand if new features were > added, and if they were it would probably depend on whether you > upgraded your pools). > > If you are on the v2rc and want to stick with it, then undo whatever > masking you did and just update both packages together: > emerge -1au zfs-kmod zfs > > Really though that should already happen if you did an emerge -u > @world assuming both are in your world. > > If you want to run v0.8.5 then I would mask both zfs-kmod and zfs > >=0.9 and then run the same command. > > If you're on 0.8.4 though you might seriously consider just accepting > only stable keywords on zfs though - it is a filesystem and maybe not > something you want to be cutting edge. > > And you definitely don't want to go uninstalling zfs-kmod as now the > module will be gone and once again you'll get a surprise when you > reboot. > > In the future though I'd probably avoid installing release candidates > if you are running one. That is, unless it is your goal to beta-test > filesystems. I was on 0.8.4 and it upgraded me to 22.0.0_rc1. I have not upgraded my pools, so I think I can go back to 0.8.4 or 5. The kernel I am upgrading is not the running kernel, so would any of this effect my running kernel which is 4.19.144 -- unfortunately on 2.0.0_rc1, but I agree maybe I should mask it off and go to 0.8.5. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
Re: [gentoo-user] problems with installing zfs-kmod under new kernel
On Wed, Oct 7, 2020 at 9:28 AM John Covici wrote: > > Hi. I am having problems installing zfs-kmod on my new kernel > 5.4.69. Originally I got this: > > !!! Multiple package instances within a single package slot have been > pulled > !!! into the dependency graph, resulting in a slot conflict: > > sys-fs/zfs-kmod:0 > > (sys-fs/zfs-kmod-2.0.0_rc3:0/0::gentoo, ebuild scheduled for merge) > USE="rootfs -custom-cflags -debug" ABI_X86="(64)" pulled in by > (no parents that aren't satisfied by other packages in this > slot) > > (sys-fs/zfs-kmod-2.0.0_rc1:0/0::gentoo, installed) USE="rootfs > -custom-cflags -debug" ABI_X86="(64)" pulled in by > ~sys-fs/zfs-kmod-2.0.0_rc1 required by > (sys-fs/zfs-2.0.0_rc1-r1:0/0::gentoo, installed) USE="nls pam rootfs > (split-usr) -custom-cflags -debug (-kernel-builtin) -libressl > -minimal -python (-static-libs) -test-suite" ABI_X86="(64)" > PYTHON_TARGETS="python3_7 -python3_6 -python3_8" > ^^ > This is because you're attempting to upgrade zfs-kmod and not zfs. You didn't paste your command line but chances are you didn't have both packages on it. > Then I masked off the -rc3 version thinking that would help and I got > this: > > > > !!! Multiple package instances within a single package slot have been > pulled > !!! into the dependency graph, resulting in a slot conflict: > > sys-fs/zfs-kmod:0 > > (sys-fs/zfs-kmod-0.8.5:0/0::gentoo, ebuild scheduled for merge) > USE="rootfs -custom-cflags -debug" ABI_X86="(64)" pulled in by > (no parents that aren't satisfied by other packages in this > slot) > > (sys-fs/zfs-kmod-2.0.0_rc1:0/0::gentoo, installed) USE="rootfs > -custom-cflags -debug" ABI_X86="(64)" pulled in by > ~sys-fs/zfs-kmod-2.0.0_rc1 required by > (sys-fs/zfs-2.0.0_rc1-r1:0/0::gentoo, installed) USE="nls pam rootfs > (split-usr) -custom-cflags -debug (-kernel-builtin) -libressl > -minimal -python (-static-libs) -test-suite" ABI_X86="(64)" > PYTHON_TARGETS="python3_7 -python3_6 -python3_8" > ^^ > That is because masking rc3 forces it to downgrade to an older version of zfs (which may or may not be compatible with what you have on-disk so you might be in for a surprise when you reboot). But, since you're only updating one package but not the other you still get the same error. What version of zfs do you WANT to use? Are you already running on the v2 release candidate? (Probably not what most people should be doing...) If so you need to figure out if your pools are even compatible with v0.8.5 (I'm not sure offhand if new features were added, and if they were it would probably depend on whether you upgraded your pools). If you are on the v2rc and want to stick with it, then undo whatever masking you did and just update both packages together: emerge -1au zfs-kmod zfs Really though that should already happen if you did an emerge -u @world assuming both are in your world. If you want to run v0.8.5 then I would mask both zfs-kmod and zfs >=0.9 and then run the same command. If you're on 0.8.4 though you might seriously consider just accepting only stable keywords on zfs though - it is a filesystem and maybe not something you want to be cutting edge. And you definitely don't want to go uninstalling zfs-kmod as now the module will be gone and once again you'll get a surprise when you reboot. In the future though I'd probably avoid installing release candidates if you are running one. That is, unless it is your goal to beta-test filesystems. -- Rich
[gentoo-user] problems with installing zfs-kmod under new kernel
Hi. I am having problems installing zfs-kmod on my new kernel 5.4.69. Originally I got this: !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: sys-fs/zfs-kmod:0 (sys-fs/zfs-kmod-2.0.0_rc3:0/0::gentoo, ebuild scheduled for merge) USE="rootfs -custom-cflags -debug" ABI_X86="(64)" pulled in by (no parents that aren't satisfied by other packages in this slot) (sys-fs/zfs-kmod-2.0.0_rc1:0/0::gentoo, installed) USE="rootfs -custom-cflags -debug" ABI_X86="(64)" pulled in by ~sys-fs/zfs-kmod-2.0.0_rc1 required by (sys-fs/zfs-2.0.0_rc1-r1:0/0::gentoo, installed) USE="nls pam rootfs (split-usr) -custom-cflags -debug (-kernel-builtin) -libressl -minimal -python (-static-libs) -test-suite" ABI_X86="(64)" PYTHON_TARGETS="python3_7 -python3_6 -python3_8" ^^ It may be possible to solve this problem by using package.mask to prevent one of those packages from being selected. However, it is also possible that conflicting dependencies exist such that they are impossible to satisfy simultaneously. If such a conflict exists in the dependencies of two different packages, then those packages can not be installed simultaneously. For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. Then I masked off the -rc3 version thinking that would help and I got this: !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: sys-fs/zfs-kmod:0 (sys-fs/zfs-kmod-0.8.5:0/0::gentoo, ebuild scheduled for merge) USE="rootfs -custom-cflags -debug" ABI_X86="(64)" pulled in by (no parents that aren't satisfied by other packages in this slot) (sys-fs/zfs-kmod-2.0.0_rc1:0/0::gentoo, installed) USE="rootfs -custom-cflags -debug" ABI_X86="(64)" pulled in by ~sys-fs/zfs-kmod-2.0.0_rc1 required by (sys-fs/zfs-2.0.0_rc1-r1:0/0::gentoo, installed) USE="nls pam rootfs (split-usr) -custom-cflags -debug (-kernel-builtin) -libressl -minimal -python (-static-libs) -test-suite" ABI_X86="(64)" PYTHON_TARGETS="python3_7 -python3_6 -python3_8" ^^ It may be possible to solve this problem by using package.mask to prevent one of those packages from being selected. However, it is also possible that conflicting dependencies exist such that they are impossible to satisfy simultaneously. If such a conflict exists in the dependencies of two different packages, then those packages can not be installed simultaneously. For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. So, how do I fix -- I was thinking of uninstalling zfs-kmod, but was afraid it would delete from my running kernel (4.19.144) or some other fcatastrophe, so I thought I'd ask here first. I am on the zfs-discuss list and a few months ago they were talking about a necessary patch to install in 5.4 kernels because of not exporting some symhbols as well. Thanks in advance for any suggestions. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
Re: [gentoo-user] RAID: new drive on aac raid
Am 07.10.20 um 10:40 schrieb Stefan G. Weichinger: > Am 06.10.20 um 15:08 schrieb k...@aspodata.se: >> Stefan G. Weichinger: >>> I know the model: ICP5165BR >> >> https://ask.adaptec.com/app/answers/detail/a_id/17414/~/support-for-sata-and-sas-disk-drives-with-a-size-of-2tb-or-greater >> >> says it is supported up to 8TB drives using firmware v5.2.0 Build 17343 ** >> >> ** Firmware v5.2.0 Build 17343 for the ICP5045BL, ICP5085BL, ICP5805BL, >>ICP5125BR, and ICP5165BR: Adaptec is providing minimally tested >>firmware packages. Please contact Adaptec by PMC Technical Support >>to obtain these firmware files. Have the TSID or serial number of >>the product at hand when contacting support. > > Yes, I saw that as well. > > I managed to flash the "stable" firmware via arcconf, so I now have > 15753 ... > > I submitted a ticket there. They only offer support for money. I think I tried enough. Waiting for the smaller drive now. Thanks for your help, all.
Re: [gentoo-user] RAID: new drive on aac raid
Am 06.10.20 um 15:08 schrieb k...@aspodata.se: > Stefan G. Weichinger: >> I know the model: ICP5165BR > > https://ask.adaptec.com/app/answers/detail/a_id/17414/~/support-for-sata-and-sas-disk-drives-with-a-size-of-2tb-or-greater > > says it is supported up to 8TB drives using firmware v5.2.0 Build 17343 ** > > ** Firmware v5.2.0 Build 17343 for the ICP5045BL, ICP5085BL, ICP5805BL, >ICP5125BR, and ICP5165BR: Adaptec is providing minimally tested >firmware packages. Please contact Adaptec by PMC Technical Support >to obtain these firmware files. Have the TSID or serial number of >the product at hand when contacting support. Yes, I saw that as well. I managed to flash the "stable" firmware via arcconf, so I now have 15753 ... I submitted a ticket there. In the meantime we already ordered a smaller drive as well.
