David Wright writes:
> You presumably aren't running 686 and amd64 kernels, then,
> unlike Felix.
It depends on the system too. My amd64 based router doesn't have
microcode in the initramfs but that's OK since microcode is handled by
the BIOS (Coreboot). Also I think the microcode's not free to
David Wright composed on 2023-02-04 22:43 (UTC-0600):
> The other problem for your initrds is that both the amdgpu and radeon
> directories are being included, presumably because, according to your
> dracut post, both the amdgpu.ko and radeon.ko modules are included
> (and I think you implied they
On Sat 04 Feb 2023 at 18:04:21 (-0500), Felix Miata wrote:
> David Wright composed on 2023-02-04 10:59 (UTC-0600):
>
> > I don't yet know which directories are being included in yours.
>
> 6 instances of lsinitramfs, with and without -l for 3 kernels:
>
> # initrd.img-5.17.0-1-amd64; gzip bytes:
David Wright composed on 2023-02-04 10:59 (UTC-0600):
> I don't yet know which directories are being included in yours.
6 instances of lsinitramfs, with and without -l for 3 kernels:
# initrd.img-5.17.0-1-amd64; gzip bytes:7,649,297; lines:445:
https://termbin.com/2o3z https://paste.debian.net/1
On Sat 04 Feb 2023 at 11:53:36 (-0500), Stefan Monnier wrote:
> > I'm guessing his machine has no microcode installed, since that's what
> > my first archive contains. Whether that's because his machine is so
> > old that it doesn't *need* any, or because he just lives dangerously,
> > I cannot sa
On Fri 03 Feb 2023 at 01:45:33 (-0500), Felix Miata wrote:
> David Wright composed on 2023-02-01 22:39 (UTC-0600):
> > On Wed 01 Feb 2023 at 00:50:07 (-0500), Felix Miata wrote:
>
> >> I think 6.0's is smaller because that upgrade cycle is when I installed
> >> zstd
> >> before the newer kernel.
> I'm guessing his machine has no microcode installed, since that's what
> my first archive contains. Whether that's because his machine is so
> old that it doesn't *need* any, or because he just lives dangerously,
> I cannot say. :-)
None of my ARM machines have a microcode update in their initr
On Sat, Feb 04, 2023 at 10:38:12AM -0600, David Wright wrote:
> Sure, I knew that. The problem was that AFAICT, Felix's
> initrd had no first, uncompressed cpio, archive, so
> $ cpio -t < /boot/initrd.img-6.0.0-6-amd64
> immediately ran into the compressed, main archive. That
> took me by surprise
On Fri 03 Feb 2023 at 20:34:55 (-0500), Greg Wooledge wrote:
> On Fri, Feb 03, 2023 at 06:45:14PM -0600, David Wright wrote:
> > It's useful, as seen in my post, to skip past the early archive in
> > order to see how the main archive has been compressed.
>
> If you want to see the contents of the *
Felix Miata composed on 2022-11-12 01:57 (UTC-0500):
> # grep MODULES= /etc/initramfs-tools/initramfs.conf
> MODULES=dep
> # ls -Ggh /boot/initrd.img-[5,6]*
> -rw-r--r-- 1 6.8M May 8 2022 /boot/initrd.img-5.17.0-1-686
> -rw-r--r-- 1 31M Aug 2 03:06 /boot/initrd.img-5.18.0-3-686
> -rw-r--r-- 1
On Fri, Feb 03, 2023 at 06:45:14PM -0600, David Wright wrote:
> It's useful, as seen in my post, to skip past the early archive in
> order to see how the main archive has been compressed.
If you want to see the contents of the *second* archive in the initrd,
you have to call cpio a second time.
On Fri 03 Feb 2023 at 07:49:39 (-0500), Greg Wooledge wrote:
> On Fri, Feb 03, 2023 at 01:45:33AM -0500, Felix Miata wrote:
> > David Wright composed on 2023-02-01 22:39 (UTC-0600):
> > > $ cpio -t < /boot/initrd.img-6.0.0-6-amd64
> >
> > Is that a typo? I copied & pasted that and the screen loa
On 2023-02-03 at 09:57, Felix Miata wrote:
> The Wanderer composed on 2023-02-03 07:16 (UTC-0500):
>
>> FTLIW, my own primary desktop has an AMD graphics card (and has since
>> before the initial Debian install), and doesn't have these large
>> initrds:
>
> Oh, but it does
>
>> $ lh /boot/
The Wanderer composed on 2023-02-03 07:16 (UTC-0500):
> FTLIW, my own primary desktop has an AMD graphics card (and has since
> before the initial Debian install), and doesn't have these large
> initrds:
Oh, but it does
> $ lh /boot/initrd.img-*
> -rw-r--r-- 1 root root 36M Sep 2 08:27 /bo
Hi,
David Wright wrote:
> > > $ cpio -t < /boot/initrd.img-6.0.0-6-amd64
Felix Miata wrote:
> > Is that a typo? I copied & pasted that and the screen loaded binary
> > gibberish.
Greg Wooledge wrote:
> GNU cpio(1) says that -t implies -i, so it should work on Debian.
Probably the initrd is co
On Fri, Feb 03, 2023 at 01:45:33AM -0500, Felix Miata wrote:
> David Wright composed on 2023-02-01 22:39 (UTC-0600):
> > $ cpio -t < /boot/initrd.img-6.0.0-6-amd64
>
> Is that a typo? I copied & pasted that and the screen loaded binary gibberish.
GNU cpio(1) says that -t implies -i, so it shoul
On 2023-02-03 at 01:45, Felix Miata wrote:
> David Wright composed on 2023-02-01 22:39 (UTC-0600):
>> FTR, I reinstalled 5.10.0-21-amd64 on another machine with MODULES=dep
>> and for comparison (initrd only):
>
>> $ unmkinitramfs /boot/initrd.img-5.10.0-21-amd64 /tmp/unpacked10-21
>> cpio: et
David Wright composed on 2023-02-01 22:39 (UTC-0600):
> On Wed 01 Feb 2023 at 00:50:07 (-0500), Felix Miata wrote:
>> I think 6.0's is smaller because that upgrade cycle is when I installed zstd
>> before the newer kernel. It's specified by default in initramfs.conf, but the
>> upgrades from 11 t
The Wanderer composed on 2022-11-13 06:54 (UTC-0500):
> On 2022-11-12 Felix Miata wrote:
>> # grep MODULES= /etc/initramfs-tools/initramfs.conf
>> MODULES=dep
>> # ls -Ggh /boot/initrd.img-[5,6]*
>> -rw-r--r-- 1 6.8M May 8 2022 /boot/initrd.img-5.17.0-1-686
>> -rw-r--r-- 1 31M Aug 2 03:06 /bo
On Wed 01 Feb 2023 at 00:50:07 (-0500), Felix Miata wrote:
> David Wright composed on 2023-01-31 22:56 (UTC-0600):
> > On Tue 31 Jan 2023 at 18:31:15 (-0500), Felix Miata wrote:
> >> David Wright composed on 2023-01-28 09:10 (UTC-0600):
> >>> On Sat 28 Jan 2023 at 03:15:11 (-0500), Felix Miata wrot
David Wright composed on 2023-01-31 22:56 (UTC-0600):
> On Tue 31 Jan 2023 at 18:31:15 (-0500), Felix Miata wrote:
>> David Wright composed on 2023-01-28 09:10 (UTC-0600):
>>> On Sat 28 Jan 2023 at 03:15:11 (-0500), Felix Miata wrote:
I thought only Windows was like that, but apparently n
On Tue 31 Jan 2023 at 18:31:15 (-0500), Felix Miata wrote:
> David Wright composed on 2023-01-28 09:10 (UTC-0600):
> > On Sat 28 Jan 2023 at 03:15:11 (-0500), Felix Miata wrote:
>
> >> I thought only Windows was like that, but apparently not always. I keep my
> >> initramfs configuration set to =d
David Wright composed on 2023-01-28 09:10 (UTC-0600):
> On Sat 28 Jan 2023 at 03:15:11 (-0500), Felix Miata wrote:
>> I thought only Windows was like that, but apparently not always. I keep my
>> initramfs configuration set to =dep.
> And is that the reason behind, and cure for, your mushroomin
On Sun 13 Nov 2022 at 06:54:47 (-0500), The Wanderer wrote:
> On 2022-11-12 at 01:57, Felix Miata wrote:
>
> > # grep MODULES= /etc/initramfs-tools/initramfs.conf
> > MODULES=dep
> > # ls -Ggh /boot/initrd.img-[5,6]*
> > -rw-r--r-- 1 6.8M May 8 2022 /boot/initrd.img-5.17.0-1-686
> > -rw-r--r-- 1
On Sat 12 Nov 2022 at 01:57:51 (-0500), Felix Miata wrote:
> # grep MODULES= /etc/initramfs-tools/initramfs.conf
> MODULES=dep
> # ls -Ggh /boot/initrd.img-[5,6]*
> -rw-r--r-- 1 6.8M May 8 2022 /boot/initrd.img-5.17.0-1-686
> -rw-r--r-- 1 31M Aug 2 03:06 /boot/initrd.img-5.18.0-3-686
> -rw-r--r
On 2022-11-12 at 01:57, Felix Miata wrote:
> # grep MODULES= /etc/initramfs-tools/initramfs.conf
> MODULES=dep
> # ls -Ggh /boot/initrd.img-[5,6]*
> -rw-r--r-- 1 6.8M May 8 2022 /boot/initrd.img-5.17.0-1-686
> -rw-r--r-- 1 31M Aug 2 03:06 /boot/initrd.img-5.18.0-3-686
> -rw-r--r-- 1 31M Sep 3
On Sat 12 Nov 2022 at 01:57:51 (-0500), Felix Miata wrote:
> # grep MODULES= /etc/initramfs-tools/initramfs.conf
> MODULES=dep
> # ls -Ggh /boot/initrd.img-[5,6]*
> -rw-r--r-- 1 6.8M May 8 2022 /boot/initrd.img-5.17.0-1-686
> -rw-r--r-- 1 31M Aug 2 03:06 /boot/initrd.img-5.18.0-3-686
> -rw-r--r
>> > Hm. Apt-file search says (Buster) that /usr/bin/lsinitrd is in package
>> > dracut-core (not installed in my box, so I can't double check now).
>> initramfs-tools-core: /usr/bin/lsinitramfs
Apparently `lsinitrd` only lists the contents of the first archive,
whereas `lsinitramfs` lists the con
Curt composed on 2020-11-23 12:39 (UTC):
> tomas wrote:
>> The initramfs is a compressed cpio archive (of the initial file
>> system at boot time). You can inspect it like so:
>> gunzip < /boot/initrd.img-4.19.0-10-amd64 | cpio -it | less
> lsinitramfs /boot/initrd.img-4.19.0-10-amd64
If
On Mon, Nov 23, 2020 at 12:19:02PM +0100, Sven Hartge wrote:
> to...@tuxteam.de wrote:
> > On Mon, Nov 23, 2020 at 01:36:05AM -0500, Felix Miata wrote:
> >> Tomas composed on 2020-11-21 22:46 (UTC+0100):
>
> >>> You can inspect it like so:
> >>
> >>> gunzip < /boot/initrd.img-4.19.0-10-amd64 |
to...@tuxteam.de wrote:
> On Mon, Nov 23, 2020 at 01:36:05AM -0500, Felix Miata wrote:
>> Tomas composed on 2020-11-21 22:46 (UTC+0100):
>>> You can inspect it like so:
>>
>>> gunzip < /boot/initrd.img-4.19.0-10-amd64 | cpio -it | less
>> That was shortened to 'lsinitrd | less' in 2008 in o
On Mon, Nov 23, 2020 at 01:36:05AM -0500, Felix Miata wrote:
> Tomas composed on 2020-11-21 22:46 (UTC+0100):
>
> > You can inspect it like so:
>
> > gunzip < /boot/initrd.img-4.19.0-10-amd64 | cpio -it | less
>
> That was shortened to 'lsinitrd | less' in 2008 in openSUSE[1],
> which
> Mand
Tomas composed on 2020-11-21 22:46 (UTC+0100):
> You can inspect it like so:
> gunzip < /boot/initrd.img-4.19.0-10-amd64 | cpio -it | less
That was shortened to 'lsinitrd | less' in 2008 in openSUSE[1],
which
Mandriva already had, eventually upstream'd to dracut, I'm guessing well over 5
yea
Hello,
i was also fighting with the same issue after upgrading to newer kernel.
The wiki
https://wiki.debian.org/Keyboard#How_to_enable_USB_keyboard_in_initramfs
helped me to figure out the problem. In short:
1. identify all kernel modules your USB keyboard is using/depends on
2. add those modules
> From: deb...@alexkretschmer.de
> Date: Fri, 10 Jul 2015 14:44:14 +0200
>
> Hello,
> I have a system running raid1, dmcrypt and lvm2.
> Debian Version is jessie / stable
> My disks have a small partition for boot, the rest ist encrypted incl. the
> system.
> Therefore I'm forced to work with an
Hugo Vanwoerkom wrote:
Johann Spies wrote:
According to the kernel-package README.gz one can use the following
command to compile a kernel with an initrd.img:
$Get_Root make-kpkg --initrd --revision=3:custom.2.0 kernel_image
In the past I could compile a kernel like that and when I install the
Johann Spies wrote:
According to the kernel-package README.gz one can use the following
command to compile a kernel with an initrd.img:
$Get_Root make-kpkg --initrd --revision=3:custom.2.0 kernel_image
In the past I could compile a kernel like that and when I install the
package an initrd image
On Aug 27, 12:20 pm, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> I install debian-40r4a in VMware on one machine and upgrade the kernel
> from 2.6.18-6-686 to 2.6.26.3. I don't make an initrd image and
> comment the initrd line in grub's menu.lst file. I can boot the new
> 2.6.26 kernel and th
On Aug 27, 12:20 pm, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> I install debian-40r4a in VMware on one machine and upgrade the kernel
> from 2.6.18-6-686 to 2.6.26.3. I don't make an initrd image and
> comment the initrd line in grub's menu.lst file. I can boot the new
> 2.6.26 kernel and th
On 27 Feb at 11:34 George <[EMAIL PROTECTED]> wrote in message
<[EMAIL PROTECTED]>
> Tony van der Hoff wrote:
> > Hi,
>>
> > I've just built a 2.6.18-6-686 kernel, using the etch configure as the
> > base, and following the instructions in the kernel source README.
>>
> > Do I additionally need
Tony van der Hoff wrote:
Hi,
I've just built a 2.6.18-6-686 kernel, using the etch configure as the base,
and following the instructions in the kernel source README.
Do I additionally need to make an initrd for it to boot?
NO. As long as you have everything you need.
--
To UNSUBSCRIBE, e
After flogging this for a while, I traced it down to my cpio format. I
was using the old POSIX format. I switched to newc, and things worked fine.
--
-- Skylar Thompson ([EMAIL PROTECTED])
-- http://www.cs.earlham.edu/~skylar/
signature.asc
Description: OpenPGP digital signature
On Tue, Jan 03, 2006 at 02:45:26PM -0500, Joey Hess wrote:
> J.F. Gratton wrote:
> > - I know my hardware, it's unlikely to change in a near-future; a new
> > kernel is more likely to come out thant my hardware to change; why using
> > an initrd then if I know exactly what needs to be put in module
On Tue, Jan 03, 2006 at 02:45:26PM -0500, Joey Hess wrote:
> J.F. Gratton wrote:
> > - I know my hardware, it's unlikely to change in a near-future; a new
> > kernel is more likely to come out thant my hardware to change; why using
> > an initrd then if I know exactly what needs to be put in module
John Hasler wrote:
Joey Hess writes:
This assumes a best case scenario that you will never need to get some
new peice of hardware working at a time when taking the time out to set
up a new kernel will be painful.
You seem to be equating initrd to modular kernel. I have the drivers for
my
Joey Hess writes:
> This assumes a best case scenario that you will never need to get some
> new peice of hardware working at a time when taking the time out to set
> up a new kernel will be painful.
You seem to be equating initrd to modular kernel. I have the drivers for
my present hardware comp
On Tue, 2006-01-03 at 14:45 -0500, Joey Hess wrote:
> J.F. Gratton wrote:
> > - I know my hardware, it's unlikely to change in a near-future; a new
> > kernel is more likely to come out thant my hardware to change; why using
> > an initrd then if I know exactly what needs to be put in modules and
>
J.F. Gratton wrote:
> - I know my hardware, it's unlikely to change in a near-future; a new
> kernel is more likely to come out thant my hardware to change; why using
> an initrd then if I know exactly what needs to be put in modules and
> must not ?
This assumes a best case scenario that you will
Ignore my last mail.
Ironic, 2 days troubleshooting and 2h after mailing this list and the
problem solves. ;)
FYI, according to Documentation/initrd.txt you should(?) have a pivot_root
and a chroot in your /linuxrc (initrd-image). This is not so, works better
without them. The kernel alre
On Monday 22 November 2004 07:06, Brian Coiley wrote:
> Hi all.
>
> As a complete newbie, I've had lots of help from people here over the
> last few days, and as a result have upgraded Woody to Sarge. However, I
> have also been advised to install a 2.4 kernel version, as opposed to the
> 2.2 vers
"Brian Coiley" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi all.
>
> As a complete newbie, I've had lots of help from people here over the last
> few days, and as a result have upgraded Woody to Sarge. However, I have
> also been advised to install a 2.4 kernel version, as oppo
On Wed, 15 Sep 2004 [EMAIL PROTECTED] wrote:
> I been trying for what feels like ever to build an initrd to boot an
> LVM 2 root partition on a foreign architecture. Unfortunately, I keep
> seeing:
>
> RAMDISK: Compressed image found at block 0
> VFS: Mounted root (ext2 filesystem) readonly.
hi ya
On Sat, 11 Sep 2004, Steven Curtis wrote:
> I can't drop this initrd problem because I've run into this before and
> I'm determined to figure out how to make it work correctly because until
> now, I've always bailed and compiled a new kernel. This time, I'm going
> to figure it out. I
I can't drop this initrd problem because I've run into this before and
I'm determined to figure out how to make it work correctly because until
now, I've always bailed and compiled a new kernel. This time, I'm going
to figure it out. In order to verify the contents of the ram disk
image, I ne
Hello
May be the simplest way is to build your own kernel.
On the other I guess that surch an information is somewhere in the
initrd file.
Jerome
Steven Curtis wrote:
I'm not sure how to check that. I am using the kernel that is included
with the Debian package kernel-image version 2.6.7-2. Ho
I'm not sure how to check that. I am using the kernel that is included
with the Debian package kernel-image version 2.6.7-2. How can you tell
what version of initrd was used to build it?
Jerome BENOIT wrote:
Hello,
the package initrd-tools was recently updated [and if I remember well
importan
Hello,
the package initrd-tools was recently updated [and if I remember well
important bugs were fixed]:
have you check that your kernel was built with the latest version ?
hth,
Jerome
Steven Curtis wrote:
Stefan O'Rear wrote:
On Fri, Sep 10, 2004 at 07:58:53PM -0400, Steven Curtis wrote:
I'm
Stefan O'Rear wrote:
On Fri, Sep 10, 2004 at 07:58:53PM -0400, Steven Curtis wrote:
I'm trying to upgrade to the vmlinuz-2.6.7-1-k7 kernel and my system has
an Adaptec AIC7XXX EISA/VLB/PCI adapter. The stock vmlinuz-2.6.7-1-k7
kernel has aic7xxx support compiled as a module. I added the aic7
On Fri, Sep 10, 2004 at 07:58:53PM -0400, Steven Curtis wrote:
> I'm trying to upgrade to the vmlinuz-2.6.7-1-k7 kernel and my system has
> an Adaptec AIC7XXX EISA/VLB/PCI adapter. The stock vmlinuz-2.6.7-1-k7
> kernel has aic7xxx support compiled as a module. I added the aic7xxx
> module line
It is a simple trick:
mkdir /tmp/r
mount --bind / /tmp/r
cd /tmp/r/dev
umount /tmp/r
The "mount --bind" remounts a directory so it appears twice, but
without any submounts in the target directory. So it was exactly what
the doctor ordered.
--
Barak A. Pearlmutter <[EMAIL PROTECTED]>
Hamil
Thomas Adam wrote:
--- Jerome BENOIT <[EMAIL PROTECTED]> wrote:
Hello List,
I may need to use the `initrd-tools' Debian package,
so I am beginning to learn it: I have one very naive question:
I should write "to learn to deal with".
I just want to install Debian on a box with an USB hard drive:
i
--- Jerome BENOIT <[EMAIL PROTECTED]> wrote:
> Hello List,
>
> I may need to use the `initrd-tools' Debian package,
> so I am beginning to learn it: I have one very naive question:
Why do you need to "learn" initrd-tools?
-- Thomas Adam
=
"The Linux Weekend Mechanic" -- http://linuxgazette
On Sun, Feb 29, 2004 at 08:45:17PM -0800, Jason D. Berg wrote:
> I'm compiling a new kernel and I need to create a new initrd for it. I
> don't want to go through and manually copy all the files (especially the
> modules). Is there any easy way to do it? Any debian package? Any script
> that you ju
From: Keith Goettert <[EMAIL PROTECTED]>
>Date: Today 11:17:18
>My support of cramfs was complied into the kernel, but it still would
>not work. A very telling sign that it was compiled in was its
>complaint
>that it couldn't find a valid filesystem in the boot messages (which
>according to m
My support of cramfs was complied into the kernel, but it still would
not work. A very telling sign that it was compiled in was its
complaint that it couldn't find a valid filesystem in the boot messages
(which according to my readings is also a disputed and unresolved
bug/feature.) Now I hav
> On Wed, 2003-12-17 at 21:07, Keith Goettert wrote:
>> I have a kernel built from kernel.org source. I have included
>> support for ramdisk, initial ramdisk, and cramfs.
Is there not a specific patch for this in the Debian kernels?
A
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subj
Hi!
On Wed Dec 17, 2003 at 07:07:14PM -0800, Keith Goettert wrote:
> I have a kernel built from kernel.org source. I have included support
> for ramdisk, initial ramdisk, and cramfs.
>
> I built a ram disk image using mkinitrd
The vanilla linux kernels don't support cramfs. See mkinitrd(8):
B
On Wed, 2003-12-17 at 21:07, Keith Goettert wrote:
> I have a kernel built from kernel.org source. I have included support
> for ramdisk, initial ramdisk, and cramfs.
>
> I built a ram disk image using mkinitrd
>
> I can mount the image and list directories and files in it by using
> mount -o
Thanks Herbert that did the trick, should have guessed that from the
example...
> > # Examples:
> > #
> > # ext2
> > # wd io=0x300
> > FastTrak.o
>
> Try just "FastTrak".
Cheers,
Lewis
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL P
On Wed, Dec 10, 2003 at 10:23:14AM +1100, Lewis Shobbrook wrote:
>
> # Examples:
> #
> # ext2
> # wd io=0x300
> FastTrak.o
Try just "FastTrak".
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herb
ignored.
#
# You must run mkinitrd(8) to effect this change.
#
# Examples:
#
# ext2
# wd io=0x300
FastTrak.o
> -Original Message-
> From: Herbert Xu [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 9 December 2003 06:08
> To: Lewis Shobbrook
> Cc: [EMAIL PROTECTED]; [EMAIL PROTE
On Tue, Dec 09, 2003 at 11:04:22AM +1100, Lewis Shobbrook wrote:
>
> Basically the driver module is not loading and we can't mount the root
> filesystem. The module FastTrak.o can't be found, but I've mounted the
> rd image and can verify the inclusion. I've adjusted the modules file
> within the
On Wed Nov 12, 2003 at 07:32:47PM +0100, Goswin von Brederlow wrote:
> This is very very similar to what S390 wants. Except that they might
> make do with telnetd instead of sshd.
http://matt.ucc.asn.au/dropbear/dropbear.html
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
e-bone <[EMAIL PROTECTED]> writes:
> Hi, I am just curious if something like this is possible.
>
> I essentially need a two part boot process.
>
> I would like to have linux first boot to an initrd with a sshd running
> on it.
> Then, after connecting to this system over the network, I would lik
On Tue, Oct 21, 2003 at 02:07:39AM +0100, Antony Gelberg wrote:
> On Mon, Oct 20, 2003 at 08:13:59PM -0400, Jerome R. Acks wrote:
> > On Sun, Oct 19, 2003 at 05:39:49PM +0200, Ron Rademaker wrote:
> >
> > > modprobe: Can't locate module cramsfs
> > > mount: fs type cramfs not supported by kernel
>
On Mon, Oct 20, 2003 at 08:13:59PM -0400, Jerome R. Acks wrote:
> On Sun, Oct 19, 2003 at 05:39:49PM +0200, Ron Rademaker wrote:
>
> > modprobe: Can't locate module cramsfs
> > mount: fs type cramfs not supported by kernel
>
> > I use romfs... So I guess I shouldn't need cramfs, why it tries to l
On Sun, Oct 19, 2003 at 05:39:49PM +0200, Ron Rademaker wrote:
> modprobe: Can't locate module cramsfs
> mount: fs type cramfs not supported by kernel
> I use romfs... So I guess I shouldn't need cramfs, why it tries to load
> it, no idea.
> I created the initrd with mkinitrd (the debian package)
arl [mailto:[EMAIL PROTECTED]
Sent: 17 October 2003 15:56
To: Ron Rademaker
Cc: [EMAIL PROTECTED]
Subject: Re: Initrd modules
On Fri, Oct 17, 2003 at 11:22:22AM +0200, Ron Rademaker wrote:
> Hello,
>
> I've created a cramsfs initrd image and while booting the kernel says
&
On Fri, Oct 17, 2003 at 11:22:22AM +0200, Ron Rademaker wrote:
> Hello,
>
> I've created a cramsfs initrd image and while booting the kernel says
> it's loaded okay. I've set the modules to all in mkinitrd.conf and just
> to be sure I've added the following modules to the modules file:
> scsi_mod,
On Tue, 27 May 2003 12:22:54 -0400
"Brian W. Carver" <[EMAIL PROTECTED]> wrote:
> I just compiled a custom 2.4.18 kernel for my woody-running laptop.
>
> I'm new at this and am pretty sure I am about to shutdown and be unable to
>
> boot back up, because this initrd/lilo stuff has me baffled. P
On Tuesday 27 May 2003 14:08, Mark Roach wrote:
> I imagine this is because you don't have initrd-tools installed. For
> some reason the stock kernel images put this for depends:
> Depends: initrd-tools (>= 0.1.40), coreutils | fileutils (>= 4.0),
> modutils (>= 2.4.19)
>
> but when you use make-
On (27/05/03 10:32), Brian Carver wrote:
> New problem:
>
> When I proceeded with the
>
> dpkg -i kernel-image-2.4.18-custom.1.0_i386.deb
>
> after deciding that initrd.img was ok to put in lilo.conf I get an
> error:
> -
> Setting up kernel-image-2.4.18 (custom.1.0) ...
> Failed to create
On Tue, 2003-05-27 at 13:32, Brian Carver wrote:
> New problem:
>
> When I proceeded with the
>
> dpkg -i kernel-image-2.4.18-custom.1.0_i386.deb
>
> after deciding that initrd.img was ok to put in lilo.conf I get an error:
> -
> Setting up kernel-image-2.4.18 (custom.1.0) ...
> Failed to c
ake-kpkg options; read kernel howto re. initrd for
more detail
Both require some work. Invest in (1) unless you intend to distribute your
kernel to many different machine configurations, then (2) is a good
investment of your time.
HTH,
--
Mike M.
--
To UNSUBSCRIBE, email to [EMAIL PROTECT
New problem:
When I proceeded with the
dpkg -i kernel-image-2.4.18-custom.1.0_i386.deb
after deciding that initrd.img was ok to put in lilo.conf I get an error:
-
Setting up kernel-image-2.4.18 (custom.1.0) ...
Failed to create initrd image.
dpkg: error processing kernel-image-2.4.18 (--ins
Hi Brian
On (27/05/03 12:22), Brian W. Carver wrote:
> I just compiled a custom 2.4.18 kernel for my woody-running
> laptop.
> I'm new at this and am pretty sure I am about to shutdown
> and be unable to boot back up, because this initrd/lilo
> stuff has me baffled. Please help!
> I followed t
Ludwig Meyerhoff wrote:
Hallo!
I have a SCSI client running a AHA-2940. I wanted to run a USB
flashcard-reader with it and that does not work.
Same configuration on a IDE client works.
After some playing around I compiled a new kernel with integrated USB
support and modulized SCSI support - it
On Mon, Feb 17, 2003 at 15:40:29 -0600, Jamin W. Collins wrote:
> On Mon, Feb 17, 2003 at 11:10:46PM +0200, Shaul Karl wrote:
> > 1. initrd + aha1542
> > I am failing to convert a kernel with aha1542 builtin into an initrd
> > one because of the aha1542 module.
>
> I had a similar problem a
I just want to thank everyone for all your explanations -- it's been
very helpful! Moving on to newer problems now, but it's always great
to have things explained to you!
matt
On Fri, Jan 31, 2003 at 05:34:59PM -0600, Shyamal Prasad wrote:
> "Matt" == Matt Price <[EMAIL PROTECTED]> writes:
"Pigeon" == jah pigeon writes:
Pigeon> On Fri, Jan 31, 2003 at 05:34:59PM -0600, Shyamal Prasad
Pigeon> wrote:
>> You can use 'mount -t cramfs -o loop /mnt intrd.img.file.path'
>> to look into an initrd image. You will find it quite
>> instructive I'm sure.
Pigeon> Th
Pigeon <[EMAIL PROTECTED]> wrote:
>
> The rescue disks appear to use an initrd in 'root.bin' which isn't
> cramfs... at least the above doesn't work, nor does -t auto. Any idea
> what type this is? My curiosity has been aroused!
It's a gzipped ext2 file system. Uncompress it with gunzip before
m
On Fri, Jan 31, 2003 at 05:34:59PM -0600, Shyamal Prasad wrote:
> You can use 'mount -t cramfs -o loop /mnt intrd.img.file.path' to look
> into an initrd image. You will find it quite instructive I'm sure.
The rescue disks appear to use an initrd in 'root.bin' which isn't
cramfs... at least the ab
On Fri, Jan 31, 2003 at 12:42:22PM -0800, nate wrote:
> Matt Price said:
> > hi there,
> >
> > can someone help me figure out what exactly initrd is, and why
> > kernels use it? I have looked through the docs, and I understand that
> > it's thefile used for an initial ramdisk in some cases, but I
"Matt" == Matt Price <[EMAIL PROTECTED]> writes:
Matt> hi there, can someone help me figure out what exactly initrd
Matt> is, and why kernels use it? I have looked through the docs,
Matt> and I understand that it's thefile used for an initial
Matt> ramdisk in some cases, but I
Matt Price said:
> hi there,
>
> can someone help me figure out what exactly initrd is, and why
> kernels use it? I have looked through the docs, and I understand that
> it's thefile used for an initial ramdisk in some cases, but I don't
> understand why it would be used in some cases and not in o
On Sun, Jan 26, 2003 at 09:52:16PM -0500, Jameson C. Burt wrote:
> On Sun, Jan 26, 2003 at 03:30:32AM +0100, Carel Fellinger wrote:
...
> > I never could really find the info whether that 15Watt power supply is
> > part of the bricks or not and whether it needs any fan itself.
> > Could you enlight
The power supply is external, the size of a large eraser,
in the middle of a cord like
||
house-connection--|power-supply|diskless-workstation
||
where "--" represents a foot (30cm) of cord.
The power-supply say
On Fri, Jan 24, 2003 at 09:55:06PM -0500, Jameson C. Burt wrote:
> I re-emphasize the www.ltsp.org approach.
...
> I bought a diskless workstation 3 weeks ago from a link on ltsp.org,
> a workstation the size of your outstretched hand yet having
> audio, USB, parallel, serial, and ethernet ports
I re-emphasize the www.ltsp.org approach.
In the mid-1990's, I worked with diskless Suns
and also tried making several Debian Linux computers diskless.
After several weeks identifying files I wanted to keep,
sometimes different for each computer,
I abandoned that too-time-consuming approach to dis
Check www.ltsp.org . This might help you.
Tobias
Am Donnerstag, 16. Januar 2003 17:17 schrieb Rodrigo F. Baroni:
> m needing to set a diskless pc, and I have been
> studing the initrd procedure.
> The idea is to have the read-only directories
> mounted on nfs, and others one read-write in
> ram-
1 - 100 of 130 matches
Mail list logo
