Bug#686468: marked as done ([wheezy] [amd64] [daily 20120831] Fujitsu Lifebook AH532 installation report)
Your message dated Sun, 2 Sep 2012 08:07:07 +0200 with message-id 20120902060707.gh21...@mykerinos.kheops.frmug.org and subject line Re: Bug#686468: [wheezy] [amd64] [daily 20120831] Fujitsu Lifebook AH532 installation report has caused the Debian Bug report #686468, regarding [wheezy] [amd64] [daily 20120831] Fujitsu Lifebook AH532 installation report 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.) -- 686468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Boot method: netboot mini.iso (isohybrid image) booted from a USB flash drive with the (non-free) firmware debs needed for this system copied onto the firmware partition of the mini.iso Image version: http://d-i.debian.org/daily-images/amd64/daily/netboot/mini.iso dated 31-Aug-2012 00:09 Date: 2012-08-31 Machine: Fujitsu Lifebook AH532 Processor: Core i5-3210M Memory: 4GB Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09) Subsystem: Fujitsu Limited. Device [10cf:16bf] Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) Subsystem: Fujitsu Limited. Device [10cf:16c2] Kernel driver in use: i915 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) Subsystem: Fujitsu Limited. Device [10cf:16ee] Kernel driver in use: xhci_hcd 00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) Subsystem: Fujitsu Limited. Device [10cf:16ea] 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) Subsystem: Fujitsu Limited. Device [10cf:16e8] Kernel driver in use: ehci_hcd 00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04) Subsystem: Fujitsu Limited. Device [10cf:1757] Kernel driver in use: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4) Kernel driver in use: pcieport 00:1c.2 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 [8086:1e14] (rev c4) Kernel driver in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 [8086:1e18] (rev c4) Kernel driver in use: pcieport 00:1c.5 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 6 [8086:1e1a] (rev c4) Kernel driver in use: pcieport 00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04) Subsystem: Fujitsu Limited. Device [10cf:16e8] Kernel driver in use: ehci_hcd 00:1f.0 ISA bridge [0601]: Intel Corporation HM76 Express Chipset LPC Controller [8086:1e59] (rev 04) Subsystem: Fujitsu Limited. Device [10cf:16e0] 00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04) Subsystem: Fujitsu Limited. Device [10cf:16e2] Kernel driver in use: ahci 00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller [8086:1e22] (rev 04) Subsystem: Fujitsu Limited. Device [10cf:16e6] 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 07) Subsystem: Fujitsu Limited. Device [10cf:175a] Kernel driver in use: r8169 08:00.0 Network controller [0280]: Intel Corporation Centrino Wireless-N 2230 [8086:0887] (rev c4) Subsystem: Intel Corporation Centrino Wireless-N 2230 BGN [8086:4062] Kernel driver in use: iwlwifi 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: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone
Finalizing beta2: please dak copy-installer, urgent d-i, build images
Hi ftpmasters, release team, cd team, please respectively, do: - dak copy-installer - urgent d-i - start building installation images (I think it needs at least a dinstall + a mirror pulse though); putting them into a “dot-dir” for the time being would be nice. Mraw, KiBi. signature.asc Description: Digital signature
Re: EFI approach and patches
Nice work Steve, And just in time for me. I bought a UEFI system second hand and got it from mail on Friday. Its got a ASUS Sabertooth 990FX board with the newest bios. I installed with your third version of the installer and it worked. Though still having trouble with double booting to win7 and Asus bootmgr. It boots win7 loader, but doesn't find the grub one. I can get it to load grub from my debian install when I efi-boot with your cd and load the config file to that grub from hd. Well getting off topic so finishing. PS of to find more info on repairing the grub efi boot -- 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/1346588085.5891.9.ca...@birdfarm0.kicks-ass.net
Bug#686502: pxz produces archives broken for busybox's unxz
package: pxz version: 4.999.9~beta+git537418b-1 severity: important affects: busybox x-debbugs-cc: debian-boot@lists.debian.org,xz-ut...@packages.debian.org,jn...@users.sourceforge.net Hi, pxz (somtimes) produces archives broken for busybox's unxz, while they decompress fine with unxz from xz-utils packges. I noticed when trying to uncompress pxz compressed initramfs files, while this is an universal way to reproduce it: (this is sid, and busybox from squeeze behaves the same.) # get some big archive: ~/t$ apt-get source typo3 Reading package lists... Done Building dependency tree Reading state information... Done Picking 'typo3-src' as source package instead of 'typo3' NOTICE: 'typo3-src' packaging is maintained in the 'Git' version control system at: git://github.com/sir-gawain/debian-typo3.git Skipping already downloaded file 'typo3-src_4.5.19+dfsg1-1.dsc' Skipping already downloaded file 'typo3-src_4.5.19+dfsg1.orig.tar.gz' Skipping already downloaded file 'typo3-src_4.5.19+dfsg1-1.debian.tar.gz' Need to get 0 B of source archives. Skipping unpack of already unpacked source in typo3-src-4.5.19+dfsg1 # preserve it ~/t$ cp typo3-src_4.5.19+dfsg1.orig.tar.gz typo3-src_4.5.19+dfsg1.orig.tar.gz.orig # now show that busybox unxz chokes: ~/t$ gunzip typo3-src_4.5.19+dfsg1.orig.tar.gz ~/t$ pxz -z typo3-src_4.5.19+dfsg1.orig.tar ~/t$ busybox unxz typo3-src_4.5.19+dfsg1.orig.tar.xz ~/t$ tar tf typo3-src_4.5.19+dfsg1.orig.tar 1/dev/null tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now # cleanup ~/t$ rm typo3-src_4.5.19+dfsg1.orig.tar ~/t$ cp typo3-src_4.5.19+dfsg1.orig.tar.gz.orig typo3-src_4.5.19+dfsg1.orig.tar.gz # show that unxz has no problems ~/t$ gunzip typo3-src_4.5.19+dfsg1.orig.tar.gz ~/t$ pxz -z typo3-src_4.5.19+dfsg1.orig.tar ~/t$ unxz typo3-src_4.5.19+dfsg1.orig.tar.xz ~/t$ tar tf typo3-src_4.5.19+dfsg1.orig.tar 1/dev/null ~/t$ echo $? 0 Any help with this is appreciated. cheers, Holger -- 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/201209021518.41705.hol...@layer-acht.org
Re: Bug#686502: pxz produces archives broken for busybox's unxz
Hi Bastian, On Sonntag, 2. September 2012, Bastian Blank wrote: On Sun, Sep 02, 2012 at 03:18:40PM +0200, Holger Levsen wrote: ~/t$ busybox unxz typo3-src_4.5.19+dfsg1.orig.tar.xz ~/t$ tar tf typo3-src_4.5.19+dfsg1.orig.tar 1/dev/null tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now Where does busybox choke here? I only see tar choking on the result of the decompression. What do you find in the file? understandable, my instructions to reproduce it hide the problem a bit ;) tar fails, because busybox unxz fails to decompress correctly (as can be seen in the filesize) despite exiting with exit code 0: ~/t$ gunzip typo3-src_4.5.19+dfsg1.orig.tar.gz ~/t$ ls -l typo3-src_4.5.19+dfsg1.orig.tar -rw-r--r-- 1 me me 51845120 Aug 18 05:36 typo3-src_4.5.19+dfsg1.orig.tar ~/t$ pxz -z typo3-src_4.5.19+dfsg1.orig.tar ~/t$ busybox unxz typo3-src_4.5.19+dfsg1.orig.tar.xz ~/t$ echo $? 0 ~/t$ ls -l typo3-src_4.5.19+dfsg1.orig.tar -rw-r--r-- 1 me me 25169920 Sep 2 14:32 typo3-src_4.5.19+dfsg1.orig.tar cheers, Holger -- 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/201209021634.44021.hol...@layer-acht.org
Re: Amending task-xfce-desktop (was: Bug#686468: [wheezy] [amd64] [daily 20120831] Fujitsu Lifebook AH532 installation report)
Karsten Merker wrote: A possible solution would be to add a recommends on gstreamer0.10-alsa to task-xfce-desktop, so that it gets pulled in during the system installation while not fiddling with the xfce4-mixer dependencies which are correct from the package point of view. What do you think about that? I agree, except I don't think the dependencies are correct. Fixing this in tasksel is just a workaround. -- see shy jo signature.asc Description: Digital signature
Re: EFI approach and patches
Mika Rastas wrote: Nice work Steve, *grin* Thanks! And just in time for me. I bought a UEFI system second hand and got it from mail on Friday. Its got a ASUS Sabertooth 990FX board with the newest bios. I installed with your third version of the installer and it worked. Awesome. Though still having trouble with double booting to win7 and Asus bootmgr. It boots win7 loader, but doesn't find the grub one. I can get it to load grub from my debian install when I efi-boot with your cd and load the config file to that grub from hd. Well getting off topic so finishing. What does efibootmgr say once you've got your system booted into Debian? -- Steve McIntyre, Cambridge, UK.st...@einval.com Google-bait: http://www.debian.org/CD/free-linux-cd Debian does NOT ship free CDs. Please do NOT contact the mailing lists asking us to send them to you. -- 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/e1t8cg8-0007lx...@mail.einval.com
Re: pxz produces archives broken for busybox's unxz
Hi Holger, Holger Levsen wrote: pxz (somtimes) produces archives broken for busybox's unxz, while they decompress fine with unxz from xz-utils packges. I noticed when trying to uncompress pxz compressed initramfs files, while this is an universal way to reproduce it: Thanks! Could you please attach such an example archive, or upload it somewhere and send a link if it is too large? Lazily, Jonathan -- 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/20120902195429.GB2187@mannheim-rule.local
Re: EFI approach and patches
The debian entry that was made during install broke eighter on windows install or Asus boot menu just wouldn't get it running. I wasn't sure could I use efi recovery boot selection to install grub again automatically? Does it work so or is it just for manual recovery with the system loaded as efi and using console to setup grub again? Anyhow I got it working now all together. Grub2-efi is loading at first and then I can chainload win7 bootloader. The installer and grub probe didn't find the win7 automatically though. Now efibootmgrs got the debian entry that was generated at install as 2 but it didn't work after windows install. I got it working after making a new entry for Uefi and installing grub again with these instructions. http://forums.debian.net/viewtopic.php?f=16t=81120 The output now: BootCurrent: Timeout: 3 seconds BootOrder: ,0002,0003,0005,0001 Boot* Debian GNU/Linux Boot0001 Hard Drive Boot0002* debian Boot0003* Windows Boot Manager Boot0005* CD/DVD Drive I also read somewhere that I might run into trouble again when Win7 updates itself. So I think I will keep your efi install cd near and use it for recovering again if I run into trouble. :) -- Mika On Sun, Sep 2, 2012 at 7:05 PM, Steve McIntyre st...@einval.com wrote: Mika Rastas wrote: Nice work Steve, *grin* Thanks! And just in time for me. I bought a UEFI system second hand and got it from mail on Friday. Its got a ASUS Sabertooth 990FX board with the newest bios. I installed with your third version of the installer and it worked. Awesome. Though still having trouble with double booting to win7 and Asus bootmgr. It boots win7 loader, but doesn't find the grub one. I can get it to load grub from my debian install when I efi-boot with your cd and load the config file to that grub from hd. Well getting off topic so finishing. What does efibootmgr say once you've got your system booted into Debian? -- Steve McIntyre, Cambridge, UK. st...@einval.com Google-bait: http://www.debian.org/CD/free-linux-cd Debian does NOT ship free CDs. Please do NOT contact the mailing lists asking us to send them to you.
Re: EFI approach and patches
Dough of course the verbose output is nicer.
/home# efibootmgr -v
BootCurrent:
Timeout: 3 seconds
BootOrder: ,0002,0003,0005,0001
Boot* Debian GNU/Linux
HD(3,613a4800,f4000,ea481e18-9503-404e-84ed-088f005a3ee1)File(\EFI\debian\grubx64.efi)
Boot0001 Hard DriveBIOS(2,0,00)P0: WDC WD15EARX-00PASB0 .
Boot0002* debian
HD(3,613a4800,f4000,ea481e18-9503-404e-84ed-088f005a3ee1)File(\EFI\debian\grubx64.efi)
Boot0003* Windows Boot Manager
HD(3,613a4800,f4000,ea481e18-9503-404e-84ed-088f005a3ee1)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...o....
Boot0005* CD/DVD DriveBIOS(3,0,00)P1: ASUSDRW-24B5ST.
/home#
So I see the entry has been right all along, as it is the same as the one I
created by hand. Somehow fiddling with win7 broke the ESD then.
-- Mika
On Mon, Sep 3, 2012 at 12:16 AM, Mika mika.ras...@gmail.com wrote:
The debian entry that was made during install broke eighter on windows
install or Asus boot menu just wouldn't get it running. I wasn't sure could
I use efi recovery boot selection to install grub again automatically? Does
it work so or is it just for manual recovery with the system loaded as efi
and using console to setup grub again?
Anyhow I got it working now all together. Grub2-efi is loading at first
and then I can chainload win7 bootloader. The installer and grub probe
didn't find the win7 automatically though.
Now efibootmgrs got the debian entry that was generated at install as 2
but it didn't work after windows install. I got it working after making a
new entry for Uefi and installing grub again with these instructions.
http://forums.debian.net/viewtopic.php?f=16t=81120
The output now:
BootCurrent:
Timeout: 3 seconds
BootOrder: ,0002,0003,0005,0001
Boot* Debian GNU/Linux
Boot0001 Hard Drive
Boot0002* debian
Boot0003* Windows Boot Manager
Boot0005* CD/DVD Drive
I also read somewhere that I might run into trouble again when Win7
updates itself. So I think I will keep your efi install cd near and use it
for recovering again if I run into trouble. :)
-- Mika
On Sun, Sep 2, 2012 at 7:05 PM, Steve McIntyre st...@einval.com wrote:
Mika Rastas wrote:
Nice work Steve,
*grin* Thanks!
And just in time for me. I bought a UEFI system second hand and got it
from mail on Friday. Its got a ASUS Sabertooth 990FX board with the
newest bios.
I installed with your third version of the installer and it worked.
Awesome.
Though still having trouble with double booting to win7 and Asus
bootmgr. It boots win7 loader, but doesn't find the grub one. I can get
it to load grub from my debian install when I efi-boot with your cd and
load the config file to that grub from hd. Well getting off topic so
finishing.
What does efibootmgr say once you've got your system booted into
Debian?
--
Steve McIntyre, Cambridge, UK.
st...@einval.com
Google-bait: http://www.debian.org/CD/free-linux-cd
Debian does NOT ship free CDs. Please do NOT contact the mailing
lists asking us to send them to you.
Bug#679276: debian-installer: Debian installer fails to prevent the user from defining more than 10 md devices
As a matter of fact it *does* prevent the creation of more than 11 md devices
but as far as I can see this is a bug, not a feature.
In the file lib/md-base.sh:
# Find the next available MD device number
md_next_device_number () {
local md_num=$(grep ^md /proc/mdstat | \
sed -e 's/^md\(.*\) : active .*/\1/' | sort | tail -n1)
if [ -z $md_num ]; then
md_num=0
else
md_num=$(($md_num + 1))
fi
echo $md_num
}
What does 'sort' do with 0 1 2 3 4 5 6 7 8 9 10? Well not what one might
expect: 0 1 10 2 3 4 5 6 7 8 9.
That means we get 9 even if md10 exists and return 10 as the next available
device number. So the installer will try to create md10 again. It should be
'sort -n' instead to handle this properly.
@Carsten: why should the limit for md devices be 10?
Regards,
Stefan
--
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/20120903034625.0e9637e7@Gondolin
