Bug#597799: installation-report: GPT related issues
Package: installation-reports Version: 2.42 Severity: important Tags: squeeze -- Package-specific info: Boot method: network Image version: http://ftp.nl.debian.org/debian/dists/lenny/main/installer-amd64/current/images/netboot/gtk/netboot.tar.gz 17:58 26-06-10 Date: 22-09-2010 Machine: Custom-made i7 machine Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] Configure network: [O] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[E] Comments/Problems: First, a little digression about the network card. The on-board network controller is a Realtek controller for which the installer told me I needed a non-free firmware. It happens that answering No left the network... working. It would have been helpful if the installer told me the network may still work without the firmware. Back to the core of my issues. I went through a manual partitionning, and didn't create a boot partition for the grub core image, assuming I was creating an MBR partition. It turned out, in the end, that GRUB failed because of that, because the partition table was GPT. I didn't see anything about GPT being used (or maybe wasn't paying too much attention), and surely the partitioner could issue a warning that no such partition was created and that the risk is that GRUB can't be installed. Other than that, everything went fine. Awesome installer. Thanks Mike -- 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=6.0 (squeeze) - installer build 20100912 X_INSTALLATION_MEDIUM=netboot-gtk == Installer hardware-summary: == uname -a: Linux goemon 2.6.32-5-amd64 #1 SMP Thu Aug 12 13:01:50 UTC 2010 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DMI [8086:d131] (rev 11) lspci -knn: Subsystem: Micro-Star International Co., Ltd. Device [1462:7588] lspci -knn: 00:03.0 PCI bridge [0604]: Intel Corporation Core Processor PCI Express Root Port 1 [8086:d138] (rev 11) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:08.0 System peripheral [0880]: Intel Corporation Core Processor System Management Registers [8086:d155] (rev 11) lspci -knn: Subsystem: Device [0062:0088] lspci -knn: 00:08.1 System peripheral [0880]: Intel Corporation Core Processor Semaphore and Scratchpad Registers [8086:d156] (rev 11) lspci -knn: Subsystem: Device [0062:0088] lspci -knn: 00:08.2 System peripheral [0880]: Intel Corporation Core Processor System Control and Status Registers [8086:d157] (rev 11) lspci -knn: Subsystem: Device [0062:0088] lspci -knn: 00:08.3 System peripheral [0880]: Intel Corporation Core Processor Miscellaneous Registers [8086:d158] (rev 11) lspci -knn: Subsystem: Device [0062:0088] lspci -knn: 00:10.0 System peripheral [0880]: Intel Corporation Core Processor QPI Link [8086:d150] (rev 11) lspci -knn: Subsystem: Device [0062:0088] lspci -knn: 00:10.1 System peripheral [0880]: Intel Corporation Core Processor QPI Routing and Protocol Registers [8086:d151] (rev 11) lspci -knn: Subsystem: Device [0062:0088] lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05) lspci -knn: Subsystem: Micro-Star International Co., Ltd. Device [1462:7588] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 05) lspci -knn: Subsystem: Micro-Star International Co., Ltd. Device [1462:7588] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 05) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 [8086:3b4c] (rev 05) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.6 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 7 [8086:3b4e] (rev 05) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.7 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 8 [8086:3b50]
Bug#325002: sqmi on which the the of
the reasons density Peter usually been is selection Dakota Northern -- 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/debian-boot
Bug#250025: sign used front
away students but Mexico use Million of everlasting -- 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/debian-boot
Bug#311152: Fuentes cultural as
characters still organizations Saving -- 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/debian-boot
Bug#597799: installation-report: GPT related issues
On Thu, Sep 23, 2010 at 08:13:26AM +0200, Mike Hommey wrote: Back to the core of my issues. I went through a manual partitionning, and didn't create a boot partition for the grub core image, assuming I was creating an MBR partition. It turned out, in the end, that GRUB failed because of that, because the partition table was GPT. I didn't see anything about GPT being used (or maybe wasn't paying too much attention), and surely the partitioner could issue a warning that no such partition was created and that the risk is that GRUB can't be installed. Oh I forgot to add this: the installed fdisk is pointless as the only thing it can do is tell you to use parted, which supports GPT... except parted is not installed. If the install is done on GPT, shouldn't parted be installed (or any other fdisk equivalent supporting GPT) 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/20100923101237.ga24...@glandium.org
Bug#277592: ascend those Rufus postmodernism not
new spoken of ineffective similar Act Real paid -- 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/debian-boot
Bug#597799: installation-report: GPT related issues
On Thu, Sep 23, 2010 at 12:12:37PM +0200, Mike Hommey wrote: On Thu, Sep 23, 2010 at 08:13:26AM +0200, Mike Hommey wrote: Back to the core of my issues. I went through a manual partitionning, and didn't create a boot partition for the grub core image, assuming I was creating an MBR partition. It turned out, in the end, that GRUB failed because of that, because the partition table was GPT. I didn't see anything about GPT being used (or maybe wasn't paying too much attention), and surely the partitioner could issue a warning that no such partition was created and that the risk is that GRUB can't be installed. Oh I forgot to add this: the installed fdisk is pointless as the only thing it can do is tell you to use parted, which supports GPT... except parted is not installed. If the install is done on GPT, shouldn't parted be installed (or any other fdisk equivalent supporting GPT) Was this a blank unused HD or had something else already been installed before? How big is the HD? I have not seen Debian efault to GPT unless the disk was over 2TB before, or unless windows 7 had already chosen to make it GPT. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100923132955.gb8...@caffeine.csclub.uwaterloo.ca
Bug#597799: installation-report: GPT related issues
On Thu, Sep 23, 2010 at 09:29:55AM -0400, Lennart Sorensen wrote: On Thu, Sep 23, 2010 at 12:12:37PM +0200, Mike Hommey wrote: On Thu, Sep 23, 2010 at 08:13:26AM +0200, Mike Hommey wrote: Back to the core of my issues. I went through a manual partitionning, and didn't create a boot partition for the grub core image, assuming I was creating an MBR partition. It turned out, in the end, that GRUB failed because of that, because the partition table was GPT. I didn't see anything about GPT being used (or maybe wasn't paying too much attention), and surely the partitioner could issue a warning that no such partition was created and that the risk is that GRUB can't be installed. Oh I forgot to add this: the installed fdisk is pointless as the only thing it can do is tell you to use parted, which supports GPT... except parted is not installed. If the install is done on GPT, shouldn't parted be installed (or any other fdisk equivalent supporting GPT) Was this a blank unused HD or had something else already been installed before? How big is the HD? I have not seen Debian efault to GPT unless the disk was over 2TB before, or unless windows 7 had already chosen to make it GPT. The disk is a new one, though I didn't check if there was a pre-existing partitioning (but I really doubt it). OTOH, the disk is 2000GB, which is not quite over 2TB, but close enough that it may have mattered. 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/20100923133908.ga6...@glandium.org
Bug#597854: bug report
Package: installation-reports Boot method: DVD Image version: http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-dvd/debian-testing-i386-DVD-1.iso Date: 23 October 2010 0530 Machine: Asus Z9000 Processor: Pentium M Memory: 1 GB Partitions: Have another OS on it at present, so I could back into debian lenny Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: ATI Technologies Inc RS300 Host Bridge [1002:5830] (rev 02) Kernel driver in use: agpgart-ati 00:01.0 PCI bridge [0604]: ATI Technologies Inc Radeon 9100 IGP AGP Bridge [1002:5838] Kernel modules: shpchp 00:13.0 USB Controller [0c03]: ATI Technologies Inc OHCI USB Controller #1 [1002:4347] (rev 01) Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00:13.1 USB Controller [0c03]: ATI Technologies Inc OHCI USB Controller #2 [1002:4348] (rev 01) Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00:13.2 USB Controller [0c03]: ATI Technologies Inc EHCI USB Controller [1002:4345] (rev 01) Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd 00:14.0 SMBus [0c05]: ATI Technologies Inc SMBus [1002:4353] (rev 18) Kernel modules: i2c-piix4 00:14.1 IDE interface [0101]: ATI Technologies Inc Dual Channel Bus Master PCI IDE Controller [1002:4349] Kernel driver in use: pata_atiixp Kernel modules: pata_atiixp 00:14.3 ISA bridge [0601]: ATI Technologies Inc Device [1002:434c] 00:14.4 PCI bridge [0604]: ATI Technologies Inc IXP200 3COM 3C920B Ethernet Controller [1002:4342] 00:14.5 Multimedia audio controller [0401]: ATI Technologies Inc IXP150 AC'97 Audio Controller [1002:4341] Kernel driver in use: ATI IXP AC97 controller Kernel modules: snd-atiixp 00:14.6 Modem [0703]: ATI Technologies Inc IXP AC'97 Modem [1002:434d] (rev 01) Kernel driver in use: ATI IXP MC97 controller Kernel modules: snd-atiixp-modem 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS300M AGP [Radeon Mobility 9100IGP] [1002:5835] Kernel modules: radeonfb, radeon 02:05.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c475 [1180:0475] (rev b8) Kernel driver in use: yenta_cardbus Kernel modules: yenta_socket 02:05.1 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C551 IEEE 1394 Controller [1180:0551] Kernel driver in use: firewire_ohci Kernel modules: firewire-ohci 02:06.0 Ethernet controller [0200]: Broadcom Corporation BCM4401 100Base-T [14e4:4401] (rev 01) Kernel driver in use: b44 Kernel modules: b44 02:07.0 Network controller [0280]: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection [8086:4220] (rev 05) Kernel driver in use: ipw2200 Kernel modules: ipw2200 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:[E] Overall install:[E] Comments/Problems: The install seemed to go fine until it wasn't able to install the bootloader, then, of course, it wouldn't boot. Very strange, as squeeze installed fine around a month ago. However at that time, I couldn't get grub2 to recognize and boot lenny, so uninstalled it. I really like the looks of squeeze. I was excited to try it again, because I installed kernel 2.6.32 bpo on lenny, and it requires the uuid's of the partitions, and so might work with grub2 better. Thanks for any help and/or recommendations. john -- John F. Godfrey, Pastor Belgrade Christian Assembly Belgrade, MT 59714 Jesus said to him, 'I am the Way, and the Truth, and the Life; no one comes to the Father but through Me' (John 14:6). -- 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/1285257260.4906.10.ca...@spirit.org
Bug#597799: installation-report: GPT related issues
On Thu, Sep 23, 2010 at 03:39:08PM +0200, Mike Hommey wrote: The disk is a new one, though I didn't check if there was a pre-existing partitioning (but I really doubt it). OTOH, the disk is 2000GB, which is not quite over 2TB, but close enough that it may have mattered. Certainly MBR partitions do not work when you pass 2TB (2^32 512byte sectors). After all if it had a partition table already, it would have just used it. Now so far I have been running a few machines with GPT partitions on a 2.5TB raid for a few years and with grub2 it works just fine, even with a machine that just uses a plain old BIOS. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100923162845.gc8...@caffeine.csclub.uwaterloo.ca
Bug#380579: This leader to The for the
second De than launch club -- 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/debian-boot
Bug#337806: of Kaohsiung figurehead consecutive first established for
figurehead closely Shaw installations -- 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/debian-boot
Processed: Change submitter e-mail
Processing commands for cont...@bugs.debian.org: submitter 247757 peter.karbalio...@gmail.com Bug #247757 [partman-target] [sparc] bootable partitions need to be 1gb Changed Bug submitter to 'peter.karbalio...@gmail.com' from 'Peter Karbaliotis peter.karbalio...@ualberta.ca' End of message, stopping processing here. Please contact me if you need assistance. -- 247757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=247757 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.12852630801605.transcr...@bugs.debian.org
Bug#596889: flash-kernel: please add ARM-Versatile Express CA9x4 support
Hi Martin (and Loïc), I re-factored this patch to incorporate the suggested changes and so it will apply cleanly to the latest svn repository. See comments in-line: On 09/19/2010 09:38 AM, Loïc Minier wrote: Hey Sorry for the delay On Tue, Sep 14, 2010, Matt Waddel wrote: + check_size kernel $(($kfilesize + 8 + 64)) $kmtdsize The 8+64 seems to be copied from other platforms which prepend 8 bytes of ARM assembly to set the machine id (the devio calls in the script) and wrap the resulting prefixed kernel in an uImage which presunably adds 64 bytes of header -- I checked the latter with a simple mkimage call on a vmlinuz file, and it showed exactly 64 bytes of increment, but I have no idea whether any padding / rounding is going on, or whether your specific mkimage args might require more than 64 bytes. So I think this should be: check_size kernel $(($kfilesize + 64)) $kmtdsize but am not sure. Yep - this was a copy paste error. The extra 8 bytes are not required. + tmp=$(tempfile) + cat $kfile $tmp + mkimage -A arm -O linux -T kernel -C none -a 0x60008000 \ + -e 0x60008000 -n Linaro Kernel -d $tmp $tmp.uboot \ + 2 1/dev/null Don't think you actually need a tmp file since you don't prepend anything to the kernel; just mkimage $kfile directly. Removed the $tmp file creation. + printf Erasing Kernel NOR space... 2 + dd if=/dev/zero of=$kmtd bs=$kmtdsize count=1 2/dev/null Does one really need to erase the NOR space? Given that access are done with mtdblock devices, I expected the kenrel would just do it. In some cases, it's useful to zero-pad, but I'm not sure I see why here. Good catch - removing this step makes the upgrade go a _lot_ faster. + initrd_nor_size=25165824 Hardcoding the value sucks; could you please read it from /proc/mtd? Apparently, there's information since you do: + imtd=$(mtdblock initrd) you can get the size of the mtd just like for the kernel with: imtdsize=$(mtdsize initrd) Done. On Tue, Sep 14, 2010, Martin Michlmayr wrote: That's fine but you should also add support for the udeb, i.e. debian/flash-kernel-installer.isinstallable, debian/flash-kernel-installer.postinst Perhaps not unless we add d-i support? Right now, this board is only used in Linaro images and we don't use d-i or udebs at all, only flash-kernel for upgrades. This might change in the future though. I didn't think about this when I suggested to Matt he could send the Vexpress support to Debian. Would you rather have us add d-i support as well, or can you live with just the flash-kernel.deb changes for now? Martin - I am sending this patch in 2 sections. One to fix the problems found in the code review and one to add the d-i parts. However, like Loïc pointed out the d-i sections are not tested. I think those changes are pretty straight forward, but without testing it is risky to add them. I'm ok if you decide not to. Would it also make sense to add the device to initramfs-tools/hooks/flash_kernel_set_root? Ah good catch; Matt, this allows either setting a default root= in the initrd for cases where the bootloader might not pass one, or to always override the root= passed by the bootloader. Depending on what the default bootloader config is, pick one! :-) If you allow to install to anywhere and the bootloader has a hardcoded root=, override is the best choice; if the bootloader does not pass any root= by default, default is the best choice. If you tell people to upgrade the bootloader config, it doesn't matter. I didn't know or I didn't remember about this set_root infrastructure, but I suppose another option is to arrange to update the bootloader config to set root=, in which case one doesn't need the initramfs bits. Colin, Loïc: can you comment on the patch since I don't know anything about Versatile Express? Eh, I don't know much either; good idea to have copied Colin as I understand he knows the hardware quite well. case $machine in + ARM-Versatile Express CA9x4) + check_mtd Should there be a call to check_subarch? Or there an agreen subarch name for this platform? I think the subarch is vexpress, The subarch is vexpress but I need to note that I find this test quite bad for the mid-term. It means we're stuck with one kernel per-subarch. Perhaps we should check whether the corresponding kernel's config has support for this subarch instead? Isn't the subarch variable is just the last value of the kernel name? So in this case vmlinuz-2.6.35-1006-linaro-vexpress = vexpress. If there are other tiles that can connect to the Versatile Express motherboard won't they have similar kernel naming constructs? Wouldn't this mean we could have multiple kernels per
Bug#595903: apt-setup: Fail to set up DVD as APT source during installation
Be patient with me for my english. After done the minimal installation (by squeeze dvd medium 20100913), the installer does install nothing more, also after uncommenting the installation disk line in sources.list. I needed to end installation as it was, and rebooted the system with another bootloader from another partition. Trying to install remaining packages, aptitude ask to insert the dvd #1, so I do that, but installation fails with file not found error for each package. Noted that the disk were installed by aptitude on /media/apt, I unmounted it and remounted on /media/cdrom. Now the installation goes straight ahead. So the installer mounts the disk on one place but searches its contents on another. Regards, Franco -- 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/4c9bdaee.8090...@yahoo.it
Bug#550584: Running flash-kernel automatically from postinst
tags 550584 +patch
thanks
Hiya,
I'm just upgrading the kernels on the armel dev boards we're hosting
at ARM for buildds, and I've done exactly what's suggested here. I've
added the following script as /etc/kernel/postinst.d/zz-flash-kernel :
---
#!/bin/sh
version=$1
bootopt=
# passing the kernel version is required
[ -z ${version} ] exit 0
echo Running flash-kernel ${version}
flash-kernel ${version}
-
--
Steve McIntyre, Cambridge, UK.st...@einval.com
Support the Campaign for Audiovisual Free Expression: http://www.eff.org/cafe/
--
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/20100923115546.ga24...@einval.com
Processed: Running flash-kernel automatically from postinst
Processing commands for cont...@bugs.debian.org: tags 550584 +patch Bug #550584 [flash-kernel] flash-kernel not run when going to new upstream kernel version Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 550584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550584 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.128530439726682.transcr...@bugs.debian.org
Bug#594878: flash-kernel: please add mv78xx0 support
I've added things to initramfs-tools/hooks/flash_kernel_set_root locally, and I'm looking at updating the udeb too. However, it's not very clear what's needed. Looking at code in debian/flash-kernel-installer.postinst, the comment on the default case in write_to_flash() seems backwards to me: # Assume that we write to flash for all other devices *) return 0 ;; In debian/flash-kernel-installer.isinstallable, what does ininstallable mean? That the flash-kernel package should be installed? I'm looking for the archdetect code now so I can test it on the hardware to see what's returned. -- Steve McIntyre, Cambridge, UK.st...@einval.com You raise the blade, you make the change... You re-arrange me 'til I'm sane... -- 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/20100923123128.ga28...@einval.com
