LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Slack 8.1--X gives fatal IO and Virtual height (http://www.linuxquestions.org/questions/slackware-14/slack-8-1-x-gives-fatal-io-and-virtual-height-33055/)

Texicle 10-17-2002 02:29 PM

Slack 8.1--X gives fatal IO and Virtual height
 
Hello,

After having worse problems than the one I have now, and being unable to fix it, I decided I'd just reinstall Slackware. I first deleted all the partitions, repartitioned, formatted the new partitions, then reinstalled.

Right after I installed, I thought I'd try to startx. XFCE started up just fine (the resolution sucked, but it was viewable), but then I moved my mouse. I moved it about 1/4 inch, and the mouse pointer got lodged in the upper right corner of the screen.

CTRL+ALT+Backspace

Back to bash prompt. I go to XF86Config, and find that my mouse is set to P/S 2, so I change the protocol to "Microsoft" as it is a generic 2 button serial mouse (I had this same problem the first few times I installed any Linux distro and this fixes the mouse problem). I startx and the mouse works perfectly. However, my resolution isn't as sharp as I would like.

After having reviewed and researched my video card (Trident TGUI9660 with TGUI9680 chipset with 1024 Video RAM) I found that it is compatible with Linux, and that it should be able to handle 1024x768 (even if at 8 bit). The 800x600 is just too huge for me. I researched my monitor (Hyundai DeluxScan 15G+) and found the correct horizontal and vertical syncs/refresh rates. After doing xf86cfg, I found the "clocks" rates as well for the Trident card.

I go to edit XF86Config and this is what I have (I took out all the excess comments provided by the file):
-------------------------------------------------------------
Section "Device"

Identifier "tgui9660"
Driver "trident"
VideoRam 1024
#Insert Clocks lines here if appropriate

End Section
Section "Screen"

Identifier "Screen1"
Device "tgui9660"
Monitor "My Monitor"

# Default Depth 8
# Default Depth 16
# Default Depth 24
# Default Depth 32

SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"

Depth 16
Modes "1024x768" "800x600" "640x480"

Depth 24
Modes "1024x768" "800x600" "640x480"

Depth 32
Modes "1024x768" "800x600" "640x480"
End SubSection
End Section
-----------------------------------------------------------

The reason I didn't change "My Monitor" yet, is that it created huge problems for me last time (causing me to eventually reinstall). Now, notice there is no "View Port 0 0" or anything remotely related to Virtual Screen/desktop. This does not appear on my XF86Config file until I run xf86config. After I ran this last time, and selected no for virtual desktop I ran into major problems. Someone once advised me to comment out glx so right now it is at:

# Load "glx"

Everything else, other than what I posted above, is still set to default.

With the XF86Config file as is, I went to startx and got the following:

(EE) TRIDENT (0): Virtual height (0) is too small for the hardware (min 128)
(EE) Screen(s) found, but none have a usable configuration

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.

I have done various searches through the General Linux Questions, Window/Desktop Managers, and Technical Support forums only to find that this particular string of events has not been reported here before (most are nVidia drivers needing to be downloaded). I have seen some with the same XIO error and the no screens found errors, but none with the virtual height error. Additionally, the resolution to most of the other people's problems has been to run xf86config or XFree86 -configure or...

Last time I ran xf86config, I ended up having more problems than when I started. For some reason, X seems to prefer the VESA framebuffer defaults and all the other default generic video settings. I had no problems when I was running Mandrake 8.1, so I know the video card works well and according to xfree86.org, it is compatible and supported.

Oh yeah, if anyone has a copy of their XF86Config file where:

# Insert Clocks lines here if appropriate

is actually filled in correctly, could you please post it for me? I've got all the information, but I don't know the correct format I should use. Thank you kindly.

Thanks to those who took the time to read all this. Any suggestions are appreciated.

LNXman 10-17-2002 03:13 PM

You don't seem to have your monitor defined in your XF86Config File.

You should have a section like:
------------------------------->8---------------------------
Section "Monitor"
Identifier "Hyundai DeluxScan 15G+"
HorizSync <your_monitors_horizontal_range>
VertRefresh <your_monitors_vertical_range>

# The following is a Modeline example, If you decide to uncomment the second line after this comment, I am not guaranteeing it will work perfectly.
# 1024x1024-61Hz,64.2kHz (uncomment below, not this one)
#Modeline "1280x1024" 110 1280 1328 1512 1712 1024 1025 1028 1054
End Section
---------------------------------->8---------------------------

The above Section is usually defined after the InputDevice Section.

AND. . .

Make sure you change the Monitor definition in your Screen Section from Monitor "My Monitor" to Monitor "Hyundai DeluxScan 15G+", if you decide to use the example above. . . And input the approprite Vertical and Horizontal ranges of your monitor as well.

Hope this helps,

GL

P.S. Are those all the settings in your XF86Config file? Or you also took out some Sections from it along with the commented stuff? Just curious, because I do not see a Modules Section, a Files Section, an InputDevice Section, etc. . .

WRT your clock timings, XFree86 -configure should be able to detect them and write them for you. . .

You can also try XFree86 -probeonly to check out what XFree86 Finds about your card before making changes. . .

/edit: Added P.S.
/edit: fixed Monitor Section example

Texicle 10-17-2002 04:54 PM

Thanks for quick response!

You're right, I did leave out much of the XF86Config file. Reason is, I had to copy all that by hand, then type it into my pc at work. At home, my wife's Winbox is the only one connected to the internet (still can't get pppsetup to work--but that's another animal:D). Anyway, I didn't include several sections, as they were all set to default or were not causing any problems. The reason I didn't set my monitor section correctly is that last time I did, I had CRAZY problems with X which basically caused me to reinstall after 2 weeks of trying to fix it with xf86config. I had the correct monitor, horiz/vert rates, etc. My system got hosed pretty good (X couldn't find several files, etc).

I've got my clock timings, but the "modelines" I've never seen in an XF86Config. I'll have to research that a bit more as I'm confused by them right now.

Oh, just to give some background, I know that my video card is good and compatible as it worked fine when I had Mandrake 8.1. I decided to go with Slackware so I could get my hands dirty (which I am) and so far I'm enjoying it, problems and all.

I'm going to try the two command that you gave me as well since I haven't tried them yet. xf86cfg seemed to freeze up too. But, I probably just didn't give it time to run. The screen went blank for about 3 minutes (but then again, I'm on a Pentium 120Mhz, 80MB RAM system). I ended up stupidly hitting reset. I checked the XFree86.8.log file and found lots of info that it was getting, but then errors showed up as well (I'm attributing this to my hasty reset).

Thanks again for the suggestions. I really appreciate your help. I'll try this tonight when I get home from work and keep you posted. :)

LNXman 10-17-2002 08:32 PM

K

One thing I forgot to mention is to make sure you run the XFree86 command as root. But I am sure you already knew that. BTW, the command resides under /usr/X11/bin. Just in case you need to find it.

GL

Texicle 10-17-2002 09:42 PM

Cool, thanks. I knew about the root part (after the reinstall I haven't even created a new user yet anyway). I did not, however, know where command resided. I'll give it a shot tonight.

Texicle 10-18-2002 01:15 AM

There is no directory /usr/X11/bin. I've got /usr/X11R6/bin.

I tried running both commands. XFree86 -probeonly provided the same errors as above with the (EE) TRIDENT... and XFree86 -configure told me to run the /root/XF86Config.new which I did--blank screen.

I'm going to run xf86config and enter in all the information about my monitor and graphics card, etc. Hopefully it works. If not, I'm guess I'm going to have to just live with all the defaults. I have no idea why this is happening.:confused:

LNXman 10-18-2002 01:45 AM

I did a search with your particular problem, and what I found out was that some users where missing setup information wrt their monitor, or had the wrong refresh rates for it.

Out of curiosity, when you run the XF86Config.new file, what does the /var/log/XFree86.0.log file say? Does it give you the same error, or does it show something different happens?

Could you also show me your Monitor Section? I am curious about the info you are writing there as well.

L8

Texicle 10-18-2002 02:07 AM

Okay, I ran xf86config, entered everything as it's supposed to be, and then checked XF86Config. I'm going to post everything (except comments) so you can see what I have. I ran startx and the screen went completely blank (again--it always does this after I run xf86config and provide all the right stuff). I tried to toggle resolutions (CTRL+ALT+"-" and CTRL+ALT+"+" as well as CTRL+ALT+Backspace to get out), but I was forced to CTRL+ALT+DEL to reboot. I checked /var/log/XFree86.0.log and there were no (EE)'s in there, but there was one (WW) which is:

(WW) System lacks support for changing MTRRs

Also, for every single resolution, I got:

(II) TRIDENT(0): Not using default mode "****x****" (insufficient memory for mode)

where **** equals ANY resolution.

Additionally, I just checked and found out I'm running XFree86 version 4.2.0. Is this too high of a version for my system (Pentium 120Mhz, 80MB RAM, 4.3GB drive, Trident TGUI9660 video card 1024 RAM)? I think I might need an earlier version. BTW, I am NOT dual booting, this is a strictly Slack box. :D

LNXman 10-18-2002 02:33 AM

K

At least you are getting a different error this time, which is sort of good.
My believe is that the XFree86 server has problems loading a resolution. What happens (at least if you have not specifically stated a Modeline) is it cycles through a bunch of built in default resolutions, and fails at every single one for whatever reason. In your case I think It may be a memory issue, but then again, you say it worked with Mandrake 8.1. Which is kind of odd.

Maybe you just need to indicate your total memory in your config file. . .or,

Maybe, the driver included with Slackware may not be the latest for your trident chip. Check this URL for the latest trident driver so you can give it a shot.

I will be checking for you config file later tonight, or tomorrow.

L8

/edit: fixed statement

Texicle 10-18-2002 02:40 AM

Sorry it took so long to reply.

Here's my XF86Config file (Reader's Digest version because I'm typing it all out using a monitor switchbox to back and forth between my wife's Winbox and my Slackbox:eek:):
**************************
Section "Module"

#This loads the "DBE" extension module

load "dbe" #double buffer extension

#comments snipped
SubSection "extmod"
Option "omit xfree86-dga"
End SubSection

#snip
Load "type1"
Load "freetype"

#snip
End Section

Section "Files"
#snip
RgbPath "/usr/X11R6/lib/X11/rgb"

#snip
FontPath "usr/X11R6/lib/X11/local/"
FontPath "usr/X11R6/lib/X11/misc/"
FontPath "usr/X11R6/lib/X11/75dpi/:unscaled"
# FontPath "usr/X11R6/lib/X11/100dpi/:unscaled"
FontPath "usr/X11R6/lib/X11/Type1/"
FontPath "usr/X11R6/lib/X11/Speedo/"
FontPath "usr/X11R6/lib/X11/75dpi/"
# FontPath "usr/X11R6/lib/X11/100dpi/"

#snip
End Section

Section "Server Flags"
#snip--everything is commented out
End Section
********Input Device Section******
Section "InputDevice"
Identifier "Keyboard1"
Driver "Keyboard"
#snip
Option "AutoRepeat" "500 30"
#snip
Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"
EndSection

*******Core Pointers InputDevice Section******
Section "InputDevice"
#Identifer and driver
Identifer "Mouse1"
Driver "mouse"
Option "Protocol" "Microsoft"
Option "Device" "/dev/mouse"
#snip
EndSection

#snip
******Monitor Section*******

Section "Monitor"
Identifier "Hyndia DeluxScan 15G+"
#snip
HorizSync 30-70
#snip
VertRefresh 50-150
EndSection

******Graphics device section*******
#Standard VGA Device:

Section "Device"
Identifier "Standard VGA"
Vendor "Unknown"
BoardName "Unknown"
#snip
Driver "vga"
#snip
EndSection

#Device configured by xf86config:
Section "Device"
Identifier "Trident TGUI9660"
Driver "trident"
#VideoRam 1024
#Insert Clocks lines here if appropriate
EndSection
********Screen sections******
Section "Screen"
Identifier "Screen 1"
Device "Trident TGUI9660"
Monitor "Hyundai DeluxScan 15G+"
DefaultDepth 8

Subsection "Display"
Depth 8
Modes "1024x768" "800X600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800X600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800X600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
*********Server Layout section********
Section "ServerLayout"
Identifier "Simple Layout"
#snip
Screen "Screen 1"
#snip
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
**************

And that is it.

Texicle 10-18-2002 02:47 AM

Quote:

Originally posted by LNXman
<snip>

Maybe, the driver included with Slackware may not be the latest for your trident chip. Check this URL for the latest trident driver so you can give it a shot.

I will be checking for you config file later tonight, or tomorrow.

L8

/edit: fixed statement

I checked that page a while back (the TGUI9660 driver will not work with the TGUI9660 card, you HAVE to use the TGUI9680 driver, which for some reason works--according to Trident and many other sites I've searched). When I set it up with the TGUI9680 driver, it worked in Mandrake 8.1. Now, xf86cfg detected my card as TGUI9660 with a TGUI9680 chipset. If I select TGUI9660 in xf86config, I get a blank screen when trying to startx. Same thing happens if I try to select TGUI9680 in xf86config. It's really weird. With Mandrake 8.1 setup, I had the choice of installing 4.x.x version or 3.x.x (can't remember them exactly). I went with 3.x.x. With Slack install, there were no options. If it is the version that's killing me, how would I go about getting rid of 4.2.0 and going with a 3.x.x?

BTW, I really appreciate all your help and support you've given me. I hope I can return the favor someday. Thanks.

LNXman 10-18-2002 03:18 AM

HMMM, your config file seems to be fine. I see nothing out of the ordinary.

Things you can try in the mean time:

1.
..........a) Uncomment the #VideoRam 1024 argument line
..........b) Run startx again
..........NOTE: If you want to force a particular depth when running startx
........................then you can run it like this startx -- -bbp <depth>.
..........c) If it fails, continue, else you are done. 8^)

2.
...........a) Instead of using the trident driver as you are doing. Maybe you could
................use the generic VGA driver instead, or the generic VESA driver.
................So, first comment the line Driver "trident" out with the #.
...........b) Below it type Driver "vga"
...........c) Save the file
...........d) run startx again
...........e) If it fails, continue, else you are done. 8^)

3.
...........a) Follow directions from step 2a from above, but comment the line
.................Driver "vga" out this time.
...........b) Below it type Driver "fbdev"
...........c) Save the file
...........d) run startx again
...........e) if it fails, then "CRAP!!!!!!!, a;sldkjf;alsjdie;j" . . . . . . 8^( , and continue

4.
............a) Post errors or warning found in the log file while running the vga driver
.................and the frame buffer driver.

Then we can go from there. . . again. . .

BTW, can you try to use FTP between your wife's box and your box? Don't waste your life away with unecessary typing when you don't have to . . . ;^)

GL

/edit: fixed typo

LNXman 10-18-2002 12:58 PM

I just realized one thing this morning while checking your XF86Config file. In your config file, you are not forcing a specific chipset for XFree86 to use. Therefore I believe that when the XFree86 Server loads your config, and attempts to detect your video, for whatever reason keeps loading the 9660 chipset instead of the 9680 that you want. It is an assumptions since I do not have your logs. . .

Also, what backs that assumption up is the fact you have mentioned xf86config detects your card as a 9660, which mostlikely the XFree86 server does as well whey you try to run it . . .

SO . . .

What you can do to force the XFree86 Server to use the 9680 chipset instead (So at least you can feel sure it is using the right chipset when you start XFree86), you can add the Chipset <chipset_type> option to your config file, like:

------------------------------->8-------------------------------
Section "Device"
Identifier "Trident TGUI9660"
Driver "trident"
Chipset "tgui9680"
VideoRam 1024
#Insert Clocks lines here if appropriate
EndSection
--------------------------------->8-----------------------------

Then, give it a go again with startx, and see what happens.


GL

Texicle 10-18-2002 04:03 PM

Thanks. I think I'll try the second suggestion first, with the chipset force. If that doesn't work, I'll try with the steps 1-4 that you provided. I'll give it a try later tonight.

Quote:

BTW, can you try to use FTP between your wife's box and your box? Don't waste your life away with unecessary typing when you don't have to . . . ;^)
I would, but both boxes are using 33.6 modems. I have no idea how to network them yet. As for FTP, (don't laugh) I never FTP'd anything in my life.

I'm on a switchbox right now with cables going all over the place. My desk looks like something Dr. Frankenstein would have used had computers been around back then. :p

Texicle 10-20-2002 11:42 PM

Okay, here's what happened when I entered the chipset info. The screen went blank for a few seconds, but then a portion of the XFree86.0.log came up with the following:

<comments>
(EE) TRIDENT(0): No support for "tgui9680"
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
<comments about reporting problems>

XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.

Then the bash prompt comes up. I've seen this error before, but have know clue as to what it means. I'll post the results of your other suggestions in a few minutes. :)


All times are GMT -5. The time now is 01:32 AM.