On 07 Nov 2013, Mauro Santos wrote:
On 07-11-2013 08:56, Anthony Campbell wrote:
I was relying on my memory (affected by a heavy cold) of what had been
upgraded the previous day, before the change in boot order occurred. I
thought that linux-firmware was the most likely source but I accept
[2013-11-08 17:27:59 +] Anthony Campbell:
I see that what happened was a kernel upgrade. This
led to a lot of activity by mkinitcpio as it built the image. I don't
know if that could have altered the boot sector.
No. What may alter the boot sector is a bootloader upgrade...
--
Gaetan
On 06 Nov 2013, Gaetan Bisson wrote:
[2013-11-06 08:56:04 +] Anthony Campbell:
After an upgrade yesterday which I'm pretty sure included linux-firmware
I found that boot reversed the order
What do you mean by pretty sure? How do you know linux-firmware is to
blame? This package only
On 07-11-2013 08:56, Anthony Campbell wrote:
I was relying on my memory (affected by a heavy cold) of what had been
upgraded the previous day, before the change in boot order occurred. I
thought that linux-firmware was the most likely source but I accept that
it's unlikely. Sorry for muddying
My laptop has dual boot with Arch and Debian. I normally have it set so
that it defaults to booting Arch.
After an upgrade yesterday which I'm pretty sure included linux-firmware
I found that boot reversed the order and there were some other unwanted
effects too. I reinstalled grub and grub.cfg
[2013-11-06 08:56:04 +] Anthony Campbell:
After an upgrade yesterday which I'm pretty sure included linux-firmware
I found that boot reversed the order
What do you mean by pretty sure? How do you know linux-firmware is to
blame? This package only modifies files under /usr so it is unlikely
6 matches
Mail list logo
