Fedora This forum is for the discussion of the Fedora Project. |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
07-24-2007, 08:46 AM
|
#1
|
LQ Newbie
Registered: Jul 2007
Posts: 3
Rep:
|
Monitor works until X is restarted, FC7
Hey guys,
I recently installed FC7 on my desktop machine, an Intel Celeron 2.6 with ATI Radeon 9550 and an Acer LCD AL1716 19" monitor.
As Fedora installs, all is fine, but as soon as it tries to start X when it reboots a little box starts floating around the screen saying "Input Not Supported".
I fetched an old 12" CRT monitor from my garage and plugged it in and it worked straight up, and after I log into Fedora I can swap the monitor plugs to the Acer LCD and it displays perfectly, however when I try to restart X or reboot my computer, it comes up with "Input Not Supported" again.
Howcome it works until I restart?
I've tried editing xorg.conf with my monitors h & v settings, but it still occurs (tried installing ATI drivers which crashed X so I replaced the xorg.conf with the backup and it booted fine on the CRT.
Any help is greatly appreciated
Regards,
RyaN
|
|
|
07-25-2007, 11:18 AM
|
#2
|
Senior Member
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,187
|
The "input not supported" is a message from the monitor telling you that it's receiving an invalid input. This is typically caused by an invalid refresh rate or screen size setting. Sometimes by an invalid color rendition setting.
Try your "switch the monitor" thing to get your 19" monitor working and then go to system-config-display to set (and save) your default values. That should fix your problem.
Note that, when you change the display settings, you get a pop-up giving you a few seconds to accept the new settings before reverting to the older (presumably, working) settings, so entering an invalid setting combination will just display the "input not supported" for a while and then revert to the previous settings, so you can try anything you want to try without too many problems.
|
|
|
07-25-2007, 11:46 PM
|
#3
|
LQ Newbie
Registered: Jul 2007
Posts: 3
Original Poster
Rep:
|
Unfortunately it didn't.
When I used system-config-display, it allowed me to change resoulutions and colour depths but instead of previewing them and reverting, it just wrote the changes to xorg.conf, and I had to restart X, which didn't work for any combination of resolutions and colour depths.
After I receive the "Input Not Supported" message on the 19", and try to plug it into the old CRT again, I get it's equivilent of the error, ie: a blank screen and the light flashing, and have to restart X again for that monitor to display.
If I go into System > Preferences > Hardware > Screen Resolution I get a small box that has Default Settings, and is set to 1024x768, 60Hz which I can change and it reverts if it fails on the CRT, if I do it on the 19" LCD it Auto-Configures itself to suit.
This is really getting on my nerves, its been 4 days now that I've been trying to fix this.
Thanks for your help,
Regards,
RyaN.
|
|
|
07-26-2007, 09:40 AM
|
#4
|
Senior Member
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,187
|
Have you tried the aticonfig command? An aticonfig --help | less should give you several screens of command line options. Perhaps an aticonfig --initial might get you going.
By the way, most ATI boards support "dual head" operation, so you might be able to run your old monitor and your new one at the same time. (I've got an old ATI chipset in this laptop, and sometimes have it connected to my LCD TV as a second screen.)
|
|
|
09-12-2007, 10:15 AM
|
#5
|
LQ Newbie
Registered: Sep 2007
Location: Ljubljana, Slovenia
Posts: 2
Rep:
|
Has this issue been resolved yet?
I seem to be experiencing it as well on a HP dc5750 with Acer AL1716 LCD monitor. Shortly after the beginning of the boot process, Fedora switches to graphics mode, and all I see on my screen is "Input Not Supported". Once I successfully log in (which I do by help of an old CRT monitor sitting next to AL1716 on my desk), the system works fine in 1280x1024 mode @ 75 Hz.
HP dc5750 is supposedly using ATI Xpress 1150 chipset.
Here is my /etc/X11/xorg.conf file:
Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "si"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Acer"
ModelName "AL1716"
DisplaySize 340 270
HorizSync 31.0 - 81.0
VertRefresh 56.0 - 75.0
Option "dpms"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "radeon"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 16
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024"
EndSubSection
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
Some more data:
# lspci -v
[...]
01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress 200] (prog-if 00 [VGA])
Subsystem: Hewlett-Packard Company Unknown device 280a
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17
Memory at c8000000 (32-bit, prefetchable) [size=128M]
I/O ports at 2100 [size=256]
Memory at d8500000 (32-bit, non-prefetchable) [size=64K]
[virtual] Expansion ROM at d8000000 [disabled] [size=128K]
Capabilities: [50] Power Management version 2
[...]
# ddcprobe
Monitor autoprobe results
Monitor autoprobe failed.
Does anybody have some insightful thought on how I can get X to produce a video signal my monitor can sync with *before* I log in?
With kind regards,
Primoz
|
|
|
09-12-2007, 06:20 PM
|
#6
|
Senior Member
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,187
|
I believe that the rhgb option is implemented before your xorg configuration file is accessed.
If you remove the rhgb option from your GRUB boot command line it might help you boot without the aggravation.
|
|
|
09-13-2007, 12:00 AM
|
#7
|
LQ Newbie
Registered: Jul 2007
Posts: 3
Original Poster
Rep:
|
Not sure about the rhgb option, but I resolved my issue just the other day by editing my xorg.conf and adding _60 to the end of each pre-defined display type ie: "1024x768_60" and it works fine.
Hope that helps somebody else =)
Thanks everybody...
|
|
|
09-13-2007, 03:52 AM
|
#8
|
LQ Newbie
Registered: Sep 2007
Location: Ljubljana, Slovenia
Posts: 2
Rep:
|
Thanks everybody. As I have never tinkered with rhgb options before, I decided to try the second solution first, and it works! In my case (Acer AL1716), the winning combination seems to be "1280x1024_72".
Once again, thank you for your help!
Last edited by peterlin; 09-13-2007 at 03:53 AM.
Reason: more detailed information on hardware used
|
|
|
All times are GMT -5. The time now is 12:01 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|