Bug#257844: marked as done (kernel-image-2.4.25-powerpc-pmac: irda not detected until macserial is loaded)

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Bug#257844: marked as done (kernel-image-2.4.25-powerpc-pmac: irda not detected until macserial is loaded)

Debian Bug Tracking System
Your message dated Mon, 31 Jul 2006 19:03:19 +0200
with message-id <[hidden email]>
and subject line old 2.4 kernel bug
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Package: kernel-image-2.4.25-powerpc-pmac
Version: 2.4.25-8
Severity: minor

This is reporting a difference between 2.4.24 and 2.4.25:
Irda on ttyS1 is not detected by 2.4.25 by bootup anymore,
until the macserial module is loaded.

(Apple Powerbook G3 400 MHZ lombard.)

It took me a while to find the cause because I did not expect
this change and thought irda would just start up as before.
So this might break installations at upgrades and I unsure if
a configuration question would ease the situation, thus I am just
filing a minor bug. :)


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Kernel: Linux 2.4.25-powerpc
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro

Versions of packages kernel-image-2.4.25-powerpc-pmac depends on:
ii  kernel-modules-2.4.25-powerpc 2.4.25-8   linux kernel modules for the power

-- no debconf information

dear bug subitters,

thanks for your bug report. Newest Debian unstable ships much newer
linux 2.6 kernels. So either your bug repot got solved or due to new
packageing is no longer relevant. therefor closing.
if you still experience the mentioned problem, don't hesitate to write
back and the report will be reopened.

you might want to test out the daily builds of the debian installer:
the next beta 3 installer for Debian Etch is expected soon. :)

thanks for your feedback.

best regards