Re: [SOLVED Realtek 8111/8168] was Re: [qubes-users] R2rc1 networking issue

2016-11-25 Thread Vincent Elliott
Okay.

I guess solving these issues help with to accelerate learning curve.

Thanks again.
Vincent

Vincent "Kim" Elliott
ITC Consultant
Kingston, Jamaica
876-381-0661


On Fri, Nov 25, 2016 at 6:39 PM, Marek Marczykowski-Górecki <
marma...@invisiblethingslab.com> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Fri, Nov 25, 2016 at 11:59:26AM -0500, Vincent Elliott wrote:
> > Marek,
> >
> > Thanks a mil.
> >
> > I doubled the size, restarted the VM and the interface came right up.
> >
> > I spent many days trying to find a fix... perhaps the default size should
> > be doubled to accomodate any other noobs with the same hardware?
>
> No, because the bigger the value is, the greater chance you won't be
> able to start the VM at all. This amount of memory needs to be
> continuous (in terms of physical memory pages) and its hard to get one,
> especially after some time of running a lot of VMs...
>
> - --
> Best Regards,
> Marek Marczykowski-Górecki
> Invisible Things Lab
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQEcBAEBCAAGBQJYOMvKAAoJENuP0xzK19csB5QH/234khPD8UrXqy02/c7uneye
> lR+TvWh8sUA86VetrOQT//IIVHEaw4EygMS6ezI3ipM7wz3WoXga8CO1brMkD9Zt
> 8bJpl+3COqR4DYBV/AHhbYmRshzz5F5pyBRgzPSV6ifqze4kfHnkrSpC+z0PH5pg
> nR9qMKp6uMBW9Udea+oA72IRkZeszGzFcEDBGGCoSXQzSLJLi6oRD1eUF/drDfBL
> oOwamQQkTJV+THpEGvvmFSdA/W3yONgQix7QUpFIYGaAp83MnwzZBTzCjxjHqpMG
> IkHNK+l37FnU9RXQhIANFIlrE2CuhwIeTH6YU2ffuO+unH81AtK4WejUbL7jkdU=
> =gIsV
> -END PGP SIGNATURE-
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "qubes-users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/qubes-users/6hhO7SCFzM8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> qubes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to qubes-users@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/qubes-users/20161125233952.GH1145%40mail-itl.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CANNetsPOuPEwPzGOP5GW%2B-DgLXBfgwVa47zqgbmPXWPbKZWkCA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [SOLVED Realtek 8111/8168] was Re: [qubes-users] R2rc1 networking issue

2016-11-25 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, Nov 25, 2016 at 11:59:26AM -0500, Vincent Elliott wrote:
> Marek,
> 
> Thanks a mil.
> 
> I doubled the size, restarted the VM and the interface came right up.
> 
> I spent many days trying to find a fix... perhaps the default size should
> be doubled to accomodate any other noobs with the same hardware?

No, because the bigger the value is, the greater chance you won't be
able to start the VM at all. This amount of memory needs to be
continuous (in terms of physical memory pages) and its hard to get one,
especially after some time of running a lot of VMs...

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJYOMvKAAoJENuP0xzK19csB5QH/234khPD8UrXqy02/c7uneye
lR+TvWh8sUA86VetrOQT//IIVHEaw4EygMS6ezI3ipM7wz3WoXga8CO1brMkD9Zt
8bJpl+3COqR4DYBV/AHhbYmRshzz5F5pyBRgzPSV6ifqze4kfHnkrSpC+z0PH5pg
nR9qMKp6uMBW9Udea+oA72IRkZeszGzFcEDBGGCoSXQzSLJLi6oRD1eUF/drDfBL
oOwamQQkTJV+THpEGvvmFSdA/W3yONgQix7QUpFIYGaAp83MnwzZBTzCjxjHqpMG
IkHNK+l37FnU9RXQhIANFIlrE2CuhwIeTH6YU2ffuO+unH81AtK4WejUbL7jkdU=
=gIsV
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20161125233952.GH1145%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


Re: [SOLVED Realtek 8111/8168] was Re: [qubes-users] R2rc1 networking issue

2016-11-25 Thread Vincent Elliott
Marek,

Thanks a mil.

I doubled the size, restarted the VM and the interface came right up.

I spent many days trying to find a fix... perhaps the default size should
be doubled to accomodate any other noobs with the same hardware?

Vincent

Vincent "Kim" Elliott
ITC Consultant
Kingston, Jamaica
876-381-0661


On Fri, Nov 25, 2016 at 11:10 AM, Marek Marczykowski-Górecki <
marma...@invisiblethingslab.com> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Fri, Nov 25, 2016 at 07:57:59AM -0800, Vincent Elliott wrote:
> > On Thursday, 15 May 2014 01:27:56 UTC-5, inf...@gmail.com  wrote:
> > > On Monday, 12 May 2014 09:58:30 UTC+2, Marek Marczykowski-Górecki
> wrote:On 12.05.2014 00:43, inf...@gmail.com wrote:
> > >
> > > > On 12/05/14 00:38, Marek Marczykowski-Górecki wrote:
> > >
> > > >>
> > >
> > > >> ..
> > >
> > > >> Looks more like some missing package (linux-firmware?). On my fc20
> > >
> > > >> template
> > >
> > > >> there is /lib/firmware/rtl_nic...
> > >
> > > >>
> > >
> > > >>> Aha, indeed
> > >
> > > >>>
> > >
> > > >>> when I do a "sudo yum install linux-firmware" it begins to install
> but
> > >
> > > >>> fails with:
> > >
> > > >>>
> > >
> > > >>> Error unpacking rpm package linux-firmware-20140317-37
> .gitdec41bce.fc2noarch
> > >
> > > >>> error: unpacking of archive failed on file
> /usr/lib/firmware/updates: cpio:
> > >
> > > >>> chmod
> > >
> > > >>>
> > >
> > > >>> ?
> > >
> > > >> Ah, I see... That symlink is leftover from times where firmwares
> were provided
> > >
> > > >> by dom0. Now you can simply remove it and retry package
> installation.
> > >
> > > >> The next qubes-core-vm package will also remove that link.
> > >
> > > >
> > >
> > > > Sorry, am still Linux doofus, what exactly should I do?
> > >
> > >
> > >
> > > sudo rm /usr/lib/firmware/updates
> > >
> > >
> > >
> > > So that worked :-) :-)
> > >
> > > For anyone with an 8168 chip (until the update kicks in), best
> procedure (assuming have WiFi as well)..
> > >
> > > 1) disable 8168 network adapters in BIOS (necessary - it interferes
> with WiFi), get the WiFi connection going
> > > 2) in the Template VM, remove the symlink as above
> > > 3) sudo yum install linux-firmware
> > > 4) update Template VM, and dom0
> > > 5) reboot, re-enable 8168 network adapter in BIOS
> > >
> > > The wired network should now settle immediately, and seems to run fine
> on standard r8169 (sic)
> > >
> > > CB
> >
> > All,
> >
> > Am having the following issues on R3.2 and just cannot get the Ethernet
> connection working (8188CE WiFi is fine!):
> >
> > [user@sys-net ~]$ sudo journalctl | grep r8169
> > Nov 25 08:46:17 sys-net kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI
> loaded
> > Nov 25 08:46:17 sys-net kernel: r8169 :00:00.0: Xen PCI mapped GSI16
> to IRQ22
> > Nov 25 08:46:17 sys-net kernel: r8169 :00:00.0 eth0: RTL8168e/8111e
> at 0xc92f4000, 28:92:4a:2a:8d:16, XID 0c20 IRQ 23
> > Nov 25 08:46:17 sys-net kernel: r8169 :00:00.0 eth0: jumbo features
> [frames: 9200 bytes, tx checksumming: ko]
> > Nov 25 08:46:18 sys-net kernel: r8169 :00:00.0 enp0s0: renamed from
> eth0
> > Nov 25 08:46:28 sys-net NetworkManager[543]:   (enp0s0): new
> Ethernet device (carrier: OFF, driver: 'r8169', ifindex: 2)
> > Nov 25 08:46:28 sys-net kernel: r8169 :00:00.0: swiotlb buffer is
> full (sz: 16383 bytes)
> > Nov 25 08:46:28 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map
> RX DMA!
> > Nov 25 09:27:32 sys-net kernel: r8169 :00:00.0: swiotlb buffer is
> full (sz: 16383 bytes)
> > Nov 25 09:27:32 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map
> RX DMA!
> > Nov 25 09:27:32 sys-net kernel: r8169 :00:00.0: swiotlb buffer is
> full (sz: 16383 bytes)
> > Nov 25 09:27:32 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map
> RX DMA!
> > Nov 25 10:25:17 sys-net kernel: r8169 :00:00.0: swiotlb buffer is
> full (sz: 16383 bytes)
> > Nov 25 10:25:17 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map
> RX DMA!
> > Nov 25 10:26:13 sys-net kernel: r8169 :00:00.0: swiotlb buffer is
> full (sz: 16383 bytes)
> > Nov 25 10:26:13 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map
> RX DMA!
> > Nov 25 10:47:16 sys-net kernel: r8169 :00:00.0: swiotlb buffer is
> full (sz: 16383 bytes)
> > Nov 25 10:47:16 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map
> RX DMA!
> > [user@sys-net ~]$
>
> Try increasing swiotlb parameter on sys-net kernel cmdline. See here:
> https://www.qubes-os.org/doc/assigning-devices/#possible-issues
>
> - --
> Best Regards,
> Marek Marczykowski-Górecki
> Invisible Things Lab
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQEcBAEBCAAGBQJYOGJpAAoJENuP0xzK19cs4QoH/2jDyzwgrtN06LNzva4xoXer
> oYwySJ65m5uZAvw5e6EbD4fQqrppva8dnjqWIxFN9gZYm/DTGLUXOxoO86+Tv8BS
> CVdNJD4yPYWePBdeNZxQug2MZmMM5ad3+5gsvSlr+6Gza7mgKc8/g7G9JRItBGc1
> EFLX9G

Re: [SOLVED Realtek 8111/8168] was Re: [qubes-users] R2rc1 networking issue

2016-11-25 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, Nov 25, 2016 at 07:57:59AM -0800, Vincent Elliott wrote:
> On Thursday, 15 May 2014 01:27:56 UTC-5, inf...@gmail.com  wrote:
> > On Monday, 12 May 2014 09:58:30 UTC+2, Marek Marczykowski-Górecki  wrote:On 
> > 12.05.2014 00:43, inf...@gmail.com wrote:
> > 
> > > On 12/05/14 00:38, Marek Marczykowski-Górecki wrote:
> > 
> > >>
> > 
> > >> ..
> > 
> > >> Looks more like some missing package (linux-firmware?). On my fc20
> > 
> > >> template
> > 
> > >> there is /lib/firmware/rtl_nic...
> > 
> > >>
> > 
> > >>> Aha, indeed
> > 
> > >>>
> > 
> > >>> when I do a "sudo yum install linux-firmware" it begins to install but
> > 
> > >>> fails with:
> > 
> > >>>
> > 
> > >>> Error unpacking rpm package 
> > >>> linux-firmware-20140317-37.gitdec41bce.fc2noarch
> > 
> > >>> error: unpacking of archive failed on file /usr/lib/firmware/updates: 
> > >>> cpio:
> > 
> > >>> chmod
> > 
> > >>>
> > 
> > >>> ?
> > 
> > >> Ah, I see... That symlink is leftover from times where firmwares were 
> > >> provided
> > 
> > >> by dom0. Now you can simply remove it and retry package installation.
> > 
> > >> The next qubes-core-vm package will also remove that link.
> > 
> > > 
> > 
> > > Sorry, am still Linux doofus, what exactly should I do?
> > 
> > 
> > 
> > sudo rm /usr/lib/firmware/updates
> > 
> > 
> > 
> > So that worked :-) :-)
> > 
> > For anyone with an 8168 chip (until the update kicks in), best procedure 
> > (assuming have WiFi as well)..
> > 
> > 1) disable 8168 network adapters in BIOS (necessary - it interferes with 
> > WiFi), get the WiFi connection going
> > 2) in the Template VM, remove the symlink as above
> > 3) sudo yum install linux-firmware
> > 4) update Template VM, and dom0
> > 5) reboot, re-enable 8168 network adapter in BIOS
> > 
> > The wired network should now settle immediately, and seems to run fine on 
> > standard r8169 (sic)
> > 
> > CB
> 
> All,
> 
> Am having the following issues on R3.2 and just cannot get the Ethernet 
> connection working (8188CE WiFi is fine!):
> 
> [user@sys-net ~]$ sudo journalctl | grep r8169
> Nov 25 08:46:17 sys-net kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI 
> loaded
> Nov 25 08:46:17 sys-net kernel: r8169 :00:00.0: Xen PCI mapped GSI16 to 
> IRQ22
> Nov 25 08:46:17 sys-net kernel: r8169 :00:00.0 eth0: RTL8168e/8111e at 
> 0xc92f4000, 28:92:4a:2a:8d:16, XID 0c20 IRQ 23
> Nov 25 08:46:17 sys-net kernel: r8169 :00:00.0 eth0: jumbo features 
> [frames: 9200 bytes, tx checksumming: ko]
> Nov 25 08:46:18 sys-net kernel: r8169 :00:00.0 enp0s0: renamed from eth0
> Nov 25 08:46:28 sys-net NetworkManager[543]:   (enp0s0): new Ethernet 
> device (carrier: OFF, driver: 'r8169', ifindex: 2)
> Nov 25 08:46:28 sys-net kernel: r8169 :00:00.0: swiotlb buffer is full 
> (sz: 16383 bytes)
> Nov 25 08:46:28 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map RX 
> DMA!
> Nov 25 09:27:32 sys-net kernel: r8169 :00:00.0: swiotlb buffer is full 
> (sz: 16383 bytes)
> Nov 25 09:27:32 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map RX 
> DMA!
> Nov 25 09:27:32 sys-net kernel: r8169 :00:00.0: swiotlb buffer is full 
> (sz: 16383 bytes)
> Nov 25 09:27:32 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map RX 
> DMA!
> Nov 25 10:25:17 sys-net kernel: r8169 :00:00.0: swiotlb buffer is full 
> (sz: 16383 bytes)
> Nov 25 10:25:17 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map RX 
> DMA!
> Nov 25 10:26:13 sys-net kernel: r8169 :00:00.0: swiotlb buffer is full 
> (sz: 16383 bytes)
> Nov 25 10:26:13 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map RX 
> DMA!
> Nov 25 10:47:16 sys-net kernel: r8169 :00:00.0: swiotlb buffer is full 
> (sz: 16383 bytes)
> Nov 25 10:47:16 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map RX 
> DMA!
> [user@sys-net ~]$ 

Try increasing swiotlb parameter on sys-net kernel cmdline. See here:
https://www.qubes-os.org/doc/assigning-devices/#possible-issues

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJYOGJpAAoJENuP0xzK19cs4QoH/2jDyzwgrtN06LNzva4xoXer
oYwySJ65m5uZAvw5e6EbD4fQqrppva8dnjqWIxFN9gZYm/DTGLUXOxoO86+Tv8BS
CVdNJD4yPYWePBdeNZxQug2MZmMM5ad3+5gsvSlr+6Gza7mgKc8/g7G9JRItBGc1
EFLX9GbfFFTGhd9wrKqO+L54s+FbgwSjEiUTwmPeWQx0OZE/rPueZaYACAoZgUZe
QL2PSvEVPulpv+Fy2JpAA05BmLwlgdNqnaE/wS0iurky3SIxY8JvZYwPyzdHVamC
OKEiiByiu25YTn/wJPHEKwJmNggJVSeWozYYQVdiItausLFRg1YYdCEo0CGzGCc=
=GJ7m
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web vis

Re: [SOLVED Realtek 8111/8168] was Re: [qubes-users] R2rc1 networking issue

2016-11-25 Thread Vincent Elliott
On Thursday, 15 May 2014 01:27:56 UTC-5, inf...@gmail.com  wrote:
> On Monday, 12 May 2014 09:58:30 UTC+2, Marek Marczykowski-Górecki  wrote:On 
> 12.05.2014 00:43, inf...@gmail.com wrote:
> 
> > On 12/05/14 00:38, Marek Marczykowski-Górecki wrote:
> 
> >>
> 
> >> ..
> 
> >> Looks more like some missing package (linux-firmware?). On my fc20
> 
> >> template
> 
> >> there is /lib/firmware/rtl_nic...
> 
> >>
> 
> >>> Aha, indeed
> 
> >>>
> 
> >>> when I do a "sudo yum install linux-firmware" it begins to install but
> 
> >>> fails with:
> 
> >>>
> 
> >>> Error unpacking rpm package 
> >>> linux-firmware-20140317-37.gitdec41bce.fc2noarch
> 
> >>> error: unpacking of archive failed on file /usr/lib/firmware/updates: 
> >>> cpio:
> 
> >>> chmod
> 
> >>>
> 
> >>> ?
> 
> >> Ah, I see... That symlink is leftover from times where firmwares were 
> >> provided
> 
> >> by dom0. Now you can simply remove it and retry package installation.
> 
> >> The next qubes-core-vm package will also remove that link.
> 
> > 
> 
> > Sorry, am still Linux doofus, what exactly should I do?
> 
> 
> 
> sudo rm /usr/lib/firmware/updates
> 
> 
> 
> So that worked :-) :-)
> 
> For anyone with an 8168 chip (until the update kicks in), best procedure 
> (assuming have WiFi as well)..
> 
> 1) disable 8168 network adapters in BIOS (necessary - it interferes with 
> WiFi), get the WiFi connection going
> 2) in the Template VM, remove the symlink as above
> 3) sudo yum install linux-firmware
> 4) update Template VM, and dom0
> 5) reboot, re-enable 8168 network adapter in BIOS
> 
> The wired network should now settle immediately, and seems to run fine on 
> standard r8169 (sic)
> 
> CB

All,

Am having the following issues on R3.2 and just cannot get the Ethernet 
connection working (8188CE WiFi is fine!):

[user@sys-net ~]$ sudo journalctl | grep r8169
Nov 25 08:46:17 sys-net kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Nov 25 08:46:17 sys-net kernel: r8169 :00:00.0: Xen PCI mapped GSI16 to 
IRQ22
Nov 25 08:46:17 sys-net kernel: r8169 :00:00.0 eth0: RTL8168e/8111e at 
0xc92f4000, 28:92:4a:2a:8d:16, XID 0c20 IRQ 23
Nov 25 08:46:17 sys-net kernel: r8169 :00:00.0 eth0: jumbo features 
[frames: 9200 bytes, tx checksumming: ko]
Nov 25 08:46:18 sys-net kernel: r8169 :00:00.0 enp0s0: renamed from eth0
Nov 25 08:46:28 sys-net NetworkManager[543]:   (enp0s0): new Ethernet 
device (carrier: OFF, driver: 'r8169', ifindex: 2)
Nov 25 08:46:28 sys-net kernel: r8169 :00:00.0: swiotlb buffer is full (sz: 
16383 bytes)
Nov 25 08:46:28 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map RX DMA!
Nov 25 09:27:32 sys-net kernel: r8169 :00:00.0: swiotlb buffer is full (sz: 
16383 bytes)
Nov 25 09:27:32 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map RX DMA!
Nov 25 09:27:32 sys-net kernel: r8169 :00:00.0: swiotlb buffer is full (sz: 
16383 bytes)
Nov 25 09:27:32 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map RX DMA!
Nov 25 10:25:17 sys-net kernel: r8169 :00:00.0: swiotlb buffer is full (sz: 
16383 bytes)
Nov 25 10:25:17 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map RX DMA!
Nov 25 10:26:13 sys-net kernel: r8169 :00:00.0: swiotlb buffer is full (sz: 
16383 bytes)
Nov 25 10:26:13 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map RX DMA!
Nov 25 10:47:16 sys-net kernel: r8169 :00:00.0: swiotlb buffer is full (sz: 
16383 bytes)
Nov 25 10:47:16 sys-net kernel: r8169 :00:00.0 enp0s0: Failed to map RX DMA!
[user@sys-net ~]$ 

Vincent

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/aa1107e7-dcf8-445c-b6cd-499699ea18f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.