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

then I reinsert FFS flash, not seen in show devices, but visible on show usb

kas1e wrote:@Sailor
See, you expect usbdisk2 , but CFE handle only usbdisk0 and usbdisk1. Usbdisk2 and usbdisk3 probably need to implement. I never seen in CFE in devices usbdisk2 or usbdisk3. So while we add unit 2 and unit3 , then simple rejected by CFE (at least, that how it was with SATA)

Sure you use CORRECT version of CFE as noted in readme and in first post in this topic ? The one which "2012_june_08". That memory patches, if you use different version all addresses will be wrong.

Also are you copy to FFS stick correct system files from which you actually can boot ? If it pure x1000 iso copy, you may have no luck because of HD/RX issues, etc. You should copy your working system partition from which you 100% can boot till working workbench if you ever have one in last years.

Wtf ! :) you have 15 boot partitions ?:) looks like memory corruption ?

Your issues with "no files" on FFS can be simple maybe you just after copy do reboot too fast, and USB (especially old ones) need some seconds to cope with copy.

While load command suck (at least ith combination of amigafs) , but it was noted before : you need to specify in -max a size of the binary 1:1 , then it will work. So -max should be called -size, like that:

I mean, you need one time to note every quirks of CFE to some text file and used to it :) It's all the same bugs and quirks which you need to remember one time and used to them :)

Because for now, its more looks like you in total mess even without patches and everything working/not-working and you don't know why and when. At least that sounds and looks like that. Adding on top of this mess a hacking-firmware patches is call to more mess, for sure :)

CFE> load -raw -fs=amigafs -addr=0x600000 usbdisk0:Kickstart.zip
Loader:raw Filesys:amigafs Dev:usbdisk0 File:Kickstart.zip Options:(null)
Loading:  0 bytes read
Entry at 0x0000000000600000
*** command status = 0
CFE> ramdisk -raw -fs=amigafs -addr=0x600000 usbdisk0:Kickstart.zip
Invalid switch: -raw
*** command status = -8
CFE> ramdisk -fs=amigafs -addr=0x600000 usbdisk0:Kickstart.zip
Loader:raw Filesys:amigafs Dev:ide0.1,dh12 File:ramdisk Options:usbdisk0:Kickstart.zip
Loading: ..................................... 37037056 bytes read
Entry at 0x0000000024000000
*** command status = 0

[...]
In any case bboot crashed again. Likely because zip corrupted in memory. But I would have expected an error like no zip signature found or bad CRC. I wonder about how robust the zip unpacker is as it shouldn't just crash like that. Assuming that was what it was doing. Needs a debug mode specifying what it is doing next. I did use the X1000 alpha version posted.

So, seeing the mess you have in system, we of course can't rely on your tests :( It can be anything, if you says so easy that you may lost files somewhere else , those are not very good tests then :)

Booting amigaboot.of from an ISO imaged USB stick does work. It was the filesystem

This must be what was fixed up in that version where they added ISO9660 support to USB.

My other USB stick has FFS DOS7 and is a copy of my recovery volume. I couldn't get this to load. On my last test it loaded all the modules off USB then just hung, with no sign of Exec on serial. Left it for a minute then reset. I'll do some more tests on that.

No BBoot likely could not find it because zip was loaded at wrong address.

According to the above output ramdisk command may load at the default 0x24000000 address not at the -addr you specified. According to previous posts load command is also broken in other ways that it honors -addr but without also specifing -max with the exact size of the zip to the byte it either loads 0 bytes or tries to load too many and crashes. The commands @kas1e gave before (adjusting the -max number to be your zip size) should work but you did something else.

Also BBoot does print debug and errors but serial on X1000 is not yet supported so these are printed in the CFE console (provided you used the 0.9-alpha version from earlier post) so look for it there but you did not post that part of the output so I don't know what it said. Older BBoot versions won't work or could tell you that on X1000 as there's no support for that machine in those versions. (Older BBoot version could still tell you machine is not supported if you 'setenv bboot "Of V5 Ab"' that disables serial output but all it would tell you is unknown machine.)

You mean with my patch booting work now for you ? (yes/no please)

Did it work till full workbench load, or hang after modules load ? (please answer short).

If you mean amigaboot, then try this version of amigaboot where they add it.

And don't do load/go , do "boot". That for clear test case.

I do not understand still sorry : its all chaotic unstructured report with lots of phrases on differnt matters :(( Can you make it all VERY short by simple points ?

All i undertand now, is that you have 2 usb sticks: one ISO and one FFS7. ISO one, is booting fine with my patch you say, but then, few phrases later, you show me log showing it didn't boot, what is right answer then ? Then you have second FFS based one, which boots, load kickstart files, but then nothing happens. While i understand what you mean about FFS one, i didn't get about ISO is it boot or not , what of your answers is correct one ?

I am 99% now sure you mess with FFS stick, just really sure. You copy wrong data, or something of that sort. Or you forget something, and will find it after a days or weeks :) Before you have crash you say not just hang doing nothing, now crash somehow gone. Before it wasn't booting from ISO, few big posts about, and then it can now, but then again can't with log that it can't.

TearsOfMe wrote:Could it be that the "bootargs" env isn't working properly with the VGA patch?

When I enter the line "setenv bootargs "root=/dev/sdb1" the saved environment is still used.
I must use setenv -p .. and a reset to change the bootargs.

Can anyone confirm this?