Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

[greg]

August 22, 2019 12:23 AM, "O. Hartmann"  wrote:

> Am Wed, 21 Aug 2019 15:58:24 -0500
> Karl Denninger  schrieb:
> 
>> I would see if you can get REFIND loaded and use that.  I have a Lenovo
>> X1 Carbon Gen 6 and that's the answer I used, as it allows multi-boot
>> (e.g. Win10 and FreeBSD) easily.
> 
> mmmhhh, Linux software to make FreeBSD boot? ;-)

rEFInd is not "Linux software", I use it to get a nice menu to choose between 
FreeBSD and Windows on my desktop. No Linux in sight. If anything, rEFInd has 
its roots in Macs :)

> This Lenovo firmware seems very reluctant or the efibootmgr doesn't operate 
> properly on
> setting variables: when trying to label the boot number (e.g. Boot000A) with 
> "-L FreeBSD", it
> is always set back to "Boot000A ATA HDD0". On other platforms, like Fujitsu 
> servers or even
> the cheap crap from ASRock a label once set is permenent until deleted.

Many laptops just ignore the boot variables outright. My X240 is the same.
I never switched to a proper efibootmgr setup on mine, I just have loader.efi 
as bootx64.efi and that's it.
 
>> If there's a way to get into the EFI shell on Lenovo's laptops from the
>> BIOS during the boot I've not found it yet.  There's supposed to be on
>> all EFI devices, but you know how "supposed to" works in many cases, right?

You can just download the EFI Shell from the internet, it's a normal .efi 
executable you can "boot". Put it as efi/boot/bootx64.efi onto a USB flash 
drive and enjoy.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

[Karl Denninger]

BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Am Wed, 21 Aug 2019 22:34:21 +0300
> Toomas Soome  schrieb:
>
> >> On 21 Aug 2019, at 22:30, O. Hartmann  wrote:
> >>
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA256
> >>
> >> Am Wed, 21 Aug 2019 22:14:46 +0300
> >> Toomas Soome mailto:tso...@me.com>> schrieb:
> >>   
> >>> If you drop into efi shell, can you start efi/boot/bootx64.efi
> manually? you should have
> >>> fs0: or like for ESP.
> >>>
> >>> rgds,
> >>> toomas  
> >>
> >> Hello,
> >>
> >> I can't even stop to gain access to the shell; there is no
> timeframe to hit any key to
> >> stop by and access the efi shell.
> >>
> >> Kind regards,
> >> oh  
>
>
> > hm? efi shell should be available from boot device menu, so you
> mean, you can not even get
> > into firmware setup?
>
> > rgds,
> > toomas
>
> Sorry,
> I confused loader prompt and EFI shell.
>
> I do not have a EFI shell on that type of laptop, not to know about
> it. I can access the
> firmware setup and already performed a reset and switched back to
> default settings. No effect.
>
> I just downloaded the newest CURRENT mem stick and extracted both
> boot1.efi and loader.efi and
> installed those into the ESP as described, setting the efibootmgr env
> accordingly. Still the
> same error.
>
> It seems that there is indeed no EFI/UEFI shell. There are Lenovo
> specific EFI boot options,
> like "diagnostics" and so on, if selected, the UEFI boots into a
> firmware embedded diagnostic
> menu. I tried several from the list given via efibootmgr show -v, but
> there is no shell from
> which I could access/boot an alternative loader.
>
> How I'm supposed to achive the access to this EFI shell? I doubt that
> on the E540 (beware of
> the E, it is not a L or T model) does have such a shell.
>
> Regards,
> oh

I would see if you can get REFIND loaded and use that.  I have a Lenovo
X1 Carbon Gen 6 and that's the answer I used, as it allows multi-boot
(e.g. Win10 and FreeBSD) easily.

I've not had trouble with 12.x on it, and I do use the
geli-encrypted-aware loader.efi.

If there's a way to get into the EFI shell on Lenovo's laptops from the
BIOS during the boot I've not found it yet.  There's supposed to be on
all EFI devices, but you know how "supposed to" works in many cases, right?

-- 
Karl Denninger
k...@denninger.net 
/The Market Ticker/
/[S/MIME encrypted email preferred]/




smime.p7s
Description: S/MIME Cryptographic Signature

HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

[O. Hartmann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I ran into serious trouble booting several boxes off UEFI. On modern hardware,
the ESP is around 200 - 300 MB in size and usually I install
/efi/freebsd/loader.efi, loader.efi taken from /boot/loader.efi. On some older
hardware, specifically on a Lenovo E540 with latest available firmware (2.28),
which uses 12-STABLE and a ZFS-only installation, there seems no working loader
anymore!
The installation of the Laptop has been performed using 12.0-PRERELEASE on an
Samsung EVO 860 500GB SSD. The ESP is 200M in size and contained
/efi/boot/BOOTx64.efi and /efi/boot/startup.nsh.

The ESP has been destroyed by accident. Now I tried to solve the problem by
installing a new ESP and the proper loader, assuming that /boot/loader.efi
(taken from a FreeBSD-13-CURRENT or from 12-STABLE of the same revision and
sompiled on the same platform (Intel Haswell) as the lost laptop's revison of
the OS is at. But I fail doing so. Somehow Lenovo's firmware is setting up a
lot of UEFI boot numbers as provided via "efibootmgr -b 000X", X some Hex
numer. -b 000A is usually denoted/labeld with "ATA HDD0".

Installing the proper boot/loader.efi loader file from 12-STABLE (r351108) and
setting the EFI variable according the following steps:

mount -t msdosfs /dev/ada0p1 /mnt (ESP is on GPT partition 1, 0p2 is zroot)
Install then loader.efi either as BOOTx64.efi or loader.efi under
/mnt/efi/boot/ or /mnt/efi/freebsd/ and then set the boot environment
accordingly via

delete 000A first:
efibootmgr -B -b 000A

create the new efi boot var:
efibootmgr -a -b 000A -c -l /mnt/efi/{freebsd|boot}/{loader.efi|BOOTx64.efi} -L
FreeBSD

The result is a non booting system, the Lenovo firmware jumps immediately into
the menu for selecting a proper boot media.

The same happens with /boot/boot1.efi installed as loader.efi or BOOTx64.efi
shown above.

In case I just brute-force flash the ESP with /boot/boot1.efifat, dd
if=boot1.efifat of=/dev/ada0p1 (ESP) (taken from the propper 12-STABLE system I
spoeke of above), then booting fails again, but this time with an error I watch
on so many boxes recently:

[...]
Ignoring Boot000a: Only one DP found
Trying ZFS pool
Setting currdev to zfs:zroot/ROOT/default:

Then the console freezes at that point and only RESET or POWER OFF is capable
of a revive.

What is wrong here? What am I missing?

Thanks in advance,

oh


- -- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXV2GbQAKCRA4N1ZZPba5
R8nBAP9GBNJGQV+Q6BD2BlMYDX1Toxu9ybQZc2uahniHNER6cAEA5TmHBDTu94eE
fX+hTk4vDUkf8ga4EsrUDZflage6LAk=
=3img
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

[O. Hartmann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Am Wed, 21 Aug 2019 22:34:21 +0300
Toomas Soome  schrieb:

> > On 21 Aug 2019, at 22:30, O. Hartmann  wrote:
> > 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> > 
> > Am Wed, 21 Aug 2019 22:14:46 +0300
> > Toomas Soome mailto:tso...@me.com>> schrieb:
> >   
> >> If you drop into efi shell, can you start efi/boot/bootx64.efi manually? 
> >> you should have
> >> fs0: or like for ESP.
> >> 
> >> rgds,
> >> toomas  
> > 
> > Hello,
> > 
> > I can't even stop to gain access to the shell; there is no timeframe to hit 
> > any key to
> > stop by and access the efi shell. 
> > 
> > Kind regards,
> > oh  
> 
> 
> hm? efi shell should be available from boot device menu, so you mean, you can 
> not even get
> into firmware setup?
> 
> rgds,
> toomas

Sorry,
I confused loader prompt and EFI shell.

I do not have a EFI shell on that type of laptop, not to know about it. I can 
access the
firmware setup and already performed a reset and switched back to default 
settings. No effect.

I just downloaded the newest CURRENT mem stick and extracted both boot1.efi and 
loader.efi and
installed those into the ESP as described, setting the efibootmgr env 
accordingly. Still the
same error.

It seems that there is indeed no EFI/UEFI shell. There are Lenovo specific EFI 
boot options,
like "diagnostics" and so on, if selected, the UEFI boots into a firmware 
embedded diagnostic
menu. I tried several from the list given via efibootmgr show -v, but there is 
no shell from
which I could access/boot an alternative loader.

How I'm supposed to achive the access to this EFI shell? I doubt that on the 
E540 (beware of
the E, it is not a L or T model) does have such a shell.

Regards,
oh 
> 
> >   
> >>   
> >>> On 21 Aug 2019, at 20:58, O. Hartmann  wrote:
> >>> 
> >>> -BEGIN PGP SIGNED MESSAGE-
> >>> Hash: SHA256
> >>> 
> >>> I ran into serious trouble booting several boxes off UEFI. On modern 
> >>> hardware,
> >>> the ESP is around 200 - 300 MB in size and usually I install
> >>> /efi/freebsd/loader.efi, loader.efi taken from /boot/loader.efi. On some 
> >>> older
> >>> hardware, specifically on a Lenovo E540 with latest available firmware 
> >>> (2.28),
> >>> which uses 12-STABLE and a ZFS-only installation, there seems no working 
> >>> loader
> >>> anymore!
> >>> The installation of the Laptop has been performed using 12.0-PRERELEASE 
> >>> on an
> >>> Samsung EVO 860 500GB SSD. The ESP is 200M in size and contained
> >>> /efi/boot/BOOTx64.efi and /efi/boot/startup.nsh.
> >>> 
> >>> The ESP has been destroyed by accident. Now I tried to solve the problem 
> >>> by
> >>> installing a new ESP and the proper loader, assuming that /boot/loader.efi
> >>> (taken from a FreeBSD-13-CURRENT or from 12-STABLE of the same revision 
> >>> and
> >>> sompiled on the same platform (Intel Haswell) as the lost laptop's 
> >>> revison of
> >>> the OS is at. But I fail doing so. Somehow Lenovo's firmware is setting 
> >>> up a
> >>> lot of UEFI boot numbers as provided via "efibootmgr -b 000X", X some Hex
> >>> numer. -b 000A is usually denoted/labeld with "ATA HDD0".
> >>> 
> >>> Installing the proper boot/loader.efi loader file from 12-STABLE 
> >>> (r351108) and
> >>> setting the EFI variable according the following steps:
> >>> 
> >>> mount -t msdosfs /dev/ada0p1 /mnt (ESP is on GPT partition 1, 0p2 is 
> >>> zroot)
> >>> Install then loader.efi either as BOOTx64.efi or loader.efi under
> >>> /mnt/efi/boot/ or /mnt/efi/freebsd/ and then set the boot environment
> >>> accordingly via
> >>> 
> >>> delete 000A first:
> >>> efibootmgr -B -b 000A
> >>> 
> >>> create the new efi boot var:
> >>> efibootmgr -a -b 000A -c -l 
> >>> /mnt/efi/{freebsd|boot}/{loader.efi|BOOTx64.efi} -L
> >>> FreeBSD
> >>> 
> >>> The result is a non booting system, the Lenovo firmware jumps immediately 
> >>> into
> >>> the menu for selecting a proper boot media.
> >>> 
> >>> The same happens with /boot/boot1.efi installed as loader.efi or 
> >>> BOOTx64.efi
> >>> shown above.
> >>> 
> >>> In case I just brute-force flash the ESP with /boot/boot1.efifat, dd
> >>> if=boot1.efifat of=/dev/ada0p1 (ESP) (taken from the propper 12-STABLE 
> >>> system I
> >>> spoeke of above), then booting fails again, but this time with an error I 
> >>> watch
> >>> on so many boxes recently:
> >>> 
> >>> [...]
> >>> Ignoring Boot000a: Only one DP found
> >>> Trying ZFS pool
> >>> Setting currdev to zfs:zroot/ROOT/default:
> >>> 
> >>> Then the console freezes at that point and only RESET or POWER OFF is 
> >>> capable
> >>> of a revive.
> >>> 
> >>> What is wrong here? What am I missing?
> >>> 
> >>> Thanks in advance,
> >>> 
> >>> oh
> >>> 
> >>> 
> >>> - -- 
> >>> O. Hartmann
> >>> 
> >>> Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
> >>> Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
> >>> -BEGIN PGP SIGNATURE-
> >>> 

Re: Working ath10k device?

[Anthony Jenkins]

On 8/2/19 6:19 PM, Steve Kargl wrote:

I have a Dell XPS 13 that reports the wifi chip is
a Qualcomm Atheros 6147.  I've found Adrain's WIP
driver, and built it.  I'm seeing the panic reported
at

https://lists.freebsd.org/pipermail/freebsd-current/2019-February/072769.html

Does anyone have a /dev/if_athp.ko and firmware?

I pushed a simple fix to my github repo - 
https://github.com/ScoobiFreeBSD/athp/pull/1


Anthony
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

[Toomas Soome]

> On 22 Aug 2019, at 00:07, Clay Daniels Jr.  wrote:
> 
> I would agree with Karl & Steffen about using rEFInd. It really gives you a
> lot more control of your computers boot. Take a look at Rod Smith's pages:
> http://www.rodsbooks.com/refind/
> 
> I use it to triple boot Windows 10, MX Linux, and FreeBSD.
> 
> Clay


rEFInd is fancy menu to start real boot loader, it really does not help if your 
boot loader is broken. In worst case, you can get fragmented memory from having 
rEFInd and native boot loader (depending on how stupid/buggy the firmware is).

rgds,
toomas

> 
> On Wed, Aug 21, 2019 at 3:59 PM Karl Denninger  wrote:
> 
>> BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA256
>>> 
>>> Am Wed, 21 Aug 2019 22:34:21 +0300
>>> Toomas Soome  schrieb:
>>> 
> On 21 Aug 2019, at 22:30, O. Hartmann  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Am Wed, 21 Aug 2019 22:14:46 +0300
> Toomas Soome mailto:tso...@me.com>> schrieb:
> 
>> If you drop into efi shell, can you start efi/boot/bootx64.efi
>>> manually? you should have
>> fs0: or like for ESP.
>> 
>> rgds,
>> toomas
> 
> Hello,
> 
> I can't even stop to gain access to the shell; there is no
>>> timeframe to hit any key to
> stop by and access the efi shell.
> 
> Kind regards,
> oh
>>> 
>>> 
 hm? efi shell should be available from boot device menu, so you
>>> mean, you can not even get
 into firmware setup?
>>> 
 rgds,
 toomas
>>> 
>>> Sorry,
>>> I confused loader prompt and EFI shell.
>>> 
>>> I do not have a EFI shell on that type of laptop, not to know about
>>> it. I can access the
>>> firmware setup and already performed a reset and switched back to
>>> default settings. No effect.
>>> 
>>> I just downloaded the newest CURRENT mem stick and extracted both
>>> boot1.efi and loader.efi and
>>> installed those into the ESP as described, setting the efibootmgr env
>>> accordingly. Still the
>>> same error.
>>> 
>>> It seems that there is indeed no EFI/UEFI shell. There are Lenovo
>>> specific EFI boot options,
>>> like "diagnostics" and so on, if selected, the UEFI boots into a
>>> firmware embedded diagnostic
>>> menu. I tried several from the list given via efibootmgr show -v, but
>>> there is no shell from
>>> which I could access/boot an alternative loader.
>>> 
>>> How I'm supposed to achive the access to this EFI shell? I doubt that
>>> on the E540 (beware of
>>> the E, it is not a L or T model) does have such a shell.
>>> 
>>> Regards,
>>> oh
>> 
>> I would see if you can get REFIND loaded and use that.  I have a Lenovo
>> X1 Carbon Gen 6 and that's the answer I used, as it allows multi-boot
>> (e.g. Win10 and FreeBSD) easily.
>> 
>> I've not had trouble with 12.x on it, and I do use the
>> geli-encrypted-aware loader.efi.
>> 
>> If there's a way to get into the EFI shell on Lenovo's laptops from the
>> BIOS during the boot I've not found it yet.  There's supposed to be on
>> all EFI devices, but you know how "supposed to" works in many cases, right?
>> 
>> --
>> Karl Denninger
>> k...@denninger.net 
>> /The Market Ticker/
>> /[S/MIME encrypted email preferred]/
>> 
>> 
>> 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

[O. Hartmann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Am Wed, 21 Aug 2019 15:58:24 -0500
Karl Denninger  schrieb:

> BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Am Wed, 21 Aug 2019 22:34:21 +0300
> > Toomas Soome  schrieb:
> >  
> > >> On 21 Aug 2019, at 22:30, O. Hartmann  wrote:
> > >>
> > >> -BEGIN PGP SIGNED MESSAGE-
> > >> Hash: SHA256
> > >>
> > >> Am Wed, 21 Aug 2019 22:14:46 +0300
> > >> Toomas Soome mailto:tso...@me.com>> schrieb:
> > >>     
> > >>> If you drop into efi shell, can you start efi/boot/bootx64.efi  
> > manually? you should have  
> > >>> fs0: or like for ESP.
> > >>>
> > >>> rgds,
> > >>> toomas    
> > >>
> > >> Hello,
> > >>
> > >> I can't even stop to gain access to the shell; there is no  
> > timeframe to hit any key to  
> > >> stop by and access the efi shell.
> > >>
> > >> Kind regards,
> > >> oh    
> >
> >  
> > > hm? efi shell should be available from boot device menu, so you  
> > mean, you can not even get  
> > > into firmware setup?  
> >  
> > > rgds,
> > > toomas  
> >
> > Sorry,
> > I confused loader prompt and EFI shell.
> >
> > I do not have a EFI shell on that type of laptop, not to know about
> > it. I can access the
> > firmware setup and already performed a reset and switched back to
> > default settings. No effect.
> >
> > I just downloaded the newest CURRENT mem stick and extracted both
> > boot1.efi and loader.efi and
> > installed those into the ESP as described, setting the efibootmgr env
> > accordingly. Still the
> > same error.
> >
> > It seems that there is indeed no EFI/UEFI shell. There are Lenovo
> > specific EFI boot options,
> > like "diagnostics" and so on, if selected, the UEFI boots into a
> > firmware embedded diagnostic
> > menu. I tried several from the list given via efibootmgr show -v, but
> > there is no shell from
> > which I could access/boot an alternative loader.
> >
> > How I'm supposed to achive the access to this EFI shell? I doubt that
> > on the E540 (beware of
> > the E, it is not a L or T model) does have such a shell.
> >
> > Regards,
> > oh  
> 
> I would see if you can get REFIND loaded and use that.  I have a Lenovo
> X1 Carbon Gen 6 and that's the answer I used, as it allows multi-boot
> (e.g. Win10 and FreeBSD) easily.

mmmhhh, Linux software to make FreeBSD boot? ;-)

> 
> I've not had trouble with 12.x on it, and I do use the
> geli-encrypted-aware loader.efi.

Until today I also did not have any trouble. In Novmeber 2018 I installed 
12-CURRENT (or
12-RC) with a ZFS filesystem on a new SSD and everything worked fine - until 
today, when I was
so insane to copy the most recent 12-STABLE loader.efi into the ESP and 
adjusted the efiboot
vartiable accordingly.  

This Lenovo firmware seems very reluctant or the efibootmgr doesn't operate 
properly on
setting variables: when trying to label the boot number (e.g. Boot000A) with 
"-L FreeBSD", it
is always set back to "Boot000A ATA HDD0". On other platforms, like Fujitsu 
servers or even
the cheap crap from ASRock a label once set is permenent until deleted.

> 
> If there's a way to get into the EFI shell on Lenovo's laptops from the
> BIOS during the boot I've not found it yet.  There's supposed to be on
> all EFI devices, but you know how "supposed to" works in many cases, right?
> 


I havn't tested all options available by setting the current boot number to 
those entries
predefined by Lenovo, but setting Boot0003 (I recall ...) gives a really funny 
diagnostics
menu with lots of options. Maybe there is more to discover ...

Thanks anyway, but I have to postpone the efforts until tomorrow evening ...
Regards
oh


- -- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXV22VgAKCRA4N1ZZPba5
R2C/AP0WR1oKX/EpeRzDovQoeEbaSyVwg8PhTIaEciMwzEnLvwD9HJ83Czygd9Rd
kGM/24FRcYKDdJMD9ec46PQE38/UMgg=
=93bM
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

[Clay Daniels Jr.]

I would agree with Karl & Steffen about using rEFInd. It really gives you a
lot more control of your computers boot. Take a look at Rod Smith's pages:
http://www.rodsbooks.com/refind/

I use it to triple boot Windows 10, MX Linux, and FreeBSD.

Clay

On Wed, Aug 21, 2019 at 3:59 PM Karl Denninger  wrote:

> BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Am Wed, 21 Aug 2019 22:34:21 +0300
> > Toomas Soome  schrieb:
> >
> > >> On 21 Aug 2019, at 22:30, O. Hartmann  wrote:
> > >>
> > >> -BEGIN PGP SIGNED MESSAGE-
> > >> Hash: SHA256
> > >>
> > >> Am Wed, 21 Aug 2019 22:14:46 +0300
> > >> Toomas Soome mailto:tso...@me.com>> schrieb:
> > >>
> > >>> If you drop into efi shell, can you start efi/boot/bootx64.efi
> > manually? you should have
> > >>> fs0: or like for ESP.
> > >>>
> > >>> rgds,
> > >>> toomas
> > >>
> > >> Hello,
> > >>
> > >> I can't even stop to gain access to the shell; there is no
> > timeframe to hit any key to
> > >> stop by and access the efi shell.
> > >>
> > >> Kind regards,
> > >> oh
> >
> >
> > > hm? efi shell should be available from boot device menu, so you
> > mean, you can not even get
> > > into firmware setup?
> >
> > > rgds,
> > > toomas
> >
> > Sorry,
> > I confused loader prompt and EFI shell.
> >
> > I do not have a EFI shell on that type of laptop, not to know about
> > it. I can access the
> > firmware setup and already performed a reset and switched back to
> > default settings. No effect.
> >
> > I just downloaded the newest CURRENT mem stick and extracted both
> > boot1.efi and loader.efi and
> > installed those into the ESP as described, setting the efibootmgr env
> > accordingly. Still the
> > same error.
> >
> > It seems that there is indeed no EFI/UEFI shell. There are Lenovo
> > specific EFI boot options,
> > like "diagnostics" and so on, if selected, the UEFI boots into a
> > firmware embedded diagnostic
> > menu. I tried several from the list given via efibootmgr show -v, but
> > there is no shell from
> > which I could access/boot an alternative loader.
> >
> > How I'm supposed to achive the access to this EFI shell? I doubt that
> > on the E540 (beware of
> > the E, it is not a L or T model) does have such a shell.
> >
> > Regards,
> > oh
>
> I would see if you can get REFIND loaded and use that.  I have a Lenovo
> X1 Carbon Gen 6 and that's the answer I used, as it allows multi-boot
> (e.g. Win10 and FreeBSD) easily.
>
> I've not had trouble with 12.x on it, and I do use the
> geli-encrypted-aware loader.efi.
>
> If there's a way to get into the EFI shell on Lenovo's laptops from the
> BIOS during the boot I've not found it yet.  There's supposed to be on
> all EFI devices, but you know how "supposed to" works in many cases, right?
>
> --
> Karl Denninger
> k...@denninger.net 
> /The Market Ticker/
> /[S/MIME encrypted email preferred]/
>
>
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

[Toomas Soome]

If you drop into efi shell, can you start efi/boot/bootx64.efi manually? you 
should have fs0: or like for ESP.

rgds,
toomas

> On 21 Aug 2019, at 20:58, O. Hartmann  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> I ran into serious trouble booting several boxes off UEFI. On modern hardware,
> the ESP is around 200 - 300 MB in size and usually I install
> /efi/freebsd/loader.efi, loader.efi taken from /boot/loader.efi. On some older
> hardware, specifically on a Lenovo E540 with latest available firmware (2.28),
> which uses 12-STABLE and a ZFS-only installation, there seems no working 
> loader
> anymore!
> The installation of the Laptop has been performed using 12.0-PRERELEASE on an
> Samsung EVO 860 500GB SSD. The ESP is 200M in size and contained
> /efi/boot/BOOTx64.efi and /efi/boot/startup.nsh.
> 
> The ESP has been destroyed by accident. Now I tried to solve the problem by
> installing a new ESP and the proper loader, assuming that /boot/loader.efi
> (taken from a FreeBSD-13-CURRENT or from 12-STABLE of the same revision and
> sompiled on the same platform (Intel Haswell) as the lost laptop's revison of
> the OS is at. But I fail doing so. Somehow Lenovo's firmware is setting up a
> lot of UEFI boot numbers as provided via "efibootmgr -b 000X", X some Hex
> numer. -b 000A is usually denoted/labeld with "ATA HDD0".
> 
> Installing the proper boot/loader.efi loader file from 12-STABLE (r351108) and
> setting the EFI variable according the following steps:
> 
> mount -t msdosfs /dev/ada0p1 /mnt (ESP is on GPT partition 1, 0p2 is zroot)
> Install then loader.efi either as BOOTx64.efi or loader.efi under
> /mnt/efi/boot/ or /mnt/efi/freebsd/ and then set the boot environment
> accordingly via
> 
> delete 000A first:
> efibootmgr -B -b 000A
> 
> create the new efi boot var:
> efibootmgr -a -b 000A -c -l /mnt/efi/{freebsd|boot}/{loader.efi|BOOTx64.efi} 
> -L
> FreeBSD
> 
> The result is a non booting system, the Lenovo firmware jumps immediately into
> the menu for selecting a proper boot media.
> 
> The same happens with /boot/boot1.efi installed as loader.efi or BOOTx64.efi
> shown above.
> 
> In case I just brute-force flash the ESP with /boot/boot1.efifat, dd
> if=boot1.efifat of=/dev/ada0p1 (ESP) (taken from the propper 12-STABLE system 
> I
> spoeke of above), then booting fails again, but this time with an error I 
> watch
> on so many boxes recently:
> 
> [...]
> Ignoring Boot000a: Only one DP found
> Trying ZFS pool
> Setting currdev to zfs:zroot/ROOT/default:
> 
> Then the console freezes at that point and only RESET or POWER OFF is capable
> of a revive.
> 
> What is wrong here? What am I missing?
> 
> Thanks in advance,
> 
> oh
> 
> 
> - -- 
> O. Hartmann
> 
> Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
> Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
> -BEGIN PGP SIGNATURE-
> 
> iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXV2GbQAKCRA4N1ZZPba5
> R8nBAP9GBNJGQV+Q6BD2BlMYDX1Toxu9ybQZc2uahniHNER6cAEA5TmHBDTu94eE
> fX+hTk4vDUkf8ga4EsrUDZflage6LAk=
> =3img
> -END PGP SIGNATURE-
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

[O. Hartmann]

I ran into serious trouble booting several boxes off UEFI. On modern hardware,
the ESP is around 200 - 300 MB in size and usually I install
/efi/freebsd/loader.efi, loader.efi taken from /boot/loader.efi. On some older
hardware, specifically on a Lenovo E540 with latest available firmware (2.28),
which uses 12-STABLE and a ZFS-only installation, there seems no working loader
anymore!
The installation of the Laptop has been performed using 12.0-PRERELEASE on an
Samsung EVO 860 500GB SSD. The ESP is 200M in size and contained
/efi/boot/BOOTx64.efi and /efi/boot/startup.nsh.

The ESP has been destroyed by accident. Now I tried to solve the problem by
installing a new ESP and the proper loader, assuming that /boot/loader.efi
(taken from a FreeBSD-13-CURRENT or from 12-STABLE of the same revision and
sompiled on the same platform (Intel Haswell) as the lost laptop's revison of
the OS is at. But I fail doing so. Somehow Lenovo's firmware is setting up a
lot of UEFI boot numbers as provided via "efibootmgr -b 000X", X some Hex
numer. -b 000A is usually denoted/labeld with "ATA HDD0".

Installing the proper boot/loader.efi loader file from 12-STABLE (r351108) and
setting the EFI variable according the following steps:

mount -t msdosfs /dev/ada0p1 /mnt (ESP is on GPT partition 1, 0p2 is zroot)
Install then loader.efi either as BOOTx64.efi or loader.efi under
/mnt/efi/boot/ or /mnt/efi/freebsd/ and then set the boot environment
accordingly via

delete 000A first:
efibootmgr -B -b 000A

create the new efi boot var:
efibootmgr -a -b 000A -c -l /mnt/efi/{freebsd|boot}/{loader.efi|BOOTx64.efi} -L
FreeBSD

The result is a non booting system, the Lenovo firmware jumps immediately into
the menu for selecting a proper boot media.

The same happens with /boot/boot1.efi installed as loader.efi or BOOTx64.efi
shown above.

In case I just brute-force flash the ESP with /boot/boot1.efifat, dd
if=boot1.efifat of=/dev/ada0p1 (ESP) (taken from the propper 12-STABLE system I
spoeke of above), then booting fails again, but this time with an error I watch
on so many boxes recently:

[...]
Ignoring Boot000a: Only one DP found
Trying ZFS pool
Setting currdev to zfs:zroot/ROOT/default:

Then the console freezes at that point and only RESET or POWER OFF is capable
of a revive.

What is wrong here? What am I missing?

Thanks in advance,

oh
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

[O. Hartmann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Am Wed, 21 Aug 2019 22:14:46 +0300
Toomas Soome  schrieb:

> If you drop into efi shell, can you start efi/boot/bootx64.efi manually? you 
> should have
> fs0: or like for ESP.
> 
> rgds,
> toomas

Hello,

I can't even stop to gain access to the shell; there is no timeframe to hit any 
key to stop by
and access the efi shell. 

Kind regards,
oh

> 
> > On 21 Aug 2019, at 20:58, O. Hartmann  wrote:
> > 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> > 
> > I ran into serious trouble booting several boxes off UEFI. On modern 
> > hardware,
> > the ESP is around 200 - 300 MB in size and usually I install
> > /efi/freebsd/loader.efi, loader.efi taken from /boot/loader.efi. On some 
> > older
> > hardware, specifically on a Lenovo E540 with latest available firmware 
> > (2.28),
> > which uses 12-STABLE and a ZFS-only installation, there seems no working 
> > loader
> > anymore!
> > The installation of the Laptop has been performed using 12.0-PRERELEASE on 
> > an
> > Samsung EVO 860 500GB SSD. The ESP is 200M in size and contained
> > /efi/boot/BOOTx64.efi and /efi/boot/startup.nsh.
> > 
> > The ESP has been destroyed by accident. Now I tried to solve the problem by
> > installing a new ESP and the proper loader, assuming that /boot/loader.efi
> > (taken from a FreeBSD-13-CURRENT or from 12-STABLE of the same revision and
> > sompiled on the same platform (Intel Haswell) as the lost laptop's revison 
> > of
> > the OS is at. But I fail doing so. Somehow Lenovo's firmware is setting up a
> > lot of UEFI boot numbers as provided via "efibootmgr -b 000X", X some Hex
> > numer. -b 000A is usually denoted/labeld with "ATA HDD0".
> > 
> > Installing the proper boot/loader.efi loader file from 12-STABLE (r351108) 
> > and
> > setting the EFI variable according the following steps:
> > 
> > mount -t msdosfs /dev/ada0p1 /mnt (ESP is on GPT partition 1, 0p2 is zroot)
> > Install then loader.efi either as BOOTx64.efi or loader.efi under
> > /mnt/efi/boot/ or /mnt/efi/freebsd/ and then set the boot environment
> > accordingly via
> > 
> > delete 000A first:
> > efibootmgr -B -b 000A
> > 
> > create the new efi boot var:
> > efibootmgr -a -b 000A -c -l 
> > /mnt/efi/{freebsd|boot}/{loader.efi|BOOTx64.efi} -L
> > FreeBSD
> > 
> > The result is a non booting system, the Lenovo firmware jumps immediately 
> > into
> > the menu for selecting a proper boot media.
> > 
> > The same happens with /boot/boot1.efi installed as loader.efi or BOOTx64.efi
> > shown above.
> > 
> > In case I just brute-force flash the ESP with /boot/boot1.efifat, dd
> > if=boot1.efifat of=/dev/ada0p1 (ESP) (taken from the propper 12-STABLE 
> > system I
> > spoeke of above), then booting fails again, but this time with an error I 
> > watch
> > on so many boxes recently:
> > 
> > [...]
> > Ignoring Boot000a: Only one DP found
> > Trying ZFS pool
> > Setting currdev to zfs:zroot/ROOT/default:
> > 
> > Then the console freezes at that point and only RESET or POWER OFF is 
> > capable
> > of a revive.
> > 
> > What is wrong here? What am I missing?
> > 
> > Thanks in advance,
> > 
> > oh
> > 
> > 
> > - -- 
> > O. Hartmann
> > 
> > Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
> > Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
> > -BEGIN PGP SIGNATURE-
> > 
> > iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXV2GbQAKCRA4N1ZZPba5
> > R8nBAP9GBNJGQV+Q6BD2BlMYDX1Toxu9ybQZc2uahniHNER6cAEA5TmHBDTu94eE
> > fX+hTk4vDUkf8ga4EsrUDZflage6LAk=
> > =3img
> > -END PGP SIGNATURE-
> > ___
> > freebsd-current@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"  
> 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"



- -- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
-BEGIN PGP SIGNATURE-

iHQEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXV2b/AAKCRA4N1ZZPba5
R+DDAP9LN8SDMDm/0ybGw+TBqczvS+m51n0DMYEqMZxTsikIFgD46rrBkm4zpKH5
BDk3pkVT+h7MH8ghESa7XfhFGg3pCg==
=/Hm2
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

[O. Hartmann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Am Wed, 21 Aug 2019 22:34:21 +0300
Toomas Soome  schrieb:

> > On 21 Aug 2019, at 22:30, O. Hartmann  wrote:
> > 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> > 
> > Am Wed, 21 Aug 2019 22:14:46 +0300
> > Toomas Soome mailto:tso...@me.com>> schrieb:
> >   
> >> If you drop into efi shell, can you start efi/boot/bootx64.efi manually? 
> >> you should have
> >> fs0: or like for ESP.
> >> 
> >> rgds,
> >> toomas  
> > 
> > Hello,
> > 
> > I can't even stop to gain access to the shell; there is no timeframe to hit 
> > any key to
> > stop by and access the efi shell. 
> > 
> > Kind regards,
> > oh  
> 
> 
> hm? efi shell should be available from boot device menu, so you mean, you can 
> not even get
> into firmware setup?
> 
> rgds,
> toomas
> 
> >   
> >>   
> >>> On 21 Aug 2019, at 20:58, O. Hartmann  wrote:
> >>> 
> >>> -BEGIN PGP SIGNED MESSAGE-
> >>> Hash: SHA256
> >>> 
> >>> I ran into serious trouble booting several boxes off UEFI. On modern 
> >>> hardware,
> >>> the ESP is around 200 - 300 MB in size and usually I install
> >>> /efi/freebsd/loader.efi, loader.efi taken from /boot/loader.efi. On some 
> >>> older
> >>> hardware, specifically on a Lenovo E540 with latest available firmware 
> >>> (2.28),
> >>> which uses 12-STABLE and a ZFS-only installation, there seems no working 
> >>> loader
> >>> anymore!
> >>> The installation of the Laptop has been performed using 12.0-PRERELEASE 
> >>> on an
> >>> Samsung EVO 860 500GB SSD. The ESP is 200M in size and contained
> >>> /efi/boot/BOOTx64.efi and /efi/boot/startup.nsh.
> >>> 
> >>> The ESP has been destroyed by accident. Now I tried to solve the problem 
> >>> by
> >>> installing a new ESP and the proper loader, assuming that /boot/loader.efi
> >>> (taken from a FreeBSD-13-CURRENT or from 12-STABLE of the same revision 
> >>> and
> >>> sompiled on the same platform (Intel Haswell) as the lost laptop's 
> >>> revison of
> >>> the OS is at. But I fail doing so. Somehow Lenovo's firmware is setting 
> >>> up a
> >>> lot of UEFI boot numbers as provided via "efibootmgr -b 000X", X some Hex
> >>> numer. -b 000A is usually denoted/labeld with "ATA HDD0".
> >>> 
> >>> Installing the proper boot/loader.efi loader file from 12-STABLE 
> >>> (r351108) and
> >>> setting the EFI variable according the following steps:
> >>> 
> >>> mount -t msdosfs /dev/ada0p1 /mnt (ESP is on GPT partition 1, 0p2 is 
> >>> zroot)
> >>> Install then loader.efi either as BOOTx64.efi or loader.efi under
> >>> /mnt/efi/boot/ or /mnt/efi/freebsd/ and then set the boot environment
> >>> accordingly via
> >>> 
> >>> delete 000A first:
> >>> efibootmgr -B -b 000A
> >>> 
> >>> create the new efi boot var:
> >>> efibootmgr -a -b 000A -c -l 
> >>> /mnt/efi/{freebsd|boot}/{loader.efi|BOOTx64.efi} -L
> >>> FreeBSD
> >>> 
> >>> The result is a non booting system, the Lenovo firmware jumps immediately 
> >>> into
> >>> the menu for selecting a proper boot media.
> >>> 
> >>> The same happens with /boot/boot1.efi installed as loader.efi or 
> >>> BOOTx64.efi
> >>> shown above.
> >>> 
> >>> In case I just brute-force flash the ESP with /boot/boot1.efifat, dd
> >>> if=boot1.efifat of=/dev/ada0p1 (ESP) (taken from the propper 12-STABLE 
> >>> system I
> >>> spoeke of above), then booting fails again, but this time with an error I 
> >>> watch
> >>> on so many boxes recently:
> >>> 
> >>> [...]
> >>> Ignoring Boot000a: Only one DP found
> >>> Trying ZFS pool
> >>> Setting currdev to zfs:zroot/ROOT/default:
> >>> 
> >>> Then the console freezes at that point and only RESET or POWER OFF is 
> >>> capable
> >>> of a revive.
> >>> 
> >>> What is wrong here? What am I missing?
> >>> 
> >>> Thanks in advance,
> >>> 
[...]

What does the message:

Only one DP found

mean? Obviously, "Trying ZFS pool - Setting currdev to zfs"zroot/ROOT/default:" 
indicates that
the loader has already found its partition to bbot from, but why is it 
freezing/crashing then?
No Ctrl-Alt-Del helps, only hard reset or power cycle brings the box back.

oh
- -- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXV2tQgAKCRA4N1ZZPba5
R8PmAQCysRllIHaShJZOAQHy6YY2THQwRruzziJUY+zer/i/7QEAi/C68BgEJtuW
mD2oPCsXJR8AO10XFDvO+uI8ugCV/wE=
=ILkO
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

[Warner Losh]

On Wed, Aug 21, 2019 at 2:50 PM O. Hartmann  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Am Wed, 21 Aug 2019 22:34:21 +0300
> Toomas Soome  schrieb:
>
> > > On 21 Aug 2019, at 22:30, O. Hartmann  wrote:
> > >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA256
> > >
> > > Am Wed, 21 Aug 2019 22:14:46 +0300
> > > Toomas Soome mailto:tso...@me.com>> schrieb:
> > >
> > >> If you drop into efi shell, can you start efi/boot/bootx64.efi
> manually? you should have
> > >> fs0: or like for ESP.
> > >>
> > >> rgds,
> > >> toomas
> > >
> > > Hello,
> > >
> > > I can't even stop to gain access to the shell; there is no timeframe
> to hit any key to
> > > stop by and access the efi shell.
> > >
> > > Kind regards,
> > > oh
> >
> >
> > hm? efi shell should be available from boot device menu, so you mean,
> you can not even get
> > into firmware setup?
> >
> > rgds,
> > toomas
> >
> > >
> > >>
> > >>> On 21 Aug 2019, at 20:58, O. Hartmann 
> wrote:
> > >>>
> > >>> -BEGIN PGP SIGNED MESSAGE-
> > >>> Hash: SHA256
> > >>>
> > >>> I ran into serious trouble booting several boxes off UEFI. On modern
> hardware,
> > >>> the ESP is around 200 - 300 MB in size and usually I install
> > >>> /efi/freebsd/loader.efi, loader.efi taken from /boot/loader.efi. On
> some older
> > >>> hardware, specifically on a Lenovo E540 with latest available
> firmware (2.28),
> > >>> which uses 12-STABLE and a ZFS-only installation, there seems no
> working loader
> > >>> anymore!
> > >>> The installation of the Laptop has been performed using
> 12.0-PRERELEASE on an
> > >>> Samsung EVO 860 500GB SSD. The ESP is 200M in size and contained
> > >>> /efi/boot/BOOTx64.efi and /efi/boot/startup.nsh.
> > >>>
> > >>> The ESP has been destroyed by accident. Now I tried to solve the
> problem by
> > >>> installing a new ESP and the proper loader, assuming that
> /boot/loader.efi
> > >>> (taken from a FreeBSD-13-CURRENT or from 12-STABLE of the same
> revision and
> > >>> sompiled on the same platform (Intel Haswell) as the lost laptop's
> revison of
> > >>> the OS is at. But I fail doing so. Somehow Lenovo's firmware is
> setting up a
> > >>> lot of UEFI boot numbers as provided via "efibootmgr -b 000X", X
> some Hex
> > >>> numer. -b 000A is usually denoted/labeld with "ATA HDD0".
> > >>>
> > >>> Installing the proper boot/loader.efi loader file from 12-STABLE
> (r351108) and
> > >>> setting the EFI variable according the following steps:
> > >>>
> > >>> mount -t msdosfs /dev/ada0p1 /mnt (ESP is on GPT partition 1, 0p2 is
> zroot)
> > >>> Install then loader.efi either as BOOTx64.efi or loader.efi under
> > >>> /mnt/efi/boot/ or /mnt/efi/freebsd/ and then set the boot environment
> > >>> accordingly via
> > >>>
> > >>> delete 000A first:
> > >>> efibootmgr -B -b 000A
> > >>>
> > >>> create the new efi boot var:
> > >>> efibootmgr -a -b 000A -c -l
> /mnt/efi/{freebsd|boot}/{loader.efi|BOOTx64.efi} -L
> > >>> FreeBSD
> > >>>
> > >>> The result is a non booting system, the Lenovo firmware jumps
> immediately into
> > >>> the menu for selecting a proper boot media.
> > >>>
> > >>> The same happens with /boot/boot1.efi installed as loader.efi or
> BOOTx64.efi
> > >>> shown above.
> > >>>
> > >>> In case I just brute-force flash the ESP with /boot/boot1.efifat, dd
> > >>> if=boot1.efifat of=/dev/ada0p1 (ESP) (taken from the propper
> 12-STABLE system I
> > >>> spoeke of above), then booting fails again, but this time with an
> error I watch
> > >>> on so many boxes recently:
> > >>>
> > >>> [...]
> > >>> Ignoring Boot000a: Only one DP found
> > >>> Trying ZFS pool
> > >>> Setting currdev to zfs:zroot/ROOT/default:
> > >>>
> > >>> Then the console freezes at that point and only RESET or POWER OFF
> is capable
> > >>> of a revive.
> > >>>
> > >>> What is wrong here? What am I missing?
> > >>>
> > >>> Thanks in advance,
> > >>>
> [...]
>
> What does the message:
>
> Only one DP found
>
> mean? Obviously, "Trying ZFS pool - Setting currdev to
> zfs"zroot/ROOT/default:" indicates that
> the loader has already found its partition to bbot from, but why is it
> freezing/crashing then?
> No Ctrl-Alt-Del helps, only hard reset or power cycle brings the box back.
>

It means there was no explicit kernel specified and so the system is going
to guess which kernel (and which root) to use. The fact that you don't see
a kernel booting suggests it's unable to do so properly.

Warner


> oh
> - --
> O. Hartmann
>
> Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
> Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
> -BEGIN PGP SIGNATURE-
>
> iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXV2tQgAKCRA4N1ZZPba5
> R8PmAQCysRllIHaShJZOAQHy6YY2THQwRruzziJUY+zer/i/7QEAi/C68BgEJtuW
> mD2oPCsXJR8AO10XFDvO+uI8ugCV/wE=
> =ILkO
> -END PGP SIGNATURE-
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> 

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

[Toomas Soome]

> On 21 Aug 2019, at 22:30, O. Hartmann  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Am Wed, 21 Aug 2019 22:14:46 +0300
> Toomas Soome mailto:tso...@me.com>> schrieb:
> 
>> If you drop into efi shell, can you start efi/boot/bootx64.efi manually? you 
>> should have
>> fs0: or like for ESP.
>> 
>> rgds,
>> toomas
> 
> Hello,
> 
> I can't even stop to gain access to the shell; there is no timeframe to hit 
> any key to stop by
> and access the efi shell. 
> 
> Kind regards,
> oh


hm? efi shell should be available from boot device menu, so you mean, you can 
not even get into firmware setup?

rgds,
toomas

> 
>> 
>>> On 21 Aug 2019, at 20:58, O. Hartmann  wrote:
>>> 
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA256
>>> 
>>> I ran into serious trouble booting several boxes off UEFI. On modern 
>>> hardware,
>>> the ESP is around 200 - 300 MB in size and usually I install
>>> /efi/freebsd/loader.efi, loader.efi taken from /boot/loader.efi. On some 
>>> older
>>> hardware, specifically on a Lenovo E540 with latest available firmware 
>>> (2.28),
>>> which uses 12-STABLE and a ZFS-only installation, there seems no working 
>>> loader
>>> anymore!
>>> The installation of the Laptop has been performed using 12.0-PRERELEASE on 
>>> an
>>> Samsung EVO 860 500GB SSD. The ESP is 200M in size and contained
>>> /efi/boot/BOOTx64.efi and /efi/boot/startup.nsh.
>>> 
>>> The ESP has been destroyed by accident. Now I tried to solve the problem by
>>> installing a new ESP and the proper loader, assuming that /boot/loader.efi
>>> (taken from a FreeBSD-13-CURRENT or from 12-STABLE of the same revision and
>>> sompiled on the same platform (Intel Haswell) as the lost laptop's revison 
>>> of
>>> the OS is at. But I fail doing so. Somehow Lenovo's firmware is setting up a
>>> lot of UEFI boot numbers as provided via "efibootmgr -b 000X", X some Hex
>>> numer. -b 000A is usually denoted/labeld with "ATA HDD0".
>>> 
>>> Installing the proper boot/loader.efi loader file from 12-STABLE (r351108) 
>>> and
>>> setting the EFI variable according the following steps:
>>> 
>>> mount -t msdosfs /dev/ada0p1 /mnt (ESP is on GPT partition 1, 0p2 is zroot)
>>> Install then loader.efi either as BOOTx64.efi or loader.efi under
>>> /mnt/efi/boot/ or /mnt/efi/freebsd/ and then set the boot environment
>>> accordingly via
>>> 
>>> delete 000A first:
>>> efibootmgr -B -b 000A
>>> 
>>> create the new efi boot var:
>>> efibootmgr -a -b 000A -c -l 
>>> /mnt/efi/{freebsd|boot}/{loader.efi|BOOTx64.efi} -L
>>> FreeBSD
>>> 
>>> The result is a non booting system, the Lenovo firmware jumps immediately 
>>> into
>>> the menu for selecting a proper boot media.
>>> 
>>> The same happens with /boot/boot1.efi installed as loader.efi or BOOTx64.efi
>>> shown above.
>>> 
>>> In case I just brute-force flash the ESP with /boot/boot1.efifat, dd
>>> if=boot1.efifat of=/dev/ada0p1 (ESP) (taken from the propper 12-STABLE 
>>> system I
>>> spoeke of above), then booting fails again, but this time with an error I 
>>> watch
>>> on so many boxes recently:
>>> 
>>> [...]
>>> Ignoring Boot000a: Only one DP found
>>> Trying ZFS pool
>>> Setting currdev to zfs:zroot/ROOT/default:
>>> 
>>> Then the console freezes at that point and only RESET or POWER OFF is 
>>> capable
>>> of a revive.
>>> 
>>> What is wrong here? What am I missing?
>>> 
>>> Thanks in advance,
>>> 
>>> oh
>>> 
>>> 
>>> - -- 
>>> O. Hartmann
>>> 
>>> Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
>>> Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
>>> -BEGIN PGP SIGNATURE-
>>> 
>>> iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXV2GbQAKCRA4N1ZZPba5
>>> R8nBAP9GBNJGQV+Q6BD2BlMYDX1Toxu9ybQZc2uahniHNER6cAEA5TmHBDTu94eE
>>> fX+hTk4vDUkf8ga4EsrUDZflage6LAk=
>>> =3img
>>> -END PGP SIGNATURE-
>>> ___
>>> freebsd-current@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"  
>> 
>> ___
>> freebsd-current@freebsd.org  mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current 
>> 
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org 
>> "
> 
> 
> 
> - -- 
> O. Hartmann
> 
> Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
> Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
> -BEGIN PGP SIGNATURE-
> 
> iHQEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXV2b/AAKCRA4N1ZZPba5
> R+DDAP9LN8SDMDm/0ybGw+TBqczvS+m51n0DMYEqMZxTsikIFgD46rrBkm4zpKH5
> BDk3pkVT+h7MH8ghESa7XfhFGg3pCg==
> =/Hm2
> -END PGP SIGNATURE-

___
freebsd-current@freebsd.org mailing list

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

[Steffen Nurpmeso]

O. Hartmann wrote in <20190821145234.6fe455b4@freyja>:
 |I ran into serious trouble booting several boxes off UEFI. On modern \
 |hardware,
 |the ESP is around 200 - 300 MB in size and usually I install
 |/efi/freebsd/loader.efi, loader.efi taken from /boot/loader.efi. On \
 |some older
 |hardware, specifically on a Lenovo E540 with latest available firmware \
 |(2.28),
 |which uses 12-STABLE and a ZFS-only installation, there seems no working \
 |loader
 |anymore!
 |The installation of the Laptop has been performed using 12.0-PRERELEASE \
 |on an
 |Samsung EVO 860 500GB SSD. The ESP is 200M in size and contained
 |/efi/boot/BOOTx64.efi and /efi/boot/startup.nsh.

It may be that the Lenovo BIOS/firmware searches for that specific
Microsoft location

  EFI/Microsoft/Boot/bootmgfw.efi

Onto which i radically (according to docu) moved refind_x64.efi:

  #?0|kent:~# ll /mnt/EFI/Microsoft/Boot/bootmg*
  -rwxr-xr-x 1 root root 1453056 Sep 14  2018 
/mnt/EFI/Microsoft/Boot/bootmgr.efi
  -rwxr-xr-x 1 root root 1469752 Mar 21 17:43 
/mnt/EFI/Microsoft/Boot/bootmgfw.efi.safe
  -rwxr-xr-x 1 root root  208776 Mar 21 17:43 
/mnt/EFI/Microsoft/Boot/bootmgfw.efi

and that now finds its normal installation (etc.), simply copied
via cp(1):

  #?0|kent:~# ll /mnt/EFI/refind/
  total 260
  drwxr-xr-x 2 root root   4096 Mar 21 17:13 drivers_x64
  -rwxr-xr-x 1 root root 208776 Mar 21 17:14 refind_x64.efi
  drwxr-xr-x 3 root root   8192 Mar 21 17:18 icons
  drwxr-xr-x 2 root root   4096 Apr  8 13:39 vars
  drwxr-xr-x 5 root root   4096 Apr  8 13:39 ..
  -rwxr-xr-x 1 root root  32233 Apr 16 22:55 refind.conf
  drwxr-xr-x 5 root root   4096 Apr 16 22:55 .

  ...
 |What is wrong here? What am I missing?

Maybe that helps.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

[Toomas Soome]

> On 22 Aug 2019, at 06:04, O. Hartmann  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Am Wed, 21 Aug 2019 22:29:29 +
> greg@unrelenting.technology schrieb:
> 
>> August 22, 2019 12:23 AM, "O. Hartmann"  wrote:
>> 
>>> Am Wed, 21 Aug 2019 15:58:24 -0500
>>> Karl Denninger  schrieb:
>>> 
 I would see if you can get REFIND loaded and use that.  I have a Lenovo
 X1 Carbon Gen 6 and that's the answer I used, as it allows multi-boot
 (e.g. Win10 and FreeBSD) easily.  
>>> 
>>> mmmhhh, Linux software to make FreeBSD boot? ;-)  
>> 
>> rEFInd is not "Linux software", I use it to get a nice menu to choose 
>> between FreeBSD and
>> Windows on my desktop. No Linux in sight. If anything, rEFInd has its roots 
>> in Macs :)
> 
> My apologizes; when searching the net, the first "logo" I see is this silly 
> penguine face. I'm
> sorry about making such simple implications.
> 
>> 
>>> This Lenovo firmware seems very reluctant or the efibootmgr doesn't operate 
>>> properly on
>>> setting variables: when trying to label the boot number (e.g. Boot000A) 
>>> with "-L FreeBSD",
>>> it is always set back to "Boot000A ATA HDD0". On other platforms, like 
>>> Fujitsu servers or
>>> even the cheap crap from ASRock a label once set is permenent until 
>>> deleted.  
>> 
>> Many laptops just ignore the boot variables outright. My X240 is the same.
>> I never switched to a proper efibootmgr setup on mine, I just have 
>> loader.efi as bootx64.efi
>> and that's it.
> 
> I tried copying loader.efi as bootx64.efi - but didn't help.
> 
 If there's a way to get into the EFI shell on Lenovo's laptops from the
 BIOS during the boot I've not found it yet.  There's supposed to be on
 all EFI devices, but you know how "supposed to" works in many cases, 
 right?  
>> 
>> You can just download the EFI Shell from the internet, it's a normal .efi 
>> executable you can
>> "boot". Put it as efi/boot/bootx64.efi onto a USB flash drive and enjoy.
> 
> I'll give this a chance as soon I have hands on the workitem again.
> 

The reason to try rEFInd and/or EFI shell is to see if we get extra error 
messages otherwise hidden by GUI.

In any case, to get to the root cause, we would need to start to insert more 
debug printouts and see what we will find. Once you are ready to go with it, 
you can poke me directly and then we can start…

rgds,
toomas

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Working ath10k device?

[Steve Kargl]

On Wed, Aug 21, 2019 at 10:39:33PM -0400, Anthony Jenkins wrote:
> On 8/2/19 6:19 PM, Steve Kargl wrote:
> > I have a Dell XPS 13 that reports the wifi chip is
> > a Qualcomm Atheros 6147.  I've found Adrain's WIP
> > driver, and built it.  I'm seeing the panic reported
> > at
> >
> > https://lists.freebsd.org/pipermail/freebsd-current/2019-February/072769.html
> >
> > Does anyone have a /dev/if_athp.ko and firmware?
> >
> I pushed a simple fix to my github repo - 
> https://github.com/ScoobiFreeBSD/athp/pull/1
> 

Thanks for the heads up.  I'll pull down the source and see what
progress I can make.  Unfortunately, Real Work(tm) sidetrack my
efforts of getting the Dell up and running.

-- 
Steve
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: panic... r350849M panic: ng_snd_item: 42 != 1414

[Andrey V. Elsukov]

On 20.08.2019 16:26, Larry Rosenman wrote:
> the M is a patch from rrs@ for the previous crash on m_pullup.
> 
> Ideas?  I have a core.
> 
> 
> Unread portion of the kernel message buffer:
> panic: ng_snd_item: 42 != 1414

I think you had the same panic about a month ago. Probably it is time to
fill the PR.

-- 
WBR, Andrey V. Elsukov



signature.asc
Description: OpenPGP digital signature

Re: hdac0: Unexpected unsolicited response from address 0: 00000000

[Justin Hibbits]

On Wed, 21 Aug 2019 13:23:05 +0200
"Hartmann, O."  wrote:

> Hello list,
> 
> on a Lenovo E540 I get this weird error since I used 12-STABLE/CURRENT
> on this specific notebook. I guess it has a Optimus Intel iGPU/nVidia
> NV940 GPU system and usable is only the iGPU with port
> graphics/drm-fbsd12.0-kmod.
> 
> The notebook doesn't have audio anymore, nor can I use vlc, mplayer or
> smplayer anymore, the applications are stuck as they are waiting for
> the audio which never comes up. The same in Firefox (recent versions),
> videos, i.e. via youtube, never played since a while now.
> 
> I can't say when this problem first occured, it is now for a while,
> say 6 or 8 months so. I receive massive kernel messages on the
> console like
> 
> [...]
> hdac0: Unexpected unsolicited response from address 0: 
> hdac0: Unexpected unsolicited response from address 0: 
> hdac0: Unexpected unsolicited response from address 0: 
> [...]
> 
> What is wrong here?
> 
> Thanks,
> 
> oh
> 
> The dmesg shows:
> 
> ---<>---
> Copyright (c) 1992-2019 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993,
> 1994 The Regents of the University of California. All rights
> reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 12.0-STABLE #61 r351164: Sat Aug 17 08:37:38 CEST 2019
> root@toedd:/usr/obj/usr/src/amd64.amd64/sys/TOEDD amd64
> FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on
> LLVM 8.0.1)
> VT(efifb): resolution 1920x1080
> module zfsctrl already present!
> module_register: cannot register tmpfs from kernel; already loaded
> from tmpfs.ko
> Module tmpfs failed to register: 17
> CPU: Intel(R) Core(TM) i5-4200M CPU @ 2.50GHz (2494.28-MHz K8-class
> CPU) Origin="GenuineIntel"  Id=0x306c3  Family=0x6  Model=0x3c
> Stepping=3
> Features=0xbfebfbff
> Features2=0x7fdafbbf
> AMD Features=0x2c100800 AMD
> Features2=0x21 Structured Extended
> Features=0x27ab
>   Structured Extended Features3=0x9c00
>   XSAVE Features=0x1
>   VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
>   TSC: P-state invariant, performance statistics
> real memory  = 17179869184 (16384 MB)
> avail memory = 16439214080 (15677 MB)
> Event timer "LAPIC" quality 600
> ACPI APIC Table: 
> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
> FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 hardware threads
> random: unblocking device.
> Security policy loaded: MAC/ntpd (mac_ntpd)
> ioapic0  irqs 0-23 on motherboard
> Launching APs: 1 3 2
> Timecounter "TSC-low" frequency 1247140210 Hz quality 1000
> random: entropy device external interface
> kbd1 at kbdmux0
> module_register_init: MOD_LOAD (vesa, 0x80d41390, 0) error 19
> [...]
> 
> 
> [...]
> dmesg|grep hda
> hdac0:  mem 0xf161-0xf1613fff at
> device 3.0 on pci0 hdac1:  mem
> 0xf1614000-0xf1617fff at device 27.0 on pci0 hdacc0:  HDA
> CODEC> at cad 0 on hdac0 hdaa0: 
> CODEC> at nid 1 on hdacc0  
> pcm0:  at nid 3 on hdaa0
> hdacc1:  at cad 0 on hdac1
> hdaa1:  at nid 1 on hdacc1
> pcm1:  at nid 23 on
> hdaa1 pcm2:  at nid 22
> on hdaa1 hdac0: Unexpected unsolicited response from address 0:
>  hdac0: Unexpected unsolicited response from address 0:
>  hdac0: Unexpected unsolicited response from address 0:
>  hdac0: Unexpected unsolicited response from address 0:
> 

I see that on my Talos, with my Radeon card, when the PCI bus is reset.
 In my case, it causes a panic, too.

- Justin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: hdac0: Unexpected unsolicited response from address 0: 00000000

[Poul-Henning Kamp]

In message <20190821132305.1c11bb9c@hermann>, "Hartmann, O." writes:

>on a Lenovo E540 I get this weird error since I used 12-STABLE/CURRENT

>[...]
>hdac0: Unexpected unsolicited response from address 0: 
>hdac0: Unexpected unsolicited response from address 0: 
>hdac0: Unexpected unsolicited response from address 0: 
>[...]

I used to get a lot of similar-ish noise on my T480, but it seems
to have disappeared with my latest update to -CURRENT.

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

hdac0: Unexpected unsolicited response from address 0: 00000000

[Hartmann, O.]

Hello list,

on a Lenovo E540 I get this weird error since I used 12-STABLE/CURRENT
on this specific notebook. I guess it has a Optimus Intel iGPU/nVidia
NV940 GPU system and usable is only the iGPU with port
graphics/drm-fbsd12.0-kmod.

The notebook doesn't have audio anymore, nor can I use vlc, mplayer or
smplayer anymore, the applications are stuck as they are waiting for
the audio which never comes up. The same in Firefox (recent versions),
videos, i.e. via youtube, never played since a while now.

I can't say when this problem first occured, it is now for a while, say
6 or 8 months so. I receive massive kernel messages on the console like

[...]
hdac0: Unexpected unsolicited response from address 0: 
hdac0: Unexpected unsolicited response from address 0: 
hdac0: Unexpected unsolicited response from address 0: 
[...]

What is wrong here?

Thanks,

oh

The dmesg shows:

---<>---
Copyright (c) 1992-2019 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights
reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.0-STABLE #61 r351164: Sat Aug 17 08:37:38 CEST 2019
root@toedd:/usr/obj/usr/src/amd64.amd64/sys/TOEDD amd64
FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on
LLVM 8.0.1)
VT(efifb): resolution 1920x1080
module zfsctrl already present!
module_register: cannot register tmpfs from kernel; already loaded from
tmpfs.ko
Module tmpfs failed to register: 17
CPU: Intel(R) Core(TM) i5-4200M CPU @ 2.50GHz (2494.28-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x306c3  Family=0x6  Model=0x3c  Stepping=3
  
Features=0xbfebfbff
  
Features2=0x7fdafbbf
  AMD Features=0x2c100800
  AMD Features2=0x21
  Structured Extended
Features=0x27ab
  Structured Extended Features3=0x9c00
  XSAVE Features=0x1
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
real memory  = 17179869184 (16384 MB)
avail memory = 16439214080 (15677 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 hardware threads
random: unblocking device.
Security policy loaded: MAC/ntpd (mac_ntpd)
ioapic0  irqs 0-23 on motherboard
Launching APs: 1 3 2
Timecounter "TSC-low" frequency 1247140210 Hz quality 1000
random: entropy device external interface
kbd1 at kbdmux0
module_register_init: MOD_LOAD (vesa, 0x80d41390, 0) error 19
[...]


[...]
dmesg|grep hda
hdac0:  mem 0xf161-0xf1613fff at
device 3.0 on pci0 hdac1:  mem
0xf1614000-0xf1617fff at device 27.0 on pci0 hdacc0:  at cad 0 on hdac0 hdaa0:  at
CODEC> nid 1 on hdacc0
pcm0:  at nid 3 on hdaa0
hdacc1:  at cad 0 on hdac1
hdaa1:  at nid 1 on hdacc1
pcm1:  at nid 23 on hdaa1
pcm2:  at nid 22 on hdaa1
hdac0: Unexpected unsolicited response from address 0: 
hdac0: Unexpected unsolicited response from address 0: 
hdac0: Unexpected unsolicited response from address 0: 
hdac0: Unexpected unsolicited response from address 0: 


pgpFAxTFoeOu_.pgp
Description: OpenPGP digital signature