On 20 Jun 1997, Ben Gertzfield wrote:
Ah hah!
You have to re-build your kernel, unfortunately, The Deskpro series
have been known to be really sneaky about where they hide their BIOS
information.
My 1985 Compaq DeskPro 8086 had problems caused by a weird BIOS. It looks
like they haven't
Tried to install debian 1.3 from the TRI-Linux CD.
At some point during Linux loading, the system reboots and enters
an infinite cycle.
I have an Adaptec 2940U and tried to pass aic7xxx=no_reset
to the kernel, but I don't know what the kernel name is!
I tried:
boot: default aic7xxx=no_reset
None worked. Any idea how to get passed this hurdle?
Try 'linux'--you can probably find out for sure by hitting TAB.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
I'm guessing the kernel name is 'linux'. It's actaully the label name
in LILO, if you had a label ... otherwise it's the name of he image, I
believe. No matter, as you can hit the tab key at the boot prompt to
see a list of valid boot images.
However, I don't think your 2940U is the problem.
Nathan E Norman wrote:
I'm guessing the kernel name is 'linux'.
No matter, as you can hit the tab key at the boot prompt to
see a list of valid boot images.
I tried that, but it didn't work. Perhaps this hints to a bad image?
I'll try booting with the same diskette on another
Peter S Galbraith [EMAIL PROTECTED] writes:
The PC is a Compaq Deskpro 6000:
PPro 200, 64 MB
Adaptec 2940U SCSI (IRQ 11) w/ one 4.3 GB disk attached.
ATAPI PD-CD (The CD shows up as /dev/hdc on Slackware)
Matrox Millenium graphics card, IRQ11
SMC EtherPower 10/100 (Tulip-based)
Ben Gertzfield wrote:
The PC is a Compaq Deskpro 6000:
PPro 200, 64 MB
Adaptec 2940U SCSI (IRQ 11) w/ one 4.3 GB disk attached.
ATAPI PD-CD (The CD shows up as /dev/hdc on Slackware)
Matrox Millenium graphics card, IRQ11
SMC EtherPower 10/100 (Tulip-based) Ethernet card.
--- Peter S Galbraith wrote:
However, I don't think your 2940U is the problem. The no_reset
parameter is to prevent the HBA from resetting the SCSI bus, which it
does by default to allow all the SCSI devices on the bus to initialise.
Then I don't need the `linux' label anyway.
...
The last
Joost Kooij wrote:
Building a kernel with exact
support for your hardware might get you `over the hill'.
Just include support for all you need plus ramdisk and initrd support for
the installation rootdisk. Can't remember if a 'rdev /dev/ramdisk' is
9 matches
Mail list logo
