Bug#782378: marked as done (installation-report: Jessie-RC on DELL notebook)
Your message dated Sun, 12 Apr 2015 13:24:33 +0200 with message-id <20150412132433.4b73a9b5@s5.lokal> and subject line done has caused the Debian Bug report #782378, regarding installation-report: Jessie-RC on DELL notebook to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 782378: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.58 Severity: wishlist Dear Maintainer, this wa a flawless installation, wishlist only. - -- Package-specific info: Boot method: USB Image version: http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso, 2015-04-08 Date: 2015-04-11, about 7.00 h to 9.00 h Machine: Dell Latitude E 4300 Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on /dev/mmcblk0p1 btrfs 14647296 4650552 9713976 33% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 3888565988382868 2% /run tmpfs tmpfs 972132 140971992 1% /dev/shm tmpfs tmpfs 5120 4 5116 1% /run/lock tmpfs tmpfs 972132 0972132 0% /sys/fs/cgroup /dev/mmcblk0p2 btrfs 146483205072 14369040 1% /home /dev/sda3 xfs1038336 64568973768 7% /boot tmpfs tmpfs 194428 4194424 1% /run/user/119 tmpfs tmpfs 194428 20194408 1% /run/user/1000 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [o] Detect network card:[o] Configure network: [o] Detect CD: [o] Load installer modules: [o] Clock/timezone setup: [o] User/password setup:[o] Detect hard drives: [o] Partition hard drives: [o] Install base system:[o] Install tasks: [o] Install boot loader:[o] Overall install:[o] Comments/Problems: The last grub-update disabled my 32-bit testing-system. Now I installed newly on a low-cost 32GB-SD-card, also with compressed btrfs, GNOME and Cinnamon desktops. It seems to do quite well so far. Installation itself was quite quick, but defragmenting/recompressing everything takes some time, it is probably not recommended to do it this way. - -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="8 (jessie) - installer build 20150408-00:04" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux e4300 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) lspci -knn: Subsystem: Dell Device [1028:024d] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) lspci -knn: Subsystem: Dell Device [1028:024d] lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07) lspci -knn: Subsystem: Dell Device [1028:024d] lspci -knn: 00:03.0 Communication controller [0780]: Intel Corporation Mobile 4 Series Chipset MEI Controller [8086:2a44] (rev 07) lspci -knn:Subsystem: Dell Device [1028:024d] lspci -knn: 00:03.2 IDE interface [0101]: Intel Corporation Mobile 4 Series Chipset PT IDER Controller [8086:2a46] (rev 07) lspci -knn:Subsystem: Dell Device [1028:024d] lspci -knn: Kernel driver in use: ata_generic lspci -knn: 00:03.3 Serial controller [0700]: Intel Corporation Mobile 4 Series Chipset AMT SOL Redirection [8086:2a47] (rev 07) lspci - -knn: Subsystem: Dell Device [1028:024d] lspci -knn: Kernel driver in use: serial lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82567LM Gigabit Network Connection [8086:10f5] (rev 03) lspci -knn: Subsystem: Dell Device [10
Re: Help with the arm64 and ppc64el installation-guides needed
On Sat, Apr 11, 2015 at 9:53 PM, Paul Wise 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: Hints for d-i jessie RC3, part 2
Ivo De Decker wrote: > On Thu, Apr 09, 2015 at 11:09:13PM +0200, Cyril Brulebois wrote: > > # no objections for d-i (kfreebsd-specific), but please check with BSD > > # guys (cc'd) before the matching unblock: > > unblock-udeb kfreebsd-10/10.1~svn274115-4 > > Added all of these. For kfreebsd, the unblock is still needed. Please feel free to unblock, it has security fixes only. Thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150412133415.ga92...@pyro.eu.org
d-i talk at mini DebConf Lyon 2015
Hi people, I've just given a lightning talk about d-i at the mini DebConf in Lyon. You can find the slides here: https://people.debian.org/~kibi/talks/2015-04-12-Lyon-mini-DebConf--lightning-talk.pdf Mraw, KiBi. signature.asc Description: Digital signature
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 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-boot-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
Bug#782461: PPC - PowerBook G4 Jessie test install - successful
Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/jessie_di_rc2/powerpc/iso-cd/debian-jessie-DI-rc2-powerpc-netinst.iso Date: Sat Apr 11 22:00:00 PDT 2015 Machine: PowerBook G4 12" Aluminum Processor: 32-bit ppc 1GHz PowerBook6,2 Memory: 768 MB Partitions: /dev/sda #type name length base ( size ) system /dev/sda1 Apple_partition_map Apple63 @ 1( 31.5k) Partition map /dev/sda2 Apple_Bootstrap untitled 1954 @ 64 (977.0k) NewWorld bootblock /dev/sda3 Apple_UNIX_SVR2 untitled 74837891 @ 2018 ( 35.7G) Linux native /dev/sda4 Apple_UNIX_SVR2 swap3300250 @ 74839909 ( 1.6G) Linux swap /dev/sda5 Apple_Free Extra 1 @ 78140159 ( 0.5k) Free space Block size=512, Number of Blocks=78140160 DeviceType=0x0, DeviceId=0x0 Output of lspci -knn (or lspci -nn): :00:0b.0 Host bridge [0600]: Apple Inc. UniNorth 2 AGP [106b:0034] Kernel driver in use: agpgart-uninorth :00:10.0 VGA compatible controller [0300]: NVIDIA Corporation NV34M [GeForce FX Go5200] [10de:0329] (rev a1) Subsystem: NVIDIA Corporation Powerbook G4 [10de:0010] Kernel driver in use: nouveau 0001:10:0b.0 Host bridge [0600]: Apple Inc. UniNorth 2 PCI [106b:0035] 0001:10:12.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03) Subsystem: Apple Inc. AirPort Extreme [106b:004e] Kernel driver in use: b43-pci-bridge 0001:10:17.0 Unassigned class [ff00]: Apple Inc. KeyLargo/Intrepid Mac I/O [106b:003e] Kernel driver in use: macio 0001:10:18.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f] 0001:10:19.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f] 0001:10:1a.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f] Kernel driver in use: ohci-pci 0001:10:1b.0 USB controller [0c03]: NEC Corporation OHCI USB Controller [1033:0035] (rev 43) Subsystem: NEC Corporation USB Controller [1033:0035] Kernel driver in use: ohci-pci 0001:10:1b.1 USB controller [0c03]: NEC Corporation OHCI USB Controller [1033:0035] (rev 43) Subsystem: NEC Corporation USB Controller [1033:0035] Kernel driver in use: ohci-pci 0001:10:1b.2 USB controller [0c03]: NEC Corporation uPD72010x USB 2.0 Controller [1033:00e0] (rev 04) Subsystem: NEC Corporation uPD72010x USB 2.0 Controller [1033:00e0] Kernel driver in use: ehci-pci 0002:20:0b.0 Host bridge [0600]: Apple Inc. UniNorth 2 Internal PCI [106b:0036] 0002:20:0d.0 Unassigned class [ff00]: Apple Inc. UniNorth/Intrepid ATA/100 [106b:003b] Kernel driver in use: pata-pci-macio 0002:20:0e.0 FireWire (IEEE 1394) [0c00]: Apple Inc. UniNorth 2 FireWire [106b:0031] (rev 81) Subsystem: Apple Inc. iBook G4 2004 [106b:5811] Kernel driver in use: firewire_ohci 0002:20:0f.0 Ethernet controller [0200]: Apple Inc. UniNorth 2 GMAC (Sun GEM) [106b:0032] (rev 80) Kernel driver in use: gem Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Smooth install - I just hit return at the CD "boot: " prompt, and almost everything worked as I would expect. It was a little odd that the background color was red through almost the entire install - I think it changed to blue right at the end. The d-i was not used to install an initial desktop; after the first reboot, tasksel was run manually, and the MATE desktop installed - it works very well, escpecially given the age of the system. A big "Thank You" to everyone involved in putting time and effort into keeping this architecture going. Initially I tried installing to an external USB drive, but the boot loader refused to install at the end of the installation process - there was a message about USB drive booting not being supported on this system. As Wheezy was on the internal drive, I tried to configure its yaboot.conf manually to boot the mostly installed Jessie on the external drive. I've had some luck on other archtitectures with this kind of thing in the past. Unfortunately, my lack of yaboot knowledge resulted in X11 support on the Wheezy install becoming unstable, and I didn't get the external drive booting, either. At that point I thought trying a Jessie install to the internal drive was the best thing to do. So far, the system actually seems more stable with Jessie than it di
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 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
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 @@ > > > > + > + Booting a ppc64el machine > + > + > +How to boot a ppc64el machine: > + > + > + > + Petitboot > + > + > +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. > + > + > + > +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. > + > + > + > + > + > + > + Since petitboot runs inside a running linux kernel, that only shifts the problem of booting that linux kernel :) Samuel -- To UNSUBSCRIBE, email to debian-boot-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 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-boot-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 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-boot-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
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-boot-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-boot-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-boot-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-boot-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
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: Hints for d-i jessie RC3, part 2
Hi, On Sun, Apr 12, 2015 at 02:34:42PM +0100, Steven Chamberlain wrote: > > Added all of these. For kfreebsd, the unblock is still needed. > > Please feel free to unblock, it has security fixes only. Unblocked. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150412195935.gb15...@ugent.be
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-boot-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 @@ > > > > > > > > + > > + Booting a ppc64el machine > > + > > + > > +How to boot a ppc64el machine: > > + > > + > > + > > + Petitboot > > + > > + > > +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. > > + > > + > > + > > +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. > > + > > + > > + > > + > > + > > + > > + > > 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-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150412200844.go4...@aurel32.net
Bug#782305: ask for keyboard layout before asking for password
Hi :) On Fri, 10 Apr 2015 14:00:20 +0200 Samuel Thibault wrote: > *I* know what bépo is. But ask people installing Debian, they won't > know. Same for dvorak, Norwegian dvorak, etc. etc. Maybe they should … if they have a chance to see "bépo/dvorak" some where. > > Really, please read the bug reports I've mentioned. We've already had > this very discussion several times, no need to repeat what has been > already said, and let's just move on with the compromise I have > suggested. Done. Just a point, you can't say adding all layouts will confuse users. Because, for some (ok, few) users it's mre complex to install Debian with a azerty layout … (username, password, hostname, domain name, Logical Volume name >6 … arg, … …) than other distributions. We are not more stupid than Ubuntu's users. It is the fact of hiding information that makes us stupid (just take a look on many new gui … firefox, gnome, …). Anyway, if stats/experiences shows adding dialog box is too complex, Debian has a really good "Expert install" for that :) For the size of the non-standard layouts, there is absolutely no other alternate way to add it? Only for the cd iso (or the dvd) for example? Gardouille-kun signature.asc Description: OpenPGP digital signature
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-boot-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
Bug#782305: ask for keyboard layout before asking for password
Hello, Gardouille, le Sun 12 Apr 2015 22:08:32 +0200, a écrit : > Just a point, you can't say adding all layouts will confuse users. We *have* seen that in the past. Really. The fact that Ubuntu and others go that way doesn't make it good. > Because, for some (ok, few) users it's mre complex to install Debian > with a azerty layout … (username, password, hostname, domain name, > Logical Volume name >6 … arg, … …) than other distributions. That's a non-argument. Not only we are talking about few users, but also those users do know very well that they are using a non-standard keyboard, and will know they should look for an ergonomic variant somewhere. Thus the proposal to add an "ergonomic" choice. > For the size of the non-standard layouts, there is absolutely no other > alternate way to add it? Only for the cd iso (or the dvd) for example? Again, please read my compromise proposal. This is precisely the kind of thing I'm suggesting: the gtk images, which happens to be what most CD/DVD images include. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150412211043.gb2...@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-boot-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 (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 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-boot-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 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 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-boot-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
On Sun, Apr 12, 2015 at 6:43 PM, Lennart Sorensen 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-boot-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
