CD 1 install goes fine, with YaST icons all the way through [taking about 40 mins], but on the reboot I only get the > grub command! Nothing to suggest how I get onto the 2nd CD or continue the install.
I am new to linux!!
Any suggestions gratefully received. Thanks

Did you choose to install grub into the MBR of the first hard disk drive?
And did you let SuSE installer partition your drive on its own?
I guess grub cannot find the boot partition...

Sorry, I didn't choose to put it anywhere!
I chose keyboard layout ect, auto partition etc, but that's all. The rest happened automatically
No other OS on the machine- only one HDD!!!

Do you know which filesystem your root partition has?

Oops, what a question. You said you're new to Linux...
I guess it is ReiserFS. That should work. There was a problem with XFS I remember...
I would reinstall SuSE and begin with the first CD. When partitioning can be choosen I would do it on my own. And it's easy. By the way... you can't damage anything 'cause the drive is empty.
You should create a boot partition (mountpoint is /boot, filesystem ext2 (as SuSEs standard)) which is 16 MB,
a root partition (mountpoint is /, filesystem ReiserFS (as standard of SuSE)) with size you wish
and a swap partition with double size of your RAM.

installation of GRUB into MBR of /dev/hda (or what the installer says...)

I hope that will work. I always did it this way - choosing partitions on my own. And never had problems.

Did you take away the CD1 before the system first rebooting ? if so , the installation won't continue!

yes- I suspect I did
Will try again & leave it in
Thanks

Google led me here but I didn't find an answer so I thought I would try my luck posting my problem here.

I just bought SuSE 9.1 Pro and I'm having trouble getting it installed on my server, a Dell PowerEdge 2200. It has a HW RAID and 512MB RAM, but I'm not having trouble with either of those. I believe the problem is X / video related. The Dell has ATI on-board video "ATI mach64 (264VT)". I was a bit surprised to see SuSE using a pre-release version of XFree86: Version 4.3.99.902 (4.4.0 RC 2). FYI I see version 4.4.0 is now out.

Note that this server was running SuSE 7.1 Pro before I started a complete install of SuSE 9.1 Pro. SuSE 7.1 had installed without problem.


Here are my notes.:

I've tried to load 9.1 but the screen/keyboard locks up near what I assume to be the end of the install. I'm guessing this is perhaps where it tries to set up X windows. The screen and keyboard are totally unresponsive. <Ctrl><Alt><Backspace> does nothing. But sshd is running by this point. ssh'ing in, I see that X is using all available CPU and keeps looping as fast as strace will scroll this.:

gettimeofday({1088010974, 864178}, NULL) = 0

As it scrolls, the first number seems to increment by 1 every second, while
the second argument seems to run from 1 through 999999 repeatedly but does so
so rapidly it's just a blur (many thousands skipped per line of output).

This isn't totally matching what `man gettimeofday` indicates.:

int gettimeofday(struct timeval *tv, struct timezone *tz);

I guess it could just be in an intentional command loop or something watching
the time for some reason. I don't feel like getting in to the level of
running X in a debugger or such.

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
5004 root 25 0 10268 6724 4928 R 99.3 1.3 718:22.61 X

I had to use a -9 to kill X. Killing it had no effect other than to free up
the CPU time.

I then did a startx

lildell:~ # startx
xauth: creating new authority file /root/.Xauthority

This is a pre-release version of XFree86, and is not supported in any
way. Bugs may be reported to XFree86@XFree86.Org and patches submitted
to fixes@XFree86.Org. Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs).

XFree86 Version 4.3.99.902 (4.4.0 RC 2)
Release Date: 18 December 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: SuSE Linux [ELF] SuSE
Current Operating System: Linux lildell 2.6.4-52-default #1 Wed Apr 7 02:08:30
UTC 2004 i686
Build Date: 06 April 2004
Changelog Date: 29 February 2004
Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Wed Jun 23 19:19:28 2004
(==) Using config file: "/etc/X11/XF86Config"



It hung here. Keyboard came back to life (num lock LED came back on and caps
lock no toggles LED), but the screen was still blank. <Alt><Ctrl><Backspace>
had no effect. <Alt><Ctrl><Del> started a shutdown which printed "The system
is going down for reboot NOW!" but otherwise seemed to have no effect. ps
showed X again using all available CPU. Kill -9 stopped it again.

/var/log/XFree86.0.log had 545 lines in it. Nothing looked obviously wrong
therein. At the top it said it was pre-release.:

This is a pre-release version of XFree86, and is not supported in any
way. Bugs may be reported to XFree86@XFree86.Org and patches submitted
to fixes@XFree86.Org. Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs).

XFree86 Version 4.3.99.902 (4.4.0 RC 2)


And the last few lines were.:

(II) Loading /usr/X11R6/lib/modules/libi2c.a
(II) Module i2c: vendor="The XFree86 Project"
compiled for 4.3.99.902, module version = 1.2.0
ABI class: XFree86 Video Driver, version 0.7
(II) ATI(0): I2C bus "Mach64" initialized.



In the 500 or so lines between, it said things like it was loading the ATI
stuff which looked good as far as I can tell.

I also looked at /etc/X11/XF86Config and saw nothing odd. It looked fairly
standard / simple. I've not tried to run the X configuration program
manually yet.

I ran a shutdown (via the ssh session) and rebooted. It came back up but went back to the blank screen as before. I'm not sure it completed 100% of the install? It was back to it's state of X soaking up all available CPU cycles but doing nothing useful.

Thanks in advance.

Update: I've tried about everything I could think of and still can't get X working with SuSE 9.1. I've installed the online updates. I tried a manual xf86configure. I've reinstalled a few times. X still loops trying ot start, using all available CPU cycles, and looping with a gettimeofday() call. Anyone have any suggestions? Note that earlier versions of SuSE installed and ran fine on this Dell PowerEdge 2200 server. Thanks.

I'm bumping this as I've still not resolved it. More details here.:

http://forums.suselinuxsupport.de/in...showtopic=2333

Hallo jfelten,

sorry for being "pingelig", but please open a new Thread. Your problem is not related to the original one, and it's easier to track.
Thanx in advance!

OK. Now back to your problem.
I am not 100% sure that it's driver related. It may be an interaction between two modules or interrupt conflict or whatever.
It's also advisable to check RAM => means Memory test
I think that also a good idea would be to run YAST Online Update
(YOU) prior proceeding.

Let's try a framebuffer driver instead of the ATI driver. Framebuffer driver will work also for cards not having a genuine driver.

At the boot prompt please enter in the command line.

In the case you have GRUB as Bootmanager:
3 vga=xxx


If your Bootmanager however is LILO, then enter:
linux 3 vga=xxx

where xxx can be, depending on the color-depth and resolution

______________________Resolution_________________
Colors__________|_640x480_|_800x600_|_1024x768
256_____(8bit)__|__769_______771_______773
32000___(15bit)_|__784_______787_______790
65000___(16bit)_|__785_______788_______791
16.7Mil.__(24bit)_|__786_______789_______792

(Sorry for using that __, but if I use spaces then the table is not displayed correctly.
"_" means a space.)

I suggest you start conservative, so 800 X 600 with 256 colors (8 Bit) => vga=771

Yow will reach now Run Level 3. Please log in as root.

Start now sax with:
sax2 -m 0=fbdev

and set up other parameters (e.g. screen, mouse, etc.)

When everything is done start x with
startx or init5.

If everything works how it should then add vga=xxx, with the xxx value you want to use, as boot option
into your /boot/grub/menu.lst (if you are using GRUB) or /etc/lilo.conf (in case you are using LILO) for
the kernel you are booting.

BTW: [CTRL]+[ALT]+[BACKSPACE] restarts the X server.
[CTRL]+[ALT]+[F1] kills x-server, althought I do not know
if this will work if the x-server is not proerly started (e.g. hangs
during initialization like in your case)

Please also copy this response to the new thread you will open for your problem, so anyone who want's
to help knows what has be done so far.

Last but not least: VIEL GLÜCK!