Bug#596762: installation-reports: installer failed to add winXP to grub2
(answering to the bug report and leaving your full answer so that it's recordedas your answer was only a private message to me) Quoting sdfsdfsdf ewfwdfsdf (spamfang1...@yahoo.de): > I have used the snapshot from today (2010/09/14). > > 1. Grub2 still did not include my winXP partition to the menuentries. Please provide the full installation log (you'll find it in /var/log/debian-installer on the installed system). > > 2. The grub-question-loop (see above) did not happen again. BUT this may be > due to the fact, that i had not the prior grub version installed anymore, but > already grub2. > > > > Could you use a daily build of the installer? At this step > > of the > > squeeze development, we no longer recommend using alpha1 > > releases. > > > > GRUB issues, particularly, should be tested with latest > > releases. > > > > You can find daily builds from > > http://www.debian.org/devel/debian-installer. Please > > preferrably > > choose the *netboot* image (not netinst). Despite its name, > > it is not > > reserved for people who use network boot servers. It is > > indeed just an > > "as minimal as possible" image that downloads components > > off the > > network as soon as the network is up and running in D-I. > > > > > > > > -- 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/20100915052406.go12...@mykerinos.kheops.frmug.org
Re: kFreeBSD Hardware support part of the Debian Installation Guide
Quoting Samuel Thibault (sthiba...@debian.org): > Hello, > > I have commited (r64720) fixes and a bit of triaging for the kFreeBSD > Hardware support part in the Debian Installation Guide: replacing Linux > with kFreeBSD where it makes sense, dropping apparently Linux-specific > sections, enabling what I know apply to kFreeBSD. I just forwarded this to -i18n so that translators know they have work to do. signature.asc Description: Digital signature
Bug#596907: installation-reports: mostly successful squeeze install from USB stick
Quoting Miles Fidelman (mfidel...@ntcorp.com): Thanks for your regular tests. They help a lot figuring out areas that still need work. > Comments/Problems: > - no opportunity to load custom installer modules > - no opportunity to install grub legacy, installed grub2 ok > > successfully installed squeeze from a USB stick > > > 1. The installer mostly does things on auto-pilot - no splash screen (so no > opportunity to enter rescue mode), no opportunity to install optional > components, The first time it stops for user input is after entering the > partitioner. Next time is for tasksel. After that it goes all the way > through > installing grub before it stops. No language/country/keyboard/network questions? Loading custom modules is proposed only in expert mode. *That* is on purpose..:-) Rescue mode is to be chosen at boot time, by choosing a special entry in the boot menu. > > 2. It seems to install grub2, without giving the opportunity to install grub- > legacy. It seems to do all the right things, and the installed system boots > properly. I don't think we really want to still suppor tgrub-legavy during installation. Supporting grub2 has already been a suffisiant PITA..:-) signature.asc Description: Digital signature
Re: kFreeBSD Hardware support part of the Debian Installation Guide
Samuel Thibault, le Wed 15 Sep 2010 02:11:45 +0200, a écrit : > I have commited (r64720) fixes and a bit of triaging for the kFreeBSD > Hardware support part in the Debian Installation Guide: replacing Linux > with kFreeBSD where it makes sense, dropping apparently Linux-specific > sections, enabling what I know apply to kFreeBSD. > > There are however quite a few places which are mostly unknown to me: > typically, are SATA Disk/CDROM supported? I guess the answer is yes, > but there are a lot of questions like this which need correct answers. > > Basically, I'd say: read the i386/amd64 version of the manual, and check > which sections should be included also in the kfreebsd equivalents. I forgot to say: I mean section 2, specifically. Samuel -- 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/20100915001527.gc4...@const.famille.thibault.fr
kFreeBSD Hardware support part of the Debian Installation Guide
Hello, I have commited (r64720) fixes and a bit of triaging for the kFreeBSD Hardware support part in the Debian Installation Guide: replacing Linux with kFreeBSD where it makes sense, dropping apparently Linux-specific sections, enabling what I know apply to kFreeBSD. There are however quite a few places which are mostly unknown to me: typically, are SATA Disk/CDROM supported? I guess the answer is yes, but there are a lot of questions like this which need correct answers. Basically, I'd say: read the i386/amd64 version of the manual, and check which sections should be included also in the kfreebsd equivalents. Samuel -- 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/20100915001145.ga4...@const.famille.thibault.fr
Re: Bug#514654: debian-cd: [squeeze] include kbd on first CD rather than console-tools
On Mon, Feb 09, 2009 at 10:54:18PM +, Steve McIntyre wrote: >On Mon, Feb 09, 2009 at 09:01:54PM +, Colin Watson wrote: >>Package: debian-cd >>Severity: wishlist >> >>For squeeze, we'll be changing d-i to install kbd rather than >>console-tools. Please make sure that kbd ends up on the first CD and >>that console-tools doesn't. > >Sure, no problem. Hi, Just noticed that the tasks haven't been updated for this as requested. But I'm assuming that current daily CDs are working OK. Is this still desired, or should I close this wishlist bug now? Cheers, -- Steve McIntyre, Cambridge, UK.st...@einval.com Can't keep my eyes from the circling sky, Tongue-tied & twisted, Just an earth-bound misfit, I... -- 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/20100914221629.gd18...@einval.com
Bug#596907: installation-reports: mostly successful squeeze install from USB stick
Package: installation-reports Severity: normal Tags: d-i -- Package-specific info: Boot method: USB Image version: squeeze, daily build 9/14/10 16:07 using netinst .iso Date: 9/14/10 approx. 5pm Machine: custom tower Partitions: r...@linuxbox:/home/milesf# df -Tl FilesystemType 1K-blocks Used Available Use% Mounted on /dev/md2 ext3 9614052 3424084 5701600 38% / tmpfstmpfs 500924 0500924 0% /lib/init/rw udev tmpfs 495960 228495732 1% /dev tmpfstmpfs 500924 0500924 0% /dev/shm 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/E ] 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/E ] Overall install:[ O] Comments/Problems: - no opportunity to load custom installer modules - no opportunity to install grub legacy, installed grub2 ok successfully installed squeeze from a USB stick 1. The installer mostly does things on auto-pilot - no splash screen (so no opportunity to enter rescue mode), no opportunity to install optional components, The first time it stops for user input is after entering the partitioner. Next time is for tasksel. After that it goes all the way through installing grub before it stops. 2. It seems to install grub2, without giving the opportunity to install grub- legacy. It seems to do all the right things, and the installed system boots properly. 3. I Still need to figure out the nits of setting things up for a RAID1 /boot. - initially, it installs on one drive - it has the interesting feature that it sets root=(md0) - which grub2 seems to be able to handle at boot time, but you have to go back and manually install an MBR on the 2nd drive in order to load grub regardless of which drive is 1st in boot order - the new approach of referring to drives by GUID seems to present some trickiness - only one drive's info ends up in /etc/fstab - not sure yet what happens if that drive fails and you try to boot off a degraded array -- 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 20100914-16:04" X_INSTALLATION_MEDIUM=hd-media == Installer hardware-summary: == uname -a: Linux LinuxBox 2.6.32-5-486 #1 Thu Aug 12 12:59:56 UTC 2010 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 661FX/M661FX/M661MX Host [1039:0661] (rev 11) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: agpgart-sis lspci -knn: 00:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] SiS AGP Port (virtual PCI-to-PCI bridge) [1039:0003] lspci -knn: 00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] [1039:0964] (rev 36) lspci -knn: 00:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513 [IDE] [1039:5513] (rev 01) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: pata_sis lspci -knn: 00:02.7 Multimedia audio controller [0401]: Silicon Integrated Systems [SiS] AC'97 Sound Controller [1039:7012] (rev a0) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: 00:03.0 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:03.1 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:03.2 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:03.3 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 2.0 Controller [1039:7002] lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:7002] lspci -knn: Kernel driver i
Bug#596889: flash-kernel: please add ARM-Versatile Express CA9x4 support
* Matt Waddel [2010-09-14 14:05]: > -- The list of supported architectures seems pretty much alphabetical. So I >put this one at the top. Hope that's OK. That's fine but you should also add support for the udeb, i.e. debian/flash-kernel-installer.isinstallable, debian/flash-kernel-installer.postinst Would it also make sense to add the device to initramfs-tools/hooks/flash_kernel_set_root? Colin, Loïc: can you comment on the patch since I don't know anything about Versatile Express? > 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? > + kmtd=$(mtdblock "kernel") > + if [ -z "$kmtd" ]; then > + error "Cannot find mtd partition 'kernel'" > + fi > + check_dev_mtdblock "$kmtd" > + kmtdsize=$(mtdsize "kernel") > + check_size "kernel" $(($kfilesize + 8 + 64)) $kmtdsize > + printf "Generating a u-boot compatible kernel image... " >&2 > + 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 \ This shouldn't say "Linaro". I wonder if it would make sense to drop "Debian" from all kernel/ramdisk references. > + >&2 1>/dev/null > + printf "Erasing Kernel NOR space... " >&2 > + dd if=/dev/zero of=$kmtd bs=$kmtdsize count=1 2>/dev/null How large is this partition? The reason I ask is because I wonder why you don't pad the file on disk before writing it, but maybe that's a bad idea when the mtd partition is very large. (Same goes for the initrd partition) -- Martin Michlmayr http://www.cyrius.com/ -- 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/20100914215051.gn5...@jirafa.cyrius.com
Bug#249049: Healthcare/Business and many other marketing lists available
Send me an email here for a complete catalog including samples and stats: qualityli...@gmx.com Forward email to offthel...@gmx.com to purge you from our records -- 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/20100914214429.d1c4353...@webmail.verena.co.id
Bug#593235: flash-kernel-installer: Please add gta02 support
* Thibaut Girka [2010-08-31 23:43]: > If you're talking about the discussion in #503292, then yes, s3c24xx was > decided. Ok, that's fine then. > There is already basic (really basic, no display or even µSD) support in > mainline kernel, and the name is "GTA02". Ok. > > Why do you need to compress the kernel? It should be a zImage or > > LZMA-image already anywhere. > > Yeah, I know, that's a bit tricky (I commented it on the d-i target, but > I haven't sent it yet). > So, U-Boot have an image format called multi-file images. > But there is only one header for the whole image, and so, only one > compression method. > This compression method is used both to uncompress the kernel and as the > compression type of the initrd image. > If I don't compress the kernel and say "-C gzip", U-Boot will try to > uncompress the kernel, and will obviously fail (since the kernel is > executable and uncompress itself). > If I specify "-C none", it'll run the kernel just fine, but will fail to > tell the kernel that the initrd image is gzip-compressed... > So, the only way is to re-compress the kernel... We use multi-file images on the HP mv2120 and -C none works fine with a regular kernel/compressed initrd combination. Does u-boot actually need to tell the kernel that the ramdisk is compressed? AFAIK the kernel figures this out itself... but I don't have a Freerunner so I cannot verify this myself. Maybe you can test again if -C none works, but it it doesn't then I guess your patch is fine (but maybe with a comment). > > Will this actually boot on any Freerunner machines without the -p > > option you proposed in #584166? > > If you're lucky. > Indeed, the chances aren't negligible, maybe this bug will wait for > #584166. Ok, fine with me. -- Martin Michlmayr http://www.cyrius.com/ -- 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/20100914213858.gl5...@jirafa.cyrius.com
Bug#596787: marked as done (installation-reports: grub legacy writes incorrect menu.lst when disks are RAIDed)
Your message dated Tue, 14 Sep 2010 22:39:24 +0200 with message-id <20100914203924.gq3...@mykerinos.kheops.frmug.org> and subject line Re: Bug#596787: installation-reports: grub legacy writes incorrect menu.lst when disks are RAIDed has caused the Debian Bug report #596787, regarding installation-reports: grub legacy writes incorrect menu.lst when disks are RAIDed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 596787: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596787 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: important Tags: d-i system has two mirrored disks, /dev/md0 is boot, /dev/md2 is root selecting grub-legacy, and specifying either /dev/hda or (hd0) for installation results in a menu.lst file with the line groot=(md0) and all of the boot sections starting with root (md0) at boot time, grub throws an error - it (corretly) doesn't recognize md0 as a proper construction editing menu.lst to read groot=(hd0,0) and running update-grub leads to a correct and functional menu.lst -- Package-specific info: Boot method: CD Image version: squeeze alpha1 Date: Machine: custom tower Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] 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="6.0 (squeeze) - installer build 20100211" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux new-host-2 2.6.30-2-486 #1 Sat Sep 26 00:03:46 UTC 2009 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 661FX/M661FX/M661MX Host [1039:0661] (rev 11) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: 00:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] SiS AGP Port (virtual PCI-to-PCI bridge) [1039:0003] lspci -knn: 00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] [1039:0964] (rev 36) lspci -knn: 00:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513 [IDE] [1039:5513] (rev 01) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: SIS_IDE lspci -knn: 00:02.7 Multimedia audio controller [0401]: Silicon Integrated Systems [SiS] AC'97 Sound Controller [1039:7012] (rev a0) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: 00:03.0 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:03.1 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:03.2 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:03.3 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 2.0 Controller [1039:7002] lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:7002] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:04.0 Ethernet controller [0200]: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet [1039:0900] (rev 90) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: sis900 lspci -knn: 00:05.0 IDE interface [0101]: Silicon Integrated Systems [SiS] RAID bus controll
Bug#596889: flash-kernel: please add ARM-Versatile Express CA9x4 support
Package: flash-kernel Version: 2.13ubuntu17 Severity: wishlist Tags: patch -- System Information: Debian Release: squeeze/sid APT prefers lucid APT policy: (500, 'lucid') Architecture: armel (armv7l) Kernel: Linux 2.6.35-1005-linaro-vexpress (SMP w/4 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 flash-kernel depends on: ii devio 1.2-1build1 correctly read (or write) a region ii initramfs-tools0.92bubuntu78 tools for generating an initramfs ii redboot-tools 0.7build1 Collection of utilities to manipul flash-kernel recommends no packages. Versions of packages flash-kernel suggests: pn uboot-envtools (no description available) ii uboot-mkimage 0.4build1 generate kernel image for U-Boot -- no debconf information -- The list of supported architectures seems pretty much alphabetical. So I put this one at the top. Hope that's OK. Index: flash-kernel === --- flash-kernel (revision 64675) +++ flash-kernel (working copy) @@ -85,6 +85,7 @@ if [ "x$1" = "x--supported" ]; then case "$machine" in + "ARM-Versatile Express CA9x4") exit 0 ;; "Buffalo Linkstation Pro/Live") exit 0 ;; "Buffalo/Revogear Kurobox Pro") exit 0 ;; "D-Link DNS-323") exit 0 ;; @@ -140,6 +141,48 @@ subarch=$(echo "$kfile" | sed -e 's/.*-//') case "$machine" in + "ARM-Versatile Express CA9x4") + check_mtd + kmtd=$(mtdblock "kernel") + if [ -z "$kmtd" ]; then + error "Cannot find mtd partition 'kernel'" + fi + check_dev_mtdblock "$kmtd" + kmtdsize=$(mtdsize "kernel") + check_size "kernel" $(($kfilesize + 8 + 64)) $kmtdsize + printf "Generating a u-boot compatible kernel image... " >&2 + 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 + printf "Erasing Kernel NOR space... " >&2 + dd if=/dev/zero of=$kmtd bs=$kmtdsize count=1 2>/dev/null + printf "Writing kernel to flash... " >&2 + cat $tmp.uboot > $kmtd || error "failed." + echo "done." >&2 + rm -f $tmp.uboot $tmp + + initrd_nor_size=25165824 + imtd=$(mtdblock "initrd") + if [ -z "$imtd" ]; then + error "Cannot find mtd partition for initrd" + fi + check_dev_mtdblock "$imtd" + check_size "initrd" $ifilesize $initrd_nor_size + printf "Generating u-boot compatible initrd image... " >&2 + tmp=$(tempfile) + cat $ifile >> $tmp + mkimage -A arm -O linux -T ramdisk -C none -a 0x8100 \ + -e 0x8100 -n "initramfs" -d $tmp $tmp.uboot \ + >&2 1>/dev/null + printf "Erasing initrd NOR space... " >&2 + dd if=/dev/zero of=$imtd bs=$initrd_nor_size count=1 2>/dev/null + printf "Writing initrd to flash... " >&2 + cat $tmp.uboot > $imtd || error "failed." + echo "done." >&2 + rm -f $tmp.uboot $tmp + ;; "Buffalo Linkstation Pro/Live" | "Buffalo/Revogear Kurobox Pro") check_subarch "orion5x" tmp="$(tempfile)" Index: README === --- README (revision 64675) +++ README (working copy) @@ -21,6 +21,7 @@ At the moment, the following systems are supported: + - ARM-Versatile Express CA9x4 - Buffalo Linkstation Live - Buffalo Linkstation Pro - Buffalo/Revogear Kurobox Pro
Bug#596787: installation-reports: grub legacy writes incorrect menu.lst when disks are RAIDed
Christian PERRIER wrote: Quoting Miles Fidelman (mfidel...@ntcorp.com): Package: installation-reports Severity: important Tags: d-i system has two mirrored disks, /dev/md0 is boot, /dev/md2 is root selecting grub-legacy, and specifying either /dev/hda or (hd0) for installation results in a menu.lst file with the line groot=(md0) and all of the boot sections starting with root (md0) at boot time, grub throws an error - it (corretly) doesn't recognize md0 as a proper construction editing menu.lst to read groot=(hd0,0) and running update-grub leads to a correct and functional menu.lst Which image did you use for this? How did you proceed to setupthis in the partitioning step. We need that information in order to try reproducing the problem I was using the alpha1 CD image, somewhat old at this point. Currently running an install with today's USB image, and it seems to have discovered the network card, loaded the firmware and is working properly. Would probably be hard to collect the info at this point. Might be better to close the report. -- 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/4c8fc692.2080...@ntcorp.com
Re: using isohybrid for usb bootable isos
Joey Hess writes: > Steve McIntyre wrote: > > That itself is a minor pain, but not enough to make me complain about > > a useful feature. The *more* difficult thing is trying to make > > iso-hybrid work with jigdo: we make the .iso and .jigdo files directly > > in the same invocation of genisoimage, so anything we do to > > post-process the .iso files won't show up in the .jigdo > > equivalents. :-( > > > > I've been trying to find time for ages to either: (a) add iso-hybrid > > support directly into genisoimage, or (b) port the jigdo code from > > genisoimage to xorriso, which is the long-term plan. xorriso already > > includes the needed iso-hybrid support, but it'll take quite a lot of > > work to add jigdo code there. > > I take it it's not an easy option to have jidgo just run isohybrid? Actually, jigdo-file(1) is not involved with the creation of *.jigdo and *.template files, as it is replaced by Steve's JTE code (run inside genisoimage) which eventually could be changed isohybrid-wise. I don't know how doable and sane would be that, to be honest. I agree that generating both representations (ISO and jigdo/templete) by reading the source data just once, does cut the read-IO about twice. > One problem with your long-term plan is that it would not allow adding > on the firmware partition prior to generating the jidgo, as xorriso > won't be doing that. > > (I do wonder if it's worth spending scarce time on jidgo.) Well, the jigdo representation efficiently upgrades (slightly) outdated iso- images, you have downloaded a week or month ago. Nothing beats that with regard to the impact on saving time and bandwidth at the user's side, especially image testers and early adopters. Thus, I'd rather see it as more efficient approach to have that whole post-processing work just done once on a central site, many to reuse efficiently. This is currently even doable via xorriso (iso-hybrid support included) generating these images, which can then be given to jigdo-file to complete their jigdo representation. Steve, this does not mean we have given up on porting JTE to xorriso. We are currently discussing that with Thomas as time permits, but identifying a proper design and eventually implement it takes its time. -- pub 4096R/0E4BD0AB -- 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/201009142133.29064.danc...@spnet.net
Bug#596787: installation-reports: grub legacy writes incorrect menu.lst when disks are RAIDed
Quoting Miles Fidelman (mfidel...@ntcorp.com): > Package: installation-reports > Severity: important > Tags: d-i > > system has two mirrored disks, /dev/md0 is boot, /dev/md2 is root > > selecting grub-legacy, and specifying either /dev/hda or (hd0) for > installation > results in a menu.lst file with the line > groot=(md0) and all of the boot sections starting with root (md0) > > at boot time, grub throws an error - it (corretly) doesn't recognize md0 as a > proper construction > > editing menu.lst to read > groot=(hd0,0) > and running update-grub > > leads to a correct and functional menu.lst Which image did you use for this? How did you proceed to setupthis in the partitioning step. We need that information in order to try reproducing the problem. signature.asc Description: Digital signature
Bug#596786: installation-reports: installer also couldn't find broadcom card
Quoting Miles Fidelman (mfidel...@ntcorp.com): > Package: installation-reports > Severity: important > Tags: d-i > > eth0 is intel board > eth1 is broadcom card > > installer 1st asks for firmware (e100/d102e_ucode.bin) - download from > debian.org per install instructions, put on usb stick, insert - seems to load > (takes several minutes) > > then, selecting eth1 leads to failure to obtain DHCP address > selecting eth0 works Which image did you use? Are there some information showing up in console 4? signature.asc Description: Digital signature
Processed: Re: Bug#596877: The last netinstall iso's don't install grub
Processing commands for cont...@bugs.debian.org: > reassign 596877 grub-installer Bug #596877 [debian-testing-i386-netinst.iso] The last netinstall iso's don't install grub Warning: Unknown package 'debian-testing-i386-netinst.iso' Bug reassigned from package 'debian-testing-i386-netinst.iso' to 'grub-installer'. > thanks Stopping processing here. Please contact me if you need assistance. -- 596877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596877 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.128448831818316.transcr...@bugs.debian.org
Bug#246498: Do we really need to say "hey, I'm rebooting" when user press Ctrl-Alt-Suppr inside D-I?
Quoting Scott Robinson (sc...@quadhome.com): > Excerpts from Christian PERRIER's message of Tue Sep 14 03:25:47 +1000 2010: > > [...] > > I agree that nothing shows up. But that nothing shows up for a > > fraction of second, then the system reboots > > [...] > > But it isn't a fraction of a second on a lot of machines. (old machines, > netbooks, embedded installs, etc.) Well, sure. However, I roughly guess that the delay happens not because something is being done before doing a "safe" rebootbut just because it takes time for the system to intercept and process the key combination. So, assuming we would want a nice display instead of "Sending HUP to terminate all running processes"there would still be a delay before that thing is triggerredwith the current actions still apparently continuing. Really, I don't exactly see the point and benefit unless you suggest something that would intercept Ctrl-Alt-Del and display a confirmation bow or something similar. The use case seems vague for me, indeed. signature.asc Description: Digital signature
hw-detect_1.80_i386.changes ACCEPTED into unstable
Accepted: archdetect_1.80_i386.udeb to main/h/hw-detect/archdetect_1.80_i386.udeb disk-detect_1.80_all.udeb to main/h/hw-detect/disk-detect_1.80_all.udeb driver-injection-disk-detect_1.80_all.udeb to main/h/hw-detect/driver-injection-disk-detect_1.80_all.udeb ethdetect_1.80_all.udeb to main/h/hw-detect/ethdetect_1.80_all.udeb hw-detect_1.80.dsc to main/h/hw-detect/hw-detect_1.80.dsc hw-detect_1.80.tar.gz to main/h/hw-detect/hw-detect_1.80.tar.gz hw-detect_1.80_i386.udeb to main/h/hw-detect/hw-detect_1.80_i386.udeb Override entries for your package: archdetect_1.80_i386.udeb - standard debian-installer disk-detect_1.80_all.udeb - optional debian-installer driver-injection-disk-detect_1.80_all.udeb - optional debian-installer ethdetect_1.80_all.udeb - optional debian-installer hw-detect_1.80.dsc - source debian-installer hw-detect_1.80_i386.udeb - standard debian-installer Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ovzb3-0002gj...@franck.debian.org
Processing of hw-detect_1.80_i386.changes
hw-detect_1.80_i386.changes uploaded successfully to localhost along with the files: hw-detect_1.80.dsc hw-detect_1.80.tar.gz hw-detect_1.80_i386.udeb ethdetect_1.80_all.udeb disk-detect_1.80_all.udeb driver-injection-disk-detect_1.80_all.udeb archdetect_1.80_i386.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ovzpy-xz...@franck.debian.org
Re: using isohybrid for usb bootable isos
Christian PERRIER wrote: > I would be OK to commit all this but we first need a confirmation that > someone will be handling the work on the installation guide side: > calling for translation updates, monitoring I-G builds and releasing > the new installation guide. > > CC'ing Felipe who, I think, is the best-suited person for this. I can stick the manual's changes in a branch or something. None of my changes require immediate documentation, as they only add an optional way to create a bootable USB stick. -- see shy jo signature.asc Description: Digital signature
Re: using isohybrid for usb bootable isos
Steve McIntyre wrote: > That itself is a minor pain, but not enough to make me complain about > a useful feature. The *more* difficult thing is trying to make > iso-hybrid work with jigdo: we make the .iso and .jigdo files directly > in the same invocation of genisoimage, so anything we do to > post-process the .iso files won't show up in the .jigdo > equivalents. :-( > > I've been trying to find time for ages to either: (a) add iso-hybrid > support directly into genisoimage, or (b) port the jigdo code from > genisoimage to xorriso, which is the long-term plan. xorriso already > includes the needed iso-hybrid support, but it'll take quite a lot of > work to add jigdo code there. I take it it's not an easy option to have jidgo just run isohybrid? One problem with your long-term plan is that it would not allow adding on the firmware partition prior to generating the jidgo, as xorriso won't be doing that. (I do wonder if it's worth spending scarce time on jidgo.) -- see shy jo signature.asc Description: Digital signature
Re: using isohybrid for usb bootable isos
Hello, On Tue, Sep 14, 2010 at 8:24 AM, Steve McIntyre wrote: > On Mon, Sep 13, 2010 at 10:44:35PM -0400, Joey Hess wrote: >>Joey Hess wrote: >>This would add 6 to 7 mb to iso images it's used on, I don't know how Steve >>feels about that. :) > > That itself is a minor pain, but not enough to make me complain about > a useful feature. The *more* difficult thing is trying to make > iso-hybrid work with jigdo: we make the .iso and .jigdo files directly > in the same invocation of genisoimage, so anything we do to > post-process the .iso files won't show up in the .jigdo > equivalents. :-( The iso-hybrid is indeed a quite nice way to avoid a lot of hassle for users regarting the usb image usage; having you comments in mind I believe we could add it for netboot.iso images in d-i for now and try to make it default for Wheeze since it looks like debian-cd tools does demand a lot of work to it fit well on this. What people think? -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- 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/aanlktimvh07jzymlcappu5d5+kogf2xo6ccwxpeys...@mail.gmail.com
libdebian-installer_0.76_i386.changes ACCEPTED into unstable
Accepted: libdebian-installer-extra4-udeb_0.76_i386.udeb to main/libd/libdebian-installer/libdebian-installer-extra4-udeb_0.76_i386.udeb libdebian-installer-extra4_0.76_i386.deb to main/libd/libdebian-installer/libdebian-installer-extra4_0.76_i386.deb libdebian-installer4-dev_0.76_i386.deb to main/libd/libdebian-installer/libdebian-installer4-dev_0.76_i386.deb libdebian-installer4-udeb_0.76_i386.udeb to main/libd/libdebian-installer/libdebian-installer4-udeb_0.76_i386.udeb libdebian-installer4_0.76_i386.deb to main/libd/libdebian-installer/libdebian-installer4_0.76_i386.deb libdebian-installer_0.76.dsc to main/libd/libdebian-installer/libdebian-installer_0.76.dsc libdebian-installer_0.76.tar.gz to main/libd/libdebian-installer/libdebian-installer_0.76.tar.gz Override entries for your package: libdebian-installer-extra4-udeb_0.76_i386.udeb - optional debian-installer libdebian-installer-extra4_0.76_i386.deb - optional libs libdebian-installer4-dev_0.76_i386.deb - optional libdevel libdebian-installer4-udeb_0.76_i386.udeb - optional debian-installer libdebian-installer4_0.76_i386.deb - optional libs libdebian-installer_0.76.dsc - source libs Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ovwop-0008og...@franck.debian.org
Processing of libdebian-installer_0.76_i386.changes
libdebian-installer_0.76_i386.changes uploaded successfully to localhost along with the files: libdebian-installer_0.76.dsc libdebian-installer_0.76.tar.gz libdebian-installer4_0.76_i386.deb libdebian-installer4-dev_0.76_i386.deb libdebian-installer4-udeb_0.76_i386.udeb libdebian-installer-extra4_0.76_i386.deb libdebian-installer-extra4-udeb_0.76_i386.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ovwkc-0007oi...@franck.debian.org
Bug#554196: marked as done ([console-setup] Generic German keyboard cannot be setup to use AltGr key)
Your message dated Tue, 14 Sep 2010 14:41:36 +0300 with message-id <20100914114135.gd5...@debian.lan> and subject line Re: Bug#554196: [console-setup] Generic German keyboard cannot be setup to use AltGr key has caused the Debian Bug report #554196, regarding [console-setup] Generic German keyboard cannot be setup to use AltGr key to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 554196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: console-setup Version: 1.45 Severity: important Tags: l10n --- Please enter the report below this line. --- Whatever settings I try - I cannot enter important characters like @ (AltGr + Q) ~ (AltGr + +) | (AltGr + <) or even: {[]}\ this is a problem within TTY or GTK applications. In KDE (4) apps the AltGr key works as desired. Maybe, these informations can help: - when I type AltGr + Q twice, I get a list of known hosts (as if I type @ and 2xTAB) - same problem is there when I use the (clickable) virtual keyboard of KDE. - "less -" reports that instead of plain "@", an ESC is sent before. This means the ESC is triggered additionally before the desired @ character is sent. Did I mention that I own a straight 105-keyboard, just QWERTZ. --- System information. --- Architecture: i386 Kernel: Linux 2.6.30-5-686 Debian Release: squeeze/sid 500 unstablewww.debian-multimedia.org 500 unstableftp.us.debian.org 500 unstableftp.spline.de --- Package information. --- Depends (Version) | Installed ===-+-=== debconf (>= 0.5) | 1.5.28 OR debconf-2.0 | console-terminus (>= 4.26) | 4.28-1 xkb-data (>= 0.9) | 1.6-1 Recommends (Version) | Installed =-+- kbd (>= 0.99-12) | 1.15-4 OR console-tools (>= 1:0.2.3-16) | Suggests (Version) | Installed ===-+-=== lsb-base (>= 3.0-6) | 3.2-23 locales | 2.10.1-5 --- End Message --- --- Begin Message --- Hello, On Tue, Nov 3, 2009 at 07:37:40PM you reported the following problem: > Package: console-setup > Version: 1.45 > Severity: important > Tags: l10n > > Whatever settings I try - I cannot enter important characters like > @ (AltGr + Q) > ~ (AltGr + +) > | (AltGr + <) > or even: {[]}\ > > this is a problem within TTY or GTK applications. In KDE (4) apps the > AltGr key works as desired. I think the bug you reported was caused either by some temporary problem in an old version of console-setup, or by misconfiguration of some part of your system that is not related to console-setup. Because of this I am closing this bug now. If you think that I am not correct please feel free to say so and please provide the information I requested in my previous email messages (please check also the version of console-setup you use). You can find the full log of this bug report here: http://bugs.debian.org/554196 Anton Zinoviev --- End Message ---
Re: using isohybrid for usb bootable isos
On Mon, Sep 13, 2010 at 10:44:35PM -0400, Joey Hess wrote: >Joey Hess wrote: >> So ideally, debian-cd would add a small second partition to the iso file's >> partition table, and tack on a FAT filesystem. This could probably be done >> by running fdisk on the iso file after isohybrid. > >I've attached a patch with a script, which I am checking into d-i for now, >that does that. > >This would add 6 to 7 mb to iso images it's used on, I don't know how Steve >feels about that. :) Hey Joey, That itself is a minor pain, but not enough to make me complain about a useful feature. The *more* difficult thing is trying to make iso-hybrid work with jigdo: we make the .iso and .jigdo files directly in the same invocation of genisoimage, so anything we do to post-process the .iso files won't show up in the .jigdo equivalents. :-( I've been trying to find time for ages to either: (a) add iso-hybrid support directly into genisoimage, or (b) port the jigdo code from genisoimage to xorriso, which is the long-term plan. xorriso already includes the needed iso-hybrid support, but it'll take quite a lot of work to add jigdo code there. -- Steve McIntyre, Cambridge, UK.st...@einval.com "When C++ is your hammer, everything looks like a thumb." -- Steven M. Haflich -- 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/20100914112456.ga18...@einval.com
Bug#581756: keyboard-configuration: XKBOPTIONS does not properly propagate to xserver-xorg
On Tue, Sep 14, 2010 at 12:18:44PM +0200, Julien Cristau wrote: > > > > Do you think it will be useful if keyboard-configuration provides a > > /etc/foo.d directory where the interested packages (console-setup, X) > > can install scripts to reconfigure the keyboard? > > > It seems overkill to me, fwiw (I think it's reasonable to say that > changes to /etc/default/keyboard take effect at the next boot), but if > you want to provide this then I have no objection. Personally I don't have an opinion about this. I guess I am going to wait for some more bug reports requesting 'dpkg-reconfigure keyboard-configuration' to actually reconfigure the keyboard. :) Anton Zinoviev -- 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/20100914102459.ga5...@debian.lan
Bug#594817: marked as done (console-setup should configure the width&height of the console)
Your message dated Tue, 14 Sep 2010 11:02:18 + with message-id and subject line Bug#594817: fixed in console-setup 1.56 has caused the Debian Bug report #594817, regarding console-setup should configure the width&height of the console to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 594817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: console-setup Version: 1.55 Severity: normal Hello, Squeeze brings an accessibility regression: with some setups (like kms), the framebuffer console is enabled by default, which thus brings a high-resolution video mode, thus a screen larger than 80 columns. This is a problem for braille users: braille displays are quite often 40 cells wide, thus exactly half the screen width. Having to cope with some more text is a pain. There are also other braille display sizes, like 64, 88, etc. Also, things like 50 lines is not necessarily convenient, depending on users. A nice way to fix the regression and actually provide better support for various display sizes would be to have console-setup tune the screen size according to user's decision, thanks to a combination of proper font size and call to stty rows/cols. The way I see this is to add SCREEN_WIDTH and SCREEN_HEIGHT to /etc/default/console-setup (unset by default): - if only FONTSIZE is set, just load the font and be fine with it. - if FONTSIZE is set as well as SCREEN_WIDTH/HEIGHT, load the specified font, and call stty cols $SCREEN_WIDTH rows $SCREEN_HEIGHT to fix the screen size. - if FONTSIZE is not set but SCREEN_WIDTH/HEIGHT is, look for a font size that is almost big enough to get only the desired width and height. Calling stty cols $SCREEN_WIDTH rows $SCREEN_HEIGHT then helps to get rid of the few extra columns and rows. We could even imagine to rasterize a vector font on the fly for very big sizes. Of course, since Squeeze is frozen, we should probably not care about the 3rd case for now. I however believe that handling the second case would permit to fix the regression nicely and easily enough without bringing any other potential regressions. What do you think? Samuel -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages console-setup depends on: ii console-terminus 4.30-2 Fixed-width fonts for fast reading ii debconf [debconf-2.0] 1.5.35 Debian configuration management sy ii keyboard-configuration1.55 system-wide keyboard preferences ii xkb-data 1.8-1 X Keyboard Extension (XKB) configu Versions of packages console-setup recommends: ii kbd 1.15.2-1 Linux console font and keytable ut Versions of packages console-setup suggests: ii locales 2.11.2-2 Embedded GNU C Library: National L ii locales-all [locales] 2.11.2-2 Embedded GNU C Library: Precompile ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip -- debconf information: * console-setup/variant: France * console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages console-setup/unsupported_options: true console-setup/ctrl_alt_bksp: true console-setup/modelcode: geniuskb19e console-setup/use_system_font: console-setup/fontsize: 8 * console-setup/unsupported_layout: true console-setup/layoutcode: fr,brai debian-installer/console-setup/title: console-setup/codesetcode: Lat15 console-setup/altgr: The default for the keyboard layout * console-setup/ttys: /dev/tty[1-6] * console-setup/codeset: # Latin1 and Latin5 - western Europe and Turkic languages console-setup/toggle: Alt+Caps Lock * console-setup/fontface: VGA * console-setup/fontsize-text: 8 console-setup/compose: Right Logo key debian-installer/console-setup-udeb/title: console-setup/other: console-setup/store_defaults_in_debconf_db: true console-setup/switch: No temporary switch * console-setup/unsupported_config_layout: true * console-setup/charmap: UTF-8 * console-setup/fontface47: VGA * console-setup/fontsize-text47: 8 * console-setup/optionscode: grp:alt_caps_toggle,compose:rwin,nbsp:level3n,terminate:ctrl_alt_bksp console-setup/unsupported_config_options: true * console-setup/charmap
Bug#596547: marked as done (keyboard-configuration: upgrade from xorg.conf turns layout names to lowercase)
Your message dated Tue, 14 Sep 2010 11:02:18 + with message-id and subject line Bug#596547: fixed in console-setup 1.56 has caused the Debian Bug report #596547, regarding keyboard-configuration: upgrade from xorg.conf turns layout names to lowercase to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 596547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xkb-data Version: 1.8-1 Severity: important After updating my desktop machine to squeeze my keyboard no longer works (ok 3 keys on my keyboard among them "u" work). This happens even if I start with an empty/no xorg.conf. Starting X manually I noticed this on stderr: The XKEYBOARD keymap compiler (xkbcomp) reports: > Error:Can't find file "en_us" for symbols include > Exiting > Abandoning symbols file "default" Errors from xkbcomp are not fatal to the X server (EE) Unable to open evdev device "/dev/input/event4". (EE) PreInit returned NULL for "Microsoft Natural® Ergonomic Keyboard 4000" So I did a strace and creating this symlink fixed it for me # cd /usr/share/X11/xkb/symbols # ln -s us en_us Is this a problem/misconfiguration on my side and intended or should en_us be shipped indeed? -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35.4 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- no debconf information --- End Message --- --- Begin Message --- Source: console-setup Source-Version: 1.56 We believe that the bug you reported is fixed in the latest version of console-setup, which is due to be installed in the Debian FTP archive: bdf2psf_1.56_all.deb to main/c/console-setup/bdf2psf_1.56_all.deb console-setup-amiga-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-amiga-ekmap_1.56_all.udeb console-setup-ataritt-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-ataritt-ekmap_1.56_all.udeb console-setup-fonts-udeb_1.56_all.udeb to main/c/console-setup/console-setup-fonts-udeb_1.56_all.udeb console-setup-macintoshold-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-macintoshold-ekmap_1.56_all.udeb console-setup-mini_1.56_all.deb to main/c/console-setup/console-setup-mini_1.56_all.deb console-setup-pc-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-pc-ekmap_1.56_all.udeb console-setup-sun4-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-sun4-ekmap_1.56_all.udeb console-setup-sun5-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-sun5-ekmap_1.56_all.udeb console-setup-udeb_1.56_all.udeb to main/c/console-setup/console-setup-udeb_1.56_all.udeb console-setup_1.56.dsc to main/c/console-setup/console-setup_1.56.dsc console-setup_1.56.tar.gz to main/c/console-setup/console-setup_1.56.tar.gz console-setup_1.56_all.deb to main/c/console-setup/console-setup_1.56_all.deb keyboard-configuration_1.56_all.deb to main/c/console-setup/keyboard-configuration_1.56_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 596...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Zinoviev (supplier of updated console-setup package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 14 Sep 2010 13:06:38 +0300 Source: console-setup Binary: keyboard-configuration console-setup console-setup-mini bdf2psf console-setup-udeb console-setup-amiga-ekmap console-setup-ataritt-ekmap console-setup-macintoshold-ekmap console-setup-pc-ekmap console-setup-sun4-ekmap console-setup-sun5-ekmap console-setup-fonts-udeb Architecture: source all Version: 1.56 Distribution: unstable Urgency: low Maintainer: Debian Install System Team Changed-By: Anton Zinoviev Description: bdf2psf- font converter to generate console fonts from BDF source fonts console-setup - console font and keymap setup program console-setup-amiga-ekmap - encoded keyboard layouts for Amiga keyboards (udeb) console-setup-ataritt-ekmap - encoded keyboard layouts for Ata
Bug#575806: marked as done (console-setup-mini does not change fonts: had to install console-setup instead)
Your message dated Tue, 14 Sep 2010 11:02:18 + with message-id and subject line Bug#575806: fixed in console-setup 1.56 has caused the Debian Bug report #575806, regarding console-setup-mini does not change fonts: had to install console-setup instead to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 575806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: console-setup-mini Version: 1.51 Severity: important With /etc/default/console-setup containing FONTFACE="Fixed" FONTSIZE="14" for example, setupcon does not change the font. Similarly dpkg-reconfigure console-setup-mini does nothing. Installing console-setup instead of the mini version, all these things work. So the "mini" version is broken? ael --- -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.33 (PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages console-setup-mini depends on: ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy ii keyboard-configuration1.51 system-wide keyboard preferences Versions of packages console-setup-mini recommends: ii kbd 1.15.1-2 Linux console font and keytable ut Versions of packages console-setup-mini suggests: ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip --- End Message --- --- Begin Message --- Source: console-setup Source-Version: 1.56 We believe that the bug you reported is fixed in the latest version of console-setup, which is due to be installed in the Debian FTP archive: bdf2psf_1.56_all.deb to main/c/console-setup/bdf2psf_1.56_all.deb console-setup-amiga-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-amiga-ekmap_1.56_all.udeb console-setup-ataritt-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-ataritt-ekmap_1.56_all.udeb console-setup-fonts-udeb_1.56_all.udeb to main/c/console-setup/console-setup-fonts-udeb_1.56_all.udeb console-setup-macintoshold-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-macintoshold-ekmap_1.56_all.udeb console-setup-mini_1.56_all.deb to main/c/console-setup/console-setup-mini_1.56_all.deb console-setup-pc-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-pc-ekmap_1.56_all.udeb console-setup-sun4-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-sun4-ekmap_1.56_all.udeb console-setup-sun5-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-sun5-ekmap_1.56_all.udeb console-setup-udeb_1.56_all.udeb to main/c/console-setup/console-setup-udeb_1.56_all.udeb console-setup_1.56.dsc to main/c/console-setup/console-setup_1.56.dsc console-setup_1.56.tar.gz to main/c/console-setup/console-setup_1.56.tar.gz console-setup_1.56_all.deb to main/c/console-setup/console-setup_1.56_all.deb keyboard-configuration_1.56_all.deb to main/c/console-setup/keyboard-configuration_1.56_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 575...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Zinoviev (supplier of updated console-setup package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 14 Sep 2010 13:06:38 +0300 Source: console-setup Binary: keyboard-configuration console-setup console-setup-mini bdf2psf console-setup-udeb console-setup-amiga-ekmap console-setup-ataritt-ekmap console-setup-macintoshold-ekmap console-setup-pc-ekmap console-setup-sun4-ekmap console-setup-sun5-ekmap console-setup-fonts-udeb Architecture: source all Version: 1.56 Distribution: unstable Urgency: low Maintainer: Debian Install System Team Changed-By: Anton Zinoviev Description: bdf2psf- font converter to generate console fonts from BDF source fonts console-setup - console font and keymap setup program console-setup-amiga-ekmap - encoded keyboard layouts for Amiga keyboards (udeb) console-setup-ataritt-ekmap - encoded keyboard l
console-setup_1.56_amd64.changes ACCEPTED into unstable
Accepted: bdf2psf_1.56_all.deb to main/c/console-setup/bdf2psf_1.56_all.deb console-setup-amiga-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-amiga-ekmap_1.56_all.udeb console-setup-ataritt-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-ataritt-ekmap_1.56_all.udeb console-setup-fonts-udeb_1.56_all.udeb to main/c/console-setup/console-setup-fonts-udeb_1.56_all.udeb console-setup-macintoshold-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-macintoshold-ekmap_1.56_all.udeb console-setup-mini_1.56_all.deb to main/c/console-setup/console-setup-mini_1.56_all.deb console-setup-pc-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-pc-ekmap_1.56_all.udeb console-setup-sun4-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-sun4-ekmap_1.56_all.udeb console-setup-sun5-ekmap_1.56_all.udeb to main/c/console-setup/console-setup-sun5-ekmap_1.56_all.udeb console-setup-udeb_1.56_all.udeb to main/c/console-setup/console-setup-udeb_1.56_all.udeb console-setup_1.56.dsc to main/c/console-setup/console-setup_1.56.dsc console-setup_1.56.tar.gz to main/c/console-setup/console-setup_1.56.tar.gz console-setup_1.56_all.deb to main/c/console-setup/console-setup_1.56_all.deb keyboard-configuration_1.56_all.deb to main/c/console-setup/keyboard-configuration_1.56_all.deb Override entries for your package: bdf2psf_1.56_all.deb - optional utils console-setup-amiga-ekmap_1.56_all.udeb - extra debian-installer console-setup-ataritt-ekmap_1.56_all.udeb - extra debian-installer console-setup-fonts-udeb_1.56_all.udeb - extra debian-installer console-setup-macintoshold-ekmap_1.56_all.udeb - extra debian-installer console-setup-mini_1.56_all.deb - extra utils console-setup-pc-ekmap_1.56_all.udeb - extra debian-installer console-setup-sun4-ekmap_1.56_all.udeb - extra debian-installer console-setup-sun5-ekmap_1.56_all.udeb - extra debian-installer console-setup-udeb_1.56_all.udeb - extra debian-installer console-setup_1.56.dsc - source utils console-setup_1.56_all.deb - optional utils keyboard-configuration_1.56_all.deb - optional utils Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 575806 594817 596547 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ovthg-0005g5...@franck.debian.org
Bug#246498: Do we really need to say "hey, I'm rebooting" when user press Ctrl-Alt-Suppr inside D-I?
Excerpts from Christian PERRIER's message of Tue Sep 14 03:25:47 +1000 2010: > [...] > I agree that nothing shows up. But that nothing shows up for a > fraction of second, then the system reboots > [...] But it isn't a fraction of a second on a lot of machines. (old machines, netbooks, embedded installs, etc.) -- 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/1284461485-sup-...@elise
Processing of console-setup_1.56_amd64.changes
console-setup_1.56_amd64.changes uploaded successfully to localhost along with the files: console-setup_1.56.dsc console-setup_1.56.tar.gz keyboard-configuration_1.56_all.deb console-setup_1.56_all.deb console-setup-mini_1.56_all.deb bdf2psf_1.56_all.deb console-setup-udeb_1.56_all.udeb console-setup-amiga-ekmap_1.56_all.udeb console-setup-ataritt-ekmap_1.56_all.udeb console-setup-macintoshold-ekmap_1.56_all.udeb console-setup-pc-ekmap_1.56_all.udeb console-setup-sun4-ekmap_1.56_all.udeb console-setup-sun5-ekmap_1.56_all.udeb console-setup-fonts-udeb_1.56_all.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ovtee-0005er...@franck.debian.org
Bug#581756: keyboard-configuration: XKBOPTIONS does not properly propagate to xserver-xorg
On Mon, Sep 13, 2010 at 23:16:35 +0300, Anton Zinoviev wrote: > On Sat, May 15, 2010 at 06:15:06PM +0200, Julien Cristau wrote: > > > > Triggering udev from keyboard-configuration doesn't really make sense > > (it's a layering violation; keyboard-configuration shouldn't need to > > know what the users for this configuration file are, whether X is > > installed, etc) > > Do you think it will be useful if keyboard-configuration provides a > /etc/foo.d directory where the interested packages (console-setup, X) > can install scripts to reconfigure the keyboard? > It seems overkill to me, fwiw (I think it's reasonable to say that changes to /etc/default/keyboard take effect at the next boot), but if you want to provide this then I have no objection. Cheers, Julien signature.asc Description: Digital signature
Re: Status of some daily D-I builds
Christian PERRIER (14/09/2010): > What I would also like to have is a way to easily *monitor* these > daily builds. I had that in mind at some point, but I'm currently busy with some upstream work. Feel free to poke me in some days if you didn't find a volunteer at that point. Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#596762: installation-reports: installer failed to add winXP to grub2
Processing commands for cont...@bugs.debian.org: > tags 596762 moreinfo Bug #596762 [installation-reports] installation-reports: installer failed to add winXP to grub2 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 596762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596762 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.12844523313450.transcr...@bugs.debian.org
Bug#596762: installation-reports: installer failed to add winXP to grub2
tags 596762 moreinfo thanks Quoting spamfang (spamfang1...@yahoo.de): > Package: installation-reports > Severity: important > Tags: d-i > > > > -- Package-specific info: > > Boot method: cd > Image version: > http://cdimage.debian.org/cdimage/squeeze_di_alpha1/i386/iso-cd/debian-testing-i386-netinst.iso Could you use a daily build of the installer? At this step of the squeeze development, we no longer recommend using alpha1 releases. GRUB issues, particularly, should be tested with latest releases. You can find daily builds from http://www.debian.org/devel/debian-installer. Please preferrably choose the *netboot* image (not netinst). Despite its name, it is not reserved for people who use network boot servers. It is indeed just an "as minimal as possible" image that downloads components off the network as soon as the network is up and running in D-I. signature.asc Description: Digital signature
Re: using isohybrid for usb bootable isos
Quoting Joey Hess (jo...@debian.org): > I've done some investigation of using isohybrid on an iso image (d-i > alpha1 i386 netinst) to allow it to be booted from USB stick. Basically, > postprocess the image with isohybrid, and write it direct to the usb > stick. On the single machine I tried it on, that booted ok without any > tweaking of isohybrid options. Impressive work (as usual...). I would be OK to commit all this but we first need a confirmation that someone will be handling the work on the installation guide side: calling for translation updates, monitoring I-G builds and releasing the new installation guide. CC'ing Felipe who, I think, is the best-suited person for this. signature.asc Description: Digital signature
Bug#596791: guide doesn't discuss dynamic disks or Windows LDM
Package: installation-guide Windows LDM (Logical Disk Manager) and `dynamic disks' are a reality for anyone installing a dual boot machine, especially if Windows Vista or Windows 7 is already on the machine. The guide may need to be updated to touch on various issues: - choice of boot loader (grub doesn't support LDM yet) - GPT disk labels created by some Windows installs - Should LDM dynamic disks be used as physical volumes (PV) for LVM2? - Can the LDM part of the disk be safely shrunk to create space for a real partition for Linux or LVM2? It would be good to discuss both practical constraints and installation strategies, and provide a working example for the typical scenario of a machine with an existing all-of-disk LDM Windows 7 install. This issue is related: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569133 -- 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/4c8f2284.2050...@pocock.com.au