users September 2021

users@lists.fedoraproject.org

73 participants
77 discussions

Using locate github
by Robert Moskowitz 10 Sep '21

10 Sep '21

I have a F32 system I am using with github. Yes, I know updating is overdue.... Github has switched to person access tokens since the last time I used it. I created my https PAT but can't seem to get the git command to use it. It just uses my GIt ID and password which now gets rejected. Any recommendation (other than updating to F34!) to get my "git push origin" command to work? It seems that there is a github-cli in beta, but does not seem to be an option here. thanks

3 3

Re: Failure in gsetting up a UEFI USB Flash with Fedora 33??
by Samuel Sieb 10 Sep '21

10 Sep '21

So the error message is "initramfs unpacking failed: no cpio magic". I I guess you will need to repack your initramfs to be compatible with the Fedora kernel. Are you aware that there are various tools included with Fedora to help you create live boot images?

1 0

cups is the worst software....
by François Patte 08 Sep '21

08 Sep '21

Bonjour, I have several computers at home and one with an usr-printer attached. I struggled sometimes to configure cups on other computers to use this printer. Now I upgraded to f34, and the configuration no longer works: "printer is misconfigured or no longer exists" is the answer if I send a test page.... After deleting the printer, I try to use the discovery tool in the administration page of cups (localhost:631) and it find the printer attached to my main computer but at the end of the configuration, when I try to print a test page, the answer is the same: "printer is misconfigured or no longer exists" This tool also finds old printers I configured many years ago and which (really) non longer exist... What to do? 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. +33 (0)6 7892 5822

6 6

pipewire configuration for f34
by Jack Craig 07 Sep '21

07 Sep '21

in trying to fathom my loss of audio out, i keep seeing reference to files in /etc/pipewire/ where my install has nothing! What am I missing? thx!

5 9

Installation & EFI
by Gunnar Gervin 06 Sep '21

06 Sep '21

Hi all. Where do I find a Fedora distro with EFI ? In here cos heard & read that Fedora supports EFI boot. I set wrongfully up my Macbook 2,1 OSX 10.6.8 (2007) x86-64 with Debian 32bit. Because 32bit gets outdated and bnasically is wrong for the computer, I wanted 64bit. But of some reason the computer only opens distros with EFI, like Bionic Pupp x86-64. Fedora version I found only shows up a "Windows" cd image, no "EFI" cd image on the (right) side of it. Heard that EFI is a boot installer, but unpopular because it comes (for free, but copyrighted(?)) from Microsoft(, & probably can't be changed). Thus most installers in the end (e.g Refracta, in Devuan) claim the need of Grub, where to place Grub. Destroying all the installation work done. This, due to my low knowledge, has made my computer unusable from the hard disk, only from RAM using a live Bionicpup x86-64 dvd. A friend said he was able to UEFI install Fedora. Checked online, found article that claimed Fedora as one distro supporting EFI in installing. But my computer can only open a distro with EFI image; no EFI gives only a blinking ? sign or a black irresponsive screen with: 1. 2. Boot option I write this from my work computer. The EX Mac /Linux machine is needed 'only' for private; entertainment, friendly online contact, and writing.

3 2

OT: How to load kernels in EFI setup.
by Michael D. Setzer II 06 Sep '21

06 Sep '21

Have a project that I've maintained since 2004. Have a simple process to add it to the regular grub boot list using the 40_custom with the following lines. menuentry G4L { linux /bz5x13.14 root=/dev/ram0 initrd /ramdisk.lzma } Just copy the kernel and ramdisk.lzma to /boot and it becomes an option in the grub menu. Just had a use that got 140 new Dell machines, and they seem to no longer support any bios boot?? So, EFI is the only option. Have the EFI kernel options set, but haven't found info on how to make an efi boot. I've looked, but I've not seen anything. Did find one page that talks about just copying kernel files to the efi direct with a minor rename and including System.map file, but doesn't say anything about the filesystem? Anyone know of a web page. Currently, the user is pulling drive out, and connecting it to an older machine to make images. Thanks.

2 4

Re: Installation & EFI
by Ryan Cunningham 05 Sep '21

05 Sep '21

> El sep. 5, 2021, a la(s) 9:12 p.m., Ryan Cunningham <happytobe2e(a)outlook.com> escribió: > > El sep. 5, 2021, a la(s) 10:35 a.m., Gunnar Gervin <dofeelok(a)gmail.com> escribió: >> >> Hi all. >> Where do I find a Fedora distro with EFI ? >> In here cos heard & read that Fedora supports EFI boot. >> I set wrongfully up my Macbook 2,1 OSX 10.6.8 (2007) x86-64 with Debian 32bit. >> Because 32bit gets outdated and bnasically is wrong for the computer, I wanted 64bit. >> But of some reason the computer only opens distros with EFI, like Bionic Pupp x86-64. >> Fedora version I found only shows up a "Windows" cd image, no "EFI" cd image on the (right) side of it. > > Are you sure that you are using the latest version of Fedora? Fedora Workstation 34 in UEFI mode works fine on my Acer Spin 3. Also, look carefully, because the boot image—although it uses UEFI—might not have “EFI” or “UEFI” in its name. Fedora boot images on Macs usually show the “Fedora” name and the Infinity Design (Fedora’s logo) in the Apple Boot Manager. >> Heard that EFI is a boot installer, but unpopular because it comes (for free, but copyrighted(?)) from Microsoft(, & probably can't be changed). >> Thus most installers in the end (e.g Refracta, in Devuan) claim the need of Grub, where to place Grub. Destroying all the installation work done. >> This, due to my low knowledge, has made my computer unusable from the hard disk, only from RAM using a live Bionicpup x86-64 dvd. A friend said he was able to UEFI install Fedora. Checked online, found article that claimed Fedora as one distro supporting EFI in installing. But my computer can only open a distro with EFI image; no EFI gives only a blinking ? sign or a black irresponsive screen with: 1. 2. Boot option >> I write this from my work computer. The EX Mac /Linux machine is needed 'only' for private; entertainment, friendly online contact, and writing. >> _______________________________________________ >> users mailing list -- users(a)lists.fedoraproject.org >> To unsubscribe send an email to users-leave(a)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 > _______________________________________________ > users mailing list -- users(a)lists.fedoraproject.org > To unsubscribe send an email to users-leave(a)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

1 0

Locate not working
by GianPiero Puccioni 05 Sep '21

05 Sep '21

Hi, I have a recent installation of F34 with the default brtfs and I discovered that updatedb and locate don't see the files in /home. Is there a workaround for that? G

2 3

Fedora distro with EFI cd image
by Gunnar Gervin 05 Sep '21

05 Sep '21

Hi all. Where do I find a live Fedora x86-64 iso image with EFI 'cd image' in it ? (My 2007 ex-Mac computer now only runs Puppy x86-64 live dvd in RAM.) My Macbook 64b computer won't open any iso without a cd image named EFI. Alt key on startup will show a 'Window cd', on the right side I need an 'EFI cd', too. Read that Fedora supports EFI. So I'm here, asking for your help &/or a link to ISO. BR, Gunnar Gervin.

2 1

NFS mount
by Dave Close 05 Sep '21

05 Sep '21

I'm trying to setup an NFS mount to an older NAS device. The client is Fedora 34, the NAS is a Buffalo Linkstation. I have access to the NAS via SSH and I can successfully mount it using CIFS and SSHFS. Of course, CIFS loses some file attributes and SSHFS seems slow and doesn't see the filesystem usage properly. So I'd prefer NFS but it keeps failing. I've even tried with my firewall disabled but no luck. The NAS only works with NFS v2. It's NFS is a client-side application as there is no NFS built into its kernel. But it is nothing new; the app has been running successfully for many folks for years. All the necessary ports seem to be open. # nmap -sU -p2049,111 nas1 PORT STATE SERVICE 111/udp open rpcbind 2049/udp open nfs # nmap -sT -p2049,111 nas1 PORT STATE SERVICE 111/tcp open rpcbind 2049/tcp open nfs I can access the NAS with rpcinfo and showmount. # showmount -e nas1 Export list for nas1: /mnt/array1/share client.compata.com # rpcinfo -p nas1 program vers proto port service 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100003 2 udp 2049 nfs 100003 2 tcp 2049 nfs 100005 1 udp 726 mountd 100005 2 udp 726 mountd 100005 1 tcp 729 mountd 100005 2 tcp 729 mountd But mount fails. # mount -v -o vers=2 -t nfs nas1:/mnt/array1/share /nas1 mount.nfs: timeout set for Sat Aug 28 17:52:01 2021 mount.nfs: trying text-based options 'vers=2,addr=192.168.44.20' mount.nfs: prog 100003, trying vers=2, prot=6 mount.nfs: trying 192.168.44.20 prog 100003 vers 2 prot TCP port 2049 mount.nfs: prog 100005, trying vers=1, prot=17 mount.nfs: trying 192.168.44.20 prog 100005 vers 1 prot UDP port 726 mount.nfs: mount(2): Protocol not supported mount.nfs: Protocol not supported # mount -v -o udp -o vers=2 -t nfs nas1:/mnt/array1/share /nas1 mount.nfs: timeout set for Sat Aug 28 17:53:43 2021 mount.nfs: trying text-based options 'udp,vers=2,addr=192.168.44.20' mount.nfs: prog 100003, trying vers=2, prot=17 mount.nfs: trying 192.168.44.20 prog 100003 vers 2 prot UDP port 2049 mount.nfs: prog 100005, trying vers=1, prot=17 mount.nfs: trying 192.168.44.20 prog 100005 vers 1 prot UDP port 726 mount.nfs: mount(2): Protocol not supported mount.nfs: Protocol not supported I have tcpdump captures from both ends and I don't see anything obviously wrong. (But then I'm not sure just what I ought to see there.) I do see the portmap calls and the results seem ok. Each is followed by a null call and a null reply, again nothing obviously wrong. I don't understand why the mount proceeds to use V1 for prog 100005 (mount) without any indication of a problem with the V2 attempt for NFS. But forcing V2 for both doesn't help. # mount -v -o nfsvers=2 -o mountvers=2 -o mountproto=tcp -t nfs nas1:/mnt/array1/share /nas1 mount.nfs: timeout set for Sat Aug 28 18:28:37 2021 mount.nfs: trying text-based options 'nfsvers=2,mountvers=2, mountproto=tcp,addr=192.168.44.20,mountaddr=192.168.44.20' mount.nfs: prog 100003, trying vers=2, prot=6 mount.nfs: trying 192.168.44.20 prog 100003 vers 2 prot TCP port 2049 mount.nfs: prog 100005, trying vers=2, prot=6 mount.nfs: trying 192.168.44.20 prog 100005 vers 2 prot TCP port 729 mount.nfs: mount(2): Protocol not supported mount.nfs: Protocol not supported I can't find anything relevant in any system log. The final message, "Protocol not supported", doesn't clearly indicate which protocol -- I presume mount(2) -- nor give any clue to a remedy. But if I force v3 for mount, I get a version mismatch. -- Dave Close, Compata, Irvine CA +1 714 434 7359 dave(a)compata.com dhclose(a)alumni.caltech.edu "Computers are useless. They can only give you answers." -- Pablo Picasso

6 8