Hello all, this is my first post and I cannot see a way to attach files so I will just quote things.
I have an X1000 with an RV730 and a single mechanical SATA drive (not SSD).
The first partition is a small FFS2 partition containing the "amigaboot.of". The second partition is approx.1 GB used for the Workbench and a second partition of larger size just as a general storage partition.
I am using Amiga OS 4 FE update 2. When I run "Updater" I can see that everything is "Installed" apart from:
Kickstart/ diskcache.library.kmod which I have as 3.30 vs Remote of 3.31.
The graphics driver is
8.Workbench:Kickstart> version file RadeonHD.chip
RadeonHD.chip 3.7
8.Workbench:Kickstart> version file RadeonHD.chip.debug
RadeonHD.chip 0.32
8.Workbench:Kickstart> version file RadeonRX.chip
RadeonRX.chip 2.8
8.Workbench:Kickstart> version RadeonRX.chip.debug
RadeonRX.chip 2.8
What happens is that if I leave my X1000 for a few days and come to turn it on (cold boot) then I seem to get a hang in what I would guess is "Phase 3" of the boot process - so this is where you see the black background and the Amiga OS 4 FE screen where you would hear the default Amiga 1000 startup noise immediately before booting into the desktop.
I have left it for > 20 minutes and still nothing happens.
So, I then press the reset switch and it boots. I can then also power it off, leave it for a while on the same day and then cold boot it again and it will work.
I have checked the serial debugger and there is no textual difference. Well, apart from one thing which I doubt is a serious issue. Here is the beginning of a successful cold boot: Quote:
[HELO][DRAM]SDRAM: ECC off, Non-ECC DIMM used on channel 0. SDRAM: ECC off, Non-ECC DIMM used on channel 1. [RELO][L1CF][GOLO][GOT ][ZBSS][INIT][MAIN][KMEM][EXCP][CONS][CIOK][AREN][PCIH][P CIB][PCIS][DEVI]
Here is the beginning of the unsuccessful cold boot: Quote:
ÿ[HELO][DRAM]SDRAM: ECC off, Non-ECC DIMM used on channel 0. SDRAM: ECC off, Non-ECC DIMM used on channel 1. [RELO][L1CF][GOLO][GOT ][ZBSS][INIT][MAIN][KMEM][EXCP][CONS][CIOK][AREN][PCIH][P CIB][PCIS][DEVI]
You can see the beginning "ÿ" character.
So, I assume that is nothing. So, where does it hang?
Quote:
[mediaboot] Diskboot is present. Skip mounting static devices.
It will hang at that line. Normally, on a successful boot the serial debug would go on to:
Quote:
No CMI8738 found! CS4281 DRIVERINIT No card present. No cards found! No SOLO_ONE found! No SB128 found! No FM801 found! No Envy24 found!
I am not 100% confident in this mechanical drive because it came with the X1000 that I bought not long ago. It occassionally makes a loudish seeking noise too that doesn't remind me of the times I used to use mechanical drives long ago.
I would guess that it is possibly the hard drive or a SATA cable?
I also desoldered and completely replaced the battery on this motherboard since it came with a snapped contact. Of course, before soldering on the new one I was getting all sorts of issues as is well known with our X1000s with a bad battery.
What I will do now is just dump the log of a full successful run so that there may be interesting information there.
Quote:
[HELO][DRAM]SDRAM: ECC off, Non-ECC DIMM used on channel 0. SDRAM: ECC off, Non-ECC DIMM used on channel 1. [RELO][L1CF][GOLO][GOT ][ZBSS][INIT][MAIN][KMEM][EXCP][CONS][CIOK][AREN][PCIH][P CIB][PCIS][DEVI]
CFE version PAS-2.0.30 for NEMO (64bit,MP,BE,PPC) Build Date: Fri Jun 8 16:04:49 CEST 2012 (hfrieden@jumpgate) Copyright (C) 2000,2001,2002,2003,2004,2005 Broadcom Corporation. Portions Copyright (C) 2005-2008 PA Semi, Inc. Portions Copyright (C) 2010 Hyperion Entertainment CVBA
Initializing Arena. Initializing PCI. [] PCI bus 0 slot 16/2: PCIe: port 2 could not be activated PCI bus 0 slot 17/1: PCIe: port 5 could not be activated PCI bus 0 slot 17/2: PCIe: port 6 could not be activated PCI bus 0 slot 17/3: PCIe: port 7 could not be activated SB600 revision A21 in Intel P4 mode PCI bus 1 slot 0/0: ATI Technologies product 0x9498 (VGA display) PCI bus 1 slot 0/1: ATI Technologies product 0xaa38 (multimedia subclass 0x03) PCI bus 5 slot 18/0: ATI Technologies product 0x4380 (IDE mass storage, interfac e 0x8f) PCI bus 5 slot 19/0: ATI Technologies product 0x4387 (USB serial bus, interface 0x10) PCI bus 5 slot 19/1: ATI Technologies product 0x4388 (USB serial bus, interface 0x10) PCI bus 5 slot 19/2: ATI Technologies product 0x4389 (USB serial bus, interface 0x10) PCI bus 5 slot 19/3: ATI Technologies product 0x438a (USB serial bus, interface 0x10) PCI bus 5 slot 19/4: ATI Technologies product 0x438b (USB serial bus, interface 0x10) PCI bus 5 slot 19/5: ATI Technologies product 0x4386 (USB serial bus, interface 0x20) PCI bus 5 slot 20/0: ATI Technologies product 0x4385 (SMBus serial bus, rev 0x14 ) PCI bus 5 slot 20/1: ATI Technologies product 0x438c (IDE mass storage, interfac e 0x83) PCI bus 5 slot 20/2: ATI Technologies product 0x4383 (multimedia subclass 0x03) PCI bus 5 slot 20/3: ATI Technologies product 0x438d (ISA bridge) PCI bus 5 slot 20/4: ATI Technologies product 0x4384 (PCI bridge) PCI bus 6 slot 6/0: Realtek Semiconductor 8139 10/100 Ethernet (ethernet network , rev 0x10) Initializing Devices. GPIOLV10 Jumper: Not fitted (default VGA console) GPIOLV11 Jumper: Not fitted (default ?) PHY: mb, addr 0x00, vendor 03f1 device 15 (1) GFX: PCIe Slot GFX: Disable SB600 legacy decode VGA (1/0/0): ISA memory space mapped to f8000000000 Initializing VGA. Found 800x600x32 mode: 0x0103 (259) Current VBE mode is now: 0x0103 (259) Mode Attribs: 00BB [Graphics] [LinearFrameBuffer] Resolution: 800 x 600 BitsPerPixel: 8 BytesPerScan: 0x0340 PhysBasePtr: 0x90000000 Enabling ATI frame buffer byte-swap GFX: PCIe Slot GFX: Enable SB600 legacy decode VGA initialization successful. SATA unit 0: Disk, "ST2000DM001-9YN164", Capacity:1863GB (lba48) ATAPI unit 1: Optical Drive, "TSSTcorp CDDVDW SH-224BB" PCIIDE: 2 controllers found Initializing USB. PCI bus 5 slot 19/5: EHCI USB controller found at A0209800 USB bus 0 device 1: vendor 0000 product 0000 class 09: USB Hub PCI bus 5 slot 19/0: OHCI USB controller found at A0208000 USB bus 1 device 1: vendor 0000 product 0000 class 09: USB Hub PCI bus 5 slot 19/1: OHCI USB controller found at A0207000 USB bus 2 device 1: vendor 0000 product 0000 class 09: USB Hub PCI bus 5 slot 19/2: OHCI USB controller found at A0206000 USB bus 3 device 1: vendor 0000 product 0000 class 09: USB Hub PCI bus 5 slot 19/3: OHCI USB controller found at A0204000 USB bus 4 device 1: vendor 0000 product 0000 class 09: USB Hub PCI bus 5 slot 19/4: OHCI USB controller found at A0205000 USB bus 5 device 1: vendor 0000 product 0000 class 09: USB Hub CPU type 0x900102: 500MHz Total memory: 0x100000000 bytes (4096MB)
Total memory used by CFE: 0x7FD1DF60 - 0x80000000 (3023008) Initialized Data: 0x7FDD8420 - 0x7FDF8B00 (132832) BSS Area: 0x7FDF8B00 - 0x7FDFF000 (25856) Local Heap: 0x7FDFF000 - 0x7FFFF000 (2097152) Stack Area: 0x7FFFF000 - 0x80000000 (4096) Text (code) segment: 0x7FD1DF60 - 0x7FDCBE60 (712448) Relocation Factor: I:7FE1DF60 - D:7FE1DF60 [ENVI] [OFW ][UI ]port 0:1/1 released (low speed) USB: New device connected to bus 1 hub 1 port 1 (low speed) USB bus 1 device 2: vendor 04F2 product 0116 class 03: Human-Interface Device USBHID: Keyboard Configured. Requested state A4 (1800MHz) Loader:elf Filesys:amigafs Dev:ide0.0 File:amigaboot.of Options:(null) Loading: 0x0000000000200000/61536 Entry at 0x0000000000200000 Starting program at 0x0000000000200000 [RUN!] AmigaOS 4.x OpenFirmware Bootloader V53.21
Please choose a configuration to boot (Default choice is green): 1: AmigaOS_4.1_Final_Edition (Volume DH0)
[RETURN] Boot default [SPACE] Stop Countdown Move default [UP] or [DOWN] with arrows [1] Boot appropriate config (0 sec. until autoboot)>
I would suggest to check/change the 2032 battery. Sounds like it might be on the way out...
Simon
Comments made in any post are personal opinion, and are in no-way representative of any commercial entity unless specifically stated as such. ---- http://codebench.co.uk
welcome aboard and Merry Christmas/ Happy Holidays !
Have you confirmed with a volt meter that the new battery connection and battery are ok as I had similar issues back in 2018 which were resolved by replacing the CR2032 with a BR2032 coin cel battery (supposedly the BR keeps its 3V longer than the BR)
So, as I said, I completely resoldered a new coin cell holder. I checked voltage at the time of the existing battery and it was okay IIRC.
But, despite being a new coin cell holder, I did not go the full distance and just pop in a brand new battery.
Let me get a brand new battery anyway and see what happens since as you and I have already alluded to: X1000s do NOT like bad batteries!
So far we have the possibility of the radeon driver as also cited in the bug report which is not a 1-1 mapping of my issue but does have some similarities or an on-the-way-out battery.
It's a shame such an issue is not deterministically reproducible. Well, without waiting for what I guess is 24 hours and even then it is not 100% definite.
Thanks so far and I will report back.
If liberty means anything at all, it means the right to tell people what they do not want to hear. George Orwell.
I have the same thing on my X1000 with a Radeon HD 6670.
In my experience, if it is stuck on the black splash screen for more than 30 seconds, it won't get any further, and you might as well reset it with the button on the case. No need to wait for hours.
Sometimes it gets stuck up to three or four times before a boot finally succeeds.
I've tried inserting debug prints to serial in my Startup-Sequence, and they seem to indicate that it gets stuck in (or around) the IPrefs command.
But so far no-one in the (OS4) beta or developer team seem to have succeeded in getting any further clues to why it happens, even when running with higher debug levels.
It seems to be specific for the X1000 (not happening on my X5000/40, Sam460ex or Sam440ep).
As support tech I learned that one problem can have multiple causes. I do not think your problem necessarily has anything to do with his problem.
Ranging from hardware problems to software problems like bad PSU, connection issue, bad backup battery, overheating, and even bad soldering point, interrupt issue some hardware you plugged inn, a broken hard drive.
Typical lockups in software comes from stales states, like double unlocking, async issues, waiting for things that never happens, incompatible drivers. Memory corruption can behave different from one system to the next, depending on free used / memory layout.
IPrefs is not something anyone should play with, its responsible loading in prefs files, prefs files not backwards compatible. AEON is trying to replace the prefs files, can result incompatible prefs files and make Iprefs crash. IFF / preference files is really bad as section prefs are just structs, if the struct expands, is nothing in the IFF format that says that section needs a size, and what it contains is not in the IFF format, that is hard compiled into the loader. You can’t move data around in the struct and think it will work. if take 680x0 prefs program is compiled for powerpc it goes from being 16bit aligned struct to 32bit aligned struct, unless you specify it’s not. So, everything becomes misaligned and size no longer matches.
AK Datatypes can also make different parts of the OS freeze up, as tries to load in different images during startup.
What’s different between X1000 and X5000 is drivers, as it does contained the same hardware, changes in software can cause bug that where never found before, start showing up.
steering at black screen won’t help, you need capture rs232 debug output, if that does not help you need a special version of IPrefs with more debugging maybe, locate where most often it stops.
also, because you are beta testing more than one thing at once can make it really hard to track down, not know what changed, you might even have multiple causes of locks. Good luck!
As user, I only install what I must and hobby developer I only wont bug to related some thing I did wrong.
Edited by LiveForIt on 2021/12/26 11:26:49
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
On AmigaONE-X1000 the kickstart modules are not loaded from “SYS:Kickstart”
they are loaded from hidden BDH0:kickstart you can mount it using the mounter tool:
“Sys:System/Mounter”
It’s the “RadeonHD.chip» should be in use, the RadeonRX.chip is not relevant to you as you don’t have that graphic card.
the drivers you don’t need can be commented out in the kickstart layout. Make sure you have a bootable cd (make sure you can boot without a HD...), just in case you mess it up.. take a backup before you start editing.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
I am an X1000 beta-tester since the very beginning and I must say that I do not know why you are saying that kickstart is not loaded from SYS:Kickstart. I have more than 10 boot able partitions (ranging from the first contact edition to 4.1 final update 2) and I can assure you that each of them loads kickstart from their respective SYS:
(ps: as a beta-tester I do not have that BDH0 partition you are speaking about)
I’m think I’m remembering wrong. There is no kickstart folder in BDH0: but key here is CFE only support FFS so, the amigaboot.of has be on the partition with FFS, but workbench can be on SFS\02 once the amigaboot.of is loaded.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
1) Unfortunately once booting reaches the point where you are nothing (except programs that were ecplicitely to do so) is sent to serial anymore (as in, the boot process is done, workbench takes over) 2) From that point on the WB boot takes over, which means, *if* something stalls, it's probably software being loaded during WB boot, so everything in startup-sequence, user-startup and later WBStartup.
Could you share these three with us?
Everything in WBStartup you could temporarily turn off for testing.
I had recurring stalls because some of scripts (accessing the interwebs locked up because the network driver wasn't ready respectively there was no internet access possible), but you probably don't have anything accessing the web that early(?)
;; RJD mount g8 straight away (well, there is an in-built delay of 10SECONDS)
;;; Not using at the moment because downgraded to 1.74 (but that STILL has the COPY problem on the X1000 for
some reason. Tested it on the vampire with smbmounter 1.5 and smbfs 1.74 and it works fine! what the hell is
going on!?
;;;RUN >NIL: Other:Dev/smb_startit/smb_startit rjd g8 //192.168.1.83/gen8
;; END RJD mount g8 straight away
;; SVN
assign subversion: c:
;; END SVN
3. wbstartup (not sure if there is a text file for this, so I will just write these down manually). "Show Progress Window" is also enabled
LimpidClock is an obvious candidate to not have startup. I have not tried any further testing yet. I will do in the near future though. I may also want to try the serial debugging in the startup/user-startup to see if I get something similar to you regarding IPrefs?
If liberty means anything at all, it means the right to tell people what they do not want to hear. George Orwell.
Ok, just thought you might have some programs in network.startup.
It's prett sure a program that hags during boot. Best way is to get the programs out of the way first and add them one after the other to see which is the bad boy
*Had*. I've since then fixed all of them but the "machine exception" hard locks coming from the gfx board (where no one can do anything about, at least that what Hans told me (he also told me that these "machine exceptions" only happen on a warm reboot, but that is not true, i get them randomly on cold boots, cold reboots and warm reboots.
That's why i know that, if it isn't a "machine exception" it *must* be a program stalling or crashing (because that's what i was able to rule out over the past months)