Re: [gentoo-user] system won't boot - --no-bootloader set; Skipping bootloader update ...
On Fri, Dec 11, 2020 at 9:27 AM wrote: > On 12/11/2020 07:07 AM, the...@sys-concept.com wrote: > > Now, when I boot I get a message: > > > > Block device UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b is not a valid > > root device. > > This puzzles me. I cannot find the string "is not a valid root device" (or sub-strings) in the source code for the Linux kernel, GRUB2, and refind. It seems to me it should be in one of them. - Matthew
Re: [gentoo-user] Converting Unix time to local time
You might be able to use this shell command: TZ=US/Pacific date --date='@2147483647' - Matthew
Re: [gentoo-user] Initial console messages garbled
Robin, are you comfortable just going with a bare-bones console and build a new kernel where you _disable_ CONFIG_FB? That might do it. Alternately, you can hook up a serial cable to another computer and set "console=ttyS0,115200n8". - Matthew
Re: [gentoo-user] Hangs at "Run /init as init process"
You might verify what kind of console your VM is using. Is it VGA or serial? You can tell it to print boot messages early: earlyprintk=vga or earlyprintk=ttyS0,115200n8 - Matthew
Re: [gentoo-user] cmake 3.16.5 Segmentation Violation
On Wed, Jun 3, 2020 at 1:43 PM David Haller wrote: > > Hello, > > On Wed, 03 Jun 2020, tedheadster wrote: > >I am getting a segmentation violation when running a recompiled > >'cmake'. I rebuilt with debugging symbols; here are the results: > > > >/var/tmp/portage/dev-util/cmake-3.16.5/image/usr/bin # gdb ./cmake > [..] > >Program received signal SIGSEGV, Segmentation fault. > >0xb7de7296 in uv_loop_close (loop=0x0) at > > >/usr/src/debug/dev-libs/libuv-1.35.0/libuv-1.35.0/src/uv-common.c:757 > ^^ > >757 if (uv__has_active_reqs(loop)) > >(gdb) up > >#1 0x0053fab4 in main (ac=, av=0xb09a60) > >at > > /var/tmp/portage/dev-util/cmake-3.16.5/work/cmake-3.16.5/Source/cmakemain.cxx:706 > >706 uv_loop_close(uv_default_loop()); > >(gdb) up > > Try re-emerging dev-libs/libuv? I already had to re-emerge dev-libs/libuv to build the debug version. No change in behavior. This is from a completely fresh install using the very recent stage3-i686-systemd-20200527T000231Z.tar.xz. - Matthew
Re: [gentoo-user] Kernel panic - not syncing: No working init found.
Yes, you do need to capture the kernel output. The usual way is to hook up a serial cable to another computer and pipe the output to it. You interrupt the boot (usually by hitting or in GRUB), and then edit the kernel command line thus: console=tty1 console=ttyS0,115200n8 If you can do that you can give us some debug output. - Matthew
Re: [gentoo-user] Kernel panic - not syncing: No working init found.
Can you provide the "Command line:" information from when the kernel first boots? It is around line 5 or so. - Matthew
[gentoo-user] cmake 3.16.5 Segmentation Violation
I am getting a segmentation violation when running a recompiled 'cmake'. I rebuilt with debugging symbols; here are the results: /var/tmp/portage/dev-util/cmake-3.16.5/image/usr/bin # gdb ./cmake GNU gdb (Gentoo 9.1 vanilla) 9.1 Copyright (C) 2020 Free Software Foundation, Inc. ... Reading symbols from ./cmake... (gdb) run --version Starting program: /var/tmp/portage/dev-util/cmake-3.16.5/image/usr/bin/cmake --version [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". cmake version 3.16.5 CMake suite maintained and supported by Kitware (kitware.com/cmake). Program received signal SIGSEGV, Segmentation fault. 0xb7de7296 in uv_loop_close (loop=0x0) at /usr/src/debug/dev-libs/libuv-1.35.0/libuv-1.35.0/src/uv-common.c:757 757 if (uv__has_active_reqs(loop)) (gdb) up #1 0x0053fab4 in main (ac=, av=0xb09a60) at /var/tmp/portage/dev-util/cmake-3.16.5/work/cmake-3.16.5/Source/cmakemain.cxx:706 706 uv_loop_close(uv_default_loop()); (gdb) up Initial frame selected; you cannot go up. (gdb) Who can I work with to debug this? - Matthew
Re: [gentoo-user] 32GB RAM and Swap
Here is an article suggesting to have a _tiny_ bit of swap. They say as recently as 2019 that Linux under memory pressure acts poorly with _zero_ swap. https://rachelbythebay.com/w/2019/08/08/swap/ - Matthew
Re: [gentoo-user] can you save a filesystem destroyed with mkswap?
On Sat, Jan 18, 2020 at 6:32 AM Wols Lists wrote: > > Not that I know any gory details, but if mkswap is ALL that you have > done, then probably it's just destroyed the ext header at the start of > the partition. > > If you can get hold of the alternate (backup) header, then you should be > able to restore the filesystem. > You can learn where the alternate superblocks are by doing a 'mkfs.ext3 -n /dev/$BAD_DEV' and it will do _nothing_ to the disk, but it will tell you where it places the backup superblocks for a disk that size. - Matthew
Re: [gentoo-user] Not enough RAM for dev-qt/qtwebengine build
Alexey, you can check /etc/portage/make.conf and see if there is a MAKEOPTS="-j8" or similar variable. If not, add it and make the number of jobs small, like "-j2". I have a similar problem when I build sys-devel/binutils; it is a huge memory hog. - Matthew
[gentoo-user] emerge with alternate ROOT=
I am having problems trying to rebuild a slave disk with ROOT=/mnt/gentoo. While it is _sort_ of working, it does something very unexpected. It rebuilds 154 packages on the _host_ system. Oddly, it does notice that I have different CFLAGS set in /etc/portage/make.conf and rebuilds the host system packages correctly. But why does it rebuild them at all? Here is a sample of the emerge output: [ebuild R] sys-apps/systemd-241-r1 to /mnt/gentoo/ [ebuild R] sys-process/procps-3.3.15-r1 to /mnt/gentoo/ [ebuild R] sys-apps/gentoo-systemd-integration-7 to /mnt/gentoo/ [ebuild R] virtual/service-manager-0 to /mnt/gentoo/ [ebuild R] sys-apps/attr-2.4.47-r2 [ebuild R] sys-devel/patch-2.7.6-r3 [ebuild R] sys-apps/systemd-241-r1 [ebuild R] sys-apps/gentoo-systemd-integration-7 Why the heck is the _host_ sys-apps/systemd being recompiled? Here is my command: export ROOT="/mnt/gentoo" export DISTDIR="/mnt/gentoo/usr/portage/distfiles" export PKGDIR="/mnt/gentoo/usr/portage/packages" export PORTAGE_CONFIGROOT="/mnt/gentoo/" export PORTAGE_TMPDIR="/var/tmp" export PORTDIR="/mnt/gentoo/usr/portage" export EMERGE_LOG_DIR="/mnt/gentoo/var/log" emerge --root=/mnt/gentoo --root-deps --color n --ask -e @world - Matthew
