Bug#1054459: debian-installer: Debian 12.2 amd64 netinst failes to find a kernel image for a Dell 7812
Package: debian-installer Version: debian installer found on amd64 12.2 netinst.iso Severity: important Dear Maintainer, I have several systems and have experienced this difficulty only with the Dell 7812 with an Xeon E5 CPU. The debian 12.2.0 amd64 netinst.iso boots normally and seems to start normally. When it gets to finding a kernel to install, it complains that it cannot find a suitable kernel. I had the same results with debian 12.2 adm64 dvd-1.iso and dlbd-1.iso When I booted the debian 12.2 amd64 live.iso system, its installer ran OK. I am running on the system installed from the live installer right now. This is what made the lspci. I also successfully managed to perform a dist-upgrade from an install of debian 11.6. -- System Information: Debian Release: 12.2 Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-13-amd64 (SMP w/56 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled 00:00.0 Host bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2 (rev 01) 00:01.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1 (rev 01) 00:01.1 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1 (rev 01) 00:02.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2 (rev 01) 00:03.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 (rev 01) 00:03.1 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 (rev 01) 00:03.2 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 (rev 01) 00:03.3 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 (rev 01) 00:05.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Map/VTd_Misc/System Management (rev 01) 00:05.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO Hot Plug (rev 01) 00:05.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO RAS/Control Status/Global Errors (rev 01) 00:05.4 PIC: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D I/O APIC (rev 01) 00:11.0 Unassigned class [ff00]: Intel Corporation C610/X99 series chipset SPSR (rev 05) 00:11.4 SATA controller: Intel Corporation C610/X99 series chipset sSATA Controller [AHCI mode] (rev 05) 00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI Host Controller (rev 05) 00:16.0 Communication controller: Intel Corporation C610/X99 series chipset MEI Controller #1 (rev 05) 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 05) 00:1a.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #1 (rev d5) 00:1c.1 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #2 (rev d5) 00:1d.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation C610/X99 series chipset LPC Controller (rev 05) 00:1f.2 RAID bus controller: Intel Corporation C600/X79 series chipset SATA RAID Controller (rev 05) 00:1f.3 SMBus: Intel Corporation C610/X99 series chipset SMBus Controller (rev 05) 03:00.0 VGA compatible controller: NVIDIA Corporation GK104GL [Quadro K5000] (rev a1) 03:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev a1) 09:00.0 PCI bridge: Texas Instruments XIO2001 PCI Express-to-PCI Bridge df:08.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D QPI Link 0 (rev 01) df:08.2 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D QPI Link 0 (rev 01) df:08.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D QPI Link 0 (rev 01) df:09.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D QPI Link 1 (rev 01) df:09.2 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D QPI Link 1 (rev 01) df:09.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D QPI Link 1 (rev 01) df:0b.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 (rev 01) df:0b.1 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 (rev 01) df:0b.2 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 (rev 01) df:0b.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link Debug (r
Bug#998664: Acknowledgement (libntl43: undefined reference to `NTL::sub(NTL::ZZ&, NTL::ZZ const&, long))
This calling/type signature worked with buster that had libntl version 10.5.0. I'm faced with several workaround choices: a) custom install libntl 10.5.0 in /usr/local/lib and change the compiler and linker commands to search this directory first b) revert to buster which implements 10.5.0 c) recode source to not use this calling signature d) run bullseye with libntl35 package installed; have not tried this since choice 1) is so much easier for me On 11/5/21 4:03 PM, Debian Bug Tracking System wrote: Thank you for filing a new Bug report with Debian. You can follow progress on this Bug here: 998664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998664. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. As you requested using X-Debbugs-CC, your message was also forwarded to d...@its.caltech.edu (after having been given a Bug report number, if it did not have one). Your message has been sent to the package maintainer(s): Debian Science Maintainers If you wish to submit further information on this problem, please send it to 998...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
Bug#998664: libntl43: undefined reference to `NTL::sub(NTL::ZZ&, NTL::ZZ const&, long)
Package: libntl43
Version: 11.4.3-1+b1
Severity: normal
X-Debbugs-Cc: d...@its.caltech.edu
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 11.1
APT prefers stable-security
APT policy: (500, 'stable-security')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-9-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libntl43 depends on:
ii libc62.31-13+deb11u2
ii libgcc-s1 [libgcc1] 10.2.1-6
ii libgf2x3 1.3.0-1+b1
ii libgmp10 2:6.2.1+dfsg-1
ii libstdc++6 10.2.1-6
libntl43 recommends no packages.
libntl43 suggests no packages.
-- no debconf information
Here is the program that reproduces the problem when compiled:
#include
#include
#include
int bugdemo(NTL::ZZ & result, const NTL::ZZ &left, long right) {
result = left - right;
return 0;
}
int main(int argc, char* argv[]) {
NTL::ZZ u,v;
long w;
v = 4;
w = 4;
bugdemo(u,v,w);
}
Bug#989962: proceeding with bullseye checking using debian-bullseye-DI-rc1-amd64-DVD-1.iso and apt-mark hold shim-signed
To whom it may concern: I decided not to wait for updated version of shim-signed that runs on the very old Dell T1600 I'm proceeding with bullseye checkout using shim-signed package found on debian-bullseye-DI-rc1-amd64-DVD-1.iso This version of shim-signed works with me T1600 and its Xeon E3. Others can take advantage of this too. Procedure: install the abovementioned dvd without any ethernet connection to get working shim-signed apt-mark hold shim-signed (keeps old dvd-1 copy of shim-signed intact) connect the ethernet modify sources.list to refer to the debian online repository apt-get update Now I can check out the packages that really matter to me: gcc, g++, cython3, python3-numpy, libntl-dev, etc.
Bug#989962: update to the version of shim-signed(Re: Bug#989962: shim-signed 1.36~1+deb10u1 fails to boot some systems)
Updated: the email is incorrect: this is the version shown in Debian 10 security : shim-signed (1.36~1+deb10u2+15.4-5~deb10u1) On 6/28/21 9:19 AM, David George Henderson III wrote: Hello Steve, I generally install Debian off of DVD or a *.iso copied to flash rather than an online repository. That way I get a reproducible install. Recently, I found that my Debian 10.9 amd64 dvd-1 install stopped working on the Dell T1600 boot in UEFI mode. This is the machine that does not support secure boot. The symptoms were that the install went as expected, but the boot failed complaining about MOK list being exhausted. What I discovered was that security updates were being applied during the install off dvd: I noticed the message 'applying security updates' that flashed by briefly during the install from DVD. I surmise that the version of shim-signed in security.debian.org was being applied when the ethernet to the cable modem was plugged in. (the web site shows shim-signed (1.36~1+deb10u1+15.4-5~deb10u1) in Debian 10 security ) An install if 10.9 off of the same dvd without the ethernet cable plugged in installed and booted normally. I'm surprised at this behavior. I would have expected that these updates would be applied after booting the installed system rather than during the install. Using the Dell T1600 and the system installed with no ethernet cable connection: I copied the shim-signed file from the attachment below into /boot/efi/EFI/debian. Then I shut down and rebooted. I could not tell if a MOK message came up because something flashed by very quickly. Debian 10.9 booted up as expected. I hope this fix makes it into the online security repository. David David On 6/22/21 2:36 PM, Steve McIntyre wrote: On Tue, Jun 22, 2021 at 09:20:36PM +0200, Grzegorz Szymaszek wrote: On Tue, Jun 22, 2021 at 01:35:51PM +0200, Grzegorz Szymaszek wrote: I have recently upgraded several buster amd64 machines; shim-signed went up from 1.33 to 1.36~1+deb10u1. […] FWIW, upgrading to 1.36~1+deb10u2 brings the problem back. Looks like the same as #990158. Yes, it's the same problem. I'm testing a fix now. Could you please verify if this new build fixes the problem you're seeing on your hardware? https://people.debian.org/~93sam/shim/ has a new *unsigned* amd64 shim binary, and a checksum file. If you would be so kind, please copy that shimx64.efi binary into place on your system and test it boots OK. It may still complain about resource failures and "import_mok_state() failed", but should then boot anyway in non-secure mode.
Bug#989962: debian-bullseye-DI-rc2-amd64-DVD-1.iso image on flash media flash fails to boot on a system that does not support secure boot
Steve, I goofed on the model number, its a T1600, not a T1200. I've created a text file from /proc/cpuinfo; see attachment. The T1600 has a 11.rc1 system that installs OK but does not directly boot off the disk drive; what does work is EFI booting an existing Debian 10.9 system and placing the 11.rc1 grub stanza inside the 10.9 /etc/grub.d/40_custom file ; see Bug#989962 I have performed an 11.rc2 install via bios mode booting 11.rc2 media and performing an install without any use of EFI All my laptops boot in secure boot mode; this is greatly appreciated. I perform test installs to this T1600 system to emulate the laptop configuration. What matters the most to me is the compiler/library configuration. At the moment I'm using gnu gcc/g++ because the llvm and clang compilers on Debian 10 failed to execute some intricate c++ code. In the big picture, it does not matter very much if the T1600 boots bios mode or UEFI mode. David On 6/17/21 5:27 PM, Steve McIntyre wrote: Control: reassign -1 shim-signed Control: reassign 989810 shim-signed Hi David! On Wed, Jun 16, 2021 at 01:50:51PM -0700, David George Henderson III wrote: Package: grub-efi-amd64 The system is a Dell Precision T1200 E3, 16GB of memory,booting off flash copy of debian-bullseye-DI-rc2-amd64-DVD-1.iso Booting the rc2 version flash drive fails to go into the normal menus. (note bug 989810 my experiences with rc1 ; it installed as expected but the installed system failed to boot) The delivers the following messages and halts(I had only a few seconds to capture the gist): MoklistRT out of resources MoklistXRT out of resources import moc state() -- didn't have time to even get the gist of this error message OK. These messages are from shim, which runs before GRUB on a Secure Boot setup. Your problem isn't that your system does not support SB, it's just that it's running out of EFI variable storage space. Shim is trying to store copies of some of its internal variables, and that's failing. That's painful. :-( Google is refusing to find me anything about your system, which is surprising. Could you give me an idea of its age and the rest of its specs please? As a workaround for your installed system: if you're not wanting / trying to use SB, you could try booting with older bullseye media in Rescue mode. Get into the booted system and run # apt-get remove --purge shim-signed # grub-install and that should let you get in OK after that. processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Xeon(R) CPU E31240 @ 3.30GHz stepping: 7 microcode : 0x2f cpu MHz : 1600.719 cache size : 8192 KB physical id : 0 siblings: 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts md_clear flush_l1d vmx flags : vnmi preemption_timer invvpid ept_x_only flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit bogomips: 6584.98 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Xeon(R) CPU E31240 @ 3.30GHz stepping: 7 microcode : 0x2f cpu MHz : 1623.585 cache size : 8192 KB physical id : 0 siblings: 8 core id : 1 cpu cores : 4 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts md_clear flush_l1d vmx flags : vnmi preemption_timer invvpid ept_x_only flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest bugs
Bug#989962: shim-signed 1.36~1+deb10u1 fails to boot some systems
Hello Steve, I generally install Debian off of DVD or a *.iso copied to flash rather than an online repository. That way I get a reproducible install. Recently, I found that my Debian 10.9 amd64 dvd-1 install stopped working on the Dell T1600 boot in UEFI mode. This is the machine that does not support secure boot. The symptoms were that the install went as expected, but the boot failed complaining about MOK list being exhausted. What I discovered was that security updates were being applied during the install off dvd: I noticed the message 'applying security updates' that flashed by briefly during the install from DVD. I surmise that the version of shim-signed in security.debian.org was being applied when the ethernet to the cable modem was plugged in. (the web site shows shim-signed (1.36~1+deb10u1+15.4-5~deb10u1) in Debian 10 security ) An install if 10.9 off of the same dvd without the ethernet cable plugged in installed and booted normally. I'm surprised at this behavior. I would have expected that these updates would be applied after booting the installed system rather than during the install. Using the Dell T1600 and the system installed with no ethernet cable connection: I copied the shim-signed file from the attachment below into /boot/efi/EFI/debian. Then I shut down and rebooted. I could not tell if a MOK message came up because something flashed by very quickly. Debian 10.9 booted up as expected. I hope this fix makes it into the online security repository. David David On 6/22/21 2:36 PM, Steve McIntyre wrote: On Tue, Jun 22, 2021 at 09:20:36PM +0200, Grzegorz Szymaszek wrote: On Tue, Jun 22, 2021 at 01:35:51PM +0200, Grzegorz Szymaszek wrote: I have recently upgraded several buster amd64 machines; shim-signed went up from 1.33 to 1.36~1+deb10u1. […] FWIW, upgrading to 1.36~1+deb10u2 brings the problem back. Looks like the same as #990158. Yes, it's the same problem. I'm testing a fix now. Could you please verify if this new build fixes the problem you're seeing on your hardware? https://people.debian.org/~93sam/shim/ has a new *unsigned* amd64 shim binary, and a checksum file. If you would be so kind, please copy that shimx64.efi binary into place on your system and test it boots OK. It may still complain about resource failures and "import_mok_state() failed", but should then boot anyway in non-secure mode.
Bug#989962: debian-bullseye-DI-rc2-amd64-DVD-1.iso image on flash media flash fails to boot on a system that does not support secure boot
Package: grub-efi-amd64 The system is a Dell Precision T1200 E3, 16GB of memory,booting off flash copy of debian-bullseye-DI-rc2-amd64-DVD-1.iso Booting the rc2 version flash drive fails to go into the normal menus. (note bug 989810 my experiences with rc1 ; it installed as expected but the installed system failed to boot) The delivers the following messages and halts(I had only a few seconds to capture the gist): MoklistRT out of resources MoklistXRT out of resources import moc state() -- didn't have time to even get the gist of this error message
Bug#989810: debian 11 rc1 boot sequence fails attempting to run secure boot code on a system that does not support secure boot
Package: grub-efi-amd64 Summary: The defect occurs on a bullseye.rc1 install ; install went normally using bullseye rc1; booting the installed system fails the UEFI boot sequence on a system that doesn't support secure boot fails trying to access owner MOK Hello Debian bullseye boot sequence team, I dont have a screen grab and the message only stayed up a few seconds. The system is a Dell Precision T1200 E3, 16GB of memory, SSD, installing off CDROM to an encrypted LVM with dedicated /boot and encrypted LVM partitions. The bullseye system was installed using the bullseye rc1 system for an amd64 target. Installation went normally; the difficulty lies when attempting to boot the installed system off the ssd. Again, the boot time error message that briefly showed on the screen is that the MOK machine owner key could not be accessed. I found a workaround using a previously installed Buster 10.9 system with a similar configuration: a) boot Buster 10.9 dvd in recovery mode b) rewrite the SSD bootstrap so the Buster 10.9 system boots c) reboot into Buster 10.9 to diagnose what was going on I ran : mokutil --disable-validation the error message returned was 'this system does not support secure boot' d) update buster /etc/grub.d/40_custom so it has the bullseye rc1 boot stanza e) update grub f) shutdown the system g) boot the buster grub and select the bullseye 11 rc1 boot stanza present in 40_custom bullseye rc1 now runs
Bug#916386: Success installing Debian buster/testing using 12/3/2018 amd64.iso
Package: installation-reports Boot method: flash drive Image version: debian-testing-amd64-DVD-1.iso dated 12/3/2018 Date: 12/13/2018 Machine: Macintosh Macbook Pro model 5,1 Processor: Core 2 Duo Memory:4gb Partitions: Installed to separate /boot and encrypted LVM with swap and root. Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Used dd to copy installer from *.iso to a flash drive. Installed from flash drive and hardwired ethernet. Only anomaly was going to sid for broadcom b43 wifi firmware post-install. Not sure if this a bug or simply incomplete definition of buster.
Bug#916381: installation-reports: Sucessful install and boot of Buster on Macboot Pro 5,1
Package: installation-reports Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: Boot method: flash drive Image version: Buster amd64 dvd-1 iso of December 3,2018 Date: Machine: Macbook Pro model 5,1 Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="9 (stretch) - installer build 20170615+deb9u4" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux hp470prod 4.9.0-7-amd64 #1 SMP Debian 4.9.110-1 (2018-07-05) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:5904] (rev 02) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234] lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:5916] (rev 02) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234] lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234] lspci -knn: Kernel driver in use: xhci_hcd lspci -knn: Kernel modules: xhci_pci lspci -knn: 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234] lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234] lspci -knn: 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] [8086:9d03] (rev 21) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234] lspci -knn: Kernel driver in use: ahci lspci -knn: Kernel modules: ahci lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:9d10] (rev f1) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 [8086:9d14] (rev f1) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 [8086:9d15] (rev f1) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 [8086:9d18] (rev f1) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:9d4e] (rev 21) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234] lspci -knn: 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234] lspci -knn: 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:9d71] (rev 21) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234] lspci -knn: 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234] lspci -knn: 01:00.0 3D controller [0302]: NVIDIA Corporation GM108M [GeForce 930MX] [10de:134e] (rev a2) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8235] lspci -knn: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8234] lspci -knn: Kernel driver in use: r8169 lspci -knn: Kernel modules: r8169 lspci -knn: 03:00.0 Network controller [0280]: Intel Corporation Device [8086:24fd] (rev 78) lspci -knn:
Bug#916233: Difficulty with Debian Buster netinst dvd on Mac Pro 1,1
Package: d-i.debian.org Severity: important I'm trying to install Debian testing on a Mac Pro 1,1 dedicated boot/swap/root partition set. The 12/3/2018 debian-testing-amd64-i386-netinst.iso DVD boots using the refit boot manager. It hangs at the first splash screen when I select install for amd64. This is very similar to what I notice in 915...@bugs.debian.org What works to install Debian Buster/testing on a Mac Pro 1,1 with Radeon 570 video card: 1. Install Jessie/amd64 without X11 using the amd64-i386 netinst dvd 2. Perform a dist-upgrade to Buster, still without any X11. The dist-upgrade ran without an intermediate upgrade to Stretch. After doing this I have a functional system with no X11 window manager using firmware video. (This was tested with a shutdown and reboot) 3. After performing the dist-upgrade to buster: a. install xserver-xorg-video-nouveau b. install xfce following directions in https://wiki.debian.org/Xfce What seems to be failing with the Buster amd64-i386 netinst: It looks like installer disk seems to be running the xserver-xorg-video-radeon driver. This behavior for xserver-xorg-video-radeon seems to have started with Stretch The Mac Pro 1,1 has a 32 bit ia32 EFI firmware. I have never gotten the radeon driver to work on this machine for either Stretch or Buster. What does work is xserver-xorg-video-nouveau I have a change suggestion for the debian installer: Go back to using the text window installer. If you can't go back to using the text window installer, run installer under xserver-xorg-video-nouveau Init: systemd (via /run/systemd/system) *** /home/dgh/mp_config.txt dgh@mpgpt:~$ lspci 00:00.0 Host bridge: Intel Corporation 5000X Chipset Memory Controller Hub (rev 30) 00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 2-3 (rev 30) 00:03.0 Non-VGA unclassified device: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev 30) 00:04.0 PCI bridge: Intel Corporation 5000X Chipset PCI Express x16 Port 4-7 (rev 30) 00:05.0 Non-VGA unclassified device: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 (rev 30) 00:06.0 Non-VGA unclassified device: Intel Corporation 5000 Series Chipset PCI Express x4 Port 6 (rev 30) 00:07.0 Non-VGA unclassified device: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 (rev 30) 00:08.0 System peripheral: Intel Corporation 5000 Series Chipset DMA Engine (rev 30) 00:10.0 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 30) 00:10.1 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 30) 00:10.2 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 30) 00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 30) 00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 30) 00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 30) 00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 30) 00:1b.0 Audio device: Intel Corporation 631xESB/632xESB High Definition Audio Controller (rev 09) 00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09) 00:1c.1 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 2 (rev 09) 00:1c.2 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 3 (rev 09) 00:1c.3 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 4 (rev 09) 00:1d.0 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09) 00:1d.1 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09) 00:1d.2 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09) 00:1d.3 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 (rev 09) 00:1d.7 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9) 00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09) 00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09) 00:1f.2 SATA controller: Intel Corporation 631xESB/632xESB SATA AHCI Controller (rev 09) 00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09) 01:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01) 01:00.1 PIC: Intel Corporation 6311ESB/6321ESB I/OxAPIC Interrupt Controller (rev 01) 01:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01) 02:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01) 02:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream
Bug#916093: netinst amd64-i386.iso buster dvd fails to find kernel for Mac Pro 1,1 with i386 target
Package: d-i.debian.org Severity: important The dvd is dated 12/3/2018. Its the dvd that mounts with the volume label: /debian-testing-amd64-i386-netinst.iso Installing for the i386 target on a Mac Pro 1,1 produces the error message: "No installable kernel was found in the defined APT sources." What I have done to get around this bug is to install a previous release, then perform dist-upgrade
Bug#915813: d-i.debian.org: netinst 9.6.0 success with i386 as target, hangs in initial screen when amd64 as target
Package: d-i.debian.org Severity: important I have a Mac Pro 1,1 that is currently running 8.11.0 using a Radeon 570 video card. I am using refit boot selector to boot the debian 9.6.0 amd64-i386 netinst.iso Also installed on separation partitions: OSX Snow Leopard. This hosts the refit program. What works: boot the *.iso and installing i386 on separate boot/swap/root partitions. What doesn't work: boot the *.iso and select the amd64 CPU option. The installer program just hangs at the first spash screen. I tested the install dvd on another system with UEFI (a modern HP 470 G4). It boots in UEFI mode and started to actually run the installer. An alternate was tried. dist-upgrade on a running amd64 system. It does not work for me. Here is the procedure I used: a) install a sacrificial 8.11.0 amd64 system on the same set of partitions targeted for the 9.6.0 install b) modify the /etc/apt/sources.list to use stretch doing a dist-upgrade; shut down and reboot production system. on the production 8.11 system , created a grub boot stanza in 40_custom for the 9.6.0 dist-upgrade partition set make sure nomodeset is present update-grab then boot the production system using the 40_custom boot stanza for the 9.6.0 dist-upgrade target partition set: just shows loading vmzlinux and hangs I have looked at the xorg modules installed before and after the dist-upgrade- they all seem to be ATI or Radeon related. My tentative conclusion is that something about the radeon video card and the amd64 option Mac Pro 1,1 is not compatible with Stretch. a)The radeon video card works fine with Jessie installer dvd and 8.11.0 on the installed system. b)The radeon video card works fine on Stretch i386 installed system. -- System Information (Note this is the system used to report the bug, not the one using the install dvd): Debian Release: 9.5 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-7-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) *** /home/dgh/mp_config.txt dgh@mpgpt:~$ lspci 00:00.0 Host bridge: Intel Corporation 5000X Chipset Memory Controller Hub (rev 30) 00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 2-3 (rev 30) 00:03.0 Non-VGA unclassified device: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev 30) 00:04.0 PCI bridge: Intel Corporation 5000X Chipset PCI Express x16 Port 4-7 (rev 30) 00:05.0 Non-VGA unclassified device: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 (rev 30) 00:06.0 Non-VGA unclassified device: Intel Corporation 5000 Series Chipset PCI Express x4 Port 6 (rev 30) 00:07.0 Non-VGA unclassified device: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 (rev 30) 00:08.0 System peripheral: Intel Corporation 5000 Series Chipset DMA Engine (rev 30) 00:10.0 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 30) 00:10.1 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 30) 00:10.2 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 30) 00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 30) 00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 30) 00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 30) 00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 30) 00:1b.0 Audio device: Intel Corporation 631xESB/632xESB High Definition Audio Controller (rev 09) 00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09) 00:1c.1 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 2 (rev 09) 00:1c.2 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 3 (rev 09) 00:1c.3 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 4 (rev 09) 00:1d.0 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09) 00:1d.1 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09) 00:1d.2 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09) 00:1d.3 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 (rev 09) 00:1d.7 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9) 00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09) 00:1f.1 IDE int
Bug#805264: constructor gmpy2.xmpz(z[k]) where z is a numpy int32 array - more context
Hi Martin, I'm not far enough along to create a performance comparison. The immediate functionality is the gram-schmidt factorization of a lattice basis matrix stored in columns of int32 vectors. The numpy array of objects are the orthogonalized vectors and the dot product is the time-critical code to optimize. Please forgive my jargon, its not relevant to the bug. It seems plausible that there is a bytecode reference to an int32 array component that is defined independently of the numpy library. If this is indeed the case, the gmpy2.xmpz() constructor could be reworked to accept this datatype as input. After all, Python2 short ints are int32. The code I'm writing handles each of native int(), gmpy2.mpz() and gmpy2.xmpz() objects for the containers for big integer vector components. Each orthogonalized vector is as an numpy array of object (each object is a xmpz or other bigint container). The gmpy2.xmpz objects are going to have extremely large magnitudes. Its unclear whether the int(z[i]) is going to be a big hit in performance. What is clear that I'm going to be recalculating the int32 arrays quite frequently in each step of lattice basis reduction. A numpy dtype=int32 array holds mutable int32 array components. This is the functionality I'd like to mimic with a numpy dtype=object array where each object is a mutable xmpz. I'll certainly be doing a timing analysis on each implementation alternative. I'm not counting on the gmpy2.xmpz working because it is written up as experimental. Would you please forward this elaboration to the ultimate maintainer of gmpy2? Thanks in advance, David
Bug#805264: What I expected to to happen with gmpy2.mpz/gmpy2.xmpz
What I'm attempting to do is perform a dot product of an int32 array with a list of mpz integers. z=np.zeros(10,np.int32) y=[gmpy.mpz[1] *10 ] summation = gmp.xmpz(0) for i in range(0,10): product = gmpy2.xmpz(z[i]) product *= y[i] summation += product The bug prevents this from running. My workaround defeats the purpose of using gmpy2.xmpz typed variables : for i in range(0,10): product = gmpy2.xmpz(int(z[i]))
Bug#805264: python3-gmpy2: When z is a numpy array of int32, gmpy2.mpz(z[3]) reports TypeError: mpz() requires numeric or string argument
Package: python3-gmpy2
Version: 2.0.3-1+b1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 8.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python3-gmpy2 depends on:
ii libc62.19-18+deb8u1
ii libgmp10 2:6.0.0+dfsg-6
ii libmpc3 1.0.2-1
ii libmpfr4 3.1.2-2
ii python-gmpy2-common 2.0.3-1
ii python3 3.4.2-2
python3-gmpy2 recommends no packages.
python3-gmpy2 suggests no packages.
-- no debconf information
Using numpy installed by aptitude: python3-numpy_1.8.2-2_amd64.deb
The following program reproduces the error. The assignment to xmpz5 shows the
diagnostic message.
import numpy as np
import gmpy2
z32 = np.zeros(10,np.int32)
for i in range(0,10):
z32[i] = 3200 + i
z64 = np.zeros(10,np.int64)
for i in range(0,10):
z64[i] = 6400 + i
a5 = gmpy2.mpz(5)
aa5= gmpy2.mpz(a5)
x5= gmpy2.xmpz(5)
xx5=gmpy2.xmpz(x5)
print("value of a5 is %d"%(a5))
print("value of aa5 is %d"%(aa5))
print("value of x5 is %d"%(x5))
print("value of xx5 is %d"%(xx5))
mpz5 =gmpy2.mpz(z32[5])
print("value of mpz5 is %d"%(mpz5))
mpz9 =gmpy2.mpz(z64[9])
print("value of mpz9 is %d"%(mpz9))
xmpz3 =gmpy2.mpz(z32[3])
print("value of xmpz3 is %d"%(xmpz3))
xmpz7 =gmpy2.mpz(z64[7])
print("value of xmpz7 is %d"%(xmpz7))
