Previously Steve Dunham wrote:
The only isapnp devices I know of are audio. Are there any SCSI or
enet devices? (If so a table would be necessary as they are discovered.)
Yes, my adaptec 152x card is PnP. hint: don't use isapnp after booting
from a PnP scsi-card!
Wichert.
--
On Thu, Jun 11, 1998 at 06:10:16PM -0500, Martin Alonso Soto Jacome wrote:
Steve Dunham [EMAIL PROTECTED] wrote:
The only isapnp devices I know of are audio. Are there any SCSI or
enet devices? (If so a table would be necessary as they are discovered.)
Yes, a lot of modern soundcards
On Thu, 11 Jun 1998, Hamish Moffatt wrote:
On Wed, Jun 10, 1998 at 09:17:20PM -0600, Jason Gunthorpe wrote:
When you boot the kernel it copies the Image from the disk to 0x1000
(about 64k). If the Image is beyond 600k then you have a problem because
it suddenly will not all fit in low
Quoting Dale Scheetz ([EMAIL PROTECTED]):
Another solution is the one that slackware provides. They build a bunch
of kernels, each one for a specific hardware configuration (broad enought
to cover a range of hardware, and chosen to keep incopatibly drivers out
of the picture {like the wd9000
On Thu, Jun 11, 1998 at 09:41:03AM -0400, Dale Scheetz wrote:
The problem is that the Debian installation kernel tries to be all things
to all people. As there are machines that boot from SCSI drives, it was
necessary to have all the scsi controlers built in to the kernel, hense
its large
On Thu, Jun 11, 1998 at 03:13:37PM +0100, Enrique Zanardi wrote:
Using initrd, our default kernel may be reduced to half its current size,
as all those different controllers may be built as modules and only the
required ones will be loaded at boot time. That will save our users a few
hundred
On Fri, Jun 12, 1998 at 12:25:59AM +1000, Hamish Moffatt wrote:
On Thu, Jun 11, 1998 at 03:13:37PM +0100, Enrique Zanardi wrote:
Using initrd, our default kernel may be reduced to half its current size,
as all those different controllers may be built as modules and only the
required ones
On Thu, 11 Jun 1998, Enrique Zanardi wrote:
On Thu, Jun 11, 1998 at 09:41:03AM -0400, Dale Scheetz wrote:
The problem is that the Debian installation kernel tries to be all things
to all people. As there are machines that boot from SCSI drives, it was
necessary to have all the scsi
Dale Scheetz [EMAIL PROTECTED] wrote:
I have wondered why we didn't try this once the kernel supported initrd.
To be honest I haven't figured out yet how to do the device selection,
other than going through a list of drivers, trying to insmod each one
until you are successful.
Wouldn't PCI
On Thu, Jun 11, 1998 at 11:45:56AM -0500, Martin Alonso Soto Jacome wrote:
Dale Scheetz [EMAIL PROTECTED] wrote:
I have wondered why we didn't try this once the kernel supported initrd.
To be honest I haven't figured out yet how to do the device selection,
other than going through a list of
On Thu, Jun 11, 1998 at 09:41:03AM -0400, Dale Scheetz wrote:
The problem is that the Debian installation kernel tries to be all things
to all people. As there are machines that boot from SCSI drives, it was
necessary to have all the scsi controlers built in to the kernel, hense
its large
On Thu, Jun 11, 1998 at 10:02:21AM -0400, Avery Pennarun wrote:
This is, if I recall, exactly what initrd was made for. Your bootloader
(eg. lilo) loads an initial ramdisk containing all the kernel modules you
might need. An init script on the ramdisk loads the right modules (however
you
Dale Scheetz [EMAIL PROTECTED] writes:
On Thu, 11 Jun 1998, Enrique Zanardi wrote:
On Thu, Jun 11, 1998 at 09:41:03AM -0400, Dale Scheetz wrote:
The problem is that the Debian installation kernel tries to be all things
to all people. As there are machines that boot from SCSI drives, it
Enrique Zanardi [EMAIL PROTECTED] writes:
On Thu, Jun 11, 1998 at 11:45:56AM -0500, Martin Alonso Soto Jacome wrote:
Dale Scheetz [EMAIL PROTECTED] wrote:
I have wondered why we didn't try this once the kernel supported initrd.
To be honest I haven't figured out yet how to do the device
14 matches
Mail list logo
