Problem with X
Posts: 10
When booting on my Armada 3500, it did not configured X. I had to specify xdrvr=chips on boot prompt.
If I juste put in the CD and
Posts: 10
If I juste put in the CD and boot, I only get the text-mode login prompt, and XF86Config-4 is not complete (section for graphic card is missing).
If I boot with xdrvr=chips, then I get the graphic login prompt, and can use the KDE environment.
I think I saw an error message during boot-up about X configuration. I'll check it again, and come back with the message.
Starting K Display Manager fails
Posts: 9
Hardware: AMD 3200+ processor, XFX Nvidia 6600 PCI-e display adapter
Using Mepis 3.3.1-1 everything works fine. When I went to update to 3.3.1-2.test3, after the point in the boot sequence for
Starting K Display Manager: kdm
the KDE GUI fails to load, the next line is
MEPIS Linux testing/unstable mepis1 tty1
and I'm put back at the prompt
mepis1 login:
There is no obvious error message. If I logon as root then try to start the KDE desktop with the command startkde, I get
xsetroot: Unable to open display ''
startkde: Starting up ...
ksplash: cannot connect to X server
kdeinit: Aborting. $DISPLAY is not set
startkde: Shutting down ...
etc
I tried adding xdrvr=chips to the boot command, but this did not change anything for me.
thanks

try xdrvr=vesa also make
Posts: 4077
try xdrvr=vesa
also make sure the CD is a good burn (for checking the download use MD5Sum, burn the CD on a CDR (not CDRW) at slow speed)
--
Post questions on www.mepislovers.org too -- very helpful community.
Check out our wiki: www.mepislovers-wiki.org
xdrvr=vesa works
Posts: 9
Adding xdrvr=vesa to the boot options solved the problem, thank you. I will also try burning a new CD.
What Is The Problem?
Posts: 5513
eprevost, was adding "xdrvr=chips" the solution to your problem? You didn't state what the problem is that you are having: no display, some display, too big, too small, what?
Please clarify and we'll be happy to offer help if you need it
Jon