Eu uso o LILO, mas estou seriamente pensando em instalar o GRUB, pois
estou tendo alguns problemas como o Linux Loader.
A questão do make-kpkg eu não o uso, uso o make convencional, vou
baixa-lo e ver sua funcionalidade.
Obrigado galera inteligente
ps: inteligente = Usa LINUX
On Tue, 22 Feb
Parece que vc está compilando seu kernel sem o initrd
Dá uma olhada neste artigo acho que vai te ajudar!
http://www.vivaolinux.com.br/artigos/verArtigo.php?codigo=2039pagina=5
Já tentei várias coisas para compilar o kernel, mas sempre termina com
essa mensagem
VFS: Cannot open root device hda8
Onde eu acho o mkinitrd?
eu não achei não!
On Tue, 22 Feb 2005 16:50:54 -0300, Helder Pereira Cristo
[EMAIL PROTECTED] wrote:
Alcione Ferreira wrote:
Onde eu acho o mkinitrd?
eu não achei não!
On Tue, 22 Feb 2005 16:09:49 -0300, Helder Pereira Cristo
[EMAIL PROTECTED] wrote:
http://packages.debian.org/cgi-bin/search_contents.pl?word=mkinitrdsearchmode=searchfilescase=insensitiveversion=stablearch=i386
On Tue, 22 Feb 2005 16:51:36 -0300, Alcione Ferreira
[EMAIL PROTECTED] wrote:
Onde eu acho o mkinitrd?
eu não achei não!
On Tue, 22 Feb 2005 16:50:54 -0300,
Helder Pereira Cristo wrote:
Parece que vc está compilando seu kernel sem o initrd
Dá uma olhada neste artigo acho que vai te ajudar!
http://www.vivaolinux.com.br/artigos/verArtigo.php?codigo=2039pagina=5
Já tentei várias coisas para compilar o kernel, mas sempre termina com
essa mensagem
VFS:
Pela mensagem parece ser problema de HD.
Em Seg, 2005-02-21 s 10:41, Alcione Ferreira escreveu:
revisei toh a estrutura do config do kernel, recompilei ele mas
continua dando o mesmo erro, comea assim:
hda: bad acess: block=61239782, count=2
end_request: I/O error, dev hda, sector 61239782
tambem acho, mas como pode funcionar com a versão 2.2.20 e nao com a
versão 2.6.10?
On Mon, 21 Feb 2005 11:28:06 -0300, Marcos [EMAIL PROTECTED] wrote:
Pela mensagem parece ser problema de HD.
Em Seg, 2005-02-21 às 10:41, Alcione Ferreira escreveu:
revisei toh a estrutura do config
Realmente estranho, a no ser que a area em que foi gravado novo kernel esteja danificada. Poderia como teste compilar o 2.2.20 mesmo e instalar pra ver se ocorre este mesmo erro.
Em Seg, 2005-02-21 s 11:44, Alcione Ferreira escreveu:
tambem acho, mas como pode funcionar com a verso 2.2.20 e
Alcione Ferreira escreveu:
revisei toh a estrutura do config do kernel, recompilei ele mas
continua dando o mesmo erro, comea assim:
hda: bad acess: block=61239782, count=2
end_request: I/O error, dev hda, sector 61239782
EXT3-fs: unable to read superblock
hda: bad acess: block=61239782,
Opa Alcione,
Sera que voce nao esqueceu de adcionar nenhum modulo ao novo kernel?
Voce adcionou a nova imagem corretamente ao seu boot loader?
Alcione, pra comecar, de uma verificada nesses dois itens.
[]s
On Sun, 20 Feb 2005 10:08:35 -0300, Alcione Ferreira
[EMAIL PROTECTED] wrote:
Alcione,
Aconteceu esse problema comigo, eu tinha marcado
o suporte a HD IDE como módulo ao invés de ser parte do
kernel.
até mais,
Marcel
Alcione Ferreira escreveu:
recompilei meu kernel na versão 2.6.10, e quando fui testar a
inicialização do novo kernel, tive essa mensagem de erro, mas quando
Hallo Andreas (und alle anderen),
Ihre Nachricht vom 18.01.2005:
On 18.Jan 2005 - 17:33:32, Christoph Bohm wrote:
Ihre Nachricht vom 18.01.2005:
[wallace:/usr/src/linux]
17:30 # grep -i ide .config |grep -i blk
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_BLK_DEV_IDEPCI=y
Hallo Heiko,
ich hatte das selbe Problem. Bei mir lags daran, dass cramfs nicht im Kernel
einkompiliert war. Das braucht Debian merkwürdigerweise, um zu booten.
Ich habs dann durch Erstellung einer InitRD gelöst. Kernel musst Du dafür
mit
make-kpkg kernel_image --revision=m6800ne.0 --initrd
Am 2005-01-18 09:27:15, schrieb Jens Heidbüchel:
Hallo Heiko,
ich hatte das selbe Problem. Bei mir lags daran, dass cramfs nicht im Kernel
einkompiliert war. Das braucht Debian merkwürdigerweise, um zu booten.
Naja, wenn Du unbedingt eine initrd haben willst...
Debian benötigt KEINE initrd,
Ihre Nachricht vom 18.01.2005:
Hallo,
ich schließe mich mal an:
Ich habe genau das gleiche Problem mit 2.6.10 (vanilla):
VFS: Cannot open root device hda5 or unknown-block(0,0)
Please append a correct root= boot option
Kernel panic - not syncing: VFS: unable to mount root fs on
On 18.Jan 2005 - 17:33:32, Christoph Bohm wrote:
Ihre Nachricht vom 18.01.2005:
[wallace:/usr/src/linux]
17:30 # grep -i ide .config |grep -i blk
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_IDEDMA=y
On 18.Jan 2005 - 00:17:17, Heiko Brüning wrote:
Hallo!
Ich habe mir unter sarge einen modularen 2.6.9 gebaut. Booten bekomme
ich nun eine kernel-panic mit dem Hinweis:
VFS: Cannot open root device hdc1 or unknown-block(0,0)
Please append a correct root= boot option
Kernel panic - not
Hi...
Hast Du die IDE-Treiber und das Filesystem in den Kern kompiliert? Nicht
als Modul...
Gruß
Sebastian
Heiko Brüning schrieb:
Hallo!
Ich habe mir unter sarge einen modularen 2.6.9 gebaut. Booten bekomme
ich nun eine kernel-panic mit dem Hinweis:
VFS: Cannot open root device hdc1 or
Moin,
* Heiko Brüning wrote (2005-01-18 00:17):
Ich habe mir unter sarge einen modularen 2.6.9 gebaut. Booten bekomme
ich nun eine kernel-panic mit dem Hinweis:
VFS: Cannot open root device hdc1 or unknown-block(0,0)
Please append a correct root= boot option
Kernel panic - not syncing: VFS:
Am 2005-01-18 00:17:17, schrieb Heiko Brüning:
Hallo!
Ich habe mir unter sarge einen modularen 2.6.9 gebaut. Booten bekomme
ich nun eine kernel-panic mit dem Hinweis:
VFS: Cannot open root device hdc1 or unknown-block(0,0)
Please append a correct root= boot option
Kernel panic - not
Heiko Brüning schrieb:
VFS: Cannot open root device hdc1 or unknown-block(0,0)
Please append a correct root= boot option
Kernel panic - not syncing: VFS: unable to mount root fs on
unknown-block(0,0)
Was sagen:
lspci
egrep '^CONFIG.*_(IDE|BLK_DEV)' /boot/config-2.6.8-modules
Ciao
Walter
Bom dia!
Eu também passei por este problema do arquivo initrd. Com a opção
--initrd do make-kpkg é criado um arquivo initrd com o nome
especificado, então tu deve mover ou copiar este arquivo para o / ou
/boot e referencia-lo corretamente no arquivo de configuração do
gerenciador de boot,
Tupinamba
pegeui o .config que vc enviou, baixei o
source do 2.6.7 e tentei compilar.
Desmarquei a opcao referente a 'old disk-only'
em ATA/ATAPI/MFM/RLL e o boot aconteceu.
Mas apos a mensagem de inicio do apache os
erros
INIT: 1 respawing too fast: disable for 5 minutes
INIT: 2
) e mkinitrd(5).
Abraços,
Leonardo Lourenço Crespilho
- Original Message -
From: Arthur_Henrique_Sommerhalder_Tupinamba [EMAIL PROTECTED]
To: debian-user-portuguese debian-user-portuguese@lists.debian.org
Sent: Friday, September 17, 2004 7:18 PM
Subject: Re: Kernel Panic: VFS : Unable
: Arthur_Henrique_Sommerhalder_Tupinamba
To: debian-user-portuguese
Sent: Friday, September 17, 2004 7:18 PM
Subject: Re: Kernel Panic: VFS : Unable to mount root fs -AJUDA!!
Tentarei fazer o que nosso amigo Rubens disse, mas gostaria que mais
algueda referente ao problema Aos que já presenciaram o
problema...
por
Olá,
Tive esse mesmo problema quando testei o kernel 2.6 pela primeira vez.
O que se passou foi que existem umas novas opções relativas a suporte IDE
que eu não tinha reparado e não incluí no kernel. Sem suporte para IDE
nada feito. Pelo vistos os kernel hackers utilizam SCSI. :-)
As opções que
Oi Arthur. Faz o seguinte. Compila o suporte a ext3 como módulo.
--
Também faz as configurações que o Ruben falou:
* ATA/ATAPI/MFM/RLL support (CONFIG_IDE)
* Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support (CONFIG_BLK_DEV_IDE)
* Include IDE/ATA-2
Primeiramente Leonardo, obrigado pela força:
Vamos as dúvidas... (vamos dizer, que farei isso pelo menos em funcao de
testes)
- Se eu compilar o ext3 como módulo, jogo o ext2 como built-in ?? ou apenas o
ext3 como módulo ?
- Bom para criaçao do initrd, eu preciso alterar o mkinitrd.conf de
Arthur;
* Musashi corta a msg que Arthur Tupinambá enviou para Still:
Pessoal,
Preciso de uma ajuda urgente de quem já passou por esse tipo de experiência:
Baixei o kernel 2.6.8.1, do kernel.org, descompactei, dei um make menuconfig e
configurei-o.
após isso eu compilo e instalo do modo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Manuel Soukup schrieb:
| Leute ich hab meine Paketliste zurück gespielt. Dabei hat er ein Paket
| entfernt (konnte leider nicht sehen welches) und nun kommt beim booten:
|
| Kernel panic: VFS: Unable to mount root fs on 03:01
Naja, ich würde mal sagen,
Manuel Soukup [EMAIL PROTECTED] writes:
Hi
Leute ich hab meine Paketliste zurück gespielt. Dabei hat er ein Paket
entfernt (konnte leider nicht sehen welches) und nun kommt beim
booten:
Kernel panic: VFS: Unable to mount root fs on 03:01
Mit den Paketen direkt hat das nichts zu tun,
On Sun, 16 May 2004 11:33:03 -0300
Savio Ramos [EMAIL PROTECTED] wrote:
Respondendo a mim mesmo, para quem necessitar no futuro:
Estou compilando o núcleo 2.6.5 com o config do kernel-image-2.6.5-k7.
Deveria funcionar beleza, não?
Claro que funciona! O problema é que por padrão as imagens
On Sun, 16 May 2004 15:18:04 -0300
Vordeph [EMAIL PROTECTED] wrote:
É só um chute, mas na documentação do kernel 2.6.5 tem uma parte que fala dos
requisitos para instalação, é o arquivo Changes no diretório Documentation, lá
menciona as versões mínimas de alguns programas e bibliotecas que
On Mon, 17 May 2004 07:08:35 -0300
Savio Ramos [EMAIL PROTECTED] wrote:
O primeiro é um módulo e os outros estão embutidos. Vou tentar mudar o
primeiro.
Neca_de_pitibiriba ...
--
Savio Martins Ramos - Arquiteto
Rio de Janeiro ICQ 174972645
Pirataria não, seja livre: Linux
--- Savio Ramos [EMAIL PROTECTED] escreveu:
Você deve marcar as opções em Device, onde fica a
opção do loopback uma opção quem sob titulo RAM
[alguma coisa] lá dentro tem a opção de initrd e aí vc
marca e pronto, ou pode marcar tudo dentro do kernel e
marca automonter no próprio kernel.
Bom!
Olá Savio.
A partição root está com algum sistema de arquivos diferente do ext2?
Se estiver, o suporte a esse sistema de arquivos está compilado
diretamente no kernel? (não como módulo, mas sim estaticamente).
Abraços,
--
/*--*
*
Savio Ramos escreveu:
Olá,
Estou compilando o núcleo 2.6.5 com o config do kernel-image-2.6.5-k7.
Deveria funcionar beleza, não?
Não funcionou, na hora do boot aparece a mensagem acima.
Alguma luz?
Saudações,
É só um chute, mas na documentação do kernel 2.6.5 tem uma parte que fala
On Tue, Apr 20, 2004 at 03:10:58PM +0200, Philippe Dhont (Sea-ro) said
My new kernel is compiled with ext2, ext3 and the others also.
My filesystem is ext3.
In the kernel or as modules? They have to be builtin for it boot.
When i reboot my system i can choose to boot the debian2.6.5 but in
Philippe Dhont (Sea-ro) wrote:
Hi,
I installed debian SARGE with grub and everything works fine.
I downloaded the latest stable kernel, compiled everything and put the
boot lines in the grub configuration
Menu.lst
This was before:
Title Debian 2.4.25
Root (hd0,0)
Kernel /vmlinuz-2.4.25-1-386
Moin,
* Elimar Riesebieter [EMAIL PROTECTED] [2004-01-02 03:09]:
Thorsten Haude told:
- - - Schnipp - - -
[EMAIL PROTECTED] # lilo
/
Warning: The boot sector and map file are on different disks.
On Fri, 2 Jan 2004 12:02:41 +0100
Thorsten Haude [EMAIL PROTECTED] wrote:
Moin,
* Elimar Riesebieter [EMAIL PROTECTED] [2004-01-02 03:09]:
Thorsten Haude told:
- - - Schnipp - - -
[EMAIL PROTECTED] # lilo
Moin,
* Thorsten Haude [EMAIL PROTECTED] [2004-01-02 01:32]:
ich habe gerade einen neuen Kernel gebacken und bekomme es nicht hin,
den auch zu booten.
Ok, ich habe jetzt mal Grub installiert. Damit ist es kein Problem,
den alten Kernel zu booten, beim neuen gibt es den gleichen Fehler.
Damit ist
Hi Thorsten,
On Fri, 02 Jan 2004 the mental interface of
Thorsten Haude told:
Moin,
- - - Schnipp - - -
[EMAIL PROTECTED] # lilo
/
Warning: The boot sector and map file are on different disks.
On Tuesday 26 August 2003 14:56, Joris Huizer wrote:
--- Alphonse Ogulla [EMAIL PROTECTED] wrote:
Hi all,
Just compiled kernel 2.4.21 but cannot boot it
despite creating the initrd
image and respective links in / to files in /boot.
The last 5 lines printed on screen before hang-up
are
--- Alphonse Ogulla [EMAIL PROTECTED] wrote:
Hi all,
Just compiled kernel 2.4.21 but cannot boot it
despite creating the initrd
image and respective links in / to files in /boot.
The last 5 lines printed on screen before hang-up
are printed below.
RAMDISK: Couldn't find valid RAM disk
On Tue, Aug 26, 2003 at 12:40:44PM +0300, Alphonse Ogulla wrote:
| Just compiled kernel 2.4.21 but cannot boot it
| VFS: Cannot open root device 301 or 03:01
You probably forgot to include the driver for your hard disk when you
built the kernel. Follow Joris' suggestion for enabling the driver
El Sábado, 8 de Marzo de 2003 17:34, Borxa Varela escribió:
¿Como salgo de esta? No puedo arrancar ni con el diskete... ¿tengo que
reinstalar?
Si no tienes otra particion root por ahi yo creo q sí.
Lo siento.
--
Fernando Blat Peris
http://ttt.inf.upv.es/~ferblape
Polinux
Borxa Varela wrote:
¿Como salgo de esta? No puedo arrancar ni con el diskete... ¿tengo que
reinstalar?
Intenta dar un poco mas de información sobre tu sistema, como tipo de
sistema de ficheros para la raíz, si has hecho algun cambio ultimamente,
etc..., del error que indicas lo uúnico
Moviste el rigido de lugar ? si es asi, solo basta con bootear otro SO, aceder
a la particion y cambiar la entrada / del fstab.
JoloX
El Sáb 08 Mar 2003 16:34, Borxa Varela escribió:
¿Como salgo de esta? No puedo arrancar ni con el diskete... ¿tengo que
reinstalar?
--
Powered by JoloX 0.01
On Sat, Dec 07, 2002 at 12:38:37AM +1300, Richard Hector wrote:
It is? I thought that was the usual way to do it (with 2.4 kernels,
anyway) ... should I look at recompiling my kernel with my SCSI drivers
built in instead? Or are you specifically referring to filesystem
drivers rather than all
Paul == Paul Johnson [EMAIL PROTECTED] writes:
Paul Support for your root device hardware and filesystem should
Paul be part of your kernel for maximum ease and reliability.
Paul Pretty much everything else that can be moduled out should.
Paul,
To be fair, you should point out
Just a thought, but do you have ide and/or scsi as modules instead of
compiled into the kernel? You will get this message if the kernel can't
mount the root partition because it doesn't have the necessary drivers to
talk to the disk on which the root partition sits. That is, if / is on an
ide
In article 20021206045426.GA22017@ursine, Paul Johnson wrote:
Wait, are you trying to boot a kernel that doesn't have ext3 compiled
in on a system whose /etc/fstab specifies the / partition as being
ext3?
Nope, ext2/ext3 have been included in the vmlinuz-image all along.
I'll throw in
On Fri, Dec 06, 2002 at 08:26:48AM -0600, Shyamal Prasad wrote:
Paul,
To be fair, you should point out that this is an opinion that run's
contrary to how Debian's 2.4 kernels are packaged.
Yes, I realise this, however, when compiling one's own kernel from the
kernel archive (oppose to the
On Thu, Dec 05, 2002 at 01:04:34AM +, Stig Are M. Botterli wrote:
Basically, if my /boot/vmlinuz image exceeds a certain size (the limit seems be
somewhere around 90 bytes), the following occurs on boot:
Whoa! Huge kernel! Module some of that stuff out and it should
help if there's
In article 20021205080347.GE7442@ursine, Paul Johnson wrote:
On Thu, Dec 05, 2002 at 01:04:34AM +, Stig Are M. Botterli wrote:
Basically, if my /boot/vmlinuz image exceeds a certain size (the limit se=
ems be
somewhere around 90 bytes), the following occurs on boot:
Whoa! Huge
On Thu, 05 Dec 2002 15:16:29 +
Stig Are M. Botterli [EMAIL PROTECTED] wrote:
In article 20021205080347.GE7442@ursine, Paul Johnson wrote:
On Thu, Dec 05, 2002 at 01:04:34AM +, Stig Are M. Botterli
wrote: Basically, if my /boot/vmlinuz image exceeds a certain size
(the limit se=
In article [EMAIL PROTECTED], Klaus Imgrund wrote:
On Thu, 05 Dec 2002 15:16:29 +
I had kernels bigger than 1 MB - no problem.
It would help if you remember what things you configured as modules.
Unfortunately, I don't.
If you got i.e a driver for the wrong sound card compiled in the
On Thu, Dec 05, 2002 at 07:10:42PM +, Stig Are M. Botterli wrote:
I had kernels bigger than 1 MB - no problem.
It would help if you remember what things you configured as modules.
Unfortunately, I don't.
Wait, are you trying to boot a kernel that doesn't have ext3 compiled
in on a
On 29 Jul 2002 19:25:37 +0200
Nils Gundelach [EMAIL PROTECTED] wrote:
letzte Nacht habe ich bei einem Freund Woody mit CD's von Liniso (von
Mitte April) installiert, mit Kernel 2.4.18, ext3 (fstab auch
geändert) und ide-scsi. Anschließend habe ich apt-get update und
apt-get upgrade
Markus Liebl [EMAIL PROTECTED] writes:
Nils Gundelach [EMAIL PROTECTED] wrote:
Kernel panic: VFS: Unable to mount root fs on 03:41
Also 03:41 ist ttyr9
$: ll /dev/ | egrep 3,\ *41
crw-rw-rw-1 root tty3, 41 25. Nov 2001 ttyr9
Ich glaube nicht das deine root
Hi,
hast du vielleicht einen SCSI oder IDE Controller der nicht gefunden
wird ?
On Sun, 2002-07-28 at 22:20, Hermann Moser wrote:
Hallo,
letzte Nacht habe ich bei einem Freund Woody mit CD's von Liniso (von
Mitte April) installiert, mit Kernel 2.4.18, ext3 (fstab auch geändert)
und
Hallo Nils,
Am Montag, 29. Juli 2002 19:25 schrieb Nils Gundelach:
hast du vielleicht einen SCSI oder IDE Controller der nicht gefunden
wird ?
Ein SCSI Controller ist nicht vorhanden, dass der IDE Controller nicht
gefunden wird, glaube ich eher nicht, denn sonst würde ja der Kernel
2.2.20
Hallo Hermann,
wie ist denn das ext3 vorhanden, als Modul
oder fest im Kernel? Initial ramdisk mal
probiert? Hast Du per apt-get auch nen Kernelupdate
gemacht? Wenn Du von einem 2.2er Kernel updatest,
brauchst Du auch neue modutils, die gibts bei
kernel.org, falls Du die aus irgendeinem Grund
Hallo Sebastian,
Am Sonntag, 28. Juli 2002 22:31 schrieb Sebastian Wolfgarten:
wie ist denn das ext3 vorhanden, als Modul
Ein cat /proc/filesystems ergab unter anderem auch ext3, ich habe mich
beim Einrichten an die Anweisung auf channel.debian.de gehalten.
Als ich bei mir Woody installiert
Revisa que en el BIOS no se encuentre Activado (Enabled) la opcion UDMA
- Original Message -
From: Antxoka Gerrikabeitia Uriarte [EMAIL PROTECTED]
To: Lista de Usuarios Debian debian-user-spanish@lists.debian.org
Sent: Thursday, April 04, 2002 3:12 PM
Subject: kernel panic VFS: free block
On Thu, Mar 28, 2002 at 09:24:24AM -0300, Warning Rancid wrote:
Hola lista ...
Aca esta exactamente lo que me dice el Kernel Panik
Kernel Panic :VFS : Unable to mount root fs on 03:07
ok. no puede montar tu dispositivo raiz ( / ).
puede ser que tu kernel no tenga soporte para el
Sorry,
I've found the problem my fault I was playing with ext3 about the time it
came in the kernel and for some reason the filesystem was identified as ext3
but was ext2.
Sorry again
Nick
On Sat, Jan 12, 2002 at 05:56:37PM -0800, justin cunningham wrote:
I'm trying to get a server built with 2.2r4 potato cd and keep getting
the above error. I tried the boot options in f2-f8 and tried mounting
various root.bins from specifying floppy0 at boot: then got kernel
panic: no init
Thus spake Philip Blundell:
On Sat, Jan 12, 2002 at 05:56:37PM -0800, justin cunningham wrote:
I'm trying to get a server built with 2.2r4 potato cd and keep getting
the above error. I tried the boot options in f2-f8 and tried mounting
various root.bins from specifying floppy0 at boot:
El dom, 30 de dic de 2001, a las 05:56:27 +0100, Resman comento ...
Hola a todos,
He estado instalando una debian en un 486 con 16 MB de RAM. Empecé
instalando una Potato (y todo fue bien) y después, con el sistema
básico, me decidí a actualizarlo a Woody. Una vez más todo fue sin
On 30 Dec 2001, Resman wrote:
Hola a todos,
He estado instalando una debian en un 486 con 16 MB de RAM. Empecé
instalando una Potato (y todo fue bien) y después, con el sistema
básico, me decidí a actualizarlo a Woody. Una vez más todo fue sin
problemas.
El caso es que digo, bueno pos
On Sun, 2001-12-30 at 10:56, Resman wrote:
Con todo esto reinicio y
kernel panic: VFS unable to mount root fs
Suponiendo que tu partición root tenga ReiserFS, no será porque tenías
ReiserFS compilado en el kernel 2.2.x, y en el 2.4.16 viene como módulo?
--
-
| | |
El dom, 30-12-2001 a las 17:56, Resman escribió:
Hola a todos,
He estado instalando una debian en un 486 con 16 MB de RAM. Empecé
instalando una Potato (y todo fue bien) y después, con el sistema
básico, me decidí a actualizarlo a Woody. Una vez más todo fue sin
problemas.
El caso es que
El dom, 30-12-2001 a las 18:34, Dios del Tiempo escribió:
On Sun, 2001-12-30 at 10:56, Resman wrote:
Con todo esto reinicio y
kernel panic: VFS unable to mount root fs
Suponiendo que tu partición root tenga ReiserFS, no será porque tenías
ReiserFS compilado en el kernel 2.2.x, y en el
El dom, 30-12-2001 a las 18:54, Brain Killer escribió:
eso es que no sabe como montar el sistema de archivos raiz, posiblemente
tengas como modulo de kernel el soporte para ese sistema de archivos.
ya, pero es que no lo he compilado yo, sino que es el
kernel-image-2.4.16-386 de woody.. me
Ola pessoal, o problema estava no meu grub
root (hd0,1)
kernel=/vmlinuz root=/dev/hda == aqui estava o erro (deveria estar hda2)
Em 28 Dec 2001, [EMAIL PROTECTED] escreveu:
Ola pessoal, peguei recentemente os fontes do kernel 2.2.19 (apos a
correcao
do bug).
apt-get install
Dell Latitude CPi D300XT 128MB Ram PII 300Mhz
lilo.conf
vga=1
append=apm=on
default=Linux22
# kernel 2.4.12
image=/vmlinuz
initrd=/boot/initrd
label=LinuxNew
read-only
# kernel 2.4.10
image=/vmlinuz.old
initrd=/boot/initrd-2.4.10-686
label=LinuxOld
--- Xeno Campanoli [EMAIL PROTECTED] wrote:
Shaul Karl wrote:
As my subject line indicates, I'm getting the
diagnostic:
Kernel panic: VFS: Unable to mount root fs
on 01:00
when I try to boot up with my home grown kernel.
I've tried several
things with
--- Shaul Karl [EMAIL PROTECTED] wrote:
--- Xeno Campanoli [EMAIL PROTECTED] wrote:
Shaul Karl wrote:
As my subject line indicates, I'm getting
the
diagnostic:
Kernel panic: VFS: Unable to mount
root fs
on 01:00
when I try to boot up with my
SNIP
Now, I'm really confused. I haven't been able to
get
any of the 2.4.x debian kernel packages to boot
and
everything I had read previously in the list
archives
indicated that the initrd line was necessary for
2.4.x
kernels. I never had any problems with 2.0.x or
quote who=Xeno Campanoli
As my subject line indicates, I'm getting the diagnostic:
Kernel panic: VFS: Unable to mount root fs on 01:00
i would say the #1 cause of this is lack of support for
the disk controller which the root drive is hooked to
compiled into the kernel(it can't be a
Make sure that you have compiled the ide and ext2 into the kernel and not
just made them loadable mods.
Xeno Campanoli wrote:
Subject:
Kernel panic: VFS: Unable to mount root fs on 01:00
From:
Xeno Campanoli
As my subject line indicates, I'm getting the diagnostic:
Kernel panic: VFS: Unable to mount root fs on 01:00
when I try to boot up with my home grown kernel. I've tried several
things with lilo on this, but I'm stumped. rdev indicates the root
partition is /dev/hda1, which is
Shaul Karl wrote:
As my subject line indicates, I'm getting the diagnostic:
Kernel panic: VFS: Unable to mount root fs on 01:00
when I try to boot up with my home grown kernel. I've tried several
things with lilo on this, but I'm stumped. rdev indicates the root
partition
--- Xeno Campanoli [EMAIL PROTECTED] wrote:
Shaul Karl wrote:
As my subject line indicates, I'm getting the
diagnostic:
Kernel panic: VFS: Unable to mount root fs
on 01:00
when I try to boot up with my home grown kernel.
I've tried several
things with lilo on this,
Thus spake Charles Baker:
--- Xeno Campanoli [EMAIL PROTECTED] wrote:
Shaul Karl wrote:
As my subject line indicates, I'm getting the
diagnostic:
Kernel panic: VFS: Unable to mount root fs
on 01:00
when I try to boot up with my home grown kernel.
I've
On Sat, Oct 06, 2001 at 02:17:20PM -0400, Stan Brown wrote:
I'm trying to set up a new machine this weekend, and i'm in trouble.
I know you needed a solution by Monday, so this is a bit late, but I
haven't seen anyone else post an explanation of what the error
actually means, so...
Now, I have
During the install of the 2.4 kernel package. I goot a message about
needing to add a initrd line to lilo.conf.
This is probably the cause of your problem. I had the same problem the
first time I installed a 2.4 kernel package with apt-get.
Just follow the instructions and edit your lilo.conf
- Original Message -
From: Dave Sherohman [EMAIL PROTECTED]
To: Debian User List debian-user@lists.debian.org
Sent: Monday, October 08, 2001 4:52 PM
Subject: Re: Kernel Panic: VFS Unable to mount root fs on 21:04
On Sat, Oct 06, 2001 at 02:17:20PM -0400, Stan Brown wrote:
I'm trying
- Original Message -
From: Stan Brown [EMAIL PROTECTED]
To: Debian User List debian-user@lists.debian.org
Sent: Saturday, October 06, 2001 8:17 PM
Subject: Kernel Panic: VFS Unable to mount root fs on 21:04
I'm trying to set up a new machine this weekend, and i'm in trouble.
I
Hi, Mark!
Problems solved, thanks!
I found what happened to lead to the problem was - I changed the hard disk from
secondary master to primary master, lilo was looking for '/' in /dev/hdc5,
rather
/dev/hda5. From your tips, I first tried to put 'rescue root=/dev/hda5' at the
boot
prompt when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wilson,
When my machine boots up, Linux is auto-probing the hardware, then it
stops and pops up an error message Kernel Panic..VFS
I tried to use a 'rescue' disk and did the e2fsck, but it said the '/'
partition was clean.
I could
Mark,
Yes, thank you for reminding me the missing bits (The machine with broken O/S is
not with me at the moment, I'm sorry that I have not jotted them down properly).
Now, presuming what you said is right and once I've checked out the number,x
in the error message VFS: Unable to mount root fs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wilson,
Yes, thank you for reminding me the missing bits (The machine with broken O/S
is
not with me at the moment, I'm sorry that I have not jotted them down
properly).
Now, presuming what you said is right and once I've checked out the
Ese problema suele ocurrir si, al compilar el kernel, se selecciona
(en filesystems) el ext2fs como modulo, que no puede ser. El ext2fs
tiene que incluirse directamente en el kernel, no como modulo
Miguel
Gracias por tu rápida respuesta. Era lo de hacer como módulo el ext2fs.
Le he
Si puedes seguir botando con el kernel antiguo pero no con el nuevo,
seguramente se te ha olvidado ejectuar 'lilo' a secas después de haber
modifcado el 'lilo.conf'
El día 23/02/00 Juanma decía:
Estimados amigos:
Llevo una semana desesperado pues quiero compilar el kernel a la versión
Ese problema suele ocurrir si, al compilar el kernel, se selecciona
(en filesystems) el ext2fs como modulo, que no puede ser. El ext2fs
tiene que incluirse directamente en el kernel, no como modulo
Miguel
Barbie Dominatrix wrote:
Si puedes seguir botando con el kernel antiguo pero
On Wed, 23 Feb 2000, Miguel Rodriguez Penabad wrote:
Ese problema suele ocurrir si, al compilar el kernel, se selecciona
(en filesystems) el ext2fs como modulo, que no puede ser. El ext2fs
tiene que incluirse directamente en el kernel, no como modulo
Miguel
Barbie Dominatrix wrote:
At 01:54 AM 10/22/99 +0200, Jocke wrote:
Hi all,
I did something stupid today :(
While recompiling my kernel to add scsi support for my cdrw I accidently
forgot some ide stuff and now I can't boot.
If you want to change something important like a...*hmmm*
a kernel or something ALWAYS make lilo
1 - 100 of 108 matches
Mail list logo
