New 12.2-64 install gets ACPI error messages in dmesg

English Install/Boot/Login
1

Hello list, moderators!

Is there a fix for the errors below? The computer seems to be working despite them. Could this be a BIOS setting conflict with the 12.2? The BIOS advanced settings are still at the Asus defaults.

My new barebones box (Asus P8Z77-V LK and i7-3770) installed the 12.2-64 OK, but I see several ACPI messages in dmesg.

“ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)” and

“ACPI Error: Method parse/execution failed _SB_.PCI0.SAT0.SPT3._GTF] (Node ffff88040bb9db00), AE_NOT_FOUND (20120320/psparse-536)”.

I just did an online update, but these errors persisted. Heboland.

2

Such messages usually indicate firmware defects and can only be fixed by BIOS update from vendor. Sometimes it is possible to override ACPI tables with “improved” versions, but it appears old repository is no more available. You can find details here: https://lesswatts.org/projects/acpi/overridingDSDT.php

Do you have any real problems besides these messages?

3

Thank you arvidjaar!

I checked the Asus bios for my mobo and it’s up to date. I’m hesitant to try to take the steps your link described, mostly because of the caveats and warnings that come with such action, but thanks for sending it.

Something that you can help me with if you’re willing is to guide/advise me is how to connect up this thread with another one I started in 64-bit a few weeks ago.

The subject there dealt with a mobo recommendation. Before that thread “closed” one of the moderators described a box of his similar to mine.

Now with your response in this thread, I know that my boot errors are related to my mobo bios.

I think if I post back to that 64-bit thread, no one will notice. Is there a way to “reactivate” that past thread?

I’ll wait to hear back on this thread before I go any farther. Heboland.

4

On 02/24/2013 03:46 AM, heboland wrote:
> I’ll wait to hear back on this thread before I go any farther.

you failed to answer arvidjaar’s question: “Do you have any real
problems besides these messages?”

meaning that if you have no problems (very short battery life, high
fan noise, or overly high CPU temperature) just ignore the messages

because reading some of the hits from
https://www.google.com/search?q=ACPI+Error%3A+[DSSP]+Namespace+lookup+failure%2C+AE_NOT_FOUND

it does not sound like a big problem…and i see in at least one
“ignore the messages if everything seems to be working.”

and the Red Hat folks found that a HP bios update ‘fixed’ the problem
[problem being error messages ONLY, no affect on system] on a Proliant…

personally i would not flash my bios just to remove an error message
when everything is working as expected…

you might [read the caveat in my sig] wanna try: at the first green
screen type into the Boot Options line the first of the following,
and then boot and see if the warnings are gone AND all acpi stuff is
still working:


acpi_osi=Linux
acpi=force

if after booting with the first line alone the errors still occur:
then boot again and try the second line alone…if no changes to the
system and the error messages remain, then boot one more time and
type in both lines with a space between, like


acpi_osi=Linux acpi=force

and, boot…depending on if the error messages stay or not and if
the acpi stuff works or not, then you can decide to:

  • use one boot option or the other (and make it happen on every boot)
  • use both boot options (automatically, every time)
  • use neither and just ignore the messages
  • use neither and take the chance of bricking your machine by
    flashing the BIOS when there are NO problems other than some boot
    messages you (and i) don’t understand

–
dd
http://tinyurl.com/DD-Caveat

5

Thank you DD for your very thorough response!

First let me answer arvidjaar’s question. I’m not having any problems I know about besides these messages. Of course I’ve had only a few hours of time to spend with this new hardware since it arrived last Thursday.

With this new install, I have one more hurdle to overcome before I can try your “suggestions” - I read your sig!

I’m embarrassed to say that the “first green screen” is not giving me a chance to add boot options. My only choices seem to be two 12.2 boot profiles, one of them failsafe. On my 12.1-32 there is a kernel parameter line I don’t have now.

Even worse, I can’t log in graphically as root! After I give the root password, a virtualbox blank.
,black screen appears. I intalled vbox for future experimentation. I’m totally unacquainted with virtualbox at this point!

I can edit the grub boot line with yast to add your suggestions, while leaving the failsafe boot line as is for a lifeline.

I’m sure this “first green screen” trouble makes me sound like a rank amateur! Oh yes, my hardware is a tower, not a laptop.

Most likely I’ll ignore these dmesg error messages, but I will try your suggestions today.

One other thing I want to do is post a reply to myself on my recent 64-bit section post. What I’m hoping for there is a reply from the moderator in that section that has personal hardware similar to mine. The concern I have, which I mentioned in my previous post here, is that my post to my now dormant thread will be ignored. Am I right about that? How would you handle such a post?

I think I answered all your questions. If you have a suggestion about my green screen trouble, I would like to get it! Otherwise, I think I can use yast to edit grub and try your suggestions. Whatever means I use to implement your suggestions, I’ll report back here with the results. Heboland.

6

Replying to myself,

DD, I tried your suggestions without changing the ACPI errors. Like I wrote above, I edited the grub “normal” profile, leaving the failsafe profile unchanged.

For the record these are the original normal and failsafe kernel parameter lines:

Orig boot line:
resume=/dev/disk/by-id/ata-TOSHIBA_DT01ACA100_139AVYSRS-part6 splash=off quiet showopts
Failsafe boot line:
showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe

Both of these profiles get the same ACPI errors. I added your suggestions to the right side of the Orig line.

Since the suggestions made no difference, I took them back out.

I did post some of this info to my dormant 64-bit section thread in the hope that JDMcdonald3 will discover it and reply.

DD, in the meantime, I’ll learn more about my new system, leaving the ACPI to resolve itself. My thanks to all the responders! Hope I didn’t violate any cross posting rules! Heboland.

7

On 02/24/2013 07:36 PM, heboland wrote:
> Even worse, I can’t log in graphically as root!

never do that ever.

you should never log into KDE/GNOME/LXDE/Xfce or any other *nix-like
system’s graphical user interface desktop environment as root…

doing so 1) opens you up to several different security problems if
you (for example) browse the net, 2) too many, far too easy ways to
damage your system no matter how careful your actions (for
example: cases of unintended change of ownership of some files from
user to root sometimes occurs which can preclude logging in as the
user), 3) anyway logging into KDE/etc as root is never
required to do any or all administrative duties, 4) and, not even
logging in as root just to see if it works as root is useful, because
the “yes” or “no” learned is almost always totally useless
in finding the problem giving the symptoms…while, logging into the
GUI as root to learn the yes/no could cause the next adverse
symptom encountered.

so, always log in as yourself, and “become root” by using a root
powered application (like YaST, File Manager Superuser Mode) or using
“su -”, sudo, kdesu, or gnomesu in a terminal to launch whatever tool
is needed (like KWrite or gedit to edit a config file)…read more on
all that here:

http://tinyurl.com/593e4c
http://tinyurl.com/ydbwssh
http://tinyurl.com/4nsaqst
http://tinyurl.com/665h5ek
http://www.linfo.org/root.html
http://tinyurl.com/6ry6yd

additionally: after logging into KDE/Gnome/etc as root, if you
experience problems (for example, with uncommanded file ownership and
permissions changes) and if you can provide us with details of what
you were doing while you were logged in as root, that would help us
identify if there’s a bug that needs to be fixed…thanks for your help…

–
dd
openSUSE®, the “German Engineered Automobile” of operating systems!

8

Thanks again for your input DD!

I agree with your warnings! With my slow HW before this new box, I became an lxde convert, and mostly over the display problem. Since Sax2 went away, I would have the cursor pointer covering my screen with kde! lxde always had a reasonable display to start with.

With an xorg.conf, I could get the resolution I wanted. If necessary I would install past versions of opensuse like 11.2 or similar just to run Sax2 for that file!

Now with my 64-bit toy, I don’t have any old OS-64 to generate an xorg.conf. I read about Xorg -configure, but it seems to expect to be invoked from level3. Since I don’t have a kernel option line available when the system boots, I don’t yet know how to get to level3

With earlier OS-32 versions, I did occasionally use the graphical root desktop for building things like modem drivers.

Eventually I’ll figure out how to get to level3 and see if I can create an xorg.conf file for this box. I did try editing the xorg.d/50.monitor.conf. Nothing changed, so I don’t think lxde uses that file.

lxde has a nice 1024x768 display, which is easy to work with (nothing off the screen). I only want to get to 1152x864, but it may take me a while to achieve that.

Since you didn’t jump on me for sharing information from this thread on the 64-bit thread, I’ll take that as acceptable under the circumstances.

My methods may seem primative, but the 64-bit leap has given me a steep learning curve to climb over.

Thanks again for your time on this matter! Heboland.

9

On 2013-02-25 03:16, heboland wrote:

> Now with my 64-bit toy, I don’t have any old OS-64 to generate an
> xorg.conf. I read about Xorg -configure, but it seems to expect to be
> invoked from level3. Since I don’t have a kernel option line available
> when the system boots, I don’t yet know how to get to level3

Yes, you have. There is a key in grub2 to reach an editor that allows
you to type “3”. I don’t use grub2, so I don’t remember the trick.

Or, you can edit the appropriate configuration file in grub - which I
don’t know which one it is in grub2 (again). The kernel line for a
verbose text boot is like this (two versions):


>     kernel /boot/vmlinuz root=...  resume=...  splash=verbose quiet showopts vga=0x317 systemd.log_level=debug systemd.log_target=kmsg

>     kernel /boot/vmlinuz root=...   resume=...  splash=verbose console=tty1 loglevel=3 showopts vga=0x317

The first one is used for debugging problems, so it might be more
appropriate for your case. Try.

Notice that the two lines above are from my grub 1 menu.lst file. I
don’t know what you have to change for grub2, sorry.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

10

Thanks for the suggestions, Robin!

You know, I was googling and found an article authored by the JDMcDaniel3 from the 64-bit section.

His magic and now mine, is to press a key to stop the first green screen. Next select one of the boot profiles and press the “e” key.

Arrow down the text edit display to the line that starts with linux. Press the keyboard “end” key to go to the end of the line. From that point type a space and a 3 for level three. Finally F10 continues the boot to level 3.

JD’s formula was the good news for me. The bad news is that Xorg -configure failed with the error message “too many screens”!

In the beginning, someone must have hacked an xorg.conf from scratch, so there’s still some hope! Heboland.

11

> Since you didn’t jump on me for . . .

it was not my intention to “jump on you” for anything…sorry if you
felt so…

> the 64-bit leap has given me a steep learning curve to climb over.

it may seem that way, but the step from 32 to 64 was almost a
non-event when i first did it with SuSE, moving from 9.1 32 to 9.2
64…then the only learning curve was figuring out which things had
to be fixed…when i left 9.2 i went back to 32 because there were
so many little things that just didn’t work without extra effort…

but, the largest majority of the 64 bit ‘little problems’ have been
ironed out and the default install is clean, smooth and good to go.

the learning curve you are now facing has nothing to do with 32 vs
64, but instead it is (for example) systemv vs systemd; and grub
legacy vs grub2; and missing SAX; and the add of all the little files
inside /etc/X11/xorg.conf.d and depreciation of /etc/X11/xorg.conf;
and the advent of hal; and the death and depreciation of hal; and and
and and . . .

it is a fast moving target (i know almost nothing about systemd,
grub2, how to make the little files in xorg.conf.d do ‘right’ etc etc
etc…today i am more a n00b than i was yesterday, and 12.3 is right
around the corner!!

–
dd
openSUSE®, the “German Engineered Automobile” of operating systems!

12

On 02/25/2013 07:16 AM, heboland wrote:
> In the beginning, someone must have hacked an xorg.conf from scratch,
> so there’s still some hope! Heboland.

if you happen to have an old archive of xorg.conf’s for the
machine, graphics card/chips and monitor then you can try to hack it…

the deal is: if during boot the system sees that xorg.conf it WILL
use it in preference to whatever is in /etc/X11/xorg.conf.d

so if you have a copy of the old working great xorg.conf from any
previous X on -THAT- hardware: remove the stuff from it that works,
and leave the stuff specific to what is not working…and then create
and put it in /etc/X11/xorg.conf

like, if all the mouse and wacom stuff in your new install is working
fine, then take it out of your old xorg.conf and let the system
generated 11-mouse.conf and 50-wacom.conf control the day! (because
the system is detecting it and using the hardware as it should–and,
since it is, if you later switch mice or tablets the system is likely
to see the new hardware and config it ok also)

note: make backups and be careful out there…

–
dd
http://tinyurl.com/DD-Caveat

13

I think your problem is quite common. Here’s a Lenovo B570e.

BIOS Information
        Vendor: LENOVO
        Version: 44CN43WW
        Release Date: 10/27/2011
        Address: 0xE0000
        Runtime Size: 128 kB
        ROM Size: 2560 kB
        Characteristics:
                PCI is supported
                BIOS is upgradeable
                BIOS shadowing is allowed
                Boot from CD is supported
                Selectable boot is supported
                EDD is supported
                Print screen service is supported (int 5h)
                8042 keyboard services are supported (int 9h)
                Serial services are supported (int 14h)
                Printer services are supported (int 17h)
                CGA/mono video services are supported (int 10h)
                NEC PC-98
                ACPI is supported
                USB legacy is supported
                BIOS boot specification is supported
                Function key-initiated network boot is supported
                Targeted content distribution is supported
        BIOS Revision: 1.67
        Firmware Revision: 1.41

Handle 0x0001, DMI type 1, 27 bytes
System Information
        Manufacturer: LENOVO
        Product Name: 52152EG
        Version: Lenovo B570e
        Serial Number: ... ... ...
        UUID: ... ... ...
        Wake-up Type: Power Switch
        SKU Number: System SKUNumber
        Family: HuronRiver System

**
dmesg | grep -i error**


    0.227603]  pci0000:00: ACPI _OSC request failed (AE_ERROR), returned control mask: 0x1d
    2.906749] ACPI Error: Current brightness invalid (20120320/video-376)
  360.655172] ACPI Error: [OPST] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
  360.655198] ACPI Error: Method parse/execution failed \_SB_.PCI0.LPCB.EC0_._Q14] (Node ffff880235091650), AE_NOT_FOUND (20120320/psparse-536)
  412.179792] ACPI Error: [OPST] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
  412.179812] ACPI Error: Method parse/execution failed \_SB_.PCI0.LPCB.EC0_._Q14] (Node ffff880235091650), AE_NOT_FOUND (20120320/psparse-536)
  439.964366] ACPI Error: [OPST] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
  439.964385] ACPI Error: Method parse/execution failed \_SB_.PCI0.LPCB.EC0_._Q14] (Node ffff880235091650), AE_NOT_FOUND (20120320/psparse-536)
  441.714757] ACPI Error: [OPST] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
  441.714776] ACPI Error: Method parse/execution failed \_SB_.PCI0.LPCB.EC0_._Q14] (Node ffff880235091650), AE_NOT_FOUND (20120320/psparse-536)
  442.217739] ACPI Error: [OPST] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
  442.217758] ACPI Error: Method parse/execution failed \_SB_.PCI0.LPCB.EC0_._Q14] (Node ffff880235091650), AE_NOT_FOUND (20120320/psparse-536)
  455.093977] ACPI Error: [OPST] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
  455.093996] ACPI Error: Method parse/execution failed \_SB_.PCI0.LPCB.EC0_._Q14] (Node ffff880235091650), AE_NOT_FOUND (20120320/psparse-536)
  459.117794] ACPI Error: [OPST] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
  459.117814] ACPI Error: Method parse/execution failed \_SB_.PCI0.LPCB.EC0_._Q14] (Node ffff880235091650), AE_NOT_FOUND (20120320/psparse-536)
  460.465699] ACPI Error: [OPST] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
  460.465707] ACPI Error: Method parse/execution failed \_SB_.PCI0.LPCB.EC0_._Q14] (Node ffff880235091650), AE_NOT_FOUND (20120320/psparse-536)
  462.055218] ACPI Error: [OPST] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
  462.055237] ACPI Error: Method parse/execution failed \_SB_.PCI0.LPCB.EC0_._Q14] (Node ffff880235091650), AE_NOT_FOUND (20120320/psparse-536)
  467.949954] ACPI Error: [OPST] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
  467.949961] ACPI Error: Method parse/execution failed \_SB_.PCI0.LPCB.EC0_._Q14] (Node ffff880235091650), AE_NOT_FOUND (20120320/psparse-536)
  470.907619] ACPI Error: [OPST] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
  470.907638] ACPI Error: Method parse/execution failed \_SB_.PCI0.LPCB.EC0_._Q14] (Node ffff880235091650), AE_NOT_FOUND (20120320/psparse-536)
 4932.937513] ACPI Error: [OPST] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)

Have a look here https://forums.opensuse.org/english/get-technical-help-here/how-faq-forums/unreviewed-how-faq/386054-how-fix-your-buggy-dsdt.html If you want to check for errors in your DSDT Table: “Section 1: Fixing the DSDT, ****Find your errors & warnings.”

14

On 2013-02-25 08:55, dd wrote:
> and missing SAX;

There is a project (one of those paid summer projects) to recreate sax.
I don’t remember at what state it is. It is called sax3, and it should
be on the oss repos of 12.1 and 12.2, the search box says.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

15

On 2013-02-25 07:16, heboland wrote:
>
> Thanks for the suggestions, Robin!
>
> You know, I was googling and found an article authored by the
> JDMcDaniel3 from the 64-bit section.
>
> His magic and now mine, is to press a key to stop the first green
> screen. Next select one of the boot profiles and press the “e” key.
>
> Arrow down the text edit display to the line that starts with linux.
> Press the keyboard “end” key to go to the end of the line. From that
> point type a space and a 3 for level three. Finally F10 continues the
> boot to level 3.

Ah, that’s the trick.

However, the lines I posted give a very verbose text screen, much more
than the simple “3”.

> In the beginning, someone must have hacked an xorg.conf from scratch,
> so there’s still some hope! Heboland.

Oh, yes, we did. Long time ago. It took me weeks to get a workable
graphics mode on my first system. Don’t ask me how - because the method
is invalid now, not only because I don’t remember.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

16

Thank you all for the overwhelming responses!

This thread is drifting off topic now, but I would like to respond to some of the input.

DD, I didn’t think you “jumped on” me! At least once in the past I mentioned a previous post in a current post and the current post disappeared. A moderator joined the two threads together. That’s what I meant by being jumped on. I don’t really know why it happened.

I’m including the ACPI errors as part of the 64-bit learning curve. The failure of Xorg -configure may be related to a 64-bit OS.

Sadly I don’t have an xorg.conf from this HW! this 12.2 is the only 64 bit OS I have. I doubt an 11.2-32 would install on it. My cursory expectation is that virtual box is only intended for windows OSs.

susebh, I will look into the DSDT table after a bit. I would like to understand more about the errors. In another lifetime error messages about namespace were not to be ignored. For now several responders recommended ignoring the ACPI errors.

Robin, a special thanks for sax3! I installed it but it segfaults. Maybe the summer was too short to finish it. The buglist shows this:
"
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut for YPushButton “Ok” at 0x1c125c8
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut for YPushButton “Cancel” at 0x1c5c318

This is probably another issue:
<M> [ui] YUI.cc:529 ~YUITerminator(): Shutting down UI Segmentation fault [RIGHT] Aug 28, 2011 [/RIGHT]
If there are no shortcuts, Then new shortcuts must be automatically created. If it does not let me know "

Nothing I can find is left after the crash, but there should be at least a core file somewhere!

With the Xorg - configure, it errors out complaining about “too many screens”! I think it’s the xorg.conf.install in X11 that makes it mad. It does leave a partial config file behind when it bails out.
This is the server layout from xorg.conf.install:
Section “ServerLayout”
Identifier “Layout”
Screen “vboxvideo”
Screen “vmware”
Screen “cirrus”
Screen “fbdev”
Screen “vesa”
EndSection

I may be able to pare this list down or add to it to appease Xorg.

Like I wrote before, my 1024x768 display is adequate, so it’s not critical to change it. Heboland.

17

xorg.conf is deprecated, xorg.conf.d/* is used instead. But better leave the system to it, i.e. initially do not change values in there.

18

On 2013-02-25 21:26, heboland wrote:

> susebh, I will look into the DSDT table after a bit. I would like to
> understand more about the errors. In another lifetime error messages
> about namespace were not to be ignored. For now several responders
> recommended ignoring the ACPI errors.

I don’t know. It is the type of thing that few people know if it they
are really important or not :slight_smile:

So most of us ignore such messages if we can’t do any thing about them
and do not appear to do harm.

> Robin, a special thanks for sax3! I installed it but it segfaults.
> Maybe the summer was too short to finish it. The buglist shows this:

What a shame. Yes, I believe sax3 is not finished, but it should work,
more or less. If I recall correctly it is intended to be started in text
mode, not inside graphical mode.

> Nothing I can find is left after the crash, but there should be at
> least a core file somewhere!

No, they are usually disabled. It is a chain of programs starting other
programs. If one disables core dumps, the child have it disabled as
well. I have the idea that X disables them.

> With the Xorg - configure, it errors out complaining about “too many
> screens”! I think it’s the xorg.conf.install in X11 that makes it mad.

That file is normally ignored. If you use the boot option “x11failsafe”
in the kernel line makes xorg load that file instead of the normal one.

It is actually the same configuration that was used during the
installation of the system, so it should work always, but with lower
performance.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

19

Knurpht, Robin, thanks for your responses!

Knurpht, I did add something to the /etc/Xll/xorg.d/50-monitor.conf. In my file, everything was commented out, so I tried entering a section that worked for someone on google. It made no difference, it didn’t get overwritten and I commented that section out after my experiment. Yes it could have caused a display problem.

Robin, thanks so much for sharing you insight into the workings of the display SW! From my kde display problem days, I remember that the “nomodeset” parameter results in a default display.

I did run sax3 from a root console. It installs into sbin. If there were some chance to tweak it along, it would be worth the effort. Maybe someone has picked it lock!

When run from a root console, sax3 pops up a graphical menu asking first for mouse, kb, monitor, etc. Selecting monitor brings up a second screen with a resolution textbox defaulted to (1024x768x60) and an advanced section. The advanced section is optional and wants the monitor specs - Horz and Vert Sweep ranges.

Within the advanced section is another optional choice of CVT expecting display x and y pixels and refresh. When I filled in the CTV with the 1152x864x60, sax3 remembered that setting after the segfault. Now when it fires up again, the monitor screen shows the non-advanced resolution to be 1152x864x60.

When I run sax3 I get this:

…
/files/etc/X11/xorg.conf.d/99-saxscreen.conf/Screen[last()]/Display[last()+1]/Depth
no error
/files/etc/X11/xorg.conf.d/99-saxscreen.conf/Screen[last()]/Display[last()]/Modes
no error
<M> [ui] YUI.cc:529 ~YUITerminator(): Shutting down UI
<ERR> [ui] YUI.cc:100 ~YUI(): 1 open dialogs left over
[1] 4444 segmentation fault sax3
root[503]

At first blush, this looks like I missed a dialog box that the contents of aren’t checked, but maybe it’s a stack error. If the problem is mine, I’ve missed it.

Just out of curiosity, with the “muscle box” that I have, how hard would it be to get the pieces of this development that I could build and step thru with a debugger? I have a very slow internet connection (784 KB/sec)!

I have a feeling that with a working system like I have it would be pretty easy to parse out the equivalent xorg.conf that I’m using. But what do I know? That seems a good line to leave on! Heboland.

20

Replying to myself and to the list, I have the monitor resolution now I was after!

It had to be sax3 that made it happen, but in the end an xorg.conf was never generated. Instead three files were created today in /etc/X11/xorg.d/. They are: 99-saxdevice.conf 99-saxmonitors.conf 99-saxscreen.conf.

From the root console, execution would cause the monitor to go black like sax2 used to, but then sax3 errored out and segfaulted. I ran it several times with the last invocation pasted into my reply just previous to this post.

The time stamps on the sax generated files seem to match that last console invocation I posted. It could be that all the sax3 console invocations generated those sax files before crashing. I may not have noticed a change in monitor resolution occurring.

Just recently I ran sax3 graphically. it requests root permission, then pops up the device menu (mouse, kb, monitor, etc). When I selected monitor the device menu disappeared silently. There was no display flickering. I found the sax files looking for the output from the graphical invocation, but the sax file time stamps don’t agree.

So one more thing here! What are the chances I should save copies of those three sax files for transplantation into a fresh install? Will they be as portable as the xorg.conf used to be?

Again, thanks for all the time spent on my behalf! Heboland.