You are not logged in.

#1 2020-09-20 06:01:44

shaojin
Member
Registered: 2020-09-20
Posts: 5

Cannot identify UFS3.1's hard drive

The computer is Samsung Galaxy Book S and the hard disk is eUFS. The hard disk cannot be recognized

Offline

#2 2020-09-20 08:20:15

solskog
Member
Registered: 2020-09-05
Posts: 407

Re: Cannot identify UFS3.1's hard drive

read: https://www.kernel.org/doc/Documentation/scsi/ufs.txt
how about this module?

# modprobe ufshcd-pci

Last edited by solskog (2020-09-20 08:47:01)

Offline

#3 2020-10-14 16:19:38

shaojin
Member
Registered: 2020-09-20
Posts: 5

Re: Cannot identify UFS3.1's hard drive

# modprobe UFSHCD - PCI has no errors

But there is no Intel UFS Controller driver

Windows has this driver

Offline

#4 2020-10-14 16:54:58

progandy
Member
Registered: 2012-05-17
Posts: 5,184

Re: Cannot identify UFS3.1's hard drive

As far as I know, the galaxy book s is ARM based and uses a qualcomm chip. Looking at the kernel ufs drivers it seems there is a special ufs driver for qualcomm platforms (ufs-qcom) as well.

Anyways, that means you are asking in the wrong place. You'll need to ask for support in the Arch Linux ARM forums, we do not have the necessary knowledge.
https://archlinuxarm.org/forum/

Last edited by progandy (2020-10-14 16:55:45)


| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |

Offline

#5 2020-10-14 19:06:00

shaojin
Member
Registered: 2020-09-20
Posts: 5

Re: Cannot identify UFS3.1's hard drive

CPU is i5-L16G7
Intel Lakefield 5 core processor

Offline

#6 2020-10-14 19:11:35

shaojin
Member
Registered: 2020-09-20
Posts: 5

Re: Cannot identify UFS3.1's hard drive

It's an x86 64 bit computer

Offline

#7 2020-10-14 19:37:27

progandy
Member
Registered: 2012-05-17
Posts: 5,184

Re: Cannot identify UFS3.1's hard drive

shaojin wrote:

It's an x86 64 bit computer

You are right, there are two versions. I didn't see the intel one.

Edit: Can you see the ufs device with "lspci -nnk"? Can you give us the output?

I believe the intel implementation should be connected to the pci bus and work with ufshcd-pci.

Last edited by progandy (2020-10-14 19:52:18)


| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |

Offline

#8 2020-10-14 20:28:35

shaojin
Member
Registered: 2020-09-20
Posts: 5

Re: Cannot identify UFS3.1's hard drive

00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9800] (rev 02)
    DeviceName: Onboard - Other
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9840] (rev 03)
    DeviceName: Onboard - Video
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
00:04.0 Signal processing controller [1180]: Intel Corporation Device [8086:9820] (rev 02)
    DeviceName: Onboard - Other
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
00:05.0 Multimedia controller [0480]: Intel Corporation Device [8086:9830] (rev 02)
    DeviceName: Onboard - Sound
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
00:12.0 Serial controller [0700]: Intel Corporation Device [8086:98fc] (rev 12)
    DeviceName: Onboard - Other
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
00:12.5 Mass storage controller [0109]: Intel Corporation Device [8086:98fa] (rev 12)
    DeviceName: Onboard - Other
    Subsystem: Intel Corporation Device [8086:7270]
00:14.0 USB controller [0c03]: Intel Corporation Device [8086:98ed] (rev 12)
    DeviceName: Onboard - Other
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
    Kernel driver in use: xhci_hcd
    Kernel modules: xhci_pci
00:14.2 RAM memory [0500]: Intel Corporation Device [8086:98ef] (rev 12)
    DeviceName: Onboard - Other
    Subsystem: Intel Corporation Device [8086:7270]
00:14.5 SD Host controller [0805]: Intel Corporation Device [8086:98f8] (rev 12)
    DeviceName: Onboard - Other
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
    Kernel driver in use: sdhci-pci
    Kernel modules: sdhci_pci
00:15.0 Serial bus controller [0c80]: Intel Corporation Device [8086:98e8] (rev 12)
    DeviceName: Onboard - Other
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
00:15.1 Serial bus controller [0c80]: Intel Corporation Device [8086:98e9] (rev 12)
    DeviceName: Onboard - Other
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
00:15.2 Serial bus controller [0c80]: Intel Corporation Device [8086:98ea] (rev 12)
    DeviceName: Onboard - Other
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
00:15.3 Serial bus controller [0c80]: Intel Corporation Device [8086:98eb] (rev 12)
    DeviceName: Onboard - Other
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
00:16.0 Communication controller [0780]: Intel Corporation Device [8086:98e0] (rev 12)
    DeviceName: Onboard - Other
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
00:19.0 Serial bus controller [0c80]: Intel Corporation Device [8086:98c5] (rev 12)
    DeviceName: Onboard - Other
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
00:19.1 Serial bus controller [0c80]: Intel Corporation Device [8086:98c6] (rev 12)
    DeviceName: Onboard - Other
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:98bc] (rev 12)
    Kernel driver in use: pcieport
00:1e.0 Communication controller [0780]: Intel Corporation Device [8086:98a8] (rev 12)
    DeviceName: Onboard - Other
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
00:1e.1 Communication controller [0780]: Intel Corporation Device [8086:98a9] (rev 12)
    DeviceName: Onboard - Other
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
00:1e.2 Serial bus controller [0c80]: Intel Corporation Device [8086:98aa] (rev 12)
    DeviceName: Onboard - Other
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:9885] (rev 12)
    DeviceName: Onboard - Other
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:98c8] (rev 12)
    DeviceName: Onboard - Sound
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:98a4] (rev 12)
    DeviceName: Onboard - Other
    Subsystem: Samsung Electronics Co Ltd Device [144d:c18b]
01:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
    Subsystem: Intel Corporation Device [8086:008c]
    Kernel driver in use: iwlwifi
    Kernel modules: iwlwifi, wl

Offline

#9 2021-02-27 11:41:39

RiccardoP
Member
Registered: 2021-02-27
Posts: 1

Re: Cannot identify UFS3.1's hard drive

Same situation. Any news?

Offline

#10 2021-07-01 18:33:59

schallee
Member
Registered: 2021-07-01
Posts: 1

Re: Cannot identify UFS3.1's hard drive

The UFS pci is:

00:12.5 Mass storage controller [0109]: Intel Corporation Device [8086:98fa] (rev 12)

5.13 seems to be the first kernel to recognize this device. However, I'm not able to get it to work. Most reads just hang.

I haven't used UFS before myself so perhaps I'm missing something. The WD ufs-utils(https://github.com/westerndigitalcorporation/ufs-utils) as little documentation and everything I try with that hangs too.

Here are the relevent ufs dmesg lines from 5.13 for me:

ufshcd 0000:00:12.5: ufshcd_print_pwr_info:[RX, TX]: gear=[1, 1], lane[1, 1], pwr[SLOWAUTO_MODE, SLOWAUTO_MODE], rate = 0
ufshcd 0000:00:12.5: ufshcd_print_pwr_info:[RX, TX]: gear=[4, 4], lane[2, 2], pwr[FAST MODE, FAST MODE], rate = 2

scsi 0:0:0:49488: Well-known LUN    SAMSUNG  KLUEG8UHDB-C2D1  0089 PQ: 0 ANSI: 6
scsi 0:0:0:49476: Well-known LUN    SAMSUNG  KLUEG8UHDB-C2D1  0089 PQ: 0 ANSI: 6
scsi 0:0:0:49456: Well-known LUN    SAMSUNG  KLUEG8UHDB-C2D1  0089 PQ: 0 ANSI: 6
scsi 0:0:0:0: Direct-Access     SAMSUNG  KLUEG8UHDB-C2D1  0089 PQ: 0 ANSI: 6
sd 0:0:0:0: Power-on or device reset occurred
sd 0:0:0:0: [sda] 62480384 4096-byte logical blocks: (256 GB/238 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 32 00 10
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
sd 0:0:0:0: [sda] Optimal transfer size 524288 bytes
sda: sda1 sda2 sda3 sda4 sda5 sda6
sd 0:0:0:0: [sda] Attached SCSI disk
sd 0:0:0:0: [sda] Synchronizing SCSI cache

It is certainly seeing the device and the attached storage. It even seems to be able to read at least the partition table. That being said, any read after that hangs.

The stack trace from the hung task dmesg includes:

ufshcd_set_dev_pwr_mode+0xeb/0x1b0 [ufshcd_core]
ufshcd_suspend+0x4bd/0x570 [ufshcd_core]
ufshcd_runtime_suspend+0x2e/0xc0 [ufshcd_core]

Any thoughts?

On a related issue, any pointers on the keyboard. I can't even find info on how it is connected (it isn't usb or at).

Thanks

<-----<<<

P.S. Technically, I'm using debian but it is a 5.13.0 kernel built from git with no changes.

Offline

Board footer

Powered by FluxBB