Using kernel 5.19.8 does not boot
by dwoodyard@rdwoodyard.com
I am attaching a screen shot to show part of the boot process...
I have searched google the fedora sights with no results.
I have been using 5.18.10
Anybody have any ideas?
Thanks,
David
1 year, 9 months
Restarting pipewire
by Patrick O'Callaghan
After a recent update, tracer said I should restart pipewire:
$ sudo tracer -a
You should restart:
* These applications manually:
pipewire
pipewire-pulse
Logging out and in had no effect, nor does there appear to be a systemd
unit installed:
$ systemctl |grep pipewire
$
Although there are unit files in the RPM:
$ rpm -ql pipewire|grep service
/usr/lib/systemd/user/filter-chain.service
/usr/lib/systemd/user/pipewire.service
/usr/lib/systemd/user/filter-chain.service
/usr/lib/systemd/user/pipewire.service
The man pages for pipewire, pipewire.conf, pw-cli and pw-mon are not
helpful.
Any ideas?
poc
1 year, 9 months
Question on bad links?
by Michael D. Setzer II
I've run this little script from time to time in /
find . -xtype l >/badlinks 2>ERR
grep -v '/proc\|/run' </badlinks >/badlinks-clean
At present ends up with other 300 lines in the
badlinks-clean
Cleaned up a number of bad lines in a jre directory that
seemed to be left over stuff from fc27 to fc33? Nothing
from fc34?? and the reset were the currect fc35 files I
have on system. Seems things that just got left??
Not sure if it is coming to have these on a system?
Wonder if someone with a lot more knowledge than I
have might know best option. Just leave them, remove
some, remove all? Figured the ones in /proc and /run
should be left alone??
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, 9 months
firmware: linux-firmware depends on intel-gpu and nvidia-gpu
by Adrian Sevcenco
Hi! Does anyone know why linux-firmware depends on intel-gpu
and nvidia-gpu? and if this can be bypassed?
I have an amd only desktop and is kind of annoying that i need
also intel and nvidia firmware..
I imagine that the reason is to allow the os to run on whatever
hardware is present or changed, but is there a way to allow user to
customize somehow the presence of unneeded firmware?
Thanks a lot!
Adrian
1 year, 9 months
FYI: Microsoft broke secureboot in qemu-based VMs
by Sam Varshavchik
It is possible to run qemu VMs that emulate EFI and secureboot well enough
for Windows to boot.
This is still true, technically. Windows will boot. But it will not update
reliably anymore. Microsoft broke it, ostensibly for "security reasons".
Microsoft released a Windows update that will not install on qemu EFI VMs:
https://www.bleepingcomputer.com/news/security/windows-kb5012170-secure-b...
dbx-update-may-fail-with-0x800f0922-error/
I was scratching my head, trying to figure out why this update won't
install. A search on the cryptic error code brought up some random crap that
wasted a ton of my time, doing things like resizing my system partition,
almost bricking my VM (typical MS-Windows noise). Only after I got the
bright idea of searching for both the error code and the update code itself
did I find this article, and digging further found this:
https://github.com/tianocore/edk2/discussions/3221
There's still a lot of things I don't understand. What is being blacklisted,
exactly, here. The OVMF RPM – to the best of my understanding – is
emulated hardware. How does running some PowerShell voodoo end up updating
(emulated) hardware? And if it's not a magical hardware update, yammers
about an update to the bootloader on the EFI system partition. Except that
(at least in my case), the bootloader should be Microsoft's own bootloader,
since I used Micorosoft's own tools to convert my BIOS Windows VM to an EFI
one (mbr2gpt, that's how I was able to get a working EFI Windows VM).
But the bottom line: this is now broken. Just an FYI…
1 year, 9 months