In my new pc Xorg don't work

[vinnie]

Ok i start from a microcore with core elements, after run:
$ tce-load -w -i -r Xorg....
$ " "                    openbox...
$start x
Black screen and return to prompt
   xauth: creating new xautority file /home/tc/.Xauthority

I also tried to install graphics-2.6.29.1-tinycore.tczm with no result.
My pc is a asus M4A785TD-M EVO (785G) with an integrated ati 4200 hd graphics.


I pur my /var/log/Xorg.0.log as attachment and my /etc/X11/xorg.conf.vesa (autoconfigured)

   
what can I do?


P.s. another secondary question, with command "sudo halt" the pc stops al processes but don't shutdown the pc, i must press the start button for 5 seconds. What is the command to turn off the pc?

[jur]

P.s. another secondary question, with command "sudo halt" the pc stops al processes but don't shutdown the pc, i must press the start button for 5 seconds. What is the command to turn off the pc?

sudo poweroff

[Juanito]

..or "sudo exitcheck.sh shutdown"

[vinnie]

Ok, thanks for suggestion of command.
For xorg you don't have any suggestion?

   
I added txt extension to attachments so you can see directly from the browser.

[^thehatsrule^]

From the xorg log, it doesn't seem like you are using any xorg.conf at all (confless).

Try using one, but comment out the glx line (or perhaps try the xorg.conf.vesa) by prepending a #

[vinnie]

I used xorg.conf.vesa already present in the file /etc/X11/, i should use another? using the name xorg.conf without .vesa?

Another hypothetical reason could be the series of my video card? r700 is much recently, and is given as supported in part on xorg site (but vesa should go at leas?).

Thank's to all for yours attention

[Juanito]

What I found with my intel graphics chipset is that xorg confless does not work and "Xorg -config" does not work either.

Maybe the best thing to do is to google on "xorg.conf" and the name of your machine and/or graphics chipset - you're almost certain to find an example of a working xorg.conf

[vinnie]

One example is this http://bbs.archlinux.org/viewtopic.php?pid=648175#p648175 . but all the command that i have find for search busID of graphics card don't work

Ok, i prove to generate a Xorg.conf without .vesa

[Juanito]

Would libpci and pci-utils help search for the graphics card bus id?

[jur]

Xorg -configure in tc didn't work for me either. Xorg does work fine for me in other distros eg puppylinux; it seems to be a problem with the tc-compiled version. I used setting from my xorg.conf file generated in puppylinux. There are other distros that Xorg also don't work well for me, such as slitaz. There nothing in Xorg worked, I abandoned it.

[^thehatsrule^]

In general, the vesa driver will work for most setups, so the model should not matter.  Xorg will attempt to use the best suited driver though.  To use a configuration file, it should be /etc/X11/xorg.conf - there should be some details in the .info.

Try the usual X -configure, then manually edit the display driver to have "vesa" (autoconfigure should have your busID automatically saved too).

Side note: the gfx chipset core appears to be a rv620, which is not a r700 (which are currently only discrete, and imply something along the lines of a radeon 4850/4870 X2 - EDIT: those appear to be supported by the radeon driver).  It probably came out after this Xorg release, which is why the radeon driver does not recognize it.

[vinnie]

Ok i prove all:
.rename xorg.conf.vesa in xorg.conf
.comment the glx line
.use the command X -configure (i have one error from this command) and replace the xorg.conf.new in my home in /etc/X11/xorg.conf
.replace this configuration findend in internet

Code: [Select]

Section "Device"
        Identifier  "HD4200"
        Driver      "radeon"
        BusID       "PCI:1:5:0"
#        Option      "VGA-0"  "Samsung"
#        Option      "DVI-0"  "Dell"
EndSection

Section "Screen"
        Identifier   "HD4200"
        Device       "HD4200"
        DefaultDepth     24
    Subsection "Display"
                Virtual 3200 1200
        EndSubsection
EndSection

Section "DRI"
 Group        "staff"
 Mode         0666
EndSection
All this don't led me to success, the only thing that has changed is the black screen is no longer displayed, instead i remain in the command line and press ctrl+c for unblock the situation.
The last test I can do is to use the xorg.conf of PuppyLinux but K3b on my other notebook don't erase my rewitrable disk :/


You think that i must remain  waiting for a rebuild of xorg?

[^thehatsrule^]

Try the usual X -configure, then manually edit the display driver to have "vesa" (autoconfigure should have your busID automatically saved too).