Mykl said:
> Hi,
>
> I have a Compaq Proliant ML 330 with an 18 GB SCSI hard-drive and another
> hot-plug able SCSI HDD of the same capacity.
> I want to install Debian Potato on this machine as in I would like to use
> it as a DNS, Mail, Proxy Server.
> During boot up they system this error
>
any
Have you compiled the support of ext2 or ext3 or reiserfs in hard, not in module
(depend on your /boot partition) ?
++
On Wed, 04 Sep 2002 03:55:06 +1000
Russell <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Why do i get:
>
> RAMDISK: cramfs filesystem found at block 0
> RAMDISK: Loading 892 blocks
On Wed, 4 Sep 2002, Russell wrote:
> Hi,
>
> Why do i get:
>
> RAMDISK: cramfs filesystem found at block 0
> RAMDISK: Loading 892 blocks [1 disk] into ram disk... done.
> Freeing initrd memory: 892k freed
> request_module[nls_437]: Root fs not mounted
> Unable to load NLS charset 437
> Kernel pan
VETSEL Patrice wrote:
>
> Have you compiled the support of ext2 or ext3 or reiserfs in hard, not in module
>(depend on your /boot partition) ?
Hi, i got ext2 selected in non-module form. How
does that cause the problem? I'm recompiling as we speak;)
--
To UNSUBSCRIBE, email to [EMAIL PROTEC
VETSEL Patrice wrote:
>
> Have you compiled the support of ext2 or ext3 or reiserfs in hard,
not in module (depend on your /boot partition) ?
Compiling with ext2 as internal or module didn't help. However,
i found the problem. If generating a kernel that will use an initrd,
this uses the CramFs
On Thu, Sep 26, 2002 at 03:06:11PM +0530, J.S.Sahambi wrote:
> I patched some files and then made the kernel "2.4.19-patched" with the
> following commands:
>
> fakeroot make-kpkg --append-to-version -patched kernel_image
>
>
> and then installed the kernel with :
> dpkg -i kernel-image-2.4.19
On Fri, Sep 27, 2002 at 08:15:47AM +0530, J.S.Sahambi wrote:
> One thing more. Following is the dir list of /boot:
>
> *
> jsahambi@ws97:/boot$ ll
> total 6788
> -rw-r--r--1 root root 547232 Jul 10 14:55
> System.map-2.4.18-bf2.4
> -rw-r--r--1 root root 42
On Wed, Mar 27, 2002 at 10:36:54AM -0800, Paul Mackinney wrote:
> I thought rebuilding my kernel would be routine, but I can't get it to
> boot. Here's what I'm doing:
>
[ big snip ]
>
> But after 5+ tries I still can't boot from this thing. The error is
>
> cramfs: bad magic
> Kernel Panic
"Paul" == Paul Mackinney <[EMAIL PROTECTED]> writes:
Paul> cramfs: bad magic Kernel Panic: VFS: Unable to mount root
Paul> fs on 03:08
Paul> which seems very much like an initrd kind of error. So
Paul> what's going on? In order that my trivial and humiliating
Paul> erro
On Thu, 2002-03-28 at 02:36, Paul Mackinney wrote:
> I thought rebuilding my kernel would be routine, but I can't get it to
> boot. Here's what I'm doing:
>
> 1. Installed kernel-image-2.4.18-686.
> 2. Copied to the config, modified it take out all the stuff not on my
> system and the stuff I'll n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wilson,
> When my machine boots up, Linux is auto-probing the hardware, then it
> stops and pops up an error message "Kernel Panic..VFS"
>
> I tried to use a 'rescue' disk and did the e2fsck, but it said the '/'
> partition was clean.
> I
Mark,
Yes, thank you for reminding me the missing bits (The machine with broken O/S is
not with me at the moment, I'm sorry that I have not jotted them down properly).
Now, presuming what you said is right and once I've checked out the number,x
in the error message "VFS: Unable to mount root fs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wilson,
> Yes, thank you for reminding me the missing bits (The machine with broken O/S
> is
> not with me at the moment, I'm sorry that I have not jotted them down
> properly).
> Now, presuming what you said is right and once I've checked out the
Hi, Mark!
Problems solved, thanks!
I found what happened to lead to the problem was - I changed the hard disk from
secondary master to primary master, lilo was looking for '/' in /dev/hdc5,
rather
/dev/hda5. From your tips, I first tried to put 'rescue root=/dev/hda5' at the
boot
prompt when t
On Thu, Sep 14, 2000 at 02:00:13PM +0200, Julio Merino wrote:
> Hi all,
>
> Some days ago I was playing with noflushd/apmd and such things, and I
> got a kernel panic. I rebooted. Debian was completly a mess,
> complaining about libncurses5 was failing. I need to remove /bin/sh
> and link it to as
On Thu, Sep 14, 2000 at 04:28:07AM -0800, Ethan Benson wrote:
> you have experienced fairly severe filesystem corruption, cleaning up
> after such things is generally a nightmare. did you run fsck i
> presume? (fsck a four letter word for a reason...)
Yes; fsck was run, and after a lot of time
On Thu, Sep 14, 2000 at 03:55:18PM +0200, Julio Merino wrote:
> On Thu, Sep 14, 2000 at 04:28:07AM -0800, Ethan Benson wrote:
>
> > you have experienced fairly severe filesystem corruption, cleaning up
> > after such things is generally a nightmare. did you run fsck i
> > presume? (fsck a four l
would be helpful if you specified what kind of MB you have with what
kind of controller, and what brand/type of HD, on the linux-kernel
mailing list the IDE guy has cursed Western Digital drives for not
behaving in a sane manner when doing DMA transfers. and for causing
major problems when WD drive
On Sun, Sep 17, 2000 at 11:04:59AM -0700, Nate Amsden wrote:
> would be helpful if you specified what kind of MB you have with what
> kind of controller, and what brand/type of HD, on the linux-kernel
> mailing list the IDE guy has cursed Western Digital drives for not
> behaving in a sane manner
On 22/10/99 Jocke wrote:
I have 2 debian partitions the one that works are on hda2 and the one
that messed up is on hda5.
I have some old vmlinuz + System.map in /boot
Could anyone guide me thru this so I can get my hda5 debian to boot again ?
Can I fix it from "this" (hda2) partition or do I h
At 01:54 AM 10/22/99 +0200, Jocke wrote:
>Hi all,
>
>I did something stupid today :(
>While recompiling my kernel to add scsi support for my cdrw I accidently
>forgot some ide stuff and now I can't boot.
If you want to change something important like a...*hmmm*
a kernel or something ALWAYS make li
On Tue, May 07, 2002 at 04:16:43PM -0600, Troy Telford wrote:
| I'm having some problems with my computer, which I believe are
| hardware-related. The main indicator is either a kernel panic, or a
| BSOD (Win32).
Try memtest86 to see if your memory is ok.
# apt-get install memtest86
# http://d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 07 May 2002 03:16 pm, Troy Telford wrote:
> Linux reports it as a problem with kernel paging (sometimes deferencing a
> null pointer, h)
>
Greetings Troy:
That sure smells like a memory issue. Though the rest of the message le
On Tue, May 07, 2002 at 04:18:26PM -0600, Troy Telford wrote:
> I'm having some problems with my computer, which I believe are
> hardware-related. The main indicator is either a kernel panic, or a
> BSOD (Win32).
>
> My computer was working fine until I moved home (from college). It
> even worke
Alex Goldman wrote:
My self-compiled kernel refuses to boot, saying it can't
mount/init/access /dev/hda7 (root partition)
I compiled 2.6.14.2 following the instructions in
/usr/share/doc/kernel-package/README.gz, basically
cp /boot/config-2.6.8-2-386 linux-2.6.14.2/.config
make menuconfig (few
On Sun, Nov 20, 2005 at 02:09:23PM -0800, Alex Goldman wrote:
> My self-compiled kernel refuses to boot, saying it can't
> mount/init/access /dev/hda7 (root partition)
>
> I compiled 2.6.14.2 following the instructions in
> /usr/share/doc/kernel-package/README.gz, basically
>
> cp /boot/config-2.
On 11/20/05, Daniel Nilsson <[EMAIL PROTECTED]> wrote:
> On Sun, Nov 20, 2005 at 02:09:23PM -0800, Alex Goldman wrote:
> > My self-compiled kernel refuses to boot, saying it can't
> > mount/init/access /dev/hda7 (root partition)
> >
> > I compiled 2.6.14.2 following the instructions in
> > /usr/sha
On Mon, Nov 21, 2005 at 12:15:11AM -0800, Alex Goldman wrote:
> On 11/20/05, Daniel Nilsson <[EMAIL PROTECTED]> wrote:
> > The problem is that you are using the Debian kernel config without
> > builing an initrd, for that you need to supply --initrd as well as an
> > option to make-kpkg
>
>
> But
On 16/07/10 05:59 AM, Sunita Barve wrote:
> I have been using debian 5.0.3. I had changed disk and had connected on two
> different machines. Now I am getting the following error
I am in a similar situation.
> kinit: trying to resume from /dev/sda5
> kinit:No resume image, doing normal boot...
>
On 10-07-16 10:56 AM, H.S. wrote:
On 16/07/10 05:59 AM, Sunita Barve wrote:
I have been using debian 5.0.3. I had changed disk and had connected on two
different machines. Now I am getting the following error
I am in a similar situation.
kinit: trying to resume from /dev/sda5
kinit:No resume
On Fri, Jul 16, 2010 at 20:54, H.S. wrote:
> On 10-07-16 10:56 AM, H.S. wrote:
>
>> On 16/07/10 05:59 AM, Sunita Barve wrote:
>>
>>> I have been using debian 5.0.3. I had changed disk and had connected on
>>> two
>>> different machines. Now I am getting the following error
>>>
>>
>> I am in a sim
On Sb, 17 iul 10, 09:06:02, Anand Sivaram wrote:
> >
> It is necessary to use initrd image while using UUID. So UUID method may
> not work with custom kernels where drivers are compiled in.
Could you please elaborate on that? How can UUID fail if you have
modules compiled in the kernel, since U
On Sat, Jul 17, 2010 at 12:23, Andrei Popescu wrote:
> On Sb, 17 iul 10, 09:06:02, Anand Sivaram wrote:
> > >
> > It is necessary to use initrd image while using UUID. So UUID method may
> > not work with custom kernels where drivers are compiled in.
>
> Could you please elaborate on that? How ca
On Sb, 17 iul 10, 23:10:39, Anand Sivaram wrote:
> >
> > Could you please elaborate on that? How can UUID fail if you have
> > modules compiled in the kernel, since UUID is a property of the
> > filesystem?
>
> Even if every driver is compiled into the kernel, an initrd may be required
> to
> use
On Sun, Jul 18, 2010 at 13:39, Andrei Popescu wrote:
> On Sb, 17 iul 10, 23:10:39, Anand Sivaram wrote:
> > >
> > > Could you please elaborate on that? How can UUID fail if you have
> > > modules compiled in the kernel, since UUID is a property of the
> > > filesystem?
> >
> > Even if every driver
If you are trying to boot from the hard disk root using the rescue floppy,
try this command line:
boot: linux load_ramdisk=0 root=/dev/hd??
Replace the "??" with the appropriate details for your system, like "b2".
Bruce
--
Bruce Perens K6BP [EMAIL PROTECTED] 510-215-3502
Fin
On Tue, Oct 21, 2003 at 07:27:29AM +0100, Anim Asante wrote:
> I have got a grub menu.lst file with a section of the
> file looking like this
> root (hd1,0)
> kernel /vmlinuz root=/dev/hdb1
> boot
>
> When I restart my machine and select this option, the
> boot up process begins up
> to a poin
> -Original Message-
> From: Bill Marcum [mailto:[EMAIL PROTECTED]
> Sent: 22 October 2003 07:01
> To: [EMAIL PROTECTED]
> Subject: Re: Kernel panic error
>
>
> On Tue, Oct 21, 2003 at 07:27:29AM +0100, Anim
> Asante wrote:
> > I have got a gru
--- Anim Asante <[EMAIL PROTECTED]> wrote: > >
-Original Message-
> > From: Bill Marcum [mailto:[EMAIL PROTECTED]
> > Sent: 22 October 2003 07:01
> > To: [EMAIL PROTECTED]
> > Subject: Re: Kernel panic error
> >
> >
> > On T
On Wed, Oct 22, 2003 at 11:10:02AM +0100, Anim Asante wrote:
> > > I have got a grub menu.lst file with a section of
> > the
> > > file looking like this
> > > ?root (hd1,0)
> > > ?kernel /vmlinuz root=/dev/hdb1
> > > ?boot
> > > ?
> > > When I restart my machine and select this option,
>
will shed more light on the problem.
Regards,
Anim
> Subject: FW: FW: Kernel panic error
>
>
>
>
> > > From: Jerome R. Acks
> > > [mailto:[EMAIL PROTECTED]
> > > Sent: 24 October 2003 03:47
> > > To: Anim Asante
> > >
Hi
On Wed, Nov 06, 2013 at 12:39:42PM +0200, Vladimir Zagaychuk wrote:
> Good day!
>
> I am getting kernel panic with the kernel version 2.6.32 - call trace is
> available here:
> http://i.imgur.com/kHfhRy9.jpg
>
> Is there any ideas how to deal with this?
> Thank you!
Not really - to make sens
Hi Steve, it looks like you might have misconfigured the kernel. did you
include ext2 filesystem in your configured kernel.
Paul
On Sat, 29 Jan 2000, steve doerr wrote:
> I just compiled and installed the 2.2 kernel with the debian kernel
> package and I got the following error on booting:
>
>
Paul McDermott wrote:
>
> Hi Steve, it looks like you might have misconfigured the kernel. did you
> include ext2 filesystem in your configured kernel.
and, steve, the ext2 should no be compiled as module :)
--
hafi
On Mon, Mar 03, 2008 at 07:50:15PM -0300, Juan Seet wrote:
> Hello, I downloaded netinst for AMD64, I tried to install it and I get
> the following message:
> Code: 89 d5 81 e5 ff 00 00 00 75 70 48 c1 ea 08 48 8d b3 18 10 00
> console shuts up ...
> <0>Kernel panic - not syncing: Aiee, killing inte
2008/3/3, Douglas A. Tutty <[EMAIL PROTECTED]>:
> On Mon, Mar 03, 2008 at 07:50:15PM -0300, Juan Seet wrote:
> > Hello, I downloaded netinst for AMD64, I tried to install it and I get
> > the following message:
> > Code: 89 d5 81 e5 ff 00 00 00 75 70 48 c1 ea 08 48 8d b3 18 10 00
> > console sh
2008/3/3, Juan Seet <[EMAIL PROTECTED]>:
> 2008/3/3, Douglas A. Tutty <[EMAIL PROTECTED]>:
>
> > On Mon, Mar 03, 2008 at 07:50:15PM -0300, Juan Seet wrote:
> > > Hello, I downloaded netinst for AMD64, I tried to install it and I get
> > > the following message:
> > > Code: 89 d5 81 e5 ff 00 0
Douglas A. Tutty wrote:
>> Any idea? Thanks for your time.
>
> You don't say if this is Sarge, Etch, Lenny, or Sid. Its important.
>
He did (look in the subject line) say that it was on Etch.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [
Juan Seet wrote:
> I can't find the debian-boot list, maybe you meant
> http://lists.debian.org/debian-amd64/ ?
http://lists.debian.org/debian-boot/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Monday 03 March 2008 23:50, Juan Seet wrote:
> Hello, I downloaded netinst for AMD64, I tried to install it and I get
> the following message:
> Code: 89 d5 81 e5 ff 00 00 00 75 70 48 c1 ea 08 48 8d b3 18 10 00
> console shuts up ...
> <0>Kernel panic - not syncing: Aiee, killing interrupt handl
Le Monday 03 March 2008 23:01:23 Douglas A. Tutty,
vous avez écrit :
> On Mon, Mar 03, 2008 at 07:50:15PM -0300, Juan Seet
wrote:
> > Hello, I downloaded netinst for AMD64, I tried to
install it and I get
> > the following message:
> > Code: 89 d5 81 e5 ff 00 00 00 75 70 48 c1 ea 08 48
8d b3 18 10
On Mon May 12 2008 01:14:04 Bill wrote:
> run-init: making initramfs contents: Directory not empty
> kernel-panic: not syncing : attempted to kill init!
>
> Can anyone be of help diagnosing this problem. Any pointers
> links or suggestions as to the cause much appreciated.
First thing I'd check is
On Mon, May 12, 2008 at 01:14:04AM -0700, Bill wrote:
> Hi folks,
> Begin: Running /scripts/init-bottom
> mount: mounting /dev on /root/dev failed: Invalid argument
> Done.
> run-init: making initramfs contents: Directory not empty
> kernel-panic: not syncing : attempted to kill init!
I would foc
Bill wrote:
Hi folks,
I have to compile a vanilla kernel 2.6.25 to access a new wireless
module and keep things as small as possible on this old laptop.
So far so good. Everything compiles and all but I can't reboot
with the new kernel. Everything is fine using the 2.6.18.6 stock
kernel but the
On Mon, May 12, 2008 at 09:49:17AM -0700, Andrew Sackville-West wrote:
> On Mon, May 12, 2008 at 01:14:04AM -0700, Bill wrote:
> > Hi folks,
>
> > Begin: Running /scripts/init-bottom
> > mount: mounting /dev on /root/dev failed: Invalid argument
> > Done.
> > run-init: making initramfs contents: D
On Mon, 2008-12-05 at 09:01 -0500, Hugo Vanwoerkom wrote:
> Sid, Etch, Lenny?
> 2.6.25 is out in Sid.
Etch. Production.
b.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, May 13, 2008 at 07:57:30AM +1000, Alex Samad wrote:
> On Mon, May 12, 2008 at 09:49:17AM -0700, Andrew Sackville-West wrote:
> > On Mon, May 12, 2008 at 01:14:04AM -0700, Bill wrote:
> > > Hi folks,
> >
> > > Begin: Running /scripts/init-bottom
> > > mount: mounting /dev on /root/dev faile
On Sunday 26 March 2006 14:24, oscar wrote:
> I am trying to install Debian in a new Dell M70. I first used a CD with the
> from root=/dev/hda1 to root=/dev/sda1. No result. Still kernel panic.
> Moreover, I try testing distribution to see what happens. Now not only with
> kernel 2.6 but even wit
On Sun, Mar 26, 2006 at 02:44:23PM -0700, Glenn English wrote:
> The installer sets up disk names and labels one way, then the boot process
> names them so they don't match. SATAs are hd's at one point, sd's at another.
> And something moves them ahead of real SCSIs in /dev.
>
> Things seem to w
On Sunday 26 March 2006 16:19, Winston Smith wrote:
> Could you post a link to the bug report you're referring to.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=358510
That they already know about it: first one on
http://www.debian.org/devel/debian-installer/errata
--
Glenn English
[EMAIL
On Sun, Mar 26, 2006 at 11:24:50PM +0200, oscar wrote:
> I am trying to install Debian in a new Dell M70. I first used a CD with the
> testing installer, but although it was able to boot from the CD, later it did
> not recognize the CD. I have read in other places that it have to do with
> SATA
> VFS: Cannot open root device 08:01
> Kernel panic: VFS: unable to mount root FS on 08:01
Hi Erik, this looks like you have not anabled one or two importand things in
your configuration. Look if you selected Networking option --> Unix domain
sockets and Character devices --> Unix98 PTY suppor
On Sat, Mar 31, 2001 at 10:52:40 +0200, Erik van der Meulen wrote:
> When I reboot my new kernel (either from flop or directly) I end with:
>
> VFS: Cannot open root device 08:01
> Kernel panic: VFS: unable to mount root FS on 08:01
Thanks for all suggestions. It turned out to be a missing
To check for possible memory problems, memtest has
been run for about 5 days for a total of about 19
runs, all of which said no errors.
__
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
--
To UNSUBSCRIBE, e
michael bailey wrote:
[..]
kernel: CPU 0 : Machine Check Exception:
0004
kernel: Bank 4 : b2040151
kernel: Kernel panic: CPU context corrupt
After the reboot both the green power
light and the orange disk light on the front of the PC
are steady (i.e. not flickering).
On Fri, 2005-10-14 at 10:47 -0400, Edward J. Shornock wrote:
> michael bailey wrote:
>
> [..]
> >
> > kernel: CPU 0 : Machine Check Exception:
> > 0004
> >
> > kernel: Bank 4 : b2040151
> >
> > kernel: Kernel panic: CPU context corrupt
> >
> > After the reboot both the gre
Please, does anybody have any idea regarding this problem?
Thank you.
Mike Schleif wrote:
amd64 server will not complete boot, regardless which kernel from grub
menu
google hit on memory; but, that does not appear to be the case, after
swapping memory
last 20+ lines of boot messages:
...
On Fri, Oct 10, 2008 at 11:06 PM, Mike Schleif <[EMAIL PROTECTED]> wrote:
> Please, does anybody have any idea regarding this problem?
>
>> last 20+ lines of boot messages:
>> ...
>> Begin: Running /scripts/init-bottom ...
>> Done.
>> run-init: /sbin/init: Permission denied
You could probe to boot
On Fri, 21 Mar 1997 08:40:01 EST Brian K Servis ([EMAIL PROTECTED]
) wrote:
> I was running the checksecurity program by hand after adding the types
> vfat and supermount(not really needed) to the list of types to skip in the
> checksecurity.conf file and I got a kernel-panic.
You probably have
Philippe Troin writes:
>
>
>On Fri, 21 Mar 1997 08:40:01 EST Brian K Servis ([EMAIL PROTECTED]
>) wrote:
>
>> I was running the checksecurity program by hand after adding the types
>> vfat and supermount(not really needed) to the list of types to skip in the
>> checksecurity.conf file and I got a
On Fri, 21 Mar 1997 13:52:51 EST Brian K Servis ([EMAIL PROTECTED]
) wrote:
> If anyone wants to be a saint and send me copies of any of the
> following I would appreciate it. I don't want to download the whole
> packages over my modem just for a few files.
>
> /var/lib/dpkg/info/fvwm2.conffile
Mini Trader wrote:
> task_numa_fault+0x6ed/0xd20
what happens if you boot the vm with numa=off
Looks to be the same.
On Mon, Jul 3, 2017 at 5:48 PM, deloptes wrote:
> Mini Trader wrote:
>
> > task_numa_fault+0x6ed/0xd20
>
> what happens if you boot the vm with numa=off
>
>
>
>
More information. I found a post here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650635
They mention LRO so I disabled it. I cannot reproduce if LRO is disabled.
On Mon, Jul 3, 2017 at 5:59 PM, Mini Trader
wrote:
> Looks to be the same.
>
> On Mon, Jul 3, 2017 at 5:48 PM, delopte
Mini Trader wrote:
> More information. I found a post here:
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650635
>
> They mention LRO so I disabled it. I cannot reproduce if LRO is disabled.
>
> On Mon, Jul 3, 2017 at 5:59 PM, Mini Trader
> wrote:
>
>> Looks to be the same.
>>
>
I am on stretch Debian 4.9.30-2+deb9u2. Is there a link to submit this
bug too?
On Ubuntu's 4.4.0-83-generic this is not reproducible.
On Mon, Jul 3, 2017 at 6:45 PM, deloptes wrote:
> Mini Trader wrote:
>
> > More information. I found a post here:
> >
> > https://bugs.launchpad.net/ubuntu/
Mini Trader wrote:
> I am on stretch Debian 4.9.30-2+deb9u2. Is there a link to submit this
> bug too?
>
> On Ubuntu's 4.4.0-83-generic this is not reproducible.
usually reportbug is used to do this, however IMO you are hitting some
other bug, but this is just a guess
regards
> "Bob" == Bob Nielsen <[EMAIL PROTECTED]> writes:
Bob> --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii
Bob> I just compiled a new 2.2.14 kernel after doing a new potato
Bob> install and got the message:
Bob> Kernel panic: No init found. Try passing init= optio
Nope, it is an Intel CPU.
On Sat, Apr 01, 2000 at 09:58:58PM -0800, Bill Alexander wrote:
> > "Bob" == Bob Nielsen <[EMAIL PROTECTED]> writes:
>
> Bob> --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii
>
> Bob> I just compiled a new 2.2.14 kernel after doing a new potato
One thing to check: Make sure that you have ext2 support compiled in the
kernel, and not as a module.
Paul
On 02-Apr-2000 Bob Nielsen wrote:
> I just compiled a new 2.2.14 kernel after doing a new potato install and got
> the message:
>
> Kernel panic: No init found. Try passing init= option t
-BEGIN PGP SIGNED MESSAGE-
Dear Debians:
I have had the same problem as Bob N. and ext2 is IN the kernel, not a module
and I have a Pentium III. Is there some bug either in kpkg or latest kernel
version of 2.2.14?
"Dpkg -i the kernel-image" doesn't run through its usual routine. It ju
On Sun, Apr 02, 2000 at 09:15:34PM -0500, eric k. wolven wrote:
> I have had the same problem as Bob N. and ext2 is IN the kernel, not
> a module and I have a Pentium III. Is there some bug either in kpkg
> or latest kernel version of 2.2.14?
For what it's worth, I'm running 2.2.14 on two of my m
On Sun, Apr 02, 2000 at 09:30:07PM -0400, Mike Werner wrote:
> On Sun, Apr 02, 2000 at 09:15:34PM -0500, eric k. wolven wrote:
> > I have had the same problem as Bob N. and ext2 is IN the kernel, not
> > a module and I have a Pentium III. Is there some bug either in kpkg
> > or latest kernel vers
** On Apr 02, Bob Nielsen scribbled:
> I just compiled a new 2.2.14 kernel after doing a new potato install and got
> the message:
>
> Kernel panic: No init found. Try passing init= option to kernel.
You compiled the kernel with wrong root partition, it happens sometimes. The
best bet is to use
Daniel D Jones wrote:
My Etch server boots fine with the default 2.6.18 kernel. I downloaded the
2.6.25 kernel and did:
make all
make modules_install
make install
depmod 2.6.21.3
mkinitrd.yaird -o /boot/initrd.img-2.6.25 2.6.25
Updated grub and rebooted. I'm getting a kernel panic:
/usr/li
On Tue, 2002-06-18 at 18:54, curtis wrote:
> Now, on my personal computer after updating to 2.4.xx, I made the same
> changes, but I notices that during the boot there is a line entry:
> VFS: Mounted root (ext2 filesystem)
Look closer. There should be at least two VFS lines. For example, from a
Anthony DeRobertis wrote:
On Tue, 2002-06-18 at 18:54, curtis wrote:
Now, on my personal computer after updating to 2.4.xx, I made the same
changes, but I notices that during the boot there is a line entry:
VFS: Mounted root (ext2 filesystem)
Look closer. There should be at least two
on Sat, Nov 17, 2001 at 01:46:15AM -0600, Rory O'Connor ([EMAIL PROTECTED])
wrote:
> welp, i'm not sure if linux will ever boot from my hard disk again!
> before I was having a problem with LILO hanging at "LI", and i deemed
> it a problem with my SCSI drive. I unplugged the SCSI drive,
> reboote
replace the scsi disk, boot from the floppy, check dmesg to see what
hardware or anything else is or isn't there, and configure a new kernel
based on what you find.
Rory O'Connor wrote:
>
> welp, i'm not sure if linux will ever boot from my hard disk again! before
> I was having a problem wit
Rory O'Connor wrote:
welp, i'm not sure if linux will ever boot from my hard disk again! before
I was having a problem with LILO hanging at "LI", and i deemed it a problem
with my SCSI drive. I unplugged the SCSI drive, rebooted, and the MBR was
found and the boot process began...only to end i
On Wed, 14 Jan 2009 20:59:29 +
"Vladimir Komendantsky" wrote:
> Hi,
>
> I'm sorry to tell you that today's package update cost me a system crash.
> The problem was with the package netatalk which was starting services at
> boot time. This resulted in a kernel panic. To repair this I booted t
On Fri, Jan 16, 2009 at 08:54:32PM -0800, Amit Uttamchandani wrote:
> On Wed, 14 Jan 2009 20:59:29 +
> "Vladimir Komendantsky" wrote:
>
> > Hi,
> >
> > I'm sorry to tell you that today's package update cost me a system crash.
> > The problem was with the package netatalk which was starting s
Hi,
I'm using kernel 2.2.14 and I have a problem with ipmasqadm portfw.
When I try to add a rule for forwarding a port I get the following error :
ipmasqadm portfw -a -P tcp -L 212.69.202.112 8002 -R 192.168.1.10 8002
portfw: setsockopt failed: Invalid argument
when I try to get get a list I g
On Wed, Feb 06, 2002 at 02:24:35AM -0600, Gary Turner wrote:
> I just upgraded the kernel to 2.4.17 in a deb package. The install
> apparently went ok. On reboot I got the following:
>
> >request_module[block-major-31]: Root fs not mounted
> >VFS: Cannot open root device "303" or 03:03
> >please
On Wed, Feb 06, 2002 at 02:24:35AM -0600, Gary Turner wrote:
| I just upgraded the kernel to 2.4.17 in a deb package. The install
| apparently went ok. On reboot I got the following:
|
| >request_module[block-major-31]: Root fs not mounted
| >VFS: Cannot open root device "303" or 03:03
| >please
On Wed, 06 Feb 2002 12:15:14 -0500, dman wrote:
>On Wed, Feb 06, 2002 at 02:24:35AM -0600, Gary Turner wrote:
>| I just upgraded the kernel to 2.4.17 in a deb package. The install
>| apparently went ok. On reboot I got the following:
>|
>| >request_module[block-major-31]: Root fs not mounted
>|
On Wed, 06 Feb 2002 02:24:35 -0600, Gary Turner wrote:
>I just upgraded the kernel to 2.4.17 in a deb package. The install
>apparently went ok. On reboot I got the following:
>
>>request_module[block-major-31]: Root fs not mounted
>>VFS: Cannot open root device "303" or 03:03
>>please append a c
On Thu, 07 Feb 2002 14:47:14 -0500, Thomas R. Shemanske wrote:
>I think your initrd line is misplaced. Since some kernels do not need
>the line, you probably want it with each lilo entry
>
>For example from http://rute.sourceforge.net/node34.html, we see a lilo
>entry of the form:
>
>
>boot=/de
On 21 May 1998, Paul Mackinney wrote:
: Booting for the first time from recovery disk, I get the following
: error just after it resets the SCSI bus:
:
: aic7xxx: (aic7xxx_isr) Encountered spurious interrupt.
: scsi0: BRKADRINT error(0x1):
: Illegal Host Access
: Kernel panic: scsi0: BRKADRINT
Nathan E Norman wrote:
> On 21 May 1998, Paul Mackinney wrote:
>
> : Booting for the first time from recovery disk, I get the following
> : error just after it resets the SCSI bus:
> :
> : aic7xxx: (aic7xxx_isr) Encountered spurious interrupt.
> : scsi0: BRKADRINT error(0x1):
> : Illegal Hos
101 - 200 of 462 matches
Mail list logo
