Re: Help with the arm64 and ppc64el installation-guides needed
And last little bit - what is the linux world thinking - spaces in file names? Good grief. (as well as very long names). root@jessie:/etc/NetworkManager# ls -l system* total 4 -rw--- 1 root root 260 May 1 22:44 Wired connection 1 On Sun, May 3, 2015 at 2:49 PM, Michael Felt aixto...@gmail.com wrote: Maybe something else to add to the release notes - the new /etc/NetworkManager/* (I hate long names and caps - I know this is not UNIX, but one of the goals of UNIX was to keep things short, fewer key presses, and less output (the example given was IBM 'mainframe' that gave a page of text for a command that had no output - making it much easier to start the 'pipe' concept - only send the output) compared to /etc/network/* for configuring (static) interfaces. imho a real pain - every distribution of Linux has a different way of doing things (although I am beginning to think it is a different version of Linux - change things because we can - because every distribution of Linux seems to be a different version of Linux). Previous UNIX vendors would have been hung out to dry for this kind of 'change management (read mis-management). (imho). Anyway, please add NetworkManager - and other core Linux changes, or a link to 'Linux-world' changes - although I would expect Debian to take responsibility for the list of changes between: Linux wheezy 3.2.0-4-powerpc64 #1 SMP Debian 3.2.68-1+deb7u1 ppc64 GNU/Linux and Linux jessie 3.16.0-4-powerpc64 #1 SMP Debian 3.16.7-ckt9-3 (2015-04-23) ppc64 GNU/Linux my two cents. On Sat, May 2, 2015 at 2:16 PM, Ben Hutchings b...@decadent.org.uk wrote: On Sat, 2015-05-02 at 11:15 +0200, Michael Felt wrote: [...] BTW: I notice a slight difference in how 'login as root' works between wheezy and jessie. On both systems I have enabled 'root login' for my initial tests. With wheezy I cannot login as root on the console, but can login using ssh. On Jessie this is the reverse. I assume this is deliberate. [...] The ssh part: yes, and that's documented in the release notes: https://www.debian.org/releases/jessie/powerpc/release-notes/ch-information.en.html#openssh . The console part: I don't think so; this is probably a bug in wheezy. The last time I had that sort of problem, it was due to an omission from the file /etc/securetty (list of devices that root may log in through). But in wheezy that file does include hvc0. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less.
Re: Help with the arm64 and ppc64el installation-guides needed
Maybe something else to add to the release notes - the new /etc/NetworkManager/* (I hate long names and caps - I know this is not UNIX, but one of the goals of UNIX was to keep things short, fewer key presses, and less output (the example given was IBM 'mainframe' that gave a page of text for a command that had no output - making it much easier to start the 'pipe' concept - only send the output) compared to /etc/network/* for configuring (static) interfaces. imho a real pain - every distribution of Linux has a different way of doing things (although I am beginning to think it is a different version of Linux - change things because we can - because every distribution of Linux seems to be a different version of Linux). Previous UNIX vendors would have been hung out to dry for this kind of 'change management (read mis-management). (imho). Anyway, please add NetworkManager - and other core Linux changes, or a link to 'Linux-world' changes - although I would expect Debian to take responsibility for the list of changes between: Linux wheezy 3.2.0-4-powerpc64 #1 SMP Debian 3.2.68-1+deb7u1 ppc64 GNU/Linux and Linux jessie 3.16.0-4-powerpc64 #1 SMP Debian 3.16.7-ckt9-3 (2015-04-23) ppc64 GNU/Linux my two cents. On Sat, May 2, 2015 at 2:16 PM, Ben Hutchings b...@decadent.org.uk wrote: On Sat, 2015-05-02 at 11:15 +0200, Michael Felt wrote: [...] BTW: I notice a slight difference in how 'login as root' works between wheezy and jessie. On both systems I have enabled 'root login' for my initial tests. With wheezy I cannot login as root on the console, but can login using ssh. On Jessie this is the reverse. I assume this is deliberate. [...] The ssh part: yes, and that's documented in the release notes: https://www.debian.org/releases/jessie/powerpc/release-notes/ch-information.en.html#openssh . The console part: I don't think so; this is probably a bug in wheezy. The last time I had that sort of problem, it was due to an omission from the file /etc/securetty (list of devices that root may log in through). But in wheezy that file does include hvc0. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less.
Re: Help with the arm64 and ppc64el installation-guides needed
By the way - I just looked at your installation instructions and I did not find anything about how to install in POWER Server environment, i.e., as a virtual machine (aka LPAR) on IBM POWER5 and later. The ppc64le using KVM will obviously be different, but people using powerpc (historically 32-bit - is that correct, and why I cannot SMOKE perl with -Duse64bitall ?). Anyway - I have an installation 'story' I wrote up quite a while ago. http://www.rootvg.net/content/view/560/88/ I just reused this procedure to install Jessie and it still works fine. I like the command-line install very much. One of my reasons that debian is my personal favorite for Linux on Power. BTW: I notice a slight difference in how 'login as root' works between wheezy and jessie. On both systems I have enabled 'root login' for my initial tests. With wheezy I cannot login as root on the console, but can login using ssh. On Jessie this is the reverse. I assume this is deliberate. (I'll open a new thread to ask how to manage this, because sshd_config - which I know - seems to permit RootLogin (--without-password) but I have not managed to get it to work. Normally I do not want this, but for testing - logging in as root is how I start learning many things (i.e., I skip installing sudo and sudo su -). So, the question for here - regarding documentation - is there a CHANGES document I have missed that summarizes and/or details the changes (intended) between wheezy and jessie? Michael On Mon, Apr 13, 2015 at 9:46 PM, Holger Wansing li...@wansing-online.de wrote: Hi, Lennart Sorensen lsore...@csclub.uwaterloo.ca wrote: On Mon, Apr 13, 2015 at 09:37:42PM +0200, Holger Wansing wrote: Hi, Samuel Thibault sthiba...@debian.org wrote: Holger Wansing, le Sat 11 Apr 2015 17:13:06 +0200, a écrit : +arch_porturl=ppc64el +arch_listname=ppc64el Please take care when updating these to be sure to understand what they mean. http://www.debian.org/ports/ppc64el and http://lists.debian.org/debian-ppc64el don't exist. I knew this! But there needs to be created a site under http://www.debian.org/ports/ for ppc64el, when ppc64el gets a release arch. The only page for ppc64el on the ports page ATM is on the debian wiki. That will have to be changed. Otherwise that above entity in our d-i manual will fail to work, no matter which arch name you choose. I would think that just like armhf uses the debian-arm list, ppc64el will continue to use the debian-powerpc list. Yeah, I just saw that Samuel left the above entities at powerpc. That does of course work :-) Holger -- Created with Sylpheed 3.2.0 under D E B I A N L I N U X 7 . 0 W H E E Z Y ! Registered Linux User #311290 - https://linuxcounter.net/ -- 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/20150413214642.d550d8d8f90c341da72e7...@wansing-online.de
Re: Help with the arm64 and ppc64el installation-guides needed
Maybe - last time I tried - I mistyped the login - because login from console is working for both - thanks for the reply. re: root login on sshd - guess I need to read more carefully. I know about the cipher changes starting with OpenSSH 6.7, but had not yet stumbled on anything extra blocking root login. My apologies for a false statement! Must test again and again (so I will have to reload ubuntu, opensles and fedora to see which ones of those refuse root login at console. If both are blocked (with the newer openssh) may make some maintenance work difficult. Further - any interest in a different (in what way please) story on installing debian on PowerVM enabled systems? On Sat, May 2, 2015 at 2:16 PM, Ben Hutchings b...@decadent.org.uk wrote: On Sat, 2015-05-02 at 11:15 +0200, Michael Felt wrote: [...] BTW: I notice a slight difference in how 'login as root' works between wheezy and jessie. On both systems I have enabled 'root login' for my initial tests. With wheezy I cannot login as root on the console, but can login using ssh. On Jessie this is the reverse. I assume this is deliberate. [...] The ssh part: yes, and that's documented in the release notes: https://www.debian.org/releases/jessie/powerpc/release-notes/ch-information.en.html#openssh . The console part: I don't think so; this is probably a bug in wheezy. The last time I had that sort of problem, it was due to an omission from the file /etc/securetty (list of devices that root may log in through). But in wheezy that file does include hvc0. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less.
Re: Help with the arm64 and ppc64el installation-guides needed
Just read the link re: PermitRoot --without-password My comment - typical developer string - because many people are looking for passwordless login for root, and from my UNIX background I would take --without-password very literally. I suspect what is intended is --no-password-auth-permitted, meaning some other form of authentication is accepted, e.g., PKI. Because of the comment in sshd_config I was thinking it was something in the PAM configuration I needed to look at. And, FYI - if you follow the suggestion in the sshd_config (re PAM) no login for anyone (using passwords at least) is permitted. Thank you for the link - I shall copy my keys in (later) and report back. And secondly, for the link - for the changes history! Excellent! Michael On Sat, May 2, 2015 at 6:19 PM, Michael Felt aixto...@gmail.com wrote: Maybe - last time I tried - I mistyped the login - because login from console is working for both - thanks for the reply. re: root login on sshd - guess I need to read more carefully. I know about the cipher changes starting with OpenSSH 6.7, but had not yet stumbled on anything extra blocking root login. My apologies for a false statement! Must test again and again (so I will have to reload ubuntu, opensles and fedora to see which ones of those refuse root login at console. If both are blocked (with the newer openssh) may make some maintenance work difficult. Further - any interest in a different (in what way please) story on installing debian on PowerVM enabled systems? On Sat, May 2, 2015 at 2:16 PM, Ben Hutchings b...@decadent.org.uk wrote: On Sat, 2015-05-02 at 11:15 +0200, Michael Felt wrote: [...] BTW: I notice a slight difference in how 'login as root' works between wheezy and jessie. On both systems I have enabled 'root login' for my initial tests. With wheezy I cannot login as root on the console, but can login using ssh. On Jessie this is the reverse. I assume this is deliberate. [...] The ssh part: yes, and that's documented in the release notes: https://www.debian.org/releases/jessie/powerpc/release-notes/ch-information.en.html#openssh . The console part: I don't think so; this is probably a bug in wheezy. The last time I had that sort of problem, it was due to an omission from the file /etc/securetty (list of devices that root may log in through). But in wheezy that file does include hvc0. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less.
Re: Help with the arm64 and ppc64el installation-guides needed
On Sat, 2015-05-02 at 11:15 +0200, Michael Felt wrote: [...] BTW: I notice a slight difference in how 'login as root' works between wheezy and jessie. On both systems I have enabled 'root login' for my initial tests. With wheezy I cannot login as root on the console, but can login using ssh. On Jessie this is the reverse. I assume this is deliberate. [...] The ssh part: yes, and that's documented in the release notes: https://www.debian.org/releases/jessie/powerpc/release-notes/ch-information.en.html#openssh. The console part: I don't think so; this is probably a bug in wheezy. The last time I had that sort of problem, it was due to an omission from the file /etc/securetty (list of devices that root may log in through). But in wheezy that file does include hvc0. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part
Re: Help with the arm64 and ppc64el installation-guides needed
On Mon, Apr 13, 2015 at 09:37:42PM +0200, Holger Wansing wrote: Hi, Samuel Thibault sthiba...@debian.org wrote: Holger Wansing, le Sat 11 Apr 2015 17:13:06 +0200, a écrit : +arch_porturl=ppc64el +arch_listname=ppc64el Please take care when updating these to be sure to understand what they mean. http://www.debian.org/ports/ppc64el and http://lists.debian.org/debian-ppc64el don't exist. I knew this! But there needs to be created a site under http://www.debian.org/ports/ for ppc64el, when ppc64el gets a release arch. The only page for ppc64el on the ports page ATM is on the debian wiki. That will have to be changed. Otherwise that above entity in our d-i manual will fail to work, no matter which arch name you choose. I would think that just like armhf uses the debian-arm list, ppc64el will continue to use the debian-powerpc list. -- Len Sorensen -- 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/20150413195056.gl29...@csclub.uwaterloo.ca
Re: Help with the arm64 and ppc64el installation-guides needed
Hi, Lennart Sorensen lsore...@csclub.uwaterloo.ca wrote: On Mon, Apr 13, 2015 at 09:37:42PM +0200, Holger Wansing wrote: Hi, Samuel Thibault sthiba...@debian.org wrote: Holger Wansing, le Sat 11 Apr 2015 17:13:06 +0200, a écrit : +arch_porturl=ppc64el +arch_listname=ppc64el Please take care when updating these to be sure to understand what they mean. http://www.debian.org/ports/ppc64el and http://lists.debian.org/debian-ppc64el don't exist. I knew this! But there needs to be created a site under http://www.debian.org/ports/ for ppc64el, when ppc64el gets a release arch. The only page for ppc64el on the ports page ATM is on the debian wiki. That will have to be changed. Otherwise that above entity in our d-i manual will fail to work, no matter which arch name you choose. I would think that just like armhf uses the debian-arm list, ppc64el will continue to use the debian-powerpc list. Yeah, I just saw that Samuel left the above entities at powerpc. That does of course work :-) Holger -- Created with Sylpheed 3.2.0 under D E B I A N L I N U X 7 . 0 W H E E Z Y ! Registered Linux User #311290 - https://linuxcounter.net/ -- 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/20150413214642.d550d8d8f90c341da72e7...@wansing-online.de
Re: Help with the arm64 and ppc64el installation-guides needed
Hi, Samuel Thibault sthiba...@debian.org wrote: Holger Wansing, le Sat 11 Apr 2015 17:13:06 +0200, a écrit : +arch_porturl=ppc64el +arch_listname=ppc64el Please take care when updating these to be sure to understand what they mean. http://www.debian.org/ports/ppc64el and http://lists.debian.org/debian-ppc64el don't exist. I knew this! But there needs to be created a site under http://www.debian.org/ports/ for ppc64el, when ppc64el gets a release arch. The only page for ppc64el on the ports page ATM is on the debian wiki. That will have to be changed. Otherwise that above entity in our d-i manual will fail to work, no matter which arch name you choose. Holger -- Created with Sylpheed 3.2.0 under D E B I A N L I N U X 7 . 0 W H E E Z Y ! Registered Linux User #311290 - https://linuxcounter.net/ -- 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/20150413213742.378bdfd52d69d650cb930...@wansing-online.de
Re: Help with the arm64 and ppc64el installation-guides needed
On Mon, Apr 13, 2015 at 10:26:51AM -0300, Thadeu Lima de Souza Cascardo wrote: Well, bare metal has been mistakenly used to describe what I would call dedicated partition of single partition mode. People may call it bare metal, because there is no virtualized IO (in fact, there is the console), and CPU and memory resources are not shared with other partitions. But there is still a Hypervisor under the OS. It's still a PowerVM LPAR, and boot capabilities still apply as though you were sharing the server with other partitions. So PowerVM is built into the firmware and is always running? We certainly did not order or install PowerVM in any way. I do see in the boot messages that hvc is a virtual console. -- Len Sorensen -- 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/20150413140748.gk29...@csclub.uwaterloo.ca
Re: Help with the arm64 and ppc64el installation-guides needed
On Sun, Apr 12, 2015 at 09:43:07PM -0400, Lennart Sorensen wrote: On Sun, Apr 12, 2015 at 08:45:50PM -0300, Thadeu Lima de Souza Cascardo wrote: When it comes to IBM latest servers, that are three options for platforms: OPAL (powernv in Linux), as PowerKVM guest, and PowerVM LPAR (both pseries platform in Linux). OPAL has petitboot built-in, PowerKVM uses SLOF and PowerVM uses IBM Open Firmware. The three are capable of booting from optical media, USB, and netboot. With the exception of KVM guests, when a supported graphical card is used, graphical installation should be an option as well. For KVM guests, there is offb, which should work with VNC. Should we enable graphical installation in the media? Or is just netboot images missing graphical support on d-i? So does this mean that PowerVM LPAR is the same as running on the bare metal (which is the only way I have run debian on IBM pSeries systems, specifically a p520 power6+ and a p710 power7). Certainly openfirmware booting with grub2 is the only method I have ever used. IBM support people sure do seem confused when they hear you have no HMC or VM or anything else on your pSeries. Just Debian on the bare metal. Well, bare metal has been mistakenly used to describe what I would call dedicated partition of single partition mode. People may call it bare metal, because there is no virtualized IO (in fact, there is the console), and CPU and memory resources are not shared with other partitions. But there is still a Hypervisor under the OS. It's still a PowerVM LPAR, and boot capabilities still apply as though you were sharing the server with other partitions. Hope that clarifies. Cascardo. -- Len Sorensen signature.asc Description: Digital signature
Re: Help with the arm64 and ppc64el installation-guides needed
Breno Leitao, le Mon 13 Apr 2015 10:04:29 -0300, a écrit : Sorry, I answered your email twice regarding this topic and never heard back. I answered it initially in 2014-11-29[1] and later in 2014-12-18[2]. In both cases I told about our patches to this repository. I'm not subscribed to the debian-powerpc mailing list... Samuel -- 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/20150413133927.gj3...@type.bordeaux.inria.fr
Re: Help with the arm64 and ppc64el installation-guides needed
Hi Samuel, On 04/10/2015 07:24 PM, Samuel Thibault wrote: Hello, Breno Leitao, le Fri 10 Apr 2015 17:44:01 -0300, a écrit : On 04/09/2015 01:13 PM, Karsten Merker wrote: Hello everybody, the release date for Jessie is near, but the installation-guide does not seem to contain any arm64/ppc64el-specific information yet. We have created this installation guide, but unfortunatelly it was not integrated yet. It is still on my github repository. Can you import it? Uh. I requested this very kind of information in september and november, why wasn't this work (done in december) ever submitted before? Sorry, I answered your email twice regarding this topic and never heard back. I answered it initially in 2014-11-29[1] and later in 2014-12-18[2]. In both cases I told about our patches to this repository. [1] https://lists.debian.org/debian-powerpc/2014/12/msg00016.html [2] https://lists.debian.org/debian-powerpc/2014/12/msg00025.html -- 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/552bbedd.9080...@br.ibm.com
Re: Help with the arm64 and ppc64el installation-guides needed
On Thu, Apr 09, 2015 at 06:13:50PM +0200, Karsten Merker wrote: Hello everybody, the release date for Jessie is near, but the installation-guide does not seem to contain any arm64/ppc64el-specific information yet. It would be nice if those who are familiar with those platforms could provide patches against the installation guide, so that we can release with proper documentation. At least some basic information about the supported hardware for the overview at https://jenkins.debian.net/userContent/installation-guide/installation-guide-arm64/en/ch02s01.html https://jenkins.debian.net/userContent/installation-guide/installation-guide-ppc64el/en/ch02s01.html For arm64, we have a generic kernel that (modulo DTB) should work on all the supportable hardware, similar to i386 and amd64. I'd leave this section blank for arm64, like for the x86 maybe? Or would people rather see some text to describe the hardware as a single flavour, like for the ppc64el case? and information about available boot methods at https://jenkins.debian.net/userContent/installation-guide/installation-guide-ppc64el/en/ch05s01.html https://jenkins.debian.net/userContent/installation-guide/installation-guide-arm64/en/ch05s01.html would be nice. Currently all documentation in the arm64/ppc64el versions of the installation guide describes only the corresponding 32bit-Platforms. Right. This section is definitely going to need work for arm64, to describe both U-Boot and UEFI boot options across platforms. I'm looking it now, but it's going to need some time. I'm hoping to be able to re-use some of the existing content from amd64 and armhf, at least... -- Steve McIntyre, Cambridge, UK.st...@einval.com I've only once written 'SQL is my bitch' in a comment. But that code is in use on a military site... -- Simon Booth -- 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/20150412230508.gj1...@einval.com
Re: Help with the arm64 and ppc64el installation-guides needed
On Sun, Apr 12, 2015 at 6:43 PM, Lennart Sorensen lsore...@csclub.uwaterloo.ca wrote: On Sun, Apr 12, 2015 at 08:45:50PM -0300, Thadeu Lima de Souza Cascardo wrote: Sorry for jumping in. I would like the chance to complement and clarify some things about ppc64el platform. As Aurelien pointed out, when used in OPAL mode, the system will boot a system running petitboot, which is capable of netboot, booting from disk, and install media. So, will it boot from USB media? Yes. When it comes to IBM latest servers, that are three options for platforms: OPAL (powernv in Linux), as PowerKVM guest, and PowerVM LPAR (both pseries platform in Linux). OPAL has petitboot built-in, PowerKVM uses SLOF and PowerVM uses IBM Open Firmware. The three are capable of booting from optical media, USB, and netboot. With the exception of KVM guests, when a supported graphical card is used, graphical installation should be an option as well. For KVM guests, there is offb, which should work with VNC. Should we enable graphical installation in the media? Or is just netboot images missing graphical support on d-i? So does this mean that PowerVM LPAR is the same as running on the bare metal (which is the only way I have run debian on IBM pSeries systems, specifically a p520 power6+ and a p710 power7). Certainly openfirmware booting with grub2 is the only method I have ever used. IBM support people sure do seem confused when they hear you have no HMC or VM or anything else on your pSeries. Just Debian on the bare metal. One caveat: I may be mistaken on the current state of support for USB and netboot on SLOF. But considering it's a KVM guest using qemu, there is much more flexibility, if things are downloaded on the host. I would say that is one of the things that we should document on the installation-guide. Is that right? As for wireless network adapters, the systems don't ship with any, and I haven't heard of any testing with any drivers. Nonetheless, those systems support PCI 3.0 and USB 3.0, so there is no reason those adapters shouldn't work, giving enough testing and fixes. But I would leave that out. As for other systems supporting ppc64el, OpenPower members have been releasing new systems using Power8 and supporting little-endian from the start. As already mentioned, older IBM systems could be capable as well, but I wouldn't say that is supported. As for chips from Freescale, I can't tell much. For 64-bit capable old Macs, I suppose firmware could be a problem. For those systems, adopting ppc64 (BE) would offer an option. Why 64-bit? Well, the same answer applies for all platforms. Address space. I suppose some people cannot even run web browsers these days without 64-bit :-). Of course, that has some disadvantages, like the memory footprint because of pointers, that x32 tries to address. I sometimes wonder if limiting the browser to 2GB of memory is a convinient way to prevent the leaks from getting out of hand in the terrible code that is in web browsers. 4GB when kernel is 64-bit -- Len Sorensen -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150413014307.gj29...@csclub.uwaterloo.ca -- Liberty equality fraternity or death, Shawn Landden ChurchOfGit.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/CAJusiZXR-YYYBa1zOX_jBr=S0=iionb3s47zxe6ebyzvp9v...@mail.gmail.com
Re: Help with the arm64 and ppc64el installation-guides needed
On Sun, Apr 12, 2015 at 08:45:50PM -0300, Thadeu Lima de Souza Cascardo wrote: Sorry for jumping in. I would like the chance to complement and clarify some things about ppc64el platform. As Aurelien pointed out, when used in OPAL mode, the system will boot a system running petitboot, which is capable of netboot, booting from disk, and install media. So, will it boot from USB media? Yes. When it comes to IBM latest servers, that are three options for platforms: OPAL (powernv in Linux), as PowerKVM guest, and PowerVM LPAR (both pseries platform in Linux). OPAL has petitboot built-in, PowerKVM uses SLOF and PowerVM uses IBM Open Firmware. The three are capable of booting from optical media, USB, and netboot. With the exception of KVM guests, when a supported graphical card is used, graphical installation should be an option as well. For KVM guests, there is offb, which should work with VNC. Should we enable graphical installation in the media? Or is just netboot images missing graphical support on d-i? So does this mean that PowerVM LPAR is the same as running on the bare metal (which is the only way I have run debian on IBM pSeries systems, specifically a p520 power6+ and a p710 power7). Certainly openfirmware booting with grub2 is the only method I have ever used. IBM support people sure do seem confused when they hear you have no HMC or VM or anything else on your pSeries. Just Debian on the bare metal. One caveat: I may be mistaken on the current state of support for USB and netboot on SLOF. But considering it's a KVM guest using qemu, there is much more flexibility, if things are downloaded on the host. I would say that is one of the things that we should document on the installation-guide. Is that right? As for wireless network adapters, the systems don't ship with any, and I haven't heard of any testing with any drivers. Nonetheless, those systems support PCI 3.0 and USB 3.0, so there is no reason those adapters shouldn't work, giving enough testing and fixes. But I would leave that out. As for other systems supporting ppc64el, OpenPower members have been releasing new systems using Power8 and supporting little-endian from the start. As already mentioned, older IBM systems could be capable as well, but I wouldn't say that is supported. As for chips from Freescale, I can't tell much. For 64-bit capable old Macs, I suppose firmware could be a problem. For those systems, adopting ppc64 (BE) would offer an option. Why 64-bit? Well, the same answer applies for all platforms. Address space. I suppose some people cannot even run web browsers these days without 64-bit :-). Of course, that has some disadvantages, like the memory footprint because of pointers, that x32 tries to address. I sometimes wonder if limiting the browser to 2GB of memory is a convinient way to prevent the leaks from getting out of hand in the terrible code that is in web browsers. -- Len Sorensen -- 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/20150413014307.gj29...@csclub.uwaterloo.ca
Re: Help with the arm64 and ppc64el installation-guides needed
Aurelien Jarno, le Sun 12 Apr 2015 22:08:44 +0200, a écrit : On 2015-04-12 20:22, Samuel Thibault wrote: Since petitboot runs inside a running linux kernel, that only shifts the problem of booting that linux kernel :) Petitboot is the default bootloader on this machine when configured to run Linux. It's the interface the user see when powering up the machine. Uh. Interesting :D Thanks, Samuel -- 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/20150412210608.ga2...@type.wlan.youpi.perso.aquilenet.fr
Re: Help with the arm64 and ppc64el installation-guides needed
On Sun, 2015-04-12 at 22:04 +0200, Samuel Thibault wrote: Ben Hutchings, le Sun 12 Apr 2015 20:27:29 +0100, a écrit : On Sun, 2015-04-12 at 20:45 +0200, Samuel Thibault wrote: Ben Hutchings, le Sun 12 Apr 2015 00:35:33 +0100, a écrit : On Sat, 2015-04-11 at 20:22 +0200, Holger Wansing wrote: supports-smp-sometimes - that generation of cpu will most likely fully support smp, right? [...] Yes. That's not the question here, see the bit of documentation that it enables: it's whether the *kernel* supports SMP by default, through SMP-alternatives, in a separate image, or not in any shipped image. There is only one kernel flavour, which of course supports SMP. I don't think SMP-alternatives exist on anything but x86 and ARM, unfortunately. Ok, thanks. By the way, is this correctly documented for armhf? Both of the armhf kernel flavours support SMP with SMP-alternatives. Apparently nobody updated build/arch-options/armhf in that regard. Note that smp_config_section and smp_config_option should also be set (they are the section and option that should be used to enable SMP when configuring Linux). I've fixed these values (I hope) for armhf, arm64, mips and mipsel based on the current kernel configurations. Ben. -- Ben Hutchings compatible: Gracefully accepts erroneous data from any source signature.asc Description: This is a digitally signed message part
Re: Help with the arm64 and ppc64el installation-guides needed
Ben Hutchings, le Sun 12 Apr 2015 23:13:34 +0100, a écrit : I've fixed these values (I hope) for armhf, arm64, mips and mipsel based on the current kernel configurations. Thanks! Samuel -- 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/20150412221805.ge2...@type.wlan.youpi.perso.aquilenet.fr
Re: Help with the arm64 and ppc64el installation-guides needed
Samuel Thibault sthiba...@debian.org (2015-04-12): Holger Wansing, le Sat 11 Apr 2015 17:13:06 +0200, a écrit : All that contained in attached patch for review. The manual builds fine with it. Thanks, I have fixed a couple more things and commited it. Cyril, when should we upload an updated installation guide to be ready for RC3? Things are still a bit sketchy, but if we can have everything d-i related uploaded/unblocked by friday 17th, that'd be nice. Mraw, KiBi. signature.asc Description: Digital signature
Re: Help with the arm64 and ppc64el installation-guides needed
On Sun, Apr 12, 2015 at 11:06:08PM +0200, Samuel Thibault wrote: Aurelien Jarno, le Sun 12 Apr 2015 22:08:44 +0200, a écrit : On 2015-04-12 20:22, Samuel Thibault wrote: Since petitboot runs inside a running linux kernel, that only shifts the problem of booting that linux kernel :) Petitboot is the default bootloader on this machine when configured to run Linux. It's the interface the user see when powering up the machine. Uh. Interesting :D Thanks, Samuel Sorry for jumping in. I would like the chance to complement and clarify some things about ppc64el platform. As Aurelien pointed out, when used in OPAL mode, the system will boot a system running petitboot, which is capable of netboot, booting from disk, and install media. So, will it boot from USB media? Yes. When it comes to IBM latest servers, that are three options for platforms: OPAL (powernv in Linux), as PowerKVM guest, and PowerVM LPAR (both pseries platform in Linux). OPAL has petitboot built-in, PowerKVM uses SLOF and PowerVM uses IBM Open Firmware. The three are capable of booting from optical media, USB, and netboot. With the exception of KVM guests, when a supported graphical card is used, graphical installation should be an option as well. For KVM guests, there is offb, which should work with VNC. Should we enable graphical installation in the media? Or is just netboot images missing graphical support on d-i? One caveat: I may be mistaken on the current state of support for USB and netboot on SLOF. But considering it's a KVM guest using qemu, there is much more flexibility, if things are downloaded on the host. I would say that is one of the things that we should document on the installation-guide. Is that right? As for wireless network adapters, the systems don't ship with any, and I haven't heard of any testing with any drivers. Nonetheless, those systems support PCI 3.0 and USB 3.0, so there is no reason those adapters shouldn't work, giving enough testing and fixes. But I would leave that out. As for other systems supporting ppc64el, OpenPower members have been releasing new systems using Power8 and supporting little-endian from the start. As already mentioned, older IBM systems could be capable as well, but I wouldn't say that is supported. As for chips from Freescale, I can't tell much. For 64-bit capable old Macs, I suppose firmware could be a problem. For those systems, adopting ppc64 (BE) would offer an option. Why 64-bit? Well, the same answer applies for all platforms. Address space. I suppose some people cannot even run web browsers these days without 64-bit :-). Of course, that has some disadvantages, like the memory footprint because of pointers, that x32 tries to address. Regards. Cascardo. signature.asc Description: Digital signature
Re: Help with the arm64 and ppc64el installation-guides needed
On Sat, Apr 11, 2015 at 9:53 PM, Paul Wise p...@debian.org wrote: On Sat, Apr 11, 2015 at 5:44 AM, Sandeep G.R wrote: I have a sid PPC64 from http://ftp.de.debian.org/debian-ports running on Freescale Powerpc. Is their PPC64(Big-Endian) for Jessie similarly? The PPC64 port didn't get added to jessie, if you want jessie you'll need to switch to ppc64el. If you want PPC64 big-endian, stick to debian-ports unstable. Some info about the port is here: https://wiki.debian.org/PPC64 -- bye, pabs https://wiki.debian.org/PaulWise Thanks Paul. I guess ppc64el is for only IBM power8 machines not for Freescale powerpc right. -- *Thanks Regards,* *Sandeep G R*
Re: Help with the arm64 and ppc64el installation-guides needed
Lennart, Thanks for more information. I can check with Freescale running little endian on e6500. On Sun, Apr 12, 2015 at 10:26 AM, Lennart Sorensen lsore...@csclub.uwaterloo.ca wrote: On Sun, Apr 12, 2015 at 07:16:50AM -0600, Sandeep G.R wrote: On Sat, Apr 11, 2015 at 9:53 PM, Paul Wise p...@debian.org wrote: On Sat, Apr 11, 2015 at 5:44 AM, Sandeep G.R wrote: I have a sid PPC64 from http://ftp.de.debian.org/debian-ports running on Freescale Powerpc. Is their PPC64(Big-Endian) for Jessie similarly? The PPC64 port didn't get added to jessie, if you want jessie you'll need to switch to ppc64el. If you want PPC64 big-endian, stick to debian-ports unstable. Some info about the port is here: https://wiki.debian.org/PPC64 -- bye, pabs https://wiki.debian.org/PaulWise Thanks Paul. I guess ppc64el is for only IBM power8 machines not for Freescale powerpc right. Well I have only heard of it running on power8 (and I think as a guest in a VM on a power7 if I recall correctly). Since my understanding of the purpose of ppc64el is to make exchanging data with nvidia cards more efficient (since they are designed for little endian data), and you probably aren't doing that with the freescale chips, the ppc64el probably doesn't serve any purpose for the freescale chips. Of course I am not even sure running 64bit userspace serves much purpose for most uses either. Is there really anything gained running 64bit powerpc userspace in general? According to what I have read, the freescale e6500 can run little endian, except the altivec bit can not, which rather ruins the use in little endian mode. -- Len Sorensen -- *Thanks Regards,* *Sandeep G R*
Re: Help with the arm64 and ppc64el installation-guides needed
On Sun, Apr 12, 2015 at 07:16:50AM -0600, Sandeep G.R wrote: On Sat, Apr 11, 2015 at 9:53 PM, Paul Wise p...@debian.org wrote: On Sat, Apr 11, 2015 at 5:44 AM, Sandeep G.R wrote: I have a sid PPC64 from http://ftp.de.debian.org/debian-ports running on Freescale Powerpc. Is their PPC64(Big-Endian) for Jessie similarly? The PPC64 port didn't get added to jessie, if you want jessie you'll need to switch to ppc64el. If you want PPC64 big-endian, stick to debian-ports unstable. Some info about the port is here: https://wiki.debian.org/PPC64 -- bye, pabs https://wiki.debian.org/PaulWise Thanks Paul. I guess ppc64el is for only IBM power8 machines not for Freescale powerpc right. Well I have only heard of it running on power8 (and I think as a guest in a VM on a power7 if I recall correctly). Since my understanding of the purpose of ppc64el is to make exchanging data with nvidia cards more efficient (since they are designed for little endian data), and you probably aren't doing that with the freescale chips, the ppc64el probably doesn't serve any purpose for the freescale chips. Of course I am not even sure running 64bit userspace serves much purpose for most uses either. Is there really anything gained running 64bit powerpc userspace in general? According to what I have read, the freescale e6500 can run little endian, except the altivec bit can not, which rather ruins the use in little endian mode. -- Len Sorensen -- 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/20150412162653.gi29...@csclub.uwaterloo.ca
Re: Help with the arm64 and ppc64el installation-guides needed
On Sun, 2015-04-12 at 20:45 +0200, Samuel Thibault wrote: Ben Hutchings, le Sun 12 Apr 2015 00:35:33 +0100, a écrit : On Sat, 2015-04-11 at 20:22 +0200, Holger Wansing wrote: supports-smp-sometimes - that generation of cpu will most likely fully support smp, right? [...] Yes. That's not the question here, see the bit of documentation that it enables: it's whether the *kernel* supports SMP by default, through SMP-alternatives, in a separate image, or not in any shipped image. There is only one kernel flavour, which of course supports SMP. I don't think SMP-alternatives exist on anything but x86 and ARM, unfortunately. By the way, is this correctly documented for armhf? Both of the armhf kernel flavours support SMP with SMP-alternatives. Ben. -- Ben Hutchings compatible: Gracefully accepts erroneous data from any source signature.asc Description: This is a digitally signed message part
Re: Help with the arm64 and ppc64el installation-guides needed
Holger Wansing, le Sat 11 Apr 2015 17:13:06 +0200, a écrit : +arch_porturl=ppc64el +arch_listname=ppc64el Please take care when updating these to be sure to understand what they mean. http://www.debian.org/ports/ppc64el and http://lists.debian.org/debian-ppc64el don't exist. Samuel -- 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/20150412183314.GE2969@type
Re: Help with the arm64 and ppc64el installation-guides needed
Holger Wansing, le Sat 11 Apr 2015 21:20:37 +0200, a écrit : And: is there support for the graphical installer? As far as I can see, the images do not contain the graphical installer. See the documentation we have for powerpc: we generate only the mini GTK isos for it (on e.g. http://ftp.nl.debian.org/debian/dists/testing/main/installer-powerpc/current/images/powerpc/netboot/gtk/ ). It seems we don't generate them for ppc64el, see http://ftp.nl.debian.org/debian/dists/testing/main/installer-ppc64el/current/images/netboot/ Samuel -- 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/20150412183957.GG2969@type
Re: Help with the arm64 and ppc64el installation-guides needed
Ben Hutchings, le Sun 12 Apr 2015 00:35:33 +0100, a écrit : On Sat, 2015-04-11 at 20:22 +0200, Holger Wansing wrote: supports-smp-sometimes - that generation of cpu will most likely fully support smp, right? [...] Yes. That's not the question here, see the bit of documentation that it enables: it's whether the *kernel* supports SMP by default, through SMP-alternatives, in a separate image, or not in any shipped image. Samuel -- 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/20150412184535.GH2969@type
Re: Help with the arm64 and ppc64el installation-guides needed
Samuel Thibault, le Sun 12 Apr 2015 20:36:22 +0200, a écrit : Holger Wansing, le Sat 11 Apr 2015 20:22:49 +0200, a écrit : supports-floppy-boot - I think that arch has no floppy support Does ppc64el supports booting from a USB stick? More precisely, at the moment the only enabled documented way in Booting the Installation System is Petitboot, which is not really useful... Samuel -- 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/20150412185814.GA9152@type
Re: Help with the arm64 and ppc64el installation-guides needed
Holger Wansing, le Sat 11 Apr 2015 17:13:06 +0200, a écrit : All that contained in attached patch for review. The manual builds fine with it. Thanks, I have fixed a couple more things and commited it. Cyril, when should we upload an updated installation guide to be ready for RC3? Samuel -- 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/20150412190109.GI2969@type
Re: Help with the arm64 and ppc64el installation-guides needed
Hello, Mmm, the following looks like a useless addition: Holger Wansing, le Sat 11 Apr 2015 17:13:06 +0200, a écrit : Index: en/boot-installer/powerpc.xml === --- en/boot-installer/powerpc.xml (Revision 69729) +++ en/boot-installer/powerpc.xml (Arbeitskopie) @@ -283,3 +283,41 @@ /para /sect2 + + sect2 arch=ppc64el titleBooting a ppc64el machine/title +para + +How to boot a ppc64el machine: + +/para + + sect3 titlePetitboot/title +para + +Petitboot is a platform independent bootloader based on the Linux kexec. +Petitboot supports loading kernel, initrd and device tree files from +any Linux mountable filesystem, plus can load files from the network +using the FTP, SFTP, TFTP, NFS, HTTP and HTTPS protocols. Petitboot can +boot any operating system that includes kexec boot support. + +/parapara + +Petitboot looks for bootloader configuration files on mountable devices +in the system, and can also be configured to use boot information from a +DHCP server. + +/para + /sect3 + +!-- comment this out for now, since there is no content + sect3 titleBoot parameters/title +para +Boot parameters for ppc64el + +FIXME: add some useful content here + +/para + /sect3 +-- + + /sect2 Since petitboot runs inside a running linux kernel, that only shifts the problem of booting that linux kernel :) Samuel -- 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/20150412182233.GD2969@type
Re: Help with the arm64 and ppc64el installation-guides needed
Holger Wansing, le Sat 11 Apr 2015 20:22:49 +0200, a écrit : supports-floppy-boot - I think that arch has no floppy support Does ppc64el supports booting from a USB stick? Samuel -- 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/20150412183622.GF2969@type
Re: Help with the arm64 and ppc64el installation-guides needed
Ben Hutchings, le Sun 12 Apr 2015 20:27:29 +0100, a écrit : On Sun, 2015-04-12 at 20:45 +0200, Samuel Thibault wrote: Ben Hutchings, le Sun 12 Apr 2015 00:35:33 +0100, a écrit : On Sat, 2015-04-11 at 20:22 +0200, Holger Wansing wrote: supports-smp-sometimes - that generation of cpu will most likely fully support smp, right? [...] Yes. That's not the question here, see the bit of documentation that it enables: it's whether the *kernel* supports SMP by default, through SMP-alternatives, in a separate image, or not in any shipped image. There is only one kernel flavour, which of course supports SMP. I don't think SMP-alternatives exist on anything but x86 and ARM, unfortunately. Ok, thanks. By the way, is this correctly documented for armhf? Both of the armhf kernel flavours support SMP with SMP-alternatives. Apparently nobody updated build/arch-options/armhf in that regard. Note that smp_config_section and smp_config_option should also be set (they are the section and option that should be used to enable SMP when configuring Linux). Samuel -- 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/20150412200402.GL2969@type
Re: Help with the arm64 and ppc64el installation-guides needed
On 2015-04-12 20:22, Samuel Thibault wrote: Hello, Mmm, the following looks like a useless addition: Holger Wansing, le Sat 11 Apr 2015 17:13:06 +0200, a écrit : Index: en/boot-installer/powerpc.xml === --- en/boot-installer/powerpc.xml (Revision 69729) +++ en/boot-installer/powerpc.xml (Arbeitskopie) @@ -283,3 +283,41 @@ /para /sect2 + + sect2 arch=ppc64el titleBooting a ppc64el machine/title +para + +How to boot a ppc64el machine: + +/para + + sect3 titlePetitboot/title +para + +Petitboot is a platform independent bootloader based on the Linux kexec. +Petitboot supports loading kernel, initrd and device tree files from +any Linux mountable filesystem, plus can load files from the network +using the FTP, SFTP, TFTP, NFS, HTTP and HTTPS protocols. Petitboot can +boot any operating system that includes kexec boot support. + +/parapara + +Petitboot looks for bootloader configuration files on mountable devices +in the system, and can also be configured to use boot information from a +DHCP server. + +/para + /sect3 + +!-- comment this out for now, since there is no content + sect3 titleBoot parameters/title +para +Boot parameters for ppc64el + +FIXME: add some useful content here + +/para + /sect3 +-- + + /sect2 Since petitboot runs inside a running linux kernel, that only shifts the problem of booting that linux kernel :) Petitboot is the default bootloader on this machine when configured to run Linux. It's the interface the user see when powering up the machine. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- 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/20150412200844.go4...@aurel32.net
Re: Help with the arm64 and ppc64el installation-guides needed
Hi, Holger Wansing li...@wansing-online.de wrote: All that contained in attached patch for review. I forgot to mention the arch specific variables in build/arch-options/ppc64el. There are currently set: # Options below are assembled into one variable 'condition' # in the build scripts fdisk=mac-fdisk.txt;cfdisk.txt network=supports-tftp;supports-bootp;supports-nfsroot boot=supports-floppy-boot;bootable-disk frontend=newt;gtk other=supports-wireless;supports-pcmcia;supports-serial-console smp=supports-smp-sometimes goodies=supports-lang-chooser status=not-checked Probably some of them are not up-to-date: supports-floppy-boot - I think that arch has no floppy support supports-wireless - is there wireless hardware available? supports-smp-sometimes - that generation of cpu will most likely fully support smp, right? ... maybe some more ... Can someone on debian-powerpc give info on that? Holger -- Created with Sylpheed 3.2.0 under D E B I A N L I N U X 7 . 0 W H E E Z Y ! Registered Linux User #311290 - https://linuxcounter.net/ -- 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/20150411202249.d840b1199c45e272a4316...@wansing-online.de
Re: Help with the arm64 and ppc64el installation-guides needed
Hi, Holger Wansing li...@wansing-online.de wrote: Hi, Holger Wansing li...@wansing-online.de wrote: All that contained in attached patch for review. I forgot to mention the arch specific variables in build/arch-options/ppc64el. And: is there support for the graphical installer? As far as I can see, the images do not contain the graphical installer. So that should be set to NO. Holger -- Created with Sylpheed 3.2.0 under D E B I A N L I N U X 7 . 0 W H E E Z Y ! Registered Linux User #311290 - https://linuxcounter.net/ -- 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/20150411212037.b8353ac0ac99bd8c3508b...@wansing-online.de
Re: Help with the arm64 and ppc64el installation-guides needed
Hi, Samuel Thibault sthiba...@debian.org wrote: Breno Leitao, le Fri 10 Apr 2015 17:44:01 -0300, a écrit : It is still on my github repository. Can you import it? Uh. I requested this very kind of information in september and november, why wasn't this work (done in december) ever submitted before? We can integrate it in the installation manual, but it will most probably not get translated for the release... Yeah, it's a shame this has not been presented earlier! I'll however be unable to integrate things like blablabla (sic)... The blablabla is indeed only a placeholder which gets removed in a later commit. If noone objects, I could create one single patch out of that for a review here. Holger -- Created with Sylpheed 3.2.0 under D E B I A N L I N U X 7 . 0 W H E E Z Y ! Registered Linux User #311290 - https://linuxcounter.net/ -- 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/20150411100126.b62e9543f4975d4a861b3...@wansing-online.de
Re: Help with the arm64 and ppc64el installation-guides needed
Hi, Holger Wansing li...@wansing-online.de wrote: Samuel Thibault sthiba...@debian.org wrote: Breno Leitao, le Fri 10 Apr 2015 17:44:01 -0300, a écrit : It is still on my github repository. Can you import it? Uh. I requested this very kind of information in september and november, why wasn't this work (done in december) ever submitted before? We can integrate it in the installation manual, but it will most probably not get translated for the release... Yeah, it's a shame this has not been presented earlier! I'll however be unable to integrate things like blablabla (sic)... The blablabla is indeed only a placeholder which gets removed in a later commit. Sorry, I did not noticed there were several blablabla, only saw the first one in preparing. So there is still some content missing indeed, as Samuel mentioned! But we have several empty sections for other archs or d-i modules too... If noone objects, I could create one single patch out of that for a review here. So here we go. I have merged Brenos changings in a local tree, and additionally to that: in build/entities/common.ent there was the name of the architecture missing. So what's the exact pronunciation of that arch? (for powerpc we have PowerPC for example) Is there some special form, or simply ppc64el? In Supported hardware Breno has Power Systems as arch name. ??? The ports page on https://www.debian.org/ports/ lists https://wiki.debian.org/ppc64el/ as basic info page for the ppc64el port, and there is no mention of Power Systems... Also, in Instructions for Netboot installation under preparing there is the term PowerLinux machine. This all should be harmonized to one term. commented out Boot parameters for ppc64el in Booting the installer, since there is no content commented out Updating PowerVM hypervisor in Pre-Installation Hardware and Operating System Setup, since there is no content some small fixes (file name.img - file_name.img) Add some blank lines for document structure. Convert list in Supported Hardware - Machines into itemizedlist. All that contained in attached patch for review. The manual builds fine with it. Holger -- Created with Sylpheed 3.2.0 under D E B I A N L I N U X 7 . 0 W H E E Z Y ! Registered Linux User #311290 - https://linuxcounter.net/ Index: build/arch-options/ppc64el === --- build/arch-options/ppc64el (Revision 69729) +++ build/arch-options/ppc64el (Arbeitskopie) @@ -2,9 +2,9 @@ # the 'ppc64el' architecture # It is sourced by the build scripts -archspec=powerpc;not-s390;not-x86 -arch_listname=powerpc -arch_porturl=powerpc +archspec=ppc64el;not-s390;not-x86 +arch_listname=ppc64el +arch_porturl=ppc64el # TODO: update # This is coming from the lowmem package minimum_memory=32 Index: build/templates/docstruct.ent === --- build/templates/docstruct.ent (Revision 69729) +++ build/templates/docstruct.ent (Arbeitskopie) @@ -136,6 +136,7 @@ !ENTITY module-s390-zipl-installer.xml SYSTEM ##SRCPATH##/using-d-i/modules/s390/zipl-installer.xml !ENTITY module-powerpc-yaboot-installer.xml SYSTEM ##SRCPATH##/using-d-i/modules/powerpc/yaboot-installer.xml !ENTITY module-powerpc-quik-installer.xml SYSTEM ##SRCPATH##/using-d-i/modules/powerpc/quik-installer.xml + !ENTITY module-powerpc-grub-installer.xml SYSTEM ##SRCPATH##/using-d-i/modules/powerpc/grub-installer.xml !ENTITY module-sparc-silo-installer.xmlSYSTEM ##SRCPATH##/using-d-i/modules/sparc/silo-installer.xml !ENTITY module-arm-flash-kernel-installer.xmlSYSTEM ##SRCPATH##/using-d-i/modules/arm/flash-kernel-installer.xml !ENTITY module-nobootloader.xml SYSTEM ##SRCPATH##/using-d-i/modules/nobootloader.xml Index: build/entities/urls.ent === --- build/entities/urls.ent (Revision 69729) +++ build/entities/urls.ent (Arbeitskopie) @@ -311,6 +311,8 @@ !ENTITY url-powerpc-bootx http://penguinppc.org/projects/bootx/; +!ENTITY url-ibm-powerkvm + https://www.ibm.com/developerworks/linux/tutorials/l-ibm-powerkvm-system-bring-up/; !-- ** mips links -- Index: build/entities/common.ent === --- build/entities/common.ent (Revision 69729) +++ build/entities/common.ent (Arbeitskopie) @@ -24,7 +24,7 @@ !-- proper nouns for architectures -- !ENTITY arch-title - phrase arch='any-amd64'64-bit PC/phrasephrase arch='arm'ARM/phrasephrase arch='hppa'PA-RISC/phrasephrase arch='any-i386'32-bit PC/phrasephrase
Re: Help with the arm64 and ppc64el installation-guides needed
On Sat, 2015-04-11 at 17:13 +0200, Holger Wansing wrote: Hi, Holger Wansing li...@wansing-online.de wrote: Samuel Thibault sthiba...@debian.org wrote: Breno Leitao, le Fri 10 Apr 2015 17:44:01 -0300, a écrit : It is still on my github repository. Can you import it? Uh. I requested this very kind of information in september and november, why wasn't this work (done in december) ever submitted before? We can integrate it in the installation manual, but it will most probably not get translated for the release... Yeah, it's a shame this has not been presented earlier! I'll however be unable to integrate things like blablabla (sic)... The blablabla is indeed only a placeholder which gets removed in a later commit. Sorry, I did not noticed there were several blablabla, only saw the first one in preparing. So there is still some content missing indeed, as Samuel mentioned! But we have several empty sections for other archs or d-i modules too... If noone objects, I could create one single patch out of that for a review here. So here we go. I have merged Brenos changings in a local tree, and additionally to that: in build/entities/common.ent there was the name of the architecture missing. So what's the exact pronunciation of that arch? (for powerpc we have PowerPC for example) Is there some special form, or simply ppc64el? In Supported hardware Breno has Power Systems as arch name. ??? The ports page on https://www.debian.org/ports/ lists https://wiki.debian.org/ppc64el/ as basic info page for the ppc64el port, and there is no mention of Power Systems... Also, in Instructions for Netboot installation under preparing there is the term PowerLinux machine. This all should be harmonized to one term. [...] Based on http://openpowerfoundation.org/technical/technical-resources/technical-specifications/ I think it's 'PowerPC 64-bit little-endian', or 'PowerISA little-endian'. However, comparing with the way we've named other architectures, '64-bit PowerPC (little-endian)' would be more consistent. Ben. -- Ben Hutchings compatible: Gracefully accepts erroneous data from any source signature.asc Description: This is a digitally signed message part
Re: Help with the arm64 and ppc64el installation-guides needed
On Sat, Apr 11, 2015 at 5:44 AM, Sandeep G.R wrote: I have a sid PPC64 from http://ftp.de.debian.org/debian-ports running on Freescale Powerpc. Is their PPC64(Big-Endian) for Jessie similarly? The PPC64 port didn't get added to jessie, if you want jessie you'll need to switch to ppc64el. If you want PPC64 big-endian, stick to debian-ports unstable. Some info about the port is here: https://wiki.debian.org/PPC64 -- bye, pabs https://wiki.debian.org/PaulWise -- 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/CAKTje6FNM9Hc7pyAJsCO679_WBiqbi-W0P8w6u6WgaB8xyh=t...@mail.gmail.com
Re: Help with the arm64 and ppc64el installation-guides needed
On Sat, 2015-04-11 at 20:22 +0200, Holger Wansing wrote: Hi, Holger Wansing li...@wansing-online.de wrote: All that contained in attached patch for review. I forgot to mention the arch specific variables in build/arch-options/ppc64el. There are currently set: # Options below are assembled into one variable 'condition' # in the build scripts fdisk=mac-fdisk.txt;cfdisk.txt network=supports-tftp;supports-bootp;supports-nfsroot boot=supports-floppy-boot;bootable-disk frontend=newt;gtk other=supports-wireless;supports-pcmcia;supports-serial-console smp=supports-smp-sometimes goodies=supports-lang-chooser status=not-checked Probably some of them are not up-to-date: supports-floppy-boot - I think that arch has no floppy support supports-wireless - is there wireless hardware available? Current hardware is mostly datacentre type stuff where wireless networking is not likely to be used. In any case, none of the PowerPC architectures seem to have useful wireless drivers in the installer (only PCMCIA wireless drivers, for some reason). supports-smp-sometimes - that generation of cpu will most likely fully support smp, right? [...] Yes. Ben. -- Ben Hutchings compatible: Gracefully accepts erroneous data from any source signature.asc Description: This is a digitally signed message part
Re: Help with the arm64 and ppc64el installation-guides needed
hi Karsten, On 04/09/2015 01:13 PM, Karsten Merker wrote: Hello everybody, the release date for Jessie is near, but the installation-guide does not seem to contain any arm64/ppc64el-specific information yet. We have created this installation guide, but unfortunatelly it was not integrated yet. It is still on my github repository. Can you import it? https://github.com/leitao/installation-guide -- 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/55283611.7000...@br.ibm.com
Re: Help with the arm64 and ppc64el installation-guides needed
Hi Karsten, I have a sid PPC64 from http://ftp.de.debian.org/debian-ports running on Freescale Powerpc. Is their PPC64(Big-Endian) for Jessie similarly? On Fri, Apr 10, 2015 at 2:44 PM, Breno Leitao bren...@br.ibm.com wrote: hi Karsten, On 04/09/2015 01:13 PM, Karsten Merker wrote: Hello everybody, the release date for Jessie is near, but the installation-guide does not seem to contain any arm64/ppc64el-specific information yet. We have created this installation guide, but unfortunatelly it was not integrated yet. It is still on my github repository. Can you import it? https://github.com/leitao/installation-guide -- 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/55283611.7000...@br.ibm.com -- *Thanks Regards,* *Sandeep G R*
Re: Help with the arm64 and ppc64el installation-guides needed
Hello, Breno Leitao, le Fri 10 Apr 2015 17:44:01 -0300, a écrit : On 04/09/2015 01:13 PM, Karsten Merker wrote: Hello everybody, the release date for Jessie is near, but the installation-guide does not seem to contain any arm64/ppc64el-specific information yet. We have created this installation guide, but unfortunatelly it was not integrated yet. It is still on my github repository. Can you import it? Uh. I requested this very kind of information in september and november, why wasn't this work (done in december) ever submitted before? We can integrate it in the installation manual, but it will most probably not get translated for the release... I'll however be unable to integrate things like blablabla (sic)... Samuel -- 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/20150410222458.gd4...@type.youpi.perso.aquilenet.fr
Re: Help with the arm64 and ppc64el installation-guides needed
On Sat, Apr 11, 2015 at 12:24:58AM +0200, Samuel Thibault wrote: Hello, Breno Leitao, le Fri 10 Apr 2015 17:44:01 -0300, a écrit : On 04/09/2015 01:13 PM, Karsten Merker wrote: Hello everybody, the release date for Jessie is near, but the installation-guide does not seem to contain any arm64/ppc64el-specific information yet. We have created this installation guide, but unfortunatelly it was not integrated yet. It is still on my github repository. Can you import it? Uh. I requested this very kind of information in september and november, why wasn't this work (done in december) ever submitted before? We can integrate it in the installation manual, but it will most probably not get translated for the release... I'll however be unable to integrate things like blablabla (sic)... Samuel Also, most of the content is oriented towards updating the machine software itself, not Debian. How does one install Debian on bare-metal, using petitboot? How does one install Debian as a KVM guest with SLOF? How about Debian on a LPAR on PowerVM? Which systems would support it in that mode? Cascardo. signature.asc Description: Digital signature
