I'm currently running FC5, will probably upgrade to F7 in a couple of months.
Unfortunately my CD/DVD rewriter appears to have died, before it's
even seen a dual layer disk :'(
SATA hard drives run without problems for me, but now that SATA
optical drives are starting to appear in the shops, would it be OK to
buy one of these and get rid of another wide ribbon cable?
Is anybody already running them with Fedora?
Thanks for any advice/experiences.
On Tue, 2020-04-28 at 16:45 +0000, david richyad wrote:
> cisco ise helps safeguard your business. It lets you control access throughout your network, see the user and device details, and stop/contain any threats. You can also use it to enforce security policies throughout your network. As a result, it helps prevent any technical issues and strengthens your cybersecurity measures. In short, you can manage your network security with more ease. Everything can be handled in one place, as opposed to needing multiple different applications open at once.
Does this have anything to do with Fedora? Advertising is not
acceptable on this list.
I have both MATE and Xfce installed. If I boot
into MATE, such that Xfce is not running, or not
start a GUI at all, how do I do a group reinstall
Computers are like air conditioners.
They malfunction when you open windows
I have a Dell Latitude 5480 laptop with a Fedora 36 install. It crashes
regularly, uptime can sometimes be less that 5 mins but sometimes it
lasts several hours. There is no trace at all in journalctl of its
demise. It behaves like a machine with a memory issue. I've moved the
memory from one slot to another and cleaned the connector.
I've been using Redhat style systems for over 20 years and have known
uptimes of several years. This laptop also boots Win10 and that install
is stable. The machine passes Dells internal diagnostics. I'm travelling
this week and don't have access to memtest86, but the Win10 memory test
passes. Once I'm back home I can network boot it and run memtest86 and
FC36 live - which will eliminate the ssd & its controller from the picture.
This machine has a KabbyLake processor (Intel Core i5-7200U 2.50GHz), 8G
memory, an Intel i915 (HD Graphics 620) GPU and SSD storage. I've read
on various forums that this combination of CPU/GPU can be problematic
and some mentions that an upcoming Kernel release may contain a remedy
In addition to the FC36 standard kernel, I have tried a 6.0 kernel build
and even the development 6.1 kernel from Rawhide's daily builds ( Beta
for FC38 ) and its related firmware RPM. Also tried loading the 5.11
kernel from FC34. All with the same results. In fact the FC38 beta
kernel only survives a few minutes even without the GUI.
Is this hardware faulty, despite Win10 being stable? Does the Linux
install stress the hardware in a way Win10 doesent. Should I hold on
for a later kernel release with a fix.
Is anyone else experiencing this issue? I'd value any insights.
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
I'm using F36 on a 10 year old laptop running an nividia GPU (GeForce
GT 560M). I'm using the nvidia drivers from rpmfusion (390xx).
Yesterday, I ran dnf upgrade and got the new 6.0.5 kernel. I lost the
native screen resolution (1920x1080) and have a 1024x768 instead.
I then removed the nvidia driver with dnf but it did not improve.
Maybe what is provided below may help. In particular, it seems that
nouveau is blacklisted but nvidia is not installed anymore...
Thanks for your help,
$ lspci |grep "VGA"
01:00.0 VGA compatible controller: NVIDIA Corporation GF116M [GeForce
GT 560M] (rev a1)
$ cat /proc/cmdline
root=UUID=4aab7630-84b2-4eae-9c5e-804ff8657b7f ro rhgb quiet
$ cat /etc/sysconfig/grub
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_CMDLINE_LINUX="rhgb quiet rd.driver.blacklist=nouveau
$ journalctl -b 0
oct. 31 09:28:49 vouise kernel: video: probe of PNP0A08:00 failed with error -22
oct. 31 09:28:49 vouise kernel: ACPI: video: [Firmware Bug]:
ACPI(MXM3) defines _DOD but not _DOS
oct. 31 09:28:49 vouise kernel: ACPI: video: Video Device [MXM3]
(multi-head: yes rom: no post: no)
oct. 31 09:28:49 vouise kernel: acpi device:1a: registered as cooling_device8
oct. 31 09:28:49 vouise kernel: input: Video Bus as
I need some help.
Firstly: Please forgive the formatting - I'm new to this medium and not sure what the accepted conventions are, the HyperKitty interface is ...very basic. Also please forgive the length, I just don't know how to make it shorter without losing potentially relevant detail. If I've asked this in the wrong place, by all means punt my backside in the direction of the right place.
I seem to have got myself in a bit of a mess and I’ve having trouble finding documentation that I can apply directly to my case . This is my first time on Linux so I’m not familiar with much of the terminology or background of these systems.
I have an internal drive that used to successfully dual boot windows and a LUKS-encrypted F36 installation with BTRFS.
I also had some spare unpartitioned space, which I used to fully install some other linux distros (including another F36 installation) to troubleshoot other minor problems (a tri-boot, so to speak)
**What went wrong**
The new distros installed fine, but I discovered afterwards I could no longer find/boot into my original LUKS F36 installation. In my igornance, I tried deleting clearing the new installation partitions, and now, if I select the Fedora option thru my BIOS boot menu, I just get to a 'grub> ’ prompt.
I’ve tried a few commands there to boot manually but nothing worked and it wouldn’t even decrypt the root partition, worse still, somehow this process accidentally wiped the ORIGINAL LUKS F36 /boot partition too. I have no idea how.
**What I have now**
nvme0n1p1: EFI partition (both win and DF36)
nvme0n1p2: MS Reserved
nvme0n1p5: Original Fedora /boot (accidentally wiped)
nvme0n1p6: LUKS volume
nvme0n1p7: Former ‘third OS’ boot partition (wiped)
nvme0n1p8: Former ‘third OS’ root partition (also wiped)
nvme0n1p4: Win Recovery
**What I am trying to do**
Unbork everything, somehow?
I tried using these instructions in the official Fedora Docs, but they seem to be …wrong? Out of date? They didn’t work, I suspect due to LUKS/BTRFS. [ https://docs.fedoraproject.org/en-US/Fedora/23/html/Multiboot_Guide/commo...]
The I found these...other Fedora Docs? Which seemed more up to date and looked like they had relevant bits, bit still seem directly applicable and didn't work. [https://docs.fedoraproject.org/en-US/quick-docs/bootloading-with-grub2/#r...]
The only success I’ve had is with this guide: https://fedoramagazine.org/os-chroot-101-covering-btrfs-subvolumes/ .
I’ve managed to chroot (a very dumb word) thru a LiveUSB session, with the following commands:
>>cryptsetup luksOpen /dev/nvme0n1p6 fedora_crypt
>>mount /dev/mapper/fedora_crypt /mnt/ -t btrfs -o subvol=root
>>mount /dev/mapper/fedora_crypt /mnt/home -t btrfs -o subvol=home
>>mount /dev/nvme0n1p5 /mnt/boot
>>mount /dev/nvme0n1p1 /mnt/boot/efi
>>mount --bind /dev /mnt/dev
>>mount -t proc /proc /mnt/proc
>>mount -t sysfs /sys /mnt/sys
>>mount -t tmpfs tmpfs /mnt/run
>>mkdir -p /mnt/run/systemd/resolve/
>>nano /mnt/run/systemd/resolve/stub-resolv.conf (enter 'nameserver 22.214.171.124', save)
I can ping google, and browse the original home folder with ls, so it looks like ‘im in’ the original installation via chroot (which is still a dumb word)
What the problems are
From there, I go back to the Fedora Docs and run
>>dnf reinstall grub2-efi grub2-efi-modules shim
That seems to work? Downloads and seems to install without any errors.
The next step though;
>>grub2-mkconfig -o /boot/grub2/grub.cfg
fails with the following:
>> /usr/sbin/grub2-probe: error: failed to get canonical path of ‘/dev/mapper/fedora_crypt’
I have no idea what that means.
On the side, I also sees that despite the grub reinstall, theres no vmlinuz or initramfs kernel files in the reconstructed /boot partition, so I tried running
which results in
>>dracut: Can’t write to /boot/efi/[long-ass id code string]/[kernel version]: Directory /boot/efi/[long-ass id code string]/[kernel version] does not exist or is not accessible.
This is true - that folder isn’t in /boot/efi. But I dont remember ever seeing it there, and just to check I did a fresh test install on another drive and theres nothing like that there either.
So now I’m lost
What I’m looking for
I’m fairly sure the error messages I’m seeing are a result of oversights from my cobbled-together method and gneral lack of understanding. So if anyone knows what I missed and how/why, that’d help …but honestly I still really don’t know what’s going on and suspect I’m probably going to run into another problem just as quick
Really, I’m after some sort of clear, up to date walk-through with entry-level language/detail, on how exactly to rebuild from scratch the EFI/boot partitions for F36 with a LUKS encrypted root, using BTRFS. I know the installation itself is fine and should be recoverable, I just dont know how all these different bits fit togther, and none of the guides out there seem to explain/unify the different bits into a cohesive procedure for the unfamiliar.
Thanks very much.