Adding /29 netblock to existing system
by Alex
Hi,
I have a fedora36 system with a single static IP. I'd now like to add a /29
to it. Ideally, I'd like to create a bridge and associate all IPs with that.
It used to be that I could edit the files in
/etc/sysconfig/network-scripts, but I know I can't do that any longer. Now
I have to use nmcli, but I was hoping someone could guide me through that
process.
It appears I need to create a profile, then activate it? But I want all 6
usable addresses from the /29 and the one /32 address to be active at the
same time, much like we used to do with eth0 and eth0:0, eth0:1, etc.
I've done quite a bit of reading of nmcli tutorials, and none seem to
discuss how to not only add a /29 (+ipv4.addresses ?) but also have it
active at the same time as the /32 I already have.
Thanks,
Alex
1 year, 10 months
Dual monitor setup with Wayland not working
by Simon Colston
Hi,
I am using Fedora Workstation 36 and have 2 monitors connected via HDMI to graphics on the motherboard (Intel) and a
nvidia graphics card.
Everything works fine when I log in using Xorg.
However, if I log in using Wayland, the monitor connected to the motherboard stays blank. The monitor is detected in
Settings and appears to be 'working' i.e. if I move a window to the blank monitor I can click on it and it works as
expected, it's just that nothing is displayed on that monitor.
Do you have any suggestions as to how I could make this setup work with Wayland?
Below is come information which I thought may be helpful.
$ uname -rsvp
Linux 5.17.12-300.fc36.x86_64 #1 SMP PREEMPT Mon May 30 16:56:53 UTC 2022 x86_64
$ lspci -k | grep -A 5 VGA
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] (rev 02)
DeviceName: Onboard - Video
Subsystem: ASUSTeK Computer Inc. Device 8694
Kernel driver in use: i915
Kernel modules: i915
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
--
01:00.0 VGA compatible controller: NVIDIA Corporation GP108 [GeForce GT 1030] (rev a1)
Subsystem: eVga.com. Corp. Device 6336
Kernel driver in use: nouveau
Kernel modules: nouveau
01:00.1 Audio device: NVIDIA Corporation GP108 High Definition Audio Controller (rev a1)
Subsystem: eVga.com. Corp. Device 6336
$ cat .config/monitors.xml
<monitors version="2">
<configuration>
<logicalmonitor>
<x>0</x>
<y>0</y>
<scale>1</scale>
<primary>yes</primary>
<monitor>
<monitorspec>
<connector>HDMI-2</connector>
<vendor>DEL</vendor>
<product>DELL U2518D</product>
<serial>3C4YP93RAEDL</serial>
</monitorspec>
<mode>
<width>2560</width>
<height>1440</height>
<rate>59.950550079345703</rate>
</mode>
</monitor>
</logicalmonitor>
<logicalmonitor>
<x>2560</x>
<y>0</y>
<scale>1</scale>
<monitor>
<monitorspec>
<connector>HDMI-1-1</connector>
<vendor>DEL</vendor>
<product>DELL U2518D</product>
<serial>3C4YP93LAYAL</serial>
</monitorspec>
<mode>
<width>2560</width>
<height>1440</height>
<rate>59.950550079345703</rate>
</mode>
</monitor>
</logicalmonitor>
</configuration>
</monitors>
Thanks,
Simon
--
Simon Colston
1 year, 10 months
resurrecting old laptops
by jim.cromie＠gmail.com
so Ive got some old i686 computers,
electronics recycle day approaches, but before I do that,
I thought Id try to get them working
1st one (toshiba satellite core2 laptop) threw a hard-drive,
clunking noises, then finally falls back to pxe-boot.
I put fedora-30-live on a usb (last one with i686 support)
but booting it, I get a 2-line error:
This kernel requires x86-64, but only detected i686
unable to boot - ...
I know f30 supports i686 - I have 1 old desktop still running it.
next is hp pavilion g7
pressing power gives brief spin-up of fans, nothing else.
f2, f10, esc during boot dont help,
screen brightness or vga monitor dont help either
I pulled hard drive and memory to force BIOS / POST
to do something different, NO CHANGE.
Any suggestions?
but at least I have a new/old hard-drive for the toshiba.
I also have a dell pentium2-233,
running knoppix with a 2.6.19 kernel,
its reluctant to do anything (aptitude is trying forever)
I think its too old to have a bios that can usb boot
I have used fedora-live-usb to rescue machines
in the past, but Im running out of options.
I would welcome other distro suggestions for tired old hardware
thanks
1 year, 10 months
font tools (was "font longevity questions.").
by home user
(Fedora 35)
In the original post of the "font longevity questions/", I said:
> By the way, why do so many fonts show up twice
> in the font selection tools?
First, the only fonts I recall installing myself are the "Nimbus Roman
No9 L" fonts.
The tools are (in gnome) "Fonts" and "MATE Font Viewer". There might be
others not showing up when I click gnome's "Activities".
I did two screen captures to show what I'm referring to. They're on the
google drive here:
1.
"https://drive.google.com/file/d/1BkB55RW4jqym7_8xRdkExPtPD_XxR1Np/view?us...".
2.
"https://drive.google.com/file/d/1b7Pe_ASGEkfJj8XnIZAVaoznPHj1UOsp/view?us...".
Notice in the first, each of the "Nimbus" fonts shows up twice. When I
clicked on them, I saw no difference. In the second screen capture,
some "Open Sans" fonts show up twice. When I clicked on them, I saw no
difference. Is this how it should be, or is there a bug in the font
tools, or are some fonts actually on my work station twice?
A second issue is that fonts that are different show up in the font
tools with the same name. In this screen capture (on the google drive):
"https://drive.google.com/file/d/1qMfya_ObKot3jNbzYjTI7y17Kb0S83lz/view?us...",
notice 4 fonts called "Noto Sans". They are different from each other.
Notice 4 fonts called "Noto Sans, Bold". They are different from each
other. There are other examples. This is only my opinion, but they
should have different names. Is the problem in the font tools or in the
fonts themselves? If the problem is in the fonts themselves, then there
should be a standard requiring unique naming of fonts.
1 year, 10 months
Strange mount behaviour
by Patrick O'Callaghan
I have a couple of /etc/fstab entries which include the options
"noauto,nofail,user,x-systemd.automount", yet when I reboot the system
those entries are being mounted, despite the "noauto".
Furthermore, under my user account I can't access them:
$ sudo ls -ld GDrive/Media/
drwxrwxr-x. 1 poc poc 16 Feb 19 10:46 GDrive/Media/
$ sudo ls -l GDrive/Media/
total 0
drwxr-xr-x. 1 root root 0 Jun 3 11:24 Movies
drwxr-xr-x. 1 root root 0 Jun 3 11:24 TV
$ ls GDrive/Media/
ls: cannot access 'GDrive/Media/TV': Permission denied
ls: cannot access 'GDrive/Media/Movies': Permission denied
The mounting is done via Rclone, if it matters. If I run it manually as
myself it works as expected, so apparently this is somehow being caused
by systemd running as root., even though the directory permissions
appear to be as they should.
Is there a way to fix this without having to create a separate systemd
mount unit?
poc
1 year, 10 months
font longevity questions.
by home user
Good morning,
I have about 240 microsoft office word 2010 documents, all 9+ years old,
that I'm converting to LibreOffice Writer in Fedora-35. I'm having to
do this in 3 steps:
1. In windows-7, content is copied from the word files to Writer files.
Tweaks are made to line spacing in tables. The word documents use two
fonts: Times New Roman (various sizes; sometimes regular, sometimes
italic, sometimes bold), and Vivaldi. Writer in windows-7 seems to
support all the fonts used in the word documents.
2. Writer files are copied to my Fedora workstation.
Unfortunately, neither Times New Roman nor Vivaldi are available in
Fedora-35. So I need a step 3: to convert the fonts to choices that are
available in Fedora-35, and are expected to be available for a long time
to come. It's that last condition that I need help with. It's happened
to me in the past that a font that I used in Writer (in Fedora) ceased
to be available, so I changed it to the closest match that was
available. Then that font ceased to be available. So before I start
step 3 with them 240ish Writer files, how do I know which fonts are
likely to be permanent or supported in Fedora for many years, and which
are most vulnerable to being sunset sooner rather than later?
By the way, why do so many fonts show up twice in the font selection tools?
Thank-you in advance.
1 year, 10 months
OpenVPN breakage
by Ron Yorston
Today OpenVPN was updated from 2.5.6-1 to 2.5.7-1 and my VPN connection
broke. The log says:
nm-openvpn[8655]: --cipher is not set. Previous OpenVPN version defaulted to BF-CBC as fallback when cipher negotiation failed in this case. If you need this fallback please add '--data-ciphers-fallback BF-CBC' to your configuration and/or add BF-CBC to --data-ciphers.
nm-openvpn[8655]: OpenVPN 2.5.7 x86_64-redhat-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on May 31 2022
nm-openvpn[8655]: library versions: OpenSSL 3.0.2 15 Mar 2022, LZO 2.10
nm-openvpn[8655]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
nm-openvpn[8655]: Cipher BF-CBC not supported
nm-openvpn[8655]: Exiting due to fatal error
2.5.6-1 says almost exactly the same, apart from the last two lines,
and doesn't break.
Adding 'cipher=AES-256-GCM' to the NetworkManager keyfile for the
VPN got it working again. The advice about 'data-ciphers-fallback'
and 'data-ciphers' is bogus because NetworkManager doesn't know about
those options.
Not happy,
Ron
1 year, 10 months
Middle click paste to terminal doesn't hit [enter]
by Thomas Cameron
I use Xfce on Fedora 36. When using the shell (xfce4-terminal), I used
to be able to double click on text in one shell window and middle click
on another shell window to paste the command. If I am logged into a
bunch of kvm instances, for instance, I could double click on yum -y
update on one system and then paste it into the others.
Now, when I paste, even if I paste a newline at the end, the command is
not run in the other shell windows unless I hit [enter]. This is kind of
a pain, and I can't figure out how to enable pasting a command with a
newline to actually process that newline.
I've dug through the settings for the terminal (edit/preferences) and I
can't see anything that I can set to make this work. Anyone got a pointer?
Thanks!
Thomas
1 year, 10 months
f36 - kernel update breaks resolv.conf
by Eyal Lebedinsky
I am on f36 for a few weeks now, upgraded from f34.
This is the second time this happened. A 'dnf update' runs fine but hangs at the very end, after the list of 'Veritying'.
dnf (the python3 process) is in state D+ (though I could kill it).
dnf.log ends with
2022-05-31T21:32:33+1000 DDEBUG RPM transaction start.
2022-05-31T21:37:51+1000 DDEBUG RPM transaction over.
It is missing the usual final stanza, like
2022-05-16T22:21:23+1000 DDEBUG RPM transaction over.
2022-05-16T22:21:23+1000 DDEBUG timer: verify transaction: 672 ms
2022-05-16T22:21:23+1000 DDEBUG timer: transaction: 2669 ms
dnf.rpm.log ends with this interesting line
2022-05-31T21:37:06+1000 INFO '/etc/resolv.conf' -> '../run/systemd/resolve/stub-resolv.conf'
and sure enough I lost connectivity which may have lead to dnf hanging.
Rebooting leave my network setup broken in the same way.
Restoring resolv.conf to my usual hand made file gets things going.
This seems to happen when a kernel is updated but not at other times.
While I can "fix" it (I keep a resolv.conf.good) when it happens, I would rather sort it out permanently if it is a local issue.
Any idea?
--
Eyal Lebedinsky (fedora(a)eyal.emu.id.au)
1 year, 10 months
