Bug#493065: debootstrap fakechroot variant fails for i386 chroot on AMD64 system
Package: debootstrap Version: 1.0.10 Severity: normal On an AMD64 system, it appears to be impossible to use the fakechroot variant to create an i386 chroot. * It is entirely possible for a user to create an i386 root using fakechroot and debootstrap on an i386 Debian system. * It is also possible for a user to create an AMD64 root using fakechroot and debootstrap on an AMD64 system. * Using Etch on an AMD64 system, it is possible to debootstrap an Etch i386 chroot using fakechroot. * Using Lenny on an AMD64 system, it is NOT possible to debootstrap a Lenny i386 chroot using fakechroot. When attempting to execute the command fakechroot fakeroot debootstrap --arch i386 --variant=fakechroot etch target I receive the message W: Failure trying to run: chroot /path/to/target dpkg --force-depends --install var/cache/apt/archives/base-files_4_i386.deb var/cache/apt/archives/base-passwd_3.5.11_i386.deb The contents of the target's /debootstrap/debootstrap.log are: dpkg: /home/zpalmer/sandbox/ztemp2/test7/lib/tls/libc.so.6: version `GLIBC_2.4' not found (required by /usr/lib32/libfakeroot/libfakeroot-sysv.so) This leads me to believe that it either has something to do with the way debootstrap executes the fakechroot variant or something to do with how the fakeroot package is built. Either way, this prevents cross-platform fakechroot debootstraps. I have no workaround at this time other than to create a normal 32-bit chroot on my system using privileges and do the fakechroot from within that. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25-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/bash Versions of packages debootstrap depends on: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii wget1.11.4-1 retrieves files from the web debootstrap recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] RAID10 and RAID6
On Thu, Jul 24, 2008 at 04:14:37PM -0700, Ryan Niebur wrote: > On Thu, Jul 24, 2008 at 09:39:15PM +0200, Frans Pop wrote: > > On Sunday 20 July 2008, Ryan Niebur wrote: > > > here are the patches > > > > Other than the comments below and final testing this looks ready for > > committing to me. > > > > yay! I have merged your patchs in a slightly different order and splitted support for RAID 6 from RAID 10. I have the later ready to be commited but I prefer to wait for the upload of updated kernel udebs. Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Re: unblocking partman-multipath
* Otavio Salvador [Mon, 28 Jul 2008 08:28:24 -0300]: > > Hi, > > please unblock partman-multipath. There's no version in lenny yet. This > > way folks building custom installers (due to #440675) can pull from > > lenny instead of sid. > Hello Guido, > Let's see if we can (I and you) produce a patch Parted's 1.8 branch > using the fixes we made for 1.9. > I won't upload 1.9 for Debian now and if we do it fast, after Parted > migrates to lenny, we might test it and try to get an > exception. However until that is done, I wouldn't like to have unused > udebs on lenny. Honest question: why? Does it have any negative impact? -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Any life, no matter how long and complex it may be, is made up of a single moment: the moment in which a man finds out, once and for all, who he is. -- Jorge Luis Borges -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Meeting summary (was: List of last possible inclusions for Lenny)
Hi! Glenn, Robert and mostly Otavio and me discussed this list tonight. Here are some conclusions: (and we can still revert stuff if they don't work fine enough) On Mon, Jul 28, 2008 at 10:25:04PM +0200, Jérémy Bobbio wrote: > * Bugfixes on partman-md and automatic activation of MD devices >(Jérémy Bobbio) > * Automatic activation of LVM devices >(Jérémy Bobbio) Include: * MD won't be more broken that it currently is. * Automatic activation should be done for both MD and LVM. * Commit after more tests by Jérémy on the LVM side. > * di-netboot-assistant >(Franklin Piat) Include: * Should be committed to the SVN repository. * Should be documented in the manual. > * Support for localized text frontend >(Samuel Thibault) Include: * Simple change. * If it breaks serial installations, digress will tell us. > * Add WPA support in netcfg >(Glenn Saberton) Don't include: * Changes in wpasupplicant have not received a freeze exception by the release team. * Needs measure on memory impact. * Should received wider testing. netcfg needs some cleanup and overall improvements. Let's wait until Lenny is released to work seriously on it. > * Add atl2 support to kernel-wedge >(Glenn Saberton) Include: * Switching to 2.6.26 means another round of kernel uploads, so no extra work. * But first need a patch against hw-detect to queue atl2-modules package installation on the target system. > * Alignment of partman columns in the graphical installer >(Jérémy Bobbio) Include: * Really improve usuability. * More than enough time to NACK changes. > * Support for terminal in the graphical installer >(Jérémy Bobbio) Include: * Add to the default initrd. * Need libvte9-udeb to be available (already ACKed by release team). > * RAID 6 and RAID 10 support >(Ryan Niebur) Include: * Last review was positive. * Jérémy will do the merge with his changes for partman-md. * Otavio will take care of kernel-wedge changes. > * Make syslinux beeps >(Samuel Thibault) Include (but only beep on *released* installation media): * This needs to be a configurable in the build system. * Samuel should propose a patch. > * Support of preseeding of LVM installation on multiple disks >(Grégory Oestreicher) Undecided: * Patch is fairly complex but most issues have been sorted quickly. * Add two new strings. Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#411552: A building that melts
Petrol prices soar upon signs that McCain shows aggression towards middle east ties http://sebastian-zierow.de/gowatch.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#266970: Teachers students how to find G-spot
College parties have gone wilder and riskier, all the secrets revealed here. http://kimkiminlenerede.com/gowatch.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#492899: partman-crypto: cancel button unusable on "Erasing data" screen
On Wed, Jul 30, 2008 at 11:58:38AM +0200, J?r?my Bobbio wrote: > On Tue, Jul 29, 2008 at 06:03:34PM -0600, dann frazier wrote: > > I wonder if there's a way to split the cancel checking and the > > progress checking? [???] > > It might be, but I am not inclined to do this kind of changes that tend > to breaks in very subtle way just before Lenny. makes sense > Dividing the progress bar in 65536 parts will give us an abitility to > cancel it every 1114112 written bytes, and should make it reactive > enough. Another option might be to make it dynamic, based on the size of the disk - I assume we'd need to add a parameter to the wipe utility to negotiate this in advance. That too might be something better suited for post-lenny exploration. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
klibc unblock
please unblock klibc 1.5.12-1 it contains mostly gcc-4.3 fixes, even if not used for it's compilation would be good to have them in stable. also we have a grave packaging error in klibc, which causes signal() not to be exported, see that message http://marc.info/?l=util-linux-ng&m=121743832321246&w=2 thus i would have to upload 1.5.12-2 soonest. i'd prefer to have 1.5.12-1 before in testing. or shall i upload against 1.5.11-3 ?? best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#492878: lenny installer -dosen't detect Broadcom ethernet adapter
On Wed, Jul 30, 2008 at 01:38:56PM +0200, Peter Tuhársky wrote: > It seems for me, that it simply fails to mount the USB pendrive. Anyhow, > the partition of course resides on /dev/sda1, not on /dev/sda! So I > don't wonder it fails. Strange… Could you watch dmesg log and see if it reads the partition table of your USB stick successfully? In the installer environment, could you look for the ouput of: $ list-devices disk $ list-devices partition Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#492878: lenny installer -dosen't detect Broadcom ethernet adapter
Bingo!
It is really the mount issue! I just manually mounted /dev/sda1 to /media
and whoila, the firmware is found now!
Maybe the script dosen't try to mount the sd{a|b|c}1, just the sd{a|b|c}
and therefore it must fail!
Peter
Jérémy Bobbio wrote / napísal(a):
(Please keep the bug CC'ed)
On Wed, Jul 30, 2008 at 09:30:40AM +0200, Peter Tuhársky wrote:
The installer should at least prompted you to supply a .fw firmware file.
Did it do this?
Well, I tested daily build from 20080729, and yes, the installer prompts
for these files. However, I can't figure out, how could I give it to
him. I have put them on the root of usb pendrive, they are exactly the
files that he needs, and it still asks for them again and again.
Could you look closely at the syslog (Alt+F4, or Alt+F2 and
/var/log/syslog) for firmware related issues?
You can also edit (using nano) /bin/check-missing-firmware and add a
"set -x" at the beginning of the script. This will trace its execution
in the syslog.
Cheers,
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#492878: lenny installer -dosen't detect Broadcom ethernet adapter
I type here just what is going on for bnx2 and I will not put here messages for another hw that needs firmwaremessages, qla2xxx 11:04:56 kernel: Broadcom Nextreme II Gigabit Ethernet Driver bnx2 v1.7.4 (Feburary 18, 2008) 11:04:56 kernel: bnx2: Can't load firmware file bnx2-06-4.0.5.fw 11:04:56 kernel: bnx2: probe of :02:03.0 failed with error -2 11:04:56 kernel: bnx2: Can't load firmware file bnx2-06-4.0.5.fw 11:04:56 kernel: bnx2: probe of :02:04.0 11:06:13 check-missing-firmware: missing firmware files (ql2400_fw.bin bnx2-06-4.0.5.fw) for qlaxxx bnx2 11:13:50 kernel: FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! (repeated cca 10x in the same second) here the show begins: 11:13:51 main-menu[1481]: (process:5851): mount: mounting /dev/sda on /media failed: Invalid argument the same for sdb, sdc then FAT comply 3x again, and then it tryes to mount cciss/c0d0p2 (the internal HP raid E200) and fails with "attempt to access beyond end of device" then FAT again ... another attempts to mount all the backage found in /dev... It seems for me, that it simply fails to mount the USB pendrive. Anyhow, the partition of course resides on /dev/sda1, not on /dev/sda! So I don't wonder it fails. Peter (Please keep the bug CC'ed) On Wed, Jul 30, 2008 at 09:30:40AM +0200, Peter Tuhársky wrote: The installer should at least prompted you to supply a .fw firmware file. Did it do this? Well, I tested daily build from 20080729, and yes, the installer prompts for these files. However, I can't figure out, how could I give it to him. I have put them on the root of usb pendrive, they are exactly the files that he needs, and it still asks for them again and again. Could you look closely at the syslog (Alt+F4, or Alt+F2 and /var/log/syslog) for firmware related issues? You can also edit (using nano) /bin/check-missing-firmware and add a "set -x" at the beginning of the script. This will trace its execution in the syslog. Cheers, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#492862: marked as done (grub-installer: Fails on virtio disks)
Your message dated Wed, 30 Jul 2008 19:05:03 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#492862: grub-installer: Fails on virtio disks has caused the Debian Bug report #492862, regarding grub-installer: Fails on virtio disks 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 [EMAIL PROTECTED] immediately.) -- 492862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492862 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: grub-installer Severity: normal grub-installer currently fails on virtio disks (/dev/vd[a-z]) as grub does not list virtio disks in device.map. One quick test showed that GRUB 2 was able to cope with these devices nicely. The attached patch makes grub-installer default to GRUB 2 when boot is on virtio disks. This is pretty hacky, but worked fine in my tests. Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- commit 30b8e4591943a2e2a3b9d73687ea40281575241e Author: Jérémy Bobbio <[EMAIL PROTECTED]> Date: Tue Jul 29 11:49:34 2008 +0200 Use GRUB 2 by default on virtio disks diff --git a/packages/arch/i386/grub-installer/debian/changelog b/packages/arch/i386/grub-installer/debian/changelog index b1456f3..537001e 100644 --- a/packages/arch/i386/grub-installer/debian/changelog +++ b/packages/arch/i386/grub-installer/debian/changelog @@ -1,3 +1,10 @@ +grub-installer (1.33) UNRELEASED; urgency=low + + [ Jérémy Bobbio ] + * Use GRUB 2 by default on virtio disks. + + -- Jérémy Bobbio <[EMAIL PROTECTED]> Tue, 29 Jul 2008 11:46:30 +0200 + grub-installer (1.32) unstable; urgency=low [ Updated translations ] diff --git a/packages/arch/i386/grub-installer/grub-installer b/packages/arch/i386/grub-installer/grub-installer index 2b16484..d5eaafd 100755 --- a/packages/arch/i386/grub-installer/grub-installer +++ b/packages/arch/i386/grub-installer/grub-installer @@ -258,9 +258,14 @@ case $prefix in /dev/mapper) disc_offered_devfs="$bootfs" ;; -/dev/[hsv]d[a-z]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]|/dev/ida/c[0-9]d[0-9]) +/dev/[hs]d[a-z]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]|/dev/ida/c[0-9]d[0-9]) disc_offered_devfs="$prefix" ;; +/dev/vd[a-z]) + disc_offered_devfs="$prefix" + # Use GRUB 2 by default on virtio disks + db_set grub-installer/grub2_instead_of_grub_legacy true + ;; *) disc_offered_devfs=$(echo "$bootfs_devfs" | sed "s:\(.*\)/.*:\1/disc:") ;; signature.asc Description: Digital signature --- End Message --- --- Begin Message --- On Tue, Jul 29, 2008 at 11:59:06PM +0200, Robert Millan wrote: > On Tue, Jul 29, 2008 at 03:53:46PM +0200, Jérémy Bobbio wrote: > > > > grub-installer currently fails on virtio disks (/dev/vd[a-z]) as grub > > does not list virtio disks in device.map. > > Does this address the problem? > > grub (0.97-42) unstable; urgency=high > [...] > * patches/use_grub-probe_in_grub-install.diff: Use grub-mkdevicemap when > device.map needs to be regenerated (this brings in Virtio support, and > probably others). > (Closes: #491745) > > (pending unblock) Yes it does. :) -41 was in testing and so installed by default. Manually installing grub 0.97-42 in the chroot before running grub-installer worked without any trouble. Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature --- End Message ---
Processed: reassign 492937 to apt-setup
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.34 > reassign 492937 apt-setup Bug#492937: apt-setup: inconsistent path handling for 'security' and 'volatile' services Bug reassigned from package `apt-setup' to `apt-setup'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
reassign 492937 to apt-setup
# Automatically generated email from bts, devscripts version 2.10.34 reassign 492937 apt-setup -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: d-i preseed/late_command and interactive scripts.
On Tuesday 29 July 2008 22:56, Jérémy Bobbio wrote: > On Tue, Jul 29, 2008 at 07:07:12PM +, Ryan Braun [ADS] wrote: > > On Tuesday 29 July 2008 17:52, Ryan Braun [ADS] wrote: > > > I have a dialog driven configuration script I want to use to configure > > > several aspects of the install. The preseed works for the majority of > > > the install, all the apps get installed, then it doesn't seem to want > > > to run the dialog script. > > > > I finally got some feedback from the script, the error I'm getting is > > > > Error opening terminal: bterm > > You need to use debconf if you want to do user interactions inside > the debian-installer. Other means would just be plain hacks. > > Have a look at debian-installer scripts and to the debconf-devel(7) > man page for more details on how to use debconf. I think for this project, I'll end up putting together a nice menu system with isolinux configs, passing the hostname="whoever" kernel argument. Then I'll just have my config script pull the /target/etc/hostname value to figure out how to setup the workstations. Thanks for the feedback! Ryan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
reassign 492937 to apt-setup
# Automatically generated email from bts, devscripts version 2.10.29~bpo40+1 reassign 492937 apt-setup -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#492899: setting package to partman-crypto-loop partman-crypto partman-crypto-dm, tagging 492899
# Automatically generated email from bts, devscripts version 2.10.33 # via tagpending # # partman-crypto (34) UNRELEASED; urgency=low # # * Divide the progress bar in 65536 parts when erasing disk data. #The previous setting (100) was a bit low to allow reactive cancellation. #(Closes: #492899) # package partman-crypto-loop partman-crypto partman-crypto-dm tags 492899 + pending -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: setting package to partman-crypto-loop partman-crypto partman-crypto-dm, tagging 492899
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.33 > # via tagpending > # > # partman-crypto (34) UNRELEASED; urgency=low > # > # * Divide the progress bar in 65536 parts when erasing disk data. > #The previous setting (100) was a bit low to allow reactive cancellation. > #(Closes: #492899) > # > package partman-crypto-loop partman-crypto partman-crypto-dm Ignoring bugs not assigned to: partman-crypto partman-crypto-loop partman-crypto-dm > tags 492899 + pending Bug#492899: partman-crypto: cancel button unusable on "Erasing data" screen There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 492937 to apt-setup
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.29~bpo40+1 > reassign 492937 apt-setup Bug#492937: apt-setup: inconsistent path handling for 'security' and 'volatile' services Bug reassigned from package `debian-installer' to `apt-setup'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#489544: installation-reports
On Wed, Jul 30, 2008 at 12:47:02AM -0700, David L. Emerson wrote: > I've just finished a similar installation with the Lenny beta 2 > installer (encrypted lvm on bootable usb flash drive) Thanks. I would have been more happy if you would have used a daily build, but it's great nevertheless. > re Problem 3: STILL A BIG PROBLEM. Here are the boot messages: > > Uncompressing Linux... Ok, booting the kernel. > Loading, please wait... > Volume group "socrates" not found > Setting up cryptographic volume sda2_crypt (based on /dev/sda2) > cryptsetup: Source device /dev/sda2 not found > > [... wait about 5 seconds ...] > > sd 0:0:0:0: [sda] Assuming drive cache: write through > sd 0:0:0:0: [sda] Assuming drive cache: write through > > [... forehead -> desk ...] > > [... wait about a minute, then it drops to busybox because > the /dev/mapper/socrates-root_vol does not exist ...] > > so, it looks like I will have to manually reroll the initramfs again. If > you want me to test again with a later version, I'll try and figure out > a way to do that :) Could you give me the installed version of the initramfs-tools and cryptsetup packages? I have seen similar issues being fixed in recent version of those packages, and I am not sure if they have migrated to Lenny yet. (The development version of debian-installer installs testing by default.) Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#492899: partman-crypto: cancel button unusable on "Erasing data" screen
On Tue, Jul 29, 2008 at 06:03:34PM -0600, dann frazier wrote: > > What size is the partition being erased? > > ~73G blockdev-wipe writes random data in blocks of 65536 bytes. So we have (70 * 2^30) / 2^16 = 70 * 2^14 blocks to write. With the progress bar divided into 100 steps, this means that we have one update every 11468 written blocks. Does not really sound reactive to me! :) > > After having a look at the source code, it's possible that, for a very > > large partition, the progress would be updated rarely enough to give you > > the impression that the Cancel button do not work, as its result would > > not be checked often enough. > > That sounds plausible, and after adding some debug statments, I > believe that your theory is correct. A kill does occur after the next > iteration of the while loop after I click cancel. There's just a long > time between iterations. > […] > Consider that a user might click cancel with no immediate result, then > a minute or two later they are moved along to the next step (creating > a password for the volume). They maybe led to believe that the wipe > completed successfully, even though their cancel attempt did > eventually succeed and cause the rest of the disk to not be cleared. Let's make it more reactive then and leave the current code as is, IMHO. > > A possible fix in that case would be to divide the progress into more > > steps than the current 100. But a deeper investigation would be > > required before that. > > I wonder if there's a way to split the cancel checking and the > progress checking? […] It might be, but I am not inclined to do this kind of changes that tend to breaks in very subtle way just before Lenny. Dividing the progress bar in 65536 parts will give us an abitility to cancel it every 1114112 written bytes, and should make it reactive enough. Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#492878: lenny installer -dosen't detect Broadcom ethernet adapter
(Please keep the bug CC'ed) On Wed, Jul 30, 2008 at 09:30:40AM +0200, Peter Tuhársky wrote: > >The installer should at least prompted you to supply a .fw firmware file. > >Did it do this? > > Well, I tested daily build from 20080729, and yes, the installer prompts > for these files. However, I can't figure out, how could I give it to > him. I have put them on the root of usb pendrive, they are exactly the > files that he needs, and it still asks for them again and again. Could you look closely at the syslog (Alt+F4, or Alt+F2 and /var/log/syslog) for firmware related issues? You can also edit (using nano) /bin/check-missing-firmware and add a "set -x" at the beginning of the script. This will trace its execution in the syslog. Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Re: Bug#492878: lenny installer -dosen't detect Broadcom ethernet adapter
And as I'm looking at 492246, I also see the message "FAT: utf8 is not a recommended IO charset for FAT filesystem, filesystem will be case sensitive!" I don't know of whether THIS is causing some problems. I can easily mount the USB pendrive manually however, by ordinary mkdir /media/usb mount -t vfat /dev/sda1 /media/usb However, it dosen't matter, whether the USB is mounted or not, when installer is trying to load the firmware files. Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#489544: installation-reports
I've just finished a similar installation with the Lenny beta 2 installer (encrypted lvm on bootable usb flash drive) re Problem 1: I was able to delete the swap partition with your advise: deleting both partitions, then the volumes, then making one volume. Kinda cumbersome ... I guess it would be nice if there was a prompt about swap vs. no swap, but it's also nice not to bother most people with it. re Problem 2: this time I didn't dd my drive ahead of time, I just let the installer do its thing :P re Problem 3: STILL A BIG PROBLEM. Here are the boot messages: Uncompressing Linux... Ok, booting the kernel. Loading, please wait... Volume group "socrates" not found Setting up cryptographic volume sda2_crypt (based on /dev/sda2) cryptsetup: Source device /dev/sda2 not found [... wait about 5 seconds ...] sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] Assuming drive cache: write through [... forehead -> desk ...] [... wait about a minute, then it drops to busybox because the /dev/mapper/socrates-root_vol does not exist ...] so, it looks like I will have to manually reroll the initramfs again. If you want me to test again with a later version, I'll try and figure out a way to do that :) ~David. On Monday 28 July 2008 9:50 am, Jérémy Bobbio wrote: > On Sun, Jul 06, 2008 at 01:21:00PM -0700, David L. Emerson wrote: > > Image version: debian-40r3-i386-netinst.iso > > […] > > > > This computer supports booting from USB, so I decided to install debian > > on a USB Flash drive. I wanted an encrypted root partition. > > > > PROBLEM 1. I first tried the "automatic" encrypted LVM setup. It > > insisted upon making a swap partition, and I was unable to delete that > > partition. Of course I don't want a swap partition on a flash based > > drive. I ultimately had to back up several steps and do a manual setup. > > The automatic encrypted LVM setup create the swap partition as a Logical > Volume. The easiest (but not obvious) way to get rid of it would have > been to: > * go to "Configure the Logical Volume Manager", > * remove both Logical Volumes (swap_1 and root), > * create a new Logical Volume (root), > * apply those changes, > * configure the newly created Logical Volume (root) as / > > We could probably manage to detect that we are partitioning a Solid > State Device, and skip the creation of a swap partition, but this would > require a fair amount of changes in partman. I doubt anyone will be > working on that in the d-i team, but patches are more than welcome. > > > PROBLEM 2. Before I started the install, I used dd if=/dev/urandom > > of=/dev/sda to write random data to the drive, which makes cracking an > > encrypted partition/drive much more difficult. However, the debian > > installer insisted on writing (zeros?) to the to-be-encrypted partition > > before formatting. This was very time consuming, wasteful/redundant, > > and perhaps a security liability as well. In fact, the installer did > > this several times due to problem 1 ;) > > I should be able to skip that writing since I already did it myself. > > The installer is not writing zeros. It is actually doing a similar > process than the one you did by yourself! :) > > It can be avoided though when using manual partitioning, by switching > "Erase data" to "no" while configuring the partition used as "physical > volume for encryption". > > > PROBLEM 3. System would not boot!! . > > > > It brought up the grub menu just fine, and began loading the kernel and > > initramfs. The problem occured when it tried to configure lvm > > (/usr/share/initramfs-tools/scripts/local-top/lvm) -- the kernel had > > not yet detected the presence of the USB Flash drive! Thus the call to > > activate_vg "$ROOT" was doomed to failure, since udev had not yet > > discovered the root device. A few seconds after the failure messages, > > udev discovered the device -- udev had "settled" before running > > local-top, but the USB event came later. > > […] > > AFAIK, a lot of related issues have been fixed for Lenny. If you could > give it a try, it would be great. > > Cheers, > -- > Jérémy Bobbio .''`. > [EMAIL PROTECTED] : :Ⓐ : # apt-get install anarchism >`. `'` > `- > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#492878: lenny installer -dosen't detect Broadcom ethernet adapter
The installer should at least prompted you to supply a .fw firmware file. Did it do this? Well, I tested daily build from 20080729, and yes, the installer prompts for these files. However, I can't figure out, how could I give it to him. I have put them on the root of usb pendrive, they are exactly the files that he needs, and it still asks for them again and again. Cheers Vince -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: late_command is in never-never-land?
On Wed, Jul 23, 2008 at 09:26:50PM +0300, Shachar Or wrote: > On Wednesday 23 July 2008 01:37, Shachar Or wrote: ... > I was given advice in #debian-boot to use in-target for this purpose, so I've > solved it like this: > > d-i preseed/late_command string wget -q -O - > http://ahava/d-i/etch/late_command.sh > /target/root/late_command.sh && chmod > u+x /target/root/late_command.sh && in-target '/root/late_command.sh' > >> /var/log/syslog You might want to try this: d-i preseed/late_command string preseed-fetch late_command.sh /target/root/late_command.sh && in-target 'sh /root/late_command.sh' preseed-fetch has the advantage that it gets stuff from wherever you got the preseed files, so you can write scripts that are portable from a preseed setup on your web server, to a copy of the same on an USB stick, say. The use of sh id just to make it more concise than doing the chmod, but that's just a personal preference. Have a look at http://hands.com/d-i/ for more examples of preseed-fetch, and lots of scripting stuff. 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
