Re: Failed to find a suitable stage1 device

On Wed, 3 Apr 2024, Michael Hennebry wrote: On Tue, 2 Apr 2024, Samuel Sieb wrote: The efi partition probably needs to be bigger than that, but it also has to be mounted at /boot/efi as indicated. Ah! With custom partitioning, anaconda needs to be explicitly told the EFI partition is the EF

Re: Failed to find a suitable stage1 device

On 4/8/24 08:19, Robert McBroom via users wrote: On 4/3/24 5:45 PM, Stephen Morris wrote: On 4/4/24 00:50, Michael Hennebry wrote: On Tue, 2 Apr 2024, Samuel Sieb wrote: The efi partition probably needs to be bigger than that, but it also has to be mounted at /boot/efi as indicated. Ah!  W

Re: Failed to find a suitable stage1 device

On 4/3/24 5:45 PM, Stephen Morris wrote: On 4/4/24 00:50, Michael Hennebry wrote: On Tue, 2 Apr 2024, Samuel Sieb wrote: The efi partition probably needs to be bigger than that, but it also has to be mounted at /boot/efi as indicated. Ah!  With custom partitioning, anaconda needs to be expl

Re: Failed to find a suitable stage1 device

On 4/4/24 00:50, Michael Hennebry wrote: On Tue, 2 Apr 2024, Samuel Sieb wrote: The efi partition probably needs to be bigger than that, but it also has to be mounted at /boot/efi as indicated. Ah!  With custom partitioning, anaconda needs to be explicitly told the EFI partition is the EFI pa

Re: Failed to find a suitable stage1 device

On Tue, 2 Apr 2024, Samuel Sieb wrote: The efi partition probably needs to be bigger than that, but it also has to be mounted at /boot/efi as indicated. Ah! With custom partitioning, anaconda needs to be explicitly told the EFI partition is the EFI partition. -- Michael henne...@mail.cs.nd

Re: Failed to find a suitable stage1 device

On 4/2/24 22:19, Michael Hennebry wrote: While trying to install from Fedora-Workstation-Live-x86_64-39-1.5.iso , I got the following: Failed to find a suitable stage1 device: EFI System Partition must be mounted on one of /boot/efi.; EFI System Partition cannot be of type None; EFI System Partit

Re: Failed to start jobs message from today's F39 update

> On 13 Mar 2024, at 17:12, Neal Becker wrote: > > I need to see the lines before this, and maybe after. Any ideas? Once I find a time of interest I have use the —since and - before to get a time bounded slice of logs. Barry -- ___ users mailing

Re: Failed to start jobs message from today's F39 update

On 3/13/24 14:42, Joe Zeff wrote: On 03/13/2024 12:33 PM, Mike Wright wrote: I couldn't find any way to pass grep options to -g but grep itself has -A and -B for showing "n" number of lines After or Before the matched context. If you need to pass options to grep, consider piping the output of

Re: Failed to start jobs message from today's F39 update

On 3/13/24 10:10, Neal Becker wrote: On Tue, Mar 12, 2024 at 2:50 PM Joe Zeff > wrote: On 03/12/2024 12:33 PM, Neal Becker wrote: > Failed to start jobs: Failed to enqueue some jobs, see logs for details: > Invalid argument > > Should I worry? 

Re: Failed to start jobs message from today's F39 update

On 03/13/2024 12:33 PM, Mike Wright wrote: I couldn't find any way to pass grep options to -g but grep itself has -A and -B for showing "n" number of lines After or Before the matched context. If you need to pass options to grep, consider piping the output of journalctl through grep instead.

Re: Failed to start jobs message from today's F39 update

On 3/13/24 10:10, Neal Becker wrote: On Tue, Mar 12, 2024 at 2:50 PM Joe Zeff wrote: On 03/12/2024 12:33 PM, Neal Becker wrote: Failed to start jobs: Failed to enqueue some jobs, see logs for details: Invalid argument Should I worry? I don't even know what armadillo is. Did you look at th

Re: Failed to start jobs message from today's F39 update

On Tue, Mar 12, 2024 at 2:50 PM Joe Zeff wrote: > On 03/12/2024 12:33 PM, Neal Becker wrote: > > Failed to start jobs: Failed to enqueue some jobs, see logs for details: > > Invalid argument > > > > Should I worry? I don't even know what armadillo is. > > Did you look at the logs and if not, why

Re: Failed to start jobs message from today's F39 update

On 03/12/2024 12:33 PM, Neal Becker wrote: Failed to start jobs: Failed to enqueue some jobs, see logs for details: Invalid argument Should I worry?  I don't even know what armadillo is. Did you look at the logs and if not, why not? Checking Wikipedia, armadillo is a C++ library for linear

Re: failed to mount /boot/efi

Sorry Jonathan, But, I did not see your message! Anyway, thanks to your help. I understood that I did not boot by using the correct kernel. There was 5 options, and I did not try the right one! The issue is fixed. > To: "Community support for Fedora users" > Subject: Re: faile

Re: failed to mount /boot/efi Help!

On Jul 18, 2021, at 03:24, Patrick Dupre wrote: > > It is now 2 days that I am stuck with this issue. > I search on internet, but I did not find clear solutions which I could trust. > > Here is the fstab > UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39 / ext4 > defaults

Re: failed to mount /boot/efi Help!

Thanks for the feedback, However, I do not understand. Do you mean in the grub configuration /boot/efi/EFI/fedora/grub.cfg I have menuentry 'Fedora 34 (Workstation Edition) (on /dev/sda6)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.12.14-300.

Re: failed to mount /boot/efi Help!

The modules issue is your root= line is pointing to the wrong root device. I am going to guess that all of your boot's have root= that are the same when the f32 ones should be pointing at the f32 root and the f34 ones should be pointing at f34. On the ones that don't boot it will need to be chang

Re: failed to mount /boot/efi Help!

Hello, It is now 2 days that I am stuck with this issue. I search on internet, but I did not find clear solutions which I could trust. Here is the fstab UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39 / ext4 defaults1 1 UUID=B2EF-0CE4 /boot/efi v

Re: failed to mount /boot/efi

If he ran a grub-mkconfig to regenerate the grub I am pretty sure it will make all kernels use the same options. I will mean that all boots have the same root= On Sat, Jul 17, 2021 at 4:29 PM Jonathan Billings wrote: > > On Jul 17, 2021, at 04:29, Patrick Dupre wrote: > > > > Then, > > mount /b

Re: failed to mount /boot/efi

On Jul 17, 2021, at 04:29, Patrick Dupre wrote: > > Then, > mount /boot/efi > mount: /boot/efi: unknown filesystem type 'vfat'. > > I also noted during the load: > FAILED: failed to start load kernel modules You appear to be booting into a kernel that doesn’t have any kernel modules available.

Re: failed to mount /boot/efi

Thanks, nofail let me run the initialization. Then, mount /boot/efi mount: /boot/efi: unknown filesystem type 'vfat'. I also noted during the load: FAILED: failed to start load kernel modules Now journalctl -b -o short-monotonic --no-hostname It is long, I noted (in red): [4.338041] audi

Re: failed to mount /boot/efi

On Fri, Jul 16, 2021 at 1:20 PM Patrick Dupre wrote: > > I collected the maximum information that I could > > Failed Mounting /boot/efi > See "systemctl boot-efi" for details > Dependency failed for local file system > Dependency failed for mark the ... to relabel after reboot > Stopped > You are

Re: failed to mount /boot/efi

I collected the maximum information that I could Failed Mounting /boot/efi See "systemctl boot-efi" for details Dependency failed for local file system Dependency failed for mark the ... to relabel after reboot Stopped You are in emergency mode. After logging in type "journalctl -xb" to view syst

Re: failed to mount /boot/efi

Hello, Running fc32 and fc34 is temporary Actually, it is to be sure that I will not have issues when updating the fc32 to fc34 which really matters. The fc32 is the primary system, but again, as soon that I have been able to run properly the fc42, I will upgrade it. I did the same procedure on

Re: failed to mount /boot/efi

On Thu, Jul 15, 2021 at 12:31 PM Patrick Dupre wrote: > > I have been able to boot on a rescue kernel! > Linux localhost.localdomain 5.6.13-100.fc30.x86_64 #1 SMP Fri May 15 00:36:06 > UTC 2020 x86_64 x86_64 x86_64 GNU/Linux > > bootctl > systemd-boot not installed in ESP. > System: > Firmwa

Re: failed to mount /boot/efi

On Thu, Jul 15, 2021 at 12:01 PM Patrick Dupre wrote: > > Hello, > > On a dual boot machine (one fc32, and one fc34). > after I upgraded the fc32 to fc34, I cannot boot on the new fc34. What does happen? I'm not sure what "cannot boot" means because it doesn't tell me how it's failing. > I get

Re: failed to mount /boot/efi

I have been able to boot on a rescue kernel! Linux localhost.localdomain 5.6.13-100.fc30.x86_64 #1 SMP Fri May 15 00:36:06 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux bootctl systemd-boot not installed in ESP. System: Firmware: n/a (n/a) Secure Boot: disabled Setup Mode: user TPM2 Support:

Re: Failed to start dnf makecache

On 12/31/20 4:52 AM, Ed Greshko wrote: On 31/12/2020 20:41, Neal Becker wrote: I'm not very familiar with restorecon and it's options, what might be the command? sudo restorecon -R /var/lib/rpm Use "-Rv" if you want to see if it makes any changes.

Re: Failed to start dnf makecache

On 31/12/2020 20:41, Neal Becker wrote: On Wed, Dec 30, 2020 at 7:44 PM Jonathan Billings mailto:billi...@negate.org>> wrote: On Dec 30, 2020, at 13:49, Neal Becker mailto:ndbeck...@gmail.com>> wrote: > > Thanks for the suggestion, > > No, rpm -qa runs just fine. Could

Re: Failed to start dnf makecache

On Wed, Dec 30, 2020 at 7:44 PM Jonathan Billings wrote: > On Dec 30, 2020, at 13:49, Neal Becker wrote: > > > > Thanks for the suggestion, > > > > No, rpm -qa runs just fine. > > Could be that the selinux labels are wrong, and cron and the dnf > subprocesses can’t read the files. A ‘restorecon

Re: Failed to start dnf makecache

On Dec 30, 2020, at 13:49, Neal Becker wrote: > > Thanks for the suggestion, > > No, rpm -qa runs just fine. Could be that the selinux labels are wrong, and cron and the dnf subprocesses can’t read the files. A ‘restorecon’ on the directory probably will fix that — Jonathan Billings

Re: Failed to start dnf makecache

Thanks for the suggestion, No, rpm -qa runs just fine. On Wed, Dec 30, 2020 at 11:45 AM Jorge Fábregas wrote: > On 12/30/20 12:18 PM, Neal Becker wrote: > > Dec 30 11:01:29 nbecker8 dnf[1421142]: Error: Error: rpmdb open failed > > Do you get errors when you perform: rpm -qa ??? If so, this c

Re: Failed to start dnf makecache

On 12/30/20 12:18 PM, Neal Becker wrote: > Dec 30 11:01:29 nbecker8 dnf[1421142]: Error: Error: rpmdb open failed Do you get errors when you perform: rpm -qa ??? If so, this could be a corrupted RPM database. If so try Method #1 listed here: https://www.cyberciti.biz/tips/rebuilding-corrupted-

Re: (fedora) Re: Failed to create a dual boot F31 windows 10 on Dell E5540

On 11/4/19 2:41 AM, Jouk Jansen wrote: sam...@sieb.net wrote on 31-OCT-2019 22:45:56.20 On 10/31/19 3:27 AM, Jouk Jansen wrote: I tried to make from my Dell lattitude E5540 running windows 10 a dual boot with F31. Intallation of F31 runned as expected apart form one point: I made a custom part

Re: (fedora) Re: Failed to create a dual boot F31 windows 10 on Dell E5540

sam...@sieb.net wrote on 31-OCT-2019 22:45:56.20 >On 10/31/19 3:27 AM, Jouk Jansen wrote: >> I tried to make from my Dell lattitude E5540 running windows 10 a dual boot >> with F31. Intallation of F31 runned as expected apart form one point: I made >> a custom partion layout of the free space and

Re: Failed to create a dual boot F31 windows 10 on Dell E5540

On 10/31/19 3:27 AM, Jouk Jansen wrote: I tried to make from my Dell lattitude E5540 running windows 10 a dual boot with F31. Intallation of F31 runned as expected apart form one point: I made a custom partion layout of the free space and it compalined that my BIOS needed a small biosboot partiti

Re: Failed to create a dual boot F31 windows 10 on Dell E5540

https://youtu.be/vXMNyiEgD6o Get Outlook for Android From: Jouk Jansen Sent: Thursday, October 31, 2019 11:27:25 AM To: USERS@lists.fedoraproject.org Subject: Failed to create a dual boot F31 windows 10 on Dell E5540 Hi All, I tried to m

Re: Failed to upgrade to F-30

On 7/10/19 8:29 PM, JD wrote: # dnf groupupdate core Last metadata expiration check: 0:16:03 ago on Thu 11 Jul 2019 03:11:51 AM Boise. No match for group package "lsvpd" No match for group package "powerpc-utils" Some of the groups need to be updated to remove packages that don't exist any l

Re: Failed to upgrade to F-30

On 7/10/19 8:27 PM, stan via users wrote: On Wed, 10 Jul 2019 14:14:28 -0600 JD wrote: Justtried to download some things that are on rpmfusion. I got several lines of the type: Public key for x265-libs-3.0-2.fc30.x86_64.rpm is not installed. Failing package is: x265-libs-3.0-2.fc30.x86_64

Re: Failed to upgrade to F-30

On 7/10/19 8:27 PM, stan via users wrote: On Wed, 10 Jul 2019 14:14:28 -0600 JD wrote: Justtried to download some things that are on rpmfusion. I got several lines of the type: Public key for x265-libs-3.0-2.fc30.x86_64.rpm is not installed. Failing package is: x265-libs-3.0-2.fc30.x86_64

Re: Failed to upgrade to F-30

On Wed, 10 Jul 2019 14:14:28 -0600 JD wrote: > Justtried to download some things that are on rpmfusion. I got > several lines of the type: > > Public key for x265-libs-3.0-2.fc30.x86_64.rpm is not installed. > Failing package is: x265-libs-3.0-2.fc30.x86_64 >  GPG Keys are configured as: > fi

Re: Failed to upgrade to F-30

On 7/9/19 5:38 PM, sixpack13 wrote: ... file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-30 ... If they are downloaded, where are they located?? see above ! P.S. rpmfusion is ONLINE again ! try sudo dnf upgrade rpmfusion-\* Justtried to download some things that are on rpmfus

Re: Failed to upgrade to F-30

On 7/10/19 12:03 PM, rwar...@gmx.de wrote: On 10.07.19 19:23, JD wrote: On 7/9/19 5:38 PM, sixpack13 wrote: ... file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-30 ... If they are downloaded, where are they located?? see above ! P.S. rpmfusion is ONLINE again ! try sudo dnf

Re: Failed to upgrade to F-30

> ... > file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-30 ... > If they are downloaded, where are they located?? > see above ! P.S. rpmfusion is ONLINE again ! try sudo dnf upgrade rpmfusion-\* ___ users mailing list -- users@lists.fed

Re: Failed to upgrade to F-30

On 7/9/19 4:01 PM, sixpack13 wrote: - it seems rpmfusion is currently offline ! and I upgraded with command: sudo dnf system-upgrade download --refresh --releasever=30 --setopt='module_platform_id=platform:f30' --allowerasing or without " ' " after "setopt=" and "f30" Just retried. It sti

Re: Failed to upgrade to F-30

... and this was a draft... ...first vanished and re-appeared ... today IS NOT my day !!! :-( - a edit function for this forum software could be a win to lower (or prevent ?) a lot of "not-my-day days" ! - ___ users mailing list -- users@lists.fedorapr

Re: Failed to upgrade to F-30

... Urggghhh, cutted my reply, here the rest: workaround = 1. sudo dnf list installed | grep rpmfusion | cut -d " " -f1 > fusion_packs 2. sudo dnf remove rpmfusion-\* OR 2b. disable all rpmfusion repo's (enabled=0) under /etc/yum.repos.d 3. sudo dnf system-upgrade download --refresh --rel

Re: Failed to upgrade to F-30

it seems rpmfusion is currently offline workaround: - sudo dnf list installed | grep rpmfusion | cut -d " " -f1 > fusion_packs - sudo dnf remove rpmfusion\* OR simply disable (enabled=0) all rpmfusion repo's in /etc/yum.repos.d/ - sudo dnf system-upgrade download --refresh --releasever=30 --se

Re: Failed to upgrade to F-30

- it seems rpmfusion is currently offline ! and I upgraded with command: sudo dnf system-upgrade download --refresh --releasever=30 --setopt='module_platform_id=platform:f30' --allowerasing or without " ' " after "setopt=" and "f30" ___ users mailing

Re: Failed to switch root

Hello, In conclusion "temporally". 1) I could not boot on the first OS installed because linux instead of linuxefi and initrd instead of initrdefi were used in the menuentry If seems that moving from fedora 28 to fedora 30, a) the grub.cfg generated does not keep track b) acually, the new genera

Re: Failed to switch root

when I mount the FS, I have cat /mnt/linux/etc/fedora-release Fedora release 30 (Thirty) This seems to indicate me that the FS which is mounted is wrong. But it is the right one! This is what is before: [3.971992] localhost systemd[1]: Stopped Create list of required static device nodes fo

Re: Failed to synchronize cache for repo 'fedora-modular' (F29)

On 5/30/19 2:42 PM, Ranjan Maitra wrote: sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2019-28516f8c38 ... Failed to synchronize cache for repo 'fedora-modular' Error: Failed to synchronize cache for repo 'fedora-modular' Any suggestions how to get around this bug? I even tried

Re: Failed to start Load Kernel Modules.

I have this exact same problem on FC29. All you've said is true regarding the build and install of the kernel modules for the rpmfusion-free-updates repo. The modules get rebuilt by akmod just fine. I have dnf provides /usr/lib/modules-load.d/VirtualBox.conf VirtualBox-server-5.2.22-1.fc29.x86

Re: Failed to open device file /dev/tpm0: Permission denied

On Sun, 13 Jan 2019 at 13:23, Dave Mitchell wrote: > Fedora 29. > > journalctl -f shows the following lines appearing in the log every five > seconds. Can anyone tell me whether this is important, and if so how to > fix it, and if not, how to stop this noise filling the journal up? I often fin

Re: Failed to open device file /dev/tpm0: Permission denied

On 01/13/2019 12:52 PM, Dave Mitchell wrote: On Sun, Jan 13, 2019 at 11:36:24AM -0800, Samuel Sieb wrote: On 1/13/19 9:22 AM, Dave Mitchell wrote: journalctl -f shows the following lines appearing in the log every five seconds. Can anyone tell me whether this is important, and if so how to fix

Re: Failed to open device file /dev/tpm0: Permission denied

On 1/13/19 11:52 AM, Dave Mitchell wrote: On Sun, Jan 13, 2019 at 11:36:24AM -0800, Samuel Sieb wrote: On 1/13/19 9:22 AM, Dave Mitchell wrote: journalctl -f shows the following lines appearing in the log every five seconds. Can anyone tell me whether this is important, and if so how to fix it

Re: Failed to open device file /dev/tpm0: Permission denied

On Sun, Jan 13, 2019 at 11:36:24AM -0800, Samuel Sieb wrote: > On 1/13/19 9:22 AM, Dave Mitchell wrote: > > journalctl -f shows the following lines appearing in the log every five > > seconds. Can anyone tell me whether this is important, and if so how to > > fix it, and if not, how to stop this n

Re: Failed to open device file /dev/tpm0: Permission denied

On 1/13/19 9:22 AM, Dave Mitchell wrote: journalctl -f shows the following lines appearing in the log every five seconds. Can anyone tell me whether this is important, and if so how to fix it, and if not, how to stop this noise filling the journal up? That's the tpm2-abrmd package. I don't kn

Re: Failed to start Load Kernel Modules.

On 08/05/18 14:08, Samuel Sieb wrote: > On 08/04/2018 10:37 PM, Ed Greshko wrote: >> FWIW, on the next kernel update you can temporarily remove the  >> bbswitch.conf  file >> before reboot and see if the error still occurs. > > I expect that you would have to remove it before you do the kernel upd

Re: Failed to start Load Kernel Modules.

On 08/05/18 11:22, Sudhir Khanger wrote: > FYI I have dropped a message for the Bumblebee packager. Let's see if he has > some > thoughts. > > https://github.com/Bumblebee-Project/Bumblebee/issues/153#issuecomment-410492604 While I don't use their packages I did poke around https://linux.itecs.n

Re: Failed to start Load Kernel Modules.

On 08/04/2018 10:37 PM, Ed Greshko wrote: FWIW, on the next kernel update you can temporarily remove the  bbswitch.conf  file before reboot and see if the error still occurs. I expect that you would have to remove it before you do the kernel update. I think dracut copies that file into the i

Re: Failed to start Load Kernel Modules.

On 08/05/18 11:22, Sudhir Khanger wrote: > Is that the case with both Oracle and RPMFusion's VirtualBox or of only > former? I don't normally use the RPMFusion packages.  I don't recall why that is.  Must have had a bad experience at some point.  So, today I did install it on a laptop and found.

Re: Failed to start Load Kernel Modules.

On Sun, Aug 5, 2018 at 3:46 AM Ed Greshko wrote: > On 08/05/18 01:12, Sudhir Khanger wrote: > > Like I mentioned earlier that systemd-modules-load.service service fails > and starts > > working after I create a new initramfs. You were unwilling to accept > what I > > experienced on my system irre

Re: Failed to start Load Kernel Modules.

On 08/05/18 01:12, Sudhir Khanger wrote: > Like I mentioned earlier that systemd-modules-load.service service fails and > starts > working after I create a new initramfs. You were unwilling to accept what I > experienced on my system irrespective of the cause I shot a video of it which > you > ca

Re: Failed to start Load Kernel Modules.

On Sat, Aug 4, 2018 at 11:09 PM Samuel Sieb wrote: > Did you check if there was anything in /etc/modules-load.d/? > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora

Re: Failed to start Load Kernel Modules.

Did you check if there was anything in /etc/modules-load.d/? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html Li

Re: Failed to start Load Kernel Modules.

On Tue, Jul 24, 2018 at 10:25 AM Ed Greshko wrote: > On 07/24/18 12:08, Sudhir Khanger wrote: > > systemd-modules-load.service fails at boot and then it probably builds > the modules. > > After the system boots, systemd-modules-load.service has active status > and not > > failed. But the only way

Re: Failed to start Load Kernel Modules.

On 07/24/18 12:08, Sudhir Khanger wrote: > systemd-modules-load.service fails at boot and then it probably builds the > modules. > After the system boots, systemd-modules-load.service has active status and not > failed. But the only way to get rid of Failed to start Load Kernel > Modules**is by >

Re: Failed to start Load Kernel Modules.

On Tue, Jul 24, 2018 at 3:49 AM Ed Greshko wrote: > On 07/23/18 17:04, Sudhir Khanger wrote: > > Okay update time. Irrespective of where I install VirtualBox from if a > new kernel > > is installed then I have to manually create a new initramfs > > otherwise systemd-modules-load.service fails at

Re: Failed to start Load Kernel Modules.

On Mon, Jul 23, 2018 at 10:58 PM Rick Stevens wrote: > On 07/23/2018 10:08 AM, Samuel Sieb wrote: > > On 07/23/2018 02:04 AM, Sudhir Khanger wrote: > >> Okay update time. Irrespective of where I install VirtualBox from if a > >> new kernel is installed then I have to manually create a new initram

Re: Failed to start Load Kernel Modules.

On 07/23/18 17:04, Sudhir Khanger wrote: > Okay update time. Irrespective of where I install VirtualBox from if a new > kernel > is installed then I have to manually create a new initramfs > otherwise systemd-modules-load.service fails at the boot. > When it comes to VirtualBox from Oracle I find

Re: Failed to start Load Kernel Modules.

On 07/23/2018 10:08 AM, Samuel Sieb wrote: > On 07/23/2018 02:04 AM, Sudhir Khanger wrote: >> Okay update time. Irrespective of where I install VirtualBox from if a >> new kernel is installed then I have to manually create a new initramfs >> otherwise systemd-modules-load.service fails at the boot.

Re: Failed to start Load Kernel Modules.

On 07/23/2018 02:04 AM, Sudhir Khanger wrote: Okay update time. Irrespective of where I install VirtualBox from if a new kernel is installed then I have to manually create a new initramfs otherwise systemd-modules-load.service fails at the boot. Yes, the self-compiled modules aren't created at

Re: Failed to start Load Kernel Modules.

On Mon, Jun 18, 2018 at 5:58 PM Ed Greshko wrote: > On 06/18/18 19:19, Sudhir Khanger wrote: > > I get *Failed to start Load Kernel Modules* during the boot. > > > > Everytime Kernel is updated VirtualBox modules fail I have to reboot > into the new > > Kernel, run the following commands and then

Re: Failed to start Load Kernel Modules.

I get the same message now that is "Failed to start Load Kernel Modules" but there isn't anything in the logs. https://gist.github.com/sudhirkhanger/bcd766104e2268cb73a8d80c0152a932 The only service which fails is dbxtool.service journalctl -b | grep -ie "Failed to start Load Kernel Modules" T

Re: Failed to start Load Kernel Modules.

On Mon, Jun 18, 2018 at 5:58 PM Ed Greshko wrote: > On 06/18/18 19:19, Sudhir Khanger wrote: > > I get *Failed to start Load Kernel Modules* during the boot. > > > > Everytime Kernel is updated VirtualBox modules fail I have to reboot > into the new > > Kernel, run the following commands and then

Re: Failed to start Load Kernel Modules.

On 06/18/18 19:19, Sudhir Khanger wrote: > I get *Failed to start Load Kernel Modules* during the boot. > > Everytime Kernel is updated VirtualBox modules fail I have to reboot into the > new > Kernel, run the following commands and then it starts working. > > $ sudo akmods --force > $ sudo dracut

Re: Failed to start IPv4 firewall with iptables

On Thu, 4 Feb 2016 15:24:46 -0500 GUNA wrote: > Hello, > > I have updated Fedora core 16 Kernel from 3.4.2 to 4.4.0. Once the > system is rebooted with new kernel 4.4.0, the iptables loaded but not > started. That version of Fedora is over 3 years obsolete. In those days, the firewall service

Re: Failed to start Switch Root

Hi Patrick The log tells you how to remedy: "os-release file is missing". I asssume that this file is meant: [me@thunder ~]$ cat /etc/fedora-release Fedora release 22 (Twenty Two) [me@thunder ~]$ ls -l /etc/fedora-release -rw-r--r-- 1 root root 31 May 19 16:27 /etc/fedora-release [me@thunder ~]

Re: Failed to find cpu0 device node

On 08/29/2015 07:04 PM, Frederic Muller wrote: > On 08/29/2015 06:40 PM, Frederic Muller wrote: >> On 08/29/2015 04:33 PM, Michael D. Setzer II wrote: Try adding nosmp to the kernel boot option?? I've seen the same thing with my phenomii quad core system when booting with a 4.1x or

Re: Failed to find cpu0 device node

On 08/29/2015 06:40 PM, Frederic Muller wrote: > On 08/29/2015 04:33 PM, Michael D. Setzer II wrote: >> > Try adding nosmp to the kernel boot option?? >> > I've seen the same thing with my phenomii quad core system when booting >> > with a 4.1x or 4.2x kernel? Same kernels work fine on a quad core

Re: Failed to find cpu0 device node

On 08/29/2015 04:33 PM, Michael D. Setzer II wrote: > Try adding nosmp to the kernel boot option?? > I've seen the same thing with my phenomii quad core system when booting > with a 4.1x or 4.2x kernel? Same kernels work fine on a quad core i7, so not > sure if it is a phenomii or kernel issue wi

Re: Failed to find cpu0 device node

Try adding nosmp to the kernel boot option?? I've seen the same thing with my phenomii quad core system when booting with a 4.1x or 4.2x kernel? Same kernels work fine on a quad core i7, so not sure if it is a phenomii or kernel issue with some bios. Same kernels boot fine if I use nosmp option?

Re: Failed to find cpu0 device node

On 08/29/2015 02:13 PM, Ed Greshko wrote: > On 08/29/15 14:05, Frederic Muller wrote: >> Yes I did a Google search before but didn't find the same exact issue >> (as I am stuck looking at the error message). I'll make a 32 bit USB key >> but then again, should I reinstall and update? I fear it'll t

Re: Failed to find cpu0 device node

On 08/29/15 14:05, Frederic Muller wrote: > Yes I did a Google search before but didn't find the same exact issue > (as I am stuck looking at the error message). I'll make a 32 bit USB key > but then again, should I reinstall and update? I fear it'll take me to > the same problem. Should I downgrad

Re: Failed to find cpu0 device node

On 08/29/2015 12:54 PM, Ed Greshko wrote: > On 08/29/15 11:44, Frederic Muller wrote: >> ince yesterday (not sure when was my last restart, but at most 3-4 days >> before) my T60 gives me a "Failed to find cpu0 device node" right at >> boot and stay there. >> >> I have tried to boot with previous k

Re: Failed to find cpu0 device node

On 08/29/15 11:44, Frederic Muller wrote: > ince yesterday (not sure when was my last restart, but at most 3-4 days > before) my T60 gives me a "Failed to find cpu0 device node" right at > boot and stay there. > > I have tried to boot with previous kernel (4.1.5, 4.1.2 I think) but I > get the same

Re: failed to ..

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/31/2013 12:20 PM, Chris Murphy wrote: > > On Dec 31, 2013, at 8:57 AM, Daniel J Walsh wrote: > >> THere was a bug in libselinux which is now fixed, that was causing the >> problem. > > Right, but I thought that the bug caused the setting in

Re: failed to ..

On Dec 31, 2013, at 8:57 AM, Daniel J Walsh wrote: > THere was a bug in libselinux which is now fixed, that was causing the > problem. Right, but I thought that the bug caused the setting in /etc/selinux/config being ignored, while selinux=0 and enforcing=0 still worked? Chris Murphy -- u

Re: failed to ..

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/30/2013 11:11 AM, Chris Murphy wrote: > > On Dec 29, 2013, at 11:37 PM, Ralf Corsepius wrote: > >> On 12/30/2013 07:01 AM, Chris Murphy wrote: >>> >>> On Dec 28, 2013, at 8:15 PM, Patrick Dupre wrote: >>> Hello, I tried to s

Re: failed to ..

On Dec 29, 2013, at 11:37 PM, Ralf Corsepius wrote: > On 12/30/2013 07:01 AM, Chris Murphy wrote: >> >> On Dec 28, 2013, at 8:15 PM, Patrick Dupre wrote: >> >>> Hello, >>> >>> I tried to set relabel by using system-config-selinux, >>> but nothing happens I have to keep selinux=0 to be able t

Re: failed to ..

Allegedly, on or about 30 December 2013, Ralf Corsepius sent: > With all due respect, disabling SELinux *must not cause problems*. > > If it does, somebody is critically broken and needs to be fixed, > ASAP. Usually, yes. But you cannot expect SELinux relabelling to be done when you've disabled

Re: failed to ..

Thank for the recommendations. Do not worry, I just set enforcing=0 1 time to get the relabelling Then every thing is perfect. > > On 12/30/2013 07:01 AM, Chris Murphy wrote: > > > > On Dec 28, 2013, at 8:15 PM, Patrick Dupre wrote: > > > >> Hello, > >> > >> I tried to set relabel by using syst

Re: failed to ..

On 12/30/2013 07:01 AM, Chris Murphy wrote: On Dec 28, 2013, at 8:15 PM, Patrick Dupre wrote: Hello, I tried to set relabel by using system-config-selinux, but nothing happens I have to keep selinux=0 to be able to boot! Try autorelabel=1, and in the future if you have selinux problems you

Re: failed to ..

On Dec 28, 2013, at 8:15 PM, Patrick Dupre wrote: > Hello, > > I tried to set relabel by using system-config-selinux, > but nothing happens I have to keep selinux=0 to be able to boot! Try autorelabel=1, and in the future if you have selinux problems you don't want to troubeleshoot use enforc

Re: failed to ..

Hello, I tried to set relabel by using system-config-selinux, but nothing happens I have to keep selinux=0 to be able to boot! > > On Sat, 28 Dec 2013 16:28:33 +0100, Patrick Dupre wrote: > > > (I did not have a rsync command on the gparted live distribution that I > > have) > > Does its "cp"

Re: failed to ..

Thank again, Now, What should I do to not have to set anymore selinux=0? > Subject: Re: failed to .. > > On Sat, 28 Dec 2013 16:28:33 +0100, Patrick Dupre wrote: > > > (I did not have a rsync command on the gparted live distribution that I > > have) > > Does

Re: failed to ..

Thank you very much. It was the point. > Subject: Re: failed to .. > > On Sat, 28 Dec 2013 16:28:33 +0100, Patrick Dupre wrote: > > > (I did not have a rsync command on the gparted live distribution that I > > have) > > Does its "cp" command copy

Re: failed to ..

On Sat, 28 Dec 2013 16:28:33 +0100, Patrick Dupre wrote: > (I did not have a rsync command on the gparted live distribution that I have) Does its "cp" command copy SELinux file contexts? > And I get always the same behavior: > failed to start ... >   create static device modes in /dev >  

Re: failed to ..

On Dec 28, 2013, at 2:42 PM, Patrick Dupre wrote: > Hello Chris, > > More information. This what I get until the first FAILED > > kvm: disabled by bios Seems like this BIOS always disables virtualization so unless your other root doesn't have this message I don't know why it's relevant. > s

  1   2   >