Installed but now only have insert floppy animation

[themamboman]

Alright, I've posted something similar elsewhere, hoping to find a kind soul that might know what could be going on here.

I've been a long-time classic user, always wanting to go NextGen for OS4.x, but couldnt' due to the high cost of hardware. Well, I finally found an A1XE G3 motherboard, so I decided to take the plunge and get it and put it into a standard ATX case with Radeon AGP 9000 pro, soundblaster 128, peripheral card and RadeonHD4650 with pci/pcie adapter (the last ones are for after I get 4.1).

Anyway, since it came with a Amiga 4.0 developer pre-release CD, I decided to go with this first and if successful, then update to 4.1.
Registered pre-release of 4.0 so I could then download and use the 4.0 Final ISO to do the install (I couldn't install with pre-release, because my mouse pointer never showed up, final fixed that).

U-Boot 1.1.1, autostart=yes,
Using internal IDE controller (CDROM is master, 32GB HDD as slave), 1 GB RAM, no visible evidence that it has either the UDMA or USB fixes.

- Booted from Amiga OS4.0 Final CD
- Started the installation automatically
- Opened Media Toolbox
- Edit RDB, installed the slb_v2 file
- then partitioned the HDD into DH0 (FastFileSystem, long names, automount, bootable) and DH1 (FFS, Longnames, automount, not bootable).
- Saved changes to disk, exit Media Toolbox
- Restarted
- booted back into the CDROM,
- formatted the two partitions with Quickformat
- then ran the long installation procedure
- finally selecting the resolution of the AGP radeon 9000 pro card (maxed at 1600x1200), then restarted.

Changed to boot IDE HDD instead of IDE CDROM, It did the FLB/SLB text, then showed a single entry that was bootable: AmigaOS4.0 on DH0.
Let it boot that. Saw a progress bar in the terminal-like environment saying that it was loading the kickstart files (very fast since it was from the HDD).

Then, blank screen for a few seconds, then...

Boing Ball screen, insert floppy animation.


Anyone have any ideas?

Any help is much appreciated. I can't wait to get 4.0 running, then update to 4.1 and start developing!

[tonyw]

You're stretching the memory here...

I suggest you:
1) Interrupt the U-Boot startup process (With the space bar? Forgotten).
2) Choose the "Boot Sequence" menu item and check that it says CD first, HDD second.
3) You are using the on-board IDE interface? If so, make sure that "ide_maxbus" is set to 1 (Primary only) or 2 (Primary + secondary). If it's set too high, it will hang for 20-30 seconds while the missing device times out, but it's not harmful. You can always go back and set it back again. Use the U-Boot commands "printenv" and "setenv" to list and edit variables.
4) Go back and boot the CD again.

From the CD's Workbench:
1) Open MTB, check that the slb is installed (I know you said you did it, just recheck).
2) Check that DH0: is bootable (I know you said you did it, just recheck).
3) Check the boot priority of DH0. Don't make it any higher than about 2. (The CD is 5).
4) Check that DH0: is flagged as bootable.
5) Check that DH1: is NOT checked as bootable.
6) Try again. Remove the CD, then hit the Reset button.

There are some funnies with the old U-Boot. The one that always tricks me is that it loads its Kickstart modules from the device with the highest Boot priority, but then goes ahead and boots the first device that it comes to. So, if you have DH0: bootable with a priority of 2 and DH1: bootable with a priority of 3, and you select DH1: as the boot device, the system will load Kickstart modules from DH1:, then make DH0: the System disk. The libraries on DH0: may not be up to date with the Kickstart modules on DH1:, so problems. The solution is to have only one partition "bootable" at a time.

[themamboman]

Thanks for the update.

I went through your steps and had the same issues.

Quick update on what I tried afterwards:
- removed a 2nd IDE controller card to be safe, (DVD drive and HDD on internal IDE controller)
- ensured that ide_maxbus was set to 1
- saveenv
- Booted into install CD
- opened MTD, changed to a single parition on the HDD
- FFS with long filenames, full 32GB
- automount and bootable checked, boot priority = 0 (default)
- bootloader installed as L:/slb_v2
- rebooted, quickformat of the new paritition
- installed the software from CD to HDD
- before resetting, ensured that the L:/ drawer had slb_v2 there
- also re-verified with MTD that automount and bootable were checked
- rebooted, removed CD, set to boot from IDE
- showed a single boot option to select: AmigaOS4.0 on DH0:
- booted, fast loading of kickstart progress bar
- boot floppy animation.

Thank you for the helpful suggestions, any others that might come to mind?

[Raziel]

nvgetvar >ram:log

and post the output here, please

[tonyw]

I'm almost out of ideas, it's so many years since it happened to me.

Try reading this thread on aw.net: It describes the same thing and you may get some help from it:
http://amigaworld.net/modules/newbb/vie ... 4&forum=33

[themamboman]

Here's the output of the nvgetvar

baudrate=115200
stdout=vga
stdin=ps2kbd
ide_doreset=on
ide_cd_timeout=30
menucmd=menu
bootmethod=boota
ethact=3Com 3c920c#0
ethaddr=00:09:D2:11:00:98
limit_memory=1024
use_memory_limit=yes
bootcmd=menu; run menuboot_cmd
idemax=1
menuboot_cmd=boota; boota; boota
autostart=on
serial1_address=3f8
serial2_address=2f8
parallel_mode=0
parallel_address=378
usb0_enable=on
usb1_enable=off
usb_use_header=0
ide_maxbus=1
ide_swap=0
boot1=ide
boot2=cdrom
boot3=
boot_config=Default
boota_timeout=10
bootdevice=0:2
boot_command=diskboot
boot_method=boota
menuboot_delay=5
os4_commandline=debuglevel=0
bootargs=root=/dev/ram rw ramdisk=4096
pci_irqa=11
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
agp_enable=on
agp_sideband=off
agp_speed=2x


Thank you for all the help. The thread on AW.net is one that was old that I was also working on. NutsAboutAmiga wants me to look into a1ide_conf file but I can't seem to find it.

[Raziel]

Here's the output of the nvgetvar

Hidden Text - Click to Show :

baudrate=115200
stdout=vga
stdin=ps2kbd
ide_doreset=on
ide_cd_timeout=30
menucmd=menu
bootmethod=boota
ethact=3Com 3c920c#0
ethaddr=00:09:D2:11:00:98
limit_memory=1024
use_memory_limit=yes
bootcmd=menu; run menuboot_cmd
idemax=1
menuboot_cmd=boota; boota; boota
autostart=on
serial1_address=3f8
serial2_address=2f8
parallel_mode=0
parallel_address=378
usb0_enable=on
usb1_enable=off
usb_use_header=0
ide_maxbus=1
ide_swap=0
boot1=ide
boot2=cdrom
boot3=
boot_config=Default
boota_timeout=10
bootdevice=0:2
boot_command=diskboot
boot_method=boota
menuboot_delay=5
os4_commandline=debuglevel=0
bootargs=root=/dev/ram rw ramdisk=4096
pci_irqa=11
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
agp_enable=on
agp_sideband=off
agp_speed=2x

Thank you for all the help. The thread on AW.net is one that was old that I was also working on. NutsAboutAmiga wants me to look into a1ide_conf file but I can't seem to find it.

Yeah, thats where your problem lies, UBoot is not configured to have any devices on the internal ide

In Uboot do:
set a1ide_conf 1200
save

That is if your HDD is on the first master and your CD is on the first slave

btw: Your maxbus entry is wrong, it must be "a1ide_maxbus"
(It's set to "2" here, because i have the CD on the seond master)

These are my variables, just for the record, you can use them to look up some settings, but you gotta keep in mind that some entries differs from yours, like the "AmigaOS4.1" entry for "boot_config"

Hidden Text - Click to Show :

bootcmd=menu; run menuboot_cmd
bootdelay=0
baudrate=115200
preboot=
stdin=ps2kbd
ide_doreset=on
ide_cd_timeout=30
menucmd=menu
bootmethod=boota
ethact=3Com 3c920c#0
ethaddr=00:09:D2:11:02:BE
a1ide_timeout=20
a1ide_irq=1111
a1ide_maxbus=2
a1ide_conf=1020
kbddev_sysreqishelp=yes
kbddev_norwin=yes
sii0680ide_maxbus=0
sii3112ide_maxbus=0
sii3114ide_maxbus=0
autostart=yes
stdout=vga
menuboot_cmd=ide reset; boota; boota; boota
video_num=1
video_activate=pci
serial1_address=3f8
serial2_address=2f8
parallel_mode=2
parallel_address=378
usb0_enable=on
usb1_enable=on
usb_use_header=1
ide_maxbus=2
ide_swap=0
boot1=cdrom
boot2=ide
boot3=
boot_config=AmigaOS4.1
boota_timeout=3
boot_method=boota
menuboot_delay=3
os4_commandline=debuglevel=0
bootargs=root=/dev/ram rw ramdisk=4096
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
agp_enable=on
agp_sideband=on
agp_speed=2x
limit_memory=512
use_memory_limit=yes

[themamboman]

That definitely seems to have helped. I had to use 2100 instead of 1200 as my cdrom and hdd are reversed when it comes to which is master and which is slave.

Unfortunately, instead of a boing ball animation, I get a blank screen. I thought maybe my monitor selection at the end of the install wasn't good (I picked 1600x1200 for my 24 inch monitor which can handle up to 1920x1200), so I reinstalled, and chose the default 800x600 60 (default) which I assumed was the same as the mode used during install. Still blank screen.

Hmm... this has been a surprisingly difficult ordeal. I wonder if SAM boards or 4.1 would make it easier?

[Raziel]

That definitely seems to have helped. I had to use 2100 instead of 1200 as my cdrom and hdd are reversed when it comes to which is master and which is slave.

Unfortunately, instead of a boing ball animation, I get a blank screen. I thought maybe my monitor selection at the end of the install wasn't good (I picked 1600x1200 for my 24 inch monitor which can handle up to 1920x1200), so I reinstalled, and chose the default 800x600 60 (default) which I assumed was the same as the mode used during install. Still blank screen.

Hmm... this has been a surprisingly difficult ordeal. I wonder if SAM boards or 4.1 would make it easier?

Of course...a second Amiga around the house is always good

But back to topic...you don't say *where* you get the black screen?

Does it count down the kernel files? (White bar with kernel files being printed above?)
Do you get to the "AmigaOS4.1" splash screen?

The "black screen" (if encountered *after* the splash screen) can point to a slow internet access (this normally takes up to minutes if not correctly configured and can even stall)

[themamboman]

Ah, sorry, wasn't specific enough:

It does run through the kickstart progress bar, very fast, then goes blank. Before the last fix, there would be about 15 seconds, then the insert floppy animation. Now, it just stays black. Left it for 5 minutes.

I don't have a network connection on it right now. I wouldn't have thought that was needed. Was just hoping to get into Workbench.

Didn't see a splash screen. Just stayed blank.

I know the monitor can do the selected screenmode because the installer used it.

Thanks again!