Cheap Linux Hardware - 3ware raid card installation takes away suse's ability to load x windows

Author

3ware raid card installation takes away suse's ability to load x windows

AsdfQwerty

2006-07-12, 7:17 am

Hello,

I comfortably installed Suse 10.1 on Intel S5000VSA motherboard with
the onboard ATI
ES1000 video chip.
http://www.intel.com/design/servers...00VSA/index.htm

I used an Intel Xeon dual-core processor, a Kingston memory module and
a SATA Drive.
All worked well until it was time to add a 3ware raid card
(9590SE-12ML) to a PCI-e slot.
http://www.3ware.com/products/serial_ata2-9590.asp

With the 3ware card in the slot, Suse cannot load XWIndows and reverts
to CLI-only mode.
If I take the card out and reboot, XWindows loads comfortably again.

Would anyone have any thoughts on this problem?
Any alternative video cards I could use instead of the onboard video?

Thanks in advance for your input!

A Qwerty

Henrik Carlqvist

2006-07-12, 7:17 am

"AsdfQwerty" <ashwini_ranganathan@yahoo.com> wrote:
> With the 3ware card in the slot, Suse cannot load XWIndows and reverts
> to CLI-only mode.
> If I take the card out and reboot, XWindows loads comfortably again.
>
> Would anyone have any thoughts on this problem?

I would try the following:

First without the 3ware card:

cat /proc/pci > /tmp/no3ware.txt

Then with the 3ware card installed:

cat /proc/pci > /tmp/with3ware.txt

After that I would compare those files:

diff /tmp/no3ware.txt /tmp/with3ware.txt

The above assumes that /tmp keeps its contents after a reboot. If your tmp
is mounted as tmpfs or if SuSE as some startup scripts cleaning tmp you
might want to place the files somewhere else.

Most likely you also have a log file from X. It might be called something
like /var/log/Xorg.0.log, but I'm not familiar with SuSE so the log file
might be called something else or placed somewhere else on your system.
Save that file for comparision also:

cp /var/log/Xorg.0.log /tmp/Xno3ware.txt

and

cp /var/log/Xorg.0.log /tmp/Xwith3ware.txt

Those files might also be interesting to compare.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc8(at)uthyres.com Examples of addresses which go to spammers:
root@variousus.net root@localhost

chuckcar

2006-07-12, 7:14 pm

"AsdfQwerty" <ashwini_ranganathan@yahoo.com> wrote in
news:1152685273.189419.131170@p79g2000cwp.googlegroups.com:

> Hello,
>
> I comfortably installed Suse 10.1 on Intel S5000VSA motherboard with
> the onboard ATI
> ES1000 video chip.
> http://www.intel.com/design/servers...00VSA/index.htm
>
> I used an Intel Xeon dual-core processor, a Kingston memory module and
> a SATA Drive.
> All worked well until it was time to add a 3ware raid card
> (9590SE-12ML) to a PCI-e slot.
> http://www.3ware.com/products/serial_ata2-9590.asp
>
> With the 3ware card in the slot, Suse cannot load XWIndows and reverts
> to CLI-only mode.
> If I take the card out and reboot, XWindows loads comfortably again.
>
> Would anyone have any thoughts on this problem?
> Any alternative video cards I could use instead of the onboard video?
>
> Thanks in advance for your input!
>
> A Qwerty
>

I have a machine with an onboard video chip running X (yes,
successfully) with a plug-in video card as well. You need to have
different Device sections in your XF86Config file for *each* video card
even if you don't plug a monitor into it. You have one Screen section
for each video card being "used" - i.e. plugged into a monitor. If you
have a version of X newer than 4.1 it gets wierd - that is Xfree 86
version 4.2 onwards. Here there is the ServerLayout section required and
as far as I can tell it just confuses things - not even the source for
4.4 explains how to use it correctly in this case. If the server won't
start with this much information, reply saying so, and I'll paste the
relevant parts of my XF86Config file that I created manually (for
version 4.4 which I compiled).

For more information on this there's always:

man XF86Config

--
(setq (chuck nil) car(chuck) )