Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: atom-ant on December 25, 2010, 08:34:09 PM
-
Done a update on my samflex440ep stated to load now I get is
AOS4 FLB
FLB:No SLB found in any of the designated boot sources; returning to u-boot. press any key to contiune.
Than I press any key and got this ] Than I reset but still have the same problem.
-
Done a update on my samflex440ep stated to load now I get is
AOS4 FLB
FLB:No SLB found in any of the designated boot sources; returning to u-boot. press any key to contiune.
Than I press any key and got this ] Than I reset but still have the same problem.
It's unlikely to be "DEAD", rather some settings just got reset with the firmware update.
I get the impression that you're new to the system. If so, I'd advice you to stay away from major updates or actions that require some more experience. Try to learn the system by using the provided applications and tools and familiarize yourself with the OS and its concepts. Post to various forums and ask the questions (there are no stupid questions). Only once you've gained some confidence go on with some of the more advanced topics such as upgrading firmware or tuning firmware variables.
I believe you'll save a lot of headache and aggravation this way.
-
Thanks for the tip but can I fix it?
-
Thanks for the tip but can I fix it?
I think you should contact your reseller or ACube directly.
-
After a long time thinking were I went wrong all it was the boot opitions was not set (they were set at none) and now the Amiga is all working again but I will take good notice of the advice you gave me.
-
Glad you got the computer working again. We don't need our toys out of commission on Christmas! I echo Piru's advice -- no such thing as a dumb question, though I'm sure I've strained that a bit now and again as I've sought advice here and elsewhere.
-
I'm sorry friend, and welcome to the Sam crashed club, well, I told you in a previous that this update isn't needed, I hope that you have more luck with ACube that me.
-
I think you should contact your reseller or ACube directly.
You wanted to post "no" there, didnt you :-)
-
The problem is quite simple actually... The SAM likes you to tell it where your drives are in the ports what the device is and what the booting sequence is...
now I'm not 100% sure why it can't do it autoconfig like but since it's very easy to set the parameters it's no biggie and to be honest I don't know why people insist computers need to be dummy proof... LEARN!
for example say you have ports 20 21 22 and 23 and SAM instructs you to have the bootable HD in port 20 and a DVDRW in port 23...
sii3114ide_conf=1002 (I have sii3114ide_conf=1112 since I have 3 HDs attached)
see that 2? It means theres an optical drive in that slot... if for example you decided to swap out the DVDRW with a harddrive but didn't change and save that 2 to a 1 chances are very high it won't show in the system when it boots up
The reason why your system didn't boot is perhaps something did change with the update and it was looking for a drive attached to sii0680ide instead of sii3114ide or your bootable system HD wasn't in the list of booting devices, not sure how that would happen but something must have happened, or you left something out...
type nvgetvar in a shell window and go from there ;-) (once you type this command you'll also see what devices you have in your machine... I have sii3114ide because I am using my SAM Flex as an example and other one comes from an extra ide card I plug into the PCI slot on occasion)
tip: if you're looking for the command to change any setting type dir c: and look, if you want to change a setting rule of thumb is leave the = sign out when typing a parameter string if you muck up and have a variable saved that was typo'd type it exactly the same as you first did and it should be removed not sure if that includes the actual parameter value or not... gotta leave some experimenting to you ;-)
Look in DH0:Documentation/IDE/ for more documentation on your specific controller and settings you can implement that may or maynot be present yet and an explanation on how to use IDETool
anyway, don't be afraid and go out there and make us proud! sorry the explanation isn't exhaustive BUT It's
Time for me to go back to Star Ocean LOL :hammer:
-
@Slayer
Once set though, you shouldn't have to mess with the boot sequence again.
I have done all the updates and have never had that problem.
My guess is that when he selected the option to boot from cd to do the update, he has saved the change to the boot sequence.
-
Yes, that is why I said he might have left something out eg didn't tell us something - what you suggest sounds exactly what could have happened
next time select reboot but don't save changes or configure it so it'll try and boot of the dvdrom drive first then the boot harddrive second
I've never had any problems either
All one has to remember if dabbling in reconfigurating ones hardware setup 'expect the unexpected' since alot of people leave well enough alone as long as it works but the trouble is sometimes it still isn't set up properly and when you add that extra device it all doesn't work the way you're expecting it too...
The SAM or UBoot etc has 2 or 3 files that need to be sorted and then once that is all ticked off there's that elusive kickstart directory with the likes of diskboot.config and Kicklayout but generally most people can stay out of there ;)