eSATA expressCard not detected when system started

Bug #482699 reported by Hervé Fache
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

I just bought en expressCard eSATA card with a JMicron JMB36x chip on it. This card was not hot detected, and if plugged before kernel boot the card would appear in lspci but the hard disk connected to it would not get detected.

I found a thread where Greg K-H suggested to load the pciehp or acpiphp module. pciehp is not present as a module (is it compiled in?), but acpiphp did the trick. I have now added it to /etc/modules.

I therefore suggest this module gets added to /etc/modules on a default install, as a 'normal' user might have struggled quite a lot!

ProblemType: Bug
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: herve 2903 F.... kmix
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0700000 irq 22'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10573055,10573055,00100700 HDA:10ec0883,17341236,00100002'
   Controls : 29
   Simple ctrls : 18
Date: Sat Nov 14 17:28:49 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=554efcb6-6719-4c81-bf22-0464e8696672
MachineType: FUJITSU SIEMENS AMILO Xi 2428
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-14-generic root=UUID=0aca7818-97bb-4731-acff-2cbc8394d739 ro quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
SourcePackage: linux
Uname: Linux 2.6.31-14-generic i686
UserAsoundrc:
 # ALSA library configuration file

 # Include settings that are under the control of asoundconf(1).
 # (To disable these settings, comment out this line.)
 </home/herve/.asoundrc.asoundconf>
WpaSupplicantLog:

XsessionErrors:
 (firefox:3005): Gdk-WARNING **: XID collision, trouble ahead
 (firefox:3005): Gdk-WARNING **: XID collision, trouble ahead
dmi.bios.date: 09/30/2008
dmi.bios.vendor: Phoenix
dmi.bios.version: 1.15
dmi.board.name: F40
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: 00030D0055001048
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.modalias: dmi:bvnPhoenix:bvr1.15:bd09/30/2008:svnFUJITSUSIEMENS:pnAMILOXi2428:pvr:rvnFUJITSUSIEMENS:rnF40:rvr00030D0055001048:cvnFUJITSUSIEMENS:ct10:cvr:
dmi.product.name: AMILO Xi 2428
dmi.sys.vendor: FUJITSU SIEMENS

Revision history for this message
Hervé Fache (rvfh) wrote :
Andy Whitcroft (apw)
tags: added: kernel-karmic
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Hervé,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 482699

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Hervé Fache (rvfh) wrote : Re: [Bug 482699] Re: eSATA expressCard not detected when system started

Using Lucid, I still have issues with my expresscard... When I have more
time to investigate I'll try to find out exactly what works and what
doesn't. For now, acpiphp remains in my /etc/modules!

On 23 April 2010 23:49, Jeremy Foshee <email address hidden> wrote:

> Hi Hervé,
>
> This bug was reported a while ago and there hasn't been any activity in it
> recently. We were wondering if this is still an issue? Can you try with the
> latest development release of Ubuntu? ISO CD images are available from
> http://cdimage.ubuntu.com/releases/ .
>
> If it remains an issue, could you run the following command from a Terminal
> (Applications->Accessories->Terminal). It will automatically gather and
> attach updated debug information to this report.
>
> apport-collect -p linux 482699
>
> Also, if you could test the latest upstream kernel available that would be
> great. It will allow additional upstream developers to examine the issue.
> Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've
> tested the upstream kernel, please remove the 'needs-upstream-testing' tag.
> This can be done by clicking on the yellow pencil icon next to the tag
> located at the bottom of the bug description and deleting the
> 'needs-upstream-testing' text. Please let us know your results.
>
> Thanks in advance.
>
> [This is an automated message. Apologies if it has reached you
> inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: needs-kernel-logs
>
> ** Tags added: needs-upstream-testing
>
> ** Tags added: kj-triage
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> --
> eSATA expressCard not detected when system started
> https://bugs.launchpad.net/bugs/482699
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

To fix it you need to pass this parameter to the kernel at boot:
pciehp.pciehp_force=1

Grub -> Open /boot/grub/menu.lst
Grub 2 -> Open /etc/default/grub

add "pciehp.pciehp_force=1" at the end of the kernel parameters line.

e.g.
Grub
kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/sda5 ro quiet splash will be kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/sda5 ro quiet splash pciehp.pciehp_force=1

Grub 2
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" will be GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pciehp.pciehp_force=1"

Try this way and report here if it works for you too.

\It should be nice to have this parameter set by default in Maverick Meerkat.
Anyone in the kernel team could help about this please?
It seems to be a really simple change and it fixes a lot of bugs against express cards.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

I forgot to mention that you need to run:

sudo update-grub

in a terminalt after editing the grub file and then reboot.

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Btw, you can't find the pciehp module because it's compiled in the kernel from 9.04 (if I correctly remember the right release).

penalvch (penalvch)
tags: added: karmic lucid
removed: kernel-karmic needs-kernel-logs
Revision history for this message
penalvch (penalvch) wrote :

Hervé Fache, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.8-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.