From: Damien Guibouret
Jan van Wijk wrote:
> Hello Damien,
>
> On Mon, 12 Dec 2016 20:01:47 +0100 Damien Guibouret wrote:
>
>>
>>Jan, something you can try (if you can easily perform this), you can change
the
>>kernel to use a not FAT32 one, as this check only
From: Damien Guibouret
Eddie Anderson wrote:
> "Jan van Wijk" ecomstat...@dfsee.com wrote:
>
>
>>Message: 1
>>I have seen this problems numerous times over the last 10 years,
>>starting with the 1.0 kernel, then the 1.1, and I now just verified that
>>
Jan van Wijk wrote:
> Hello Damien,
>
> On Mon, 12 Dec 2016 20:01:47 +0100 Damien Guibouret wrote:
>
>>
>>Jan, something you can try (if you can easily perform this), you can change
>>the
>>kernel to use a not FAT32 one, as this check only exists in FAT32
Eddie Anderson wrote:
> "Jan van Wijk" ecomstat...@dfsee.com wrote:
>
>
>>Message: 1
>>I have seen this problems numerous times over the last 10 years,
>>starting with the 1.0 kernel, then the 1.1, and I now just verified that
>>it still happens with the kernel that is in the 1.2 RC1 release.
>>
Rugxulo wrote:
> Hi,
>
> On Wed, Mar 30, 2016 at 6:11 AM, matthew berardi
> wrote:
>
>>let's assume UEFI+GPT is the problem, how do I fix it?
>>
>>I do usually boot UEFI
>
>
> But I'm not sure that all so-called UEFI machines even offer CSM, so
> you may be out of luck.
>
> https://en.wikiped
John Hupp wrote:
> Now that I'm looking squarely at the issue, I have not been able to
> reproduce it yet!
>
> When I was dealing with it earlier, I was experiencing (as I wrote in
> the bug report), that the error ALWAYS occurred when I had unformatted
> D: and E: partitions, and when I format
