On 7/2/19 8:39 AM, Aere Greenway wrote:
> On 6/27/19 10:46 PM, Kai-Heng Feng wrote:
>> Ah, please try kernel parameter "nopti".
>>
> As I indicated in my earlier feedback, I tried that, and it didn't
> affect the problem.
>
I tried adding the nopti kernel parameter today, in particular, to the
default entry, and it seemed to work, though at least once, it didn't
work, but perhaps I did something wrong.
In an attempt to remove that variability, I made changes to permanently
apply the nopti parameter, and that has been working consistently, on
all 5 machines it was failing on.
Those 5 machines experiencing the problem (all of them i386), were:
Dell GX240
Dell GX260
Dell GX270
MacBook (1,1) 32-bit
HP-Mini
Anyway, applying the 'nopti' kernel parameter in a persistent way,
appears to have solved the problem.
On 7/2/19 8:39 AM, Aere Greenway wrote:
> On 6/27/19 10:46 PM, Kai-Heng Feng wrote:
>> Ah, please try kernel parameter "nopti".
>>
> As I indicated in my earlier feedback, I tried that, and it didn't
> affect the problem.
>
I tried adding the nopti kernel parameter today, in particular, to the
default entry, and it seemed to work, though at least once, it didn't
work, but perhaps I did something wrong.
In an attempt to remove that variability, I made changes to permanently
apply the nopti parameter, and that has been working consistently, on
all 5 machines it was failing on.
Those 5 machines experiencing the problem (all of them i386), were:
Dell GX240
Dell GX260
Dell GX270
MacBook (1,1) 32-bit
HP-Mini
Anyway, applying the 'nopti' kernel parameter in a persistent way,
appears to have solved the problem.
--
Sincerely,
Aere