Date: Tue, 20 Sep 2011 09:08:13 -0700 From: Garrett Cooper <yanegomi@gmail.com> To: Michal Varga <varga.michal@gmail.com> Cc: Tom Evans <tevans.uk@googlemail.com>, freebsd-current@freebsd.org, Antonio Olivares <olivares14031@gmail.com> Subject: Re: no X after installing xorg + xfce Message-ID: <CAGH67wTXZxwqm-XdJNAmMoKis-VgfB9-OOaJ8hariWKi1BU%2BQQ@mail.gmail.com> In-Reply-To: <1316521778.1744.92.camel@xenon> References: <20110918042853.3D61C106566C@hub.freebsd.org> <CAGH67wSBf5rikMXh18Cviz6f%2BsuwxsqfXp%2B%2Bonm6aEBYJ5VJ1w@mail.gmail.com> <CAJ5UdcN_-p2rjbqcUnBv28BOikpF3KRdDJ0obiTCWt9pssS51g@mail.gmail.com> <CAJ5UdcMsVwE9Lf2coEa5Gc=TcB95LBfPgASykta_UWCdNEJ91g@mail.gmail.com> <CAON0-RfOkki2LpzDcyaONiNF30r1BU=dDr4Ry0bhuF%2BMv7mi3Q@mail.gmail.com> <CAJ5UdcN2HK6X6FxBhrqA8rqR82azo4rSdNP4t02=Xn5AL1Z72g@mail.gmail.com> <CAFHbX1%2BVJYc7-Zn2v60qnihKrc%2BWKMgt96Gg1-SVF4rKZtq29g@mail.gmail.com> <CAJ5UdcMy%2ByoFcDLT5DURm_BZfufB3vGmnt7q_LVwsfJjtCQfsg@mail.gmail.com> <1316521778.1744.92.camel@xenon>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On Tue, Sep 20, 2011 at 5:29 AM, Michal Varga <varga.michal@gmail.com> wrote:
> On Tue, 2011-09-20 at 07:01 -0500, Antonio Olivares wrote:
>> > I've skimmed the thread, (apologies if I've missed it), but I haven't
>> > yet seen your Xorg log or your config file. Almost every graphics card
>> > should work with VESA at a minimum.
>>
>> I have no Xorg.conf file as it is not needed anymore. I tried to rebuild it,
>> # Xorg -configure
>
> xorg.conf isn't "needed" in case you wish to rely purely on xorg's and
> HAL's autodetection (this is a perfectly bad idea), and if you do not
> need to change any single xorg option from defaults (this would be very
> strange in my book).
>
> There are tons of manuals on the Internet detailing how to write a
> proper xorg configuration file (it even has its own man page - man
> xorg.conf) and as with any properly configured software - it pays off.
>
>
>> process hangs and returns colors on the screen :(
>
> Autodetection blows. You will have to write your configuration manually.
>
>
>> I can't attach Xorg.0.log, I know which driver to use, as I have X
>> working correctly with Linux(Slackware) on that same machine[another
>> hard drive]. It is just that I have no way of saving logs or posting
>> information without taking a picture, I would to put all doubts away.
>
> Honestly, I really don't understand the "I can't attach Xorg.log"
> wording.
>
> It's a physical log file, just a regular file. How is it that you cannot
> copy it from the particular machine/hard drive/filesystem and put it
> someplace on the Internet, or paste the relevant parts inline in one of
> the emails?
>
>
>> As of know I will rebuild world, install new kernel remove all ports
>> and start from scratch. If I can't get it to work with a fresh start.
>
> There's really nothing wrong with your ports and you'll be only wasting
> your time with this generic and pointless "Windows-style reinstall
> everything" procedure, without actually looking at the issue itself.
>
> The other poster(s) already told you. If you need any help, you will
> have to provide error messages, you will have to provide error logs (and
> you will have to properly configure your xorg, because as you already
> noticed, autodetection clearly doesn't work the way you expect it to).
>
>
>> I will wait for BETA 3 or an RC :) I just want to help in testing,
>> it is that I can't supply the information as I would like to :(
>
> I can 100% guarantee that BETA3 nor RC won't change anything in regard
> to the issue you're experiencing. Your problem lies elsewhere and you
> didn't even start systematically investigating it.
Newb hacker tip number one: try CTRL-ALT-F1 when you get the
technicolor screen. If your system isn't hosed then you'll get the
first tty.
The only time I can think of where /var/log/Xorg.0.log wouldn't be
populated with something useful is if the kernel module livelocks
talking to the card and/or fsck takes out the file on the next reboot
because it was in use.
And yes Michal is right, IIRC. 64-bit drivers didn't exist on that version.
Just try this file and get back to us please with something more
useful than "it doesn't work". Otherwise we can't help you .
-Garrett
[-- Attachment #2 --]
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
# Option "Xinerama" "0"
EndSection
Section "Files"
ModulePath "/usr/local/lib/xorg/modules"
FontPath "/usr/local/lib/X11/fonts/misc/"
FontPath "/usr/local/lib/X11/fonts/TTF/"
FontPath "/usr/local/lib/X11/fonts/OTF"
FontPath "/usr/local/lib/X11/fonts/Type1/"
FontPath "/usr/local/lib/X11/fonts/100dpi/"
FontPath "/usr/local/lib/X11/fonts/75dpi/"
EndSection
Section "Module"
Load "extmod"
Load "dbe"
# Load "glx"
Load "dri"
Load "dri2"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/sysmouse"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "MyVendor"
ModelName "MyMonitor"
EndSection
Section "Device"
Identifier "Card0"
Driver "vesa"
VendorName "MyVendor"
BoardName "MyCard"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGH67wTXZxwqm-XdJNAmMoKis-VgfB9-OOaJ8hariWKi1BU%2BQQ>