Re: (SOLVED) Help with a touchless, netbooted, preseeded installation of squeeze on lots of plugs
On 16/05/2012 17:17, Dan Tomlinson wrote: Hi all, I am trying to do something relatively advanced with the debian-installer netboot and preseed. I have been charged with the commissioning of a large number of Dreamplug armel machines with a Debian squeeze installation and I am attempting to get a completely touchless netboot install setup. I have achieved this to a large degree but there are a few pesky key presses that I can't seem to preseed away. This project, on the face of it should be simple, but the specifics of the Dreamplug hardware have caused some problems for me: - Stock Debian stable kernels do not work on this hardware. I have been forced to patch, build and package my own kernel. My kernels work but I can't install them via the normal preseed kernel selection for the following reasons... - The Dreamplug uboot bootloader needs a uImage installed into a special vfat partition on its internal SD card, with the rest of the OS installing to other partitions on the SD card. - Debian's kernel package system does not seem to support building and packaging uImages. - The d-i will not allow /boot to be vfat anyway so my special vfat partition needs to be mounted as something else (I chose /uboot). To get around all of the above, I have created a rather simple kernel package that just installs my custom uImage into /uboot and this is "apt-get installed" from my own repo in my late_command (to allow me to ignore the fact that my package is unverified). This all works but for the following error that pops up at the end of the installation: ┌─┤ [!!] Make the system bootable ├─┐ │ │ │ Installation step failed │ │ An installation step failed. You can try to run the failing item │ │ again from the menu, or skip it and choose something else. The │ │ failing step is: Make the system bootable │ │ │ │ │ │ │ └───┘ ... and syslog reports: May 16 16:16:33 in-target: Setting up uboot-mkimage (0.4) ... May 16 16:16:34 in-target: Cannot find a default kernel in /vmlinuz or /boot/vmlinuz May 16 16:16:34 flash-kernel-installer: error: flash-kernel failed May 16 16:16:34 main-menu[805]: WARNING **: Configuring 'flash-kernel-installer' failed with error code 1 May 16 16:16:34 main-menu[805]: WARNING **: Menu item 'flash-kernel-installer' failed. These errors are from the pre-built debian-installer from squeeze. I have also tried building the the one from svn but this fails due to uboot-mkimage changing to u-boot-tools and hence not being available in squeeze. Once I have navigated through the error and selected "Continue with no boot loader" from the menu, the installation finishes without any further issues and the installed system boots fine. A colleague and someone on the IRC suggested trying the nobootloader package so I put an "anna-install nobootloader" line in my early_command but aside from syslog reporting that it is queued and then retrieved, it doesn't make the problem go away. So ... my question is - does anyone have an easy way to do one of the following: a) Prevent the whole bootloader and kernel installation parts of the installer from running and just go straight onto running late_command and reboot. b) Turn off that *** warning and get the installer to just fail quietly then continue into late_command and reboot. I realise I am well out of documented preseed territory here and any solutions may require me to modify d-i source and build my own installer - this is fine. I just thought I would ask the developers before I dived into trying to hack this myself. Many thanks in advance, Dan Tomlinson PS: I may have to commission hundreds of these plugs so I really is worth my while to get this installation completely automated! Hi all, thanks to a quick reply off list from Philip Hands, I have found a solution to this! He mentioned something about about the stock kernel install automatically calling uboot-mkimage made me think I should stop fighting the installer... let it do what it wants to do and install a non-working kernel, then just fix it up at the end :) So - I found the solution! I let it install a stock kirkwood kernel (which wont work for this hardware), let the flash-kernel-installer do its stuff as it is supposed to, then in my late command I could remove the stock kernel and install mine instead - a quick switcheroo before reboot ;) I wanted a more elegant solution, but at this stage *any* solution that doesn't involve hacking "exit 0" into installer modules seems desirable :) Cheers, Dan -- Senior Systems Administrator NSMS (Network Systems Management Service) Oxford University Computing Services -- 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/4fb4d310.3030...@oucs.ox.ac.uk
Re: Debian Installation Alpha 1 AMD64 netinst ISO installation report
Le mardi 15 mai 2012 à 00:46 +0200, Cyril Brulebois a écrit : > > Note that I installed Debian within a virtual machine. When I rebooted > > the VM, and tried to install some packages (gnome-desktop-environment) > > to try out Gnome Shell, aptitude offerred to remove alsa and > > alsa-base. Apparently it did, because at the next reboot, I was left > > with no speech. This is not related to the installer, which worked > > very well. I would call this an RC bug. Hae anyone of you experienced > > this problem? Also, I wanted to let you know that their were > > alsa-related errors related to the PCM device, but didn't really > > affect anything, because I was able to get to the login prompt just > > fine. Their were also errors related to consolekit and the keymap. > > I'm putting gnome people to the loop for the sound issues. A wild guess: when installing gstreamer0.10-pulseaudio some other backends were removed, and no dependency remained on alsa-base. Since alsa-base is essential to having working sound, I’d suggest moving it to priority important, and/or adding a dependency somewhere in the stack (pulseaudio/linux-any would be a good choice). -- .''`. Josselin Mouette : :' : `. `' `- -- 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/1337250625.5346.4.camel@tomoyo
kfreebsd-* d-i autobuilding back again
Hi all! The daily builds of d-i should now be back for both kfreebsd- architectures. d-i.debian.org currently has binaries from my testrun ~2h ago and should get feed by croned builds starting tonight. Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- 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/874nrfaxb8@hepworth.siccegge.de
Re: kfreebsd-* d-i autobuilding back again
On 17/05/12 11:58, Christoph Egger wrote: > The daily builds of d-i should now be back for both kfreebsd- > architectures. Hi Christoph, Thanks a lot! I can start testing these again. Do you have any brief notes on what things you had to set up for this? Or a link to some docs / Wiki page explaining this. Just in case it needs doing again or if someone else needs needs this for some new arch. Thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.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/4fb4e2ce.2060...@pyro.eu.org
Re: [d-i alpha1 I18N] Untranslated menu entry regarding speech synthesizer
Christian PERRIER, le Thu 17 May 2012 07:46:38 +0200, a écrit : > OK, then. I made the needed change to espeakup. Thanks! > Samuel, would you upload a fixed version? Sure! 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/20120517114306.gf6...@type.famille.thibault.fr
Re: kfreebsd-* d-i autobuilding back again
Steven Chamberlain writes: > On 17/05/12 11:58, Christoph Egger wrote: >> The daily builds of d-i should now be back for both kfreebsd- >> architectures. > > Hi Christoph, > > Thanks a lot! I can start testing these again. > > Do you have any brief notes on what things you had to set up for this? > Or a link to some docs / Wiki page explaining this. Just in case it > needs doing again or if someone else needs needs this for some new arch. It's documented in the README + script from [0]. Though you'll need someone with access to the respective buildds for setup. Regards Christoph [0] https://buildd.debian.org/git/di-autobuild.git/ -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- 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/87obpn9g36@hepworth.siccegge.de
Bug#673274: installation-report: Wheezy installed for testing purposes
Package: installation-reports Version: 2.46 Severity: wishlist -- Package-specific info: Boot method: CD Image version: http://caesar.acc.umu.se/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-CD-1.iso Date: 2012-05-17, 14:00 h Machine: custom-built with 'AMD690GM-M2 PLUS' Mainboard Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on rootfs rootfs76462396 4888520 67744528 7% / udev devtmpfs376848 0 376848 0% /dev tmpfs tmpfs 76576 644 75932 1% /run /dev/disk/by-uuid/8b5a99f5-e481-4b02-9ddc-5194e9dfb50e ext4 76462396 4888520 67744528 7% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 153148 8153140 1% /tmp tmpfs tmpfs 153148 224152924 1% /run/shm /dev/sr0 iso9660 659456 659456 0 100% /media/cdrom0 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [o] Detect network card:[o] Configure network: [o] Detect CD: [o] Load installer modules: [o] Detect hard drives: [o] Partition hard drives: [o] Install base system:[o] Clock/timezone setup: [o] User/password setup:[o] Install tasks: [o] Install boot loader:[o] Overall install:[o] Comments/Problems: Installation of Wheezy pre-beta for testing purposes on AMD64 went fine, there was some delay when starting up the partitioner, that made me think the system was hanging, but the process went on after a while. Gnome3 initially started with the fallback-message, telling me that 3d-acceleration was missing. So I issued 'X -configure' in /etc/X11/ in single user mode, which gave me another error-message, telling me that the number of screens did not match. Upon system-restart the fallback-message was gone. See attachments Xorg.0.log.bz2 and the automatically generated xorg.conf.new.bz2 attached to this report. I installed the package 'gnome-desktop-environment' next and found that 'synaptic' was still missing upon that, but it should be part of the desktop-environment in my opinion. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="7.0 (wheezy) - installer build 20120508" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux a64d 3.2.0-2-amd64 #1 SMP Sun Apr 15 16:47:38 UTC 2012 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] nee ATI RS690 Host Bridge [1002:7910] lspci -knn: Subsystem: Advanced Micro Devices [AMD] nee ATI RS690 Host Bridge [1002:7910] lspci -knn: 00:01.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI RS690 PCI to PCI Bridge (Internal gfx) [1002:7912] lspci -knn: 00:12.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee ATI SB600 Non-Raid-5 SATA [1002:4380] lspci -knn:Subsystem: Elitegroup Computer Systems Device [1019:4380] lspci -knn: Kernel driver in use: ahci lspci -knn: 00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB600 USB (OHCI0) [1002:4387] lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:2621] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.1 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB600 USB (OHCI1) [1002:4388] lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:2621] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB600 USB (OHCI2) [1002:4389] lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:2621] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.3 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB600 USB (OHCI3) [1002:438a] lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:2621] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.4 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB600 USB (OHCI4) [1002:438b] lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:2621] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.5 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI
Bug#673274: attachments
xorg.conf.new.bz2 Description: application/bzip Xorg.0.log.bz2 Description: application/bzip
Re: Help with a touchless, netbooted, preseeded installation of squeeze on lots of plugs
On Wed, 16 May 2012 17:17:39 +0100, Dan Tomlinson wrote: > Hi all, > > I am trying to do something relatively advanced with the > debian-installer netboot and preseed. I have been charged with the > commissioning of a large number of Dreamplug armel machines with a > Debian squeeze installation and I am attempting to get a completely > touchless netboot install setup. I have achieved this to a large degree > but there are a few pesky key presses that I can't seem to preseed away. > > This project, on the face of it should be simple, but the specifics of > the Dreamplug hardware have caused some problems for me: > > - Stock Debian stable kernels do not work on this hardware. I have been > forced to patch, build and package my own kernel. My kernels work but I > can't install them via the normal preseed kernel selection for the > following reasons... > > - The Dreamplug uboot bootloader needs a uImage installed into a special > vfat partition on its internal SD card, with the rest of the OS > installing to other partitions on the SD card. This is odd -- I preseed OpenRD systems, and don't seem to have this problem. Are you installing the uboot-mkimage package? It seems that linux-image-2.6.32-5-kirkwood calls mkimage in its postinst, so if you make sure your kernel does the same thing, and ensure that that package is already installed, you may find that the uImage & uInitrd get generated for you automatically. Sorry to be vague, but it all just worked on the OpenRD. Anyway, if that works, you might be able to do your VFAT trick with a symlink in /boot -- but actually that just sounds like you're using the stock uboot, which is why you're restricted to VFAT (I'm assuming that the uboot they put on dreamplugs at the factory is as decrepit as the one on the OpenRD). For that reason, my automated installer includes an expect script that uses the JTAG (helpfully provided as a mini-USB on OpenRDs) to flash a more recent uboot onto the box, then set its defaults to boot from (in my case) SATA, then tell the new uboot to PXE boot from the install server, and the rest of the install goes through as a full preseed that gets enough of cfengine onto the box to then install the services I need. Sadly, the dreamplug does not include JTAG by default -- otherwise I'd have published all this already, as it would surely be useful for people then, but I'm dubious that it's that useful if step 1 is "buy the dev board" -- it's all very site specific at present too, so would need a fair amount of work for anyone else to use. Also, I'm not necessarily recommending replacing the stock uboot. uboot is a pain to get working quite often, and I wasted an inordinate amount of time trying to get all of SATA, SD and flash booting working -- IIRC the uboot I have now doesn't support SD booting on the OpenRD (it sees the SD, but always gets CRC errors on the images), whereas the other one I could have used doesn't support SATA -- so perhaps the quickest route is to live with the VFAT limitation, and add a hook somewhere that copies the images after they've been generated. HTH Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560]http://www.hands.com/ |-| HANDS.COM Ltd.http://www.uk.debian.org/ |(| 10 Onslow Gardens, South Woodford, London E18 1NE ENGLAND pgp7DpzAuDY2O.pgp Description: PGP signature
Re: Help with a touchless, netbooted, preseeded installation of squeeze on lots of plugs
On 16/05/2012 19:39, Philip Hands wrote: This is odd -- I preseed OpenRD systems, and don't seem to have this problem. Are you installing the uboot-mkimage package? It seems that linux-image-2.6.32-5-kirkwood calls mkimage in its postinst, so if you make sure your kernel does the same thing, and ensure that that package is already installed, you may find that the uImage& uInitrd get generated for you automatically. Hi Phil, thanks for your quick reply! I don't actually need a uInitrd - all the requisite hardware support is compiled into my kernel. Also, due to the non-standard way my kernel is installed (ie: the very last thing... in the late_command with an in-target apt-get), it is not in place when the installer gets around to the flash-kernel-installer stuff tries to do its work (and fails). The installer does seem to install uboot-mkimage but it fails because there is no kernel at the point where it is looking for a "/vmlinuz or /boot/vmlinuz". In the preseed kernel selection bit, I am using the options: d-i base-installer/kernel/image string none d-i base-installer/kernel/skip-install boolean true ... but this then leads on to the "Make the system bootable" error, which I can't seem to preseed away. Your line about the stock kernel install automatically calling uboot-mkimage made me think I should stop fighting the installer... let it do what it wants to do and install a non-working kernel, then just fix it up at the end :) So - I found the solution :) I let it install a stock kirkwood kernel (which wont work for this hardware), let the flash-kernel-installer do its stuff as it is supposed to, then in my late command I could remove the stock kernel and install mine instead - a quick switcheroo before reboot ;) I wanted a more elegant solution, but at this stage *any* solution that doesn't involve hacking "exit 0" into installer modules seems desirable :) Sorry to be vague, but it all just worked on the OpenRD. Anyway, if that works, you might be able to do your VFAT trick with a symlink in /boot -- but actually that just sounds like you're using the stock uboot, which is why you're restricted to VFAT (I'm assuming that the uboot they put on dreamplugs at the factory is as decrepit as the one on the OpenRD). I'm not familiar with OpenRD but your assessment sounds about right... For that reason, my automated installer includes an expect script that uses the JTAG (helpfully provided as a mini-USB on OpenRDs) to flash a more recent uboot onto the box, then set its defaults to boot from (in my case) SATA, then tell the new uboot to PXE boot from the install server, and the rest of the install goes through as a full preseed that gets enough of cfengine onto the box to then install the services I need. Sadly, the dreamplug does not include JTAG by default -- otherwise I'd have published all this already, as it would surely be useful for people then, but I'm dubious that it's that useful if step 1 is "buy the dev board" -- it's all very site specific at present too, so would need a fair amount of work for anyone else to use. Ah don't worry I have a JTAG - the Dreamplug has no on-board graphics so everything is done via serial console (one of the reasons why the stock kernel fails - it doesn't have support for this by default). Also, I'm not necessarily recommending replacing the stock uboot. uboot is a pain to get working quite often, and I wasted an inordinate amount of time trying to get all of SATA, SD and flash booting working -- IIRC the uboot I have now doesn't support SD booting on the OpenRD (it sees the SD, but always gets CRC errors on the images), whereas the other one I could have used doesn't support SATA -- so perhaps the quickest route is to live with the VFAT limitation, and add a hook somewhere that copies the images after they've been generated. I'd rather avoid replacing the uboot if possible - it may be a bit rubbish, but it works fine once you manage to get a uImage on the vfat partition. HTH You did indeed :) Cheers, Dan Cheers, Phil. -- Senior Systems Administrator NSMS (Network Systems Management Service) Oxford University Computing Services -- 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/4fb4d399.7000...@oucs.ox.ac.uk
Re: (SOLVED) Help with a touchless, netbooted, preseeded installation of squeeze on lots of plugs
On Thu, 17 May 2012 11:29:36 +0100, Dan Tomlinson wrote: ... > thanks to a quick reply off list from Philip Hands, I have found a > solution to this! due to a change in the keybindings for notmuch, that went off-list by mistake -- I've just forwarded those messages (with Dan's permission) to make them part of the list archive in case anyone else needs the same info. Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560]http://www.hands.com/ |-| HANDS.COM Ltd.http://www.uk.debian.org/ |(| 10 Onslow Gardens, South Woodford, London E18 1NE ENGLAND pgpLL2H5xmR2X.pgp Description: PGP signature
Bug#673195: [wheezy-alpha1] unable to install grub2 or lilo onto an btrfs filesystem
Hello, Holger Wansing wrote: > Package: debian-installer > > Test-installation with image: wheezy alpha1 xfce-lxde Binary-1 CD > on a virtualbox 3.2.10 i386 machine > > Since I read this in the wheezy-alpha1 announcement: > "Allow Btrfs /boot partition (GRUB 2 and LILO)" > ..., I tried to use a one-for-all btrfs filesystem (being the > only one existing partition for / a btrfs filesystem). > But installation of grub2 and lilo both failed. I choosed 'Guided partitioning' -> use hole disk -> everything on one partition -> I changed root-filesystem from ext4 into btrfs after that. grub-installer and lilo-installer failed, when it came to installing the bootloader to the MBR. Here are some infos from the logs (partly roughly translated from german to english): [Trying to install grub2 to MBR] info: Installing grub on '/dev/sda' info: grub-install supports --no-floppy info: Running chroot /target grub-install --no-floppy --force "/dev/sda" /usr/sbin/grub-probe: error cannot find a device for /boot/grub (is /dev mounted?) [Holger: yes, /dev was mounted. /dev/sda, /dev/sda1, /dev/sda2 and /dev/sda5 were existing] . error: Running 'grub-install --no-floppy --force "/dev/sda"' failed [...] WARNING **: Configuring 'grub-installer' failed with error code 1 WARNING **: Menu item 'grub-installer' failed. [Trying to install lilo to MBR] lilo (1:23.2-4 is configured... Trigger for menu are beeing processed ISO 9660 Extensions: Microsoft Joliet Level 3 ISO 9660 Extensions: RRIP_1991A ISO 9660 Extensions: Microsoft Joliet Level 3 ISO 9660 Extensions: RRIP_1991A Warning: LBA32 addressing assumed Fatal: Trying to map files from unnamed device 0x0013 (NFS/RAID mirror down ?) WARNING **: Configuring 'lilo-installer' failed with error code 1 WARNING **: Menu item 'lilo-installer' failed. Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Powered by Sylpheed 3.0.2 under Debian GNU/ / _ _ _ _ _ __ __ / /__ / / / \// //_// \ \/ / // /_/ /_/\/ /___/ /_/\_\6.0 / Squeeze. Registered LinuxUser #311290 - http://counter.li.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/20120517213542.ae4dd013.li...@wansing-online.de
Processed: Re: Bug#673200: [wheezy-alpha1] no X, when installing without internet access
Processing commands for cont...@bugs.debian.org: > retitle 673200 No X, when installing from one CD without internet access Bug #673200 [debian-installer] [wheezy-alpha1] xfce-lxde-cd #1: no X installed Changed Bug title to 'No X, when installing from one CD without internet access' from '[wheezy-alpha1] xfce-lxde-cd #1: no X installed' > thanks Stopping processing here. Please contact me if you need assistance. -- 673200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673200 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.133728733620936.transcr...@bugs.debian.org
Re: Wheezy release: CDs are not big enough any more...
Hi, Steve McIntyre wrote: > Remembering the fun that we had during the Squeeze release with trying > to make single-CD installations work well, it's time to consider what > we're going to *claim* to support in Wheezy. We've had a history of > supporting the following single-CD installations: > > * Gnome desktop from CD#1 > * KDE desktop from "KDE CD#1" > * XFCE desktop from "light CD#1" > * LXDE desktop from "light CD#1" > * base system only from netinst CD FYI: With the alpha1 images, it is not possible, to do an installation from only one CD image and without internet access, getting an X system as result. When using Alpha1 Binary-CD #1 Alpha1 KDE CD Alpha1 xfce-lxde CD and, as said before, having no internet access while installing, you are only provided the "Standard system tools" task, no "Desktop environment" is provided. See #673200. If you knew this already, sorry for the noise. Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Powered by Sylpheed 3.0.2 under Debian GNU/ / _ _ _ _ _ __ __ / /__ / / / \// //_// \ \/ / // /_/ /_/\/ /___/ /_/\_\6.0 / Squeeze. Registered LinuxUser #311290 - http://counter.li.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/20120517224902.9a3a4552.li...@wansing-online.de
Bug#673274: marked as done (installation-report: Wheezy installed for testing purposes)
Your message dated Thu, 17 May 2012 22:29:25 +0100 with message-id <4fb56db5.7030...@debianpt.org> and subject line Re: Bug#673274: installation-report: Wheezy installed for testing purposes has caused the Debian Bug report #673274, regarding installation-report: Wheezy installed for testing purposes 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.) -- 673274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Version: 2.46 Severity: wishlist -- Package-specific info: Boot method: CD Image version: http://caesar.acc.umu.se/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-CD-1.iso Date: 2012-05-17, 14:00 h Machine: custom-built with 'AMD690GM-M2 PLUS' Mainboard Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on rootfs rootfs76462396 4888520 67744528 7% / udev devtmpfs376848 0 376848 0% /dev tmpfs tmpfs 76576 644 75932 1% /run /dev/disk/by-uuid/8b5a99f5-e481-4b02-9ddc-5194e9dfb50e ext4 76462396 4888520 67744528 7% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 153148 8153140 1% /tmp tmpfs tmpfs 153148 224152924 1% /run/shm /dev/sr0 iso9660 659456 659456 0 100% /media/cdrom0 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [o] Detect network card:[o] Configure network: [o] Detect CD: [o] Load installer modules: [o] Detect hard drives: [o] Partition hard drives: [o] Install base system:[o] Clock/timezone setup: [o] User/password setup:[o] Install tasks: [o] Install boot loader:[o] Overall install:[o] Comments/Problems: Installation of Wheezy pre-beta for testing purposes on AMD64 went fine, there was some delay when starting up the partitioner, that made me think the system was hanging, but the process went on after a while. Gnome3 initially started with the fallback-message, telling me that 3d-acceleration was missing. So I issued 'X -configure' in /etc/X11/ in single user mode, which gave me another error-message, telling me that the number of screens did not match. Upon system-restart the fallback-message was gone. See attachments Xorg.0.log.bz2 and the automatically generated xorg.conf.new.bz2 attached to this report. I installed the package 'gnome-desktop-environment' next and found that 'synaptic' was still missing upon that, but it should be part of the desktop-environment in my opinion. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="7.0 (wheezy) - installer build 20120508" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux a64d 3.2.0-2-amd64 #1 SMP Sun Apr 15 16:47:38 UTC 2012 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] nee ATI RS690 Host Bridge [1002:7910] lspci -knn: Subsystem: Advanced Micro Devices [AMD] nee ATI RS690 Host Bridge [1002:7910] lspci -knn: 00:01.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI RS690 PCI to PCI Bridge (Internal gfx) [1002:7912] lspci -knn: 00:12.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee ATI SB600 Non-Raid-5 SATA [1002:4380] lspci -knn:Subsystem: Elitegroup Computer Systems Device [1019:4380] lspci -knn: Kernel driver in use: ahci lspci -knn: 00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB600 USB (OHCI0) [1002:4387] lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:2621] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.1 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB600 USB (OHCI1) [1002:4388] lspci -knn: Subsystem: Elit
Bug#673328: live-installer does not preserve /var/log; breaks freeradius
package: live-installer severity: normal If the live system includes the freeradius package, it fails to start freeradius because /var/log/freeradius fails to exist. As best I can tell something in the installer is clobbering /var/log because it's missing a lot of directories and files present in the squashfs image . I've not tracked down exactly what is going on; if it's not obvious to people familiar with d-i internals I'd be happy to try and do that. This was performed with d-i daily builds both from an image built today and from one built in December. -- 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/tslipfusdok@mit.edu
Bug#673195: [wheezy-alpha1] unable to install grub2 or lilo onto an btrfs filesystem
Hi, switching to a terminal and mounting /target/proc makes grub to install successfully: mount -t proc proc /target/proc this is the same workaround as in #662086. The installed image, when it boots, complains about fsck.btrfs not being available. -- Melhores cumprimentos/Best regards, Miguel Figueiredo <>
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * OLD BUILD:armel May 08 08:10 buildd@ancina build_iop32x_netboot http://d-i.debian.org/daily-images/armel/daily/build_iop32x_netboot.log * OLD BUILD:armel May 08 08:13 buildd@ancina build_iop32x_network-console_glantank http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_glantank.log * OLD BUILD:armel May 08 08:19 buildd@ancina build_iop32x_network-console_n2100 http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_n2100.log * OLD BUILD:armel May 08 08:22 buildd@ancina build_iop32x_network-console_ss4000e http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_ss4000e.log * OLD BUILD:armel May 08 08:24 buildd@ancina build_kirkwood_netboot http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot.log * OLD BUILD:armel May 08 08:30 buildd@ancina build_kirkwood_netboot-gtk http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot-gtk.log * OLD BUILD:armel May 08 08:33 buildd@ancina build_kirkwood_network-console http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_network-console.log * OLD BUILD:armel May 08 08:37 buildd@ancina build_orion5x_network-console http://d-i.debian.org/daily-images/armel/daily/build_orion5x_network-console.log * OLD BUILD:armel May 08 08:40 buildd@ancina build_versatile_netboot http://d-i.debian.org/daily-images/armel/daily/build_versatile_netboot.log * OLD BUILD:armel May 08 08:42 buildd@ancina build_ads_cf http://d-i.debian.org/daily-images/armel/daily/build_ads_cf.log * OLD BUILD:mipsel Apr 19 00:11 buildd@rem build_cobalt_netboot-2.6_serial http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_serial.log * OLD BUILD:mipsel Apr 19 00:14 buildd@rem build_cobalt_netboot-2.6_ssh http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_ssh.log * OLD BUILD:mipsel Apr 19 00:16 buildd@rem build_cobalt_netboot-2.6_common http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_common.log * OLD BUILD:mipsel Apr 19 00:19 buildd@rem build_malta_netboot-2.6 http://d-i.debian.org/daily-images/mipsel/daily/build_malta_netboot-2.6.log * OLD BUILD:mipsel Apr 19 00:22 buildd@rem build_sb1-bcm91250a_netboot-2.6 http://d-i.debian.org/daily-images/mipsel/daily/build_sb1-bcm91250a_netboot-2.6.log * OLD BUILD:mipsel Apr 19 00:26 buildd@rem build_loongson-2f_netboot-2.6 http://d-i.debian.org/daily-images/mipsel/daily/build_loongson-2f_netboot-2.6.log Totals: 117 builds (0 failed, 16 old) -- 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/e1svby4-0003mk...@ravel.debian.org
Participe da 6ª Edição da SEC - Semana de Encontro de Coordenadores
Olá debian-boot.lists.debian, Este programa não permite a visualização de mensagens formatadas (com cores, imagens e links), portanto solicitamos que você copie o texto abaixo, e cole no campo "Endereço" do seu navegador. http://emkt.epd.edu.br/emkt/tracer/?1,846080,ba610572,5b3e Para garantir que nossas mensagens cheguem em sua caixa de entrada, adicione o email epdm...@epd.edu.br ao seu catálogo de endereços. Não deseja mais receber nossas mensagens? Cancele sua inscrição aqui: http://emkt.epd.edu.br/emkt/tracer/?9,846080,ba610572,5b3e
Bug#673365: installation-report: dnet-common looks unnecessary for normal environment
Package: installation-reports Version: 2.44 Severity: normal Boot method: CD Image version: wheezy alpha1 i386 Date: 2012-05-18 Machine: VirtualBox 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] but... Install boot loader:[O] Overall install:[O] Comments/Problems: Of course all installations worked well on VirtualBox, but I noticed the installer (with choosing desktop on tasksel) asked dnet-common debconf configuration even debconf-level was high. Although I'm not sure what introduces dnet-common, setting DECnet seems unnecessary for modern environment. Thanks, -- Kenshi Muto km...@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/87zk96t4ww@cyclopus.topstudio-unet.ocn.ne.jp
