Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have problem in Anaconda Installer and Fedora KDE and Gnome. have resolution 640x480 when I try to change to higer resolution eg. 800 or 1024x768 still is 640x480 but desktop is larger.
I tried to run Knoppix first and everything seemed all right.
My computer: Motherboard: MSI k7n2g-ILSR, 512MB RAM,
ATI Radeon 7000, Seagate 120Gb S-ATA, Monitor: Eizo FlexScan L550
When booting from the CD, Anaconda recognizes the monitor as L550. When probing for it later with ddcprobe it does not detect any monitor at all.
Here are the specifications for my screen Eizo L550 as provided by Eizo.com
43 cm (17") TFT color LCD panel
Gray, Black, Two-Tone (gray & black)
0.264 × 0.264 mm
16.19 million (maximum)
160, 160 (at contrast ratio of 5:1)
Analog: 31.5 80 kHz, 56 75.1 Hz
Digital: 31.5 64 kHz, 59 61 Hz (VGA Text: 69 71 Hz)
1280 × 1024
300 cd/m 2
450:1 135 MHz, Digital: 108 MHz
16 ms (typical) RGB Analog, DVI Standard 1.0
Separate
D-Sub mini 15 pin, DVI-D 24 pin (switchable)
338 × 270 mm
432 mm (diagonal) VESA DDC 2B ScreenManager ® ,
AC100 120V / 200 240V, 50 60 Hz
VESA DPMS, DVI DMPM
38 watts
I use the Analog mode.
Here is the contents of the curent xorg.config file on my system. I have tried to change these parameters to look more like those in knoppix but nothing changes. Maybe I am doing something wrong?
I have not installed any drivers from nVidia because I do not know how to do that(I am used to Windows) and the drivers I have is only for windows. But I tried Mandrake awhile ago on the same system but with another monitor and I did not have this problem then. So I assume it is something with the monitor.
If anybody out there would use their time to give me some help with this I would very much appreciate it...Please tell me if you need more or information.
Welcome to LQ transke. First, have you tried simply cycle through your available monitor resolutions by pressing Alt Ctl + or Alt Ctl - (using the plus and the minus key on the numeric keypad to the right of the keyboard) If that fails, I would suggest considering that you manually rerun the xf86config or xorgconf program (I'm not sure which FC2 runs) It will go through a series of questions about your equipment and settings, etc, and the end result is a new config file. From there you would exit X, startx, and if all goes well you'll be using your preferred resolutions. I would recommend that you save your existing XF86Config or xorg.conf files first, in case you need to restore.
Pressing Ctrl+Alt+ or - does not change the resolution. Nothing happens when doing this. The FC2 uses xorg.conf but I do not know how to rerun the file, I am still a newbie. But should it not be the same result if I edit the xorg.conf file with a text editor like gedit?the Entering parameters I got from knoppix or Eizo does not help.
With a command prompt from GRub the 'vbeprobe' detects the monitor and shows some numbers. But when probing after booting linux it does not detect any monitor. Maybe I am using these commands wrong? I appreciate all help and possible solutions...
You can edit the file if you wish using your favorite text editor, or you can regenerate the xorg.conf file by running the xorgconfig program (as root). That program will take you through a series of questions about your keyboard, mouse, and video, and the resulting file will be a new xorg.conf based on whatever answers you have supplied.
I'd recommend making a backup copy first of the current xorg.conf just in case you have to restore to it. Once you've made your copy, just run: xorgconfig
Hopefully that should do it. Good luck with it -- J.W.
I am embarrassed to say this, but I don not know how to run a program from the command line...Maybe strange but I do know how to double click an icon i Windows I have tried to type run, exec, start and xorgconfig but it does not seem to start anything. Re-editing in an editor does not work either. I think it is strange that when typing 'vbeprobe' in Grub it finds monitor, but if typing 'ddcprobe" in command prompt or in runlevel 3, no monitor is found. As if there is no monitor and it does not matter what i change in the xorg.conf.. It finds the Videocard in both cases. Maybe I use the commands wrong, please tell me, because I have no manual to refer to...
Don't worry about it, it's actually pretty easy. Open a terminal session, then enter the following:
Code:
su
<enter root password>
cd /etc/X11
xorgconfig
<answer questions>
exit
The "su" command puts you into root user mode. Enter the root password, then change directories ("cd") to /etc/X11. That's where xorgconfig lives (if I remember correctly.) To run it, just enter "xorgconfig". Answer the questions, save the file, the close the terminal session with the "exit" command.
Reboot your machine and if all went well you'll be using the new settings. Good luck with it. -- J.W.
I tried exactly what you said but nothing happened. Strange. I also tried an old CRT monitor and suddenly everything was fine, it was possible to change the resolution and see all of the desktop for the first time. Is it not possible to use LCD monitors with Fedora? But I don't feel like I have solved the problem if I must buy a new monitor though...
transke -- it would be a big help if you could provide more details. What do you mean "nothing happened" -- did the commands not work, did the behavior remain as it was before, were there error messages, etc. Also, what exact resolution are you trying to use? Based on your last note, maybe the desktop image is extending beyond the borders of the screen, and if so have you tried using the control buttons on the monitor itself to adjust the size of the image? Perhaps it's not so much of a resolution issue as it is a monitor settings issue. I can't be sure - as I said, the more details you can provide, the better. -- J.W.
when I type xorgcongig, I get the message: "command not found"
The desktop is extending beyond the borders of the screen. When I pressing the "info" button on my screen it says something like "input 640x480" whereas, pressing the same button in windows says "1280x1024" and that is the resolution I am trying to set.
I wish som much it was as simple thing as adjusting the size of the image. But good idea because the solution probably is easy and it is a good chance that I have overlooked something. Afterall this is my only fourth day with linux...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
I have tried to type run, exec, start and xorgconfig but it does not seem to start anything. Re-editing in an editor does not work either. I think it is strange that when typing 'vbeprobe' in Grub it finds monitor, but if typing 'ddcprobe" in command prompt or in runlevel 3, no monitor is found. As if there is no monitor and it does not matter what i change in the xorg.conf.. It finds the Videocard in both cases. Maybe I use the commands wrong, please tell me, because I have no manual to refer to...
