I thought that I would buy a 2nd HDD to backup my data to and add it to my Flex. However when I hooked it up, UBOOT did not recognize it??
So I removed the DVD Sata connection and hooked the HDD to it. This time UBOOT did recognize it, BUT Media Toolbox did not, except for the fact that it told me that drives have been added or removed.
Went back to my original config:
Boot HDD on J20 DVD drive on J23
Adding a 2nd HDD is possible right??
I want to add it to either J21 or J22 SATA connection.
Is there any setting in UBoot or elsewhere that I am missing?
The way I understand it, you can connect devices also to the two other channels, but UBoot will currently not see them. Once OS4 is booted, all 4 should be visible. So you can add your second disk, but you cannot boot from it (currently).
@amigadad I don't have a second SATA drive to connect but when I was trying to troubleshoot other problems, I was able to connect the DVD drive to J22 and OS 4.1 recognized it (as documented you can't boot from that connector though). What I found peculiar was that I could not boot from the DVD drive when it was connected to J23 (correct connection) and there was no hard disk connected to J20. That would seem to indicate that my system will not boot at all if the primary hard disk fails. That sort of makes the DVD drive useless as a backup boot mechanism. Sorry I can't be of much help you but if you are willing to be risky you might try placing a Boot CD in the DVD drive and connect the new hard disk to J20 to see if it gets recognized.
I did hook up the new HDD to J20 and unhooked the exsisting os4.1 HDD.
Then I proceeded to install Debian Lenny net install to the new HDD.
All went well untill it wanted to get the updates from the Debian mirror and then the progress just sat at 5%. (the same thing happend to me when I tried to install Debian Lenny on the original HDD. But that is another topic!)
So I know the physical drive is OK.
Then I tried to hook the new HDD to J23 and the original HDD to J20. UBoot recognized both HDD and started to boot, HOWEVER the boot process only got to the point just prior to showing the OS4.1 splash image (Just a black screen).
My SAM Flex has 2 HDs and 2 DVDRW attached... so full SATA ports and all work fine...
Perhaps you have a jumper in the wrong place on this new SATA drive? There isn't much other explanation except for compatiability problems since you should be able to plug another drive into either the 1 or 2 port if say your SATA drives are numbered 0 1 2 3... othewise 2 and 3...
If HDTools isn't seeing it I'd be willing to be there is something else amiss... does it actually power up?
Ok I'm confused now, I just read your last post and it speaks on partial installation and partial booting etc etc etc... perhaps it is damaged on a certain part of the disk?
These problems are easier to fix and diagnose when one is there... good luck...
Revised:
If I was you I'd go back to the status quo that worked... original OS4.1 HD on port J20 and DVDRW on port J23 right?
Power down and attach the other drive to J21.
Boot right through to the WB Screen and start up HDTools... it doesn't see your HD? well, get another one, maxtor or more likely westerm digital and start again...
If you start with the proper setup that works and the harddrive is the addition dont' go breaking what works to try and make something work that doesn't seem to do just that... and as it should...
I'd be thinking, this HD isn't a good sign...
Edited by Slayer on 2009/7/25 6:45:43
~Yes I am a Kiwi, No, I did not appear as an extra in 'Lord of the Rings'~ 1x AmigaOne X5000 2.0GHz 2gM RadeonR9280X AOS4.x 3x AmigaOne X1000 1.8GHz 2gM RadeonHD7970 AOS4.x
- Connect your original HDD to the J20 connector and your DVDRW to the J23 connector, - Connect your new HDD to the J21 or J22 connector (as you wish).
After that, start up your Sam and stop the autoboot for typing the following command : - 'sete sii3114ide_conf 1112' - 'save' - 'reset'
I precise that 'sete' is working as well as 'setenv' in UBoot.
Boot on AmigaOS 4.1 and MediaToolBox should see all the harddisks now.
Note that setting the sii3114ide_conf variable to '1112' will certainly slow down AmigaOS 4.1 after the splash screen, it's normal.
If you don't set this variable to tell to uBoot what devices are connected on the motherboard, it gives your behaviour in most of case.
For your Linux problem, I've been experiencing the same behaviour since last week for the net install ; the complete install (with the iso of 680MB from ACube site) is also stopping at 'select and install software' (1%). It seems that we now have to install it with the LAN cable deconnected, Elwood will confirm it today I think.
Thanks, Laurent aka Faranheit Exclusive reseller for ARM controller for Minimig ;)
you shouldn't need to enter specific data, I didn't on either of my SAMs... the only information I have ever changed was the DMA thing...
perhaps you are speaking more of OS4 and other Hardware like an AmigaOne etc, not a SAM setup...
~Yes I am a Kiwi, No, I did not appear as an extra in 'Lord of the Rings'~ 1x AmigaOne X5000 2.0GHz 2gM RadeonR9280X AOS4.x 3x AmigaOne X1000 1.8GHz 2gM RadeonHD7970 AOS4.x
- Connect your original HDD to the J20 connector and your DVDRW to the J23 connector, - Connect your new HDD to the J21 or J22 connector (as you wish).
After that, start up your Sam and stop the autoboot for typing the following command : - 'sete sii3114ide_conf 1112' - 'save' - 'reset'
I precise that 'sete' is working as well as 'setenv' in UBoot.
Boot on AmigaOS 4.1 and MediaToolBox should see all the harddisks now.
Note that setting the sii3114ide_conf variable to '1112' will certainly slow down AmigaOS 4.1 after the splash screen, it's normal.
If you don't set this variable to tell to uBoot what devices are connected on the motherboard, it gives your behaviour in most of case.
Thanks, Laurent aka Faranheit Exclusive reseller for ARM controller for Minimig ;)
That did it!! All is working well now! Thank you so much. I presume that the long delay on the boot screen is due to one of the sata ports does not have anything attached to it, right
1112 = J20,J21,J22,J23
What is the significance of the 0 or 1 or 2 0 = disabled 1 = enabled 2 = Last device
Well that is good it was all sorted out... I never had to set it though and it was a new 320g HD...
If I recall correctly, 0 is nothing there, 1 is HD and 2 is DVDRom same as the config files in your kickstart drawer...
now...
type into an Amiga Shell
nvsetvar sii3114ide_xfer GGGG
so ya drives are all set up for DMA instead of PIO
type into an Amiga Shell
idetool -l sii3114ide.device
my readout for example:
-------------------Unit 0 information------------------------
Flags : $00000187 - present, LBA48 used, supports DMA, ATA, supports cache flush, interrupts used,
Xfer mode : best pio 12 (PIO 4, 16 MB/s) / best dma 70 (UDMA 6, 133 MB/s) / current 70 (UDMA 6, 133 MB/s)
Total blocks : 312581808
Blocksize : 512
Power mode : 2 / idle (ready for operation)
IO1 / IO2 / BMCR @ : $1100 / $110A / $1120
-------------------Unit 1 information------------------------
Flags : $0000011D - present, supports DMA, removable media, ATAPI, interrupts used,
Xfer mode : best pio 12 (PIO 4, 16 MB/s) / best dma 69 (UDMA 5, 100 MB/s) / current 69 (UDMA 5, 100 MB/s)
Total blocks : 0
Blocksize : 0
SCSI devtyp : 5
Packet size : 12
Current medium read speed : x 65535 ('65535' stands for max.)
Current medium write speed : x 65535 (idem)
Power mode : 2 / idle (ready for operation)
IO1 / IO2 / BMCR @ : $1100 / $110A / $1120
-------------------Unit 2 information------------------------
Flags : $000001A7 - present, LBA48 used, supports DMA, ATA, supports acoustic mgmt, supports cache flush, interrupts used,
Xfer mode : best pio 12 (PIO 4, 16 MB/s) / best dma 70 (UDMA 6, 133 MB/s) / current 70 (UDMA 6, 133 MB/s)
Total blocks : 625142448
Blocksize : 512
Power mode : 2 / idle (ready for operation)
IO1 / IO2 / BMCR @ : $1110 / $111A / $1128
-------------------Unit 3 information------------------------
Flags : $0000011D - present, supports DMA, removable media, ATAPI, interrupts used,
Xfer mode : best pio 12 (PIO 4, 16 MB/s) / best dma 68 (UDMA 4, 66 MB/s) / current 68 (UDMA 4, 66 MB/s)
Total blocks : 0
Blocksize : 0
SCSI devtyp : 5
Packet size : 12
Current medium read speed : x 65535 ('65535' stands for max.)
Current medium write speed : x 65535 (idem)
Power mode : 2 / idle (ready for operation)
IO1 / IO2 / BMCR @ : $1110 / $111A / $1128
*** Error opening device sii3114ide.device / unit 4
*** Error opening device sii3114ide.device / unit 5
*** Error opening device sii3114ide.device / unit 6
*** Error opening device sii3114ide.device / unit 7
*** Error opening device sii3114ide.device / unit 8
*** Error opening device sii3114ide.device / unit 9
*** Error opening device sii3114ide.device / unit 10
*** Error opening device sii3114ide.device / unit 11
*** Error opening device sii3114ide.device / unit 12
*** Error opening device sii3114ide.device / unit 13
*** Error opening device sii3114ide.device / unit 14
*** Error opening device sii3114ide.device / unit 15
Edited by Slayer on 2009/7/25 16:32:23 Edited by Slayer on 2009/7/25 16:34:05 Edited by Slayer on 2009/7/25 16:36:56 Edited by Slayer on 2009/7/25 16:56:44
~Yes I am a Kiwi, No, I did not appear as an extra in 'Lord of the Rings'~ 1x AmigaOne X5000 2.0GHz 2gM RadeonR9280X AOS4.x 3x AmigaOne X1000 1.8GHz 2gM RadeonHD7970 AOS4.x
I confirm that 0 is for no device attached, 1 for an harddrive connected and 2 for an optical drive connected.
For the sii3114ide_conf, it seems that if the user has set the s4sii_maxbus variable to 1, there is no need of this sii3114ide_conf variable, it has to be confirmed.
I didn't think to revisit these settings once I replaced the SAM with the SAM Flex (I just swapped out the MBs) seems the sii3114ide_xfer had become corrupt after either the swap or the latest OS fix... because when I looked at it tonight it was set at GOOC... WEIRD! lol
So as you see though it's back at the bottom of the list shining in 4 Gs as it should be...
anyway, lets put the subject to rest, we are getting off topic
~Yes I am a Kiwi, No, I did not appear as an extra in 'Lord of the Rings'~ 1x AmigaOne X5000 2.0GHz 2gM RadeonR9280X AOS4.x 3x AmigaOne X1000 1.8GHz 2gM RadeonHD7970 AOS4.x
hmmm that could explain it but I think it's default... but who knows
The default, if you don't have the sii3114ide_xfer variable set in UBoot, is highest PIO for all drives. At least on the A1 it is, and I don't think this was changed between the versions.
Quote:
nvgetvar command reports:
[...]
sii3114ide_xfer=GGGG
I didn't think to revisit these settings once I replaced the SAM with the SAM Flex (I just swapped out the MBs) seems the sii3114ide_xfer had become corrupt after either the swap or the latest OS fix... because when I looked at it tonight it was set at GOOC... WEIRD! lol
Don't forget that UBoot variables are kept in the non-volatile RAM on the motherboard, not on the disk. So replacing the motherboard and keeping the disk does not (in itself) preserve your old UBoot variables.
Quote:
So as you see though it's back at the bottom of the list shining in 4 Gs as it should be...
If you explicitly set the _xfer variable, why not set it to the highest mode each device can actually run, as reported by IDETool, instead of forcing all four to try the G mode and having to fall back to whatever they support? At least an optical drive will most likely not go as high, and your empty port might as well be set to 0. So the default setting you saw above, G00C, is actually quite reasonable if you have one HD and one DVD.
nbache wrote: The default, if you don't have the sii3114ide_xfer variable set in UBoot, is highest PIO for all drives. At least on the A1 it is, and I don't think this was changed between the versions.
ok but by default I was referring to s4sii_maxbus=1 , I didn't set it...
Quote:
Don't forget that UBoot variables are kept in the non-volatile RAM on the motherboard, not on the disk. So replacing the motherboard and keeping the disk does not (in itself) preserve your old UBoot variables.
This is true but I found the setting of G00C a bit random if that was a true default - but as you point out later in your post it is of course a realistic setting...
Quote:
If you explicitly set the _xfer variable, why not set it to the highest mode each device can actually run, as reported by IDETool, instead of forcing all four to try the G mode and having to fall back to whatever they support? At least an optical drive will most likely not go as high, and your empty port might as well be set to 0. So the default setting you saw above, G00C, is actually quite reasonable if you have one HD and one DVD.
Because I tried to set this specifically on the A1 and then the SAM and it seemed to cause conflicts... letting it fallback has to yet as to date... the old 'if it works and it ain't broken' leave it
And if I'm not correct G isn't actually a speed rating but a request to set each device at the best achieviable?
Thanks for your comments in anycase
~Yes I am a Kiwi, No, I did not appear as an extra in 'Lord of the Rings'~ 1x AmigaOne X5000 2.0GHz 2gM RadeonR9280X AOS4.x 3x AmigaOne X1000 1.8GHz 2gM RadeonHD7970 AOS4.x
And if I'm not correct G isn't actually a speed rating but a request to set each device at the best achieviable?
From Documentation/IDE/sii3114ide_dev.doc:
- sii3114ide_xfer
Allows to define the xfer mode which will be used for each drive. Compose
4 chars (prim master, prim slave, sec master, sec slave) using :
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)
G - UDMA 6 (133 MB/s, modeid 70)
NB : sii3114ide will fall back to the best mode that the drive claims to support
in case you ask for an unsupported mode.
Default : if you don't set this envvar, sii3114ide will use the best PIO mode
supported by the drive.
So G means explicitly set the highest UDMA mode, 70 (133 MB/s).
Of course, it probably won't harm anything, as the driver will just fall back to whatever the drive claims to support. But I usually prefer explicitly setting the mode which experiments and/or queries have identified as the best one for the drive in questions, since that reminds me and others of the fact that it was actually researched. Also, then I don't have to rely on the driver falling back to the correct mode and maybe getting it wrong (e.g. if the drive claims more than it can deliver, which I've heard is not uncommon for optical drives).
I've read the same documentation but I can see you're one of this people that like to be concise at all times...
I am not I'm generally very lazy in explaning myself or conveying the right order of things... I don't place much value on that and also, I am the king of being vague... It's so annoying speaking to someone and you make reference to something you were speaking of like 10 mins ago but they don't make the connection... but the way you word it how could they possibly NOT make the connection?
It takes all kinds of people I suppose
I am of course quite correct because there is no H and if you used F and your device could use G then it wouldn't use the best...
So G sets the best possible mode regardless of whether it accomplishes this via a fallback protocol... by design it fills this end
and I'm hungry
btw, your concerns about the device setting the speed wrong is probably because of any limitations with the IDE interface, surely with SATA we do not have to worry about the cables etc not handling TOP gear...
one last thing too, your posts are always helpful and in good faith so, continue being yourself I just wish there were more nbaches in the world of cpu forums
~Yes I am a Kiwi, No, I did not appear as an extra in 'Lord of the Rings'~ 1x AmigaOne X5000 2.0GHz 2gM RadeonR9280X AOS4.x 3x AmigaOne X1000 1.8GHz 2gM RadeonHD7970 AOS4.x
I've read the same documentation but I can see you're one of this people that like to be concise at all times...
Heh - guilty as charged . I generally find it saves time for myself when I find concise information, so I strive to give it in the same way.
Quote:
I am of course quite correct because there is no H and if you used F and your device could use G then it wouldn't use the best...
So G sets the best possible mode regardless of whether it accomplishes this via a fallback protocol... by design it fills this end
Yes - or rather by the coincidence of G currently being the highest UDMA mode designator, and of the fallback mechanism being in place. And again, only if we can assume that the drive always reports its capabilities correctly and conservatively (since the driver falls back to what the drive reports, not necessarily to what actually works reliably).
Quote:
btw, your concerns about the device setting the speed wrong is probably because of any limitations with the IDE interface, surely with SATA we do not have to worry about the cables etc not handling TOP gear...
You may be right, I don't have much expertise in that field. But I wouldn't have thought cabling was the main issue there, but rather cheap/buggy optical drives which may work at a certain speed given a certain hardware and OS (i.e. your average Win PC), but have never been tested in more exotic environments such as ours, and so they report the mode they have been seen working with.
Quote:
one last thing too, your posts are always helpful and in good faith so, continue being yourself I just wish there were more nbaches in the world of cpu forums
- If someone wants to add an harddrive on a Sam motherboard, if it is not recognized in Mediatoolbox directly, just set the 'sii3114ide_conf' variable to '1112' (assuming there is an optical device on the J23 connector),
For the speed of the devices : - For harddrives : the max speed will be obtain with the 'G' value in the 'sii3114ide_xfer' variable, - For optical drives, according to those I have tested : my advise is to set the 'sii3114ide_xfer' to 0 in order to let the motherboard using the best pio mode for this device.
I just precize that for optical drives, the SlimSata devices can cause some freeze when booting on the AmigaOS 4.1 CD if the 'sii3114ide_xfer' is set to G.
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
