Bug#617943: debian-installer: isolated "make build_netboot" fails due to missing 2.6.32 modules
Otavio Salvador wrote: > The installer itself, sometimes, need modifications or fixes to be able to > handle newer kernel versions so the version that is hard-coded on those is > the version that is supported by the installer. It is not only a matter of > recompile installer against the new kernel (sometimes this works by this is > not guaranteed). Another important point is that there are architectures > that use different kernels depending on the subarch (e.g armel uses iop32x, > kirkwood and others) and dynamically it is more difficult to handle this. > > Specifically about the patch it is incomplete since it doesn't handle all > the architectures thus we can't take it. Hi, Sorry I haven't had time to get back to this until just now. So, I don't have any of the subarch's to test this, but I believe they are already handled appropriately in the "UDEBS =" line in my patch. I'm concluding this based on the .cfg files, for example iop32x.cfg would produce 2.6.32-5 for the KERNELIMAGEVERSION var, and that is what I would automatically return from the automatic processing of the Packages file. Will it ever be the case that the kernel version as stated in the debian-installer_binary-ARCH_Packages file will differ from the hard-coded value in the cfg files? It seems like they would have to be the same, otherwise d-i would fail trying to download non-existent files, but I may be missing something. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2011092313.27e767e7ade48b285bee5...@gmail.com
Bug#642183: debian-installer: hybrid iso sizing issue for unstable build
package: debian-installer
version: 20110106
severity: important
tags: patch
d-i fails to build unstable x86 netboot images (see below), which
will become a problem as d-i development moves forward with newer
kernels/packages coming in from unstable. I've attached a patch
that fixes this by using the default last sector for the msdos
partition instead of a size offset. This certainly works, but I'm
not sure if its an ideal solution.
Best wishes,
Mike
$ cd build && USE_UDEBS_FROM=unstable make build_netboot
geniso_hybrid_plus_firmware_partition ./tmp/netboot/mini.iso
mkfs.msdos 3.0.9 (31 Jan 2010)
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4, default 2): First sector (24576-36863, default 24576):
Using default value 24576
Last sector, +sectors or +size{K,M,G} (24576-36863, default 36863): Value out
of range.
Last sector, +sectors or +size{K,M,G} (24576-36863, default 36863): Last
sector, +sectors or +size{K,M,G} (24576-36863, default 36863): Value out of
range.
Last sector, +sectors or +size{K,M,G} (24576-36863, default 36863): Value out
of range.
Last sector, +sectors or +size{K,M,G} (24576-36863, default 36863): Last
sector, +sectors or +size{K,M,G} (24576-36863, default 36863):
make[2]: *** [arch_miniiso] Error 1
make[1]: *** [_build] Error 2
make: *** [build_netboot] Error 2
--- util/geniso_hybrid_plus_firmware_partition.orig 2011-09-19 23:27:56.0 -0400
+++ util/geniso_hybrid_plus_firmware_partition 2011-09-19 23:28:06.0 -0400
@@ -49,7 +49,7 @@
echo p
echo 2
echo
-echo +"$firmware_volume_size_M"M
+echo
# Pedantically, set partition type to 1: FAT 16
echo t
Bug#642179: debian-installer: Installs on drives larger than 2.19TB fails with older bios
Package: debian-installer Version: 20110106+squeeze3 Severity: normal Tags: d-i squeeze -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Install attempts on a Tyan S7002 failed with a drive larger than 2.19TB (would fail at the grub installation) I was able to move an install to a 1TB drive then move to a larger disk - grow the partition, but on a kernel update it would no longer boot. This might have to do with the 2.19TB limitation of MBR - which means a move to GUID Partition Table (GPT) and possibly the need for a BIOS's that supports GUID. (See: http://en.wikipedia.org/wiki/GUID_Partition_Table ) In the mean time Debian installer fails to give any warning about larger drives and fdisk/sfdisk also fail to warn. The current kernels support GPT, but it is less than clear how older bios interact. It might be that just the boot disk needs to be smaller than 2.19TB and that storage disks formatted with GPT will work fine on machines with BIOS's that don't support GPT? It is also possible that fdisk/cfdisk/sfdisk are failing without warning if one tries to use these large drives. gparted supports EFI/GPT. I'm thinking that D-i needs to detect the large drive size, possible the ability of the bios to work with this drive size and give a warning. There might be problems supporting 2TB drives with the partioner in D-I that is independent to the BIOS. Sadly I have more questions than answers and hope someone with a better understanding of this issue writes it up. -- 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/20110920010828.31805.60339.reportbug@malaysia.xtronics.network
Bug#642160: installation-reports: no bags
Package: installation-reports Severity: wishlist Dear Maintainer, *** Please consider answering these questions, where appropiate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- Package-specific info: Boot method: netinstall Image version: debian-testing-amd64-netinst.iso 15.09.11 Date: Machine: asus A7U Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O ] Detect network card:[O ] Configure network: [O ] Detect CD: [O ] Load installer modules: [O ] Detect hard drives: [O ] Partition hard drives: [O ] Install base system:[O ] Clock/timezone setup: [O ] User/password setup:[O ] Install tasks: [O ] Install boot loader:[O ] Overall install:[O ] Comments/Problems: -- 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 sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="7.0 (wheezy) - installer build 20110915-00:07" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux A7U 3.0.0-1-amd64 #1 SMP Sun Jul 24 02:24:44 UTC 2011 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: ATI Technologies Inc RS690 Host Bridge [1002:7910] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:14f7] lspci -knn: 00:01.0 PCI bridge [0604]: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx) [1002:7912] lspci -knn: 00:04.0 PCI bridge [0604]: ATI Technologies Inc Device [1002:7914] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:05.0 PCI bridge [0604]: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 1) [1002:7915] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:06.0 PCI bridge [0604]: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 2) [1002:7916] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:07.0 PCI bridge [0604]: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 3) [1002:7917] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:12.0 SATA controller [0106]: ATI Technologies Inc SB600 Non-Raid-5 SATA [1002:4380] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:14f7] lspci -knn: Kernel driver in use: ahci lspci -knn: 00:13.0 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI0) [1002:4387] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:14f7] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.1 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI1) [1002:4388] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:14f7] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.2 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI2) [1002:4389] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:14f7] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.3 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI3) [1002:438a] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:14f7] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.4 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI4) [1002:438b] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:14f7] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.5 USB Controller [0c03]: ATI Technologies Inc SB600 USB Controller (EHCI) [1002:4386] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:14f7] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 14) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:14f7] lspci -knn: 00:14.1 IDE interface [0101]: ATI Technologies Inc SB600 IDE [1002:438c] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:14f7] lspci -knn: Kernel driver in use: pata_atiixp lspci -knn: 00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia (Intel HDA) [1002:4383] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:1339] lspci -knn: 00:14.3 ISA bridge [0601]: ATI Technologies Inc SB600 PCI to LPC Bridge [1002:438d] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:14f7] lspci -knn: 00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384] lspci -knn: 00:18.0 Host b
Bug#642159: debian-installer preseed broken with apt-cacher-ng mirror
Package: debian-installer Version: 20110106+squeeze3 Severity: normal Tags: d-i Copied from an Ubuntu bug report, since it resembles my problem as well: In my preseed file I set "d-i mirror/http/proxy string http://apt-cacher:3142/";, this is an apt-cacher-ng proxy. This works correctly for installing the system. I expect "d-i mirror/http/proxy" to only apply to the debian installer http proxy (apt proxy), and all other http applications, e.g., wget, curl, lynx to not use that setting. Instead when I run applications from the Kickstart %post section, all HTTP connections are proxied; curl, wget, lynx, hg (mercurial), everything. Once the system installs and reboots all is good, the only remanence of the mirror/http/proxy setting is in /etc/apt/apt.conf, which is fine (though I think that should be configurable too). mirror/http/proxy is setting the environment variable http_proxy. Repo: Set "d-i mirror/http/proxy string http://apt-cacher:3142/"; in a preseed (use your local mirror). Use a Kickstart post section like this: %post --interpreter=/bin/bash exec < /dev/tty3 > /dev/ttyS0 chvt 3 ( echo "## http_proxy = $http_proxy" echo "## lynx dump head" lynx -dump -head http://example.com echo "## wget" wget -O /root/test http://example.com ) 2>&1 | /usr/bin/tee /var/log/post_install.log chvt 1 After install check /var/log/post_install.log and it will look like: ## http_proxy = http://apt-cacher:3142/ ## lynx dump head HTTP/1.1 403 Forbidden file type or location Date: Thu Apr 22 16:29:10 2010 Server: Debian Apt-Cacher NG/0.4.6 ## wget --2010-04-22 09:29:10-- http://example.com Resolving apt-cacher... 10.0.0.10 Connecting to apt-cacher|10.0.0.10|:3142... connected. Proxy request sent, awaiting response... 403 Forbidden file type or location 2010-04-22 09:29:10 ERROR 403: Forbidden file type or location. The workaround for me it to reset $http_proxy at the top of %post: export http_proxy="" Then all the applications that use http behave normally. Suggestion: Don't set $http_proxy with "d-i mirror/http/proxy", maybe set $apt_http_proxy if d-i needs an environment variable. For users that need a general proxy a setting like "d-i http/proxy" could be created. -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information -- 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/20110919204447.8659.48512.report...@kahlo.csde.washington.edu
Bug#642031: debootstrap: Debootstrap error when host and build have different kernels
On Sep 19, 2011 5:46 PM, "Joey Hess" wrote:
>
> Milo Mak wrote:
> > debian live-helper # chroot /data/ext/live-helper/chroot
> > root@debian:/# dpkg --force-depends --install
> > /var/cache/apt/archives/libc6_2.11.2-10_amd64.deb
> > (Reading database ... 349 files and directories currently installed.)
> > Unpacking libc6 (from .../libc6_2.11.2-10_amd64.deb) ...
> > [: 392: Illegal number: 3.0-3.dmz.2-liquorix-amd64
> > /var/lib/dpkg/tmp.ci/preinst: 392: arithmetic expression: expecting EOF:
> > "3.0-3.dmz.2-liquorix-amd64"
> > dpkg: error processing /var/cache/apt/archives/libc6_2.11.2-10_amd64.deb
> > (--install):
>
> This code from the libc6 2.11.2-10 preinst is broken when presented
> with a kernel version with only two numbers, like "3.0-foo". One of
> likely many reasons that Debian versions the kernel 3.0.0-foo.
>
> linux_compare_versions () {
>verA=$(($(echo "$1" | sed 's/\([0-9]*\)\.\([0-9]*\)\.\([0-9]*\).*/\1 \*
1 + \2 \* 100 + \3/')))
>verB=$(($(echo "$3" | sed 's/\([0-9]*\)\.\([0-9]*\)\.\([0-9]*\).*/\1 \*
1 + \2 \* 100 + \3/')))
>
>test $verA -$2 $verB
> }
>
> It's fixed already in the version in unstable. (Although it's amusing
> to note this code in turn falls over if Linus decides a better kernel
> version is "4-foo".)
>
> linux_compare_versions () {
>verA=$(($(echo "$1" | sed 's/^\([0-9]*\.[0-9]*\)\([^.0-9]\|$\)/\1.0\2/;
s/\([0-9]*\)\.\([0-9]*\)\.\([0-9]*\).*/\1 \* 1 + \2 \* 100 + \3/')))
>verB=$(($(echo "$3" | sed 's/^\([0-9]*\.[0-9]*\)\([^.0-9]\|$\)/\1.0\2/;
s/\([0-9]*\)\.\([0-9]*\)\.\([0-9]*\).*/\1 \* 1 + \2 \* 100 + \3/')))
>
>test $verA -$2 $verB
> }
>
> I'm unsure about trying to work around this in debootstrap, despite
> https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/802985 having
> a LD_PRELOAD hack to do so.
>
> --
> see shy jo
Ah I see. Compiled a kernel with a name in the form of 3.x.y-foo and it did
resolve the issue.
Thanks
Milo Mak
Bug#642115: debian-installer: guided full disk encryption + LVM complains about insecure swap
Jon Dowland wrote: > If you choose Guided / Encrypted / LVM as the partitioning type, the resulting > scheme chosen by d-i basically looks like > > (physical partition) → (encrypted volume) → (LVM) → (swap) > > Thus, the swap is encrypted, but LVM sits between them. The code is this, and Max changed it most recently: # Accept e.g. swap on lvm on crypto if echo $device | grep -q "^/dev/mapper/"; then if dm_is_safe "$device"; then continue fi fi I wonder if perhaps the device for LVM does not look like /dev/mapper/ anymore. Perhaps it's seeing /dev// instead? -- see shy jo signature.asc Description: Digital signature
Processed: reassign 642115 to partman-crypto
Processing commands for cont...@bugs.debian.org: > reassign 642115 partman-crypto Bug #642115 [debian-installer] debian-installer: guided full disk encryption + LVM complains about insecure swap Bug reassigned from package 'debian-installer' to 'partman-crypto'. > thanks Stopping processing here. Please contact me if you need assistance. -- 642115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13164474226870.transcr...@bugs.debian.org
Processed: retitle 642031 to should debootstrap workaround libc6 kernel uname parsing bug (affects systems running non-debian kernels)
Processing commands for cont...@bugs.debian.org: > retitle 642031 should debootstrap workaround libc6 kernel uname parsing bug > (affects systems running non-debian kernels) Bug #642031 [debootstrap] debootstrap: Debootstrap error when host and build have different kernels Changed Bug title to 'should debootstrap workaround libc6 kernel uname parsing bug (affects systems running non-debian kernels)' from 'debootstrap: Debootstrap error when host and build have different kernels' > thanks Stopping processing here. Please contact me if you need assistance. -- 642031: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13164473846665.transcr...@bugs.debian.org
Re: Possible debootstrap issue related to different host computer kernel?
Jongi wrote: > I have tried to send a reportbug but am unsure as to whether it was successful > (prior reportbugs for other packages have not been). Your bug report went through. http://bugs.debian.org/cgi-bin/pkgreport.cgi?submitter=milo...@gmail.com -- see shy jo signature.asc Description: Digital signature
Bug#642031: debootstrap: Debootstrap error when host and build have different kernels
Milo Mak wrote:
> debian live-helper # chroot /data/ext/live-helper/chroot
> root@debian:/# dpkg --force-depends --install
> /var/cache/apt/archives/libc6_2.11.2-10_amd64.deb
> (Reading database ... 349 files and directories currently installed.)
> Unpacking libc6 (from .../libc6_2.11.2-10_amd64.deb) ...
> [: 392: Illegal number: 3.0-3.dmz.2-liquorix-amd64
> /var/lib/dpkg/tmp.ci/preinst: 392: arithmetic expression: expecting EOF:
> "3.0-3.dmz.2-liquorix-amd64"
> dpkg: error processing /var/cache/apt/archives/libc6_2.11.2-10_amd64.deb
> (--install):
This code from the libc6 2.11.2-10 preinst is broken when presented
with a kernel version with only two numbers, like "3.0-foo". One of
likely many reasons that Debian versions the kernel 3.0.0-foo.
linux_compare_versions () {
verA=$(($(echo "$1" | sed 's/\([0-9]*\)\.\([0-9]*\)\.\([0-9]*\).*/\1 \*
1 + \2 \* 100 + \3/')))
verB=$(($(echo "$3" | sed 's/\([0-9]*\)\.\([0-9]*\)\.\([0-9]*\).*/\1 \*
1 + \2 \* 100 + \3/')))
test $verA -$2 $verB
}
It's fixed already in the version in unstable. (Although it's amusing
to note this code in turn falls over if Linus decides a better kernel
version is "4-foo".)
linux_compare_versions () {
verA=$(($(echo "$1" | sed 's/^\([0-9]*\.[0-9]*\)\([^.0-9]\|$\)/\1.0\2/;
s/\([0-9]*\)\.\([0-9]*\)\.\([0-9]*\).*/\1 \* 1 + \2 \* 100 + \3/')))
verB=$(($(echo "$3" | sed 's/^\([0-9]*\.[0-9]*\)\([^.0-9]\|$\)/\1.0\2/;
s/\([0-9]*\)\.\([0-9]*\)\.\([0-9]*\).*/\1 \* 1 + \2 \* 100 + \3/')))
test $verA -$2 $verB
}
I'm unsure about trying to work around this in debootstrap, despite
https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/802985 having
a LD_PRELOAD hack to do so.
--
see shy jo
signature.asc
Description: Digital signature
Bug#642115: debian-installer: guided full disk encryption + LVM complains about insecure swap
Package: debian-installer Severity: normal Hi, Using a daily build: -rw-r--r-- 1 libvirt-qemu kvm 240M Sep 16 10:00 debian-testing-i386-netinst.iso If you choose Guided / Encrypted / LVM as the partitioning type, the resulting scheme chosen by d-i basically looks like (physical partition) → (encrypted volume) → (LVM) → (swap) Thus, the swap is encrypted, but LVM sits between them. After choosing that partitioning scheme, you are then asked to input the encryption pass-phrase. You are then shown the scheme layed out like with the manual partitioner. After you accept this, you are warned that the swap space is unsafe. d-i refuses to proceed at this point. If you set the swap LV to "do not use", you can proceed (without swap) and fix it later on. I think this is incorrect and the swap space *is* safe, since it is sitting on top of an encrypted partition. However either way, the guided partitioner should suggest a scheme which is safe. -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (700, 'stable'), (600, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20110919144713.ga19...@inoshiro.ncl.ac.uk
Bug#627015: From Mrs.Lerato Mutasa Please Kindly Open the Attachment File Thanks
-- 2011/8/12 MRS LERATO MUTASA > > > From Mrs.Lerato Mutasa > Please Kindly Open the Attachment File > Thanks O YES SUCK MY \_ | | | | THANK YOU MRS LERATO YOU SUCK VERY GOOD I TELL IT ALL OF MY PEOPLE -- --
