Hello, I was really happy to see that the Picasso IV is now supported! Unfortunately I seem to be having problems getting it to boot. I am getting the reset, but nothing after that.

I have tried all the reset levels except for 4. I have tried the init initresident, removing disableled and ramdebug. I have tried with and without kickstart image.

I have posted my current startup-sequence and debugramdump output right here.

Hardware: AT Amiga 4000T, CSPPC 180MHz/128MB, 16MB on motherboard. Picasso IV. Booting from HD on A4000T IDE, SFS 1.252.

Any help would be appreciated, I've been wanting to try this for a while now. Do I need to remove the RAM on the motherboard? I was unclear on that from the posts here.

Thanks!

Thanks for the very detailed, very precise bug report, and especially for the debug logs! I wish all of the bugreports to be like yours. I'll take a look on the logs and the problem, and test my PIV in an A4000 with MOS again. (No access to an A4000T for now, but it shouldn't cause much difference.)

As for the memory trouble, yes, could you please try to remove mainboard memory, and try again, and tell if it causes any difference?

Ok, I have had the time today to tear the thing apart and start from a bare board + Picasso IV. The result is that MorphOS boots, but no video

The crashing earlier was my fault. There is a Kickflash in the machine that wasn't disabled...it is disabled now, and the OS is booting. Strange because there is no ROM update loaded in the kickflash, but whatever.

I removed all hardware in the machine except for the CSPPC and Picasso IV, and I removed the memory from the motherboard. The serial output from that boot is right here.

After this, I tried placing the PIV in the top video slot. It is normally in the second slot to make room for the Prometheus. This had the same result. I began adding hardware back into the machine and retrying the boot: the RAM (16MB), Kickflash (disabled), X-Surf, and finally the Prometheus with Voodoo 3. The last addition caused this output and a hang. I rebooted into AmigaOS and removed the Voodoo3 driver from the monitors, and this message was no longer present. All boots except with the Voodoo3 driver present are the same as the first output (no video).

So, that's what I've got now. Any ideas?

*edit Forgot to mention, I changed the original startup sequence. I removed disableled and ramdebug, I'm using serial output for logging.

Thanks!

[ Edited by Failure on 2006/3/1 19:34 ]

Just two things:

1., Prometeus is not supported for now. There's some code in the system for it (that's what you see in debug log), but it's known not to work. There are a few requests already asking for the support, but we currently lack test hardware to solve the problem. But never say never.

2., Could you try booting from the CD? If you remove bootdevice argument from the startup command complettely, it should boot from the CD. This could help figuring out if it's some software setup, or hardware setup problem. Also, please remove the Prometheus while testing for now.

More hints will come, but i'm in a hurry now... And again, thanks for the serial logs. They're really helpful.

Ah, and one more thing: i'll get an A4000T tonight, to help further testing of MOSPUP. So, sometime soon i'll plug my PicassoIV into the thing, and i'll try to reproduce your problems. This should happen sometime on this weekend. Maybe we'll know more then.

1) Try to boot with the following debug options

HDebugFlags="Init Zorro PCI"
QDebugFlags="Init EmulMapping MMU"
EDebugFlags="Init InitResident PCI LoadSeg"

that should help analyzing the Prometheus

2) I suppose removing the Voodoo from the Prometheus shouldn't cause a boot crash, so
that's easier than removing the whole Prometheus.

3) If you only wanna analyze the Ambient/Picasso4 no
display problem use this

EDebugFlags="Init InitResident LoadSeg" DDebugFlags="LoadSeg"


4) If you get uncounted hits like in your first log something like MaxHits=1 should help. Then
the machine stops doing anything after 1 hit
happened and the ramdebug buffer isn't overwritten
with nonsense.

Thanks a lot for the continued assistance! Regarding the Voodoo 3...is it sufficient, do you think, to just remove the Voodoo 3 monitor driver when not attempting to troubleshoot the Prometheus? If not, I will pull the machine out and set it up where I have easier access to the internals so that I can add/remove the board for testing. Where I have it now it's a big pain to pull it out and operate it with the case open.

Quote:

The output from that attempt is here.

Quote:

The output for that is here. Note the Prometheus is still in the system but the Voodoo 3 driver is not present.

@Chain-Q: I need to either make a new CD without the Voodoo 3 driver on it, or relocate the machine as described above. I can't remember for sure but I believe I tried booting from CD when I had all the hardware removed from the machine. I will try again though to verify.

Thanks again, I am thinking about cranking the serial up to 19200 to deal with all this output

3)
Are you sure that you have the picasso4 executable
in mossys:devs/monitors ?
I can't see a LoadSeg with the picasso4 name there.

Oho! Good call. Yes, the driver is present, but I bet it's not executable. I mounted the CD image on the loopback device here (Linux) and checked the permissions, and the driver is not set executable in the CD image:

Code:

I will be able to check on the Amiga once I get home. If this is actually the problem does the CD image need to be fixed? Thanks!

Yeah, looks like an iso creation mistake

Ok, made some progress by making that driver executable, but it's not quite working yet. With this, I *do* see the MorphOS butterfly logo, which I was not before, but then the screen blanks and Ambient complains about the video device.

The first boot is with all the hardware still in the machine, including the Prometheus, but with disabled Voodoo3 driver. The serial log is right here.

After this I finally decided to get the machine where I could work on it easier. It is currently on a table with the case off, and the only hardware in the system is the Picasso IV and CSPPC. I also removed the RAM on the motherboard. Booting had the same result.

I made a fixed ISO image for myself to use, and tried to boot from that. This gave the butterfly logo, but again no video at the end. here is the output from that attempt.

What's next?

@Failure

although it probably hasn't much to do with this problem... did you try installing MUI4 beta (not the latest one released this month or the previous one, but the old one)

A friend of mine had a corrupted muimaster.library
but I guess this has nothing to do with your problem. anyway... MUI4 is beautiful

Quote:
True. It was my fault. Sorry everyone... The problem got fixed in my archive, where the official ISO builds from, so next MOS ISO version won't contain this error. And again, i appologize for the inconvenience.

> Are you sure that you have the picasso4 executable

Funny, I discovered that flaw last weekend myself .-) After making the driver executable MOS suddently displayed its logo. However there was no (or no usable?) Ambient screen on my TFT. The solution was to create a PicassoIVMonitor containing monitor-85khz. At that point the system was usable!

Quote:

I want to be sure I'm understanding you here. I added MONITOR=85KHZ to the icon, is this what you meant? Anyway, I didn't notice any change. It seems like it would not do anything since Ambient doesn't appear to see my card at all(?). You got me thinking though, so I tried booting with boot logo disabled. End result was no different (except no logo of course) but I posted the debug logs anyway here. Doesn't seem like anything is working for me

Were you using an A4000T as well?

Thanks for the input!

Quote:
Nope. The change I suggested is not(!) to the monitors icon. You have to create the file sys:Prefs/env-archive/CyberGraphX/PicassoIVMonitor. Simply copy one of the existing files there (Voodo, Sis, etc). Make sure sys:Prefs/Presets/Monitors/Monitor-85KHz does exist (its on the ISO from february).

Quote:
Which flags did you use to make this log?

Quote:
No, I have an A4000D but thats not important. If you can see the logo then I am very confident that all you need is the PicassoIVMonitors file.

Quote:

You're my hero. It worked! Now I need to figure out if I can get my X-surf working on it. Thanks very much.

Quote:

These flags, or actually the fourth set. I'll be switching to the top set unless someone wants me to do more Prommy testing

Thanks again, I'm looking forward to playing around with this over the weekend!

Quote:
Glad to hear that! Since I was in the same situation I knew only a small bit was missing. An that was the only thing I could find. However, at first I was conservative and used monitor-31Khz that was in a previous ISO. Then I got a barely usable 640x480 Ambient screen. Thus I decided to use what the over monitors used ;-)
Hopefully a future ISO will add monitorfiles for the 68k drivers as well (hint,hint!).

Quote:
I guess that it will be much easier to figure out ;-)

Quote:
Ah, the one that were suggested for the PIV debug earlier in this thread. BTW, you should add a final \n in your startup-sequence..

Quote:
I enjoy playing around with MOS myself. Its real fun.

BTW, what filesystem are you using for your MorphOS partition? Is the FS in a RDB? Which FS version are you using on the 68k side?