New Install of F29 in a VM Doesn't Display the Grub Menu
by Stephen Morris
Hi,
I have installed Windows 10 on my raid system as that was the only
OS the new motherboard provided raid drivers for at install time. The
install of Windows 10 was done in UEFI mode (albeit there doesn't appear
to be a UEFI partition on the ssd windows is installed to, there is only
the drive C partition, a system partition and a recovery partition) and
the bios is currently set to UEFI mode. Under windows I have installed
vmware and used the USB live install of F29 that I have (which would not
boot natively in UEFI mode) which successfully installed F29. Having
done the install every time I boot it does not display a grub menu even
though there are multiple kernels installed. In F28 there was a grub
default file with supplied initial "default" grub configurations which
other files in /etc/grub.d supplemented to build (in a bios
installation) /boot/grub2/grub.cfg, but this default file doesn't appear
to be present in F29. Looking in /etc there is a link named
grub2-efi.cfg as well as grub2.cfg, the former of which is a link to
/boot/efi/EFI/fedora/grub.cfg, but this .cfg file does not exist.
Assuming there is a menu with a timeout of 0 so that it doesn't display,
where do I find the grub files that will allow me to change that timeout
and configure how the grub menus will display?
regards,
Steve
5 years, 1 month
How to disable CapsLock.
by Erik P. Olsen
Is there a way to make CapsLock a dead key? I never use this key on purpose and it's
irritating when I sometimes hit it without knowing, so I would rather have it doing
nothing.
--
Regards,
Erik P. Olsen
5 years, 1 month
Home-directory, NFS and automount
by Paul-Erik Törrönen
I've had for a long time a setup for (Fedora-)laptops where the laptop
has local home directories for users in /home/<username>
and in fstab the directory is mounted (when available) to NFS share on
home network.
This worked nicely until recently (F28/F29) when it seems that automount
was configured to attempt to mount /home as the user logs on (GDM).
Since this automount fails, the login is terminated despite the fact
that there is a valid /home/<username> on the fs.
So the question is: Is there anything similar in simplicity to set up as
a replacement to the current setup, or, alternatively, how does one
disable the automount from attempting to mount non-reachable NFS mounts
at login time?
Poltsi
5 years, 1 month
UEFI Migrate to new hard drive
by Richard Shaw
I bought an SSD to replace my HDD and I used System Rescue CD to move my
EFI and boot partitions over and then used lvm tools to add the new drive
to the lvm and then remove the old one.
So all of my data is over on the new driver... but I can't boot it...
I've looked at efibootmgr and it still has an entry for Fedora, the
partition looks correct and per efibootmgr the loader name looks good...
But no matter what I do it won't boot.
So I figured it out...
Somehow the PARTUUID did change... And using system rescue CD the efivars
was mounted read only so even though efibootmgr didn't complain, it wasn't
actually changing anything.
I had to:
efibootmgr -B 0001 (which was the fedora entry)
and then
efibootmgr -c -d /dev/sda -p 1 -l "EFI/fedora/shim.efi" -L Fedora
then it worked...
NOTHING ABOUT THIS IS INTUITIVE!
Thanks,
Richard
5 years, 1 month
OSM & GPS??
by Beartooth
I have a pair of old Garmin RINO 120 GPSs and a gadget to connect
either of them, one at a time, to my PC, currently running F 29. For
several years I could run topo map software under WINE -- unfree software
from any, or almost any, of half a dozen vendors -- but never get any of
them to talk to either GPS. Now there is Open Street Map, a.k.a. OSM,
which I THINK runs natively under Linux.
I have studied forums and followed discussion lists (with Pan and
Gmane, since most of the content is obviously unrelated to my
questions). For years.
It seems that everyone else is a mapMAKER, and takes mere USE for
granted. I only want to use it, and only out in the woods or the desert
or the tooley weeds -- all of which, it seems, OSM does map, despite its
name. I want to get maps to scale that show things of interest to me
only, or I hope only -- things like good lunch rocks, and nests, and
particular trees, all or nearly all off any trail.
Unlike the OSM regulars, I have no advanced skills in
cartography, nor EE, nor CS. My skills and knowledge are in unrelated
areas.
All this boils down to two questions. If I install OSM under
Fedora, will it accept, incorporate, and display off-road and off-trail
data from an old GPS, either with OSM's own data, or with things like USGS
topo maps? And if it will, can an ordinary mortal learn to use it?
--
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is.
5 years, 1 month
libvirtd, pihole, dnsmasq complaints
by Chris Murphy
I think this is just noise in the journal; not a real problem (it's an
annoyance).
Fedora Server 29 running two docker containers: pihole and battery
historian. When I do 'sysmtectl start libvirtd' I immediately start
getting the following in the journal every 5s.
Feb 11 13:53:23 fnuc.local dnsmasq[32033]: failed to create listening
socket for 192.168.122.1: Address already in use
That continues until I both stop libvirtd and also remove the virbr0
link. I'm kinda wondering if this is suboptimal behavior that
constitutes a bug? I don't know why it's failing to create a socket
for 192.168.122.1, maybe docker owns it. But then why doesn't libvirtd
just fallback to some other address and notify in the journal, rather
than spamming the journal? In any case I'm still able to ssh into and
out of any VM I create. I'm also able to connect via virt-manager and
spice to any VM. So its seems like it's just noise and not an actual
problem.
fnuc.local chris ~ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UP group default qlen 1000
link/ether b8:ae:ed:77:ea:51 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.250/24 brd 10.0.0.255 scope global dynamic noprefixroute enp3s0
valid_lft 377745sec preferred_lft 377745sec
inet6 2601:282:700:8c78:3cef:4672:2da9:af30/64 scope global
dynamic noprefixroute
valid_lft 252404sec preferred_lft 252404sec
inet6 fe80::91f1:7594:6bae:99ea/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether fe:b0:a1:f2:be:c4 brd ff:ff:ff:ff:ff:ff
4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP group default
link/ether 02:42:7a:65:7b:b6 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 scope global docker0
valid_lft forever preferred_lft forever
inet6 fe80::42:7aff:fe65:7bb6/64 scope link
valid_lft forever preferred_lft forever
6: vethe8a3f14@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue master docker0 state UP group default
link/ether d2:b4:ca:37:f7:3a brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::d0b4:caff:fe37:f73a/64 scope link
valid_lft forever preferred_lft forever
8: veth1b171f3@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue master docker0 state UP group default
link/ether 9a:f4:98:f3:08:1c brd ff:ff:ff:ff:ff:ff link-netnsid 1
inet6 fe80::98f4:98ff:fef3:81c/64 scope link
valid_lft forever preferred_lft forever
9: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN group default qlen 1000
link/ether 52:54:00:24:e3:cf brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
10: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master
virbr0 state DOWN group default qlen 1000
link/ether 52:54:00:24:e3:cf brd ff:ff:ff:ff:ff:ff
fnuc.local chris ~
--
Chris Murphy
5 years, 1 month
Very slow DNF update and a workabound
by Barry Scott
I'll been putting up with very slow dnf update for a while.
strace showed that it was reading /var/lib/rpm/Packages 4KiB at a time.
My /var/lib/rpm/Packages is 118MiB so that takes a while on a hard disk
around 60s.
My desktop is i7 4GHz CPU 16GiB of ram.
Unless there is a way to configure DNF to use bigger reads this hack speeds it
up.
# cat /var/lib/rpm/* > /dev/null; dnf update --refresh
After the cat of the files Packages will be in kernel buffers and then dnf
runs in 1s-2s.
Do you want a bug report on this issue?
Barry
5 years, 1 month
VirtualBox shared folder looses connection after a while
by Paul Smith
Dear All,
With the most recent versions of VirtualBox, the shared folder is not
working properly as before.
My guest machine is running Windows 7, and the shared folder works
fine during some time. However, after some time, the connection to the
shared folder gets lost. Are other people experiencing the same? Any
workaround?
Thanks in advance,
Paul
5 years, 1 month
more systemd brilliance
by Tom Horsley
Sometime recently systemd has decided to shutdown
the network interfaces before it unmounts all the
NFS filesystems, thus resulting in about a 5 minute
timeout on reboot.
I've now added code to my pre-reboot script to
umount -l and umount -f every nfs filesystem
prior to really rebooting, and I can reboot without
the 5 minute delay now (sheesh).
5 years, 1 month