On 01/14/2018 02:22 PM, Ed Greshko wrote:
After all this time, I was able to return to my friend's laptop and I
On 01/15/18 05:19, Ed Greshko wrote:
kernel-devel x86_64 4.14.13-300.fc27 updates 12
kernel-headers x86_64 4.14.13-300.fc27 updates
Note these packages are from updates. If the laptop system hasn't been updated
dnf --disablerepo updates --downloadonly --downloaddir=/tmp install broadcom-wl
kernel-devel x86_64 4.13.9-300.fc27 fedora
kernel-headers x86_64 4.13.9-300.fc27 fedora
with all the rpms outlined by Ed.
They all installed, albeit, with the command option --disablerepo=*
They all installed, (from external disk), and I rebooted.
Network came up. I thought I was out of the woods and into
a well mapped world.
I did the update, and all the packages updated.
No problems. I did a clean shutdown.
That was yesterday.
Today, I powered up the machine, and it proceeded to do fsck!!!!
But I had done a clean install and a clcean shutdown!!!
After fsck, I rebooted.
AGAIN - machines started to do fsck.
I waited, did another clean shutdown.
AGAIN the machine ran fsck....
How in tarnation can I put an end to this?
I had not experienced this on other machines running older
versions of fedora.
OK... that was the first problem today,
Network will not come up!!!! :( :( :(
I checked to make sure all the rpm packages that brought up the network
were still there.
And indeed they are.
Yet the network will not come up :(
I have to admit that I had not set up a proper firewall yesterday.
The machine's firewall was still in it's "first install state" and I
assume in a "promiscuous" configuration.
I do not know, I am only guessing what could have happened and by what
So, how do I proceed now?
Should I re-install the rpms that first brought up the machine's wifi?
users mailing list -- firstname.lastname@example.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org