Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*mkinitrd\,\s+ramdisk\s+failure\?\s*$/: 78 ]

Total 78 documents matching your query.

1. mkinitrd, ramdisk failure? (score: 1)
Author: "D. Stimits" <stimits@xxxxxxxxxx>
Date: Tue, 12 Jun 2001 17:29:33 -0600
I am trying to take what is very close to my working kernel configuration, and change it around slightly so that ramdisk and modules are used for the XFS related items. The reason being that with the
/archives/xfs/2001-06/msg00413.html (10,405 bytes)

2. Re: mkinitrd, ramdisk failure? (score: 1)
Author: Juha Saarinen <juha@xxxxxxxxxxxx>
Date: Wed, 13 Jun 2001 12:31:36 +1200 (NZST)
Try compiling SCSI as modules instead -- that's what I've got here, and it works (Tekram controller plus two drives). Mkinitrd looks for the SCSI modules to put into the initial RAM disk image, so yo
/archives/xfs/2001-06/msg00418.html (10,373 bytes)

3. Re: mkinitrd, ramdisk failure? (score: 1)
Author: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>
Date: Wed, 13 Jun 2001 10:44:08 +1000
Probably because the XFS module has not been loaded. Did it ask for the second floppy? I am not familiar with two floppy boots but I think you need prompt_ramdisk=1 with the kernel on the first disk
/archives/xfs/2001-06/msg00420.html (9,698 bytes)

4. Re: mkinitrd, ramdisk failure? (score: 1)
Author: "D. Stimits" <stimits@xxxxxxxxxx>
Date: Tue, 12 Jun 2001 19:47:18 -0600
That's the interesting part. The bootup shows that it booted /boot/, and all scsi was detected and loaded. It was mounting of the root partition (/boot is ext2, root is xfs) where it failed, due to l
/archives/xfs/2001-06/msg00425.html (12,553 bytes)

5. Re: mkinitrd, ramdisk failure? (score: 1)
Author: "D. Stimits" <stimits@xxxxxxxxxx>
Date: Tue, 12 Jun 2001 19:47:22 -0600
To clarify, this is a lilo install to the hard drive. But I want it to work correctly prior to trying to make a floppy. In the bad old days, such as when I played with slackware and 1.0.9 kernel, flo
/archives/xfs/2001-06/msg00426.html (10,529 bytes)

6. Re: mkinitrd, ramdisk failure? (score: 1)
Author: Walt H <waltabbyh@xxxxxxxxxx>
Date: Tue, 12 Jun 2001 19:13:50 -0700
I'm not all that familiar with mkinitrd.xfs as I use the standard "unpatched" mkinitrd under Mandrake 8.0 Does it need the --preload switches to preload the appropriate modules in order for XFS to w
/archives/xfs/2001-06/msg00428.html (14,924 bytes)

7. Re: mkinitrd, ramdisk failure? (score: 1)
Author: "D. Stimits" <stimits@xxxxxxxxxx>
Date: Tue, 12 Jun 2001 21:04:25 -0600
While I'm convinced that this is the basic problem, I can't figure out what is missing. Matt Ryan gave me one very useful command to mount my initial ramdisk on loopback and see what it actually cont
/archives/xfs/2001-06/msg00432.html (15,788 bytes)

8. Re: mkinitrd, ramdisk failure? (score: 1)
Author: Matt Ryan <matt@xxxxxxxxxxxxxxxx>
Date: Tue, 12 Jun 2001 20:23:39 -0700
gzip -dc your.img > somefile mount -o loop somefile somedir also, just running mkinitrd with the verbose (-v) option is pretty helpful too (not sure if you were doing that already). Matt
/archives/xfs/2001-06/msg00433.html (9,206 bytes)

9. Re: mkinitrd, ramdisk failure? (score: 1)
Author: "D. Stimits" <stimits@xxxxxxxxxx>
Date: Tue, 12 Jun 2001 21:54:07 -0600
I've done -v, and also mounted each of the initrd images since then. I definitely have the three modules I know of which are required: pagebuf.o xfs.o xfs_support.o Perhaps there is some kind of argu
/archives/xfs/2001-06/msg00435.html (10,763 bytes)

10. Re: mkinitrd, ramdisk failure? (score: 1)
Author: Russell Cattelan <cattelan@xxxxxxxxxxx>
Date: Tue, 12 Jun 2001 23:45:05 -0500
note the modules must load in this order pagebuf xfs_support xfs When specifying them on the command the order they are given is the order they are loaded. The mkinird.xfs in the source tree just add
/archives/xfs/2001-06/msg00436.html (11,979 bytes)

11. Re: mkinitrd, ramdisk failure? (score: 1)
Author: Seth Mos <knuffie@xxxxxxxxx>
Date: Wed, 13 Jun 2001 07:16:33 +0200 (CEST)
There is a entry and link in the faq to make mkbootdisk format larger floppy's. If you do that you can compile both xfs and your scsi driver in. I use 1.68MB boot floppy's for my servers at work. The
/archives/xfs/2001-06/msg00437.html (9,918 bytes)

12. Re: mkinitrd, ramdisk failure? (score: 1)
Author: Sidik Isani <isani@xxxxxxxxxxxxxxx>
Date: Wed, 13 Jun 2001 11:37:09 -1000 (HST)
D. Stimits typed: I've never looked at mkinitrd, but XFS as modules is working for me. I generated the initrd manually, but there's nothing fancy in it. As someone else just posted, the modules must
/archives/xfs/2001-06/msg00467.html (9,707 bytes)

13. Re: mkinitrd, ramdisk failure? (score: 1)
Author: "D. Stimits" <stimits@xxxxxxxxxx>
Date: Wed, 13 Jun 2001 15:57:11 -0600
I just tested a very carefully made initial ramdisk, and it fails: mkinitrd.xfs \ --with=pagebuf \ --with=xfs_support \ --with=xfs \ /boot/initrd-2.4.6-pre1-xfs-3.img \ 2.4.6-pre1-xfs-3 My lilo.conf
/archives/xfs/2001-06/msg00468.html (10,468 bytes)

14. Re: mkinitrd, ramdisk failure? (score: 1)
Author: "D. Stimits" <stimits@xxxxxxxxxx>
Date: Wed, 13 Jun 2001 16:01:25 -0600
I carefully made certain this was the order in the mkinitrd.xfs. It still fails at the point of mounting root partition (note: this is a hard drive, not floppy). There must be something else? My comm
/archives/xfs/2001-06/msg00469.html (13,331 bytes)

15. Re: mkinitrd, ramdisk failure? (score: 1)
Author: Chris Pascoe <c.pascoe@xxxxxxxxxxxxxx>
Date: Thu, 14 Jun 2001 08:37:36 +1000 (EST)
I don't believe the read of /boot isn't done using the system SCSI modules; it's done using BIOS calls. So that it loads the kernel and initrd is not an indication that the SCSI drivers, etc, actual
/archives/xfs/2001-06/msg00471.html (11,689 bytes)

16. Re: mkinitrd, ramdisk failure? (score: 1)
Author: Chris Pascoe <c.pascoe@xxxxxxxxxxxxxx>
Date: Thu, 14 Jun 2001 08:39:18 +1000 (EST)
If you've got KDB support built in, can you hit the break key to enter it, and do an "lsmod" at this point? It should tell you what modules are loaded? Keith, correct me if I am wrong.. Chris
/archives/xfs/2001-06/msg00473.html (9,590 bytes)

17. Re: mkinitrd, ramdisk failure? (score: 1)
Author: "D. Stimits" <stimits@xxxxxxxxxx>
Date: Wed, 13 Jun 2001 18:38:14 -0600
I have not used KDB yet, it looks like I'll need to. But, say for the moment I do have KDB. "lsmod" is on the root partition, and uses libc which is also on the root partition. Would enabling KDB hel
/archives/xfs/2001-06/msg00475.html (9,955 bytes)

18. Re: mkinitrd, ramdisk failure? (score: 1)
Author: "D. Stimits" <stimits@xxxxxxxxxx>
Date: Wed, 13 Jun 2001 18:57:51 -0600
Ok, I did some experimenting. Background first: my /boot/ is the first partition; it is ext2; ext2 is compiled in. The test: I went ahead and made all scsi become a module. Voila, you were correct, r
/archives/xfs/2001-06/msg00476.html (16,010 bytes)

19. Re: mkinitrd, ramdisk failure? (score: 1)
Author: Sebastian Dransfeld <sebastid@xxxxxxxxxxxx>
Date: Thu, 14 Jun 2001 02:57:08 +0200 (MET DST)
Compile a static version of lsmod. Sebastian
/archives/xfs/2001-06/msg00477.html (10,237 bytes)

20. Re: mkinitrd, ramdisk failure? (score: 1)
Author: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>
Date: Thu, 14 Jun 2001 11:19:37 +1000
kdb has a built in lsmod command, no need for the root filesystem.
/archives/xfs/2001-06/msg00478.html (9,530 bytes)


This search system is powered by Namazu