emerge @world fails

Sputnick · n00b Joined: 10 May 2004 Posts: 64

Im tryin to emerge -UDN @world and going zlib which failed.

Output of emerge --info

https://pastebin.com/20mRMd97

Theres a link to build log.

https://pastebin.com/qDed5BVX

and make.conf

https://pastebin.com/k6uHbG5i

Trying to finish installing gentoo...

socket-754 Sempron 2600+
1,5gigs memory

The Doctor · Moderator Joined: 27 Jul 2010 Posts: 2678

Well, first off your configuration is a mess. Lets start by fixing some of the more egregious problems. 4.14.65-gentoo i686 tells me that you are running a 32 bit kernel. ACCEPT_KEYWORDS="x86" is the 32 bit stable branch and CHOST="x86_64-pc-linux-gnu" is telling the computer to build 64 bit code. So something is very wrong here. As in, start over from scratch wrong.

You should have CHOST="i686-pc-linux-gnu" in your make.conf, but the 64 bit CHOST means you must have grabbed the amd64 stage3 which is 64 bit. This means you have 64 bit packages on a system that speaks 32 bit words. It shouldn't even be able to boot. I'm afraid there is just no way back from that.

If you where messing with your CHOST and changed to CHOST="x86_64-pc-linux-gnu" then restoring it to CHOST="i686-pc-linux-gnu" and running emerge -e world might help.

For your profile you have. default/linux/x86/17.0/desktop/plasma/systemd, all well and good, except KDE is never going to run on 1.5 gig of ram. Not to mention the build time will be a few days. You may want to look into openbox, i3, or fluxbox. The real problem is that you have USE="openrc systemd" and you need to choose one. These are likely to conflict. If your profile is accurate and you want to use systemd then disable the openrc flag to avoid conflicts.

You want to use a x86 stage3 for a 32 bit system. The current stage3 is stage3-i686-20181019T143649Z.tar.xz at the time of this posting and this is the one that is compatible with your goals, assuming you want a 32 bit system.
_________________
First things first, but not necessarily in that order.

Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box.

Sputnick · n00b Joined: 10 May 2004 Posts: 64

Thank you for your answer, it has been very helpful and eyeopening.

Been doing some reading, while system compiles -e @world. Thought it might be better to flush it all and start from the scratch. Pick the right tarball with correct chost. Probably take a look on Xfce or fluxbox. Instead of KDE.

Thanks, sput

NeddySeagoon · Posted: Sat Nov 24, 2018 11:11 am Post subject:

Sputnick,

It may not be as black and white as The Doctor paints it.

You have an AMD Sempron processor. Its currently running a Linux-4.14.65-gentoo-i686 (32 bit) kernel, so you can only run 32 bit code.
ABI_X86="32" Says to build 32 bit libraries.

Here's the hard bit. Not all Semprons are equal. Some are 64 bit capable, some are not.
The 2600+ in your pastebin suggests that your CPU may be 64 bit capable but its not 100%.
What does

Sputnick · n00b Joined: 10 May 2004 Posts: 64

NeddySeagoon · Posted: Sat Nov 24, 2018 1:45 pm Post subject:

Sputnick,

Yes, that's a 64 bit Sempron.

If you have <2G RAM a 32 bit install will be best as at 1G, in 32 bit mode, the kernel, has to do some extra work to use the rest of RAM.
At 2G, it has to do more extra work. This does not apply to 64 bit mode as the kernel can address more RAM that you can fit in any motherboard that exists today.

You have

Jaglover · Posted: Sat Nov 24, 2018 2:09 pm Post subject:

OTOH, the best solution may be adding some RAM and going 64 bit. Depending on what this PC is for you may get bitten by proprietary applications not supporting 32 bit any more. Finding this RAM should not be difficult, even I have a bunch af modules in my drawer, not sure why I haven't thrown them away yet. I can't be alone, very few people keep their drawers clean.

_________________
My Gentoo installation notes.
Please learn how to denote units correctly!

Sputnick · n00b Joined: 10 May 2004 Posts: 64

Actually i have installed 2gigs. But somehow it uses only half. They are both the same model memory sticks. Weird.

Also i read that my mobo asus 8kv-mx, supports only maximum of 2gigs of memory.

So im pretty much busted..

Sput

NeddySeagoon · Posted: Sat Nov 24, 2018 4:14 pm Post subject:

Sputnick,

1485808 total RAM is 1.4GB.

The other RAM, not shown, is used by the the on board graphics card and the kernel. If you have an AGP graphics card fitted you can turn off the on board graphics in the BIOS and get the graphics memory back.
Hmm, your manual says that's only 64Mb Max.

There is more good news. Your system is Socket 754 based, not Socket A, so its 64 bit everywhere.
The Socket A based 64 bit Semprons were stuck in a motherboard intended for 32 bit operation, even though some were 64 bit CPUs
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

Hu · Administrator Joined: 06 Mar 2007 Posts: 21706

Sputnick · n00b Joined: 10 May 2004 Posts: 64

Lot of things happened during this time. My motherboard died. So i got some new stuff

Still 1Gig memory, but Pentium 4 C Northwood. 2,4Ghz hyperthreading.

I did all from the beginning. Just to avoid some errors. Like choosing x86 i686 tarball. and playing that in my make.conf.

So i got to emerge -UDn @world

was about to write about ghostscript fails, but luckily i noticed my computer clock was 15 years behind. That fixed it.. so nothing more than computer upgrade or downgrade that is...

Yeah i had one question.

What should i do with bootloader. Ive used to go with grub. But its all different now. Which i should use? boot&Efi or boot&Uefi or just boot?

My motherboard is obviously year 2003 model. Gigabyte GA-8TRS300M

How should i install grub? or something else. Have no prefs, other than it must work.

The Doctor · Moderator Joined: 27 Jul 2010 Posts: 2678

EFI and UEFI wasn't around in 2003, so that is out the window. Grub-legacy, lilo, and extlinux are your best choices here. My preference is extlinux since it is nice and simply and just works. I always preferred it to grub.

I'm not sure of you can use a gpt scheme with a motherboard that old. It will probably be fine since reverse comparability was a priority.
_________________
First things first, but not necessarily in that order.

Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box.

Sputnick · n00b Joined: 10 May 2004 Posts: 64

Lvm-6.0.1 Fails

NeddySeagoon · Posted: Mon Dec 03, 2018 12:13 pm Post subject:

Sputnick,

Sputnick · n00b Joined: 10 May 2004 Posts: 64

NeddySeagoon · Posted: Tue Dec 04, 2018 11:24 am Post subject:

Sputnick,

On most system you can mix BIOS and GPT. I'm aware of a few Dells where it doesn't work.
Understand a little of of the data layout on disk and boot sequence before I answer your question.

With a GPT partition table, you have a 'Protective MSDOS' partition table at the start of the drive, followed by the real GPT, followed by the actual partitioned space. There is no unallocated space.
With an MSDOS partition table, the following GPT partition table is missing but the actual partitioned space starts in the same place.
The unallocated space, where the GPT partition table would go is often used by boot loaders, when using BIOS/MSDOS mode.

With BIOS/GPT, to make up for the lack of unallocted space, you must allocate a bios_boot partition. The boot loader will use this space, just as if it was the unallocated space.

An EFI bootloader can read the EFI partition directly, it doesn't need any help.
BIOS can only read LBA 0 from the HDD. That's not enough space for a boot loader. Only 446 bytes are available because the partition table uses the last 66 bytes.
What goes here is a loader that calls the BIOS to load a better loader from either the bios_boot partition or the unallocated space before the first partition.
This better loader then loads another loader that can show you a menu.

Jaglover · Posted: Tue Dec 04, 2018 11:36 am Post subject:

NeddySeagoon · Posted: Tue Dec 04, 2018 3:22 pm Post subject:

Jaglover,

Agreed. bios_boot is a grub2 thing.

Well, lilo always uses block list loading and both grubs will fall back to that too.
Its really ugly when you forget to rewrite the block list.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

Sputnick · n00b Joined: 10 May 2004 Posts: 64

Thank u all for helping me out. Tried to run memtest86. Minimal installation cd doesnt load it, even it says its there.

But update for the situation:

I finished the @world after few fails. (segmentation fault always) just tryin again pays off atm. But prolly faulty ram or overheating.

compiling kde atm. 42 pkgs left. And its very difficult to overcome qtwebengine, it counts over 15000 lines and fails to segmentation fault every time at different spot.

gotta find better ram.

Sput