Sorry for the re-post, I left the subject blank the first time I sent this
message...
Perhaps his /boot was simply full? There were an awful lot of modules
listed. Butwouldn't it be simpler to just compile the stuff in and
be done with it? I mean, I understand why the installation kernel
Hi,
I wrote:
>>>CONFIG_BLK_DEV_IDEDISK=m
>>># CONFIG_IDEDISK_MULTI_MODE is not set
>>
>>
>> With this, the kernel can't even load the initrd, as it is on a disk.
>
>Wrong. PROM calls allow SILO to load the initrd from the disk into
>memory, just as it does with the kernel. That is the whole po
Hi,
you should compile the IDE disk stuff directly into the kernel, Ultra-5's
are IDE based:
[del]
>CONFIG_BLK_DEV_IDEDISK=m
># CONFIG_IDEDISK_MULTI_MODE is not set
With this, the kernel can't even load the initrd, as it is on a disk.
[del]
This should also be compiled in:
>CONFIG_IDE_GENERIC
Ulrich Teichert wrote:
CONFIG_BLK_DEV_IDEDISK=m
# CONFIG_IDEDISK_MULTI_MODE is not set
With this, the kernel can't even load the initrd, as it is on a disk.
Wrong. PROM calls allow SILO to load the initrd from the disk into
memory, just as it does with the kernel. That is the whole point of
Joshua Kwan wrote:
> Daniel E. Jonsen wrote:
> > Allocated 8 Megs of memory at 0x4000 for kernel
> > Uncompressing image...
> > Loaded kernel version 2.6.8
> > Error: initial ramdisk loading failed. No initrd will be used.
>
> Well hello there!
>
> Does this happen when booting the Debian
Daniel E. Jonsen wrote:
Allocated 8 Megs of memory at 0x4000 for kernel
Uncompressing image...
Loaded kernel version 2.6.8
Error: initial ramdisk loading failed. No initrd will be used.
Well hello there!
Does this happen when booting the Debian kernel, too? That would be your
problem.
B
Joshua Kwan wrote:
Is there a way I can copy/paste these messages? I used a good old
fashioned pen and paper to write down the last six lines. I really would
like to avoid using this method for the whole boot sequence, which is
about 50 lines.
You can use a serial console. Discussing how t
Daniel E. Jonsen wrote:
Is there a way I can copy/paste these messages? I used a good old fashioned
pen and paper to write down the last six lines. I really would like to avoid
using this method for the whole boot sequence, which is about 50 lines.
You can use a serial console. Discussing ho
Joshua Kwan wrote:
> > NET: Registered protocol family 1
> > NET: Registered protocol family 17
> > VFS: Cannot open root device "hda2" or unknown-block(0,0)
> > Please append a correct "root=" boot option
> > Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
> > <0>Press L1-A to re
Daniel E. Jonsen wrote:
I have an Ultra5 that I've been running Sarge (testing - official snapshot
11/07/04, kernel 2.4.27). I downloaded and installed
kernel-image-2.6.8-1-sparc64_2.6.8-5_sparc.deb, and also the corresponding
source deb. I compiled my own custom 2.6.8 kernel and installed i
I have an Ultra5 that I've been running Sarge (testing - official snapshot
11/07/04, kernel 2.4.27). I downloaded and installed
kernel-image-2.6.8-1-sparc64_2.6.8-5_sparc.deb, and also the corresponding
source deb. I compiled my own custom 2.6.8 kernel and installed it. Both of
the 2.6.8 k
11 matches
Mail list logo
