Re: Debian freezing on PowerMac G4

2022-02-05 Thread Herminio Hernandez Jr.
I will check. I believe 9400. I am sure it was using either the r300 or r400 
driver. 

Sent from my iPhone

> On Feb 5, 2022, at 7:44 PM, Mike  wrote:
> 
> You are going to have to be a bit more specific, what gpu? You are
> probably supposed to be using xserver-xorg-video-radeon or
> xserver-xorg-video-ati unless you happen to have a very new GPU in
> there.
> https://www.x.org/wiki/radeon/
> https://github.com/freedesktop/xorg-xf86-video-ati
> 
> 
> Michael
> 
>> On Sat, 5 Feb 2022 at 23:50, Herminio Hernandez Jr.
>>  wrote:
>> 
>> Hey,
>> 
>> Took out my PowerMac G4 and installed Debian again. The install went smooth 
>> with the exception of the grub install. Got through that and it booted 
>> perfectly. I installed the nonfree firmware and the amd graphics package. 
>> When I rebooted the system froze. In the past I would put the kernel setting 
>> Radeon.agpmode=-1 and that would resolve it. I dropped to grub edit mode and 
>> added that like and it still froze. There something else I need to do?
>> 
>> Herminio
>> 
>> Sent from my iPhone



Debian freezing on PowerMac G4

2022-02-05 Thread Herminio Hernandez Jr.
Hey,

Took out my PowerMac G4 and installed Debian again. The install went smooth 
with the exception of the grub install. Got through that and it booted 
perfectly. I installed the nonfree firmware and the amd graphics package. When 
I rebooted the system froze. In the past I would put the kernel setting 
Radeon.agpmode=-1 and that would resolve it. I dropped to grub edit mode and 
added that like and it still froze. There something else I need to do?

Herminio

Sent from my iPhone


Re: Performing installer tests on PowerMac with USB sticks

2019-04-30 Thread Herminio Hernandez Jr.
Pretty straight forward 

1. Burn the image to usb
2. Plug it in
3 boot into the boot loader by holding down the opt key
4. You should see the usb as a boot device


Sent from my iPhone

> On Apr 30, 2019, at 3:54 AM, John Paul Adrian Glaubitz 
>  wrote:
> 
> Hello!
> 
> I have dug out one of my iBook G4s now so I can perform installer tests
> on the PowerMac target. While the machine has a built-in optical drive,
> I would avoid having to burn CDs for every installation test run (even
> when using CD-RWs), so I was wondering how well booting from USB sticks
> works on these machines.
> 
> Does anyone have experience creating bootable USB media for PowerMacs
> to install Debian?
> 
> Adrian
> 
> -- 
> .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
> 



Re: Please update your sources.list for powerpc

2018-07-05 Thread Herminio Hernandez, Jr.
Awesome, thanks!

On Thu, Jul 5, 2018 at 10:11 AM John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:

> On 07/05/2018 07:09 PM, Herminio Hernandez, Jr. wrote:
> > ok I am thinking more about the non-free firmware for radeon and nvidia
> GPUs.
> Yes, that's possible since the packages are all arch:all (i.e.,
> architecture-
> independent).
>
> Just add the following line to your /etc/apt/sources.list:
>
> deb [arch=all] http://ftp.debian.org/debian/ unstable contrib non-free
>
> After an "apt update", you should be able to install the firmware
> packages.
>
> Adrian
>
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>


Re: Please update your sources.list for powerpc

2018-07-05 Thread Herminio Hernandez, Jr.
ok I am thinking more about the non-free firmware for radeon and nvidia
GPUs.

Thanks!

On Thu, Jul 5, 2018 at 9:55 AM John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:

> Hi Herminino!
>
> On 07/05/2018 06:51 PM, Herminio Hernandez, Jr. wrote:
> > Will powerpc have access to the non-free repos?
>
> Unfortunately, Debian Ports currently does not build any packages
> from the non-free repository. This means, if you need a package
> from non-free and it's not an arch-all package (_all.deb suffix),
> you will have to build that package yourself.
>
> We might build contrib and non-free packages for Debian Ports
> in the future, but I am not sure whether that's possible from
> the legal point of view.
>
> Adrian
>
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>


Re: Please update your sources.list for powerpc

2018-07-05 Thread Herminio Hernandez, Jr.
Will powerpc have access to the non-free repos?

On Thu, Jul 5, 2018 at 8:30 AM John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:

> Hello!
>
> Since powerpc is now part of Debian Ports, everyone who is running
> Debian on powerpc needs to update their /etc/apt/sources.list to
> be able to continue tracking unstable.
>
> The new sources.list should look like:
>
> # binary default
> deb http://ftp.ports.debian.org/debian-ports/ unstable main
> deb http://ftp.ports.debian.org/debian-ports/ unreleased main
>
> # source
> deb-src http://ftp.debian.org/debian/ unstable main
>
> If you want to include packages which were just built on the buildds,
> use:
>
> # binary default
> deb http://ftp.ports.debian.org/debian-ports/ unstable main
> deb http://incoming.ports.debian.org/buildd/ unstable main
> deb http://ftp.ports.debian.org/debian-ports/ unreleased main
>
> # source
> deb-src http://ftp.debian.org/debian/ unstable main
> deb-src http://incoming.debian.org/debian-buildd/ buildd-unstable main
>
> And if you use experimental, use without incoming:
>
> # binary default
> deb http://ftp.ports.debian.org/debian-ports/ unstable main
> deb http://ftp.ports.debian.org/debian-ports/ unreleased main
> # source
> deb-src http://ftp.debian.org/debian/ unstable main
> deb-src http://ftp.debian.org/debian/ experimental main
>
>
> And experimental with incoming:
>
> # binary default
> deb http://ftp.ports.debian.org/debian-ports/ unstable main
> deb http://incoming.ports.debian.org/buildd/ unstable main
> deb http://ftp.ports.debian.org/debian-ports/ unreleased main
> deb http://ftp.ports.debian.org/debian-ports/ experimental main
> # source
> deb-src http://ftp.debian.org/debian/ unstable main
> deb-src http://incoming.debian.org/debian-buildd/ buildd-unstable main
> deb-src http://ftp.debian.org/debian/ experimental main
> deb-src http://incoming.debian.org/debian-buildd/ buildd-experimental main
>
> You may have to add these lines to your /etc/apt/preferences to
> avoid packages from experimental getting installed automatically:
>
> root@sompek:~# cat /etc/apt/preferences
> Package: *
> Pin: release a=experimental
> Pin-Priority: 1
> root@sompek:~#
>
> Let me know if you have any issues. I will update the debian-installer
> images for powerpc (and all other architectures) in the following
> days.
>
> Adrian
>
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>
>


Re: Unable to boot debian ports debian-9.0-powerpc-NETINST-1.iso image in QEMU

2018-02-11 Thread Herminio Hernandez Jr.
Try installing with one XFS partition. 

Sent from my iPhone

> On Feb 11, 2018, at 12:06 PM, John Ogness  wrote:
> 
> On 2018-02-11, Frank Scheiner  wrote:
 Yeah, maybe it's just the yaboot versions (1.3.16 for Jessie,
 1.3.17 for Sid), that makes the difference.
>>> 
>>> It's annoying that something has regressed here though: is there an
>>> official git repo for yaboot to check out the differences between
>>> 1.3.16 and 1.3.17?
>>> 
>>> The fact that it still works on real hardware suggests that
>>> something has changed here:
> 
> I have real hardware (iBook G4) where the Debian 1.3.17 does not work.
> 
>>> is it possible to generate a test ISO using 1.3.16 yaboot to see if
>>> that starts working under QEMU again?  That would narrow things down
>>> immensely.
>> 
>> With QEMU would it be possible to follow the approach of John Ogness
>> ([1])? He used yaboot v1.3.16 from a USB stick and then loaded the
>> config file from the Debian Sid netinst disc.
> 
> How about Debian applies the patch [2] I submitted, which reverted the
> change that caused the problem? Tony's response [3] to my patch was that
> "we're probably safe to apply this".
> 
> John
> 
>> [1]: https://lists.debian.org/debian-powerpc/2017/10/msg00099.html
> 
> [2] https://lists.debian.org/debian-powerpc/2017/10/msg00118.html
> [3] https://lists.debian.org/debian-powerpc/2017/10/msg00119.html
> 



contrib and non-free in ports

2018-01-08 Thread Herminio Hernandez, Jr.
I was testing the Debian image from ports.debian.org and noticed that only
the 'main' repo is available and not 'contrib' and 'non-free'. I do not
recall if this was already mentioned but will ISOs in ports ever get those
packages?


Re: debian-installer now available in Ports

2017-04-15 Thread Herminio Hernandez Jr.
The problem is I do not think yaboot is maintained either. 

Sent from my iPhone

> On Apr 15, 2017, at 10:30 AM, Risto Suominen  wrote:
> 
> I still have a few powerpc Macs, both OldWorld and NewWorld.
> 
> The oldest one (6100/66) has no Open Firmware, the next one (7600/132)
> has OF 1.x, then comes Beige G3 with OF 2.x, and the first NewWorld
> machine Blue G3 with OF 3.x.
> 
> - the 6100 can only run MkLinux on top of Mach microkernel.
> 
> - the 7600 can boot Linux with Bootx from Mac OS, or with quik directly from 
> OF.
> 
> - the same applies to Beige.
> 
> - the Blue needs yaboot or grub2.
> 
> So, I'm saying that yaboot or grub2 is not usable on OldWorld
> machines. To automate the installation, the installer should be able
> to install quik on them. But I'm afraid that no one has maintained
> quik. Perhaps yaboot or grub2 could be expanded to handle OldWorld as
> well. And making a CD bootable on OldWorld machines is yet another
> challenge.
> 
> Risto
> 



Fwd: Re: Problems installing Debian on Powerbooks

2017-03-09 Thread Herminio Hernandez, Jr.
-- Forwarded message --
From: Herminio Hernandez, Jr. <herminio.hernande...@gmail.com>
Date: Thu, Mar 9, 2017 at 1:48 PM
Subject: Re: Re: Problems installing Debian on Powerbooks
To: Richard Kuenz <richard.ku...@web.de>


for audio you need to run this 'modprobe snd-aoa-i2sbus' then 'alsamixer'
set the PCM channel to 70. You will want to add the module to /etc/modules.

On Thu, Mar 9, 2017 at 1:44 PM, Richard Kuenz <richard.ku...@web.de> wrote:

> https://www.youtube.com/watch?v=c8q2WWkuvbc
>
> *Gesendet:* Donnerstag, 09. März 2017 um 21:23 Uhr
> *Von:* "Herminio Hernandez, Jr." <herminio.hernande...@gmail.com>
> *An:* "Lennart Sorensen" <lsore...@csclub.uwaterloo.ca>
> *Cc:* "Nicholas Dal Porto" <macmani...@comcast.net>, "John Paul Adrian
> Glaubitz" <glaub...@physik.fu-berlin.de>, "debian-powerpc@lists.debian.org"
> <debian-powerpc@lists.debian.org>
> *Betreff:* Re: Problems installing Debian on Powerbooks
> Also when you install firmware-b43-installer if when you do 'lsmod' and
> see that b43 is loaded, just reload it and wireless should be good.
>
> modprobe -r b43
> modprobe b43
>
> On Thu, Mar 9, 2017 at 1:21 PM, Lennart Sorensen <
> lsore...@csclub.uwaterloo.ca> wrote:
>
>> On Thu, Mar 09, 2017 at 10:50:44AM -0800, Nicholas Dal Porto wrote:
>> > I have the non-free package installed.
>> >
>> > Here's the output of lspci -vvv: http://pastebin.com/raw/aQSVwyUW
>> >
>> > I also have Network Manager installed. Anything I need to do there or
>> with any network config files?
>>
>> I think you need firmware-b43-installer installed.
>>
>> Claims to be firmware download tool for old b43xx card firmware.
>>
>> Also can you check 'lsmod' and see if b43 is loaded?
>>
>> --
>> Len Sorensen
>>
>>
>
>


Re: Problems installing Debian on Powerbooks

2017-03-09 Thread Herminio Hernandez, Jr.
Also when you install firmware-b43-installer if when you do 'lsmod' and see
that b43 is loaded, just reload it and wireless should be good.

modprobe -r b43
modprobe b43

On Thu, Mar 9, 2017 at 1:21 PM, Lennart Sorensen <
lsore...@csclub.uwaterloo.ca> wrote:

> On Thu, Mar 09, 2017 at 10:50:44AM -0800, Nicholas Dal Porto wrote:
> > I have the non-free package installed.
> >
> > Here's the output of lspci -vvv: http://pastebin.com/raw/aQSVwyUW
> >
> > I also have Network Manager installed. Anything I need to do there or
> with any network config files?
>
> I think you need firmware-b43-installer installed.
>
> Claims to be firmware download tool for old b43xx card firmware.
>
> Also can you check 'lsmod' and see if b43 is loaded?
>
> --
> Len Sorensen
>
>


Re: What are you guys running on your PowerBook G4's Debian PPC?

2017-03-09 Thread Herminio Hernandez, Jr.
My PowerBook G4 is dual booting Tiger and Lubuntu
My iBook G4 is dual booting Tiger and Debian Sid
My MacMini G4 is running Debian Jessie
My PowerMac G4 is dual-booting Leopard and Debian Sid
My PowerMac G5 is dual-booting Leopard and Lubuntu
I have also an IBook G3 and G4 cube that I will be planning to run Debian on

On Thu, Mar 9, 2017 at 12:57 AM, Mathieu Malaterre  wrote:

> On Wed, Mar 8, 2017 at 10:53 PM, PhiLLip Pi  wrote:
> > Server? Workstation? Old school text stuff? Just curious. I am trying to
> > see what I can use my slow PowerBook G4 with 512 MB of RAM to do.
>
> I use my MacMiniG4 for:
> - ssh server to outside (ppc32 is uncommon so it gives me impression
> of improved security).
> - git server
> - build+test robot for big endian compilation+testing.
>
> I used it in the past for running minidlna but I had to give up mainly
> because of bug #774149 (using kodi with a dedicated RPi3B+ now)
>
> Obviously this may not fit a laptop goal.
>
> -M
>
>


Re: Problems installing Debian on Powerbooks

2017-03-08 Thread Herminio Hernandez, Jr.
depends on your chip. What does dmesg say?

On Wed, Mar 8, 2017 at 11:28 PM, Nicholas Dal Porto 
wrote:

> It was the RAM! Replaced it and it installed without a hitch. However,
> Wireless isn't working. Anyone know a fix?
>
> > On Mar 8, 2017, at 6:33 AM, Lennart Sorensen <
> lsore...@csclub.uwaterloo.ca> wrote:
> >
> >> On Wed, Mar 08, 2017 at 01:17:11PM +0100, John Paul Adrian Glaubitz
> wrote:
> >>> On Tue, Mar 07, 2017 at 03:31:15PM -0800, Nicholas Dal Porto wrote:
> >>> Here's a photo of the pertinent section:
> http://i.imgur.com/hHZyDfg.jpg
> >>
> >> Various components and scripts load by the installer are crashing. This
> is
> >> most likely due to a broken toolchain during build. It could be related
> >> to PIE being enabled for the toolchain by default [1].
> >
> > Or the machine has bad ram.  But certainly a toolchain problem is
> > possible, although I would have thought others would have hit that
> > already if that was the case.
> >
> >> Please let me know which version of Debian you were trying to install. I
> >> need to know the exact name and source of the ISO image and how the
> image
> >> was burnt. Please always provide this information in the future as
> otherwise
> >> it very difficult to track down the issue.
> >>
> >> However, if these specific error messages are reproducible with *any*
> >> version of Debian (Squeeze, Wheezy, Jessie), it's most likely a hardware
> >> issue and you should perform some memory and CPU testing.
> >
> > Yeah testing with something else is a good idea.
> >
> > --
> > Len Sorensen
> >
>
>


Re: What are the fastest Mozilla's Gecko-based web browsers for PowerBook G4?

2017-03-07 Thread Herminio Hernandez, Jr.
First, flash is dead under PowerPC. It will never work sadly. Besides that
I cannot think of another gecko based browser to use. Besides FF I use
Midori, but that is WebKit based.

On Wed, Mar 8, 2017 at 12:01 AM, PhiLLip Pi  wrote:

> In my couple days old Debian Jessie/stable PowerPC on a very old 2002
> 15" Titanium PowerBook G4 with 512 MB of RAM, it came with Firefox v45.7
> ESR but it is very slow and uses too much memories.
>
> I wonder if there are faster Gecko-based web browsers. If they do exist,
> then they need to still work with my 20 MB places.sqlite file from and
> with my faster computers' (new/lat)est SeaMonkey and Firefox versions
> (Windows, Mac OS, and Linux/Debian). Same for plugins (e.g., Flash) and
> extensions (uBlock Origin).
>
> Any suggestions? Thank you in advance. :)
> --
> Quote of the Week: "The great companies did not know that the line
> between hunger and anger is a thin line. And money that might have gone
> to wages went for gas, for guns, for agents and spies, for blacklists,
> for drilling. On the highways the people moved like ants and searched
> for work, for food. And the anger began to ferment." --John Steinbeck's
> The Grapes of Wrath
> Note: A fixed width font (Courier, Monospace, etc.) is required to see
> this signature correctly.
>   /\___/\Phil./Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
>  / /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
> | |o   o| | E-mail: phi...@earthlink.net/a...@zimage.com
>\ _ /  If crediting, then please kindly use Ant nickname
> ( )  and AQFL URL/link.
>
>


Re: Is it possible to use a 2002 (Titanium) 15" PowerBook G4's wifi with WPA2, PSK, AES, etc.?

2017-03-07 Thread Herminio Hernandez, Jr.
I am not sure Titanium PowerBooks support WPA see *here
*

On Tue, Mar 7, 2017 at 12:55 PM, PhiLLip Pi  wrote:

>
> On Tue, Mar 07, 2017 at 02:43:37PM -0500, Lennart Sorensen wrote:
> > On Tue, Mar 07, 2017 at 10:46:16AM -0800, PhiLLip Pi wrote:
> > > Here is what I know based on my new Debian PPC v8's installation:
> > > dmesg (full log in http://pastebin.ca/3777025 ):
> > > $ dmesg |grep airport
> > > [   11.706958] airport 0.15 (Benjamin Herrenschmidt <
> b...@kernel.crashing.org>)
> > > [   11.707033] airport: Physical address 8003
> > > [   12.913489] airport 0.0003:radio: Hardware identity
> 0005:0001:0001:0002
> > > [   12.921204] airport 0.0003:radio: Station identity
> 001f:0001:0008:0046
> > > [   12.928672] airport 0.0003:radio: Firmware determined as
> Lucent/Agere 8.70
> > > [   13.135033] airport 0.0003:radio: firmware: failed to load
> agere_sta_fw.bin (-2)
> > > [   13.143969] airport 0.0003:radio: firmware: failed to load
> agere_sta_fw.bin (-2)
> > > [   13.151299] airport 0.0003:radio: Hardware identity
> 0005:0001:0001:0002
> > > [   13.158542] airport 0.0003:radio: Station identity
> 001f:0001:0008:0046
> > > [   13.165525] airport 0.0003:radio: Firmware determined as
> Lucent/Agere 8.70
> > > [   13.172456] airport 0.0003:radio: Ad-hoc demo mode supported
> > > [   13.179321] airport 0.0003:radio: IEEE standard IBSS ad-hoc
> mode supported
> > > [   13.186201] airport 0.0003:radio: WEP supported, 104-bit key
> > > As you can see, it only goes up to WEP. No WPA2. I noticed it said
> > > missing agere_sta_fw.bin firmware from
> > > added "http://ftp.de.debian.org/debian jessie main non-free" in my
> > > /etc/apt/sources.list file. So, I rebooted and rechecked. Now, it
> > > doesn't say it and shows WPA supported, but not WPA2 (better security)?
> > > :(
> >
> > The orinoco does not do WPA2 from what I can find.  WPA is the best it
> > can do.
> >
> > Apparently 15" titanium powerbook 2002 is much too vague to determine
> > the machine in question.  That covers about 5 or 6 different models
> > it seems.  Some with orinoco, some with b43, and perhaps even some with
> > something else.
> >
> > Seems the b43xx based models are b/g and WPA2 capable, while the orinoco
> > based ones are b only with WPA at best.
>
> Ah. I guess I shouldn't bother trying its internal wireless unless I
> want to sacrifice wireless security. :(
> --
> Quote of the Week: "The great companies did not know that the line
> between hunger and anger is a thin line. And money that might have gone
> to wages went for gas, for guns, for agents and spies, for blacklists,
> for drilling. On the highways the people moved like ants and searched
> for work, for food. And the anger began to ferment." --John Steinbeck's
> The Grapes of Wrath
> Note: A fixed width font (Courier, Monospace, etc.) is required to see
> this signature correctly.
>   /\___/\Phil./Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
>  / /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
> | |o   o| | E-mail: phi...@earthlink.net/a...@zimage.com
>\ _ /  If crediting, then please kindly use Ant nickname
> ( )  and AQFL URL/link.
>
>


Re: PowerMac G5 and KMS

2017-03-05 Thread Herminio Hernandez, Jr.
Per the radeon man page *here
<https://www.freebsd.org/cgi/man.cgi?query=xorg.conf=5=0=FreeBSD+11.0-RELEASE+and+Ports>.
*However this option has been removed after 10.2. Under Linux the you
set it in yaboot bootloader by using 'radeon.agpmode=-1'. I do not
know if this will work in loader.conf



  *Option* *"BusType"*  *"**string**"*
  Used  to  replace  previous ForcePCIMode option.  Should only be
  used when driver's bus detection is incorrect  or  you  want  to
  force an AGP card to PCI mode. You should NEVER force a PCI card
  to AGP bus.
  PCI-- PCI bus
  AGP-- AGP bus
  PCIE   -- PCI Express bus
  (used only when DRI is enabled)
  The default is *auto* *detect.*



On Sun, Mar 5, 2017 at 3:35 PM, Hiroo Ono (小野寛生) <
hiroo.ono+free...@gmail.com> wrote:

> Thank you. I see the point.
>
> 2017-03-05 17:20 GMT+09:00 Herminio Hernandez Jr.
> <herminio.hernande...@gmail.com>:
> > Try to force the Radeon driver into PCI mode. Under Linux doing this
> stops
> > the blank screen and locks.
>
> Could anyone tell me how to do it? Can it be done from FreeBSD?
> I googled a little but could not find anything useful (maybe search
> words were not
> appropriate), so how to do it on Linux helps me also.
>
> pciconf -lc says:
> vgapci0@pci0:0:16:0: class=0x3 card=0x41501002 chip=0x41501002
> rev=0x00 hdr=0x00
>   cap 02[58] = AGP v3 8x 4x SBA disabled]
>   cap 01[50] = powerspec 2 supports D0 D1 D2 D3 current D0
>


Re: PowerMac G5 and KMS

2017-03-05 Thread Herminio Hernandez Jr.
Try to force the Radeon driver into PCI mode. Under Linux doing this stops the 
blank screen and locks. 

Sent from my iPhone

> On Mar 4, 2017, at 11:50 PM, Joe Nosay  wrote:
> 
> This will bounce for the ppc list.
> As I have stated before: you will need to work with the debian ppc group to 
> create the proper drivers.
> Since there are people who know how to make the Linux system calls, there 
> should be people that are willing to
> work across OS and mailing list lines.
> Just don't be stubborn.
> 
>> On Thu, Mar 2, 2017 at 12:34 PM, Mark Millard  wrote:
>> On 2017-Mar-2, at 9:37 AM, Justin Hibbits  wrote:
>> 
>> > On Thu, Mar 2, 2017 at 5:42 AM, Hiroo Ono (小野寛生)
>> >  wrote:
>> >> I recently installed 12-current powerpc64 r313561 to a PowerMac G5
>> >> (it is dual processor, but I do not know its detail).
>> >>
>> >> When I try to load drm2.ko and radeonkms.ko,
>> >> the screen turns into black and recovers, then the system locks.
>> >> kldload command does not return, no response to keyboard input, etc.
>> >>
>> >> Is it possible to use KMS on FreeBSD/powerpc64?
>> >>
>> >> The log in /var/log/messages is
>> >>
>> >> after "kldload drm2",
>> >>
>> >> kernel: info: [drm] Initialized drm 1.1.0 20060810
>> >>
>> >> and then, after "kldload radeonkms",
>> >>
>> >> kernel: iic0:  on iicbus0
>> >> kernel: iic1:  on iicbus1
>> >> kernel: drmn0:  on vgapci0
>> >> kernel: info: [drm] RADEON_IS_AGP
>> >> kernel: info: [drm] initializing kernel modesetting (RV350 0x1002:0x4150
>> >> 0x1002:0x4150).
>> >> kernel: info: [drm] register mmio base: 0x9000
>> >> kernel: info: [drm] register mmio size: 65536
>> >> kernel: info: [drm] igp_read_bios_from_vram: ===> Try IGP's VRAM...
>> >> kernel: info: [drm] igp_read_bios_from_vram: VRAM base address: 0x9800
>> >> kernel: info: [drm] igp_read_bios_from_vram: Map address:
>> >> 0xc00061412000 (262144 bytes)
>> >> kernel: info: [drm] igp_read_bios_from_vram: Incorrect BIOS signature:
>> >> 0x
>> >> kernel: info: [drm] radeon_read_bios: ===> Try PCI Expansion ROM...
>> >> kernel: info: [drm] radeon_read_bios: Map address: 0xc00061412000
>> >> (131072 bytes)
>> >> kernel: info: [drm] radeon_read_bios: Incorrect BIOS signature: 0x2AFF
>> >> kernel: info: [drm] legacy_read_disabled_bios: ===> Try disabled BIOS
>> >> (legacy)...
>> >> kernel: info: [drm] radeon_read_bios: ===> Try PCI Expansion ROM...
>> >> kernel: info: [drm] radeon_read_bios: Map address: 0xc00061412000
>> >> (131072 bytes)
>> >>
>> >> As the system locks up here, I have to power it off forcibly.
>> >
>> > Congratulations (?) you are quite possibly the first person to report
>> > even attempting to use radeonkms on powerpc64.  Frankly, I'm not
>> > surprised that it doesn't work for you.  Unfortunately, I don't have a
>> > solution, or even a means to track it down.  Looking at the log
>> > snippet, my first guess is there may need to be a provision added to
>> > the driver for non-x86.  Do you know what card this is?
>> >
>> > Adding a couple other lists with people who might have more insight.
>> >
>> > If it can be made to work, I'd definitely want to get a Radeon card for my 
>> > G5(s)
>> >
>> > - Justin
>> 
>> Back on 2014-Nov-21 I wrote the following in one of my messages on the
>> lists on that day:
>> 
>> > FYI: I've been building and trying Jean-Sébastien Pédron's 
>> > kms-drm-update-38 branch when Jean requested (sometimes with patches that 
>> > Jean provided). This was to give Jean some (indirect) access to a 
>> > powerpc64 (PowerMac G5) Radeon context for some radeonkms development. 
>> > (Jean had been hoping to get my card going in that context.) We got to the 
>> > point that a kldload for radeonkms did not complain/refuse but the display 
>> > was then munged up and the driver could not find the Video BIOS. The fact 
>> > that it is a Radeon X1950 for the video hardware may make it odder than 
>> > usual for PowerMac G5 Radeons. But it is the only Radeon that I have 
>> > access to for G5's. (The card works in Mac OS X 10.5.)
>> 
>> (As I remember this was a PowerMac G5 so-called "Quad Core" as the G5
>> context. I do not currently have access to the X1950 card.)
>> 
>> I'm not sure from what I read if things are about the same vs. if things
>> are worse now. I do not remember the details from back then, such as
>> console vs. X11 that I was not explicit about in the quoted material.
>> 
>> I eventually gave up on using X11 "for a time" --and have not tried again
>> so far. I've no clue about the current status for X11 on PowerMacs of
>> any kind --or what I'd need to do to try it for the Radeon X1950 or
>> any NVIDIA cards. (Currently an NVIDIA card is installed.)
>> 
>> I will eventually have access to the X1950 again, but not soon.
>> 
>> ===
>> Mark Millard
>> markmi at dsl-only.net
>> 
>> ___
>> freebsd-...@freebsd.org mailing list
>> 

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-13 Thread Herminio Hernandez, Jr.
This does not surprise me. It is a really sad case. Even the developer of
the TenFourFox port of FF knows that he will have to cease being code
compatible. Right now I am using Midori, but once that moves to webkit2gtk
life will be painful.

Here is backtrace I did.

On Mon, Feb 13, 2017 at 4:26 AM, luigi burdo 
wrote:

> It means all are killing us in all fronts.
>
> [image: ☹]
>
>
> Luigi
>
>
> --
> *Da:* John Paul Adrian Glaubitz 
> *Inviato:* lunedì 13 febbraio 2017 11.49
> *A:* debian-powerpc@lists.debian.org
> *Oggetto:* Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC
> (PPC32): Segmentation fault
>
> Hi!
>
> On 02/06/2017 10:39 PM, Christian Zigotzky wrote:
> > I installed Firefox 51.0.1-1 with 'apt-get install -t experimental
> firefox'
> > on Debian Sid/experimental PowerPC (PPC32) today.
>
> Just as a warning in advance: Mozilla upstream has decided to make the Rust
> programming language mandatory for Firefox 54 onwards [1].
>
> Unfortunately, Mozilla currently has little interest to support Rust
> non-x86
> platforms in a stable manner which is why the Rust compiler rustc is
> currently
> really usable on i386, amd64 and with some luck on arm64 [2].
>
> Thus, it can be expected that Firefox 54 and newer will no longer run on
> any PowerPC platforms, especially 32-bit variants.
>
> It's a sad state but Mozilla upstream has decided to make this cut which
> will also eventually see the removal of XUL support and hence the support
> for most of the popular Addons that exist in Firefox like Vimperator.
>
> Adrian
>
> > [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1284816
> 1284816 – Require Rust to build - bugzilla.mozilla.org
> 
> bugzilla.mozilla.org
> At some point we're going to require Rust to build Firefox. This is a
> blocker to writing any critical components in Rust. Once we've fixed the
> blockers of bug 1283898 ...
>
>
> > [2] http://lists.alioth.debian.org/pipermail/pkg-rust-
> maintainers/Week-of-Mon-20161226/000758.html
>
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>
>
rican-linux@debian-ppc:~$ gdb firefox.real
]GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from firefox.real...Reading symbols from /usr/lib/debug/.build-id/a6/81b7e65ae15687f43f84f7c55dfc4626f13bda.debug...done.
done.
(gdb) run http://mozilla.org
Starting program: /usr/bin/firefox.real http://mozilla.org
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1".
[New Thread 0xb79ff450 (LWP 2332)]
[New Thread 0xb5c3a450 (LWP 2333)]
[Thread 0xb5c3a450 (LWP 2333) exited]
[New Thread 0xb5c3a450 (LWP 2335)]
[New Thread 0xb49ca450 (LWP 2336)]
[New Thread 0xb3fff450 (LWP 2337)]
[New Thread 0xb37ff450 (LWP 2338)]
[New Thread 0xb2fff450 (LWP 2339)]
[New Thread 0xb27ff450 (LWP 2340)]
[New Thread 0xb1fff450 (LWP 2341)]
[New Thread 0xb17ff450 (LWP 2342)]
[New Thread 0xb0bff450 (LWP 2343)]
[New Thread 0xb03ff450 (LWP 2344)]
[New Thread 0xafb09450 (LWP 2345)]
[New Thread 0xaf309450 (LWP 2346)]
[New Thread 0xb7f8a450 (LWP 2348)]
[New Thread 0xae5ff450 (LWP 2349)]
[New Thread 0xad6ff450 (LWP 2350)]
[New Thread 0xac7ff450 (LWP 2351)]
[Thread 0xac7ff450 (LWP 2351) exited]
[New Thread 0xac7ff450 (LWP 2352)]
[New Thread 0xabd0b450 (LWP 2353)]
[New Thread 0xab50b450 (LWP 2354)]
[Thread 0xac7ff450 (LWP 2352) exited]
[New Thread 0xac7ff450 (LWP 2356)]
[New Thread 0xaae85450 (LWP 2357)]
[New Thread 0xa9fff450 (LWP 2358)]
[New Thread 0xa97ff450 (LWP 2359)]
[New Thread 0xa8fff450 (LWP 2360)]
[New Thread 0xa87ff450 (LWP 2361)]
[New Thread 0xa7bff450 (LWP 2362)]
[New Thread 0xa73ff450 (LWP 2363)]
[New Thread 0xa6bff450 (LWP 2364)]
[New Thread 0xa63ff450 (LWP 2365)]
[Thread 0xa63ff450 (LWP 2365) exited]
[Thread 0xa6bff450 (LWP 2364) exited]
[Thread 0xa7bff450 (LWP 2362) exited]
[New Thread 0xa63ff450 (LWP 2366)]
[New Thread 0xa6bff450 (LWP 2368)]
[New Thread 0xa7bff450 (LWP 2369)]
[New Thread 0xa4aff450 (LWP 2370)]
[New Thread 0xa42ff450 (LWP 2371)]
[Thread 0xac7ff450 (LWP 

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-12 Thread Herminio Hernandez Jr.
Running debug now with the symbols. 

Sent from my iPhone

> On Feb 12, 2017, at 8:50 AM, Christian Zigotzky <chzigot...@xenosoft.de> 
> wrote:
> 
> Hi Herminio,
> 
> If you want to backtrace Firefox, then you need the debug version of Firefox. 
> Please add the following repositories to your /etc/apt/sources.list:
> 
> deb http://debug.mirrors.debian.org/debian-debug/ unstable-debug main
> deb http://debug.mirrors.debian.org/debian-debug/ experimental-debug main
> 
> You have to install the Firefox package with dbgsym attached:
> 
> apt-get install -t experimental firefox-dbgsym
> 
> Many thanks for your help.
> 
> Cheers,
> Christian
> 
>> On 12 February 2017 at 10:18 AM, John Paul Adrian Glaubitz wrote:
>>> On 02/12/2017 08:37 AM, Herminio Hernandez, Jr. wrote:
>>> I ran firefox 51 on my iBook G4 running Sid. I was able to get a backtrace. 
>>> I am posting it here.
>> This backtrace is not usable, it doesn't contains any symbols:
>> 
>> Thread 1 "firefox.real" received signal SIGSEGV, Segmentation fault.
>> 0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
>> (gdb) bt
>> #0  0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
>> #1  0x1ae2eed4 in ?? () from /usr/lib/firefox/libxul.so
>> #2  0x20017584 in ?? ()
>> (...)
>> 
>> The "??" indicates you don't have debug symbols installed.
>> 
>> Adrian
>> 
> 



Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-12 Thread Herminio Hernandez Jr.
Will do. Anything to help. 

Sent from my iPhone

> On Feb 12, 2017, at 8:50 AM, Christian Zigotzky <chzigot...@xenosoft.de> 
> wrote:
> 
> Hi Herminio,
> 
> If you want to backtrace Firefox, then you need the debug version of Firefox. 
> Please add the following repositories to your /etc/apt/sources.list:
> 
> deb http://debug.mirrors.debian.org/debian-debug/ unstable-debug main
> deb http://debug.mirrors.debian.org/debian-debug/ experimental-debug main
> 
> You have to install the Firefox package with dbgsym attached:
> 
> apt-get install -t experimental firefox-dbgsym
> 
> Many thanks for your help.
> 
> Cheers,
> Christian
> 
>> On 12 February 2017 at 10:18 AM, John Paul Adrian Glaubitz wrote:
>>> On 02/12/2017 08:37 AM, Herminio Hernandez, Jr. wrote:
>>> I ran firefox 51 on my iBook G4 running Sid. I was able to get a backtrace. 
>>> I am posting it here.
>> This backtrace is not usable, it doesn't contains any symbols:
>> 
>> Thread 1 "firefox.real" received signal SIGSEGV, Segmentation fault.
>> 0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
>> (gdb) bt
>> #0  0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
>> #1  0x1ae2eed4 in ?? () from /usr/lib/firefox/libxul.so
>> #2  0x20017584 in ?? ()
>> (...)
>> 
>> The "??" indicates you don't have debug symbols installed.
>> 
>> Adrian
>> 
> 



Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-12 Thread Herminio Hernandez Jr.
You are right. I will install them and run again. 

Sent from my iPhone

> On Feb 12, 2017, at 2:18 AM, John Paul Adrian Glaubitz 
> <glaub...@physik.fu-berlin.de> wrote:
> 
>> On 02/12/2017 08:37 AM, Herminio Hernandez, Jr. wrote:
>> I ran firefox 51 on my iBook G4 running Sid. I was able to get a backtrace. 
>> I am posting it here.
> 
> This backtrace is not usable, it doesn't contains any symbols:
> 
> Thread 1 "firefox.real" received signal SIGSEGV, Segmentation fault.
> 0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
> (gdb) bt
> #0  0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
> #1  0x1ae2eed4 in ?? () from /usr/lib/firefox/libxul.so
> #2  0x20017584 in ?? ()
> (...)
> 
> The "??" indicates you don't have debug symbols installed.
> 
> Adrian
> 
> -- 
> .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-11 Thread Herminio Hernandez, Jr.
I ran firefox 51 on my iBook G4 running Sid. I was able to get a backtrace.
I am posting it here.

Herminio

On Tue, Feb 7, 2017 at 12:49 AM, Christian Zigotzky 
wrote:

> Could someone also test Firefox 51.0.1-1? My gdb closes after the command
> 'run'.
>
> -- Christian
>
> Sent from my iPhone
>
> > On 7 Feb 2017, at 00:09, Christian Zigotzky 
> wrote:
> >
> > Unfortunately, gdb has closed after the command 'run'. It's not possible
> to get a backtrace.
> >
> >> On 07 February 2017 at 12:04 AM, John Paul Adrian Glaubitz wrote:
> >>> On 02/07/2017 12:02 AM, Christian Zigotzky wrote:
> >>> (gdb) run
> >>>
> >>> Starting program: /usr/lib/firefox/./firefox
> >>> warning: Could not load shared library symbols for linux-vdso32.so.1.
> >>> Do you need "set solib-search-path" or "set sysroot"?
> >>> [Thread debugging using libthread_db enabled]
> >>> Using host libthread_db library "/lib/powerpc-linux-gnu/
> libthread_db.so.1".
> >>> Dwarf Error: wrong version in compilation unit header (is 7, should be
> 2, 3, or 4) [in module
> >>> /usr/lib/debug/.build-id/18/ea31ffd1c49eaf7be933acec89325c
> b9e187bf.debug]
> >>> Dwarf Error: wrong version in compilation unit header (is 0, should be
> 2, 3, or 4) [in module
> >>> /usr/lib/debug/.build-id/26/a1e97b21731a564ed396149593f408
> 4391a20c.debug]
> >>> Dwarf Error: wrong version in compilation unit header (is 0, should be
> 2, 3, or 4) [in module
> >>> /usr/lib/debug/.build-id/7a/f876d1dcfc23d59299dd09539d4dba
> 3a2ec5ce.debug]
> >>> Dwarf Error: bad offset (0x3e83) in compilation unit header
> (offset 0x0 + 6) [in module
> >>> /usr/lib/debug/.build-id/7c/05723a7ada75d51fd4a85a036351a9
> 76ed9a68.debug]
> >>> Segmentation fault
> >> And what's the backtrace?
> >>
> >
>
>


firefox.real-gdb.log
Description: Binary data


Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-06 Thread Herminio Hernandez Jr.
Isn't there a logging feature that will capture it?

Sent from my iPhone

> On Feb 6, 2017, at 4:09 PM, Christian Zigotzky  wrote:
> 
> Unfortunately, gdb has closed after the command 'run'. It's not possible to 
> get a backtrace.
> 
>> On 07 February 2017 at 12:04 AM, John Paul Adrian Glaubitz wrote:
>>> On 02/07/2017 12:02 AM, Christian Zigotzky wrote:
>>> (gdb) run
>>> 
>>> Starting program: /usr/lib/firefox/./firefox
>>> warning: Could not load shared library symbols for linux-vdso32.so.1.
>>> Do you need "set solib-search-path" or "set sysroot"?
>>> [Thread debugging using libthread_db enabled]
>>> Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1".
>>> Dwarf Error: wrong version in compilation unit header (is 7, should be 2, 
>>> 3, or 4) [in module
>>> /usr/lib/debug/.build-id/18/ea31ffd1c49eaf7be933acec89325cb9e187bf.debug]
>>> Dwarf Error: wrong version in compilation unit header (is 0, should be 2, 
>>> 3, or 4) [in module
>>> /usr/lib/debug/.build-id/26/a1e97b21731a564ed396149593f4084391a20c.debug]
>>> Dwarf Error: wrong version in compilation unit header (is 0, should be 2, 
>>> 3, or 4) [in module
>>> /usr/lib/debug/.build-id/7a/f876d1dcfc23d59299dd09539d4dba3a2ec5ce.debug]
>>> Dwarf Error: bad offset (0x3e83) in compilation unit header (offset 0x0 
>>> + 6) [in module
>>> /usr/lib/debug/.build-id/7c/05723a7ada75d51fd4a85a036351a976ed9a68.debug]
>>> Segmentation fault
>> And what's the backtrace?
>> 
> 



Re: Where is powerpc now?

2016-11-15 Thread Herminio Hernandez, Jr.
What type of help would you need?

On Tue, Nov 15, 2016 at 1:32 PM, John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:

> On 11/15/2016 09:27 PM, Herminio Hernandez, Jr. wrote:
> > is there even a sid iso?
>
> There isn't. But it's actually possible to build d-i installation images
> yourself,
> see this guide which goes through the procedure for hppa [1].
>
> Note: This guide has one flaw: At one point it sets DI_DIR to:
>
> DI_DIR="/extra/deller/DEBIAN_INSTALLER/debian-installer/
> installer/build/tmp/netboot"
>
> This should, however, be:
>
> DI_DIR="/extra/deller/DEBIAN_INSTALLER/debian-installer/
> installer/build/tmp/cdrom"
>
> I'm planning to build updated powerpc installation images in the near
> future the same
> way I created them for sparc64 [2]. I wished I had more time for these
> things.
>
> Adrian
>
> > [1] https://parisc.wiki.kernel.org/index.php/How_to_create_
> Debian_unstable_iso_images
> > [2] https://people.debian.org/~glaubitz/debian-cd/2016-05-04/
>
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>


Re: Where is powerpc now?

2016-11-15 Thread Herminio Hernandez, Jr.
is there even a sid iso?

On Tue, Nov 15, 2016 at 9:36 AM, Lennart Sorensen <
lsore...@csclub.uwaterloo.ca> wrote:

> On Tue, Nov 15, 2016 at 01:05:02AM +0100, Matti Palmström wrote:
> > Since the other day I get
> >
> > N: Skipping acquire of configured file 'main/binary-powerpc/Packages' as
> > repository 'http://ftp.us.debian.org/debian stretch InRelease' doesn't
> > support architecture 'powerpc'
> >
> > Is this just a temporary glitch or are we moving to debian-ports?
>
> It still works with sid, but it does look like it disappeared from
> stretch, which if true is rather inconvinient for anyone that might have
> hoped to make an unofficial stretch release.  I certainly never saw any
> mention that this would happen.
>
> --
> Len Sorensen
>
>


Re: Release Architectures for Debian 9 'Stretch'

2016-11-04 Thread Herminio Hernandez Jr.
To say that no one stepped forward is not true. Adrian stepped up and asked to 
be the porter for PowerPC. There was an entire thread on PowerPC qualifying for 
Stretch where he stated his desire to support it. In the end his request was 
turned down. 

Sent from my iPhone

> On Nov 4, 2016, at 2:08 AM, Christoph Biedl <debian.a...@manchmal.in-ulm.de> 
> wrote:
> 
> Lennart Sorensen wrote...
> 
>>> On Mon, Oct 31, 2016 at 09:09:56AM -0700, Herminio Hernandez Jr.  wrote:
>>> Is there even a chance for PowerPC to return as a release architecture for 
>>> Debian 10 or is that just wishful thinking. 
>> 
>> Well as pointed out in the meeting, it does not seem any architecture
>> has ever done so.
> 
> I bet never before an architecture got kicked out that is ranking as
> number 4 according to popcon. The question is, are there enough people
> that are willing to support powerpc in Debian? The way downhill began
> when nobody stepped forward in the role call.
> 
>Christoph
> 



Re: [Debian-ports-devel] Moving powerpc to Debian Ports

2016-11-02 Thread Herminio Hernandez Jr.
I would like to know after Stretch will we be able to submit bugs to BTS or are 
we basically on our own. 

Sent from my iPhone

> On Nov 2, 2016, at 4:43 AM, Gatis Visnevskis  wrote:
> 
> Hi,
> 
> I would like to have knowledge shared, how to still run Debian on powerpc 
> without main archives.
> 
> I am going to run Debian on powerpc, and im sure that many other users will 
> do. There will be many security patches (kernel/openssl) and they must be 
> patched some way.
> Maybe we are not strong enough to keep entire distro up to Debian standarts, 
> but at least base packages?
> 
> Gasha
> 
> 
>> On 2016.11.01. 17:40, John Paul Adrian Glaubitz wrote:
>>> On 11/01/2016 10:30 PM, Lennart Sorensen wrote:
 On Tue, Nov 01, 2016 at 01:42:50PM +0900, John Paul Adrian Glaubitz wrote:
 Since Debian powerpc was recently announced to be removed as a release 
 architecture,
 I would like to formally request to move the port to Debian Ports as there 
 still seems
 to be quite some demand among users [1].
>>> 
>>> It won't be a release arch, but that doesn't imply removal in general from 
>>> debian.
>> 
>> Both ia64 and sparc were dropped for release after Wheezy and soon after 
>> removed from
>> the FTP servers and buildd infrastructure altogether. For some reason, this 
>> hasn't
>> happened to kfreebsd-i386 and kfreebsd-amd64 though, no idea what's the 
>> difference
>> between ia64/sparc and the kfreebsd ports.
>> 
 As with the other architectures in Debian Ports, I suggest providing 
 shared wanna-build
 access among all Debian Ports maintainers (CC'ing everyone involved).
 
 I really want to keep Debian powerpc maintained for the foreseeable future 
 because I
 don't want to disappoint our users who are still using PowerPC hardware.
>>> 
>>> Until someone says they want to remove it from the main debian archives,
>>> I see no reason to ask to move it to ports.  The time to ask for that
>>> is if it is announced it is going to be removed from the main debian
>>> archives, and that certainly has not happened at this time.
>> 
>> I just want to avoid a situation in which powerpc is gone from the main 
>> archives
>> and non-existing in Ports either. If we do the transition now, we can move 
>> powerpc
>> over in a healthy condition and make sure, the port remains usable for its 
>> users
>> in the foreseeable future.
>> 
>> Adrian
>> 
> 



Re: Release Architectures for Debian 9 'Stretch'

2016-10-31 Thread Herminio Hernandez, Jr.
There is some hope then...

On Mon, Oct 31, 2016 at 4:56 PM, Thadeu Lima de Souza Cascardo <
casca...@minaslivre.org> wrote:

> On Mon, Oct 31, 2016 at 04:34:15PM -0700, Herminio Hernandez, Jr. wrote:
> > I have they in the past kept and architecture that was dropped as a
> release
> > arch?
>
> GNU/kFreeBSD was released as a technology preview for squeeze, kept as
> TP in wheezy, then not made part of the jessie. I can't find it in
> testing, but I see it in sid. So, it doesn't have any chance of being
> part of a new release, as far as I understand, but it's still kept in
> the archive.
>
> Cascardo.
>


Re: Release Architectures for Debian 9 'Stretch'

2016-10-31 Thread Herminio Hernandez, Jr.
No there is no lts for ppc only i386, amd64, and arm

https://wiki.debian.org/LTS/


On Mon, Oct 31, 2016 at 4:13 PM, Rick Thomas  wrote:

>
> Will there be an LTS (long-term-support) release for powerpc — best would
> be one based on Jessie?
>
>
> On Oct 31, 2016, at 6:42 AM, Mathieu Malaterre  wrote:
>
> > Anyone has a summary of the powerpc specific discussion ?
> >
> >
> > -- Forwarded message --
> > [...]
> > The only change from Jessie is the removal of powerpc as a release
> > architecture. We discussed this at length, and eventually took
> > the view that the least disservice to users of that port is to provide
> > reasonable notice of its discontinuation. We recognise and acknowledge
> > that discontinuing any port is unavoidably disruptive.
> >
> > The question of whether powerpc remains an architecture in the main
> archive
> > or moves to ports is one for FTP masters, not the release team.
> > [...]
> >
>
>


Re: Release Architectures for Debian 9 'Stretch'

2016-10-31 Thread Herminio Hernandez, Jr.
I have they in the past kept and architecture that was dropped as a release
arch?

On Mon, Oct 31, 2016 at 4:17 PM, Thadeu Lima de Souza Cascardo <
casca...@minaslivre.org> wrote:

> On Mon, Oct 31, 2016 at 11:58:31PM +0100, Riccardo Mottola wrote:
> > Hi,
> >
> >
> > On 31/10/2016 18:44, Lennart Sorensen wrote:
> > > I am not a DD, or a DM, but I have certainly helped fix problems for
> > > powerpc, including in language runtimes for languages I don't use.
> > > Unfortunately it seems the upstream for most things don't care much for
> > > anything other than x86 and arm these days which makes it harder for
> > > other architectures to stay working.
> >
> > since I am "upstream" for certain software I assure that I do care.
> Actually
> > I am one of the persons who tested GNUstep stuff on PPC. I know of other
> > people happily using GNUstep on PPC. To do that, I need a usable
> operating
> > system of course... up to know it was debian. What could it be int he
> > future?
> > Perhaps not all upstream counts and we don't even need al possible
> packages
> > on PPC. But it is still possible today to have a ncie usable desktop
> setup.
> >
> > This Debian decision will make a dim future for PowerPC developers, not
> just
> > users: a chicken-egg problem.
> >
> > Riccardo
> >
>
> Well, as I understand, the release team decided there is not going to be
> a Debian Stretch release for PowerPC. We can still ask the ftp-masters
> and DSA to keep powerpc for testing and sid, and we will have to do our
> own release. It's harder without all the infrastructure and work the
> release team puts into a release. But it's still something we could do.
> In the worst case, we can try to publish some install media and use the
> debian-ports infrastructure that is going to use a rolling release,
> based on sid.
>
> The only powerpc I had until now was a Nintendo Wii, and though there
> are patches around that would make D-I usable, I was still playing with
> some other hacks before I could try to push for them in Debian proper,
> and it was not on my top priority. Too bad I couldn't foresee that if I
> got much more involved long before, I could say to the release team I
> was already doing porter work. But since I was not, it looked like any
> volunteering from my part would have made no difference at all.
>
> However, I just ordered and old iBook G4, and I hope I can at least test
> D-I images I could maybe help prepare. Would that help you keep testing
> your code on PPC?  :-)
>
> By the way, thanks a lot for helping all these years with the ppc port.
> I have watched from a distance, which was a mistake. Hope I can help
> with keeping up the port alive somehow.
>
> Best regards.
> Cascardo.
>


Re: Release Architectures for Debian 9 'Stretch'

2016-10-31 Thread Herminio Hernandez Jr.
I saw that after I asked the question. It just really stinks. 

Sent from my iPhone

> On Oct 31, 2016, at 9:18 AM, Lennart Sorensen <lsore...@csclub.uwaterloo.ca> 
> wrote:
> 
>> On Mon, Oct 31, 2016 at 09:09:56AM -0700, Herminio Hernandez Jr.  wrote:
>> Is there even a chance for PowerPC to return as a release architecture for 
>> Debian 10 or is that just wishful thinking. 
> 
> Well as pointed out in the meeting, it does not seem any architecture
> has ever done so.  No rule against it, but the standards for getting in
> are higher than for staying in.
> 
> -- 
> Len Sorensen



Re: Release Architectures for Debian 9 'Stretch'

2016-10-31 Thread Herminio Hernandez Jr.
Is there even a chance for PowerPC to return as a release architecture for 
Debian 10 or is that just wishful thinking. 

Sent from my iPhone

> On Oct 31, 2016, at 8:54 AM, Lennart Sorensen  
> wrote:
> 
>> On Mon, Oct 31, 2016 at 03:33:32PM +, luigi burdo wrote:
>> Really Bad news for all us who have a ppc64 hardware, server or emb too.
> 
> No kidding.  My impression from just being on the mailing list was
> that anyone that tried to step up was told they weren't qualified for
> some reason.
> 
> -- 
> Len Sorensen
> 



Re: powerpc64 in testing install

2016-10-22 Thread Herminio Hernandez Jr.
I know that but I did not see those choices as of the latest testing image. 

Sent from my iPhone

> On Oct 22, 2016, at 1:48 AM, Gatis Visnevskis <ga...@pie-dabas.net> wrote:
> 
> Some time ago, install choices were changed:
> 
> install -> install32
> install64 - > install
> 
> This means 64-bit kernel is now default
> 
> Gasha
> 
>> On 2016.10.20. 19:22, Lennart Sorensen wrote:
>>> On Wed, Oct 19, 2016 at 11:26:17PM -0700, Herminio Hernandez, Jr. wrote:
>>> I just grabbed the latest testing powerpc netinst iso and saw I no long had
>>> the option of a 64-bit kernel install, So is Stretch is not going to have
>>> PowerPC 64-bit support?
>> 
>> That's odd.
>> 
>> I do see this:
>> 
>> https://packages.debian.org/search?keywords=linux-image-4.7.0-1-powerpc64
>> 
>> So that seems like a mistake.  Certainly installing powerpc arch on a
>> 64bit ppc machine is very common.  I certainly see no reason to have a
>> 64 bit compiled user space in general, but the 64 bit kernel makes lots
>> of sense.
>> 
>> Unless it simply doesn't ask and installs the right kernel anyhow.
>> 
> 



powerpc64 in testing install

2016-10-20 Thread Herminio Hernandez, Jr.
I just grabbed the latest testing powerpc netinst iso and saw I no long had
the option of a 64-bit kernel install, So is Stretch is not going to have
PowerPC 64-bit support?


Re: Debian 8.6 fails startup for Apple PPCs

2016-10-17 Thread Herminio Hernandez Jr.
I have used MATE. It works ok PPC

Sent from my iPhone

> On Oct 16, 2016, at 11:24 PM, Mathieu Malaterre  wrote:
> 
>> On Sat, Oct 15, 2016 at 10:12 PM, Kristen  wrote:
>> List,
>> 
>> I am wondering if the Apple PowerPC line of computers are still
>> supported in Debian? I have tried to use a netinstall of Debian 8.6.0 on
>> a G3 iBook, a G4 MP, and a G5 iMac and all have failed in the same manner.
>> 
>> The install appears to progress wonderfully. However after the initial
>> reboot the system fails with a message reading "Oh no! Something has
>> gone wrong.". If I click the button to "Log out" I am given only a blank
>> black screen. The virtual terminals also fail to respond. I suppose I
>> can SSH in if I hunt for the IP address assigned via DHCP.
>> 
>> Any thoughts about this?
> 
> I cannot find the thread anymore but basically GNOME 3.x has extra
> requirement, which older graphics cards do not have. As suggested, you
> should pick another desktop environment. I would also avoid KDE. I am
> a happy xfce user, but MATE may work if you want to stay closer to
> GNOME 2.x (not tested)
> 
> -M
> 



Re: Debian 8.6 fails startup for Apple PPCs

2016-10-15 Thread Herminio Hernandez, Jr.
Have you tried this in yaboot

Linux radeon.agpmode=-1

On Sat, Oct 15, 2016 at 7:01 PM, Kristen <kris...@atmyhome.org> wrote:
> On 10/15/16 3:11 PM, Herminio Hernandez, Jr. wrote:
>> I  run Debian on a PowerBook G4, iBook G4, PM G4 MDD, and PM G5. I
>> have not seen that error before. What graphics card are you using?
>
> The G3 is an iBook. From http://everymac.com I see the card is an ATI
> Mobility Radeon 7500 (2X AGP) with 32 MB of SDRAM
>
> The G4 Gigabit computer has a AGP ATI Radeon 9600 256MB Mac Pro card.
> This is an after market card.
>
> The G5 iMac has ATI Radeon 9600 with 128 MB of DDR SDRAM (AGP 8X
> support). Again per everymac.com listing.
>
> Of course the G3 and G5 are factory as they can not be changed out. Only
> the G4 has another card then factory.
>
> So it would appear everything is Radeon and  I think there is a big
> problem with ATI cards and this version of Debian. If I recall, but I
> have not searched the archives of this list.
>
> Kristen
>
>>
>> On Sat, Oct 15, 2016 at 1:12 PM, Kristen <kris...@atmyhome.org> wrote:
>>> List,
>>>
>>> I am wondering if the Apple PowerPC line of computers are still
>>> supported in Debian? I have tried to use a netinstall of Debian 8.6.0 on
>>> a G3 iBook, a G4 MP, and a G5 iMac and all have failed in the same manner.
>>>
>>> The install appears to progress wonderfully. However after the initial
>>> reboot the system fails with a message reading "Oh no! Something has
>>> gone wrong.". If I click the button to "Log out" I am given only a blank
>>> black screen. The virtual terminals also fail to respond. I suppose I
>>> can SSH in if I hunt for the IP address assigned via DHCP.
>>>
>>> Any thoughts about this?
>>>
>>> Kristen
>>>
>>
>
>



Re: Debian 8.6 fails startup for Apple PPCs

2016-10-15 Thread Herminio Hernandez, Jr.
I  run Debian on a PowerBook G4, iBook G4, PM G4 MDD, and PM G5. I
have not seen that error before. What graphics card are you using?

On Sat, Oct 15, 2016 at 1:12 PM, Kristen  wrote:
> List,
>
> I am wondering if the Apple PowerPC line of computers are still
> supported in Debian? I have tried to use a netinstall of Debian 8.6.0 on
> a G3 iBook, a G4 MP, and a G5 iMac and all have failed in the same manner.
>
> The install appears to progress wonderfully. However after the initial
> reboot the system fails with a message reading "Oh no! Something has
> gone wrong.". If I click the button to "Log out" I am given only a blank
> black screen. The virtual terminals also fail to respond. I suppose I
> can SSH in if I hunt for the IP address assigned via DHCP.
>
> Any thoughts about this?
>
> Kristen
>



Re: PowerPC agpmode issues

2016-10-08 Thread Herminio Hernandez, Jr.
Performed an apt dist-upgrade and rebooted with agpmode=4 and still the GPU
is failing with errors. Should I proceed to place a bug report on this?

Herminio

On Tue, Sep 20, 2016 at 11:20 PM, Herminio Hernandez, Jr. <
herminio.hernande...@gmail.com> wrote:

> I am still getting errors even with radeon.agpmode=4 is set
>
> rican-linux@Debian-G5:~$ dmesg |grep -e radeom -e drm -e radeon.agpmode
> [0.00] Kernel command line: 
> root=UUID=aeca9a67-31d7-4c4b-a0f8-4db328b33305
> radeon.agpmode=4
> [9.734366] [drm] Initialized drm 1.1.0 20060810
> [   10.934519] [drm] radeon kernel modesetting enabled.
> [   10.943743] fb: switching to radeondrmfb from OFfb ATY,Simone
> [   10.954622] fb: switching to radeondrmfb from OFfb ATY,Simone
> [   10.956515] [drm] initializing kernel modesetting (RV350 0x1002:0x4150
> 0x1002:0x4150 0x00).
> [   10.956552] [drm] register mmio base: 0xA000
> [   10.956558] [drm] register mmio size: 65536
> [   11.046327] [drm] Not an x86 BIOS ROM, not using.
> [   11.046358] [drm] Using device-tree clock info
> [   11.046369] [drm] AGP mode requested: 4
> [   11.046528] [drm] Generation 2 PCI interface, using max accessible
> memory
> [   11.046582] [drm] Detected VRAM RAM=256M, BAR=256M
> [   11.046587] [drm] RAM width 128bits DDR
> [   11.046858] [drm] radeon: 64M of VRAM memory ready
> [   11.046866] [drm] radeon: 256M of GTT memory ready.
> [   11.046935] [drm] radeon: 1 quad pipes, 1 Z pipes initialized.
> [   11.061306] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [   11.061312] [drm] Driver supports precise vblank timestamp query.
> [   11.061363] [drm] radeon: irq initialized.
> [   11.061405] [drm] Loading R300 Microcode
> [   11.110467] [drm] radeon: ring at 0x0001
> [   11.257952] [drm:.r100_ring_test [radeon]] *ERROR* radeon: ring test
> failed (scratch(0x15E4)=0xCAFEDEAD)
> [   11.258060] [drm:.r100_cp_init [radeon]] *ERROR* radeon: cp isn't
> working (-22).
> [   11.404548] [drm:.r100_cp_fini [radeon]] *ERROR* Wait for CP idle
> timeout, shutting down CP.
> [   11.551199] [drm] radeon: cp finalized
> [   12.547388] [drm] radeon: cp finalized
> [   12.553854] [drm] radeon: ttm finalized
> [   12.553861] [drm] Forcing AGP to PCI mode
> [   12.643384] [drm] Not an x86 BIOS ROM, not using.
> [   12.643406] [drm] Using device-tree clock info
> [   12.643414] [drm] Generation 2 PCI interface, using max accessible
> memory
> [   12.643446] [drm] Detected VRAM RAM=256M, BAR=256M
> [   12.643452] [drm] RAM width 128bits DDR
> [   12.643712] [drm] radeon: 64M of VRAM memory ready
> [   12.643719] [drm] radeon: 512M of GTT memory ready.
> [   12.643761] [drm] GART: num cpu pages 8192, num gpu pages 131072
> [   12.645324] [drm] radeon: 1 quad pipes, 1 Z pipes initialized.
> [   12.645343] [drm] PCI GART of 512M enabled (table at
> 0x62F8).
> [   12.645462] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [   12.645468] [drm] Driver supports precise vblank timestamp query.
> [   12.645512] [drm] radeon: irq initialized.
> [   12.645689] [drm] radeon: ring at 0x9001
> [   12.793131] [drm:.r100_ring_test [radeon]] *ERROR* radeon: ring test
> failed (scratch(0x15E4)=0xCAFEDEAD)
> [   12.793235] [drm:.r100_cp_init [radeon]] *ERROR* radeon: cp isn't
> working (-22).
> [   12.939961] [drm:.r100_cp_fini [radeon]] *ERROR* Wait for CP idle
> timeout, shutting down CP.
> [   12.940193] [drm] radeon: cp finalized
> [   12.944581] [drm] Connector Table: 12 (mac g5 9600)
> [   12.944609] [drm] No valid Ext TMDS info found in BIOS
> [   12.944621] [drm] No TV DAC info found in BIOS
> [   12.944798] [drm] No TMDS info found in BIOS
> [   12.944974] [drm] Radeon Display Connectors
> [   12.944981] [drm] Connector 0:
> [   12.944985] [drm]   DVI-I-1
> [   12.944990] [drm]   HPD1
> [   12.944995] [drm]   DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
> [   12.945000] [drm]   Encoders:
> [   12.945005] [drm] DFP2: INTERNAL_DVO1
> [   12.945010] [drm] CRT2: INTERNAL_DAC2
> [   12.945015] [drm] Connector 1:
> [   12.945019] [drm]   DVI-I-2
> [   12.945023] [drm]   HPD2
> [   12.945028] [drm]   DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
> [   12.945033] [drm]   Encoders:
> [   12.945037] [drm] DFP1: INTERNAL_TMDS1
> [   12.945042] [drm] CRT1: INTERNAL_DAC1
> [   12.945046] [drm] Connector 2:
> [   12.945051] [drm]   SVIDEO-1
> [   12.945055] [drm]   Encoders:
> [   12.945059] [drm] TV1: INTERNAL_DAC2
> [   13.028211] [drm] fb mappable at 0xB004
> [   13.028229] [drm] vram apper at 0xB000
> [   13.028234] [drm] size 8323072
> [   13.028238] [drm] fb depth is 24
> [   13.028243] [drm]pitch is 7680
> [   13.122329] rad

Re: PowerPC agpmode issues

2016-09-21 Thread Herminio Hernandez, Jr.
I am still getting errors even with radeon.agpmode=4 is set

rican-linux@Debian-G5:~$ dmesg |grep -e radeom -e drm -e radeon.agpmode
[0.00] Kernel command line:
root=UUID=aeca9a67-31d7-4c4b-a0f8-4db328b33305  radeon.agpmode=4
[9.734366] [drm] Initialized drm 1.1.0 20060810
[   10.934519] [drm] radeon kernel modesetting enabled.
[   10.943743] fb: switching to radeondrmfb from OFfb ATY,Simone
[   10.954622] fb: switching to radeondrmfb from OFfb ATY,Simone
[   10.956515] [drm] initializing kernel modesetting (RV350 0x1002:0x4150
0x1002:0x4150 0x00).
[   10.956552] [drm] register mmio base: 0xA000
[   10.956558] [drm] register mmio size: 65536
[   11.046327] [drm] Not an x86 BIOS ROM, not using.
[   11.046358] [drm] Using device-tree clock info
[   11.046369] [drm] AGP mode requested: 4
[   11.046528] [drm] Generation 2 PCI interface, using max accessible memory
[   11.046582] [drm] Detected VRAM RAM=256M, BAR=256M
[   11.046587] [drm] RAM width 128bits DDR
[   11.046858] [drm] radeon: 64M of VRAM memory ready
[   11.046866] [drm] radeon: 256M of GTT memory ready.
[   11.046935] [drm] radeon: 1 quad pipes, 1 Z pipes initialized.
[   11.061306] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   11.061312] [drm] Driver supports precise vblank timestamp query.
[   11.061363] [drm] radeon: irq initialized.
[   11.061405] [drm] Loading R300 Microcode
[   11.110467] [drm] radeon: ring at 0x0001
[   11.257952] [drm:.r100_ring_test [radeon]] *ERROR* radeon: ring test
failed (scratch(0x15E4)=0xCAFEDEAD)
[   11.258060] [drm:.r100_cp_init [radeon]] *ERROR* radeon: cp isn't
working (-22).
[   11.404548] [drm:.r100_cp_fini [radeon]] *ERROR* Wait for CP idle
timeout, shutting down CP.
[   11.551199] [drm] radeon: cp finalized
[   12.547388] [drm] radeon: cp finalized
[   12.553854] [drm] radeon: ttm finalized
[   12.553861] [drm] Forcing AGP to PCI mode
[   12.643384] [drm] Not an x86 BIOS ROM, not using.
[   12.643406] [drm] Using device-tree clock info
[   12.643414] [drm] Generation 2 PCI interface, using max accessible memory
[   12.643446] [drm] Detected VRAM RAM=256M, BAR=256M
[   12.643452] [drm] RAM width 128bits DDR
[   12.643712] [drm] radeon: 64M of VRAM memory ready
[   12.643719] [drm] radeon: 512M of GTT memory ready.
[   12.643761] [drm] GART: num cpu pages 8192, num gpu pages 131072
[   12.645324] [drm] radeon: 1 quad pipes, 1 Z pipes initialized.
[   12.645343] [drm] PCI GART of 512M enabled (table at 0x62F8).
[   12.645462] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   12.645468] [drm] Driver supports precise vblank timestamp query.
[   12.645512] [drm] radeon: irq initialized.
[   12.645689] [drm] radeon: ring at 0x9001
[   12.793131] [drm:.r100_ring_test [radeon]] *ERROR* radeon: ring test
failed (scratch(0x15E4)=0xCAFEDEAD)
[   12.793235] [drm:.r100_cp_init [radeon]] *ERROR* radeon: cp isn't
working (-22).
[   12.939961] [drm:.r100_cp_fini [radeon]] *ERROR* Wait for CP idle
timeout, shutting down CP.
[   12.940193] [drm] radeon: cp finalized
[   12.944581] [drm] Connector Table: 12 (mac g5 9600)
[   12.944609] [drm] No valid Ext TMDS info found in BIOS
[   12.944621] [drm] No TV DAC info found in BIOS
[   12.944798] [drm] No TMDS info found in BIOS
[   12.944974] [drm] Radeon Display Connectors
[   12.944981] [drm] Connector 0:
[   12.944985] [drm]   DVI-I-1
[   12.944990] [drm]   HPD1
[   12.944995] [drm]   DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
[   12.945000] [drm]   Encoders:
[   12.945005] [drm] DFP2: INTERNAL_DVO1
[   12.945010] [drm] CRT2: INTERNAL_DAC2
[   12.945015] [drm] Connector 1:
[   12.945019] [drm]   DVI-I-2
[   12.945023] [drm]   HPD2
[   12.945028] [drm]   DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
[   12.945033] [drm]   Encoders:
[   12.945037] [drm] DFP1: INTERNAL_TMDS1
[   12.945042] [drm] CRT1: INTERNAL_DAC1
[   12.945046] [drm] Connector 2:
[   12.945051] [drm]   SVIDEO-1
[   12.945055] [drm]   Encoders:
[   12.945059] [drm] TV1: INTERNAL_DAC2
[   13.028211] [drm] fb mappable at 0xB004
[   13.028229] [drm] vram apper at 0xB000
[   13.028234] [drm] size 8323072
[   13.028238] [drm] fb depth is 24
[   13.028243] [drm]pitch is 7680
[   13.122329] radeon :f0:10.0: fb0: radeondrmfb frame buffer device
[   13.175092] [drm] Initialized radeon 2.43.0 20080528 for :f0:10.0 on
minor 0
rican-linux@Debian-G5:~$


On Mon, Sep 19, 2016 at 11:20 PM, Michel Dänzer <mic...@daenzer.net> wrote:

> On 20/09/16 12:43 PM, Herminio Hernandez, Jr. wrote:
> >
> > Yes to both, however when I set radeon.agpmode=1 most of the time the
> > kernel freezes when booting. When I do get past that I get these errors:
>
> [...]
>
> > *[   11.415769] [drm:.radeon_agp_init [radeon]] *ERROR* Illegal AGP
> > Mode: 1 (valid 4, 8), leaving at 8*
>
> As you can see, AGP 1x isn't supported by your setup, only 4x or 8x. How
> a

Re: PowerPC agpmode issues

2016-09-19 Thread Herminio Hernandez, Jr.
Michel,

Yes to both, however when I set radeon.agpmode=1 most of the time the
kernel freezes when booting. When I do get past that I get these errors:

rican-linux@Debian-G5:~$ dmesg |grep -e radeon -e drm
*[0.00] Kernel command line:
root=UUID=aeca9a67-31d7-4c4b-a0f8-4db328b33305  radeon.agpmode=1*
[   10.432049] [drm] Initialized drm 1.1.0 20060810
[   11.291427] [drm] radeon kernel modesetting enabled.
[   11.302838] fb: switching to radeondrmfb from OFfb ATY,Simone
[   11.317952] fb: switching to radeondrmfb from OFfb ATY,Simone
[   11.321318] radeon :f0:10.0: enabling device (0006 -> 0007)
[   11.321741] [drm] initializing kernel modesetting (RV350 0x1002:0x4150
0x1002:0x4150 0x00).
[   11.321770] [drm] register mmio base: 0xA000
[   11.321776] [drm] register mmio size: 65536
[   11.321820] radeon :f0:10.0: Invalid PCI ROM header signature:
expecting 0xaa55, got 0x
[   11.415530] [drm] Not an x86 BIOS ROM, not using.
[   11.415573] [drm] Using device-tree clock info
*[   11.415769] [drm:.radeon_agp_init [radeon]] *ERROR* Illegal AGP Mode: 1
(valid 4, 8), leaving at 8*
[   11.415818] radeon :f0:10.0: putting AGP V3 device into 8x mode
[   11.415925] radeon :f0:10.0: GTT: 256M 0x - 0x0FFF
[   11.415933] [drm] Generation 2 PCI interface, using max accessible memory
[   11.415943] radeon :f0:10.0: VRAM: 256M 0xB000 -
0xBFFF (64M used)
[   11.415987] [drm] Detected VRAM RAM=256M, BAR=256M
[   11.415993] [drm] RAM width 128bits DDR
[   11.416229] [drm] radeon: 64M of VRAM memory ready
[   11.416237] [drm] radeon: 256M of GTT memory ready.
[   11.416308] [drm] radeon: 1 quad pipes, 1 Z pipes initialized.
[   11.431606] radeon :f0:10.0: WB disabled
[   11.431627] radeon :f0:10.0: fence driver on ring 0 use gpu addr
0x and cpu addr 0xd3ee
[   11.431642] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   11.431648] [drm] Driver supports precise vblank timestamp query.
[   11.431700] [drm] radeon: irq initialized.
[   11.431743] [drm] Loading R300 Microcode
[   11.488921] radeon :f0:10.0: firmware: direct-loading firmware
radeon/R300_cp.bin
[   11.489178] [drm] radeon: ring at 0x0001





*[   11.637210] [drm:.r100_ring_test [radeon]] *ERROR* radeon: ring test
failed (scratch(0x15E4)=0xCAFEDEAD)[   11.637318] [drm:.r100_cp_init
[radeon]] *ERROR* radeon: cp isn't working (-22).[   11.637331] radeon
:f0:10.0: failed initializing CP (-22).[   11.637338] radeon
:f0:10.0: Disabling GPU acceleration[   11.784325] [drm:.r100_cp_fini
[radeon]] *ERROR* Wait for CP idle timeout, shutting down CP.[   11.931351]
[drm] radeon: cp finalized*



*[   11.931464] radeon :f0:10.0: (r300_asic_reset:425)
RBBM_STATUS=0x80010140[   12.431463] radeon :f0:10.0:
(r300_asic_reset:444) RBBM_STATUS=0x80010140[   12.927471] radeon
:f0:10.0: (r300_asic_reset:456) RBBM_STATUS=0x0140[   12.927510]
radeon :f0:10.0: GPU reset succeed*



On Mon, Sep 19, 2016 at 8:05 PM, Michel Dänzer  wrote:

> On 19/09/16 09:36 PM, Mathieu Malaterre wrote:
> >
> > Finally your dmesg looks odd since the line `[drm] Forcing AGP to PCI
> > mode` comes only after the first error.
>
> That isn't odd but the AGP->PCI(e) fallback mechanism working as
> intended, trying AGP first and falling back to PCIe if AGP fails.
>
> Herminio, does the problem also occur if you specify radeon.agpmode=-1
> (or maybe =1) on the kernel command line?
>
>
> --
> Earthling Michel Dänzer   |   http://www.amd.com
> Libre software enthusiast | Mesa and X developer
>


Re: yaboot 1.3.17 broken

2016-07-09 Thread Herminio Hernandez Jr.
Thanks Dan. I will keep looking. 

Sent from my iPhone

> On Jul 9, 2016, at 7:19 PM, Dan DeVoto <dand1...@yahoo.com> wrote:
> 
> I haven't seen these problems on Debian Sid.  Just to check, I ran ybin and 
> even yabootconfig to completely rewrite my yaboot.conf from scratch, and 
> still no problems.  I'm afraid I don't know what's behind your bug.
> 
> Regards,
> 
> Dan
> 
> ----
> On Fri, 7/8/16, Herminio Hernandez Jr <herminio.hernande...@gmail.com> wrote:
> 
> Subject: yaboot 1.3.17 broken
> To: debian-powerpc@lists.debian.org
> Date: Friday, July 8, 2016, 8:37 PM
> 
> I do not know if anyone else is
> having this issue but if you make any
> changes to yaboot.conf and try up date the bootloader with
> 'ybin -v' and
> reboot, the system will not start. I needed reinstall Jessie
> set up my
> yaboot.conf the way I wanted it updated the bootloader and
> then upgrade
> to Stretch. I have the same issue in Gentoo, thankfully
> there I can just
> load the live cd and do my changes. 
> 
> I found that the current version of yaboot 1.3.17 is broken
> (at least in
> my experience). The only solution I have seen is to
> downgrade to 1.3.16. I have also heard that yaboot is no
> longer been maintained upstream as well. I researched and
> found that the website is down so I am thinking this is
> correct.
> 
> I have not seen any reports on this in BTS so I wondering if
> this is even a
> universal problem. I am that someone can confirm if the is
> the case or
> not.
> 
> Finally does any know if migrating to grub2 is a viable
> option for ppc
> and ppc64?
> 
> Thanks
> Herminio



yaboot 1.3.17 broken

2016-07-08 Thread Herminio Hernandez Jr
I do not know if anyone else is having this issue but if you make any
changes to yaboot.conf and try up date the bootloader with 'ybin -v' and
reboot, the system will not start. I needed reinstall Jessie set up my
yaboot.conf the way I wanted it updated the bootloader and then upgrade
to Stretch. I have the same issue in Gentoo, thankfully there I can just
load the live cd and do my changes. 

I found that the current version of yaboot 1.3.17 is broken (at least in
my experience). The only solution I have seen is to downgrade to 1.3.16. I have 
also heard that yaboot is no longer been maintained upstream as well. I 
researched and found that the website is down so I am thinking this is correct.

I have not seen any reports on this in BTS so I wondering if this is even a
universal problem. I am that someone can confirm if the is the case or
not.

Finally does any know if migrating to grub2 is a viable option for ppc
and ppc64?

Thanks
Herminio


signature.asc
Description: Digital signature


Re: Radeon driver not works on PPC with X800

2016-06-18 Thread Herminio Hernandez Jr.
Also see if creating an xorg.conf file and setting Accel to False will get it 
working. 

Sent from my iPhone

> On Jun 18, 2016, at 6:15 AM, TCH <t...@amigaspirit.hu> wrote:
> 
> Nope, did not work, still black screen. I installed all the packages (except 
> the DBG ones), but still got a black screen after boot. With or without 
> modesetting.
> 
> 2016-06-17 23:54 GMT+02:00 Dan DeVoto <dand1...@yahoo.com>:
>> You might want to look at this message, too:
>> 
>> https://lists.debian.org/debian-powerpc/2016/06/msg00140.html
>> 
>> It links to 3rd party ums-debs that might still work.
>> 
>> Regards,
>> 
>> Dan
>> 
>> 
>> On Fri, 6/17/16, TCH <t...@amigaspirit.hu> wrote:
>> 
>>  Subject: Re: Radeon driver not works on PPC with X800
>>  To: "Dan DeVoto" <dand1...@yahoo.com>
>>  Cc: "Herminio Hernandez Jr." <herminio.hernande...@gmail.com>, 
>> "debian-powerpc@lists.debian.org" <debian-powerpc@lists.debian.org>
>>  Date: Friday, June 17, 2016, 6:50 AM
>> 
>>  Yeah, i
>>  noticed it and even if it wasn't about X800, i tried it.
>>  However, if i enabled the radeonfb, then it was a permanent
>>  freeze, even with nomodeset.
>>  2016-06-17 6:58 GMT+02:00
>>  Dan DeVoto <dand1...@yahoo.com>:
>>  Yes, and
>>  the FAQ has info on fixing the messed up colors by enabling
>>  the Radeon framebuffer and enabling 24-bit colors with a
>>  xorg.conf file.  It doesn't specifically mention the
>>  X800, but your symptoms sound similar to those suffered by
>>  certain iBooks and eMacs noted in the FAQ.
>> 
>> 
>> 
>>  Regards,
>> 
>> 
>> 
>>  Dan
> 


Re: Radeon driver not works on PPC with X800

2016-06-16 Thread Herminio Hernandez Jr.
Add the line video=screen resolution. For example for 1024x768

video=1024x768-32

Sent from my iPhone

> On Jun 16, 2016, at 1:32 AM, TCH <t...@amigaspirit.hu> wrote:
> 
> Same black screen and freeze. If i try "Linux radeon.modeset=0" then the 
> system boots up, but i get a 640x480 screen with chaotic colours.
> 
> 2016-06-16 1:53 GMT+02:00 Herminio Hernandez, Jr. 
> <herminio.hernande...@gmail.com>:
>> try at yaboot this:
>> 
>> Linux radeon.agpmode=-1
>> 
>>> On Wed, Jun 15, 2016 at 4:15 PM, TCH <t...@amigaspirit.hu> wrote:
>>> Hi!
>>> 
>>> I have an old G4 MDD, with an X800 card. I've just installed Debian Jessie 
>>> and tried to breathe life into the 2d acceleration, but without success. If 
>>> i install "firmware-linux-nonfree", then it loads the "r420_cp.bin", but 
>>> then i only got a black screen after boot and the machine freezes 
>>> completely.
>>> 
>>> My dmesg log:
>>> http://oscomp.hu/depot/dmesg.log
>>> 
>>> And xorg.log after a crash:
>>> http://oscomp.hu/depot/Xorg.0.log
>>> 
>>> I don't know if i am at the right place with this, but nobody could help me 
>>> with this. Is this a known problem on PPC with X800 cards? I've read in 
>>> this topic (http://ubuntuforums.org/showthread.php?t=1825309=2) that 
>>> radeon not works with X800 on PPC.
>>> 
>>> Can anyone help me with this?
>>> 
>>> - TCH
> 


Re: [Stretch] Status for architecture qualification

2016-06-15 Thread Herminio Hernandez, Jr.
I know there are still powerpc users who run Debian. I am one of them and
love to see it continue. How can I help?

Thanks!

On Wed, Jun 15, 2016 at 5:12 PM, Hector Oron  wrote:

> [Add to CC debian-wb-team@ and r...@debian.org]
>
> Hello,
>
> 2016-06-05 12:01 GMT+02:00 Niels Thykier :
> > Hi members of DSA, Security, RT and all porters.
> >
> > While the freeze still seem far away, I think it is time to start with
> > the architecture qualifications.
>
> Excellent! Thanks
>
> I tried to follow the follow-up thread, ended up watching an hour
> video which was quite fun and forgot all details. :-)
>
> I have put up the classical wiki page for Stretch at:
>   https://wiki.debian.org/ArchiveQualification/Stretch
>
> Please review and comment if required.
>
> > For starters, here are the architectures we are aware of:
> >
> >  * amd64, i386, armel, armhf, arm64, mips, mipsel, powerpc, ppc64el,
> >s390x
> >- *No* blockers at this time from RT, DSA nor security.
> >- s390, ppc64el and all arm ports have DSA concerns.
>
> I understand s390x and ppc64el DSA concerns have been clarified
> in-list and those concerns are due to nature of the architecture.
>
> For the ARM ports, which have also been clarified, let me re-confirm:
>  * arm64 port has remote power and remote console available, plus
> geo-redundancy, hardware is available and there is more hardware
> coming in the pipeline. I am unsure why it is listed with multiple DSA
> concerns, that surprises me (with DSA and ARM porter hats). The port
> currently has 4 machines up, one down waiting to be replaced, in total
> 5 and more coming.
>  * armhf/armel ports share hardware, we currently have 6 machines up
> with remote power and remote console (of course that being development
> boards is not so nice as server remote management goodies). Some
> machines require a button press but local admins are great and always
> happy to help.
>
> If none steps up explaining what are DSA concerns on the ARM
> architectures, please update status requalification page dropping
> those concerns. [DSA hat on]
>
> I see armel has one porter listed, if more are needed, please add
> myself and Riku Voipio (armel buildd maints). [ARM hat on]
> I see arm64/armhf are covered porterwise however there should be more
> porters available if needed.
>
> >- armel has a RT concern about lack of buildds (only 2)
>
> >From the above comment: "armhf/armel ports share hardware, we
> currently have 6 machines up"
>
> >  * mips64el (NEW)
> >- No DSA buildd (RT blocker)
>
> As far as I can see mips64el is using shared builds with mipsel port
> hardware, those machines are DSA.
>
> >- Rebuild after import not complete (RT Blocker)
>
> Is there a list of packages that should be rebuilt?
>
> >- Not yet in testing (due to the above).
>
> Please let's work on getting it in testing ASAP I think the above
> blockers can be worked out quite reasonably.
>
> >  * kfreebsd-i386, kfreebsd-amd64
> >- Not included in Jessie due to lack of sustainable man-power (RT
> >  blocker)
> >- No news of the situation having changed
> >- If there is no news on the situation after DebConf16, I will
> >  assume kfreebsd-* will not target Stretch.
>
> Who has been keeping it up for stretch? (As a side note Stephen
> Chamberlain, Christoph Egger and many other people keep working on it)
> Not sure if those arches have more or less manpower than powerpc (in
> example). I think it would be great to make a call here, we either
> move kfreebsd ports to debian-ports infrastructure or go for the
> release with it.
>
> While working out ArchitectureQualification/Stretch wiki page I
> believe everything is mostly fine for release, however I got a
> personal concern on powerpc architecture. Is it well maintained? Does
> it have porters? Does it have users? Does it still make sense to carry
> along?
>
> Another concern (DSA) which I have added and explained in the wiki
> page is the lack of georedundancy for the 'mips' port. Verbatim copy
> from wiki follows:
> "mips: It has 5 buildds in the same datacenter, current hardware are
> routers or development boards which makes it very difficult to ship to
> other places. The host providing redundancy (lucatelli) at UBC-ECE
> must be decomissioned ASAP, leaving the port in a situation of not
> geographic redundancy. However advanced plans exists to deploy mips
> hardware in other data centers RSN."
>
> I'll keep you posted whenever there is progress on that area. I do not
> believe it should be a blocker for release, but we must ensure geo
> redundancy first.
>
> > Beyond mips64el, we are not aware of any new architectures for Stretch.
>
> Could you please check with sparc64 porters? I think some of them
> commented on the follow ups.
>
> Regards,
> --
>  Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.
>
>


Re: Radeon driver not works on PPC with X800

2016-06-15 Thread Herminio Hernandez, Jr.
try at yaboot this:

Linux radeon.agpmode=-1

On Wed, Jun 15, 2016 at 4:15 PM, TCH  wrote:

> Hi!
>
> I have an old G4 MDD, with an X800 card. I've just installed Debian Jessie
> and tried to breathe life into the 2d acceleration, but without success. If
> i install "firmware-linux-nonfree", then it loads the "r420_cp.bin", but
> then i only got a black screen after boot and the machine freezes
> completely.
>
> My dmesg log:
> http://oscomp.hu/depot/dmesg.log
>
> And xorg.log after a crash:
> http://oscomp.hu/depot/Xorg.0.log
>
> I don't know if i am at the right place with this, but nobody could help
> me with this. Is this a known problem on PPC with X800 cards? I've read in
> this topic (http://ubuntuforums.org/showthread.php?t=1825309=2) that
> radeon not works with X800 on PPC.
>
> Can anyone help me with this?
>
> - TCH
>
>


Re: Newbie, iMac G3 600MHz 1GB Ram, black screen

2016-06-15 Thread Herminio Hernandez Jr.
What is your video card?

Sent from my iPhone

> On Jun 15, 2016, at 8:41 AM, Alex Santos  wrote:
> 
> Hello
> 
> Source: debian-8.5.0-powerpc-netinst.iso
> Using entire 40GB HD for the install.
> 
> I tried to install only the utilities and i go as far as a single user prompt.
> 
> If I install any of the GUIs the computer goes as far as a black screen.
> 
> At the boot prompt is there something I can enter to edit a file? Perhaps a 
> cone file for the GPU. I am not sure how to work around the black screen.
> 
> I am sorry for such a basic question but I honestly can’t get around this 
> issue and have searched the ubuntu and Debian site for an answer but the 
> closest I can find is some kind of instructions for modifying the horizontal 
> and vertical refresh which I have done while inside the installer, after 
> choosing a shell to config a file with nano but after having done so, I get 
> the lower 1/3 of the screen with glitches looking graphics and the remaining 
> 2/3 solid black.
> 
> Would greatly appreciate a solid answer.
> 
> Kindest regards and thanks in advance.
> 
> —Alex 
> 
> 



Re: iMac G3 Snow 600MHz

2016-06-10 Thread Herminio Hernandez Jr.
Also Debian LXDE

Sent from my iPhone

> On Jun 9, 2016, at 11:41 PM, Mathieu Malaterre  wrote:
> 
>> On Thu, Jun 9, 2016 at 10:42 PM, Alex Santos  wrote:
>> Hello
>> 
>> I have an iMac G3 Snow 600MHz with a CDR. I would like to install some kind 
>> of Unix variant with a GUI. Can someone recommend a starting point.
> 
> You could try to install Debian with XFCE.
> 
> -M
> 



Re: old G5 iMac with NVIDIA card

2016-06-09 Thread Herminio Hernandez, Jr.
radeon comes with its own set of issues

On Thu, Jun 9, 2016 at 1:39 PM, Steven Grunza 
wrote:

> I suspect my problems are from the nouveau driver - wish I had a ATI
> Radeon instead of the nVidia
>
>
> On Thu, Jun 9, 2016 at 12:51 PM, G 3  wrote:
>
>> Here is the output of your command on my iMac G5: 0 radeondrmfb
>>
>>
>> On Thu, Jun 9, 2016 at 10:16 AM, Elimar Riesebieter 
>> wrote:
>>
>>> * Steven Grunza  [2016-06-09 09:45 -0400]:
>>>
>>> [...]
>>> > so it's not using the vesa driver
>>> >
>>> > Must be using the intel driver (which makes sense since this is an i7
>>> > laptop).
>>>
>>> $ cat /proc/fb
>>>
>>> shows you the framebuffer driver in use which corresponds to the X
>>> driver.
>>>
>>> Elimar
>>> --
>>>   Never make anything simple and efficient when a way
>>>   can be found to make it complex and wonderful ;-)
>>>
>>>
>>
>


Re: old G5 iMac with NVIDIA card

2016-06-09 Thread Herminio Hernandez Jr.
With those Radeon cards adding this at boot helps radeon.agpmode=-1

Sent from my iPhone

> On Jun 9, 2016, at 1:55 AM, G 3 <programmingk...@gmail.com> wrote:
> 
> Here is the information:
> 
> :f0:10.0 VGA compatible controller: Advanced Micro Devices, Inc. 
> [AMD/ATI] RV350 [Radeon 9550/9600/X1050 Series]
> 
> 
>> On Wed, Jun 8, 2016 at 10:07 PM, Herminio Hernandez Jr. 
>> <herminio.hernande...@gmail.com> wrote:
>> To see what video card you have run this command 
>> 
>> lspci | grep VGA
>> 
>> Sent from my iPhone
>> 
>>> On Jun 8, 2016, at 6:52 PM, G 3 <programmingk...@gmail.com> wrote:
>>> 
>>> I gave up on Debian so I don't have it installed anymore. But if you mean 
>>> what I have for Ubuntu Mate, I don't know. Maybe someone could send me a 
>>> command to execute and I can email the results back to the list.
>>> 
>>>> On Jun 8, 2016, at 8:03 PM, Steven Grunza wrote:
>>>> 
>>>> What video driver do you use?
>>>> 
>>>>> On Wed, Jun 8, 2016 at 6:56 PM, Programmingkid 
>>>>> <programmingk...@gmail.com> wrote:
>>>>> 
>>>>> On Jun 8, 2016, at 12:13 PM, Steven Grunza wrote:
>>>>> 
>>>>> > Does anyone know if the nouveau driver will work with an old G5 PowerPC 
>>>>> > and the GeForce FX G05200 it originally used?
>>>>> >
>>>>> > The last time I tried it had numerous problems (no graphics, kernel 
>>>>> > panics, etc).
>>>>> >
>>>>> > lsusb reports the video card as:
>>>>> >
>>>>> >  NVIDIA Corporation NV34M [GeForce FX Go5200]  (rev a1)
>>>>> >
>>>>> >
>>>>> > Various versions of jessie failed in various ways.  Does Stretch have a 
>>>>> > different version of the nouveau driver?  Since the machine is PowerPC 
>>>>> > I can't use the NVIDIA driver.
>>>>> >
>>>>> > - Steven G.
>>>>> 
>>>>> Debian is still broken when it comes to iMac G5 compatibility. My iMac G5 
>>>>> booted to a command prompt after installing Debian. I think the only fix 
>>>>> is to move on to a different distribution like Ubuntu Mate 15.10. It 
>>>>> works well on my iMac G5.
>>>>> 
>>>>> Just to note, my iMac G5 has a ATI Radeon 9600 in it, so your issues 
>>>>> might be different from mine.
>>>> 
>>> 
> 


Re: old G5 iMac with NVIDIA card

2016-06-08 Thread Herminio Hernandez Jr.
To see what video card you have run this command 

lspci | grep VGA

Sent from my iPhone

> On Jun 8, 2016, at 6:52 PM, G 3  wrote:
> 
> I gave up on Debian so I don't have it installed anymore. But if you mean 
> what I have for Ubuntu Mate, I don't know. Maybe someone could send me a 
> command to execute and I can email the results back to the list.
> 
>> On Jun 8, 2016, at 8:03 PM, Steven Grunza wrote:
>> 
>> What video driver do you use?
>> 
>>> On Wed, Jun 8, 2016 at 6:56 PM, Programmingkid  
>>> wrote:
>>> 
>>> On Jun 8, 2016, at 12:13 PM, Steven Grunza wrote:
>>> 
>>> > Does anyone know if the nouveau driver will work with an old G5 PowerPC 
>>> > and the GeForce FX G05200 it originally used?
>>> >
>>> > The last time I tried it had numerous problems (no graphics, kernel 
>>> > panics, etc).
>>> >
>>> > lsusb reports the video card as:
>>> >
>>> >  NVIDIA Corporation NV34M [GeForce FX Go5200]  (rev a1)
>>> >
>>> >
>>> > Various versions of jessie failed in various ways.  Does Stretch have a 
>>> > different version of the nouveau driver?  Since the machine is PowerPC I 
>>> > can't use the NVIDIA driver.
>>> >
>>> > - Steven G.
>>> 
>>> Debian is still broken when it comes to iMac G5 compatibility. My iMac G5 
>>> booted to a command prompt after installing Debian. I think the only fix is 
>>> to move on to a different distribution like Ubuntu Mate 15.10. It works 
>>> well on my iMac G5.
>>> 
>>> Just to note, my iMac G5 has a ATI Radeon 9600 in it, so your issues might 
>>> be different from mine.
>> 
> 


Re: Misc PowerPC News

2016-06-07 Thread Herminio Hernandez Jr.
Yes thank you again!

Sent from my iPhone

> On Jun 7, 2016, at 6:28 AM, Brock Wittrock  wrote:
> 
> Just wanted to say thanks Matheiu for all of your work with PPC and staying 
> on top of a lot of these bugs!
> 
> Brock
> 
>> On Tue, Jun 7, 2016 at 2:33 AM, luigi burdo  wrote:
>> Mathieu,
>> add this news too.
>> finally fixed  qemu on powerpc working with sdl2 and gtk3 with gl=on 
>> enabled. 
>> next git will be update with the code patch
>> 
>> Luigi
>> 
>> > From: ma...@debian.org
>> > Date: Tue, 7 Jun 2016 08:41:14 +0200
>> > Subject: Misc PowerPC News
>> > To: debian-powerpc@lists.debian.org
>> 
>> > 
>> > I've been playing a bit with BTS lately and I have setup powerpc &
>> > ppc64 tags on a few outstanding bugs related to PowerPC arch:
>> > 
>> > http://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=powerpc=debian-powerpc%40lists.debian.org
>> > http://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=ppc64=debian-powerpc%40lists.debian.org
>> > 
>> > Here is a summary of some outstanding issues that have either been
>> > solved or are being worked on:
>> > 
>> > 1. mono (http://bugs.debian.org/819711)
>> > 
>> > The issue with mono on PowerPC (and ppc64!) has been found and
>> > reported upstream. I'll keep an eye on the package to check that mono
>> > on PowerPC comes back in Debian.
>> > 
>> > 2. yaboot 1.3.17 (http://bugs.debian.org/819549)
>> > 
>> > Thanks to Milan Kupcevic we finally have yaboot 1.3.17 in Debian !
>> > There is still an issue with PPC64 build but a patch has been provided
>> > by Lennart Sorensen (http://bugs.debian.org/322540).
>> > 
>> > 3. partman-ext3 (http://bugs.debian.org/825110)
>> > 
>> > Debian Installer Stretch Alpha 6 release is currently broken as
>> > described in the bug report. But Milan Kupcevic managed to provide a
>> > work around. I've not tested but the daily installer should work, use
>> > it instead.
>> > 
>> > 4. OFfb red / blue color inversion (http://bugs.debian.org/825840)
>> > 
>> > Currently when using d-i the text based installation display inverted
>> > colors. I am currently tracking down why this is happening and if it
>> > possible to directly fix OFfb. There are alternatives describe in this
>> > bug tracker to fix the symptoms, namely to use radeon(fb) in place of
>> > OFfb. So d-i on PowerPC may not only be suited for color blind people
>> > after all :-)
>> > 
>> > 5. partman-auto (http://bugs.debian.org/610206)
>> > 
>> > By default yaboot is the bootloader on PowerPC. But there is a secret
>> > option in d-i to install grub-ieee1275 on CHRP IBM machines. I am
>> > trying to make that also an option for NewWorld Mac machines, one
>> > patch at a time.
>> > 
>> > 6. r300: Visuals not found in (default) depth = 24
>> > (http://bugs.debian.org/746272)
>> > 
>> > Users of the r300 driver needed to use an old patch
>> > (http://wiki.debian.org/PowerPC/FAQ#How_do_I_get_graphics_working.3F)
>> > to get the default depth working. This has now been fixed upstream and
>> > will be part of the next mesa release.
>> > 
>> > 7. No sound on PowerPC with Jessie upgrade (http://bugs.debian.org/714345)
>> > 
>> > There were actually two different issues that prevented some users to
>> > have sound working. They have both been solved by Wolfram Sang
>> > (http://bugs.debian.org/714345#120 &
>> > http://bugs.debian.org/714345#161). The first one is already in linux
>> > 4.5.5, and the last patch has been tagged for stable release in linux.
>> > 
>> > -M
>> > 
> 


Re: Bug#825110: ppc64 patch for yaboot FTBFS and e2fslibs1.41-dev

2016-06-06 Thread Herminio Hernandez Jr.
When will this fix be released 

Sent from my iPhone

> On Jun 6, 2016, at 1:34 PM, Lennart Sorensen  
> wrote:
> 
>> On Mon, Jun 06, 2016 at 08:23:32PM +0200, Mathieu Malaterre wrote:
>> Fixed ! I do not believe using #825110 make sense. Thanks for the patch !
> 
> I agree.
> 
> Now I do NOT have the hardware to test if the build works, but at least
> it now builds.
> 
> -- 
> Len Sorensen
> 



Re: Bug#825110: ppc64 patch for yaboot FTBFS and e2fslibs1.41-dev

2016-06-06 Thread Herminio Hernandez Jr.


Sent from my iPhone

> On Jun 6, 2016, at 1:34 PM, Lennart Sorensen  
> wrote:
> 
>> On Mon, Jun 06, 2016 at 08:23:32PM +0200, Mathieu Malaterre wrote:
>> Fixed ! I do not believe using #825110 make sense. Thanks for the patch !
> 
> I agree.
> 
> Now I do NOT have the hardware to test if the build works, but at least
> it now builds.
> 
> -- 
> Len Sorensen
> 



Re: Bug#825110: ppc64 patch for yaboot FTBFS and e2fslibs1.41-dev

2016-06-06 Thread Herminio Hernandez Jr.
I just installed Debian PPC64 on my PowerMac G5 and yaboot will not load the 
kernel. I know in Gentoo they have a separate yaboot package for PPC64 that I 
was able load the Gentoo PPC64 kernel with. My plan was to load the Gentoo 
LiveCD mount the Debian filesystem and re-run yabootconfig. However the LiveCD 
did not recognize the filesystem so I am out of luck. 

Sent from my iPhone

> On Jun 6, 2016, at 11:23 AM, Mathieu Malaterre  wrote:
> 
> unarchive 322540
> reopen 322540 1.3.17-3
> tags 322540 patch
> thanks
> 
> On Mon, Jun 6, 2016 at 6:57 PM, Lennart Sorensen
>  wrote:
>> On Tue, May 31, 2016 at 09:17:20AM -0400,  wrote:
 On Tue, May 31, 2016 at 02:07:31PM +0200, Mathieu Malaterre wrote:
 I understand your point for ppc64el, but since `yaboot` gets build on
 ppc64, some users may break their systems...
>>> 
>>> According to buildd, it fails to build on ppc64 (not surprising since
>>> it requires 32bit static libraries to link).  yaboot does not currently
>>> exist in the archive for anything other than 32bit powerpc.  So there
>>> is no reason for it to even attempt to build on 64bit.
>> 
>> Well in case anyone wants to try and fix it, these patches seem to fix
>> yaboot build on ppc64:
>> 
>> diff -urN yaboot-1.3.17.orig/debian/control yaboot-1.3.17/debian/control
>> --- yaboot-1.3.17.orig/debian/control   2015-11-02 02:54:41.0 +
>> +++ yaboot-1.3.17/debian/control2016-06-06 15:36:46.0 +
>> @@ -3,7 +3,7 @@
>> Priority: important
>> Maintainer: Debootloaders Yaboot Maintainers Team 
>> 
>> Uploaders: Aurélien GÉRÔME , Milan Kupcevic 
>> 
>> -Build-Depends: debhelper (>= 9), e2fslibs1.41-dev
>> +Build-Depends: debhelper (>= 9), e2fslibs1.41-dev, libc6-dev-powerpc [ppc64]
>> Standards-Version: 3.9.6
>> Homepage: http://yaboot.ozlabs.org
>> 
>> 
>> diff -urN e2fsprogs1.41-1.41.14.orig/debian/rules 
>> e2fsprogs1.41-1.41.14/debian/rules
>> --- e2fsprogs1.41-1.41.14.orig/debian/rules 2015-11-02 
>> 02:20:29.0 +
>> +++ e2fsprogs1.41-1.41.14/debian/rules  2016-06-06 15:56:42.0 +
>> @@ -4,6 +4,7 @@
>> 
>> export DEB_BUILD_MAINT_OPTIONS=hardening=-stackprotector
>> export DEB_CFLAGS_MAINT_APPEND=-fgnu89-inline -fno-builtin-malloc
>> +export CC:=$(CC) -m32
>> 
>> %:
>>dh $@  --with autotools-dev
>> @@ -11,10 +12,18 @@
>> override_dh_auto_install:
>>dh_auto_install --destdir=debian/tmp -- install-libs
>> 
>> +override_dh_auto_build:
>> +   dh_auto_build -- libs
>> +
>> override_dh_auto_clean:
>>dh_auto_clean
>>rm -f asm_types.h public_config.h
>> 
>> +override_dh_auto_test:
>> +
>> +override_dh_auto_configure:
>> +   dh_auto_configure -- --host=powerpc-linux-gnu 
>> --target=powerpc-linux-gnu
>> +
>> get-orig-source:
>>wget 
>> http://downloads.sourceforge.net/project/e2fsprogs/e2fsprogs/1.41.14/e2fsprogs-1.41.14.tar.gz
>>  \
>> -O e2fsprogs1.41_1.41.14.orig.tar.gz
>> 
>> The fix is that since yaboot is always built 32bit, then on ppc64 we
>> better build-dep on the 32bit libc headers and stuff, and when building
>> the e2fslibs it has to be built 32bit, not 64bit, since yaboot is the
>> only user and it is building 32bit.  While at it I made it stop building
>> all the other crap that wasn't actually being packaged since it was
>> taking too long to build.
>> 
>> I am not entirely pleased with the CC variable as a way to pass the
>> -m32 needed, but it seems to work.  Maybe someone can see a cleaner way
>> (maybe the configure command somehow) to do that.
>> 
>> I would have sent this to bug 322540 since that is the ppc64 yaboot
>> bug, but for some reason it is closed and archived even though it never
>> actually worked and was never actually built on ppc64.  That seems like
>> a mistake.
> 
> Fixed ! I do not believe using #825110 make sense. Thanks for the patch !
> 



Re: ppc64el netinst will not boot

2016-06-05 Thread Herminio Hernandez Jr.
I agree. 

Sent from my iPhone

> On Jun 5, 2016, at 7:44 PM, Programmingkid <programmingk...@gmail.com> wrote:
> 
> 
>> On Jun 5, 2016, at 10:35 PM, Lennart Sorensen wrote:
>> 
>>> On Fri, Jun 03, 2016 at 05:40:10PM -0400, Programmingkid wrote:
>>>> On Jun 3, 2016, at 2:05 PM, Herminio Hernandez Jr. wrote:
>>>> 
>>>> I have a PowerMac G5 and I tried to load the 64el iso and it will not 
>>>> boot. Has anyone had similar issues?
>>> 
>>> Yes. I tried installing it on my iMac G5 and it would not install. It is 
>>> probably made for IBM Power workstations and RS6000 systems only.
>> 
>> IBM Power8 (and maybe freescale e6500 since it supposedly is powerisa
>> 2.07b compliant too, but I can't find anything that says for sure) only.
> 
> I suggest a note be added to the PPC64el page that explicitly states this is 
> not for a Macintosh.



ppc64el netinst will not boot

2016-06-03 Thread Herminio Hernandez Jr.
I have a PowerMac G5 and I tried to load the 64el iso and it will not boot. Has 
anyone had similar issues?

Sent from my iPhone


Re: Powermac G5 - youtube video - SOLVED

2016-02-12 Thread Herminio Hernandez Jr.
Awesome!

Sent from my iPhone

> On Feb 12, 2016, at 11:44 AM, luigi burdo  wrote:
> 
> Confirmed working on Quad G5 with RadeonHD too .
> I can see again 1080p youtube video in html5!
> 
> Luigi
> 
> > Date: Fri, 12 Feb 2016 16:18:54 +0100
> > From: csae2...@uibk.ac.at
> > To: cl...@clivemenzies.co.uk
> > CC: debian-powerpc@lists.debian.org
> > Subject: Re: Powermac G5 - youtube video - SOLVED
> > 
> > Only thing is, with these solution you block out "Subtitles" option or " 
> > captions or CC . this is as far as i know only possible with flash or 
> > html5. correct me please if i am wrong
> > 
> > thanks
> > 
> > rich
> > 
> > Clive Menzies schrieb:
> > > 
> > > Thanks Rich
> > > 
> > > I had vlc but not browser-plugin-vlc
> > > 
> > > gecko-mediaplayer isn't in stretch but I installed it from jessie.
> > > 
> > > Still no joy on youtube videos. spinning disc in the middle of the frame 
> > > as though the stream is trying to download. Same result with html5.
> > > 
> > > However, I disabled html5 according to your earlier instruction and hey 
> > > presto - youtube plays :-)
> > > 
> > > /you can disable automatic playback of it by going to//
> > > //
> > > //in firefox//
> > > //
> > > //type//
> > > //
> > > //about:config (in statusbar)//
> > > //
> > > //then click "OK"//
> > > //
> > > //search for "webm" (again in statusbar)//
> > > //
> > > //disable automatic playback webm content or so.
> > > 
> > > /Many thanks/
> > > 
> > > /Clive/
> > > /
> > > 
> > > 
> > > On 12/02/16 13:24, Richard Kuenz wrote:
> > >> plus i would install also vlc-browser-plugin or similar for the distro 
> > >> you use. if you install vlc it probably gets installed automagically
> > >>
> > >> hope this helps clive
> > >>
> > >> rich
> > >>
> > >>
> > >> Am Feb 12, 2016 um 2:13 PM schrieb Clive Menzies 
> > >> :
> > >>
> > >>> Thanks Richard
> > >>>
> > >>> Regards
> > >>>
> > >>> Clive
> > >>>
> > >>> On 12/02/16 13:04, Richard Kuenz wrote:
> >  you need gecko-mediaplayer
> > 
> >  Clive Menzies schrieb:
> > > On 12/02/16 09:18, Chris Wareham wrote:
> > >> Hi Clive,
> > >>
> > >> YouTube should just work these days, since it falls back to using a 
> > >> HTML5
> > >> player. If it's not doing
> > >> that automatically then you can go to the following page to check:
> > >>
> > >> https://www.youtube.com/html5?gl=GB
> > >>
> > >> I think you may need some extra gstreamer plugins installed if it 
> > >> show you don't
> > >> have full support
> > >> for the required formats.
> > >>
> > >> I wouldn't bother with the Gnash or Lightspark plugins that 
> > >> attempted to create
> > >> open source
> > >> equivalents of the the Flash plugin. I found them very buggy and 
> > >> incomplete even
> > >> when they were
> > >> under active development.
> > >>
> > >> Cheers,
> > >>
> > >> Chris
> > >>
> > > Hi Chris
> > >
> > > I've got these and grepped apt-cache gstrreamer for mozilla/html but 
> > > couldn't find anything. Any idea of what may be missing? There seem 
> > > to be loads of them.
> > >
> > > clive@Pandora:~$ dpkg -l | grep gstreamer
> > > ii gstreamer0.10-alsa:powerpc 0.10.36-2 powerpc GStreamer plugin for 
> > > ALSA
> > > ii gstreamer0.10-gnomevfs:powerpc 0.10.36-2 powerpc GStreamer plugin 
> > > for GnomeVFS
> > > ii gstreamer0.10-plugins-base:powerpc 0.10.36-2 powerpc GStreamer 
> > > plugins from the "base" set
> > > ii gstreamer1.0-libav:powerpc 1.6.3-1 powerpc libav plugin for 
> > > GStreamer
> > > ii gstreamer1.0-plugins-base:powerpc 1.6.3-1 powerpc GStreamer 
> > > plugins from the "base" set
> > > ii gstreamer1.0-plugins-good:powerpc 1.6.3-1 powerpc GStreamer 
> > > plugins from the "good" set
> > > ii gstreamer1.0-x:powerpc 1.6.3-1 powerpc GStreamer plugins for X11 
> > > and Pango
> > > ii libgstreamer-plugins-base0.10-0:powerpc 0.10.36-2 powerpc 
> > > GStreamer libraries from the "base" set
> > > ii libgstreamer-plugins-base1.0-0:powerpc 1.6.3-1 powerpc GStreamer 
> > > libraries from the "base" set
> > > ii libgstreamer0.10-0:powerpc 0.10.36-1.5 powerpc Core GStreamer 
> > > libraries and elements
> > > ii libgstreamer1.0-0:powerpc 1.6.3-1 powerpc Core GStreamer libraries 
> > > and elements
> > > ii libreoffice-avmedia-backend-gstreamer 1:5.0.5~rc1-1 powerpc 
> > > GStreamer backend for LibreOffice
> > >
> > > Thanks
> > >
> > > Clive
> > >
> > 


Re: 32bit PowerPC

2016-02-09 Thread Herminio Hernandez Jr.
What laptops do you have? 

Sent from my iPhone

> On Feb 9, 2016, at 4:12 PM, Lennart Sorensen  
> wrote:
> 
>> On Tue, Feb 09, 2016 at 04:56:14PM -0500, k...@kirkg.us wrote:
>> Hello all,
>>  Does anyone still do anything with 32bit PowerPC? If so, I have a handful
>> of 32bit PowerPC laptops that I'm willing to donate to the cause. If there
>> is any interest, please let me know. I can outline what I have either to the
>> list in general, or to someone privately.
>>  Depending upon the circumstances, I may even be able to cover some of the
>> shipping.
> 
> Lots of people work with 32 bit powerpc embedded systems.  No idea if
> anyone would have any use for a laptop doing it though.
> 
> -- 
> Len Sorensen
> 



Re: 32bit PowerPC

2016-02-09 Thread Herminio Hernandez Jr.
I would be interested in one of the PowerBooks G4 if no one else is. I live  in 
TX. 

Sent from my iPhone

> On Feb 9, 2016, at 9:47 PM, Kirk Gleason <k...@kirkg.us> wrote:
> 
> From Indiana, US.
>> 
>> On Feb 9 2016, at 10:46 pm, Herminio Hernandez Jr. 
>> <herminio.hernande...@gmail.com> wrote: 
>> Where would you be shipping from US?
>> 
>> Herminio
>> 
>> Sent from my iPhone
>> 
>>> On Feb 9, 2016, at 9:22 PM, Aidan Sciortino <2001flyingpig...@gmail.com> 
>>> wrote:
>>> 
>>> I am interested in doing some ports for ppc. Some 32 bit hardware would be 
>>> good, depending on the age.
>>> 
>>> Thanks!
>>> 
>>> Aidan
>>> 
>>> On Tue, Feb 9, 2016 at 7:39 PM, Herminio Hernandez Jr. 
>>> <herminio.hernande...@gmail.com> wrote:
>>> What laptops do you have?
>>> 
>>> Sent from my iPhone
>>> 
>>> > On Feb 9, 2016, at 4:12 PM, Lennart Sorensen 
>>> > <lsore...@csclub.uwaterloo.ca> wrote:
>>> >
>>> >> On Tue, Feb 09, 2016 at 04:56:14PM -0500, k...@kirkg.us wrote:
>>> >> Hello all,
>>> >>  Does anyone still do anything with 32bit PowerPC? If so, I have a 
>>> >> handful
>>> >> of 32bit PowerPC laptops that I'm willing to donate to the cause. If 
>>> >> there
>>> >> is any interest, please let me know. I can outline what I have either to 
>>> >> the
>>> >> list in general, or to someone privately.
>>> >>  Depending upon the circumstances, I may even be able to cover some of 
>>> >> the
>>> >> shipping.
>>> >
>>> > Lots of people work with 32 bit powerpc embedded systems.  No idea if
>>> > anyone would have any use for a laptop doing it though.
>>> >
>>> > --
>>> > Len Sorensen
>>> >
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Aidan Sciortino
>>> Hacker, Inventor, 
>>> Dreamer, Engineer


Re: 32bit PowerPC

2016-02-09 Thread Herminio Hernandez Jr.
Where would you be shipping from US?

Herminio

Sent from my iPhone

> On Feb 9, 2016, at 9:22 PM, Aidan Sciortino <2001flyingpig...@gmail.com> 
> wrote:
> 
> I am interested in doing some ports for ppc. Some 32 bit hardware would be 
> good, depending on the age.
> 
> Thanks!
> 
> Aidan
> 
>> On Tue, Feb 9, 2016 at 7:39 PM, Herminio Hernandez Jr. 
>> <herminio.hernande...@gmail.com> wrote:
>> What laptops do you have?
>> 
>> Sent from my iPhone
>> 
>> > On Feb 9, 2016, at 4:12 PM, Lennart Sorensen 
>> > <lsore...@csclub.uwaterloo.ca> wrote:
>> >
>> >> On Tue, Feb 09, 2016 at 04:56:14PM -0500, k...@kirkg.us wrote:
>> >> Hello all,
>> >>  Does anyone still do anything with 32bit PowerPC? If so, I have a handful
>> >> of 32bit PowerPC laptops that I'm willing to donate to the cause. If there
>> >> is any interest, please let me know. I can outline what I have either to 
>> >> the
>> >> list in general, or to someone privately.
>> >>  Depending upon the circumstances, I may even be able to cover some of the
>> >> shipping.
>> >
>> > Lots of people work with 32 bit powerpc embedded systems.  No idea if
>> > anyone would have any use for a laptop doing it though.
>> >
>> > --
>> > Len Sorensen
>> >
> 
> 
> 
> -- 
> Aidan Sciortino
> Hacker, Inventor, 
> Dreamer, Engineer


Re: Hard-drive corrupted

2016-02-03 Thread Herminio Hernandez, Jr.
http://macsales.com is a great site. I was able SSD drives for my Powermac
G4.

On Wed, Feb 3, 2016 at 3:50 PM, Jonni O'Gorman 
wrote:

> Hi All,
>
> I also successfully installed Debian 8 on my PowerMac G5 - however shortly
> afterwards the home folder became corrupted and eventually the entire drive
> became unusable...
>
> so does anyone have a good resource for replacemnt hard drive for the old
> beast?
>
> thanks
> jonny
>
> On Tue, Dec 29, 2015 at 11:27 PM, Aidan Sciortino <
> 2001flyingpig...@gmail.com> wrote:
>
>> Hello,
>>
>> I've successfully gotten Debian 8 stable up and running on my powermac
>> g5, but am struggling to get a gui configured. The computer has an Nvidia
>> fx 5200 graphics card, and I'm using the nouveau driver.   The colors are
>> extremely messed up, and I'm thinking it's a problem with nouveau. Has
>> anyone else had this problem before? Does anyone know of a solution?
>>
>> Thanks
>>
>> Aidan
>> --
>> Aidan Sciortino
>> Inventor
>> Engineer
>> Dreamer
>>
>
>
>
> --
> jogideas.com
>


Re: Xorg server

2015-12-22 Thread Herminio Hernandez, Jr.
I have a radeon 9550 card. 3D acceleration is broken but I have 2D
acceleration when I force the card to PCI mode. It could be more an issue
with the video card rather than systemd.

On Tue, Dec 22, 2015 at 2:03 PM, Riccardo Mottola <
riccardo.mott...@libero.it> wrote:

> Herminio Hernandez, Jr. ha scritto:
>
>> what is your video card? I am running Debian Sid on my IBook G4 and just
>> did a dist-upgrade and am not seeing this issue.
>>
>
> ATI 3d Rage Mobility L (Mach64 card)
>
> Riccardo
>
>


Re: Xorg server

2015-12-22 Thread Herminio Hernandez, Jr.
what is your video card? I am running Debian Sid on my IBook G4 and just
did a dist-upgrade and am not seeing this issue.

On Tue, Dec 22, 2015 at 1:49 PM, Riccardo Mottola <
riccardo.mott...@libero.it> wrote:

> Hi,
>
> Herminio Hernandez Jr. ha scritto:
>
>> Are you running Sid?
>>
>
> yes, I do.
>
> I just installed legacy server and now I have X again.
>
> I really dislike certain choices debian and more generally most Linux
> distros are taking...
>
> Riccardo
>


Re: Xorg server

2015-12-22 Thread Herminio Hernandez Jr.
Are you running Sid?

Sent from my iPhone

> On Dec 22, 2015, at 10:50 AM, Riccardo Mottola  
> wrote:
> 
> Hi,
> 
> I have seen with regret that debian moved to some X needing systemd and a 
> kernel driver.
> After my update, I don't get X starting anymore on my iBook with ATI video.
> 
> Do we need to use the legacy server now?
> 
> Riccardo
> 



is mesa fixed?

2015-11-20 Thread Herminio Hernandez, Jr.
I noticed this in mesa 11.0.3 *release notes
 * that the radeon r300 *bug
 *has been fixed.
However both Debian Sid and Lubuntu 16.04 are running versions of mesa
11.0.4 and I am still seeing the issue. I have already reported this
upstream, but I am inquiring has anyone else had any success. I am
attaching my xorg log. The only thing I see that is odd is this error:

(EE) systemd-logind: failed to get session: PID 588 does not belong to any
> known session


thanks
Herminio


stretch installer broken

2015-11-11 Thread Herminio Hernandez, Jr.
I was planning on installing Stretch on my iBook G4. So I got my netinst cd
and went through the install process. Everything was fine till I got to the
section where I selected my mirrors. I chose the US/ftp.debian.org mirror
and it failed so I tried the ftp.kernel.org and that failed as well. Then I
tried the third on the list and I was able to connect and get my packages.
The install completed, however when I rebooted the bootup froze. So I
thought that it could my cd so I went and grabbed the latest stretch iso
from the site.

Yet again I ran into issues. The biggest was that I kept getting sent back
to install menu to manually select what steps I wanted to do. I found this
odd since normally the install will just walk you through. Then I ran into
the same issues with mirrors. finally the install completed and I was
rebooted. However the boot failed again, but this I got dropped into the
initramfs shell.

Has anyone else ran into this issue? Should I file this as bug with the
debain-installer package?

Herminio


Re: Unable to log in to iMac G4, graphical login workaround?

2015-10-05 Thread Herminio Hernandez Jr.
Use the Debian link in the Ubuntu forums thread then on the right side you see 
the links you need. 

Sent from my iPhone

> On Oct 5, 2015, at 12:58 PM, Roger Harkavy <rogerhark...@gmail.com> wrote:
> 
> Herminio, thank you for pointing me to this:
> 
> https://wiki.ubuntu.com/PowerPCFAQ#Nvidia_cards
> 
> I noticed this post linked from the FAQ:
> 
> http://ubuntuforums.org/showthread.php?t=2203756=12922410#post12922410
> 
> Unfortunately, I am having trouble getting the right source files and 
> compiling. I performed this command to get the source files:
> 
> wget 
> http://ftp.us.debian.org/debian/pool/non-free/x/xserver-xorg-video-nv/xserver-xorg-video-nv_2.1.20-3_kfreebsd-amd64.deb
> 
> Unfortunately, after that I cannot find a dsc file that is supposed to be 
> used in compiling the driver. I think I need more specific instructions than 
> the post provides. Can anyone please give me some additional info? Thank you.
> 
>> On Thu, Oct 1, 2015 at 1:37 AM, Herminio Hernandez Jr. 
>> <herminio.hernande...@gmail.com> wrote:
>> Another great resource is here 
>> https://wiki.ubuntu.com/PowerPCFAQ#Nvidia_cards
>> Sent from my iPhone
>> 
>>> On Sep 30, 2015, at 11:23 PM, Roger Harkavy <rogerhark...@gmail.com> wrote:
>>> 
>>> Ah, this information is helping! The following options allow me to get to 
>>> where what should be the login screen appears, but it is black with a 
>>> purple cursor:
>>> 
>>> nomodeset
>>> 
>>> or
>>> 
>>> nouveau.modeset=0 
>>> 
>>> From there I can press Ctrl-Alt-F1 and get to a command prompt.
>>> 
>>> I also tried these commands but neither of them change anything:
>>> 
>>>     nouveau.noaccel=1
>>> 
>>> or
>>> 
>>> nouveau.config=NvMSI=0
>>> 
>>> Maybe I can try them all together? I don't know. I feel like I am getting 
>>> closer, though. It is a problem with the Nouveau driver.
>>> 
>>>> On Wed, Sep 30, 2015 at 11:26 PM, Herminio Hernandez, Jr. 
>>>> <herminio.hernande...@gmail.com> wrote:
>>>> Check this post out 
>>>> http://powerpcliberation.blogspot.ca/2015/05/jessie-meets-bigmac.html
>>>> 
>>>> It is deal with G5 but I think the Nvidia issue may apply to you.
>>>> 
>>>>> On Wed, Sep 30, 2015 at 10:18 PM, <h...@shaw.ca> wrote:
>>>>> Dear Roger,
>>>>> 
>>>>> What I would try is appending "single" to the "Linux" option at the 
>>>>> second stage yaboot prompt.
>>>>> 
>>>>> Peter
>>>>> 
>>>>> 
>>>>> 
>>>>>> On 30/09/15 07:33 PM, Roger Harkavy wrote:
>>>>>> I originally posted this on the Debian user forums but I was directed to
>>>>>> this mailing list. Hopefully I can give you enough information for some
>>>>>> guidance on troubleshooting this.
>>>>>> 
>>>>>> I have an iMac G4 "desk lamp," 512k of RAM, 200 GB HD, I believe the
>>>>>> processor is a 7450. I downloaded the Debian Jessie netboot powerpc
>>>>>> "mini.iso" image from here and burned it to a CD:
>>>>>> 
>>>>>> http://http.us.debian.org/debian/dists/jessie/main/installer-powerpc/current/images/powerpc/netboot/
>>>>>> 
>>>>>> Installation seemed to go smoothly, no errors, and I selected MATE as the
>>>>>> desktop choice during install. The only other option I selected was the
>>>>>> "additional desktop software" (sorry, do not remember the exact text).
>>>>>> 
>>>>>> However, after installation, when it boots, one of the last messages you
>>>>>> see is:
>>>>>> 
>>>>>> [FAILED] Failed to start Load Kernel Modules.
>>>>>> 
>>>>>> Last line is something along the lines of:
>>>>>> 
>>>>>> fb: switching to nouveaufb from OFfb NVDA,NVMac
>>>>>> 
>>>>>> And then the text starts dissolving, and the entire screen cycles through
>>>>>> different colors. I presume it is sitting at the graphical login prompt 
>>>>>> but
>>>>>> it's not displaying correctly.
>>>>>> 
>>>>>> Based on some Google searches, it seems like I should be able to resolve
>>>>>> this by editing /etc/modules using nano from a command prompt but I can't
>>>>>> get to that point. After the machine starts cycling through the colors, I
>>>>>> press ctrl-alt-F1 through ctrl-alt-F12. If there is a command prompt 
>>>>>> being
>>>>>> offered, I can't see it.
>>>>>> 
>>>>>> I also tried different yaboot options I found in searches that were
>>>>>> supposed to avoid using the video driver. Unfortunately these didn't work
>>>>>> either, but maybe I'm not choosing the right ones.
>>>>>> 
>>>>>> How do I get the machine to boot straight to a regular text login instead
>>>>>> of the X-based one?
>>>>>> 
>>>>>> Also, this machine worked fine running Mac OS X this morning (partition 
>>>>>> was
>>>>>> deleted during the install process), so I don't think it's the hardware.
>>>>>> 
>>>>>> Please let me know what I can do. Thank you in advance for any help you 
>>>>>> can
>>>>>> provide.
> 


Re: Unable to log in to iMac G4, graphical login workaround?

2015-10-05 Thread Herminio Hernandez Jr.
You are welcome

Sent from my iPhone

> On Oct 5, 2015, at 7:26 PM, Roger Harkavy <rogerhark...@gmail.com> wrote:
> 
> I did not see that, thank you!
> 
>> On Mon, Oct 5, 2015 at 8:24 PM, Herminio Hernandez Jr. 
>> <herminio.hernande...@gmail.com> wrote:
>> Use the Debian link in the Ubuntu forums thread then on the right side you 
>> see the links you need. 
>> 
>> Sent from my iPhone
>> 
>>> On Oct 5, 2015, at 12:58 PM, Roger Harkavy <rogerhark...@gmail.com> wrote:
>>> 
>>> Herminio, thank you for pointing me to this:
>>> 
>>> https://wiki.ubuntu.com/PowerPCFAQ#Nvidia_cards
>>> 
>>> I noticed this post linked from the FAQ:
>>> 
>>> http://ubuntuforums.org/showthread.php?t=2203756=12922410#post12922410
>>> 
>>> Unfortunately, I am having trouble getting the right source files and 
>>> compiling. I performed this command to get the source files:
>>> 
>>> wget 
>>> http://ftp.us.debian.org/debian/pool/non-free/x/xserver-xorg-video-nv/xserver-xorg-video-nv_2.1.20-3_kfreebsd-amd64.deb
>>> 
>>> Unfortunately, after that I cannot find a dsc file that is supposed to be 
>>> used in compiling the driver. I think I need more specific instructions 
>>> than the post provides. Can anyone please give me some additional info? 
>>> Thank you.
>>> 
>>>> On Thu, Oct 1, 2015 at 1:37 AM, Herminio Hernandez Jr. 
>>>> <herminio.hernande...@gmail.com> wrote:
>>>> Another great resource is here 
>>>> https://wiki.ubuntu.com/PowerPCFAQ#Nvidia_cards
>>>> Sent from my iPhone
>>>> 
>>>>> On Sep 30, 2015, at 11:23 PM, Roger Harkavy <rogerhark...@gmail.com> 
>>>>> wrote:
>>>>> 
>>>>> Ah, this information is helping! The following options allow me to get to 
>>>>> where what should be the login screen appears, but it is black with a 
>>>>> purple cursor:
>>>>> 
>>>>>   nomodeset
>>>>> 
>>>>> or
>>>>> 
>>>>>   nouveau.modeset=0 
>>>>> 
>>>>> From there I can press Ctrl-Alt-F1 and get to a command prompt.
>>>>> 
>>>>> I also tried these commands but neither of them change anything:
>>>>> 
>>>>>   nouveau.noaccel=1
>>>>> 
>>>>> or
>>>>> 
>>>>>   nouveau.config=NvMSI=0
>>>>> 
>>>>> Maybe I can try them all together? I don't know. I feel like I am getting 
>>>>> closer, though. It is a problem with the Nouveau driver.
>>>>> 
>>>>>> On Wed, Sep 30, 2015 at 11:26 PM, Herminio Hernandez, Jr. 
>>>>>> <herminio.hernande...@gmail.com> wrote:
>>>>>> Check this post out 
>>>>>> http://powerpcliberation.blogspot.ca/2015/05/jessie-meets-bigmac.html
>>>>>> 
>>>>>> It is deal with G5 but I think the Nvidia issue may apply to you.
>>>>>> 
>>>>>>> On Wed, Sep 30, 2015 at 10:18 PM, <h...@shaw.ca> wrote:
>>>>>>> Dear Roger,
>>>>>>> 
>>>>>>> What I would try is appending "single" to the "Linux" option at the 
>>>>>>> second stage yaboot prompt.
>>>>>>> 
>>>>>>> Peter
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>> On 30/09/15 07:33 PM, Roger Harkavy wrote:
>>>>>>>> I originally posted this on the Debian user forums but I was directed 
>>>>>>>> to
>>>>>>>> this mailing list. Hopefully I can give you enough information for some
>>>>>>>> guidance on troubleshooting this.
>>>>>>>> 
>>>>>>>> I have an iMac G4 "desk lamp," 512k of RAM, 200 GB HD, I believe the
>>>>>>>> processor is a 7450. I downloaded the Debian Jessie netboot powerpc
>>>>>>>> "mini.iso" image from here and burned it to a CD:
>>>>>>>> 
>>>>>>>> http://http.us.debian.org/debian/dists/jessie/main/installer-powerpc/current/images/powerpc/netboot/
>>>>>>>> 
>>>>>>>> Installation seemed to go smoothly, no errors, and I selected MATE as 
>>>>>>>> the
>>>>>>>&

Re: Unable to log in to iMac G4, graphical login workaround?

2015-09-30 Thread Herminio Hernandez, Jr.
Check this post out
http://powerpcliberation.blogspot.ca/2015/05/jessie-meets-bigmac.html

It is deal with G5 but I think the Nvidia issue may apply to you.

On Wed, Sep 30, 2015 at 10:18 PM,  wrote:

> Dear Roger,
>
> What I would try is appending "single" to the "Linux" option at the second
> stage yaboot prompt.
>
> Peter
>
>
>
> On 30/09/15 07:33 PM, Roger Harkavy wrote:
>
>> I originally posted this on the Debian user forums but I was directed to
>> this mailing list. Hopefully I can give you enough information for some
>> guidance on troubleshooting this.
>>
>> I have an iMac G4 "desk lamp," 512k of RAM, 200 GB HD, I believe the
>> processor is a 7450. I downloaded the Debian Jessie netboot powerpc
>> "mini.iso" image from here and burned it to a CD:
>>
>>
>> http://http.us.debian.org/debian/dists/jessie/main/installer-powerpc/current/images/powerpc/netboot/
>>
>> Installation seemed to go smoothly, no errors, and I selected MATE as the
>> desktop choice during install. The only other option I selected was the
>> "additional desktop software" (sorry, do not remember the exact text).
>>
>> However, after installation, when it boots, one of the last messages you
>> see is:
>>
>> [FAILED] Failed to start Load Kernel Modules.
>>
>> Last line is something along the lines of:
>>
>> fb: switching to nouveaufb from OFfb NVDA,NVMac
>>
>> And then the text starts dissolving, and the entire screen cycles through
>> different colors. I presume it is sitting at the graphical login prompt
>> but
>> it's not displaying correctly.
>>
>> Based on some Google searches, it seems like I should be able to resolve
>> this by editing /etc/modules using nano from a command prompt but I can't
>> get to that point. After the machine starts cycling through the colors, I
>> press ctrl-alt-F1 through ctrl-alt-F12. If there is a command prompt being
>> offered, I can't see it.
>>
>> I also tried different yaboot options I found in searches that were
>> supposed to avoid using the video driver. Unfortunately these didn't work
>> either, but maybe I'm not choosing the right ones.
>>
>> How do I get the machine to boot straight to a regular text login instead
>> of the X-based one?
>>
>> Also, this machine worked fine running Mac OS X this morning (partition
>> was
>> deleted during the install process), so I don't think it's the hardware.
>>
>> Please let me know what I can do. Thank you in advance for any help you
>> can
>> provide.
>>
>>
>


Re: Unable to log in to iMac G4, graphical login workaround?

2015-09-30 Thread Herminio Hernandez Jr.
Another great resource is here 
https://wiki.ubuntu.com/PowerPCFAQ#Nvidia_cards
Sent from my iPhone

> On Sep 30, 2015, at 11:23 PM, Roger Harkavy <rogerhark...@gmail.com> wrote:
> 
> Ah, this information is helping! The following options allow me to get to 
> where what should be the login screen appears, but it is black with a purple 
> cursor:
> 
>   nomodeset
> 
> or
> 
>   nouveau.modeset=0 
> 
> From there I can press Ctrl-Alt-F1 and get to a command prompt.
> 
> I also tried these commands but neither of them change anything:
> 
>   nouveau.noaccel=1
> 
> or
> 
>   nouveau.config=NvMSI=0
> 
> Maybe I can try them all together? I don't know. I feel like I am getting 
> closer, though. It is a problem with the Nouveau driver.
> 
>> On Wed, Sep 30, 2015 at 11:26 PM, Herminio Hernandez, Jr. 
>> <herminio.hernande...@gmail.com> wrote:
>> Check this post out 
>> http://powerpcliberation.blogspot.ca/2015/05/jessie-meets-bigmac.html
>> 
>> It is deal with G5 but I think the Nvidia issue may apply to you.
>> 
>>> On Wed, Sep 30, 2015 at 10:18 PM,  <h...@shaw.ca> wrote:
>>> Dear Roger,
>>> 
>>> What I would try is appending "single" to the "Linux" option at the second 
>>> stage yaboot prompt.
>>> 
>>> Peter
>>> 
>>> 
>>> 
>>>> On 30/09/15 07:33 PM, Roger Harkavy wrote:
>>>> I originally posted this on the Debian user forums but I was directed to
>>>> this mailing list. Hopefully I can give you enough information for some
>>>> guidance on troubleshooting this.
>>>> 
>>>> I have an iMac G4 "desk lamp," 512k of RAM, 200 GB HD, I believe the
>>>> processor is a 7450. I downloaded the Debian Jessie netboot powerpc
>>>> "mini.iso" image from here and burned it to a CD:
>>>> 
>>>> http://http.us.debian.org/debian/dists/jessie/main/installer-powerpc/current/images/powerpc/netboot/
>>>> 
>>>> Installation seemed to go smoothly, no errors, and I selected MATE as the
>>>> desktop choice during install. The only other option I selected was the
>>>> "additional desktop software" (sorry, do not remember the exact text).
>>>> 
>>>> However, after installation, when it boots, one of the last messages you
>>>> see is:
>>>> 
>>>> [FAILED] Failed to start Load Kernel Modules.
>>>> 
>>>> Last line is something along the lines of:
>>>> 
>>>> fb: switching to nouveaufb from OFfb NVDA,NVMac
>>>> 
>>>> And then the text starts dissolving, and the entire screen cycles through
>>>> different colors. I presume it is sitting at the graphical login prompt but
>>>> it's not displaying correctly.
>>>> 
>>>> Based on some Google searches, it seems like I should be able to resolve
>>>> this by editing /etc/modules using nano from a command prompt but I can't
>>>> get to that point. After the machine starts cycling through the colors, I
>>>> press ctrl-alt-F1 through ctrl-alt-F12. If there is a command prompt being
>>>> offered, I can't see it.
>>>> 
>>>> I also tried different yaboot options I found in searches that were
>>>> supposed to avoid using the video driver. Unfortunately these didn't work
>>>> either, but maybe I'm not choosing the right ones.
>>>> 
>>>> How do I get the machine to boot straight to a regular text login instead
>>>> of the X-based one?
>>>> 
>>>> Also, this machine worked fine running Mac OS X this morning (partition was
>>>> deleted during the install process), so I don't think it's the hardware.
>>>> 
>>>> Please let me know what I can do. Thank you in advance for any help you can
>>>> provide.
> 


building chromium for powerpc

2015-09-04 Thread Herminio Hernandez Jr
I am trying to build chromium for powerpc. I installed the dependencies 
and got the source from the repos. I am getting the following error (see 
below). I am thinking that the all.gyp needs editing to allow the build 
for powerpc. Am I wrong?


|gyp: Undefined variable platform_heap_asm_files in 
/home/rican-linux/src/chromium-browser-45.0.2454.85~powerpc1/third_party/WebKit/Source/platform/blink_platform.gyp 
while loading dependencies of 
/home/rican-linux/src/chromium-browser-45.0.2454.85~powerpc1/third_party/WebKit/public/blink.gyp 
while loading dependencies of 
/home/rican-linux/src/chromium-browser-45.0.2454.85~powerpc1/ui/compositor/compositor.gyp 
while loading dependencies of 
/home/rican-linux/src/chromium-browser-45.0.2454.85~powerpc1/ui/views/views.gyp 
while loading dependencies of 
/home/rican-linux/src/chromium-browser-45.0.2454.85~powerpc1/components/components.gyp 
while loading dependencies of 
/home/rican-linux/src/chromium-browser-45.0.2454.85~powerpc1/build/all.gyp 
while trying to load 
/home/rican-linux/src/chromium-browser-45.0.2454.85~powerpc1/build/all.gyp||

||debian/rules:107: recipe for target 'override_dh_auto_configure' failed||
||make[1]: *** [override_dh_auto_configure] Error 1||
||make[1]: Leaving directory 
'/home/rican-linux/src/chromium-browser-45.0.2454.85~powerpc1'||

||debian/rules:104: recipe for target 'binary' failed||
||make: *** [binary] Error 2||
||dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit 
status 2|





Re: piglit tests

2015-08-23 Thread Herminio Hernandez Jr.
I already joined the piglit mailing list and I am going to see if there is a 
recent bug report on the r300 driver and offer my test results. Thanks!

Sent from my iPhone

 On Aug 23, 2015, at 2:08 AM, Dan DeVoto dand1...@yahoo.com wrote:
 
 You should probably go upstream.  Even if they don't fix the bug, they're 
 usually pretty good about giving workarounds, or even an unofficial patch 
 like with that Mesa default depth bug.
 
 Regards,
 
 Dan
 
 
 On Sat, 8/22/15, Herminio Hernandez, Jr. herminio.hernande...@gmail.com 
 wrote:
 
 Subject: piglit tests
 To: debian-powerpc@lists.debian.org debian-powerpc@lists.debian.org
 Date: Saturday, August 22, 2015, 2:29 PM
 
 I have downloaded the
 piglit opengl test suite and am running test on radeon
 cards. I wondering would it be profitable to open a new bug
 report on radeon r300 driver and posts my results there or
 just go directly upstream with my tests results?
 



piglit tests

2015-08-22 Thread Herminio Hernandez, Jr.
I have downloaded the piglit opengl test suite and am running test on
radeon cards. I wondering would it be profitable to open a new bug report
on radeon r300 driver and posts my results there or just go directly
upstream with my tests results?


Re: how to solve sound on powerbook g4/12''/debian jessie

2015-08-14 Thread Herminio Hernandez Jr.
Remove the /etc/modprobe.d/blacklist.local.conf file then load the 
snd-aoa-i2sbus module. Run alsamixer and the PCM channel to 75 or 80. 

Sent from my iPhone

 On Aug 14, 2015, at 11:15 AM, Mathieu Malaterre ma...@debian.org wrote:
 
 
 
 On Fri, Jul 31, 2015 at 6:08 PM, richard kuenz csae2...@uibk.ac.at wrote:
 Hello ,
 
 can someone please indicate me a solution on how to fix the sound on the 
 powerbook g4 1,5 ghz 12'' by apple. sound worked only with debian squeeze 
 here; neither with wheeezy, nor with jessie. 
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778469#24


Re: Report on Debian 8 on Late 2005 G5 with custom kernel, Graphics Issues

2015-07-10 Thread Herminio Hernandez Jr.
Awesome 

Sent from my iPhone

 On Jul 10, 2015, at 9:10 PM, Rick Thomas rbtho...@pobox.com wrote:
 
 I checked…
 Package: xserver-xorg-core
 State: installed
 Automatically installed: yes
 Version: 2:1.17.1-2
 Archive: now
 
 So I did an update  upgrade  reboot and now…
 Package: xserver-xorg-core
 State: installed
 Automatically installed: yes
 Version: 2:1.17.2-1
 Archive: now
 
 And guess what!  Desktop colors are normal again!  Whoopie!
 
 Thank you Herminio!  Thank you Peter!   (-: (-: (-:
 This list is tops!
 
 Gratefully,
 Rick
 
 On Jul 10, 2015, at 2:35 PM, Herminio Hernandez Jr. 
 herminio.hernande...@gmail.com wrote:
 
 What version of xorg-core are you running? The latest 1.17.2-1 should have 
 fixed that.
 
 
 PS:  Any idea what the problem was?  It would be great to know what got fixed.


--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/b5a542c4-133a-4f57-9b70-72c3da577...@gmail.com



Re: Report on Debian 8 on Late 2005 G5 with custom kernel, Graphics Issues

2015-07-10 Thread Herminio Hernandez Jr.
What version of xorg-core are you running? The latest 1.17.2-1 should have 
fixed that. 

Sent from my iPhone

 On Jul 10, 2015, at 4:12 PM, Rick Thomas rbtho...@pobox.com wrote:
 
 
 It’s still Sid.  I haven’t taken the time to reinstall with Jessie yet.  But 
 it’s in the works!
 
 If I generate an xorg.conf (Shut down X, run “Xorg -configure”) can you help 
 me with the changes?
 
 Thanks!
 Rick
 
 On Jul 10, 2015, at 4:12 AM, Peter Saisanas psaisa...@gmail.com wrote:
 
 Is this sid or jessie your running?
 Im running jessie and i dont have the issues your having with some of the 
 icon colours being mixed up. Sorry, im not really sure exactly why your 
 config is doing this!
 
 In saying this, I have seen this similar colour effect before and my guess 
 is you are starting to see the big endian issues with mesa / dri and colour 
 formats being incorrect, 3d hw acceleration wouldn't be able to work and 
 perhaps it is falling back on software rasterisaton for some effect of xfce 
 maybe
 
 An interesting test perhaps would be to attempt to run glxgears and see if 
 it uses software rendering and if so, do you have the same colour effects 
 you are noticing on the desktop!
 
 Perhaps in this case you could try and experiment by creating an xorg.conf 
 and disabling the glx or xrender extension. Thats what i would try maybe 
 theres some issue with some alpha transparency effect used in xfce. Just 
 guessing!
 
 Not sure if there is a deb pkg for acdcontrol.
 
 Im not too sure about the 3d side of things with linux.
 
 But im sure there are others that know more about the 3d side of things than 
 me!
 
 My quad is really in need of a rebuild as the lcs is starting to show some 
 signs of overheating and maybe leaking. No doubt from all the kernel 
 compiles i have done have given it quite a workout! 
 Cheers,
 Peter
 
 
 -- 
 To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 https://lists.debian.org/852106fb-4808-4da1-b418-359c8ca54...@pobox.com
 


--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/3b677fd8-3af6-4302-aecb-d47d22286...@gmail.com



Re: Report on Debian 8 on Late 2005 G5 with custom kernel, Graphics Issues

2015-07-08 Thread Herminio Hernandez Jr
The Invalid ROM is an error that appears once KMS is working. I shows up on 
G4 machines as well.

On Wed, 8 Jul 2015 14:42:00 -0700
Rick Thomas rbtho...@pobox.com wrote:

 Thanks Peter!
 
 I’m sure I’ve got the 3.18 kernel.  I confirmed that with “uname -a” after 
 the boot.  Your yaboot stanza looks exactly (in the relevant particulars) 
 like mine.  And, yes, I did “ybin -v” and checked to make sure the output 
 looked right.
 
 The ppdev and parport_pc anomalies have been there all along.  I don’t think 
 they have anything to do with this problem, though.
 
 The only thing I can think of that might be related (and possibly causing the 
 “Invalid ROM” message) is that the base system is Sid, not Jessie.  The 
 default kernel is 
 
  rbthomas@bigal:~$ uname -a
  Linux bigal 4.0.0-2-powerpc64 #1 SMP Debian 4.0.5-1 (2015-06-16) ppc64 
  GNU/Linux
 
 So there may be remnants of that lying around that confuse the issue when 
 running with your kernel…
 
 Didn’t you mention you had some trouble with the firmware blob in Sid?
 
 I’ll be interested to look at your dmesg and xorg logs.  I’m not getting to 
 anything involving xorg — the black screen happens before I get to the login 
 prompt.  I have /etc/X11/default-display-manager set to “/bin/false to 
 prevent X from starting up automatically.  When I want to start X, I do a 
 manual “startx” from a text console.
 
 Enjoy!
 Rick
 
 PS: I’m planning to install a plain-vanilla, fresh-out-of-the-box, Jessie 
 then add your kernel, and I’ll report back on that.
 
 Re, the FCODE ROM:  Where can I read-up (RTFM, but what FM?) on the nouveau 
 module parameters?
 
 Thanks!
 
 On Jul 8, 2015, at 1:04 PM, Peter Saisanas psaisa...@gmail.com wrote:
 
  Hi Rick,
  I should probably start a new thread for reports
  
  Seems odd to me that systemd is attempting to load modules ppdev, 
  parport_pc along with snd-powermac...
  
  Are you sure you are booting up with my actual compiled kernel and initrd?
  
  Please confirm your /etc/yaboot.conf file has entries for the image and 
  initrd, see below.
  
  image=/boot/vmlinux-3.18.16-powerpc64
  label=linux
  read-only
  initrd=/boot/initrd.img-3.18.16-powerpc64
  append=
  
  Ensure you have saved the yaboot.conf and then run ybin -v to apply the 
  changes to your boot loader.
  
  I have attached a dmesg log from my system. note my audio hardware isn't 
  working (hardware fault), so disregard the issues with snd-aoa-onyx.
  
  I have also attached my xorg log for reference.
  
  The nouveau driver attempts to scan for the nVidia DCB block (within a 
  typical VGA bios or FCODE ROM via alternate methods, it seems to perform 
  this scan automatically, but if curious, refer to the NvBios nouveau 
  module parameter.
  
  Let me know how you go.
  
  Cheers,
  Peter
  
  
  On 08/07/15 19:40, Rick Thomas wrote:
  On Jun 30, 2015, at 3:48 AM, Rick Thomas rbtho...@pobox.com
   wrote:
  
  
  I’ll definitely report on how things work on my hardware with your 
  kernel, but it will have to wait til after the weekend.  4th of July == 
  US Independence Day == lots of neighborhood/family/etc parties and 
  celebrations == no time for playing with computers.  
  
  I’m looking forward to sending a report soon!
  Rick
  
  Hi Peter,
  
  I installed your 3.18… kernel.  I get a black screen.
  
  Here’s what “journalctl -b | grep -C5 nouveau ” says.  I hope it help.  
  Note the error from nouveau about “Invalid ROM contents”.  Is that 
  expected?
  
  Thanks!
  Rick
  
  
  
  
  
  
  
  dmesg.logXorg.0.log
 
 
 -- 
 To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 https://lists.debian.org/b3819c60-bbd0-45c3-920c-5fc1e09a2...@pobox.com
 


-- 
Herminio Hernandez Jr herminio.hernande...@gmail.com


pgpMD6C8cztKR.pgp
Description: PGP signature


Xorg bug

2015-07-02 Thread Herminio Hernandez, Jr.
In Stretch and Sid the latest package of xorg-core fixed the bug that hit
PPC machines that run the latest version of X in Ubuntu and Debian. I do
not know if this has made it down stream to Ubuntu. Checking now.


Fwd: startx goes to black screen with mouse pointer

2015-06-30 Thread Herminio Hernandez Jr.
Luigi 

Take a look at this thread. This may help you. 

Sent from my iPhone

Begin forwarded message:

 Resent-From: debian-powerpc@lists.debian.org
 From: Rick Thomas rbtho...@pobox.com
 Date: June 30, 2015 at 2:55:51 PM CDT
 To: Jonni O'Gorman jonni.ogor...@gmail.com
 Cc: PowerPC List Debian debian-powerpc@lists.debian.org
 Subject: Re: startx goes to black screen with mouse pointer
 
 
 On Jun 30, 2015, at 5:24 AM, Jonni O'Gorman jonni.ogor...@gmail.com wrote:
 
 mate gives the same result - don’t have a lot of time to fiddle around with 
 it - but IO will try again at some stage and report back on any success - 
 its very interesting that yellowdoglinux 6.2 runs to graphics display no 
 problem but debian 8 doesn’t - maybe there is something to be learned form 
 ydl about how to get these old clunkers going again...
 
 Jonni,
 
 We may have a fix.  Please see the discussion in the debian-powerpc list at
https://lists.debian.org/debian-powerpc/2015/06/msg8.html
 
 Peter Saisanas has build a fixed kernel for us G5 users that he wants us to 
 try.   In that thread, he gives very complete instructions for how to install 
 it.
 
 Contact me if you have trouble.
 
 Enjoy!
 Rick
 
 -- 
 To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 https://lists.debian.org/d101b056-f584-4216-b3fb-33bc70906...@pobox.com
 


Help with Debian Site

2015-06-21 Thread Herminio Hernandez Jr
I started doing some clean up work on the Debain PPC/FAQ wiki. It is really 
outdated and needs work. If any is intrested in helping out you are more than 
welcome. Thanks!

-- 
Herminio Hernandez Jr herminio.hernande...@gmail.com


pgpd01z7Fzcem.pgp
Description: PGP signature


8.1 lightdm issues

2015-06-13 Thread Herminio Hernandez, Jr.
I just recently upgraded to 8.1 and now in order to get lxde to load I need
to drop to console and startx. Anyone else having to do the same thing?


Re: Debian 8 on Late 2005 G5, Graphics Issues

2015-06-09 Thread Herminio Hernandez Jr
Use LXDE or XFCE. They are much more lightweight and you will have a better 
experience.

On Tue, 09 Jun 2015 18:20:23 -0500
Dylan dylan.maxw...@ymail.com wrote:

 That actually worked. It's REALLY slow in software rendering though, might 
 have to install kde or something :(
 
 Thanks,
 Dylan
 
 On June 9, 2015 9:15:56 AM CDT, Brock Wittrock brockwittr...@gmail.com 
 wrote:
 On my dual core G5, I have to disable hardware acceleration when using
 the
 nouveau driver by adding this to my yaboot parameters.
 nouveau.noaccel=1
 
 If that works, you'll want to add this to your /etc/yaboot.conf file as
 the
 last line under your default kernel (probably named Linux) as well to
 make
 it permanent.
 append=nouveau.noaccel=1
 
 Save those changes, and then run sudo ybin -v to apply those changes.
 
 I'm currently trying to get 3D acceleration working again on the
 nouveau
 driver by compiling the latest drivers directly from Nouveau's git
 repository and using a later kernel. Unfortunately, I'm getting a GPU
 locked up message at boot, which causes my system to fall back to the
 fbdev
 driver, but that's an issue for another email on the Debian PowerPC
 mailing
 list and possibly a bug report to the nouveau maintainers.
 
 B-rock
 
 
 On Tue, Jun 9, 2015 at 8:40 AM, Dylan dylan.maxw...@ymail.com wrote:
 
  Computer is a Late 05 G5 Tower
  PowerPC Dual Core 2.0
  2GB Ram
  Random 160Gig HD
  Geforce 6600 Graphics
  Trying to run Debian 8 Jessie -official Powerpc
  Chose Cinnamon on Install
 
  I have installed Jessie but it boots to a scrambled black and white
 screen.
  I can get into terminal from this screen and work there just fine
 except
  for a constant isochronous cycle too long error, but I think that
 is a
  different issue.
 
  Have tried nomodeset at boot. It gets me to a black screen with a
  purplish cursor.
 
  Wheezy worked fine, no problems and worked perfect right from install
 so
  Im guessing if I could roll back to whatever Wheezy had for X/Nouveau
 (or
  whatever runs the graphics), I might be able to get this working.
 
  I'm a noob and looking for some steps to take, Id really like to get
  Jessie working if possible.
 
  Ive asked about this in a couple different places and didn't get much
 help.
 
  Here:
 
 https://www.linuxquestions.org/questions/debian-26/ppc-mac-g5-debian-8-jessie-graphics-problems-4175543659/
  And here: http://forums.debian.net/viewtopic.php?f=30t=122386
 
  Thanks,
  Dylan
 
 
  --
  To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
  with a subject of unsubscribe. Trouble? Contact
  listmas...@lists.debian.org
  Archive: https://lists.debian.org/5576eceb.4010...@ymail.com
 
 
 
 -- 
 Sent from my Android device with K-9 Mail. Please excuse my brevity.


-- 
Herminio Hernandez Jr herminio.hernande...@gmail.com


pgpBnsYH4BHcg.pgp
Description: PGP signature


Re: Debian 8 on Late 2005 G5, Graphics Issues

2015-06-09 Thread Herminio Hernandez Jr
LXDE is a great DE and also very customizable


On Tue, 09 Jun 2015 19:54:57 -0500
Dylan dylan.maxw...@ymail.com wrote:

 That's what I did. Have lxde running, seems to be doing pretty good, idling 
 ~8% and 323MB.
 
 On June 9, 2015 6:59:48 PM CDT, Herminio Hernandez Jr 
 herminio.hernande...@gmail.com wrote:
 Use LXDE or XFCE. They are much more lightweight and you will have a
 better experience.
 
 On Tue, 09 Jun 2015 18:20:23 -0500
 Dylan dylan.maxw...@ymail.com wrote:
 
  That actually worked. It's REALLY slow in software rendering though,
 might have to install kde or something :(
  
  Thanks,
  Dylan
  
  On June 9, 2015 9:15:56 AM CDT, Brock Wittrock
 brockwittr...@gmail.com wrote:
  On my dual core G5, I have to disable hardware acceleration when
 using
  the
  nouveau driver by adding this to my yaboot parameters.
  nouveau.noaccel=1
  
  If that works, you'll want to add this to your /etc/yaboot.conf file
 as
  the
  last line under your default kernel (probably named Linux) as well
 to
  make
  it permanent.
  append=nouveau.noaccel=1
  
  Save those changes, and then run sudo ybin -v to apply those
 changes.
  
  I'm currently trying to get 3D acceleration working again on the
  nouveau
  driver by compiling the latest drivers directly from Nouveau's git
  repository and using a later kernel. Unfortunately, I'm getting a
 GPU
  locked up message at boot, which causes my system to fall back to
 the
  fbdev
  driver, but that's an issue for another email on the Debian PowerPC
  mailing
  list and possibly a bug report to the nouveau maintainers.
  
  B-rock
  
  
  On Tue, Jun 9, 2015 at 8:40 AM, Dylan dylan.maxw...@ymail.com
 wrote:
  
   Computer is a Late 05 G5 Tower
   PowerPC Dual Core 2.0
   2GB Ram
   Random 160Gig HD
   Geforce 6600 Graphics
   Trying to run Debian 8 Jessie -official Powerpc
   Chose Cinnamon on Install
  
   I have installed Jessie but it boots to a scrambled black and
 white
  screen.
   I can get into terminal from this screen and work there just fine
  except
   for a constant isochronous cycle too long error, but I think
 that
  is a
   different issue.
  
   Have tried nomodeset at boot. It gets me to a black screen with
 a
   purplish cursor.
  
   Wheezy worked fine, no problems and worked perfect right from
 install
  so
   Im guessing if I could roll back to whatever Wheezy had for
 X/Nouveau
  (or
   whatever runs the graphics), I might be able to get this working.
  
   I'm a noob and looking for some steps to take, Id really like to
 get
   Jessie working if possible.
  
   Ive asked about this in a couple different places and didn't get
 much
  help.
  
   Here:
  
 
 https://www.linuxquestions.org/questions/debian-26/ppc-mac-g5-debian-8-jessie-graphics-problems-4175543659/
   And here: http://forums.debian.net/viewtopic.php?f=30t=122386
  
   Thanks,
   Dylan
  
  
   --
   To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
   with a subject of unsubscribe. Trouble? Contact
   listmas...@lists.debian.org
   Archive: https://lists.debian.org/5576eceb.4010...@ymail.com
  
  
  
  -- 
  Sent from my Android device with K-9 Mail. Please excuse my brevity.
 
 
 -- 
 Herminio Hernandez Jr herminio.hernande...@gmail.com
 
 -- 
 Sent from my Android device with K-9 Mail. Please excuse my brevity.


-- 
Herminio Hernandez Jr herminio.hernande...@gmail.com


pgpMCtc8HMVs_.pgp
Description: PGP signature


Re: Debian 8.0 PPC not working on Pegasos II G4 (working now!)

2015-06-06 Thread Herminio Hernandez Jr
awesome!

On Sat, 6 Jun 2015 21:17:39 +0200
aPEX a...@gmx.ch wrote:

 Hello all,
 
 just want to say that installing without network was the solution! :-) It 
 seems that a security update break the
 automatic installation. Now also the right bootimage vmlinuz is generated. 
 Next to this I installed the MATE
 desktop. This mean the 3.x kernel is still running fine on the Peg. :-)
 
 Attached the logfiles of my installation:
 
 


-- 
Herminio Hernandez Jr herminio.hernande...@gmail.com


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150606153356.bf2f855e0c250cfd4fd32...@gmail.com



Re: yaboot: How to load Debian8 netboot installation images directly from the boot: prompt?

2015-05-26 Thread Herminio Hernandez Jr.
Here is how you boot with usb. 

https://wiki.ubuntu.com/PowerPCFAQ#How_do_I_boot_from_a_USB_drive.3F

Sent from my iPhone

 On May 26, 2015, at 2:37 AM, Clark Wang dearv...@gmail.com wrote:
 
 On Tue, May 26, 2015 at 3:05 PM, yu kkn...@gmail.com wrote:
 As I know, yaboot can't set vmlinux and initrd at the same time in its
 prompt, the right way is to load an alternative config file, such as
 conf file=/boot/deb/yaboot.conf, but in this yaboot.conf, both
 vmlinux and initrd.gz are under /, the path is incorrect.
 
 so I guess you can write a new yaboot.conf in a USB flash drive, like:
 
 boot=/dev/sdaX(the prep partition)
 partition=3
 root=/dev/sda3
 timeout=30
 
 image=/boot/vmlinux (can use the jessie kernel image directly, not
 netboot image)
  label=Linux
  initrd=/boot/initrd.img
 
 
 and then try to load the conf  file in yaboot prompt by
 
 conf [device=device] [partition=partno] [file=/path/to/configfile]
 
 p.s.  I'm not sure whether yaboot can load a conf in usb device or not
  under iBook :(
 
 Thanks for the info. I may give it a try.
 
 -clark 
 
 2015-05-26 14:17 GMT+08:00 clarkw clark.w...@oracle.com:
  On Tue, May 26, 2015 at 2:09 PM, Petter Adsen pet...@synth.no wrote:
 
  On Tue, 26 May 2015 13:16:04 +0800
  Clark Wang dearv...@gmail.com wrote:
 
   On Tue, May 26, 2015 at 1:10 PM, Herminio Hernandez Jr 
   herminio.hernande...@gmail.com wrote:
  
On Tue, 2015-05-26 at 10:22 +0800, Clark Wang wrote:
 I have an `iBook G4` and have `Debian 8 (Jessie)` installed on it.
 Yesterday I did something stupid (messed up `yaboot.conf` and ran
 `ybin`) and now the system cannot boot up.

 The old Debian 8 was installed on a single partition (`/dev/sda3`,
 `ext4`). I ever put the Debian 8 netboot installation images
 (downloaded from here) under `/boot/deb/`:

 /boot/deb/initrd.gz
 /boot/deb/vmlinux
 /boot/deb/yaboot
 /boot/deb/yaboot.conf

 So how can I boot the netboot installation images from the `boot:`
 prompt and reinstall Debian 8?

 I tried `boot: hd:3,/boot/deb/vmlinux root=/dev/ram read-only
 initrd=/boot/deb/initrd.gz initrd-size=300` but it did not
 work. (The screenshot taken with my phone.)


 Thanks.



 -clark

You can use the netinst cd as a recovery cd by doing the following.
   
  
   I forgot to mention that my iBook's CD drive is broken. :)
  
   
1. boot into the cd and at boot type recovery
   
  
   Or can I boot the netboot installation images (under /boot/deb/) from
   the Open Firmware prompt?
 
  Can the machine boot from a USB flash drive? Or over the network? One
  of these approaches might be easier for you.
 
 
  I'm trying to find out how to boot form USB. Boot from network also sounds
  good. I'll investigate how to setup a DHCP and TFTP server on my OS X
  (Yosemite) and how to boot iBook from network.
 
 
  Other than that, I'm afraid I can't help you - I know nothing about
  yaboot.
 
 
  I never know about yaboot and Open Firmware when I was using Mac OS X on 
  the
  iBook. They're all mysterious to me. Still learning. :)
 
  Thanks.
 
  -clark
 
 
  Petter
 
  --
  I'm ionized
  Are you sure?
  I'm positive.
 
 
 


Re: [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM

2015-05-26 Thread Herminio Hernandez Jr.
What are your yaboot boot parameters? It looks like you have KMS enabled. That 
is the first step. Also what is your video card?

Sent from my iPhone

 On May 26, 2015, at 6:17 AM, Mathieu Malaterre ma...@debian.org wrote:
 
 Hi there,
 
 I cannot remember if this ever work on Mac Mini G4. Is it possible to
 have hardware acceleration on those machines ?
 
 Here is what I see (ssh connection):
 
 $ xvfb-run -s -screen 0 640x480x24 glxinfo  /tmp/out
 $ cat /tmp/out
 libGL: screen 0 does not appear to be DRI3 capable
 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so
 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so
 libGL: Can't open configuration file /home/mathieu/.drirc: No such
 file or directory.
 name of display: :99
 display: :99  screen: 0
 direct rendering: Yes
 [...]
 OpenGL vendor string: Mesa Project
 OpenGL renderer string: Software Rasterizer
 OpenGL version string: 2.1 Mesa 10.3.2
 OpenGL shading language version string: 1.20
 [...]
 
 With:
 
 $ apt-cache policy libgl1-mesa-dri libdrm-radeon1 firmware-linux-nonfree
 libgl1-mesa-dri:
  Installed: 10.3.2-1
  Candidate: 10.3.2-1
  Version table:
 *** 10.3.2-1 0
500 http://ftp.fr.debian.org/debian/ jessie/main powerpc Packages
100 /var/lib/dpkg/status
 libdrm-radeon1:
  Installed: 2.4.58-2
  Candidate: 2.4.58-2
  Version table:
 *** 2.4.58-2 0
500 http://ftp.fr.debian.org/debian/ jessie/main powerpc Packages
100 /var/lib/dpkg/status
 firmware-linux-nonfree:
  Installed: 0.43
  Candidate: 0.43
  Version table:
 *** 0.43 0
500 http://ftp.fr.debian.org/debian/ jessie/non-free powerpc Packages
100 /var/lib/dpkg/status
 
 Some info from `dmesg`:
 
 $ dmesg | grep drm
 [   12.340684] [drm] Initialized drm 1.1.0 20060810
 [   13.466376] [drm] radeon kernel modesetting enabled.
 [   13.470558] fb: switching to radeondrmfb from OFfb ATY,RockHo
 [   13.480404] [drm] initializing kernel modesetting (RV280
 0x1002:0x5962 0x1002:0x5962).
 [   13.480442] [drm] register mmio base: 0x9000
 [   13.480451] [drm] register mmio size: 65536
 [   13.480579] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
 [   13.480602] [drm] Using device-tree clock info
 [   13.480721] [drm] Generation 2 PCI interface, using max accessible memory
 [   13.480782] [drm] Detected VRAM RAM=128M, BAR=128M
 [   13.480792] [drm] RAM width 64bits DDR
 [   13.481041] [drm] radeon: 32M of VRAM memory ready
 [   13.481052] [drm] radeon: 256M of GTT memory ready.
 [   13.481684] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [   13.481694] [drm] Driver supports precise vblank timestamp query.
 [   13.481734] [drm] radeon: irq initialized.
 [   13.481773] [drm] Loading R200 Microcode
 [   13.838673] [drm] radeon: ring at 0x1000
 [   13.838713] [drm] ring test succeeded in 0 usecs
 [   13.839477] [drm] ib test succeeded in 0 usecs
 [   13.841646] [drm] Connector Table: 7 (mini internal tmds)
 [   13.841681] [drm] No TMDS info found in BIOS
 [   13.841695] [drm] No TV DAC info found in BIOS
 [   13.842693] [drm] Radeon Display Connectors
 [   13.842711] [drm] Connector 0:
 [   13.842719] [drm]   DVI-I-1
 [   13.842727] [drm]   HPD1
 [   13.842737] [drm]   DDC: 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c
 [   13.842746] [drm]   Encoders:
 [   13.842755] [drm] DFP1: INTERNAL_TMDS1
 [   13.842764] [drm] CRT2: INTERNAL_DAC2
 [   13.842772] [drm] Connector 1:
 [   13.842779] [drm]   SVIDEO-1
 [   13.842786] [drm]   Encoders:
 [   13.842794] [drm] TV1: INTERNAL_DAC2
 [   13.863556] [drm] fb mappable at 0x9804
 [   13.863572] [drm] vram apper at 0x9800
 [   13.863581] [drm] size 786432
 [   13.863588] [drm] fb depth is 8
 [   13.863596] [drm]pitch is 1024
 [   13.922887] radeon :00:10.0: fb0: radeondrmfb frame buffer device
 [   13.923538] [drm] Initialized radeon 2.39.0 20080528 for
 :00:10.0 on minor 0
 
 
 -- 
 To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 https://lists.debian.org/CA+7wUswkgxyx=icxw5kevuxfdz46c8uzq3w09nl89v1ruas...@mail.gmail.com
 


--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/6299fdb8-4081-446f-b290-910308856...@gmail.com



Re: [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM

2015-05-26 Thread Herminio Hernandez, Jr.
hmm are you adding anything to yaboot on boot like this

Linux radeon.modeset=1 video=offb:off video=radeonfb:off radeon.agpmode=-1

On Tue, May 26, 2015 at 11:56 AM, Mathieu Malaterre ma...@debian.org
wrote:

 $ lspci -s :00:10.0 -vv
 :00:10.0 VGA compatible controller: Advanced Micro Devices [AMD]
 nee ATI RV280 [Radeon 9200] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices [AMD] nee ATI RV280 [Radeon 9200]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
 Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort-
 TAbort- MAbort- SERR- PERR- INTx-
 Latency: 255 (2000ns min), Cache Line Size: 32 bytes
 Interrupt: pin A routed to IRQ 48
 Region 0: Memory at 9800 (32-bit, prefetchable) [size=128M]
 Region 1: I/O ports at 0400 [size=256]
 Region 2: Memory at 9000 (32-bit, non-prefetchable) [size=64K]
 Expansion ROM at 9002 [size=128K]
 Capabilities: access denied
 Kernel driver in use: radeonfb


 On Tue, May 26, 2015 at 6:34 PM, Herminio Hernandez Jr.
 herminio.hernande...@gmail.com wrote:
  What is your video card?
 
  Sent from my iPhone
 
  On May 26, 2015, at 10:28 AM, Mathieu Malaterre ma...@debian.org
 wrote:
 
  From the log, this look like this is the case:  [drm] radeon kernel
  modesetting enabled.
 
  Here you go anyway:
 
  $ cat /etc/yaboot.conf
  ## yaboot.conf generated by debian-installer
  ##
  ## run: man yaboot.conf for details. Do not make changes until you
 have!!
  ## see also: /usr/share/doc/yaboot/examples for example configurations.
  ##
  ## For a dual-boot menu, add one or more of:
  ## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ
 
  boot=/dev/disk/by-id/scsi-SATA_SAMSUNG_HM160HCS12TJ1LB742280-part2
  device=/pci@f400/ata-6@d/@0
  partition=3
  root=UUID=7ad09054-310d-44e6-959a-b8c2ab7f9edd
  timeout=50
  install=/usr/lib/yaboot/yaboot
  magicboot=/usr/lib/yaboot/ofboot
  enablecdboot
 
  image=/boot/vmlinux
 label=Linux
 read-only
 initrd=/boot/initrd.img
 
  image=/boot/vmlinux.old
 label=old
 read-only
 initrd=/boot/initrd.img.old
 
 
  On Tue, May 26, 2015 at 3:18 PM, Herminio Hernandez Jr.
  herminio.hernande...@gmail.com wrote:
  What are your yaboot boot parameters? It looks like you have KMS
 enabled. That is the first step. Also what is your video card?
 
  Sent from my iPhone
 
  On May 26, 2015, at 6:17 AM, Mathieu Malaterre ma...@debian.org
 wrote:
 
  Hi there,
 
  I cannot remember if this ever work on Mac Mini G4. Is it possible to
  have hardware acceleration on those machines ?
 
  Here is what I see (ssh connection):
 
  $ xvfb-run -s -screen 0 640x480x24 glxinfo  /tmp/out
  $ cat /tmp/out
  libGL: screen 0 does not appear to be DRI3 capable
  libGL: OpenDriver: trying
 /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so
  libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so
  libGL: Can't open configuration file /home/mathieu/.drirc: No such
  file or directory.
  name of display: :99
  display: :99  screen: 0
  direct rendering: Yes
  [...]
  OpenGL vendor string: Mesa Project
  OpenGL renderer string: Software Rasterizer
  OpenGL version string: 2.1 Mesa 10.3.2
  OpenGL shading language version string: 1.20
  [...]
 
  With:
 
  $ apt-cache policy libgl1-mesa-dri libdrm-radeon1
 firmware-linux-nonfree
  libgl1-mesa-dri:
  Installed: 10.3.2-1
  Candidate: 10.3.2-1
  Version table:
  *** 10.3.2-1 0
500 http://ftp.fr.debian.org/debian/ jessie/main powerpc
 Packages
100 /var/lib/dpkg/status
  libdrm-radeon1:
  Installed: 2.4.58-2
  Candidate: 2.4.58-2
  Version table:
  *** 2.4.58-2 0
500 http://ftp.fr.debian.org/debian/ jessie/main powerpc
 Packages
100 /var/lib/dpkg/status
  firmware-linux-nonfree:
  Installed: 0.43
  Candidate: 0.43
  Version table:
  *** 0.43 0
500 http://ftp.fr.debian.org/debian/ jessie/non-free powerpc
 Packages
100 /var/lib/dpkg/status
 
  Some info from `dmesg`:
 
  $ dmesg | grep drm
  [   12.340684] [drm] Initialized drm 1.1.0 20060810
  [   13.466376] [drm] radeon kernel modesetting enabled.
  [   13.470558] fb: switching to radeondrmfb from OFfb ATY,RockHo
  [   13.480404] [drm] initializing kernel modesetting (RV280
  0x1002:0x5962 0x1002:0x5962).
  [   13.480442] [drm] register mmio base: 0x9000
  [   13.480451] [drm] register mmio size: 65536
  [   13.480579] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS
 ROM
  [   13.480602] [drm] Using device-tree clock info
  [   13.480721] [drm] Generation 2 PCI interface, using max accessible
 memory
  [   13.480782] [drm] Detected VRAM RAM=128M, BAR=128M
  [   13.480792] [drm] RAM width 64bits DDR
  [   13.481041] [drm] radeon: 32M of VRAM memory ready
  [   13.481052] [drm] radeon: 256M of GTT memory ready.
  [   13.481684] [drm] Supports vblank timestamp caching Rev 2
 (21.10.2013).
  [   13.481694] [drm] Driver supports precise vblank timestamp query

Re: [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM

2015-05-26 Thread Herminio Hernandez Jr.
What is your video card?

Sent from my iPhone

 On May 26, 2015, at 10:28 AM, Mathieu Malaterre ma...@debian.org wrote:
 
 From the log, this look like this is the case:  [drm] radeon kernel
 modesetting enabled.
 
 Here you go anyway:
 
 $ cat /etc/yaboot.conf
 ## yaboot.conf generated by debian-installer
 ##
 ## run: man yaboot.conf for details. Do not make changes until you have!!
 ## see also: /usr/share/doc/yaboot/examples for example configurations.
 ##
 ## For a dual-boot menu, add one or more of:
 ## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ
 
 boot=/dev/disk/by-id/scsi-SATA_SAMSUNG_HM160HCS12TJ1LB742280-part2
 device=/pci@f400/ata-6@d/@0
 partition=3
 root=UUID=7ad09054-310d-44e6-959a-b8c2ab7f9edd
 timeout=50
 install=/usr/lib/yaboot/yaboot
 magicboot=/usr/lib/yaboot/ofboot
 enablecdboot
 
 image=/boot/vmlinux
label=Linux
read-only
initrd=/boot/initrd.img
 
 image=/boot/vmlinux.old
label=old
read-only
initrd=/boot/initrd.img.old
 
 
 On Tue, May 26, 2015 at 3:18 PM, Herminio Hernandez Jr.
 herminio.hernande...@gmail.com wrote:
 What are your yaboot boot parameters? It looks like you have KMS enabled. 
 That is the first step. Also what is your video card?
 
 Sent from my iPhone
 
 On May 26, 2015, at 6:17 AM, Mathieu Malaterre ma...@debian.org wrote:
 
 Hi there,
 
 I cannot remember if this ever work on Mac Mini G4. Is it possible to
 have hardware acceleration on those machines ?
 
 Here is what I see (ssh connection):
 
 $ xvfb-run -s -screen 0 640x480x24 glxinfo  /tmp/out
 $ cat /tmp/out
 libGL: screen 0 does not appear to be DRI3 capable
 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so
 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so
 libGL: Can't open configuration file /home/mathieu/.drirc: No such
 file or directory.
 name of display: :99
 display: :99  screen: 0
 direct rendering: Yes
 [...]
 OpenGL vendor string: Mesa Project
 OpenGL renderer string: Software Rasterizer
 OpenGL version string: 2.1 Mesa 10.3.2
 OpenGL shading language version string: 1.20
 [...]
 
 With:
 
 $ apt-cache policy libgl1-mesa-dri libdrm-radeon1 firmware-linux-nonfree
 libgl1-mesa-dri:
 Installed: 10.3.2-1
 Candidate: 10.3.2-1
 Version table:
 *** 10.3.2-1 0
   500 http://ftp.fr.debian.org/debian/ jessie/main powerpc Packages
   100 /var/lib/dpkg/status
 libdrm-radeon1:
 Installed: 2.4.58-2
 Candidate: 2.4.58-2
 Version table:
 *** 2.4.58-2 0
   500 http://ftp.fr.debian.org/debian/ jessie/main powerpc Packages
   100 /var/lib/dpkg/status
 firmware-linux-nonfree:
 Installed: 0.43
 Candidate: 0.43
 Version table:
 *** 0.43 0
   500 http://ftp.fr.debian.org/debian/ jessie/non-free powerpc Packages
   100 /var/lib/dpkg/status
 
 Some info from `dmesg`:
 
 $ dmesg | grep drm
 [   12.340684] [drm] Initialized drm 1.1.0 20060810
 [   13.466376] [drm] radeon kernel modesetting enabled.
 [   13.470558] fb: switching to radeondrmfb from OFfb ATY,RockHo
 [   13.480404] [drm] initializing kernel modesetting (RV280
 0x1002:0x5962 0x1002:0x5962).
 [   13.480442] [drm] register mmio base: 0x9000
 [   13.480451] [drm] register mmio size: 65536
 [   13.480579] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
 [   13.480602] [drm] Using device-tree clock info
 [   13.480721] [drm] Generation 2 PCI interface, using max accessible memory
 [   13.480782] [drm] Detected VRAM RAM=128M, BAR=128M
 [   13.480792] [drm] RAM width 64bits DDR
 [   13.481041] [drm] radeon: 32M of VRAM memory ready
 [   13.481052] [drm] radeon: 256M of GTT memory ready.
 [   13.481684] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [   13.481694] [drm] Driver supports precise vblank timestamp query.
 [   13.481734] [drm] radeon: irq initialized.
 [   13.481773] [drm] Loading R200 Microcode
 [   13.838673] [drm] radeon: ring at 0x1000
 [   13.838713] [drm] ring test succeeded in 0 usecs
 [   13.839477] [drm] ib test succeeded in 0 usecs
 [   13.841646] [drm] Connector Table: 7 (mini internal tmds)
 [   13.841681] [drm] No TMDS info found in BIOS
 [   13.841695] [drm] No TV DAC info found in BIOS
 [   13.842693] [drm] Radeon Display Connectors
 [   13.842711] [drm] Connector 0:
 [   13.842719] [drm]   DVI-I-1
 [   13.842727] [drm]   HPD1
 [   13.842737] [drm]   DDC: 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c
 [   13.842746] [drm]   Encoders:
 [   13.842755] [drm] DFP1: INTERNAL_TMDS1
 [   13.842764] [drm] CRT2: INTERNAL_DAC2
 [   13.842772] [drm] Connector 1:
 [   13.842779] [drm]   SVIDEO-1
 [   13.842786] [drm]   Encoders:
 [   13.842794] [drm] TV1: INTERNAL_DAC2
 [   13.863556] [drm] fb mappable at 0x9804
 [   13.863572] [drm] vram apper at 0x9800
 [   13.863581] [drm] size 786432
 [   13.863588] [drm] fb depth is 8
 [   13.863596] [drm]pitch is 1024
 [   13.922887] radeon :00:10.0: fb0: radeondrmfb frame buffer device
 [   13.923538] [drm] Initialized radeon

Re: yaboot: How to load Debian8 netboot installation images directly from the boot: prompt?

2015-05-25 Thread Herminio Hernandez Jr
On Tue, 2015-05-26 at 10:22 +0800, Clark Wang wrote:
 I have an `iBook G4` and have `Debian 8 (Jessie)` installed on it.
 Yesterday I did something stupid (messed up `yaboot.conf` and ran
 `ybin`) and now the system cannot boot up.
 
 The old Debian 8 was installed on a single partition (`/dev/sda3`,
 `ext4`). I ever put the Debian 8 netboot installation images
 (downloaded from here) under `/boot/deb/`:
 
 /boot/deb/initrd.gz
 /boot/deb/vmlinux
 /boot/deb/yaboot
 /boot/deb/yaboot.conf
 
 So how can I boot the netboot installation images from the `boot:`
 prompt and reinstall Debian 8?
 
 I tried `boot: hd:3,/boot/deb/vmlinux root=/dev/ram read-only
 initrd=/boot/deb/initrd.gz initrd-size=300` but it did not work.
 (The screenshot taken with my phone.)
 
 
 Thanks.
 
 
 
 -clark
 
You can use the netinst cd as a recovery cd by doing the following.

1. boot into the cd and at boot type recovery
2. the cd will go through the initial install process, when you get to
the part that it is setting up dhcp there should be either a 'cancell'
or 'go back' option on the bottom left. Select it
3. it should take you to a list of options one of which is recovery
mode. select that and from there you should be able to get to a bash
prompt and fix yaboot.


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1432617003.16711.3.ca...@gmail.com



radeon 9000 PowerMac G4

2015-05-20 Thread Herminio Hernandez Jr
On a Powermac G4 when I use these parameters
radeon.agpmode=-1
radeon.modeset=1 radeon.agpmode=-1
radeon.modeset=1 video=offb:off radeon.agpmode=-1

KMS does not load fbdev does and my colors are all off. However if I do
this

radeon.modeset=1 video=offb:off video=radeonfb:off radeon.agpmode=-1

then I get the right colors but the screen freezes. I am betting it is
due to the really old card I have. I am planning replacing it with a
better one, but I was wonder has anyone found a work around. Thanks!


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1432102289.15896.3.ca...@gmail.com



Re: radeon 9000 PowerMac G4

2015-05-20 Thread Herminio Hernandez Jr.
I have had KMS working on my PowerBook and iBook G4 machines. This is the first 
time those kernel boot options have not worked. 

Sent from my iPhone

 On May 20, 2015, at 2:55 AM, Rick Thomas rbtho...@pobox.com wrote:
 
 Hi Herminio,
 
 I gather you’re hoping for video acceleration via KMS?
 
 If not, you can use boot parameters
nomodeset vga=0x31B
 
 This gives un-accelerated graphics, but at least it doesn’t freeze (on my 
 machine) or give scrambled colors.  The default jessie amd64 install either 
 gives scrambled colors or freezes randomly.  The vga=0x31b parameter sets the 
 video resolution, in this case it’s 1280x1024, 24-bits.
 
 See
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers
 for a chart of resolution options that may be used.
 
 The web page also suggests the “hwinfo —framebuffer” command.  You’ll need to 
 install the “hwinfo” package — it’s available in Debian, but it seems to only 
 work on x86/amd64 hardware.   I tried it on a powerpc64 machine and it gave 
 me lots of error messages and no useful output.
 
 For powerpc hardware, there’s the “fbset” command (also available as a 
 separate package in Debian).
 
 I’ve seen hints that the “vga=“ boot-option may not be supported on 
 non-x86/amd64 hardware, but it’s certainly worth a try!  And I can vouch from 
 personal experience that the “nomodeset” option is supported, and works, on 
 powerpc/powerc64.
 
 My graphics card (on the amd64 machine) is
09:02.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] 
 (rev a1)
 
 On the powerpc64 machine, it’s
:0b:00.0 VGA compatible controller: NVIDIA Corporation NV43 [GeForce 
 6600 LE] (rev a2)
 
 Hope that helps!
 Enjoy!
 Rick
 
 On May 19, 2015, at 11:11 PM, Herminio Hernandez Jr 
 herminio.hernande...@gmail.com wrote:
 
 On a Powermac G4 when I use these parameters
 radeon.agpmode=-1
 radeon.modeset=1 radeon.agpmode=-1
 radeon.modeset=1 video=offb:off radeon.agpmode=-1
 
 KMS does not load fbdev does and my colors are all off. However if I do
 this
 
 radeon.modeset=1 video=offb:off video=radeonfb:off radeon.agpmode=-1
 
 then I get the right colors but the screen freezes. I am betting it is
 due to the really old card I have. I am planning replacing it with a
 better one, but I was wonder has anyone found a work around. Thanks!
 
 
 -- 
 To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: https://lists.debian.org/1432102289.15896.3.ca...@gmail.com
 


--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/73a6885b-12a7-4ca6-b3e0-e82c81572...@gmail.com



Re: radeon 9000 PowerMac G4

2015-05-20 Thread Herminio Hernandez, Jr.
I have heard about G5 issues in Jessie. I baffles me b/c I running
testing/stretch on my iBook G4 with accelerated graphics!

On Wed, May 20, 2015 at 2:17 PM, Rick Thomas rbtho...@pobox.com wrote:


 On May 20, 2015, at 7:25 AM, Herminio Hernandez Jr. 
 herminio.hernande...@gmail.com wrote:

  I have had KMS working on my PowerBook and iBook G4 machines. This is
 the first time those kernel boot options have not worked.
 
  Sent from my iPhone

 My PowerMac G5 worked fine with Wheezy.  It’s just when I tried loading
 Jessie on it that I started to have problems.  The only thing that worked
 was the “nomodeset” option.

 I’m afraid we have to face facts.  The old Mac powerpc machines we love
 just aren’t common enough or sexy enough to attract the developer attention
 needed to keep bugs from creeping in.  Sooner or later, one of those bugs
 will be fatal and powerpc will go the way of ia64 (“itanium”)…   /-:

 Rick




Re: Jessie on iMac G5 : advise needed about GPU setup

2015-05-17 Thread Herminio Hernandez Jr.
What video card are you using?

Sent from my iPhone

 On May 17, 2015, at 5:31 AM, Christophe De Natale 
 christophedenat...@orange.fr wrote:
 
 Hi friend,
 
 Yes I’ve it running on fresh install without any modif (however my integrated 
 ati X600 needs to load non-free firmware and then breaks OpenGL engine) but 
 regarding your hardware it’s probably due to your gpu adding card (?)
 Did you check Jessie HCL ?
 Note : I’ve choose Mate desktop environnement (gnome3=not working, kde=not 
 trying, xfce=ok but not satisfied)
 
 Regards,
 
 Christophe De Natale
 
 
 
 Le 17 mai 2015 à 12:17, luigi burdo intermedi...@hotmail.com a écrit :
 
 you have xorg running on imac g5???
 interesting on my quad i have xorg crash with core dump on jessie, same is 
 with lubuntu, mate 15.x everything was working right on wheezy, and 
 lubuntu, mate 14.x
 
 Inviato da iPad
 
 Il giorno 17/mag/2015, alle ore 00:10, Christophe De Natale 
 christophedenat...@orange.fr ha scritto:
 
 Hello everybody,
 
 I manage to post a step-by-step on Debian-wiki regarding install jessie on 
 iMac G5 17  20 inches rev C but I need to achieve gpu setup.
 Two machines are installed, it seems to work well but I’ve some doubts 
 about ATI X600 adjustements and then I need to validate that all is right.
 Sure, I read many topics, wikis, then mesa-utils tests were performed but 
 my knowledge stops here and all these mechanisms about gpu are
 complicated to understand for me.
 
 I wrote three documents which contains glxinfo :
 * at the fresh install (without non-free firmware + radeon driver)
 * after install non-free (it breaks glxgears functionality)
 * after downgrading mesa-lib in the previous version (to recover glxgears)
 * according with the wiki, no try to use fglrx
 
 So, I’ll be very grateful if somebody could to be a guide for me (all I 
 need is to know how to choose a correct setup), I can send more 
 informations about that.
 And sorry for my bad english :-)
 
 Cheers from France,
 
 Christophe De Natale
 
 
 
 
 -- 
 To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact 
 listmas...@lists.debian.org
 Archive: 
 https://lists.debian.org/efbf153c-623f-407e-9be3-592ea94ac...@orange.fr
 
 
 -- 
 To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 https://lists.debian.org/f1523206-6321-4cac-8667-0eee7d1da...@orange.fr
 


--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/eeaada69-4e65-41ac-9837-754ebc882...@gmail.com



LXQT

2015-05-08 Thread Herminio Hernandez, Jr.
I just watch an Lubuntu talk on LXQT development and was wonder when would
we see this in Debian? Can anyone tell me if it is Sid or experimental for
PowerPC? Would someone need to install from source? Any help would be great!

Thanks
Herminio


Re: LXQT

2015-05-08 Thread Herminio Hernandez, Jr.
Thanks for the response! It looks it may be a while before we see it in
Debian.

On Fri, May 8, 2015 at 12:30 PM, Breno Leitao bren...@br.ibm.com wrote:

 Hi Herminio,

 On 05/08/2015 01:18 PM, Herminio Hernandez, Jr. wrote:
  I just watch an Lubuntu talk on LXQT development and was wonder when
 would we see
  this in Debian? Can anyone tell me if it is Sid or experimental for
 PowerPC? Would
  someone need to install from source? Any help would be great!
 I understand that lxqt is still not in Debian.

 There are severeal ITP to add lxqt into Debian, that are not fully
 accepted.

 * [ITP: liblxqt -- Core utility library for all LXDE-Qt
 components](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747620)

 * [ITP: liblxqt-mount -- Library used to manage removable devices for
 LXDE-Qt](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747596)

 * [ITP: lxqt-config -- LXQt system settings
 center](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747597)

 * [ITP: lxqt-config-randr -- Qt config GUI for X11 RandR for LXQt system
 settings](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747598)

 * [ITP: lxqt-common -- Common files for
 LXQt](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747599)

 * [The standalone LXQt About
 dialog](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747600)

 * [ITP: lxqt-globalkeys -- Daemon used to register global keyboard
 shortcuts](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747601)

 * [ITP: lxqt-notificationd -- The LXQt notification
 daemon](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747602)

 * [ITP: lxqt-openssh-askpass -- OpenSSH user/password GUI dialog for
 LXQt](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747603)

 * [ITP: lxqt-qtplugin -- LXDE-Qt platform integration plugin for
 Qt](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747604)

 * [ITP: pcmanfm-qt -- File manager and desktop icon manager (Qt port of
 PCManFM
 and libfm)](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747605)

 * [ITP: lxqt-policykit -- The LXQt PolicyKit
 agent](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747607)

 * [ITP: lxqt-session -- An alternative session manager ported from the
 original
 razor-session](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747608)

 * [ITP: lxqt-panel -- The LXQt desktop
 panel](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747610)

 * [ITP: lxqt-powermanagement -- Power management module for
 LXQt](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747611)

 * [ITP: lxqt-runner -- Tool used to launch programs quickly by typing their
 names](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747613)


 --
 To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: https://lists.debian.org/554cf2c8.2030...@br.ibm.com




Re: Debian 7.8 PPC not working on Pegasos II G4

2015-04-30 Thread Herminio Hernandez Jr.
What is the video card you are using?

Sent from my iPhone

 On Apr 30, 2015, at 12:07 PM, aPEX a...@gmx.ch wrote:
 
 Hello,
 
 no one who can help? Debian 6.8 was still running fine…
 I think if I will try Debian 8 I will have same problem like with 7.8?
 
 Best regards, aPEX
 
 
 
 Am 27.04.2015 um 20:27 schrieb aPEX a...@gmx.ch:
 
 Hello all,
 
 I was using a long time Debian 6.x on my Pegasos II G4 with 1Ghz CPU und 2GB 
 Memory.
 Last week I got the stupid idea to install everything new using latest 
 Debian 7.8, because
 on the DVD there is still the install script for the Pegasos. :-)
 
 Installation itself is working fine till 95% and then abort there, some like 
 after-installation trigger.
 We tested it on several Pegasos II that we have, always the same. I can go 
 on without installing
 more software, but I assume that also some basic stuff is missing.
 
 Also the 3.x kernel is no more working on the Pegasos II, you will get 
 screen with grafic trash
 right after starting the kernel.
 
 IMG_9965.JPG
 
 Any idea? I tried it in the IRC, but got no answer. 
 
 It would be really fantastic if this problem could be fixed and the Pegasos 
 II will work again. 
 
 
 Best regards, Robert aka aPEX
 
 
 
 PS: I am just a user, no Linux guru, sorry for this…
 
 
 -- 
 To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: https://lists.debian.org/a1381917-b685-409d-8700-e25f3186f...@gmx.ch
 


--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/806dd26d-3f78-411c-9a64-22d775eb5...@gmail.com



Re: Debian 7.8 PPC not working on Pegasos II G4

2015-04-30 Thread Herminio Hernandez Jr.
If you are yaboot try this

Linux radeon.modeset=1 video=offb:off video=radeonfb:off 

If that does not help then add this as well radeon.agpmode=-1

Sent from my iPhone

 On Apr 30, 2015, at 1:46 PM, aPEX a...@gmx.ch wrote:
 
 Hello,
 
 it is a RADEON 9000 Pro with 128MB Memory.
 
 Best regards, aPEX
 
 
 
 Am 30.04.2015 um 19:38 schrieb Herminio Hernandez Jr. 
 herminio.hernande...@gmail.com:
 
 What is the video card you are using?
 
 Sent from my iPhone
 
 On Apr 30, 2015, at 12:07 PM, aPEX a...@gmx.ch wrote:
 
 Hello,
 
 no one who can help? Debian 6.8 was still running fine…
 I think if I will try Debian 8 I will have same problem like with 7.8?
 
 Best regards, aPEX
 
 
 
 Am 27.04.2015 um 20:27 schrieb aPEX a...@gmx.ch:
 
 Hello all,
 
 I was using a long time Debian 6.x on my Pegasos II G4 with 1Ghz CPU und 
 2GB Memory.
 Last week I got the stupid idea to install everything new using latest 
 Debian 7.8, because
 on the DVD there is still the install script for the Pegasos. :-)
 
 Installation itself is working fine till 95% and then abort there, some 
 like after-installation trigger.
 We tested it on several Pegasos II that we have, always the same. I can go 
 on without installing
 more software, but I assume that also some basic stuff is missing.
 
 Also the 3.x kernel is no more working on the Pegasos II, you will get 
 screen with grafic trash
 right after starting the kernel.
 
 IMG_9965.JPG
 
 Any idea? I tried it in the IRC, but got no answer. 
 
 It would be really fantastic if this problem could be fixed and the 
 Pegasos II will work again. 
 
 
 Best regards, Robert aka aPEX
 
 
 
 PS: I am just a user, no Linux guru, sorry for this…
 
 
 -- 
 To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact 
 listmas...@lists.debian.org
 Archive: 
 https://lists.debian.org/a1381917-b685-409d-8700-e25f3186f...@gmx.ch
 
 
 --
 To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 https://lists.debian.org/806dd26d-3f78-411c-9a64-22d775eb5...@gmail.com
 


--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/48ca16db-ab4c-4ee8-938e-8bb4535d1...@gmail.com



Re: Debian Jessie with openbox on iBook G4 crashing when firmware-linux-nonfree is installed

2015-04-29 Thread Herminio Hernandez Jr.
What did you use as your boot parameters in yaboot?

Sent from my iPhone

 On Apr 29, 2015, at 12:47 PM, luigi burdo intermedi...@hotmail.com wrote:
 
 Here on Quad G5 Xorg crash totally on jessie and it is not usable ... 
 sed the Wheezy was working really good.
 The same issue i face on Lubuntu 15.04 and Ubuntu Mate too.
 No problems on Open Suse 13.2
 I had been reported the issue of Xorg to xorg devs with a screenshot of the 
 issue and crash.
 
 Luigi Burdo
 
 Date: Tue, 28 Apr 2015 20:14:30 +0200
 From: christ...@chw.onl
 Subject: Debian Jessie with openbox on iBook G4 crashing when 
 firmware-linux-nonfree is installed
 To: debian-powerpc@lists.debian.org
 
 Hi!
 
 I have upgraded my Debian Wheezy to Jessie on my iBook G4 following the 
 upgrade manual from Debian which is really great by the way. 
 After that I wasn't able to  type the username in the Loginpanel (slim). 
 I was able to change to the command line with CTRL+ALT+F1 and starting a 
 openbos session with startx. Openbox crashes then after ii try to resize a 
 window.
 With firmware-linux-nonfree not installed it works without crashing once. 
 There are also two kernel modules that can't be loaded.  ppdev andapm_emu.
 I decied to make a fresh install. Same behaviour. I made a fresh install on 
 another iBook G3. Same behaviour.
 Then I tried uninstalling packages. firmware-linux-nonfree was the 
 reproducable cause. After reinstalling it crashes again.
 
 When running the system without firmware-linux-nonfree I have no sound. So I 
 decided to help myself with a 10$ USB DAC from EBAY. It worked fine as 
 workaround.
 
 Does anyone else had also the same problem?
 
 Cheers
 Chris
 


Re: Debian Jessie with openbox on iBook G4 crashing when firmware-linux-nonfree is installed

2015-04-29 Thread Herminio Hernandez, Jr.
I know you have my friend. Christian has an iBook and is having the same
issues. I am running stretch on mine and I am having no serious issues even
got 3D acceleration working.

On Wed, Apr 29, 2015 at 2:10 PM, luigi burdo intermedi...@hotmail.com
wrote:

 Herminio .
 i had been try with all parameters .
 with and without ofaonly with and without offb:off and all the radeon and
 nouveau ... and with
 screen resolution fixed.. i try all the combinations but nothing works
 here ... the Quad Xorg crash and the same on Qemu kvm ppc 64


 Luigi


 --
 Subject: Re: Debian Jessie with openbox on iBook G4 crashing when
 firmware-linux-nonfree is installed
 From: herminio.hernande...@gmail.com
 Date: Wed, 29 Apr 2015 13:30:34 -0500
 CC: christ...@chw.onl; debian-powerpc@lists.debian.org
 To: intermedi...@hotmail.com


 What did you use as your boot parameters in yaboot?

 Sent from my iPhone

 On Apr 29, 2015, at 12:47 PM, luigi burdo intermedi...@hotmail.com
 wrote:

 Here on Quad G5 Xorg crash totally on jessie and it is not usable ...
 sed the Wheezy was working really good.
 The same issue i face on Lubuntu 15.04 and Ubuntu Mate too.
 No problems on Open Suse 13.2
 I had been reported the issue of Xorg to xorg devs with a screenshot of
 the issue and crash.

 Luigi Burdo

 --
 Date: Tue, 28 Apr 2015 20:14:30 +0200
 From: christ...@chw.onl
 Subject: Debian Jessie with openbox on iBook G4 crashing when
 firmware-linux-nonfree is installed
 To: debian-powerpc@lists.debian.org

 Hi!

 I have upgraded my Debian Wheezy to Jessie on my iBook G4 following the
 upgrade manual from Debian which is really great by the way.
 After that I wasn't able to  type the username in the Loginpanel (slim).
 I was able to change to the command line with CTRL+ALT+F1 and starting a
 openbos session with startx. Openbox crashes then after ii try to resize
 a window.
 With firmware-linux-nonfree not installed it works without crashing once.
 There are also two kernel modules that can't be loaded.  ppdev andapm_emu.
 I decied to make a fresh install. Same behaviour. I made a fresh install
 on another iBook G3. Same behaviour.
 Then I tried uninstalling packages. firmware-linux-nonfree was the
 reproducable cause. After reinstalling it crashes again.

 When running the system without firmware-linux-nonfree I have no sound. So
 I decided to help myself with a 10$ USB DAC from EBAY. It worked fine as
 workaround.

 Does anyone else had also the same problem?

 Cheers
 Chris




  1   2   >