Try putting "nv" as your driver instead of "vesa". Where's the rest of the file?

I can't get the rest of the file

You see, I have a Serial ATA drive with win XP on it
and I want to switch to linux

I know the 2.4.20 kernel doesn't "see" sata drives so I found an old 4.2 gb IDE harddisk and installed Slackware 9.0 there
so I dont know how to copy the xf86config file to paste here (on windows xp)

to boot in linux I change the sequence from the BIOS, and Lilo thinks that theres only Linux installed on the machine because it can't see my win XP as a "hdx" drive

what's the difference between vesa, vga and nv?
why whould the monitor close?

OK

so I changed vesa to nv

what happens now is that the screen is always on like it's working, but IT'S BLACK and this time even if I CTRL-ALT-BACKSPACE I still can't see anything?

Question :

Can I look into the xf86config of Knoppix when it's working so I can see how Knoppix works on my system?
If so how?

Thanks a lot! You guys are being a great support!

the panther

nv is the generic nvidia driver. The monitor problem closed because X is configured wrong (wrong refresh rate, etc.), so it closes itself so it won't break. Try putting the refresh rate and resolution you use in Windows, example (for 1024x768@60hz):

Subsection "Display"
Depth 24
Modes "1024x768/60hz" "800x600" "640x480"
EndSubsection
EndSection

This assumes that your default depth is 24. It is specified in this section:

Section "Screen"
Identifier "screen1"
Device "device1"
Monitor "monitor1"
DefaultColorDepth 24

here is my xf86 config for comparison. I have a gforce4 mx460.
I did notice that you used "my card" in this section; make sure it ties up with the rest of the file (screen section for instance). It would probably be best to change it back to what it was before you changed it (if you can remember!)

anyway, here goes:

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

Identifier "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync 27-115

# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 50-160


ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
ModeLine "1600x1200" 220 1600 1616 1808 2080 1200 1204 1207 1244 +HSync +VSync
ModeLine "1280x1024" 181.75 1280 1312 1440 1696 1024 1031 1046 1072 -HSync -VSync
ModeLine "1152x864" 135 1152 1464 1592 1776 864 864 876 908
ModeLine "1024x768" 115.5 1024 1056 1248 1440 768 771 781 802 -HSync -VSync
ModeLine "800x600" 69.65 800 864 928 1088 600 604 610 640 -HSync -VSync
ModeLine "640x480" 45.8 640 672 768 864 480 488 494 530 -HSync -VSync

Option "DPMS"

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

Section "Device"
Identifier "0x017"
Driver "nvidia"
VideoRam 65536
Option "NoLogo" "True"
# Insert Clocks lines here if appropriate
EndSection

# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "0x017"
Monitor "My Monitor"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

# DefaultDepth 8
# DefaultDepth 16
DefaultDepth 24
# DefaultDepth 32

# "1024x768" is also a conservative usable default resolution. If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)

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

EndSection

note: I couldn't fit all of it on! but this is the most useful bit.... DON'T use "nvidia" as the driver until you install the nvidia drivr from nvidia.com!

Great!

I'm going to try that right this moment

Start --> Turn Off Computer --> Restart

YEEEEEEEEEEESSSSSSSSSSSSSSS


I have succesfully launched KDE 3.1
how, you ask?

Because of aaa and LinFreak!

Man guys you can't believe how helpful you guys were!

Now I have 1 last question which I'm certain it is because of xf86config

I have a Microsoft (dont ask why ) IntelliMouse Optical
It's a USB mouse and I can't controll it when KDE opens??

that probably has a configuration in xf86config too?

Thanks A LOT!

here's my mouse section:

# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"

# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:

# Option "Protocol" "Auto"

# The available mouse protocols types that you can set below are:
# Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
# Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
# MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
# ThinkingMouse ThinkingMousePS/2 Xqueue
Option "Protocol" "IMPS/2"
Option "Buttons" "5"
Option "ZAxis Mapping" "4 5"

# The mouse device. The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.

Option "Device" "/dev/mouse"
# Option "Device" "/dev/psaux"
# Option "Device" "/dev/ttyS0"
# Option "Device" "/dev/ttyS1"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

# Option "Protocol" "Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

# Option "BaudRate" "9600"
# Option "SampleRate" "150"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"

# ChordMiddle is an option for some 3-button Logitech mice

# Option "ChordMiddle"

EndSection

note: i am using s ps/2 mouse which uses intellimouse preferences hence:

Opion "protocol" "IMPS/2" ("IM" stands for intellimouse i think)

not too sure what you should use but i suggest using a usb-ps2 adapter (usually supplied with an intellimouse) and use the ps2 port on your computer, thats what it's for!

the next two options setup the mouse wheel:

Option "Buttons" "5"
Option "ZAxis Mapping" "4 5"

What mouse protocol is being used in XF86Config? It is listed in Section "InputDevice". Try posting the whole section.

But the thing is that I selected USB CONNECTED MOUSE in the setup of Slackware 9.0

and besides the mouse works perofectly in MC , etc...


BTW, aaa, I still dont know how to post my xf86config?

It isnt possible to copy from linux, then restart, and paste in windows, is it?????

I think I'm going to try to get it working in USB so that there wont be any conflicts with the SETUP PART of Slackware 9.0

ok leave it as is!


try copying the file into your windows partition as a .txt file

aaa: if you look closer you will see the entries are "input device"! look for the lines i mentioned in my last post

mc uses gpm for its mouse. Check out the /etc/rc.d/rc.gpm file to see what protocol gpm uses, then use it for X.
To post your XF86Config, copy it to a FAT32 partition. That way, both XP and linux can read it.

LinFreak,
What do you mean?

the panther,
I don't know about XP's Notepad, but in win9x Notepad jumbles Linux text. Try using Wordpad (if you have it) or Word instead.

GUYS

I'M POSTING THIS MESSAGE FROM SLACKWARE 9.0

TA DAAAAAAAAa

I got the mouse working by using LinFreak!'s settings

Now I have my Linux to Play with, learn with, and hopefully in a very short time, I'll be helping people as well

THANK YOU GUYS SO MUCH!!!

the panther has left the building

aaa:

Qutoe:

note: i am using s ps/2 mouse which uses intellimouse preferences hence:

Opion "protocol" "IMPS/2" ("IM" stands for intellimouse i think)

not too sure what you should use but i suggest using a usb-ps2 adapter (usually supplied with an intellimouse) and use the ps2 port on your computer, thats what it's for!

the next two options setup the mouse wheel:

Option "Buttons" "5"
Option "ZAxis Mapping" "4 5"