Bug#683773: btrfs-write-performance rechecked, downgrading the severity to 'wishlist'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 07 Aug 2012 13:31:28 +0200 Gaudenz Steinlin wrote: > > Hi Andreas > > > Andreas Glaeser writes: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > To check if btrfs is really slow I tried the following: > > - -# aptitude install btrfs-tools > > - -created a btrfs-partition as /dev/sdb14 with gparted and aligned it to > > sector, not > > to mbr, because the harddisk is an advanced format model with 4096k blocks. > > - -# mkfs -t btrfs /dev/sdb14 > > - -# mkdir /mnt/test > > - -# mount /dev/sdb14 /mnt/test > > - -# exit > > andreas@g4d:~$ cd /mnt/test > > andreas@g4d:/mnt/test$ mkdir fs-root-c-arc > > andreas@g4d:/mnt/test$ time cp -a /* fs-root-c-arc/ >c-arc.txt 2>c-err.txt > > > > real7m48.020s > > user0m5.304s > > sys 1m22.868s > > andreas@g4d:/mnt/test$ ls -l > > total 2775172 > > - -rw-r--r-- 1 andreas andreas 0 Aug 7 08:20 c-arc.txt > > - -rw-r--r-- 1 andreas andreas1145749 Aug 7 08:27 c-err.txt > > drwxr-xr-x 1 andreas andreas136 Aug 7 08:27 fs-root-c-arc > > andreas@g4d:/mnt/test$ du -hs fs-root-c-arc/ > > 3.6Gfs-root-c-arc/ > > > > andreas@g4d:/mnt/test$ chmod 000 fs-root-c-arc/ > > andreas@g4d:/mnt/test$ time tar -cvf t-arc.tar /* >t-out.txt 2>t-err.txt > > > > real6m25.904s > > user0m6.016s > > sys 0m47.936s > > andreas@g4d:/mnt/test$ ls -l > > total 2784108 > > - -rw-r--r-- 1 andreas andreas 0 Aug 7 08:20 c-arc.txt > > - -rw-r--r-- 1 andreas andreas1145749 Aug 7 08:27 c-err.txt > > drwxr--r-- 1 andreas andreas136 Aug 7 08:27 fs-root-c-arc > > - -rw-r--r-- 1 andreas andreas 2841907200 Aug 7 08:47 t-arc.tar > > - -rw-r--r-- 1 andreas andreas1348292 Aug 7 08:47 t-err.txt > > - -rw-r--r-- 1 andreas andreas6513194 Aug 7 08:47 t-out.txt > > > > This were two tests, first created an archive of the root filesystem using > > cp below > > the folder /mnt/test/fs-root-c-arc/. This issued a lot of errors and > > warning because > > of missing permissions or files, which changed while being read, but in the > > end after > > 7m48s there were 151869 items in that folder, totalling 3.6 GB. > > Next the mode of the folder was set to 000, because else the content of the > > folder > > would be taken into the newly created .tar-archive recursively. > > Then doing basically the same thing, but putting all readable and > > accessable files > > into a single uncompressed .tar-archive instead of just copying them. > > this was even faster with 6m25s and the archive was 2.6 Gb in size. > > This is not the same as installing from DVD and via network over http, but > > big files > > and many small files are both written fast enough from xfs to btrfs, given > > that this > > is a green-labeled harddisk, which is not supposed to break any > > velocity-records. So I > > downgraded the installation-report to 'wishlist'. I consider the problems > > were due to > > some kind of strange IRQ-conflict or the like. A software-upgrade was not > > done since > > installation, just some additional packages installed. > > No, your test did not really simulate the situation during installation. > The problem with btrfs is not poor write performance in general, but > very poor fsync performance. dpkg does a lot of fsync's and is therefore > heavily affected by this. > > You could verify this by running debootstrap on a btrfs filesstem > (debootstrap wheezy /mnt). This will be incredibly slow. On the other > hand if you use the "eatmydata" utility which turns all fsync calls into > noops, it will be fast: "eatmydata debootstrap wheezy /mnt". But beware, > it's called eatmydata for a reason... > > Gaudenz > Now I retried installing the debian base-system onto my previously created test-partition, selected the smp-kernel, which has no effect until next reboot, so everythin is done on a single core only, and chose the default generic initrd.img. This took about 19m 05s. I retried this with a newly created partition, created during the installation-process using the d-i-partitioning-tool, the result was almost identical, taking 19m 25s, the difference probably being due to my slow resposiveness on interactive questions. When I looked at the two partitions with gparted, there was no information about their alignment, the tool only allows to select this while creating partitions, but can not display information seemingly about existing partitions. cfdisk was not able to show any partitions on the harddrive, but claimed, the disk was empty. It is a bit strange, might actually be another bug. So overall it was right to set the bug-severity to wishlist, because the weak performance was obviously due to faulty hardware and maybe due to some fault-correction or -avoidance mechanism in btrfs. the file system probably tries to preserve data integrity when disk-problems occur. Reading data did go at near to normal speed actually. It is safe now to close
Processed: found 684900 in 175-6, found 672160 in 1.82, user debian...@lists.debian.org, usertagging 657904 ...
Processing commands for cont...@bugs.debian.org: > found 684900 175-6 Bug #684900 [udev] udev: fails to purge: rmdir: failed to remove `/etc/udev/rules.d/': No such file or directory Marked as found in versions 175-6/. > found 672160 1.82 Bug #672160 [console-setup] console-setup: unowned files after purge (policy 6.8, 10.8) Marked as found in versions 1.82/. > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was deb...@abeckmann.de). > usertags 657904 piuparts There were no usertags set. Usertags are now: piuparts. > found 657904 1.82 Bug #657904 [console-setup] console-setup: Shouldn't console-setup package put files in /usr/share/doc/console-setup? Marked as found in versions 1.82/. > thanks Stopping processing here. Please contact me if you need assistance. -- 657904: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657904 672160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672160 684900: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.134501895422084.transcr...@bugs.debian.org
Bug#684968: debian-installer: requests non-free firmware for a device that works just as well without it
Package: debian-installer Severity: wishlist Tags: d-i Dear Maintainer, I have a notebook with a realtek nic which doesn't need any non-free firmware files to operate. However, debian installer requests me to install non-free firmware. It doesn't make any difference if I install it or reject the request – the network adapter just works. Debian installer shouldn't ask me to install non-free firmware for a device that works just as well without it. My hardware: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06) Firmware file which debian installer requests: rtl_nic/rtl8168e-3.fw -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20120815083006.4733.88375.reportbug@rosa
Re: Bug#684968: debian-installer: requests non-free firmware for a device that works just as well without it
On Wed 15 Aug 2012 at 10:30:06 +0200, Stefan Nagy wrote: > Package: debian-installer > Severity: wishlist > Tags: d-i > > Dear Maintainer, > > I have a notebook with a realtek nic which doesn't need any non-free firmware > files to operate. However, debian installer requests me to install non-free > firmware. It doesn't make any difference if I install it or reject the request > – the network adapter just works. > > Debian installer shouldn't ask me to install non-free firmware for a device > that works just as well without it. What else can the installer do other than pass on the request from the kernel? Please don't shoot the messenger. -- 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/20120815103552.GC5539@desktop
Bug#684968: debian-installer: requests non-free firmware for a device that works just as well without it
On Wed 15 Aug 2012 at 10:30:06 +0200, Stefan Nagy wrote: [I sent to debian-boot and forgot to Cc: the bug] > Package: debian-installer > Severity: wishlist > Tags: d-i > > Dear Maintainer, > > I have a notebook with a realtek nic which doesn't need any non-free firmware > files to operate. However, debian installer requests me to install non-free > firmware. It doesn't make any difference if I install it or reject the request > – the network adapter just works. > > Debian installer shouldn't ask me to install non-free firmware for a device > that works just as well without it. What else can the installer do other than pass on the request from the kernel? Please don't shoot the messenger. -- 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/20120815105349.GA12097@desktop
Bug#684954: installation-reports: fine apart from timezone & apt translations
Christian PERRIER wrote: > Quoting Jamie Heilman (ja...@audible.transient.net): > > Christian PERRIER wrote: > > > Localechooser makes it very clear that the country location impacts > > > the timezone choices (at least as clear as one can be in a two > > > sentences screen). > > > > Sure, I don't debate that, but I heartly debate the utility of forcing > > me to lie and say my server is in London just to set the #@!$ing > > timezone to UTC. Note to anybody who thought that would even work: it won't, as it turns out, Europe/London isn't the same as UTC. > > Just as forcing the user to set their location to Asia/Japan to > > set their locale to ja_JP.whatever would be stupid, forcing the > > user to set system location to somewhere where the system isn't to > > achieve the desired timezone is equally stupid. > > You don't have to say your server is in Japan to get a ja_JP locale. > Please better choose your arguments. This one is wrong. Ask Japanese > users. That's my point, I'm saying language *isn't* tied to location because doing so would be wrong, much like tying timezone to location is wrong. The same logic applies. Host location is a red herring, the installer shouldn't even ask about it. It should just ask what timezone the user wants to configure, and let them choose from the full list. If for some unfathomable reason we simply *must* be forced to select a server location, then stuffing the less-likely timezone selections under a sub-menu called "other" would be acceptable too. > > > If you want to use a given timezone, then choose the appropriate > > > country in localechooser. This is meant for that purpose. > > > > That's inane, and unless I've totally forgotten the logic flow of > > previous installations (ISTR being able to actually choose my timezone > > from a list in previous Debian releases), it's a sad regression. > > It is not. Nothing changed about this since woody. Wow, has it been broken for that long? Admittedly, I usually bootstrap new systems with debootstrap after slapping a drive into an existing host, so it has been a while since I took the traditional route. Running through older installers... Sarge - asks for timezone explicitly and lets the user set it to anything; this is the correct behavior Etch- timezone selection is restricted based on language selection Lenny - timezone selection is restricted based on language selection Squeeze - timezone selection is restricted based on language selection So Wheezy is arguably a small step forward, restricting timezone based on language is worse than restricting it based on location; but the installer has still regressed, the last time it did the right thing was Sarge. -- Jamie Heilman http://audible.transient.net/~jamie/ -- 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/20120815112346.ge32...@cucamonga.audible.transient.net
Bug#684968: debian-installer: requests non-free firmware for a device that works just as well without it
Am Mittwoch, den 15.08.2012, 11:53 +0100 schrieb Brian Potkin: > What else can the installer do other than pass on the request from the > kernel? Please don't shoot the messenger. Sorry – I wasn't sure to which package this bug belongs… Could you reassign it please? Thanks, Stefan. signature.asc Description: This is a digitally signed message part
Summary for "D-I hangs in some configurations" issues
Today, I did some testing about these often reported issues of D-I "hanging", most often when detecting network hardware or when mounting ISO images. These issue is a kernel issue. It is being dealt with in #684293. A workaround has been committed and uploaded in mountmedia. It is confirmed working by my tests. Another workaround for iso-scan has been sent in #684293 (when I sent it, I forgot that this was the bug that had been reassigned to the kernel, sorry). It is also confirmed as working but I think it is quite ugly (blame my bad shell programming skills). The bug has been tagged pending by the kernel maintainers, so I guess that a kernel patch is on its way. If a new kernel with that patch reaches wheezy, then we don't need the workarounds anymore: - no need to commit one for iso-scan - need to revert the one in mountmedia -- signature.asc Description: Digital signature
Bug#684968: debian-installer: requests non-free firmware for a device that works just as well without it
Stefan Nagy writes: > I have a notebook with a realtek nic which doesn't need any non-free firmware > files to operate. However, debian installer requests me to install non-free > firmware. It doesn't make any difference if I install it or reject the request > – the network adapter just works. > > Debian installer shouldn't ask me to install non-free firmware for a device > that works just as well without it. You cannot know that it works "just as well". The firmware may enable additional features you don't use, or which does not matter to your usage pattern. Or the firmware fixes known bugs which you just haven't hit or which you didn't know you were hitting. Both of these are quite common for network adapter firmware. > My hardware: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit > Ethernet controller [10ec:8168] (rev 06) > Firmware file which debian installer requests: rtl_nic/rtl8168e-3.fw I believe this works exactly as intended. The adapter does function without the firmware and the driver allows you to continue using it even if the firmware load fails, thereby enabling you to complete the installation and download the firmware if acceptable. The driver firmware request is required to enable those who want to load the optional firmware. Just ignore it if you don't want to. Bjørn -- 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/87zk5wqamt@nemi.mork.no
Bug#685010: installation-reports
Package: installation-reports Boot method: cat onto usb drive. Image version: http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-CD-1.iso Date: 13.august 2012 Machine: ASUS AT3IONT-1 Processor: Atom 330 Memory: Kingston KVR1333D3N9K2/2G Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [0] Detect network card:[E] Configure network: [E] Detect CD: [0] Load installer modules: [0] Detect hard drives: [0] Partition hard drives: [0] Install base system:[0] Clock/timezone setup: [0] User/password setup:[0] Install tasks: [0] Install boot loader:[0] Overall install:[E] Comments/Problems: Detecting network hardware stalls and hangs. Can be skipped with expert installer, but that doesn't result in a working desktop. http://www.debian.org/devel/debian-installer/errata 3.2.0-3-amd64 This is what happens as the d-i tries to bring up the network NIC: eth1: link is not ready r8169 unable to load firmware patch rtl_nic/rtl8168d-2.fw eth0: link down eth0: link is notready check missing firmware /dev/.udev/firmware-missing does not exist, skipping check missing firmware: missing firmware files (rtl_nic/rtl8168d-2.fw) for r8169 Ethernet controller [0200] Realtek RTL8111/8168B rev 03 Subsystem ASUStek Device [1043:83a3] Kernel driver in use r8169 but that module isnt used by 0. On my other computer, which is build with a gigabyte ga-x48-dq6 MB, cant remember what bios i flashed it with, reported as GA-EP45-DS5/GA-EG45M-DS2H Motherboard, there is a rtl8168c/8111c (rev 02) NIC Loading the r8169 driver for 8168 hardware has been troublesome for quite some time http://lists.debian.org/debian-kernel/2011/12/msg00212.html I tried on a separate occasion to compile the 8168 driver from realtek myself, and that worked like a charm. The b1 testing d-i works on the gigabyte board, but it does produce a bunch of silent link up / down errors in dmesg. notable difference, "mii" module is used by r8169 and ethernet driver 2.3LK-NAPI loaded rtl8168c/8111c shows up in dmesg Usb drive confirmed to work on an asrock machine to install debian testing.
Bug#684968: debian-installer: requests non-free firmware for a device that works just as well without it
Am Mittwoch, den 15.08.2012, 20:21 +0200 schrieb Bjørn Mork: > The driver firmware request is required to enable those who want to load > the optional firmware. Just ignore it if you don't want to. I'm not saying debian installer shouldn't recommend / ask for non-free firmware at all [1] but I do care about my freedom as software user. My notebook has an Intel WLAN adapter and a Realtek NIC – debian installer tells me in both cases that my hardware needs proprietary software to operate even if the consequences of not installing the non-free firmware are completely different. My WLAN adapter doesn't work at all when I decide not to install the firmware. I don't think that it's a good solution to seperate non-free firmware just to tell users to provide it while installation process. In my opinion debian (installer) should provide more information about the concrete consequences of not installing a specific firmware file: Will the device work at all? What are the probable limitations? Debian (installer) should enable users to make a decision here. Instead right now it seems like the safe way in each and every case is to install proprietary firmware – and everyone who decides not to install it is on his/her own. This is just my opinion (and that's why I reported this bug with severity: wishlist). [1] http://tinyurl.com/bp6pz9b signature.asc Description: This is a digitally signed message part
Bug#684968: debian-installer: requests non-free firmware for a device that works just as well without it
On Wed, Aug 15, 2012 at 6:05 PM, Stefan Nagy wrote: > Debian (installer) should enable users to make a decision here. Instead > right now it seems like the safe way in each and every case is to > install proprietary firmware – and everyone who decides not to install > it is on his/her own. > > This is just my opinion (and that's why I reported this bug with > severity: wishlist). This recently came up on the fsf-collab list. Here are my thoughts on appropriate wording: http://lists.alioth.debian.org/pipermail/fsf-collab-discuss/2012-August/000200.html Obviously that's rather long given character constraints in the installer's debconf messages. But it could be a starting point for discussion. Best wishes, Mike -- 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/CANTw=mofklh-rjoqhczotdy14wkucc3gcixrzfnoq-xeq8k...@mail.gmail.com
Bug#684968: debian-installer: requests non-free firmware for a device that works just as well without it
Quoting Michael Gilbert (mgilb...@debian.org): > On Wed, Aug 15, 2012 at 6:05 PM, Stefan Nagy wrote: > > Debian (installer) should enable users to make a decision here. Instead > > right now it seems like the safe way in each and every case is to > > install proprietary firmware – and everyone who decides not to install > > it is on his/her own. > > > > This is just my opinion (and that's why I reported this bug with > > severity: wishlist). > > This recently came up on the fsf-collab list. Here are my thoughts on > appropriate wording: > http://lists.alioth.debian.org/pipermail/fsf-collab-discuss/2012-August/000200.html > > Obviously that's rather long given character constraints in the > installer's debconf messages. But it could be a starting point for > discussion. Post-wheezy, of course..:-) And by shortening the text quite strongly (I think the first two paragraphs are enough: the rest belongs to freeness zealotism -no offense intended, I happen to be a zealot, too). signature.asc Description: Digital signature
Bug#685010: marked as done (installation-reports)
Your message dated Thu, 16 Aug 2012 06:07:36 +0200 with message-id <20120816040736.gt5...@mykerinos.kheops.frmug.org> and subject line Re: Bug#685010: installation-reports has caused the Debian Bug report #685010, regarding installation-reports 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.) -- 685010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Boot method: cat onto usb drive. Image version: http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-CD-1.iso Date: 13.august 2012 Machine: ASUS AT3IONT-1 Processor: Atom 330 Memory: Kingston KVR1333D3N9K2/2G Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [0] Detect network card:[E] Configure network: [E] Detect CD: [0] Load installer modules: [0] Detect hard drives: [0] Partition hard drives: [0] Install base system:[0] Clock/timezone setup: [0] User/password setup:[0] Install tasks: [0] Install boot loader:[0] Overall install:[E] Comments/Problems: Detecting network hardware stalls and hangs. Can be skipped with expert installer, but that doesn't result in a working desktop. http://www.debian.org/devel/debian-installer/errata 3.2.0-3-amd64 This is what happens as the d-i tries to bring up the network NIC: eth1: link is not ready r8169 unable to load firmware patch rtl_nic/rtl8168d-2.fw eth0: link down eth0: link is notready check missing firmware /dev/.udev/firmware-missing does not exist, skipping check missing firmware: missing firmware files (rtl_nic/rtl8168d-2.fw) for r8169 Ethernet controller [0200] Realtek RTL8111/8168B rev 03 Subsystem ASUStek Device [1043:83a3] Kernel driver in use r8169 but that module isnt used by 0. On my other computer, which is build with a gigabyte ga-x48-dq6 MB, cant remember what bios i flashed it with, reported as GA-EP45-DS5/GA-EG45M-DS2H Motherboard, there is a rtl8168c/8111c (rev 02) NIC Loading the r8169 driver for 8168 hardware has been troublesome for quite some time http://lists.debian.org/debian-kernel/2011/12/msg00212.html I tried on a separate occasion to compile the 8168 driver from realtek myself, and that worked like a charm. The b1 testing d-i works on the gigabyte board, but it does produce a bunch of silent link up / down errors in dmesg. notable difference, "mii" module is used by r8169 and ethernet driver 2.3LK-NAPI loaded rtl8168c/8111c shows up in dmesg Usb drive confirmed to work on an asrock machine to install debian testing. --- End Message --- --- Begin Message --- > Detecting network hardware stalls and hangs. Can be skipped with expert > installer, but that doesn't result in > a working desktop. http://www.debian.org/devel/debian-installer/errata > > 3.2.0-3-amd64 > > This is what happens as the d-i tries to bring up the network NIC: > > eth1: link is not ready > r8169 unable to load firmware patch rtl_nic/rtl8168d-2.fw > eth0: link down > eth0: link is notready > check missing firmware /dev/.udev/firmware-missing does not exist, skipping > check missing firmware: missing firmware files (rtl_nic/rtl8168d-2.fw) for > r8169 This is a known issue in the kernel. It is worked around in mountmedia anf is indeed fixed in daily built images: http://d-i.debian.org/daily-images/ (pick the netboot image). signature.asc Description: Digital signature --- End Message ---
Bug#685047: Debian Wheezy B1 installer for amd64 fails during base system install reporting unmet (awk) dependencies.
Package: installation-reports Boot method: netinst running from USB thumbdrive Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta1/amd64/iso-cd/debian-wheezy-DI-b1-amd64-netinst.iso ftp://ftp.debian.org/debian/dists/wheezy/main/installer-amd64/20120712/images/hd-media/boot.img.gz Date: 2012-08-16 01:40:00 UTC-3 Machine: HP425 Laptop Processor: AMD Athlon II P340 Memory: 2x2GB Partitions: FilesystemSize Used Available Use% Mounted on none371.2M 88.0K371.1M 0% /run tmpfs 1.8G 0 1.8G 0% /dev /dev/sdb7 396.7M283.2M113.5M 71% /hd-media /dev/loop0 231.0M231.0M 0 100% /cdrom /dev/mapper/vg--ginger-lv--root 3.7G134.4M 3.4G 4% /target /dev/sdb2 247.5M 11.4M223.6M 5% /target/boot /dev/mapper/vg--ginger-lv--home 223.3G 3.4G219.9G 2% /target/home /dev/mapper/vg--ginger-lv--opt 9.3G267.8M 8.6G 3% /target/opt /dev/mapper/vg--ginger-lv--tmp 9.3G267.8M 8.6G 3% /target/tmp /dev/mapper/vg--ginger-lv--usr 27.9G629.5M 25.9G 2% /target/usr /dev/mapper/vg--ginger-lv--var 18.6G469.4M 17.2G 3% /target/var Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS880 Host Bridge [1022:9601] 00:01.0 PCI bridge [0604]: Hewlett-Packard Company Device [103c:9602] 00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 0) [1022:9604] 00:07.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 3) [1022:9607] 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:14.5 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI2 Controller [1002:4399] 00:16.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] 00:16.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration [1022:1200] 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Address Map [1022:1201] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller [1022:1202] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control [1022:1203] 00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Link Control [1022:1204] 01:05.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RS880M [Mobility Radeon HD 4200 Series] [1002:9712] 01:05.1 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI RS880 HDMI Audio [Radeon HD 4200 Series] [1002:970f] 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 02) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[E] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: D-I fails to install the base system and complains about awk not being installed; relevant abridged syslog dump follows. Aug 16 04:13:36 syslogd started: BusyBox v1.20.2 Aug 16 04:13:36 kernel: klogd started: BusyBox v1.20.2 (Debian 1:1.20.0-5) Aug 16 04:13:36 kernel: [0.00] Initializing cgroup subsys cpuset Aug 16 04:13:36 kernel: [0.00]
