Processing of libdebian-installer_0.91_mipsel.changes
libdebian-installer_0.91_mipsel.changes uploaded successfully to localhost along with the files: libdebian-installer_0.91.dsc libdebian-installer_0.91.tar.gz libdebian-installer4_0.91_mipsel.deb libdebian-installer4-dev_0.91_mipsel.deb libdebian-installer4-udeb_0.91_mipsel.udeb libdebian-installer-extra4_0.91_mipsel.deb libdebian-installer-extra4-udeb_0.91_mipsel.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/e1vwrwn-0004yh...@franck.debian.org
libdebian-installer_0.91_mipsel.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 28 Dec 2013 09:50:51 +0100 Source: libdebian-installer Binary: libdebian-installer4 libdebian-installer4-dev libdebian-installer4-udeb libdebian-installer-extra4 libdebian-installer-extra4-udeb Architecture: source mipsel Version: 0.91 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Aurelien Jarno aure...@debian.org Description: libdebian-installer-extra4 - Library of some extra debian-installer functions libdebian-installer-extra4-udeb - Library of some extra debian-installer functions (udeb) libdebian-installer4 - Library of common debian-installer functions libdebian-installer4-dev - Library of common debian-installer functions libdebian-installer4-udeb - Library of common debian-installer functions (udeb) Changes: libdebian-installer (0.91) unstable; urgency=medium . * mips, mipsel: rewrite subarch-mips-linux.c: - Use a regex system instead of a two level lookup to provide more flexibility. - Use subarch-mips-linux.c for mipsel, as more and more systems are bi-endian. - Remove non-supported platforms. - Add support for Cavium Octeon platforms. - Detect more Loongson 2E and 2F machines. Checksums-Sha1: c8f7d0c1d810f244267b9af293be35859908eb78 1465 libdebian-installer_0.91.dsc 4ba9f564a81798bd69f23addf1a07fa689a56853 74692 libdebian-installer_0.91.tar.gz 6ae8286019def3968849225e117bd3a131dcbc98 27612 libdebian-installer4_0.91_mipsel.deb 46d9a90ad6df0939157c8a134e46a7188a5365e1 129722 libdebian-installer4-dev_0.91_mipsel.deb b80af0180f517483c2ee75639c0ad9dfe7fcb108 16458 libdebian-installer4-udeb_0.91_mipsel.udeb 466e33d910884ae1508bb3b911ac871c8940b16f 14542 libdebian-installer-extra4_0.91_mipsel.deb 2c912c17721b7aa68789209aeca2fa17c488f8a6 3466 libdebian-installer-extra4-udeb_0.91_mipsel.udeb Checksums-Sha256: 3019ed00f9844fb8e391861a6db725198569d5b4b7a13f6c2ceaadd9f6316ad5 1465 libdebian-installer_0.91.dsc 03c3980471ec786171187ff5ea508382c63c6996ccf832864f3e6b8540d036d8 74692 libdebian-installer_0.91.tar.gz 49486a745be9af44cfb258b9f43d075350524c9614467940973cbfb64f491cef 27612 libdebian-installer4_0.91_mipsel.deb 8ada27f1eae5b30538d8ce7357d8e18aecde75f1f7153f32330a47a258dadac1 129722 libdebian-installer4-dev_0.91_mipsel.deb fd753f6fa658b1da0b537a69bec1d465d4773c18bc32a5e36d59105bdcbe31ec 16458 libdebian-installer4-udeb_0.91_mipsel.udeb f36ecb8ee69323c6174173f5ad667500a4a5ff94287499c551d1de61238b4fbd 14542 libdebian-installer-extra4_0.91_mipsel.deb e6b389d1c3a935d054874f4291d65fe35046d758dce951a9fac78c3ba734feb2 3466 libdebian-installer-extra4-udeb_0.91_mipsel.udeb Files: dff364fab275ecb652808752d47d0411 1465 libs optional libdebian-installer_0.91.dsc 762e301403e70b4127e741cefa914fec 74692 libs optional libdebian-installer_0.91.tar.gz 3ae3e3e44252a9bb2cb63b18a1c715ce 27612 libs optional libdebian-installer4_0.91_mipsel.deb 2bc8e92b4b8951a422e573835ef53d45 129722 libdevel optional libdebian-installer4-dev_0.91_mipsel.deb 1a94f7b804dc5e6dbc9cec8dccfccc9c 16458 debian-installer optional libdebian-installer4-udeb_0.91_mipsel.udeb 766183775357356ae9cfe88c65cdf709 14542 libs optional libdebian-installer-extra4_0.91_mipsel.deb 6b9181d815700d575490e4895f89ede4 3466 debian-installer optional libdebian-installer-extra4-udeb_0.91_mipsel.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iD8DBQFSvqqQw3ao2vG823MRAt+WAKCEYvqhHwuVIhLTbtrOVso50ut6+wCfWFP8 +x0dGx+Tr1+TVqsoslYdsn4= =ZpFK -END PGP SIGNATURE- Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1vwrhb-0008g0...@franck.debian.org
Bug#724869: base: Deadkeys do not work in Xorg French canadian keyboard
On Sat, Dec 21, 2013 at 09:05:28PM -0500, James Brookes wrote: But there is a file named /etc/default/keyboard, here is the content: # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL=pc105 XKBLAYOUT=ca XKBVARIANT= XKBOPTIONS= BACKSPACE=guess Yes, this file is correct so the problem is not related to console-setup/keyboard-configuration in any way. I have no idea what has caused this bug so I don't know where should I reassing it. Unfortunately this means unless somebody else reassigns it this bug is going to be totally ignored... 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/20131228154427.ga1...@logic.fmi.uni-sofia.bg
Bug#733337: installation-report: Jessie testing set up on FSC Futro S 500 thinclient
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.55 Severity: wishlist Dear Maintainer, *** Please consider answering these questions, where appropriate *** * 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: USB-key Image version: http://gemmei.acc.umu.se/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso, 2013-12-23 Date: 2013-12-17, about 12.00 h to 15.00 h Machine: FSC Futro S 500 Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on /dev/sda1 xfs 13660160 4954352 8705808 37% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 192740 664192076 1% /run tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 780120 140779980 1% /run/shm none tmpfs4 0 4 0% /sys/fs/cgroup 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] Clock/timezone setup: [o] User/password setup:[o] Detect hard drives: [o] Partition hard drives: [o] Install base system:[o] Install tasks: [o] Install boot loader:[o] Overall install:[o] Comments/Problems: My secondary surfbox was upgraded from Wheezy/stable to Jessie/testing by reinstalling. I was using the backported 3.11 kernel already, now the whole system is 'testing', with lots of software-upgrades coming in. This line is required in /etc/default/grub: . .. GRUB_CMDLINE_LINUX_DEFAULT=quiet video=LVDS-1:d .. . in order to get proper video-output, this is the same as with FSC Futro S450, I was using before: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721310 The box is with an 'AMD Athlon 64 x2 L310' CPU now, that runs at a fixed frequency of 1,2 GHz, which seems to be a good trade off between energy-consumption and performance. Also the normal stock-kernel is working on it, there is no need to build your own, or to mess with ACPI-tables. When running the 'testing'-branch of Debian on it in my opinion it is recommended to have a 600x speed CF-card at least, because else software-updates are blocking the machine for too long while being installed, I am going to get one at least. Also two GB of RAM are better than one, especially when one likes browsing the web with many tabs open. At installation-time I tried the ZFS-filesystem, which is not workable yet in partman. There were complaints, that there was an XFS filesystem already on the CF-disk, when I zeroed the beginning of the disk in rescue-mode prior to partitioning it did not work either. The BTRFS-filesystem was not workable either, this means not at installation-time, but it is OK to add an lzo-compressed BTRFS-filesystem as /home/ partition for example after the main system was set up. Adding the /home/-partition, that was in use before actually worked fine, even opening files and folders with a single click in Nautilus/file-mananger was reenabled by the operation, which I failed to enable otherwise. - -- 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=8 (jessie) - installer build 20131223-00:14 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux s5 3.12-1-amd64 #1 SMP Debian 3.12.6-1 (2013-12-21) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD/ATI] RS690 Host Bridge [1002:7910] lspci -knn: Subsystem: Fujitsu Technology Solutions Device [1734:111d] lspci -knn: 00:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RS690 PCI to PCI Bridge (Internal gfx) [1002:7912] lspci -knn: 00:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] 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]: Advanced Micro Devices, Inc. [AMD/ATI] RS690 PCI to PCI Bridge (PCI Express Port 3) [1002:7917] lspci -knn: Kernel driver in use: pcieport lspci - -knn: 00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB600 USB
Q: How to rebuild d-i or initrd?
I made a replacement for rootskel-gtk, using the previous version rootskel-gtk_1.27_amd64.udeb as the source, with a higher version number. I've changed the theme and the logo. I've been told that the way to have the d-i use this new version is to rebuild d-i (preferably) or the initrd (at least). My question is, how do I rebuild the d-i and then how do I incorporate the new d-i in my build? Cheers
Bug#732039: installation-reports: success on Lenovo Thinkpad X201 using Jessie current ISO copies to USB stick
Hi Buck, On 13.12.2013 00:29, Buck Huppmann wrote: After failing to install using the latest image, because the md5sum.txt file had a bad md5sum for one of the installation packages (e2fsprogs*udeb*), This is usually due to an error while copying to the USB stick. i downloaded the image from earlier in the day and it worked just fine, with manual partition- ing, creating an LVM, ext4 filesystems, etc., clobbering an NTFS partition and leaving the rescue partition alone Great. Suspend to disk works fine, wireless works fine after installing the appropriate firmware non-free package. (I installed using the wired Ethernet; wireless wasn't configured by the installer, and so it didn't go looking for the firmware tarball i unpacked into a /firmware directory on a VFAT filesystem i appended to the USB stick) This is a known problem, see bug #725714 [1]. Comments/Problems: Reboot failed, as i'd tried to install grub into the /boot partition so i could boot into the recovery partition, but couldn't figure out how to do that, so i input /dev/sda which seemed to work, but i got Operating system missing or some such DOS/Windows MBR boot-failure message, so i rebooted the USB stick in rescue mode, started up a shell using the newly installed root filesystem and mounted /usr and /boot, and ran grub-install, which refused to install in /dev/sda1, so i let it overwrite the /dev/sda Grub2 should not be installed into a partition, but rather on a hard disk. If you really need it, you could try the --force option. I think this bug can be closed, because the remaining problem is discussed in [1]. Do you agree? Best regards, Andreas 1: http://bugs.debian.org/725714 -- 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/52bf4e08.7000...@googlemail.com
Bug#733454: installation-reports: Install freezes after install selection from first menu
Package: installation-reports Severity: important -- Package-specific info: Boot method: CD Image version: any form Release 7 Date: Date and time of the install Machine: Asus m2v890 Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] 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: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. The Install menu comes on screen. The install selection is done The screen get dark No change for ever... If I give 3 return hits some activities happens on the hard disk but no signe on screen. I have tested RLs6 amd64 all runs OK. The video drive after Xorg installation is openchrome To my own feeling it's the video init that runs wrong(even in text Mode) -- 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 20110106+squeeze4+b4 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux phil 2.6.32-5-amd64 #1 SMP Fri Feb 15 15:39:52 UTC 2013 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. K8M890CE Host Bridge [1106:0336] lspci -knn: Subsystem: VIA Technologies, Inc. K8M890CE Host Bridge [1106:0336] lspci -knn: Kernel driver in use: agpgart-amd64 lspci -knn: 00:00.1 Host bridge [0600]: VIA Technologies, Inc. K8M890CE Host Bridge [1106:1336] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:80ed] lspci -knn: 00:00.2 Host bridge [0600]: VIA Technologies, Inc. K8M890CE Host Bridge [1106:2336] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:80ed] lspci -knn: 00:00.3 Host bridge [0600]: VIA Technologies, Inc. K8M890CE Host Bridge [1106:3336] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:80ed] lspci -knn: 00:00.4 Host bridge [0600]: VIA Technologies, Inc. K8M890CE Host Bridge [1106:4336] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:80ed] lspci -knn: 00:00.5 PIC [0800]: VIA Technologies, Inc. K8M890CE I/O APIC Interrupt Controller [1106:5336] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:80ed] lspci -knn: 00:00.6 Host bridge [0600]: VIA Technologies, Inc. Device [1106:6290] lspci -knn: Subsystem: Device [0008:] lspci -knn: 00:00.7 Host bridge [0600]: VIA Technologies, Inc. K8M890CE Host Bridge [1106:7336] lspci -knn: 00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South] [1106:b188] lspci -knn: 00:02.0 PCI bridge [0604]: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller [1106:a238] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:03.0 PCI bridge [0604]: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller [1106:c238] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:0f.0 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 07) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:80ed] lspci -knn: Kernel driver in use: pata_via lspci -knn: 00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev a0) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:80ed] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev a0) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:80ed] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev a0) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:80ed] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:10.3 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev a0) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:80ed] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:10.4 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104]
Bug#732039: marked as done (installation-reports: success on Lenovo Thinkpad X201 using Jessie current ISO copies to USB stick)
Your message dated Sat, 28 Dec 2013 22:20:36 -0500 with message-id 20131229032036.GA31940@brain and subject line Re: Bug#732039: installation-reports: success on Lenovo Thinkpad X201 using Jessie current ISO copies to USB stick has caused the Debian Bug report #732039, regarding installation-reports: success on Lenovo Thinkpad X201 using Jessie current ISO copies to USB stick 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.) -- 732039: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: wishlist Dear Maintainer, After failing to install using the latest image, because the md5sum.txt file had a bad md5sum for one of the installation packages (e2fsprogs*udeb*), i downloaded the image from earlier in the day and it worked just fine, with manual partition- ing, creating an LVM, ext4 filesystems, etc., clobbering an NTFS partition and leaving the rescue partition alone Suspend to disk works fine, wireless works fine after installing the appropriate firmware non-free package. (I installed using the wired Ethernet; wireless wasn't configured by the installer, and so it didn't go looking for the firmware tarball i unpacked into a /firmware directory on a VFAT filesystem i appended to the USB stick) -- Package-specific info: Boot method: USB Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/current/amd64/iso-cd/debian-testing-amd64-netinst.iso Dec 10 2013 Date: Date and time of the install Machine: Lenovo Thinkpad X201 Partitions: df -Tl will do; the raw partition table is preferred 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] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Reboot failed, as i'd tried to install grub into the /boot partition so i could boot into the recovery partition, but couldn't figure out how to do that, so i input /dev/sda which seemed to work, but i got Operating system missing or some such DOS/Windows MBR boot-failure message, so i rebooted the USB stick in rescue mode, started up a shell using the newly installed root filesystem and mounted /usr and /boot, and ran grub-install, which refused to install in /dev/sda1, so i let it overwrite the /dev/sda I only selected the base Debian and print server tasks -- == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=8 (jessie) - installer build 20131124-00:05 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux runt 3.11-2-amd64 #1 SMP Debian 3.11.8-1 (2013-11-13) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0044] (rev 02) lspci -knn: Subsystem: Lenovo Device [17aa:2193] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) lspci -knn: Subsystem: Lenovo Device [17aa:215a] lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06) lspci -knn: Subsystem: Lenovo Device [17aa:215f] lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82577LM Gigabit Network Connection [8086:10ea] (rev 06) lspci -knn: Subsystem: Lenovo Device [17aa:2153] lspci -knn: Kernel driver in use: e1000e lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 06) lspci -knn: Subsystem: Lenovo Device [17aa:2163] lspci -knn: Kernel driver in use: ehci-pci lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 06) lspci -knn: Subsystem: Lenovo Device [17aa:215e] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 06) lspci -knn:
Re: Q: How to rebuild d-i or initrd?
Hi, I am also wanting to rebuild the debian-installer as I am totally blind and would like to build a version that automatically starts speakup on boot rather then having to press a letter as sometimes I am not always sure when the drive stops spinning so most of the time I am successful but not all of the time. Also having the ability to set the proper volume and speech rate as well as what language espeak uses by default would be a very nice thing to document. On my desktop system that is 32 bit I like the feature where the pc speaker beeps but how in my local copy of the debian-installer can I just configure all of the targets to beep if a built in pc speaker is installed as I read about the configuration leaves or so they call it but to make a change across the entire local copy of the debian-installer so they all do the same thing I am not sure where to look. On my 64 bit system there is no pc speaker that can beep but the sound card is detected properly so I do get speech and my next question is can I build a 32 and a 64 bit debian-installer on either system even if the 64 bit debian-installer won't run on the 32 bit system? Nick Gawronski On 12/28/2013 3:36 PM, Ozi Traveller wrote: I made a replacement for rootskel-gtk, using the previous version rootskel-gtk_1.27_amd64.udeb as the source, with a higher version number. I've changed the theme and the logo. I've been told that the way to have the d-i use this new version is to rebuild d-i (preferably) or the initrd (at least). My question is, how do I rebuild the d-i and then how do I incorporate the new d-i in my build? Cheers