Upgraded from 35 to 36, and noticed that VirtualBox wasn't working with 6.0.15, but would with 6.0.14?
by Michael D. Setzer II
Appears there is
kmod-VirtualBox-6.0.14-200.fc36.x86_64-7.0.4-1.fc36.x86_64
but not a version for 6.0.15 yet?
Gave message the vboxdrv wasn't loaded, but ran the
commands it said, but guess without the package, it
couldn't build the module.
But was able to boot with 6.0.14, and do the testing I
needed. Took a while to figure out the issue, so have to
check for updates.
Just thought I'd mention it. Had no issues with Fedora
35, so at first thought it might be a Fedora 36 issue.
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
1 year, 3 months
monitor/display problem.
by home user
(f36)
Good afternoon,
A short while ago, I did my weekly patches (dnf upgrade), and then
re-booted. Just before that, the workstation display (dual monitor) was
fine. After the reboot, only one display works. If I switch the monitor
cables, I still get a one-monitor display, but on the other monitor.
This leads me to think that the problem is not with the monitors. The
display in the one monitor looks a little fuzzy and stretched out
horizontally. I also notice at the end of the boot log the following lines:
-----
M
[K[ [0;31m*[0;1;31m*[0m] (2 of 3) Job plymouth-quit-wait.ser…tart
running (1min 17s / no limit)
M
[K[ [0;31m*[0;1;31m*[0m[0;31m*[0m] (2 of 3) Job
plymouth-quit-wait.ser…tart running (1min 17s / no limit)
M
[K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] (3 of 3) Job
akmods.service/start running (1min 18s / no limit)
M
[K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] (3 of 3) Job
akmods.service/start running (1min 18s / no limit)
M
[K[[0;32m OK [0m] Finished [0;1;39makmods.service[0…all new kmods
from akmod packages.
[K Starting [0;1;39mnvidia-fallback.s… nouveau as nvidia did
not load...
[[0;32m OK [0m] Finished [0;1;39mnvidia-fallback.s…to nouveau as
nvidia did not load.
Starting [0;1;39mgdm.service[0m - GNOME Display Manager...
[[0;32m OK [0m] Started [0;1;39mgdm.service[0m - GNOME Display
Manager.
-----
(first and last lines are for context only)
I can't memorize fast enough, but I did notice during the last boot
lines very much like (or identical to?) the lines above that mentioned
"nvidia".
What is the problem?
More important, how do I fix it?
thanks,
Bill.
1 year, 3 months
need perm. fix for monitor/display problem.
by home user
f36; workstation is 9 years old; dual boot (the other OS is the nearly
useless windows-7); dual monitor; stand-alone (not a part of a LAN, WAN,
etc.); I don't have other hardware to fall back on, not even a cell
phone; nvidia geforce gtx 660 graphics card; driver is from RPM Fusion
non-free.
Note: I have no training or significant experience in sys. admin.
original problem:
On Nov. 03, I did my weekly "dnf upgrade". This resulted in only one
monitor working, and the display on that monitor looking fuzzy and
horizontally stretched out.
diagnosis (from the Fedora users list):
The driver version installed by the "dnf upgrade" is not compatible with
the latest kernel and needs updating. The kernel version was
6.0.5-200.fc36. The fixed nvidia 470 drivers were still in testing.
work-around until fixed nvidia 470 drivers pass testing and reach
rpmfusion-nonfree-updates (from the Fedora users list):
1. back-up the initrd being used before the Nov. 03 "dnf upgrade".
2. use the kernel in use (5.19) before the Nov. 03 "dnf upgrade".
The recommended back-up was done on Nov. 04. I've been using the 5.19
kernel exclusively since then. I have not run "dnf upgrade" since Nov. 03.
current situation:
I'm using the 5.19 kernel exclusively.
I have not run "dnf upgrade" since Nov. 03.
The RPM Fusion web site page
"https://mirror.fcix.net/rpmfusion/nonfree/fedora/updates/36/x86_64/repovi..."
now shows this...
---------------
Latest packages:
2022-11-29: nvidia-settings-470xx-470.161.03-1.fc36
2022-11-29: akmod-nvidia-470xx-470.161.03-1.fc36
2022-11-29: kmod-nvidia-470xx-470.161.03-1.fc36
2022-11-29: xorg-x11-drv-nvidia-470xx-470.161.03-1.fc36
2022-11-29: xorg-x11-drv-nvidia-470xx-cuda-470.161.03-1.fc36
2022-11-29: xorg-x11-drv-nvidia-470xx-cuda-libs-470.161.03-1.fc36
2022-11-29: xorg-x11-drv-nvidia-470xx-devel-470.161.03-1.fc36
2022-11-29: xorg-x11-drv-nvidia-470xx-kmodsrc-470.161.03-1.fc36
2022-11-29: xorg-x11-drv-nvidia-470xx-libs-470.161.03-1.fc36
2022-11-29: xorg-x11-drv-nvidia-470xx-power-470.161.03-1.fc36
(and other things not relevant to this issue)
---------------
The original problem left my workstation quite crippled. It took a lot
of time and effort to research, construct, and post messages in the
original list thread. I don't have other hardware to fall back on, not
even a cell phone. Proceeding with the fix to the problem strikes me as
risky.
first question:
Is what is currently in RPM Fusion non-free 36 updates everything I need
to really fix the problem for f36?
Please don't jump the gun. Just answer that first question. If the
answer is positive, I'll follow up with more questions.
further information:
Anyone wanting to view the original Nov. 03-04 thread, it's here:
"https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...".
Thank-you in advance.
Bill.
1 year, 3 months
USB 4 - usb4net - do we have it yet?
by lejeczek
Hi guys.
There have been a number of newest AMD Ryzen systems (not
just laptops) with USB 4 available and I wonder....
Has anybody tried hooking up two hosts together in order to
get network over such connection?
From what I read - I think these come from Windowze
consumers - connecting two (or perhaps more) hosts via usb4
automatically creates "traditional" network connection.
Now, automatically or not - do we have that in
Linux/kernel/Fedora too?
many thanks, L.
1 year, 3 months
F37 update
by Paolo Galtieri
Folks,
I got the following error during an update to F37
Cloning into 'vmware-host-modules'...
fatal: Remote branch workstation- not found in upstream origin
/etc/kernel/install.d/99-vmmodules.install: line 20: cd:
vmware-host-modules: No such file or directory
make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target 'install'. Stop.
warning: %posttrans(kernel-core-6.0.15-300.fc37.x86_64) scriptlet
failed, exit status 2
Error in POSTTRANS scriptlet in rpm package kernel-core
This is the output of cat /etc/vmware/config
cat /etc/vmware/config
.encoding = "UTF-8"
installerDefaults.componentDownloadEnabled = "yes"
installerDefaults.autoSoftwareUpdateEnabled.epoch = "8066165664"
installerDefaults.dataCollectionEnabled.epoch = "9436500008"
installerDefaults.transferVersion = "1"
installerDefaults.autoSoftwareUpdateEnabled = "yes"
product.name = "VMware Workstation"
telemetryUUID = "b0e8b526-887e-11e9-b472-4cd98f6d8721"
acceptEULA = "yes"
acceptOVFEULA = "yes"
installerDefaults.dataCollectionEnabled = "no"
installerDefaults.dataCollectionEnabled.initialized = "yes"
VMware workstation was uninstalled on this system yet some parts remained.
Paolo
1 year, 3 months
Two minor issues after dnf upgrade from 35 to 36?
by Michael D. Setzer II
The actual upgrade process went fine to a point.
Downloaded the files fine.
Did the reboot to install, and that went fine.
Issue here. It rebooted after completing upgrade, but at
that point have a totally black screen. After a while
monitor comes up with a no vga signal, and touching
keyboard would not do anything?
Device is:
01:00.0 VGA compatible controller: Advanced Micro
Devices, Inc. [AMD/ATI] Turks GL [FirePro V3900]
Fortunately, system is setup to run vncserver on boot,
and was able to vnc into machine, and it was actually
working just fine, but just no VGA output?
Did a systemctl reboot, and this time the grub menu
appeared and the regular boot process and login screen
happened, so appeared to only be issue on boot after the
upgrade?? No clue why. Know it is an old PCI card, and
might be that it somehow was not using the VGA port but
the DVI port on card that I don't have a cable or monitor
on.
The other issue was very minor. Checked the wine
version afterwards, and found it hadn't updated the
winehq version to the latest Fedora 36 files. Checked the
/etc/yum.repos.d/winehq.repo and it was still showing 35
instead of 36. Just modified it manually, and then ran dnf
update and it installed the latest files.
Don't know if that would be an issue with dnf upgrade or
something with winehq or is just that one is suppose to
manually update it.
Thanks.
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor
(Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
1 year, 3 months
Lost NFS Export
by Jonathan Ryshpan
The machine OaklandWeather is set up to export some directories to the
machine amito. But when OaklandWeather is restarted the export is lost.
Running "# exportfs -a" restores the export and the desired files can be
seen by amito.
Some Details:
root@OaklandWeather# cat /etc/exports
# /etc/exportfs created by Jon : Fri 2021-11-05 02:33:51 PM PDT
# edited by Jon : Tue Nov 16 10:30:08 AM PST 2021
# / amito(rw,no_subtree_check,no_root_squash)
/ amito(rw)
/home amito(rw)
The problem seems to happen because nfs is started before amito can be
resolved:
Nov 07 07:37:42 OaklandWeather.localdomain systemd[1]: Starting nfs-
server.service - NFS server and services...
Nov 07 07:37:42 OaklandWeather.localdomain exportfs[1074]: exportfs:
Failed to resolve amito
When OaklandWeather is running, amito can be resolved without
difficulty:
[jonrysh@oaklandweather ~]$ ping amito
PING amito(fe80::eaa3:138b:df4f:7e60%enp4s0) 56 data bytes
64 bytes from fe80::eaa3:138b:df4f:7e60%enp4s0: icmp_seq=1 ttl=64
time=0.739 ms
System Info
Operating System: Fedora Linux 36
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.6
Kernel Version: 6.0.5-200.fc36.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 2 × Intel® Pentium® CPU G2030 @ 3.00GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 2500
Manufacturer: Dell Inc.
Product Name: Inspiron 660s
--
Sincerely Jonathan Ryshpan <jonrysh(a)pacbell.net>
The Website you seek
Cannot be located, but
Countless more exist.
1 year, 3 months
snapper on fedora
by Neal Becker
For several years I've been jealous of Suse for snapper. There's been a
snapper package for Fedora for some time, but I don't think it set up the
subvolumes correctly. I tried following this guide (warning: chrome
doesn't seem to like this page)
https://www.reddit.com/r/Fedora/comments/tv7wg5/comment/i393qc7/?context=3
I setup everything but not any timers - I'm not looking for automatic
periodic backups.
I had thought it would be really great to be able to undo dnf updates -
there is a python3-dnf-plugin-snapper.
But we already have dnf history undo, so no I wonder, is there really any
point?
I suppose one use is if my system became unbootable I could somehow mount a
snapshot. OTOH, I can't recall the last time I would have needed this.
1 year, 3 months
nmcli dev show eno2 question
by ToddAndMargo
Hi All,
nmcli dev show eno2
Give me tons of wonderful information about my interface.
Missing is:
network (192.168.1.0 etc.)
broadcast (192.168.1.255 etc.)
Any way to get nmcli to cough them up?
Many thanks,
-T
p.s, the "network" is not always the lowest
address in the subnet mask. At&t fiber
likes to reverse the network and the
broadcast address.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 year, 3 months
Adding file swap on btrfs
by Neal Becker
I've just installed f37 on a new lenovo x1 carbon.
One thing, the installation didn't setup any swap (other than zswap).
After a bit of reading I found
sudo btrfs filesystem mkswapfile -s 32G /swapfile
But:
sudo swapon -v /swapfile
swapon: /swapfile: found signature [pagesize=4096, signature=swap]
swapon: /swapfile: pagesize=4096, swapsize=1073741824, devsize=34359738368
Although I created 32G swapfile, only 1G is used.
swapon
NAME TYPE SIZE USED PRIO
/dev/zram0 partition 8G 6.3M 100
/swapfile file 1024M 0B -2
What's wrong?
Thanks,
Neal
1 year, 3 months