Plans for di-netboot-assistant (and debian-installer-netboot-***)
We had a discussion during DebConf about di-netboot-assistant.
Here are the ideas we gathered
Verifying netboot image signatures
---
netboot images for Debian are already signed by Release file
1. check SHA256SUM only
2. download the Release file
3. verify the GPG signature for SHA256 only
gpgv --keyring /usr/share/keyrings/debian-role-keys.gpg
Daily image ?
TODO! note: the HTTP directory hierarchy for Daily and regular
release aren't the same.
Easier installation of netboot images
-
Idea: Installing a debian-installer-netboot-*** image should invoke
di-netboot-assistant in postinst.
di-netboot-assistant
Suggests: debian-installer-netboot-amd64
Suggests: debian-installer-netboot-i386
debian-installer-netboot-{amd64,i386}
Recommends: di-netboot-assistant
in postinst
= di-netboot-assistant install --package=debian-installer-netboot-amd64
Note: each time the debian-installer-netboot-amd64 is upgraded on the
system, then debian-installer-netboot-amd64 overwrites that TFTP
directory.
Debian-CD
Put a copy of the netboot image on the DVD.
Which format should be on the DVD? .deb, tarball, extracted ?
Which netboot image arch should be present on which DVD image ?
Validate the di-source file.
implement a feature to make sure that all the netboot images listed in
/etc/di-netboot-assistant/di-source.list exist
Andreas and Franklin
Bug#442225: Reporting false-positive to Anti-virus vendor
Hello, While it was a good idea to report the bug here so other users are aware of the problem, the best way to solve this issue is to submit the false positive to the anti-virus editor. Do you know if the problem still occurs? (IMHO, one should not use an anti-virus which editor don't let me submit false positive... what would you do if your anti-virus were to prevent you for using an important program, like an accounting or bank account management tool?) Thanks, Franklin -- 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/1271500043.7450.1927.ca...@solid.paris.klabs.be
Re: di-netboot-assistant update for experimental
On Thu, 2009-11-19 at 08:42 +0100, Frans Pop wrote: On Thursday 19 November 2009, Frank Lin PIAT wrote: I'll test it. If that work, would it be ok to modify the default netboot images ? I have tested multiple initrd with pxelinux, using initrd=initrd.gz,extra.cpio.gz and that works. Actually, initrd don't have to be on it's own line in pxelinux configuration file (as opposed to what the documentation seems to imply). So there is no need to change D-I images. Not sure that I understand you correctly, but I don't think it would be a good idea to list a morestuff.cpio.gz in standard images if we don't ship it in those standard images. Sure. It is up to the system admin (and/or di-netboot-assistant) to add more images (both in the bootloader configuration file and the actual cpio file). Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: di-netboot-assistant update for experimental
On Tue, 2009-11-17 at 20:08 +0100, Frans Pop wrote: On Tuesday 17 November 2009, Frans Pop wrote: Wouldn't it be simpler to just allow a user to specify the image on the command line using a new command? Something like: di-netboot-assistant custom --name=mybuild filename The name option could be optional with a default of custom. The architecture can AFAIK be derived from the contents on the tarball. But not for all arches (the ones that have a single image instead of a tarball), so maybe in that case you could just require the --arch option to be set too. I have started to work on this scheme. I think the uninstall etc. options should just work as AFAIK it depends on your registration of the images, and not their origin. BTW, a tarball can contain both a newt and a gtk installer; It would be great if they could both be added to the menu (as custom and custom-gtk?). di-netboot-assistant custom --name=mybuild --arch=i386 \ --alias=foo-gtk filename Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: di-netboot-assistant update for experimental
On Tue, 2009-11-17 at 18:59 +0100, Frans Pop wrote: On Tuesday 27 October 2009, Frank Lin PIAT wrote: Allow preseeding using TFTP (reqested by Otavio) --- 3. Or is it possible to pass multiple initrd= to a given Kernel? I have investigated this situation a little bit. The most elegant way to introduce preseeding (and firmware) capability seems to use bootloaders capability to concatenate multiple initrd cpio archives. At least Syslinux (since 2005)[1] and Yaboot should support this (elilo don't seems to support it, yet) Syslinux/PXELinux, the syntax is |label install |menu label ^Install |menu default |kernel debian-installer/lenny/i386/linux |append vga=normal |initrd=path/to/initrd.gz,path/to/morestuff.cpio.gz For Yaboot, the syntax is |image=/vmlinux | label=install | initrd=/initrd.gz|morestuff.cpio.gz | initrd-size=14030 | append=-- | read-only I'll test it. If that work, would it be ok to modify the default netboot images ? Franklin [1] http://syslinux.zytor.com/archives/2005-January/004474.html http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=commitdiff;h=a966e54c [2] http://hermes.ppckernel.org/cgi-bin/man/man2html?5+yaboot.conf -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: di-netboot-assistant update for experimental
Frank Lin PIAT wrote: On Sun, 2009-10-25 at 06:20 +0100, Frans Pop wrote: On Friday 16 October 2009, Frank Lin PIAT wrote: I have finally resolved and merged a bunch of patch I had for di-netboot-assistant. [..] I have worked on some patch to clean-up the code, and fix buggy package removal behaviour. I'll merge them by tomorrow evening. I have two feature request that are pending, and I need your help: Using local repository (requested by fjp) I wondered how to address this. I now think it would be possible if the images where structured like this (we can switch arch and dist folder hierarchy): . |`-i386 ||`-lenny || |`netboot.tar.gz || ` MD5SUMS ||`-daily-2009-10-28 || |`netboot.tar.gz || ` MD5SUMS | `-daily-2009-10-28 | |`netboot.tar.gz | ` MD5SUMS `-amd64 |`-lenny | |`netboot.tar.gz | ` MD5SUMS `-daily-2009-10-28 |`netboot.tar.gz ` MD5SUMS Does it suite your needs? (That could be used to ship netboot in Debian-Live CDs) Allow preseeding using TFTP (reqested by Otavio) --- 1. Is it possible to simply concatenate multiple tar.gz files? 2. Is it possible to simply concatenate multiple tar in one .gz files? 3. Or is it possible to pass multiple initrd= to a given Kernel? 4. Or Do I have to modify the tar.gz files. The above scheme could also be used to include/embedded firmware Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: di-netboot-assistant update for experimental
On Sun, 2009-10-25 at 06:20 +0100, Frans Pop wrote: On Friday 16 October 2009, Frank Lin PIAT wrote: I have finally resolved and merged a bunch of patch I had for di-netboot-assistant. [..] I don't think experimental is the right choice here. I doubt you would get anybody to actually test it from experimental. The new way to handle prefix (was) an experimental. If you are happy with it, I think you should just upload to unstable and deal with bug reports ASAP when they come in. Yep, I am ashamed that some of the bugs have been pending for many months. IMO the ::/ prefix that looks to be required now should be documented[..] Done (I mean, I hope it is clear enough now) There is also an upgrade problem. It looks like when I upgrade that the default configs do get changed, but not the actual existing configs in /var/lib/di-netboot-assistant/, nor the generated ones under the tftpboot directory. So after I changed my DHCP server config to drop option 210, nothing works anymore. Please provide clear instructions how to move from an old setup to a new one. I have included a migration script. The remaining action are explained in NEWS.Debian but they should actually be optional. I tried making the changes manually, but ended up with a broken setup. Not sure if that means the ::/ prefix does not work for me or if I missed something... Adding ::/ manually everywhere would be very tedious. My script should be idempotent, so if you downgrade and re-repgrade, you should be fine (unless you actually broke a repository, which you can simply purge/reinstall). Could you also fix the fact that the generated debian-installer/pxelinux.cfg/default file gets double newlines between items? This is fixed for new installed repositories (the transition won't be really nice). Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
di-netboot-assistant update for experimental
Hi all, I have finally resolved and merged a bunch of patch I had for di-netboot-assistant. (Frans, could you have a look at it and upload it to experimental please). This version is Experimental, because of feature #1 below. The major features are: 1. Drop PXELinux's DHCP option 210 requirement (pathprefix=/) 2. Allow customizing netboot parameters. 3. Allow saving a repository as a different name, like saving the daily images as $(date +%a) 4. allow running by a non-privileged user (Thanks to Daniel Gillmor) The actual changelog below. Your feedback is welcome. Franklin FYI, My roadmap (post Squeeze?) still to includes: - Allow preseeding, by embedding file preseed in initrd - Use local repository - Download/Embed Firmware - Allow embedding on D-I or Live-CD for easy Netboot setup. di-netboot-assistant (0.37) unstable; urgency=low * DHCP option 210 (pathprefix=/) isn't needed anymore. (Closes:#498206) * add options di-args and target-args for boot parameters. * Improve command line argument parsing. * Implement --alias option. * Improve comments in di-sources.list * Improve di-netboot-assistant manpage. * allow running by a non-privileged user (Closes:#503359, Thanks to Daniel Kahn Gillmor for the patch) * Change umask to allow group writables files. * Use dpkg --print-architecture to query arch. * Display failed URL without requiring --verbose (Closes:#493418, Thanks to Chris Lamb) * Output status messages to STDOUT, not STDERR (Closes:#493426, Thanks to Chris Lamb) * Default PROMPT to 0 in pxelinux.HEAD (Closes:#493548, Thanks to Chris Lamb) * Bump standards to 3.8.3 * Fetch daily images from d-i.debian.org -- Frank Lin PIAT fp...@klabs.be Mon, 31 Aug 2009 21:40:20 +0200 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Risk of dataloss using
Hello, Someone posted this warning on the the wiki: http://wiki.debian.org/Xen?action=diffrev2=90rev1=89 I suppose it would be nice to replace the line: disk = ['phy:hda1,xvda,w'] with something safer in the sample file(s): ftp://ftp.debian.org/debian/dists/lenny/main/installer-i386/current/images/netboot/xen/xm-debian.cfg Thanks, Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Illustrated Guide to Installing Debian GNU/Linux
Hello, On Wed, 2009-02-18 at 13:01 -0800, Praveen A wrote: 2009/2/18 Eric Doviak e...@doviak.net: For people who are new to GNU/Linux and are simply trying to install Debian on a home desktop, I wrote an Illustrated Guide to Installing Debian GNU/Linux.[3] Some comments, Now openjdk is in debian so it is better to suggest it over gcj. Just a quick comment regarding the Appendix D Suggested Packages. Your recommendation aren't consistent with Debian. * openoffice, gimp, ekiga, pigin... are installed by default[1] so there is no need to explain how to install them. * Debian has chosen to install openoffice rather that abiword and gnumeric, so it's awkward that your first example is to install it. Also the wiki pages http://wiki.debian.org/WindowsEquivalent aims to list equivalent application, *in* Debian. It isn't complete yet. Great guide, thanks Franklin [1] reminder, to list package installed by default (without dependencies), use tasksel install -t desktop aptitude search ~t^desktop\$ ~t^gnome-desktop$ The base system is: aptitude search ~prequired ~pimportant ~pstandard A few other package could be auto-installed like popcon and hardware related packages. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Netboot and firmware
On Wed, 2009-05-27 at 10:32 -0300, Otavio Salvador wrote: On Tue, May 26, 2009 at 7:35 PM, Frank Lin PIAT wrote: I'll probably add an option like FIRMWARE_IN_INITRD=(none|all|$firmwarename) (but I would rather default to all). I'd default to 'none'. I wasn't clear that all means all firmware present in /lib/firmware/ of the host system... I now realize the I have a major problem, fetching and installing the proper firmware version :( Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Netboot and firmware
Hello, I have just noticed Marco d'Itris note on http://wiki.debian.org/DebianInstaller/NetbootFirmware Do you think it would be a problem if di-netboot-assistant was concatenating all local firmware, to the init.rd files? Are we likely to hit some size limit? I'll probably add an option like FIRMWARE_IN_INITRD=(none|all|$firmwarename) (but I would rather default to all). Thanks, Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Proposed changes to linux-2.6
On Sat, 2009-05-23 at 22:57 +0200, Bastian Blank wrote: On Sat, May 23, 2009 at 04:41:16PM +0200, Bastian Blank wrote: On Wed, May 20, 2009 at 05:32:48PM +0200, Bastian Blank wrote: I intend to do the following changes to linux-2.6: * Change i386/686(-bigmem) to include generic optimizations, should work on all x86 then. Maybe rename them somehow later. I checked it again, this is incorrect. A generic optimized kernel with a 686 setting will not work on older cpus. Virtual machines (including those from Redmond) probably needs testing. Let me know when you have something I can test on Hyper-V, VirtualPC and ESX. (There are probably lots of candidates to test qemu, kvm, VirtualBox 12, vmware...) Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Re: Re: di-netboot-assistant - toward version 1.0
Hello,
I would like to fire-up a brainstorming for netboot images in Squeeze.
As far as I can say, there are two typical architecture:
* Move to .deb images
* Generalize and structure the .tar.gz files
Moving toward .deb images
=
Probably raises some problems:
* Are the image BYHAND?
* Images must be arch all (So any netboot server can netboot any arch)
* Would in imply extra delays, when we want to switch to a new kernel
revision during the release freeze?
* What about the daily builds: which repository? How to sign/upload?
* Turn di-netboot-installer into a debconf helper.
At the same time it has some advantages:
* Rely on dpkg to install.
* All the images are referenced in debian repository. There is no need
no maintain other repositories manually.
* Images are signed
Generalize and structure the .tar.gz files
==
(If we don't switch to .deb, I wish all arch could provide a .tar.gz
with some meta-data).
Problems/drawbacks:
* The opposite of .deb advantages :)
Advantages:
* Everyone knows how to un-tar a file, what ever the host.
* Less work/No migration (i.e keep using di-netboot-assistant
or a similar tool).
I have embedded below my previous email on this topic, which could seems
to advocate for .tar.gz (but I have no opinion yet).
Your feedback is welcome.
Franklin
On Wed, 2008-06-18 at 00:42 +0200, Franklin PIAT wrote:
Hello,
On Tuesday 03 June 2008, Franklin PIAT wrote:
I had a small home-made script to retrieve and untar Debian Installer
netboot images.
I've had a few though toward a di-netboot-assistant version 1.0 (read:
more robust with less heuristics). The problem is that today, di-n-a is
doing some black-magic to detect the bootloader, and determine which
files should be patched to rewrite the menu files according to the
location where the files got extracted.
What about the following two ideas (which should be done on the
debian-installer side, not on di-netboot-assistant side ;)
*** Pack D-I netboot images in a consistent way, for all archs.
Currently, some arch like arm and mips provide multiple individual
files, but no .tar.gz file, that's harder to fetch.
Also, some architectures (like sparc, alpha and hppa) provide a single
boot.img, but nothing else.
Providing consistent pack of files would help unpacking them.
Actually, I've fount the way the i386/ia64/amd64 tar.gz files are
arranged to be very convenient :
- It's a tar.gz, so it can be expanded on any [tftp server] system.
- It contains a common top directory (debian-installer/$arch), so
it's easy to rewrite the included configuration files, in case the
file is extracted in a different directory
('s/debian-installer\/$arch/foobar/').
This layout also has two nice side effects :
1.It's possible to provide a meta-data file, to describe the
content of the tar file (currently, it's version.info, but it
could be enhanced to contain arch, dist, bootloader type,
arch-variant, d-i variant... Also, another file could
contain individual files check-sums, etc
2.It's possible to *not* extract the meta-data file when the
netboot files are extracted.
(thanks to tar -zxf foo.tar.gz --strip=2)
*** Provide .Package and .Release like files
It would be great to have file that lists all the available
netboot for a given distribution, very similar to .Release and
.Packages files that are referenced in /etc/apt/sources.list.
Benefits :
- It would be possible to list all netboot images in a single place.
- It would be possible to provide checksum of those files.
- It would be possible to sign all those files.
What do you think about it ?
I don't think this could be achieved by Lenny, but it would be great to
have it in Lenny+1.
Franklin
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: DebConf: D-I Workshops and a D-I talk to explain and motivate?
On Mon, 2009-04-13 at 17:47 +0200, Luk Claes wrote: Official events have to be submitted in the Pentabarf interface before Wednesday if I'm not mistaken. Would it be ok if I submit D-I Work Sessions for during DebCamp? How long and how many do we want in that case? Does someone want to give a D-I talk during DebConf to explain how it all works, how people can help and why it's a cool project to work on? I submitted a talk about Hardware Report, Database and PopCon. Abstract: Hardware support implies two different points : Providing a Driver and configuring the system. We need a tool to collect information to improve both situation. - When Debian/Stable is prepared, we need to improve the devices support by improving the drivers and packages (identify most used devices, devices without driver, etc..) - Once Debian/Stable is released, the users needs some documentation : How a given system or device is supported by Debian/Stable and what extra configuration is needed to use it at it's best. I am working on a tool that collects the current list of hardware on a computer (through sysfs|lscpi... and hal|lsmod... ), then submit it to a central database. Once those data are loaded in a central database, we can make lots of useful statistics about the devices and modules that are actually used. I consider that this tool is closely related to D-I (I plan to ship a D-I package, so people can report [failing hardware] from D-I. The integration with reportbug will have to be discussed at that time) Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: The future of the D-I team
On Sat, 2009-02-28 at 09:37 +0100, Luk Claes wrote: Colin Watson wrote: On Thu, Feb 26, 2009 at 09:49:58PM +0100, Christian Perrier wrote: Now that the lenny release is over, I think it's time for all of us to gather and discuss what the D-I team currently is and what should be done for the lenny-squeeze release cycle (not technically speaking but first more on organisational issues). If we organize something called a team meeting to talk about this, who would attend? I would probably try to attend as I would like to get involved in d-i, though I'm not sure I'll find the time to help a lot... +1 Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: wiki.d.o/DebianInstaller
On Sun, 2009-03-01 at 13:01 +0100, hlf wrote: Curently, in wiki.debian.org, there are about one hundred pages begining with DebianInstaller. I think the structure should be different. I can do the renaming of the pages (and modify also the pages which link to thoses pages) I make a proposal. Feel free to make others. --- wiki.debian.org/DebianInstaller/ /Team On the wiki, the teams page should be named Teams/DebianInstaller. /Dev/Ports/PowerPC/OldWorld Rather than over-structuring the wiki page names, what about rewriting the index page (i.e http://wiki.debian.org/DebianInstaller ) Also, it's better to avoid renaming pages (cool URIs don't change[1]). Franklin [1] http://www.w3.org/Provider/Style/URI -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: 40r6 locks up during boot
On Sun, 2009-01-11 at 23:31 +0900, John wrote: I'm running Windows Virtual Server on Windows Server 2003 on and HP DC5950, Athlon 4550B CPU running in IA32. It's not clear to me whether it has hardware virtualisation, I thought all recent AMD CPUs do, but virtual PC (which got removed when I installed Server 2003) said not. It's not configurable in the BIOS. Hi, Those pages my help: http://wiki.debian.org/MicrosoftVirtualPc2007/lenny http://wiki.debian.org/WindowsServerHyperV I'll try to write a page about MicrosoftVirtualServer2003 at some point. Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514098: debootstrap: /dev/fd isn't created
Package: debootstrap Version: 0.3.3.2etch1 Severity: normal Hi, I have installed a lenny VM under etch using xen-create-image (package:xen-tools). It uses debootstrap to install the guest system. The symlink /dev/fd wasn't created during the installation. I am not sure which package should create the file (debootstrap, mkinitramfs/udev...) This seems to be fixed in Lenny because running debootstrap lenny ... on a lenny system works fine. Typically, bash_completion expects to find it (at bash prompt, type ls then press tab), and complains with: ls -bash: /dev/fd/62: No such file or directory -bash: /dev/fd/60: No such file or directory As a workaround, one can manually execute: ln -s /proc/self/fd /dev/fd Regards, Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [net boot doc] please recommend atftpd instead of tftpd-hpa
Hello, Luca Favatella wrote: [please cc me when replying as I am not subscribed to the debian-boot mailing list] [..] Initially I tried to use tftpd-hpa, as recommended in [d-i manual] (we recommend tftpd-hpa). From the same guide, I read Debian packages will in general set this up correctly by default when they are installed , but it is not true for tftpd-hpa; instead it is true for atftpd. I lost at least 2 hours trying to set it up. Then I switched to atftpd and all worked flawlessly with my settings. Could you clarify what was the problem with tftpd-hpa? (behaviour/error message...) Do you think that some part of the documentation could be improved? which part/which step/what topic? Regards, Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Call for testing of RC2 images
Frank Lin PIAT wrote: On Thu, 2009-01-29 at 11:19 -0200, Otavio Salvador wrote: The Debian-CD Team has built the images based on RC2 installer and I'd like to ask for some tests before we finally announce the release. The images are available at http://cdimage.debian.org/cdimage/.lenny_bibble/ Please send feedback to the mailing list (even successful ones). I could run a few offline tests, under i386 Qemu-KVM: Netinst CD install = OK crypto install (dm-crypt) = OK - rescue: prompt for passord = OK - gtk rescue = OK 32 mb ram install (text)= ok 48 mb ram install (newt)= ok rescue mode = ok graphical rescue mode = ok graphical (gtk) = ok The pxelinux menu of the following images _looks_ sensible and _seems_ to provide correct options for all entries: debian-Lenny-DI-rc2-i386-businesscard.iso debian-Lenny-DI-rc2-i386-netinst.iso debian-Lenny-DI-rc2-i386-amd64-source-DVD-1.iso debian-Lenny-DI-rc2-amd64-i386-powerpc-netinst.iso (mutli-arch+multi-desktop needs to scroll the menu, but that's a known behaviour) Regards, Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Call for testing of RC2 images
On Thu, 2009-01-29 at 11:19 -0200, Otavio Salvador wrote: The Debian-CD Team has built the images based on RC2 installer and I'd like to ask for some tests before we finally announce the release. The images are available at http://cdimage.debian.org/cdimage/.lenny_bibble/ Please send feedback to the mailing list (even successful ones). I have downloaded a few images, but since I'm away for the weekend, I won't have much time to run the tests... I'll let you know how things goes. Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513080: installation-report: Thinkpad T400 on Lenny (w/ intel graphics)
reassign 513080 xserver-xorg-video-intel -- Hi, On Mon, 2009-01-26 at 08:37 +0100, Frank Lin PIAT wrote: The T400 is very well supported out of the Box, eventhough it's very recent model (BTW, the R400 and T500 should quite be similar). (SATA runs in AHCI, Xorg video driver, event brightness keys works ;) [..] The main configuration step is to configure xorg.conf to use intel driver. lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07) The vesa driver was installed during Lenny RC1 installation. However, the intel driver provides a much better support, see : http://wiki.debian.org/InstallingDebianOn/Thinkpad/T400/lenny Regards, Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513080: installation-report: Thinkpad T400 on Lenny (w/ intel graphics)
Package: installation-reports Version: 2.38 Severity: normal -- Package-specific info: Boot method: network Image version: http://people.debian.org/~joeyh/d-i/images/daily/netboot/netboot.tar.gz (Lenny's daily) 20090123-10:05 Date: 2009-01-23 Machine: Lenovo Thinkpad T400 (w/ intel graphics) Partitions: /manual/ Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [ ] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: The T400 is very well supported out of the Box, eventhough it's very recent model (BTW, the R400 and T500 should quite be similar). (SATA runs in AHCI, Xorg video driver, event brightness keys works ;) On this model, the Wifi card is an Intel 5100, which isn't supported in Lenny[1]. The main configuration step is to configure xorg.conf to use intel driver. - Suspend feature should be tested further, it's broken with vesa X driver. - The 3G card should be supported by 2.6.28 kernel (according to modinfo). I assume this bug can be forwarded to xserver-xorg-video-intel Franklin PS I don't own the laptop, and I have to return it, so I won't be able to anwser further questions. PPS As usually, I have written a wiki page http://wiki.debian.org/InstallingDebianOn/Thinkpad/T400/lenny [1] http://wiki.debian.org/iwlagn and http://bugs.debian.org/501157 == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=5.0 (lenny) - installer build 20090123-10:05 X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == umame -a: Linux t400-lenny 2.6.26-1-486 #1 Sat Jan 10 17:46:23 UTC 2009 i686 unknown lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07) lspci -knn: 00:03.0 Communication controller [0780]: Intel Corporation Mobile 4 Series Chipset MEI Controller [8086:2a44] (rev 07) lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82567LM Gigabit Network Connection [8086:10f5] (rev 03) lspci -knn: Kernel driver in use: e1000e lspci -knn: Kernel modules: e1000e lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 03) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 03) lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 [8086:2946] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 [8086:2948] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci
Re: [RFC] New installer-settings component - please test and comment!
On Tue, 2009-01-13 at 23:06 +0100, Frans Pop wrote: On Tuesday 13 January 2009, Frank Lin PIAT wrote: If I understand correctly, the idea is to be able to be able to switch *easily* between standard and expert mode during the installation. This is a nice. Hmm. Have you tried booting in expert mode? I have quickly tested the updated images... The behaviour of the bug-free images is very much sensible ;) I like the Using expert mode isn't recommended notice. I still like the possibility to opt-out some DI steps. Being able to easily (and really), switch from expert mode to standard mode is really great for those who just needs expert mode in the firsts steps. I didn't fount any problem/drawback in this quick test. Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [RFC] New installer-settings component - please test and comment!
Hello Frans, On Tue, 2009-01-13 at 12:06 +0100, Frans Pop wrote: Over the past months I've been working on a new component that allows to change settings for the installer. [..] What I will say is: * it completely changes the concept of expert mode If I understand correctly, the idea is to be able to be able to switch *easily* between standard and expert mode during the installation. This is a nice. I took me a few minutes to understand how that's supposed to work (I though it was a bug or an incomplete implementation whereas it is just a matter of changing the wording) * you can now have the main menu displayed optionally for both high and medium prio installs! Being able to opt-in or opt-out some steps (like dmraid) is a great idea. (would it be possible to switch between [standard|expert|skip]?) * for this demo only a limited number of settings are available: - changing the installation level - activating support for dmraid and multipath * demo images use vga=788 for newt frontend For the demo there are a few implementation differences between the activation of dmraid and multipath to show the versatility. Just try changing those settings at different points during an installation. I haven't tested it yet. I'll sleep on it, and let you know If I have more ideas. Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Debian / hardware compatibility popcon
Hello Chris, [CC'ing debian-boot in case some other people are interested] For DebConf8, it seems that you planned to give a talk about hardware compatibility (according to penta). That's also something I am planning to work on [for Squeeze], and I wonder if you still plan to work on that? As far as I am concerned, I came to the conclusion that there are two separate needs: - On one side, we need to collect the devices on a computer (and may be try to figure-out which drivers are used). This could be use for two purposes: A. A hardware-popcon B. A tool to report devices, that would work under debian-installer (using the same code as above). - On the other side, there's a place for advance tool that would: A. Automatically try to detect if the devices is working (I don't know if you attended Bdale Garbee's talk at Debconf8) B. Prompt the user on how he consider his device is working. I am mainly interested in the first part (my priorities are: 1A, then 1B, then 2A, then 2B). Regarding the second part, smolt seems to become more and more popular: https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2008-December/006443.html I might setup a server too... but that would be it (since I had packaged it in Q2-2008). BTW, are you planning to go to Fosdem ? Franklin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Creating usb boot pendrives
Hi, For the record, there's a windows frontend to assist creating usb bootable pendrives. it's looks nice, probably compatible with our images (not tested), and it's GPL. Thanks for the anonymous who posted that on the wiki. Franklin [1] https://fedorahosted.org/releases/l/i/liveusb-creator/ [2] http://www.pendrivelinux.com/2008/06/02/usb-centos-5-live-install-via-windows/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [RFC] Consequences for official CD/DVD images for Lenny
Hi, [My two cents tips below] On Wed, 2008-12-03 at 23:32 +0100, Frans Pop wrote: Now that everybody has had a chance to take a look at the patches and try out the test images (ahem...) we should decide how to use the new options and what it will mean for the images we make available for Lenny. [..] The following images will remain essentially unchanged: - netinst/businesscard images for arches other than i386/amd64 - full CD images - KDE installation CD - alpha/hppa/ia64 multi-arch CD I have noticed that Ubuntu only advertises CD1 on their download page. I think it is really sensible: The CD-1 contains Xwindow, so a [new] user gets a usable desktop... even if he/she face network connectivity problem. Advanced users can still use netboot/BC/jigdo/DVD... netinst and businesscard (i386 and amd64 only) -- We can also add the option to select an alternative DE to the smaller images. After all, packages will be downloaded from a mirror anyway so we know all desktops will be available. The contents of the images themselves will not change. I see only benefits from this as general usability is improved. yes multi-arch images - The i386/amd64/powerpc CD is basically a netinst image, so that can get desktop=all to enable DE selection in the boot menu for i386 and amd64. The i386/amd64/powerpc DVD is more problematic as having all desktops will completely fill the DVD leaving no room for other packages with a high popcon score. Proposal is therefore to drop powerpc support from this DVD. With only i386 and amd64 there is still room for the top ~2600 packages on the DVD. PowerPC's popcon is steady (or even decreasing), probably because Apple don't sale any PPC system anymore. On the other hand, x86_64 system are now extremely popular now. I like the idea of such 2arch/4desktop/+2600pkg DVDs for events. Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [RFR/RFC] Multi-desktop CDs for lenny - take 2
[drop [EMAIL PROTECTED]
On Mon, 2008-12-01 at 03:05 +0100, Frans Pop wrote:
(Follow-up to http://lists.debian.org/debian-cd/2008/11/msg00048.html.)
I have done quite a bit of additional development since that previous mail
and things are now much nicer and implemented a lot cleaner.
Overview of changes:
- isolinux config files for additional desktops moved to subdirectories
- multi-arch multi-desktop is now supported
Who said Universal Operating System. :-)
- for light CD: separate rescue submenu on first isolinux screen
That's sensible. (even though a little,bit inconsistent with DVD)
BTW, I'm wondering whether light is misleading ( netinst). maybe
lightx, lightX or something else.
Finally a few comment on the images I tested:
* There's an empty /install folder on the CD, even though
/install.{386,amd} are used.
* The file /pxelinux.cfg/default is a symlink, which make it impossible
to use on FAT/NTFS file system. would it be possible to replace it
with a simple file containing : include ../boot-screens/syslinux.cfg
* The multi-arch (i386+amd64) advanced sub-menu needs scrolling
I'll try to have a look.
Thanks,
Franklin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Log from the D-I team meeting of Sat. Nov. 29th 20:00 UTC
Hi, On Sun, 2008-11-30 at 11:56 +0100, Christian Perrier wrote: I just linked the log of the D-I team meeting that happened yesterday, on the Meetings wiki page: http://wiki.debian.org/DebianInstaller/Meetings Sorry for missing Saturday's meeting. bubulle Next issue also has been well worked out: bubulle Multiarch CD directly boots in the amd64 installer bubulle franklin_: around? otavio This is a very small issue and I believe it's not worth the risk of a syslinux new upstream release only for it. I'd prefer to add it to errata. That was an important bug. Especially it used to prevent a regular user from choosing a i386 kernel, rescue mode, Graphical installer, etc. otavio Other problems were workarounded by Frans and Franklin bubulle but does the fix really need a new syslinux? No, IMO (YMMV) bubulle ok, so if the main problem is sorted with commited changes to the build system, then I think it's OK otavio IIRC the only remaining issue is that if he is on help and press enter it boots the wrong kernel (i386 iirc) AFAIK, the only remaining known issue is specific to VirtualBox: If one boots the CD, press enter on the Help menu to browse the help page, then pressing enter again will launch amd64 image instead of i386. This isn't a major problem because the kernel refuse to load. Typically the screen looks like: + | Loading /install.amd/vmlinuz | Loading /install.amd/initrd.gz...ready | This kernel requires an x86-64 CPU, but only detected an i686 CPU. | Unable to boot - please a kernel appropriate for your CPU. +--- otavio fjp: franklin_: can you confirm the above later? bubulle so, we just document the remaining bit in the errata, then I don't think it deserves to be documented, since the message is pretty clear. YMMV. otavio bubulle: if it is the last remaining issue; yes. Now, I'll test the multi desktop CDs. Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Multi-desktop CDs for lenny (was: Support lxde-desktop properly in lenny D-I RC2?)
On Sun, 2008-11-23 at 01:16 +0100, Frans Pop wrote: Steve and I have been brainstorming a bit about this and it looks like we'll be going for a combined light desktop CD after all, containing packages needed for both Xfce and LXDE desktop tasks. However, debian-cd will also support building LXDE only images. [..] A new idea that Steve suggested was to make the i386 and amd64 DVDs, and if possible also the i386/amd64 multi-arch DVD (with or without powerpc depending on space), support *all four* desktops. Universal OS, and user friendly. You raised the bar, again. Great job. Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [PROPOSAL] Identify tasks in the D-I team and assign them
On Thu, 2008-11-20 at 08:40 -0200, Otavio Salvador wrote: Christian Perrier [EMAIL PROTECTED] writes: wiki page with nice tables (one per section) and for each entry have room for a name and a backup name? This works fine and makes quite easy to find who does what. Here's a first attempt: http://wiki.debian.org/DebianInstaller/Tasks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505243: Multiarch CD directly boots in the amd64 installer
On Tue, 2008-11-18 at 12:55 +0100, Frans Pop wrote: (Switching to #505243 as that is the BR about the direct boot issue.) Hi Philip, On Tuesday 18 November 2008, Philip Hands wrote: On Mon, Nov 17, 2008 at 01:51:37PM +0100, Frans Pop wrote: If others want to give it a try: http://cdimage.debian.org/cdimage/unofficial/fjp/debian-50-amd64-i386 -BC-1.iso Just booted that under KVM -- it went straight through to a default install without any menu or boot prompt. I've built a new image with a small, but relevant change. Could you try that please? If it works I have an idea for an alternative solution based on a different analysis of what the problem in syslinux may be. So, I'll have one more image to test then. Hello Philip, Could you check the md5sum of the image you have tested is one of the the last two release listed below. What CPU and kernel do you use? I have tested two images debian-50-amd64-i386-BC-1.iso, with kvm on lenny-i386-on-i386-cpu and lenny-amd64-on-intel-core-2-duo: 2008-11-18 00:59 / 2cbb1cb9462896b50eed34bb47858631 (bug: duplicate default install in text.cfg) 2008-11-18 11:00 / 288d4aae033ecf74579d77647f411e04 (The one which properly uses ifcpu64.c32) Thanks, Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505773: debian-installer: Bootable netboot image for USB stick patch
On Mon, 2008-11-17 at 13:17 +0100, Frans Pop wrote: On Monday 17 November 2008, Otavio Salvador wrote: I'm not in the position to decide about the inclusion of that into the Installation Guide but I believe it would be a problem due the translation. I think we should keep two patches in a queue to be commited as soon as we open svn to squeeze work. Do anyone disagrees with me? I have a few minor, mostly practical, reservations against this. 2) Problem with these small USB images and the way they are written is that anything already on the USB stick gets deleted and that - given that most USB sticks nowadays are significantly larger in size - makes most of the stick completely unusable. Same goes for hd-media. If someone could come up with some solution to these problems, that would be great. One alternative option for the second issue could be to instead create a tarball with everything in it, including syslinux config and a script the user can run manually to make the stick bootable (with appropriate warnings if required commands, possibly checking for availability of alternative commands, are not available). I would expect such a script to become smarter with time as users provide feedback. di-netboot-assistant achieve very similar tasks for netbooting. Since the development version in git[1] allows specifying the target folder for extraction, the most difficult task might be to run syslinux to install the bootloader ;) Franklin [1] http://git.debian.org/?p=users/franklin-guest/di-netboot-assistant.git;a=summary -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505750: d-i: Add help text.
Frans Pop wrote: On Monday 17 November 2008, Frank Lin PIAT wrote: The attached patch enables syslinux help text menu features to display the following help text when the help menu entry is selected: Display help screens; type 'menu' at boot prompt to return to this menu This patch also fix another bug (previously, if someone pressed [tab] then edit a command line longer than one line, then the prompt was weird) Tested and looks great. I've committed it in my local git-svn repo together with my own patch. One error in the patch: the back option in the advanced menu does not need the help help text... Finishing and submitting a patch late in the evening (and in a rush) isn't a good idea ;) I've made a few very minor other changes, but nothing that really changes the patch. If others want to give it a try: http://cdimage.debian.org/cdimage/unofficial/fjp/debian-50-amd64-i386-BC-1.iso The color Franklin has chosen for the help text is yellow. Personally I'm fine with that. It is not something that i have carefully chosen... So any suggestion is welcome. Strangely enough VirtualBox now suddenly no longer tries to boot the amd64 image (as I mentioned in #505243), but correctly selects i386 when I hit enter from the help screen boot prompt. This may be related to the fact that I now run 2.6.28-rc5 on the host system instead of 2.6.27.4. Only ifcpu64.c32 is buggy under Vitualbox: default64 is known to work. (on the other hand, default64 works, until one loads vesamenu.c32) Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#505750: d-i: Add help text.
On Mon, 2008-11-17 at 22:16 +0100, Frans Pop wrote: On Monday 17 November 2008, Frank Lin PIAT wrote: Strangely enough VirtualBox now suddenly no longer tries to boot the amd64 image (as I mentioned in #505243), but correctly selects i386 when I hit enter from the help screen boot prompt. This may be related to the fact that I now run 2.6.28-rc5 on the host system instead of 2.6.27.4. Only ifcpu64.c32 is buggy under Vitualbox: default64 is known to work. Eh, hit enter from the help screen boot prompt _is_ ifcpu64.c32. I guess we don't use the same image! I was using : If others want to give it a try: http://cdimage.debian.org/cdimage/unofficial/fjp/debian-50-amd64-i386-BC-1.iso $ ls -al *.iso.1 -rw-rw-r-- 1 root fpiat 126085120 2008-11-17 13:39 debian-50-amd64-i386-BC-1.iso.1 $ grep -E (default|ifcpu) /mnt/isolinux/*.cfg /mnt/isolinux/amdtext.cfg:default64 amd64-install /mnt/isolinux/amdtext.cfg:menu default64 /mnt/isolinux/isolinux.cfg:default vesamenu.c32 /mnt/isolinux/text.cfg:default install /mnt/isolinux/text.cfg: menu default -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Non-regression checklist: virtual machine.
Here's a proposed addition to the non-regression checklist. qemu qemu-system_x86-64 kvm (32bits) virtualbox/linux (32bits) virtualbox/linux (64bits) virtualbox/windows (32bits) vmware virtualPC (32bits) hyperV (32bits) And maybe a hint like: Those test should be made using GTK 'netinst CD', and choose Desktop installation Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505750: d-i: Add help text.
The attached patch enables syslinux help text menu features to display
the following help text when the help menu entry is selected:
Display help screens; type 'menu' at boot prompt to return to
this menu
This patch also fix another bug (previously, if someone pressed [tab]
then edit a command line longer than one line, then the prompt was
weird)
Franklin
Index: menu.cfg
===
--- menu.cfg (revision 56664)
+++ menu.cfg (working copy)
@@ -12,6 +12,11 @@
label mainmenu
menu label ^Back..
menu exit
+ text help
+ Display help screens; type 'menu' at boot prompt to return to this menu.
+ endtext
+
+
include ${SYSDIR}stdmenu.cfg
include ${SYSDIR}adtext.cfg
include ${SYSDIR}adamdtext.cfg
@@ -21,3 +26,7 @@
label help
menu label ^Help
config ${SYSDIR}prompt.cfg
+ text help
+ Display help screens; type 'menu' at boot prompt to return to this menu.
+ endtext
+
Index: stdmenu.cfg
===
--- stdmenu.cfg (revision 56664)
+++ stdmenu.cfg (working copy)
@@ -4,8 +4,14 @@
menu color sel * # #76a1d0ff *
menu color hotsel 1;7;37;40 # #76a1d0ff *
menu color tabmsg * # # *
+menu color help 37;40 #ff00 # none
menu vshift 11
menu rows 10
-menu tabmsgrow 16
-menu timeoutrow 17
+menu tabmsgrow 18
+menu timeoutrow 16
menu tabmsg Press ENTER to boot or TAB to edit a menu entry
+
+menu helpmsgrow 15
+
+#The command line must be at least one line from the bottom.
+menu cmdlinerow 16
Bug#505773: debian-installer: Bootable netboot image for USB stick patch
On Sat, 2008-11-15 at 05:35 -0200, Otavio Salvador wrote: Christian Perrier [EMAIL PROTECTED] writes: Quoting Kenshi Muto ([EMAIL PROTECTED]): After this patch is applied, 'make build_netboot' will build boot.img.gz in dest/netboot/ directory for i386 and amd64 with both text and gtk installers. Because I didn't know well about other architectures, my patch didn't touch them. This boot.img.gz is more convenience than hd-media image for usual installation scene (install Debian into machine with wired network), because it isn't necessary to copy any ISOs, isn't necessary to setup TFTP server, and is pretty small. Currently I set 63MB for this image but we can change it to even 31MB. (I assumed user may copy firmwares and something into it). Nice. However, as this requires documentation changes, I think this should be post-Lenny. Kenshi, could you propose a text for it to the installer guide? Hello, I have a two cents question: what is the benefit over hd-media (which is 20MB to download, fits on 99% of the current usb keys, don't require to burn an ISO on a CD and don't requires a TFTP server)? Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [PROPOSAL] Identify tasks in the D-I team and assign them
Added a few topics marked with +. Also in many places, I suggest to s/Maintain/\0 and Coordinate/g On Wed, 2008-11-12 at 19:50 +, Miguel Figueiredo wrote: Reorganized in 3 main topics: [..] Added a few topics marked with +. - Mensagem Original- De: Christian Perrier [EMAIL PROTECTED] Para: debian-boot@lists.debian.org Assunto: [PROPOSAL] Identify tasks in the D-I team and assign them Data: Wed, 12 Nov 2008 18:36:17 +0100 [...] d-i release Management: === = Initial answer to installation reports = Interface with porters = Ack unblock requests from the RM team = Organize team meetings = Validate new committers = Maintain the wished features list and the release goals list Define releases (objectives for each release and planned week/month) -RCs, ... track progression towards next release (project page with status? blockers, builds, regressions, ...) Bits from the d-i team Bug reports tracking (wishlist as input from users, track evolution of BRs on the maintained packages and to debian-installer) Product Development: == = Porters powerpc alpha m68k mips/mipsel arm ia64 x86 amd64 = Packages maintenance: aboot-installer anna apt-setup arcboot-installer auto-install base-installer bterm-unifont cdebconf cdebconf-entropy cdebconf-terminal cdrom-checker cdrom-detect cdrom-retriever choose-mirror clock-setup colo-installer console-setup debian-installer-utils debootstrap efi-reader elilo-installer etch-support finish-install flash-kernel glantank grub-installer hw-detect installation-locale installation-report iso-scan kbd-chooser kernel-wedge kickseed libdebian-installer lilo-installer live-installer localechooser lowmem lvmcfg main-menu mdcfg media-retriever mklibs mountmedia netcfg net-retriever network-console nobootloader oldsys-preseed os-prober palo-installer partconf partitioner partman-auto partman-auto-crypto partman-auto-lvm partman-auto-raid partman-base partman-basicfilesystems partman-basicmethods partman-crypto partman-efi partman-ext2r0 partman-ext3 partman-jfs partman-lvm partman-md partman-multipath partman-newworld partman-palo partman-partitioning partman-prep partman-reiserfs partman-target partman-xfs pkgsel prep-installer preseed quik-installer rescue rootskel rootskel-gtk s390-dasd s390-netdevice s390-sysconfig-writer sarge-support sibyl-installer silo-installer srm-reader tzsetup udpkg usb-discover userdevfs user-setup vmelilo-installer yaboot-installer zipl-installer +di-netboot-assistant: franklin = Manual non regression tests = Automated D-I tests Usability and interface (text and graphical - including art) * Documentation: = Maintain the errata = Maintain DebianInstallerToday = Prepare Release announcements = Maintain web site + Maintain Debian Installer internals + Maintain wiki pages / review changes. = Maintain i18n = Maintain Installation Guide contents = Maintain Installation Guide translations = Track Installation Guide builds -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505243: Multiarch CD directly boots in the amd64 installer
On Wed, 2008-11-12 at 16:23 +0100, Frans Pop wrote: On Tuesday 11 November 2008, Frank Lin PIAT wrote: Here's a proper patch against SVN repository: I'll try to build a CD, and test it tomorrow on some computers at work. I'm afraid that IMO this patch is not a very good idea. First of all, as it is, it is incomplete and breaks other installation methods (in fact, I think the change in config/x86.cfg is wrong for CD). But that could be fixed. I agree that the cd builder scripts should have been modified so only multiarch would haved used this new trick. But: More importantly, I think it will break the addition of boot options by the user, for example booting with 'install noapic'. Or are they preserved somehow? That's confirmed: the arguments aren't passed. And last but not least I feel that it is a too elaborate patch to support multi-arch, which is after all an exception, and makes the far more common single-arch use case needlessly complicated. I agree that if such solution were used, the trick should only be present in multiarch CD (But I wasn't able to provide such improvement). I still feel that the basic problem is not in D-I, but in syslinux and the best option for Lenny may still be to just comment out 'default64 amd64-install' and accept the resulting (minor) erratum. Especially since we are so close from the release, I completely agree. I'll try to do some testing myself today on this issue. Let me know if I can help. Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505494: syslinux: ifcpu64.c32 doesn't work under virtualbox (always run 64bit thing)
Package: syslinux
Version: 2:3.71+dfsg-5
Severity: normal
The module ifcpu64.c32 doesn't work as expected under virtualbox.
If we build a simple test image with the script below.
* virtualbox will always try to run the entry a64, where as qemu and
qemu-system-x86_64 works as expected.
* default/default64 does detects cpu correctly.
* I have tried upstream's 3.72 it has the same bug.
Franklin
A script to generate a test.iso
D=$(mktemp -d) ;
echo -e 'say type go or press Enter.\ndefault run-default32\ndefault64
run-default64\nprompt 1\ntimeout 0\nlabel go\n\tkernel ifcpu64.c32\n\tappend
a64 -- i32' $D/isolinux.cfg
cp /usr/lib/syslinux/{isolinux.bin,ifcpu64.c32} $D/
mkisofs -R -J -joliet-long -cache-inodes -b isolinux.bin -c boot.cat
-no-emul-boot -boot-load-size 4 -boot-info-table -o /tmp/test.iso $D
[ $D ] rm -Rf $D
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (200, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-openvz-686 (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
Versions of packages syslinux depends on:
ii dosfstools 2.11-6utilities for making and checking
ii libc6 2.7-15GNU C Library: Shared libraries
ii mtools 3.9.11-1 Tools for manipulating MSDOS files
ii syslinux-common2:3.71+dfsg-5 Kernel loader which uses a FAT, ex
syslinux recommends no packages.
syslinux suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505496: syslinux: default64 doesn't work after after reloading config file.
Package: syslinux
Version: 2:3.71+dfsg-5
Severity: normal
In the attached example (built with the script below), the idea is to
automatically
load vesamenu from isolinux.cfg. Then it is possible to quit the vesa menu (to
use
the F1 and F2 help screen. If one press Enter, default or default64 should be
run.
The way we quit vesamenu is to invoke config menu.cfg.
The problem it's that before vesamenu.c32, default64 is obeyed... but after we
quit
vesamenu.c32 the entry default is obeyed when a user press enter (even for
amd64).
Franklin
Note: As a work around, in the attached menu.cfg, it is possible to use
default run-autodetect which uses ifcpu64.c32 for cpu detection.
--
D=/tmp/TesT
mkdir $D
cp
/usr/lib/syslinux/{dmitest.c32,ifcpu64.c32,solinux.bin,pcitest.c32,vesamenu.c32}
$D/
cp /tmp/{isolinux.cfg,menu.cfg} $D/
mkisofs -R -J -joliet-long -cache-inodes -b isolinux.bin -c boot.cat
-no-emul-boot -boot-load-size 4 -boot-info-table -o /tmp/test.iso $D
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (200, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-openvz-686 (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
Versions of packages syslinux depends on:
ii dosfstools 2.11-6utilities for making and checking
ii libc6 2.7-15GNU C Library: Shared libraries
ii mtools 3.9.11-1 Tools for manipulating MSDOS files
ii syslinux-common2:3.71+dfsg-5 Kernel loader which uses a FAT, ex
syslinux recommends no packages.
syslinux suggests no packages.
-- no debconf information
prompt 1
say press F1 or F2 for help screen
F1 isolinux.cfg
F2 menu.cfg
# Note that default 64 here doesn't work
default64 run-a64
default run-i32
#default run-autodetect
##It is possible to replace the default run-i32 above with
##default run-autodetect that works (well... except on virtual box)
label quit
MENU LABEL Quit
config menu.cfg
label run-a64
menu default64
kernel dmitest.c32
label run-i32
menu default
kernel pcitest.c32
label run-autodetect
MENU HIDE
kernel ifcpu64.c32
append run-a64 -- run-i32
include menu.cfg
prompt 0
timeout 0
default vesamenu.c32
#Note that default64 does work here.
default64 vesamenu.c32
Bug#505243: [TEST RC1] Resize NTFS ; windows detection ; Nec VL360
On Tue, 2008-11-11 at 07:51 +0100, Christian Perrier wrote: Quoting Frank Lin PIAT ([EMAIL PROTECTED]): I have a concern regarding the multiarch CD : syslinux/isolinux boots the amd-64 installer directly (i.e it doesn't show the menu). I suspect that it isn't the desired behavior. I've had a quick look and I suppose it's because isolinux/isolinux.cfg declares timeout 0, then amd64text.cfg declares default64 amd64-install. I assume it can be solved either by: - declaring timeout 999 in amd64text.cfg or - removing default64 amd64-install. How thinks works: isolinux.bin is loaded. it loads isolinux.cfg and all the included files. isolinux sees prompt 0, so it jumps to the action described in default (vesamenu.cfg) or default64 (amd-install). * The first action is to change default64 to vesamenu.c32 (or just remove it completely). See amdtext.cfg.diff Now the problem is that there's a bug in isolinux: It is possible to specify two different default action for boot prompt (Do action vesamenu.c32 the first time, then do action install). This feature isn't possible with default64 (the second action is always the same action as the second default, //or something like that//). We have at least three options : * Keep that new behaviour (We you press enter in the help screen, you launch i386 installation). * Apply the patch text.cfg.diff so when a user press enter after reading the help pages, he/she returns to the GUI menu. this can be a problem for people using serial console or some floppies according to fjp. * Apply the patch text-ifcpu64.diff, which uses ifcpu64.c32[1] to automatically choose the good cpu profile. (It event seems to automaticaly fallback to 32bit, it the 64bit label isn't fount) Note: the patch are against an existing Cd, not again the source files ;( [I start working on the source files] Franklin [1] http://syslinux.zytor.com/wiki/index.php/Ifcpu64.c32 --- scratch pad --- To rebuild an ISO iamge, based on extracted files, I have used: mkisofs -J -joliet-long -cache-inodes -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -o /tmp/test.iso --- isolinux/text-orig.cfg 2008-11-11 19:10:16.0 +0100 +++ isolinux/text.cfg 2008-11-11 19:10:07.0 +0100 @@ -1,4 +1,9 @@ -default install +default gui + +label gui + kernel vesamenu.c32 + + label install menu label ^Install menu default --- isolinux/text-orig.cfg 2008-11-11 19:10:16.0 +0100 +++ isolinux/text.cfg 2008-11-11 19:34:03.0 +0100 @@ -1,6 +1,14 @@ default install + +label menu + kernel vesamenu.c32 + label install + kernel ifcpu64.c32 + append amd64-install -- i386-install + +label i386-install menu label ^Install menu default kernel /install.386/vmlinuz - append vga=normal initrd=/install.386/initrd.gz -- quiet + append vga=normal initrd=/install.386/initrd.gz -- quiet --- isolinux/amdtext-orig.cfg 2008-11-11 19:41:39.0 +0100 +++ isolinux/amdtext.cfg 2008-11-11 19:41:24.0 +0100 @@ -1,4 +1,5 @@ -default64 amd64-install +default64 vesamenu.c32 + label amd64-install menu label ^64 bit install menu default64
Bug#505243: [TEST RC1] Resize NTFS ; windows detection ; Nec VL360
tag 505243 +patch
thanks
On Tue, 2008-11-11 at 19:45 +0100, Frank Lin PIAT wrote:
On Tue, 2008-11-11 at 07:51 +0100, Christian Perrier wrote:
Quoting Frank Lin PIAT ([EMAIL PROTECTED]):
I have a concern regarding the multiarch CD :
syslinux/isolinux boots the amd-64 installer directly (i.e it doesn't
show the menu).
I suspect that it isn't the desired behavior.
* Apply the patch text-ifcpu64.diff, which uses ifcpu64.c32[1] to
automatically choose the good cpu profile.
(It event seems to automaticaly fallback to 32bit, it the 64bit label
isn't fount)
Note: the patch are against an existing Cd, not again the source
files ;( [I start working on the source files]
Here's a proper patch against SVN repository:
I'll try to build a CD, and test it tomorrow on some computers at work.
Franklin
Index: build/boot/x86/text.cfg
===
--- build/boot/x86/text.cfg (revision 56632)
+++ build/boot/x86/text.cfg (working copy)
@@ -1,5 +1,11 @@
default install
+
label install
+ # Detect the cpu, jump to the appropriate label
+ kernel ifcpu64.c32
+ append amd64-install -- i386-install
+
+label i386-install
menu label ^Install
menu default
kernel ${KERNEL}
Index: build/boot/x86/gtk.cfg
===
--- build/boot/x86/gtk.cfg (revision 56632)
+++ build/boot/x86/gtk.cfg (working copy)
@@ -1,4 +1,9 @@
label installgui
+ # Detect the cpu, jump to the appropriate label
+ kernel ifcpu64.c32
+ append amd64-installgui -- i386-installgui
+
+label i386-installgui
menu label ^Graphical install
kernel ${KERNEL}
append ${VIDEO_MODE_GTK} initrd=${INITRD_GTK} -- quiet ${CONSOLE}
Index: build/boot/x86/adtext.cfg
===
--- build/boot/x86/adtext.cfg (revision 56632)
+++ build/boot/x86/adtext.cfg (working copy)
@@ -1,12 +1,26 @@
label expert
+ # Detect the cpu, jump to the appropriate label
+ kernel ifcpu64.c32
+ append amd64-expert -- i386-expert
+label i386-expert
menu label ^Expert install
kernel ${KERNEL}
append priority=low ${VIDEO_MODE} initrd=${INITRD} -- ${CONSOLE}
+
label rescue
+ # Detect the cpu, jump to the appropriate label
+ kernel ifcpu64.c32
+ append amd64-rescue -- i386-rescue
+label i386-rescue
menu label ^Rescue mode
kernel ${KERNEL}
append ${VIDEO_MODE} initrd=${INITRD} rescue/enable=true -- quiet ${CONSOLE}
+
label auto
+ # Detect the cpu, jump to the appropriate label
+ kernel ifcpu64.c32
+ append amd64-auto -- i386-auto
+label i386-auto
menu label ^Automated install
kernel ${KERNEL}
append auto=true priority=critical ${VIDEO_MODE} initrd=${INITRD} -- quiet ${CONSOLE}
Index: build/boot/x86/adgtk.cfg
===
--- build/boot/x86/adgtk.cfg (revision 56632)
+++ build/boot/x86/adgtk.cfg (working copy)
@@ -2,14 +2,27 @@
menu width 58
label expertgui
+ # Detect the cpu, jump to the appropriate label
+ kernel ifcpu64.c32
+ append amd64-expertgui -- i386-expertgui
+label i386-expertgui
menu label Graphical expert install
kernel ${KERNEL}
append priority=low ${VIDEO_MODE_GTK} initrd=${INITRD_GTK} -- ${CONSOLE}
+
label rescuegui
+ # Detect the cpu, jump to the appropriate label
+ kernel ifcpu64.c32
+ append amd64-rescuegui -- i386-rescuegui
+label i386-rescuegui
menu label Graphical rescue mode
kernel ${KERNEL}
append ${VIDEO_MODE_GTK} initrd=${INITRD_GTK} rescue/enable=true -- quiet ${CONSOLE}
label autogui
+ # Detect the cpu, jump to the appropriate label
+ kernel ifcpu64.c32
+ append amd64-autogui -- i386-autogui
+label i386-autogui
menu label Graphical automated install
kernel ${KERNEL}
append auto=true priority=critical ${VIDEO_MODE_GTK} initrd=${INITRD_GTK} -- quiet ${CONSOLE}
Index: build/boot/x86/amdtext.cfg
===
--- build/boot/x86/amdtext.cfg (revision 56632)
+++ build/boot/x86/amdtext.cfg (working copy)
@@ -1,4 +1,3 @@
-default64 amd64-install
label amd64-install
menu label ^64 bit install
menu default64
Index: build/config/x86.cfg
===
--- build/config/x86.cfg (revision 56632)
+++ build/config/x86.cfg (working copy)
@@ -90,6 +90,7 @@
if [ ! $(NO_VESAMENU) ]; then \
mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/vesamenu.c32 ::vesamenu.c32; \
+ mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/ifcpu64.c32 ::ifcpu64.c32; \
if [ -e $(TEMP_BOOT_SCREENS)/splash.png ]; then \
mcopy -i$(TEMP_BOOT) $(TEMP_BOOT_SCREENS)/splash.png ::splash.png; \
fi; \
Installation manual: searching firmware
Hello, Here's a suggested improvement for the installation manual. (even though I know it's too late for Lenny). Franklin Index: build/entities/urls.ent === --- build/entities/urls.ent (revision 56613) +++ build/entities/urls.ent (working copy) @@ -77,9 +77,10 @@ !-- location of tarballs with firmware packages -- !ENTITY url-firmware-tarballs http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/; -!-- rough list of firmware packages -- -!ENTITY url-firmware-packages http://packages.debian.org/search?keywords=firmware; +!-- search the contents of packages -- +!ENTITY url-search-contents-of-packages http://www-debian-org;/distrib/packages#search_contents; + !-- WNPP -- !ENTITY url-wnpp http://www-debian-org;/devel/wnpp/; Index: en/using-d-i/loading-firmware.xml === --- en/using-d-i/loading-firmware.xml (revision 56613) +++ en/using-d-i/loading-firmware.xml (working copy) @@ -78,13 +78,12 @@ If the firmware you need is not included in the tarball, you can also download specific firmware packages from the (non-free section of the) -archive. The following overview should list most available firmware -packages but is not guaranteed to be complete and may also contain -non-firmware packages: +archive. You can search the firmware's filename in the contents of packages +using: itemizedlist listitempara -ulink url=url-firmware-packages;/ +ulink url=url-search-contents-of-packages;/ /para/listitem /itemizedlist
Bug#505243: [TEST RC1] Resize NTFS ; windows detection ; Nec VL360
Package: installation-reports -- Package-specific info: Boot method: CD Image version: multiarch lenny-pre-rc1 (2008-11-xx) Date: 2008-11-10 Machine: NEC Powermate VL360 Processor: AMD64 Memory: 1GB Partitions: see below Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[ ] Configure network: [ ] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [ ] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: The following regression test are passed : * resize NTFS partition (for Windows XP) * Detect windows (in GRUB, if that's what the test means). I have a concern regarding the multiarch CD : syslinux/isolinux boots the amd-64 installer directly (i.e it doesn't show the menu). I suspect that it isn't the desired behavior. I've had a quick look and I suppose it's because isolinux/isolinux.cfg declares timeout 0, then amd64text.cfg declares default64 amd64-install. I assume it can be solved either by: - declaring timeout 999 in amd64text.cfg or - removing default64 amd64-install. Franklin df -Tl FilesystemType 1K-blocks Used Available Use% Mounted on /dev/sda3 ext3 9155584437260 8253244 6% / tmpfstmpfs 481916 0481916 0% /lib/init/rw udev tmpfs 1024092 10148 1% /dev tmpfstmpfs 481916 0481916 0% /dev/shm /dev/sdb vfat 127476 68548 58928 54% /mnt fdisk -l Disk /dev/sda: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0f300f2f Device Boot Start End Blocks Id System /dev/sda1 1 340627358663+ 7 HPFS/NTFS /dev/sda23407 857141487862+ f W95 Ext'd (LBA) /dev/sda3 *8572 9729 9301635 83 Linux /dev/sda53407 8513410219467 HPFS/NTFS /dev/sda68514 8571 465853+ 82 Linux swap / Solaris /boot/grub/menu.lst [[..]] # This entry automatically added by the Debian installer for a non-linux OS # on /dev/sda1 title Microsoft Windows XP Professionnel root (hd0,0) savedefault makeactive chainloader +1 umame -a: Linux p310401 2.6.26-1-amd64 #1 SMP Thu Oct 9 14:16:53 UTC 2008 x86_64 GNU/Linux /proc/bus/pci/devices: 10de02f00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 /proc/bus/pci/devices: 0001 10de02fa0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 /proc/bus/pci/devices: 0002 10de02fe0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 /proc/bus/pci/devices: 0003 10de02f80 0 0 0 0 0 0 0 0 0 0 0 0 0 0 /proc/bus/pci/devices: 0004 10de02f90 0 0 0 0 0 0 0 0 0 0 0 0 0 0 /proc/bus/pci/devices: 0005 10de02ff0 0 0 0 0 0 0 0 0 0 0 0 0
Bug#505244: installation-reports: [TEST RC1] raid 1 root and boot (lilo) ; full CD desktop install
Package: installation-reports Severity: normal -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/cdimage/.lenny_rc1/i386/iso-cd/debian-testing-i386-CD-1.iso Date: 2009-11-10 Machine: Qemu/KVM Partitions: df -Tl FilesystemType 1K-blocks Used Available Use% Mounted on /dev/md0 ext3 3020048 1585832 1280804 56% / tmpfstmpfs 387852 0387852 0% /lib/init/rw udev tmpfs 1024084 10156 1% /dev tmpfstmpfs 387852 0387852 0% /dev/shm mdadm --detail /dev/md0 /dev/md0: Version : 00.90 Creation Time : Tue Nov 11 00:19:13 2008 Raid Level : raid1 Array Size : 3068288 (2.93 GiB 3.14 GB) Used Dev Size : 3068288 (2.93 GiB 3.14 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Tue Nov 11 01:21:23 2008 State : active Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : e2988e23:a0fd968a:33723341:e670d402 Events : 0.7 Number Major Minor RaidDevice State 0 310 active sync /dev/hda1 1 3 651 active sync /dev/hdb1 fdisk -l Disk /dev/hda: 3145 MB, 3145728000 bytes 255 heads, 63 sectors/track, 382 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0002ef9e Device Boot Start End Blocks Id System /dev/hda1 1 382 3068383+ fd Linux raid autodetect Disk /dev/hdb: 3145 MB, 3145728000 bytes 255 heads, 63 sectors/track, 382 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x000687a5 Device Boot Start End Blocks Id System /dev/hdb1 1 382 3068383+ fd Linux raid autodetect grep oot=/dev /etc/lilo.conf boot=/dev/md0 root=/dev/md0 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [o] Detect network card:[ ] Configure network: [ ] Detect CD: [o] Load installer modules: [o] Detect hard drives: [o] Partition hard drives: [o] Install base system:[o] Clock/timezone setup: [o] User/password setup:[o] Install tasks: [?] Install boot loader:[o] Overall install:[o] Comments/Problems: This system was installed under Qemu/KVM, with root and boot mounted as RAID-1, using lilo as bootloader. The task Desktop Environnement was installed from the CD-1 only (no network connection). Therefore, the following regression test can be considered passed: * raid 1 root and boot (lilo) * full CD desktop install (Note that I actually to manually check-in that task... I don't know if it's because of qemu, the low disk space, or if it's a bug). Franklin == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=5.0 (lenny) - installer build 20081029 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux gnome-raid 2.6.26-1-486 #1 Thu Oct 9 14:22:52 UTC 2008 i686 unknown df: Filesystem 1k-blocks Used Available Use% Mounted on df: tmpfs 38808840388048 0% /dev df: /dev/md0 3020048 1580780 1285856 55% /target df: /dev/md0 3020048 1580780 1285856 55% /dev/.static/dev df: tmpfs 38808840388048 0% /target/dev -- System Information: Debian Release: lenny/sid Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505093: Partitioning, /boot, swap and dm-crypt.
package: partman-crypto-dm I wanted to install a system with dm-crypt. So, I have created some partitions and a non-encrypted partition for /boot. By mistake,I've mixed-up swap and /boot: I defined /boot on an encrypted partition. DI told me that was wrong, so I reconfigured the encrypted partition to be swap and define /boot on the non-encrypted partition. The problem is that DI was still complaining that /boot shouldn't be on an encrypted partition. This is because DI remembers that I said that the encrypted partition was mounted on /boot... even though it is now used as swap) I had to go back to my swap on dm-crypt partition, change the type to ext3, change the mount point to not used, re-change the type to swap, and voilà. Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505106: installation-reports: [TEST RC1] multiarch CD, tested on AMD64.
Package: installation-reports Severity: normal -- Package-specific info: Boot method: CD Image version: cdimage/.lenny_rc1 (2008-11-05) Date: 2008-11-09 Machine: Thinkpad T61 Partitions: df -Tl: FilesystemType 1K-blocks Used Available Use% Mounted on /dev/sda7 ext3 2403420427524 1853804 19% / tmpfstmpfs 501752 0501752 0% /lib/init/rw udev tmpfs 10240 116 10124 2% /dev tmpfstmpfs 501752 0501752 0% /dev/shm /dev/sda8 ext3 190323 22264158233 13% /boot losetup /dev/loop0: /dev/loop0: [000d]:2530 (/dev/sda7) encryption=AES256 multi-key-v3 losetup /dev/loop0: /dev/loop1: [000d]:2516 (/dev/sda9) offset=4096 encryption=AES256 multi-key-v3 cat /proc/swaps FilenameType SizeUsedPriority /dev/loop1 partition1315396 0 -1 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [ ] User/password setup:[O] Install tasks: [?] Install boot loader:[O] Overall install:[O] Comments/Problems: * This system was installed using multiarch CD. amd64 was properly selected automatically. * This system was installed with crypto root (loop-AES) * Tasksel ! The tested CD contained an old tasksel (2.76 instead of 2.77) -- == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=5.0 (lenny) - installer build 20081029 X_INSTALLATION_MEDIUM=cdrom -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-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/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505099: installation-reports: [RC1 TEST] Thinkpad T61 ; netboot-install ; crypto-root (dm-crypt)
Package: installation-reports
Severity: normal
-- Package-specific info:
Boot method: netboot
Image version: testing gtk netboot image ; 20091029
Date: 2009-11-09
Machine: Lenovo Thinkpad T61
Partitions: df -Tl will do; the raw partition table is preferred
FilesystemType 1K-blocks Used Available Use% Mounted on
/dev/mapper/sda7_crypt
ext3 2402468 2052564227864 91% /
tmpfstmpfs 505184 0505184 0% /lib/init/rw
udev tmpfs 10240 124 10116 2% /dev
tmpfstmpfs 505184 0505184 0% /dev/shm
/dev/sda8 ext3 190323 20817159680 12% /boot
fdisk -l:
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x2d1e9a64
Device Boot Start End Blocks Id System
/dev/sda1 1 801 6429696 27 Unknown
Partition 1 does not end on cylinder boundary.
/dev/sda2 801 13955 1056563207 HPFS/NTFS
Partition 2 does not end on cylinder boundary.
/dev/sda3 * 13955 1586715367 HPFS/NTFS
Partition 3 does not end on cylinder boundary.
/dev/sda4 15867 1945728839816+ f W95 Ext'd (LBA)
Partition 4 does not end on cylinder boundary.
/dev/sda5 15867 1714210247 HPFS/NTFS
/dev/sda6 17142 1896514643688+ 83 Linux
/dev/sda7 18965 19269 2441848+ 83 Linux
/dev/sda8 19269 19294 196528+ 83 Linux
/dev/sda9 19294 19457 1315408+ 83 Linux
Disk /dev/dm-0: 2499 MB, 2499400192 bytes
255 heads, 63 sectors/track, 303 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x
Disk /dev/dm-1: 1345 MB, 1345925632 bytes
255 heads, 63 sectors/track, 163 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x
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: [ ]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Install base system:[O]
Clock/timezone setup: [O]
User/password setup:[O]
Install tasks: [O]
Install boot loader:[O]
Overall install:[O]
Comments/Problems:
- Netboot works fine.
But the netboot images seems older that CD 29-Oct instead of 04-Nov
- Crypto-root (dm-crypt) works :
dmsetup info:
Name: sda9_crypt
State: ACTIVE
Read Ahead:256
Tables present:LIVE
Open count:2
Event number: 0
Major, minor: 254, 1
Number of targets: 1
Name: sda7_crypt
State: ACTIVE
Read Ahead:256
Tables present:LIVE
Open count:1
Event number: 0
Major, minor: 254, 0
Number of targets: 1
- Thinkpad T61 :
I have noticed this error message in syslog :
kernel: [ 736.811533] irq 19: nobody cared (try booting with the irqpoll
option)
kernel: [ 736.811533] Pid: 0, comm: swapper Not tainted 2.6.26-1-686 #1
kernel: [ 736.811533] [c0152677] __report_bad_irq+0x24/0x69
kernel: [ 736.811533] [c015267e] __report_bad_irq+0x2b/0x69
kernel: [ 736.811533] [c0152890] note_interrupt+0x1d4/0x208
kernel: [ 736.811533] [c0151e3e] handle_IRQ_event+0x23/0x51
kernel: [ 736.811533] [c0152f51] handle_fasteoi_irq+0x85/0xa4
kernel: [ 736.811533] [c0105f3a] do_IRQ+0x4d/0x63
kernel: [ 736.811533] [c01042a7] common_interrupt+0x23/0x28
kernel: [ 736.811533] [c01300d8] module_param_sysfs_remove+0xf/0x23
kernel: [ 736.811533] [f8850097] acpi_idle_enter_bm+0x2a9/0x317
[processor]
kernel: [ 736.811533] [c02495a9] cpuidle_idle_call+0x5b/0x86
kernel: [ 736.811533] [c024954e] cpuidle_idle_call+0x0/0x86
kernel: [ 736.811533] [c01025ce] cpu_idle+0xab/0xcb
kernel: [ 736.811533] ===
kernel: [ 736.811533] handlers:
kernel: [ 736.811533] [f88f007f] (usb_hcd_irq+0x0/0x73 [usbcore])
kernel: [ 736.811533] Disabling IRQ #19
cat /proc/interrupts | grep 19:
19: 46299 53702 IO-APIC-fasteoi ehci_hcd:usb7
grep /sys/bus/usb/drivers/usb/usb7/{id,manu}*
/sys/bus/usb/drivers/usb/usb7/idProduct:0002
/sys/bus/usb/drivers/usb/usb7/idVendor:1d6b
/sys/bus/usb/drivers/usb/usb7/manufacturer:Linux 2.6.26-1-686 ehci_hcd
USB seems to work though... I'll try to test USB further later, and
see how it goes.
Franklin
--
==
Installer lsb-release:
==
DISTRIB_ID=Debian
Bug#505106: installation-reports: [TEST RC1] multiarch CD, tested on AMD64 + i386
On Sun, 2008-11-09 at 15:40 +0100, Frank Lin PIAT wrote: Boot method: CD Image version: cdimage/.lenny_rc1 (2008-11-05) As mentioned in the bug tile, the CD was the i386/amd64/ppc multiarch. * This system was installed using multiarch CD. amd64 was properly selected automatically. Actually, the menu didn't showed up (i.e the system automatically boot to amd64 installer). I could press shift to have syslinux's prompt. Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505106: installation-reports: [TEST RC1] multiarch CD, tested on i386
Package: installation-reports
Followup-For: Bug #505106
-- Package-specific info:
Boot method: CD (multiarch i386,amd64,ppc)
Image version: cdimage/.lenny_rc1 ... multiarch 2008-11-05
Date: 2008-11-09
Machine: Thinkpad A22e
Partitions: {single partition}
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [O]
Detect network card:[ ]
Configure network: [ ]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Install base system:[O]
Clock/timezone setup: [ ]
User/password setup:[O]
Install tasks: [O]
Install boot loader:[O]
Overall install:[O]
Comments/Problems:
* The multiarch-CD presented the syslinux menu.
The amd64 entry were present in the list, eventhough this
system don't support x86_64 instructions (It doesn't
really hurt either to have them).
* The installation was tested without network.
The Standard installation task was properly
self-contained on Cd-Rom.
* The laptop itself seems to to be well supported
(except the sound card, which doesnt' seems to be supported
by kernel).
Franklin
--
==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=5.0 (lenny) - installer build 20081029
X_INSTALLATION_MEDIUM=cdrom
==
Installer hardware-summary:
==
umame -a: Linux i386 2.6.26-1-486 #1 Thu Oct 9 14:22:52 UTC 2008 i686 unknown
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX -
82443BX/ZX/DX Host bridge [8086:7190] (rev 03)
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 440BX/ZX/DX -
82443BX/ZX/DX AGP bridge [8086:7191] (rev 03)
lspci -knn: 00:02.0 CardBus bridge [0607]: Texas Instruments PCI1450
[104c:ac1b] (rev 03)
lspci -knn: Kernel driver in use: yenta_cardbus
lspci -knn: Kernel modules: yenta_socket
lspci -knn: 00:02.1 CardBus bridge [0607]: Texas Instruments PCI1450
[104c:ac1b] (rev 03)
lspci -knn: Kernel driver in use: yenta_cardbus
lspci -knn: Kernel modules: yenta_socket
lspci -knn: 00:03.0 Ethernet controller [0200]: 3Com Corporation 3c556B CardBus
[Tornado] [10b7:6056] (rev 20)
lspci -knn: Kernel driver in use: 3c59x
lspci -knn: Kernel modules: 3c59x
lspci -knn: 00:03.1 Communication controller [0780]: 3Com Corporation Mini PCI
56k Winmodem [10b7:1007] (rev 20)
lspci -knn: 00:05.0 Multimedia audio controller [0401]: Cirrus Logic CS
4614/22/24/30 [CrystalClear SoundFusion Audio Accelerator] [1013:6003] (rev 01)
lspci -knn: 00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ISA
[8086:7110] (rev 02)
lspci -knn: 00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4
IDE [8086:7111] (rev 01)
lspci -knn: Kernel driver in use: PIIX_IDE
lspci -knn: Kernel modules: piix
lspci -knn: 00:07.2 USB Controller [0c03]: Intel Corporation 82371AB/EB/MB
PIIX4 USB [8086:7112] (rev 01)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI
[8086:7113] (rev 03)
lspci -knn: 01:00.0 VGA compatible controller [0300]: S3 Inc. 86C270-294
Savage/IX-MV [5333:8c12] (rev 13)
lsmod: Module Size Used by
lsmod: ufs63620 0
lsmod: qnx47684 0
lsmod: ntfs 180416 0
lsmod: dm_mod 45384 0
lsmod: md_mod 65940 0
lsmod: xfs 446836 0
lsmod: reiserfs 187008 0
lsmod: jfs 148060 0
lsmod: ext3 103432 1
lsmod: jbd35092 1 ext3
lsmod: vfat8832 0
lsmod: fat39964 1 vfat
lsmod: ext2 52616 0
lsmod: mbcache 6656 2 ext3,ext2
lsmod: 3c59x 36136 0
lsmod: mii 4864 1 3c59x
lsmod: nls_utf81664 2
lsmod: isofs 27684 0
lsmod: nls_base6528 6 ntfs,jfs,vfat,fat,nls_utf8,isofs
lsmod: zlib_inflate 13952 1 isofs
lsmod: ide_generic 2432 0 [permanent]
lsmod: usb_storage75200 0
lsmod: scsi_mod 129420 1 usb_storage
lsmod: vga16fb11276 2
lsmod: vgastate7552 1 vga16fb
lsmod: fan 4100 0
lsmod: ide_cd_mod 27524 0
lsmod: cdrom 30112 1 ide_cd_mod
lsmod: ide_disk 10368 3
lsmod: pcmcia 29484 0
lsmod: firmware_class 6656 1 pcmcia
lsmod: parport_pc 22308 0
lsmod: parport30152 1 parport_pc
lsmod: uhci_hcd 18320 0
lsmod: piix
[TEST RC1] Xfce CD ; lvm boot
Boot method: CD Image version: cdimage/.lenny_rc1.../debian-testing-i386-CD-1.iso BUILT 2008-10-29 Date: 2008-11-09 Machine: Qemu Partitions: df -Tl FilesystemType 1K-blocks Used Available Use% Mounted on /dev/mapper/xfce-root ext3 3563904 1488112 1894752 44% / tmpfstmpfs 63080 0 63080 0% /lib/init/rw udev tmpfs 1024080 10160 1% /dev tmpfstmpfs 63080 0 63080 0% /dev/shm /dev/hda1 ext2 25 15357205530 7% /boot Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[ ] Configure network: [ ] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [ ] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: The installation went fine. The following regression are considered passed: - XFCE CD - lvm boot -- == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=5.0 (lenny) - installer build 20081029 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux xfce 2.6.26-1-486 #1 Thu Oct 9 14:22:52 UTC 2008 i686 unknown -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Call for testing of RC1 images
On Wed, 2008-11-05 at 13:54 -0200, Otavio Salvador wrote: The Debian-CD Team has prepared a testing set of images[1] of RC1 for us to give it a try. If all goes well we should release Debian Installer RC1 in Monday. 1. http://cdimage.debian.org/cdimage/.lenny_rc1/ I have tested root on SoftRaid+LVM, under kvm i386. So the following regression tests[1] might be considered passed : * lvm over raid * raid 1 root and boot (lilo) * netinst CD install[I had Internet connection too] * rescue mode [I love the RAID+LVM detection !] * lvm install from netinst CD [I had Internet connection too] Franklin [1] http://svn.debian.org/wsvn/d-i/trunk/installer/doc/devel/release-checklist?op=filerev=0sc=0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Call for testing of RC1 images
On Sat, 2008-11-08 at 17:22 +0100, Frank Lin PIAT wrote: On Wed, 2008-11-05 at 13:54 -0200, Otavio Salvador wrote: The Debian-CD Team has prepared a testing set of images[1] of RC1 for us to give it a try. If all goes well we should release Debian Installer RC1 in Monday. 1. http://cdimage.debian.org/cdimage/.lenny_rc1/ * I have tested qemu/i386 with 32mb ram, from netinst cdrom + mirror. The installation went fine (in legacy text mode, but I assume it is normal). So the following regression tests[1] might be considered passed : - 32 mb ram install - netinst CD install * I have also tested qemu/i386 with 48mb ram, from netinst cdrom + mirror. The installation went fine (in newt mode). So the following regression tests[1] might be considered passed : - 48 mb ram install - netinst CD install Regarding installgui, qemu refused to boot it with less than 52Mb of RAM. The installation guide mention 48[1] (the screen is black). However another VM (VirtualPC) was happy with 48Mb. [1] http://d-i.alioth.debian.org/manual/en.i386/apds06.html Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#470601: Debian Lenny-pre-RC1 on Virtual PC 2007 / unrecoverable processor error
Hello, Here's an update for my previous report. Newer kernel (maybe 2.6.24, and 2.6.26) reveals a bug in VirtualPC, where it fails to boot with the error message An unrecoverable processor error has been encountered. The virtual machine will reset now. This bug only occurs on the installed system (i.e not when booting debian-installer). An easy work-around is to add noreplace-paravirt to the boot command line. A patch was applied upstream (for 2.6.27) to solve this problem. see http://marc.info/?l=linux-kernelm=122090760532385w=2 http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=28f7e66fc1da53997a545684b21b91fb3ca3f321 Some other bugs exists, but they have been reported to DD maintainer or upstream, then documented on the wiki page: http://wiki.debian.org/MicrosoftVirtualPc2007/lenny Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#485064: clock-setup works with kernel 2.6.26
Package: clock-setup Followup-For: Bug #485064 I have just tested this hwclock bug on a Thinkpad T61, using the DI build : 5.0 (lenny) - installer build 20081023-09:05 which uses clock-setup 0.97, kernel 2.6.26, and util-linux 2.13.1.1-1. The problem didn't show up. Franklin -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (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/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495726: installation-reports: Updating status of Lenovo Thinkpad T61 report
Package: installation-reports Followup-For: Bug #495726 -- Package-specific info: Boot method: network Image version: joey's daily image. Date: 2008-08-25 Machine: Lenovo Thinkpad T61 (intel graphic card and Wifi) Partitions: /manual/ 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: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [ ] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[ ] Overall install:[O] Comments/Problems: 1) HDAPS don't work! Tested, it works (install hdaps + tp-smapi-modules + hdaps-utils). 2) Kernel source is incomplete! I guess this issue is now solved, since the krenel is now in testing. also the file exists : /usr/src/linux-headers-2.6.26-1-686/scripts/gcc-x86_64-has-stack-protector.sh 3) Nv driver have a very poor performance! 4) Is necessary change XkbModel in xorg.conf 5) Tapping/Scrolling over touchpad don't work! 3,4,5 Not tested myself. 6) HD-AUDIO-INTEL don't work very well in my laptop. Works out of this box with Gnome. 7) I install openoffice.org (2.4.1), openoffice.og-kde and openoffice.org-gtk. Out of DI scope, I guess. 8) After installation, I need go to kcontrol and force DPI fonts to 96. Not tested myself. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to [EMAIL PROTECTED] == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=5.0 (lenny) - installer build 20081023-09:05 X_INSTALLATION_MEDIUM=netboot-gtk == Installer hardware-summary: == umame -a: Linux t61 2.6.26-1-486 #1 Thu Oct 9 14:22:52 UTC 2008 i686 unknown lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c) lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c) lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a03] (rev 0c) lspci -knn: 00:03.0 Communication controller [0780]: Intel Corporation Mobile PM965/GM965 MEI Controller [8086:2a04] (rev 0c) lspci -knn: 00:03.2 IDE interface [0101]: Intel Corporation Mobile PM965/GM965 PT IDER Controller [8086:2a06] (rev 0c) lspci -knn: 00:03.3 Serial controller [0700]: Intel Corporation Mobile PM965/GM965 KT Controller [8086:2a07] (rev 0c) lspci -knn: Kernel driver in use: serial lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82566MM Gigabit Network Connection [8086:1049] (rev 03) lspci -knn: Kernel driver in use: e1000e lspci -knn: Kernel modules: e1000e lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 [8086:2835] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 [8086:283a] (rev 03) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 03) lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 [8086:283f] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 [8086:2841] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 [8086:2843] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 [8086:2845] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 [8086:2847] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 [8086:2830]
non-free firmware, WEP/WPA, freeness and disk-order on reboot.
Hello,
When a firmware is missing, DI now prompts for a device with that
firmware. (great, I love that feature!).
If I understand the situation correctly, the fact that one introduces a
usb key causes that key to be enumerated before the sata hard disk,
which causes grub to write an incorrect configuration file (since the
standard kernel enumerate HD first).
As a workaround for that bug :
Shouldn't the prompt for firmware mention that this is optional? (and
the side effects).
in packages/hw-detect/debian/hw-detect.templates
Template: hw-detect/load_firmware
Type: boolean
Default: true
Shouldn't the default value be false?
# :sl2:
_Description: Load missing firmware from removable media?
Some of your hardware needs non-free firmware files to operate. The
firmware can be loaded from removable media, such as a USB stick or
floppy.
If the enumeration order can't be fixed, maybe we could add
Probing for those firmware may prevent the system from rebooting
properly, as described in the Installation Guide, chapter...
.
The missing firmware files are: ${FILES}
I also suggest to add a note like (You can either provide a raw
firmware, or a .deb package)
.
If you have such media available now, insert it, and continue.
Finally, since D-I doesn't seems to support WPA. I wonder if we really
should prompt for wifi firmware... which would encourage people to use
the very unsecure WEP protocol?
I could work on a patch to use a blacklist of modules so we don't ask
for those wifi firmwares.
Regards,
Franklin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-free firmware, WEP/WPA, freeness and disk-order on reboot.
On Sat, 2008-10-25 at 22:01 +0200, Frans Pop wrote: On Saturday 25 October 2008, Steve Langasek wrote: On Sat, Oct 25, 2008 at 06:01:42PM +0200, Frank Lin PIAT wrote: If I understand the situation correctly, the fact that one introduces a usb key causes that key to be enumerated before the sata hard disk, which causes grub to write an incorrect configuration file (since the standard kernel enumerate HD first). That would only be true if the USB disk is detected by the kernel prior to the SATA hard disk, which seems to only be plausible if the SATA driver itself needs to load firmware. Is that what you're talking about here? It's true for any net-based installation (netboot, mini.iso) as those images do contain usb-related modules, but not disk drivers. Would it be possible/sensible to add the disk drivers to the netboot and mini.iso image. At 5am, this seems to be an easy way to ensure that DI and regular systems enumerates disks in the same order (I understand that the main drawback is that disk images size would get increased, but I don't know the current limits). Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release RC1 NOW
Hello, By the way, could you update the Installation Guide (at [1]). On Thu, 2008-10-23 at 09:47 +0200, Martin Michlmayr wrote: * Frans Pop [EMAIL PROTECTED] [2008-10-22 21:16]: The continued postponing of RC1 is hurting D-I and Debian in general! Again, I'm totally with Frans on this. Thanks, Franklin [1] http://www.debian.org/releases/testing/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503244: installation-report: Lenny on Thinkpad T42 (2373) [SUCCESS]
Package: installation-reports Version: 2.38 Severity: normal -- Package-specific info: Boot method: network/PXE Image version: http://people.debian.org/~joeyh/d-i/images/daily/netboot/gtk/netboot.tar.gz Date: Machine: IBM Thinkpad T43 (type 2373) Partitions: manual 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: [ ] Load installer modules: [o] Detect hard drives: [o] Partition hard drives: [o] Install base system:[o] Clock/timezone setup: [o] User/password setup:[o] Install tasks: [o] Install boot loader:[o] Overall install:[o] Comments/Problems: None, again ;) * This laptop has an intel 2200 wireless chipset. D-I prompted for the firmware ipw2200-bss.fw I retreived that firmware as explained in the release notes and from http://wiki.debian.org/ipw2200 End users should visit: http://wiki.debian.org/InstallingDebianOn/Thinkpad/T42/lenny Thanks, Franklin == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=5.0 (lenny) - installer build 20081023-09:05 X_INSTALLATION_MEDIUM=netboot-gtk == Installer hardware-summary: == umame -a: Linux t42 2.6.26-1-486 #1 Thu Oct 9 14:22:52 UTC 2008 i686 unknown lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 82855PM Processor to I/O Controller [8086:3340] (rev 03) lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 82855PM Processor to AGP Controller [8086:3341] (rev 03) lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 01) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 01) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 01) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.7 USB Controller [0c03]: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller [8086:24cd] (rev 01) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 81) lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge [8086:24cc] (rev 01) lspci -knn: 00:1f.1 IDE interface [0101]: Intel Corporation 82801DBM (ICH4-M) IDE Controller [8086:24ca] (rev 01) lspci -knn: Kernel driver in use: PIIX_IDE lspci -knn: Kernel modules: piix lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller [8086:24c3] (rev 01) lspci -knn: 00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 01) lspci -knn: 00:1f.6 Modem [0703]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller [8086:24c6] (rev 01) lspci -knn: 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] [1002:4c57] lspci -knn: 02:00.0 CardBus bridge [0607]: Texas Instruments PCI4520 PC card Cardbus Controller [104c:ac46] (rev 01) lspci -knn: Kernel driver in use: yenta_cardbus lspci -knn: Kernel modules: yenta_socket lspci -knn: 02:00.1 CardBus bridge [0607]: Texas Instruments PCI4520 PC card Cardbus Controller [104c:ac46] (rev 01) lspci -knn: Kernel driver in use: yenta_cardbus lspci -knn: Kernel modules: yenta_socket lspci -knn: 02:01.0 Ethernet controller [0200]: Intel Corporation 82540EP Gigabit Ethernet Controller (Mobile) [8086:101e] (rev 03) lspci -knn: Kernel driver in use: e1000 lspci -knn: Kernel modules: e1000 lspci -knn: 02:02.0 Network controller [0280]: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection [8086:4220] (rev 05) lspci -knn: Kernel driver in use: ipw2200 lspci -knn: Kernel modules: ipw2200 lsmod: Module Size Used by lsmod: ufs63620 0 lsmod: qnx47684 0 lsmod: ntfs 180416 0 lsmod: dm_mod 45384 0 lsmod: md_mod 65940 0 lsmod: xfs 446836 0 lsmod: reiserfs 187008 0 lsmod: jfs 148060 0 lsmod: ext3 103432 1 lsmod: jbd35092 1
