Acpi bios error bug a valid rsdp was not found

Others have experienced similar issues surrounding kdump on efi systems: http://lists.infradead.org/pipermail/kexec/2012-October/006924.html http://lists.infradead.org/pipermail/kexec/2010-March/00...

@vcaputo

nh2

added a commit
to nh2/kexec-tools
that referenced
this issue

Apr 28, 2019

@nh2

In many situations, especially on read-only file systems
and initial ramdisks (intramfs/initrd), /etc/mtab does not exist.

Before this commit, kexec would fail to read mounts on such systems
in `find_mnt_by_fsname()`, such that `get_bootparam()` would not
`boot_params/data`, which would then lead to e.g. `setup_efi_data()`
not being called in `setup_efi_info()`.

As a result, kexec'ed kernels would not obtain EFI data,
subsequentially lack an `ACPI RSDP` entry, and thus fail to turn off the
machine on poweroff, instead printing only `reboot: System halted`.

This problem had to be worked around by passing `acpi_rsdp=` manually
before. This commit obviates this workaround.

See also:

* coreos/bugs#167 (comment)
* http://lists.infradead.org/pipermail/kexec/2012-October/006924.html

nh2

added a commit
to nh2/kexec-tools
that referenced
this issue

Apr 28, 2019

@nh2

In many situations, especially on read-only file systems
and initial ramdisks (intramfs/initrd), /etc/mtab does not exist.

Before this commit, kexec would fail to read mounts on such systems
in `find_mnt_by_fsname()`, such that `get_bootparam()` would not
`boot_params/data`, which would then lead to e.g. `setup_efi_data()`
not being called in `setup_efi_info()`.

As a result, kexec'ed kernels would not obtain EFI data,
subsequentially lack an `ACPI RSDP` entry, emitting:

    ACPI BIOS Error (bug): A valid RSDP was not found (20180810/tbxfroot-210)

and thus fail to turn off the machine on poweroff, instead printing only:

		reboot: System halted

This problem had to be worked around by passing `acpi_rsdp=` manually
before. This commit obviates this workaround.

See also:

* coreos/bugs#167 (comment)
* http://lists.infradead.org/pipermail/kexec/2012-October/006924.html

Signed-off-by: Niklas Hambüchen <mail@nh2.me>

horms

pushed a commit
to horms/kexec-tools
that referenced
this issue

May 15, 2019

@nh2

@horms

In many situations, especially on read-only file systems
and initial ramdisks (intramfs/initrd), /etc/mtab does not exist.

Before this commit, kexec would fail to read mounts on such systems
in `find_mnt_by_fsname()`, such that `get_bootparam()` would not
`boot_params/data`, which would then lead to e.g. `setup_efi_data()`
not being called in `setup_efi_info()`.

As a result, kexec'ed kernels would not obtain EFI data,
subsequentially lack an `ACPI RSDP` entry, emitting:

    ACPI BIOS Error (bug): A valid RSDP was not found (20180810/tbxfroot-210)

and thus fail to turn off the machine on poweroff, instead printing only:

		reboot: System halted

This problem had to be worked around by passing `acpi_rsdp=` manually
before. This commit obviates this workaround.

See also:

* coreos/bugs#167 (comment)
* http://lists.infradead.org/pipermail/kexec/2012-October/006924.html

Signed-off-by: Niklas Hambüchen <mail@nh2.me>
Signed-off-by: Simon Horman <horms@verge.net.au>

Правила форума
Убедительная просьба юзать теги [code] при оформлении листингов.
Сообщения не оформленные должным образом имеют все шансы быть незамеченными.

NewUse

рядовой
Сообщения: 20
Зарегистрирован: 2010-03-26 2:51:29

ACPI на динозавре (ZIDA BXi98-ATX)

Помогите заставить выключаться нормально старый комп с FreeBSD 7.2, не хочет подхватывать старые ACPI, та же проблема встречалась и на Asus TX97-E….

Код: Выделить всё

ACPI Error (tbxfroot-0308): A valid RSDP was not found [20070320]
ACPI: Table initialisation failed: AE_NOT_FOUND
ACPI: Try disabling either ACPI or apic support. 

Зы:
apm тоже не подхватывается :((

Последний раз редактировалось f_andrey 2010-03-26 4:36:07, всего редактировалось 1 раз.

Причина: Автору, выбирайте пожалуйста раздел соответствуюший тематике вашего сообщения.


Хостинговая компания Host-Food.ru

Хостинг HostFood.ru

 

Услуги хостинговой компании Host-Food.ru

Хостинг HostFood.ru

Тарифы на хостинг в России, от 12 рублей: https://www.host-food.ru/tariffs/hosting/
Тарифы на виртуальные сервера (VPS/VDS/KVM) в РФ, от 189 руб.: https://www.host-food.ru/tariffs/virtualny-server-vps/
Выделенные сервера, Россия, Москва, от 2000 рублей (HP Proliant G5, Intel Xeon E5430 (2.66GHz, Quad-Core, 12Mb), 8Gb RAM, 2x300Gb SAS HDD, P400i, 512Mb, BBU):
https://www.host-food.ru/tariffs/vydelennyi-server-ds/
Недорогие домены в популярных зонах: https://www.host-food.ru/domains/


Гость

проходил мимо

Re: ACPI на динозавре (ZIDA BXi98-ATX)

Непрочитанное сообщение

Гость » 2010-03-26 10:45:45

у вас три варианта
1) обновить биос
2) обновить БСД
3) написать в рассылку freebsd-acpi@
выбирайте любой или одновременно все


NewUse

рядовой
Сообщения: 20
Зарегистрирован: 2010-03-26 2:51:29

Re: ACPI на динозавре (ZIDA BXi98-ATX)

Непрочитанное сообщение

NewUse » 2010-03-26 13:50:45

1)Более нового БИОСа нет.
2)А поможет ли? Достаточно ли скачать исходники модуля ACPICA для FreeBSD-9 и пересобрать именно модуль ACPI или надо полностью мир и ядро обновлять?
3)А как это сделать? Что и куда посылать?


NewUse

рядовой
Сообщения: 20
Зарегистрирован: 2010-03-26 2:51:29

Re: ACPI на динозавре (ZIDA BXi98-ATX)

Непрочитанное сообщение

NewUse » 2010-03-26 15:20:49

Я совсем чайник :(, только недавно ХэндБук прочёл до конца…., Спасибо, отписал…

2) вам сказали БСД обновить а не какие то модули(хотите секса от каких то модулей? вперед)

Ок, попробую, но позже, а то пересобирать мир на этой тачке то ещё удовольствие…. Да и с этим дурацким поиском различай большой гемор….. Кста, можно ли как-то его настроить только на определённые файлы?


Гость

проходил мимо

Re: ACPI на динозавре (ZIDA BXi98-ATX)

Непрочитанное сообщение

Гость » 2010-03-26 15:27:08

если вы разбиратесь, то нет никакой сложности обновить только один ACPI и пересобрать всю БСД

кстати 7.2 желательно обновите до СТЕИБЛА, а иначе на вас просто забьют, потому что нет смысла разбираться с проблемами которые уже возможно пофиксили в стеибле


NewUse

рядовой
Сообщения: 20
Зарегистрирован: 2010-03-26 2:51:29

Re: ACPI на динозавре (ZIDA BXi98-ATX)

Непрочитанное сообщение

NewUse » 2010-03-26 16:01:36

кстати 7.2 желательно обновите до СТЕИБЛА, а иначе на вас просто забьют, потому что нет смысла разбираться с проблемами которые уже возможно пофиксили в стеибле

а не подскажите какой командой узнать текущую версию и тип (может уже стейбл, я не помню, на какую обновлял….)
хотя, нет, в dmesg релиз записан….
На что порекомендуете обновить? на 8.0 на 7.3, 7.2 стейбл или сразу на 9.0?


_Gendos_^..^_

проходил мимо

Re: ACPI на динозавре (ZIDA BXi98-ATX)

Непрочитанное сообщение

_Gendos_^..^_ » 2010-03-26 19:20:49

Под столом лежит TX-97 4-ка на нём была замечательна чего и Вам желаю. А ну еще redhat 5.2 крутился без проблем.


NewUse

рядовой
Сообщения: 20
Зарегистрирован: 2010-03-26 2:51:29

Re: ACPI на динозавре (ZIDA BXi98-ATX)

Непрочитанное сообщение

NewUse » 2010-03-30 1:07:20

Под столом лежит TX-97 4-ка на нём была замечательна чего и Вам желаю.

если бы не кернел нат поставил бы именно 4-ку, но кернел нат больно удобная зараза…


  • #1

Greetings, all.

I’m attempting to configure an optimal kernel on RELENG_8 (8.8-STABLE). As I parse the dmesg output from the DVD installation’s GENERIC, I see the following:

Code:

CPU0: local APIC error 0x80
ACPI Error: A valid RSDP was not found (20101013/tbxfroot-309)
ACPI: Table initialisation failed: AE_NOT_FOUND
ACPI: Try disabling either ACPI or apic support.

This is a 2 CPU TYAN Thunder LE-T S2518. While I realize it’s an old board. I thought I’d put it to good use, by turning it into a POINTYHAT. So I could create releases (kernels/world/etc) for the many different ARCs I run. I had already updated the BIOS to the most recent TYAN had to offer. So I guess my question is: what to do regarding a KERNCONF for the error indicated by dmesg output?

Thank you for all your time, and consideration.

—Chris

  • Index
  • » Kernel & Hardware
  • » Trying to get kdump to work, doesn’t load crash kernel on crash

Pages: 1

#1 2018-11-17 15:55:34

Torxed
Member
Registered: 2013-01-10
Posts: 194

Trying to get kdump to work, doesn’t load crash kernel on crash

When I do

# echo c > /prov/sysreq-trigger

I expect to enter a kernel where I can dump

But for whatever reason, that crash kernel never «boots» meaning I can’t get access to vmcore.

I’ve followed: https://wiki.archlinux.org/index.php/Kdump meticulously.
Followed a bunch of other resources such as: https://unix.stackexchange.com/question … arch-linux

What I’ve ended up with is a service script (tried manually as well) that looks like this:

[Unit]
Description=Load dump capture kernel
After=local-fs.target

[Service]
ExecStart=kexec -p /boot/vmlinuz-wifi --initrd=/boot/initramfs-linux419.img --apend="root=/dev/mapper/luksdev systemd.unit=kdump-save.service single irqpoll maxcpus=1 reset_devices"
Type=oneshot

[Install]
WantedBy=multi-user.target
# cat /proc/cmdline
initrd=intel-ucode.img initrd=initramfs-linux419.img cryptodevice=UUID=<uuid>:luksdev root=/dev/mapper/luksdev rw crashkernel=256M intel_pstate=no_hwp i915.enable_guc=3
# ls -l /boot/vmlinuz-wifi
-rwxr-xr-x 1 root root 5686144 Nov 17 13:14 /boot/vmlinuz-wifi

# ls -l /boot/initramfs-linux419.img
-rwxr-xr-x 1 root root 9351628 Nov 17 14:04 /boot/initramfs-linux419.img
# cat /sys/kernel/kexec_crash_loaded
1

The kernel was compiled with (which appears to be default in the arch kernel?):

CONFIG_DEBUG_INFO=y
CONFIG_CRASH_DUMP=y
CONFIG_PROC_VMCORE=y
# journalctl -u kdump
-- Reboot --
Nov 17 16:43:45 Archinstall systemd[1]: Starting Load dump capture kernel...
Nov 17 16:43:46 Archinstall systemd[1]: Started Load dump capture kernel.

I’ve rebooted a couple of times, tried manual approaches to loading in the kernel dump etc.
Any ideas where to begin debugging the debugger-mess? I’ve run out of ideas (and experience in kernel debugging) but suspect the culprint to be the luksdev device, will the crash kernel retain the unlocked disk?

Last edited by Torxed (2018-11-17 16:10:16)

#2 2018-11-17 17:37:42

Torxed
Member
Registered: 2013-01-10
Posts: 194

Re: Trying to get kdump to work, doesn’t load crash kernel on crash

So as soon as you ask for help, it starts working (sorta).
I finally managed to get it to boot some how, most likely one of the config flags got screwed up even tho I double-checked them.

Had to change the `root=…` as well to match that of the output of `cat /proc/cmdline` (which should have been obvious).

The problem now, is that the luksdev passphrase input doesn’t register any input..
Not sure if the HID got broken in the boot process or something. Not that I know what I’m talking about or anything..

#3 2018-11-17 17:40:19

loqs
Member
Registered: 2014-03-06
Posts: 15,644

Re: Trying to get kdump to work, doesn’t load crash kernel on crash

How did you produce the .config for the custom kernel?

#4 2018-11-17 17:42:37

Torxed
Member
Registered: 2013-01-10
Posts: 194

Re: Trying to get kdump to work, doesn’t load crash kernel on crash

loqs wrote:

How did you produce the .config for the custom kernel?

I went with option B:

I can boot the kernel that was built, but it won’t boot in recovery situation.
Gets stuck on keyboard input.

If I use a external keyboard (laptop btw), I get the following during crash-kernel-boot:

xhci_hcd 0000:00:14.0: Error while assining device slot ID
xhci_hcd 0000:00:14.0: Max number of devices this xHCI host supports is 64
usb usb1-port1: couldn't allocate usb_device

Last edited by Torxed (2018-11-17 17:46:53)

#5 2018-11-17 17:49:55

loqs
Member
Registered: 2014-03-06
Posts: 15,644

Re: Trying to get kdump to work, doesn’t load crash kernel on crash

Never used kdump so this could be completely wrong

xhci_hcd 0000:00:14.0: Error while assining device slot ID
xhci_hcd 0000:00:14.0: Max number of devices this xHCI host supports is 64

That output seems to be because xhci_hcd has read spurious data (from the firmware?) and is trying to add numerous USB controllers.

#6 2018-11-17 17:52:59

Torxed
Member
Registered: 2013-01-10
Posts: 194

Re: Trying to get kdump to work, doesn’t load crash kernel on crash

loqs wrote:

Never used kdump so this could be completely wrong

xhci_hcd 0000:00:14.0: Error while assining device slot ID
xhci_hcd 0000:00:14.0: Max number of devices this xHCI host supports is 64

That output seems to be because xhci_hcd has read spurious data (from the firmware?) and is trying to add numerous USB controllers.

It’s probably because of the no-name brand keyboard, which probably does more than it should hehe.
Never the less, the built-in keyboard in the laptop should be working out of the box.

#7 2018-11-17 18:04:09

loqs
Member
Registered: 2014-03-06
Posts: 15,644

Re: Trying to get kdump to work, doesn’t load crash kernel on crash

The system uses the same kernel on boot and kexec but the built-in keyboard only fails on kexec or it fails on boot as well?

#8 2018-11-17 18:39:07

Torxed
Member
Registered: 2013-01-10
Posts: 194

Re: Trying to get kdump to work, doesn’t load crash kernel on crash

loqs wrote:

The system uses the same kernel on boot and kexec but the built-in keyboard only fails on kexec or it fails on boot as well?

Only fails on kexec :)

#9 2018-11-17 18:56:58

loqs
Member
Registered: 2014-03-06
Posts: 15,644

Re: Trying to get kdump to work, doesn’t load crash kernel on crash

Torxed wrote:

loqs wrote:

The system uses the same kernel on boot and kexec but the built-in keyboard only fails on kexec or it fails on boot as well?

Only fails on kexec smile

That would indicate to me that keyboard support is correct but the state the system is in on kexec is causing the issue.  (No idea how to resolve it)
Edit:
The initrd’s are the same as well?

Last edited by loqs (2018-11-17 18:57:29)

#10 2018-11-17 19:36:44

Torxed
Member
Registered: 2013-01-10
Posts: 194

Re: Trying to get kdump to work, doesn’t load crash kernel on crash

loqs wrote:

The initrd’s are the same as well?

That’s correct. I made sure they were via:

# echo $(cat /proc/cmdline) >> /etc/systemd/system/kdump.service

And added the initrd + kernel options to the `ExecStart` line.<br>
So whatever systemd-boot uses to boot my system entry should be 100% identical to whatever kexec executes.

After a few boots, I got this error message:

ACPI BIOS Error (bug): A valid RSDP was not found (20180810/tbxfroot-210)
[Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSD 38d is b0)
efi: EFI_MEMMAP is not enabled.

Which lead me to: https://askubuntu.com/questions/613241/ … ot-working

Unfortunately the information given isn’t helpful but the title says exactly the same thing I’m struggling with.
And most resources say that those messages can be ignored, since it’s more of a BIOS glitch that shouldn’t have any OS impact in the laptop i’m using.

Also tried telling kexec to boot my «normal kernel» to see if it was something specific to my own build.
Turns out, that get stuck on the same step, the HID being dead (when booted via kexec, works otherwise)

Last edited by Torxed (2018-11-17 23:14:22)

Topic: 15.1.6.1 not booting on Soekris net6501  (Read 33375 times)

I just installed (twice) the new version. i386 serial USB drive.

Installation went without a problem, apart from the Local Echo problem which makes reading almost anything from start till I press the Enter key on the menu (I can sorta see the box it draws for the menu options).
After that I displays everything just fine.
Got the same thing with pfSense. Baud speed of 19200 (in case of pfSense) and 115200 don’t matter.
Local Echo is at Auto. On of Off won’t make a difference.

Anyway, the big problem is that on bootup I see the selecting F1 FreeBSD and F6 PXE, and once it starts it reboots the machines. Not even the /boot/serialwhatever line.

Below is what I see in the serial console.

1 Seconds to automatic boot.   Press Ctrl-P for entering Monitor.

F1  FreeBSD

F6 PXE
Boot:  F1

POST: 0123456789bcefghipsajklnopqr,,,tvwxy

comBIOS ver. 1.41c  20121115  Copyright (C) 2000-2011 Soekris Engineering.

net6501

0512 Mbyte Memory                        CPU Atom E6xx 600 Mhz

On the second installation I did a Custom install to see if I could select anything special.
But that is not the case.


Logged

Hobbyist at home, sysadmin at work. Sometimes the first is mixed with the second.


yup, I can confirm this behavior with my net6501. installation onto an mSATA SSD went fine but then it’ll never boot properly. I had zero trouble to get OPNsense up and running on my PC Engines APU though…

regards,
michael


Logged


Good to hear it’s not just me then.


Logged

Hobbyist at home, sysadmin at work. Sometimes the first is mixed with the second.



Logged


Didn’t know that link yet. I used the pfSense wiki page before. Not that much info there, ad it pretty much just worked.
I will try and check things tomorrow.
And if I can’t get it to work, I hopefully will have my Supermicro Superserver in by next weekend so I can run OPNsense virtualized. And then perhaps I could ship you my net6501 for testing.


Logged

Hobbyist at home, sysadmin at work. Sometimes the first is mixed with the second.


That would be awesome. I’m guessing it needs a bit of loader tweaks, which need to go in the installer / direct disk images as soon as the build support is here.


Logged


Hi,
i See the following on the serial console booting it up on the 6501
jakob

KDB: debugger backends: ddb        d                      s                 +   x8
KDB: current backend: ddb
ACPI BIOS Error (bug): A valid RSDP was not found (20130823/tbxfroot-223)
panic: running without device atpic requires a local APIC
cpuid = 0
KDB: enter: panic
[ thread pid 0 tid 0 ]
Stopped at      kdb_enter+0x3e: movq    $0,kdb_why
db>


Logged


Hi,
i See the following on the serial console booting it up on the 6501
jakob

KDB: debugger backends: ddb        d                      s                 +   x8
KDB: current backend: ddb
ACPI BIOS Error (bug): A valid RSDP was not found (20130823/tbxfroot-223)
panic: running without device atpic requires a local APIC
cpuid = 0
KDB: enter: panic
[ thread pid 0 tid 0 ]
Stopped at      kdb_enter+0x3e: movq    $0,kdb_why
db>

I have seen this error on a mailing list before with pfSense 2.2-Alpha but as far as I know the issue was caused by trying to run a amd64 version instead of 32bit. See this: http://lists.pfsense.org/pipermail/list/2014-April/006016.html


Logged


jschellevis,
I think you are right. (I was inserting the image from my APU into the 6501)
Jakob


Logged


Can you try again with 32bit image? Perhaps we can get a bit more information on what is going wrong…
It may just be the baudrate as I think the soekris boards do not like it that the bootloader switches to 115200.

If so you can try to change the /boot.config file to -S19200 -D and also change the config.xml with same serial speed…


Logged


I take it I have to do that after installing and choosing the Shell option before the reboot?
I’m not familiar with *BSD when it comes to installing and troubleshooting. More Linux which I try to never ever use again.

I’m at work right now, so will have to wait till tonight before I can try.


Logged

Hobbyist at home, sysadmin at work. Sometimes the first is mixed with the second.


You will have to mount the partition from a working system and make the changes if it does not boot at all.

If it boots but does not show serial output then you can make the config.xml change in the GUI (select the correct serial speed) and the other from the shell by using ssh (enable ssh in the Advanced menu).

I can also create an image for you with 19200 that you can dd onto a CF (lets say 2Gb) if you are not able to do it yourself.


Logged


It doesn’t boot at all, just shows the selection (F1 FreeBSD, and F6 PXE) and after selecting F1 (pressing enter that is) it just reboots.

I might try altering it from pfSense by placing the second SSD (the one with OPNsense on it) and use it’s shell to alter the OPNsense files.

If instead of a CF I can use a USB flash drive too, then sure. The net6501 doesn’t have a CF slot.
Only mSATA and USB ports.

Right now I don’t have a working FreeBSD workstation installation as the laptop I was trying to install it on refuses to boot from the hard drive.


Logged

Hobbyist at home, sysadmin at work. Sometimes the first is mixed with the second.


jschellevis,
I will try a 32 bit version on the 6501 this evening.
Jakob


Logged


Hi,
I can confirm 6501 i386 does not boot from mSATA.
Here is what I did:
— loaded the opensense i386 to the USB
— (I) install to mSATA SSD
— reboot —>> wich fails, see log below

Remark: what is the block size the installer writes to the mSATA SSD?
I had problems (in another case) when I used large block i.e 64k writing the image with dd. After I used bs=512 all went well.
Jakob

6501 Console LOG:
5 Seconds to automatic boot.   Press Ctrl-P for entering Monitor.

F1  FreeBSD
F6 PXE
Boot:  F1
POST: 0123456789bcefghipsajklnopqr,,,tvwxy
comBIOS ver. 1.41c  20121115  Copyright (C) 2000-2011 Soekris Engineering.
net6501
2048 Mbyte Memory                        CPU Atom E6xx 1600 Mhz
SATA AHCI BIOS ver. 0.61 20121115  Copyright (C) 2003-2011 Intel Corporation
Controller Bus#02, Device#06, Function#00: 02 Ports, 01 Devices
 Port-00: Hard Disk, SATA SSD
 Port-01: No device detected
Soekris USB Expansion ROM ver. 1.01  20111203

Initializing Intel(R) Boot Agent GE v1.3.72
PXE 2.1 Build 089 (WfM 2.0)

Slot   Vend Dev  ClassRev Cmd  Stat CL LT HT  Base1    Base2   Int
———————————————————————
00:00:0 8086 4114 06000005 0007 0000 00 00 00 00000000 00000000
00:23:0 8086 8184 06040000 0107 0010 08 00 01 1FFF1000 A0FFA000 10
00:24:0 8086 8185 06040000 0107 0010 08 00 01 3FFF2000 A2FFA100 11
00:25:0 8086 8180 06040000 0107 0010 08 00 01 5FFF4000 A4FFA300 05
00:26:0 8086 8181 06040000 0107 0010 08 00 01 0FFF1000 00FFA000 09
00:31:0 8086 8186 06010000 0003 0000 00 00 80 00000000 00000000
02:02:0 8086 8804 0C031002 0106 0010 00 00 80 A0000B00 00000000 09
02:02:1 8086 8805 0C031002 0106 0010 00 00 80 A0000C00 00000000 09
02:02:2 8086 8806 0C031002 0106 0010 00 00 80 A0000D00 00000000 09
02:02:3 8086 8807 0C032002 0106 0010 00 00 80 A0000E00 00000000 09
02:06:0 8086 880B 01060102 0107 0010 00 00 00 00000000 00000000 11
02:08:0 8086 880C 0C031002 0106 0010 00 00 80 A0004800 00000000 10
02:08:1 8086 880D 0C031002 0106 0010 00 00 80 A0004900 00000000 10
02:08:2 8086 880E 0C031002 0106 0010 00 00 80 A0004A00 00000000 10
02:08:3 8086 880F 0C032002 0106 0010 00 00 80 A0004B00 00000000 10
02:10:1 8086 8811 07000201 0107 0010 00 00 80 00001041 A0004D00 09
02:10:2 8086 8812 07000200 0107 0010 00 00 80 00001049 A0004D10 09
02:12:2 8086 8817 0C800000 0106 0010 00 00 80 00000000 A0005000 05
02:12:3 8086 8818 0C090000 0106 0010 00 00 80 00000000 A0005200 05
03:00:0 111D 803A 0604000E 0107 0010 08 00 01 3FFF2000 A2FFA100
05:00:0 8086 10D3 02000000 0107 0010 08 00 00 A1000000 00000000 09
06:00:0 8086 10D3 02000000 0107 0010 08 00 00 A2000000 00000000 10
08:00:0 111D 803A 0604000E 0107 0010 08 00 01 5FFF4000 A4FFA300
10:00:0 8086 10D3 02000000 0107 0010 08 00 00 A3000000 00000000 10
11:00:0 8086 10D3 02000000 0107 0010 08 00 00 A4000000 00000000 11

1 Seconds to automatic boot.   Press Ctrl-P for entering Monitor.
F1  FreeBSD
F6 PXE
Boot:  F1

This repeats on and on.


Logged


I’ve installed according to https://wiki.alpinelinux.org/wiki/Create_a_Bootable_Compact_Flash#Automated and successfully activated serial console as outlined in https://wiki.alpinelinux.org/wiki/Enable_Serial_Console_on_Boot#Example_syslinux.cfg .

Now when I boot, I get this error:

[    0.000000] ACPI BIOS Error (bug): A valid RSDP was not found (20160831/tbxfroot-244)
[    1.826586] ACPI BIOS Error (bug): A valid RSDP was not found (20160831/tbxfroot-244)
[    2.292134] dmi: Firmware registration failed.
[   11.617601] i8042: Can't read CTR while initializing i8042
[   11.648009] microcode: no support for this CPU vendor
Mounting boot media failed.
initramfs emergency recovery shell launched. Type 'exit' to continue boot
sh: can't access tty; job control turned off
/ #

I am dropped to a shell, /sysroot is empty and I cannot find any of the disks:

/ # modprobe vfat && cd /dev && ls  | grep -vE 'ram|tty|loop'
bus
console
cpu_dma_latency
full
grsec
kmsg
mem
memory_bandwidth
network_latency
network_throughput
null
ptmx
pts
random
rd
rtc0
shm
urandom
vcs
vcs1
vcsa
vcsa1
vga_arbiter
zero

These are the current mounts:

/ # mount
rootfs on / type rootfs (rw,size=56804k,nr_inodes=14201)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,relatime,size=2048k,nr_inodes=14203,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime)

This is the system, as shown by the BIOS while booting:

comBIOS ver. 1.33  20080103  Copyright (C) 2000-2007 Soekris Engineering.

net4801

0128 Mbyte Memory                        CPU Geode SC1100 233 Mhz

Pri Mas  SanDisk SDCFX3-4096             LBA Xlt 995-128-63  4013 Mbyte
Pri Sla  HTS726060M9AT00                 LBA Xlt 1024-255-63  58605 Mbyte

How can I get these drives (or at least the CF) to be visible/mountable and boot correctly from them?

Понравилась статья? Поделить с друзьями:

Читайте также:

  • Acm exe ошибка приложения 0xc0000906
  • Acm driver error
  • Aclocal error configure ac is required ubuntu
  • Acl check error
  • Ach 1000 1 ц ошибка l

  • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии