How to turn on networking from rescue boot
by vendor@billoblog.com
So... I did a "sudo dnf upgrade" and things seemed to do well.
However, when I rebooted, it hangs on bootup with the statment "Holding
until bootup processes complete" or something like that -- I'm doing
this from memory. I tried with a couple of older kernels, but they also
hung.
I assume that this is some transient thing associated with the upgrade.
Over the years, I've had glitches appear on an upgrade and disappear on
the next upgrade. Accordingly, I'd like to boot into rescue mode and
see if I can upgrade again.
However, I've forgotten how to turn on wifi networking from rescue mode.
Can anybody point me to a tutorial?
Thanks,
billo
3 years, 8 months
4.17.x kernels cause "nvme0: controller is down" on MacBook Air
by Lonni J Friedman
Ever since Fedora(27) released a 4.17.x kernel, my MacBook Air (7,1)
is no longer able to boot at all. It hangs when trying to use the
NVMe disk controller:
nvme nvme0: controller is down; will reset: CSTS=0x3, PCI_STATUS=0x810
and the entire boot process eventually times out completely. If I
return to using the last 4.16.x kernel (4.16.14-200.fc27.x86_64), then
the problem does *not* reproduce, and everything boots normally.
i opened a bug for this problem:
https://bugzilla.redhat.com/show_bug.cgi?id=1601196
however, I'm surprised that no one else has run into this issue. Any
ideas or suggestions?
thanks!
3 years, 8 months
Brother MFCL2710DW on Fedora?
by Gianluca Cecchi
Hello,
i'm replacing an Hp Officejet 4620 after print heads problems in 2 years of
life.
I got tired with inkjet and their imitations and due to my sporadic needs
and only b/w, I would like to buy a black white laserjet with scanner
capabilities too.
I see the product in object that seems quite good from an hw point of view
but it is not clear to me the status with Linux support, both with printing
and scanning.
Anyone using this product or similar one in the line?
Any suggestions?
Thanks in advance,
Gianluca
3 years, 9 months
convert to EUFI boot?
by ToddAndMargo
Hi All,
Fedora 28, x64
Two questions:
1) Is there a way to convert a Fedora hard drive that
is set up to boot off the old BIOS into a EUFI boot?
2) Is there a way to convert a Fedora hard drive that
is set up to boot off the old BIOS into a dual
BIOS and EUFI boot drive?
Many thanks,
-T
3 years, 9 months
Startup messages shown twice on EFI boot
by Richard Shaw
For some time now (i.e. multiple Fedora releases) I've noticed that on two
of my laptops that use EFI instead of BIOS booting, all of the startup
lines from SystemD are shown twice. No big issue but o a whim I decided to
google the problem and couldn't find much.
I can't be the only person that's seen this though... Any easy fix known?
Thanks,
Richard
3 years, 10 months
tip: found a flash drive for direct install
by ToddAndMargo
Hi All,
I finally found a flash drive I like for installing
Fedora directly (not live). Flash drives break down
when a lot of small files go fly around and bog
the OS down and often corrupt. I have had issues
with both Kanguru and Kingston drives.
I also test a Patriot drive. They goof around with
parameters so that large file transfers give good
numbers at the expense of small file transfers
being so bad the stick almost unusable. Fedora on
a Patriot was a joke.
On a lark I tried a Samsung MUF-64BE3/AM and a
Samsung MUF-64DA1/WW. Both are USB 3.1.
And Wow. On two customer machines running USB 2,
they preformed flawlessly. Actually even faster than
the native Windows. And no corruptions and no ten
minutes to shutdown Firefox.
On my own USB 3.0 machine, they ran almost as 1/2 as
fast as native (I have an NVMe drive).
Both these guys ate Fedora 28 Xfce x64 alive, meaning
it handled multiple small file transfers with ease.
Anyone want to know the special tweaks to run
off a USB drive, drop me a line.
-T
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3 years, 10 months
services don't start
by Mike Zingale
One of our Fedora 28 machines now longer boots. Services fail to start, and there are a lot of errors like:
[ 3881.765993] systemd[2018]: dbus.service: Failed to execute command: Permission denied
[ 3881.766884] systemd[2018]: dbus.service: Failed at step EXEC spawning /usr/bin/dbus-daemon: Permission denied
for each service. gdm or a prompt on other terminals on the machine never come up, but I can ssh into the machine.
dnf doesn't work (it gives Error: Failed to synchronize cache for repo 'updates' )
any other system commands take forever (just doing `su` or querying systemctl takes a few minutes, and then usually fails).
Any thoughts on what might be causing this?
3 years, 10 months
Regionset - a little known utility that is a globetrotter's friend
by Temlakos
Everyone:
I don't bring a question or a complaint here. I want to mention a
utility I never even knew was part of Fedora. But it is, and it's a
great boon to anyone who wants to sample DVD content from regions other
than your region of residence.
It's called: regionset.
It resets the region code of any internal /or external/ DVD
player/burner, /no matter how it's connected/. I just used it to reset
the region on a USB-connected external burner (Samsung/TSST BDDVDW
SE-506BB TS00).
Installation is a breeze. If you have the Fedora repos enabled (and,
being in this community, of course you do), execute:
sudo dnf install regionset
(Replace "sudo" with "su -c" if you're not a member of the "wheel" group.)
To use, execute:
sudo regionset /dev/dvd
where you replace "dvd" with a particular device name. (My system does
not use the dvd name. It numbers my drives sr0, sr1, etc. I used vlc to
figure out the device name.)
Make sure you load a disk in the drive before you begin! Otherwise it
will throw an error and tell you to make sure you put a readable disk in.
When you get through, you get back the make and model of the drive, the
current region code (if it has one--the SE-506BB didn't have one), how
many times the /vendor/ can change the code, and how many times /you/
(the user) can change the code. Then it asks you whether you want to
change the code or not.
If you do, then it asks you to specify a region (1 through 8, according
to convention) and confirm twice. (The second confirmation shows you the
proper "back mask." Second-guessing that is an advanced concept.) If
successful, it will confirm that for you.
What does that mean? Well, if you're used to traveling extensively and
picking up optical media along the way, you need to do one of two things:
1. Shell out big bucks (or quid or euros or whatever) to buy a
multiregion player. (Do /not/ bother with the old region-free players!
Studios are wise to that and now encrypt their disks so that they will
play in one region and /only/ one region. If your player doesn't have
the code to match, you're out of luck. Which is why I /had to/ set the
region on my SE-506BB to play anything other than a Region 1 disk. But
some of the new players will read the region code on the disk and adapt
to it pro-actively.)
2. Have at least one drive available so that you can reset its region.
Depending on how many regions you regularly visit, I'd recommend buying
as many external USB drives as you have regions (other than your home
region) you travel to, setting one for each region, and labeling them.
Problem solved.
Of course if you travel the whole world, you might as well get one of
those standalone multi-region machines. Beyond a certain point, you'll
pay more for the extra drives than for one device. (Except for one
thing: when you're on the road, those little portable drives are a lot
easier to carry, and to power up, than a big monster you have to lug
around and entrust to non-gentloe baggage handlers and customs officers!)
I don't do that. I use disks from Regions 1 and 2. (Some titles aren't
available in Region 1, and my retailer will import them.) I then /rip/
the disks so I have the playable files on hand. But: /to do that, I
needed a drive set to Region 2 to rip my Region 2 material/.
Now I have that. And I just used MakeMKV to rip a Region 2 disk.
Success.
Temlakos
3 years, 10 months
Software to create bootable USB stick
by Danny Horne
Hi all,
I'm running Fedora Workstation 28. What software can I use to install a
downloaded OS .ISO onto a USB stick so the OS can be installed on
another machine?
Thanks for looking
3 years, 10 months
[F28] dnf upgrade -> failure to remove sssd-libwbclient-devel and
other errors
by Frédéric
Hi,
I have just upgraded one of my F28 systems and got many errors, in
particular related to sssd-libwbclient-devel (failed to remove),
chromium (value error) and kernel (failed to remove 4.17.12). Below is
an exerpt of the log (sorry, it's in French).
Is this a problem? Is my system corrupted now?
Kind regards,
F
# dnf upgrade -y
Dernière vérification de l’expiration des métadonnées effectuée il y a
0:48:33 le mer. 29 août 2018 20:46:25 CEST.
...
Téléchargement des paquets :
...
[MIRROR] kolourpaint-18.04.3-1.fc28.x86_64.rpm: Curl error (56):
Failure when receiving data from the peer for
http://ftp.lip6.fr/ftp/pub/linux/distributions/fedora/updates/28/Everythi...
[Recv failure: Connection reset by peer]
[MIRROR] ktouch-18.04.3-1.fc28.x86_64.rpm: Curl error (56): Failure
when receiving data from the peer for
http://ftp.lip6.fr/ftp/pub/linux/distributions/fedora/updates/28/Everythi...
[Recv failure: Connection reset by peer]
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total
1.4 MB/s | 669 MB 08:08
Delta RPMs a réduit la taille des mises à jour de 753.2 Mio à 668.9
Mio (11.1% économisés)
Test de la transaction en cours
La vérification de la transaction a réussi.
Lancement de la transaction de test
Transaction de test réussie.
Exécution de la transaction
...
Mise à jour de : chromium-68.0.3440.106-3.fc28.x86_64
173/567
Exécution du scriptlet: chromium-68.0.3440.106-3.fc28.x86_64
173/567
ValueError: File context for /usr/lib/chromium-browser already defined
ValueError: File context for
/usr/lib/chromium-browser/chromium-browser.sh already defined
ValueError: File context for /usr/lib/chrome-sandbox already defined
Mise à jour de : geogebra5-5.0.488.0-636770.x86_64
264/567
Exécution du scriptlet: geogebra5-5.0.488.0-636770.x86_64
264/567
/var/tmp/rpm-tmp.MPdKp1: ligne 1: /usr/local/bin/update-mime-database:
No such file or directory
...
Suppression de :
kmod-nvidia-340xx-4.17.12-100.fc27.x86_64-1:340.107-2.fc27.x86_64
331/567
Exécution du scriptlet:
kmod-nvidia-340xx-4.17.12-100.fc27.x86_64-1:340.107-2.fc27.x86_64
331/567
Exécution du scriptlet: sssd-libwbclient-devel-1.16.3-1.fc28.x86_64
332/567
/var/lib/alternatives/libwbclient.so-64 est vide !
erreur : %preun(sssd-libwbclient-devel-1.16.3-1.fc28.x86_64) scriptlet
échoué, état de sortie 2
Error in PREUN scriptlet in rpm package sssd-libwbclient-devel
Error in PREUN scriptlet in rpm package sssd-libwbclient-devel
Nettoyage de : perl-Pod-Perldoc-3.28-396.fc28.noarch
333/567
erreur : sssd-libwbclient-devel-1.16.3-1.fc28.x86_64: effacer échoué
...
Suppression de : kernel-devel-4.17.12-100.fc27.x86_64
504/567
Exécution du scriptlet: None
505/567
/var/lib/alternatives/libwbclient.so-64 est vide !
erreur : %preun(sssd-libwbclient-devel-1.16.2-4.fc27.x86_64) scriptlet
échoué, état de sortie 2
Error in PREUN scriptlet in rpm package sssd-libwbclient-devel
Error in PREUN scriptlet in rpm package sssd-libwbclient-devel
Nettoyage de : pango-1.42.3-1.fc28.i686
506/567
erreur : sssd-libwbclient-devel-1.16.2-4.fc27.x86_64: effacer échoué
Exécution du scriptlet: pango-1.42.3-1.fc28.i686
506/567
...
Nettoyage de : geogebra5-5.0.486.0-635380.x86_64
510/567
Exécution du scriptlet: geogebra5-5.0.486.0-635380.x86_64
510/567
/var/tmp/rpm-tmp.ibufyA: ligne 1: /usr/local/bin/update-mime-database:
No such file or directory
...
Exécution du scriptlet: kernel-core-4.17.12-100.fc27.x86_64
528/567
Suppression de : kernel-core-4.17.12-100.fc27.x86_64
528/567
attention : fichier /lib/modules/4.17.12-100.fc27.x86_64/updates :
échec de la suppression : No such file or directory
...
Exécution du scriptlet: sssd-libwbclient-devel-1.16.3-2.fc28.x86_64
567/567
/var/lib/alternatives/libwbclient.so-64 est vide !
attention : %posttrans(sssd-libwbclient-devel-1.16.3-2.fc28.x86_64)
scriptlet échoué, état de sortie 2
Non-fatal POSTTRANS scriptlet failure in rpm package sssd-libwbclient-devel
Non-fatal POSTTRANS scriptlet failure in rpm package sssd-libwbclient-devel
...
Vérification de : sssd-proxy-1.16.3-1.fc28.x86_64
524/566
sssd-libwbclient-devel-1.16.3-1.fc28.x86_64 est censé être supprimé,
mais ne l’est pas !
Vérification de : sssd-libwbclient-devel-1.16.3-1.fc28.x86_64
525/566
Vérification de : sssd-nfs-idmap-1.16.3-1.fc28.x86_64
526/566
...
Échec:
sssd-libwbclient-devel.x86_64 1.16.3-2.fc28
Erreur : La transaction a échoué
3 years, 10 months