Bug#513283: debian-installer: "keymap select" is ignored when loading the preseeding file from kernel parameters

[Lasse Aagren]

On 20/02/2009, at 06.48, Christian Perrier wrote:


Quoting Lasse Aagren (aag...@dtic.dk):


Have you tried with "d-i console-keymaps-at/keymap select Danish"?



Now I have. And it seems still not to work. You can see a slightly
modified (anonymized) version of my preseed file here:


OK, that was a wild guess as console-data templates have changed
during etch->lenny

Another possibility is preseeding with "dk-latin1" which is indeed the
real name of the choice (the dk.kmap is a simple link to dk-latin1)


Bingo. dk-latin1 works. I should probably have thought about that. But  
dk worked with etch :-)


Thanks for the help.

Best regards,
--
Lasse Aagren
Technical Information Center of Denmark



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#516280: GRUB Installed on wrong device during Lenny Install

[Rob Fulton]

Package: debian-installer
Version: 20090123

When installing Lenny on a HP DL360 / DL380 server Grub is installed on 
the wrong device.


The server is booted from CD, during network detection, the bnx2 firmware 
is required. A USB key is inserted to provide the firmware. The disks are 
then partitioned and the install proceeds, grub is installed on the master 
boot record. On reboot with the USB stick still connected, GRUB loads and 
the os is booted from the internal disks. Without the USB drive, the OS 
refuses to boot.


The internal disks are presented as /dev/cciss/c0d0 devices, the USB drive 
is presented as /dev/sda.


Running grub-install to the /dev/cciss/c0d0 device after install resolves 
the problem but the installer appears to be picking the wrong device when 
grub is installed


Regards

Rob Fulton



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processing of rescue_1.20_i386.changes

[Archive Administrator]

rescue_1.20_i386.changes uploaded successfully to localhost
along with the files:
  rescue_1.20.dsc
  rescue_1.20.tar.gz
  rescue-check_1.20_all.udeb
  rescue-mode_1.20_all.udeb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#283318: marked as done (Installation results in an unbootable system)

[Debian Bug Tracking System]

Your message dated Fri, 20 Feb 2009 14:37:08 +0100
with message-id <20090220133708.gb30...@ibr.ch>
and subject line Re: Bug#283318: Installation results in an unbootable system
has caused the Debian Bug report #283318,
regarding Installation results in an unbootable system
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.)


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

Debian-installer-version: sarge-i386-1.iso, 15.11.2004, ftp.acc.umu.se
uname -a: Linux t1 2.4.27-1-386 #1 Fri Sep 3 06:24:46 UTC 2004 i686 unknown
Date: 20.11.2004
Method: Debian boot-CD, IDE drive

Machine: NoName-PC (board MS6119)
Processor: PII-233 MMX
Memory: 128 MB
Root Device: IDE (Seagate ST 34342A)
Root Size/partition table: 1: 4.1 GB root, 5: 200 MB swap, boot loader in MBR

Output of lspci and lspci -n:
:00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(rev 02)
:00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge 
(rev 02)
:00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
:00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
:00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
:00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
:00:0e.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL-8139/8139C/8139C+ (rev 10)
:01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G200 AGP (rev 
01)

:00:00.0 0600: 8086:7190 (rev 02)
:00:01.0 0604: 8086:7191 (rev 02)
:00:07.0 0601: 8086:7110 (rev 02)
:00:07.1 0101: 8086:7111 (rev 01)
:00:07.2 0c03: 8086:7112 (rev 01)
:00:07.3 0680: 8086:7113 (rev 02)
:00:0e.0 0200: 10ec:8139 (rev 10)
:01:00.0 0300: 102b:0521 (rev 01)

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

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O] (manually)
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:[O]
Install boot loader:[O]
Reboot: [E]

Comments/Problems:

GRUB loading stage 1.5.
GRUB loading, please wait...
Error 18

That's all what I get after reboot.

I'm not familiar with grub, but error 18 indicates a problem with the
disk geometry. And indeed after the reboot the BIOS recognizes a wrong
disk geometry (495 MB instead of the original 4.3 GB).
I have retried the installation, even with another board
(MS6140 / Celeron 300A), but I always get the same result.
I had to overwrite the disk (with dd) to get the original disk geometry
back (displayed in the BIOS).

Today I have checked installation from the updated sarge-i386-1.iso
image from 22.11.2004, same result. Installing woody and upgrading it
to sarge works fine on the same system now.


As this is my first try with the new installer a few additional
comments:

- It would be nice to have a rescue boot mode as with the woody disks.

- The network config happily ignores a missing dhcp server:
  "The network autoconfiguration was successful." ... but nothing was
  configured!
  It should switch to manual configuration mode instead or at least give
  an adequate error message.

- The meaning of the symbols in the disk partition screen should be
  explained (smiley, skull, bolt, ..) or better be replaced by self
  explaining text.

- There are often empty "blue screens" for a more or less lasting time
  during the installation (e.g. between partitioning and installing
  the base system).
  This may not be a problem on a fast machine. But on a slower machine
  this may give the impression of a crashed installation, especially
  for windows users.
  If the system has to do something there should be a message or a
  progress bar on the screen, but not an empty screen.

Regards,

Uwe

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

Sorry, this has gone lost somewhere in my mails. But as sarge is
out of support, this PC has died long ago and as far as I can see
all the other issues are also fixed in the current installer I
close this old bug.

Thanks

Uwe

--- End Message ---

Re: debconf BUG ?

[Colin Watson]

On Wed, Feb 18, 2009 at 05:27:15PM +0100, Anthony wrote:
> it seems that a error occur during the partman installation,
> 
> the debconf seems to be wrong...
> 
> after an install, and a debconf-get-selections --installer
> 
> I get somethink like :
> 
> "partman-auto partman-auto/init_automatically_partition   select  
> 50some_device__regular"

I don't see the error; this appears to be as expected. You should be a
bit more verbose when reporting things you think are wrong, really.

However, 'debconf-get-selections --installer' does not (unfortunately)
output information suitable for preseeding directly. If your goal here
is to perform automatic partitioning, you should read the installation
guide instead; Appendix B has copious information about preseeding.

-- 
Colin Watson   [cjwat...@debian.org]


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#509117: Can I overwrite a file in /etc?

[Colin Watson]

On Mon, Feb 09, 2009 at 07:36:31PM +0200, Anton Zinoviev wrote:
> On Thu, Dec 18, 2008 at 04:44:28PM +0100, Frédéric Boiteux wrote:
> > I've used the '--save' command of setupcon to save it to disk (in 
> > /etc/console-setup/boottime.kmap.gz and now, these boot scripts run very 
> > quickly, 
> > and bootchart tells me I gained 9 seconds :-)
> > 
> > Perhaps a mechanism could be added to save config or suggest it ?
> 
> Setupcon uses /etc/console-setup/boottime.kmap.gz only if it is not older 
> than the 
> configuration file /etc/default/console-setup.  If it is older this means the 
> keymap has to be regenerated.
> 
> In order to avoid future time consuming regenerations, setupcon has to 
> overwrite 
> boottime.kmap.gz.  But this file is situated in /etc so accordingly to the 
> policy 
> it is a configuration file and may not be overwriten without administrator's 
> knowledge.
> 
> I'd like to ask if I can make an exception for this case.  The standard 
> solution -- 
> move boottime.kmap.gz from /etc to /var -- is not available because setupcon 
> must 
> be able to work when /var is not yet mounted.

I think this would be fine. It's effectively a cache of another
configuration file, and I would expect it to be fairly rare to fiddle
with /etc/console-setup/boottime.kmap.gz directly, given its format.

I definitely agree that the boot speed changes are worth it.

-- 
Colin Watson   [cjwat...@debian.org]



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: dmraid 1.0.0.rc15-1

[Colin Watson]

On Mon, Feb 16, 2009 at 02:11:17PM +, Colin Watson wrote:
> On Mon, Feb 16, 2009 at 02:16:48PM +0100, Frans Pop wrote:
> > On Monday 16 February 2009, Colin Watson wrote:
> > > The necessary improvements are attached, and I can commit these once
> > > Giuseppe has uploaded this to unstable. I don't think we should
> > > simplify it by throwing out the old output-comparison code yet, since
> > > that would presumably cause problems for lenny-and-a-half.
> > 
> > It's not a problem for lenny-and-a-half, unless we call dmraid in the 
> > chroot target as well as the D-I environment. The D-I environment has to 
> > be consistent by definition [1].
> 
> Oh, good point, I was confused. Updated patch attached.

All committed to trunk now.

-- 
Colin Watson   [cjwat...@debian.org]


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

rescue_1.20_i386.changes ACCEPTED

[Debian Installer]

Accepted:
rescue-check_1.20_all.udeb
  to pool/main/r/rescue/rescue-check_1.20_all.udeb
rescue-mode_1.20_all.udeb
  to pool/main/r/rescue/rescue-mode_1.20_all.udeb
rescue_1.20.dsc
  to pool/main/r/rescue/rescue_1.20.dsc
rescue_1.20.tar.gz
  to pool/main/r/rescue/rescue_1.20.tar.gz


Override entries for your package:
rescue-check_1.20_all.udeb - standard debian-installer
rescue-mode_1.20_all.udeb - optional debian-installer
rescue_1.20.dsc - source misc

Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 505113 


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#505113: marked as done (rescue-mode requires a root filesystem to be useful)

[Debian Bug Tracking System]

Your message dated Fri, 20 Feb 2009 13:47:07 +
with message-id 
and subject line Bug#505113: fixed in rescue 1.20
has caused the Debian Bug report #505113,
regarding rescue-mode requires a root filesystem to be useful
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.)


-- 
505113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505113
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rescue
Version: 20081029
Severity: normal

In trying to rescue my system, which had a screwed up RAID/LVM
configuration (#505111), I gave the d-i rescue image a shot. I tried
to install the cfdisk and network-console components, but d-i
wouldn't let me unless I told it where my root filesystem was.
Unfortunately, I could not answer that question, since I first had
to rescue the root filesystem. As a whole, rescue mode was
completely unhelpful.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
 .''`.   martin f. krafft 
: :'  :  proud Debian developer, author, administrator, and user
`. `'`   http://people.debian.org/~madduck - http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
--- End Message ---
--- Begin Message ---
Source: rescue
Source-Version: 1.20

We believe that the bug you reported is fixed in the latest version of
rescue, which is due to be installed in the Debian FTP archive:

rescue-check_1.20_all.udeb
  to pool/main/r/rescue/rescue-check_1.20_all.udeb
rescue-mode_1.20_all.udeb
  to pool/main/r/rescue/rescue-mode_1.20_all.udeb
rescue_1.20.dsc
  to pool/main/r/rescue/rescue_1.20.dsc
rescue_1.20.tar.gz
  to pool/main/r/rescue/rescue_1.20.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 505...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated rescue package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 20 Feb 2009 13:27:53 +
Source: rescue
Binary: rescue-check rescue-mode
Architecture: source all
Version: 1.20
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team 
Changed-By: Colin Watson 
Description: 
 rescue-check - enter d-i rescue mode if requested (udeb)
 rescue-mode - mount requested partition and start a rescue shell (udeb)
Closes: 505113
Changes: 
 rescue (1.20) unstable; urgency=low
 .
   * Merge from Ubuntu:
 - Load ext4 module if available.
   * Allow operation without a root filesystem (closes: #505113).
 .
   [ Updated translations ]
   * Belarusian (be.po) by Pavel Piatruk
   * Basque (eu.po) by Piarres Beobide
   * French (fr.po) by Christian Perrier
   * Galician (gl.po) by marce villarino
   * Hindi (hi.po) by Kumar Appaiah
   * Kazakh (kk.po) by daur88
   * Malayalam (ml.po) by Praveen Arimbrathodiyil
   * Marathi (mr.po) by Sampada
   * Portuguese (pt.po) by Miguel Figueiredo
   * Slovak (sk.po) by Ivan Masár
   * Swedish (sv.po) by Daniel Nylander
   * Thai (th.po) by Theppitak Karoonboonyanan
   * Tagalog (tl.po) by Eric Pareja
Checksums-Sha1: 
 a85d7670353ff2ae2d6c3189b16d5d3a7e887c0d 892 rescue_1.20.dsc
 f0bd3f93127ce81000133c99de359cd48031a201 100732 rescue_1.20.tar.gz
 4285d77856bbeb8059e69a3802ed7dfb59e1c185 2340 rescue-check_1.20_all.udeb
 bb4839c9770c42fe6fd6eb079645491a7f78128e 80338 rescue-mode_1.20_all.udeb
Checksums-Sha256: 
 b9e297676dc2b4f0b619d4460b20e92e572b22be9dfb5282ba3d8f5985c4ee34 892 
rescue_1.20.dsc
 16b5d8172851abc5847b6f40012b158dba3c8c2712366c4c49c867f7b162eec4 100732 
rescue_1.20.tar.gz
 7e5e0cb75f3430be4b3ac75e6eb4149b0aeb19fd80a6f682f717d0d647c1b1a5 2340 
rescue-check_1.20_all.udeb
 204f1d6720e485f20c07aba6d817e7248d171c8b0be3279866caae092f55af57 80338 
rescue-mode_1.20_all.udeb
Files: 
 3e52d0a7e29f1ef665fbce99e74aa9f8 892 debian-installer optional rescue_1.20.dsc
 a3fa61fb88353248c0a5df725f1f554b 100732 debian-installer optional 
rescue_1.20.tar.gz

Bug#516127: Status bar

[Marco Túlio Gontijo e Silva]

Another thing I've noticed is that the status bar was stuck in about 20%
while downloading the debs, even when it was about to finish.

Greetings.
-- 
marcot
http://marcot.iaaeee.org/




-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: reassign 368294 to partman-target

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 368294 partman-target
Bug#368294: debian-installer: "go back" "continue" are the same if ROOT(/) not 
selected
Bug reassigned from package `partman-base' to `partman-target'.

>
End of message, 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

Re: debconf BUG ?

[Anthony]

Le vendredi 20 février 2009 14:46, Colin Watson a écrit :
|> On Wed, Feb 18, 2009 at 05:27:15PM +0100, Anthony wrote:
|> > it seems that a error occur during the partman installation,
|> > 
|> > the debconf seems to be wrong...
|> > 
|> > after an install, and a debconf-get-selections --installer
|> > 
|> > I get somethink like :
|> > 
|> > "partman-auto  partman-auto/init_automatically_partition   select  
50some_device__regular"
|> 
|> I don't see the error; this appears to be as expected. You should be a
|> bit more verbose when reporting things you think are wrong, really.
|> 

sorry
i forgotted to say that the message occurs during etch-and-a-half 
installation...

AND

i just wanted to know if it is a bug or not and If t's  a bug, inform about 
this bug...:


and i know,

read doc..;

i read the doc B

and i don't agree with you, doc has not copious informations :
the only information about partitionning is :
### Partitioning
# If the system has free space you can choose to only partition that space.
#d-i partman-auto/init_automatically_partition select biggest_free

do you think this has copious about init_automatically_partition ?


 

|> However, 'debconf-get-selections --installer' does not (unfortunately)
|> output information suitable for preseeding directly. If your goal here
|> is to perform automatic partitioning, you should read the installation
|> guide instead; Appendix B has copious information about preseeding.
|> 


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Please unblock libsdl1.2/1.2.13-4

[Aurelien Jarno]

On Wed, Feb 18, 2009 at 11:58:59AM +0100, Aurelien Jarno wrote:
> Hi, 
> 
> Could you please allow libsdl1.2/1.2.13-4 to migrate into testing, if it
> is ok from a d-i PoV? It has no RC bug and is waiting for more than 100
> days old.
> 

Any new on that?

-- 
Aurelien Jarno  GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#516280: GRUB Installed on wrong device during Lenny Install

[Christian Perrier]

Quoting Rob Fulton (r...@cow-frenzy.co.uk):
> Package: debian-installer
> Version: 20090123
>
> When installing Lenny on a HP DL360 / DL380 server Grub is installed on  
> the wrong device.
>
> The server is booted from CD, during network detection, the bnx2 firmware 
> is required. A USB key is inserted to provide the firmware. The disks are 
> then partitioned and the install proceeds, grub is installed on the 
> master boot record. On reboot with the USB stick still connected, GRUB 
> loads and the os is booted from the internal disks. Without the USB 
> drive, the OS refuses to boot.
>
> The internal disks are presented as /dev/cciss/c0d0 devices, the USB 
> drive is presented as /dev/sda.
>
> Running grub-install to the /dev/cciss/c0d0 device after install resolves 
> the problem but the installer appears to be picking the wrong device when 
> grub is installed


Such issues are documented in the errata file.

This issue indeed pertains to thegeneral goal of having fixed mount
names instead of relying on the devices names

As this issue is documented and well known, I propose closing it.




signature.asc
Description: Digital signature

Bug#513283: debian-installer: "keymap select" is ignored when loading the preseeding file from kernel parameters

[Christian Perrier]

Quoting Lasse Aagren (aag...@dtic.dk):

> Bingo. dk-latin1 works. I should probably have thought about that. But  
> dk worked with etch :-)


This is indeed the consequence of changes that happened in
console-data with the removal of such aliases from possible choices.

I don't really consider this to be a bug indeed as these aliases have
never been really supported nor documented TTBOMK.




signature.asc
Description: Digital signature

Re: Lenny 5.0 i386 Install with LVM Cannot Reboot

[Peter McGill]

Ferenc Wagner wrote:

Peter McGill  writes:


Appears to install fine, but boot after install fails.

Volume group "debian" not found.
The above line repeats after a time.


This repeat is somewhat strange, but anyway...


Ok, so I booted again to try your suggestions...
Here is a more detailed bootup sequence.

My SCSI Adapter is detected by the kernel.
Running /scripts/init-premount ...
Mounting root filesystem ...
device-mapper
  Volume group "debian" not found
  Volume group "debian" not found
Waiting for root filesystem ...

About 1 second later My SCSI hard disk is detected by the kernel.
sda: sda1 sda2

Then about 3 minutes go by and it gives up and drops to the shell.
Gave up waiting for root device.
ALERT! /dev/mapper/debian-root does not exist. Dropping to a shell!


Then a while later the following is reported.
ALERT! /dev/mapper/debian-root does not exist. Dropping to a shell!


What happens if you invoke

vgchange -ay

in this shell?  If it activates the volume group, exit the shell and
see if it boots up.


It also seems to not be loading the usb keyboard driver cause I cannot 
type anything at the shell. I plugged in a PS/2 temporarily to run the 
commands.


vgchange -ay does not appear to do anything.
cat /proc/cmdline
  root=/dev/mapper/debian-root ro

I rebooted and using grub's online editing feature added rootdelay=5
It booted fine then. Then I updated grub so rootdelay=5 is default.
Appears to boot consistently now, thanks for the help.

Peter


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#516339: debian-installer: init_automatically_partition behaves different on lenny with LVM

[Andreas Unterkircher]

Package: debian-installer
Version: 20090123
Severity: normal

for etch I was using the following preseed lines to setup my systems
partition with LVM:

d-i partman-auto/purge_lvm_from_device boolean true
d-i partman/confirm_write_new_label boolean true
d-i partman/confirm boolean true
d-i partman-lvm/confirm boolean true
d-i partman-lvm/device_remove_lvm boolean true
d-i partman-auto/choose_recipe select boot-root-lvm
d-i partman-auto/init_automatically_partition \
   select Guided - use entire disk and set up LVM
d-i partman/choose_partition \
   select Finish partitioning and write changes to disk

d-i partman-auto/expert_recipe string \
  boot-root-lvm ::\
  100 512 200 ext2\
  $primary{ } $bootable{ }\
  method{ format } format{ }  \
  use_filesystem{ } filesystem{ ext2 }\
  mountpoint{ /boot } \
  .   \
  1000 512 1000 xfs   \
  $lvmok{ }   \
  method{ format } format{ }  \
  use_filesystem{ } filesystem{ xfs } \
  mountpoint{ / } \
  .   \
. (more LVs)


When I do this now with the rc2 debian-installer instead, the behavior of
init_automatically_partition has changed. Feeding it with "Guided - use
entire disk and set up LVM" will not as the name say use logical volumes
for the partition, furthermore it creates common logical partitions.

When I instead provide the option as

d-i partman-auto/init_automatically_partition \
   select some_device_lvm

the previous etch behavior gets restored and the logical volumes get
created correctly.

It seems that this "Guided - use entire disk and set up LVM" in fact now
matches the "Guided - use entire disk" option.

So far this is reproduceable here.

Andreas

-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#516347: debian-installer: guided-with-lvm no longer allows multiple primary partition

[Andreas Unterkircher]

Package: debian-installer
Version: 20090123
Severity: normal

With etch's debian-installer we used the preseed lines below to
automatically setup our partitions. /boot and / as primary
partitions, all others as logical volumes.

d-i partman-auto/init_automatically_partition \
   select Guided - use entire disk and set up LVM

d-i partman-auto/expert_recipe string \
  boot-root-lvm ::\
  100 512 200 ext2\
  $primary{ } $bootable{ }\
  method{ format } format{ }  \
  use_filesystem{ } filesystem{ ext2 }\
  mountpoint{ /boot } \
  .   \
  1000 512 1000 xfs   \
  $primary{ } \
  method{ format } format{ }  \
  use_filesystem{ } filesystem{ xfs } \
  mountpoint{ / } \
  .   \
  512 512 200% linux-swap \
  $lvmok{ }   \
  method{ swap } format{ }\
  .   \
  3000 512 4000 xfs   \
  $lvmok{ }   \
  method{ format } format{ }  \
  use_filesystem{ } filesystem{ xfs } \
  mountpoint{ /usr }  \
  .   \
  2000 512 3000 xfs   \
  $lvmok{ }   \
  method{ format } format{ }  \
  use_filesystem{ } filesystem{ xfs } \
  mountpoint{ /var }  \
  .   \
  100 384 200 xfs \
  $lvmok{ }   \
  method{ format } format{ }  \
  use_filesystem{ } filesystem{ xfs } \
  mountpoint{ /var/tmp }  \
  .   \
  512 384 2000 xfs\
  $lvmok{ }   \
  method{ format } format{ }  \
  use_filesystem{ } filesystem{ xfs } \
  mountpoint{ /tmp }  \
  .   \
  200 256 1000 xfs\
  $lvmok{ }   \
  method{ format } format{ }  \
  use_filesystem{ } filesystem{ xfs } \
  mountpoint{ /home } \
  .   \
  200 256 1000 xfs\
  $lvmok{ }   \
  method{ format } format{ }  \
  use_filesystem{ } filesystem{ xfs } \
  mountpoint{ /srv }  \
  .   \
  10 128 10 xfs   \
  $lvmok{ }   \
  method{ format } format{ }  \
  use_filesystem{ } filesystem{ xfs } \
  mountpoint{ /tobedeleted }  \
  .



Now with d-i from lenny, it refuses to accept our receipe by
complaining: Can't have a partition outside the disk!

In /var/log/partman I can find:

parted_server: add_primary_partition(disk(67108864),2345490-67109161)
parted_server: OUT: Error
parted_server: OUT: Can't have a partition outside the disk!
parted_server: OUT:
parted_server: OUT: Cancel
parted_server: OUT:
/bin/autopartition-lvm: error_handler: exception with type Error
...

The exact same receipe on the same machine with the etch installer
works fine. So I'm not sure if this is now the indeed behavior of
guided-with-lvm (compared to etch) or just some regression.

Andreas

-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Re: Please unblock libsdl1.2/1.2.13-4

[Otavio Salvador]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Aurelien Jarno  writes:

> On Wed, Feb 18, 2009 at 11:58:59AM +0100, Aurelien Jarno wrote:
>> Hi, 
>> 
>> Could you please allow libsdl1.2/1.2.13-4 to migrate into testing, if it
>> is ok from a d-i PoV? It has no RC bug and is waiting for more than 100
>> days old.
>> 
>
> Any new on that?
>
> -- 
> Aurelien JarnoGPG: 1024D/F1BCDB73
> aurel...@aurel32.net http://www.aurel32.net

Ack

- -- 
O T A V I OS A L V A D O R
- -
 E-mail: ota...@debian.org  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://otavio.ossystems.com.br
- -
"Microsoft sells you Windows ... Linux gives
 you the whole house."
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ 

iEYEARECAAYFAkmfIcoACgkQLqiZQEml+FXGugCgl9fHXAKdJbknYacHSiLZJRo9
gtYAnRIR2E73IibkCymbj2xaFV05eOV8
=fnK+
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

lenny corrupt image

[Jian Gao]

Hello,

I tried to install the lenny but failed when reached "Install the base
system". I got a warring says:
"Warning:
ftp://ftp.us.debian.org/debian/dists/lenny/main/binary-armel/Packages.gz was
corrupt"

I also tried Canada mirror and had the same problem.

here is syslog:
-
Feb 20 21:36:31 apt-install: Queueing package e2fsprogs for later
installation
Feb 20 21:36:31 main-menu[2513]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)
Feb 20 21:36:48 main-menu[2513]: INFO: Falling back to the package
description for auto-install
Feb 20 21:36:48 main-menu[2513]: INFO: Falling back to the package
description for ai-choosers
Feb 20 21:36:48 main-menu[2513]: INFO: Menu item 'bootstrap-base' selected
Feb 20 21:36:53 debootstrap: gpgv:
Feb 20 21:36:53 debootstrap: Signature made Sat Feb 14 14:02:52 2009 UTC
using DSA key ID 6070D3A1
Feb 20 21:36:53 debootstrap: gpgv:
Feb 20 21:36:53 debootstrap: Good signature from "Debian Archive Automatic
Signing Key (4.0/etch) "
Feb 20 21:36:53 debootstrap:
Feb 20 21:36:53 debootstrap: gpgv:
Feb 20 21:36:53 debootstrap: Signature made Sat Feb 14 14:05:28 2009 UTC
using DSA key ID F42584E6
Feb 20 21:36:54 debootstrap: gpgv:
Feb 20 21:36:54 debootstrap: Good signature from "Lenny Stable Release Key <
debian-rele...@lists.debian.org>"
Feb 20 21:36:54 debootstrap:
Feb 20 21:45:40 base-installer: error: exiting on error
base-installer/debootstrap-failed
Feb 20 21:45:45 main-menu[2513]: WARNING **: Configuring 'bootstrap-base'
failed with error code 1
Feb 20 21:45:45 main-menu[2513]: WARNING **: Menu item 'bootstrap-base'
failed.
Feb 20 21:45:51 main-menu[2513]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)

Thanks for help.

Jian

Re: Please unblock libsdl1.2/1.2.13-4

[Luk Claes]

Otavio Salvador wrote:
> Aurelien Jarno  writes:
> 
>> On Wed, Feb 18, 2009 at 11:58:59AM +0100, Aurelien Jarno wrote:
>>> Hi, 
>>>
>>> Could you please allow libsdl1.2/1.2.13-4 to migrate into testing, if it
>>> is ok from a d-i PoV? It has no RC bug and is waiting for more than 100
>>> days old.
>>>
>> Any new on that?
> 
> Ack

unblocked

Cheers

Luk


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#513283: debian-installer: "keymap select" is ignored when loading the preseeding file from kernel parameters

[Lasse Aagren]

On 20/02/2009, at 17.52, Christian Perrier wrote:


Quoting Lasse Aagren (aag...@dtic.dk):

Bingo. dk-latin1 works. I should probably have thought about that.  
But

dk worked with etch :-)



This is indeed the consequence of changes that happened in
console-data with the removal of such aliases from possible choices.

I don't really consider this to be a bug indeed as these aliases have
never been really supported nor documented TTBOMK.



Ok. But on a freshly installed lenny (i386) machine a "dpkg -L console- 
data" gives me both:


/usr/share/keymaps/i386/qwerty/dk-latin1.kmap.gz

and

/usr/share/keymaps/i386/qwerty/dk.kmap.gz

(which btw are not totally alike - they differ in 2 or 3 lines). So if  
this package decides which "names" is allowed in the "d-i console- 
keymaps-at/keymap" statement, then I'm confused.


--
Lasse Aagren
Technical Information Center of Denmark



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#516392: debian-installer: unbootable system after install

[Derek Chan]

Package: debian-installer
Version: lenny
Severity: normal


I have a Dell SC420 with a ICH6 on-board SATA controller (sda), and a
PDC20268 2-port PATA with two drives on it (hde, hdg)

I installed from the business card iso on a USB flash stick.  I install
GRUB to the root partition (sda2) because then Windows can't get at it.
This was a fresh install, and I install to sda2 (hde, hdg are my data
disks).  After the install, the machine was unbootable.  "Unable to load
operating system".  Booting back into the installer (soon wishing I had
the 'rescue' image on the full CD), I was able to determine with dd that
GRUB had NOT been installed on any drive or partition.  dd if=/dev/sda2
bs=512 count=1 showed only zero'd out bytes (this was a newly
partition/filesystem).  I did the install a couple more times without
any more success (I saw a grub-installer error, I think it was about a
device map file missing, but in my haste to get the machine up, I didn't
think to write it down exactly).  Removing the PDC20268 card made the
install and subsequent boot work fine.

Please let me know what more information you need.



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#516393: debian-installer: inability to unmount /hd-media causes failure errors

[Derek Chan]

Package: debian-installer
Version: lenny
Severity: normal


I was doing an install off a usb stick, with the business card iso on
the media.

Every partitition with an ISO on it was mounted, but after finding that
it was not the correct installer ISO (winxp.iso, for example), it would
try to unmount and fail (busy) and spit me back to the main installer
menu (what would you like to do next?).  I could pick the same option
(looking for the installer ISO) and it would continue where it left off
(it had no trouble mounting a second or third partition on /hd-media)
and eventually it made it to sdb (the usb stick) and continued.
Annoying, and misleading to a newcomer, but has a workaround (scan
repeatedly)

Let me know what other information you need.




-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org