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
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...-re5jqeeqqe8avxt
-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 fo
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/i
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
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
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
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
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.
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
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 li
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
12 matches
Mail list logo
