Michael wrote:
> On Sunday, 3 March 2024 19:31:30 GMT Dale wrote:
>>
>> Since my last post, I did my weekly updates. During that, I log out,
>> switch to boot runlevel, restart anything that checkrestart says needs
>> it, then back to default runlevel and log back in. With the config file
>>
Daniel Frey wrote:
> On 3/3/24 13:57, Dale wrote:
>> I think most is in the .config directory now. I have to say tho, I used
>> to zap that thing about once a year, sometimes two, to correct some
>> things that were weird but couldn't fix otherwise. I think the devs try
>> to make things forward
On 03/03/24 at 04:18, Jack wrote:
On 2024.03.03 15:23, Wol wrote:
On 03/03/2024 19:40, Jack wrote:
On 2024.03.03 13:54, Wols Lists wrote:
On 03/03/2024 09:47, Wols Lists wrote:
I'm getting this output from
emerge --update --newuse --deep --with-bdeps=y @world
whoops I mean "emerge
On 3/3/24 13:48, Michael wrote:
It could be AMD have not yet released microcode updates for the community.
OEMs receive new microcode first and patch it in their MoBo BIOS/UEFI
firmware. Eventually the CPU manufacturers release microcode for older CPUs
no longer supported by OEMs. Since you
On 3/3/24 13:57, Dale wrote:
I think most is in the .config directory now. I have to say tho, I used
to zap that thing about once a year, sometimes two, to correct some
things that were weird but couldn't fix otherwise. I think the devs try
to make things forward compatible but no one is
Daniel Frey wrote:
> On 3/3/24 11:31, Dale wrote:
>> Since my last post, I did my weekly updates. During that, I log out,
>> switch to boot runlevel, restart anything that checkrestart says needs
>> it, then back to default runlevel and log back in. With the config file
>> change, my monitors
On Sunday, 3 March 2024 19:14:23 GMT Daniel Frey wrote:
> Hi all,
>
> I've always had problems updating the microcode for my AMD processor. I
> have various other Intel-based PCs and this has never been an issue.
>
> I have confirmed it's not updating:
>
>
> ~ # dmesg | grep -i microcode
> [
On Sunday, 3 March 2024 19:31:30 GMT Dale wrote:
> Daniel Frey wrote:
> > On 2/29/24 03:27, Dale wrote:
> >> To provide a little more info on how this works. This is how I did
> >> it. It helps a LOT to have tab completion with this. It will fill
> >> in a lot of the info and when unsure, list
On 2024.03.03 15:23, Wol wrote:
On 03/03/2024 19:40, Jack wrote:
On 2024.03.03 13:54, Wols Lists wrote:
On 03/03/2024 09:47, Wols Lists wrote:
I'm getting this output from
emerge --update --newuse --deep --with-bdeps=y @world
whoops I mean "emerge --depclean"
I'm trying to get a clean
On 03/03/2024 19:40, Jack wrote:
On 2024.03.03 13:54, Wols Lists wrote:
On 03/03/2024 09:47, Wols Lists wrote:
I'm getting this output from
emerge --update --newuse --deep --with-bdeps=y @world
whoops I mean "emerge --depclean"
I'm trying to get a clean system, and don't know what exactly
On 2024.03.03 13:54, Wols Lists wrote:
On 03/03/2024 09:47, Wols Lists wrote:
I'm getting this output from
emerge --update --newuse --deep --with-bdeps=y @world
whoops I mean "emerge --depclean"
I'm trying to get a clean system, and don't know what exactly is
wrong, or what to try ...
On 3/3/24 11:31, Dale wrote:
Since my last post, I did my weekly updates. During that, I log out,
switch to boot runlevel, restart anything that checkrestart says needs
it, then back to default runlevel and log back in. With the config file
change, my monitors came up just like they should. I
Daniel Frey wrote:
> On 2/29/24 03:27, Dale wrote:
>> To provide a little more info on how this works. This is how I did
>> it. It helps a LOT to have tab completion with this. It will fill
>> in a lot of the info and when unsure, list the available options.
>> First, I had to install the
Hi all,
I've always had problems updating the microcode for my AMD processor. I
have various other Intel-based PCs and this has never been an issue.
I have confirmed it's not updating:
~ # dmesg | grep -i microcode
[0.201619] Zenbleed: please update your microcode for the most
optimal
On 2/29/24 03:27, Dale wrote:
To provide a little more info on how this works. This is how I did it.
It helps a LOT to have tab completion with this. It will fill in a lot
of the info and when unsure, list the available options. First, I had to
install the package xrandr. My first problem
On 03/03/2024 09:47, Wols Lists wrote:
I'm getting this output from
emerge --update --newuse --deep --with-bdeps=y @world
whoops I mean "emerge --depclean"
I'm trying to get a clean system, and don't know what exactly is wrong,
or what to try ...
Cheers,
Wol
Am Sonntag, 3. März 2024, 14:32:41 CET schrieb Andreas K. Huettel:
> > I set CFLAGS="-O2 -pipe march=x86-64-v2" on the buildhost and performed a
> > emerge -ev @world, re-creating all packages in binary form.
> >
> > My expectation was that these packages would work on the target platform,
> >
>
> I set CFLAGS="-O2 -pipe march=x86-64-v2" on the buildhost and performed a
> emerge -ev @world, re-creating all packages in binary form.
>
> My expectation was that these packages would work on the target platform, but
> they don't. Error message "CPU ISA level is lower than required".
>
I'm getting this output from
emerge --update --newuse --deep --with-bdeps=y @world
Calculating dependencies... done!
* Dependencies could not be completely resolved due to
* the following required packages not being installed:
*
* >=dev-libs/icu-73.1:0/73.1= pulled in by:
*
Hi,
I tried to tweak some settings regarding CFLAGS="march=x86-64-v2" on my
buildhost and then install the binary packages on the target machines.
Buildhost: AMD Ryzen 7 2700; ld.so --help says:
Subdirectories of glibc-hwcaps directories, in priority order:
x86-64-v4
x86-64-v3 (supported,
20 matches
Mail list logo
