[gentoo-user] How to config nullmailer
Recently, I typed 'mailq' and found some mail have not been sending. So I want to install a MTA, then found that the system have already installed nullmailer, but it did not work, and the config file at /etc/nullmailer/ is empty. Besides, wiki is useless. How to config this one, or I should replace it with postfix? bobwxc == -BEGIN PGP PUBLIC KEY BLOCK- mDMEX0aJURYJKwYBBAHaRw8BAQdASLmtsBXRo9ZbNOKisvEuvK8pTGNcsNgFsLU5 fcuEnd20G3ctY2hyb21lYm9vayAody1jaHJvbWVib29rKYiWBBMWCAA+FiEEeUf5 B4zw9YQZtU5OABzGqG8YykcFAl9GiVECGwMFCQlmAYAFCwkIBwIGFQoJCAsCBBYC AwECHgECF4AACgkQABzGqG8YykfF7QEAtdrAplwKcMnSBuxSQPRAQ+RvVaXt8sUc lVhtNSPukBABALWtY4J6deiihXG5o1zijsF85fucNiDTVLveIfSs+HYKuDgEX0aJ URIKKwYBBAGXVQEFAQEHQMcsqz2UMo1KjOi/dlismg6RUdf/mM5YcnqTR7PDGI59 AwEIB4h+BBgWCAAmFiEEeUf5B4zw9YQZtU5OABzGqG8YykcFAl9GiVECGwwFCQlm AYAACgkQABzGqG8YykcjqAD9Ffss3s6H/xiKdQ7IlcNlFNNKbTZjimxKOcVRO6eA r98A/0cWQxd4i7LWDHRu5ixbG0qT3WXipq+t22RpOqLM0IYO =TyBA -END PGP PUBLIC KEY BLOCK-
Re: [gentoo-user] [SOLVED] fsck.fat 4.1 - File system couldn't be fixed [SOLVED]
On 12/12/2020 11:00 PM, Victor Ivanov wrote: > On 13/12/2020 03:07, the...@sys-concept.com wrote: >> if you have UEFI system most likely your "boot" partition is some form >> of "vfat" > > I strongly disagree with this statement. Most Linux distributions, > including Gentoo, advise (or outright default to) having your /boot > partition either separate, or having /boot as part of your root > filesystem. And this is very sensible indeed. > > Personally, I would even go further by saying that /boot should be > journaled (e.g. ext4). Most distros do that by default. > > A UEFI set-up only requires the EFI system partition to be vfat. It does > not require the kernel or the ramdisk to be on it. GRUB2 can be > configured to install only its own EFI-related files on the EFI system > partition, then reading the kernel and the grub config file from your > /boot partition: > > # grub-install --efi-directory=/path/to/efi --boot-directory=/boot/efi > /dev/[nvme...|sd...] > > You do not need CSM enabled for this. > > Unfortunately, sometimes guides put the EFI partition mount point to be > a directory within the /boot directory (e.g. /boot/efi) which itself can > be the mount point for the boot partition. This can lead to people > formatting both as vfat or indeed using the EFI partition itself in lieu > of a separate /boot partition. I am not suggesting this is what happened > in your case, but I have seen it happen. > > Now if you use a different boot loader (e.g. rEFInd) it is up to that > bootloader to have relevant support for the filesystem that your /boot > partition is using. > >> fsck.fat 4.1 (2017-01-24) open: no such file or directory >> >> There is a similar related bug filed about it (but I don't know why is >> it marked resolved) >> https://bugs.gentoo.org/306119 > > I don't think this issue is related wrt the root cause. But > force-checking for filesystem errors certainly revealed the issue for > your case: you don't have the fsck.fat binary in your initramfs. As a > result, the filesystem checking process fails, the boot process is > interrupted prematurely, and you're dropped into a shell to investigate. > This is normal behaviour when an error occurs before the boot process > switches to the real root. > > One option is to disable filesystem checking for vfat - like you did, > another is to make sure that the mkfs.fat binary is included in the > ramdisk image. I am not sure how the latter would be best achieved with > genkernel, perhaps others can advise on this. > > - Victor You are absolutely correct. I'm an old timer, before there was no need for initramfs. One of my 10-year old system is still running /boot with ext2; never had a problem. HD is making noise and they system was running 24/7. But it is slowly failing, might be HD or memory. I was following the Gentoo handbook, maybe I didn't read it correctly and/or miss the information on alternative setting. I didn't see any explanation that I need to have support for "fsck.fat". I better stay away from any "vfat" format on boot partition, and I don't see a reason to have initramfs (another complexity).
Re: [gentoo-user] No logging output to tty12
> -- 原始邮件 -- > 发 件 人："Walter Dnes" > 发送时间：2020-12-13 01:54:32 > 收 件 人："Gentoo Users List" > 抄 送： > 主 题：[gentoo-user] No logging output to tty12 > > I used to get stuff going to tty12, e.g.when attaching a USB drive, > etc. My recent fresh install doesn't have this output. What am I doing > wrong? > > -- > Walter Dnes > I don't run "desktop environments"; I run useful applications check you /etc/inittab label # TERMINALS looks like: ``` # TERMINALS #x1:12345:respawn:/sbin/agetty 38400 console linux c1:12345:respawn:/sbin/agetty 38400 tty1 linux c2:2345:respawn:/sbin/agetty 38400 tty2 linux c3:2345:respawn:/sbin/agetty 38400 tty3 linux c4:2345:respawn:/sbin/agetty 38400 tty4 linux c5:2345:respawn:/sbin/agetty 38400 tty5 linux c6:2345:respawn:/sbin/agetty 38400 tty6 linux ``` the agetty will give a login console bobwxc == -BEGIN PGP PUBLIC KEY BLOCK- mDMEX0aJURYJKwYBBAHaRw8BAQdASLmtsBXRo9ZbNOKisvEuvK8pTGNcsNgFsLU5 fcuEnd20G3ctY2hyb21lYm9vayAody1jaHJvbWVib29rKYiWBBMWCAA+FiEEeUf5 B4zw9YQZtU5OABzGqG8YykcFAl9GiVECGwMFCQlmAYAFCwkIBwIGFQoJCAsCBBYC AwECHgECF4AACgkQABzGqG8YykfF7QEAtdrAplwKcMnSBuxSQPRAQ+RvVaXt8sUc lVhtNSPukBABALWtY4J6deiihXG5o1zijsF85fucNiDTVLveIfSs+HYKuDgEX0aJ URIKKwYBBAGXVQEFAQEHQMcsqz2UMo1KjOi/dlismg6RUdf/mM5YcnqTR7PDGI59 AwEIB4h+BBgWCAAmFiEEeUf5B4zw9YQZtU5OABzGqG8YykcFAl9GiVECGwwFCQlm AYAACgkQABzGqG8YykcjqAD9Ffss3s6H/xiKdQ7IlcNlFNNKbTZjimxKOcVRO6eA r98A/0cWQxd4i7LWDHRu5ixbG0qT3WXipq+t22RpOqLM0IYO =TyBA -END PGP PUBLIC KEY BLOCK-
Re: [gentoo-user] [SOLVED] fsck.fat 4.1 - File system couldn't be fixed [SOLVED]
On 13/12/2020 03:07, the...@sys-concept.com wrote: if you have UEFI system most likely your "boot" partition is some form of "vfat" I strongly disagree with this statement. Most Linux distributions, including Gentoo, advise (or outright default to) having your /boot partition either separate, or having /boot as part of your root filesystem. And this is very sensible indeed. Personally, I would even go further by saying that /boot should be journaled (e.g. ext4). Most distros do that by default. A UEFI set-up only requires the EFI system partition to be vfat. It does not require the kernel or the ramdisk to be on it. GRUB2 can be configured to install only its own EFI-related files on the EFI system partition, then reading the kernel and the grub config file from your /boot partition: # grub-install --efi-directory=/path/to/efi --boot-directory=/boot/efi /dev/[nvme...|sd...] You do not need CSM enabled for this. Unfortunately, sometimes guides put the EFI partition mount point to be a directory within the /boot directory (e.g. /boot/efi) which itself can be the mount point for the boot partition. This can lead to people formatting both as vfat or indeed using the EFI partition itself in lieu of a separate /boot partition. I am not suggesting this is what happened in your case, but I have seen it happen. Now if you use a different boot loader (e.g. rEFInd) it is up to that bootloader to have relevant support for the filesystem that your /boot partition is using. > fsck.fat 4.1 (2017-01-24) open: no such file or directory > > There is a similar related bug filed about it (but I don't know why is > it marked resolved) > https://bugs.gentoo.org/306119 I don't think this issue is related wrt the root cause. But force-checking for filesystem errors certainly revealed the issue for your case: you don't have the fsck.fat binary in your initramfs. As a result, the filesystem checking process fails, the boot process is interrupted prematurely, and you're dropped into a shell to investigate. This is normal behaviour when an error occurs before the boot process switches to the real root. One option is to disable filesystem checking for vfat - like you did, another is to make sure that the mkfs.fat binary is included in the ramdisk image. I am not sure how the latter would be best achieved with genkernel, perhaps others can advise on this. - Victor
Re: [gentoo-user] [SOLVED] fsck.fat 4.1 - File system couldn't be fixed [SOLVED]
On 12/12/2020 03:40 PM, Neil Bothwick wrote: > On Fri, 11 Dec 2020 14:36:51 -0700, the...@sys-concept.com wrote: > >> I wipe the /boot, reinstall kernel, initframes, grub. >> The system boots, I can login as root but X is not running, >> the command is displaying: "(none) /#" >> >> When I try to start the network I get: >> fsck.fat 4.1 (2017-01-24) open: no such file or directory >> Filesystems couldn't be fixed >> ERROR: fsck failed to start >> >> It seems to me "/" file system mount in "read only" mode. >> When I try to emerge anything I get: /var/log/emerge.log Read-only file >> system. > > Have you actually booted fully? This looks like the situation when > mounting root fails and the initramfs drops you to a console? Does mount > show that you partitions from fstab have mounted? A lot of folks get hurt over this bug, I'm supersized that nobody reported it yet that fsck.fat 4.1 has bugs. Symptoms: One day you end up with command line login: (none) login: Your root file system will be mounted as RO and only way to access your system is to boot-strap it. Recompiling anything (emerge -e system) will not help. The screen output fly by so fast that you need to have a high speed camera to catch the scrolling line. What help me is in "/" running: touch forcefsck It will force the system to run a check on all file systems in fstab. This will slow down the system, so you will notice that error message: fsck.fat 4.1 (2017-01-24) open: no such file or directory There is a similar related bug filed about it (but I don't know why is it marked resolved) https://bugs.gentoo.org/306119 SOLUTION (workaround): if you have UEFI system most likely your "boot" partition is some form of "vfat" if you have in fstab: LABEL=boot /boot vfatnoauto,noatime 1 2 Change it to: LABEL=boot /boot vfatnoauto,noatime 0 0 The force check of vfat system will skip and your system will boot normally. My permanent solution will be to go back to old reliable "ext2 as boot". Most newer BIOS system have CSM (compatibility support module under Boot menu) turning it ON will allow the boot partition to be in "ext2", it will avoid future problems with "fsck.fat" Running "boot" in ext2 I don't need "initramfs" either.
Re: [gentoo-user] update fails, but I don't see why
Have to agree with Neil on this one. You've got a LOT of updates. World is great, but start with emerge -UDuv @system, after you find the culprit that is still setting python3_6 as a target. Once the system emerge is done then you can try world again and hopefully get a much smaller list. We can help you much better from there. On 12/12/2020 3:35 PM, Neil Bothwick wrote: On Sat, 12 Dec 2020 23:08:15 +0100, n952162 wrote: I did a --depclean but that didn't help. I'm not seeing where an error is indicated. This was done with this still installed: */* PYTHON_TARGETS: python3_7 I commented that out and tried again, and after a few USE flag iterations, I ended up with what seems like the same situation. Log on request. There's a lot to trawl through here, it looks like you haven't updated for quite some time. I'd suggest you try to cut down on the noise by updating only @system instead of @world. A quick glance at some of the output suggests that you still have PYTHON_TARGETS="python3_6" set somewhere. What do grep -r python3_6 /etc/portage emerge --info | grep -i python tell you? -- Dan Egli From my Test Server
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
If you have a rescue cd, then you do just what I see you've already done. run fsck against the file sytem and let it fix any errors. As to being in read only mode, HOPEFULLY that's fixed, but if not you can try manually remounting your filesystem: mount / -o remount,rw On 12/12/2020 12:49 PM, the...@sys-concept.com wrote: How to to fix it? I can bootstrap from USB but what command to run it? On 12/12/2020 03:59 AM, Tamer Higazi wrote: Take systemrescuecd and fix your partitions. Let's see what might be the result. best, Tamer On 12/11/20 10:36 PM, the...@sys-concept.com wrote: I wipe the /boot, reinstall kernel, initframes, grub. The system boots, I can login as root but X is not running, the command is displaying: "(none) /#" When I try to start the network I get: fsck.fat 4.1 (2017-01-24) open: no such file or directory Filesystems couldn't be fixed ERROR: fsck failed to start It seems to me "/" file system mount in "read only" mode. When I try to emerge anything I get: /var/log/emerge.log Read-only file system. -- Dan Egli From my Test Server
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
You want to add it to the default command line in /etc/default/grub, if it's needed. Frankly, as long as you have ext4 support built in to your kernel (not a module) then I don't think you need it. I've gotten similar warnings on my machines and they've never had a problem loading the root FS. Oh, and it's not initframes, it is INIT RAM FS (no spaces, of course). For Initial Ram Filesystem. :) On 12/12/2020 12:47 PM, the...@sys-concept.com wrote: I took care of this error, it was about cfg80211 enable wireless support (which I don't have) so I disable it in .config. But when I generate initframes I'm getting a warning: genkernel --install --kernel-config=/usr/src/linux/.config initramfs * WARNING... WARNING... WARNING... * Additional kernel parameters that *may* be required to boot properly: * * With support for several ext* filesystems available, it may be needed to * add "rootfstype=ext3" or "rootfstype=ext4" to the list of boot parameters. Which grub file I edit to add support for "rootfstype=ext4" ? -- Dan Egli From my Test Server
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
On Fri, 11 Dec 2020 14:36:51 -0700, the...@sys-concept.com wrote: > I wipe the /boot, reinstall kernel, initframes, grub. > The system boots, I can login as root but X is not running, > the command is displaying: "(none) /#" > > When I try to start the network I get: > fsck.fat 4.1 (2017-01-24) open: no such file or directory > Filesystems couldn't be fixed > ERROR: fsck failed to start > > It seems to me "/" file system mount in "read only" mode. > When I try to emerge anything I get: /var/log/emerge.log Read-only file > system. Have you actually booted fully? This looks like the situation when mounting root fails and the initramfs drops you to a console? Does mount show that you partitions from fstab have mounted? -- Neil Bothwick Why is bra singular and pants plural? pgpsxihYqwumr.pgp Description: OpenPGP digital signature
Re: [gentoo-user] update fails, but I don't see why
On Sat, 12 Dec 2020 23:08:15 +0100, n952162 wrote: > I did a --depclean but that didn't help. I'm not seeing where an error > is indicated. > > This was done with this still installed: > > */* PYTHON_TARGETS: python3_7 > > I commented that out and tried again, and after a few USE flag > iterations, I ended up with what seems like the same situation. Log on > request. There's a lot to trawl through here, it looks like you haven't updated for quite some time. I'd suggest you try to cut down on the noise by updating only @system instead of @world. A quick glance at some of the output suggests that you still have PYTHON_TARGETS="python3_6" set somewhere. What do grep -r python3_6 /etc/portage emerge --info | grep -i python tell you? -- Neil Bothwick Never argue with an idiot. First, they bring you down to their level. Then they beat you with experience. pgp9ukqmfDk8J.pgp Description: OpenPGP digital signature
Re: [gentoo-user] fsck: caught SIGTERM, aborting
On 12/12/2020 02:03 PM, the...@sys-concept.com wrote: > I created empty "forcefsck" file in root (and reboot) to see what happens and > I get this: > > /dev/nvme0n1p4 780154/12206080 files (0.2% non-continous), 90753174/488213782 > blocks > fsck.fat 4.1 (2017-01-24) > Open: No such file or directory > * Filesystem couldn't be fixed > * rc: Aborting! > * * fsck: caught SIGTERM, aborting > INIT: Entering runlevel: 3 > * Checking local filesystems (check forced) ... I booted from USB and run: fsck -fy /dev/nvme0n1p4 fsck from util-linux 2.35.2 e2fsck 1.45.5 (07-Jan-2020) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/nvme0n1p4: 780154/122060800 files (0.2% non-contiguous), 90753174/488213782 blocks fsck -n /dev/nvme0n1p4 fsck from util-linux 2.35.2 e2fsck 1.45.5 (07-Jan-2020) /dev/nvme0n1p4: clean, 780154/122060800 files, 90753174/488213782 blocks (check after next mount)
[gentoo-user] fsck: caught SIGTERM, aborting
I created empty "forcefsck" file in root (and reboot) to see what happens and I get this: /dev/nvme0n1p4 780154/12206080 files (0.2% non-continous), 90753174/488213782 blocks fsck.fat 4.1 (2017-01-24) Open: No such file or directory * Filesystem couldn't be fixed * rc: Aborting! * * fsck: caught SIGTERM, aborting INIT: Entering runlevel: 3 * Checking local filesystems (check forced) ...
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
On 12/12/2020 12:32 AM, Dan Egli wrote: > Actually, you have an error or two below. > > On 12/11/2020 6:16 PM, the...@sys-concept.com wrote: >> No, I did not reformat the /boot partition. I just cd to /boot and run: >> rm -r * > Probably better to wipe the file system. But you talk about moving away > from EFI in another thread, so we'll just say that should this happen > again, you should wipe with mkfs. instead of just rm -r. >> >> Yes, this machine is new but I run it for a over 10-days, configured >> most of the programs and it was running without much problems. >> Yesterday, I decided to check some parameters in kernel .config so I run: >> genkernel --menuconfig all >> > Next time, just do this: > > cd /usr/src/linux > make menconfig (or nconfig) > >> * Gentoo Linux Genkernel; Version 4.1.2 >> * Using genkernel configuration from '/etc/genkernel.conf' ... >> * Running with options: --kernel-config=/proc/config.gz all >> >> * Working with Linux kernel 5.4.72-gentoo-x86_64 for x86_64 >> * Using kernel config file '/proc/config.gz' ... >> * >> * Note: The version above is subject to change (depends on config and >> status of kernel sources). >> >> * kernel: >> Initializing ... >> * >> Running 'make clean' ... >> * >> --mrproper is set; Making 'make mrproper' ... >> * >> Will ignore kernel config from '/proc/config.gz' >> * in favor of already existing but different kernel config >> * found in '/usr/src/linux/.config' ... >> * > So you are wrong below. As you can see above, genkernel IS using > /usr/src/linux/.config. I'm not 100% certain, but I THINK genkernel will > compare the config files, and prefer the .config if it is present. >> >> Running 'make oldconfig' ... >> * >> Compiling 5.4.72-gentoo-x86_64 bzImage ... >> >> >> When I exit it it started to compile the kernel (it did not finish) I >> pressed >> "CTRL-C" (interrupted). >> I didn't know then, but running genkernel --menuconfig all >> takes configuration from: >> /etc/kernels/kernel-config-5.4.72-gentoo-x86_64 >> >> not from: /usr/src/linux/.config > No, unless /etc/kernels/kernel-config- is NEWER than .config, > and maybe not even then. See above. >> However, NO FILE HAD CHANGED IN /boot >> But this this is the moment, I couldn't boot correctly. > What was the boot error? >> make && make modules_install >> make install >> genkernel --install --kernel-config=/usr/src/linux/.config initramfs >> grub-install --target=x86_64-efi --efi-directory=/boot >> grub-mkconfig -o /boot/grub/grub.cfg >> >> But nothing had changed. So I tired newer kernel: 5.4.80-gentoo-r1-x86_64 >> But this time I run (without interruptions): >> genkernel --menuconfig all >> grub-mkconfig -o /boot/grub/grub.cfg >> >> And again nothing changed, root "/" still mounts "ro" >> >> findmnt >> TARGET SOURCE FSTYPE OPTIONS >> / /dev/nvme0n1p4 ext4 ro,relatime >> >> Normally it should be: >> findmnt >> TARGET SOURCE FSTYPE OPTIONS >> / /dev/sda4 ext4 >> rw,noatime,data=ordered > Looks like it's not getting to the root remount stage. The kernel will > almost always boot in ro mode. So you're probably getting stuck in the > emergency shell. Can you see your device in /dev? Yes, I can see /dev/nvme0n1p4 (this is root partition) brw-rw root disk /dev/nvme0n1p4 >>> Does dmesg show the drive being recognised, corresponding drivers being >>> loaded, partitions and filesystems recognised? >> cat dmesg |grep error >> doesn't show any errors No, no errors in dmesg >> > What's the last 10 or so lines from dmesg when it fails to boot and goes > to what I'm guessing is the emergency shell? >> I'll try to boot GParted and see what comes up. > > > I don't think gparted is your answer. Sounds to me like something is > causing it to fail in the changeover from your initrd to the actual > drive. If that's the case I bet your partitions are fine. Can you show > us the last 10-15 lines printed on the screen before you get stuck? In dmesg, I see some lines at the end like: findsf (728) used greatest stack depth: 14048 bytes left EXT4-fs (nvme0n1p4): mounted filesystem with ordered data mode. Opts: (null) findsf (728) used greatest stack depth: 13896 bytes left awk (735) used greatest stack depth: 13000 bytes left udevd (682) used greatest stack depth: 13792 bytes left
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
How to to fix it? I can bootstrap from USB but what command to run it? On 12/12/2020 03:59 AM, Tamer Higazi wrote: > Take systemrescuecd and fix your partitions. > > Let's see what might be the result. > > > best, Tamer > > On 12/11/20 10:36 PM, the...@sys-concept.com wrote: >> I wipe the /boot, reinstall kernel, initframes, grub. >> The system boots, I can login as root but X is not running, >> the command is displaying: "(none) /#" >> >> When I try to start the network I get: >> fsck.fat 4.1 (2017-01-24) open: no such file or directory >> Filesystems couldn't be fixed >> ERROR: fsck failed to start >> >> It seems to me "/" file system mount in "read only" mode. >> When I try to emerge anything I get: /var/log/emerge.log Read-only file >> system. >> >> > >
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
On 12/12/2020 12:25 PM, Dan Egli wrote: > Hmmm, looks like a missing or corrupted firmware file is failing to > load. Observe: > > On 12/12/2020 11:48 AM, the...@sys-concept.com wrote: >> >> platform regulatory.0: Direct firmware load for regulatory.db failed >> with error -2 >> cfg80211: failed to load regulatory.db >> nvme mvme0: missing or invalid SUBNQN field >> > I'd say, off my head, that your regulatory.db file has gotten corrupted. > I'd suggest booting from a rescue CD, chrooting into your main > partition, and reinstalling your firmware. It mentions the wireless, of > course (cfg80211) but also it looks like either the firmware or the > driver for your nvme system has gotten corrupted. It's obviously > present, but it's complaining about missing information. You may want to > go ahead and re-compile the kernel and the modules.If you're using > genkernel I'd even go so far as to suggest a mrproper. Just to ensure > that EVERYTHING is cleaned out. Then let genkernel rebuild everything. > Another option, although one I dislike for _purely ascetic_ reasons, > would be to just grab the gentoo-kernel-bin package. That's a > precompiled kernel with a lot of stuff enabled as modules. It could very > well be helpful in getting your system back on it's feet. I took care of this error, it was about cfg80211 enable wireless support (which I don't have) so I disable it in .config. But when I generate initframes I'm getting a warning: genkernel --install --kernel-config=/usr/src/linux/.config initramfs * WARNING... WARNING... WARNING... * Additional kernel parameters that *may* be required to boot properly: * * With support for several ext* filesystems available, it may be needed to * add "rootfstype=ext3" or "rootfstype=ext4" to the list of boot parameters. Which grub file I edit to add support for "rootfstype=ext4" ?
Re: [gentoo-user] Gobbledegook error message from emerge.
On Sat, Dec 12, 2020 at 5:08 AM Alan Mackenzie wrote: > > Hello, Mark. > > On Fri, Dec 11, 2020 at 12:11:02 -0700, Mark Knecht wrote: > > On Fri, Dec 11, 2020 at 11:09 AM Alan Mackenzie wrote: > > > > > (dependency required by "dev-vcs/bzr-2.7.0::gentoo" [installed]) > > > (dependency required by "@selected" [set]) > > > (dependency required by "@world" [argument]) > > > > So I'm totally guessing here but as you have no other responses yet: > > > I'd start near the 'top', which of course is near the bottom. > > > What is 'bzr'? > > > https://packages.gentoo.org/categories/dev-vcs > > It is (or was) the version control system bazaar. It was a competitor > for mercurial and git, but just wasn't quite as good. It was poorly > documented, too (like git still is). It became unmaintained maybe three > or four years ago. And it was written in python. > > > I do not see 'bzr' on this page. Is it something left over in your world > > file, or just installed by some other app and no longer used, or moved to > > some other package category? > > I used to use bazaar until the Emacs project converted to git. It's > time I expunged it altogether. > > > If you don't know what it is and think you don't need it then if it were me > > I'd consider just removing it and letting emerge @world figure out how to > > proceed. > > > And all of that is just a guess. No Gentoo available right now to delve > > further. > > > Best of luck, > > Thanks! Hey, I got lucky! Not bad for not even having a Gentoo machine to double check on. Glad it worked out. I think the lesson here is start at the bottom and work up toward the problem. That first line is just that in the weeds computer stuff. Cheers, Mark
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
Hmmm, looks like a missing or corrupted firmware file is failing to load. Observe: On 12/12/2020 11:48 AM, the...@sys-concept.com wrote: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 cfg80211: failed to load regulatory.db nvme mvme0: missing or invalid SUBNQN field I'd say, off my head, that your regulatory.db file has gotten corrupted. I'd suggest booting from a rescue CD, chrooting into your main partition, and reinstalling your firmware. It mentions the wireless, of course (cfg80211) but also it looks like either the firmware or the driver for your nvme system has gotten corrupted. It's obviously present, but it's complaining about missing information. You may want to go ahead and re-compile the kernel and the modules.If you're using genkernel I'd even go so far as to suggest a mrproper. Just to ensure that EVERYTHING is cleaned out. Then let genkernel rebuild everything. Another option, although one I dislike for _purely ascetic_ reasons, would be to just grab the gentoo-kernel-bin package. That's a precompiled kernel with a lot of stuff enabled as modules. It could very well be helpful in getting your system back on it's feet. -- Dan Egli From my Test Server
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
On 12/12/2020 12:32 AM, Dan Egli wrote: > Actually, you have an error or two below. > > On 12/11/2020 6:16 PM, the...@sys-concept.com wrote: >> No, I did not reformat the /boot partition. I just cd to /boot and run: >> rm -r * > Probably better to wipe the file system. But you talk about moving away > from EFI in another thread, so we'll just say that should this happen > again, you should wipe with mkfs. instead of just rm -r. >> >> Yes, this machine is new but I run it for a over 10-days, configured >> most of the programs and it was running without much problems. >> Yesterday, I decided to check some parameters in kernel .config so I run: >> genkernel --menuconfig all >> > Next time, just do this: > > cd /usr/src/linux > make menconfig (or nconfig) > >> * Gentoo Linux Genkernel; Version 4.1.2 >> * Using genkernel configuration from '/etc/genkernel.conf' ... >> * Running with options: --kernel-config=/proc/config.gz all >> >> * Working with Linux kernel 5.4.72-gentoo-x86_64 for x86_64 >> * Using kernel config file '/proc/config.gz' ... >> * >> * Note: The version above is subject to change (depends on config and >> status of kernel sources). >> >> * kernel: >> Initializing ... >> * >> Running 'make clean' ... >> * >> --mrproper is set; Making 'make mrproper' ... >> * >> Will ignore kernel config from '/proc/config.gz' >> * in favor of already existing but different kernel config >> * found in '/usr/src/linux/.config' ... >> * > So you are wrong below. As you can see above, genkernel IS using > /usr/src/linux/.config. I'm not 100% certain, but I THINK genkernel will > compare the config files, and prefer the .config if it is present. >> >> Running 'make oldconfig' ... >> * >> Compiling 5.4.72-gentoo-x86_64 bzImage ... >> >> >> When I exit it it started to compile the kernel (it did not finish) I >> pressed >> "CTRL-C" (interrupted). >> I didn't know then, but running genkernel --menuconfig all >> takes configuration from: >> /etc/kernels/kernel-config-5.4.72-gentoo-x86_64 >> >> not from: /usr/src/linux/.config > No, unless /etc/kernels/kernel-config- is NEWER than .config, > and maybe not even then. See above. >> However, NO FILE HAD CHANGED IN /boot >> But this this is the moment, I couldn't boot correctly. > What was the boot error? >> make && make modules_install >> make install >> genkernel --install --kernel-config=/usr/src/linux/.config initramfs >> grub-install --target=x86_64-efi --efi-directory=/boot >> grub-mkconfig -o /boot/grub/grub.cfg >> >> But nothing had changed. So I tired newer kernel: 5.4.80-gentoo-r1-x86_64 >> But this time I run (without interruptions): >> genkernel --menuconfig all >> grub-mkconfig -o /boot/grub/grub.cfg >> >> And again nothing changed, root "/" still mounts "ro" >> >> findmnt >> TARGET SOURCE FSTYPE OPTIONS >> / /dev/nvme0n1p4 ext4 ro,relatime >> >> Normally it should be: >> findmnt >> TARGET SOURCE FSTYPE OPTIONS >> / /dev/sda4 ext4 >> rw,noatime,data=ordered > Looks like it's not getting to the root remount stage. The kernel will > almost always boot in ro mode. So you're probably getting stuck in the > emergency shell. Can you see your device in /dev? >>> Does dmesg show the drive being recognised, corresponding drivers being >>> loaded, partitions and filesystems recognised? >> cat dmesg |grep error >> doesn't show any errors >> > What's the last 10 or so lines from dmesg when it fails to boot and goes > to what I'm guessing is the emergency shell? >> I'll try to boot GParted and see what comes up. > > > I don't think gparted is your answer. Sounds to me like something is > causing it to fail in the changeover from your initrd to the actual > drive. If that's the case I bet your partitions are fine. Can you show > us the last 10-15 lines printed on the screen before you get stuck? The last 10-15 lines are not showing much but there is more (I'm retyping it from the screen) dmesg: (why the line BOOT_IMAGE is Read Only) Kernel command line: BOOT_IMAGE=/vmlinuz-5.7.72-gentoo root=UUID=d3229... ro platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 cfg80211: failed to load regulatory.db nvme mvme0: missing or invalid SUBNQN field usb 3-4: config 1 has an invalid interface number: 2 but nax is 1 usb 3-4: config 1 has no interface number 1
Re: [gentoo-user] Gobbledegook error message from emerge.
I doubt goblins wrote any part of gentoo, from what Neil wrote me earlier if memory serves the language is actually Portagese. On Sat, 12 Dec 2020, Alan Mackenzie wrote: > Date: Sat, 12 Dec 2020 09:22:40 > From: Alan Mackenzie > Reply-To: gentoo-user@lists.gentoo.org > To: gentoo-user@lists.gentoo.org > Subject: Re: [gentoo-user] Gobbledegook error message from emerge. > > Hello, Neil. > > On Fri, Dec 11, 2020 at 21:05:48 +, Neil Bothwick wrote: > > On Fri, 11 Dec 2020 18:08:55 +, Alan Mackenzie wrote: > > > > I got back a horrendously long list of packages to merge (most of them > > > re-merges), followed by: > > > > emerge: there are no ebuilds built with USE flags to satisfy > > > "dev-python/pycparser[python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]". > > > !!! One of the following packages is required to complete your request: > > > - dev-python/pycparser-2.20-r1::gentoo (Change USE: > > > +python_targets_python3_7) > > > - dev-python/cffi-1.14.0-r3::gentoo (Change USE: > > > -python_targets_python3_7) (dependency required by > > > A required package is just a dependency. If package A depends on package > > B then package B is required is you have A installed. > > OK. I can now see that "dependency required by" just means "is a > dependency of". Dependency is a relationship; it is not a thing. > > > > "dev-python/cffi-1.14.0-r3::gentoo" [ebuild]) (dependency required by > > > "dev-python/bcrypt-3.2.0::gentoo" [installed]) (dependency required by > > > "dev-python/paramiko-2.7.1::gentoo" [installed]) (dependency required > > > by "dev-vcs/bzr-2.7.0::gentoo" [installed]) > > > This is part of the python cleanup/upgrade already discussed at length on > > this list over the past week, so the answers are already available. > > Yes, sorry. I've not been keeping up with the list as assiduously as I > might. > > > You have had some useful replies already but one thing I noticed it > > that this is brought about by bzr, which is no longer in portage. > > Unless you have it installed from an overlay for a particular need of > > yours, you should let it be depcleaned. > > Yes, bazaar was indeed the sticking point. It's been unmaintained for > quite a few years, and is written in python. I just unmerged it, then > the mega-merge went ahead without problems (though I excluded > libreoffice from that merge, for now). > > I still amn't happy about the error message I got. But I'm not unhappy > enough about it to invest the time needed to get up to speed on portage > and submit patches. :-( > > Anyhow, thanks for the tip! > > > -- > > Neil Bothwick > > > A TRUE Klingon warrior does not comment his code! > > --
[gentoo-user] No logging output to tty12
I used to get stuff going to tty12, e.g.when attaching a USB drive, etc. My recent fresh install doesn't have this output. What am I doing wrong? -- Walter Dnes I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] Gobbledegook error message from emerge.
Hello, Neil. On Fri, Dec 11, 2020 at 21:05:48 +, Neil Bothwick wrote: > On Fri, 11 Dec 2020 18:08:55 +, Alan Mackenzie wrote: > > I got back a horrendously long list of packages to merge (most of them > > re-merges), followed by: > > emerge: there are no ebuilds built with USE flags to satisfy > > "dev-python/pycparser[python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]". > > !!! One of the following packages is required to complete your request: > > - dev-python/pycparser-2.20-r1::gentoo (Change USE: > > +python_targets_python3_7) > > - dev-python/cffi-1.14.0-r3::gentoo (Change USE: > > -python_targets_python3_7) (dependency required by > A required package is just a dependency. If package A depends on package > B then package B is required is you have A installed. OK. I can now see that "dependency required by" just means "is a dependency of". Dependency is a relationship; it is not a thing. > > "dev-python/cffi-1.14.0-r3::gentoo" [ebuild]) (dependency required by > > "dev-python/bcrypt-3.2.0::gentoo" [installed]) (dependency required by > > "dev-python/paramiko-2.7.1::gentoo" [installed]) (dependency required > > by "dev-vcs/bzr-2.7.0::gentoo" [installed]) > This is part of the python cleanup/upgrade already discussed at length on > this list over the past week, so the answers are already available. Yes, sorry. I've not been keeping up with the list as assiduously as I might. > You have had some useful replies already but one thing I noticed it > that this is brought about by bzr, which is no longer in portage. > Unless you have it installed from an overlay for a particular need of > yours, you should let it be depcleaned. Yes, bazaar was indeed the sticking point. It's been unmaintained for quite a few years, and is written in python. I just unmerged it, then the mega-merge went ahead without problems (though I excluded libreoffice from that merge, for now). I still amn't happy about the error message I got. But I'm not unhappy enough about it to invest the time needed to get up to speed on portage and submit patches. :-( Anyhow, thanks for the tip! > -- > Neil Bothwick > A TRUE Klingon warrior does not comment his code! -- Alan Mackenzie (Nuremberg, Germany).
Re: [gentoo-user] switching from "refine" to "grub"
On Sat, 12 Dec 2020 01:57:40 -0700, Dan Egli wrote: > What complexity? GRUB2 is hugely complex as it tries to be everything to everyone. That's not a bad thing in itself, but EFI can use a far more minimal setup. > I have a couple EFI machines booting via Grub, and > they work great. I didn't say it didn't work, but it is overkill for EFI booting where a bootloader isn't needed. > I just had to ensure the correct GRUB_TARGET in > make.conf and then after I had my partitions setup and formatted, I > just did grub-install --target=x86_64-efi --efi-directory=/boot/EFI and > it went smooth as silk as long as I didn't have /boot on newer ZFS > setup. Even ZFS would work if you setup /boot to be a separate dataset > and make it with absolute minimal options. > > On 12/12/2020 1:31 AM, Neil Bothwick wrote: > > On Fri, 11 Dec 2020 07:48:06 -0700, the...@sys-concept.com wrote: > > > >> I use refine as boot loader but it is giving me a problems. > >> How to switch back to grub 2 > >> And remove any refine files from /boot > > I take it you mean refind? It may well be easier to solve the problem > > with refind rather than trying to deal with the overcomplexity of GRUB > > for an EFI system. > > > > I normally use systemd-boot but when I have used refind, it has > > picked up everything it needs to know without a config file. What > > errors are you seeing? > > > > -- Neil Bothwick Sir! Romulan warbird decloaki\xBB\xAE\xF5\xF7\xFC\xC1 NO CARRIER pgp_Sd7I8LwqB.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Gobbledegook error message from emerge.
On Fri, 11 Dec 2020 at 19:09, Alan Mackenzie wrote: > emerge: there are no ebuilds built with USE flags to satisfy > "dev-python/pycparser[python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]". > !!! One of the following packages is required to complete your request: > - dev-python/pycparser-2.20-r1::gentoo (Change USE: +python_targets_python3_7) > - dev-python/cffi-1.14.0-r3::gentoo (Change USE: -python_targets_python3_7) > (dependency required by "dev-python/cffi-1.14.0-r3::gentoo" [ebuild]) > (dependency required by "dev-python/bcrypt-3.2.0::gentoo" [installed]) > (dependency required by "dev-python/paramiko-2.7.1::gentoo" [installed]) > (dependency required by "dev-vcs/bzr-2.7.0::gentoo" [installed]) > (dependency required by "@selected" [set]) > (dependency required by "@world" [argument]) To solve your problem, you already have your answer (remove dev-vcs/bzr), but I don't think you got the explanation you wanted for the logic of this output, so I'll also give it a go. I would really ignore the first line with all the brackets and question marks unless you are completely unable to fix your problem, but the logic of the rest of the lines, as I understand them, is as follows: Your problem has two possible solutions, either ADD py3.7 (USE="python_targets_python3_7") to dev-python/pycparser, or REMOVE py3.7 (USE="-python_targets_python3_7") to dev-python/cffi. This is required by dev-python/cffi-1.14.0-r3::gentoo. Which in turn is required by dev-python/bcrypt-3.2.0::gentoo. Which in turn is required by dev-python/paramiko-2.7.1::gentoo Which in turn is required by dev-vcs/bzr-2.7.0::gentoo Which in turn is required by the selected packages which the current emerge command was given Which in turn was found through the emerge argument @world In other words, the "dependency of A on B" you speak about is clearly outlined here, but it is as a chain of dependencies, and hence spread out over multiple lines, which in my opinion for these kinds of things actually makes it more readable. But of course, you have to first know what is trying to express, before you can decipher the syntax. Regards, Arve
Re: [gentoo-user] Gobbledegook error message from emerge.
Hello, Mark. On Fri, Dec 11, 2020 at 12:11:02 -0700, Mark Knecht wrote: > On Fri, Dec 11, 2020 at 11:09 AM Alan Mackenzie wrote: > > > (dependency required by "dev-vcs/bzr-2.7.0::gentoo" [installed]) > > (dependency required by "@selected" [set]) > > (dependency required by "@world" [argument]) > So I'm totally guessing here but as you have no other responses yet: > I'd start near the 'top', which of course is near the bottom. > What is 'bzr'? > https://packages.gentoo.org/categories/dev-vcs It is (or was) the version control system bazaar. It was a competitor for mercurial and git, but just wasn't quite as good. It was poorly documented, too (like git still is). It became unmaintained maybe three or four years ago. And it was written in python. > I do not see 'bzr' on this page. Is it something left over in your world > file, or just installed by some other app and no longer used, or moved to > some other package category? I used to use bazaar until the Emacs project converted to git. It's time I expunged it altogether. > If you don't know what it is and think you don't need it then if it were me > I'd consider just removing it and letting emerge @world figure out how to > proceed. > And all of that is just a guess. No Gentoo available right now to delve > further. > Best of luck, Thanks! > Mark -- Alan Mackenzie (Nuremberg, Germany).
Re: [gentoo-user] UEFI system - installing Grub without EFI
On Saturday, 12 December 2020 07:51:06 GMT J. Roeleveld wrote: > On 12 December 2020 03:28:35 CET, the...@sys-concept.com wrote: > >I was trying to check VFAT boot partition on my disk with Gparted but > >it failed. Root partition checked OK. How did it fail? What message did you get? How did you repair it? > >Can I format the VFAT to EXT2 and install grub on it without EFI? Why? What is there to gain by moving from UEFI firmware booting your OS, to using the same UEFI firmware to emulate a legacy BIOS in order to boot your OS? I suggest it would be better to find out what is wrong with your UEFI set up and fix that in the first instance, instead of jumping around without bottoming out the cause of any failure. > >There is a possibility VFAT partition got damaged. > > UEFI needs VFAT for the efi-partition. Yes, a UEFI MoBo needs a partition type of ESP 'EFI system partition' formatted in fat (12, 16, or 32). signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
Take systemrescuecd and fix your partitions. Let's see what might be the result. best, Tamer On 12/11/20 10:36 PM, the...@sys-concept.com wrote: I wipe the /boot, reinstall kernel, initframes, grub. The system boots, I can login as root but X is not running, the command is displaying: "(none) /#" When I try to start the network I get: fsck.fat 4.1 (2017-01-24) open: no such file or directory Filesystems couldn't be fixed ERROR: fsck failed to start It seems to me "/" file system mount in "read only" mode. When I try to emerge anything I get: /var/log/emerge.log Read-only file system.
Re: [gentoo-user] switching from "refine" to "grub"
What complexity? I have a couple EFI machines booting via Grub, and they work great. I just had to ensure the correct GRUB_TARGET in make.conf and then after I had my partitions setup and formatted, I just did grub-install --target=x86_64-efi --efi-directory=/boot/EFI and it went smooth as silk as long as I didn't have /boot on newer ZFS setup. Even ZFS would work if you setup /boot to be a separate dataset and make it with absolute minimal options. On 12/12/2020 1:31 AM, Neil Bothwick wrote: On Fri, 11 Dec 2020 07:48:06 -0700, the...@sys-concept.com wrote: I use refine as boot loader but it is giving me a problems. How to switch back to grub 2 And remove any refine files from /boot I take it you mean refind? It may well be easier to solve the problem with refind rather than trying to deal with the overcomplexity of GRUB for an EFI system. I normally use systemd-boot but when I have used refind, it has picked up everything it needs to know without a config file. What errors are you seeing? -- Dan Egli From my Test Server
Re: [gentoo-user] switching from "refine" to "grub"
On Fri, 11 Dec 2020 07:48:06 -0700, the...@sys-concept.com wrote: > I use refine as boot loader but it is giving me a problems. > How to switch back to grub 2 > And remove any refine files from /boot I take it you mean refind? It may well be easier to solve the problem with refind rather than trying to deal with the overcomplexity of GRUB for an EFI system. I normally use systemd-boot but when I have used refind, it has picked up everything it needs to know without a config file. What errors are you seeing? -- Neil Bothwick "Do not handicap your children by making their lives easy." -- Robert Heinlein pgpnqewHvzCa9.pgp Description: OpenPGP digital signature
