Hi Mark,
I didn't feel right about putting untested code up for the innocent to
trip over, particularly newcomers, so I decided to try booting the
bootdisk I created by recompiling with scsi enabled (I only have scsi
drives). I experienced some errors with the ramdisk, as I feared might
Hi Mark,
I have some good news, and I have some bad news.
THe good news first. I do have a boot disk for you. (details below)
THe bad news is that since I'm removing scsi support (this was reported
to be the problem, see
http://www.debian.org/Lists-Archives/debian-user-9810/msg03176.html
The only lead I had to a location for slink 1440 floppy images gives
an error now. Maybe someone else will come up with a URL.
I'm afraid you will probably need someone with more in-depth knowledge
than me to solve the problem.
John
Mark Weston wrote:
On 10 Dec 98, at 11:17, John C.
On 12 Dec 98, at 10:24, David Stern wrote:
Yes, I was trying again last nigt, and waited for 20 minutes or so
without result. And the Master/Slave jumpers are definitely configured
correctly.
I thought of something the other day.. umm.. I know it's generally
considered somewhat of a
Hi Robert Vollmert; unless Mutt is confused, you wrote:
The installation (CD or rescue floppy) loads the Linux kernel, and during
the
long series of hardware detection messages, successfully detects all the
IDE
devices and then hangs on the line.
md driver 0.35 MAX_MD_DEV=4
On 10 Dec 98, at 10:23, David Stern wrote:
I tried booting with SoundBlaster, CD-ROM and SyJet disabled, but it
seem to help. And all the devices work fine under another O/S (that
speak its name on this list), so I don't think the actual hardware's
You'll find the Debianeers have a
On 10 Dec 98, at 11:17, John C. Ellingboe wrote:
Look at the message just before the md driver message for the
problem. It will probably turn out to be the disk controler doesn't
like being probed at boot time and is locking up. Some systems will
require an entry on the boot line or use the
Look at the message just before the md driver message for the
problem. It will probably turn out to be the disk controler doesn't
like being probed at boot time and is locking up. Some systems will
require an entry on the boot line or use the tecra rescue disk like the
lap top systems
On 9 Dec 98, at 0:12, David Stern wrote:
I searched the kernel sources and I found this is the multiple
devices driver. That handles disk striping (RAID 0), RAID 5, etc.
I have never heard of this problem, nor do I have any insight as to
what might cause this error. I was taught to
I searched the kernel sources and I found this is the multiple
devices driver. That handles disk striping (RAID 0), RAID 5, etc.
I have never heard of this problem, nor do I have any insight as to
what might cause this error. I was taught to disconnect unnecessary
devices when things
At 11:13 AM 12/10/1998 -0500, Tun Yang wrote:
This is not related to this problem, but I thought I'd just throw in some
ideas...
I have an Adaptec 2940UW, and when I upgraded my motherboard and cpu, I put
it in PCI slot #1. Debian cd boot up hung somewhere. (I think at the scsi
init area). That
Kent West wrote:
At 11:13 AM 12/10/1998 -0500, Tun Yang wrote:
This is not related to this problem, but I thought I'd just throw in some
ideas...
I have an Adaptec 2940UW, and when I upgraded my motherboard and cpu, I put
it in PCI slot #1. Debian cd boot up hung somewhere. (I think at the
Not sure what the original post is, but you might want to check the MB
compatibility HOWTO. I had a SuperMicro P5MMA98 board and I found out that
it had a BIOS glitch that pissed Linux off. I was able to download a flash
upgrade and then Linux installed perfectly.
- Joe
BEGIN:VCARD
VERSION:2.1
On Tue, 08 Dec 1998 23:48:07 GMT, Mark Weston wrote:
Hi,
I've been trying my first ever Linux installation from a Debian 2.0 CD,
and have run into problems which are beyond me at the moment. I'd be
really grateful for some help.
The installation (CD or rescue floppy) loads the Linux
The installation (CD or rescue floppy) loads the Linux kernel, and during the
long series of hardware detection messages, successfully detects all the IDE
devices and then hangs on the line.
md driver 0.35 MAX_MD_DEV=4 MAX_REAL=8
I have almost the same problem on my similar machine: When
15 matches
Mail list logo
