On Fri, Jan 05, 2007 at 08:27:25AM +0100, maximilian attems wrote: > tags 334104 -wontfix > tags 334104 pending > thanks > > morning jurij, > > On Thu, Jan 04, 2007 at 10:36:12PM -0800, Jurij Smakov wrote: > > tag 373621 wontfix > > thanks > > > > My attempt to actually do something about this ancient bug (#334104) > > has been blocked by Bastian Blank, who considers the proposed patch to > > violate the patch acceptance policy. As I don't feel like wasting my > > breath arguing about it, the best thing I can do is tag this bug > > wontfix, in hope that the debian-installer people will be able to > > provide some alternative solution. > > well i considered your patch to be a fine distro specific workaround. > now i've gone another way and disabled the dup pci-id's in tulip for i386. > afaik dmfe.ko explodes on parisc. so you could do the inverse for sparc. > > ideally dmfe and tulip shouldn't pretend to work for chipsets they > can't, but that codebase won't get fixed in time for the etch release.
Hi, As I said, I don't think the solution of dropping the duplicate PCI IDs in different drivers for different architectures to be optimal. There is always a possibility that someone will insert an arbitrary PCI card into any box with a PCI bus. If currently the user will be slightly inconvenienced, if your proposed solution is implemented, he/she will have to rebuild the kernel to get it to work. Anyway, Frans Pop has recently posted a proposed patch for the installer, which will make it possible to blacklist and arbitrary module from loading, see http://lists.debian.org/debian-boot/2007/01/msg00207.html If this will make it into etch, that will solve the problem. Best regards, -- Jurij Smakov [EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
