Re: Bug#382129: Beta3 won't boot on OldWorld PowerPC Mac
Hi, On Friday 18 August 2006 22:49, Aurélien GÉRÔME wrote: > On Fri, Aug 18, 2006 at 02:56:52PM -0400, Rick Thomas wrote: > > Do you think it will be ready for inclusion in etch at release time? > Hard to say, since Piotr and I have no deadline... :) I'm not sure what you mean by this. If you mean, you and Piotr only work on this with low priority, I cannot say anything except "a pity" :) If you mean, you don't know the deadline to get it into etch, I can help: According to http://lists.debian.org/debian-devel-announce/2006/08/msg5.html the final build for d-i will be on October the 18th. So, your deadline is in two or three weeks I would say (if your changes are non-intrusive...), so that we have time for testing and integrating. So, to summarize: be quick, if you want this in etch. I'm happy to assist in testing, writing documentation and commiting tested stuff to the svn (in cooperation with Frans.) And kudos for your efforts to free miboot and make it work on harddrives! regards, Holger pgpRQwQjVMyeG.pgp Description: PGP signature
Re: Quik and atyfb
Hi, On Friday 11 August 2006 09:33, Simon Stapleton wrote: > On 10 Aug 2006, at 22:19, Holger Levsen wrote: > Yes, just using video=atyfb causes the same issue. There is a > difference somewhere in the way quik configures stuff and the way > BootX/miBoot do it, using video=atyfb (+ all the various gubbins) > from a BootX / miBoot boot works fine and gives you accelerated > video, the same from a quik boot results in garbage. > > It's a bit of a pain, to be frank, but I don't currently have the > time to delve into the source of both to see what is happening. Some more information from a private disucssion on IRC, p2-mate is the quik maintainer: Aug 11 10:12:16 p2-mate, have you seen http://lists.debian.org/debian-powerpc/2006/08/msg00073.html ? Aug 11 10:13:43 p2-mate, re: that mail: i'll ask the guy to file a bug against quik? Aug 11 10:14:08h01ger: no Aug 11 10:14:13it's not a quik bug Aug 11 10:14:33it's probably because macos inits the aty card in a different way then OF does Aug 11 10:14:52there is very little I can do against that I'm afraid Aug 11 10:16:05I think the proper solution is to fix atyfb Aug 11 10:16:09 ah Aug 11 10:16:55both miboot and bootx cause macos to init the gfx hardware Aug 11 10:18:05 so there are circumstances where bootx is a better choice then quik? Aug 11 10:19:40it causes more hw to be initialized by macos yes Aug 11 10:19:51personally I don't like bootx at all Aug 11 10:20:16it makes for horrible boottimes regards, Holger pgp3GpBDJdxTR.pgp Description: PGP signature
Re: Bug#382129: Beta3 won't boot on OldWorld PowerPC Mac
Hi Aurélien,
please don't cc: me - I'm subscribed to both lists, it's against the mailing
lists code of conduct (something you agree on when joining debian..) and it's
annoying. Thanks.
On Saturday 19 August 2006 14:05, Aurélien GÉRÔME wrote:
> > I'm not sure what you mean by this. If you mean, you and Piotr only work
> > on this with low priority, I cannot say anything except "a pity" :)
> I did not mean it is low priority. ;) I meant we are not paid
> Canonical employees to do a job following a timeline.
Ahh.
> And frankly, come one... miBoot is 10 years old inactive software,
> so I think there is no hurry.
That's right. But also machines, for which miboot is useful, are also at least
10 years old and get less useful each day^wmonth.
> On a side note, I am also fscked up in
> NM without even starting, because someone in the Front Desk seems to
> dislike me, even though I maintain 11 packages in Debian, so there
> is really no hurry...
I don't see, what this has to do with it.
But anyway, you're only waiting for an advocate for five weeks and the number
of AMs is lower than the number of people in NM - so this is quite natural.
That said, I dont understand the comment on your application ("on hold until
2006-11 waiting for visible activity") either, if you maintain 11 packages in
debian :-) Did you ask Myon why he made that comment?
> > If you mean, you don't know the deadline to get it into etch, I can help:
> > According to
> > http://lists.debian.org/debian-devel-announce/2006/08/msg5.html the
> > final build for d-i will be on October the 18th. So, your deadline is in
> > two or three weeks I would say (if your changes are non-intrusive...), so
> > that we have time for testing and integrating.
> It is really not enough time... :(
Pity. But sometimes wonders happen :)
> I asked Christian Perrier to add my account to the d-i Alioth project
> to work on miboot targets and miboot-installer.
You don't need an account to do the work. The svn allows anonymous checkouts,
so you can work on it and provide patches, which other people will hapily
commit (with crediting you) if they work. I very certainly would/will.
> I am also really afraid to interact with Frans, because I would rather
> not be treated as dipshit like Sven was. :(
Frans is a nice guy. Just don't constantly throw dipshit like Sven did and
neither Frans nor anybody else will treat you badly.
(Sven is a nice guy, too. But... ...I'm tired of this discussion so I wont go
into more detail here. I feel I've said too much already.)
> Thanks and cheers,
to you too!
Holger
pgpzUqAIBJD8e.pgp
Description: PGP signature
Re: Bug#382129: Beta3 won't boot on OldWorld PowerPC Mac
Hi,
On Saturday 19 August 2006 16:17, Aurélien GÉRÔME wrote:
> Sure, no problem and I apologise, which leads me to: how would I know
> you are subscribed? ;)
Thanks for caring! :)
Of course you cannot know if someone is subscribed. But you can know that the
default is not to cc: people and assume they're either subscribed or read via
the web-interface, are subscribed to the bugs or whatever. The list policy
is, that people who want cc:s ask, and that the rest doesnt want cc:s.
If you really really want the sender to be notified, bcc: works better. This
way, at least that person isn't cc:ed on all following replies.
> > > And frankly, come one... miBoot is 10 years old inactive software,
> > > so I think there is no hurry.
> >
> > That's right. But also machines, for which miboot is useful, are also at
> > least 10 years old and get less useful each day^wmonth.
>
> I did not say the contrary, but I will *not* work under pressure
> from someone I do not work for.
I fail to see what this has to do with anything mentioned above. Noone wants
to work under pressure, especially in a volunteer project.
> > > On a side note, I am also fscked up in
> > > NM without even starting, because someone in the Front Desk seems to
> > > dislike me, even though I maintain 11 packages in Debian, so there
> > > is really no hurry...
> > I don't see, what this has to do with it.
> How would I put it? Lack of motivation, be considered as nothing,
> etc...
I understand, but...
> > But anyway, you're only waiting for an advocate for five weeks and the
> > number of AMs is lower than the number of people in NM - so this is quite
> > natural.
> No, I am not, I am stalled in NM by Christoph Berg.
from your reply (and Frans too) it seems you haven't asked Christoph if he's
willing to reevalute the sitation or how he came to that conclusion in the
first place.
Because, the procedure you're in is new, checking if NMs have done any work
before, has only been done like this since very recently. So if you would
have given feedback, maybe the form-mail can be improved - I guess it says
something like "we've put you on hold, please inform us if you think this is
not correct or not correct anymore" - but maybe the last sentence is missing
or whatever.
But, whining doesnt help for sure. Especially in an unrelated thread. It is
much more likely to bring you into a bad light then to actually change that
situation.
> > That said, I dont understand the comment on your application ("on hold
> > until 2006-11 waiting for visible activity") either, if you maintain 11
> > packages in debian :-) Did you ask Myon why he made that comment?
>
> Because there is no so-called "visible activity" of me on
> mailing-lists, on Google, and on the BTS... I still fail to see why
> I cannot be in the state "waiting for AM" which I would be satisfied
> with if it was the case...
Disclaimer: I'm in NM myself too :) But as said before: if only you had asked
instead of complaining. I guess the answer is simple: the distinction is
done, to make Frontdesk life easier: NMs marked "on hold" and "waiting for
AM" are both waiting for AM, only that those on hold are not ready yet. (And
thus don't need to be considered when a spare ressource, an AM, becomes
available.)
If Christoph would have thought you're not suited (yet) to become a DD you
would have got the status "rejected". But you're on hold and you've picked up
packages since then. Whooohoo! Tell that to frontdesk, instead of
complaining!!
As said: this is a more or less educated guess.
> > > I asked Christian Perrier to add my account to the d-i Alioth project
> > > to work on miboot targets and miboot-installer.
> > You don't need an account to do the work. The svn allows anonymous
> > checkouts, so you can work on it and provide patches, which other people
> > will hapily commit (with crediting you) if they work. I very certainly
> > would/will.
> Oh, come on, I hope you will not ask me to send patches like a dog
> following his master, as d-i people did with Sven...
Oh come on, do you really think you made a good impression with that comment.
I would say the opposite is true :(
> They are 149 d-i
> members, why can it not be 150?
Most all of them sent many patches before they got commit access. There are
exceptions, but the general rule is like this. To give one prominent example:
g-i was pretty usable before the first commit to svn was allowed.
> OK, thanks to put it that way, so I am awaiting an account to work
> on miBoot support in Debian Installer.
Don't just wait. Do useful work and you will see people will come to you,
asking you to join. But without evidence, that a.) you work well and b.) you
work well in this team, it's quite unlikely you will get access just because
you asked.
Or you might explain what you could do with svn _write_ access what you cannot
do now. But I asked you that in the previous mail already :) If you need help
with building d-
Fwd: Debian Edu for powerpc ready for testing
Hi, as I'm away from powerpc machines for the next two weeks I would be happy for testers, too... regards, Holger -- Forwarded Message -- Subject: Debian Edu for powerpc ready for testing Date: Thursday 21 September 2006 00:51 From: Petter Reinholdtsen <[EMAIL PROTECTED]> To: debian-edu@lists.debian.org Thanks to the work of Holger and with some help from me, there are now automatically build powerpc test CDs for Debian Edu. Currently only for the etch-test profile. The CD images are available from ftp://ftp.skolelinux.org/cd-etch-test-powerpc/>. rsync should work too, use something like this to download it: rsync -vt \ ftp.skolelinux.no::skolelinux-etch-test-powerpc/debian-edu-powerpc-binary-1. raw \ debian-edu-powerpc-binary-1.raw I have no idea if it boots, nor if it installs. Feedback is most welcome. :) Friendly, -- Petter Reinholdtsen pgpe0JypsyVYM.pgp Description: PGP signature
Re: miboot
Hi, On Tuesday 26 September 2006 12:27, Sven Luther wrote: > On Tue, Sep 26, 2006 at 11:42:13AM +1000, Benjamin Herrenschmidt wrote: > > It's to be noted that the miboot images generated by the kernel are > > busted and have been so for a lng time (possibly most of 2.6.x). We > > found that only recently. > Indeed, but the debian miboot images where done by hand (usinz gzip and > stuff). Is that fixed now? > > That should fix it: > He, neat, i will integrate this in mkvmlinuz :) Did you? regards, Holger (trying to track those fixes) pgp6mAXSJBLCu.pgp Description: PGP signature
boot failure on powerpc newworld, imac g3
Hi, this didn't make it to the lists, but it's in the bts as #394209, please reply to [EMAIL PROTECTED] - thanks. Package: installation-reports severity: important Boot method: netinstall-cd and netboot-cd images Image version: 2006-10-19 from http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/powerpc/iso-cd/debian-testing-powerpc-netinst.iso and http://people.debian.org/~wouter/d-i/powerpc/daily/ (this one being the latest, built on the 19th, 22:53) plus beta3 and beta2 Date: 2006-10-19, 2006-10-20 Machine: imac g3, tray-loading cd R32)> processor : 0 cpu : 740/750 clock : 233MHz revision: 2.2 (pvr 0008 0202) machine : iMac,1 motherboard : iMac MacRISC Power Macintosh detected as : 65 (iMac (first generation)) pmac flags : L2 cache: 512K unified memory : 32MB pmac-generation : NewWorld /dev/hda #type namelength base ( size ) system /dev/hda1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hda2 Apple_Bootstrap bootstrap 1600 @ 64 (800.0k) NewWorld bootblock /dev/hda3 Apple_Bootstrap linux 7782400 @ 1664 ( 3.7G) NewWorld bootblock /dev/hda4 Apple_UNIX_SVR2 swap634752 @ 7784064 (309.9M) Linux swap Block size=512, Number of Blocks=8418816 DeviceType=0x0, DeviceId=0x0 Output of lspci and lspci -n: 00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) 00:10.0 Class ff00: Apple Computer Inc. Paddington Mac I/O 00:12.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC 215IIC [Mach64 GT IIC] (rev 3a) 00:14.0 USB Controller: OPTi Inc. 82C861 (rev 10) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[E] Configure network HW: [ ] Config network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: beta2 (and the sarge installer) work well, but neither the dailies nor beta3 boots. Screenshots attached. (Both are after selecting install, expert or rescue.) The dailys fail with: RAMDISK: Compressed image found at block 0 RAMDISK: ran out of compressed data Invalid compressed format (err=1) No filesystem could mount root, tried: cramfs Kernel panic - not syncing: VFS: Unable to mount roos fs on unknown-block(1,0) I'm not making this serious atm, as I have seen beta3 booting successfully on a g4 powerbook... BTW, booting fails slightly different, after uprading a sarge system to etch, no matter if I use a 2.6.17 (from etch) or .18 kernel (from sid). Screenshot also attached. regards, Holger [beta3.png (image/png, attachment)] http://bugs.debian.org/cgi-bin/bugreport.cgi/beta3.png?bug=394209;msg=5;att=1 [daily.png (image/png, attachment)] http://bugs.debian.org/cgi-bin/bugreport.cgi/daily.png?bug=394209;msg=5;att=2 [etch-upgrade.png (image/png, attachment)] http://bugs.debian.org/cgi-bin/bugreport.cgi/daily.png?bug=394209;msg=5;att=3 pgpamvL0a3Fc5.pgp Description: PGP signature
Re: old world nonsense, please rectify
Hi, On Sunday 22 October 2006 10:20, Benjamin Herrenschmidt wrote: > What is the exact problem ? I'm pretty sure I had 2.6.18 booting fine on > a couple of oldworld boxes here before relase. (A fix for IDE on some > performa went in later on, I think in 2.6.18.1) The problem I see here (even on newworld), is that 32mb is too little memory for kernel (4.3mb) plus initrd (5mb, both compressed sizes). regards, Holger pgprgMpNlwa1g.pgp Description: PGP signature
Re: bug#390432 - still no boot 2.6.18 here
Hi, On Monday 23 October 2006 12:01, Brian Morris wrote: > well i tried again, still same result as ever trying > to boot 2.6.18 on my old powerbook. how much memory do you have? regards, Holger pgp4Xlo2S183e.pgp Description: PGP signature
Re: old world nonsense, please rectify
Hi, On Sunday 22 October 2006 13:54, Sven Luther wrote: > 1) using yaird instead of initramfs-tools, or initramfs-tools with the > modules=dep option. initramfs-tools with the dep option didnt help. I now added more memory and that helped :) From experiementing with "mem=xM" append parameter I learned that 40mb is sufficient, while 32mb is not. regards, Holger pgpppMyHiGLEF.pgp Description: PGP signature
Re: old world nonsense, please rectify
Hi, On Monday 30 October 2006 17:16, you wrote: > Mmm, are you able to boot d-i with 32MB on this box ? No. regards, Holger pgpnFJg8GsQsz.pgp Description: PGP signature
Re: acroread
Hi, On Tuesday 07 November 2006 14:01, Eddy Petrișor wrote: > > What can you do with acroread that would not work with kdpf for example ? > Form templates. Can you please point out a pdf (or create one), so that we can open bugs against the pdf-viewers in debian? regards, Holger pgpZEI6vJYTW4.pgp Description: PGP signature
Re: acroread
Hi Wolfram, On Tuesday 07 November 2006 17:27, Wolfram Quester wrote: > In this case there is a bug report: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=317984 Ah, thanks. I also filed a bug against poppler now (#397590), so that this is on the radar of other pdf viewers as well. > It was forwarded to kde's BTS and there there are example files. Yup, two years ago and nothing happened :( regards, Holger pgpA2q3QACb0k.pgp Description: PGP signature
which serious bugs exactly? (Re: if you care about debian on powerpc, please react ...)
Hi, summary for powerpc-users: _if_ you have serious problems with debian-powerpc working on your machine(s), please report them to the bug tracking system, so we can fix them. If you don't know how (or need a bit help), I'm glad to help on this. http://bugs.debian.org is a good starting point :) I'm not interesting in this thread. Read the full mail to see why. On Wednesday 22 November 2006 18:00, Sven Luther wrote: > As some of you may have noticed, there is an ugly dispute going on between > some few d-i team members (Frans Pop and Joey Hess mostly, but Geert and > Holger also seem to support them), and which result in a over 6 month old > dispute Sven, the dispute is much older. I'm too lazy to dig it up now, but I would say it's about and at least 18-24 month old (but you only see your svn-commit rights and think it started when they where removed. The dispute did not start when they where removed, this was only one climax.). And you're behaviour of claiming to let it rest and then writing tens (!) of mails to various lists certainly didn't help at all to let the issue settle. For the sake of the users of the powerpc-port I'll quote here what I replied to your mail to debian-release on this wednesday about the same issue. And, I will not participate in this topic/thread anymore, as I seriously think this is a waste of time and I prefer to instead work on debian, including debian powerpc. And I have to admit, that in the last two or three month I often refrained from working on debian-ppc, because you, Sven, have too often killed my motivation to work on it. (I work mostly (but not completly on debian-edu/ppc now...) So please stop this. Either fork d-i (or debian/ppc) or _work_ on patches and bugreports instead of wasting our time trying to "solve" this situation, which according to you can only be "solved" by giving you svn-commit-rights back, which doesn't work, if the people maintaining the debian-installer doesn't want to work with you. Debian is a volunteer project and you cannot force people to work with you, no matter what. If you would have worked (as I suggested to you in June (or July?) this year) on patches and bugreports and not continuesly ranted and insulted the people who cannot work with you (which you have done on >5 lists and by writing (estimated) 40% of all mails in those threads), because you rant and insult so much, and would have the commit right issue rested, the situation would have calmed down by now. Maybe not enough to get the commit rights (now), but as you haven't done this, *you* have worsen the chances to get them back sooner than later. My mail to debian-release on thursday: begin On Wednesday 22 November 2006 18:22, Sven Luther wrote: > I know that you maybe defavorably biased against me in the petty dispute > between me and frans and joeyh some unnamed others, over the powerpc port > of d-i. > > But, we are nearing the release, and the actions of Frans are clearly > endangering the quality of the d-i powerpc port, and there is a decision to > take about this issue, and i guess the decision is yours to make. I'm sad you don't stick to your promise which you wrote down on at http://wiki.debian.org/DebianInstaller/FransPopAndOthersVs.SvenLutherIssue/ etc.: "I propose we meet at fosdem, and discuss the dispute then. Until then, i will consider that the dispute is solved and relations have normalized, and will continue to work through the BTS for patches and stuff. I will try to not go balistic if you reply provocatively, but i can't promise i will always be able to do so, just as you probably cannot promise me you will never be provocative again. In any case, until fosdem, there is ample time to reflect on this issue, but i hope you will find that restoring the commit access by then will be acceptable. So, unless during that face to face meeting something goes very wrong, i consider the case closed, and wish you good luck with your upcoming trip." > 1) We drop support for powerpc for etch. Why exactly? On http://wiki.debian.org/DebianInstaller/EtchRC1Prep I only see rather minor issues regardings powerpc (btw, I think that declaring which subarchs are broken would help. But the powerpc subarch with the biggest userbase, newworld, works just fine (IMEs).) http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED];include=powerpc lists 4 important bugs, but no serious ones. And http://wiki.debian.org/powerpcEtchReleaseRecertification lists six d-developers, and not only you, Sven. And on http://release.debian.org/etch_arch_qualify.html powerpc is one of the five archs (out of 12) which only "green" fields. So I would say, the powerpc-port is in a pretty good shape overall. If you have other indications, please file them with the appropriate severity in the BTS or stop spreading fear, uncertainty and doubt. Thanks. regards, Holger (who seriously asks himself why I even took the time to answer this.
which serious bugs exactly? (Re: if you care about debian on powerpc, please react ...)
Hi, summary for powerpc-users: _if_ you have serious problems with debian-powerpc working on your machine(s), please report them to the bug tracking system, so we can fix them. If you don't know how (or need a bit help), I'm glad to help on this. http://bugs.debian.org is a good starting point :) I'm not interesting in this thread. Read the full mail to see why. (If you only care about the technical details, you might skip the first paragraphs and start after the begin line below...) On Wednesday 22 November 2006 18:00, Sven Luther wrote: > As some of you may have noticed, there is an ugly dispute going on between > some few d-i team members (Frans Pop and Joey Hess mostly, but Geert and > Holger also seem to support them), and which result in a over 6 month old > dispute Sven, the dispute is much older. I'm too lazy to dig it up now, but I would say it's about and at least 18-24 month old (but you only see your svn-commit rights and think it started when they where removed. The dispute did not start when they where removed, this was only one climax.). And you're behaviour of claiming to let it rest and then writing tens (!) of mails to various lists certainly didn't help at all to let the issue settle. For the sake of the users of the powerpc-port I'll quote here what I replied to your mail to debian-release on this wednesday about the same issue. And, I will not participate in this topic/thread anymore, as I seriously think this is a waste of time and I prefer to instead work on debian, including debian powerpc. And I have to admit, that in the last two or three month I often refrained from working on debian-ppc, because you, Sven, have too often killed my motivation to work on it. (I work mostly (but not completly on debian-edu/ppc now...) So please stop this. Either fork d-i (or debian/ppc) or _work_ on patches and bugreports instead of wasting our time trying to "solve" this situation, which according to you can only be "solved" by giving you svn-commit-rights back, which doesn't work, if the people maintaining the debian-installer doesn't want to work with you. Debian is a volunteer project and you cannot force people to work with you, no matter what. If you would have worked (as I suggested to you in June (or July?) this year) on patches and bugreports and not continuesly ranted and insulted the people who cannot work with you (which you have done on >5 lists and by writing (estimated) 40% of all mails in those threads), because you rant and insult so much, and would have the commit right issue rested, the situation would have calmed down by now. Maybe not enough to get the commit rights (now), but as you haven't done this, *you* have worsen the chances to get them back sooner than later. My mail to debian-release on thursday: begin On Wednesday 22 November 2006 18:22, Sven Luther wrote: > I know that you maybe defavorably biased against me in the petty dispute > between me and frans and joeyh some unnamed others, over the powerpc port > of d-i. > > But, we are nearing the release, and the actions of Frans are clearly > endangering the quality of the d-i powerpc port, and there is a decision to > take about this issue, and i guess the decision is yours to make. I'm sad you don't stick to your promise which you wrote down on at http://wiki.debian.org/DebianInstaller/FransPopAndOthersVs.SvenLutherIssue/ etc.: "I propose we meet at fosdem, and discuss the dispute then. Until then, i will consider that the dispute is solved and relations have normalized, and will continue to work through the BTS for patches and stuff. I will try to not go balistic if you reply provocatively, but i can't promise i will always be able to do so, just as you probably cannot promise me you will never be provocative again. In any case, until fosdem, there is ample time to reflect on this issue, but i hope you will find that restoring the commit access by then will be acceptable. So, unless during that face to face meeting something goes very wrong, i consider the case closed, and wish you good luck with your upcoming trip." > 1) We drop support for powerpc for etch. Why exactly? On http://wiki.debian.org/DebianInstaller/EtchRC1Prep I only see rather minor issues regardings powerpc (btw, I think that declaring which subarchs are broken would help. But the powerpc subarch with the biggest userbase, newworld, works just fine (IMEs).) http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED] rg;include=powerpc lists 4 important bugs, but no serious ones. And http://wiki.debian.org/powerpcEtchReleaseRecertification lists six d-developers, and not only you, Sven. And on http://release.debian.org/etch_arch_qualify.html powerpc is one of the five archs (out of 12) which only "green" fields. So I would say, the powerpc-port is in a pretty good shape overall. If you have other indications, please file them with the appropriate severity in the BTS or stop spreading fear, uncertainty and
Re: which serious bugs exactly? (Re: if you care about debian on powerpc, please react ...)
Hi, On Saturday 25 November 2006 23:08, Sven Luther wrote: > Thank you for this, why could you not at least leave me alone ? Because you spread FUD about the debian-powerpc port and claim it's so broken it needs to be removed from etch?! > joeyh accused me of delaying single-handledly the release a full week for a > very minor typo. This might be^w^wis unfortunate, that a single typo at the wrong place and time can delay a release by a week, but if it's like this, then it is like this. And if you don't understand this, maybe you should not be in the position to make such typos and cause such delays? > > For the sake of the users of the powerpc-port I'll quote here what I > > replied to your mail to debian-release on this wednesday about the same > > issue. > I saw now such thing, assuredly you forgot to CC me, right ? No. I didn't cc: you on purpose, because that's how the code of conduct on debian mailing lists is. If a person doesn't explicitly request a cc: you don't cc: that person. It's commonly considered unpolite to cc: people on mailinglists and this policy is written down. And you have been told this many times. > Yeah, this is your accusation. But still, frans and you and others have > also killed my motivation, but i still continue to work on debian, because > i care for the users. When was your last contribution ? I'm perfectly aware that you're motivation is also hurt. But you are not the only one in this world. Last weekend I created http://developer.skolelinux.no/~holger/archivestatus/needs_love.html and my primary motivation for this was to bring the debian-edu-powerpc port into shape. > Please go ahead, and count my patches and commits. I number 20-30 of them > since june. What have you done in this whole last year for powerpc ? I'm perfectly aware that you contributed more code for powerpc than I. But contributing code is not the only thing that counts. > > If you would have worked (as I suggested to you in June (or July?) this > > year) > And i did so. No. You started to bash and rant and attack people on various lists and demanded your commit rights back. > > on patches and bugreports and not continuesly ranted and insulted the > > people who cannot work with you (which you have done on >5 lists and by > > writing > Who, as you, chose to not work with me. Yes. Because I don't get any work done with you but just engange in effectivly useless discussions with you. So I rather do something else. Instead of writing this email, I could have contributed my research about the memory requirements for d-i on powerpc for the installation manual for example. Instead of doing so I write this email, which I sadly believe (been there, done that, too often) is a waste of time. That I still write this email has two reasons: I still have empathy for you, I would be very happy if you would understand that this whole situation is not about you as a person, even though your current and past behaviors are (IMO) the main reason the situation is like it is. And I do care about powerpc and it's users. So I see a need to correct your misinformations. > Since then, my upload of the fan control patch was reverted without > mention, after it had rested for a full 29 days in the BTS without a single > comment. The patch is in svn now. And the patch rested in svn, because we're preparing a release (candidate) and shortly before releasing such a thing, the packages are uploading (with all changes from svn) to include new translations for example. This is why your patch rested in the BTS, to be included after the RC1 release as it has been done now. And really, loud fans are an issue, but they don't make the installer completly usuable (play some louder music during the 30mins of installations, whatever) for the minority of powerpc users with such a hardware, while there is a risk of breaking the whole powerpc port by commiting last-minute changes. I appreciate a conservative release policy for the sake of all users. > currently shiping powerpc hardware are : > > IBM pseries : not really supported, patch sitting without comment since > months, early work lost because of svn commit conflicts. raise the bug severity? which bug#, btw? > Genesi Efika : upcoming product, patches not ready for 2.6.18, will not > be supported in etch. debian never supported non-available hardware so far, and upcoming products are often delayed or changed. And this machine is not exacly currently shipping... And you're in the kernel team and have commit rights there, so you can make the patches ready for 2.6.18... > Mercury 1U G5 servers : never saw one of those, the linux/powerpc > upstream guys have no idea how it works, may work identical to IBM pseries, > or not, but in any case, i wouldn't mention them as supported. Right. Nor would I. So what, exactly? > Sony PS3 : no hardware available to us, not supported right now. Right. So what? > assorted powerpc embed
Re: which serious bugs exactly? (Re: if you care about debian on powerpc, please react ...)
Hi,
On Sunday 26 November 2006 11:39, Johannes Berg wrote:
> > And really, loud fans are an issue, but they don't make the installer
> > completly usuable (play some louder music during the 30mins of
> > installations, whatever) for the minority of powerpc users with such a
> > hardware, while there
> Clearly you belong to the majority who don't own such a machine.
Right. (Not that I would not like to have one :)
> In this
> case, it does really make the whole machine pretty much unusable.
During installation. How often does one install?
> Besides (I might be mistaken) if the installer doesn't know about those
> modules then they won't be in the installed system either, no?
AFAIK they are incuded in the sid kernels (at least, maybe etch too) and you
can easily manually load them. Problem solved. (And _if_ they weren't in the
kernel, the kernel team would need to enable them, and Sven is part of the
kernel team. And if they are not in etch, it's the kernel teams duty again.)
A note for the d-i RC1 errata ("do $this+that after installation to make the
fans less noisy") would defintly be nice - but certainly anybody with access
to the hardware can write such a note.
(Basically it's in the last commits at
http://svn.debian.org/wsvn/d-i/trunk/packages/rootskel/src/lib/debian-installer-startup.d/?op=log&rev=0&sc=0&isdir=1
which I cannot access atm (writing offline) and all you need to do do is to
load three modules.)
regards,
Holger
pgp4nPmtsnIoH.pgp
Description: PGP signature
Re: which serious bugs exactly? (Re: if you care about debian on powerpc, please react ...)
Hi, On Sunday 26 November 2006 19:25, Johannes Berg wrote: > > During installation. How often does one install? > Well, it does take a while :) Though when I installed mine, the So you have such a machine :) Could you please test, if those noisy fans are made silent with d-i RC1 and with the current daily-builds and tell us the results. (You don't have to do a full install, the fans should be silent by the time you reach partioning at latest...) If RC1 still has the noisy fans, I'd suggest to link http://svn.debian.org/wsvn/d-i/trunk/packages/rootskel/src/lib/debian-installer-startup.d/S05fancontrol-linux-powerpc?op=file&sc=1 in the errata and with that tell people how to manually turn the fans silent. regards, Holger pgpYkfgqkgLdt.pgp Description: PGP signature
Re: which serious bugs exactly? (Re: if you care about debian on powerpc, please react ...)
Hi, On Sunday 26 November 2006 15:09, Sven Luther wrote: > > > currently shiping powerpc hardware are : > > > IBM pseries : not really supported, patch sitting without comment > > > since months, early work lost because of svn commit conflicts. > > raise the bug severity? which bug#, btw? > > Outstanding bugs -- Normal bugs; Patch Available (1 bug) > #394970: finish-install: [powerpc64] Add support for IBM serial consoles > (hvc and hvsi) > Package: finish-install (finish-install 2.4); Reported by: Sven Luther > <[EMAIL PROTECTED]>; Tags: patch; 33 days old Sven, the last info on this bug is from you, saying that you would test the patch Frans corrected the coming (and now past) weekend. You didn't post an update how the test went, so I'm not surprised the patch isn't commited. How did the test went? Is the patch now fine? Could you please add this information to the bugreport?! Thanks. As you mention this bug in this thread under the "powerpc should be removed because arch support is poor" label (which I still think isn't true), I wonder if the severity "normal" is correct. regards, Holger pgprCqbgFZjRC.pgp Description: PGP signature
Re: which serious bugs exactly? (Re: if you care about debian on powerpc, please react ...)
Hi, On Sunday 26 November 2006 15:45, Alex Fernandez wrote: > One of the selling points of Free Software in general, and Debian in > particular, is that the people doing the coding are the people in > charge. Right. The people doing the vast majority of work on the debian-installer, which runs on 12 architectures, are in charge. Sven is "only" working on the powerpc port of it. And he is not the only person working on powerpc in d-i. regards, Holger pgpB0INjrMEzB.pgp Description: PGP signature
Re: linux-kernel-di-powerpc-2.6_1.24_powerpc.changes REJECTED
Hi, On Monday 27 November 2006 18:38, Michael Schmitz wrote: > I see. Is the installer smart enough to pull packages from more than one > archive? Yes. During build time it looks for local udebs which will be included in the cd-image. regards, Holger pgpyCjvVeSRTS.pgp Description: PGP signature
Re: linux-kernel-di-powerpc-2.6_1.24_powerpc.changes REJECTED
Hi, On Thursday 30 November 2006 15:49, you wrote: > That's not what I was asking - during run (install) time, there is no way > to pull udebs off the net then, I gather? If you use your own mirror and modify that, you can. It's even explained in the d-i developer documentation how to do this, as this is a FAQ. > Just to make myself clear: I do _not_ consider hiding a note on how to > silence the fans in the release notes' errata to be sufficient according > to Debian quality standards. Not the standards I've come to expect from > past releases, at least. I completly agree, but you seem to be not aware, that we are talking about RC1 of the debian-installer and RC1 means "Release Candiate 1". It's called "RC1", "testing" and "unstable" for reasons. The only reason I care about this info in the release notes for RC1, is to have this issue solved (by documenting a workaround) in etch as well. In unstable it's fixed. regards, Holger -- quoting http://www.debian.org/MailingLists/index.de.html#codeofconduct "When using the Debian mailing lists, please follow these rules:... When replying to messages on the mailing list, do not send a carbon copy (CC) to the original poster unless they explicitly request to be copied." We live in the year 2006, a few bytes wasted in the footer of a mail don't hurt anymore, but everybody is flooded with information and attention is a spare ressource. If you send a mail cc: to a list and to me, it will catch my attention even if I have none. Please don't. Unless you specifically want to catch my attention of course :) But If I don't say otherwise, I'm subscribed to the mailinglist (and this is true for non-Debian lists as well) and you don't need to cc: me. Thanks. pgpHmT1TAZAN9.pgp Description: PGP signature
Re: which serious bugs exactly? (Re: if you care about debian on powerpc, please react ...)
Hi, On Thursday 30 November 2006 12:20, Charles Plessy wrote: > No need to test, they are not: > http://lists.debian.org/debian-boot/2006/11/msg00789.html Ok. I will add info about this in the errata then. > On the other hand, I recommend to test wether they also stay silent on > the installed system as well. Could you do this? regards, Holger pgp7hqlMjw3lr.pgp Description: PGP signature
Re: which serious bugs exactly? (Re: if you care about debian on powerpc, please react ...)
Hi, On Thursday 30 November 2006 15:30, Sven Luther wrote: > > > #394970: finish-install: [powerpc64] Add support for IBM serial > I didn't, because [1, 2 & 3 - basically no time] And then you complain, that other people don't find the time to reply to the bugreport. Can't you imagine, that they are either busy like you or don't have the hardware or both? regards, Holger pgpYhttbbQDRp.pgp Description: PGP signature
g5 imacs now silent?
Hi, this bug was originally about building certain windfarm drivers into the kernel instead of modules, but it seems, that this was a red herring and the current kernel in sid now includes working modules to turn the G5 fans silent. If this is correct, this bug can be closed. Is it correct? regards, Holger pgpjSQSfjK1Ai.pgp Description: PGP signature
Re: which serious bugs exactly? (Re: if you care about debian on powerpc, please react ...)
Hi, On Thursday 30 November 2006 18:21, Fabio Tranchitella wrote: > * Holger, Frans and who others involved, could you please stop to reply > to Sven's non-technical e-mail messages? It surely do not help anybody. Indeed, I did regret sending the previous mail in this thread to the list and not privatly. Sorry. Fabio, also I would appreciate no cc:s on mails to bugs in d-i (or the debian-boot or debian-powerpc list), thanks, but I'm subscribed. Similarily I suggest you, Fabio, subscribe to these lists as well. I want to work on d-i and debian powerpc, and not be thinking all the time: "will this become an interaction with Sven and do I need to cc: Fabio??"... so I might forget to cc: you. regards, Holger pgpYymf127Q1l.pgp Description: PGP signature
Re: g5 imacs now silent?
Hi, On Thursday 30 November 2006 23:04, Étienne Bersac wrote: > Beware not to confuse iMac G5 rev A&B and rev C (among PowerMac G5). > iMac G5 rev C (chip PowerMac 12,1) do not have yet their windfarm > driver. Benh told that he began the work on this driver but has > difficulties to get access to de device. Benh, can you confirm ? Thanks for the information! Are those the latest G5 imacs? or the first ones? regards, Holger pgpkFKl7yQjXA.pgp Description: PGP signature
Re: g5 imacs now silent?
Hi, On Thursday 30 November 2006 18:06, Sven Luther wrote: [#397942] > > If this is correct, this bug can be closed. Is it correct? > The bug should be retitled and reassigned to initramfs-tools, if it is not > already. It only makes sense to do this, if its confirmed, that initramfs-tools doesn't make sure the modules are loaded. I lack this confirmation atm. Can someone confirm (or deny) that on a newly installed sid system, these modules are not loaded? If so, I'm happy to open a bug against initramfs-tools, but I close this bug now, because the history of it is not interesting to read for the initramfs-tools maintainer anyway :) > Holger: thanks for the work you are doing. Can you also comment on : > #397973: [powerpci/mac] partman-md appears to not write back the raid > flag to partitions. > Maybe it would be worth to raise the severity of this bug, but i can hardly > do this, or i will be seen as whiner who ups the severity of his pet bugs, > can i ask you to have a look at them ? I think the severity is right, if it's not a bit too high already :) RAID is not working, that's bad, but not the end of the world. So certainly not higher than important (which it is), maybe it's even normal. I'll leave it as it is. regards, Holger -- quoting http://www.debian.org/MailingLists/index.de.html#codeofconduct "When using the Debian mailing lists, please follow these rules:... When replying to messages on the mailing list, do not send a carbon copy (CC) to the original poster unless they explicitly request to be copied." We live in the year 2006, a few bytes wasted in the footer of a mail don't hurt anymore, but everybody is flooded with information and attention is a spare ressource. If you send a mail cc: to a list and to me, it will catch my attention even if I have none. Please don't. Unless you specifically want to catch my attention of course :) But If I don't say otherwise, I'm subscribed to the mailinglist (and this is true for non-Debian lists as well) and you don't need to cc: me. Thanks. pgpbBmgZdPhzp.pgp Description: PGP signature
2nd version of the patch for the errata about imac g5 fans(Re: g5 imacs now silent?)
Hi, On Friday 01 December 2006 15:33, Charles Plessy wrote: > > Thanks for the information! Are those the latest G5 imacs? or the first > > ones? > > I think that it is the latest. For the moment, the windfarm drivers are > available for powermacs 8,1 ; 9,1 ; and 11,2. (grep FARM > /boot/config-2.6.*-powerpc64). > > You can find the correspondance between these codes and the commercial > name in the following page: http://www.theapplemuseum.com/index.php?id=36 On Friday 01 December 2006 17:26, Étienne Bersac wrote: > Those are the latest iMac G5 (first iMac with iSight). Based on this information, I now propose the following patch (also attached) to the errata: + on G5 Apple machines the fans are very loud, switch to a different + console and run http://svn.debian.org/wsvn/d-i/trunk/packages/rootskel/src/lib/debian-installer-startup.d/S05fancontrol-linux-powerpc?op=file&sc=1";>these commands. This doesn't work on the latest modell (powermac 12,1 "iSight") yet (not supported in the kernel). regards, Holger -- quoting http://www.debian.org/MailingLists/index.de.html#codeofconduct "When using the Debian mailing lists, please follow these rules:... When replying to messages on the mailing list, do not send a carbon copy (CC) to the original poster unless they explicitly request to be copied." We live in the year 2006, a few bytes wasted in the footer of a mail don't hurt anymore, but everybody is flooded with information and attention is a spare ressource. If you send a mail cc: to a list and to me, it will catch my attention even if I have none. Please don't. Unless you specifically want to catch my attention of course :) But If I don't say otherwise, I'm subscribed to the mailinglist (and this is true for non-Debian lists as well) and you don't need to cc: me. Thanks. Index: errata.wml === RCS file: /cvs/webwml/webwml/english/devel/debian-installer/errata.wml,v retrieving revision 1.97 diff -u -r1.97 errata.wml --- errata.wml 17 Nov 2006 05:43:15 - 1.97 +++ errata.wml 2 Dec 2006 09:56:42 - @@ -128,6 +128,8 @@ the snd-powermac module is no longer loaded by default as it will lock up some systems; you will need to add it to /etc/modules manually + on G5 Apple machines the fans are very loud, switch to a different + console and run http://svn.debian.org/wsvn/d-i/trunk/packages/rootskel/src/lib/debian-installer-startup.d/S05fancontrol-linux-powerpc?op=file&sc=1";>these commands. This doesn't work on the latest modell (powermac 12,1 "iSight") yet (not supported in the kernel). pgpBxuumnByvs.pgp Description: PGP signature
miboot-floppies (powerpc oldworld) for sarge
Hi, The miboot enabled d-i sarge floppies for oldworld powerpc are now available again, you can find them at http://layer-acht.org/d-i-miboot/ When/if :) I become a DD, I'll move them to people.d.o and leave a note on my webserver.. I'll keep them available until lenny (!) is released at least, to ensure that people can still install (and then manually upgrade) their machines, even if newer versions of d-i should drop support for oldworld. Oh, and I have not tested them yet, because I'm away from my oldworld machines. So if you can, please test them and report back here. If nobody else does, I will test them at some time ;) regards, Holger pgpXOkT5hW1f9.pgp Description: PGP signature
Re: miboot-floppies (powerpc oldworld) for sarge
Hi Lucas, On Friday 15 December 2006 13:30, Lucas Rossi wrote: >Unfortunately the images didn't work, man...I just tested here... :-( Thanks for telling though. Can you say what didn't work / where it failed how? Would probably help to fix it :) regards, Holger pgpIWfpOpCm0y.pgp Description: PGP signature
Re: miboot-floppies (powerpc oldworld) for sarge
Hi Lucas, On Friday 15 December 2006 15:32, you wrote: >As I said, you didn't (until now) ;) >the computer just spits out the disks, you tried the 2.4 and 2.6 ones? > I would think that it's a problem with my > computer, but I was able to boot from an old Debian disk, I think it > was woody. I've seen all kinds of strange effects with floppies. Did you try another physical one? >There's no error message, nothing...and since I'm kind of a > beginner I can't help you with the advanced stuff...it's the first > time I'm installing Debian in a Mac. Does the "mac-computer"-icon in the middle of the screen turn into a penguin? Do yo see that icon at all when turning on the machine? Which oldworld machine do you have? >I'll help the way I can, by testing...;-) That's very appreciated, thanks! regards, Holger pgpOI65VwoJT0.pgp Description: PGP signature
Re: miboot-floppies (powerpc oldworld) for sarge
Hi, On Friday 15 December 2006 21:37, Sven Luther wrote: > Notice that the 2.6 sarge d-i image had a bug which was later fixed in the > etch/sid version. It has to do with calling mkvmlinuz i think, instead of > simply gzipping it by hand. > > Holger, can you backport the little change from the sid branch, this should > fix it. But why? People can install with 2.4 just fine and then later upgrade to 2.6, so why do the work and backport it? The CDs work fine with 2.6, don't they? It's only the miboot floppies, isn't it? regards, Holger pgpoUmmzYlOAB.pgp Description: PGP signature
Re: miboot-floppies (powerpc oldworld) for sarge
Hi, On Saturday 16 December 2006 00:52, Sven Luther wrote: > > But why? People can install with 2.4 just fine and then later upgrade to > > 2.6, so why do the work and backport it? > Because even when using 2.4 floppies, they will install the 2.6.8 kernels, > so it is best to have the same kernel for installation media and reboot > kernels. As I don't know of any hardware that a.) needs to boot from floppy and b.) doesnt work with 2.4 but only with 2.6 I still don't see a good reason to do the work and do a rebuild of the _sarge_ miboot-floppies. Since almost 10 years (1997 I think) apple switched to newworld, which all can boot from cdrom or have proper OF implementations to boot from network - so I also doubt there is a hardware which needs this and I don't know :) > The change is trivial, please try it : At the moment I only have/had to run "debuild", everything else, takes some of my time which I rather invest in improving etch and lenny. Sorry for not using your patch, but you can always rebuild the miboot floppies yourself ;-) regards, Holger pgpfYZ4vVlYzC.pgp Description: PGP signature
Re: miboot-floppies (powerpc oldworld) for sarge
Hi, On Wednesday 20 December 2006 04:09, John Schmidt wrote: > I have an oldworld ppc that can't boot from cdrom that would benefit from > sarge miboot floppies. download them from http://layer-acht.org/d-i-miboot/ regards, Holger pgp1HPYA1i1ja.pgp Description: PGP signature
Re: miboot-floppies (powerpc oldworld) for sarge
Hi, On Wednesday 20 December 2006 00:25, Rick Thomas wrote: > There are plenty of OldWorld Macs out there (I own 6 of them) that > would benefit from a kernel 2.6 bootable Sarge floppy-set. How?`Are you really sure the 2.4 floppies don't work with them? What I forgot to say in my mail yesterday, at which is quite important: after installing sarge with the 2.4 floppies you can easily upgrade your sarge installation to 2.6: sudo apt-get install kernel-image-2.6-powerpc regards, Holger > Please! Please: -- quoting http://www.debian.org/MailingLists/index.de.html#codeofconduct "When using the Debian mailing lists, please follow these rules:... When replying to messages on the mailing list, do not send a carbon copy (CC) to the original poster unless they explicitly request to be copied." We live in the year 2006, a few bytes wasted in the footer of a mail don't hurt anymore, but everybody is flooded with information and attention is a spare ressource. If you send a mail cc: to a list and to me, it will catch my attention even if I have none. Please don't. Unless you specifically want to catch my attention of course :) But If I don't say otherwise, I'm subscribed to the mailinglist (and this is true for non-Debian lists as well) and you don't need to cc: me. Thanks. pgpdQrzWS1w4G.pgp Description: PGP signature
Re: miboot-floppies (powerpc oldworld) for sarge
Hi, On Wednesday 20 December 2006 07:43, Rick Thomas wrote: > Not to put words into his mouth, but I think that is what Holger is > saying. For the purpose the Sarge floppyset serves, it's enough to > have just a 2.4 kernel for the installer. Yes. > Holger seems to reply "Why bother?" I rather like to concentrate on etch/lenny now. > My thought (admittedly a bit of a stretch) is that there *may* be > hardware out there (SATA disks?) that a user can plug into an > OldWorld PowerMac PCI slot that is not supported by the 2.4 kernel, > but is supported by the 2.6 kernel, and why should we artificially > limit our user base to exclude such users? Because such users only *might* exist and even they can easily work around this themselves? regards, Holger pgplWLpY49T7Z.pgp Description: PGP signature
Re: miboot-floppies (powerpc oldworld) for sarge
Moin, On Wednesday 20 December 2006 21:05, Rick Thomas wrote: > > listing the working reports and not working ones, or something. > > Then give out > > a call for testers of the last daily-builds. > That would be a good idea. Unfortunately I don't have the time or > the HTML skills to do such a thing. Anybody else willing to set it > up? I'll contribute data-points if you do... I think I have the needed wiki-skilz and created a table on http://wiki.debian.org/DebianInstaller/PowerPC/OldWorld - but I haven't included real data yet... (also the table columns need to be improved...) regards, Holger pgp9Z2WDFxi0U.pgp Description: PGP signature
Re: miboot-floppies (powerpc oldworld) for sarge
Hi, On Monday 25 December 2006 06:40, Christian Müller wrote: > I've just successfully tested the --boot d-i set of files-- @ > http://people.debian.org/~wouter/d-i/powerpc/20061224-03:00/powerpc/cdrom/ > > method: BootX under MacOS9, video=ofonly > machine: Beige G3 desktop model, openfirmware version 2.4 > > I tried lot's of floppy images floating around lately but must have > missed the ones that work ;-) Unfortunately ~wouter seems to have given > up on the floppy building part (assumption made on the fact that there > is netboot, cdrom, mini-iso, etc. but no floppy images). Anyway, I wish they are here: http://people.debian.org/~wouter/d-i/powerpc-miboot/ I haven't tested them in a while, though. regards, Holger pgp8xonCYtGkR.pgp Description: PGP signature
Re: Who is actively porting the Debian architectures?
Hi, On Monday 25 December 2006 23:40, Frans Pop wrote: > PowerPC -- > member Daniel Jacobowitz > member Martin Schulze > member Hartmut Koptein > I would suggest at least the following changes: > PowerPC: add Sven Luther and Bastian Blank http://wiki.debian.org/powerpcEtchReleaseRecertification lists the following people for powerpc (Bastian is missing there): Roger Leigh Alexander Wirt Sven Luther Michel Daenzer Colin Watson Mark Brown Holger Levsen Given the rumors powerpc would be dead, I suggest to name them all :) regards, Holger pgpa8wXhlyMJc.pgp Description: PGP signature
Re: Who is actively porting the Debian architectures?
Hi, On Tuesday 26 December 2006 12:52, Charles Plessy wrote: > Le Tue, Dec 26, 2006 at 11:20:50AM +0100, Holger Levsen a écrit : > > http://wiki.debian.org/powerpcEtchReleaseRecertification lists the > > following people for powerpc (Bastian is missing there): [...] > I would like to recommend that only persons who do volunteer to be > reactive would be listed here. This mail is bcc:ed to those listed on that wiki page, to see if they are still active with powerpc and should be listed on http://www.debian.org/intro/organization - ping... > I had some difficulties in the past to rebuild a package on powerpc, and I'm happy to build packages on ppc for you. But I'm no DD, so I cannot upload those and you shouldnt :) regards, Holger pgpdJnFJdsl9J.pgp Description: PGP signature
Re: Who is actively porting the Debian architectures?
Hi, On Tuesday 26 December 2006 12:37, Aurélien GÉRÔME wrote: > The Debian's Organizational Structure page only lists DD. At least, > one of them in the previous list is not DD; find the intruder. :) Funnily I claimed "I'm no DD" on that wiki page, and that other page lists my name :-D regards, Holger pgpAXc4ZodzHI.pgp Description: PGP signature
Re: Migrating from iMac/powerpc to iMac/intel
Hi, On Sunday 31 December 2006 04:02, Eduardo Trápani wrote: > I just wrote to debian-users because I need to move a whole debian box > from a powerpc iMac to an intel pc. The problem is that there seems to > be platform specific files in use and that means that simply > reinstalling packages and copying /etc will not be enough. You need to identifiy those files that _seem_ to be platform specific. From my experience there are basically none. When my ibook broke, I installed the same packages on a i386 laptop, copied the configuration files and /home and kept working :-) "bacially none" because the bootloader config is different and I used a different partitioning, so fstab was different too... Stuff in /usr/local is likely to be platform specific, too. But not in /etc. regards, Holger pgpwQXVPaQkQ8.pgp Description: PGP signature
Re: Installing Debian on a Beige G3 PowerMac (OldWorld)
Hi, On Saturday 30 December 2006 07:33, Rick Thomas wrote: > your machine won't boot til you re-key the options. I find this > prospect enough of a potential PITA that I strongly recommend the > fourth option. > > The fourth and final boot loader option is MacOS-9 with a simple > little extension called BootX (This is *not* the same BootX as you > may be using to get your G3 to run MacOS-X. This BootX was written > by Benjamin Herrenschmidt, who does most of the heavy lifting porting > work for Linux on PowerPC hardware. (He also wrote miboot.) Please not that Benjamin recommends not to use bootX if possible: http://lists.debian.org/debian-powerpc/2006/07/msg00017.html Bootx is mostly useful if you also want to boot mac os <=9, which is a even more rare usecase nowadays then running these machines at all :) If you only run linux, go with quik. (And for the troubles Rick mentiones, have miboot floppies ready (available at http://layer-acht.org/d-i-miboot/) and write down the steps needed to configure OF properly for your machine. And while you're at it, share those steps :) regards, Holger pgpWswDRBoekc.pgp Description: PGP signature
Re: Bug #400919: Bug affecting Kino (and Cinelerra) on PowerPC, any ideas?
Hi, On Friday 05 January 2007 14:36, Michael Schmitz wrote: > > On Thu, 2007-01-04 at 19:46 +0100, Herman Robak wrote: > > > DV video playback in Kino is unusably slow on Debian Sid for PowerPC. > > > I get only 1-2 frames per second on a Mac mini, whereas Mplayer and > > > Vlc both give smooth playback. > > > > This is because libdv is broken for big-endian systems, and not > > optimized for PPC. The dv decoder in FFMPEG is faster and looks correct. > > Amen to that. This is an old bug; incredible enough no one bothered to fix > libdv for big endian systems yet? > > > IIRC kino will use the ffmpeg decoder if it is available, or used to > > anyway. Solution is to investigate seeing how kino can use the ffmpeg > > decoder. > > That's been done - IIRC Guido Guenther provided ffmpeg enabled binaries at > http://honk.sigxcpu.org/linux-ppc/debian ... cc:ed so he can comment on this. On my imac kino crashed when trying to load a .dv file, log is attached. But I could see the preview window for a second, with correct colors. IMHO the severity of this bug should be upgraded. > is ffmpeg OK to distribute now? ffmpeg is available in debian main since some time. regards, Holger > Kino Common being built > Creating page editor > Creating Capture Page > Creating Export Page > Creating Export1394 Page > Creating ExportAVI Page > Creating ExportStills Page > Creating ExportAudio Page > Creating Preferences Loading preferences from "/home/mythtv/.kinorc" Saving preferences. > Creating ExportMJPEG Page /usr/share/kino/scripts/dvdauthor/dvdauthor-k3b.sh /usr/share/kino/scripts/dvdauthor/dvdauthor.sh /usr/share/kino/scripts/dvdauthor/none.sh /usr/share/kino/scripts/dvdauthor/growisofs.sh /usr/share/kino/scripts/dvdauthor/qdvdauthor.sh > Initializing MJPEG Export Page settings from Preferences > Creating ExportPipe Page /usr/share/kino/scripts/exports/ffmpeg_mp4_dual.sh /usr/share/kino/scripts/exports/ffmpeg_vcd.sh /usr/share/kino/scripts/exports/ffmpeg_3gp.sh /usr/share/kino/scripts/exports/extract_chapters /usr/share/kino/scripts/exports/ffmpeg_divx_dual.sh /usr/share/kino/scripts/exports/ffmpeg_h264.sh /usr/share/kino/scripts/exports/ffmpeg_dvd_dual.sh /usr/share/kino/scripts/exports/ffmpeg_divx.sh /usr/share/kino/scripts/exports/ffmpeg_dvd.sh /usr/share/kino/scripts/exports/ffmpeg_h264_dual.sh /usr/share/kino/scripts/exports/mencoder.sh /usr/share/kino/scripts/exports/ffmpeg_flv.sh /usr/share/kino/scripts/exports/ffmpeg_mp4.sh /usr/share/kino/scripts/exports/ffmpeg_mp3.sh /usr/share/kino/scripts/exports/rawplay.sh /usr/share/kino/scripts/exports/mencoder_dual.sh /usr/share/kino/scripts/exports/ffmpeg2theora.sh /usr/share/kino/scripts/exports/ffmpeg_utils.sh > Creating page trim > Creating Magick Page >> Searching /usr/lib/kino-gtk2 for plugins >>> Registering plugin /usr/lib/kino-gtk2/libdvtitler.so >>> Registering plugin /usr/lib/kino-gtk2/libtimfx.so >> Starting Editor >>> dv1394Writer::dv1394Writer /dev/dv1394/0 channel 63 fd -1 >> Kino Common newFile >> Creating undo/redo buffer >>> Received playlist to store at position 0 Adding to end >>> Received playlist to store at position 1 Adding to end >> image creator repository created >>> Image Create: Fixed Colour >>> Image Create: Random noise >>> Image Create: Colour Range >>> Image Create: Gradiant >>> Image Create: Create From File >> image filter repository created >>> Image Filter: No Change >>> Image Filter: Black & White >>> Image Filter: Sepia >>> Image Filter: Reverse Video >>> Image Filter: Mirror >>> Image Filter: Kaleidoscope >>> Image Filter: Swap >> image transition repository created >>> Image Transition: No Change >>> Image Transition: Switch >>> Image Transition: Fade >>> Image Transition: Push Wipe >>> Image Transition: Barn Door Wipe >>> Image Transition: Differences >> audio filter repository created >>> Audio Filter: No Change >>> Audio Filter: Silence >>> Audio Filter: Fade In >>> Audio Filter: Fade Out >> audio transition repository created >>> Audio Transition: No Change >>> Audio Transition: Cross Fade >>> Audio Transition: Dub >>> Audio Transition: Mix >>> Image Filter: Titler >>> Image Filter: Superimpose >>> Image Filter: Blur >>> Image Filter: Color Hold >>> Image Filter: Soft Focus >>> Image Transition: Luma Wipe >> Trying XVideo at 720x576 >>> XvQueryAdaptors count: 1 >>> Xv: ATI Mach64 Back-end Overlay Scaler: ports 65 - 65 >>> formats supported: 4 >>> 0x32595559 (YUY2) packed >>> 0x59565955 (UYVY) packed >>> 0x32315659 (YV12) planar >>> 0x30323449 (I420) planar >>> 0: XV_IMAGE, 720x2048 rate = 1/1 The program 'kino' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 1100 error_code 11 request_code 140 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it wi
Re: Bug #400919: Bug affecting Kino (and Cinelerra) on PowerPC, any ideas?
Hi, On Sunday 07 January 2007 16:59, Guido Guenther wrote: > The ffmpeg and mplayer packages I provided were based on the packages > from Christian Marillat (debian-multimedia.org). I sent all the > necessary modifications back to him. I no longer build the packages > myself - Christian autobuilds these now like on the other architectures. > > The ffmpeg binaries and libavcodec libs on debian-multimedia.org are (or > at least were the last time I looked at) altivec optimized [1]. Building > kino against it should give reasonable performance. Holger, could you > try that as a first step? Once we have that we need two versions of > ffmeg (altivec optimized and not and select the correct one during > runtime) - probably using glibc capabilities like openssl does for i386. actually it's about kino and ffmpeg in debian-main which should not have altivec optimations, because if it does, it doesnt run on all ppc-hardware, like my imac g3. Unfortunatly I dont have time to build and test now, as I will leave tomorrow and be away from my imac the next weeks :( regards, Holger pgpDeMDGp9mMf.pgp Description: PGP signature
Re: Debian has failed us
Hi, On Saturday 13 January 2007 08:47, Joey Hess wrote: > Benjamin Herrenschmidt wrote: > > Yes, I've seen various mails/rants etc... and haven't wanted to take > > part of it neither in the past, but it looks like this has gone too far, > > and it's more and more looking like even perfectly good bug fixes that > > are needed for most users are being rejected on the sole basis of the > > person they originate from. Either that or somebody has an agenda of > > fucking up powerpc support in debian... > I'm trying to figure out how you're getting from the posts that have > been made to this thread, stating that the aforementioned bug was fixed > in a timely manner and has a fix available in the current daily builds, > and that the OP just used the wrong image, to the assertian above. > > Having a hard time making that connection, could you explain your logic? I dont think _this_ thread is the cause for Bens perception, rather those threads which _started_ with these mails (and others): http://lists.debian.org/debian-powerpc/2006/04/msg00407.html http://lists.debian.org/debian-powerpc/2006/08/msg00100.html http://lists.debian.org/debian-powerpc/2006/09/msg00139.html http://lists.debian.org/debian-powerpc/2006/11/msg00164.html http://lists.debian.org/debian-powerpc/2006/11/msg00137.html http://lists.debian.org/debian-powerpc/2007/01/msg00012.html *sigh* And to repeat what not only I've said before: various debian people (whether they are part of the installer team or not) care about powerpc, are happy about patches and run it daily on their main machines. And to repeat what also has been said before: the ongoing flamewars probably hurt the powerpc port more than anything else. I switched my focus mostly over to powerpc on debian-edu (instead of debian-installer) cause I'm sick of these flamewars. But I'm also sick to hear that debian (or the debian-installer team) wants the powerpc port to die or that it's dead already (so I sometimes take a stand in this dispute). FUD as its best. regards, Holger pgp2cVTCicKLQ.pgp Description: PGP signature
Re: Can't boot Mac OSX after installing Etch - solved
Hi, On Tuesday 23 January 2007 10:13, Ananda Samaddar wrote: > Must have been something with the buggy graphical installer or my messing > with the partitions. I used OSX partitioning tool to partition the HDD > (it's piece of crap by the way) and everything is working dual-boot wise > now. > > Feel like a bit of a moron now! Na :) Mistakes are for learning, they're good :) Thanks for sharing your experiences! In my experience with 96mb ram, the partitioning tool of the graphical installer also behaved badly, thats why we made it switch to the text based installer if there are less than 128mb of ram available. But this doesn't seem to be enough - probably only if there are macosx partitions - which I cannot test :-/ (i suspect it needs to do more calculations and these calculation process is quite inefficient...) Does someone has a.) maxosx installed b.) more than 128mb (it's possible to tell the system to use less, if you have half a gig or something) and c.) is willing to do a test-install which might destroy the installation..? Uhh. Also it needs to be tested with our partitioning tool :) And the test should be done with the daily-build of the installer - which one did you use exactly? daily? rc1? ubuntu? regards, Holger pgpKWIOVcOLnk.pgp Description: PGP signature
Re: mol with 2.6.18-3 [Was: mol-modules 2.6.16-2]
Hi, On Friday 19 January 2007 17:01, brian wrote: > this is nice, however the last time i tried it > a few weeks ago, it deblesses my macosx system, > which is a pain to correct, especially for a novice. Could you try again please and submit an error, so this issue can be fixed and others wont have the problem? Thanks & regards, Holger pgpFe6etwYNKe.pgp Description: PGP signature
Re: miboot floppies from layer-acht
Hi rob, sorry for my late reply I was too busy the last two weeks... On Sunday 14 January 2007 10:00, rob rob wrote: > 1.At one point you're asked if you want to install stable, unstable or > testing. Won't this be a problem when sarge becomes old stable. I image the > installation will fail here because it will start installing etch, which > doesn't work with the 2.4 kernel. Hmm, good point. I hope it's actually using sarge and not stable :) (Which you could see in the logs) But if that fails, I could patch the source to s/stable/sarge/ and rebuild the flopppies once etch is out. > 2. There's no warning that you have to use a ext2 file system if you want > to use quik. I know this is a known problem, but I'll say it again in case > someone out there cares since it's a bitch to have to reinstall the base > system on a 275 mhz machine with 96 mb ram. /me nods. > 3. Quik doesn't work. I know this "just happens" on some old world macs, > but I hope that's not my case. I got the following error message: > > This machine is not supported: AAPL,e411MacFisc (no big surprise there) > quik-installer failed with error code 1 I cannot really comment on this, as I dont know your mac (6500). http://penguinppc.org/bootloaders/quik/quirks.php says: Requires special: output-device /bandit/ATY,264GT-B load-base may need to be changed to 10. > I then went over to the terminal and tried running quik both on a chrooted > filesystem and by changing into the /target directory and using the quik -r > /target, both came out with error messages. The first one had something to > do with /proc/cpu not being readable, mount /proc or mount /proc /proc fixes that. > the second one with /dev/hda2 not > being mountable. Thats because of the devfs pathes... > Unfortunately I didn't take any notes on those error messages or exactly > what I did. Those are quite useful to get help :) > I would appreciate any tips on how to get quik working with layer-acht > floppies, just to prove it's possible. I'm away from oldworld hardware at the moment :( > I'm also always up for testing the > ~wouter floppies if there are any changes made there. Cool! regards, Holger pgplwrRt7Hq18.pgp Description: PGP signature
Re: G3 B/W pcilynx firewire blues
Hi, On Tuesday 13 February 2007 05:30, Rick Thomas wrote: > I'd suggest that pcilynx be disabled in the Debian PPC kernels, and a > note to that effect be put in the release documents. > > To what package should I send a bug report with that payload? package "release-notes" for documentation and "linux-2.6" for disabling the driver. regards, Holger pgpElhPHIofhY.pgp Description: PGP signature
Re: PowerPC buildd is looking for a new home
Hi Daniel, On Wednesday 09 May 2007 22:49, Daniel Jacobowitz wrote: > voltaire.debian.org, our venerable but still reliable build daemon, > has been living in my apartment for a number of years. I'm moving > house shortly, though, and won't be able to host it in my new home. > So it needs a new guardian. Thank you for hosting voltaire for so long! When do you move? (As in, until when the machine needs to be moved?) I have added this to rt.debian.org as ticket #86. regards, Holger pgps9FMUkEoOl.pgp Description: PGP signature
Re: PowerPC buildd is looking for a new home
Hi, On Thursday 10 May 2007 12:56, Daniel Jacobowitz wrote: > > When do you move? (As in, until when the machine needs to be moved?) > By the beginning of June. Adding to the request tracker. If nothing happens within ten days or so I'll ping DSA again, to make sure you can happily move and we keep our powerpc buildd :) regards, Holger pgpZ1TdMEynpw.pgp Description: PGP signature
Re: PowerPC buildd is looking for a new home
Hi, On Friday 11 May 2007 09:50, Ralf Saalmüller wrote: > it's 20 day to go until the buildd for the debian powerpc port gets > disconnected. Yes, we know. But this has nothing to do with those powerpc64 machines discussed in this thread. regards, Holger pgpnMHEwZu69A.pgp Description: PGP signature
Re: PowerPC buildd is looking for a new home
Hi, On Thursday 10 May 2007 14:32, Holger Levsen wrote: > Adding to the request tracker. If nothing happens within ten days or so > I'll ping DSA again, to make sure you can happily move and we keep our > powerpc buildd :) voltaire.d.o will be relocated this weekend :) regards, Holger pgp0UyHvFxucw.pgp Description: PGP signature
Re: Network-manager issues.
Hi, On Tuesday 22 May 2007 10:06, Jimmy Johnson wrote: > computer running SimplyMEPIS version 6.0 i386, just yesterday I had the > same problem with a new install of Skolelinux RC1 and copied the did you try the new powerpc etch based version of Skolelinux? I would love to hear about powerpc users of Skolelinux! (It is not yet clear if we release the powerpc version, because we have little feedback on it so far...) BTW, reading /usr/share/doc/network-manager/README.Debian solved my network manager problems.. :) regards, Holger pgpELnLpln0iU.pgp Description: PGP signature
powerpc hardware to give away
Hi, I'm giving away my fully working oldworld powermacs: a g3 beige, a 7200 and a 4400, fully working with RAM and (most probably) harddrives. These machine are older than ten years and probably only interesting if you want to work on oldworld powerpc. Then I'm giving away my broken pegasos2 powerpc machine, where the 1ghz cpu overheated, due to a broken fan. The rest of the machine should still work. All items to be picked up in Hamburg, Germany. Contact me if you are interested, in about a week I'll throw^wrecycle them. regards, Holger pgp3rmeSelD09.pgp Description: PGP signature
Re: PowerMac 7200-platinumfb display problem
Hi, On Thursday 27 July 2006 03:35, Tomasz Grzegurzko wrote: > > > http://people.debian.org/~wouter/d-i/powerpc-miboot/daily/ > > > I tried this image today (27-Jul-2006) and suffered the same fate.. The image from there from the 23rd of July worked for me on a g3 oldworld, so give it a try. Some time after that the miboot build broke, it should be working again since August, the 4th (iirc), but I haven't had the time to test that myself. regards, Holger pgpjXqdxRLdre.pgp Description: PGP signature
Re: Still unable to install debian Etch on a 7046-b50 RS/6000
Hi, On Thursday 10 August 2006 00:30, Torsten Zirzlaff wrote: > I'm still fighting with my RS/6000 to get a Debian Etch on it. The > problem is, at least in my case, that I'm unable to use the stock > install images. Where did you download them? >Any idea where to ask for further help? debian-boot@lists.debian.org or better yet, send a bug report, see http://d-i.alioth.debian.org/manual/en.i386/ch05s03.html#submit-bug for details. (That bug reports get send to the mailing-list, too.) regards, Holger pgpRdjqnD0gmt.pgp Description: PGP signature
Re: Quik and atyfb
Hi, On Saturday 15 July 2006 17:17, Ben Racher wrote: > So my Powerbook G3 266mhz Wallstreet is now successfully running Debian, > however its a little slow. And I suspect the culprit is the video > acceleration that is issued by quik when you first load the kernel. I've > been using: > video=atyfb:vmode:16,cmode:32,mclk:67 > However, it doesn't seem to let me boot, as a get a crazy mess of > graphics going hangwire. Is there something in quik that needs to > changed, or is the above command incorrect? have you tried just using video=atyfb ? According to http://www.jonh.net/lppcfom-serve/cache/1043.html you should use a cmode of 24 and probably also a lower vmode. Whats mclk? regards, Holger pgpkz0iyUtry4.pgp Description: PGP signature
Re: howto move from yellow dog -> debian
Hi Russel, cc:ed cause I'm not sure wether you read the list... On Monday 10 January 2005 03:17, Russell McManus wrote: > I've got a 9600/MP running yellow dog linux, that I'd like to upgrade > to sarge. But I had some trouble with the sarge install cd, which I > have so far been unable to resolve. (See Message-ID: > <[EMAIL PROTECTED]>, subject line was "sarge > install help on 9600MP") According to your message, your network card (mace) was not detected. But you didn't tell which version of the debian-installer you've tried. Did you try the release candidate 2 from http://www.debian.org/devel/debian-installer ? (it has support for the mace driver.) If your system can only boot from floppy, you could also try http://ftp.debian.org/debian/dists/testing/main/installer-powerpc/rc2/images/powerpc/floppy-2.4/ > So I would like to ask: are there any nifty ways to install sarge from > a running, non-debian system? You could also bootstrap your system as Shyamal Prasa suggested. regards, Holger -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
d-i on pmac 9600 (was Re: howto move from yellow dog -> debian
Hi, On Monday 10 January 2005 17:17, Russell McManus wrote: > Holger Levsen <[EMAIL PROTECTED]> writes: > > On Monday 10 January 2005 03:17, Russell McManus wrote: > >> I've got a 9600/MP running yellow dog linux, that I'd like to upgrade > >> to sarge. But I had some trouble with the sarge install cd, which I > > According to your message, your network card (mace) was not > > detected. But you didn't tell which version of the debian-installer > > you've tried. Did you try the release candidate 2 from > > http://www.debian.org/devel/debian-installer ? (it has support for > > the mace driver.) > I downloaded an install iso from that site, not sure exactly which > one. The md5 sum of the iso I used is: > > MD5 (sarge-powerpc-1.iso) = a618fe6371390f2673b729ce673c3715 Well, this is the first cd of a full cd set. But I have no idea which one and google also doesn't know that md5-sum. > I couldn't find md5 sums for the iso's that are available to nail down > exactly which one I used. To be safe, you could just download a netinstall-image of rc2, it's only ~200mb. > > If your system can only boot from floppy, you could also try > > http://ftp.debian.org/debian/dists/testing/main/installer-powerpc/rc2/ima > >ges/powerpc/floppy-2.4/ > Thanks for the pointer. I haven't tried floppy booting, but I don't > think that will help, because the problem is not booting, but later on > during the install process. I'm pretty sure this is fixed in rc2. > Could the problem be related to the fact that I have an add-on pci NIC > inside the case in addition to the mc0 on-board interface? Maybe, dunno. For testing purposes you could unplug it :) > Thanks for taking the time to reply, much appreciated, > -russ you're welcome. If rc2 doesn't help, you should try to post on debian-boot@, this is the mailing list for the new installer. Alternativly, you could send a bug report (package: debian-installer). regards, Holger -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Trouble installing debian on a 8500/120
Hi, On Monday 24 January 2005 09:15, Marco Gaiarin wrote: > Hem, i've just tried sarge rc2, but as i've just stated, the floppy > image seems not bootable, and the documentation still speak about the > woody image (boot-floppy-hfs.img), so seems not updated. Try the floppy-images from http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy-2.4/ - the official floppy images are built without miboot (due to licence problems) and therefore are not bootable. HTH & regards, Holger pgpMGM4lEzNgT.pgp Description: PGP signature
Re: Switching from BootX to quik
Hi, On Wednesday 16 February 2005 13:02, Hans Ekbrand wrote: > > This was a common problem with previous, non-initrd enabled quik > > versions-- are you sure you've got the latest quik from sarge ? > > Yes, > > pc236:~# apt-cache policy quik > quik: > Installed: 2.1-3 > Candidate: 2.1-3 > Version Table: > *** 2.1-3 0 > 500 http://ftp.sunet.se testing/main Packages > 100 /var/lib/dpkg/status > 2.0e-0.6 0 > 500 http://ftp.sunet.se stable/main Packages > pc236:~# quik -V > QUIK version 2.1 > pc236:~# did you run quik without "-V" as well ? :) regards, Holger pgpxuoBBKAc9Q.pgp Description: PGP signature
Re: old apple machines supported ?
Hi, On Thursday 17 February 2005 04:08, teefour wrote: > The 4400 should work. Some time ago I had one running linux. No Idea > about the others. the 4400 does work (also with the new debian-installer) for sure. it even boots from a 160gb ide-harddrive :-) regards, holger pgpZNUAy6Llyu.pgp Description: PGP signature
Re: Problem installing on PowerMac 8600
Hi Patrick, On Tuesday 22 February 2005 18:02, Patrick Bachmann wrote: > This OldWorld-maschine doesn't want to boot the floppies, I'm trying to > feed it with. > There are various floppies I have tried, e.g. the woody and sarge boot > floppies and the floppies of the rc2 of the debian installer. > The only floppy, that gives me some kind of feedback is the > boot-floppy-hfs.img. After being read, an icon of a floppy with tux on it, > apears. But nothing else happens. Hmmm... this is the woody floppy and it should work, I guess this might by a floppy media issue -> try another floppy. Always write floppies with "dd" and compare them with "cmp" after writing. Because of unresolved legal problems with miboot, the official builds of the new debian-installer cannot contain working (boot-) floppies images. But they are available at http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy-2.4/ (Be "warned" that these are unstable builds of d-i which install Debian sid. When rc3 is is available, we'll make sure that there will be unofficial rc3-builds with miboot, which then can be used to install sarge.) You could also try ../floppy/ which contains floppy images with 2.6 kernel - if you have success with those please report it. (I never had.) > Can someone please give me a pointer at what to do? I really want to > resolve this issue, it has been occupiing me for a while. Feel free to ask again, if needed... regards, Holger pgpF1o8pMps4J.pgp Description: PGP signature
Re: Problem installing on PowerMac 8600
Hi Patrick, On Thursday 24 February 2005 02:47, Patrick Bachmann wrote: > Well, I went to Staples and got me a new set of floppies that even have a > two year guarantee on them, but it still didn't work. well, you might use brand new floppies, but the problem could also be your old floppy drive... and even new floppies fail sometimes. so: floppies smell+are rotten but sometimes the only choice... > > Always write floppies with "dd" and compare them with "cmp" after > > writing. > That's how I did it for all floppies. cmp can't find any difference. But > the images just don't get recognized by the Macintosh to be bootable. might be, that you mac drive has some problems reading floppies written by another drive. > > But they are available at > > http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy-2.4/ > Hm, I tried those today, but got still no luck. If you replace "daily" with "2005-02-18" I can assure you, that floppy-2.4/boot.img works here on a pmac 7200. Current dailys should also work, but as you experience strange floppy problems go for a known good source. Oh, and if you managed to boot and begin your installation with d-i, and this fails in a later stage (after loading the root-floppy)- then you might have to go for the daily builds as a transition is happening in d-i _now_ and 2005-02-18 is a little old ;) > Tomorrow afternoon, I'll be paying the CS-department's cluster a visit and > try to write the images there. I have only two working floppy-drives in my > apartment and neither can write bootable images. No written image gets > recognized but the woody install image with the earlier described result. Where did you write the woody image ? I almost got really crazy until I got my way around floppies. I made my first oldworld powerpc steps with a Pmac 4400 which would boot from a boot floppy just fine but _never_ managed to read the root floppy. Took me some days to believe that - fortunatly I had another 4400 at that time, tried this, and it read the the boot+root floppy just fine. So, floppies really suck, try to avoid if possible. But sometimes it's not ;) So, in short, have patience & don't give up. regards, Holger pgpRMUw8ooNJo.pgp Description: PGP signature
Re: giveaway: Beige G3 - complete system (Switzerland)
Hi Tormod, On Thursday 07 April 2005 15:33, Tormod Volden wrote: > I want to get rid of my Power Macintosh G3 (beige desktop), since I am > gonna move. It would be nice if it could be used by (and/or): > > 1) someone developing, testing or using Debian (or some other free OS) > 2) someone who can't afford to buy a system > 3) someone near to Zurich, Switzerland (because of shipping cost) > > I realize that the combination of 2 and 3 is not easy ;) So I only qualify for 1) :-) And 2... (but only for testing purposes...) I do work on FAI (fully automatic installation of debian+more, see www.informatik.uni-koeln.de/fai) for powerpc and also do occasionally work on the new debian installer, also mainly on powerpc. Your machine is espacially interesting as it's the fastest "oldworld" machine available. (I also have good contacts with the quik (oldworld bootloader) maintainer, I've seen quik problems on the g3 beige for a long time and would really like to work on a solution for that problem...) Currently I only have an pmac 7200 and a pmac 4400 as test machines (I also do have two faster ppc machines but realyl cannot use them for testing as they are in "production use" > Any suggestions for what to do with it are welcome. I would pay the shipping costs, so you could ship it to me. But not the monitor and printer, please :-) So, if you still got that machine and nobody wanted it, I would gladly take it. If it's allready taken, anyway thanks for the offer :-) regards from Hamburg, Holger pgphU9oMiBQHM.pgp Description: PGP signature
Re: Orphaned kernel config project for PowerBook G4
Hi, On Monday 25 April 2005 20:18, Johannes Mockenhaupt wrote: > > Hence two questions, the first is who would like to take over the > > maintenance of this configuration and hosting of the web pages (you > > could source forge it). > Creating a sourceforge project might be a bit overkill and there are a > lot of small pages covering ppc realated topics already, so how about > merging your page with a project like PPCConfDB[1]? just curious: why don't you work within debian and push the config (it's nothing more, isn't it?) into the proper kernel packages ? regards, Holger pgp4Rzd0Z22M8.pgp Description: PGP signature
[powerpc] simplifying and updating http://www.debian.org/devel/debian-installer/ports-status
Hi, http://www.debian.org/devel/debian-installer/ports-status is IMHO a bit confusing and missing some infos: - for oldworld cd- and net-booting a note should be added: "needs booting from OpenFirmware" (this is currently not described in the manual - if it's added (it's on my list for today to properly document it, so it can be added), IMHO a link to the relevant section in the manual should be added as well, or not) - apple g5 is available now (in sarge or sid) ?! afaik it takes the power4 kernel and the powerpc userland ?! - notes should be added to power3 rs6k and power4 rs6k: 32bit mode only. - "power3 IBM rs6k" and "power4 IBM rs6k" use the same images, merge them into one subarch column - d-i for IBM pseries is available and uses the same Images as power4 -> merge them into one subarch column - "powerpc ibm rs6k" uses the same images as "chrp" -> merge them into one subarch column - power3 IBM RS6000 netboot rc3-link is broken: typo: "netboo" :) - mention the unsupported rs6k models as notes. Please correct my assumption or confirm them! I'll will provide a proper patch (to the wml-source) for another round of reviews when these questions are clear... regards, Holger afaik the following rs6ks exist : power 1 - MCA power 2 - MCA ppc32 - MCA ppc32 - prep ppc32 - chrp power3 - chrp ? power4 - ? power5 - ? anything - MCA is not supported as in no kernel :) afaik d-i doesnt support mca, not really sure about ppc32-prep linux kernel doesn't support mca either so :) pgpRaxSkQ5ChU.pgp Description: PGP signature
ibook2.2, sarge, kernel2.6.8 & devfsd: no sound, no cd-writing
Hello, I have an ibook2.2, which is running sarge with kernel-image-2.6.8-powerpc (2.6.8-3) and devfsd now. processor : 0 cpu : 750FX temperature : 19-21 C (uncalibrated) clock : 800MHz revision: 2.2 (pvr 7000 0202) bogomips: 1585.15 machine : PowerBook4,3 motherboard : PowerBook4,3 MacRISC2 MacRISC Power Macintosh detected as : 257 (iBook 2 rev. 2) pmac flags : 000b L2 cache: 512K unified memory : 640MB pmac-generation : NewWorld matrix:~$ cat /proc/version Linux version 2.6.8-powerpc ([EMAIL PROTECTED]) (gcc version 3.3.4 (Debian 1:3.3.4-9)) #1 Fri Aug 27 18:02:26 CEST 2004 My problems are no sound (no errors, xmms plays without problems, but there _is_ no sound) and not being able to burn cd (process hangs) With woody (and adrian bunks backported packages for kernel 2.6 on woody (rebuildt for powerpc)) and kernel-2.6.7-powerpc (deb from sarge) I had sound without problems. but using that kernel-package on sarge doesnt give me sound. should I use ALSA or OSS on this machine with kernel 2.6 ? I have "hdb=ide-scsi devfs=mount" on my kernel-commandline (yaboot.conf), the user trying to use sound is in the group "audio" and the following modules in /etc/modules: "auto usbkbd usb-uhci keybdev mousedev hid sungem dmasound_pmac hfs agpgart uninorth-agp radeon ide-scsi ide-cd sr_mod sg usb-storage ehci-hcd hci_usb ohci-hcd usbhid aes cryptoloop" Should I use ALSA (with these two modules. snd-powermac, snd-pcm-oss) instead ? matrix:~$ cat /dev/sound/unknown6 PowerMac Snapper DMA sound driver rev 016 : Core driver edition 01.06 : PowerMac Built-in Sound driver edition 00.07 HW rates: 44100 s/sec HW AFMTS: signed 16 bit BE === Formats & settings === Parameter softhard Format :signed 16 bit BEsigned 16 bit BE Samp Rate: 44100 s/sec 44100 s/sec Channels : stereo stereo === Sound Queue status === Allocated: Buffers Size write: 4 32768 read: 0 0 Current : MaxFrg FragSiz MaxAct Frnt Rear Cnt RrSize A B S L xruns write: 44096 40 -1 0 0 0 0 0 0 6 read: 0 0 000 0 0 0 0 0 0 0 matrix:~$ ls /dev/sound/ -la total 0 drwxr-xr-x 1 root root 0 Jan 1 1970 . drwxr-xr-x 1 root root 0 Jan 1 1970 .. crw-rw 1 root audio 14, 3 Jan 1 1970 dsp crw-rw 1 root audio 14, 0 Jan 1 1970 mixer crw-rw 1 root audio 14, 6 Jan 1 1970 unknown6 xmms plays my music without error, but I cannot hear anything :( Last, should I file a bug ? any help & hints are very much appreciated. regards, Holger p.s.: this system is installed with fai (packages.debian.org/fai), so every debconf-question was answered with the default values.
Re: Plea for help from PowerMac Open Firmware gurus -- Testing newoldworld pmac miboot 2.6 floppies
Hi, I was busy with lots of "real life stuff", so I was away from debian-boot a while... I'm sorry for that ;-) > > So I'm no longer so sure as I once was that the parameters after "boot" > > in Open Firmware are getting passed to the kernel. Is it possible to > > modify the boot-parameters that are compiled into the kernel? For > > example, the "ofonlyboot" kernel differs from the "boot" kernel only in > > that there is a string "video=ofonly" in the former, but not in the > > latter. How does that get there? Maybe the same mechanism could be used > > to give it the "debug" and "console=ttyS0" options... > > I have the feeling that those are set using the rsrce utility. In the d-i > build, they are set in > installer/build/config/powerpc/powerpc/floppy/boot-ofonly.cfg : > > KERNEL_CMDL = root=0200 load_ramdisk=1 prompt_ramdisk=1 devfs=mount \ > video=ofonly > > and for boot.cfg : > > KERNEL_CMDL = root=0200 load_ramdisk=1 prompt_ramdisk=1 devfs=mount > > So, the best would be to build those floppies yourself and add these > values. > > They are then added to miboot config with : > > echo device $(TEMP_BOOT).new > $(TEMP)/miboot.conf; \ > echo kernel $(TEMP_KERNEL).gz $(KERNEL_CMDL) >> > $(TEMP)/miboot.conf;\ miboot -c $(TEMP)/miboot.conf; \ > > in installer/build/config/powerpc/powerpc/floppy.cfg > for the woody floppy there was a perl-script to set the command-line parameters. i'm not sure whether this script could be re-used so I've attached it, so you can have a look. Oh, and btw, I'm just installing my oldworld 4400/200 mac with d-i and the daily built 2.4-floppy images (with root.img and root-2.img) and it seems to work fine - right now. I'll keep you informed in another mail. regards, Holger patch-floppy-image.pl Description: Perl program
Re: ibook2.2, sarge, kernel2.6.8 & devfsd: no sound, no cd-writing
Hi, just in case someone has the same problems, I'll sum up what I've learned since then: - cd-burning as none-root is broken in kernel 2.6.8, use 2.6.7 or 2.6.9 (not available yet) - devfs is deprecated, use udev instead - in 2.6.8 oss-sound is working, alsa has some issues (playing to fast, some gaps) - i still _believe_ that i should switch to alsa if possible regards, Holger On Monday 13 September 2004 10:50, Holger Levsen wrote: > Hello, > > I have an ibook2.2, which is running sarge with kernel-image-2.6.8-powerpc > (2.6.8-3) and devfsd now. > > processor : 0 > cpu : 750FX > temperature : 19-21 C (uncalibrated) > clock : 800MHz > revision: 2.2 (pvr 7000 0202) > bogomips: 1585.15 > machine : PowerBook4,3 > motherboard : PowerBook4,3 MacRISC2 MacRISC Power Macintosh > detected as : 257 (iBook 2 rev. 2) > pmac flags : 000b > L2 cache: 512K unified > memory : 640MB > pmac-generation : NewWorld > > matrix:~$ cat /proc/version > Linux version 2.6.8-powerpc ([EMAIL PROTECTED]) (gcc version 3.3.4 (Debian > 1:3.3.4-9)) #1 Fri Aug 27 18:02:26 CEST 2004 > > My problems are no sound (no errors, xmms plays without problems, but there > _is_ no sound) and not being able to burn cd (process hangs) > > With woody (and adrian bunks backported packages for kernel 2.6 on woody > (rebuildt for powerpc)) and kernel-2.6.7-powerpc (deb from sarge) I had > sound without problems. but using that kernel-package on sarge doesnt give > me sound. > > should I use ALSA or OSS on this machine with kernel 2.6 ? > > I have "hdb=ide-scsi devfs=mount" on my kernel-commandline (yaboot.conf), > the user trying to use sound is in the group "audio" and the following > modules in /etc/modules: "auto usbkbd usb-uhci keybdev mousedev hid sungem > dmasound_pmac hfs agpgart uninorth-agp radeon ide-scsi ide-cd sr_mod sg > usb-storage ehci-hcd hci_usb ohci-hcd usbhid aes cryptoloop" > > Should I use ALSA (with these two modules. snd-powermac, snd-pcm-oss) > instead ? > > matrix:~$ cat /dev/sound/unknown6 > PowerMac Snapper DMA sound driver rev 016 : > Core driver edition 01.06 : PowerMac Built-in Sound driver edition 00.07 > HW rates: 44100 s/sec > HW AFMTS: signed 16 bit BE > === Formats & settings === > Parameter softhard > Format :signed 16 bit BEsigned 16 bit BE > Samp Rate: 44100 s/sec 44100 s/sec > Channels : stereo stereo > === Sound Queue status === > Allocated: Buffers Size > write: 4 32768 > read: 0 0 > Current : MaxFrg FragSiz MaxAct Frnt Rear Cnt RrSize A B S L xruns > write: 44096 40 -1 0 0 0 0 0 0 6 > read: 0 0 000 0 0 0 0 0 0 0 > > > matrix:~$ ls /dev/sound/ -la > total 0 > drwxr-xr-x 1 root root 0 Jan 1 1970 . > drwxr-xr-x 1 root root 0 Jan 1 1970 .. > crw-rw 1 root audio 14, 3 Jan 1 1970 dsp > crw-rw 1 root audio 14, 0 Jan 1 1970 mixer > crw-rw 1 root audio 14, 6 Jan 1 1970 unknown6 > > xmms plays my music without error, but I cannot hear anything :( > > Last, should I file a bug ? > > > any help & hints are very much appreciated. > > regards, > Holger > > p.s.: this system is installed with fai (packages.debian.org/fai), so every > debconf-question was answered with the default values.
modifying/modified powerpc boot-floppies (was Re: Testing newoldworld pmac miboot 2.6 floppies
Hi, On Saturday 18 September 2004 10:03, Jens Schmalzing wrote: > The resource is called CMDL. More detailed instructions are here: > http://portal.suse.com/sdb/en/2000/06/olh_ppc_miboot.html> ok, this is cool for everybody who as macos. but i would really like to see a linux-only solution. a question: the daily build powerpc floppies still use miboot - will this still be included within sarge or will they get removed / replaced ? an idea: for woody there was patch-floppy-image.pl (attached), which is a simple perl script which will search and replace the boot params in the floppy image. couldn't we provide a similar solution for sarge ? I tried it (with http://people.debian.org/~luther/debian-installer/daily-powerpc-built/daily/powerpc/floppy-2.4/boot.img from september 13th), but had no luck. I used "hexedit" and found parts of the commandline around 6008 - but I only found parts of it. Looking at boot-floppy-hfs.img from woody (http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/powermac/images-1.44/) I found the complete commandline with hexedit at 00018e74 - that's why patch-floppy-image.pl work back in those days. another idea: sven, could you please daily build two (2.4/2.6) more boot floppies, with the extra kernel commandline parameter "mirror/suite=unstable" ?! That way, it would be much easier to test sid d-i on oldworld machines which can only boot from floppy - and where going back and manually downgrading the d-i priority is a very boring task as oldworld machines are mostly slow. would be very nice & helpful! regards, Holger patch-floppy-image.pl Description: Perl program
Re: Plea for help from PowerMac Open Firmware gurus -- Testing newoldworld pmac miboot 2.6 floppies
Hi, miboot is used on them as well. regards, holger On Sunday 19 September 2004 17:26, Christian Leimer wrote: > I found that website > http://mike.quintero.staff.noctrl.edu/slackintosh/ > which offers two boot disks. I dont test them but they are for Linux. If > they dont use miboot it may help for building debian boot floppies. > Can you test and report about them. Thanks. > > Bye Chris.
Re: ibook2.2, sarge, kernel2.6.8 & devfsd: no sound, no cd-writing
Hi, > This is not true anymore i have no problem burning CDs and DVDs with the > current 2.6.8 and cdrecord in sid. thanx - with 2.6.8-3 (from sarge) and cdrecord from sid (with or without recompilation with dvd-patch) i can burn CD-RWs as root and as user. but still, k3b doesnt find a cd-writer with 2.6.8, but does find it with 2.6.7. regards, holger
missing udev permissions
for power management of ibooks Date: Sat, 25 Sep 2004 02:41:05 +0200 User-Agent: KMail/1.6.2 Cc: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Disposition: inline X-KMail-Transport: Layer-Acht Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <[EMAIL PROTECTED]> Status: R X-Status: NQ X-KMail-EncryptionState: X-KMail-SignatureState: X-KMail-MDN-Sent: Hi, I believe the following devices are missing from /etc/udev/permissions.d/udev.permissions (udev, Version: 0.031-2, sarge install with kernel-image-powerpc-2.6.8): adb:root:users:0660 pmu:root:users:0660 input/event*:root:users:0660 I needed them to be able to use "fnset" as user, and pbbuttons-setupenv suggested them as well. Also I'm not sure into which group these files belong as I don't really know any deeper details about the devices. (And I am a little tired as well ;) regards, Holger
Re: missing udev permissions
Hi, On Saturday 25 September 2004 20:01, Brad Boyer wrote: > On Fri, Sep 24, 2004 at 07:41:15PM -0500, Holger Levsen wrote: > > I believe the following devices are missing > > from /etc/udev/permissions.d/udev.permissions (udev, Version: 0.031-2, > > sarge install with kernel-image-powerpc-2.6.8): > > > > adb:root:users:0660 > > pmu:root:users:0660 > > input/event*:root:users:0660 > > > > I needed them to be able to use "fnset" as user, and pbbuttons-setupenv > > suggested them as well. > > > > Also I'm not sure into which group these files belong as I don't really > > know any deeper details about the devices. (And I am a little tired as > > well ;) > > I honestly cannot suggest allowing regular users to access /dev/adb. It > is a raw interface directly onto the bus, and you can really mess up > stuff if you misuse it. The code does try to prevent a few things by > paying a little attention to what you send, but the code for it is most > certainly not written with user access in mind. > > I understand that several utilities like fnset and trackpad use it > anyway, but I still think it's a bad idea to allow users full access. Ok, after reading this i fully agree that giving it to the group users is a bad idea. Do you think it's a good idea to treat the three above mentioned devices the same ? On Wednesday 29 September 2004 03:13, Bryan Forbes wrote: > For my machine, I have this in a pmud.permissions file > in /etc/udev/permissions.d: > > pmu:root:pmu:660 > > Then I added myself to the pmu group. Works like a charm, and I'd say > it's fairly secure. I've thought about proposing this to the developer > of pmud or pbbuttonsd, but never got around to it. Would this be a sane approach for a default install ? Give a warning about the implied security implications and ask which users to add to the pmu group (which has to be created as well)... At the moment these devices are not mentioned in /etc/udev which I believe is a bug. (I'm not really looking for a solution only for myself (then I could easily give the devices to my users main group) but a more general approach which works out of the box.) thanx for your replies, regards, holger
Re: No HFS driver, and "change install priority" menu option missing -- and other bugs found while testing 2.4 boot floppies on OldWorld PowerMac
Hi, > > However... There is one important thing missing from the boot > > disks. Specifically, the "System" file is zero length. This is > > true of both boot and ofonlyboot for both 2.4 and 2.6. It won't > > boot that way. > Arg, again. I have to checkup and see what is missing in the build process, > but i will not be able to do so until friday. I just successfully booted the kernel from http://people.debian.org/~luther/d-i/images/2004-09-29/powerpc/floppy-2.4/boot.img and was asked for the root floppy. (on a power mac 4400/200) http://people.debian.org/~luther/d-i/images/2004-09-29/powerpc/floppy/boot.img loaded, the background went black from gray, the colors of the tiny tux went inverse, and that's it :( regards, Holger
please test new quik with initrd-support (was: Re: getting quik into sarge?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, cc:s added to gain more attention, reply-to: set. On Friday 26 November 2004 10:17, [EMAIL PROTECTED] wrote: > i'm the current maintainer of quik, the oldworld PPC bootloader. i'm > currently sponsored by Jakko Niemi. there have been many code changes > made to it, including fixing bug #259359. for instance, initrd support, > using chosen/bootargs in OF, and a couple of other things. i would like to point out that the default kernel for powerpc is 2.6 and that the debian kernel packages for 2.6 need initrd support - so this is needed to be able to use the default debian kernels on oldworld (with a free bootloader). so this quik is desirable for d-i, too. > since it's in Section: base, and Priority: important, and there are many > positive changes to it, i thought it should go into > sarge-proposed-updates. is there any objection to this? no, but as far as i know the initrd code has "only" been tested on three machines: ANS, pmac 4400 and pmac 7200. If you got access to another oldworld machine please test and report it. > BTW, many thanks to go Peter 'p2' De Schrijver for his tremendous help in > making it even possible to close that bug, as it was a pretty hefty bug. yup! :-) and, better not to forget, the new quik.deb is available at http://www.ulyssis.org/~p2/debjes/ regards, Holger -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBpv5YUHLQNqxYNSARAnr2AJ9uUEnJw33vOqE3OvxrQZx/4tI+9gCfRaxl qXY98lBKp9DVE+aI+J7XoAI= =8kK4 -END PGP SIGNATURE-
entering sleep mode quietly/non-verbose
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, each time my ibook g3 enters sleep mode, the displays switches from graphics to text console and displays some kernel stufff, which is pretty useful for debugging etc. But this doesn't look really pretty in everyday operations - especially for people who are not interesting in kernel debugging every day ;-) So I wonder if there is this option somewhere in the kernel or in which BTS I should submit this wishlist bug ;-) regards, Holger (who likes debug infos - but who also likes to turn them off - sometimes ;) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBrtkFUHLQNqxYNSARArGgAJ9RX4SrL7Pb0/DhSLRkby3YXrE+OgCeJa+R irZDEWAUuSwlX0QmnFIv3Ls= =nh4T -END PGP SIGNATURE-
Summary / new quik available (was Re: please test new quik with initrd-support (was: Re: getting quik into sarge?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Peter 'p2' De Schrijver has made some new updates to the quik - you can get it (.deb and source) at the http://www.ulyssis.org/~p2/debjes/ changes include: - manpage tells about initrd - compiles with gcc3 - sprintf bug fixed - ANS raid support quik with initrd has been tested on - - ANS (Peter 'p2' De Schrijver) - - PMac 4400/200 (me) - - PMac 6500/250 (Romain Francoise) - - PMac 7200/90 (Peter 'p2' De Schrijver, me) - - PMac 9500 (Jaakko Niemi) - - PMac Beige G3 Rev II (Simon Vallet) If you got an(other) oldworld machine, please test this quik while installing the latest kernel-image-2.6.8-powerpc.deb (contains an initrd). Nobody mentioned to have tried with less than 32mb ram, if you do, please report your results as well. Colin Watson wrote: > This seems to be inappropriately built as a native package. If it were > built non-native then it would be easier for me to look over the > .diff.gz to see the changes from upstream. Still on the todo list - should be done as fast as possible to be able to achieve the goal of inclusion in sarge.. ;-) regards, Holger -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBsIxXUHLQNqxYNSARApY3AJ992wMaZX5fF7xK0Uly9zvv6JRvhgCfZfhy FUBb29pI2Wc4+msxMRyw8mY= =u/oi -END PGP SIGNATURE-
SOLVED: Re: entering sleep mode quietly/non-verbose
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Friday 03 December 2004 08:30, Colin Leroy wrote: > You can add fblevel 0 and fblevel 15 in /etc/power/pmcs-pbbuttonsd > script, in suspend and resume case... It should work. Thanks! It does work nicely indeed ;-) Only X still looks a little bit sluggish when waking up, but it looks a lot better than before (IMHO). Also thanks to Ben for the explaination (and for all the code ;) Attached is "sleep-quiet", which I put into /etc/power/scripts.d/ and made a link to /etc/power/event.d/sleep-quiet. As I didn't find a way to determine the current fblevel easily - a level of 15 is assumed. If you know how to do this, I'd be happy to hear about it. regards, Holger -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBtGPiUHLQNqxYNSARAh4QAJ9Bx+Cm0oHKzIsmxwqCM7Jg2yArdwCghkgt BFvOP7dHG2GHlcGaXLAOPY0= =oUrM -END PGP SIGNATURE- sleep-quiet Description: application/shellscript
Re: SOLVED: Re: entering sleep mode quietly/non-verbose
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Monday 06 December 2004 15:22, Michael Schmitz wrote: > > Attached is "sleep-quiet", which I put into /etc/power/scripts.d/ and > > made a link to /etc/power/event.d/sleep-quiet. As I didn't find a way to > > determine the current fblevel easily - a level of 15 is assumed. If you > > know how to do this, I'd be happy to hear about it. > 'fblevel' with no option will report the backlight level. Arghh ;-) This is not stated in fblevels manpage :( btw, the manpage also tells me about a maximum vaue of 31 while my ibook (2.6.8) only gives me a maximum of 15. Would you mind to enhance those two things in the manpage ? Enhanced script attached. regards, Holger -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBtH6sUHLQNqxYNSARApItAJ9EokoIiMCoIlAw4YGA/y2OIZWJmwCfR7UK Azenbr7RbUubQbC4Cvu2PPw= =SzET -END PGP SIGNATURE- sleep-quiet Description: application/shellscript
Re: Magic for sid changeroot required on ppc?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Sunday 12 December 2004 15:53, Helge Kreutzmann wrote: > Hello, > I want to set up a sid changeroot on my ibook. I use the command > provided in the manual page of debootstrap: > > env LANG=C debootstrap sid /scr/build/chroot-sid/ > http://ftp.de.debian.org/debian/ > > It downloads and installs some debs, but always dies with [...] > P.S. I reported this a bug #285188 but did not yet got a reply. in the bugreport I can see that you're using debootstrap from woody ?! IIRC you need a newer debootstrap - so, build debootstrap from testing, install it into your woody system, then debootstrap sid. This should work. If it works, and the info to your bug and please it. regards, holger -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBvGuOUHLQNqxYNSARAvjGAKC4j4qZaUKVHHvKfmfkauxMIbCfzgCgkbOc KMekw6Lj8HGvdRex1u/Qu38= =kcqv -END PGP SIGNATURE-
Re: Magic for sid changeroot required on ppc?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Monday 13 December 2004 10:56, Helge Kreutzmann wrote: > ok, I solved it: I mounted the partition with nodev, hence no > /dev/null and friends. good that you found the reason... ;) > Now it misses a dependency of pppoeconf on gettext, but this time the > woody install worked, so I start from there. That's easy to fix: debootstrap --include=gettext sid . http://ftp.de.debian.org/debian/ regards, Holger -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBvWs5UHLQNqxYNSARAoyvAJ9DVmTDF/iNLSjNyzaT5IxxjZ6azACff/BY vgOSangC/Q2Vg1cdv4F6edQ= =IdJK -END PGP SIGNATURE-
Re: gtkpbbuttons MacOSX theme
Hi, Guillaume, at most I can confirm your reports. Unfortunatly I think that's all. On Monday 13 December 2004 19:16, Guillaume Florey wrote: > Thanks for the help, but I cant find any gtkpbbuttons with ps -ax nor pid > in /var/run/ ... I can confirm this. It's so strange and it even has vanished (the ugly theme) a week, maybe two, ago or so. So I used to have two on-screen-displays, now I only have one, but...: a few days ago I had two again, for a few hours and now it's back to one (MacOSX theme, too). And I didn't touch it. The last time I was doing anything related to it, is more than four weeks ago. Strange indeed. > I'm running debian sarge with gtkpbbuttons 0.6.4-3 and pbbuttonsd 0.6.6 > from unstable Here it's sarge only. _Maybe_ it got fixed by an update two weeks ago, I haven't updated since then. Still it's strange, why I saw it again a few days ago. And, the progress-bar here also looks a bit uglier than on Guillaume's screenshots. I'm using ion2 as my window manager and start gtkpbbuttons manually (*) with "gtkpbbuttons -t MacOSX &". (*) to busy to decide which xDM to use: xdm, gdm, kdm, wdm. I haven't found the one which sucks less. And I'm using sleep mode mostly anyway ;) regards, Holger
Re: gtkpbbuttons MacOSX theme
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Monday 13 December 2004 22:29, Matthias Grimm wrote: > This is _not_ gtkpbbuttons! What you saw is the KDE laptoptool 'kmilo'. It > gets its informations also from pbbuttonsd but kmilo is not my project. Thanks. I was using kde before, and i'm still using some tools. So i guess somehow it got started by something. Exactly the reason why I'm moving away from kde... > If you don't like it :-) deinstall it. As I remember right there is no > other way to disable it. Arg :( regards, Holger -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBvs4NUHLQNqxYNSARAhn9AJ9Rv+TBGB9ytOQB6PJtOkTZ+avhLgCeKWxH Ru3hEKYDMzCXKQ4xtdbMlLc= =mJcf -END PGP SIGNATURE-
Re: howto move from yellow dog -> debian
Hi Russel, cc:ed cause I'm not sure wether you read the list... On Monday 10 January 2005 03:17, Russell McManus wrote: > I've got a 9600/MP running yellow dog linux, that I'd like to upgrade > to sarge. But I had some trouble with the sarge install cd, which I > have so far been unable to resolve. (See Message-ID: > <[EMAIL PROTECTED]>, subject line was "sarge > install help on 9600MP") According to your message, your network card (mace) was not detected. But you didn't tell which version of the debian-installer you've tried. Did you try the release candidate 2 from http://www.debian.org/devel/debian-installer ? (it has support for the mace driver.) If your system can only boot from floppy, you could also try http://ftp.debian.org/debian/dists/testing/main/installer-powerpc/rc2/images/powerpc/floppy-2.4/ > So I would like to ask: are there any nifty ways to install sarge from > a running, non-debian system? You could also bootstrap your system as Shyamal Prasa suggested. regards, Holger
d-i on pmac 9600 (was Re: howto move from yellow dog -> debian
Hi, On Monday 10 January 2005 17:17, Russell McManus wrote: > Holger Levsen <[EMAIL PROTECTED]> writes: > > On Monday 10 January 2005 03:17, Russell McManus wrote: > >> I've got a 9600/MP running yellow dog linux, that I'd like to upgrade > >> to sarge. But I had some trouble with the sarge install cd, which I > > According to your message, your network card (mace) was not > > detected. But you didn't tell which version of the debian-installer > > you've tried. Did you try the release candidate 2 from > > http://www.debian.org/devel/debian-installer ? (it has support for > > the mace driver.) > I downloaded an install iso from that site, not sure exactly which > one. The md5 sum of the iso I used is: > > MD5 (sarge-powerpc-1.iso) = a618fe6371390f2673b729ce673c3715 Well, this is the first cd of a full cd set. But I have no idea which one and google also doesn't know that md5-sum. > I couldn't find md5 sums for the iso's that are available to nail down > exactly which one I used. To be safe, you could just download a netinstall-image of rc2, it's only ~200mb. > > If your system can only boot from floppy, you could also try > > http://ftp.debian.org/debian/dists/testing/main/installer-powerpc/rc2/ima > >ges/powerpc/floppy-2.4/ > Thanks for the pointer. I haven't tried floppy booting, but I don't > think that will help, because the problem is not booting, but later on > during the install process. I'm pretty sure this is fixed in rc2. > Could the problem be related to the fact that I have an add-on pci NIC > inside the case in addition to the mc0 on-board interface? Maybe, dunno. For testing purposes you could unplug it :) > Thanks for taking the time to reply, much appreciated, > -russ you're welcome. If rc2 doesn't help, you should try to post on debian-boot@, this is the mailing list for the new installer. Alternativly, you could send a bug report (package: debian-installer). regards, Holger
Re: Installer problems on Beige PowerMac G3
Hi, On Wednesday 10 August 2005 17:56, Magnus Sandberg wrote: > I have some problems installing Debian Sarge on my OldWorld PowerMac. > I sent a bug report to the bugtracking system; > http://lists.debian.org/debian-boot/2005/08/msg00288.html > > Does any one has any ideas regarding thies problems? > Debian-installer-version: ? (I'm not by the machine right now) did you use the stable sarge installer or something newer ? The beige oldworld g3 have some known problems with OpenFirmware and quik, search for "quik quirks"... regards, Holger pgpfLqJeVGAOd.pgp Description: PGP signature
Re: got quik working with OldWorld G3 Beige 233MHz
Hi, On Thursday 07 October 2004 06:35, Duane Cottle wrote: > > Perhaps someone will step up and provide evidence to the contrary, > > but I'm pretty sure that quik doesn't support loading a ramdisk. I've > > never tried it myself, but I don't remember ever hearing about anyone > > doing it. > man quik.conf says it does, and d-i sets quik.conf up that way. > Not supported? That'd be news to me. man quik.conf is wrong, but d-i used to believe that . There are code fragments for initrd-supports in quik but not more. As the debian 2.6 kernels use initrds (and will continue to use them as they won't be changed so close to sarge getting released) they cannot work with quik. (see http://lists.debian.org/debian-boot/2004/09/msg01884.html for more info, look for "quik, bootx & initrd") If you need to use quik, you have to use the 2.4 kernels (with debian sarge standard kernel packages). Of course, you can build your own 2.6 kernels without initrd. So sarge / debian-installer will have to use 2.4.27 with quik - and I don't see this as a major problems as this old hardware is well supported with 2.4 and you still have the option to build a custom 2.6 kernel after installation. regards, Holger
Re: kernel-image-2.4.27-powerpc-smp-pmac unstable with CONFIG_HIGHMEM=y
Hi, [no debian 2.6 kernel packages with quik] > Well, actually, the only reason is the initrd. We could make a 2.6 > non-initrd kernel flavour for powerpc, which would solve those problems. I > bet Jens would be vetoing any such moves though. Why would Jens be vetoing ? regards, Holger
howto create boot-floppy-hfs.img for oldworld macs ?
Hello, I got an Apple Powermac 4400 and want to create a bootfloppy with a custom kernel for it but I fail. I manage to build a debian kernel package on another ppc machine with make-kpgg, but the vmlinux which is built is to big for a floppy: 3218566 2004-02-20 23:12:32 ./boot/vmlinux-2.4.23-ben1 1077339 2004-02-20 23:12:32 ./boot/vmlinux.coff-2.4.23-ben1 What is that vmlinux.coff ? Then I use hcopy from package hfsutils to copy kernel on woodys boot-floppy-hfs.img-floppy. When I boot the 4400 I see an image of a mac overlapped with the pinguin ;-) but after the disk is read the screen becomes black and the logo inverted. (The original boot-floppy-hfs.img-floppy boots the kernel just fine but chrashes when trying to mount the root filesystem.) Sometimes the logo get crossed by a red "X", what does that mean ? Then I tried building a kernel with "make bzImage" but neither of these files booted correctly: [EMAIL PROTECTED]:/usr/src/kernel-source-2.4.23-benh$ ls arch/ppc/boot/images/ -la insgesamt 8876 drwxrwxr-x2 root root 4096 21. Feb 01:00 . drwxrwxr-x 11 root root 4096 21. Feb 00:06 .. -rw-rw-r--1 root root 293 12. Okt 15:41 Makefile -rw-r--r--1 root root 1259719 21. Feb 01:00 miboot.image -rwxr-xr-x1 root root 1294427 21. Feb 01:00 vmlinux.coff -rwxr-xr-x1 root root 1365146 21. Feb 01:00 vmlinux.elf-pmac -rwxr-xr-x1 root root 1259442 21. Feb 01:00 vmlinux.gz -rwxr-xr-x1 root root 1360869 21. Feb 01:00 zImage.chrp -rwxr-xr-x1 root root 1360869 21. Feb 01:00 zImage.chrp-rs6k lrwxrwxrwx1 root root 12 21. Feb 01:00 zImage.pmac -> vmlinux.coff -rwxr-xr-x1 root root 1311434 21. Feb 01:00 zImage.prep How can a build a boot-floppy for an oldworld mac ? thank you very much for your help! And btw, I volunteer to help test debian-installer on oldwolrd-macs, too. But there are no boot floppies yet, does anybody know wether someone is working on them ? regards, Holger
Re: howto create boot-floppy-hfs.img for oldworld macs ?
hello, i read http://lists.debian.org/debian-boot/2004/debian-boot-200402/msg01478.html now, and indeed, I got a Peforma 4400, so I have to boot from floppy or fiddle a lot with hardware or hw & open firmware :( so I would rather like to get floppies working. regards, Holger Am Dienstag, 24. Februar 2004 19:18 schrieb Holger Levsen: > Hello, > > I got an Apple Powermac 4400 and want to create a bootfloppy with a custom > kernel for it but I fail. > > I manage to build a debian kernel package on another ppc machine with > make-kpgg, but the vmlinux which is built is to big for a floppy: > >3218566 2004-02-20 23:12:32 ./boot/vmlinux-2.4.23-ben1 >1077339 2004-02-20 23:12:32 ./boot/vmlinux.coff-2.4.23-ben1 > > What is that vmlinux.coff ? > > Then I use hcopy from package hfsutils to copy kernel on woodys > boot-floppy-hfs.img-floppy. > When I boot the 4400 I see an image of a mac overlapped with the pinguin > ;-) but after the disk is read the screen becomes black and the logo > inverted. (The original boot-floppy-hfs.img-floppy boots the kernel just > fine but chrashes when trying to mount the root filesystem.) > Sometimes the logo get crossed by a red "X", what does that mean ? > > Then I tried building a kernel with "make bzImage" but neither of these > files booted correctly: > > [EMAIL PROTECTED]:/usr/src/kernel-source-2.4.23-benh$ ls arch/ppc/boot/images/ > -la insgesamt 8876 > drwxrwxr-x2 root root 4096 21. Feb 01:00 . > drwxrwxr-x 11 root root 4096 21. Feb 00:06 .. > -rw-rw-r--1 root root 293 12. Okt 15:41 Makefile > -rw-r--r--1 root root 1259719 21. Feb 01:00 miboot.image > -rwxr-xr-x1 root root 1294427 21. Feb 01:00 vmlinux.coff > -rwxr-xr-x1 root root 1365146 21. Feb 01:00 vmlinux.elf-pmac > -rwxr-xr-x1 root root 1259442 21. Feb 01:00 vmlinux.gz > -rwxr-xr-x1 root root 1360869 21. Feb 01:00 zImage.chrp > -rwxr-xr-x1 root root 1360869 21. Feb 01:00 zImage.chrp-rs6k > lrwxrwxrwx1 root root 12 21. Feb 01:00 zImage.pmac -> > vmlinux.coff > -rwxr-xr-x1 root root 1311434 21. Feb 01:00 zImage.prep > > How can a build a boot-floppy for an oldworld mac ? > > thank you very much for your help! > > And btw, I volunteer to help test debian-installer on oldwolrd-macs, too. > But there are no boot floppies yet, does anybody know wether someone is > working on them ? > > regards, > Holger
Re: patch-floppy-image.pl
Hi,
> I´m searching for that perl script patch-floppy-image.pl which the
> installation manual of debian linuxppc mentions but I can´t find it anymore
> at the cvs.debian site. Does anyone have this script yet?? If yes, please,
> can you send it to me?
Not long ago I was also looking for it, it is attached. I found via
www.archive.org. There I searched for the URL where patch-floppy-image.pl was
located once and found it!
> Thanks!!!
> Clovis
you're welcome,
Holger
#!/usr/bin/perl -w
# patches powerpc hfs-boot-floppy.img with desired boot arguments
# for example, to create a boot floppy for a /dev/hda8 root:
# ./patch-floppy-image.pl 'root=/dev/hda8' boot-floppy-hfs.img > boot-hfs-hda8.img
# another example, add video=ofonly to the archive floppy image
# ./patch-floppy-image.pl 'root=0200 load_ramdisk=1 prompt_ramdisk=1 video=ofonly' boot-floppy-hfs.img > boot-video-ofonly.img
# We have 98 characters to work with in the floppy's System CMDL resource
# (Always maintain the right number of bytes in the floppy image)
my $absolute_max_length = 98;
# $current must be the same as what is currently inside
# boot-floppies/powerpc-specials/miBoot/System.bin.
my $current = "root=0200 load_ramdisk=1 prompt_ramdisk=1 adb_buttons=103,111 video=ofonly";
# I think it's a good idea to maintain "adb_buttons=103,111 "
# $maintain can be changed as needed; your boot arguments will be appended to it.
my $maintain = "adb_buttons=103,111 ";
my $pad_len = $absolute_max_length - length( $maintain );
my $new_arguments = shift;
if ( length( $new_arguments ) > $pad_len ) {
die "arguments longer than $pad_len characters; aborting"
}
$new_arguments = pack( "A$pad_len" , $new_arguments );
my $subst = $maintain . $new_arguments;
while (<>) { s|$current|$subst|; print }
2.4.26 from kernel.org or from benh tree ?
Hello, is it still "mandatory" to use Benjamins 2.4 repository or have all (or mostly all) patches been applied to 2.4.26/27 ? As I can see from this list, most of the effort is going into 2.6 now, which is good, but I still want to use 2.4 on my ibook for a while. (And for various reasons I want to build it by myself.) http://www.penguinppc.org/dev/kernel.shtml still says that the benh tree is the stable tree, but this page also talks about kernel 2.5, so I believe that page is outdated. (I will send them mails asking to corrrect the page when this question has been answered.) regards, Holger
Re: [Stretch] Status for architecture qualification
On Sun, Jun 05, 2016 at 01:26:39PM +0200, John Paul Adrian Glaubitz wrote: > ppc64: > > This architecture is basically on par with the release architectures. We have > over > 11.000 packages installed [...] > sparc64: > We are close to 11.000 installed packages. I'm not sure whether you are talking about source or binary packages but sid/amd64 has over 24000 source packages and over 5 binary packages, so I would call the above "on par". Or what am I missing? -- cheers, Holger signature.asc Description: Digital signature
Re: [Stretch] Status for architecture qualification
thanks to everyone explaining arch:any to me :) -- cheers, Holger signature.asc Description: Digital signature
Re: Bits from the Release Team (Jessie freeze info)
Hi, On Mittwoch, 23. Oktober 2013, Stewart Smith wrote: > Jenkins can have slaves on remote hosts, via SSH. It runs a small java > app there, so as long as the arch has a JVM then you're pretty right. that JVM is not even needed, just schedule jobs via ssh and be done. cheers, Holger signature.asc Description: This is a digitally signed message part.
