[opensuse] OpenSuse10.3 will not boot into KDM with ATi graphics card
Hi all, I've done several test installs of opensuse 10.3, but none will boot into KDM. I formatted over my old 9.3 install in did an clean install there, with /home there as well. I always try a test install before I move to the new version. I've tried 2 different video cards but neither works so far, of is an ATI 9200 AGP, the other is an ATI 9500 AGP. In all cases I get to the command line showing that runlevel 5 has been reached, but no desktop. I have not tried Gnome, but I don't think that matters. To summarize what I did... With ATI 9200 card 1. Format with ext3, install, did online update, select 3D at the end of the install config, runlevel 5 shows to be reached, but no desktop. 2. Re-format with reiser, install, did not do online update, do not select 3D, no desktop. 3. Re-format with ext 3, install, did not do online, update, do not select 3D, no desktop. With Ai 9500 card 1. Re-format with ext3, install, do not select 3D, no desktop. I can VNC into port 5901 in all cases, but local graphics won't work. In all cases running sax2 returns an error citing to check the log, but sadly, I don't know what I'm looking for in there. FYI the 9200 ran better in opensuse10.2 in 3D. The 9500 ran very slowly in 10.2 and only in 2D, but I was hoping 10.3 would get me working in 3D with the 9500, but so far I'm moving backwards, not forwards. I'd really like to get this graphics stuff sorted out. All installs were done on the same machine, Abit nf7 mobo, Athlon 2500, 1.5gb ram, both pata and sata drives seem to work fine. I'd really appreciate any help with this. Many thanks, Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 2007-10-14 at 22:03 -0500, Jim Flanagan wrote:
Hi all,
I've done several test installs of opensuse 10.3, but none will boot into KDM. I formatted over my old 9.3 install in did an clean install there, with /home there as well. I always try a test install before I move to the new version. I've tried 2 different video cards but neither works so far, of is an ATI 9200 AGP, the other is an ATI 9500 AGP. In all cases I get to the command line showing that runlevel 5 has been reached, but no desktop. I have not tried Gnome, but I don't think that matters. To summarize what I did...
With ATI 9200 card 1. Format with ext3, install, did online update, select 3D at the end of the install config, runlevel 5 shows to be reached, but no desktop. 2. Re-format with reiser, install, did not do online update, do not select 3D, no desktop. 3. Re-format with ext 3, install, did not do online, update, do not select 3D, no desktop.
I'd really appreciate any help with this.
Many thanks,
Jim F
Have you tried changing the driver in xorg.conf to vesa? -- Regards, Aniruddha Please adhere to the OpenSUSE_mailing_list_netiquette http://en.opensuse.org/OpenSUSE_mailing_list_netiquette -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Aniruddha wrote:
On Sun, 2007-10-14 at 22:03 -0500, Jim Flanagan wrote:
Hi all,
I've done several test installs of opensuse 10.3, but none will boot into KDM. I formatted over my old 9.3 install in did an clean install there, with /home there as well. I always try a test install before I move to the new version. I've tried 2 different video cards but neither works so far, of is an ATI 9200 AGP, the other is an ATI 9500 AGP. In all cases I get to the command line showing that runlevel 5 has been reached, but no desktop. I have not tried Gnome, but I don't think that matters. To summarize what I did...
With ATI 9200 card 1. Format with ext3, install, did online update, select 3D at the end of the install config, runlevel 5 shows to be reached, but no desktop. 2. Re-format with reiser, install, did not do online update, do not select 3D, no desktop. 3. Re-format with ext 3, install, did not do online, update, do not select 3D, no desktop.
I'd really appreciate any help with this.
Many thanks,
Jim F
Have you tried changing the driver in xorg.conf to vesa?
I believe the vesa driver is the default install, which I did. I have not upgraded the driver yet, but I'll check it later today to make sure. Thanks, Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Aniruddha wrote:
On Sun, 2007-10-14 at 22:03 -0500, Jim Flanagan wrote:
Hi all,
I've done several test installs of opensuse 10.3, but none will boot into KDM. I formatted over my old 9.3 install in did an clean install there, with /home there as well. I always try a test install before I move to the new version. I've tried 2 different video cards but neither works so far, of is an ATI 9200 AGP, the other is an ATI 9500 AGP. In all cases I get to the command line showing that runlevel 5 has been reached, but no desktop. I have not tried Gnome, but I don't think that matters. To summarize what I did...
With ATI 9200 card 1. Format with ext3, install, did online update, select 3D at the end of the install config, runlevel 5 shows to be reached, but no desktop. 2. Re-format with reiser, install, did not do online update, do not select 3D, no desktop. 3. Re-format with ext 3, install, did not do online, update, do not select 3D, no desktop.
I'd really appreciate any help with this.
Many thanks,
Jim F
Have you tried changing the driver in xorg.conf to vesa?
OK, you are most correct, the driver was radeon. I changed it to vesa, then rebooted, but no change in behavior, not GUI at all. I only get to command line. Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/16/2007 11:02 AM, Jim Flanagan wrote:
OK, you are most correct, the driver was radeon. I changed it to vesa, then rebooted, but no change in behavior, not GUI at all. I only get to command line.
FWIW, I also have a 9200 (SE) using the radeon driver. Selecting 3D did not work originally (monitor could not sync). I noticed in the log agpgart was trying to work in 8x. In 10.2 it worked in 4x, so I set up 3D and added "AGPMode" "4" via sax2, and mine worked again immediately. There may be a problem with the driver. When i used fglrx, it did work in 8x. Anyway, try adding the agp limitation and retry. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris (NTM) wrote:
On 10/16/2007 11:02 AM, Jim Flanagan wrote:
OK, you are most correct, the driver was radeon. I changed it to vesa, then rebooted, but no change in behavior, not GUI at all. I only get to command line.
FWIW, I also have a 9200 (SE) using the radeon driver. Selecting 3D did not work originally (monitor could not sync). I noticed in the log agpgart was trying to work in 8x. In 10.2 it worked in 4x, so I set up 3D and added "AGPMode" "4" via sax2, and mine worked again immediately. There may be a problem with the driver. When i used fglrx, it did work in 8x. Anyway, try adding the agp limitation and retry.
Hi Joe, I noticed your post in the other thread about agp in 4x mode, and did try that. It did not work in my case. But, I had already switched video cards out. At present I'm running (or trying to run) the ATI 9800 Pro. (I could not get this card to run at all in 10.2, but thought that might be fixed in 10.3). I'll go back to the 9200 and try your suggestion on that card. (The default 10.3 install did not work with the 9200, which is why I tried switching cards). FYI I also tried the fglrx driver on the 9800 pro last night and I could not even see the command line with that driver. Fortunately uninstalling the fglrx drivers from yast did get me back to at least seeing the command line. Switching driver from radeon to vesa makes no difference, command line but no kde. Thanks for the suggestion, will try the 9200 again later today. Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 16 October 2007, Jim Flanagan wrote:
Joe Morris (NTM) wrote:
On 10/16/2007 11:02 AM, Jim Flanagan wrote:
OK, you are most correct, the driver was radeon. I changed it to vesa, then rebooted, but no change in behavior, not GUI at all. I only get to command line.
FWIW, I also have a 9200 (SE) using the radeon driver. Selecting 3D did not work originally (monitor could not sync). I noticed in the log agpgart was trying to work in 8x. In 10.2 it worked in 4x, so I set up 3D and added "AGPMode" "4" via sax2, and mine worked again immediately. There may be a problem with the driver. When i used fglrx, it did work in 8x. Anyway, try adding the agp limitation and retry.
Hi Joe, I noticed your post in the other thread about agp in 4x mode, and did try that. It did not work in my case. But, I had already switched video cards out. At present I'm running (or trying to run) the ATI 9800 Pro. (I could not get this card to run at all in 10.2, but thought that might be fixed in 10.3). I'll go back to the 9200 and try your suggestion on that card. (The default 10.3 install did not work with the 9200, which is why I tried switching cards).
FYI I also tried the fglrx driver on the 9800 pro last night and I could not even see the command line with that driver. Fortunately uninstalling the fglrx drivers from yast did get me back to at least seeing the command line. Switching driver from radeon to vesa makes no difference, command line but no kde.
Thanks for the suggestion, will try the 9200 again later today.
Jim F
=========== Have you guys tried the "ati" driver instead of the "radeon"? I know both seem to work for me, but the differences were usually the cards they worked with, which may be the case with you. Either run sax2 with ati sax2 -m 0=ati or just change the driver in xorg.conf to test it. Lee -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
BandiPat wrote:
On Tuesday 16 October 2007, Jim Flanagan wrote:
Joe Morris (NTM) wrote:
On 10/16/2007 11:02 AM, Jim Flanagan wrote:
OK, you are most correct, the driver was radeon. I changed it to vesa, then rebooted, but no change in behavior, not GUI at all. I only get to command line.
FWIW, I also have a 9200 (SE) using the radeon driver. Selecting 3D did not work originally (monitor could not sync). I noticed in the log agpgart was trying to work in 8x. In 10.2 it worked in 4x, so I set up 3D and added "AGPMode" "4" via sax2, and mine worked again immediately. There may be a problem with the driver. When i used fglrx, it did work in 8x. Anyway, try adding the agp limitation and retry.
Hi Joe, I noticed your post in the other thread about agp in 4x mode, and did try that. It did not work in my case. But, I had already switched video cards out. At present I'm running (or trying to run) the ATI 9800 Pro. (I could not get this card to run at all in 10.2, but thought that might be fixed in 10.3). I'll go back to the 9200 and try your suggestion on that card. (The default 10.3 install did not work with the 9200, which is why I tried switching cards).
FYI I also tried the fglrx driver on the 9800 pro last night and I could not even see the command line with that driver. Fortunately uninstalling the fglrx drivers from yast did get me back to at least seeing the command line. Switching driver from radeon to vesa makes no difference, command line but no kde.
Thanks for the suggestion, will try the 9200 again later today.
Jim F
===========
Have you guys tried the "ati" driver instead of the "radeon"? I know both seem to work for me, but the differences were usually the cards they worked with, which may be the case with you.
Either run sax2 with ati sax2 -m 0=ati or just change the driver in xorg.conf to test it.
Lee
Hi Lee, Will try that too. Will revert. Thanks, Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
BandiPat wrote:
On Tuesday 16 October 2007, Jim Flanagan wrote:
Joe Morris (NTM) wrote:
On 10/16/2007 11:02 AM, Jim Flanagan wrote:
OK, you are most correct, the driver was radeon. I changed it to vesa, then rebooted, but no change in behavior, not GUI at all. I only get to command line.
FWIW, I also have a 9200 (SE) using the radeon driver. Selecting 3D did not work originally (monitor could not sync). I noticed in the log agpgart was trying to work in 8x. In 10.2 it worked in 4x, so I set up 3D and added "AGPMode" "4" via sax2, and mine worked again immediately. There may be a problem with the driver. When i used fglrx, it did work in 8x. Anyway, try adding the agp limitation and retry.
Hi Joe, I noticed your post in the other thread about agp in 4x mode, and did try that. It did not work in my case. But, I had already switched video cards out. At present I'm running (or trying to run) the ATI 9800 Pro. (I could not get this card to run at all in 10.2, but thought that might be fixed in 10.3). I'll go back to the 9200 and try your suggestion on that card. (The default 10.3 install did not work with the 9200, which is why I tried switching cards).
FYI I also tried the fglrx driver on the 9800 pro last night and I could not even see the command line with that driver. Fortunately uninstalling the fglrx drivers from yast did get me back to at least seeing the command line. Switching driver from radeon to vesa makes no difference, command line but no kde.
Thanks for the suggestion, will try the 9200 again later today.
Jim F
===========
Have you guys tried the "ati" driver instead of the "radeon"? I know both seem to work for me, but the differences were usually the cards they worked with, which may be the case with you.
Either run sax2 with ati sax2 -m 0=ati or just change the driver in xorg.conf to test it.
Lee
Ok, I tried the ati driver with the radeon 9800 pro card. Makes no difference, does not work either. Then I tried setting agpmode to 4x, but that did not get me to a destop either, with 4 different drivers, vesa, radeon, ati, and flgrx. So I re-installed the 9200, and my monitor says "mode out of range", which happens with this card during default res installation, Don't even see the command line running by on boot. This with the vesa, radeon, and ati driver. I can edit the 10.3 xrog.conf file from my 10.2 install, but I don't know what to change to make this card feed something my monitor can handle. So I'll do a re-install of 10.3 again. At this point the only thing I can think of that I haven't tried, is the ati fglrx driver with 10.3 on the 9200 card. I'll try that and report back. After that I'm out of ideas. Any more thoughts would be most helpful. I was really hoping 10.3 would be "it" for me. Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/19/2007 06:34 AM, Jim Flanagan wrote:
Ok, I tried the ati driver with the radeon 9800 pro card. Makes no difference, does not work either. Then I tried setting agpmode to 4x, but that did not get me to a destop either, with 4 different drivers, vesa, radeon, ati, and flgrx. So I re-installed the 9200, and my monitor says "mode out of range", which happens with this card during default res installation, Don't even see the command line running by on boot. This with the vesa, radeon, and ati driver.
So it sounds to me like it is your monitor specs which are causing your problems. Do you know the specs? You could add them to the Monitor database so sax2 gets it right to start with. Also, if the boot screens are not visible, which are using frame buffer mode, you need to replace the vga= line in your grub menu.lst. What do you have there? You can pass this on boot also, i.e. vga=ask, or vga=0x31a (which is 1280x1024x64k, check /usr/src/linux/Documentation/fb/vesafb.txt if you have kernel sources installed). What is your monitor? I think your monitor is not well supported automatically is more your problem than your video card.
I can edit the 10.3 xrog.conf file from my 10.2 install, but I don't know what to change to make this card feed something my monitor can handle. Section Monitor would help. So I'll do a re-install of 10.3 again. At this point the only thing I can think of that I haven't tried, is the ati fglrx driver with 10.3 on the 9200 card. I'll try that and report back. After that I'm out of ideas.
Hope it works, but a reinstall seems drastic. If you want, i can send you my xorg.conf, but since they are not exactly the same, it could only be a reference, which I'm sure you have already. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris (NTM) wrote:
On 10/19/2007 06:34 AM, Jim Flanagan wrote:
Ok, I tried the ati driver with the radeon 9800 pro card. Makes no difference, does not work either. Then I tried setting agpmode to 4x, but that did not get me to a destop either, with 4 different drivers, vesa, radeon, ati, and flgrx. So I re-installed the 9200, and my monitor says "mode out of range", which happens with this card during default res installation, Don't even see the command line running by on boot. This with the vesa, radeon, and ati driver.
So it sounds to me like it is your monitor specs which are causing your problems. Do you know the specs? You could add them to the Monitor database so sax2 gets it right to start with. Also, if the boot screens are not visible, which are using frame buffer mode, you need to replace the vga= line in your grub menu.lst. What do you have there? You can pass this on boot also, i.e. vga=ask, or vga=0x31a (which is 1280x1024x64k, check /usr/src/linux/Documentation/fb/vesafb.txt if you have kernel sources installed). What is your monitor? I think your monitor is not well supported automatically is more your problem than your video card.
I can edit the 10.3 xrog.conf file from my 10.2 install, but I don't know what to change to make this card feed something my monitor can handle.
Section Monitor would help.
So I'll do a re-install of 10.3 again. At this point the only thing I can think of that I haven't tried, is the ati fglrx driver with 10.3 on the 9200 card. I'll try that and report back. After that I'm out of ideas.
Hope it works, but a reinstall seems drastic. If you want, i can send you my xorg.conf, but since they are not exactly the same, it could only be a reference, which I'm sure you have already.
Hi Joe, My monitor works OK, but 1280x1024 wont run on my radeon 9200 card. If I set the boot to 1024x768 I can see the boot screen, and the text. Thanks for pointing out how to set that in grub. For some reason the installer on 10.3 and 10.2 does not detect that so I have to set the res first then all goes well. Until I get to runlevel 5, then no gui. I tried a different vid card, but with the known good card, 9200, 10.3 will not run kdm. 10.2 does. I just installed the ati fglrx driver to run wtih the 9200, but that does not work either. So all 4 drivers I've tried, vesa, ati, radeon and fglrx will not boot into a gui. Short of changing my mother board, I guess I can try buying an inexpensive nvidia card. But I really don't want to spend the $$ on an agp card. Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris (NTM) wrote:
On 10/19/2007 06:34 AM, Jim Flanagan wrote:
So I re-installed the 9200, and my monitor says "mode out of range", which happens with this card during default res installation, Don't even see the command line running by on boot.
So it sounds to me like it is your monitor specs which are causing your problems. Do you know the specs?
My monitor works OK, but 1280x1024 wont run on my radeon 9200 card. I realize mine is an 9200 SE, but I don't think they are that different. Mine is currently running 1280x1024. If I set the boot to 1024x768 I can see the boot screen, and the text. So there is progress. Sounds like the frequencies of your monitor are not compatible with what the card puts out at particular resolutions. Thanks for pointing out how to set that in grub. For some reason the installer on 10.3 and 10.2 does not detect that so I have to set the res first then all goes well. This is something you set when you first install. There is no way for it to set this before it has run. I believe it is F2 or F3. Until I get to runlevel 5, then no gui. Is your monitor blanking out? Loosing sync? What happens? I tried a different vid card, but with the known good card, 9200, 10.3 will not run kdm. 10.2 does. Is the monitor section from 10.2 the same as 10.3? How about the mode
On 10/19/2007 10:40 PM, Jim Flanagan wrote: lines?
I just installed the ati fglrx driver to run wtih the 9200, but that does not work either.
I believe the card is getting wrong info about the capabilities of your monitor and are pushing it beyond its limit.
So all 4 drivers I've tried, vesa, ati, radeon and fglrx will not boot into a gui. You changed the drivers, did you change your monitor info? If they all get the wrong info and overdrive your monitor, because it thinks it is capable of a high horizontal freq or something, it will cause your monitor to blank. Short of changing my mother board, I guess I can try buying an inexpensive nvidia card. But I really don't want to spend the $$ on an agp card. I am not sure that would even fix it I'm afraid. Is your monitor auto detected? Can you boot to runlevel 3? Can you run sax2?
-- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris (NTM) wrote:
On 10/19/2007 10:40 PM, Jim Flanagan wrote:
Joe Morris (NTM) wrote:
On 10/19/2007 06:34 AM, Jim Flanagan wrote:
So I re-installed the 9200, and my monitor says "mode out of range", which happens with this card during default res installation, Don't even see the command line running by on boot.
So it sounds to me like it is your monitor specs which are causing your problems. Do you know the specs?
My monitor works OK, but 1280x1024 wont run on my radeon 9200 card.
I realize mine is an 9200 SE, but I don't think they are that different. Mine is currently running 1280x1024.
If I set the boot to 1024x768 I can see the boot screen, and the text.
So there is progress. Sounds like the frequencies of your monitor are not compatible with what the card puts out at particular resolutions.
Thanks for pointing out how to set that in grub. For some reason the installer on 10.3 and 10.2 does not detect that so I have to set the res first then all goes well.
This is something you set when you first install. There is no way for it to set this before it has run. I believe it is F2 or F3.
Until I get to runlevel 5, then no gui.
Is your monitor blanking out? Loosing sync? What happens?
I tried a different vid card, but with the known good card, 9200, 10.3 will not run kdm. 10.2 does.
Is the monitor section from 10.2 the same as 10.3? How about the mode lines?
I just installed the ati fglrx driver to run wtih the 9200, but that does not work either.
I believe the card is getting wrong info about the capabilities of your monitor and are pushing it beyond its limit.
So all 4 drivers I've tried, vesa, ati, radeon and fglrx will not boot into a gui.
You changed the drivers, did you change your monitor info? If they all get the wrong info and overdrive your monitor, because it thinks it is capable of a high horizontal freq or something, it will cause your monitor to blank.
Short of changing my mother board, I guess I can try buying an inexpensive nvidia card. But I really don't want to spend the $$ on an agp card.
I am not sure that would even fix it I'm afraid. Is your monitor auto detected? Can you boot to runlevel 3? Can you run sax2?
I may have put too many variables in my post. I do have a monitor sync
issue, but I can work around that. My main issue is that during boot of
a clean 10.3 install, I see the splash screens, and can press esc to see
the boot txt scroll by, but when the system reached runlevel 5 it won't
run kdm. I can vnc into it at that point from another box, but the local
kdm will not start. Sax2 fails to run, and gives an error meesage saying
to see /var/log/SaX.log (see attached).
In the boot txt I also see a line that says gdm is unknown, but I have
not installed gdm, only kdm.
Jim F
===========
/var/log/SaX.log
/*************
SaX2 log : SaX2 version 8.1 - SVN Release: 1.49 2003/03/17
**************
SVN RELEASE : 1443
:
DESCRIPTION : X11 configuration log file to collect information
: about detection, startup and configuration.
: There are three parts of logging:
: ---
: 1) INIT ( detection, 3D )
: 2) STARTUP ( xorg.conf, X11 log, glxinfo )
: 3) CONFIG ( config actions )
: ---
:
VERSION : SaX2 compiled for: [openSUSE 10.3 (i586)]
PARAMETER : -r
:
LOG DATE : Fri Oct 19 10:11:12 CDT 2007
*************/
============================
Framebuffer Info:
----------------------------
Framebuffer is active
19-Oct 10:11:13 <I> Initializing...
19-Oct 10:11:15 <I> [ Sysp: Mouse detection data
Mouse0 => Protocol : explorerps/2
Mouse0 => Device : /dev/input/mice
Mouse0 => Buttons : 12
Mouse0 => Wheel : 2
Mouse0 => Emulate : 0
Mouse0 => Name : PS2++ Logitech MX Mouse
Mouse0 => VendorID : 0x0210
Mouse0 => DeviceID : 0x0028
Mouse0 => Profile : logitech-mxlaser
Mouse0 => RealDevice : <undefined>
Mouse0 => NutShell : 0
]
19-Oct 10:11:15 <I> [ Sysp: Keyboard detection data
Keyboard0 => XkbModel : microsoftpro
Keyboard0 => XkbLayout : us
Keyboard0 => Name : AT Translated Set 2 keyboard
Keyboard0 => VendorID : 0x0211
Keyboard0 => DeviceID : 0x0001
Keyboard0 => Profile : <undefined>
Keyboard0 => RealDevice : /dev/input/event0
]
19-Oct 10:11:15 <I> [ Sysp: Server detection data
Card0 => DomainId : 0x0
Card0 => BusId : 0x2
Card0 => SlotId : 0x00
Card0 => FuncId : 0x0
Card0 => Vendor : ATI
Card0 => Device : RV250 If
Card0 => VID : 0x1002
Card0 => DID : 0x4966
Card0 => Module : radeon
Card0 => BusType : AGP
Card0 => Detected : 1
Card0 => Flag : DEFAULT
Card0 => SUB-VID : 0x1002
Card0 => SUB-DID : 0x2002
Card0 => DrvProfile : Depth24,Radeon
]
19-Oct 10:11:26 <I> [ Sysp: XStuff detection data
Card0 => DDC : PTS2517
Card0 => DDC[2] : PTS2517
Card0 => Name : PROVIEW LT782s
Card0 => Vendor : PTS
Card0 => Name[2] : PROVIEW LT782s
Card0 => Vendor[2] : PTS
Card0 => Primary : 02-00-0
Card0 => Chipset : <undefined>
Card0 => Vsync : 75
Card0 => Hsync : 80
Card0 => Vsync[2] : 75
Card0 => Hsync[2] : 80
Card0 => Vesa : 800 600 36 60
Card0 => Vesa : 800 600 43 72
Card0 => Vesa : 800 600 45 75
Card0 => Vesa : 1024 768 46 60
Card0 => Vesa : 1024 768 53 70
Card0 => Vesa : 1024 768 57 75
Card0 => Vesa : 1280 1024 76 75
Card0 => Vesa : 1280 1024 61 60
Card0 => Vesa : 1280 1024 80 75
Card0 => Vesa[2] : 800 600 36 60
Card0 => Vesa[2] : 800 600 43 72
Card0 => Vesa[2] : 800 600 45 75
Card0 => Vesa[2] : 1024 768 46 60
Card0 => Vesa[2] : 1024 768 53 70
Card0 => Vesa[2] : 1024 768 57 75
Card0 => Vesa[2] : 1280 1024 76 75
Card0 => Vesa[2] : 1280 1024 61 60
Card0 => Vesa[2] : 1280 1024 80 75
Card0 => Dacspeed : 108
Card0 => Dacspeed[2]: 108
Card0 => Modeline : 1280 1328 1440 1688 1024 1025 1028 1066 +/+
Card0 => Modeline[2]: 1280 1328 1440 1688 1024 1025 1028 1066 +/+
Card0 => Memory : 65536
Card0 => RandR : <undefined>
Card0 => Current : 02-00-0
Card0 => RawDef : None
Card0 => Option : None
Card0 => Extension : None
Card0 => Module : radeon
Card0 => Display : LCD/TFT
Card0 => Display[2] : LCD/TFT
Card0 => Size : 337x270
Card0 => Size[2] : 337x270
Card0 => VesaBios : 2.0
Card0 => FBBoot : 800 600 8 771
Card0 => FBBoot : 800 600 15 787
Card0 => FBBoot : 800 600 16 788
Card0 => FBBoot : 800 600 24 789
Card0 => FBBoot : 800 600 24 802
Card0 => FBBoot : 1024 768 8 773
Card0 => FBBoot : 1024 768 15 790
Card0 => FBBoot : 1024 768 16 791
Card0 => FBBoot : 1024 768 24 792
Card0 => FBBoot : 1024 768 24 803
Card0 => FBBoot : 1280 1024 8 775
Card0 => FBBoot : 1280 1024 15 793
Card0 => FBBoot : 1280 1024 16 794
Card0 => FBBoot : 1280 1024 24 795
Card0 => FBBoot : 1280 1024 24 804
]
19-Oct 10:11:28 <I> [ Sysp: 3D detection data
Card3D0 => Install : <none>
Card3D0 => Remove : <none>
Card3D0 => Packages : <none>
Card3D0 => Active : 0
Card3D0 => Answer : no
Card3D0 => ScriptReal : <none>
Card3D0 => ScriptSoft : <none>
Card3D0 => Flag : <none>
]
19-Oct 10:11:31 <X> Startup...
19-Oct 10:11:31 <X> Startup on new Server: <:0.0>
19-Oct 10:11:31 <X> Logging File contents: /tmp/sax2-4011/xorg.conf [
# /.../
# SaX generated X11 config file
# Created on: 2007-10-19T10:11:31-0500.
#
# Version: 8.1
# Contact: Marcus Schaefer
On 10/19/2007 11:54 PM, Jim Flanagan wrote:
My main issue is that during boot of a clean 10.3 install, I see the splash screens, and can press esc to see the boot txt scroll by, OK, this is using the video card's frame buffer. but when the system reached runlevel 5 it won't run kdm. This is because of a non functional xorg.conf. I can vnc into it at that point from another box, but the local kdm will not start. So the local X isn't working. Sax2 fails to run, and gives an error meesage saying to see /var/log/SaX.log (see attached).
And the error message was? Wasn't there more of an error than to just see sax2.log?
In the boot txt I also see a line that says gdm is unknown, but I have not installed gdm, only kdm.
That is a separate bug, not an issue here.
=========== /var/log/SaX.log /************* SaX2 log : SaX2 version 8.1 - SVN Release: 1.49 2003/03/17 ************** SVN RELEASE : 1443 <snip> 19-Oct 10:11:26 <I> [ Sysp: XStuff detection data Card0 => DDC : PTS2517 Card0 => DDC[2] : PTS2517 Card0 => Name : PROVIEW LT782s Card0 => Vendor : PTS Card0 => Name[2] : PROVIEW LT782s
This is correct for your monitor?
Card0 => Vendor[2] : PTS Card0 => Primary : 02-00-0 Card0 => Chipset : <undefined> Card0 => Vsync : 75 Card0 => Hsync : 80 Card0 => Vsync[2] : 75 Card0 => Hsync[2] : 80
Will it support these upper limits for its frequencies?
Card0 => Vesa : 800 600 36 60 Card0 => Vesa : 800 600 43 72 Card0 => Vesa : 800 600 45 75 Card0 => Vesa : 1024 768 46 60 Card0 => Vesa : 1024 768 53 70 Card0 => Vesa : 1024 768 57 75 Card0 => Vesa : 1280 1024 76 75 Card0 => Vesa : 1280 1024 61 60 Card0 => Vesa : 1280 1024 80 75
These are all possible resolutions. You mentioned before you had to make changes for your frame buffer to work with your monitor. It did not work at 1280x1024. IIRC you changed it to 1024x768 and it worked. Notice above how much lower the horizontal frequencies are for those resolutions.
Card0 => Modeline : 1280 1328 1440 1688 1024 1025 1028 1066 +/+
This was the chosen mode line. So it will try starting it up at 1280x1024. If it cannot handle 80 for horiz or 75 for vert, your monitor will not work.
Card0 => Display : LCD/TFT
Is this true? Is your monitor an LCD? Most do not like such a high vert. freq. Even though mine says it works at 75, it shifts the display. I need to tweak mine to 72 limit to force a lower freq mode line, which works perfectly. Most LCDs are great with 60.
Section "Monitor" Option "CalcAlgorithm" "XServerPool" DisplaySize 337 270 HorizSync 30-80 Identifier "Monitor[0]" ModelName "PROVIEW LT782S" Option "DPMS" VendorName "PTS" VertRefresh 43-75 UseModes "Modes[0]" EndSection
Section "Modes" Identifier "Modes[0]" EndSection
Looks like no identified modes. I have read here that sometimes this is OK, as it is determined differently. Mine has: Section "Modes" Identifier "Modes[0]" Modeline "1152x864" 99.64 1152 1224 1344 1536 864 865 868 901 Modeline "1152x864" 83.25 1152 1200 1232 1312 864 867 871 894 +HSync -VSync Modeline "1024x768" 78.43 1024 1080 1192 1360 768 769 772 801 Modeline "1024x768" 66.50 1024 1072 1104 1184 768 771 775 794 +HSync -VSync Modeline "800x600" 46.87 800 840 920 1040 600 601 604 626 Modeline "800x600" 42.25 800 848 880 960 600 603 607 621 +HSync -VSync Modeline "1280x1024" 108.00 1280 1328 1440 1688 1024 1025 1028 1066 EndSection
(II) ATI Proprietary Linux Driver Version Identifier:8.41.7 (II) ATI Proprietary Linux Driver Release Identifier: UNSUPPORTED-8.413.1 (II) ATI Proprietary Linux Driver Build Date: Sep 7 2007 22:35:20 (WW) fglrx: No matching Device section for instance (BusID PCI:2:0:1) found (EE) No devices detected.
Fatal server error: no screens found ]
I believe this is saying it could not find a resolution it could use that would be accepted by your monitor. From what I am able to find, it is best at 1280x1024x60Hz. I think this is the problem. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris (NTM) wrote:
On 10/19/2007 11:54 PM, Jim Flanagan wrote:
My main issue is that during boot of a clean 10.3 install, I see the splash screens, and can press esc to see the boot txt scroll by,
OK, this is using the video card's frame buffer.
but when the system reached runlevel 5 it won't run kdm.
This is because of a non functional xorg.conf.
I can vnc into it at that point from another box, but the local kdm will not start.
So the local X isn't working.
Sax2 fails to run, and gives an error meesage saying to see /var/log/SaX.log (see attached).
And the error message was? Wasn't there more of an error than to just see sax2.log?
In the boot txt I also see a line that says gdm is unknown, but I have not installed gdm, only kdm.
That is a separate bug, not an issue here.
=========== /var/log/SaX.log /************* SaX2 log : SaX2 version 8.1 - SVN Release: 1.49 2003/03/17 ************** SVN RELEASE : 1443 <snip> 19-Oct 10:11:26 <I> [ Sysp: XStuff detection data Card0 => DDC : PTS2517 Card0 => DDC[2] : PTS2517 Card0 => Name : PROVIEW LT782s Card0 => Vendor : PTS Card0 => Name[2] : PROVIEW LT782s
This is correct for your monitor?
Card0 => Vendor[2] : PTS Card0 => Primary : 02-00-0 Card0 => Chipset : <undefined> Card0 => Vsync : 75 Card0 => Hsync : 80 Card0 => Vsync[2] : 75 Card0 => Hsync[2] : 80
Will it support these upper limits for its frequencies?
Card0 => Vesa : 800 600 36 60 Card0 => Vesa : 800 600 43 72 Card0 => Vesa : 800 600 45 75 Card0 => Vesa : 1024 768 46 60 Card0 => Vesa : 1024 768 53 70 Card0 => Vesa : 1024 768 57 75 Card0 => Vesa : 1280 1024 76 75 Card0 => Vesa : 1280 1024 61 60 Card0 => Vesa : 1280 1024 80 75
These are all possible resolutions. You mentioned before you had to make changes for your frame buffer to work with your monitor. It did not work at 1280x1024. IIRC you changed it to 1024x768 and it worked. Notice above how much lower the horizontal frequencies are for those resolutions.
Card0 => Modeline : 1280 1328 1440 1688 1024 1025 1028 1066 +/+
This was the chosen mode line. So it will try starting it up at 1280x1024. If it cannot handle 80 for horiz or 75 for vert, your monitor will not work.
Card0 => Display : LCD/TFT
Is this true? Is your monitor an LCD? Most do not like such a high vert. freq. Even though mine says it works at 75, it shifts the display. I need to tweak mine to 72 limit to force a lower freq mode line, which works perfectly. Most LCDs are great with 60.
Section "Monitor" Option "CalcAlgorithm" "XServerPool" DisplaySize 337 270 HorizSync 30-80 Identifier "Monitor[0]" ModelName "PROVIEW LT782S" Option "DPMS" VendorName "PTS" VertRefresh 43-75 UseModes "Modes[0]" EndSection
Section "Modes" Identifier "Modes[0]" EndSection
Looks like no identified modes. I have read here that sometimes this is OK, as it is determined differently. Mine has: Section "Modes" Identifier "Modes[0]" Modeline "1152x864" 99.64 1152 1224 1344 1536 864 865 868 901 Modeline "1152x864" 83.25 1152 1200 1232 1312 864 867 871 894 +HSync -VSync Modeline "1024x768" 78.43 1024 1080 1192 1360 768 769 772 801 Modeline "1024x768" 66.50 1024 1072 1104 1184 768 771 775 794 +HSync -VSync Modeline "800x600" 46.87 800 840 920 1040 600 601 604 626 Modeline "800x600" 42.25 800 848 880 960 600 603 607 621 +HSync -VSync Modeline "1280x1024" 108.00 1280 1328 1440 1688 1024 1025 1028 1066 EndSection
(II) ATI Proprietary Linux Driver Version Identifier:8.41.7 (II) ATI Proprietary Linux Driver Release Identifier: UNSUPPORTED-8.413.1 (II) ATI Proprietary Linux Driver Build Date: Sep 7 2007 22:35:20 (WW) fglrx: No matching Device section for instance (BusID PCI:2:0:1) found (EE) No devices detected.
Fatal server error: no screens found ]
I believe this is saying it could not find a resolution it could use that would be accepted by your monitor. From what I am able to find, it is best at 1280x1024x60Hz. I think this is the problem.
Hi Joe, thanks for the rundown. My xorg.conf shows the correct monitor, an lcd. Under opensuse 10.2 it ran kde at 1600x1200 in the gui, but I think that is different than the boot res. In any case, based on your post, I did a clean re-install of 10.3 and made sure to set the res to 1024x768 at the end of the installer config setup. This still did not load x, I only see the command line saying runlevel 5 has been reached. I do not think this is a monitor problem. When this monitor gets a signal it can't handle, it shows a little blue window saying mode is out of range. This is not happening at this point. Only X is not loading. So I log in and run sax2. This tries to load, the screen goes black for a few moments, then the command line comes back saying that sax failed to load, and to see the SaX.log. Thats the only error. But this means that I can't use sax to correct any problem here, it simply won't load. This did not happen with 10.2. This card ran fine with the default settings, sax2 ran if I needed it, and I could enable 3d which worked well too. Not at all with 10.3. Without sax2 to work with, I'm not sure how to set the res to 1024x768 at 60 hz by editing xorg.conf. So at this point thinking there is something in my hardware that 10.3 didn't like, I went out and bought a cheap nvidia geforce2 mx 400 agp card. Did a new clean install to make sure that it was picked up right, and after all that I still did not get x, only the command line showing runlevel 5. Again, sax2 would not run, with the same error as before. (In this case I could not even vnc into the box like I could with the previous radeon card). I was certain that 10.3 would work with a card this old, but it didn't. So, thinking that perhaps the issue was with 10.3 and AGP on this board, I went out a bought a not so cheap PCI (not PCI-E) nvidia 6200 card. Again, I did a complete clean reinstall, but unfortunately still did not get X to start, only the command line in runlevel 5. Again sax2 failed to run with the same error as the rest. So, I believe I ruled out an AGP problem on this board as 1) it works fine with 10.2 and 2) a PCI card won't work with 10.3 either. So, thinking that it must be a 10.3 issue, I installed 2 different distros (something I had never done before). Pclinuxos and zenwalk both run fine in gui, pclinuxos is running at 1280x1024 at 60hz. I don't recall what zenwalk ran at, but it was higher than that. So, to me this must be a 10.3 issue. If I'm on the wrong track guys please let me know. I'm not at all sure what to do next as I've never seen a problem where nothing you try works. Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2007/10/20 23:38 (GMT-0500) Jim Flanagan apparently typed:
(EE) No devices detected.
No devices, no video. Need to focus on why it can't find devices. If you still have a functional xorg.conf file from 10.2 around, I'd start evaluating differences from the 10.3 versions you've tried so far, maybe even try that file as is.
Fatal server error: no screens found
It'll never find any screens without first finding device(s) (gfxcard, with video ram and acceptable modelines).
I believe this is saying it could not find a resolution it could use that would be accepted by your monitor.
Resolution is something it can't manage to work out prior to finding hardware to apply it to.
Hi Joe, thanks for the rundown. My xorg.conf shows the correct monitor, an lcd. Under opensuse 10.2 it ran kde at 1600x1200 in the gui
Xorg keeps getting smarter and dumber. Some people are able to run X with no xorg.conf file at all - that's the ultimate goal of the project - or, like me, at least an xorg.conf version containing no modelines. I'd start by trying no file at all. If it works, it's a good start. If not, you need to focus on (EE) lines in Xorg.0.log. First, unless you're skilled at manually manipulating xorg.conf, you'll need to get sax2 to work, focusing on whatever error messages you find in SaX.log. If you can't sort that out on your own, including looking through Novell's Bugzilla for similar trouble, ask here for more, but without bombing everyone with loads of data each time. Put the logs and xorg.conf on pastebin or personal web space, including only those links in the list email. I don't believe there's any possibility you won't be able to make 10.3 work at 1600x1200 with at least one of those gfxcards if 10.2 did. But, stop with fresh installs, and direct your energy at the logs - they're pretty good at pointing to what needs fixing. If you really feel compelled to keep installing in hope something will turn out differently, I suggest an HTTP install from Factory. If that too fails, then, assuming you can't find an existing one on point, file a bug, and let the development experts spot the reason for failure. -- "The basis of our Bill of Rights comes from the teachings we get from Exodus and St. Matthew, from Isaiah and St. Paul. President Harry S. Truman Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Felix Miata wrote:
On 2007/10/20 23:38 (GMT-0500) Jim Flanagan apparently typed:
(EE) No devices detected.
No devices, no video. Need to focus on why it can't find devices. If you still have a functional xorg.conf file from 10.2 around, I'd start evaluating differences from the 10.3 versions you've tried so far, maybe even try that file as is.
<snip>
If you can't sort that out on your own, including looking through Novell's Bugzilla for similar trouble, ask here for more, but without bombing everyone with loads of data each time. Put the logs and xorg.conf on pastebin or personal web space, including only those links in the list email.
I don't believe there's any possibility you won't be able to make 10.3 work at 1600x1200 with at least one of those gfxcards if 10.2 did. But, stop with fresh installs, and direct your energy at the logs - they're pretty good at pointing to what needs fixing. If you really feel compelled to keep installing in hope something will turn out differently, I suggest an HTTP install from Factory. If that too fails, then, assuming you can't find an existing one on point, file a bug, and let the development experts spot the reason for failure.
Copying over the xorg.conf file from my10.2 install did work. I get X in 10.3 for the first time. Not perfectly, but it is up. Great idea to look at/copy over. Sax runs from within yast, but it still will not run in command line at runlevel 3, running sax2 with no args. For some reason not reading in my pasted in xorg.conf causes sax2 to fail on this box. Why would sax run in yast, but not in command line? I guess in yast it is reading in current config. That means there is something about my system that it is not picking up. Will keep investigating..... Many thanks, Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 21 October 2007 10:11:04 am Jim Flanagan wrote:
Why would sax run in yast, but not in command line? I guess in yast it is reading in current config. That means there is something about my system that it is not picking up. Will keep investigating.....
To tell sax2 to use current configuration: sax2 -s It will interesting anyway to see Xorg.0.log produced by bad xorg.conf. As Felix suggested: http://pastebin.com/ -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 20 October 2007 11:38:16 pm Jim Flanagan wrote: ...
So, thinking that it must be a 10.3 issue, I installed 2 different distros (something I had never done before). Pclinuxos and zenwalk both run fine in gui, pclinuxos is running at 1280x1024 at 60hz. I don't recall what zenwalk ran at, but it was higher than that.
So, to me this must be a 10.3 issue. If I'm on the wrong track guys please let me know. I'm not at all sure what to do next as I've never seen a problem where nothing you try works.
.... Sax2.log ---------
19-Oct 10:11:15 <I> [ Sysp: Server detection data Card0 => DomainId : 0x0 Card0 => BusId : 0x2 Card0 => SlotId : 0x00 Card0 => FuncId : 0x0
# Which is 2:0:0 xorg.conf ---------
Section "Device" BoardName "RV250 If" BusID "2:0:0"
# and that is written in configuration Xorg.0.log: --------- ...
(II) PCI: PCI scan (all values are in hex) ... (II) PCI: 02:00:1: chip 1002,496e card 1002,2003 rev 01 class 03,80,00 hdr 00
# PCI: 02:00:1 ??
(II) PCI: End of PCI scan ... (II) Primary Device is: PCI 02:00:0 (WW) fglrx: No matching Device section for instance (BusID PCI:2:0:1) found
# sax2 and Xorg see different BusID's. That can be xorg or sax2. You may try to change manually xorg.conf line: BusID "2:0:0" to BusID "2:0:1" and see if that helps. If you have multiboot, it will be fine if you can supply head var/log/Xorg.0.log for all distros. You can snip output below 'Current Operating System:' line. That will tell what version of X Window System they use. It will be interesting to see what nvidia Xorg.0.log tells. BTW, do you have any other Xorg logs in /var/log/ -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 21 October 2007 12:50:32 am Rajko M. wrote:
On Saturday 20 October 2007 11:38:16 pm Jim Flanagan wrote:
...
So, thinking that it must be a 10.3 issue, I installed 2 different distros (something I had never done before). Pclinuxos and zenwalk both run fine in gui, pclinuxos is running at 1280x1024 at 60hz. I don't recall what zenwalk ran at, but it was higher than that.
So, to me this must be a 10.3 issue. If I'm on the wrong track guys please let me know. I'm not at all sure what to do next as I've never seen a problem where nothing you try works.
.... Sax2.log ---------
19-Oct 10:11:15 <I> [ Sysp: Server detection data Card0 => DomainId : 0x0 Card0 => BusId : 0x2 Card0 => SlotId : 0x00 Card0 => FuncId : 0x0
# Which is 2:0:0
xorg.conf ---------
Section "Device" BoardName "RV250 If" BusID "2:0:0"
# and that is written in configuration
Xorg.0.log: --------- ...
(II) PCI: PCI scan (all values are in hex)
...
(II) PCI: 02:00:1: chip 1002,496e card 1002,2003 rev 01 class 03,80,00 hdr 00
# PCI: 02:00:1 ??
(II) PCI: End of PCI scan
...
(II) Primary Device is: PCI 02:00:0 (WW) fglrx: No matching Device section for instance (BusID PCI:2:0:1) found
# sax2 and Xorg see different BusID's.
That can be xorg or sax2. You may try to change manually xorg.conf line: BusID "2:0:0" to BusID "2:0:1" and see if that helps.
If you have multiboot, it will be fine if you can supply head var/log/Xorg.0.log for all distros. You can snip output below 'Current Operating System:' line. That will tell what version of X Window System they use.
It will be interesting to see what nvidia Xorg.0.log tells. BTW, do you have any other Xorg logs in /var/log/
-- Regards, Rajko.
Looking explanation of warning 'no matching Device section for instance(BusIDPCI:' this thread showed up in results: http://lists.freedesktop.org/archives/xorg/2005-October/010923.html -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rajko M. wrote:
On Saturday 20 October 2007 11:38:16 pm Jim Flanagan wrote:
...
So, thinking that it must be a 10.3 issue, I installed 2 different distros (something I had never done before). Pclinuxos and zenwalk both run fine in gui, pclinuxos is running at 1280x1024 at 60hz. I don't recall what zenwalk ran at, but it was higher than that.
So, to me this must be a 10.3 issue. If I'm on the wrong track guys please let me know. I'm not at all sure what to do next as I've never seen a problem where nothing you try works.
<snip>
# sax2 and Xorg see different BusID's.
That can be xorg or sax2. You may try to change manually xorg.conf line: BusID "2:0:0" to BusID "2:0:1" and see if that helps.
If you have multiboot, it will be fine if you can supply head var/log/Xorg.0.log for all distros. You can snip output below 'Current Operating System:' line. That will tell what version of X Window System they use.
It will be interesting to see what nvidia Xorg.0.log tells. BTW, do you have any other Xorg logs in /var/log/
OK guys, sorry for the delay, its been a busy week. (I don't know if its best to keep posting here or start a new thread, but as this one is pretty mangled anyway, I'll post here, hope you see it). I had some grub problems to sort out as well. As I said in my last post, I took the other cards back and am staying with my existing radeon 9000 for the moment. It worked acceptably in 10.2. My clean 10.3 install will not load X, nor will sax2 run. I pasted into 10.3 the xorg.conf from 10.2. This does get X up and I can log in, but not reliably, certainly not optimally. Sometimes the bottom 1/6th or so of the screen is black showing no kikker, but most times I get a full screen. Sometimes apps like Thunderbird freeze with warning to terminate it. So I still have some work to do here. I have not tried changing the PCI bus to "2.0.1". Also as I said before, sax will run in yast, but not in cli, runlevel 5 or 3. Here are logs currently on the system: xorg.conf from 10.2 but after running yast>sax in 10.3 that I'm running now http://pastebin.com/m24b230f xorg.conf from the 10.3 install that did not work http://pastebin.com/m4a33cb60 sax.log after running yast>sax in 10.3 http://pastebin.com/m40037ff1 Xorg.0.log http://pastebin.com/m883c4cb Xorg.99.log http://pastebin.com/m7325d2d0 I don't know if this is helpful or not, but the test install I did of pclinuxos loaded this card with no problems and runs glxgears at about 2200fps on this card (about 7 times faster than I'm getting in 10.3). pclox xorg.conf http://pastebin.com/m7eb8eb8f pclox Xorg.0.log http://pastebin.com/m68e2233 I have not tried using this xorg.conf in 10.3 and don't know if that would be advisable due to different kernel and different xorg version. Anyway I hope this is easier to follow. I'd certainly appreciate any help. I don't know if this is a bug or not, but I have to say that I'm surprised that 10.3 won't pick up my settings that 10.2 did. Many many thanks, Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jim Flanagan wrote:
Rajko M. wrote:
On Saturday 20 October 2007 11:38:16 pm Jim Flanagan wrote:
...
So, thinking that it must be a 10.3 issue, I installed 2 different distros (something I had never done before). Pclinuxos and zenwalk both run fine in gui, pclinuxos is running at 1280x1024 at 60hz. I don't recall what zenwalk ran at, but it was higher than that.
So, to me this must be a 10.3 issue. If I'm on the wrong track guys please let me know. I'm not at all sure what to do next as I've never seen a problem where nothing you try works.
<snip>
# sax2 and Xorg see different BusID's.
That can be xorg or sax2. You may try to change manually xorg.conf line: BusID "2:0:0" to BusID "2:0:1" and see if that helps.
If you have multiboot, it will be fine if you can supply head var/log/Xorg.0.log for all distros. You can snip output below 'Current Operating System:' line. That will tell what version of X Window System they use.
It will be interesting to see what nvidia Xorg.0.log tells. BTW, do you have any other Xorg logs in /var/log/
OK guys, sorry for the delay, its been a busy week. (I don't know if its best to keep posting here or start a new thread, but as this one is pretty mangled anyway, I'll post here, hope you see it). I had some grub problems to sort out as well.
As I said in my last post, I took the other cards back and am staying with my existing radeon 9000 for the moment. It worked acceptably in 10.2. My clean 10.3 install will not load X, nor will sax2 run. I pasted into 10.3 the xorg.conf from 10.2. This does get X up and I can log in, but not reliably, certainly not optimally. Sometimes the bottom 1/6th or so of the screen is black showing no kikker, but most times I get a full screen. Sometimes apps like Thunderbird freeze with warning to terminate it. So I still have some work to do here. I have not tried changing the PCI bus to "2.0.1". Also as I said before, sax will run in yast, but not in cli, runlevel 5 or 3.
Here are logs currently on the system:
xorg.conf from 10.2 but after running yast>sax in 10.3 that I'm running now http://pastebin.com/m24b230f
xorg.conf from the 10.3 install that did not work http://pastebin.com/m4a33cb60
sax.log after running yast>sax in 10.3 http://pastebin.com/m40037ff1
Xorg.0.log http://pastebin.com/m883c4cb
Xorg.99.log http://pastebin.com/m7325d2d0
I don't know if this is helpful or not, but the test install I did of pclinuxos loaded this card with no problems and runs glxgears at about 2200fps on this card (about 7 times faster than I'm getting in 10.3).
pclox xorg.conf http://pastebin.com/m7eb8eb8f
pclox Xorg.0.log http://pastebin.com/m68e2233
I have not tried using this xorg.conf in 10.3 and don't know if that would be advisable due to different kernel and different xorg version. Anyway I hope this is easier to follow. I'd certainly appreciate any help. I don't know if this is a bug or not, but I have to say that I'm surprised that 10.3 won't pick up my settings that 10.2 did.
Many many thanks,
Jim F
Section "Device" BoardName "RV250 If" ^^^^^^^^^^^^^^^^^^^^^^^^^^^ BusID "2:0:0" Driver "radeon" Identifier "Device[0]" Option "AGPMode" "4" Screen 0 VendorName "ATI" EndSection Now I'm not certain that this is your problem, but I have had fits with 10.3 and my ATI Mobility 9700 not being recognized properly. Have you looked at: http://en.opensuse.org/ATI_Driver_HOWTO -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin J.D. P.E. wrote:
Section "Device" BoardName "RV250 If" ^^^^^^^^^^^^^^^^^^^^^^^^^^^ BusID "2:0:0" Driver "radeon" Identifier "Device[0]" Option "AGPMode" "4" Screen 0 VendorName "ATI" EndSection
Now I'm not certain that this is your problem, but I have had fits with 10.3 and my ATI Mobility 9700 not being recognized properly. Have you looked at:
I have looked at the ati howto page, but that relates to getting the ATI fglrx driver working. I've had problems with that in the past with 10.2 and 10.3 and am still trying to get the default "radeon" driver working at this point. Someone posted earlier to try setting AGPMode to 4 using yast as that fixes his problem, but it has not helped me with mine. Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 27 October 2007 08:17:31 am Jim Flanagan wrote:
Rajko M. wrote: ...
It will be interesting to see what nvidia Xorg.0.log tells. BTW, do you have any other Xorg logs in /var/log/
OK guys, sorry for the delay, its been a busy week. (I don't know if its best to keep posting here or start a new thread, but as this one is pretty mangled anyway, I'll post here, hope you see it). I had some grub problems to sort out as well.
As I said in my last post, I took the other cards back and am staying with my existing radeon 9000 for the moment. It worked acceptably in 10.2. My clean 10.3 install will not load X, nor will sax2 run. I pasted into 10.3 the xorg.conf from 10.2. This does get X up and I can log in, but not reliably, certainly not optimally. Sometimes the bottom 1/6th or so of the screen is black showing no kikker, but most times I get a full screen. Sometimes apps like Thunderbird freeze with warning to terminate it. So I still have some work to do here. I have not tried changing the PCI bus to "2.0.1".
No need. I posted link to mail archive article that explains that PCI BusID is really 2:0:0 and 2:0:1 is used to satisfy some Win 2000 drivers. This is not a reason for problems.
Also as I said before, sax will run in yast, but not in cli, runlevel 5 or 3.
That was my problem with SaX2 and nvidia 6100 on board plus TwinView capable FX 5200. Using 10.2 xorg.conf made TwinView working. Otherwise it will have only one screen or Xorg server will hang after restart and lock computer.
Here are logs currently on the system:
xorg.conf from 10.2 but after running yast>sax in 10.3 that I'm running now http://pastebin.com/m24b230f
xorg.conf from the 10.3 install that did not work http://pastebin.com/m4a33cb60
sax.log after running yast>sax in 10.3 http://pastebin.com/m40037ff1
Xorg.0.log http://pastebin.com/m883c4cb
Xorg.99.log http://pastebin.com/m7325d2d0
I don't know if this is helpful or not, but the test install I did of pclinuxos loaded this card with no problems and runs glxgears at about 2200fps on this card (about 7 times faster than I'm getting in 10.3).
pclox xorg.conf http://pastebin.com/m7eb8eb8f
It also usefull as it tells that monitor and card are not configured to specific model, but few basic features. Which allows Xorg server to set graphic as it finds good.
pclox Xorg.0.log http://pastebin.com/m68e2233
It is usefull as it tells that Xorg is version 7.1 not 7.2 as openSUSE.
I have not tried using this xorg.conf in 10.3 and don't know if that would be advisable due to different kernel and different xorg version. Anyway I hope this is easier to follow. I'd certainly appreciate any help. I don't know if this is a bug or not, but I have to say that I'm surprised that 10.3 won't pick up my settings that 10.2 did.
You can try it. It seems pretty generic. The worst that can happen is that you have to find out hardware reset button on your computer (mostly keep pressed power longer than 4 seconds). I used as root in runlevel 3 command: X -configure which produced some generic xorg.conf.new saved in root home directory. After test with: X -config xorg.conf.new that gave X server generic screen without window manager (Ctrl-Alt-Backspace is the way to get out of that screen) I started GUI with: startx which gave me working GUI. In my case I had to add monitor sections, modes sections, and limit highest resolution in screen section, but that is due to exotic (read old) hardware I use, otherwise it will work with very simple xorg.conf right away. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rajko M. wrote:
On Saturday 27 October 2007 08:17:31 am Jim Flanagan wrote:
Rajko M. wrote:
...
It will be interesting to see what nvidia Xorg.0.log tells. BTW, do you have any other Xorg logs in /var/log/
I used as root in runlevel 3 command: X -configure which produced some generic xorg.conf.new saved in root home directory. After test with: X -config xorg.conf.new that gave X server generic screen without window manager (Ctrl-Alt-Backspace is the way to get out of that screen) I started GUI with: startx which gave me working GUI. In my case I had to add monitor sections, modes sections, and limit highest resolution in screen section, but that is due to exotic (read old) hardware I use, otherwise it will work with very simple xorg.conf right away.
Running X -configure did not run on my system, failed with errors, so I
filed a bug report. The fix that was posted by the moderator did resolve
my issue, and I can now run sax2 to configure my system. See quote from
bugzilla below:
----
https://bugzilla.novell.com/show_bug.cgi?id=338011#c12
--- Comment #12 from Stefan Dirsch
On Thursday 18 October 2007, Jim Flanagan wrote:
Have you guys tried the "ati" driver instead of the "radeon"? I know both seem to work for me, but the differences were usually the cards they worked with, which may be the case with you.
Either run sax2 with ati sax2 -m 0=ati or just change the driver in xorg.conf to test it.
Lee
Ok, I tried the ati driver with the radeon 9800 pro card. Makes no difference, does not work either. Then I tried setting agpmode to 4x, but that did not get me to a destop either, with 4 different drivers, vesa, radeon, ati, and flgrx. So I re-installed the 9200, and my monitor says "mode out of range", which happens with this card during default res installation, Don't even see the command line running by on boot. This with the vesa, radeon, and ati driver.
I can edit the 10.3 xrog.conf file from my 10.2 install, but I don't know what to change to make this card feed something my monitor can handle. So I'll do a re-install of 10.3 again. At this point the only thing I can think of that I haven't tried, is the ati fglrx driver with 10.3 on the 9200 card. I'll try that and report back. After that I'm out of ideas.
Any more thoughts would be most helpful. I was really hoping 10.3 would be "it" for me.
Jim F
========= Jim, I'm beginning to believe you have other problems at this point. Both of those cards should be solid performers and easily set up! I don't know if you have had the opportunity to try those cards in a different motherboard or even have access to another, but I would certainly try that. There's no reason those cards should not work without problems, unless of course there's another hardware problem. I've still got a 9200 in my test machine, but have not tried 10.3 on it yet. Thing is 10.1 worked without mishap, pretty much updated to 10.2 before I wiped it. The new Zenwalk Linux 4.8 I have installed on it now gives no problem either. You are having way too many problems for me to believe both those cards are defective or 10.2/3 is the culprit. I think you're going to have to do some more investigation, starting with your hardware. It doesn't happen to be an ASUS motherboard does it? Lee -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Aniruddha -
BandiPat -
David C. Rankin J.D. P.E. -
Felix Miata -
Jim Flanagan -
Joe Morris (NTM) -
Rajko M.