Bug#825110: yaboot vs grub: metadata_csum and 64bit ext4
tags 825110 + pending unblock 825110 by 610206 thanks On 05/31/2016 04:35 AM, Mathieu Malaterre wrote: > Here is the short explanation on why I played with the `pending` tag. > , > Switching from yaboot to grub for d-i is a great news. However I > feared two things, with the current applied patch for #825110 we are > currently restricting users solely for yaboot user This patch just allows yaboot to read files, it does not restrict grub in any way. > (I did not understand why the switch was done only for 'powerpc' and 'ppc64' > was > skipped). Yaboot does not get installed on ppc64 nor on ppc64el. > This would also need to be reverted once we fully move to grub only in d-i. There is a lot of stuff to do to get to that point. Milan signature.asc Description: OpenPGP digital signature
Bug#825110: /pci@f400000/ata-6@d/@0:3,/boot/vmlinux: Unknown or corrupt
On 05/30/2016 12:20 PM, Lennart Sorensen wrote: > On Mon, May 30, 2016 at 12:17:19AM -0400, Milan Kupcevic wrote: >> affects 825110 yaboot >> tags 825110 pending >> thanks >> >> Yaboot is not able to load files from a partition with metadata_csum and >> 64bit ext4 features enabled. > [...] > Of course if ext4 is being created by default in 64bit mode these days > (I have no idea), then the installer may need to be taught to not do > that for whatever filesystem /boot is going in. > It seems ext4 is being created by default with 64bit and metadata_csum features since stretch beta 6 d-i release. A separate /boot partition formatted as ext3 would be a solution; as it was for some time before yaboot got support for ext4. Instead of doing separate /boot we might be better off to adjust newworld partition recipe to accommodate grub installation while disabling d-i 64bit and metadata_csum features on powerpc to allow for installation of yaboot.[0] Once we transition to grub we can get rid of yaboot-installer together with ext4 feature limitations. Mathieu is volunteering to do some work in this regard.[1] Milan [0] https://anonscm.debian.org/cgit/d-i/partman-ext3.git/commit/?id=f87dc92157262de1ad8dd3f2343436f08271b4dc [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610206#14 signature.asc Description: OpenPGP digital signature
Bug#825110: /pci@f400000/ata-6@d/@0:3,/boot/vmlinux: Unknown or corrupt
affects 825110 yaboot tags 825110 pending thanks Yaboot is not able to load files from a partition with metadata_csum and 64bit ext4 features enabled. Milan
Bug#783982: D-i: preseed from floppy no longer works !
On 05/01/2015 06:09 PM, Alexey Eromenko wrote: [...] Debian 8 (mini-)kernel (inside amd64-DVD) does NOT see /dev/fd0 ! (part of debian-installer); This works just fine with Debian 6 and 7 ! Post-install Debian 8 kernel _does_ see /dev/fd0, can loop-mount and can read files from it. (after installing from Debian 8 amd64-DVD), so no problem here. The natural question: Are those kernels different ? (I always assumed it is the *same* kernel) It seems the mini-kernel does not provide me with /proc/config.gz, so I have no clue what's included and what's excluded. How can I check ? The kernel is the same but the number of modules included in d-i initrd.gz is reduced to bare minimum needed for d-i to boot up. The list of included modules is different on cdrom d-i image, netboot d-i image, and hd-media d-i image. One way to check it out would be to unpack the d-i image initrd.gz and look what is in there. The /proc/config.gz would not help as it would provide info about what is compiled, but not what is included in d-i. The fact that floppy works in final installation likely means the module is in fact compiled but not included in d-i image. Therefore, the way to go would be to figure out which module is needed to provide access to floppy on your platform and then work with kernel team on inclusion of the module in in the d-i initrd. Milan signature.asc Description: OpenPGP digital signature
Bug#781936: rootskel (d-i): G5 fans run full speed
Bug fix is pending upload: http://anonscm.debian.org/cgit/d-i/rootskel.git/commit/?id=73d613f581ae06b35ca21119f914210571cb7b11 Milan -- 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/5521491f.Gm9v/wgdw8ch8kl5%mi...@physics.harvard.edu
Re: Removing partman-ext2r0
On 12/15/2013 07:43 AM, Martin Michlmayr wrote: * Milan Kupcevic mi...@physics.harvard.edu [2013-12-14 13:11]: If I remember it right, Pegasos II needs revision 0 ext2 filesystem to boot off. Debian is still running and installing fine on Pegasos II machines. I did a quick search and couldn't find anything about ext2 rev 0 and Pegasos II. Do you have such a machine or know someone who does so someone can check? I just checked it up. Pegasos wants ext2, does not have to be revision 0. Therefore, no need for partman-ext2r0 package as far as Pegasos is concerned. Milan signature.asc Description: OpenPGP digital signature
Re: Removing partman-ext2r0
On 12/14/2013 05:33 AM, Martin Michlmayr wrote: I just removed support for Cobalt devices from the installer as these devices are extremely old now and there are problems with the boot loader. We still have partman-ext2r0. This package was created to generate a revision 0 ext2 filesystem, which is required to boot on 2 systems: Netwinder (ARM) and Cobalt (MIPS). Neither Netwinder nor Cobalt devices are supported by the installer anymore, so I suggest we remove partman-ext2r0. Any objections? If I remember it right, Pegasos II needs revision 0 ext2 filesystem to boot off. Debian is still running and installing fine on Pegasos II machines. Milan signature.asc Description: OpenPGP digital signature
Re: New partman-basicfilesystems debconf templates
On 07/27/2013 02:23 AM, Christian PERRIER wrote: Hello Milan, I noticed that you added new templates to partman-basicfilesystems for the following: * Warn if bootable partition is not ext2 on Pegasos machines. Closes: #717511 I'll turn these templates to translatable (they are not, yet) and mark them for sublevel 4 or 5 (belong to less common architectures). However, before doing that, I'd like to use the same wording than other similar templates (so that translations can be re-used). Particularly, the following: Template: partman-basicfilesystems/boot_not_first_partition Type: boolean Description: Go back to the menu and correct this problem? Your boot partition is not located on the first partition of your hard disk. This is needed by your machine in order to boot. Please go back and use your first partition as a boot partition. . If you do not go back to the partitioning menu and correct this error, the partition will be used as is. This means that you may not be able to boot from your hard disk. We already have such a template, but it says on the first PRIMARY partition. Would it be wrong to add this primary word to the templates you added? The partition table on this platform has no concept of primary and secondary class of partitions. Therefore, the word primary is not technically correct if you contrast it with the same word as used in DOS partition table concept. But the word itself does not change the message to the user that the partition should be first. FYI I've found the same message in templates of partman-ext2r0 and partman-ext3 packages, where I actually took the text from. The best, Milan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51f41d90.3050...@physics.harvard.edu
Bug#717511: Kernel does not start up on Pegasos-2
On 07/22/2013 02:42 PM, Ben Hutchings wrote: On Mon, Jul 22, 2013 at 09:59:18PM +0400, Pavel Fedin wrote: Hello, Milan. 22 июля 2013 г., 5:23:34, you wrote: User did not let installer to create default partition layout but manually created incorrect one, or installed on a previously created partitions and used ext4 and ext3 file-systems. Yes, exactly. Actually i agree, there's little to blame in Installer. Only one small thing - nobody told me that my layout (previously worked) became incorrect. Perhaps Installer should warn about it ? Or, we can consider one more corner case. What if i install the whole OS to a single EXT2 partition ? Yes, again, i agree, you may ask Why, EXT2 is outdated and there's cool new EXT4. I have already said - this is corner case. Maybe the installer could warn about a likely broken partition layout after you choose manual layout. It doesn't seem right that if you want to customise layout at all you must remember any machine-specific constraints. Also, this constraint is not documented in the installation manual. Reassigning to installation-guide-powerpc and partman-ext3. Milan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51ee88d0.20...@physics.harvard.edu
Bug#717511: Kernel does not start up on Pegasos-2
Control: notfound 717511 yaboot-installer/1.1.26 On 07/21/2013 08:49 PM, Ben Hutchings wrote: On Sun, 2013-07-21 at 20:36 -0400, Milan Kupcevic wrote: Control: notfound -1 yaboot-installer/1.1.26 On 07/21/2013 04:55 PM, Ben Hutchings wrote: Control: reassign -1 yaboot-installer 1.1.26 On Mon, 2013-07-22 at 00:38 +0400, Pavel Fedin wrote: [...] So, it's not kernel's fault. It seems to be installer fault which does not generate correct vmlinuz image when not using separate /boot partition. vmlinux, i know, is another thing. It's a plain image meant to be ran from GRUB or yaboot. It cannot be run from OFW. So, we can close this, probably with a notification to Installer guys. There is no need to close it. I'm reassigning to the relevant part of the installer. The particular partition/file-system layout reported in this bug report cannot work. This platform does not have a boot loader at all. Sorry, I misunderstood. [...] Installer correctly creates ext2 boot partition and ext4 root partition. [...] Then how did this go wrong? User did not let installer to create default partition layout but manually created incorrect one, or installed on a previously created partitions and used ext4 and ext3 file-systems. Milan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51ec8996.8060...@physics.harvard.edu
Re: Bug#332227: partconf: Exclude CD/DVD drives from partition search
Control: reassign -1 partconf Control: tag -1 +wheezy +pending Control: severity -1 serious Hi Cyril, Patch [0] supplied by Frank Fegert fixes this bug. Can we push partconf 1.41 with this fix in Wheezy r1? It will allow installation of Debian on VIOS virtual drives in LPAR's of IBM Power machines. Milan [0] http://lists.gnu.org/archive/html/bug-parted/2013-02/msg7.html signature.asc Description: OpenPGP digital signature
Bug#702125: 'Invalid device' error on reboot after installation on YDL PowerStation
Package: installation-reports Severity: important -- Package-specific info: Boot method: CD Image version: official netinst wheezy RC1 for powerpc Date: Sat Mar 2 16:13:10 EST 2013 Machine: Quad-Core YDL PowerStation Partitions: Partition Table for /dev/sda ---Starting Ending-Start Number of # Flags Head Sect Cyl ID Head Sect Cyl SectorSectors -- - - - --- --- 1 0x80 641 0 0x41 127 32 32048 14336 2 0x0001 4 0x83 63 32 33554 16384 137422848 3 0x00 127 31 33554 0x05 127 32 35002 137441278 5931010 4 0x0000 0 0x0000 0 0 0 5 0x0001 33555 0x82 127 32 35002 2 5931008 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[E] Comments/Problems: The installation itself went with no errors, but on reboot I've got this error message: Welcome to yaboot version 1.3.16 Enter help to get some basic usage information boot: Linux Please wait, loading kernel... /ht/pci@1/obsidian@1/scsi@0/sd@0,0:2,/boot/vmlinux: Unable to open file, Invalid device boot: -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=7.0 (wheezy) - installer build 20130211 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux debian 3.2.0-4-powerpc64 #1 SMP Debian 3.2.35-2 ppc64 GNU/Linux lspci -knn: :f0:0b.0 PCI bridge [0604]: Apple Inc. CPC945 PCIe Bridge [106b:005b] lspci -knn: :f1:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV535 [Radeon X1650 Series] [1002:71c7] (rev 9e) lspci -knn: Subsystem: PC Partner Limited Device [174b:0840] lspci -knn: :f1:00.1 Display controller [0380]: Advanced Micro Devices [AMD] nee ATI RV535 [Radeon X1650 Series] [1002:71e7] (rev 9e) lspci -knn: Subsystem: PC Partner Limited Device [174b:0841] lspci -knn: 0001:00:01.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-X bridge [1166:0130] (rev b0) lspci -knn: 0001:00:02.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-X bridge [1166:0130] (rev b0) lspci -knn: 0001:00:03.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-Express Bridge [1166:0132] (rev b0) lspci -knn: 0001:00:04.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-Express Bridge [1166:0132] (rev b0) lspci -knn: 0001:00:05.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-Express Bridge [1166:0132] (rev b0) lspci -knn: 0001:00:06.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-Express Bridge [1166:0132] (rev b0) lspci -knn: 0001:00:07.0 PCI bridge [0604]: Advanced Micro Devices [AMD] AMD-8111 PCI [1022:7460] (rev 07) lspci -knn: 0001:00:08.0 ISA bridge [0601]: Advanced Micro Devices [AMD] AMD-8111 LPC [1022:7468] (rev 05) lspci -knn: 0001:00:08.1 IDE interface [0101]: Advanced Micro Devices [AMD] AMD-8111 IDE [1022:7469] (rev 03) lspci -knn: Kernel driver in use: pata_amd lspci -knn: 0001:01:01.0 RAID bus controller [0104]: IBM Obsidian chipset SCSI controller [1014:02bd] (rev 01) lspci -knn: Subsystem: IBM Device [1014:02c1] lspci -knn: Kernel driver in use: ipr lspci -knn: 0001:02:04.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5780 Gigabit Ethernet [14e4:166a] (rev 10) lspci -knn: Subsystem: IBM Device [1014:0329] lspci -knn: Kernel driver in use: tg3 lspci -knn: 0001:02:04.1 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5780 Gigabit Ethernet [14e4:166a] (rev 10) lspci -knn: Subsystem: IBM Device [1014:0329] lspci -knn: Kernel driver in use: tg3 lspci -knn: 0001:05:00.0 PCI bridge [0604]: Texas Instruments XIO2000(A)/XIO2200A PCI Express-to-PCI Bridge [104c:8231] (rev 03) lspci -knn: 0001:06:01.0 USB controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) lspci -knn: Subsystem: NEC Corporation USB [1033:0035] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 0001:06:01.1 USB controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) lspci -knn:
Bug#702125: 'Invalid device' error on reboot after installation on YDL PowerStation
Control: reassign -1 yaboot-installer 1.1.25 Control: tag -1 wheezy pending On 03/02/2013 05:45 PM, Milan Kupcevic wrote: Welcome to yaboot version 1.3.16 Enter help to get some basic usage information boot: Linux Please wait, loading kernel... /ht/pci@1/obsidian@1/scsi@0/sd@0,0:2,/boot/vmlinux: Unable to open file, Invalid device boot: This bug was fixed in yaboot-installer 1.1.26. Milan signature.asc Description: OpenPGP digital signature
Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
On 02/06/2013 10:38 AM, Daniel Baumann wrote: On 02/06/2013 12:55 AM, Don Armstrong wrote: Is it the intention of the Release Managers not to accept a newer version of syslinux into wheezy? [That is, if the CTTE were to decide to require some fix to d-i, we'd also have to override the RMs?] jftr, i never did nor intended to ask for having syslinux 5 in wheezy. what i care about is having it in unstable (for reasons said earlier). Well, the d-i development is happening in sid. Therefore, this upload disrupted the development process of syslinux dependent d-i components that have to end up, but are not yet in wheezy. Milan signature.asc Description: OpenPGP digital signature
Bug#629492: Installing on dual-processor PowerPC system (ex. QuickSilver PowerMac G4) installs non-SMP kernel
On 12/20/2012 05:50 AM, Cyril Brulebois wrote:
reopen 629492
found 629492 1.129
thanks
Hi Milan,
Milan Kupcevic mi...@physics.harvard.edu (06/11/2012):
reassign 629492 base-installer
tags + pending
thanks
diff --git a/debian/changelog b/debian/changelog
index 7712e5e..c015a71 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+base-installer (1.129) UNRELEASED; urgency=low
+
+ * Properly recognize PowerPC SMP machines. Closes: #629492
+
+ -- Milan Kupcevic mi...@physics.harvard.edu Tue, 06 Nov 2012 11:21:07
-0500
+
base-installer (1.128) unstable; urgency=low
* Add support for armhf/vexpress.
diff --git a/kernel/powerpc.sh b/kernel/powerpc.sh
index d8f09d0..b2b9b93 100644
--- a/kernel/powerpc.sh
+++ b/kernel/powerpc.sh
@@ -29,7 +29,7 @@ arch_check_usable_kernel () {
}
arch_get_kernel () {
-CPUS=$(grep -ci ^processor $CPUINFO) || CPUS=1
+CPUS=$(ls /proc/device-tree/cpus/ | grep -ci @[0-9]) || CPUS=1
if [ $CPUS ] [ $CPUS -gt 1 ] \
[ $1 != powerpc64 ] [ $1 != prep ] ; then
SMP=-smp
this was merged into base-installer 1.129, and seems to be responsible
for the build failure, in the test suite:
FAIL powerpc/powermac_newworld.test arch_get_kernel want
'linux-image-powerpc', got 'linux-image-powerpc-smp linux-image-powerpc'
powerpc: 113 passes, 1 failures.
(https://buildd.debian.org/status/fetch.php?pkg=base-installerarch=powerpcver=1.129stamp=1355061770)
It looks to me like this is just a matter of registering the smp
flavour as one of the possible value for kernel-2.6 in
kernel/tests/powerpc/powermac_newworld.test (it's already known as a
usable flavour anyway), but a confirmation would be nice.
Hi Cyril,
The trouble was that there was no support for this kind of processor(s)
detection in the test suite. I just did a commit to base-installer with
test suite support for Open Firmware /cpus directory and added a smp
test. Now the package builds fine and passes all tests in my pbuilder.
M
signature.asc
Description: OpenPGP digital signature
Bug#695058: NO SIGNAL monitor problem..
On 12/03/2012 04:28 PM, Jack Wilborn wrote: I forgot to add that I have an 'NVIDIA GeForce card. I wonder if the change to a VGA display via a cable change is part of the problem. I also wonder if there is some way to get control of the machine before it completes the restart or boot. It responds to CTL-ALT-DEL keys and reboots, but is there any other combination that will just give me control in a command line? If it is a dual head graphic card try to connect the monitor to the other connector. There may be a phantom TV port on this card (with no actual TV connector on it) which gets chosen as the output. You can disable the TV part by passing video=TV-1:d or video=TV-2:d to kernel. You can add these options to append field in yaboot.conf Example: image=/boot/vmlinux label=Linux read-only initrd=/boot/initrd.img append=video=TV-1:d Boot the machine using install DVD. On boot prompt type: rescue64 choose the apropriate options until you get the Enter rescue mode screen, then chose your root partition and choose to execute shell in the root filesystem. You will have the familiar command line environment. You can edit yaboot.conf using vi or nano to add wanted options to append field. You can install openssh-server with intention to log into the machine using ssh after reboot. Type exit, and choose reboot. Milan signature.asc Description: OpenPGP digital signature
yaboot-installer and base-installer need upload
Hi Christian and Cyril, As d-i beta 4 is out, could you please upload yaboot-installer and base-installer? Thanks, Milan signature.asc Description: OpenPGP digital signature
Bug#629492: Installing on dual-processor PowerPC system (ex. QuickSilver PowerMac G4) installs non-SMP kernel
reassign 629492 base-installer
tags + pending
thanks
diff --git a/debian/changelog b/debian/changelog
index 7712e5e..c015a71 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+base-installer (1.129) UNRELEASED; urgency=low
+
+ * Properly recognize PowerPC SMP machines. Closes: #629492
+
+ -- Milan Kupcevic mi...@physics.harvard.edu Tue, 06 Nov 2012 11:21:07 -0500
+
base-installer (1.128) unstable; urgency=low
* Add support for armhf/vexpress.
diff --git a/kernel/powerpc.sh b/kernel/powerpc.sh
index d8f09d0..b2b9b93 100644
--- a/kernel/powerpc.sh
+++ b/kernel/powerpc.sh
@@ -29,7 +29,7 @@ arch_check_usable_kernel () {
}
arch_get_kernel () {
- CPUS=$(grep -ci ^processor $CPUINFO) || CPUS=1
+ CPUS=$(ls /proc/device-tree/cpus/ | grep -ci @[0-9]) || CPUS=1
if [ $CPUS ] [ $CPUS -gt 1 ] \
[ $1 != powerpc64 ] [ $1 != prep ] ; then
SMP=-smp
Bug#691264: grub-installer: Allow grub installation on IBM Power machines
tags 691264 pending
thanks
On 10/23/2012 02:32 PM, Lennart Sorensen wrote:
On Tue, Oct 23, 2012 at 02:03:46PM -0400, Milan Kupcevic wrote:
Partitioning recipe for IBM Power machines already creates PReP
partition for yaboot. If we do check for PReP partition in addition to
/boot/grub to allow grub installer it will make grub the default
bootloader on IBM Power machines for wheezy.
Actually, we can enable grub-installer on IBM Power machines in wheezy.
Yaboot-installer will stay the default option because it has higher
menu-item priority. Grub-installer will become an optional item that
user can choose in expert installation mode. In this case the current
partitioning recipe will work for grub, too.
This would be great if we are sure that d-i installs grub with no
issues. I did not test it, so I'm not quite sure.
It does seem a bit late for wheezy. And at least yaboot now seems to
be a version that might actually work. I seem to recall some issues
with ofpathname, but I can't quite remember what they were right now or
whether they were fixed or not. A quick check says that yes indeed in
wheezy the ofpathname issue (bug 607001) was fixed.
Actually given grub is 1.99 in wheezy I think it is safe to say it
won't work in a number of cases. 2.00 fixed some endianess issues with
software raid among other things that matter to powerpc, which is why
I am running grub 2.00 and not 1.99 now. The older versions were OK
with the old mdraid format, but not the 1.x format which is of course
now the default in debian's installer.
diff --git a/debian/changelog b/debian/changelog
index 204cc11..cf478cd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,8 +2,9 @@ grub-installer (1.83) UNRELEASED; urgency=low
* Allow grub installation on PowerPC machines if /boot/grub partition
is present. Closes: #664128
+ * Allow grub installation on IBM Power machines. Closes: #691264
- -- Milan Kupcevic mi...@physics.harvard.edu Mon, 22 Oct 2012 17:39:07 -0400
+ -- Milan Kupcevic mi...@physics.harvard.edu Wed, 24 Oct 2012 09:22:28 -0400
grub-installer (1.82) unstable; urgency=low
diff --git a/debian/isinstallable b/debian/isinstallable
index 89fadb7..c86173f 100755
--- a/debian/isinstallable
+++ b/debian/isinstallable
@@ -15,6 +15,8 @@ case $ARCH in
exit 1
fi
;;
+powerpc/chrp|powerpc/chrp_rs6k|powerpc/chrp_ibm|powerpc/cell)
+ ;;
powerpc/*)
mount | grep on /target/boot/grub 12 || {
log GRUB requires OF bootable partition mounted at /boot/grub on PowerPC systems
diff --git a/grub-installer b/grub-installer
index 7056f11..d709de0 100755
--- a/grub-installer
+++ b/grub-installer
@@ -225,6 +225,8 @@ bootfstype=$(findfstype /boot)
[ -n $bootfstype ] || bootfstype=$(findfstype /)
case $ARCH in
+powerpc/chrp|powerpc/chrp_rs6k|powerpc/chrp_ibm|powerpc/cell)
+;;
powerpc/*)
offs=$(findfs /boot/grub)
[ -n $offs ] || error GRUB requires that the OF partition is mounted in /boot/grub 12
signature.asc
Description: OpenPGP digital signature
Bug#691216: iBook v2 G3, 800MHZ not supported?
On 10/22/2012 10:57 PM, tsch...@nexgo.de wrote: Package: installation-reports Boot method: netinst : CD (external drive), root directory (first disk HFS+) and TFTP Image versions : 1.) debian-wheezy-DI-b3-powerpc-netinst.iso, and 2.a) http://ftp.nl.debian.org/debian/dists/squeeze/main/installer-powerpc/current/images/powerpc/netboot/ and 2.b) Debian GNU/Linux 6.0.6 Squeeze - Official powerpc DVD Binary-1 20120929-17:11 (chksums OK) and 3.) files fron netinst : lenny (5.10 for ppc) Date: 22.10.2012 - 23.10.2012 Machine: iBook v2 G3, 800MHZ, FW, USB, RJ11, RJ45, 384 MB RAM, internal cd-rom defect, OSX 10.3.9 (on second partition). Processor: G3, 800MHZ Memory: 384 MB SDRAM Partitions: /dev/disk0s10 (root directory (first disk HFS+)) /dev/disk0s10 (OSX) pdisk -dump : 1: @ 64 for 23, type = 0x1 2: @ 120 for 36, type = 0x 3: @ 176 for 21, type = 0x701 4: @ 232 for 34, type = 0xf8ff Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: after two lines of boot a No trespassing sign appears vmlinux-files maybe corrupted/not adopted for G3 No Idea, I installed some Linux (ubuntu some years ago without problems (external CD-Rom activated via OpenFirmware)) Thomas Schenk Try to start wheezy installer from an external FireWire CD/DVD drive or a USB memory stick. For more insights see: http://lists.debian.org/503bee2b.10...@physics.harvard.edu and http://lists.debian.org/4fdd55cc.7020...@physics.harvard.edu Milan signature.asc Description: OpenPGP digital signature
Bug#664128: debian-installer: please default to grub-ieee1275 on powerpc instead of yaboot
On 10/23/2012 09:52 AM, Daniel Kahn Gillmor wrote:
On 10/22/2012 05:55 PM, Milan Kupcevic wrote:
We can allow d-i grub installation on powerpc machines for wheezy, but
not make it default.
[...]
Manual creation of the appropriate partition in d-i (/boot/grub) will
enable grub installation in wheezy d-i. Thus, we will be able to
experiment with d-i grub installation on powerpc machines.
ok, this sounds like a good step to me. Are you saying this is present
in the current wheezy beta3 ?
No. It will eventually hit the daily builds soon. See attachment.
Milan
commit cf2fc86abf0fd34963afb49047c21e94a2cde40e
Author: Milan Kupcevic mi...@physics.harvard.edu
Date: Mon Oct 22 17:46:06 2012 -0400
Allow grub installation on PowerPC machines
* Allow grub installation on PowerPC machines if /boot/grub partition
is present. Closes: #664128
diff --git a/debian/changelog b/debian/changelog
index 9105cdb..204cc11 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+grub-installer (1.83) UNRELEASED; urgency=low
+
+ * Allow grub installation on PowerPC machines if /boot/grub partition
+is present. Closes: #664128
+
+ -- Milan Kupcevic mi...@physics.harvard.edu Mon, 22 Oct 2012 17:39:07 -0400
+
grub-installer (1.82) unstable; urgency=low
[ Updated translations ]
diff --git a/debian/isinstallable b/debian/isinstallable
index e66bac1..89fadb7 100755
--- a/debian/isinstallable
+++ b/debian/isinstallable
@@ -15,11 +15,11 @@ case $ARCH in
exit 1
fi
;;
-powerpc/chrp_pegasos)
- ;;
powerpc/*)
- log GRUB not yet usable on PowerPC systems other than Pegasos/Efika
- exit 1
+ mount | grep on /target/boot/grub 12 || {
+ log GRUB requires OF bootable partition mounted at /boot/grub on PowerPC systems
+ exit 1
+ }
;;
mipsel/loongson-2f)
;;
signature.asc
Description: OpenPGP digital signature
Bug#664128: debian-installer: please default to grub-ieee1275 on powerpc instead of yaboot
clone 664128 -1
retitle -1 Allow grub installation on IBM Power machines
thanks
On 10/23/2012 11:36 AM, Lennart Sorensen wrote:
On Tue, Oct 23, 2012 at 10:18:00AM -0400, Milan Kupcevic wrote:
On 10/23/2012 09:52 AM, Daniel Kahn Gillmor wrote:
On 10/22/2012 05:55 PM, Milan Kupcevic wrote:
We can allow d-i grub installation on powerpc machines for wheezy, but
not make it default.
[...]
Manual creation of the appropriate partition in d-i (/boot/grub) will
enable grub installation in wheezy d-i. Thus, we will be able to
experiment with d-i grub installation on powerpc machines.
ok, this sounds like a good step to me. Are you saying this is present
in the current wheezy beta3 ?
No. It will eventually hit the daily builds soon. See attachment.
Milan
commit cf2fc86abf0fd34963afb49047c21e94a2cde40e
Author: Milan Kupcevic mi...@physics.harvard.edu
Date: Mon Oct 22 17:46:06 2012 -0400
Allow grub installation on PowerPC machines
* Allow grub installation on PowerPC machines if /boot/grub partition
is present. Closes: #664128
diff --git a/debian/changelog b/debian/changelog
index 9105cdb..204cc11 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+grub-installer (1.83) UNRELEASED; urgency=low
+
+ * Allow grub installation on PowerPC machines if /boot/grub partition
+is present. Closes: #664128
+
+ -- Milan Kupcevic mi...@physics.harvard.edu Mon, 22 Oct 2012 17:39:07
-0400
+
grub-installer (1.82) unstable; urgency=low
[ Updated translations ]
diff --git a/debian/isinstallable b/debian/isinstallable
index e66bac1..89fadb7 100755
--- a/debian/isinstallable
+++ b/debian/isinstallable
@@ -15,11 +15,11 @@ case $ARCH in
exit 1
fi
;;
-powerpc/chrp_pegasos)
-;;
powerpc/*)
-log GRUB not yet usable on PowerPC systems other than Pegasos/Efika
-exit 1
+mount | grep on /target/boot/grub 12 || {
+log GRUB requires OF bootable partition mounted at /boot/grub
on PowerPC systems
+exit 1
+}
;;
mipsel/loongson-2f)
;;
And that would be wrong. That is NOT how grub works on IBM powerpc
machines. That is true of powermac and possible a few other types.
The IBM OF does NOT support filesystems. It executes the ELF binary in
the PReP partition, which can not be mounted.
IBM Firmware does support filesystems, just not the same filesystems as
Macs and Pegasos. IBM Firmware likes FAT and iso9660, Mac wants HFS,
while Pegasos works with ext2, AFFS, and iso9660.
If you put a bootloader on FAT filesystem you could put other meta
information in /ppc/bootinfo.txt file so that IBM Firmware and other IBM
boot management tools can get full textual description and optionally an
icon of the bootable OS. It would make it possible to dual boot Linux
(GRUB) and AIX while choosing which one you want to boot using standard
IBM tools (ie Multiboot menu). We will see if we want to go this way or
we want to keep resetting firmware variables using '/sbin/nvsetenv' on
Linux and 'bootlist' on AIX when we want to reboot into the other OS.
grub-install simply dd's
the grub core image into that partition and that's it. When creating the
image it passes and argument to the grub-mkimage to set which partition
to look at to get the grub modules and config files since in the IBM
case it won't be the boot partition (since it has no filesystem).
Yaboot installer installs yaboot on IBM Power machines exactly the same way.
So please don't make such a wrong change. You will just make life harder
for IBM users.
This will not make life harder nor easier for IBM users. Grub
installation was not offered on IBM Power machines by d-i until now, and
will not be offered after this particular change.
The correct thing to check for on an IBM is that a PReP boot type
partition exists. That is all. It can not be mounted.
For example:
root@rceng03:~# parted
GNU Parted 2.3
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: IBM MBE2147RC (scsi)
Disk /dev/sda: 147GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End SizeType File system Flags
1 1049kB 8389kB 7340kB primary boot, prep
2 8389kB 10.0GB 10.0GB primary raid
3 10.0GB 147GB 137GB primary raid
In this case the setup is RAID1 across sd[abc]2 for / and RAID5 across
sd[abc]3 for LVM.
grub is happily installed to /dev/sda1 (and sdb1 and sdc1 as well for
redundancy) using grub-install. This works.
Thank you for providing information about your experience with grub on
IBM Power machines. After wheezy release we will go forward with
transition from yaboot to grub. Your experience will be valuable for
further discussion about d-i issues
Bug#664128: debian-installer: please default to grub-ieee1275 on powerpc instead of yaboot
tags 691264 -pending thanks On 10/23/2012 01:33 PM, Lennart Sorensen wrote: On Tue, Oct 23, 2012 at 01:06:06PM -0400, Milan Kupcevic wrote: IBM Firmware does support filesystems, just not the same filesystems as Macs and Pegasos. IBM Firmware likes FAT and iso9660, Mac wants HFS, while Pegasos works with ext2, AFFS, and iso9660. If you put a bootloader on FAT filesystem you could put other meta information in /ppc/bootinfo.txt file so that IBM Firmware and other IBM boot management tools can get full textual description and optionally an icon of the bootable OS. It would make it possible to dual boot Linux (GRUB) and AIX while choosing which one you want to boot using standard IBM tools (ie Multiboot menu). We will see if we want to go this way or we want to keep resetting firmware variables using '/sbin/nvsetenv' on Linux and 'bootlist' on AIX when we want to reboot into the other OS. I have never got it to work with a fat filesystem. I have tried on a p710 and a p520. Maybe it worked on older ones. Yaboot installer installs yaboot on IBM Power machines exactly the same way. This will not make life harder nor easier for IBM users. Grub installation was not offered on IBM Power machines by d-i until now, and will not be offered after this particular change. Well it looks like it will if you happen to create the /boot/grub partition, except it won't work that way. So the error message will tell you to do something that won't work. Partitioning recipe for IBM Power machines already creates PReP partition for yaboot. If we do check for PReP partition in addition to /boot/grub to allow grub installer it will make grub the default bootloader on IBM Power machines for wheezy. This would be great if we are sure that d-i installs grub with no issues. I did not test it, so I'm not quite sure. Thank you for providing information about your experience with grub on IBM Power machines. After wheezy release we will go forward with transition from yaboot to grub. Your experience will be valuable for further discussion about d-i issues on IBM Power machines. I will certainly try to help test it at that time. The way I am using it is what grub-install expects on IBM powerpc at this time. I would love to see a working example where you use FAT on an IBM powerpc, because I haven't found any reference to it in any of the documentation or anywhere else, and it has never worked when I tried it. The openfirmware syntax where you specify a file on a filesystem simply never worked on either machine I have here. Seems to work fine on Macs though. I will look up the bootinfo.txt though. Maybe that will provide some hints. Could make grub simpler to work with. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5086dc02.2010...@physics.harvard.edu
Bug#664128: debian-installer: please default to grub-ieee1275 on powerpc instead of yaboot
On 03/15/2012 03:05 PM, Daniel Kahn Gillmor wrote: Please have debian-installer on powerpc default to grub-ieee1275 instead of yaboot. We can allow d-i grub installation on powerpc machines for wheezy, but not make it default. Differences in the setup: yaboot expects a ~1MiB bootstrap partition in an apple-formatted disk that is openfirmware-visible. This partition isn't mounted on the running host, but is managed/updated when the admin runs ybin. grub-ieee1275 expects a larger bootstrap partition (~10MiB should be fine) in an apple-formatted disk that is openfirmware-visible. This partition should have a plain HFS (not HFS+) filesystem on it, and should be mounted by the host at /boot/grub. To transition fully to grub on powerpc machines we will have to change partitioning recipes for CHRP IBM, CHRP Pegasos and NewWorld Mac machines. This will have to wait for jessie. Manual creation of the appropriate partition in d-i (/boot/grub) will enable grub installation in wheezy d-i. Thus, we will be able to experiment with d-i grub installation on powerpc machines. Users of grub-ieee1275 probably therefore also want to have hfsprogs installed on their system for /sbin/fsck.hfs so that routine filesystem checks at boot time can proceed for the filesystem mounted at /boot/grub. I agree. I'm also happy to test powerpc d-i images that use grub-ieee1275 if you need testers. Do you have access to any IBM Power machines? Milan signature.asc Description: OpenPGP digital signature
Bug#664128: grub-installer: Allow grub installation on powerpc machines if /boot/grub partition is present
clone 664128 -1 -2 -3 -4 -5 reassign 664128 grub-installer retitle 664128 Allow grub installation on powerpc machines if /boot/grub partition is present tags 664128 pending reassign -1 grub-installer retitle -1 Provide instruction for Pegasos/Efika users to enable auto-boot in OF reassign -2 partman-auto retitle -2 Create OF boot partition and mount it at /boot/grub on CHRP IBM machines reassign -3 partman-auto retitle -3 Resize current boot partition and mount it at /boot/grub on NewWorld Mac machines reassign -4 partman-auto retitle -4 Create OF boot partition and mount it at /boot/grub on CHRP Pegasos/Efika retitle -5 Install hfsprogs on powerpc machines by default thanks Creating non-exhaustive list of bugs/tasks to transition from yaboot to grub on powerpc machines. Milan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5085c2bf.6ufht4pms+qjejet%mi...@physics.harvard.edu
Re: Bug#684265: Still with us
On 09/24/2012 05:04 AM, Rick Thomas wrote: On Sep 13, 2012, at 2:58 PM, Rick Thomas wrote: 1) It seems likely that adding a udeb for fuse-modules will allow os-prober to identify other Linux OS root partitions and get them added to the boot-loader config file... But only as long as those partitions are not LVM partitions. I have not performed definitive experiments to verify either half of this assertion, but the evidence so far does point in that direction. When can I expect the udeb for fuse fix to be included in an upcoming daily iso? I'll be happy to test it when it's available. I tried a test installation with the following: Debian GNU/Linux testing Wheezy - Official Snapshot amd64 NETINST Binary-1 20120923-03:20 which seems to have the necessary module: $ find /mnt -name '*fuse*' -print /mnt/pool/main/f/fuse /mnt/pool/main/f/fuse/fuse-udeb_2.9.1-1_amd64.udeb /mnt/pool/main/f/fuse/libfuse2_2.9.0-2_amd64.deb /mnt/pool/main/f/fuse/libfuse2-udeb_2.9.1-1_amd64.udeb /mnt/pool/main/l/linux/fuse-modules-3.2.0-4-amd64-di_3.2.29-1_amd64.udeb However, it still doesn't find the other OS partitions... They are located in /dev/mapper/monk-root2 and /dev/mapper/monk-root3. The partition being installed to is in /dev/mapper/monk-root. I'm attaching the (gzipped) installer logs. Rick Please file a separate debian-installer bug report for problems related to finding other OS's on LVM partitions. Milan signature.asc Description: OpenPGP digital signature
Re: Bug#684265: Debian Installer 7.0 Beta2 release bug #684265
On 09/13/2012 01:41 AM, Christian PERRIER wrote: Quoting Rick Thomas (rbtho...@pobox.com): On Sep 12, 2012, at 4:21 PM, Rick Thomas wrote: I have not tried running os-prober from the alt-F2 console during the install, to see if it gives different results. I'll do that and report back. Any hints of things I should be looking out for? Here's the stderr/stdout output when os-prober is run in the installer environment: umount: can't umount /var/lib/os-prober/mount: Invalid argument grub-probe: error: no such disk. grub-probe: error: no such disk. grub-probe: error: no such disk. Could be something like #686314. Can you try (in the installer) to do the workaround found there (loading the fuse module)? Definitely, os-prober needs fuse module to work properly. D-i is trying to load the fuse module but it is not available in the d-i environment. Here is d-i log extract: Sep 11 02:15:31 anna-install: Installing ufs-modules Sep 11 02:15:31 anna-install: Installing btrfs-modules Sep 11 02:15:31 anna-install: Installing fuse-modules Sep 11 02:15:31 os-prober: unknown udeb fuse-modules When I load the fuse module manually os-prober works fine. Therefore solution for bug reports 684265, 686314, 686631, 687286 is to create fuse-modules udeb package. Patch is available here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684265#35 Other problems related to listing other OS's in grub menu, that may or may not be related to os-prober, are described in bug reports 587397, 603107, 608025, 608219, 609251. If you see similar problems related to LVM please file a separate bug report. Milan signature.asc Description: OpenPGP digital signature
Bug#685414: installation-reports: Hangs while searching drives on a Mac Mini G4 (PowerPC)
On 08/27/2012 12:33 PM, Gunnar Wolf wrote: Gaudenz Steinlin dijo [Thu, Aug 23, 2012 at 09:31:03PM +0200]: ... I guess this is #683849. Can you try a daily image? ... The bug you mention happens at a much later stage (at partman-auto-lvm, my lockup happens just after localechooser), although it does sound related - Trying to mount /dev/sda1 from the console still hangs. However, the following messages in /var/log/syslog grab my attention: Aug 27 16:05:32 hw-detect: Missing modules 'pata_macio (KeyLargo ATA) This log line is not related to your problem. hw-detect is letting us know that the pata_macio module does not exist, anymore. No harm comes out of it. The pata-macio module was compiled in the kernel since November 2011 and is working fine, at least for me. Boot into the installer again. When you get to the problematic point choose 'Save debug logs' from the 'Debian installer main menu'. Attach the files to this bug report. They may reveal what is going on. You may try to start the installer form an external firewire cd/dvd drive. See: http://lists.debian.org/4fdd55cc.7020...@physics.harvard.edu You may also try to boot the installer form the USB stick directly. It is not quite straightforward how to do it, but try this: Copy .iso to a USB memory stick using dd. sudo dd if=debian-testing-powerpc-netinst.iso of=/dev/sd[x] Unplug all USB devices and hubs, except the keyboard and mouse. Plug the USB memory stick directly into the machine. Restart the machine while holding option+command+o+f keys. On the Open Firmware prompt type: boot usb0/disk:,\install\yaboot if it does not work, one of these should, depending on which connector you plugged the USB memory stick in: boot usb1/disk:,\install\yaboot boot usb2/disk:,\install\yaboot boot usb-1a/disk:,\install\yaboot boot usb-1b/disk:,\install\yaboot boot usb-1c/disk:,\install\yaboot boot usb-2a/disk:,\install\yaboot boot usb-2b/disk:,\install\yaboot boot usb-2c/disk:,\install\yaboot On some machines usb device aliases can be different. To get hints where the USB device is and which alias could be the right one, type: devalias and dev / ls -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/503bee2b.10...@physics.harvard.edu
Re: Reviewing nobootloader for wheezy
On 08/12/2012 02:59 PM, Cyril Brulebois wrote: Hello Milan, and thanks for your patch for nobootloader. Got a quick question though. Changelog excerpt: | nobootloader (1.35) unstable; urgency=low | | [ Milan Kupcevic ] | * Do not assume Linux kernel verison is 2.* | * Use symlink 'vmlinuz' instead of full kernel name. But I see this change in postinst which looks a bit unrelated: | @@ -148,7 +148,7 @@ | scsi,0) | path=/pci/scsi/disk@$bus,$target,$lun ;; | *) | - path=unknown path ;; | + path=hd ;; | esac | | # map theidevice to the OF aliases from /proc/device-tree/aliases. Can you please clarify whether it was intended? This changelog line is missing: * Fallback to factory default HD firmware alias, not to unknown device And what that does? At the end of nobootloader installation, d-i prints out a line the user installing the system is supposed to type into firmware prompt to make it find kernel on machine boots/reboots. The 'path' variable in question is the firmware device path used in the printed line on Pegasos machines. I've replaced the technically invalid firmware path 'unknown path' with the device alias 'hd' which works out fine when the machine has only one HD, or if the user installs the system on the first HD when the machine has more than one drive. In my wheezy installer tests it always falls back to unknown path. This happens because the kernel internals changed since the original Pegasos code in nobootloader was written. To fix it properly, it requires significant rewrite. Which is not worth. I would rather spend more time into making Grub2 installer working on Pegasos and other PowerPC machines. But this change is too late for Wheezy. It has to wait for Jessie. In the meantime, the changes made in nobootloader version 1.35 are enough to make it work for wheezy. Milan signature.asc Description: OpenPGP digital signature
Bug#683233: debian-installer: ppc: /boot too small on guided partitioning
tags 683233 moreinfo thanks On 07/29/2012 08:50 PM, Gabriele Giacone wrote: Package: debian-installer Trying to install on a ppc VM, 20 GB disk (LVM lv) and Guided partitioning - whole disk, it proposes a 32MB /boot which is too small because update-initramfs fills it up during install process and makes it fail. Workaround is removing / partition, resizing /boot from 32 to 64 MB and recreating / partition. Please make /boot size 64 MB by default or make update-initramfs not to write temporary files under /boot. Don't know if it's a problem on other archs too. Start the installation procedure. When 'Finish partitioning and write changes to disk' option gets offered chose Go back, then choose 'Save debug logs'. Attach hardware-summary, partman and syslog files to this bug report. Milan signature.asc Description: OpenPGP digital signature
Bug#683233: debian-installer: ppc: /boot too small on guided partitioning
tags 683233 - moreinfo + pending thanks Fix is pending upload. Milan signature.asc Description: OpenPGP digital signature
Bug#549681: bug#549681: mkvmlinuz: use xz to compress vmlinuz-boxed initrd
reassign 549681 mkvmlinuz retitle 549681 use xz to compress vmlinuz-boxed initrd tags 549681 - help + pending d-i wheezy sid severity 549681 serious owner 549681 ! thanks -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fed0bd7.5080...@physics.harvard.edu
Re: Nonexistent modules in Linux kernel-wedge configuration
On 01/29/2012 03:24 PM, Ben Hutchings wrote: The IDE modules listed here have presumably been replaced by libata-based modules, but there might be some cases where neither driver is built or neither is included in the installer. IBM Intellistation POWER 275 needs pata_sl82c105 in PowerPC installer. I have no idea why it got kicked out. Can anyone explain the others? pata_macio gets compiled in the kernel now, not as a module. Milan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f25fe3e.6020...@physics.harvard.edu
Bug#642296: base-installer: on IBM Power 740 installer selects 32bit ppc kernel despite booting with install64
forcemerge 637519 642296 thanks Duplicate bug. Fix is pending upload. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e79fca2@physics.harvard.edu
Re: installation failed
On 09/05/2011 11:50 AM, Jeroen Diederen wrote: Is the info I gave you enough for you ? It was not quite clear at the begining, but if loading pata-macio fixes your issue, then you've had hit a known problem. Currently, kernel in d-i is using pmac driver compiled-in. The latest kernel avaliable in wheezy is using pata-macio module instead. The pata-macio module isn't getting loaded automatically on machines with KeyLargo, Heathrow/Paddington and OHare controllers. The problem should disapear with upload of hw-detect 1.88, which will let d-i to add pata-macio into /etc/initramfs-tools/modules on the machines where this module isn't getting loaded automatically. Milan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e658ceb.6080...@physics.harvard.edu
Re: installation failed
On 09/04/2011 10:58 AM, Jeroen Diederen wrote: I used the latest netboot image: http://d-i.debian.org/daily-images/powerpc/daily/powerpc/netboot/mini.iso I tried to install a base system. Installation went fine, yaboot installed ok too. At reboot I am thrown into a busybox shell. The error messages I get are: Gave up waiting for a root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/long-number does not exist. Dropping to a shell! FATAL: Error inserting i8042 (/lib/modules/3.0.0-1-powerpc/kernel/drivers/input/serio/i8042.ko): No such device FATAL: Error inserting atkbd (/lib/modules/3.0.0-1-powerpc/kernel/drivers/input/keyboard/atkbd.ko): No such device It has nothing to do with yaboot as I also installed on another computer where I skipped yaboot installation (I had yaboot working fine). I get the same errors on that machine. It seems it has something to do with some kernel modules. Regards Jeroen Diederen http://mintppc.org Which machine are you trying to install it on? Proper installation report would help. If it is a Mac please try the suggestion from: http://lists.debian.org/debian-powerpc/2011/08/msg00050.html and report back. Milan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e63b0a0.5070...@physics.harvard.edu
Re: [Debootloaders-yaboot] Bug#636269:
This problem is PowerMac specific. We have to compile in pata-macio (libata) instead of ide-pmac (deprecated ide) driver into kernel. Yaboot has to be fixed first to support pata-macio. Milan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e3d3783.5040...@physics.harvard.edu
Re: Bug#603536: Linux on POWER Bootable ISO
On 12/30/2010 02:24 AM, Christian PERRIER wrote: Quoting Milan Kupcevic (mi...@physics.harvard.edu): Unofficial Debian Install CD created with --iso-level 4 mkisofs option boots fine on both machines. Steve McIntyre applied your patch to debian-cd. Could you confirm whether that fixes this issue (by checking daily builds, I guess)? I booted YDL PowerStation with official weekly testing CD1 [1] built on December 20, 2010. Therefore, this issue is fixed in testing CD production environment. [1] .disk/info: Debian GNU/Linux testing Squeeze - Official Snapshot powerpc CD Binary-1 20101220-08:05 signature.asc Description: OpenPGP digital signature
Bug#332227: Unofficial Squeeze NetInst CDs: call for testers
On 12/15/2010 02:31 AM, Frank Fegert wrote: Hello, On Tue, Dec 14, 2010 at 11:43:03PM +0100, Gaudenz Steinlin wrote: Excerpts from Frank Fegert's message of Die Dez 14 19:34:12 +0100 2010: i tried the unofficial-debian-squeeze-powerpc-netinst-1-yaboot-1.3.16.iso on a p550 Power6+ LPAR, Microcode 01EL350_085_038, dual VIOS. The install fails at Install yaboot on a hard disk with: [!!] Install yaboot on a hard disk No bootstrap partition found No hard disks were found which have an Apple_Bootstrap partition. You must create an 819200-byte partition with type Apple_Bootstrap. This error message comes from yaboot-installer when it is not able to find ANY bootable partition, not just when there is no Apple_Bootstrap partition. This is a generic error message pulled from yaboot-installer.templates, which has to be changed because it gives wrong advice to non Mac users. Exiting to a shell shows the following partition layout: ~ # /target/sbin/sfdisk -l Disk /dev/sda: 16384 cylinders, 64 heads, 32 sectors/track Units = cylinders of 1048576 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls#blocks Id System /dev/sda1 1 10 10 10240 41 PPC PReP Boot /dev/sda2 11 964 954 976896 83 Linux /dev/sda3965 16382 15418 15788032 8e Linux LVM /dev/sda4 0 - 0 00 Empty Are these partitions created manually? PPC PReP boot partition should be between 4-8 MB, not bigger than 10MB. It also has to be a primary partition and marked active/bootable. This one is not marked bootable. If you want to use LVM you will have to put /boot on second primary partition (sda2) and copy yaboot.conf from /etc/yaboot.conf to /boot/etc/yaboot.conf at the end of installation procedure (right before installer reboots the machine). Sorry, yaboot-installer development was stalled for last 5 years. Do you know if this error is a regression regarding the lenny installer or the current official beta2 installer? If so we have to investigate this and fix the bug before the packages enter testing. But I suspect this nerver worked. See also Debian bugs #332227, #352914 and #350372. I guess this really needs someone with the right hardware to dig in and solve the bugs or write the missing code for the installer. Bug 352914 was influenced by the same misleading error message. All three bug reports became one big confused discussion. the ISOs i used for previous installs were debian-500-powerpc-netinst.iso and debian-504-powerpc-netinst.iso, both worked as far as the install is concerned. There were some yaboot issues with getting the successfully in- stalled system to boot (see my previous postings to the list). Could you please do clean install on one disk with no lvm, no raid, no manual partitioning. Just choose Guided - use entire disk, and then All files in one partition. If you hit an error screen, download all install logs, pack them and send with your report. When you test official install CD, submit official installation-report or bug report. We can discuss unofficial install CD issues in this mailing list. Thank you for the extra info you collected from the installer. The nvram info you sent is useful, boot-device was set to network boot. I'm collecting content of boot-device and diag-device variables from nvram on various configurations. Currently I need the most those that are set to boot Linux or AIX installed in any LPAR, especially if they boot from a virtual drive provided by VIOS. Can you get output of /sbin/nvsetenv from already running Linux installations that you have around? Thanks, Milan signature.asc Description: OpenPGP digital signature
Re: Bug#603536: Linux on POWER Bootable ISO
Official Debian PowerPC install iso images wont boot on my two machines because IBM OpenFirmware on IBM RS/6000 44P Model 170 and IBM SLOF firmware on YDL PowerStation are not able to read files from isofs. Unofficial Debian Install CD created with --iso-level 4 mkisofs option boots fine on both machines. Linux on POWER Bootable ISO HOWTO [1] instruction says: The mkisofs man page lists all the options that can be passed on the command line, here is a simple set of options that will be enough to produce a bootable CD. mkisofs -r -U -chrp-boot -o image.iso base_directory You should now have a bootable ISO image that you can boot on a Linux on POWER system. Other linux distributions targeting IBM POWER machines create their PowerPC install CD images using -U option. The -U option Allows 'Untranslated filenames, completely violating the iso9660 standards, so it is probably better to go for --iso-level 4 as it produces ISO-9660:1999 compliant CD/DVD images, and as far as I can see works fine on Macs and IBM machines. Could you, please, apply the patch attached to bug report #603536 to create proper bootable .iso for Power machines, and make sure Squeeze PowerPC iso images are produced with the same option. Thanks, Milan [1] http://penguinppc.org/ppc64/power-bootable-iso/ [Appendix] Here is how official Debian install CD files look from IBM OpenFirmware's point of view: 0 dir cdrom DIR 12-15-2010 09:11:19 . DIR 12-15-2010 09:11:19 .. DIR 12-15-2010 09:10:48 CSS 0 12-15-2010 09:11:19 DEBIAN DIR 12-15-2010 09:10:48 DISTS DIR 12-15-2010 09:10:47 DOC DIR 12-15-2010 09:10:49 ETC DIR 12-15-2010 09:10:50 FIRMWARE DIR 12-15-2010 09:10:49 INSTALL 46888 12-15-2010 09:11:19 MD5SUM.TXT DIR 12-15-2010 09:10:48 PICS DIR 12-15-2010 09:10:49 POOL DIR 12-15-2010 09:10:49 PPC 8992 12-15-2010 09:11:19 README.HTML 375 12-15-2010 09:10:49 README.SOURCE 5564 12-15-2010 09:11:19 README.TXT 141804 12-15-2010 01:56:06 README_MIRRORS.HTML 76266 12-15-2010 01:56:06 README_MIRRORS.TXT DIR 12-15-2010 09:11:19 _DISK ok Here is how they look on an unofficial Debian install CD created with --iso-level 4 mkisofs option: 0 dir cdrom DIR 12-11-2010 20:57:25 . DIR 12-11-2010 20:57:25 .. DIR 12-11-2010 20:57:25 .disk 8962 12-11-2010 20:57:25 README.html 141274 11-20-2010 08:52:23 README.mirrors.html 76044 11-20-2010 08:52:23 README.mirrors.txt 306 12-11-2010 20:55:38 README.source 5544 12-11-2010 20:57:25 README.txt DIR 12-11-2010 20:55:33 css 0 12-11-2010 20:57:25 debian DIR 12-11-2010 20:55:33 dists DIR 12-11-2010 20:55:32 doc DIR 12-11-2010 20:55:38 etc DIR 12-11-2010 20:55:49 firmware DIR 12-11-2010 20:55:38 install 48176 12-11-2010 20:57:25 md5sum.txt DIR 12-11-2010 20:55:33 pics DIR 12-11-2010 20:55:39 pool DIR 12-11-2010 20:55:38 ppc ok Here is how an Official IBM AIX install CD looks from the IBM OpenFirmware point of view: 0 dir cdrom DIR 09-23-2002 11:44:52 . DIR 09-23-2002 11:44:52 .. 42 09-23-2002 11:44:52 .Version DIR 09-23-2002 11:40:19 5100-03 16 09-23-2002 11:40:19 OSLEVEL DIR 09-23-2002 11:43:00 RPMS 10445 09-23-2002 11:40:19 bosinst.data 12788 09-23-2002 11:40:19 image.data DIR 09-23-2002 11:44:25 installp DIR 09-23-2002 11:40:20 ppc DIR 09-23-2002 11:40:22 root DIR 09-23-2002 11:41:16 usr ok signature.asc Description: OpenPGP digital signature
Re: Bug#606441: unblock: yaboot/1.3.13a-1squeeze1
On 12/10/2010 06:21 PM, Lennart Sorensen wrote: On Fri, Dec 10, 2010 at 11:42:49PM +0100, Mehdi Dogguy wrote: Well, Gaudenz and Milan worked on fixing the reported RC bugs against yaboot. And, I'd rather thank them for that. sid's version doesn't look like fixing the critical problems experienced by our users. Besides, I don't see any bugreport of yours explaining your issue. Having found the bug reported upstream, fixed in 1.3.14 years ago, and seeing how many people had made attemps at getting 1.3.14 into Debian, there seemed to be no point filling another bug report. So I didn't bother. I usually file bug reports, but yaboot seemed obviously futile. I am rather surprised to see there now is a new version in unstable. A few months too late to really help anyone wanting to run Squeeze though, but at least in a couple of years there will be a Debian version that might be useful for those machines. Well, the whole situation you are describing actually motivated me to do something about it. And I did what was possible to do in short period of time. Any bugreport I could read? Well given I don't even know if an IBM p520 power6+ machine is expected to work with Debian, I haven't filled one. I pointed out a few drivers and other issues I hit, although they seemed to get no interest from anyone. There is a bug report in grub2 (upstream) about the issues left to solve for the IBM pseries servers. You have hands on that machine, I do not. Fix the issue, produce patch, we are eager to see the solution. Also take a look at this thread, we discuss about IBM p520 power6+ machine: http://lists.debian.org/debian-powerpc/2010/12/msg00032.html grub2 does work once you manually generate the image and install it on a boot partition, and it supports software raid (something yaboot didn't, although it appears the 1.3.16 version now in unstable might), so it worked out OK for me. Please provide fully working and tested yaboot 1.3.16 Debian package and propose its upload, I'm sure it will override this one. Or even better, provide fully functional grub2 package for power platform. I'm sure it will get approved quickly. The grub developers helped fix some endianess bugs in the md raid 1.x format handling (as well as in mdadm, which has been fixed upstream now). To make life easier, grub needs working handling of devices without aliases (which IBM machines don't create, unlike apple and sun and most other openfirmware machines). I don't know if that has been completed yet, although some work was being done on it. I have created aliases myself for now which made grub happy. The bug report in grub is: http://savannah.gnu.org/bugs/?30576 If we do not get yaboot 1.3.13a-1squeeze1 and fixed yaboot-installer bug #605932 into squeeze, it will be uninstallable, without manual tweaking, on all machines with SATA, SAS, and SCSI controllers (this includes all Mac G5 machines). All Mac G5 machines also need fixed initramfs-tools bug #603981. I sent a question about the missing network driver and console entries in securetty to debian-boot and heard nothing: http://www.mail-archive.com/debian-boot@lists.debian.org/msg118643.html FYI: a bug report #605774 regarding ehea network driver was submitted on December 03, 2010 by Xavier Grave and was fixed in SVN promptly. It will get to squeeze install CD soon. And finally we should get back to the subject of this message. Do you advocate for or against getting yaboot/1.3.13a-1squeeze1 into squeeze? Why, or why not? Milan signature.asc Description: OpenPGP digital signature
Bug#606147: yaboot-installer: Use short unique OS labels returned by os-prober
Package: yaboot-installer
Tags: patch
Yaboot-installer should use short unique OS labels returned by os-prober
instead of long titles. It should add oldlabel to the label, if available.
Currently, first word from long title is actually used by yaboot. This
regularly makes duplicate labels. Current solution of prepending the
last part of the partition name to the label just adds to the confusion
as unix device/partition names are not persistent anymore.
Index: debian/postinst
===
--- debian/postinst (revision 65533)
+++ debian/postinst (working copy)
@@ -255,10 +255,10 @@
linux)
IFS=:
linux-boot-prober $partition | while read \
- rootpart bootpart label kernel initrd params; do
+ rootpart bootpart oldlabel kernel initrd params; do
IFS=$OLDIFS
info linux-boot-probed: \
- $rootpart:$bootpart:$label:$kernel:$initrd:$params
+ $rootpart:$bootpart:$oldlabel:$kernel:$initrd:$params
ofrootpart=$(map_of_path $mappedpartition) || continue
debug OF root partition: $ofrootpart
# bootpart may or may not be in devfs syntax.
@@ -267,13 +267,8 @@
debug mapped boot partition: $mappedbootpart
ofbootpart=$(map_of_path $mappedbootpart) || continue
debug OF boot partition: $ofbootpart
- if [ -z $label ]; then
- label=$title
- fi
- # Prepend the last part of the partition name to the label,
- # for uniqueness and (I hope) clarity, given that we don't
- # have a way to display a useful description in yaboot.
- label=${mappedbootpart##*/}-$label
+ # Add oldlabel to os-prober provided label, if available.
+ label=$label${oldlabel:+-${oldlabel}}
if echo $kernel | grep -q '^/boot/' \
[ $mappedbootpart != $mappedpartition ]; then
# separate /boot partition
signature.asc
Description: OpenPGP digital signature
Bug#605900: PowerMac G3 (BW): X running wild filling log file
clone 605900 -1 -2 reassign -1 yaboot-installer retitle -1 drives seem to be detected in undefined order severity -1 important merge 572925 -1 tags 572925 - help reassign -2 yaboot retitle -2 mkofboot couldn't find /proc/scsi forcemerge 572869 -2 reassign 605900 xorg retitle 605900 PowerMac G3 (BW): X running wild filling log file tags 605900 moreinfo thanks On 12/04/2010 10:00 AM, Risto Suominen wrote: Third problem was with X. It was running wild and filling the disk with its log file. The salvation came with package firmware-linux-nonfree containing the file r128_cce.bin. Still, I'm unable to log out and in again, as this makes X hang. Please run /usr/share/bug/xorg/script 3/tmp/script.log and attach the generated file. signature.asc Description: OpenPGP digital signature
Bug#605932: drives seem to be detected in undefined order
forcemerge 572925 605932 thanks On 12/04/2010 10:00 AM, Risto Suominen wrote: After manually editing /etc/yaboot.conf, I was facing another problem on boot: the disk drives seem to be detected in undefined order, and this makes it difficult to guess correct /dev/sd letter (and yaboot doesn't accept LABEL= syntax). I have two IDE disks (pata_cmd64x) and one SCSI disk (the one used here) (aic7xxx). This is a known problem with a known solution. Fixed Yaboot, which will be uploaded within next few days, will recognize persistent device naming symlinks and UUID/LABEL syntax. Soon after, yaboot-installer will be fixed to produce yaboot.conf using the same features. signature.asc Description: OpenPGP digital signature
Bug#605774: debian-installer: Missing ehea.ko module for powerpc install
tags 605774 pending thanks Ehea module added to linux-kernel-di-powerpc-2.6. Pending upload. signature.asc Description: OpenPGP digital signature
Bug#572925: installation-reports: PowerMac G5 ofpath doesn't work in the absence of /proc/scsi/scsi
tags 572925 patch
thanks
linux-base package already transforms old yaboot.conf unix block device
names into persistent device names on upgrades. Yaboot just got bug fix
for #572869 and will be able to parse such configuration files. We
should commit the attached patch and upload yaboot-installer at the same
time, or soon after fixed yaboot reaches squeeze.
Find bug-fix test install cd at:
http://www.quarkline.net/debian/bug/yaboot/
Index: debian/postinst
===
--- debian/postinst (revision 65804)
+++ debian/postinst (working copy)
@@ -240,6 +240,27 @@
chroot /target ofpath $1 || return 1
}
+# Get a symlink which always points to the correct block device.
+# If it does not exist, give the unix block device name back.
+devsymlink() {
+ [ $2 != nobyid ] BYID=/dev/disk/by-id/scsi* /dev/disk/by-id/*
+ for SYMLINK in $BYID /dev/disk/by-uuid/* /dev/disk/by-label/*; do
+[ `readlink -f $SYMLINK` = $1 ] {
+ echo $SYMLINK
+ return
+}
+ done
+ echo $1
+}
+
+# Get UUID= or LABEL= for the given unix partition block device.
+# If it could not be determined, give the unix partition block device back.
+uuidlabel() {
+ echo `devsymlink $1 nobyid` \
+ | sed -e s,/dev/disk/by-uuid/,UUID=, \
+-e s,/dev/disk/by-label/,LABEL=,
+}
+
OLDIFS=$IFS
IFS=:
# Note that this creates a subshell, so variables set inside this loop won't
@@ -270,6 +291,8 @@
if [ -z $label ]; then
label=$oldlabel
fi
+ # remove root parameter from params
+ params=`echo $params | sed -e s,root=[^[:space:]]*,,`
if echo $kernel | grep -q '^/boot/' \
[ $mappedbootpart != $mappedpartition ]; then
# separate /boot partition
@@ -282,7 +305,7 @@
# Linux installation on $mappedpartition.
image=$ofbootpart,$kernel
label=$label
-root=$ofrootpart
+root=`uuidlabel $mappedpartition`
append=$params
EOF
if [ -n $initrd ]; then
@@ -297,13 +320,13 @@
macosx)
if ! [ $macosx ]; then
macosx=1
- echo macosx=$mappedpartition | writeglobals
+ echo macosx=\`devsymlink $mappedpartition`\ | writeglobals
fi
;;
macos)
if ! [ $macos ]; then
macos=1
- echo macos=$mappedpartition | writeglobals
+ echo macos=\`devsymlink $mappedpartition`\ | writeglobals
fi
;;
*)
@@ -408,7 +431,7 @@
if [ $boot ]; then
writeyabootconf EOF
-boot=$boot
+boot=`devsymlink $boot`
EOF
fi
@@ -421,7 +444,7 @@
fi
writeyabootconf EOF
partition=$partnr
-root=$root
+root=`uuidlabel $root`
timeout=$timeout
install=$yaboot_location
EOF
signature.asc
Description: OpenPGP digital signature
Bug#572925: lastest Sid upgrade breakes yaboot.conf
block 572925 by 580455 thanks Blocking this bug by #580455, which will actually fix the upgrade breaks yaboot.conf problem. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580455#71 signature.asc Description: OpenPGP digital signature
Bug#604611: os-prober: Properly Detect International Mac OS
tags + help affects - yaboot-installer thanks Current os-prober implementation won't detect system folders in various languages in international versions of Mac OS. Assembling a list of all system folder names may be one way to go. Another way could be to do MacOS X probe in a shell script first, and if it yields nothing, run a small binary executable which would check blessing status. UInt32 finderInfo[3] has non-zero value if a blessed MacOS 8/9 folder is located on a HFS+ volume (HFSPlusVolumeHeader struct). UInt32 drFndrInfo[0] has non-zero value if a blessed folder is located on a HFS volume (HFSMasterDirectoryBlock struct). Make sure no Yaboot, Quik, or Grub is located on the blessed volume. HFS wrapping details are described in Apple Technical Note TN1150. signature.asc Description: OpenPGP digital signature
Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize disk anymore
It looks like installer creates MacOS 9 incompatible partition table, but which works fine with MacOS X and Linux. After partitioning a disk using default settings with MacOS X installer CD I installed MacOS X on its third partition and MacOS 9 on its second partition. Then: - booted the machine using squeeze testing installer cd and backed up partition table to a memory stick. - installed squeeze testing by manually removing the first HFS+ partition and then letting Guided partitioning to use the largest continuous free space. - rebooted into squeeze and observed that it works fine, it can mount and use all partitions - rebooted into MacOS X and observed that it also works fine, able to mount and use the partition containing MacOS 9 installation - rebooted into MacOS 9: - firmware finds the partition - loads MacOS 9 - MacOS 9 displays a small disk with a blinking question mark, not being able to find any partition - reboot into squeeze again - restore partition table from the memory stick - reboot into MacOS 9, it works fine - reboot into MacOS X, it works fine Hope this helps. signature.asc Description: OpenPGP digital signature
Bug#603891: libdebian-installer: Add subarch support for YDL PowerStation
tags 603891 patch
thanks
Attached patch adds subarch detection for YDL PowerStation.
diff -Nru ./src/system/subarch-powerpc-linux.c ../libdebian-installer-0.76/src/system/subarch-powerpc-linux.c
--- ./src/system/subarch-powerpc-linux.c 2008-05-30 04:02:31.0 -0400
+++ ../libdebian-installer-0.76/src/system/subarch-powerpc-linux.c 2010-11-17 16:52:56.0 -0500
@@ -33,6 +33,7 @@
{ PS3, ps3 },
{ Cell, cell },
{ PA Semi, pasemi },
+ { Maple, chrp_ibm },
{ NULL, NULL }
};
signature.asc
Description: OpenPGP digital signature
Bug#603892: base-installer: Add YDL PowerStation regression test
tags 603892 patch thanks Attached patch adds YDL PowerStation regression test. diff -Nru ./kernel/tests/powerpc/ydl_powerstation.cpuinfo ../base-installer-1.113/kernel/tests/powerpc/ydl_powerstation.cpuinfo --- ./kernel/tests/powerpc/ydl_powerstation.cpuinfo 1969-12-31 19:00:00.0 -0500 +++ ../base-installer-1.113/kernel/tests/powerpc/ydl_powerstation.cpuinfo 2010-11-07 15:04:24.0 -0500 @@ -0,0 +1,23 @@ +processor : 0 +cpu : PPC970MP, altivec supported +clock : 2500.00MHz +revision: 1.1 (pvr 0044 0101) + +processor : 1 +cpu : PPC970MP, altivec supported +clock : 2500.00MHz +revision: 1.1 (pvr 0044 0101) + +processor : 2 +cpu : PPC970MP, altivec supported +clock : 2500.00MHz +revision: 1.1 (pvr 0044 0101) + +processor : 3 +cpu : PPC970MP, altivec supported +clock : 2500.00MHz +revision: 1.1 (pvr 0044 0101) + +timebase: 14318278 +platform: Maple +model : TSS,7047-191 diff -Nru ./kernel/tests/powerpc/ydl_powerstation.test ../base-installer-1.113/kernel/tests/powerpc/ydl_powerstation.test --- ./kernel/tests/powerpc/ydl_powerstation.test 1969-12-31 19:00:00.0 -0500 +++ ../base-installer-1.113/kernel/tests/powerpc/ydl_powerstation.test 2010-11-07 15:06:18.0 -0500 @@ -0,0 +1,17 @@ +subarch chrp_ibm +cpuinfo ydl_powerstation.cpuinfo +majors 2.6 +flavour powerpc64 +kernel-2.6 linux-image-2.6-powerpc64 +usable \ + linux-image-2.6-powerpc64 \ + linux-image-2.6.32-5-powerpc64 +unusable \ + linux-image-2.6-powerpc \ + linux-image-2.6-powerpc-miboot \ + linux-image-2.6-powerpc-smp \ + linux-image-2.6-prep \ + linux-image-2.6.32-5-powerpc \ + linux-image-2.6.32-5-powerpc-miboot \ + linux-image-2.6.32-5-powerpc-smp \ + linux-image-2.6.32-5-prep signature.asc Description: OpenPGP digital signature
Bug#603893: debian-installer: YDL PowerStation needs pata-modules in powerpc cdrom initrd
tags 603893 patch
thanks
Debian installer needs pata_amd module to detect CD drive in YDL
PowerStation.
diff -Nru ./build/pkg-lists/cdrom/powerpc.cfg ../debian-installer-20101121/build/pkg-lists/cdrom/powerpc.cfg
--- ./build/pkg-lists/cdrom/powerpc.cfg 2010-01-11 10:35:40.0 -0500
+++ ../debian-installer-20101121/build/pkg-lists/cdrom/powerpc.cfg 2010-11-21 17:22:13.0 -0500
@@ -2,6 +2,7 @@
firewire-core-modules-${kernel:Version}
ide-modules-${kernel:Version}
+pata-modules-${kernel:Version}
console-keymaps-at
console-keymaps-usb
kbd-chooser
signature.asc
Description: OpenPGP digital signature
Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize disk anymore
clone 604134 -1 reassign -1 os-prober retitle -1 os-prober: Won't detect MacOS 9 severity -1 important affects -1 yaboot-installer thanks I can confirm that os-prober takes a look at hfsplus partition containing MacOS 9, but won't report installed MacOS 9. Cloning to os-prober. signature.asc Description: OpenPGP digital signature
Bug#604192: os-prober: Won't detect MacOS 9
tags 604192 patch
thanks
os-prober wouldn't detect installed MacOS because it missed actual mount
point of the tested partition. Variable '$dir' was always empty.
diff -Nru ./os-probes/mounted/m68k/10macos6-9 ../os-prober-1.40/os-probes/mounted/m68k/10macos6-9
--- ./os-probes/mounted/m68k/10macos6-9 2010-02-10 18:06:57.0 -0500
+++ ../os-prober-1.40/os-probes/mounted/m68k/10macos6-9 2010-11-20 22:39:12.0 -0500
@@ -13,7 +13,7 @@
hfsplus) debug Partition is HFS+ (Mac OS 9 only, we hope) ;;
esac
-if [ -e $dir/System Folder/System ]; then
+if [ -e $mpoint/System Folder/System ]; then
label=$(count_next_label MacOS)
result ${partition}:Macintosh System 6/7, OS 8/9:${label}:chain
exit 0
diff -Nru ./os-probes/mounted/powerpc/10macos6-9 ../os-prober-1.40/os-probes/mounted/powerpc/10macos6-9
--- ./os-probes/mounted/powerpc/10macos6-9 2010-02-10 18:06:57.0 -0500
+++ ../os-prober-1.40/os-probes/mounted/powerpc/10macos6-9 2010-11-20 22:39:58.0 -0500
@@ -13,7 +13,7 @@
hfsplus) debug Partition is HFS+ (Mac OS 9 only, we hope) ;;
esac
-if [ -e $dir/System Folder/System ]; then
+if [ -e $mpoint/System Folder/System ]; then
label=$(count_next_label MacOS)
result ${partition}:Macintosh System 6/7, OS 8/9:${label}:macos
exit 0
signature.asc
Description: OpenPGP digital signature
Bug#603533: Missing sl82c105 ide module on IBM IntelliStation POWER 275
On 11/18/2010 02:22 PM, Julien Cristau wrote: On Tue, Nov 16, 2010 at 17:34:57 -0500, Milan Kupcevic wrote: This is not true, AFAICT. No architecture has CONFIG_PATA_WINBOND set. Both powerpc and armel/iop32x have CONFIG_BLK_DEV_SL82C105=m. Therefore, pata_sl82c105 does not exist at all in Debian Squeeze. But sl82c105 exists in powerpc and armel/iop32x. We need sl82c105 in powerpc udeb to enable cdrom installation on IBM pSeries machines. signature.asc Description: OpenPGP digital signature
Bug#603891: libdebian-installer: Add subarch support for YDL PowerStation
Package: libdebian-installer Version: 0.76 Add support for YDL PowerStation, a CHRP machine with IBM Bimini board and SLOF firmware. uname -a: Linux debian 2.6.32-5-powerpc64 #1 SMP Sun Oct 31 03:03:00 UTC 2010 ppc64 GNU/Linux lspci -knn: :f0:0b.0 PCI bridge [0604]: Apple Computer Inc. CPC945 PCIe Bridge [106b:005b] lspci -knn: :f1:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV535 [Radeon X1650 Series] [1002:71c7] (rev 9e) lspci -knn: Subsystem: PC Partner Limited Device [174b:0840] lspci -knn: Kernel driver in use: radeon lspci -knn: :f1:00.1 Display controller [0380]: ATI Technologies Inc RV535 [Radeon X1650 Series] [1002:71e7] (rev 9e) lspci -knn: Subsystem: PC Partner Limited Device [174b:0841] lspci -knn: 0001:00:01.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-X bridge [1166:0130] (rev b0) lspci -knn: 0001:00:02.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-X bridge [1166:0130] (rev b0) lspci -knn: 0001:00:03.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-Express Bridge [1166:0132] (rev b0) lspci -knn: 0001:00:04.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-Express Bridge [1166:0132] (rev b0) lspci -knn: 0001:00:05.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-Express Bridge [1166:0132] (rev b0) lspci -knn: 0001:00:06.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-Express Bridge [1166:0132] (rev b0) lspci -knn: 0001:00:07.0 PCI bridge [0604]: Advanced Micro Devices [AMD] AMD-8111 PCI [1022:7460] (rev 07) lspci -knn: 0001:00:08.0 ISA bridge [0601]: Advanced Micro Devices [AMD] AMD-8111 LPC [1022:7468] (rev 05) lspci -knn: 0001:00:08.1 IDE interface [0101]: Advanced Micro Devices [AMD] AMD-8111 IDE [1022:7469] (rev 03) lspci -knn: Kernel driver in use: pata_amd lspci -knn: 0001:01:01.0 RAID bus controller [0104]: IBM Obsidian chipset SCSI controller [1014:02bd] (rev 01) lspci -knn: Subsystem: IBM PCI-X DDR 3Gb SAS Adapter (572A/572C) [1014:02c1] lspci -knn: Kernel driver in use: ipr lspci -knn: 0001:02:04.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5780 Gigabit Ethernet [14e4:166a] (rev 10) lspci -knn: Subsystem: IBM Device [1014:0329] lspci -knn: Kernel driver in use: tg3 lspci -knn: 0001:02:04.1 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5780 Gigabit Ethernet [14e4:166a] (rev 10) lspci -knn: Subsystem: IBM Device [1014:0329] lspci -knn: Kernel driver in use: tg3 lspci -knn: 0001:05:00.0 PCI bridge [0604]: Texas Instruments XIO2000(A)/XIO2200(A) PCI Express-to-PCI Bridge [104c:8231] (rev 03) lspci -knn: 0001:06:01.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) lspci -knn: Subsystem: NEC Corporation Hama USB 2.0 CardBus [1033:0035] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 0001:06:01.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) lspci -knn: Subsystem: NEC Corporation Hama USB 2.0 CardBus [1033:0035] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 0001:06:01.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 04) lspci -knn: Subsystem: Device [1838:1074] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 0001:08:00.0 USB Controller [0c03]: Advanced Micro Devices [AMD] AMD-8111 USB OHCI [1022:7464] (rev 0b) lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 0001:08:00.1 USB Controller [0c03]: Advanced Micro Devices [AMD] AMD-8111 USB OHCI [1022:7464] (rev 0b) lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 0001:08:02.0 Serial controller [0700]: Exar Corp. XR17C/D152 Dual PCI UART [13a8:0152] (rev 02) lspci -knn: Kernel driver in use: serial usb-devices: usb-devices: T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 5 usb-devices: D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 usb-devices: P: Vendor=1d6b ProdID=0002 Rev=02.06 usb-devices: S: Manufacturer=Linux 2.6.32-5-powerpc64 ehci_hcd usb-devices: S: Product=EHCI Host Controller usb-devices: S: SerialNumber=0001:06:01.2 usb-devices: C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA usb-devices: I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub usb-devices: usb-devices: T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 3 usb-devices: D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 usb-devices: P: Vendor=1d6b ProdID=0001 Rev=02.06 usb-devices: S: Manufacturer=Linux 2.6.32-5-powerpc64 ohci_hcd usb-devices: S: Product=OHCI Host Controller usb-devices: S: SerialNumber=0001:06:01.0 usb-devices: C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA usb-devices: I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub usb-devices: usb-devices: T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 usb-devices: D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 usb-devices: P: Vendor=1d6b ProdID=0001 Rev=02.06 usb-devices: S: Manufacturer=Linux 2.6.32-5-powerpc64 ohci_hcd usb-devices: S:
Bug#603891: libdebian-installer: Add subarch support for YDL PowerStation
clone 603891 -1 -2 -3 reassign -1 base-installer retitle -1 base-installer: Add YDL PowerStation regression test reassign -2 debian-installer retitle -2 debian-installer: Add pata-modules to powerpc cdrom initrd reassign -3 yaboot retitle -3 Add YDL PowerStation support thanks signature.asc Description: OpenPGP digital signature
Bug#603533: Missing sl82c105 ide module on IBM IntelliStation POWER 275
On 11/16/2010 12:38 PM, Otavio Salvador wrote: On Mon, Nov 15, 2010 at 9:17 PM, Miguel Figueiredo el...@debianpt.org wrote: tags 603533 + pending Hello, The right fix, in this case, is to change the powerpc specific udebs otherwise it will be added to all flavours and we moved to pata on those. It won't. This module is not compiled in those other flavours. But you are right, to be on the safe side we should add it to ide-modules in linux-kernel-di-powerpc-2.6. Milan signature.asc Description: OpenPGP digital signature
Bug#603533: Missing sl82c105 ide module on IBM IntelliStation POWER 275
On 11/16/2010 04:19 PM, Miguel Figueiredo wrote: Is this hardware PowerPC specific? On the driver source i found this on the header: SL82C105/Winbond 553 IDE driver Please advise. This controller is not PowerPC specific. It can be run by traditional IDE driver or by modern libata pata driver. PowerPC kernel is compiled with the traditional IDE driver (sl82c105 module). Other kernel flavors use modern libata pata driver (pata_sl82c105). These two modules won't be used together, so a kernel flavor is compiled with either traditional IDE, or libata driver, but not both. I'm not quite sure why is PowerPC kernel not compiled with the modern libpata driver in Squeeze. At some point in the future all traditional IDE drivers will be purged out, and pata_sl82c105 will appear in the PowerPC flavor, too. Milan signature.asc Description: OpenPGP digital signature
Bug#603533: Missing sl82c105 ide module on IBM IntelliStation POWER 275
tags 603533 patch thanks On 11/15/2010 05:03 PM, Miguel Figueiredo wrote: Hi, kernel-wedge has pata_sl82c105 included. Is this the module you have loaded? Can you give more details? [..] No common CD-ROM drive was detected pops up while trying to install using factory built-in ide cdrom drive. Manually inserting sl82c105 module fixes the issue. I loaded sl82c105 module. PowerPC kernel has sl82c105 ide module instead of pata_sl82c105 module. So we should add it to ide-modules in kernel-wedge, or alternatively add it into ide-modules in linux-kernel-di-powerpc-2.6. Thanks, Milan diff -Nru ./modules/ide-modules ../kernel-wedge-2.71/modules/ide-modules --- ./modules/ide-modules 2010-01-11 10:36:10.0 -0500 +++ ../kernel-wedge-2.71/modules/ide-modules 2010-11-15 17:42:28.0 -0500 @@ -24,6 +24,7 @@ serverworks ? siimage ? sis5513 ? +sl82c105 ? slc90e66 ? triflex ? trm290 ? signature.asc Description: OpenPGP digital signature
Bug#603533: Missing sl82c105 ide module on IBM IntelliStation POWER 275
Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/powerpc/iso-cd/debian-testing-powerpc-netinst.iso Date: Sun Nov 14 20:01:27 EST 2010 Machine: IBM IntelliStation POWER 275 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: [E] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: No common CD-ROM drive was detected pops up while trying to install using factory built-in ide cdrom drive. Manually inserting sl82c105 module fixes the issue. report-hw.gz Description: GNU Zip compressed data dmesg.gz Description: GNU Zip compressed data signature.asc Description: OpenPGP digital signature
Bug#603536: installation-reports: YDL PowerStation CD Boot
Package: installation-reports Tags: patch Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/powerpc/iso-cd/debian-testing-powerpc-netinst.iso Date: Sun Nov 14 21:05:09 EST 2010 Machine: YDL PowerStation Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Current Debian install CD's built with mkisofs --level 2 won't boot on this machine. After some investigation I realized that other distros use -U mkisofs option when creating install CD/DVD's. Their install cd's boot just fine on this machine. I built three custom install cd's using debian-cd package with mkisofs options: --level 3 --level 4 -U Level 3 did not boot. The other two created with '--level 4' and '-U' options boot just fine. It is probably best to go for --level 4 as it produces ISO-9660:1999 compliant CD/DVD images. report-hw.gz Description: GNU Zip compressed data diff -Nru ./tools/boot/squeeze/boot-powerpc ../debian-cd-3.1.3/tools/boot/squeeze/boot-powerpc --- ./tools/boot/squeeze/boot-powerpc 2009-08-18 11:01:25.0 -0400 +++ ../debian-cd-3.1.3/tools/boot/squeeze/boot-powerpc 2010-10-23 02:10:39.0 -0400 @@ -29,7 +29,7 @@ install_languages $CDDIR -add_mkisofs_opt $CDDIR/../$N.mkisofs_opts --iso-level 2 +add_mkisofs_opt $CDDIR/../$N.mkisofs_opts --iso-level 4 add_mkisofs_opt $CDDIR/../$N.mkisofs_opts --netatalk add_mkisofs_opt $CDDIR/../$N.mkisofs_opts -hfs add_mkisofs_opt $CDDIR/../$N.mkisofs_opts -probe signature.asc Description: OpenPGP digital signature
Bug#603536: installation-reports: YDL PowerStation CD Boot
The bug-fix test install cd at [1], created with --iso-level 4 mkisofs option, successfully boots my YDL PowerStation: [1] http://www.quarkline.net/debian/bug/ydl-powerstation signature.asc Description: OpenPGP digital signature
