[gentoo-user] Re: Going through these one by one.
Steven Lembark wrote: > (dev-python/idna-3.1:0/0::gentoo, ebuild scheduled for merge) > (no parents that aren't satisfied by other packages in this slot) > > (dev-python/idna-2.10-r1:0/0::gentoo, ebuild scheduled for merge) >
Re: [gentoo-user] Gentoo system suddenly failed to boot.
пн, 15 февр. 2021 г. в 22:18, Oli Schmidt : > > ata5.04: SATA link down (SStatus 0 SControl 0) > ata5.04: hard resetting link > ata5.04: failed to resume link (SStatus 0 Scontrol 0) > > and > > ata5.04: SATA link down (SStatus 0 SControl 0) > ata5.04: hard resetting link > ata5.04: failed to resume link (SStatus 0 Scontrol 0) > > > beside all the install/reinstalls - both errors indicate the drive is > failing OR (my best guess) the cable is bad. Replace the cable with a > new one and try again. Thank you for the tips. However, the same cable allows me to boot Gentoo from minimal CD and legacy system from an old IDE drive. As to the new SATA drive, I formatted it anew and created ext4 file system with mkfs.ext4 --cc /dev/sdb2 which 4 times tested the partition writing and reading from it. Moreover, after chrooting into the partition, I do all update and emerge tasks, and it works fine. > On 2021-02-15 21:13, gevisz wrote: > > пн, 15 февр. 2021 г. в 20:59, Jude DaShiell : > >> > >> Check the date and time when you boot and if it isn't correct, you > >> probably have a dead battery on your motherboard. I had to replace > >> one a > >> couple days ago. Fortunately the kind of battery my computer uses is > >> sold > >> in pharmacies since blood sugar meters also use them. > > > > Legacy system shows incorrect time but I think that it is because of > > the dual-boot with Linux and not because of the battery issue. > > The date is still correct: Monday, February 15, 2021. > > > > Well, probably my best option to reinstall the system from scratch. :( > > > >> On Mon, 15 Feb 2021, gevisz wrote: > >> > >> > Yesterday, my relatively new install of Gentoo failed to boot with the > >> > following repeated messages: > >> > > >> > ata5.04: SATA link down (SStatus 0 SControl 0) > >> > ata5.04: hard resetting link > >> > ata5.04: failed to resume link (SStatus 0 Scontrol 0) > >> > > >> > My first thought was that something is wrong with my old IDE (ATA) > >> > drive. (The Gentoo system partition was on /dev/sda5.) > >> > > >> > Nevertheless, I was able to boot from a flash drive with a live Gentoo > >> > CD and chroot into the Gentoo system partition of my IDE drive. > >> > > >> > So, I formatted a new SATA drive according to instructions given in > >> > Gentoo AMD64 Handbook, rsynced the corresponding IDE system partition > >> > into it by the following command: > >> > > >> > rsync -qaHAXS source_dir target_dir > >> > > >> > made the necessary changes to the corresponding fstab file, chrooted > >> > into the new system SATA partition, recompiled grub and installed it > >> > on the new disk. > >> > > >> > After all that I was able to boot the Gentoo system from the new > >> > partition. However, the booting process went as slow as hell, and at > >> > the end Xorg server failed to start. > >> > > >> > My next guess was that something went wrong with the last kernel I > >> > used to boot. So, I tried to boot using the previous kernel. > >> > > >> > However, this time the booting failed with almost the same messages as > >> > above: > >> > > >> > ata5.03: failed to resume link (SStatus 0 SControl 0) > >> > ata5.03: SATA link down (SStatus 0 SControl 0) > >> > ata5.03: hard resetting link > >> > ata6.04: failed to resume link (SStatus 0 SControl 0) > >> > > >> > (Now, my new Gentoo system partition is on /dev/sdb2.) > >> > > >> > Shall I try to do something to fix it before reinstalling Gentoo anew? > >> > > >> > For example, I thought of booting with a live Gentoo flash drive, > >> > chrooting into the new system partition and recompiling @system. > >> > However, if it is not some package that is corrupted, it may be a waste > >> > of time. > >> > Or, maybe, @system may be narrowed to just a few packages needed at boot > >> > time? > >> > Shall I try to recreate initramfs, what in my case means re-emerging > >> > gentoo-kernel package? > >> > What do you think? > >> > > >> > P.S. Nevertheless, I still can successfully boot my very old legacy > >> > system from another partition of my IDE drive. > >> > > >> > > >> >
Re: [gentoo-user] Gentoo system suddenly failed to boot.
ata5.04: SATA link down (SStatus 0 SControl 0) ata5.04: hard resetting link ata5.04: failed to resume link (SStatus 0 Scontrol 0) and ata5.04: SATA link down (SStatus 0 SControl 0) ata5.04: hard resetting link ata5.04: failed to resume link (SStatus 0 Scontrol 0) beside all the install/reinstalls - both errors indicate the drive is failing OR (my best guess) the cable is bad. Replace the cable with a new one and try again. Oli On 2021-02-15 21:13, gevisz wrote: пн, 15 февр. 2021 г. в 20:59, Jude DaShiell : Check the date and time when you boot and if it isn't correct, you probably have a dead battery on your motherboard. I had to replace one a couple days ago. Fortunately the kind of battery my computer uses is sold in pharmacies since blood sugar meters also use them. Legacy system shows incorrect time but I think that it is because of the dual-boot with Linux and not because of the battery issue. The date is still correct: Monday, February 15, 2021. Well, probably my best option to reinstall the system from scratch. :( On Mon, 15 Feb 2021, gevisz wrote: > Yesterday, my relatively new install of Gentoo failed to boot with the > following repeated messages: > > ata5.04: SATA link down (SStatus 0 SControl 0) > ata5.04: hard resetting link > ata5.04: failed to resume link (SStatus 0 Scontrol 0) > > My first thought was that something is wrong with my old IDE (ATA) > drive. (The Gentoo system partition was on /dev/sda5.) > > Nevertheless, I was able to boot from a flash drive with a live Gentoo > CD and chroot into the Gentoo system partition of my IDE drive. > > So, I formatted a new SATA drive according to instructions given in > Gentoo AMD64 Handbook, rsynced the corresponding IDE system partition > into it by the following command: > > rsync -qaHAXS source_dir target_dir > > made the necessary changes to the corresponding fstab file, chrooted > into the new system SATA partition, recompiled grub and installed it > on the new disk. > > After all that I was able to boot the Gentoo system from the new > partition. However, the booting process went as slow as hell, and at > the end Xorg server failed to start. > > My next guess was that something went wrong with the last kernel I > used to boot. So, I tried to boot using the previous kernel. > > However, this time the booting failed with almost the same messages as above: > > ata5.03: failed to resume link (SStatus 0 SControl 0) > ata5.03: SATA link down (SStatus 0 SControl 0) > ata5.03: hard resetting link > ata6.04: failed to resume link (SStatus 0 SControl 0) > > (Now, my new Gentoo system partition is on /dev/sdb2.) > > Shall I try to do something to fix it before reinstalling Gentoo anew? > > For example, I thought of booting with a live Gentoo flash drive, > chrooting into the new system partition and recompiling @system. > However, if it is not some package that is corrupted, it may be a waste of time. > Or, maybe, @system may be narrowed to just a few packages needed at boot time? > Shall I try to recreate initramfs, what in my case means re-emerging > gentoo-kernel package? > What do you think? > > P.S. Nevertheless, I still can successfully boot my very old legacy > system from another partition of my IDE drive. > >
Re: [gentoo-user] Gentoo system suddenly failed to boot.
пн, 15 февр. 2021 г. в 20:59, Jude DaShiell : > > Check the date and time when you boot and if it isn't correct, you > probably have a dead battery on your motherboard. I had to replace one a > couple days ago. Fortunately the kind of battery my computer uses is sold > in pharmacies since blood sugar meters also use them. Legacy system shows incorrect time but I think that it is because of the dual-boot with Linux and not because of the battery issue. The date is still correct: Monday, February 15, 2021. Well, probably my best option to reinstall the system from scratch. :( > On Mon, 15 Feb 2021, gevisz wrote: > > > Yesterday, my relatively new install of Gentoo failed to boot with the > > following repeated messages: > > > > ata5.04: SATA link down (SStatus 0 SControl 0) > > ata5.04: hard resetting link > > ata5.04: failed to resume link (SStatus 0 Scontrol 0) > > > > My first thought was that something is wrong with my old IDE (ATA) > > drive. (The Gentoo system partition was on /dev/sda5.) > > > > Nevertheless, I was able to boot from a flash drive with a live Gentoo > > CD and chroot into the Gentoo system partition of my IDE drive. > > > > So, I formatted a new SATA drive according to instructions given in > > Gentoo AMD64 Handbook, rsynced the corresponding IDE system partition > > into it by the following command: > > > > rsync -qaHAXS source_dir target_dir > > > > made the necessary changes to the corresponding fstab file, chrooted > > into the new system SATA partition, recompiled grub and installed it > > on the new disk. > > > > After all that I was able to boot the Gentoo system from the new > > partition. However, the booting process went as slow as hell, and at > > the end Xorg server failed to start. > > > > My next guess was that something went wrong with the last kernel I > > used to boot. So, I tried to boot using the previous kernel. > > > > However, this time the booting failed with almost the same messages as > > above: > > > > ata5.03: failed to resume link (SStatus 0 SControl 0) > > ata5.03: SATA link down (SStatus 0 SControl 0) > > ata5.03: hard resetting link > > ata6.04: failed to resume link (SStatus 0 SControl 0) > > > > (Now, my new Gentoo system partition is on /dev/sdb2.) > > > > Shall I try to do something to fix it before reinstalling Gentoo anew? > > > > For example, I thought of booting with a live Gentoo flash drive, > > chrooting into the new system partition and recompiling @system. > > However, if it is not some package that is corrupted, it may be a waste of > > time. > > Or, maybe, @system may be narrowed to just a few packages needed at boot > > time? > > Shall I try to recreate initramfs, what in my case means re-emerging > > gentoo-kernel package? > > What do you think? > > > > P.S. Nevertheless, I still can successfully boot my very old legacy > > system from another partition of my IDE drive. > > > > >
Re: [gentoo-user] Gentoo system suddenly failed to boot.
Check the date and time when you boot and if it isn't correct, you probably have a dead battery on your motherboard. I had to replace one a couple days ago. Fortunately the kind of battery my computer uses is sold in pharmacies since blood sugar meters also use them. On Mon, 15 Feb 2021, gevisz wrote: Yesterday, my relatively new install of Gentoo failed to boot with the following repeated messages: ata5.04: SATA link down (SStatus 0 SControl 0) ata5.04: hard resetting link ata5.04: failed to resume link (SStatus 0 Scontrol 0) My first thought was that something is wrong with my old IDE (ATA) drive. (The Gentoo system partition was on /dev/sda5.) Nevertheless, I was able to boot from a flash drive with a live Gentoo CD and chroot into the Gentoo system partition of my IDE drive. So, I formatted a new SATA drive according to instructions given in Gentoo AMD64 Handbook, rsynced the corresponding IDE system partition into it by the following command: rsync -qaHAXS source_dir target_dir made the necessary changes to the corresponding fstab file, chrooted into the new system SATA partition, recompiled grub and installed it on the new disk. After all that I was able to boot the Gentoo system from the new partition. However, the booting process went as slow as hell, and at the end Xorg server failed to start. My next guess was that something went wrong with the last kernel I used to boot. So, I tried to boot using the previous kernel. However, this time the booting failed with almost the same messages as above: ata5.03: failed to resume link (SStatus 0 SControl 0) ata5.03: SATA link down (SStatus 0 SControl 0) ata5.03: hard resetting link ata6.04: failed to resume link (SStatus 0 SControl 0) (Now, my new Gentoo system partition is on /dev/sdb2.) Shall I try to do something to fix it before reinstalling Gentoo anew? For example, I thought of booting with a live Gentoo flash drive, chrooting into the new system partition and recompiling @system. However, if it is not some package that is corrupted, it may be a waste of time. Or, maybe, @system may be narrowed to just a few packages needed at boot time? Shall I try to recreate initramfs, what in my case means re-emerging gentoo-kernel package? What do you think? P.S. Nevertheless, I still can successfully boot my very old legacy system from another partition of my IDE drive.
[gentoo-user] Gentoo system suddenly failed to boot.
Yesterday, my relatively new install of Gentoo failed to boot with the following repeated messages: ata5.04: SATA link down (SStatus 0 SControl 0) ata5.04: hard resetting link ata5.04: failed to resume link (SStatus 0 Scontrol 0) My first thought was that something is wrong with my old IDE (ATA) drive. (The Gentoo system partition was on /dev/sda5.) Nevertheless, I was able to boot from a flash drive with a live Gentoo CD and chroot into the Gentoo system partition of my IDE drive. So, I formatted a new SATA drive according to instructions given in Gentoo AMD64 Handbook, rsynced the corresponding IDE system partition into it by the following command: rsync -qaHAXS source_dir target_dir made the necessary changes to the corresponding fstab file, chrooted into the new system SATA partition, recompiled grub and installed it on the new disk. After all that I was able to boot the Gentoo system from the new partition. However, the booting process went as slow as hell, and at the end Xorg server failed to start. My next guess was that something went wrong with the last kernel I used to boot. So, I tried to boot using the previous kernel. However, this time the booting failed with almost the same messages as above: ata5.03: failed to resume link (SStatus 0 SControl 0) ata5.03: SATA link down (SStatus 0 SControl 0) ata5.03: hard resetting link ata6.04: failed to resume link (SStatus 0 SControl 0) (Now, my new Gentoo system partition is on /dev/sdb2.) Shall I try to do something to fix it before reinstalling Gentoo anew? For example, I thought of booting with a live Gentoo flash drive, chrooting into the new system partition and recompiling @system. However, if it is not some package that is corrupted, it may be a waste of time. Or, maybe, @system may be narrowed to just a few packages needed at boot time? Shall I try to recreate initramfs, what in my case means re-emerging gentoo-kernel package? What do you think? P.S. Nevertheless, I still can successfully boot my very old legacy system from another partition of my IDE drive.
Re: [gentoo-user] why both /usr/lib and /usr/lib64 on a 64bit system?
On February 15, 2021 4:15:43 AM PST, Peter Humphrey wrote: >On Sunday, 14 February 2021 21:48:36 GMT Frank Steinmetzger wrote: >> Am Sun, Feb 14, 2021 at 12:51:30PM -0500 schrieb Jack: >> > As I remember, /lib and /usr/lib hold not only 32 bit libraries, >but >> > non-arch or arch-irrelevant (I know there's a better term) files. >> >> arch-agnostic? ;-) > >No, it should be arch-neutral. Agnosticism is about religion and has >nothing >to do with it. Technically "canonical" also only applies to religious texts. That doesn't keep us from using it descriptively in other areas. Bigger problem is that "arch agnostic" would mean only that the program is incapable of knowing what the arch was. Not that it can work with any arch or that the arch is irrelevant. So "independent" or "neutral" is a better choice in this context. LMP
[gentoo-user] Start conflict "elogind" vs "fwupd"
Greetings, since my last routine Gentoo upgrade on 2021-02-01 "fwupd" is no longer started in the "default" run level. Reason is that "fwupd" erroneously thinks its prerequisite "elogind" is not yet running, starts it again, interprets the error message "already started" and the non-zero exit code as "not startable", and gives in. In order to allow "fwupd" to start" I had to -- temporarily -- remove the "elogind" prerequisite in file "/etc/init.d/fwupd". Did anybody else observe this behaviour? Is this a known problem? Sincerely, Rainer
Re: [gentoo-user] why both /usr/lib and /usr/lib64 on a 64bit system?
On Mon, Feb 15, 2021 at 3:17 AM Walter Dnes wrote: > > On Sun, Feb 14, 2021 at 06:09:58PM -0700, Grant Taylor wrote > > On 2/14/21 10:51 AM, Jack wrote: > > > I don't think you can completely get rid of it. > > > > My (long term) desire is to do away with /lib32 and /lib64, ultimately > > only using /lib. Likewise for the other library directories in /usr or > > wherever they are. I don't see a need for the specific bit variants in > > the future. > > How long before we see /lib and /lib64 *AND* /lib128 ? Well, anything is possible, but it seems unlikely. If it happens soon then chances are that multilib will still be a thing and so less stuff will break than when amd64 was introduced. If it happens in a century when we're all running no-multilib then we'll be reinventing the wheel. The main things that drove amd64 though were: * increasing the number of registers available * allowing direct access to >4GB of RAM (or a fraction of this depending on the OS design) I suspect the first is less of a concern these days - compilers generally only need so many registers and when instructions are added that need more register space they tend to come with registers to accommodate them. The second will be a concern when exabyte-scale data structures are common to work with. Note that current processors generally can't handle this much address space, but the amd64 instruction set itself can (I think), so the CPUs can continue to scale up. RAM capacity doesn't really seem to be increasing in recent years - I'm not sure if that is more market-driven or a technological limitation. RAM speed has improved somewhat, especially in niches like GPUs. Computers with 1GB of RAM were a thing in Y2K and today it is pretty uncommon for a standard desktop to have more than 8GB, and if you want to even cram more than about 128GB into a motherboard you start needing more enterprise-grade hardware. That isn't a very large increase in 20 years - doubling every 3 years (in terms of max capacity). We're using 37 bits today (on desktops), so at 3 years per bit that is another 80 years until we exhaust 64 bits, assuming that we continue to grow exponentially at the same rate. Though you do have to think about what use cases actually need that kind of working set. At 64-bit depth 300dpi 3D graphics would require 200MB/in^3, If you had a house-sized VR space (20k ft^3) rendered at that detail you'd need 7TB of RAM to store a frame of video, which is still only 50 bits. Maybe if you want a holodeck that 1000 people can play around in at once you'd run into the 64-bit limit (of course you'd have a ton of IO issues to fix long before then). So, that makes me wonder what the practical requirements are in order to implement The Matrix. :) Of course, if you're sticking people in it maybe you can borrow some of their own memory capacity and processing abilities to drive it. Kind of makes you wonder why you'd even need the human brains in the first place if you're able to deal with that kind of data in a simulation... -- Rich
Re: [gentoo-user] why both /usr/lib and /usr/lib64 on a 64bit system?
Peter, On Monday, 2021-02-15 12:15:43 +, you wrote: > ... > No, it should be arch-neutral. Agnosticism is about religion and has nothing > to do with it. First sentence: arch-independent? Second sentence: yep :-) Sincerely, Rainer
Re: [gentoo-user] why both /usr/lib and /usr/lib64 on a 64bit system?
On Sunday, 14 February 2021 21:48:36 GMT Frank Steinmetzger wrote: > Am Sun, Feb 14, 2021 at 12:51:30PM -0500 schrieb Jack: > > As I remember, /lib and /usr/lib hold not only 32 bit libraries, but > > non-arch or arch-irrelevant (I know there's a better term) files. > > arch-agnostic? ;-) No, it should be arch-neutral. Agnosticism is about religion and has nothing to do with it. -- Regards, Peter.
Re: [gentoo-user] why both /usr/lib and /usr/lib64 on a 64bit system?
On Sun, Feb 14, 2021 at 06:09:58PM -0700, Grant Taylor wrote > On 2/14/21 10:51 AM, Jack wrote: > > I don't think you can completely get rid of it. > > My (long term) desire is to do away with /lib32 and /lib64, ultimately > only using /lib. Likewise for the other library directories in /usr or > wherever they are. I don't see a need for the specific bit variants in > the future. How long before we see /lib and /lib64 *AND* /lib128 ? -- Walter Dnes I don't run "desktop environments"; I run useful applications
