Bug#526542: initramfs-tools: fails if swap is encrypted and LVM is used
Package: initramfs-tools Version: 0.92o Severity: important Use LVM and have a swap an encrypted partition. Then suspend to disk. Then try to resume now all those nasty no sed, no tr errors during boot (before the passphrase prompt) will kick into effect, and your system will boot normally, instead of resuming. Also, there is a useless prompt where the computer asks at every boot to identify the swap, even though the correct path in the LVM is on the prompt (but says that that's not good). Once the sed and tr are in the generated iniramfs, all is OK. -- Package-specific info: -- /proc/cmdline root=/dev/hda2 ro quiet -- /proc/filesystems ext3 -- lsmod Module Size Used by i915 25856 2 drm66120 3 i915 binfmt_misc 7336 1 ppdev 6500 0 parport_pc 27576 0 lp 8140 0 parport30964 3 ppdev,parport_pc,lp acpi_cpufreq6636 1 cpufreq_conservative 5896 0 cpufreq_userspace 3204 0 cpufreq_stats 3844 0 cpufreq_powersave 1824 0 microcode 8336 0 nfsd 187644 17 auth_rpcgss31048 1 nfsd exportfs4000 1 nfsd nfs 217432 0 lockd 54040 2 nfsd,nfs nfs_acl 2880 2 nfsd,nfs sunrpc163156 13 nfsd,auth_rpcgss,nfs,lockd,nfs_acl ipv6 210372 22 loop 13164 0 snd_hda_intel 323540 1 snd_pcm_oss32096 0 snd_mixer_oss 12256 1 snd_pcm_oss snd_pcm62788 2 snd_hda_intel,snd_pcm_oss arc41824 2 ecb 2624 2 snd_seq_dummy 2660 0 snd_seq_oss24636 0 iwlagn 76676 0 snd_seq_midi5760 0 iwlcore74724 1 iwlagn pcmcia 29940 0 snd_rawmidi18688 1 snd_seq_midi snd_seq_midi_event 6368 2 snd_seq_oss,snd_seq_midi psmouse32016 0 led_class 3876 1 iwlcore rtc_cmos8704 0 snd_seq41576 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event firmware_class 6888 3 microcode,iwlagn,pcmcia rtc_core 13948 1 rtc_cmos i2c_i8018112 0 mac80211 114864 2 iwlagn,iwlcore rtc_lib 2848 1 rtc_core yenta_socket 20780 1 rsrc_nonstatic 9344 1 yenta_socket serio_raw 4804 0 i2c_core 20564 1 i2c_i801 iTCO_wdt9572 0 pcmcia_core30484 3 pcmcia,yenta_socket,rsrc_nonstatic snd_timer 17992 2 snd_pcm,snd_seq cfg80211 21320 3 iwlagn,iwlcore,mac80211 snd_seq_device 6412 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq video 16240 0 snd45688 11 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device output 2784 1 video intel_agp 22460 1 soundcore 6440 1 snd joydev 8672 0 wmi 6408 0 snd_page_alloc 7336 2 snd_hda_intel,snd_pcm battery10116 0 agpgart29780 3 drm,intel_agp button 6032 0 ac 4132 0 evdev 8324 9 dcdbas 6336 0 ext3 105128 5 jbd40820 1 ext3 mbcache 7396 1 ext3 sha256_generic 11392 0 cbc 3264 1 dm_crypt 11268 1 crypto_blkcipher 15204 4 ecb,cbc,dm_crypt dm_mirror 15936 0 dm_log 8548 1 dm_mirror dm_snapshot15332 0 dm_mod 46772 15 dm_crypt,dm_mirror,dm_log,dm_snapshot usbhid 23364 0 hid33868 1 usbhid ide_disk 10464 4 ata_piix 15460 0 ata_generic 4580 0 libata143788 2 ata_piix,ata_generic scsi_mod 129948 1 libata dock8368 1 libata piix5800 3 atkbd 15476 0 firewire_ohci 18020 0 firewire_core 32096 1 firewire_ohci crc_itu_t 2080 1 firewire_core ide_pci_generic 3588 0 ide_core 84548 3 ide_disk,piix,ide_pci_generic ehci_hcd 29292 0 tg3 104836 0 libphy 17248 1 tg3 uhci_hcd 19088 0 usbcore 118392 4 usbhid,ehci_hcd,uhci_hcd thermal15132 0 processor 33420 4 acpi_cpufreq,thermal fan 4324 0 thermal_sys 9416 4 video,thermal,processor,fan -- /etc/kernel-img.conf # Kernel image management overrides # See
Bug#502955: debian-installer: essid cannot be chosen
Package: debian-installer Severity: normal There are multiple wireless spots around my house. Debian defaults to an unsecured network(see later how I discovered this), but that network needs a web-based login (only available to paying customers), so it doesn't actually work. My own wireless router works, and I have the key for it, but the installer never actually asks for the essid, so I don't have a chance to select it. What is worse, is that being a sort-of-expert, I tried to get around this using a console+iwconfig combo, but iwconfig was not available. So, I had to do a very minimial install, then boot into bash, then set the correct essidkey using iwconfig and then do apt-get It worked in the end, but under /etc/network/interfaces debian of course put the essid of the unsecured network (just as I suspected). This behaviour is not correct, as I believe: 1) Wireless is getting very widespread 2) So most normal people will try to install debian through wifi 3) And most people will live next to other people, who also have wifi 4) So it is essential to be able to select the correct essid -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502912: debian-installer: mounting fat32 system broken, needs modprobe vfat first
Package: debian-installer Severity: normal I needed to have ipw2100 firmware, so I switched to console, and typed mkdir /mnt/disk then mount /dev/sda1 /mnt/disk but it gave a really impossible-to-understand error, nothing to do with vfat. I realised that all it needed was modprobe vfat. I have USB keys formatted to fat32 due to windows-compatibility. As a side-note, the directory /lib/firmware does *not* exist, and there is no textual indication where the firmware should be placed. I just guessed it had to be at /lib/firmware. The /lib/firmware should exist, and the interface should make it clear that if the firmware is manually installed, it should be placed there. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26 (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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502912: closed by Frans Pop [EMAIL PROTECTED] (reply to [EMAIL PROTECTED]) (Re: Bug#502912: debian-installer: mounting fat32 system broken, needs modprobe vfat first)
Hi, I actually used a daily lenny snapshot for installation. I saw the microcode-related dialog, but honestly, I didn't quite understand what it was trying to say. Plugging in the USB key with the firmware on it and clicking continue didn't seem to help, the installer (seemed to) hang (I think it tried to mount the non-existent floppy (looking at 'ps xa') and that takes a lot to time-out). The dialog was all too new to me, and I had no clue what it was saying (it wasn't the english, neither my stupidity in Linux -- the text is definitely badly written). So, I re-booted, and when faced the message, I tried the good-old-console. And that is why I wrote the bug report. The bug I think is still somewhat relevant, though next time, I will try to do something useful with that dialog. Until then, maybe a re-wording of that dialog would help: the dialog did not indicate it will search through all pulugged-in mediums, though according to what you said, that is what I suspect it would have done had I given it time. Maybe a one-liner to indicate this would be nice to have. Bests, Mate Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the debian-installer package: #502912: debian-installer: mounting fat32 system broken, needs modprobe vfat first It has been closed by Frans Pop [EMAIL PROTECTED] (reply to [EMAIL PROTECTED]). Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Frans Pop [EMAIL PROTECTED] (reply to [EMAIL PROTECTED]) by replying to this email. Subject: Re: Bug#502912: debian-installer: mounting fat32 system broken, needs modprobe vfat first From: Frans Pop [EMAIL PROTECTED] Date: Mon, 20 Oct 2008 23:03:17 +0200 To: Mate Soos [EMAIL PROTECTED], [EMAIL PROTECTED] To: Mate Soos [EMAIL PROTECTED], [EMAIL PROTECTED] On Monday 20 October 2008, Mate Soos wrote: I needed to have ipw2100 firmware, so I switched to console, and typed mkdir /mnt/disk then mount /dev/sda1 /mnt/disk Current versions of D-I (daily built images and RC1 when it is released) support loading firmware in a more structured way. See the installation guide [1] for details. [1] http://d-i.alioth.debian.org/manual/en.i386/ch02s02.html http://d-i.alioth.debian.org/manual/en.i386/ch06s04.html Subject: debian-installer: mounting fat32 system broken, needs modprobe vfat first From: Mate Soos [EMAIL PROTECTED] Date: Mon, 20 Oct 2008 22:02:22 +0200 To: Debian Bug Tracking System [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Package: debian-installer Severity: normal I needed to have ipw2100 firmware, so I switched to console, and typed mkdir /mnt/disk then mount /dev/sda1 /mnt/disk but it gave a really impossible-to-understand error, nothing to do with vfat. I realised that all it needed was modprobe vfat. I have USB keys formatted to fat32 due to windows-compatibility. As a side-note, the directory /lib/firmware does *not* exist, and there is no textual indication where the firmware should be placed. I just guessed it had to be at /lib/firmware. The /lib/firmware should exist, and the interface should make it clear that if the firmware is manually installed, it should be placed there. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26 (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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
