Re: X won't start with latest snapshot as user (Solution provided)

[butresin]

On  0926, Edgar Pettijohn III wrote:
> 
> On 11/11/18 12:59 AM, Marc Espie wrote:
> > On Sat, Nov 10, 2018 at 10:42:57PM -0600, Andrew wrote:
> > > Personally I use spectrwm, so I can't speak for other the wm's. In my
> > > case, all I had to do was:
> > > 
> > > $> cp .xinitrc .xsession
> > > $> chmod +x .xsession
> > > 
> > > ... and it "just worked" as expected :-)
> > You were lucky to not have something interesting in your .profile
> > That one got me.
> > 
> you weren't alone. took me a while to figure out why stuff didn't work how
> it did before. :)
> 

+1
. ~/.profile helped me in ~/.xsession.

Re: X won't start with latest snapshot as user (Solution provided)

[Marc Espie]

On Sun, Nov 11, 2018 at 09:26:32AM -0600, Edgar Pettijohn III wrote:
> 
> On 11/11/18 12:59 AM, Marc Espie wrote:
> >On Sat, Nov 10, 2018 at 10:42:57PM -0600, Andrew wrote:
> >>Personally I use spectrwm, so I can't speak for other the wm's. In my
> >>case, all I had to do was:
> >>
> >>$> cp .xinitrc .xsession
> >>$> chmod +x .xsession
> >>
> >>... and it "just worked" as expected :-)
> >You were lucky to not have something interesting in your .profile
> >That one got me.
> >
> you weren't alone. took me a while to figure out why stuff didn't work how
> it did before. :)

Well, it was mostly that it happened at the exact same time the unveil bug
broke doas, so for a moment I thought more shell scripts got broken. Turns
out I just lost $HOME/bin from my PATH.

Re: X won't start with latest snapshot as user (Solution provided)

[Edgar Pettijohn III]

On 11/11/18 12:59 AM, Marc Espie wrote:

On Sat, Nov 10, 2018 at 10:42:57PM -0600, Andrew wrote:

Personally I use spectrwm, so I can't speak for other the wm's. In my
case, all I had to do was:

$> cp .xinitrc .xsession
$> chmod +x .xsession

... and it "just worked" as expected :-)

You were lucky to not have something interesting in your .profile
That one got me.

you weren't alone. took me a while to figure out why stuff didn't work 
how it did before. :)

Re: X won't start with latest snapshot as user (Solution provided)

[Chris Bennett]

Thanks!
I use spectrwm too.
Now I know exactly what man pages to read, which I will do first, before
any copy/paste crap.
I have found the sheer size of X everything to be a bit intimidating. I
think this whole xenodm thing will fill in crucial gaps for me.

Happier,
Chris Bennett

Re: X won't start with latest snapshot as user (Solution provided)

[Arnoud Otten]

Thanks  all for your answers.

I did think that i had checked everything before posting something on the
mailing list, but missed the current faq.

Arnoud




On Saturday, November 10, 2018 23:32 CET, Zé Loff  wrote:

>
> On Sat, Nov 10, 2018 at 04:00:53PM -0500, Arnoud Otten wrote:
> > Startx doesn`t work anymore on my Lenovo W520.
> > I had a working X setup with Mate on 6.4 stable. Then i did an upgrade to 
> > 6.4 current, snapshot from 5 Nov, and couldn`t start X anymore.
> >
> > Did a fresh install with that snapshot, and found out, root could start X. 
> > Upgrade to snapshot from 9 Nov did not resolve the problem for the user
> > also a clean install did not.
> >
> > I found this thread about SUID on Xorg, and this fixed the problem for my 
> > situation:
> >
> > chmod 4755 Xorg
> >
> > https://groups.google.com/forum/#!topic/mailing.openbsd.bugs/VKf8XZAco08
>
> You really should read www.openbsd.org/faq/current.html before
> upgrading.  As of Oct-26 the Xorg binary is deliberately *not* installed
> setuid, which I suppose has something to do with the recently detected
> security hole:
>
> https://www.securityweek.com/xorg-flaw-exposes-unix-oses-attacks
>
> I guess removing setuid is a quick workaround which was necessary given
> that OpenBSD developers were kept in the dark about it for much longer
> than necessary:
>
> https://marc.info/?l=openbsd-tech=154050351216908=2
>
> So, the solution you provide is, basically, to revert the safeguard that
> was put it place to obviate the security hole.  And since you apparently
> didn't read the FAQ page on upgrading, you are more than likely to get
> scolded on misc@...
>
> Just use xenodm for the time being (that's what I did too).  Probably
> permanently too:
>
> https://marc.info/?l=openbsd-cvs=154050453117246=2
>
> Good luck
> Zé
>
> > [   198.792]
> > X.Org X Server 1.19.6
> > Release Date: 2017-12-20
> > [   198.819] X Protocol Version 11, Revision 0
> > [   198.833] Build Operating System: OpenBSD 6.4 amd64
> > [   198.846] Current Operating System: OpenBSD bsd520.my.domain 6.4 
> > GENERIC.MP#429 amd64
> > [   198.860] Build Date: 09 November 2018  11:59:57AM
> > [   198.874]
> > [   198.888] Current version of pixman: 0.34.0
> > [   198.901]Before reporting problems, check http://wiki.x.org
> > to make sure that you have the latest version.
> > [   198.901] Markers: (--) probed, (**) from config file, (==) default 
> > setting,
> > (++) from command line, (!!) notice, (II) informational,
> > (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> > [   198.957] (==) Log file: "/home/arnoud/.local/share/xorg/Xorg.0.log", 
> > Time: Sat Nov 10 21:24:06 2018
> > [   198.972] (==) Using system config directory 
> > "/usr/X11R6/share/X11/xorg.conf.d"
> > [   198.972] (==) No Layout section.  Using the first Screen section.
> > [   198.972] (==) No screen section available. Using defaults.
> > [   198.972] (**) |-->Screen "Default Screen Section" (0)
> > [   198.972] (**) |   |-->Monitor ""
> > [   198.972] (==) No monitor specified for screen "Default Screen Section".
> > Using a default monitor configuration.
> > [   198.972] (==) Automatically adding devices
> > [   198.972] (==) Automatically enabling devices
> > [   198.972] (==) Not automatically adding GPU devices
> > [   198.972] (==) Max clients allowed: 256, resource mask: 0x1f
> > [   198.973] (==) FontPath set to:
> > /usr/X11R6/lib/X11/fonts/misc/,
> > /usr/X11R6/lib/X11/fonts/TTF/,
> > /usr/X11R6/lib/X11/fonts/OTF/,
> > /usr/X11R6/lib/X11/fonts/Type1/,
> > /usr/X11R6/lib/X11/fonts/100dpi/,
> > /usr/X11R6/lib/X11/fonts/75dpi/
> > [   198.973] (==) ModulePath set to "/usr/X11R6/lib/modules"
> > [   198.973] (II) The server relies on wscons to provide the list of input 
> > devices.
> > If no devices become available, reconfigure wscons or disable 
> > AutoAddDevices.
> > [   198.973] (II) Loader magic: 0x9d2ea27c000
> > [   198.973] (II) Module ABI versions:
> > [   198.973]X.Org ANSI C Emulation: 0.4
> > [   198.973]X.Org Video Driver: 23.0
> > [   198.973]X.Org XInput driver : 24.1
> > [   198.973]X.Org Server Extension : 10.0
> > [   198.973] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
> > (Permission denied)
> > Check that you have set 'machdep.allowaperture=1'
> > in /etc/sysctl.conf and r

Re: X won't start with latest snapshot as user (Solution provided)

[Marc Espie]

On Sat, Nov 10, 2018 at 10:42:57PM -0600, Andrew wrote:
> Personally I use spectrwm, so I can't speak for other the wm's. In my
> case, all I had to do was:
> 
> $> cp .xinitrc .xsession
> $> chmod +x .xsession
> 
> ... and it "just worked" as expected :-)

You were lucky to not have something interesting in your .profile
That one got me.

Re: X won't start with latest snapshot as user (Solution provided)

[Andrew]

On 11/10/18 19:29, Chris Bennett wrote:

On Sat, Nov 10, 2018 at 11:36:17PM +0100, Solene wrote:

This is normal. Look at 26th October https://www.openbsd.org/faq/current.html

The suid was removed to prevent bad things to happen. Use xenodm instead of 
startx.



I have switched to using xenodm. I am also think I screwed up something
during installation. It happens. Shrug.
I have found that I am stuck using fvwm, but I would like to use another
wm. Not very important which one. But I really have no idea how to
accomplish that.
The reason I think I screwed up something else is that the performance
across the board is terribly slow. Happy to reinstall from scratch.

I'm happy to find the  answers reading man pages, but man fvwm wasn't
helpful for me. Which ones should I read?

Running 6.4 stable amd64

Thank you,
Chris Bennett


Chris, 


After 20+ years of typing startx, I switched to xenodm about three days
ago. The FAQ, "Following -current" and the xenodm manpage are very
helpful. Thanks to all the authors !!!

Personally I use spectrwm, so I can't speak for other the wm's. In my
case, all I had to do was:

$> cp .xinitrc .xsession
$> chmod +x .xsession

... and it "just worked" as expected :-)

N.B. If you have a custom .Xresources file, like I do for xterm, then
make sure a line like the following is in your ~/.xsession.

[[ -f ~/.Xresources ]] && xrdb -load ~/.Xresources

or simply

xrdb -load ~/.Xresources

Regarding fvwm ...

Read the last 20 lines or so of /etc/X11/xenodm/Xsession and you will
understand why you are "stuck using fvwm." It helped me a lot. The
xenodm manpage is solid gold. It's very well written.

You should be able to configure your X deskop the way you want it
between those docs.

Re: X won't start with latest snapshot as user (Solution provided)

[Chris Bennett]

On Sat, Nov 10, 2018 at 11:36:17PM +0100, Solene wrote:
> This is normal. Look at 26th October https://www.openbsd.org/faq/current.html
> 
> The suid was removed to prevent bad things to happen. Use xenodm instead of 
> startx.
> 

I have switched to using xenodm. I am also think I screwed up something
during installation. It happens. Shrug.
I have found that I am stuck using fvwm, but I would like to use another
wm. Not very important which one. But I really have no idea how to
accomplish that.
The reason I think I screwed up something else is that the performance
across the board is terribly slow. Happy to reinstall from scratch.

I'm happy to find the  answers reading man pages, but man fvwm wasn't
helpful for me. Which ones should I read?

Running 6.4 stable amd64

Thank you,
Chris Bennett

Re: X won't start with latest snapshot as user (Solution provided)

[Solene]

This is normal. Look at 26th October https://www.openbsd.org/faq/current.html

The suid was removed to prevent bad things to happen. Use xenodm instead of 
startx.

Le 10 novembre 2018 22:00:53 GMT+01:00, Arnoud Otten  a 
écrit :
>Startx doesn`t work anymore on my Lenovo W520.
>I had a working X setup with Mate on 6.4 stable. Then i did an upgrade
>to 6.4 current, snapshot from 5 Nov, and couldn`t start X anymore.
>
>Did a fresh install with that snapshot, and found out, root could start
>X. Upgrade to snapshot from 9 Nov did not resolve the problem for the
>user
>also a clean install did not.
>
>I found this thread about SUID on Xorg, and this fixed the problem for
>my situation:
>
>chmod 4755 Xorg
>
>https://groups.google.com/forum/#!topic/mailing.openbsd.bugs/VKf8XZAco08
>
>[   198.792]
>X.Org X Server 1.19.6
>Release Date: 2017-12-20
>[   198.819] X Protocol Version 11, Revision 0
>[   198.833] Build Operating System: OpenBSD 6.4 amd64
>[   198.846] Current Operating System: OpenBSD bsd520.my.domain 6.4
>GENERIC.MP#429 amd64
>[   198.860] Build Date: 09 November 2018  11:59:57AM
>[   198.874]
>[   198.888] Current version of pixman: 0.34.0
>[   198.901]Before reporting problems, check http://wiki.x.org
>to make sure that you have the latest version.
>[   198.901] Markers: (--) probed, (**) from config file, (==) default
>setting,
>(++) from command line, (!!) notice, (II) informational,
>(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>[   198.957] (==) Log file:
>"/home/arnoud/.local/share/xorg/Xorg.0.log", Time: Sat Nov 10 21:24:06
>2018
>[   198.972] (==) Using system config directory
>"/usr/X11R6/share/X11/xorg.conf.d"
>[   198.972] (==) No Layout section.  Using the first Screen section.
>[   198.972] (==) No screen section available. Using defaults.
>[   198.972] (**) |-->Screen "Default Screen Section" (0)
>[   198.972] (**) |   |-->Monitor ""
>[   198.972] (==) No monitor specified for screen "Default Screen
>Section".
>Using a default monitor configuration.
>[   198.972] (==) Automatically adding devices
>[   198.972] (==) Automatically enabling devices
>[   198.972] (==) Not automatically adding GPU devices
>[   198.972] (==) Max clients allowed: 256, resource mask: 0x1f
>[   198.973] (==) FontPath set to:
>/usr/X11R6/lib/X11/fonts/misc/,
>/usr/X11R6/lib/X11/fonts/TTF/,
>/usr/X11R6/lib/X11/fonts/OTF/,
>/usr/X11R6/lib/X11/fonts/Type1/,
>/usr/X11R6/lib/X11/fonts/100dpi/,
>/usr/X11R6/lib/X11/fonts/75dpi/
>[   198.973] (==) ModulePath set to "/usr/X11R6/lib/modules"
>[   198.973] (II) The server relies on wscons to provide the list of
>input devices.
>If no devices become available, reconfigure wscons or disable
>AutoAddDevices.
>[   198.973] (II) Loader magic: 0x9d2ea27c000
>[   198.973] (II) Module ABI versions:
>[   198.973]X.Org ANSI C Emulation: 0.4
>[   198.973]X.Org Video Driver: 23.0
>[   198.973]X.Org XInput driver : 24.1
>[   198.973]X.Org Server Extension : 10.0
>[   198.973] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
>(Permission denied)
>Check that you have set 'machdep.allowaperture=1'
>in /etc/sysctl.conf and reboot your machine
>refer to xf86(4) for details
>[   198.973]linear framebuffer access unavailable
>[   198.973] (II) LoadModule: "glx"
>[   198.974] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
>[   198.978] (II) Module glx: vendor="X.Org Foundation"
>[   198.978]compiled for 1.19.6, module version = 1.0.0
>[   198.978]ABI class: X.Org Server Extension, version 10.0
>[   198.978] (==) Assigned the driver to the xf86ConfigLayout
>[   198.978] (EE) No drivers available.
>[   198.978] (EE)
>Fatal server error:
>[   198.991] (EE) no screens found(EE)
>[   199.005] (EE)
>Please consult the The X.Org Foundation support
> at http://wiki.x.org
> for help.
>[   199.018] (EE) Please also check the log file at
>"/home/arnoud/.local/share/xorg/Xorg.0.log" for additional information.
>[   199.032] (EE)
>[   199.048] (EE) Server terminated with error (1). Closing log file.
>
>
>
>
>
>
>OpenBSD Snapshot 9 November
>
>
>
>
>OpenBSD 6.4-current (GENERIC.MP) #429: Fri Nov  9 11:38:58 MST 2018
>   dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>real mem = 17041059840 (16251MB)
>avail mem = 16515330048 (15750MB)
>mpath0 at root
>scsibus0 at mpath0: 256 targets
>mainbus0 at root
>bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (67 entries)
>bios0: vendor

X won't start with latest snapshot as user (Solution provided)

[Arnoud Otten]

Startx doesn`t work anymore on my Lenovo W520.
I had a working X setup with Mate on 6.4 stable. Then i did an upgrade to 6.4 
current, snapshot from 5 Nov, and couldn`t start X anymore.

Did a fresh install with that snapshot, and found out, root could start X. 
Upgrade to snapshot from 9 Nov did not resolve the problem for the user
also a clean install did not.

I found this thread about SUID on Xorg, and this fixed the problem for my 
situation:

chmod 4755 Xorg

https://groups.google.com/forum/#!topic/mailing.openbsd.bugs/VKf8XZAco08

[   198.792]
X.Org X Server 1.19.6
Release Date: 2017-12-20
[   198.819] X Protocol Version 11, Revision 0
[   198.833] Build Operating System: OpenBSD 6.4 amd64
[   198.846] Current Operating System: OpenBSD bsd520.my.domain 6.4 
GENERIC.MP#429 amd64
[   198.860] Build Date: 09 November 2018  11:59:57AM
[   198.874]
[   198.888] Current version of pixman: 0.34.0
[   198.901]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   198.901] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   198.957] (==) Log file: "/home/arnoud/.local/share/xorg/Xorg.0.log", Time: 
Sat Nov 10 21:24:06 2018
[   198.972] (==) Using system config directory 
"/usr/X11R6/share/X11/xorg.conf.d"
[   198.972] (==) No Layout section.  Using the first Screen section.
[   198.972] (==) No screen section available. Using defaults.
[   198.972] (**) |-->Screen "Default Screen Section" (0)
[   198.972] (**) |   |-->Monitor ""
[   198.972] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   198.972] (==) Automatically adding devices
[   198.972] (==) Automatically enabling devices
[   198.972] (==) Not automatically adding GPU devices
[   198.972] (==) Max clients allowed: 256, resource mask: 0x1f
[   198.973] (==) FontPath set to:
/usr/X11R6/lib/X11/fonts/misc/,
/usr/X11R6/lib/X11/fonts/TTF/,
/usr/X11R6/lib/X11/fonts/OTF/,
/usr/X11R6/lib/X11/fonts/Type1/,
/usr/X11R6/lib/X11/fonts/100dpi/,
/usr/X11R6/lib/X11/fonts/75dpi/
[   198.973] (==) ModulePath set to "/usr/X11R6/lib/modules"
[   198.973] (II) The server relies on wscons to provide the list of input 
devices.
If no devices become available, reconfigure wscons or disable 
AutoAddDevices.
[   198.973] (II) Loader magic: 0x9d2ea27c000
[   198.973] (II) Module ABI versions:
[   198.973]X.Org ANSI C Emulation: 0.4
[   198.973]X.Org Video Driver: 23.0
[   198.973]X.Org XInput driver : 24.1
[   198.973]X.Org Server Extension : 10.0
[   198.973] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
(Permission denied)
Check that you have set 'machdep.allowaperture=1'
in /etc/sysctl.conf and reboot your machine
refer to xf86(4) for details
[   198.973]linear framebuffer access unavailable
[   198.973] (II) LoadModule: "glx"
[   198.974] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
[   198.978] (II) Module glx: vendor="X.Org Foundation"
[   198.978]compiled for 1.19.6, module version = 1.0.0
[   198.978]ABI class: X.Org Server Extension, version 10.0
[   198.978] (==) Assigned the driver to the xf86ConfigLayout
[   198.978] (EE) No drivers available.
[   198.978] (EE)
Fatal server error:
[   198.991] (EE) no screens found(EE)
[   199.005] (EE)
Please consult the The X.Org Foundation support
 at http://wiki.x.org
 for help.
[   199.018] (EE) Please also check the log file at 
"/home/arnoud/.local/share/xorg/Xorg.0.log" for additional information.
[   199.032] (EE)
[   199.048] (EE) Server terminated with error (1). Closing log file.






OpenBSD Snapshot 9 November




OpenBSD 6.4-current (GENERIC.MP) #429: Fri Nov  9 11:38:58 MST 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17041059840 (16251MB)
avail mem = 16515330048 (15750MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (67 entries)
bios0: vendor LENOVO version "8BET66WW (1.46 )" date 06/14/2018
bios0: LENOVO 4284Y54
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA SSDT 
SSDT UEFI UEFI UEFI
acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4) EHC1(S3) 
EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz, 2193.20 MHz, 06-2a-07
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,

Re: X not start

[Daniel Bareiro]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Oct 17, Stijn [EMAIL PROTECTED] wrote:

 Hi Daniel,

Hi, Stijn.

 Did you already tried to start X with the command startx without
 using any xorg.conf file (none in /root/ or /etc/X11/)? When no
 xorg.conf file is found X will try to run with default settings. Does
 X start up that way?

I did not try to initiate X of that way. After to have tried, it did not
work either. This is what I obtain in the log:

(EE) Unable to locate/open config file
(EE) Failed to load module dri (module does not exist, 0)
(EE) Failed to load module fbdev (module does not exist, 0)
(EE) CIRRUS(0): No valid modes found
(EE) Screen(s) found, but none have a usable configuration.

 For the dri error, if I recall correctly 4.3 does not have dri
 enabled, so you can ignore this error.

Ok.

Thanks for your reply.

Regards,
Daniel
iEYEARECAAYFAkj6cxsACgkQZpa/GxTmHTdP1wCbBYhsic8AzbbX+Rs1L7GhrgSF
uS0AnjWgFSuf1QEfRUGE8yC/3ifcVcpx
=0otZ
-END PGP SIGNATURE-

Re: X not start

[Girish Venkatachalam]

On 20:37:53 Oct 18, Daniel Bareiro wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 I did not try to initiate X of that way. After to have tried, it did not
 work either. This is what I obtain in the log:
 
 (EE) Unable to locate/open config file

Why are you getting this error? Copy the /root/xorg.conf.new file to
/etc/X11/xorg.conf

 (EE) Failed to load module dri (module does not exist, 0)

Harmless.

 (EE) Failed to load module fbdev (module does not exist, 0)

Harmless but you can remove that line from xorg.conf.

You have to look for Load fbdev line.

 (EE) CIRRUS(0): No valid modes found
 (EE) Screen(s) found, but none have a usable configuration.
 

This is what you have to fix.

Try googling and look at pcidump(8) and also trying modifying the Modes
line to something conservative like 800x600 just for testing.

You need a bit of patience with X. ;)

Best of luck!

-Girish

Re: X not start

[Daniel Bareiro]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Oct 17, Girish Venkatachalam [EMAIL PROTECTED] wrote:

 I'm trying to use KDE in OpenBSD but I'm having problems with the
 basic step: to obtain that X server works. I have this problem with
 OpenBSD 4.3. With snapshot of OpenBSD 4.4, X server works without
 problems. For both cases, I indicated during the installation that X
 server would be used.
 
 Both installations are kvm virtual machines in the same hardware.
 
 In both installations I generate the X configuration file with:
 
 # X -configure
 
 And I test it with:
 
 # X -config xorg.conf.new

 If the previous step reported success then you should try exactly what
 it says. And it asks you to run

 # X -config /root/xorg.conf.new

 There is a silly bug and 'X -config' won't work with relative paths...

Oh, ok :-)

After to have tried 'X -config' with complete path, it follows without
initiating X on OpenBSD 4.3. But the error that I obtain changed
slightly.

Of that I three indicated before, now only I see: 

(EE) Failed to load module dri (module does not exist, 0)

Also I see the following, that although was in log that I copied, had
not indicated them.

(EE) CIRRUS(0): No valid modes found
(EE) Screen(s) found, but none have a usable configuration.

Thanks for your reply, Girish.

Regards,
Daniel
iEYEARECAAYFAkj4WQIACgkQZpa/GxTmHTfeRQCgj+kngBkbbcNvPMEiAUOeeSiw
6WsAoIAMiQuSJU4FMTJCSLt8J6ijDHkg
=m4Yr
-END PGP SIGNATURE-

X not start

[Daniel Bareiro]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi all!

I'm trying to use KDE in OpenBSD but I'm having problems with the basic
step: to obtain that X server works. I have this problem with OpenBSD
4.3. With snapshot of OpenBSD 4.4, X server works without problems. For
both cases, I indicated during the installation that X server would be
used.

Both installations are kvm virtual machines in the same hardware.

In both installations I generate the X configuration file with:

# X -configure

And I test it with:

# X -config xorg.conf.new

Doing 'diff' of both configuration files, I obtain the following thing:

# diff xorg.conf.new.43 xorg.conf.new.44
21a22
   Load  dri

It is the log that I obtain in OpenBSD 4.3:

- 
(--) checkDevMem: using aperture driver /dev/xf86
(--) Using wscons driver on /dev/ttyC4 in pcvt compatibility mode
(version 3.32)

This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the xorg product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.

X.Org X Server 1.4.0.90
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: OpenBSD 4.3 i386
Current Operating System: OpenBSD puffy.educ.ar 4.3 GENERIC#698 i386
Build Date: 07 March 2008  07:40:46PM

Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Thu Oct 16 22:33:15 2008
(EE) Unable to locate/open config file: xorg.conf.new
(II) Loader magic: 0x3c01c4e0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 2.0
X.Org XInput driver : 2.0
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
(II) Loader running on openbsd
(II) LoadModule: pcidata
(II) Loading /usr/X11R6/lib/modules//libpcidata.so
(II) Module pcidata: vendor=X.Org Foundation
compiled for 1.4.0.90, module version = 1.0.0
ABI class: X.Org Video Driver, version 2.0
(WW) OS did not count PCI devices, guessing wildly
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,1237 card , rev 02 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,7000 card , rev 00 class 06,01,00 hdr 80
(II) PCI: 00:01:1: chip 8086,7010 card , rev 00 class 01,01,80 hdr 00
(II) PCI: 00:01:3: chip 8086,7113 card , rev 03 class 06,80,00 hdr 00
(II) PCI: 00:02:0: chip 1013,00b8 card , rev 00 class 03,00,00 hdr 00
(II) PCI: 00:03:0: chip 10ec,8029 card , rev 00 class 02,00,00 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,0), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1  0   0x - 0x (0x1) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1  0   0x - 0x (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1  0   0x - 0x (0x0) MX[B]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:1:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is
set)
(--) PCI:*(0:2:0) Cirrus Logic GD 5446 rev 0, Mem @ 0xf000/25,
0xf200/12
New driver is cirrus
(==) Using default built-in configuration (55 lines)
(==) --- Start of built-in configuration ---
Section Module
Loadextmod
Loaddbe
Loadglx
Loadfreetype
Loadtype1
Loadrecord
Loaddri
EndSection
Section Monitor
Identifier  Builtin Default Monitor
EndSection
Section Device
Identifier  Builtin Default cirrus Device 0
Driver  cirrus
EndSection
Section Screen
Identifier  Builtin Default cirrus Screen 0
Device  Builtin Default cirrus Device 0
Monitor Builtin Default Monitor
EndSection
Section Device
Identifier  Builtin Default fbdev Device 0
Driver  fbdev
EndSection
Section Screen
Identifier  Builtin Default fbdev Screen 0
Device  Builtin Default fbdev Device 0
Monitor Builtin Default Monitor
EndSection
Section Device
Identifier  Builtin Default vesa Device 0
Driver  vesa
EndSection
Section 

Re: X not start

[Girish Venkatachalam]

On 00:55:38 Oct 17, Daniel Bareiro wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hi all!
 
 I'm trying to use KDE in OpenBSD but I'm having problems with the basic
 step: to obtain that X server works. I have this problem with OpenBSD
 4.3. With snapshot of OpenBSD 4.4, X server works without problems. For
 both cases, I indicated during the installation that X server would be
 used.
 
 Both installations are kvm virtual machines in the same hardware.
 
 In both installations I generate the X configuration file with:
 
 # X -configure
 
 And I test it with:
 
 # X -config xorg.conf.new
 

If the previous step reported success then you should try exactly what
it says. And it asks you to run

# X -config /root/xorg.conf.new

There is a silly bug and 'X -config' won't work with relative paths...

-Girish