Ask Your Question

pgueckel's profile - activity

2018-07-27 07:00:18 -0500 received badge  Notable Question (source)
2018-07-27 07:00:18 -0500 received badge  Popular Question (source)
2017-04-13 17:22:27 -0500 asked a question WiFi: RTL8821ae frequent loss of connectivity

I have been experiencing frequent loss of connectivity with the built-in Realtek8821ae Wireless Adapter. This began in Fedora 25, starting about a month ago, with the last of the 4.9 series of kernels. I have since migrated to Fedora 26, where the 4.11 series kernels are in use, and the problem still persists.

I have filed a bug report on bugzilla, #1435793, but there has been no response.

The wireless cuts out anywhere from about every 5 seconds to about every 2 minutes, rendering it nearly impossible to use.

I have spent countless hours researching and, last night, discovered this report, which confirms both the bug and the existence of a patch!

https://github.com/lwfinger/rtlwifi_n...

After reading it sketchily, I have been using the following commands to reset the wireless to allow me to use it with some modicum of comfort:

sudo modprobe -r rtl8821ae;sudo modprobe rtl8821ae ips=1

While I haven't read the article thoroughly and cannot confirm that this is the best work-around or even that this is indeed suggested in the article ;-) it has provided some relief, but it is not a solution. [I am scanning the article as I am writing and I see that someone suggests ips=0 as a solution; I have not yet tried this. Further down, another user has conflicting results.]

The only solution would appear to be to have the patch applied to the kernels in use in Fedora 26. There were lots of commits on this regression and the consensus among users is that the problem is solved—but not on Fedora!

How can we get this working on Fedora 26?

2017-01-14 11:23:12 -0500 received badge  Popular Question (source)
2016-05-08 08:32:58 -0500 received badge  Nice Question (source)
2016-05-07 20:38:28 -0500 asked a question TPM error 1 on Fedora 24 beta forces grub rescue impasse

I installed Fedora-Workstation-24-20160506.n.0 (24ß) on my laptop. I have used this laptop for nearly 10 years for Fedora without problem. Today, I have encountered a major one.

When I boot the computer with the newly installed system, instead of the grub menu, a message "TPM error 1" appears and beneath it the grub rescue prompt. I have gone into the BIOS and disabled the TPM, then restored the factory setting, then enabled it, then reloaded the certificate (or whatever it is) and so on. I have tried combinations of all available TPM settings. I have been unable to get any result with grub rescue either. I suspect that TPM is blocking access to grub and preventing access to the contents of the drives. I have been unable to discover the means to disable or bypass it. I even reinstalled the OS all over again.

Still, I am unable to gain access to the grub menu or boot the computer.

2016-04-22 06:01:11 -0500 received badge  Famous Question (source)
2016-04-22 06:01:11 -0500 received badge  Notable Question (source)
2016-04-22 06:01:11 -0500 received badge  Popular Question (source)
2015-10-07 15:17:52 -0500 received badge  Student (source)
2015-07-23 18:05:59 -0500 received badge  Famous Question (source)
2015-07-23 18:05:59 -0500 received badge  Notable Question (source)
2015-03-27 11:40:59 -0500 marked best answer pam.d/*.rpmnew on first update

I installed Fedora 20ß from the DVD. The files:

/etc/pam.d/password-auth /etc/pam.d/postlogin /etc/pam.d/system-auth

were either copied to my system from the DVD or generated by the installer. They are all dated November 14 2013.

When I updated the system on my first login, password-auth.rpmnew, postlogin.rpmnew and system-auth.rpmnew were created. Obviously, they are different from the original files. These files are all dated October 14, 2013. They are one month older than the files from the DVD, even though they come from the updates.

Which version of the files should I keep?

2015-03-24 11:49:41 -0500 received badge  Famous Question (source)
2015-03-24 11:49:41 -0500 received badge  Notable Question (source)
2015-03-24 11:49:41 -0500 received badge  Popular Question (source)
2014-12-18 20:05:19 -0500 edited question firefox causes high internet traffic

In Fedora 21, I noticed that firefox was using so much internet bandwidth, that pages would not load or only partially load. I could barely access local news sites, Amazon, not even google, without having to reload the page. Transmission was that slow! This went on for one to two weeks, when I finally noticed that the internet LED on the router/adsl modem was continually flashing wildly and at high rate, indicating data transmission, even when I wasn't loading any pages in firefox. Even the start page was causing this, but as soon as I shut firefox down, it stopped.

I finally solved the problem myself. It was the new tab page in firefox that was constantly trying to update all of the tabs. This took so much bandwidth, that I was almost unable to surf the web! I tried setting the new tab page setting from enhanced to classic, but it persisted, so I set it to blank and... voilà! The browser functions normally again.

I am now able to surf and pages load speedily and without problems.

2014-09-30 20:12:31 -0500 commented question How To Get Correct Framebuffer and Display Manager Resolution?

xorg.conf hasn't existed since about Fedora 14 or so ;-) There might be a way to specify a primary monitor in /etc/X11/xorg.conf.d/ but I don't know how to do it. Any ideas? And is this really necessary? Shouldn't the system automatically be able to 'see' that the television (HDMI1) is not even turned on?

2014-09-30 09:18:01 -0500 commented question How To Get Correct Framebuffer and Display Manager Resolution?

Fedora 20.

2014-09-29 22:44:32 -0500 asked a question How To Get Correct Framebuffer and Display Manager Resolution?

I use Intel onboard graphics, which supports the resolutions of both of my monitors:

  1. VGA LCD Monitor, 1280x1024, shown as VGA1 by xrandr
  2. HDMI LED Television, 1920x1080, shown as HDMI1 by xrandr

Both moitors are plugged in, but the VGA is always turned on when I'm using the computer; the HDMI is only turned on when I want to use the large screen. I can switch from one monitor to the other, but I haven't gotten display on both at the same time, but that is not what I am asking presently, but wouldn't mind knowing how :-)

Here is the problem:

When I boot the computer with only the VGA monitor connected, everything is fine. However, when I have both monitors connected while booting (even when the HDMI monitor is powered off), then plymouth always starts in 1920x1080 resolution. When the boot process has completed and the display manager arrives (GDM), there is nothing/only greyness visible on my 1280x1024 LCD monitor. I can move the mouse way beyond the visible screen and I am able to log in by first hitting enter and then typing my password, but I am unable to see the GDM menu. If I disconnect the HDMI LED monitor, then the screen resolution immediately shrinks to 1280x1024 and all looks fine.

Why can I not boot the computer (and get 1280x1024 resolution) with both monitors plugged in (when the secondary HDMI monitor is not even powered on)? Is there way to tell grub2/the system that the VGA monitor is the default and that the HDMI monitor should only be used when I expressly switch to it? Must I constantly unplug the HDMI monitor when I boot the computer? There has to be a more elegant way to manage a computer with two monitors.

2014-04-27 17:37:58 -0500 received badge  Supporter (source)
2014-04-27 03:53:40 -0500 received badge  Popular Question (source)
2014-04-27 00:53:59 -0500 commented answer cron job output no longer in systemd journal (or sSMTP barges in)

I erased ssmtp and smartmontools (I don't use either). I also edited /etc/sysconfig/crond and now the output shows up in the systemd journal and there is no more ~/dead.letter. I am not sure if the last step is essential, but it is all back to how I want it.

2014-04-27 00:48:10 -0500 commented question cron job output no longer in systemd journal (or sSMTP barges in)

Thanks to both of you!

2014-04-26 19:00:51 -0500 asked a question cron job output no longer in systemd journal (or sSMTP barges in)

In Fedora 20, we no longer have an MTA, such as sendmail. Yay!

I have been running a nightly backup script as a user cron job. Everything has been going fine, until last night, when I noticed that the backup script is still running fine, but that there is now a dead.letter file (owned by mail:me) in my home directory.

I recall that shortly after installing Fedora 20 a few months ago, I checked the systemd journal and the cron messages were showing up there. I assumed that this was the default and this is what I want. I just checked the journal and it now shows:

Apr 26 17:15:12 desk.home sSMTP[18062]: Unable to locate mail
Apr 26 17:15:12 desk.home sSMTP[18062]: Cannot open mail:25
Apr 26 17:15:12 desk.home CROND[18058]: (me) MAIL (mailed 613 bytes of output but got status 0x0001

Why is this suddenly happening? How can I go back to the former behaviour?