Update2 - Boot Issues...

This forum is for all AmigaOne 500, Sam440 and Sam460 specific issues.
Belxjander
Posts: 311
Joined: Mon May 14, 2012 10:26 pm
Location: 日本千葉県松戸市 / Matsudo City, Chiba, Japan
Contact:

Re: Update2 - Boot Issues...

Post by Belxjander »

@nbache:

The "logical test" you proposed is irrelevant,

TEST: Two Kicklayout Entries, with "Update2" specific kmods in Sys:Kickstart/u2/ and configured appropriately,

Implementation:
Attempt to boot "AmigaOS4.1FE+U1" and "AmigaOS4.1FE+U2" entries independently *without* Startup-Sequence script.

I used the Kicklayout from the 4.1FE CD and made two entries...
"AmigaOS4.1FE+U1" is the Sys:Kickstart/ tree as applied from the CD with Update1 installed,
"AmigaOS4.1FE+U2" is replacing specifically the dos/elf/newlib kmod triplet with "Sys:Kickstart/u2/" path prefixing as the exclusive difference.

Testing is attempting to boot each KickLayout entry as presented by the Boot menu listing the two labels configured in the KickLayout.

RESULTS:
AmigaOS4.1FE+U1 KickLayout entrie worked and provided a Boot Shell which enabled Execution of the renamed Startup-Sequence and a usable system.
= SUCCESSFUL Boot Shell provision and a working system

AmigaOS4.1FE+U2 (using u2/dos.library.kmod + u2/elf.library.kmod + u2/newlib.library.kmod [=sam440ep])
= FAILURE of Boot Shell provision, even given a full 10 minutes...

Therefore, *regardless* of the system isntalled onto the HDD ... if the Kickstart itself CAN NOT provision a boot shell at all,
something is seriously broken BEFORE the system on disk is even looked at.

so the argument of requiring a fresh install at this point is irrelevant.

please explain how I am suppossed to obtain a "hotfix" where I can not actually boot the specific Kickstart module set for Update 2?

HARDWARE:
sam440ep-flex mainboard with PCI "Radeon 9250 Graphics Card", "Broadcom Wireless Network Controller", "USB3 XHCI Controller" cards installed,
2x SATA 1TB Samsung HDDs
(1st is AmigaOS RDSK prepared with multiple AmigaOS4.x and Linux partitions, 2nd is PTBL partitioned with a single 1TB NTFS partition)
USB Keyboard+Mouse by Wireless controller
USB BeagleBoneBlack (Arch Linux with "USB Device" options "disk", "serial", Network[EEM, ECM] enabled, "RNDIS" and "printer" disabled)


additionally...
AmiUpdate is specifically listing the same 3 specific updates repeatedly even AFTER installation of the updates in question.

The system itself has not displayed any major errors outside of what is expected for software development.
User avatar
nbache
Beta Tester
Beta Tester
Posts: 1620
Joined: Mon Dec 20, 2010 7:25 pm
Location: Copenhagen, Denmark
Contact:

Re: Update2 - Boot Issues...

Post by nbache »

Belxjander wrote: Mon Feb 08, 2021 9:56 am @nbache:

The "logical test" you proposed is irrelevant,
If you say so ...

Best regards,

Niels
User avatar
Hypex
Beta Tester
Beta Tester
Posts: 518
Joined: Mon Dec 20, 2010 2:23 pm
Location: Vic. Australia.

Re: Update2 - Boot Issues...

Post by Hypex »

Belxjander wrote: Mon Feb 08, 2021 9:56 am Implementation:
Attempt to boot "AmigaOS4.1FE+U1" and "AmigaOS4.1FE+U2" entries independently *without* Startup-Sequence script.

I used the Kicklayout from the 4.1FE CD and made two entries...
"AmigaOS4.1FE+U1" is the Sys:Kickstart/ tree as applied from the CD with Update1 installed,
"AmigaOS4.1FE+U2" is replacing specifically the dos/elf/newlib kmod triplet with "Sys:Kickstart/u2/" path prefixing as the exclusive difference.
That looks complicated. Did you ever fix this? I understand without AmigaBoot that menu needs setting up by hand.

One thing I didn't see mentioned, using AmiUpdate is all well and good, but it won't work on a fresh install. Unless you have installed your password this won't work. Did you reinstall your account settings? I would suggest to download the updates manually and then install from the archive which should include an installer.

Also, do you have interrupts enabled for your graphics? Your system is different. But I found my Workbench will freeze for some reason if I have interrupts enabled on Update 2.
Belxjander
Posts: 311
Joined: Mon May 14, 2012 10:26 pm
Location: 日本千葉県松戸市 / Matsudo City, Chiba, Japan
Contact:

Re: Update2 - Boot Issues...

Post by Belxjander »

Not that complicated...

Using a second HDD... I booted and re-installed clean-slate from the Installer CD...

I then duplicated the Boot Entry for the OS on the clean-slate.

I then applied AmiUpdate and updates on the clean-slate... which led me into the exact same error condition as my main drive.

I do NOT get any options about Interrupts or anything else unless you are talking about something in the sam440-flex U-boot firmware...

as *nothing* past the Kickstart will be loaded to run once the Kickstart bootstraps with Update2 materials applied...

so this is still an outstanding issue without resolution.

I'm normally using my main installation and the above install was only temporary...

also the reason why I stated that clean-slate installation was irrelevant to the problem ( renaming the startup-sequence and booting with exclusively only the Kickstart into a boot-shell **DOES NOT HAPPEN** due to where the problem is within the kickstart post-load image itself.

Honestly... Editing the KickLayout in a Text editor and making a second entry is not that difficult...

Begin with a label line and needs the launcher and then a whole set of modules to be listed.

I just had to deal with all that twice.

I did have AmigaOS 4.1 FE and +U1 as separate entries in the list...but changed that to the two updates...

I prefer to always have at least one means of rescue bootstrap setup. that is all there is to it.
Post Reply