Hello,
As of version 0.0.20040329-20, hotplug has re-blacklisted the de4x5 module,
so this is probably no longer an RC bug.
However, please c.f.
http://lists.debian.org/debian-alpha/2005/04/msg2.html, which is a
report from a user indicating that tulip still doesn't work on his hardware.
:/
severity 294867 important
thanks
On Sat, Apr 02, 2005 at 02:12:30AM -0800, Steve Langasek wrote:
As of version 0.0.20040329-20, hotplug has re-blacklisted the de4x5 module,
so this is probably no longer an RC bug.
I've just accepted hotplug -21 into testing, so this is indeed no longer RC.
As
I've just switched to tulip from de4x5 on my alpha, and none of the problems
that were present previously appear to persist under 2.4.27-2. So I don't
have any objections to blacklisting de4x5.
OTOH, I also can't find anything in the current kernel-image 2.6.8-2
packages that explains why the
Now I see that de4x5 used to be blacklisted by default by hotplug, but I
removed last year when somebody told me that the driver was obsolete.
Please let me know if you will finally kill it or I have to add it again
to the default blacklist.
As of 2.4.27-2, de4x5 appears to still be the most
reassign 294867 kernel-image-2.6.8-i386
thanks
If a driver hangs the system when loaded, it is a good hint of a kernel
bug.
--
ciao,
Marco
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Mon, Feb 14, 2005 at 06:21:24PM +0100, Marco d'Itri wrote:
reassign 294867 kernel-image-2.6.8-i386
thanks
If a driver hangs the system when loaded, it is a good hint of a kernel
bug.
I think de4x5 should be a driver of last resort. Tulip should always
be preferred to drive a given piece
Matthew Wilcox wrote:
I think de4x5 should be a driver of last resort. Tulip should always
be preferred to drive a given piece of hardware. I wouldn't shed any
tears if we stopped shipping de4x5 by default -- it's caused no end of
problems on parisc and ia64.
OTOH it's the only module that
On Mon, Feb 14, 2005 at 01:09:43PM -0500, Joey Hess wrote:
Matthew Wilcox wrote:
I think de4x5 should be a driver of last resort. Tulip should always
be preferred to drive a given piece of hardware. I wouldn't shed any
tears if we stopped shipping de4x5 by default -- it's caused no end of
Matthew Wilcox wrote:
On Mon, Feb 14, 2005 at 01:09:43PM -0500, Joey Hess wrote:
Matthew Wilcox wrote:
I think de4x5 should be a driver of last resort. Tulip should always
be preferred to drive a given piece of hardware. I wouldn't shed any
tears if we stopped shipping de4x5 by
On Feb 14, Matthew Wilcox [EMAIL PROTECTED] wrote:
I think you have that backwards. de4x5 *doesn't* work on hppa whereas
tulip does.
Now I see that de4x5 used to be blacklisted by default by hotplug, but I
removed last year when somebody told me that the driver was obsolete.
Please let me know
Package: base
Severity: critical
Justification: breaks the whole system
Debian autodetects my 4 port Phobos P430TX and attempts to use the de4x5.ko
driver. When the boot process gets to initializeing the card it outputs an
endless loop of this message, and won't finish booting:
bad media code
reassign 294867 hotplug
thanks
This sounds like a problem with hotplug (or discover?) loading the wrong
driver for the hardware.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
12 matches
Mail list logo
