Amelia A Lewis [amyz...@talsever.com] wrote:
>
> Can anyone suggest why a machine, with no activity but ssh logins and
> then a syspatch of patches 2-3 on 6.8 would spontaneously start
> considering the SATA disks in the machine (which were previously loaded
> as sd0-sd2) as IDE (wd0-wd2)?
On Fri, 30 Oct 2020 16:42:18 -0700, Chris Cappuccio wrote:
> Amelia A Lewis [amyz...@talsever.com] wrote:
[snip]
>
> Perhaps the CMOS battery failed and the BIOS reverted to a default setting.
-and-
On Fri, 30 Oct 2020 15:05:23 -0700, obs...@loopw.com wrote:
> My guess is that the nvram of the
My guess is that the nvram of the bios somehow reset its configuration back to
default. (corruption, power loss, etc. - these are cheap parts made with
failure rates after all)
The default of most x86 bioses up until the last few years was to bring up SATA
ports in IDE compatible mode, which
> I remember Theo(?) mentioning this about a MacBookAir some time ago.
Oops, that was jsg, sorry Theo:
http://www.undeadly.org/cgi?action=article=20130608064453
On Fri, 30 Oct 2020 14:43:12 -0600, John McGuigan wrote:
> Two things that jump to mind are weirdness with Apple hardware (not sure
> this is the case or not) but I recall that in Bootcamp mode the EFI displays
> IDE devices instead of SATA in some cases. I remember Theo(?) mentioning
> this about
Ahoy!
Two things that jump to mind are weirdness with Apple hardware (not sure
this is the case or not) but I recall that in Bootcamp mode the EFI displays
IDE devices instead of SATA in some cases. I remember Theo(?) mentioning
this about a MacBookAir some time ago.
The other is if you've
Heylas again,
So, I have a working machine again, after copying a kernel over from a
working machine, verifying it, and generating a new hash (I have a
whole long saga of investigation, but I'll spare you).
Can anyone suggest why a machine, with no activity but ssh logins and
then a syspatch
7 matches
Mail list logo
