Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-06-13 Thread Hor Jiun Shyong

On 06/11/2012 06:01 AM, Issam Mehssani wrote:


I believe the problem comes from an incompatibility between FGLRX 
version 12-4-1 and xorg 1.12.
I've had the same symptoms and solved it by downgrading xorg to 
1.11.4-1. Make sure to downgrade the input packages too.



Thanks for the feedback. Will try out and feedback the result.

--
Regards,
Hor Jiun Shyong 何俊雄

Blog: jiunshyong.dyndns.org
twitter.com/jiunshyong
facebook.com/jiunshyong

I'm an FSF member -- Help us support software freedom! 
http://www.fsf.org/jf?referrer=2442

Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce 
Lee.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4fd92aeb.6010...@gmail.com



[SOLVED] Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-06-13 Thread Hor Jiun Shyong




I believe the problem comes from an incompatibility between FGLRX 
version 12-4-1 and xorg 1.12.
I've had the same symptoms and solved it by downgrading xorg to 
1.11.4-1. Make sure to downgrade the input packages too.



Thanks for the feedback. Will try out and feedback the result.



Hi Issam,

I have downgraded core xorg files to 1.11.4-1 and xorg input files to 
lower versions matching the 1.11.4-1 release dates.


xserver-xorg-core_2%3a1.11.4-1_amd64.deb
xserver-common_2%3a1.11.4-1_all.deb
xserver-xorg-dev_2%3a1.11.4-1_amd64.deb

xorg_1%3a7.6+12_amd64.deb
xorg-dev_1%3a7.6+12_all.deb
xserver-xorg_1%3a7.6+12_amd64.deb

xserver-xorg-input-all_1%3a7.6+12_amd64.deb
xserver-xorg-input-evdev_1%3a2.7.0-1_amd64.deb
xserver-xorg-input-synaptics_1.5.99.901-1_amd64.deb
xserver-xorg-input-wacom_0.12.0-1_amd64.deb


This is followed with a install of 
amd-driver-installer-12-4-x86.x86_64.run .Success:  got my my gdm3 
in standard mode.


Thanks again.



--
Regards,
Hor Jiun Shyong 何俊雄

Blog: jiunshyong.dyndns.org
twitter.com/jiunshyong
facebook.com/jiunshyong

I'm an FSF member -- Help us support software freedom! 
http://www.fsf.org/jf?referrer=2442

Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce 
Lee.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4fd94529.6000...@gmail.com



Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-06-10 Thread Issam Mehssani
Hi,

I believe the problem comes from an incompatibility between FGLRX version
12-4-1 and xorg 1.12.
I've had the same symptoms and solved it by downgrading xorg to 1.11.4-1.
Make sure to downgrade the input packages too.


Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-05-23 Thread Hor Jiun Shyong

Hi,

Is this bug (Bug#665000: SUMO2: blank screen after load radeon module) 
related to my issue? As I am using Sumo chip too AMD Llano A6-3670 APU 
with Radeon(tm) HD Graphics stepping 00


root@szechuan:~#: dmesg | grep -i sumo
[ 7.451590] [drm] initializing kernel modesetting (SUMO 0x1002:0x964A 
0x1043:0x84C8).

[ 7.453403] [drm] Loading SUMO Microcode


Thanks.








On 05/21/2012 10:52 PM, Chris Bannister wrote:

On Mon, May 21, 2012 at 09:27:32AM +0800, Hor Jiun Shyong wrote:

grep -v \^# /etc/inittab

[output same as mine]

Can't see anything different there.




--
Regards,
Jiun Shyong 俊雄

Blog: jiunshyong.dyndns.org
twitter.com/jiunshyong
facebook.com/jiunshyong
Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce 
Lee.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4fbc9e62.8020...@gmail.com



Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-05-21 Thread Chris Bannister
On Mon, May 21, 2012 at 09:27:32AM +0800, Hor Jiun Shyong wrote:
 grep -v \^# /etc/inittab

[output same as mine]

Can't see anything different there.

-- 
If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing. --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120521145255.GE24726@tal



Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-05-20 Thread Chris Bannister
On Thu, May 17, 2012 at 11:37:54AM +0800, Hor Jiun Shyong wrote:
 I checked and noticed the default runlevel under inittab is 5.  (I
 must have changed it for reason I can't remember now).I have
 changed it back to run level 2 and will try the ati driver again to
 see if the problem still persists.  Thanks.

What is output of:
head -n 21 /etc/inittab

-- 
If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing. --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120520133459.GN31474@tal



Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-05-20 Thread Chris Bannister
On Mon, May 21, 2012 at 01:34:59AM +1200, Chris Bannister wrote:
 On Thu, May 17, 2012 at 11:37:54AM +0800, Hor Jiun Shyong wrote:
  I checked and noticed the default runlevel under inittab is 5.  (I
  must have changed it for reason I can't remember now).I have
  changed it back to run level 2 and will try the ati driver again to
  see if the problem still persists.  Thanks.
 
 What is output of:
 head -n 21 /etc/inittab

Actually, better would be:
What is output of:
grep -v \^# /etc/inittab

-- 
If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing. --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120520154012.GA7988@tal



Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-05-20 Thread Hor Jiun Shyong

grep -v \^# /etc/inittab


id:2:initdefault:

si::sysinit:/etc/init.d/rcS

~~:S:wait:/sbin/sulogin


l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
z6:6:respawn:/sbin/sulogin

ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now


pf::powerwait:/etc/init.d/powerfail start
pn::powerfailnow:/etc/init.d/powerfail now
po::powerokwait:/etc/init.d/powerfail stop

1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6


On 05/20/2012 11:40 PM, Chris Bannister wrote:

On Mon, May 21, 2012 at 01:34:59AM +1200, Chris Bannister wrote:

On Thu, May 17, 2012 at 11:37:54AM +0800, Hor Jiun Shyong wrote:

I checked and noticed the default runlevel under inittab is 5.  (I
must have changed it for reason I can't remember now).I have
changed it back to run level 2 and will try the ati driver again to
see if the problem still persists.  Thanks.

What is output of:
head -n 21 /etc/inittab





--
Regards,
Jiun Shyong 俊雄

Blog: jiunshyong.dyndns.org
twitter.com/jiunshyong
facebook.com/jiunshyong
Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce 
Lee.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4fb99a04.1030...@gmail.com



Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-05-18 Thread Arnt Karlsen
On Thu, 17 May 2012 12:14:01 +0800, Hor wrote in message 
4fb47b09.9080...@gmail.com:

 Is amd-driver-installer-12-4-x86.x86_64.run  driver the same with the 
 non free debianised fglrx driver ?  
 amd-driver-installer-12-4-x86.x86_64.run uses fglrx version 8.961

..I dunno, I only use the free|open source X drivers.  Guys?

 lspci result under amd-driver-installer-12-4-x86.x86_64.run  driver:

..guys, this below is, or is not normal with fglrx???

 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
 Stepping- SERR- FastB2B- DisINTx-
 00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee
 ATI BeaverCreek [Radeon HD 6530D] (prog-if 00 [VGA controller])
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx+
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx+
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop+
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B-
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx+
  BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B-
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx+
  BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B-
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx+
  BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B-
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx+
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx+
 
 
 


-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120518152029.4bd28...@celsius.lan



Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-05-16 Thread Arnt Karlsen
On Tue, 15 May 2012 21:03:12 +0800, Hor wrote in message 
4fb25410.5050...@gmail.com:

 Hi All,
 
 Would be grateful if anyone could provide feedback on the below,
 thanks.
 
 After installing proprietary driver 
 amd-driver-installer-12-4-x86.x86_64.run on Sid amd64, both console
 and X cannot be started. All was left after booting is a blinking - 
 prompt. 

..this isn't a kernel panic?  
What happens _immediately_before_ your blinking dash?

 Xorg log as below.

..this is relevant only if it was written between your boot and your
blinking dash.

 I then ssh into this pc from another and removed this driver. Managed
 to get gnome 3 back but under fallback mode. Previously was able to
 be on gnome3 standard mode.

..your Xorg log is gnome 3 under fallback mode?

 package: Linux 3.2.0-2-amd64 x86_64 Debian
 version: 3.2.17-1
 
 package: xserver-xorg-core:
 version: 2:1.12.1-2
 
 package: xorg-server
 version: 1:7.6+13
 
 package: fglrx-driver
 version: 1:12-4-1

..first things first: Does this fglrx driver even support 
your card?

..please post your output of: 'lspci |grep VGA '.
If that shows an ATI card, we will probably want 
to see your dmesg.


..what happens if you try use the ati driver instead?

-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120516133246.774c6...@celsius.lan



Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-05-16 Thread Hor Jiun Shyong

Hi,


..this isn't a kernel panic?
What happens _immediately_before_ your blinking dash?


Kernel is able to boot up.





..this is relevant only if it was written between your boot and your
blinking dash.

Yes it is so.






..your Xorg log is gnome 3 under fallback mode? 


Yes






..first things first: Does this fglrx driver even support
your card?

..please post your output of: 'lspci |grep VGA '.
If that shows an ATI card, we will probably want
to see your dmesg.


..what happens if you try use the ati driver instead?



fglrx driver.   I will post the lspci result under ati driver in another 
email.  Thanks. Jiun Shyong


lspci -vv | grep VGA
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI 
BeaverCreek [Radeon HD 6530D] (prog-if 00 [VGA controller])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop+ ParErr- 
Stepping- SERR- FastB2B- DisINTx-

BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+

BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+

BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+

BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+





--
Regards,
Jiun Shyong 俊雄

Blog: jiunshyong.dyndns.org
twitter.com/jiunshyong
facebook.com/jiunshyong
Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce 
Lee.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4fb47148.6090...@gmail.com



Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-05-16 Thread Hor Jiun Shyong

On 05/16/2012 01:23 AM, Indulekha wrote:

Maybe something (like /etc/inittab) got edited, and tty7
was repurposed for a getty? It's important to leave tty7
alone or X won't run.


Also if inittab did get edited, could be you're calling a getty
that isn't installed...





I checked and noticed the default runlevel under inittab is 5.  (I must 
have changed it for reason I can't remember now).I have changed it 
back to run level 2 and will try the ati driver again to see if the 
problem still persists.  Thanks.



--
Regards,
Jiun Shyong 俊雄

Blog: jiunshyong.dyndns.org
twitter.com/jiunshyong
facebook.com/jiunshyong
Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce 
Lee.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4fb47292.40...@gmail.com



Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-05-16 Thread Hor Jiun Shyong
Is amd-driver-installer-12-4-x86.x86_64.run  driver the same with the 
non free debianised fglrx driver ?  
amd-driver-installer-12-4-x86.x86_64.run uses fglrx version 8.961



lspci result under amd-driver-installer-12-4-x86.x86_64.run  driver:

Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI 
BeaverCreek [Radeon HD 6530D] (prog-if 00 [VGA controller])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop+ ParErr- 
Stepping- SERR- FastB2B- DisINTx-

BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+

BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+

BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+

BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+




--
Regards,
Jiun Shyong 俊雄

Blog: jiunshyong.dyndns.org
twitter.com/jiunshyong
facebook.com/jiunshyong
Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce 
Lee.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4fb47b09.9080...@gmail.com



Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-05-15 Thread Hor Jiun Shyong
[ 312.759] ABI class: X.Org Server Extension, version 6.0
[ 312.759] (II) Loading extension RECORD
[ 312.759] (II) LoadModule: dri
[ 312.759] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 312.759] (II) Module dri: vendor=X.Org Foundation
[ 312.759] compiled for 1.12.1, module version = 1.0.0
[ 312.759] ABI class: X.Org Server Extension, version 6.0
[ 312.759] (II) Loading extension XFree86-DRI
[ 312.759] (II) LoadModule: dri2
[ 312.759] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 312.759] (II) Module dri2: vendor=X.Org Foundation
[ 312.759] compiled for 1.12.1, module version = 1.2.0
[ 312.759] ABI class: X.Org Server Extension, version 6.0
[ 312.759] (II) Loading extension DRI2
[ 312.759] (II) LoadModule: fglrx
[ 312.759] (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
[ 312.881] (II) Module fglrx: vendor=FireGL - ATI Technologies Inc.
[ 312.881] compiled for 1.4.99.906, module version = 8.96.4
[ 312.881] Module class: X.Org Video Driver
[ 312.881] (II) Loading sub module fglrxdrm
[ 312.881] (II) LoadModule: fglrxdrm
[ 312.881] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
[ 312.881] (II) Module fglrxdrm: vendor=FireGL - ATI Technologies Inc.
[ 312.881] compiled for 1.4.99.906, module version = 8.96.4
[ 312.881] (II) ATI Proprietary Linux Driver Version Identifier:8.96.4
[ 312.881] (II) ATI Proprietary Linux Driver Release Identifier: 8.961
[ 312.881] (II) ATI Proprietary Linux Driver Build Date: Apr 5 2012 
23:06:21

[ 312.888]
Fatal server error:
[ 312.888] xf86OpenConsole: Cannot find a free VT
[ 312.888]
[ 312.888]

--
Regards,
Jiun Shyong ??

Blog: jiunshyong.dyndns.org
twitter.com/jiunshyong
facebook.com/jiunshyong
Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce 
Lee.



Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-05-15 Thread Camaleón
On Tue, 15 May 2012 21:03:12 +0800, Hor Jiun Shyong wrote:

 Hi All,

Hi... but there's no need to send this twice and please, no html posts :-)

 Would be grateful if anyone could provide feedback on the below, thanks.

Okay, let's see if I can give you some hints. There are usually X gurus 
around the list but let's do some tests until they can provide a more 
insightful view on this issue :-)

 After installing proprietary driver
 amd-driver-installer-12-4-x86.x86_64.run on Sid amd64, both console and
 X cannot be started. All was left after booting is a blinking -
 prompt. Xorg log as below.

Let me move up the fatal error:

 [ 312.888] Fatal server error:
 [ 312.888] xf86OpenConsole: Cannot find a free VT 
 [ 312.888]
 [ 312.888]

That's weird... It's like the xserver is not able to allocate a virtual 
console where to start X but I can't figure out what could be causing 
this :-?

 I then ssh into this pc from another and removed this driver. Managed to
 get gnome 3 back but under fallback mode. Previously was able to be on
 gnome3 standard mode.

(...)

If gnome-shell cannot be started it usually means a problem regarding the 
3D capabilities of the VGA driver (take a look at your ~/.xession-
errors file). And what's the full X log now that you are using Debian 
stock ATI closed driver?

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jou1pj$tg8$1...@dough.gmane.org



Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-05-15 Thread Indulekha
On Tue, May 15, 2012 at 04:55:15PM +, Camaleón wrote:
 On Tue, 15 May 2012 21:03:12 +0800, Hor Jiun Shyong wrote:
 
  Hi All,
 
 Hi... but there's no need to send this twice and please, no html posts :-)
 
  Would be grateful if anyone could provide feedback on the below, thanks.
 
 Okay, let's see if I can give you some hints. There are usually X gurus 
 around the list but let's do some tests until they can provide a more 
 insightful view on this issue :-)
 
  After installing proprietary driver
  amd-driver-installer-12-4-x86.x86_64.run on Sid amd64, both console and
  X cannot be started. All was left after booting is a blinking -
  prompt. Xorg log as below.
 
 Let me move up the fatal error:
 
  [ 312.888] Fatal server error:
  [ 312.888] xf86OpenConsole: Cannot find a free VT 
  [ 312.888]
  [ 312.888]
 
 That's weird... It's like the xserver is not able to allocate a virtual 
 console where to start X but I can't figure out what could be causing 
 this :-?
 

Maybe something (like /etc/inittab) got edited, and tty7 
was repurposed for a getty? It's important to leave tty7 
alone or X won't run.

-- 
❤ ♫ ❤ ♫ ❤ ♫ ❤   
 Indulekha 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120515170158.GB4098@radhesyama



Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-05-15 Thread Indulekha
On Tue, May 15, 2012 at 12:01:58PM -0500, Indulekha wrote:
 On Tue, May 15, 2012 at 04:55:15PM +, Camaleón wrote:
  On Tue, 15 May 2012 21:03:12 +0800, Hor Jiun Shyong wrote:
  
   Hi All,
  
  Hi... but there's no need to send this twice and please, no html posts :-)
  
   Would be grateful if anyone could provide feedback on the below, thanks.
  
  Okay, let's see if I can give you some hints. There are usually X gurus 
  around the list but let's do some tests until they can provide a more 
  insightful view on this issue :-)
  
   After installing proprietary driver
   amd-driver-installer-12-4-x86.x86_64.run on Sid amd64, both console and
   X cannot be started. All was left after booting is a blinking -
   prompt. Xorg log as below.
  
  Let me move up the fatal error:
  
   [ 312.888] Fatal server error:
   [ 312.888] xf86OpenConsole: Cannot find a free VT 
   [ 312.888]
   [ 312.888]
  
  That's weird... It's like the xserver is not able to allocate a virtual 
  console where to start X but I can't figure out what could be causing 
  this :-?
  
 
 Maybe something (like /etc/inittab) got edited, and tty7 
 was repurposed for a getty? It's important to leave tty7 
 alone or X won't run.


Also if inittab did get edited, could be you're calling a getty 
that isn't installed... 

-- 
❤ ♫ ❤ ♫ ❤ ♫ ❤   
 Indulekha 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120515172345.GA4792@radhesyama



Fatal server error: xf86OpenConsole: Cannot find a free VT

2012-05-14 Thread Hor Jiun Shyong
[ 312.759] ABI class: X.Org Server Extension, version 6.0
[ 312.759] (II) Loading extension RECORD
[ 312.759] (II) LoadModule: dri
[ 312.759] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 312.759] (II) Module dri: vendor=X.Org Foundation
[ 312.759] compiled for 1.12.1, module version = 1.0.0
[ 312.759] ABI class: X.Org Server Extension, version 6.0
[ 312.759] (II) Loading extension XFree86-DRI
[ 312.759] (II) LoadModule: dri2
[ 312.759] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 312.759] (II) Module dri2: vendor=X.Org Foundation
[ 312.759] compiled for 1.12.1, module version = 1.2.0
[ 312.759] ABI class: X.Org Server Extension, version 6.0
[ 312.759] (II) Loading extension DRI2
[ 312.759] (II) LoadModule: fglrx
[ 312.759] (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
[ 312.881] (II) Module fglrx: vendor=FireGL - ATI Technologies Inc.
[ 312.881] compiled for 1.4.99.906, module version = 8.96.4
[ 312.881] Module class: X.Org Video Driver
[ 312.881] (II) Loading sub module fglrxdrm
[ 312.881] (II) LoadModule: fglrxdrm
[ 312.881] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
[ 312.881] (II) Module fglrxdrm: vendor=FireGL - ATI Technologies Inc.
[ 312.881] compiled for 1.4.99.906, module version = 8.96.4
[ 312.881] (II) ATI Proprietary Linux Driver Version Identifier:8.96.4
[ 312.881] (II) ATI Proprietary Linux Driver Release Identifier: 8.961
[ 312.881] (II) ATI Proprietary Linux Driver Build Date: Apr 5 2012 23:06:21
[ 312.888]
Fatal server error:
[ 312.888] xf86OpenConsole: Cannot find a free VT
[ 312.888]
[ 312.888]
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.

--
Regards,
Jiun Shyong 俊雄

Blog: jiunshyong.dyndns.org
twitter.com/jiunshyong
facebook.com/jiunshyong
Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce 
Lee.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4fb1000f.2040...@gmail.com