Just a quick and dirty video of my mini-itx SAM440ep.
I have had it since 2008 and never really used it as I have been too busy doing other stuff.
So my knowledge of the hardware and especially OS4.1 is rather weak.
The board is a SAM440ep at 666MHz, year: 2008-09 with 512MB, onboard Radeon M9, SATA 24x DVD-RW and the award winning OCZ 60GB Agility 3 SSD SATA 3. There are no moving parts and it's absolutely silent!
I have been playing with it more and more in the last few weeks as some friends of mine wanted to know more about it and possibly going back to Amiga.
So I have assembled the fastest SAM440ep configuration I could possibly come up with and shot a couple of videos for fun.
Sorry about the quality, the video was taken at night and without any recording software just a camera pointing at my 24" monitor.
After finishing the build I have to say I am very impressed with this tiny machine.
Well it can be boring for people who know about the Amiga and OS4.1 but to a newcomer or an old Amigan then it's, I hope, interesting. My friend was really impressed and he used to have an A1200 with 4MB Fast. He didn't even know that Amiga, nowadays, can run videos.
I love when the OS gets installed from 1:38...the second bar flies (writing to the SSD).
Perhaps a suggestion for youre next one, maybe you can show the SAM browsing more common sites such as the BBC or eBay? Maybe a voice-ver commentary too?
Keep em coming! This is great for awareness of the platform!
nothing special, I have only got back into OS4.1 recently, the SAM I got with OS4.1 CD in 2008 has been sitting on my bench for three years (I have been working on my A500 inspired case for it) so I decided to mess about with it.
The addition of an OCZ Agility 3 SATA III 60GB SSD is scary!
It makes my 7200 rpm HDD feel useless, booting and opening windows is fast and it's a SATA 3 SSD on SATA 1 controller, if we had a SATA 3 controller even in PCI mode I am sure it would cut the times in half!
Shame I haven't got proper recording software and had to do everything with a camera at one metre distance
@TheDaddy Regarding DMA, you can check whether it is enabled using one of these two Shell commands: IDETool -l sii3114ide.device NVGetVar sii3114ide_xfer
And you can permanently enable it using this one: NVSetVar sii3114ide_xfer GGGG
If you have problems, then you can disable it again using: NVSetVar sii3114ide_xfer 0000 (something similar can also be done from Uboot, should OS4 not boot for some reason, but we'll cross that bridge if we come to it)
What do I have to look for to see if it's enabled after typing those lines?
These are the results:
Flags : $000001C5 - present, supports DMA, ATA, supports power 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 12 (PIO 4, 16 MB/s)
I know you already got your answer off-thread, but for the benefit of any future readers searching for the answer:
The line with the transfer mode info is the interesting one. It tells you that your drive can do PIO mode 4 max or UDMA mode 6 max, and that it is currently set to do PIO 4. So the solution would be to change it to do UDMA mode 6 by setting the sii3114ide_xfer UBoot variable to something with a G (upper case) in the corresponding position. More info in the sii3114ide_dev.doc.
Thanks everyone and thanks Niels, I'll do some more reading.
So from what I gather my machine was set to PIO4 and could do DMA 70 (UDMA 6, 133MB/s) but by inputting this line (I have done it in a shell in Workbench):
So from what I gather my machine was set to PIO4 and could do DMA 70 (UDMA 6, 133MB/s) but by inputting this line (I have done it in a shell in Workbench):
NVSetVar sii3114ide_xfer GGGG
I have changed it to DMA 70 (UDMA 6/ 133MB/sec)
Correct?
Yes.
Quote:
The same can be done via UBoot?
Yes, in fact NVSetVar does exactly the same as a setenv (followed by a saveenv) would do on the UBoot command line. But if you mean through the UBoot menu system, then no, I don't believe it can be done there. The UBoot env variables for the IDE (SCSI/SATA) drivers are a bit special, because although they are set as part of UBoot's variables, they are not used (or known) by UBoot, only by the OS once booted. But they are needed very early in the boot process, when a normal AmigaOS ENV: variable would not be available yet, which is why the other method was used.