Re: Plymouth on ppc [yaboot, nouveau]
On Die, 2014-01-14 at 14:59 +0100, gw [j] iza [b] superstar wrote: > > I'm not aware of any direct interaction between yaboot and plymouth, so > > I doubt your problem is directly related to yaboot. > > Plymouth has to be configured specifically within the other boot loaders for > it > to work, right? So then I assumed there is something I didn't set up > properly > in yaboot / related-- this is why I mentioned this. For example in Grub 2 > there are settings the plymouth wiki suggests to use, to give the resolution > and tell the system to display a splash. The only thing I'm doing is specifying 'splash' on the kernel command line. If that doesn't work for you, verify in /proc/cmdline that it's really there (and 'nosplash' is not). -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1389750871.23067.56.camel@thor.local
Re: Creating a PowerPC task force?
Hi, Rick Thomas wrote: Hi All! Did anything ever come of this? What can we do to make it happen? now that the holidays are over and we each have a little more free time… Rick I missed that message! I love PPC and I am still very sad it is getting, along with MIPS; a second-level platform with x86 and ARM now having the dominance. I use PPC on two iBooks one with MacOS with Debian, on two iBooks, to check that all thw GNUstep software I am involved with works on that wonderful platform. I veryfy compilation natively and then on Debian+GNUstep. There are, however, lots of difficulties! People code less and less for big-endian platforms and for non-x86 as you write lots of stuff breaks. X currently for me is in bad shape: the driver is crashing with cairo (I hope the patch gets into debian soon) and I have skewed colors. I can survive by exporting X and testing stuff this way, but it is again a proof of this "uphill battle". a lot of work goes beyond debian, it goes in fixes that would benefit also BSD and others, since they are fixes in the userland! I'm not using them currently, but I would have available an older 9600 running NetBSD, which always had SCSI problems, and 9500 which had a G4 card which I never got running full speed and I don't remember which OS it was running. I could dust them off :) GNUstep stuff is a good candiate, since it is quite designed to be corss-platform and most developers, not just me, are receptive about platform compatibility. However Debian is our worst-packaged distribution... so well, not brightnews. Riccardo -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52d56219.8030...@libero.it
Re: Creating a PowerPC task force?
Hi
I spent some time, to learn about automatic build of packages.
Target was to try to recompile with newer GCC.
Not much progress however...
Gasha
On 01/14/2014 12:16 PM, Rick Thomas wrote:
Hi All!
Did anything ever come of this? What can we do to make it happen? now that the
holidays are over and we each have a little more free time…
Rick
On Nov 20, 2013, at 9:07 PM, Rogério Brito wrote:
Dear people,
Motivated by:
* the results of the last call to porters
* the fact that PowerPC (at least) used to be an architecture where Debian
shined
* the lack of external support (which means that we should help ourselves)
* the documentation that is too spread
* the need of architecture-specific tools (pbbuttonsd? mouseemu?
gtkpbbutons? anything that needs to be revived? yahoot? grub2?)
I thought: perhaps are people out there that may be interested in shaping up
the powerpc port of Debian?
In fact, since:
* Ubuntu doesn't offer an official PowerPC release anymore.
* Apple has long given up updating the operating system for PowerPC users.
* Major projects like Chromium/v8/nodejs are not available for PowerPC.
* Firefox for PowerPC is essentially dead as far as Mozilla is concerned,
with only a very bright enthusiast working on building it with JavaScript
acceleration (http://tenfourfox.blogspot.com/),
we are essentially orphans of the architecture. Again, would anybody else be
interested in addressing the current problems that PowerPC seems to have?
It would be super nice to work on having the installs as good as possible
(meaning: "working with as little fiddling as possible after a fresh
install"), integrating intelligence about snd-aoa, snd-powermac etc. in
debian-installer, making the 3D thing work as well as feasible,
automatically suggesting programs (alas, even firmware) that are of use for
a powerpc user?
What about this idea?
Perhaps we can already grab/compile the resources that others have already
kept (say, the Gentoo pages, which are very good, the Ubuntu PowerPC FAQ,
which is another very good resource), an old document that I, a long time
ago, started writing at https://github.com/rbrito/powerpc-tutorial etc.
Of course, having both the document for those people that want to know how
things are done and having the code that just works is the golden goal...
Please, let me know if you are interested in joining efforts. I will only
commit efforts if I see other people contributing, as I have my hands full
already.
Thanks,
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131121050736.ga22...@ime.usp.br
--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52d55966.7070...@pie-dabas.net
powerbook g4 12" revamping, part 1, upgrade disk with SATA SSD
(also posted on my blog on http://www.freevec.org/node/93) Hi all, After a while of inactivity, I decided to give my trusty powerbook G4 a second chance. But I thought it might be a good idea to upgrade some parts of it in the meantime. Now being as it is, I can't upgrade the CPU or RAM (G4 is fixed at 1Ghz and RAM at 1.2GB), but I could upgrade the disk and screen. This time I upgraded the disk plus I replaced the thermal toothpaste with something much more efficient so it wouldn't get as hot. I won't go into the actual details of doing the upgrades, these are covered by the excellent ifixit.com articles: http://www.ifixit.com/Guide/PowerBook+G4+Aluminum+12-Inch+1-1.5+GHz+Hard+Drive+Replacement/548 and http://www.ifixit.com/Guide/PowerBook+G4+Aluminum+12-Inch+1-1.5+GHz+Heat+Sink+Replacement/550 The main difference for the thermal paste is that I used the expensive but nearly top of the line Innovator Cooling Diamond 24 carat, which really dropped the temperature and now the fan doesn't kick in as often as it did -I'd say it did a 8-10C temperature drop on average. This is the one: http://www.amazon.com/IC-Diamond-Carat-Thermal-Compound/dp/B0042IBAOG As for the harddisk replacement, I wanted to go with an SSD, but PATA 2.5" SSDs are rather expensive, so I opted for another solution, use a 1.8" SATA SSD with an adaptor. Specifically, I bought from ebay: * Laptop 1.8" Micro SATA Hard Disk Drive SSD HDD to 44 pins for ~€15 * TOSHIBA THNS064GG2BNAA 1.8" SATA SSD 64GB for ~€55 The speed difference is very apparent, hdparm -t /dev/sda reports a whopping 74MB/s compared to just 23MB/s with the 7200RPM hitachi PATA 2.5" disk! Now, since the 1.8" SSD+adaptor are quite smaller than the 2.5" PATA disk, I had to make sure they keep steady and firm inside the case, so I used some kind of plastic foam that was used in another package, cut it in the dimension of the disk+adapter combo and put it on both ends. It is both firm and insulating. The end result can be seen here: http://www.freevec.org/files/powerbook%2Bssd.JPG Next I'll post about installing new Debian using only a USB storage (no cd/dvd, I removed it completely both because it was broken and for weight reasons, the powerbook is heavy for a 12" laptop by today's standards). I'll also be using grub exclusively, no more yaboot! I hope this was of interest to some people. Cheers Konstantinos Margaritis pgpT2D__ibI93.pgp Description: PGP signature
Re: Plymouth on ppc [yaboot, nouveau]
> I'm not aware of any direct interaction between yaboot and plymouth, so > I doubt your problem is directly related to yaboot. Plymouth has to be configured specifically within the other boot loaders for it to work, right? So then I assumed there is something I didn't set up properly in yaboot / related-- this is why I mentioned this. For example in Grub 2 there are settings the plymouth wiki suggests to use, to give the resolution and tell the system to display a splash. > > What's the problem? The specific problem is that nothing happens, (computer starts normally); there is no splash (not even text/default), and no new error messages related to plymouth, at least that I've found Thanks for the reply, jb --- || pub 2048R/71E92172 2013-11-28 [expires: 2014-08-25] Key fingerprint = 2A4D EE8E 8D41 18AB E461 09D8 1A1F 151F 71E9 2172 || On Tuesday 14 January 2014 08:18:48 Michel Dänzer wrote: > On Mon, 2014-01-13 at 18:53 +0100, gw [j] iza [b] superstar wrote: > > I'm having some problems setting up Plymouth (boot splash package), and > > specifically I'm using the latest Stable, on an old powermac. > > > > In the plymouth documentation wiki and debian wiki there were some tips > > at configuring the nouveau drivers, but I'm wondering if plymouth is > > compatable at all with yaboot? > > I'm not aware of any direct interaction between yaboot and plymouth, so > I doubt your problem is directly related to yaboot. > > What's the problem? > > Anyone have some suggestions or experiences to report? > > plymouth from current sid/experimental basically works for me, but the > colours are wrong (probably due to endianness bugs in plymouth). -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201401141459.45463.gw-supers...@mp3groupie.de
Re: Creating a PowerPC task force?
Hi All!
Did anything ever come of this? What can we do to make it happen? now that the
holidays are over and we each have a little more free time…
Rick
On Nov 20, 2013, at 9:07 PM, Rogério Brito wrote:
> Dear people,
>
> Motivated by:
>
> * the results of the last call to porters
> * the fact that PowerPC (at least) used to be an architecture where Debian
> shined
> * the lack of external support (which means that we should help ourselves)
> * the documentation that is too spread
> * the need of architecture-specific tools (pbbuttonsd? mouseemu?
> gtkpbbutons? anything that needs to be revived? yahoot? grub2?)
>
> I thought: perhaps are people out there that may be interested in shaping up
> the powerpc port of Debian?
>
> In fact, since:
>
> * Ubuntu doesn't offer an official PowerPC release anymore.
> * Apple has long given up updating the operating system for PowerPC users.
> * Major projects like Chromium/v8/nodejs are not available for PowerPC.
> * Firefox for PowerPC is essentially dead as far as Mozilla is concerned,
> with only a very bright enthusiast working on building it with JavaScript
> acceleration (http://tenfourfox.blogspot.com/),
>
> we are essentially orphans of the architecture. Again, would anybody else be
> interested in addressing the current problems that PowerPC seems to have?
>
> It would be super nice to work on having the installs as good as possible
> (meaning: "working with as little fiddling as possible after a fresh
> install"), integrating intelligence about snd-aoa, snd-powermac etc. in
> debian-installer, making the 3D thing work as well as feasible,
> automatically suggesting programs (alas, even firmware) that are of use for
> a powerpc user?
>
> What about this idea?
>
> Perhaps we can already grab/compile the resources that others have already
> kept (say, the Gentoo pages, which are very good, the Ubuntu PowerPC FAQ,
> which is another very good resource), an old document that I, a long time
> ago, started writing at https://github.com/rbrito/powerpc-tutorial etc.
>
> Of course, having both the document for those people that want to know how
> things are done and having the code that just works is the golden goal...
>
> Please, let me know if you are interested in joining efforts. I will only
> commit efforts if I see other people contributing, as I have my hands full
> already.
>
>
> Thanks,
>
> --
> Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
> http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
> DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
>
>
> --
> To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/20131121050736.ga22...@ime.usp.br
>
>
--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/71b46e25-812a-4eff-916f-7b97e18d2...@pobox.com
ofpath command giving different results for same device between wheezy and jessie
It appears that the powerpc64 (Mac G5) kernel change (or something else?) between Wheezy and Jessie is causing the ofpath command to give different results for the same device… e.g. On Wheezy: "of path /dev/sda" results in "/ht@0,f200/pci@5/k2-sata-root@c/@1/@0" but on Jessie: "/ht@0,f200/pci@5/k2-sata-root@c/@/@0" What changed? The /usr/sbin/ofpath files are identical, bit-for-bit, so it almost has to be in the kernel, doesn't it? Interestingly enough, there is no difference if this test is performed with a powerpc (i.e. 32-bit, "Mac G4") kernel. Anybody got a clue? Thanks! Rick PS: This is preventing me from installing Jessie on my PowerMac G5 "macpro" machine. Very frustrating! -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/9f3d9be7-2686-402d-bfa8-790061dee...@pobox.com
Bug#735260: installation-reports: Jessie Netinst for PowerPC-64 creates will not boot after installation -- but works for PowerPC-32
Package: installation-reports Severity: important Tags: d-i -- Package-specific info: Boot method: CD Image version: Debian GNU/Linux testing "Jessie" - Official Snapshot powerpc NETINST Binary-1 20140108-22:14 Date: Jan 13, 2014 Machine: PowerPC MacPro G5 Partitions: sudo mac-fdisk -l /dev/sda /dev/sda #type name length base ( size ) system /dev/sda1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/sda2 Apple_Bootstrap untitled 1954 @ 64 (977.0k) NewWorld bootblock /dev/sda3 Apple_UNIX_SVR2 untitled 13671876 @ 2018 ( 6.5G) Linux native /dev/sda4 Apple_UNIX_SVR2 swap 11748047 @ 13673894 ( 5.6G) Linux swap /dev/sda5 Apple_UNIX_SVR2 untitled 1928103178 @ 25421941 (919.4G) Linux native /dev/sda6 Apple_Free Extra 49 @ 1953525119 ( 24.5k) Free space Block size=512, Number of Blocks=1953525168 DeviceType=0x0, DeviceId=0x0 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [o] Detect network card:[o] Configure network: [o] Detect CD: [o] Load installer modules: [o] Clock/timezone setup: [o] User/password setup:[o] Detect hard drives: [o] Partition hard drives: [o] Install base system:[o] Install tasks: [o] Install boot loader:[o] Overall install:[e] Comments/Problems: All went well until it came time to reboot after the install. The machine rebooted and gave the question about whether to boot "linux" or "CD". I answered "l" for "Linux". Then it said "loading secondary bootloader" and nothing after that except the blinking folder icon with a questionmark. I believe the CD or Linux quetion and the "loading second stage" message come from the open-firmware program "ofboot.b" which is customized by ybin to account for the OF device location of the second stage bootloader, yaboot. It seems likely that the cusomiation is failing, somehow. It never gets into yaboot. I tried the same netinst CD on a G4, PowerPC-32 Mac and it worked perfectly. This bug report is being submitted from the G5 machine with Wheezy, so you can get all the hardware stuff for it. I'm also attaching the two yaboot.conf files for comparison. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="7 (wheezy) - installer build 20130613+deb7u1" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux macpro 3.2.0-4-powerpc64 #1 SMP Debian 3.2.51-1 ppc64 GNU/Linux lspci -knn: :f0:0b.0 Host bridge [0600]: Apple Inc. U3H AGP Bridge [106b:0059] lspci -knn: Kernel driver in use: agpgart-uninorth lspci -knn: :f0:10.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV350 AP [Radeon 9600] [1002:4150] lspci -knn: Subsystem: Advanced Micro Devices [AMD] nee ATI RV350 AP [Radeon 9600] [1002:4150] lspci -knn: Kernel driver in use: radeonfb lspci -knn: 0001:00:00.0 Host bridge [0600]: Apple Inc. U3 HT Bridge [106b:0057] lspci -knn: 0001:00:01.0 PCI bridge [0604]: Apple Inc. K2 HT-PCI Bridge [106b:0045] lspci -knn: 0001:00:02.0 PCI bridge [0604]: Apple Inc. K2 HT-PCI Bridge [106b:0046] lspci -knn: 0001:00:03.0 PCI bridge [0604]: Apple Inc. K2 HT-PCI Bridge [106b:0047] lspci -knn: 0001:00:04.0 PCI bridge [0604]: Apple Inc. K2 HT-PCI Bridge [106b:0048] lspci -knn: 0001:00:05.0 PCI bridge [0604]: Apple Inc. K2 HT-PCI Bridge [106b:0049] lspci -knn: 0001:01:07.0 Unassigned class [ff00]: Apple Inc. K2 KeyLargo Mac/IO [106b:0041] (rev 60) lspci -knn: Kernel driver in use: macio lspci -knn: 0001:01:08.0 USB controller [0c03]: Apple Inc. K2 KeyLargo USB [106b:0040] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 0001:01:09.0 USB controller [0c03]: Apple Inc. K2 KeyLargo USB [106b:0040] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 0001:02:0d.0 Unassigned class [ff00]: Apple Inc. K2 ATA/100 [106b:0043] lspci -knn: Kernel driver in use: pata-pci-macio lspci -knn: 0001:02:0e.0 FireWire (IEEE 1394) [0c00]: Apple Inc. K2 FireWire [106b:0042] lspci -knn: Subsystem: Apple Inc. Device [106b:5811] lspci -knn: Kernel driver in use: firewire_ohci lspci -knn: 0001:03:0f.0 Ethernet controller [0200]: Apple Inc. K2 GMAC (Sun GEM) [106b:004c] lspci -knn: Kernel driver in use:
