subject:"RE\: Kernel panic"

Re: Kernel panic....

2024-07-08 Thread Henning Follmann

On Sun, Jul 07, 2024 at 07:07:26PM -0700, Van Snyder wrote:
> I recently installed Debian 12.5 with kernel 6.5.0.0 on an antique Dell
> Vostro 1700. Occasionally it crashes with
>

So you installed this kernel from where?

Stable (Debian 12/ bookworm) uses linux kernal 6.1.XXX

> "Kernel Panic - not syncing: Can not allocate SWIOTLB buffer earlier
> and can't now provide you with the DMA bounce buffer"
> 
> I saw some remarks about this from 2013 in the context of release 3.5.
> 
> Is this a problem in the kernel, or is the computer broken?
> 
> Should I revert to an earlier release?

Maybe try the official kernel?


-H 

-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: Kernel panic....

2024-07-08 Thread Andrew M.A. Cater

On Sun, Jul 07, 2024 at 07:07:26PM -0700, Van Snyder wrote:
> I recently installed Debian 12.5 with kernel 6.5.0.0 on an antique Dell
> Vostro 1700. Occasionally it crashes with
> 
> "Kernel Panic - not syncing: Can not allocate SWIOTLB buffer earlier
> and can't now provide you with the DMA bounce buffer"
> 

Hi,

As suggested, use the Debian 6.1 kernel.

This is a laptop from around 2008 if I'm reading the spec. correctly.
This is a laptop with an older Nvidia card. How did you install it?
Did you try to install the Nvidia drivers at any point? I can't 
find out whether this is one of the machines that has dual chipsets
(one Intel / one Nvidia). If so, have you used the instructions
for bumblebee/primus or whatever the appropriate magic now is?

> I saw some remarks about this from 2013 in the context of release 3.5.
> 
> Is this a problem in the kernel, or is the computer broken?
> 
> Should I revert to an earlier release?
> 
>

Ideally, if you're running Debian stable, don't revert to prior versions.

Apt-get update to ensure that you're running the latest point release.

All the very best, as ever,

Andy
(amaca...@debian.org)

Re: Kernel panic....

2024-07-08 Thread Van Snyder

On Mon, 2024-07-08 at 17:46 +, Andrew M.A. Cater wrote:
> On Sun, Jul 07, 2024 at 07:07:26PM -0700, Van Snyder wrote:
> > I recently installed Debian 12.5 with kernel 6.5.0.0 on an antique
> > Dell
> > Vostro 1700. Occasionally it crashes with
> > 
> > "Kernel Panic - not syncing: Can not allocate SWIOTLB buffer
> > earlier
> > and can't now provide you with the DMA bounce buffer"
> > 
> 
> Hi,
> 
> As suggested, use the Debian 6.1 kernel.
> 
> This is a laptop from around 2008 if I'm reading the spec. correctly.
> This is a laptop with an older Nvidia card. How did you install it?
> Did you try to install the Nvidia drivers at any point? I can't 
> find out whether this is one of the machines that has dual chipsets
> (one Intel / one Nvidia). If so, have you used the instructions
> for bumblebee/primus or whatever the appropriate magic now is?

I tried unsuccessfully to install the NVidia 340 driver from the NVidia
drivers page. I found a SourceForge/GitHub page by MeowIce that had the
patched driver, but not for kernel 6.1, so I installed 6.5.0.0 from
backports-bookworm and the patched NVidia 340 driver. That also didn't
work, so I reinstalled bog-standard Debian 12.5 with the 6.1 kernel
using the net-install ISO from the Debian site. It doesn't have dual
graphic chipsets. The video driver is nouveau.

> 
> > I saw some remarks about this from 2013 in the context of release
> > 3.5.
> > 
> > Is this a problem in the kernel, or is the computer broken?
> > 
> > Should I revert to an earlier release?
> > 
> > 
> 
> Ideally, if you're running Debian stable, don't revert to prior
> versions.
> 
> Apt-get update to ensure that you're running the latest point
> release.
> 
> All the very best, as ever,
> 
> Andy
> (amaca...@debian.org) 
>

Re: Kernel Panic

2020-01-26 Thread Keith Bainbridge


try sudo apt-get update

Keith Bainbridge

keith.bainbridge.3...@gmail.com
0447 667 468

On 27/1/20 5:24 pm, William Torrez Corea wrote:

sudo apt get update

Re: Kernel Panic

2020-01-26 Thread john doe

On 1/27/2020 7:24 AM, William Torrez Corea wrote:
> I get the following error, when i send this command
> sudo apt get update
>
> sudo: unable to resolve host debian: Temporary failure in name resolution
> apt: relocation error: /lib/x86_64-linux-gnu/libgcrypt.so.20: symbol
> gpgrt_get_syscall_clamp version GPG_ERROR_1.0 not defined in file
> libgpg-error.so.0 with link time reference
>
> I'm trying found a solution, but i don't get results.
>
> Follow the following steps
> https://gutl.jovenclub.cu/chroot-la-salvacion-elegante-ante-un-kernel-panic/
>

You can only use 'apt-get' or 'apt' but not both at the same time.

$ sudo apt-get update
$sudo apt update

However, it looks like your GPG installation is broken.

--
John Doe

Re: Kernel Panic

2020-01-26 Thread john doe

On 1/27/2020 8:20 AM, William Torrez Corea wrote:
> Ready. I configure Ligpg-error and Libgcrypt but i now get the following
> error:
>
> E: List directory /var/lib/apt/lists/partial is missing. - Acquire (2: No
> such file or directory)
> E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or
> directory)
> E: Could not open file  - open (2: No such file or directory)
> E: Problem opening
> E: The package lists or status file could not be parsed or opened.
>
> On Mon, Jan 27, 2020 at 6:59 AM john doe  wrote:
>
>> On 1/27/2020 7:24 AM, William Torrez Corea wrote:
>>> I get the following error, when i send this command
>>> sudo apt get update
>>>
>>> sudo: unable to resolve host debian: Temporary failure in name resolution
>>> apt: relocation error: /lib/x86_64-linux-gnu/libgcrypt.so.20: symbol
>>> gpgrt_get_syscall_clamp version GPG_ERROR_1.0 not defined in file
>>> libgpg-error.so.0 with link time reference
>>>
>>> I'm trying found a solution, but i don't get results.
>>>
>>> Follow the following steps
>>>
>> https://gutl.jovenclub.cu/chroot-la-salvacion-elegante-ante-un-kernel-panic/
>>>
>>
>> You can only use 'apt-get' or 'apt' but not both at the same time.
>>
>> $ sudo apt-get update
>> $sudo apt update
>>
>> However, it looks like your GPG installation is broken.
>>
>> --
>> John Doe
>>
>>
>

Try this:

$ rm -r /var/lib/apt/*
$ apt-get update


Please post through the list.

--
John Doe

Re: Kernel Panic

2020-01-26 Thread deloptes

john doe wrote:

> On 1/27/2020 7:24 AM, William Torrez Corea wrote:
>> I get the following error, when i send this command
>> sudo apt get update
>>
>> sudo: unable to resolve host debian: Temporary failure in name resolution
>> apt: relocation error: /lib/x86_64-linux-gnu/libgcrypt.so.20: symbol
>> gpgrt_get_syscall_clamp version GPG_ERROR_1.0 not defined in file
>> libgpg-error.so.0 with link time reference
>>
>> I'm trying found a solution, but i don't get results.
>>
>> Follow the following steps
>>
https://gutl.jovenclub.cu/chroot-la-salvacion-elegante-ante-un-kernel-panic/
>>
> 
> You can only use 'apt-get' or 'apt' but not both at the same time.
> 
> $ sudo apt-get update
> $sudo apt update
> 
> However, it looks like your GPG installation is broken.
> 
> --
> John Doe

GPG_ERROR_1.0 is fundamental. It is in buster
in /lib/x86_64-linux-gnu/libgpg-error.so.0.26.1, if I am not wrong.

nm -DC /lib/x86_64-linux-gnu/libgpg-error.so.0.26.1| grep
gpgrt_get_syscall_clamp
ef50 T gpgrt_get_syscall_clamp

And gcrypt is libcrypt-2.28.so not .so.20

perhaps something is wrong with the library paths setup on the system

perhaps you have some custom installed software loading libraries before the
system libraries. Could be also libraries are missing and some left over
has appeared or similar.

Re: Kernel Panic

2020-01-27 Thread deloptes

deloptes wrote:

> And gcrypt is libcrypt-2.28.so not .so.20

sorry I was wrong about that /lib/x86_64-linux-gnu/libgcrypt.so.20 is linked
to /lib/x86_64-linux-gnu/libgpg-error.so.0

check where the link is pointing to

ldd /lib/x86_64-linux-gnu/libgcrypt.so.20
linux-vdso.so.1 (0x7ffebd761000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0
(0x7f0628e58000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f0628c97000)
/lib64/ld-linux-x86-64.so.2 (0x7f0628fce000)

Re: Kernel Panic

2006-12-13 Thread Erico Schuch


Same as I have.
I found that the 2.6 pre-compiled debian kernel is using ext3, reiser 
and others fs as modules. I  did :

# apt-get install kernel-image.2.6XXX
# apt-get install kernel-source.2.6XXX
# apt-get install kernel-tree.2.6XXX
The last "apt-get" I think its no necessary.
note the XXX ! please change to your kernel variant. My is 686!
Then :
cd /usr/src
# tar xjf kernel-source-2.6XXX
# cp /boot/config-2.6* kernel-source-2.6XXX/.config
# cd kernel-source-2.6XXX
# make menuconfig
Configured to use ext3, xfs and reiserfs not as modules. Save and quit 
the menu.

# make-kpkg --initrd --us --uc kernel_image
# dpkg -i kernel-image-2.6_10.00.Custom_iXXX.deb
after all, I remove the lilo.conf and generate another as I don´t realy 
care about lilo

# rm /etc/lilo.conf
# liloconfig
# reboot

Good luck

Erico Schuch

Morgan Walker escreveu:


Hey guys,

 

After updating to 2.6.16-2-amd64-k8-smp on my Sun X4100 I rebooted and 
got the following error:


 


VFS: Cannot open root device md0 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)


 

And this is where it will stop during the boot process.  I am running 
a RAID1 on this machine.  When the screen comes up to choose which 
kernel I want to boot, I press "e" to edit the grub/menu.list, but all 
looks well.  Here is what I have:


 


root(hd0,0)

kernel  /boot/vmlinuz-2.6.16-2-amd64-k8-smp root=/dev/md0 ro

initrd  /boot/initrd.img-2.6.16-2-amd64-k8-smp

savedefault

 


I'm stumped, what options do I have?

 


Thanks in advance,

 


Morgan

 


**Morgan Walker**

**Systems Administrator/Engineer**

**M·CAM, Inc.**

**210 Ridge-McIntire Rd., Suite 300**

**Charlottesville, VA 22903**

**434-979-7240 x311**

 


http://www.m-cam.com
=
This message, including any attachments, is intended solely for the use
of the named recipient(s) and may contain confidential and/or
privileged information.  Any unauthorized review, use, disclosure or
distribution of this communication(s) is expressly prohibited.
If you are not the intended recipient, please contact the sender by
reply e-mail and destroy any and all copies of the original message.
Thank you.
=

Re: Kernel Panic

2006-12-13 Thread Alan Ianson

On Wed December 13 2006 08:10, Morgan Walker wrote:
> Hey guys,
>
>
>
> After updating to 2.6.16-2-amd64-k8-smp on my Sun X4100 I rebooted and
> got the following error:
>
>
>
> VFS: Cannot open root device md0 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)
>
>
>
> And this is where it will stop during the boot process.  I am running a
> RAID1 on this machine.  When the screen comes up to choose which kernel
> I want to boot, I press "e" to edit the grub/menu.list, but all looks
> well.  Here is what I have:
>
>
>
> root(hd0,0)
>
> kernel  /boot/vmlinuz-2.6.16-2-amd64-k8-smp root=/dev/md0 ro
>
> initrd  /boot/initrd.img-2.6.16-2-amd64-k8-smp

I thought the amd64-k8 and -smp kernels were merged into the -amd64.

> I'm stumped, what options do I have?

If you really have a kernel like that in /boot I'm stumped too.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Kernel Panic

2006-12-13 Thread Erico Schuch


Erico Schuch escreveu:

Same as I have.

Correction HAD ;)
I found that the 2.6 pre-compiled debian kernel is using ext3, reiser 
and others fs as modules. I  did :

# apt-get install kernel-image.2.6XXX
# apt-get install kernel-source.2.6XXX
# apt-get install kernel-tree.2.6XXX
The last "apt-get" I think its no necessary.
note the XXX ! please change to your kernel variant. My is 686!
Then :
cd /usr/src
# tar xjf kernel-source-2.6XXX
# cp /boot/config-2.6* kernel-source-2.6XXX/.config
# cd kernel-source-2.6XXX
# make menuconfig
Configured to use ext3, xfs and reiserfs not as modules. Save and quit 
the menu.

# make-kpkg --initrd --us --uc kernel_image
# dpkg -i kernel-image-2.6_10.00.Custom_iXXX.deb
after all, I remove the lilo.conf and generate another as I don´t 
realy care about lilo

# rm /etc/lilo.conf
# liloconfig
# reboot

Good luck

Erico Schuch

Morgan Walker escreveu:


Hey guys,

 

After updating to 2.6.16-2-amd64-k8-smp on my Sun X4100 I rebooted 
and got the following error:


 


VFS: Cannot open root device md0 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)


 

And this is where it will stop during the boot process.  I am running 
a RAID1 on this machine.  When the screen comes up to choose which 
kernel I want to boot, I press "e" to edit the grub/menu.list, but 
all looks well.  Here is what I have:


 


root(hd0,0)

kernel  /boot/vmlinuz-2.6.16-2-amd64-k8-smp root=/dev/md0 ro

initrd  /boot/initrd.img-2.6.16-2-amd64-k8-smp

savedefault

 


I'm stumped, what options do I have?

 


Thanks in advance,

 


Morgan

 


**Morgan Walker**

**Systems Administrator/Engineer**

**M·CAM, Inc.**

**210 Ridge-McIntire Rd., Suite 300**

**Charlottesville, VA 22903**

**434-979-7240 x311**

 


http://www.m-cam.com
=
This message, including any attachments, is intended solely for the use
of the named recipient(s) and may contain confidential and/or
privileged information.  Any unauthorized review, use, disclosure or
distribution of this communication(s) is expressly prohibited.
If you are not the intended recipient, please contact the sender by
reply e-mail and destroy any and all copies of the original message.
Thank you.
=

RE: Kernel Panic

2006-12-13 Thread Morgan Walker

Thing is I can't get into a terminal to use APT, it freezes right after this 
error:-(.

 

~Morgan

 



From: Erico Schuch [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, December 13, 2006 11:54 AM
To: Erico Schuch
Cc: Morgan Walker; debian-user@lists.debian.org
Subject: Re: Kernel Panic

 

Erico Schuch escreveu: 

Same as I have.

Correction HAD ;)



I found that the 2.6 pre-compiled debian kernel is using ext3, reiser and 
others fs as modules. I  did :
# apt-get install kernel-image.2.6XXX
# apt-get install kernel-source.2.6XXX
# apt-get install kernel-tree.2.6XXX 
The last "apt-get" I think its no necessary.
note the XXX ! please change to your kernel variant. My is 686!
Then : 
cd /usr/src
# tar xjf kernel-source-2.6XXX
# cp /boot/config-2.6* kernel-source-2.6XXX/.config
# cd kernel-source-2.6XXX
# make menuconfig
Configured to use ext3, xfs and reiserfs not as modules. Save and quit the menu.
# make-kpkg --initrd --us --uc kernel_image
# dpkg -i kernel-image-2.6_10.00.Custom_iXXX.deb
after all, I remove the lilo.conf and generate another as I don´t realy care 
about lilo
# rm /etc/lilo.conf
# liloconfig
# reboot 

Good luck

Erico Schuch

Morgan Walker escreveu: 

Hey guys,

 

After updating to 2.6.16-2-amd64-k8-smp on my Sun X4100 I rebooted and got the 
following error:

 

VFS: Cannot open root device md0 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)

 

And this is where it will stop during the boot process.  I am running a RAID1 
on this machine.  When the screen comes up to choose which kernel I want to 
boot, I press "e" to edit the grub/menu.list, but all looks well.  Here is what 
I have:

 

root(hd0,0)

kernel  /boot/vmlinuz-2.6.16-2-amd64-k8-smp root=/dev/md0 ro

initrd  /boot/initrd.img-2.6.16-2-amd64-k8-smp

savedefault

 

I'm stumped, what options do I have?

 

Thanks in advance,

 

Morgan

 

Morgan Walker

Systems Administrator/Engineer

M·CAM, Inc.

210 Ridge-McIntire Rd., Suite 300

Charlottesville, VA 22903

434-979-7240 x311

 

http://www.m-cam.com 
=
This message, including any attachments, is intended solely for the use
of the named recipient(s) and may contain confidential and/or
privileged information.  Any unauthorized review, use, disclosure or
distribution of this communication(s) is expressly prohibited.
If you are not the intended recipient, please contact the sender by
reply e-mail and destroy any and all copies of the original message.
Thank you. 
=

Re: Kernel Panic

2006-12-13 Thread Erico Schuch

As a install of a new kernel, I sugest you to make some "tools" beforer 
doing it.

A live CD is a good start.
Use a live-cd that have the same kernel/distribution that was in your 
machine.

If you have some live cd, boot your machine with it.
Turn to a tty, mount the original "/" of the HD in new place ("/disc" is 
a good place!)

mount the disc as it is in the hd etc/fstab
execut the command pivo_root to the new HD mount point.
Give a init 3 if the interfaces aren´t up.
then exec as I discribe before.

Good luck ;)

Erico Schuch

Morgan Walker escreveu:


Thing is I can't get into a terminal to use APT, it freezes right 
after this errorL.


 


~Morgan

Re: Kernel Panic

2006-12-13 Thread Andrew Sackville-West

On Wed, Dec 13, 2006 at 11:57:56AM -0500, Morgan Walker wrote:
> Thing is I can't get into a terminal to use APT, it freezes right after this 
> error:-(.

did you delete the other kernels? if you did, then you need to, as
Erico suggested, boot with a live-cd (knoppix?) and chroot into your
system to fix it. 

if you still have other kernels installed, then use grub to manually
boot one of the other kernels.

grub> root (0,0)
grub> kernel /boot/vmlinuz-2.6.X root=/dev/md0 ro
grub> initrd /boot/initrd.img-2.6.
grub> boot

good luck

A

signature.asc
Description: Digital signature

Re: Kernel Panic

2006-12-13 Thread Erico Schuch



Sory, but I din´t discribe to you why it hapens.

The fs tha you use in /boot is not ext2.
Ext2 is the only thing that is load by kernel as standart. Not as a module.
As you update to a pre-compiled kernel image, its assume that you have 
/boot as ext2. (strange but that is!)
As you boot your machine, it get stok, because the kernel don´t 
understand what tipe of fs you are using.




Morgan Walker escreveu:


Thing is I can't get into a terminal to use APT, it freezes right 
after this errorL.


 


~Morgan

 




*From:* Erico Schuch [mailto:[EMAIL PROTECTED]
*Sent:* Wednesday, December 13, 2006 11:54 AM
*To:* Erico Schuch
*Cc:* Morgan Walker; debian-user@lists.debian.org
*Subject:* Re: Kernel Panic

 


Erico Schuch escreveu:

Same as I have.

Correction HAD ;)

I found that the 2.6 pre-compiled debian kernel is using ext3, reiser 
and others fs as modules. I  did :

# apt-get install kernel-image.2.6XXX
# apt-get install kernel-source.2.6XXX
# apt-get install kernel-tree.2.6XXX
The last "apt-get" I think its no necessary.
note the XXX ! please change to your kernel variant. My is 686!
Then :
cd /usr/src
# tar xjf kernel-source-2.6XXX
# cp /boot/config-2.6* kernel-source-2.6XXX/.config
# cd kernel-source-2.6XXX
# make menuconfig
Configured to use ext3, xfs and reiserfs not as modules. Save and quit 
the menu.

# make-kpkg --initrd --us --uc kernel_image
# dpkg -i kernel-image-2.6_10.00.Custom_iXXX.deb
after all, I remove the lilo.conf and generate another as I don´t 
realy care about lilo

# rm /etc/lilo.conf
# liloconfig
# reboot

Good luck

Erico Schuch

Morgan Walker escreveu:

Hey guys,

 

After updating to 2.6.16-2-amd64-k8-smp on my Sun X4100 I rebooted and 
got the following error:


 


VFS: Cannot open root device md0 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)


 

And this is where it will stop during the boot process.  I am running 
a RAID1 on this machine.  When the screen comes up to choose which 
kernel I want to boot, I press "e" to edit the grub/menu.list, but all 
looks well.  Here is what I have:


 


root(hd0,0)

kernel  /boot/vmlinuz-2.6.16-2-amd64-k8-smp root=/dev/md0 ro

initrd  /boot/initrd.img-2.6.16-2-amd64-k8-smp

savedefault

 


I'm stumped, what options do I have?

 


Thanks in advance,

 


Morgan

 


**Morgan Walker**

**Systems Administrator/Engineer**

**M·CAM, Inc.**

**210 Ridge-McIntire Rd., Suite 300**

**Charlottesville, VA 22903**

**434-979-7240 x311**

 


http://www.m-cam.com
=
This message, including any attachments, is intended solely for the use
of the named recipient(s) and may contain confidential and/or
privileged information.  Any unauthorized review, use, disclosure or
distribution of this communication(s) is expressly prohibited.
If you are not the intended recipient, please contact the sender by
reply e-mail and destroy any and all copies of the original message.
Thank you.
=

Re: Kernel Panic

2006-12-13 Thread Alan Ianson

On Wed December 13 2006 08:57, Morgan Walker wrote:
> Thing is I can't get into a terminal to use APT, it freezes right after
> this error:-(.

Is grub your boot loader? If so I would hit "e" at the grub screen to edit 
your kernel and initrd lines. On my amd64 box I have symlinks in / that point 
to the actual kernel and initrd. I would try...

kernel  /vmlinuz root=/dev/md0 ro

and...

initrd  /initrd.img

Just a shot, not sure if that will work there or not.

> From: Erico Schuch [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 13, 2006 11:54 AM
> To: Erico Schuch
> Cc: Morgan Walker; debian-user@lists.debian.org
> Subject: Re: Kernel Panic
>
>
>
> Erico Schuch escreveu:
>
> Same as I have.
>
> Correction HAD ;)
>
>
>
> I found that the 2.6 pre-compiled debian kernel is using ext3, reiser and
> others fs as modules. I  did : # apt-get install kernel-image.2.6XXX
> # apt-get install kernel-source.2.6XXX
> # apt-get install kernel-tree.2.6XXX
> The last "apt-get" I think its no necessary.
> note the XXX ! please change to your kernel variant. My is 686!
> Then :
> cd /usr/src
> # tar xjf kernel-source-2.6XXX
> # cp /boot/config-2.6* kernel-source-2.6XXX/.config
> # cd kernel-source-2.6XXX
> # make menuconfig
> Configured to use ext3, xfs and reiserfs not as modules. Save and quit the
> menu. # make-kpkg --initrd --us --uc kernel_image
> # dpkg -i kernel-image-2.6_10.00.Custom_iXXX.deb
> after all, I remove the lilo.conf and generate another as I don´t realy
> care about lilo # rm /etc/lilo.conf
> # liloconfig
> # reboot
>
> Good luck
>
> Erico Schuch
>
> Morgan Walker escreveu:
>
> Hey guys,
>
>
>
> After updating to 2.6.16-2-amd64-k8-smp on my Sun X4100 I rebooted and got
> the following error:
>
>
>
> VFS: Cannot open root device md0 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)
>
>
>
> And this is where it will stop during the boot process.  I am running a
> RAID1 on this machine.  When the screen comes up to choose which kernel I
> want to boot, I press "e" to edit the grub/menu.list, but all looks well. 
> Here is what I have:
>
>
>
> root(hd0,0)
>
> kernel  /boot/vmlinuz-2.6.16-2-amd64-k8-smp root=/dev/md0 ro
>
> initrd  /boot/initrd.img-2.6.16-2-amd64-k8-smp
>
> savedefault
>
>
>
> I'm stumped, what options do I have?
>
>
>
> Thanks in advance,
>
>
>
> Morgan
>
>
>
> Morgan Walker
>
> Systems Administrator/Engineer
>
> M·CAM, Inc.
>
> 210 Ridge-McIntire Rd., Suite 300
>
> Charlottesville, VA 22903
>
> 434-979-7240 x311
>
>
>
> http://www.m-cam.com
> =
> This message, including any attachments, is intended solely for the use
> of the named recipient(s) and may contain confidential and/or
> privileged information.  Any unauthorized review, use, disclosure or
> distribution of this communication(s) is expressly prohibited.
> If you are not the intended recipient, please contact the sender by
> reply e-mail and destroy any and all copies of the original message.
> Thank you.
> =

RE: Kernel Panic

2006-12-13 Thread Morgan Walker

Alan that did not work.  

Erico, in your steps, did you mean:

apt-get install linux-source.2.6.XXX?



-Original Message-
From: Alan Ianson [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, December 13, 2006 2:51 PM
To: debian-user@lists.debian.org
Subject: Re: Kernel Panic

On Wed December 13 2006 08:57, Morgan Walker wrote:
> Thing is I can't get into a terminal to use APT, it freezes right after
> this error:-(.

Is grub your boot loader? If so I would hit "e" at the grub screen to edit 
your kernel and initrd lines. On my amd64 box I have symlinks in / that point 
to the actual kernel and initrd. I would try...

kernel  /vmlinuz root=/dev/md0 ro

and...

initrd  /initrd.img

Just a shot, not sure if that will work there or not.

> From: Erico Schuch [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 13, 2006 11:54 AM
> To: Erico Schuch
> Cc: Morgan Walker; debian-user@lists.debian.org
> Subject: Re: Kernel Panic
>
>
>
> Erico Schuch escreveu:
>
> Same as I have.
>
> Correction HAD ;)
>
>
>
> I found that the 2.6 pre-compiled debian kernel is using ext3, reiser and
> others fs as modules. I  did : # apt-get install kernel-image.2.6XXX
> # apt-get install kernel-source.2.6XXX
> # apt-get install kernel-tree.2.6XXX
> The last "apt-get" I think its no necessary.
> note the XXX ! please change to your kernel variant. My is 686!
> Then :
> cd /usr/src
> # tar xjf kernel-source-2.6XXX
> # cp /boot/config-2.6* kernel-source-2.6XXX/.config
> # cd kernel-source-2.6XXX
> # make menuconfig
> Configured to use ext3, xfs and reiserfs not as modules. Save and quit the
> menu. # make-kpkg --initrd --us --uc kernel_image
> # dpkg -i kernel-image-2.6_10.00.Custom_iXXX.deb
> after all, I remove the lilo.conf and generate another as I don´t realy
> care about lilo # rm /etc/lilo.conf
> # liloconfig
> # reboot
>
> Good luck
>
> Erico Schuch
>
> Morgan Walker escreveu:
>
> Hey guys,
>
>
>
> After updating to 2.6.16-2-amd64-k8-smp on my Sun X4100 I rebooted and got
> the following error:
>
>
>
> VFS: Cannot open root device md0 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)
>
>
>
> And this is where it will stop during the boot process.  I am running a
> RAID1 on this machine.  When the screen comes up to choose which kernel I
> want to boot, I press "e" to edit the grub/menu.list, but all looks well. 
> Here is what I have:
>
>
>
> root(hd0,0)
>
> kernel  /boot/vmlinuz-2.6.16-2-amd64-k8-smp root=/dev/md0 ro
>
> initrd  /boot/initrd.img-2.6.16-2-amd64-k8-smp
>
> savedefault
>
>
>
> I'm stumped, what options do I have?
>
>
>
> Thanks in advance,
>
>
>
> Morgan
>
>
>
> Morgan Walker
>
> Systems Administrator/Engineer
>
> M·CAM, Inc.
>
> 210 Ridge-McIntire Rd., Suite 300
>
> Charlottesville, VA 22903
>
> 434-979-7240 x311
>
>
>
> http://www.m-cam.com
> =
> This message, including any attachments, is intended solely for the use
> of the named recipient(s) and may contain confidential and/or
> privileged information.  Any unauthorized review, use, disclosure or
> distribution of this communication(s) is expressly prohibited.
> If you are not the intended recipient, please contact the sender by
> reply e-mail and destroy any and all copies of the original message.
> Thank you.
> =

Re: Kernel Panic

2006-12-13 Thread Douglas Tutty

On Wed, Dec 13, 2006 at 11:10:02AM -0500, Morgan Walker wrote:
> After updating to 2.6.16-2-amd64-k8-smp on my Sun X4100 I rebooted and
> got the following error:
> 
> VFS: Cannot open root device md0 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)
> 
> And this is where it will stop during the boot process.  I am running a
> RAID1 on this machine.  When the screen comes up to choose which kernel
> I want to boot, I press "e" to edit the grub/menu.list, but all looks
> well.  Here is what I have:
> 
> root(hd0,0)
> kernel  /boot/vmlinuz-2.6.16-2-amd64-k8-smp root=/dev/md0 ro
> initrd  /boot/initrd.img-2.6.16-2-amd64-k8-smp
> savedefault
> 
> I'm stumped, what options do I have?
> 

Hi Morgan

Is the problem that the kernel can't read the filesystem on the raid1
md0 block device or that it can't find the block device?  The initramfs
should take care of loading any modules required so you shouldn't have
to recompile the kernel.

You could try editing that root= line to point directly to one of the
disks (and add init=/bin/sh to avoid doing anything other than testing
the kernel).  If this works, it means that the kernel is not handling
your raid setup; if it doesn't it means the problem is not the raid
setup.

My hunch is that in the process of updating the kernel that the initrd
didn't get made right.  If the above suggestion doesn't get you back in,
and you don't have a previous kernel installed to boot, you can boot
your installer media in rescue mode.

Once into you system, try dpkg-reconfigure the kernel package involved.
I say to do this instead of manually running mkinitrd (or initramfs)
since I don't know what parameters it needs; that's the job of the
kernel post-inst.

Good luck.

Doug.

-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2001-08-10 Thread Michael Heldebrant

Does your BIOS see the ram as all good?  If so you may need to find
something that tests the memory a bit more rigorously.

A quick scan of the packages list gives memtest86 and memtest.  Both
look like they should help you out in testing your ram.

--mike

On 10 Aug 2001 20:12:15 +0200, Marco Herrn wrote:
> Hello list,
> 
> a few days ago I had the following error message while booting:
> 
> /-
> kmem_alloc: Bad slab magic (corrupt) (name=kmem_cache)
> Kernel panic: kmem_cache_sizes_init: Error creating caches
> In swapper task - not swapping
> /-
> 
> After a second reboot everything worked fine.
> 
> But a few days later I had a similar problem, also on booting.
> This was the message:
> 
> /-
> Unable to handle kernel paging request at virtual address 7fdaa0e4
> current->tss.cr3 = 00101000, %cr3 = 00101000
> *pde = 
> Oops: 0002
> CPU:0
> EIP: 0010:[]
> EFLAGS: 00010245
> eax:    ebx: c02b8444   ecx: 0015   edx: 8500
> esi:    edi: 7fdaa0e4   ebp: 00a0   esp: c02fbf80
> ds: 0018   es: 0018   ss: 0018
> Process swapper (pid: 0, process nr: 0, stackpage=c02fb000)
> stack:  00a0  effef028 fff0  
> 0020
>  0010 0004 7fdaa0e4 c0300377 c0257ab8
> 0020
> 2000    000a0200 c0106000
> c02fcc05
> Call Trace: [] [] [] []
> Code: f3 ...
> /-
> 
> Unfortunately the screen suddenly blanked dfor some reason so I didn't have
> the chance to copy the rest of the message. Thats the reason for the three
> dots at the end.
> 
> 
> So what does this mean?
> I think it is a hardware problem, but which? Is it a problem with my RAM?
> 
> I would be glad if someone could tell me.
> 
> 
> Thanks in advance
> 
> Marco
> --
> Marco Herrn   [EMAIL PROTECTED]
> (GnuPG/PGP-signed and crypted mail preferred)
> Key ID: 0x94620736
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 
>

Re: kernel panic

2001-08-10 Thread Adam Bower

On 10 Aug 2001, Michael Heldebrant wrote:

> Does your BIOS see the ram as all good?  If so you may need to find
> something that tests the memory a bit more rigorously.

Don't rely on the BIOS check, it doesn't (usually) check the memory just
counts it for you and pretends to be doing a check.

I would also advocate the installation of memtest86 but it will/may take
some time to run depending on how much memory you have and how fast your
processor/bus speed is.

Adam
-- 
This message is Copyleft - all rights reversed
Adam

Re: kernel panic

2001-08-11 Thread Sebastiaan

Hi,

I had this behaviour once. Fortunately I remembered that I overclocked my
processor and it was becoming summer, so the temperature raised, causing
an unstable system.

Just to be sure you are not overlooking something :-)

Greetz,
Sebastiaan


On Fri, 10 Aug 2001, Marco Herrn wrote:

> Hello list,
> 
> a few days ago I had the following error message while booting:
> 
> /-
> kmem_alloc: Bad slab magic (corrupt) (name=kmem_cache)
> Kernel panic: kmem_cache_sizes_init: Error creating caches
> In swapper task - not swapping
> /-
> 
> After a second reboot everything worked fine.
> 
> But a few days later I had a similar problem, also on booting.
> This was the message:
> 
> /-
> Unable to handle kernel paging request at virtual address 7fdaa0e4
> current->tss.cr3 = 00101000, %cr3 = 00101000
> *pde = 
> Oops: 0002
> CPU:0
> EIP: 0010:[]
> EFLAGS: 00010245
> eax:    ebx: c02b8444   ecx: 0015   edx: 8500
> esi:    edi: 7fdaa0e4   ebp: 00a0   esp: c02fbf80
> ds: 0018   es: 0018   ss: 0018
> Process swapper (pid: 0, process nr: 0, stackpage=c02fb000)
> stack:  00a0  effef028 fff0  
> 0020
>  0010 0004 7fdaa0e4 c0300377 c0257ab8
> 0020
> 2000    000a0200 c0106000
> c02fcc05
> Call Trace: [] [] [] []
> Code: f3 ...
> /-
> 
> Unfortunately the screen suddenly blanked dfor some reason so I didn't have
> the chance to copy the rest of the message. Thats the reason for the three
> dots at the end.
> 
> 
> So what does this mean?
> I think it is a hardware problem, but which? Is it a problem with my RAM?
> 
> I would be glad if someone could tell me.
> 
> 
> Thanks in advance
> 
> Marco
> --
> Marco Herrn   [EMAIL PROTECTED]
> (GnuPG/PGP-signed and crypted mail preferred)
> Key ID: 0x94620736
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>

Re: Kernel Panic

2012-07-06 Thread Harshad Joshi

i am testing it on a dell vostro running Ubuntu 10.10 and Oracle
Virtualbox..i havent tested it on real machine as yet..

the same iso runs well on older debian lenny and Virtualbox

On Fri, Jul 6, 2012 at 4:09 PM, Kirill Sotnikov <
kirill.sotni...@maxifier.com> wrote:

> What motherboard do u use?
> Kirill Sotnikov
> Maxifier, Inc.
>
> phone: +79179468634
> skype: wlan1024
>
>
>
>
> On Fri, Jul 6, 2012 at 1:38 PM, Harshad Joshi wrote:
>
>> I saw a very strange error while installing debian cd -
>>
>> kernel panic - not syncing vfs unable to mount root fs on unknown block
>> (254,6)
>>
>> What might be the reason for this error? !!!
>>
>>
>> --
>> Harshad Joshi
>>
>>
>>
>


-- 
Harshad Joshi

Re: Kernel Panic

2012-07-06 Thread Camaleón

On Fri, 06 Jul 2012 15:08:18 +0530, Harshad Joshi wrote:

(please, no html posts, thanks...)

> I saw a very strange error while installing debian cd -
> 
> kernel panic - not syncing vfs unable to mount root fs on unknown block
> (254,6)
> 
> What might be the reason for this error? !!!

I've never seen it before :-?

You can:

1/ Check the validity of the original ISO file checksum
2/ Try to install from USB stick instead

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jt70pg$339$1...@dough.gmane.org

Re: kernel panic

2002-03-21 Thread Mark Janssen

On Thu, 2002-03-21 at 21:42, Pier wrote:
> My kenel (2.4.18) panic.
> Request_module[block-major-3]:Root fs not mounted
> 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'm afraid that (as I read it) 
> the problem comes from my mother board which is a K7S5A 
> (Duron 1GH) and seems to have trouble with memory 
> that cause file corruption. But kernel 2.2 is ok.

Nope that's not it...

This message tells you that the kernel cannot find the root partition.
This can be because it is f**ked up, or because the kernel is just
looking in the wrong place. Since we'll assume all is well, and your
drive still works, you need to tell the kernel where to find the root
disk/partition.

On the lilo prompt enter what You usually enter (linux, or whatever) and
after it type: 'root=/dev/hdx#' which x# replaced by the correct drive
and partition number (Primary master = hda, slave=hdb, secondary master
hdc, slave=hdd, scsi's sda-sd?. Partitions are numbered from 1)

WHen you find the correct one, linux should continue booting. After
getting it up and running fix your lilo (or grub) configfile and
reinstall lilo.

-- 
Mark Janssen Unix / Linux, Open-Source and Internet Consultant @
SyConOS IT
E-mail: mark(at)markjanssen.nl / maniac(at)maniac.nl GnuPG Key Id:
357D2178
Web: Maniac.nl Unix-God.[Net|Org] MarkJanssen.[com|net|org|nl]
SyConOS.[com|nl]

Re: kernel panic

2002-03-23 Thread Hans Gubitz

Tell the kernel the ramsize you have installed.

append = "mem=224M"



On Sat, Mar 23, 2002 at 12:32:01AM -0500, Jerome Acks Jr wrote:
> On Thu, Mar 21, 2002 at 09:42:59PM +0100, Pier wrote:
> > My kenel (2.4.18) panic.
> > 
> > the boot message is :
> > 
> > Request_module[block-major-3]:Root fs not mounted
> > 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
> 
> Check the config file for the kernel. Make sure IDE and root filesystem
> support is compiled into kernel. 
> 
> -- 
> Jerome



-- 
Hans Gubitz <[EMAIL PROTECTED]>

Re: kernel panic

2002-03-23 Thread Jerome Acks Jr

On Thu, Mar 21, 2002 at 09:42:59PM +0100, Pier wrote:
> My kenel (2.4.18) panic.
> 
> the boot message is :
> 
> Request_module[block-major-3]:Root fs not mounted
> 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

Check the config file for the kernel. Make sure IDE and root filesystem
support is compiled into kernel. 

-- 
Jerome


pgp769HsQMRMM.pgp
Description: PGP signature

Re: Kernel Panic

2002-03-24 Thread Jerome Acks Jr

On Sun, Mar 24, 2002 at 12:41:56PM -0500, james martinez wrote:
> If anyone could help with this I would appriciate it. I installed a new
> Nvidia Gforce 4 card in my system last weekend. So I had to compile a
> custom kernel to setup the drivers for it. I got the 2.4.18 source with
> apget and used the kernel-packaging tool to create a new kernel image. I
> got the nvidia drives installed and working but had left out some other
> drivers that my system needs. So this weekend I decided to fix that. I
> started by rerunning xconfig and selecting the drivers I needed to be
> loaded as modules. Then used make-kpkg --append_to_version foo when I
> rebuilt the kernel. Now I have a 2.4.18 kernel and a 2.4.18.2.4 when I
> try to boot the 2.4.18.2.4 which is the one built using
> --append_to_version with make-kpkg I get this
> Kernel Panic: VFS:unable to mount root fs on 03:42
> Anyone have any ideas what I messed up? 
> I can still boot the 2.4.18 kernel but it is missing modules I need. 
> Thanks for any help.

You could possibly still have kernel configured to use initrd but didn't run
make-kpkg with --initrd option.

Assuming you are not using initrd, look at kernel config and make sure
you've compiled in support for IDE (CONFIG_IDE=y) [or SCSI
(CONFIG_SCSI=y) if your boot disk is SCSI] and for your root filesystem.

-- 
Jerome


pgp6zWeI7txgi.pgp
Description: PGP signature

Re: Kernel Panic

2002-03-24 Thread james martinez

I tried running it with the initrd option and got the same failure
message. One thing I did notice is whaen I dpkg -i the kernel image I
got the following
*** Unresolved symbols in
/lib/modules/2.4.18/kernel/net/ipv4/netfilter/ipchains.o

On Sun, 2002-03-24 at 18:25, Jerome Acks Jr wrote:
> You could possibly still have kernel configured to use initrd but didn't run
> make-kpkg with --initrd option.
> 
> Assuming you are not using initrd, look at kernel config and make sure
> you've compiled in support for IDE (CONFIG_IDE=y) [or SCSI
> (CONFIG_SCSI=y) if your boot disk is SCSI] and for your root filesystem.
> 
> -- 
> Jerome

-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Kernel Panic

2002-03-29 Thread Rob Weir

On Sun, Mar 24, 2002 at 12:41:56PM -0500, james martinez wrote:
> If anyone could help with this I would appriciate it. I installed a new
> Nvidia Gforce 4 card in my system last weekend. So I had to compile a
> custom kernel to setup the drivers for it. I got the 2.4.18 source with
> apget and used the kernel-packaging tool to create a new kernel image. I
> got the nvidia drives installed and working but had left out some other
> drivers that my system needs. So this weekend I decided to fix that. I
> started by rerunning xconfig and selecting the drivers I needed to be
> loaded as modules. Then used make-kpkg --append_to_version foo when I
> rebuilt the kernel. Now I have a 2.4.18 kernel and a 2.4.18.2.4 when I
> try to boot the 2.4.18.2.4 which is the one built using
> --append_to_version with make-kpkg I get this
> Kernel Panic: VFS:unable to mount root fs on 03:42

I had this problem just a few days ago, when I compiled ReiserFS
(which is the format of my root file system) as a module, rather than
monolithically.  Are you sure you have enough drivers compiled into
the kernel for it to be able to mount a root file system?  This means
IDE/SCSI (whichever or both), filesystem modules, possibly RAID or
network drivers... You could also try using the --initrd option with
make-kpkg.  I've never used initrd's before, but I think this is the
sort of thing they're for.

-rob

pgpKBvf7wWRyJ.pgp
Description: PGP signature

Re: kernel panic

2000-12-05 Thread kmself

on Wed, Dec 06, 2000 at 12:08:59AM -, Robert Feri ([EMAIL PROTECTED]) wrote:
> What can i do (unless reinstall the system) if a message kernel panic
> appears while booting the system (debian 2.2) ?

Report the message in detail, and try to find related information online
or in other references.

-- 
Karsten M. Self  http://www.netcom.com/~kmself
 Evangelist, Zelerate, Inc.  http://www.zelerate.org
  What part of "Gestalt" don't you understand?  There is no K5 cabal
   http://gestalt-system.sourceforge.net/http://www.kuro5hin.org


pgp4em16dWkYD.pgp
Description: PGP signature

Re: kernel panic

2000-12-05 Thread kmself

Please use postfix response format.
Please respond to list.
Response redirected to list.
Reply-to set to list.

on Wed, Dec 06, 2000 at 01:57:26AM -, Robert Feri ([EMAIL PROTECTED]) wrote:
> 
> >From: kmself@ix.netcom.com
> >To: debian-user@lists.debian.org
> >Subject: Re: kernel panic
> >Date: Tue, 5 Dec 2000 17:24:58 -0800
> >
> >on Wed, Dec 06, 2000 at 12:08:59AM -, Robert Feri 
> >([EMAIL PROTECTED]) wrote:
> > > What can i do (unless reinstall the system) if a message kernel panic
> > > appears while booting the system (debian 2.2) ?
> >
> >Report the message in detail, and try to find related information online
> >or in other references.
> >
> >--
> >Karsten M. Self  http://www.netcom.com/~kmself
> >  Evangelist, Zelerate, Inc.  http://www.zelerate.org
> >   What part of "Gestalt" don't you understand?  There is no K5 cabal
> >http://gestalt-system.sourceforge.net/http://www.kuro5hin.org

> It gives me the following message:
> Kernel panic: VFS: Unable to mount root fs
> 
> Robert

LILO can't find your root filesystem.   You've either configured LILO
wrong or specified the wrong partition at boot time.

You might want to try typing running something like:

linux root=/dev/hda1

...at the LILO prompt.  If you're not given one by default, hold down
the shift, alt, or control keys, or set either capslock or scroll lock.

...typical root partitions are hda[1-9] for IDE drives or sda[1-9] for
SCSI.

This information is contained in /usr/doc/lilo/Manual.txt.gz.

FWIW, chances are if you've configured your root filesystem incorrectly
that you may not be able to locate your kernel or init as well.  Try
fixing the root filesystem issue first, if you have additional problems,
read the LILO manual for more information.

-- 
Karsten M. Self  http://www.netcom.com/~kmself
 Evangelist, Zelerate, Inc.  http://www.zelerate.org
  What part of "Gestalt" don't you understand?  There is no K5 cabal
   http://gestalt-system.sourceforge.net/http://www.kuro5hin.org

pgpFWqrsDP4Sc.pgp
Description: PGP signature

Re: kernel panic

2000-12-07 Thread Ian Lee

From: "Robert Feri" <[EMAIL PROTECTED]>
To: 
Subject: kernel panic
Date: Wed, 06 Dec 2000 00:08:59 -

What can i do (unless reinstall the system) if a message kernel panic
appears while booting the system (debian 2.2) ?

Robert

Just in case this was overlooked.
Re-installing is not necessary, but booting from a backup/rescue disk is.
Then you can at least get into the system to find out what went wrong.

If this was no help at all sorry.

Ian
_
Get more from the Web.  FREE MSN Explorer download : http://explorer.msn.com

Re: kernel panic

2000-06-25 Thread kmself

On Fri, Jun 23, 2000 at 02:30:33PM -0700, cls--colo spgs wrote:
> debs,
> 
> successfully, i've done a compile of source kernel
> 2.2.16 for my potato deskbox; but trying to do the same
> thing (approximately 5 times) on my slink lapbox leads
> to the infamous "kernel panic."  the first re-boot (via
> floppy) after the compile is fine.  it's the next
> re-boot after that, that things get weird.

Second reboot is from floppy or hard drive?  What did you change?

> ...the last line before hanging:
> 
> kernel panic: vfs: unable to mount fs on 03:01
> 
> 
> here's my partition scheme:
> 
> / on hda1 (1.5gb)
> swap on hda5 (66mb)
> hda3 (500mb) (for storing large files (e.g. kernel
> sources, netscape, wordperfect...) that i don't want to
> re-download after i re-install slink).

Why don't you post your partition table:

   $ fdisk -l /dev/hda

> before the compile, slink was using kernel 2.0.36
> (/boot/vmlinuz-2.0.36).  (after the compile, i moved
> the old kernel to /boot/oldvmlinuz-2.0.36, as i
> thought, perhaps needlessly, that the new kernel
> (/boot/vmlinuz-2.2.16)) needed its own "vmlinuz"
> "identity."

Did you re-run lilo, manually?

> in case the compile is at issue, here's what i did from
> "bt:/usr/src/linux#":
> 
> make menuconfig
> make dep
> make install
> make modules
> make modules_install
> 
> 
> there isn't, nor will there be, another os on the
> lapbox, just "dlinux."
> 
> the rescue disk won't even let me "backdoor" the
> system:  "mount failed: invalid argument" (when i tried
> to mount hda1).

Give commands and output.

> anyway, ...suggestions/options?
> 
> ia, t.  
> 
> bentley taylor.

Suggest you try a boot disk such as Tom's Root Boot, mount the HD,
chroot to the root FS, and re-run lilo, or indicate what commands and
what errors result in attempting to do so.

-- 
Karsten M. Self  http://www.netcom.com/~kmself
  Evangelist, Opensales, Inc.   http://www.opensales.org
   What part of "Gestalt" don't you understand?  Debian GNU/Linux rocks!
 http://gestalt-system.sourceforge.net/  K5: http://www.kuro5hin.org
GPG fingerprint: F932 8B25 5FDD 2528 D595  DC61 3847 889F 55F2 B9B0


pgpvIutx9z3sC.pgp
Description: PGP signature

Re: kernel panic

2000-06-25 Thread kmself

On Fri, Jun 23, 2000 at 02:30:33PM -0700, cls--colo spgs wrote:
> debs,
> 
> successfully, i've done a compile of source kernel

[...]

> in case the compile is at issue, here's what i did from
> "bt:/usr/src/linux#":
> 
> make menuconfig
> make dep
> make install
> make modules
> make modules_install

Re-reading the above, I note you don't mention running 'lilo', which
will be an issue.  You also are doing a raw Linux kernel compile an
install rather than using the debian makekpkg utility.  It's a bit
nonstandard (for Linux), but makes the process of building and updating
the kernel more Debian-like.

If you do use makekpgk, you get to install the kernel you create just
like any other Debian package.  This automajikaly does Good Things (tm)
like run lilo, move packages, and put kernel modules where they should
be.

-- 
Karsten M. Self  http://www.netcom.com/~kmself
  Evangelist, Opensales, Inc.   http://www.opensales.org
   What part of "Gestalt" don't you understand?  Debian GNU/Linux rocks!
 http://gestalt-system.sourceforge.net/  K5: http://www.kuro5hin.org
GPG fingerprint: F932 8B25 5FDD 2528 D595  DC61 3847 889F 55F2 B9B0

pgpMRS9cvNIQY.pgp
Description: PGP signature

Re: Kernel Panic

2002-01-03 Thread J.A.Serralheiro

at first try to boot with a rescue disk, either a floppy or a instalation
cd.


On Thu, 3 Jan 2002, Mike Kuhar wrote:

> Hello everyone,
> 
> Yesterday I built the kernel-source-2.4.17.  All seemed well.  I had
> re-booted a couple times without problems.
> 
> Today, however, I get the error message "Kernel panic:VFS:unable to mount
> root fs on 03:03".
> 
> Two months ago I had converted by fs from ext2 to ext3.
> 
> I'm wondering what I need to do the get my system back without a re-install,
> if that's at all possible.  Any and all ideas would be greatly appreciated.
> 
> Thanks -mk
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 
>

Re: kernel panic

2000-12-18 Thread Andy Bastien

Pending further investigation, we now allege that q wrote:
> debs,
> 
> in one of my dual-boot deskboxes, i have a kernel panic:
> 
> unable to load NLS charset cp 437
> kernel panic:  VFS: unable to mount root fs on 03:03
> 
> my potato on custom kernel 2.2.17 was functioning well until yesterday.  
> 
> i don't mind a re-install, but i'd really like to know what's going on, as 
> this happens like every couple of months to one of my machines.
> 
> (i know i have a line-wrap problem w/ vi.  when i get some time to learn how 
> to fix it, i'll be very happy.  until then, my apologies.)
> 
> anyway, when i use the rescue disk and mount a partition, i only get the 
> choices of /dev/hda1 (wincrap) /dev/hda3 and /dev/hda4.  i'm sure i had 
> /dev/hda2 (linux) and /dev/hda5 (swap).  and when i try to mount 
> /dev/hda3-hda4, i get, "invalid argument."
> 
> i think i'm screwed; but if anyone has suggestions, please cc me.  
> 
> ia, t.
> 
> bentley taylor.
> 

Is /dev/hda3 is a FAT volume?

Re: kernel panic

2000-12-18 Thread Peter Jay Salzman

egads, man.  don't reinstall an operating system!

don't you have any spare kernels laying around?   i always leave myself at
least 1 other old kernel.

as for vim, try:

echo "set textwidth=76" >> $HOME/.vimrc

p

On Mon 18 Dec 00,  2:07 PM, q said...
> debs,
> 
> in one of my dual-boot deskboxes, i have a kernel panic:
> 
> unable to load NLS charset cp 437
> kernel panic:  VFS: unable to mount root fs on 03:03
> 
> my potato on custom kernel 2.2.17 was functioning well until yesterday.  
> 
> i don't mind a re-install, but i'd really like to know what's going on, as 
> this happens like every couple of months to one of my machines.
> 
> (i know i have a line-wrap problem w/ vi.  when i get some time to learn how 
> to fix it, i'll be very happy.  until then, my apologies.)
> 
> anyway, when i use the rescue disk and mount a partition, i only get the 
> choices of /dev/hda1 (wincrap) /dev/hda3 and /dev/hda4.  i'm sure i had 
> /dev/hda2 (linux) and /dev/hda5 (swap).  and when i try to mount 
> /dev/hda3-hda4, i get, "invalid argument."
> 
> i think i'm screwed; but if anyone has suggestions, please cc me.  
> 
> ia, t.
> 
> bentley taylor.
> 
> //   
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 

-- 
Just upgraded to Woody?  Don't have permission to run X? linux
In Xwrapper.config, change allowed_users from root to console. -
--._.
To err is human, to forgive is divine.  [EMAIL PROTECTED]  /v\
To moo is bovine, to meow is feline.http://www.dirac.org/p   // \\
--   ^^ ^^
GPG Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D   rules


pgpB4Y7Uz7Yy1.pgp
Description: PGP signature

Re: kernel panic

2000-12-19 Thread q

On Mon, Dec 18, 2000 at 01:40:35PM -0800, Peter Jay Salzman wrote:
> egads, man.  don't reinstall an operating system!
> 
> don't you have any spare kernels laying around?   i always leave myself at
> least 1 other old kernel.
> 
> as for vim, try:
> 
>   echo "set textwidth=76" >> $HOME/.vimrc
> 
> p
> 
> On Mon 18 Dec 00,  2:07 PM, q said...
> > debs,
> > 
> > in one of my dual-boot deskboxes, i have a kernel panic:
> > 
> > unable to load NLS charset cp 437
> > kernel panic:  VFS: unable to mount root fs on 03:03
> > 
> > my potato on custom kernel 2.2.17 was functioning well until yesterday.  
> > 
> > i don't mind a re-install, but i'd really like to know what's going on, as 
> > this happens like every couple of months to one of my machines.
> > 
> > (i know i have a line-wrap problem w/ vi.  when i get some time to learn 
> > how to fix it, i'll be very happy.  until then, my apologies.)
> > 
> > anyway, when i use the rescue disk and mount a partition, i only get the 
> > choices of /dev/hda1 (wincrap) /dev/hda3 and /dev/hda4.  i'm sure i had 
> > /dev/hda2 (linux) and /dev/hda5 (swap).  and when i try to mount 
> > /dev/hda3-hda4, i get, "invalid argument."
> > 
> > i think i'm screwed; but if anyone has suggestions, please cc me.  
> > 
> > ia, t.
> > 
> > bentley taylor.
> > 
> > //   
> > 
> > 
> > -- 
> > To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> > 
> 
> -- 
> Just upgraded to Woody?  Don't have permission to run X? linux
> In Xwrapper.config, change allowed_users from root to console. -
> --._.
> To err is human, to forgive is divine.  [EMAIL PROTECTED]  /v\
> To moo is bovine, to meow is feline.http://www.dirac.org/p   // \\
> --   ^^ ^^
> GPG Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D   rules

debs,

i was booting with floppy, which will still boot one of my potato lapboxes.  
so, i basically have a hardware prob, right?

ia, t.

bentley taylor

//

Re: Kernel panic

2000-12-25 Thread urbanyon

> "Kernel panic"
is it just me, or does anyone else think this sounds like the title of a
really nerdy action movie? :-)

Re: Kernel panic

2001-01-16 Thread kmself

on Tue, Jan 16, 2001 at 03:29:00PM +0100, Manuel Hendel ([EMAIL PROTECTED])
wrote:
> Hi all,
>
> can anyone help me with the error message of a kernel panic?

Debugging kernel panics is a bit of a black art.

Knowing what kernel you're using helps a bit.

Take a look at the attached script. It will create a kernel bug report
based on the format suggested in /usr/src/linux/REPORTING-BUGS. You'll
need to put ksymoops somewhere on your path for it to work.

No promises, but this may provide additional insight.

--
Karsten M. Self http://kmself.home.netcom.com/
What part of "Gestalt" don't you understand? There is no K5 cabal
http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org
#!/bin/bash

# Kernel bug report generator script
# Script generated from prior bug report form by Karsten M. Self
# $Revision: 1.3 $ $Date: 2000/05/13 07:48:36 $ $Author: root $

#
# [Some of this is taken from Frohwalt Egerer's original linux-kernel FAQ]
#
# What follows is a suggested procedure for reporting Linux bugs. You
# aren't obliged to use the bug reporting format, it is provided as a guide
# to the kind of information that can be useful to developers - no more.
#
# If the failure includes an "OOPS:" type message in your log or on
# screen please read "Documentation/oops-tracing.txt" before posting your
# bug report. This explains what you should do with the "Oops" information
# to make it useful to the recipient.
#
# Send the output the maintainer of the kernel area that seems to
# be involved with the problem. Don't worry too much about getting the
# wrong person. If you are unsure send it to the person responsible for the
# code relevant to what you were doing. If it occurs repeatably try and
# describe how to recreate it. That is worth even more than the oops itself.
# The list of maintainers is in the MAINTAINERS file in this directory.
#
# If you are totally stumped as to whom to send the report, send it to
# [EMAIL PROTECTED] (For more information on the linux-kernel
# mailing list see http://www.tux.org/lkml/).
#
# This is a suggested format for a bug report sent to the Linux kernel mailing
# list. Having a standardized bug report form makes it easier for you not to
# overlook things, and easier for the developers to find the pieces of
# information they're really interested in. Don't feel you have to follow it.
#
#First run the ver_linux script included as scripts/ver_linux or
# at ftp://ftp.sai.msu.su/pub/Linux/ver_linux> It checks out
# the version of some important subsystems. Run it with the command
# "sh scripts/ver_linux"
#
# Use that information to fill in all fields of the bug report form, and
# post it to the mailing list with a subject of "PROBLEM: " for easy identification by the developers
#

# indent by one tabstop
function tabout () { sed -e '/^/s// /'; }

cat <

pgpbbudxLzoE4.pgp
Description: PGP signature

Re: Kernel panic

2000-04-27 Thread Antonio Rodriguez

I did select it.

"Ivan J. Varzinczak" wrote:

> [Antonio Rodriguez ([EMAIL PROTECTED]), April, 26 (2000)]:
> > Kernel Panic: VFS: Unable to mount root fs on 03:42.
> > This is happenning after compiling a new kernel. I can still access the
> > system through an old kernel.
> > Any ideas to solve it?
>
> Maybe you haven't selected the support for your hard drive in
> the kernel configuration (IDE or SCSI).
>
> --
> Ivan J. Varzinczak - http://www.inf.ufpr.br/~ivan
> Scholarship holder - Boursier - (PET/CAPES)
> Informatics Department - Département d'Informatique
> Federal University of Paraná - Université Fédérale du Paraná
> Curitiba - Paraná - Brazil/Brésil
>
> 26-IV-2000

Re: Kernel panic

2000-04-27 Thread Ivan J. Varzinczak

[Antonio Rodriguez ([EMAIL PROTECTED]), April, 26 (2000)]:
> Kernel Panic: VFS: Unable to mount root fs on 03:42.
> This is happenning after compiling a new kernel. I can still access the
> system through an old kernel.
> Any ideas to solve it?

Maybe you haven't selected the support for your hard drive in
the kernel configuration (IDE or SCSI).

-- 
Ivan J. Varzinczak - http://www.inf.ufpr.br/~ivan
Scholarship holder - Boursier - (PET/CAPES)
Informatics Department - Département d'Informatique
Federal University of Paraná - Université Fédérale du Paraná
Curitiba - Paraná - Brazil/Brésil

26-IV-2000

Re: Kernel panic

2000-04-27 Thread Peter Palfrader

Hi Antonio!

On Wed, 26 Apr 2000, Antonio Rodriguez wrote:

> Kernel Panic: VFS: Unable to mount root fs on 03:42.
> This is happenning after compiling a new kernel. I can still access the
> system through an old kernel.
> Any ideas to solve it?
> Thanx

Did you compile ext2 (or whatever your root filesystem is) into the
kernel (!not as a module!)?

yours,
peter

-- 
PGP encrypted messages prefered.
http://www.cosy.sbg.ac.at/~ppalfrad/

pgpJTj0fcBIR7.pgp
Description: PGP signature

Re: Kernel panic

2000-04-27 Thread Antonio Rodriguez

I am almost sure I did (99.999%)

Peter Palfrader wrote:

> Hi Antonio!
>
> On Wed, 26 Apr 2000, Antonio Rodriguez wrote:
>
> > Kernel Panic: VFS: Unable to mount root fs on 03:42.
> > This is happenning after compiling a new kernel. I can still access the
> > system through an old kernel.
> > Any ideas to solve it?
> > Thanx
>
> Did you compile ext2 (or whatever your root filesystem is) into the
> kernel (!not as a module!)?
>
> yours,
> peter
>
> --
> PGP encrypted messages prefered.
> http://www.cosy.sbg.ac.at/~ppalfrad/
>
>   
>Part 1.2Type: application/pgp-signature

Re: Kernel panic

2000-04-27 Thread Tom Pfeifer

You probably forgot to enable IDE support under block devices when you
configured the kernel. It has to be compiled directly into the kernel
(not a module) if the root file system is on an IDE disk. 

Tom

Antonio Rodriguez wrote:
> 
> Kernel Panic: VFS: Unable to mount root fs on 03:42.
> This is happenning after compiling a new kernel. I can still access the
> system through an old kernel.
> Any ideas to solve it?
> Thanx
>

Re: Kernel panic

2000-04-27 Thread Andrew Weiss

on 4/26/00 8:19 PM, Antonio Rodriguez at [EMAIL PROTECTED] wrote:

> I am almost sure I did (99.999%)
> 
> Peter Palfrader wrote:
> 
>> Hi Antonio!
>> 
>> On Wed, 26 Apr 2000, Antonio Rodriguez wrote:
>> 
>>> Kernel Panic: VFS: Unable to mount root fs on 03:42.
>>> This is happenning after compiling a new kernel. I can still access the
>>> system through an old kernel.
>>> Any ideas to solve it?
>>> Thanx
>> 
>> Did you compile ext2 (or whatever your root filesystem is) into the
>> kernel (!not as a module!)?
>> 
>> yours,
>> peter
>> 
>> --
>> PGP encrypted messages prefered.
>> http://www.cosy.sbg.ac.at/~ppalfrad/
>> 
>> 
>> Part 1.2Type: application/pgp-signature
> 
He probably had an initial ramdisk and no initrd, romfs, or other support.
I have a SCSI system, and I have to either compile the driver into a
monolithic kernel or use an initial ramdisk which has the scsi module on it.
I once tried to boot without the ramdisk and the same thing happened to me.

Andrew

Re: Kernel panic

2000-04-27 Thread Kerstin Hoef-Emden

Hi Antonio,

On Wed, 26 Apr 2000, Antonio Rodriguez wrote:

> Kernel Panic: VFS: Unable to mount root fs on 03:42.
> This is happenning after compiling a new kernel. I can still access the
> system through an old kernel.

In most cases it simply means, that you forgot something really
important when compiling the kernel. E. g. never forget ext2fs or the
IDE- or SCSI-drivers. Have a thorough look at all your kernel configs
and recompile it.

Regards,

Kerstin

-- 

[EMAIL PROTECTED]

Re: Kernel panic

2000-04-27 Thread Antonio Rodriguez

What else can the reason be? I have cheked and made sure that I have almost 
every
single option embeded in the kernel. Still doing it.

Kerstin Hoef-Emden wrote:

> Hi Antonio,
>
> On Wed, 26 Apr 2000, Antonio Rodriguez wrote:
>
> > Kernel Panic: VFS: Unable to mount root fs on 03:42.
> > This is happenning after compiling a new kernel. I can still access the
> > system through an old kernel.
>
> In most cases it simply means, that you forgot something really
> important when compiling the kernel. E. g. never forget ext2fs or the
> IDE- or SCSI-drivers. Have a thorough look at all your kernel configs
> and recompile it.
>
> Regards,
>
> Kerstin
>
> --
>
> [EMAIL PROTECTED]
>
> --
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

Re: Kernel panic

2000-04-27 Thread Kerstin Hoef-Emden

Hi Antonio,

On Thu, 27 Apr 2000, Antonio Rodriguez wrote:

> What else can the reason be? I have cheked and made sure that I have
> almost every single option embeded in the kernel. Still doing it. 

Hmm, what else is necessary? You do have IDE or SCSI support compiled
into the kernel as well as the specific driver for your card? Are the
bootoptions O.K.? 
I am not exactly an expert when it comes to booting up an i386 system so
I don´t know what you have to tell LILO exactly. 

Regards,

Kerstin

-- 

[EMAIL PROTECTED]

Re: Kernel panic

2000-04-27 Thread Oswald Buddenhagen

> Kernel Panic: VFS: Unable to mount root fs on 03:42.
03:42 is hdb2. are you sure, that this is your root filesystem?
possibly your lilo is misconfigured or (when not using lilo) hdb2 was root
at compilation time, but isn't anymore now?

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Linux - the last service pack you'll ever need.

Re: Kernel panic

2000-04-27 Thread Antonio Rodriguez

This is probably waht it is, since I am booting from floppy (can not boot from
hdb), and I think I didn't exactly fix Lilo. I think I had my root file system
in hdb?, ups , don't remember! I have installed it so many times... I will
check on it and report back.

Oswald Buddenhagen wrote:

> > Kernel Panic: VFS: Unable to mount root fs on 03:42.
> 03:42 is hdb2. are you sure, that this is your root filesystem?
> possibly your lilo is misconfigured or (when not using lilo) hdb2 was root
> at compilation time, but isn't anymore now?
>
> --
> Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
> --
> Linux - the last service pack you'll ever need.

RE: Kernel panic

2000-04-28 Thread Christian Pernegger

> -Original Message-
> From: Antonio Rodriguez [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 27, 2000 1:59 AM
> To: debian-user@lists.debian.org
> Subject: Kernel panic
>
>
> Kernel Panic: VFS: Unable to mount root fs on 03:42.
> This is happenning after compiling a new kernel. I can still access the
> system through an old kernel.
> Any ideas to solve it?

I got this today because I changed my disk layout from

sda: [ Win 2k partition | Linux root partition ]

to

sda: [ free space | Linux partition ]

via the NT disk administrator. It would delete the 1. partition and then
_renumbered_ the second so it became number 1.
Linux tried to mount root specifically from sda2, which wasn't there
anymore...

If something like that could be the reason, boot with the rescue and root
floppies, change the fstab entry and root location argument for the kernel.

Christian

Re: Kernel Panic

2000-05-05 Thread brian moore

On Fri, May 05, 2000 at 05:08:50PM -0500, eric k. wolven wrote:
> Fellow debians:
> 
>  Up until now I have had no problems compiling kernels.  I used the latest 
> "make-kpkg" on the downloaded kernel-source-2.2.15, dpkg'd it, lilo reports 
> successful install and on re-boot I get the following message:
> 
> "kmod: failed to exec /sbin/modprobe -s -k binfmt-464c, errno 8"
> Kernel panic: No init found.  Try passing init=option to kernel."
> 
> 
> Can anybody give me a clue as to what is going on and how to fix it?  I'm a 
> relative newbie.

Boot from a rescue disk and rebuild your kernel.  You want to be
careful about what you make as modules.  Specifically, don't make ELF
executables a module.

-- 
Brian Moore   | Of course vi is God's editor.
  Sysadmin, C/Perl Hacker | If He used Emacs, He'd still be waiting
  Usenet Vandal   |  for it to load on the seventh day.
  Netscum, Bane of Elves.

Re: Kernel Panic

2000-05-06 Thread eric k. wolven

Brian:

Success!  You were right about the elf binaries.  I'm still getting wonky 
messages about my modules but the darn thing actually boots...

Thanks for your quick response.

Eric Wolven

Re: Kernel panic... :-(

2002-06-10 Thread Helgi Örn Helgason

On Mon, 2002-06-10 at 17:03, Helgi Örn wrote:
[snip]
At last I managed to get back into the system on the old kernel
(2.2.20), so now I just have to study further the art of upgrading the
kernel in Debian... :-)

Cheers,
Helgi Örn

-- 



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Kernel panic... :-(

2002-06-10 Thread Helgi Örn

On Mon, 2002-06-10 at 18:43, Helgi Örn Helgason wrote:
> On Mon, 2002-06-10 at 17:03, Helgi Örn wrote:
> [snip]
> At last I managed to get back into the system on the old kernel
> (2.2.20), so now I just have to study further the art of upgrading the
> kernel in Debian... :-)
>
apt-get remove kernel-image-2.4.18 
apt-get install kernel-image-2.4.18-686
writing a new lilo.conf (I just love lilo!)
run lilo (over the SuSE lilo so now Debian rules this box...:-)
reboot
Voila!

Now I just have these left to config:
Sound: Creative Audigy Platinum eX
CD-burner: HP cd-writer 9500
TV-card: Hauppauge WinTV

Any hints?

Cheers,
Helgi Örn
 
-- 
 





-- 
 


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Kernel panic... :-(

2002-06-10 Thread Mathias Gygax

On Mon, Jun 10, 2002 at 08:46:07PM +0200, Helgi Örn wrote:
> Now I just have these left to config:
> Sound: Creative Audigy Platinum eX

apt-get -f install alsa-modules-2.4.18-686 alsaconf

and alsaconf it.

> CD-burner: HP cd-writer 9500

"hdX=ide-scsi" into append line of lilo.conf

cdrecord -scanbus should print the scsi-generic ID of your device.

> TV-card: Hauppauge WinTV

here is my /etc/modutils/bttv

-[snip]-
#
# TV
#

alias char-major-81 videodev
alias char-major-81-0   bttv
alias char-major-89 i2c-dev
pre-install bttvmodprobe -k msp3400; modprobe -k tuner
options i2c i2c_debug=0 verbose=0 scan=1
options i2c-corei2c_debug=1
options i2c-algo-bitbit_test=1
#options bttvradio=0 card=10 pll=2 triton1=1 tuner=5
options bttvradio=0 card=10
options msp3400 debug=0
options tuner   debug=1
-[snip]-

update-modules and "modprobe bttv". be sure to adjust above driver
options to your fit. above setup ist for my hauppauge wintv pci with a
BT878 chipset.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Kernel panic... :-(

2002-06-10 Thread Helgi Örn

Thank's for the information Mathias!

On Mon, 2002-06-10 at 23:05, Mathias Gygax wrote:
> apt-get -f install alsa-modules-2.4.18-686 alsaconf
> 
> and alsaconf it.
Works very well...:-)

> 
> > CD-burner: HP cd-writer 9500
> 
> "hdX=ide-scsi" into append line of lilo.conf
> 
> cdrecord -scanbus should print the scsi-generic ID of your device.
Yes, and modprobe ide-scsi.
I also wonder which init file I can put the line: 
/sbin/modprobe ide-scsi
would /etc/init.d/bootmisc.sh be the right place?

> here is my /etc/modutils/bttv
> 
 -[snip]-
> 
> update-modules and "modprobe bttv". be sure to adjust above driver
> options to your fit. above setup ist for my hauppauge wintv pci with a
> BT878 chipset.
> 
I got the same chipset and everything works jolly nice.

Cheers,
Helgi Örn

-- 
 


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Kernel panic... :-(

2002-06-11 Thread Mathias Gygax

On Tue, Jun 11, 2002 at 05:46:41AM +0200, Helgi Örn wrote:
> Thank's for the information Mathias!

np.

> Yes, and modprobe ide-scsi.
> I also wonder which init file I can put the line: 
> /sbin/modprobe ide-scsi
> would /etc/init.d/bootmisc.sh be the right place?

nope. the modutils package have a great range of helper scripts and
config files. for loading modules automatically from startup, you could

1. install an initital ramdisk and load the driver from there. needed if
   the driver has to be loaded for accessing the root partition. i dont'
   recommend it, unless it's necessary.

2. if it's not needed for accessing root, just but the name of the
   module to /etc/modules. just the name of the module (without .o) on one
   line there. it will be auto-loaded at startup.

3. if you want an automatically loading and unloading of module, for
   e.g. if a device is accessed, you'll need to do an alias of the
   specified device at the proper place below /etc/modutils. see
   examples already there.  never tested it out with ide-scsi, but you
   could try to alias the /dev/sg0 device to ide-scsi. don't forget to
   run update-modules after change. dont's know if this works with
   ide-scsi, never tried it out

-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Kernel panic

2001-04-30 Thread Karsten M. Self

on Tue, May 01, 2001 at 08:21:00AM +0700, Oki DZ ([EMAIL PROTECTED]) wrote:
> Hi,
>
> I have the following in my /var/log/messages (after the system went
> kernel panic):

You may want to provide additional information.

Not familiar with the 2.4 series yet, but check to see if there's a
/usr/src/linux/REPORTING-BUGS file. The attached script may be helpful,
though it's not been compared to the 2.4 series reporting procedures.

Cheers.

--
Karsten M. Self http://kmself.home.netcom.com/
What part of "Gestalt" don't you understand? There is no K5 cabal
http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org
#!/bin/bash

# Kernel bug report generator script
# Script generated from prior bug report form by Karsten M. Self
# $Revision: 1.3 $ $Date: 2000/05/13 07:48:36 $ $Author: root $

# indent by one tabstop
function tabout () { sed -e '/^/s// /'; }

cat <

pgpHeeFkh9LIK.pgp
Description: PGP signature

Re: kernel panic

2006-09-20 Thread Fred J.

"Fred J." <[EMAIL PROTECTED]> wrote: Hion boot, I am getting the error message below after doing the stepsunderneath it.VFS: Cannot open root device "hdb1" on unknown-block (0,0)please append a correct "root=" boot optionkernel panic - not syncing: VFS: unable to mount root fs onunknown-block (0,0)$ sudo apt-get install linux-source-2.6.16$ cd /usr/src$ rm linux$ tar -jxf linux-source-2.6.16.tar.bz2$ ln -s linux-source-2.6.16 linux$ cd linux$ cp /boot/config-2.6.15-1-686 .config$ make oldconfig(accept all the defaults)$ fakeroot make-kpkg clean$ fakeroot make-kpkg --append-to-versionfiltered=.060919 kernel_image# dpkg -i
 kernel-image-2.6.16.060919_10.00.Custom_i386.debhere is my /boot/grup/menu.listdefault 0timeout 5color cyan/blue  white/bluetitle   Debian GNU/Linux, kernel 2.6.16.1root    (hd1,0)kernel  /boot/vmlinuz-2.6.16.1 root=/dev/hdb1 ro savedefaulttitle   Debian GNU/Linux, kernel 2.6.16.1 (recovery mode)root    (hd1,0)kernel  /boot/vmlinuz-2.6.16.1 root=/dev/hdb1 ro singlesavedefaulttitle   Debian GNU/Linux, kernel
 2.6.15-1-686root    (hd1,0)kernel  /boot/vmlinuz-2.6.15-1-686 root=/dev/hdb1 ro  initrd  /boot/initrd.img-2.6.15-1-686savedefaulttitle   Debian GNU/Linux, kernel 2.6.15-1-686 (recovery mode)root    (hd1,0)kernel  /boot/vmlinuz-2.6.15-1-686 root=/dev/hdb1 ro singleinitrd  /boot/initrd.img-2.6.15-1-686savedefaulttitle   Other operating systems:roottitle   Microsoft Windows 2000
 Professionalroot    (hd0,0)savedefaultmakeactivechainloader +1more info:in the above grub/menu.list, I noticed there is no initrd  /boot/initrd.img-2.6.16well, look at this:[EMAIL PROTECTED]:~$ ls -l /boot/; ls -l /usr/src/; dpkg -l linux-image* | grep ^ii; total 8322-rw-r--r-- 1 root root   65416 2006-03-06 23:30 config-2.6.15-1-686-rw-r--r-- 1 root root   64362 2006-09-20 18:27 config-2.6.16.1drwxr-xr-x 2 root root    1024 2006-09-21 03:36 grub-rw-r--r-- 1 root root 4722380 2006-09-19 21:09 initrd.img-2.6.15-1-686-rw-r--r-- 1 root root  680667 2006-03-07 02:31 System.map-2.6.15-1-686-rw-r--r-- 1 root root  650025 2006-09-20 21:03 System.map-2.6.16.1-rw-r--r-- 1 root root 1147143 2006-03-07 02:30
 vmlinuz-2.6.15-1-686-rw-r--r-- 1 root root 1146244 2006-09-20 21:03 vmlinuz-2.6.16.1total 54832lrwxrwxrwx  1 fred src    19 2006-09-17 05:16 linux -> linux-source-2.6.16-rw-r--r--  1 fred src  15058280 2006-09-20 21:05 linux-image-2.6.16.1_2.6.16.1-10.00.Custom_i386.debdrwxr-sr-x 21 fred src  4096 2006-09-21 03:59 linux-source-2.6.16-rw-r--r--  1 root root 41014224 2006-08-19 07:59 linux-source-2.6.16.tar.bz2ii  linux-image-2.6.15-1-686  2.6.15-8   Linux kernel 2.6.15 image on PPro/Celeron/PIii  linux-image-2.6.16.1  2.6.16.1-10.00.Custom  Linux kernel binary image for version 2.6.16[EMAIL PROTECTED]:~$ I really don't know why. 
	
	
		Want to be your own boss? Learn how on  Yahoo! Small Business.

Re: kernel panic

2006-09-20 Thread Roman Laubinger

On Wed, Sep 20, 2006 at 11:25:22AM -0700, Fred J. wrote:
>  VFS: Cannot open root device "hdb1" on unknown-block (0,0)
>  please append a correct "root=" boot option

Hm. I had this with a kernel > 2.6.16 under gentoo (before I
switched over). The solution was to compile GENERIC_IDE_SUPPORT into
the kernel. You'll find it under ATA-Devices in the device drivers
section.

Hope that helps.

Cheers
Roman

___ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2006-09-20 Thread Jason Stelzer


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


On Sep 20, 2006, at 5:30 PM, Roman Laubinger wrote:


On Wed, Sep 20, 2006 at 11:25:22AM -0700, Fred J. wrote:

 VFS: Cannot open root device "hdb1" on unknown-block (0,0)
 please append a correct "root=" boot option


Hm. I had this with a kernel > 2.6.16 under gentoo (before I
switched over). The solution was to compile GENERIC_IDE_SUPPORT into
the kernel. You'll find it under ATA-Devices in the device drivers
section.



Depending on your hardware, that can work. An alternative since  
you're using the old config file is to recreate an appropriate  
initial ramdisk which bootstraps needed kernel modules. See mkinitrd  
and the various linux kernel howtos for details.



- --
J.


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFFEag6vxud+cMTf5IRArxjAKCG3x3oxlwUBfVuS8/DcdBEgwB2PACeLmj4
C8YRoLl0qDFnhL0Q4y+EDq4=
=qbJe
-END PGP SIGNATURE-


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2006-09-20 Thread Fred J.

Roman Laubinger <[EMAIL PROTECTED]> wrote: On Wed, Sep 20, 2006 at 11:25:22AM -0700, Fred J. wrote:>  VFS: Cannot open root device "hdb1" on unknown-block (0,0)>  please append a correct "root=" boot optionHm. I had this with a kernel > 2.6.16 under gentoo (before Iswitched over). The solution was to compile GENERIC_IDE_SUPPORT intothe kernel. You'll find it under ATA-Devices in the device driverssection.did that for no avail. same problem# IDE chipset support/bugfixes#CONFIG_IDE_GENERIC=y...not sure if this help;after I installed my custom compiled kernel, I don't have a/boob/initrd.img-2.6.16.1 file. is this a problem?[EMAIL PROTECTED]:~$ ls -l /boot/total 8373-rw-r--r-- 1 root root   65416 2006-03-06
 23:30 config-2.6.15-1-686-rw-r--r-- 1 root root   64396 2006-09-21 12:18 config-2.6.16.1drwxr-xr-x 2 root root    1024 2006-09-21 15:28 grub-rw-r--r-- 1 root root 4722380 2006-09-19 21:09 initrd.img-2.6.15-1-686-rw-r--r-- 1 root root  680667 2006-03-07 02:31 System.map-2.6.15-1-686-rw-r--r-- 1 root root  668074 2006-09-21 15:03 System.map-2.6.16.1-rw-r--r-- 1 root root 1147143 2006-03-07 02:30 vmlinuz-2.6.15-1-686-rw-r--r-- 1 root root 1180672 2006-09-21 15:03 vmlinuz-2.6.16.1[EMAIL PROTECTED]:~$  
		How low will we go? Check out Yahoo! Messengers low  PC-to-Phone call rates.

Re: kernel panic

2008-12-09 Thread Emanoil Kotsev

Olivier Deckers wrote:

> Hello,
> 
> I have a machine running debian in text-only mode, and I am having a lot
> of kernel panics lately, while downloading torrent files with rtorrent.
> An image with the screen dump can be found at
> http://users.telenet.be/olivierdeckers/kpanic.jpg
> I have no idea what I can do about it, and I would appreciate any help
> because this machine is also used as a server.
> 
> Many thanks in advance,
> olivier

why not trying newer kernel?

regards


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2008-12-09 Thread Olivier Deckers

Is it possible to update the kernel with default options? Because I have 
no idea what modules should be included in the new kernel.


Emanoil Kotsev schreef:

Olivier Deckers wrote:

  

Hello,

I have a machine running debian in text-only mode, and I am having a lot
of kernel panics lately, while downloading torrent files with rtorrent.
An image with the screen dump can be found at
http://users.telenet.be/olivierdeckers/kpanic.jpg
I have no idea what I can do about it, and I would appreciate any help
because this machine is also used as a server.

Many thanks in advance,
olivier



why not trying newer kernel?

regards


  



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2008-12-10 Thread Emanoil Kotsev

Olivier Deckers wrote:

> Is it possible to update the kernel with default options? Because I have
> no idea what modules should be included in the new kernel.
> 
> Emanoil Kotsev schreef:
>> Olivier Deckers wrote:
>>
>>   
>>> Hello,
>>>
>>> I have a machine running debian in text-only mode, and I am having a lot
>>> of kernel panics lately, while downloading torrent files with rtorrent.
>>> An image with the screen dump can be found at
>>> http://users.telenet.be/olivierdeckers/kpanic.jpg
>>> I have no idea what I can do about it, and I would appreciate any help
>>> because this machine is also used as a server.
>>>
>>> Many thanks in advance,
>>> olivier
>>> 
>>
>> why not trying newer kernel?
>>
>> regards
>>
>>
>>

I would try first the stock debian kernel like 2.6.26.
If it is not working you may keep and fall back to your current 2.6.18.
I think that the bug might be resolved in recent kernel version.

regards


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2008-12-11 Thread Olivier Deckers





I installed 2.6.24 (etchnhalf), but the problem still remains. When
tranferring large files over the network, the kernel still panics after
a while.

Emanoil Kotsev schreef:

  Olivier Deckers wrote:

  
  
Is it possible to update the kernel with default options? Because I have
no idea what modules should be included in the new kernel.

Emanoil Kotsev schreef:


  Olivier Deckers wrote:

  
  
  
Hello,

I have a machine running debian in text-only mode, and I am having a lot
of kernel panics lately, while downloading torrent files with rtorrent.
An image with the screen dump can be found at
http://users.telenet.be/olivierdeckers/kpanic.jpg
I have no idea what I can do about it, and I would appreciate any help
because this machine is also used as a server.

Many thanks in advance,
olivier


  
  why not trying newer kernel?

regards



  

  
  
I would try first the stock debian kernel like 2.6.26.
If it is not working you may keep and fall back to your current 2.6.18.
I think that the bug might be resolved in recent kernel version.

regards


  





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel-panic !!!

1998-02-07 Thread Bob Nielsen

Does the file /usr/bin/as86 exist?   Is the bin86 package installed?  If
not, install it.

On Sat, 7 Feb 1998, Lothar Krenzien wrote:

> Hi everybody !
> 
> I´m using Debian 1.3.1. from the german computer magazin "Chip"
> and have a very misterious problem when I want to build / compile
> a customize kernel. On every time I use "make zImage" after about 5
> minutes
> I get an error like " command as86 (also ld86) not found , leaving
> directory ./linux/arch/i386/boot, [bootsect.o] Error 127, [zImage] Error
> 
> 2" . And the process aborts without anything done. When I use "make
> bzImage" the end is the same.
> I tryed it with many configurations and kernel sources ( 2.0.29 - 2.0.33
> 
> ). But nothing work. I also edited the Makefile in that directory and
> comment out the lines with this operations. Then I get only errors
> like "unknown ( or invalid ) processor command ". Then I probed to
> rename
> the files /usr/i486-linuxaout/bin/as and ld to as86 and ld86 or create
> a link from the directory named above to these files. It didn´t
> work. I used "make menuconfig" because "make xconfig" didn´t work.
> But X with the KDE display manager works fine. All the required links
> should
> be ok. I didn´t have any *.rej after that or a file /usr/bin/encaps
> ( a tip from the S.u.S.e online support database ) ." Make dep" and "
> make
> clean" worked correct. I don´t know what could it be. Perhaps has
> somebody other an idea or can help me in any way (but I don´t want to do
> an BIOS update). I had a problem like this also with an older Slackware
> distribution.
> Then I have an another problem with kdm. Since few days it doesn´t work
> and I don´t no why.
> The problem is that I don´t get any error messages or entrys in
> log-files or so on. The programm just don´t do anything. I can type in
> "xdm" and after 1 or 2 seconds I see the prompt again. That´s all ! On
> reason could be that the file /etc/init.de/xdm has 0 byte and is empty.
> Does somebody know from where I can get an installation package ? On the
> CD or the Debian ftp-Server I didn´t found it.
> 
> greetings
> Lothar
> 
> Some informations about my system :
> =
> harddisk : Seagate ST52520A ; 2.5 GB (IDE)
> board : Octek Rhino 9 HX PCI
> graphic : Matrox Mystique (yes ... ) 2 MB
> processor : Cyrix 6x86 P166 + Rev. 2.7
> other : Soundblaster 16 PnP ( ... ) and Hauppauge WinTV/pci ( also
> called as WinCastTV)
> Win95b on a primary partition (hda1) and Linux on a logical partition
> (hda5 and hda6)
> LILO in MBR
> Award PnP PCI-Bios v. 4.51PG 1996
> 
> Some Debian informations :
> 
> gcc-2.7.2.1-3
> libc4-4.6.27-15
> libc5-5.4.17-1
> libc5-dev-5.4.17-1
> libc5-pic-5.4.17-1
> binutils-2.7-5
> ldso-1.8.5-1
> make-3.75-1
> dpkg-dev-1.4.0.5
> 
> 
> 
> --
> TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
> [EMAIL PROTECTED] . 
> Trouble?  e-mail to [EMAIL PROTECTED] .
> 
> 

---
Bob Nielsen Internet: [EMAIL PROTECTED]
Tucson, AZ  AMPRnet: [EMAIL PROTECTED]
http://www.primenet.com/~nielsen/


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: kernel panic

1997-10-28 Thread Ben Pfaff

I Brake for Moths <[EMAIL PROTECTED]> writes:
> I am trying to install Debian on an EISA wide SCSI machine.  When the
> resc1440.bin kernel boots (no boot parameters), it gets to the aic7xxx
> section and properly detects the SCSI controller (Adaptec AHA 2740),
> resets the SCSI bus, then panics with this message: 
> 
> aic7xxx: (aicxxx_isr) Encountered spurious interrupt
> scsi0: BRKADRINT error (0x1):
>   Illegal Host Access
> Kernel panic: scsi0: BRKADRINT, error 0x1, seqaddr 0x0.

Have you tried recompiling the kernel with all the aic7xxx options
turned off?  I find that my 2940UW card doesn't work right if I turn
on some of the aic7xxx options, but it works fine with all of them
off.
-- 
Ben Pfaff <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Senders of unsolicited commercial e-mail will receive free 32MB core files!


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Kernel Panic

1999-03-31 Thread Jens B. Jorgensen

[EMAIL PROTECTED] wrote:

> I had my system hang last night while running a statistical process.  I used 
> Ctrl-Alt-Delete to
> reboot.  Now I get a kernel panic.
>
> UMSDOS: msdos_read_super failed, mount aborted ...
>
> HPFS: hpfs_read_super: Not HPFS ...
>
> Kernel panic: VFS: Unable to mount root fs on 03:05
>
> Does 03:05 mean 3rd harddisk, 5th partition?  Linux is on Harddisk 1, 
> partition 05.

03:05 means the device with major number 3, minor number 5. This is in fact 
/dev/hda5.

> Other things I have tried.
>
> Booting from floppy, same error.
>
> I have OS2 on my system as well. I dualboot to DOS and try the Debian install 
> CD, but I get
>
> boot from dos install
>   ran out of input data   ---system halted
>
> When I was compiling a kernel before I was able to use this to reset lilo but 
> now it won't
> work.
>
> I have ext2-os2 so I should be able to read my linux partitions from OS2, but 
> I am not able to
> read the Linux partition.
>
> Any suggestions on how to solve this problem?

Boot the rescue disk. After you get to the menus go down all the way to the 
option to exit to a
shell. At the shell prompt run: 'e2fsck /dev/hda5' to fix the file system.

Good luck!

--
Jens B. Jorgensen
[EMAIL PROTECTED]

Re: Kernel panic!

1999-08-16 Thread Alvin Oga


hi 

> VFS: cannot open root device 03:01
> Kernel panic: VFS: Unable to mount root fs on 03:01

i get the same silly error when I tried 2.2.10 on my rh-6.0 box...
( that is /dev/hda1 )

i gave up trying to find out whyand just reverted back to 
2.2.5-15 from rh...  will try again later...

have fun
alvin

> What does this message mean?? The kernel booted from /dev/hda1 so why can't it
> mount the root partition now? I've tried giving Linux the different
> combinations of the "root=..." parameter but it doesn't seem to work.
> 
> Does it matter which version of LILO I use to install the boot sector??
> This system is running kernel 2.2.10 (custom build) and most packages are from
> potato. Due to some problems I had to use an older (slink) version of LILO --
> will this screw it up? It seemed to be fine when I booted this same HD on my
> other machine (with the LILO setup for the other machine, of course).
> 
> Also, if LILO is the cause of the problem, how would I run a glibc2.1 version
> of LILO from a slink rescue disk??? I don't have a potato boot disk handy...
>

Re: Kernel panic!

1999-08-17 Thread Hwei Sheng TEOH


Hi all! Thanks for the replies...

I managed to figure out what was wrong: my custom-compiled kernel had the IDE
drivers as *modules* (and I didn't list them in /etc/modules) -- so after the
kernel finished initializing, it discovers that it didn't know *how* to read
/dev/hda1 because it hadn't loaded the IDE drivers yet!! That was what the
kernel panic was all about. :-)

Silly, silly, me... don't know why in the world I would configure the IDE
drivers to be modules rather than compiled-in, but after managing to boot into
the system with the older kernel on my Rescue Disk (which, of course, had
built-in IDE drivers, not modules), I managed to recompile the kernel with the
right config. Now the server is up and running.

Thanks anyway for the help...


T

Re: Kernel panic

1997-04-07 Thread G. Kapetanios

Thanks for your reply

I am afraid root is set to /dev/hda3 
The precompiled 2.0.29 kernel works fine. The problem seems to be in the
options chosen for the new kernel . I just don't know which one I must
change  :-( 
Thanks
  George 


On Mon, 7 Apr 1997, Steffen R. Mueller wrote:

> Thus spake G. Kapetanios ([EMAIL PROTECTED]):
> 
> Hi George,
> 
> > Two days ago I managed to recompile my own kernel. It went roughly OK
> > I only tried it on my office computer today though and there seems to be a
> > problem. I seem to have  chosen a wrong option since at a very early stage
> > of booting I get the following error
> > 
> > VFS: cannot open root device 03:03
> > kernel panic VFS: unable to mount root fs on 03:03
> 
> Oh, then only the root device was set wrong. Asuming you're using LILO you
> can force to mount the boot device like /dev/hda3 with the following command
> on the LILO prompt :
> 
> LILO : linux root=/dev/hda3
> 
> This should work. After doing that you can change the root device used by
> default with the rdev command.
> 
> man rdev will give you the required information.
> 
> BTW : rdev can also change the video mode a.s.o.
> 
> You see... not really a big problem ;-)
> 
> Greetings,
> 
> Steffen
> -- 
> -
> NTG Netzwerk und Telematic GmbH, Sitz Chemnitz.
> Kreisgericht Chemnitz/Stadt HRB 4217 Geschaeftsfuehrer: Michael Rotert
> -
> Steffen R. Mueller __  ___ _   _ email: [EMAIL PROTECTED]
> NTG Netzwerk und Telematic GmbH\ \/ / (_)_ __ | | __ fax  : +49 721 9652 210
> Geschaeftsbereich Xlink \  /| | | '_ \| |/ / phone: +49 721 9652 211
> Vincenz-Priessnitz-Str. 3   /  \| | | | | |   <  RIPE : SM25-RIPE
> D-76131 Karlsruhe, Germany /_/\_\_|_|_| |_|_|\_\ WWW.Xlink.net/~steffen
>INTERNET. MIT SICHERHEIT
> 

---
George Kapetanios
Churchill College
Cambridge, CB3 0DS  
U.K.E-Mail: [EMAIL PROTECTED]
---

Re: Kernel panic

1997-04-07 Thread David Wright

On Mon, 7 Apr 1997, G. Kapetanios wrote:
> Two days ago I managed to recompile my own kernel. It went roughly OK
> I only tried it on my office computer today though and there seems to be a
> problem. I seem to have  chosen a wrong option since at a very early stage
> of booting I get the following error
> 
> VFS: cannot open root device 03:03
> kernel panic VFS: unable to mount root fs on 03:03
Perhaps you forgot to compile in EIDE support (if you have an EIDE disk,
which most modern non-SCSI disks are)?
--
David Wright, Open University, Earth Science Department, Milton Keynes MK7 6AA
U.K.  email: [EMAIL PROTECTED]  tel: +44 1908 653 739  fax: +44 1908 655 151

Re: Kernel panic

1997-04-07 Thread Paul Chau

Probably you have all the filesystem drivers modularised. Have a look
of /usr/src/linux/.config and check if ext2fs got an answer of y or m in
the configuration.

Regards.
Paul :)

On Mon, 7 Apr 1997, G. Kapetanios wrote:

> 
> Hi,
> 
> Two days ago I managed to recompile my own kernel. It went roughly OK
> I only tried it on my office computer today though and there seems to be a
> problem. I seem to have  chosen a wrong option since at a very early stage
> of booting I get the following error
> 
> VFS: cannot open root device 03:03
> kernel panic VFS: unable to mount root fs on 03:03
> 
> 
> Could somebody please tell me what went wrong?
> 
> I have /dev/hda1 as my dos partition /dev/hda2 as my swap partition and 
> /de/hda3 as my root partition 
> 
> I would appreciate any help.
> 
>Thanks 
>George 
>  
> 
> 
> ---
> George Kapetanios
> Churchill College
> Cambridge, CB3 0DS  
> U.K.E-Mail: [EMAIL PROTECTED]
> ---
> 
>

Re: Kernel panic

1997-04-16 Thread G. Kapetanios

On Wed, 16 Apr 1997, Pilon wrote:

> I am getting this message while booting my  Linux box:
> 
> "VFS unable to mount root fs on 03:03"
> 
> Can someone tell me what does it mean?
> 
> 
> --
> TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
> [EMAIL PROTECTED] . 
> Trouble?  e-mail to [EMAIL PROTECTED] .
> 
> 

If you have compiled your own  kernel you probably forgot to include
support for your hard disk. If you have a IDE hard disk set 

CONFIG_BLK_DEV_IDE to y. 
George 


---
George Kapetanios
Churchill College
Cambridge, CB3 0DSE-Mail: [EMAIL PROTECTED]
U.K.  WWW: http://garfield.chu.cam.ac.uk/~gk205/work_info.html
---



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Kernel Panic

1997-07-08 Thread Emilio Lopes

> "SA" == Syd Alsobrook <[EMAIL PROTECTED]> writes:

SA> I just recently compiled a new kernel on my linux box, this isn't
SA> the first time that I have done this, but this the first one that
SA> had a problem. After recompiling the kernel servel times with
SA> different options and decided to check here.  The compile runs
SA> fine with no problems but when I boot it I get the following
SA> message.

SA> VFS: Cannot open root dev 03:01
SA> Kernel Panic: VFS: Unable to mount root fs on 03:01

Did you included the driver for your root filesystem (probable ext2)
in the kernel (*not* as a module)? Seems to be the problem here.

-- 
 Emilio C. Lopes 


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Kernel Panic

1997-07-08 Thread Syd Alsobrook

At 09:36 PM 7/8/97 +0200, you wrote:
>Did you included the driver for your root filesystem (probable ext2)
>in the kernel (*not* as a module)? Seems to be the problem here.
>
>-- 
> Emilio C. Lopes 
 Yeh, But I think that I figuared out the problem. I compiled some
controller chipsets in that my machine does not have I just ran another
compile and it works great. Thanks Alot
Syd

http://www.uc.edu/~alsobrsp

"How do you know you're having fun   
 if there's no one watching you have it."
Douglas Adams
-BEGIN PGP PUBLIC KEY BLOCK-
Version: 2.6.2

mQCNAzN3eq0AAAEEAMGqDqrPkUM0PEPT4UBXCVDylEkUabrkqq/yBk1koSqHWlxs
02wVIVl/2B33MuS1aF3XfjvQLH2J6VJTUtyOwH2yglfpyJ68/TaE7od2gT3V99ax
a/bENj3x5xnCxQFuKJCBUi4l5CoHEEn8Og6I0IS3vz+nJFkKF0AiZe6TgKrhAAUR
tCVTeWQgQWxzb2Jyb29rIDxhbHNvYnJzcEBlbWFpbC51Yy5lZHU+iQCVAwUQM3eI
00AiZe6TgKrhAQHMWAP/W/ZacyMwNrHF0LU3eMyzTbjeFotEws1FmmE2ALjTgVI2
emtsN7vynlZ17p4qPDPlO18G/PTQ2r61kIywmn3bApaTsij5wSXMYv+4VRUvs1wX
Ie8gHs6jGZBa3wnutCzaDDW/VPy/atpvLSWTc7Mku1BJzee5whRxxw+QUK2KjD0=
=EjnG
-END PGP PUBLIC KEY BLOCK-


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Kernel Panic

1997-07-09 Thread joost witteveen

> Hello!
> 
>   I just recently compiled a new kernel on my linux box, this isn't the
> first time that I have done this, but this the first one that had a
> problem. After recompiling the kernel servel times with different options
> and decided to check here.
>   The compile runs fine with no problems but when I boot it I get the
> following message.
> 
>   VFS: Cannot open root dev 03:01
>   Kernel Panic: VFS: Unable to mount root fs on 03:01

Probably no support for your root filesystem compiled in.
Did you say "yes" to ext2 in the "make config" stage?

Another option may be (I'm not sure) that you have SCSII disks, and
your kernel is apparently (dev 03:01) configured to load the first
partition on the first IDE disk. If so, change the "root = /dev/hda1"
statement in /etc/lilo.conf to where your root fs really is.

-- 
joost witteveen, [EMAIL PROTECTED]
#!/usr/bin/perl -sp0777ihttp://www.dcs.ex.ac.uk/~aba/rsa/


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? 
e-mail to [EMAIL PROTECTED] .

Re: Kernel Panic !!!!!

1997-10-18 Thread Brandon Mitchell

On Sat, 18 Oct 1997, PATRICK DAHIROC wrote:

>   hda: read_intr: status=0x59 {DriveReady SeekComplete DataRequest
>   Error}
>   hda: read-intr: error 0x49 {UncorrectableError}, LBAsect=1897876,
>   sector 180244
>   end_request: I/O dev 03:02 sector 180244

> Is this as serious as it looks?  

Maybe, maybe not.  Best case, you found your first bad block.  Get a list
of the bad blocks from the badblocks program and use that with fsck to
mark these as unusable.  Worst case, you are seeing the beginning of the
end of your harddrive.  The more you see, the worse it is.  And if they
keep increasing, get a new harddrive, it's not worth the trouble.  Either
way, you need to use a rescue disk, and if you can, backup anything you
want to keep.

Good luck,
Brandon

-
Brandon Mitchell <[EMAIL PROTECTED]>   "We all know linux is great... it
PGP: finger -l [EMAIL PROTECTED]  does infinite loops in 5 seconds"
Phone: (757) 221-4847  --Linus Trovalds

--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Kernel Panic !!!!!

1997-10-18 Thread Lorens Kockum

On Sat, Oct 18, 1997 at 03:12:21AM -0400, Brandon Mitchell wrote:
> 
> Maybe, maybe not.  Best case, you found your first bad block.

It can't always have been there, the machine worked before ...

> Worst case, you are seeing the beginning of the end of your harddrive.

If the drive isn't too old, but is running hot, that's certainly the
problem. Make sure your new hard-disk is well ventilated.

-- 
include   Lorens KOCKUM ( [EMAIL PROTECTED] )

--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: kernel panic

2004-07-15 Thread Robert William Hutton

Marvin Gerardo Aguero Salazar wrote:
I am trying to install the kernel 2.6.6, so I downloaded it, compiled it
and installed it, but, when I boot I get a whole bunch of errors.
How did you build it (make or make-kpkg)?  Did you use an initrd?  Are you on 
stable/testing/unstable?

Unfortunately I haven't been able to grab all the messages it displays
while booting, but the last ones I see on the screen show the following:
modprobe: Can't open dependencies file /lib/modules/2.6.6/modules.dep
(No such file or directory)
-> This is strange for the file does exist. I have checked the
permissions and it has the same permissions for the current kernel (2.4).
mount: /dev2/root2 is not a valid block device
-> This message is displayed 8 times. When did that 2 come from?
/scripts/ext3-add-journal.sh: 30: cannot open /mnt/etc/fstab: No such file
-> Well, it's true. That file does not exist.
mount: /dev2/root2 is not a valid block device
-> This message is displayed 8 times.
pivot_root: No such file or directory
/sbin/init: 348: cannot open dev/console: No such file
kernel panic: Attempted to kill init!
Any ideas of what I have done wrong here?
Does anyone know what is going on here and how to fix it?
Ok, this all looks like you've compiled the kernel with an initrd, and not 
loaded it at boot.  Or you've just compiled your HDD driver as a module...

In order for the kernel to boot and start reading from your hard disks (which is 
really useful), it needs to load the driver for your hard drive controller. 
Now, this can either be compiled into the kernel, or included as a module in an 
initrd (initial ramdisk).  Debian's stock kernels do the latter, as this allows 
a greater number of drivers to be included.

If you compile the HDD controller driver as a module, but don't have an initrd, 
you have the chicken-and-the-egg problem of needing the driver to read the disk, 
but having it stored as a module ON the disk.  You can see why the kernel might 
get a bit panicy about this situation.

What I recommend you do is boot into a debian stock kernel, and watch the boot 
messages (which can be recalled on the command line with the "dmesg" command). 
Look for the line which tells you which HDD controller driver is loaded. 
Something like this:

Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH3M: IDE controller at PCI slot :00:1f.1
ICH3M: chipset revision 2
ICH3M: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xcfa0-0xcfa7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xcfa8-0xcfaf, BIOS settings: hdc:DMA, hdd:pio
You can see from the above, that my HDD controller uses the ICH3M chipset.  This 
is the info you need, generally.  Now go into your kernel config, and compile 
this into the kernel (not as a module).  Rebuild, reinstall, run LILO and 
reboot.  If you're lucky and managed to get the correct HDD controller driver, 
everything should work.

HTH,
Rob.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2004-08-26 Thread Martin Dickopp

geekboy <[EMAIL PROTECTED]> writes:

> Just tried upgrading my kernel from knoppix 2.4.22xfs to 2.4.26-1-k7
> while booting it grinds to a halt with error:
>
> freeing initrd memory: 3956k freed
> FAT: bogus logical sectro size 0
> kernel panic: VFS : unable to mount root fs on 03:05
>
> So the initrd.img is working. remembered to run lilo after upgrade.
> does the 03:05 mean the fat partition on hda3 is screwed?

No, 03:05 refers to hda5. It means the kernel cannot mount hda5 as the
root filesystem. Is it perhaps trying to mount it as fat32, while it is
in fact ext2?

> hda5 is the root ext2 partition
> have hda1 ntfs still for now.
> hda3 fat32
> hda6 swap
> hda7  an ext2 linux partition (/backup)

Martin


-- 
   ,--.  ,= ,-_-. =.
  / ,- )Martin Dickopp, Dresden, Germany((_/)o o(\_))
  \ `-'http://www.zero-based.org/`-'(. .)`-'
   `-.   \_/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2004-08-26 Thread geekboy

Martin Dickopp wrote:

freeing initrd memory: 3956k freed
FAT: bogus logical sectro size 0
kernel panic: VFS : unable to mount root fs on 03:05
So the initrd.img is working. remembered to run lilo after upgrade.
does the 03:05 mean the fat partition on hda3 is screwed?
   

No, 03:05 refers to hda5. It means the kernel cannot mount hda5 as the
root filesystem. Is it perhaps trying to mount it as fat32, while it is
in fact ext2?
 

Okay well I checked fstab, and it's listed as loading it as ext2.
I removed the fat32 partition just in case (from fstab & with cfdisk remove)
and it still panics.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2004-08-26 Thread John Summerfield

geekboy wrote:
Martin Dickopp wrote:

freeing initrd memory: 3956k freed
FAT: bogus logical sectro size 0
kernel panic: VFS : unable to mount root fs on 03:05
So the initrd.img is working. remembered to run lilo after upgrade.
does the 03:05 mean the fat partition on hda3 is screwed?
  

No, 03:05 refers to hda5. It means the kernel cannot mount hda5 as the
root filesystem. Is it perhaps trying to mount it as fat32, while it is
in fact ext2?
 

Okay well I checked fstab, and it's listed as loading it as ext2.
I removed the fat32 partition just in case (from fstab & with cfdisk 
remove)
and it still panics.

I'm with Martin in that the problem is with hda5. Here's how to tell:
kowari:~# ls /dev/hda5
brw-rw  1 root disk 3, 5 Mar 15  2002 /dev/hda5
kowari:~#
Presumably your kernel commandline iis something like this:
root=/dev/hda5 ro
Now,it's likely that support for ext2 is in a module. If so, then your 
kernel can't read the filesystem until the module is loaded.

The module should be in your initial ram disk. I see you are using one, 
so you need to check on how it's created.


--
Cheers
John
-- spambait
[EMAIL PROTECTED]  [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2004-05-24 Thread Shaul Karl

On Sun, May 23, 2004 at 06:59:39PM -0700, [EMAIL PROTECTED] wrote:
> I am dual booting xp and linux on a single harddrive.  I got both booting
> with xp controlling the mbr and I added my linux grub bootsector to the xp
> boot.ini in order to get linux to boot.  I installed debian off the sarge
> net install cd using the 2.6 kernel.  The kernel that came with it runs
> fine, but I compiled and installed a new kernel and it will not run.  When
> I boot to it, it complains :
> VFS: Cannot open root device "hda3" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
> 
> By the way:
> /dev/hda3 is /
> /dev/hda6 is boot
> 
> The auto generated boot options in grub are as follows(the top two work,
> the bootom don't):
> 
> title   Debian GNU/Linux, kernel 2.6.5-1-386
> root(hd0,5)
> kernel  /vmlinuz-2.6.5-1-386 root=/dev/hda3 ro
> initrd  /initrd.img-2.6.5-1-386
> savedefault
> boot
> 
> title   Debian GNU/Linux, kernel 2.6.5-1-386 (recovery mode)
> root(hd0,5)
> kernel  /vmlinuz-2.6.5-1-386 root=/dev/hda3 ro single
> initrd  /initrd.img-2.6.5-1-386
> savedefault
> boot
> 
> title   Debian GNU/Linux, kernel 2.6.5
> root(hd0,5)
> kernel  /vmlinuz-2.6.5 root=/dev/hda3 ro
> savedefault
> boot
> 
> title   Debian GNU/Linux, kernel 2.6.5 (recovery mode)
> root(hd0,5)
> kernel  /vmlinuz-2.6.5 root=/dev/hda3 ro single
> savedefault
> boot
> 
> 
> Might this have something to do with the no initrd option?


  Probably. I assume that 2.6.5-1-386 is the installation kernel and
2.6.5 is the one you compiled. How did you compiled your kernel? In
particular, were you using the --initrd flag?


> I thought debian boot loaders used the whole vmlinuz vmlinuz.old scenario,
> is there a way to make this work?


  With grub the vmlinuz vmlinuz.old scenario is named differently. While
the default kernel installation with lilo used the new kernel and the
most recent one, the default kernel installation with grub is using the
new kernel and up to 6 of the previous ones. You might want to take a 
look at /boot/grub/menu.lst.

-- 
"If you have an apple and I have  an apple and we  exchange apples then
you and I will still each have  one apple. But  if you have an idea and I
have an idea and we exchange these ideas, then each of us will have two
ideas." -- George Bernard Shaw (sent by  shaulk @ actcom . net . il)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2004-05-24 Thread Shaul Karl

On Mon, May 24, 2004 at 08:59:21AM -0700, [EMAIL PROTECTED] wrote:
> >
> You are correct, the 2.6.5 is the new one.
> I did not use any flags I just did a make-kpkg kernel_image and a dpkg -i
> I noticed that the new boot loader menu items didn't have the initrd
> lines, is that required.  I didn't think you really needed to use initrd?
> 

  In general, depending on the kernel configuration, you can do without
an initrd. However since the configuration of the new kernel doesn't 
differ much from the old one, it could be that you must have an initrd
because essential components are compiled as modules. Another option is
that for your hardware the difference in the configuration of the old 
and new kernels is important.
  The new boot loader menu items didn't have the initrd lines because it
identified the new kernel as not requiring an initrd. Which is correct
since you didn't make-kpkg --initrd.

-- 
"If you have an apple and I have  an apple and we  exchange apples then
you and I will still each have  one apple. But  if you have an idea and I
have an idea and we exchange these ideas, then each of us will have two
ideas." -- George Bernard Shaw (sent by  shaulk @ actcom . net . il)

-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2004-05-24 Thread developer

>>>I am dual booting xp and linux on a single harddrive.  I got both booting
>>>with xp controlling the mbr and I added my linux grub bootsector to the
>>>xp
>>>boot.ini in order to get linux to boot.  I installed debian off the sarge
>>>net install cd using the 2.6 kernel.  The kernel that came with it runs
>>>fine, but I compiled and installed a new kernel and it will not run. 
>>>When
>>>I boot to it, it complains :
>>>VFS: Cannot open root device "hda3" or unknown-block(0,0)
>>>Please append a correct "root=" boot option
>>>Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
>>>
>>>By the way:
>>>/dev/hda3 is /
>>>/dev/hda6 is boot
>>>
>>>The auto generated boot options in grub are as follows(the top two work,
>>>the bootom don't):

>>>title   Debian GNU/Linux, kernel 2.6.5-1-386
>>>root(hd0,5)
>>>kernel  /vmlinuz-2.6.5-1-386 root=/dev/hda3 ro
>>>initrd  /initrd.img-2.6.5-1-386
>>>savedefault
>>>boot

>>>title   Debian GNU/Linux, kernel 2.6.5-1-386 (recovery mode)
>>>root(hd0,5)
>>>kernel  /vmlinuz-2.6.5-1-386 root=/dev/hda3 ro single
>>>initrd  /initrd.img-2.6.5-1-386
>>>savedefault
>>>boot
>>>
>>>title   Debian GNU/Linux, kernel 2.6.5
>>>root(hd0,5)
>>>kernel  /vmlinuz-2.6.5 root=/dev/hda3 ro
>>>savedefault
>>>boot
>>>
>>>title   Debian GNU/Linux, kernel 2.6.5 (recovery mode)
>>>root(hd0,5)
>>>kernel  /vmlinuz-2.6.5 root=/dev/hda3 ro single
>>>savedefault
>>>boot


>>>Might this have something to do with the no initrd option?
>>>I thought debian boot loaders used the whole vmlinuz vmlinuz.old
>>>scenario,
>>>is there a way to make this work?
> On Mon, May 24, 2004 at 08:59:21AM -0700, [EMAIL PROTECTED] wrote:
>> >
>> You are correct, the 2.6.5 is the new one.
>> I did not use any flags I just did a make-kpkg kernel_image and a dpkg
>> -i
>> I noticed that the new boot loader menu items didn't have the initrd
>> lines, is that required.  I didn't think you really needed to use
>> initrd?
>>
>
>
>   In general, depending on the kernel configuration, you can do without
> an initrd. However since the configuration of the new kernel doesn't
> differ much from the old one, it could be that you must have an initrd
> because essential components are compiled as modules. Another option is
> that for your hardware the difference in the configuration of the old
> and new kernels is important.
>   The new boot loader menu items didn't have the initrd lines because it
> identified the new kernel as not requiring an initrd. Which is correct
> since you didn't make-kpkg --initrd.
>
> --
> "If you have an apple and I have  an apple and we  exchange apples then
> you and I will still each have  one apple. But  if you have an idea and I
> have an idea and we exchange these ideas, then each of us will have two
> ideas." -- George Bernard Shaw (sent by  shaulk @ actcom . net . il)
>

So what you are saying is that what I did is fine?  So why do I get this
kernel panic error???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2004-05-25 Thread Shaul Karl

On Mon, May 24, 2004 at 05:54:59PM -0700, [EMAIL PROTECTED] wrote:
> 
> So what you are saying is that what I did is fine?  So why do I get this
> kernel panic error???


  If the new kernel has built in, as opposed to modules, for everything
that is required to boot then I don't know what to say. 
-- 
"If you have an apple and I have  an apple and we  exchange apples then
you and I will still each have  one apple. But  if you have an idea and I
have an idea and we exchange these ideas, then each of us will have two
ideas." -- George Bernard Shaw (sent by  shaulk @ actcom . net . il)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2004-03-04 Thread Kent West

sda wrote:

Hello Folks:

I'm desperate -- Previous to this morning I had the install bf24 
kernel installed. I read on another list that basically it's intended 
for the install process only and should be replaced for adequate 
performance.

So, I took the plunge and installed '2.4.18.img' and ran lilo 
afterwards. Lilo gave an error on the stanza I added to lilo as per 
the debian installer instructions: I think it was the 
'initrd=/initrd.img' line. I obviously added it to the wrong place.

Anyways, "Murphy's law' conveniently came to be, while I was doing 
this, I let the sink overflow in the kitchen, and the water was 
threating to splash over the electric equipment (power bars etc) that 
runs my 4 workstations. So, because we were tramping through water 
(electrocution possibility to) I had to throw the circuit breaker that 
was responsible for these components.

So, to make a long story short, I'm unable to boot into my Woody 
server, with the newly installed kernel. I tried the rescue disk, but 
it gives me a kernel panic. I tried the 'shift-tab' sequence at the 
lilo prompt, and it only gives me one kernel choice -- I can't see the 
old one.

The messages I'm getting at the kernel are thus;

-root filesytem not mounted
-VFS cannot open root device
-please append a correct root=boot option
-kernel panic
This is way over my head. Is there anything I can do, to mount this box?

I'd rather try to recover it if possible, as I'm not backed up... (I 
know, I know).

Thanks.
You'll need an installer CD or a Knoppix CD or something similar.

Boot off that CD, and at the prompt, enter something like:
linux root=/dev/hda1 single
or
knoppix root=/dev/hda1 single
(with /dev/hda1 being your root partition).
If that gets you in, you should be able to repair your lilo.conf and 
rerun lilo and reboot back into business.

If that doesn't work, boot into the installation normally, and don't 
partition/initialize, but then mount the / and /usr partitions. Then 
shell out (Alt-F2), "chroot /target"; "vi /etc/lilo.conf" and fix; 
"lilo"; Alt-F1 and choose reboot.

--
Kent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2004-03-04 Thread Jonathan Schmitt

Hallo

>So, I took the plunge and installed '2.4.18.img' and ran lilo afterwards. 
Lilo 
>gave an error on the stanza I added to lilo as per the debian installer 
>instructions: I think it was the 'initrd=/initrd.img' line. I obviously added 
it 
>to the wrong place.

You should always keep the old kernel in Your bootmenu to prevent such things, 
this is, what the construct with /vmlinuz and /vmlinuz.old is for.
Nevertheless, You could boot the woody installation disk, select "execute a 
shell" from the menu and then 
mount /dev/hda1 /mnt # assuming this is, where Your root partition is
cd /mnt
chroot /mnt
So You should get back to Your old system environment and be able to rerun 
lilo with Your old kernel in the boot menu.
Best regards
   js

-- 
Any fool can paint a picture, but it takes a wise person to be able to sell 
it.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2004-03-04 Thread sda

Jonathan Schmitt wrote:

Hallo


So, I took the plunge and installed '2.4.18.img' and ran lilo afterwards. 
Lilo 

gave an error on the stanza I added to lilo as per the debian installer 
instructions: I think it was the 'initrd=/initrd.img' line. I obviously added 
it 

to the wrong place.


You should always keep the old kernel in Your bootmenu to prevent such things, 
this is, what the construct with /vmlinuz and /vmlinuz.old is for.
Nevertheless, You could boot the woody installation disk, select "execute a 
shell" from the menu and then 
mount /dev/hda1 /mnt # assuming this is, where Your root partition is
cd /mnt
chroot /mnt
So You should get back to Your old system environment and be able to rerun 
lilo with Your old kernel in the boot menu.
Best regards
   js



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2004-03-04 Thread sda

Jonathan Schmitt wrote:



> You should always keep the old kernel in Your bootmenu to prevent such things,
> this is, what the construct with /vmlinuz and /vmlinuz.old is for.
Yes, however, I didn't delete anything... When I was working in Lilo previous to 
the 'accident', the old config was there. Beats me what happened to it. It was 
called 'Linux.old'

> Nevertheless, You could boot the woody installation disk, select "execute a
> shell" from the menu and then
> mount /dev/hda1 /mnt # assuming this is, where Your root partition is
> cd /mnt
> chroot /mnt
Yeah, I did something similar prior to posting on debian-user. I booted from the 
install cd, attempted to rescue/mount hda1, but the system kept saying 'invalid 
argument'.

> So You should get back to Your old system environment and be able to rerun
> lilo with Your old kernel in the boot menu.
> Best regards
>js
I'll try your commands above.

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2004-03-04 Thread Jonathan Schmitt


>Yes, however, I didn't delete anything... When I was working in Lilo previous 
to 
>the 'accident', the old config was there. Beats me what happened to it. It 
was 
>called 'Linux.old'

Generally, it's a wise idea, not to touch lilo.conf anymore unless You have 
to. The debian-way is to move Your kernel somewhere and set a soft-link to 
it, pointing to /vmlinuz. You should save the old /vmlinuz to vmlinuz.old 
prior to that.
If You do so, You'll always find Your old, working configuration using the 
"Linux.OLD" entry in the lilo menu.

>Yeah, I did something similar prior to posting on debian-user. I booted from 
the 
>install cd, attempted to rescue/mount hda1, but the system kept saying 
'invalid 
>argument'.

The correct argument, as far as I remember is "rescue root=/dev/hda1". Aside 
from that, it is a different approach. If You've already deleted the 2.2.19 
modules on Your disk, rescue using this method might be impossible, because 
You might get trapped in an infinite loop, trying to load modules, no longer 
there.

Best regards,
   js
-- 
I can't drive 55.
I'm looking forward to not being able to drive 65, either.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2004-03-04 Thread edward

Yes. Your simplest option (going from memory here) is to boot off the CD
again, choose the bf24 kernel, skip the majority of the configuration
options, opting instead for mount previous installation, install lilo, and
reboot - then you should be back in bussiness.
NOTE: I'm at uni at the moment, doing this from memory, if anything look
weird, cancel out and let me know, I'll be home in a couple of hours, atwhich point I 
can actually take a look myself at the menu and give you the
exact instructions.
Cheers
Edward

> Hello Folks:
>
> I'm desperate -- Previous to this morning I had the install bf24 kernel
>  installed. I read on another list that basically it's intended for the
> install  process only and should be replaced for adequate performance.
>
> So, I took the plunge and installed '2.4.18.img' and ran lilo
> afterwards. Lilo  gave an error on the stanza I added to lilo as per
> the debian installer  instructions: I think it was the
> 'initrd=/initrd.img' line. I obviously added it  to the wrong place.
>
> Anyways, "Murphy's law' conveniently came to be, while I was doing
> this, I let  the sink overflow in the kitchen, and the water was
> threating to splash over the  electric equipment (power bars etc) that
> runs my 4 workstations. So, because we  were tramping through water
> (electrocution possibility to) I had to throw the  circuit breaker that
> was responsible for these components.
>
> So, to make a long story short, I'm unable to boot into my Woody
> server, with  the newly installed kernel. I tried the rescue disk, but
> it gives me a kernel  panic. I tried the 'shift-tab' sequence at the
> lilo prompt, and it only gives me  one kernel choice -- I can't see the
> old one.
>
> The messages I'm getting at the kernel are thus;
>
>   -root filesytem not mounted
>   -VFS cannot open root device
>   -please append a correct root=boot option
>   -kernel panic
>
> This is way over my head. Is there anything I can do, to mount this
> box?
>
> I'd rather try to recover it if possible, as I'm not backed up... (I
> know, I know).
>
> Thanks.
> --
> Stephen
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2004-03-04 Thread sda

[EMAIL PROTECTED] wrote:
Yes. Your simplest option (going from memory here) is to boot off the CD
again, choose the bf24 kernel, skip the majority of the configuration
options, opting instead for mount previous installation, install lilo, and
reboot - then you should be back in bussiness.
NOTE: I'm at uni at the moment, doing this from memory, if anything look
weird, cancel out and let me know, I'll be home in a couple of hours, atwhich point I 
can actually take a look myself at the menu and give you the
exact instructions.
Cheers
Edward
Thanks Edward and everyone else, appreciated the effort very much!

In the meantime, I re-installed. I couldn't do nothing for a day, so had to go 
and do the windoze thing, and re-install. I tried to use the exisiting 
configuration and fake an install, but unfortunately it didn't work.

--
Stephen


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2004-03-05 Thread David Baron

When installing kernel images, the installer first give a lengthy warning 
about initrds. If one continues, it offers to wipe out your old lilo, etc. 
Word to the wize: DON'T.

After installation is done, leaving lilo alone: Edit lilo.conf and add the new 
kernel image and its initrd to the bootup choices. Then, ALWAYS, rerun lilo.

Before doing the installation, make sure the /etc/mkinitrd/mkinitrd.conf 
and .../modules are what you need. My first attemp to run 2.6.* panicked but 
suggested I specify the boot device. The place to do it is in mkinitrd.conf. 
Don't use "probe", specify the device and file system, in quotes. All plays 
fine.

example:
ROOT="/dev/hdb1 ext3"



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2004-03-07 Thread Andreas Janssen

Hello

la2 (<[EMAIL PROTECTED]>) wrote:

>   I compiled kernel 2.4.18, Installed it.
>   When I try to boot, it prints : "kernel panic: VFS: cannot mount
>   root on 03:06".
>   My MBR is on /dev/hda, Debian is on /dev/hda6.
>   BTW before when i compiled the same kernel all had succeded.

You forgot to compile either support for your boot hardware (likely IDE
support) and/or support for your root file system into the kernel. If
you want to compile the drivers as modules, use an initrd and don't
forget to compile support for the initrd into the kernel.

best regards
Andreas Janssen

-- 
Andreas Janssen <[EMAIL PROTECTED]>
PGP-Key-ID: 0xDC801674
Registered Linux User #267976
http://www.andreas-janssen.de/debian-tipps.html

-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel panic

2004-03-08 Thread David Clymer

On Sun, 2004-03-07 at 19:24, la2 wrote:
> Hello debian-user,
> 
>   HELP!
>   I compiled kernel 2.4.18, Installed it.
>   When I try to boot, it prints : "kernel panic: VFS: cannot mount root
>   on 03:06".
>   My MBR is on /dev/hda, Debian is on /dev/hda6.
>   BTW before when i compiled the same kernel all had succeded.

Are you are using a filesystem other than ext2/3 on /dev/hda6? If so,
its possble that you forgot to compile support for that filesystem into
your kernel.

Have you made any hardware or partition changes?

To recover, you should be able to boot the original kernel image by
selecting it at the LILO prompt (you did leave your original kernel in
your LILO config, right?). If not, you can boot using your woody install
CD by selecting a rescue kernel at the boot prompt and passing
root=/dev/hda6 to it.

-davidc

-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

1 2 3 4 5 >

1 - 100 of 462 matches

Mail list logo