Soyo Motherboard SY-KT600 Dragon slays Mandrake?
 

Hey Guys,

I swapped out my Albatron-Motherboard for this Soyo SY-KT600 Plus V2.0 and kept all my same hardware and just transfered them back on this Soyo board. My big fear was with Windows not accepting the chip set of the new board. To my surprise, Windows has accepted the transfer of hard-drives with Windows XP, but Mandrake Linux did not.

I have attempted to reinstall Mandrake 10.1 Official 4 different times and it appears my graphic card is not allowing the Nvidia splash screen to boot up to my desktop. Just right before it gets to that point, my monitor turns grayish black. I have done a complete new install.

I have attempted to boot into failsafe and all the modules are installed, but it just boots to a grayish black screen with no prompts.

Any idea what might be going on here? This exact same card worked before with Mandrake 10.0, but it was on the Albatron motherboard.

I am stuck and don't know what else to do.

d-1

A black grey screen normally indicates that the system is FINE but the video resolution and clock timings exceed your monitor's capabilities.

When you get to the grey screen hit [CTRL][ALT][F1] to get to a console.

Log in as root and type in

service dm stop

now run XFDrake and TEST each configuration or setting, particularly the monitor.

Choose a slightly inferior monitor if needed to have the timings adjusted properly for yours, as often X chooses the absolute limits of your monitors capabilities.

Run each test but once started do not hit any yes on the keyboard.

If the monitor goes black wait 12 seconds for the text screen to return.

Once you do see the rainbow test screen immediately click OK to accept the new settings.

Save and exit.

Now type

service dm start

and away you go.

( post #14)


I have tried different combinations in test mode and I have not been successful. When I run a Test I get this error message:





Anytime I try to change the resolution of monitor, lets say to 1024X768 8bbps or 24 the screen goes gray again and nothing happens, even if I hit the CTRL+Alt-F1 keys.

Any other suggestions?

I have a Samtron 76DF monitor
and a Best Data MX 440 video card with maxium 3D/2D resolution of 2048X1536 @75 HZ witn Nvidia Gforce2.

d-1

When I say "gray" I mean a charcol black color. Not deep black like the color of Konsole or DOS screen.

Every test I try I still get that (EE) Problem parsing the config file.

???

d-1

Opjose,

I found this post and was wondering if this might help me solve my problem?


Re: error trying to run lg3d-session

Posted: Oct 24, 2004 11:42 PM



Reply




On Sun, Oct 24, 2004 at 11:30:19PM -0400, lg3d-interest@javadesktop.org wrote:
> my xf86Config-4 configuration file is:
I think I see.
Since the release of 0.5.1 lg3d makes use of the xorg server, not the
xfree86 x server. With this the config file has changed, it is
xorg.conf, not XF86Config-4. In terms of the configuration parameters,
they should all be the same as in the XF86Config-4 file, except that the
'keyboard' driver is no longer available and should be replaced with the
'kbd' driver, as ddew suggested.

So if you copy you /etc/X11/XF85Config-4 to /etc/X11/xorg.conf and
change the keyboard config to:
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "en_US"
Option "XkbOptions" ""
EndSection

You should be able to run the lg3d-session.

Hope that helps,

Kirk

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@lg3d.dev.java.net
For additional commands, e-mail: interest-help@lg3d.dev.java.net







masdc


Posts: 8
From: Colombia
Registered: Oct 24, 2004


Re: error trying to run lg3d-session

Posted: Oct 25, 2004 1:01 PM



Reply




Hi Kirk:

yes, that was the error. I copy the file to xorg.conf and changed the Keyboard driver and it worked. Thank you so much.

Thanks also to David.

Bye,

OPjose,

When I type startx in login screen area I get the following error - that /etc/X11/xorg.conf is incomplete, it says at least one Device section is required. Atleast one device section is required. EE Problem parsing the config file, EE Error parsing the config file. Fatal server eror: no screens found, Please consult the X.Org Foundation support at http://wiki.Org for help also check the log file at "/var/log/Xorg.0.log" for additonal information. X10: fatal error 104 (Connection reset by peer) on xserver "0.0" after 0 requests (0 unknown processed) with 0 events remaining.

d-1

Are you running onboard sound on your soyo board?

Hmmm...

XFDrake should rebuild the file for you automatically whenever you select a new or different video card.

Also you should be able to delete the file and then run XFDrake which is supposed to rebuild it as needed.

You can always test the configuration(s) by typing X at the prompt, after shutting down the X display manager with

service dm stop

It sounds like the XFDrake command may not be correctly building the configuration file.

Here is where I stand today. I installed "Thiz-Linux" 7.0 and it installed perfectly. Now Thiz-Linux does not have the NVIDA driver modules. The kernel version is 2.4.18-12Thiz and may explain why. So I can boot into Windows and Thiz, but not Mandrake.

d-1

Mandrake also provides the correct modules and drivers, but unfortunately only on the "official" release disks and powerpacks.

This makes the community edition somewhat difficult for a first time user... sigh.

http://www.linuxquestions.org/questi...hreadid=248323 This may help.

Thanks for your message. Just to set the record straight, I have Mandrake 10.1 Official DVD. I read that thread and it appears he never solved his problem with his sound. I am trying to locate and different motherboard and see if that works....

Any suggestions on any other boards that may be compatable?

I called Soyo and they had not clue and to what is going on.

d-1

Under the Intel realm I haven't had any problem with motherboards based upon the following chipsets.

Intel 815
Intel 845
Intel 850
Intel 865
Intel 875

All hardware seem to be supported, even using the (lame) on board video and sound when purchased that way.

Also remember that the HCL (Upper right side of this page) also lists user success with different motherboards.

Remember though that often the people who post the HCL reviews are not looking to far past getting Linux up and running.

E.G. they are not posting the hardware list to determine if ALL mainboard components are recognized (which they should).

With the above chipsets and the later kernels, I see no unsupported devices appearing.

Do you then recommend running Intel over AMD? Also do you know what type of motherboard you have?

d-1

I'm not particularly recommending one over the other, just relaying my experiences.

I often deploy Linux systems as boundry servers and for other tasks.

I tend to stick with the more conservative Intel approach as these things end up running 24/7 w/o any user intervention whatsoever. To make my life easier I need these things running flawlessly. Usually they are only noticed when someone stupidly disconnects the machine(s).

I've used just about every Intel manufactured motherboard which use the listed chipsets w/o any problems and with seemingly full support by the kernel, especially the later ones.

That said, I've also have had sucess with non-intel boards (which I usually do not use for servers) set up as workstations, that employ the same Intel chipsets.

Go to the Intel Products page and select any Workstation and Server board based upon everything from the 440bx up thru the 875 series, and I've used them with Linux w/o problems. Even those server boards with dual 10/100baseT and Gigabit Ethernet interfaces built in work fine.

I have not yet tried the 9xx series with the newest prescotts.... so I don't know how the PCIe units will behave.