Bug#819470: installation-reports: Reiser4 Software Format Release Number 4.0.1 kernel successfully installed on Debian Stretch
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: CD Image version: Sid (Unstable) d-i Date: 03-28-2016 Machine: VirtualBox Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on udev devtmpfs371716 0371716 0% /dev tmpfs tmpfs76280 1356 74924 2% /run /dev/sda5 reiser46123092 605608 5517484 10% / tmpfs tmpfs 381380 0381380 0% /dev/shm tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 381380 0381380 0% /sys/fs/cgroup /dev/sda6 jfs3876540 233852 3642688 7% /var /dev/sda1 ext2140805 32524101011 25% /boot tmpfs tmpfs76280 0 76280 0% /run/user/1000 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: One to the smoothest Reiser4 installations I've ever done. -- 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 20160325-08:35" X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == uname -a: Linux oyohualli 4.4.0-1-amd64 #1 SMP Debian 4.4.6-2 (2016-03-17) x86_64 Xonecuiltzin lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01) lspci -knn: Kernel driver in use: ata_piix lspci -knn: Kernel modules: ata_piix, ata_generic lspci -knn: 00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] lspci -knn: 00:03.0 Ethernet controller [0200]: Intel Corporation 82540EM Gigabit Ethernet Controller [8086:100e] (rev 02) lspci -knn: Subsystem: Intel Corporation Device [8086:001e] lspci -knn: Kernel driver in use: e1000 lspci -knn: Kernel modules: e1000 lspci -knn: 00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH VirtualBox Guest Service [80ee:cafe] lspci -knn: 00:06.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f] lspci -knn: Kernel driver in use: ohci-pci lspci -knn: Kernel modules: ohci_pci lspci -knn: 00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 08) lspci -knn: 00:0d.0 SATA controller [0106]: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] [8086:2829] (rev 02) lspci -knn: Kernel driver in use: ahci lspci -knn: Kernel modules: ahci usb-list: usb-list: Bus 01 Device 01: OHCI PCI host controller [1d6b:0001] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 00 usb-list:Manufacturer: Linux 4.4.0-1-amd64 ohci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 01 Device 02: USB Tablet [80ee:0021] usb-list:Level 01 Parent 01 Port 00 Class 00(>ifc ) Subclass 00 Protocol 00 usb-list:Manufacturer: VirtualBox usb-list:Interface 00: Class 03(HID ) Subclass 00 Protocol 00 Driver usbhid lsmod: Module Size Used by lsmod: nls_utf8 16384 1 lsmod: dm_mod110592 0 lsmod: md_mod135168 0 lsmod: xfs 954368 0 lsmod: libcrc32c 16384 1 xfs lsmod: reiser4 434176 1 lsmod: jfs 176128 1 lsmod: crc32c_generic 16384 4 lsmod: btrfs 970752 0 lsmod: xor24576 1 btrfs lsmod: raid6_pq 102400 1 btrfs lsmod: ntfs 200704 0 lsmod: vfat 20480 0 ls
Bug#819484: installation-reports: Successful Reiser4 Software Format Release Number 4.0.1 kernel installed on Debian Sid
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: CD Image version: Unstable (Sid) d-i Date: March 03, 2016 Machine: HP Pavilion dv6-6c53cl Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on udev devtmpfs 81678400 8167840 0% /dev tmpfs tmpfs 1634408 972 1633436 1% /run /dev/sda15 reiser4 92435000 74331708 18103292 81% / tmpfs tmpfs 51204 5116 1% /run/lock tmpfs tmpfs 385516018300 3836860 1% /run/shm /dev/sda9 ext213626986373 42626 67% /boot /dev/sda12 jfs 80317856 73055436 7262420 91% /home cgroup tmpfs 12012 0% /sys/fs/cgroup cgmfs tmpfs 1000 100 0% /run/cgmanager/fs tmpfs tmpfs 1634408 16 1634392 1% /run/user/119 tmpfs tmpfs 1634408 36 1634372 1% /run/user/1000 /dev/sda13 reiser4 9730 8264288 89035712 9% /mnt/sda13 /dev/sda1 jfs 123243648 75285948 47957700 62% /mnt/abc /dev/sda8 reiser4 61468304 49140316 12327988 80% /mnt/def /dev/sda11 reiser4 92791120 46791348 45999772 51% /mnt/ghi /dev/sda14 ext4 25066604 14563168 9207052 62% /mnt/uvw /dev/sda17 reiser4 24170476 12561380 11609096 52% /mnt/xyz Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Reiser4 SFRN 4.0.1-enabled d-i smooth installation. -- 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 20160303-06:42" X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == uname -a: Linux cohuatlicue 4.4.0-1+reiser4.0.1-amd64 #1 SMP Debian 4.4.2-3+reiser4.0.1 (2016-02-21) x86_64 Xonecuiltzin lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1658] lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1658] lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1658] lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1658] lspci -knn: Kernel driver in use: ehci-pci lspci -knn: Kernel modules: ehci_pci lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 05) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1658] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 [8086:1c12] (rev b5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 [8086:1c14] (rev b5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b5) lspci -knn: Ker
Re: [RFC] screen/tmux support for network-console
On Sun, Mar 6, 2016 at 9:29 PM, Roger Shimizu wrote: > Yes, UI/cursor-hightlight is bit strange. But it at least works. > I'll try to make libraries, introduced by screen, udeb support first, > and then fix the UI issue. Some progress updates for this RFC. I have made a few libraries udeb supported, and submitted patches by bug report [0][1][2]. There may need some time before those patches would be merged, and package get released. My question is, can I use local udeb library to build my udeb version of screen? and how? I find udeb related documentation is quite limited, so I ask the lists. Thank you and look forward to your reply! [0] https://bugs.debian.org/819358 [1] https://bugs.debian.org/819359 [2] https://bugs.debian.org/819397 Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 17B3ACB1
Simultaneous EFI and Legacy bootloader installation
Hi, I was briefly discussing this with Steve McIntyre and wanted to bring it to a wider discussion. Currently users need to make a selection at installation time whether to install in UEFI mode or in Legacy mode. If they installed in legacy mode and later discovered that their system supported extra features in UEFI mode (For example firmware updates) they are penalized and need to redo the installation in order to switch modes. I'd like to propose changing this and by default install both legacy and UEFI bootloaders on architectures that support both regardless of which mode the system is running in at installation. Making this change has a few obvious implications: * The installation disk would always be formatted GPT. * An ESP would always be created. * If the user is in legacy at installation time, it's not possible to create an EFI boot entry since EFI runtime services aren't present. The removable media fallback path (\efi\boot\boot$ARCH.efi) will need to be used to boot the system at this point and at some point create a "debian" NVRAM boot entry I'm not aware of any modern systems that are unable to boot a GPT partitioned disk. If there are systems like this in the wild, it would be worthwhile to leave support to install in MBR mode when doing an expert install so that people can still use them. Thoughts? Thanks,
Re: Simultaneous EFI and Legacy bootloader installation
On 03/29/2016 07:50 PM, Limonciello, Mario wrote: > Hi, > > I was briefly discussing this with Steve McIntyre and wanted to bring it to a > wider discussion. Currently users need to make a selection at installation > time whether to install in UEFI mode or in Legacy mode. If they installed in > legacy mode and later discovered that their system supported extra features > in UEFI mode (For example firmware updates) they are penalized and need to > redo the installation in order to switch modes. > > I'd like to propose changing this and by default install both legacy and UEFI > bootloaders on architectures that support both regardless of which mode the > system is running in at installation. Making this change has a few obvious > implications: > * The installation disk would always be formatted GPT. > * An ESP would always be created. > * If the user is in legacy at installation time, it's not possible to create > an EFI boot entry since EFI runtime services aren't present. The removable > media fallback path (\efi\boot\boot$ARCH.efi) will need to be used to boot > the system at this point and at some point create a "debian" NVRAM boot entry > > I'm not aware of any modern systems that are unable to boot a GPT partitioned > disk. If there are systems like this in the wild, it would be worthwhile to > leave support to install in MBR mode when doing an expert install so that > people can still use them. > > Thoughts? > > Thanks, Add debian-efi mailing list as well for awareness and to include in discussion.
RE: Simultaneous EFI and Legacy bootloader installation
My only hesitation is that hybrid boot has never been anything more than a hack, but that's vastly outweighed by the fact that it's so pervasive. -Original Message- From: Limonciello, Mario Sent: Tuesday, March 29, 2016 08:04 PM Central Standard Time To: pkg-grub-de...@lists.alioth.debian.org; debian-boot@lists.debian.org; Debian UEFI List Subject: Re: Simultaneous EFI and Legacy bootloader installation On 03/29/2016 07:50 PM, Limonciello, Mario wrote: > Hi, > > I was briefly discussing this with Steve McIntyre and wanted to bring it to a > wider discussion. Currently users need to make a selection at installation > time whether to install in UEFI mode or in Legacy mode. If they installed in > legacy mode and later discovered that their system supported extra features > in UEFI mode (For example firmware updates) they are penalized and need to > redo the installation in order to switch modes. > > I'd like to propose changing this and by default install both legacy and UEFI > bootloaders on architectures that support both regardless of which mode the > system is running in at installation. Making this change has a few obvious > implications: > * The installation disk would always be formatted GPT. > * An ESP would always be created. > * If the user is in legacy at installation time, it's not possible to create > an EFI boot entry since EFI runtime services aren't present. The removable > media fallback path (\efi\boot\boot$ARCH.efi) will need to be used to boot > the system at this point and at some point create a "debian" NVRAM boot entry > > I'm not aware of any modern systems that are unable to boot a GPT partitioned > disk. If there are systems like this in the wild, it would be worthwhile to > leave support to install in MBR mode when doing an expert install so that > people can still use them. > > Thoughts? > > Thanks, Add debian-efi mailing list as well for awareness and to include in discussion.
Re: Simultaneous EFI and Legacy bootloader installation
Hi On 2016-03-29, Mario Limonciello wrote: > On 03/29/2016 07:50 PM, Limonciello, Mario wrote: [...] > > I'd like to propose changing this and by default install both legacy > > and UEFI bootloaders on architectures that support both regardless of > > which mode the system is running in at installation. Making this > > change has a few obvious implications: > > * The installation disk would always be formatted GPT. > > * An ESP would always be created. > > * If the user is in legacy at installation time, it's not possible to > > create an EFI boot entry since EFI runtime services aren't present. > > The removable media fallback path (\efi\boot\boot$ARCH.efi) will need > > to be used to boot the system at this point and at some point create > > a "debian" NVRAM boot entry > > > > I'm not aware of any modern systems that are unable to boot a GPT > > partitioned disk. If there are systems like this in the wild, it > > would be worthwhile to leave support to install in MBR mode when > > doing an expert install so that people can still use them. [...] At least well into 2009/ 2010 era systems (most of those are early UEFI based underneath, but only expose a mandatory BIOS CSM to the user), you can sometimes find mainboards which refuse booting from a disk that doesn't have a MBR partition with the bootflag set. On these systems it is often possible to trick them into booting by setting the bootflag on the protective MBR around the GPT partitions, although this is a blatant violation of the UEFI specification (and might break more modern systems). Of course, most of the affected systems won't be detected as UEFI capable in the first place (because they will only allow booting via the BIOS CSM), but it's still something to be aware of. I'd very much appreciate BIOS and UEFI variants of grub to be co-installable (including their maintainer script orchestration), also to make moving installed systems between different mainboards easier (I am using a custom /etc/grub.d/ hook using grub-pc and grub-efi-amd64-bin for semi-portable installations on USB sticks myself, usually without any particular problems besides the one mentioned above). Regards Stefan Lippers-Hollmann pgpWPZ_Z6aH6l.pgp Description: Digitale Signatur von OpenPGP
