Another attempt: no sync of Promise RAID controller

"Jurzitza, Dieter" <[email protected]>
Newsgroups gmane.linux.suse.sparc
Message-ID <[email protected]>
Dear Listmembers,
to circumvent my problem with that promise device not reporting sync I tried
to install a 29160 adaptec controller. However, booting from the original
iso-image I was not able to load a module called aic7xxx.
Moreover, I have some questions (SuSE Sparc 7.3):
1.) I haven't found any obvious differences between saying "manual" or
"yast2" at the boot prompt. Both end up in a graphic yast2 window. No way to
say insmod XXXX. I can remove the symbios scsi-driver module, but I cannot
load another one. The only offer is sym58xxx. Am I doing something very
wrong here?
2.) saying "text" at boot prompt leads to yast2 / text mode. I had the same
problems here, at last I could see a message on Alt F4 : no module called
aic7xxx.
So here is my question:
- how can I make linux aware of the aic7xxx module at boot time? Should I
expect stability issues? Am I doing something wrong? Any help is greatly
appreciated,
many thanks in advance,
take care



Dieter Jurzitza

P.S. I am using a Sparc U 60.


-- 
________________________________________________

HARMAN BECKER AUTOMOTIVE SYSTEMS

Dr.-Ing. Dieter Jurzitza
Manager Hardware Systems
         ESI

Industriegebiet Ittersbach
Becker-Göring Str. 16
D-76307 Karlsbad / Germany

Phone: +49 (0)7248 71-1577
Fax:   +49 (0)7248 71-1216
eMail: [email protected]
Internet: http://www.becker.de
 

> -----Original Message-----
> From: Harty, Brook [mailto:[email protected]]
> Sent: Friday, October 11, 2002 7:21 PM
> To: 'Robert Schiele'; Harty, Brook
> Cc: [email protected]
> Subject: RE: [suse-sparc] sparc-suse-linux/bin/ld: cannot 
> find -lstdc++
> 
> 
> 
> 
> -----Original Message-----
> From: Robert Schiele [mailto:[email protected]]
> Sent: Thursday, October 10, 2002 10:53 AM
> To: Harty, Brook
> Cc: [email protected]
> Subject: Re: [suse-sparc] sparc-suse-linux/bin/ld: cannot 
> find -lstdc++
> 
> 
> On Thu, Oct 10, 2002 at 11:42:23AM -0500, Harty, Brook wrote:
> > Any ideas on how to install the new gcc3.2 packages? 
> Everything seemed to
> > work, until I compiled the new vnc.
> > error - sparc-suse-linux/bin/ld: cannot find -lstdc++
> > 
> > ldconfig -v | grep -i libstd
> > 
> > ldconfig: /usr/lib/libstdc++-libc6.2-2.so.3 is not a symbolic link
> > ldconfig: /usr/lib/libg++-libc6.2-2.so.3 is not a symbolic link
> > 
> > 
> > But checking the directory, libstdc++.so.5 is there.
> > 
> > -r-xr-xr-x    1 root     root       360031 Sep 20 11:32
> > libstdc++-3-libc6.1-2-2.10.0.so
> > -rw-r--r--    1 root     root       541424 Oct 28  2001
> > libstdc++-3-libc6.2-2-2.10.0.a
> > -r-xr-xr-x    1 root     root       379038 Oct 28  2001
> > libstdc++-3-libc6.2-2-2.10.0.so
> > -r-xr-xr-x    1 root     root       452801 Sep 20 11:32
> > libstdc++-libc6.1-1.so.2
> > lrwxrwxrwx    1 root     root           31 Sep 27 13:49
> > libstdc++-libc6.1-2.so.3 -> libstdc++-3-libc6.1-2-2.10.0.so
> > lrwxrwxrwx    1 root     root           30 Sep 27 13:48
> > libstdc++-libc6.2-2.a.3 -> libstdc++-3-libc6.2-2-2.10.0.a
> > -r-xr-xr-x    1 root     root       379034 Sep 20 11:32
> > libstdc++-libc6.2-2.so.3
> > lrwxrwxrwx    1 root     root           18 Sep 27 15:50 
> libstdc++.so.2.8
> ->
> > libstdc++.so.2.8.0
> > -rwxr-xr-x    1 root     root       368928 Sep 20 11:32 
> libstdc++.so.2.8.0
> > lrwxrwxrwx    1 root     root           18 Sep 27 15:48 
> libstdc++.so.5 ->
> > libstdc++.so.5.0.0
> > -rwxr-xr-x    1 root     root       942594 Sep 20 06:25 
> libstdc++.so.5.0.0
> > 
> > 
> > Any ideas?
> 
> You didn't install libstdc++-devel, did you?
> 
> Robert
> 
> -- 
> Robert Schiele			Tel.: +49-621-181-2517
> Dipl.-Wirtsch.informatiker	mailto:[email protected]
> 
> 
> Nope. That was the problem. Thanks!
> -Brook
> 
> 
> -- 
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.