The speakers that are not working are the built in laptop speakers
On 9/17/24 9:14 PM, ToddAndMargo via users wrote:
On 9/17/24 17:22, Tom Horsley wrote:
On Tue, 17 Sep 2024 18:03:32 -0600
Sbob wrote:
Can anyone help me debug this?
Check the sound control panel and see if there are multipl
On 9/17/24 17:22, Tom Horsley wrote:
On Tue, 17 Sep 2024 18:03:32 -0600
Sbob wrote:
Can anyone help me debug this?
Check the sound control panel and see if there are multiple sound devices
and pick a different default (if there is one). If there aren't multiple
devices then I'm no help :-).
On Tue, 17 Sep 2024 18:03:32 -0600
Sbob wrote:
> Can anyone help me debug this?
Check the sound control panel and see if there are multiple sound devices
and pick a different default (if there is one). If there aren't multiple
devices then I'm no help :-).
--
On 9/17/24 17:03, Sbob wrote:
All;
I have just installed a fresh install of Fedora 40 - KDE spin on a new
Lenovo Legion 9
I have no sound, if I open elise and play music, or go to say a you tube
video I get no sound.
If I click on the speaker icon in my taskbar (at the right side of the
All;
I have just installed a fresh install of Fedora 40 - KDE spin on a new
Lenovo Legion 9
I have no sound, if I open elise and play music, or go to say a you tube
video I get no sound.
If I click on the speaker icon in my taskbar (at the right side of the
default panel) I can see the
On 8/27/24 4:38 AM, Ger van Dijck wrote:
Hi All,
I had a total crash on my PC and had to restore Windows 10
Professionel by
using Veeam Recorvery. This was succesfull , but the bootloader was gone
and Fedora 40 also .
I did install a 1 Terra SSD drive .
I burned a netinstall DVD Fedora 40
On Tue, Aug 27, 2024 at 7:41 AM Ger van Dijck
wrote:
> Hi All,
>
> I had a total crash on my PC and had to restore Windows 10 Professionel by
> using Veeam Recorvery. This was succesfull , but the bootloader was gone
> and Fedora 40 also .
>
> I did install a 1 Terra SSD d
Hi All,
I had a total crash on my PC and had to restore Windows 10 Professionel by
using Veeam Recorvery. This was succesfull , but the bootloader was gone
and Fedora 40 also .
I did install a 1 Terra SSD drive .
I burned a netinstall DVD Fedora 40 and tried to install Fedora 40 :
Normally
Hi,
> This is on a PowerEdge R720, booting from a virtual DVD ISO.
>
>
> I used a USB stick with Fedora live image on it to install on a R720,
> likely it was f37 or f38 as after the first install I did dnf
> system-upgrade.
>
> I think booting an ISO was tried and fail
When trying to start the NFS-server on a just installed F40 system it stops
immediately. What is wrong? Below I give the systemctl status and the relevant
part of the journalctl.
root@s185:~# systemctl status nfs-server
● nfs-server.service - NFS server and services
Loaded: loaded (/usr/lib
> On 21 Jul 2024, at 12:40, Alex wrote:
>
> This is on a PowerEdge R720, booting from a virtual DVD ISO.
I used a USB stick with Fedora live image on it to install on a R720,
likely it was f37 or f38 as after the first install I did dnf system-upgrade.
I think booting an ISO was
Hi,
I have received the following error very early on in the install of
fedora40 server:
Failed to fork off sandboxing environment for executing generators:
Protocol error
[!!] Failed to start up manager.
Exiting PID 1...
This is on a PowerEdge R720, booting from a virtual DVD ISO. This
> > However, to install it, I'm obliged to remove lsb_release (see below).
> > Is it safe?
>
> Well, it's just a ".noarch" package containing a single shell script,
> and it isn't installed by default, and specific to your installation
> nothing
On Mon, 15 Jul 2024 17:53:04 +0200, Frédéric wrote:
> However, to install it, I'm obliged to remove lsb_release (see below).
> Is it safe?
Well, it's just a ".noarch" package containing a single shell script,
and it isn't installed by default, and specific to your
Hi,
I'm trying to reinstall my Epson Stylus SX525WD printer after a brand
new install of Fedora 40. I normally install a rpm package found on
http://download.ebz.epson.net/. However the driver that worked in the
past giving all features is called "Printer Driver ESC/P Driver (full
fea
On 5/7/24 02:29, François Patte wrote:
Le 2024-07-04 18:18, Mike Wright a écrit :
On 7/4/24 09:09, François Patte wrote:
Should I understand that if you have a windows installation on a
disk with some (big) space left, you cannot install f40 as a dual
boot system? (because anaconda is unable
François Patte composed on 2024-07-05 18:14 (UTC+0200):
> how can I boot the installer as a BIOS boot?
First ensure that the BIOS has CSM (legacy boot, by whatever name used) enabled.
After exiting setup, hit the BBS hotkey during POST, which will present a boot
device selection menu. Choose the
On Jul 5, 2024, at 12:15, François Patte
wrote:
> Yes! But how can I boot the installer as a BIOS boot?
You would need to either turn off UEFI boot in the BIOS or choose a special
boot option upon boot. It is entirely up to your hardware - Fedora can’t do
anything about it once it’s booted the
Le 2024-07-05 13:28, Jonathan Billings a écrit :
On Jul 5, 2024, at 04:00, François Patte
wrote:
Le 2024-07-05 03:03, Tide Ka a écrit :
Should I understand that if you have a windows installation on a
disk with some (big) space left, you cannot install f40 as a dual
boot system? (because
On Jul 5, 2024, at 04:00, François Patte
wrote:
>
> Le 2024-07-05 03:03, Tide Ka a écrit :
>>> Should I understand that if you have a windows installation on a disk with
>>> some (big) space left, you cannot install f40 as a dual boot system?
>>> (because
On Thu, 2024-07-04 at 18:09 +0200, François Patte wrote:
> Should I understand that if you have a windows installation on a disk
> with some (big) space left, you cannot install f40 as a dual boot
> system? (because anaconda is unable to ignore the windows partition)
It's been age
Le 2024-07-05 03:03, Tide Ka a écrit :
Should I understand that if you have a windows installation on a disk
with some (big) space left, you cannot install f40 as a dual boot
system? (because anaconda is unable to ignore the windows partition)
That (dual-boot) is based upon anaconda&#
Should I understand that if you have a windows installation on a disk
with some (big) space left, you cannot install f40 as a dual boot
system? (because anaconda is unable to ignore the windows partition)
That (dual-boot) is based upon anaconda's behaviour. Basically it is
about te
On 7/4/24 16:30, Mike Wright wrote:
--> EFI EXPLAINED <--
I just found this collection of pages about EFI. If you learn all of
this you will know more about EFI than all but a miniscule percentage of
humanity.
https://www.rodsbooks.com/efi-bootloaders/index.html
--
___
On 7/4/24 11:37, Tim via users wrote:
If you install other OSs, they should do something similar. You'd have
something like:
... EFI/debian
... EFI/fedora
Which should keep all the OSs separate from each other.
If you wanted dual booting different versions of Fedora, withou
On 7/4/24 2:25 PM, Tim via users wrote:
And for what it's worth, on the newly installed Fedora 40 (after a
fight and half), it's not mounted on /boot/efi, but inside it (like my
CentOS example did).
i.e. /boot/efi/EFI/fedora
That's a clean install, so it does that itself.
tc.
>
> Not much you can do about that.
I know, I'd already covered that, but I was just pointing out it was
less than straight-forward.
And for what it's worth, on the newly installed Fedora 40 (after a
fight and half), it's not mounted on /boot/efi, but inside it (like my
On 7/4/24 11:37 AM, Tim via users wrote:
EFI is its own partition, that will be mounted inside /boot when Linux
boots. I'm not actually sure why that decision was made, I don't see
why we couldn't have just had /EFI. I suppose someone wanted to hide
all the boot things in /boot. On this PC, it
ot/efi/EFI/centos.
Deeper inside EFI are directories for each bootable OS. Generally,
there's a simplistic naming scheme "fedora" for any/all fedora
installation files to go inside it.
If you install other OSs, they should do something similar. You'd have
something like:
On 7/4/24 09:29, François Patte wrote:
Le 2024-07-04 18:18, Mike Wright a écrit :
On 7/4/24 09:09, François Patte wrote:
Should I understand that if you have a windows installation on a disk
with some (big) space left, you cannot install f40 as a dual boot
system? (because anaconda is unable
Le 2024-07-04 18:18, Mike Wright a écrit :
On 7/4/24 09:09, François Patte wrote:
Should I understand that if you have a windows installation on a disk
with some (big) space left, you cannot install f40 as a dual boot
system? (because anaconda is unable to ignore the windows partition)
I
On 7/4/24 09:09, François Patte wrote:
Should I understand that if you have a windows installation on a disk
with some (big) space left, you cannot install f40 as a dual boot
system? (because anaconda is unable to ignore the windows partition)
I *think* that there can be only one /boot/efi
a windows installation on a disk
with some (big) space left, you cannot install f40 as a dual boot
system? (because anaconda is unable to ignore the windows partition)
--
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pèr
er LVM or software RAID etc.
And also, if your problem is to use /efi or /boot or /boot/efi, it will
also require configurations, which probably require a completely manual
install.
https://wiki.archlinux.org/title/EFI_system_partition#Typical_mount_points
may explain better.
--
Tide Ka
En
Bonjour,
I am stuck trying to installe f40 on my computer.
I have 4 disks, 2 SSD and 2 HDD.
On the SSDs run a fedora 36 install *which I want to keep untill the f40
will be installed and configured.*
On the SSDs 2 partitions:
1) sda1 sdb1, 1Gb RAID1 array as /boot for the f36 install
2
> Am 03.07.2024 um 18:34 schrieb François Patte
> :
>
> Bonjour,
>
> Where can I find some details on the installation of fedora 40, I would like
> to have raid1 arrays and lvm.
For Fedora server you may have a look at:
https://pboy.fedorapeople.org/InstGuideF33-Hetzner-en.pdf
Not really a
Bonjour,
Where can I find some details on the installation of fedora 40, I would
like to have raid1 arrays and lvm.
Thank you.
--
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél.
y click on the
existing backup subvolume and then assign it a mountpoint /backup to have the
installer do this for you and add it to fstab. Or you can do it post-install
yourself.
Note that unless you explicitly delete the current (broken?) root in the
intstaller, it will live on. And you also
On Tue, 2024-06-04 at 23:36 +0930, Tim via users wrote:
> You're supposed to reply to the bits you're responding to, and cut
> out
> the rest that isn't actually needed. Unfortunately people are
> forgetting this and trying to get an entire thread inside each and
> every message.
>
> If anyone ha
On Mon, 2024-06-03 at 15:59 +0200, Patrick Dupre via users wrote:
> With your message we lost the thread.
The thread is there. You're not supposed to keep quoting every prior
reply when you respond to messages. Messages become huge and
unreadable messes.
You're supposed to reply to the bits you
sing a separate partition for /home
with
ext[2|3|4] and this was conveniently not touched if I did a custom
install to upgrade - I want to do something similar for this backup
subvolume.
I would never consider a btrfs subvolume a suitable location for a
backup. The btrfs
snapshots provide a way to
tition for /home with
> ext[2|3|4] and this was conveniently not touched if I did a custom
> install to upgrade - I want to do something similar for this backup
> subvolume.
>
I would never consider a btrfs subvolume a suitable location for a backup.
The btrfs
snapshots provide a way to go ba
,224
24% /
/dev/nvme0n1p3btrfs 1,951,850,496 464,659,184 1,486,438,224
24% /backup
For decades I have just been using a separate partition for /home with
ext[2|3|4] and this was conveniently not touched if I did a custom
install to upgrade - I want to do something similar for t
Hello,
With your message we lost the thread.
The Fedora 38 is installed on sda4 with /boot/efi on sda3 (fat16 EFI System
Partition)
The fedora 40 is installed on sdc3 I only have /boot installed on sdc2
I guess that I could run something like
grub-install /dev/sda --target=x86_64-efi --efi
On Mon, Jun 3, 2024 at 3:11 AM Patrick Dupre via users
wrote:
> I updated a fedora 38 installation to 40 (on sdc3) as I used to do.
> But this installation is now not visible from the grub bot menu.
> I run grub2-mkconfig -o /boot/grub2/grub.cfg
> again, and again from both installation (40 and 38
On Mon, 2024-06-03 at 13:53 +0200, Patrick Dupre via users wrote:
> I wish to add that efibootmgr does not list the sdc3 installation.
By default, it'll only show the boot options that installations have
entered into it. If your install didn't do that, you can add entries,
yourself.
I wish to add that
efibootmgr
does not list the sdc3 installation.
> Subject: Re: grub2-install
>
> Thank for the feedback,
>
> Thus, I am going to summarize the situation.
> I updated a fedora 38 installation to 40 (on sdc3) as I used to do.
> But this installation is now
Thank for the feedback,
Thus, I am going to summarize the situation.
I updated a fedora 38 installation to 40 (on sdc3) as I used to do.
But this installation is now not visible from the grub bot menu.
I run grub2-mkconfig -o /boot/grub2/grub.cfg
again, and again from both installation (40 and 38
On 2/6/24 23:00, Patrick Dupre via users wrote:
Hello,
There is bug reported about grub2-install
2240994
for a while
but no solution are proposed.
grub2-install: error: This utility should not be used for EFI platforms because
it does not support UEFI Secure Boot. If you really wish to
On 6/2/24 6:00 AM, Patrick Dupre via users wrote:
There is bug reported about grub2-install
2240994
for a while
but no solution are proposed.
grub2-install: error: This utility should not be used for EFI platforms because
it does not support UEFI Secure Boot. If you really wish to proceed
Hello,
There is bug reported about grub2-install
2240994
for a while
but no solution are proposed.
grub2-install: error: This utility should not be used for EFI platforms because
it does not support UEFI Secure Boot. If you really wish to proceed, invoke the
--force option.
Make sure Secure
a special property of the hardware you are using. I suppose,
> the disk are used and already had some data on it. Ist there something
> special? E.g. had they different partitioning schemes?
Nope, they were all just type fd (Linux RAID), created by anaconda.
> - Both times I tried t
> Am 01.06.2024 um 20:29 schrieb Jonathan Billings :
>
> If you can just point at an ISO, use the Everything boot.iso
>
> https://dl.fedoraproject.org/pub/fedora/linux/releases/40/Everything/x86_64/os/images/
Why do you think this is advantageous?
In general, this is bad advice for an install
is it specific
to a special property of the hardware you are using. I suppose, the disk are
used and already had some data on it. Ist there something special? E.g. had
they different partitioning schemes?
> - Both times I tried to install, the systemd-resolved daemon wouldn't resolve
&
/boot/efi is small and thus raid 1 made the most sense. It let me
> select 3 disks and the install (under VirtualBox) is going on right now.
> Note that raid 1 is not limited to just two disks/partitions, it can make
> multi disk mirror sets. Most people don't really think about tha
On Sat, Jun 1, 2024 at 12:45 PM Alex wrote:
> I don't see anything else on any of the other consoles that would indicate a
> problem.
Perhaps the installer's log files will be more revealing:
https://docs.fedoraproject.org/en-US/quick-docs/anaconda-logging/
> During
of graphical access at all, unless you use IPMI,
> > which brings you back to square one anyway. So this is a lot more
> > work unless you plan to install a lot of Fedora servers, in which case
> > you also want to use kickstart and not a graphical install. ;-)
>
> If you can speci
help. A few general questions:
>>
>> - Can (should?) I put /boot/efi on RAID5? It lets me choose the option,
>> but then complains and wants it on RAID1. Does it set up RAID1 with a
>> failover?
>
> I was thinking about this thread and just started a test. My thinking w
the option,
> but then complains and wants it on RAID1. Does it set up RAID1 with a
> failover?
I was thinking about this thread and just started a test. My thinking was that
/boot/efi is small and thus raid 1 made the most sense. It let me select 3
disks and the install (under VirtualBox
past, but maybe it's changed?
I'm concerned the IPMI session will time out, as it's happened before :-(
I don't see anything else on any of the other consoles that would indicate
a problem.
During install, there were repeated messages like:
kernel: EDID has corrupt header
bu
isk
layout was ignored.
- Both times I tried to install, the systemd-resolved daemon wouldn't
resolve hostnames, as the "software selection" menu could not identify a
local mirror. I had to remove the /etc/resolv.conf symlink and create it
using 8.8.8.8.
Thanks,
Alex
--
/releases/40/Everything/x86_64/os/images/pxeboot/
… and boot using them, and add the kernel arguments described here:
https://anaconda-installer.readthedocs.io/en/latest/boot-options.html
There are options for setting up the networking, choosing a graphical or text
install, and other options.
I’d
> Am 01.06.2024 um 07:20 schrieb Peter Boy :
> ...
> Additionally, I can send you my original documentation that I wrote for
> Hetzner (for F33, but it basically didn’t change much) by e-mail if you like.
Or you may download it from
https://pboy.fedorapeople.org/InstGuideF33-Hetzner-en.pdf
--
. So this is a lot more
work unless you plan to install a lot of Fedora servers, in which case
you also want to use kickstart and not a graphical install. ;-)
If you can specify the parameters, then the PXE boot can do VNC as well.
--
___
users mailing
> Am 01.06.2024 um 04:12 schrieb Alex :
>
> Hi,
> I'm trying to install fedora40 server on a server with 3x4TB disks and I
> don't understand how the RAID options work. I'm familiar with RAID and how it
> works, but it's been quite some time since I&#
Hi,
I'm trying to install fedora40 server on a server with 3x4TB disks and I
don't understand how the RAID options work. I'm familiar with RAID and how
it works, but it's been quite some time since I've used the fedora
installer, and it appears to have changed.
How do I
On Fri, May 31, 2024 at 6:06 PM Alex wrote:
> I have a new server with OVH that I'd like to install fedora40 over the
> network in some way. I can do IPMI, but that prevents me from doing a
> graphical install.
After booting the ISO via IPMI, you can spawn a VNC server and
comp
Hi,
I have a new server with OVH that I'd like to install fedora40 over the
network in some way. I can do IPMI, but that prevents me from doing a
graphical install.
I don't think I can do the PXE option because DHCP doesn't work across the
Internet. I'm assuming the DHCP serve
"liveinst --vnc" not working was filed as a bug 13 years ago and closed at EOL,
I reopened it.
https://bugzilla.redhat.com/show_bug.cgi?id=678354
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@list
The Linux video mode numbers are at
https://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers .
Since the best resolution of the old CRT I have connected to the machine is
1280x1024, I tried "vga=792", "vga=794" and "vga=795" and each of those work.
When in the 1024x768 modes
I found a solution. When booting the live image, I went into the
Troubleshooting menu and looked at the boot options for starting in basic
graphics mode. It had not only "nomodeset" but also "vga=791". By booting with
both of those, not just "nomodeset", I can boot the live image into graphical
John Pilkington composed on 2024-04-27 12:54 (UTC+0100):
> Felix Miata wrote:
...
>> System:
>>Host: mcp61 Kernel: 6.6.23-1-longterm arch: x86_64 bits: 64 compiler: gcc
>> v: 13.2.1 clocksource: tsc avail: acpi_pm parameters:
>> root=LABEL=
>> ipv6.disable=1 net.ifnames=0 noresume c
On 27/04/2024 04:28, Felix Miata wrote:
Andre Robatino composed on 2024-04-27 02:49 (UTC):
I have an old machine from 2008 with very old integrated graphics (GeForce
6150SE nForce 430). Up to and including F39, I was able to do a Live
Workstation install simply by using the nomodeset boot
elf but works much better than
a
6150SE. If another GeForce, it would be completely plug 'N play. Even if an AMD
it
could nevertheless be pure PNP.
OTOH, why install afresh rather than upgrade from F39 to F40 in the first
place? I
love how well upgrades go, and have no love for all the chang
I have 2 desktops, each running Fedora, the one in question is a backup that I
normally just log into with ssh and do updates, and would only use normally if
the main machine dies. I'll probably be buying a new machine in a year or two
and this one will go into storage, all of its hardware is ol
Andre Robatino composed on 2024-04-27 02:49 (UTC):
> I have an old machine from 2008 with very old integrated graphics (GeForce
> 6150SE nForce 430). Up to and including F39, I was able to do a Live
> Workstation install simply by using the nomodeset boot option. With F40 that
&g
I have an old machine from 2008 with very old integrated graphics (GeForce
6150SE nForce 430). Up to and including F39, I was able to do a Live
Workstation install simply by using the nomodeset boot option. With F40 that no
longer works - it fails to come up in graphical. I ended up doing a
u are using Fedora server, is that correct? I'm just curious
because I played around with using Raid 10 a couple of years ago
and ran into issues where Fedora workstation would not install on
raid only Fedora server had support for doing that.
I don't know why there would be a d
rrect? I'm just curious because I
played around with using Raid 10 a couple of years ago and ran into
issues where Fedora workstation would not install on raid only Fedora
server had support for doing that.
I don't know why there would be a difference. The installer and
drivers are t
yed around with using Raid 10 a couple of years ago and ran into
issues where Fedora workstation would not install on raid only Fedora
server had support for doing that.
I don't know why there would be a difference. The installer and
drivers are the same in both cases. I've never used
On Mar 20, 2024, at 20:10, Sam Varshavchik wrote:
>
> Stephen Morris writes:.
>>
>> If I can ask a silly question, given that on UEFI systems grub2-install is
>> redundant, and the initial messages you were getting were indicating you are
>> booting in a
Stephen Morris writes:
resynced all RAID partitions, I ran grub2-install and I'm fairly certain
there was a definitive change in grub's behavior, afterwards. Originally
three periods were initially shown, for a few seconds, before the grub menu
opened. I have a recollectio
e of years ago and ran into
issues where Fedora workstation would not install on raid only Fedora
server had support for doing that.
I don't know why there would be a difference. The installer and drivers
are the same in both cases. I've never used the server install and I've
bee
On 20/3/24 11:28, Sam Varshavchik wrote:
Samuel Sieb writes:
On 3/19/24 16:50, Sam Varshavchik wrote:
Samuel Sieb writes:
On 3/19/24 16:05, Sam Varshavchik wrote:
I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run
grub2-install to
On 3/19/24 17:29, Tom Horsley wrote:
On Tue, 19 Mar 2024 19:05:51 -0400
Sam Varshavchik wrote:
[root@jack ~]# grub2-install /dev/sda
That is the way you install grub for old MSDOS partitions.
To install grub with GPT and use EFI, it needs different
arguments. Something like:
grub2-install
disk, recently – after I reassembled
and resynced all RAID partitions, I ran grub2-install and I'm fairly
certain there was a definitive change in grub's behavior, afterwards.
Originally three periods were initially shown, for a few seconds, before
the grub menu opened. I have a recoll
On Tue, 19 Mar 2024 19:05:51 -0400
Sam Varshavchik wrote:
> [root@jack ~]# grub2-install /dev/sda
That is the way you install grub for old MSDOS partitions.
To install grub with GPT and use EFI, it needs different
arguments. Something like:
grub2-install --target x86_64-efi --removable --b
Samuel Sieb writes:
On 3/19/24 16:50, Sam Varshavchik wrote:
Samuel Sieb writes:
On 3/19/24 16:05, Sam Varshavchik wrote:
I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run grub2-install
to actually update the bootloader. Additionally I
On 3/19/24 16:50, Sam Varshavchik wrote:
Samuel Sieb writes:
On 3/19/24 16:05, Sam Varshavchik wrote:
I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run
grub2-install to actually update the bootloader. Additionally I run
mdraid, so I need
Samuel Sieb writes:
On 3/19/24 16:05, Sam Varshavchik wrote:
I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run grub2-install
to actually update the bootloader. Additionally I run mdraid, so I need the
bootloader on both /dev/sda and /dev
On 3/19/24 16:05, Sam Varshavchik wrote:
I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run
grub2-install to actually update the bootloader. Additionally I run
mdraid, so I need the bootloader on both /dev/sda and /dev/sdb.
[root@jack
I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run grub2-install to
actually update the bootloader. Additionally I run mdraid, so I need the
bootloader on both /dev/sda and /dev/sdb.
But:
[root@jack ~]# grub2-install /dev/sda
grub2-install
ions to Fedora that I am
>> stuck. I can work with GIT, that part is easy. But when I get past that,
>> I stall.
>>
>>
>> Can anyone take a look at this and advise?
>>
>
> The only Ubuntu specific command I saw was installing Flight Gear which
>
command I saw was installing Flight Gear
which would translate to:
$ sudo dnf install FlightGear
So
Tools/environment_install/install-prereqs-ubuntu.sh -y
or the alternative method
are not needed?
If so, I will give this a try when I get back Tuesday...
--
___
dvise?
>
The only Ubuntu specific command I saw was installing Flight Gear which
would translate to:
$ sudo dnf install FlightGear
Thanks,
RIchard
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-l
Greetings again,
I am continuing on my UAS work with one step wanting to simulate a set
of flights with the MAVlink data sent to my esp32 RemoteID modules for
transmission.
I have a couple esp32 set up, but how to get the data into them using
Fedora and not Windows and not even Ubuntu. Afte
On Thu, 2023-12-28 at 06:18 -0500, bruce wrote:
> Working with a test DO process, to install a package/module
I've no idea what "a test DO process" means.
poc
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscrib
On 12/28/23 06:44, bruce wrote:
I had tested on both, with same results... my bad..
pretty sure it's user err somewhere
If you want Fedora help, you will need to provide actual commands and
more details on what you're trying to do and what's happening.
What you provided in the initial post
Hi Barry.
I had tested on both, with same results... my bad..
pretty sure it's user err somewhere
On Thu, Dec 28, 2023 at 7:17 AM Barry Scott wrote:
>
>
>
> > On 28 Dec 2023, at 11:18, bruce wrote:
> >
> > Hi,
> >
> > Working with a test DO process,
> On 28 Dec 2023, at 11:18, bruce wrote:
>
> Hi,
>
> Working with a test DO process, to install a package/module
>
> install npm
>
> .
> .
> .
> Failed to restart ssh.service: Transaction contains conflicting jobs
> 'stop' and 'restart&
1 - 100 of 3861 matches
Mail list logo
