[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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.GH21377@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 owner@bugs.debian.org
immediately.)


-- 
686468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686468
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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 setup:   [O]
User/password setup:    [O]
Install tasks:          [O]
Install boot loader:    [E]
Overall install:        worked, but with a few glitches

Comments/Problems:

The installation was done in expert mode, with XFCE selected as
the desktop environment. Partitioning was done manually.

The netboot mini.iso (isohybrid image) contains a small (about
6MB) empty partition labeled "firmware" into which one can copy
non-free firmware images which are needed during the installation
process.  I did so with the ethernet card and wifi firmware. 
Both have been successfully copied into the target system during
the installation.

Automatically installing grub failed; d-i tried to install grub
to /dev/sda, which was the USB flash drive from which d-i was
booted.  The harddisk onto which grub should have been installed
was detected as /dev/sdb.  After re-running the "install grub"
stage and manually specifying /dev/sdb as target, the
installation of grub was successful.

An existing Windows 7 installation on the computer was not
detected by d-i and therefore did not show up in the grub boot
menu.  Manually calling update-grub from the installed system
created the missing boot enty.

Xfce4-mixer did not work out of the box. On start, it complained
that "GStreamer was unable to detect any sound devices".  The
reason for this was that the gstreamer0.10-alsa package was not
installed.  This problem has already been submitted by somebody
else in bug #651495 last year; the problem has been confirmed by
another submitter in June 2012 and is still open.  This should be
fixed before the wheezy release, in particular as xfce is now the
default desktop for wheezy.  From a first look at the issue it
seems that there is no explicit dependency on gstreamer0.10-alsa
in task-xfce-desktop.  Xfce4-mixer itself depends on
"gstreamer0.10-alsa | gstreamer0.10-audiosink", whereby
gstreamer0.10-audiosink is a purely virtual package provided by
other gstreamer-plugins, so if some other application pulls in
e.g. gstreamer0.10-plugins-good, the dependency gets fulfilled
but the mixer nonetheless does not work on an alsa device.

I have not tested wicd functionality on this system; due to
certain requirements which cannot be fulfilled by wicd I have
replaced wicd by network-manager and the network-manager-gnome
plugin, which works flawlessly in the xfce taskbar.

The system's touchpad has only two buttons. On other systems
pressing both buttons at the same time usually emulates a
middle-mouse-button event, but this does not work here.

Regards,
Karsten
-- 
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.

--- End Message ---
--- Begin Message --- 
Quoting Karsten Merker (merker@debian.org):

> Automatically installing grub failed; d-i tried to install grub
> to /dev/sda, which was the USB flash drive from which d-i was
> booted.  The harddisk onto which grub should have been installed
> was detected as /dev/sdb.  After re-running the "install grub"
> stage and manually specifying /dev/sdb as target, the
> installation of grub was successful.

We have many such reports, some reassigned to grub-installer. I wish
someone looks at them and fixes them....

> An existing Windows 7 installation on the computer was not
> detected by d-i and therefore did not show up in the grub boot
> menu.  Manually calling update-grub from the installed system
> created the missing boot enty.


That seems to be due to a missing fuse module. A detailed bug report
was sent recently with such information. Loading the fuse module
manually (from console 2 in the installer) then allows os-prober to
detect Windows 7.

Given that your installation was (nearly) a complete success, I do as
usual with reports for successful installations: I close the bug..:-)

This does not of course mean you weren't right to report. Knowing the
installations are correct is important for the d-i team.

Many thanks for your time testing the Debian Installer and reporting
your results. Have fun with your new Debian system!

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: