Re: Signal over range, WAS: X -configure fails: Number of created screens does not match number of detected devices. Configuration failed.
On Tue, Dec 22, 2009 at 08:47:19PM +, Anton Shterenlikht wrote: > On Tue, Dec 22, 2009 at 09:29:54PM +0100, Marius Strobl wrote: > > On Tue, Dec 22, 2009 at 08:12:14PM +, Anton Shterenlikht wrote: > > > On Tue, Dec 22, 2009 at 12:26:03PM -0700, Warren Block wrote: > > > > On Tue, 22 Dec 2009, Anton Shterenlikht wrote: > > > > > Warren, thank you, but this doesn't help. I've added: > > > > > > > > > > Section "Monitor" > > > > > Identifier "Monitor0" > > > > > HorizSync 30-50 > > > > > VertRefresh 60 > > > > > EndSection > > > > > > > > > > Section "Device" > > > > > Identifier "Card0" > > > > > Driver "mach64" > > > > > BusID "PCI:0:2:0" > > > > > EndSection > > > > > > > > Hmm. Some web searching says non-Intel platforms might need a > > > > different > > > > reference clock: > > > > > > > > http://www.gentoo.org/doc/en/gentoo-sparc-faq.xml#doc_chap4_sect1 > > > > > > yes, now you told me I see it's actually in the logs: > > > > > > (--) MACH64(0): Reference clock 157.5/11 (14.318) MHz. > > > (II) MACH64(0): If modes do not work on Ultra 5/10 or Blade 100/150, > > > set option "reference_clock" to "28.636 MHz" or "29.5 MHz" > > > > > > by using either 28.636 or 29.5 I now get no "signal over range". > > > > The right value for a Rage XL is 29.5 MHz. > > Marius, thank you, I figured it out already. > Here's the winning xorg.conf: http://seis.bris.ac.uk/~mexas/freebsd/xorg.conf > in case somebody else might be using this hardware. > > Also, could you comment on Warren's suggestion of Radeon 7000? > Do you think it might work on blade 1500? > It won't work currently and also unlikely in the future. Marius ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Signal over range, WAS: X -configure fails: Number of created screens does not match number of detected devices. Configuration failed.
On Tue, Dec 22, 2009 at 09:29:54PM +0100, Marius Strobl wrote: > On Tue, Dec 22, 2009 at 08:12:14PM +, Anton Shterenlikht wrote: > > On Tue, Dec 22, 2009 at 12:26:03PM -0700, Warren Block wrote: > > > On Tue, 22 Dec 2009, Anton Shterenlikht wrote: > > > > Warren, thank you, but this doesn't help. I've added: > > > > > > > > Section "Monitor" > > > > Identifier "Monitor0" > > > > HorizSync 30-50 > > > > VertRefresh 60 > > > > EndSection > > > > > > > > Section "Device" > > > > Identifier "Card0" > > > > Driver "mach64" > > > > BusID "PCI:0:2:0" > > > > EndSection > > > > > > Hmm. Some web searching says non-Intel platforms might need a different > > > reference clock: > > > > > > http://www.gentoo.org/doc/en/gentoo-sparc-faq.xml#doc_chap4_sect1 > > > > yes, now you told me I see it's actually in the logs: > > > > (--) MACH64(0): Reference clock 157.5/11 (14.318) MHz. > > (II) MACH64(0): If modes do not work on Ultra 5/10 or Blade 100/150, > > set option "reference_clock" to "28.636 MHz" or "29.5 MHz" > > > > by using either 28.636 or 29.5 I now get no "signal over range". > > The right value for a Rage XL is 29.5 MHz. Marius, thank you, I figured it out already. Here's the winning xorg.conf: http://seis.bris.ac.uk/~mexas/freebsd/xorg.conf in case somebody else might be using this hardware. Also, could you comment on Warren's suggestion of Radeon 7000? Do you think it might work on blade 1500? many thanks as always anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Signal over range, WAS: X -configure fails: Number of created screens does not match number of detected devices. Configuration failed.
On Tue, Dec 22, 2009 at 08:12:14PM +, Anton Shterenlikht wrote: > On Tue, Dec 22, 2009 at 12:26:03PM -0700, Warren Block wrote: > > On Tue, 22 Dec 2009, Anton Shterenlikht wrote: > > > Warren, thank you, but this doesn't help. I've added: > > > > > > Section "Monitor" > > > Identifier "Monitor0" > > > HorizSync 30-50 > > > VertRefresh 60 > > > EndSection > > > > > > Section "Device" > > > Identifier "Card0" > > > Driver "mach64" > > > BusID "PCI:0:2:0" > > > EndSection > > > > Hmm. Some web searching says non-Intel platforms might need a different > > reference clock: > > > > http://www.gentoo.org/doc/en/gentoo-sparc-faq.xml#doc_chap4_sect1 > > yes, now you told me I see it's actually in the logs: > > (--) MACH64(0): Reference clock 157.5/11 (14.318) MHz. > (II) MACH64(0): If modes do not work on Ultra 5/10 or Blade 100/150, > set option "reference_clock" to "28.636 MHz" or "29.5 MHz" > > by using either 28.636 or 29.5 I now get no "signal over range". The right value for a Rage XL is 29.5 MHz. Marius ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
SOLVED: Re: Signal over range, WAS: X -configure fails: Number of created screens does not match number of detected devices. Configuration failed.
On Tue, Dec 22, 2009 at 12:26:03PM -0700, Warren Block wrote: > On Tue, 22 Dec 2009, Anton Shterenlikht wrote: > > Warren, thank you, but this doesn't help. I've added: > > > > Section "Monitor" > > Identifier "Monitor0" > > HorizSync 30-50 > > VertRefresh 60 > > EndSection > > > > Section "Device" > > Identifier "Card0" > > Driver "mach64" > > BusID "PCI:0:2:0" > > EndSection > > Hmm. Some web searching says non-Intel platforms might need a different > reference clock: > > http://www.gentoo.org/doc/en/gentoo-sparc-faq.xml#doc_chap4_sect1 out of desperation was re-reading the manual and saw this: Starting with Xorg 7.4 and above, this test produces a black screen which may make it difficult to diagnose whether X11 is working properly. The older behavior is still available by using the retro option: # Xorg -config xorg.conf.new -retro so, yes, I got the grey screen and a cross, and the mouse seems to be working. Warren, many thanks for your help! -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Signal over range, WAS: X -configure fails: Number of created screens does not match number of detected devices. Configuration failed.
On Tue, Dec 22, 2009 at 12:26:03PM -0700, Warren Block wrote: > On Tue, 22 Dec 2009, Anton Shterenlikht wrote: > > Warren, thank you, but this doesn't help. I've added: > > > > Section "Monitor" > > Identifier "Monitor0" > > HorizSync 30-50 > > VertRefresh 60 > > EndSection > > > > Section "Device" > > Identifier "Card0" > > Driver "mach64" > > BusID "PCI:0:2:0" > > EndSection > > Hmm. Some web searching says non-Intel platforms might need a different > reference clock: > > http://www.gentoo.org/doc/en/gentoo-sparc-faq.xml#doc_chap4_sect1 yes, now you told me I see it's actually in the logs: (--) MACH64(0): Reference clock 157.5/11 (14.318) MHz. (II) MACH64(0): If modes do not work on Ultra 5/10 or Blade 100/150, set option "reference_clock" to "28.636 MHz" or "29.5 MHz" by using either 28.636 or 29.5 I now get no "signal over range". In fact I just get a black screen. Not sure if this is worse or better... many thanks -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Signal over range, WAS: X -configure fails: Number of created screens does not match number of detected devices. Configuration failed.
On Tue, 22 Dec 2009, Anton Shterenlikht wrote: Warren, thank you, but this doesn't help. I've added: Section "Monitor" Identifier "Monitor0" HorizSync 30-50 VertRefresh 60 EndSection Section "Device" Identifier "Card0" Driver "mach64" BusID "PCI:0:2:0" EndSection Hmm. Some web searching says non-Intel platforms might need a different reference clock: http://www.gentoo.org/doc/en/gentoo-sparc-faq.xml#doc_chap4_sect1 (EE) [drm] drmOpen failed. (EE) MACH64(0): [dri] DRIScreenInit Failed should I add device drm to the kernel? It seems unlikely that you'll get DRM on that card anyway. Just to remind, this is sparc64. Incidentally, Radeon 7000 cards are available in standard PCI for $20 or so. Not a great card, but quite an upgrade over a Mach64, and supported by a current driver. wow.. you mean on sparc64? I didn't know. If it'll work on sparc, this would be great. There are many more radeon 7000 on offer than pgx64. No experience on my part, but... The card BIOS may not work (as above with the reference clock), but if the system can do without and the PCI bus is standard... -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Signal over range, WAS: X -configure fails: Number of created screens does not match number of detected devices. Configuration failed.
On Tue, Dec 22, 2009 at 11:12:35AM -0700, Warren Block wrote: > On Tue, 22 Dec 2009, Anton Shterenlikht wrote: > > ok, I moved a step further. 'X -configure' is now successful. > > All I had to do is to move the graphics card to another pci > > slot. Perhaps where xvr600 was, is not a standard pci slot > > at all? pgx64 worked fine there in the text mode, but not > > in the graphics mode. > > > > So now I'm stopped with "Signal over range" message reported > > by the monitor firmware (?). > > > > The card seems to be detected, the scan frequencies I put > > are from the manufacturer's specs, but still something is wrong. > > > > I put conf and log files here: > > > > http://seis.bris.ac.uk/~mexas/freebsd/xorg.conf.new > > http://seis.bris.ac.uk/~mexas/freebsd/Xorg.0.log > > Manually setting a single mode is probably the easiest: > > Section "Screen" > Identifier "Screen0" > Device "Card0" > Monitor"Monitor0" > DefaultDepth 24 > SubSection "Display" > Viewport 0 0 > Depth 24 > Modes "1280x1024" > EndSubSection > EndSection > > That might be enough, or you might have to go to 1024x768. You could > limit the entries in the Monitor section to trick the card into picking > a single reasonable mode, like VertRefresh 70, or HorizSync 30-50. > (Assuming this is a CRT. If it's an LCD, use VertRefresh 60.) Warren, thank you, but this doesn't help. I've added: Section "Monitor" Identifier "Monitor0" HorizSync 30-50 VertRefresh 60 EndSection Section "Device" Identifier "Card0" Driver "mach64" BusID "PCI:0:2:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" DefaultDepth24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" EndSubSection EndSection This is an LCD monitor, and the manuf. specs state max res 1280x1024 horizontal: 30-80 vertical: 50-75 I tried modes down to 800x600 - no change. I noticed also this error: (EE) [drm] drmOpen failed. (EE) MACH64(0): [dri] DRIScreenInit Failed should I add device drm to the kernel? Just to remind, this is sparc64. > Incidentally, Radeon 7000 cards are available in standard PCI for $20 or > so. Not a great card, but quite an upgrade over a Mach64, and supported > by a current driver. wow.. you mean on sparc64? I didn't know. If it'll work on sparc, this would be great. There are many more radeon 7000 on offer than pgx64. many thanks as always anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: Signal over range, WAS: X -configure fails: Number of created screens does not match number of detected devices. Configuration failed.
On Tue, 22 Dec 2009, Anton Shterenlikht wrote: ok, I moved a step further. 'X -configure' is now successful. All I had to do is to move the graphics card to another pci slot. Perhaps where xvr600 was, is not a standard pci slot at all? pgx64 worked fine there in the text mode, but not in the graphics mode. So now I'm stopped with "Signal over range" message reported by the monitor firmware (?). The card seems to be detected, the scan frequencies I put are from the manufacturer's specs, but still something is wrong. I put conf and log files here: http://seis.bris.ac.uk/~mexas/freebsd/xorg.conf.new http://seis.bris.ac.uk/~mexas/freebsd/Xorg.0.log Manually setting a single mode is probably the easiest: Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" EndSubSection EndSection That might be enough, or you might have to go to 1024x768. You could limit the entries in the Monitor section to trick the card into picking a single reasonable mode, like VertRefresh 70, or HorizSync 30-50. (Assuming this is a CRT. If it's an LCD, use VertRefresh 60.) Incidentally, Radeon 7000 cards are available in standard PCI for $20 or so. Not a great card, but quite an upgrade over a Mach64, and supported by a current driver. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: Signal over range, WAS: X -configure fails: Number of created screens does not match number of detected devices. Configuration failed.
On Sun, Dec 20, 2009 at 11:20:12PM +0100, Marius Strobl wrote: > On Sun, Dec 20, 2009 at 10:10:10PM +, Anton Shterenlikht wrote: > > On Sun, Dec 20, 2009 at 04:00:05PM +0100, Marius Strobl wrote: > > > On Sat, Dec 19, 2009 at 09:48:03PM +, Anton Shterenlikht wrote: > > > > > > > > I've built X without hal, but get this error on X -configure: > > > > > > > > > > Actually when running `X -configure` or when trying to use the > > > resulting /root/xorg.conf.new? This looks more like an error in > > > the configuration file and the results returned by google for > > > this failure message suggest that this can be due to the server > > > not being able to load a configured module. Anyway, I'd try > > > to use the resulting xorg.conf.new and if that fails manually > > > checking its contents and removing unnecessary and unavailable > > > stuff like DRI for example. > > > > yes, on 'X -configure'. Removing modules doesn't help. > > > > and then on 'X -config ./xorg.conf.new': > > > > Could you please make that xorg.conf.new available somewhere? ok, I moved a step further. 'X -configure' is now successful. All I had to do is to move the graphics card to another pci slot. Perhaps where xvr600 was, is not a standard pci slot at all? pgx64 worked fine there in the text mode, but not in the graphics mode. So now I'm stopped with "Signal over range" message reported by the monitor firmware (?). The card seems to be detected, the scan frequencies I put are from the manufacturer's specs, but still something is wrong. I put conf and log files here: http://seis.bris.ac.uk/~mexas/freebsd/xorg.conf.new http://seis.bris.ac.uk/~mexas/freebsd/Xorg.0.log I also get this on the console: (++) Using config file: "./xorg.conf.new" failed to unset mtrr: Operation not supported by device failed to unset mtrr: Operation not supported by device ^Cfailed to unset mtrr: Operation not supported by device failed to unset mtrr: Operation not supported by device # not sure if this matters.. Please advise many thanks all your help and support -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
