Re: WiFi conflicting with Bluetooth
Allegedly, on or about 23 July 2016, Chris Murphy sent: > Thing is, I don't see this same behavior on macOS with the same > hardware and environment: I don't see the constant > disconnects/reconnects, and I don't ever have BT problems. Looking at a couple of WiFi/bluetooth de-snaggling pages, I was (a) surprised to learn that the two were in the same RF neighbourhood, that seems like bad planning, and (b) see that either technology *can* use some automation to avoid congested channels. Perhaps your Mac *is* discovering and avoiding problem frequencies with the bluetooth. The various other solutions offered won't be do-able by everyone. You can't always change the position of wireless and bluetooth devices, since they're fixed inside the chassis of things, unless you're using a USB dongle. But moving the position of everything to change a reception pattern may be possible, and you might only have to move something an inch to move it out of a dead zone, or out of somewhere that received interference. Changing USB cables around may help, some are poorly shielded and radiate interference. And if you're prone to external interference (microwave ovens, video transmitters, cordless phones), you *may* not be able to do anything about them, certainly not if they're not yours. Video transmitters often have a frequency selector switch, I know I have one with the opposite problem (it's disrupted badly by WiFi). And maybe moving a cordless phone base station could change things. -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 Boilerplate: All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I only get to see the messages posted to the mailing list. This email brought to you by potato omelates: Cut three medium-sized potatoes into pieces, and boil them for ten minutes, then smash them (that's mash them only once, so they're a bit chunky). Stir up four eggs, like you're going to make scrambled eggs. Mix potatoes and eggs together. Melt a large lump of butter in a frypan. Slowly fry (turn the flame down low) small helpings until golden brown. Replenish the butter as you go along, don't burn the butter. Tip out any butter that's starting to burn, as you go along. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Date change on reboot
My F22 randomly crashes to a frozen state that requires a power cycle to restart. When this happens, the time stamp on log files such as /var/log/messages changes for a while before reverting to the correct date and time. Today,the sequence was: Jul 24 10:55:55 mustang rsyslogd: [origin software="rsyslogd" swVersion="8.8.0" x-pid="853" x-info="http://www.rsyslog.com";] start Jul 15 11:19:20 mustang systemd: Stopped target Default. Jul 15 11:19:25 mustang systemd: Stopping Default. followed by some 17,000 lines with Jul 15 through to: Jul 15 19:28:11 mustang named[1221]: client 122.61.143.143#39431 (isc.org): query (cache) 'isc.org/ANY/IN' denied Jul 24 10:56:14 mustang rsyslogd-2177: imjournal: begin to drop messages due to rate-limiting Sun Jul 24 10:56:16 ACST 2016 rc.fw Jul 24 11:06:11 mustang rsyslogd-2177: imjournal: 2971956 messages lost due to rate-limiting A similar thing happens in /var/log/secure (though with fewer Jul 15 entries). The Jul 15 dates have been appearing at/after the last two or three crashes. Even though the Jul 15 entries look to span over eight hours, the actual time span was only a minute or so. Any suggestions as to what is happening here? Cheers and thanks, Stephen -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: gnome fc22 fc24
On Sat, Jul 23, 2016 at 7:45 AM, Patrick Dupre wrote: > Hello, > > Is the gnome environment compatible between fc22 and fc24 ? > In other words, can a user run back in fc22 other an update have been > in fc24 ? My expectation is once you go to Fedora 24, any new applications that touch their own settings files can update them in a way that's not backwards compatible. So it might work but chances are it'll confuse the older versions. -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F24 gedit and large text files, background becomes black
On Sat, 23 Jul 2016 21:43:07 -0600 Chris Murphy wrote: > I'm having myriad problems with gedit and large text files. OK 81MB > isn't really that large, it should be able to handle that without this > much difficulty. > > First, it takes a long time to open, more than a minute, and this is > on an SSD. Next, it's doing some processing for a really long time > after it loads the document, about 5-6 minutes, while the process > consumes 100% CPU and the fans start running on high like I'm blowing > my hair dry rather than reading a document. > > But the actual problem is, at some point I click out of gedit, then > back into gedit, and somehow the white background becomes black. So > it's a sea of black text on a black background and thus totally > useless. > > Can anyone else reproduce this? > > https://bugzilla.redhat.com/show_bug.cgi?id=1359476 > > I don't think there's anything magical about it being 81M. I don't > have this problem though with smaller files in the 1MB or less range. > I just don't know at what threshold it becomes a problem. I don't normally use gedit, but I fired it up on a text file that is about 118 MB. It quickly shows the initial screen, but then seems to lock up the screen. When I look in top, it's using 100% of one CPU. But it isn't really using a lot of memory. The text shows as white on a black background. When I switch to a different workspace and back, the screen is completely black until I move the mouse, then it shows up as white on black. I see that there is a progress bar at the top of the screen, and it is moving very slowly, about the rate you reported. So, yes, it appears that if I was using gedit I would have the problem also. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Timeline of a Fedora-24/KDE reboot
Another option: sync && reboot -f sync && poweroff -f That's if you don't want to troubleshoot this, or logout first. I've actually been doing a lot of just 'reboot -f' for the past year or so, without sync, to no ill effect. But I'm also using Btrfs, use no databases, and pretty much have no important data on this system. So... you might not want to do this, or at least use sync first. For sure any documents you haven't saved you'll lose because it's an ungraceful kernel level reboot, your DE and its applications won't ask, you'll get a reboot in about 1-2 seconds. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Timeline of a Fedora-24/KDE reboot
On Sat, Jul 23, 2016 at 8:43 AM, Timothy Murphy wrote: > As you will see, there is a long delay (90 seconds or so) > while shutting down. > If anyone can throw light on this I should be very grateful. If it's exactly 90 seconds, that sounds like the user session is hung up, something isn't quitting, systemd is waiting for it, and there's a 1m30s timeout for user sessions to get killed off. And then the reboot/shutdown happens. Here's the bug I filed for this on GNOME. https://bugzilla.redhat.com/show_bug.cgi?id=1337307 And with KillUserProcesses=yes, it still doesn't get killed. https://bugzilla.redhat.com/show_bug.cgi?id=1341837 What does appear to work, is if I logout first. That kills user processes. And then from the login screen, a restart/shutdown happens quickly. > > This is the re-boot timeline on my Thinkpad T510: > > f=>Leave=>Restart command given and confirmed > 19s just cursor on screen > f icon appears and remains on screen > 114s > Thinkpad icon appears > 14s automatic choice of kernel > bulb appears and slowly fills > 25s > login screen - after logging in > 5s > K icon appears and horizontal bar fills > 30s > panel appears > > It will be seen that there is a long delay (almost 2 minutes) > while shutting down. > > I see from "journalctl -b-1" that the delay occurs here > -- > Jul 23 14:11:38 william.gayleard.com NetworkManager[908]: > [1469275898.3807] device (wlp3s0): > supplicant interface state: completed -> disconnected > Jul 23 14:11:41 william.gayleard.com wpa_supplicant[1061]: > wlp3s0: Reject scan trigger since one is already pending > Jul 23 14:13:02 william.gayleard.com NetworkManager[908]: > [1469275982.5130] connectivity: check for uri > 'http://fedoraproject.org/static/hotspot.txt' failed wit > Jul 23 14:13:05 william.gayleard.com systemd[1]: session-1.scope: > Stopping timed out. Killing. > Jul 23 14:13:05 william.gayleard.com systemd[1]: > Stopped Session 1 of user tim. > -- > > Is the delay due to the timeout mentioned? > I am not good at interpreting the output of journalctl. If you login remotely with ssh, you should be able to do 'lsof /home' and get an idea of what's holding onto home. You can also use loginctl to get a list of sessions and also 'loginctl session-status ' to get a list of stuff that's still running. One of those is the culprit. You could try to kill them in reverse order of PID and see if that releases the user session. The last one you do right before your shell session is killed is probably the culprit. Thing is, for a pile of reasons, programs lurk around and don't quit when they should and it's not always their fault as I understand it. -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
F24 gedit and large text files, background becomes black
I'm having myriad problems with gedit and large text files. OK 81MB isn't really that large, it should be able to handle that without this much difficulty. First, it takes a long time to open, more than a minute, and this is on an SSD. Next, it's doing some processing for a really long time after it loads the document, about 5-6 minutes, while the process consumes 100% CPU and the fans start running on high like I'm blowing my hair dry rather than reading a document. But the actual problem is, at some point I click out of gedit, then back into gedit, and somehow the white background becomes black. So it's a sea of black text on a black background and thus totally useless. Can anyone else reproduce this? https://bugzilla.redhat.com/show_bug.cgi?id=1359476 I don't think there's anything magical about it being 81M. I don't have this problem though with smaller files in the 1MB or less range. I just don't know at what threshold it becomes a problem. -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 24 and PNY SSD Problems
On 07/23/2016 06:04 AM, Gregory P. Ennis wrote: I went to Fry's yesterday to pick up SATA controller card and the Fry's expert told me that their SATA controllers did not work with Linux. That seems very unlikely, most (all?) controllers are supported. I haven't heard of one not working for many years. Find out what chipset they use. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 24 and PNY SSD Problems
On Sat, Jul 23, 2016 at 08:04:42AM -0500, Gregory P. Ennis wrote: > > On Sun, Jul 17, 2016 at 08:45:13AM -0500, Gregory P. Ennis wrote: > > > > Everyone, > > > > I am trying to reclaim some use out of a couple old Compaq Presaio > > SR1720NX machines for the office by adding some memory and a PNY 240 > > GB > > CS1311 SSD drives. The bios was made by Phoenix; I did not identify > > a > > version number of the bios. I did not plan on keep the hard drive > > installed and planned on just using the SSD. These machines were IDE > > machines and only had two SATA ports on the motherboard. > > > > When I install the SSD the bios recognizes the Pny SSD properly, and > > I > > was able to set up the boot order without difficulty. > > > When I had to replace the MB of a similar, older system, I used a non- > HP MB. > Later when I wanted to beef it up, the new MB only had 2 SATA ports and > I wanted to install more drives. So I purchased a really cheap SATA > controller card. > > I got a store-brand SSD and to my surprise the MB controller did not > see it but the cheap controller did. Blaming the store-brand SSD, > I returned it and got a Crucial SSD. Same problem though. So it > was the controller, not the SSD. MB controller worked fine with > other SATA drives, but not with the SSD. > > Jon > -- > > Jon, > > I went to Fry's yesterday to pick up SATA controller card and the Fry's > expert told me that their SATA controllers did not work with Linux. > Can you look up the name of the SATA card that you used and publish > it. > > Thanks, > > Greg Silicon Image SiL 3124 PCI-X SATA RAID Controller When I ran the simple "hdparm -t" tests on the same convevtional disks the add-in controller had about 75% the performance of the MB controller. jon -- Jon H. LaBadie jo...@jgcomp.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: sign_and_send_pubkey: signing failed: agent refused operation
Tom, I noticed that earlier when I got an "invalid cipher 3des" error. Thanks, Paolo On 07/23/2016 10:00 AM, Tom Horsley wrote: On Sat, 23 Jul 2016 09:10:39 -0700 Paolo Galtieri wrote: Anyone have an idea of what's going on and how to fix it? Well, somewhere in that timeframe the security geeks of the world declared several encryption algorithms and dsa keys as insecure and turned them off by default. Perhaps you are hitting something in that vicinity. I spent weeks tracking down all the places that had a dsa public key in authorized keys and changing them to rsa version 2 keys (which no doubt means rsa version 2 will soon be declared insecure as well :-). -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: gnome fc22 fc24
Hi, You always could make a test by removing the graphical link : sudo systemctl set-default multi-user.target And make the roll back. sudo systemctl set-default graphical.target To come back to normal. But I think that a roll back should rolling back everything (gnome included) no ? Good luck ! ;) On 23/07/2016 15:45, Patrick Dupre wrote: > Hello, > > Is the gnome environment compatible between fc22 and fc24 ? > In other words, can a user run back in fc22 other an update have been > in fc24 ? > > Thank. > > === > Patrick DUPRÉ | | email: pdu...@gmx.com > Laboratoire de Physico-Chimie de l'Atmosphère | | > Université du Littoral-Côte d'Opale | | > Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 > 189A, avenue Maurice Schumann | | 59140 Dunkerque, France > === > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org -- “One original thought is worth a thousand mindless quotings.” “Le vrai n'est pas plus sûr que le probable.” Diogene Laerce -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: sign_and_send_pubkey: signing failed: agent refused operation
On Sat, 23 Jul 2016 09:10:39 -0700 Paolo Galtieri wrote: > Anyone have an idea of what's going on and how to fix it? Well, somewhere in that timeframe the security geeks of the world declared several encryption algorithms and dsa keys as insecure and turned them off by default. Perhaps you are hitting something in that vicinity. I spent weeks tracking down all the places that had a dsa public key in authorized keys and changing them to rsa version 2 keys (which no doubt means rsa version 2 will soon be declared insecure as well :-). -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
sign_and_send_pubkey: signing failed: agent refused operation
I upgraded one of my systems from F22 -> F24. The upgrade went fine, however, after the upgrade when I do an ssh from the F24 system to the F22 system I get the following error: sign_and_send_pubkey: signing failed: agent refused operation I re ran ssh-keygen on the F24 to generate the keys. I removed the F24 system entries in the known_hosts file on the F22 system. I copied the F22 public key to the F24 system and added it to the authorized_keys file. I still get the error. Running ssh from the F22 system to the F24 system works fine after having copied the F22 public key to the F24 system and adding it to the authorized_keys file and deleting the F22 entries in the known_hosts file. Now here's the strange part. If I start on the F22 system and ssh to the F24 system and then ssh back to the F22 system I don't see the error, it connects without prompting for a password. I also tried ssh F24 -> F24 and I get the error when the system on which I run the ssh is 192.168.10.5, but not when the originating system is my other F24 system at 192.168.10.2. ssh F24 (192.168.10.2) -> F24 (192.168.10.5) no error, but still prompts for password. ssh F24 (192.168.10.2) -> F22 (192.168.10.65) works no password prompt. Anyone have an idea of what's going on and how to fix it? Any help is appreciated. Paolo -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: WiFi conflicting with Bluetooth
On Fri, Jul 22, 2016 at 2:37 PM, Tod Merley wrote: > .. so what mods are loaded to handle wifi and bluetooth ... 03:00.0 Network controller [0280]: Broadcom Corporation BCM4331 802.11a/b/g/n [14e4:4331] (rev 02) Subsystem: Broadcom Corporation BCM4331 802.11a/b/g/n [14e4:4331] [...snip...] Kernel driver in use: bcma-pci-bridge Kernel modules: bcma lspci doesn't list Bluetooth. I'm not sure what driver is being used, but I suspect one of these: btusb 45056 0 snd_hda_codec_hdmi 45056 1 btrtl 16384 1 btusb btbcm 16384 1 btusb btintel16384 1 btusb bluetooth 491520 36 bnep,hidp,btbcm,btrtl,btusb,rfcomm,btintel It looks like bluetooth module just drags in generic, Intel, Broadcom, and Realtek device drivers, whether the hardware is present or not. I was almost ready to give up on b43/bcma because I don't get even get 802.11n support with that driver. What I found on Broadcom's site for Linux is hybrid-v35_64-nodebug-pcoem-6_30_223_271.tar.gz but I haven't gone down that rabbit hole yet. -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: WiFi conflicting with Bluetooth
On Fri, Jul 22, 2016 at 11:54 AM, Rick Stevens wrote: > Both bluetooth and wifi use the 2.4GHz frequency band. If you have > dual-band wifi, try using a frequency in the 5GHz band. Failing that, > try to get your wifi to use a different channel. That may clear it up. > This is always going to be an issue. Unfortunately the local WiFi offers 2.4GHz only. And WDS is involved, and there's something about either NetworkManager, or the kernel driver, or the WiFi firmware that causes it to disconnect from the AP every two minutes exactly, and tries to connect to another one. For all I know, this constant hunting, seeking, disconnecting, reconnecting is what's pissing off BT. Thing is, I don't see this same behavior on macOS with the same hardware and environment: I don't see the constant disconnects/reconnects, and I don't ever have BT problems. -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Timeline of a Fedora-24/KDE reboot
On Sat, 23 Jul 2016 16:43:02 +0200 Timothy Murphy wrote: > Is the delay due to the timeout mentioned? > I am not good at interpreting the output of journalctl. I can't interpret anything systemd says either, but you'd be more likely to see something if you remove the "rhgb quiet" from the kernel boot lines in grub.cfg. Instead of useless animation, you get actual messages about what is going on. Personally, I found that using the big hammer I wrote up here to reboot makes things go much faster: http://tomhorsley.com/game/punch.html The output from the program in there can be piped to sudo to kill off all the "user daemons" that never die, yet systemd waits for them forever. Another thing that slows down my reboots is the external USB drive I have that spins down and takes a while to spin up so it can be unmounted. If I explicitly unmount them, I can at least see what it is waiting for. Lately systemd has started waiting on apache httpd to shut down for some reason, so I added a "die apache die!" command to my "reboot" alias as well as all the above stuff. If you have any NFS filesystems mounted, you'll want to do a "umount -l -t nfs -a" as well, otherwise systemd can take hours to timeout on nfs mounts for systems that have actually gone down. (The -l option being the important bit). The list of things systemd waits on for no reason appears to grow every release or systemd update, but I try to track them down and hit them over the head with my hammer when new ones appear :-). -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Timeline of a Fedora-24/KDE reboot
As you will see, there is a long delay (90 seconds or so) while shutting down. If anyone can throw light on this I should be very grateful. This is the re-boot timeline on my Thinkpad T510: f=>Leave=>Restart command given and confirmed 19s just cursor on screen f icon appears and remains on screen 114s Thinkpad icon appears 14s automatic choice of kernel bulb appears and slowly fills 25s login screen - after logging in 5s K icon appears and horizontal bar fills 30s panel appears It will be seen that there is a long delay (almost 2 minutes) while shutting down. I see from "journalctl -b-1" that the delay occurs here -- Jul 23 14:11:38 william.gayleard.com NetworkManager[908]: [1469275898.3807] device (wlp3s0): supplicant interface state: completed -> disconnected Jul 23 14:11:41 william.gayleard.com wpa_supplicant[1061]: wlp3s0: Reject scan trigger since one is already pending Jul 23 14:13:02 william.gayleard.com NetworkManager[908]: [1469275982.5130] connectivity: check for uri 'http://fedoraproject.org/static/hotspot.txt' failed wit Jul 23 14:13:05 william.gayleard.com systemd[1]: session-1.scope: Stopping timed out. Killing. Jul 23 14:13:05 william.gayleard.com systemd[1]: Stopped Session 1 of user tim. -- Is the delay due to the timeout mentioned? I am not good at interpreting the output of journalctl. -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 24 and PNY SSD Problems
On Sat, 2016-07-23 at 08:04 -0500, Gregory P. Ennis wrote: > On Sun, Jul 17, 2016 at 08:45:13AM -0500, Gregory P. Ennis wrote: > > > > > > Everyone, > > > > I am trying to reclaim some use out of a couple old Compaq Presaio > > SR1720NX machines for the office by adding some memory and a PNY > > 240 > > GB > > CS1311 SSD drives. The bios was made by Phoenix; I did not > > identify > > a > > version number of the bios. I did not plan on keep the hard drive > > installed and planned on just using the SSD. These machines were > > IDE > > machines and only had two SATA ports on the motherboard. > > > > When I install the SSD the bios recognizes the Pny SSD properly, > > and > > I > > was able to set up the boot order without difficulty. > > > When I had to replace the MB of a similar, older system, I used a > non- > HP MB. > Later when I wanted to beef it up, the new MB only had 2 SATA ports > and > I wanted to install more drives. So I purchased a really cheap SATA > controller card. > > I got a store-brand SSD and to my surprise the MB controller did not > see it but the cheap controller did. Blaming the store-brand SSD, > I returned it and got a Crucial SSD. Same problem though. So it > was the controller, not the SSD. MB controller worked fine with > other SATA drives, but not with the SSD. > > Jon > -- > > Jon, > > I went to Fry's yesterday to pick up SATA controller card and the > Fry's > expert told me that their SATA controllers did not work with Linux. > Can you look up the name of the SATA card that you used and publish > it. > > Thanks, > > Greg > -- Why do you not replace the SSD that works with SATA-1 (1.5g)? the PNY does only Sata2 or 3. Just check for the SATA 1.5 support (I checked Samsung for the 850 EVO and accoding to http://www.samsung.com/semicond uctor/minisite/ssd/product/consumer/850evo.html tha drive is backward compatible with SATA 1.5). Now if you want to replace the controller, check what chip it uses and see if that is supported by Linux. I think most are nowadays Louis -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
gnome fc22 fc24
Hello, Is the gnome environment compatible between fc22 and fc24 ? In other words, can a user run back in fc22 other an update have been in fc24 ? Thank. === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France === -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 24 and PNY SSD Problems
On Sun, Jul 17, 2016 at 08:45:13AM -0500, Gregory P. Ennis wrote: > > Everyone, > > I am trying to reclaim some use out of a couple old Compaq Presaio > SR1720NX machines for the office by adding some memory and a PNY 240 > GB > CS1311 SSD drives. The bios was made by Phoenix; I did not identify > a > version number of the bios. I did not plan on keep the hard drive > installed and planned on just using the SSD. These machines were IDE > machines and only had two SATA ports on the motherboard. > > When I install the SSD the bios recognizes the Pny SSD properly, and > I > was able to set up the boot order without difficulty. > When I had to replace the MB of a similar, older system, I used a non- HP MB. Later when I wanted to beef it up, the new MB only had 2 SATA ports and I wanted to install more drives. So I purchased a really cheap SATA controller card. I got a store-brand SSD and to my surprise the MB controller did not see it but the cheap controller did. Blaming the store-brand SSD, I returned it and got a Crucial SSD. Same problem though. So it was the controller, not the SSD. MB controller worked fine with other SATA drives, but not with the SSD. Jon -- Jon, I went to Fry's yesterday to pick up SATA controller card and the Fry's expert told me that their SATA controllers did not work with Linux. Can you look up the name of the SATA card that you used and publish it. Thanks, Greg -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
