Results 1 to 7 of 7
I just set up Slackintosh on my Powerbook G3 and I when I log in as root and type startkde. I get an error message that says:
xsetroot: unable to ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 11-11-2005 #1Linux Newbie
- Join Date
- Nov 2004
- Location
- Jersey
- Posts
- 102
Problems with x-org in Slackintosh
I just set up Slackintosh on my Powerbook G3 and I when I log in as root and type startkde. I get an error message that says:
xsetroot: unable to open display' '
xset: unable to open display ''''
xset: unable to open display ''''
xset: unable to open display ''''
xsetroot: unable to open display' '
startkde: Starting up...
startkde: Running kpersonalizer...
kwin: cannot connect to X server
keprsonalizer: cannot connect to X server
keprsonalizer: cannot connect to X server
keprsonalizer: cannot connect to X server
keprsonalizer: cannot connect to X server
keprsonalizer: cannot connect to X server
keprsonalizer: cannot connect to X server..........
and i t will keep going until I hit crtl c.
Any suggestions?Registered user #372186 -- http://counter.li.org
- 11-11-2005 #2Linux Newbie
- Join Date
- Nov 2004
- Location
- Jersey
- Posts
- 102
Note:::
When I run Xorg -configure, at the top of the screen I see an error message that says:
XSERVTranSocketOpenCOTSServer: Unable to open socket for inet6
XSERVTransOpen: transport open failed for inet6/slackintosh:0
XSERVTransMakeAllCOTServerListeners: failed to open listeners for inet6Registered user #372186 -- http://counter.li.org
- 11-12-2005 #3
Were you able to successfully configure X? Also, what happens if you do startx instead of startkde?
BryanLooking for a distro? Look here.
"There can be no doubt that all our knowledge begins with experience." - Immanuel Kant (Critique of Pure Reason)
Queen's University - Arts and Science 2008 (Sociology)
Registered Linux User #386147.
- 11-13-2005 #4Linux Newbie
- Join Date
- Apr 2005
- Location
- CT --> PA
- Posts
- 170
you don't have an Xserver running.
use startx instead of startkdeChicks dig giant mechanized war machines
- 11-15-2005 #5Linux Newbie
- Join Date
- Nov 2004
- Location
- Jersey
- Posts
- 102
I tried startx and I get this:
xauth: creating new authority file /root/.Xauthority
xauth: creating new authority file /root/.Xauthority
_XSERVTransSocketOpenCOTSServer: Uanble to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/slackintosh:0
_XSERVTransMakeAllCOTServerListeners: failed to open listeners for inet6
:BUCH OF UNIMPORTANT LINES:
(EE) Failed to load module "vesa" (module does not exists, 0)
(EE) No drivers available.
Fatal server error:
no screens found
XIO: Fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.Registered user #372186 -- http://counter.li.org
- 11-25-2005 #6Just Joined!
- Join Date
- Nov 2005
- Posts
- 1
I had that same problem. I've installed slackintosh on a blue powermac. If you use "fbdev" instead of "vesa" as the driver in xorg.conf it'll work.
The vda chipset in this mac is the ATI rage 128 RE/SE but infortunately none of the ati drivers (ati, atimisc & r12
work. They're unable to locate the video BIOS. I havn't figured out how to get them working yet. Any ideas anyone?
Anyway using fbdev works but its not very fast.
Regards,
John
- 02-21-2007 #7Just Joined!
- Join Date
- Feb 2007
- Posts
- 2
Simple fix
Hey guys,
I was having the same problem, and there really isn't a lot on the web that really tells you how to fix this problem, so I hacked at it for a bit and found a solution.
I am running slackintosh 11.0 with the kernel 2.6.20 on s g4 power mac. It has an ati radeon 7500 agp card.
Basically to fix this, is really simple. I went through a lot to come to this. I used Xorg -configure and had no luck, but examining the xorg.conf file it created is what led me to the solution.
If you have an ati card, the solution is as simple as opening the vesa xorg.conf and replacing where it is set to the vesa driver, with ati, telling it to use the ati driver. the vesa config file is already set up nicely, you just need to set it to the drive for the card you are using.
In this section,
# ************************************************** ********************
# Graphics device section
# ************************************************** ********************
# Any number of graphics device sections may be present
Section "Device"
Identifier "VESA Framebuffer"
Driver "vesa"
#VideoRam 4096
# Insert Clocks lines here if appropriate
EndSection
Change it too
# ************************************************** ********************
# Graphics device section
# ************************************************** ********************
# Any number of graphics device sections may be present
Section "Device"
Identifier "VESA Framebuffer"
Driver "ati"
#VideoRam 4096
# Insert Clocks lines here if appropriate
EndSection
there are specific drivers for nvidia too, I am not sure if it is simply nvidia, or if it is called something else.
hope this works for you!!!


Reply With Quote
