Re: [gentoo-user] frei0r-plugins opencv ffmpeg Error: circular dependencies
On Monday, 29 April 2024 06:07:04 BST Dale wrote: > Dale wrote: > > Howdy, > > > > I'm installing Gentoo on that old Dell Inspiron still. I'm getting > > close. I'm now at this. > > > > > > * Error: circular dependencies: > > > > (media-plugins/frei0r-plugins-1.8.0:0/0::gentoo, ebuild scheduled for > > merge) depends on > > (media-libs/opencv-4.9.0:0/4.9.0::gentoo, ebuild scheduled for merge) > > (buildtime_slot_op) > > (media-video/ffmpeg-6.1.1-r5:0/58.60.60::gentoo, ebuild scheduled for > > merge) (buildtime_slot_op) > >(media-plugins/frei0r-plugins-1.8.0:0/0::gentoo, ebuild scheduled for > > merge) (buildtime) > > > > It might be possible to break this cycle > > by applying any of the following changes: > > - media-video/ffmpeg-6.1.1-r5 (Change USE: -frei0r) > > - media-plugins/frei0r-plugins-1.8.0 (Change USE: -facedetect) > > - media-libs/opencv-4.9.0 (Change USE: -ffmpeg) > > > > Note that this change can be reverted, once the package has been > > installed. > > NAS2 ~ # > > > > > > Earlier, I added those USE flags so that it could continue on with the > > install. I figured it was like that harfbuzz and something else thing. > > Now that everything else is done, I want to go back to the default USE > > flags, like it said I could. Thing is, when I remove the ones it wants > > above, it still complains. It either fails to build or spits out > > something like above. > > > > Has anyone doing a recent new install ran into this and know how to get > > around it? I've tried different options but they either fail or tell me > > to change back to the settings it suggests above. I searched the forums > > but didn't find anything. Google didn't find anything either. I may > > have found something new. ROFL > > > > Thoughts?? > > > > Dale > > > > :-) :-) > > Found a solution for most of it. When I did my install, I added a line > for CFLAGS but failed to comment out the other line. It seems to have > confused either emerge or that package or maybe both. Basically, it > left it empty, no setting at all. > > Now I'm left with a failure for net-dns/avahi which gives me this: > > > sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \ > -e 's,@servicedir\@,/etc/avahi/services,g' \ > -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop > (dot) org,g' \ > -e 's,@PACKAGE_URL\@,http://avahi.org/,g' > avahi-discover.1.xml.in > avahi-discover.1.xml > sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \ > -e 's,@servicedir\@,/etc/avahi/services,g' \ > -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop > (dot) org,g' \ > -e 's,@PACKAGE_URL\@,http://avahi.org/,g' > avahi-bookmarks.1.xml.in > avahi-bookmarks.1.xml > sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \ > -e 's,@servicedir\@,/etc/avahi/services,g' \ > -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop > (dot) org,g' \ > -e 's,@PACKAGE_URL\@,http://avahi.org/,g' bssh.1.xml.in > bssh.1.xml > xmltoman avahi-daemon.8.xml > avahi-daemon.8 > Can't locate XML/Parser.pm in @INC (you may need to install the > XML::Parser module) (@INC entries checked: /etc/perl This message above looks suspicious: "Can't locate XML/Parser.pm in @INC (you may need to install the XML::Parser module) (@INC entries checked: /etc/perl" In the first instance I'd throw 'perl-cleaner --reallyall' at it and see if the situation improves. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.
On Sunday, 28 April 2024 19:39:16 BST Dale wrote: > Grant Edwards wrote: > > On 2024-04-28, Grant Edwards wrote: > >> With DOS disk lables, Grub uses empty space between the boot sector > >> and the first partition as a location to store it's core image file. > >> That empty space does not exist when using GPT disk label. When using > >> a GPT disk label, Grub requires that you need to create a "BIOS Boot" > >> or "Grub Boot" partition so that Grub has somwhere to store it's core > >> image[1]. > > > > And it bears repeating that the bios/grub boot partition only needs to > > be 1 or 2MB in size, is _not_ formatted with a filesystem, and is > > _not_ the same as either > > > > 1) The "boot" directory where the kernel images and grubs other files > > > > are installed within a Linux filesystem. [Which you still need > > when booting in Legacy/BIOS mode.] > > > > or > > > > 2) The UEFI partition that's formated with a FAT filesystem and used > > > > in UEFI boot mode [which you don't need when booting in > > Legacy/BIOS mode.] > > I think I got a grasp on this now. Basically, partitions should be like > this. > > > First spot is the alignment thing. Usually a few MBs or so and unused. This is created automatically by the partitioning tool, in your case cgdisk, when you create the first partition on the disk and accept the default starting sector. > Grub boot partition with ef02 setting, not to be formatted. > > /boot partition for kernel and init thingy. Usually 1GB or so, enough > for memtest, bootable rescue image etc. > > / or root partition that is around 150GBs or so. Enough to expand a bit > and includes /usr and /var. > > /home rest of disk unless some needed for something else. > > > Do you recall when running grub-install what that command looks like? > Lets say the Grub partition with ef02 setting is sda1, would it be > grub-install /dev/sda1 or just sda and it finds the empty partition on > its own? The unformatted and empty /dev/sda1 'BIOS Boot Partition' will be found by GRUB when you run grub-install and it will store its core.img in there. You install GRUB's boot.img in the MBR and therefore you have to specify the disk, NOT a partition, e.g.: grub-install /dev/sda This command should: 1. Install GRUB's boot.img in the MBR of /dev/sda. 2. Install GRUB's core.img in /dev/sda1 which you created as a 'BIOS boot partition', type EF02. 3. Create directory /boot/grub to install all the grub fs drivers and files. If you have mounted /boot, all is well. If you are repairing an installation from a liveUSB you can mount the /boot partition, e.g. /mnt/gentoo/boot and specify this in the CLI: grub-install --boot-directory=/mnt/gentoo/boot /dev/sda NOTE: As per the link Grant helpfully posted you can create the 'BIOS boot partition' with cgdisk "... by setting the partition type to 0xEF02 and giving it a label of gptbios". https://wiki.gentoo.org/wiki/GRUB#BIOS_with_GPT signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Grub, gpt partitions and BIOS, not uefi thing.
On Sunday, 28 April 2024 13:57:23 BST Dale wrote: > I just got to figure out how to make it so I can login as root via ssh > again. I set PermitRootLogin to yes in ssh config but still refuses. I > did it on my NAS box but can't recall what else I had to do. Just checking the obvious, did you start sshd? Is a port open and listening for ssh connections (use nc, telnet, nmap to find out). Will it let you login as a plain user, then 'su' to run as root? Make sure the plain user is in the wheel group. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] dhcp error. No network. Address family not supported.
On Sunday, 28 April 2024 03:29:09 BST Dale wrote: > Michael wrote: > > On Saturday, 27 April 2024 23:30:46 BST Dale wrote: [snip ...] > >> Anyone ever seen this? Searching didn't help. This is a new kernel so > >> maybe I missed something in there? > > > > Yes, most likely. > > > > What does this show: > > > > grep SOCKET /usr/src/linux/.config > > > > or this: > > > > grep PACKET /usr/src/linux/.config > > OK. Some of those were turned off. I cut on anything that looked like > something I'd need. Recompiled the kernel and rebooted. What do you > know, it worked. Cool :-) > Now some questions, why is something that most anyone would need turned > off by default? Why is it not mentioned along with other things in the > install docs? I went through the install docs for those options needed, > I don't recall seeing those. I don't know what the devs' thinking on this has been, but it could be such options are not enabled by default because the network configuration can affect security. For a binary desktop distro, more generic options would be preconfigured, as I expect is the case with genkernel. > The only things I left out were the UEFI > thingy stuff. I so dread that UEFI thingy on the new build. o_O I think UEFI is rather simpler to set up, no "BIOS Boot Partition" required. Just create a partition with type ef00 (GUID type C12A7328-F81F-11D2- BA4B-00A0C93EC93B - EFI system partition) and format it as FAT32, before you mount it as /efi. The handbook details how to set up a UEFI system with ESP, so spend some time reading through the docs before you jump in and consider options and permutations if you will be using openrc or systemd. > Thanks to all. It running, apparently with IPv6 at that. O_O Consider your firewall settings to include IPv6, if IPv6 is enabled. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Grub, gpt partitions and BIOS, not uefi thing.
On Sunday, 28 April 2024 06:24:09 BST Dale wrote: > Michael wrote: > > On Saturday, 27 April 2024 17:53:25 BST Dale wrote: [snip ...] > >> I did some research but still find myself in some muddy > >> waters. My take on some things I've read, I need a boot partition, not > >> to be confused with the /boot for kernels, init thingys and such. Where > >> I get lost, most use gdisk. I like cgdisk. Before that I liked > >> cfdisk. Anyway, how do I set up that partition with cgdisk? Any > >> minimum size requirements or tiny is enough? > > > > 1MB > > OK. You know that "alignment" thing that is always on the beginning of > a drive, could it use it? I think it is like 2MBs or something. It should be 1MB, sector 2048. For 512 byte sector size you'd get: 2048 x 512 = 1,048,576 bytes This is coded in on modern partitioning tools to ensure alignment of logical and physical sectors by default. This alignment is critical for the performance of so called "Advanced Format" disks with 4096 byte size of physical sectors. Therefore I strongly suggest you let the partitioning tool align its logical partitions where it feels best - at the 1MB boundary and not change it. HOWEVER ... If you are partitioning an old disk on a BIOS MoBo with logical/physical sector sizes both at 512/512 bytes, then you can take matters into your own hands and force it to start your 'BIOS Boot Partition' at sector 34. Sectors 0-33 are used by the MBR and the GPT headers, so leave these alone. Start sector 34 End sector 2047 > >> Does it have to be a > >> specific type? > > > > Yes, it has to be set up as a "BIOS Boot Partition", with the "ef02", or > > GUID 21686148-6449-6E6F-744E-656564454649. > > Light bulb moment. I've seen 8300 and friends, 8200 etc but never seen > EF02 before. Now I see what that type means. That cleared up some > muddy water. That lead me to finding this, it has a nice table of > common codes. > > https://wiki.archlinux.org/title/GPT_fdisk If you select [Type] in cgdisk and then press "L" it will list all the partition types available. I suggest you familiarise yourself with gdisk, which has more options, or as already suggested GParted has an easy GUI to navigate through. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] dhcp error. No network. Address family not supported.
On Saturday, 27 April 2024 23:30:46 BST Dale wrote: > Howdy, > > I finally got Gentoo on the old rig I had laying around. This is not > the one I usually refer to as NAS box. I named this one NAS2. LOL I > got one problem that is confusing me. I've compared it to my main rig > and the install guide and I think I got everything right but maybe I > have a typo, missed something or got some other issue. This is what the > screen says, typing by hand so I hope I don't insert a typo. > > > Bringing up interface enp3s0 > dhcp ... > Running dhcpcd ... > dhcpcd-10.0.6 starting > main: if_opensockets: address family not supported by protocol > dhcpcd exited. > > > At first I thought that 10.0.6 was a typo on my part in some config > file. The usual IP address for that port is 10.0.0.6. Eventually I > figured out it was the version of dhcp. So, after getting past that, I > started checking everything network related in the install guide. > Basically, set it to use dhcp and let er rip. Well, this is the first > time dhcp has gave me any grief, which is why I think I did something > wrong. > > Anyone ever seen this? Searching didn't help. This is a new kernel so > maybe I missed something in there? Yes, most likely. What does this show: grep SOCKET /usr/src/linux/.config or this: grep PACKET /usr/src/linux/.config signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Grub, gpt partitions and BIOS, not uefi thing.
On Saturday, 27 April 2024 17:53:25 BST Dale wrote: > Howdy, > > I'm installing Gentoo on another old box. To be consistent I like to > use cgdisk, GPT I think it is called, to partition all my drives, > regardless of size. GPT is the partition table structure, which is more advanced than the old DOS partition table structure. > Thing is, Grub works differently with GPT than it > does with the old DOS or whatever it is called, like fdisk does in the > old days. GRUB works the same, but the disk/partition table structure is different. > I did some research but still find myself in some muddy > waters. My take on some things I've read, I need a boot partition, not > to be confused with the /boot for kernels, init thingys and such. Where > I get lost, most use gdisk. I like cgdisk. Before that I liked > cfdisk. Anyway, how do I set up that partition with cgdisk? Any > minimum size requirements or tiny is enough? 1MB > Does it have to be a > specific type? Yes, it has to be set up as a "BIOS Boot Partition", with the "ef02", or GUID 21686148-6449-6E6F-744E-656564454649. > Does it need to be in a specific place? Not necessarily, but since you're not booting this disk on a UEFI MoBo and consequently won't be using an EFI System Partition (ESP), the very first partition is fine and will be out of the way of the remaining disk. > Formatted with a file system? Do not format it. The raw 1MB partition will be used by GRUB to install its core.img file. > Also, when I do grub-install, do I still point to > /dev/sda or to /dev/sda1, if sda1 is the special boot partition? Sector 0 of your disk /dev/sda is where GRUB will drop its boot loader image 'boot.img'. This is the Master Boot Record region. Normally, with a DOS partition table, GRUB's core.img would be dropped in the empty space of sector 1, following sector 0. However, in the GPT structure sector 1 is where the GPT partition array data is stored. You don't want GRUB making a mess by dropping it's core.img on top of it! So, from what I recall you'd install GRUB like so: grub-install --boot-directory=/mnt/gentoo/boot --force /dev/sda If this won't do it, I'll have to boot an old system of mine to check the disk layout in more detail. > I tried to find a step by step howto with this info but the ones I find > either don't work or leaves me more confused. Given that the method is > also aging out, it's hard to find good guides. I'd be real happy just > to have a link to a good howto that I can make sense of. I can save a > copy local and even print it. Maybe someone has some notes that will > help. I just need something to help clear up the muddy waters. > > Thanks to anyone who has a link, some notes or something. :-D > > Dale > > :-) :-) signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Hibernation without initramfs
On Friday, 26 April 2024 10:23:28 BST Wojciech Kuzyszyn wrote: > On Fri, 26 Apr 2024 09:40:54 +0100 > > Michael wrote: > > [*] Hibernation (aka 'suspend to disk') > > [*] Userspace snapshot device > > (/dev/sdb6)Default resume partition > > My swap partition is /dev/nvme0n1p2 - this would work I assume, right? Yes, it is a block device accessed via the PCIe bus. > > However, if you are using RAM heavily when you try to hibernate, e.g. > > because you are compiling some large package, have many memory hungry > > applications open, etc., you may find hibernation fails due to lack > > of space. This would be more acute if your RAM is not large enough > > and swap is used on a regular basis. With large enough RAM less swap > > space will be used, since swap would be virtually empty. Therefore > > size your swap device accordingly. > > I have oldschool swap - 2x RAM. OK, with this much space you'd have at least 2x more hibernation storage space than you will need. :-) signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Hibernation without initramfs
On Thursday, 25 April 2024 22:29:01 BST Wojciech Kuzyszyn wrote: > Hello! > > Quick question: is it possible to use hibernation (suspend to disk) > with no initramfs? Yes. > I don't have one and don't want to have one. So I'd > rather disable hibernate in kernel (so I won't do this by accident) or > leave it to use it happily when needed. You have to specify a swap block device - a swap partition, or a preconfigured swap file on an already mounted partition - in your kernel configuration, for hibernation to work, e.g.: [*] Hibernation (aka 'suspend to disk') [*] Userspace snapshot device (/dev/sdb6)Default resume partition This swap device will be used at hibernation time to compress and store what is running in your RAM. Since the contents of your RAM will be compressed less space will be required than the size of your RAM. However, if you are using RAM heavily when you try to hibernate, e.g. because you are compiling some large package, have many memory hungry applications open, etc., you may find hibernation fails due to lack of space. This would be more acute if your RAM is not large enough and swap is used on a regular basis. With large enough RAM less swap space will be used, since swap would be virtually empty. Therefore size your swap device accordingly. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Handbook and question about manual network setup
On Sunday, 21 April 2024 20:36:56 BST J. Roeleveld wrote: > On Friday, 19 April 2024 16:05:47 CEST Dale wrote: > > Howdy, > > > > I'm playing around with my NAS box again. I ran into a network issue. > > I sorta forgot I unplugged the network cable so obviously, it made it > > difficult to ssh into the thing from my main rig. After hooking up a > > monitor and keyboard, I found the problem and plugged the network cable > > back in. ROFLMBO Told y'all I forget stuff. > > > > Anyway, while investigating this, I realized the network setup is not > > like on my old rig. Heck, I couldn't even figure out how to restart it > > other than switching to the boot runlevel and back to default, or > > rebooting. After a bit, I think I can restart DHCP and it restart the > > network. I figured out the cable was unplugged before trying that. I'm > > wanting to set up the NAS box network the same way as my main rig. > > That's the old manual way. I went back to the install handbook, that's > > what I followed when installing on my main rig. Thing is, it has been > > updated and the old way isn't all there. I followed what little bit is > > there but it defaults back to the new way. I'm sure I'm missing some > > file I need to edit but I can't figure out which one it is. So, is > > there a way to get the old instructions again? The ones I followed > > several years ago for my main rig? I tried searching but it seems they > > all gone. Maybe there is a place I'm not aware of tho. Basically, I > > want to be able to start/stop/restart enp3s0 as a service and have it in > > a runlevel. > > > > Also, I'd like to get the install handbook as one large page. My > > intention is to save it locally for future reference as it is now. I > > may even print a copy. I looked at all the places that have different > > options but can't find the whole thing as one large page. I looked > > under several drop down menus and such. A long time ago, it was a > > option. I just can't find it now. May that option isn't available > > anymore. I wish I had a copy of the one from several years ago. Back > > when I installed on my main rig. > > > > Some network info. Lines that are commented out are options I tried but > > didn't work. It was worth a shot. o_O > > > > > > nas / # grep -r '!net' /etc/ > > /etc/rc.conf:rc_hotplug="!net.*" > > nas / # grep -r 'enp3s0' /etc/ > > /etc/resolv.conf:# Generated by dhcpcd from enp3s0.dhcp > > /etc/conf.d/net:config_enp3s0="dhcp" > > /etc/conf.d/net:dns_servers_enp3s0="8.8.8.8 8.8.4.4" > > /etc/conf.d/net:#config_enp3s0="10.0.0.5" > > nas / #nas / # ifconfig -s enp3s0 > > Iface MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP > > TX-OVR Flg > > enp3s0 150016802 0 0 0 17196 0 > > 0 0 BMRU > > nas / # > > > > > > Thoughts? If I had the old install info, I think I could get it to > > work. I did last time. ;-) > > Yes, try: > config_enp3s0="10.0.0.5/24" > routes_enp3s0="default gw " > > Changes to what I see: > 1) You forgot the netmask ( /24 ) for the network > 2) I don't see a default route > > -- > Joost That'll certainly work to specify a static IP address on the PC, but I understood Dale wanted to use DHCP to obtain an IP dynamically from the router and only use netifrc to set up DNS resolvers. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Handbook and question about manual network setup
Hi Dale, On Sunday, 21 April 2024 03:32:32 BST Dale wrote: > OK. I did my weekend OS updates on my main rig, fireball. That > involves me switching to boot runlevel and back again. When the network > started, no message about going to default. It just showed it starting > up and using DHCP. Looks like this: > > > * Bringing up interface enp3s0 > * dhcp ... > * Running dhcpcd ... > > > > I thought of something. My NAS box is shutdown right now so can't > check. I bet DHCP is set to start in the default runlevel. On my main > rig it is not set to start the DHCP service at all. I suspect the NAS > box finds the DHCP service first and starts the network and then finds > the network service but it is already started. When it starts the > network with the DHCP service, it does the default thing. I'll test > that next time I boot up the NAS box. On one box here I have neither netifrc configured, nor dhcpcd, although both are installed. I have also made sure networkmanager is not installed. However, netmount is in the default runlevel and netmount has the default net dependency enabled: $ grep -v "^#" /etc/conf.d/netmount rc_need="net" $ rc-update show -v | grep -i net local | default nonetwork net-online | net.lo | netmount | default I believe this is what kicks in on my system first and brings up dhcpcd, which in turn obtains an IP address from my router. I mostly configure static IP addresses for known devices in my LAN on the router. You can compare which network services are configured to come up on your NAS Vs your main PC and also check any differences in /etc/rc.conf. Finally search for "rc_need=" dependencies defined in your /etc/conf.d/*. https://wiki.gentoo.org/wiki/OpenRC#Dependency_behavior > I guess no one else found a way to get the install handbook on a single > page. I'll have to copy and paste I guess. That's gonna take a while. > O_O > > Dale > > :-) :-) To save you copying: https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation but note the warning about links redirecting to individual pages: https://wiki.gentoo.org/wiki/Handbook:AMD64/Full signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Handbook and question about manual network setup
On Friday, 19 April 2024 18:04:57 BST Dale wrote: > I'm missing something. I don't think you are. Shutdown your main rig. Pull the ethernet cable. Reboot. If the main rig's config is the same as the old rig, AND the router addressing is analogous on both PCs, THEN their behaviour and messages ought to be the same. > > Dale > > :-) :-) > > P. S. Back to mowing grass. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Handbook and question about manual network setup
On Friday, 19 April 2024 17:20:44 BST Dale wrote: > Matt Connell wrote: > > On Fri, 2024-04-19 at 09:05 -0500, Dale wrote: > >> Basically, I want to be able to start/stop/restart enp3s0 as a > >> service and have it in a runlevel. > > > > You should just need to create a symlink at /etc/init.d/net.enp3s0 that > > points to /etc/init.d/net.lo and then you can do the usual rc-service > > stuff with it. > > I did that and went from default to boot runlevel and back to default > again but I still couldn't restart with the net.enp3s0 file. Luckily, I > shut the rig down a bit ago. I went to mow some grass. Using push > mower since battery went bad on riding mower. Anyway, when I booted it > back up just now, it worked. I can start/stop/restart with the enp3s0 > file like on my main rig. It still says it is defaulting to DHCP which > makes me think I'm still missing something. It says, I'm typing this in > manually. > > > Bringing up interface enp3s0 > config_enp3s0 not specified; defaulting to DHCP > > > Then it continues bringing up the network. I have this set: > > nas / # cat /etc/conf.d/net > config_enp3s0="dhcp" > dns_servers_enp3s0="8.8.8.8 8.8.4.4" > nas / # > > > Since I have it set to use DHCP already, why is it saying it is > defaulting to it? Did I miss a file or something? Shouldn't it just > use it without saying it is defaulting to it? I don't recall seeing > this on my main rig. > > Dale > > :-) :-) Normally you would use netifrc to configure a gateway and static IP address. DHCP is a fallback, in case the static IP subnet has changed - e.g. because you changed your home router. If you *are* using dhcpcd to obtain an IP address from the router then arguably your don't need netifrc at all, as I explained in my other message earlier. Regarding the messages you see on your main rig Vs the old rig, you can compare the two PC's conf.net files for any differences. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Handbook and question about manual network setup
On Friday, 19 April 2024 17:26:43 BST Dale wrote: > Michael wrote: > > On Friday, 19 April 2024 15:05:47 BST Dale wrote: > >> Anyway, while investigating this, I realized the network setup is not > >> like on my old rig. Heck, I couldn't even figure out how to restart it > >> other than switching to the boot runlevel and back to default, or > >> rebooting. After a bit, I think I can restart DHCP and it restart the > >> network. I figured out the cable was unplugged before trying that. I'm > >> wanting to set up the NAS box network the same way as my main rig. > >> That's the old manual way. I went back to the install handbook, that's > >> what I followed when installing on my main rig. Thing is, it has been > >> updated and the old way isn't all there. I followed what little bit is > >> there but it defaults back to the new way. I'm sure I'm missing some > >> file I need to edit but I can't figure out which one it is. So, is > >> there a way to get the old instructions again? The ones I followed > >> several years ago for my main rig? I tried searching but it seems they > >> all gone. Maybe there is a place I'm not aware of tho. Basically, I > >> want to be able to start/stop/restart enp3s0 as a service and have it in > >> a runlevel. > > > > Without knowing what you refer to as 'The Old Way' Vs 'The New Way', or > > how > > your 'main rig', Vs your 'old rig' may have been configured, I'll try to > > make a guess, or two: > > > > 1. Old Way = netifrc > > > > You configure /etc/conf.d/net using the well commented example provided > > in: > > > > /usr/share/doc/netifrc-*/net.example.bz2 > > > > You symlink your interface enp3s0 to the net.lo netifrc init script and > > add it to the default runlevel: > > > > ln -s /etc/init.d/net.lo /etc/init.d/net.enp3s0 > > rc-update add net.enp3s0 default > > > > then (re)start, check the status, or stop your newly configured interface, > > e.g.: > > > > rc-service -v net.enp3s0 status > > rc-service -v net.enp3s0 restart > > > > More detailed info than you should ever need and all on one page, is > > provided here: > > > > https://wiki.gentoo.org/wiki/Netifrc > > > > > > 2. New Way = DHCP (?) > > > > Although dhcp can be configured as a fallback option within > > /etc/conf.d/net in addition to static addresses, gateways, etc., it can > > also be set up as a standalone service without netifrc. Emerge dhcpcd > > and add it to the default runlevel. > > > > If you have set static IP address(es) at your home router for the old box > > and its MAC address, then that's all you need to do before you run: > > > > rc-service -v dhcpcd restart > > > > If you prefer to not set up a configuration for your old rig on the > > router, > > then you can add a static IP address in your /etc/dhcpcd.conf. > > > > Again, more info than you should need is provided here: > > > > https://wiki.gentoo.org/wiki/Dhcpcd > > > > HTH, otherwise ask if you get stuck. > > Rebooting the NAS box improved things. See reply to Matt. By old way, > I mean using a symlink to net.lo with the interface/card name such as > enp3s0 to start/stop/restart the service. It still uses DHCP to get > connection info but I'd also like to specify the IP address if I can. I > like to set those so that they don't change even if I move cables > around. Main rig, NAS box, cell phone and printer. The printer really > gets upset when something changes. > > I think I should have used the word "older" instead of "old". ROFL :-D > > Dale > > :-) :-) OKey, dOKey, you can: Configure static IP addresses for all your LAN devices on your home router. Then set your devices to use DHCP to obtain an address from the router when they come up. With a large number of devices which often change (e.g. guests in a hotel) this is inadvisable, but with a home LAN with a handful of devices this is not too much of a chore. Alternatively, you can configure each of your devices with static IP addresses. The URLs I sent you explain how to do this. For a couple of PCs this should take less than 5 minutes, inc. restarting the NIC service, or a reboot to make sure all works as intended on statup. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Handbook and question about manual network setup
On Friday, 19 April 2024 15:05:47 BST Dale wrote: > Anyway, while investigating this, I realized the network setup is not > like on my old rig. Heck, I couldn't even figure out how to restart it > other than switching to the boot runlevel and back to default, or > rebooting. After a bit, I think I can restart DHCP and it restart the > network. I figured out the cable was unplugged before trying that. I'm > wanting to set up the NAS box network the same way as my main rig. > That's the old manual way. I went back to the install handbook, that's > what I followed when installing on my main rig. Thing is, it has been > updated and the old way isn't all there. I followed what little bit is > there but it defaults back to the new way. I'm sure I'm missing some > file I need to edit but I can't figure out which one it is. So, is > there a way to get the old instructions again? The ones I followed > several years ago for my main rig? I tried searching but it seems they > all gone. Maybe there is a place I'm not aware of tho. Basically, I > want to be able to start/stop/restart enp3s0 as a service and have it in > a runlevel. Without knowing what you refer to as 'The Old Way' Vs 'The New Way', or how your 'main rig', Vs your 'old rig' may have been configured, I'll try to make a guess, or two: 1. Old Way = netifrc You configure /etc/conf.d/net using the well commented example provided in: /usr/share/doc/netifrc-*/net.example.bz2 You symlink your interface enp3s0 to the net.lo netifrc init script and add it to the default runlevel: ln -s /etc/init.d/net.lo /etc/init.d/net.enp3s0 rc-update add net.enp3s0 default then (re)start, check the status, or stop your newly configured interface, e.g.: rc-service -v net.enp3s0 status rc-service -v net.enp3s0 restart More detailed info than you should ever need and all on one page, is provided here: https://wiki.gentoo.org/wiki/Netifrc 2. New Way = DHCP (?) Although dhcp can be configured as a fallback option within /etc/conf.d/net in addition to static addresses, gateways, etc., it can also be set up as a standalone service without netifrc. Emerge dhcpcd and add it to the default runlevel. If you have set static IP address(es) at your home router for the old box and its MAC address, then that's all you need to do before you run: rc-service -v dhcpcd restart If you prefer to not set up a configuration for your old rig on the router, then you can add a static IP address in your /etc/dhcpcd.conf. Again, more info than you should need is provided here: https://wiki.gentoo.org/wiki/Dhcpcd HTH, otherwise ask if you get stuck. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] NAS box and switching from Phenom II X6 1090T to FX-6300
On Wednesday, 17 April 2024 23:13:40 BST Dale wrote: > Frank Steinmetzger wrote: > > Am Wed, Apr 17, 2024 at 01:18:39PM -0400 schrieb Rich Freeman: > >> On Wed, Apr 17, 2024 at 9:33 AM Dale wrote: > >>> Rich Freeman wrote: > All AM5 CPUs have GPUs, but in general motherboards with video outputs > do not require the CPU to have a GPU built in. The ports just don't > do anything if this is lacking, and you would need a dedicated GPU. [snip ...] > >> If you don't play games, then definitely get integrated graphics. I'd add to this, you could still play many games, especially older games using a modern APU. The integrated graphics capability is broadly comparable with the entry level discrete GPUs. For driving a couple of monitors and watching videos an APU is more than adequate, saves money on a graphics card and consumes less power. > >> Even if the CPU costs a tiny bit more, it will give you a free empty > >> 16x PCIe slot at whatever speed the CPU supports (v5 in this case - > >> which is as good as you can get right now). > > > > Not to mention a cut in power draw. > > > >>> I might add, simply right clicking on the desktop can take sometimes 20 > >>> or 30 seconds for the menu to pop up. Switching from one desktop to > >>> another can take several seconds, sometimes 8 or 10. This rig is > >>> getting slower. > > > > Wut. I am running plasma 6 on a Surface Go 1 whose Pentium Gold was slow > > even when it came out. It is half as fast as your 8350 and does not have > > such problems. > > Benchmark FX 8350: https://www.cpubenchmark.net/cpu.php?id=1780 > > Benchmark Pentium Gold: https://www.cpubenchmark.net/cpu.php?id=3300 > > > > You have NVidia, right? Did you try the other graphics driver (i.e. > > proprietary ←→ foss)? Do those delays disappear if you disable 3D effects > > with Shift+Alt+F12? > > I do have Nvidia and I use the Nvidia drivers. Thought about using the > ones in the kernel but just never did. I don't think it is the video > card tho. I think some of it is all the hard drives I have installed > and that they are busy. I run torrent software all the time. It stays > very busy. I actually set the connection speed to a little lower so > that I have some network speed that isn't being used so that when I do > something, I get some network bandwidth. Plus, there's that growing > software problem that always exists. Software rarely shrinks. > > >> That sounds like RAM but I couldn't say for sure. In any case a > >> modern system will definitely help. +1 In particular it sounds like I/O becomes saturated as swap ramps up. Also, fstrim, updatedb, rkhunter, etc., running in the background can make things worse. > > Well, is the RAM full? My 10 years old PC has 32 Gigs and still runs very > > smooth (with Intel integrated graphics). > > Generally, I use about 20 to 25GBs of RAM. Mostly, Seamonkey, Firefox > and the torrent software. An 8-core/thread CPU can eat up to 16G of RAM with -j8 and proportionately more if a higher job number has been configured. Torrent can eat up *a lot* of memory, depending how its caching has been set up. Endless tabs on browsers will also eat up RAM, and/or place demand on swap. Some addons can make things worse, as can a corrupt content-prefs.sqlite file - see here: https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-or-cpu-resources > Either way, the age of my current rig is a big reason I want to build a > new one. It's getting a lot of gray hairs. > > Dale > > :-) :-) IMHO the good ol' FX-8350 with a boost of 4.2 GHz and dual channel memory access is still a very respectable CPU for day to day desktop computing. Sure, it is inefficient energy wise and it can't compete with high multicore/ multithreaded CPUs and DDR4/5 RAM modern architectures, if non-stop 24-7 parallel compiling were a user requirement, but for its age and architecture I would categorise it as a competent package. Most importantly, it comes already assembled and with zero additional cost! ;-) There were/are a lot corporates throwing out workstations and server spec towers, since many employees switched to working from home. It may be worth taking a look at those, if what you are missing at present is a faster/bigger NAS box. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Slightly corrupted file systems when resuming from hibernation
On Wednesday, 17 April 2024 11:37:04 BST Dr Rainer Woitok wrote:
> Grant,
>
> On Tuesday, 2024-04-16 19:26:25 -, you wrote:
> > ...
> > That means that all gentoo-sources stable kernels are "longterm"
> > kernel versions on kernel.org. It does not mean that all "longterm"
> > kernel versions from kernel.org are available as "stable" in
> > gentoo-sources.
> >
> > It is a statement that "gentoo-sources stable" is a subset of
> > "kernel.org longterm".
>
> This sort of deteriorates into a debate about words rather than meanings
> without explaining HOW LONG such a series of related kernels are main-
> tained and provided. After all, "longterm" or "LTS" suggest that these
> lines of developement are less short-lived than others. To give an ex-
> ample: the oldest "longterm" kernels listed on "kernel.org" are 4.19.*,
> 5.4.* and 5.10.*. Of these only 5.10.* is still available from Gentoo.
>
> Digging through my Gentoo installation logs, I can see that 4.19.72 was
> one of the first kernels I built myself. This was somewhen in the mid-
> dle of 2019, that is, not yet five years back. And this kernel line has
> already vanished from Gentoo. So what time span are we talking about
> when we say "LTS Gentoo kernel"? Roughly four, three or two years? And
> why is the support provided by Gentoo significantly shorter than that by
> "kernel.org"?
>
> Sincerely,
> Rainer
LTS kernels were being supported for ~6 years, although the projected EOL I
see here indicates later LTS releases may not be supported for as long:
https://www.kernel.org/category/releases.html
The stable gentoo-sources are tree cleaned more frequently, so the oldest
stable release for amd64 in portage is now 5.10.212:
$ eix gentoo-sources
[I] sys-kernel/gentoo-sources
Available versions:
(5.10.208) *5.10.208^bs
(5.10.212) 5.10.212^bs
(5.10.213) ~5.10.213^bs
(5.10.214) ~5.10.214^bs
(5.10.215) ~5.10.215^bs
(5.15.147) *5.15.147^bs
(5.15.151) 5.15.151^bs
(5.15.152) ~5.15.152^bs
(5.15.153) ~5.15.153^bs
(5.15.154) ~5.15.154^bs
(5.15.155) ~5.15.155^bs
(6.1.74) *6.1.74^bs
(6.1.81) 6.1.81^bs
(6.1.83) ~6.1.83^bs
(6.1.84) ~6.1.84^bs
(6.1.85) ~6.1.85^bs
(6.1.86) ~6.1.86^bs
(6.6.13) *6.6.13^bs
(6.6.21) 6.6.21^bs
(6.6.24) ~6.6.24^bs
(6.6.25) ~6.6.25^bs
(6.6.26) ~6.6.26^bs
(6.6.26-r1) ~6.6.26-r1^bs
(6.6.27) ~6.6.27^bs
(6.8.3) ~6.8.3^bs
(6.8.4) ~6.8.4^bs
(6.8.5) ~6.8.5^bs
(6.8.5-r1) ~6.8.5-r1^bs
(6.8.6) ~6.8.6^bs
{build experimental symlink}
Installed versions: 6.6.21(6.6.21)^bs(03:21:20 24/03/24)(-build -
experimental -symlink)
Homepage:https://dev.gentoo.org/~mpagano/genpatches
Description: Full sources including the Gentoo patchset for the
6.8 kernel tree
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Slightly corrupted file systems when resuming from hibernation
On Tuesday, 16 April 2024 20:26:25 BST Grant Edwards wrote: > On 2024-04-16, Dr Rainer Woitok wrote: > > Arve, > > > > On Tuesday, 2024-04-16 15:53:48 +0200, you wrote: > >> ... > >> Only LTS kernels get stabilised, so this information is readily > >> available. > > > > I'm sure I don't understand this: According to "https://www.kernel.org/; > > kernel 6.6.27 is "longterm", but according to "eix" the most recent > > 6.6.* kernels are 6.6.22 and 6.6.23 which both are non-stable (well, I > > ran my last "sync" immediately before the profile upgrade, so this might > > not be current). I'm still using stable kernel 6.6.13 as my backup ker- > > nel, but this kernel is no longer provided by Gentoo. So, what precise- > > ly does LTS or "longterm" mean? LTS stands for Long Term Support and it means the kernel maintainers will continue to backport bug fixes and security patches into the LTS kernels from the Mainline tree, as they progress in their development of the kernel code. When they do this backporting they bump the LTS kernel version, e.g. from 6.6.24 to 6.6.25. They will not go into this prolonged maintenance effort with the kernel's 'Stable' tree, which has a higher churn as it acquires the Mainline kernels as soon as the latter are signed for release. > That means that all gentoo-sources stable kernels are "longterm" > kernel versions on kernel.org. It does not mean that all "longterm" > kernel versions from kernel.org are available as "stable" in > gentoo-sources. > > It is a statement that "gentoo-sources stable" is a subset of > "kernel.org longterm". > > It is not a statement that the two sets are identical. > > In other words: > >"ONLY LTS kernels get stabilized." > > is a different statement from > >"ALL LTS kernels get stabilized." > > The former is true. The latter is not. Yes, precisely. This happens because Gentoo acquire the latest LTS kernel, apply various Gentoo related patches, test and eventually mark as stable the corresponding version of the gentoo-sources in portage. This process incurs some inevitable delay compared with the LTS kernel tree releases, but nevertheless the stable gentoo-sources follow the LTS releases. > > But, to get back to the beginning of this discussion: if there is a > > risk that my aging hardware possibly can less and less cope with > > newer and newer kernels, should I put something like > > > >>=sys-kernel/gentoo-sources-6.7.0 > > > > into file "package.mask" to stay with "longterm" 6.6.* kernels? > > Yes: if you want to avoid getting upgraded to 6.8 when it gets > kernel.org "longterm" status and gentoo-sources "stable" status, then > a statement like that in in package.mask will keep you on > gentoo-sources 6.6 kernels (which are "longterm" on kernel.org). > > Again: not all longterm 6.6.x kernel versions get marked as "stable" > for gentoo-sources. If you have not enabled the testing keyword for > gentoo-sources, then you'll only get the 6.6.x kernel versions that > the gentoo-sources maintainers have declared as "stable". > > -- > Grant I am not sure the assumption "... aging hardware possibly can less and less cope with newer and newer kernels" is correct. As already mentioned newer kernels have both security and bug fixes. As long as you stick with stable gentoo-sources you'll have these in your system. Later kernels also come with additional kernel drivers for new(er) hardware. You may not need/want these drivers if you do not run the latest hardware. Using 'make oldconfig' allows you to exclude such new drivers, but include new security options and/or functionality as desired. It can happen for new code to introduce some software regression. However, this is not limited to old hardware. If there is no workaround, or some patch you can apply manually to your kernel from a later release, then by all means you can mask later minor LTS releases *for a little while only* and keep an eye open for the latest releases which could have addressed the bug you suffered from. PS. Regarding your earlier question about different make *config commands and their meaning you can check the latest make help page: $ cd /usr/src/linux $ make help Then take a look at the section "Configuration targets". signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Slightly corrupted file systems when resuming from hibernation
On Tuesday, 16 April 2024 11:55:20 BST Dale wrote: > If you update often, it shouldn't take long answer the questions. If > you do like me and don't update often, it may take longer but no more > time than it would if you updated often and added all the time > together. As far as I know, if one manually updates their kernel, make > oldconfig is the safest and recommended method. You are prompted for > new drivers/options and can see if they apply to you or not. If you > don't want to update that way, I think there is a kernel that does it's > own thing. I think it is sort of like boot media uses. If the time > needed to answer all the questions isn't there, that may be a option to > look into. It's called genkernel. I've never used it but read it works. The sys-kernel/genkernel package will automatically build & install your kernel and initramfs in /boot, but it will NOT prepare a kernel configuration tuned to your hardware and desired options. It uses a generic default configuration safe for most circumstances. The user can tweak the default configuration to suit their needs and genkernel will use that. For quick(er) and automated kernel update and installation there are the gentoo *distribution kernels*: https://wiki.gentoo.org/wiki/Project:Distribution_Kernel > In short, make oldconfig is the recommended way as far as I know. In my > opinion, it is the safest way to know what you are going to get. Links > for more info. > > https://wiki.gentoo.org/wiki/Kernel/Upgrade > > https://wiki.gentoo.org/wiki/Kernel/Configuration > > Someone else may have a different opinion, even a better one. This is > how I always do it and kernel failure is rare. Hope it helps. > > Dale > > :-) :-) signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Slightly corrupted file systems when resuming from hibernation
On Tuesday, 16 April 2024 10:04:43 BST Dr Rainer Woitok wrote: > Michael, > > On Monday, 2024-04-15 12:48:34 +0100, you wrote: > > ... > > Why have you set your /boot to be mounted at boot? > > Well, I think, I then just followed the Gentoo Handbook. But I see your > point of saving time which could be better used to successfully unmount > the "/home/" partition. I'll change my "/etc/fstab" file as well as a > few of my scripts. Thanks for pointing that out :-) > > > ... > > > > MoBo firmware can be notoriously buggy and is > > > > typically frozen/abandoned within a couple of years by the OEMs. In > > addition, kernel code changes and any previous symbiosis with the > > firmware can fall apart with a later kernel release. > > Hm, this sounds a bit like "never change your running kernel", doesn't > it? Not really, because a newer kernel has any security patches, plus it can include bug fixes. You won't know if a later release fixes or breaks something on your system until you tried it. > But this brings up two related questions: > > 1. Why does Gentoo not somehow mark LTS kernels either in the version >number or in the slot name? This would make it easier to prevent the >installation of too modern kernels. My understanding is the gentoo-sources kernels are aligned with the LTS upstream releases. > 2. I'm building new kernels with "make olddefconfig" rather than "make >oldconfig" because I thought providing default values to new configu- >ration variables is a good idea. It is a good idea if the new config items are something you need/want on your system and in addition if the default setting suits your needs. >But what precisely does "make old- >config" do with new configuration variables instead? Just leaving >them out? But what's the difference between not defining a configu- >ration variable and setting it to a default value? Or is "make old- >config" really the way to generate more conservative kernels which do >not as quickly overburden aging motherboards? The make oldconfig script will identify new config items not present in your old kernel config, show which is the default option and ask you to interactively select which one you prefer; e.g. SPECULATION_MITIGATIONS [Y/n/m/?] (NEW) The default option above has been identified as Y, if the devs have determined this is a safe default for the arch. You can hit Enter to select Y, or type 'n' for no, 'm' for module, or '?' to read the extended description and help for this option before you make up your mind. With make olddefconfig the option 'Y' will be automatically selected without asking your input. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Slightly corrupted file systems when resuming from hibernation
On Sunday, 14 April 2024 19:41:41 BST Dr Rainer Woitok wrote:
> Greetings,
>
> On Friday, 2024-01-05 18:46:09 +0100, I myself wrote:
> > ...
> > since a few month or so off and on my laptop fails to resume from hiber-
> > nation due to the "dirty bit" being set on the ext4 "/home" partition.
>
> I was reading this flickering by on the screen, and it wasn't quite cor-
> rect. Meanwhile I found this in my "openrc.log":
>
>fsck.fat 4.2 (2021-01-31)
>There are differences between boot sector and its backup.
>This is mostly harmless. Differences: (offset:original/backup)
> 65:01/00
> Not automatically fixing this.
>Dirty bit is set. Fs was not properly unmounted and some data may be
> corrupt. Automatically removing dirty bit.
>*** Filesystem was changed ***
>Writing changes.
>/dev/sda1: 368 files, 116600/258078 clusters
Why have you set your /boot to be mounted at boot?
You can run 'fsck.fat -v /dev/sda1' after you unmount it to remove the dirty
bit (if not already removed) and then change your fstab to 'noauto'. Just
remember to remount /boot before you make any changes to your boot manager/
kernels.
>/dev/sdb1: recovering journal
>/dev/sdb1: Clearing orphaned inode 54789026 (uid=1000, gid=1000,
> mode=0100600, size=32768) /dev/sdb1: Clearing orphaned inode 54788311
> (uid=1000, gid=1000, mode=0100600, size=553900) /dev/sdb1: clean,
> 172662/61054976 files, 36598898/244190385 blocks * Filesystems repaired
>
> So one cause always is some problem on disk "/dev/sda1/" ("/boot/") and
> another cause are one or more orphaned inodes on disk "/dev/sdb1/"
> ("/home/"). But while the values of offset, original and backup for
> "/dev/sda1/" are always the same when this happens, the number of or-
> phaned inodes on "/dev/sdb1/" and the inodes itself change from occur-
> rence to occurrence. Besides it only happens sporadically when resuming
> from hibernation, not every time. More precisely, the problem surfaces
> when resuming from hibernation but could as well be caused during the
> hibernation process itself.
>
> Does this ring some bell somewhere what could cause this?
>
> Sincerely,
> Rainer
Unlike the /boot partition, the /home partition has data written to it
regularly. The ext4 fs does not perform atomic writes - it is not a CoW fs.
Therefore a sudden unsync'ed shutdown could leave it in a state of corruption
- IF for some reason data in memory is not either fully written to disk or
retained in memory. The way ACPI interacts with firmware *should* ensure the
S3 system state does not suspend I/O operations halfway through an inline
write operation ... but ... MoBo firmware can be notoriously buggy and is
typically frozen/abandoned within a couple of years by the OEMs. In addition,
kernel code changes and any previous symbiosis with the firmware can fall
apart with a later kernel release.
On one PC of mine, with the same MoBo/CPU and the same version firmware, I
have over the years experienced a whole repertoire of random problems resuming
from suspend. At this point in time I avoid placing this PC in sleep, because
it always crashes with a Firefox related segfault, some time after waking up.
Check if the situation with /dev/sdb1 improves when you leave your /boot
unmounted. This may make more process time available for the system to finish
I/O operations, which may then allow /dev/sdb1 to suspend cleanly.
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] How to find out all openrc dependencies?
On Sunday, 14 April 2024 08:28:07 BST J. Roeleveld wrote: > On Thursday, 11 April 2024 12:10:31 CEST Michael wrote: > > On Thursday, 11 April 2024 10:48:15 BST J. Roeleveld wrote: > > > On Thursday, 11 April 2024 11:35:10 CEST Michael wrote: > > > > On Thursday, 11 April 2024 06:19:57 BST J. Roeleveld wrote: > > > > > Hi all, > > > > > > > > > > For a while I've been seeing the following ERROR-messages when > > > > > booting > > > > > 1 > > > > > of > > > > > my systems: > > > > > > > > > > * ERROR: cannot start multipathd as localmount would not start > > > > > > > > > > * ERROR: cannot start zfs-import as localmount would not start > > > > > > > > > > This isn't a big concern as these services will start correctly > > > > > later: > > > > > > > > > > INIT: Entering runlevel: 3 > > > > > > > > > > * Starting multipathd ... > > > > > [ ok ] > > > > > * Importing ZFS pool(s) ... > > > > > [ ok ] > > > > > > > > > > But I am trying to find the cause of these errors as they are > > > > > preventing > > > > > parallel-start from actually working correctly. > > > > > > > > > > When I check with "rc-depend", I don't see an obious cause: > > > > > > > > > > # /lib/rc/bin/rc-depend multipathd > > > > > sysfs devfs udev udev-trigger modules fsck root localmount > > > > > multipathd > > > > > > > > > > # /lib/rc/bin/rc-depend localmount > > > > > sysfs devfs udev udev-trigger modules fsck root localmount > > > > > > > > > > # /lib/rc/bin/rc-depend zfs-import > > > > > multipath sysfs devfs udev udev-trigger modules fsck root localmount > > > > > multipathd zfs-import > > > > > > > > > > # /lib/rc/bin/rc-depend multipath > > > > > multipath > > > > > > > > > > From how I read these, it should be able to start "localmount" > > > > > properly > > > > > before even trying to start "multipathd" and "zfs-import" > > > > > There is also no technical dependency for "localmount" (the root > > > > > filesystem > > > > > is not on ZFS on this system) > > > > > > > > > > Any help/suggestions on how to find the cause would be appreciated. > > > > > > > > > > -- > > > > > Joost > > > > > > > > Check if hwclock is in the boot runlevel: > > > > > > > > rc-update -s -v | grep hwclock > > > > > > What does "hwclock" got to do with this? > > > It has no dependency with multipathd, zfs-import, localmount or anything > > > else that is showing an error. > > > > > > -- > > > Joost > > > > Our systems are certainly different, but I noticed this dependency on my > > localmount which is missing on yours: > > > > # /lib/rc/bin/rc-depend localmount > > sysfs devfs udev udev-trigger hwclock modules fsck root dmcrypt localmount > > > > ^^^ > > > > Have you compared your system services which has this problem, with other > > systems of yours which can startup properly? > > Adding additional dependencies into the tree is more likely to cause further > issues. I am actually looking for how to quickly find out which dependency > is causing a circular dependency issue as the first time it thinks it needs > to start a service it fails. But the 2nd time it starts, it goes correctly. > > I removed hwclock from ALL VMs as they don't actually have a hwclock. > > I did find out the actual cause of the problem through a lot of trial and > error, Out of curiosity - what was the cause of this? I have only come across hwclock on my installations (not VMs). > but this is not really useful in actually quickly finding the > problem. Being able to "simulate" the startup sequence for how OpenRC wants > to do things would have simplified and sped up the entire process. > > -- > Joost I enable the rc log and check how the various services try to start up, however the information provided is not always useful. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Getting WiFi to work
On Saturday, 13 April 2024 15:49:27 BST Peter Humphrey wrote: > On Friday, 12 April 2024 16:39:12 BST Michael wrote: > > On Friday, 12 April 2024 16:05:46 BST Peter Humphrey wrote: > > > On Friday, 12 April 2024 14:35:02 BST Michael wrote: > > > > There are GUI front-ends for the above to suit various desktop and > > > > user > > > > preferences, some more polished than others. > > > > > > Hm. I haven't found one for iwd yet... > > > > There is net-wireless/iwgtk in portage. Other GUI applications exist > > (idwgui, dmenu-iwd-gui), plus the general GUI front ends of networkmanager > > and connman. > > Of course, I found iwgtk a minute after sending that last. Network Manager > is what I'm trying to avoid, mostly because it makes a mess of my existing > wired LAN with its static addresses. I may have to revisit that whole > setup. If you are using the netifrc script for your wired ethernet, you can add to your /etc/conf.d/net the wireless part and call upon wpa_supplicant or iwd to manage association and authentication with your AP. For a laptop, when using different APs, you can use wpa_supplicant or iwd with dhcpcd without using netifrc. Then use wpa_gui or iwgtk to select preferred APs and to enter your credentials. There are a number of combinations and permutations with the above tools to try out and see what suits. I have never used networkmanager unless it comes as the default software with a binary distro. Thankfully Gentoo offers a lot of choice and flexibility. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] NAS box and switching from Phenom II X6 1090T to FX-6300
On Saturday, 13 April 2024 12:12:04 BST Dale wrote: > Michael wrote: > > On Saturday, 13 April 2024 08:58:50 BST Dale wrote: > >> Howdy, > >> > >> As most likely know, I have a older box I use for backups. The hard > >> drives are encrypted which likes the CPU to have AES support. The > >> Phenom CPUs don't seam to support AES from what I've seen. The specs > >> for the mobo says the mobo does support the FX-6300 CPU tho which has > >> AES support. Since the biggest thing I use that system for is my > >> backups, would it be better to have the FX-6300 CPU which supports AES > >> or the Phenom 1090T? Mobo only shows it supports the FX-6300 and no > >> other FX series CPU. Could be that it doesn't support anything else, > >> could be the list hasn't been updated. I dunno. > >> > >> Given the FX-6300 has a higher clocks speed, 3.8GHz versus 3.2GHz for > >> the Phenom, I'd think the FX would be a upgrade, quite a good one at > >> that. More L2 cache too. Both are 6 cores according to what I found. > >> Anyone know something I don't that would make switching to the FX-6300 a > >> bad idea? > >> > >> https://www.gigabyte.com/us/Motherboard/GA-770T-USB3-rev-10/support#suppo > >> rt-> cpu > >> > >> You may have to click on CPU support to see it. Sometimes it goes to it > >> directly, sometimes not. :/ > >> > >> Thanks. > >> > >> Dale > >> > >> :-) :-) > > > > I can't find where the link you provide mentions FX-6300, an AM3+ socket > > CPU, being compatible with GA-770T-USB3-rev-10, an AM3 socket MoBo. The > > FX-6300 would definitely be a noticeable upgrade (higher base and boost > > frequency, plus AES crypto), assuming you can find a MoBo to fit it on. > > You'll probably find the cost of buying just the CPU of unknown > > provenance, which may well have been cooked with overclocking, will more > > or less equal the cost of buying a suitable MoBo + CPU + RAM already > > assembled. Or even a whole PC ready to run: > > > > https://www.ebay.com/itm/166707210724 > > > > You could get a better result if you start with a budget in mind and then > > fish for the best performance combo you can bag with it. > > Your right. I misread that somehow. Good thing I asked. I could have > ordered a CPU that won't fit. It's a FX-4130 I should be looking at. > No idea where I got the FX-6300 from. As you point out, it's not listed > on the specs page. Still, the FX-4130 shows a faster clock and other > stuff I mentioned except it has 4 cores instead of 6. I got it right > except for the model of the CPU. According to this page it supports AES > for encryption as well. > > > https://www.amd.com/en/support/cpu/amd-fx-series-processors/amd-fx-4-core-bl > ack-edition-processors/fx-4130#! > > > Now that I got the right model of CPU, still be a improvement? I'm > mostly wanting to use this mobo I already have. I just wish the > encryption was faster. The loss of two cores may slow it down a lot, > despite having AES built in. > > Dale > > :-) :-) I think the FX-4130 should give a noticeable improvement on crypto and a small improvement on single thread processing (higher frequency and larger cache). On the other hand it'll suffer on parallel tasks. TBH I'd rather spend the $10 or so for a used FX-4130 on a more modern MoBo plus CPU, than throw good money after bad. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] NAS box and switching from Phenom II X6 1090T to FX-6300
On Saturday, 13 April 2024 08:58:50 BST Dale wrote: > Howdy, > > As most likely know, I have a older box I use for backups. The hard > drives are encrypted which likes the CPU to have AES support. The > Phenom CPUs don't seam to support AES from what I've seen. The specs > for the mobo says the mobo does support the FX-6300 CPU tho which has > AES support. Since the biggest thing I use that system for is my > backups, would it be better to have the FX-6300 CPU which supports AES > or the Phenom 1090T? Mobo only shows it supports the FX-6300 and no > other FX series CPU. Could be that it doesn't support anything else, > could be the list hasn't been updated. I dunno. > > Given the FX-6300 has a higher clocks speed, 3.8GHz versus 3.2GHz for > the Phenom, I'd think the FX would be a upgrade, quite a good one at > that. More L2 cache too. Both are 6 cores according to what I found. > Anyone know something I don't that would make switching to the FX-6300 a > bad idea? > > https://www.gigabyte.com/us/Motherboard/GA-770T-USB3-rev-10/support#support-> > cpu > > You may have to click on CPU support to see it. Sometimes it goes to it > directly, sometimes not. :/ > > Thanks. > > Dale > > :-) :-) I can't find where the link you provide mentions FX-6300, an AM3+ socket CPU, being compatible with GA-770T-USB3-rev-10, an AM3 socket MoBo. The FX-6300 would definitely be a noticeable upgrade (higher base and boost frequency, plus AES crypto), assuming you can find a MoBo to fit it on. You'll probably find the cost of buying just the CPU of unknown provenance, which may well have been cooked with overclocking, will more or less equal the cost of buying a suitable MoBo + CPU + RAM already assembled. Or even a whole PC ready to run: https://www.ebay.com/itm/166707210724 You could get a better result if you start with a budget in mind and then fish for the best performance combo you can bag with it. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Getting WiFi to work
On Friday, 12 April 2024 16:05:46 BST Peter Humphrey wrote: > On Friday, 12 April 2024 14:35:02 BST Michael wrote: > > There are GUI front-ends for the above to suit various desktop and user > > preferences, some more polished than others. > > Hm. I haven't found one for iwd yet... There is net-wireless/iwgtk in portage. Other GUI applications exist (idwgui, dmenu-iwd-gui), plus the general GUI front ends of networkmanager and connman. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Getting WiFi to work
On Friday, 12 April 2024 13:51:37 BST Peter Humphrey wrote: > On Tuesday, 9 April 2024 15:56:28 BST Wojciech Kuzyszyn wrote: > > On Tue, 09 Apr 2024 14:23:31 +0100 > > > > Peter Humphrey wrote: > > > Hello list, > > > > > > I want to move my Intel i5 NUC box to a place where Ethernet is not > > > available, nor like to become so. That means I have to get WiFi > > > working, but I've had no success so far. The wiki pages are many, > > > confusing and contradictory, so I'd like the panel's advice on the > > > way to proceed. > > > > > > The first thing I tried was the traditional wpa_supplicant, which > > > seemed to go well - except that I couldn't get the link out of the > > > DOWN state. > > > > > > Then I tried NetworkManager, and failed with that too. > > > > > > This is the hardware: > > > # lspci -v -s 00:14.3 > > > 00:14.3 Network controller: Intel Corporation Raptor Lake PCH CNVi > > > WiFi (rev 01) > > > --->8 > > > > > > Kernel driver in use: iwlwifi > > > Kernel modules: iwlwifi > > > > > > And this is dmesg: > > > > > > $ dmesg | grep -i wifi > > > [1.622343] Intel(R) Wireless WiFi driver for Linux > > > [1.622432] iwlwifi :00:14.3: enabling device ( -> 0002) > > > [1.625069] iwlwifi :00:14.3: Detected crf-id 0x400410, cnv-id > > > 0x80400 wfpm id 0x8020 > > > [1.625121] iwlwifi :00:14.3: PCI dev 51f1/0094, rev=0x370, > > > rfid=0x2010d000 > > > [1.625313] Loading firmware: iwlwifi-so-a0-gf-a0-86.ucode > > > [1.626644] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ > > > Version: 0.0.2.41 > > > [1.626902] iwlwifi :00:14.3: loaded firmware version > > > 86.fb5c9aeb.0 so- a0-gf-a0-86.ucode op_mode iwlmvm > > > [1.643426] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6E AX211 > > > 160MHz, REV=0x370 > > > [1.651382] iwlwifi :00:14.3: WRT: Invalid buffer destination > > > [1.809375] iwlwifi :00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20 > > > [1.809385] iwlwifi :00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f > > > [1.809394] iwlwifi :00:14.3: WFPM_AUTH_KEY_0: 0x90 > > > [1.809401] iwlwifi :00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0 > > > [1.809403] Loading firmware: iwlwifi-so-a0-gf-a0.pnvm > > > [1.810724] iwlwifi :00:14.3: loaded PNVM version e28bb9d7 > > > [1.810817] iwlwifi :00:14.3: RFIm is deactivated, reason = 4 > > > [1.825831] iwlwifi :00:14.3: Detected RF GF, rfid=0x2010d000 > > > [1.897387] iwlwifi :00:14.3: base HW address: > > > f4:6d:3f:2a:33:3e > > > > > > Would net-wireless/iwd get me a bit further? > > > > > > Meanwhile, I'll keep on exploring with the results of > > > sys-apps/hw-probe. > > > > Hello! > > > > I have never managed to get WiFi working with iwlwifi, but iwd works > > great for me. Give it a try! > > According to > https://wiki.gentoo.org/wiki/Handbook:AMD64/Networking/Wireless, "the > net-wireless/iw software...cannot connect to WPA-only Access Points." > > I think my Fritz!Box 7530 router has that limitation, but It's hard to know. For clarity: The iwlwifi is a kernel driver for Intel wireless chips. The net-wireless/iw software can be used to manage the wireless association with an AP if the latter has been configured to offer connections with the deprecated and insecure WEP, or no encryption. The net-wireless/wpa_supplicant software can be used to manage the negotiation for a wireless connection with an AP when this has encryption enabled (WPA, WPA-2, WPA-3). The net-wireless/iwd is a more modern software developed by Intel to replace wpa_supplicant. In addition it will also create wireless interfaces as it needs to and manage these, as opposed to leaving this function to udev. Essentially iwd takes over the management of wireless interfaces and their encrypted communication with an AP in a standalone fashion. I haven't tried this yet to find out how it behaves, but it is rumoured to be more polished than wpa_supplicant and can work without netifrc scripts or dhcpcd. There are GUI front-ends for the above to suit various desktop and user preferences, some more polished than others. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] acct-user/man usermod: user 'man' does not exist in /etc/passwd
On Thursday, 11 April 2024 16:08:54 BST Dale wrote: > I don't recall editing this file ever. From my understanding, commands > are used to manage that file. I can't say for sure but it's doubtful I > edited that file. > > I can easily do a emerge -ek world if you think it would be wise to do > so. I guess that would reset ownership of files as it reinstalls. > Thoughts? > > Thanks. > > Dale > > :-) :-) I can't really advise what to do, it depends on your level of concern about this discrepancy with the 'man' account. The question to mull over is what could a rogue 'man' account have changed since your last full emerge @world? If you upgraded your profile from 17.1 to 23.0 recently you would have re- emerged @world, so all packages would have been reinstalled. If you run find to print recently changed files since the profile upgrade, you'll have some pointers for packages to emerge again. Or, with the 'man' account safely back in its box you can change passwds/keys and re-emerge the whole @world once more. If you are totally worried to the point of not being able to trust your system, then you'll need to reformat and start with a fresh stage3 download and fresh sources. Do not blindly copy all your configuration files from the backups, but diff them to make sure only changes you approve make it into the new system. This can be a lot of work, which you may not be inclined to embark on and could potentially be an overkill. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Getting WiFi to work
On Thursday, 11 April 2024 16:15:52 BST Peter Humphrey wrote: > On Thursday, 11 April 2024 16:08:35 BST Michael wrote: > > On Thursday, 11 April 2024 13:49:18 BST Peter Humphrey wrote: > --->8 > > > > I decided to establish a firm, clean system to fall back to after > > > messing > > > about with the various wifi packages, so I built a fresh system building > > > on the merged-usr stage-3. I was surprised to find that kde-plasma/ > > > powerdevil now insists on installing Network Manager unless I set USE=- > > > wireless against it. > > > > > > Why has this happened? Can't the poor power devil cope with any other > > > way > > > of running WiFi? > > > > The USE="wireless" flag on powerdevil is needed to save energy when the > > bluetooth/wireless chip is idle. This function could be useful with > > laptops running on battery. > > > > If you set USE="-networkmanager" in make.conf and USE="-wireless" for the > > powerdevil package you won't be bothered by this again. > > I already had USE="-networkmanager" in make.conf. > > This is not a laptop and it has no battery. Nowhere on the system is there > any hint to the contrary, so I still think this has not been thought > through. The logic should have included alternatives to Network Manager. Yes, I agree wholeheartedly. However, these decisions are taken upstream, where there is a tendency of convergence to monoculture. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Getting WiFi to work
On Thursday, 11 April 2024 13:49:18 BST Peter Humphrey wrote: > On Tuesday, 9 April 2024 14:44:05 BST Paul Sopka wrote: > > On 09.04.24 15:23, Peter Humphrey wrote: > > > Hello list, > > > > > > I want to move my Intel i5 NUC box to a place where Ethernet is not > > > available, nor like to become so. That means I have to get WiFi working, > > > but I've had no success so far. The wiki pages are many, confusing and > > > contradictory, so I'd like the panel's advice on the way to proceed. > > > > > > The first thing I tried was the traditional wpa_supplicant, which seemed > > > to go well - except that I couldn't get the link out of the DOWN state. > > > > > > Then I tried NetworkManager, and failed with that too. > > > > > > This is the hardware: > > > # lspci -v -s 00:14.3 > > > 00:14.3 Network controller: Intel Corporation Raptor Lake PCH CNVi WiFi > > > (rev 01) > > > --->8 > > > > > > Kernel driver in use: iwlwifi > > > Kernel modules: iwlwifi > > > > > > And this is dmesg: > > > > > > $ dmesg | grep -i wifi > > > [1.622343] Intel(R) Wireless WiFi driver for Linux > > > [1.622432] iwlwifi :00:14.3: enabling device ( -> 0002) > > > [1.625069] iwlwifi :00:14.3: Detected crf-id 0x400410, cnv-id > > > 0x80400 wfpm id 0x8020 > > > [1.625121] iwlwifi :00:14.3: PCI dev 51f1/0094, rev=0x370, > > > rfid=0x2010d000 > > > [1.625313] Loading firmware: iwlwifi-so-a0-gf-a0-86.ucode > > > [1.626644] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: > > > 0.0.2.41 > > > [1.626902] iwlwifi :00:14.3: loaded firmware version > > > 86.fb5c9aeb.0 > > > so- a0-gf-a0-86.ucode op_mode iwlmvm > > > [1.643426] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6E AX211 > > > 160MHz, REV=0x370 > > > [1.651382] iwlwifi :00:14.3: WRT: Invalid buffer destination > > > [1.809375] iwlwifi :00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20 > > > [1.809385] iwlwifi :00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f > > > [1.809394] iwlwifi :00:14.3: WFPM_AUTH_KEY_0: 0x90 > > > [1.809401] iwlwifi :00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0 > > > [1.809403] Loading firmware: iwlwifi-so-a0-gf-a0.pnvm > > > [1.810724] iwlwifi :00:14.3: loaded PNVM version e28bb9d7 > > > [1.810817] iwlwifi :00:14.3: RFIm is deactivated, reason = 4 > > > [1.825831] iwlwifi :00:14.3: Detected RF GF, rfid=0x2010d000 > > > [1.897387] iwlwifi :00:14.3: base HW address: f4:6d:3f:2a:33:3e > > > > > > Would net-wireless/iwd get me a bit further? > > > > > > Meanwhile, I'll keep on exploring with the results of sys-apps/hw-probe. > > > > Hey Peter > > > > This might be the wrong firmware being loaded. > > > > Are you building your the iwlwifi driver not as a module but directly > > into the kernel? > > > > Are you including your firmware into the kernel? > > > > If you do the above, try loading the driver as a module. Also enable > > both DVM and MVM Firmware support. > > > > Then emerge sys-kernel/linux-firmware without USE=savedconfig. > > > > Finally reboot and check wther it works. If it works, check which > > firmware is loaded in your dmesg. > > I decided to establish a firm, clean system to fall back to after messing > about with the various wifi packages, so I built a fresh system building on > the merged-usr stage-3. I was surprised to find that kde-plasma/powerdevil > now insists on installing Network Manager unless I set USE=-wireless > against it. > > Why has this happened? Can't the poor power devil cope with any other way of > running WiFi? The USE="wireless" flag on powerdevil is needed to save energy when the bluetooth/wireless chip is idle. This function could be useful with laptops running on battery. If you set USE="-networkmanager" in make.conf and USE="-wireless" for the powerdevil package you won't be bothered by this again. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] acct-user/man usermod: user 'man' does not exist in /etc/passwd
On Thursday, 11 April 2024 12:58:17 BST Dale wrote: > Michael wrote: > > On Thursday, 11 April 2024 10:22:59 BST Dale wrote: > >> I fixed it by commenting out the entry in the passwd file. It then > >> created a new entry. I guess it was set wrong at some point. Just > >> looks like emerge would be able to update it tho. Joost showing my > >> setting was different gave me the clue that my current entry was wrong. > >> I was kinda chicken to comment it out or remove it before then. ;-) > >> > >> Dale > >> > >> :-) :-) > > > > It begs the question who/what could have changed the root group membership > > to include the system account 'man'. This is highly irregular. Have you > > looked at your backups to find out when /etc/group was changed last time? > > Also emerge.log to find the last time acct-user/man was installed > > successfully before this error started occurring. > > Well, this has been failing for a while. It's just that with the > profile change, I wanted to re-emerge all packages. I'm sure this one > hasn't really changed or anything but still, I wanted a clean start. > > My OS backup updates each week. So, backups is far to up to date to > know. It's what I use to build the binary packages in. I also > sometimes experiment as well when some package is giving me grief. I > mostly just use the -k option on my main OS. > > I looked in /usr/share/man, I guess that is where most if not all man > pages are, and they all appear to be owned by root and group is root. > Should they be owned by man? If possible, can you post the owner and > group for yours? I can change mine. I tested a few man pages, they all > post fine but I'm usually root anyway. Works for user dale to tho. > > Thanks. > > Dale > > :-) :-) The /usr/share/man directory and man pages within it are owned by root:root; e.g. # ls -al /usr/share/man/man8/agetty.8.bz2 -rw-r--r-- 1 root root 7307 Apr 4 10:46 /usr/share/man/man8/agetty.8.bz2 The problem in your case was the system account 'man' had been added to group 'root'. This creates a privilege escalation and as such it is suspicious. Had you done this by accident and now you corrected it, then hopefully you do not need to be unduly worried. Had someone else done this ... then this should be setting off alarm bells. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] How to find out all openrc dependencies?
On Thursday, 11 April 2024 10:48:15 BST J. Roeleveld wrote: > On Thursday, 11 April 2024 11:35:10 CEST Michael wrote: > > On Thursday, 11 April 2024 06:19:57 BST J. Roeleveld wrote: > > > Hi all, > > > > > > For a while I've been seeing the following ERROR-messages when booting 1 > > > of > > > my systems: > > > > > > * ERROR: cannot start multipathd as localmount would not start > > > > > > * ERROR: cannot start zfs-import as localmount would not start > > > > > > This isn't a big concern as these services will start correctly later: > > > > > > INIT: Entering runlevel: 3 > > > > > > * Starting multipathd ... > > > [ ok ] > > > * Importing ZFS pool(s) ... > > > [ ok ] > > > > > > But I am trying to find the cause of these errors as they are preventing > > > parallel-start from actually working correctly. > > > > > > When I check with "rc-depend", I don't see an obious cause: > > > > > > # /lib/rc/bin/rc-depend multipathd > > > sysfs devfs udev udev-trigger modules fsck root localmount multipathd > > > > > > # /lib/rc/bin/rc-depend localmount > > > sysfs devfs udev udev-trigger modules fsck root localmount > > > > > > # /lib/rc/bin/rc-depend zfs-import > > > multipath sysfs devfs udev udev-trigger modules fsck root localmount > > > multipathd zfs-import > > > > > > # /lib/rc/bin/rc-depend multipath > > > multipath > > > > > > From how I read these, it should be able to start "localmount" properly > > > before even trying to start "multipathd" and "zfs-import" > > > There is also no technical dependency for "localmount" (the root > > > filesystem > > > is not on ZFS on this system) > > > > > > Any help/suggestions on how to find the cause would be appreciated. > > > > > > -- > > > Joost > > > > Check if hwclock is in the boot runlevel: > > > > rc-update -s -v | grep hwclock > > What does "hwclock" got to do with this? > It has no dependency with multipathd, zfs-import, localmount or anything > else that is showing an error. > > -- > Joost Our systems are certainly different, but I noticed this dependency on my localmount which is missing on yours: # /lib/rc/bin/rc-depend localmount sysfs devfs udev udev-trigger hwclock modules fsck root dmcrypt localmount ^^^ Have you compared your system services which has this problem, with other systems of yours which can startup properly? signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] How to find out all openrc dependencies?
On Thursday, 11 April 2024 06:19:57 BST J. Roeleveld wrote: > Hi all, > > For a while I've been seeing the following ERROR-messages when booting 1 of > my systems: > > * ERROR: cannot start multipathd as localmount would not start > * ERROR: cannot start zfs-import as localmount would not start > > This isn't a big concern as these services will start correctly later: > > INIT: Entering runlevel: 3 > * Starting multipathd ... > [ ok ] > * Importing ZFS pool(s) ... > [ ok ] > > But I am trying to find the cause of these errors as they are preventing > parallel-start from actually working correctly. > > When I check with "rc-depend", I don't see an obious cause: > > # /lib/rc/bin/rc-depend multipathd > sysfs devfs udev udev-trigger modules fsck root localmount multipathd > > # /lib/rc/bin/rc-depend localmount > sysfs devfs udev udev-trigger modules fsck root localmount > > # /lib/rc/bin/rc-depend zfs-import > multipath sysfs devfs udev udev-trigger modules fsck root localmount > multipathd zfs-import > > # /lib/rc/bin/rc-depend multipath > multipath > > From how I read these, it should be able to start "localmount" properly > before even trying to start "multipathd" and "zfs-import" > There is also no technical dependency for "localmount" (the root filesystem > is not on ZFS on this system) > > Any help/suggestions on how to find the cause would be appreciated. > > -- > Joost Check if hwclock is in the boot runlevel: rc-update -s -v | grep hwclock signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] acct-user/man usermod: user 'man' does not exist in /etc/passwd
On Thursday, 11 April 2024 10:22:59 BST Dale wrote: > I fixed it by commenting out the entry in the passwd file. It then > created a new entry. I guess it was set wrong at some point. Just > looks like emerge would be able to update it tho. Joost showing my > setting was different gave me the clue that my current entry was wrong. > I was kinda chicken to comment it out or remove it before then. ;-) > > Dale > > :-) :-) It begs the question who/what could have changed the root group membership to include the system account 'man'. This is highly irregular. Have you looked at your backups to find out when /etc/group was changed last time? Also emerge.log to find the last time acct-user/man was installed successfully before this error started occurring. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] acct-user/man usermod: user 'man' does not exist in /etc/passwd
On Thursday, 11 April 2024 02:23:22 BST Dale wrote: > Howdy, > > This failed once before but I didn't worry about it. However, since the > profile update, it still fails. I'd like to figure out how to fix it. > I tried doing a emerge -C and then emerging it again. No help. This is > the output. It's not to long, whole thing. :-D > >>> Completed installing acct-user/man-1-r3 into > > /var/tmp/portage/acct-user/man-1-r3/image OK, so far so good. :-) > * Final size of build directory: 0 KiB > * Final size of installed tree: 4 KiB > > ./ > ./usr/ > ./usr/lib/ > ./usr/lib/sysusers.d/ > ./usr/lib/sysusers.d/acct-user-man.conf > > >>> Done. > > * checking 1 files for package collisions > > >>> Merging acct-user/man-1-r3 to / > > error writing passwd entry: Invalid argument > * User man already exists > --- /usr/ > --- /usr/lib/ > --- /usr/lib/sysusers.d/ > > >>> /usr/lib/sysusers.d/acct-user-man.conf > > * Removing user man from group(s): root What?! Group 'root' should only have user 'root' as its member: # grep root:x /etc/group root:x:0:root > * To retain the user's group membership in the local system > * config, override with ACCT_USER_MAN_GROUPS or > * ACCT_USER_MAN_GROUPS_ADD in make.conf. > * Documentation reference: > * > https://wiki.gentoo.org/wiki/Practical_guide_to_the_GLEP_81_migration#Overri > de_user_groups * Updating user man > usermod: user 'man' does not exist in /etc/passwd This is not right, unless you removed 'man' manually? # grep man /etc/passwd man:x:13:15:System user; man:/dev/null:/sbin/nologin > usermod: failed to unlock /etc/gshadow > * usermod: user 'man' does not exist in /etc/passwd > * usermod: failed to unlock /etc/gshadow # stat /etc/passwd File: /etc/passwd Size: 1636Blocks: 4 IO Block: 4096 regular file Device: 259,2 Inode: 18587 Links: 1 Access: (0644/-rw-r--r--) Uid: (0/root) Gid: (0/root) # stat /etc/shadow File: /etc/shadow Size: 815 Blocks: 2 IO Block: 4096 regular file Device: 259,2 Inode: 18602 Links: 1 Access: (0640/-rw-r-) Uid: (0/root) Gid: (0/root) # stat /etc/gshadow File: /etc/gshadow Size: 636 Blocks: 2 IO Block: 4096 regular file Device: 259,2 Inode: 18562 Links: 1 Access: (0400/-r) Uid: (0/root) Gid: (0/root) Check what yours look like, then try to correct them. It would be a good idea to fsck the partition too and check smartctl, in case you have fs corruption. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] eselect repository and adding overlay.
On Sunday, 7 April 2024 20:17:31 BST Dale wrote: > Howdy, > > A while back using overlays changed. Using eselect is supposed to be > the new way, and easier. Either I'm missing something or something is > missing from the docs. I tried to add voyageur to my NAS box/backup > rig. The command to add it works fine. However, when I try to sync it, > either just the overlay or the whole tree with eix-sync, I get this: > > >>> Syncing repository 'voyageur' into '/var/db/repos/voyageur'... > > /usr/bin/git clone --depth 1 > https://cafarelli.fr/cgi-bin/cgit.cgi/voyageur-overlay/ . > fatal: destination path '.' already exists and is not an empty directory. > !!! git clone error in /var/db/repos/voyageur > > Action: sync for repo: gentoo, returned code = 0 > Action: sync for repo: voyageur, returned code = 128 > > > > When I try to emerge something, anything will do, I start seeing this. > > > > WARNING: One or more repositories have missing repo_name entries: > > /var/db/repos/voyageur/profiles/repo_name > > NOTE: Each repo_name entry should be a plain text file containing a > unique name for the repository on the first line. > > > Shouldn't adding the overlay or syncing it fix that? Shouldn't all the > files it needs be put there by either eselect or a sync? If you have older files in there it may be causing a clash. I'd run: eselect repository remove -f voyageur Then check the directory /var/db/repos/ no longer contains the subdirectory voyager. If it does remove it manually. Then add the repository afresh: eselect repository add voyageur and finally try to resync it. Should the error repeat itself, then something must be amiss with the overlay itself and you should report it to the overlay maintainer. HTH, signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New profile - gentoo and binutils ...
On Sunday, 7 April 2024 15:46:18 BST Wols Lists wrote: > On 07/04/2024 13:07, Michael wrote: > > Did you emerge any packages using the new 23.0 profile, then went back to > > the old profile to run the above command? > > No ... > > Ummm ... I have had trouble emerging other stuff that didn't want to > work with oneshot ... > > Let me look at my make.conf - I had to over-ride something to get > vbox-modules to emerge, this is probably the same thing ... > > Yup - as soon as I comment the EMERGE_DEFAULT_OPTS out I get it asking > me if I want to emerge binutils. > > # EMERGE_DEFAULT_OPTS = "--buildpkg --deep --newuse --oneshot --usepkg" > > So I'm doing an emerge @world now with the old profile ... > > Cheers, > Wol Cool, once your system is up to date you should be able to change your profile and follow the rest of the instructions. I hope all goes well. :-) signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New profile - gentoo and binutils ...
On Sunday, 7 April 2024 12:04:32 BST Wols Lists wrote: > On 07/04/2024 11:48, Wols Lists wrote: > > On 07/04/2024 11:23, Michael wrote: > >> On Sunday, 7 April 2024 11:21:00 BST Wols Lists wrote: > >>> On 07/04/2024 11:00, Wols Lists wrote: > >>>> What do I do here - "emerge binutils" (step 9) wants to emerge gcc, > >>>> which the instructions say "emerge AFTER binutils". > >>>> > >>>> With gcc it says "don't let it emerge glibc", should I apply the same > >>>> logic and not let binutils emerge gcc? > >>> > >>> Just to follow up to myself, I've just done a complete update, but a lot > >>> of the dependencies are pulled in by "change-use", namely lzma, zstd. Is > >>> that fallout from the XZ debacle? Would a --no-deps be safe? > >>> > >>> Cheers, > >>> Wol > >> > >> Are you still on your original profile, or have you used eselect to > >> change it > >> to profile 23.0? > >> > >> If the latter, change back to your old profile, update @world, > >> depclean and > >> then start with the rest of the migration instructions. > > > > Just done that. See my other email. > > > > NOTHING TO UPDATE (unless I've messed up my emerge ...) > > Interesting ... just done this under the old profile ... > > thewolery /usr/local/bin # emerge --ask --oneshot sys-devel/binutils > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > Dependency resolution took 3.19 s (backtrack: 0/20). > > > Nothing to merge; quitting. > > Cheers, > Wol Hmm ... something is amiss with your system. Normally you would get this: # emerge --ask --oneshot sys-devel/binutils These are the packages that would be merged, in order: Calculating dependencies... done! Dependency resolution took 1.30 s (backtrack: 0/20). [ebuild R] sys-devel/binutils-2.41-r5 Would you like to merge these packages? [Yes/No] Did you emerge any packages using the new 23.0 profile, then went back to the old profile to run the above command? signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New profile - gentoo and binutils ...
On Sunday, 7 April 2024 11:48:07 BST Wols Lists wrote: > On 07/04/2024 11:23, Michael wrote: > > On Sunday, 7 April 2024 11:21:00 BST Wols Lists wrote: > >> On 07/04/2024 11:00, Wols Lists wrote: > >>> What do I do here - "emerge binutils" (step 9) wants to emerge gcc, > >>> which the instructions say "emerge AFTER binutils". > >>> > >>> With gcc it says "don't let it emerge glibc", should I apply the same > >>> logic and not let binutils emerge gcc? > >> > >> Just to follow up to myself, I've just done a complete update, but a lot > >> of the dependencies are pulled in by "change-use", namely lzma, zstd. Is > >> that fallout from the XZ debacle? Would a --no-deps be safe? > >> > >> Cheers, > >> Wol > > > > Are you still on your original profile, or have you used eselect to change > > it to profile 23.0? > > > > If the latter, change back to your old profile, update @world, depclean > > and > > then start with the rest of the migration instructions. > > Just done that. See my other email. > > NOTHING TO UPDATE (unless I've messed up my emerge ...) > > Cheers, > Wol OK, in case you haven't, I'd also run: emerge @preserved-rebuild -v -a and emerge --depclean -v -a to remove any dependencies no longer needed. Then change your profile to: [28] default/linux/amd64/23.0/desktop/plasma/systemd (stable) and continue with the emerge of binutils, gcc, glibc, libtool. You can use '--nodeps' to emerge them in the order given in the profile migration guide, although from what I've experienced this only happens with gcc and glibc. :-/ signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New profile - gentoo and binutils ...
On Sunday, 7 April 2024 11:21:00 BST Wols Lists wrote: > On 07/04/2024 11:00, Wols Lists wrote: > > What do I do here - "emerge binutils" (step 9) wants to emerge gcc, > > which the instructions say "emerge AFTER binutils". > > > > With gcc it says "don't let it emerge glibc", should I apply the same > > logic and not let binutils emerge gcc? > > Just to follow up to myself, I've just done a complete update, but a lot > of the dependencies are pulled in by "change-use", namely lzma, zstd. Is > that fallout from the XZ debacle? Would a --no-deps be safe? > > Cheers, > Wol Are you still on your original profile, or have you used eselect to change it to profile 23.0? If the latter, change back to your old profile, update @world, depclean and then start with the rest of the migration instructions. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New profile - gentoo and binutils ...
On Sunday, 7 April 2024 11:00:49 BST Wols Lists wrote: > What do I do here - "emerge binutils" (step 9) wants to emerge gcc, > which the instructions say "emerge AFTER binutils". > > With gcc it says "don't let it emerge glibc", should I apply the same > logic and not let binutils emerge gcc? > > Cheers, > Wol Step 1: Ensure your system backups are up to date. Please also update your system fully and depclean before proceeding. Have you done this already after a fresh rsync of portage? signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Program shutting down - where is its status held?
On Fri, 2024-04-05 at 16:09 +0100, Peter Humphrey wrote:
> On Thursday, 4 April 2024 10:12:23 BST I wrote:
>
> > Some of my machines run BOINC, which I want to stop while doing my sync &
> > update. For some reason, '/etc/init.d/boinc stop' often takes exactly 60s to
> > complete instead of its normal 6-10s.
> >
> > I'd like my update script to detect this condition, but I can't see how.
> > I've tried grepping /bin/ps output, and I've tried checking for existence
> > of a BOINC pid file, but those both tell me that BOINC is "running" while
> > it's in the process of shutting down.
> >
> > Is there somewhere in /proc where this shutting-down status is held?
>
> Let me ask a different way: does start-stop-daemon keep the current,
> transient
> status of the daemon it's operating on anywhere other than in its own
> variables, and thus accessible for inspection?
>
>
Not really. All start-stop-daemon is doing is sending SIGTERM/SIGKILL
signals to the boinc process:
stop() {
local stop_timeout="SIGTERM/60/SIGTERM/30/SIGKILL/30"
env_check || return 1
ebegin "Stopping ${RC_SVCNAME}"
start-stop-daemon --stop --quiet --progress \
--retry ${stop_timeout} \
--pidfile "${BOINC_PIDFILE}"
eend $?
}
The "stop_timeout" thing says that a SIGTERM will be tried first, and
if that doesn't work, a second SIGTERM will be sent after 60s. If
*that* doesn't work, then finally a SIGKILL will be sent after an
additional 30s.
Personally, I would try to figure out why boinc doesn't want to stop
when you tell it to stop. But barring that, you could add pre- and
post-stop hooks that will let you know that the daemon is stopping.
For example, in /etc/conf.d/boinc, you could put
stop_pre(){
touch /run/stopping-boinc
}
stop_post(){
rm -f /run/stopping-boinc
}
or something like that. (I haven't tested, but the idea is sound.)
Then, if that file exists, boinc is stopping.
Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
On Friday, 5 April 2024 07:34:01 BST Paul Sopka wrote: > On 05.04.24 08:31, Paul Sopka wrote: > > On 05.04.24 00:55, Michael wrote: > >> Your toolchain is now correct. Can you show the output of: > >> > >> equery u media-libs/libjpeg-turbo > >> > >> and > >> > >> emerge --info media-libs/libjpeg-turbo > >> > >> However, it could be this is a bug, you can check here for reports: > >> > >> https://bugs.gentoo.org/buglist.cgi?quicksearch=media-libs%2Flibjpeg-turb > >> o > >> > >> > >> If this is the only package you're getting a problem with, you can run: > >> > >> emerge --resume --skipfirst > >> > >> to complete your migration to profile 23.0, then try again to emerge > >> libjpeg- > >> turbo on its own. > > Also one or two weeks ago I successfully emerged with emptytree after > migrating to profile 23.0. OK, for some reason (packages which require 32bit binary compatibility, or you setting some specific USE flag for a package in portage) the media-libs/ libjpeg-turbo had been built also with abi_x86_32. Now it seems your USE flags and corresponding build time dependencies have changed. Can you get it to build with: ABI_X86="64 -32 -x32" emerge -1aDv media-libs/libjpeg-turbo Check what flags you have set for packages in your /etc/portage/package.use to make them consistent. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
On Thursday, 4 April 2024 21:32:37 BST Paul Sopka wrote: > On 04.04.24 00:44, Michael wrote: > > No, this is not normal. I wonder if your make.conf settings are correct. > > Start with some safe CFLAGS as suggested here: > > > > https://wiki.gentoo.org/wiki/Safe_CFLAGS > > > > Then use the package 'app-portage/cpuid2cpuflags' to set the correct CPU > > flags: > > > > https://wiki.gentoo.org/wiki/CPU_FLAGS_* > > > > At this point you should be able to use gcc with no further problems. You > > can try to optimise your settings further by taking a look at suggestions > > here: > > > > https://wiki.gentoo.org/wiki/GCC_optimization > > A little correction, even though the "-march=" change removed the > warning gcc threw, it unfortunately didn't solve the issue. I just > recompiled dev-lang/nasm, and after that recompiled libjpeg-turbo, and I > have the same hang on "Detecting C compiler ABI info" again. Your toolchain is now correct. Can you show the output of: equery u media-libs/libjpeg-turbo and emerge --info media-libs/libjpeg-turbo However, it could be this is a bug, you can check here for reports: https://bugs.gentoo.org/buglist.cgi?quicksearch=media-libs%2Flibjpeg-turbo If this is the only package you're getting a problem with, you can run: emerge --resume --skipfirst to complete your migration to profile 23.0, then try again to emerge libjpeg- turbo on its own. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Every other startup results in a black screen (possibly SDDM related?)
On Thursday, 4 April 2024 05:55:20 BST Markus Gustafsson wrote: > Hi again, > > I tried to catch the error again and while doing so I realized you guys are of course correct: sddm usually starts on tty 2. I don't know why I got it into my head that it would start on tty 8. Anyway, when I finally got it to reproduce (took a few restarts) I didn't get a blinking cursor on tty 2, the monitor just goes to sleep (kind of like it does when it has no signal). Switching to tty 1 showed me the init log and let me log on so I could run the commands suggested earlier in this thread: > > $ ps aux | grep sddm > > root 2253 0.0 0.0 142408 14248 ?Ssl 06:26 0:00 > > /usr/bin/sddm root 2300 0.2 0.2 1653332 89588 ? Ssl 06:26 > > 0:00 /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth > > /run/sddm/xauth_UanezA -noreset -displayfd 16 root 2358 0.0 0.0 > > 61872 14024 ?S06:26 0:00 /usr/libexec/sddm-helper --socket > > /tmp/sddm-auth-49123ec6-075d-4982-860d-ea1de56059ca --id 2 --start > > /usr/bin/sddm-greeter --socket /tmp/sddm-:0-emmSdV --user sddm --greeter > > sddm 2359 0.0 0.4 1557540 135804 ? Sl 06:26 0:00 > > /usr/bin/sddm-greeter --socket /tmp/sddm-:0-emmSdV sddm 2365 0.0 > > 0.0 4320 1892 ?S06:26 0:00 dbus-launch --autolaunch > > d3bb17ba0dc5f70ad177e3f764fe168e --binary-syntax --close-stderr sddm > > 2366 0.0 0.0 4620 224 ?Ss 06:26 0:00 > > /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 > > --session All of the above looks healthy to me. > > $ rc-service sddm status > > * rc-service: service `sddm' does not exist > > This is what the command yields for a successful startup as well though. Should 'sddm' perhaps be 'display-manager' in the command above? Yes, the sddm DM is started by the 'display-manager' OpenRC service from the 'default' runlevel: ~ $ rc-update -s -v | grep display display-manager | default display-manager-setup | > Anyway: > > rc-status > > Runlevel: default > > > > sysklogd [ > > started ] dhcpcd > > [ started ] dbus > > [ started ] netmount > >[ started ] chronyd > > [ started ] cupsd > > [ started ] switcheroo-control > > [ started ] display-manager > >[ started ] numlock > > [ started ] local > > [ started > > ]> > > Dynamic Runlevel: hotplugged > > Dynamic Runlevel: needed/wanted > > > > display-manager-setup [ > > started ] avahi-daemon > > [ started ]> > > Dynamic Runlevel: manual > > This is also what it looks like for a successful startup. Yes, nothing wrong with the above. > And finally from /var/log/sddm.log: > > [06:26:03.740] (II) DAEMON: Initializing... > > [06:26:03.743] (II) DAEMON: Starting... > > [06:26:03.743] (II) DAEMON: Logind interface found > > [06:26:03.743] (II) DAEMON: Adding new display... > > [06:26:03.744] (II) DAEMON: Loaded empty theme configuration > > [06:26:03.744] (II) DAEMON: Xauthority path: "/run/sddm/xauth_UanezA" > > [06:26:03.744] (II) DAEMON: Using VT 2 > > [06:26:03.744] (II) DAEMON: Display server starting... > > [06:26:03.744] (II) DAEMON: Writing cookie to "/run/sddm/xauth_UanezA" > > [06:26:03.744] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -background > > none -seat seat0 vt2 -auth /run/sddm/xauth_UanezA -noreset -displayfd 16 > > [06:26:04.993] (II) DAEMON: Setting default cursor > > [06:26:05.010] (II) DAEMON: Running display setup script > > "/usr/share/sddm/scripts/Xsetup" [06:26:05.012] (II) DAEMON: Display > > server started. > > [06:26:05.012] (II) DAEMON: Socket server starting... > > [06:26:05.012] (II) DAEMON: Socket server started. > > [06:26:05.012] (II) DAEMON: Loaded empty theme configuration > > [06:26:05.012] (II) DAEMON: Greeter starting... > > [06:26:05.022] (II) HELPER: [PAM] Starting... > > [06:26:05.022] (II) HELPER: [PAM] Authenticating... > > [06:26:05.022] (II) HELPER: [PAM] returning. > > [06:26:05.142] (II) HELPER: Writing cookie to "/tmp/xauth_hBdSRs" > > [06:26:05.142] (II) HELPER: Starting X11 session: "" > > "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-emmSdV" [06:26:05.152] (II) > > DAEMON: Greeter session started successfully > > [06:26:05.208] (II) DAEMON: Message
Re: [gentoo-user] Every other startup results in a black screen (possibly SDDM related?)
On Wednesday, 3 April 2024 19:29:11 BST Markus Gustafsson wrote: > Hi, > > I'm having a problem I'm not quite sure how to tackle: every other startup > or so results in a black screen. Usually nothing gets printed (no bios > splash, not GRUB menu, no OpenRC prints), and the monitor goes to low power > mode after a while (I haven't quite confirmed if this is actually the case, > or if everything happens before my monitor have actually stated, but I'd > expect the GRUB menu would hang long enough for it to do so). You can increase the GRUB timeout to a longer interval, but if this an intermittent phenomenon it is probably related to hardware. Check your cable and replace it if possible, or use an alternative port (DP/HDMI/DVI). > However, it does wake up if I switch to another TTY (e.g. ctrl+alt+F4) and > lets me log on, so it has obviously booted up. If I switch back to TTY 8 > from there it just shows a blinking cursor (i.e. not SDDM, which is what > I'd expect). If I reboot from the TTY that lets me log on, the boot process > is usually normal and leaves me at the SDDM login. As others have mentioned sddm now starts in the first available tty, normaly on VT2. However, some users/PCs appear to have problems with more recent sddm versions, whereby the sddm-greeter fails to start, or fails to login into a desktop: https://bugs.gentoo.org/913862 > Any tips on how to debug this would be much appreciated. Check the output on /var/log/ssdm when this problem manifests. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
On Wednesday, 3 April 2024 19:20:27 BST Paul Sopka wrote: > On 03.04.24 09:40, Michael wrote: > > In case you haven't done it yet, if you rebuild the toolchain things > > should > > hopefully self-correct on your system: > > > > emerge --sync > > > > emerge -1av sys-devel/binutils > > > > emerge -1av --nodeps sys-devel/gcc > > > > Use 'gcc-config -l' to check you are using the correct gcc version. > > > > emerge -1av sys-libs/glibc > > > > emerge -1av dev-build/libtool > > > > env-update && source /etc/profile > > Good evening Michael > > Thank you for your suggestions, I tried them, but unfortunately it > didn't help. > > Also, i found out that removing CPU_FLAGS_X86 made the issue disappear, > but another issue appeared later. I experience a similar hang, at "-- > Looking for a ASM_NASM compiler". > > Further, compiling GCC throws the following warnings: > > * QA Notice: Installing libtool files (.la) without corresponding > static libraries! > * /usr/libexec/gcc/x86_64-pc-linux-gnu/13/liblto_plugin.la > * QA Notice: Found the following implicit function declarations in > configure logs: > * > /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-g > nu/32/libgfortran/config.log:4628 - fpsetmask > * > /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-g > nu/libgfortran/config.log:4536 - fpsetmask > * Check that no features were accidentally disabled. > * See https://wiki.gentoo.org/wiki/Modern_C_porting. > * QA Notice: Package triggers severe warnings which indicate that it > *may exhibit random runtime failures. > * > /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/gcc/vec > .h:316: warning: ‘free’ called on unallocated object ‘accesses’ > [-Wfree-nonheap-object] > * > /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/gcc/vec > .h:316:10: warning: ‘free’ called on unallocated object ‘dest_bbs’ > [-Wfree-nonheap-object] > * > /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/gcc/vec > .h:316: warning: ‘free’ called on unallocated object ‘accesses’ > [-Wfree-nonheap-object] > * > /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/gcc/vec > .h:316:10: warning: ‘free’ called on unallocated object ‘dest_bbs’ > [-Wfree-nonheap-object] > * > /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/libsani > tizer/hwasan/hwasan.cpp:539:52: warning: format ‘%zd’ expects a matching > ‘signed size_t’ argument > [-Wformat=] > * Please do not file a Gentoo bug and instead report the above QA > * issues directly to the upstream developers of this software. > * Homepage: https://gcc.gnu.org/ > > Is this normal? No, this is not normal. I wonder if your make.conf settings are correct. Start with some safe CFLAGS as suggested here: https://wiki.gentoo.org/wiki/Safe_CFLAGS Then use the package 'app-portage/cpuid2cpuflags' to set the correct CPU flags: https://wiki.gentoo.org/wiki/CPU_FLAGS_* At this point you should be able to use gcc with no further problems. You can try to optimise your settings further by taking a look at suggestions here: https://wiki.gentoo.org/wiki/GCC_optimization signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Resizing boot partition while dual-booting
On Wednesday, 3 April 2024 16:10:41 BST Vít Smolík wrote: > Hello fellow Gentooers, > > I want to dual-boot Gentoo and M$ Windows on my computer, but windows only > created a 100MB EFI partition. Is it necessary to resize it so my boot > files will fit? If so - how to resize it so I don't mess up my Windows EFI > files? 100M for boot should be enough. This is what I have on one PC here, where / mnt/Windows is the 100M EFI partition: ~ # du -s -h /mnt/Windows 68M /mnt/Windows ~ # du -s -h /mnt/Windows/EFI/* 1.9M/mnt/Windows/EFI/Boot 36M /mnt/Windows/EFI/Gentoo 27M /mnt/Windows/EFI/Microsoft 4.3M/mnt/Windows/EFI/ubuntu The /EFI/Gentoo directory has two kernels, but no initramfs (I don't use it) and I don't use GRUB either: ~ # ls -la /mnt/Windows/EFI/Gentoo/ total 36381 drwxr-xr-x 2 root root 2048 Jan 26 16:51 . drwxr-xr-x 6 root root 1024 Aug 2 2023 .. -rwxr-xr-x 1 root root 11743360 Dec 13 10:36 bootx64-6.1.67-gentoo.efi -rwxr-xr-x 1 root root 13105984 Feb 18 08:44 bootx64-6.6.13-gentoo.efi -rwxr-xr-x 1 root root 137161 Dec 13 10:36 config-6.1.67-gentoo -rwxr-xr-x 1 root root 140301 Feb 18 08:44 config-6.6.13-gentoo -rwxr-xr-x 1 root root 4615431 Dec 13 10:36 System.map-6.1.67-gentoo -rwxr-xr-x 1 root root 7504974 Feb 18 08:44 System.map-6.6.13-gentoo The /EFI/ubuntu directory has only the GRUB .efi executable in it, because the ubuntu distribution kernel and initramfs is installed in the ubunutu / partition, not in EFI. If you really want to make the EFI partition larger you can use gparted to do this, but you have to be very careful. This is how I have done it whenever I needed to resize Windows partitions: 1. Boot into MSWindows and defragment the drive. Press Shift as you click to shutdown fully the MSWindows OS (to avoid hybrid hybernation). 2. Reboot with gparted Live USB, or with the Gentoo OS. 3. Unmount the EFI partition, if mounted and resize the C:\ drive to make it smaller, in order to release enough space on the right of it, to be able to move it out of the way. Careful you *only* drag the right hand edge of the C: \ partition when you shrink it, toward the left. 3. After you apply the changes move the C:\ partition to the right away from the EFI partition. 4. Apply the change and then resize the EFI partition to a desired size, e.g. 500M. 5. Apply again and next move the C:\ partition to the left. 6. Apply and then resize the C:\ partition to enlarge it. Apply the last change and you're done. NOTE: Do NOT delete any of the MSWindows partitions and do NOT attempt to change their order. If in doubt ask. After you reboot into MSWindows, it will pop up a warning about the C:\ drive filesystem needing checking, click to accept the warning and wait until it finishes checking the filesystem. Enjoy your Gentoo! signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
On Wednesday, 3 April 2024 06:24:53 BST Paul Sopka wrote: > On 02.04.24 21:43, Paul Sopka wrote: > > On 02.04.24 20:50, J. Roeleveld wrote: > >> Did you upgrade GCC recently? > >> If yes, did you follow the gcc-upgrade guide: > >> > >> https://wiki.gentoo.org/wiki/Upgrading_GCC > >> > >> ? > > > > Thank you for your answer Joost. > > > > As far as I know, I didn't upgrade GCC recently. I just rebuilt > > libtool to be sure, but that didn't help. > > > > Nanderty > > I rebuilt with emptytree over night from tty. The system didn't crash, > but it hung up at the first program to use this, media-libs/libjpeg-turbo. In case you haven't done it yet, if you rebuild the toolchain things should hopefully self-correct on your system: emerge --sync emerge -1av sys-devel/binutils emerge -1av --nodeps sys-devel/gcc Use 'gcc-config -l' to check you are using the correct gcc version. emerge -1av sys-libs/glibc emerge -1av dev-build/libtool env-update && source /etc/profile signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] some problems moving to 23.0 profile
On Tuesday, 2 April 2024 07:03:42 BST J. Roeleveld wrote: > On Monday, 1 April 2024 23:46:49 CEST John Covici wrote: > > Hi. Well, I followed the steps in the news item, to move > > todefault/linux/amd64/23.0/desktop/gnome/systemd > > > > and it all worked till it wants me to emerge the whole world file. > > Here is what I get: > > > > emerge --ask --emptytree @world > > > > These are the packages that would be merged, in order: > > > > Calculating dependencies done! > > Dependency resolution took 4.58 s (backtrack: 0/200). > > > > > > !!! Problems have been detected with your world file > > !!! Please run emaint --check world > > > > > > !!! Ebuilds for the following packages are either all > > !!! masked or don't exist: > > www-apps/nextcloud:26.0.10 > > > > emerge: there are no ebuilds to satisfy > > "sys-kernel/gentoo-sources:6.1.69". > > (dependency required by "@kernels" [set]) > > (dependency required by "@selected" [set]) > > (dependency required by "@world" [argument]) > > > > I don't want to unmerge that kernel -- its my backup kernel, so I > > definitely want to keep it. I am using the nextcloud they are > > complaining about , I will upgrade it soon, but I want to keep it for > > now. > > Do you actually need to keep the kernel-sources? > Once the kernel is compiled and you moved the image to /boot/..., you don't > need to keep the sources. > > I also keep an older kernel just in case, but I don't tend to actually keep > the sources around once I have confirmed the new kernel will boot. > > -- > Joost When gentoo-sources are tree-cleaned, it is typically because they have been superseded by later kernel patches to improve security and resolve bugs. Therefore it is usually a 'good idea' to emerge a later kernel when this happens, even if we're talking about a backup kernel. Last week I came upon a similar problem on an old system I was trying to migrate to profile 23.0, only this happened not with my backup but with the running kernel. This PC had not been updated for 5-6 months. It's resource constrained and I didn't want to spend many days updating most of its deprecated packages, only to have to re-emerge them as part of the profile migration. I can't recall if it was the same kernel as John's. During the migration I came across some package (llvm?) which required a more up to date kernel to be able to emerge. This forced me to upgrade the kernel first, before I could continue with the migration. I'm mentioning this since the utility of a backup kernel would be limited when you can't use it to run your software. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] My emerge @preserved-rebuild is wedged. Help, please!
On Monday, 1 April 2024 16:12:51 BST Alan Mackenzie wrote: > Hello, Gentoo. > > I'm trying to do > > # emerge -a @preserved-rebuild > > .. For this purpose, I created a temporary repository, filling it with > ancient ebuilds recovered from /var/db/pkg. I may be missing something, but why are you doing this? Why don't you run @world update first, which will bring your system to a stable state, before you proceed with anything else, e.g. migrating to profile 23.0? signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: [gentoo-dev] Current unavoidable use of xz utils in Gentoo
On Mon, 2024-04-01 at 01:32 +0300, Alexandru N. Barloiu wrote: > https://piaille.fr/@zeno/112185928685603910 > > There's an ENV var you can set that is a kill switch for the whole thing :) > For the part that we found :) The author of the backdoor had commit access to the upstream repository for a long time: https://git.tukaani.org/?p=xz.git;a=search;s=Jia+Tan;st=author Personally I would be skeptical of running any version of any package that he has touched.
Re: [gentoo-user] Re: [gentoo-dev] Current unavoidable use of xz utils in Gentoo
On Sun, 2024-03-31 at 18:19 -0400, Michael Orlitzky wrote: > > The old version will show up as liblzma.so.5.6.1. Restart anything that > uses it. Or liblzma.so.5.6.0
Re: [gentoo-user] Re: [gentoo-dev] Current unavoidable use of xz utils in Gentoo
On Sun, 2024-03-31 at 12:04 -0400, Rich Freeman wrote: > > It is not necessary to rebuild anything, unless you're doing something > so unusual that you'd already know the answer to the question. > You should probably reboot afterwards though. For a more fine-grained approach, you can check for running processes that still use the old library with something like, root # grep liblzma /proc/*/maps The old version will show up as liblzma.so.5.6.1. Restart anything that uses it.
Re: [gentoo-user] Re: [gentoo-dev] Current unavoidable use of xz utils in Gentoo
On Sunday, 31 March 2024 13:33:20 BST Rich Freeman wrote: > (moving this to gentoo-user as this is really getting off-topic for -dev) Thanks for bringing this to our attention Rich. Is downgrading to app-arch/xz-utils-5.4.2 all that is needed for now, or are we meant to rebuilding any other/all packages, especially if we rebuilt our @world only a week ago as part of the move to profile 23.0? signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] merge-usr and SPF implementations
On Friday, 29 March 2024 19:06:45 GMT Stefan Schmiedl wrote: > > > Michael wrote on Friday, 29. März 2024 18:53: > > My guess and this is only a guess, is the two binaries are in separate > > subdirectories of /usr and therefore there shouldn't be a problem. Before > > you progress with this you could raise a bug, or try to seek a dev's > > advice on IRC. A fresh backup before you make any changes is definitely > > a good idea. > Quoting the wiki page: > "In addition, the script applies the "sbin merge" at the same time > where /sbin and /usr/sbin are both actually merged to /usr/bin." So while > it is not a problem with split-usr, those two packages will clash with > merged-usr. You're right, they will be in the same subdirectory! ~ $ ls -la /usr total 390 drwxr-xr-x 11 root root 3452 Mar 24 08:52 . drwxr-xr-x 16 root root 4096 Mar 26 15:43 .. drwxr-xr-x 3 root root 118784 Mar 29 16:09 bin drwxr-xr-x 369 root root 53248 Mar 29 13:58 include drwxr-xr-x 34 root root 4096 Mar 24 08:57 lib drwxr-xr-x 88 root root 249856 Mar 29 13:58 lib64 drwxr-xr-x 17 root root 3452 Mar 29 16:09 libexec drwxr-xr-x 6 root root 3452 Jul 23 2023 local lrwxrwxrwx 1 root root 3 Mar 24 08:52 sbin -> bin drwxr-xr-x 272 root root 8192 Mar 29 13:58 share drwxr-xr-x 3 root root 3452 Mar 19 15:25 src drwxr-xr-x 6 root root 3452 Jul 23 2023 x86_64-pc-linux-gnu > https://bugs.gentoo.org/928140 > > Thanks, > s. The bug report should hopefully resolve these. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] merge-usr and SPF implementations
On Friday, 29 March 2024 16:05:29 GMT Stefan Schmiedl wrote: > Greetings. > > After updating profiles, I decided to try switching to merged-user, too, > following the wiki page at https://wiki.gentoo.org/wiki/Merge-usr > > One server reported during the dry run: > ERROR: Conflict for file '/usr/sbin/spfd': [Errno 17] File exists: > '/usr/bin/spfd' > > # equery belongs /usr/bin/spfd > * Searching for /usr/bin/spfd ... > mail-filter/libspf2-1.2.11 (/usr/bin/spfd) > # equery belongs /usr/sbin/spfd > * Searching for /usr/sbin/spfd ... > dev-perl/Mail-SPF-2.9.0-r3 (/usr/sbin/spfd) > > That does put me in a bit of a pickle, as both are active dependencies > pulled in by essential software: > > # emerge -cav Mail-SPF > > Calculating dependencies ... done! >dev-perl/Mail-SPF-2.9.0-r3 pulled in by: > mail-filter/spamassassin-4.0.0-r4 requires dev-perl/Mail-SPF > > >>> No packages selected for removal by depclean > > # emerge -cav libspf2 > > Calculating dependencies... done! >mail-filter/libspf2-1.2.11 pulled in by: > mail-filter/opendmarc-1.4.1.1-r5 requires mail-filter/libspf2 > mail-mta/exim-4.97.1-r5 requires >=mail-filter/libspf2-1.2.5-r1 > > > What is the recommended way to proceed in this scenario? > > Regards, > Stefan My guess and this is only a guess, is the two binaries are in separate subdirectories of /usr and therefore there shouldn't be a problem. Before you progress with this you could raise a bug, or try to seek a dev's advice on IRC. A fresh backup before you make any changes is definitely a good idea. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New profiles 23.0
On Tuesday, 26 March 2024 13:01:16 GMT Michael wrote: > On Tuesday, 26 March 2024 10:32:05 GMT William KENWORTHY wrote: > > I have a question about binaries and the new profile: I have a number of > > almost identical architectures that I build binaries for and share across > > the similar sytems e.g. arm, aarch64, amd64 etc. > > > > Is deleting the bin host storage (rm -rf ) enough on the > > buildhost so I can share/use the binaries for the "emerge -e" on the > > other hosts? Or does it have to be a native emerge? BillK > > I'm about to try this out in the next couple of days. I will clean binpkgs > on both host and guest, transfer the freshly compile packages with the 23.0 > profile to the guest and then emerge them there as binaries, but following > the profile migration guide, i.e. toolchain first followed by world. > Should things break I'll report back. All went according to plan. Cleared out all files in binpks on both build-host and the guest. Carried out the steps for the migration to profile 23.0 on the host, transferred binaries to the guest, migrated guest to profile 23.0 using binaries. Then merged /usr on both. All is good following this upgrade, but as always YMMV. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] openrc - parallel start - timeouts
On Friday, 29 March 2024 13:30:23 GMT J. Roeleveld wrote: > Hi All, > > To improve the bootup time of my server, I want to enable "parallel", > however, I run into an issue where some of the services take longer than 60 > seconds to start, causing this to be classed as "not started", which then > kills the entire boot sequence. > > Boot, obviously, goes fine with parallel off, but I am certain I can reduce > the boot time significantly using parallel. I also spent quite some time > checking dependencies between the services to ensure they are all present. > > Now, how do I configure a longer timeout? Preferably on a per-service basis, > but at the very least, globally. > > Many thanks in advance, > > Joost Take a look in /etc/rc.conf, the section titled "SERVICE CONFIGURATION VARIABLES". signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Issue with new hardened profiles 23.0
On Thursday, 28 March 2024 10:23:29 GMT Matthias Hanft wrote: > J. Roeleveld wrote: > > Do you use the binary packages supplied by Gentoo? > > Or all local-compiled? > > All local-compiled, with the exemption of "monster-packages" which > would take hours or even days to compile (e.g. rust - here I use > "dev-lang/rust-bin" instead). > > I don't even have any of /etc/portage/binrepos.conf or /var/cache/binpkgs/ > (and "emerge --getbinpkg ..." displays a warning that it won't work). > > -Matt You mentioned you have created your custom profile with hardened and desktop - could this action have inadvertently mixed merged with split /usr profiles in your system? What does 'tree -L 1 /' show on your server? signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New profiles 23.0
On Tuesday, 26 March 2024 15:21:32 GMT Walter Dnes wrote: > I'm AMD64 stable OpenRC. I got tired of dicking around resizing > partitions years ago, so I have all data and binaries in one honking > big partition. Also separate partitions for UEFI and swap. I assume > my system is already "merged-usr". Current profile... > > [12] default/linux/amd64/17.1/no-multilib (exp) * > > I just ran "emerge --sync" and got the profile news item. So do I > update world and then update profile? No! Please check the migration instructions for profile 23 as provided in the news item. You must follow the steps suggested in the order they are written *and* you must select the correct profile. The profile you show above is split-usr, which was the default. This is the traditional split-usr linux fs which has / bin, /sbin, /lib and /lib64 as discrete directories under /, e.g.: ~ # tree -L 1 / / ├── bin ├── boot ├── dev ├── etc ├── home ├── lib ├── lib64 ├── lost+found ├── media ├── mnt ├── opt ├── proc ├── root ├── run ├── sbin ├── sys ├── tmp ├── usr └── var 20 directories, 0 files The merged-usr fs structure has the aforementioned directories set as symlinks under /usr, e.g.: ~ # tree -L 1 / / ├── bin -> usr/bin ├── boot ├── dev ├── etc ├── home ├── lib -> usr/lib ├── lib64 -> usr/lib64 ├── media ├── mnt ├── opt ├── proc ├── root ├── run ├── sbin -> usr/bin ├── sys ├── tmp ├── usr ├── var └── BackUps 20 directories, 0 files Consequently, in following the migration instructions methodically and assuming you have a split-usr fs layout, you will need to change profile to: [49] default/linux/amd64/23.0/split-usr/no-multilib (stable) rebuild your toolchain in the order and in the way suggested in the news item, then emerge @world with '--emptytree'. If you want to convert the fs structure to a merged-usr layout after the migration to your new profile follow the instructions here: https://wiki.gentoo.org/wiki/Merge-usr Assuming the --dryrun does not come up with any problems you then have to run emerge -uaNDv world, which will spit out which packages are affected by it - e.g. on one of my systems I see these candidates: Dependency resolution took 35.09 s (backtrack: 0/20). [ebuild R] sys-apps/baselayout-2.14-r2::gentoo USE="-build (-split- usr*)" 0 KiB [ebuild R] dev-libs/lzo-2.10:2::gentoo USE="-examples (-split-usr*) - static-libs" ABI_X86="(64) -32 (-x32)" 0 KiB [ebuild R] app-alternatives/bzip2-1::gentoo USE="reference -lbzip2 - pbzip2 (-split-usr*)" 0 KiB [ebuild R] app-alternatives/tar-0::gentoo USE="gnu -libarchive (-split- usr*)" 0 KiB [ebuild R] app-alternatives/gzip-1::gentoo USE="reference -pigz (- split-usr*)" 0 KiB [ebuild R] app-alternatives/cpio-0::gentoo USE="gnu -libarchive (- split-usr*)" 0 KiB [ebuild R] app-alternatives/awk-4::gentoo USE="gawk -busybox -mawk - nawk (-split-usr*)" 0 KiB [ebuild R] sys-apps/coreutils-9.4-r1::gentoo USE="acl nls openssl xattr -caps -gmp -hostname -kill -multicall (-selinux) (-split-usr*) -static -test - vanilla -verify-sig" 0 KiB [ebuild R] sys-libs/libxcrypt-4.4.36:0/1::gentoo USE="(compat) (system) -headers-only (-split-usr*) -static-libs -test" ABI_X86="32 (64) (-x32)" 0 KiB [ebuild R] sys-apps/systemd-utils-254.8::gentoo USE="acl kmod tmpfiles udev -boot -kernel-install -secureboot (-selinux) (-split-usr*) -sysusers - test -ukify" ABI_X86="(64) -32 (-x32)" PYTHON_SINGLE_TARGET="python3_11 - python3_10 -python3_12" 0 KiB [ebuild R] sys-libs/ncurses-6.4_p20230401:0/6::gentoo USE="cxx gpm stack-realign (tinfo) -ada -debug -doc -minimal -profile (-split-usr*) - static-libs -test -trace -verify-sig" ABI_X86="(64) -32 (-x32)" 0 KiB [ebuild R] dev-libs/libusb-1.0.26:1::gentoo USE="udev -debug -doc - examples (-split-usr*) -static-libs -test" ABI_X86="(64) -32 (-x32)" 0 KiB [ebuild R] sys-process/procps-3.3.17-r2:0/8::gentoo USE="elogind kill ncurses nls (unicode) -modern-top (-selinux) (-split-usr*) -static-libs - systemd -test" ABI_X86="(64) -32 (-x32)" 0 KiB [ebuild R] sys-apps/shadow-4.14.2:0/4::gentoo USE="acl nls pam xattr - audit -cracklib (-selinux) -skey (-split-usr*) -su -systemd -verify-sig" 0 KiB [ebuild R] net-firewall/iptables-1.8.10:0/1.8.3::gentoo USE="-conntrack -netlink -nftables -pcap (-split-usr*) -static-libs -test" 0 KiB [ebuild R] net-mail/mailutils-3.15::gentoo USE="clients gdbm ipv6 nls pam ssl threads -berkdb -bidi -emacs -guile -kerberos -kyotocabinet -ldap - mysql -postgres -python -sasl -servers (-split-usr*) -static-libs -tcpd - tokyocabinet" PYTHON_SINGLE_TARGET="python3_11 -python3_10" 0 KiB Total: 16 packages (16 reinstalls), Size of downloads: 0 KiB HTH. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New profiles 23.0
On Tuesday, 26 March 2024 10:32:05 GMT William KENWORTHY wrote: > I have a question about binaries and the new profile: I have a number of > almost identical architectures that I build binaries for and share across > the similar sytems e.g. arm, aarch64, amd64 etc. > > Is deleting the bin host storage (rm -rf ) enough on the buildhost > so I can share/use the binaries for the "emerge -e" on the other hosts? Or > does it have to be a native emerge? BillK I'm about to try this out in the next couple of days. I will clean binpkgs on both host and guest, transfer the freshly compile packages with the 23.0 profile to the guest and then emerge them there as binaries, but following the profile migration guide, i.e. toolchain first followed by world. Should things break I'll report back. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Stage-3 and profile 23.x
On Tuesday, 26 March 2024 00:54:26 GMT Peter Humphrey wrote: > On Monday, 25 March 2024 23:14:50 GMT Michael wrote: > > On Monday, 25 March 2024 21:48:24 GMT Peter Humphrey wrote: > > > On Monday, 25 March 2024 16:52:19 GMT Michael wrote: > > > > The default OpenRC installation now assumes a merged-usr fs structure > > > > - > > > > therefore make sure you select the appropriate profile in a new > > > > installation. > > > > > > I was wondering about that. Now that we have 23.0 in place, are we meant > > > to > > > change to merged-usr? Should I run the eponymous script? > > > > You can, if you want to. I've installed sys-apps/merge-usr and ran it on > > my OpenRC system, after I completed the migration to profile 23.0. It > > didn't take any time at all: > > > > https://wiki.gentoo.org/wiki/Merge-usr > > I'd want a good reason to do so, as I can't imagine it being reversed easily > - I'd need to keep a backup of /bin, /usr and so on which I could restore > if necessary, then run emerge -e @world and save those directories again. > Not worth the candle. > > There being no foreseeable prospect of the systemd bandwagon picking me up > on its way by, I think I'll stick to what I know*. > > * For some vague approximation to 'know'. :) The reason for a unified filesystem layout is to align Linux with Unix (Open Solaris) and increase compatibility between distributions, which in turn makes it easier to install/run various tools with hardcoded paths. It also makes it easier to separate OS Vs user binaries, while keeping the former read only, to allow various guest OS instances to use the same host OS /usr as read only, without treading over each other toes. I can't see why the average non- systemd Linux desktop user will want to rush into this change for their personal computing needs. Regardless of personal choices at this stage, the direction of travel is towards a unified layout. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Question about emerge sync and where it all goes.
On Tuesday, 26 March 2024 00:37:31 GMT Dale wrote: > Michael wrote: > > On Monday, 25 March 2024 02:58:21 GMT Dale wrote: > >> I did this with the following command earlier. > >> > >> rsync -av --progress --delete /var/cache/portage/tree/* > >> /backup/gentoo-build/var/cache/portage/tree/ > > > > Your syntax for the source tree will fail to copy a couple files > > immediately under /var/cache/portage/tree/ which start with "." > > > > It would be better if you used: > > > > /var/cache/portage/tree /backup/gentoo-build/var/cache/portage/tree > > I edited that in my little script. The locations with rsync can be > tricky. Each way that one can use gives a slightly different execution. Oops! Scratch that - I was wrong. Sorry! This is what will work: /foo/ /backup/foo will copy the contents of source /foo into destination /backup/foo, without copying the top level directory /foo itself. This way both /foo at source and /backup/foo at destination will have identical content. If you omit a trailing slash you'll copy the source top level directory itself and will get: /backup/foo/foo/... which NOT what you're after. Hope this helps. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Stage-3 and profile 23.x
On Monday, 25 March 2024 21:48:24 GMT Peter Humphrey wrote: > On Monday, 25 March 2024 16:52:19 GMT Michael wrote: > > The default OpenRC installation now assumes a merged-usr fs structure - > > therefore make sure you select the appropriate profile in a new > > installation. > I was wondering about that. Now that we have 23.0 in place, are we meant to > change to merged-usr? Should I run the eponymous script? You can, if you want to. I've installed sys-apps/merge-usr and ran it on my OpenRC system, after I completed the migration to profile 23.0. It didn't take any time at all: https://wiki.gentoo.org/wiki/Merge-usr signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New profiles 23.0
On Monday, 25 March 2024 17:37:40 GMT Jacques Montier wrote: > Le lun. 25 mars 2024 à 18:18, Michael a écrit : > > Therefore, you can fetch binaries from the mirrors when these have the > > same > > configuration as your locally compiled software to make the whole upgrade > > complete faster, but it remains a personal choice. > > Thanks Michael for your response, > but how could i know if one package has the same configuration as my > locally compiled software and if this one is as much tested as the > source-based package ? > > -- > Jacques Montier When the packages on the Gentoo binhost mirror have been compiled with different USE flags to your choices, these packages will not be fetched from the mirror but compiled locally. Have a look here for more details: https://wiki.gentoo.org/wiki/Gentoo_Binary_Host_Quickstart signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New profiles 23.0
On Monday, 25 March 2024 17:00:18 GMT Jacques Montier wrote: > Le lun. 25 mars 2024 à 15:41, Peter Humphrey a > > écrit : > > On Saturday, 23 March 2024 17:42:29 GMT Michael wrote: > > > I suggest it would be best to take heed of the devs hard work and read > > > > the > > > > > instructions they have provided instead of winging it: > > > > > > https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_instructions > > > > Of course I was doing that, but from the news item. My problem was that I > > wasn't reading straight. > > > > (I think I had a form of covid last month, and it's left a few loose ends > > - > > mostly in my brain!) > > > > -- > > Regards, > > Peter. > > Hello all, > > I updated my profile from amd64/17.1/desktop/systemd/merged-usr to > amd64/23.0/desktop/systemd. > I followed the quite clear instructions without any issue. > With emerge --ask --emptytree @world, i had to recompile 1400 packages, so > it took all night long !!! > Some scare when the package 1201 failed and everything stopped (i forgot > the keep-going option). > Nevertheless, I rebooted and everything works fine ! Whew !!! > > What i understand is that Gentoo is now mostly based on binary packages. > The sources are now the exception. > It's the opposite of what Gentoo was before... Right ? > > Regards, > > -- > Jacques Not really, Gentoo is still based on compiling from source - for those who want to optimise/customise their systems. More recently pre-compiled binary packages which suit generic hardware and software configurations are also made available for those who want to get something up and running quickly. This makes Gentoo similar to other binary distributions. The command syntax in the instructions included "--getbinpkg" to download pre- built binaries, but with this note: "In case you are already familiar with binary packages, you should be able to add '--getbinpkg' to the emerge calls to speed things up. The use of binary packages is completely optional though, and also not as much tested as the source-based upgrade path yet." Therefore, you can fetch binaries from the mirrors when these have the same configuration as your locally compiled software to make the whole upgrade complete faster, but it remains a personal choice. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Stage-3 and profile 23.x
On Monday, 25 March 2024 15:30:41 GMT Peter Humphrey wrote: > Hello list, > > It would be good if a stage-3 tarball were available with profile 23.x built > in. Sooner or later someone will want to build a new system with such a > profile. > > Is this in the offing? It is already there; e.g. https://mirror.bytemark.co.uk/gentoo/releases/amd64/autobuilds/ 20240324T164906Z/stage3-amd64-desktop- openrc-20240324T164906Z.tar.xz.CONTENTS.gz >From what I recall make.profile 23.0 has been available for a while now, albeit it was previously shown as experimental (exp). NOTE: The default OpenRC installation now assumes a merged-usr fs structure - therefore make sure you select the appropriate profile in a new installation. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New profile, gcc-13.2.1_p20240210 fails to build. ATTN: Peter Humphrey.
On Monday, 25 March 2024 07:04:57 GMT Dale wrote: > Paul Colquhoun wrote: > > I had the gcc compile fail, but was successful after removing the "objc" > > use flag. > > > > Unfortunately, it seemd to be required by app-arch/unar during step 16, > > rebuild world. > > > > I'm re-enbleing it and will see how it all goes. > > Here is my update. I wanted to skip the system update and change > profiles first. Then do the emerge -e world which would also update > anything that was new as well. I'd only have to compile once tho. > Well, that may have caused a problem. It may work for some but it > didn't here. I first had to do my usual emerge -auDN world and get a > clean run. I had one build to fail, had to work on that. Anyway, where > it says update first, it is best to do that. It might work if you > don't, might not. I'm trying to do the same on an old, slow PC which had not been touched for a few months now. Most packages would need updating anyway and didn't fancy spending a week to get it up to date before changing the profile, only to rebuild everything once more. We'll see how it goes ... > Overall, the devs did a really good job with the instructions. Just > have to update first as it says. It works better. ;-) A big thank you to the devs for their effort to make our life easier! signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Question about emerge sync and where it all goes.
On Monday, 25 March 2024 02:58:21 GMT Dale wrote: > Howdy, > > I've mentioned before that I build my packages in a chroot. I have a OS > copy on a separate drive. I do this because of the long compile times > of some packages. On occasion tho, I catch the tree in a bad place. > Some conflict or other happens and I need to sync again to get fixes > etc. Given my process tho, I don't want to sync the chroot without also > syncing my main system because the two will not be in sync and I'll lose > my update since it deletes files as well including any updates I did > emerge successfully. I need the two to be identical. So, I'd like to > sync my main system and then copy the new data over to the chroot > without copying the rest of the OS. What you do is duplicating effort and storage space with questionable benefit, besides warming up your room. I think it would be more efficient if you used the same /var/cache/distfiles and /var/db/repos/ filesystems on both installations. This way you'd sync once and then download any source files once only. However, an even more optimised solution would be to compile packages once in your chrooted fs with the '--buildpkg y' option and then emerge these as binary packages from /var/cache/binpkgs/ in your production OS. An overnight emerge in the chrooted OS will take only a few minutes on the production system. > I did this with the following command earlier. > > rsync -av --progress --delete /var/cache/portage/tree/* > /backup/gentoo-build/var/cache/portage/tree/ Your syntax for the source tree will fail to copy a couple files immediately under /var/cache/portage/tree/ which start with "." It would be better if you used: /var/cache/portage/tree /backup/gentoo-build/var/cache/portage/tree > As you can see, my tree location is not the default. It is located at > /var/cache/portage/tree/. It's the same on the chroot obviously. Would > the above command copy all the needed files/directories over that it > needs after a emerge sync or is there more to it? The reason I think it > needs more, when I tried to do the usual emerge -aukDN world on my main > system, it wanted to emerge more packages than the chroot did. I > suspect there is more to it than just the tree directory. > > Anyone have the details on this? Anyone know what other > files/directories need to be copied over as well? > > Thanks. > > Dale > > :-) :-) Did you diff /var/lib/portage/world between the two systems to see what differences may be there? I can think of a hypothetical case where the chrooted fs may have already emerged build time dependencies, e.g. if some emerge failed and then you fixed/restarted it a number of times, but the production system would not yet have such build time dependencies installed. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New profiles 23.0
On Sunday, 24 March 2024 18:31:37 GMT Björn Fischer wrote: > Hi folks, > > my current profile is default/linux/amd64/17.1, but I already migrated > to merged-usr some while ago (I know, that is not supported, really). > > Any advice how to migrate to 23.0? > > Cheers, > Björn The default OpenRC 23.0 profiles now use merged-usr. So select a flavour to suit your needs which does NOT show split-usr. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New profile, gcc-13.2.1_p20240210 fails to build. ATTN: Peter Humphrey.
On Saturday, 23 March 2024 21:28:27 GMT Dale wrote: > Michael wrote: > > On Saturday, 23 March 2024 20:45:03 GMT Dale wrote: > >> I saw where Peter mentioned in another thread gcc failing with no error > >> message for him. This could be related. A solution to this may help > >> more than just me. I'm not sure how to diagnose a failure when it gives > >> no real error. Heck, having a error sometimes isn't much help. :/ I > >> might add, the errors listed above didn't stop the compile until close > >> to the end. It did seem to ignore them since it compiled a good while > >> afterwards. I'm including in case those errors lead to the failure > >> later on. They could be nothing or may be a clue. > >> > >> Open to ideas. > >> > >> Dale > >> > >> :-) :-) > > > > Hmm ... my gcc is failing on one of my installations, with no error ... > > after it built successfully once already, as part of the initial > > toolchain update.> > > :-/ > > > > OK, I'm out of ideas too. May have to sleep on this and look at it again > > tomorrow. > > Nice to know I'm not alone. I forgot to mention, it wanted to update > glibc first. The news item said NOT to let it do that and use the > --nodeps option instead. So, the command I used had that option. I've > since restarted it, just in case it finishes. I'll post back if it > does. I find it odd that it builds fine one time but fails on others. > Strange things happen tho. > > Dale > > :-) :-) There's a new patch for gcc. You need to follow the guide as you did, then resync portage to fetch the latest ebuild for gcc, before you start the emerge --emptytree world. This is how I managed to get ggc to build after previous attempts with 'no error' failures. Hope this works for you. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New profile, gcc-13.2.1_p20240210 fails to build. ATTN: Peter Humphrey.
On Saturday, 23 March 2024 20:45:03 GMT Dale wrote: > Howdy, > > I'm doing this in a chroot. This is *not* my live system. This is the > mount info, in case it matters. > > > root@fireball / # mount | grep gentoo > /proc on /backup/gentoo-build/proc type proc (rw,relatime) > sysfs on /backup/gentoo-build/sys type sysfs > (rw,nosuid,nodev,noexec,relatime) > debugfs on /backup/gentoo-build/sys/kernel/debug type debugfs > (rw,nosuid,nodev,noexec,relatime) > fusectl on /backup/gentoo-build/sys/fs/fuse/connections type fusectl > (rw,nosuid,nodev,noexec,relatime) > none on /backup/gentoo-build/sys/fs/cgroup type cgroup2 > (rw,nosuid,nodev,noexec,relatime,nsdelegate) > devtmpfs on /backup/gentoo-build/dev type devtmpfs > (rw,nosuid,noexec,size=10240k,nr_inodes=4104300,mode=755) > devpts on /backup/gentoo-build/dev/pts type devpts > (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) > tmpfs on /backup/gentoo-build/dev/shm type tmpfs (rw,nosuid,nodev,noexec) > shm on /backup/gentoo-build/dev/shm type tmpfs > (rw,nosuid,nodev,noexec,relatime) > mqueue on /backup/gentoo-build/dev/mqueue type mqueue > (rw,nosuid,nodev,noexec,relatime) > /run on /backup/gentoo-build/run type tmpfs (rw,relatime) > tmpfs on /backup/gentoo-build/run type tmpfs (rw,size=262144k,mode=755) > root@fireball / # > > > I've following the news item with this. This is early and already it > has issues. Maybe switching is a bit early yet?? Anyway, this is what > gcc fails with: > > > make[3]: Entering directory > '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux- > gnu/32/libstdc++-v3/include' echo timestamp > stamp-pb > echo timestamp > stamp-host > make[3]: [Makefile:1820: x86_64-pc-linux-gnu/bits/largefile-config.h] > Error 1 (ignored) > echo 0 > stamp-namespace-version > echo 1 > stamp-visibility > echo 1 > stamp-extern-template > echo 1 > stamp-dual-abi > echo 1 > stamp-cxx11-abi > echo 1 > stamp-allocator-new > echo 'define _GLIBCXX_USE_FLOAT128 1' > stamp-float128 > sed -e '/^#pragma/b' \ > > > And further down, this: > > > make[3]: Leaving directory > '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux- > gnu/32/libstdc++-v3/include' config.status: executing libtool commands > config.status: executing generate-headers commands > make[3]: Entering directory > '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux- > gnu/libstdc++-v3/include' echo timestamp > stamp-pb > echo timestamp > stamp-host > make[3]: [Makefile:1819: x86_64-pc-linux-gnu/bits/largefile-config.h] > Error 1 (ignored) > make[3]: [Makefile:1820: x86_64-pc-linux-gnu/bits/largefile-config.h] > Error 1 (ignored) > echo 0 > stamp-namespace-version > echo 1 > stamp-visibility > echo 1 > stamp-extern-template > echo 1 > stamp-dual-abi > echo 1 > stamp-cxx11-abi > echo 1 > stamp-allocator-new > echo 'define _GLIBCXX_USE_FLOAT128 1' > stamp-float128 > > > And even further down: > > > sed -e 's/\(UNUSED\)/_GLIBCXX_\1/g' \ > -e 's/\(GCC[ABCDEFGHIJKLMNOPQRSTUVWXYZ_]*_H\)/_GLIBCXX_\1/g' \ > -e 's/SUPPORTS_WEAK/__GXX_WEAK__/g' \ > -e 's/\([ABCDEFGHIJKLMNOPQRSTUVWXYZ_]*USE_WEAK\)/_GLIBCXX_\1/g' \ > -e 's,^#include "\(.*\)",#include ,g' \ > < > /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/libstdc > ++-v3/../libgcc/gthr-posix.h > > x86_64-pc-linux-gnu/bits/gthr-default.h > > make[3]: Leaving directory > '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux- > gnu/32/libstdc++-v3/include' config.status: executing libtool commands > config.status: executing generate-headers commands > make[3]: Entering directory > '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux- > gnu/libstdc++-v3/include' echo timestamp > stamp-pb > echo timestamp > stamp-host > make[3]: [Makefile:1819: x86_64-pc-linux-gnu/bits/largefile-config.h] > Error 1 (ignored) > make[3]: [Makefile:1820: x86_64-pc-linux-gnu/bits/largefile-config.h] > Error 1 (ignored) > echo 0 > stamp-namespace-version > echo 1 > stamp-visibility > echo 1 > stamp-extern-template > echo 1 > stamp-dual-abi > echo 1 > stamp-cxx11-abi > echo 1 > stamp-allocator-new > echo 'define _GLIBCXX_USE_FLOAT128 1' > stamp-float128 > > > Very close to the end, this: > > > Makefile:901: warning: ignoring old recipe for target 'all-multi' > make[8]: Leaving directory > '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux- > gnu/32/libatomic' make[8]: Entering directory > '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux- > gnu/32/libatomic' true DO=install multi-do # make > /bin/mkdir -p > '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib' > /bin/sh ./libtool --mode=install /usr/bin/install -c libatomic.la > '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib' > libtool: install: /usr/bin/install -c .libs/libatomic.so.1.2.0 >
Re: [gentoo-user] New profiles 23.0
On Saturday, 23 March 2024 18:29:58 GMT ralfconn wrote: > Il 23/03/24 18:42, Michael ha scritto: > > I suggest it would be best to take heed of the devs hard work and > > read the > > > instructions they have provided instead of winging it: > > > > https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_instructions > > I'm currently running a local merged profile: > > # cat /var/db/repos/local/profiles/no-multilib-hardened-desktop/parent > gentoo:default/linux/amd64/17.1/no-multilib/hardened > gentoo:targets/desktop > > $ euse -a | grep usr > split-usr [+ D F ] > > I suppose that before step 3 of the wiki I'd need to create a new local > merged profile, e.g.: > > #cat > /var/db/repos/local/profiles/23.0-split-usr-no-multilib-hardened-desktop/par > ent gentoo:default/linux/amd64/23.0/split-usr/no-multilib/hardened > gentoo:targets/split-usr/desktop > > Does that make sense? > > thanks > > raf Update portage and check the profiles offered by 'eselect profile list'. For example, I can see: [51] default/linux/amd64/23.0/split-usr/no-multilib/hardened (stable) which should provide what you're after. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New profiles 23.0
On Saturday, 23 March 2024 17:33:17 GMT Dale wrote: > Peter Humphrey wrote: > > On Saturday, 23 March 2024 15:08:56 GMT Peter Humphrey wrote: > >> On Saturday, 23 March 2024 14:59:15 GMT Peter Humphrey wrote: > >>> Hello list, > >>> > >>> Has anyone tried the profile upgrade that was notified today? I tried it > >>> just now on a small rescue system and it failed on installing the first > >>> binary package, complaining that my disk layout was split-usr. > >>> > >>> My /var is on a separate partition, for easy of file recovery, but /usr > >>> is > >>> not. Is this the cause of the problem? > >> > >> Please ignore that. Three seconds later I realised what I should have > >> done: run emerge-usr first. > > > > No, that's wrong too. I need to do a bit of head-scratching. > > I just did my weekly sync. I'm currently on this profile. > > > [8] default/linux/amd64/17.1/desktop/plasma (stable) * > > > To find the profile I want to upgrade to, I look for the same name but > with the added split-usr added, for us old fuggys who still do things > the OLD way. ;-) > > > [48] default/linux/amd64/23.0/split-usr/desktop/plasma (exp) > > > If one uses systemd, look for the same thing as old but with systemd. > Same with no-multilib or some of the other options. Basically, just > look for the same as old but with the new bits you need. > > I have a spare hard drive that I do my updates on. It's like a stage 4 > thing that I update with a script, if you can call it that, right after > syncing. I chroot in and do my updates there. If anything goes wrong, > I just reset back to the stage 4 and try again if worse comes to worse. > Once done, I copy the packages over to my main system and add -k to > emerge. It makes updates a lot faster and stable. Sometimes during KDE > updates, things can get out of sync and things stop working. Having > packages that take a long time to compile makes that worse. The qt > package, LOo, Firefox etc etc. You can be sure I'm going to do that > with this update. It's gonna take long enough to do the -k bit much > less the actual compile part. I seem to recall we have to do a emerge > -e world with this. o_O > > I hope that helps you pick the correct one. I been concerned about the > switch too. It's easy to mess up something. > > Dale > > :-) :-) I suggest it would be best to take heed of the devs hard work and read the instructions they have provided instead of winging it: https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_instructions signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New profiles 23.0
On Saturday, 23 March 2024 15:08:56 GMT Peter Humphrey wrote: > On Saturday, 23 March 2024 14:59:15 GMT Peter Humphrey wrote: > > Hello list, > > > > Has anyone tried the profile upgrade that was notified today? I tried it > > just now on a small rescue system and it failed on installing the first > > binary package, complaining that my disk layout was split-usr. > > > > My /var is on a separate partition, for easy of file recovery, but /usr is > > not. Is this the cause of the problem? > > Please ignore that. Three seconds later I realised what I should have done: > run emerge-usr first. The advice on the e-news item is to switch to the new 23.0 profile first using the same fs structure you currently have and then to proceed with the migration to a merged-usr. Therefore if you have a split usr fs structure, you need to select a 'split- usr' 23.0 profile. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] gnucash will not generate a report
On Monday, March 11, 2024, Thelma wrote: > I tried to generate a report in GnuCash but I'm getting and empty page. > > Can anybody confirm! > > -- > Thelma > > -- Kind regards, Mike
Re: [gentoo-user] Re: How to set up drive with many Linux distros?
On Friday, 8 March 2024 23:24:02 GMT Grant Edwards wrote: > On 2024-02-22, Grant Edwards wrote: > > For many years, I've used a hard drive on which I have 8-10 Linux > > distros installed -- each in a separate (single) partition. > > > > [...] > > > > Is there an easier way to do this? > > After some additional studying of UEFI and boot managers like rEFInd, > I decided that my current approach was still the easiest method. I did > switch from DOS to GPT disklabel (I bricked my old drive tring to > update the firmware, so I had to start over anyway). > > In case anybody is interested in the gory details, I documented my > scheme and the helper shell scripts at > > https://github.com/GrantEdwards/Linux-Multiboot Thank you Grant for taking time to share your clear and well structured write up, what with helpful scripts and all! Its easy to follow and should help others, hopefully before they discover belatedly many distro installers can mess up a multiboot scheme, if they don't step in to keep things in check. Perhaps I'm picking up on semantics, but shouldn't this sentence: "... The gap between the DOS disklabel and the first partition" read: "The gap between the MBR and the first partition"? I'm saying this because the MBR in sector 0 contains the bootstrap code (446 bytes), the partition table (a.k.a. DOS disklabel 4x16 bytes) and the boot sector signature (2 bytes). On MBR partitioned disks the core.img is stored after the MBR, in sector 1 onward. Your next paragraph pointed out something which I hadn't considered at any length. Namely, the installation of GRUB's boot.img in a MBR or VBR also hardcodes in a block list format the location of the first sector where the core.img is stored and more importantly, the physical position of this sector can be altered both by COW fs (and by the wear levelling firmware of flash storage devices). I had assumed both the COW fs and/or the flash controller will in both cases translate any physical data position to the logical layer and presented this to inquiring software. Have you actually tried using btrfs as a distro's root fs to see if the VBR installed GRUB boot.img will ever lose access to the core.img? signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] AMD microkernel update failing (trying to patch zenbleed)
On Sunday, 3 March 2024 19:14:23 GMT Daniel Frey wrote: > Hi all, > > I've always had problems updating the microcode for my AMD processor. I > have various other Intel-based PCs and this has never been an issue. > > I have confirmed it's not updating: > > > ~ # dmesg | grep -i microcode > [0.201619] Zenbleed: please update your microcode for the most > optimal fix > [0.748482] microcode: CPU1: patch_level=0x08701030 > [0.748482] microcode: CPU0: patch_level=0x08701030 > [0.748484] microcode: CPU3: patch_level=0x08701030 > [0.748485] microcode: CPU5: patch_level=0x08701030 > [0.748485] microcode: CPU4: patch_level=0x08701030 > [0.748486] microcode: CPU6: patch_level=0x08701030 > [0.748486] microcode: CPU7: patch_level=0x08701030 > [0.748487] microcode: CPU8: patch_level=0x08701030 > [0.748488] microcode: CPU9: patch_level=0x08701030 > [0.748488] microcode: CPU10: patch_level=0x08701030 > [0.748488] microcode: CPU11: patch_level=0x08701030 > [0.748491] microcode: CPU12: patch_level=0x08701030 > [0.748491] microcode: CPU13: patch_level=0x08701030 > [0.748492] microcode: CPU14: patch_level=0x08701030 > [0.748493] microcode: CPU15: patch_level=0x08701030 > [0.748496] microcode: CPU17: patch_level=0x08701030 > [0.748496] microcode: CPU18: patch_level=0x08701030 > [0.748498] microcode: CPU19: patch_level=0x08701030 > [0.748498] microcode: CPU20: patch_level=0x08701030 > [0.748500] microcode: CPU21: patch_level=0x08701030 > [0.748500] microcode: CPU22: patch_level=0x08701030 > [0.748501] microcode: CPU24: patch_level=0x08701030 > [0.748501] microcode: CPU23: patch_level=0x08701030 > [0.748503] microcode: CPU16: patch_level=0x08701030 > [0.748503] microcode: CPU26: patch_level=0x08701030 > [0.748503] microcode: CPU27: patch_level=0x08701030 > [0.748505] microcode: CPU28: patch_level=0x08701030 > [0.748506] microcode: CPU29: patch_level=0x08701030 > [0.748507] microcode: CPU30: patch_level=0x08701030 > [0.748508] microcode: CPU25: patch_level=0x08701030 > [0.748509] microcode: CPU31: patch_level=0x08701030 > [0.748511] microcode: CPU2: patch_level=0x08701030 > [0.748554] microcode: Microcode Update Driver: v2.2. > > I'm pretty sure I wouldn't be getting a zenbleed warning if it was using > the most recent microcode. > > My processor is this one: > > vendor_id : AuthenticAMD > cpu family : 23 > model : 113 > model name : AMD Ryzen 9 3950X 16-Core Processor > > This leads me to the 17h family. > > I do not use an initramfs as my system doesn't require one. I am not > willing to try an initramfs as my system fully functions without one and > this is not an issue with the Intel machines I have. > > I have properly configured the kernel (gentoo-sources-6.6.13): > > CONFIG_CPU_SUP_AMD=y > CONFIG_EXTRA_FIRMWARE="brcm/BCM20702B0-19ff-0239.hcd > amd-ucode/microcode_amd_fam17h.bin" > CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" > > The firmware loading is working as it does load the firmware for my > bluetooth adapter with no issues. > > (In the newer kernels microcode loading is enabled by default - no way > to turn it off. All you have to do is select CPU_SUP_AMD apparently. It > works on Intel machines.) > > I've even updated the motherboard BIOS firmware, and while that fixed > all the other issues it apparently does not have patches for zenbleed. > > Does anyone have any idea why this will not update? > > -Dan It could be AMD have not yet released microcode updates for the community. OEMs receive new microcode first and patch it in their MoBo BIOS/UEFI firmware. Eventually the CPU manufacturers release microcode for older CPUs no longer supported by OEMs. Since you have embedded 'amd-ucode/ microcode_amd_fam17h.bin' in your kernel I don't think there's anything else you can do at this point in time, beyond emerging the latest sys-kernel/linux- firmware and rebooting. PS. I always place the microcode string first in the CONFIG_EXTRA_FIRMWARE= entries, since it should be the fist thing to load by the CPU. I don't know if it would makes any difference, since the whole string of firmwares will be parsed in one go. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Why is KDE so bad at multiple monitors?
On Sunday, 3 March 2024 19:31:30 GMT Dale wrote: > Daniel Frey wrote: > > On 2/29/24 03:27, Dale wrote: > >> To provide a little more info on how this works. This is how I did > >> it. It helps a LOT to have tab completion with this. It will fill > >> in a lot of the info and when unsure, list the available options. > >> First, I had to install the package xrandr. My first problem is the > >> command isn't available since it wasn't installed. So, if you don't > >> have it, install it. It's tiny. This is what I have for my setup. > >> You can ignore that I watch TV and just pretend you have two monitors > >> side by side or whatever and get the same results. I have a DB15HD > >> connector, referred to as VGA within xrandr. That is my main > >> monitor. The second monitor is is connected to a HDMI port, seen as > >> same in xrandr, and what I watch TV with. This is the output I > >> started with to get good clues. > >> > >> > >> root@fireball / # xrandr --listmonitors > >> Monitors: 2 > >> 0: +*VGA-0 1920/598x1080/336+0+0 VGA-0 > >> 1: +HDMI-0 1920/1150x1080/650+1920+0 HDMI-0 > >> root@fireball / # > >> > >> > >> Since I have different ports, it is easy to see which is which. The > >> last bit is what you use in the command, not the first bits. If all > >> your ports are the same, mini HDMI for example, I think the port > >> lowest to the bottom of the video card is number 0, or the first > >> port. Anyway, mine is easy. I then typed in xrandr --output and hit > >> tab twice. It will list all the available monitors. Pick the one > >> you want to be the first output or main monitor. In my case, VGA-0 > >> as shown on the end of line one. Once you type enough, tab > >> completion will fill it in. Then add --primary to that to make it > >> the primary display. > >> > >> For the second monitor, continue on with the command and tab > >> completion. Type in --output and hit tab twice again to list > >> options. Pick the second monitor and type enough in for tab > >> completion to fill in the rest. Then add --right-of, --left-of, > >> --above or --below and then the output device for the main monitor. > >> For me, this is what my command looks like. > >> > >> > >> root@fireball / # xrandr --output VGA-0 --primary --output HDMI-0 > >> --right-of VGA-0 > >> root@fireball / # > >> > >> > >> That makes VGA the primary, HDMI-0 second and to the right of VGA-0. > >> If you have more than two monitors, just keep adding --output and > >> list and place the other monitors. I don't have the means to test > >> but that should work. I'd think setting the primary is key in this > >> so I wouldn't forget to include that. > >> > >> Once you get that command, you can test it by going to a Konsole if > >> using KDE or some other similar tool you can type commands in as root > >> and run the command manually. If it works correctly, add the command > >> to the file in this path. /usr/share/sddm/scripts/Xsetup I haven't > >> logged out and back in again yet so we will see when that happens if > >> it really works and my little quirk goes away. > >> > >> There is a man page for this. It may have other options that you may > >> need to add. Just keep in mind, what is between each --output is > >> what it applies too. One could have different resolutions, image > >> flipped or something and lots of other options. Just keep the > >> options in the right section of the command. > >> > >> I hope this helps someone and makes decent sense. I also hope it > >> works after I logout and back in again. :/ I'm making a note of > >> the location in case I need to comment it out. Better to be safe > >> than sorry. LOL > >> > >> Dale > >> > >> :-) :-) > > > > I've been gone for a few days as I was rebuilding my main PC. > > > > I thought I'd provide an update: it was xorg-server causing all the > > issues. > > > > I figured as I had to redo everything anyway to switch to systemd and > > wayland as that's what the bigger DE's tend to be supporting nowadays. > > > > After fiddling around with systemd for a day (I'd tried it once before > > converting a system from openrc->systemd and failed miserably - > > nothing worked) I've reconfigured most things the "systemd" way. > > > > I guess starting fresh solves all sorts of issues. :o) > > > > Some things I like about systemd: > > - It is capable of automounting NFS shares out of the box; I just > > configured fstab so systemd automatically generated the automount > > configured it required. No extra steps needed; > > - It provides a scrollable list by default showing all the items you > > have access to in order to change how your machines behaves; > > - It isolates services in logs. This was helpful when sddm didn't want > > to behave. > > > > Some things I don't like: > > - It has nutty network configuration. It was applying an APIPA network > > address as the primary for my interface which broke all sorts of
Re: [gentoo-user] profile is not depricated -- how to switch correctly
On Thursday, 29 February 2024 09:52:19 GMT John Covici wrote: > On Thu, 29 Feb 2024 04:24:06 -0500, > > Michael wrote: > > [1 ] > > > > On Thursday, 29 February 2024 09:01:52 GMT John Covici wrote: > > > I got a message on my world update that said my profile which is > > > /var/db/repos/gentoo/profiles/default/linux/amd64/17.1/desktop/gnome/sys > > > temd / is depricated and no longer supported. So, afterr this update is > > > finished, which one should I switch to -- portage says to use > > > default/linux/amd64/17.1/desktop/gnome/systemd/merged-usr but in > > > looking through the list I see one that says > > > default/linux/amd64/23.0/desktop/gnome/systemd (exp) which doesn't say > > > merged-usr, so what would be the advantages of either choice here? > > > > > > Thanks in advance for any suggestions. > > > > There should have been an e-news item on this? Did you check 'eselect > > news > > list'? > > > > https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html > > > > HTH, > > I did read the news item, that is why I am asking, so which of the two > profiles 17.1 or 23.0 ? I have to update my system and run depclean > before I can switch, but I was wondering which of those to choose? The "(exp)" suffix indicates profiles masked as such are "experimental" at this point in time. Personally, unless I am testing things I tend to stick with stable to minimise maintenance work, but it is your call. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] profile is not depricated -- how to switch correctly
On Thursday, 29 February 2024 09:01:52 GMT John Covici wrote: > I got a message on my world update that said my profile which is > /var/db/repos/gentoo/profiles/default/linux/amd64/17.1/desktop/gnome/systemd > / is depricated and no longer supported. So, afterr this update is > finished, which one should I switch to -- portage says to use > default/linux/amd64/17.1/desktop/gnome/systemd/merged-usr but in > looking through the list I see one that says > default/linux/amd64/23.0/desktop/gnome/systemd (exp) which doesn't say > merged-usr, so what would be the advantages of either choice here? > > Thanks in advance for any suggestions. There should have been an e-news item on this? Did you check 'eselect news list'? https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html HTH, signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Why is KDE so bad at multiple monitors?
On Sunday, 25 February 2024 17:36:25 GMT Daniel Frey wrote: > On 2/25/24 01:01, Michael wrote: > > I used to experience the same when using Xorg with AMD-Radeon graphics > > instead of Nvidia, but since I moved to Wayland the problem of losing > > screen settings has gone. One monitor is using the DVI port of the card > > and the other HDMI. It should be worth trying Wayland instead of Xorg to > > see if it works out better for your setup. > > I actually tried Wayland maybe 3 months ago to try to solve the problem. > Wayland doesn't work at all - it just gave me a blank screen at login. I > did check USE flags and recompiled and still login did not work at all. > > At least Xorg gave me a misconfigured working login (better than no > login at all.) > > -Dan >From the little I know about Nividia nuances the symptom of a black screen points to KMS mode setting missing in the kernel. Also nvidia_drm.modeset should be able to load without errors, or the wayland compositor will not work. Also, I recall reading somewhere Nvidia does not like monitors with different resolutions and refresh rates, but I don't know if there is any workaround to this. TBH I moved away from Xorg because it was getting worse and worse over time with my graphics. Wayland was a bit unstable on my systems in the beginning, but over time it has improved significantly. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Why is KDE so bad at multiple monitors?
On Sunday, 25 February 2024 05:52:20 GMT Dale wrote: > Daniel Frey wrote: > > After cursing KDE for a while with three monitors, does anyone have > > any idea why KDE is so bad at managing multiple monitors? > > > > All I'm trying to do is get it to remember *where* my monitors are (I > > have two side-by-side and one above the right monitor.) I go into > > System Settings, set it up and it works perfectly... until I log out. > > Then it resets everything and I have to set it up again. > > > > Anyone have any clue why it refuses to save settings? > > > > -Dan > > I have two monitors too, sort of. One monitor is for computer stuff, > checking email, surfing the net etc etc etc. The other monitor I use to > watch TV with. The output from the video card second output goes to a > splitter so I can have the same video in both my bedroom and the living > room. I use Nvidia settings to manage mine but I run into the same > problem you do. Sometimes when I login, the second monitor output is > dead. TV shows the dreaded "No signal" thing floating around. I have > to open Nvidia settings, disable the second monitor output, hit apply, > click that I can see the screen still, re-enable the second monitor, > click apply, click I can see the monitor and then the second monitor > works again. It's annoying as heck. I'm on the 470 series of Nvidia > drivers. Best my old card can do. LOL > > I looked in the KDE System Settings display settings screen and it shows > the same as Nvidia. Maybe one copies the other??? There's really > nothing for me to change there so I can't hit apply. :/ I've always > wondered if I can set this up in xorg.conf file instead of the GUI. > Maybe it would work better. Thing is, everything says it should "just > work" and the file shouldn't be needed. > > This may not be a KDE problem. It could be a Nvidia problem. It may be > KDE but I'm not sure which to blame. I don't let my screen go off > except for the once a week trip to town to get shots so I just put up > with it. The rest of the time, my monitors and TVs tend to stay on. > > You are not alone. I'm just not real sure this is a KDE problem. It's > possible tho. Mostly, you are not alone. > > Dale > > :-) :-) I used to experience the same when using Xorg with AMD-Radeon graphics instead of Nvidia, but since I moved to Wayland the problem of losing screen settings has gone. One monitor is using the DVI port of the card and the other HDMI. It should be worth trying Wayland instead of Xorg to see if it works out better for your setup. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: How to set up drive with many Linux distros?
On Friday, 23 February 2024 00:28:59 GMT Grant Edwards wrote: > On 2024-02-22, Wol wrote: > > On 22/02/2024 21:45, Grant Edwards wrote: > >> I've been reading up on UEFI, and it doesn't seem to be any > >> better. People complain about distro's stomping on each other's files > >> in the ESP partiton and multiple distro's using the same name in the > >> boot slots stored in NVM. And then the boot choice order changes > >> (though it may not be apparent to the naked eye) when one of the > >> distros decides to update/reinstall its boot stuff. > > > > At least if you use UEFI *as* your bootloader, then that won't > > happen. That assumes you're using UEFI, though! > > According to what I've read UEFI isn't a bootloader. It's a boot > manager which can load and run EFI bootloaders (of which there can be > multiple installed). The UEFI firmware of the MoBo contains its own bootloader and a boot manager with its own boot menu, initialised and running from the MoBo's EEPROM. Unlike conventional/legacy bootloaders stored in the first sector of a disk (MBR), the UEFI firmware is stored in the MoBo's EEPROM, a larger equivalent to the old CMOS. However, this comes with the caveat the UEFI 'bootloader' can only load .efi executables which have already been placed in the FAT32 formatted EFI System Partition (ESP). Unlike GRUB's MBR Stage 1 bootloader code, the UEFI firmware is large enough to contain its own fs driver to be able to read the ESP fs content and identify and run all .efi applications. Kernel images which have been built with the EFI stub and therefore masquerade as .efi compatible files can be loaded directly by the UEFI firmware without the need of an additional bootloader. > > In which case, 's bootloader doesn't get a look-in. > > Yes, AFAICT, it does (sometimes?). When you install under > UEFI it installs EFI bootloader files (either kernels wrapped in EFI > bootloader executables or the grub EFI bootloader) in the EFI Systgem > Partition (ESP), and then adds one or more entries in the EFI NVM that > points to those files (or something like that). The Linux UEFI > systems I have all still use grub2 (which gets written to the ESP). Legacy GRUB on an MBR partitioned disk, writes its Stage 1 bootloader code in the first sector and Stage 1.5 with the fs drivers in sector 34, before the first partition. GRUB2 on a UEFI system installs the file /efi//grubx64.efi in the ESP, an equivalent of the Stage 1 and Stage 1.5 of legacy GRUB. The Stage 2 /boot/ grub/ files can be installed either in the ESP, or on a different partition. > It's entirely possible for one distro to overwrite files in the ESP > that belong to other distros. I've read multiple complaints about > exactly that when trying to do multi-boot with UEFI. In practice it's > just like the fight over who owns the MBR and the DOS disklable gap. It doesn't really matter if the grubx64.efi executable is overwritten, as long as the OS_PROBER is not disabled in /etc/default/grub. Re-running grub- mkconfig will re-scan the ESP and any drive/partitions, pick up any OS kernel images known by GRUB and add them to GRUB's boot menu. The problem starts if/when kernel images are overwritten by successive Linux OS distros. This is likely when derivatives of the same main distros e.g. Ubuntu all create a directory called /EFI/ubuntu/ in the ESP and drop their kernels & initrd images in there potentially overwriting other distro's files. > One recipe I read about for doing what I wanted to do with UEFI > involved installing a Linux distro (didn't really matter which), then > installing rEFInd. After that, some manual renaming and deleting of > the files in the ESP was required. Then he started installing various > distros. After each distro installation, the author had to re-install > rEFInd, and after many of them he had to manually remove or rename > files in the ESP (or adjust the rEFInd config file). > > And in the end, he ended up with multiple menu entries (for different > installations) that had identical names. The concept of one bootloader/manager ruling them all is broadly the same whether you use rEFInd or GRUB, as are the hoops you have to jump through to accommodate distros' automated/hardcoded installation scripts. When using a distro's installer menu on a legacy BIOS MoBo you can select a partition (PBR) to install GRUB, but GRUB will complain and suggest you could use blocklists but it is unreliable. Last time I received an error like this, I installed grub in a PBR manually with the '--force' option, without using the installer GUI. After that, whenever I updated GRUB it complained again about blocklists, but it worked fine. > It was more complicated and difficult than my current scheme. > > > As for "'s obviously superior bootloader", well > > is using the exact same boot-loader, and when IT installs, how is it > > going to be able to boot if it can't call 's boot > > loader because it's
Re: [gentoo-user] is there something wrong with net-misc/inetutils?
On 2/18/24 01:50, n952162 wrote: On 2/17/24 23:10, Michael Cook wrote: On 2/17/24 14:03, n952162 wrote: On 2/17/24 20:00, n952162 wrote: On 2/17/24 19:56, n952162 wrote: On 2/17/24 19:22, n952162 wrote: On 2/17/24 16:38, Arsen Arsenović wrote: n952162 writes: When I try to emerge it, it fails, but https://packages.gentoo.org/packages/net-misc/inetutils seems normal. Am I misreading it? There does seem to be an open bug: https://bugs.gentoo.org/924493 If this one does not match your issue, please file a bug: https://wiki.gentoo.org/wiki/Bugzilla/Bug_report_guide Thanks in advance, have a lovely day. Would that make the package not emerge? I can't imagine a more mature package ... The package must have worked once. Is it possible and practical to get an earlier, working version out of git? I'm currently using the ftp in /net-ftp/ftp-0.17.34.0.2.5.1/ and it's broken - it doesn't send the last block. Other FTPs listed in https://wiki.gentoo.org/wiki/FTP have different command syntax, which breaks my expect(1) script. The inetutils on nixos runs fine. I wonder why gentoo can't get it working ... I assume you're trying to build inetutils with the ftp use flag set? net-ftp/ftp blocks inetutils in that case, you need to remove net-ftp/ftp first. Can you give some more information about that? E.g. how one package can block another one? I removed net-ftp/ftp (good riddance): $ equery l net-ftp/ftp !!! No installed packages matching 'net-ftp/ftp' * Searching for ftp in net-ftp ... But I'm still getting the same problem: emerge: there are no ebuilds to satisfy "net-misc/inetutils". emerge: searching for similar names... emerge: Maybe you meant any of these: net-misc/iputils, net-misc/tipcutils, net-misc/bridge-utils? It looks like you're portage tree is out of date ... rather very out of date. The package was first added in September of 2023. So you'll have to sync up and probably have lots of other updates to handle as well.
Re: [gentoo-user] Issues with amdgpu driver: Compositor hangs, sysfs not working
On Sunday, 18 February 2024 09:17:13 GMT Paul Sopka wrote: > Thank you for your reply. > > >> Hello everybody, > >> > >> I installed an AMD Radeon RX 7900 XTX today, switching from Nvidia. But > >> once I enable FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y to have a tty once > >> the driver is up, the following happens: > >> > >> 1) My Wayland compositor (Hyprland) takes very long to start. > >> > >> 2) reading from sysfs (e.g. running "cat > >> /sys/class/drm/card0/device/gpu_busy_percent") does not work and causes > >> a hang. > >> > >> Once I disable FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=n, I have no issues > >> with the starting speed of the compositors at all and the mentioned > >> command works. But this leads to a black tty. > > > > You'd normally need this enabled to get a fb display on the console, but I > > don't know if this would be provided by proprietary drivers instead for > > your card - see below. > > I made a mistake here, sorry. The issue causing setting is > DRM_FBDEV_EMULATION=y, which on itself works with the open source > driver, but causes issues as soon as I start Hyprland. I have an older AMD card here, using amdgpu only. If I disable DRM_FBDEV_EMULATION I lose my framebuffer and end up with a black screen. When the sddm display manager starts I have a GUI again to login to Plasma with. This is to be expected in my case, because I rely on the KMS driver (KMS FB helpers) to provide a framebuffer device. Unless an AMD proprietary driver is available via amdgpu-pro to substitute for the KMS FB emulation, then you won't get a framebuffer device to render your tty console. > > It could be both. I don't think there's any Linux firmware released yet > > for this card - but I don't follow the latest & greatest so I could be > > wrong. You'd need the AMD amdgpu-pro on top of the amdgpu driver, to > > bring in the proprietary OpenGL, OpenCL, Vulkan and AMF components: > > > > https://wiki.gentoo.org/wiki/AMDGPU-PRO > > > > This is what's in portage today: [snip ...] > The firmare seems good, since it is loaded just fine, "dmesg | grep > amdgpu | grep firmware" returns: > [ 16.905914] Loading firmware: amdgpu/psp_13_0_0_sos.bin > [ 16.905916] Loading firmware: amdgpu/psp_13_0_0_ta.bin > [ 16.905917] Loading firmware: amdgpu/smu_13_0_0.bin > [ 16.905917] Loading firmware: amdgpu/dcn_3_2_0_dmcub.bin > [ 16.905918] Loading firmware: amdgpu/gc_11_0_0_pfp.bin > [ 16.905919] Loading firmware: amdgpu/gc_11_0_0_me.bin > [ 16.905919] Loading firmware: amdgpu/gc_11_0_0_rlc.bin > [ 16.905920] Loading firmware: amdgpu/gc_11_0_0_mec.bin > [ 16.905921] Loading firmware: amdgpu/gc_11_0_0_imu.bin > [ 16.905922] Loading firmware: amdgpu/sdma_6_0_0.bin > [ 16.905923] Loading firmware: amdgpu/vcn_4_0_0.bin > [ 16.906095] Loading firmware: amdgpu/gc_11_0_0_mes_2.bin > [ 16.906096] Loading firmware: amdgpu/gc_11_0_0_mes1.bin > [ 16.906496] amdgpu :03:00.0: amdgpu: Will use PSP to load VCN > firmware These are for the amdgpu driver. I expect the amdgpu-pro proprietary driver contains additional firmware. > Also the mesa libraries work just fine, Mesa is the open source implementation of OpenGL, Vulkan, et al. graphics API specifications. If you are using proprietary AMD drivers then I understand all the graphics API instructions will go through these proprietary drivers, instead of being translated by Mesa. > if I disable > DRM_FBDEV_EMULATION=n, I just get a black tty, but Hyprland starts and I > can play games with the expected performance. I am not sure how the fbdev emulation in the kernel works with the amdgpu-pro when combined with Hyprland. Have you tried a different compositor to see how it compares. If your problem is caused by some Hyprland bug, you'd soon know. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] "xset dpms" not working
On Sunday, 18 February 2024 08:35:18 GMT Walter Dnes wrote: > On Sat, Feb 17, 2024 at 08:21:42PM -0500, Walter Dnes wrote > > > Regardless of the above, the monitor does not blank after 10 minutes > > > > (i.e. 600 seconds). If I run "xset dpms force off" from xterm (both as > > local user and as root), the display goes dark... for approximately 1 > > second... and then returns to normal. > > So I turned the monitor off with the physical switch, took a nap, and > turned it on when I got up. Now the blanking works again. Cue the > Microsoft support jokes. What gives??? Are you using a Display Port, or HDMI connection perhaps? Modern monitors come with their own onboard chipset which may lose sync with the PC. I've experience the opposite with mine when I first bought it and thought the PC had crashed ... :-) signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Issues with amdgpu driver: Compositor hangs, sysfs not working
On Saturday, 17 February 2024 19:34:37 GMT Paul Sopka wrote: > Hello everybody, > > I installed an AMD Radeon RX 7900 XTX today, switching from Nvidia. But > once I enable FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y to have a tty once > the driver is up, the following happens: > > 1) My Wayland compositor (Hyprland) takes very long to start. > > 2) reading from sysfs (e.g. running "cat > /sys/class/drm/card0/device/gpu_busy_percent") does not work and causes > a hang. > > Once I disable FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=n, I have no issues > with the starting speed of the compositors at all and the mentioned > command works. But this leads to a black tty. You'd normally need this enabled to get a fb display on the console, but I don't know if this would be provided by proprietary drivers instead for your card - see below. > The only two error messages from amdgpu I find in dmesg are: > > [ 66.757500] amdgpu :03:00.0: amdgpu: SMU: I'm not done with your > previous command: SMN_C2PMSG_66:0x0029 SMN_C2PMSG_82:0x > [ 66.757502] amdgpu :03:00.0: amdgpu: Failed to disable gfxoff! > > and > > [ 870.087856] amdgpu :03:00.0: amdgpu: SMU: I'm not done with your > previous command: SMN_C2PMSG_66:0x0029 SMN_C2PMSG_82:0x > [ 870.087858] amdgpu :03:00.0: amdgpu: Failed to export SMU metrics > table! > > Did I forget anything or is this a bug? It could be both. I don't think there's any Linux firmware released yet for this card - but I don't follow the latest & greatest so I could be wrong. You'd need the AMD amdgpu-pro on top of the amdgpu driver, to bring in the proprietary OpenGL, OpenCL, Vulkan and AMF components: https://wiki.gentoo.org/wiki/AMDGPU-PRO This is what's in portage today: ~ $ eix -l amdgpu-pro * dev-libs/amdgpu-pro-opencl Available versions: ~20.40.1147286 ^fmsd [ABI_X86="32 64"] ["|| ( abi_x86_32 abi_x86_64 )"] Homepage: https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-linux-20-40 Description: Proprietary OpenCL implementation for AMD GPUs * media-libs/amdgpu-pro-vulkan Available versions: ~21.50.2.1384496-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] ~22.10.4.1452060-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] ~22.20.5.1511376-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] ~22.40.6.1580631-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] ~23.10.3.1620044-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] ~23.20.0.1654522-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] Homepage:https://www.amd.com/en/support Description: AMD's closed source vulkan driver, from Radeon Software for Linux * media-video/amdgpu-pro-amf Available versions: ~1.4.24.1452059 ^md ~1.4.26.1511376 ^md ~1.4.29.1580631 ^md ~1.4.30.1620044 ^md ~1.4.31.1654522 (0/31)^md Homepage:https://www.amd.com/en/support Description: AMD's closed source Advanced Media Framework (AMF) driver Found 3 matches signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] is there something wrong with net-misc/inetutils?
On 2/17/24 14:03, n952162 wrote: On 2/17/24 20:00, n952162 wrote: On 2/17/24 19:56, n952162 wrote: On 2/17/24 19:22, n952162 wrote: On 2/17/24 16:38, Arsen Arsenović wrote: n952162 writes: When I try to emerge it, it fails, but https://packages.gentoo.org/packages/net-misc/inetutils seems normal. Am I misreading it? There does seem to be an open bug: https://bugs.gentoo.org/924493 If this one does not match your issue, please file a bug: https://wiki.gentoo.org/wiki/Bugzilla/Bug_report_guide Thanks in advance, have a lovely day. Would that make the package not emerge? I can't imagine a more mature package ... The package must have worked once. Is it possible and practical to get an earlier, working version out of git? I'm currently using the ftp in /net-ftp/ftp-0.17.34.0.2.5.1/ and it's broken - it doesn't send the last block. Other FTPs listed in https://wiki.gentoo.org/wiki/FTP have different command syntax, which breaks my expect(1) script. The inetutils on nixos runs fine. I wonder why gentoo can't get it working ... I assume you're trying to build inetutils with the ftp use flag set? net-ftp/ftp blocks inetutils in that case, you need to remove net-ftp/ftp first.
Re: [gentoo-user] Re: [SOLVED?] Upgrade old laptop kernel 5.15.69 ==> 6.6.13; no console
On Saturday, 3 February 2024 16:16:42 GMT Walter Dnes wrote: > On Sat, Feb 03, 2024 at 10:18:41AM +0000, Michael wrote > > Also, unless you use an initrd don't forget any firmware blobs which > > may be be needed by your graphics card and while you're at it add > > your CPU microcode there too. > > The graphics is a bog standard Intel i915 integrated chip that's been > running on the laptop for years without blobs. It is running for years with the blobs included in the OEM's BIOS firmware. The hardware could do with the patches for bugs and vulnerabilities issued since you bought the PC. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Suggestions for backup scheme?
On Saturday, 3 February 2024 17:32:17 GMT Rich Freeman wrote: > On Fri, Feb 2, 2024 at 6:39 PM Grant Edwards wrote: > > On 2024-01-31, Rich Freeman wrote: > > > In any case, these COW filesystems, much like git, store data in a > > > way that makes it very efficient to diff two snapshots and back up > > > only the data that has changed. [...] > > > > In order to take advantage of this, I assume that the backup > > destination and source both have to be ZFS? > > So, the data needs to be RESTORED to ZFS for this to work. However, > the zfs send command serializes the data and so you can just store it > in files. Those files can only be read back into zfs. > > It is probably a bit more typical to just pipe the send command into > zfs receive (often over ssh) so that you're just directly mirroring > the filesystem, and not storing the intermediate data. > > > Do backup source and > > destination need to be in the same filesystem? Or volume? Or Pool? > > No on all of these, but they can be. > > > If you'll forgive the analogy, we'll say the the functionality of > > rsync (as used by rsnapshot) is built-in to ZFS. Is there an > > application that does with ZFS snapshots what the rsnapshot > > application itself does with rsync? > > There are a few wrappers around zfs send. I'm using > sys-fs/zfs-auto-snapshot and what looks like a much older version of: > https://github.com/psy0rz/zfs_autobackup > > > I googled for ZFS backup applications, but didn't find anything that > > seemed to be widespread and "supported" the way that rsnapshot is. > > They're less popular since many just DIY them, but honestly I think > the wrapper is a nicer solution. It will rotate backups, make sure > that snapshots aren't needed before deleting them, and so on. In > order to do an incremental backup the source/destination systems need > to have matching snapshots to base them on, so that is important if > backups are sporadic. If you're just saving all the send streams then > knowing which ones are obsolete is also important, unless you want to > have points in time. This article offers some comparison tests between ZFS, Btrfs and mdadm+dm- integrity. Although the setup and scenarios are not directly comparable with the OP's use case they provide some insight on more typical implementations where these fs excel. https://unixsheikh.com/articles/battle-testing-zfs-btrfs-and-mdadm-dm.html signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Suggestions for backup scheme?
On Friday, 2 February 2024 23:39:18 GMT Grant Edwards wrote: > On 2024-01-31, Rich Freeman wrote: > > Honestly, at this point I would not run any storage I cared about on > > anything but zfs. There are just so many benefits. > > > > [...] > > > > In any case, these COW filesystems, much like git, store data in a > > way that makes it very efficient to diff two snapshots and back up > > only the data that has changed. [...] > > In order to take advantage of this, I assume that the backup > destination and source both have to be ZFS? Do backup source and > destination need to be in the same filesystem? Or volume? Or Pool? > (I'm not clear on how those differ exactly.) Or can the backup > destination be "unrelated" to the backup source? The primary source of > failure in my world is definitely hardware failure of the disk drive, > so my backup destination is always a separate physical (usually > external) disk drive. TBH using ext4/xfs/f2fs/etc. on the host plus an incremental backup method on any other fs of choice on external storage is IMHO a better method for a laptop. Unless your data is changing continuously and you need incremental backups every 5 minutes what you use is well suited to your use case. > If you'll forgive the analogy, we'll say the the functionality of > rsync (as used by rsnapshot) is built-in to ZFS. Broadly and rather loosely yes, by virtue of the COW and snapshot fs architecture and the btrfs/zfs send-receive commands. > Is there an > application that does with ZFS snapshots what the rsnapshot > application itself does with rsync? COW filesystems do not need a 3rd party application. They come with their own commands which can be called manually, or scripted for convenience and automation. Various people have created their own scripts and applications, e.g. https://unix.stackexchange.com/questions/696513/best-strategy-to-backup-btrfs-root-filesystem > I googled for ZFS backup applications, but didn't find anything that > seemed to be widespread and "supported" the way that rsnapshot is. > > -- > Grant There must be quite a few scripts out there, but can't say what support they may receive. Random search revealed: https://www.zfsnap.org/ https://github.com/shirkdog/zfsbackup https://gbyte.dev/blog/simple-zfs-snapshotting-replicating-backup-rotating-convenience-bash-script signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Upgrade old laptop kernel 5.15.69 ==> 6.6.13; no console
On Saturday, 3 February 2024 09:23:15 GMT netfab wrote: > Le 03/02/24 à 03:06, Walter Dnes a tapoté : > > I got linux-6.1.57-gentoo kernel built and working, but > > > > linux-6.6.13-gentoo still comes up with no console. Here's my latest > > .config attempt for 6.6.13 attached. Any ideas? > > You should try to enable an early framebuffer driver, CONFIG_FB_VESA=y > for example. See: > > https://wiki.gentoo.org/wiki/Framebuffer#DRM_framebuffer_drivers It could well be more than 15-20 years since I had VESA FB enabled and not once since then, without any detriment to a console coming up at boot. Try switching to [*] the following: # CONFIG_SYSFB_SIMPLEFB is not set # CONFIG_DRM_SIMPLEDRM is not set # CONFIG_FB_SIMPLE is not set Then hopefully you'll get a console kicking in. Also, unless you use an initrd don't forget any firmware blobs which may be be needed by your graphics card and while you're at it add your CPU microcode there too. Currently you only show the firmware for your wireless: # Firmware loader # CONFIG_FW_LOADER=y CONFIG_EXTRA_FIRMWARE="iwlwifi-6000-4.ucode" Then, if you still fail to get a console, connect over ssh to check what dmesg reports for any hints of missing drivers. HTH. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Suggestions for backup scheme?
On Wednesday, 31 January 2024 21:30:56 GMT Rich Freeman wrote: > On Wed, Jan 31, 2024 at 1:42 PM Wols Lists wrote: > > On 31/01/2024 17:56, Rich Freeman wrote: > > > I don't think there are > > > any RAID implementations that do full write journaling to protect > > > against the write hole problem, but those would obviously underperform > > > zfs as well. > > > > This feature has been added to mdraid, iirc. > > Oh, it looks like it has. Kind of annoying that it only works for a > separate device. I guess you could create a separate partition on all > of the devices, create a mirror across all of those, and then use that > as the journal for the real raid. It would be nice if it had an > option for an internal journal. > > I'd expect the performance of btrfs/zfs to be better of course because > it just does the write to known-unused blocks, so interrupted writes > don't cause any issues. Depending on how far it gets when interrupted > the write will be ignored (it is just data written into unused space), > or will get completed (the root of the metadata was updated and now > points to a consistent new state). I have been running BTRFS on a system for just over 10 years now, on SSD and spinning SATA drives. I recall the odd glitch (file corruption, but no data lost) some 7 or 8 years ago. Since then I've had no problems. A second system on BTRFS has been running since last summer and had some hard reboots (I need a bigger UPS) but still no problem with it. Subjectively and anecdotally therefore, I'd consider BTRFS for Linux as long as long as the use case requires it - ease of snapshots, flexible space requirements, compression, etc. Known problems like RAID 5, 6 and perhaps quotas(?) on BTRFS are for experimentation only. On FreeBSD I use ZFS. For a personal filesystem where data does not change frequently I'd probably choose ext4. [Slightly O/T]: On a new laptop installation on SSD I'm thinking of trying F2FS for the OS and ext4 for /home. I've only tried F2FS on USB sticks so far. Would you have some feedback to share on F2FS? signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Suggestions for backup scheme?
On Tuesday, 30 January 2024 18:15:09 GMT Grant Edwards wrote: > I need to set up some sort of automated backup on a couple Gentoo > machines (typical desktop software development and home use). One of > them used rsnapshot in the past but the crontab entries that drove > that have vanished :/ (presumably during a reinstall or upgrade -- > IIRC, it took a fair bit of trial and error to get the crontab entries > figured out). > > I believe rsnapshot ran nightly and kept daily snapshots for a week, > weekly snapshots for a month, and monthly snapshots for a couple > years. > > Are there other backup solutions that people would like to suggest I > look at to replace rsnapshot? I was happy enough with rsnapshot (when > it was running), but perhaps there's something else I should consider? > > -- > Grant You have probably seen the backup packages suggested in this wiki page? https://wiki.gentoo.org/wiki/Backup and what's available in the tree: https://packages.gentoo.org/categories/app-backup You may also want to consider integral filesystem solutions like btrfs and zfs, depending on your needs and how often your data change, as well as related scripts; e.g.: https://github.com/masc3d/btrfs-sxbackup signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: The hopeless futility of printing.
On Monday, 29 January 2024 22:42:12 GMT Grant Edwards wrote: > On 2024-01-29, Michael wrote: > > On Monday, 29 January 2024 18:19:19 GMT Alan Grimes wrote: > >> It's a LaserJet Pro M453-4. > > > > You shouldn't need hplip drivers and what not, IPP Everywhere ought to > > allow driverless CUPS to allow you to print: > > > > https://www.pwg.org/printers/ > > Does anybody have any experience with using IPP everywhere for > driverless printing with a USB attached printer? (e.g. LasterJet > 1320)? > > Yea, I know, it works as is with the PCL driver, so don't futz with it... > > -- > Grant Quite right, if it ain't broken ... ;-) The Internet Printing Protocol (IPP) is a network protocol, so it won't work over USB. If you have a driver which works then your printing needs are addressed, but in case you want to try something different this link may be useful: https://www2.alfter.us/2015/03/23/gentoo-linux-hplip-and-the-hp-laserjet-1320-dont-mix/ signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] The hopeless futility of printing.
On Monday, 29 January 2024 18:19:19 GMT Alan Grimes wrote: > It's a LaserJet Pro M453-4. You shouldn't need hplip drivers and what not, IPP Everywhere ought to allow driverless CUPS to allow you to print: https://www.pwg.org/printers/ > When I was shopping for it, there was a $350 model with wireless, and a > $450 model without wireless, I was like OMG, i DON'T HAVE TO WORRY ABOUT > WIRELESS??? SHUT UP AND TAKE MY MONEY!!! Aw, the drama of it all! o_O > Apparently there is a stack of about twenty baroque, fiddly, obscure, > and broken demons and libraries that all must work together perfectly to > get the darn thing to work. Each of those packages are advertised as > being the epitome of convenience and plug-and-play perfection except > they don't work, at all... It's well past the point of being pointful > to mess with it. Even if I got it working today, It would be broken > tomorrow in such a way that I'd have no hope of diagnosing or fixing it. =| Read these pages to get to grips with the basics for CUPS: https://wiki.gentoo.org/wiki/Printing (No need for USE="zeroconf" if you prefer static IP addresses in your LAN) Then check this page to try out the IPP everywhere driver: https://wiki.gentoo.org/wiki/Driverless_printing Finally, if IPP Everywhere fails to connect and print, try the old hplip driver: https://wiki.gentoo.org/wiki/HPLIP HTH. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] AMD microcode error?
On Monday, 29 January 2024 16:18:22 GMT Peter Humphrey wrote: > On Sunday, 28 January 2024 17:39:56 GMT Michael wrote: > > I'm not sure a microcode update has been released yet by AMD as a blob, > > outside what they make available to MoBo OEMs within 'BIOS firmware' > > updates. To find what's in the box use: > > > > dmesg | grep -i 'family:' > > > > Then check what CPU family and model microcodes the linux-firmware > > contains: > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.gi > > t/ tree/amd-ucode/README > > No luck with those. OK, this means there is no microcode to load via the linux-firmware releases (yet). > > If you can't find your family and model in the above, then you could check > > what firmware updates are available by the MoBo's OEM. These would > > include > > microcode made directly available by AMD to the OEM. > > That's ASRock X570 Taichi. Their pages suggest that they only acknowledge > Windows 10 & 11. Check the BIOS version in dmesg and compare it with the with the ASRock's AMD chipset image on the asrock.com website. If the versions/dates are the same you have nothing more to do. If the version on the website is more recent then you may want to flash the MoBo with it. Download the zip archive on offer and unzip it, then store the new image on a USB stick which has been formatted with FAT32. Some OEMs require you rename the firmware image file, it will say so on the website, or in a README within the zip archive. Reboot and press [F2] during POST to get into the BIOS setup menu, then go to the Tools tab to flash it from the USB. You may have to re-apply in the BIOS menu any changes you had previously made after the PC reboots, because restoring the settings from a backup file doesn't always work. > I'll keep my eyes open for another glitch. Maybe the microcode isn't to > blame at all, in which case I'd better not sleep on the job. Well, updating the BIOS firmware with the latest version often contains patches for bugs and microcode patches for CPU vulnerabilities. However, this does not mean it will address the MCE errors you were experiencing. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Unable to locate printer
On Monday, 29 January 2024 14:43:07 GMT Thelma wrote: > On 1/29/24 05:16, Michael wrote: > I tried Without '-E' and still no ppd file in: /etc/cups/ppd/ OK, let's try a different syntax[1] to see if those pesky .ppd files will be created: lpadmin -p 3170-color2 -E -v ipp://10.0.0.105/ipp/print -m everywhere lpadmin -p 5370-bw -E -v ipp://10.0.0.106/ipp/print -m everywhere If they still fail to work with IPP-Everywhere, then I'm afraid you have to use specific Brother drivers for these printers[2]. [1] https://www.cups.org/doc/network.html [2] https://wiki.gentoo.org/wiki/Brother_networked_printer signature.asc Description: This is a digitally signed message part.
