SOLVED: Installation to hdd snag

[towo]

Trinity APU is not propper supportet by free drivers at the moment.
So the only chance is installing fglrx (i would use the 13.3~beta3 from our experimental repo) after booting to runlevel 3.

[grady]

@towo:
Thank you for your helpful reply.
I conform with the debian/Stallman free-software ethic- with a few exceptions: e.g.C.M.'s site.

I had some suspicion when I was installing that I'd need non-free; and so I enabled it.
In this case, my choices appear to be:
-dump debian, install Windows; but the object is a siduction box!
-store the equipment for months 'til free software catches up,
-go non-free.
 So I elect to go non-free.

From my reading, non-free (perhaps experimental only?) supports my card with some acceptable faults. Is that your understanding, towo?
grady

[towo]

I don't understand your problem.
You have 2 possibilities

1st, install firmware-linux-nonfree and look, if our recent kernel is supporting your device for your needs.
2nd, install fglrx and hpe, that it work.

[grady]

SOLVED: The solution came in two stages.

I first (using gparted) improved my partitioning advised above. And then reinstalled.

The major snag then presented: no screen when the OS on hdd was booted. A profi friend (who has been running siduction for a few months) after some trial-and-error, finally fixed that.

Piper's suggested grub argument did work!

Code Select Expand

radeon.modeset+0
But only like so:

Code Select Expand

radeon.modeset=0 init=3

That was the "Sesam öffne dich!"
Everything else was simple: a dist-upgrade and getting/installing the files suggested by towo.

Siduction, the beta graphics driver, and the hardware components are working together very well.
FM2 socket was chosen because AMD are saying they expect to retain FM2 through at least one more iteration. And there's a lot of potential for overclocking the mobo, cpu, and the Mushkin ram. The only used parts are a good quality 500w PSU and SyncMaster 2233 monitor.

Thank you all for your kind advice.

grady

[michaa7]

"+0" was wrong, "=0" is right, but "init=3" (if not used temporarily) will boot the  computer to the terminal each time!

Nice you got your problem fixed.

[grady]

@michaa7:

Thank you, once again, for that helpful clarification. I'd hate to lead anyone astray.
My guru must have gone back later and removed the "init=3" argument while my back was turned.
Alles ist in ordnung.

grady