Re: monitor restarting (from sleep) issue on F25, HP Envy

[Ed Greshko]

On 03/29/17 09:47, Matt Morgan wrote:
> I just bought an HP Envy and installed F25 over the weekend. I have a
> few problems I did not have on the Dell XPS 13 it replaced. First,
> upon resuming from sleep, my external monitor doesn't wake up. The
> monitor says it's getting no input from the PC, and the Displays
> settings app doesn't show a second monitor.
>
> The only differences from before are
>
> a) the XPS 13 had a mini-displayport, and this one is HDMI
> b) this is a fresh install of F25, where the old computer was upgraded
> probably from F22.
>
> What can I do, any suggestions? Right now only rebooting seems to work.


I have a similar issue.  Running F25 with nVidia HW and the nVidia
drivers from rpmfusion. 

Sometimes the display settings doesn't "show" the monitor but it is
actually hidden behind the other monitor in that GUI and I can see it is
there when use xrandr.  I can get it back using a series of xrandr commands.

At other times it isn't shown.  But just pulling the plug from the video
card and reinserting brings it back for me.


-- 
Fedora Users List - The place to go to get others to do the work for you
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

monitor restarting (from sleep) issue on F25, HP Envy

[Matt Morgan]

I just bought an HP Envy and installed F25 over the weekend. I have a few
problems I did not have on the Dell XPS 13 it replaced. First, upon
resuming from sleep, my external monitor doesn't wake up. The monitor says
it's getting no input from the PC, and the Displays settings app doesn't
show a second monitor.

The only differences from before are

a) the XPS 13 had a mini-displayport, and this one is HDMI
b) this is a fresh install of F25, where the old computer was upgraded
probably from F22.

What can I do, any suggestions? Right now only rebooting seems to work.

Thanks,
Matt
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F25 + Killer 1535 @ 1mb/s

[Rick Stevens]

On 03/28/2017 12:24 PM, InvalidPath wrote:
> 
> On Tue, Mar 28, 2017 at 12:05 PM, InvalidPath  > wrote:
> 
> Fellas, I noticed today, while finally getting to use the Fedora
> side of my work laptop, that my wifi is running at 1MB/s on d Dell
> XPS 13 9550. According to Dell this model has the Killer AC 1535
> wireless chipset so possibly just a driver issue?
> 
> ➜  .ssh iwconfig 
> wlp2s0IEEE 802.11  ESSID:"waffle_house"   
>  Mode:Managed  Frequency:2.447 GHz  Access Point:
> C0:56:27:C4:77:BC
>  Bit Rate=1 Mb/s   Tx-Power=20 dBm
>  Retry short limit:7   RTS thr:off   Fragment thr:off 
>  Power Management:on 
>  Link Quality=58/70  Signal level=-52 dBm   
>  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0 
>  Tx excessive retries:285  Invalid misc:1819   Missed beacon:0 
> 
> lono wireless extensions. 
> 
> virbr0-nic  no wireless extensions. 
> 
> macvtap0  no wireless extensions. 
> 
> virbr0no wireless extensions. 
> 
> vnet0 no wireless extensions. 
> 
> 
> 
> 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac
> Wireless Network Adapter (rev 32)
> 
> 
> 
> Attached is wireless-info.txt, generated from: wget -N -t 5 -T
> 10 https://github.com/UbuntuForums/wireless-info/raw/master/wireless-info
>  
> &&
> chmod +x wireless-info && ./wireless-info Found
> via: https://forums.linuxmint.com/viewtopic.php?t=217258
> 
> 
> (Yes I know Mint.. the results for later version of Fedora were
> severely lacking)  
> 
> Whats odd is that I Put F25 on the wifes Lenovo just Sunday night to
> resolve this exact issue.
> 
> Thanks!
> 
> 
> 
> I think my issue is an incorrect or missing firmware: 
> 
> ➜  hw3.0git:(master)dmesg | grep ath10k
> [6.119173] ath10k_pci :02:00.0: enabling device ( -> 0002)
> [6.120108] ath10k_pci :02:00.0: pci irq msi oper_irq_mode 2
> irq_mode 0 reset_mode 0
> [6.334091] ath10k_pci :02:00.0: Direct firmware load for
> ath10k/pre-cal-pci-:02:00.0.bin failed with error -
> 2
> [6.334119] ath10k_pci :02:00.0: Direct firmware load for
> ath10k/cal-pci-:02:00.0.bin failed with error -2
> [6.334346] ath10k_pci :02:00.0: Direct firmware load for
> ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -
> 2
> [6.334350] ath10k_pci :02:00.0: could not fetch firmware file
> 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
> [6.336178] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
> chip_id 0x00340aff sub 1a56:1535
> [6.336181] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1
> tracing 0 dfs 0 testmode 0
> [6.337640] ath10k_pci :02:00.0: firmware ver
> WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4
> addr-pad crc32 75dee6c5
> [6.401049] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A
> crc32 6fc88fe7
> [8.522760] ath10k_pci :02:00.0: htt-ver 3.26 wmi-op 4 htt-op 3
> cal otp max-sta 32 raw 0 hwcrypto 1
> [8.596395] ath10k_pci :02:00.0 wlp2s0: renamed from wlan0
> ➜  hw3.0git:(master)ll
> 
> 
> Checking here: 
> 
> http://www.forums.fedoraforum.org/showthread.php?t=313191=2
> 
> I have cloned the kvalo git and have teh files staged for copying later.

It's interesting that it's looking for the firmware-5.bin file in
the hw3.0 directory, as it doesn't exist there. It DOES exist in the
hw2.1 directory (at least on my F25 system):

[root@prophead ~]# ls -lR /lib/firmware/ath10k/QCA6174
/lib/firmware/ath10k/QCA6174:
total 8
drwxr-xr-x. 2 root root 4096 Jan 23 11:38 hw2.1
drwxr-xr-x. 2 root root 4096 Jan 23 11:38 hw3.0

/lib/firmware/ath10k/QCA6174/hw2.1:
total 804
-rw-r--r--. 1 root root 263188 Dec  5 08:39 board-2.bin
-rw-r--r--. 1 root root   8124 Dec  5 08:39 board.bin
-rw-r--r--. 1 root root 498172 Dec  5 08:39 firmware-5.bin
-rw-r--r--. 1 root root  46087 Dec  5 08:39 notice_ath10k_firmware-5.txt

/lib/firmware/ath10k/QCA6174/hw3.0:
total 1140
-rw-r--r--. 1 root root 337204 Dec  5 08:39 board-2.bin
-rw-r--r--. 1 root root   8124 Dec  5 08:39 board.bin
-rw-r--r--. 1 root root 733784 Dec  5 08:39 firmware-4.bin
-rw-r--r--. 1 root root  79689 Dec  5 08:39 notice_ath10k_firmware-4.txt

Perhaps a simple copy to the 3.0 directory would satisfy it.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-  Perseverance:  When you're too damned stubborn to say "I quit!"   -
--

Re: Restoring a QEMU snapshot

[Robert Nichols]

On 03/28/2017 01:56 PM, Patrick O'Callaghan wrote:

On Tue, 2017-03-28 at 12:38 -0500, Robert Nichols wrote:

What you have is not a snapshot.  A snapshot is created with "qemu-img snapshot -c  
", and that is _not_ a separate file.  That "" is not a file name but just a tag 
to identify one of possibly several snapshots within that "" file.


I did create it with the above line. Clearly I didn't understand where
it was, or perhaps I inadvertently deleted it.


That output from "qemu-img info ..." says otherwise. That /var/lib/libvirt/images/Windows10.qcow2 
file was created with "qemu-img create -b /home/poc/Win10/win10.qcow2 
/var/lib/libvirt/images/Windows10.qcow2". There is no other way that "backing file: 
/home/poc/Win10/win10.qcow2" could appear in the output.


I can only say I have no recollection of typing that, and that I did
want to create a snapshot as a test. But it was a few days ago so I may
be wrong.


In order for the .../Windows10.qcow2 file to be valid, that backing file _must_ 
exist and be unchanged since that new file was created.


OK, though I can't guarantee it hasn't changed since I did run the VM
afterwards.


Did you really run the VM from the file in /home/poc/Win10/ ? It would be 
unusual to run a VM from a file in your home directory and not from one in the 
/var/lib/libvirt/images/ directory. Check the modification times on the files. 
If /home/poc/Win10/win10.qcow2 really has changed, then the 
/var/lib/libvirt/images/Windows10.qcow2 file is pretty much worthless.

If you want to test that backing file, create _another_ file using 
/home/poc/Win10/win10.qcow2 as a backing file and see if that new file can run 
or be made to run. You can do that safely and know that the backing file is not 
being affected.

--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F25 + Killer 1535 @ 1mb/s

[InvalidPath]

On Tue, Mar 28, 2017 at 12:05 PM, InvalidPath 
wrote:

> Fellas, I noticed today, while finally getting to use the Fedora side of
> my work laptop, that my wifi is running at 1MB/s on d Dell XPS 13 9550.
> According to Dell this model has the Killer AC 1535 wireless chipset so
> possibly just a driver issue?
>
> ➜  .ssh iwconfig
> wlp2s0IEEE 802.11  ESSID:"waffle_house"
>  Mode:Managed  Frequency:2.447 GHz  Access Point:
> C0:56:27:C4:77:BC
>  Bit Rate=1 Mb/s   Tx-Power=20 dBm
>  Retry short limit:7   RTS thr:off   Fragment thr:off
>  Power Management:on
>  Link Quality=58/70  Signal level=-52 dBm
>  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>  Tx excessive retries:285  Invalid misc:1819   Missed beacon:0
>
> lono wireless extensions.
>
> virbr0-nic  no wireless extensions.
>
> macvtap0  no wireless extensions.
>
> virbr0no wireless extensions.
>
> vnet0 no wireless extensions.
>
>
>
> 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
> Network Adapter (rev 32)
>
>
>
> Attached is wireless-info.txt, generated from: wget -N -t 5 -T 10
> https://github.com/UbuntuForums/wireless-info/raw/master/wireless-info &&
> chmod +x wireless-info && ./wireless-info Found via:
> https://forums.linuxmint.com/viewtopic.php?t=217258
>
> (Yes I know Mint.. the results for later version of Fedora were severely
> lacking)
>
> Whats odd is that I Put F25 on the wifes Lenovo just Sunday night to
> resolve this exact issue.
>
> Thanks!
>


I think my issue is an incorrect or missing firmware:

➜  hw3.0 git:(master) dmesg | grep ath10k
[6.119173] ath10k_pci :02:00.0: enabling device ( -> 0002)
[6.120108] ath10k_pci :02:00.0: pci irq msi oper_irq_mode 2
irq_mode 0 reset_mode 0
[6.334091] ath10k_pci :02:00.0: Direct firmware load for
ath10k/pre-cal-pci-:02:00.0.bin
failed with error -
2
[6.334119] ath10k_pci :02:00.0: Direct firmware load for
ath10k/cal-pci-:02:00.0.bin
failed with error -2
[6.334346] ath10k_pci :02:00.0: Direct firmware load for
ath10k/QCA6174/hw3.0/firmware-5.bin
failed with error -
2
[6.334350] ath10k_pci :02:00.0: could not fetch firmware file '
ath10k/QCA6174/hw3.0/firmware-5.bin': -2
[6.336178] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:1535
[6.336181] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 0
dfs 0 testmode 0
[6.337640] ath10k_pci :02:00.0: firmware ver
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4
addr-pad crc32 75dee6c5
[6.401049] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
6fc88fe7
[8.522760] ath10k_pci :02:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[8.596395] ath10k_pci :02:00.0 wlp2s0: renamed from wlan0
➜  hw3.0 git:(master) ll


Checking here:

http://www.forums.fedoraforum.org/showthread.php?t=313191=2

I have cloned the kvalo git and have teh files staged for copying later.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Restoring a QEMU snapshot

[stan]

On Tue, 28 Mar 2017 19:56:48 +0100
Patrick O'Callaghan  wrote:

> I can only say I have no recollection of typing that, and that I did
> want to create a snapshot as a test. But it was a few days ago so I
> may be wrong.

If you use bash, and have bash history enabled, at a command line you
could type a CTRL-R and then type qemu to search back through history
for commands with qemu in them that you've run.  Each time you hit
CTRL-R it will look back one more time.

Or, you can just do
less ~/.bash_history, type G to go to the bottom, and look for qemu
using ?qemu.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Restoring a QEMU snapshot

[InvalidPath]

On Tue, Mar 28, 2017 at 12:48 PM, Patrick O'Callaghan  wrote:

> On Tue, 2017-03-28 at 10:21 -0600, InvalidPath wrote:
> > Ahh interesting. Thanks for this info Patrick.
>
> I think you meant to thank Robert.
>
> poc
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>

Wow Im having a hard tie reading today :(

Thanks Robert!
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Restoring a QEMU snapshot

[Patrick O'Callaghan]

On Tue, 2017-03-28 at 12:38 -0500, Robert Nichols wrote:
> > > What you have is not a snapshot.  A snapshot is created with "qemu-img 
> > > snapshot -c  ", and that is _not_ a separate 
> > > file.  That "" is not a file name but just a tag to 
> > > identify one of possibly several snapshots within that "" file.
> > 
> > I did create it with the above line. Clearly I didn't understand where
> > it was, or perhaps I inadvertently deleted it.
> 
> That output from "qemu-img info ..." says otherwise. That 
> /var/lib/libvirt/images/Windows10.qcow2 file was created with "qemu-img 
> create -b /home/poc/Win10/win10.qcow2 
> /var/lib/libvirt/images/Windows10.qcow2". There is no other way that "backing 
> file: /home/poc/Win10/win10.qcow2" could appear in the output.

I can only say I have no recollection of typing that, and that I did
want to create a snapshot as a test. But it was a few days ago so I may
be wrong.

> In order for the .../Windows10.qcow2 file to be valid, that backing file 
> _must_ exist and be unchanged since that new file was created.

OK, though I can't guarantee it hasn't changed since I did run the VM
afterwards.

> > Currently 'qemu-img snapshot -l ' gives no output, so it
> > looks like it's gone assuming it was ever there.
> 
> There should not be any output. You simply do not have anything that qemu-img 
> calls a "snapshot".
> 
> > (BTW the "no such file or directory" message could not be less
> > helpful).
> 
> Agreed, 100%.
> 
> > > What you made was a copy-on-write image using /home/poc/Win10/win10.qcow2 
> > > as a backing file.  You can make changes in 
> > > /var/lib/libvirt/images/Windows10.qcow2 and not affect the backing file, 
> > > but the backing file _must_not_be_changed_ during the lifetime of that 
> > > dependent image.  That c-o-w image cannot be restored to its original 
> > > state.  The way you do that is to throw it away and create a new one with 
> > > the same backing file.
> > 
> > I'm going to try to attach it to another Windows instance to see if it
> > can be repaired. Otherwise, it looks like I'm screwed.
> 
> That backing file _must_ exist, or else you have nothing. If the backing file 
> exists, but has changed, then the only valid image is what is currently in 
> the backing file. If an unchanged backing file exists, you have the option to 
> (a) throw away that /var/lib/libvirt/images/Windows10.qcow2 file and create 
> it anew from that backing file, or (b) merge the changes that have been made 
> in the /var/lib/libvirt/images/Windows10.qcow2 file back into the backing 
> file. You do the latter with "qemu-img commit 
> /var/lib/libvirt/images/Windows10.qcow2".

OK, I'll look into that.

Thanks again.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Restoring a QEMU snapshot

[Patrick O'Callaghan]

On Tue, 2017-03-28 at 10:21 -0600, InvalidPath wrote:
> Ahh interesting. Thanks for this info Patrick.

I think you meant to thank Robert.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

F25 + Killer 1535 @ 1mb/s

[InvalidPath]

Fellas, I noticed today, while finally getting to use the Fedora side of my
work laptop, that my wifi is running at 1MB/s on d Dell XPS 13 9550.
According to Dell this model has the Killer AC 1535 wireless chipset so
possibly just a driver issue?

➜  .ssh iwconfig
wlp2s0IEEE 802.11  ESSID:"waffle_house"
 Mode:Managed  Frequency:2.447 GHz  Access Point: C0:56:27:C4:77:BC

 Bit Rate=1 Mb/s   Tx-Power=20 dBm
 Retry short limit:7   RTS thr:off   Fragment thr:off
 Power Management:on
 Link Quality=58/70  Signal level=-52 dBm
 Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
 Tx excessive retries:285  Invalid misc:1819   Missed beacon:0

lono wireless extensions.

virbr0-nic  no wireless extensions.

macvtap0  no wireless extensions.

virbr0no wireless extensions.

vnet0 no wireless extensions.



02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
Network Adapter (rev 32)



Attached is wireless-info.txt, generated from: wget -N -t 5 -T 10
https://github.com/UbuntuForums/wireless-info/raw/master/wireless-info &&
chmod +x wireless-info && ./wireless-info Found via:
https://forums.linuxmint.com/viewtopic.php?t=217258

(Yes I know Mint.. the results for later version of Fedora were severely
lacking)

Whats odd is that I Put F25 on the wifes Lenovo just Sunday night to
resolve this exact issue.

Thanks!
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Restoring a QEMU snapshot

[Robert Nichols]

On 03/28/2017 10:28 AM, Patrick O'Callaghan wrote:

On Tue, 2017-03-28 at 09:13 -0500, Robert Nichols wrote:

On 03/27/2017 12:31 PM, Patrick O'Callaghan wrote:

I have a QEMU image snapshot:

$ sudo qemu-img info /var/lib/libvirt/images/Windows10.qcow2
image: /var/lib/libvirt/images/Windows10.qcow2
file format: qcow2
virtual size: 20G (21474836480 bytes)
disk size: 196K
cluster_size: 65536
backing file: /home/poc/Win10/win10.qcow2
backing file format: qcow2
Format specific information:
compat: 1.1
lazy refcounts: true
refcount bits: 16
corrupt: false

However when I try to restore the virtual disk I get:

$ sudo qemu-img snapshot -a /var/lib/libvirt/images/Windows10.qcow2 
/home/poc/Win10/win10.qcow2
qemu-img: Could not apply snapshot '/var/lib/libvirt/images/Windows10.qcow2': 
-2 (No such file or directory)

I must be doing something obviously wrong, but can't see what it is.
Hints would be appreciated.


What you have is not a snapshot.  A snapshot is created with "qemu-img snapshot -c  
", and that is _not_ a separate file.  That "" is not a file name but just a tag 
to identify one of possibly several snapshots within that "" file.


I did create it with the above line. Clearly I didn't understand where
it was, or perhaps I inadvertently deleted it.


That output from "qemu-img info ..." says otherwise. That /var/lib/libvirt/images/Windows10.qcow2 
file was created with "qemu-img create -b /home/poc/Win10/win10.qcow2 
/var/lib/libvirt/images/Windows10.qcow2". There is no other way that "backing file: 
/home/poc/Win10/win10.qcow2" could appear in the output.

In order for the .../Windows10.qcow2 file to be valid, that backing file _must_ 
exist and be unchanged since that new file was created.


Currently 'qemu-img snapshot -l ' gives no output, so it
looks like it's gone assuming it was ever there.


There should not be any output. You simply do not have anything that qemu-img calls a 
"snapshot".


(BTW the "no such file or directory" message could not be less
helpful).


Agreed, 100%.


What you made was a copy-on-write image using /home/poc/Win10/win10.qcow2 as a 
backing file.  You can make changes in /var/lib/libvirt/images/Windows10.qcow2 
and not affect the backing file, but the backing file _must_not_be_changed_ 
during the lifetime of that dependent image.  That c-o-w image cannot be 
restored to its original state.  The way you do that is to throw it away and 
create a new one with the same backing file.


I'm going to try to attach it to another Windows instance to see if it
can be repaired. Otherwise, it looks like I'm screwed.


That backing file _must_ exist, or else you have nothing. If the backing file exists, but 
has changed, then the only valid image is what is currently in the backing file. If an 
unchanged backing file exists, you have the option to (a) throw away that 
/var/lib/libvirt/images/Windows10.qcow2 file and create it anew from that backing file, 
or (b) merge the changes that have been made in the 
/var/lib/libvirt/images/Windows10.qcow2 file back into the backing file. You do the 
latter with "qemu-img commit /var/lib/libvirt/images/Windows10.qcow2".

--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F25: Desktop PC not booting without a screen

[Simon Eigeldinger]

Hi Stan,
Hi Ed,


Am 28.03.2017 um 16:54 schrieb stan:

On Tue, 28 Mar 2017 15:53:44 +0800
Ed Greshko  wrote:


On 03/28/17 14:13, Eigeldinger Simon wrote:

I guess the plugs or the transistor seems to be the only solution
at the moment. I wonder if we could ask the devs to find a solution
to that?


Well, given the nature of the LiveOS images they would have to create
a whole new "spin" that is pre-configured to run the way you desire.
I don't know how much effort would be involved.  But it would add to
the QA process.  But it never hurts to ask.

According to the wayland people this shouldn't be much trouble.
As far as i know Fedora already uses wayland?


For the Gnome desktop the default is now Wayland with a fallback to
X11 if the drivers in use don't support Wayland.


Ed is right.


I partly agree unfortunately.
according to the wayland people its a small mod in the gnome wayland 
adapter which can then also being used in screenless mode and in a 
screen mode.
so basically it checks if a screen is present and then does its normal 
job or if a screen isn't present it still continues booting and starting 
gnome.



maybe another idea also might be some adapters.
if they draw enough power the machine might be thinking its something 
attached.

i will check tomorrow in the office.
we have some lying around.

greetings and thanks,
Simon

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Weird crashes and slowdowns

[Rick Stevens]

On 03/27/2017 12:13 PM, Susi Lehtola wrote:
> Hi,
> 
> 
> I'm wondering if anyone else has noticed weird things happening on their
> Intel laptops.
> 
> My Lenovo U31-70 has been misbehaving for a long long time under Fedora.
> Firefox and/or X often slow to a crawl, and sometimes X even crashes.
> I'm wondering if this is due to a buggy video driver.

I don't think your video driver is at cause. My first guess would be a
Firefox plugin that's the issue as there are a lot of anecdotal reports
of either Firefox or one or more of its plugins causing issues (such as
leaking memory).

First, run "top" and see what's eating CPU and/or memory. Check the
output of "free" or "vmstat" and see if you're using swap space (using
"vmstat 5", look at the "si" and "so" columns). If you're swapping a
lot, that'll slow your machine down a LOT.

Should you find it is firefox, you might also try using a different
browser or disabling all of Firefox's plugins and re-enabling them one
at a time. I think you'll probably find it.

> 
> Some relevant info
> 
> $ uname -r
> 4.9.14-200.fc25.x86_64
> $ uptime
>  12:11:54 up 6 days, 22:55,  1 user,  load average: 1.11, 0.98, 0.87
> $ ps aux|grep Xorg
>  1241 root  20   0 10.160g 4.014g 159388 S   1.1 52.1 648:10.37 Xorg
> 
> $ lspci
> 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev
> 09)
> 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500
> (rev 09)
> 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller
> (rev 09)
> 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI
> Controller (rev 03)
> 00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI
> Controller #1 (rev 03)
> 00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition
> Audio Controller (rev 03)
> 00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root
> Port #1 (rev e3)
> 00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root
> Port #3 (rev e3)
> 00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root
> Port #4 (rev e3)
> 00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI
> Controller (rev 03)
> 00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller
> (rev 03)
> 00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA
> Controller [AHCI Mode] (rev 03)
> 00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
> 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
> 03:00.0 Network controller: Qualcomm Atheros QCA6164 802.11ac Wireless
> Network Adapter (rev 20)
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
- The trouble with troubleshooting is that trouble sometimes -
- shoots back.   -
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Restoring a QEMU snapshot

[InvalidPath]

On Tue, Mar 28, 2017 at 8:13 AM, Robert Nichols 
wrote:

> On 03/27/2017 12:31 PM, Patrick O'Callaghan wrote:
>
>> I have a QEMU image snapshot:
>>
>> $ sudo qemu-img info /var/lib/libvirt/images/Windows10.qcow2
>> image: /var/lib/libvirt/images/Windows10.qcow2
>> file format: qcow2
>> virtual size: 20G (21474836480 bytes)
>> disk size: 196K
>> cluster_size: 65536
>> backing file: /home/poc/Win10/win10.qcow2
>> backing file format: qcow2
>> Format specific information:
>> compat: 1.1
>> lazy refcounts: true
>> refcount bits: 16
>> corrupt: false
>>
>> However when I try to restore the virtual disk I get:
>>
>> $ sudo qemu-img snapshot -a /var/lib/libvirt/images/Windows10.qcow2
>> /home/poc/Win10/win10.qcow2
>> qemu-img: Could not apply snapshot '/var/lib/libvirt/images/Windows10.qcow2':
>> -2 (No such file or directory)
>>
>> I must be doing something obviously wrong, but can't see what it is.
>> Hints would be appreciated.
>>
>
> What you have is not a snapshot.  A snapshot is created with "qemu-img
> snapshot -c  ", and that is _not_ a separate
> file.  That "" is not a file name but just a tag to identify
> one of possibly several snapshots within that "" file.
>
> What you made was a copy-on-write image using /home/poc/Win10/win10.qcow2
> as a backing file.  You can make changes in 
> /var/lib/libvirt/images/Windows10.qcow2
> and not affect the backing file, but the backing file _must_not_be_changed_
> during the lifetime of that dependent image.  That c-o-w image cannot be
> restored to its original state.  The way you do that is to throw it away
> and create a new one with the same backing file.
>
> --
> Bob Nichols "NOSPAM" is really part of my email address.
> Do NOT delete it.
>
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>


Ahh interesting. Thanks for this info Patrick.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Restoring a QEMU snapshot

[Patrick O'Callaghan]

On Tue, 2017-03-28 at 09:13 -0500, Robert Nichols wrote:
> On 03/27/2017 12:31 PM, Patrick O'Callaghan wrote:
> > I have a QEMU image snapshot:
> > 
> > $ sudo qemu-img info /var/lib/libvirt/images/Windows10.qcow2
> > image: /var/lib/libvirt/images/Windows10.qcow2
> > file format: qcow2
> > virtual size: 20G (21474836480 bytes)
> > disk size: 196K
> > cluster_size: 65536
> > backing file: /home/poc/Win10/win10.qcow2
> > backing file format: qcow2
> > Format specific information:
> > compat: 1.1
> > lazy refcounts: true
> > refcount bits: 16
> > corrupt: false
> > 
> > However when I try to restore the virtual disk I get:
> > 
> > $ sudo qemu-img snapshot -a /var/lib/libvirt/images/Windows10.qcow2 
> > /home/poc/Win10/win10.qcow2
> > qemu-img: Could not apply snapshot 
> > '/var/lib/libvirt/images/Windows10.qcow2': -2 (No such file or directory)
> > 
> > I must be doing something obviously wrong, but can't see what it is.
> > Hints would be appreciated.
> 
> What you have is not a snapshot.  A snapshot is created with "qemu-img 
> snapshot -c  ", and that is _not_ a separate file.  
> That "" is not a file name but just a tag to identify one of 
> possibly several snapshots within that "" file.

I did create it with the above line. Clearly I didn't understand where
it was, or perhaps I inadvertently deleted it.

Currently 'qemu-img snapshot -l ' gives no output, so it
looks like it's gone assuming it was ever there.

(BTW the "no such file or directory" message could not be less
helpful).

> What you made was a copy-on-write image using /home/poc/Win10/win10.qcow2 as 
> a backing file.  You can make changes in 
> /var/lib/libvirt/images/Windows10.qcow2 and not affect the backing file, but 
> the backing file _must_not_be_changed_ during the lifetime of that dependent 
> image.  That c-o-w image cannot be restored to its original state.  The way 
> you do that is to throw it away and create a new one with the same backing 
> file.

I'm going to try to attach it to another Windows instance to see if it
can be repaired. Otherwise, it looks like I'm screwed.

Thanks for the information.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F25: Desktop PC not booting without a screen

[stan]

On Tue, 28 Mar 2017 15:53:44 +0800
Ed Greshko  wrote:

> On 03/28/17 14:13, Eigeldinger Simon wrote:
> > I guess the plugs or the transistor seems to be the only solution
> > at the moment. I wonder if we could ask the devs to find a solution
> > to that?  
> 
> Well, given the nature of the LiveOS images they would have to create
> a whole new "spin" that is pre-configured to run the way you desire.
> I don't know how much effort would be involved.  But it would add to
> the QA process.  But it never hurts to ask.
> > According to the wayland people this shouldn't be much trouble.
> > As far as i know Fedora already uses wayland?  
> 
> For the Gnome desktop the default is now Wayland with a fallback to
> X11 if the drivers in use don't support Wayland.

Ed is right.  

But there might be a messy workaround using the existing LiveOS image.
I've never done this, and I haven't used a LiveOS, so these
instructions could be completely wrong.  After you are booted into the
image, switch to a virtual console (Ctrl-Alt-F2). I think that you can
then login as root with the empty password, but that is from memory of
messages on the mailing list.  If you can, you can then dnf install the
dummy driver, and add the xorg.conf file for it.  Since you aren't
using actual hardware, you can make the screen 4k for lots of real
estate, if you want.  Then kill X.  You might be able to just logout
of the gui desktop (Ctrl-Alt-F1), but that also might shutdown the
LiveOS.  If logging out doesn't work, you can find the pid of X by using
top or ps. After X is no longer running, switch to a different virtual
console (Ctrl-Alt-F3), and type startx. This should start X with the
dummy screen.  A lot of ifs and maybes in there, but it might work.

If it does, it would only last while you were up with the current
version of the LiveOS.  If you rebooted, you would have to go through
it all again.

Another possibility is building a custom virtual image that does what
you want.  But I'm even more ignorant there than about LiveOS images.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Firefox and flash plugin

[Terry Polzin]

No, further research shows me it's Firefox and its' API

On Tue, Mar 28, 2017 at 10:33 AM, Robert Moskowitz 
wrote:

> On 03/28/2017 09:07 AM, Terry Polzin wrote:
>
>> Firefox is complaining about flash not being up to date.  I believe i
>> have the latest of both.
>>
>> dnf list installed | grep -e firefox -e flash-plugin
>> firefox.x86_64 52.0-6.fc25   @updates
>> flash-plugin.x86_64 25.0.0.127-release@adobe-linux-x86_64
>>
>
> If you updated and not restarted Firefox, it will complain.  You have to
> restart Firefox after each new flash-plugin update.
>
> I *hate* that...
>
>
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Firefox and flash plugin

[Robert Moskowitz]

On 03/28/2017 09:07 AM, Terry Polzin wrote:
Firefox is complaining about flash not being up to date.  I believe i 
have the latest of both.


dnf list installed | grep -e firefox -e flash-plugin
firefox.x86_64 52.0-6.fc25   @updates
flash-plugin.x86_64 25.0.0.127-release@adobe-linux-x86_64


If you updated and not restarted Firefox, it will complain.  You have to 
restart Firefox after each new flash-plugin update.


I *hate* that...

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Firefox and flash plugin

[Ted Roche]

Is FireFox complaining, or are you getting that error when you
navigate to a website?

On Tue, Mar 28, 2017 at 10:07 AM, Terry Polzin  wrote:
> Firefox is complaining about flash not being up to date.  I believe i have
> the latest of both.
>
> dnf list installed | grep -e firefox -e flash-plugin
> firefox.x86_64   52.0-6.fc25   @updates
> flash-plugin.x86_64  25.0.0.127-release
> @adobe-linux-x86_64
>
>
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>



-- 
Ted Roche
Ted Roche & Associates, LLC
http://www.tedroche.com
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Restoring a QEMU snapshot

[Robert Nichols]

On 03/27/2017 12:31 PM, Patrick O'Callaghan wrote:

I have a QEMU image snapshot:

$ sudo qemu-img info /var/lib/libvirt/images/Windows10.qcow2
image: /var/lib/libvirt/images/Windows10.qcow2
file format: qcow2
virtual size: 20G (21474836480 bytes)
disk size: 196K
cluster_size: 65536
backing file: /home/poc/Win10/win10.qcow2
backing file format: qcow2
Format specific information:
compat: 1.1
lazy refcounts: true
refcount bits: 16
corrupt: false

However when I try to restore the virtual disk I get:

$ sudo qemu-img snapshot -a /var/lib/libvirt/images/Windows10.qcow2 
/home/poc/Win10/win10.qcow2
qemu-img: Could not apply snapshot '/var/lib/libvirt/images/Windows10.qcow2': 
-2 (No such file or directory)

I must be doing something obviously wrong, but can't see what it is.
Hints would be appreciated.


What you have is not a snapshot.  A snapshot is created with "qemu-img snapshot -c  
", and that is _not_ a separate file.  That "" is not a file name but just a tag 
to identify one of possibly several snapshots within that "" file.

What you made was a copy-on-write image using /home/poc/Win10/win10.qcow2 as a 
backing file.  You can make changes in /var/lib/libvirt/images/Windows10.qcow2 
and not affect the backing file, but the backing file _must_not_be_changed_ 
during the lifetime of that dependent image.  That c-o-w image cannot be 
restored to its original state.  The way you do that is to throw it away and 
create a new one with the same backing file.

--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Firefox and flash plugin

[Terry Polzin]

Firefox is complaining about flash not being up to date.  I believe i have
the latest of both.

dnf list installed | grep -e firefox -e flash-plugin
firefox.x86_64   52.0-6.fc25
@updates
flash-plugin.x86_64  25.0.0.127-release
@adobe-linux-x86_64
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Restoring a QEMU snapshot

[InvalidPath]

On Mar 28, 2017 6:28 AM, "Patrick O'Callaghan" 
wrote:

On Mon, 2017-03-27 at 13:35 -0600, InvalidPath wrote:
> > > You have all the required permissions I'm sure, yes?
> >
> > I'm using sudo, so yes.
> >
> > poc
> > ___
> > users mailing list -- users@lists.fedoraproject.org
> > To unsubscribe send an email to users-le...@lists.fedoraproject.org
> >
>
>
> Gotcha, Just making sure ;)
>
> Can you create a new VM, attaching that image and use it successfully?

I'll try that, but I'd still like to figure out why it didn't work.
Note that the VM suffered a crash (forced power-down) so its filesystem
needs fixing. However a Windows DVD in rescue mode didn't work, so I
was hoping a snapshot would do the trick. However I'm not entirely sure
if this is supported, or if snapshots are only useful as a rollback
mechanism.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org



Sure, by all means. However performing this test, will hopefully shed light
and verify the image is solid.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Restoring a QEMU snapshot

[Patrick O'Callaghan]

On Mon, 2017-03-27 at 13:35 -0600, InvalidPath wrote:
> > > You have all the required permissions I'm sure, yes?
> >
> > I'm using sudo, so yes.
> >
> > poc
> > ___
> > users mailing list -- users@lists.fedoraproject.org
> > To unsubscribe send an email to users-le...@lists.fedoraproject.org
> >
> 
> 
> Gotcha, Just making sure ;)
> 
> Can you create a new VM, attaching that image and use it successfully?

I'll try that, but I'd still like to figure out why it didn't work.
Note that the VM suffered a crash (forced power-down) so its filesystem
needs fixing. However a Windows DVD in rescue mode didn't work, so I
was hoping a snapshot would do the trick. However I'm not entirely sure
if this is supported, or if snapshots are only useful as a rollback
mechanism.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: AW: F25: Desktop PC not booting without a screen

[Ed Greshko]

On 03/28/17 14:13, Eigeldinger Simon wrote:
> I guess the plugs or the transistor seems to be the only solution at the 
> moment.
> I wonder if we could ask the devs to find a solution to that?

Well, given the nature of the LiveOS images they would have to create a
whole new "spin" that is pre-configured to run the way you desire.  I
don't know how much effort would be involved.  But it would add to the
QA process.  But it never hurts to ask.
> According to the wayland people this shouldn't be much trouble.
> As far as i know Fedora already uses wayland?

For the Gnome desktop the default is now Wayland with a fallback to X11
if the drivers in use don't support Wayland.


-- 
Fedora Users List - The place to go to get others to do the work for you
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

AW: F25: Desktop PC not booting without a screen

[Eigeldinger Simon]

Hi Stan, Hi Ed,

I guess the plugs or the transistor seems to be the only solution at the moment.
I wonder if we could ask the devs to find a solution to that?
According to the wayland people this shouldn't be much trouble.
As far as i know Fedora already uses wayland?

Greetings and thanks,
Simon


Mit freundlichen Grüßen

Simon Eigeldinger
Informatik
Nebengebäude 1, OG1
-   
Stadt Hohenems 
Kaiser-Franz-Josef-Straße 4 
6845 Hohenems
Österreich
Tel.:   +43 5576 7101-1143 
Fax:+43 5576 7101-1149
E-Mail: simon.eigeldin...@hohenems.at 
Web:www.hohenems.at

Diese Nachricht und allfällige angehängte Dokumente sind vertraulich und nur 
für den/die Adressaten bestimmt.
-Ursprüngliche Nachricht-
Von: stan [mailto:stanl-fedorau...@vfemail.net] 
Gesendet: Dienstag, 28. März 2017 00:13
An: users@lists.fedoraproject.org
Betreff: Re: F25: Desktop PC not booting without a screen

On Tue, 28 Mar 2017 05:47:39 +0800
Ed Greshko  wrote:

> To me, all of this makes perfect sense when applied to an installed 
> and running system.
> 
> However, in the original post, Simon referred to booting a "Fedora 
> Workstation Live USB".  AFAIK, the Live image does not contain the 
> xorg-x11-drv-dummy.  Additionally, the way the Live image is 
> structured I don't believe there is the chance to make a configuration 
> change to the drivers that are being used.
> 
> That is why I only suggested the dummy plugs.

Thanks for the correction.  I missed that little detail.  :-) 
___
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an 
email to users-le...@lists.fedoraproject.org
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org