Re: Processed: severity of 691046 is normal

[Julien Cristau]

On Wed, Oct 24, 2012 at 12:33:00 +0200, Luca Capello wrote:

> tags 691046 + patch
> thanks
> 
> Hi there!
> 
> On Tue, 23 Oct 2012 21:33:09 +0200, Debian Bug Tracking System wrote:
> > Processing commands for cont...@bugs.debian.org:
> >
> >> severity 691046 normal
> > Bug #691046 [installation-reports] installation-reports: manual
> > partitioning for GPT does not suggest a BIOS Boot Partition
> > Severity set to 'normal' from 'critical'
> 
> I do not understand this: the bug is at least 'important' and I decided
> to report it as 'critical' because it "makes unrelated software on the
> system (or the whole system) break".
> 
I think 'critical' is grossly overinflated for this bug.

> If you think partman is fine and does not to be fixed, as I wrote at
> least the installation guide should have a note, here is a patch:
> 
I don't know if partman is fine, I just don't think this warrants a rc
severity from what you described.

Cheers,
Julien


signature.asc
Description: Digital signature

Processing of apt-setup_0.75_i386.changes

[Debian FTP Masters]

apt-setup_0.75_i386.changes uploaded successfully to ftp-master.debian.org
along with the files:
  apt-setup_0.75.dsc
  apt-setup_0.75.tar.gz
  apt-setup-udeb_0.75_all.udeb
  apt-mirror-setup_0.75_all.udeb
  apt-cdrom-setup_0.75_all.udeb

Greetings,

Your Debian queue daemon (running on host ravel.debian.org)


-- 
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/e1trjj8-0005gd...@ravel.debian.org

Processing of apt-setup_0.75_i386.changes

[Debian FTP Masters]

apt-setup_0.75_i386.changes uploaded successfully to localhost
along with the files:
  apt-setup_0.75.dsc
  apt-setup_0.75.tar.gz
  apt-setup-udeb_0.75_all.udeb
  apt-mirror-setup_0.75_all.udeb
  apt-cdrom-setup_0.75_all.udeb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)


-- 
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/e1trjl2-0004iz...@franck.debian.org

apt-setup_0.75_i386.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 25 Oct 2012 06:12:12 +0200
Source: apt-setup
Binary: apt-setup-udeb apt-mirror-setup apt-cdrom-setup
Architecture: source all
Version: 1:0.75
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team 
Changed-By: Christian Perrier 
Description: 
 apt-cdrom-setup - set up a CD in sources.list (udeb)
 apt-mirror-setup - set up a mirror in sources.list (udeb)
 apt-setup-udeb - Configure apt (udeb)
Changes: 
 apt-setup (1:0.75) unstable; urgency=low
 .
   [ Updated translations ]
   * Amharic (am.po) by Tegegne Tefera
   * Asturian (ast.po) by ivarela
   * Welsh (cy.po) by Dafydd Tomos
   * Kannada (kn.po) by Prabodh
   * Serbian (sr.po) by Karolina Kalic
   * Tamil (ta.po) by Dr.T.Vasudevan
   * Ukrainian (uk.po) by Yuri Chornoivan
Checksums-Sha1: 
 96233cceaed897968c96e18211a64f53139cafa1 1728 apt-setup_0.75.dsc
 25ed6d1c11d0d185f8143bc4737ca963dee0c236 298571 apt-setup_0.75.tar.gz
 3b0cc0f564a91b4b6d630ac6cfa33da32404acdc 64786 apt-setup-udeb_0.75_all.udeb
 9f9c3207126e40d5f827f868faad4957bf06d658 72864 apt-mirror-setup_0.75_all.udeb
 bd3020ab1b71f9cd8394d10ed17d7f657c8c7eb5 95526 apt-cdrom-setup_0.75_all.udeb
Checksums-Sha256: 
 5505a9657401fec44308dc5b5eac20e093f20f91f37a4e1c2ad4714817a9da46 1728 
apt-setup_0.75.dsc
 2e5c56a02a0401d57849c6ff83a7526319cd8f1c75b0342334eb2c927de225e7 298571 
apt-setup_0.75.tar.gz
 cf684619ccafbedff58c8c025aab4a6499923d54e1d3d0f91d7e55be912b3a72 64786 
apt-setup-udeb_0.75_all.udeb
 13464786cfbff179f98dc32375dc58dddb2bb7c1b2e42a99dc8bd46e98606769 72864 
apt-mirror-setup_0.75_all.udeb
 32325a7e945ed9659d8446ec536ba7ee28bf16ec33f4884968faa6e7f25e19ce 95526 
apt-cdrom-setup_0.75_all.udeb
Files: 
 4eb97f4364abb9f76fbe6cb7db46275d 1728 debian-installer extra apt-setup_0.75.dsc
 fda252119ccb48504a019e7203f66050 298571 debian-installer extra 
apt-setup_0.75.tar.gz
 6bbb142c2dcbfc0d29ea9a8b8d3df098 64786 debian-installer standard 
apt-setup-udeb_0.75_all.udeb
 a54fe6abc70f9d19ba8ed34d4baf9068 72864 debian-installer extra 
apt-mirror-setup_0.75_all.udeb
 cbf79442fdd263d7e4f66a62622f41c5 95526 debian-installer extra 
apt-cdrom-setup_0.75_all.udeb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIVAwUBUIj/QocvcCxNbiWoAQIbHg/+JTNV6E7mWhbsQaAJbh3kNuWePIfvpFXq
DSMELwS0WknpAQR/nam2LSJuQ7B4ArcGFzN9vNjQR+fMsx/f4rUu2jqOGAOPlSU+
93tcmTnAOz95tHGakOYWYOHctsvGpL2GmIOVIU/6NLwtzy5mq8D+WpN9YTdVbRzX
3T/L+YLIDouWKP61FYjNfJYnIREZ9sbmPAYSkcR0+eWdLvNoaYaQQB9WPigowLhx
g3ZjWdNYxEWaRIdU5b4Tf8n4F/Q7BGzZN1ySS3VTw+RRbkMX6BQmhueRVsXFp3Qn
IQ1BZFnD6azVsiBc6JyLD19BasNmoWmv4fAAliLQxOXJcIxHtDNFLBM++L65M1Na
+Rd8vKX7CzFTaKcXJl40wT66SoqPcyowUlQZ0g15dKoeqaNhzO5N65Qk0gMXaB46
POA+QfFtnLlmCWoy+W2Insl2IsXzFWyh6sRwuwz/cTPlEs5baLerNZIwXzK4r7/u
/5LKnU/uXZTxAvgm8nlIMIw57mABXJQc7vo6tHU/JfRIsXTfi33c8GN9iMTuTV2m
iwrInui0LC11V+vnN91PdXVHMmIt2PUPpTwRiW/2O65MTiwAHHtJpl8ucI/d2Usn
M0yFv9eSY6tVdpsFfm/UJpXuL9Gwo7AosVcBov4OtVLr4RgvJ/dRqY4I66PkaIuT
1oJYQqH2cWI=
=kLTO
-END PGP SIGNATURE-


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1trjzb-yo...@franck.debian.org

Bug#691366: wheezy 2012-10-24 daily built netinst

[Stephan Beyer]

Version: 2.48

Hi,

I am now at the machine where I installed the system and I can provide further
information.


 4. Booting the newly installed system

 Something at the installation f**ked up the /etc/network/interfaces
 file. However, the "failed" was because of a funny last line in that
 file but it nevertheless got the network up and running...


To be more concrete, the /etc/network/interfaces file looks like this:
-- snip --
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
#NetworkManager#iface eth0 inet dhcp
# This is an autoconfigured IPv6 interface
#NetworkManager#iface eth0 inet6 auto
# Activate RFC 4941 privacy extensions for outgoing connections. The
# machine will still be reachable via its EUI-64 interface identifier.
privext 2
-- snap --

And the error message is:
/etc/network/interfaces:15: misplaced option
ifup: couldn't read interfaces file "/etc/network/interfaces"

Looks pretty dangerous. However, as mentioned, everything worked though.
(In the meantime I commented out the "privext 2" line and the error
message vanished.)


 5. Starting the desktop environment


The described GNOME bug is already stated in #690017 [1]
and it is connected to the oddity of the preselected "Print Server" in the
tasksel menu in debian-installer.

1.http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690017

Should some GNOME Debian maintainers be Cc'ed?

The problem could either be solved by adding cups dependencies into the
gnome package ...or by fixing gnome. ;)


 6. KDE programs work but only after some minutes


I tested several programs and wrote bug report #691406 [2] against kde-standard
containing further information. I hope that helps.

2.http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691406

Best
  Stephan

PS: I add the info reportbug installation-report provides although I think
these are all mere software bugs.

Boot method: CD
Image 
version:http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
  from Oct 24

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="7.0 (wheezy) - installer build 20120930+b1"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux ipc700 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DMI 
[8086:d131] (rev 11)
lspci -knn: Subsystem: Intel Corporation Device [8086:]
lspci -knn: 00:03.0 PCI bridge [0604]: Intel Corporation Core Processor PCI 
Express Root Port 1 [8086:d138] (rev 11)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:08.0 System peripheral [0880]: Intel Corporation Core Processor 
System Management Registers [8086:d155] (rev 11)
lspci -knn: 00:08.1 System peripheral [0880]: Intel Corporation Core Processor 
Semaphore and Scratchpad Registers [8086:d156] (rev 11)
lspci -knn: 00:08.2 System peripheral [0880]: Intel Corporation Core Processor 
System Control and Status Registers [8086:d157] (rev 11)
lspci -knn: 00:08.3 System peripheral [0880]: Intel Corporation Core Processor 
Miscellaneous Registers [8086:d158] (rev 11)
lspci -knn: 00:10.0 System peripheral [0880]: Intel Corporation Core Processor 
QPI Link [8086:d150] (rev 11)
lspci -knn: 00:10.1 System peripheral [0880]: Intel Corporation Core Processor 
QPI Routing and Protocol Registers [8086:d151] (rev 11)
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82578DC 
Gigabit Network Connection [8086:10f0] (rev 05)
lspci -knn: Subsystem: Intel Corporation Device [8086:]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 5 Series/3400 
Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05)
lspci -knn: Subsystem: Intel Corporation Device [8086:4257]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series 
Chipset High Definition Audio [8086:3b56] (rev 05)
lspci -knn: Subsystem: Intel Corporation Device [8086:0034]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series 
Chipset PCI Express Root Port 1 [8086:3b42] (rev 05)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 5 Series/3400 
Series Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 05)
lspci -knn: Subsystem: Intel Corporation Device [8086:4257]
lspci -knn: Kernel driver in use: ehci_hcd

Bug#691366: wheezy 2012-10-24 daily built netinst

[Stephan Beyer]

Hi again,

On 10/25/2012 12:27 PM, Stephan Beyer wrote:

6. KDE programs work but only after some minutes


I tested several programs and wrote bug report #691406 [2] against
kde-standard containing further information. I hope that helps.

2.http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691406


As it turned out, the problem is not a genuine KDE problem.
The problem occured because the lo interface was down and no
connection to localhost could be established (and hence
timeouted). This has caused the long delays.

This means the problem is based on a broken installation.

I solved it for me, but imho it is a release-critical bug
in the installer or ifupdown.

Best
  Stephan


--
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/50892b44.1060...@uni-jena.de

Bug#681227: installation-reports: grub-install tries to install to a nonsense string

[willem kuyn]

Hi,

I tried to reproduce the bug in different settings.
- A virtual machine installation: grub always writes to /dev/sda
- A new lenova laptop booting from dvd: grub writes to /dev/sda
- Installation on an external usb disk: grub writes to /dev/sda
This is the original disk in the machine, while it was my
expectation that grub should write to the MBR of usb disk.
Booting from the usb disk is not possible only via /dev/sda.

The question is:
What is the configuration where grub writes to the MBR of /dev/sdb?

Willem


-- 
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/20121025144215.0c314...@amd5400.kuyn

Re: Unexpanded #DEBHELPER# tokens

[Niels Thykier]

On 2012-10-25 08:49, Niels Thykier wrote:
> On Oct 25, 2012 01:53 "Cyril Brulebois"  wrote:
>> Hello folks,
>>
>> [...]
>>
>> Lintian folks, maybe it would be nice to have some check to detect
>> unexpanded #DEBHELPER# tokens in maintainer scripts (as shipped in
>> binary packages)?
>>
>> Mraw,
>> KiBi.
>>
> 
> As far as I understand dh_installdeb and the code it uses, the #DEBHELPER#
> is removed when debhelper does the substitution.  So if it is actually
> present in the resulting script it wasn't substituted.
> 
> So yes, it should be doable. 
> 
> ~Niels
> 
> 
> 

Hi,

I did an archive-wide scan today and got the following results:

"""
binary:units/1.88-1/i386: postinst (line: 9)
binary:units/1.88-1/i386: postrm (line: 9)
udeb:cpuburn-udeb/1.4a-3/i386: postinst (line: 3)
udeb:debian-edu-profile-udeb/1.701/all: postinst (line: 5)
udeb:emdebian-archive-keyring-udeb/2.0.3/all: postinst (line: 12)
udeb:localechooser/2.48/i386: postinst (line: 7)
udeb:ltsp-client-builder/5.4.2-2/all: postinst (line: 236)
udeb:lvmcfg/1.27/all: postinst (line: 4)
udeb:partman-base/161/i386: postinst (line: 5)
udeb:ppp-udeb/2.4.5-5.1+b1/i386: postinst (line: 343)
udeb:simple-cdd-profiles/0.3.14/all: postinst (line: 81)
"""

Source is at [0], results obtained via [1].  In case you want to
reproduce it, it takes about 20-30 minutes to scan all those packages.

~Niels

[0] ~nthykier/check-debhelper-maint.pl on lintian.d.o

[1] On lintian.d.o:

~nthykier/bin/access-lintian-lab check-debhelper-maint.pl


-- 
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/50893cf6.1020...@thykier.net

Bug#685618: d-i: do not install mpt-status on vmware hardware

[Christopher Odenbach]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Hi,

I can confirm the PCI subsystem id of 15ad:1976 on current VMware
virtual machines:

root@kastner[~]# lspci -vvvnn | grep  LSI
00:10.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic
53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01)
Subsystem: VMware LSI Logic Parallel SCSI Controller [15ad:1976]

So this is clearly only a virtual SCSI controller, not a RAID
controller. Installing mpt-status is really useless in this case.
Please exclude it for this PCI subsystem id.

Thanks,

Christopher

- -- 
==
Dipl.-Ing. Christopher Odenbach
Zentrum fuer Informations- und Medientechnologien
Universitaet Paderborn
Raum N5.311
odenb...@uni-paderborn.de
Tel.: +49 5251 60 5315
==
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iD8DBQFQiVH5hxiCJKeLY0IRAvxfAJ97z2uMhfF/VC1gBPpPc0ve6ryT4wCdEnKV
apQNhKYpNlajsYSRYdVJltE=
=sLEX
-END PGP SIGNATURE-


-- 
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/508951f9@uni-paderborn.de

Processed: re: tasksel: execution aborted due to compilation errors

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #690594 [tasksel] tasksel: execution aborted due to compilation errors
Added tag(s) patch.

-- 
690594: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690594
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.b690594.13511885916643.transcr...@bugs.debian.org

Bug#690594: tasksel: execution aborted due to compilation errors

[Michael Gilbert]

control: tag -1 patch

Hi,

I've uploaded an nmu fixing this issue to delayed/7.  The extra time
is in case you want to do a maintainer upload instead.  See attached
patch.

Best wishes,
Mike


tasksel.patch
Description: Binary data

Bug#680084: os-prober: postinst script gets stuck

[Michael Gilbert]

> Maybe some information about the disk layout helps, too:
>
> /dev/sda is the only disk installed.
>
>   /dev/sda1   /boot ext4
>   /dev/sda2   encrypted physical volume for lvm2:
>
>   /dev/mapper/pv00physical volume
>   /dev/mapper/vg00-root   / filesystem ext4
>   /dev/mapper/vg00-swap   swap
>   /dev/mapper/vg00-root2  empty ext4
>   /dev/mapper/vg00-export empty ext4

Is this the contents of your /etc/fstab?  If so, using "empty" as the
mount point could be part of the problem.  If this is the case, could
you try changing "empty" to a real mount point?

Thanks,
Mike


-- 
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/CANTw=MPZ9SmH9Y8Ay0BoczrO=-5EYSgx=5q4y5pqrgodg9b...@mail.gmail.com

Please update d-i manual translations for Wheezy now

[Holger Wansing]

[Again sorry for cross-list posting]

Hello all,

Holger Wansing  wrote:
> - I did a complete checkout of the manual in revision before my bad commit
> - update manual/en
> - perform the usual po|pot update process (with the merge_xml.awk script 
>   fixed with the patch by nabetaro 
>   (thanks for providing this so quick, Nozomu!))
> - copy the changed files to my local svn tree
> - and commit them.
> 
> 
> So, at the end, all should be fine now.

Caused by a corrupted script (and me not noting that the script has failed,
since there was no error message) I created and committed incorrect po files, 
and translators have worked on them (notably Miguel, Yuri and Ji). 
Sorry guys, thanks for your time, but your work unfortunately was of no 
avail and had to be reverted.

Now that the po files are correct, you will have to start again.
I am really sorry!

Nevertheless:
Translators, please update your translations, if you have time.


Thanks

Holger

-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 3.0.2
under  D e b i a n   G N U / L I N U X   6.0  ( S q u e e z e )
Registered LinuxUser #311290 - http://counter.li.org/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


-- 
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/20121025205018.9857e539.li...@wansing-online.de

PowerPC bootp+tftp Network Boot: "method 'load' failed 00000300, newer yaboot version, alternate kernel images

[Patrick Fitzmorris]

Attempting to boot a Powerbook over the network has been a frustrating
endeavor. I did it once in the past with this machine, installing
Lenny. It seems little has changed, except that now it doesn't work.
Here's a snippet of output:

Welcome to yaboot version 1.3.13
Enter "help" to get some basic usage information
boot: install
Please wait, loading kernel...

CLIENT: [mac address] [IP]
SERVER: [mac address] [IP] [Hostname]
Transfer FILE: vmlinux [it pauses here for a little bit] method 'load'
failed 0300

Can't read Elf e_ident/e_type/e_machine info
boot:


Looking through the mailing list archives, it looks like the problem
is that the kernel image is too large, at 6.7 MB, for yaboot to
successfully load it. (does anyone test the functionality of the ppc
netboot images anymore?)

Is there any way to cut it down to 6 MB or less? Perhaps by using an
older kernel, or excluding some of the fancier features? My research
indicates that 6 MB's as large as yaboot 1.x.x will go.

Additionally, yaboot 1.1.13 is more than eight years old now. 1.1.17
is out and has been since last october, and includes, among other
things, improved netboot functionality, with IPv6 support and such. (i
suspect they'll be releasing 1.1.18 in the near future, since the
release schedule looks to be once a year or so) I think it's still
limited to 6 MB max kernel size.

Until it's been fixed, can you give me some tips? like, can I replace
the vmlinux image and initrd image, without having to assemble a
custom mini.iso? where should I look for info on the recommended
procedure? my google work hasn't been very fruitful so far, so i
though I'd ask the experts.


-- 
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/cafpxt5+amq51bzyeo1oqxn5mdhqgs5fwahkddmnuattvsac...@mail.gmail.com

Re: PowerPC bootp+tftp Network Boot: "method 'load' failed 00000300, newer yaboot version, alternate kernel images

[Lennart Sorensen]

On Thu, Oct 25, 2012 at 11:39:22AM -0700, Patrick Fitzmorris wrote:
> Attempting to boot a Powerbook over the network has been a frustrating
> endeavor. I did it once in the past with this machine, installing
> Lenny. It seems little has changed, except that now it doesn't work.
> Here's a snippet of output:
> 
> Welcome to yaboot version 1.3.13
> Enter "help" to get some basic usage information
> boot: install
> Please wait, loading kernel...
> 
> CLIENT: [mac address] [IP]
> SERVER: [mac address] [IP] [Hostname]
> Transfer FILE: vmlinux [it pauses here for a little bit] method 'load'
> failed 0300
> 
> Can't read Elf e_ident/e_type/e_machine info
> boot:
> 
> 
> Looking through the mailing list archives, it looks like the problem
> is that the kernel image is too large, at 6.7 MB, for yaboot to
> successfully load it. (does anyone test the functionality of the ppc
> netboot images anymore?)
> 
> Is there any way to cut it down to 6 MB or less? Perhaps by using an
> older kernel, or excluding some of the fancier features? My research
> indicates that 6 MB's as large as yaboot 1.x.x will go.
> 
> Additionally, yaboot 1.1.13 is more than eight years old now. 1.1.17
> is out and has been since last october, and includes, among other
> things, improved netboot functionality, with IPv6 support and such. (i
> suspect they'll be releasing 1.1.18 in the near future, since the
> release schedule looks to be once a year or so) I think it's still
> limited to 6 MB max kernel size.

That would be sad.

> Until it's been fixed, can you give me some tips? like, can I replace
> the vmlinux image and initrd image, without having to assemble a
> custom mini.iso? where should I look for info on the recommended
> procedure? my google work hasn't been very fruitful so far, so i
> though I'd ask the experts.

wheezy has a newer yaboot version.  Maybe it would work.  Could try and
see if it boots or not.  Would be a clue at least.

Changing the kernel would require a custom iso since the modules have
to match the kernel.

The yaboot in wheezy (1.1.16) has a changelog entry that mentions fixing
support for kernel+initrd that uncompressed is bigger than 12MB.  That is
probably the issue you are hitting.  1.3.16 should have at least 20MB
now for the uncompressed kernel+initrd, and on some systems even more
than that.

-- 
Len Sorensen


-- 
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/20121025190949.gt18...@csclub.uwaterloo.ca

d-i 7.0 beta3 comments

[Miroslav Kure]

Hello,

after several years of living in the cave I have bought myself
somewhat modern computer with EFI BIOS, SSD storage and all the
fancy goodies like CPU with virtualization support.

The installation using amd64 beta3 netinst cd was painless as usual,
I just want to highlight few points:

 * EFI boot from CD / GPT partitioning with EFI partition / grub-efi
   installation worked like a charm - thanks Steve!


 * Installer did not mount my target ext4 partitions on SSD drive with
   'discard' option / it was not possible to choose 'discard' option
   in partman.

   Some discussion about TRIM/discard happened earlier this year:
   http://lists.debian.org/debian-boot/2012/03/msg00184.html


 * os-prober did not recognize Windows 7 boot loader on the EFI boot
   partition:
 - Windows entry does not appear in the grub boot menu
 - clock setup assumed Debian is the only system and set hw
   clock to UTC

   Patch for this has been proposed here:
   http://lists.debian.org/debian-boot/2012/10/msg00185.html

All in all, great job everybody!
-- 
Miroslav Kure


-- 
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/20121025193037.ga29...@pharaoh.inf.upol.cz

Re: PowerPC bootp+tftp Network Boot: "method 'load' failed 00000300, newer yaboot version, alternate kernel images

[Rick Thomas]

On Oct 25, 2012, at 11:39 AM, Patrick Fitzmorris wrote:


(does anyone test the functionality of the ppc
netboot images anymore?)


Well, I try...  I have a number of old PowerPC Macs that I keep just  
for the purpose.  I haven't tried network booting yet.  Can you give  
me some pointers on how it's done?


Thanks!

Rick


--
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/9d3657d5-6abc-4e46-b21c-584acede8...@pobox.com

Re: PowerPC bootp+tftp Network Boot: "method 'load' failed 00000300, newer yaboot version, alternate kernel images

[Patrick Fitzmorris]

Oh, well.
I used the bootpd and tftpd that ship with OS X10.5 (not the server
edition). If you want to do the same,  then do this:

Tweak /etc/bootpd.plist* to disable all dhcp features, since your home
network probably already has a DHCP server, and Open Firmware only does
bootp, prior to version 3.

Put an entry in  /etc/bootptab* for the target system, giving it the same
IP the DHCP server gives it when it's fully booted into an OS, [and putting
in "yaboot" for the bootfile. (this doesn't actually work)]**

Enable the daemons with launchd, like this:
sudo launchctl load -F /System/Library/LaunchDaemons/tftpd.plist
sudo launchctl load -F /System/Library/LaunchDaemons/bootps.plist
(the -F is to override the "Disabled" string in the plists, which prevents
them from coming up on [re]boot)

Copy all the files from the mirror to /private/tftpboot/

Bring the target system up in Open Firmware, type in: boot enet:0,yaboot
[if the bootfile entry had worked, then you could, theoretically, just hold
the N key down, instead of invoking Open Firmware]

Install! Or do a dry run, i guess.

*The OS X bootpd does not use the same syntax! see:
bootpd(8)
bootptab(5)

**for reasons which I cannot fathom, OS X's bootpd prepends
"/private/tftpboot/" on the bootfile path it sends to the target system,
unless the bootfile path in the bootptab is already an absolute path. For
reasons which I cannot fathom, the tftpd throws an error code 2 if you try
to fetch files by anything other than a path relative to /private/tftpboot,
with NO leading / allowed. This means that using the Netboot hotkey on the
target system won't work, you must use the Open Firmware prompt


OR, you could just install a tftpd and bootpd on your Linux box, configure
more or less the same, copy the files to the correct dir, and bring up the
target in Open Firmware. booting with the same command (you can probably
omit the ",yaboot" in this case)

On Thu, Oct 25, 2012 at 12:41 PM, Rick Thomas  wrote:

>
> On Oct 25, 2012, at 11:39 AM, Patrick Fitzmorris wrote:
>
>  (does anyone test the functionality of the ppc
>> netboot images anymore?)
>>
>
> Well, I try...  I have a number of old PowerPC Macs that I keep just for
> the purpose.  I haven't tried network booting yet.  Can you give me some
> pointers on how it's done?
>
> Thanks!
>
> Rick
>
>

Re: PowerPC bootp+tftp Network Boot: "method 'load' failed 00000300, newer yaboot version, alternate kernel images

[Patrick Fitzmorris]

Oh!

That worked perfectly, thank you.

Is the changelog in question viewable somewhere?
the one I was referring to, bundled into the tarball for 1.3.17 from
yaboot.ozlabs.org, doesn't go past 1.3.13. All the info I had on more
recent versions came from the project homepage, which as you can probably
see, is pretty sparse.

Thanks again. I was really not looking forward to fiddling with it much
more.
On Thu, Oct 25, 2012 at 12:09 PM, Lennart Sorensen <
lsore...@csclub.uwaterloo.ca> wrote:

> On Thu, Oct 25, 2012 at 11:39:22AM -0700, Patrick Fitzmorris wrote:
> > Attempting to boot a Powerbook over the network has been a frustrating
> > endeavor. I did it once in the past with this machine, installing
> > Lenny. It seems little has changed, except that now it doesn't work.
> > Here's a snippet of output:
> >
> > Welcome to yaboot version 1.3.13
> > Enter "help" to get some basic usage information
> > boot: install
> > Please wait, loading kernel...
> >
> > CLIENT: [mac address] [IP]
> > SERVER: [mac address] [IP] [Hostname]
> > Transfer FILE: vmlinux [it pauses here for a little bit] method 'load'
> > failed 0300
> >
> > Can't read Elf e_ident/e_type/e_machine info
> > boot:
> >
> >
> > Looking through the mailing list archives, it looks like the problem
> > is that the kernel image is too large, at 6.7 MB, for yaboot to
> > successfully load it. (does anyone test the functionality of the ppc
> > netboot images anymore?)
> >
> > Is there any way to cut it down to 6 MB or less? Perhaps by using an
> > older kernel, or excluding some of the fancier features? My research
> > indicates that 6 MB's as large as yaboot 1.x.x will go.
> >
> > Additionally, yaboot 1.1.13 is more than eight years old now. 1.1.17
> > is out and has been since last october, and includes, among other
> > things, improved netboot functionality, with IPv6 support and such. (i
> > suspect they'll be releasing 1.1.18 in the near future, since the
> > release schedule looks to be once a year or so) I think it's still
> > limited to 6 MB max kernel size.
>
> That would be sad.
>
> > Until it's been fixed, can you give me some tips? like, can I replace
> > the vmlinux image and initrd image, without having to assemble a
> > custom mini.iso? where should I look for info on the recommended
> > procedure? my google work hasn't been very fruitful so far, so i
> > though I'd ask the experts.
>
> wheezy has a newer yaboot version.  Maybe it would work.  Could try and
> see if it boots or not.  Would be a clue at least.
>
> Changing the kernel would require a custom iso since the modules have
> to match the kernel.
>
> The yaboot in wheezy (1.1.16) has a changelog entry that mentions fixing
> support for kernel+initrd that uncompressed is bigger than 12MB.  That is
> probably the issue you are hitting.  1.3.16 should have at least 20MB
> now for the uncompressed kernel+initrd, and on some systems even more
> than that.
>
> --
> Len Sorensen
>

Re: PowerPC bootp+tftp Network Boot: "method 'load' failed 00000300, newer yaboot version, alternate kernel images

[Lennart Sorensen]

On Thu, Oct 25, 2012 at 02:36:48PM -0700, Patrick Fitzmorris wrote:
> Oh!
> 
> That worked perfectly, thank you.
> 
> Is the changelog in question viewable somewhere?
> the one I was referring to, bundled into the tarball for 1.3.17 from
> yaboot.ozlabs.org, doesn't go past 1.3.13. All the info I had on more
> recent versions came from the project homepage, which as you can probably
> see, is pretty sparse.

The one I found mentioned 1.3.14, but nothing since.

-- 
Len Sorensen


-- 
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/20121025214807.gu18...@csclub.uwaterloo.ca

Bug#691366: wheezy 2012-10-24 daily built netinst

[Philipp Kern]

On Thu, Oct 25, 2012 at 12:27:12PM +0200, Stephan Beyer wrote:
> To be more concrete, the /etc/network/interfaces file looks like this:
> -- snip --
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
> 
> # The loopback network interface
> auto lo
> iface lo inet loopback
> 
> # The primary network interface
> allow-hotplug eth0
> #NetworkManager#iface eth0 inet dhcp
> # This is an autoconfigured IPv6 interface
> #NetworkManager#iface eth0 inet6 auto
> # Activate RFC 4941 privacy extensions for outgoing connections. The
> # machine will still be reachable via its EUI-64 interface identifier.
> privext 2
> -- snap --
> 
> And the error message is:
> /etc/network/interfaces:15: misplaced option
> ifup: couldn't read interfaces file "/etc/network/interfaces"
> 
> Looks pretty dangerous. However, as mentioned, everything worked though.
> (In the meantime I commented out the "privext 2" line and the error
> message vanished.)

Added to the errata[1], thanks.

@d-boot: I guess that means that we should really merge Sorina's netcfg
patchset for n-m integration and get rid of that blacklisting script.

Kind regards
Philipp Kern

[1] http://www.debian.org/devel/debian-installer/errata
Might take a few hours to get visible.


-- 
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/2012102522.ga21...@hub.kern.lc

Bug#688297: Wheezy beta 3 working on old Packard Bell

[Bertil]

Just wanted to inform that with beta 3 release of wheezy, the previous reported 
beta 2 non-bootable installer problem does not exists anymore. Now the old 
Packard Bell machine is up and running as expected.