Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1053937: debian-installer: installer does not detect internal UFS-drive
275 views
Skip to first unread message
Patrick Rudin
Oct 14, 2023, 12:20:05 PM10/14/23
to
Package: debian-installer
Severity: important
Tags: d-i
X-Debbugs-Cc: tax...@gmx.ch
I have a Microsoft Surface Go 4 Tablet, which has an internal 256 GB UFS-Drive.
Debian Live works fine, but its not possible to install Debian: When I get to
partitioning, the installer does not see the drive (the ubuntu installer does)
and only shows my installer-stick.
I guess the installer would need the ufshci-module to recognize the internal
UFS-Flash.
Tried with the stable-installer from Debian 12 and also with the daily build
from testing, no difference.
-- System Information:
Debian Release: 12.1
APT prefers bookworm
APT policy: (500, 'bookworm'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-10-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Severity: important
Tags: d-i
X-Debbugs-Cc: tax...@gmx.ch
I have a Microsoft Surface Go 4 Tablet, which has an internal 256 GB UFS-Drive.
Debian Live works fine, but its not possible to install Debian: When I get to
partitioning, the installer does not see the drive (the ubuntu installer does)
and only shows my installer-stick.
I guess the installer would need the ufshci-module to recognize the internal
UFS-Flash.
Tried with the stable-installer from Debian 12 and also with the daily build
from testing, no difference.
-- System Information:
Debian Release: 12.1
APT prefers bookworm
APT policy: (500, 'bookworm'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-10-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Patrick Rudin
Oct 15, 2023, 8:10:04 AM10/15/23
to
Correction: If I use the Calamares-Installer directly from the debian live-system, it seems to work fine: I can see the internal disk and all the partitions.
So this bug report concerns only the official debian 12 netinstall.
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.2.0-amd64-netinst.iso
regards
Patrick
So this bug report concerns only the official debian 12 netinstall.
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.2.0-amd64-netinst.iso
regards
Patrick
Cyril Brulebois
Oct 15, 2023, 12:10:04 PM10/15/23
to
Hi Patrick,
and thanks for your report.
Patrick Rudin <tax...@gmx.ch> (2023-10-14):
the industry calls UFSHCI, and seems to be shipped as ufshcd-core.ko
(ufs/core) and ufshcd-pci.ko (ufs/host). Those are likely to be
sufficient as the only dependency is between them (no extra modules
should be needed), and I can load both of them in a test VM. But we've
already seen that sometimes another seemingly unrelated module might be
needed (I did spot a softdep on a governor, so I'm not sure about the
runtime when such a device is present).
I've built a test netboot-gtk installation image; contrary to a full
netinst ISO, there's no firmware in there, but I thought it might be
good enough for you to test and report whether the storage appears,
without going through the whole installation process.
https://people.debian.org/~kibi/bug-1053937/
Your follow-up about Live was very nice as well. Hopefully that fits
your immediate needs and lets you install Debian without waiting on a
fix in debian-installer; a full netinst ISO could be arranged
otherwise.
Cheers,
--
Cyril Brulebois (ki...@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
and thanks for your report.
Patrick Rudin <tax...@gmx.ch> (2023-10-14):
> I have a Microsoft Surface Go 4 Tablet, which has an internal 256 GB UFS-Drive.
> Debian Live works fine, but its not possible to install Debian: When I get to
> partitioning, the installer does not see the drive (the ubuntu installer does)
> and only shows my installer-stick.
>
> I guess the installer would need the ufshci-module to recognize the internal
> UFS-Flash.
Looking around, it seems “ufshci-module” is a best guess name for what
> Debian Live works fine, but its not possible to install Debian: When I get to
> partitioning, the installer does not see the drive (the ubuntu installer does)
> and only shows my installer-stick.
>
> I guess the installer would need the ufshci-module to recognize the internal
> UFS-Flash.
the industry calls UFSHCI, and seems to be shipped as ufshcd-core.ko
(ufs/core) and ufshcd-pci.ko (ufs/host). Those are likely to be
sufficient as the only dependency is between them (no extra modules
should be needed), and I can load both of them in a test VM. But we've
already seen that sometimes another seemingly unrelated module might be
needed (I did spot a softdep on a governor, so I'm not sure about the
runtime when such a device is present).
I've built a test netboot-gtk installation image; contrary to a full
netinst ISO, there's no firmware in there, but I thought it might be
good enough for you to test and report whether the storage appears,
without going through the whole installation process.
https://people.debian.org/~kibi/bug-1053937/
Your follow-up about Live was very nice as well. Hopefully that fits
your immediate needs and lets you install Debian without waiting on a
fix in debian-installer; a full netinst ISO could be arranged
otherwise.
Cheers,
--
Cyril Brulebois (ki...@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
Patrick Rudin
Oct 15, 2023, 8:00:04 PM10/15/23
to
Hi Cyril :)
Cyril Brulebois wrote:
> Looking around, it seems “ufshci-module” is a best guess name for what
> the industry calls UFSHCI, and seems to be shipped as ufshcd-core.ko
> (ufs/core) and ufshcd-pci.ko (ufs/host).
$ lsmod | grep ufs
ufshcd_pci 20480 0
ufshcd_core 262144 3 ufshcd_pci
scsi_mod 286720 3 sd_mod,sg,ufshcd_core
> I've built a test netboot-gtk installation image; contrary to a full
> netinst ISO, there's no firmware in there, but I thought it might be
> good enough for you to test and report whether the storage appears,
> without going through the whole installation process.
> https://people.debian.org/~kibi/bug-1053937/
YES! Thank you, works perfectly. I can see the drive and all partitions.
Of course an alpha installer for trixie with ufs would be nice, as most people with a surface go 4 probably want Gnome 45...
By the way, this is the lspci -vv entry of the drive:
00:12.7 Universal Flash Storage controller: Intel Corporation Device 54ff (prog-if 01 [UFSHCI])
Subsystem: Intel Corporation Device 7270
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin C routed to IRQ 18
IOMMU group: 7
Region 0: Memory at 60e9153000 (64-bit, non-prefetchable) [size=4K]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] Vendor Specific Information: Len=14 <?>
Kernel driver in use: ufshcd
Kernel modules: ufshcd_pci
hwinfo:
29: PCI 12.7: 0109 Mass storage controller
[Created at pci.386]
Unique ID: Gd_A.0f3BFfhdmt1
SysFS ID: /devices/pci0000:00/0000:00:12.7
SysFS BusID: 0000:00:12.7
Hardware Class: storage
Model: "Intel Mass storage controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x54ff
SubVendor: pci 0x8086 "Intel Corporation"
SubDevice: pci 0x7270
Driver: "ufshcd"
Driver Modules: "ufshcd_pci"
Memory Range: 0x60e9153000-0x60e9153fff (rw,non-prefetchable)
IRQ: 18 (18496 events)
Module Alias: "pci:v00008086d000054FFsv00008086sd00007270bc01sc09i01"
Driver Info #0:
Driver Status: ufshcd_pci is active
Driver Activation Cmd: "modprobe ufshcd_pci"
Config Status: cfg=new, avail=yes, need=no, active=unknown
40: SCSI 00.0: 10600 Disk
[Created at block.255]
Unique ID: R7kM.7vZj0wQ2tpB
Parent ID: Gd_A.0f3BFfhdmt1
SysFS ID: /class/block/sda
SysFS BusID: 0:0:0:0
SysFS Device Link: /devices/pci0000:00/0000:00:12.7/host0/target0:0:0/0:0:0:0
Hardware Class: disk
Model: "SKhynix HN8T15DEHKX075"
Vendor: "SKhynix"
Device: "HN8T15DEHKX075"
Revision: "A801"
Serial ID: "2F0F13D97400"
Driver: "ufshcd", "sd"
Driver Modules: "ufshcd_pci", "sd_mod"
Device File: /dev/sda (/dev/sg3)
Device Files: /dev/sda, /dev/disk/by-diskseq/1, /dev/disk/by-id/scsi-1SKhynix, /dev/disk/by-path/pci-0000:00:12.7-scsi-0:0:0:0
Device Number: block 8:0-8:15 (char 21:3)
BIOS id: 0x80
Geometry (Logical): CHS 3889/255/63
Size: 62486528 sectors a 4096 bytes
Capacity: 238 GB (255944818688 bytes)
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #29 (Mass storage controller)
Thanks for all your work!
Cyril Brulebois wrote:
> Looking around, it seems “ufshci-module” is a best guess name for what
> the industry calls UFSHCI, and seems to be shipped as ufshcd-core.ko
> (ufs/core) and ufshcd-pci.ko (ufs/host).
ufshcd_pci 20480 0
ufshcd_core 262144 3 ufshcd_pci
scsi_mod 286720 3 sd_mod,sg,ufshcd_core
> I've built a test netboot-gtk installation image; contrary to a full
> netinst ISO, there's no firmware in there, but I thought it might be
> good enough for you to test and report whether the storage appears,
> without going through the whole installation process.
> https://people.debian.org/~kibi/bug-1053937/
Of course an alpha installer for trixie with ufs would be nice, as most people with a surface go 4 probably want Gnome 45...
By the way, this is the lspci -vv entry of the drive:
00:12.7 Universal Flash Storage controller: Intel Corporation Device 54ff (prog-if 01 [UFSHCI])
Subsystem: Intel Corporation Device 7270
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin C routed to IRQ 18
IOMMU group: 7
Region 0: Memory at 60e9153000 (64-bit, non-prefetchable) [size=4K]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] Vendor Specific Information: Len=14 <?>
Kernel driver in use: ufshcd
Kernel modules: ufshcd_pci
hwinfo:
29: PCI 12.7: 0109 Mass storage controller
[Created at pci.386]
Unique ID: Gd_A.0f3BFfhdmt1
SysFS ID: /devices/pci0000:00/0000:00:12.7
SysFS BusID: 0000:00:12.7
Hardware Class: storage
Model: "Intel Mass storage controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x54ff
SubVendor: pci 0x8086 "Intel Corporation"
SubDevice: pci 0x7270
Driver: "ufshcd"
Driver Modules: "ufshcd_pci"
Memory Range: 0x60e9153000-0x60e9153fff (rw,non-prefetchable)
IRQ: 18 (18496 events)
Module Alias: "pci:v00008086d000054FFsv00008086sd00007270bc01sc09i01"
Driver Info #0:
Driver Status: ufshcd_pci is active
Driver Activation Cmd: "modprobe ufshcd_pci"
Config Status: cfg=new, avail=yes, need=no, active=unknown
40: SCSI 00.0: 10600 Disk
[Created at block.255]
Unique ID: R7kM.7vZj0wQ2tpB
Parent ID: Gd_A.0f3BFfhdmt1
SysFS ID: /class/block/sda
SysFS BusID: 0:0:0:0
SysFS Device Link: /devices/pci0000:00/0000:00:12.7/host0/target0:0:0/0:0:0:0
Hardware Class: disk
Model: "SKhynix HN8T15DEHKX075"
Vendor: "SKhynix"
Device: "HN8T15DEHKX075"
Revision: "A801"
Serial ID: "2F0F13D97400"
Driver: "ufshcd", "sd"
Driver Modules: "ufshcd_pci", "sd_mod"
Device File: /dev/sda (/dev/sg3)
Device Files: /dev/sda, /dev/disk/by-diskseq/1, /dev/disk/by-id/scsi-1SKhynix, /dev/disk/by-path/pci-0000:00:12.7-scsi-0:0:0:0
Device Number: block 8:0-8:15 (char 21:3)
BIOS id: 0x80
Geometry (Logical): CHS 3889/255/63
Size: 62486528 sectors a 4096 bytes
Capacity: 238 GB (255944818688 bytes)
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #29 (Mass storage controller)
Thanks for all your work!
0 new messages