Greg Folkert wrote:
[snip ksymoops]
Warning: Gut reactions have come forth, please be aware that your
feeling MAY be hurt.
Okay, I think I see an ID10T error afloat here.
Re-Install the latest kernel (the one you are running), but before you
do move the modules dir to .old
Then re-run lilo -v if
Hello,
have you checke your system memory? To check the memory, reboot the system
with memtest86 and look whether you get any error messages.
Regards
Jakob
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
2: 0f 94 c0 sete %al
> Code; c01bc649
> 5: 0f b6 c0 movzbl %al,%eax
> Code; c01bc64c
> 8: ba 01 00 00 00mov$0x1,%edx
> Code; c01bc651
> d: 85 c0 test %eax,%eax
> Code; c01bc653
5: 0f b6 c0 movzbl %al,%eax
Code; c01bc64c
8: ba 01 00 00 00mov$0x1,%edx
Code; c01bc651
d: 85 c0 test %eax,%eax
Code; c01bc653
f: 0f 45 54 24 24cmovne 0x24(%esp,1),%edx
<0> Kernel panic: Aiee,
Calltrace: [] [] [] []
[]
[] [] [] [] []
[]
[] [] [] [] []
[]
[] [] [] []
Code : 39 16 0f 94 c0 0f b6 c0 ba 01 00 00 00 85 c0 0f 45 54 24 24
<0> Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
On Mon, Oct 27, 2003 at 06:45:28AM +, Anim Asante wrote:
> <[EMAIL PROTECTED]> wrote: >
> >
> > From: Jerome R. Acks
> > [mailto:[EMAIL PROTECTED]
> > Sent: 24 October 2003 03:47
> > To: Anim Asante
> > Cc: [EMAIL PROTECTED]
> > Subjec
--- "Asante, Emmanuel [ING-WBK]"
<[EMAIL PROTECTED]> wrote: >
>
> -Original Message-
> From: Jerome R. Acks
> [mailto:[EMAIL PROTECTED]
> Sent: 24 October 2003 03:47
> To: Anim Asante
> Cc: [EMAIL PROTECTED]
> Subject: Re: Kernel panic error
t; ?
> > > When I restart my machine and select this option,
> > the
> > > boot up process begins up
> > > to a point and it gives the following error
> > message:
> > > ?Warning: unable to open an initial console.
> > > ?Kernel panic:
--- Anim Asante <[EMAIL PROTECTED]> wrote: > >
-Original Message-
> > From: Bill Marcum [mailto:[EMAIL PROTECTED]
> > Sent: 22 October 2003 07:01
> > To: [EMAIL PROTECTED]
> > Subject: Re: Kernel panic error
> >
> >
> > On T
> -Original Message-
> From: Bill Marcum [mailto:[EMAIL PROTECTED]
> Sent: 22 October 2003 07:01
> To: [EMAIL PROTECTED]
> Subject: Re: Kernel panic error
>
>
> On Tue, Oct 21, 2003 at 07:27:29AM +0100, Anim
> Asante wrote:
> > I have got a gru
process begins up
> to a point and it gives the following error message:
> Warning: unable to open an initial console.
> Kernel panic: No init found.
> Try passing init= option to kernel.
>
> Can anybody indicate what "option" should be?
> Thanks
>
The kernel c
initial console.
Kernel panic: No init found.
Try passing init= option to kernel.
Can anybody indicate what "option" should be?
Thanks
Want to chat instantly with your online friends? Get the FREE Yahoo!
Mess
may have made other changes; don't quite
remember.
Anyway, it's been chugging along quite happily since then, up until the
aforementioned kernel panic.
I rebooted and, a couple of minutes after the reboot, it panicked again,
implicating exim.
I rebooted again and it (meaning lilo?
root device "341" or 03:41
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 03:41
(by the way, is there any way to get a log of all the messages from a
failed boot? I had to copy these out by hand)
I'm using lilo as my boot manag
Hello all,
Sorry for this message that should be posted onto debian.user.french!
Thanks,
Eclice.
--
Sylvain Briole (a.k.a. Eclice)
E-Technik Doktorand / München
EMail : sbriole (à) free.fr
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMA
e dans les archives des groupes sur initrd :
[...]
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 248k freed
Kernel panic: No init found. Try passing init= option to kernel.
Gasp.
J'en perds mon latin.
Une idée d'où je me suis planté?
Merci par avance
e last 5 lines printed on screen before hang-up
> > are printed below.
> >
> > RAMDISK: Couldn't find valid RAM disk image starting
> > at 0.
> > Freeing initrd memory: 2664k freed
> > VFS: Cannot open root device "301" or 03:01
> > Ple
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 drive
; RAMDISK: Couldn't find valid RAM disk image starting
> at 0.
> Freeing initrd memory: 2664k freed
> VFS: Cannot open root device "301" or 03:01
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 03:01
>
>
2664k freed
VFS: Cannot open root device "301" or 03:01
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 03:01
Passing root=/dev/hda1 to lilo at boot time did not bear fruit.
Created initrd as follows:
# mkinitrd -o /boot/initrd.img-2.4.21 /
Hi all,
Having the following system
configuration...
VIA EDEN 800 MHz processor
256 MB RAM
Wildcard X100P
Debian 3.1
kernel-2.4.18-bf2.4
I am gtting this error when I want to load wcfxo
driver
general protection fault
CPU: 0--<0> Kernel panic
Debian users;
I'm traying to install a Debian/Gnu Linux in a notebook.
I installed a i386 Debian version / network from www.debian.com
When I finished the instalation a error ocurred:
Kernel Panic
Attempted to kill the idle tesk
In interrupt handler-not syncing
Please, if know this
18:50, Alexandre Passito wrote:
> Kernel Panic
> Attempted to kill the idle tesk
> In interrupt handler-not syncing
Maybe this post to the portuguese debian users lists help
http://lists.debian.org/debian-user-portuguese/2002/debian-user-portuguese-200203/msg00199.html
In general: it seems
ake/model is your notebook. What video card and sound card does it
use. How much ram does it have. Also,
Did you install debian from CD's, with floppy disks or some other way.
Are you using LILO or GRUB as your boot loader.
HTH.
-Kev
>
> When I finished the instalation a error ocurred:
&g
checktime reached, running e2fsck is recommended
> VFS: Mounted root (ext2 filesystem).
> VFS: Mounted root (ext2 filesystem) readonly.
> change_root: old root has d_count=1
> Trying to unmount old root ... okay
> Freeing unused kernel memory: 156k freed
> Kernel panic: No init
warning: checktime reached, running e2fsck is recommended
> > > > VFS: Mounted root (ext2 filesystem).
> > > > VFS: Mounted root (ext2 filesystem) readonly.
> > > > change_root: old root has d_count=1
> > > > Trying to unmount old root ... okay
> > > >
On Wed, 12 Mar 2003 13:09:50 -0500 (EST)
Reid Mumford <[EMAIL PROTECTED]> wrote:
> I have a problem that has brought my laptop down.
>
> Any ideas on how to save this system without having to reinstall?
Your filesystem was corrupted and you've lost some files (or pieces of files).
You may be a
root (ext2 filesystem) readonly.
> change_root: old root has d_count=1
> Trying to unmount old root ... okay
> Freeing unused kernel memory: 156k freed
> Kernel panic: No init found. Try passing init= option to kernel
>
> this is basically the same thing that i get when i boot without
stem).
> > > VFS: Mounted root (ext2 filesystem) readonly.
> > > change_root: old root has d_count=1
> > > Trying to unmount old root ... okay
> > > Freeing unused kernel memory: 156k freed
> > > Kernel panic: No init found. Try passing init= option to ke
ilesystem).
> > > VFS: Mounted root (ext2 filesystem) readonly.
> > > change_root: old root has d_count=1
> > > Trying to unmount old root ... okay
> > > Freeing unused kernel memory: 156k freed
> > > Kernel panic: No init found. Try passing init= option t
Warwick Brown wrote:
tbh it looks like you have lost some vital system binaries, your best bet is
to boot off the rescue disk, back up yer data files and reinstall, but make
sure u bad block check the disks when u reformat them, coz lappies do get
bounced around a fair bit, so disk damage shoul
; change_root: old root has d_count=1
> > Trying to unmount old root ... okay
> > Freeing unused kernel memory: 156k freed
> > Kernel panic: No init found. Try passing init= option to kernel
> >
> > Any ideas on how to save this system without having to reinstall?
&g
d root ... okay
> Freeing unused kernel memory: 156k freed
> Kernel panic: No init found. Try passing init= option to kernel
>
> Any ideas on how to save this system without having to reinstall?
try booting up with init=/bin/sh and see if you can get yourself
a root prompt. if so, you&#x
tbh it looks like you have lost some vital system binaries, your best bet is
to boot off the rescue disk, back up yer data files and reinstall, but make
sure u bad block check the disks when u reformat them, coz lappies do get
bounced around a fair bit, so disk damage shouldnt be ruled out
rega
ay
Freeing unused kernel memory: 156k freed
Kernel panic: No init found. Try passing init= option to kernel
this is basically the same thing that i get when i boot without the cd
too.
Any ideas on how to save this system without having to reinstall?
thanks
reid mumford
--
To UNSUBSCRIBE, email
it happened to me once (IBM p200mhz), but when I replaced my old simms at
70ns with 80ns (the new ones had more memory), I had to set that up at
startup not via system and all worked.
R>
>I tried it, a couple of times to be sure, but , NO, it does not solve
>the problem. Thanks, though. V.
>---
llowing instructions given in:
http://www.webmo.net/support/linux_memory.html
I added
append="mem=256M"
to lilo.conf and ran and executed /sbin/lilo -v
A warm re-boot has no effect, but a cold reboot ends in kernel panic
"unable to handle kernell null pointer dereference at virt
nit, 0k highmem)
>
> Following instructions given in:
> http://www.webmo.net/support/linux_memory.html
>
> I added
> append="mem=256M"
> to lilo.conf and ran and executed /sbin/lilo -v
>
> A warm re-boot has no effect, but a cold reboot ends in kernel panic
> &q
I tried it, a couple of times to be sure, but , NO, it does not solve
the problem. Thanks, though. V.
--- Mike Dresser <[EMAIL PROTECTED]> wrote:
> On Fri, 31 Jan 2003, Virgil wrote:
>
> > I added
> > append="mem=256M"
> > to lilo.conf and ran and executed /sbin/lilo -v
>
> Try mem=255M and see w
On Fri, 31 Jan 2003, Virgil wrote:
> I added
> append="mem=256M"
> to lilo.conf and ran and executed /sbin/lilo -v
Try mem=255M and see what happens
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
n in:
http://www.webmo.net/support/linux_memory.html
I added
append="mem=256M"
to lilo.conf and ran and executed /sbin/lilo -v
A warm re-boot has no effect, but a cold reboot ends in kernel panic
"unable to handle kernell null pointer dereference at virtual address
0003.
Could it be tha
On Wed, Jan 22, 2003 at 06:12:31PM -, Colin Ellis wrote:
>> From: Rodrigo Otavio Weymar Fonseca [mailto:[EMAIL PROTECTED]]
>> Sent: 22 January 2003 17:54
>> To: Colin Ellis
>> Cc: debian user list
>> Subject: RE: [HELP] - kernel panic 2.4.18 on Dual-PIII
>>
Try append="noapic" to turn off power management.
-Original Message-
From: Rodrigo Otavio Weymar Fonseca [mailto:[EMAIL PROTECTED]]
Sent: 22 January 2003 17:54
To: Colin Ellis
Cc: debian user list
Subject: RE: [HELP] - kernel panic 2.4.18 on Dual-PIII
Hello Colin,
I h
Hello Colin,
I have tested the 2.4.18smp also and I got the same type of errors.
But, are there problems in using a up kernel in a smp hardware ?
I thought the only problem in not using a smp kernel in a smp hw was the
loss of performance.
If someone doesn`t use a smp kernel, or bett
Original Message-
From: Rodrigo Otavio Weymar Fonseca [mailto:[EMAIL PROTECTED]]
Sent: 22 January 2003 16:28
To: debian user list
Subject: [HELP] - kernel panic 2.4.18 on Dual-PIII
Hi,
I sent this message yesterday, but I am not sure it reached the
debian-user list.
I am sorry
n user list <[EMAIL PROTECTED]>
Subject: [HELP] - kernel panic 2.4.18 on Dual-PIII
Hello all,
I am using the standard kernel 2.4.18(stable) provided with Woody cd's on
a Dual-PIII 733 Mhz.
I have just installed that, after have using the 2.2.20-idepci version.
But I am facing a
Hello all,
I am using the standard kernel 2.4.18(stable) provided with Woody cd's on
a Dual-PIII 733 Mhz.
I have just installed that, after have using the 2.2.20-idepci version.
But I am facing a kernel panic with the 2.4.18 (up) version.
When I try to boot, it appears the foll
I am having an issue with my SID install. Every once in a while I boot up
and during system bootup I get a kernel panic. I then reboot and all is
fine, at least for the next week or so. I also dual boot into Redhat and
this does not happen on that installation. This is the message on the
screen
the best way to do it?
I've got a log of most of the updates I've done.
Thanks again,
Rich B
Original post:
>> I can no longer boot my Sarge laptop. Here are the last few lines of
>> boot up:
>>
>> VFS: Mounted root (ext3 filesystem) readonly.
>> Fr
s that the best way to do it?
I've got a log of most of the updates I've done.
Thanks again,
Rich B
Original post:
>> I can no longer boot my Sarge laptop. Here are the last few lines of
>> boot up:
>>
>> VFS: Mounted root (ext3 filesystem) readonly.
>> F
Rich <[EMAIL PROTECTED]> writes:
> I can no longer boot my Woody laptop. Here are the last few lines of
> boot up:
>
> VFS: Mounted root (ext3 filesystem) readonly.
> Freeing unused kernel momory 208k freed
> kernel panic: No init found. Try passing init=
All,
I can no longer boot my Woody laptop. Here are the last few lines of
boot up:
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel momory 208k freed
kernel panic: No init found. Try passing init= option to kernel.
I use GRUB and have tried adding the kernel parameters
On Sat, 2002-12-28 at 18:31, Eric G. Miller wrote:
> AFAIK, change to "kernel /vmlinuz ro root=/dev/hda2 vga=788"
>
> I'm not familiar with the "root=LABEL=/" syntax. The root= should
> translate into a device/partition name per Linux naming.
Brilliant! I got it working, hmmm I never noticed th
On Sat, Dec 28, 2002 at 04:18:37PM +0900, Elijah wrote:
> Hello,
>
> got this error upon booting to debian, here's some details on the boot
[snip]
> Kernel panic: I have no root and I want to scream
> ---
>
> here's my grub menu.lst
> --
unted
...
...
Kernel panic: I have no root and I want to scream
---
here's my grub menu.lst
title Debian
root (hd0,1)
kernel /vmlinuz ro root=LABEL=/ vga=788
I've reintalled Debian woody 3 times, a
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 th
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
igured as modules.
>
> Unfortunately, I don't.
>
> > If you got i.e a driver for the wrong sound card compiled in the kernel
> > it can give you a kernel panic.If it is compiled as module the module
> > just doesn't load.
>
> Perhaps, but I doubt anything
"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
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 a
On Fri, 2002-12-06 at 17:54, Paul Johnson wrote:
> You can't get away with having your root partition being a
> filesystem for which you must load a module to support. Unless you
> use initrd, but that's messy and not very failproof.
It is? I thought that was the usual way to do it (with 2.4 ker
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
the wrong sound card compiled in the kernel
> it can give you a kernel panic.If it is compiled as module the module
> just doesn't load.
Perhaps, but I doubt anything like that can cause this particular kernel
panic.
Anyway, I've been able to boot a vanilla 2.4.20 kernel, and I'
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
> >
_request: I/O error, dev 16:06 (hdc), sector 2
>> EXT3-fs: Unable to read superblock
>> hdc6: bad access: block=3D2, count=3D2
>> end_request: I/O error, dev 16:06 (hdc), sector 2
>> EXT2-fs: Unable to read superblock
>> hdc6: bad access: block=3D0, count=3D1
>&g
Paul Johnson said:
> Whoa! Huge kernel! Module some of that stuff out and it should
> help if there's some hidden size limitation. I have a pretty big
> kernel, the bzImage is 644,225 bytes.
sounds like a 2.4.x kernel. I was amazed how huge the 2.4.x kernel
got. my biggest 2.2.x kernel I think
I/O error, dev 16:06 (hdc), sector 2
> EXT2-fs: Unable to read superblock
> hdc6: bad access: block=0, count=1
> end_request: I/O error, dev 16:06 (hdc), sector 0
> NTFS: Reading super block failed
> Kernel panic: VFS: Unable to mount root fs on 16:06
Is your drive going bad? Are the file
end_request: I/O error, dev 16:06 (hdc), sector 2
EXT2-fs: Unable to read superblock
hdc6: bad access: block=0, count=1
end_request: I/O error, dev 16:06 (hdc), sector 0
NTFS: Reading super block failed
Kernel panic: VFS: Unable to mount root fs on 16:06
While some googling revealed that I&#
the IOpener, I get:
> > > > VFS: Cannot open root device "301" or 03:01
> > > > Please append a correct "root=" boot option
> > > > Kernel panic: VFS: Unable to mount root fs on
> > > 03:01
> > >
> > > The IOpe
"Travis" == Travis Crump <[EMAIL PROTECTED]> writes:
Travis> Based on the theory that a kernel image would only depend
Travis> on initrd-tools if it used an initrd.img, I checked the
Travis> reverse depends section for initrd-tools and since at
Travis> least 2.4.12[the first 2.
On Sun, Nov 24, 2002 at 01:49:07PM -0700, Tom Schutter wrote:
| On Sun, 2002-11-24 at 07:44, Charles Baker wrote:
| > I had the same problem when I first moved to a 2.4.x
| > kernel on a plain intel based machine. The problem wa
| > slack of initrd line in lilo.conf . For example,
| >
| > image=/
Tom Schutter wrote:
On Sat, 2002-11-23 at 22:30, Travis Crump wrote:
You need a line:
initrd=/boot/initrd.img-2.4.19-bf2.4
in the image section of your lilo.conf[assuming initrd.img-2.4.19-bf2.4
exists, it should or something very similarly named]. Also, it is my
understanding that 2.4.19-bf2
n another machine, and
> > then hooking it up to
> > > the IOpener and attempting to boot. When I
> > attempt to boot with the
> > > drive in the IOpener, I get:
> > > VFS: Cannot open root device "301" or 03:01
> > > Please append a corre
ot with the
> > drive in the IOpener, I get:
> > VFS: Cannot open root device "301" or 03:01
> > Please append a correct "root=" boot option
> > Kernel panic: VFS: Unable to mount root fs on 03:01
> >
> > I have tried to add root=/dev/hda1
On Sun, 2002-11-24 at 07:26, Torsten Wolny wrote:
> Hi,
>
> Am Sonntag, 24. November 2002 15:05 schrieb Tom Schutter:
> > > The IOpener may not be seeing the disk as hda (aka 03:01).
> > > Please post the messages before that as it may tell you what
> > > the kernel thinks the disk is called, or
ting to boot. When I
> attempt to boot with the
> > drive in the IOpener, I get:
> > VFS: Cannot open root device "301" or 03:01
> > Please append a correct "root=" boot option
> > Kernel panic: VFS: Unable to mount root fs on
> 03:01
>
>
Hi,
Am Sonntag, 24. November 2002 15:05 schrieb Tom Schutter:
> > The IOpener may not be seeing the disk as hda (aka 03:01).
> > Please post the messages before that as it may tell you what
> > the kernel thinks the disk is called, or if it doesn't see it
> > at all.
>
> Is there a way that I can
ot. When I attempt to boot with the
> > drive in the IOpener, I get:
> > VFS: Cannot open root device "301" or 03:01
> > Please append a correct "root=" boot option
> > Kernel panic: VFS: Unable to mount root fs on 03:01
>
> The IOpener may not b
et:
> VFS: Cannot open root device "301" or 03:01
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 03:01
The IOpener may not be seeing the disk as hda (aka 03:01). Please post
the messages before that as it may tell you what
uot; or 03:01
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 03:01
I have tried to add root=/dev/hda1 to the boot prompt with no success.
I can boot fine to the drive when it is hooked up to my desktop
machine.
"uname -a" gives:
Li
e append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 03:01
I have tried to add root=/dev/hda1 to the boot prompt with no success.
I can boot fine to the drive when it is hooked up to my desktop
machine.
"uname -a" gives:
Linux newman 2.4.18-bf2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 02 November 2002 7:14 pm, Mariano Kamp wrote:
> Hi,
>
> no need to further look at the problem. I am now using the ide drive
> as my primary drive and that seems to work. Its just amazing that it did
> work before with SuSE also using LIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 02 November 2002 8:35 am, Mariano Kamp wrote:
> I was unsure what to do with the type of partition when fdisking my
> hd. I left the type as "eightysomething - linux" as I haven't found
> ReiserFS as a vaild type.
I don't know off the to
Hi,
no need to further look at the problem. I am now using the ide drive
as my primary drive and that seems to work. Its just amazing that it did
work before with SuSE also using LILO
Anyway ... thx very much for your help.
Mariano
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wit
Last night all was well, this morning -> no boot.
ds: 0018 es: 0018ss: 0018
Process insmod (pid: 220, stackpage=c05b1000)
Stack: c05ff3eo c01154e6 c032eca0 c0399d89 18c9 c05b1d4c
3 more lines of address',...
Call Trace: [] [] [] [] []
7 more lines of []
Last night all was well, this morning -> no boot.
ds: 0018 es: 0018ss: 0018
Process insmod (pid: 220, stackpage=c05b1000)
Stack: c05ff3eo c01154e6 c032eca0 c0399d89 18c9 c05b1d4c
3 more lines of address',...
Call Trace: [] [] [] [] []
7 more lines of []
Hi Alan,
ok, it's good to hear that it would be possible to use ReiserFS out of
the box. Still I am wondering which problem I did hit then?
In the posting of Seneca he quoted the explanation regarding the lilo
error messages. As far as I understood there is a serious problem with
my hard disk
"Mariano" == Mariano Kamp <[EMAIL PROTECTED]> writes:
Mariano> Seneca, thank you. That was an impressive answer.
>> Does your kernel have reiserfs support compiled into it ( not
>> module)? You can check in /boot/config-$KERNEL
Mariano> To be honest .. I don't know for certai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 01 November 2002 9:29 pm, Seneca wrote:
>
> Reiser and EXT3 are compiled as modules with the Debian kernel that I
> have here (2.4.19-586tsc). Your rootfs cannot be compiled as a module.
> For your system to boot, you need to use a different
g: BIOS drive 0x may not be accessible"
> in section "Warnings".
>
> > Using the CDROM to boot the system and issuing the following commands
> > at the lilo prompt
> >
> > A. rescue boot=/dev/sda
> > B. rescue boot=/dev/sda1
rompt
>
> A. rescue boot=/dev/sda
> B. rescue boot=/dev/sda1
> C. rescue boot=/dev/sda3
>
> Linux comes up, but panics. The last lines read like this:
>
> [network stuff]
> Partition check:
>hda: [PTBL] [2433/255/63] h
boot=/dev/sda3
Linux comes up, but panics. The last lines read like this:
[network stuff]
Partition check:
hda: [PTBL] [2433/255/63] hda1 hda2 < hda5 hda6 >
[ apm stuff ]
request_module[block-major-58]: Root fs not mounted
VFS: Cannot open roo
Mykl said:
> Hi,
>
> I have a Compaq Proliant ML 330 with an 18 GB SCSI hard-drive and another
> hot-plug able SCSI HDD of the same capacity.
> I want to install Debian Potato on this machine as in I would like to use
> it as a DNS, Mail, Proxy Server.
> During boot up they system this error
>
any
Hi,
I have a Compaq Proliant ML 330 with an 18 GB SCSI hard-drive and another
hot-plug able SCSI HDD of the same capacity.
I want to install Debian Potato on this machine as in I would like to use it
as a DNS, Mail, Proxy Server.
During boot up they system this error
Kernel Panic: VFS: Unable
Russell, Thanks, I've been trying to get a grasp of this, I'm sure this will
help!
Best Wishes!
Mike Olds www.buddhadust.org
-Original Message-
From: Russell [mailto:[EMAIL PROTECTED]]
Sent: Sunday, October 13, 2002 6:55 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject:
Russell wrote:
>
> Michael Olds wrote:
> >
> > Russell,
> >
> > Ok...I am going to remake my package...
...
> echo "System backup successful"
> exit 0
I forgot to update the script. Change ext2 to ext3 if that's what
you have.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "
Michael Olds wrote:
>
> Russell,
>
> Ok...I am going to remake my package...without initrd as I thought it not
> such a good idea to have my main file system as a module and so included it
> in the kernel.
>
> You say: Backup your HDD. Easy for you to say: I come from Windows where I
> press tw
ou are intending to use the system for. This you need to work out yourself.
> Once this is figured out, it might be helpful, on the first rebuild, to make
> your updates with reference to the original configuration, (called
> config-2.4.18bf24 (or your kernel version)) which you should fin
]
Subject: Re: Kernel Panic~: Rebuild Kernel: miniHOWTO draft .001
Michael Olds wrote:
>
> Russel...noted and I will do a revision shortly...however I got as far as
> making the package with the --initrd option and managed to control my
> fingers long enough to read the caution about editing
HELP option for brief explanations. This at least until you
understand which can be safely changed under your setup.
Note: If you're using --initrd, make sure "Compressed ROM file system
support" is built in, or you'll get a kernel panic (need CramFS).
(Side note: I see that a
501 - 600 of 1036 matches
Mail list logo
