Hi

Been away from the Amiga scene for over a year but getting back into it again and so wanted to get my AmigaOne G4 XE 800MHz updated to the latest OS4.

My AmigaOne would not boot at all so i changed the battery with one from an old PC which was the same type and it came back to life, i needed to update uboot to the latest version so burnt a CD image and flashed the rom with it, it all went through fine just like previous uboot updates i have done in the past but after the automatic restart all i get is a flashing white cursor in the top left of the screen :(

So it looks like a problem with uboot but the re-flashing all looked fine when i updated it.

Does anyone know what i can do to fix it?

Cheers

@Leki

Have you tried to boot Amiga OS 4.0 with the CD Rom?

You have to type "ide reset" "setenv boot1 cdrom" and at last "boota".Each command followed by "Enter".

After this you can boot and make the installation of OS 4.0.

Try and tell me if you boot the CD or not.

_________________
AMIGA 500 1.5 MB ACA500/ACA1232 accelerators
AMIGA 500 German
CD32 unexpanded
Amiga 1200 Tower on AmigaKit since years
AMIGA 1300 030/50 Mhz/32 MB WB 3.9 with lots of games&demos
AMIGA ONE XE G3 PPC 800 Mhz/1 GB RAM/RADEON 9250 128 MB/SATA CONTROLLER

@newlight

Hi

It doesn't allow me to type anything in, it doesn't show the usual IDE controller listing of HD, CD drive etc as it goes instantly to the flashing cursor and does nothing else.

the cursor is an _ and not the usual ] from uboot.

@Leki

Try a new battery, the one from your PC prolly only had enough power for a single boot, like when you leave old batteries for a few weeks and then you can get 1 small blast of power from them.

_________________
OS4 Rocks
X1000 beta tester, Sam440 Flex (733)

Visit the Official OS4 Support Site for more help.

It may be that your sole purpose is to serve as a warning to others.

@Leki

You are getting something so the flast must be okay in sme ways. Otherwise, if no code was running, I don't think the gfx card would be initalised enough to display anything.

If I get a failed boot here my monitor doesn't turn on. Of course this is assuming that your gfx card doesn't display a flashing cursor when it comes on, but UBoot is needed to run any gfx card boot code.

Did you flash from your old update to the one after or a straight flush? In the old versions they liked intermittent updates of the flash code. So if you always flashed to the new versions you were fine. But flashing to the latest and skiping some updates was said not to be done.

@Leki

Possibly it's outputting the UBoot prompt to the serial port instead. If you have a null modem cable and another machine I'd suggest connecting it up and checking if you're getting any text.

Hans

_________________
Join the Kea Campus - upgrade your skills; support my work; enjoy the Amiga corner.
https://keasigmadelta.com/ - see more of my work

thanks for the replies guys

@Severin
i will purchase a few new batterys when i get chance to see it helps.

@Hypex
i think i went from oct 2004 uboot to march 2005.....should that be ok?

@Hans
i think i do have a cable somewhere....i'll dig it out and see if i can get any output.

@Leki

type in "setenv stdout vga"( you won't see anything as you type and curspr will not move). Then press enter. that will sow you if you are set to serial output.
If yo were in serial output you can now type saveenv and see what you are typing.


painter

Last edited by painter on 22-Sep-2007 at 06:40 PM.

Hi @painter

You're NOT reading -- there's no prompt. The machine boots up to a black screen with a flashing cursor in upper left hand corner. Nothing else.

I got the same identical problem; trying to determine the problem!

_________________

@Snuffy

You will need to connect a serial cable to another computer and the A1 and read the output, let us know what it says.

_________________
AmigaOS 4.x Beta Tester - Classic Amiga enthusiast - http://www.hd-zone.com is my Amiga Blog, check it out!

Hi @HammerD

You will need to connect a serial cable to another computer
I only have a stock A1200 and A2000. Would one those work; and how?

_________________

@Snuffy

Yes if you have the correct cable. Then use a Terminal program like Term on your A1200 or A2000 and set it to 115200, 8-N-1). You should see output to the screen on the Amiga when you turn on the A1.

For me I use 9-pin serial cable to connect from my MicroA1 to the PC with Windows. I use Hyperterminal on the PC.

_________________
AmigaOS 4.x Beta Tester - Classic Amiga enthusiast - http://www.hd-zone.com is my Amiga Blog, check it out!

@Leki

A wild guess:
I returned to A1 after a very long break (had a broken module) and replaced the battery with a new one.
When I fired it up, I got no video (I know, a different symptom). I found this solution:

1 disconnect ac and remove battery
2 wait couple of minutes (2 or so)
3 put in the AC, and ensure the A1 is shut down (mine sometimes powers up on connection of AC, just shut it down then)
4 put the battery in and fire up

Good luck,
Jack

_________________

"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg

@HammerD

Quote:

Then use a Terminal program like Term on your A1200 or A2000 and set it to 115200, 8-N-1)

The UBoot default is 9600 if I recall correctly, so unless you have changed it yourself, try with 9600 first.

_________________
Site admins are people too..pooff!

@Leki

My A1 failed whilst booted. It would not reboot and ended with the flashing cursor (or, it may have been a completely blank screen) where UBoot command line should have been. I changed the battery, got UBoot menu and tried to recover settings. Back to flashing cursor.

I suggest you try pulling out the mains plug (or equivalent) and removing the battery for a minute or so. If you get a proper UBoot after replacing the battery, choose 'restore default settings'. If you were as lucky as I was it should reboot into OS4.0 and you will be able to use UBoot prefs to fine tune HDD and other settings.

Regards
Roy Leith

@Snuffy

Quote:

Snuffy wrote: Hi @painter You're NOT reading -- there's no prompt. The machine boots up to a black screen with a flashing cursor in upper left hand corner. Nothing else.

I'm sorry to say this but your ignorance is showing again. It's no good having a go at painter, he's right. if you ever see the display from an initalised gfx card it is just a blank screen with a flashing underscore cursor, which means either uboot is not working (possible dead battery) or the output is going somewhere else (like the serial port but this would not stop the boot process unless the settings are corrupted).

_________________
OS4 Rocks
X1000 beta tester, Sam440 Flex (733)

Visit the Official OS4 Support Site for more help.

It may be that your sole purpose is to serve as a warning to others.

@Leki

Quote:

i think i went from oct 2004 uboot to march 2005.....should that be ok?

I examined the readme files and they don't mention it. Plus the dates you mention are the latest and one eariler edition on the Hyperion site. So it looks like you should be safe.

Hi @Severin

You're butting in! You should get some intelligence. Why don't you write a A1 User Manual instead of making cheap comments. I owned the A1 for the last four years.; I know something.

There are no guide lines for me determine the problem, so I am guessing. I pointed this out to Amiga Center here.

_________________

@Snuffy

Easy now, lets keep this thread civil - I can understand your frustrations my friend. Did you try Roy Leith's suggestion?

Cheers,
Rude!

_________________
2017 Camaro 2SS

@Snuffy

You can perfectly enter commands in UBoot even if there is no prompt.

For the record, if you turn on your A1 and see the flashing cursor, it means MANY things are working correctly.
Having a working video frequency output plus the cursor means the x86 BIOS emulator run correctly, which means:
1) CPU is fine
2) RAM is (somewhat) fine, because UBoot relocates itself very early in RAM.
3) the graphics card is fine too
4) the x86 emulator was able to run

I'll join the chorus of those saying you should try to replace the battery with a new one, not one scavenged from an old PC.
And connect a null-modem cable for diagnosis.