Hmm, help?

I missed the slb readme as well. So I tried booting an old formware update cd to go back to an old uboot but this command just doesn't work:

diskboot 500000 2:0 1

It just says device 2 not available. I have a paralell sil device. And the CDROM is on device 2.

So I decided to try booting the os4 update CD instead. But I can't get it to boot from the CD. Boota doesn't work. I can't change the default boot device in the menu system, it just resets back to the onboard ide device.

So what do I do?

Ps. Why not provide one singe readme in the root level sayign READTHISORDIE or something instead of hiding it away in some sub directory?

/Björn

Thank you Hyperion.

After a little fiddling about my boot time from pushing the power button to the time that AmigaOS4 is ready to use is now just 38 seconds!

I could shave even that down by two seconds, and I am sure if I really knew what I was doing it could get even lower.

UBoot is marvelous, I sit looking at my XP machine which does all sorts of things I have no control over and where the kids have got so many startups in the registry and hell knows where that I have to purge the threads once it is eventually going and then I come to a 38 second cold bootup -- its just magic, moreover that even I can get my head around Uboot and could see how I could style it for specific needs.

Great work, -- please let the next update come realy soon.... it just gets better and better.

Now my problem is only the long BUS 0: timeout because I have a PCI IDE, otherwise no bother.

Menu > Intergated Peripherals > Internal IDE Controller: Disabled

Quote:

It just says device 2 not available. I have a paralell sil device. And the CDROM is on device 2.

Have you tried "ide reset"? If the CD was not in the drive when you switched on, it would not be recognized in U-Boot.

Quote:

Boota doesn't work. I can't change the default boot device in the menu system, it just resets back to the onboard ide device.

Try the following from the U-Boot prompt

setenv boot1 psii (or psiicdrom if you want to boot from the CD)
boota

and see if that works.

Quote:

Why not provide one singe readme in the root level sayign READTHISORDIE or something instead of hiding it away in some sub directory?

Last-minute addition. I thought that if people would find the slb they would also find the readme for that...

@mufa
Quote:

Menu > Intergated Peripherals > Internal IDE Controller: Disabled

Thanks for that, I did finally find it, but it is useful to have it published here, there might be others.

Installed the october uboot. Turned out I had to reboot to get it to boot from the oct uboot update cd. ide reset did absolutely nothing. Possible because changing default device in the menu system doesn't work. I guess "setenv boot1 psii" would have worked.

Anyway, I continued:

I updated the slb to slb_v2 from the updater archive.

reset and installed new mar 2005 uboot.

reset again.

waited very long for the internal ide checks to timeout.

Disabled internal ide in the menu system.

set the boot device to paralell sil. Saved and exited menu system.

System refused to boot 4.0 with boota.

started menu system again, boot device had reset to internal ide. exited menu system.

tried setenv boot1 psii after reading your reply

saved prefs

boota

AmigaOS boots as normal.

/Björn

Quote:

started menu system again, boot device had reset to internal ide. exited menu system.

I'll investigate that. Can't really imagine why it would not save the variable correctly...

@Greg
Quote:

and then I come to a 38 second cold bootup -- its just magic,

Magic eh? Now how about cutting that in half?

I could tell you how, but figuring it out is more fun, at least now you know that it's possible.
(It takes 20 sec. here if there's no disk in the CD drive)

@ Rogue

I also had problems getting the new SII Parallel Disk settings to save. I gave up trying to do it with setenv, so used the menu in UBoot and each time I saved it there it would reset back to the onboard VIA. Eventually, after 4 attempts it finally saved and all is fine here now.

Thanks for the update.

@lylehaze:

"Flash is wonderful stuff, sure beats booting from paper tape. (Oops, my age is showing again)"

Ah, but can you still remember the PDP-11 absolute loader to key in on the front panel switches?

tony

@Rogue

It's as likely as "ide reset" don't read the variable

mtreasure:

odd, all thats needed is "setenv ide=psii" and then hit enter and type "saveenv" anyway glad u got it running again.

Installed and rockin' its a good job i read these posts before i updated or my
A1 would not of booted with the old SLB!

Still no VIA DMA, I suppose a 30 sec. boot time will just have to do for now!

Wizz.

Quote:

Still no VIA DMA, I suppose a 30 sec. boot time will just have to do for now!

VIA DMA has nothing to do with the firmware. You need a DMA-enabled driver for that.

Quote:

VIA DMA has nothing to do with the firmware. You need a DMA-enabled driver for that.

Since Eyetech claims that the problems with VIA DMA is in the initialization, I would suspect the firmware would be the place for the initialization. Or am I wrong?

After the VIA DMA has been setup correctly, yes, we would need a DMA-enabled driver.

"problems with VIA DMA"

oh plase go and get your hw fixed for the driver now,

Quote:

Poster: drHirudo Date: 6-Mar-2005 2:02:10 Quote: "1. with an A1XE-G4 with radeon 9200SE/128MB card, post uBoot/AOS4 selection, my screen remains blank for ~10+ seconds before coming up with the workbench screen. Will the AGP fix in uBoot perhaps affect this?" That has happened to me and to my friend after we installed update 2 (we both own ua1) He thought maybe it was scanning usb drvices. Anyone have any ideas on this? During the black screen AmigaOS4 also configures the Internet connection, and when I used DHCP there was such slowdown. So I turned off DHCP and configured my LAN settings properly and now it boots much faster.

Thanks, I'll give that a shot. Normally all my systems are indeed static IP, but figured 'if it works, don't fix it' might be an idea for a bit.

Last edited by wegster on 06-Mar-2005 at 06:47 PM.

Quote:

Since Eyetech claims that the problems with VIA DMA is in the initialization, I would suspect the firmware would be the place for the initialization. Or am I wrong? After the VIA DMA has been setup correctly, yes, we would need a DMA-enabled driver.

I don't know of any form of initialization that could cure the DMA problems. A lot of research has gone into this topic, and to the best of my knowledge there is no software fix (all software fixes involve the VIA Northbridge).

The hardware fix is the only thing that works.

Quote:

Suns and flowers, btw...you mean like "Sun Microsystems" and "Petunia"?

Quote:

Quote: am i correct that the "keyboard-mouse-usb-combos" are not yet supported with this update? at least here my hardware is not identified/used. Mice are unsupported in U-Boot.

that's clear
Quote:

A combo should be recognized, though, at least my Microsoft wireless combo is correctly identified.

strange...

i tried both of our wireless keyboard/mouse combos: "logitech wireless desktop" and "logitch wireless desktop navigator"... both are neither recognized by u-boot nor by os4.
u-boot does not recognize the usb device at all (only telling me "one usb device found" which is the controller...)
with os4 i always get "hub drive was unable to add the attached device" when i plug it in.

what's wrong?

byebye...