With interest I am following this thread, thanks so far for clarification.
On 17-06-2024 12:01, David Wright wrote:
Does the noacpi affect anything else, like fans?
This question has my attention because I run an off grit network. For
those interested: https://vanderworp.org/labora-energy-acc
On Mon, 17 Jun 2024 at 10:45, Alex Johns wrote:
> On 6/17/24 20:21, David Wright wrote:
>
>
> On Mon, 17 Jun 2024 at 08:42, Alex Johns wrote:
>
>>
> Can I suggest then that you try editing the line I suggested and removing
> quiet splash and adding nomodset noacpi in the past that has solved ma
On 6/17/24 20:21, David Wright wrote:
On Mon, 17 Jun 2024 at 08:42, Alex Johns wrote:
Can I suggest then that you try editing the line I suggested and
removing quiet splash and adding nomodset noacpi in the past that has
solved many boot issues for me
good luck
cheers Chris
Hi Chris
T
On Mon, 17 Jun 2024 at 08:42, Alex Johns wrote:
>
Can I suggest then that you try editing the line I suggested and removing
quiet splash and adding nomodset noacpi in the past that has solved many
boot issues for me
good luck
cheers Chris
Hi Chris
That has worked! Thank you! For my educati
On 6/17/24 18:23, David Wright wrote:
On Sat, 15 Jun 2024 at 19:28, Alex Johns wrote:
On 6/16/24 03:15, David Wright wrote:
On Sat, 15 Jun 2024 at 02:12, Phil wrote:
On 6/14/24 22:00, David Wright wrote:
> Hi all
>
> On Saturday 8th June, I booted u
On Sat, 15 Jun 2024 at 19:28, Alex Johns wrote:
> On 6/16/24 03:15, David Wright wrote:
>
>
> On Sat, 15 Jun 2024 at 02:12, Phil wrote:
>
>>
>> On 6/14/24 22:00, David Wright wrote:
>> > Hi all
>> >
>> > On Saturday 8th June, I booted up my PC and it was fine for the couple
>> > of hours of use.
On Sat, 15 Jun 2024 at 16:55, Ralf Mardorf wrote:
> On Sat, 2024-06-15 at 17:45 +0200, Ralf Mardorf wrote:
> > remove the 'quiet' option from the kernel parameter
>
> Oops, this will not solve "the monitor showed no display found" issue.
>
> Unlikely adding 'nomodeset' will help either, but it do
On 6/16/24 03:15, David Wright wrote:
On Sat, 15 Jun 2024 at 02:12, Phil wrote:
On 6/14/24 22:00, David Wright wrote:
> Hi all
>
> On Saturday 8th June, I booted up my PC and it was fine for the
couple
> of hours of use.
>
> Next boot-up on Monday 10th June, th
On Sat, 2024-06-15 at 17:45 +0200, Ralf Mardorf wrote:
> remove the 'quiet' option from the kernel parameter
Oops, this will not solve "the monitor showed no display found" issue.
Unlikely adding 'nomodeset' will help either, but it doesn't harm to
test this option.
Does running
grep EE /var/
Hi,
remove the 'quiet' option from the kernel parameter and then manually
update with that GRUB auto-thingy again. Too funny, that a user still
needs to run the auto-thingy manually.
Btw. if you remove all that GRUB auto-crap you can edit a clean and lean
grub.cfg manually, an example is attached
On Sat, 15 Jun 2024 at 02:12, Phil wrote:
>
> On 6/14/24 22:00, David Wright wrote:
> > Hi all
> >
> > On Saturday 8th June, I booted up my PC and it was fine for the couple
> > of hours of use.
> >
> > Next boot-up on Monday 10th June, the monitor showed no display
> > found. I forced a reboot
On 6/14/24 22:00, David Wright wrote:
Hi all
On Saturday 8th June, I booted up my PC and it was fine for the couple
of hours of use.
Next boot-up on Monday 10th June, the monitor showed no display
found. I forced a reboot into recovery mode and then it booted fine.
I had exactly the same
Hi all
On Saturday 8th June, I booted up my PC and it was fine for the couple of
hours of use.
Next boot-up on Monday 10th June, the monitor showed no display found. I
forced a reboot into recovery mode and then it booted fine.
Left it on all this week but tried a re-boot this afternoon and sam
13 matches
Mail list logo
