Bug#600320: Installation: set password for root; did not create a user; could not login after 1st reboot.

[Denis Laxalde]

Hello,

I'm trying to help a bit on triaging installation reports.

Here, the main problem (as per the bug title and part of the report)
seems to be (quoting John Hunter [2010-10-16]):
> I set up the root password but declined to create any
> [more] users. The install apparently finished OK and then I rebooted.
> Upon reboot, the system would not let me log in as root so that I
> could not manually set up /etc/password, /etc/shadow, /etc/group
> and /etc/sudoers.

So, starting from that, I tried to reproduce this by doing a fresh
(KVM) installation. I set a root password but did not create any
regular user. The installation completed normally (just had to go back
twice in the installation procedure to be able to skip the user
creation step) and, upon reboot, I actually had no problem logging-in
as root.
I would then say that this bug is not reproducible and its severity
may be downgraded. The partition formatting debate is probably another
issue.

Hope this helps...


  Denis



-- 
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/20101122144213.78ae6...@gmail.com

Bug#604155: Windows 7 not in grub menu

[Denis Laxalde]

tags 604155 + moreinfo
thanks

Hi,

On Mon, 22 Nov 2010 21:21:03 +0100, Daniel Pocock wrote:
> I had already run update-grub, but that hasn't made any difference

update-grub should call the script '/etc/grub.d/30_os-prober'. What if
you call it directly? Does it return any error? You may also call
os-prober directly.

Maybe some details about your partitions (or a complete installation
report) would be usefull.

Cheers,

Denis.



-- 
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/20101125155321.21276...@gmail.com

Bug#603731: Debian will not load

[Denis Laxalde]

tags 603731 + moreinfo
thanks

Hi,

Bert wrote:
> Package:  Lenny
> Version:  5.0.6
> 
> After inserting DVD #1 and entering the command:
> netcfg/disable_dhcp=true debian-installer/framebuffer=false  hit 
> Enter and the following is displayed:
> 
> BUG:  Int 6: CR2 
> 
> EDI:   c0365f8cESI 4000EBP c0365f88   ESP  c0365f44
> EBX:     EDX: 0006  ECX:  EAX:  4000
> ERR:     EIP:  c0112c13  CS:  c0370060  flg:  00010092
> 
> Stack:
>   c0365f90   c0365f8c   c0365f88   c0365f94   c0365f90 
> c0365f8c   c036588c   c03749d0
>   c0365f94   c0365f8c   c0365f88   c0365f94   c0365f90 
> c400  00441031   
>   c000  0009f000   03bed000    c0365fd0 
> c036c430     

First, could you provide more information about:
 - the installer image you used (with an URL)
 - your hardware

Then, it looks like a kernel issue. A more recent kernel may help. Since
you are apparently trying to install Lenny, I would suggest that you
try to install Squeeze (the upcoming stable Debian release).
See: http://www.debian.org/devel/debian-installer/

Thanks for your report,


Denis



-- 
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/20101125214250.15600...@gmail.com

Bug#604155: Windows 7 not in grub menu

[Denis Laxalde]

reassign 604155 grub-pc
tags 604155 - moreinfo
forcemerge 604155 568639
thanks

Hello Daniel,

Daniel Pocock wrote:
> So os_prober can find Windows, but it isn't in the menu

Thanks for the follow-up. Since grub is apparently not able to generate
the windows menu entry even after installation, I would say this is a
bug in grub rather than in the installer.
Hence, reassigning and merging with #568639 ("winxp partition detected,
but not added to grub.cfg").

Cheers,

Denis  



-- 
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/20101128214519.1c94b...@gmail.com

Bug#603673: RTL8111/8168B problems

[Denis Laxalde]

tags 603673 + moreinfo
thanks

Hi,

On Tue, 16 Nov 2010 10:27:59 +0100, Paul van der Vlis wrote:
> RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168]
> (rev 06) Subsystem: ASUSTeK Computer Inc. Device [1043:8432]
>   Kernel driver in use: r8169
> 
> 
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> 
> Initial boot:   [O]
> Detect network card:[E]
> Configure network:  [E]

It seems that your 8168 card does not work with the r8169 shipped with
Linux kernel 2.6.32. However, from #531172, it seems that this module
used to work with Lenny's kernel. Can you confirm this?

Thanks in advance,

Denis 



-- 
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/20101129124854.061ec...@gmail.com

Bug#603649: installation-reports: XServe G5: Network interface goes down

[Denis Laxalde]

tags 603649 + moreinfo
thanks

Milan Kupcevic a écrit :
> Package: installation-reports
> 
> Boot method: CD
> Image version:
> http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/powerpc/iso-cd/debian-testing-powerpc-netinst.iso
> Date: Mon Nov 15 20:52:21 EST 2010
> 
> Machine: XServe G5
[...] 
> I get "Configure the package manager" window with "Bad archive mirror"
> message. I open second terminal and check network interface state with
> "ip addr" command. Network interfaces are there, but in DOWN state. At
> this point I chose  until I get to the Debian installer main
> menu, where I choose 'Configure the network' and go through network
> configuration again. Network interface gets up, the "Configure the
> package manager" installer module then continues fine.
> 
> I went through installation procedure several times. The same problem
> happened every time. Network interface initially gets detected and
> configured, but goes into DOWN state at the point when "Detect disks"
> discovers hardware.

>From the syslog you provided:
> Nov 16 00:53:50 kernel: [   41.455504] tg3 0001:07:04.0: firmware: requesting 
> tigon/tg3_tso.bin
> Nov 16 00:53:50 kernel: [   41.459852] eth0: Failed to load firmware 
> "tigon/tg3_tso.bin"
> Nov 16 00:53:50 kernel: [   41.459857] eth0: TSO capability disabled.
> Nov 16 00:53:50 kernel: [   41.514498] ADDRCONF(NETDEV_UP): eth0: link is not 
> ready
> Nov 16 00:53:50 kernel: [   41.585672] tg3 0001:07:04.1: firmware: requesting 
> tigon/tg3_tso.bin
> Nov 16 00:53:50 kernel: [   41.589493] eth1: Failed to load firmware 
> "tigon/tg3_tso.bin"
> Nov 16 00:53:50 kernel: [   41.589497] eth1: TSO capability disabled.
> Nov 16 00:53:50 kernel: [   41.644029] ADDRCONF(NETDEV_UP): eth1: link is not 
> ready
> Nov 16 00:53:51 check-missing-firmware: missing firmware files 
> (tigon/tg3_tso.bin) for tg3
(The same appears several times later.)

Aren't you missing a firmware for you network card? Did you load the
firmware during installation?

Cheers,

Denis



-- 
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/20101130154439.ga8...@mail.gmail.com

Bug#602539: Successfull install creates broken system (mounting fs fails)

[Denis Laxalde]

clone 602539 -1
reassign -1 partman
retitle -1 the number of devices in raid arrays can be modified afterwards
tags -1 d-i
thanks

On Fri, 05 Nov 2010 19:15:19 +0100, Goswin von Brederlow wrote:
> Partitioning hard drives (DI uses title 'Partitioning disks'):
>   - Creating raid 1
> In the dialog it says:
> + "A minimum of 2 active devices is required."
>   The system will have 4 disks but 3 are full with data in the
> old system and need to be transfered disk by disk. So I wanted to
> create a raid 1 with 1 active disk and grow it later to 4 disks.
> 
> + "NOTE: this setting cannot be changed later."
>   mdadm --grow can change it so this is simply not true.

The aforementioned dialog may be updated.



-- 
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/20101130155012.2bfb2...@gmail.com

Bug#602539: Successfull install creates broken system (mounting fs fails)

[Denis Laxalde]

clone 602539 -1
reassign -1 partman-base
retitle -1 Selecting a predefined mount point should set a corresponding label 
if none is set already
severity -1 wishlist
tags -1 d-i
thanks

On Fri, 05 Nov 2010 19:15:19 +0100, Goswin von Brederlow wrote:
>   - Creating filesystem
> + Selecting a predefined mount point should set a coresponding
> label if none is set already. My root partition has label root, /usr
> has label usr, /var has label var and /home has label home.

This looks like a wishlist bug to me. So reassigning to partman-base (my
best guess here ;).



-- 
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/20101130161609.6c068...@gmail.com

Bug#602539: Successfull install creates broken system (mounting fs fails)

[Denis Laxalde]

clone 602539 -1
reassign -1 base-installer
retitle -1 should check size of common mountpoints before proceeding to 
installation
tags -1 d-i
thanks

On Fri, 05 Nov 2010 19:15:19 +0100, Goswin von Brederlow wrote:
> Install base system:
>   + Check size of common mountpoints (/, /usr, /var)
> At first I made / too small and it failed much later during the
> installation of the kernel image. Debian kernels are HUGE
> compared to my usual build-to-fit custom kernel.
> It would be good if the installer would know the size requirement
> for all the usual mountpoints people use and check if the defined
> partitions have sufficient space. The numbers should be known for at
> least the standard task, more would be better.

This may also be a wishlist.



-- 
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/20101130162354.002a8...@gmail.com

Bug#602539: Successfull install creates broken system (mounting fs fails)

[Denis Laxalde]

reassign 605516 partman-base
thanks

On Tue, 30 Nov 2010 22:35:44 +0100, Christian PERRIER wrote:
> Why against base-installer? 

You're right. partman-base would be better I guess.



-- 
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/20101130164623.72cef...@gmail.com

Bug#602292: Squeeze disk detection failed on MacBook Air 11.6"

[Denis Laxalde]

forcemerge 600305 602292
thanks

On Wednesday, 03 November 2010, KAMAGASAKO Masatoshi wrote:
> Package: installation-reports
> 
> Boot method: netinstall CD
> Image version: 
> cdimage/daily-builds/squeeze_d-i/20101103-3/amd64/iso-cd/debian-testing-amd64-netinst.iso
> Date: Wed, 03 Nov 2010 19:30:58 +0900
> 
> Machine: Apple MacBook Air 11.6"
> Processor: Intel Core 2 Duo 1.6GHz
> Memory: 4GB
> Partitions: 128GB SSD, MCP89 chipset
> 
> Base System Installation Checklist:
> 
> Initial boot:   [O]
> Detect network card:[O]
> Configure network:  [O]
> Detect CD:  [O]
> Load installer modules: [O]
> Detect hard drives: [E]
> Partition hard drives:  [ ]
> Install base system:[ ]
> Clock/timezone setup:   [ ]
> User/password setup:[ ]
> Install tasks:  [ ]
> Install boot loader:[ ]
> Overall install:[ ]
> 
> Comments/Problems:
> boot from rEFIt graphical menu, selected expert installation.
> no hard disk is detected in the stage.
> 
> some messages found in dmesg about ata;
> 
> > [time] ata1: SATA max UDMA/133 irq_stat 0x00400040, connection status 
> > changed irq 25
> ...
> > [time] ata1: link is slow to repond, please be patient (ready=0)
> > [time] ata1: COMRESET failed (errno=-16)
> > [time] ata1: link is slow to repond, please be patient (ready=0)
> > [time] ata1: COMRESET failed (errno=-16)
> > [time] ata1: link is slow to repond, please be patient (ready=0)
> > [time] ata1: COMRESET failed (errno=-16)
> > [time] ata1: limiting SATA link speed to 1.5 Gbps
> > [time] ata1: COMRESET failed (errno=-16)
> > [time] ata: reset failed, giving up
> 
> same problem?
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600305

Very likely, thanks for the pointer. However, this should be solved with
the last installer which includes version 2.6.32-27 of the Linux kernel.
Can you try again?

Thanks for your report.

Denis



-- 
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/20101201193200.ga22...@mail.gmail.com

Bug#602539: Successfull install creates broken system (mounting fs fails)

[Denis Laxalde]

clone 602539 -1
reassign -1 debian-installer
retitle -1 /etc/network/run is directory, not link to /dev/shm/network
tags -1 d-i
thanks

On Thu, 02 Dec 2010 09:05:35 +0100, Goswin von Brederlow wrote:
> >> - /etc/network/run is directory, not link to /dev/shm/network
> >>   This makes ifup fail during boot and the system is left without
> >> networking. The strange thing is that ifupdown support read-only /
> >> just fine normaly. The postinst script makes /etc/network/run a
> >> link to /dev/shm/network if /etc/network/run is mising
> >> and /dev/shm exists.
> >> 
> >>   So is /dev/shm missing during DI?
> >> 
> >>   The fix for this was quite easy:
> >>   % rm -rf /etc/network/run
> >>   % dpkg-reconfigure ifupdown  
> >
> > #387611  
> 
> Nope. /etc/network/run does exist. It is just created wrong because
> /dev/shm was not mounted in DI. This really is a DI bug.
> 
> If you find out where this should belong to then the install report
> can be closed.

Ok, thanks for the explanation. As I don't exactly know which d-i
package is faulty here, I reassign to debian-installer pseudo package.
You may adjust the severity and update the title of the clone if it's
not accurate.

Thanks again for your report,

Denis



-- 
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/20101203135729.16a89...@gmail.com

Bug#600524: installation-reports: After install grub doesn't boot

[Denis Laxalde]

reassign 600524 grub-installer
retitle 600524 system unbootable after installation using GPT
thanks

On Sun, 17 Oct 2010 23:22:52 +0400, Khudyakov Alexey wrote:
> Package: installation-reports
> Severity: normal
> Tags: d-i
[...]
> Install boot loader:[E ]
> Overall install:[E ]
> 
> Comments/Problems:
> 
> == Attempt 1. ==
> 
> Install goes without any problems. However after install computer
> is unbootable it even doesn't come to GRUB menu, just says
> "no bootable medium found". Still it's possible to boot from USB
> stick in resque mode. When I try to reinstall GRUB it fails to do
> so because of GPT
> 
> Here is error message
> grub-installer: grub-setup: warn: This GPT partition label has no
> BIOS Boot Partition; embedding won't be possible!
> 
> Some googling reveals following links:
> 
> * http://grub.enbug.org/BIOS_Boot_Partition
> * https://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/506670
> * https://bugs.launchpad.net/ubuntu/+source/parted/+bug/107326
> 
> When GPT is used and it's silently used with 2TB+ disk GRUB require
> small partition so I made another attempt to install debian.
> 
> 
> == Attempt 2. ==
> 
> During install I created small (1MB) partition and marked is as
> bios_grub. GRUB installs without any errors or warnings after that
> but system is still unbootable. I can boot in resque mode from 
> USB stick and run 'grub-install /dev/sda' in the shell or 
> reinstall grub from menu no errors reported but system still
> fail to boot
> 

It looks like an issue in grub-installer, maybe similar to #548156.
Thanks for your report.



-- 
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/20101206124535.3ac4e...@mail.gmail.com

Bug#600235: installer forgot boot partition, after the step "configure encrypted volumes"

[Denis Laxalde]

reassign 600235 partman-crypto
retitle 600235 previously defined mount points are discarded after encrypted 
volumes configuration
tags 600235 d-i
thanks

On Thu, 14 Oct 2010 23:09:24 +0200, Matthias Köhne wrote:
> Package: installation-reports
> 
> Boot method: CD
> Image version: debian-testing-i386-netinst.iso
> (daily build: Thu Oct 14 15:15:49 UTC 2010)
> Date: 2010-10-14
> 
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> 
> Initial boot:   [x]
> Detect network card:[x]
> Configure network:  [x]
> Detect CD:  [x]
> Load installer modules: [x]
> Detect hard drives: [x]
> Partition hard drives:  [E]
> Install base system:[ ]
> Clock/timezone setup:   [ ]
> User/password setup:[ ]
> Install tasks:  [ ]
> Install boot loader:[ ]
> Overall install:[ ]
> 
> Comments/Problems:
> 
> Hi!
> 
> I got a test enviroment with 2 harddisk drives. I want install Debian
> with RAID, dm-crypt and LVM. I used for the test a virtual machine
> (VirtualBox).
> 
> 
> HDD /dev/sda
> /dev/sda1 - physical volume for RAID
> /dev/sda2 - physical volume for RAID
> 
> HDD /dev/sdb
> /dev/sdb1 - physical volume for RAID
> /dev/sdb2 - physical volume for RAID
> 
> 
> 
> Here are my steps:
> 
> Configure software RAID
> 
> Create MD device: RAID1
> - /dev/sda1
> - /dev/sdb1
> 
> Create MD device: RAID1
> - /dev/sda2
> - /dev/sdb2
> 
> RAID1 device #0 (md0)
> - Use as: Ext3
> - Mount point: /boot
> 
> RAID1 device #1 (md1)
> - Use as: physical volume for encryption
> 
> Configure encrypted volumes
> 
> 
> After this step, the "RAID1 device #0" (md0) is no longer the /boot
> partition. This means the installation will fail.

I can confirm this (at least from a KVM installation). However, I would
not say that the installation will necessarily fail as you still have
the opportunity to (re)define the mount point of md0 after encrypted
volumes have been configured. 
Also, the correct procedure might be to configure all devices (raid,
crypto, etc.) *before* defining mount points. Yet, previously defined
mount points should probably not be discarded by partman.

Thanks for your report.



--
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/20101207123305.4c3b2...@mail.gmail.com

Bug#598668: Fwd: Re: Installation fails on acer aspire one za3

[Denis Laxalde]

reassign 598668 grub-pc
forcemerge 594967 598668
thanks

On Fri, 01 Oct 2010 01:31:41 +0200, Luc Novales wrote:
> During a minimal install no problem, no error, but first boot stop
> only displaying cursor. Grub was installed on usb drive installer.
> Trying to boot from this media, boot stops after  displaying "grub"

This was fixed in grub-installer 1.57.

> After grub install on netbook hdd using rebuild usb drive installer 
> rescue mode, boot fails after "welcome to grub" (no grub rescue 
> possibility).

On Wed, 17 Nov 2010 10:24:19 +0100, Mariusz Białończyk wrote:
> I have exactly same behavior yesterday on this netbook. I suppose the
> problem is with the graphical mode which grub is trying to initialize.
> The graphics chipset is Poulsbo - it is even wrong handled by xorg
> (i mean out of the box) so maybe grub have also problems with it.

This occurs with recent versions of grub-pc apparently (see #594967).

Thank you both for your reports and comments and for your time testing
the Debian Installer.



--
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/20101207145716.35bf3...@mail.gmail.com

Bug#581687: Device naming scheme changed from GRUB to GRUB2

[Denis Laxalde]

On Thu, 16 Dec 2010 05:58:05 +0100, Christian PERRIER wrote:
> Quoting Karsten Loeft (karstenlo...@yahoo.de):
> > I noticed that, as of installer beta2, this bug is still not fixed.
> > I am not an expert, but yet I would like to draw your attention to
> > the fact that from lenny to squeeze Debian switched from using GRUB
> > to using GRUB2. GRUB2 now uses a different device numbering scheme
> > than GRUB used. It seems to me that the explanation in the
> > installer was written for GRUB and was forgotten to be rewritten in
> > order to reflect the different device numbering scheme of GRUB2. 

Grub2 uses a different numbering scheme for partitions, not devices.
See:
http://grub.enbug.org/Manual#head-db861a16884db1252847a6ce554b625974134d7e

> The template is:
> 
> Template: grub-installer/bootdev
> Type: string
> # :sl2:
> _Description: Device for boot loader installation:
>  You need to make the newly installed system bootable, by installing
>  the GRUB boot loader on a bootable device. The usual way to do this
> is to install GRUB on the master boot record of your first hard
> drive. If you prefer, you can install GRUB elsewhere on the drive, or
> to another drive, or even to a floppy.
>  .
>  The device can be specified using GRUB's "(hdn,m)" notation, or as a
> device in /dev. Below are some examples:
>   - "(hd0)" or "/dev/hda" will install GRUB to the master boot record
> of your first hard drive (IDE);
>   - "(hd0,1)" or "/dev/hda2" will use the second partition of your
> first IDE drive;
>   - "(hd2,4)" or "/dev/sdc5" will use the first extended partition of
> your third drive (SCSI here);
>   - "(fd0)" or "/dev/fd0" will install GRUB to a floppy.
> 
> 
> I'm not 100% sure of what should be changedpreferrably in a way
> that doesn't affect translations. My understanding is that we should
> replace (hd0,1) by (hd0,2) and (hd2,4) by (hd2,5) as only partitions
> numbering changed. Am I right?

So, I would say yes, you're right.



-- 
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/20101216094556.7542c...@mail.gmail.com

Bug#609887: installation-reports: squeeze preseed recipe (partitioning) does not provide the same layout as lenny

[Denis Laxalde]

reassign 609887 partman-base
reassign 608906 partman-base
forcemerge 597005 608906 609887
thanks


On Thu, 13 Jan 2011 16:17:12 +0100, Marc Leeman wrote:
> I issued the following bug against the debian-installer; but I now
> noticed that bugs were requested against installation-reports for
> squeeze.
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608906

Your previous report was sufficient. Actually, this was already
reported, see #597005.
This issue may be due to some change in the alignment settings in the
installer. Does it help if you try to preseed "partman/alignment" to
something else than "optimal" (e.g. "cylinder" or "minimal")?

-- 
Denis Laxalde



-- 
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/20110113125308.2efff...@mail.gmail.com

Bug#509186: Closing 509186

[Denis Laxalde]

reassign 509186 debian-installer
forcemerge 435769 509186
block 435769 by 130550
thanks

On Mon, 24 Jan 2011 15:05:39 +0100, Didier 'OdyX' Raboud wrote:
> As for the issue, I think d-i should check for available space in /var before
> launching the actual download of packages.

This issue has been reported in #435769 already, although the correct
d-i component may be tasksel.
If I understand correctly, tasksel uses aptitude which apparently does
not handle low disk-space situations properly, see #130550.



-- 
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/20110124100222.423e6...@mail.gmail.com

Bug#611839: non-free network drivers not really supported with netinstall of squeeze/rc2

[Denis Laxalde]

On Thu, 03 Feb 2011 07:59:32 +0100, Armin Fuerst wrote:
> What do you mean with "images with firmware included"? There is only
> one netinstall not providing non-free firmware.

See here:

  http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/



-- 
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/20110203084122.33759...@mail.gmail.com

Bug#612411: debian-6.0.0-i386-netinst.iso installs KDE by default

[Denis Laxalde]

tags 612411 + moreinfo
thanks

On Tue, 08 Feb 2011 13:05:08 +0100, H.A.J. Koster wrote:
> Package: debian-installer
> 
> The Debian Installer (or the "tasksel" task) on the above noted version 
> installs KDE as the default desktop environment, while not being a 
> "kde"-specific version. That default should be Gnome.

Which version exactly?



-- 
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/20110208095143.3a0bb...@mail.gmail.com

Bug#612436: installation-reports: Erroneously warns about a missing NewWorld boot partition

[Denis Laxalde]

reassign 612436 partman-newworld
forcemerge 248437 612436
tags 248437 + confirmed
thanks

On Tue, 08 Feb 2011 15:21:09 +0100, Adrian Lang wrote:
> Package: installation-reports
> Severity: minor
> Tags: squeeze d-i
> 
> I used expert installation method since I wanted to encrypt my installation.
> partman chose useful defaults for partitions, but warned after accepting the
> partition configuration with the following text: "No Newworld boot partition
> was found, the yaboot boot laoder requires an apple_bootstrap partition at
> least 819200 byes in size using the HFS macintosh file system". I ignored the
> warning since there was such a partition present. No further problems occured,
> installation runs fine.

Thanks for your report. There seems to be an old bug in
partman-newworld which triggers this erroneous warning message.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=248437;msg=48



-- 
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/20110208103901.4e1b9...@mail.gmail.com

Bug#612411: debian-6.0.0-i386-netinst.iso installs KDE by default

[Denis Laxalde]

tags 612411 + moreinfo + unreproducible
thanks

On Tue, 08 Feb 2011 16:55:01 +0100, H.A.J. Koster wrote:
> That /debian-6.0.0-i386-netinst.iso/ may just be a wrongly-labeled 
> KDE-specific iso.
> Someone on the Debian User Forum said that his non-specific 
> businesscard.iso installed
> Gnome by default...

This is a netinstall image, which does not contain desktop packages.
Tasksel is in charge of selecting the proper desktop.
Actually, I just tried and could not reproduce this.

Can you check the image you downloaded with MD5SUMS?
From  you
should get:
2840eea06e9cdd2e125f32cefa25fa1d debian-6.0.0-i386-netinst.iso



--
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/20110208120900.1da57...@mail.gmail.com

Bug#612411: debian-6.0.0-i386-netinst.iso installs KDE by default

[Denis Laxalde]

[Just forwarding your message — Please keep the bug CC'ed next times.] 

On Tue, 08 Feb 2011 19:29:13 +0100, H.A.J. Koster wrote:
> On 08-02-11 18:09, Denis Laxalde wrote:
> > tags 612411 + moreinfo + unreproducible
> > thanks
> >
> > On Tue, 08 Feb 2011 16:55:01 +0100, H.A.J. Koster wrote:
> >> That /debian-6.0.0-i386-netinst.iso/ may just be a wrongly-labeled
> >> KDE-specific iso.
> >> Someone on the Debian User Forum said that his non-specific
> >> businesscard.iso installed
> >> Gnome by default...
> > This is a netinstall image, which does not contain desktop packages.
> > Tasksel is in charge of selecting the proper desktop.
> > Actually, I just tried and could not reproduce this.
> >
> > Can you check the image you downloaded with MD5SUMS?
> > From<http://cdimage.debian.org/debian-cd/6.0.0/i386/iso-cd/MD5SUMS>  you
> > should get:
> > 2840eea06e9cdd2e125f32cefa25fa1d debian-6.0.0-i386-netinst.iso
> >
> Yes, that's what I get as well.
> 
> Somebody on the Debian User Forums pointed out that I had installed this
> netinst.iso to a USB-key with unetbootin, and that this could cause the 
> problem.
> I can't imagine that to be true, but just to be safe I'll dd the image 
> to the USB-key
> and try again. Stay tuned.
> 
> Regards,
> 
> Henk Koster



--
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/20110208144055.25602...@mail.gmail.com

Bug#612505: installation-reports: no sound and no alsaconf on AMD64

[Denis Laxalde]

On Wed, 9 Feb 2011 07:04:15 +0100, Christian PERRIER wrote:
> Quoting frox (mazda...@gmail.com):
> > Package: installation-reports
> > Severity: important
> > 
> > there is no sound available. all seamsto be good, no errors or something. 
> > e.g.
> > mplayer runs normaly but i can't hear any sound.  i can't do 'alsaconf' 
> > becaus
> > it is not installed. alsa-util is installed.
> 
> 
> Well, this bug probably doesn't directly belong to the installer (who
> apparently did its job properly) but more to whatever is responsible
> for dealing with sound nowadays (this has always been black  magic for
> me and Linux had so many difference interface for sound that I'm
> always lost with it on my personal systems...).
> 
> Anyone with a clearer idea than me?

According to:
| lspci -knn: 05:05.0 Multimedia audio controller [0401]: ESS Technology ES1969 
Solo-1 Audiodrive [125d:1969] (rev 01)
| lspci -knn:   Subsystem: ESS Technology Device [125d:]
and , the module snd-es1938.ko
should be used. But it's does not appear to be loaded. I don't know
whether the Linux kernel or alsa is faulty here, though.



-- 
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/20110209085705.61bfb...@mail.gmail.com

Bug#606365: installation-reports

[Denis Laxalde]

tags 606365 + moreinfo
thanks

On Wed, 8 Dec 2010 16:11:24 -0200, José Roberto wrote:
> Package: installation-reports
> 
> Boot method: .iso in VirtualBox
> Image version: 
> http://caesar.acc.umu.se/cdimage/daily-builds/daily/arch-latest/kfreebsd-amd64/iso-cd/debian-testing-kfreebsd-amd64-netinst.iso
> Date: 08-Dec-2010 16:30
> 
> 
> Machine: VirtualBox
> Processor:
> Memory: 512M
> Partitions:
> 
> 
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> 
> Initial boot:   [O]
> Detect network card:[O]
> Configure network:  [O]
> Detect CD:  [O]
> Load installer modules: [O]
> Detect hard drives: [O]
> Partition hard drives:  [O]
> Install base system:[O]
> Clock/timezone setup:   [O]
> User/password setup:[O]
> Install tasks:  [E]
> Install boot loader:[E]
> Overall install:[E]
> 
> Comments/Problems:
> I preferred to send for you 2 screens about error I got.

So this seems to be a mirror issue ("mirror does not support the
specified release (squeeze)"). Could you try again now that Squeeze has
been released?



--
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/2011020204.7b074...@mail.gmail.com

Bug#615948: Installation report

[Denis Laxalde]

reassign 615948 debootstrap
forcemerge 614315 615948
thanks

Lorenzo Bernardi  wrote [2011-03-01]:
> I cannot install the base system with the error:
> 
> Install the base system
> Debootstrap Error
> Invalid Release File: no entry for main/binary-386/Packages
> 
> While at least the main/binary-386/Packages exist on the cdrom.
> 
> It looks like there was a problem in md5sum and sha-1 checksum in 
> deboostrap but I cannot really check this while installing the
> computer.

Yes, this problem is known. See #615948.

Thanks for your report.

-- 
Denis Laxalde



-- 
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/20110301084041.22084...@mail.gmail.com

Bug#611108: installation-report: Succesful install with some remarks

[Denis Laxalde]

tags 611108 +moreinfo
clone 611108 -1
reassign -1 save-logs
retitle -1 installer should not suggest to save logs to a media mounted 
read-only
severity -1 wishlist
tags -1 d-i
thanks

Matthijs Kooijman a écrit :
> Package: installation-reports
> Version: 2.44
> Severity: normal
[…]
> 
> I did an (non-graphical) expert install.
> 
> Partitioning was done manually, since I needed to thrash an existing
> recovery partition first. After that, I created a single big LVM
> partition and proceeded to the LVM setup. When creating a new volume
> group, I was asked what physical volumes to include in that list. This
> list offered all partitions in the system, not just the ones I had
> marked as LVM physical volumes (so also the existing ntfs
> filesystems and I think also the partition on the install USB disk,
> though I'm not 100% sure about that). I would have expected to get a
> list of just the LVM PVs. I guess this is a feature so you can convert
> any partition to an LVM PV at a later stage, but right now, the
> interface isn't quite clear about this. Also, the partition that I did
> mark as an LVM PV in the previous step was not marked as such, so I
> needed to doublecheck that I was selecting the right one.

This looks like #612850: "VG creation dialog should show only PVs".

> After doing the install software step, I left my machine unattended
> for a few hours. When I got back and started on the install grub
> step, my network connectivity was broken. It seems that the
> DHCP-obtained address was no longer set on eth0. The DHCP client was
> still running according to "ps". Also, /etc/resolv.conf was still
> ok.  Unplugging my ethernet cable showed a "Link down" in dmesg, but
> plugging it back in didn't show a "Link up" message (though the led
> on the ethernet port did light up). Rerunning the "Configure the
> network" step fixed my connectivity and allowed me to finish the
> installation. This was all using an Intel 82577LM network adapter.

Could you provide us with the installer logs so that somebody can
investigate further?
This may be a lease problem. For instance see #596667
(http://bugs.debian.org/596667).

> Finally, I tried to save the debug logs before finishing the
> installation. This step suggested to save the logs to /hd-media, but
> that failed because /hd-media is mounted read-only. Saving the logs to
> /target worked, but perhaps the installer shouldn't suggest /hd-media
> then?

I guess this concerns save-logs, cloning and reassigning accordingly.

Thank you for your report.

-- 
Denis Laxalde



--
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/2011032604.141d0...@schloss.campus.mcgill.ca

Bug#611108: installation-report: Succesful install with some remarks

[Denis Laxalde]

tags 611108 -moreinfo
reassign 611108 debian-installer
forcemerge 596667 611108
thanks

Matthijs Kooijman a écrit :
> > > After doing the install software step, I left my machine unattended
> > > for a few hours. When I got back and started on the install grub
> > > step, my network connectivity was broken. It seems that the
> > > DHCP-obtained address was no longer set on eth0. The DHCP client was
> > > still running according to "ps". Also, /etc/resolv.conf was still
> > > ok.  Unplugging my ethernet cable showed a "Link down" in dmesg, but
> > > plugging it back in didn't show a "Link up" message (though the led
> > > on the ethernet port did light up). Rerunning the "Configure the
> > > network" step fixed my connectivity and allowed me to finish the
> > > installation. This was all using an Intel 82577LM network adapter.
> > 
> > Could you provide us with the installer logs so that somebody can
> > investigate further?
> > This may be a lease problem. For instance see #596667
> > (http://bugs.debian.org/596667).
> 
> I've attached /install/syslog. The few hours of leaving the installer
> unattended happens around line 7600 (Jan 24 22:42 until Jan 25 09:01).

Quoting the syslog:
[…]
> Jan 24 20:06:14 main-menu[443]: (process:4529): Lease of 192.168.1.43 
> obtained, lease time 28800
[…]
> Jan 24 22:42:41 pkgsel: finishing up
> Jan 25 09:01:59 main-menu[443]: INFO: Menu item 'grub-installer' selected
> Jan 25 09:01:59 grub-installer: info: architecture: amd64/generic
> Jan 25 09:02:00 in-target: Reading package lists...
> Jan 25 09:02:00 in-target: 
> Jan 25 09:02:00 in-target: Building dependency tree...
> Jan 25 09:02:00 in-target: 
> Jan 25 09:02:00 in-target: Reading state information...
> Jan 25 09:02:00 in-target: 
> Jan 25 09:02:00 in-target: The following extra packages will be installed:
> Jan 25 09:02:00 in-target:   os-prober
> Jan 25 09:02:00 in-target: Suggested packages:
> Jan 25 09:02:00 in-target:   multiboot-doc grub-emu xorriso
> Jan 25 09:02:00 in-target: The following NEW packages will be installed:
> Jan 25 09:02:00 in-target:   grub-common os-prober
> Jan 25 09:02:56 in-target: 0 upgraded, 2 newly installed, 0 to remove and 0 
> not upgraded.
> Jan 25 09:02:56 in-target: Need to get 23.9 kB/1,823 kB of archives.
> Jan 25 09:02:56 in-target: After this operation, 4,415 kB of additional disk 
> space will be used.
> Jan 25 09:02:56 in-target: Err http://mirrors.nl.kernel.org/debian/ 
> squeeze/main os-prober amd64 1.42
> Jan 25 09:02:56 in-target:   Something wicked happened resolving 
> 'mirrors.nl.kernel.org:http' (-5 - No address associated with hostname)
> Jan 25 09:02:56 in-target: Failed to fetch 
> http://mirrors.nl.kernel.org/debian/pool/main/o/os-prober/os-prober_1.42_amd64.deb
>   Something wicked happened resolving 'mirrors.nl.kernel.org:http' (-5 - No 
> address associated with hostname)
> Jan 25 09:02:56 in-target: E: Unable to fetch some archives, maybe run 
> apt-get update or try with --fix-missing?
[…]
> Jan 25 09:09:23 main-menu[443]: INFO: Menu item 'grub-installer' succeeded 
> but requested to be left unconfigured.
> Jan 25 09:09:27 main-menu[443]: INFO: Menu item 'netcfg' selected
> Jan 25 09:09:27 netcfg[13035]: INFO: eth0 is connected. (MII)
> Jan 25 09:09:27 netcfg[13035]: INFO: found link on interface eth0, making it 
> the default.
> Jan 25 09:09:30 kernel: [44141.802281] lo: Disabled Privacy Extensions
> Jan 25 09:09:30 kernel: [44141.83] e1000e :00:19.0: irq 32 for 
> MSI/MSI-X
> Jan 25 09:09:30 kernel: [44141.895660] e1000e :00:19.0: irq 32 for 
> MSI/MSI-X
> Jan 25 09:09:30 kernel: [44141.897463] ADDRCONF(NETDEV_UP): eth0: link is not 
> ready
> Jan 25 09:09:32 kernel: [44143.511309] e1000e: eth0 NIC Link is Up 10 Mbps 
> Full Duplex, Flow Control: RX
> Jan 25 09:09:32 kernel: [44143.511313] :00:19.0: eth0: 10/100 speed: 
> disabling TSO
> Jan 25 09:09:32 kernel: [44143.514254] ADDRCONF(NETDEV_CHANGE): eth0: link 
> becomes ready
> Jan 25 09:09:34 udhcpc: Got IP 192.168.1.43 (using eth0) and routing through 
> 192.168.1.254
> Jan 25 09:09:36 netcfg[13035]: INFO: DHCP hostname: "grubby"
> Jan 25 09:09:42 netcfg[13035]: INFO: Detected eth0 as a hotpluggable device
> Jan 25 09:09:42 main-menu[443]: (process:13034): udhcpc (v1.17.1) started
> Jan 25 09:09:42 main-menu[443]: (process:13034): Sending discover...
> Jan 25 09:09:42 main-menu[443]: (process:13034): Sending discover...
> Jan 25 09:09:42 main-menu[443]: (process:13034): Sending select for 
> 192.168.1.43...
> Jan 25 09:09:42 main-menu[443]: (process:13034): L

Bug#621753: debian-installer: screen title says "Configuring man-db" instead of "Configuring grub"

[Denis Laxalde]

Miguel Figueiredo a écrit :
> > Not sure what the correct title should be, but "Configuring man-db"
> > seems odd…
> 
> I've just tried debian-6.0.1a-amd64-i386-netinst.iso (standard
> install, text-mode) and it's fixed on this version. Can you try
> 6.0.1a ?

That's the one I used, in graphical mode though.

-- 
Denis Laxalde



--
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/20110410094844.7e4f0...@gmail.com

Re: kernel panic on startup

[Denis Laxalde]

Pedro Larroy a écrit :
> Which is the correct package name to submit this kind of bugs?

It has already been reported, see: http://bugs.debian.org/623710

Cheers.

-- 
Denis


--
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/20110427101926.3fe38...@schloss.campus.mcgill.ca

Bug#672140: Processed: Re: [Pkg-utopia-maintainers] Bug#672140: prompts for root passwords on a sudo-only system

[Denis Laxalde]

Christian PERRIER a écrit :

Reassigning to the right D-I component.

However, in user-setup-apply:

 if [ -e $ROOT/etc/sudoers ]; then
 # Test if we can add the user to the sudo group
 # (possible if sudo>= 1.7.2-2 is installed on the 
target system)
 # If we can, do it this way, otherwise add the user to 
sudoers
 # See #597239
 if ! $log $chroot $ROOT adduser "$USER" sudo>/dev/null 
2>&1; then
 echo "$USER ALL=(ALL) ALL">>  $ROOT/etc/sudoers
 fi
 else
 # sudo failed to install, system won't be usable
 exit 1
 fi


In short, according to this code, this is already implemented, as of
user-setup 1.34, assuming the sudo group exists at the time this is
done. Adding the sudo user to sudoers is only a fallback.


I just installed a fresh wheezy system without a root account and the 
first user is indeed in the sudo group. And network-manager does not ask 
for the root password to setup a wireless connection. So I'd say that 
there's no bug after all...


--
Denis Laxalde


--
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/503a8551.2030...@laxalde.org