Udo Mueller schrieb:
[...]
Du sagtest, dass /dev/hdb1 auf /boot eingehängt ist. Meinst du das
/boot von Debian oder von Suse? Benutzt du für beide Systeme das
gleiche /boot?
Nein! Auf jeder Platte sitzt eine eigene Boot-Partition.
Wenn Debian sein eigenes hat, dann musst du unter Debian hdb1
Quoting Oliver Vecernik [EMAIL PROTECTED]:
Gut , habe ich gemacht. Nur meckert lilo wieder, daß er den Pfad
/boot/vmlinuz nicht finden kann (was ja eigentlich auch stimmt,
da die /boot-Partition ja auf /dev/hdb1 liegt und / auf /dev/hdb3.
Nur steht das ja in /etc/fstab der SuSE-Platte und
On Fri, 22 Mar 2002, Jonathan Tabaco wrote:
Sorry to all those who are inconvenienced by this but I have tried
multiple times to get removed from the mailing list.
I even sent in the confirm CONFIRM u03180819391769
PLEASE REMOVE ME MANUALLY, as your automated system doesn't work.
To
begin Paul 'Baloo' Johnson quotation:
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
or visit http://lists.debian.org/
Telling him once, nicely, was kind of you. Telling him repeatedly, you
risk becoming as much of a problem as
On Fri, 22 Mar 2002 14:22, Michal Novotny wrote:
I have a real problem booting my Debian.
I just upgraded all packages (running dselect).
Now what I get after reboot is (last lines):
request_module[block-major-3]: Root fs not mounted
VFS: Cannot open root device 301 or 03:01
Please append a
On Fri, 22 Mar 2002 17:16, Michal Novotny wrote:
Something else, there is in /boot/config-2.4.17-386 line:
CONFIG_BLK_DEV_SIS5513=y
that is my IDE controller
but there is too:
CONFIG_IDE=m
CONFIG_BLK_DEV_IDE=m
CONFIG_BLK_DEV_IDEDISK=m
CONFIG_BLK_DEV_IDEPCI=y
You have two options. One is
Sorry to all those who are inconvenienced by this but I have tried
multiple times to get removed from the mailing list.
I even sent in the confirm CONFIRM u03180819391769
PLEASE REMOVE ME MANUALLY, as your automated system doesn't work.
I will unfortunately have to resort to spamming the
Hi,
hope you can boot with your previous kernel or from disk. If so, look for error
messages in the log files: /var/log/dmesg, kern.log or syslog.
HTH, Joachim
On Fri, Mar 15, 2002 at 06:21:54PM +0100, [EMAIL PROTECTED] wrote:
I can't boot my new kernel 2.4.10, the boot process looks
like :
On Fri, Mar 15, 2002 at 06:21:54PM +0100, [EMAIL PROTECTED] wrote:
I can't boot my new kernel 2.4.10, the boot process looks
like :
LILO Loading Linux ...
Uncompressing Linux ... Ok booting the kernel
and then nothing else !
Look for Debian install disk set (CD/FD) and boot from it with
I can't boot my new kernel 2.4.10, the boot process looks
like :
LILO Loading Linux ...
Uncompressing Linux ... Ok booting the kernel
and then nothing else !
thanks for help.
You might consider booting into single user mode where you will be able
to run each rc script in turn by hand. Afterwards you can run the
system shutdown scripts by hand too; thus trying to pin point the
problem.
As an alternative to a single user mode you might try to issue
init=/bin/sh
as
I'm running Debian Woody, and have been using kernel v2.2.18 for a long
while. Recently, I upgraded to 2.4.16. make, make modules, and make
modules_install worked great. However, when I boot to the new kernel,
as soon as Lilo.. finishes, the system reboots. Just for kicks, I
tried with
On Friday, August 31, 2001 9:00 AM, [EMAIL PROTECTED] wrote
I don't know if the windows 2000 boot loader is different than windows
9x,
but when I used to use windows 98, I had in /etc/lilo.conf:
other=/dev/hda1
label=win
Works just fine for w2k.
I am not sure though cos
On Thursday, August 30, 2001 4:40 PM, [EMAIL PROTECTED] wrote:
On Thu, Aug 30, 2001 at 05:56:39PM +, Giri X wrote:
| I recently installed Debian on a ayatem that had Win2k on it b4. I
made 2
| [...]
| thing). There was no Windows image. So now i can boot only into Debian
but
| now
On Thursday 30 August 2001 17:56, Giri X wrote:
Hi
I recently installed Debian on a ayatem that had Win2k on it b4. I made 2
partiotions using GNU Parted and put Debian on the second. But after the
installation of Debian, I am not able to boot into Win2k. I checked
/etc/lilo.conf. It had only
On Fri, 31 Aug 2001, Greg Wiley wrote:
On Thursday, August 30, 2001 4:40 PM, [EMAIL PROTECTED] wrote:
On Thu, Aug 30, 2001 at 05:56:39PM +, Giri X wrote:
| I recently installed Debian on a ayatem that had Win2k on it b4. I
made 2
| [...]
| thing). There was no Windows image. So
what about table=/dev/hda ?
- Original Message -
From: Greg Wiley [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Sent: Friday, August 31, 2001 8:23 PM
Subject: Re: dual boot problem
On Thursday, August 30, 2001 4:40 PM, [EMAIL PROTECTED] wrote:
On Thu, Aug 30, 2001 at 05:56
On Fri, Aug 31, 2001 at 12:00:54PM -0400, Narasimhamurthy Giridhar wrote:
I am not sure though cos yday I removed Win2k , put back Win ME and only
then did the dual boot work. Owise i used to get that
inlcuding Win9
Fatal: no image installed error. Havent still figured out the problem.
did
FAT32-thats how i formatted it.
Narasimhamurthy Giri, Clemson University Computer Science Dept.
---
Judge not lest ye be judged yourself.
---
On Fri, Aug 31, 2001 at 04:55:50PM -0400, Narasimhamurthy Giridhar wrote:
FAT32-thats how i formatted it.
here's a lilo.conf that i use on one of my debian boxes
which has windoze on it as a dual-boot (windoze is on hda1,
debian has a small /boot partition on hda2 and the root partition
on
Hi
I recently installed Debian on a ayatem that had Win2k on it b4. I made 2
partiotions using GNU Parted and put Debian on the second. But after the
installation of Debian, I am not able to boot into Win2k. I checked
/etc/lilo.conf. It had only 2 images, vmlinuz and old*.*(forgot the exact
On Thu, Aug 30, 2001 at 05:56:39PM +, Giri X wrote:
| Hi
| I recently installed Debian on a ayatem that had Win2k on it b4. I made 2
| partiotions using GNU Parted and put Debian on the second. But after the
| installation of Debian, I am not able to boot into Win2k. I checked
|
On Thu, Aug 30, 2001 at 02:31:30PM -0400 or thereabouts, dman wrote:
On Thu, Aug 30, 2001 at 05:56:39PM +, Giri X wrote:
| Hi
| I recently installed Debian on a ayatem that had Win2k on it b4. I made 2
| partiotions using GNU Parted and put Debian on the second. But after the
|
on Thu, Aug 30, 2001 at 02:31:30PM -0400, dman ([EMAIL PROTECTED]) wrote:
On Thu, Aug 30, 2001 at 05:56:39PM +, Giri X wrote:
| Hi
| I recently installed Debian on a ayatem that had Win2k on it b4. I made 2
| partiotions using GNU Parted and put Debian on the second. But after the
|
On Thu, Aug 30, 2001 at 05:56:39PM +, Giri X wrote:
Hi
I recently installed Debian on a ayatem that had Win2k on it b4. I made 2
partiotions using GNU Parted and put Debian on the second. But after the
installation of Debian, I am not able to boot into Win2k. I checked
/etc/lilo.conf.
On Tue, 17 Jul 2001, D-Man wrote:
On Wed, Jul 18, 2001 at 01:12:56AM +1000, Sam Varghese wrote:
| On Tue, Jul 17, 2001 at 10:43:26AM +0100, J.A.Serralheiro wrote:
| well maybe you misconfigured your video card.
| Run xf86config. Its a text based environment and re-do the configurations.
| It
During the boot process the computer starts starting all the regular
services but hangs at ,Starting X font server: xfs/usr/bin/X11/xfs notice:
listening on port 7100 What do I do? I just have a blinking prompt. The
boot doesn't go anywhere. I have been trying to get x installed (another
post).
well maybe you misconfigured your video card.
Run xf86config. Its a text based environment and re-do the configurations.
It may help. be sure you know what chipset your board has. I think yuo can
also choose and general chipset that should work on most cards.
If you can put it to work, then use
On Tue, Jul 17, 2001 at 10:43:26AM +0100, J.A.Serralheiro wrote:
well maybe you misconfigured your video card.
Run xf86config. Its a text based environment and re-do the configurations.
It may help. be sure you know what chipset your board has. I think yuo can
also choose and general chipset
On Wed, Jul 18, 2001 at 01:12:56AM +1000, Sam Varghese wrote:
| On Tue, Jul 17, 2001 at 10:43:26AM +0100, J.A.Serralheiro wrote:
| well maybe you misconfigured your video card.
| Run xf86config. Its a text based environment and re-do the configurations.
| It may help. be sure you know what
Sorry. Ididnt check that, and its been a while since i did the last
configuration.
I'm having a problem booting my firewall box from a syslinux floppy. It
boots the same kernel from the HD under lilo just fine. I know that this
worked once upon a time using kernel 2.2.17, but it's not working now
with kernel 2.2.19, and (he sheepishly adds) I seem to have misplaced
the .config I
Answering my own question, here is the configuration selection (from
block devices using make menuconfig) that boots from lilo but not from
syslinux:
[*] Normal PC floppy disk support
[ ] Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
--- Please see Documentation/ide.txt for help/info on IDE
I'm trying to install Debian potato on my laptop. I've got the generic
i386 disks (rescue.bin and root.bin + the drivers1-4, etc).
My laptop (a sony vaio picturebook) has a USB floppy drive and no cdrom.
So I generally do net installs of RedHat on it.
The floppy works great to boot the first
Please keep list mail on list. Reply redirected to list.
on Wed, Apr 11, 2001 at 09:33:56PM -0700, Jack Moffitt ([EMAIL PROTECTED])
wrote:
Bad floppies are legion in Debian installs. Try another. And another.
And another. If you can't get it right in six to ten, consider another
route.
Hello,
I've just finished recompiling the kernel for the first time ever.
Unfortunately, I've probably done something wrong, because I can't reboot
the system. The story goes like this:
When I tried booting my new kernel everything seemed to be going well, at
first. The kernel was
Although I can't tell you what went wrong, don't reinstall yet. Using a
windows machine, head over to tomsrtbt:
http://www.toms.net/rb/home.html
There is a version to install from windows.
With tomsrtbt, you will be able to mount your original root partition and
fix the problem.
Gil Elad
Hello,
I've just finished recompiling the kernel for the first time ever.
Unfortunately, I've probably done something wrong, because I can't reboot
the system. The story goes like this:
When I tried booting my new kernel everything seemed to be going well, at
first. The kernel was
Hi,
I installed a modem and configured(?) with pppconf.
Now the problem is that at boot time is trying to start the
pppd, configuration is probably wrong, so it get frozen - Cntr C
or anything else doesn't work.
Any ideas haw can the system be rebooted, so I can configure again
ppp
On Sat, Feb 03, 2001 at 06:53:47PM -0500, Tino Ionescu wrote:
Hi,
I installed a modem and configured(?) with pppconf.
Now the problem is that at boot time is trying to start the
pppd, configuration is probably wrong, so it get frozen - Cntr C
or anything else doesn't work.
Any ideas
I don't know for sure, but often - even under Linux - Ctrl+Alt+Del will
do a reboot. That depends on your /etc/inittab settings though. And I can
easily imagine a situation where that wouldn't work, if the keyboard is
in raw mode (maybe ?), but it's at least worth a try.
I hope this helps to
: UDMA66 boot problem/HPT370
Date: Tue, 12 Dec 2000 21:46:46 +0100
When I try installing Debian 2.2r2 on my HPT370 Raid/UDMA100 controller, with
the UDMA66 boot floppies, the system halts during the boot process. ...
...
Abit KT7-Raid Motherboard
...
Alexander
--
From
Jon Branch wrote:
Hi Alexander
Sorry no solution from me. I'm faced with a near identical problem using the
HPT 370 on-board controller with a 2theMax BX7 +100 motherboard (actually
with five of them). So I'll be interested to see the solution if/when you get
one.
Regards
I read
be
interested to see the solutionif/when you get one.
Regards Jon Branch
--Original Message-- From: "Alexander Sawallich"
[EMAIL PROTECTED] To: debian-user debian-user@lists.debian.org, debian-bootdebian-boot@lists.debian.org Sent: December 12, 2000 8:46:46 PM GMT
Subject: U
--
From: Alexander Sawallich [EMAIL PROTECTED]
To: debian-user debian-user@lists.debian.org, debian-boot
debian-boot@lists.debian.org
Sent: December 12, 2000 8:46:46 PM GMT
Subject: UDMA66 boot problem/HPT370
When I try installing Debian 2.2r2 on my HPT370 Raid/UDMA100 controller
When I try installing Debian 2.2r2 on my HPT370 Raid/UDMA100
controller, with the UDMA66 boot floppies, the system halts during the boot
process. Why? Thnanks for any help. I´m sorry this description got so long, but
if someone really wants to help he might need some of the info below.
I´m
When I try installing Debian 2.2r2 on my HPT370 Raid/UDMA100 controller, with
the UDMA66 boot floppies, the system halts during the boot process. Why? Thnanks
for any help. I´m sorry this description got so long, but if someone really
wants to help he might need some of the info below.
I´m
On Sat, 28 Oct 2000, Janos Kramar wrote:
My error message was different (kernel panic during boot) but it was
caused by the built-in Boot virus detection in my new ASUS CUSL2
motherboard. I could boot from floppy but not from the harddrive that I
pulled out of my old P200 machine. I turned off
After installing Debian without any apparent problems and rebooting the
computer without the boot disk, it says:
MBR
L 07 07 07 07 07 07 07 07 07 ... and so forth.
It works fine with the boot disk. I have an hda unused approx. 5GB hard
drive, a hdb dvd-rom, and hdc cd-rom, and an hdd 30GB
I would try reinstalling Lilo just off the top of my head that is what it looks
like to me.
-- Original Message --
From: Janos Kramar [EMAIL PROTECTED]
Date: Sat, 28 Oct 2000 12:52:14 -0400
After installing Debian without any apparent problems and
[EMAIL PROTECTED] writes:
I would try reinstalling Lilo just off the top of my head that is what it
looks like to me.
After installing Debian without any apparent problems and rebooting the
computer without the boot disk, it says:
MBR
L 07 07 07 07 07 07 07 07 07 ... and so forth.
It works fine
Ok, I'm sure if this is lilo, or what but the last few times I have had
to
reboot(not often, admitedly) Lilo has been rendered unusable and I have
to
boot from a CD and re-run lilo. I havn't been changing kernels or
anything.
Usually it'll go LIL- and freeze, but just recently it tried to boot
Hi,
I'm a novice to Linux and Unix in general. I've
installed Debian on my system - a 133MHz Pentium with 32MB RAM and 2 Hard Disks
with the Linux Swap partition being 8 MB and the core Linux Partition being
484MB.I dont have an idea as to the Debian version however at boot up the Linux
On Wed, Jan 03, 1996 at 01:17:56AM +0530, Jeetu Golani wrote:
Hi,
I'm a novice to Linux and Unix in general. I've installed Debian on
my system - a 133MHz Pentium with 32MB RAM and 2 Hard Disks with the
Linux Swap partition being 8 MB and the core Linux Partition being
484MB.I dont have an
I had no idea where to post this message,i hope it's ok here.
Compiling the kernel was no problem. But when i tried to boot with the new
image, i got
kmod: failed to exec /sbin/modprobe -s -h binfmt=464c, errno= 8
in the middle of the bootprocess, It fills the screen completely, so i
can't
I had no idea where to post this message,i hope it's ok here.
Compiling the kernel was no problem. But when i tried to boot with the new
image, i got
kmod: failed to exec /sbin/modprobe -s -h binfmt=464c, errno= 8
in the middle of the bootprocess, It fills the screen completely, so
hi!
i just try to get a brandnew machine running. now the kernel hangs at
boottime when it finds the scsi controller. the last message ist:
scsi 0 Downloading sequencer code ... 396 instructions downloaded
i use a compact bootdisk from the frozen (potato) distribution. i also
tried the no_probe
Hi all
I have trouble setting up LILO correctly. :-(
When booting LILO V20 (on other distro), I get error 0x02. This is
when I try to boot debian potato from a different disk (/dev/hdb) using
the other distro's LILO. (Other distro is on /dev/sda)
This is what (part of) my config file looks like:
When booting LILO V20 (on other distro), I get error 0x02. This is
Sorry, but the error code should have been 0x01 instead. Apologies.
In a README I've found data on error code 0x01:
0x01 Illegal command. This shouldn't happen, but if it does, it
may
indicate an attempt to access a disk
Hello
I don't know if it would help you, but I got error 0x01...which was
because
I forgot to enable the disk in my BIOS.
In fact my error is 0x01, as yours. In my BIOS I too haven't enabled the
IDE disk. This hasnt been a problem to Linux so far as it bypasses the
BIOS in many cases AFAIK.
I installed linux on apartition of 7GB using text installation and
fdisk instead of diskdruid because diskdruid limited the size of each
partition to 4GB maximum.
I installed the PC with dual boot: winnt and Linux. When the system
boot up, it only see Linux at the boot time. I was surprise
Hi Daisy
Did you run /sbin/lilo after changing lilo.conf? Dean
Daisy Nguyen Davis wrote:
I installed linux on apartition of 7GB using text installation and
fdisk instead of diskdruid because diskdruid limited the size of each
partition to 4GB maximum.
I installed the PC with dual boot:
I'm a newbie to Debian. I bought a book entitled Debian GNU/Linux 2.1
from SAMS. It had a single Debian CD in the back. From what I can tell from
the documentation, the CD was made sometime last November. After reading
the installation appendix, I tried installing from the CD. The system hung
Most of the time this means that you have Lilo configured wrong. There
are essentially two steps needed to get Lilo going: editing the file
/etc/lilo.conf to correctly reflect your setup, and then running the
/sbin/lilo command to install Lilo.
If you post more information, such as...
1) the
Hello,
I'm in a desperate need of assistence. I just a got my new computer
and I'm trying to install Debian 2.0 on it (to be upgraded to potato after
initial install). The problem is that it won't boot during the installation
process.
The last thing printed is md driver 0.35 MAX_MD_DEV=4,
as far as i know the athlon requires kernel 2.2.13 to boot(or
newer) anything less will crash (i read that 2.2.12 works but from what i
remember on the kernel mailing list 2.2.13 was the one to use)
nate
On Wed, 5 Jan 2000, Peter Schuller wrote:
scode Hello,
scode
scode I'm in a desperate need
David Johnstone wrote:
Hi,
Im running win95 on harddisk 1 (primary ide master). it has 2
partitions, but used by windows. On harddisk 2 (secondary ide
master), I have just installed linux. I can boot using the boot disk
- however for some reason it takes about 10 minutes when it says
ktb wrote:
David Johnstone wrote:
Hi,
Im running win95 on harddisk 1 (primary ide master). it has 2
partitions, but used by windows. On harddisk 2 (secondary ide
master), I have just installed linux. I can boot using the boot disk
- however for some reason it takes about 10
Floyd Rodgers [EMAIL PROTECTED] writes:
trying to initial load slink stable version sparc2 via floppies results in
these messages.
fatal error: cannot read file system
error: bad or malformed address
fatal error: cannot read file system
fatal error: cannot read file system
Please ask on
Hi,
Im running win95 on harddisk 1 (primary ide
master). it has 2 partitions, but used by windows. On harddisk 2
(secondary ide master), I have just installed linux. I can boot using the
boot disk - however for some reason it takes about 10 minutes when it says
"Loading linux..". I have
Hi,
I was warned that original message might cause the problems, and therefore
I sent it again.
Could anyone help me! Suddenly my Linux Debia2.1 box (2.2.3) cannt boot. It
worked for couple of mounths perfectly. Now, the last what I get is:
INIT: version 2.76 booting
INIT: Entering runlevel: 2
Hi,
could anyone help me! Suddenly my Linux Debia2.1 box (2.2.3) cannt boot. It
worked for couple of mounths perfectly. Now, the last what I get is:
.
.
.
INIT: version 2.76 booting
INIT: Entering runlevel: 2
INIT: Id 1 respawning too fast: disabled for 5 minutes
INIT: Id 2 respawning too fast:
configuration files for
lilos in your replying letter?
Thanks so much :)
Jack
From: Jean-Yves Barbier [EMAIL PROTECTED]
To: Jack Lee [EMAIL PROTECTED]
CC: debian-user@lists.debian.org
Subject: Re: Multi-Boot Problem
Date: Sun, 22 Aug 1999 15:02:37 +0200
Jack Lee wrote:
...
I can't solve
Hi:
I'm currently using Debian on
/de/hda1, which is 2G. Also, I have
MSDOS on /dev/hda2. Im just wondering
how can I use lilo to boot /dev/hda2?
I can't solve the problem because
I find /dev/hda2 is out of the 1024
cylinder area.
I tried to use linear option in
/etc/lilo.conf , but
Hello,
I have the same problem, but I have two partitions for Dos/Dr-Dos and
then Linux like:
hda1c: Dos 6.22 + WfW 3.11
hda2d: DR-Dos 7.03 with TCPIP and DJGPP
hda3Linux-Root/Boot
hda4Linux-Swap
hda5Linux-User
I have tried to boot with
Jack Lee wrote:
...
I can't solve the problem because
I find /dev/hda2 is out of the 1024
cylinder area.
HiJack (;-),
I would suggest you to use loadlin instead of lilo (see /usr/doc/lilo/)
Otherwise, if you intend to change your partitions, I had no problems with
1024 cyl lilo BUT
Hello all,
I seem to be causing myself problems in my boot somewhere. Sometime after
installing a new kernel and before my next reboot. I do something that breaks
my boot process, (I am not used to uptimes of weeks instead of hours ;-).
I am using slink with lilo for my boot on a dedicated
Quoting [EMAIL PROTECTED]:
boot=/dev/hda1
root=/dev/hda1
append=ether=10,0x300,eth0 ether=11,0x310,eth1
compact
install=/boot/boot.b
delay=20
map=/boot/map
vga=normal
image=/vmlinuz
label=Linux
read-only
I would remove the compact option. I never got a kernel to boot
Hello,
When I boot, I got the following error messages
.
Partition check:
hda1: hda1
hdb: [DM6:DD0] [remap +63] [624/128/63] hdb1/hdb2
attempt to access beyond end of device
03:03: rw=0, want=2, limit=0
EXT2-fs: unable to read
Hi
On Tue, 09 Feb, 1999 à 10:48:53AM -0600, Jiao Lingxiu wrote:
Hello,
When I boot, I got the following error messages
.
Partition check:
hda1: hda1
hdb: [DM6:DD0] [remap +63] [624/128/63] hdb1/hdb2
attempt to access beyond end of device
When I boot up my Linux box it get's stuck on LILO Loading Linux...
This has never happened before. I just compiled and installed a sound
supporting kernel, but that has been working until now. I installed my
kernel backup but it still does the same thing. The only way that I can
boot my
Even more wierd, I've reinstalled kernel-image (2.0.35 right from slink)
the NFS started working, but dhcpcd stopped - just gives me IP 0.0.0.0
Reinstallation of dhcpcd did not help.
Any ideas ?
Sergey.
On Fri, 23 Oct 1998, Sergey V Kovalyov wrote:
Hi,
I have a wierd problem: during boot
On Fri, 23 Oct 1998, Sergey V Kovalyov wrote:
Hi,
I have a wierd problem: during boot process mount fails with the following
message:
Starting portmapper... Mounting remote filesystems...
mount: RPC: Program not registered
I saw this once when rpc.mountd and/or rpc.nfsd on the server
Hi,
I have a wierd problem: during boot process mount fails with the following
message:
Starting portmapper... Mounting remote filesystems...
mount: RPC: Program not registered
But after the boot mount -a works perfectly.
This runs latest slink from unstable.
I did not have such a problem on a
Debian doesn't install LILO as the MBR, but rather uses a program
called MBR. It is MBR that is presenting this prompt. Look in
/usr/doc/MBR for documentation.
You don't give enough of a description of your installation to
determine the problem. Here's a guess though. It sounds as if
you
I'm hoping to run a course including the installation towards the end of next
week, but the machines I'll be using have a problem. When debian is installed
to boot off the hard disk, a prompt:
1FA:
comes up. According to the docs, this should mean that I can boot off
partition 1 of the hard
Well, I loaded Debian from floppy. However, while it boots from the boot
floppy fine, when I try to boot from the hd, it doesn't appear to load
anything, and stops at a 1FA: prompt (to which nothing can be typed).
Also, do I have to load the drivers for the serial ports, or is that
automatically
Well, I loaded Debian from floppy. However, while it boots from the boot
floppy fine, when I try to boot from the hd, it doesn't appear to load
anything, and stops at a 1FA: prompt (to which nothing can be typed).
Hm, to me it sounds like a problem with lilo. What does it say, if you
execute
Viola! Success. That was rather strange. After booting with the floppy,
I went and executed lilo like you said (actually I went to bin rather
than sbin, but it worked anyway), rebooted sans floppy, and it booted
without hesitation. What did I miss? At the end of the install, where
you were given a
I think my ppp crapped out on me while I was sending my last email. Here
it is again:---BeginMessage---
Viola! Success. That was rather strange. After booting with the floppy,
I went and executed lilo like you said (actually I went to bin rather
than sbin, but it worked anyway), rebooted sans
Thanks to all that offered suggestions on this one. For future use, I'm
posting below the solution that worked (quite nicely) for me, since it
wasn't posted previously.
Michael Stenner wrote (Wed, 19 Aug 1998 09:39:43 -0400
Following instructions I found on this list some time ago, I installed
hamm and win98 separately: each have their own drive - only one was
hooked up at a time. Than, I put both drives in: Linux as hda and win
as hdb. THis was nothing new for linux, so I started up linux and ran
lilo with the
On Wed 19 Aug 1998, Michael Stenner [EMAIL PROTECTED] wrote:
Following instructions I found on this list some time ago, I installed
hamm and win98 separately: each have their own drive - only one was
hooked up at a time. Than, I put both drives in: Linux as hda and win
as hdb. THis was
On Wed 19 Aug 1998, Michael Stenner [EMAIL PROTECTED] wrote:
Following instructions I found on this list some time ago, I installed
hamm and win98 separately: each have their own drive - only one was
hooked up at a time. Than, I put both drives in: Linux as hda and
win
as hdb. THis was
On 19 Aug 98 13:39:43 GMT, [EMAIL PROTECTED] wrote:
Following instructions I found on this list some time ago, I installed
hamm and win98 separately: each have their own drive - only one was
hooked up at a time. Than, I put both drives in: Linux as hda and win
as hdb. THis was nothing new for
On Tue, May 26, 1998 at 02:56:13PM -0400, Norbert Veber wrote:
On Tue, May 26, 1998 at 08:27:09PM +0200, Tomas Petersson wrote:
Hello, I have just installed Debian Linux, everything
went fine except I can't boot from the harddrive.
If I boot from the 'Custom Boot Floppy' it works,
but
On Wed, 27 May 1998, Hamish Moffatt wrote:
On Tue, May 26, 1998 at 02:56:13PM -0400, Norbert Veber wrote:
On Tue, May 26, 1998 at 08:27:09PM +0200, Tomas Petersson wrote:
Hello, I have just installed Debian Linux, everything
went fine except I can't boot from the harddrive.
If I boot
That is the wrong solution to the problem. Something is probably wrong
with lilo.conf, or the wrong partition is marked active, but changing
lilo.conf isn't the best solution.
As far as I can tell, the problem is with the boot disks, as it has happened
on 2 of my friends computers as well,
Hello, I have just installed Debian Linux, everything
went fine except I can't boot from the harddrive.
If I boot from the 'Custom Boot Floppy' it works,
but when I boot the harddrive I get the following
prompt: '2FA:', and nothing happens.
/Tomas Petersson
--
To UNSUBSCRIBE, email to [EMAIL
On Tue, May 26, 1998 at 08:27:09PM +0200, Tomas Petersson wrote:
Hello, I have just installed Debian Linux, everything
went fine except I can't boot from the harddrive.
If I boot from the 'Custom Boot Floppy' it works,
but when I boot the harddrive I get the following
prompt: '2FA:', and
301 - 400 of 420 matches
Mail list logo
