LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   problem with starting x (https://www.linuxquestions.org/questions/slackware-14/problem-with-starting-x-399276/)

Paxmaster 01-03-2006 11:02 PM

problem with starting x
 
I have dell inspiron 2600, the video card is i830 I did a search on google and I found this link http://sauen.com/dell/inspiron/2600/ I believe that I have the same problem.

hear the my xorg.conf
----------------------------------------------------------
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the font modules
Load "type1"
Load "freetype"
#Load "speedo"
# This loads the GLX module
Load "glx"
EndSection
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/X11R6/lib/X11/rgb"

FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/"
EndSection
Section "ServerFlags"
EndSection
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
EndSection
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Device" "/dev/mouse"
EndSection
# Any number of monitor sections may be present
Section "Monitor"
Identifier "My Monitor"
HorizSync 31.5 - 50.0
VertRefresh 40-90
EndSection
# 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
Section "Screen"
Identifier "Screen 1"
Device "VESA Framebuffer"
Monitor "My Monitor"

# DefaultDepth 8
# DefaultDepth 16
DefaultDepth 24
# DefaultDepth 32

Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubsection

EndSection

Section "ServerLayout"

# The Identifier line must be present
Identifier "Simple Layout"

Screen "Screen 1"

InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection
----------------------------------------------------------
----------------------------------------------------------
hear my xorg-log in /var/log/ error message ( I did tail -20)

(II) VESA(0): Total Memory: 125 64KB banks (8000kB)
(EE) VESA(0): No matching modes
(II) UnloadModule: "vesa"
(II) UnloadModule: "ddc"
(II) Unloading /usr/X11R6/lib/modules/libddc.a
(II) UnloadModule: "int10"
(II) Unloading /usr/X11R6/lib/modules/linux/libint10.a
(II) UnloadModule: "vbe"
(II) Unloading /usr/X11R6/lib/modules/libvbe.a
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

Please consult the The X.Org Foundation support
at http://wiki.X.Org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
----------------------------------------------------------

I have also edit my lilo.conf to append="video=vga16:off"
and run lilo as root but no luck

anyway I have given much information as possible to solve this problem

please give some feedback thanks

BajaNick 01-03-2006 11:15 PM

If you have not, Try xorgconfig and then reboot and see if that solves the no screens found error.

rkrishna 01-04-2006 12:50 AM

no xorgsetup
 
i think it is better to try xorgsetup and it wil make an xorg.cong automatically,

Quote:

If you have not, Try xorgconfig and then reboot and see if that solves the no screens found error.
no need to reboot, ok u can restart the X, by force( Alt+Ctrl+Backspace)

till now u havent really specified teh problem,
r u using slack?????
by default slackware login to console only (default runlevel is 3) from there try startx, it will go to X (if u want cange it later but this is good)

xwmconfig will let u select the window managers

tell us what u c when u type startx

regards

Paxmaster 01-04-2006 01:04 PM

yeah I am using slackware 10.2, well I am not home I will try those command when I leave from work. for now it's runlevel 3 but soon I will change it to 5 Thanks

shilo 01-04-2006 02:11 PM

Any one of these will do. Try them all. Use the one that a) works, and b) you like best

X -configure
xorgcfg
xorgconfig
xorgsetup

***Bonus tip***

Here's a way to learn a lot. Consider trying this after you have everything working.

Try all four. Save the results separately (re-naming in a way that allows you to keep track). Study them. Read online, man pages, etc. Search the web for specs on your video card and monitor

When you understand the format of the X configuration file, use the four generated configs to help you create your own config. Don't forget to add plenty of comments (they are helpful if you need to re-configure later).

Mess around with that for a day and you will know a whole bunch about configuring X.

***Bonus tip 2***
Runlevel 5 not too useful in Slackware. :) (try 4, though.)

Woodsman 01-04-2006 03:56 PM

I spend a lot of time with my sleeves rolled up digging into Slackware. A person needs to be a DIY (Do It Yourself) type to endure Slackware's lack of user-friendliness and usability. I have learned a lot because Slack does not come packaged with a lot of overhead to get in my way, but that same minimalism has meant I spend far too much time surfing for answers for mostly straightforward usability issues.

There are a few areas where I believe the Slack maintainer easily could improve usability with only nominal effort. Of course, the problem is hardly entirely Slack's fault, but instead is a basic overall attitude within the old GNU/Linux circles of ignoring usability. Everything packaged with GNU/Linux is functional, but often one has to learn obtuse syntax and read reams of man pages, doc files, and how-tos to obtain that functionality. Usability is almost forgotten with a lot of this software. I do not wonder why many non-computer-literate people stick with Windows or Macs.

One area that I recommend people not waste their time in Slack is configuring X. All of the X configuration utilities packaged with X are sick jokes. If you have older hardware those utilities might help---and might not, but I've noticed that far too many people with newer hardware struggle to get X in Slack configured. This seems especially true for laptop owners.

Therefore, grab a Knoppix CD, boot, and copy the resulting xorg.conf file. This recommendation is unpopular with Slackware die-hards and fan-boys, but time is a scarce resource. Get X configured and then enjoy Slack. I use nothing but Slack, but I don't waste time trying to figure out the logic or non-logic of X.

I'm not at all declaring that people should forsake GNU/Linux or Slackware. I'm only stating that sometimes the journey is not as important as the solution. Sometimes getting from A to B is the critical issue, not the path of actually getting there. This is called usability.

Paxmaster 01-05-2006 11:38 AM

well I reconfigure my xorg but it didn't work, I also try two live cd such as knoppix and ubuntu live cd it did't work same error comes up

dgeenens 01-05-2006 12:37 PM

try to look up the vertical sync and horizontal sync range for your monitor. I have a dell e773c and needed to manually input a horizontal sync from 30-70 and a vertical sync from 50-160 to get my X going.

mdarby 01-05-2006 12:42 PM

Quote:

Originally Posted by Woodsman
I spend a lot of time with my sleeves rolled up digging into Slackware. A person needs to be a DIY (Do It Yourself) type to endure Slackware's lack of user-friendliness and usability. I have learned a lot because Slack does not come packaged with a lot of overhead to get in my way, but that same minimalism has meant I spend far too much time surfing for answers for mostly straightforward usability issues.

There are a few areas where I believe the Slack maintainer easily could improve usability with only nominal effort. Of course, the problem is hardly entirely Slack's fault, but instead is a basic overall attitude within the old GNU/Linux circles of ignoring usability. Everything packaged with GNU/Linux is functional, but often one has to learn obtuse syntax and read reams of man pages, doc files, and how-tos to obtain that functionality. Usability is almost forgotten with a lot of this software. I do not wonder why many non-computer-literate people stick with Windows or Macs.

One area that I recommend people not waste their time in Slack is configuring X. All of the X configuration utilities packaged with X are sick jokes. If you have older hardware those utilities might help---and might not, but I've noticed that far too many people with newer hardware struggle to get X in Slack configured. This seems especially true for laptop owners.

Therefore, grab a Knoppix CD, boot, and copy the resulting xorg.conf file. This recommendation is unpopular with Slackware die-hards and fan-boys, but time is a scarce resource. Get X configured and then enjoy Slack. I use nothing but Slack, but I don't waste time trying to figure out the logic or non-logic of X.

I'm not at all declaring that people should forsake GNU/Linux or Slackware. I'm only stating that sometimes the journey is not as important as the solution. Sometimes getting from A to B is the critical issue, not the path of actually getting there. This is called usability.

'Usability' to one person is limiting to others. Installing/Configuring/Running X in Slackware/Linux is really rather easy. Answer a few questions (xorgconfig), select your preferred DE (xwmconfig) and you're off (startx).

I don't see a reason why X on a laptop would be different on a desktop. I've run both for years on rather different hardware without a problem. I've had it running under both NVidia and ATI cards effortlessly...

lestoil 01-05-2006 03:34 PM

Have u tried i810 driver instead of vesa driver. Chkout cfwilson post on i830 and dri lower down in this forum. Putting correct HZ and V refresh rate should help too. Check back of monitor or monitor manual for numbers.
Have u tried ubuntu setting(if they work) for SW?
Keep /etc/inittab default at 3 until u get good desktop then change default to 4 to boot into desktop.

rkrishna 01-06-2006 04:20 AM

may b problem with graphix driver,
 
hi Paxmaster
u r not able login to X, :(
since knoppix and ubundu is not working it is the problem with driver u have to compile it into the kernel

which board u r using ?
is it a intel graphix or nvidia etc..
(on board? )do an lspci and check
root@darkstar#lspci (post the result)
...download the driver

hi lestoil
how do u know the modules are loaded for ur driver...
so not manually edit the xorg.conf like simpl;y changing vesa to some other like ( i810 driver) make modules of that for specific kernel and load it into kernel and then it will work

happy to c shilo here hai
woodsman with a detailed note hai
hi Paxmaster
r u still in the black screen on the darkstar login
Paxmaster@darkstar$ or root@darkstar#
so u r on default runlevel tht is 3
dont reinstall, u can do everything except the X apli..

u can edit inittab to change ot to 4, after u have done ur x configured
use shilo's guide

Quote:

I also try two live cd such as knoppix and ubuntu live cd it did't work same error comes up
then simply try slax not much help eventhen...


All times are GMT -5. The time now is 02:03 PM.