Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 467732 - x11-drivers/ati-drivers-13.4 looses VT console mode
Summary: x11-drivers/ati-drivers-13.4 looses VT console mode
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: AMD64 Linux
: Normal normal with 2 votes (vote)
Assignee: Gentoo X packagers
URL: http://phoronix.com/forums/showthread...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-28 12:18 UTC by ChaosEngine
Modified: 2014-01-28 09:48 UTC (History)
6 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ChaosEngine 2013-04-28 12:18:34 UTC
After upgrade to 13.4 there is no VT console mode (plain text console, no FB). Switchinf with Ctrl+Alt-F1-F6 does not show nothing. F7 properly switches to xdm and Xorg session.
Downgrading to <=ati-drivers=13.3_beta3 fixes the issue

Reproducible: Always

Steps to Reproduce:
1.upgrade to x11-drivers/ati-drivers-13.4
2. try to from xdm or Xorg session to VT by Ctrl+Alt-F1-F6
3. no login session in VT displayed
Actual Results:  
no VT login propmt appear, no display!

Expected Results:  
VT login propmpt visible

when on 13.1 and 13.3* issue was not found. Also /var/log/Xor.0.log shows:
[    15.261] (II) fglrx(0): AC Adapter is used
[    15.261] (EE) fglrx(0): Failed to get ConsoleMode
[    15.261] (II) fglrx(0): AMD Video BIOS revision 9 or later detected

and /var/log/messages:
Apr 28 13:43:02 notebook3 kernel: [   15.343317] <3>[fglrx:firegl_get_console_mode_info] *ERROR* Get Console Mode failed
Comment 1 Dennis Schridde 2013-05-09 11:34:32 UTC
I confirm the issue.
Comment 2 Marius Caldas 2013-05-13 14:53:49 UTC
I can confirm this issue as well on two different setups:

 1 - An Intel Xeon system with an AMD 6760
 2 - An AMD FX-8350 system with thwo 7970's

In another system, an AMD Athlon X2 with an AMD 6760 PCIe card, this issue does not appear. Very odd.
Comment 3 ChaosEngine 2013-05-13 15:02:26 UTC
AFAIR under x11-drivers/ati-drivers-13.3_beta3 I haven't had the issue. Not sure though :-/
Comment 4 Marius Caldas 2013-05-13 18:28:24 UTC
I found this in the kernel log:

[fglrx:firegl_get_console_mode_info] *ERROR* Get Console Mode failed
Comment 5 ChaosEngine 2013-05-13 22:31:14 UTC
Marius, are there any specific differences between config of the bad and good machine? Of course without going too deep in it :-)
Comment 6 Dennis Schridde 2013-05-14 09:36:17 UTC
(In reply to comment #5)
> Marius, are there any specific differences between config of the bad and
> good machine? Of course without going too deep in it :-)

Maybe this is helpful: http://ati.cchtml.com/show_bug.cgi?id=741#c3

See also:
http://ati.cchtml.com/show_bug.cgi?id=741
http://ati.cchtml.com/show_bug.cgi?id=783
http://ati.cchtml.com/show_bug.cgi?id=784
Comment 7 Marius Caldas 2013-05-15 11:59:39 UTC
@ChaosEngine,

Well yes there are several differences but the most relevant perhaps are the kernel versions:

 1 - An Intel Xeon system with an AMD 6760 - Kernel 3.9.1-pf
 2 - An AMD FX-8350 system with thwo 7970's - Kernel 3.8.2-pf
 3 - An AMD Athlon X2 with an AMD 6760 - Kernel 3.3.1-gentoo

The last system is an embedded target at work. Looking at the links above that Dennis posted, I'm starting to believe it could be EFI related. The first two systems have UEFI, the third does not. I did enable the runtime EFI support in the kernel for the first two systems. Let me know if the specific kernel configs could be of any help.

Thanks,
 - Marius
Comment 8 Marius Caldas 2013-05-15 13:04:41 UTC
I just turned off the runtime EFI support on system #1's kernel above (the Xeon system), and voila', I have VT's again. I really need the VT's, but I don't need EFI support for now, so this work around is enough for me. But I guess this is something that still has to be looked at by upstream.
Comment 9 Navar 2013-07-04 19:55:03 UTC
I can confirm on AMD 7850 with Intel i5-3570K going from 13.1 (unaffected) to 13.4, gentoo sources kernel 3.8.13.
Comment 10 Simon Matthews 2013-08-14 15:00:03 UTC
I am also seeing this problem. 

Linux newhome 3.8.13-gentoo #4 SMP PREEMPT Sun Aug 4 12:39:06 PDT 2013 x86_64 AMD A6-3500 APU with Radeon(tm) HD Graphics AuthenticAMD GNU/Linux

x11-drivers/ati-drivers-13.4:1

One other (possibly related) issue: if I reboot but don't log in, the screen goes blank and is never restored, irrespective of what key I hit. If I log in quickly after the reboot, the screen is normal (not blank)

In either case (log in or not), I when I switch to a virtual terminal, it is blank.
Comment 11 Cliff 2013-09-07 01:48:36 UTC
I want to report similar issues with Aspire 7745g.

CPU: i7 Q720
Video: ATI 5650HD

Any >13.1 i will produce a black screen caused by a seg fault, so I have to use  kernel 3.8 with atidrivers-13.1.

The curious thing is that i couldn't switch VT console before (same black screen) and only F7 worked so maybe my config have worsened the issue. Not even F7 works with any >13.1 .

Xorg file: http://pastebin.com/Yp2AP9j6
Comment 12 Dennis Schridde 2013-09-07 09:45:03 UTC
(In reply to Cliff from comment #11)
> Xorg file: http://pastebin.com/Yp2AP9j6

Please do not pastebin anything for bugreports - use bugzilla attachments instead.
Comment 13 Austin S. Hemmelgarn 2013-09-09 13:50:09 UTC
I can confirm with a Radeon HD 5450 on gentoo-sources-3.11.
When booting without EFI enabled in the kernel, or booting through legacy BIOS with EFI enabled in the kernel, the problem appears to be resolved.

I don't know if this helps or not, but this particular system has no integrated graphics on the motherboard, just the Radeon PCI Express card.
Comment 14 Navar 2013-10-06 19:38:51 UTC
This seems resolved for me with 13.9 release and gentoo sources kernel 3.10.7-r1 on a Gigabyte Z77X-UD5H motherboard with AMD 7850.  I haven't changed any BIOS/EFI related settings since comment #9.
Comment 15 Sergey Popov gentoo-dev 2014-01-28 09:48:40 UTC
Closing per last comment. Feel free to reopen if this issue still happens