Updating to the new kernel temporarily knocked out my wireless
connectivity on my Dell Inspiron 1545.
That is, until I executed:
# modprobe b43
Or, since I am a member of "wheel":
$ sudo modprobe b43
A few seconds after I issued that command, wireless was enabled, and the
connection I had long been using, re-activated itself.
Question: must I execute "modprobe xxx" with every kernel upgrade?
(By the way: it turns out that module "wl" is not necessary.)
On 07/01/2014 01:58 PM, Paul Cartwright wrote:
> On 07/01/2014 01:32 PM, Temlakos wrote:
>> # echo b43 >> modules
>> while is directory /etc
>> Now I have a file called "modules" with the line "b43" in it.
> I had to do that very thing for my Uncle... I showed him how to do the
> "modprobe b43" but he is 80 years old... so I found this to make it
> permanent & it did work..
The problem is: it doesn't seem to work for me. When I reboot, the
machine does not mention wireless at all. Not, that is, until I execute
"sudo modprobe b43" from a regular user prompt. Then it finds the
connection at once.
PS: next I'm going to try to load "wl" first, then "b43" and see what
I ran yum -y update.
After all the files were downloaded, the delta processing started. From
there on, all the way through to the end of
installation and cleanup, cpu was 99.99% taken up
by the update process, and the entire desktop became
unresponsive. I was unable to switch display windows,
of which I had 6.
The update had downloaded a total of 161MB, for a total
of about 30 updates, most of them wine related.
The machine is a dual core Intel running at 2.4GHz,
with 4GB ram.
When I run /sbin/system-config-services
I see that iptables is enabled, and that
/etc/sysconfig/iptables contains the rules
However, after bootup, I open a terminal and
run iptables -L -n
and do not see those rules at all, and all
the rules are in "ACCEPT" state.
I have to resort to start iptables manually
in order to install the rules I have in
So, what needs to be done to force iptables to run
and to use the rules I have in the iptables file?
Using f20, gnome3.
Appears to be a bug in dconf-editor-0.18.0-2.fc20.
org->gnome->desktop->wm->preferences: *auto-raise* has no effect.
Targeted window receives focus but doesn't raise to the top when mouse
or sloppy is selected.
If somebody else verifies it I'll bz it.
The latest updates--pushed yesterday--cause the touchpad on my Dell
Inspiron 1545 to run v-e-r-y s-l-o-w.
It was so bad, I tried to reinstall Fedora.
At first the reinstall restored the swift movement of the touchpad pointer.
But as soon as it took the updates, everything slowed down once again.
When I run in Setup, the touchpad cursor moves swiftly. But not when
Fedora is loaded.
What a time for this to happen. I simply cannot use it for any kind of
presentation in the shape it's in.
What package might I possibly be able to roll back until somebody fixes
f20 fully updated. Not using NetworkManager.
There are an assortment of interfaces and bridges defined in my
network-scripts/ifcfg files. The interfaces come up but the bridges
don't. I have to manually restart networking to bring the bridges up
and bind the interfaces to them.
This had been working up through f18 (didn't try f19).
Any ideas on how to get them to be created on boot or why they don't?
Is this a candidate for a bug report?
Thanks for any help,