[qubes-users] Re: Boot Problem

2019-07-27 Thread sourcexorapprentice
For the Precision, I fortunately had an Intel NIC (Precision M4700 
https://groups.google.com/forum/#!topic/qubes-users/-5Vbi5vhbms) but 
experienced the Broadcom pains too. Here's some ideas:

You can get an RTL8187 for about $5 on eBay, works great. I would remove 
the Broadcom wifi card and swap in a Realtek wifi card, disable the 
integrated NIC ethernet card in Bios, and install Qubes in legacy mode - 
not UEFI (in case you need Grub for recovery options later). In Bios, this 
should be in System configuration, Integrated NIC and uncheck those boxes 
(check the whole menu for other locations too).

If you need ethernet, then after install you can look online on how to 
install the specific Broadcom drivers into sys-net VM's template (if you 
can find a safe source). Then reboot into bios and re-enable the ethernet 
NIC, and after boot in the Qubes sys-net VM settings move the PCI bridge 
for the ethernet controller into the "selected" column and try restarting 
the VM and using the ethernet card. If it works reboot to see if everything 
is still successful. If it won't boot, then just disable ethernet again in 
Bios and try maybe switching the sys-net VM template to Debian and 
installing the drivers there in case you get the support.

On Wednesday, April 19, 2017 at 4:35:06 PM UTC-4, craig@gmail.com wrote:
>
> I am having at boot problem with my Qubes OS 3.2.  When I boot up I enter 
> the disk password and the boot process continues until it gets to the 
> line...
>
> A start job is running for Qubes NetVM startup (32s / no limit)
>
> And it hangs.  The HDD turns off and the computer will stay here never 
> booting or shutting down until you force it to turn off.  Anyone have an 
> idea of what is going on and how to fix it?
>
> Thank you,
>
> Craig
>
>

-- 
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/cbc291a6-257b-4551-9092-d240f3f238b2%40googlegroups.com.


[qubes-users] Re: Boot Problem

2019-07-10 Thread drownthepoor
On Friday, April 28, 2017 at 1:27:58 PM UTC-4, craig@gmail.com wrote:
> On Saturday, April 22, 2017 at 8:28:35 PM UTC-7, Andrew Morgan wrote:
> > On 04/22/2017 03:21 PM,
> > craig.g.jes...@gmail.com wrote:
> > > On Wednesday, April 19, 2017 at 1:35:06 PM UTC-7, 
> > > craig.g...-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
> > >> I am having at boot problem with my Qubes OS 3.2.  When I boot up I 
> > >> enter the disk password and the boot process continues until it gets to 
> > >> the line...
> > >>
> > >> A start job is running for Qubes NetVM startup (32s / no limit)
> > >>
> > >> And it hangs.  The HDD turns off and the computer will stay here never 
> > >> booting or shutting down until you force it to turn off.  Anyone have an 
> > >> idea of what is going on and how to fix it?
> > >>
> > >> Thank you,
> > >>
> > >> Craig
> > > 
> > > Thank you for your information.  Using your directions I have managed to 
> > > get into my Qubes system.  I disabled qubes-netvm.service and my system 
> > > will now shutdown and startup without any kernel command line options.  
> > > Of course this means I have no network connections to anything.  If I 
> > > enable the qubes-netvm.service and start sys-net the Qubes OS freezes up 
> > > and I have to power cycle the laptop.  How do I fix the 
> > > qubes-netvm.service?  It seems to be causing the problem but what do I 
> > > check next?
> > > 
> > > Thank you,
> > > 
> > > Craig Jesson
> > > 
> > 
> > When I was having issues with my NetVM, I backed off all my AppVMs and
> > templates (sans the NetVM) to an external drive, reinstalled QubesOS,
> > generated a new sys-net and sys-firewall, then restored all my AppVMs
> > back again. Fixed all my issues.
> > 
> > May be a good last resort if you're not sure what's the issue with the
> > NetVM.
> > 
> > Andrew
> 
> First I want to thank Manual Amador and Andrew Morgan for your help.  Using 
> Manual's advice I was able to get into my frozen laptop.  I then used 
> Andrew's advice to backup all of my vm's except for sys-net and sys-firewall. 
>  Then I reinstalled Qubes OS v. 3.2.  I have figured out what went wrong.  
> Qubes on my laptop started freezing after a recent update.  The update 
> replaced qubes-netvm.service with a new qubes-netvm.service.  This overwrote 
> changes I made to qubes-netvm.service to make my Broadcom NetXtreme BCM5761 
> Gigabit Ethernet PCIe and BCM4313 802.11bgn Wireless Network Adapter work.  
> Unfortunately I did not backup the qubes-netvm.service to document the 
> changes I made.  So I am trying to remember what I did to get these cards 
> working.  But everything I have tried has not worked.  I did the "Assigning 
> Devices" work around listed here 
> https://www.qubes-os.org/doc/assigning-devices/
> and This does not seem to matter on the BCM5761 Ethernet card.  But it does 
> seem necessary for the wireless card.  Right now I have the wireless card 
> disabled in the BIOS figuring that I will get each card working one at a 
> time.  So the Ethernet card shows up and I have it assigned to the sys-net vm 
> but it will not get an IP address.  I have live booted the laptop with 
> Knoppix and I can get an IP address and use the Internet so I know the 
> Ethernet card, the cable, and the residential gateway are all working fine so 
> it has to be some kind of configuration problem in Qubes.  Here is my Qubes 
> HCL Report...
> 
> ---
> layout:
>   'hcl'
> type:
>   'laptop'
> hvm:
>   'yes'
> iommu:
>   'yes'
> slat:
>   'yes'
> tpm:
>   'unknown'
> brand: |
>   Dell Inc.
> model: |
>   Latitude E5520
> bios: |
>   A14
> cpu: |
>   Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz
> cpu-short: |
>   FIXME
> chipset: |
>   Intel Corporation 2nd Generation Core Processor Family DRAM Controller 
> [8086:0104] (rev 09)
> chipset-short: |
>   FIXME
> gpu: |
>   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
> Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
> gpu-short: |
>   FIXME
> network: |
>   Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)
>   Broadcom Corporation NetXtreme BCM5761 Gigabit Ethernet PCIe (rev 10)
> memory: |
>   8089
> scsi: |
>   ST9500423AS  Rev: DEM1
>   DVD+-RW GT60NRev: A102
> 
> versions:
> 
> - works:
> 'FIXME:yes|no|partial'
>   qubes: |
> R3.2
>   xen: |
> 4.6.1
>   kernel: |
> 4.4.14-11
>   remark: |
> FIXME
>   credit: |
> FIXAUTHOR
>   link: |
> FIXLINK
> 
> ---
> 
> Here is my Qubes-pre-netvm.service
> 
> [Unit]
> Description=Netvm fixup
> Before=qubes-netvm.service
> 
> [Service]
> ExecStart=/bin/sh -c echo ':09:00.0 > 
> /sys/bus/pci/drivers/pciback/permissive'
> Type=oneshot
> RemainAfterExit=yes
> 
> [Install]
> WantedBy=multi-user.target
> 
> 
> Anybody have a clue as how to make my network cards work?
> 
> Thank you,
> 
> Craig Jesson

Hey, did you ever get this issue resolved? I am using a Dell Precision 
Workstation and I ONLY have the Broadcom

Re: [qubes-users] Re: boot problem on my production qubes (urgent!)

2018-04-16 Thread donoban
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 04/11/18 15:49, 'awokd' via qubes-users wrote:
> 
> I think it's related to this. My guess is, when you installed 4.0,
> it overwrote the boot menu entry in your EFI firmware, so now it
> doesn't work for 3.2. If you were using legacy mode boot for 3.2,
> try to set that first in your boot order. If EFI mode, you might
> have to boot into Qubes recovery mode (possibly from the 3.2 DVD),
> then repair the EFI boot entry. The command will be something
> like:
> 
> sudo efibootmgr -c -L Qubes32 -d /dev/sda -p 1 -l
> \\EFI\\qubes\\xen.efi
> 
> Note the "/dev/sda" and "-p 1" might vary. "-p 1" is the partition
> number for your EFI partition (and this is what might have changed
> with your 4.0 install.
> 

I also had this problem when I did my first Qubes 4 test. For avoid
fixing anytime I install Qubes 4, I renamed the Qubes 3.2 entry.

Maybe would be a good idea to default Qubes 4 to a different name to
avoid this kind of problems.
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAlrUwIYACgkQFBMQ2OPt
CKVXWg/6A4LBBn9V/RimfNrq9psvQZ9zAYUOkz1EnK4xXhBSES8DHL9trHeG0gng
4gYLbBBkNTbvDjMvbQGLnk7CqPr9XE7pwZUk5TjNlkUh9BjqG59kLlegmec6qKA6
cD82CU+nY58DKd99it4FZa8YDJRATgOwAEwI5Gvc5WKWLvvnFELFwqL2zOMCHfae
FNJt4uqKDpd2TBFQd1vtPI3qcNkRlttdgbZEvsDfEfEUh5dWpqYMtI+tGA7YAGlt
a9yc16xTI4+EwL5R9/p70rldUVQJBK8ZpsteaFY6ShsNpPWucd9P9M+j8/PpgvuH
T1C7fdTGN9/9f4SdKzXkGwTkR6+IrslY8Cd4/lPvGcgKAbjqU0KshIKJcEyTm46G
O52fmHue+XMcB3P+3JUHzXRakQWrGT6U2vltI2VPg7mWI7ufNZl81ZAaZMsNJl8S
tKp9e3i1VSBg1Bf7IUuxdh9vX9HxKMnagbzTVvSuc36FePcAD+rISXcUKUysp83b
UfHR3PoNmWLXcu8c90IElEE4JTd2kQgAGAD2EPP7mlDliikkyDvBv0zwhz/A83vK
YDF2zN68gU68lgeWDc6f/pn1j+szvSYb5sKQaxpcb4qWmw+Qf/gb0NvY8lR1VPUd
WeY7Xyu4ytpTCq19HA1eipQAVQljDMCUbYfAkyH1wQ7FF5fr+Jc=
=JdcM
-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/a60b487f-c65e-4361-297d-66309904a501%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: boot problem on my production qubes (urgent!)

2018-04-11 Thread '97a6sd67fs9' via qubes-users
Thanks a lot guys! It works again and I learned something new...

The Qubes 4.0 installation changed the EFI boot entry. With the following 
command I fixed it:

"efibootmgr -v -c -L Qubes -l /EFI/qubes/xen.efi -d /dev/nvme0n1p1"

(With hint from awokd and 
https://github.com/QubesOS/qubes-issues/issues/2381#issuecomment-294405605)

See you


‐‐‐ Original Message ‐‐‐

On April 11, 2018 3:49 PM, 'awokd' via qubes-users 
 wrote:

> On Wed, April 11, 2018 1:17 pm, berto0...@gmail.com wrote:
> 
> > On Wednesday, April 11, 2018 at 7:05:04 PM UTC+7, 97a6sd67fs9 wrote:
> > 
> > > In order not to ruin my 3.2 production installation I bought a new NVME
> > > 
> > > SSD. After disk replacement I installed Qubes 4.0 and test my needs.
> > > 
> > > Then I put the old SSD back in and now my PC doesn't start anymore. It
> > > 
> > > hangs on the boot menu screen (Lenovo T460s) and when I enter into
> > > 
> > > "Qubes" or the SSD device, it only refresh the screen.
> > 
> > Have you connected any other storage devices to your machine? That might
> > 
> > mess up the the device names if the configs don't use the device UUIDs.
> 
> I think it's related to this. My guess is, when you installed 4.0, it
> 
> overwrote the boot menu entry in your EFI firmware, so now it doesn't work
> 
> for 3.2. If you were using legacy mode boot for 3.2, try to set that first
> 
> in your boot order. If EFI mode, you might have to boot into Qubes
> 
> recovery mode (possibly from the 3.2 DVD), then repair the EFI boot entry.
> 
> The command will be something like:
> 
> sudo efibootmgr -c -L Qubes32 -d /dev/sda -p 1 -l \EFI\qubes\xen.efi
> 
> Note the "/dev/sda" and "-p 1" might vary. "-p 1" is the partition number
> 
> for your EFI partition (and this is what might have changed with your 4.0
> 
> install.
> 
> 
> 
> 
> 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/985f2785ea76ae44e0dfa2171bc4acc2.squirrel%40tt3j2x4k5ycaa5zt.onion.
> 
> 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/O3qglD8oiigND-m-a0bQQGtxUJhY0DECnSt_Y49FEqfoX74yFJ45M3JcW8s6_3o8UsN5FLOTPExRmnLDK4dIe-I8YxWXKspKzwtM4hC_AEU%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: boot problem on my production qubes (urgent!)

2018-04-11 Thread 'awokd' via qubes-users
On Wed, April 11, 2018 1:17 pm, berto0...@gmail.com wrote:
> On Wednesday, April 11, 2018 at 7:05:04 PM UTC+7, 97a6sd67fs9 wrote:
>
>
>> In order not to ruin my 3.2 production installation I bought a new NVME
>> SSD. After disk replacement I installed Qubes 4.0 and test my needs.
>> Then I put the old SSD back in and now my PC doesn't start anymore. It
>> hangs on the boot menu screen (Lenovo T460s) and when I enter into
>> "Qubes" or the SSD device, it only refresh the screen.
>>
>
> Have you connected any other storage devices to your machine? That might
> mess up the the device names if the configs don't use the device UUIDs.

I think it's related to this. My guess is, when you installed 4.0, it
overwrote the boot menu entry in your EFI firmware, so now it doesn't work
for 3.2. If you were using legacy mode boot for 3.2, try to set that first
in your boot order. If EFI mode, you might have to boot into Qubes
recovery mode (possibly from the 3.2 DVD), then repair the EFI boot entry.
The command will be something like:

sudo efibootmgr -c -L Qubes32 -d /dev/sda -p 1 -l \\EFI\\qubes\\xen.efi

Note the "/dev/sda" and "-p 1" might vary. "-p 1" is the partition number
for your EFI partition (and this is what might have changed with your 4.0
install.

-- 
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/985f2785ea76ae44e0dfa2171bc4acc2.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: boot problem on my production qubes (urgent!)

2018-04-11 Thread berto00000001
On Wednesday, April 11, 2018 at 8:36:23 PM UTC+7, 97a6sd67fs9 wrote:
> Pure notebook only.
> 
> Maybe I have to repair the boot sector or grub? I don't know how...
> 
Have a look at https://www.supergrubdisk.org/ . I haven't tried it out myself, 
yet.

-- 
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/ecc0575e-df6f-402a-aec1-821a9feb1ad2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: boot problem on my production qubes (urgent!)

2018-04-11 Thread '97a6sd67fs9' via qubes-users
Pure notebook only.

Maybe I have to repair the boot sector or grub? I don't know how...

 Original Message 
On 11 Apr 2018, 15:17, wrote:

> On Wednesday, April 11, 2018 at 7:05:04 PM UTC+7, 97a6sd67fs9 wrote:
>
>> In order not to ruin my 3.2 production installation I bought a new NVME SSD. 
>> After disk replacement I installed Qubes 4.0 and test my needs. Then I put 
>> the old SSD back in and now my PC doesn't start anymore. It hangs on the 
>> boot menu screen (Lenovo T460s) and when I enter into "Qubes" or the SSD 
>> device, it only refresh the screen.
>
> Have you connected any other storage devices to your machine? That might mess 
> up the the device names if the configs don't use the device UUIDs.
>
> --
> 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/d22b0749-57ad-45c1-a674-554383194f00%40googlegroups.com.
> 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/4jiE0Wxpka81yVYSNHkT44GtPlF9wTe8Ec_b-Q3vRdnxLrhced1qgtHdu8TuXtFAIYGhVmZcFx1zAmt58xQLoZ0gz5Q4XKSlh3S-r1uCwHA%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: boot problem on my production qubes (urgent!)

2018-04-11 Thread berto00000001
On Wednesday, April 11, 2018 at 7:05:04 PM UTC+7, 97a6sd67fs9 wrote:

> In order not to ruin my 3.2 production installation I bought a new NVME SSD. 
> After disk replacement I installed Qubes 4.0 and test my needs. Then I put 
> the old SSD back in and now my PC doesn't start anymore. It hangs on the boot 
> menu screen (Lenovo T460s) and when I enter into "Qubes" or the SSD device, 
> it only refresh the screen.

Have you connected any other storage devices to your machine? That might mess 
up the the device names if the configs don't use the device UUIDs.

-- 
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/d22b0749-57ad-45c1-a674-554383194f00%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Boot Problem

2017-04-28 Thread craig . g . jesson
On Saturday, April 22, 2017 at 8:28:35 PM UTC-7, Andrew Morgan wrote:
> On 04/22/2017 03:21 PM,
> craig.g.jes...@gmail.com wrote:
> > On Wednesday, April 19, 2017 at 1:35:06 PM UTC-7, 
> > craig.g...-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
> >> I am having at boot problem with my Qubes OS 3.2.  When I boot up I enter 
> >> the disk password and the boot process continues until it gets to the 
> >> line...
> >>
> >> A start job is running for Qubes NetVM startup (32s / no limit)
> >>
> >> And it hangs.  The HDD turns off and the computer will stay here never 
> >> booting or shutting down until you force it to turn off.  Anyone have an 
> >> idea of what is going on and how to fix it?
> >>
> >> Thank you,
> >>
> >> Craig
> > 
> > Thank you for your information.  Using your directions I have managed to 
> > get into my Qubes system.  I disabled qubes-netvm.service and my system 
> > will now shutdown and startup without any kernel command line options.  Of 
> > course this means I have no network connections to anything.  If I enable 
> > the qubes-netvm.service and start sys-net the Qubes OS freezes up and I 
> > have to power cycle the laptop.  How do I fix the qubes-netvm.service?  It 
> > seems to be causing the problem but what do I check next?
> > 
> > Thank you,
> > 
> > Craig Jesson
> > 
> 
> When I was having issues with my NetVM, I backed off all my AppVMs and
> templates (sans the NetVM) to an external drive, reinstalled QubesOS,
> generated a new sys-net and sys-firewall, then restored all my AppVMs
> back again. Fixed all my issues.
> 
> May be a good last resort if you're not sure what's the issue with the
> NetVM.
> 
> Andrew

First I want to thank Manual Amador and Andrew Morgan for your help.  Using 
Manual's advice I was able to get into my frozen laptop.  I then used Andrew's 
advice to backup all of my vm's except for sys-net and sys-firewall.  Then I 
reinstalled Qubes OS v. 3.2.  I have figured out what went wrong.  Qubes on my 
laptop started freezing after a recent update.  The update replaced 
qubes-netvm.service with a new qubes-netvm.service.  This overwrote changes I 
made to qubes-netvm.service to make my Broadcom NetXtreme BCM5761 Gigabit 
Ethernet PCIe and BCM4313 802.11bgn Wireless Network Adapter work.  
Unfortunately I did not backup the qubes-netvm.service to document the changes 
I made.  So I am trying to remember what I did to get these cards working.  But 
everything I have tried has not worked.  I did the "Assigning Devices" work 
around listed here https://www.qubes-os.org/doc/assigning-devices/
and This does not seem to matter on the BCM5761 Ethernet card.  But it does 
seem necessary for the wireless card.  Right now I have the wireless card 
disabled in the BIOS figuring that I will get each card working one at a time.  
So the Ethernet card shows up and I have it assigned to the sys-net vm but it 
will not get an IP address.  I have live booted the laptop with Knoppix and I 
can get an IP address and use the Internet so I know the Ethernet card, the 
cable, and the residential gateway are all working fine so it has to be some 
kind of configuration problem in Qubes.  Here is my Qubes HCL Report...

---
layout:
  'hcl'
type:
  'laptop'
hvm:
  'yes'
iommu:
  'yes'
slat:
  'yes'
tpm:
  'unknown'
brand: |
  Dell Inc.
model: |
  Latitude E5520
bios: |
  A14
cpu: |
  Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz
cpu-short: |
  FIXME
chipset: |
  Intel Corporation 2nd Generation Core Processor Family DRAM Controller 
[8086:0104] (rev 09)
chipset-short: |
  FIXME
gpu: |
  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
gpu-short: |
  FIXME
network: |
  Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)
  Broadcom Corporation NetXtreme BCM5761 Gigabit Ethernet PCIe (rev 10)
memory: |
  8089
scsi: |
  ST9500423AS  Rev: DEM1
  DVD+-RW GT60NRev: A102

versions:

- works:
'FIXME:yes|no|partial'
  qubes: |
R3.2
  xen: |
4.6.1
  kernel: |
4.4.14-11
  remark: |
FIXME
  credit: |
FIXAUTHOR
  link: |
FIXLINK

---

Here is my Qubes-pre-netvm.service

[Unit]
Description=Netvm fixup
Before=qubes-netvm.service

[Service]
ExecStart=/bin/sh -c echo ':09:00.0 > 
/sys/bus/pci/drivers/pciback/permissive'
Type=oneshot
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target


Anybody have a clue as how to make my network cards work?

Thank you,

Craig Jesson

-- 
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/d10f7c65-fe73-4b6e-ada8-ce9bd2cff29b%40googlegroups.com.
For more options, visit https://groups.google.com/d

[qubes-users] Re: Boot Problem

2017-04-22 Thread Andrew Morgan
On 04/22/2017 03:21 PM,
craig.g.jes...@gmail.com wrote:
> On Wednesday, April 19, 2017 at 1:35:06 PM UTC-7, 
> craig.g...-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
>> I am having at boot problem with my Qubes OS 3.2.  When I boot up I enter 
>> the disk password and the boot process continues until it gets to the line...
>>
>> A start job is running for Qubes NetVM startup (32s / no limit)
>>
>> And it hangs.  The HDD turns off and the computer will stay here never 
>> booting or shutting down until you force it to turn off.  Anyone have an 
>> idea of what is going on and how to fix it?
>>
>> Thank you,
>>
>> Craig
> 
> Thank you for your information.  Using your directions I have managed to get 
> into my Qubes system.  I disabled qubes-netvm.service and my system will now 
> shutdown and startup without any kernel command line options.  Of course this 
> means I have no network connections to anything.  If I enable the 
> qubes-netvm.service and start sys-net the Qubes OS freezes up and I have to 
> power cycle the laptop.  How do I fix the qubes-netvm.service?  It seems to 
> be causing the problem but what do I check next?
> 
> Thank you,
> 
> Craig Jesson
> 

When I was having issues with my NetVM, I backed off all my AppVMs and
templates (sans the NetVM) to an external drive, reinstalled QubesOS,
generated a new sys-net and sys-firewall, then restored all my AppVMs
back again. Fixed all my issues.

May be a good last resort if you're not sure what's the issue with the
NetVM.

Andrew

-- 
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/odh70h%24bhg%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature


[qubes-users] Re: Boot Problem

2017-04-22 Thread craig . g . jesson
On Wednesday, April 19, 2017 at 1:35:06 PM UTC-7, craig.g...@gmail.com wrote:
> I am having at boot problem with my Qubes OS 3.2.  When I boot up I enter the 
> disk password and the boot process continues until it gets to the line...
> 
> A start job is running for Qubes NetVM startup (32s / no limit)
> 
> And it hangs.  The HDD turns off and the computer will stay here never 
> booting or shutting down until you force it to turn off.  Anyone have an idea 
> of what is going on and how to fix it?
> 
> Thank you,
> 
> Craig

Thank you for your information.  Using your directions I have managed to get 
into my Qubes system.  I disabled qubes-netvm.service and my system will now 
shutdown and startup without any kernel command line options.  Of course this 
means I have no network connections to anything.  If I enable the 
qubes-netvm.service and start sys-net the Qubes OS freezes up and I have to 
power cycle the laptop.  How do I fix the qubes-netvm.service?  It seems to be 
causing the problem but what do I check next?

Thank you,

Craig Jesson

-- 
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/1e85e5a8-9ab2-4e4a-ac71-98af0ed2579d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: boot problem after switching bios from uefi to legacy to uefi

2017-02-19 Thread joe . m

 Quoting jo...@vfemail.net:


hi.
since i saw multiple people posting things about aem, i thought i would
also setup aem.

i looked at


https://github.com/QubesOS/qubes-antievilmaid/blob/master/anti-evil-maid/README

and saw i need to use legacy.
i installed my system while booting uefi and then switched to legacy.
i was not sure whether the system could boot again, but if it did not
boot, i would switch back again.

after switching to legacy, the system did not boot (i am not sure wheter
it should boot normally after switchin, of if that does not work).
after switching back to uefi, it still does not boot
is there a way to fix this?

also when looking at the bios, i did not find an option for TPM or TXT.
but there is some stuff like secure boot mode/control with pks (could
this be it?)
or does my laptop mybe not have this feature?

some system info:
msigp60
bios version E16GDIMS.30B (build date: 23/08/2013)

should i update the bios? (maybe the old bios version does not display
the tpm option)

i am grateful for any ideas.
wit best regards.
joe mitchell


managed to fix this!

the problem seems to be:
efi forgot the entry

i found a guide via:
https://forums.linuxmint.com/viewtopic.php?t=204585#p1063821
-> http://www.rodsbooks.com/efi-bootloaders/installation.html#register

here my guide for perople as stupid as me. (maybe you can add this to
your doc)
1) create a qubes install media (have fun verifying the master key again)
2) boot it and select the recovery entry (last entry)
3) select continue (oprion 1)
4) enter your key
5) hit enter (to get a shell)
6) chroot /mnt/sysimage
7) fdisk -l to find your efi dev (we assume it is /dev/sda1)
8) use efibootmgrt to fix your efi.
efibootmgr -c -d /dev/sda -p 1 -l \\EFI\\qubes\\xen.efi -L qubes
9) reboot

on lenovo you may have to use a different name.
according to  
http://www.rodsbooks.com/efi-bootloaders/installation.html#register :
'Also note that at least one manufacturer (Lenovo) ships products with  
a known bug that causes the system to refuse to boot unless the boot  
loader's name (NewLoader in this example) is either Windows Boot  
Manager or Red Hat Enterprise Linux.'


with best regards.
joe mitchell

ps.: does someone know a good mail-provider where you can create an  
anonymous free account (via tor and no phone number etc required).
openmailbox has currently disabled new accounts and vfemail delays my  
last mail by 11h (currently the delay is only 6717 seconds, so this  
seemed to be a temp problem)



-

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  


--
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/20170219023552.Horde.WZB9k2CzXiZKhWBofZ4KUQ1%40www.vfemail.net.
For more options, visit https://groups.google.com/d/optout.