You are not logged in.
Hey all,
I realised something a little strange. Recently, I built a new PC, and put my old Arch install on it.
Onn my old PC, the console (before I startx) appeared on my big monitor, which was sometimes useful if I broke X and had to use w3m to google something (And other silly errors by me)
However, on this PC, it appears on my smaller monitor, which while it's not a huge issue, I'd sort of like it back on the other one!
I haven't actually changed anything graphics-wise (I used my old Graphics card in the new PC, no point upgrading something that works great already) So I'm not sure what could've caused this...
Is there a way to have this back? Or even better, is there a way to use both screens? ![]()
Thanks!
"Some humans would do anything to see if it was possible to do it. If you put a large switch in some cave somewhere, with a sign on it saying "End-of-the-World Switch. PLEASE DO NOT TOUCH", the paint wouldn't even have time to dry."
Offline
If you enter the BIOS set up, does it too use the small screen?
Are both displays served from the same graphics card?
Did you, by chance, reverse the connectors from the configuration you had before?
If not, have you tried swapping them?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
You could also try to use a framebuffer terminal emulator on one or both screens (e.g. fbterm)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
@ Ewaller,
From 1st to last -
No, it uses the big screen.
Yes.
No, as one is HDMI and the other isn't. (HDMI is the 'big' screen, and the one I would like my console to appear on)
See above![]()
Progandy, but how would that run on both screens when my current one won't? Right now, my right (big) screen gets shut off until I startx ![]()
Last edited by Reded (2012-07-21 20:26:25)
"Some humans would do anything to see if it was possible to do it. If you put a large switch in some cave somewhere, with a sign on it saying "End-of-the-World Switch. PLEASE DO NOT TOUCH", the paint wouldn't even have time to dry."
Offline
Progandy, but how would that run on both screens when my current one won't? Right now, my right (big) screen gets shut off until I startx
How many framebuffer-devices do you have (/dev/fb...)? One for each screen? Then try to run fbterm with "FRAMEBUFFER=/dev/fb... fbterm"
If you want a login screen for the framebuffer, try qingy ![]()
Last edited by progandy (2012-07-21 20:34:13)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
There's only one file in /dev/ called fb0, if that's what you mean ![]()
I'll give that a try and see what happens!
I'm not too fussed about login screens, it's only me who uses this PC, and Arch auto-logs me in so all I have to do is startx.
Unfortunately FRAMEBUFFER=/dev/fb0 fbterm still only displays it on my small monitor!
Last edited by Reded (2012-07-21 20:37:28)
"Some humans would do anything to see if it was possible to do it. If you put a large switch in some cave somewhere, with a sign on it saying "End-of-the-World Switch. PLEASE DO NOT TOUCH", the paint wouldn't even have time to dry."
Offline