On Sat, Sep 20, 2008 at 11:43:12AM -0400, [EMAIL PROTECTED] wrote:
> >And what do dpkg and aptitude think now?
>
> They still showed the file, it wasn't forgotten as the previous reply stated
> it would be. For some reason, it did finally go ahead and get through the
> installation. Not sure w
Rook asked:
>> Hmmm. Dpkg and aptitude still knew that it was installed and in a bad way,
>> but after removing the files (I went further and did 'rm
>> linux-image-2.6.26.*)
> the system did finish the installation. So, many thanks. You saved me a lot
> of headache.
>And what do dpkg and apti
Sven Joachim stated in a not very friendly tone:
>> run-parts: executing /etc/kernel/postrm.d/update-initramfs
>From the existence of this file I conclude that you have initramfs-tools
>0.92k installed, which is known to be broken.
>> Cannot delete /boot/initrd.img-2.6.26, doesn't exist.
>That
On Thu, Sep 18, 2008 at 09:37:50AM -0500, Hugo Vanwoerkom wrote:
>> That's bug #499270. My advice to you: don't run sid if you cannot
>> figure out such things on your own.
>>
>
> That's rather severe. OP asked and you provided info and showed me
> something I did not know in the process.
>
> I
Sven Joachim wrote:
On 2008-09-18 00:52 +0200, [EMAIL PROTECTED] wrote:
run-parts: executing /etc/kernel/postrm.d/update-initramfs
From the existence of this file I conclude that you have initramfs-tools
0.92k installed, which is known to be broken.
Cannot delete /boot/initrd.img-2.6.26,
On 2008-09-18 00:52 +0200, [EMAIL PROTECTED] wrote:
> run-parts: executing /etc/kernel/postrm.d/update-initramfs
>From the existence of this file I conclude that you have initramfs-tools
0.92k installed, which is known to be broken.
> Cannot delete /boot/initrd.img-2.6.26, doesn't exist.
That's
On Wed, Sep 17, 2008 at 10:13:28PM -0400, [EMAIL PROTECTED] wrote:
> >Please try to put margin limits on your messages. They're easier to read
> >that way, and you look less like an Outlook user.
>
> Sorry, using webmail because I'm not on my main computer
>
> >If you're NOT using an initramfs
>Please try to put margin limits on your messages. They're easier to read
>that way, and you look less like an Outlook user.
Sorry, using webmail because I'm not on my main computer
>If you're NOT using an initramfs, rip out initramfs-tools, then try to
>remove the foobarred packag
On Wed, Sep 17, 2008 at 06:52:56PM -0400, [EMAIL PROTECTED] wrote:
> If I could get update-initramfs to not run on the post-removal script, or
> if I could just get the package management system to forget that this
> one package is installed
Please try to put margin limits on your messag
Roberto C. Sanchez said:
>
> The last time I had that problem I had compiled the kernel on a machine
> that ran a different version of GCC from the target machine. Is that
> the case with your setup?
Nope, I compiled the kernel on the machine I'm going to install it on. I'm
running the testing f
On Mon, Aug 08, 2005 at 08:35:25PM -0500, Josh Battles wrote:
> I've been putting off the 2.6 kernel upgrade on my main workstation for a
> while because I wanted to learn the debian method to compilation/installation
> (and because it's been rock solid stable running the 2.4 kernel) so I gave it
>
Cool ! this works.
Thanks one more for help.
Regards,
Eugen.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Thanks for help, but I prefer more classical / general kernel build
process , because at home I use Debian, at work Red Hat , at
school Suse
The point is not to get loosed in distro specific stuff :(
Best wishes ,
Eugen.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTE
--- "M. Maas" <[EMAIL PROTECTED]> ha scritto:
> jenea wrote:
> > Hi!
> >
> >
> > When I type :
> >
> > >$ mkinitrd -k vmlinux-2.6.10 -i initrd-2.6.10
> >
> > I get the same result ( mknitrd help ).
> > Could somebody help me with this stuff ?
> >
> > Best regards,
> > Eugen.
> >
> >
Am Freitag, 6. Mai 2005 07:43 schrieb jenea:
> None of them works on my system ;I have mkinitrd v 1.201 , my
> system's kernel is v 2.4.27-1-386 ; I use debian distro.
>
> When I type ( I try to build 2.6.10 kernel ) :
> > mkinitrd /boot/initrd-2.6.10.img 2.6.10
>
> it gives me mkinitrd help ,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jenea wrote:
> Hi!
>
> I tried to build a new kernel and install it following the steps
> described in
> http://www.digitalhermit.com/linux/Kernel-Build-HOWTO.html
> All goes ok till I get to
>
> " To create the initrd, do the following:
>
>
In message <[EMAIL PROTECTED]>, Adam Funk <[EMAIL PROTECTED]>
writes
On Thursday 06 January 2005 21:20, Joe wrote:
Is it a "defect" that requires the noapic option?
I think so. I don't believe a mere absence of a feature should stop a
kernel booting, particularly a Knoppix one. I think it must be
On Thursday 06 January 2005 21:20, Joe wrote:
>>Is it a "defect" that requires the noapic option?
>>
>>
> I think so. I don't believe a mere absence of a feature should stop a
> kernel booting, particularly a Knoppix one. I think it must be a
> hardware bug.
>
> In fact a quick Google on 'k7s8x n
In message <[EMAIL PROTECTED]>, Adam Funk <[EMAIL PROTECTED]>
writes
On Tuesday 04 January 2005 20:40, Joe wrote:
The motherboard is an ASRock K7S8X. (I don't know what chips are on
it.)
I didn't see the beginning of this. I have one of these and I've yet
to see any Linux boot without noapic. In
On Tuesday 04 January 2005 20:40, Joe wrote:
>>The motherboard is an ASRock K7S8X. (I don't know what chips are on
>>it.)
> I didn't see the beginning of this. I have one of these and I've yet
> to see any Linux boot without noapic. Including Knoppix, and Woody on
> 2.4.18, and the current Sarge
In message <[EMAIL PROTECTED]>, Adam Funk <[EMAIL PROTECTED]>
writes
On Wednesday 29 December 2004 00:10, Roberto Sanchez wrote:
Thanks. I added that to the append="..." in /etc/lilo.conf and it
fixed the problem.
Just out of curiosity, why did this become necessary (for my hardware
at least) bet
On Wednesday 29 December 2004 00:10, Roberto Sanchez wrote:
>> Thanks. I added that to the append="..." in /etc/lilo.conf and it
>> fixed the problem.
>>
>> Just out of curiosity, why did this become necessary (for my hardware
>> at least) between the 2.4.23 and 2.4.26 kernels?
>>
> What motherbo
Adam Funk wrote:
Herbert Xu <[EMAIL PROTECTED]> wrote:
Adam Funk <[EMAIL PROTECTED]> wrote:
I'm running Debian testing on an Athlon 1100 and currently using the
2.4.23-1-386 kernel. I've tried to upgrade to the following packages:
kernel-image-2.4.25-1-386
kernel-image-2.4.26-1-386
kernel-image-2.
Herbert Xu <[EMAIL PROTECTED]> wrote:
> Adam Funk <[EMAIL PROTECTED]> wrote:
> > I'm running Debian testing on an Athlon 1100 and currently using the
> > 2.4.23-1-386 kernel. I've tried to upgrade to the following packages:
> >
> > kernel-image-2.4.25-1-386
> > kernel-image-2.4.26-1-386
> > kerne
Adam Funk <[EMAIL PROTECTED]> wrote:
> I'm running Debian testing on an Athlon 1100 and currently using the
> 2.4.23-1-386 kernel. I've tried to upgrade to the following packages:
>
> kernel-image-2.4.25-1-386
> kernel-image-2.4.26-1-386
> kernel-image-2.4.26-1-k7
>
> and they all get stuck on "
On Friday 14 May 2004 10:41 am, Adam Funk wrote:
> On Friday 14 May 2004 17:10, Roberto Sanchez wrote:
> > What motherboard do you have?
>
> ASRock K7S8X
>
> > Are you loading the module for your
> > IDE chipset?
>
> Here's some info about the kernel that works. AFAIK all the kernels
> I've tried
On Friday 14 May 2004 17:10, Roberto Sanchez wrote:
> What motherboard do you have?
ASRock K7S8X
> Are you loading the module for your
> IDE chipset?
Here's some info about the kernel that works. AFAIK all the kernels
I've tried would use the same modules.conf file, so I can't see why
changi
Adam Funk wrote:
I'm running Debian testing on an Athlon 1100 and currently using the
2.4.23-1-386 kernel. I've tried to upgrade to the following packages:
kernel-image-2.4.25-1-386
kernel-image-2.4.26-1-386
kernel-image-2.4.26-1-k7
and they all get stuck on "hda: lost interrupt" while trying to b
Dear Joost and Manoj,
thanks a lot for your help !
Joost,
unfortunately installing kernel and modules with the same dpkg
command leads to the same error messages and dpkg bailout.
best regards,
nicola
Manoj,
There is a point I really do not understand:
I know for sure I am not downgrading the k
>>"Nicola" == Nicola Botta <[EMAIL PROTECTED]> writes:
That kernel is actually creating the problem. Firstly, your
new kernel has a version tht is lower than the kernel that is
installed: that creates the first error about downgrades.
Then you have pcmcia-modules installed, a
On Thu, Jun 28, 2001 at 03:11:49PM +0200, Nicola Botta wrote:
> at installation, I get
>
> lt28:/usr/src# dpkg -i kernel-image-2.2.18pre21_lt28.2_i386.deb
[..]
> conflicting packages - not installing kernel-image-2.2.18pre21
> Errors were encountered while processing:
> kernel-image-2.2.18pre21
Jim Worthington scripsit:
|1)Boot Message - I get the following message when booting:
|
|
|Oct 8 17:10:10 hercules syslogd 1.3-0#6: restart.
|Oct 8 17:10:11 hercules kernel: Cannot find map file.
|
|What is a map file?
Map of kernel symbols (= functions and external variables)
|Where is it su
32 matches
Mail list logo
