Message-ID: <002701c05c65$c40ccf40$0b0aa8c0@alpha>
From: "Andrew Smith"
Message-ID: <3A2912BD.5D6FC34C@gypsyfarm.com>
Date: Sat, 02 Dec 2000 10:18:21 -0500
From: zentara
Hi
I'm setting up a small Linux network for my school. I'm trying to install SuSE 6.1 on the server - an old AST machine (P100, 32MB RAM) which has a new hard disk (13.6GB). After upgrading the BIOS to the latest version, I booted up from floppy and installed via CD. Installation goes fine until the system is started and YaST attempts to run to configure everything. The YaST 'splash screen' comes up, but then the machine just sits there doing sod all... I took a look at other consoles when this happened - on one of them (forgotten which) there was a 3 line stack dump. How can I solve this problem?
The disk is partitioned physically in this order: hda1 /boot 20MB hda4 swap 128MB hda2 /home 5GB hda3 / 8GB
Also, the system cant be started by LILO. LILO installs fine, but when the machine is switched on, it cant find an OS and asks for a system disk... any ideas?
Can you use the suse boot install floppy and use the feature "boot installed system", when you specify /dev/hda3 for /? Also try adding the linear option to lilo.conf.
Andrew Smith wrote:
Hi
I'm setting up a small Linux network for my school. I'm trying to
install
SuSE 6.1 on the server - an old AST machine (P100, 32MB RAM) which has a new hard disk (13.6GB). After upgrading the BIOS to the latest version, I booted up from floppy and installed via CD. Installation goes fine until the system is started and YaST attempts to run to configure everything. The YaST 'splash screen' comes up, but then the machine just sits there doing sod all... I took a look at other consoles when this happened - on one of
(forgotten which) there was a 3 line stack dump. How can I solve this problem?
The disk is partitioned physically in this order: hda1 /boot 20MB hda4 swap 128MB hda2 /home 5GB hda3 / 8GB
Also, the system cant be started by LILO. LILO installs fine, but when
Message-ID: <001c01c05d35$27bb2580$0b0aa8c0@alpha>
From: "Andrew Smith"
machine is switched on, it cant find an OS and asks for a system disk... any ideas?
Can you use the suse boot install floppy and use the feature "boot installed system", when you specify /dev/hda3 for /?
Yes. After the first install failed and the system didnt boot, I tried using the bootdisk to start the system and it boots fine. But then it sees that the installation hasnt finished, so starts up YaST, which crashes. Because no terminals are started by the time YaST is started, the machine is usless and requires a hard reboot (reset button).
Also try adding the linear option to lilo.conf.
Will do so (will next have access to the machine on tuesday). Out of interest, what does this do? <p>Many Thanks, <p><p>Andrew
Message-ID: <3A2BA7B6.59C8E496@iname.com>
Date: Mon, 04 Dec 2000 14:18:30 +0000
From: Chris Reeves
Andrew Smith wrote:
I'm setting up a small Linux network for my school. I'm trying to
SuSE 6.1 on the server - an old AST machine (P100, 32MB RAM) which has a new hard disk (13.6GB). After upgrading the BIOS to the latest version, I booted up from floppy and installed via CD. Installation goes fine until the system is started and YaST attempts to run to configure everything. The YaST 'splash screen' comes up, but then the machine just sits there doing sod all... I took a look at other consoles when this happened - on one of
(forgotten which) there was a 3 line stack dump. How can I solve this problem?
The disk is partitioned physically in this order: hda1 /boot 20MB hda4 swap 128MB hda2 /home 5GB hda3 / 8GB
Also, the system cant be started by LILO. LILO installs fine, but when
install them the
machine is switched on, it cant find an OS and asks for a system disk... any ideas?
Did you install LILO into the MBR? You might have accidentally installed LILO onto the root partition. Under normal circumstances, you would at least get an 'L' when you boot up, unless the BIOS is set to not try and boot off the HD (which may be the case, since you upgraded the BIOS).
Can you use the suse boot install floppy and use the feature "boot installed system", when you specify /dev/hda3 for /?
Yes. After the first install failed and the system didnt boot, I tried using the bootdisk to start the system and it boots fine. But then it sees that the installation hasnt finished, so starts up YaST, which crashes. Because no terminals are started by the time YaST is started, the machine is usless and requires a hard reboot (reset button).
Also try adding the linear option to lilo.conf.
Will do so (will next have access to the machine on tuesday). Out of interest, what does this do?
The linear option 'Generate[s] linear sector addresses instead of sector/head/cylinder addresses.' Basically, some drives get confused about their geometry (or at least, there is confusion between the drive, BIOS, and LILO). To counter this, the 'linear' option make LILO use linear sector addresses which are translated at run time, and which are entirely independent of the disk geometry in terms of cylinders, etc. Hope that helps, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
Andrew Smith wrote:
I'm setting up a small Linux network for my school. I'm trying to
install
SuSE 6.1 on the server - an old AST machine (P100, 32MB RAM) which
has a
new
hard disk (13.6GB). After upgrading the BIOS to the latest version, I booted up from floppy and installed via CD. Installation goes fine until
is started and YaST attempts to run to configure everything. The YaST 'splash screen' comes up, but then the machine just sits there doing sod all... I took a look at other consoles when this happened - on one of
system them
(forgotten which) there was a 3 line stack dump. How can I solve
Message-ID: <008901c063c7$3cd04de0$0b0aa8c0@alpha>
From: "Andrew Smith"
problem?
The disk is partitioned physically in this order: hda1 /boot 20MB hda4 swap 128MB hda2 /home 5GB hda3 / 8GB
Also, the system cant be started by LILO. LILO installs fine, but when the machine is switched on, it cant find an OS and asks for a system disk... any ideas?
Did you install LILO into the MBR? You might have accidentally installed LILO onto the root partition. Under normal circumstances, you would at least get an 'L' when you boot up, unless the BIOS is set to not try and boot off the HD (which may be the case, since you upgraded the BIOS).
Yes, LILO is in the MBR, but for some reason the machine doesnt detect it there (yes, I know that sounds strange). I've installed Linux/LILO loads of times before sucessfully, so I'm not sure what the problem is... AKIK the mackine boots from HD, but I will check...
Can you use the suse boot install floppy and use the feature "boot installed system", when you specify /dev/hda3 for /?
Yes. After the first install failed and the system didnt boot, I tried
the bootdisk to start the system and it boots fine. But then it sees
using that
the installation hasnt finished, so starts up YaST, which crashes. Because no terminals are started by the time YaST is started, the machine is usless and requires a hard reboot (reset button).
Also try adding the linear option to lilo.conf.
Will do so (will next have access to the machine on tuesday). Out of interest, what does this do?
The linear option 'Generate[s] linear sector addresses instead of sector/head/cylinder addresses.' Basically, some drives get confused about their geometry (or at least, there is confusion between the drive, BIOS, and LILO). To counter this, the 'linear' option make LILO use linear sector addresses which are translated at run time, and which are entirely independent of the disk geometry in terms of cylinders, etc.
Ah, I see. Because LILO doesnt run at boot time (above problem) I cant parse the linar option to it as i'm stuck to booting via the install disk. Any ideas why YaST keeps crashing... ? Many Thanks again, <p>Andrew Smith
Message-ID: <006201c05d57$92ccb100$f8477018@shprd1.on.wave.home.com>
From: "j"
From: Álvaro A. Novo
I've been since 5.0, never ever any problems. Now with 7.0 after upgrade from 6.4. I have no mouse after upgrade.
Console messages: " gpm [1125] :oops() invoked from gpm.c ( 923 ) gpm ... :/dev/mouse No such file or directory "
in /dev/ is a link:
/dev/mouse -> /dev/ttyS0
Is your mouse really in ttyS0 (com1)? My PS2 is in port /dev/psaux... in ttyS0 i have my external modem and in ttyS1 Memory Stick Serial Port Adaptor.. . Hope it helps... Alvaro Novo SuSE 6.4 -=- Kernel 2.2.16 -=- KDE 2.0.0-0 1:56pm up 2 days, 22:35, 2 users, load average: 0.04, 0.01, 0.00
Message-ID: <002101c05d77$4c0d3800$f8477018@shprd1.on.wave.home.com>
From: "j"
/dev/mouse -> /dev/ttyS0
Is your mouse really in ttyS0 (com1)? My PS2 is in port /dev/psaux... in ttyS0 i have my external modem and in ttyS1 Memory Stick Serial Port Adaptor.. .
Hope it helps...
Alvaro Novo
<p>Thanks for respond. It is on the com1 . Under version 5.0 - 6.4 worked fine. Just after upgrade to 7.0 mouse does not exist. Jul
participants (5)
-
andrew＠andrewsmith.plus.com -
chris.reeves＠iname.com -
julg＠home.com -
novo＠uiuc.edu -
zentara＠gypsyfarm.com