Bug#963119: petitboot: please make the build reproducible
Opened Bug#978103 to remove Petitboot package from Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978103 -Geoff
Bug#978103: RM: petitboot -- ROM; obsolete, unmaintained
Package: ftp.debian.org Severity: normal Please remove petitboot. It is now obsolete and the package is unmaintained. The Debian build is also not reproducible. See Bug#963119 -Geoff
Bug#963119: petitboot: please make the build reproducible
Hi, Petitboot is not receiving much maintenance these days, I think it would be best to remove this package from Debian. What steps need to be taken to remove it? -Geoff On 12/21/20 5:07 AM, Chris Lamb wrote: > Chris Lamb wrote: > >> [..] > > Friendly ping on this? > > > Regards, >
Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.
Hi Ben, On 09/21/2018 04:20 PM, Ben Hutchings wrote: > I've applied these, with some changes: > > 0001: Rather than changing the setting of CONFIG_ACPI_NFIT for arm64, I > removed it entirely as it would be redundant with the top-level config. > > 0002: I dropped several of the config symbols which are automatic. Any > config symbol that doesn't have a description can only be enabled via > other symbols that select it. These shouldn't be mentioned in > debian/config files. > > I also removed CONFIG_ACPI_CONFIGFS as I have a concern that this > feature allows subverting Secure Boot. If this feature is important to > you, I can investigate further and maybe add a patch to conditionally > disable it at run-time instead. The changes you've committed look fine. I have no need for CONFIG_ACPI_CONFIGFS. If it seems a risk, then I think it OK to have it disabled until a real need comes up. -Geoff
Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.
On 09/20/2018 12:49 PM, Geoff Levand wrote: > Attached are the two kernel config patches rebased to the latest v4.18.6-1 > Buster kernel. Forgot to include the rebased m400 fixup patch. 0001-arm64-Use-default-of-CONFIG_ACPI_NFIT-m.patch 0002-arm64-Updates-for-ACPI-servers.patch 0003-arm64-Add-fixup-for-HPE-m400-APEI-firmware-problems.patch -Geoff >From 63d1232a77b667090e2dd3fff0ac7868784850e9 Mon Sep 17 00:00:00 2001 From: Geoff Levand Date: Thu, 20 Sep 2018 12:23:55 -0700 Subject: [PATCH 1/8] [arm64] Use default of CONFIG_ACPI_NFIT=m Commit ed497f3cb706d0e0f63844b064d9ebbf6f33b052 (Add server and 96boards options) added an arm64 specific CONFIG_ACPI_NFIT=y, overriding the default of =m, but the commit message mentions nothing about why this was done. Remove the arm64 specific setting and use the default of module build. Cc: Riku Voipio Signed-off-by: Geoff Levand --- debian/config/arm64/config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/config/arm64/config b/debian/config/arm64/config index d14f3ff13174..0e0bf1b05db7 100644 --- a/debian/config/arm64/config +++ b/debian/config/arm64/config @@ -71,7 +71,7 @@ CONFIG_ACPI_NUMA=y ## ## file: drivers/acpi/nfit/Kconfig ## -CONFIG_ACPI_NFIT=y +CONFIG_ACPI_NFIT=m ## ## file: drivers/android/Kconfig -- 2.14.1 >From b1e30cf4155b5496234da7b1072f4c246cdfc9a1 Mon Sep 17 00:00:00 2001 From: Geoff Levand Date: Thu, 20 Sep 2018 12:23:55 -0700 Subject: [PATCH 2/8] [arm64] Updates for ACPI servers o Enable CONFIG_SCHED_SMT for hyperthreading processors. o Enable CONFIG_ARM64_LSE_ATOMICS for v8.1 processors. o Enable a number of ACPI options likely to be available on servers. o CONFIG_ACPI_APEI selects PSTORE, so remove the arm64 specific setting. Signed-off-by: Geoff Levand --- debian/config/arm64/config | 29 - 1 file changed, 24 insertions(+), 5 deletions(-) diff --git a/debian/config/arm64/config b/debian/config/arm64/config index 0e0bf1b05db7..1a6c6a41d6e4 100644 --- a/debian/config/arm64/config +++ b/debian/config/arm64/config @@ -9,6 +9,7 @@ CONFIG_ARM64_ERRATUM_834220=y CONFIG_ARM64_VA_BITS_48=y ## end choice CONFIG_SCHED_MC=y +CONFIG_SCHED_SMT=y CONFIG_NR_CPUS=256 CONFIG_NUMA=y CONFIG_SECCOMP=y @@ -24,6 +25,7 @@ CONFIG_RANDOMIZE_BASE=y CONFIG_RANDOMIZE_MODULE_REGION_FULL=y CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y CONFIG_COMPAT=y +CONFIG_ARM64_LSE_ATOMICS=y ## ## file: arch/arm64/crypto/Kconfig @@ -67,6 +69,21 @@ CONFIG_ARCH_XGENE=y ## CONFIG_ACPI=y CONFIG_ACPI_NUMA=y +CONFIG_ACPI_PCI_SLOT=y +CONFIG_ACPI_HED=y +CONFIG_ACPI_BGRT=y +CONFIG_ACPI_WATCHDOG=y +CONFIG_ACPI_CONFIGFS=m + +## +## file: drivers/acpi/apei/Kconfig +## +CONFIG_ACPI_APEI=y +CONFIG_ACPI_APEI_GHES=y +CONFIG_ACPI_APEI_PCIEAER=y +CONFIG_ACPI_APEI_SEA=y +CONFIG_ACPI_APEI_MEMORY_FAILURE=y +CONFIG_ACPI_APEI_EINJ=m ## ## file: drivers/acpi/nfit/Kconfig @@ -222,6 +239,12 @@ CONFIG_EXTCON_USB_GPIO=m ## CONFIG_RASPBERRYPI_FIRMWARE=y +## +## file: drivers/firmware/efi/Kconfig +## +CONFIG_UEFI_CPER=y +CONFIG_UEFI_CPER_ARM=y + ## ## file: drivers/gpio/Kconfig ## @@ -1097,6 +1120,7 @@ CONFIG_VIRTIO_MMIO=m ## file: drivers/watchdog/Kconfig ## CONFIG_GPIO_WATCHDOG=m +CONFIG_WDAT_WDT=m CONFIG_ARM_SP805_WATCHDOG=m CONFIG_ARM_SBSA_WATCHDOG=m CONFIG_DW_WATCHDOG=m @@ -1107,11 +1131,6 @@ CONFIG_MESON_GXBB_WATCHDOG=m CONFIG_MESON_WATCHDOG=m CONFIG_BCM2835_WDT=m -## -## file: fs/pstore/Kconfig -## -CONFIG_PSTORE=y - ## ## file: mm/Kconfig ## -- 2.14.1 >From 0fc33a4cfa3bb1ad35f18d161c9b78298dd08770 Mon Sep 17 00:00:00 2001 From: Geoff Levand Date: Thu, 20 Sep 2018 12:23:55 -0700 Subject: [PATCH 3/8] [arm64] Add fixup for HPE m400 APEI firmware problems Signed-off-by: Geoff Levand --- .../arm64-acpi-Add-fixup-for-HPE-m400-quirks.patch | 94 ++ debian/patches/series | 1 + 2 files changed, 95 insertions(+) create mode 100644 debian/patches/bugfix/arm64/arm64-acpi-Add-fixup-for-HPE-m400-quirks.patch diff --git a/debian/patches/bugfix/arm64/arm64-acpi-Add-fixup-for-HPE-m400-quirks.patch b/debian/patches/bugfix/arm64/arm64-acpi-Add-fixup-for-HPE-m400-quirks.patch new file mode 100644 index ..efd13e36faa0 --- /dev/null +++ b/debian/patches/bugfix/arm64/arm64-acpi-Add-fixup-for-HPE-m400-quirks.patch @@ -0,0 +1,94 @@ +From e0dc30ae9056c3c01423c75ea28c20fb135f72ad Mon Sep 17 00:00:00 2001 +From: Geoff Levand +Date: Wed, 13 Jun 2018 10:56:08 -0700 +Subject: [PATCH] arm64/acpi: Add fixup for HPE m400 quirks + +Adds a new ACPI init routine acpi_fixup_m400_quirks that adds +a work-around for HPE ProLiant m400 APEI firmware problems. + +The work-around disables APEI when CONFIG_ACPI_APEI is set and +m400 firmware is detected. Without this fixup m400 systems +experience errors like these on startup: + + [Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 2 + [Hardware Error]: event severity: fatal +
Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.
Hi Ben, Attached are the two kernel config patches rebased to the latest v4.18.6-1 Buster kernel. 0001-arm64-Use-default-of-CONFIG_ACPI_NFIT-m.patch 0002-arm64-Updates-for-ACPI-servers.patch Do you plan to merge these? If there is anything I can do to make things easier for you please let me know. -Geoff >From 63d1232a77b667090e2dd3fff0ac7868784850e9 Mon Sep 17 00:00:00 2001 From: Geoff Levand Date: Thu, 20 Sep 2018 12:23:55 -0700 Subject: [PATCH 1/8] [arm64] Use default of CONFIG_ACPI_NFIT=m Commit ed497f3cb706d0e0f63844b064d9ebbf6f33b052 (Add server and 96boards options) added an arm64 specific CONFIG_ACPI_NFIT=y, overriding the default of =m, but the commit message mentions nothing about why this was done. Remove the arm64 specific setting and use the default of module build. Cc: Riku Voipio Signed-off-by: Geoff Levand --- debian/config/arm64/config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/config/arm64/config b/debian/config/arm64/config index d14f3ff13174..0e0bf1b05db7 100644 --- a/debian/config/arm64/config +++ b/debian/config/arm64/config @@ -71,7 +71,7 @@ CONFIG_ACPI_NUMA=y ## ## file: drivers/acpi/nfit/Kconfig ## -CONFIG_ACPI_NFIT=y +CONFIG_ACPI_NFIT=m ## ## file: drivers/android/Kconfig -- 2.14.1 >From b1e30cf4155b5496234da7b1072f4c246cdfc9a1 Mon Sep 17 00:00:00 2001 From: Geoff Levand Date: Thu, 20 Sep 2018 12:23:55 -0700 Subject: [PATCH 2/8] [arm64] Updates for ACPI servers o Enable CONFIG_SCHED_SMT for hyperthreading processors. o Enable CONFIG_ARM64_LSE_ATOMICS for v8.1 processors. o Enable a number of ACPI options likely to be available on servers. o CONFIG_ACPI_APEI selects PSTORE, so remove the arm64 specific setting. Signed-off-by: Geoff Levand --- debian/config/arm64/config | 29 - 1 file changed, 24 insertions(+), 5 deletions(-) diff --git a/debian/config/arm64/config b/debian/config/arm64/config index 0e0bf1b05db7..1a6c6a41d6e4 100644 --- a/debian/config/arm64/config +++ b/debian/config/arm64/config @@ -9,6 +9,7 @@ CONFIG_ARM64_ERRATUM_834220=y CONFIG_ARM64_VA_BITS_48=y ## end choice CONFIG_SCHED_MC=y +CONFIG_SCHED_SMT=y CONFIG_NR_CPUS=256 CONFIG_NUMA=y CONFIG_SECCOMP=y @@ -24,6 +25,7 @@ CONFIG_RANDOMIZE_BASE=y CONFIG_RANDOMIZE_MODULE_REGION_FULL=y CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y CONFIG_COMPAT=y +CONFIG_ARM64_LSE_ATOMICS=y ## ## file: arch/arm64/crypto/Kconfig @@ -67,6 +69,21 @@ CONFIG_ARCH_XGENE=y ## CONFIG_ACPI=y CONFIG_ACPI_NUMA=y +CONFIG_ACPI_PCI_SLOT=y +CONFIG_ACPI_HED=y +CONFIG_ACPI_BGRT=y +CONFIG_ACPI_WATCHDOG=y +CONFIG_ACPI_CONFIGFS=m + +## +## file: drivers/acpi/apei/Kconfig +## +CONFIG_ACPI_APEI=y +CONFIG_ACPI_APEI_GHES=y +CONFIG_ACPI_APEI_PCIEAER=y +CONFIG_ACPI_APEI_SEA=y +CONFIG_ACPI_APEI_MEMORY_FAILURE=y +CONFIG_ACPI_APEI_EINJ=m ## ## file: drivers/acpi/nfit/Kconfig @@ -222,6 +239,12 @@ CONFIG_EXTCON_USB_GPIO=m ## CONFIG_RASPBERRYPI_FIRMWARE=y +## +## file: drivers/firmware/efi/Kconfig +## +CONFIG_UEFI_CPER=y +CONFIG_UEFI_CPER_ARM=y + ## ## file: drivers/gpio/Kconfig ## @@ -1097,6 +1120,7 @@ CONFIG_VIRTIO_MMIO=m ## file: drivers/watchdog/Kconfig ## CONFIG_GPIO_WATCHDOG=m +CONFIG_WDAT_WDT=m CONFIG_ARM_SP805_WATCHDOG=m CONFIG_ARM_SBSA_WATCHDOG=m CONFIG_DW_WATCHDOG=m @@ -1107,11 +1131,6 @@ CONFIG_MESON_GXBB_WATCHDOG=m CONFIG_MESON_WATCHDOG=m CONFIG_BCM2835_WDT=m -## -## file: fs/pstore/Kconfig -## -CONFIG_PSTORE=y - ## ## file: mm/Kconfig ## -- 2.14.1
Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.
Hi Ben, On 09/04/2018 10:25 AM, Ben Hutchings wrote: > On Fri, 2018-08-31 at 15:42 -0700, Geoff Levand wrote: >> I've rebased my two kernel config patches, attached, to the latest >> v4.17.17-1 buster kernel. These patches enable kernel features for >> newer ARM64 servers. >> >> 0001-arm64-Use-default-of-CONFIG_ACPI_NFIT-m.patch >> 0002-arm64-Updates-for-ACPI-servers.patch >> >> The issue that Riku brought up of how to support HPE m400 moonshot >> systems when ACPI_APEI is enabled has been resolved on the >> arm-kernel ML [1]. In summary, the latest released m400 firmware >> did not support APEI, and so no special work-around or kernel quirk >> support is needed. >> >> With the resolution of that issue I feel these patches are ready to >> apply. Please consider. > > Is it resolved? Graeme Gregory claimed > (https://www.spinics.net/lists/arm-kernel/msg669946.html) that "most > people are running the firmware provided from HPe support but was never > put on release site". I took that as just a comment on the discussion which it follows, which seemed to end with 'distro maintainers deciding how to handle the problem' and then Riku recommending to document the need in Debian for a m400 specific command line option. Based on the several mail list discussions that came out of this I think it very unlikely we'll get an upstream kernel fix. My appeal directly to Will Deacon for guidance even went unanswered. At this point I feel our choices are: 1) Merge the kernel config patch I proposed and add a comment to the arm64 Installation Guide about the need to add 'hest_disable=1' to the kernel command line for the m400. 2) Merge the kernel config patch and the 'Add fix for broken HPE moonshot ACPI-APEI support' patch I proposed. 3) Remove the CONFIG_ACPI_APEI options from the the kernel config patch I proposed and merge that. I prefer #2, which would get us ACPI_APEI support and a seamless install for m400 users. If there is anything you recommend I could try it. I'm not apposed to any solution. I just want to get the kernel config updated so Buster better supports newer systems. -Geoff
Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.
Hi, I've rebased my two kernel config patches, attached, to the latest v4.17.17-1 buster kernel. These patches enable kernel features for newer ARM64 servers. 0001-arm64-Use-default-of-CONFIG_ACPI_NFIT-m.patch 0002-arm64-Updates-for-ACPI-servers.patch The issue that Riku brought up of how to support HPE m400 moonshot systems when ACPI_APEI is enabled has been resolved on the arm-kernel ML [1]. In summary, the latest released m400 firmware did not support APEI, and so no special work-around or kernel quirk support is needed. With the resolution of that issue I feel these patches are ready to apply. Please consider. [1] https://www.spinics.net/lists/arm-kernel/msg670446.html (efi: add contents of LinuxExtraArgs EFI var to command line) -Geoff >From 7d93f2d534f3ba60b94402b337e165d34e1caf25 Mon Sep 17 00:00:00 2001 From: Geoff Levand Date: Wed, 13 Jun 2018 10:50:57 -0700 Subject: [PATCH 1/7] [arm64] Use default of CONFIG_ACPI_NFIT=m Commit ed497f3cb706d0e0f63844b064d9ebbf6f33b052 (Add server and 96boards options) added an arm64 specific CONFIG_ACPI_NFIT=y, overriding the default of =m, but the commit message mentions nothing about why this was done. Remove the arm64 specific setting and use the default of module build. Cc: Riku Voipio Signed-off-by: Geoff Levand --- debian/config/arm64/config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/config/arm64/config b/debian/config/arm64/config index adf3e60bd9f5..72f2dadc16e3 100644 --- a/debian/config/arm64/config +++ b/debian/config/arm64/config @@ -71,7 +71,7 @@ CONFIG_ACPI_NUMA=y ## ## file: drivers/acpi/nfit/Kconfig ## -CONFIG_ACPI_NFIT=y +CONFIG_ACPI_NFIT=m ## ## file: drivers/android/Kconfig -- 2.14.1 >From 10f4c4399f54d99f293047c3d6dfeba08849526e Mon Sep 17 00:00:00 2001 From: Geoff Levand Date: Wed, 13 Jun 2018 10:50:57 -0700 Subject: [PATCH 2/7] [arm64] Updates for ACPI servers o Enable CONFIG_SCHED_SMT for hyperthreading processors. o Enable CONFIG_ARM64_LSE_ATOMICS for v8.1 processors. o Enable a number of ACPI options likely to be available on servers. o CONFIG_ACPI_APEI selects PSTORE, so remove the arm64 specific setting. Signed-off-by: Geoff Levand --- debian/config/arm64/config | 29 - 1 file changed, 24 insertions(+), 5 deletions(-) diff --git a/debian/config/arm64/config b/debian/config/arm64/config index 72f2dadc16e3..250395babf59 100644 --- a/debian/config/arm64/config +++ b/debian/config/arm64/config @@ -9,6 +9,7 @@ CONFIG_ARM64_ERRATUM_834220=y CONFIG_ARM64_VA_BITS_48=y ## end choice CONFIG_SCHED_MC=y +CONFIG_SCHED_SMT=y CONFIG_NR_CPUS=256 CONFIG_NUMA=y CONFIG_SECCOMP=y @@ -24,6 +25,7 @@ CONFIG_RANDOMIZE_BASE=y CONFIG_RANDOMIZE_MODULE_REGION_FULL=y CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y CONFIG_COMPAT=y +CONFIG_ARM64_LSE_ATOMICS=y ## ## file: arch/arm64/crypto/Kconfig @@ -67,6 +69,21 @@ CONFIG_ARCH_XGENE=y ## CONFIG_ACPI=y CONFIG_ACPI_NUMA=y +CONFIG_ACPI_PCI_SLOT=y +CONFIG_ACPI_HED=y +CONFIG_ACPI_BGRT=y +CONFIG_ACPI_WATCHDOG=y +CONFIG_ACPI_CONFIGFS=m + +## +## file: drivers/acpi/apei/Kconfig +## +CONFIG_ACPI_APEI=y +CONFIG_ACPI_APEI_GHES=y +CONFIG_ACPI_APEI_PCIEAER=y +CONFIG_ACPI_APEI_SEA=y +CONFIG_ACPI_APEI_MEMORY_FAILURE=y +CONFIG_ACPI_APEI_EINJ=m ## ## file: drivers/acpi/nfit/Kconfig @@ -222,6 +239,12 @@ CONFIG_EXTCON_USB_GPIO=m ## CONFIG_RASPBERRYPI_FIRMWARE=y +## +## file: drivers/firmware/efi/Kconfig +## +CONFIG_UEFI_CPER=y +CONFIG_UEFI_CPER_ARM=y + ## ## file: drivers/gpio/Kconfig ## @@ -1097,6 +1120,7 @@ CONFIG_VIRTIO_MMIO=m ## file: drivers/watchdog/Kconfig ## CONFIG_GPIO_WATCHDOG=m +CONFIG_WDAT_WDT=m CONFIG_ARM_SP805_WATCHDOG=m CONFIG_ARM_SBSA_WATCHDOG=m CONFIG_DW_WATCHDOG=m @@ -1107,11 +1131,6 @@ CONFIG_MESON_GXBB_WATCHDOG=m CONFIG_MESON_WATCHDOG=m CONFIG_BCM2835_WDT=m -## -## file: fs/pstore/Kconfig -## -CONFIG_PSTORE=y - ## ## file: mm/Kconfig ## -- 2.14.1
Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.
Hi, I've rebased my two kernel config patches, attached, to the latest v4.17.17-1 buster kernel. These patches enable kernel features for newer ARM64 servers. 0001-arm64-Use-default-of-CONFIG_ACPI_NFIT-m.patch 0002-arm64-Updates-for-ACPI-servers.patch The issue that Riku brought up of how to support HPE m400 moonshot systems when ACPI_APEI is enabled has been resolved on the arm-kernel ML [1]. In summary, the latest released m400 firmware did not support APEI, and so no special work-around or kernel quirk support is needed. With the resolution of that issue I feel these patches are ready to apply. Please consider. [1] https://www.spinics.net/lists/arm-kernel/msg670446.html (efi: add contents of LinuxExtraArgs EFI var to command line) -Geoff >From 7d93f2d534f3ba60b94402b337e165d34e1caf25 Mon Sep 17 00:00:00 2001 From: Geoff Levand Date: Wed, 13 Jun 2018 10:50:57 -0700 Subject: [PATCH 1/7] [arm64] Use default of CONFIG_ACPI_NFIT=m Commit ed497f3cb706d0e0f63844b064d9ebbf6f33b052 (Add server and 96boards options) added an arm64 specific CONFIG_ACPI_NFIT=y, overriding the default of =m, but the commit message mentions nothing about why this was done. Remove the arm64 specific setting and use the default of module build. Cc: Riku Voipio Signed-off-by: Geoff Levand --- debian/config/arm64/config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/config/arm64/config b/debian/config/arm64/config index adf3e60bd9f5..72f2dadc16e3 100644 --- a/debian/config/arm64/config +++ b/debian/config/arm64/config @@ -71,7 +71,7 @@ CONFIG_ACPI_NUMA=y ## ## file: drivers/acpi/nfit/Kconfig ## -CONFIG_ACPI_NFIT=y +CONFIG_ACPI_NFIT=m ## ## file: drivers/android/Kconfig -- 2.14.1 >From 10f4c4399f54d99f293047c3d6dfeba08849526e Mon Sep 17 00:00:00 2001 From: Geoff Levand Date: Wed, 13 Jun 2018 10:50:57 -0700 Subject: [PATCH 2/7] [arm64] Updates for ACPI servers o Enable CONFIG_SCHED_SMT for hyperthreading processors. o Enable CONFIG_ARM64_LSE_ATOMICS for v8.1 processors. o Enable a number of ACPI options likely to be available on servers. o CONFIG_ACPI_APEI selects PSTORE, so remove the arm64 specific setting. Signed-off-by: Geoff Levand --- debian/config/arm64/config | 29 - 1 file changed, 24 insertions(+), 5 deletions(-) diff --git a/debian/config/arm64/config b/debian/config/arm64/config index 72f2dadc16e3..250395babf59 100644 --- a/debian/config/arm64/config +++ b/debian/config/arm64/config @@ -9,6 +9,7 @@ CONFIG_ARM64_ERRATUM_834220=y CONFIG_ARM64_VA_BITS_48=y ## end choice CONFIG_SCHED_MC=y +CONFIG_SCHED_SMT=y CONFIG_NR_CPUS=256 CONFIG_NUMA=y CONFIG_SECCOMP=y @@ -24,6 +25,7 @@ CONFIG_RANDOMIZE_BASE=y CONFIG_RANDOMIZE_MODULE_REGION_FULL=y CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y CONFIG_COMPAT=y +CONFIG_ARM64_LSE_ATOMICS=y ## ## file: arch/arm64/crypto/Kconfig @@ -67,6 +69,21 @@ CONFIG_ARCH_XGENE=y ## CONFIG_ACPI=y CONFIG_ACPI_NUMA=y +CONFIG_ACPI_PCI_SLOT=y +CONFIG_ACPI_HED=y +CONFIG_ACPI_BGRT=y +CONFIG_ACPI_WATCHDOG=y +CONFIG_ACPI_CONFIGFS=m + +## +## file: drivers/acpi/apei/Kconfig +## +CONFIG_ACPI_APEI=y +CONFIG_ACPI_APEI_GHES=y +CONFIG_ACPI_APEI_PCIEAER=y +CONFIG_ACPI_APEI_SEA=y +CONFIG_ACPI_APEI_MEMORY_FAILURE=y +CONFIG_ACPI_APEI_EINJ=m ## ## file: drivers/acpi/nfit/Kconfig @@ -222,6 +239,12 @@ CONFIG_EXTCON_USB_GPIO=m ## CONFIG_RASPBERRYPI_FIRMWARE=y +## +## file: drivers/firmware/efi/Kconfig +## +CONFIG_UEFI_CPER=y +CONFIG_UEFI_CPER_ARM=y + ## ## file: drivers/gpio/Kconfig ## @@ -1097,6 +1120,7 @@ CONFIG_VIRTIO_MMIO=m ## file: drivers/watchdog/Kconfig ## CONFIG_GPIO_WATCHDOG=m +CONFIG_WDAT_WDT=m CONFIG_ARM_SP805_WATCHDOG=m CONFIG_ARM_SBSA_WATCHDOG=m CONFIG_DW_WATCHDOG=m @@ -1107,11 +1131,6 @@ CONFIG_MESON_GXBB_WATCHDOG=m CONFIG_MESON_WATCHDOG=m CONFIG_BCM2835_WDT=m -## -## file: fs/pstore/Kconfig -## -CONFIG_PSTORE=y - ## ## file: mm/Kconfig ## -- 2.14.1
Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.
Hi All, On 08/06/2018 06:29 AM, Riku Voipio wrote: > Thanks indeed - unfortunately we seem to be endind up in > a dead end with the upstream developers: > > https://www.spinics.net/lists/arm-kernel/msg669674.html > > Considering HPE didn't actually release the firmware, I think we > can go with just enabling the options and documenting the command line > option. Just to mention it, I went through and verified the info James Morse had posted regarding m400 System ROM releases [1] and came to the same conclusion; the latest official release of m400 System ROM did not support ACPI HEST/AEPI. [1] https://www.spinics.net/lists/arm-kernel/msg670446.html -Geoff
Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.
On 06/09/2018 05:15 AM, Ian Campbell wrote: > I think this is probably something for the arch (or perhaps platform) > code to deal with. See for example all the various platform quirks in > arch/x86/kernel/acpi/boot.c, which fixup various wrongness and/or > disable features. I followed your advice and created a fix in the arm64 acpi init code of arch/arm64/kernel/acpi.c. Here's the submission: https://marc.info/?l=linux-acpi=152891415600796=2 https://www.spinics.net/lists/linux-acpi/msg82887.html
Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.
On 06/05/2018 12:28 AM, Ian Campbell wrote:
> On Tue, 2018-06-05 at 02:14 +0100, Ben Hutchings wrote:
>
>> I don't think it's OK to cause a regression like this. Since this is
>> problem affects a specific known platform, the driver ought to
>> recognise it and disable itself automatically.
>
> Indeed, while the Fedora bug upthread claims such a patch wouldn't be
> upstreamable, AFAIK it is not uncommon to have such quirks for broken
> firmware based upon DMI identifiers or similar.
Just to mention it, Mark Salter submitted one of the work-around patches
for the m400 firmware. The reply from the ACPI maintainer wasn't very
encouraging. See:
https://lkml.org/lkml/2018/4/19/1020 (ACPI / scan: Fix regression related to
X-Gene UARTs)
CONFIG_ACPI_APEI allows for automated error reporting, so it is something
that is very desirable for unattended servers in a production environment.
Mark sent me a minimal patch that allows CONFIG_ACPI_APEI to work on m400.
I've attached a patch that puts his patch into the kernel patch series.
arm64-Add-fix-for-broken-HPE-moonshot-ACPI-APEI-supp.patch
Is this an acceptable solution?
>From e2bbf7bd8ef0231dcaa440a5baa8722a11634f75 Mon Sep 17 00:00:00 2001
From: Geoff Levand
Date: Fri, 8 Jun 2018 10:52:29 -0700
Subject: [PATCH] [arm64] Add fix for broken HPE moonshot ACPI-APEI support
Signed-off-by: Geoff Levand
---
...4-Ignore-broken-HPE-moonshot-APEI-support.patch | 39 ++
debian/patches/series | 1 +
2 files changed, 40 insertions(+)
create mode 100644 debian/patches/bugfix/arm64/ACPI-APEI-arm64-Ignore-broken-HPE-moonshot-APEI-support.patch
diff --git a/debian/patches/bugfix/arm64/ACPI-APEI-arm64-Ignore-broken-HPE-moonshot-APEI-support.patch b/debian/patches/bugfix/arm64/ACPI-APEI-arm64-Ignore-broken-HPE-moonshot-APEI-support.patch
new file mode 100644
index ..ca7a7bf67258
--- /dev/null
+++ b/debian/patches/bugfix/arm64/ACPI-APEI-arm64-Ignore-broken-HPE-moonshot-APEI-support.patch
@@ -0,0 +1,39 @@
+From 2c4be2497e1cdbeaeee2decd9f85bfd9926d0321 Mon Sep 17 00:00:00 2001
+From: Mark Salter
+Date: Tue, 27 Feb 2018 00:21:23 -0500
+Subject: [PATCH] ACPI: APEI: arm64: Ignore broken HPE moonshot APEI support
+
+The aarch64 HP moonshot platforms have a firmware bug which causes a
+spurious fatal memory error via APEI at boot time. This platform is no
+longer supported and no further firmware updates are expected. This is
+a downstream-only hack to avoid the problem by bailing out of HEST
+table probing if we detect a moonshot HEST table.
+
+Signed-off-by: Mark Salter
+Signed-off-by: Geoff Levand
+---
+ drivers/acpi/apei/hest.c | 8
+ 1 file changed, 8 insertions(+)
+
+diff --git a/drivers/acpi/apei/hest.c b/drivers/acpi/apei/hest.c
+index 9cb74115a43d..9305daabe24c 100644
+--- a/drivers/acpi/apei/hest.c
b/drivers/acpi/apei/hest.c
+@@ -89,6 +89,14 @@ int apei_hest_parse(apei_hest_func_t func, void *data)
+ if (hest_disable || !hest_tab)
+ return -EINVAL;
+
++#ifdef CONFIG_ARM64
++ /* Ignore broken firmware */
++ if (!strncmp(hest_tab->header.oem_id, "HPE ", 6) &&
++ !strncmp(hest_tab->header.oem_table_id, "ProLiant", 8) &&
++ MIDR_IMPLEMENTOR(read_cpuid_id()) == ARM_CPU_IMP_APM)
++ return -EINVAL;
++#endif
++
+ hest_hdr = (struct acpi_hest_header *)(hest_tab + 1);
+ for (i = 0; i < hest_tab->error_source_count; i++) {
+ len = hest_esrc_len(hest_hdr);
+--
+2.14.1
+
diff --git a/debian/patches/series b/debian/patches/series
index cb1d40074141..d77fa2bf4faf 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -68,6 +68,7 @@ bugfix/x86/perf-tools-fix-unwind-build-on-i386.patch
bugfix/sh/sh-boot-do-not-use-hyphen-in-exported-variable-name.patch
bugfix/x86/mmap-remember-the-map_fixed-flag-as-vm_fixed.patch
bugfix/x86/mmap-add-an-exception-to-the-stack-gap-for-hotspot-jvm.patch
+bugfix/arm64/ACPI-APEI-arm64-Ignore-broken-HPE-moonshot-APEI-support.patch
# Arch features
features/mips/MIPS-increase-MAX-PHYSMEM-BITS-on-Loongson-3-only.patch
--
2.14.1
Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.
On 06/04/2018 03:51 AM, Riku Voipio wrote: > On Fri, Jun 01, 2018 at 10:07:57AM -0700, Geoff Levand wrote: >> o Change CONFIG_ACPI_NFIT=y to CONFIG_ACPI_NFIT=m. >> o Enable CONFIG_SCHED_SMT for hyperthreading processors. >> o Enable CONFIG_ARM64_LSE_ATOMICS for v8.1 processors. >> o Enable a number of ACPI options likely to be available on servers. >> o CONFIG_ACPI_APEI selects PSTORE, so remove the arm64 specific setting. > > ACPI_APEI breaks HP m400, the xgene moonshot: > > https://bugzilla.redhat.com/show_bug.cgi?id=1574718 > > The rest of options are generally fine. Wish more of these were modules tho. > If we ok with telling M400 users to setting kernel command line of > ghes.disable=1, > we can enable APEI as well. I think the hardware error logging/reporting features ACPI_APEI allows is desired for servers. The M400 problem is a problem with its firmware. I don't think we should hold everyone else back because of one platform with a known problem and relatively straight forward fix. M400 users would in general need to work around the problem with kernels from other sources/distros. So, I think it OK to require M400 users to add a command line fix. >> -- System Information: >> Debian Release: buster/sid >> APT prefers testing >> APT policy: (500, 'testing') >> Architecture: arm64 (aarch64) >> >> Kernel: Linux 4.16.12 (SMP w/224 CPU cores) > > Cheeky. I take that means Debian kernel works well on you plaform. Seems to be working good with the kernel config updates.
Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.
X-Debbugs-Cc: ge...@infradead.org, Riku Voipio Source: linux Severity: normal Tags: patch buster Attached patches enable kernel features for newer ARM64 servers. o Change CONFIG_ACPI_NFIT=y to CONFIG_ACPI_NFIT=m. o Enable CONFIG_SCHED_SMT for hyperthreading processors. o Enable CONFIG_ARM64_LSE_ATOMICS for v8.1 processors. o Enable a number of ACPI options likely to be available on servers. o CONFIG_ACPI_APEI selects PSTORE, so remove the arm64 specific setting. 0001-arm64-Use-default-of-CONFIG_ACPI_NFIT-m.patch 0002-arm64-Updates-for-ACPI-servers.patch -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 4.16.12 (SMP w/224 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) >From 45de8904c961d98f48f61a87198579a90daa61f9 Mon Sep 17 00:00:00 2001 From: Geoff Levand Date: Thu, 31 May 2018 17:38:38 -0700 Subject: [PATCH 1/4] [arm64] Use default of CONFIG_ACPI_NFIT=m Commit ed497f3cb706d0e0f63844b064d9ebbf6f33b052 (Add server and 96boards options) added an arm64 specific CONFIG_ACPI_NFIT=y, overriding the default of =m, but the commit message mentions nothing about why this was done. Remove the arm64 specific setting and use the default of module build. Cc: Riku Voipio Signed-off-by: Geoff Levand --- debian/config/arm64/config | 5 - 1 file changed, 5 deletions(-) diff --git a/debian/config/arm64/config b/debian/config/arm64/config index 4d862989014c..2cbdc9092de1 100644 --- a/debian/config/arm64/config +++ b/debian/config/arm64/config @@ -68,11 +68,6 @@ CONFIG_ARCH_XGENE=y CONFIG_ACPI=y CONFIG_ACPI_NUMA=y -## -## file: drivers/acpi/nfit/Kconfig -## -CONFIG_ACPI_NFIT=y - ## ## file: drivers/ata/Kconfig ## -- 2.14.1 >From 60439ed76d7c9660285d8805d40d35a84de218d3 Mon Sep 17 00:00:00 2001 From: Geoff Levand Date: Thu, 31 May 2018 17:38:38 -0700 Subject: [PATCH 2/4] [arm64] Updates for ACPI servers o Enable CONFIG_SCHED_SMT for hyperthreading processors. o Enable CONFIG_ARM64_LSE_ATOMICS for v8.1 processors. o Enable a number of ACPI options likely to be available on servers. o CONFIG_ACPI_APEI selects PSTORE, so remove the arm64 specific setting. Signed-off-by: Geoff Levand --- debian/config/arm64/config | 29 - 1 file changed, 24 insertions(+), 5 deletions(-) diff --git a/debian/config/arm64/config b/debian/config/arm64/config index 2cbdc9092de1..ed40c33ce47d 100644 --- a/debian/config/arm64/config +++ b/debian/config/arm64/config @@ -9,6 +9,7 @@ CONFIG_ARM64_ERRATUM_834220=y CONFIG_ARM64_VA_BITS_48=y ## end choice CONFIG_SCHED_MC=y +CONFIG_SCHED_SMT=y CONFIG_NR_CPUS=256 CONFIG_NUMA=y CONFIG_SECCOMP=y @@ -24,6 +25,7 @@ CONFIG_RANDOMIZE_BASE=y CONFIG_RANDOMIZE_MODULE_REGION_FULL=y CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y CONFIG_COMPAT=y +CONFIG_ARM64_LSE_ATOMICS=y ## ## file: arch/arm64/crypto/Kconfig @@ -67,6 +69,21 @@ CONFIG_ARCH_XGENE=y ## CONFIG_ACPI=y CONFIG_ACPI_NUMA=y +CONFIG_ACPI_PCI_SLOT=y +CONFIG_ACPI_HED=y +CONFIG_ACPI_BGRT=y +CONFIG_ACPI_WATCHDOG=y +CONFIG_ACPI_CONFIGFS=m + +## +## file: drivers/acpi/apei/Kconfig +## +CONFIG_ACPI_APEI=y +CONFIG_ACPI_APEI_GHES=y +CONFIG_ACPI_APEI_PCIEAER=y +CONFIG_ACPI_APEI_SEA=y +CONFIG_ACPI_APEI_MEMORY_FAILURE=y +CONFIG_ACPI_APEI_EINJ=m ## ## file: drivers/ata/Kconfig @@ -212,6 +229,12 @@ CONFIG_EXTCON_USB_GPIO=m ## CONFIG_RASPBERRYPI_FIRMWARE=y +## +## file: drivers/firmware/efi/Kconfig +## +CONFIG_UEFI_CPER=y +CONFIG_UEFI_CPER_ARM=y + ## ## file: drivers/gpio/Kconfig ## @@ -1074,6 +1097,7 @@ CONFIG_VIRTIO_MMIO=m ## file: drivers/watchdog/Kconfig ## CONFIG_GPIO_WATCHDOG=m +CONFIG_WDAT_WDT=m CONFIG_ARM_SP805_WATCHDOG=m CONFIG_ARM_SBSA_WATCHDOG=m CONFIG_DW_WATCHDOG=m @@ -1084,11 +1108,6 @@ CONFIG_MESON_GXBB_WATCHDOG=m CONFIG_MESON_WATCHDOG=m CONFIG_BCM2835_WDT=m -## -## file: fs/pstore/Kconfig -## -CONFIG_PSTORE=y - ## ## file: mm/Kconfig ## -- 2.14.1
Bug#900036: firmware-nonfree: Buster kernel needs updated (upstream) firmware versions
X-Debbugs-Cc: ge...@infradead.org Package: firmware-nonfree Version: 20170823-1 Severity: grave Tags: d-i Justification: renders package unusable The current firmware-nonfree package is out of date and does not include firmware files the drivers in the Buster kernel require. Specifically, the Buster kernel driver (qede) for QLogic network adapters needs firmware 'qed_init_values_zipped-8.33.1.0.bin', which is available in the upstream kernel firmware from commit [1], but this is not included in the current firmware-nonfree package. This situation makes it very difficult for users trying to netboot install to machines with QLogic network adapters (Cavium Thunder2). >From the kernel log: qede :0a:00.0: firmware: failed to load qed/qed_init_values_zipped-8.33.1.0.bin [1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/qed?id=5582ca4caff8dc029b136722d11e7df6f40888ad -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 4.16.0-1-arm64 (SMP w/224 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#804273: (no subject)
Hi, On Tue, 2015-11-17 at 09:48 -0500, Breno Leitao wrote: > Any feedback about this patch? this bug is quite important for > ppc64el. Sorry for the delay. I think the best solution is to drop the libtwin package. -Geoff
Bug#803133: 803133
This has not yet been fixed upstream. The referenced patch in my coreos--coreos-overlay repo is just a local work-around that reverts the etcd v2.1.2 to v2.2.0 update.
Bug#620296: ps3-utils uploaded to mentors.debian.net
Hi Ana, On Thu, 2014-12-18 at 16:22 +0100, Ana Guerrero Lopez wrote: On Thu, May 30, 2013 at 04:32:29PM -0700, Geoff Levand wrote: Hi Sean, I updated the ps3-utils package to bring it up to the latest sources, which fixes a few bugs, and also brought the debian build system files up to date. I put myself down as package maintainer, since it seemed to make sense to do so. I would certainly appreciate if you would act as sponsor and review the package and upload if it looks OK. Hi Geoff, I'm sorry nobody replied this bug report. Sean has retired from Debian and from the Debian QA team, we were looking at orphaning his packages. Given the low popularity of this one, I was about to file for its removal but if you're still interested, you could adopt it as you stated in this email. The challenge here is there are not so much people with powerpc machine or interest who could upload the package for you. That's probably the reason why your package didn't receive that much attention at mentors.debian.net I think there are still users interested in having this package in Debian, so I would like to try to continue its maintenance. If you could suggest a mentor who could help to do the uploads I would certainly appreciate it. -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744623: (no subject)
Hi Ben, On Wed, 2014-10-22 at 10:53 +1100, Benjamin Herrenschmidt wrote: On Tue, 2014-10-21 at 16:23 -0700, Geoff Levand wrote: X-Debbugs-CC: Benjamin Herrenschmidt b...@kernel.crashing.org On Tue, 2014-10-21 at 09:41 -0200, Breno Leitao wrote: Any status about this bug? This is caused by the altivec optimized routines done by Ben Herrenschmidt. I've tried to fix those up, but could never figure them out enough to do so. The quick fix is to add --enable-altivec=no to the powerpc build. The proper fix is to update the altivec routines. Ben, do you want to give that a try? libtwin/twin_primitive.c:292:38: error: incompatible types when initializing type '__vector unsigned short' using type '__vector unsigned char' const vector unsigned short v8 = vec_splat_u8(8); ^ libtwin/twin_primitive.c:309:9: error: incompatible types when assigning to type '__vector unsigned char' from type '__vector unsigned short' dst = vec_perm(dmule, dmulo, merge); ^ yeah it looks bad ... not sure what's up there, I'll need to context switch a pile of old crap back into my brain.. Where do you keep that libtwin ? Or is it the upstream fdo one ? git://git.kernel.org/pub/scm/linux/kernel/git/geoff/libtwin.git Thanks for taking a look. -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744623: (no subject)
X-Debbugs-CC: Benjamin Herrenschmidt b...@kernel.crashing.org Hi, On Tue, 2014-10-21 at 09:41 -0200, Breno Leitao wrote: Hi Geoff, Any status about this bug? This is caused by the altivec optimized routines done by Ben Herrenschmidt. I've tried to fix those up, but could never figure them out enough to do so. The quick fix is to add --enable-altivec=no to the powerpc build. The proper fix is to update the altivec routines. Ben, do you want to give that a try? libtwin/twin_primitive.c:292:38: error: incompatible types when initializing type '__vector unsigned short' using type '__vector unsigned char' const vector unsigned short v8 = vec_splat_u8(8); ^ libtwin/twin_primitive.c:309:9: error: incompatible types when assigning to type '__vector unsigned char' from type '__vector unsigned short' dst = vec_perm(dmule, dmulo, merge); ^ -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722542: gcc-spu went away but is still being used
Hi, On Thu, 2013-09-12 at 14:37 +0200, Matthias Klose wrote: Control: reassign -1 newlib Am 12.09.2013 08:31, schrieb Niels Thykier: Package: gcc-defaults,newlib Severity: important Dear maintainers of gcc-defaults and newlib, I noticed that gcc-defaults have removed the gnu-spu package in sid, but newlib still build-depends on it. Since there was no bug against either package, I am assuming no one has noticed this so far. As it is, this is one (of several) things blocking gcc-defaults migration to testing. This bug can be fixed either by re-introducing gcc-spu (possibly as a transitional package, if gcc-spu is no longer needed) or by newlib no longer Build-Depending on gcc-spu (since it is the last package using it). I will leave it to you to decide how this will be solved; please reassign this bug to the proper package. I don't maintain the spu cross toolchain anymore, as previously written to the gcc and powerpc ML. So newlib maybe shouldn't build the spu packages anymore. I guess this means users will also need to build newlib (in addition to the gnu-spu) if they want to do spu programming for cell. Matthias, please let us know in general what a user needs to do for this. -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619236: debian PS3 installation kboot.conf needed
We still have a need for the kboot-utils package in debian. Recent daily builds of D-I work fine on PS3, but the installed system still cannot boot due to lack of a kboot.conf file for the PS3's native bootloader (petitboot). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719040: installation-report: debian 7.1 wheezy installation success on PS3
Package: installation-reports Version: 2.49 Severity: normal Dear Maintainer, Installed from CD-ROM media. Install went as expected. Followed the PS3 install instructions here: https://www.kernel.org/pub/linux/kernel/people/geoff/cell/ps3-howto/ps3-debian-install-howto.txt -- Package-specific info: Boot method: network Image version: debian-7.1.0-powerpc-netinst.iso Date: August 7, 2013 Machine: Sony PS3 Game Console Partitions: df -Tl will do; the raw partition table is preferred 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:[E] Overall install:[O] Comments/Problems: Needed to add /etc/kboot.conf manually after install finished as described in ps3-debian-install-howto.txt. -- == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=7 (wheezy) - installer build 20130613 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux ps3 3.2.0-4-powerpc64 #1 SMP Debian 3.2.46-1 ppc64 GNU/Linux usb-list: usb-list: Bus 01 Device 01: PS3 EHCI Host Controller [1d6b:0002] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 00 usb-list:Manufacturer: Linux 3.2.0-4-powerpc64 ehci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 01 Device 02: USB2.0 Hub [05e3:0607] usb-list:Level 01 Parent 01 Port 01 Class 09(hub ) Subclass 00 Protocol 02 usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 02 Driver hub usb-list: usb-list: Bus 01 Device 03: Generic USB Hub [04fe:0008] usb-list:Level 02 Parent 02 Port 00 Class 09(hub ) Subclass 00 Protocol 00 usb-list:Manufacturer: Chicony usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 01 Device 04: PFU-65 USB Keyboard [04fe:0006] usb-list:Level 03 Parent 03 Port 00 Class 00(ifc ) Subclass 00 Protocol 00 usb-list:Manufacturer: Chicony usb-list:Interface 00: Class 03(HID ) Subclass 01 Protocol 01 Driver usbhid usb-list: usb-list: Bus 01 Device 05: USB Optical Mouse [192f:0416] usb-list:Level 03 Parent 03 Port 02 Class 00(ifc ) Subclass 00 Protocol 00 usb-list:Interface 00: Class 03(HID ) Subclass 01 Protocol 02 Driver usbhid usb-list: usb-list: Bus 02 Device 01: PS3 EHCI Host Controller [1d6b:0002] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 00 usb-list:Manufacturer: Linux 3.2.0-4-powerpc64 ehci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 02 Device 02: Bluetooth Transceiver [054c:0267] usb-list:Level 01 Parent 01 Port 01 Class e0(wlcon) Subclass 01 Protocol 01 usb-list:Manufacturer: Sony usb-list:Interface 00: Class e0(wlcon) Subclass 01 Protocol 01 Driver none usb-list:Interface 01: Class e0(wlcon) Subclass 01 Protocol 01 Driver none usb-list:Interface 02: Class e0(wlcon) Subclass 01 Protocol 01 Driver none usb-list:Interface 03: Class fe(app. ) Subclass 01 Protocol 00 Driver none usb-list: usb-list: Bus 03 Device 01: PS3 OHCI Host Controller [1d6b:0001] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 00 usb-list:Manufacturer: Linux 3.2.0-4-powerpc64 ohci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 04 Device 01: PS3 OHCI Host Controller [1d6b:0001] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 00 usb-list:Manufacturer: Linux 3.2.0-4-powerpc64 ohci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub lsmod: Module Size Used by lsmod: binfmt_misc12959 1 lsmod: nls_utf83660 0 lsmod: dm_mod 93728 0 lsmod: md_mod119708 0 lsmod: xfs 769865 0 lsmod: jfs 188224 0 lsmod: ext4 459391 1 lsmod: crc16 3076 1 ext4 lsmod: jbd2 84639 1 ext4 lsmod: ext3 212973 0 lsmod: jbd75718 1 ext3 lsmod: btrfs 730845 0 lsmod: crc32c 5187 1 lsmod: libcrc32c 3338 1 btrfs lsmod: vfat 14927 0 lsmod: fat63315 1 vfat lsmod: ext2 81388 0 lsmod: mbcache
Bug#620296: ps3-utils uploaded to mentors.debian.net
Hi Sean, I updated the ps3-utils package to bring it up to the latest sources, which fixes a few bugs, and also brought the debian build system files up to date. I put myself down as package maintainer, since it seemed to make sense to do so. I would certainly appreciate if you would act as sponsor and review the package and upload if it looks OK. Thanks in advance. -Geoff Forwarded Message Subject: ps3-utils uploaded to mentors.debian.net Date: Thu, 30 May 2013 23:12:44 + (UTC) Hi. Your upload of the package 'ps3-utils' to mentors.debian.net was successful. Others can now see it. The URL of your package is: http://mentors.debian.net/package/ps3-utils The respective dsc file can be found at: http://mentors.debian.net/debian/pool/main/p/ps3-utils/ps3-utils_13.05.30.14.14-g486082c-1.dsc Thanks, -- mentors.debian.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709260: RM: petitboot, petitboot-twin [mips mipel s390x sparc] -- depends on kexec-tools which doesn't exist on all archs
Package: ftp.debian.org Severity: normal Hi, I need to have the 12.10.16.14.58-ge7815dc-1 builds of petitboot and petitboot-twin removed from ftp.debian.org. These will block later versions of petitboot from migrating to testing. The builds should be fixed in bug #708691 (petitboot-13.05.21.22.00-g1435814-1). petitboot/mips unsatisfiable Depends: kexec-tools petitboot/mipsel unsatisfiable Depends: kexec-tools petitboot/s390x unsatisfiable Depends: kexec-tools petitboot/sparc unsatisfiable Depends: kexec-tools -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708691: petitboot: depends on kexec-tools which doesn't exist on all archs
Hi Julien, On Fri, 2013-05-17 at 20:54 +0200, Julien Cristau wrote: Package: petitboot Version: 12.10.16.14.58-ge7815dc-1 Severity: serious kexec-tools is not available on all archs. If petitboot needs it, it needs to be restricted to those architectures with a kexec-tools package. petitboot/mips unsatisfiable Depends: kexec-tools petitboot/mipsel unsatisfiable Depends: kexec-tools petitboot/s390x unsatisfiable Depends: kexec-tools petitboot/sparc unsatisfiable Depends: kexec-tools It was decided by others before you that what you suggest is not correct. With the way we have it now when kexec-tools works for those arches, petitboot will work for those arches automatically. If you want to do something I recommend you file a bug against kexec-tools to have it fixed for those listed arches. -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708691: petitboot: depends on kexec-tools which doesn't exist on all archs
Hi Adam, On Sat, 2013-05-18 at 12:47 +0100, Adam D. Barratt wrote: On Sat, 2013-05-18 at 17:49 +0800, Geoff Levand wrote: On Fri, 2013-05-17 at 20:54 +0200, Julien Cristau wrote: kexec-tools is not available on all archs. If petitboot needs it, it needs to be restricted to those architectures with a kexec-tools package. petitboot/mips unsatisfiable Depends: kexec-tools petitboot/mipsel unsatisfiable Depends: kexec-tools petitboot/s390x unsatisfiable Depends: kexec-tools petitboot/sparc unsatisfiable Depends: kexec-tools It was decided by others before you that what you suggest is not correct. That doesn't mean they were right. Was this decision made somewhere public? I asked on #debian-mentors how to set up my package config to handle this situation, where some arches do not have kexec-tools, and I followed the recommendation given. That was in response to a bug you reported (Bug #669663). With the way we have it now when kexec-tools works for those arches, petitboot will work for those arches automatically. And in the meantime it's RC buggy on those architectures, meaning the new version will not migrate to testing. What you're describing sounds like a suggestion to build-depend on kexec-tools - in fact, the package in stable and testing does exactly that; the build dependency appears to have been dropped in petitboot's 12.10.16.14.58-ge7815dc-1 upload with no mention in the changelog. Yes, it seems there was a regression there (the build-depend got dropped). I misunderstood what this problem was. I think the solution is then to add back the build-depend. I will prepare an update with this fix. Once fixed, will I need to need to ask for removal of the 12.10.16.14.58-ge7815dc-1 build for those arches? If you want to do something I recommend you file a bug against kexec-tools to have it fixed for those listed arches. Such a bug wouldn't be RC in any case, and doesn't change the fact that petitboot has been uninstallable on several architectures for nearly six months. As above, I'll prepare an update. -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705492: Uses deprecated RUN+=socket:
A fix has been committed to the upstream petitboot repository and is now in testing. commit 0c3348684455144089d1da574b1096c95f4b0a80 Author: Geoff Levand ge...@infradead.org Date: Sun Apr 21 22:20:14 2013 -0700 discover: Update udev routines to use libudev Support for 'RUN+=socket:' in udev rules files has been removed in udev version 183. Update the discover server to use libudev. Signed-off-by: Geoff Levand ge...@infradead.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705492: Uses deprecated RUN+=socket:
X-Debbugs-CC: Jeremy Kerr j...@ozlabs.org Hi Michael, On Fri, 2013-05-10 at 07:36 +0200, Michael Biebl wrote: Am 10.05.2013 07:11, schrieb Geoff Levand: A fix has been committed to the upstream petitboot repository and is now in testing. Cool, thanks! When do you plan to upload this fix to unstable? Jeremy has been doing some improvement and stabilization work on petitboot recently that I want to get into the next Debian package release. I would guess we'll be ready for that in three weeks or so. -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705492: Uses deprecated RUN+=socket:
I verified that this is a problem, and am working on a fix. -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#665189: [petitboot] You can't remove package.
Hi, On Thu, 2012-03-22 at 15:37 +0100, Karol KozÅowski wrote: Removing petitboot ... postrm called with unknown argument `remove' dpkg: error processing petitboot (--purge): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: petitboot I confirmed this error and will make a fix. Thanks for testing. -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660025: ITP: libtwin - A tiny window system
Package: wnpp Severity: wishlist Owner: Geoff Levand ge...@infradead.org * Package name: libtwin Version : 11.12.11-gcc20d5f Upstream Author : Geoff Levand ge...@infradead.org * URL : http://git.kernel.org/?p=linux/kernel/git/geoff/twin.git * License : LGPLv2 Programming Lang: C Description : A tiny window system With embedded systems gaining high resolution displays and powerful CPUs, the desire for sophisticated graphical user interfaces can be realized in even the smallest of systems. While the CPU power available for a given power budget has increased dramatically, these tiny systems remain severely memory constrained. This unique environment presents interesting challenges in graphical system design and implementation. To explore this particular space, a new window system, TWIN, has been developed. Using ideas from modern window systems in larger environments, TWIN offers overlapping translucent windows, anti-aliased graphics and scalable fonts in a total memory budget of 100KB. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659668: ITP: petitboot -- A kexec based bootloader
Package: wnpp Severity: wishlist Owner: Geoff Levand ge...@infradead.org * Package name: petitboot Version : 12.02.12-g944bccf Upstream Author : Geoff Levand ge...@infradead.org * URL : http://www.kernel.org/pub/linux/kernel/people/geoff/petitboot/petitboot.html * License : GPLv2 Programming Lang: C Description : A kexec based bootloader Petitboot is a platform independent bootloader based on the Linux kexec warm reboot mechanism. Petitboot supports loading kernel and initrd image files from any mountable Linux device, plus can load image files from the network using TFTP, NFS, HTTP, HTTPS, and SCP. Petitboot can boot any operating system supported by kexec. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#620296: ps3-utils package needs update
Package: ps3-utils Version: 2.3-1 Severity: normal Tags: patch upstream Hi, I made a debian specific fix to the ps3-utils package today. Please update the debian package with the latest sources: git://git.kernel.org/pub/scm/linux/kernel/git/geoff/ps3-utils.git commit 530223b95464505c886dcc0e62568f4e45e0ada7 Author: Geoff Levand ge...@infradead.org Date: Thu Mar 31 13:14:32 2011 -0700 Use bash as interpreter Debian uses dash as default shell, which does not support the 'let' command. -Geoff -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc64) Kernel: Linux 2.6.32-5-powerpc64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ps3-utils depends on: ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib ps3-utils recommends no packages. ps3-utils suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619236: [Cbe-oss-dev] Bug#619236: installation-reports: installation works fine on PS3 now, but we still can't boot after the installation
On 03/22/2011 02:29 AM, Antonio Ospite wrote: Hi, the installation on PS3 now completes pretty fine, however there are still some details that could be improved. The installer warns about the boot loader not being installed, which is fine, I already had the 'petitboot' bootloader installed, but some configuration is still needed to make the system actually boot _after_ the installation. petitboot needs a /etc/kboot.conf in the root filesystem with this content to successfully boot the installed system: linux=/boot/vmlinux initrd=/boot/initrd.img root=/dev/ps3da1 quiet I could successfully do a gnome desktop install using the 20110329 daily: http://cdimage.debian.org/cdimage/daily-builds/daily/20110329-5/powerpc/iso-cd/debian-testing-powerpc-netinst.iso I encountered the same problems as Antonio. Once the installer was finished, but before it rebooted the system I used this from a tty console: echo 'linux=/boot/vmlinux initrd=/boot/initrd.img root=/dev/ps3da1' /target/etc/kboot.conf -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619621: installer fails looking for mirror
Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/20110324-3/powerpc/iso-cd/debian-testing-powerpc-netinst.iso Date: Mar 25, 2011 Machine: PS3 Comments/Problems: Failed on looking for mirrors. Installer looks for 'Architecture:' but file has 'Architectures:' See http://mirrors.kernel.org/debian/dists/wheezy/Release -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#570430: debian installer network config fails on PS3
Package: netcfg Version: 1.51 X-Debbugs-CC: rbtho...@pobox.com, debian-powe...@lists.debian.org, cbe-oss-...@lists.ozlabs.org Original Message Subject: Re: Has anybody recently done a Debian install on a playstation-3? Date: Tue, 16 Feb 2010 11:27:27 -0800 From: Levand, Geoffrey geoffrey.lev...@am.sony.com To: Rick Thomas rbtho...@pobox.com CC: PowerPC List Debian debian-powe...@lists.debian.org, Installer List Debian debian-b...@lists.debian.org, Norberto Feliberty thegame4121...@msn.com Hi, On 02/15/2010 09:13 PM, Rick Thomas wrote: Norberto is having trouble getting Debian to install on his PS3. It's a bit out of my usual line, so any advice from somebody who has done it will be much appreciated! I just tested the current daily-build (08-Feb-2010 00:09) from here: http://d-i.debian.org/daily-images/powerpc/daily/powerpc64/netboot/ The installer fails on network config. If I run 'dhclient eth0' from a console I can see the request at the dhcp server, and dhclient reports the correct address, but networking does not function properly. If I run 'netcfg' from a console I get: netcfg: undefined symbol: _savegpr_19 I guess this is our problem. I don't have enough knowledge of D-I to do much more. -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514055: [Cbe-oss-dev] Bug#514055: debian still not working on PS3
On 05/28/2009 09:39 AM, Levand, Geoffrey wrote: On 05/01/2009 03:18 PM, Geoff Levand wrote: I tried today's build (20090430) and the 'CD-ROM driver not found' problem is fixed: http://people.debian.org/~wouter/d-i/powerpc/20090430-22:00/powerpc64/netboot/ I was able to finish the install, but still got the same other known problems: (1) At kernel install: 'No installable kernel was found in the defined APT sources' 'base-installer: info: could not determine kernel flavor' (2) At boot loader install: 'No boot loader has been installed' 'GRUB not yet usable on PowerPC systems' It should create a /etc/yaboot.conf on the same partition that the kernel was installed to, but nothing else is needed. The petitboot bootloader can read from vfat, ext2, ext3, and ext4 file systems. Hi, Could someone familiar with D-I internals give a brief summary of what needs to be done to fix these two problems. Thanks. I tried the sid installer build today: http://cdimage.debian.org/cdimage/daily-builds/sid_d-i/arch-latest/powerpc/iso-cd/ but there were no ps3 drivers in the image. What needs to be done to get those drivers included? -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514055: [Cbe-oss-dev] Bug#514055: debian still not working on PS3
On 12/02/2009 03:25 PM, Levand, Geoffrey wrote: On 05/28/2009 09:39 AM, Levand, Geoffrey wrote: On 05/01/2009 03:18 PM, Geoff Levand wrote: I tried today's build (20090430) and the 'CD-ROM driver not found' problem is fixed: http://people.debian.org/~wouter/d-i/powerpc/20090430-22:00/powerpc64/netboot/ I was able to finish the install, but still got the same other known problems: (1) At kernel install: 'No installable kernel was found in the defined APT sources' 'base-installer: info: could not determine kernel flavor' (2) At boot loader install: 'No boot loader has been installed' 'GRUB not yet usable on PowerPC systems' It should create a /etc/yaboot.conf on the same partition that the kernel was installed to, but nothing else is needed. The petitboot bootloader can read from vfat, ext2, ext3, and ext4 file systems. Hi, Could someone familiar with D-I internals give a brief summary of what needs to be done to fix these two problems. Thanks. I tried the sid installer build today: http://cdimage.debian.org/cdimage/daily-builds/sid_d-i/arch-latest/powerpc/iso-cd/ but there were no ps3 drivers in the image. What needs to be done to get those drivers included? After some searching, I found this commit that seems it should add the drivers: http://svn.debian.org/viewsvn/d-i/trunk/packages/kernel/linux-kernel-di-powerpc-2.6/modules/powerpc-powerpc64/scsi-extra-modules?r1=48552r2=57888 That change doesn't seem to be in the daily build I tested though. Can anyone explain? -Goeff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514055: [Cbe-oss-dev] Bug#514055: debian still not working on PS3
On 12/02/2009 05:32 PM, Norberto Feliberty wrote: hello, while the changes may have not been committed to cd or dvd media, the changes are in place for the netboot images. I tried the netboot image anywhere between the 10th and 20th of november. I can't recall the exact date but It was a squeeze build. Could you please let me know the URL where you downloaded the netboot image? -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514055: [Cbe-oss-dev] Bug#514055: debian still not working on PS3
On 05/01/2009 03:18 PM, Geoff Levand wrote: I tried today's build (20090430) and the 'CD-ROM driver not found' problem is fixed: http://people.debian.org/~wouter/d-i/powerpc/20090430-22:00/powerpc64/netboot/ I was able to finish the install, but still got the same other known problems: (1) At kernel install: 'No installable kernel was found in the defined APT sources' 'base-installer: info: could not determine kernel flavor' (2) At boot loader install: 'No boot loader has been installed' 'GRUB not yet usable on PowerPC systems' It should create a /etc/yaboot.conf on the same partition that the kernel was installed to, but nothing else is needed. The petitboot bootloader can read from vfat, ext2, ext3, and ext4 file systems. Hi, Could someone familiar with D-I internals give a brief summary of what needs to be done to fix these two problems. Thanks. -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514055: [Cbe-oss-dev] Bug#514055: debian still not working on PS3
On 04/23/2009 01:54 AM, Wouter Verhelst wrote: On Tue, Apr 21, 2009 at 10:34:34PM -0400, thegame4121...@msn.com wrote: This is great news. Is this only for the testing version of Debian codename squeeze or will this fix also be included in the next point release of Debian Lenny? It will not be included in the next point release. However, it might be included as part of the planned 'lenny and a half' release where a new kernel and installer will be provided, to support new hardware. Before that can happen, however, testing will be necessary. You can find the daily builds here: http://people.debian.org/~wouter/d-i/powerpc/ Hi, I tried today's build (20090430) and the 'CD-ROM driver not found' problem is fixed: http://people.debian.org/~wouter/d-i/powerpc/20090430-22:00/powerpc64/netboot/ I was able to finish the install, but still got the same other known problems: (1) At kernel install: 'No installable kernel was found in the defined APT sources' 'base-installer: info: could not determine kernel flavor' It should install the 64 bit powerpc kernel. (2) At boot loader install: 'No boot loader has been installed' 'GRUB not yet usable on PowerPC systems' It should create a /etc/yaboot.conf on the same partition that the kernel was installed to, but nothing else is needed. The petitboot bootloader can read from vfat, ext2, ext3, and ext4 file systems. -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514055: debian still not working on PS3
Hi Wartan, On 03/22/2009 01:46 PM, Wartan Hachaturow wrote: On Sun, Mar 22, 2009 at 10:25 PM, Wouter Verhelst w...@uter.be wrote: I'll continue working on this stuff, this was just a test image to make sure kernel modules were loaded fine. If you have patches, I can help you get them into d-i proper. Well, I've got commit rights in d-i's svn ;) I just tried the latest d-i testing image (16-Apr-2009 17:59), but it still fails with this CD-ROM drivers not found problem. Did these changes get committed? If not, could you please commit them, or post what you have so Wouter can do that? Thanks. -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514055: debian still not working on PS3
On 03/22/2009 10:45 AM, Geoff Levand wrote: On 03/21/2009 10:38 AM, Wouter Verhelst wrote: On Fri, Mar 20, 2009 at 04:40:51PM -0700, Geoff Levand wrote: 1) At boot there were some kernel I/O errors about /dev/sr0. That is the BD drive. Did you have a disc in the drive at that point? If so, what kind of disc? The mini.iso installer, a CD-ROM. Here are the messages. Geert, any idea about them? Mar 20 21:57:32 kernel: [5.399309] Driver 'sr' needs updating - please use bus_type methods Mar 20 21:57:32 kernel: [5.426872] sr0: scsi3-mmc drive: 0x/0x cd/rw xa/form2 cdda tray Mar 20 21:57:32 kernel: [5.433191] Uniform CD-ROM driver Revision: 3.20 Mar 20 21:57:32 kernel: [5.433678] sr 0:0:0:0: Attached scsi CD-ROM sr0 Mar 20 21:57:32 kernel: [5.457911] sr 0:0:0:0: Attached scsi generic sg0 type 5 ... Mar 20 21:57:32 kernel: [7.704702] sr 0:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Mar 20 21:57:32 kernel: [7.710429] sr 0:0:0:0: [sr0] Sense Key : Medium Error [current] Mar 20 21:57:32 kernel: [7.716198] sr 0:0:0:0: [sr0] Add. Sense: L-EC uncorrectable error Mar 20 21:57:32 kernel: [7.722110] end_request: I/O error, dev sr0, sector 45712 Mar 20 21:57:32 kernel: [7.727934] Buffer I/O error on device sr0, logical block 11428 ... Mar 20 21:57:32 kernel: [9.394691] sr 0:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Mar 20 21:57:32 kernel: [9.401118] sr 0:0:0:0: [sr0] Sense Key : Medium Error [current] Mar 20 21:57:32 kernel: [9.407622] sr 0:0:0:0: [sr0] Add. Sense: L-EC uncorrectable error Mar 20 21:57:32 kernel: [9.414009] end_request: I/O error, dev sr0, sector 45712 Mar 20 21:57:32 kernel: [9.420386] Buffer I/O error on device sr0, logical block 11428 Mar 20 21:57:32 kernel: [ 10.864657] sr 0:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Mar 20 21:57:32 kernel: [ 10.871199] sr 0:0:0:0: [sr0] Sense Key : Medium Error [current] Mar 20 21:57:32 kernel: [ 10.877661] sr 0:0:0:0: [sr0] Add. Sense: L-EC uncorrectable error Mar 20 21:57:32 kernel: [ 10.884132] end_request: I/O error, dev sr0, sector 45712 Mar 20 21:57:32 kernel: [ 10.890609] Buffer I/O error on device sr0, logical block 11428 ... -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514055: debian still not working on PS3
On 03/21/2009 11:05 PM, Wartan Hachaturow wrote: PS3 is booted with kboot, which is able to interpret yaboot.conf. Thus, the correct behaviour on that platform would be to create yaboot.conf, but without bootloader installation itself :) (as Debian does not have kboot, and I presume hardly ever will). Just FYI, use of kboot is now depreciated. Only petitboot will be maintained. I'll continue working on this stuff, this was just a test image to make sure kernel modules were loaded fine. Thanks for your efforts. -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514055: debian still not working on PS3
On 03/21/2009 10:38 AM, Wouter Verhelst wrote: On Fri, Mar 20, 2009 at 04:40:51PM -0700, Geoff Levand wrote: On 03/20/2009 02:21 PM, Wartan Hachaturow wrote: On Mon, Mar 02, 2009 at 03:00:37PM +0300, Wartan Hachaturow wrote: The short answer is that there isn't really an active powerpc porter working on the installer. That's why your bug report is unanswered. I'm copying Wouter Verhelst who indicated some interest in helping with the powerpc port. I own a lot of PPC/Cell hardware, including a couple of PS3's. I'll have a look on the issue. Geoff, could you please test this image: http://people.debian.org/~wart/ps3/mini.iso I tested this image and could do a complete install using Ethernet with the resulting notes below. I did not try to install over wireless. 1) At boot there were some kernel I/O errors about /dev/sr0. That is the BD drive. Did you have a disc in the drive at that point? If so, what kind of disc? The mini.iso installer, a CD-ROM. 2) During the HD setup I had some warning dialogs. One about HPFS, and one about a PREP partition. I answered 'No' to both and continued. 3) I got a warning 'No installable kernel was found in the defined APT sources'. I answered 'Yes' (no install) and continued. The correct installer is chosen based on a set of rules for the subsystem. I'm assuming that there's no rule for PS3 here. Similar things are true for the partitioner. Afterward I could install the debian 2.6.26 kernel using apt-get, and then a manual entry in yaboot.conf. It booted and worked OK, so it seems we just need a slight change here to get it installed. 4) I needed to manually select to not install a bootloader. No yaboot.conf was installed, so I needed to create one manually. Hrm. Does the PS3 boot with yaboot? If so, you should have been able to select yaboot, and have it be installed to the system. That should also have created your yaboot.conf. PS3 uses petitboot (http://ozlabs.org/~jk/projects/petitboot/). It is a kexec based bootloader which can read kboot.conf and yaboot.conf files. Due to the way the PS3 boots, the user must install a bootloader to flash memory before they can load a distro's installer. I'll try the yaboot install and see what happens. Is it possible to arrange for the installer to just create the yaboot.conf without installing yaboot? -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514055: debian still not working on PS3
On 03/22/2009 12:44 PM, Wouter Verhelst wrote: On Sun, Mar 22, 2009 at 10:45:25AM -0700, Geoff Levand wrote: On 03/21/2009 10:38 AM, Wouter Verhelst wrote: That is the BD drive. Did you have a disc in the drive at that point? If so, what kind of disc? The mini.iso installer, a CD-ROM. The fact that you were successful makes me doubt it's a serious problem, but it warrants investigating. The installer should store some logs on your hard disk, under /var/log/installer. Could you send me those files? Note that it may contain some private information, such as your root password, and a list of the packages you've got installed. I'll send you that tomorrow. PS3 uses petitboot (http://ozlabs.org/~jk/projects/petitboot/). It is a kexec based bootloader which can read kboot.conf and yaboot.conf files. Due to the way the PS3 boots, the user must install a bootloader to flash memory before they can load a distro's installer. I'll try the yaboot install and see what happens. Is it possible to arrange for the installer to just create the yaboot.conf without installing yaboot? No, that won't work. I simply wasn't aware of the particular way in which the PS3 is booted. I see that petitboot is free software. In that case, we should be able to at least put it on the CD images. Yes, but as Wartan mentioned, it is not so practical for distros to build it from sources. Just FYI, I put binary releases of petitboot here: http://www.kernel.org/pub/linux/kernel/people/geoff/cell/ps3-petitboot/ Is it possible to install or update the flash booter from Linux, or can one only do that from the PS3 builtin operating system? It can be done from either. From Linux, it is done with ps3-flash-util from the ps3-utils package (http://packages.debian.org/squeeze/ps3-utils). Command is 'ps3-flash-util -w image'. -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514055: debian still not working on PS3
On 03/20/2009 02:21 PM, Wartan Hachaturow wrote: On Mon, Mar 02, 2009 at 03:00:37PM +0300, Wartan Hachaturow wrote: The short answer is that there isn't really an active powerpc porter working on the installer. That's why your bug report is unanswered. I'm copying Wouter Verhelst who indicated some interest in helping with the powerpc port. I own a lot of PPC/Cell hardware, including a couple of PS3's. I'll have a look on the issue. Geoff, could you please test this image: http://people.debian.org/~wart/ps3/mini.iso I tested this image and could do a complete install using Ethernet with the resulting notes below. I did not try to install over wireless. 1) At boot there were some kernel I/O errors about /dev/sr0. 2) During the HD setup I had some warning dialogs. One about HPFS, and one about a PREP partition. I answered 'No' to both and continued. 3) I got a warning 'No installable kernel was found in the defined APT sources'. I answered 'Yes' (no install) and continued. 4) I needed to manually select to not install a bootloader. No yaboot.conf was installed, so I needed to create one manually. -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514055: debian still not working on PS3
On 03/02/2009 03:34 AM, Wouter Verhelst wrote: On Fri, Feb 27, 2009 at 07:53:33PM +0100, Martin Michlmayr wrote: * Geoff Levand geoffrey.lev...@am.sony.com [2009-02-26 09:43]: I just tried the latest testing CD (2000.02.12), and it still fails with the same problem I reported for Lenny DI RC2. The installer fails on mounting the CD-ROM. The PS3 ps3_gelic network and PS3 ps3rom and ps3disk storage drivers are missing from the installer's initrd. I entered a bug report that went unanswered here: The short answer is that there isn't really an active powerpc porter working on the installer. That's why your bug report is unanswered. I'm copying Wouter Verhelst who indicated some interest in helping with the powerpc port. Martin is currently working to get me a PegasosII which will be used to build the powerpc dailies. When I get it, however, I will also use it to fix the installer for the PegasosII platform, which does not currently work because it creates partitions with a too large blocksize or some such (I don't know the details offhand). When I'm working on this, I could as well look at doing PS3 support at the same time. I don't currently own a PS3, however, and while I do plan to eventually acquire one, I'm going to have to do this blind; so while I'm working on this, I might have to ask you to test my images from time to time. OK, thank you for the support. I can test the images. Please put a image somewhere, and then let me know. I'm hoping there isn't much to do other that get the proper drivers into DI's initrd. -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514055: debian still not working on PS3
Hi, I just tried the latest testing CD (2000.02.12), and it still fails with the same problem I reported for Lenny DI RC2. The installer fails on mounting the CD-ROM. The PS3 ps3_gelic network and PS3 ps3rom and ps3disk storage drivers are missing from the installer's initrd. I entered a bug report that went unanswered here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514055 -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514055: test debian-Lenny-DI-rc2-powerpc-netinst
Package: installation-reports X-Debbugs-CC: Geert Uytterhoeven geert.uytterhoe...@sonycom.com Boot method: CD Image version: http://cdimage.debian.org/cdimage/lenny_di_rc2/powerpc/iso-cd/debian-Lenny-DI-rc2-powerpc-netinst.iso Date: Thu Jan 15 14:31:51 2009 Machine: PS3 game console (A model) Processor: Cell (powerpc64) Output of lspci -knn (or lspci -nn): No PCI bus. Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] No ps3_gelic driver Configure network: [ ] Detect CD: [E] No ps3rom driver Load installer modules: [ ] Detect hard drives: [E] No ps3disk driver Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: * Seems just the hard drive, CD-ROM and network drivers are missing from the install initrd. * System boots OK with 'install64' menu item. * System boots OK with 'install64' menu item with added 'video=720p' to kernel command line. * Once booted, 'reboot' command from shell works as expected, so kernel seems to be working OK. Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#484693: linux-2.6: Add RTC class support for powerpc64 machines
On 06/05/2008 09:45 AM, Geoff Levand wrote: The attached kernel and config.powerpc64 patches add a new style RTC class driver that works with most powerpc64 platforms. This patch was merged in to mainline for 2.6.26-rc6. author David Woodhouse [EMAIL PROTECTED] Fri, 6 Jun 2008 05:46:50 + (22:46 -0700) committer Linus Torvalds [EMAIL PROTECTED] Fri, 6 Jun 2008 18:29:13 + (11:29 -0700) commit aabe188565124ee2ed060a072764d6ed34dfa4ed treeb2570905b65a6caa39f266f591b2907ff2c530f2 parent ec0ced156f930aba24e7527905de294ad929ef65 -Geoff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484693: linux-2.6: Add RTC class support for powerpc64 machines
Package: linux-2.6
Version: 2.6.25
Severity: normal
Tags: patch
The attached kernel and config.powerpc64 patches add a
new style RTC class driver that works with most powerpc64
platforms.
This driver, enabled with the CONFIG_RTC_DRV_PPC option,
replaces the old gen_rtc support that was enabled with
the CONFIG_GEN_RTC option. The old CONFIG_GEN_RTC option
is incompatible with the RTC class system and can no
longer be enabled in the Debian kernel config.
This patch has been submitted for mainline 2.6.27:
http://patchwork.ozlabs.org/linuxppc/patch?id=18139
Without this RTC class driver, the following error can
be seen at start up:
Setting the system clock.
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
* Unable to set System Clock to: Fri May 30 20:33:06 UTC 2008
The problem can also be reproduced with these steps:
# hwclock --debug
hwclock from util-linux-ng 2.13.1.1
hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
No usable clock interface found.
Cannot access the Hardware Clock via any known method.
# ls -l /dev/rtc*
ls: cannot access /dev/rtc*: No such file or directory
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: powerpc (ppc64)
Kernel: Linux 2.6.25-3-powerpc64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- a/debian/config/powerpc/config.powerpc64
+++ b/debian/config/powerpc/config.powerpc64
@@ -155,6 +155,11 @@ CONFIG_IBM_NEW_EMAC_RX_SKB_HEADROOM=0
##
# CONFIG_HOTPLUG_PCI is not set
+###
+### file: drivers/rtc/Kconfig
+###
+CONFIG_RTC_DRV_PPC=m
+
##
## file: drivers/scsi/Kconfig
##
From [EMAIL PROTECTED] Fri Apr 25 19:29:12 2008
From: David Woodhouse [EMAIL PROTECTED]
Subject: [PATCH, RESEND] RTC class driver for ppc_md RTC functions
Date: Fri, 25 Apr 2008 19:29:12 +1000
X-Patchwork-ID: 18139
This hooks up the platform-specific [gs]et_rtc_time functions so that
kernels using CONFIG_RTC_CLASS have RTC support on most PowerPC
platforms.
Signed-off-by: David Woodhouse [EMAIL PROTECTED]
---
diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
index 1e6715e..3e788b7 100644
--- a/drivers/rtc/Kconfig
+++ b/drivers/rtc/Kconfig
@@ -461,4 +461,12 @@ config RTC_DRV_RS5C313
help
If you say yes here you get support for the Ricoh RS5C313 RTC chips.
+config RTC_DRV_PPC
+ tristate PowerPC machine dependent RTC support
+ depends on PPC_MERGE
+ help
+ The PowerPC kernel has machine-specific functions for accessing
+ the RTC. This exposes that functionality through the generic RTC
+ class.
+
endif # RTC_CLASS
diff --git a/drivers/rtc/Makefile b/drivers/rtc/Makefile
index 465db4d..e822e56 100644
--- a/drivers/rtc/Makefile
+++ b/drivers/rtc/Makefile
@@ -49,3 +49,4 @@ obj-$(CONFIG_RTC_DRV_TEST) += rtc-test.o
obj-$(CONFIG_RTC_DRV_V3020) += rtc-v3020.o
obj-$(CONFIG_RTC_DRV_VR41XX) += rtc-vr41xx.o
obj-$(CONFIG_RTC_DRV_X1205) += rtc-x1205.o
+obj-$(CONFIG_RTC_DRV_PPC) += rtc-ppc.o
--- /dev/null 2007-12-03 03:08:41.854157978 +
+++ b/drivers/rtc/rtc-ppc.c 2007-12-03 16:56:15.0 +
@@ -0,0 +1,69 @@
+/*
+ * RTC driver for ppc_md RTC functions
+ *
+ * © 2007 Red Hat, Inc.
+ *
+ * Author: David Woodhouse [EMAIL PROTECTED]
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+
+
+#include linux/module.h
+#include linux/err.h
+#include linux/rtc.h
+#include linux/platform_device.h
+#include asm/machdep.h
+
+static int ppc_rtc_read_time(struct device *dev, struct rtc_time *tm)
+{
+ ppc_md.get_rtc_time(tm);
+ return 0;
+}
+
+static int ppc_rtc_set_time(struct device *dev, struct rtc_time *tm)
+{
+ return ppc_md.set_rtc_time(tm);
+}
+
+static const struct rtc_class_ops ppc_rtc_ops = {
+ .set_time = ppc_rtc_set_time,
+ .read_time = ppc_rtc_read_time,
+};
+
+static struct rtc_device *rtc;
+static struct platform_device *ppc_rtc_pdev;
+
+static int __init ppc_rtc_init(void)
+{
+ if (!ppc_md.get_rtc_time || !ppc_md.set_rtc_time)
+ return -ENODEV;
+
+ ppc_rtc_pdev = platform_device_register_simple(ppc-rtc, 0, NULL, 0);
+ if (IS_ERR(ppc_rtc_pdev))
+ return PTR_ERR(ppc_rtc_pdev);
+
+ rtc = rtc_device_register(ppc_md, ppc_rtc_pdev-dev,
+ ppc_rtc_ops, THIS_MODULE);
+ if (IS_ERR(rtc)) {
+ platform_device_unregister(ppc_rtc_pdev);
+ return PTR_ERR(rtc);
+ }
+
+ return 0;
+}
+
+static void __exit ppc_rtc_exit(void)
+{
+ rtc_device_unregister(rtc);
+ platform_device_unregister(ppc_rtc_pdev);
+}
+
+module_init(ppc_rtc_init);
+module_exit(ppc_rtc_exit);
+
+MODULE_LICENSE(GPL);
+MODULE_AUTHOR(David Woodhouse [EMAIL PROTECTED]);
+MODULE_DESCRIPTION(Generic RTC class driver for PowerPC);
Bug#462529: linux-2.6: Add config file support for efika and PS3 (preliminary)
Geoff Levand wrote:
Bastian Blank wrote:
-# CONFIG_GEN_RTC is not set
+CONFIG_GEN_RTC=y
Why?
I am not so familiar with this option. I saw
an RTC error message when this was not enabled.
Please show the error.
This is the error:
Setting the system clock.
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access
method.
* Unable to set System Clock to: Fri May 30 20:33:06 UTC 2008
ice:~# hwclock --debug
hwclock from util-linux-ng 2.13.1.1
hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
No usable clock interface found.
Cannot access the Hardware Clock via any known method.
ice:~# ls -l /dev/rtc*
ls: cannot access /dev/rtc*: No such file or directory
The PS3 does not have an RTC driver. The PS3 platform code just hooks into
the standard powerpc ppc_md.set_rtc_time and ppc_md.get_rtc_time pointers
(arch/powerpc/platforms/ps3/time.c).
From what I understand the work to hookup the powerpc ppc_md. rtc routines
to the RTC_INTF_DEV routines has not been done. See here:
http://marc.info/?t=12035265472r=1w=2
I'll look into this. I either need to make a gen_rtc driver for the
new rtc subsytem, or make a ps3 specific rtc driver.
A patch to fix this problem is attached. It has been submitted
for 2.6.27:
http://patchwork.ozlabs.org/linuxppc/patch?id=18139
With it there is a new driver rtc-ppc, enabled with CONFIG_RTC_DRV_PPC.
Should I submit another bug report for this?
-Geoff
From [EMAIL PROTECTED] Fri Apr 25 19:29:12 2008
From: David Woodhouse [EMAIL PROTECTED]
Subject: [PATCH, RESEND] RTC class driver for ppc_md RTC functions
Date: Fri, 25 Apr 2008 19:29:12 +1000
X-Patchwork-ID: 18139
This hooks up the platform-specific [gs]et_rtc_time functions so that
kernels using CONFIG_RTC_CLASS have RTC support on most PowerPC
platforms.
Signed-off-by: David Woodhouse [EMAIL PROTECTED]
---
diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
index 1e6715e..3e788b7 100644
--- a/drivers/rtc/Kconfig
+++ b/drivers/rtc/Kconfig
@@ -461,4 +461,12 @@ config RTC_DRV_RS5C313
help
If you say yes here you get support for the Ricoh RS5C313 RTC chips.
+config RTC_DRV_PPC
+ tristate PowerPC machine dependent RTC support
+ depends on PPC_MERGE
+ help
+ The PowerPC kernel has machine-specific functions for accessing
+ the RTC. This exposes that functionality through the generic RTC
+ class.
+
endif # RTC_CLASS
diff --git a/drivers/rtc/Makefile b/drivers/rtc/Makefile
index 465db4d..e822e56 100644
--- a/drivers/rtc/Makefile
+++ b/drivers/rtc/Makefile
@@ -49,3 +49,4 @@ obj-$(CONFIG_RTC_DRV_TEST) += rtc-test.o
obj-$(CONFIG_RTC_DRV_V3020) += rtc-v3020.o
obj-$(CONFIG_RTC_DRV_VR41XX) += rtc-vr41xx.o
obj-$(CONFIG_RTC_DRV_X1205) += rtc-x1205.o
+obj-$(CONFIG_RTC_DRV_PPC) += rtc-ppc.o
--- /dev/null 2007-12-03 03:08:41.854157978 +
+++ b/drivers/rtc/rtc-ppc.c 2007-12-03 16:56:15.0 +
@@ -0,0 +1,69 @@
+/*
+ * RTC driver for ppc_md RTC functions
+ *
+ * © 2007 Red Hat, Inc.
+ *
+ * Author: David Woodhouse [EMAIL PROTECTED]
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+
+
+#include linux/module.h
+#include linux/err.h
+#include linux/rtc.h
+#include linux/platform_device.h
+#include asm/machdep.h
+
+static int ppc_rtc_read_time(struct device *dev, struct rtc_time *tm)
+{
+ ppc_md.get_rtc_time(tm);
+ return 0;
+}
+
+static int ppc_rtc_set_time(struct device *dev, struct rtc_time *tm)
+{
+ return ppc_md.set_rtc_time(tm);
+}
+
+static const struct rtc_class_ops ppc_rtc_ops = {
+ .set_time = ppc_rtc_set_time,
+ .read_time = ppc_rtc_read_time,
+};
+
+static struct rtc_device *rtc;
+static struct platform_device *ppc_rtc_pdev;
+
+static int __init ppc_rtc_init(void)
+{
+ if (!ppc_md.get_rtc_time || !ppc_md.set_rtc_time)
+ return -ENODEV;
+
+ ppc_rtc_pdev = platform_device_register_simple(ppc-rtc, 0, NULL, 0);
+ if (IS_ERR(ppc_rtc_pdev))
+ return PTR_ERR(ppc_rtc_pdev);
+
+ rtc = rtc_device_register(ppc_md, ppc_rtc_pdev-dev,
+ ppc_rtc_ops, THIS_MODULE);
+ if (IS_ERR(rtc)) {
+ platform_device_unregister(ppc_rtc_pdev);
+ return PTR_ERR(rtc);
+ }
+
+ return 0;
+}
+
+static void __exit ppc_rtc_exit(void)
+{
+ rtc_device_unregister(rtc);
+ platform_device_unregister(ppc_rtc_pdev);
+}
+
+module_init(ppc_rtc_init);
+module_exit(ppc_rtc_exit);
+
+MODULE_LICENSE(GPL);
+MODULE_AUTHOR(David Woodhouse [EMAIL PROTECTED]);
+MODULE_DESCRIPTION(Generic RTC class driver for PowerPC);
--- a/debian/config/powerpc/config.powerpc64
+++ b/debian/config/powerpc/config.powerpc64
@@ -155,6 +155,11 @@ CONFIG_IBM_NEW_EMAC_RX_SKB_HEADROOM=0
##
# CONFIG_HOTPLUG_PCI is not set
+###
+### file: drivers/rtc/Kconfig
+###
+CONFIG_RTC_DRV_PPC=m
+
##
## file: drivers/scsi/Kconfig
##
Bug#483489: linux-2.6: Optional powerpc64 patches for PS3
Bastian Blank wrote: tags 483489 wontfix thanks On Wed, May 28, 2008 at 05:26:37PM -0700, Geoff Levand wrote: Attached are two patches against the debian linux-2.6-2.6.25 sources that would be nice to apply for the PS3. Please send them to [EMAIL PROTECTED] Also you have to use that way to fix the following error, after it have been applied to Linus' tree: | ERROR: fb_mode_option [drivers/ps3/ps3av_mod.ko] undefined! Tagging as wontfix for now. Just FYI, I submitted the memory leak and undefined symbol bugs for the stable kernel. I don't think the vmemmap-variable-page-size patch is suitable as it is quite intrusive and is not really a 'critical' fix. -Geoff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462529: linux-2.6: Add config file support for efika and PS3 (preliminary)
Bastian Blank wrote: On Wed, May 28, 2008 at 04:22:45PM -0700, Geoff Levand wrote: Bastian Blank wrote: There is a 2.6.25 undefined symbol bug in PS3AV that won't allow it to be built as a module. It is even unfixed in -rc4 and it is needed by FB_PS3. I just found that bug a few days ago (testing debian). It should go into -rc5. It went unfound for many months because no one builds the PS3 frame buffer as a module. It comes up too late. I think if you have it as a module, most users will complain about it. -# CONFIG_GEN_RTC is not set +CONFIG_GEN_RTC=y Why? I am not so familiar with this option. I saw an RTC error message when this was not enabled. Please show the error. This is the error: Setting the system clock. Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. * Unable to set System Clock to: Fri May 30 20:33:06 UTC 2008 ice:~# hwclock --debug hwclock from util-linux-ng 2.13.1.1 hwclock: Open of /dev/rtc failed, errno=2: No such file or directory. No usable clock interface found. Cannot access the Hardware Clock via any known method. ice:~# ls -l /dev/rtc* ls: cannot access /dev/rtc*: No such file or directory The PS3 does not have an RTC driver. The PS3 platform code just hooks into the standard powerpc ppc_md.set_rtc_time and ppc_md.get_rtc_time pointers (arch/powerpc/platforms/ps3/time.c). From what I understand the work to hookup the powerpc ppc_md. rtc routines to the RTC_INTF_DEV routines has not been done. See here: http://marc.info/?t=12035265472r=1w=2 I'll look into this. I either need to make a gen_rtc driver for the new rtc subsytem, or make a ps3 specific rtc driver. I can test your proposed config if you make it available to me. I commited large parts of it in the trunk. I tested it, and in general it works OK. I put the dmesg here: http://cell.gotdns.org/pub/debian-cell-kernel-2/ You don't have CONFIG_LOGO_LINUX_CLUT224 set, so the SPE logos are not rendered correctly. It looks like the lines of pixel are not aligned. Geert, can you say why? Is it a bug in the logo code? I'll do some more testing next week. -Geoff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462529: linux-2.6: Add config file support for efika and PS3 (preliminary)
Robert Millan wrote: I just updated your patch to the latest version of the package (moving the definitions to the pre-existing PS3 section), but I cannot check if it still works. Is it safe to assume it does? In any case, would be nice if someone could test. I made the following updated patch and tested it. It should be complete. There are some optional 2.6.25 kernel patches that would be nice to have applied for the PS3. I will make a separate bug report for those. -- Update the Debian powerpc64 2.6.25 kernel config for Cell platforms. Adds support for the PS3 game console and updates the Cell blade config to support QS20 and QS21 machines. --- linux-2.6-2.6.25.orig/debian/config/powerpc/config.powerpc64 +++ linux-2.6-2.6.25/debian/config/powerpc/config.powerpc64 @@ -14,6 +14,7 @@ CONFIG_SCHED_SMT=y CONFIG_CMDLINE=console=hvsi0 console=hvc0 console=ttyS0,9600 console=tty0 CONFIG_KERNEL_START=0xc000 +# CONFIG_MEMORY_HOTREMOVE is not set ## ## file: arch/powerpc/Kconfig.debug @@ -30,12 +31,24 @@ CONFIG_CPU_FREQ_PMAC64=y #. It's a bool CONFIG_PPC_PASEMI_CPUFREQ=y +CONFIG_UDBG_RTAS_CONSOLE=y +CONFIG_PPC_PMI=m +CONFIG_AXON_RAM=m ## ## file: arch/powerpc/platforms/cell/Kconfig ## -# CONFIG_PPC_IBM_CELL_BLADE is not set +CONFIG_PPC_CELL=y +CONFIG_PPC_CELL_NATIVE=y +CONFIG_PPC_IBM_CELL_BLADE=y CONFIG_SPU_FS=m +CONFIG_SPU_FS_64K_LS=y +CONFIG_SPU_BASE=y +CONFIG_CBE_RAS=y +CONFIG_CBE_THERM=m +CONFIG_CBE_CPUFREQ=m +CONFIG_CBE_CPUFREQ_PMI=m +CONFIG_OPROFILE_CELL=y ## ## file: arch/powerpc/platforms/celleb/Kconfig @@ -72,7 +85,19 @@ ## ## file: arch/powerpc/platforms/ps3/Kconfig ## -# CONFIG_PPC_PS3 is not set +CONFIG_PPC_PS3=y +CONFIG_PS3_ADVANCED=y +CONFIG_PS3_HTAB_SIZE=20 +# CONFIG_PS3_DYNAMIC_DMA is not set +CONFIG_PS3_VUART=y +CONFIG_PS3_PS3AV=y +CONFIG_PS3_SYS_MANAGER=y +CONFIG_PS3_STORAGE=m +CONFIG_PS3_DISK=m +CONFIG_PS3_ROM=m +CONFIG_PS3_FLASH=m +CONFIG_OPROFILE_PS3=m +CONFIG_PS3_LPM=m ## ## file: arch/powerpc/platforms/pseries/Kconfig @@ -93,7 +118,7 @@ CONFIG_HVC_CONSOLE=y CONFIG_HVCS=m # CONFIG_RTC is not set -# CONFIG_GEN_RTC is not set +CONFIG_GEN_RTC=y CONFIG_HANGCHECK_TIMER=m ## @@ -127,6 +152,24 @@ CONFIG_SPIDER_NET=m # CONFIG_MV643XX_ETH is not set CONFIG_PASEMI_MAC=m +CONFIG_GELIC_NET=m +CONFIG_GELIC_WIRELESS=y +CONFIG_GELIC_WIRELESS_OLD_PSK_INTERFACE=y + +## +## file: drivers/net/ibm_newmac/Kconfig +## +CONFIG_IBM_NEW_EMAC=m +CONFIG_IBM_NEW_EMAC_RXB=128 +CONFIG_IBM_NEW_EMAC_TXB=64 +CONFIG_IBM_NEW_EMAC_POLL_WEIGHT=32 +CONFIG_IBM_NEW_EMAC_RX_COPY_THRESHOLD=256 +CONFIG_IBM_NEW_EMAC_RX_SKB_HEADROOM=0 +# CONFIG_IBM_NEW_EMAC_DEBUG is not set +CONFIG_IBM_NEW_EMAC_ZMII=y +CONFIG_IBM_NEW_EMAC_RGMII=y +CONFIG_IBM_NEW_EMAC_TAH=y +CONFIG_IBM_NEW_EMAC_EMAC4=y ## ## file: drivers/pci/hotplug/Kconfig @@ -159,6 +202,10 @@ # CONFIG_FB_IMSTT is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_ATY128 is not set +CONFIG_FB_PS3=y +CONFIG_FB_PS3_DEFAULT_SIZE_M=9 +CONFIG_FB_LOGO_EXTRA=y +CONFIG_LOGO_LINUX_CLUT224=y ## ## file: drivers/watchdog/Kconfig @@ -176,3 +223,8 @@ # CONFIG_MEMORY_HOTPLUG is not set CONFIG_MIGRATION=y +## +## file: sound/ppc/Kconfig +## +CONFIG_SND_PS3=m +CONFIG_SND_PS3_DEFAULT_START_DELAY=2000 --- linux-2.6-2.6.25.orig/debian/config/defines +++ linux-2.6-2.6.25/debian/config/defines @@ -1,5 +1,5 @@ [abi] -abiname: 2 +abiname: 3 [base] arches: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462529: linux-2.6: Add config file support for efika and PS3 (preliminary)
Bastian Blank wrote: On Wed, May 28, 2008 at 12:28:30PM -0700, Geoff Levand wrote: -# CONFIG_PPC_IBM_CELL_BLADE is not set +CONFIG_PPC_IBM_CELL_BLADE=y CONFIG_SPU_FS=m +CONFIG_SPU_FS_64K_LS=y +CONFIG_CBE_RAS=y +CONFIG_CBE_THERM=m +CONFIG_CBE_CPUFREQ=m Okay. +CONFIG_CBE_CPUFREQ_PMI=m Default n and experimental. OK, we don't need it. -# CONFIG_PPC_PS3 is not set +CONFIG_PPC_PS3=y +CONFIG_PS3_ADVANCED=y +CONFIG_PS3_HTAB_SIZE=20 +# CONFIG_PS3_DYNAMIC_DMA is not set +CONFIG_PS3_PS3AV=m +CONFIG_PS3_STORAGE=m +CONFIG_PS3_DISK=m +CONFIG_PS3_ROM=m +CONFIG_PS3_FLASH=m +CONFIG_PS3_LPM=m This is what I posted: +CONFIG_PPC_PS3=y +CONFIG_PS3_ADVANCED=y +CONFIG_PS3_HTAB_SIZE=20 +# CONFIG_PS3_DYNAMIC_DMA is not set +CONFIG_PS3_VUART=y +CONFIG_PS3_PS3AV=y +CONFIG_PS3_SYS_MANAGER=y +CONFIG_PS3_STORAGE=m +CONFIG_PS3_DISK=m +CONFIG_PS3_ROM=m +CONFIG_PS3_FLASH=m +CONFIG_OPROFILE_PS3=m +CONFIG_PS3_LPM=m CONFIG_PS3_SYS_MANAGER is needed for proper operation. It controls button events and system shutdown. It could be a module, but is is small and with it built-in users can reboot without a forced power off if the root FS is not found. There is a 2.6.25 undefined symbol bug in PS3AV that won't allow it to be built as a module. If you don't want to support profiling, you can disable these: CONFIG_OPROFILE_PS3=n CONFIG_PS3_LPM=n -# CONFIG_GEN_RTC is not set +CONFIG_GEN_RTC=y Why? I am not so familiar with this option. I saw an RTC error message when this was not enabled. Maybe it is not needed? +CONFIG_GELIC_NET=m +CONFIG_GELIC_WIRELESS=y +CONFIG_IBM_NEW_EMAC=m +CONFIG_IBM_NEW_EMAC_RXB=128 +CONFIG_IBM_NEW_EMAC_TXB=64 +CONFIG_IBM_NEW_EMAC_POLL_WEIGHT=32 +CONFIG_IBM_NEW_EMAC_RX_COPY_THRESHOLD=256 +CONFIG_IBM_NEW_EMAC_RX_SKB_HEADROOM=0 +# CONFIG_IBM_NEW_EMAC_DEBUG is not set Okay. +CONFIG_FB_PS3=y Yeah, everyone wants its favorite fb built-in. We can make this a module, the trouble is that PS3 can only output to the virtual frame buffer, and it comes up very late, so the there is a long delay between starting the boot and some text being displayed. Also, if there is a hang before that, the user is left with a blank screen. CONFIG_FB_PS3 depends on CONFIG_PS3_VUART and CONFIG_PS3_PS3AV. +CONFIG_FB_PS3_DEFAULT_SIZE_M=9 We need this. It sets the default size of the virtual frame buffer. This setting will support up to 1080p or WUXGA resolution. +CONFIG_FB_LOGO_EXTRA=y +CONFIG_LOGO_LINUX_CLUT224=y Why? These put the SPE penguins up. Users seem to like (expect?) them: http://www.kernel.org/pub/linux/kernel/people/geoff/cell/debian-penguin-shot.png They aren't needed if CONFIG_FB_PS3=m. Without CONFIG_LOGO_LINUX_CLUT224=y the SPE penguin images are not rendered correctly. I don't know why. +CONFIG_SND_PS3=m +CONFIG_SND_PS3_DEFAULT_START_DELAY=2000 Okay. I can test your proposed config if you make it available to me. -Geoff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483489: linux-2.6: Optional powerpc64 patches for PS3
Package: linux-2.6 Version: 2.6.25 Severity: normal Tags: patch Attached are two patches against the debian linux-2.6-2.6.25 sources that would be nice to apply for the PS3. - debian-powerpc64-vmemmap-variable-page-size.diff This patch changes vmemmap to use a different region (region 0xf) of the address space whose page size can be dynamically configured at boot. The problem with the current approach of always using 16M pages is that it's not well suited to machines that have small amounts of memory such as small partitions on pseries, or PS3's. In fact, on the PS3, failure to allocate the 16M page backing vmmemmap tends to prevent hotplugging the HV's additional memory, thus limiting the available memory even more, from my experience down to something like 80M total, which makes it really not very useable. - debian-powerpc64-ps3-gelic-wireless-fix-memory-leak.patch This fixes the bug that the I/O buffer is not freed at the driver removal. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc64) Kernel: Linux 2.6.25-3-powerpc64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Add the patch powerpc-vmemmap-variable-page-size.diff to the debian linux-2.6-2.6.25 source tree. This is a backport of the patch merged into 2.6.26. --- debian/patches/bugfix/powerpc/powerpc-vmemmap-variable-page-size.diff | 214 ++ debian/patches/series/1 |1 2 files changed, 215 insertions(+) --- /dev/null +++ b/debian/patches/bugfix/powerpc/powerpc-vmemmap-variable-page-size.diff @@ -0,0 +1,214 @@ +ps3-linux-stable-2.6.25 + o Backported to 2.6.25.4 + o Removed DEBUG's + +Subject: [RFC] [PATCH] vmemmap fixes to use smaller pages + +From: Benjamin Herrenschmidt [EMAIL PROTECTED] + +This patch changes vmemmap to use a different region (region 0xf) of the +address space whose page size can be dynamically configured at boot. + +The problem with the current approach of always using 16M pages is that +it's not well suited to machines that have small amounts of memory such +as small partitions on pseries, or PS3's. + +In fact, on the PS3, failure to allocate the 16M page backing vmmemmap +tends to prevent hotplugging the HV's additional memory, thus limiting +the available memory even more, from my experience down to something +like 80M total, which makes it really not very useable. + +The logic used by my match to choose the vmemmap page size is: + + - If 16M pages are available and there's 1G or more RAM at boot, use that size. + - Else if 64K pages are available, use that + - Else use 4K pages + +--- + arch/powerpc/mm/hash_utils_64.c | 28 ++-- + arch/powerpc/mm/init_64.c |8 + arch/powerpc/mm/slb.c | 14 +- + arch/powerpc/mm/slb_low.S | 16 +--- + include/asm-powerpc/mmu-hash64.h|1 + + include/asm-powerpc/pgtable-ppc64.h | 10 +- + 6 files changed, 62 insertions(+), 15 deletions(-) + +--- a/arch/powerpc/mm/hash_utils_64.c b/arch/powerpc/mm/hash_utils_64.c +@@ -93,6 +93,9 @@ unsigned long htab_hash_mask; + int mmu_linear_psize = MMU_PAGE_4K; + int mmu_virtual_psize = MMU_PAGE_4K; + int mmu_vmalloc_psize = MMU_PAGE_4K; ++#ifdef CONFIG_SPARSEMEM_VMEMMAP ++int mmu_vmemmap_psize = MMU_PAGE_4K; ++#endif + int mmu_io_psize = MMU_PAGE_4K; + int mmu_kernel_ssize = MMU_SEGSIZE_256M; + int mmu_highuser_ssize = MMU_SEGSIZE_256M; +@@ -363,11 +366,32 @@ static void __init htab_init_page_sizes( + } + #endif /* CONFIG_PPC_64K_PAGES */ + ++#ifdef CONFIG_SPARSEMEM_VMEMMAP ++ /* We try to use 16M pages for vmemmap if that is supported ++ * and we have at least 1G of RAM at boot ++ */ ++ if (mmu_psize_defs[MMU_PAGE_16M].shift ++ lmb_phys_mem_size() = 0x4000) ++ mmu_vmemmap_psize = MMU_PAGE_16M; ++ else if (mmu_psize_defs[MMU_PAGE_64K].shift) ++ mmu_vmemmap_psize = MMU_PAGE_64K; ++ else ++ mmu_vmemmap_psize = MMU_PAGE_4K; ++#endif /* CONFIG_SPARSEMEM_VMEMMAP */ ++ + printk(KERN_DEBUG Page orders: linear mapping = %d, +- virtual = %d, io = %d\n, ++ virtual = %d, io = %d ++#ifdef CONFIG_SPARSEMEM_VMEMMAP ++ , vmemmap = %d ++#endif ++ \n, + mmu_psize_defs[mmu_linear_psize].shift, + mmu_psize_defs[mmu_virtual_psize].shift, +- mmu_psize_defs[mmu_io_psize].shift); ++ mmu_psize_defs[mmu_io_psize].shift ++#ifdef CONFIG_SPARSEMEM_VMEMMAP ++ ,mmu_psize_defs[mmu_vmemmap_psize].shift ++#endif ++ ); + + #ifdef CONFIG_HUGETLB_PAGE + /* Init large page size. Currently, we pick 16M or 1M depending +--- a/arch/powerpc/mm/init_64.c b/arch/powerpc/mm/init_64.c +@@ -208,12 +208,12 @@ int __meminit vmemmap_populated(unsigned + } + + int __meminit vmemmap_populate(struct page *start_page, +- unsigned
Bug#462529: linux-2.6: Add config file support for efika and PS3 (preliminary)
Hi, Robert Millan wrote: retitle 462529 please enable PS3 support in -powerpc64 build thanks On Thu, May 15, 2008 at 04:46:10PM +0200, Sven Luther wrote: On Thu, May 15, 2008 at 04:25:40PM +0200, Robert Millan wrote: Please provide a patch if you can. I already provided a patch, which is smoledring in the BTS, since months now. Thanks Sven. I just updated your patch to the latest version of the package (moving the definitions to the pre-existing PS3 section), but I cannot check if it still works. Is it safe to assume it does? In any case, would be nice if someone could test. I'm sorry I'm not so familiar with how to build the debian kernel, but if you give me some help where and how to get the sources, or a link to some docs that explain it I will do the testing. I have an up to date install of Lenny on PS3 here to use. -Geoff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
