Bug#631172: Wrong kernel installed for VIA C3 Nehemia

2011-06-20 Thread Bernhard
Package: installation-reports

Boot method: CD
Image version: Self-made Boot-CD with daily build of sid installer
Date: 2011-06-21

Machine: Self-made Desktop PC
Processor: VIA C3 Nehemia
Memory: 256MB
Partitions: -not performed-

Output of lspci -knn:

>> 00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8623 [Apollo CLE266] 
>> [1106:3123]
>>  Subsystem: VIA Technologies, Inc. Device [1106:aa01]
>>  Kernel driver in use: agpgart-via
>> 00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] 
>> [1106:b091]
>> 00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 
>> Controller [1106:3038] (rev 80)
>>  Subsystem: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller 
>> [1106:3038]
>>  Kernel driver in use: uhci_hcd
>> 00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 
>> Controller [1106:3038] (rev 80)
>>  Subsystem: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller 
>> [1106:3038]
>>  Kernel driver in use: uhci_hcd
>> 00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 
>> Controller [1106:3038] (rev 80)
>>  Subsystem: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller 
>> [1106:3038]
>>  Kernel driver in use: uhci_hcd
>> 00:10.3 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] 
>> (rev 82)
>>  Subsystem: VIA Technologies, Inc. USB 2.0 [1106:3104]
>>  Kernel driver in use: ehci_hcd
>> 00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8235 ISA Bridge 
>> [1106:3177]
>>  Subsystem: VIA Technologies, Inc. Device [1106:aa01]
>> 00:11.1 IDE interface [0101]: VIA Technologies, Inc. 
>> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06)
>>  Subsystem: VIA Technologies, Inc. Device [1106:aa01]
>>  Kernel driver in use: pata_via
>> 00:11.5 Multimedia audio controller [0401]: VIA Technologies, Inc. 
>> VT8233/A/8235/8237 AC97 Audio Controller [1106:3059] (rev 50)
>>  Subsystem: VIA Technologies, Inc. Device [1106:aa01]
>>  Kernel driver in use: VIA 82xx Audio
>> 00:12.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6102 [Rhine-II] 
>> [1106:3065] (rev 74)
>>  Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet 
>> Controller on VT8235 [1106:0102]
>>  Kernel driver in use: via-rhine
>> 00:14.0 Ethernet controller [0200]: D-Link System Inc DWL-510 / DWL-610 
>> 802.11b [Realtek RTL8180L] [1186:3300] (rev 20)
>>  Subsystem: D-Link System Inc DWL-510 Wireless PCI Adapter [1186:3301]
>>  Kernel driver in use: rtl8180
>> 01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. VT8623 
>> [Apollo CLE266] integrated CastleRock graphics [1106:3122] (rev 03)
>>  Subsystem: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated 
>> CastleRock graphics [1106:3122]

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:[E]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

During installation of Base system, the installer try to install the
686-Kernel.
Since 2.6.39, the 686 Kernel is only supported, if CPU supports PAE.
But, the VIA C3 has no PAE.

Please install the 486 Kernel instead of 686 Kernel.

Best regards
Bernhard



-- 
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/4e003b88.1070...@yahoo.de



Bug#630523: Interested ???

2011-06-20 Thread jeffrice

Hello Friend,

I have a business proposal for you worth 7.5Million Great British Pound
Sterling's. If you are interested, please send a response .

Best regards,
Jeff Rice.



--
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/20110620035902.52144j7igh7a7...@webmail.fuac.edu.co



Bug#516911: marked as done (Wrong kernel installed at K7 architecture)

2011-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2011 11:45:05 +0200
with message-id <4dff16a1.8070...@yahoo.de>
and subject line Lenny no more installed on this computer
has caused the Debian Bug report #516911,
regarding Wrong kernel installed at K7 architecture
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.)


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

Boot method: CD
Image version: Self-made boot CD with Lenny Debian Installer 5.0.0
Date: 2009-02-23

Machine: Self-made Desktop PC
Processor: AMD Duron 800MHz
Memory: 256MB
Partitions: 

> Dateisystem   Typ1K‐Blöcke   Benutzt Verfügbar Ben% Eingehängt auf
> /dev/hda1 ext3 1921156635360   1188204  35% /
> tmpfstmpfs  128284 4128280   1% /lib/init/rw
> udev tmpfs   1024084 10156   1% /dev
> tmpfstmpfs  128284 0128284   0% /dev/shm
> /dev/hda5  xfs77443576  26133228  51310348  34% /storage1
> /dev/hdb5  xfs   244076732 160107184  83969548  66% /storage2

Output of lspci -knn:

> 00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 735 Host 
> [1039:0735] (rev 01)
>   Kernel driver in use: agpgart-sis
>   Kernel modules: sis-agp
> 00:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] Virtual 
> PCI-to-PCI bridge (AGP) [1039:0001]
>   Kernel modules: shpchp
> 00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] SiS85C503/5513 
> (LPC Bridge) [1039:0018]
>   Kernel modules: i2c-sis630
> 00:02.1 SMBus [0c05]: Silicon Integrated Systems [SiS] SiS961/2 SMBus 
> Controller [1039:0016]
>   Kernel driver in use: sis96x_smbus
>   Kernel modules: i2c-sis96x
> 00:02.2 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 
> Controller [1039:7001] (rev 07)
>   Kernel driver in use: ohci_hcd
>   Kernel modules: ohci-hcd
> 00:02.3 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 
> Controller [1039:7001] (rev 07)
>   Kernel driver in use: ohci_hcd
>   Kernel modules: ohci-hcd
> 00:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513 [IDE] 
> [1039:5513] (rev d0)
>   Kernel driver in use: SIS_IDE
>   Kernel modules: sis5513
> 00:0f.0 Network controller [0280]: RaLink RT2500 802.11g Cardbus/mini-PCI 
> [1814:0201] (rev 01)
>   Kernel driver in use: rt2500pci
>   Kernel modules: rt2500pci
> 00:11.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8169 
> Gigabit Ethernet [10ec:8169] (rev 10)
>   Kernel driver in use: r8169
>   Kernel modules: r8169
> 00:13.0 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 
> Controller [1106:3038] (rev 50)
>   Kernel driver in use: uhci_hcd
>   Kernel modules: uhci-hcd
> 00:13.1 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 
> Controller [1106:3038] (rev 50)
>   Kernel driver in use: uhci_hcd
>   Kernel modules: uhci-hcd
> 00:13.2 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] 
> (rev 51)
>   Kernel driver in use: ehci_hcd
>   Kernel modules: ehci-hcd
> 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Rage 128 RF/SG 
> AGP [1002:5246]
>   Kernel modules: aty128fb

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:[E]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

The used architecture is a K7 architecture (AMD Duron 800MHz).
The kernel has to be the 686 image.
But there is the 486 image installed.

Regards
Bernhard


--- End Message ---
--- Begin Message ---
As described, Lenny is no more installed on this computer.

--- End Message ---


rootskel: Add Freescale i.MX serial consoles, /dev/ttymxc*

2011-06-20 Thread Loïc Minier
Hi

 While checking how framebuffer gets set, I saw that the list of serial
 consoles in rootskel missed the Freescale i.MX ones, /dev/ttymxc[0-9].
 According to etc/securetty, these seem to be the only missing ones as
 the other devices start with a capital letter.

 ok to commit?

   Cheers,



-- 
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/1308566781-5871-1-git-send-email-l...@debian.org



[PATCH] Add Freescale i.MX serial consoles, /dev/ttymxc*

2011-06-20 Thread Loïc Minier
---
 src/lib/debian-installer/detect-console-linux |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/src/lib/debian-installer/detect-console-linux 
b/src/lib/debian-installer/detect-console-linux
index 79dde91..404a4e7 100644
--- a/src/lib/debian-installer/detect-console-linux
+++ b/src/lib/debian-installer/detect-console-linux
@@ -1,6 +1,6 @@
 if [ -z "$TERM_TYPE" ]; then
case $(readlink /proc/self/fd/0) in
-   /dev/console|/dev/tty[A-Z]*|/dev/hvc*|/dev/hvsi*)
+   /dev/console|/dev/tty[A-Z]*|/dev/ttymxc*|/dev/hvc*|/dev/hvsi*)
TERM_TYPE=serial
;;
/dev/tty*)
-- 
1.7.5.4


-- 
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/1308566781-5871-2-git-send-email-l...@debian.org



[PATCH] Remove armeb netboot config

2011-06-20 Thread Loïc Minier
---

Hey

 It seems this file is a leftover from the armeb removal; ok to remove?

   Thanks,

 build/pkg-lists/netboot/armeb.cfg |   12 
 1 files changed, 0 insertions(+), 12 deletions(-)
 delete mode 100644 build/pkg-lists/netboot/armeb.cfg

diff --git a/build/pkg-lists/netboot/armeb.cfg 
b/build/pkg-lists/netboot/armeb.cfg
deleted file mode 100644
index db2897d..000
--- a/build/pkg-lists/netboot/armeb.cfg
+++ /dev/null
@@ -1,12 +0,0 @@
-console-keymaps-at
-
-kbd-chooser
-bogl-bterm-udeb
-hw-detect
-ethdetect
-netcfg
-
-#kernel modules
-
-#for all targets
-
-- 
1.7.5.4


-- 
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/1308571655-7704-1-git-send-email-l...@debian.org



[PATCH] armel: Check whether fb0 has a sysfs driver

2011-06-20 Thread Loïc Minier
---
 .../S40framebuffer-module-linux-armel  |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

Hey,

 I was seeing some busybox output (Usage: basename FILE [SUFFIX] etc.)
 when starting d-i under QEMU emulating armel+vexpress.  Turns out that
 under vexpress kernels, /sys/class/graphics/fb0 has a dev file which
 contains "29:0" but no device symlink to the platform device entry (nor
 any matching platform device) which I can see for instance on OMAP.
 I'm not entirely sure whether it's a linux bug or not, but it seems
 we'd be better off checking whether the node exists before readlink-ing
 across it.

 I've confirmed that this change silences the error message.

 From a quick look at the actual fb driver causing this, it seems that
 it's CONFIG_FB_ARMCLCD / linux/drivers/video/amba-clcd.c / "ARM
 PrimeCell PL110 support" which can indeed be built as a module; not
 sure how to detect this or have it register a platform device though.

   Cheers,

diff --git 
a/src/lib/debian-installer-startup.d/S40framebuffer-module-linux-armel 
b/src/lib/debian-installer-startup.d/S40framebuffer-module-linux-armel
index 0989d02..da6a052 100644
--- a/src/lib/debian-installer-startup.d/S40framebuffer-module-linux-armel
+++ b/src/lib/debian-installer-startup.d/S40framebuffer-module-linux-armel
@@ -9,7 +9,7 @@ if [ -n "$TERM_FRAMEBUFFER_TRY" ] && \
if [ -d /sys/class/graphics/fb0 ]; then
if [ "$(cat /sys/class/graphics/fb0/name)" = "udlfb" ]; then
register-module -i udlfb
-   else
+   elif [ -e /sys/class/graphics/fb0/device/driver ]; then
driver=$(basename $(readlink 
/sys/class/graphics/fb0/device/driver))
register-module -i "$driver"
fi
-- 
1.7.5.4


-- 
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/1308576254-22459-1-git-send-email-l...@debian.org



Bug#562122: marked as done (netcfg: Improve preseeding of network device to use)

2011-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2011 17:26:08 +0100
with message-id <20110620162608.ga22...@riva.ucam.org>
and subject line Re: Bug#562122: Improve preseeding of network device to use
has caused the Debian Bug report #562122,
regarding netcfg: Improve preseeding of network device to use
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.)


-- 
562122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: netcfg
Version: 1.51
Severity: wishlist

I've just sat through many installs on ThinkPad T41, T43 vintage laptops, using 
PXE, wired Ethernet, and a preseeded installation.

I've preseeded netcfg/choose_interface to "auto", to try and avoid the
netcfg/choose_interface question being asked. What I suspect is the problem, is 
the wireless interface is showing "link" so the question still gets asked.

My thoughts on how to extend this functionality was:

allow preseeding the interface to use based on:

1) vendor component of the MAC
2) PCI ID
3) some substring of the interface description

because preseeding the specific interface by name is a non-starter, due to the
way Linux can't consistently enumerate the interfaces.

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

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


--- End Message ---
--- Begin Message ---
Source: netcfg
Source-Version: 1.63

On Mon, Jan 31, 2011 at 05:48:49AM +1100, Matthew Palmer wrote:
> On Sun, Jan 30, 2011 at 04:24:13PM +0100, Floris Bos wrote:
> > I think that at least selection of the network interface by MAC-address 
> > instead of interface name should be possible.
> > 
> > There is currently a patch pending for Ubuntu:
> >  http://launchpadlibrarian.net/60443113/S31pxedust
> > (belonging to bug 
> > https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/56679 
> > )
> > 
> > Any chance of getting this into Debian as well?
> 
> The feature, yes.  That patch... not so much.

I fixed this in netcfg 1.63 (not using the above patch!) without
realising that this bug report existed.  Closing.

netcfg (1.63) unstable; urgency=low

  * If BOOTIF= is set on the Linux command line, look for an interface with
that address and use it by default (closes: #615600, LP: #56679).

  [ Updated translations ]
  * Asturian (ast.po) by MAAC
  * German (de.po) by Holger Wansing
  * Italian (it.po) by Milo Casagrande

 -- Colin Watson   Thu, 16 Jun 2011 18:03:01 +0100

Cheers,

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

--- End Message ---


Bug#570905: marked as done (iceweasel is no longer a desktop environment independent browser)

2011-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2011 12:55:27 -0400
with message-id <4dff7b7f.3040...@gmail.com>
and subject line Close
has caused the Debian Bug report #570905,
regarding iceweasel is no longer a desktop environment independent browser
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.)


-- 
570905: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xulrunner
Version: 1.9.1.8-2
Severity: important
Tags: d-i
X-Debbugs-CC: task...@packages.debian.org

I was very surprised when I upgraded a KDE system to find that xulrunner 
tried to pull in all sorts of GNOME packages. It was quite a bit of work 
to unselect everything that got pulled in through those Recommends.

I'm talking about the Recommends for:
- libdbus-glib-1-2
- libgconf2-4
- libgnome2-0
- libgnomeui-0
- libgnomevfs2-0
And the deps for those packages are far from trivial.

I guess the change was introduced in 1.9.1.6-2 with:
   Merge xulrunner-1.9.1-gnome-support into xulrunner-1.9.1.

But I question if the Recommends of those packages is policy compliant as 
Recommends should only be used for packages "that would be found together 
with this one in all but unusual installations" [1].
And that's only true for systems running a GNOME desktop environment. For 
systems running KDE the GNOME packages are not needed and even in a lot of 
cases very much not desired.

I also question the value of the Recommends: if a user is running GNOME 
they will all be installed already anyway!

As Debian Installer now installs Recommends by default and the desktop 
tasks installs iceweasel for all desktops, this means that all those GNOME 
packages would get installed on KDE desktop systems by default, 

As iceweasel is supposed to be desktop environment independent, I urge you 
to reconsider this change. IMO the current Recommends make iceweasel 
unsuitable for default installation.
I also feel that for packages like iceweasel integration support for 
specific desktop environments should always be optional.

Cheers,
FJP

[1]http://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps


--- End Message ---
--- Begin Message ---
xulrunner 1.9.1.8-4 has indeed demoted the problematic Recommends to 
Suggests.


Although I probably have several of these packages installed now, I used 
Iceweasel without the problematic packages for a long time on KDE and 
didn't notice issues. I also don't really share the idea that Konqueror 
can be a replacement for Iceweasel. I don't see anything that could 
actually replace Mozilla on KDE.


If anyone still considers this a problem, feel free to open a new report 
pointing to actual issues currently seen.


--- End Message ---


Re: [PATCH] armel: Check whether fb0 has a sysfs driver

2011-06-20 Thread Loïc Minier
 So turns out it's indeed a driver problem;
 https://bugs.launchpad.net/linux-linaro/+bug/799795

 we can go either way for d-i; if we keep the warning, it will look ugly
 on bogus platforms and might hint / push at fixing it

-- 
Loïc Minier


-- 
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/20110620181247.ga26...@bee.dooz.org



Debian installer build: failed or old builds

2011-06-20 Thread Daily build aggregator
Debian installer build overview
---

Failed or old builds:

* FAILED BUILD: amd64 Jun 21 00:09 buildd@barber build_netboot 
http://d-i.debian.org/daily-images/amd64/daily/build_netboot.log

* FAILED BUILD: amd64 Jun 21 00:12 buildd@barber build_netboot-gtk 

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

* FAILED BUILD: amd64 Jun 21 00:12 buildd@barber build_netboot-xen 

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

* FAILED BUILD: armel Jun 19 18:49 buildd@alain build_iop32x_netboot 

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

* FAILED BUILD: armel Jun 19 18:49 buildd@alain 
build_iop32x_network-console_glantank 

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

* FAILED BUILD: armel Jun 19 18:50 buildd@alain 
build_iop32x_network-console_n2100 

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

* FAILED BUILD: armel Jun 19 18:50 buildd@alain 
build_iop32x_network-console_ss4000e 

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

* FAILED BUILD: armel Jun 19 18:51 buildd@alain build_kirkwood_netboot 

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

* FAILED BUILD: armel Jun 19 18:51 buildd@alain build_kirkwood_netboot-gtk 

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

* FAILED BUILD: armel Jun 19 18:52 buildd@alain build_kirkwood_network-console 

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

* FAILED BUILD: armel Jun 19 18:52 buildd@alain build_orion5x_network-console 

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

* FAILED BUILD: armel Jun 19 18:53 buildd@alain build_versatile_netboot 

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

* FAILED BUILD: i386 Jun 21 00:08 buildd@biber build_netboot 
http://d-i.debian.org/daily-images/i386/daily/build_netboot.log

* FAILED BUILD: i386 Jun 21 00:10 buildd@biber build_netboot-gtk 

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


Totals: 111 builds (14 failed, 0 old)


-- 
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/e1qypjz-0001ln...@ravel.debian.org



Various failures in D-I daily builds

2011-06-20 Thread Christian PERRIER
Quoting Daily build aggregator (debian-boot@lists.debian.org):
> Debian installer build overview
> ---
> 
> Failed or old builds:

1) armel iop32x and kirkwood subarches builds fail because of missing kernel 
udebs


2) netboot images for amd64 and i386 fail because of:

.../...
-no-emul-boot -boot-load-size 4 -boot-info-table \
-o ./tmp/netboot-gtk/mini.iso ./tmp/netboot-gtk/cd_tree
Size of boot image is 4 sectors -> No emulation
 35.68% done, estimate finish Tue Jun 21 00:12:34 2011
 71.25% done, estimate finish Tue Jun 21 00:12:23 2011
Total translation table size: 2048
Total rockridge attributes bytes: 4913
Total directory bytes: 10622
Path table size(bytes): 46
Max brk space used 0
14035 extents written (27 MB)
geniso_hybrid_plus_firmware_partition ./tmp/netboot-gtk/mini.iso
mkfs.msdos 3.0.9 (31 Jan 2010)

Command (m for help): Command action
   e   extended
   p   primary partition (1-4)
Partition number (1-4, default 2): First sector (57344-69631, default 57344): 
Using default value 57344
Last sector, +sectors or +size{K,M,G} (57344-69631, default 69631): Value out 
of range.
Last sector, +sectors or +size{K,M,G} (57344-69631, default 69631): Last 
sector, +sectors or +size{K,M,G} (57344-69631, default 69631): Value out of 
range.
Last sector, +sectors or +size{K,M,G} (57344-69631, default 69631): Value out 
of range.
Last sector, +sectors or +size{K,M,G} (57344-69631, default 69631): Last 
sector, +sectors or +size{K,M,G} (57344-69631, default 69631): 
make[2]: *** [arch_miniiso] Error 1
make[1]: *** [_build] Error 2
make: *** [build_netboot-gtk] Error 2





-- 





signature.asc
Description: Digital signature