I had to make internal alterations to the PC; new usb 3 adapter card, new fans now running off the mobo, different connections used from the psu, etc, etc.
All seems to have gone smoothly enough except I can’t get to the desktop and am dropped to the emergency console screen. I can boot into the desktop using Recovery Mode and I know it’s recognised the new usb 3 adapter card because I can use it. I’ve disturbed something but don’t know exactly what. Any ideas?
Thanks.
Sounds like video but could be something else. You change the video adapter card?
No, but I took it out and cleaned it!
Try resetting it
I’ve shutdown, removed the power cable and re-seated the card and still get the same.
Some older cards require an extra power connection??? What card? I used to always forget to reconnect that one 
But I don’t think the machine would boot in that case.
Remove the new card and try. Also what type of video card motherboard connector be sure it is in a slot closest to the cpu.
Does everything work when you boot into windows?
aye, all fine there…
it’s an older HD5770 series card so I can still use normal fglrx, but it turns out if you remove the new usb 3 card out of the pcie x1 slot into the pcie x16 slot then the bugger works. PITA. What’s that all about??
Timing is everything. PCI bus can be picky and one card must have been stepping on the signal of the other.
I’ll have to move things around again to get what I want re space / cable management etc, at a later date, it works fine for now though. Thanks for the second pair of eyes. :good:
On 2014-12-18 22:36, david banner wrote:
> it’s an older HD5770 series card so I can still use normal fglrx, but it
> turns out if you remove the new usb 3 card out of the pcie x1 slot into
> the pcie x16 slot then the bugger works. PITA. What’s that all about??
Surely there are error messages and logs.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Probably, if you know the exact log you want and it’s location and / or know the commands to type off the top of your head from the emergency console. It was easier to just take the cards out and swap them around and do it by trial and error. Could only have been a small handful of possibilities really.
On 2014-12-19 16:06, david banner wrote:
>
> Probably, if you know the exact log you want and it’s location and / or
> know the commands to type off the top of your head from the emergency
> console. It was easier to just take the cards out and swap them around
> and do it by trial and error. Could only have been a small handful of
> possibilities really.
Well, the typical reason is a failed fsck or wrong fstab. And with
systemv you had the reason right above the prompt. With systemd the
information got lost.
The logs to look could be /var/log/boot.* and /var/log/messages.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)