On 2019-04-29 15:24, Ian Lepore wrote:
>
> I can't say anything at all about drm or other video driver issues, I'm
> just not knowledgeable about that stuff at all.
>
> The only thing I was getting at was that the changes I made in r346675
> might make this error stop happening:
>
>gptzfsboo
On 2019-04-29 14:58, Toomas Soome wrote:
>
> It means you have different issues - one is about gptzfsboot causing boot
> problems and apparently it got fixed when you did update the bootcode (the
> boot partition is global). But also you got bitten by DRM update, and since
> you had old BE arou
On Mon, 2019-04-29 at 14:47 -0400, Thomas Laus wrote:
> On 2019-04-29 14:27, Thomas Laus wrote:
> > It was more than a broken console. All of the other 2 computers
> > that I
> > upgraded to r346885 were essentially 'dead'. I could not even
> > remotely
> > login to them via ssh. All of them req
> On 29 Apr 2019, at 21:47, Thomas Laus wrote:
>
> On 2019-04-29 14:27, Thomas Laus wrote:
>> It was more than a broken console. All of the other 2 computers that I
>> upgraded to r346885 were essentially 'dead'. I could not even remotely
>> login to them via ssh. All of them required a hard
On 2019-04-29 14:27, Thomas Laus wrote:
> It was more than a broken console. All of the other 2 computers that I
> upgraded to r346885 were essentially 'dead'. I could not even remotely
> login to them via ssh. All of them required a hard power button reset
> to get into single user mode to let
On 2019-04-29 11:14, Ian Lepore wrote:
>
> I'm fighting my own video driver troubles (seems like a lot of that
> going around lately); on an upgrade of a machine from 11-stable to 12-
> stable I lost my console.
>
> But, a broken kernel and/or userland shouldn't affect your ability to
> use the n
On 2019-04-29 10:33, Thomas Laus wrote:
> Updating to r346885 turned out to be a disaster! There were changes to
> DRM between FreeBSD 13.0-CURRENT r346544 and r346885. The desktop that
> I use for a build machine because it is much faster than any of my other
> PC's installed kernel and world wi
On Mon, 2019-04-29 at 10:33 -0400, Thomas Laus wrote:
> > On 2019-04-28 22:27, Ian Lepore wrote:
> > >
> > > If you're using gptzfsboot, I guess you're using zfs? I just
> > > fixed a
> > > problem with probing disks for zfs volumes a few days ago
> > > (r346675).
> > > There is even some small
> On 2019-04-28 22:27, Ian Lepore wrote:
>>
>> If you're using gptzfsboot, I guess you're using zfs? I just fixed a
>> problem with probing disks for zfs volumes a few days ago (r346675).
>> There is even some small chance it fixes this problem, because one of
>> the things I noticed was that in
On 2019-04-28 22:27, Ian Lepore wrote:
>
> If you're using gptzfsboot, I guess you're using zfs? I just fixed a
> problem with probing disks for zfs volumes a few days ago (r346675).
> There is even some small chance it fixes this problem, because one of
> the things I noticed was that in one of
On Sun, 2019-04-28 at 19:29 -0400, Thomas Laus wrote:
> On 2019-04-28 08:07, Ronald Klop wrote:
> >
> > Is this the same as this?
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234
> >
>
> The messages are similar. The boot process will normally proceed on
> the
> second or third atte
On Sun, Apr 28, 2019 at 5:30 PM Thomas Laus wrote:
> On 2019-04-28 08:07, Ronald Klop wrote:
> >
> > Is this the same as this?
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234
> >
> The messages are similar. The boot process will normally proceed on the
> second or third attempt. On
On 2019-04-28 08:07, Ronald Klop wrote:
>
> Is this the same as this?
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234
>
The messages are similar. The boot process will normally proceed on the
second or third attempt. On some days, I don't see this message appear
and my laptops boot no
On Fri, 26 Apr 2019 13:31:02 +0200, Thomas Laus wrote:
List:
I have been having gptzfsboot issues with my two laptops since 12.0 was
still CURRENT. I receive 'error 1' on the first boot most days.
gptzfsboot: error 1 LBA 18446744072709551608
gptzfsboot: error 1 LBA 1
gptzfsboot: No ZFS pools
Toomas Soome [tso...@me.com] wrote:
>
> > I always update the bootcode with gpart each time when updating my system.
> >
>
> Oh right, this from gptzfsboot⦠ok, I guess I should do something
> I have been planning all along⦠Do you need some sort of quick workaround?
>
No quick workaround is
> On 26 Apr 2019, at 16:20, Thomas Laus wrote:
>
> Toomas Soome [tso...@me.com] wrote:
>>
>> The key is about LBA in first message. Make sure you have latest
>> boot code installed with gpart.
>>
> I always update the bootcode with gpart each time when updating my system.
>
Oh right, this f
Toomas Soome [tso...@me.com] wrote:
>
> The key is about LBA in first message. Make sure you have latest
> boot code installed with gpart.
>
I always update the bootcode with gpart each time when updating my system.
Tom
--
Public Keys:
PGP KeyID = 0x5F22FDC1
GnuPG KeyID = 0x620836CF
__
> On 26 Apr 2019, at 14:31, Thomas Laus wrote:
>
> List:
>
> I have been having gptzfsboot issues with my two laptops since 12.0 was
> still CURRENT. I receive 'error 1' on the first boot most days.
>
> gptzfsboot: error 1 LBA 18446744072709551608
> gptzfsboot: error 1 LBA 1
> gptzfsboot: N
List:
I have been having gptzfsboot issues with my two laptops since 12.0 was
still CURRENT. I receive 'error 1' on the first boot most days.
gptzfsboot: error 1 LBA 18446744072709551608
gptzfsboot: error 1 LBA 1
gptzfsboot: No ZFS pools located, can't boot
Most of the time the boot process is
19 matches
Mail list logo
