I have to say from a user experience... figuring that all out was hell.
When you look at what I did.. I essentially added 2 main bits to the code
mapbs=1
noexitboot=1
I really just wonder.. if there's any reason QUBES developers couldn't just add
these 2 lines themselves, so that the user
On 10/07/16 21:59, neilhard...@gmail.com wrote:
> OK... I have found a solution.
>
> Just use QUBES 3.2
>
> ---
>
> That's it. Problem solved.
>
> It was nothing to do with EUFI or legacy boot or anything like that.
>
> As I said, I had already done all the BIOS stuff.
>
> Thanks
On 10/07/16 21:01, Frank wrote:
>
>
>> On 10.07.2016, at 19:36, donoban donoban-at-riseup.net
|qubes-mailing-list/Example Allow| wrote:
>>
>>
>>
>>> On 10/07/16 18:11, neilhard...@gmail.com wrote:
>>> OK... This is what I get
>>>
>>> ubuntu@ubuntu:~$ sudo mount
On 10/07/16 18:11, neilhard...@gmail.com wrote:
> OK... This is what I get
>
> ubuntu@ubuntu:~$ sudo mount /dev/sda1 /mnt
> ubuntu@ubuntu:~$ sudo mount /dev/sda2 /mnt
> mount: block device /dev/sda2 is write-protected, mounting read-only
> NTFS signature is missing.
> Failed to mount
On Sunday, July 10, 2016 at 1:19:09 PM UTC-4, neilh...@gmail.com wrote:
> It may be possible that I'm following the EUFI guidelines incorrectly.
>
> Replace existing Qubes entry with modified one. Replace with entry
> number from previous step, /dev/sda with your disk name and -p 1 with
>
It may be possible that I'm following the EUFI guidelines incorrectly.
Replace existing Qubes entry with modified one. Replace with entry number
from previous step, /dev/sda with your disk name and -p 1 with /boot/efi
partition number):
With this for example.. how am I supposed to
OK... This is what I get
ubuntu@ubuntu:~$ sudo mount /dev/sda1 /mnt
ubuntu@ubuntu:~$ sudo mount /dev/sda2 /mnt
mount: block device /dev/sda2 is write-protected, mounting read-only
NTFS signature is missing.
Failed to mount '/dev/sda2': Invalid argument
The device '/dev/sda2' doesn't seem to have
On 10/07/16 17:33, neilhard...@gmail.com wrote:
> In the installer, it shows the USB external HDD, and the local HDD.
>
> I am currently in a Ubuntu live disc, and in the partition manager, it shows
>
> partition -- file system -- size -- used -- flags
>
> /dev/sda1 -- ext4 -- 500MB -- 155.12MB
One thing I notice is that I used to be able to press F12, and get the HDD as a
boot option.
Now it's just missing altogether.
--
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,
In the installer, it shows the USB external HDD, and the local HDD.
I am currently in a Ubuntu live disc, and in the partition manager, it shows
partition -- file system -- size -- used -- flags
/dev/sda1 -- ext4 -- 500MB -- 155.12MB -- boot
/dev/sda2 -- crypt-luks -- 698.15GB -- N/A -- N/A
On 10/07/16 17:18, neilhard...@gmail.com wrote:
> It was all disabled from the start.
>
> It simply will not work.
>
> As I say, it can install to an external HDD just fine. Just not the local
> drive.
>
I think it has some problem with Grub (the bootloader), are you sure you
are installing
It was all disabled from the start.
It simply will not work.
As I say, it can install to an external HDD just fine. Just not the local drive.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/07/16 16:50, neilhard...@gmail.com wrote:
> My EUFI is disabled and i still get the message "bootable device
> was not found"
>
> What do i do?
>
But was UEFI enabled when you did the installation? If yes try
reinstalling, if no I don't
My EUFI is disabled and i still get the message "bootable device was not found"
What do i do?
--
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
14 matches
Mail list logo