When I went to use an app last night, I received a message stating that I did not have 3D enabled. When I went into Yast to change the setting, I was given a message stating that I needed to setup the monitor; it was set to Vesa, and should have been set to my monitor via the manufacturers disk. When I setup my monitor I received a parse error for the config file.
I wasn't able to set up the monitor, not even with generic Vesa settings, and upon restarting X I was bumped to command line. I tried to set things up via sax but had same results, unless I took sax recommendation only. Now not only is the monitor with generic settings, but also mouse and keyboard. If I try to make any adjustments in Yast or directly in sax I'm back on the same merry-go-round.
Thoughts???
By sax you mean sax2, right? I'm only wondering if you've dropped into runlevel 3. That's the typical level you want to be in for running sax2. HTH...? -- kai ponte www.perfectreign.com linux - genuine windows replacement part
On Wednesday 25 January 2006 13:09, Kai Ponte wrote: <snip>
By sax you mean sax2, right?
I'm only wondering if you've dropped into runlevel 3. That's the typical level you want to be in for running sax2.
HTH...?
HTH? Sorry, yes sax2. From command line the only way to access sax 2 is in runlevel 3. Bernd
On Wednesday 25 January 2006 16:40, bernd wrote:
Sorry, yes sax2. From command line the only way to access sax 2 is in runlevel 3.
Hi Bernd, From "man SaX2": "-r Remove detection database and re-init the hardware database" So, as root from the command line (you're in run level 3, anyway...): "SaX2 -r" might get you back to a point where you can set your monitor, keyboard and mouse up again. regards, - Carl PS: I'm not running 3D graphics here (yet) but I seem to recall reading that nVidia's driver will enable 3D *but* that fact will /not/ be reflected in YaST2. Search the SLE archives for "nVidia" or check the instructions at nVidia's website or possibly someone will clear this detail up with a short post?
On Wednesday 25 January 2006 17:32, Carl Hartung wrote:
On Wednesday 25 January 2006 16:40, bernd wrote:
Sorry, yes sax2. From command line the only way to access sax 2 is in runlevel 3.
Hi Bernd,
From "man SaX2": "-r Remove detection database and re-init the hardware database"
So, as root from the command line (you're in run level 3, anyway...):
"SaX2 -r" might get you back to a point where you can set your monitor, keyboard and mouse up again.
Carl, That "almost" did the trick! I was able to setup my mouse and keyboard (although I am not able to get lineak to work right again. I'll deal with that later.), but I cannot setup my monitor right, and it keeps getting worse. I am not able to use the manufacturers driver for my monitor (Dell E193FP 19" LCD). The monitor (not linux) keeps spitting out the message that it cannot display the resolution that I am setting (1280x1024) and I'm left with 1024x768. When I go back in to sax2, I get the message "Unknown Monitor - monitor (0) with ID: undefined option "NoDDC" not found - please set up your monitor manually". The monitor settings are blanked, and I need to fill them in from scratch. NoDDC is an option for the card (Intel 915 G). I'm not touching it, and it's not set, so why am I getting the message? I get no success with VESA or LCD settings either. Further thoughts? Bernd
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2006-01-28 at 23:50 -0800, bernd wrote:
I am not able to use the manufacturers driver for my monitor (Dell E193FP 19" LCD). The monitor (not linux) keeps spitting out the message that it cannot display the resolution that I am setting (1280x1024) and I'm left with 1024x768.
Are you sure it supports 1280x1024? If it does, it will probably be at a lower frequency. If it doesn't, remove the entries for it in xorg.conf. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD3K4GtTMYHG2NR9URAntxAKCPMdWWvAibAhurdNdDhgO48JuuewCglygD HWZLhr6WoKZVNRe6WkMl2Jw= =iteb -----END PGP SIGNATURE-----
On Sunday 29 January 2006 02:50, bernd wrote: <snip>
NoDDC is an option for the card (Intel 915 G). I'm not touching it, and it's not set, so why am I getting the message?
I get no success with VESA or LCD settings either.
Further thoughts?
Hi Bernd, I think the only problem is the hardware detection not working well with this combination. I assume you've already run the built-in self-test? Shut down the whole system, disconnect the display from the computer and power up the display. An OSD self-test will run and the results displayed. If it's OK, turn it off, reattach it to the computer, boot to run level 3 and configure it with SaX2 as tried previously, but enter the settings manually. The relevant specs are: Screen dimensions Diagonal 19 inches (480.0 mm) Horizontal 14.8 inches (376.32 mm) Vertical 11.8 inches (301.05 mm) Horizontal scan range 30 kHz to 82 kHz (automatic) Vertical scan range 56 Hz to 76 Hz (automatic) Optimal [best looking] preset resolution 1280 x 1024 at 60 Hz Highest [fastest supported] preset resolution 1280 x 1024 at 75 Hz Mode, H(kHz), V(Hz), Pixel Clock(MHz), Sync Polarity(H/V) VESA 1280 x 1024, 80.0 , 75.0 , 135.0, +/+ VESA 1280 x 1024, 64.0 , 60.0 , 108.0, +/+ I'd experiment with both of these, since "optimal" can really mean "acceptable" vis a vis text clarity, "ghosting" and color quality. Finally, in case you don't have it, the User's Guide is available online at: http://support.dell.com/support/edocs/monitors/E193FP/English/index.htm Good luck & regards, - Carl
On Sunday 29 January 2006 08:43, Carl Hartung wrote:
On Sunday 29 January 2006 02:50, bernd wrote: <snip>
NoDDC is an option for the card (Intel 915 G). I'm not touching it, and it's not set, so why am I getting the message?
I get no success with VESA or LCD settings either.
Further thoughts?
Hi Bernd,
I think the only problem is the hardware detection not working well with this combination.
I assume you've already run the built-in self-test? Shut down the whole system, disconnect the display from the computer and power up the display. An OSD self-test will run and the results displayed. If it's OK, turn it off, reattach it to the computer, boot to run level 3 and configure it with SaX2 as tried previously, but enter the settings manually. The relevant specs are:
Screen dimensions Diagonal 19 inches (480.0 mm) Horizontal 14.8 inches (376.32 mm) Vertical 11.8 inches (301.05 mm)
Horizontal scan range 30 kHz to 82 kHz (automatic) Vertical scan range 56 Hz to 76 Hz (automatic) Optimal [best looking] preset resolution 1280 x 1024 at 60 Hz Highest [fastest supported] preset resolution 1280 x 1024 at 75 Hz
Mode, H(kHz), V(Hz), Pixel Clock(MHz), Sync Polarity(H/V) VESA 1280 x 1024, 80.0 , 75.0 , 135.0, +/+ VESA 1280 x 1024, 64.0 , 60.0 , 108.0, +/+
I'd experiment with both of these, since "optimal" can really mean "acceptable" vis a vis text clarity, "ghosting" and color quality.
Thanks for the tips! There is only one way that I am able to get 1280x1024, and that is by accepting the suggested settings from sax2 after using the -r option! The monitor self-tests just fine. Yet no go with the manual settings or any presets. During boot, the display shows fine all the way through the splash. Once KDM (or xdm) starts, the monitor either shows an error message that it is unable to display the video mode, or I am left with what I am able to manually set up, 1024x768. I have started sax 2 with -r, and that is the *only* time I do not get the message "Unknown Monitor - monitor (0) with ID: undefined option "NoDDC" not found - please set up your monitor manually". As I said sax2 suggested settings are the only way I have found to get 1280x1024 back, yet without 3d enabled, or correct settings for my mouse, keyboard, or VNC. Further Thoughts??? Bernd
On Tuesday 31 January 2006 16:49, bernd wrote:
As I said sax2 suggested settings are the only way I have found to get 1280x1024 back, yet without 3d enabled, or correct settings for my mouse, keyboard, or VNC.
Further Thoughts???
Hi Bernd, How does 3D fit into this effort? I thought the problem we were working on was getting the on-board Intel graphics working with the display without killing your keyboard and mouse? Have you tried 'tweaking' settings in the BIOS related to the graphics subsystem? (Like possibly bumping up the shared video memory?) Can you manually toggle and test between AGP and PCI graphics in the BIOS? And/or turn one of them off? Have you done any research to see if that mainboard and/or chipset is even supported? I'll keep my thinking cap on, but that's probably all I can suggest for now. regards, - Carl
On Tuesday 31 January 2006 15:26, Carl Hartung wrote:
On Tuesday 31 January 2006 16:49, bernd wrote:
As I said sax2 suggested settings are the only way I have found to get 1280x1024 back, yet without 3d enabled, or correct settings for my mouse, keyboard, or VNC.
Further Thoughts???
Hi Bernd,
How does 3D fit into this effort? I thought the problem we were working on was getting the on-board Intel graphics working with the display without killing your keyboard and mouse?
Have you tried 'tweaking' settings in the BIOS related to the graphics subsystem? (Like possibly bumping up the shared video memory?) Can you manually toggle and test between AGP and PCI graphics in the BIOS? And/or turn one of them off?
Have you done any research to see if that mainboard and/or chipset is even supported?
Wanting to enable 3D was where it all began. As soon as I opened up sax2, and before I touched anything (really!), I got the error message about "...NoDDC..." The only thing I can do in BIOS is to tweak the vid memory. The BIOS default is maxed at 8MB. SuSE hardware database shows the Intel I915G fully supported for 9.3; Xorg with 3D using the i810 driver. I'm posting on the boards at Dell to find out if there are any other linux users that found the same problem. It's my understanding that their business support people are familiar with Redhat, and so I may find common ground. I'll be calling tomorrow. Thanks! I'll keep you posted, and if you can think of anything else to try, please let me know. Can I directly edit Xorg or XF86Conf without pain? It says in the comments at the beginning of the files not to, because they are Sax2 generated files. Bernd
bernd wrote:
On Tuesday 31 January 2006 15:26, Carl Hartung wrote:
On Tuesday 31 January 2006 16:49, bernd wrote:
As I said sax2 suggested settings are the only way I have found to get 1280x1024 back, yet without 3d enabled, or correct settings for my mouse, keyboard, or VNC.
Further Thoughts??? Hi Bernd,
How does 3D fit into this effort? I thought the problem we were working on was getting the on-board Intel graphics working with the display without killing your keyboard and mouse?
Have you tried 'tweaking' settings in the BIOS related to the graphics subsystem? (Like possibly bumping up the shared video memory?) Can you manually toggle and test between AGP and PCI graphics in the BIOS? And/or turn one of them off?
Have you done any research to see if that mainboard and/or chipset is even supported?
Wanting to enable 3D was where it all began. As soon as I opened up sax2, and before I touched anything (really!), I got the error message about "...NoDDC..."
The only thing I can do in BIOS is to tweak the vid memory. The BIOS default is maxed at 8MB.
SuSE hardware database shows the Intel I915G fully supported for 9.3; Xorg with 3D using the i810 driver.
I'm posting on the boards at Dell to find out if there are any other linux users that found the same problem. It's my understanding that their business support people are familiar with Redhat, and so I may find common ground. I'll be calling tomorrow.
Thanks! I'll keep you posted, and if you can think of anything else to try, please let me know.
Can I directly edit Xorg or XF86Conf without pain? It says in the comments at the beginning of the files not to, because they are Sax2 generated files.
Bernd
Sorry, came in in the middle of this thread, so I may be off the mark here... Intel 915 Chipset? The problem may be the on-chip 915 BIOS settings (not your PC BIOS). Intel 915 chipset BIOS do not list all of the resolutions that the chipset can support. This can confuse sax2. So, you need to reprogram the 915 BIOS by deleting one of the pre-programmed video settings you will never use and replacing it with the settings you want. I had to do this to get 1400x1050 resolution on my IBM R52 laptop under SuSE 10. Fortunately, their is a utility called "855resolution" bundled with SuSE 10 (not sure about 9.3) that does the job. If you Google for this utility and Intel 915 you will get a lot of hits. It is also possible to automate this configuration by editing the boot.local file (I believe; I'm at a Windows workstation at the moment). The whole thing works because you are not really patching the on-chip BIOS; only the copy shadowed in RAM during the boot process, before X loads. Once you set it up, you should be able to run sax2 normally and it should find everything re your chipset OK. Whether your monitor's settings are in the sax database is another story. All I can tell you is that I get 1400x1050 resolution with 3D on my IBM R52 laptop under SuSE 10 just fine. YMMV! Hope that helps, Mark -- _______________________________________________________________ A Message From... L. Mark Stone Reliable Networks of Maine, LLC "We manage your network so you can manage your business" 477 Congress Street Portland, ME 04101 Tel: (207) 772-5678 Web: http://www.rnome.com This email was sent from Reliable Networks of Maine LLC. It may contain information that is privileged and confidential. If you suspect that you were not intended to receive it, please delete it and notify us as soon as possible. Thank you.
On Wednesday 01 February 2006 09:47, L. Mark Stone wrote:
Sorry, came in in the middle of this thread, so I may be off the mark here...
What's up with that, Mark? You been *working* or something? ;-) I think poor Bernd is going to be thrilled... and I'm copying your post into my 'special hardware' archive folder. Thanks for sharing! - Carl
On Wednesday 01 February 2006 06:47, L. Mark Stone wrote: <snip>
Intel 915 Chipset?
<snip> Here's the output from 855 resolution, yet the question is - Which mode do I change? I want 1280x1024, and it is already a listed mode with 8, 16, & 32 bits/pixel! Bernd suse:/home/bernd # 855resolution -l 855resolution version 0.4, by Alain Poirier Chipset: 915G (id=0x25808086) VBIOS type: 2 VBIOS Version: 3414 Mode 30 : 640x480, 8 bits/pixel Mode 32 : 800x600, 8 bits/pixel Mode 34 : 1024x768, 8 bits/pixel Mode 38 : 1280x1024, 8 bits/pixel Mode 3a : 1600x1200, 8 bits/pixel Mode 3c : 1920x1440, 8 bits/pixel Mode 41 : 640x480, 16 bits/pixel Mode 43 : 800x600, 16 bits/pixel Mode 45 : 1024x768, 16 bits/pixel Mode 49 : 1280x1024, 16 bits/pixel Mode 4b : 1600x1200, 16 bits/pixel Mode 4d : 1920x1440, 16 bits/pixel Mode 50 : 640x480, 32 bits/pixel Mode 52 : 800x600, 32 bits/pixel Mode 54 : 1024x768, 32 bits/pixel Mode 58 : 1280x1024, 32 bits/pixel Mode 5a : 1600x1200, 32 bits/pixel Mode 5c : 1920x1440, 32 bits/pixel
participants (5)
-
bernd -
Carl Hartung -
Carlos E. R. -
Kai Ponte -
L. Mark Stone