Re: Installation & EFI
by Ryan Cunningham
> 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
8 months, 2 weeks
Locate not working
by GianPiero Puccioni
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
8 months, 2 weeks
Fedora distro with EFI cd image
by Gunnar Gervin
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.
8 months, 2 weeks
NFS mount
by Dave Close
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
8 months, 2 weeks
rkhunter warning
by François Patte
Bonjour,
Since I upgraded to f34, rkhunter is warning me with this file:
Warning: Hidden file found: /usr/share/man/fr/man1/..1.gz: symbolic link
to builtins.1.gz
Asking rpm -qf /usr/share/man/fr/man1/..1.gz, it returns that this file
belongs to the man-pages-fr package.
rkhunter --propupd does not change anything, every day rkhunter sends me
a warning mail...
Which of these two must be believed: rkhunter or rpm -qf?
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
8 months, 2 weeks
OT: RGB mechanical keyboard
by Frederic Muller
Hi!
This is a bit borderline but since I guess everybody is using a PC here
(or a MAC...) you probably have a keyboard too...
I recently (less than a year) got a mechanical keyboard (Logitech G512 -
liked the 512 number...) and it's been complicated. I initially offered
one to my wife, she loved it and "forced" me to get one too.
I had to wash it dismantling the keys, putting them in soap and water,
drying them, etc. I also bought a small hover to suck the potential dust
creating problems (or ... something else). After less than a year both
keyboards have been back under warranty, one because of the RGB lights
breaking on some keys, the other one because of keys not working after a
few hours of work (that's mine).
When having problems (like the space bar, C key, arrows, etc stop
working) I eventually took other keyboards I already have, and then I
really missed the 'typing quality' of the mechanical one.
I also appreciate that the Logitech keyboard do have Free Software
projects allowing you to control each key and set up the lighting the
way you want. You can even do (keyboard) games with those.
I however suffered all those (un)typing issues and am disappointed by
the overall quality. 2 keyboards, 2 went back under warranty (1
replaced, 1... waiting for it).
So let's say I am hooked with the technology but...
Do you guys know of any keyboard with similar typing quality but with
durability and eventually free software driving the RGB lighting? I can
probably live without the RGB stuff as well ;-)
Oh .. I don't play games, just spend the whole day (and night?) behind
(in front of?) my PC.
Thank you.
Fred
ps: numeric pad is a must
8 months, 2 weeks
Windows (Super) key stopped working
by Richard Shaw
At some point my Windows (Super) key stopped working.
Trying the following doesn't produce any output when the super key is
pressed:
$ xinput list
WARNING: running xinput against an Xwayland server. See the xinput man page
for details.
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ xwayland-pointer:18 id=6 [slave pointer (2)]
⎜ ↳ xwayland-relative-pointer:18 id=7 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ xwayland-keyboard:18 id=8 [slave keyboard (3)]
$ xinput test 8
But pluggin my keyboard into my work laptop running windows it works fine.
Thanks,
Richard
8 months, 2 weeks
installing Fedora: says empty disk is almost full
by Douglas McGarrett
Hello. I'm a potential new user, but I'm having trouble with the install.
I have Windows and Leap on one of the new on-board drives, and I
have added /dev/sda, a new Samsung 465 GiB ssd (ordinary type) to
the system. I formatted it to ext4 using GParted, and it's empty except
for 8.38 GiB at the beginning that GParted must have added. When I try
to add theFedora system to this, it says there is only 1.2 GiB available.
I went back and ran GParted on it again, but it still comes up the same way.
What am I doing wrong? Or is the drive defective? GParted doesn't
complain about it.
Thans for your assistance--doug
8 months, 2 weeks
Fedora 34/KDE/Plasma desktop wallpaper showing through application
windows ?
by linux guy
Hi.
Fedora 34 / KDE / Plasma. Everything works great except that I can see the
Fedora 34 desktop wallpaper patterns in my application windows. The
desktop wallpaper is "bleeding through", like the application windows are
transparent.
How do I fix this ? Is it an effect in Settings ?
Hardware: Asus A17 4800H with integrated GPU as well as a discrete
GTX1660Ti.
$ uname -a
Linux fedora 5.13.12-200.fc34.x86_64 #1 SMP Wed Aug 18 13:27:18 UTC 2021
x86_64 x86_64 x86
_64 GNU/Linux
Installed Packages
plasma-breeze.x86_64 5.22.4-1.fc34 @updates
Thanks.
Fedora rocks !
8 months, 2 weeks
