[qubes-users] Re: failed Qubes 4.0.3 install on Dell Inspiron 14 5485

2020-02-10 Thread fiftyfourthparallel
Fellow Dell Inspiron user here,

Your problems are different from mine, and I'm no expert, but maybe the 
simple solution that worked for me might work for you:

Mount the ANACONDA partition of the Qubes boot USB, then edit BOOTX64.cfg 
so that kernel parameters include 'nouveau.modeset=0'

-- 
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/9a4c0edc-4e6c-4b7c-968b-b0929396ca54%40googlegroups.com.


[qubes-users] Chromium OS in qubes

2020-02-10 Thread Dominique St-Pierre Boucher
Hello Qubes Users,

Did anyone tried or better succeeded in installing Chromium OS in qubes? 

Thanks

Dominique

-- 
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/1d7c64a2-9fbb-48d8-99d9-68e6b6c276cc%40googlegroups.com.


[qubes-users] failed Qubes 4.0.3 install on Dell Inspiron 14 5485

2020-02-10 Thread 'aihey' via qubes-users
Hi there,

I've been trying to install the latest release of Qubes (4.0.3) into a Dell 
Inspiron 14 5485 laptop (spec below) but having a few problems. I've followed 
the 'Installation Guide' to setup the correct BIOS configuration (AMD 
virtualization enabled and secure boot disabled) and load the ISO image of 
Qubes into a USB drive using the dd tool. I've tried a few BIOS configurations 
which problems I'll describe below:

1) default behaviour (UEFI mode): on boot I press F12 to choose boot media and 
select USB flash. The installation start and prints a couple of messages but 
then goes to a blank screen and freezes;
2) legacy mode: on boot I press F12 and choose the USB drive. It opens a pop-up 
with 3 options- install Qubes, test USB media and install Qubes or 
troubleshooting. Inside troubleshooting you've a few other options, including 
installing Qubes in graphics mode. The test media option doesn't display any 
messages (freezes straight away). If you choose any of the installation 
options, it will start printing messages but then shows a blank screen and 
freezes;
3) legacy mode: pressed TAB in the installation dialogue and edited the command 
to trigger display of more information (console=vga and removal of 'noerror' 
flag). The installation still frezed but I was able to read the last message 
(an error related with ACPI).
4) legacy mode (console=vga, 'noerror' flag removed and acpi=off): introduced 
acpi=off in the installation command. Was able to go a bit further but the 
installation still freezed.
5) I've also followed the instructions in 
https://www.qubes-os.org/doc/uefi-troubleshooting/ (2 and 3 sections) but had 
no success (both in UEFI or legacy modes);
6) there is a setting in the BIOS for fast boot (options are minimal, Auto or 
through). None of these seem to make a difference both in UEFI or Legacy modes.

Any ideas of what I could be doing wrong or other things to try? Happy to give 
more information if required.

Thanks

---

Machine:   Type: Laptop System: Dell product: Inspiron 5485 v: 2.1.0 serial: 
 Chassis:
   type: 10 v: 2.1.0 serial: 
   Mobo: Dell model: 0RWVK3 v: A00 serial:  UEFI: Dell v: 2.1.0 
date: 04/12/2019
Battery:   ID-1: BAT0 charge: 6.5 Wh condition: 39.4/42.0 Wh (94%) volts: 
11.7/11.4
   model: SMP-ATL-3.61 DELL VM73283 serial:  status: Charging
CPU:   Topology: Quad Core model: AMD Ryzen 5 3500U with Radeon Vega Mobile 
Gfx bits: 64
   type: MT MCP arch: Zen rev: 1 L2 cache: 2048 KiB
   flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
bogomips: 33538
   Speed: 1223 MHz min/max: 1400/2100 MHz Core speeds (MHz): 1: 1223 2: 
1222 3: 1223
   4: 1222 5: 1223 6: 1223 7: 1222 8: 1222
Graphics:  Device-1: AMD Picasso vendor: Dell driver: amdgpu v: kernel bus ID: 
05:00.0
   chip ID: 1002:15d8
   Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
   resolution: 1920x1080~60Hz
   OpenGL: renderer: AMD RAVEN (DRM 3.33.0 5.3.0-28-generic LLVM 9.0.0) 
v: 4.5 Mesa 19.2.8
   direct render: Yes
Audio: Device-1: AMD vendor: Dell driver: snd_hda_intel v: kernel bus ID: 
05:00.1
   chip ID: 1002:15de
   Device-2: AMD vendor: Dell driver: snd_hda_intel v: kernel bus ID: 
05:00.6
   chip ID: 1022:15e3
   Sound Server: ALSA v: k5.3.0-28-generic
Network:   Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter 
vendor: Dell
   driver: ath10k_pci v: kernel bus ID: 02:00.0 chip ID: 168c:0042
   IF: wlp2s0 state: up mac: 
   Device-2: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169 
v: kernel port: 2000
   bus ID: 03:00.0 chip ID: 10ec:8136
   IF: enp3s0 state: down mac: 
   Device-3: Atheros type: USB driver: btusb bus ID: 3-2.3:3 chip ID: 
0cf3:e009
   IF-ID-1: orpheu-laptop state: unknown speed: N/A duplex: N/A mac: N/A
Drives:Local Storage: total: 523.04 GiB used: 40.97 GiB (7.8%)
   ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB 
size: 465.76 GiB
   speed: 31.6 Gb/s lanes: 4 serial: 
   ID-2: /dev/sda type: USB vendor: SanDisk model: Ultra Fit size: 
57.28 GiB
   serial: 
Partition: ID-1: / size: 455.31 GiB used: 40.72 GiB (8.9%) fs: ext4 dev: 
/dev/dm-1
   ID-2: /boot size: 704.5 MiB used: 245.0 MiB (34.8%) fs: ext4 dev: 
/dev/nvme0n1p2
   ID-3: swap-1 size: 980.0 MiB used: 1024 KiB (0.1%) fs: swap dev: 
/dev/dm-2
Sensors:   System Temperatures: cpu: 58.9 C mobo: 38.0 C sodimm: 48.0 C
   Fan Speeds (RPM): cpu: 2562

-- 
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 

Re: [qubes-users] sys-firewall based on debian-10-minimal not recognized

2020-02-10 Thread 'awokd' via qubes-users
Sven Semmler:
> On Sun, Feb 09, 2020 at 01:46:12PM +, 'awokd' via qubes-users wrote:
>> Maybe it doesn't like the "disposable" part? Try it with a regular AppVM
>> based on that same minimal template.
> 
> I did: makes no difference. Also I've been running debian-based and
> fedora-based disposable sys-firewall for years. It has most likely to do
> with the -minimal template and me being oblivious to what the Qubes
> Manger looks for. 

I had double-checked my debian-10-minimal firewall template against the
packages you installed and they matched, so I'm trying to think what
else is different. Maybe because you manually edited the rules? I've
seen that confuse the GUI before.

> After verifying that the firewall does indeed work and does what it's
> supposed to do I see this as a minor annoyance. I saw some discussion on
> github about how the Qubes Manager recognizes firewall functionality but
> all those things I already checked - I think (see previous postings).
> 
> Could you point out to me please how I would verify that the qubes-firewall 
> service is up and running?

Systemctl in sys-firewall tells me qubes-firewall.service is "loaded
active running", if that helps.

-- 
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

-- 
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/bcebe0c4-2a47-fe4b-cd9c-ff36c857cad5%40danwin1210.me.


Re: [qubes-users] Re: Upgrade to 16 GB RAM for an X230

2020-02-10 Thread brendan . hoar
Two inter-related arguments for switching to Coreboot so that one can replace 
an Intel wireless card with another card:

1. Lenovo BIOS generally has a small whitelist of WiFi cards that work and 
block all others.

2. Presumably the reason for this whitelist is support for AMT “out of band and 
silent” organizational inventory, configuration and tracking of laptops 
regardless of what OS it is running (e.g. even after wipe). The BIOS only has 
drivers for specific intel WiFi and Ethernet chipsets and can only “phone home” 
using known networking hardware. 

If you avoid the in-built Ethernet and the factory specified WiFi cards, it is 
much more difficult to leverage AMT and similar technologies for remote control 
and tracking of a device. Not impossible but more difficult.

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/601ce3bf-4b86-4613-8711-041ad4f5d07f%40googlegroups.com.


Re: [qubes-users] Re: Upgrade to 16 GB RAM for an X230

2020-02-10 Thread unman
On Mon, Feb 10, 2020 at 05:22:37AM -0800, ggg...@gmail.com wrote:
> Thanks to all who replied.   I have the X230 in hand now.   It was promised 
> to be in A condition, (for $228.00, taxes included and at my door)   Looks 
> brand new.
> 
> Thanks for the advice on the Clip, I suspect I will end up repeating the 
> process on the same laptop.  Nothing goes well for me the first time. 
> Just as verification:   You have flashed one with an I5 processor.  I was 
> thinking of replacing the processor in a Chromebook, Mr Chromebox advised 
> his version of Core Boot would not work if I did, but I might get away with 
> changing the SSD.  My brother used to make a living repairing PC boards, 
> and felt with the right tools it would not be a problem.   I am guessing 
> that the processor in X230 is not soldered in.  More likely it is still 
> cheaper to buy a new X230 than to buy both RAM and an I7 processor.  
> 

I have flashed an i5 x230.
The x230 chip is soldered in and not swappable.

> I do not know the advantage of the Atheros Wireless chip over the one which 
> came in device.   I know that the folks who rebuild the Thinkpad X230 to 
> meet the Qubes certification test, change it.  So I blindly go along 
> thinking they had a good reason.  
> 
> If I looked a bit, it might be freeware software versus a blob.  It might 
> be the Atheros chip is faster, more reliable. or the original install chip 
> does not do dual band.

The Atheros chip uses free drivers, in kernel. The Intel chip requires
Intel drivers, not free.

> 
> On another forum I see someone who said that the BIOS would show if the RAM 
> was in Dual Channel Mode, which might not be the same as Interleaved.  Or 
> one could use CPU-Z, freeware application is for Windows or Android.   
> (hmm, can Windows start with Core Boot?) Long ago someone defined 
> Interleaved memory to me as if the memory is interleaved once, it 
> effectively doubles the speed of the CPU.   However that was the old core 
> doughnut memory.   I would be glad if someone could clarify.
> 
Yes, Windows can start with coreboot. I expect there's a Linux
alternative to CPU-Z - quick ddg suggests "CPU-X"?

Interleaved memory just means that the memory addresses are spread
across the modules. This has nothing to do with Dual Channel, which
increases the transfer rate between the RAM and the controller. I don't
think the lenovo BIOS will show interleaved status.
As I said before, it's designed to work interleaved if possible. If the
modules are matched, it will be interleaved.
It certainly wont double the CPU speed.

> Thanks for the replies.  I now know the direction I should go.  If I have 
> the money.
> 
> 

-- 
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/20200210135114.GA12510%40thirdeyesecurity.org.


Re: [qubes-users] Re: Upgrade to 16 GB RAM for an X230

2020-02-10 Thread ggg397
Thanks to all who replied.   I have the X230 in hand now.   It was promised 
to be in A condition, (for $228.00, taxes included and at my door)   Looks 
brand new.

Thanks for the advice on the Clip, I suspect I will end up repeating the 
process on the same laptop.  Nothing goes well for me the first time. 
Just as verification:   You have flashed one with an I5 processor.  I was 
thinking of replacing the processor in a Chromebook, Mr Chromebox advised 
his version of Core Boot would not work if I did, but I might get away with 
changing the SSD.  My brother used to make a living repairing PC boards, 
and felt with the right tools it would not be a problem.   I am guessing 
that the processor in X230 is not soldered in.  More likely it is still 
cheaper to buy a new X230 than to buy both RAM and an I7 processor.  

I do not know the advantage of the Atheros Wireless chip over the one which 
came in device.   I know that the folks who rebuild the Thinkpad X230 to 
meet the Qubes certification test, change it.  So I blindly go along 
thinking they had a good reason.  

If I looked a bit, it might be freeware software versus a blob.  It might 
be the Atheros chip is faster, more reliable. or the original install chip 
does not do dual band.

On another forum I see someone who said that the BIOS would show if the RAM 
was in Dual Channel Mode, which might not be the same as Interleaved.  Or 
one could use CPU-Z, freeware application is for Windows or Android.   
(hmm, can Windows start with Core Boot?) Long ago someone defined 
Interleaved memory to me as if the memory is interleaved once, it 
effectively doubles the speed of the CPU.   However that was the old core 
doughnut memory.   I would be glad if someone could clarify.

Thanks for the replies.  I now know the direction I should go.  If I have 
the money.





-- 
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/0e75e2bf-60aa-4574-8bdd-50f97f4e5923%40googlegroups.com.


Re: [qubes-users] create custom image result in problems with python-blivet sources

2020-02-10 Thread Frédéric Pierret
Hello,
You need the src.rpm. Else, you can use the branch in the PR 
https://github.com/QubesOS/qubes-blivet/pull/4
Best,
Frédéric

On 2020-02-09 19:16, user74...@disroot.org wrote:
> Hello.
> 
> thanks for your hints, but i need a little more help.
> The actual versions in fc31 are:
> - python3-blivet-3.1.5-2.fc31.noarch.rpm
> - python3-blivet-3.1.7-1.fc31.noarch.rpm
> 
> If i look for a matching storaged-project/blivet version then i don't find 
> the file blivet-xxx-tests.tar.gz.
> The only version with the test-archive is 3.2.0. This version would be 
> available in fc rawhide.
> And do i need the existing patches or some others?
> 
> I'm now not sure how i can solve this situation. 
> This is the first time for me to use the qubes-builder, can someone help me?
> 
> Thanks
> 
> 
>> Hello,
>> Do a 'make get-sources' in blivet repo. The pull of sources is done once 
>> during the global get sources. Here the problem is that we use SRPM from 
>> fedora repositories but they are not keeping all the versions. In 
>> consequence, we currently need to sync with Fedora update.
>>
>> Best,
>> Frédéric
>>
>> Le 8 février 2020 14:35:10 GMT+01:00, user74...@disroot.org a écrit :
>>> Hello,
>>> i'm trying to create a custom qubes image to install a fedora 31 dom0
>>> using https://www.qubes-os.org/doc/qubes-builder/ 
>>> (mailto:qubes-users+nore...@googlegroups.com)to see how it will run on
>>> my hardware.
>>> Already the step 'make get-sources' show the following problem up:
>>> --> Downloading additional sources for blivet...
>>> Cannot find source RPM: python-blivet-3.1.6-1.fc31.src.rpm
>>> make[1]: *** [Makefile:21: blivet-3.1.6.tar.gz.UNTRUSTED] Error 1
>>> make: *** [Makefile:205: blivet.get-sources-extra] Error 2
>>>
>>> I've tried to solve this with a newer version 3.1.7, but then there are
>>> the test-src's... missing while building.
>>> Please give me some hints to solve my problem .
>>> 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/649a6a486daecf809d99c69427baeff5%40disroot.org.
>> -- 
>> Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
>> brièveté.
> 

-- 
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/994ab7e0-3b68-2d87-f17e-0ce0b5c0be79%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature