subject:"Re\: \[gentoo\-user\]"

Wols Lists wrote:
> On 16/06/2024 09:40, Michael wrote:
>> Now to get temp sensors and stuff to work.  I want to keep a eye on
>> temps for a bit.  I think the boot media was reporting the wrong
>> info.
>> Even the ambient temp was to high for this cool room.  It showed
>> like
>> 100F or something when my A/C is set to 68F or so.  Plus, the
>> side is
>> off the case at times.  New battle.  
>
>> The side panel should help improve air flow through the case
>> (depending on the
>> design).  I've seen CPU temperatures on big tower servers with dual
>> xeon CPUs
>> going up when the side panel was removed.
>
> My previous case had a cone connecting the CPU to a vent in the side.
> Whether that sucked warm case air over the CPU and vented it directly
> out, or sucked cool outside air over the CPU and vented it into the
> case, I don't know. Either way, the air flowing over the CPU was
> outside the case just before or after doing so.
>
> Cheers,
> Wol
>
>


I've seen factory puters have a duct thing that goes from the CPU fan to
the rear of the case also.  That way the heat from the CPU is never
vented inside the case.  I've also seen a few that are like you
mentioned.  I kinda liked the ones that remove the CPU heat from the
case to the rear myself.  That helps keep the other components cooler
since the heat from the CPU isn't released into the case. 

A lot of case makers use different tactics to control heat.  To me tho,
the best is a fan on the top of the case.  Every case that I've had that
had top fans ran cooler.  Heat wants to rise anyway so it's natural for
heat to go to the top.  As I mentioned elsewhere, I really like a side
fan as well.  They keep the mobo cool by providing fresh air to
everything from the video card to other components on the mobo.  When I
remove the side from my Cooler Master, the one thing that really gets
affected, the video card.

I think most case makers really put thought into cooling.  They want the
flashy crap to sadly but regardless of looks, cooling has to be a very
high priority.  Some come up with some inventive ways to do it. 

Dale

:-)  :-)

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

2024-06-16 Thread Wols Lists


On 16/06/2024 09:40, Michael wrote:

Now to get temp sensors and stuff to work.  I want to keep a eye on
temps for a bit.  I think the boot media was reporting the wrong info.
Even the ambient temp was to high for this cool room.  It showed like
100F or something when my A/C is set to 68F or so.  Plus, the side is
off the case at times.  New battle.  



The side panel should help improve air flow through the case (depending on the
design).  I've seen CPU temperatures on big tower servers with dual xeon CPUs
going up when the side panel was removed.


My previous case had a cone connecting the CPU to a vent in the side. 
Whether that sucked warm case air over the CPU and vented it directly 
out, or sucked cool outside air over the CPU and vented it into the 
case, I don't know. Either way, the air flowing over the CPU was outside 
the case just before or after doing so.


Cheers,
Wol

Re: [gentoo-user] Re: Keep getting LC_ALL error during install.

2024-06-16 Thread Wols Lists


On 16/06/2024 23:39, Nuno Silva wrote:

And of course, all the rules get bent by the various
manufacturers. Bear in mind that basic EFI predates vFAT so even in
UEFI vFAT isn't actually mandatory. Apple don't use it, iirc. There's
nothing stopping GNU's OpenBIOS project or whatever it is using
ext4. But vFAT is the official "lowest common denominator" which
everything must support if it's not "single vendor for hardware and
software". Which is why, of course, MS can't play fun and games - if
they say Windows won't support vFAT they'll get hammered for
anti-trust.



But there are systems using exFAT, right? You mean UEFI firmwares will
happily accept other filesystems?


I don't know. But the formal specification of UEFI says it must accept 
vFAT (I believe exFAT was not acceptable because Microsoft had patented 
it). It does not say it can't accept other stuff. Which is why Apple 
doesn't use vFAT.


And it explicitly states the version of vFAT. I don't know which 
version, but it's along the lines of "version X dated Y", so that is 
locked in stone.


So basically, the UEFI spec says it CAN accept multiple filesystems, but 
it MUST accept vFAT if it wants the moniker "Universal". So unless (and 
probably even if) it's Apple hardware, it does support vFAT.


Cheers,
Wol

[OT] Re: [gentoo-user] Keep getting LC_ALL error during install.

2024-06-16 Thread Peter Humphrey

On Sunday, 16 June 2024 20:39:52 BST Wol wrote:

> ... Back in the ancient days, you had a switch panel you toggled to put in
> the boot code.

I remember that. It was 1974. 24 key switches and lots of buttons. You set an 
address on the key switches and hit SET, then ditto its contents and STORE. 
All set and ready, GO. That was a Ferranti Argus 500, like what was in the 
latest submarines, but these were for AGR power stations. 24-bit words, 16MB 
of 2 microsecond core store, 2MB disks, ASTRAL assembler language. Full 
closed-loop reactor control.

They don't make them like that any more.

PS. Our gas-cooled reactors were intrinsically stable: rising temperature 
caused reduction of power, without any intervention. On the other hand, all 
water-cooled reactors are inherently unstable: rising temperature causes an 
increase of power. They have to be controlled by brute force.

PPS. Guess which I prefer.

-- 
Regards,
Peter.

Re: [gentoo-user] Keep getting LC_ALL error during install.

2024-06-16 Thread Wol


On 15/06/2024 20:35, Dale wrote:
I'm not opposed to efi.  I remember when the old Grub reached its end of 
life. Grub2 is different but it works.  I don't use the eye candy part 
so that makes it even easier.  The biggest thing, I copy my kernels and 
such over manually and I keep a couple older ones that I want to be 
available.  I also plan to install memtest, a rescue image or two and 
those need to be available as well.  I may still use Grub, I may not.  
Right now, I'm clueless.  I'm just trying to follow the docs which given 
all the options available are confusing to follow.


At the end of the day, all these things are pretty much the same. Back 
in the ancient days, you had a switch panel you toggled to put in the 
boot code.


Then they put a basic interpreter in ROM.

Then they got rid of basic and put code in that said "here's a bit of 
disk controller code, go to chs(0,0,0), read one block and execute it".


Now UEFI is just a bit more fancy code that says "here's a gpt table 
reader, a vFAT driver, and a mini program that looks in any FAT 
partition it can find for an EFI directory, and runs whatever it finds 
in there".


So the principle hasn't changed, but the detail has.

And of course, all the rules get bent by the various manufacturers. Bear 
in mind that basic EFI predates vFAT so even in UEFI vFAT isn't actually 
mandatory. Apple don't use it, iirc. There's nothing stopping GNU's 
OpenBIOS project or whatever it is using ext4. But vFAT is the official 
"lowest common denominator" which everything must support if it's not 
"single vendor for hardware and software". Which is why, of course, MS 
can't play fun and games - if they say Windows won't support vFAT 
they'll get hammered for anti-trust.


More and more everything is turning into "System on a chip", and that 
includes the bios! It has just enough of a driver now to read everything 
it needs from the attached storage, and that's your modern UEFI.


Cheers,
Wol

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

Rich Freeman wrote:
> On Sun, Jun 16, 2024 at 12:55 AM Dale  wrote:
>> Besides, for the wattage
>> the CPU uses, the cooler I have is waay overkill.  I think my cooler
>> is rated well above 200 watts.  The CPU is around 100 watts, 105 I think
>> or maybe 95.
> So, I am just picking someplace a little random to reply to all of this.
>
> Normal temps vary by CPU model and you need to look up what is expected.
>
> All modern CPUs will throttle to maintain below a certain temp, and so
> if you have thermal issues you'll just get lower performance.
>
> A cooler might dissipate a certain amount of power, but that is going
> to be at a particular temp.  Obviously a radiator that is at ambient
> temperature will dissipate no heat at all.
>
> The external temp of the CPU has nothing to do with the internal temp
> of the CPU, and a modern CPU can generate MUCH more heat than it can
> internally transfer to the surface of the die, and so internally it
> will heat up even if you use liquid cooling.
>
> As far as governors go, I'm not sure what is even recommended with
> Linux with modern CPUs.  Most modern CPUs and their firmware manage
> heat/power based on performance limits.  AMD calls this
> Performance-based Overclocking, but it is basically how they work even
> up to factory clock rates.  Assuming you meet the cooling/power
> requirements the CPU can sustain a particular frequency on all its
> cores at once, and a higher frequency on only one core if the rest are
> idle, and then it has a maximum frequency that a small number of cores
> can temporarily exceed but internal temperature will rise when this
> happens until throttling kicks in (I think this is at least in part
> firmware modeled and not exclusively based on sensor data).  This is
> all by design in a desktop CPU, and allows a CPU to have significantly
> better burst performance than sustained performance, which is a good
> approach as desktop loads tend to be bursty.  I imagine server
> processors (like enterprise SSDs) are optimized more around sustained
> performance as they tend to be operated more at load.
>
> I suspect that the most recent CPU generations will work best if the
> hardware is allowed to manage frequency, with the OS at most being
> used to communicate whether a core is idle or not.
>

I have to say, mobos and CPUs have come a long ways since my last build
about 10 or 11 years ago.  When the ASUS first booted and I went into
the BIOS thing, is it still called BIOS, it was very different.  I think
my current rig allows you to use the mouse.  It's slow tho.  This ASUS
is vastly improved.  It gives you a LOT more control and I'm not even
interesting in trying to overclock or anything.  Just the fan controls
are a huge improvement.  I suspect most newer mobos are all that way.

I'm going to have to get used to seeing CPU temps in the 190F area I
guess.  But dang, that's hot.  I suspect tho that if the sensor was in
the same place on my current rig, it may measure that high as well, deep
inside the chip.  It may be giving a temp where the CPU is always
cooler, closer to the top where the CPU cooler is touching or
something.  Placement of the sensor is key.   

Still, if I could get it down to 140F or even 150F, I'd be happier. 

Dang rig is snappy tho.  :-D 

Dale

:-)  :-)

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

Mark Knecht wrote:
>
> Dale - sorry to bother you.
>
> Mark

No bother at all.  Could learn something.  FYI.  I read most every post
on this list.  Unless it is something I know absolutely nothing about or
don't use at all, I read the posts.  I just might learn something. 

I might add, stress-ng does a good job of putting a load on a CPU. 
According to htop, it maxes every core/thread out to 100% and stays
there.  I think it does memory to.  Never used it for that tho.  Might
could test the m.2 stick with it too.  ;-) 

Dale

:-)  :-)

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

Peter Humphrey wrote:
> On Sunday, 16 June 2024 14:35:34 BST Dale wrote:
>
>> I mentioned I found the correct drivers for the CPU and other temps
>> sensors but needed to reboot.
> What sensors are you using now? I just rely on what gkrellm finds; where it 
> shows more than one CPU or GPU temp I choose the highest one.
>

I finally got around to setting up the GUI part.  I ran gkrellm, love
that thing, and figured out the temps.  When on command line tho, I
stuck a command that filters out the working stuff and spits the info
out for me.  This is the command I use.

sensors -f | egrep '(Tctl|Tccd1|GPU
core|fan1|temp1|fan2|fan3|Adapter|Sensor 1|Sensor 2)'

It looks like this: 

Gentoo-1 ~ # /root/temps
Adapter: PCI adapter
Tctl:    +130.3°F 
Tccd1:    +94.1°F 
Adapter: PCI adapter
GPU core:    900.00 mV (min =  +0.78 V, max =  +1.16 V)
fan1:    2670 RPM
temp1:   +109.4°F  (high = +203.0°F, hyst = +37.4°F)
Adapter: ISA adapter
fan1:    0 RPM  (min =    0 RPM)
fan2: 1262 RPM  (min =    0 RPM)
fan3:  940 RPM  (min =    0 RPM)
Adapter: PCI adapter
Sensor 1:    +107.3°F  (low  = -459.7°F, high = +117503.3°F)
Sensor 2: +94.7°F  (low  = -459.7°F, high = +117503.3°F)
Gentoo-1 ~ #

That gets CPU, GPU, fans, and I think the m.2 stick is on the bottom. 
Basically, I get everything that is important.  If needed, I just run
sensors -f and get all of it, even things that don't work or have
nothing connected to them. The biggest thing, getting the right drivers
in the kernel so that it can see the stuff correctly. 

I did a duck search.  I don't use Google anymore because of the captcha
thing always popping up. Anyway, I found this web page. 

https://www.linux.com/topic/desktop/advanced-lm-sensors-tips-and-tricks-linux-0/

If you scroll down a bit, it tells what some of the sensors are for. 

I also found a video on youtube that talks about how to set the fan
controllers up in the BIOS. I didn't know that I was supposed to set up
the fans before booting and installing things.  Anyway, I made it a
little faster to respond and make the fans really spin up when things
warm up.  When I ran stress, in seconds I could hear the fans speed up. 
I had to mute the TV to hear them tho.  The case has six 140mm fans. 
Three in front, two on top and one in the back.  The power supply kinda
does its own thing.  Linky to video.

https://www.youtube.com/watch?v=65vsrzYOLZg

I may adjust the CPU fan a little bit next time I boot up.  I'll see
what it looks like and go from there.  It still runs warmer than I think
it should.  Also, I put my finger on the base of the CPU cooler, it
wasn't even warm and it shows it is around 190F.  That sensor must be
deep in the CPU die or something.  Nothing in the mobo is very warm to
the touch.  The VRM heat sinks are a tad bit warm but nothing to worry
about. 

I may do some tweaking but as far as the cooling goes, I think I'm OK. 
It shouldn't blow smoke.  I hope. 

Oh, I tried the kernel video drivers, that thing is slow.  I may switch
to the Nvidia drivers and see how that goes.  Thing is, I have another
card coming in.  I may wait until it gets here. 

Dale

:-)  :-)

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

2024-06-16 Thread Rich Freeman

On Sun, Jun 16, 2024 at 12:55 AM Dale  wrote:
>
> Besides, for the wattage
> the CPU uses, the cooler I have is waay overkill.  I think my cooler
> is rated well above 200 watts.  The CPU is around 100 watts, 105 I think
> or maybe 95.

So, I am just picking someplace a little random to reply to all of this.

Normal temps vary by CPU model and you need to look up what is expected.

All modern CPUs will throttle to maintain below a certain temp, and so
if you have thermal issues you'll just get lower performance.

A cooler might dissipate a certain amount of power, but that is going
to be at a particular temp.  Obviously a radiator that is at ambient
temperature will dissipate no heat at all.

The external temp of the CPU has nothing to do with the internal temp
of the CPU, and a modern CPU can generate MUCH more heat than it can
internally transfer to the surface of the die, and so internally it
will heat up even if you use liquid cooling.

As far as governors go, I'm not sure what is even recommended with
Linux with modern CPUs.  Most modern CPUs and their firmware manage
heat/power based on performance limits.  AMD calls this
Performance-based Overclocking, but it is basically how they work even
up to factory clock rates.  Assuming you meet the cooling/power
requirements the CPU can sustain a particular frequency on all its
cores at once, and a higher frequency on only one core if the rest are
idle, and then it has a maximum frequency that a small number of cores
can temporarily exceed but internal temperature will rise when this
happens until throttling kicks in (I think this is at least in part
firmware modeled and not exclusively based on sensor data).  This is
all by design in a desktop CPU, and allows a CPU to have significantly
better burst performance than sustained performance, which is a good
approach as desktop loads tend to be bursty.  I imagine server
processors (like enterprise SSDs) are optimized more around sustained
performance as they tend to be operated more at load.

I suspect that the most recent CPU generations will work best if the
hardware is allowed to manage frequency, with the OS at most being
used to communicate whether a core is idle or not.

-- 
Rich

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

2024-06-16 Thread Mark Knecht

On Sun, Jun 16, 2024 at 5:59 AM Frank Steinmetzger  wrote:
>
> Am Sat, Jun 15, 2024 at 04:07:28PM -0700 schrieb Mark Knecht:
>
> >Now, the fun part. I wrote you a little Python program which on
> > my system is called Dales_Loop.py. This program has 3
> > parameters - a value to count to, the number of cores to be used,
> > and a timeout value to stop the program. Using a program like
> > this can give you repeatable results.
>
> FYI, there is a problem with your approach: python is not capable of true
> multiprocessing. While you can have multiple threads in your programm, in
> the end they are executed by a single thread in a time-sharing manner.
>
> This problem is known as the GIL—the Global Interpreter Lock. Unless you
use
> an external program to do the actual CPU work, i.e. let the linux kernel
do
> the actual parallelism and not python, your program is not faster than
doing
> everything in a single loop.
>
> See this page for a nice example which does basically the same as your
> program (heading “The Impact on Multi-Threaded Python Programs”),
including
> some comparative benchmarking between single loop and threaded loops:
> https://realpython.com/python-gil/
>

I'm sorry Frank but apparently you didn't read the code. Indeed the GIL
i an  issue but this program uses the multiprocessing library and starts
processes, not threads. Running the program for 30 seconds with
different values of num_processes I see

1   2212
2   
3   6107
4   8199
5   10174

I additionally I see roughly the number of num_process python
jobs running in btop at all times the program is running clearly
demonstrating each has its own process ID and are being
managed by the kernel. As each process is completed a new
one is started with a new process number.

I use this library successfully in a home built AI program I'm writing
and I clearly get roughly through the number of processes * data
sets during training, validation and testing.

If someone wants to use a packaged stress test program I
see nothing wrong with that. If you don't want to read the
code and understand it for yourself, then I see nothing wrong with that
either, but please, if you're gonna talk to me about a little code
snippet then at least read it , run it and understand it first.

Dale - sorry to bother you.

Mark

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

2024-06-16 Thread Peter Humphrey

On Sunday, 16 June 2024 14:35:34 BST Dale wrote:

> I mentioned I found the correct drivers for the CPU and other temps
> sensors but needed to reboot.

What sensors are you using now? I just rely on what gkrellm finds; where it 
shows more than one CPU or GPU temp I choose the highest one.

-- 
Regards,
Peter.

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

Michael wrote:
> On Sunday, 16 June 2024 09:40:57 BST you wrote:
>> On Sunday, 16 June 2024 05:55:45 BST Dale wrote:
>>> William Kenworthy wrote:
 On 16/6/24 07:07, Mark Knecht wrote:
> 
>
>> I still don't understand the efi thing.  I'm booted up tho.  I'm
> happy.
>
>> Now to get temp sensors and stuff to work.  I want to keep a eye on
>> temps for a bit.  I think the boot media was reporting the wrong
>> info.
>> Even the ambient temp was to high for this cool room.  It showed like
>> 100F or something when my A/C is set to 68F or so.  Plus, the side is
>> off the case at times.  New battle.  ;-)
>> The side panel should help improve air flow through the case (depending on
>> the design).  I've seen CPU temperatures on big tower servers with dual
>> xeon CPUs going up when the side panel was removed.
>>


This is very true of a LOT of cases.  This one is so open and the way
the fans blow, it doesn't seem to make much difference.  I usually only
take the side off when I'm looking at something or measuring temps of
different things with my IR thing.  Some things are warmer than I'd like
but they have factory heatsinks.  On my current rig tho which has a side
fan, one of those large 200mm things, it makes a big difference on both
the CPU and the video card.  It is truly amazing how much difference
that side fan makes even tho it is blowing only a moderate amount of
air.  With the side on, I think my Cooler Master HAF-932 case cools
better than the Fractal.  If the Fractal had a side fan, it would win
hands down.  Thing is, the side is glass so no cutting allowed. 

>> It used to be the case the thermal paste would dry out and needed replacing
>> within 5 years or so.  These days the top end thermal paste lasts longer and
>> it is much more expensive, but I'm yet to find out how long it lasts.  ;-)

I agree.  I bought a couple syringes of some top dollar thermal grease
several years ago, likely with the last build.  I have enough to last a
really long time.  One tube is Arctic Silver I think.  Then I bought
another brand that is supposed to be even better than the Arctic
Silver.  I can't recall the name.  Some of my tubes have silver in it to
some degree.  I've never had any of the good ones to dry out.  I have
had some cheap stuff I use on transistors to dry out tho.  It's some
pink stuff with no brand on it.  No silver either. 


>Now, the fun part. I wrote you a little Python program which on
>> [snip ...]
>>
>>> My complaint, the temps sensors is reporting is way higher than my IR
>>> thermometer says.  Even what I think is the ambient temp is way off.
>>> I've googled and others report the same thing.  During one compile, I
>>> pointed the IR sensor right at the base of the CPU cooler.  It may not
>>> be as hot as the CPU is but it is closer than anything else.  I measured
>>> like 80F or something
>> That's approximating the TCase, but you're still not close enough to measure
>> that temperature.  You'd need to delid the CPU for this ... definitely NOT
>> recommended.
>>
>>> while sensors was reporting above 140F or so.
>> That's the TjMax and for your 5800X CPU this is comfortably within the TjMax
>> temperature of 194°F (90°C):
>>
>> https://www.amd.com/en/products/processors/desktops/ryzen/5000-series/amd-ry
>> zen-7-5800x.html#product-specs

See below for more info.  I thought it had the wrong sensor driver and
those temps are just wrong.  The BIOS, or whatever it is called
nowadays, also shows much lower temps. 

>>> I
>>> can see a little difference but not that much.  Besides, for the wattage
>>> the CPU uses, the cooler I have is waay overkill.  I think my cooler
>>> is rated well above 200 watts.  The CPU is around 100 watts, 105 I think
>>> or maybe 95.
>> 105W - see link above.

I thought it was either 5 watts high or low.  I wasn't 100% sure. 

>>> Plus, this room is fairly cold.  A/C currently set to
>>> 68F.  One can dispute the CPU temp I guess but not the ambient temp.  If
>>> one is off, I suspect both are off.
>> Not necessarily - where is the ambient temperature sensor located?
>>

My current Gigabyte has one on the mobo somewhere.  I never have found
it tho.  With the side off and a large fan blowing on it, it gets real
close to room temp.  With the side on, it does warm up a little, likely
just because of the way the air flows around in there and some warm
components around it.  I'm not real sure on this ASUS but I've never
seen a mobo without a ambient temp sensor.  I've read the BIOS uses it
to help determine the speed of the case fans if they are connected to
the mobo.  I think my front fan and top fan is connected to the mobo on
current rig and when it warms up inside, even if the CPU isn't that
warm, the front fan and top fan speeds up.  I sometimes turn the A/C off
and forget.  When I do that, the mobo controlled case fans spins up even
tho the CPU is idle.  It seems to like 85F or so.  The side fan is
connected to

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

2024-06-16 Thread Frank Steinmetzger

Am Sat, Jun 15, 2024 at 04:07:28PM -0700 schrieb Mark Knecht:

>Now, the fun part. I wrote you a little Python program which on
> my system is called Dales_Loop.py. This program has 3
> parameters - a value to count to, the number of cores to be used,
> and a timeout value to stop the program. Using a program like
> this can give you repeatable results.

FYI, there is a problem with your approach: python is not capable of true 
multiprocessing. While you can have multiple threads in your programm, in 
the end they are executed by a single thread in a time-sharing manner.

This problem is known as the GIL—the Global Interpreter Lock. Unless you use 
an external program to do the actual CPU work, i.e. let the linux kernel do 
the actual parallelism and not python, your program is not faster than doing 
everything in a single loop.

See this page for a nice example which does basically the same as your 
program (heading “The Impact on Multi-Threaded Python Programs”), including 
some comparative benchmarking between single loop and threaded loops:
https://realpython.com/python-gil/

-- 
Grüße | Greetings | Salut | Qapla’
Please do not share anything from, with or about me on any social network.

At night, when everybody sleeps, usually there’s nobody awake.


signature.asc
Description: PGP signature

Re: [gentoo-user] Clang update with musl

On Sunday, 16 June 2024 12:39:40 BST efeizbu...@disroot.org wrote:
> Hi everyone,
> 
> I've been trying to update my clang but I keep getting linking errors.
> I'm on the default/linux/amd64/23.0/split-usr/musl profile. My system
> has been acting kind of weird ever since the profile updates 17 -> 23.
> Can anyone point me in the right direction here?
> 
> emerge --info '=sys-devel/clang-17.0.6::gentoo':
> https://bin.disroot.org/?27973d77c13e8ffe#2xHi8eEnKv9g7FWtcB4v5mTWAarNXfsuy2
> QaV2qDKfcp
> 
> emerge -pqv '=sys-devel/clang-17.0.6::gentoo':
> https://bin.disroot.org/?36922e347145d88e#J8bs9oYZWjR294rWMnCGGvZcpWTWThji2D
> Gog2Q5EEYM
> 
> last bit of the build.log (Can't post it all since it is 5.4M):
> https://bin.disroot.org/?e7c428e663f760b4#6mJbF2mhqGpMqHcc9QM9cXXYSp6KdqRx8q
> p9JmxN3RgB
> 
> Thank you
> 
> --
> Efe

I don't use musl to know if this is some esoteric error pertinent to it - but 
have a look at this post in case it helps:

https://forums.gentoo.org/viewtopic-p-8825213.html?
sid=9bfcd5bda8f258b41746420194e9e01a


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Uefi + uki stuck while booting (/dev/gpt-auto-root)

I'm not the right person to comment reliably on this, because I don't use 
systemd and do not use LVM, but until someone else chimes in I'll give it a go 
...  :-)

On Sunday, 16 June 2024 09:04:26 BST Alexander Puchmayr wrote:
> Hi there,
> 
> I just tried to prepare my new laptop for UFEI+secureboot by creating a
> single unified kernel image including kernel,initrd,microcode,etc.
> NB: The partition layout has a vfat/Efi partition and a luks encrypted lvm
> container holding SYS(Root), Data(home) and swap.
> 
> I added uki and ukify use flags to installkernel and systemd, checked the
> configuration again and configured the kernel by emerge --config sys-kernel/
> gentoo-kernel.
> 
> Bulding the kernel image seems to work fine, the log messages say its
> creating a initrd using dracut, creating a efi file, signing it properly
> and even installs it under /boot/efi/EFI/Linux.

Why is the ESP mounted under /boot/efi, instead of /efi?

https://wiki.gentoo.org/wiki/EFI_System_Partition#Mount_point

> When booting it, it loads the kernel and then seems to get stuck:
> 
> Timed out waiting for device /dev/gpt-auto-root
> Dependency failed for File System Check in /dev/gpt-auto-root
> Dependency failed for Root Partition
> Dependency failed for Initrd Root File System
> Dependency failed for Initrd Mountpoints Configured in the Real Root
> Dependency failed for Initrd Root Device

The gpt-auto-root is a script which tries to automatically detect and mount 
the root fs.  Did you create your partition(s) with GPT and did you select the 
correct partition type "Linux Root (x86-64)" to make sure the partition GUID 
code for LUKS is correct according to the Discoverable Partitions 
Specification?  If you used fdisk, you'll probably need to add the partition 
type GUID code manually, as advised in the Handbook.  Press -i in fdisk to 
find out what it currently is set as.

> Then it ends up in an emergency shell.
> 
> There's a log in /run/initramfs/rdsosreport.txt, which reveals that it does
> not find my encrypted lvm partition (LUKS encrypted lvm container holding
> SYS, DATA, SWAP, etc), which obviously needs to be setup first. Seems like
> some boot parameter is missing.

Did you configure dracut to include the necessary modules and to add the 
corresponding LUKS and LVM UUIDs?

https://wiki.gentoo.org/wiki/
Full_Disk_Encryption_From_Scratch#Initramfs_configuration

> Checking systemd's USE flags: Relevant flags lvm + cryptsetup + boot +
> secureboot use flags are set
> 
> To me it looks like as if its missing information which partition to use for
> decrypting/mounting, and which lvm volume to use as real-root.
> 
> Is this a dracut configuration? A systemd configruation? An installkernel
> configuration? Something else?
> 
> Thanks
>   Alex

I think this is a dracut configuration issue, because systemd's 'kernel-
install' setup is relatively straight forward:

https://wiki.gentoo.org/wiki/Installkernel#Systemd_kernel-install_.28USE.3D.
2Bsystemd.29

If the problem is with dracut as I suspect, you may find 'sys-kernel/ugrd' 
easier than dracut for your type of installation, but dracut should work too 
if correctly configured.

HTH.

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

On Sunday, 16 June 2024 09:40:57 BST you wrote:
> On Sunday, 16 June 2024 05:55:45 BST Dale wrote:
> > William Kenworthy wrote:
> > > On 16/6/24 07:07, Mark Knecht wrote:
> > >> 
> > >> 
> > >> > I still don't understand the efi thing.  I'm booted up tho.  I'm
> > >> 
> > >> happy.
> > >> 
> > >> > Now to get temp sensors and stuff to work.  I want to keep a eye on
> > >> > temps for a bit.  I think the boot media was reporting the wrong
> > >> > info.
> > >> > Even the ambient temp was to high for this cool room.  It showed like
> > >> > 100F or something when my A/C is set to 68F or so.  Plus, the side is
> > >> > off the case at times.  New battle.  ;-)
> 
> The side panel should help improve air flow through the case (depending on
> the design).  I've seen CPU temperatures on big tower servers with dual
> xeon CPUs going up when the side panel was removed.
> 
> > >> > Dale
> > >> 
> > >> 
> > >> 
> > >> Hi Dale,
> > >> 
> > >>Congrats on getting your new machine working. I think you've
> > >>received
> > >> 
> > >> a lot of good info on temperature effects but there is one thing I
> > >> didn't
> > >> see anyone talking about so I'll mention it here. (Note - my career was
> > >> chip design in Silicon Valley so I'm speaking from experience in both
> > >> chips and PCs that use them.
> > >> 
> > >>First, don't worry too much about high temperatures hurting your
> > >> 
> > >> processor or the chips in the system. They can stand up to 70C
> > >> pretty much forever and 100C for long periods of time. Long before
> > >> anything would get damaged at the chip level, if it ever gets damaged,
> > >> you are going to have timing problems that would either cause the
> > >> system to crash, corrupt data, or both, so temps are important
> > >> but it won't be damage to the processor. (Assuming it's a good
> > >> chip that meets all specs and is well tested which I'm sure yours
> > >> is.
> > >> 
> > >>The thing I think you should be aware of is that long-term high
> > >> 
> > >> temps, while they don't hurt the processor, can very possibly degrade
> > >> the thermal paste that is between your processor or M.2 chips
> > >> and their heat sinks & fans. Thermal paste can and will degrade
> > >> of time and high temps make it degrade faster so the temps you
> > >> see today may not be the same as what you see 2 or 3 years from
> > >> now.
> 
> It used to be the case the thermal paste would dry out and needed replacing
> within 5 years or so.  These days the top end thermal paste lasts longer and
> it is much more expensive, but I'm yet to find out how long it lasts.  ;-)
> > >>Now, the fun part. I wrote you a little Python program which on
> 
> [snip ...]
> 
> > My complaint, the temps sensors is reporting is way higher than my IR
> > thermometer says.  Even what I think is the ambient temp is way off.
> > I've googled and others report the same thing.  During one compile, I
> > pointed the IR sensor right at the base of the CPU cooler.  It may not
> > be as hot as the CPU is but it is closer than anything else.  I measured
> > like 80F or something
> 
> That's approximating the TCase, but you're still not close enough to measure
> that temperature.  You'd need to delid the CPU for this ... definitely NOT
> recommended.
> 
> > while sensors was reporting above 140F or so.
> 
> That's the TjMax and for your 5800X CPU this is comfortably within the TjMax
> temperature of 194°F (90°C):
> 
> https://www.amd.com/en/products/processors/desktops/ryzen/5000-series/amd-ry
> zen-7-5800x.html#product-specs
> > I
> > can see a little difference but not that much.  Besides, for the wattage
> > the CPU uses, the cooler I have is waay overkill.  I think my cooler
> > is rated well above 200 watts.  The CPU is around 100 watts, 105 I think
> > or maybe 95.
> 
> 105W - see link above.
> 
> > Plus, this room is fairly cold.  A/C currently set to
> > 68F.  One can dispute the CPU temp I guess but not the ambient temp.  If
> > one is off, I suspect both are off.
> 
> Not necessarily - where is the ambient temperature sensor located?
> 
> > Oh, the CPU fan isn't spinning fast
> > either.  I'd guess it isn't even running at half speed even when
> > compiling and htop shows all cores/threads at the max.
> 
> Your UEFI (BIOS) menu should have settings for tweaking the fans and
> changing their cooling profile to make them quieter, or spin them up
> sooner.  Start with default settings and tune it up/down from there to
> match your needs.

Take a look at the CPU Thermal Expectations in this article:

https://www.pcgamer.com/amd-views-ryzen-5000-cpu-temperatures-up-to-95c-as-typical-and-by-design/


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

On Sunday, 16 June 2024 05:55:45 BST Dale wrote:
> William Kenworthy wrote:
> > On 16/6/24 07:07, Mark Knecht wrote:
> >> 
> >> 
> >> > I still don't understand the efi thing.  I'm booted up tho.  I'm
> >> 
> >> happy.
> >> 
> >> > Now to get temp sensors and stuff to work.  I want to keep a eye on
> >> > temps for a bit.  I think the boot media was reporting the wrong info.
> >> > Even the ambient temp was to high for this cool room.  It showed like
> >> > 100F or something when my A/C is set to 68F or so.  Plus, the side is
> >> > off the case at times.  New battle.  ;-)

The side panel should help improve air flow through the case (depending on the 
design).  I've seen CPU temperatures on big tower servers with dual xeon CPUs 
going up when the side panel was removed.


> >> > Dale
> >> 
> >> 
> >> 
> >> Hi Dale,
> >>Congrats on getting your new machine working. I think you've received
> >> a lot of good info on temperature effects but there is one thing I
> >> didn't
> >> see anyone talking about so I'll mention it here. (Note - my career was
> >> chip design in Silicon Valley so I'm speaking from experience in both
> >> chips and PCs that use them.
> >> 
> >>First, don't worry too much about high temperatures hurting your
> >> processor or the chips in the system. They can stand up to 70C
> >> pretty much forever and 100C for long periods of time. Long before
> >> anything would get damaged at the chip level, if it ever gets damaged,
> >> you are going to have timing problems that would either cause the
> >> system to crash, corrupt data, or both, so temps are important
> >> but it won't be damage to the processor. (Assuming it's a good
> >> chip that meets all specs and is well tested which I'm sure yours
> >> is.
> >> 
> >>The thing I think you should be aware of is that long-term high
> >> temps, while they don't hurt the processor, can very possibly degrade
> >> the thermal paste that is between your processor or M.2 chips
> >> and their heat sinks & fans. Thermal paste can and will degrade
> >> of time and high temps make it degrade faster so the temps you
> >> see today may not be the same as what you see 2 or 3 years from
> >> now.

It used to be the case the thermal paste would dry out and needed replacing 
within 5 years or so.  These days the top end thermal paste lasts longer and 
it is much more expensive, but I'm yet to find out how long it lasts.  ;-)


> >>Now, the fun part. I wrote you a little Python program which on
[snip ...]

> My complaint, the temps sensors is reporting is way higher than my IR
> thermometer says.  Even what I think is the ambient temp is way off. 
> I've googled and others report the same thing.  During one compile, I
> pointed the IR sensor right at the base of the CPU cooler.  It may not
> be as hot as the CPU is but it is closer than anything else.  I measured
> like 80F or something 

That's approximating the TCase, but you're still not close enough to measure 
that temperature.  You'd need to delid the CPU for this ... definitely NOT 
recommended.  

> while sensors was reporting above 140F or so.

That's the TjMax and for your 5800X CPU this is comfortably within the TjMax 
temperature of 194°F (90°C):

https://www.amd.com/en/products/processors/desktops/ryzen/5000-series/amd-ryzen-7-5800x.html#product-specs


> I
> can see a little difference but not that much.  Besides, for the wattage
> the CPU uses, the cooler I have is waay overkill.  I think my cooler
> is rated well above 200 watts.  The CPU is around 100 watts, 105 I think
> or maybe 95.

105W - see link above.

> Plus, this room is fairly cold.  A/C currently set to
> 68F.  One can dispute the CPU temp I guess but not the ambient temp.  If
> one is off, I suspect both are off.

Not necessarily - where is the ambient temperature sensor located?

> Oh, the CPU fan isn't spinning fast
> either.  I'd guess it isn't even running at half speed even when
> compiling and htop shows all cores/threads at the max.

Your UEFI (BIOS) menu should have settings for tweaking the fans and changing 
their cooling profile to make them quieter, or spin them up sooner.  Start 
with default settings and tune it up/down from there to match your needs.


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

William Kenworthy wrote:
>
> On 16/6/24 07:07, Mark Knecht wrote:
>> 
>> > I still don't understand the efi thing.  I'm booted up tho.  I'm
>> happy.
>> > Now to get temp sensors and stuff to work.  I want to keep a eye on
>> > temps for a bit.  I think the boot media was reporting the wrong info.
>> > Even the ambient temp was to high for this cool room.  It showed like
>> > 100F or something when my A/C is set to 68F or so.  Plus, the side is
>> > off the case at times.  New battle.  ;-)
>> >
>> > Dale
>> 
>>
>> Hi Dale,
>>    Congrats on getting your new machine working. I think you've received
>> a lot of good info on temperature effects but there is one thing I
>> didn't
>> see anyone talking about so I'll mention it here. (Note - my career was
>> chip design in Silicon Valley so I'm speaking from experience in both
>> chips and PCs that use them.
>>
>>    First, don't worry too much about high temperatures hurting your
>> processor or the chips in the system. They can stand up to 70C
>> pretty much forever and 100C for long periods of time. Long before
>> anything would get damaged at the chip level, if it ever gets damaged,
>> you are going to have timing problems that would either cause the
>> system to crash, corrupt data, or both, so temps are important
>> but it won't be damage to the processor. (Assuming it's a good
>> chip that meets all specs and is well tested which I'm sure yours
>> is.
>>
>>    The thing I think you should be aware of is that long-term high
>> temps, while they don't hurt the processor, can very possibly degrade
>> the thermal paste that is between your processor or M.2 chips
>> and their heat sinks & fans. Thermal paste can and will degrade
>> of time and high temps make it degrade faster so the temps you
>> see today may not be the same as what you see 2 or 3 years from
>> now.
>>
>>    Now, the fun part. I wrote you a little Python program which on
>> my system is called Dales_Loop.py. This program has 3
>> parameters - a value to count to, the number of cores to be used,
>> and a timeout value to stop the program. Using a program like
>> this can give you repeatable results. I use btop in a second
>> terminal to watch individual core temps As provided it will
>> loop 1,000,000 on 4 cores in parallel. When it finishes the
>> count it will start another process and count again. It will
>> do this for 30 seconds and then stop. When finished it will
>> tell you how many processes it ran over the complete test.
>>
>>    If you wanted to do other things inside the loop, like floating
>> point math or things that would stress the machine in other
>> ways you can add that to the subroutine.
>>
>>    Anyway, you can start with 4 cores, up the time value
>> to run the test longer, up the count value to run each
>> process longer, and most fun, raise the number of cores
>> to start using more of the processor. On my Ryzen 9
>> 5950X, which is water cooled, I don't get much fan reaction
>> until I'm using 16 of the 32 threads.
>>
>>    Best wishes for you and your new rig.
>>
>> Cheers,
>> Mark
>>
>>
>>
>> import multiprocessing
>> import time
>>
>> def count_to_large_number(count_value):
>>     for i in range(count_value):
>>         pass  # Replace with your desired computation or task
>>
>> def main():
>>     num_processes = 4
>>     count_value = 100
>>     runtime_seconds = 30
>>
>>     processes = []
>>     start_time = time.time()
>>     total_processes_started = 0
>>
>>     while time.time() - start_time < runtime_seconds:
>>         for process in processes:
>>             if not process.is_alive():
>>                 processes.remove(process)
>>
>>         while len(processes) < num_processes:
>>             process =
>> multiprocessing.Process(target=count_to_large_number,
>> args=(count_value,))
>>             processes.append(process)
>>             process.start()
>>             total_processes_started += 1
>>
>>     for process in processes:
>>         process.join()
>>
>>     print(f"Total processes started: {total_processes_started}")
>>
>> if __name__ == "__main__":
>>     main()
>>
> or use app-benchmarks/stress
>
> BillK

That's the plan.  I'm still installing KDE in bits.  I'm going through
the meta packages right now.  That gives it heating and cooling cycles
which helps heat up the thermal grease but doesn't heat it up for very
long periods.  Tomorrow maybe, I'll use stress to really heat it up.  30
minutes with all cores and threads should stir up something.  :/

My complaint, the temps sensors is reporting is way higher than my IR
thermometer says.  Even what I think is the ambient temp is way off. 
I've googled and others report the same thing.  During one compile, I
pointed the IR sensor right at the base of the CPU cooler.  It may not
be as hot as the CPU is but it is closer than anything else.  I measured
like 80F or something while sensors was reporting above 140F or so.  I
can see a little difference but not that much.  Besides, for the wattage

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

2024-06-15 Thread William Kenworthy

On 16/6/24 07:07, Mark Knecht wrote:

> I still don't understand the efi thing.  I'm booted up tho.  I'm happy.
> Now to get temp sensors and stuff to work.  I want to keep a eye on
> temps for a bit.  I think the boot media was reporting the wrong info.
> Even the ambient temp was to high for this cool room.  It showed like
> 100F or something when my A/C is set to 68F or so.  Plus, the side is
> off the case at times.  New battle.  ;-)
>
> Dale

Hi Dale,
   Congrats on getting your new machine working. I think you've received
a lot of good info on temperature effects but there is one thing I didn't
see anyone talking about so I'll mention it here. (Note - my career was
chip design in Silicon Valley so I'm speaking from experience in both
chips and PCs that use them.

   First, don't worry too much about high temperatures hurting your
processor or the chips in the system. They can stand up to 70C
pretty much forever and 100C for long periods of time. Long before
anything would get damaged at the chip level, if it ever gets damaged,
you are going to have timing problems that would either cause the
system to crash, corrupt data, or both, so temps are important
but it won't be damage to the processor. (Assuming it's a good
chip that meets all specs and is well tested which I'm sure yours
is.

   The thing I think you should be aware of is that long-term high
temps, while they don't hurt the processor, can very possibly degrade
the thermal paste that is between your processor or M.2 chips
and their heat sinks & fans. Thermal paste can and will degrade
of time and high temps make it degrade faster so the temps you
see today may not be the same as what you see 2 or 3 years from
now.

   Now, the fun part. I wrote you a little Python program which on
my system is called Dales_Loop.py. This program has 3
parameters - a value to count to, the number of cores to be used,
and a timeout value to stop the program. Using a program like
this can give you repeatable results. I use btop in a second
terminal to watch individual core temps As provided it will
loop 1,000,000 on 4 cores in parallel. When it finishes the
count it will start another process and count again. It will
do this for 30 seconds and then stop. When finished it will
tell you how many processes it ran over the complete test.

   If you wanted to do other things inside the loop, like floating
point math or things that would stress the machine in other
ways you can add that to the subroutine.

   Anyway, you can start with 4 cores, up the time value
to run the test longer, up the count value to run each
process longer, and most fun, raise the number of cores
to start using more of the processor. On my Ryzen 9
5950X, which is water cooled, I don't get much fan reaction
until I'm using 16 of the 32 threads.

   Best wishes for you and your new rig.

Cheers,
Mark

import multiprocessing
import time

def count_to_large_number(count_value):
    for i in range(count_value):
        pass  # Replace with your desired computation or task

def main():
    num_processes = 4
    count_value = 100
    runtime_seconds = 30

    processes = []
    start_time = time.time()
    total_processes_started = 0

    while time.time() - start_time < runtime_seconds:
        for process in processes:
            if not process.is_alive():
                processes.remove(process)

        while len(processes) < num_processes:
            process = 
multiprocessing.Process(target=count_to_large_number, args=(count_value,))

            processes.append(process)
            process.start()
            total_processes_started += 1

    for process in processes:
        process.join()

    print(f"Total processes started: {total_processes_started}")

if __name__ == "__main__":
    main()

or use app-benchmarks/stress

BillK

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

2024-06-15 Thread Mark Knecht


> I still don't understand the efi thing.  I'm booted up tho.  I'm happy.
> Now to get temp sensors and stuff to work.  I want to keep a eye on
> temps for a bit.  I think the boot media was reporting the wrong info.
> Even the ambient temp was to high for this cool room.  It showed like
> 100F or something when my A/C is set to 68F or so.  Plus, the side is
> off the case at times.  New battle.  ;-)
>
> Dale


Hi Dale,
   Congrats on getting your new machine working. I think you've received
a lot of good info on temperature effects but there is one thing I didn't
see anyone talking about so I'll mention it here. (Note - my career was
chip design in Silicon Valley so I'm speaking from experience in both
chips and PCs that use them.

   First, don't worry too much about high temperatures hurting your
processor or the chips in the system. They can stand up to 70C
pretty much forever and 100C for long periods of time. Long before
anything would get damaged at the chip level, if it ever gets damaged,
you are going to have timing problems that would either cause the
system to crash, corrupt data, or both, so temps are important
but it won't be damage to the processor. (Assuming it's a good
chip that meets all specs and is well tested which I'm sure yours
is.

   The thing I think you should be aware of is that long-term high
temps, while they don't hurt the processor, can very possibly degrade
the thermal paste that is between your processor or M.2 chips
and their heat sinks & fans. Thermal paste can and will degrade
of time and high temps make it degrade faster so the temps you
see today may not be the same as what you see 2 or 3 years from
now.

   Now, the fun part. I wrote you a little Python program which on
my system is called Dales_Loop.py. This program has 3
parameters - a value to count to, the number of cores to be used,
and a timeout value to stop the program. Using a program like
this can give you repeatable results. I use btop in a second
terminal to watch individual core temps. As provided it will
loop 1,000,000 on 4 cores in parallel. When it finishes the
count it will start another process and count again. It will
do this for 30 seconds and then stop. When finished it will
tell you how many processes it ran over the complete test.

   If you wanted to do other things inside the loop, like floating
point math or things that would stress the machine in other
ways you can add that to the subroutine.

   Anyway, you can start with 4 cores, up the time value
to run the test longer, up the count value to run each
process longer, and most fun, raise the number of cores
to start using more of the processor. On my Ryzen 9
5950X, which is water cooled, I don't get much fan reaction
until I'm using 16 of the 32 threads.

   Best wishes for you and your new rig.

Cheers,
Mark



import multiprocessing
import time

def count_to_large_number(count_value):
for i in range(count_value):
pass  # Replace with your desired computation or task

def main():
num_processes = 4
count_value = 100
runtime_seconds = 30

processes = []
start_time = time.time()
total_processes_started = 0

while time.time() - start_time < runtime_seconds:
for process in processes:
if not process.is_alive():
processes.remove(process)

while len(processes) < num_processes:
process = multiprocessing.Process(target=count_to_large_number,
args=(count_value,))
processes.append(process)
process.start()
total_processes_started += 1

for process in processes:
process.join()

print(f"Total processes started: {total_processes_started}")

if __name__ == "__main__":
main()

Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

On Saturday, 15 June 2024 23:00:07 BST Jack wrote:

> A bit of searching found the wiki page for dispatch-conf, which
> includes:
> 
> Before running dispatch-conf for the first time, the settings in
> /etc/dispatch-conf.conf should be edited, and the archive directory
> specified in /etc/dispatch-conf.conf will need to be created
> (/etc/config-archive by default).
> 
> So it appears that directory may be specific to that tool, and not
> directly related to portage.

I wondered if it was a systemd feature, but apparently not. Thanks for 
clearing that up.

-- 
Regards,
Peter.

Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

2024-06-15 Thread Jack

On 2024.06.15 02:38, Vitaliy Perekhovy wrote:

On Fri, Jun 14, 2024 at 04:54:09PM -0400, Jack wrote:
> I don't have any such directory.  What package does it belong to,  
or is

> it a config setting for portage or another package?

Yes, it is a configuration of portage itself. There is an env variable
CONFIG_PROTECT that contains a list of directories that portage will
protect from automatic modification. Please check this article:
https://wiki.gentoo.org/wiki/CONFIG_PROTECT

You can query that variable by `portageq envvar CONFIG_PROTECT'.
/etc is the first entry in my CONFIG_PROTECT, but I still have no  
config-archive under /etc.  I think the folders listed in that variable  
are treated specially by portage in terms of not silently replacing  
config files, but doesn't control save/archive.

A bit of searching found the wiki page for dispatch-conf, which  
includes:

Before running dispatch-conf for the first time, the settings in  
/etc/dispatch-conf.conf should be edited, and the archive directory  
specified in /etc/dispatch-conf.conf will need to be created  
(/etc/config-archive by default).

So it appears that directory may be specific to that tool, and not  
directly related to portage.

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

Michael wrote:
> On Saturday, 15 June 2024 12:01:26 BST Dale wrote:
>> Michael wrote:
>>> b) Using a bootloader:
>>>
>>> Mount your ESP under the /efi mountpoint.  GRUB et al, will install their
>>> .efi image in the /efi/EFI/ directory.  You can have your /boot as a
>>> directory on your / partition, or on its own separate partition with a
>>> more robust fs type than ESP's FAT and your kernel images will be
>>> installed in there.
>> H.  If I have a separate /boot, then efi gets mounted under /boot? 
>> Like this:
>>
>> /boot/efi/
> "...  Mounting the ESP to /boot/efi/, as was traditionally done, is not 
> recommended."
>
> Please read:
>
> https://wiki.gentoo.org/wiki/EFI_System_Partition#Mount_point
>
>> I'd like to use Grub, it's what I'm used to mostly.  That way I can
>> update grub with its command and I guess update the efi thingy too when
>> I add kernels.  I'm not sure on that tho.  I could be wrong.
> You can still use GRUB.  Example:
> =
> EFI Partition:  /dev/nvme0n1p1 type ef00
>
> Partition GUID code: C12A7328-F81F-11D2-BA4B-00A0C93EC93B (EFI system 
> partition)
>
> Mountpoint: /efi
>
> Filesystem: FAT32
> =
>
> Then you can have a separate boot partition, example:
> =
> Boot Partition:  /dev/nvme0n1p2, type 8300
>
> Partition GUID code: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (Linux filesystem)
>
> Mountpoint: /boot
>
> Filesystem: ext2/3/4/xfs/btrfs/etc.
> ===
>
>
> [snip...]
>>> ~ # du -s -h /var
>>> 17G /var
>> Well, it is large but it should last me a long time.  Who knows what
>> portage will do next.  When the distfiles and such moved to /var, it's a
>> good thing I was on LVM.  This time, I'm not using LVM so gotta plan
>> further ahead. 
> You can use btrfs or zfs and have /root, /home, /var, /what-ever mounted in 
> subvolumes.  This way they will use/share the free space of the single top 
> level partition/disk.
>


Update.  I just followed the docs.  I had little idea of what I was
doing but I just did what it said.  Dang thing booted, first time.  Even
my fresh new kernel worked.  :-D :-D 

Since I was confused and thought /boot and efi could be the same
partition, I ended up with /boot on the root partition.  I may redo that
later.  It works tho.  Plus, loads of space for other images etc. 

I still don't understand the efi thing.  I'm booted up tho.  I'm happy. 
Now to get temp sensors and stuff to work.  I want to keep a eye on
temps for a bit.  I think the boot media was reporting the wrong info. 
Even the ambient temp was to high for this cool room.  It showed like
100F or something when my A/C is set to 68F or so.  Plus, the side is
off the case at times.  New battle.  ;-) 

Dale

:-)  :-)

Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

2024-06-15 Thread Alan Mackenzie

Hello, Vitaliy.

On Fri, Jun 14, 2024 at 21:25:23 +0300, Vitaliy Perekhovy wrote:
> On Fri, Jun 14, 2024 at 03:53:35PM +, Alan Mackenzie wrote:
> > I think portage is at fault here - it should retain the older standard
> > version of /etc/bash/bashrc so that users can resolve the differences
> > with a 3-way diff.

> Before replace your old bashrc file, portage place the old one
> here: /etc/config-archive/etc/bash/bashrc

Thanks, I didn't know that.  It was extremely helpful.

It turns out that Gentoo has reorganised the layout of /etc/bash/bashrc,
fragmenting it into bashrc itself and three files in /etc/bash/bashrc.d.
Knowing that I was able to sort things out without further problems.

It would have been nice to have known about this change before it
happened, but I suppose it's too minor a change to clog up the eselect
news system with.

> -- 
> Regards,
> Vitaliy Perekhovy

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

2024-06-15 Thread Alan Mackenzie

Hello, Netfab.

On Fri, Jun 14, 2024 at 19:52:32 +0200, netfab wrote:
> Le 14/06/24 à 19:33, Alan Mackenzie a tapoté :
> > Are these files freely available, anywhere, perhaps?

> Else, everything is also available from gentoo.org :
>   
> https://gitweb.gentoo.org/repo/gentoo.git/tree/app-shells/bash/files/bashrc

> Click on plain to  get the raw version.

Thanks, that helped.

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] Keep getting LC_ALL error during install.

Michael wrote:
> On Saturday, 15 June 2024 19:33:54 BST Dale wrote:
>
>> (chroot) livecd / # cat /etc/env.d/02locale
>> # Configuration file for eselect
>> # This file has been automatically generated.
>> LANG="en_US.UTF8"
>> #LC_ALL="en_US.UTF8"
>> (chroot) livecd / #
>>
>> I commented out the LC_ALL thinking it might make the error go away. 
>> The docs mention not setting it at all. 
> Yes, it should not be set.  You can try unsetting it:
>
> export LC_ALL=""
> source /etc/profile
>
> [snip ...]

That fixed it.  Since I was in a chroot, I had to run the command that
changes PS1 so I don't forget where I am.  LOL

>> I think I either missed something or set something wrong somewhere.  I
>> just can't figure out what it is.  I was hoping another pair of eyes
>> would help.  If not, I may just start over.  I'm still really confused
>> over the efi thing and how partitions are to be set up.  While I've read
>> about efi, I've never understood how it works.  If I could, I'd still
>> use the old BIOS method.  It worked just fine for me.  :/
>>
>> Dale
>>
>> :-)  :-) 
> You can contact me off list in case I'm able to answer specific questions 
> with 
> your UEFI installation, or ask on list for a wider audience and broader 
> contributions.  There's nothing magic about UEFI.  Actually I find it rather 
> easier than the obscure CMOS jump code.  :-/


I think I'm going to try and find a video that shows the install, one
that shows it booting and maybe a couple other things.  I need to
understand efi better.  Right now, all I know is it takes the place of
the old BIOS.  Beyond that, no idea.  Keep in mind, I've never seen one
before, haven't even seen one now either.  o_-

I'm not opposed to efi.  I remember when the old Grub reached its end of
life. Grub2 is different but it works.  I don't use the eye candy part
so that makes it even easier.  The biggest thing, I copy my kernels and
such over manually and I keep a couple older ones that I want to be
available.  I also plan to install memtest, a rescue image or two and
those need to be available as well.  I may still use Grub, I may not. 
Right now, I'm clueless.  I'm just trying to follow the docs which given
all the options available are confusing to follow. 

Thanks for the help.  Progress.  :-D 

Dale

:-)  :-)

Re: [gentoo-user] Arrow and edit keys?

On Saturday, 15 June 2024 19:20:26 BST Alan Grimes wrote:
> A number of my softwarez requires the use of the arrow keys and can't
> use the numpad in edit mode to work around it. So who do I need to kill
> to get arrow keys to work in x11 again?

I don't understand what is the "edit mode" you refer to.  There ought to be a 
NumLock key to enable/disable the numeric pad.  Also, your DE would have some 
config GUI for enabling/disabling the numlock.

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

On Saturday, 15 June 2024 17:55:17 BST Michael wrote:

--->8

Thanks, but I'll stick to what I know if you don't mind.

-- 
Regards,
Peter.

Re: [gentoo-user] Keep getting LC_ALL error during install.

On Saturday, 15 June 2024 19:33:54 BST Dale wrote:

> (chroot) livecd / # cat /etc/env.d/02locale
> # Configuration file for eselect
> # This file has been automatically generated.
> LANG="en_US.UTF8"
> #LC_ALL="en_US.UTF8"
> (chroot) livecd / #
> 
> I commented out the LC_ALL thinking it might make the error go away. 
> The docs mention not setting it at all. 

Yes, it should not be set.  You can try unsetting it:

export LC_ALL=""
source /etc/profile

[snip ...]

> I think I either missed something or set something wrong somewhere.  I
> just can't figure out what it is.  I was hoping another pair of eyes
> would help.  If not, I may just start over.  I'm still really confused
> over the efi thing and how partitions are to be set up.  While I've read
> about efi, I've never understood how it works.  If I could, I'd still
> use the old BIOS method.  It worked just fine for me.  :/
> 
> Dale
> 
> :-)  :-) 

You can contact me off list in case I'm able to answer specific questions with 
your UEFI installation, or ask on list for a wider audience and broader 
contributions.  There's nothing magic about UEFI.  Actually I find it rather 
easier than the obscure CMOS jump code.  :-/

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Keep getting LC_ALL error during install.

Michael wrote:
> On Saturday, 15 June 2024 19:09:18 BST Dale wrote:
>> Michael wrote:
>>> On Saturday, 15 June 2024 18:24:27 BST Dale wrote:
 Howdy,

 I got down to the time zone part.  When I try to run emerge --config
 sys-libs/timezone-data I get this output.



 (chroot) livecd / # emerge --config sys-libs/timezone-data


 Configuring pkg...

 Traceback (most recent call last):
   File "/usr/lib/python-exec/python3.12/emerge", line 57, in main
   
 retval = emerge_main()
 
  ^
   
   File "/usr/lib/python3.12/site-packages/_emerge/main.py", line 1308,

 in emerge_main

 return run_action(emerge_config)
 
^
   
   File "/usr/lib/python3.12/site-packages/_emerge/actions.py", line

 3876, in run_action

 return action_config(
 
^^
   
   File "/usr/lib/python3.12/site-packages/_emerge/actions.py", line 758,

 in action_config

 retval = portage.doebuild(
 
  ^
   
   File

 "/usr/lib/python3.12/site-packages/portage/package/ebuild/doebuild.py",
 line 1218, in doebuild

 rval = _prepare_env_file(mysettings)
 
^
   
   File

 "/usr/lib/python3.12/site-packages/portage/package/ebuild/doebuild.py",
 line 1686, in _prepare_env_file

 env_extractor.start()
   
   File "/usr/lib/python3.12/site-packages/_emerge/AsynchronousTask.py",

 line 34, in start

 self._start()
   
   File

 "/usr/lib/python3.12/site-packages/_emerge/BinpkgEnvExtractor.py", line
 43, in _start

 env=self.settings.environ(),
 
 ^^^
   
   File

 "/usr/lib/python3.12/site-packages/portage/package/ebuild/config.py",
 line 3378, in environ

 raise AssertionError(

 AssertionError: LC_ALL=en_US.UTF8 for posixish locale. It seems that
 split_LC_ALL was not called for phase config?
 (chroot) livecd / #



 The next section is locale so I skipped ahead to set the locale settings
 but nothing I do gets me past this error.  Did I miss a step somewhere?
 I'm currently booted from the Gentoo LiveGUI USB Image and am in the
 chroot.  I been following the handbook with the parts that apply to me
 but maybe I missed something???  This is the current setting.


 (chroot) livecd / # eselect locale list

 Available targets for the LANG variable:
   [1]   C
   [2]   C.utf8
   [3]   en_US
   [4]   en_US.iso88591
   [5]   en_US.utf8
   [6]   POSIX
   [7]   en_US.UTF8 *
   [ ]   (free form)

 (chroot) livecd / #


 I also tried setting it to #5.  Same error but works on current rig.
 Anyone know what I missed?  I even tried copying settings from my
 current rig but same error.  I've also ran the following after each
 setting I tried.


 env-update && source /etc/profile && export PS1="(chroot) ${PS1}"


 Any thoughts?

 Dale

 :-)  :-)
>>> Please share:
>>>
>>> $ cat /etc/locale.gen
>>>
>>> $ locale -a
>>>
>>> $ locale
>> I'm going to remove most of the commented out stuff.  Also separating it
>> a bit.  Make it easier to read. 
>>
>>
>>
>> livecd / # cat /etc/locale.gen
>>
>> en_US ISO-8859-1
>> en_US.UTF-8 UTF-8
>> (chroot) livecd / #
>>
>> livecd / # locale -a
>> C
>> C.utf8
>> en_US
>> en_US.iso88591
>> en_US.utf8
>> POSIX
>> (chroot) livecd / #
>>
>> livecd / # locale
>> LANG=en_US.utf8
>> LC_CTYPE="en_US.UTF8"
>> LC_NUMERIC="en_US.UTF8"
>> LC_TIME="en_US.UTF8"
>> LC_COLLATE="en_US.UTF8"
>> LC_MONETARY="en_US.UTF8"
>> LC_MESSAGES="en_US.UTF8"
>> LC_PAPER="en_US.UTF8"
>> LC_NAME="en_US.UTF8"
>> LC_ADDRESS="en_US.UTF8"
>> LC_TELEPHONE="en_US.UTF8"
>> LC_MEASUREMENT="en_US.UTF8"
>> LC_IDENTIFICATION="en_US.UTF8"
>> LC_ALL=en_US.UTF8
> Hmm ... how did the last entry end up in there?
>
> Can you please check your /etc/env.d/02locale and your ~/.bashrc.
>


(chroot) livecd / # cat /etc/env.d/02locale
# Configuration file for eselect
# This file has been automatically generated.
LANG="en_US.UTF8"
#LC_ALL="en_US.UTF8"
(chroot) livecd / #

I commented out the LC_ALL thinking it might make the error go away. 
The docs mention not setting it at all. 

There's no /root/.bashrc, yet anyway. 

>> (chroot) livecd / #
>>
>>
>> I tried to copy the settings from my current rig and the docs seem to
>> agree with that still.  I think I either missed something or set
>> something wrong.  I just can't figure out which as it matches my current
>> rig.  :/
>>
>> Where did I go wrong?
> Re-use, it saves time, but check first what it is you are re-using.  You 
>

Re: [gentoo-user] Keep getting LC_ALL error during install.

On Saturday, 15 June 2024 19:09:18 BST Dale wrote:
> Michael wrote:
> > On Saturday, 15 June 2024 18:24:27 BST Dale wrote:
> >> Howdy,
> >> 
> >> I got down to the time zone part.  When I try to run emerge --config
> >> sys-libs/timezone-data I get this output.
> >> 
> >> 
> >> 
> >> (chroot) livecd / # emerge --config sys-libs/timezone-data
> >> 
> >> 
> >> Configuring pkg...
> >> 
> >> Traceback (most recent call last):
> >>   File "/usr/lib/python-exec/python3.12/emerge", line 57, in main
> >>   
> >> retval = emerge_main()
> >> 
> >>  ^
> >>   
> >>   File "/usr/lib/python3.12/site-packages/_emerge/main.py", line 1308,
> >> 
> >> in emerge_main
> >> 
> >> return run_action(emerge_config)
> >> 
> >>^
> >>   
> >>   File "/usr/lib/python3.12/site-packages/_emerge/actions.py", line
> >> 
> >> 3876, in run_action
> >> 
> >> return action_config(
> >> 
> >>^^
> >>   
> >>   File "/usr/lib/python3.12/site-packages/_emerge/actions.py", line 758,
> >> 
> >> in action_config
> >> 
> >> retval = portage.doebuild(
> >> 
> >>  ^
> >>   
> >>   File
> >> 
> >> "/usr/lib/python3.12/site-packages/portage/package/ebuild/doebuild.py",
> >> line 1218, in doebuild
> >> 
> >> rval = _prepare_env_file(mysettings)
> >> 
> >>^
> >>   
> >>   File
> >> 
> >> "/usr/lib/python3.12/site-packages/portage/package/ebuild/doebuild.py",
> >> line 1686, in _prepare_env_file
> >> 
> >> env_extractor.start()
> >>   
> >>   File "/usr/lib/python3.12/site-packages/_emerge/AsynchronousTask.py",
> >> 
> >> line 34, in start
> >> 
> >> self._start()
> >>   
> >>   File
> >> 
> >> "/usr/lib/python3.12/site-packages/_emerge/BinpkgEnvExtractor.py", line
> >> 43, in _start
> >> 
> >> env=self.settings.environ(),
> >> 
> >> ^^^
> >>   
> >>   File
> >> 
> >> "/usr/lib/python3.12/site-packages/portage/package/ebuild/config.py",
> >> line 3378, in environ
> >> 
> >> raise AssertionError(
> >> 
> >> AssertionError: LC_ALL=en_US.UTF8 for posixish locale. It seems that
> >> split_LC_ALL was not called for phase config?
> >> (chroot) livecd / #
> >> 
> >> 
> >> 
> >> The next section is locale so I skipped ahead to set the locale settings
> >> but nothing I do gets me past this error.  Did I miss a step somewhere?
> >> I'm currently booted from the Gentoo LiveGUI USB Image and am in the
> >> chroot.  I been following the handbook with the parts that apply to me
> >> but maybe I missed something???  This is the current setting.
> >> 
> >> 
> >> (chroot) livecd / # eselect locale list
> >> 
> >> Available targets for the LANG variable:
> >>   [1]   C
> >>   [2]   C.utf8
> >>   [3]   en_US
> >>   [4]   en_US.iso88591
> >>   [5]   en_US.utf8
> >>   [6]   POSIX
> >>   [7]   en_US.UTF8 *
> >>   [ ]   (free form)
> >> 
> >> (chroot) livecd / #
> >> 
> >> 
> >> I also tried setting it to #5.  Same error but works on current rig.
> >> Anyone know what I missed?  I even tried copying settings from my
> >> current rig but same error.  I've also ran the following after each
> >> setting I tried.
> >> 
> >> 
> >> env-update && source /etc/profile && export PS1="(chroot) ${PS1}"
> >> 
> >> 
> >> Any thoughts?
> >> 
> >> Dale
> >> 
> >> :-)  :-)
> > 
> > Please share:
> > 
> > $ cat /etc/locale.gen
> > 
> > $ locale -a
> > 
> > $ locale
> 
> I'm going to remove most of the commented out stuff.  Also separating it
> a bit.  Make it easier to read. 
> 
> 
> 
> livecd / # cat /etc/locale.gen
> 
> en_US ISO-8859-1
> en_US.UTF-8 UTF-8
> (chroot) livecd / #
> 
> livecd / # locale -a
> C
> C.utf8
> en_US
> en_US.iso88591
> en_US.utf8
> POSIX
> (chroot) livecd / #
> 
> livecd / # locale
> LANG=en_US.utf8
> LC_CTYPE="en_US.UTF8"
> LC_NUMERIC="en_US.UTF8"
> LC_TIME="en_US.UTF8"
> LC_COLLATE="en_US.UTF8"
> LC_MONETARY="en_US.UTF8"
> LC_MESSAGES="en_US.UTF8"
> LC_PAPER="en_US.UTF8"
> LC_NAME="en_US.UTF8"
> LC_ADDRESS="en_US.UTF8"
> LC_TELEPHONE="en_US.UTF8"
> LC_MEASUREMENT="en_US.UTF8"
> LC_IDENTIFICATION="en_US.UTF8"
> LC_ALL=en_US.UTF8

Hmm ... how did the last entry end up in there?

Can you please check your /etc/env.d/02locale and your ~/.bashrc.


> (chroot) livecd / #
> 
> 
> I tried to copy the settings from my current rig and the docs seem to
> agree with that still.  I think I either missed something or set
> something wrong.  I just can't figure out which as it matches my current
> rig.  :/
> 
> Where did I go wrong?

Re-use, it saves time, but check first what it is you are re-using.  You could 
end up falling behind, because the world of code moves on and you may also end 
up copying over previous latent mistakes.




signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Keep getting LC_ALL error during install.

Michael wrote:
> On Saturday, 15 June 2024 18:24:27 BST Dale wrote:
>> Howdy,
>>
>> I got down to the time zone part.  When I try to run emerge --config
>> sys-libs/timezone-data I get this output. 
>>
>>
>>
>> (chroot) livecd / # emerge --config sys-libs/timezone-data
>>
>>
>> Configuring pkg...
>>
>> Traceback (most recent call last):
>>   File "/usr/lib/python-exec/python3.12/emerge", line 57, in main
>> retval = emerge_main()
>>  ^
>>   File "/usr/lib/python3.12/site-packages/_emerge/main.py", line 1308,
>> in emerge_main
>> return run_action(emerge_config)
>>^
>>   File "/usr/lib/python3.12/site-packages/_emerge/actions.py", line
>> 3876, in run_action
>> return action_config(
>>^^
>>   File "/usr/lib/python3.12/site-packages/_emerge/actions.py", line 758,
>> in action_config
>> retval = portage.doebuild(
>>  ^
>>   File
>> "/usr/lib/python3.12/site-packages/portage/package/ebuild/doebuild.py",
>> line 1218, in doebuild
>> rval = _prepare_env_file(mysettings)
>>^
>>   File
>> "/usr/lib/python3.12/site-packages/portage/package/ebuild/doebuild.py",
>> line 1686, in _prepare_env_file
>> env_extractor.start()
>>   File "/usr/lib/python3.12/site-packages/_emerge/AsynchronousTask.py",
>> line 34, in start
>> self._start()
>>   File
>> "/usr/lib/python3.12/site-packages/_emerge/BinpkgEnvExtractor.py", line
>> 43, in _start
>> env=self.settings.environ(),
>> ^^^
>>   File
>> "/usr/lib/python3.12/site-packages/portage/package/ebuild/config.py",
>> line 3378, in environ
>> raise AssertionError(
>> AssertionError: LC_ALL=en_US.UTF8 for posixish locale. It seems that
>> split_LC_ALL was not called for phase config?
>> (chroot) livecd / #
>>
>>
>>
>> The next section is locale so I skipped ahead to set the locale settings
>> but nothing I do gets me past this error.  Did I miss a step somewhere? 
>> I'm currently booted from the Gentoo LiveGUI USB Image and am in the
>> chroot.  I been following the handbook with the parts that apply to me
>> but maybe I missed something???  This is the current setting.
>>
>>
>> (chroot) livecd / # eselect locale list
>> Available targets for the LANG variable:
>>   [1]   C
>>   [2]   C.utf8
>>   [3]   en_US
>>   [4]   en_US.iso88591
>>   [5]   en_US.utf8
>>   [6]   POSIX
>>   [7]   en_US.UTF8 *
>>   [ ]   (free form)
>> (chroot) livecd / #
>>
>>
>> I also tried setting it to #5.  Same error but works on current rig. 
>> Anyone know what I missed?  I even tried copying settings from my
>> current rig but same error.  I've also ran the following after each
>> setting I tried. 
>>
>>
>> env-update && source /etc/profile && export PS1="(chroot) ${PS1}"
>>
>>
>> Any thoughts? 
>>
>> Dale
>>
>> :-)  :-) 
> Please share:
>
> $ cat /etc/locale.gen
>
> $ locale -a
>
> $ locale


I'm going to remove most of the commented out stuff.  Also separating it
a bit.  Make it easier to read. 



livecd / # cat /etc/locale.gen

en_US ISO-8859-1
en_US.UTF-8 UTF-8
(chroot) livecd / #

livecd / # locale -a
C
C.utf8
en_US
en_US.iso88591
en_US.utf8
POSIX
(chroot) livecd / #

livecd / # locale
LANG=en_US.utf8
LC_CTYPE="en_US.UTF8"
LC_NUMERIC="en_US.UTF8"
LC_TIME="en_US.UTF8"
LC_COLLATE="en_US.UTF8"
LC_MONETARY="en_US.UTF8"
LC_MESSAGES="en_US.UTF8"
LC_PAPER="en_US.UTF8"
LC_NAME="en_US.UTF8"
LC_ADDRESS="en_US.UTF8"
LC_TELEPHONE="en_US.UTF8"
LC_MEASUREMENT="en_US.UTF8"
LC_IDENTIFICATION="en_US.UTF8"
LC_ALL=en_US.UTF8
(chroot) livecd / #


I tried to copy the settings from my current rig and the docs seem to
agree with that still.  I think I either missed something or set
something wrong.  I just can't figure out which as it matches my current
rig.  :/

Where did I go wrong?

Dale

:-)  :-)

Re: [gentoo-user] Keep getting LC_ALL error during install.

On Saturday, 15 June 2024 18:24:27 BST Dale wrote:
> Howdy,
> 
> I got down to the time zone part.  When I try to run emerge --config
> sys-libs/timezone-data I get this output. 
> 
> 
> 
> (chroot) livecd / # emerge --config sys-libs/timezone-data
> 
> 
> Configuring pkg...
> 
> Traceback (most recent call last):
>   File "/usr/lib/python-exec/python3.12/emerge", line 57, in main
> retval = emerge_main()
>  ^
>   File "/usr/lib/python3.12/site-packages/_emerge/main.py", line 1308,
> in emerge_main
> return run_action(emerge_config)
>^
>   File "/usr/lib/python3.12/site-packages/_emerge/actions.py", line
> 3876, in run_action
> return action_config(
>^^
>   File "/usr/lib/python3.12/site-packages/_emerge/actions.py", line 758,
> in action_config
> retval = portage.doebuild(
>  ^
>   File
> "/usr/lib/python3.12/site-packages/portage/package/ebuild/doebuild.py",
> line 1218, in doebuild
> rval = _prepare_env_file(mysettings)
>^
>   File
> "/usr/lib/python3.12/site-packages/portage/package/ebuild/doebuild.py",
> line 1686, in _prepare_env_file
> env_extractor.start()
>   File "/usr/lib/python3.12/site-packages/_emerge/AsynchronousTask.py",
> line 34, in start
> self._start()
>   File
> "/usr/lib/python3.12/site-packages/_emerge/BinpkgEnvExtractor.py", line
> 43, in _start
> env=self.settings.environ(),
> ^^^
>   File
> "/usr/lib/python3.12/site-packages/portage/package/ebuild/config.py",
> line 3378, in environ
> raise AssertionError(
> AssertionError: LC_ALL=en_US.UTF8 for posixish locale. It seems that
> split_LC_ALL was not called for phase config?
> (chroot) livecd / #
> 
> 
> 
> The next section is locale so I skipped ahead to set the locale settings
> but nothing I do gets me past this error.  Did I miss a step somewhere? 
> I'm currently booted from the Gentoo LiveGUI USB Image and am in the
> chroot.  I been following the handbook with the parts that apply to me
> but maybe I missed something???  This is the current setting.
> 
> 
> (chroot) livecd / # eselect locale list
> Available targets for the LANG variable:
>   [1]   C
>   [2]   C.utf8
>   [3]   en_US
>   [4]   en_US.iso88591
>   [5]   en_US.utf8
>   [6]   POSIX
>   [7]   en_US.UTF8 *
>   [ ]   (free form)
> (chroot) livecd / #
> 
> 
> I also tried setting it to #5.  Same error but works on current rig. 
> Anyone know what I missed?  I even tried copying settings from my
> current rig but same error.  I've also ran the following after each
> setting I tried. 
> 
> 
> env-update && source /etc/profile && export PS1="(chroot) ${PS1}"
> 
> 
> Any thoughts? 
> 
> Dale
> 
> :-)  :-) 

Please share:

$ cat /etc/locale.gen

$ locale -a

$ locale

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] CPU frequency governors and temperatures

On Saturday, 15 June 2024 18:24:04 BST Walter Dnes wrote:
> On Sat, Jun 15, 2024 at 12:39:09PM +0100, Michael wrote
> 
> > The maximum temperature at which your CPU die with its 65W TDP starts
> > throttling to keep its temperatures safe is 100°C TjMax.  Look at the
> > TJunction number here:
> > 
> > https://www.intel.com/content/www/us/en/products/sku/199271/intel-core-i51
> > 0400-processor-12m-cache-up-to-4-30-ghz/specifications.html
> > 
> > According to Intel anything below 100°C is 'normal'.  If this were
> > my CPU I would not worry with temperatures ~70-85°C.  Above that
> > I would install a better CPU cooler.
> 
>   Thanks.  I wasn't aware of the two different versions of "Max
> Temperature".

I have had laptops which throttled on hot days and when there wasn't enough 
airflow around/underneath them.  You'll see dmesg filling up with warnings 
about max temp reached or some such and any heavy lifting compilation taking 
forever to finish, since the CPU is throttling and cutting out.  If the 
overheating was extreme due to a race condition, then the laptop would just 
shutdown.  Since you have not observed this kind of rather concerning 
symptoms, I think you can continue using the schedutil governor which is quite 
intelligent in juggling and optimising tasks.  Check the documentation for 
your kernel in:

/usr/src/linux-6.6.30-gentoo/Documentation/scheduler/schedutil.rst

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] CPU frequency governors and temperatures

2024-06-15 Thread Walter Dnes

On Sat, Jun 15, 2024 at 12:39:09PM +0100, Michael wrote

> The maximum temperature at which your CPU die with its 65W TDP starts 
> throttling to keep its temperatures safe is 100°C TjMax.  Look at the 
> TJunction number here:
> 
> https://www.intel.com/content/www/us/en/products/sku/199271/intel-core-i510400-processor-12m-cache-up-to-4-30-ghz/specifications.html
 
> According to Intel anything below 100°C is 'normal'.  If this were
> my CPU I would not worry with temperatures ~70-85°C.  Above that
> I would install a better CPU cooler.

  Thanks.  I wasn't aware of the two different versions of "Max Temperature".

-- 
Roses are red
Roses are blue
Depending on their velocity
Relative to you

Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

2024-06-15 Thread Wol


On 14/06/2024 18:39, Alan Mackenzie wrote:

Does etc-update or dispatch-conf not give you the option to selectively
update and/or to diff the file?



In theory, yes.  In practice, dispatch-conf just offers a single
~130-line long hunk, which is useless for distinguishing wanted pieces of
code from old superseded code.  As I say, what's missing is the old
repository version, which would allow a diff3.


etc-update certainly, and I would be surprised if dispatch-conf didn't, 
does offer you a diff.


The (faulty) assumption here is that the user actually knows how to make 
use of a diff!


Certainly true for me, and quite likely for a sizeable minority, I 
predate both Linux and Windows by quite a large margin, and have never 
been part of the Unix eco-system. I use linux because it's better than 
Windows, I use gentoo because I want to learn, but I'm not comfortable 
with pretty much the entire development ecosystem including things like 
diff.


I so rarely use diff, that I find it simplest to run a diff (which tells 
me *what* has changed, then I open both old and new in kate, and 
manually investigate. It may be more work than using diff properly, but 
once I factor in the cost of working out how to use diff it's not worth 
it. It's doubly not worth it because I'll have forgotten all that hard 
work next time I need it!


Cheers,
Wol

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

On Saturday, 15 June 2024 16:28:29 BST Peter Humphrey wrote:
> On Saturday, 15 June 2024 13:01:33 BST Dale wrote:
> > Could you share the boot screen again?
> 
> New version attached...
> 
> > I used lilo ages ago then switched to Grub.  Grub is massive but it works
> > well enough.
> 
> ...as long as you only want to specify one kernel image.

Not really.  You can add as many kernel image versions as you like and in 
addition customise the GRUB configuration to add kernel command-line 
parameters of choice.


> > Thing is, seeing your screen may help me to understand how
> > certain options work. It may make me use the bootloader you use, which is
> > what by the way?
> 
> I use bootctl from sys-apps/systemd-utils* with USE="acl boot kernel-install
> kmod tmpfiles udev -secureboot (-selinux) (-split-usr) -sysusers -test
> -ukify"
> 
> Sys-kernel/kernelinstall has USE="-dracut (-efistub) -grub -refind -systemd
> -systemd-boot -uki -ukify"
> 
> Notice the -systemd -systemd-boot flags. The wiki and some news items say to
> set those, but then I'd end up with the unintelligible file and directory
> names I mentioned - I'm not well versed in mental 32-digit hex
> number-juggling.  :)
> 
> --->8

I thought the 'title' for any systemd-boot listed kernel can be edited to suit 
user preferences, as described here:

https://forums.gentoo.org/viewtopic-p-8826048.html


> > Like you, I keep old kernels around too.  Eventually, I clean out old
> > ones but I like to keep at least a couple around just in case one goes
> > wonky.  At least I can boot a older kernel to fix things.  I also do
> > things the manual way.  I copy my kernels over with names I like, copy
> > the config file over with a matching name as well.
> 
> That's all automatic here; kernelinstall does it when I call 'make install'.
> All but two of the files shown in 'ls -1 /boot', below, are as 'make
> install' set them. The exceptions to that are early_ucode.cpio and
> intel-uc.img.

You can build these in-kernel, by adding their path/name in your kernel 
config, e.g.:

CONFIG_FW_LOADER=y
CONFIG_EXTRA_FIRMWARE="intel-ucode/06-3c-03"
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"

See here:

https://wiki.gentoo.org/wiki/Intel_microcode#New_method_without_initram-fs.
2Fdisk_.28efistub_compatible.29


> The only files I maintain myself are those under /boot/loader/entries; they
> define the menu items in the attachment here:
> 
> 06-gentoo-rescue-6.6.30.conf
> 07-gentoo-rescue-6.6.30.nonet.conf
> 08-gentoo-rescue-6.6.21.conf
> 09-gentoo-rescue-6.6.21.nonet.conf
> 30-gentoo-6.6.30.conf
> 32-gentoo-6.6.30.nox.conf
> 34-gentoo-6.6.30.nonet.conf
> 40-gentoo-6.6.21.conf
> 42-gentoo-6.6.21.nox.conf
> 44-gentoo-6.6.21.nonet.conf
> 
> E.g: $ cat /boot/loader/entries/34-gentoo-6.6.30.nonet.conf
> title Gentoo 6.6.30 (No network)
> version 6.6.30-gentoo
> linux vmlinuz-6.6.30-gentoo
> options root=/dev/nvme0n1p5 net.ifnames=0 raid=noautodetect \
> softlevel=nonetwork
> 
> > I do let dracut build the init thingy.  I do edit the name to match the
> > kernel so that grub sees it.  So, you not alone doing it the manual way,
> > as
> > much as I can anyway.
> 
> I don't need an initramfs, other than early_ucode.cpio and intel-uc.img,
> because I don't want the complications of a separate /usr partition.
> 
> $ ls -1 /boot
> config-6.6.21-gentoo
> config-6.6.21-gentoo-rescue
> config-6.6.30-gentoo
> config-6.6.30-gentoo-rescue
> early_ucode.cpio
> EFI
> intel-uc.img
> loader
> System.map-6.6.21-gentoo
> System.map-6.6.21-gentoo-rescue
> System.map-6.6.30-gentoo
> System.map-6.6.30-gentoo-rescue
> vmlinuz-6.6.21-gentoo
> vmlinuz-6.6.21-gentoo-rescue
> vmlinuz-6.6.30-gentoo
> vmlinuz-6.6.30-gentoo-rescue
> 
> > Thanks much.
> 
> *   The handbook says to use efibootmgr to create boot entries, but that
> again assumes you only want a single bootable image. It is occasionally
> useful, though, to clear up any mess I may have made.

With the efibootmgr you can have more than one bootable image, set your own 
preferred label for it and you can hardcode any kernel command-line parameters 
in each kernel image; e.g.:

CONFIG_CMDLINE="root=PARTUUID=--XXX-- snd-hda-
intel.index=1,0"


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

2024-06-15 Thread Wol


On 14/06/2024 16:53, Alan Mackenzie wrote:

I think portage is at fault here - it should retain the older standard
version of /etc/bash/bashrc so that users can resolve the differences
with a 3-way diff.


Is it portage itself that DID the update, or it did it tell you to do 
the update with etc-update, or dispatch-conf, or any one of those 
programs. Ime portage leaves the new version as ._something so you 
should have both the old and new versions until you mess it up yourself :-)


And as I keep moaning, you can't blame portage for other software being 
stupid. Doesn't bash have a ~/.bashrc you can edit? I know - all too 
often the DE gets in the way ...


Imho dovecot gets it perfectly right (as does systemd, actually, both of 
them thought this through properly) because it has a configuration in 
the default file that tells it to read a local file. So the package 
manager updates the standard file, and the standard file reads the local 
configuration to update it with the local settings.


Cheers,
Wol

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

On Saturday, 15 June 2024 12:01:26 BST Dale wrote:
> Michael wrote:

> > b) Using a bootloader:
> > 
> > Mount your ESP under the /efi mountpoint.  GRUB et al, will install their
> > .efi image in the /efi/EFI/ directory.  You can have your /boot as a
> > directory on your / partition, or on its own separate partition with a
> > more robust fs type than ESP's FAT and your kernel images will be
> > installed in there.
> 
> H.  If I have a separate /boot, then efi gets mounted under /boot? 
> Like this:
> 
> /boot/efi/

"...  Mounting the ESP to /boot/efi/, as was traditionally done, is not 
recommended."

Please read:

https://wiki.gentoo.org/wiki/EFI_System_Partition#Mount_point

> I'd like to use Grub, it's what I'm used to mostly.  That way I can
> update grub with its command and I guess update the efi thingy too when
> I add kernels.  I'm not sure on that tho.  I could be wrong.

You can still use GRUB.  Example:
=
EFI Partition:  /dev/nvme0n1p1 type ef00

Partition GUID code: C12A7328-F81F-11D2-BA4B-00A0C93EC93B (EFI system 
partition)

Mountpoint: /efi

Filesystem: FAT32
=

Then you can have a separate boot partition, example:
=
Boot Partition:  /dev/nvme0n1p2, type 8300

Partition GUID code: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (Linux filesystem)

Mountpoint: /boot

Filesystem: ext2/3/4/xfs/btrfs/etc.
===


[snip...]
> > ~ # du -s -h /var
> > 17G /var
> 
> Well, it is large but it should last me a long time.  Who knows what
> portage will do next.  When the distfiles and such moved to /var, it's a
> good thing I was on LVM.  This time, I'm not using LVM so gotta plan
> further ahead. 

You can use btrfs or zfs and have /root, /home, /var, /what-ever mounted in 
subvolumes.  This way they will use/share the free space of the single top 
level partition/disk.



signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

Peter Humphrey wrote:
> On Saturday, 15 June 2024 07:53:06 BST Dale wrote:
>> Peter Humphrey wrote:
>>> Here's the output of parted -l on my main NVMe disk in case it helps:
>>>
>>> Model: Samsung SSD 970 EVO Plus 250GB (nvme)
>>> Disk /dev/nvme1n1: 250GB
>>> Sector size (logical/physical): 512B/512B
>>> Partition Table: gpt
>>> Disk Flags:
>>>
>>> Number  Start   End SizeFile system Name  Flags
>>>
>>>  1  1049kB  135MB   134MB
>>>  2  135MB   4296MB  4161MB  fat32   boot  boot, esp
>>>  3  4296MB  12.9GB  8590MB  linux-swap(v1)  swap1 swap
>>>  4  12.9GB  34.4GB  21.5GB  ext4rescue
>>>  5  34.4GB  60.1GB  25.8GB  ext4root
>>>  6  60.1GB  112GB   51.5GB  ext4var
>>>  7  112GB   114GB   2147MB  ext4local
>>>  8  114GB   140GB   25.8GB  ext4home
>>>  9  140GB   183GB   42.9GB  ext4common
>>>
>> I'm starting the process here.  I'm trying to follow the install guide
>> but this is still not clear to me and the guide is not helping.  In your
>> list above, is #2 where /boot is mounted?  Is that where I put kernels,
>> init thingys, memtest and other images to boot from? 
> Yes, and yes ('tree -L 3 /boot' below). I've had no success with the layout 
> recommended in the wiki, because I want a choice of kernels to boot; I've 
> shown my boot-time screen here before. In fact, gparted shows the unformatted 
> first partition as bios_grub. I don't know why parted didn't show the same 
> (it 
> does show it now) Gparted screen shot attached.
>
> Thus, I have an unused bios_grub partition, then a FAT32 EFI system 
> partition, 
> then the rest as usual.


Could you share the boot screen again?  I used lilo ages ago then
switched to Grub.  Grub is massive but it works well enough.  Thing is,
seeing your screen may help me to understand how certain options work. 
It may make me use the bootloader you use, which is what by the way? 

>> My current layout for a 1TB m.2 stick, typing by hand:
>>
>> 18GBEFI System   
>> 2400GBLinux file system for root or /.
>> 3180GBLinux file system for /var.
>>
>> I'll have /home and such on other drives, spinning rust. I'm just
>> wanting to be sure if my #1 and your #2 is where boot files go, Grub,
>> kernels, init thingys etc.  I've always had kernels and such on ext2 but
>> understand efi requires fat32. 
> Yes. I believe the EFI spec requires a file system that any OS can access, 
> and 
> FAT is it, FAT32 usually being recommended.
>
> Then, when it comes to bootctl and installkernel, I ignore the Gentoo advice 
> on USE flags because it results in illegible file names and impenetrable 
> directories. My version is far simpler to manage, which I do by hand. I don't 
> suppose anyone else would use my approach, but I started it long before the 
> days of EFI, and it still works for me.
>
> Also, as I've said here before, I dislike the all-things-to-all-men grub, so 
> I 
> don't use it.
>
> Incidentally, do you really need so much space in root and /var? Mine are 
> just 
> 40GB each, and not even half full. I don't run a lot of media apps though. 
> Still, space is cheap.   :)
>
> $ tree -L 3 /boot
> /boot
> ├── config-6.1.67-gentoo-rescue
> ├── config-6.6.21-gentoo
> ├── config-6.6.21-gentoo-rescue
> ├── config-6.6.30-gentoo
> ├── config-6.6.30-gentoo-rescue
> ├── config-6.7.9-gentoo
> ├── config-6.8.5-gentoo-r1
> ├── early_ucode.cpio
> ├── EFI
> │   ├── BOOT
> │   │   └── BOOTX64.EFI
> │   ├── Linux
> │   └── systemd
> │   └── systemd-bootx64.efi
> ├── intel-uc.img
> ├── loader
> │   ├── entries
> │   │   ├── 06-gentoo-rescue-6.6.30.conf
> │   │   ├── 07-gentoo-rescue-6.6.30.nonet.conf
> │   │   ├── 08-gentoo-rescue-6.6.21.conf
> │   │   ├── 09-gentoo-rescue-6.6.21.nonet.conf
> │   │   ├── 30-gentoo-6.6.30.conf
> │   │   ├── 32-gentoo-6.6.30.conf
> │   │   ├── 34-gentoo-6.6.30.conf
> │   │   ├── 40-gentoo-6.6.21.conf
> │   │   ├── 42-gentoo-6.6.21.conf
> │   │   └── 44-gentoo-6.6.21.conf
> │   ├── entries.srel
> │   ├── loader.conf
> │   └── random-seed
> ├── System.map-6.6.21-gentoo
> ├── System.map-6.6.21-gentoo-rescue
> ├── System.map-6.6.30-gentoo
> ├── System.map-6.6.30-gentoo-rescue
> ├── System.map-6.7.9-gentoo
> ├── System.map-6.8.5-gentoo-r1
> ├── vmlinuz-6.1.67-gentoo-rescue
> ├── vmlinuz-6.6.21-gentoo
> ├── vmlinuz-6.6.21-gentoo-rescue
> ├── vmlinuz-6.6.30-gentoo
> ├── vmlinuz-6.6.30-gentoo-rescue
> ├── vmlinuz-6.7.9-gentoo
> └── vmlinuz-6.8.5-gentoo-r1
>


OK.  So, I mount /boot and put my kernels, config files and all the
things I usually put there as usual.  Then I have a efi directory under
/boot that the efi tools use.  I only created one partition so I assume
when I boot it will find the efi directory within /boot???  If this is
the case, I don't need to redo my partitions.  I already started a OS
backup but oh well. ;-) 

Like you, I keep old kernels around too.  Eventually, I clean out old

Re: [gentoo-user] CPU frequency governors and temperatures

On Friday, 14 June 2024 20:53:04 BST Walter Dnes wrote:
> On Fri, Jun 14, 2024 at 11:54:52AM +0100, Michael wrote
> 
> > I would think 46-48°C is refreshingly cool, but it very much depends
> > on the CPU chip, the MoBo and its BIOS/microcode settings.
> 
>   I looked up my CPU (see my reply to Dale).  The max temp allowed is
> 71.3 C.  A short kernel compile is one thing.  I tried schedutil during
> an emerge world update, and the temp was hitting 70 C.  Ouch!  schedutil
> has to go.

Not so fast!  :-)

The maximum temperature at which your CPU die with its 65W TDP starts 
throttling to keep its temperatures safe is 100°C TjMax.  Look at the 
TJunction number here:

https://www.intel.com/content/www/us/en/products/sku/199271/intel-core-i510400-processor-12m-cache-up-to-4-30-ghz/specifications.html

As I understand it 72°C is the TCase temperature.  sys-apps/lm-sensors are 
meant to report TjMax, the core temperature of the CPU.  The TCase can be 
measured (approximately) with an infrared thermometer, or by hacking the cover 
of the CPU (seriously NOT recommended!).  Assuming you have enough RAM and you 
use all your CPU threads, a big package compile (e.g. chromium) will indicate 
typical max temperatures your particular installation achieves.  Something 
like MAKEOPTS="-j13 -l12.8" ought to squeeze the juice out of it.

The TjMax is controlled by the MoBo firmware and any updates to it.  
Aftermarket CPU coolers and thermal paste will give you an edge here over 
stock options for desktops, especially when ambient temperatures hit higher 
numbers in the summer months.  For a laptop there are limited things to try, 
e.g. better thermal pads/paste and a cooling pad with external fans.  However, 
such measures may only be necessary if the stock cooler does not keep 
temperatures within normal operating range.

According to Intel anything below 100°C is 'normal'.  If this were my CPU I 
would not worry with temperatures ~70-85°C.  Above that I would install a 
better CPU cooler.

> > I recall an early i7 CPU laptop would not go above 2,400MHz when
> > 4core/8threads were running, but on single core processes I would
> > see it on i7z jumping up to 4,200MHz.
> 
>   Speaking of cores+threads... I had always thought my cpu had 12
> cores.  i.e. /proc/cpuinfo showed 12 "cpus" as did directory
> /sys/devices/system/cpu/  But I was wrong.  The specs show 6 real cores,
> plus hyperthreading.

You can use lscpu.  It shows threads and cores.

> See Greg Kroah-Hartman's presentation about the
> security issue called "hyperthreading"...
> https://events19.linuxfoundation.org/wp-content/uploads/2018/07/gregkh_mds.p
> df Read it and weep.  Page 6 summarizes it succinctly...
> 
> ==
>   OpenBSD was right
> * Guessed more problems would be in this area
> * Disabled SMT for Intel chips in June 2018
> * Repeated the plea to disable this in August 2018
> * Prevented almost all MDS issues automatically
> * Security over performance
> * Huge respect!
> ==
> 
>   I immediately went into the BIOS and disabled hyperthreading... and
> adjusted makeopts in make.conf 

In June 2018 and for 2019 the idea to disable hyperthreading would be a 
security precaution, especially for datacenters and systems running VM 
installations.

I am not sure this is either necessary or even recommended anymore.  More 
knowledgeable contributors should chime in here.  As far as I know, OEM MoBo 
firmware updates, CPU microcode releases, OS kernels, compilers and 
applications have implemented a lot of fixes and patches to cover the litany 
of CPU bugs and vulnerabilities discovered since then.

If you run lscpu and also check your dmesg output, you'll see what known 
vulnerabilities your CPU may be still be exposed to - if any.  Sadly Intel are 
not very charitable toward their older retail market CPUs and did not release 
needed microcode updates.  This steered me away from their CPUs since then.

You could also take a look at the spectre-meltdown-checker if you want a more 
detailed report on the latest revealed vulnerabilities:

https://github.com/speed47/spectre-meltdown-checker

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

On Friday, 14 June 2024 18:33:57 BST Alan Mackenzie wrote:

> Are these files freely available, anywhere, perhaps?

Your backup from last week?   :)

-- 
Regards,
Peter.

Re: [gentoo-user] CPU frequency governors and temperatures

On Friday, 14 June 2024 16:16:09 BST Michael wrote:

> Liquid cooling would have made it as quiet as a church mouse.  ;-)

I have a machine here with liquid cooling, and over its few years it's become 
deafening under full load (24 simultaneous floating-point physics 
applications). It is quiet when idling, though - of course.

Perhaps I should get busy cleaning...

-- 
Regards,
Peter.

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

On Saturday, 15 June 2024 07:53:06 BST Dale wrote:
> Peter Humphrey wrote:
> > Here's the output of parted -l on my main NVMe disk in case it helps:
> > 
> > Model: Samsung SSD 970 EVO Plus 250GB (nvme)
> > Disk /dev/nvme1n1: 250GB
> > Sector size (logical/physical): 512B/512B
> > Partition Table: gpt
> > Disk Flags:
> > 
> > Number  Start   End SizeFile system Name  Flags
> > 
> >  1  1049kB  135MB   134MB
> >  2  135MB   4296MB  4161MB  fat32   boot  boot, esp
> >  3  4296MB  12.9GB  8590MB  linux-swap(v1)  swap1 swap
> >  4  12.9GB  34.4GB  21.5GB  ext4rescue
> >  5  34.4GB  60.1GB  25.8GB  ext4root
> >  6  60.1GB  112GB   51.5GB  ext4var
> >  7  112GB   114GB   2147MB  ext4local
> >  8  114GB   140GB   25.8GB  ext4home
> >  9  140GB   183GB   42.9GB  ext4common
> > 
> I'm starting the process here.  I'm trying to follow the install guide
> but this is still not clear to me and the guide is not helping.  In your
> list above, is #2 where /boot is mounted?  Is that where I put kernels,
> init thingys, memtest and other images to boot from? 

Yes, and yes ('tree -L 3 /boot' below). I've had no success with the layout 
recommended in the wiki, because I want a choice of kernels to boot; I've 
shown my boot-time screen here before. In fact, gparted shows the unformatted 
first partition as bios_grub. I don't know why parted didn't show the same (it 
does show it now) Gparted screen shot attached.

Thus, I have an unused bios_grub partition, then a FAT32 EFI system partition, 
then the rest as usual.

> My current layout for a 1TB m.2 stick, typing by hand:
> 
> 18GBEFI System   
> 2400GBLinux file system for root or /.
> 3180GBLinux file system for /var.
> 
> I'll have /home and such on other drives, spinning rust. I'm just
> wanting to be sure if my #1 and your #2 is where boot files go, Grub,
> kernels, init thingys etc.  I've always had kernels and such on ext2 but
> understand efi requires fat32. 

Yes. I believe the EFI spec requires a file system that any OS can access, and 
FAT is it, FAT32 usually being recommended.

Then, when it comes to bootctl and installkernel, I ignore the Gentoo advice 
on USE flags because it results in illegible file names and impenetrable 
directories. My version is far simpler to manage, which I do by hand. I don't 
suppose anyone else would use my approach, but I started it long before the 
days of EFI, and it still works for me.

Also, as I've said here before, I dislike the all-things-to-all-men grub, so I 
don't use it.

Incidentally, do you really need so much space in root and /var? Mine are just 
40GB each, and not even half full. I don't run a lot of media apps though. 
Still, space is cheap.   :)

$ tree -L 3 /boot
/boot
├── config-6.1.67-gentoo-rescue
├── config-6.6.21-gentoo
├── config-6.6.21-gentoo-rescue
├── config-6.6.30-gentoo
├── config-6.6.30-gentoo-rescue
├── config-6.7.9-gentoo
├── config-6.8.5-gentoo-r1
├── early_ucode.cpio
├── EFI
│   ├── BOOT
│   │   └── BOOTX64.EFI
│   ├── Linux
│   └── systemd
│   └── systemd-bootx64.efi
├── intel-uc.img
├── loader
│   ├── entries
│   │   ├── 06-gentoo-rescue-6.6.30.conf
│   │   ├── 07-gentoo-rescue-6.6.30.nonet.conf
│   │   ├── 08-gentoo-rescue-6.6.21.conf
│   │   ├── 09-gentoo-rescue-6.6.21.nonet.conf
│   │   ├── 30-gentoo-6.6.30.conf
│   │   ├── 32-gentoo-6.6.30.conf
│   │   ├── 34-gentoo-6.6.30.conf
│   │   ├── 40-gentoo-6.6.21.conf
│   │   ├── 42-gentoo-6.6.21.conf
│   │   └── 44-gentoo-6.6.21.conf
│   ├── entries.srel
│   ├── loader.conf
│   └── random-seed
├── System.map-6.6.21-gentoo
├── System.map-6.6.21-gentoo-rescue
├── System.map-6.6.30-gentoo
├── System.map-6.6.30-gentoo-rescue
├── System.map-6.7.9-gentoo
├── System.map-6.8.5-gentoo-r1
├── vmlinuz-6.1.67-gentoo-rescue
├── vmlinuz-6.6.21-gentoo
├── vmlinuz-6.6.21-gentoo-rescue
├── vmlinuz-6.6.30-gentoo
├── vmlinuz-6.6.30-gentoo-rescue
├── vmlinuz-6.7.9-gentoo
└── vmlinuz-6.8.5-gentoo-r1

-- 
Regards,
Peter.

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

Michael wrote:
> On Saturday, 15 June 2024 07:53:06 BST Dale wrote:
>> Peter Humphrey wrote:
>>> On Sunday, 2 June 2024 16:11:38 BST Dale wrote:
 My plan, given it is a 1TB, use maybe 300GBs of it.  Leave the rest
 blank.  Have the /boot, EFI directory, root and maybe put /var on a
 separate partition.  I figure for the boot stuff, 3GBs would be plenty
 for all combined.  Make them large so they can grow.  Make root, which
 would include /usr, say 150GBs.  /var can be around 10GBs.  My current
 OS is on a 160GB drive.  I wish I could get the nerve up to use LVM on
 everything except the boot stuff, /boot and the EFI stuff.  If I make
 them like above, I should be good for a long time.  Could go much larger
 tho.  Could use maybe 700GBs of it.  I assume it would use the unused
 part if needed.  I still don't know a lot about those things.  Mostly
 what I see posted on this list really.
>>> Doesn't everyone mount /tmp and /var/tmp/portage on tmpfs these days? I
>>> use
>>> hard disk for a few large packages, but I'm not convinced it's needed -
>>> except when running an emerge -e, that is, when they can get in the way
>>> of lots of others. That's why, some months ago, I suggested introducing
>>> an ability to mark some packages for compilation solitarily. (Is that a
>>> word?)
>>>
>>> Here's the output of parted -l on my main NVMe disk in case it helps:
>>>
>>> Model: Samsung SSD 970 EVO Plus 250GB (nvme)
>>> Disk /dev/nvme1n1: 250GB
>>> Sector size (logical/physical): 512B/512B
>>> Partition Table: gpt
>>> Disk Flags:
>>>
>>> Number  Start   End SizeFile system Name  Flags
>>>
>>>  1  1049kB  135MB   134MB
>>>  2  135MB   4296MB  4161MB  fat32   boot  boot, esp
>>>  3  4296MB  12.9GB  8590MB  linux-swap(v1)  swap1 swap
>>>  4  12.9GB  34.4GB  21.5GB  ext4rescue
>>>  5  34.4GB  60.1GB  25.8GB  ext4root
>>>  6  60.1GB  112GB   51.5GB  ext4var
>>>  7  112GB   114GB   2147MB  ext4local
>>>  8  114GB   140GB   25.8GB  ext4home
>>>  9  140GB   183GB   42.9GB  ext4common
>>>
>>> The common partition is mounted under my home directory, to keep
>>> everything
>>> I'd want to preserve if I made myself a new user account. It's v. useful,
>>> too.
>> I'm starting the process here.  I'm trying to follow the install guide
>> but this is still not clear to me and the guide is not helping.  In your
>> list above, is #2 where /boot is mounted?  Is that where I put kernels,
>> init thingys, memtest and other images to boot from? 
> I'm simplifying this to keep it short, but you can understand the UEFI MoBo 
> firmware to be no different than the legacy CMOS code on your old MoBo, 
> except 
> upgraded, much larger and more powerful in its capabilities.  In particular, 
> it can access, load and execute directly specially structured executables, 
> stored as *.efi files on a GPT formatted disk, in the EFI System Partition 
> (ESP).  The ESP should be formatted as FAT32 and contain a directory named 
> EFI 
> in its top level, where any .EFI executables should be stored.  The ESP does 
> not have to be the first partition on the disk, the UEFI firmware will scan 
> and find .efi files in whichever FAT32 partition they are stored.
>
> NOTES: 
>
> 1. Some MoBo's UEFI firmware offer a 'Compatibility Support Module' (CSM) 
> setting, which if enabled will allow disks with a DOS partition table and a 
> boot loader in the MBR to be booted by the UEFI MoBo.  Since you are starting 
> from scratch and you're not installing Windows 98 there is no reason to have 
> this feature enabled.  I suggest you follow the handbook and use a GPT 
> partitioned disk with an ESP installed boot loader.

Left CSM cut off, didn't know what it was anyway.  LOL  Using GPT,
prefer to use GPT on everything just to be consistent.

> 2. The UEFI firmware is capable of loading Linux kernels directly without a 
> 3rd party boot loader, as long as the kernels have been created to include 
> the 
> 'EFI stub'.  This makes the kernel image executable by the UEFI firmware, 
> without the intervention of a boot loader/manager like GRUB:
>
> https://wiki.gentoo.org/wiki/EFI_stub
>
> Multibooting of different OSs or kernels can be managed thereafter by using 
> the CLI tool efibootmgr, or the UEFI boot menu (by pressing F2, DEL, or some 
> such key during POST).
>
> https://wiki.gentoo.org/wiki/Efibootmgr
>
> Given the above you broadly have the following choices:
>
> a) Simplest, direct, without a 3rd party bootloader:
>
> Mount your ESP under the /boot mountpoint and drop your kernel .efi images in 
> there, under the /boot/EFI/ directory, then boot them directly using the UEFI 
> firmware or efibootmgr to switch between them.
>
> b) Using a bootloader:
>
> Mount your ESP under the /efi mountpoint.  GRUB et al, will install their 
> .efi 
> image in the /efi/EFI/ directory.  You

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

On Saturday, 15 June 2024 07:53:06 BST Dale wrote:
> Peter Humphrey wrote:
> > On Sunday, 2 June 2024 16:11:38 BST Dale wrote:
> >> My plan, given it is a 1TB, use maybe 300GBs of it.  Leave the rest
> >> blank.  Have the /boot, EFI directory, root and maybe put /var on a
> >> separate partition.  I figure for the boot stuff, 3GBs would be plenty
> >> for all combined.  Make them large so they can grow.  Make root, which
> >> would include /usr, say 150GBs.  /var can be around 10GBs.  My current
> >> OS is on a 160GB drive.  I wish I could get the nerve up to use LVM on
> >> everything except the boot stuff, /boot and the EFI stuff.  If I make
> >> them like above, I should be good for a long time.  Could go much larger
> >> tho.  Could use maybe 700GBs of it.  I assume it would use the unused
> >> part if needed.  I still don't know a lot about those things.  Mostly
> >> what I see posted on this list really.
> > 
> > Doesn't everyone mount /tmp and /var/tmp/portage on tmpfs these days? I
> > use
> > hard disk for a few large packages, but I'm not convinced it's needed -
> > except when running an emerge -e, that is, when they can get in the way
> > of lots of others. That's why, some months ago, I suggested introducing
> > an ability to mark some packages for compilation solitarily. (Is that a
> > word?)
> > 
> > Here's the output of parted -l on my main NVMe disk in case it helps:
> > 
> > Model: Samsung SSD 970 EVO Plus 250GB (nvme)
> > Disk /dev/nvme1n1: 250GB
> > Sector size (logical/physical): 512B/512B
> > Partition Table: gpt
> > Disk Flags:
> > 
> > Number  Start   End SizeFile system Name  Flags
> > 
> >  1  1049kB  135MB   134MB
> >  2  135MB   4296MB  4161MB  fat32   boot  boot, esp
> >  3  4296MB  12.9GB  8590MB  linux-swap(v1)  swap1 swap
> >  4  12.9GB  34.4GB  21.5GB  ext4rescue
> >  5  34.4GB  60.1GB  25.8GB  ext4root
> >  6  60.1GB  112GB   51.5GB  ext4var
> >  7  112GB   114GB   2147MB  ext4local
> >  8  114GB   140GB   25.8GB  ext4home
> >  9  140GB   183GB   42.9GB  ext4common
> > 
> > The common partition is mounted under my home directory, to keep
> > everything
> > I'd want to preserve if I made myself a new user account. It's v. useful,
> > too.
> I'm starting the process here.  I'm trying to follow the install guide
> but this is still not clear to me and the guide is not helping.  In your
> list above, is #2 where /boot is mounted?  Is that where I put kernels,
> init thingys, memtest and other images to boot from? 

I'm simplifying this to keep it short, but you can understand the UEFI MoBo 
firmware to be no different than the legacy CMOS code on your old MoBo, except 
upgraded, much larger and more powerful in its capabilities.  In particular, 
it can access, load and execute directly specially structured executables, 
stored as *.efi files on a GPT formatted disk, in the EFI System Partition 
(ESP).  The ESP should be formatted as FAT32 and contain a directory named EFI 
in its top level, where any .EFI executables should be stored.  The ESP does 
not have to be the first partition on the disk, the UEFI firmware will scan 
and find .efi files in whichever FAT32 partition they are stored.

NOTES: 

1. Some MoBo's UEFI firmware offer a 'Compatibility Support Module' (CSM) 
setting, which if enabled will allow disks with a DOS partition table and a 
boot loader in the MBR to be booted by the UEFI MoBo.  Since you are starting 
from scratch and you're not installing Windows 98 there is no reason to have 
this feature enabled.  I suggest you follow the handbook and use a GPT 
partitioned disk with an ESP installed boot loader.

2. The UEFI firmware is capable of loading Linux kernels directly without a 
3rd party boot loader, as long as the kernels have been created to include the 
'EFI stub'.  This makes the kernel image executable by the UEFI firmware, 
without the intervention of a boot loader/manager like GRUB:

https://wiki.gentoo.org/wiki/EFI_stub

Multibooting of different OSs or kernels can be managed thereafter by using 
the CLI tool efibootmgr, or the UEFI boot menu (by pressing F2, DEL, or some 
such key during POST).

https://wiki.gentoo.org/wiki/Efibootmgr

Given the above you broadly have the following choices:

a) Simplest, direct, without a 3rd party bootloader:

Mount your ESP under the /boot mountpoint and drop your kernel .efi images in 
there, under the /boot/EFI/ directory, then boot them directly using the UEFI 
firmware or efibootmgr to switch between them.

b) Using a bootloader:

Mount your ESP under the /efi mountpoint.  GRUB et al, will install their .efi 
image in the /efi/EFI/ directory.  You can have your /boot as a directory on 
your / partition, or on its own separate partition with a more robust fs type 
than ESP's FAT and your kernel images will be installed in there.

c) For systemd you can mount your ESP

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

Peter Humphrey wrote:
> On Sunday, 2 June 2024 16:11:38 BST Dale wrote:
>
>> My plan, given it is a 1TB, use maybe 300GBs of it.  Leave the rest
>> blank.  Have the /boot, EFI directory, root and maybe put /var on a
>> separate partition.  I figure for the boot stuff, 3GBs would be plenty
>> for all combined.  Make them large so they can grow.  Make root, which
>> would include /usr, say 150GBs.  /var can be around 10GBs.  My current
>> OS is on a 160GB drive.  I wish I could get the nerve up to use LVM on
>> everything except the boot stuff, /boot and the EFI stuff.  If I make
>> them like above, I should be good for a long time.  Could go much larger
>> tho.  Could use maybe 700GBs of it.  I assume it would use the unused
>> part if needed.  I still don't know a lot about those things.  Mostly
>> what I see posted on this list really. 
> Doesn't everyone mount /tmp and /var/tmp/portage on tmpfs these days? I use 
> hard disk for a few large packages, but I'm not convinced it's needed - 
> except 
> when running an emerge -e, that is, when they can get in the way of lots of 
> others. That's why, some months ago, I suggested introducing an ability to 
> mark some packages for compilation solitarily. (Is that a word?)
>
> Here's the output of parted -l on my main NVMe disk in case it helps:
>
> Model: Samsung SSD 970 EVO Plus 250GB (nvme)
> Disk /dev/nvme1n1: 250GB
> Sector size (logical/physical): 512B/512B
> Partition Table: gpt
> Disk Flags: 
>
> Number  Start   End SizeFile system Name  Flags
>  1  1049kB  135MB   134MB
>  2  135MB   4296MB  4161MB  fat32   boot  boot, esp
>  3  4296MB  12.9GB  8590MB  linux-swap(v1)  swap1 swap
>  4  12.9GB  34.4GB  21.5GB  ext4rescue
>  5  34.4GB  60.1GB  25.8GB  ext4root
>  6  60.1GB  112GB   51.5GB  ext4var
>  7  112GB   114GB   2147MB  ext4local
>  8  114GB   140GB   25.8GB  ext4home
>  9  140GB   183GB   42.9GB  ext4common
>
> The common partition is mounted under my home directory, to keep everything 
> I'd want to preserve if I made myself a new user account. It's v. useful, too.


I'm starting the process here.  I'm trying to follow the install guide
but this is still not clear to me and the guide is not helping.  In your
list above, is #2 where /boot is mounted?  Is that where I put kernels,
init thingys, memtest and other images to boot from? 

My current layout for a 1TB m.2 stick, typing by hand:

1    8GB        EFI System   
2    400GB    Linux file system for root or /.
3    180GB    Linux file system for /var.

I'll have /home and such on other drives, spinning rust. I'm just
wanting to be sure if my #1 and your #2 is where boot files go, Grub,
kernels, init thingys etc.  I've always had kernels and such on ext2 but
understand efi requires fat32. 

Thanks.

Dale

:-)  :-)

Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

2024-06-15 Thread Vitaliy Perekhovy

On Fri, Jun 14, 2024 at 04:54:09PM -0400, Jack wrote:
> I don't have any such directory.  What package does it belong to, or is  
> it a config setting for portage or another package?

Yes, it is a configuration of portage itself. There is an env variable
CONFIG_PROTECT that contains a list of directories that portage will
protect from automatic modification. Please check this article:
https://wiki.gentoo.org/wiki/CONFIG_PROTECT

You can query that variable by `portageq envvar CONFIG_PROTECT'.

-- 
Regards,
Vitaliy Perekhovy

signature.asc
Description: PGP signature

Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?

2024-06-14 Thread Dale

Dale wrote:
> Howdy, again,
>
> <<< SNIP >>>
>
> Dale
>
> :-)  :-) 
>

Update, number 1.  The CPU finally came in.  It was supposed to be here
Monday, finally left the hub on Wednesday morning, went to the wrong
post office.  This morning, it finally made it to the right post office
and arrived in my mailbox this afternoon.  I might add, some other
things came in too.  I got the thermal pads and a couple more of my
favorite vintage soup spoons.  O_O 

Anyway, installed a couple more 140mm case fans, also added a .5mm thick
thermal pad to the m.2 heatsink so that it makes better contact.  Then I
figured out how to install the CPU cooler base and installed the CPU and
cooler.  I then rechecked all the power and fan connectors.  I dug out
the always handy Ventoy USB stick, thanks again for pointing that thing
out to me ages ago, and I proceeded to my first boot up.  I hit the
power button and watched for smoke at first, with a finger on the power
supply power button, and then watched the fans spin up, 2 CPU fans and 6
case fans.  All good.  Then came the very tiny beep.  A couple seconds
later, the screen popped on and said I had a new CPU installed.  Well
duh!!!  To be honest, I reset to defaults, restarted, then updated the
BIOS.  So far, very good.  No smoke or fire and everything is working. 

Once all that was done, I booted the Ventoy stick and worked my way to a
memtest tool that works with EFI thingy.  It is currently at 16% of
64GBs and testing pretty fast.  Keep in mind, first new rig I built in a
decade, first ASUS mobo, first time using efi thingy and likely other
firsts I don't know about.  This reminds me of the sub-thread
discussion.  Every transistor on the CPU has to work, every chip on mobo
has to work, everything connected to it has to work.  And it all worked,
first time.  The old saying about a wink link in a chain comes to mind. 
This chain has a LOT of links.  They all seem to be strong.

The memtest is at 42% now.  Zero errors. 

Oh, I ordered a 4 port video card.  I found a comparison site that
compares video card abilities and speed.  It is about 150% faster than
current card in my main rig.  It's a Quadro P1000.  It's not a lot but
it is more than enough for me.  It's not here yet so I'm using one of a
four pack I bought when I started the NAS box project.  It has four
ports but is PCIe V2.  New card is PCIe V3.  Any newer, gets expensive
and a whole lot more than I need.  The ports is the big thing. 

Will update as things progress.  I suspect the efi thingy is going to
get interesting.  o_O  A link to pictures will come later.  Oh, the
memory sticks put on a light show.  What is up with that???  The little
m.2 cooler looks really cute.  Pretty much adorable.  LOL  I found one
that looks almost the same but taller and has two heat pipes instead of
one like mine.  Kinda pricey tho.  Must be for really large capacity m.2
sticks.  Some are quite large, and expensive too. 

Later.

Dale

:-)  :-)

Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

2024-06-14 Thread Jack

On 2024.06.14 14:25, Vitaliy Perekhovy wrote:

On Fri, Jun 14, 2024 at 03:53:35PM +, Alan Mackenzie wrote:
> I think portage is at fault here - it should retain the older  
standard
> version of /etc/bash/bashrc so that users can resolve the  
differences

> with a 3-way diff.

Before replace your old bashrc file, portage place the old one
here: /etc/config-archive/etc/bash/bashrc
I don't have any such directory.  What package does it belong to, or is  
it a config setting for portage or another package?

Re: [gentoo-user] CPU frequency governors and temperatures

2024-06-14 Thread Walter Dnes

On Fri, Jun 14, 2024 at 11:54:52AM +0100, Michael wrote

> I would think 46-48°C is refreshingly cool, but it very much depends
> on the CPU chip, the MoBo and its BIOS/microcode settings.

  I looked up my CPU (see my reply to Dale).  The max temp allowed is
71.3 C.  A short kernel compile is one thing.  I tried schedutil during
an emerge world update, and the temp was hitting 70 C.  Ouch!  schedutil
has to go.

> I recall an early i7 CPU laptop would not go above 2,400MHz when
> 4core/8threads were running, but on single core processes I would
> see it on i7z jumping up to 4,200MHz.

  Speaking of cores+threads... I had always thought my cpu had 12
cores.  i.e. /proc/cpuinfo showed 12 "cpus" as did directory
/sys/devices/system/cpu/  But I was wrong.  The specs show 6 real cores,
plus hyperthreading.  See Greg Kroah-Hartman's presentation about the
security issue called "hyperthreading"...
https://events19.linuxfoundation.org/wp-content/uploads/2018/07/gregkh_mds.pdf
Read it and weep.  Page 6 summarizes it succinctly...

==
  OpenBSD was right
* Guessed more problems would be in this area
* Disabled SMT for Intel chips in June 2018
* Repeated the plea to disable this in August 2018
* Prevented almost all MDS issues automatically
* Security over performance
* Huge respect!
==

  I immediately went into the BIOS and disabled hyperthreading... and
adjusted makeopts in make.conf 

> What do you get when you run make with '-j jobs', where jobs=max
> threads of your CPU?

  I hadn't realized that this applied to kernel compiling as well as
portage "emerge".  Since my system now shows 6 (real) cores, I set 5
jobs.  My /usr/src/makeover script is now...

===
#!/bin/bash
make -j 5 && \
make modules_install && \
cp  arch/x86_64/boot/bzImage /boot/vmlinuz-experimental && \
cp System.map /boot/System.map-experimental && \
cp .config /boot/config-experimental
===

  Since I wanted to exorcise schedutil from my system, I had an excuse
to run another compile.  From /usr/src/linux I executed...

cp .config ..
make mrproper
cp ../.config .
time ../makeover

  I had manually selected "userspace" and 290 khz.  The result was
so farcical, I repeated it a second time to confirm it was for real.

real4m43.120s
user20m11.003s
sys 1m25.728s.

  Under 5 minutes.  Like wow!  The CPU stayed pegged at around 2.900 Ghz
and the temperature never got over 47 C.  Thank you very much for that
info about jobs for make.

-- 
Roses are red
Roses are blue
Depending on their velocity
Relative to you

Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

2024-06-14 Thread Vitaliy Perekhovy

On Fri, Jun 14, 2024 at 03:53:35PM +, Alan Mackenzie wrote:
> I think portage is at fault here - it should retain the older standard
> version of /etc/bash/bashrc so that users can resolve the differences
> with a 3-way diff.

Before replace your old bashrc file, portage place the old one
here: /etc/config-archive/etc/bash/bashrc

-- 
Regards,
Vitaliy Perekhovy


signature.asc
Description: PGP signature

Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

2024-06-14 Thread Waldo Lemmer

On Fri, Jun 14, 2024, 19:39 Alan Mackenzie  wrote:

Maybe I should submit a feature request to Gentoo's bugzilla.
>

Occasionally a package updates a file in /etc/, and I can't remember
whether the file was modified by me or not. This usually happens with
things I don't completely understand and therefore don't know what I did in
the past, such as PAM and libvirt.

Adding a comment to the top of each file I edit would help with this, but
sometimes I edit files indirectly using utilities. libvirt's package
recently updated ~30 files in /etc/ and I still don't know which of those
were stock. I hope I got the u's and the z's right.

This feature, if implemented, would help immensely.

>

Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

2024-06-14 Thread netfab

Le 14/06/24 à 19:33, Alan Mackenzie a tapoté :
> Are these files freely available, anywhere, perhaps?

Else, everything is also available from gentoo.org :

https://gitweb.gentoo.org/repo/gentoo.git/tree/app-shells/bash/files/bashrc

Click on plain to  get the raw version.

Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

2024-06-14 Thread netfab

Le 14/06/24 à 19:33, Alan Mackenzie a tapoté :
> Are these files freely available, anywhere, perhaps?
> 

And if you try to get the raw version with wget ?

> $ cd /tmp
> $ wget 
> https://raw.githubusercontent.com/gentoo/gentoo/master/app-shells/bash/files/bashrc

Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

2024-06-14 Thread Alan Mackenzie

Hello, Mike.

On Fri, Jun 14, 2024 at 17:19:31 +0100, Mike Civil wrote:
> On 14/06/2024 17:00, Alan Mackenzie wrote:
> > Right now, I have a problem.  Is there any convenient way I can get the
> > older standard file contents back again, so as to be able to do this
> > 3-way diff?

> Does etc-update or dispatch-conf not give you the option to selectively 
> update and/or to diff the file?

In theory, yes.  In practice, dispatch-conf just offers a single
~130-line long hunk, which is useless for distinguishing wanted pieces of
code from old superseded code.  As I say, what's missing is the old
repository version, which would allow a diff3.

Maybe I should submit a feature request to Gentoo's bugzilla.

> Going forward it might be better to put your custom changes in a file 
> under /etc/bash/bashrc.d which won't then get clobbered by portage.

Or something like that, yes!

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

2024-06-14 Thread Alan Mackenzie

Hello, Netfab.

On Fri, Jun 14, 2024 at 18:22:11 +0200, netfab wrote:
> Le 14/06/24 à 17:53, Alan Mackenzie a tapoté :
> > Right now, I have a problem.  Is there any convenient way I can get
> > the older standard file contents back again, so as to be able to do
> > this 3-way diff?

> The old bashrc file installed by previous versions of the ebuild :

>   
> https://github.com/gentoo/gentoo/blob/master/app-shells/bash/files/bashrc

> The new bashrc file :

>   
> https://github.com/gentoo/gentoo/blob/master/app-shells/bash/files/bashrc-r1

I don't have access to these files, unfortunately.  Github has blocked
them behind a script.  I certainly amn't about to let a Microsoft script
run in my browser.  That is just too high a cost to pay.

Are these files freely available, anywhere, perhaps?

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

2024-06-14 Thread netfab

Le 14/06/24 à 17:53, Alan Mackenzie a tapoté :
> Right now, I have a problem.  Is there any convenient way I can get
> the older standard file contents back again, so as to be able to do
> this 3-way diff?

The old bashrc file installed by previous versions of the ebuild :


https://github.com/gentoo/gentoo/blob/master/app-shells/bash/files/bashrc

The new bashrc file :


https://github.com/gentoo/gentoo/blob/master/app-shells/bash/files/bashrc-r1

Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

2024-06-14 Thread Mike Civil


On 14/06/2024 17:00, Alan Mackenzie wrote:

Right now, I have a problem.  Is there any convenient way I can get the
older standard file contents back again, so as to be able to do this
3-way diff?


Does etc-update or dispatch-conf not give you the option to selectively 
update and/or to diff the file?


Going forward it might be better to put your custom changes in a file 
under /etc/bash/bashrc.d which won't then get clobbered by portage.

Re: [gentoo-user] CPU frequency governors and temperatures

2024-06-14 Thread Michael

On Friday, 14 June 2024 15:18:36 BST Peter Humphrey wrote:
> On Friday, 14 June 2024 13:55:49 BST William Kenworthy wrote:
> > I have a (now quite old) MSsurface-pro4 with an I5 - it runs about
> > 50-60c on normal use but compiling (for example) webkit-gtk and
> > Libreoffice causes the temp to go way too high. I have a script checking
> > the cpu temps - at something like 65 deg it switches from performance to
> > the powersave governer (helps some), at greater than 71c it hibernates.
> > After a cooldown I restart it and it continues on. If I move the 71c
> > trippoint to 72c, it will reliably hard lockup after a short delay.
> > Ideally, I would like to be able to tune MAKEOPTS dynamicly to reduce
> > the number of cpu cores to help further but I dont believe portage can
> > do that.
> 
> Sounds like a useful script, but is 71C really too high? The fan in this i5
> Intel NUC, admittedly much younger (just a few months old), doesn't start
> until the CPU temperature reaches 90C. No doubt you've done your research,
> so by all means ignore me if you want to.

Some Intel chips will not throttle until the temperatures have exceeded 103°C.  
71°C should be considered normal operating temperature, but as always ... it 
depends.


> > I am in the process of setting up distcc to try and help distribute the
> > load while limiting the i5 to -J2 which I hope can speed things up
> > whilst still keeping its cool.
> 
> That makes me think a bit. I used to use a 24-thread Ryzen M9 as a compute
> host with smaller machines being NFS-mounted into a chroot, which worked
> well, but that beast has become too noisy. Now I just use the Gentoo
> packages where I can.

Liquid cooling would have made it as quiet as a church mouse.  ;-)


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] CPU frequency governors and temperatures

2024-06-14 Thread Peter Humphrey

On Friday, 14 June 2024 13:55:49 BST William Kenworthy wrote:

> I have a (now quite old) MSsurface-pro4 with an I5 - it runs about
> 50-60c on normal use but compiling (for example) webkit-gtk and
> Libreoffice causes the temp to go way too high. I have a script checking
> the cpu temps - at something like 65 deg it switches from performance to
> the powersave governer (helps some), at greater than 71c it hibernates.
> After a cooldown I restart it and it continues on. If I move the 71c
> trippoint to 72c, it will reliably hard lockup after a short delay.
> Ideally, I would like to be able to tune MAKEOPTS dynamicly to reduce
> the number of cpu cores to help further but I dont believe portage can
> do that.

Sounds like a useful script, but is 71C really too high? The fan in this i5 
Intel NUC, admittedly much younger (just a few months old), doesn't start 
until the CPU temperature reaches 90C. No doubt you've done your research, so 
by all means ignore me if you want to.

> I am in the process of setting up distcc to try and help distribute the
> load while limiting the i5 to -J2 which I hope can speed things up
> whilst still keeping its cool.

That makes me think a bit. I used to use a 24-thread Ryzen M9 as a compute 
host with smaller machines being NFS-mounted into a chroot, which worked well, 
but that beast has become too noisy. Now I just use the Gentoo packages where 
I can.

-- 
Regards,
Peter.

Re: [gentoo-user] CPU frequency governors and temperatures

2024-06-14 Thread William Kenworthy

On 14/6/24 20:16, Dale wrote:

Walter Dnes wrote:

On Thu, Jun 13, 2024 at 10:49:57PM -0500, Dale wrote

The biggest thing, find out what the exact specs are for your CPU.
Then go from there. That's your starting point tho.

"grep model /proc/cpuinfo" returns 12 instances of...

model : 165
model name : Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz

"I asked Mr.Google" and the best hit was...
https://www.cpu-world.com/Compare/463/Intel_Core_i5_i5-10400_vs_Intel_Core_i5_i5-9400.html
...which compares my CPU against a previous generation. The "model" and
"model name" both match. My CPU is stepping 3 versus 5 on the web page.
The "Core name" is "Comet Lake-S", which matches output from "lspci" on
my system. The base max frequency is 2900 Mhz and the "turbo frequency"
is 4300, which matches what I see during compiles.

Now for the important part...Max temperature = 71.3 C (160.34 F). So
schedutil is not a problem.

If it were my CPU with a max of 70C and I was running at 48C, I wouldn't
be worried. In degrees F, that's a difference of about 40 degrees. It
seems your max temp and mine are pretty close. You are actually running
a little cooler than mine.

Unless someone else sees a problem, I would carry on. The CPU at those
temps should have a nice long life. You can also enjoy the speed increase.

Dale

:-) :-)

I have a (now quite old) MSsurface-pro4 with an I5 - it runs about
50-60c on normal use but compiling (for example) webkit-gtk and
Libreoffice causes the temp to go way too high. I have a script checking
the cpu temps - at something like 65 deg it switches from performance to
the powersave governer (helps some), at greater than 71c it hibernates.
After a cooldown I restart it and it continues on. If I move the 71c
trippoint to 72c, it will reliably hard lockup after a short delay.
Ideally, I would like to be able to tune MAKEOPTS dynamicly to reduce
the number of cpu cores to help further but I dont believe portage can
do that.

I am in the process of setting up distcc to try and help distribute the
load while limiting the i5 to -J2 which I hope can speed things up
whilst still keeping its cool.

BillK

Re: [gentoo-user] CPU frequency governors and temperatures

2024-06-14 Thread Dale

Walter Dnes wrote:
> On Thu, Jun 13, 2024 at 10:49:57PM -0500, Dale wrote
>
>> The biggest thing, find out what the exact specs are for your CPU. 
>> Then go from there.  That's your starting point tho. 
>   "grep model /proc/cpuinfo" returns 12 instances of...
>
> model   : 165
> model name  : Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz
>
>   "I asked Mr.Google" and the best hit was...
> https://www.cpu-world.com/Compare/463/Intel_Core_i5_i5-10400_vs_Intel_Core_i5_i5-9400.html
> ...which compares my CPU against a previous generation.  The "model" and
> "model name" both match.  My CPU is stepping 3 versus 5 on the web page.
> The "Core name" is "Comet Lake-S", which matches output from "lspci" on
> my system.  The base max frequency is 2900 Mhz and the "turbo frequency"
> is 4300, which matches what I see during compiles.
>
>   Now for the important part...Max temperature = 71.3 C (160.34 F).  So
> schedutil is not a problem.
>

If it were my CPU with a max of 70C and I was running at 48C, I wouldn't
be worried.  In degrees F, that's a difference of about 40 degrees.  It
seems your max temp and mine are pretty close.  You are actually running
a little cooler than mine. 

Unless someone else sees a problem, I would carry on.  The CPU at those
temps should have a nice long life.  You can also enjoy the speed increase.

Dale

:-)  :-)

Re: [gentoo-user] CPU frequency governors and temperatures

2024-06-14 Thread Walter Dnes

On Thu, Jun 13, 2024 at 10:49:57PM -0500, Dale wrote

> The biggest thing, find out what the exact specs are for your CPU. 
> Then go from there.  That's your starting point tho. 

  "grep model /proc/cpuinfo" returns 12 instances of...

model   : 165
model name  : Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz

  "I asked Mr.Google" and the best hit was...
https://www.cpu-world.com/Compare/463/Intel_Core_i5_i5-10400_vs_Intel_Core_i5_i5-9400.html
...which compares my CPU against a previous generation.  The "model" and
"model name" both match.  My CPU is stepping 3 versus 5 on the web page.
The "Core name" is "Comet Lake-S", which matches output from "lspci" on
my system.  The base max frequency is 2900 Mhz and the "turbo frequency"
is 4300, which matches what I see during compiles.

  Now for the important part...Max temperature = 71.3 C (160.34 F).  So
schedutil is not a problem.

-- 
Roses are red
Roses are blue
Depending on their velocity
Relative to you

Re: [gentoo-user] CPU frequency governors and temperatures

2024-06-14 Thread Michael

On Friday, 14 June 2024 03:52:38 BST Walter Dnes wrote:
>   I've been doing a bunch of kernel-compiling recently and I've switched
> between schedulers from compile to compile to compare.  See
> https://www.kernel.org/doc/html/v6.6/admin-guide/pm/cpufreq.html for
> background info.  All frequencies in khz.  On my machine...
> 
> * bios_limit == 2901000
> 
> * scaling_available_frequencies == 2901000 290 270 260 240
> 230 210 200 180 170 150 140 120 110
> 90 80
> 
> * scaling_available_governors == conservative ondemand userspace powersave
> performance schedutil NOTE: You must build the governors you want into the
> kernel
> make menuconfig
> Power management and ACPI options
> CPU Frequency scaling
> ...and select the desired governors.
> 
>   *YOUR NUMBERS AND GOVERNORS WILL BE DIFFERENT*  When rebuilding
> kernels, I wanted to do "apples-to-apples" comparisons so I would...
> 
> * make menuconfig (in /usr/src/linux)
> * cp .config .. (*VERY IMPORTANT*)
> * make mrproper (initialize stuff in /usr/src/linux to a sane state)
> * cp ../.config . (restore .config which got wiped by "make mrproper")
> * (build new kernel, "time blah blah blah")
> 
>   I've cobbled together a bash script that can list and set cpu
> frequencies and governors.  Note that root or sudo permission is needed
> to set anything, because the script is writing to the /sys/ filesystem.
> I would hover the mouse pointer over the ICEWM toolbar CPU widget to get
> CPU data.
> 
> * select governor "userspace" and speed 290
> * computer "idling"; CPU speed approx 2.900 ghz and temp 28 C
> * compiling kernel; CPU speed approx 2.900 ghz and temp 35-to-37 C
> * kernel takes 20 minutes to build
> 
> * select governor "schedutil"
> * computer "idling"; CPU speed approx 0.800 ghz and temp 28 C
> * compiling kernel; CPU speed approx 4.200 ghz and temp 46-to-48 C
> * kernel takes 15 minutes to build
> 
>   Is that a dangerously high CPU temperature?  Building the kernel 5
> minutes faster is a minor improvement.

I would think 46-48°C is refreshingly cool, but it very much depends on the 
CPU chip, the MoBo and its BIOS/microcode settings.

As a rule laptops have lower temperatures than desktops, before they start 
throttling.  Laptop platforms also tend to limit the maximum frequency when 
all cores are running to keep the temperature under control.  I recall an 
early i7 CPU laptop would not go above 2,400MHz when 4core/8threads were 
running, but on single core processes I would see it on i7z jumping up to 
4,200MHz.

Similarly, on modern CPUs the boost frequency on all cores is lower than when 
applied on a single core only.

A 25% improvement on a kernel compilation time is rather significant and 
corresponds to your 30% increase in frequency minus thermal losses.

What do you get when you run make with '-j jobs', where jobs=max threads of 
your CPU?

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] CPU frequency governors and temperatures

2024-06-13 Thread Dale

Walter Dnes wrote:
>   I've been doing a bunch of kernel-compiling recently and I've switched
> between schedulers from compile to compile to compare.  See
> https://www.kernel.org/doc/html/v6.6/admin-guide/pm/cpufreq.html for
> background info.  All frequencies in khz.  On my machine...
>
> * bios_limit == 2901000
>
> * scaling_available_frequencies == 2901000 290 270 260 240 
> 230 210 200 180 170 150 140 120 110 
> 90 80
>
> * scaling_available_governors == conservative ondemand userspace powersave 
> performance schedutil
>   NOTE: You must build the governors you want into the kernel
> make menuconfig
> Power management and ACPI options
> CPU Frequency scaling
> ...and select the desired governors.
>
>   *YOUR NUMBERS AND GOVERNORS WILL BE DIFFERENT*  When rebuilding
> kernels, I wanted to do "apples-to-apples" comparisons so I would...
>
> * make menuconfig (in /usr/src/linux)
> * cp .config .. (*VERY IMPORTANT*)
> * make mrproper (initialize stuff in /usr/src/linux to a sane state)
> * cp ../.config . (restore .config which got wiped by "make mrproper")
> * (build new kernel, "time blah blah blah")
>
>   I've cobbled together a bash script that can list and set cpu
> frequencies and governors.  Note that root or sudo permission is needed
> to set anything, because the script is writing to the /sys/ filesystem.
> I would hover the mouse pointer over the ICEWM toolbar CPU widget to get
> CPU data.
>
> * select governor "userspace" and speed 290
> * computer "idling"; CPU speed approx 2.900 ghz and temp 28 C
> * compiling kernel; CPU speed approx 2.900 ghz and temp 35-to-37 C
> * kernel takes 20 minutes to build
>
> * select governor "schedutil"
> * computer "idling"; CPU speed approx 0.800 ghz and temp 28 C
> * compiling kernel; CPU speed approx 4.200 ghz and temp 46-to-48 C
> * kernel takes 15 minutes to build
>
>   Is that a dangerously high CPU temperature?  Building the kernel 5
> minutes faster is a minor improvement.
>


I think some CPUs can run at different temps.  I'd check the specs to
see what the max is.  Obviously, stay away from that.  I converted to F
since C eludes me.  It converts to about 118F.  My FX-8350 during long
compiles reaches 123F, sometimes 125F.  I have a very large cooler on
that thing and serious fans in my case.  I've never worried about it
even at that temp.  I think mine starts to slow down at around 160F. 
Shutdown is a little more than that.  I wouldn't want to go above 135F
myself.  That gives good wiggle room. 

I'd think that 118F is OK but it can vary from CPU to CPU.  I'd check
the specs for that chip and stay at least 30 degrees below that if
possible.  If you're using a laptop, that limits your options.  A
cooling pad can help and make sure the dust bunnies are blown out as
well.  If desktop, blow the dust bunnies out, make sure you have good
case air flow and nothing is blocking the flow in or out.  I tend to
blow mine out twice a year, at least. 

The biggest thing, find out what the exact specs are for your CPU.  Then
go from there.  That's your starting point tho. 

Hope that helps.

Dale

:-)  :-)

Re: [gentoo-user] Weird system freeze?

2024-06-13 Thread William Kenworthy




On 13/6/24 23:57, Dale wrote:

Waldo Lemmer wrote:

By the way, you should really just use the linux-firmware package if
it has the firmware you need. You can plug the name of the firmware
into https://portagefilelist.de to check if it does.

I agree.  For firmware, this is the way to go.  I use dracut and I think
it even picks up firmware that needs to be loaded early on.  So far, I
don't recall ever doing anything, it just works.  Plus, as pointed out
before, it updates as needed.  You don't have to remember to do anything
or track updates elsewhere, which one may forget to do.

Dale

:-)  :-)

P. S.  Still waiting on CPU for the build.  Sent message to seller
requesting them to scream loudly.  I'm about sick of that post office
hub.  :-@

Its in linux-firmware - much easier/safer to install (even temporarily 
while you grab the files) than asking for a random from the web.


BillK


bunyip ~ # equery f linux-firmware|grep i915|grep kbl
/lib/firmware/i915/kbl_dmc_ver1.bin
/lib/firmware/i915/kbl_dmc_ver1_01.bin
/lib/firmware/i915/kbl_dmc_ver1_04.bin
/lib/firmware/i915/kbl_guc_32.0.3.bin
/lib/firmware/i915/kbl_guc_33.0.0.bin
/lib/firmware/i915/kbl_guc_49.0.1.bin
/lib/firmware/i915/kbl_guc_62.0.0.bin
/lib/firmware/i915/kbl_guc_69.0.3.bin
/lib/firmware/i915/kbl_guc_70.1.1.bin
/lib/firmware/i915/kbl_guc_ver9_14.bin
/lib/firmware/i915/kbl_guc_ver9_39.bin
/lib/firmware/i915/kbl_huc_4.0.0.bin
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin
bunyip ~ # ls -al /lib/firmware/i915/kbl_dmc_ver1_04.bin
-rw-r--r-- 1 root root 8840 Jun 3 15:06 
/lib/firmware/i915/kbl_dmc_ver1_04.bin

bunyip ~ #

Re: [gentoo-user] Weird system freeze?

2024-06-13 Thread Waldo Lemmer

On Thu, Jun 13, 2024, 15:06 Walter Dnes  wrote:

I dove into my download with mc, and it's actually a webpage with some
> binary listing!  No wonder it didn't work.  I tried different websites
> and got a 62768 byte file.  I switched from Pale Moon (a Firefox fork) to
> Google Chrome for linux... 62768 bytes.  Even wget got me a 62768 byte
> file.  What's going on???
>

Some file repositories have misleading URLs.

Try going to https://github.com/torvalds/linux, right-clicking on
".gitignore" and clicking "Copy link" or "Save link as...". If you copied
the link, you would've gotten "
https://github.com/torvalds/linux/blob/master/.gitignore;. If you chose to
save it, your browser would've downloaded a file called ".gitignore". Seems
innocuous enough.

What you actually get is just a web page. The actual file is often
accessible from a link labeled "Raw", which leads to the actual file (at
https://raw.githubusercontent.com/torvalds/linux/master/.gitignore in this
case).

By the way, you should really just use the linux-firmware package if it has
the firmware you need. You can plug the name of the firmware into
https://portagefilelist.de to check if it does.

>

Re: [gentoo-user] Weird system freeze?

2024-06-13 Thread Dale

Waldo Lemmer wrote:
> By the way, you should really just use the linux-firmware package if
> it has the firmware you need. You can plug the name of the firmware
> into https://portagefilelist.de to check if it does.

I agree.  For firmware, this is the way to go.  I use dracut and I think
it even picks up firmware that needs to be loaded early on.  So far, I
don't recall ever doing anything, it just works.  Plus, as pointed out
before, it updates as needed.  You don't have to remember to do anything
or track updates elsewhere, which one may forget to do. 

Dale

:-)  :-) 

P. S.  Still waiting on CPU for the build.  Sent message to seller
requesting them to scream loudly.  I'm about sick of that post office
hub.  :-@

Re: [gentoo-user] Weird system freeze?

2024-06-13 Thread Walter Dnes

On Thu, Jun 13, 2024 at 09:33:54AM +0100, Michael wrote

> For the firmware file(s) code to be built into the kernel *all*
> necessary firmware files must be present in your filesystem and the
> path for these defined.  The i915 directory contains the attached
> list of files on my system.

  At first I didn't understand.  It asked for a file, and I gave it that
file, but it still errored out.  Then things got curiouser and curiouser.
Webpage 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
lists kbl_dmc_ver1_04.bin as being 8840 bytes... ***BUT*** the downloaded
file on my system is 62768 bytes!!!  Houston... we have a problem.  I
dove into my download with mc, and it's actually a webpage with some
binary listing!  No wonder it didn't work.  I tried different websites
and got a 62768 byte file.  I switched from Pale Moon (a Firefox fork) to
Google Chrome for linux... 62768 bytes.  Even wget got me a 62768 byte
file.  What's going on???

> PS. Your post prompted me to look into an old i915 system, where I
> discovered a kernel trace hidden undetected in dmesg!  Thank you.  :-)

> ~ $ ls -la /lib/firmware/i915/*kbl*
> lrwxrwxrwx 1 root root 19 May 20 12:18 
> /lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
> -rw-r--r-- 1 root root   8616 May 20 12:18 
> /lib/firmware/i915/kbl_dmc_ver1_01.bin
> -rw-r--r-- 1 root root   8840 May 20 12:18 
> /lib/firmware/i915/kbl_dmc_ver1_04.bin

  Is kbl_dmc_ver1_04.bin still on your system?  Can you email it to me
off-list as an attachment?  That 8840 byte size is what I'm looking for.

  BTW, there is a thread...
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9244
about problems with that firmware.

-- 
Roses are red
Roses are blue
Depending on their velocity
Relative to you

Re: [gentoo-user] Weird system freeze?

2024-06-13 Thread Michael

On Thursday, 13 June 2024 04:11:40 BST Walter Dnes wrote:
> On Tue, Jun 11, 2024 at 07:45:09PM +0100, Michael wrote
> 
> > The above errors are an indication something is amiss with the
> > requisite firmware for your graphics.
> > 
> > Have you specified this in your kernel, or in your initramfs?
> 
>   OK, I've downloaded kbl_dmc_ver1_04.bin now, but I'm having problems
> implementing it.  First I saved it to /lib/firmware, entered the
> firmware name in "make menuconfig" (Build named firmware blobs into the
> kernel) and recompiled; same error message about no such file.
> 
>   Then I created subdirectory /lib/firmware/i915 and moved the bin there.
> I changed the entry in "make menuconfig" to "i915/kbl_dmc_ver1_04.bin"
> and recompiled.  It finds the file now, but still errors out.  dmesg says
> 
> =
> [0.221960] Loading firmware: i915/kbl_dmc_ver1_04.bin
> [0.221962] i915 :00:02.0: [drm] *ERROR* DMC firmware has wrong CSS
> header length (1097158924 bytes) [0.221964] i915 :00:02.0: [drm]
> Failed to load DMC firmware i915/kbl_dmc_ver1_04.bin. Disabling runtime
> power management. [0.221967] i915 :00:02.0: [drm] DMC firmware
> homepage:
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> /tree/i915
> =
> 
>   Any ideas what I'm doing wrong?  And why is it trying to load the file
> even after I (try to) build it into the kernel?

For the firmware file(s) code to be built into the kernel *all* necessary 
firmware files must be present in your filesystem and the path for these 
defined.  The i915 directory contains the attached list of files on my system.

You can fetch these individually, or it would make more sense to emerge sys-
kernel/linux-firmware.  This package will fetch way more than the firmware 
files you need for your hardware.  You can configure it to only fetch the 
files you actually need and use, thereafter:

https://wiki.gentoo.org/wiki/Linux_firmware#Optional:_Savedconfig

but it will require to emerge the package twice each time.

Using sys-kernel/linux-firmware is a better idea than manually downloading 
individual files, because the package is updated regularly with any changes 
released by the OEMs, but either will work as long as all the needed files are 
present.

PS. Your post prompted me to look into an old i915 system, where I discovered 
a kernel trace hidden undetected in dmesg!  Thank you.  :-)~ $ ls -la /lib/firmware/i915/*kbl*
lrwxrwxrwx 1 root root 19 May 20 12:18 /lib/firmware/i915/kbl_dmc_ver1.bin 
-> kbl_dmc_ver1_01.bin
-rw-r--r-- 1 root root   8616 May 20 12:18 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
-rw-r--r-- 1 root root   8840 May 20 12:18 
/lib/firmware/i915/kbl_dmc_ver1_04.bin
-rw-r--r-- 1 root root 176448 May 20 12:18 /lib/firmware/i915/kbl_guc_32.0.3.bin
-rw-r--r-- 1 root root 182912 May 20 12:18 /lib/firmware/i915/kbl_guc_33.0.0.bin
-rw-r--r-- 1 root root 197184 May 20 12:18 /lib/firmware/i915/kbl_guc_49.0.1.bin
-rw-r--r-- 1 root root 200448 May 20 12:18 /lib/firmware/i915/kbl_guc_62.0.0.bin
-rw-r--r-- 1 root root 217664 May 20 12:18 /lib/firmware/i915/kbl_guc_69.0.3.bin
-rw-r--r-- 1 root root 206976 May 20 12:18 /lib/firmware/i915/kbl_guc_70.1.1.bin
-rw-r--r-- 1 root root 142656 May 20 12:18 
/lib/firmware/i915/kbl_guc_ver9_14.bin
-rw-r--r-- 1 root root 147776 May 20 12:18 
/lib/firmware/i915/kbl_guc_ver9_39.bin
-rw-r--r-- 1 root root 226048 May 20 12:18 /lib/firmware/i915/kbl_huc_4.0.0.bin
-rw-r--r-- 1 root root 218688 May 20 12:18 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Weird system freeze?

2024-06-12 Thread Walter Dnes

On Tue, Jun 11, 2024 at 07:45:09PM +0100, Michael wrote
> 
> The above errors are an indication something is amiss with the
> requisite firmware for your graphics.

> Have you specified this in your kernel, or in your initramfs?

  OK, I've downloaded kbl_dmc_ver1_04.bin now, but I'm having problems
implementing it.  First I saved it to /lib/firmware, entered the
firmware name in "make menuconfig" (Build named firmware blobs into the
kernel) and recompiled; same error message about no such file.

  Then I created subdirectory /lib/firmware/i915 and moved the bin there.
I changed the entry in "make menuconfig" to "i915/kbl_dmc_ver1_04.bin"
and recompiled.  It finds the file now, but still errors out.  dmesg says

=
[0.221960] Loading firmware: i915/kbl_dmc_ver1_04.bin
[0.221962] i915 :00:02.0: [drm] *ERROR* DMC firmware has wrong CSS 
header length (1097158924 bytes)
[0.221964] i915 :00:02.0: [drm] Failed to load DMC firmware 
i915/kbl_dmc_ver1_04.bin. Disabling runtime power management.
[0.221967] i915 :00:02.0: [drm] DMC firmware homepage: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
=

  Any ideas what I'm doing wrong?  And why is it trying to load the file
even after I (try to) build it into the kernel?

-- 
Roses are red
Roses are blue
Depending on their velocity
Relative to you

Re: [gentoo-user] teams gentoo and firefox

2024-06-12 Thread Joost Roeleveld





--- Original message ---
From: Pulkit Sukhija 
To: gentoo-user@lists.gentoo.org
Date: Wed, 12 Jun 2024 20:28:51 +0200






microsoft has deprecated the linux binary as per my knowledge. I  
myself use it in a browser now.





On Wed, 12 Jun, 2024, 16:16 hitachi303,

Re: [gentoo-user] teams gentoo and firefox

2024-06-12 Thread Pulkit Sukhija

microsoft has deprecated the linux binary as per my knowledge. I myself use
it in a browser now.

On Wed, 12 Jun, 2024, 16:16 hitachi303, 
wrote:

> Hi there,
>
> is anyone successfully using MS teams? Successfully like able to use it?
> It appears MS is using its powers of being big to shut linux users with
> firefox out or am I wrong with this assessment? I used to be able to use
> it (there was a message they are optimizing for other browsers which I
> do not use and do not intend to use) but now I am just not able to use it.
>
> Any advice beside not using MS teams?
>
> Thanks
>
>

Re: [gentoo-user] teams gentoo and firefox

2024-06-12 Thread Matt Connell

On Wed, 2024-06-12 at 18:43 +0200, hitachi303 wrote:
> Thanks for the answer. I think teams-for-linux is no longer in
> portage.

My bad, this package is actually in ::guru (and some other
repositories), not ::gentoo.  I always have guru enabled so I tend to
forget that its there as a separate repository.

http://gpo.zugaina.org/net-im/teams-for-linux

Re: [gentoo-user] teams gentoo and firefox

2024-06-12 Thread Lewis Handy

Microsoft to my knowledge is no longer developing / supporting teams for
linux, hence why I am using it via Chrome these days - the Linux version
just did not work correctly for me in my corporate environment.

On Wed, 12 Jun 2024 at 17:43, hitachi303 
wrote:

> Am 12.06.24 um 18:22 schrieb Matt Connell:
> > On Wed, 2024-06-12 at 12:46 +0200, hitachi303 wrote:
> >> is anyone successfully using MS teams? Successfully like able to use
> >> it?
> >
> > I use Teams, and I rely on it, but not in a browser.
> >
> > I use the teams-for-linux[1] version, which is available as a
> > flatpak[2] or via portage as net-im/teams-for-linux
> >
> > Personally, I've had great success with the flatpak version, and I have
> > not tried the portage version, although the latter appears to be more
> > up-to-date, so I might make the switch in the future.
> >
> > 1: https://github.com/IsmaelMartinez/teams-for-linux
> >
> > 2: https://flathub.org/apps/com.github.IsmaelMartinez.teams_for_linux
> >
>
> Thanks for the answer. I think teams-for-linux is no longer in portage.
>
> https://packages.gentoo.org/packages/search?q=teams-for-linux
>
>

Re: [gentoo-user] teams gentoo and firefox

2024-06-12 Thread hitachi303


Am 12.06.24 um 18:22 schrieb Matt Connell:

On Wed, 2024-06-12 at 12:46 +0200, hitachi303 wrote:

is anyone successfully using MS teams? Successfully like able to use
it?


I use Teams, and I rely on it, but not in a browser.

I use the teams-for-linux[1] version, which is available as a
flatpak[2] or via portage as net-im/teams-for-linux

Personally, I've had great success with the flatpak version, and I have
not tried the portage version, although the latter appears to be more
up-to-date, so I might make the switch in the future.

1: https://github.com/IsmaelMartinez/teams-for-linux

2: https://flathub.org/apps/com.github.IsmaelMartinez.teams_for_linux



Thanks for the answer. I think teams-for-linux is no longer in portage.

https://packages.gentoo.org/packages/search?q=teams-for-linux

Re: [gentoo-user] teams gentoo and firefox

2024-06-12 Thread Matt Connell

On Wed, 2024-06-12 at 12:46 +0200, hitachi303 wrote:
> is anyone successfully using MS teams? Successfully like able to use
> it?

I use Teams, and I rely on it, but not in a browser.

I use the teams-for-linux[1] version, which is available as a
flatpak[2] or via portage as net-im/teams-for-linux

Personally, I've had great success with the flatpak version, and I have
not tried the portage version, although the latter appears to be more
up-to-date, so I might make the switch in the future.

1: https://github.com/IsmaelMartinez/teams-for-linux

2: https://flathub.org/apps/com.github.IsmaelMartinez.teams_for_linux

Re: [gentoo-user] teams gentoo and firefox

2024-06-12 Thread Lewis Handy

I use it with Chrome and it works just fine for me - not tried with firefox

On Wed, 12 Jun 2024 at 11:46, hitachi303 
wrote:

> Hi there,
>
> is anyone successfully using MS teams? Successfully like able to use it?
> It appears MS is using its powers of being big to shut linux users with
> firefox out or am I wrong with this assessment? I used to be able to use
> it (there was a message they are optimizing for other browsers which I
> do not use and do not intend to use) but now I am just not able to use it.
>
> Any advice beside not using MS teams?
>
> Thanks
>
>

Re: [gentoo-user] teams gentoo and firefox

2024-06-12 Thread Meowie Gamer

Try using chromium maybe?

Sent from Proton Mail Android


 Original Message 
On 6/12/24 06:46, hitachi303  wrote:

>  Hi there,
>  
>  is anyone successfully using MS teams? Successfully like able to use it?
>  It appears MS is using its powers of being big to shut linux users with
>  firefox out or am I wrong with this assessment? I used to be able to use
>  it (there was a message they are optimizing for other browsers which I
>  do not use and do not intend to use) but now I am just not able to use it.
>  
>  Any advice beside not using MS teams?
>  
>  Thanks
>  
>

Re: [gentoo-user] Weird system freeze?

2024-06-12 Thread Michael

On Wednesday, 12 June 2024 06:53:29 BST Walter Dnes wrote:
> On Tue, Jun 11, 2024 at 07:45:09PM +0100, Michael wrote
> 
> > The above errors are an indication something is amiss with the
> > requisite firmware for your graphics.  Have you specified this in
> > your kernel, or in your initramfs?
> > 
> > See here:  https://wiki.gentoo.org/wiki/Intel
> 
>   No mention of my "Comet Lake" system.  According to
> https://en.wikipedia.org/wiki/Skylake_(microarchitecture)
> 
> > Skylake CPUs share their microarchitecture with Kaby Lake, Coffee
> > Lake, Whiskey Lake, and Comet Lake CPUs.
> 
>   I assume that the "kbl" in "kbl_dmc_ver1_04.bin" refers to the Kaby
> Lake family which my "Comet Lake" machine is part of.  According to
> https://wiki.gentoo.org/wiki/Intel#cite_ref-firmware_9-0
> 
> > DMC firmware
> > 
> > Display Microcontroller firmware provides support for advanced graphics
> > low-power idle states.
>   My system has worked fine for years.

The software ecosystem around the hardware has evolved over the years.  It 
wouldn't be unreasonable to assume the current versions of kernel, graphics 
drivers, applications, etc. have been coded to deal with hardware involving 
the latest firmware blobs made available by the OEM.  Power states of devices 
and their power management are known to cause and/or resolve bugs - I have a 
laptop which would crash from overheating before a new BIOS was released by 
the OEM.  There have been wireless NICs where power management had to be 
disabled to stop drop outs.

Consequently, what "worked fine for years" with your graphics may not continue 
to do so hereon.  You can test your browser in full screen using a couple of 
benchmarking websites and see if it crashes again, repeatably:

https://web.basemark.com/

https://browserbench.org/

> > The rtl8168h is related to your NIC.  Assuming you have configured
> > this, does 'ethtool -i eth0' or whatever you card is detected as
> > show if the firmware has been loaded?
> 
>   I don't have "ethtool" installed but I know I don't have that blob.
> According to a discussion at...
> 
> https://superuser.com/questions/1736705/missing-firmware-to-network-boot-deb
> ian-installer-via-ipxe-using-realtek-rtl8111
> 
> ...the blob is necessary for iPXE booting.
> 
>   Both of these blobs seem to support esoteric features, which are
> "nice, but not necessary" for me.

Fair enough, the iPXE function for the NIC should not be related to a graphics 
crash.  The Intel firmware may or may not materially affect your use cases and 
the crash you reported.

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Weird system freeze?

2024-06-11 Thread Walter Dnes

On Tue, Jun 11, 2024 at 07:45:09PM +0100, Michael wrote

> The above errors are an indication something is amiss with the
> requisite firmware for your graphics.  Have you specified this in
> your kernel, or in your initramfs?
> 
> See here:  https://wiki.gentoo.org/wiki/Intel

  No mention of my "Comet Lake" system.  According to
https://en.wikipedia.org/wiki/Skylake_(microarchitecture)

> Skylake CPUs share their microarchitecture with Kaby Lake, Coffee
> Lake, Whiskey Lake, and Comet Lake CPUs.

  I assume that the "kbl" in "kbl_dmc_ver1_04.bin" refers to the Kaby
Lake family which my "Comet Lake" machine is part of.  According to
https://wiki.gentoo.org/wiki/Intel#cite_ref-firmware_9-0

> DMC firmware
>
> Display Microcontroller firmware provides support for advanced graphics 
> low-power idle states.

  My system has worked fine for years.

> The rtl8168h is related to your NIC.  Assuming you have configured
> this, does 'ethtool -i eth0' or whatever you card is detected as
> show if the firmware has been loaded?

  I don't have "ethtool" installed but I know I don't have that blob.
According to a discussion at...

https://superuser.com/questions/1736705/missing-firmware-to-network-boot-debian-installer-via-ipxe-using-realtek-rtl8111

...the blob is necessary for iPXE booting.

  Both of these blobs seem to support esoteric features, which are
"nice, but not necessary" for me.

-- 
Roses are red
Roses are blue
Depending on their velocity
Relative to you

Re: [gentoo-user] Re: (EE) AddScreen/ScreenInit failed for driver 0 [SOLVED]

2024-06-11 Thread Michael

On Tuesday, 11 June 2024 20:17:44 BST n952162 wrote:
> On 6/11/24 17:58, n952162 wrote:
> > Am I forgetting something ?
> 
> Yes. x11-drivers/xf86-video-intel

This package will be brought in as a dependency by emerge, as long as you have 
specified the correct VIDEO_CARDS="" drivers[1] in your make.conf and then 
emerged x11-base/xorg-server.[2]

Therefore it is not xf86-video-intel you forgot, but adding the necessary in 
make.conf.

[1] https://wiki.gentoo.org/wiki/Intel
[2] https://wiki.gentoo.org/wiki/X_server


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Weird system freeze?

2024-06-11 Thread Matt Connell

On Tue, 2024-06-11 at 00:14 -0400, Walter Dnes wrote:
>   What is "lean"?  My system has 16 gigs ram.

16GB is what I meant by lean.

IMO, for a machine that is running desktop applications and building
packages while being used interactively, at the same time, 16 just
doesn't cut it.  It doesn't for me, anyway.

Given what you said, and that you weren't building while trying to use
the machine actively, I'm certain you didn't run out of memory, but
I've experienced the same behavior when I *do* run out of memory. 
That's all I really meant.

Re: [gentoo-user] (EE) AddScreen/ScreenInit failed for driver 0

On 6/11/24 19:48, Joost Roeleveld wrote:

--- Original message ---
From: n952162 
To: gentoo-user@lists.gentoo.org
Date: Tue, 11 Jun 2024 18:59:25 +0200

Just wanted to see if it was a known, current issue before I put in some
due-diligence.

On 6/11/24 18:55, Joost Roeleveld wrote:

--- Original message ---
From: n952162 
To: gentoo-user@lists.gentoo.org
Date: Tue, 11 Jun 2024 17:58:40 +0200

Am I forgetting something ?

Yes:
What are you trying to do.
What you tried so far
The full logs
What versions are you using
Anything else that would be helpful

With just that, no clue.
Tried google?

Well, actually, no.  But DDG and startpage.

Re: [gentoo-user] Weird system freeze?

2024-06-11 Thread Michael

On Tuesday, 11 June 2024 19:30:28 BST Walter Dnes wrote:
> On Tue, Jun 11, 2024 at 11:05:27AM +0100, Michael wrote
> 
> > Can you share the output of your dmesg?
> 
>   The only potentially interesting stuff is attempting to load a couple
> of firmware blobs that I'm not aware of...
> 
> [0.220521] Loading firmware: i915/kbl_dmc_ver1_04.bin
> [0.220530] i915 :00:02.0: Direct firmware load for
> i915/kbl_dmc_ver1_04.bin failed with error -2 [0.220533] i915
> :00:02.0: [drm] Failed to load DMC firmware i915/kbl_dmc_ver1_04.bin.
> Disabling runtime power management. [0.220535] i915 :00:02.0: [drm]
> DMC firmware homepage:
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> /tree/i915
> * [
>   57.302978] Loading firmware: rtl_nic/rtl8168h-2.fw
> [   57.302993] r8169 :01:00.0: Direct firmware load for
> rtl_nic/rtl8168h-2.fw failed with error -2 [   57.302997] r8169
> :01:00.0: Unable to load firmware rtl_nic/rtl8168h-2.fw (-2)

The above errors are an indication something is amiss with the requisite 
firmware for your graphics.  Have you specified this in your kernel, or in 
your initramfs?

See here:  https://wiki.gentoo.org/wiki/Intel

The rtl8168h is related to your NIC.  Assuming you have configured this, does 
'ethtool -i eth0' or whatever you card is detected as show if the firmware has 
been loaded?


> > Next time it happens you can boot straight back into a LiveUSB and
> > save dmesg, syslog and Xorg.0.log from your disk, where the errors
> > related to the crash should have been captured.


>   It's too late now.  The only potentially interesting stuff is..
> .
> [89.701] (EE) Unable to locate/open config file: "xorg.conf"
[snip ...]

Nothing interesting in that, but dmesg reveals a firmware issue.



signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] (EE) AddScreen/ScreenInit failed for driver 0

On 6/11/24 20:16, Michael wrote:

On Tuesday, 11 June 2024 18:48:56 BST Joost Roeleveld wrote:

--- Original message ---
From: n952162 
To: gentoo-user@lists.gentoo.org
Date: Tue, 11 Jun 2024 18:59:25 +0200

Just wanted to see if it was a known, current issue before I put in some
due-diligence.

On 6/11/24 18:55, Joost Roeleveld wrote:

--- Original message ---
From: n952162 
To: gentoo-user@lists.gentoo.org
Date: Tue, 11 Jun 2024 17:58:40 +0200

Am I forgetting something ?

Yes:
What are you trying to do.
What you tried so far
The full logs
What versions are you using
Anything else that would be helpful

With just that, no clue.
Tried google?

In the first instance you can check if graphics drivers & firmware have been
configured correctly (in kernel/initramfs) and if they have loaded.

Otherwise post additional info in case someone can come up with a more
meaningful suggestion.

That's where I suspect the problem is, but how do I do that?

Note that this hardware has been running gentoo for years.

Re: [gentoo-user] (EE) AddScreen/ScreenInit failed for driver 0


On 6/11/24 18:55, Joost Roeleveld wrote:


--- Original message ---
From: n952162 
To: gentoo-user@lists.gentoo.org
Date: Tue, 11 Jun 2024 17:58:40 +0200



Am I forgetting something ?


Yes:
What are you trying to do.
What you tried so far
The full logs
What versions are you using
Anything else that would be helpful




Okay, I'm afraid I know what's wrong, unfortunately ...

I'm re-installing gentoo, because everybody here said my configuration
is too old.

X won't start, and if I try to do xterm over ssh, I get the old error:

   /xterm: Xt error: Can't open display: /
   /xterm: DISPLAY is not set/

I followed my usual, successful recipe.  One thing I did was to use
genkernel to build a new kernel based on default values. That's always
worked okay but I'm wondering if it's not okay anymore.  Unfortunately,
I neglected to save my old /proc/config.gz.  I've attached the new one.

I just downloaded the minimal cd about 2 weeks ago.
[53.070] 
X.Org X Server 1.21.1.13
X Protocol Version 11, Revision 0
[53.076] Current Operating System: Linux txm2 6.6.30-gentoo-x86_64 #1 SMP 
PREEMPT_DYNAMIC Sat Jun  1 12:13:53 -00 2024 x86_64
[53.076] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.6.30-gentoo-x86_64 
root=UUID=7b3a15f7-9d6b-40af-a161-be74d9f0c4c3 ro
[53.082]  
[53.085] Current version of pixman: 0.43.4
[53.090]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[53.090] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[53.100] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 11 20:00:54 
2024
[53.139] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[53.169] (==) No Layout section.  Using the first Screen section.
[53.169] (==) No screen section available. Using defaults.
[53.169] (**) |-->Screen "Default Screen Section" (0)
[53.169] (**) |   |-->Monitor ""
[53.169] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[53.169] (**) Allowing byte-swapped clients
[53.169] (==) Automatically adding devices
[53.169] (==) Automatically enabling devices
[53.169] (==) Automatically adding GPU devices
[53.169] (==) Automatically binding GPU devices
[53.187] (==) Max clients allowed: 256, resource mask: 0x1f
[53.215] (WW) The directory "/usr/share/fonts/TTF" does not exist.
[53.216]Entry deleted from font path.
[53.216] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[53.216]Entry deleted from font path.
[53.216] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[53.216]Entry deleted from font path.
[53.216] (WW) `fonts.dir' not found (or not valid) in 
"/usr/share/fonts/100dpi".
[53.216]Entry deleted from font path.
[53.216](Run 'mkfontdir' on "/usr/share/fonts/100dpi").
[53.216] (WW) `fonts.dir' not found (or not valid) in 
"/usr/share/fonts/75dpi".
[53.216]Entry deleted from font path.
[53.216](Run 'mkfontdir' on "/usr/share/fonts/75dpi").
[53.216] (==) FontPath set to:
/usr/share/fonts/misc
[53.216] (==) ModulePath set to "/usr/lib64/xorg/modules"
[53.216] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[53.216] (II) Module ABI versions:
[53.216]X.Org ANSI C Emulation: 0.4
[53.216]X.Org Video Driver: 25.2
[53.216]X.Org XInput driver : 24.4
[53.216]X.Org Server Extension : 10.0
[53.218] (II) xfree86: Adding drm device (/dev/dri/card0)
[53.218] (II) Platform probe for 
/sys/devices/pci:00/:00:02.0/drm/card0
[53.234] (--) PCI:*(0@0:2:0) 8086:29c2:1043:8276 rev 2, Mem @ 
0xfe90/524288, 0xd000/268435456, 0xfe80/1048576, I/O @ 
0xbc00/8, BIOS @ 0x/131072
[53.234] (--) PCI: (0@0:2:1) 8086:29c3:1043:8276 rev 2, Mem @ 
0xfe98/524288
[53.234] (II) LoadModule: "glx"
[53.255] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[53.398] (II) Module glx: vendor="X.Org Foundation"
[53.398]compiled for 1.21.1.13, module version = 1.0.0
[53.398]ABI class: X.Org Server Extension, version 10.0
[53.398] (==) Matched intel as autoconfigured driver 0
[53.398] (==) Matched modesetting as autoconfigured driver 1
[53.398] (==) Matched fbdev as autoconfigured driver 2
[53.398] (==) Matched vesa as autoconfigured driver 3
[53.398] (==) Assigned the driver to the xf86ConfigLayout
[53.398] (II) LoadModule: "intel"
[53.413] (WW) Warning, couldn't open module intel
[53.413] (EE) Failed to load module

Re: [gentoo-user] Weird system freeze?

2024-06-11 Thread Walter Dnes

On Tue, Jun 11, 2024 at 11:05:27AM +0100, Michael wrote

> Can you share the output of your dmesg?

  The only potentially interesting stuff is attempting to load a couple
of firmware blobs that I'm not aware of...

[0.220521] Loading firmware: i915/kbl_dmc_ver1_04.bin
[0.220530] i915 :00:02.0: Direct firmware load for 
i915/kbl_dmc_ver1_04.bin failed with error -2
[0.220533] i915 :00:02.0: [drm] Failed to load DMC firmware 
i915/kbl_dmc_ver1_04.bin. Disabling runtime power management.
[0.220535] i915 :00:02.0: [drm] DMC firmware homepage: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
*
[   57.302978] Loading firmware: rtl_nic/rtl8168h-2.fw
[   57.302993] r8169 :01:00.0: Direct firmware load for 
rtl_nic/rtl8168h-2.fw failed with error -2
[   57.302997] r8169 :01:00.0: Unable to load firmware 
rtl_nic/rtl8168h-2.fw (-2)


> Next time it happens you can boot straight back into a LiveUSB and
> save dmesg, syslog and Xorg.0.log from your disk, where the errors
> related to the crash should have been captured.

  It's too late now.  The only potentially interesting stuff is..
.
[89.701] (EE) Unable to locate/open config file: "xorg.conf"
[89.701] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[89.732] (==) No Layout section.  Using the first Screen section.
[89.732] (==) No screen section available. Using defaults.
[89.732] (**) |-->Screen "Default Screen Section" (0)
[89.732] (**) |   |-->Monitor ""
[89.732] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
*
[89.784] (II) LoadModule: "glx"
[89.785] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[89.915] (II) Module glx: vendor="X.Org Foundation"
[89.915]compiled for 1.21.1.13, module version = 1.0.0
[89.915]ABI class: X.Org Server Extension, version 10.0
[89.915] (==) Matched intel as autoconfigured driver 0
[89.915] (==) Matched modesetting as autoconfigured driver 1
[89.915] (==) Matched fbdev as autoconfigured driver 2
[89.915] (==) Matched vesa as autoconfigured driver 3
[89.915] (==) Assigned the driver to the xf86ConfigLayout
[89.915] (II) LoadModule: "intel"
[89.916] (WW) Warning, couldn't open module intel
[89.916] (EE) Failed to load module "intel" (module does not exist, 0)
[89.916] (II) LoadModule: "modesetting"
[89.916] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[90.040] (II) Module modesetting: vendor="X.Org Foundation"
[90.040]compiled for 1.21.1.13, module version = 1.21.1
[90.040]Module class: X.Org Video Driver
[90.040]ABI class: X.Org Video Driver, version 25.2
[90.040] (II) LoadModule: "fbdev"
[90.040] (WW) Warning, couldn't open module fbdev
[90.040] (EE) Failed to load module "fbdev" (module does not exist, 0)
[90.040] (II) LoadModule: "vesa"
[90.040] (WW) Warning, couldn't open module vesa
[90.040] (EE) Failed to load module "vesa" (module does not exist, 0)
[90.040] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
*
[90.066] (II) LoadModule: "glamoregl"
[90.066] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
[90.130] (II) Module glamoregl: vendor="X.Org Foundation"
[90.130]compiled for 1.21.1.13, module version = 1.0.1
[90.130]ABI class: X.Org ANSI C Emulation, version 0.4
[90.704] (II) modeset(0): glamor X acceleration enabled on Mesa Intel(R) 
UHD Graphics 630 (CML GT2)
[90.704] (II) modeset(0): glamor initialized
*
[91.552] (II) LoadModule: "fb"
[91.552] (II) Module "fb" already built-in
*
[92.423] (II) LoadModule: "libinput"
[92.423] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so
[92.541] (II) Module libinput: vendor="X.Org Foundation"
[92.541]compiled for 1.21.1.13, module version = 1.4.0
[92.541]Module class: X.Org XInput Driver
[92.541]ABI class: X.Org XInput driver, version 24.4
*


-- 
Roses are red
Roses are blue
Depending on their velocity
Relative to you

Re: [gentoo-user] (EE) AddScreen/ScreenInit failed for driver 0

2024-06-11 Thread Michael

On Tuesday, 11 June 2024 18:48:56 BST Joost Roeleveld wrote:
> --- Original message ---
> From: n952162 
> To: gentoo-user@lists.gentoo.org
> Date: Tue, 11 Jun 2024 18:59:25 +0200
> 
> 
> > Just wanted to see if it was a known, current issue before I put in some
> > due-diligence.
> > 
> > On 6/11/24 18:55, Joost Roeleveld wrote:
> >> --- Original message ---
> >> From: n952162 
> >> To: gentoo-user@lists.gentoo.org
> >> Date: Tue, 11 Jun 2024 17:58:40 +0200
> >> 
> >> 
> >>> Am I forgetting something ?
> >> 
> >> Yes:
> >> What are you trying to do.
> >> What you tried so far
> >> The full logs
> >> What versions are you using
> >> Anything else that would be helpful
> 
> With just that, no clue.
> Tried google?

In the first instance you can check if graphics drivers & firmware have been 
configured correctly (in kernel/initramfs) and if they have loaded.

Otherwise post additional info in case someone can come up with a more 
meaningful suggestion.

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] (EE) AddScreen/ScreenInit failed for driver 0

2024-06-11 Thread Joost Roeleveld

--- Original message ---
From: n952162 
To: gentoo-user@lists.gentoo.org
Date: Tue, 11 Jun 2024 18:59:25 +0200

Just wanted to see if it was a known, current issue before I put in some
due-diligence.

On 6/11/24 18:55, Joost Roeleveld wrote:

--- Original message ---
From: n952162 
To: gentoo-user@lists.gentoo.org
Date: Tue, 11 Jun 2024 17:58:40 +0200

Am I forgetting something ?

Yes:
What are you trying to do.
What you tried so far
The full logs
What versions are you using
Anything else that would be helpful

With just that, no clue.
Tried google?

Re: [gentoo-user] (EE) AddScreen/ScreenInit failed for driver 0