You are not logged in.
I just installed the proprietary catalyst driver from the unofficial repositories and followed the wiki to successfully install the driver, however upon reboot, the text size(within all the terminals) appears to be twice the size of the regular size.
Here is my xorg.conf file that was generated by doing 'aticonfig --initial'
Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
EndSection
Section "Module"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSectionI tried setting my default resolution by adding the line
Modes "1920x1080"
so the xorg.conf file looked like this
Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
EndSection
Section "Module"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1920x1080"
EndSubSection
EndSectionAfter a reboot, the size was still the same.
I am not sure what else could have changed the resolution/text size of the terminals.
Last edited by PigsInSpace (2015-03-20 00:17:02)
Offline
What terminals have you checked?
Anything interesting in the logs and systemd's journal?
Offline
What terminals have you checked?
Anything interesting in the logs and systemd's journal?
I checked all the terminals(1-6)
I checked the systemds journal and didn't see anything wrong. Should I post the systemds journal?
Im not sure what logs you are referring to.
Offline
If it's about text size in tty, then it's probably a KMS issue, see the note on https://wiki.archlinux.org/index.php/Ke … de_setting
It's not big text, it's small resolution. Do you care about doing something about it or were you just curious?
I thought you were talking about terminal emulators in X, I was referring to the X server logs.
Last edited by karol (2015-03-18 20:08:34)
Offline
If it's about text size in tty, then it's probably a KMS issue, see the note on https://wiki.archlinux.org/index.php/Ke … de_setting
It's not big text, it's small resolution. Do you care about doing something about it or were you just curious?I thought you were talking about terminal emulators in X, I was referring to the X server logs.
I would like to fix it if it isn't too much work. I asked because I wasn't sure if the Catalyst driver had installed correctly.
Looking at the wiki you posted, it seems like I have generate an edid file and then load it as a kernel param. I have the nomodeset parameter set as a kernel module set as well because the wiki on the Catalyst driver said to set it to that but running without that param didn't change anything.
Offline
You can work out your correct dpi here: http://dpi.lv/
and then create an entry in your xorg.conf.d as per the wiki...
Offline
You can work out your correct dpi here: http://dpi.lv/
and then create an entry in your xorg.conf.d as per the wiki...
xorg.conf.d is for X, would this fix the tty?
Try setting the desired resolution with 'video=' or 'vga=' on the kernel command line.
What is the native resolution of your display? What bootloader are you using?
Offline
If you're going to be using the proprietary driver, you won't be able to use KMS as others have said.
That means that your TTY will be a lower resolutioon. So if you need your TTYs at native resolution, the best thing to do would probably be to use the open drivers.
Offline
jasonwryan wrote:You can work out your correct dpi here: http://dpi.lv/
and then create an entry in your xorg.conf.d as per the wiki...
xorg.conf.d is for X, would this fix the tty?
Try setting the desired resolution with 'video=' or 'vga=' on the kernel command line.
What is the native resolution of your display? What bootloader are you using?
Because OP started the thread with detailing changes to xorg.conf. Obviously.
Reading the thread, it isn't clear to me that the issue is in the console: mainly because terminal, TTY and console are used randomly throughout the thread...
Offline
karol wrote:jasonwryan wrote:You can work out your correct dpi here: http://dpi.lv/
and then create an entry in your xorg.conf.d as per the wiki...
xorg.conf.d is for X, would this fix the tty?
Because OP started the thread with detailing changes to xorg.conf. Obviously.
Reading the thread, it isn't clear to me that the issue is in the console: mainly because terminal, TTY and console are used randomly throughout the thread...
Yeah, I was confused too: https://bbs.archlinux.org/viewtopic.php … 6#p1512246
Offline
You can work out your correct dpi here: http://dpi.lv/
and then create an entry in your xorg.conf.d as per the wiki...
I read the xorg wiki and I set the display size and rebooted but its the same still.
Try setting the desired resolution with 'video=' or 'vga=' on the kernel command line.
What is the native resolution of your display? What bootloader are you using?
I tried setting the kernel params of video to my native resolution. My native resolution is 1920x1080@144 and I'm using GNU Grub as a boot loader.
Reading the thread, it isn't clear to me that the issue is in the console: mainly because terminal, TTY and console are used randomly throughout the thread...
Sorry about that, I'm not sure what to refer to it as. Its the default terminal that shows up when you log on without using any graphics or any of that.
If you're going to be using the proprietary driver, you won't be able to use KMS as others have said.
That means that your TTY will be a lower resolutioon. So if you need your TTYs at native resolution, the best thing to do would probably be to use the open drivers.
I don't think think the open drivers support for 3d acceleration on the newer graphics card are as good as the proprietary drivers. Also, I do not need to have native resolution on my TTY's but it would be a major convenience to have it display at native resolution.
Offline
If you haven't started X, then you are in the console, aka, one of the TTYs. There is no point messing with xorg, as it obviously doesn't apply.
You will not, as has been pointed out, get native resolution outside X with the proprietary driver, unless you use a framebuffer driver: https://wiki.archlinux.org/index.php/Uvesafb (assuming that even works with the AMD cards)...
Offline
If you haven't started X, then you are in the console, aka, one of the TTYs. There is no point messing with xorg, as it obviously doesn't apply.
You will not, as has been pointed out, get native resolution outside X with the proprietary driver, unless you use a framebuffer driver: https://wiki.archlinux.org/index.php/Uvesafb (assuming that even works with the AMD cards)...
Ok, Thanks. I like working in the console but It looks like ill have to adapt to the resolution.
Offline
Depending on what exactly do you want to do in the terminal (just text or pictures, pdfs too?), try fbterm or https://wiki.archlinux.org/index.php/KMSCON I have only Intel cards, so I probably would have to use 'nomodeset' to check if these tools can change the resolution on their own.
Edit: I only had to append 'nomodeset vga=0x31A' to get native resolution (1280x1024, 16 bit). kmscon works.
I did work with just 'nomodeset' too, but wasn't much use, because the screen was blank. I could login blind and see in htop in another (non-kmscon) tty that tmux was started automatically, as expected. Still, I couldn't see anything in kmscon. Adding the proper 'vga=' setting fixed that.
X failed to start, as expected.
Last edited by karol (2015-03-20 01:35:53)
Offline