Bug#489006: have /boot on md0 (dm-raid1), but install grub to MBRs of both disks?
Well, Subject basically says what I try: I want to have /boot on /dev/md0 (raid1, sda1+sdb1) / on /dev/md1 (also raid1, sda5/sdb5 swap, non-critical data on lvm on /dev/md2 (raid0, sda6/sdb6) The Debian installer easily lets me create such a layout, even using preseeding. However, grub (both legacy and grub2) fail to generate a device mapping for md0, thus being unable to install grub. In my opinion such a partition layout should either be impossible to create with d-i (or at least generate a warning) or grub-pc should support this setup. Especially since this sort of partitioning is an example in the partman-raid (or was it partman-lvm?) documentation. Not exactly the way I described it, but with /root on lvm on raid. Regards, Sven -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bc1a07e.4000...@incase.de
Re: 5.0.4-i386 freezes at boot
On Sun, 2010-04-11 at 14:04 +0300, Sakari Aaltonen wrote: Quoting Ben Hutchings b...@decadent.org.uk: Please try to install the 'testing' suite (work in progress for Debian 6.0 'squeeze') using the installer from http://www.debian.org/devel/debian-installer/. This will install a newer kernel version (2.6.32) which might include a fix for this bug. Even if you are sure you want to use Debian 5.0 'lenny', this will at least tell us whether a bug fix exists. Here are the results from my attempt to install *netinst testing squeeze Alpha 1*. Without 'noapic', the newer install did not stop at the MP-BIOS bug error message, but did advance to the language selection screen. But it was impossible to select the language, as the keyboard did not work. This is obviously a kernel bug, but may be fixed now (the installer currently runs on Linux 2.6.30 but installs 2.6.32). With 'noapic', the install proceeded to completion. However, the language/locale selection was strange in that if I selected English as the language, I was only able to select the locale from a list of English-language countries. This does not make sense. I could very well be a native speaker of English residing in a non-English-language locale. You may need to use 'expert' mode to make that choice. However I believe there have been some later changes to locale selection to make it more flexible. Or, I could simply prefer to use English at the installation stage - if there is a problem in the screen Tee pakettienhallintajärjestelmän asetukset, say, then how do I file a bug report if I don't know how that phrase was written, originally, in English? The installer finds the Fedora 12 that I installed earlier and promises that that OS will be bootable in addition to the Debian one. However, when I next restart the machine, the GRUB menu does *not* have an entry for Fedora. There are only Debian entries - 4 of them, in fact. OK, I select the top entry. But... I cannot log in, as the Welcome screen does not accept me either as a normal user or as root. I have now done the installation - all of it - twice, to make sure I did input the password(s) correctly. But, well, no luck. I'm wondering whether the keyboard is still broken here. Did you type the username in or did you select it with the mouse? Or were you forced to select the wrong keymap for your keyboard because of the restrictions in the installer? I will note that I have, successively, installed OpenSUSE 11.2, Ubuntu 9.10 and Fedora 12 on this machine. They did have problems, yes, but I could still log in. Also, the Debian install seems to have made the Fedora 12 installation unbootable. A pity, as it was working pretty well this morning. Sorry about that; maybe the installer developers (debian-boot list) can help you to debug and fix this. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Re: 5.0.4-i386 freezes at boot
Quoting Ben Hutchings b...@decadent.org.uk: I'm wondering whether the keyboard is still broken here. Did you type the username in or did you select it with the mouse? Or were you forced to select the wrong keymap for your keyboard because of the restrictions in the installer? I typed in the usernames, both 'root' and my own. They appeared correctly on-screen, so I would assume the passwords that I typed in were correct, too. But the installed system just did not accept them. I will note that I have, successively, installed OpenSUSE 11.2, Ubuntu 9.10 and Fedora 12 on this machine. They did have problems, yes, but I could still log in. Also, the Debian install seems to have made the Fedora 12 installation unbootable. A pity, as it was working pretty well this morning. Sorry about that; maybe the installer developers (debian-boot list) can help you to debug and fix this. It's OK; I found instructions at http://fedoraforum.org/forum/showthread.php?t=975 on what to do to make the Fedora 12 installation bootable again. It's odd how the Debian installer (correctly) claims to have identified the F12 (on a different partition), but then does not list it in the boot menu. Sakari Aaltonen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100411194831.6l5azzmyo0gwc...@webmail1.tkk.fi
Bug#577451: hw-detect: Should automatically install hardware related packages (RAID tools, printer drivers, fingerprint scanner tools, etc)
Package: hw-detect Version: 1.50 Tags:patch For some kind of hardware, it would be very nice if the Debian installer automatically installed the packages to support the hardware in question. An example is the RAID monitoring and administration tools needed to check and configure a hardware RAID (like cpqarrayd and mpt-status). Another is a TV card which might need V4L(2) tools to configure it. In Debian, the discover tool is capable of handling this for USB and PCI devices at the moment. I've written a wrapper script discover-pkginstall to provide hw-detect with a simple way to get these hardware specific packages installed by the installer. The feature have been on my todo list for a long time, so I report this against an old hw-detect version to document this. :) To make the feature really useful, the database with hardware to package mappings in discover-data need to be updated to list all the packages that should be installed when a given PCI or USB device is discovered. At the moment there are 34 PCI and 48 USB devices with package mappings in the database, but I am sure there are more hardware we should handle out there. This untested patch relative to the current svn source should implement this feature: Index: hw-detect.post-base-installer.d/60install-hwpackages === --- hw-detect.post-base-installer.d/60install-hwpackages(revision 0) +++ hw-detect.post-base-installer.d/60install-hwpackages(revision 0) @@ -0,0 +1,10 @@ +#!/bin/sh + +set -e + +. /usr/share/debconf/confmodule + +apt-install discover || true +if [ -x /target/sbin/discover-pkginstall ] ; then + in-target discover-pkginstall +fi I suspect it need more work to get the debconf stuff to work properly from within d-i. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2fl7hodrh1h@login2.uio.no
Bug#577451: hw-detect: Should automatically install hardware related packages (RAID tools, printer drivers, fingerprint scanner tools, etc)
Petter Reinholdtsen wrote: +apt-install discover || true +if [ -x /target/sbin/discover-pkginstall ] ; then + in-target discover-pkginstall +fi I suspect it need more work to get the debconf stuff to work properly from within d-i. debconf passthrough should work with in-target used like that. But, discover-pkginstall needs to use the debconf-apt-progress command when it runs aptitude to install packages. -- see shy jo signature.asc Description: Digital signature
Bug#577461: installation-guide: Updates to textmode activation
Package: installation-guide Version: 20090901 Severity: normal Tags: patch Hello, Squeeze apparently needs vga=0 in addition to fb=false, else the kernel switches to graphical mode very early. This needs to be documented in the accessibility section, here is a patch, which also mentions how useful it can be for qemu. Samuel -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.33 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Samuel Thibault samuel.thiba...@fnac.net Pour un p�re, autant mourir que de faire plein de calculs et pas s'occuper de son fils -+- y sur #ens-mim - sombres histoires de zombies -+- Index: en/boot-installer/accessibility.xml === --- en/boot-installer/accessibility.xml (révision 60852) +++ en/boot-installer/accessibility.xml (copie de travail) @@ -81,14 +81,15 @@ /para /sect2 - sect2titleBoard Devices/title + sect2titleBoard Devices and virtualization/title para Some accessibility devices are actual boards that are plugged inside the -machine and that read text directly from the video memory. To get them -to work framebuffer support must be disabled by using the -userinputfb=false/userinput boot parameter. This will however reduce -the number of available languages. +machine and that read text directly from the video memory. Also, some +virtualization tools have a textual interface (e.g. userinputqemu +-curses/userinput). To get them to work framebuffer support must be disabled +by using the userinputvga=0 fb=false/userinput boot parameter. This will +however reduce the number of available languages. /para /sect2
Bug#505564: marked as done (Please document the braille support)
Your message dated Sun, 11 Apr 2010 22:56:36 +0200 with message-id 20100411205635.ga21...@const.famille.thibault.fr and subject line Re: Bug#505564: Please document the braille support has caused the Debian Bug report #505564, regarding Please document the braille support 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.) -- 505564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505564 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-guide Severity: wishlist Hello Debian-Team, You can use the Debian Installer very good with a braille display. Please document how to install Lenny with a braille display. http://svn.debian.org/viewsvn/ddp/manuals/branches/release-notes/lenny/en/installing.dbk?logsort=daterev=5413view=markup Thank you very much in advance for the further documentation. Simon Bienlein ---End Message--- ---BeginMessage--- Version: 20090427 Hello, The documentation about accessibility had been added last year, before the Lenny release. Samuel ---End Message---
Re: Bug#577461: installation-guide: Updates to textmode activation
Samuel Thibault, le Sun 11 Apr 2010 22:58:39 +0200, a écrit : Squeeze apparently needs vga=0 in addition to fb=false, else the kernel switches to graphical mode very early. That being said, it could actually been considered as a regression, since fb=false used to be enough. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100411213011.gj4...@const.famille.thibault.fr
Debian installer shortcuts?
Hello, I'm having a look at the debian installer documentation atm, and I'd like to precisely document the various keypresses needed to enable the accessibility parts of the debian installer. I have no problem with finding out information on x86 as I have a lot of x86 boxes. I however do not have a powerpc, an itanium or an alpha box (these are the archs where brltty is enabled). Can anybody get me details? The list of what I'd need is the keypresses to - just boot (enter on x86), - get to appending boot parameters (tab, type, enter on x86) Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100411215155.gk4...@const.famille.thibault.fr
Bug#577461: installation-guide: Updates to textmode activation
Ah, sorry, I thought that what follows would have been independent from this bugreport but actually it's not. The help menu is in textmode and can be used to type boot parameters etc., so let's document that too. Samuel Index: en/boot-installer/accessibility.xml === --- en/boot-installer/accessibility.xml (révision 62894) +++ en/boot-installer/accessibility.xml (copie de travail) @@ -81,13 +81,24 @@ /para /sect2 - sect2titleBoard Devices/title + sect2titleBoard Devices and virtualization/title para Some accessibility devices are actual boards that are plugged inside the -machine and that read text directly from the video memory. To get them -to work framebuffer support must be disabled by using the -userinputfb=false/userinput boot parameter. This will however reduce +machine and that read text directly from the video memory. Also, some +virtualization tools have a textual interface (e.g. userinputqemu +-curses/userinput). + +/parapara + +For such case, a textual version of the bootloader can be activated by typing +userinputh/userinput enterkey; . This permits to easily append boot +parameters at will. + +/parapara + +The purely textual version of the installer must also be activated by using the +userinputvga=0 fb=false/userinput boot parameter. This will however reduce the number of available languages. /para
Bug#577451: hw-detect: Should automatically install hardware related packages (RAID tools, printer drivers, fingerprint scanner tools, etc)
reassign 577451 pkgsel severity 577451 wishlist thanks On Sunday 11 April 2010, Petter Reinholdtsen wrote: For some kind of hardware, it would be very nice if the Debian installer automatically installed the packages to support the hardware in question. IMO this belongs in pkgsel, not in hw-detect. It has nothing to do with hardware detection as used in D-I itself. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201004112355.58260.elen...@planet.nl
Processed: Re: Bug#577451: hw-detect: Should automatically install hardware related packages (RAID tools, printer drivers, fingerprint scanner tools, etc)
Processing commands for cont...@bugs.debian.org: reassign 577451 pkgsel Bug #577451 [hw-detect] hw-detect: Should automatically install hardware related packages (RAID tools, printer drivers, fingerprint scanner tools, etc) Bug reassigned from package 'hw-detect' to 'pkgsel'. Bug No longer marked as found in versions hw-detect/1.50. severity 577451 wishlist Bug #577451 [pkgsel] hw-detect: Should automatically install hardware related packages (RAID tools, printer drivers, fingerprint scanner tools, etc) Severity set to 'wishlist' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127102371023052.transcr...@bugs.debian.org
Processed: Re: Bug#577461: installation-guide: Updates to textmode activation
Processing commands for cont...@bugs.debian.org: tag 577461 pending Bug #577461 [installation-guide] installation-guide: Updates to textmode activation Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127102560632754.transcr...@bugs.debian.org
Bug#577461: installation-guide: Updates to textmode activation
tag 577461 pending thanks On Sunday 11 April 2010, Samuel Thibault wrote: Samuel Thibault, le Sun 11 Apr 2010 22:58:39 +0200, a écrit : Squeeze apparently needs vga=0 in addition to fb=false, else the kernel switches to graphical mode very early. That being said, it could actually been considered as a regression, since fb=false used to be enough. It's not a regression but a necessary change since we now use VESA framebuffer by default for all x86 installs in order to have a better display resolution. The fact that now two parameters are needed is the simple consequence of the fact that one is a kernel parameter (which *must* be passed at boot time) and one is a D-I parameter and the fact that the one does not automatically imply the other. I've applied a modified version of both your patches. I've left out the virtualization bits as I don't think they belong in a section about accessibility and disabling framebuffer in general is already also documented in the general boot parameters section. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201004120039.57664.elen...@planet.nl
Bug#577461: installation-guide: Updates to textmode activation
On Monday 12 April 2010, Frans Pop wrote: The fact that now two parameters are needed is the simple consequence of the fact that one is a kernel parameter (which *must* be passed at boot time) and one is a D-I parameter and the fact that the one does not automatically imply the other. Actually, *maybe* we could remove the need for fb=false for x86 if we dropped support for the vga16 framebuffer driver. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201004120124.46754.elen...@planet.nl
Re: Bug#577461: installation-guide: Updates to textmode activation
Frans Pop, le Mon 12 Apr 2010 00:39:57 +0200, a écrit : I've left out the virtualization bits as I don't think they belong in a section about accessibility and disabling framebuffer in general is already also documented in the general boot parameters section. That is true, but knowing that one can install a Debian virtual machine quite easily in textmode _is_ about accessibility. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100411234008.gt4...@const.famille.thibault.fr
[D-I Manual] Build log for en (11 Apr 2010) - ERRORS DURING BUILD
A build of the Debian Installer Manual was triggered by an update to SVN.
!!! There were errors during the build process.
!!! Please check the log and correct the errors.
Only architectures (if any) that were built correctly have been uploaded.
A log of the build is available at:
- http://d-i.alioth.debian.org/manual/logs/en.log
===
It is possible to use RSS to track changes to the manual.
For more information, see:
http://d-i.alioth.debian.org/manual/translators.html
===
Note: PDF output is not yet supported for some languages; help
with this would be appreciated.
===
If you have any questions about the build or this message, feel
free to contact me at faw AT funlabs DOT org.
===
Updated files ('svn up')
Uen/boot-installer/x86.xml
Uen/boot-installer/accessibility.xml
Uen/boot-installer/parameters.xml
Updated to revision 62897.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100412002956.ga20...@mustang.funlabs.org
