user mode linux on ppc32
Hi all, some days ago lynuxworks.com guys made an announcement about their port of uml on ppc32; after that Jeff Dike has received this work, you can read his article on usermodelinux.org (there's also a patch for uml on ppc64). As you can see in Jeff's article the code he has received is a 28MB tarball, i've downloaded it and tried to compile it "as is" without success. According to Jeff i've started to "diff" the whole code; i've sent him a patch, you can find it there: http://www.artha.org/shammash/ppc/uml-2.6.0-test9_x86_ppc.diff Since there was an amount of history files (file.c~), .orig, .patched, strange symlinks outside the source tree, great cuts of non i386/ppc code and also looping links, i hope to have understood correctly their work (if someone wants to check, i appreciate that) Now, next step is splitting up the uml code from lynxos code (their RTOS) and make it compiling somehow. If you are interested in coding/testing it you can ask Jeff. I think that he'll need an account on a ppc machine; perhaps Ben can send him his new macmini :) luca -- Beware of programmers who carry screwdrivers. -- Leonard Brandwein Linux Registered User # 286841 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] Set accel in radeon driver
Just wanted to verify if my fix has been included. Looks like it might
have fallen between the cracks. If needed I can repost it.
Thanks,
Martin
On Thu, Jan 20, 2005 at 03:18:45PM +1100, Benjamin Herrenschmidt wrote:
> On Sat, 2005-01-08 at 00:00 +0100, Sven Luther wrote:
> > On Fri, Jan 07, 2005 at 05:34:18PM +, Martin Habets wrote:
> > > The patch below enhances the FBIOGET_FSCREENINFO ioctl. It is used
> > > by the lcd_hack tool that Ben H wrote. Before this fix accel is set
> > > to 0 and lcd_hack aborts. With it, the tool works again.
> > >
> > > Please apply. Thanks,
> > > --
> > > Martin
> > >
> > > --- 2.6.8/drivers/video/aty/radeon_base.c.orig2005-01-07
> > > 16:55:49.0 +
> > > +++ 2.6.8/drivers/video/aty/radeon_base.c 2005-01-07 16:57:22.0
> > > +
> > > @@ -1812,9 +1812,12 @@ static int __devinit radeon_set_fbinfo (
> > >
> > > fb_alloc_cmap(&info->cmap, 256, 0);
> > >
> > > - if (noaccel)
> > > + if (noaccel) {
> > > info->flags |= FBINFO_HWACCEL_DISABLED;
> > > + info->fix.accel = FB_ACCEL_NONE;
> > > + } else
> > > + info->fix.accel = FB_ACCEL_ATI_RADEON;
> > >
> > > return 0;
> > > }
> >
> > benh, could you comment on this ? Does it make sense to include this in the
> > debian kernel ?
>
> Yes.
>
> Ben.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: d-i on a second hard drive in a G5
On Thu, Feb 03, 2005 at 02:39:48PM -0800, Brad Boyer wrote: > On Thu, Feb 03, 2005 at 10:13:17AM -0500, Pedro Sanchez wrote: > > 4. /target/etc/yaboot.config (as installed by the d-i): > > > > boot=/dev/sdb2 > > device=/[EMAIL PROTECTED]/[EMAIL PROTECTED]: > > This last line seems odd. My G5 has only one disk and has a very > similar line for device. That makes me think that it isn't getting > the right OF path for /dev/sdb2. I would have expected the second > drive to be on the second sata channel. Without having a second > device on sata on my G5, I can't really test, but it seems worth > investigating for someone who knows the installer better. The installer uses ofpath to translate from device nodes to open firmware paths. Pedro: Can you run the following commands in Linux: ofpath /dev/sda ofpath /dev/sdb My guess is that ofpath does not output the correct path for your second harddisk. You can see the whole open firmware device-tree in /proc/device-tree or by entering open firmware and issuing dev / ls If my guess is correct and ofpath does not give you the correct device path then please file a bug on the yaboot package, which contains ofpath. BTW, you can directly load the second-stage yaboot from open firmware with something like this: boot openFirmwarePath:partition,\yaboot If you are new to OpenFirmware you will find some usefull information on http://d-i.alioth.debian.org/manual/en.powerpc/ch05s01.html (look into the usb booting section) Gaudenz signature.asc Description: Digital signature
bounty for fixing ALSA's powermac driver
According to the following BTS entry, the ALSA maintainer assigned to the snd-powermac driver doesn't even have any Mac to play with: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=306 This prooves that all attempts at fixing the driver have been shooting in the dark. No f* wonder the snd-powermac driver is such a mess! Wouldn't it be a good idea to place a bounty to encourage Ubuntu PPC developers to get around fixing snd-powermac for all Mac PPC chips? -- Martin-Éric Racine http://www.iki.fi/q-funk/
Re: bounty for fixing ALSA's powermac driver
ben mentioned some thoughts he had on improving the driver, many of which (or mainly from what i read) involved dividing up the driver into chipset groups... something like that as obviously not every mac has the same sound hardware but for some wierd reason we just have an all in one driver (which has its pros and cons) seperating it up into chipset groups means that perhaps a few people will be inconvenienced, but that people will be more able (and perhaps more willing) to bug fix and tweak. i for one, not being much of a kernel hacker, am terrified of potentially fiddling with a monolithic driver please forgive me if im wrong. Dean Martin-Éric Racine wrote: According to the following BTS entry, the ALSA maintainer assigned to the snd-powermac driver doesn't even have any Mac to play with: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=306 This prooves that all attempts at fixing the driver have been shooting in the dark. No f* wonder the snd-powermac driver is such a mess! Wouldn't it be a good idea to place a bounty to encourage Ubuntu PPC developers to get around fixing snd-powermac for all Mac PPC chips? -- WWW: http://dean.bong.com.au LAN: http://www.bong.com.au EMAIL: [EMAIL PROTECTED] or [EMAIL PROTECTED] ICQ: 16867613 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bounty for fixing ALSA's powermac driver
On Fri, Feb 04, 2005 at 02:21:33PM +0200, Martin-Ãric Racine wrote: > According to the following BTS entry, the ALSA maintainer assigned to the > snd-powermac driver doesn't even have any Mac to play with: > > https://bugtrack.alsa-project.org/alsa-bug/view.php?id=306 > > This prooves that all attempts at fixing the driver have been shooting in > the dark. No f* wonder the snd-powermac driver is such a mess! > > Wouldn't it be a good idea to place a bounty to encourage Ubuntu PPC > developers to get around fixing snd-powermac for all Mac PPC chips? Oh yes, I would support that. Wouter van Heyst
Auctex on iBook fails (same version works on x86)
I've got the auctex package (advanced tex/latex mode for emacs) on several boxes and it works just fine on the x86 boxes but on my iBook it fails with the error: File mode specification error: (error "Lisp nesting exceeds max-lisp-eval-depth") There are also numerous such errors in the installation log (I have saved same but it's not obviously that informative so I'll only post it here if anyone thinks they can get anything from it). The auctex version is 11.54-4 and emacs is 21.3+1-8 on all boxes (Debian Sarge). Does anyone here have any feeling as to whether this is a packaging problem, a configuration problem on my iBook (and if so what) or an upstream problem? FWIW auctex does work with "carbon emacs" on the Mac OSX side. TIA James -- ++---+-+ | James Tappin | School of Physics & Astronomy | O__| | [EMAIL PROTECTED] | University of Birmingham | -- \/` | | Ph: 0121-414-6462. Fax: 0121-414-3722 | | ++-+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bounty for fixing ALSA's powermac driver
Hi! On Fri, Feb 04, 2005 at 02:21:33PM +0200, Martin-Éric Racine wrote: > > Wouldn't it be a good idea to place a bounty to encourage Ubuntu PPC > developers to get around fixing snd-powermac for all Mac PPC chips? Sorry but I failed to parse your message. Are the Ubuntu people setting a bounty? Or you want us to set a bounty so that Ubuntu people can fix the problem and get the money? In the second case, what the fsck do the Ubuntu people have to do with anything? Can we target that bounty to whoever fixes the problem, and not just them? On the other hand, I am sorry I have not put any money to BenH's pool, but I am in the process of buying a house and I am rather broke. Anyway, I would put a bounty, I would give it to BenH and then I would think about a second bounty for the sound problems. (In case is not obvious, I am trying to say that Ben deserves, among others (M.Daenzer, Guido come to mind right now), a bounty for all the work he has already done for, say, iBookG4 sleep) -- Jesus Climent info:www.pumuki.org Unix SysAdm|Linux User #66350|Debian Developer|2.6.10|Helsinki Finland GPG: 1024D/86946D69 BB64 2339 1CAA 7064 E429 7E18 66FC 1D7F 8694 6D69 Good night and sweet dreams... which we'll analyze in the morning. --Dr Alex Brulov (Spellbound) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: d-i on a second hard drive in a G5
On Fri, 2005-02-04 at 11:10 +0100, Gaudenz Steinlin wrote: > On Thu, Feb 03, 2005 at 02:39:48PM -0800, Brad Boyer wrote: > > On Thu, Feb 03, 2005 at 10:13:17AM -0500, Pedro Sanchez wrote: > > > 4. /target/etc/yaboot.config (as installed by the d-i): > > > > > > boot=/dev/sdb2 > > > device=/[EMAIL PROTECTED]/[EMAIL PROTECTED]: > > > > This last line seems odd. My G5 has only one disk and has a very > > similar line for device. That makes me think that it isn't getting > > the right OF path for /dev/sdb2. I would have expected the second > > drive to be on the second sata channel. Without having a second > > device on sata on my G5, I can't really test, but it seems worth > > investigating for someone who knows the installer better. > > The installer uses ofpath to translate from device nodes to open > firmware paths. Pedro: Can you run the following commands in Linux: > > ofpath /dev/sda > ofpath /dev/sdb > Here's what I get: #ofpath /dev/sda /[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]: #ofpath /dev/sdb /[EMAIL PROTECTED]/[EMAIL PROTECTED]: So indeed it seems that ofpath has decided that both sata drives are "[EMAIL PROTECTED]" :| I manually edited the yaboot config file to have device=/[EMAIL PROTECTED]/[EMAIL PROTECTED]: and then I run the command chroot /target ybin --config /etc/yaboot.conf -b /dev/sdb2 Unfortunately this doesn't change anything. Selecting "l" in the text boot menu still sends me back to the graphical boot menu. Maybe the ybin command that I used is not right? -- Pedro > My guess is that ofpath does not output the correct path for your second > harddisk. You can see the whole open firmware device-tree in > /proc/device-tree or by entering open firmware and issuing > > dev / > ls > > If my guess is correct and ofpath does not give you the correct device > path then please file a bug on the yaboot package, which contains > ofpath. > > BTW, you can directly load the second-stage yaboot from open firmware > with something like this: > > boot openFirmwarePath:partition,\yaboot > > If you are new to OpenFirmware you will find some usefull information on > http://d-i.alioth.debian.org/manual/en.powerpc/ch05s01.html > (look into the usb booting section) > > Gaudenz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bounty for fixing ALSA's powermac driver
On Sat, Feb 05, 2005 at 12:49:31AM +1100, Dean Hamstead wrote: > ben mentioned some thoughts he had on improving the > driver, many of which (or mainly from what i read) > involved dividing up the driver into > chipset groups... something like that > as obviously not every mac has the same sound hardware > but for some wierd reason we just have an all in one > driver (which has its pros and cons) > > seperating it up into chipset groups means that > perhaps a few people will be inconvenienced, but > that people will be more able (and perhaps more > willing) to bug fix and tweak. i for one, not > being much of a kernel hacker, am terrified > of potentially fiddling with a monolithic driver > > please forgive me if im wrong. I wonder, which chipsets support hardware mixing (so you do not have to use esoud/dmix/whatever), if any. [...] wrobell <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Auctex on iBook fails (same version works on x86)
hi, on my ibook g3 it seems to work without problem (though there might be problems that i havent encountered yet), versions are the same: ii auctex 11.54-2 An integrated environment for... ii emacs21 21.3+1-8The GNU Emacs editor cheers float On Fri, Feb 04, 2005 at 02:27:50PM +, James Tappin wrote: > I've got the auctex package (advanced tex/latex mode for emacs) on > several boxes and it works just fine on the x86 boxes but on my iBook it > fails with the error: > File mode specification error: (error "Lisp nesting exceeds > max-lisp-eval-depth") > > There are also numerous such errors in the installation log (I have > saved same but it's not obviously that informative so I'll only post it > here if anyone thinks they can get anything from it). > > The auctex version is 11.54-4 and emacs is 21.3+1-8 on all boxes (Debian > Sarge). > Does anyone here have any feeling as to whether this is a packaging > problem, a configuration problem on my iBook (and if so what) or an > upstream problem? > > FWIW auctex does work with "carbon emacs" on the Mac OSX side. > > TIA > James > > > -- > ++---+-+ > | James Tappin | School of Physics & Astronomy | O__| > | [EMAIL PROTECTED] | University of Birmingham | -- \/` | > | Ph: 0121-414-6462. Fax: 0121-414-3722 | | > ++-+ > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Auctex on iBook fails (same version works on x86)
[Copy by mail since I don't know whether posting to the Usenet mirror will propagate back to the list] James Tappin <[EMAIL PROTECTED]> writes: > I've got the auctex package (advanced tex/latex mode for emacs) on > several boxes and it works just fine on the x86 boxes but on my iBook it > fails with the error: > File mode specification error: (error "Lisp nesting exceeds > max-lisp-eval-depth") > Suspect #1: emacspeak-17. Suspect #2: conflicting remains of a previous manual AUCTeX installation. In either case M-x list-load-path-shadows RET should give you a clue about the problem. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bounty for fixing ALSA's powermac driver
Rather than complainting, maybe someone can offer access to their Mac. Either physical or via ssh. Usually the real guru's don't need much time to put things right. (having said that, the cleanup Ben suggested would be a big effort) I use the powermac driver on 2.6.8 with ALSA 1.0.4 and it works fine for me. But my mac has the snapper chip, not the burgundy one. I am able to help debugging, though I'm not a real expert on this driver. Martin On Fri, Feb 04, 2005 at 02:21:33PM +0200, Martin-?ric Racine wrote: > According to the following BTS entry, the ALSA maintainer assigned to the > snd-powermac driver doesn't even have any Mac to play with: > > https://bugtrack.alsa-project.org/alsa-bug/view.php?id=306 > > This prooves that all attempts at fixing the driver have been shooting in > the dark. No f* wonder the snd-powermac driver is such a mess! > > Wouldn't it be a good idea to place a bounty to encourage Ubuntu PPC > developers to get around fixing snd-powermac for all Mac PPC chips? > > -- > Martin-?ric Racine > http://www.iki.fi/q-funk/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bounty for fixing ALSA's powermac driver
They should get macs period. I know of one ppc dev that doesn't even have a mac. Apple has to be the largest subset of ppc, certainly commercially. That is reason enough to have their dev work and test things out on macs. I can't even started to get them testing for the DRI bug I have with accel on an old iMac because they (or is it just this one dev) runs a Pegaseus (however you spell it). Mauro On 4-Feb-05, at 6:58 AM, Wouter van Heyst wrote: On Fri, Feb 04, 2005 at 02:21:33PM +0200, Martin-Éric Racine wrote: According to the following BTS entry, the ALSA maintainer assigned to the snd-powermac driver doesn't even have any Mac to play with: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=306 This prooves that all attempts at fixing the driver have been shooting in the dark. No f* wonder the snd-powermac driver is such a mess! Wouldn't it be a good idea to place a bounty to encourage Ubuntu PPC developers to get around fixing snd-powermac for all Mac PPC chips? Oh yes, I would support that. Wouter van Heyst
Re: bounty for fixing ALSA's powermac driver
On 04 Feb 2005 at 16h02, Martin Habets wrote: Hi, > Rather than complainting, maybe someone can offer access to their > Mac. Either physical or via ssh. Usually the real guru's don't need > much time to put things right. (having said that, the cleanup Ben > suggested would be a big effort) Ben also told me once that ssh access to progam kernel stuff was rather useless. Especially when working on video or audio drivers :) -- Colin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bounty for fixing ALSA's powermac driver
On Fri, 4 Feb 2005, Jesus Climent wrote: > On Fri, Feb 04, 2005 at 02:21:33PM +0200, Martin-Éric Racine wrote: > > > > Wouldn't it be a good idea to place a bounty to encourage Ubuntu PPC > > developers to get around fixing snd-powermac for all Mac PPC chips? > > Sorry but I failed to parse your message. Are the Ubuntu people > setting a bounty? Or you want us to set a bounty so that Ubuntu people > can fix the problem and get the money? I am suggesting that we set a bounty. Whether Ubuntu people or someone else gets around fixing it is unimportant; what matters is that getting ALSA support properly and definitely handled on PPC is badly needed. Mark Shuttleworth himself has just volunteered 500 USD towards this. -- Martin-Éric Racine http://www.iki.fi/q-funk/
Re: Auctex on iBook fails (same version works on x86)
On Fri, 04 Feb 2005 16:13:47 +0100 David Kastrup <[EMAIL PROTECTED]> wrote: DK> DK> [Copy by mail since I don't know whether posting to the Usenet DK> mirror will propagate back to the list] DK> DK> James Tappin <[EMAIL PROTECTED]> writes: DK> DK> > I've got the auctex package (advanced tex/latex mode for emacs) on DK> > several boxes and it works just fine on the x86 boxes but on my DK> > iBook it fails with the error: DK> > File mode specification error: (error "Lisp nesting exceeds DK> > max-lisp-eval-depth") DK> > DK> DK> Suspect #1: emacspeak-17. Suspect #2: conflicting remains of a DK> previous manual AUCTeX installation. DK> DK> In either case DK> M-x list-load-path-shadows RET DK> DK> should give you a clue about the problem. DK> list-load-path-shadows only showed shadowing of the .el files by the .elc files. #1 never installed #2 possible but a purging auctex and then removing everything that was #left didn't help. I eventually managed to fix it by purging auctex and emacs21*. Then moving everything left in the /usr/share/emacs/site-lisp to a temporary location and reinstalling, moving back any of the site-lisp stuff that was demanded by the emacs installation. Still a bit puzzled but at least operational. Thanks for the pointers. James -- ++---+-+ | James Tappin | School of Physics & Astronomy | O__| | [EMAIL PROTECTED] | University of Birmingham | -- \/` | | Ph: 0121-414-6462. Fax: 0121-414-3722 | | ++-+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: d-i on a second hard drive in a G5
On Fri, Feb 04, 2005 at 09:42:45AM -0500, Pedro Sanchez wrote: > On Fri, 2005-02-04 at 11:10 +0100, Gaudenz Steinlin wrote: > > On Thu, Feb 03, 2005 at 02:39:48PM -0800, Brad Boyer wrote: > > > On Thu, Feb 03, 2005 at 10:13:17AM -0500, Pedro Sanchez wrote: > > > > 4. /target/etc/yaboot.config (as installed by the d-i): > > > > > > > > boot=/dev/sdb2 > > > > device=/[EMAIL PROTECTED]/[EMAIL PROTECTED]: > > > > > > This last line seems odd. My G5 has only one disk and has a very > > > similar line for device. That makes me think that it isn't getting > > > the right OF path for /dev/sdb2. I would have expected the second > > > drive to be on the second sata channel. Without having a second > > > device on sata on my G5, I can't really test, but it seems worth > > > investigating for someone who knows the installer better. > > > > The installer uses ofpath to translate from device nodes to open > > firmware paths. Pedro: Can you run the following commands in Linux: > > > > ofpath /dev/sda > > ofpath /dev/sdb > > > Here's what I get: > > #ofpath /dev/sda > /[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL > PROTECTED]/[EMAIL PROTECTED]: > > #ofpath /dev/sdb > /[EMAIL PROTECTED]/[EMAIL PROTECTED]: This look strange to me. Is /[EMAIL PROTECTED]/[EMAIL PROTECTED]: a valid OF path on your system? Comparing it to the first path it seems to miss some components. > > So indeed it seems that ofpath has decided that both sata drives are > "[EMAIL PROTECTED]" :| > > I manually edited the yaboot config file to have > > device=/[EMAIL PROTECTED]/[EMAIL PROTECTED]: > > and then I run the command > chroot /target > ybin --config /etc/yaboot.conf -b /dev/sdb2 These options to ybin shouldn't be neccessary, but I don't think that this will solve your problem. Does the path /[EMAIL PROTECTED]/[EMAIL PROTECTED]: exist on your system or is this just a guess? Gaudenz signature.asc Description: Digital signature
Re: bounty for fixing ALSA's powermac driver
On Fri, Feb 04, 2005 at 03:22:40PM +0100, Jesus Climent wrote: > Hi! > > On Fri, Feb 04, 2005 at 02:21:33PM +0200, Martin-Éric Racine wrote: > > > > Wouldn't it be a good idea to place a bounty to encourage Ubuntu PPC > > developers to get around fixing snd-powermac for all Mac PPC chips? All Mac sound chips? Because sound here, on a Titanium IV, with 2.6.8, stock debian powerpc kernel, works like a charm: I didn't even do a complicated ALSA setup: Just added non-root to the cdrom, audio groups, and that was it ... Even on my old 2.4.25 kernel, same machine, ALSA was doing a fairly nice job. The fact I had problems at the beginning when starting using ALSA prolly was due to the person in front of the machine here ... :) BTW: I'm writing this mail while listening to a CD, via Xine, on the Powerbook ... # lsmod | grep snd snd_powermac 44304 2 snd_pcm_oss68136 0 snd_mixer_oss 23264 1 snd_pcm_oss snd_pcm 119800 3 snd_powermac,snd_pcm_oss snd_page_alloc 13480 1 snd_pcm snd_timer 29348 1 snd_pcm snd67800 8 snd_powermac,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 11812 1 snd [ ... ] > On the other hand, I am sorry I have not put any money to BenH's > pool, Ditto ... > but I am in the process of buying a house and I am rather > broke. No house buying here, but broke anyway .. :) > Anyway, I would put a bounty, I would give it to BenH and > then I would think about a second bounty for the sound problems. > > (In case is not obvious, I am trying to say that Ben deserves, among others > (M.Daenzer, Guido come to mind right now), a bounty for all the work he has > already done for, say, iBookG4 sleep) [ ... ] I'm rather sure I'd give my Titanium to eBay without the possibility to run Linux on it ... Sorry, Steve Jobs ... :) So thanks for all the Linux software, to all those making it available for this machine here ... Best Regards Wolfgang -- Wolfgang Pfeiffer http://profiles.yahoo.com/wolfgangpfeiffer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bounty for fixing ALSA's powermac driver
On Fri, 4 Feb 2005, Wolfgang Pfeiffer wrote: > On Fri, Feb 04, 2005 at 03:22:40PM +0100, Jesus Climent wrote: > > On Fri, Feb 04, 2005 at 02:21:33PM +0200, Martin-Éric Racine wrote: > > > > > > Wouldn't it be a good idea to place a bounty to encourage Ubuntu PPC > > > developers to get around fixing snd-powermac for all Mac PPC chips? > > All Mac sound chips? Because sound here, on a Titanium IV, with 2.6.8, > stock debian powerpc kernel, works like a charm: I didn't even do a > complicated ALSA setup: Just added non-root to the cdrom, audio groups, > and that was it ... There is about a dozen of different sound chips used on PowerMacs. ALSA works as it should on some of the Mac hardware. On other hardware, the console beep or the mixer is broken, or the mixer controls are wrong for your particular hardware, etc. -- Martin-Éric Racine http://www.iki.fi/q-funk/
Re: d-i on a second hard drive in a G5
On Fri, 2005-02-04 at 20:00 +0100, Gaudenz Steinlin wrote: > On Fri, Feb 04, 2005 at 09:42:45AM -0500, Pedro Sanchez wrote: > > On Fri, 2005-02-04 at 11:10 +0100, Gaudenz Steinlin wrote: > > > On Thu, Feb 03, 2005 at 02:39:48PM -0800, Brad Boyer wrote: > > > > On Thu, Feb 03, 2005 at 10:13:17AM -0500, Pedro Sanchez wrote: > > > > > 4. /target/etc/yaboot.config (as installed by the d-i): > > > > > > > > > > boot=/dev/sdb2 > > > > > device=/[EMAIL PROTECTED]/[EMAIL PROTECTED]: > > > > > > > > This last line seems odd. My G5 has only one disk and has a very > > > > similar line for device. That makes me think that it isn't getting > > > > the right OF path for /dev/sdb2. I would have expected the second > > > > drive to be on the second sata channel. Without having a second > > > > device on sata on my G5, I can't really test, but it seems worth > > > > investigating for someone who knows the installer better. > > > > > > The installer uses ofpath to translate from device nodes to open > > > firmware paths. Pedro: Can you run the following commands in Linux: > > > > > > ofpath /dev/sda > > > ofpath /dev/sdb > > > > > Here's what I get: > > > > #ofpath /dev/sda > > /[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL > > PROTECTED]/[EMAIL PROTECTED]: > > > > #ofpath /dev/sdb > > /[EMAIL PROTECTED]/[EMAIL PROTECTED]: > > This look strange to me. Is /[EMAIL PROTECTED]/[EMAIL PROTECTED]: a valid OF > path on your > system? Comparing it to the first path it seems to miss some components. > To run these commands I boot from the CD and get all the partitions mounted. Then I exit to a shell from the main installer menu. Therefore, could it be that because all these partitions on the second drive are mounted at that point, the ofpath command simply returns an abbreviated version of the full path? > > > > So indeed it seems that ofpath has decided that both sata drives are > > "[EMAIL PROTECTED]" :| > > > > I manually edited the yaboot config file to have > > > > device=/[EMAIL PROTECTED]/[EMAIL PROTECTED]: > > > > and then I run the command > > chroot /target > > ybin --config /etc/yaboot.conf -b /dev/sdb2 > These options to ybin shouldn't be neccessary, but I don't think that > this will solve your problem. Does the path /[EMAIL PROTECTED]/[EMAIL > PROTECTED]: exist on > your system or is this just a guess? > I went to the openfirmware boot and listed the devices (dev /, ls). This is the hierarchy that I see (just the sata-relevant lines): /[EMAIL PROTECTED],f200 /[EMAIL PROTECTED] /[EMAIL PROTECTED] /[EMAIL PROTECTED] /[EMAIL PROTECTED] /[EMAIL PROTECTED] /[EMAIL PROTECTED] I put the full path in the device=xxx section of yaboot config, run ybin again, rebooted, and nothing new happens. Still in the same loop between the graphical and text boot menus. Any other ideas? -- Pedro > Gaudenz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Booting High Speed
Hi All Here: $ cat /proc/cpuinfo processor : 0 cpu : 7455, altivec supported clock : 867MHz revision: 3.2 (pvr 8001 0302) bogomips: 865.18 machine : PowerBook3,5 motherboard : PowerBook3,5 MacRISC2 MacRISC Power Macintosh detected as : 80 (PowerBook Titanium IV) pmac flags : 000b L2 cache: 256K unified memory : 768MB pmac-generation : NewWorld seems my machine boots with only 667 MHZ: # dmesg | grep Low Low: 667 Mhz, High: 867 Mhz, Boot: 667 Mhz Some values from the config from the kernel where this is happening on: $ grep -i freq /boot/config-2.6.8-powerpc CONFIG_CPU_FREQ=y # CONFIG_CPU_FREQ_PROC_INTF is not set CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=m # CONFIG_CPU_FREQ_24_API is not set CONFIG_CPU_FREQ_PMAC=y CONFIG_CPU_FREQ_TABLE=y # Wireless 802.11 Frequency Hopping cards support Actually I thought with CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y full speed would be the default when booting: What did I miss? Where's the speed switch? Anyone who knows how to turn on full speed/867 MHz while booting this machine? Thanks in anticipation Best Regards Wolfgang -- Wolfgang Pfeiffer http://profiles.yahoo.com/wolfgangpfeiffer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: d-i on a second hard drive in a G5
On Fri, Feb 04, 2005 at 03:28:26PM -0500, Pedro Sanchez wrote: > On Fri, 2005-02-04 at 20:00 +0100, Gaudenz Steinlin wrote: > > On Fri, Feb 04, 2005 at 09:42:45AM -0500, Pedro Sanchez wrote: > > > On Fri, 2005-02-04 at 11:10 +0100, Gaudenz Steinlin wrote: > > > > On Thu, Feb 03, 2005 at 02:39:48PM -0800, Brad Boyer wrote: > > > > > On Thu, Feb 03, 2005 at 10:13:17AM -0500, Pedro Sanchez wrote: > > > > > > 4. /target/etc/yaboot.config (as installed by the d-i): > > > > > > > > > > > > boot=/dev/sdb2 > > > > > > device=/[EMAIL PROTECTED]/[EMAIL PROTECTED]: > > > > > > > > > > This last line seems odd. My G5 has only one disk and has a very > > > > > similar line for device. That makes me think that it isn't getting > > > > > the right OF path for /dev/sdb2. I would have expected the second > > > > > drive to be on the second sata channel. Without having a second > > > > > device on sata on my G5, I can't really test, but it seems worth > > > > > investigating for someone who knows the installer better. > > > > > > > > The installer uses ofpath to translate from device nodes to open > > > > firmware paths. Pedro: Can you run the following commands in Linux: > > > > > > > > ofpath /dev/sda > > > > ofpath /dev/sdb > > > > > > > Here's what I get: > > > > > > #ofpath /dev/sda > > > /[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL > > > PROTECTED]/[EMAIL PROTECTED]: > > > > > > #ofpath /dev/sdb > > > /[EMAIL PROTECTED]/[EMAIL PROTECTED]: > > > > This look strange to me. Is /[EMAIL PROTECTED]/[EMAIL PROTECTED]: a valid > > OF path on your > > system? Comparing it to the first path it seems to miss some components. > > > To run these commands I boot from the CD and get all the partitions > mounted. Then I exit to a shell from the main installer menu. Therefore, > could it be that because all these partitions on the second drive are > mounted at that point, the ofpath command simply returns an abbreviated > version of the full path? It shouldn't. I'm quite sure this is a bug in ofpath. > I went to the openfirmware boot and listed the devices (dev /, ls). This > is the hierarchy that I see (just the sata-relevant lines): > > /[EMAIL PROTECTED],f200 > /[EMAIL PROTECTED] > /[EMAIL PROTECTED] > /[EMAIL PROTECTED] > /[EMAIL PROTECTED] > /[EMAIL PROTECTED] > /[EMAIL PROTECTED] > > I put the full path in the device=xxx section of yaboot config, run ybin > again, rebooted, and nothing new happens. Still in the same loop between > the graphical and text boot menus. try setting ofboot=/[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:2 in your yaboot.conf. This tells the first stage ofboot.b where to look for the yaboot binary. > > Any other ideas? You can try booting the second stage yaboot from OF like this: boot /[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:2,\yaboot Gaudenz signature.asc Description: Digital signature
Re: d-i fails on new PowerMac G5
> Hey, you're the expert :-) I'll take your word over mine any day (I've > used powerpc linux exactly 6 weeks). > > I was under the impression that if the boot strap partition went after > the Mac OS X partition then Mac OS X "de-blessed" all but itself. Am I > wrong there? Nope, the only difference is that if you end up resetting your PRAM, the default that will be loaded is the first one of MacOS X and/or linux bootstrap. Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bounty for fixing ALSA's powermac driver
Wouldn't it be a good idea to place a bounty to encourage Ubuntu PPC developers to get around fixing snd-powermac for all Mac PPC chips? Sorry but I failed to parse your message. Are the Ubuntu people setting a bounty? Or you want us to set a bounty so that Ubuntu people can fix the problem and get the money? In the second case, what the fsck do the Ubuntu people have to do with anything? Can we target that bounty to whoever fixes the problem, and not just them? Who cares who fixes it, jut get the patches into alsa and everyone is happy. We benefit from patches to the kernel from fedora, suse whatever. heck, alsa pretty much has suse to thank for what it is today. On the other hand, I am sorry I have not put any money to BenH's pool, but I am in the process of buying a house and I am rather broke. Anyway, I would put a bounty, I would give it to BenH and then I would think about a second bounty for the sound problems. On that note, ben has published his paypal account. Ill send an email to everyone who pledged for the minimac to get them to send their money. Id be happy to receive direct deposits from australians and then send it on through my paypal account (if people trust me). As for the g5 project, we have a handfull or pledges but not even close to enough to get an imac g5. Dean -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bounty for fixing ALSA's powermac driver
I remember I always got a pop thru my speakers every once in a while. The volume settings where seemed to be somewhat "unlevel" too as using kde's mixer always jumped my volume to a somewhat loud volume as the volume increased. mauro On Fri, 2005-04-02 at 22:25 +0200, Martin-Éric Racine wrote: > On Fri, 4 Feb 2005, Wolfgang Pfeiffer wrote: > > > On Fri, Feb 04, 2005 at 03:22:40PM +0100, Jesus Climent wrote: > > > On Fri, Feb 04, 2005 at 02:21:33PM +0200, Martin-Éric Racine wrote: > > > > > > > > Wouldn't it be a good idea to place a bounty to encourage Ubuntu PPC > > > > developers to get around fixing snd-powermac for all Mac PPC chips? > > > > All Mac sound chips? Because sound here, on a Titanium IV, with 2.6.8, > > stock debian powerpc kernel, works like a charm: I didn't even do a > > complicated ALSA setup: Just added non-root to the cdrom, audio groups, > > and that was it ... > > There is about a dozen of different sound chips used on PowerMacs. > > ALSA works as it should on some of the Mac hardware. On other hardware, > the console beep or the mixer is broken, or the mixer controls are wrong > for your particular hardware, etc. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bounty for fixing ALSA's powermac driver
There is no such thing as suse ppc and there hasn't been for a few versions. Things have to get tested after porting because things are not always a simple matter of porting as the start of this thread already suggests. On Sat, 2005-05-02 at 13:08 +1100, Dean Hamstead wrote: > >>Wouldn't it be a good idea to place a bounty to encourage Ubuntu PPC > >>developers to get around fixing snd-powermac for all Mac PPC chips? > > > > > > Sorry but I failed to parse your message. > > > > Are the Ubuntu people setting a bounty? Or you want us to set a bounty so > > that > > Ubuntu people can fix the problem and get the money? > > > > In the second case, what the fsck do the Ubuntu people have to do with > > anything? Can we target that bounty to whoever fixes the problem, and not > > just > > them? > > Who cares who fixes it, jut get the patches into alsa and everyone is > happy. We benefit from patches to the kernel from fedora, suse whatever. > heck, alsa pretty much has suse to thank for what it is today. > > > On the other hand, I am sorry I have not put any money to BenH's pool, but I > > am in the process of buying a house and I am rather broke. Anyway, I would > > put > > a bounty, I would give it to BenH and then I would think about a second > > bounty > > for the sound problems. > > On that note, ben has published his paypal account. > > Ill send an email to everyone who pledged for the minimac to get them > to send their money. Id be happy to receive direct deposits from > australians and then send it on through my paypal account (if people > trust me). > > As for the g5 project, we have a handfull or pledges but not even > close to enough to get an imac g5. > > Dean > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bounty for fixing ALSA's powermac driver
im talking about suse supporting alsa Dean Mauro wrote: There is no such thing as suse ppc and there hasn't been for a few versions. Things have to get tested after porting because things are not always a simple matter of porting as the start of this thread already suggests. On Sat, 2005-05-02 at 13:08 +1100, Dean Hamstead wrote: Wouldn't it be a good idea to place a bounty to encourage Ubuntu PPC developers to get around fixing snd-powermac for all Mac PPC chips? Sorry but I failed to parse your message. Are the Ubuntu people setting a bounty? Or you want us to set a bounty so that Ubuntu people can fix the problem and get the money? In the second case, what the fsck do the Ubuntu people have to do with anything? Can we target that bounty to whoever fixes the problem, and not just them? Who cares who fixes it, jut get the patches into alsa and everyone is happy. We benefit from patches to the kernel from fedora, suse whatever. heck, alsa pretty much has suse to thank for what it is today. On the other hand, I am sorry I have not put any money to BenH's pool, but I am in the process of buying a house and I am rather broke. Anyway, I would put a bounty, I would give it to BenH and then I would think about a second bounty for the sound problems. On that note, ben has published his paypal account. Ill send an email to everyone who pledged for the minimac to get them to send their money. Id be happy to receive direct deposits from australians and then send it on through my paypal account (if people trust me). As for the g5 project, we have a handfull or pledges but not even close to enough to get an imac g5. Dean -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bounty for fixing ALSA's powermac driver
I guess my point is that it does matter who fixes alsa for it to be usable for ppc. I agree in part it should not matter, to a point. It should definitely be a ppc distro if not debian/ubuntu. On Sat, 2005-05-02 at 14:25 +1100, Dean Hamstead wrote: > im talking about suse supporting alsa > > > > Dean > > Mauro wrote: > > There is no such thing as suse ppc and there hasn't been for a few > > versions. Things have to get tested after porting because things are > > not always a simple matter of porting as the start of this thread > > already suggests. > > > > > > > > > > > > On Sat, 2005-05-02 at 13:08 +1100, Dean Hamstead wrote: > > > Wouldn't it be a good idea to place a bounty to encourage Ubuntu PPC > developers to get around fixing snd-powermac for all Mac PPC chips? > >>> > >>> > >>>Sorry but I failed to parse your message. > >>> > >>>Are the Ubuntu people setting a bounty? Or you want us to set a bounty so > >>>that > >>>Ubuntu people can fix the problem and get the money? > >>> > >>>In the second case, what the fsck do the Ubuntu people have to do with > >>>anything? Can we target that bounty to whoever fixes the problem, and not > >>>just > >>>them? > >> > >>Who cares who fixes it, jut get the patches into alsa and everyone is > >>happy. We benefit from patches to the kernel from fedora, suse whatever. > >>heck, alsa pretty much has suse to thank for what it is today. > >> > >> > >>>On the other hand, I am sorry I have not put any money to BenH's pool, but > >>>I > >>>am in the process of buying a house and I am rather broke. Anyway, I would > >>>put > >>>a bounty, I would give it to BenH and then I would think about a second > >>>bounty > >>>for the sound problems. > >> > >>On that note, ben has published his paypal account. > >> > >>Ill send an email to everyone who pledged for the minimac to get them > >>to send their money. Id be happy to receive direct deposits from > >>australians and then send it on through my paypal account (if people > >>trust me). > >> > >>As for the g5 project, we have a handfull or pledges but not even > >>close to enough to get an imac g5. > >> > >>Dean > >> > >> > > > > > > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bounty for fixing ALSA's powermac driver
i see your point, but if someone wants to fix it on intel and it works on ppc they can go for it what other ppc dists are there? deb, ubuntu, crux? Dean Mauro wrote: I guess my point is that it does matter who fixes alsa for it to be usable for ppc. I agree in part it should not matter, to a point. It should definitely be a ppc distro if not debian/ubuntu. On Sat, 2005-05-02 at 14:25 +1100, Dean Hamstead wrote: im talking about suse supporting alsa Dean Mauro wrote: There is no such thing as suse ppc and there hasn't been for a few versions. Things have to get tested after porting because things are not always a simple matter of porting as the start of this thread already suggests. On Sat, 2005-05-02 at 13:08 +1100, Dean Hamstead wrote: Wouldn't it be a good idea to place a bounty to encourage Ubuntu PPC developers to get around fixing snd-powermac for all Mac PPC chips? Sorry but I failed to parse your message. Are the Ubuntu people setting a bounty? Or you want us to set a bounty so that Ubuntu people can fix the problem and get the money? In the second case, what the fsck do the Ubuntu people have to do with anything? Can we target that bounty to whoever fixes the problem, and not just them? Who cares who fixes it, jut get the patches into alsa and everyone is happy. We benefit from patches to the kernel from fedora, suse whatever. heck, alsa pretty much has suse to thank for what it is today. On the other hand, I am sorry I have not put any money to BenH's pool, but I am in the process of buying a house and I am rather broke. Anyway, I would put a bounty, I would give it to BenH and then I would think about a second bounty for the sound problems. On that note, ben has published his paypal account. Ill send an email to everyone who pledged for the minimac to get them to send their money. Id be happy to receive direct deposits from australians and then send it on through my paypal account (if people trust me). As for the g5 project, we have a handfull or pledges but not even close to enough to get an imac g5. Dean -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bounty for fixing ALSA's powermac driver
sure, but the original post says that this is not working out. As far as ppc *nixes: There is also mandrake-ppc which is now only a volunteer project, yellow dog, fedora-ppc, source mage, gentoo, rock linux and that's just linux. On the bsd front there is open and net, and they are working on a Freebsd-ppc. I've probably missed a few too. On Sat, 2005-05-02 at 16:03 +1100, Dean Hamstead wrote: > i see your point, but if someone wants to fix it on intel > and it works on ppc they can go for it > > what other ppc dists are there? deb, ubuntu, crux? > > Dean > > Mauro wrote: > > I guess my point is that it does matter who fixes alsa for it to be > > usable for ppc. I agree in part it should not matter, to a point. It > > should definitely be a ppc distro if not debian/ubuntu. > > > > On Sat, 2005-05-02 at 14:25 +1100, Dean Hamstead wrote: > > > >>im talking about suse supporting alsa > >> > >> > >> > >>Dean > >> > >>Mauro wrote: > >> > >>>There is no such thing as suse ppc and there hasn't been for a few > >>>versions. Things have to get tested after porting because things are > >>>not always a simple matter of porting as the start of this thread > >>>already suggests. > >>> > >>> > >>> > >>> > >>> > >>>On Sat, 2005-05-02 at 13:08 +1100, Dean Hamstead wrote: > >>> > >>> > >>Wouldn't it be a good idea to place a bounty to encourage Ubuntu PPC > >>developers to get around fixing snd-powermac for all Mac PPC chips? > > > > > >Sorry but I failed to parse your message. > > > >Are the Ubuntu people setting a bounty? Or you want us to set a bounty > >so that > >Ubuntu people can fix the problem and get the money? > > > >In the second case, what the fsck do the Ubuntu people have to do with > >anything? Can we target that bounty to whoever fixes the problem, and > >not just > >them? > > Who cares who fixes it, jut get the patches into alsa and everyone is > happy. We benefit from patches to the kernel from fedora, suse whatever. > heck, alsa pretty much has suse to thank for what it is today. > > > > >On the other hand, I am sorry I have not put any money to BenH's pool, > >but I > >am in the process of buying a house and I am rather broke. Anyway, I > >would put > >a bounty, I would give it to BenH and then I would think about a second > >bounty > >for the sound problems. > > On that note, ben has published his paypal account. > > Ill send an email to everyone who pledged for the minimac to get them > to send their money. Id be happy to receive direct deposits from > australians and then send it on through my paypal account (if people > trust me). > > As for the g5 project, we have a handfull or pledges but not even > close to enough to get an imac g5. > > Dean > > > >>> > >>> > >>> > >> > > > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
