|
Bugzilla – Full Text Bug Listing |
| Summary: | check state of 3D configuration for intel 945gm | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Casual J. Programmer <casualprogrammer> |
| Component: | SaX2 | Assignee: | Marcus Schaefer <ms> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | sndirsch |
| Version: | Alpha 3plus | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
/var/log/SaX2.log
/var/log/Xorg.0.log |
||
|
Description
Casual J. Programmer
2007-05-04 09:53:32 UTC
Your turn. :-) After
init 3
sax2 -r
Sax states that is has arrived at a configuration based on assumptions it made, do I want to accept it ?
Pressing OK completely breaks the x-server, output after init 5 is:
(WW) intel: No matching Device section for instance (Bus ID PCI:0:2:1) found
...
(EE)intel(0):V_BIOS address 0x7d8c0 out of rangege
(EE)intel(0):Bad VBT signaturere
(EE)intel(0):No valid modules.s.
(EE)Screen(s) found, but none have a useable configuration.n.
Fatal server error: no screens found!
Note the repeating of the last two characters on the (EE)-lines.
copying a backup to /etc/X11/xorg.conf from run level 3 did only cure the situation after reboot.
Created attachment 137470 [details]
/var/log/SaX2.log
Created attachment 137471 [details]
/var/log/Xorg.0.log
Not sure what other information I could provide, please advise. in reply to comment #2 click on "change configuration" and tell me in the following dialog whether the 3D check box is grayed out or not Thanks > (EE)intel(0):V_BIOS address 0x7d8c0 out of rangege
> (EE)intel(0):Bad VBT signaturere
> (EE)intel(0):No valid modules.s.
> (EE)Screen(s) found, but none have a useable configuration.n.
I'm afraid it's time to reboot your machine (reset!) and try again :-(
starting with comment #7 CTL+ALT+F1 login as root sax2 -r this time press change, the setup menu comes on, 3D is NOT greyed out so, what next ? > CTL+ALT+F1
> login as root
> sax2 -r
Why do you make such things? Either run sax2 on top of a Xserver when you're logged in a regular session or switch to runlevel 3/terminate your displaymanager before starting sax2. Otherwise sax2 needs to start a second Xserver for itself and a third Xserver for testing. Which is always good for anny kind of problems.
I was under the impression, that Sax2 is run from YaST which is always asking for root privileges, so I assumed, that SaX2 itself needs to be run as root as well. SaX2 asks for the root password when running as regular user. There is no need to switch to a console before starting sax2. It's not a good idea at all, because one more Xserver needs to be started. So what happens after reboot, when you follow the advices of Marcus in comment #2? Remember ? "For this one I would suggest to start from scratch with a clean
configuration:
init 3
sax2 -r
---> check state of 3D check box"
Now, just for my understanding, how would I go to runlevel 3 without being logged in as root ?
Did you expext me to logoff in runlevel 3 and login again as cjp, the start sax2 -r as cjp and enter the root password to get it running ? Sounds a bit weird, doesn't it ?
Regarding comment #12, as I already mentioned in Comment #8 3D is not greyed out here. But setting it greys out dual head mode, so I can't set it with sax2 from control center.
Also the issues from Bug 237676 are back: There appears an xserver... and garbled display when logging out.
>Did you expext me to logoff in runlevel 3 and login again as cjp, the start
>sax2 -r as cjp and enter the root password to get it running ? Sounds a bit
>weird, doesn't it ?
Maybe, but it should work. If we need to discuss all the instructions we give to you we'll never get anywhere soon.:-(
Stefan, we don't need to discuss all the instructions, but this stuff should be understandable by an average user. Now if I am asked to issue init 3 sax2 -r how should I guess that I need to become a normal user before issuing the second command ? Come to think of it, runlevel 3 terminates all x-servers, so, no matter as who you start sax2, it will start an x-server for the menu and another one for the test. I can't possibly see a third instance being created. The information you requested is already there in Comment #13 as well as Comment #8: Regarding comment #12, as I already mentioned in Comment #8 3D is not greyed out here. But setting it greys out dual head mode, so I can't set it with sax2 from control center. Also the issues from Bug 237676 are back: There appears an xserver... and garbled display when logging out. Ok. So you're back to 3D support. |