-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm getting the same problem with kernel-image-2.6.6-2-k7. The tail end of
the messages before the kernel panics indicate that it can't
load /lib/modules/2.6.6-2-k7/modules.dep
2.6.6-1-k7 works fine, and the modules.dep file for -2-k7 is where
On Fri, Jun 18, 2004 at 11:01:26PM +0200, Jens Schmalzing wrote:
Hi,
Sven Luther writes:
Well, only 2.4.25 packages, which is why we should make a test for non
2.4 kernels or something such. 2.4 kernels don't have the the necessary
mkvmlinuz magic to make it work anyway.
You can
On Mon, 14 Jun 2004 10:03:16 +0200, Francesco P Lovergine
[EMAIL PROTECTED] said:
I think the only serious reason to use svn is its similarity with
cvs by the human interface point of view. So, using it is
straightforward. Arch is quite involuted and underdocumented
AFAIK. But, as always
On Thu, 17 Jun 2004 19:52:56 +0200, Sven Luther [EMAIL PROTECTED] said:
Well, until you count the many not documented subtilities, and the
I use arch daily for my Debian work, and I am not sure what
you are talking about.
fact that the arch people claim that the tutorial is mostly
On Sat, Jun 19, 2004 at 01:19:49AM -0500, Manoj Srivastava wrote:
On Thu, 17 Jun 2004 19:52:56 +0200, Sven Luther [EMAIL PROTECTED] said:
Well, until you count the many not documented subtilities, and the
I use arch daily for my Debian work, and I am not sure what
you are talking
This one time, at band camp, Sven Luther wrote:
But again, feel free to setup the initial arch repository, and give some
easy instructions on how to use it for us non-arch familiar people.
John Goerzen already has an arch mirror of the kernel sources at
http://arch.debian.org/arch/linux .
--
Hi,
Sven Luther writes:
how would mkvmlinuz act if there were no vmlinux installed, but only
a vmlinuz ?
It exits with a non-zero exit status.
Since the postinst comes from kernel-package, you need to sort this
out with Manoj.
Well, that would be a possibility. The other possibility
On Sat, Jun 19, 2004 at 09:41:58AM +0200, Jens Schmalzing wrote:
Hi,
Sven Luther writes:
how would mkvmlinuz act if there were no vmlinux installed, but only
a vmlinuz ?
It exits with a non-zero exit status.
Which would kill dpkg, right ? Not such a good idea.
Friendly,
Sven Luther
I've just got this same thing with the 2.6.6-2-686 kernel packages.
The same message on failing to boot.
The vmlinuz and initrd.img symlinks all look fine:
vmlinuz - boot/vmlinuz-2.6.6-2-686
initrd.img - boot/initrd.img-2.6.6-2-686
I'm using ext3 with a pentium M processor running debian unstable.
On Sat, Jun 19, 2004 at 11:10:46AM +0200, Jens Schmalzing wrote:
Hi,
Sven Luther writes:
how would mkvmlinuz act if there were no vmlinux installed, but
only a vmlinuz ?
It exits with a non-zero exit status.
Which would kill dpkg, right ?
Have you actually tried this?
Hi,
Sven Luther writes:
how would mkvmlinuz act if there were no vmlinux installed, but
only a vmlinuz ?
It exits with a non-zero exit status.
Which would kill dpkg, right ?
Have you actually tried this?
If not, please do so. If it does not work as expected, try again with
the
Hi,
Sven Luther writes:
Please tell me what you gain by not having a depends there ? what
is the benefit in _NOT_ installing it ?
No cruft on the many systems where it is not needed at all.
If you are really going to insist in doing it this way, i would
insist that we create at least a
reassign 254264 kernel-image-2.6.6-1-686
thanks
On Jun 14, Steven Gardner [EMAIL PROTECTED] wrote:
Attached is part of my /var/syslog. Please note the it just keeps repeating
until I remove the card.
udev does what the kernel asks it to do, so I think this is a kernel
bug.
--
ciao, |
Marco
Package: kernel-image-2.6.6-2-686
Version: 2.6.6-2
Severity: normal
** Please type your report below this line ***
Kernel boots to point where it does the calculating module dependencies,
then reports error: Module does not exist in /proc/modules/
This error is repeated for numerous modules
Package: kernel-image-2.4.26-1-686
Version: 2.4.26-2
Priority: normal
I really don't know what caused this (the computer in which this was found
is turned on 24h a day and I didn't see the oops, I just found it
unresponsive at that time). Digging in the logs (today, now that I had
time) I
reassign initrd-tools 255180
thanks
On Jun 19, Henning Glawe [EMAIL PROTECTED] wrote:
after installing module-init-tools 3.1-pre2-1 mkinitrd, which is needed
for the debian-prepackaged kernels, ceases to work. this is cause by the
removal of modprobe.conf generation in
Hi,
Sven Luther writes:
Please tell me exactly in how far you feel that this would be so
much of a hindrance compared to the benefit of having kernel-image
installation work out of the box on non-pmac subarches ?
mkvmlinuz serves the purpose of making some systems bootable given an
Package: kernel-image-2.6.6-2-686
Version: 2.6.6-2
Severity: normal
Followup-For: Bug #255174
it also happens with
kernel-image-2.6.6-2-k7
but not with
kernel-image-2.6.6-1-686
or
kernel-image-2.6.6-1-k7
I tried it on some sid machines.
I will use kernel-image-2.6.6-1-* by now.
-- System
reassign module-init-tools 255180
merge 255180 254950
thanks
Hi,
Marco d'Itri writes:
reassign initrd-tools 255180
thanks
On Jun 19, Henning Glawe [EMAIL PROTECTED] wrote:
after installing module-init-tools 3.1-pre2-1 mkinitrd, which is needed
for the debian-prepackaged kernels,
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.7.95.1
reassign 255180 initrd-tools
Bug#255180: module-init-tools: removal of modprobe.conf breaks mkinitrd
Bug reassigned from package `module-init-tools' to `initrd-tools'.
End of
Processing commands for [EMAIL PROTECTED]:
reassign 255149
kernel-image-2.6.6-i386,kernel-image-2.6.6-2-k7,kernel-image-2.6.6-2-686
Bug#255149: no initrd: panic on boot
Bug reassigned from package `kernel-image-2.6.6-i386' to
Processing commands for [EMAIL PROTECTED]:
reassign 255149 module-init-tools
Bug#255149: no initrd: panic on boot
Bug#255174: kernel-image-2.6.6-2-686: Kernel fails to boot
Bug reassigned from package
`kernel-image-2.6.6-i386,kernel-image-2.6.6-2-k7,kernel-image-2.6.6-2-686' to
Package: kernel-image-2.6.6-2-k7
Version: 2.6.6-2
While installing kernel-image-2.6.6-2-k7 (over kernel-image-2.6.6-1-k7) I
got two error messages from cpio about missing files:
/etc/modprobe.conf
/lib/modules/modprobe.conf
I tired to touch them in order that cpio cound access them and reinstall
On Sat, Jun 19, 2004 at 01:02:39PM +0200, Jens Schmalzing wrote:
Hi,
Sven Luther writes:
Please tell me exactly in how far you feel that this would be so
much of a hindrance compared to the benefit of having kernel-image
installation work out of the box on non-pmac subarches ?
On Sat, Jun 19, 2004 at 01:05:08PM +0200, Jens Schmalzing wrote:
Hi,
Sven Luther writes:
Going to fix this then over working on dpatchified kernel-source-2.6.7
though.
Am I understanding correctly that you are postponing work on
kernel-source-2.6.7 in order to fix CHRP booting first?
On Sat, Jun 19, 2004 at 01:26:13PM +0200, Jens Schmalzing wrote:
Hi,
Sven Luther writes:
Some kind of alternative dependency on yaboot | quik | mkvmlinuz
would take care of fullfilling the dependency, without allowing
cruft to be installed, at least without needing yaboot and quik
* Christoph Hellwig [EMAIL PROTECTED] [2004-06-03 12:43]:
Fine with me. So let's create an alitoh project for the kernel,
and a subversion repo. Anyone is already looking into this ?
Ok, Martin?
I wanted to ask for a debian-kernel project but I see that Sven has
requested a kernel project
* tbm [EMAIL PROTECTED] [2004-06-14 17:05]:
There are some other kernel related packages that have to be taken
care of:
cramfs
initrd-tools
kernel-image-*-alpha
kernel-image-*-i386
kernel-kbuild-*
kernel-source-*
modules-scyld-source-0.1
Jeff Bailey was interested in helping with
Processing commands for [EMAIL PROTECTED]:
severity 255180 grave
Bug#255180: module-init-tools: removal of modprobe.conf breaks mkinitrd
Severity set to `grave'.
reassign 255180 module-init-tools
Bug#255180: module-init-tools: removal of modprobe.conf breaks mkinitrd
Bug reassigned from
Hi,
Sven Luther writes:
i don't see how you are caring for anything
[...]
No, no, no, you don't understand.
[...]
you seem to make a fanatical issue out of it,
[...]
i haven't heard yet one single valable reason
That about ends the discussion for me. Stop whining, implement a
solution
Hi,
Sven Luther writes:
it doesn't make much sense for me to have a non-working 2.6.7
package over a non-working 2.6.6 one.
Well.
Is the work you have done on kernel-source-2.6.7 available in some
repository? If not, can you please send it to me?
Regards, Jens.
--
J'qbpbe, le m'en fquz
tags 255199 patch
thanks
Hi,
Lior Kaplan writes:
While installing kernel-image-2.6.6-2-k7 (over kernel-image-2.6.6-1-k7) I
got two error messages from cpio about missing files:
/etc/modprobe.conf
/lib/modules/modprobe.conf
The ramdisk works nonetheless, provided the modprobe bug is fixed.
On Sat, Jun 19, 2004 at 08:30:59PM +0200, Francesco Paolo Lovergine wrote:
On Sat, Jun 19, 2004 at 03:13:44PM +0100, Martin Michlmayr wrote:
* tbm [EMAIL PROTECTED] [2004-06-14 17:05]:
There are some other kernel related packages that have to be taken
care of:
cramfs
On Sat, Jun 19, 2004 at 08:30:59PM +0200, Francesco Paolo Lovergine wrote:
On Sat, Jun 19, 2004 at 03:13:44PM +0100, Martin Michlmayr wrote:
* tbm [EMAIL PROTECTED] [2004-06-14 17:05]:
There are some other kernel related packages that have to be taken
care of:
cramfs
This is fixed in 2.6.7-final and various other fixes from the Debian
sources are also included there.
I'm preparing a 2.6.7-final -based package to address this.
-- wli
35 matches
Mail list logo
