Alan Mackenzie wrote:
> Hello, Wol.
>
> On Mon, Jun 17, 2024 at 13:39:35 +0100, Wols Lists wrote:
>> On 17/06/2024 12:17, Alan Mackenzie wrote:
>>> Sadly, the FBR never made it into commercial deployment.
>> Was that the one with the heavy water moderator? So a thermal runaway
>> was impossible
Hello, Wol.
On Mon, Jun 17, 2024 at 13:39:35 +0100, Wols Lists wrote:
> On 17/06/2024 12:17, Alan Mackenzie wrote:
> > Sadly, the FBR never made it into commercial deployment.
> Was that the one with the heavy water moderator? So a thermal runaway
> was impossible because you'd have no
On 17/06/2024 12:17, Alan Mackenzie wrote:
Sadly, the FBR never made it into commercial deployment.
Was that the one with the heavy water moderator? So a thermal runaway
was impossible because you'd have no moderator left?
Cheers,
Wol
Hello, Peter.
On Sun, Jun 16, 2024 at 23:52:15 +0100, Peter Humphrey wrote:
> 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.
Dale wrote:
>
> 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.
On 15/06/2024 21:10, Alan Mackenzie wrote:
Why didn't you keep a copy of the old file?
Because that's one of the itsy-bitsy routine things that ought to be
automatic, not something that each user should have to think out for
himself.
Dunno which update tool it is, but istr there is a tool
On Sonntag, 16. Juni 2024, 12:59:54 CEST Michael wrote:
> 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 ... :-)
>
I found the solution for my specific setup (lvm+luks+secureboot:
On 6/16/24 7:22 PM, Wols Lists wrote:
> 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
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
>>
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.
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
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.
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
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
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
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
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
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
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.
--
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.
>
>>
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.
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 ->
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
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.
> > >>
> > >>
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
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.
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
> 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
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
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
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 /
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
>
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 :
>
>
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
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
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.
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
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.
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)
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...
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
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:
> >
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:
>
>
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
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
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
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
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):
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
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.
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
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:
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
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.
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
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
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
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
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
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
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
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.
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
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
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
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 :
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
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
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
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
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
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)
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
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...
>
> *
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
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...
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
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
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?
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
--- 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
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
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
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
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
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
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
>
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
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?
>
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
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
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
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
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...
>
> [
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
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 ?
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
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
--- 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
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
201 - 300 of 146667 matches
Mail list logo
