Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 3 Feb 2009 18:02:45 +0100 (CET)
From:      "Torgeir Hoffmann" <twhoffma@student.matnat.uio.no>
To:        Fernando =?iso-8859-1?Q?Apestegu=EDa?= <fernando.apesteguia@gmail.com>
Cc:        Ewald Jenisch <a@jenisch.at>, freebsd-questions@freebsd.org, Luke Dean <luked@pobox.com>
Subject:   Re: X.org-update -> screen garbled / settings for xorg.conf?
Message-ID:  <f8592e0c044f05d1b8fea509f231b475.squirrel@webmail.uio.no>
In-Reply-To: <1bd550a00902021020y7ecc02doe8c3859997e5b61@mail.gmail.com>
References:  <20090130144614.GA4897@aurora.oekb.co.at> <alpine.BSF.2.00.0901301101050.94462@border.lukas.is-a-geek.org> <20090202163647.GD2908@aurora.oekb.co.at> <1bd550a00902021020y7ecc02doe8c3859997e5b61@mail.gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Hi,

> On Mon, Feb 2, 2009 at 5:36 PM, Ewald Jenisch <a@jenisch.at> wrote:
>> On Fri, Jan 30, 2009 at 11:30:02AM -0800, Luke Dean wrote:
>>>
>>> Me too.
>>> I started a thread a few days ago titled "Restarting new Xorg freezes
>>> system".
>>> My symptoms are the same as yours.
>>> I'm not running hald at all.
>>> I'm not using full-blown gnome, just windowmaker.
>>> I'm using the "radeon" driver on an ATI HD 4350
>>>
>>> I just tried switching to the "vesa" driver, and now I can stop and
>>> start
>>> X as much as I want with no problems whatsoever.
>>> I know that this was not a problem with the "radeon" driver prior to
>>> the
>>> Xorg update.
>>
>> Hi,
>>
>> Did a few tests more:
>>
>> 1) Section "ServerLayout"
>>    Option "AllowEmptyInput" "false"
>> Section "Device"
>>       Driver      "radeon"
>> moused running
>> hald running
>>
>> Result: X (gnome in my case) starts, mouse moves. Upon leaving X the
>> console is to something different than 80x25 lines - at least I can't
>> see about 2-3 lines on the bottom of the screen. However - as soon as
>> a start X again I get graphical junk on the display, mouse & keyboard
>> frozen, no switching of consoles nor can I log in via the net (ssh)
>
> Just for the record, this used to happen in Linux (Fedora 9) but it's
> working since some time ago (sorry, I don't remember when this was
> fixed)
> radeon now works and doesn't freeze if you try to bring the X Server up
> again.
>
> I'm using Xorg 7.4 too


Just wanted to say that I experienced similar problems quite some months ago,
and posted under the title:

"Re: [FreeBSD 7] Radeon Mobility M10/9600 + xorg 7.3 + ati/radeon driver
causes complete system hang/freeze".


I never got it to work, and that was with xorg 7.3. Also, everything
worked with vesa. I tried everything from disabling most things in
rc.conf, most modules,
dri in xorg.conf. I tried deleting the renaming the log for xorg, and then
you
could most of the times start xorg once, but not twice. The second time would
result in a black screen. (of course removing the log and the following
effect
is most likely random).

I had an idea that it might be that the drm-implementation wasn't able to
load the microcode (?) for the r300 correctly sometimes, but this is
guesswork
at best. Is it possible that this is a bug partly related to xorg, but
more related
to the radeon driver and freebsd that slipped through in the last
bug-hunting?

> However, I experience the same problems in my system (ATI RadeonHD
> 2400 with FreeBSD 7.1-RELEASE-p2)
>
>
>>
>>
>> 2) Same as 1) above however this time with
>> Driver "radeonhd"
>>
>> Result: Almost the same as 1) above - only difference: When I leave X
>> the console comes back again to 80x25 lines. Hoever - like in 1) above
>> - the second attempt to start X ends in a machine completely frozen :-(
>>
>> 3) Same as 1) - this time with
>> Driver "vesa"
>>
>> Result: Everything works - i.e. back and forth between X and
>> console. Sure enough working with Vesa is a workaround only given the
>> huge difference in speed between the Vesa- and radeon drivers.
>>
>>
>> 4) Option "AutoAddDevices" "Off" under 'Section "ServerLayout"'
>> with
>> Driver      "radeonhd"
>>
>> Result: X works only once (as in Tests 1&2 above). Second attempt to
>> start X gives a "frozen box" again.
>>
>>
>>
>> As you already mentioned
>>
>> o) no problem with VESA-Driver
>>
>> o) no problems with radeon-driver prior to the Upgrade to X 7.4
>>
>>
>> Hope this helps someone out there to track things down.


//Torgeir




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?f8592e0c044f05d1b8fea509f231b475.squirrel>