| View previous topic :: View next topic |
| Author |
Message |
nielchiano
Veteran
Joined: 11 Nov 2003
Posts: 1287
Location: 50N 3E
|
 Posted: Thu Jun 21, 2007 4:29 pm Post subject: ATI X1650 (fglrx) won't come back from text mode |
 |
|
My brand new Radeon X1650 works great; switching from X to a tty (by pressing CTRL+ALT+F1) works fine; but coming back (CTRL+ALT+F7) gives me no video anymore (monitors go into sleep); Also I can't switch back to the tty (I assume the computer hangs).
Does anyone have some experience with this?
some info:
ati-drivers-8.32.5
xorg-x11-7.1
I can post the Xorg.0.log if needed, but I don't want to flood this post right away |
|
| Back to top |
|
 |
warrawarra
Tux's lil' helper
Joined: 30 May 2007
Posts: 84
|
| Posted: Fri Jun 22, 2007 5:04 am Post subject: |
|
|
Might try to kill sleepmode or power saving etc to stop it from going into sleep mode.
Also you will have to look at the log and see what is going on then as well and see if there is a change.
dmesg
the end might list a error or two.
I cheat by pressing ctrl+alt+backspace buttons to restart the x server.
I wonder if you will be able to use the ati control panel in kde / gnome to change some options as well.
Hope this helps. |
|
| Back to top |
|
|
andretti
Tux's lil' helper
Joined: 25 Feb 2007
Posts: 94
|
| Posted: Fri Jun 22, 2007 6:32 am Post subject: |
|
|
| My X1900 give me something similar. It turns out that the monitor was confused or mislead. My system did not crash, and I can get video back on by pressing the input button on the monitor, switching it from DVI to D-SUB and then back to DVI again. |
|
| Back to top |
|
|
nielchiano
Veteran
Joined: 11 Nov 2003
Posts: 1287
Location: 50N 3E
|
| Posted: Fri Jun 22, 2007 7:43 am Post subject: |
|
|
| andretti wrote: | | My X1900 give me something similar. It turns out that the monitor was confused or mislead. My system did not crash, and I can get video back on by pressing the input button on the monitor, switching it from DVI to D-SUB and then back to DVI again. |
Hmm; I might try that, but at best it will solve half the problem: I have 2 monitors connected (one DVI, one VGA); both go into sleep mode |
|
| Back to top |
|
|
nielchiano
Veteran
Joined: 11 Nov 2003
Posts: 1287
Location: 50N 3E
|
| Posted: Fri Jun 22, 2007 7:45 am Post subject: |
|
|
| warrawarra wrote: | | Might try to kill sleepmode or power saving etc to stop it from going into sleep mode. |
It has nothing to do with powersaving; that works just fine. The point when is goes wrong is after CTRL+ALT+F1, CTRL+ALT+F7.
I'll try to catch the dmesg-log-file |
|
| Back to top |
|
|
nielchiano
Veteran
Joined: 11 Nov 2003
Posts: 1287
Location: 50N 3E
|
| Posted: Fri Jun 22, 2007 8:27 am Post subject: |
|
|
Here they are:
dmesg | Code: | irq 19: nobody cared (try booting with the "irqpoll" option)
[<c0140bca>] __report_bad_irq+0x36/0x83
[<c0140dbf>] note_interrupt+0x1a8/0x1e9
[<c01402b7>] handle_IRQ_event+0x26/0x4e
[<c0141575>] handle_fasteoi_irq+0x94/0xb9
[<c01058b7>] do_IRQ+0x7d/0xa6
[<c014158c>] handle_fasteoi_irq+0xab/0xb9
[<c01039be>] common_interrupt+0x1a/0x20
[<c018007b>] bd_claim_by_disk+0x128/0x1a3
[<c0134e1c>] bit_waitqueue+0x20/0x43
[<c0134e7d>] wake_up_bit+0xb/0x16
[<c018f7fa>] proc_delete_inode+0x0/0x96
[<c017002d>] generic_delete_inode+0x100/0x11f
[<c016f6e8>] iput+0x49/0x79
[<c016d718>] dentry_iput+0x99/0xb9
[<c0164f9a>] do_lookup+0xd5/0x16b
[<c016e42b>] dput+0x10f/0x129
[<c0164ad7>] path_release+0x12/0x2e
[<c01670a2>] __link_path_walk+0xc24/0xc53
[<c01039be>] common_interrupt+0x1a/0x20
[<c0167126>] link_path_walk+0x55/0xd4
[<c015c9a0>] get_unused_fd+0xc7/0xd1
[<c0167458>] do_path_lookup+0x188/0x1a4
[<c015f473>] get_empty_filp+0x91/0x166
[<c0167e97>] __path_lookup_intent_open+0x45/0x77
[<c0168054>] open_namei+0x8c/0x5f0
[<c01611c4>] cp_new_stat64+0x103/0x115
[<c015cc75>] do_filp_open+0x31/0x48
[<c015c9a0>] get_unused_fd+0xc7/0xd1
[<c015ccd7>] do_sys_open+0x4b/0xe7
[<c015cdc5>] sys_open+0x27/0x2b
[<c0102fcd>] sysenter_past_esp+0x56/0x79
=======================
handlers:
[<c02d12c8>] (usb_hcd_irq+0x0/0x58)
[<c02d12c8>] (usb_hcd_irq+0x0/0x58)
[<f89fcb3f>] (islpci_interrupt+0x0/0x1fd [prism54])
Disabling IRQ #19
|
Xorg.0.log: nothing special |
|
| Back to top |
|
|
x.para
Apprentice
Joined: 22 May 2005
Posts: 174
Location: CZ
|
| Posted: Wed Jul 11, 2007 7:55 am Post subject: |
|
|
Same problem here. It looks, that switching to another console makes Xorg crashing without any log  Using 2.6.20-suspend2-r6 kernel now.
_________________
Miracles are happening! |
|
| Back to top |
|
|
nielchiano
Veteran
Joined: 11 Nov 2003
Posts: 1287
Location: 50N 3E
|
| Posted: Mon Jul 16, 2007 6:26 pm Post subject: |
|
|
I "solved" this by upgrading to the (currently ~x86) ati-drivers-8.37.6-r1
The display in MythTV is still bad, however. |
|
| Back to top |
|
|
|
Kernel & Hardware
