Hi All,
I'm a relative new-comer to the world of Linux and need some advice/help regarding an install of Redhat 8.0.
I'm installing to a second HD on the primary channel, PCChips 810, 384MB, Radeon 7500VE to a Dell 1025HE monitor. This is networked via crossover cable to a RISC OS box using a KVM.
Everything seems to progress fine, including the graphics card selection. The installer picks up the correct card model, RAM type and size.
The problem arises with the monitor selection, it reports "un-probed". I have tried selecting the correct Dell model from the list but it will not give me the test screen or indeed any other help.
If I then continue with the install the boot screen errors on the boot screen with EE for the graphics card and the monitor and then hangs. The error is something along the lines of 'screens found but no usable screens defined' or very similar.
Has anybody had this problem or can anyone shed any light?
TIA
On Thu, 12 Dec 2002 23:53:52 -0000 "Greg Harris" greg@deloney.demon.co.uk wrote:
Everything seems to progress fine, including the graphics card selection. The installer picks up the correct card model, RAM type and size.
The problem arises with the monitor selection, it reports "un-probed". I have tried selecting the correct Dell model from the list but it will not give me the test screen or indeed any other help.
If I then continue with the install the boot screen errors on the boot screen with EE for the graphics card and the monitor and then hangs. The error is something along the lines of 'screens found but no usable screens defined' or very similar.
I have only worked very briefly with RedHat and not version 8.0 but I think I can take a guess at what is going on here.
Normally RedHat presents a graphical login screen which in turns relies on the services of a piece of software called XFree86. One aspect of configuring XFree86 involves providing it with possible "Modes" in which it can drive the monitor and the program that configures XFree86 at installation time would normally do that for you as well as telling it what your monitor is capable of.
In the event that the parameters it has for your monitor are wrong it (Xfree86) can conclude that there are no acceptable modes in which to drive the monitor and it effectively gives up which is what seems to be happenning in your case.
One solution is to edit the XFree86 configuration file by hand to correct the problem - to do that you would need to be able to use the system in 80x24 text mode rather than rely on the graphical login screen. If you use Control+Alt and the functions keys F1 to F6 do any of these present you with a text-mode screen with a login prompt?
If so check out the file /etc/X11/XF86Config or /etc/X11/XF86Config-4. You will need the spec. on your monitor, i.e. which H and V refresh rates it can do. if you still can't make sense of it after doing 'man XF86Config' then come back here for more help.
HTH, Steve.
On 13 Dec 2002 at 1:00, Steve Fosdick wrote:
[snip]
In the event that the parameters it has for your monitor are wrong it (Xfree86) can conclude that there are no acceptable modes in which to drive the monitor and it effectively gives up which is what seems to be happenning in your case.
One solution is to edit the XFree86 configuration file by hand to correct the problem - to do that you would need to be able to use the system in 80x24 text mode rather than rely on the graphical login screen. If you use Control+Alt and the functions keys F1 to F6 do any of these present you with a text-mode screen with a login prompt?
I've tried all options during install ie: text/graphical. I've tried all variations of ATI radeon cards in all of the basic screen modes. Still it goes tits up on boot.
If so check out the file /etc/X11/XF86Config or /etc/X11/XF86Config-4. You will need the spec. on your monitor, i.e. which H and V refresh rates it can do. if you still can't make sense of it after doing 'man XF86Config' then come back here for more help.
As a lemon, you'll have to give me a better clue as to how to get into and edit the config file. I can traverse to the correct dir, but how do i call up an editor to change the file (bearing in mind the best I can manage atm is a text login screen). Tried all combinations of Ctrl+Alt+F keys with no joy. :-((
I've had a better look at the errors and they are as follows;
(EE) Radeon(0); No valid mode found for this DFP/LCD (EE) Screen(s) found, but none have a usable configuration. Noscreens found
As a lemon, you'll have to give me a better clue as to how to get into and edit the config file. I can traverse to the correct dir, but how do i call up an editor to change the file (bearing in mind the best I can manage atm is a text login screen). Tried all combinations of Ctrl+Alt+F keys with no joy. :-((
I've had a better look at the errors and they are as follows;
(EE) Radeon(0); No valid mode found for this DFP/LCD (EE) Screen(s) found, but none have a usable configuration. Noscreens found
what type of Radeon do u have, perhaps someone on list may have the same one and can send u the correct XF86Config-4 file for you to crib from? I don't have a radeon at all unfortunately!
try going to that directory and typing: emacs XF86Config-4
(if u press tab after typing a filname, it should autocomplete btw)
if not, try nano XF86Config-4 or vim XF86... etc or vi XF86...
(I'd read some help text from somewhere on vi if u have to resort to that, as it's not the easiest to use if you don't know what ur doing)
hope that helps
Ricardo
On 14 Dec 2002 at 22:53, N3tw0rkAng31B0y wrote:
[snip]
what type of Radeon do u have, perhaps someone on list may have the same one and can send u the correct XF86Config-4 file for you to crib from? I don't have a radeon at all unfortunately!
try going to that directory and typing: emacs XF86Config-4
(if u press tab after typing a filname, it should autocomplete btw)
if not, try nano XF86Config-4 or vim XF86... etc or vi XF86...
(I'd read some help text from somewhere on vi if u have to resort to that, as it's not the easiest to use if you don't know what ur doing)
hope that helps
Thanks for all the help. The problem is now solved, it was operator error.
Some idiot, namely me, had left the svid out lead still connected and I think this confused things. removing this and a re-install with noprobe sorted it.
Once again thanks,
-
Greg Harris -
N3tw0rkAng31B0y -
Steve Fosdick