|
Bugzilla – Full Text Bug Listing |
| Summary: | hard disk device node lost for hdd inside eSATA Tevion case. | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Elmar Stellnberger <estellnb> |
| Component: | Basesystem | Assignee: | E-mail List <bnc-team-screening> |
| Status: | VERIFIED NORESPONSE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | jeffm |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
barehdd.lshal
preplug.lshal postplug.lshal postplug2.lshal dmesg lspci -nn |
||
|
Description
Elmar Stellnberger
2009-06-18 12:09:21 UTC
Created attachment 298978 [details]
barehdd.lshal
Created attachment 298980 [details]
preplug.lshal
Created attachment 298988 [details]
postplug.lshal
Created attachment 298989 [details]
postplug2.lshal
Unfortunately /var/log/messages does not come up with any output about it. Seems having worsened under Opensuse 11.2, Milestone 6. lshal -lu /org/freedesktop/Hal/devices/storage_serial_SATA_SAMSUNG_HD753LJS13UJ1KQ301303 does not give any output any more. The drive works under Windows. What about Novells` hardware initiative? What is a tevion case? Is it an eSATA cage? Yes, Tevion is a synonyme for the manufactorer of the eSATA case. . Can you please attach the output of "dmesg" after connecting the esata device? Also, please attach the output of "lspci -nn". Thanks. Created attachment 327660 [details]
dmesg
no messages in dmesg; dmesg is the same before and after plugging.
Created attachment 327662 [details]
lspci -nn
Sorry for the late reply; I had to do a complete system reinstallation.
That means that the controller is not seeing the device being attached at all - ie. no communication link is being established between the eSATA port on your computer and the device. I suggest checking the hardware. Thanks. Strange; why it could create the hal device nodes before. Perhaps I should retest with os11.1. . Why do you think it created hal nodes? Which node are you referring to in which file? That just cannot happen. see for the attachements: *.lshal (os11.1) Yeah, I looked at them and diff'd them. I don't know how you did the testing but it looks like the device node for bare hadd was hanging around till you did preplug lshal and later went away before you did post lshals (ATA drive unplugging usually takes from 15 to 20 secs). If the kernel isn't noticing it, there simply is no way hal would know anything about it. Does booting with "libata.force=1.5Gbps" make any difference? Can you please boot with the parameter, hotplug the eSATA device and then attach full output of dmesg? Unfortunately there is still no dmesg-output when I boot with libata.force=1.5Gbps with 2.6.31.6-0.0.0.23.273000e-desktop. I wonder why it had recognized the presence of the hdd with os 11.1. I'm getting confused. Didn't you say the first lshal output was taken by connecting the drive directly to the port without going through the eSATA harness? Does the drive appear if you connect it directly to the port under 11.2? Yes, by connecting the HDD directly (without the eSATA case) it still works well with 11.2. I can't think of anything which can make 11.1 and 11.2 behave differently like that. At that level, it's basically all hardware and the driver is simply listening for events. Link powersave mode can interfere with hotplugging but if it were link powersave issue, direct connection should have failed the same way. Can you please boot 11.1 live media and attach the drive via the eSATA harness and attach the log? Thanks. Hi ,all I close it because no response ,please reopen it if you can provide more information . Thanks , wei |