Bug#571204: tasksel: Does not install network management software for LXDE
Daniel Baumann wrote: i don't know why tasksel uses lxde-core, but, if you would depend on lxde instead, you would get network-manager-gnome that the lxde maintainers in debian recommend for their users. I think lxde shouldn't use NetworkManager by default. It's Lightweight X11 Desktop Environment, and use wicd instead. -- 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/20120708134329.GA11907@lisko
Bug#680519: please do depend on gdm3 for lxde-desktop
On Sat, Jul 07, 2012 at 06:53:13PM +0200, Daniel Baumann wrote: Touko Korpela touko.korp...@iki.fi wrote: Isn't it too big? for the live images, we've always been using gdm/gdm3 in lxde-desktop, for the installer (via tasksel), up to squeeze, gdm was used too. i don't think it's to big. having lxdm at some later point though, is nice, and i wouldn't mind the size decrease it bringts, however, until then the size difference doesn't matter much. otoh, choosing xdm is a no-go anyway, it doesn't support autologin (which is essential for live systems) and i don't think that the the installer (via tasksel) should use anything different than what we do with the live systems. Shouldn't it use lightdm by default like Xfce does? lightdm is relatively buggy, does not reasonably support autologin yet, and doesn't bring any advantages over gdm3. gdm3 is even smaller in footprint size than gdm in squeeze, hence, using gdm3 in wheezy rather than gdm in squeeze is already an improvement. New lightdm (1.2.2-3) says to support autologin, but I haven't tested that. If you make this change, does it make Xfce+lxde CD-images try to pull Gnome depends in and make too tight to fit all? -- 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/20120707174904.GA2307@tiikeri.vuoristo.local
Bug#680519: please do depend on gdm3 for lxde-desktop
Daniel Baumann wrote: Hi, I'm one of the lxde maintainers in debian and we have the consens in the team that we are recommending gdm3 to be used as the display manager for lxde systems (which can be seen by e.g. looking at src:lxde-metapackages, until lxdm is in the archive for wheezy+1). Hence, please use gdm3 and not xdm in tasksel for lxde-desktop. Isn't it too big? Shouldn't it use lightdm by default like Xfce does? -- 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/20120706213744.GA18307@lisko
Re: Bug#645709: www.debian.org: Debian “squeeze” Installation Information , errata outdated?
On Mon, Oct 17, 2011 at 07:31:39PM -0400, David Prévot wrote: http://www.debian.org/releases/squeeze/debian-installer/ Errata lists some items as This will be fixed on the next Squeeze point release (6.0.1). Now 6.0.3 is released, so maybe those are now fixed? Thanks for your report, Debian Installer team CC: could you please update the page as needed? I know that you are busy with wheezy installer, but squeeze installer errata list is still at pre 6.0.1 level. Many bugs are now fixed but some remain. -- 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/20120627165348.GA25600@tiikeri.vuoristo.local
Re: Please upgrade your chroots: dpkg 1.16.4
Cyril Brulebois wrote: Hello, apparently dpkg had quite some nasty bugs (#675613, #676061, #676062, #676107, #676118, #676122), making it hard to deal with anything sgml-related. This should be fixed in dpkg 1.16.4, so please upgrade your chroots. Please also give back debian-installer if it failed to build on your arch. 1.16.4 introduced regressions while fixing bugs, that were fixed in 1.16.4.[12] 1.16.4.3 should migrate tomorrow (I asked if it was possible sooner...) -- 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/20120627182646.GA12130@lisko
Bug#678795: task-desktop: Flash support should pull in browser-plugin-lightspark
On Sun, Jun 24, 2012 at 12:27:21PM +0200, Petter Reinholdtsen wrote: [Christian PERRIER] So both can coexist peacefully? I believe so. I have not checked it myself, but know there were talk about having lightspark calling gnash when it found AVM1 flash files. Not sure if both browsers plugin should be installed, or only the lightspark one and the gnash standalone program. Flash maintainers, can you tell about compatibility of these plugins and what packages should be installed by default in wheezy? -- 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/20120626151305.GA20158@lisko
Bug#678015: debian-installer: Guided partitioning took 26 hours to complete erasure of encripted LVM volume
On Mon, Jun 18, 2012 at 09:54:13PM +0200, Philipp Kern wrote: On Mon, Jun 18, 2012 at 01:40:23PM -0300, Fernando J. RodrÃguez wrote: Please consider: a) changing the erase algorithm for someting more expeditive, even at the expense of some effectiveness; b) asking the user if she actually wants to erase the contents of the newly created volume; c) warning the user that the erasing could take more than 1 day. The latter probably makes sense. I'm pretty sure that the user is asked, because I always skipped it. On the other hand it's not for pre-existing data to be wiped but for the encrypted volume to appear completely random. Otherwise it's pretty obvious which blocks are allocated and which are not. (Not sure how useful that information is.) It's not about effectiveness but about security, sadly. If it is using /dev/urandom now, that is overkill. There exists many algorithms/programs using random output (many packaged in Debian) that are many times faster and they are safe enough for this. -- 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/20120618202608.GA22389@lisko
Re: Confirmed
On Thu, Jun 14, 2012 at 11:36:42PM -0400, Filipus Klutiero wrote: Thank you for the fix Milan. I verified that 0.9.6 fixes the problem on my testing install. However, this report shouldn't have been downgraded. Thank you also for applying the fix David, although it would be nice to watch credits in the future. It would also have been nice to upload a new version focusing on this bug (and perhaps other important bugs) at high urgency. This needs to migrate to testing before dailies and weeklies get usable again. I asked the release team to consider urging migration anyway. Release team, maybe you should let apt 0.9.6 migrate testing faster so CD images work again. (Filipus is maybe still blocked from posting to some lists so this didn't reach you first) -- 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/20120616001800.GA24973@lisko
Bug#672160: Fw: Re: Bug#672160: Directory /boot/console-setup
Yves-Alexis Perez wrote on debian-devel: On ven., 2012-05-11 at 00:16 +0300, Anton Zinoviev wrote: On Thu, May 10, 2012 at 09:40:23PM +0100, Ben Hutchings wrote: Generally the console has to work even before root is mounted, so that the user can enter a decryption password if necessary. Unfortunately, as far as I know currently this doesn't work in Debian. Proper wishlist bug reports have been filled but we haven't come yet to a solution that is good for all developers. What do you mean with “this doesn't work in Debian”? Some people do use encrypted root and they do have a working console asking for the passphrase. -- 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/20120512112517.GA5146@lisko
Bug#672316: Update for new HW data
Package: discover-data Version: 2.2010.10.18 Severity: normal Tags: wheezy,sid This package seems to contain hardware lists downloaded from net. Maybe update for wheezy installer is needed? -- Package-specific info: lspci: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 14h Processor Root Complex [1022:1510] 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6310] [1002:9802] 00:01.1 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI Wrestler HDMI Audio [Radeon HD 6250/6310] [1002:1314] 00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Family 14h Processor Root Port [1022:1512] 00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391] 00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] 00:12.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] 00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] 00:13.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] 00:14.0 SMBus [0c05]: Advanced Micro Devices [AMD] nee ATI SBx00 SMBus Controller [1002:4385] (rev 42) 00:14.2 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA) [1002:4383] (rev 40) 00:14.3 ISA bridge [0601]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 LPC host controller [1002:439d] (rev 40) 00:14.4 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI SBx00 PCI to PCI Bridge [1002:4384] (rev 40) 00:15.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0) [1002:43a0] 00:15.2 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI SB900 PCI to PCI bridge (PCIE port 2) [1002:43a2] 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 0 [1022:1700] (rev 43) 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 1 [1022:1701] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 2 [1022:1702] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 3 [1022:1703] 00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 4 [1022:1704] 00:18.5 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 6 [1022:1718] 00:18.6 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 5 [1022:1716] 00:18.7 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 7 [1022:1719] 01:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01) 06:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller [1b21:1042] lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 002 Device 003: ID 13d3:5711 IMC Networks Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub loaded modules: 1002:9802 drm 1002:1314 snd_hda_intel 1002:4391 ahci 1002:4397 ohci_hcd 1002:4396 ehci_hcd 1002:4397 ohci_hcd 1002:4396 ehci_hcd 1002:4383 snd_hda_intel 1022:1703 k10temp 14e4:4727 brcmsmac 1b21:1042 xhci_hcd -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash discover-data depends on no packages. Versions of packages discover-data recommends: ii pciutils 1:3.1.9-2 discover-data suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120509232856.6550.64780.reportbug@lisko
Bug#661069: Bug#649448: radeon (evergreen): random-looking pattern of pixels when firmware not installed
Installer has also a bug report about this (#661069). It would be good if Debian kernel radeon driver learned to fall back sensibly if running on hardware where firmware is required. Also installer should warn user about what happens if firmware is missing. -- 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/20120423182150.GA8524@tiikeri.vuoristo.local
Bug#650819: Confirmed, serious
On Sat, Mar 31, 2012 at 07:58:17PM -0400, Filipus Klutiero wrote: severity 650819 serious tags 650819 + confirmed patch retitle 650819 GRUB entries (grub.cfg) sometimes lacking other operating systems, particularly installing 686 or amd64 images (i386) reassign 650819 os-prober, grub-common thanks Looks like your BTS commands were ignored (maybe because of MIME multipart message). -- 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/20120405121620.GA18110@lisko
Bug#645997: installation-reports: Failed install with encrypted LVM (kernel install fails)
On Wed, Oct 26, 2011 at 09:13:11PM +0100, Miguel Figueiredo wrote: Hi, i have been trying to reproduce the bug but i haven't been able to do it anymore even after several atempts. Can you still reproduce it? Sorry taking long to answer. It was btrfs issue, I soon made another try with ext4, it worked. I have read that btrfs should now work with current 3.2.x kernel. -- 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/20120320215109.GA26014@tiikeri.vuoristo.local
Bug#645997: installation-reports: Failed install with encrypted LVM (kernel install fails)
On Tue, Mar 20, 2012 at 11:00:45PM +, Miguel Figueiredo wrote: Hi, a few days ago i've tested an installation with btrfs and didn't failed as before. Please give also some feedback on your tests. I haven't made any new tests after first try. You can close this. -- 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/20120321003416.GA29678@tiikeri.vuoristo.local
Bug#646306: installation-reports: Corrupted display in wheezy with Asus 1215b
On Mon, Oct 24, 2011 at 11:31:56PM +0100, Miguel Figueiredo wrote: A Sábado, 22 de Outubro de 2011 22:33:17 Touko Korpela você escreveu: Asus 1215B According manufacturer specifications [1] that machine can have 3 different graphic cards. Can you identify the one you have with lspci? I will reassign it to linux-2.6, due to the radeon module, if there's no objections. 1 - http://www.asus.com/Eee/Eee_PC/Eee_PC_1215B/#specifications lspci output can be found at bug #645997 -- 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/20111025132213.GA4871@tiikeri.vuoristo.local
Bug#646306: installation-reports: Corrupted display in wheezy with Asus 1215b
I suspect this may be missing video firmware releated. Screen becomes corrupted soon after encryption password is given when screen mode should switch. I think non-free firmware is required for non-vga modes. I have firmware packages installed in old system and it works fine. Installer didn't warn about it or give option to include non-free repo. I had during install (at separate usb-media) firmware packages firmware-brcm80211_0.33_all.deb (for wlan, installer could use it and wlan worked during installation) and firmware-linux-nonfree_0.33_all.deb (this includes needed Radeon firmwares). Is installer smart enough to copy these packages to installed system? -- 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/20111023224324.GA21369@tiikeri.vuoristo.local
Bug#645997: installation-reports: Failed install with encrypted LVM (kernel install fails)
On Fri, Oct 21, 2011 at 01:17:20AM +0300, Touko Korpela wrote: On Thu, Oct 20, 2011 at 10:08:53PM +0100, Miguel Figueiredo wrote: Hi, There were several pre-dependency problems but in the end it seems the disk is filled up and prevents the kernel to be installed: Oct 20 10:01:02 in-target: dpkg: error processing /media/cdrom//pool/main/l/linux-2.6/linux-image-3.0.0-1- amd64_3.0.0-3_amd64.deb (--unpack): Oct 20 10:01:02 in-target: unable to install new version of `/lib/modules/3.0.0-1-amd64/kernel/drivers/scsi/advansys.ko': No space left on device Oct 20 10:01:02 in-target: configured to not write apport reports Oct 20 10:01:03 in-target: Examining /etc/kernel/postrm.d . Oct 20 10:01:03 in-target: run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.0.0-1-amd64 /boot/vmlinuz-3.0.0-1-amd64 Oct 20 10:01:03 in-target: Processing triggers for man-db ... Oct 20 10:01:04 in-target: Errors were encountered while processing: Oct 20 10:01:04 in-target: /media/cdrom//pool/main/l/linux-2.6/linux- image-3.0.0-1-amd64_3.0.0-3_amd64.deb Oct 20 10:01:04 in-target: E: Sub-process /usr/bin/dpkg returned an error code (1) Oct 20 10:01:04 base-installer: error: exiting on error base- installer/kernel/failed-install Target /boot was 290MB and root was 6GB . I'm quite sure that they didn't get full during base system install. Stable 3.0.x kernel releases have some btrfs fixes, that aren't included in installer kernel (3.0.0-1 is quite old release). Or maybe it's not btrfs related, but more testing is needed. New install from same media completed fine when I used just ext4 filesystems. But it has bad screen corruption problem (I opened new bugreport for it). -- 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/20111023002355.GA27106@tiikeri.vuoristo.local
Bug#645997: installation-reports: Failed install with encrypted LVM (kernel install fails)
Package: installation-reports Severity: important Tags: d-i -- Package-specific info: Boot method: CD Image version: debian-testing-amd64-netinst.iso (2011101921461800) (sid build) Date: Date and time of the install Machine: Asus 1215B Partitions: df -Tl will do; the raw partition table is preferred Filesystem 1K-blocks Used Available Use% Mounted on none36550440365464 0% /run tmpfs 1827508 0 1827508 0% /dev /dev/sdc1 215008215008 0 100% /cdrom /dev/mapper/LISKO_VG-rootlv 5857280300552 4461768 6% /target (btrfs) /dev/sda1 282599 10254257753 4% /target/boot (ext4) /dev/mapper/LISKO_VG-homelv 4589568056 43769856 0% /target/home (btrfs) /dev/mapper/LISKO_VG-rootlv 5857280300552 4461768 6% /dev/.static/dev tmpfs 1827508 0 1827508 0% /target/dev /dev/sdc1 215008215008 0 100% /target/media/cdrom Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] (loaded wlan firmware from separate media) Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O?] Install base system:[E] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: I passed priority=medium boot parameter to installer I used manual partitioning, because guided partitioning didn't seem to let me create encrypted LVM that won't fill up whole disk (maybe it should). Kernel used during install was old version from July (Linux version 3.0.0-1-amd64 (Debian 3.0.0-1). Shouldn't daily images use current wheezy kernel (same that is installed to target system)? Base installer gave kernel options for installation: linux-image-amd64 linux-image-3.0.0-1-amd64 linux-image-2.6-amd64 Those options are one and same kernel, right? It should tell that others are metapackages and recommend them. But I selected linux-image-3.0.0-1-amd64 Then installation failed. Did it try to install kernel or modules to wrong filesystem? lspci and lsusb listings are taken from previous Debian install with same system rootfs on / type rootfs (rw) none on /run type tmpfs (rw,nosuid,relatime,size=365504k,mode=755) none on /proc type proc (rw,relatime) none on /sys type sysfs (rw,relatime) tmpfs on /dev type tmpfs (rw,relatime,mode=755) none on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) /dev/sdc1 on /cdrom type iso9660 (ro,relatime) /dev/mapper/LISKO_VG-rootlv on /target type btrfs (rw,relatime) /dev/sda1 on /target/boot type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered) /dev/mapper/LISKO_VG-homelv on /target/home type btrfs (rw,relatime) /dev/mapper/LISKO_VG-rootlv on /dev/.static/dev type btrfs (rw,relatime) tmpfs on /target/dev type tmpfs (rw,relatime,mode=755) /dev/sdc1 on /target/media/cdrom type iso9660 (ro,relatime) 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1510] Subsystem: Advanced Micro Devices [AMD] Device [1022:1510] 00:01.0 VGA compatible controller [0300]: ATI Technologies Inc Device [1002:9802] Subsystem: ASUSTeK Computer Inc. Device [1043:84a5] Kernel driver in use: radeon 00:01.1 Audio device [0403]: ATI Technologies Inc Device [1002:1314] Subsystem: ASUSTeK Computer Inc. Device [1043:84a5] Kernel driver in use: HDA Intel 00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:1512] Kernel driver in use: pcieport 00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] [1002:4391] Subsystem: ATI Technologies Inc Device [1002:4390] Kernel driver in use: ahci 00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] Subsystem: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] Kernel driver in use: ohci_hcd 00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] Subsystem: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] Kernel driver in use: ehci_hcd 00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] Subsystem: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] Kernel driver in use: ohci_hcd 00:13.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] Subsystem: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] Kernel driver in use: ehci_hcd 00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 42)
Bug#645997: installation-reports: Failed install with encrypted LVM (kernel install fails)
On Thu, Oct 20, 2011 at 04:04:11PM +0300, Touko Korpela wrote: Package: installation-reports Severity: important Tags: d-i -- Package-specific info: Boot method: CD Image version: debian-testing-amd64-netinst.iso (2011101921461800) (sid build) installer was booted from USB flash media, not CD -- 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/20111020131710.GA21107@tiikeri.vuoristo.local
Bug#645997: installation-reports: Failed install with encrypted LVM (kernel install fails)
On Thu, Oct 20, 2011 at 10:08:53PM +0100, Miguel Figueiredo wrote: Hi, There were several pre-dependency problems but in the end it seems the disk is filled up and prevents the kernel to be installed: Oct 20 10:01:02 in-target: dpkg: error processing /media/cdrom//pool/main/l/linux-2.6/linux-image-3.0.0-1- amd64_3.0.0-3_amd64.deb (--unpack): Oct 20 10:01:02 in-target: unable to install new version of `/lib/modules/3.0.0-1-amd64/kernel/drivers/scsi/advansys.ko': No space left on device Oct 20 10:01:02 in-target: configured to not write apport reports Oct 20 10:01:03 in-target: Examining /etc/kernel/postrm.d . Oct 20 10:01:03 in-target: run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.0.0-1-amd64 /boot/vmlinuz-3.0.0-1-amd64 Oct 20 10:01:03 in-target: Processing triggers for man-db ... Oct 20 10:01:04 in-target: Errors were encountered while processing: Oct 20 10:01:04 in-target: /media/cdrom//pool/main/l/linux-2.6/linux- image-3.0.0-1-amd64_3.0.0-3_amd64.deb Oct 20 10:01:04 in-target: E: Sub-process /usr/bin/dpkg returned an error code (1) Oct 20 10:01:04 base-installer: error: exiting on error base- installer/kernel/failed-install Target /boot was 290MB and root was 6GB . I'm quite sure that they didn't get full during base system install. Stable 3.0.x kernel releases have some btrfs fixes, that aren't included in installer kernel (3.0.0-1 is quite old release). Or maybe it's not btrfs related, but more testing is needed. I plan to complete this install soon, and don't want to test things too long. Some bugreports are made about hybrid CD images (I used that too), it can cause trouble when installing from USB media. -- 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/20111020221720.GA30751@tiikeri.vuoristo.local
Re: Daily build netinst documentation
On Wed, Oct 19, 2011 at 04:12:12AM +0300, Touko Korpela wrote: I'm planning to install wheezy using netinstall, but not always wanting to use cutting edge daily installer build (or is it required at this stage of wheezy cycle?). http://www.debian.org/CD/netinst/ ...links to: http://www.debian.org/devel/debian-installer/ ...that offers downloads with installer build from sid What's the difference between installer build from wheezy and installer build from sid? You should tell what wheezy uses the last known-good d-i image from the archive (aka squeeze release at the moment). means. Does it use old squeeze kernel during install (2.6.32) or wheezy (3.x) and has it any new features compared to squeeze installer (apart that it installs wheezy by default)? I looked inside of both images and it looks like they use 3.x kernel, good. What about btrfs support and wlan card support (unsecured or with WPA)? I know that firmware files have to be given with separate media. -- 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/20111019154041.GA4294@lisko
Re: Daily build netinst documentation
On Wed, Oct 19, 2011 at 06:40:41PM +0300, Touko Korpela wrote: On Wed, Oct 19, 2011 at 04:12:12AM +0300, Touko Korpela wrote: I'm planning to install wheezy using netinstall, but not always wanting to use cutting edge daily installer build (or is it required at this stage of wheezy cycle?). http://www.debian.org/CD/netinst/ ...links to: http://www.debian.org/devel/debian-installer/ ...that offers downloads with installer build from sid What's the difference between installer build from wheezy and installer build from sid? You should tell what wheezy uses the last known-good d-i image from the archive (aka squeeze release at the moment). means. Does it use old squeeze kernel during install (2.6.32) or wheezy (3.x) and has it any new features compared to squeeze installer (apart that it installs wheezy by default)? I looked inside of both images and it looks like they use 3.x kernel, good. I tested, installer build from wheezy uses 2.6.32 kernel during install :( -- 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/20111019163228.GA2161@lisko
Re: Daily build netinst documentation
On Wed, Oct 19, 2011 at 07:32:28PM +0300, Touko Korpela wrote: On Wed, Oct 19, 2011 at 04:12:12AM +0300, Touko Korpela wrote: I'm planning to install wheezy using netinstall, but not always wanting to use cutting edge daily installer build (or is it required at this stage of wheezy cycle?). http://www.debian.org/CD/netinst/ ...links to: http://www.debian.org/devel/debian-installer/ ...that offers downloads with installer build from sid What's the difference between installer build from wheezy and installer build from sid? I tested, installer build from wheezy uses 2.6.32 kernel during install :( I think it would be good to show at help page of installer download page (parent directory), kernel version used by different image flavours. 2.6.32 is too old for some new machines. Does weekly builds use 3.x kernel or 2.6.32? Is there a reason why weekly builds don't have netinst images? -- 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/20111019180231.GA2358@lisko
Daily build netinst documentation
I'm planning to install wheezy using netinstall, but not always wanting to use cutting edge daily installer build (or is it required at this stage of wheezy cycle?). http://www.debian.org/CD/netinst/ ...links to: http://www.debian.org/devel/debian-installer/ ...that offers downloads with installer build from sid What's the difference between installer build from wheezy and installer build from sid? You should tell what wheezy uses the last known-good d-i image from the archive (aka squeeze release at the moment). means. Does it use old squeeze kernel during install (2.6.32) or wheezy (3.x) and has it any new features compared to squeeze installer (apart that it installs wheezy by default)? quote from http://cdimage.debian.org/cdimage/daily-builds/ --- What are the daily builds? These images are produced regularly, normally twice daily but this may change from time to time. There are multiple CDs built in each run: * wheezy businesscard for each arch except s390 (small image, no * packages - just contains d-i) * wheezy netinst for each arch except s390 (slightly larger image, d-i * and the base system only) * sid businesscard (as above) * sid netinst (as above) The wheezy and sid versions determine the version of d-i used in each case. wheezy uses the last known-good d-i image from the archive (aka squeeze release at the moment). sid uses the latest build from the porters for each architecture. The daily, daily.new and daily.old links below are just symlinks to wheezy_d-i and sid_d-i as appropriate (for convenience). Within each directory, you'll find the last 6 builds labelled by date and build number within that day. There are more symlinks provided too: current points to the last build that was done; arch-latest points to the last successful CD build for each architecture. (NOTE: that's not a guarantee that the CDs are useful, just that the build script did not fail!). --- -- 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/20111019011212.GA2972@lisko
Documenting USB install
At www.debian.org/CD (various subpages and FAQ) documents talk mainly CD images and CD install. Nowdays USB install is maybe already more common. Current images can also boot from USB media (hybrid image), correct? Debian Live documents USB install so I think that main installer should too. -- 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/20110701194343.GA8949@tiikeri.vuoristo.local
Stable 6.0.2.1 images broken?
At http://cdimage.debian.org/debian-cd/6.0.2.1/$arch/iso-cd/ (i386,amd64 etc.) reads the following text: Daily build # for i386, using installer build from squeeze These images will install the testing version of Debian, currently Wheezy. See the top-level daily directory for more information about the daily builds. This build finished at Tue Jun 28 13:01:51 UTC 2011. This seems to be an error, are just this text wrong or are squeeze installation images now installing wheezy instead? -- 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/20110628191310.GA11652@tiikeri.vuoristo.local
Installation with multiple Software RAID devices + LVM
I'd like to install Lenny into existing LVM volume group built top of Software RAID-1 physical volumes like this: pvs: PV VG Fmt Attr PSize PFree /dev/md0 LVM_VG_2 lvm2 a- 50,13G 0 /dev/md1 LVM_VG_2 lvm2 a- 14,80G 80,00M /proc/mdstat: Personalities : [raid1] md1 : active raid1 hda9[0] hdc6[1] 15518686 blocks super 1.2 [2/2] [UU] md0 : active raid1 hda7[0] hdc5[1] 52564544 blocks [2/2] [UU] Partitions are type fd Linux raid autodetect and autodetected fine using existing installation (mix of etch and lenny). I used priority=medium boot option to give more control during install. But Lenny installer or kernel doesn't autoassemble md1, only md0. I think it should bring md1 up too. Could it be about superblock version (md1 has version 1.2 superblock). Why version 0.90 is default? As workaround how I assemble array manually from installer without erasing data? (I'm not subscribed) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Can libcairo be unblocked?
* 10 days old (needed 10 days) * Not touching package, as requested by freeze (contact debian-release if update is needed) * Not considered Testing has 1.4.6-1.1 and unstable 1.4.10-1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [D-I] Kernel/module udebs status - massbuild script update
Frans Pop wrote: (Reply-to set to debian-boot list) Did you forget to cc debian-kernel? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#379129: Same issue still in Etch
Still MD5sums aren't signed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
