Re: Failure in gsetting up a UEFI USB Flash with Fedora 33??
On 9/10/21 10:32 PM, Michael D. Setzer II via users wrote: All those options are talking about Secure boot keys. Turning off the Secure boot is not an issue. The user has done that, but the exact same USB Flash that boots fine on a 3070 doesn't show up as an option on the 3080. He can take a hard disk from a 3080 machine, install it in a 3070 machine, boot from the exact same USB on the 3070, and create and image with the 3070. The exact same USB does not show up on the 3080 as a boot option. Yes, it is not currently an EFI Flash so would not show up as a UEFI Flash boot option, but it also doesn't show up as a regular USB boot option. You seem to be stuck on harping about turning off secure boot, but that has been done with no problem. A lot of the problem is that you are being very unclear about what you're doing and it's very hard to follow. Now what you're saying is that a non-EFI flash drive doesn't boot on an EFI system. Why do you need to point that out? Unless you can enable legacy or CSM mode, it's obviously not going to work. And newer systems don't have that option any more. Also, you apparently ignored the part where he told you that there is no point in trying to use grub-install. It's not useful for EFI. You just need to copy a few files into the right directories. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Failure in gsetting up a UEFI USB Flash with Fedora 33??
On 11 Sep 2021 at 0:55, Samuel Sieb wrote: Subject:Re: Failure in gsetting up a UEFI USB Flash with Fedora 33?? To: users@lists.fedoraproject.org From: Samuel Sieb Date sent: Sat, 11 Sep 2021 00:55:54 -0700 Send reply to: Community support for Fedora users > On 9/10/21 10:32 PM, Michael D. Setzer II via users wrote: > > All those options are talking about Secure boot keys. > > Turning off the Secure boot is not an issue. The user has > > done that, but the exact same USB Flash that boots fine > > on a 3070 doesn't show up as an option on the 3080. > > > > He can take a hard disk from a 3080 machine, install it in > > a 3070 machine, boot from the exact same USB on the > > 3070, and create and image with the 3070. The exact > > same USB does not show up on the 3080 as a boot option. > > Yes, it is not currently an EFI Flash so would not show up > > as a UEFI Flash boot option, but it also doesn't show up > > as a regular USB boot option. > > > > You seem to be stuck on harping about turning off secure > > boot, but that has been done with no problem. > > A lot of the problem is that you are being very unclear about what > you're doing and it's very hard to follow. Now what you're saying is > that a non-EFI flash drive doesn't boot on an EFI system. Why do you > need to point that out? Unless you can enable legacy or CSM mode, it's > obviously not going to work. And newer systems don't have that option > any more. > Not sure how I can be clearer? Have a system that works fine with regular booting from a USB, but doesn't work on a new machine? Looking for a way to get it to work. Syslinux 6.04pre has some efi stuff, but I've tried it a couple times, and didn't work. Last release files go back to 2016?? > Also, you apparently ignored the part where he told you that there is no > point in trying to use grub-install. It's not useful for EFI. You just > need to copy a few files into the right directories. Question: Have a web site that I mentioned that says the grub2-install actually did work at some point, and a user on this list said that he used it in the past with no issue. If grub2-install doesn't support efi why does man grub2-install show grub-install [--modules=MODULES] [--install-modules=MODULES] [--themes=THEMES] [--fonts=FONTS] [--locales=LOCALES] [--compress[=no,xz,gz,lzo]] [-d | --directory=DIR] [--grub-mkimage=FILE] [--boot-directory=DIR] [--target=TARGET] [--grub-setup=FILE] [--grub-mkrelpath=FILE] [--grub-probe=FILE] [--allow-floppy] [--recheck] [--force] [--force-file-id] [--disk-module=MODULE] [--no-nvram] [--removable] [--bootloader-id=ID] [--efi-directory=DIR] It lists efi-directory, and it has an option --removable that seems to be able create on a flash?? So, did it work at some point, and someone decided to change it, and if so why didn't they remove the --efi-directory option?? I can see where if you already have a system that has the EFI boot setup, it would just be copying files. similar to how the 40_custom file allows the regular grub2 to add options to the grub.cfg to boot. But that doesn't help in creating a standalone flash to boot the files.. I've looked at the Dell machine I've got, and it is a 9020, and it boots the regular usb just fine. Did search thru the setup, and did find under the advanced bios option a check box to allow loading additional rom to support non-UEFI booting, and on my machine it is checked. It does say that if that isn't check you can not boot regular USB devices? Wondering if the 3080 machines might have this option unchecked, so I've sent a message to the user. So, it might be just enabling the option if it is there. If it isn't there still have an issue. The grub2-install with the i386 option does work, and it puts files on the flash, but the x86_64 option fails and writes nothing to the flash. Perhaps I need to look at other distros that might support it. Started with Unixware long long ago, and moved the Redhat 9, and have been with Fedora since Core 1 thru 33. Do have a Virtual box setup of 34 as well. Sorry to have bothered anyone. Seems I can't get there from here.. Have a nice day. > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure
Re: Failure in gsetting up a UEFI USB Flash with Fedora 33??
On Sat, Sep 11, 2021 at 06:51:47PM +1000, Michael D. Setzer II via users wrote: > Not sure how I can be clearer? Have a system that works > fine with regular booting from a USB, but doesn't work > on a new machine? Looking for a way to get it to work. > Syslinux 6.04pre has some efi stuff, but I've tried it a > couple times, and didn't work. Last release files go back > to 2016?? Newer machines == no longer supports legacy boot. Maybe you should look at some of the other suggestions on your project's forums, such as using Refind? It might be easier to create a bootable disk using refind than trying to build your own image? > > Also, you apparently ignored the part where he told you that there is no > > point in trying to use grub-install. It's not useful for EFI. You just > > need to copy a few files into the right directories. > > Question: Have a web site that I mentioned that says the > grub2-install actually did work at some point, and a user > on this list said that he used it in the past with no issue. > > If grub2-install doesn't support efi why does man > grub2-install show > grub-install [--modules=MODULES] [--install-modules=MODULES] > [--themes=THEMES] [--fonts=FONTS] [--locales=LOCALES] > [--compress[=no,xz,gz,lzo]] [-d | --directory=DIR] > [--grub-mkimage=FILE] [--boot-directory=DIR] > [--target=TARGET] [--grub-setup=FILE] > [--grub-mkrelpath=FILE] [--grub-probe=FILE] > [--allow-floppy] [--recheck] [--force] [--force-file-id] > [--disk-module=MODULE] [--no-nvram] [--removable] > [--bootloader-id=ID] [--efi-directory=DIR] > > It lists efi-directory, and it has an option --removable that > seems to be able create on a flash?? > > So, did it work at some point, and someone decided to > change it, and if so why didn't they remove the > --efi-directory option?? If you are curious, here is the patch Fedora adds: https://src.fedoraproject.org/rpms/grub2/blob/f34/f/0169-grub-install-disable-support-for-EFI-platforms.patch This is where it's disabled. GRUB2 has the capability, but it is patched to not work because it doesn't make sense for *Fedora*. > I've looked at the Dell machine I've got, and it is a 9020, > and it boots the regular usb just fine. Did search thru the > setup, and did find under the advanced bios option a > check box to allow loading additional rom to support > non-UEFI booting, and on my machine it is checked. It > does say that if that isn't check you can not boot regular > USB devices? Wondering if the 3080 machines might > have this option unchecked, so I've sent a message to the > user. So, it might be just enabling the option if it is there. > If it isn't there still have an issue. Intel and motherboard vendors have been saying they're going to drop legacy bootloader support. Honestly, I expected it sooner. It looks like you're seeing some Dells that don't support the legacy bootloader. Since you appear to be one of the people supporting G4L (I found the thread that must be related to this: https://sourceforge.net/p/g4l/discussion/408763/thread/24d7652d5f/?limit=25#88d0 ) then I am sorry that Fedora isn't useful for creating your project's boot images. But the grub2 package for Fedora is built for booting Fedora, and since it has signed EFI executables that can only be used for booting signed Fedora kernels, that makes sense. If you want to mess around with building your own UEFI capable boot image with your own kernel and initrd, I suggest going to the GRUB2 web site and compiling it. I think part of the confusion here was that many people didn't realize you were basically a proxy for supporting someone else in another forum. -- Jonathan Billings ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Problem reporting / Mate-Screensaver crash / Packagekit crach.
To all, When I activate the screesaver I get the message : Mate-Screensaver quit unexpectedly : Application crash, Packagekit idem : Application crash . When this happens ( after a delay of 5 minutes ) I get a blue screen and have to turn off the system by force , so hardware OFF. When I want to do a Problem Reporting I get the message : https://retrace.fedoraproject.org does not excist (server error 404) . Question : What now ? Regards , Ger van Dijck. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: has anyone got pipewire working F34??
On Fri, 10 Sep 2021 11:45:10 -0700 Jack Craig wrote: > i see ... > > aplay -L > null > Discard all samples (playback) or generate zero samples (capture) > samplerate > Rate Converter Plugin Using Samplerate Library > pipewire > PipeWire Sound Server > upmix > Plugin for channel upmix (4,6,8) > vdownmix > Plugin for channel downmix (stereo) with a simple spacialization > default > Default ALSA Output (currently PipeWire Media Server) > hdmi:CARD=NVidia,DEV=0 > HDA NVidia, HDMI 0 > HDMI Audio Output > hdmi:CARD=NVidia,DEV=1 > HDA NVidia, HDMI 1 > HDMI Audio Output > hdmi:CARD=NVidia,DEV=2 > HDA NVidia, HDMI 2 > HDMI Audio Output > hdmi:CARD=NVidia,DEV=3 > HDA NVidia, HDMI 3 > HDMI Audio Output > hdmi:CARD=NVidia,DEV=4 > HDA NVidia, HDMI 4 > HDMI Audio Output > usbstream:CARD=NVidia > HDA NVidia > USB Stream Output > [jackc@ws ~ $ aplay -lv > List of PLAYBACK Hardware Devices > card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 0: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 0: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 0: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 0: NVidia [HDA NVidia], device 10: HDMI 4 [HDMI 4] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > > snd 110592 10 > snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_timer,snd_pcm > snd_hda_codec 172032 2 snd_hda_codec_hdmi,snd_hda_intel > snd_hda_codec_hdmi 73728 1 > snd_hda_core 110592 3 > snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec > snd_hda_intel 57344 1 > snd_hrtimer16384 0 > snd_hwdep 16384 1 snd_hda_codec > snd_intel_dspcfg 28672 1 snd_hda_intel > snd_intel_sdw_acpi 20480 1 snd_intel_dspcfg > snd_pcm 135168 4 > snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core > snd_seq90112 1 snd_seq_dummy > snd_seq_device 16384 1 snd_seq > snd_seq_dummy 16384 0 > snd_timer 49152 3 snd_seq,snd_hrtimer,snd_pcm > soundcore 16384 1 snd The proper audio codecs are all loaded. > > 03:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce > GT 730] (rev a1) > 03:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio > Controller (rev a1) The proper video controller is loaded > > cat /proc/asound/devices > 1:: sequencer > 2: [ 0- 3]: digital audio playback > 3: [ 0- 7]: digital audio playback > 4: [ 0- 8]: digital audio playback > 5: [ 0- 9]: digital audio playback > 6: [ 0-10]: digital audio playback > 7: [ 0- 0]: hardware dependent > 8: [ 0] : control > 33:: timer The aplay -lv and this agree, that your sound devices are hdmi:0,[3,7,8,9,10] I'm not sure why the aplay -L isn't showing the same thing. The alternative method should have found one of these as the correct output in order to give you sound. You then would have to somehow tell pipewire to use that device. Online, I see that people are using pavucontrol with pipewire successfully. If you can do that, it should be easy to fix this. Just go into pavucontrol and, while music is playing (even if there is no sound), set the default device to the each of the hdmi outputs in turn, hdmi:0,3 hdmi:0,7 etc. When one of them outputs sound, leave it as the default. You then don't have to worry about translating the alsa form into the pipewire form; pavucontrol will have done it for you. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Problem with the dovecot-fts-xapian package.
Problem with the dovecot-fts-xapian package. Fedora 34 with latest updates. dovecot-2.3.16-1.fc34.x86_64 dovecot-fts-xapian-1.4.12-1.fc34.x86_64 [root@smicro conf.d]# systemctl restart dovecot [root@smicro conf.d]# doveadm index -A \* Fatal: Couldn't load required plugin /usr/lib64/dovecot/lib21_fts_xapian_plugin.so: Module is for different ABI version 2.3.ABIv15(2.3.15) (we have 2.3.ABIv16(2.3.16)) BR, Bob ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
