Re: Cannot Login to Fedora Forums Issue

2022-08-22 Thread Kevin Fenzi
On Fri, Aug 19, 2022 at 07:59:59PM -, Robert Weir wrote: > I am having issues with knowing what exact URLs to use and also cannot get my > SSO working for Fedora. Hey Robert. Sorry to hear it. Your subject mentions Fedora Forums... If you mean https://forums.fedoraforum.org/forum.php that

Re: Fw: mount fails for btrfs filesystem, need help please.

2022-08-22 Thread George N. White III
On Mon, Aug 22, 2022 at 9:57 AM George R Goffe via users < users@lists.fedoraproject.org> wrote: > Hi, > > I started getting i/o error messages accessing this filesystem so I > rebooted the system. This might have been the wrong thing to do. This > subsequent boot went to maintenance mode due the

Fw: mount fails for btrfs filesystem, need help please.

2022-08-22 Thread George R Goffe via users
Hi, I started getting i/o error messages accessing this filesystem so I rebooted the system. This might have been the wrong thing to do. This subsequent boot went to maintenance mode due the filesystem's path being in /etc/fstab. I need some help with this please. Here is what mount says: mou

Re: Interrogating BIOS from CLI? - dmidecode doesn't have the info

2022-08-22 Thread Tim via users
Roger Heflin: >> And the bios will have no way to know what is hot-swappable as that is >> an external case feature/add-on enclosure. Philip Rhoades: > Not sure what you mean - I can set "Hot Swappable" in the BIOS. For something to be hotswappable, everything has to support it (the host port, t

Re: Interrogating BIOS from CLI? - dmidecode doesn't have the info

2022-08-22 Thread ToddAndMargo via users
On 8/21/22 23:23, Philip Rhoades via users wrote: I think he is stuck with booting into BIOS It does look like it . . a bit sad . . Just out of curiosity, is there some reason why you can't reboot? User have hot tar and feathers waiting for you? ___

Re: Interrogating BIOS from CLI? - dmidecode doesn't have the info

2022-08-22 Thread Roger Heflin
It generally is worse than that. It should be almost trivial to code, if you have the internal document for each bios version laying out the structure that is stored in the nvram. The other issue is even though it is trivial, the structure could be different between bios versions in the same MB,