Hi, why am I seeing this message all of a sudden. I power on, see the AEON screen and then see this message on a white background.
Just before this happened, I was in uboot. I was trying to remember how to start the system without startup-sequence.
I was using uboot which was a little glitch due to the new keyboard I am using. The POLL error messages showing and a glitch menu. But before it was still usable.
I navigated to the menu option with "Boot" in the name, I think it was the second to last entry. Pressed enter. I got this message and it just hung. So, I reset the machine, now I get this message all the time. I powered off for 10 minutes and from cold it still shows itself.
Neither of these have a solution. It just seems to have randomly happened and randomly stopped. Going from NGFS to SFS2 didn't really help. Will consider using a brand new SATA SSD next. As much as a doubt that it is due to badly connected SATA cables, my doubt becomes less, but that confuses me, because those cables literally do not move.
Perhaps I will try a combination of a new SARA drive and some "gold plated" (if such things exist) SATA cables, hot glued all-to-hell into the ports.
Edited by rjd324 on 2022/12/22 13:11:05 Edited by rjd324 on 2022/12/23 13:40:54 Edited by rjd324 on 2022/12/23 13:43:18
If liberty means anything at all, it means the right to tell people what they do not want to hear. George Orwell.
Local Bus Controller Registers
BR0xE0001001 OR0xFFF00010
BR0xE1001001 OR0xFFF00010
BR0x00000000 OR0x00000000
BR0x00000000 OR0x00000000
BR0x00000000 OR0x00000000
BR0x00000000 OR0x00000000
BR0x00000000 OR0x00000000
BR0x00000000 OR0x00000000
LBC0x40000000 LCR0x80010004
L2: 512 KiB enabled
Corenet Platform Cache: 2 MiB enabled
SERDES: bank 2 disabled
MMC: FSL_SDHC: 0
Board Revision dead
MAC: 00:04:A3:6B:43:E1
MAC: 00:1E:C0:F8:34:66
EEPROM: NXID v0
PCIe1: Root Complex, x4 gen2, regs @ 0xfe200000
01:00.0 - 1002:67ff - Display controller
01:00.1 - 1002:aae0 - Multimedia device
PCIe1: Bus 00 - 01
PCIe2: Root Complex, x4 gen2, regs @ 0xfe201000
03:00.0 - 111d:8092 - Bridge device
04:01.0 - 111d:8092 - Bridge device
05:00.0 - 12d8:e111 - Bridge device
04:02.0 - 111d:8092 - Bridge device
04:03.0 - 111d:8092 - Bridge device
08:00.0 - 1102:0012 - Multimedia device
04:08.0 - 111d:8092 - Bridge device
04:10.0 - 111d:8092 - Bridge device
PCIe2: Bus 02 - 0a
PCIe3: disabled
PCIe4: disabled
Looking for VGA
PINS: 0xfc000808
videoboot: Booting PCI video card bus 1, function 0, device 0
Begin BIOS POST
End BIOS POST
Setting VESA Mode
Found required VESA mode
About to set mode 279
About to get mode
Got mode 49431 (0xc117)
OK
XSize = 1024 YSize = 768 Base =0xe0000000
mmio_base = 0x80000000
bgx = 0xad55ad55 fgx = 0x0
In: serial
Out: serial
Err: serial
ID: NXID v0
SN: 116370027
UID: 4429431001910050d4cea080a0800000
Errata: ÿÿÿÿÿ%Dÿ
Build date: 2016/02/02 10:25:44
CRC: c924fbb7
SCSI: scanning bus for devices...
Found 0 device(s).
Net: Initializing Fman
MMC read: dev # 0, block # 56985, count 128 ...
Fman1: Uploading microcode version 106.1.0
Tuning PHY @ 3
Tuning PHY @ 7
FM1@DTSEC4 [PRIME], FM1@DTSEC5
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
USB1: USB EHCI 1.00
scanning bus 1 for devices... 2 USB Device(s) found
SATA0 (1.5 Gbps)
CE at device
SATA1 (3 Gbps)
scanning bus for devices...
No medium present
Device 0: (0:0) Vendor: Optiarc Prod.: DVD RW AD-7260S Rev: 1.03
Type: Removable CD ROM
Capacity: not available
Found 1 device(s).
Couldn't find a boot loader. Halting.
If liberty means anything at all, it means the right to tell people what they do not want to hear. George Orwell.
Okay, now it seems to be okay. I plugged in the X1000 keyboard. That was all really weird. Thanks for the thread link. For some reason I did not provide a reason for why that "HALT" message appeared.
EDIT: I think I performed a full reinstall, actually. I should have documented that in the thread which I normally do. I think I went with SFS2 instead of NGFS.
How can I boot with no startup sequence?
If liberty means anything at all, it means the right to tell people what they do not want to hear. George Orwell.
Keep CTRL key pressed while booting. It will get you to the cli.
Pressing both mouse buttons while booting will get you to the early boot menu. But the option "boot without startup-sequence" will not work if you have a Radeon RX because it performs a soft reset.
Yes, it does, but it’s extremely hard, you need to press the mouse button just after USB is initialized, after kickstart modules are loaded, if you have a scroll lock key, you can press that insted, press lots of times. don't press and hold.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
@LiveForIt Maybe I was unclear so let me rephrase:
Holding RMB+LMB does work if you want to display the early startup menu like on the classic amigas. But if you select the option "Boot without startup-sequence", this will perform a soft reset before booting into the CLI. This will NOT work for RadeonRX owners and will result in a black screen. But please correct me if I am wrong.
Holding CTRL while booting will take you directly to the CLI.
Holding RMB+LMB does work if you want to display the early startup menu like on the classic amigas. But if you select the option "Boot without startup-sequence", this will perform a soft reset before booting into the CLI. This will NOT work for RadeonRX owners and will result in a black screen. But please correct me if I am wrong.
Your are right, that exactly what happens. Holding 2 buttons of mouse works well, and detect fine (you just can hold it right once power up machine, and they will reacts fine while kickstarts to be loaded), but then does not matter what you choose, you will back to soft-boot which do not work and so black screen are there.
But Holding CTRL while booting will take you directly to the CLI works still.
There were discussion about in the os4beta just recently when i brought this topic up, and in short, Hans can't make soft-reset works. Even if it possible, he tried best he can and can't make it works. So a workaround were suggested to change boot-menu boot menu module instead, so to not perform soft-reboot when we want to go further with boot-with-no-ss , etc. But there wasn't anyone willing to implement it and everything ends up with no final result.
Sorry for dredging up an old topic, but is there a way to remap that key? My kvm seems to want to have that key active when I boot up my x5000 so u have to unplug the USB for it before booting.