Re: [qubes-users] Re: HCL - Dell Inspiron 15 5000 (5575) AMD Ryzen 5 2500U w/ Vega 8 Graphics

[Claudia]

January 3, 2020 5:53 PM, "Claudia"  wrote:

> January 1, 2020 5:09 PM, "Claudia"  wrote:
> 
>> However, I still have a long road ahead of me. I did several suspend/resume 
>> cycles, and each time I
>> had a different combination of problems, including the mouse sticking, the 
>> keyboard not working,
>> and finally input/output errors and segmentation faults in the terminal. But 
>> the Xen problem has
>> been identified nonetheless. I'll try kernel-latest and see if that changes 
>> anything.
> 
> Installed kernel-latest from stable, 5.3.11-1.qubes.x86, and no difference as 
> far as I can tell. It
> resumes fine the first time usually, but after the second or third cycle, I 
> get a bunch of io
> errors, as though someone unplugged the SATA connector. I think this is 
> actually the underlying
> cause of the other symptoms. This is with no VMs running. No swap.
> 
> ata1.00: qc timeout (cmd 0xec)
> ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata1.00: limiting SATA link speed to 3.0 Gbps
> ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
> ata1.00: revalidation failed (errno=-5)
> ata1.00: disabled
> sd 0:0:0:0: [sda] Start/Stop Unit failed: Result: hostbyte=DID_BAD_TARGET 
> driverbyte=DRIVER_OK
> sd 0:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET 
> driverbyte=DRIVER_OK
> sd 0:0:0:0: [sda] tag#21 CDB: Write(10) 2a 00 3c 9f [...]
> blk_update_request: I/O error, dev sda, sector [...] op 0x1: (WRITE) flags 
> 0x10 phys_seg 1 prio
> class 0
> BTRFS error (device dm-0): bdev /dev/mapper/luks-[...] errs: wr 1, rd 0, 
> flush 0, corrupt 0, gen0
> 
> Note this different than the Fedora 25 resume behavior. In F25 with 4.8.6, 
> the screen doesn't power
> on, but the system seems responsive otherwise. For example ctrl-alt-delete 
> reboots after 60 seconds
> as expected. (In Qubes, after resuming a second or third time and getting 
> disk errors, when you try
> to shutdown it will just hang indefinitely.) But F25 was running from a USB 
> drive so I wouldn't
> necessarily know if there were SATA errors in that case.
> 
> I'll see if I can figure out how to apply the patch to the latest 4.1 
> (F31-based) and try it from
> there. In the mean time, if anyone has any ideas please share.


And... SUCCESS 2.0!

Perhaps it's still too early to celebrate, but after six months of 
troubleshooting I think I might finally have working suspend/resume. I did some 
googling around, and eventually came across a rather inconspicuous post[1] from 
2013 in the Xen archives that mentioned something I hadn't tried or heard about 
before. All I had to do was add to the Xen command line "dom0_max_vcpus=1 
dom0_vcpus_pin". And that's it. Couldn't have been simpler. I should not have 
had to go to the 20th page of search results to find out about this.

This runs dom0 on CPU0 and only CPU0. My understanding is that it has to be 
running on the boot CPU at the exact moment of suspend and resume. Or something 
like that. Not sure of the specifics. Note that this may have a performance 
impact depending on your situation. 

At first, I thought maybe this would render the Xen patch unnecessary: e.g. 
that it was suspending on one core and resuming on another causing an apparent 
change in cpuid bits. But I can see from the log the cpuid capability bits are 
still changing as before. (Those of you just tuning in, the patch and 
instructions are earlier in this thread. However you probably won't need it 
unless you have an AMD Fam15h processor. Note that there may be security 
implications associated with this patch.)

I've only had a chance to test about 15-20 cycles or so, but it works great so 
far. Suspends fast, resumes fast, lid-switch triggers both suspend and resume, 
WiFi automatically reconnects. I suspended in the middle of a YouTube video and 
came back up seamlessly. However after resume all instances of Firefox seem to 
jump to 100% CPU (but not frozen) until I close it, but that appears to be a 
known issue outside of Qubes and Xen also. 

Tested on R4.0 stable with kernel-latest 5.3.11-1.qubes.x86 on Xen 
4.8.5-14.fc25 (patched). I haven't tried this yet on the default kernel but I 
think it would probably work just as well. It also very well might work on 
other Qubes/Xen versions. I'll update my HCL accordingly when I have a chance.

[1] https://lists.gt.net/xen/devel/270965#270965

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/87602866f77e6fa8866448a22b48b4a1%40disroot.org.

[qubes-users] Re: sys-usb issues recognizing devices & maintaining drive connections

[Lorenzo Lamas]

On Friday, January 3, 2020 at 11:02:24 PM UTC+1, scal...@posteo.net wrote:
>
> Since Qubes 3.2 I've had issues with sys-usb not recognizing devices. My 
> solution has been to reboot until it works. 1 in 4 times it seems to 
> work correctly. 
>
> The device that I have the most trouble with is a trackpad. Sometimes 
> after using the machine successfully for days, I'll wake it up and the 
> trackpad mouse speed will be slowed down. Sometimes rebooting sys-usb 
> will fix this. Other times I have to reboot the whole machine. 
>
> All that i've been able to live with. 
>
> But the other problem I've had with sys-usb is connecting to external 
> drives. Here are the copy speeds I get on my machine to an external usb 
> device: 
>
> Tails OS 33mb/sec 
> Qubes OS 12mb/sec 
>
> HOWEVER, the Qubes # is misleading because it seems to have regular i/o 
> issues so it is 12mb/sec when it is working, which is off and on. Then 
> after some time the whole device will become read only and i'll get a 
> i/o error message after copying for some time. This has become a serious 
> problem because i can no longer do Backups to external drives. (Copying 
> smaller files to/from usb is manageable.) 
>
> Therefore I've decided to ask for help here. A search for "sys-usb" 
> didn't reveal any examples of others having similar problems, but maybe 
> someone can help me narrow down the problem here. 
>
> This is my hardware: https://www.coreboot.org/Board:asus/kgpe-d16 
>
> Any advice is much appreciated. 
>
> scallyob 
>

I may have a similar problem. 
It started with Qubes 4.0 for me. I have 2 usb controllers, one for USB 3.0 
and one for USB 2.0.
The USB 2.0 ports also don't recognize devices a lot of the time and I have 
to reboot as well, also probably works about 1 in 4 times. The strange 
thing is, when it was summer, and the temperature inside the house was 
warmer, I rarely had this issue, but now that it's colder again, it happens 
a lot again.
When it is not recognizing devices, the Qubes Devices Widget shows an 
additional device: "sys-usb:2-1:1 - 138a_003c_0030009d7e88". It is not 
visible when everything works fine. Do you have that as well?

When it works it is also slow for me, just mounting and opening the folder 
of an USB drive seems to take ages, transferring small files as well. I 
don't know if it would also become read-only after a while, because I don't 
use it that long, because I use my USB 3.0 ports for that, which still work 
fine fortunately.

I haven't found a solution, so I can't help you there, unfortunately.
I'm on a 2nd gen Intel i5 laptop btw.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a71a1465-a0d4-48ba-993a-4b17f4538ea2%40googlegroups.com.

[qubes-users] sys-usb issues recognizing devices & maintaining drive connections

[scallyob]

Since Qubes 3.2 I've had issues with sys-usb not recognizing devices. My 
solution has been to reboot until it works. 1 in 4 times it seems to 
work correctly.


The device that I have the most trouble with is a trackpad. Sometimes 
after using the machine successfully for days, I'll wake it up and the 
trackpad mouse speed will be slowed down. Sometimes rebooting sys-usb 
will fix this. Other times I have to reboot the whole machine.


All that i've been able to live with.

But the other problem I've had with sys-usb is connecting to external 
drives. Here are the copy speeds I get on my machine to an external usb 
device:


Tails OS 33mb/sec
Qubes OS 12mb/sec

HOWEVER, the Qubes # is misleading because it seems to have regular i/o 
issues so it is 12mb/sec when it is working, which is off and on. Then 
after some time the whole device will become read only and i'll get a 
i/o error message after copying for some time. This has become a serious 
problem because i can no longer do Backups to external drives. (Copying 
smaller files to/from usb is manageable.)


Therefore I've decided to ask for help here. A search for "sys-usb" 
didn't reveal any examples of others having similar problems, but maybe 
someone can help me narrow down the problem here.


This is my hardware: https://www.coreboot.org/Board:asus/kgpe-d16

Any advice is much appreciated.

scallyob

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/eff15f60f1a86c2252647614dd05763c%40posteo.net.

[qubes-users] IBM X3550 M4 - Ethernet connection not working

[Dylan]

Hi, I've recently installed Qubes R4 on a IBM X3550 M4 and everything 
worked as expected apart from the networking. Originally I thought this 
might be a problem with R4 so I upgraded to R4.0.2 but no avail.

The connection is detected as being plugged in, I've tried manually setting 
the IP in sys-net, different switch, router, cable, pretty much anything I 
can think of; but it will not connect to the network.

I then thought it could be a conflict of some type so I removed 3 of the 4 
i350 NIC's pcie devices; but this had no effect either.

I should add there were no issues during install.

Any help would be appreciated, thanks.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/9fcc18a7-dc02-4e90-9c57-31d8f11fa206%40googlegroups.com.

Re: [qubes-users] Re: HCL - Dell Inspiron 15 5000 (5575) AMD Ryzen 5 2500U w/ Vega 8 Graphics

[brendan . hoar]

On Friday, January 3, 2020 at 3:48:33 PM UTC-5, Claudia wrote:
>
> January 3, 2020 7:17 PM, brend...@gmail.com  wrote:
>
> > Since it appears the old made-for-purpose USB 2.0 EHCI Debug port 
> dongles are impossible to find
> > these days, I've been looking around for alternatives and stumbled upon 
> use of the raspberry pi
> > zero w/ USB Gadget drivers to log chromebook coreboot debug data. Pretty 
> sure (but not 100%) the
> > same could be done for Xen debug data:
> ... 
>
> So...now I have a pi zero on the way.
>
> Funny you should mention that. I happened to have a Pi Zero W lying 
> around, and I almost did go that route. However when I started looking into 
> USB 2.0 EHCI debug (thanks to user Qubes123 for the tip), it looked pretty 
> complicated and somewhat unreliable, so I decided to try some simpler 
> techniques first. Also my USB controllers don't list the debug capability 
> so I don't think it would work on this machine.
>

On the W520, lspci -nvvD shows two PCI USB EHCI devices with Debug enabled. 
Probably the same PCI device presenting itself twice. From what I've read 
elsewhere, the USB 2.0 port on the back of the unit is the one wired up for 
debug use. Presumably the X230 units are similarly equipped.
 
Haven't checked the P52 yet.

Luckily Qubes123's patch worked, or at least fixed the Xen panic, so I 
> don't think I have a need for USB debugging at the moment.
>
> However it is something I'd like to learn more about in case I need it in 
> the future. Please let me know how you make out!
>

Will do.
 

> Also something you might be interested in is USB 3.0 XHCI Debug 
> Capability, or DbC, which is built into the USB 3.0 spec. It's a 
> host-to-host protocol so it doesn't require any OTG/gadget hardware, just 
> two devices that support USB 3.0 Enhanced Superspeed, a USB 3.0 Enhanced 
> Superspeed cable, and the target device (USB controller) must support XHCI 
> Debug Capability (DbC). 
> https://www.kernel.org/doc/html/v4.17/driver-api/usb/usb3-debug-port.html
>
> The machine I was trying to debug does have a USB 3.1 controller, but it 
> doesn't list the either the XHCI nor EHCI debug capability, even when USB 
> debug is enabled in firmware. Just because there's a setting for it in 
> firmware doesn't necessarily mean the hardware supports it, I suppose. 
>

I'm not entirely sure that the XHCI capability is as "low level" friendly 
as the EHCI capability (it might require at least a mini USB stack to be 
utilized). Haven't dived into that fully yet.

B

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e2f34648-a0db-44ad-8e81-d5d78acd7323%40googlegroups.com.

Re: [qubes-users] Re: HCL - Dell Inspiron 15 5000 (5575) AMD Ryzen 5 2500U w/ Vega 8 Graphics

[Claudia]

January 3, 2020 7:17 PM, brendan.h...@gmail.com wrote:

> On Friday, January 3, 2020 at 12:53:31 PM UTC-5, Claudia wrote:
>> January 1, 2020 5:09 PM, "Claudia"  wrote:I'll see if I 
>> can figure out how to
>> apply the patch to the latest 4.1 (F31-based) and try it from there. In the 
>> mean time, if anyone
>> has any ideas please share.
> 
> Maybe not directly helpful, but I've been looking to be able to better debug 
> Xen issues, so
> reposting this from https://github.com/QubesOS/qubes-issues/issues/5529
> ...
> Since it appears the old made-for-purpose USB 2.0 EHCI Debug port dongles are 
> impossible to find
> these days, I've been looking around for alternatives and stumbled upon use 
> of the raspberry pi
> zero w/ USB Gadget drivers to log chromebook coreboot debug data. Pretty sure 
> (but not 100%) the
> same could be done for Xen debug data:
> 
> https://johnlewis.ie/pi-zero-w-flashrom-and-usb-gadget-debug/
> https://johnlewis.ie/wp-content/uploads/2017/04/ehcidebug.gif
> raspberrypi/linux#1907
> https://gist.github.com/gbaman/50b6cca61dd1c3f88f41
> 
> So...now I have a pi zero on the way.

Funny you should mention that. I happened to have a Pi Zero W lying around, and 
I almost did go that route. However when I started looking into USB 2.0 EHCI 
debug (thanks to user Qubes123 for the tip), it looked pretty complicated and 
somewhat unreliable, so I decided to try some simpler techniques first. Also my 
USB controllers don't list the debug capability so I don't think it would work 
on this machine. Luckily Qubes123's patch worked, or at least fixed the Xen 
panic, so I don't think I have a need for USB debugging at the moment.

However it is something I'd like to learn more about in case I need it in the 
future. Please let me know how you make out!

Also something you might be interested in is USB 3.0 XHCI Debug Capability, or 
DbC, which is built into the USB 3.0 spec. It's a host-to-host protocol so it 
doesn't require any OTG/gadget hardware, just two devices that support USB 3.0 
Enhanced Superspeed, a USB 3.0 Enhanced Superspeed cable, and the target device 
(USB controller) must support XHCI Debug Capability (DbC). 
https://www.kernel.org/doc/html/v4.17/driver-api/usb/usb3-debug-port.html

The machine I was trying to debug does have a USB 3.1 controller, but it 
doesn't list the either the XHCI nor EHCI debug capability, even when USB debug 
is enabled in firmware. Just because there's a setting for it in firmware 
doesn't necessarily mean the hardware supports it, I suppose.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/de518a5fbdcafb8e65c8e64fa6cc768c%40disroot.org.

Re: [qubes-users] Re: HCL - Dell Inspiron 15 5000 (5575) AMD Ryzen 5 2500U w/ Vega 8 Graphics

[brendan . hoar]

On Friday, January 3, 2020 at 12:53:31 PM UTC-5, Claudia wrote:
>
> January 1, 2020 5:09 PM, "Claudia" > 
> wrote:
>
> I'll see if I can figure out how to apply the patch to the latest 4.1 
> (F31-based) and try it from there. In the mean time, if anyone has any 
> ideas please share. 
>

Maybe not directly helpful, but I've been looking to be able to better 
debug Xen issues, so reposting this from 
https://github.com/QubesOS/qubes-issues/issues/5529
...

Since it appears the old made-for-purpose USB 2.0 EHCI Debug port dongles 
are impossible to find these days, I've been looking around for 
alternatives and stumbled upon use of the raspberry pi zero w/ USB Gadget 
drivers to log chromebook coreboot debug data. Pretty sure (but not 100%) 
the same could be done for Xen debug data:

https://johnlewis.ie/pi-zero-w-flashrom-and-usb-gadget-debug/
https://johnlewis.ie/wp-content/uploads/2017/04/ehcidebug.gif
raspberrypi/linux#1907 
https://gist.github.com/gbaman/50b6cca61dd1c3f88f41


So...now I have a pi zero on the way.


Brendan

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a3f62e27-517c-4eb3-8f8e-73bde2a0bb56%40googlegroups.com.

Re: [qubes-users] Re: HCL - Dell Inspiron 15 5000 (5575) AMD Ryzen 5 2500U w/ Vega 8 Graphics

[Vít Šesták]

While comparing Qubes 4 to Fedora 25 might be tempting, it is not similar as it 
might seem. Qubes 4 is based on Fedora 25, but some parts including kernel are 
independent. So, seeing different kernel-related behavior in Fedora 25 and 
Qubes 4 is definitely not a surprise.

Regards,
Vít Šesták 'v6ak'

On January 3, 2020 6:53:24 PM GMT+01:00, Claudia  wrote:
>January 1, 2020 5:09 PM, "Claudia"  wrote:
>
>> However, I still have a long road ahead of me. I did several
>suspend/resume cycles, and each time I
>> had a different combination of problems, including the mouse
>sticking, the keyboard not working,
>> and finally input/output errors and segmentation faults in the
>terminal. But the Xen problem has
>> been identified nonetheless. I'll try kernel-latest and see if that
>changes anything.
>
>Installed kernel-latest from stable, 5.3.11-1.qubes.x86, and no
>difference as far as I can tell. It resumes fine the first time
>usually, but after the second or third cycle, I get a bunch of io
>errors, as though someone unplugged the SATA connector. I think this is
>actually the underlying cause of the other symptoms. This is with no
>VMs running. No swap.
>
>ata1.00: qc timeout (cmd 0xec)
>ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
>ata1.00: limiting SATA link speed to 3.0 Gbps
>ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
>ata1.00: revalidation failed (errno=-5)
>ata1.00: disabled
>sd 0:0:0:0: [sda] Start/Stop Unit failed: Result:
>hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
>sd 0:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET
>driverbyte=DRIVER_OK
>sd 0:0:0:0: [sda] tag#21 CDB: Write(10) 2a 00 3c 9f [...]
>blk_update_request: I/O error, dev sda, sector [...] op 0x1: (WRITE)
>flags 0x10 phys_seg 1 prio class 0
>BTRFS error (device dm-0): bdev /dev/mapper/luks-[...] errs: wr 1, rd
>0, flush 0, corrupt 0, gen0
>
>Note this different than the Fedora 25 resume behavior. In F25 with
>4.8.6, the screen doesn't power on, but the system seems responsive
>otherwise. For example ctrl-alt-delete reboots after 60 seconds as
>expected. (In Qubes, after resuming a second or third time and getting
>disk errors, when you try to shutdown it will just hang indefinitely.)
>But F25 was running from a USB drive so I wouldn't necessarily know if
>there were SATA errors in that case.
>
>I'll see if I can figure out how to apply the patch to the latest 4.1
>(F31-based) and try it from there. In the mean time, if anyone has any
>ideas please share.
>
>-- 
>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/67LmZ8LsR9A/unsubscribe.
>To unsubscribe from this group and all its topics, send an email to
>qubes-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>https://groups.google.com/d/msgid/qubes-users/8b5cad4abcdce9da863ab033c86752d7%40disroot.org.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/86C1ED2B-2651-459F-BF1C-D927C2A2EFA1%40v6ak.com.

Re: [qubes-users] Re: HCL - Dell Inspiron 15 5000 (5575) AMD Ryzen 5 2500U w/ Vega 8 Graphics

[Claudia]

January 1, 2020 5:09 PM, "Claudia"  wrote:

> However, I still have a long road ahead of me. I did several suspend/resume 
> cycles, and each time I
> had a different combination of problems, including the mouse sticking, the 
> keyboard not working,
> and finally input/output errors and segmentation faults in the terminal. But 
> the Xen problem has
> been identified nonetheless. I'll try kernel-latest and see if that changes 
> anything.

Installed kernel-latest from stable, 5.3.11-1.qubes.x86, and no difference as 
far as I can tell. It resumes fine the first time usually, but after the second 
or third cycle, I get a bunch of io errors, as though someone unplugged the 
SATA connector. I think this is actually the underlying cause of the other 
symptoms. This is with no VMs running. No swap.

ata1.00: qc timeout (cmd 0xec)
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.00: limiting SATA link speed to 3.0 Gbps
ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
ata1.00: revalidation failed (errno=-5)
ata1.00: disabled
sd 0:0:0:0: [sda] Start/Stop Unit failed: Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK
sd 0:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK
sd 0:0:0:0: [sda] tag#21 CDB: Write(10) 2a 00 3c 9f [...]
blk_update_request: I/O error, dev sda, sector [...] op 0x1: (WRITE) flags 
0x10 phys_seg 1 prio class 0
BTRFS error (device dm-0): bdev /dev/mapper/luks-[...] errs: wr 1, rd 0, flush 
0, corrupt 0, gen0

Note this different than the Fedora 25 resume behavior. In F25 with 4.8.6, the 
screen doesn't power on, but the system seems responsive otherwise. For example 
ctrl-alt-delete reboots after 60 seconds as expected. (In Qubes, after resuming 
a second or third time and getting disk errors, when you try to shutdown it 
will just hang indefinitely.) But F25 was running from a USB drive so I 
wouldn't necessarily know if there were SATA errors in that case.

I'll see if I can figure out how to apply the patch to the latest 4.1 
(F31-based) and try it from there. In the mean time, if anyone has any ideas 
please share.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/8b5cad4abcdce9da863ab033c86752d7%40disroot.org.

[qubes-users] Re: Android-x86 7.1-r2 with GAPPS installation guide

[arthur . summers]

Here are my modified instructions. There were a few tweaks such as adding a 
few more packages to get via apt, editing a different manifest, and 
retrieving OpenGapps via git lfs:

# Create a builder AppVM based on whonix-14-ws or Debian in which you'll 
build android-x86.
# You'll need 120GB for android-x86 sources and temp build files and 30GB 
for swap.
# Extend private storage size to 160GB via GUI or in dom0:
qvm-volume extend android-builder:private 160g


# Add 30GB swap in builder VM:
sudo fallocate -l 30G /tmp/swapfile
sudo chmod 0600 /tmp/swapfile 
sudo mkswap /tmp/swapfile 
sudo swapon /tmp/swapfile


# Add the following repository to /etc/apt/sources.list (openjdk-8 is 
required, but it is not available under Debian 10):
# deb https://deb.debian.org/debian sid main


# Install packages in whonix-14-ws (or Debian) template:
sudo apt-get update
sudo apt-get install openjdk-8-jdk gnupg flex bison gperf build-essential 
zip zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev 
x11proto-core-dev libx11-dev lib32z-dev libgl1-mesa-dev libxml2-utils 
xsltproc unzip gettext libyaml-dev dosfstools syslinux syslinux-utils 
xorriso mtools makebootfat lunzip git-core curl python-pip libssl-dev bc 
libelf-dev git-lfs python-pip git-core curl clang libncurses5 
libncurses5-dev


# In builder VM run:
sudo ln -s /sbin/mkdosfs /usr/local/bin/mkdosfs
sudo pip install prettytable Mako pyaml dateutils --upgrade
export _JAVA_OPTIONS="-Xmx8G"
echo 'export _JAVA_OPTIONS="-Xmx8G"' >> ~/.profile
echo "sudo swapon /tmp/swapfile" >> /rw/config/rc.local


# Download android-x86 sources:
mkdir android-x86
cd android-x86
curl https://storage.googleapis.com/git-repo-downloads/repo > repo
chmod a+x repo
sudo install repo /usr/local/bin
rm repo
git config --global user.name "Your Name"
git config --global user.email "r...@example.com"
repo init -u git://git.osdn.net/gitroot/android-x86/manifest -b oreo-x86 -m 
android-x86-8.1-r1.xml


# To add GAPPS to your build you need to add the build system, and the 
wanted sources to your manifest.
# Edit .repo/manifests/android-x86-8.1-r1.xml and add the following towards 
the end:
https://github.com/opengapps/;  />
https://gitlab.opengapps.org/opengapps/;  />









# Download sources:
repo sync --no-tags --no-clone-bundle --force-sync -j$( nproc --all )


# If you choose to add GAPPS, then edit file 
device/generic/common/device.mk and add at the beginning:
#OpenGAPPS

GAPPS_VARIANT := pico

GAPPS_PRODUCT_PACKAGES += Chrome \
KeyboardGoogle \
LatinImeGoogle \
GoogleTTS \
YouTube \
PixelIcons \
PixelLauncher \
Wallpapers \
PixelLauncherIcons \
WebViewGoogle \
GoogleServicesFramework \
GoogleLoginService \

GAPPS_FORCE_BROWSER_OVERRIDES := true
GAPPS_FORCE_PACKAGE_OVERRIDES := true

GAPPS_EXCLUDED_PACKAGES := FaceLock \
AndroidPlatformServices \
PrebuiltGmsCoreInstantApps \


# And at the end add:
#OpenGAPPS
$(call inherit-product, vendor/opengapps/build/opengapps-packages.mk)

# OpenGapps changed their repo to require git-lfs. There may be a better 
way to do this, but if you're building with GApps, this gets the right 
files. It takes awhile:
cd vendor
rm -r opengapps
git clone https://github.com/opengapps/opengapps.git
cd opengapps
git lfs install
./download_sources.sh --shallow x86_64
cd ../../

# Edit android-x86 sources for XEN compatibility:
sed -i -e 's|/sys/block/\[shv\]d\[a-z\]|/sys/block/\[shv\]d\[a-z\] 
/sys/block/xvd\[a-z\]|g' bootable/newinstaller/install/scripts/1-install
sed -i -e 's|/sys/block/\[shv\]d\$h/\$1|/sys/block/\[shv\]d\$h/\$1 
/sys/block/xvd\$h/\$1|g' bootable/newinstaller/install/scripts/1-install
sed -i -e 's|hmnsv|hmnsvx|g' bootable/newinstaller/initrd/init


# Edit android-x86 sources for Debian build environment:
sed -i -e 's|genisoimage|xorriso -as mkisofs|g' 
bootable/newinstaller/Android.mk


# Configure build target:
. build/envsetup.sh
lunch android_x86_64-userdebug


# Configure kernel:
/usr/bin/make -C kernel O=$OUT/obj/kernel ARCH=x86_64 menuconfig


# You need to edit these parameters:
XEN=yes
XEN_BLKDEV_BACKEND=yes
XEN_BLKDEV_FRONTEND=yes
XEN_NETDEV_BACKEND=no
XEN_NETDEV_FRONTEND=no
SECURITY_SELINUX_BOOTPARAM=yes
SECURITY_SELINUX_BOOTPARAM_VALUE=1
SECURITY_SELINUX_DISABLE=yes
DEFAULT_SECURITY_SELINUX=yes


# The kernel config will be in out/target/product/x86_64/obj/kernel/.config

# Also, you can edit the config to set the device type from tablet to phone.
# Edit device/generic/common/device.mk and change PRODUCT_CHARACTERISTICS 
from tablet to default:
PRODUCT_CHARACTERISTICS := default


# Start the build:
make -j$( nproc --all ) iso_img


# After you got the iso, create the android network VM. If you choose the 
android VM's netvm as sys-whonix directly, the network won't work. You need 
to have intermediate netvm between android VM and sys-whonix. Create new 
AppVM sys-android based on fedora template with netvm sys-whonix and set 
"provides network".

# Create android 

Re: [qubes-users] Qubes OS 4.0.2 has been released!

[haaber]

On 1/3/20 3:21 AM, Andrew David Wong wrote:

Dear Qubes Community,

We're pleased to announce the release of Qubes 4.0.2! This is the second
stable point release of Qubes 4.0. It includes many updates over the
initial 4.0 release, in particular:

- - All 4.0 dom0 updates to date
- - Fedora 30 TemplateVM
- - Debian 10 TemplateVM
- - Whonix 15 Gateway and Workstation TemplateVMs
- - Linux kernel 4.19 by default

Qubes 4.0.2 is available on the Downloads page:

> ...

Dear Andrew (and other users), thanks and a happy new year! I observe
since one week, that my usual update command

sudo qubes-dom0-update --enablerepo=qubes*testing

shows "no new updates available", despite this announcement and a
previous QSB announcement by Marek. Is this normal? Should I worry?
Thank you, Bernhard

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/9a5aa093-dadf-b2dc-1604-277315016aa5%40web.de.