well, i guess every amigaone owner got his own experience with the "amigaohne" (german word play "amigawithout"),
so here is mine
putting the thing together was quiet easy, ist just a normal atx board.
on first poweron everything was fine. the machine was running without any signs of a hardware problem.
the first thing i did notice was that it did not find my scsi controller.
its a symbios 53c8xx based card, so it should have worked.
unfourtunatly the pci device adress for scsi is a fixed value with the current amigaone bios (uboot), but this is going to be "fixed".
so i got myself some aged ide harddrive and 1 ide dvdrom to get the thing to run something at all.
unlucky me had decided to go for a radeon 9100, that made the graphical interface (xserver) impossible to run, if you are not connected to the internet (unless you can happily go through a massive dependency tree).
well, 2 weeks later i got online and had the thing running.
if i tryed to start a browser it was crashing, pretty much strange i thought, but it was due to irq problems. took me just some days to find out, hey i was used to amigas and never taken care of irqs.
the browser was about to use sound and my soundcard was on the same irq as usb and network or was it with via stuff together?... cant remeber.
as i did try to enable dma for ide devices i had to reinstall linux thereafter, but thats probably not a bug in hardware, but my over 10 years old ide harddrive which doesnt seem to be dma capable
still i was not happy, the mouse was connected to usb and running very unsmooth, replaced by a ps2 mouse later, made me change my mind about the xservers performance as well, linux did feel much better then.
so now i have my linux running nicely, scsi works with the kernel from the amigaone linux page and still i have strange things happening.
few days ago i found out the memory has biterrors, even tho i ordered it with the amigaone from my dealer, looks like im unlucky again and have to send the ram back in for a replacement. these simple memtesters in the linux pool didnt find the errors when i did the test some time ago, so i was about to blame the board, but i got prof it has to be the mem later then.
besides i had no clue of linux at the start, that made things like installing etc a very time consuming process for me, as i had to read like a maniac all the time how to do these and how to do that, this made me feel like a total computer newbie
so this is what you get if you give some clueless german pc style hardware and a linux
at first i did blame linux, then i did blame the board, now i do stick to blame myself for not recognising the signs of bad memory.
(or maybe i blame kingston, yeah thats good
)