Processed: Tag as +patch, next try

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 380531 +patch
Bug#380531: linux-2.6: mips and mipsel personality(2) support is broken
There were no tags set.
Tags added: patch

> thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Re: Bug#380531: linux-2.6: mips and mipsel personality(2) support is broken

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 380531 normal
Bug#380531: linux-2.6: mips and mipsel personality(2) support is broken
Severity set to `normal' from `important'

> thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#380531: linux-2.6: mips and mipsel personality(2) support is broken

[Bastian Blank]

severity 380531 normal
thanks

On Sun, Jul 30, 2006 at 07:39:39PM +0100, Roger Leigh wrote:
> personality(2) only works the first time it is called [in the lifetime
> of a process/program].  All subsequent calls return EPERM, which is
> not a documented return value;

As the linux source don't document return values and it is linux
specific, the linux kernel is allowed to return any error is thinks is
needed.

>   None of the other architectures I have tested
> (amd64, arm, i386, ia64, powerpc) behave this way: personality(2) is
> not a privileged call.

That it return sane values everything else don't document it as a non
priviledged call.

Bastian

-- 
Women are more easily and more deeply terrified ... generating more
sheer horror than the male of the species.
-- Spock, "Wolf in the Fold", stardate 3615.4


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#380531: linux-2.6: mips and mipsel personality(2) support is broken

[Roger Leigh]

Bastian Blank <[EMAIL PROTECTED]> writes:

> severity 380531 normal
> thanks
>
> On Sun, Jul 30, 2006 at 07:39:39PM +0100, Roger Leigh wrote:
>> personality(2) only works the first time it is called [in the lifetime
>> of a process/program].  All subsequent calls return EPERM, which is
>> not a documented return value;
>
> As the linux source don't document return values and it is linux
> specific, the linux kernel is allowed to return any error is thinks is
> needed.

The point was, it's not documented *in the kernel source*, either.
-EPERM is not used *anywhere*, in either the arch/mips or generic
kernel execdomain code.  See kernel/exec_domain.c and
arch/mips/kernel/linux32.c.

>>   None of the other architectures I have tested
>> (amd64, arm, i386, ia64, powerpc) behave this way: personality(2) is
>> not a privileged call.
>
> That it return sane values everything else don't document it as a non
> priviledged call.

There are no permissions checks in the kernel source.  EPERM is a
bogus return value due to some weirdness in the sys32_personality code
on mips (See ths's patch).


-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?   http://gutenprint.sourceforge.net/
   `-GPG Public Key: 0x25BFB848   Please sign and encrypt your mail.


pgpR03q4BrfeD.pgp
Description: PGP signature

usplash_0.3b_i386.changes ACCEPTED

[Debian Installer]

Accepted:
usplash_0.3b.dsc
  to pool/main/u/usplash/usplash_0.3b.dsc
usplash_0.3b.tar.gz
  to pool/main/u/usplash/usplash_0.3b.tar.gz
usplash_0.3b_i386.deb
  to pool/main/u/usplash/usplash_0.3b_i386.deb


Override entries for your package:
usplash_0.3b.dsc - optional misc
usplash_0.3b_i386.deb - optional misc

Announcing to debian-devel-changes@lists.debian.org
Closing bugs: 356193 


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Decision about oot-modules for etch

[Daniel Baumann]

Hi,

as stated in [0], waldi is working on an oot-module conglomeration
package to solve NEW spamming for oot-module packages when the kernel
ABI is bumped.

As stated in [1], there are though about to not allow other oot-modules
in main outside of the conglomeration package for etch.

As discussed on IRC at the end of june with aba and HE, they are in
favour to dropp those modules from the release-team point of view.

Now, I would like to have a definitive statement for that to get
everything prepared for etch (basically the ipw packages[2]). This
means, a decision of the kernel-team and the release-team is required.
Atm, there are the following questions open:

  * What is the ETA for the linux-modules-extra package in the archive?

  * Will be oot-modules in main outside of the linux-modules-extra be
removed by the release-team for etch?

  * Will there be something similar for contrib modules too (e.g.
linux-modules-contrib)?

  * If no conglomeration package for contrib modules, will oot-modules
of contrib be removed by the release-team for etch?

  * If contrib oot-modules outside of a conglomeration packages will not
be removed, will it be possible to have updates to the usual
conditions for point-releases, or, will this be refused for
oot-modules of contrib given no contrib-conglomeration package is
done?

Regards,
Daniel

[0] http://lists.debian.org/debian-kernel/2006/06/msg00438.html
[1] http://lists.debian.org/debian-kernel/2006/06/msg00441.html

[2] The ipw drivers are in the kernel mainline (ipw3945 will hopefully
follow soon). Given that Intel does lack several weeks to month
behind with the integration of their independent release drivers
into mainline, it is nice to have those drivers as oot-modules too
in the archive (especially for later backporting once etch is
released and without the need of using a backported kernel too).
Therefore, a decision is required for me, otherwise I'm not going
to do potentially useless work to convert them to oot when they will
be removed in a month or two anyway.

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  [EMAIL PROTECTED]
Internet:   http://people.panthera-systems.net/~daniel-baumann/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#335538: Similar problem - kernel 2.6.8-2-386

[Stephen G]

I am running Debian3.1 with kernel 2.6.8-2-386 on a Dell Laptop. I am using it 
as a remotely accessed always-on server. It seems to run quite well, but 
sometimes after a few months, I get a "dma_timer_expiry: dma status == 0x20" 
error the file system (reiserFS) resets itself into readonly mode. I get all 
sorts of Input/Output errors and I can't even reboot the box.
Is this showing that the disk is bad? It seems not to be as it is working fine 
for months before getting the DMA errors. Is there anything I can configure to 
avoid these problems? Is there a kernel modification, or fstab/hdparm command, 
or other filesystem that I should use that will prevent the drive going into 
read-only mode?
Thank you for any help!

[EMAIL PROTECTED]:/etc# cat debian_version
cat: debian_version: Input/output error
from syslog:
Jul 1 13:55:54 localhost kernel: hda: dma_timer_expiry: dma status == 0x20
Jul 1 13:56:59 localhost syslogd: /var/log/kern.log: Input/output error
Jul 1 13:56:59 localhost kernel: hda: DMA timeout retry
Jul 1 13:56:59 localhost kernel: hda: timeout waiting for DMA
Jul 1 13:56:59 localhost kernel: hda: status timeout: status=0xd0 { Busy }
Jul 1 13:56:59 localhost kernel:
Jul 1 13:56:59 localhost kernel: hda: drive not ready for command
Jul 1 13:56:59 localhost kernel: ide0: reset timed-out, status=0xd0
Jul 1 13:56:59 localhost kernel: hda: status timeout: status=0xd0 { Busy }
Jul 1 13:56:59 localhost kernel:
Jul 1 13:56:59 localhost kernel: hda: drive not ready for command
Jul 1 13:56:59 localhost kernel: ide0: reset timed-out, status=0xd0
Jul 1 13:56:59 localhost kernel: end_request: I/O error, dev hda, sector 
13187688
Jul 1 13:56:59 localhost kernel: end_request: I/O error, dev hda, sector 270432
Jul 1 13:56:59 localhost kernel: Buffer I/O error on device hda2, logical block 
1674
Jul 1 13:56:59 localhost kernel: lost page write due to I/O error on hda2
Jul 1 13:56:59 localhost kernel: end_request: I/O error, dev hda, sector 270440
Jul 1 13:56:59 localhost kernel: Buffer I/O error on device hda2, logical block 
1675
Jul 1 13:56:59 localhost kernel: lost page write due to I/O error on hda2
Jul 1 13:56:59 localhost kernel: end_request: I/O error, dev hda, sector 270448
Jul 1 13:56:59 localhost kernel: Buffer I/O error on device hda2, logical block 
1676
Jul 1 13:56:59 localhost kernel: lost page write due to I/O error on hda2
Jul 1 13:56:59 localhost kernel: REISERFS: abort (device hda2): Journal write 
error in flush_commit_list
Jul 1 13:56:59 localhost kernel: REISERFS: Aborting journal for filesystem on 
hda2
Jul 1 13:56:59 localhost kernel: ReiserFS: hda2: warning: clm-6006: writing 
inode 688 on readonly FS
Jul 1 13:56:59 localhost last message repeated 11 times
Jul 1 13:56:59 localhost kernel: ReiserFS: hda2: warning: clm-6006: writing 
inode 1726 on readonly FS
Jul 1 13:56:59 localhost last message repeated 5 times
Jul 1 13:56:59 localhost kernel: ReiserFS: hda2: warning: clm-6006: writing 
inode 688 on readonly FS
Jul 1 13:56:59 localhost last message repeated 5 times
Jul 1 13:56:59 localhost kernel: ReiserFS: hda2: warning: clm-6006: writing 
inode 1726 on readonly FS
Jul 1 13:56:59 localhost last message repeated 5 times
Jul 1 13:56:59 localhost kernel: ReiserFS: hda2: warning: clm-6006: writing 
inode 688 on readonly FS
Jul 1 13:56:59 localhost last message repeated 11 times
Jul 1 13:56:59 localhost kernel: ReiserFS: hda2: warning: clm-6006: writing 
inode 1726 on readonly FS
Jul 1 13:56:59 localhost [EMAIL PROTECTED]:/var/log#


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Decision about oot-modules for etch

[Bastian Blank]

On Mon, Jul 31, 2006 at 12:46:09PM +0200, Daniel Baumann wrote:
>   * What is the ETA for the linux-modules-extra package in the archive?

I'm just finished with my exams, so I hope I can get it finished this
week.

>   * Will there be something similar for contrib modules too (e.g.
> linux-modules-contrib)?

If really needed, this is possible. If I understand Ganneff correctly,
it is even possible to have a source package in main which builds
binaries for contrib under some conditions.

> [2] The ipw drivers are in the kernel mainline (ipw3945 will hopefully
> follow soon).

Only if they remove the dependency on the binary-only deamon. I'm
currently doing this for my own anyway.

Bastian

-- 
Only a fool fights in a burning house.
-- Kank the Klingon, "Day of the Dove", stardate unknown


signature.asc
Description: Digital signature

Re: Decision about oot-modules for etch

[Andreas Barth]

* Daniel Baumann ([EMAIL PROTECTED]) [060731 12:46]:
> as stated in [0], waldi is working on an oot-module conglomeration
> package to solve NEW spamming for oot-module packages when the kernel
> ABI is bumped.

> Now, I would like to have a definitive statement for that to get
> everything prepared for etch (basically the ipw packages[2]). This
> means, a decision of the kernel-team and the release-team is required.
> Atm, there are the following questions open:

AFAICS ipw doesn't provide oot-modules, but only ipw*-source. Is that
correct?


Cheers,
Andi
-- 
  http://home.arcor.de/andreas-barth/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#380089: possibly inadequate solution

[maximilian attems]

On Sun, Jul 30, 2006 at 07:25:20PM -0700, Steve Langasek wrote:
> On Sat, Jul 29, 2006 at 05:53:27PM +0100, martin f krafft wrote:
> > Anyway, I disagree with the way 0.73 fixes the bug: it replicates
> > the functionality provided by mdadm >=2.5-1 into a hack within the
> > package. Granted, the hack is only used when mdadm >=2.5-1  is not
> > installed, but still, it's a hack.
> 
> > The maintainer failed to give any reasons why his solution is
> > preferred over a simple conflict against mdadm <<2.5-1, which is
> > what I proposed even before we started the transition. I do not see
> > why we should have a hack ensuring that everything works when mdadm
> > <<2.5-1 is installed, instead of just ensuring that a newer mdadm
> > should be installed by means of a conflict. Then again, a conflict
> > could possibly remove the mdadm package altogether, which would be
> > equally bad. There seems to be no way to tell Debian to conflict
> > with versions prior to a specific package's specific version, but to
> > ensure an upgrade as a resolution conflict, not the package's
> > removal.
> 
> Yes, that would be a dependency then, not a conflict.  The reasons for not
> making this a dependency are clear.
> 
> The reasons for wishing to avoid a versioned Conflicts: are also clear to
> me, being precisely those that you describe above.

indeed aboves thoughts where the primary reason.
also i wanted to stay on the path of a proven solution:
ubuntu had faced the same transition to dapper from breezy, with
prior mdadm without mdadm hooks and they choose to add this small
functionality to mkinitramfs. afaik from their bug tracking system
this worked out. this "duplicate" code will be easily dropped postetch.
 
> So making initramfs-tools compatible with older versions of mdadm seems like
> a good idea to me.  Are there specific reasons why you think the proposed
> solution is technically inadequate?

the implementation itself needs more test,
i had a test sarge upgrade box that weekend where it worked out fine.

mdrun was avoided due too getting random md devices.
although according to fjp older mdadm seems to have it's share
of problems:
http://lists.debian.org/debian-boot/2006/07/msg00244.html

so i hope to stay in contact with madduck to check out
on which range the chosen solution works and refine it.

best regards

-- 
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Decision about oot-modules for etch

[Daniel Baumann]

Andreas Barth wrote:
> AFAICS ipw doesn't provide oot-modules, but only ipw*-source. Is that
> correct?

As I wrot in '[2]' of the previous mail, I want ipw2100 and ipw2200
(and, therefore also ieee8201) as oot, *although* they are already in
mainline. But I'm not going to do that when a few weeks afterwards they
are removed anyway in favour for a conglomeration package.

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  [EMAIL PROTECTED]
Internet:   http://people.panthera-systems.net/~daniel-baumann/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Decision about oot-modules for etch

[Andreas Barth]

* Daniel Baumann ([EMAIL PROTECTED]) [060731 16:29]:
> Andreas Barth wrote:
> > AFAICS ipw doesn't provide oot-modules, but only ipw*-source. Is that
> > correct?

> As I wrot in '[2]' of the previous mail, I want ipw2100 and ipw2200
> (and, therefore also ieee8201) as oot, *although* they are already in
> mainline. But I'm not going to do that when a few weeks afterwards they
> are removed anyway in favour for a conglomeration package.

Ah, ok. Thanks.


Cheers,
Andi
-- 
  http://home.arcor.de/andreas-barth/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Decision about oot-modules for etch

[Andreas Barth]

* Daniel Baumann ([EMAIL PROTECTED]) [060731 12:46]:
> Now, I would like to have a definitive statement for that to get
> everything prepared for etch (basically the ipw packages[2]). This
> means, a decision of the kernel-team and the release-team is required.

I don't see any release-team decisions required right now. :)

Basically, I tend to something like:

>   * Will be oot-modules in main outside of the linux-modules-extra be
> removed by the release-team for etch?

If there are fewer (source) packages to be rebuild in case of kernel abi
changes, that's something good. If "all important" modules are there, we
might consider to deprecate/disallow other packages to require to be
rebuild in case of kernel changes. I don't really mind to make one
exception for some package if there are good reasons; but if that means
that 40 maintainers start jumping because their package should get the
exception, that boils down to no exception. :)

As to allow new packages with build oot-modules: I'm not too sure if we
should allow that, as every module makes a kernel update more
complicated. But of course, you could try to convince us that ipw is
important enough for that.

>   * If no conglomeration package for contrib modules, will oot-modules
> of contrib be removed by the release-team for etch?

Same for contrib: If there is no alternative to single packages, well,
we need to use single packages. Also, how many packages in contrib
generate oot-modules? If there are only 1 or 2, why bother?

>   * If contrib oot-modules outside of a conglomeration packages will not
> be removed, will it be possible to have updates to the usual
> conditions for point-releases, or, will this be refused for
> oot-modules of contrib given no contrib-conglomeration package is
> done?

I don't see a reason to refuse upgrades during point release right now.
If the oot-package with their own modules are updated, everything is
fine. Updates during point release are more problematic with a
conglomeration package, as all binary packages need to be rebuild,
forcing users a (potentially) unneeded package upgrade. (Of course,
there are the normal rules for stable updates as well.)


Cheers,
Andi
-- 
  http://home.arcor.de/andreas-barth/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#380089: possibly inadequate solution

[martin f krafft]

also sprach maximilian attems <[EMAIL PROTECTED]> [2006.07.31.1439 +0100]:
> mdrun was avoided due too getting random md devices.
> although according to fjp older mdadm seems to have it's share
> of problems:
> http://lists.debian.org/debian-boot/2006/07/msg00244.html

These problems should be solved with 2.5. Frans was testing with
2.4, which had these problems as confirmed by upstream.

-- 
Please do not send copies of list mail to me; I read the list!
 
 .''`. martin f. krafft <[EMAIL PROTECTED]>
: :'  :proud Debian developer and author: http://debiansystem.info
`. `'`
  `-  Debian - when you have better things to do than fixing a system


signature.asc
Description: Digital signature (GPG/PGP)

PowerPC 2.4 removal

[Martin Michlmayr]

Can someone please look through these PowerPC 2.4 kernel bug reports
and close those which no longer apply in 2.6 and reassign the rest to
the linux-2.6 package.  Thanks.

67718: normal: boot-floppies: SCSI hangs on iMac
80878: normal: problem booting - keyboard not responding
100421: normal: kernel-image-2.2.19-pmac: Panic during autofs upgrade
120116: normal: base: [kernel-image-2.2.19] Attempting to install ltpc driver 
results in kernel panic
132498: minor: kernel-image-2.4.16-newpmac: displays garbage on console
145504: normal: 2.4.18 damages dmasound on original (300) ibook
163091: normal: card services cause kernel oops with any pcmcia card on PPC arch
190751: normal: console-data: can no longer change the virtual terminal with 
the keyboard
204976: normal: console-tools: changing to virtual terminal 7 makes the machine 
unusable
212678: normal: aic7xxx driver failure, System hangs on startup Adaptec SCSI 
connect card 2906
217540: minor: kernel-patch-benh: weird patch behavior when combined with 
lowlatency patch
217612: normal: kernel-patch-2.4.21-powerpc: please build mace as a module
217778: important: kernel-image-2.4.22-powerpc: CRT output doesn't work (when 
enabled by m3mirror)
228211: normal: kernel-build-... should provide kernel-headers-...
240801: minor: kernel-image-2.4.25-powerpc-pmac: sound module switches to full 
volume
242553: normal: kernel-image-2.4.25-powerpc-pmac: beta3 installer uninorth 
support not included
243254: normal: reiserfs root = kernel panic
244798: normal: Architecture value is "any"
245012: important: initrd does not work with XFS root on powerpc
247391: normal: Kernel hangs when inserting airport module
248234: important: debian-installer: Cannot boot the installer on powerpc
252402: important: kernel-image-2.4.25-powerpc-prep: "could not chdir to =D:No 
such file or directory"
253327: normal: kernel-image: Wrong boot install for PPC PReP
257841: normal: kernel-image-2.4.25-powerpc-pmac: dying durch wakeup
257844: minor: kernel-image-2.4.25-powerpc-pmac: irda not detected until 
macserial is loaded
258520: normal: kernel-image-2.4.25-powerpc-small-pmac: fail to install
259903: normal: installation reports
270992: critical: kernel-patch-powerpc-2.4.26: 2.4.26 powerpc package is 
scheduled for removal, see 2.4.27 package for bug reports.
274249: normal: kernel-image-2.4.27-powerpc-prep does not install because of an 
not working .deb package
277500: wishlist: kernel-image-2.4.27-powerpc-pmac: please use 
CONFIG_MAC_SERIAL=y
298565: normal: bug in kernel-patch-powerpc-2.4.27
302192: wishlist: kernel-patch-powerpc-2.4.27: Please build-depend on exact 
kernel-tree-version
330777: important: kernel-patch-powerpc-2.4.27-11: "make dep" asks for 
"arch/ppc/appleboot" which does not excist

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#380649: initramfs-tools: nfs options should comply with nfsroot.txt from linux documentation

[Vagrant Cascadian]

Package: initramfs-tools
Severity: wishlist

it would be nice if the nfs kernel commandline boot options of
initramfs-tools supported the options found in the linux kernel
Documentation/nfsroot.txt, in the "kernel command line" section.

http://lxr.linux.no/source/Documentation/nfsroot.txt

particularly "root=/dev/nfs" as a means of enabling the NFS support,
rather than hacking a configuration file option, but also more complete
support for "nfsroot", and "ip".

i'll try and work on some patches in the near future...

thanks!

live well,
  vagrant


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Decision about oot-modules for etch

[Daniel Baumann]

Andreas Barth wrote:
> I don't see any release-team decisions required right now. :)

I beg to differ, see below.

> Basically, I tend to something like:
> 
>>   * Will be oot-modules in main outside of the linux-modules-extra be
>> removed by the release-team for etch?
> 
> If there are fewer (source) packages to be rebuild in case of kernel abi
> changes, that's something good. If "all important" modules are there, we
> might consider to deprecate/disallow other packages to require to be
> rebuild in case of kernel changes. I don't really mind to make one
> exception for some package if there are good reasons; but if that means
> that 40 maintainers start jumping because their package should get the
> exception, that boils down to no exception. :)

That's the reason why I ask. I know about this "if 'all important'
modules are there, we might consider to deprecate/disallow other
packages" since the discussion with you on IRC end of june already.

It's way to uncertain to have still the same statement and I think, it's
late enough to nail that down, because if maintainers shall put their
packages together, they have know that now and start doing that now.

Can you make an announcement to all oot-module maintainers, telling them
that they should put their packages together into linux-modules-extra
(for main) or a similar one for contrib, and if they're not doing it,
they will end up in an unsupported (no updates for point-releases, no
updates for kernel ABI bump updates) package.

> As to allow new packages with build oot-modules: I'm not too sure if we
> should allow that, as every module makes a kernel update more
> complicated. But of course, you could try to convince us that ipw is
> important enough for that.

Let's get the generic thing above first, after that, depending on your
'decision', there is more specifically for ipw needed or not.

> Same for contrib: If there is no alternative to single packages, well,
> we need to use single packages. Also, how many packages in contrib
> generate oot-modules? If there are only 1 or 2, why bother?

I think it's less than 10.

> I don't see a reason to refuse upgrades during point release right now.
> If the oot-package with their own modules are updated, everything is
> fine. Updates during point release are more problematic with a
> conglomeration package, as all binary packages need to be rebuild,
> forcing users a (potentially) unneeded package upgrade. (Of course,
> there are the normal rules for stable updates as well.)

Ok.

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  [EMAIL PROTECTED]
Internet:   http://people.panthera-systems.net/~daniel-baumann/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Decision about oot-modules for etch

[Otavio Salvador]

Daniel Baumann <[EMAIL PROTECTED]> writes:

> Can you make an announcement to all oot-module maintainers, telling them
> that they should put their packages together into linux-modules-extra
> (for main) or a similar one for contrib, and if they're not doing it,
> they will end up in an unsupported (no updates for point-releases, no
> updates for kernel ABI bump updates) package.

Where I find the source package to hack on? I want to move spca5xx to
it.

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#380089: possibly inadequate solution

[maximilian attems]

On Mon, Jul 31, 2006 at 03:13:32PM +0100, martin f krafft wrote:
> also sprach maximilian attems <[EMAIL PROTECTED]> [2006.07.31.1439 +0100]:
> > mdrun was avoided due too getting random md devices.
> > although according to fjp older mdadm seems to have it's share
> > of problems:
> > http://lists.debian.org/debian-boot/2006/07/msg00244.html
> 
> These problems should be solved with 2.5. Frans was testing with
> 2.4, which had these problems as confirmed by upstream.

cool to hear that it was an 2.4 specific trouble.

anyway the initramfs-tools implementation targets 1.9.0-4sarge1,
so i'm happy on your input for the sarge specific version.
 
-- 
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#380089: possibly inadequate solution

[martin f krafft]

also sprach maximilian attems <[EMAIL PROTECTED]> [2006.07.31.1658 +0100]:
> anyway the initramfs-tools implementation targets 1.9.0-4sarge1,
> so i'm happy on your input for the sarge specific version.

difficult to say. creating mdadm.conf (see /usr/share/mdadm/mkconf)
and running `mdadm -Asayes --run` should do. If it doesn't do what
mdrun used to do, and even better, I am in trouble. But so far, I've
had no indication that it doesn't work the way I expect it.

Anyway, mdrun will be in etch, albeit deprecated. I'll only remove
it after etch if everything goes well. Thus, we could potentially
revert to mdrun in the last second before the release.

-- 
Please do not send copies of list mail to me; I read the list!
 
 .''`. martin f. krafft <[EMAIL PROTECTED]>
: :'  :proud Debian developer and author: http://debiansystem.info
`. `'`
  `-  Debian - when you have better things to do than fixing a system


signature.asc
Description: Digital signature (GPG/PGP)

Re: PowerPC 2.4 removal

[maximilian attems]

heya,

On Mon, Jul 31, 2006 at 05:37:34PM +0200, Martin Michlmayr wrote:
> Can someone please look through these PowerPC 2.4 kernel bug reports
> and close those which no longer apply in 2.6 and reassign the rest to
> the linux-2.6 package.  Thanks.

the one below need a check by ppc guys - reassigning those:
> 67718: normal: boot-floppies: SCSI hangs on iMac
no idea
> 145504: normal: 2.4.18 damages dmasound on original (300) ibook
> 240801: minor: kernel-image-2.4.25-powerpc-pmac: sound module switches to 
> full volume
older oss drivers - alsa alternative?
> 212678: normal: aic7xxx driver failure, System hangs on startup Adaptec SCSI 
> connect card 2906
woow i thought 2.6 aic7xxx got worse.
> 217612: normal: kernel-patch-2.4.21-powerpc: please build mace as a module
> 248234: important: debian-installer: Cannot boot the installer on powerpc
> 257841: normal: kernel-image-2.4.25-powerpc-pmac: dying durch wakeup
> 298565: normal: bug in kernel-patch-powerpc-2.4.27
all those needs a reping - will dow tomorrow.
> 253327: normal: kernel-image: Wrong boot install for PPC PReP
> 252402: important: kernel-image-2.4.25-powerpc-prep: "could not chdir to 
> =D:No such file or directory"
do we support prep??
> 277500: wishlist: kernel-image-2.4.27-powerpc-pmac: please use 
> CONFIG_MAC_SERIAL=y
check in 2.6


the list below no longer matter or
submitter left moreinfo bug open since long,
i'm closing those:

> 80878: normal: problem booting - keyboard not responding
input system in 2.6 reworked
> 100421: normal: kernel-image-2.2.19-pmac: Panic during autofs upgrade
no current report about ppc autofs troubles
> 120116: normal: base: [kernel-image-2.2.19] Attempting to install ltpc driver 
> results in kernel panic
newer ltpc driver
> 132498: minor: kernel-image-2.4.16-newpmac: displays garbage on console
userspace trouble
> 163091: normal: card services cause kernel oops with any pcmcia card on PPC 
> arch
newer 2.6 pcmcia is very different
> 190751: normal: console-data: can no longer change the virtual terminal with 
> the keyboard
input changed a lot since
> 204976: normal: console-tools: changing to virtual terminal 7 makes the 
> machine unusable
old userspace stuff
> 217540: minor: kernel-patch-benh: weird patch behavior when combined with 
> lowlatency patch
no longer relevant.
> 217778: important: kernel-image-2.4.22-powerpc: CRT output doesn't work (when 
> enabled by m3mirror)
userspace stuff
> 228211: normal: kernel-build-... should provide kernel-headers-...
2.6 provides headers
> 242553: normal: kernel-image-2.4.25-powerpc-pmac: beta3 installer uninorth 
> support not included
talks about backport patch - assume upstream ok
> 243254: normal: reiserfs root = kernel panic
normal very old reiserfs
> 244798: normal: Architecture value is "any"
can't be the case
> 245012: important: initrd does not work with XFS root on powerpc
yaboot trouble
> 247391: normal: Kernel hangs when inserting airport module
driver got better
> 257844: minor: kernel-image-2.4.25-powerpc-pmac: irda not detected until 
> macserial is loaded
need more info no answer by submitter
> 258520: normal: kernel-image-2.4.25-powerpc-small-pmac: fail to install
fixed
> 259903: normal: installation reports
needs moreinfo no answer
> 270992: critical: kernel-patch-powerpc-2.4.26: 2.4.26 powerpc package is 
> scheduled for removal, see 2.4.27 package for bug reports.
done
> 274249: normal: kernel-image-2.4.27-powerpc-prep does not install because of 
> an not working .deb package
submitter found a workaround not interested in 2.6 testing
> 302192: wishlist: kernel-patch-powerpc-2.4.27: Please build-depend on exact 
> kernel-tree-version
useless inbetwen
> 330777: important: kernel-patch-powerpc-2.4.27-11: "make dep" asks for 
> "arch/ppc/appleboot" which does not excist
make dep is no longer needed in 2.6
 
> -- 
> Martin Michlmayr
> http://www.cyrius.com/

thanks 

-- 
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#380649: initramfs-tools: nfs options should comply with nfsroot.txt from linux documentation

[maximilian attems]

severity important
stop

On Mon, Jul 31, 2006 at 08:36:15AM -0700, Vagrant Cascadian wrote:
> Package: initramfs-tools
> Severity: wishlist

please tell the version.

latest initramfs-tools in unstable uses mount from busybox.
 
> it would be nice if the nfs kernel commandline boot options of
> initramfs-tools supported the options found in the linux kernel
> Documentation/nfsroot.txt, in the "kernel command line" section.
> 
> http://lxr.linux.no/source/Documentation/nfsroot.txt
> 
> particularly "root=/dev/nfs" as a means of enabling the NFS support,
> rather than hacking a configuration file option, but also more complete
> support for "nfsroot", and "ip".

which cmdline are your using atm?
 
> i'll try and work on some patches in the near future...

thanks yes nfsmount from klibc still needs polishing.
 
best regards

-- 
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: reassign ppc -> linuc-2.6

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 67718 linux-2.6
Bug#67718: boot-floppies: SCSI hangs on iMac
Bug reassigned from package `kernel-patch-powerpc-2.4.27' to `linux-2.6'.

> reassign 145504 linux-2.6
Bug#145504: 2.4.18 damages dmasound on original (300) ibook
Bug reassigned from package `kernel-patch-powerpc-2.4.27' to `linux-2.6'.

> reassign 240801 linux-2.6
Bug#240801: kernel-image-2.4.25-powerpc-pmac: sound module switches to full 
volume
Bug reassigned from package `kernel-patch-powerpc-2.4.27' to `linux-2.6'.

> reassign 212678 linux-2.6
Bug#212678: aic7xxx driver failure, System hangs on startup Adaptec SCSI 
connect card 2906
Bug reassigned from package `kernel-patch-powerpc-2.4.27' to `linux-2.6'.

> reassign 217612 linux-2.6
Bug#217612: kernel-patch-2.4.21-powerpc: please build mace as a module
Bug reassigned from package `kernel-patch-powerpc-2.4.27' to `linux-2.6'.

> reassign 248234 linux-2.6
Bug#248234: debian-installer: Cannot boot the installer on powerpc
Bug reassigned from package `kernel-patch-powerpc-2.4.27' to `linux-2.6'.

> reassign 257841 linux-2.6
Bug#257841: kernel-image-2.4.25-powerpc-pmac: dying durch wakeup
Bug reassigned from package `kernel-patch-powerpc-2.4.27' to `linux-2.6'.

> reassign 298565 linux-2.6
Bug#298565: bug in kernel-patch-powerpc-2.4.27
Bug reassigned from package `kernel-patch-powerpc-2.4.27' to `linux-2.6'.

> reassign 253327 linux-2.6
Bug#253327: kernel-image: Wrong boot install for PPC PReP
Bug reassigned from package `kernel-patch-powerpc-2.4.27' to `linux-2.6'.

> reassign 252402 linux-2.6
Bug#252402: kernel-image-2.4.25-powerpc-prep: "could not chdir to =D:No such 
file or directory"
Bug reassigned from package `kernel-patch-powerpc-2.4.27' to `linux-2.6'.

> reassign 277500 linux-2.6
Bug#277500: kernel-image-2.4.27-powerpc-pmac: please use CONFIG_MAC_SERIAL=y
Bug reassigned from package `kernel-patch-powerpc-2.4.27' to `linux-2.6'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#80878: marked as done (problem booting - keyboard not responding)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 18:46:56 +0200
with message-id <[EMAIL PROTECTED]>
and subject line old kernel bugs
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)

--- Begin Message ---
Package: boot-floppies
Version: 2.2r2
architecture: powerpc
model: Apple PowerMac 7200 Desktop - 70MHz 603e, I think.  I wouldn't be
so
  lucky to have a 604, I'm assuming.
memory: 40MB
scsi0: 53C94
cdrom: MATSHITA CR-8005A, SCSI
network: MACE, chip rev. 9.64
pcmcia: none
keyboard/mouse: apple adb

disk is a scsi disk, but none of that really matters at present.  it
won't boot off the CDROM,
and when I boot the first floppy, it boots up and outputs the usual
kernel messages, 3 or
4 of which I don't get to see because of this penguin holding a beer
~:^) and
then prompts for the second (root) floppy.  But the keyboard doesn't
respond when
I hit 'ENTER'  Or any other key for that matter.

[EMAIL PROTECTED]


--- End Message ---
--- Begin Message ---
input system got reworked in 2.6,
please reopen if pain subsist.

-- 
maks
--- End Message ---

Bug#270992: marked as done (kernel-patch-powerpc-2.4.26: 2.4.26 powerpc package is scheduled for removal, see 2.4.27 package for bug reports.)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 19:03:19 +0200
with message-id <[EMAIL PROTECTED]>
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)

--- Begin Message ---
Package: kernel-patch-powerpc-2.4.26
Version: 2.4.26-1
Severity: critical


The 2.4.26 powerpc kernels have been scheduled for removal from
sid/sarge as soon as the ftp-master process the bug report asking for
their removal (#270989).

This is a placeholder bug to redirect users/bugreporters to the
kernel-patch-powerpc-2.4.27 package.

Friendly,

Sven Luther

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.8-powerpc
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]

-- no debconf information

--- End Message ---
--- Begin Message ---
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:
http://www.debian.org/devel/debian-installer/
the next beta 3 installer for Debian Etch is expected soon. :)

thanks for your feedback.

best regards

--
maks
--- End Message ---

Bug#132498: marked as done (kernel-image-2.4.16-newpmac: displays garbage on console)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 18:55:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line old 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)

--- Begin Message ---
Package: kernel-image-2.4.16-newpmac
Version: 2.4.16-1.1
Severity: minor

Using mutt on the console, I sometimes see characters or parts of
characters appear.  For example, the ?:Help text on the help line
is often repeated to the edge of the right edge of the screen.

Since this occurs with other curses applications, and often
repeats only parts of characters, I believe this is a kernel
problem.

This occurs on my iBook2.

-- System Information
Debian Release: 3.0
Architecture: powerpc
Kernel: Linux catalonia 2.4.16-newpmac #1 Mon Jan 7 20:51:25 EST 2002 ppc
Locale: LANG=C, LC_CTYPE=C


pgpGQJBEm9mov.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
there are now newer reports against console usage in powerpc against
2.6, so assuming that your bug report got fixed inbetween.

you might want to test the latest Debian installer:
-> http://www.debian.org/devel/debian-installer/
daily builds will be soon switched to expected beta3 for etch.

thanks for your feedback.

-- 
maks
--- End Message ---

Bug#274249: marked as done (kernel-image-2.4.27-powerpc-prep does not install because of an not working .deb package)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 19:03:19 +0200
with message-id <[EMAIL PROTECTED]>
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)

--- Begin Message ---
Package: kernel-image-2.4.27-powerpc-prep
Version: -

During installation of this package i get this error message:

  Internal Error: (=D) is not a directory!

I suppose that is because the variable $image_dir is set to "=D" in
line 35 of  the .deb packages postinst script (the varaiable is
checked validity in line 98 and produces the error message...)
This variable should be set to something usefull like '\boot'

--- End Message ---
--- Begin Message ---
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:
http://www.debian.org/devel/debian-installer/
the next beta 3 installer for Debian Etch is expected soon. :)

thanks for your feedback.

best regards

--
maks
--- End Message ---

Bug#228211: marked as done (kernel-build-... should provide kernel-headers-...)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 19:03:19 +0200
with message-id <[EMAIL PROTECTED]>
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)

--- Begin Message ---
Package: module-assistant
Version: 0.5
Severity: normal

It appears that module-assistant doesn't cope terribly well with the way
the kernel is packaged for PowerPC machines.  The program appears to
insist on having a package kernel-headers-$(uname -r) installed but the
only format in which the source is avaliable as a package is a
kernel-patch-$VER-powerpc package.

I'm not entirely sure what the way forward here is or if this is even a
problem for module-assistant to address - a large part of the reason I'm
trying to use module-assistant is that I don't really follow how one is
supposed to work with kernel module packages shipped as source.

-- System Information:
Debian Release: testing/unstable
Architecture: powerpc
Kernel: Linux damiel 2.4.22-powerpc #1 Wed Jan 14 17:02:37 CET 2004 ppc
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8

Versions of packages module-assistant depends on:
ii  perl  5.8.2-2Larry Wall's Practical Extraction 

-- no debconf information


--- End Message ---
--- Begin Message ---
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:
http://www.debian.org/devel/debian-installer/
the next beta 3 installer for Debian Etch is expected soon. :)

thanks for your feedback.

best regards

--
maks
--- End Message ---

Bug#259903: marked as done (installation reports)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 19:03:19 +0200
with message-id <[EMAIL PROTECTED]>
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)

--- Begin Message ---
Package: installation-reports

Debian-installer-version:
http://cdimage.debian.org/pub/cdimage-testing/sid_d-i/powerpc/20040716/sarge-powerpc-netinst.iso

uname -a: Linux ayu 2.4.25-powerpc #1 mer avr 14 15:38:38 CEST 2004 ppc 
GNU/Linux
Date: 2004-07-16
Method: I used that cdrom image.
Machine: iBook G4 12" 800MHz
Processor: PowerPC G4 (3.3)
Memory: 256 MB
Root Device: IDE
Root Size/partition table:

Filesystem   1K-blocks  Used Available Use% Mounted on
/dev/hda5  3952568416520   3335268  12% /
tmpfs   127000 0127000   0% /dev/shm

Output of lspci:
:00:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 AGP
:00:10.0 VGA compatible controller: ATI Technologies Inc RV250 5c63 [Radeon 
Mobility 9200 M9+] (rev 01)
:10:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 PCI
:10:12.0 Network controller: Broadcom Corporation BCM94306 802.11g (rev 03)
:10:17.0 Class ff00: Apple Computer Inc. KeyLargo/Intrepid Mac I/O
:10:18.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB
:10:19.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB
:10:1a.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB
:10:1b.0 USB Controller: NEC Corporation USB (rev 43)
:10:1b.1 USB Controller: NEC Corporation USB (rev 43)
:10:1b.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
:20:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 Internal PCI
:20:0d.0 Class ff00: Apple Computer Inc. UniNorth/Intrepid ATA/100
:20:0e.0 FireWire (IEEE 1394): Apple Computer Inc. UniNorth 2 FireWire (rev 
81)
:20:0f.0 Ethernet controller: Apple Computer Inc. UniNorth 2 GMAC (Sun GEM) 
(rev 80)

Base System Installation Checklist:

Initial boot worked:[E]
Configure network HW:   [O]
Config network: [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[O]
Reboot: [O]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:
Initial boot with argument "install" didn't work.
I used "install-safe" and I could go on. Any other things were successful.
I have some troubles with configuring X11, but that's not the installation 
problem.



--- End Message ---
--- Begin Message ---
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:
http://www.debian.org/devel/debian-installer/
the next beta 3 installer for Debian Etch is expected soon. :)

thanks for your feedback.

best regards

--
maks
--- End Message ---

Bug#242553: marked as done (kernel-image-2.4.25-powerpc-pmac: beta3 installer uninorth support not included)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 19:03:19 +0200
with message-id <[EMAIL PROTECTED]>
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)

--- Begin Message ---
Package: kernel-image-2.4.25-powerpc-pmac
Severity: normal

The 2.4.25 kernel included in the beta3 installer does not include
uninorth agp support, and needs it for some iBooks such as my 800Mhz G3
model.

Please refer to the message thread on debian-powerpc@lists.debian.org
starting 5 April 2004, entitled "X problem ibook 2.2".

Thanks to the amazing Debian PowerPC team for their work.

Rory

--- End Message ---
--- Begin Message ---
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:
http://www.debian.org/devel/debian-installer/
the next beta 3 installer for Debian Etch is expected soon. :)

thanks for your feedback.

best regards

--
maks
--- End Message ---

Bug#244798: marked as done (Architecture value is "any")

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 19:03:19 +0200
with message-id <[EMAIL PROTECTED]>
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)

--- Begin Message ---
Package: kernel-patch-2.4.25-powerpc
Version: 2.4.25-8

kernel-patch-2.4.25-powerpc fails to build on i386:

 ...
 Processor family (386, 486, 586/K5/5x86/6x86/6x86MX, Pentium-Classic, 
Pentium-MMX, Pentium-Pro/Celeron/Pentium-II, Pentium-III/Celeron(Coppermine), 
Pentium-4, K6/K6-II/K6-III, Athlon/Duron/K7, Opteron/Athlon64/Hammer/K8, Elan, 
Crusoe, Winchip-C6, Winchip-2, Winchip-2A/Winchip-3, CyrixIII/VIA-C3, VIA-C3-2) 
[Pentium-Pro] (NEW) make[2]: *** [oldconfig] Error 1
 make[2]: Leaving directory 
`/tmp/buildd/kernel-patch-2.4.25-powerpc-2.4.25/build-tmp/kernel-source-2.4.25'
 ...

It should use "powerpc" in the Architecture field.

-- 
Matt Kraai[EMAIL PROTECTED]http://ftbfs.org/

--- End Message ---
--- Begin Message ---
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:
http://www.debian.org/devel/debian-installer/
the next beta 3 installer for Debian Etch is expected soon. :)

thanks for your feedback.

best regards

--
maks
--- End Message ---

Bug#100421: marked as done (kernel-image-2.2.19-pmac: Panic during autofs upgrade)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 18:48:08 +0200
with message-id <[EMAIL PROTECTED]>
and subject line old 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)

--- Begin Message ---

Package: kernel-image-2.2.19-pmac
Version: 2.2.19-2
Severity: normal

Greetings,

2.2.19 has generally been crash-free for me, but the two crashes I've  
seen have happened during the last two upgrades of autofs.  In the  most 
recent one, I copied what I could from the screen before reboot,  which 
went something like:


Unable to handle (forgot) address 0004 (error 2000)
NIP: C0055568  XER:   LR: C0056078  regs c11abc90  TRAP: 0300
(lots of other stuff)
Call backtrace:
0001 C0056078 C005618C C002F994 C0003EC4 6FFD91A8 6FFD9998 1000A2FC 
1000A9FC 6FEAE3F8 
Kernel panic: kernel access of bad area pc C0055568 lr C0056078 address 
0004 tsk ps/8022


What's funny is that both times, when I rebooted, automount started 
just  fine; and when I did "dpkg --configure --all", automount set up 
just  fine, complete with start and stop.  So I don't know why this 
only  happens during the first apt-get dselect-upgrade.


Thanks,
--

Adam P.

GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Welcome to the best software in the world today cafe! 





--- End Message ---
--- Begin Message ---
no current report about ppc autofs troubles,
therefor closing this bugreport.
feel free to reopen if pain subsists.

--
maks
--- End Message ---

Bug#302192: marked as done (kernel-patch-powerpc-2.4.27: Please build-depend on exact kernel-tree-version)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 19:03:19 +0200
with message-id <[EMAIL PROTECTED]>
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)

--- Begin Message ---
Package: kernel-patch-powerpc-2.4.27
Version: 2.4.27-4
Severity: wishlist


For the tracking of the open security issues in testing [1], we need a
way to automatically determine for every kernel-image the exact
version of the kernel-source it was compiled with. The easiest way to
do this seems to be a versioned build-dependency.

Is it possible to change the build-dependency from kernel-tree-2.4.27 to
kernel-tree-2.4.27-xx?



[1] http://merkel.debian.org/~joeyh/testing-security.html

--- End Message ---
--- Begin Message ---
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:
http://www.debian.org/devel/debian-installer/
the next beta 3 installer for Debian Etch is expected soon. :)

thanks for your feedback.

best regards

--
maks
--- End Message ---

Bug#245012: marked as done (initrd does not work with XFS root on powerpc)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 19:03:19 +0200
with message-id <[EMAIL PROTECTED]>
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)

--- Begin Message ---
Package: installation-reports
Version: daily 20040419
Severity: important


INSTALL REPORT

Debian-installer-version: daily 20040419
uname -a: 
Date: 2004-apr-21 02:00 CET
Method: netinst CD image
Machine: Apple PowerBook G4 15"
Processor: 1 PowerPC @ 867Mhz
Memory: 512Mb
Root Device: 
Root Size/partition table:
Output of lspci:
Base System Installation Checklist:

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[E]
Reboot: [O]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:

I installed the complete system on a new XFS partition but was unable of
install yaboot because of #244957. So I rebooted the system using the
installation disk and typed, at the boot prompt:

hd:4 root=/dev/hda4 rw

but the kernel was unable to mount the root partition probably because
XFS isn't compiled into the default kernel (2.4.25-powerpc-pmac).
I reinstalled everthing using ext3 and the new system mounted the root
partition correctly.

I believe that all filesystems offered during the installation need to
be compiled *into* the kernel.

When rebooting (with ext3) I found that /etc/fstab contained only one
line: # UNCONFIGURED FSTAB FOR BASE SYSTEM

After rebooting I kept the installation process until prompted for APT
sources. The system found the installation CD inserted so it indexed it,
but then I was unable to specify a different CD I have because I couldn't
eject the first CD. I had to switch to the second console, login as root,
execute eject, read the error message, find out the device name for the
cdrom, execute 'eject /dev/hdc', switch back to the first console.

Then I selected to do not use aptitude, dselect or apt-get and I still
got a message about installing popularity-context but APT stopped
asking for a cdrom but it couldn't mount it because of the wrong /etc/fstab

After creating /etc/fstab, APT worked correctly.

Bye,
Giuseppe

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.3-1-k7
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]

--- End Message ---
--- Begin Message ---
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:
http://www.debian.org/devel/debian-installer/
the next beta 3 installer for Debian Etch is expected soon. :)

thanks for your feedback.

best regards

--
maks
--- End Message ---

Bug#258520: marked as done (kernel-image-2.4.25-powerpc-small-pmac: fail to install)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 19:03:19 +0200
with message-id <[EMAIL PROTECTED]>
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)

--- Begin Message ---
Package: kernel-image-2.4.25-powerpc-small-pmac
Version: 2.4.25-8
Severity: normal

I need to install this package in order to build debian-installer, but when 
installing it on a system with kernel kernel-image-2.6.7-powerpc and LVM the 
install fails:

tux13:/home/rafael# apt-get install kernel-image-2.4.25-powerpc-small-pmac
Reading Package Lists... Done
Building Dependency Tree... Done
Suggested packages:
  kernel-doc-2.4.25
The following NEW packages will be installed:
  kernel-image-2.4.25-powerpc-small-pmac
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 0B/2386kB of archives.
After unpacking 4686kB of additional disk space will be used.
Selecting previously deselected package kernel-image-2.4.25-powerpc-small-pmac.
(Reading database ... 24952 files and directories currently installed.)
Unpacking kernel-image-2.4.25-powerpc-small-pmac (from 
.../kernel-image-2.4.25-powerpc-small-pmac_2.4.25-8_powerpc.deb) ...
Setting up kernel-image-2.4.25-powerpc-small-pmac (2.4.25-8) ...
/usr/sbin/mkinitrd: /lib/modules/2.4.25-powerpc-small: Not a directory
/usr/sbin/mkinitrd: MODULES needs to be set to none?
Failed to create initrd image.
dpkg: error processing kernel-image-2.4.25-powerpc-small-pmac (--configure):
 subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
 kernel-image-2.4.25-powerpc-small-pmac
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

Versions of packages kernel-image-2.4.25-powerpc-small-pmac depends on:
ii  initrd-tools  0.1.71 tools to create initrd image for p
ii  kernel-modules-2.4.25-powerpc 2.4.25-8   linux kernel modules for the power

-- no debconf information

--- End Message ---
--- Begin Message ---
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:
http://www.debian.org/devel/debian-installer/
the next beta 3 installer for Debian Etch is expected soon. :)

thanks for your feedback.

best regards

--
maks
--- End Message ---

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 <[EMAIL PROTECTED]>
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)

--- Begin Message ---
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. :)

Bernhard

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Kernel: Linux 2.4.25-powerpc
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]

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

--- End Message ---
--- Begin Message ---
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:
http://www.debian.org/devel/debian-installer/
the next beta 3 installer for Debian Etch is expected soon. :)

thanks for your feedback.

best regards

--
maks
--- End Message ---

Bug#190751: marked as done (console-data: can no longer change the virtual terminal with the keyboard)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 18:55:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line old 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)

--- Begin Message ---
Package: console-data
Version: 2002.12.04dbs-12
Severity: normal

I can no longer change the virtual terminal with the keyboard on
my Titanium (using the mac-usb-us keymap). I think that this is a
consequence of the patch for bug #108433.

Note: as the Titanium has only one mouse button, I needed two keys
for the other two buttons. The two keys on the right of the space
bar were the most practical ones. So, I have in my /etc/sysctl.conf:

dev.mac_hid.mouse_button_emulation = 1
dev.mac_hid.mouse_button2_keycode = 96
dev.mac_hid.mouse_button3_keycode = 56

-- System Information:
Debian Release: testing/unstable
Architecture: powerpc
Kernel: Linux ay 2.4.18-newpmac #1 Thu Mar 14 22:44:49 EST 2002 ppc
Locale: LANG=C, LC_CTYPE=en_US.ISO8859-1

Versions of packages console-data depends on:
ii  debconf   1.2.34 Debian configuration management sy

-- debconf information:
  console-data/keymap/qwerty/norvegian/standard/keymap: Standard
  console-data/keymap/qwertz/slovene/standard/keymap: Standard
  console-data/keymap/qwerty/portugese/variant: Standard
  console-data/keymap/qwertz/swiss/french/keymap: Standard
  console-data/keymap/qwerty/serbian/standard/keymap: Standard
  console-data/keymap/azerty/layout: French
  console-data/keymap/qwerty/swedish/apple_usb/keymap: Standard
  console-data/keymap/qwerty/spanish/standard/keymap: Standard
  console-data/keymap/qwerty/portugese/apple_usb/keymap: Standard
* console-data/keymap/qwerty/layout: US american
  console-data/keymap/dvorak/unknown/apple_usb/keymap: Standard
  console-data/keymap/qwerty/norwegian/variant: Standard
  console-data/keymap/qwerty/italian/standard/keymap: Standard
  console-data/keymap/qwerty/latin_american/variant: Standard
  console-data/keymap/qwerty/brazilian/standard/keymap: Standard ABNT2
  console-data/keymap/qwerty/estonian/variant: Standard
  console-data/keymap/qwertz/slovene/variant: Standard
  console-data/keymap/dvorak/unknown/left_single-handed/keymap: Standard
  console-data/keymap/dvorak/layout: Unknown
  console-data/keymap/qwerty/dutch/standard/keymap: Standard
  console-data/keymap/qwertz/hungarian/variant: Standard
  console-data/keymap/qwerty/byelorussian/variant: Standard
  console-data/keymap/qwerty/swedish/standard/keymap: Standard
  console-data/keymap/azerty/french/same_as_x11__latin_1_/keymap: Standard
  console-data/keymap/qwerty/slovak/variant: Standard
  console-data/keymap/qwerty/romanian/variant: Standard
  console-data/keymap/azerty/french/with_euro__latin_9_/keymap: Standard
  console-data/keymap/qwerty/canadian/english/keymap: Standard
* console-data/keymap/family: qwerty
  console-data/keymap/qwertz/slovak/standard/keymap: Standard
  console-data/keymap/qwerty/canadian/variant: us
  console-data/keymap/qwertz/serbian/standard/keymap: Standard
  console-data/keymap/qwerty/russian/variant: Standard
  console-data/keymap/qwerty/byelorussian/standard/keymap: Standard
  console-data/keymap/qwerty/bulgarian/variant: Standard
  console-data/keymap/qwerty/hungarian/standard/keymap: Standard
  console-data/keymap/qwertz/hungarian/standard/keymap: Standard
  console-data/keymap/azerty/french/variant: With Euro (latin 9)
  console-data/keymap/qwerty/lithuanian/variant: Standard
  console-data/keymap/qwerty/macedonian/variant: Standard
  console-data/keymap/qwerty/spanish/apple_usb/keymap: Standard
  console-data/keymap/qwertz/layout: German
  console-data/keymap/qwertz/german/standard/keymap: de-latin1
  console-data/keymap/dvorak/unknown/right_single-handed/keymap: Standard
  console-data/keymap/qwerty/us_american/standard/keymap: Standard
  console-data/keymap/qwerty/british/variant: Standard
  console-data/keymap/qwerty/latvian/standard/keymap: latin4
  console-data/keymap/fggiod/layout: Unknown
  console-data/keymap/azerty/belgian/apple_usb/keymap: Standard
  console-data/keymap/qwerty/bulgarian/cp_1251_coding/keymap: Standard
  console-data/keymap/qwerty/finnish/standard/keymap: Standard
  console-data/keymap/qwertz/german/variant: Standard
  console-data/keymap/qwerty/lithuanian/standard/keymap: latin4
  console-data/keymap/azerty/belgian/variant: Standard
  console-data/keymap/qwerty/dutch/variant: Standard
  console-data/keymap/qwerty/estonian/standard/keymap: Standard
  console-data/keymap/azerty/french/with_euro__latin_15_/keymap: Standard
  console-

Bug#204976: marked as done (console-tools: changing to virtual terminal 7 makes the machine unusable)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 18:55:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line old 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)

--- Begin Message ---
Package: console-tools
Version: 1:0.2.3dbs-39
Severity: grave
Justification: causes non-serious data loss

When I change to virtual terminal 7, I get a blank screen with a cursor
and no login prompt. Then I can no longer control the machine (unless
it is connected to a network so that I can connect by ssh). Without a
network connection, the only solution seems to switch off the machine.

The virtual terminal shouldn't be changed if one can't do anything from
the new one.

-- System Information:
Debian Release: testing/unstable
Architecture: powerpc
Kernel: Linux ay 2.4.18-newpmac #1 Mon Jun 9 03:10:07 UTC 2003 ppc
Locale: LANG=C, LC_CTYPE=en_US.ISO8859-1

Versions of packages console-tools depends on:
ii  console-common 0.7.22Basic infrastructure for text cons
ii  debconf1.2.35Debian configuration management sy
ii  libc6  2.3.1-16  GNU C Library: Shared libraries an
ii  libconsole 1:0.2.3dbs-39 Shared libraries for Linux console
ii  sysvinit   2.85-4.1  System-V like init.

-- no debconf information

--- End Message ---
--- Begin Message ---
there are now newer reports against console usage in powerpc against
2.6, so assuming that your bug report got fixed inbetween.

you might want to test the latest Debian installer:
-> http://www.debian.org/devel/debian-installer/
daily builds will be soon switched to expected beta3 for etch.

thanks for your feedback.

-- 
maks
--- End Message ---

Bug#247391: marked as done (Kernel hangs when inserting airport module)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 19:03:19 +0200
with message-id <[EMAIL PROTECTED]>
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)

--- Begin Message ---
Package: installation-reports

Debian-installer-version: Beta4
uname -a: 
Date: 1500, 05/04/04
Method: sarge-powerpc-netinst.iso

Machine: Apple PowerMac G4
Processor: dual 867 G4
Memory: 512 MB
Root Device: 
Root Size/partition table: 
Output of lspci:

Base System Installation Checklist:

Initial boot worked:[]
Configure network HW:   []
Config network: [E]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Create file systems:[ ]
Mount partitions:   [ ]
Install base system:[ ]
Install boot loader:[ ]
Reboot: [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems: hangs on loading airport module, I do have a airport
card installed.  Works fine if airport card is removed.

--- End Message ---
--- Begin Message ---
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:
http://www.debian.org/devel/debian-installer/
the next beta 3 installer for Debian Etch is expected soon. :)

thanks for your feedback.

best regards

--
maks
--- End Message ---

Bug#217540: marked as done (kernel-patch-benh: weird patch behavior when combined with lowlatency patch)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 19:03:19 +0200
with message-id <[EMAIL PROTECTED]>
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)

--- Begin Message ---
Package: kernel-patch-benh
Version: 20031005
Severity: normal

I am trying to build a 2.4.22 kernel with the benh, lowlatency and
preempt patches. This results in a build error:

  make[4]: Entering directory `/usr/src/kernel-source-2.4.22/drivers/block'
  gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.22/include -Wall
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2
-fomit-frame-pointer -I/usr/src/kernel-source-2.4.22/arch/ppc
-fsigned-char -msoft-float -pipe -ffixed-r2 -Wno-uninitialized
-mmultiple -mstring   -nostdinc -iwithprefix include
-DKBUILD_BASENAME=ll_rw_blk  -DEXPORT_SYMTAB -c ll_rw_blk.c
  ll_rw_blk.c: In function `blkdev_release_request':
  ll_rw_blk.c:927: error: `rw' undeclared (first use in this function)
  ll_rw_blk.c:927: error: (Each undeclared identifier is reported only once
  ll_rw_blk.c:927: error: for each function it appears in.)
  ll_rw_blk.c:927: error: `bh' undeclared (first use in this function)
  ll_rw_blk.c:927: error: `count' undeclared (first use in this function)
  make[4]: *** [ll_rw_blk.o] Error 1
  make[4]: Leaving directory `/usr/src/kernel-source-2.4.22/drivers/block'
  make[3]: *** [first_rule] Error 2
  make[3]: Leaving directory `/usr/src/kernel-source-2.4.22/drivers/block'
  make[2]: *** [_subdir_block] Error 2
  make[2]: Leaving directory `/usr/src/kernel-source-2.4.22/drivers'
  make[1]: *** [_dir_drivers] Error 2
  make[1]: Leaving directory `/usr/src/kernel-source-2.4.22'
  make: *** [stamp-build] Error 2

Upon examining the patches, it appears that both the lowlatency and benh
patch include a patch for ll_rw_blk.c. The offending line is part of the
benh patch. However, it seems it was applied in completely the wrong
place. This could be caused by the fact that the lowlatency patch tries
to patch ll_rw_blk.c in exactly the same place.

The lines in the benh patch are:

  diff -Nur linux-2.4.22/drivers/block/ll_rw_blk.c 
linux-2.4-benh/drivers/block/ll_rw_blk.c
  --- linux-2.4.22/drivers/block/ll_rw_blk.c  2003-08-25 13:44:41.0 
+0200
  +++ linux-2.4-benh/drivers/block/ll_rw_blk.c2003-08-31 11:39:42.0 
+0200
  [snip]
  @@ -1302,6 +1316,9 @@
  kstat.pgpgin += count;
  break;
  }
  +
  +   if (block_dump)
  +   printk("%s: %s block %lu/%u on %s\n", current->comm, rw == 
WRITE ? "WRITE" : "READ", bh->b_rsector, count, kdevname(bh->b_rdev)); }

   
   /**

This patch ends up as lines 926-928, in a completely different function.

The lines in the lowlatency patch are:

  diff -pruN kernel-source-2.4.22.orig/drivers/block/ll_rw_blk.c 
kernel-source-2.4.22/drivers/block/ll_rw_blk.c
  --- kernel-source-2.4.22.orig/drivers/block/ll_rw_blk.c 2003-08-30 
02:01:36.0 -0400
  +++ kernel-source-2.4.22/drivers/block/ll_rw_blk.c  2003-09-17 
21:23:17.0 -0400
  @@ -1302,6 +1302,7 @@ void submit_bh(int rw, struct buffer_hea
  kstat.pgpgin += count;
  break;
  }
  +   conditional_schedule();
   }

Frankly, I have no idea how this happened, so I could be reporting this
to the wrong package.

-- System Information:
Debian Release: testing/unstable
Architecture: powerpc
Kernel: Linux pomme 2.4.20-ben10mvz2 #1 Thu May 8 16:10:24 CEST 2003 ppc
Locale: LANG=C, LC_CTYPE=C

Versions of packages kernel-patch-benh depends on:
ii  bash  2.05b-11   The GNU Bourne Again SHell
ii  grep-dctrl1.102  Grep Debian package information
ii  kernel-patch-scripts  0.99.28Scripts to help dealing with packa
ii  patch 2.5.9-1Apply a diff file to an original

-- no debconf information


--- End Message ---
--- Begin Message ---
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:
http://www.debi

Bug#120116: marked as done (base: [kernel-image-2.2.19] Attempting to install ltpc driver results in kernel panic)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 18:49:12 +0200
with message-id <[EMAIL PROTECTED]>
and subject line old 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)

--- Begin Message ---
Package: base
Version: N/A; reported 2001-11-18
Severity: normal

I was installing a recent boot-floppies version (3.0.17) on a PowerBase 150
powermac computer. I didn't know which network card it had, so I was just
trying a couple. When I tried the Farallon card, the kernel panic'd right
after displaying the message 'Attempting to load ltpc module, if your
computer stops responding...'. 

-- System Information
Debian Release: testing/unstable
Architecture: powerpc
Kernel: Linux Obsession 2.2.19 #1 Sat Apr 14 23:20:24 CDT 2001 ppc
Locale: LANG=C, LC_CTYPE=C


--- End Message ---
--- Begin Message ---
linux-2.6 has newer ltpc driver,
there for closing your bug report.

-- 
maks
--- End Message ---

Bug#330777: marked as done (kernel-patch-powerpc-2.4.27-11: "make dep" asks for "arch/ppc/appleboot" which does not excist)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 19:03:19 +0200
with message-id <[EMAIL PROTECTED]>
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)

--- Begin Message ---
Package: kernel-patch-powerpc-2.4.27-11
Version: 2.4.27-11
Severity: important

After "make menuconfig" I do "make dep" which stops because it needs 
"arch/ppc/appleboot" which does not excist.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.4.27
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

--- End Message ---
--- Begin Message ---
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:
http://www.debian.org/devel/debian-installer/
the next beta 3 installer for Debian Etch is expected soon. :)

thanks for your feedback.

best regards

--
maks
--- End Message ---

Bug#217778: marked as done (kernel-image-2.4.22-powerpc: CRT output doesn't work (when enabled by m3mirror))

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 18:55:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line old 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)

--- Begin Message ---
Package: kernel-image-2.4.22-powerpc
Version: 2.4.22-1
Severity: important

When I enable CRT output with m3mirror, instead of getting the same
data as on the LCD, I get the screen that appeared just before linux
booted (OF things, black characters on a white background).

There was no problem with the 2.4.18-newpmac kernel.

-- System Information:
Debian Release: testing/unstable
Architecture: powerpc
Kernel: Linux ay 2.4.18-newpmac #1 Mon Jun 9 03:10:07 UTC 2003 ppc
Locale: LANG=C, LC_CTYPE=en_US.ISO8859-1

-- no debconf information

--- End Message ---
--- Begin Message ---
there are now newer reports against console usage in powerpc against
2.6, so assuming that your bug report got fixed inbetween.

you might want to test the latest Debian installer:
-> http://www.debian.org/devel/debian-installer/
daily builds will be soon switched to expected beta3 for etch.

thanks for your feedback.

-- 
maks
--- End Message ---

Bug#380649: initramfs-tools: nfs options should comply with nfsroot.txt from linux documentation

[Vagrant Cascadian]

On Mon, Jul 31, 2006 at 06:40:45PM +0200, maximilian attems wrote:
> severity important
> stop

it is a feature request... though if you want to bloat it to important,
that's fine by me :)
 
> On Mon, Jul 31, 2006 at 08:36:15AM -0700, Vagrant Cascadian wrote:
> > Package: initramfs-tools
> > Severity: wishlist
> 
> please tell the version.

well, looking at the source code, it appears to be present in 0.73 and
all earlier versions i've seen...
 
> latest initramfs-tools in unstable uses mount from busybox.

which mount is used is somewhat irrelevent to this bug (though nfsmount
from klibc indeed appears buggy)...

the request of this bug is for initramfs-tools to parse /proc/cmdline
the same way (or as similar as possible) that the in-kernel nfsroot code
does.

> > it would be nice if the nfs kernel commandline boot options of
> > initramfs-tools supported the options found in the linux kernel
> > Documentation/nfsroot.txt, in the "kernel command line" section.
> > 
> > http://lxr.linux.no/source/Documentation/nfsroot.txt
> > 
> > particularly "root=/dev/nfs" as a means of enabling the NFS support,
> > rather than hacking a configuration file option, but also more complete
> > support for "nfsroot", and "ip".

so, instead of (or in addition to) implementing the "nfsopts"
parameter(as initramfs-tools does now), parsing the "nfsroot" parameter
the same way the kernel does:

  nfsroot=[:][,]
 
also, instead of having an option in initramfs.conf for BOOT=nfs, it
should just enable the NFS code when root=/dev/nfs is passed at the
kernel commandline (i.e. via the bootloader).

any options not defined should hopefully get grabbed by dhcp (or rarp or
bootp, if you're stuck with that for some odd reason), or use a "sane"
default.

does that clear up the request a bit?

> which cmdline are your using atm?

qemu's -append option, pxelinux.0 from syslinux, etherboot...

live well,
  vagrant


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Decision about oot-modules for etch

[Steve Langasek]

On Mon, Jul 31, 2006 at 12:46:09PM +0200, Daniel Baumann wrote:

> As stated in [1], there are though about to not allow other oot-modules
> in main outside of the conglomeration package for etch.

> [1] http://lists.debian.org/debian-kernel/2006/06/msg00441.html

I don't see anything of the sort stated there, and it's not the kernel
team's place to disallow such packages anyway.

> As discussed on IRC at the end of june with aba and HE, they are in
> favour to dropp those modules from the release-team point of view.

Sure, the release team is always in favor of strategies that make
maintenance easier.

>   * If no conglomeration package for contrib modules, will oot-modules
> of contrib be removed by the release-team for etch?

Why would they be unless they're broken at the time of release (i.e., built
for the wrong kernel)?

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


signature.asc
Description: Digital signature

Re: Decision about oot-modules for etch

[Daniel Baumann]

Steve Langasek wrote:
> I don't see anything of the sort stated there, and it's not the kernel
> team's place to disallow such packages anyway.

I asked waldi for explaining this 'unsupported idea' which svenl was
indicating in the mentioned mail. waldi explained me in that IRC
discussion at the end of june, that they (the kernel-team) will
recommend to RM to not allow other (oot?) modules for etch at all.
According to your answer, this seems not to have happened (already?).

Well, and my original mail has only the intention to get precise
information about those different things beeing said from different
persons wrt/ oot-modules in etch. I do that some time in advance so that
I will have time enough to react and adapt for having everything ready
for etch. Atm, I've the impression, that this is not taken as a serious
effort. After these few mails, I'm none the wiser now.

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  [EMAIL PROTECTED]
Internet:   http://people.panthera-systems.net/~daniel-baumann/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#380686: initramfs-tools: busybox mount doesn't support nfs

[Vagrant Cascadian]

Package: initramfs-tools
Version: 0.73
Severity: important

when setting BOOT=nfs and trying to boot, the nfs mount fails, because
busybox mount does not support nfs mounting (debian bug #348664:
busybox: consider CONFIG_NFSMOUNT)

this is what happens on boot:

IP-Config: eth0 complete (from 10.0.2.2):
 address: 10.0.2.15broadcast: 10.0.2.255   netmask: 255.255.255.0
 gateway: 10.0.2.2 dns0 : 10.0.2.3 dns1   : 0.0.0.0
 rootserver: 10.0.2.2 rootpath:
 filename  :
Begin: Running /scripts/nfs-premount ...
Done.
mount: Mounting 10.0.2.2:/opt/ltsp/i386 on /root failed: No such file or
directory
Begin: Running /scripts/nfs-bottom ...
Done.

i've manually verified that "busybox mount" behaves the same way if run
on a normal system (not from initramfs-tools).

when i try setting BUSYBOX=n in initramfs.conf, i get an ugly warning:

update-initramfs: Generating /boot/initrd.img-2.6.16-2-486
Warning: Busybox is required for successful boot!

is there any way around this (to get regular mount installed in the
initramfs)?

live well,
  vagrant

-- System Information:
Kernel: Linux 2.6.16-2-486

Versions of packages initramfs-tools depends on:
ii  busybox1.1.3-2Tiny utilities for 
small and embedded systems
ii  cpio   2.6-16 GNU cpio -- a program 
to manage archives of files
ii  klibc-utils1.4.11-3   small 
statically-linked utilities built with klibc
ii  module-init-tools  3.2.2-3tools for managing 
Linux kernel modules
ii  udev   0.093-1/dev/ and hotplug 
management daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processing of linux-2.6_2.6.17-5_m68k.changes

[Archive Administrator]

linux-2.6_2.6.17-5_m68k.changes uploaded successfully to localhost
along with the files:
  linux-headers-2.6.17-1-all_2.6.17-5_m68k.deb
  linux-headers-2.6.17-1-all-m68k_2.6.17-5_m68k.deb
  linux-headers-2.6.17-1_2.6.17-5_m68k.deb
  linux-image-2.6.17-1-amiga_2.6.17-5_m68k.deb
  linux-headers-2.6.17-1-amiga_2.6.17-5_m68k.deb
  linux-image-amiga_2.6.17-5_m68k.deb
  linux-image-2.6-amiga_2.6.17-5_m68k.deb
  linux-headers-2.6-amiga_2.6.17-5_m68k.deb
  linux-image-2.6.17-1-mac_2.6.17-5_m68k.deb
  linux-headers-2.6.17-1-mac_2.6.17-5_m68k.deb
  linux-image-mac_2.6.17-5_m68k.deb
  linux-image-2.6-mac_2.6.17-5_m68k.deb
  linux-headers-2.6-mac_2.6.17-5_m68k.deb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

linux-2.6_2.6.17-5_m68k.changes ACCEPTED

[Debian Installer]

Accepted:
linux-headers-2.6-amiga_2.6.17-5_m68k.deb
  to pool/main/l/linux-2.6/linux-headers-2.6-amiga_2.6.17-5_m68k.deb
linux-headers-2.6-mac_2.6.17-5_m68k.deb
  to pool/main/l/linux-2.6/linux-headers-2.6-mac_2.6.17-5_m68k.deb
linux-headers-2.6.17-1-all-m68k_2.6.17-5_m68k.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.17-1-all-m68k_2.6.17-5_m68k.deb
linux-headers-2.6.17-1-all_2.6.17-5_m68k.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.17-1-all_2.6.17-5_m68k.deb
linux-headers-2.6.17-1-amiga_2.6.17-5_m68k.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.17-1-amiga_2.6.17-5_m68k.deb
linux-headers-2.6.17-1-mac_2.6.17-5_m68k.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.17-1-mac_2.6.17-5_m68k.deb
linux-headers-2.6.17-1_2.6.17-5_m68k.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.17-1_2.6.17-5_m68k.deb
linux-image-2.6-amiga_2.6.17-5_m68k.deb
  to pool/main/l/linux-2.6/linux-image-2.6-amiga_2.6.17-5_m68k.deb
linux-image-2.6-mac_2.6.17-5_m68k.deb
  to pool/main/l/linux-2.6/linux-image-2.6-mac_2.6.17-5_m68k.deb
linux-image-2.6.17-1-amiga_2.6.17-5_m68k.deb
  to pool/main/l/linux-2.6/linux-image-2.6.17-1-amiga_2.6.17-5_m68k.deb
linux-image-2.6.17-1-mac_2.6.17-5_m68k.deb
  to pool/main/l/linux-2.6/linux-image-2.6.17-1-mac_2.6.17-5_m68k.deb
linux-image-amiga_2.6.17-5_m68k.deb
  to pool/main/l/linux-2.6/linux-image-amiga_2.6.17-5_m68k.deb
linux-image-mac_2.6.17-5_m68k.deb
  to pool/main/l/linux-2.6/linux-image-mac_2.6.17-5_m68k.deb


Override entries for your package:
linux-headers-2.6-amiga_2.6.17-5_m68k.deb - optional devel
linux-headers-2.6-mac_2.6.17-5_m68k.deb - optional devel
linux-headers-2.6.17-1-all-m68k_2.6.17-5_m68k.deb - optional devel
linux-headers-2.6.17-1-all_2.6.17-5_m68k.deb - optional devel
linux-headers-2.6.17-1-amiga_2.6.17-5_m68k.deb - optional devel
linux-headers-2.6.17-1-mac_2.6.17-5_m68k.deb - optional devel
linux-headers-2.6.17-1_2.6.17-5_m68k.deb - optional devel
linux-image-2.6-amiga_2.6.17-5_m68k.deb - optional base
linux-image-2.6-mac_2.6.17-5_m68k.deb - optional base
linux-image-2.6.17-1-amiga_2.6.17-5_m68k.deb - optional base
linux-image-2.6.17-1-mac_2.6.17-5_m68k.deb - optional base
linux-image-amiga_2.6.17-5_m68k.deb - optional base
linux-image-mac_2.6.17-5_m68k.deb - optional base



Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: reassign 343417 to linux-2.6

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.20
> reassign 343417 linux-2.6
Bug#343417: Several crashs in many machines.
Bug reassigned from package `kernel-image-2.4.27-nubus' to `linux-2.6'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#316025: marked as done (different bogomips on powerpc)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 19:03:19 +0200
with message-id <[EMAIL PROTECTED]>
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)

--- Begin Message ---

Package:debian-installer on powerpc
Severity: important

I'm used d-i floppy for powerpc (d-i/rc3) from 
http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy-2.4/

and a hade a different bogomips...

bogomips: 5.44 on installation time
bogomips:  Calibrating delay loop... 132.60 BogoMIPS  after 
installation



hardware-summary (power macintosh 4400/200)

info: /bin/report-hw: discover: ;;;Unknown;XF00D1 E;/dev/hdc
info: /bin/report-hw: discover: 8139too;;;Realtek Semiconductor Co., 
Ltd.;RTL-8139/8139C/8139C+;
info: /bin/report-hw: discover: ide-scsi;;;Linux;IDE-SCSI emulation 
layer;
info: /bin/report-hw: discover: ;;;Unknown;QUANTUM FIREBALL 
SE3.2A;/dev/hda

info: /bin/report-hw: discover: ;;;IBM;DDRS-39130;/dev/sda
error: /bin/report-hw: Unable to find lspci.
info: /bin/report-hw: /proc/pci: PCI devices found:
info: /bin/report-hw: /proc/pci:   Bus  0, device  11, function  0:
info: /bin/report-hw: /proc/pci: Host bridge: Apple Computer Inc. 
Bandit PowerPC host bridge (rev 3).

info: /bin/report-hw: /proc/pci:   IRQ 21.
info: /bin/report-hw: /proc/pci:   Master Capable.  Latency=32.  
info: /bin/report-hw: /proc/pci:   Bus  0, device  13, function  0:
info: /bin/report-hw: /proc/pci: Ethernet controller: Realtek 
Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 16).

info: /bin/report-hw: /proc/pci:   IRQ 23.
info: /bin/report-hw: /proc/pci:   Master Capable.  Latency=32.  
Min Gnt=32.Max Lat=64.

info: /bin/report-hw: /proc/pci:   I/O at 0x400 [0x4ff].
info: /bin/report-hw: /proc/pci:   Non-prefetchable 32 bit memory 
at 0x8080 [0x808000ff].

info: /bin/report-hw: /proc/pci:   Bus  0, device  16, function  0:
info: /bin/report-hw: /proc/pci: Class ff00: Apple Computer Inc. 
O'Hare I/O (rev 1).

info: /bin/report-hw: /proc/pci:   IRQ 21.
info: /bin/report-hw: /proc/pci:   Master Capable.  Latency=32.  
info: /bin/report-hw: /proc/pci:   Non-prefetchable 32 bit memory 
at 0xf300 [0xf307].

info: /bin/report-hw: /proc/pci:   Bus  0, device  17, function  0:
info: /bin/report-hw: /proc/pci: VGA compatible controller: ATI 
Technologies Inc 264VT [Mach64 VT] (rev 64).

info: /bin/report-hw: /proc/pci:   IRQ 22.
info: /bin/report-hw: /proc/pci:   Non-prefetchable 32 bit memory 
at 0x8100 [0x81ff].

info: /bin/report-hw: /proc/pci:   I/O at 0x1000 [0x10ff].
info: /bin/report-hw: /proc/bus/pci/devices: 0058106b000115


   
info: /bin/report-hw: /proc/bus/pci/devices: 006810ec813917
04018080
808101000100
00018139too
info: /bin/report-hw: /proc/bus/pci/devices: 0080106b000715
f300
0008
   
info: /bin/report-hw: /proc/bus/pci/devices: 00881002565416
81001001
01000100
0001   
info: /bin/report-hw: lsmod: Module  Size  Used by
Not tainted

info: /bin/report-hw: lsmod: xfs   454720   0 (unused)
info: /bin/report-hw: lsmod: reiserfs  231824   0 (unused)
info: /bin/report-hw: lsmod: jfs   162256   0 (unused)
info: /bin/report-hw: lsmod: ext3   69856   5
info: /bin/report-hw: lsmod: jbd46512   5 [ext3]
info: /bin/report-hw: lsmod: sd_mod 12592  14
info: /bin/report-hw: lsmod: isofs  26240   0
info: /bin/report-hw: lsmod: ide-cd 30704   0
info: /bin/report-hw: lsmod: cdrom  29472   0 [ide-cd]
info: /bin/report-hw: lsmod: ide-disk   17232   0
info: /bin/report-hw: lsmod: aec62xx 6528   0 (unused)
info: /bin/report-hw: lsmod: alim15x37920   0 (unused)
info: /bin/report-hw: lsmod: amd74xx11088   0 (u

Processed: reassign 328522 to linux-2.6

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.20
> reassign 328522 linux-2.6
Bug#328522: kernel-image-2.4.27-nubus: startup doesn't end in a login prompt 
but stays in a loop
Bug reassigned from package `kernel-image-2.4.27-nubus' to `linux-2.6'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#369760: Similar symptoms using miboot ofonlyboot floppy

[Rick Thomas]

Interestingly enough, I get similar results when booting from the  
miboot "ofonlyboot" floppy.


Even more interesting, when I use the miboot "boot" floppy the video  
is slightly strange (some columns flicker) but usable for installation.


Rick



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#163091: marked as done (card services cause kernel oops with any pcmcia card on PPC arch)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 19:03:19 +0200
with message-id <[EMAIL PROTECTED]>
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)

--- Begin Message ---
Package: kernel-image-2.4.19-powerpc
Version:  2.4.19-2

Hi

card services cause kernel oops with any pcmcia card on a Powerbook
Titanium.

This will probable be an upstream problem. This happens on kernel 2.4.18
as well.

related packages:

ii  bluez-pcmcia-s 2.0-release-1  PCMCIA support files for BlueZ 2.0
Bluetooth
ii  pcmcia-cs  3.2.1-1PCMCIA Card Services for Linux.


Dmesg puts out:


Memory BAT mapping: BAT2=256Mb, BAT3=128Mb, residual: 0Mb
Total memory = 384MB; using 2048kB for hash table (at c040)
Linux version 2.4.19-powerpc ([EMAIL PROTECTED]) (gcc version 2.95.4
20011002 (Debian prerelease)) #1 Mon Sep 9 09:01:43 EDT 2002
Found Uninorth memory controller & host bridge, revision: 8
Found a Keylargo mac-io controller, rev: 3, mapped at 0xfdf7f000
Processor NAP mode on idle enabled.
PowerMac motherboard: PowerBook Titanium
Found UniNorth PCI host bridge at 0xf000. Firmware bus number: 0->0
Found UniNorth PCI host bridge at 0xf200. Firmware bus number: 0->1
Found UniNorth PCI host bridge at 0xf400. Firmware bus number: 0->0
PMU driver 2 initialized for Core99, firmware: 0c
On node 0 totalpages: 98304
zone(0): 98304 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/hda6 ro 
PowerMac using OpenPIC irq controller
OpenPIC Version 1.2 (4 CPUs and 64 IRQ sources) at fc731000
OpenPIC timer frequency is 4.16 MHz
GMT Delta read from XPRAM: 120 minutes, DST: on
time_init: decrementer frequency = 24.966218 MHz
Console: colour dummy device 80x25
Calibrating delay loop... 797.90 BogoMIPS
Memory: 383644k available (1668k kernel code, 1008k data, 164k init, 0k
highmem)
AGP special page: 0xd7fff000
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
POSIX conformance testing by UNIFIX
PCI: Probing PCI hardware
Fixup res 1 (101) of dev 00:10.0: 400 -> 802400
Can't get bus-range for /[EMAIL PROTECTED]/[EMAIL PROTECTED]
PCI->OF bus map:
0 -> 0
1 -> 0
6 -> 0
PCI:00:10.0: Resource 0: b400-b7ff (f=1208)
PCI:00:10.0: Resource 2: b000-b0003fff (f=200)
PCI:01:17.0: Resource 0: 8000-8007 (f=200)
PCI:01:1a.0: Resource 0: a000-afff (f=200)
PCI:06:0f.0: Resource 0: f520-f53f (f=200)
PCI:00:10.0: Resource 1: 00802400-008024ff (f=101)
PCI:01:18.0: Resource 0: a0002000-a0002fff (f=200)
PCI:01:19.0: Resource 0: a0001000-a0001fff (f=200)
PCI:06:0e.0: Resource 0: f500-f5000fff (f=200)
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Thermal assist unit using timers, shrink_timer: 200 jiffies
Starting kswapd
VFS: Diskquotas version dquot_6.4.0 initialized
Journalled Block Device driver loaded
devfs: v1.12a (20020514) Richard Gooch ([EMAIL PROTECTED])
devfs: boot_options: 0x0
PCI: Enabling device 00:10.0 (0086 -> 0087)
aty128fb: Rage Mobility M3 (AGP) [chip rev 0x0] 8M 128-bit SDR SGRAM
(1:1)
Console: switching to colour frame buffer device 144x48
Registered "ati" backlight controller, level: 15/15
fb0: ATY Rage128 frame buffer device on PCI
no framebuffer address found for
/[EMAIL PROTECTED]/ATY,[EMAIL PROTECTED]/ATY,RageM3p12B
input0: Macintosh mouse button emulation
pty: 256 Unix98 ptys configured
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
pmac_ide: enabling IDE bus ID 2
pmac_ide: enabling IDE bus ID 0
pmac_ide: enabling IDE bus ID 1
hda: TOSHIBA MK2016GAP, ATA DISK drive
hdc: MATSHITADVD-ROM SR-8187, ATAPI CD/DVD-ROM drive
ide0 at 0xdc897000-0xdc897007,0xdc897160 on irq 19
ide1 at 0xdc89b000-0xdc89b007,0xdc89b160 on irq 20
hda: Enabling Ultra DMA 4
ide_pmac: Set UDMA timing for mode 4, reg: 0x0c50038c
hda: 39070080 sectors (20004 MB), CHS=38760/16/63, UDMA(66)
hdc: Enabling MultiWord DMA 2
ide_pmac: MDMA, cycleTime: 120, accessTime: 90, recTime: 30
ide_pmac: Set MDMA timing for mode 2, reg: 0x00011d26
hdc: ATAPI 46X DVD-ROM drive, 512kB Cache, (U)DMA
Uniform CD-ROM driver Revision: 3.12
Partition check:
 /dev/ide/host0/bus0/target0/lun0: [mac] p1 p2 p3 p4 p5 p6 p7
RAMDISK driver initialized

Bug#379647: linux-image-2.6.16-2-k7 shows the same behavior

[Joe Pfeiffer]

Package: linux-image-2.6.16-2-k7
Version: 2.6.16-17
Followup-For: Bug #379647

I'm seeing exactly the same behavior with 2.6.16-2-k7, also with a
Logitech cordless mouse.  2.6.15-1-k7 worked fine.

Here's the information requested of the
original reporter:

dpkg -l udev:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name   VersionDescription
+++-==-==-
ii  udev   0.093-1/dev/ and hotplug management daemon

lsmod:
Module  Size  Used by
radeon 96032  0 
drm62228  1 radeon
binfmt_misc10312  1 
nfsd  200772  13 
exportfs5248  1 nfsd
lockd  54248  2 nfsd
nfs_acl 3328  1 nfsd
sunrpc133476  9 nfsd,lockd,nfs_acl
autofs416836  2 
apm18476  1 
ipv6  218912  16 
dm_mod 48180  0 
evdev   8832  0 
shpchp 39424  0 
pci_hotplug24308  1 shpchp
i2c_amd756  6020  0 
i2c_core   19536  1 i2c_amd756
amd_k7_agp  8012  1 
agpgart29296  2 drm,amd_k7_agp
rtc11444  0 
snd_cmipci 30624  0 
gameport   13576  1 snd_cmipci
snd_pcm_oss44128  0 
snd_mixer_oss  15744  1 snd_pcm_oss
snd_pcm74504  2 snd_cmipci,snd_pcm_oss
snd_page_alloc  9864  1 snd_pcm
snd_opl3_lib9216  1 snd_cmipci
snd_timer  20420  2 snd_pcm,snd_opl3_lib
snd_hwdep   8580  1 snd_opl3_lib
snd_mpu401_uart 6656  1 snd_cmipci
snd_rawmidi22496  1 snd_mpu401_uart
snd_seq_device  8332  2 snd_opl3_lib,snd_rawmidi
snd46400  10 
snd_cmipci,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_opl3_lib,snd_timer,snd_hwdep,snd_mpu401_uart,snd_rawmidi,snd_seq_device
floppy 55916  0 
soundcore   8736  1 snd
pl2303 17028  0 
usbserial  28364  1 pl2303
pcspkr  3012  0 
psmouse34504  0 
serio_raw   6532  0 
usblp  12224  0 
parport_pc 31728  0 
parport32008  1 parport_pc
ext3  116872  1 
jbd47316  1 ext3
mbcache 7684  1 ext3
raid1  19520  1 
md_mod 64596  2 raid1
ide_generic 1216  0 [permanent]
ide_cd 35680  0 
cdrom  32240  1 ide_cd
ide_disk   14720  6 
generic 4228  0 [permanent]
usbhid 32416  0 
amd74xx12764  0 [permanent]
ide_core  111536  5 ide_generic,ide_cd,ide_disk,generic,amd74xx
ohci_hcd   17348  0 
usbcore   36  6 pl2303,usbserial,usblp,usbhid,ohci_hcd
8139too24384  0 
8139cp 19776  0 
mii 5248  2 8139too,8139cp
processor  21760  0 

And, just for grins, here's ls -R /dev/input
/dev/input:
by-id/
by-path/
event0
event1
event2

/dev/input/by-id:
usb-Logitech_USB_Receiver-event-kbd@
usb-Logitech_USB_Receiver-event-mouse@

/dev/input/by-path:
pci-:00:07.4-usb-0:1:1.0-event-kbd@
pci-:00:07.4-usb-0:1:1.1-event-mouse@
platform-pcspkr-event-spkr@

modprobe mousedev fixes it (and, of course, adding mousedev to
/etc/modules is a successful workaround)

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable'), (500, 
'oldstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.16-2-k7 depends on:
ii  initramfs-tools [linux-initra 0.72   tools for generating an initramfs
ii  module-init-tools 3.2.2-3tools for managing Linux kernel mo

Versions of packages linux-image-2.6.16-2-k7 recommends:
ii  libc6-i6862.3.6-15   GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.16-2-k7/preinst/elilo-initrd-2.6.16-2-k7: true
  linux-image-2.6.16-2-k7/preinst/failed-to-move-modules-2.6.16-2-k7:
  linux-image-2.6.16-2-k7/prerm/would-invalidate-boot-loader-2.6.16-2-k7: true
  linux-image-2.6.16-2-k7/preinst/already-running-this-2.6.16-2-k7:
  linux-image-2.6.16-2-k7/postinst/bootloader-error-2.6.16-2-k7:
  linux-image-2.6.16-2-k7/postinst/bootloader-test-error-2.6.16-2-k7:
  linux-image-2.6.16-2-k7/postinst/kimage-is-a-directory:
  linux-image-2.6.16-2-k7/preinst/bootloader-initrd-2.6.16-2-k7: true
  linux-image-2.6.16-2-k7/preinst/lilo-has-ramdisk:
  linux-image-2.6.16-2-k7/preinst

Bug#243254: marked as done (reiserfs root = kernel panic)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 19:03:19 +0200
with message-id <[EMAIL PROTECTED]>
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)

--- Begin Message ---
Package: installation-reports 
Debian-installer-version: 2004-04-11 
http://gluck.debian.org/cdimage/testing/sarge_d-i/powerpc/beta3/sarge-powerpc-netinst.iso
uname -a: Linux imac 2.4.25-powerpc #1 ven mar 19:29:26 CET 2004 ppc GNU/Linux
Date: 2004-04-12, very early morning
Method: Installed from bootable CD.  Installed base from CD.

Machine: Original iMac (ie Bondi Blue)
Processor: 233MHz, 740/750, pmac-generation: NewWorld
Memory: 160MB
Root Device: IDE (QUANTUM FIREBALL SE4.3A, ATA DISK drive)
Root Size/partition table:
4.3 GB hard disk partitioned as follows:
Apple partition map:63 sectors
Root partition: ~3.8GB
Swap partition: ~200MB

Output of lspci:
[ Email me if this is necessary.  I can't currently acquire this. ]

Base System Installation Checklist:

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[O]
Reboot: [E]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:

Reboot - Root partition was formatted ReiserFS.  On boot kernel panicked
because it could not mount root filesystem (this happened a couple of 
lines after it said cramfs: wrong magic).  A re-installation using ext3
on the root filesystem worked fine.


--- End Message ---
--- Begin Message ---
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:
http://www.debian.org/devel/debian-installer/
the next beta 3 installer for Debian Etch is expected soon. :)

thanks for your feedback.

best regards

--
maks
--- End Message ---

Re: Decision about oot-modules for etch

[Marco d'Itri]

In linux.debian.kernel Bastian Blank <[EMAIL PROTECTED]> wrote:

>> [2] The ipw drivers are in the kernel mainline (ipw3945 will hopefully
>> follow soon).
>Only if they remove the dependency on the binary-only deamon. I'm
>currently doing this for my own anyway.
Matthew Garrett has an almost working replacement for the daemon and
would be happy to get help.

-- 
ciao,
Marco


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#380693: hda: dma_timer_expiry

[antonio]

Package: linux-image-2.6.17-1-k7
Version: 2.6.17-4
Severity: important


Moving from 2.4 to 2.6 kernel results on errors like this:

hda: DMA timeout error
hda: dma timeout error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
hda: dma timeout error: status=0x84 { DriveStatusError BadCRC}
ide: failed opcode was: unknown

The system is frozen.
I have changed to other disk but still have DMA errors, so there is not
a hard disk issue. No errors got running a 2.4 kernel.

-- lspci:
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133]
(rev 03)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
(rev 40)
00:07.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1
Controller (rev 1a)
00:07.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1
Controller (rev 1a)
00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev
40)
00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686
AC97 Audio Controller (rev 50)
00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
01:00.0 VGA compatible controller: S3 Inc. 86c368 [Trio 3D/2X] (rev 02)


-- lspci -n
00:00.0 0600: 1106:0305 (rev 03)
00:01.0 0604: 1106:8305
00:07.0 0601: 1106:0686 (rev 40)
00:07.1 0101: 1106:0571 (rev 06)
00:07.2 0c03: 1106:3038 (rev 1a)
00:07.3 0c03: 1106:3038 (rev 1a)
00:07.4 0680: 1106:3057 (rev 40)
00:07.5 0401: 1106:3058 (rev 50)
00:0b.0 0200: 10ec:8139 (rev 10)
01:00.0 0300: 5333:8a13 (rev 02)

-- lsmod
Module  Size  Used byNot tainted
usb-uhci   22928   0  (unused)
usbcore62252   1  [usb-uhci]
via82cxxx_audio20956   0  (unused)
ac97_codec 13108   0  [via82cxxx_audio]
uart401 6404   0  [via82cxxx_audio]
sound  56552   0  [via82cxxx_audio uart401]
soundcore   3972   4  [via82cxxx_audio sound]
ide-scsi9904   0
scsi_mod   94628   1  [ide-scsi]
8139too14536   1
mii 2432   0  [8139too]
crc32   2880   0  [8139too]
parport_pc 23368   0
parport25768   0  [parport_pc]
agpgart45412   0  (unused)
dm-mod 46904   0  (unused)
ide-cd 31008   0
cdrom  29412   0  [ide-cd]
rtc 6376   0  (autoclean)
ext3   80044   2  (autoclean)
jbd41604   2  (autoclean) [ext3]
ide-detect   288   0  (autoclean) (unused)
via82cxxx  10504   1  (autoclean)
ide-disk   16640   3  (autoclean)
ide-core  107192   3  (autoclean) [ide-scsi ide-cd
ide-detect via82cxxx ide-disk]
unix   14832  25  (autoclean)

-- syslog info
Aug  1 00:20:35 arkhipov kernel: PCI: Using ACPI for IRQ routing
Aug  1 00:20:35 arkhipov kernel: PCI: If a device doesn't work, try
"pci=routeirq".  If it helps, post a report
Aug  1 00:20:35 arkhipov kernel: PCI: Bridge: :00:01.0
Aug  1 00:20:35 arkhipov kernel:   IO window: disabled.
Aug  1 00:20:35 arkhipov kernel:   MEM window: d400-dbff
Aug  1 00:20:35 arkhipov kernel:   PREFETCH window: 1000-100f
Aug  1 00:20:35 arkhipov kernel: PCI: Setting latency timer of device
:00:01
.0 to 64

[...]

Aug  1 00:20:35 arkhipov kernel: Uniform Multi-Platform E-IDE driver
Revision: 7.00alpha2
Aug  1 00:20:35 arkhipov kernel: ide: Assuming 33MHz system bus speed
for PIO modes; override with idebus=xx
Aug  1 00:20:35 arkhipov kernel: VP_IDE: IDE controller at PCI slot
:00:07.1
Aug  1 00:20:35 arkhipov kernel: PCI: VIA IRQ fixup for :00:07.1,
from 255 to 0
Aug  1 00:20:35 arkhipov kernel: VP_IDE: chipset revision 6
Aug  1 00:20:35 arkhipov kernel: VP_IDE: not 100%% native mode: will
probe irqs later
Aug  1 00:20:35 arkhipov kernel: VP_IDE: VIA vt82c686b (rev 40) IDE
UDMA100 controller on pci:00:07.1
Aug  1 00:20:35 arkhipov kernel: ide0: BM-DMA at 0xd000-0xd007, BIOS
settings: hda:DMA, hdb:DMA
Aug  1 00:20:35 arkhipov kernel: ide1: BM-DMA at 0xd008-0xd00f, BIOS
settings: hdc:DMA, hdd:pio
Aug  1 00:20:35 arkhipov kernel: Probing IDE interface ide0...
Aug  1 00:20:35 arkhipov kernel: USB Universal Host Controller Interface
driverv3.0
Aug  1 00:20:35 arkhipov kernel: hda: SAMSUNG SV1296D, ATA DISK drive
Aug  1 00:20:35 arkhipov kernel: hdb: RW-201040, ATAPI CD/DVD-ROM drive
Aug  1 00:20:35 arkhipov kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Aug  1 00:20:35 arkhipov kernel: Probing IDE interface ide1...
ug  1 00:20:35 arkhipov kernel: hdc: ST3120022A, ATA DISK drive
Aug  1 00:20:35 arkhipov kernel: ide1 at 0x170-0x177,0x376 on irq 15
Aug  1 00:20:35 arkhipov kernel: ACPI: PCI Interrupt Link [LNKD] enabled
at IRQ10
Aug  1 00:20:35 arkhip

Bug#369314: Addendum: Latest linux-image-2.6.16-2-powerpc-miboot fixed this

[alemc . 2]

Just to add, the combination of the latest quik (0.0.15) *with* the latest 
linux-image-2.6.16-2-powerpc-miboot fixed the bug.

-- 
GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C
And that's my crabbing done for the day.  Got it out of the way early, 
now I have the rest of the afternoon to sniff fragrant tea-roses or 
strangle cute bunnies or something.   -- Michael Devore


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#306805: marked as done (kernel-image-2.4.27-nubus cannot install because of wrong file name)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2006 19:03:19 +0200
with message-id <[EMAIL PROTECTED]>
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)

--- Begin Message ---
Package: kernel-image-2.4.27-nubus
Version: 2.4.27-4
Severity: normal


dpkg error in the subprocess post-installation because this script looks
for /boot/vmlinux-2.4.27-nubus where the actual file contained in the
packet is /boot/vmlinuz-2.4.27-nubus

doing a
mv /boot/vmlinuz-2.4.27-nubus /boot/vmlinux-2.4.27-nubus
solves the installation but a cleaner package would be nice.


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Kernel: Linux 2.4.26-nubus
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=locale: Cannot set 
LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)

-- debconf information excluded

--- End Message ---
--- Begin Message ---
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:
http://www.debian.org/devel/debian-installer/
the next beta 3 installer for Debian Etch is expected soon. :)

thanks for your feedback.

best regards

--
maks
--- End Message ---

Bug#380649: initramfs-tools: patches for root=/dev/nfs and full "nfsroot=" support

[Vagrant Cascadian]

Package: initramfs-tools
Version: 0.73
Followup-For: Bug #380649

i implemented some initial patches in a bzr branch for "root=/dev/nfs"
as well as more complete support for "nfsroot".

http://llama.freegeek.org/~vagrant/bzr-archives/initramfs-tools/vagrant-initramfs-tools

i'll try and work on implementing the "ip=" option as well in the same
branch.

live well,
  vagrant


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#379647: Info received (linux-image-2.6.16-2-k7 shows the same behavior)

[Joe Pfeiffer]

maximilian attems <[EMAIL PROTECTED]> Suggested the following to fix
this:

> upgrade to latest udev than all the input is loaded!

udev 0.093-1 *is* the latest version in Debian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

ir-kbd-gpio.ko missing from kernel images

[David Shepherd]

Hi All

I'm trying to get the infra-red remote control working on my MythTV box
and can't find the correct module (ir-kbd-gpio)

So, can anyone tell me where I can find, or how I can compile the
ir-kbd-gpio.ko module. 

The module is part of the bttv video4linux driver but the ir-kbd-gpio.c
source file seems to be missing from the kernel source tree and the
module is not part of the debian kernel images.

The bttv 0.9.15 source tar (linux.bytesex.org) contains the file so I
guess I could just to compile the module from that but I'd prefer to do
it in a more Debian way if possible.

Newbie disclaimer: I've built my own nvidia module and compiled the
kernel once so I can follow instructions but I'm no guru.

Thanks in advance
Dave



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

usplash_0.3c_i386.changes ACCEPTED

[Debian Installer]

Accepted:
usplash_0.3c.dsc
  to pool/main/u/usplash/usplash_0.3c.dsc
usplash_0.3c.tar.gz
  to pool/main/u/usplash/usplash_0.3c.tar.gz
usplash_0.3c_i386.deb
  to pool/main/u/usplash/usplash_0.3c_i386.deb


Override entries for your package:
usplash_0.3c.dsc - source misc
usplash_0.3c_i386.deb - optional misc

Announcing to debian-devel-changes@lists.debian.org
Closing bugs: 380618 


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processing of usplash_0.3c_i386.changes

[Archive Administrator]

usplash_0.3c_i386.changes uploaded successfully to localhost
along with the files:
  usplash_0.3c.dsc
  usplash_0.3c.tar.gz
  usplash_0.3c_i386.deb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

unsubscribe

[Lord Steve Ataucuri Cruz]

On 8/1/06, Debian Installer <[EMAIL PROTECTED]> wrote:


Accepted:
usplash_0.3c.dsc
  to pool/main/u/usplash/usplash_0.3c.dsc
usplash_0.3c.tar.gz
  to pool/main/u/usplash/usplash_0.3c.tar.gz
usplash_0.3c_i386.deb
  to pool/main/u/usplash/usplash_0.3c_i386.deb


Override entries for your package:
usplash_0.3c.dsc - source misc
usplash_0.3c_i386.deb - optional misc

Announcing to debian-devel-changes@lists.debian.org
Closing bugs: 380618


Thank you for your contribution to Debian.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]