Hi nice folks
Like the good little forum person I am, I've had a hunt and not found an answer here, and a general Google finds answers elsewhere that don't quite fit. So...
Brand new puter, bought for my father (85) -- as all he really needs is a bit of word processing and the net, I thought this dirt cheap one would do:
AMD Llano Dual Core 2.5GHz Processor
4GB Patriot DDR3 1333MHz Memory
AMD Radeon HD 6530D Graphics
(Isn't it amazing what you can get for the money these days? His last one, in 2005, was near-bottom of the range too, and cost £599.)
Not sure what flavour of BIOS it has -- we're now at the outer edges of my knowledge -- but I think it's a Gigabyte motherboard, if that helps. (It either will, or it'll show you how little I really know )
No other operating systems on it. So, it's a fresh, blank machine, and it's had an overnight memtest.
This morning, I popped the Mint 12 Lisa DVD into the drive. The disc has done its job fine on my own machine.
Boot from disc, Enter.
Initial Mint 12 screen appears, causing that mix of excitement and sigh of happy relief, knowing you're about to be off into the safe and carefree world of Windows-less computing. (Well, till something goes wrong, and you find that you've got to bash your bin or whatever )
Then the monitor goes black but for a 'No signal detected' message, and then just black.
The disc continues to whirr away in the drive, and presumably all's going well -- apart from there being no way to know what it's up to, or when any input from me might be required.
Rinse, repeat, same result.
Okay, so in some way the monitor isn't receiving the info it needs in the right way, and so it gets all huffy and goes to sleep.
So, what to do?
I doubt it's a driver issue, both since the initial Lisa boot screen displays fine and because it's Lisa, which I'm assuming will have everything needed to run on a new machine. (Plus, I've no idea what make the monitor is without upending it -- nothing on the front at all, and my dad seems to have lost all the documentation. I'm now at work and can't check the back right now either. So hoping that it doesn't matter!)
So, it's... something to do with the... um... settings in the BIOS...?
At which point, I'm lost. Though I've done odds and ends in BIOSes before, it's been boot order, fan speeds, and so on. I've never spotted anything to do with displays. And have no idea what I would need to change -- and to what -- anyway.