ATI Radeon HD 4350 (RV710) on ASUS P5K Deluxe/WiFi-AP hang at Xorg startup.

[Markiyan Kushnir]

Switched to NVIDIA GeForce 8600 GT (G84). Direct rendering appears to
work using the NVIDIA-FreeBSD-x86-260.19.29 driver (the latest from
the NVidia at the moment), as well as with that from the ports,
currently 256.53. DRI does not work with the xf86-video-nv 2.1.17.


Markiyan.



2011/1/5 Markiyan Kushnir <markiyan.kushnir at gmail.com>:
> 2011/1/5, Mehmet Erol Sanliturk <m.e.sanliturk at gmail.com>:
>> On Tue, Jan 4, 2011 at 6:55 PM, Markiyan Kushnir <markiyan.kushnir at gmail.com
>>> wrote:
>>
>>> Another DRI-related freeze ...
>>>
>>> ATI Radeon HD 4350 (RV710) on ASUS P5K Deluxe hangs at the
>>> startup of the Xorg with DRI enabled. Hard freeze, the Power Button
>>> does not bring the system down. I could only use the Reset Button.
>>>
>>> % uname -a
>>> FreeBSD localhost.test 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #0: Mon
>>> Jan  3 17:29:21 EET 2011
>>> root at localhost.test:/usr/obj/usr/src/sys/MAREK  i386
>>>
>>> An older Radeon R200 on an Intel 945PRN worked OK running the same FreeBSD
>>> release. This older Radeon, when plugged in the ASUS P5K, hits the same
>>> hard freeze (I actually moved the hard drive and the video card from
>>> that Intel 945PRM to the ASUS P5K).
>>>
>>> This ASUS board has two PCI-E alots, so I tried a different slot,
>>> no success. As another exercise, I forced a separate IRQ to the video
>>> card using "hw.pci0.2.0.INTA.irq=3" loader tunable (based on the
>>> $PIR table). With this separate irq, still no luck, not sure if I should
>>> try it at all, since the card gets an MSI any way.
>>>
>>> I also tried a trick with forcing the libthr.so.3 linking into the Xorg
>>> binary, discussed a year ago at:
>>>
>>>  http://lists.freebsd.org/pipermail/freebsd-x11/2010-February/009362.html
>>>
>>> I built the xorg-server with the HAL support, no luck.
>>>
>>> As a side note, each test of the Xorg was done on a newly started-up
>>> system,
>>> that is no previous "successful" X session took place.
>>>
>>> Since no Xorg.log.0 in such cases was normally available, I have collected
>>> output from /var/log/messages. Because of the "hw.dri.0.debug: 1", the
>>> output is quite huge, here are a couple of cases:
>>>
>>>
>>> http://sites.google.com/site/markiyankushnir/radeon-dri-freebsd-files/1960.tgz
>>>
>>> http://sites.google.com/site/markiyankushnir/radeon-dri-freebsd-files/1991.tgz
>>>
>>> http://sites.google.com/site/markiyankushnir/radeon-dri-freebsd-files/3238.tgz
>>>
>>> http://sites.google.com/site/markiyankushnir/radeon-dri-freebsd-files/3239.tgz
>>>
>>> http://sites.google.com/site/markiyankushnir/radeon-dri-freebsd-files/3249.tgz
>>>
>>> Additional info:
>>>
>>> % devinfo -rv:
>>>
>>> http://sites.google.com/site/markiyankushnir/radeon-dri-freebsd-files/devinfo-rv.tgz
>>>
>>> % pciconf -lvc
>>>
>>> http://sites.google.com/site/markiyankushnir/radeon-dri-freebsd-files/pciconf-lvc.tgz
>>>
>>> The output of dmesg:
>>>
>>> http://sites.google.com/site/markiyankushnir/radeon-dri-freebsd-files/dmesg.tgz
>>>
>>> The Xorg configuration:
>>>
>>> http://sites.google.com/site/markiyankushnir/radeon-dri-freebsd-files/xorg.conf.tgz
>>>
>>> I am aware that some video card + motherboard ensembles have issues
>>> like this one, so I am curious if anyone could suggest a hint.
>>>
>>> Thanks,
>>> Markiyan.
>>>
>>
>>
>> There is the following list :
>>
>> http://www.asus.com/websites/global/aboutasus/OS/Linux.pdf
>>
>> The mother board P5K Deluxe does not appear in that list . It means that it
>> is not tested and listed for Linux ( which is an indicator about usability
>> by Unix like operating systems ) .
>>
>>
>> Also there is no any such name among  ¨All products¨ list about Main boards
>> :
>>
>>
>> http://www.asus.com/AllProducts.aspx?PG_ID=mKyCKlQ4oSEtSu5m
>>
>>
>> The following board ( if your board is exactly that one )
>> P5K Deluxe/WiFi-AP( exact match of names is very important ) is for only XP
>> and Vista :
>>
>> http://www.asus.com/product.aspx?P_ID=0e9NyGEDLjtBRtyB
>>
>>
>
> You are right, the board is P5K Deluxe/WiFi-AP. I have updated the
> subject with the full name.
>
>
>> If name of your board is exactly
>>
>> P5K Deluxe
>> these are different from each other ( in the sense that , if one is working
>> with a Unix-like operating system , it does not make a guaranty that the
>> other will work ( Please see the above Linux.pdf list and products in All
>> Products list for similar sounding names )) .
>>
>>
>> It could not be possible to see your dmesg because access to
>> sites.google.com is prohibited in Turkey .
>>
>
> Sorry, didn't know of it. I am attaching dmesg, and others with this mail.
>
>>
>> To test your main board , you may install one of the Linux (  Asus is using
>> Ubuntu , RedHat , SuSe , Fedora ) distributions . If it works well , this
>> may mean that FreeBSD
>> related driver(s) has(have) problems .
>>
>>
>
> I bought this board from my friend. He was successfully running Linux
> on it, including Xorg + DRI. So looks like it's an issue with the
> FreeBSD handling this board?
>
> I have just got an idea to try an NVIDIA card with this motherboard.
> Will let you know if it works.
>
>> My expectation is that FreeBSD or any Linux will NOT work satisfactorily on
>> that board
>> because it is mainly produced for Windows means some circuits are not
>> suitable for Unix-like operating systems . It may work for a while but it is
>> very likely that , at some point it will crash ( from my personal experience
>> from another board ).
>>
>>
>
> I also have the same feeling, but cannot certainly tell. I don't know
> which details to give to help fix it. From the message logs (all they
> are kernel-side) it's clear that some initial step went OK, and in all
> cases the last message before the hanging is
>
>  [drm:pid1960:drm_ioctl] pid=1960, cmd=0x800c6459, nr=0x59, dev
> 0x86f0a880, auth=1
>
> The ioctl number (0x59, vendor specific) is defined as
> DRM_RADEON_SETPARAM in the xorg ati driver's  radeon_drm.h. This ioctl
> is called in several places to set GART parameters, tiling, etc... in
> the driver code.  Looks like an attempt to set some video card
> parameter makes the system freeze. I don't know which point is it in
> the overall initialization path. I think I could trace it, if needed.
>
>
>> It is not clear from you message that whether FreeBSD is installed in that
>> board , or an installed hard disk in another board is moved to that board .
>> If previously installed hard disk moved without new install in the new main
>> board ( I think , this is not the case ), it will surely not work .
>>
>>
>
> Here I am not so sure on this point, since I widely use this approach.
> I have a home file server, which runs OK both on a removable system
> drive, which I prepared on a different system, or, if needed, it runs
> on a network-mounted system drive, that is completely without its own
> system drive.
>
> In the case being discussed here, only couple of things is needed:
> adjust the names of FreeBSD slices in the /etc/fstab file, unless they
> were previously labeled with glabel, and "position independent" labels
> are used; names of network interfaces in the /etc/rc.conf[.local] --
> all this is pretty obvious in FreeBSD.
>
> Before posting to the list, I also made a clean install on the system
> without any hardware manipulation, and ran several attempts, so I am
> pretty sure, the drive should not be an issue here.
>
>
>> ( If the above links do not work , please access directly to Asus site and
>> follow links in their pages . )
>>
>>
>
> Thank you for your suggestion, I will explore the possibility to try
> different motherboard (and different video card). I will also think of
> finding a way to fix the problem on the P5K Deluxe/WiFi-AP. I am also
> considering to post to freebsd-hardware@ and freebsd-drivers@ ...
>
>> Thank you very much .
>>
>> Mehmet Erol Sanliturk
>>
>