!Internet,Bin updates casuing boot failure

Hi,

With updates to the !Internet.Bin files post 5th Feb 23 I am seeing my ARMX6 failing to boot properly and giving various errors like incorrect screen mode and Filename errors.

If I update the HardDisc image up to a beta one of the 5th Feb 23 then all is well but if I update with the next available one I have , 25th Feb 23, then I get the issues.

I have done a replace and reboot to track things down and get the following:

ARP Dated 25th Feb gives “Unknown Library Chunk” errors
IFConfig and SysCtrl give no error but replacing the 5th Feb 23 ones with 25th Feb 23 ones results in the boot error.

I guess this may be due to the changes as part of the Internet stack bounty but thought it may stop others falling foul of issues when testing out the beta hard disc updates.

I am happy if someone wants to suggest some means of testing and finding any more information that may help track down the issue.

ARP Dated 25th Feb gives “Unknown Library Chunk” errors

Ah, that’ll probably be a knock-on from the reshuffling of the C stubs

Try updating the SharedCLibrary RMEnsure in System.!Run to 6.19 (assuming your disc image is new enough to contain that version)

I have seen that on the Titanium with a ROM that predated the new internet tools. The solution is to use an up to date ROM. In general the ROM and disc image are a pair, too old a ROM may not support new features in the disc image.

It made a bit of a nonsense of the softload arrangement of an old safe ROM flashed but the current beta softloaded. The beta softloaded ROM would start up but if the softload was declined the older ROM fell into Boot errors.

HTH

Try updating the SharedCLibrary RMEnsure in System.!Run to 6.19

Good tip, OS5.28 now does fully boot with the new internet tools on the case. (After a ‘new’ WimpVisualFlags call in PreDesk.ThemeSetup had been commented out that is.)

Should not 6.19 be rmensured by default as that version is indeed required.

Should not 6.19 be rmensured by default as that version is indeed required.

Yes – I’m preparing that change now

Try updating the SharedCLibrary RMEnsure in System.!Run to 6.19

That does indeed fix the issue and I have even installed 9th March HardDisc beta as well so it looks like that fixes the issues with ARP/IfConfig and SysCtl.

In general the ROM and disc image are a pair

Normally I do that but on the ARMX6 I stick with the RComp supplied ROM which in this case is 5.29 (20-Nov-22).

Also the Wandaboard beta on here doesn’t have the usual softload set up.

Any way thanks to everyone for the help resolving this issue and even my Router/Powerline adaptors throwing in a curve ball and deciding not to work and supplying no network/gateway details whilst I was testing the suggested fix didn’t throw me too far off once I had done the usual three pin reset on them:-)

Should not 6.19 be rmensured by default as that version is indeed required.

That worked until today, 16May23. SharedCLibrary 6.20 has arrived.

Updating Dev !Boot but remaining with the previous Dev ROM, now gives an error on setting up networking, “Shared C Library is out of date”. A peek inside IfConfig, for example, shows it does indeed RMEnsure CLib 6.20, the version now in !System.

Double clicking on IfConfig shows the error.

Updating the RmEnsure in !System.!Run fixes this.

If the Dev ROM had been updated first this issue would not have been seen.

A bit later New ROOL tools? CLib.o.stubs?

A peek inside IfConfig, for example, shows it does indeed RMEnsure CLib 6.20, the version now in !System.
Double clicking on IfConfig shows the error.

I’m confused (well, more than usual): the string for RMEnsuring CLib 6.20 is in the IfConfig binary, but it shouldn’t be being used since IfConfig doesn’t appear to be written in C++. If I run !Reporter to confirm this

12:59:30.64 Run ADFS::Solid.$.!Boot.Resources.!Internet.bin.IfConfig
12:59:30.64 RMEnsure UtilityModule 3.70 RMEnsure CallASWI 0.02 RMLoad System:Modules.CallASWI
12:59:30.64 RMEnsure FPEmulator 4.03 RMLoad System:Modules.FPEmulator
12:59:30.64 RMEnsure SharedCLibrary 5.17 RMLoad System:Modules.CLib
12:59:30.64 RMEnsure SharedCLibrary 5.34
12:59:30.64 Exec

That’s what I expected, so I don’t think the error message you saw relates to those RMEnsures, I think it reflects that during unstable development more stub entries may be added which will be reported that way. Once frozen (either in a new DDE or new stable release) any new stub entries need a new chunk to avoid the splattering of unknown stub entries.

so I don’t think the error message you saw relates to those RMEnsures

That was just a too easy a conclusion to jump to!!

The CLib 6.20 RMEnsures are a recent addition

“RMEnsure a newer SharedCLib in stubs if they detect ctors/dtors”

I could conclude that IfConfig really does need CLib 6.20 in the present scheme of things, there are ctor’s and dtor’s in the source. If so there is no bug other than that only CLib 6.19 is RMEnsured.

OTOH I refer the reader to my first sentence above.