Debian Bug report logs - #686314
Requires the fuse module to be loaded in order to detect Windows 7

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: "Ruben Leote Mendes" <ruben@nocturno.org>

To: submit@bugs.debian.org

Subject: Wheezy Instalation Report on Samsung NP305U1A

Date: Fri, 31 Aug 2012 03:29:10 +0100 (WEST)

Package: installation-reports

Boot method: USB stick
Image version: Beta 1 -
http://cdimage.debian.org/cdimage/wheezy_di_beta1/amd64/iso-cd/debian-wheezy-DI-b1-amd64-netinst.iso
Date: 2012/08/30

Machine: Samsung NP305U1A
Processor: AMD E-450
Memory: 4GB
Partitions:
Filesystem                                             Type     1K-blocks 
  Used Available Use% Mounted on
rootfs                                                 rootfs    19464068
4097784  15170988  22% /
udev                                                   devtmpfs     10240 
     0     10240   0% /dev
tmpfs                                                  tmpfs       380000 
   732    379268   1% /run
/dev/disk/by-uuid/72d72937-453a-4690-95e2-12ef2ac3f4c7 ext4      19464068
4097784  15170988  22% /
tmpfs                                                  tmpfs         5120 
     0      5120   0% /run/lock
tmpfs                                                  tmpfs       759996 
    92    759904   1% /tmp
tmpfs                                                  tmpfs       759996 
    80    759916   1% /run/shm
/dev/mapper/sda6_crypt                                 ext4     392900060
6092452 382874048   2% /home

Output of lspci -knn:
00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 14h
Processor Root Complex [1022:1510]
        Subsystem: Samsung Electronics Co Ltd Device [144d:c600]
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee
ATI Wrestler [Radeon HD 6320] [1002:9806]
        Subsystem: Samsung Electronics Co Ltd Device [144d:c600]
00:01.1 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI Wrestler
HDMI Audio [Radeon HD 6250/6310] [1002:1314]
        Subsystem: Samsung Electronics Co Ltd Device [144d:c600]
        Kernel driver in use: snd_hda_intel
00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Family 14h
Processor Root Port [1022:1512]
        Kernel driver in use: pcieport
00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee ATI
SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391]
        Subsystem: Samsung Electronics Co Ltd Device [144d:c600]
        Kernel driver in use: ahci
00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
        Subsystem: Samsung Electronics Co Ltd Device [144d:c600]
        Kernel driver in use: ohci_hcd
00:12.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI
SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]
        Subsystem: Samsung Electronics Co Ltd Device [144d:c600]
        Kernel driver in use: ehci_hcd
00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
        Subsystem: Samsung Electronics Co Ltd Device [144d:c600]
        Kernel driver in use: ohci_hcd
00:13.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI
SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]
        Subsystem: Samsung Electronics Co Ltd Device [144d:c600]
        Kernel driver in use: ehci_hcd
00:14.0 SMBus [0c05]: Advanced Micro Devices [AMD] nee ATI SBx00 SMBus
Controller [1002:4385] (rev 42)
        Subsystem: Samsung Electronics Co Ltd Device [144d:c600]
        Kernel driver in use: piix4_smbus
00:14.2 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI SBx00
Azalia (Intel HDA) [1002:4383] (rev 40)
        Subsystem: Samsung Electronics Co Ltd Device [144d:c600]
        Kernel driver in use: snd_hda_intel
00:14.3 ISA bridge [0601]: Advanced Micro Devices [AMD] nee ATI
SB7x0/SB8x0/SB9x0 LPC host controller [1002:439d] (rev 40)
        Subsystem: Samsung Electronics Co Ltd Device [144d:c600]
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]
        Subsystem: Samsung Electronics Co Ltd Device [144d:c600]
        Kernel driver in use: ohci_hcd
00:15.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI
SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0) [1002:43a0]
        Kernel driver in use: pcieport
00:15.1 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI
SB700/SB800/SB900 PCI to PCI bridge (PCIE port 1) [1002:43a1]
        Kernel driver in use: pcieport
00:15.2 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI SB900 PCI
to PCI bridge (PCIE port 2) [1002:43a2]
        Kernel driver in use: pcieport
00:15.3 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI SB900 PCI
to PCI bridge (PCIE port 3) [1002:43a3]
        Kernel driver in use: pcieport
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h
Processor Function 0 [1022:1700] (rev 43)
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h
Processor Function 1 [1022:1701]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h
Processor Function 2 [1022:1702]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h
Processor Function 3 [1022:1703]
        Kernel driver in use: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h
Processor Function 4 [1022:1704]
00:18.5 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h
Processor Function 6 [1022:1718]
00:18.6 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h
Processor Function 5 [1022:1716]
00:18.7 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h
Processor Function 7 [1022:1719]
03:00.0 Network controller [0280]: Broadcom Corporation BCM4313
802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
        Subsystem: Wistron NeWeb Corp. Device [185f:051a]
        Kernel driver in use: brcmsmac
05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)
        Subsystem: Samsung Electronics Co Ltd Device [144d:c600]
        Kernel driver in use: r8169

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [O]
Detect network card:    [E]
Configure network:      [O]
Detect CD:              [O]
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:        [O]

Comments/Problems:
The error on Detect network card is Bug #683849. After workaround the
instalation proceeds until installing GRUB. It does not detect Windows 7.
The problem is grub-mount requires fuse kernel support but the module is
not available. I did "insmod
/target/lib/modules/3.2.0-3-amd64/kernel/fs/fuse/fuse.ko". Retried the
bootloader install and it detected Windows 7. The instalation then
finished successfully.
When booting the screen was garbled with random pixels. To solve this I
add to append radeon.modeset=0 to the kernel line in grub, as found in
http://forums.debian.net/viewtopic.php?f=7&t=75795

-- 
Rúben Leote Mendes -- ruben@nocturno.org

Message #10 received at 686314@bugs.debian.org (full text, mbox, reply):

From: Christian PERRIER <bubulle@debian.org>

To: Ruben Leote Mendes <ruben@nocturno.org>, 686314@bugs.debian.org

Subject: Re: Bug#686314: Wheezy Instalation Report on Samsung NP305U1A

Date: Fri, 31 Aug 2012 07:09:40 +0200

[Message part 1 (text/plain, inline)]

reassign 686314 os-prober
retitle 686314 Requires the fuse module to be loaded in order to detect Windows 7
thanks

Quoting Ruben Leote Mendes (ruben@nocturno.org):

> The error on Detect network card is Bug #683849. After workaround the
> instalation proceeds until installing GRUB. It does not detect Windows 7.
> The problem is grub-mount requires fuse kernel support but the module is
> not available. I did "insmod
> /target/lib/modules/3.2.0-3-amd64/kernel/fs/fuse/fuse.ko". Retried the
> bootloader install and it detected Windows 7. The instalation then
> finished successfully.

 That's very interesting information as it seems we have several
 reports of Win7 not being detected if I'm correct.

Can you confirm that loading the fuse module *during the install
process before the boot loader setup* was enough for W7 to be
detected?

If so, we would really need to do it but we can't do it the way you
did of course-->we'd need the fuse module in the installer's kernel.

[signature.asc (application/pgp-signature, inline)]

Message #19 received at 686314@bugs.debian.org (full text, mbox, reply):

From: Rúben Leote Mendes <ruben@nocturno.org>

To: 686314@bugs.debian.org

Cc: Christian PERRIER <bubulle@debian.org>

Subject: Re: Bug#686314: Wheezy Instalation Report on Samsung NP305U1A

Date: Tue, 04 Sep 2012 02:25:58 +0100

Em 31-08-2012 06:09, Christian PERRIER escreveu:
> Can you confirm that loading the fuse module *during the install
> process before the boot loader setup* was enough for W7 to be
> detected?

The first time the boot loader setup run it did not find W7. I went back 
several times and retried the setup. The same. Then I lookup up the 
installation scripts and one of them (don't remember now which one) 
called grub-mount. I invoked grub-mount on the command line and got the 
error "fuse not available" or something like that. I tried to insmod 
fuse but the module was not found. Then I installed the fuse module from 
the "target" dir. Retried the boot loader setup and W7 was now found.

If it helps I can reinstall wheezy from scratch. Just Let me know which 
information I should collect.

Message #24 received at 686314@bugs.debian.org (full text, mbox, reply):

From: Christian PERRIER <bubulle@debian.org>

To: Rúben Leote Mendes <ruben@nocturno.org>

Cc: 686314@bugs.debian.org

Subject: Re: Bug#686314: Wheezy Instalation Report on Samsung NP305U1A

Date: Tue, 4 Sep 2012 06:50:53 +0200

[Message part 1 (text/plain, inline)]

clone 686314 -1
reassign -1 linux
retitle -1 Please add the fuse module to d-i kernel packages
thanks

Quoting Rúben Leote Mendes (ruben@nocturno.org):
> Em 31-08-2012 06:09, Christian PERRIER escreveu:
> >Can you confirm that loading the fuse module *during the install
> >process before the boot loader setup* was enough for W7 to be
> >detected?
> 
> The first time the boot loader setup run it did not find W7. I went
> back several times and retried the setup. The same. Then I lookup up
> the installation scripts and one of them (don't remember now which
> one) called grub-mount. I invoked grub-mount on the command line and
> got the error "fuse not available" or something like that. I tried
> to insmod fuse but the module was not found. Then I installed the
> fuse module from the "target" dir. Retried the boot loader setup and
> W7 was now found.
> 
> If it helps I can reinstall wheezy from scratch. Just Let me know
> which information I should collect.
> 

No, that's not needed. Your information seems enough to confirm that
we need the fuse module in the installer kernel and have it loaded in
os-prober prior to OS tests. Thanks for your help.

I'm therefore cloning this bug so that kernel maintainers add the fuse
module to installer kernel packages and we modify os-prober (probably
os-probes/common/50mounted-tests) to load this module beforecalling
grub-mount (not sure about the latter).



-- 

[signature.asc (application/pgp-signature, inline)]

Message #31 received at 686314@bugs.debian.org (full text, mbox, reply):

From: Filipus Klutiero <chealer@gmail.com>

To: 684265@bugs.debian.org, 650819@bugs.debian.org, Debian Bug Control <control@bugs.debian.org>

Cc: 686314@bugs.debian.org

Subject: Worked around

Date: Tue, 18 Sep 2012 19:49:20 -0400

severity 650819 normal
close 684265 3.2.29-1
forcemerge 650819 686314
thanks

This is no longer RC. A workaround has finally been applied, namely the 
first one, adding fuse. It will take some time before the fix makes it 
to install media. Note that I did not verify that the current symptom is 
gone and am closing its report assuming that fuse was properly added to 
installer images.

We should still apply one of solutions 3 or 4, but this is no longer urgent.

Send a report that this bug log contains spam.