ALT Linux Sisyphus discussions
 help / color / mirror / Atom feed
From: Sergey Vlasov <vsu@altlinux.ru>
To: ALT Linux Sisyphus discussion list <sisyphus@lists.altlinux.org>
Subject: Re: [sisyphus] LVM в initrd для ядра 2.6.14-std26-up-alt5
Date: Fri, 10 Mar 2006 21:07:45 +0300
Message-ID: <20060310180745.GF10180@procyon.home> (raw)
In-Reply-To: <4411B853.6030805@stc.donpac.ru>

[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]

On Fri, Mar 10, 2006 at 08:33:07PM +0300, Eugene Prokopiev wrote:
> Sergey Vlasov пишет:
> > On Fri, Mar 10, 2006 at 02:43:40PM +0300, Eugene Prokopiev wrote:
> >>>>Однако ядро совсем не смогло загрузиться с таким initrd, повиснув,
> >>>>похоже, на стадии его извлечения.
> >>>На каком именно сообщении?
> >>даже не на сообщении, а на точках
> >>
> >>Loading 2614-std26-alt5 .........
> > Тогда это даже не ядро, а загрузчик.
> 
> И как его лечить? Загрузчик - стандартный LILO version 22.4.1 из ALM 2.4
> 
> Какое ему дело до типа ФС initrd?

Возможно, дело не в типе, а в размере.

> На всякий случай, в lilo.conf написано:
> 
> raid-extra-boot=mbr-only
> boot=/dev/md0
> map=/boot/map
> install=/boot/boot-bmp.b
> vga=0x0311
> default=linux-up
> ramdisk=16384
> prompt
> timeout=50
> image=/boot/vmlinuz-up
>          label=linux-up
>          root=/dev/system/root
>          initrd=/boot/initrd-up
>          append=" splash=off"
>          read-only
> image=/boot/vmlinuz-2.6.14-std26-up-alt5
>          initrd=/boot/initrd.cpio

Можно запаковать его gzip-ом.

Ещё можно попробовать опцию large-memory.

>          root=/dev/ram0
>          label=2614-std26-up-5
>          read-only
>          append=" splash=off"
>          optional

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-03-10 18:07 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-09  6:20 Eugene Prokopiev
2006-03-09  7:15 ` Konstantin A. Lepikhov
2006-03-09  8:55   ` Eugene Prokopiev
2006-03-09 12:56     ` Denis Pynkin
2006-03-09 13:06       ` Led
2006-03-09 14:00         ` Nick S. Grechukh
2006-03-09 14:43           ` Led
2006-03-09 15:13             ` Kirill A. Shutemov
2006-03-09 15:19               ` Led
2006-03-09 15:45                 ` Kirill A. Shutemov
2006-03-09 15:36               ` Sergey Vlasov
2006-03-09 15:52                 ` Michael Shigorin
2006-03-10  6:04                 ` Eugene Prokopiev
2006-03-10  6:53                   ` Eugene Prokopiev
2006-03-10  9:55                     ` Sergey Bolshakov
2006-03-10 10:02                     ` Sergey Vlasov
2006-03-10 11:43                       ` Eugene Prokopiev
2006-03-10 12:39                         ` Sergey Vlasov
2006-03-10 12:51                           ` Led
2006-03-10 13:05                             ` Sergey Vlasov
2006-03-10 17:33                           ` Eugene Prokopiev
2006-03-10 18:07                             ` Sergey Vlasov [this message]
2006-03-10 20:07                               ` Eugene Prokopiev
2006-03-11  1:33                                 ` Sergey Bolshakov
2006-03-12  9:41                                   ` Eugene Prokopiev
2006-03-12 11:50                                     ` Sergey Bolshakov
2006-03-12 11:57                                       ` Eugene Prokopiev
2006-03-12 19:33                                         ` Sergey Vlasov
2006-03-13  7:23                                           ` Eugene Prokopiev
2006-03-12 12:14                                     ` Michael Shigorin
2006-03-12 12:59                                       ` Eugene Prokopiev
2006-03-12 19:31                                         ` Sergey Vlasov
2006-03-13  7:14                                           ` Eugene Prokopiev
2006-03-13  9:49                                             ` Sergey Vlasov
2006-03-13 10:23                                               ` Eugene Prokopiev
2006-03-09 16:45     ` Konstantin A. Lepikhov
2006-03-09 16:50       ` Konstantin A. Lepikhov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060310180745.GF10180@procyon.home \
    --to=vsu@altlinux.ru \
    --cc=sisyphus@lists.altlinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Sisyphus discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/sisyphus/0 sisyphus/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 sisyphus sisyphus/ http://lore.altlinux.org/sisyphus \
		sisyphus@altlinux.ru sisyphus@altlinux.org sisyphus@lists.altlinux.org sisyphus@lists.altlinux.ru sisyphus@lists.altlinux.com sisyphus@linuxteam.iplabs.ru sisyphus@list.linux-os.ru
	public-inbox-index sisyphus

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.sisyphus


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git