X1000 CFE Patches: Testers Welcome (Fear not: real-time, no reflashing) v.02 NEW!

@kas1e

So I successfully managed to load amigaboot.of and Kickstart off USB but the Workbench wouldn't boot. The USB stick was plugged into my keyboard hub so is at USB1.1 speed or full speed as its called.

The end result was OS4 logo stuck on screen. I check the startup menu and all but the USB drive was listed. So the first problem is the USB drive not showing up. That's pretty much a showstopper regardless. Another problem is that nothing is booting. I can keep rebooting to see DOS boot drives so system is technically working but when letting it boot it cannot boot at all. Somehow, even though the volumes are there, it is not even booting from the first boot drive. There's not much clue as to why.

The following is last seen on serial.

@Hypex
Quote:

Now, see, after a while you have LOGO on screen (before it was halt with nothing) :)) Some days more and you will be able to boot :)

My wild guess is that you simple overmess everything with your 15 boot partitions, boot priorities and so on.

Just do simple test : disconnect everything from sata port (not from mother board itself, just disconnect all devices for test). And then simple power on, load usb patch, reinstert usb-stick (ffs one, with boot priority flag set to 0) , and then amigaboot from it. But you should be sure :

1). all drivers disconnected
2). stick correctly done like this : https://g-a-p.me/inside/x5kbootstick.html
3). you not forget to set boot flag on it in mediatoolbox.


@TSK
With patch just more devices found , and if any of them have boot flag set, amigaboot will find them (that not about patch, but about amigaboot scanning all available devices in devtree and add them to the list). So patch just enable all devices you have connected.

@TearsOfMe
Quote:

Now sure i understand, but as Sailor said it works that way : when -p it then saved permanently , when without, just used for current session. Or issue is that when you use it without -p even for localy session doing "printenv" it didn't changes ?

@Sailor
How it going ? Weren't you able to test something else, like new cmds with pager / editenv , sfs2, etc ?

@kas1e

So i have "root=/dev/sdb1" as permanent bootarg for Linux root.

When i now change the bootarg with setenv (without -p) and
look with printenv bootargs shows the updated content. All ok.

But when i boot Linux root is the permanent bootarg env and not the
updated bootarg.

Example. The A-EON Linux CD sets the bootarg for booting from cd. This works not, while the permanent env is used.

Dont now if this is normal. I have tried Linux Years ago.

I try now if i unset the env and change then for current session. Maybe the env should not set permanent?

P.S.: Tested and it make no difference. Set the bootarg env and boot. Linux command line is then empty.

@TearsOFMe
Can you check this all without patches at all ? Or you mean there some general CFE issue ?

Okay without vga or any other patch bootargs works as it should.

When using only one patch at a time.
With sata or usb or cmds it works not as it should.

@kas1eQuote:

SFS2 works fine I booted from USB / SFS2 with no problems.
editenv is nice feature, but if there are spaces in env, is needed to close between ´´ manually.
Thanks, it is very nice work you did on old X1000!

Now I am not testing neither Amiga, neither Mirari, neither linux kernels. We are moved to garage, because we are repairing floors in the house. So all my computers are packed in basement, and stays there one or two weeks more

@kas1e

Quote:

It lists partitions without boot flags definitely.

Either somebody must update amigaboot.of to not list everything in the device tree but check the boot flag by itself. Or your code should not add any partitions to the device tree without the boot flag.

Why would you need any partitions to be listed which you can't boot. You don't have any Amiga DOS commands in CFE so you can't access any files anyway. Any reason to do anything in CFE is to boot the machine.

@TSK
Quote:

There can be bugs on my side with patches of course, but there we need to be double sure that this is the case. What are the names in the amigaboot list of those partitions which shouldn't be bootable ? It can't be that you have some test partitions (old ones and forgotten) ? Can you check to be double sure in media toolbox ? What the names of those partitions in the amigaboot list which shouldn't be there as you think ?

Quote:

No one will update amigaboot.of , and even if anyone will, forget about "soon to be released", so that out of question.

My patchs code didn't add any paritions at all, my code didn't know about partitions. All my code do in regards to allow booting, is add missing before devices to the CFE three, nothing else. So if you have in your amigaboot.of list some paritions which you think should't be there, then:

1). double sure you didn't have connected any HDD/SSD/CD/USB which may have those boot partitions and about which you simple forget.

2). check the name of partition in amigaboot list and device name, and check (again, yeah) in mediatoolbox what bootable flag is have.

Quote:

It should't. Either you have bootable flag on them and forget about (like, some old HDD connected and you just forgot that it have it), or something of that sort. Amigaboot actually itself check if your device have boot flag or not as i aware, so chances that you need to recheck bootable flag and open up a x1000 case to see what is connected to sata ports are high.

Quote:

Are you for real ? YOU CAN access any files via CFE. You can list them, you can even load them to memory and read them, you can do a lot of things from CFE, because CFE is small OS. You just didn't know about seems so.

Quote:

Probably for you, others ones want to work with it in all the ways before hi-level kind of OS starts.

So, plz check if you have connected another HDDs to other ports on your x1000 which you simple forget, and as they wasn't ever detected by CFE before patch , amigaboot.of didn't see them, but see now. Check the name of those partitions and devices name , and check via mediatool box about.