Bug#960626: Solution

2020-05-17 Thread cyrille 
Hi,

 

I've received help from some nice guy on #debian-boot

 

The problem is in all likelihood linked to this strange partition layout
shown by parted.

 

Anyway, here's the trick I used to solve my issue:

 

1- format my USB stick using a GPT partition table

2- create a single vfat partition of type ef00 spanning the whole USB stick
(I've used gdisk to be able to set the partition's type)

3- mount the partition

4- mount the debian iso

5- copy all files from the debian iso to the partition (taking care to also
copy the ".disk" folder), while ignoring the several warnings that some
symbolic links can't be copied 

6- unmount the partition

7- use the USB disk to install debian on my new hp laptop

 

That's it.

 

So, my issue is solved: You may do wathever you like with this bug report
now.

 

Thanks to the folks on #debian-boot for the assistance.

 

Cyrille

Bug#939862: installation-guide-amd64: "Windows 8 fast boot" is now "Windows 10 fast startup"

2020-05-17 Thread Holger Wansing 
Control: tags -1 + pending


Lou Poppler  wrote:
> Package: installation-guide-amd64
> Severity: minor
> Tags: d-i
> 
> Dear Maintainer,
> 
> Buster installation guide section 3.6.4. documents the dangers of the Windows 
> 8
> "fast boot" feature.  Most users now have Windows 10, where this feature is
> renamed "fast startup".  I suggest this section (and its title) should mention
> both Windows versions, and both feature names.
> 
> I suggest also adding additional text something like: "Sometimes the Windows
> Update mechanism has been known to automatically re-enable this feature, after
> it has been previously disabled by the user.  It is suggested to re-check this
> setting periodically."

Fixed in git. Thanks

Tagging this bug as pending


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Processed: Re: Bug#939862: installation-guide-amd64: "Windows 8 fast boot" is now "Windows 10 fast startup"

2020-05-17 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 + pending
Bug #939862 [installation-guide-amd64] installation-guide-amd64: "Windows 8 
fast boot"  is now "Windows 10 fast startup"
Added tag(s) pending.

-- 
939862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: Bug#459357: installation-guide-i386: 8.6.1. Kernel Image Management -- too few prerquisits

2020-05-17 Thread Holger Wansing 


Michael Junker  wrote:
> The statement
>  To compile a kernel the Debian way, you need some packages: fakeroot, 
>  kernel-package, linux-source-2.6 and a few others which are probably 
>  already installed (see /usr/share/doc/kernel-package/README.gz for 
>  the complete list).
> 
> appeared to me quite a bit misleading. I had to install quite more 

This content is no longer in the installation-guide, instead we just link
to the Debian Linux Kernel Handbook under
https://kernel-team.pages.debian.net/kernel-handbook/

Closing this bug

Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#459357: marked as done (installation-guide-i386: 8.6.1. Kernel Image Management -- too few prerquisits)

2020-05-17 Thread Debian Bug Tracking System 
Your message dated Sun, 17 May 2020 12:40:02 +0200
with message-id <20200517124002.a521cc67d59b5ece641fc...@mailbox.org>
and subject line Re: Bug#459357: installation-guide-i386: 8.6.1. Kernel Image 
Management -- too few prerquisits
has caused the Debian Bug report #459357,
regarding installation-guide-i386: 8.6.1. Kernel Image Management -- too few 
prerquisits
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
459357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-guide-i386
Version: 20070319
Severity: normal

The statement
 To compile a kernel the Debian way, you need some packages: fakeroot, 
 kernel-package, linux-source-2.6 and a few others which are probably 
 already installed (see /usr/share/doc/kernel-package/README.gz for 
 the complete list).

appeared to me quite a bit misleading. I had to install quite more 
packages. The documentation in 
/usr/share/kernel-package/doc/README mentions gcc, libc6-dev, bin86, 
ncursesX.X-dev, libqt3-mt-dev, g++, libglade2-dev, binutils, make, 
module-init-tools, awk, gzip, shellutils, grep. Most of them have not 
been installed already.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

-- no debconf information


--- End Message ---
--- Begin Message ---

Michael Junker  wrote:
> The statement
>  To compile a kernel the Debian way, you need some packages: fakeroot, 
>  kernel-package, linux-source-2.6 and a few others which are probably 
>  already installed (see /usr/share/doc/kernel-package/README.gz for 
>  the complete list).
> 
> appeared to me quite a bit misleading. I had to install quite more 

This content is no longer in the installation-guide, instead we just link
to the Debian Linux Kernel Handbook under
https://kernel-team.pages.debian.net/kernel-handbook/

Closing this bug

Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

[installation-guide] Closing powerpc bugreports

2020-05-17 Thread Holger Wansing 


Closing bugs which are no longer relevant because content is no longer existing
in the installation-guide (due to no longer supported powerpc archs/machines):

#233864 [powerpc] document need for BootX on oldworld
#273994 provide download-url for MacOS 7.5 as bootloader on oldworld
#717657 Bug#717511: installation-guide-powerpc: describe boot partiton layout 
constraints for Pegasos machines


Also closing this one:
#515249 installation-reports: Various issues on IBM Power5 (lvm, multipath, 
yaboot.conf)
because it's a left-over clone from #537590.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#515249: marked as done (installation-reports: Various issues on IBM Power5 (lvm, multipath, yaboot.conf))

2020-05-17 Thread Debian Bug Tracking System 
Your message dated Sun, 17 May 2020 14:13:23 +0200
with message-id <20200517141323.d26d6e23dd67379e768a4...@mailbox.org>
and subject line [installation-guide] Closing powerpc bugreports
has caused the Debian Bug report #515249,
regarding installation-reports: Various issues on IBM Power5 (lvm, multipath, 
yaboot.conf)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
515249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: grave
Justification: renders package unusable



-- Package-specific info:

Boot method: Network boot using a TFTP server
Image version: 
ftp://ftp.debian.org/debian/dists/sid/main/installer-powerpc/current/images/powerpc64/netboot/vmlinuz-chrp.initrd
 ** see note below
Date: Sat Feb 14 21:00:00 GMT 2009

Machine: IBM,9117-570 (pSeries)
Partitions:

Machine: IBM,9117-570 (pSeries)
Partitions:

* sfdisk -d /dev/mapper/mpath0

# partition table of /dev/mapper/mpath0
unit: sectors

/dev/mapper/mpath0p1 : start=   63, size=16002, Id=41, bootable
/dev/mapper/mpath0p2 : start=16065, size=   498015, Id=83
/dev/mapper/mpath0p3 : start=   514080, size= 66589425, Id=8e
/dev/mapper/mpath0p4 : start=0, size=0, Id= 0



Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [E]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [O]
Detect hard drives: [E]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [ ]
Install boot loader:[O]
Overall install:[E]

Comments/Problems:

Initial boot: Maybe not soe much an error, I had to specify the
  console at the boot prompt "console=hvc0,38400"

Detect had drives: During an attempt to reinstall after a failed
   install, I had to drop to a shell and remove
   any existing logical volumes before the
   disk detection process was able to detect
   the hard drive. Otherwise, it simply told
   me that there were not hard drives...

Overall install:

* Although the URL above is for the SID installer, when the
install was complete, I noticed that LENNY had been installed.
I noticed this by looking at the /etc/apt/sources.list file.

Other issues that I was not particularly happy with were:

1.
Selecting guided LVM allowed a the root filesystem to be
placed in a logical volume (which I wanted), but then the
yaboot.conf file was still writted to /etc/yaboot.conf.
I had to manually rescue the system after the install and
move /etc/yaboot.conf to /boot/etc/yaboot.conf. In my view
LVM is going to be the way forward and this configuration
file should not been located on the root filesystem. I
hope everyone is aware of this issue and has looked at
keeping files required to boot the system in /boot

2.
After fixing the location of the yaboot.conf file, the
system refused to boot. It was trying to boot the label
"old" which was invalid because the kernel has not yet
been upgraded. I therefore had to add the following to
the yaboot.conf before the correct default entry would
boot:

defaultos=Linux


3.
I also had issues with multipath root and LVM:

3.1
I had to add multipath to the lvm2 PREREQ's in order
for multipath to be started before LVM.

3.2
Debian installer was called with:

disk-detect/multipath/enable=true

However, once the install had completed, the lvm.conf
was not configured to filter out the underlying SCSI
devices. I had to add the following filter:

filter = [ "r/disk/", "r/sd.*/", "a/.*/" ]


After rebuilding the initramfs (above two changes
commited), it all worked quite nicely ;)



-- 

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="5.0 (lenny) - installer build 20090123"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
umame -a: Linux rootvg 2.6.26-1-powerpc64 #1 SMP Sat Jan 10 14:42:07

Bug#377017: marked as done (please include the bits from this wikipage in the manual)

2020-05-17 Thread Debian Bug Tracking System 
Your message dated Sun, 17 May 2020 14:13:23 +0200
with message-id <20200517141323.d26d6e23dd67379e768a4...@mailbox.org>
and subject line [installation-guide] Closing powerpc bugreports
has caused the Debian Bug report #233864,
regarding please include the bits from this wikipage in the manual
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
233864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=233864
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: debian-installer-manual
severity: wishlist

Hi,

http://wiki.debian.org/DebianInstaller/PowerPC/OldWorld/PreAlphaManualUpdates 
should be reviewed and included in the documentation.


regards,
Holger


pgpYzhgdOVwoz.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---

Closing bugs which are no longer relevant because content is no longer existing
in the installation-guide (due to no longer supported powerpc archs/machines):

#233864 [powerpc] document need for BootX on oldworld
#273994 provide download-url for MacOS 7.5 as bootloader on oldworld
#717657 Bug#717511: installation-guide-powerpc: describe boot partiton layout 
constraints for Pegasos machines


Also closing this one:
#515249 installation-reports: Various issues on IBM Power5 (lvm, multipath, 
yaboot.conf)
because it's a left-over clone from #537590.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#273994: marked as done (provide download-url for MacOS 7.5 as bootloader on oldworld)

2020-05-17 Thread Debian Bug Tracking System 
Your message dated Sun, 17 May 2020 14:13:23 +0200
with message-id <20200517141323.d26d6e23dd67379e768a4...@mailbox.org>
and subject line [installation-guide] Closing powerpc bugreports
has caused the Debian Bug report #273994,
regarding provide download-url for MacOS 7.5 as bootloader on oldworld
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
273994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=273994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer-manual

This bugreport is a todo-item, it is filed to prevent getting lost.

On Tue, Sep 28, 2004 at 11:46:29PM -0400, Rick Thomas wrote:
> On Tuesday, September 28, 2004, at 07:19 PM, Holger Levsen wrote:
> 
> > Hi,
> >
> >> Remember that MacOS 7.5 doesn't work on all models of OldWorld Mac.
> >> Folks should check the matrix on this Apple web page:
> >>   
> >
> > Oh no! ;-) But maybe that's got information for the manual.
> >
> >> to see if their hardware can run MacOS 7.5, before they invest a 
> >> lot of
> >> effort in downloading 19 floppy image files and burning a bunch of
> >> floppies they can't use.
> >
> > Can you please provide the URL where the unlucky can download the 
> > floppy
> > images ?!
> > In my opinion this should be included in the manual as well.
> >
> 
> Glad to help!
> 
> http://download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/English-North_American/
> Macintosh/System/Older_System/System_7.5_Version_7.5.3/
> 
> Be careful of URL-wrap-syndrome!
> 
> Enjoy!
> 
> Rick


Cheers
Geert Stappers

--- End Message ---
--- Begin Message ---

Closing bugs which are no longer relevant because content is no longer existing
in the installation-guide (due to no longer supported powerpc archs/machines):

#233864 [powerpc] document need for BootX on oldworld
#273994 provide download-url for MacOS 7.5 as bootloader on oldworld
#717657 Bug#717511: installation-guide-powerpc: describe boot partiton layout 
constraints for Pegasos machines


Also closing this one:
#515249 installation-reports: Various issues on IBM Power5 (lvm, multipath, 
yaboot.conf)
because it's a left-over clone from #537590.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#717657: marked as done (Bug#717511: installation-guide-powerpc: describe boot partiton layout constraints for Pegasos machines)

2020-05-17 Thread Debian Bug Tracking System 
Your message dated Sun, 17 May 2020 14:13:23 +0200
with message-id <20200517141323.d26d6e23dd67379e768a4...@mailbox.org>
and subject line [installation-guide] Closing powerpc bugreports
has caused the Debian Bug report #717657,
regarding Bug#717511: installation-guide-powerpc: describe boot partiton layout 
constraints for Pegasos machines
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
717657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-3.2.0-4-powerpc
Version: 3.2.46-1

 Hello!
 I  have  just upgraded Linux installation on my Pegasos-II machine to
Debian  7.1.0  Wheezy.  The installer worked flawlessly, but the newly
installed  kernel  refused  to  boot up. Attempt to boot up the kernel
ends  up  in  a  text-mode  screen  filled  up  with  garbage  (randon
characters and attributes).
 What's up ? Did you drop Pegasos support ?

-- 
С уважением,
 Pavel  mailto:pavel_fe...@mail.ru
--- End Message ---
--- Begin Message ---

Closing bugs which are no longer relevant because content is no longer existing
in the installation-guide (due to no longer supported powerpc archs/machines):

#233864 [powerpc] document need for BootX on oldworld
#273994 provide download-url for MacOS 7.5 as bootloader on oldworld
#717657 Bug#717511: installation-guide-powerpc: describe boot partiton layout 
constraints for Pegasos machines


Also closing this one:
#515249 installation-reports: Various issues on IBM Power5 (lvm, multipath, 
yaboot.conf)
because it's a left-over clone from #537590.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#233864: marked as done ([powerpc] document need for BootX on oldworld)

2020-05-17 Thread Debian Bug Tracking System 
Your message dated Sun, 17 May 2020 14:13:23 +0200
with message-id <20200517141323.d26d6e23dd67379e768a4...@mailbox.org>
and subject line [installation-guide] Closing powerpc bugreports
has caused the Debian Bug report #233864,
regarding [powerpc] document need for BootX on oldworld
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
233864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=233864
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Debian-installer-version: netinst cd from http://people.debian.org/cdimage/
testing/daily/powerpc/20040219/
uname -a: Linux (none) 2.4.22-powerpc #1 Mon Feb 2 14:15:53 CET 2004 ppc 
unknown
Date: 2004-02-20 12:00
Method: that's an oldworld machine, so: copied vmlinux in "/Dossier système/
Linux kernels" and root.bin in "/Dossier système/". I've booted the 
installation with BootX (args: "video=atyfb:vmode:14,cmode:32 devfs=mount 
DEBCONF_PRIORITY=medium" and "high".

Machine: Apple Powerbook Wallstreet II ('98) M4753
Processor: Sonnet G3@500 update processor card (replacing a 266MHz G3)
Memory: 192Mb
Root Device: ide, /dev/hda9
Root Size/partition table: just using /dev/hda9 and /dev/hda10 for swap (for 
now)
Output of lspci:

Base System Installation Checklist:

Initial boot worked:[ E]
Configure network HW:   [ O]
Config network: [ O]
Detect CD:  [ O]
Load installer modules: [ O]
Detect hard drives: [ O]
Partition hard drives:  [ O]
Create file systems:[ O]
Mount partitions:   [O ]
Install base system:[ E]
Install boot loader:[ ]
Reboot: [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:

Initial boot: doesn't work on oldworld PPC. BootX works. Yeah, it's a known 
problem. What about providing BootX in the cdrom and adding this hint to 
debian-installer documentation?

kbd-chooser: crashes with "Configuring 'kbd-chooser' failed with error 139" on 
tty4
Tried it with en_US and fr_FR

After a little fiddling, it appears to be a kernel/ramdisk image problem.
If I use the kernel from 20040219 netinst with 20040218 netinst cdrom, it 
crashes.
If I use the kernel from 20040218 netinst with 20040219 netinst cdrom, it 
works.

At the end of the base system installation, the installer fails with an error 
127. In /var/log/messages:
dpkg:error processing man-db (--configure):
  subprocess post-installation script returned error exit status 1
(...)
Errors were encountered while processing:
 man-db
/usr/sbin/debootstrap: 1: sleep: not found

the "sleep not found" error might not be related...

--- End Message ---
--- Begin Message ---

Closing bugs which are no longer relevant because content is no longer existing
in the installation-guide (due to no longer supported powerpc archs/machines):

#233864 [powerpc] document need for BootX on oldworld
#273994 provide download-url for MacOS 7.5 as bootloader on oldworld
#717657 Bug#717511: installation-guide-powerpc: describe boot partiton layout 
constraints for Pegasos machines


Also closing this one:
#515249 installation-reports: Various issues on IBM Power5 (lvm, multipath, 
yaboot.conf)
because it's a left-over clone from #537590.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#903393: [initramfs-tools] update-initramfs -u warns: Unknown X keysym "dead_belowmacron"

2020-05-17 Thread bakhelit 

Dear Maintainer,

On Debian 9 (with console-setup 1.164) running "sudo update-initramfs 
-u" produces:

update-initramfs: Generating /boot/initrd.img-4.9.0-12-amd64
WARNING: Unknown X keysym "dead_belowbreve"
WARNING: Unknown X keysym "dead_belowbreve"
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowring"
WARNING: Unknown X keysym "dead_belowring"
WARNING: Unknown X keysym "dead_belowcircumflex"
WARNING: Unknown X keysym "dead_belowcircumflex"
WARNING: Unknown X keysym "dead_greek"
WARNING: Unknown X keysym "dead_greek"
WARNING: Unknown X keysym "dead_greek"
WARNING: Unknown X keysym "dead_greek"
WARNING: Unknown X keysym "dead_belowdiaeresis"
WARNING: Unknown X keysym "dead_belowdiaeresis"
WARNING: Unknown X keysym "dead_belowtilde"
WARNING: Unknown X keysym "dead_belowtilde"
WARNING: Unknown X keysym "dead_belowtilde"
WARNING: Unknown X keysym "dead_belowtilde"

On Debian 10 (with console-setup 1.193~deb10u1) running "sudo 
update-initramfs -u" produces:

update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64

This is with my custom XKB keyboard layout where I included the quite a 
few "dead_*" X keysyms.


The problem is indeed caused by the Perl script "/usr/bin/ckbcomp" because:

- The script does not support all X keysyms.

- Despite not supporting all X keysyms the supported X keysyms are used 
as if the remaining unknown X keysyms are potentially invaild X keysyms.


- On Debian 9 the "/usr/share/initramfs-tools/hooks/keymap" script calls 
"/bin/setupcon" via "setupcon --save-keyboard ..." which causes it to 
call "/usr/bin/ckbcomp".


- On Debian 10 the "/usr/share/initramfs-tools/hooks/keymap" script 
calls "/bin/setupcon" via "setupcon --setup-dir ..." which causes it to 
not call "/usr/bin/ckbcomp".


Perhaps the Perl script "/usr/bin/ckbcomp" should be updated to support 
all X keysyms or the current supported X keysyms should be used as just 
an incomplete whitelist, where the remaining unknown X keysyms are also 
potentially vaild keysyms. In other words an info or warning about 
unsupported X keysym could be printed only in verbose or debug mode or 
not at all.


Regards,
Bakhelit

Bug#924290: [rfc] information about EFI partitions

2020-05-17 Thread Holger Wansing 
Hi,

 wrote:
> Package: installation-guide
> Version: 20180930
> Severity: wishlist
> Tags: patch
> 
> Hi
> 
> recently I was learning about presseding UEFI installs and
> I think the install guide could use a small addition to make
> that journey easier. I also sent a patch to partman-auto-recipe.txt
> but I am sure the readership of that is much less than the d-i manual.

I am unable to proof the patch correct or not, could anyone comment on that?



>From 4697c54b3f61bc145980f52206bb20e2280c0a63 Mon Sep 17 00:00:00 2001
From: Vincent McIntyre 
Date: Mon, 11 Mar 2019 15:38:19 +1100
Subject: [RFC PATCH] Add some information about preseeding EFI partitions

---
 en/appendix/preseed.xml | 17 +
 1 file changed, 17 insertions(+)

diff --git a/en/appendix/preseed.xml b/en/appendix/preseed.xml
index c55860e34..9e334738a 100644
--- a/en/appendix/preseed.xml
+++ b/en/appendix/preseed.xml
@@ -1211,6 +1211,20 @@ d-i partman-auto/choose_recipe select atomic
 # system labels, volume group names and which physical devices to include
 # in a volume group.
 
+## Partitioning for EFI
+# If your system needs an EFI partition you could add something like
+# this to the recipe above, as the first element in the recipe:
+#   538 538 1075 free  \
+#  $iflabel{ gpt } \
+#  $reusemethod{ } \
+#  method{ efi }   \
+#  format{ }   \
+#   .  \
+#
+# The fragment above is for the amd64 architecture; the details may be
+# different on other architectures. The 'partman-auto' package in the
+# D-I source repository may have an example you can follow.
+
 # This makes partman automatically partition without confirmation, provided
 # that you told it what to do using one of the methods above.
 d-i partman-partitioning/confirm_write_new_label boolean true
@@ -1218,6 +1232,9 @@ d-i partman/choose_partition select finish
 d-i partman/confirm boolean true
 d-i partman/confirm_nooverwrite boolean true
 
+# Force UEFI booting ('BIOS compatibility' will be lost). Default: false.
+#d-i partman-efi/non_efi_system boolean true
+
 # When disk encryption is enabled, skip wiping the partitions beforehand.
 #d-i partman-auto-crypto/erase_disks boolean false
 
-- 
2.11.0



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#233864: marked as done ([powerpc] document need for BootX on oldworld)

2020-05-17 Thread John Paul Adrian Glaubitz 
On 5/17/20 2:15 PM, Debian Bug Tracking System wrote:
> Initial boot: doesn't work on oldworld PPC. BootX works. Yeah, it's a known 
> problem. What about providing BootX in the cdrom and adding this hint to 
> debian-installer documentation?

That's actually a good point. I can look adding OldWorld support in the
future provided that booting on OldWorld machines currently works.

I remember there being issues, in particular with PowerBook 34xx machines.

BootX might also help with the NewWorld machines that have early OpenFirmware
implementations that are not properly supported by GRUB.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#515249: marked as done (installation-reports: Various issues on IBM Power5 (lvm, multipath, yaboot.conf))

2020-05-17 Thread John Paul Adrian Glaubitz 
Hello Holger!

Closing the bug report in this case is okay, but the actual reason why
this can be closed is that I have switched the powerpc and ppc64 ports
over from Yaboot to GRUB meaning that Yaboot-specific installation issues
should no longer be relevant.

Thanks,
Adrian

On 5/17/20 2:15 PM, Debian Bug Tracking System wrote:
> Base System Installation Checklist:
> * Although the URL above is for the SID installer, when the
> install was complete, I noticed that LENNY had been installed.
> I noticed this by looking at the /etc/apt/sources.list file.
> 
> Other issues that I was not particularly happy with were:
> 
> 1.
> Selecting guided LVM allowed a the root filesystem to be
> placed in a logical volume (which I wanted), but then the
> yaboot.conf file was still writted to /etc/yaboot.conf.
> I had to manually rescue the system after the install and
> move /etc/yaboot.conf to /boot/etc/yaboot.conf. In my view
> LVM is going to be the way forward and this configuration
> file should not been located on the root filesystem. I
> hope everyone is aware of this issue and has looked at
> keeping files required to boot the system in /boot
> 
> 2.
> After fixing the location of the yaboot.conf file, the
> system refused to boot. It was trying to boot the label
> "old" which was invalid because the kernel has not yet
> been upgraded. I therefore had to add the following to
> the yaboot.conf before the correct default entry would
> boot:
> 
> defaultos=Linux
> 
> 
> 3.
> I also had issues with multipath root and LVM:
> 
> 3.1
> I had to add multipath to the lvm2 PREREQ's in order
> for multipath to be started before LVM.
> 
> 3.2
> Debian installer was called with:
> 
> disk-detect/multipath/enable=true
> 
> However, once the install had completed, the lvm.conf
> was not configured to filter out the underlying SCSI
> devices. I had to add the following filter:
> 
> filter = [ "r/disk/", "r/sd.*/", "a/.*/" ]
> 
> 
> After rebuilding the initramfs (above two changes
> commited), it all worked quite nicely ;)

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Emulate 'vga=none' by gfxpayload as kernel boot parameter

2020-05-17 Thread john doe 

On 5/15/2020 6:31 PM, john doe wrote:

Debians-boot,

I'm trying to troubleshoot what I'm doing rong when trying to install
Debian through serial console.

If I start a Qemu VM like so:

qemu-system-x86_64 -cdrom debian-bullseye-DI-alpha2-amd64-netinst.iso
-nographic -vga none -m 1024

At the Debian install prompt pressing the escape key get me to the boot
prompt.

boot: install console=ttyS0,115200n8 DEBIAN_FRONTEND=text gfxpayload=text
Undefined video mode number: 314
Press  to see video modes available,  to continue, or wait
30 sec


If I use 'vga=none' the above is suppressed but Debian will not start
properly after installation by saying that 'vga=none' is deprecated and
that 'set gfxpayload=text' should be used instead.

How can I specify 'set gfxpayload=text' to the boot prompt above?

In other words, how can i emulate 'vga=none' when this argument is
deprecated.

This issue originated from a host on which I'm facing this issue and
reproduced here for testing purposes with Qemu.



Does anyone has any feedback on this, is this a kernel issue, a grub issue?

I'm not sure which package I should file a bug against?

--
John Doe