Jump to content
Compatible Support Forums
Sign in to follow this  
debianUser

Trouble with x windows

Recommended Posts

I have installed Debian Sarge on my new Sony VGN-FS550 and I am having some trouble getting xwindows to install. I have all the packages I need for the X system and gdm installed. When I try and run gdm or startx the output says "no screens found" along with much more (which I can provide if necessary). Sarge does not recognize the intel 910/915 graphics chipset and it does not have that option stock. I have tried installing the drivers from the intel website but their installer bombs out. Does anyone have any suggestions?

 

Thanks

Share this post


Link to post

I looked around and found that Debian does not support the 915 graphics chipset. Previous models with the 855 required special drivers as well. I bet that the drivers that you found are in a gz compressed format? Not a deb package? Can you supply a link to the download page?

 

In this case, you need to have the sarge compilers installed to do the installation of the drivers. Did you install the development packages during the install as well?

 

I'm afraid that I won't be much help here, except to tell you that Vaio laptops are a special problem with many Linux distros. I think it was Fedora that mentioned some special boot settings that are needed for the Vaio as well.

 

Hopefully someone has installed Debian or Linux on this system and will see this post as well.

 

For what it is worth, I saw that Mandrake has released beta 2 for their 10.2 vertsion with 915 chipset support. You may want to wait for the formal release of 10.2.

Share this post


Link to post

greetings debianUser

 

Unfortunately I only have Debian running on servers, but as it goes for X setup, Debian should be fairly similar to any other distro. Therefore: Open the X config file from "/etc/X11" (or the respective folder in case it's XOrg) and see what the installer placed there as graphics driver. If it's anything different than "vesa" you might want to give it a go and try the "vesa" driver instead. If this works it would at least enable X for you, even if the performance would be rotten. But even a slow X with internet access is a million times better than searching a driver solution in lynx on the console.

 

Ad "startx"/compilation error msgs: Getting to see the err. msgs. could be helpful as the regular "no screens found" can have around 12^34*6 reasons (misconfigured display, module missing etc.). Also a look at the make-output would reveal some possibly unmet dependancies.

 

good luck

 

(edited due to overwhelming nr. of typos smile

Share this post


Link to post

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×