@NutsAboutAmiga

Okay, so I changed the irqa to be 9 to get rid of the conflict with irqc. I have not put the HDD on another cable yet as I haven't found a spare.

I did up the debuglevel to 20 and rebooted. The DH0: partition where I installed AmigaOS4.0final has a lable of AmigaOS4.0:

The log is here:

http://pastebin.com/paKGcBUQ

As you can see, the last thing that happens is LoadWB was called, then all goes quiet. I let it sit for 5 minutes after that, nothing else happened. Are the read-only attributes a problem?

@NutsAboutAmiga

Quote:

I do not understand way it try's mode 12, we asked for mode 1.

Mode "1" doesn't exist. So it's a default used. And it translates the UBoot mode into the actual IDE mode. Whatr we want is mode "0" set. See here:


0 - Automatic PIO (driver will use the best PIO mode
that the drive claims to support)
a - PIO 0 ( 3 MB/s, modeid 8)
b - PIO 1 ( 5 MB/s, modeid 9)
c - PIO 2 ( 8 MB/s, modeid 10)
d - PIO 3 ( 11 MB/s, modeid 11)
e - PIO 4 ( 16 MB/s, modeid 12)
A - UDMA 0 ( 16 MB/s, modeid 64)
B - UDMA 1 ( 25 MB/s, modeid 65)
C - UDMA 2 ( 33 MB/s, modeid 66)
D - UDMA 3 ( 44 MB/s, modeid 67)
E - UDMA 4 ( 66 MB/s, modeid 68)
F - UDMA 5 (100 MB/s, modeid 69)

Last edited by Hypex on 23-Nov-2013 at 12:27 AM.

@themamboman

Quote:

Okay, so I changed the irqa to be 9 to get rid of the conflict with irqc

It should look like this:

pci_irqa=9
pci_irqa_select=level
pci_irqb=10
pci_irqb_select=level
pci_irqc=11
pci_irqc_select=level
pci_irqd=7
pci_irqd_select=level

Strange that your IRQ settngs were messed up. That factory reset is starting to look good

Quote:

I have not put the HDD on another cable yet as I haven't found a spare.

Okay, regardless you might want to try blanking out the a1ide_conf variable. OS4 can detect what is on there and if you shift drives around you don't need to change it before hand.

Quote:

Are the read-only attributes a problem?

They are in a read only section of the executables so not much you can do about that.

@Hypex

Okay, I'll make sure the pci_irq... values are just like you show above. To blank out the values, just delete the whole a1ide_conf setting altogether or set to 0000?


Thanks so much everyone. Sorry to be a pain. I would have thought this would have been easier...

@themamboman

No its a1ide_xfer values you set to 0000, a1ide_xfer sets the speed.

0 = is Best PIO mode.

0000 is Best PIO mode,Best PIO mode,Best PIO mode,Best PIO mode.

a1ide_conf defines what is connected to your controller

0 = NC (Not connected)
1 = HD
2 = CDROM

2100 is CDROM,HD,NC,NC.

Hypex suggest you should blank the a1ide_conf.
He says a1ide_conf is not needed.

if you delete the setting you can set it again if does not work, I do not think it make any difference for you.

The first thing for you to do is to fix the IRQ problem.

Last edited by NutsAboutAmiga on 22-Nov-2013 at 10:55 PM.
Last edited by NutsAboutAmiga on 22-Nov-2013 at 08:46 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Quote:

Hypex suggest you should blank the a1ide_conf

Yes I am. Because that would set it to default and make OS4 probe the devices. And because I've seen trouble with this variable and OS4 loosing drives.

I've even checked to see if it match the hardware on one machine I was setting up. To me it checked out. Kickstart loaded and OS4 couldn't find a disk!

So I just end up blanking it out. Blanking out is a good option when testing.

@themamboman

And by blanking I mean to erase the variable. So in this case a1ide_conf is the one to erase. Also check on a1ide_irq. Some drives conflict IRQ on UBoot.

Please let me ask something that might be a piece of help as well.

In the classic Amiga OS4.0 and 4.1 releases there is an ASCII file called BootDevice it is generated on a simple text editor including the name of the device that kickstart should look at to boot the OS -WHEN having entered in OS4 native mode-.

A typical BootDevice file would include this for example:

DH0

And there is a MODULE line on the kicklayout file that enables this feature, disabled if commented.

Does this exists on the AmigaOne?

_________________
Peg1, Peg2, Efika,
Amiga 500, Amiga 1230,
Amiga 4000PPC,
Sam 440EP, AmigaOne XE,
MacMini PPC, PowerMac G4, G5

@Morphix

Yes but its optional, if you want to setup a multi boot system, there is a trick you can use.
(One of the uboot kickstart layout option will have this to override the boot priority.)

I used to use this trick to boot a older version of AmigaOS, so I was able to use NallePuh.

Last edited by NutsAboutAmiga on 23-Nov-2013 at 01:02 PM.
Last edited by NutsAboutAmiga on 23-Nov-2013 at 01:02 PM.
Last edited by NutsAboutAmiga on 23-Nov-2013 at 01:00 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Perhaps if this line is added then the kickstart would know where to look. So no disk requester (boing window with floopy disk insert request).

Can you remember the exact syntax on the kick layout?

Should someone simply add

MODULE Bootdevice

(I wanna test it as well).

_________________
Peg1, Peg2, Efika,
Amiga 500, Amiga 1230,
Amiga 4000PPC,
Sam 440EP, AmigaOne XE,
MacMini PPC, PowerMac G4, G5

@Morphix

Thats not the problem it loads, but crashes on loadwb.

Its some sort of corruption I think,

a) Interrupt problem,
b) problem whit loading from disk, bad hd, bad cables.
c) bad RAM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@Hypex

Hi and thanks for the suggestions.

Removing/blanking the a1ide_conf file returns to the original problem I had: Boing ball insert floppy screen. Putting it back with value 2100 goes back to the blank screen. I'm going to dig around looking for another IDE cable to put it onto the other internal IDE header and see if that help (and changing the a1ide_conf value)

@themamboman

I'm going to just restart from scratch, factory reset UBOOT parameters, get another harddrive, and put both it and the DVD drive as master drives on their own headers. Using only a single RAM SIMM and the AGP card, I'll try to reinstall using the guide included in the CD.

I may also just try to install Debian first to see where that leads.

Maybe doing it all from the start again will find and fix the problem.

Thanks again to all who helped!

@themamboman

I hope you remember to remove the CD before taking a cold reboot, or else the kickstart modules might be loaded from CD, and the OS files from HD, the result is not that great, if the OS is newer then the kickstart files.

Last edited by NutsAboutAmiga on 27-Nov-2013 at 05:19 PM.
Last edited by NutsAboutAmiga on 27-Nov-2013 at 04:19 PM.
Last edited by NutsAboutAmiga on 25-Nov-2013 at 01:42 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@themamboman

Quote:

Removing/blanking the a1ide_conf file returns to the original problem I had: Boing ball insert floppy screen

Damn! Okay default according to my UBoot Prefs save looks like a space. Guess tihs woudn't help on UBoot CLI:

setenv a1ide_conf "    "

Last edited by Hypex on 28-Nov-2013 at 09:06 AM.