> At 1151942614 past the epoch, Arvind Marathe wrote:
> ...
>> said the 'libc.so.6' does not exist. So i transferred the file from a
> ...
> ^^
>> chroot: error while loading shared libraries: /lib/libc.s0.6: file too
short
>
At 1151942614 past the epoch, Arvind Marathe wrote:
...
> said the 'libc.so.6' does not exist. So i transferred the file from a
...
^^
> chroot: error while loading shared libraries: /lib/libc.s0.6: file too short
^^
I'm gue
rnel panic: Attempted to kill init!
%
I have some data on the hard disks which is not backed up so is there an
easy way out other than reinstalling debian?
this is what i have done so far:
I got the source dvd, put it in the slot
The problem is solved but I am not quite sure why and how I have done.
Seems that cramfs supporting should be configured within the kernel. And
append a --initrd option to make-kpkg.
>
> Is your HD SATA? The problem might be that in /boot/grub/menu.lst (or
> lilo file) you have a line like:
>
>
exist
> pivot_root: No such file or directory
> /sbin/init: 432: cannot open dev/console: No such file
> Kernel panic - not syncing: Attempted to kill init!
>
> The same error is shown when kernel 2.6.13 is used. What should I do? My
> current system is debian-amd64 sarge 3.1
: cannot open dev/console: No such file
Kernel panic - not syncing: Attempted to kill init!
The same error is shown when kernel 2.6.13 is used. What should I do? My
current system is debian-amd64 sarge 3.1.
Thank you for your suggestions and best regards!
Li Weichen
2005-10-24
--
To UNSUBSCRIBE
>> autodetect on the IDE chain (Which it does sucessfully) and then says:
> >> >>
> >> >> invalid operand
> >> >>
> >> >> (Whole string of hex and other associated stuff, see below)
> >> >>
> >> &
gt; However.
>> >>
>> >> Every time I boot into the new kernel, it gets as far as running the
>> >> autodetect on the IDE chain (Which it does sucessfully) and then says:
>> >>
>> >> invalid operand
>> >>
>>
IDE chain (Which it does sucessfully) and then says:
>
> invalid operand
>
> (Whole string of hex and other associated stuff, see below)
>
> Kernel Panic: Attempted to kill init.
>
> I'd quote you the entire message, but it doesn't seem to be logged anywher
> >>
> >> Every time I boot into the new kernel, it gets as far as running the
> >> autodetect on the IDE chain (Which it does sucessfully) and then says:
> >>
> >> invalid operand
> >>
> >> (Whole string of hex and other associ
snip
>
>>
>> However.
>>
>> Every time I boot into the new kernel, it gets as far as running the
>> autodetect on the IDE chain (Which it does sucessfully) and then says:
>>
>> invalid operand
>>
>> (Whole string of hex and other associat
.9 (Actually, I tried this for 2.4.6
snip
>
> However.
>
> Every time I boot into the new kernel, it gets as far as running the
> autodetect on the IDE chain (Which it does sucessfully) and then says:
>
> invalid operand
>
> (Whole string of hex and other associa
e string of hex and other associated stuff, see below)
Kernel Panic: Attempted to kill init.
I'd quote you the entire message, but it doesn't seem to be logged anywhere
(The drives aren't mounted yet, I assume, so it isn't logging, but feel
free to prove me wrong).
Can anyone
(sorry for 1st post without subject!)
Hello,
seem to have a lot of problem for a single Monday morning...
I booted my system this morning, and it gave a
'kernel panic: attempted to kill init' msg.
I used a rescue floppy to 'e2fsck' all the partitions, and now it's c
14 matches
Mail list logo
