date:20130721

Bug#717534: partconf: Drop reiserfs support

2013-07-21 Thread Cyril Brulebois

Source: partconf
Version: 1.42
Severity: important

Hi,

since reiserfs got dropped, various d-i components need to drop support
for it. Most of the changes[1] should already be in the relevant git
repositories, but partconf still needs updating.

 1. Hopefully the documentation under doc/devel/internals in
src:debian-installer should cover most of them.

Mraw,
KiBi.


-- 
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/20130722015940.9474.18238.reportbug@arya

Processed: Re: Bug#717511: Kernel does not start up on Pegasos-2

2013-07-21 Thread Debian Bug Tracking System

Processing control commands:

> notfound 717511 yaboot-installer/1.1.26
Bug #717511 {Done: Milan Kupcevic } 
[yaboot-installer] Kernel does not start up on Pegasos-2
No longer marked as found in versions yaboot-installer/1.1.26.

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


--
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.b717511.13744572123131.transcr...@bugs.debian.org

Bug#717511: Kernel does not start up on Pegasos-2

2013-07-21 Thread Milan Kupcevic


Control: notfound 717511 yaboot-installer/1.1.26

On 07/21/2013 08:49 PM, Ben Hutchings wrote:

On Sun, 2013-07-21 at 20:36 -0400, Milan Kupcevic wrote:

Control: notfound -1 yaboot-installer/1.1.26

On 07/21/2013 04:55 PM, Ben Hutchings wrote:

Control: reassign -1 yaboot-installer 1.1.26

On Mon, 2013-07-22 at 00:38 +0400, Pavel Fedin wrote:
[...]

   So,  it's  not  kernel's  fault. It seems to be installer fault which
does  not generate correct vmlinuz image when not using separate /boot
partition.  vmlinux,  i  know,  is another thing. It's a "plain" image
meant to be ran from GRUB or yaboot. It cannot be run from OFW.
   So,  we  can  close  this,  probably with a notification to Installer
guys.


There is no need to close it.  I'm reassigning to the relevant part of
the installer.




The particular partition/file-system layout reported in this bug report
cannot work.

This platform does not have a boot loader at all.


Sorry, I misunderstood.

[...]

Installer correctly creates ext2 boot partition and ext4 root partition.

[...]

Then how did this go wrong?



User did not let installer to create default partition layout but 
manually created incorrect one, or installed on a previously created 
partitions and used ext4 and ext3 file-systems.


Milan


--
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/51ec8996.8060...@physics.harvard.edu

Debian installer build: failed or old builds

2013-07-21 Thread Daily build aggregator

Debian installer build overview
---

Failed or old builds:

* FAILED BUILD: amd64 Jul 22 00:03 buildd@barber build_cdrom_isolinux 

http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_isolinux.log

* FAILED BUILD: amd64 Jul 22 00:03 buildd@barber build_cdrom_gtk 

http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_gtk.log

* FAILED BUILD: amd64 Jul 22 00:03 buildd@barber build_cdrom-xen 

http://d-i.debian.org/daily-images/amd64/daily/build_cdrom-xen.log

* FAILED BUILD: amd64 Jul 22 00:03 buildd@barber build_netboot 
http://d-i.debian.org/daily-images/amd64/daily/build_netboot.log

* FAILED BUILD: amd64 Jul 22 00:03 buildd@barber build_netboot-gtk 

http://d-i.debian.org/daily-images/amd64/daily/build_netboot-gtk.log

* FAILED BUILD: amd64 Jul 22 00:03 buildd@barber build_netboot-xen 

http://d-i.debian.org/daily-images/amd64/daily/build_netboot-xen.log

* FAILED BUILD: armel Jul 21 08:09 buildd@ancina build_iop32x_netboot 

http://d-i.debian.org/daily-images/armel/daily/build_iop32x_netboot.log

* FAILED BUILD: armel Jul 21 08:09 buildd@ancina 
build_iop32x_network-console_glantank 

http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_glantank.log

* FAILED BUILD: armel Jul 21 08:10 buildd@ancina 
build_iop32x_network-console_n2100 

http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_n2100.log

* FAILED BUILD: armel Jul 21 08:11 buildd@ancina 
build_iop32x_network-console_ss4000e 

http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_ss4000e.log

* FAILED BUILD: armel Jul 21 08:11 buildd@ancina build_kirkwood_netboot 

http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot.log

* FAILED BUILD: armel Jul 21 08:12 buildd@ancina build_kirkwood_netboot-gtk 

http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot-gtk.log

* FAILED BUILD: armel Jul 21 08:12 buildd@ancina build_kirkwood_network-console 

http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_network-console.log

* FAILED BUILD: armel Jul 21 08:13 buildd@ancina build_orion5x_network-console 

http://d-i.debian.org/daily-images/armel/daily/build_orion5x_network-console.log

* FAILED BUILD: armel Jul 21 08:13 buildd@ancina build_versatile_netboot 

http://d-i.debian.org/daily-images/armel/daily/build_versatile_netboot.log

* FAILED BUILD: armhf Jul 21 09:39 buildd@hasse build_mx5_netboot 

http://d-i.debian.org/daily-images/armhf/daily/build_mx5_netboot.log

* FAILED BUILD: armhf Jul 21 09:39 buildd@hasse build_mx5_network-console 

http://d-i.debian.org/daily-images/armhf/daily/build_mx5_network-console.log

* FAILED BUILD: armhf Jul 21 09:40 buildd@hasse build_mx5_netboot-gtk 

http://d-i.debian.org/daily-images/armhf/daily/build_mx5_netboot-gtk.log

* FAILED BUILD: armhf Jul 21 09:40 buildd@hasse build_vexpress_netboot 

http://d-i.debian.org/daily-images/armhf/daily/build_vexpress_netboot.log

* FAILED BUILD: i386 Jul 22 00:02 buildd@biber build_cdrom_isolinux 

http://d-i.debian.org/daily-images/i386/daily/build_cdrom_isolinux.log

* FAILED BUILD: i386 Jul 22 00:03 buildd@biber build_cdrom_gtk 

http://d-i.debian.org/daily-images/i386/daily/build_cdrom_gtk.log

* FAILED BUILD: i386 Jul 22 00:03 buildd@biber build_cdrom-xen 

http://d-i.debian.org/daily-images/i386/daily/build_cdrom-xen.log

* FAILED BUILD: i386 Jul 22 00:03 buildd@biber build_netboot 
http://d-i.debian.org/daily-images/i386/daily/build_netboot.log

* FAILED BUILD: i386 Jul 22 00:03 buildd@biber build_netboot-gtk 

http://d-i.debian.org/daily-images/i386/daily/build_netboot-gtk.log

* FAILED BUILD: i386 Jul 22 00:03 buildd@biber build_netboot-xen 

http://d-i.debian.org/daily-images/i386/daily/build_netboot-xen.log

* OLD BUILD:ia64 May 26 00:12 buildd@alkman build_cdrom 
http://d-i.debian.org/daily-images/ia64/daily/build_cdrom.log

* OLD BUILD:ia64 May 26 00:16 buildd@alkman build_netboot 
http://d-i.debian.org/daily-images/ia64/daily/build_netboot.log

* FAILED BUILD: kfreebsd-amd64 Jul 22 00:32 buildd@fano build_netboot 

http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log

* FAILED BUILD: kfreebsd-amd64 Jul 22 00:33 buildd@fano build_netboot-9 

http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-9.log

* FAILED BUILD: kfreebsd-amd64 Jul 22 00:36 buildd@fano build_netboot-gtk 

http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-gtk.log

* FAILED BUILD: kfreebsd-amd64 Jul 22 00:39 buildd

Bug#717511: marked as done (Kernel does not start up on Pegasos-2)

2013-07-21 Thread Debian Bug Tracking System

Your message dated Sun, 21 Jul 2013 20:36:41 -0400
with message-id <51ec7e99.9030...@physics.harvard.edu>
and subject line Re: Bug#717511: Kernel does not start up on Pegasos-2
has caused the Debian Bug report #717511,
regarding Kernel does not start up on Pegasos-2
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.)


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

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

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

Control: notfound -1 yaboot-installer/1.1.26

On 07/21/2013 04:55 PM, Ben Hutchings wrote:

Control: reassign -1 yaboot-installer 1.1.26

On Mon, 2013-07-22 at 00:38 +0400, Pavel Fedin wrote:
[...]

  So,  it's  not  kernel's  fault. It seems to be installer fault which
does  not generate correct vmlinuz image when not using separate /boot
partition.  vmlinux,  i  know,  is another thing. It's a "plain" image
meant to be ran from GRUB or yaboot. It cannot be run from OFW.
  So,  we  can  close  this,  probably with a notification to Installer
guys.


There is no need to close it.  I'm reassigning to the relevant part of
the installer.




The particular partition/file-system layout reported in this bug report 
cannot work.


This platform does not have a boot loader at all. Firmware knows how to 
load kernel directly from affs1, ext2 or older implementations of ext3 
file systems. It is possible to tweak options while creating ext3 with 
current tools to make it work, but it is not worth the trouble.


In practice this means you have to have ext2 boot partition, to place 
the kernel onto, for this machine to boot.


Installer correctly creates ext2 boot partition and ext4 root partition. 
The identical mkinitramfs and mkvmlinuz commands are issued during 
installation as those during kernel upgrades. The generated vmlinuz 
loads and kernel works fine.


Closing this bug report. This is not a bug.


Milan--- End Message ---

Bug#717511: Kernel does not start up on Pegasos-2

2013-07-21 Thread Ben Hutchings

On Sun, 2013-07-21 at 20:36 -0400, Milan Kupcevic wrote:
> Control: notfound -1 yaboot-installer/1.1.26
> 
> On 07/21/2013 04:55 PM, Ben Hutchings wrote:
> > Control: reassign -1 yaboot-installer 1.1.26
> >
> > On Mon, 2013-07-22 at 00:38 +0400, Pavel Fedin wrote:
> > [...]
> >>   So,  it's  not  kernel's  fault. It seems to be installer fault which
> >> does  not generate correct vmlinuz image when not using separate /boot
> >> partition.  vmlinux,  i  know,  is another thing. It's a "plain" image
> >> meant to be ran from GRUB or yaboot. It cannot be run from OFW.
> >>   So,  we  can  close  this,  probably with a notification to Installer
> >> guys.
> >
> > There is no need to close it.  I'm reassigning to the relevant part of
> > the installer.
> >
> 
> 
> The particular partition/file-system layout reported in this bug report 
> cannot work.
> 
> This platform does not have a boot loader at all.

Sorry, I misunderstood.

[...]
> Installer correctly creates ext2 boot partition and ext4 root partition. 
[...]

Then how did this go wrong?

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

Bug#714710: dpkg: when installed from live usb/cd /sbin/start-stop-daemon is empty shell script

2013-07-21 Thread Edwin Fukunaga

It looks like the usb-hdd images also have this issue.  If I boot with
the image from

 
http://live.debian.net/cdimage/release/6.0.7/amd64/usb-hdd/debian-live-6.0.7-amd64-gnome-desktop.img

then /sbin/start-stop-daemon is again empty:

 $ cat /sbin/start-stop-daemon
 #!/bin/sh

 exit 0
 $

@Emanoil: It looks like there is no .deb file for dpkg included in the
netboot or usb-hdd images.  I get no output from  find | grep dpkg ,
and the pool/main/d directory doesn't have a dpkg subdirectory.
Actually, maybe the /sbin/start-stop-daemon is being changed by
live-build, because it is the same in the image as it is after booting
(using  unsquashfs -lls filesystem.squashfs /sbin/start-stop-daemon ).

By the way, the iso-hybrid image does not seem to have this issue, at
least the gnome-desktop one from


http://live.debian.net/cdimage/release/6.0.7/amd64/iso-hybrid/debian-live-6.0.7-amd64-gnome-desktop.iso


Thanks,
Edwin



On Sun, Jul 7, 2013 at 11:44 PM, Emanoil Kotsev  wrote:
> Hi
> thanks Edwin for reporting the details on your side.
> This is exactly what I have experienced in my case and spent about 4-5h
> looking for an issue with nfs and why it is not mounting remote dir, why
> portmap was not running etc.
> I did check the current 7.x installer debian-7.1.0-amd64-netinst.iso but it
> looks ok there in the dpkg package.
> In debian-testing-amd64-businesscard.iso there is no dpkg package.
> I need to check the backup disks and usb of installation and the notes to
> find out what I have used for setting up the machine but no time left
> unfortunately. I think the machine was installed in Feb or Jan this year.
>
> @Edwin: Can you check if the included dpkg package has this inside
> /sbin/start-stop-daemon in binary, basically I'm wondering if there is a
> script somewhere which overwrites something in /sbin, which would be
> dangerous
> I mount -o loop debianiso and then  find | grep dpkg followed by mkdir
> tmp && dpkg -x dpkg...deb tmp
>
> regards
> 
> From: Guillem Jover 
> To: deloptes ; 714...@bugs.debian.org
> Cc: live-ima...@packages.debian.org
> Sent: Tuesday, July 2, 2013 11:42 AM
> Subject: Re: Bug#714710: dpkg: when installed from live usb/cd
> /sbin/start-stop-daemon is empty shell script
>
> Control: reassign -1 live-images
>
> Hi!
>
> [ I got confirmation off-list this is with official Live images, but
>   feel free to re-reassign as I don't really know what the culprit is. ]
>
> On Tue, 2013-07-02 at 08:29:19 +0200, Guillem Jover wrote:
>> On Tue, 2013-07-02 at 02:33:36 +0200, deloptes wrote:
>> > Package: dpkg
>> > Version: 1.15.8.13
>> > Severity: important
>> >
>> > When installed from live usb/cd /sbin/start-stop-daemon is empty shell
>> > script
>> > This results in strange behaviour of start/stop services like nfs
>> >
>> > I read a whole bunch of issues related to nfs (rpc.statd not running)
>> > While having another machine with same setup and nfs working I excluded
>> > the possibility of being related to some mostly discussed bugs
>> > I noticed that portmap and rpc.statd are simply not starting, because
>> > the start-stop-daemon program was an empty shells script
>> > unfortunately the version reported here was overwritten by dpkg
>> > --reinstall install dpkg, but I hope in this way that other people having
>> > similar issues with daemons not starting properly will solve it easily.
>>
>> This would be an issue with whatever Live USB/CD software you are using.
>> If that's one of the packaged solutions in Debian, then we can reassign
>> the bug report there, otherwise there's not much that can be done, except
>> that you'd need to file such bug report on the project producing those
>> Live images.
>
> Thanks,
> Guillem
>
>


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

Re: Avoiding "warning: jobserver unavailable: using -j1. Add `+' to parent make rule." in src:debian-installer?

2013-07-21 Thread Cyril Brulebois

Cyril Brulebois (2013-06-06):
> Hi,
> 
> src:debian-installer has a few definitions in build/Makefile to
> recurse once or many times depending on a few parameters. That
> currently leads to some:
> | make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make 
> rule.
> 
> Since I suspect we want that to be sequential anyway, I guess we could
> specify -j1 on that rule explicitly (see attached patch), thoughts?

Ping?

> From bde88aec7b74d2d5683e503c607f47d576d998e8 Mon Sep 17 00:00:00 2001
> From: Cyril Brulebois 
> Date: Thu, 6 Jun 2013 22:55:14 +0200
> Subject: [PATCH] Specify -j1 for the submake definition.
> 
> That's what happens anyway, and warnings go away accordingly.
> ---
>  build/Makefile   |2 +-
>  debian/changelog |2 ++
>  2 files changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/build/Makefile b/build/Makefile
> index 54a2fde..9e7833e 100644
> --- a/build/Makefile
> +++ b/build/Makefile
> @@ -108,7 +108,7 @@ endif
>  
>  # Useful command sequences
>  define submake
> -  $(ROOTCMD) $(MAKE) --no-print-directory
> +  $(ROOTCMD) $(MAKE) --no-print-directory -j1
>  endef
>  
>  define recurse_once
> diff --git a/debian/changelog b/debian/changelog
> index 10ff1f8..53aceb5 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -18,6 +18,8 @@ debian-installer (2013) UNRELEASED; urgency=low
>  - doc/i18n/languages.xsl
>* Bump linux kernel version from 3.2.0-4 to 3.9-1.
>* Set DEBIAN_VERSION to just '8'.
> +  * Specify -j1 for the submake definition in build/Makefile; that's what
> +happens anyway, and warnings go away accordingly.
>  
>[ Philipp Kern ]
>* s390(x): Remove the tape image flavour (no longer supported by


-- 
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/20130722001700.ga17...@mraw.org

Processed: dealing with old debian-installer bugs

2013-07-21 Thread Debian Bug Tracking System

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

> reassign 690832 choose-mirror
Bug #690832 [debian-installer] debian-installer: proxy for mirror not updated 
on retry
Bug reassigned from package 'debian-installer' to 'choose-mirror'.
No longer marked as found in versions debian-installer/20120930.
Ignoring request to alter fixed versions of bug #690832 to the same values 
previously set
> reassign 687488 netcfg
Bug #687488 [debian-installer] debian-installer: LIFEBOOK P7120: association 
fails with WPA-PSK but works after installation
Bug reassigned from package 'debian-installer' to 'netcfg'.
Ignoring request to alter found versions of bug #687488 to the same values 
previously set
Ignoring request to alter fixed versions of bug #687488 to the same values 
previously set
> retitle 709319 wheezy 7.1: scanning for more DVDs is confusing
Bug #709319 [debian-installer] Installer bug: amd-64 for 7.0.0.
Changed Bug title to 'wheezy 7.1: scanning for more DVDs is confusing' from 
'Installer bug: amd-64 for 7.0.0.'
> tags 709319 + confirmed
Bug #709319 [debian-installer] wheezy 7.1: scanning for more DVDs is confusing
Added tag(s) confirmed.
> tags 626219 + confirmed
Bug #626219 [debian-installer] Installer could not detect booted USB drive in 
USB3 port
Added tag(s) confirmed.
> reassign 616722 partman-md
Bug #616722 [debian-installer] Add support to give logical name of md device
Bug reassigned from package 'debian-installer' to 'partman-md'.
Ignoring request to alter found versions of bug #616722 to the same values 
previously set
Ignoring request to alter fixed versions of bug #616722 to the same values 
previously set
> reassign 616125 partman-crypto
Bug #616125 [debian-installer] debian-installer: Setting up encryption fails if 
hostname (?) from previous installation is used
Bug reassigned from package 'debian-installer' to 'partman-crypto'.
No longer marked as found in versions debian-installer/20110106.
Ignoring request to alter fixed versions of bug #616125 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
616125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616125
616722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616722
626219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626219
687488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687488
690832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690832
709319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709319
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
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.1374450578966.transcr...@bugs.debian.org

Bug#680675: marked as done (debian-installer: Prompts when InRelease file cannot be downloaded)

2013-07-21 Thread Debian Bug Tracking System

Your message dated Mon, 22 Jul 2013 01:12:11 +0200
with message-id <201307220112.30643.hol...@layer-acht.org>
and subject line dealing with old debian-installer bugs
has caused the Debian Bug report #680675,
regarding debian-installer: Prompts when InRelease file cannot be downloaded
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.)


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

When installing using debian-installer 20120508 wheezy mini.iso netboot image,
and using a mirror that doesn't support InRelease files (squeeze's version of 
approx), during the "Installing the base system" step it prompts with a message 
that the InRelease file cannot be downloaded.

Selecting continue seems to work fine, presumably falling back to debootstrap's 
handling of old-style Release and Release.gpg files.

It seems like debian-installer shouldn't bother to warn the user at that point 
if the fallback methods haven't yet been tried...


live well,
  vagrant


--- End Message ---
--- Begin Message ---
reassign 690832 choose-mirror
reassign 687488 netcfg
retitle 709319 wheezy 7.1: scanning for more DVDs is confusing
tags 709319 + confirmed
tags 626219 + confirmed
reassign 616722 partman-md
reassign 616125 partman-crypto
thanks

Hi,

thank you for submitting bug reports concering debian-installer, much 
appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they have been from a development phase where things were not stable and/or
- they are very old and/or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - and that's often better, as the bug 
log will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
--- End Message ---

Bug#680347: marked as done (No disk found (C602 chipset))

2013-07-21 Thread Debian Bug Tracking System

Your message dated Mon, 22 Jul 2013 01:12:11 +0200
with message-id <201307220112.30643.hol...@layer-acht.org>
and subject line dealing with old debian-installer bugs
has caused the Debian Bug report #680347,
regarding No disk found (C602 chipset)
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.)

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

Package: debian-installer

Hi,

I was trying to install Debian on a new Lenovo S30 system. I downloaded
the file

http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso

(label: Debian GNU/Linux testing "Wheezy" - Official Snapshot amd64
NETINST Binary-1 20120704-09:15)

and started the installer from the CD. Unfortunately, it was unable to
detect any drives.

I did some searching, and found that it seems to not contain the right
drivers for the SAS controller of my system. lspci -v shows

05:00.0 Serial Attached SCSSI controller: Intel Corporation C602
chipset 4-Port SATA Storage Control Unit (rev 06).

When running from a Knoppix CD, I got some line saying 'Kernel driver
in use: isci'. I do not see that line when running the Debian installer.
For reference, lspci -n shows '05:00.0 0107: 8086:1d6b (rev 06)'.

It seems to me that the installer doesn't contain or is unable to load
the isci driver.

Best,
Koen

--- End Message ---
--- Begin Message ---
reassign 690832 choose-mirror
reassign 687488 netcfg
retitle 709319 wheezy 7.1: scanning for more DVDs is confusing
tags 709319 + confirmed
tags 626219 + confirmed
reassign 616722 partman-md
reassign 616125 partman-crypto
thanks

Hi,

thank you for submitting bug reports concering debian-installer, much
appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they have been from a development phase where things were not stable and/or
- they are very old and/or
- they are wishlist but rather special + exotic and not have been acted on for
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll
do if requested) or just file a new one - and that's often better, as the bug
log will be clearer and shorter and not contain cruft.

cheers,
Holger

signature.asc
Description: This is a digitally signed message part.
--- End Message ---

Bug#661833: marked as done (The "Automated Install" is in the "Advanced Options" section of installation disk)

2013-07-21 Thread Debian Bug Tracking System

Your message dated Mon, 22 Jul 2013 01:12:11 +0200
with message-id <201307220112.30643.hol...@layer-acht.org>
and subject line dealing with old debian-installer bugs
has caused the Debian Bug report #661833,
regarding The "Automated Install" is in the "Advanced Options" section of 
installation disk
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.)


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

package: debian-installer

Less experienced users will likely be intimidated and won't look in the 
Advanced

Options section of the installer disk.

The Automated Install option is easier on n00bs. It may make the 
difference between
a successful installation or them running back to windows which of 
course sucks

finally resulting in given n00b becoming yet another computerphobe.

No n00b in their right mind will go to Advanced Options. Therefore 
Automated Install

should be visible in the main menu.


--- End Message ---
--- Begin Message ---
reassign 690832 choose-mirror
reassign 687488 netcfg
retitle 709319 wheezy 7.1: scanning for more DVDs is confusing
tags 709319 + confirmed
tags 626219 + confirmed
reassign 616722 partman-md
reassign 616125 partman-crypto
thanks

Hi,

thank you for submitting bug reports concering debian-installer, much 
appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they have been from a development phase where things were not stable and/or
- they are very old and/or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - and that's often better, as the bug 
log will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
--- End Message ---

Bug#637613: marked as done (base: Terminal can't display Korean when the system locale is Korean.)

2013-07-21 Thread Debian Bug Tracking System

Your message dated Mon, 22 Jul 2013 01:12:11 +0200
with message-id <201307220112.30643.hol...@layer-acht.org>
and subject line dealing with old debian-installer bugs
has caused the Debian Bug report #637613,
regarding base: Terminal can't display Korean when the system locale is Korean.
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.)


-- 
637613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: base
Severity: grave
Tags: d-i l10n
Justification: renders package unusable


When the user selects only Korean language from installer and install only 
standard system
the console can't display Korean messages at all. 

This is very serious problem for Korean users.

The installer must provide console environment that display Korean properly if 
system 
locale is Korean and it's the only language set by the user. 

To fix the problem, user needs to add English locale as super user.

$ sudo dpkg-reconfigure locales
Add en_US.utf-8

Then change English as system locale or set export LANG=en_US.utf-8.

The window messages are unreadable - full of tiny retangles.
Without the knowlede or access to other system, users will unlikely give up or 
reinstall 
the system.

It makes Debian as useless system. When I used to use IBM XT years ago, MS-DOS 
provides
console that handles Korean using bitmap fonts.




-- System Information:
Debian Release: 6.0.2
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'testing'), (500, 'stable-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---
reassign 690832 choose-mirror
reassign 687488 netcfg
retitle 709319 wheezy 7.1: scanning for more DVDs is confusing
tags 709319 + confirmed
tags 626219 + confirmed
reassign 616722 partman-md
reassign 616125 partman-crypto
thanks

Hi,

thank you for submitting bug reports concering debian-installer, much 
appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they have been from a development phase where things were not stable and/or
- they are very old and/or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - and that's often better, as the bug 
log will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
--- End Message ---

Bug#620309: marked as done (installation-reports: "fakeroot make rebuild_netboot" has unmet dependencies)

2013-07-21 Thread Debian Bug Tracking System

Your message dated Mon, 22 Jul 2013 01:12:11 +0200
with message-id <201307220112.30643.hol...@layer-acht.org>
and subject line dealing with old debian-installer bugs
has caused the Debian Bug report #620309,
regarding installation-reports: "fakeroot make rebuild_netboot" has unmet 
dependencies
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.)


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


I wanted to install debian remotely on my (next door) server
by following these instructions:

http://wiki.debian.org/DebianInstaller/Remote

When I do "fakeroot make rebuild_netboot" it doesn't find a
bunch of packages - see the end of the shell log. Some 
editing was done with the mc editor and so is invisible in 
the log.

--- shell log -
bernhard@s:~$ apt-get source debian-installer
Reading package lists... Done
Building dependency tree   
Reading state information... Done
NOTICE: 'debian-installer' packaging is maintained in the 'Git' version control 
system at:
git://git.debian.org/d-i/debian-installer.git
Need to get 1,368 kB of source archives.
Get:1 ftp://debian.sil.at/debian/ squeeze/main debian-installer 
20110106+squeeze1 (dsc) [3,306 B]
Get:2 ftp://debian.sil.at/debian/ squeeze/main debian-installer 
20110106+squeeze1 (tar) [1,365 kB]
Fetched 1,368 kB in 1s (1,061 kB/s)   
dpkg-source: info: extracting debian-installer in 
debian-installer-20110106+squeeze1
dpkg-source: info: unpacking debian-installer_20110106+squeeze1.tar.gz
bernhard@s:~$ 
bernhard@s:~$ mc
No protocol specified

bernhard@s:/data/home/bernhard/mail$ cat >/tmp/mypreseed.cfg
 d-i debian-installer/localestring en_US
 d-i debconf/priority   select critical
 d-i auto-install/enabled   boolean true
 d-i netcfg/choose_interfaceselect eth0
 d-i netcfg/disable_dhcpboolean true
 d-i netcfg/get_nameservers string 192.168.2.3
 d-i netcfg/get_ipaddress   string 192.168.2.25
 d-i netcfg/get_netmask string 255.255.255.0
 d-i netcfg/get_gateway string 192.168.2.1
 d-i netcfg/confirm_static  boolean true
 d-i netcfg/get_hostnamestring myserver
 d-i netcfg/get_domain  string myhome.none
 d-i network-console/password   password password
 d-i network-console/password-again password password
bernhard@s:/data/home/bernhard/mail$ 
bernhard@s:/data/home/bernhard/src/debian-installer-20110106+squeeze1/build/config$
 touch local


bernhard@s:/data/home/bernhard/src/debian-installer-20110106+squeeze1$ fakeroot 
make rebuild_netboot
make: *** No rule to make target `rebuild_netboot'.  Stop.  

bernhard@s:/data/home/bernhard/src/debian-installer-20110106+squeeze1$  

bernhard@s:/data/home/bernhard/src/debian-installer-20110106+squeeze1/build$ 
bernhard@s:/data/home/bernhard/src/debian-installer-20110106+squeeze1/build$ 
fakeroot make rebuild_netboot   
   
rm -f ./stamps/tree-unpack-netboot-stamp ./stamps/tree-netboot-stamp 
./stamps/extra-netboot-stamp ./stamps/get_udebs-netboot-stamp   
   
rm -f ./tmp/netboot/diskusage.txt   

rm -f ./tmp/netboot/all.utf
rm -f ./tmp/netboot/unifont.bdf ./tmp/netboot/tree/lib/unifont.bgf
rm -f pkg-lists/standard-udebs pkg-lists/kernel-module-udebs
rm -rf ./dest/netboot/debian-installer ./dest/netboot/netboot.tar.gz 
./dest/netboot/mini.iso
rm -rf ./tmp/netboot
update-manifest
Using generated sources.list.udeb:
   deb copy:/data/home/bernhard/src/debian-installer-20110106+squeeze1/build/ 
localudebs/
   deb ftp://debian.sil.at/debian unstable main/debian-installer
make[3]: `sources.list.udeb' is up to date.
Ign copy: localudebs/ Release.gpg
Ign copy:/data/home/bernhard/src/debian-installer-20110106+squeeze1/build/ 
localudebs/ Translation-en
Ign copy:/data/home/bernhard/src/debian-installer-20110106+squeeze1/build/ 
localudebs/ Translation-en_US
Ign copy: localudebs/ Release 
Ign copy: localudebs/ Packages
Ign copy: localudebs/ Packages
Ge

Bug#633725: marked as done (debian-installer: On IBM x3650 M3 debian installer language selection broken)

2013-07-21 Thread Debian Bug Tracking System

Your message dated Mon, 22 Jul 2013 01:12:11 +0200
with message-id <201307220112.30643.hol...@layer-acht.org>
and subject line dealing with old debian-installer bugs
has caused the Debian Bug report #633725,
regarding debian-installer: On IBM x3650 M3 debian installer language selection 
broken
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.)


-- 
633725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: squeeze amd64
Severity: normal
Tags: l10n


 On IBM x3650 M3 debian installer language selection broken-Only english is 
available. Same ISO (usb-stick or DVD-R) is OK on another hardware. I tried 
with both Netinstall and DVD-1 ISO provided on debian.org. Netinstall ISO has 
been written on 3 several USB sticks using Unetbootin running on windows 7, and 
DVD burned from Windows 7 integrated tools. All the media have been tested and 
confirmed OK on other computers. The bug seems to be linked to hardware. ISO 
versions are 6.0.2.1.
-- System Information:
Debian Release: 6.0.2.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32.5-amd64 (SMP w/12 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


--- End Message ---
--- Begin Message ---
reassign 690832 choose-mirror
reassign 687488 netcfg
retitle 709319 wheezy 7.1: scanning for more DVDs is confusing
tags 709319 + confirmed
tags 626219 + confirmed
reassign 616722 partman-md
reassign 616125 partman-crypto
thanks

Hi,

thank you for submitting bug reports concering debian-installer, much 
appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they have been from a development phase where things were not stable and/or
- they are very old and/or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - and that's often better, as the bug 
log will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
--- End Message ---

Bug#606055: marked as done (Expert installer freezes when selecting "Configure MD devices")

2013-07-21 Thread Debian Bug Tracking System

Your message dated Mon, 22 Jul 2013 01:12:11 +0200
with message-id <201307220112.30643.hol...@layer-acht.org>
and subject line dealing with old debian-installer bugs
has caused the Debian Bug report #606055,
regarding Expert installer freezes when selecting "Configure MD devices"
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.)


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

Package: debian-installer
Version: 20101127 (6.0 squeeze)

Just trying out Debian for the first time, installing it over the top of a 
Gentoo box.  I configured all the partitions (mostly by accepting the existing 
software-RAID configuration and leaving it unchanged except for reformatting 
everything.)


After this the main menu came up with "Configure MD devices" which I selected, 
and half an hour later it's still sitting at a blank (blue) screen.


This is a network install, booted over TFTP and running through SSH.  Syslog 
says:

Dec  6 00:00:15 kernel: [  644.380596] md1: detected capacity change from 0 to 
725173403648

Dec  6 00:00:15 kernel: [  644.389755]  md1: unknown partition table
Dec  6 00:00:16 kernel: [  644.814460] device-mapper: uevent: version 1.0.3
Dec  6 00:00:16 kernel: [  644.815527] device-mapper: ioctl: 4.15.0-ioctl 
(2009-04-01) initialised: dm-de...@redhat.com

Dec  6 00:00:16 partman:   No matching physical volumes found
Dec  6 00:00:16 partman:
Dec  6 00:00:16 partman: No volume groups found
Dec  6 00:00:16 partman:
Dec  6 00:00:16 partman:   Reading all physical volumes.  This may take a 
while...
Dec  6 00:00:16 partman-lvm:
Dec  6 00:00:16 partman-lvm: No volume groups found
Dec  6 00:00:16 partman-lvm:
Dec  6 00:08:21 partman: mke2fs 1.41.12 (17-May-2010)
Dec  6 00:09:02 partman: mke2fs 1.41.12 (17-May-2010)
Dec  6 00:09:10 partman: mke2fs 1.41.12 (17-May-2010)
Dec  6 00:09:12 kernel: [ 1181.567882] EXT4-fs (md0): mounted filesystem with 
ordered data mode
Dec  6 00:09:12 kernel: [ 1181.648716] EXT4-fs (md2): mounted filesystem with 
ordered data mode
Dec  6 00:09:13 kernel: [ 1181.758433] EXT4-fs (md1): mounted filesystem with 
ordered data mode

Dec  6 00:09:14 apt-install: Queueing package e2fsprogs for later installation
Dec  6 00:09:16 main-menu[3021]: INFO: Falling back to the package description 
for mdcfg
Dec  6 00:09:16 main-menu[3021]: INFO: Falling back to the package description 
for mdcfg
Dec  6 00:09:18 kernel: [ 1187.001596] JBD: barrier-based sync failed on md0-8 
- disabling barriers
Dec  6 00:11:57 main-menu[3021]: INFO: Falling back to the package description 
for mdcfg

Dec  6 00:11:57 main-menu[3021]: INFO: Menu item 'mdcfg' selected
Dec  6 00:11:57 main-menu[3021]: WARNING **: Unable to set title for mdcfg.
Dec  6 00:11:57 apt-install: Queueing package mdadm for later installation
Dec  6 00:48:10 sshd[15349]: WARNING: /etc/ssh/moduli does not exist, using 
fixed modulus
Dec  6 00:48:14 sshd[15349]: Accepted password for installer from 192.168.0.14 
port 53709 ssh2


Last two messages are from my login to get this.  /proc/mdstat says all RAID 
arrays are functioning normally.  I just tried reconnecting and doing it again 
with the same result.  New log messages are:


Dec  6 00:58:09 debconf: Setting debconf/language to en_AU:en
Dec  6 00:58:11 debconf: Setting debconf/priority to low
Dec  6 00:58:11 debconf: Setting debconf/language to en_AU:en
Dec  6 00:58:11 main-menu[15390]: INFO: Falling back to the package 
description for mdcfg
Dec  6 00:58:17 main-menu[15390]: INFO: Falling back to the package 
description for mdcfg

Dec  6 00:58:17 main-menu[15390]: INFO: Menu item 'mdcfg' selected
Dec  6 00:58:17 main-menu[15390]: WARNING **: Unable to set title for mdcfg.

Guess I should skip this step...


--- End Message ---
--- Begin Message ---
reassign 690832 choose-mirror
reassign 687488 netcfg
retitle 709319 wheezy 7.1: scanning for more DVDs is confusing
tags 709319 + confirmed
tags 626219 + confirmed
reassign 616722 partman-md
reassign 616125 partman-crypto
thanks

Hi,

thank you for submitting bug reports concering debian-installer, much 
appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they have been from a development phase where things were not stable and/

Bug#623187: marked as done (Squeeze installation fails on IBM x3650 M3 with LSI MegaRAID)

2013-07-21 Thread Debian Bug Tracking System

Your message dated Mon, 22 Jul 2013 01:12:11 +0200
with message-id <201307220112.30643.hol...@layer-acht.org>
and subject line dealing with old debian-installer bugs
has caused the Debian Bug report #623187,
regarding Squeeze installation fails on IBM x3650 M3 with LSI MegaRAID
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.)


-- 
623187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: debian-6.0.1a-amd64-businesscard.iso

After regular installation of Debian Squeeze from businesscard
netinst.iso on IBM x3650 M3 with LSI MegaRAID system is not booting.
There are no errors reported during installation, all hardware is
properly recognized and GRUB installs without problem but after restart
GRUB is not loading, only cursor blinks at top left corner of screen.
I suspect, that the problem is related to the GRUB installation.
To fix the problem, I have started netinst/rescue and installed LILO on
target system. With LILO, system works flawlessly. What is more funny,
if I install GRUB after LILO, GRUB is working also.
It means that LILO must change something in boot sector making it
bootable.
Server has LSI MegaRAID SAS controller and two disks in RAID-1.
This problem has been confirmed on second IBM x3650 M3 servers.


lspci:
===
00:00.0 Host bridge: Intel Corporation 5520 I/O Hub to ESI Port (rev 22)
00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express
Root Port 1 (rev 22)
00:02.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express
Root Port 2 (rev 22)
00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express
Root Port 3 (rev 22)
00:05.0 PCI bridge: Intel Corporation 5520/X58 I/O Hub PCI Express Root
Port 5 (rev 22)
00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express
Root Port 7 (rev 22)
00:09.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express
Root Port 9 (rev 22)
00:10.0 PIC: Intel Corporation 5520/5500/X58 Physical and Link Layer
Registers Port 0 (rev 22)
00:10.1 PIC: Intel Corporation 5520/5500/X58 Routing and Protocol Layer
Registers Port 0 (rev 22)
00:11.0 PIC: Intel Corporation 5520/5500 Physical and Link Layer
Registers Port 1 (rev 22)
00:11.1 PIC: Intel Corporation 5520/5500 Routing & Protocol Layer
Register Port 1 (rev 22)
00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management
Registers (rev 22)
00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch
Pad Registers (rev 22)
00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and
RAS Registers (rev 22)
00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers
(rev 22)
00:15.0 PIC: Intel Corporation 5520/5500/X58 Trusted Execution
Technology Registers (rev 22)
00:16.0 System peripheral: Intel Corporation 5520/5500/X58 Chipset
QuickData Technology Device (rev 22)
00:16.1 System peripheral: Intel Corporation 5520/5500/X58 Chipset
QuickData Technology Device (rev 22)
00:16.2 System peripheral: Intel Corporation 5520/5500/X58 Chipset
QuickData Technology Device (rev 22)
00:16.3 System peripheral: Intel Corporation 5520/5500/X58 Chipset
QuickData Technology Device (rev 22)
00:16.4 System peripheral: Intel Corporation 5520/5500/X58 Chipset
QuickData Technology Device (rev 22)
00:16.5 System peripheral: Intel Corporation 5520/5500/X58 Chipset
QuickData Technology Device (rev 22)
00:16.6 System peripheral: Intel Corporation 5520/5500/X58 Chipset
QuickData Technology Device (rev 22)
00:16.7 System peripheral: Intel Corporation 5520/5500/X58 Chipset
QuickData Technology Device (rev 22)
00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #4
00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #5
00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2
EHCI Controller #2
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express
Root Port 1
00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express
Root Port 5
00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #1
00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #2
00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #3
00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2
EHCI Controller #1
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporatio

Bug#616124: marked as done (debian-installer: APT fails to connect to repository after network reconfiguration)

2013-07-21 Thread Debian Bug Tracking System

Your message dated Mon, 22 Jul 2013 01:12:11 +0200
with message-id <201307220112.30643.hol...@layer-acht.org>
and subject line dealing with old debian-installer bugs
has caused the Debian Bug report #616124,
regarding debian-installer: APT fails to connect to repository after network 
reconfiguration
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.)


-- 
616124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: 20110106+b1
Severity: normal
Tags: d-i

Installing Squeeze 64-bit graphical netinst through eth0.

I changed my physical location just before the "Popularity contest" page 
without turning off the computer.

I ran the "Network configuration" step again, and it said "Autoconfiguration is 
successful", and in the log on console 4 I could see that DHCP went OK.

However, when installing packages APT said in console 4 "Temporary failure in 
resolving ", even if I tried very different mirrors.

At the same time, "wget http://google.com && cat index.html" could pull down 
the frontpage of that website without any problem, so I assume that the network 
was indeed configured and working.

Impact: I had to restart the whole installation process.

-- System Information:
Debian Release: 6.0
  APT prefers squeeze-updates
  APT policy: (500, 'squeeze-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---
reassign 690832 choose-mirror
reassign 687488 netcfg
retitle 709319 wheezy 7.1: scanning for more DVDs is confusing
tags 709319 + confirmed
tags 626219 + confirmed
reassign 616722 partman-md
reassign 616125 partman-crypto
thanks

Hi,

thank you for submitting bug reports concering debian-installer, much 
appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they have been from a development phase where things were not stable and/or
- they are very old and/or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - and that's often better, as the bug 
log will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
--- End Message ---

Bug#615599: marked as done (debian-installer prefers usb Blockdevices over "real" harddrives)

2013-07-21 Thread Debian Bug Tracking System

Your message dated Mon, 22 Jul 2013 01:12:11 +0200
with message-id <201307220112.30643.hol...@layer-acht.org>
and subject line dealing with old debian-installer bugs
has caused the Debian Bug report #615599,
regarding debian-installer prefers usb Blockdevices over "real" harddrives
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.)


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

Package: debian-installer
Version: 20110106+b1

Tried to autoinstall squeeze on dell poweredge hardware with drac5 or 
idrac6 KVM. The installer always tried to use 40MB usb vflash (/dev/sda) 
instead of the 1tb real harddrive (/dev/sdb).


I'd suggest to give real harddrive controllers (like cciss, mptfusion, 
ahci, megaraid_sas) precedence over usb_storage.


Regards Thomas


--- End Message ---
--- Begin Message ---
reassign 690832 choose-mirror
reassign 687488 netcfg
retitle 709319 wheezy 7.1: scanning for more DVDs is confusing
tags 709319 + confirmed
tags 626219 + confirmed
reassign 616722 partman-md
reassign 616125 partman-crypto
thanks

Hi,

thank you for submitting bug reports concering debian-installer, much 
appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they have been from a development phase where things were not stable and/or
- they are very old and/or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - and that's often better, as the bug 
log will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
--- End Message ---

Bug#717519: [debian-installer] daily-build cd image won't boot since 20130715

2013-07-21 Thread Eugene Paskevich

Please also find attached the diff -ruN output between the 20130714 and  
20130716 initrd trees.


--
Eugene Paskevich |   *==)---   | Plug me into
eug...@raptor.kiev.ua|   ---(==*   |  The Matrix

initrd.diff.gz
Description: GNU Zip compressed data

Processed: Re: Bug#717511: Kernel does not start up on Pegasos-2

2013-07-21 Thread Debian Bug Tracking System

Processing control commands:

> reassign -1 yaboot-installer 1.1.26
Bug #717511 [linux-image-3.2.0-4-powerpc] Kernel does not start up on Pegasos-2
Bug reassigned from package 'linux-image-3.2.0-4-powerpc' to 'yaboot-installer'.
No longer marked as found in versions linux/3.2.46-1.
Ignoring request to alter fixed versions of bug #717511 to the same values 
previously set
Bug #717511 [yaboot-installer] Kernel does not start up on Pegasos-2
Marked as found in versions yaboot-installer/1.1.26.

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


--
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.b717511.13744401486832.transcr...@bugs.debian.org

79 matches

Mail list logo