You closed the wrong bug.
On Feb 23, 2007, at 4:33 PM, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
#304507: kernel-source-2.6.11: please apply the evms bd-claim patch
to debian kernel sources,
which was filed against the linux-2.6 package.
I
Package: initramfs-tools
Version: 0.51
Severity: minor
Incorrect English usage...
was been altered. Cannot update.
Should be
has been altered. Cannot update.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (650, 'testing'), (600, 'unstable'), (1
Package: initramfs-tools
Version: 0.41
Severity: minor
Here's what I'm getting in my generated initramfs conf.modules, this is
not good:
ext3
ide_disk
sd_mod
ata_piix
piix
generic
ide_generic
acpid evms evms_bootdebug kernelextras lvm md udev
unix
The bad line in question is the acpid one
Package: initramfs-tools
Version: 0.39
Severity: normal
per our discussion via e-mail, please remove all support for evms from
initramfs-tools, I'm working with the evms maintainer to release a new
version of evms which will install the required scripts and hooks, per
your request.
The current fi
Package: initramfs-tools
Version: 0.38
Followup-For: Bug #339568
--- mkinitramfs 2005-10-24 01:05:05.0 -0700
+++ mkinitramfs 2005-11-20 09:49:08.881214220 -0800
@@ -167,13 +167,16 @@
cp -p "/etc/mkinitramfs/scripts/${f}" "${DESTDIR}/scripts/$(dirname "${f}")"
done
cp "${CONFDIR}/initra
Package: initramfs-tools
Version: 0.38
Severity: important
Tags: patch
udev 0.74 moved some files around, initramfs-tools needs to adapt to the
new version. (also, udev should have marked itself incompatible with
current versions of initramfs-tools until you apply my changes, but that
is their bu
hurrah for opening an separate bug.
Sesse is using plain EVMS root, you seem to use an heavier mix.
Yes, as I mentioned, I use just about every little bit of EVMS on the
way up. My root is a LVM2 volume inside a LVM2 container inside a RAID5
md array, all controlled by evms.
your patch als
Package: initramfs-tools
Version: 0.38
Severity: important
Tags: patch
336617 was closed out without using the additional patches I submitted.
I'm having problems re-opening the bug, so I'm just submitting a new one.
The following two patches need to be applied to evms 0.38 in order to allow
boot
Thats what I initially thought as well, all I can say is that it the
error messages related to it have gone away for me. Of course, the
errors I could be seeing could also have been due to the second run once
the real root was up.
Paul
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a su
I tried Rusty's suggested patch to modprobe.c (moving the lock forward).
Works like a charm with stock 2.6.14-2 with an initramfs based upon
initramfs-tools.
Please ignore my comments about manual modprobes and the intel sound stuff
screwing up with unknown symbols, I realized that that is a DIFFE
Please ignore/delete the comments about snd_intel8x0, that is a totally
unrelated bug. I tried Rusty's proposed fix for modprobe.c (in bug
333052) and it solves the problem reported in 522 and 333052 for
me (running on a stock linux-image-2.6.14-2 with initramfs made by
initramfs-tools).
--
Package: linux-image-2.6.14-1-686-smp
Version: 2.6.14-2
Followup-For: Bug #333522
Well, I can pretty consistently reproduce this bug, and an interesting
datapoint is that even a manual modprobe after startup causes further
Unknown symbol problems.
I do not know if this is because udev/m-i-t/linux
Package: linux-image-2.6.14-1-686-smp
Version: 2.6.14-1
Followup-For: Bug #333522
udev/unstable uptodate 0.071-1
Just to cover the blanks, it is occuring as well with stock 2.6.14
debian kernels. This is a straight kernel built with an up to date
initramfs tools. initramfs-tools rebuilt the ini
Package: initramfs-tools
Version: 0.37
Followup-For: Bug #336617
Kernel 2.6.14, evms 2.3.3-6
root filesystem is on a lvm2 volume inside a md based raid, all held together
with evms.
Standard EVMS installs do not use the userspace md and lvm tools, but do
require their kernel modules, so it is no
Package: linux-source-2.6.12
Version: 2.6.12-10
Followup-For: Bug #328513
Please turn on *BOTH*:
CONFIG_VIDEO_CX88=m
CONFIG_VIDEO_CX88_DVB=m
in the default kernel. Both modules build and work properly. I'm now
running MythTV on debian with untouched kernel sources. :-)
-- System Information:
Package: linux-image-2.6.12-1-686-smp
Version: 2.6.12-6
Severity: normal
All the V4L drivers are built in the default kernel config, except for
the CX88. I suspect this is either because CX88 support is quite new,
or because there were bugs and conflicts in the CX88 code earlier.
In 2.6.12, the
Package: kernel-source-2.6.11
Severity: wishlist
Tags: patch
In kernel 2.6, a patch was added to the system to allow a block device
driver to claim an entire device as its own. That well meaning change
has been a bane to everyone trying to migrate from hard partition support
to using the device m
17 matches
Mail list logo
