I have a strange problem. I have an IBM e325 server with two opteron
chips on it. We installed SUSE 9.1 on this machine with out any problems
and it works great. We just purchased SLES 9 and now we are trying to
install SLES 9 on the machine but the install fails.
The machine boots and starts the install and gets to the point where it
start to load the RAM disk with this message on the screen.
"Loading data into Ram disk 57950 KB"
Then on the console I see this message
Loading image "/var/adm/mount/boot/root"
/dev/ram2: unknown fs type
mount: /dev/ram2: no such device
and right after this I get put on the "Main Menu" of the install program
and can not continue from here.
Any ideas why Suse 9.1 installs with no problems but SLES 9 does not?
We are really happy with SuSe 9.1 but we have to switch to SLES 9 in order
to get support from IBM.
Thank you for any help on this.
we have two machines with MSI K8N Neo Platinum mainboards and USB
hotplugging doesn't work. Has anybody got it working with 9.2?
Martin Schröder, ms(a)artcom-gmbh.de
ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany
Voice +49 421 20419-44 / Fax +49 421 20419-10
I'm currently uploading to ftp.suse.com (will soon be also on its
The ISO is called:
If you have experienced installation problems with our 9.2 DVD, then
download this CD and boot from it. It will ask you then for "CD1",
and just insert the DVD at that point. During installation it will
load packages from CD1 several times...
This PatchCD has two advantages:
* Installation with a new kernel. If you had problems installing with
the DVD, please try it this way.
* All the updated packages are installed directly.
You can also download the CD and start "PatchCD" in YaST to only
install the updated packages.
Note the packages and the kernel are from before Christmas, so we have
some more updates out since then...
Hope this helps,
Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
the answer is :
recompile with -fPIC
put this option (-fPIC) in every Makefile of this project as a CFLAG .
In german you find the docu http://www.pseudonym.org/schauen.html, than look
for mjpeg on this page.
> -----Ursprüngliche Nachricht-----
> Von: Michael Steinhauser [mailto:firstname.lastname@example.org]
> Gesendet am: Montag, 4. Oktober 2004 21:04
> An: Mike.Philipp(a)passau.netsurf.de
> Cc: suse-amd64(a)suse.com
> Betreff: Re: [suse-amd64] mjpegtools
> Mike Philipp wrote:
> >Hi All,
> >could anyone compile and link mjpegtools-1.6.2 on the AMD!
> >I've tried it for three days now, but it doesn't work.
> >Does anybody has a src.rpm or an already compiled x86_64
> >(with mpeg2enc)???
> >Thanx in advance
> > Mike
> I tried it too and asked at mjpeg-users list.
> Here are the postings:
> I tried to install mjpegtools 1.6.2 on Suse 9.1 x86_64. I ran
> with --enable-libsuffix=64 and got no errors.
> When I typed make, the following error was reportet:
> -Wl,-soname -Wl,libmplex2-1.6.so.0 -o .libs/libmplex2-1.6.so.0.2.2
> ../utils/libmjpegutils.a(mjpeg_logging.o): relocation R_X86_64_32 can
> not be used when making a shared object; recompile with -fPIC
> ../utils/libmjpegutils.a: could not read symbols: Bad value
> collect2: ld returned 1 exit status
> make: *** [libmplex2.la] Fehler 1
> make: Leaving directory
> make: *** [all-recursive] Fehler 1
> make: Leaving directory `/SHARE/Linux/RPMS/SRC/mjpegtools-1.6.2'
> make: *** [all] Fehler 2
> Can anyone help?
> the answer:
> On Fri, 2004-09-03 at 10:18, Michael Steinhauser wrote:
> >> I tried to install mjpegtools 1.6.2 on Suse 9.1 x86_64.
> >> ../utils/libmjpegutils.a(mjpeg_logging.o): relocation
> R_X86_64_32 can
> >> not be used when making a shared object; recompile with -fPIC
> >> ../utils/libmjpegutils.a: could not read symbols: Bad value
> This should be corrected in CVS for some time already.
> So i downloaded the latest CVS-version, did a ./configure
> --prefix=/usr --libdir=/usr/lib64 --enable-libsuffix=64
> --sysconfdir=/etc --with-x --x-includes=/usr/X11R6/include
> --x-libraries=/usr/X11R6/lib64 --with-gnu-ld
> --without-libquicktime --with-gtk-prefix=/opt/gnome and it
> compiled with no errors. After a checkinstall, where i had to
> change some settings (version was there to often) i had a
> installable rpm. It installed without errors, but i did not
> try it till now.
> Check the List-Unsubscribe header to unsubscribe
> For additional commands, email: suse-amd64-help(a)suse.com
I have been running SuSe 9.1 pro (installed all latest updates)
for AMD64 on my S2882 motherboard with two opteron processors for a long
time (8-months) without any major problem. The system hard drive is an
ide drive. I have a promise sx6000 external raid array attached to the
on-board SCSI on chanel A and a VXA2 tape drive on chanel B. Last
thursday night the machine ran into trouble with the scsi part. The scsi
devices were not accessible and the kernel put out the following in the
Feb 26 04:08:35 raid1lac kernel: scsi0: At time of recovery, card was
Feb 26 04:08:35 raid1lac kernel: >>>>>>>>>>>>>>>>>> Dump Card State
Feb 26 04:08:35 raid1lac kernel: scsi0: Dumping Card State at program
address 0x11 Mode 0x33
Feb 26 04:08:35 raid1lac kernel: Card was paused
Feb 26 04:08:35 raid1lac kernel: HS_MAILBOX[0x0]
Feb 26 04:08:35 raid1lac kernel: SAVED_MODE[0x11]
Feb 26 04:08:35 raid1lac kernel: SCSISIGI[0x0]:(P_DATAOUT)
Feb 26 04:08:35 raid1lac kernel: LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE)
Feb 26 04:08:35 raid1lac kernel: SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI)
Feb 26 04:08:35 raid1lac kernel:
Feb 26 04:08:35 raid1lac kernel: SSTAT0[0x0] SSTAT1[0x8]:(BUSFREE)
Feb 26 04:08:35 raid1lac kernel: PERRDIAG[0x0]
Feb 26 04:08:35 raid1lac kernel: LQISTAT0[0x0] LQISTAT1[0x0]
Feb 26 04:08:35 raid1lac kernel: LQOSTAT1[0x0] LQOSTAT2[0x0]
The system works fine after I reboot the computer and the raid array. I
am not sure wether the scsi card is going bad or is it the raid array
going bad. Could anybody tell me what is exactly happening here or how I
should go about figuring our what has went bad.
I'm trying to install 9.2 x86_64 into my new machine. It's configured with
a single SATA drive & the BIOS is set to treat it as an IDE drive. I also
have a NV6600GT PCI express video card. I'm attempting a network FTP
install. The install always hangs just as YAST is activated. I see the
floppy drive light come on for a moment, the system speaker beeps once, &
then blank screen. The virtual consoles (ctl/alt/F1-F6) work & show the
YAST started message. Ctl/alt/del reboots the machine as well so the
machine is not hung, just the installation. I've tried the 32 bit as well
with the exact same result. Knoppix runs OK with the hard drive mounted
properly and all, so I don't think it's an issue with the hard drive
configuration or my Samsung LCD. Any help would be appreciated. Thank you.
I have an NVidia GeForceFX 5200 / 256MB AGP card.
It's identified as NVidia 0x0322 (nv) by Yast->Graphics Card and Monitor
I'm using SuSE 9.2.
The open source driver, nv, works great.
I downloaded and installed the nvidia driver with YOU. It works but
there is one problem. It will not use the 1280x1024 native resolution
of my 17" flat panel. When I tried to reconfigure the card, it allowed
me to select the 1280x1024 resolution (and all lower resolutions were
chosen as well). However, when I restart the X server I can only get
1280x960. This of course doesn't look so hot and a flat panel that
natively does 1280x1024.
The nv driver correctly uses the 1280x1024 res. Instead of configuring
with sax2, I also tried to use the original xorg.conf file for the nv
driver and replace "nv" by "nvidia". That still
didn't correct the resolution problem.
I wanted to know if anybody else had a similar situation with nvidia and
if there's a simple quick fix.
# Department of Applied Physics and Applied Mathematics
# Columbia University
Anyone out there tried using PearPC?
I would like to be able to compile 32 bit binaries for it on my 9.2
AMD64 box, I tried all sorts of combinations but the best I could get
was a segfault :( using:
espresso:/home/eheath/Downloads/pearpc-0.3.1 # CFLAGS=-m32
espresso:/home/eheath/Downloads/pearpc-0.3.1 # export CFLAGS
espresso:/home/eheath/Downloads/pearpc-0.3.1 # echo $CFLAGS
espresso:/home/eheath/Downloads/pearpc-0.3.1 # linux32 ./configure
--libdir=/usr/lib --enable-cpu=jitc_x86 --enable-ui=sdl
It runs pretty well if I copy a 32 bit binary from a 32 bit box but I'm
having issues with networking and want to try a few different builds
Any pointers would be much appreciated.
I am trying to get mainactor to behave on on my SuSE 9.2 64 bit system.
The only missing link I have is now libavc1394. It is installed per
default in its 64 bit form. Mainactor is a 32 bit application and will
need to have access to the 32 bit form of libavc. My question is this:
If I pull the rpm from the 32 bit SuSE version and install it on top of my
system, will it work? Will other things break?
Best regards, Alex.