Hi I am using Fedora 32 with 5.8.11-200.fc32.x86_64 linux kernel. The specs of the Acer a315-56 Laptop is as follows: Intel core i5 1035g1 (Ice Lake) 8 GB DDR4 One NVMe SSD and one 2.5" SSD BIOS SATA Mode : AHCI The BIOS always see both the drives and the SATA mode is set to AHCI. Have the latest updates of Fedora and BIOS. The problem is when I boot the system only NVMe is visible and 2.5" SSD is not. But, if I put the computer to sleep, and then after resuming the session, the 2.5" SSD shows up. Before that it doesn't. If I run the following command upon boot " echo "- - -" > /sys/class/scsi_host/host0/scan " then I get the error message in the log : ata1: SATA link down (SStatus 1 SControl 300) After resuming from sleep, the 2.5" SSD shows up as removable drive and the relevant message in the log is : ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) The ouptut of "sudo lshw -c storage" upon resuming when both SSDs show up to the system: *-sata description: SATA controller product: Ice Lake-LP SATA Controller [AHCI mode] vendor: Intel Corporation physical id: 17 bus info: pci@0000:00:17.0 logical name: scsi0 version: 30 width: 32 bits clock: 66MHz capabilities: sata msi pm ahci_1.0 bus_master cap_list emulated configuration: driver=ahci latency=0 resources: irq:125 memory:4fc10000-4fc11fff memory:4fc14000-4fc140ff ioport:4080(size=8) ioport:4088(size=4) ioport:4060(size=32) memory:4fc13000-4fc137ff *-nvme description: NVMe device product: WDC WDS250G2B0C-00PXH0 vendor: Sandisk Corp physical id: 0 bus info: pci@0000:03:00.0 logical name: /dev/nvme0 version: 211070WD serial: 202142806846 width: 64 bits clock: 33MHz capabilities: nvme pm msi msix pciexpress nvm_express bus_master cap_list configuration: driver=nvme latency=0 nqn=nqn.2018-01.com.wdc:nguid:E8238FA6BF53-0001-001B448B46F8A623 state=live resources: irq:16 memory:4fa00000-4fa03fff memory:4fa04000-4fa040ff Steps to reproduce : Boot into Fedora 32 or linux Mint 20 installed on NVMe, only the NVMe will show up. To see the 2.5" SSD, one will have to put the computer to sleep and then resume it. Upon resuming the SSD will show up as a removable drive and will have to be mounted manually using root password. The problem persists if I replace the SATA SSD with 2.5" 1 TB HDD. Even that is detected only upon resuming from sleep. So, the problem is not with 2.5" SSD/HDD. One cannot even boot directly to Linux from the 2.5" SSD or HDD. Windows 10 can see both the SSDs but it boots only in "Optane RST mode without RAID" in BIOS. I believe that mode does not work with Linux. Windows 10 can boot from NVMe and from 2.5" SATA SSD. After ofcourse installing SATA drivers and all. The problem is not with Fedora. Same problem occurs in other linux distros like Linux Mint, Ubuntu. Even the Fedora Live USB or CloneZilla can see only NVMe and not SSD upon boot. Other people are also facing the same problem. Therefore, the problem is not with my laptop either. Others have put their grievances here on Acer forum: https://community.acer.com/en/discussion/comment/921105#Comment_921105 https://community.acer.com/en/discussion/comment/921106#Comment_921106 Output of lspci on my laptop. The SATA controller is visible on boot. But the 2.5" SATA SSD is not. [fedd@localhost ~] $ lspci 00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G1 (Ice Lake) (rev 07) 00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Management Engine Interface (rev 30) 00:17.0 SATA controller: Intel Corporation Ice Lake-LP SATA Controller [AHCI mode] (rev 30) 00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #9 (rev 30) 00:1d.1 PCI bridge: Intel Corporation Device 34b1 (rev 30) 00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30) 00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Smart Sound Technology Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI Controller (rev 30) 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) 03:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) Is the bug widespread? Probably not as not many people use two SSDs or One NVMe and one SSD/HDD in one laptop.
Could you provide output of command sudo lspci -vvnn -s 00:17 before and after suspend? They are probably different. Could you also attach full dmesg (/var/log/dmesg) after suspend?
*****Output upon Boot: [root@localhost fed] # sudo lspci -vvnn -s 00:17 00:17.0 SATA controller [0106]: Intel Corporation Ice Lake-LP SATA Controller [AHCI mode] [8086:34d3] (rev 30) (prog-if 01 [AHCI 1.0]) Subsystem: Acer Incorporated [ALI] Device [1025:1422] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 125 Region 0: Memory at 4fc10000 (32-bit, non-prefetchable) [size=8K] Region 1: Memory at 4fc14000 (32-bit, non-prefetchable) [size=256] Region 2: I/O ports at 4080 [size=8] Region 3: I/O ports at 4088 [size=4] Region 4: I/O ports at 4060 [size=32] Region 5: Memory at 4fc13000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00298 Data: 0000 Capabilities: [70] 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: [a8] SATA HBA v1.0 BAR4 Offset=00000004 Kernel driver in use: ahci *****After resuming from sleep when 2.5" SSD shows up!! [root@localhost fed] # sudo lspci -vvnn -s 00:17 00:17.0 SATA controller [0106]: Intel Corporation Ice Lake-LP SATA Controller [AHCI mode] [8086:34d3] (rev 30) (prog-if 01 [AHCI 1.0]) Subsystem: Acer Incorporated [ALI] Device [1025:1422] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 125 Region 0: Memory at 4fc10000 (32-bit, non-prefetchable) [size=8K] Region 1: Memory at 4fc14000 (32-bit, non-prefetchable) [size=256] Region 2: I/O ports at 4080 [size=8] Region 3: I/O ports at 4088 [size=4] Region 4: I/O ports at 4060 [size=32] Region 5: Memory at 4fc13000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00298 Data: 0000 Capabilities: [70] 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: [a8] SATA HBA v1.0 BAR4 Offset=00000004 Kernel driver in use: ahci *****Entire dmesg after resuming from sleep is added as an attachment as it was too big too post here
Created attachment 292717 [details] Full dmesg after resuming from sleep when 2.5" SSD is visible as requested. Full dmesg after resuming from sleep when 2.5" SSD is visible.
Fortunately it is not root fs. Does reloading kernel module help? sudo modprobe -rv ahci sudo modprobe -v ahci or maybe something like modprobe -v ahci mobile_lpm_policy=0 If reloading doesn't help you could try device sleep. After resume there is [ 211.413607] ahci 0000:00:17.0: port does not support device sleep However after resume device shows up. Edit /sys/class/scsi_host/host0/ on Edit /sys/class/scsi_host/host0/ auto. Powertop might be easiest way to do this.
Tried all this through tlp and tlpui. Didn't worked. :( Tried powertop changed everything to "Good" even then nothing...
Did you also change relevant device back to bad? Perhaps it is resume that helps. If that doesnt work there is more tools. You could compare lspci lshw dmidecode and acpidump with diff. https://wiki.ubuntu.com/FirmwareTestSuite/Reference/acpidump
[root@localhost Desktop] # diff lshw-pre lshw-post.txt 1,2c1 < [root@localhost fed] # lshw < localhost.localdomain --- > localhost.localdomain 36c35 < size: 1231MHz --- > size: 1189MHz 298c297 < resources: iomemory:600-5ff irq:139 memory:6001107000-6001107fff --- > resources: iomemory:600-5ff irq:129 memory:6001107000-6001107fff 304a304 > logical name: scsi0 308c308 < capabilities: sata msi pm ahci_1.0 bus_master cap_list --- > capabilities: sata msi pm ahci_1.0 bus_master cap_list emulated 310a311,332 > *-disk > description: ATA Disk > product: SanDisk SDSSDA12 > physical id: 0.0.0 > bus info: scsi@0:0.0.0 > logical name: /dev/sdb > version: 00RL > serial: 153056402699 > size: 111GiB (120GB) > capabilities: gpt-1.00 partitioned partitioned:gpt > configuration: ansiversion=5 > guid=ac02fce3-0e70-18e0-590a-088a82532497 > logicalsectorsize=512 sectorsize=512 > *-volume > description: EXT4 volume > vendor: Linux > physical id: 1 > bus info: scsi@0:0.0.0,1 > logical name: /dev/sdb1 > version: 1.0 > serial: 5401de88-f6d6-6a04-661d-15c131f906a1 > size: 111GiB > capabilities: journaled extended_attributes large_files > dir_nlink 64bit extents ext4 ext2 initialized > configuration: filesystem=ext4 modified=2020-10-03 > 07:06:11 state=clean 537d558 < [root@localhost Desktop] # diff acpidump.txt acpidump-post.txt [root@localhost Desktop] # diff dmidecode-pre dmidecode-post.txt 1d0 < [root@localhost fed] # dmidecode [root@localhost Desktop] # diff lspci-pre lspci-post.txt 1d0 < [root@localhost fed] # lspci 20d18 < [root@localhost Desktop] # Conclusion: No changes in lspci, dmidecode or acpi before/after sleep. lshw does change. All the changes are in communication controller and SATA LP Controller. First) The IRQ for communiation controller changes from 139 to 129. Pre: *-communication description: Communication controller product: Management Engine Interface vendor: Intel Corporation physical id: 16 bus info: pci@0000:00:16.0 version: 30 width: 64 bits clock: 33MHz capabilities: pm msi bus_master cap_list configuration: driver=mei_me latency=0 resources: iomemory:600-5ff irq:139 memory:6001107000-6001107fff Post: *-communication description: Communication controller product: Management Engine Interface vendor: Intel Corporation physical id: 16 bus info: pci@0000:00:16.0 version: 30 width: 64 bits clock: 33MHz capabilities: pm msi bus_master cap_list configuration: driver=mei_me latency=0 resources: iomemory:600-5ff irq:129 memory:6001107000-6001107fff Second) SATA controller's capabilities changes. A new capability "emulated" gets added after resume. Pre: *-sata description: SATA controller product: Ice Lake-LP SATA Controller [AHCI mode] vendor: Intel Corporation physical id: 17 bus info: pci@0000:00:17.0 version: 30 width: 32 bits clock: 66MHz capabilities: sata msi pm ahci_1.0 bus_master cap_list configuration: driver=ahci latency=0 resources: irq:125 memory:4fc10000-4fc11fff memory:4fc14000-4fc140ff ioport:4080(size=8) ioport:4088(size=4) ioport:4060(size=32) memory:4fc13000-4fc137ff Post: *-sata description: SATA controller product: Ice Lake-LP SATA Controller [AHCI mode] vendor: Intel Corporation physical id: 17 bus info: pci@0000:00:17.0 logical name: scsi0 version: 30 width: 32 bits clock: 66MHz capabilities: sata msi pm ahci_1.0 bus_master cap_list emulated configuration: driver=ahci latency=0 resources: irq:125 memory:4fc10000-4fc11fff memory:4fc14000-4fc140ff ioport:4080(size=8) ioport:4088(size=4) ioport:4060(size=32) memory:4fc13000-4fc137ff Third) Information regarding SATA 2." SSD is shown after resuming. Before sleep, nothing. Description: ATA Disk.
Created attachment 292777 [details] lshw before sleep Before sleep
Created attachment 292779 [details] lshw after sleep lshw after resuming from sleep is different than from before sleep.
Strange that lspci doesn't show IRQ change but lshw shows. Did you use lspci -vvnn? Could you boot with some parameters? https://help.ubuntu.com/community/DebuggingIRQProblems
No, I did not used lspci -vvnn. I ran commands without options as you told me too as I am not educated with these commands of Linux. Sry. Anyways, I ran lspci -vvnn and I found out that there are lots of changes pre and post. The changes are given below. The "Acer Incorporated [ALI] Device [1025:1422]" changes to "Device [0000:0000]". Also, the IRQs change is shown here too. PS: If you expected me to run any other command with any other options then let me know. :) [root@localhost Desktop] # diff lspci-pre.txt lspci-post.txt 110c110 < Interrupt: pin A routed to IRQ 139 --- > Interrupt: pin A routed to IRQ 129 116c116 < Address: 00000000fee00418 Data: 0000 --- > Address: 00000000fee002f8 Data: 0000 189c189 < Capabilities: [90] Subsystem: Acer Incorporated [ALI] Device [1025:1422] --- > Capabilities: [90] Subsystem: Device [0000:0000] 212c212 < PTMControl: Enabled:+ RootSelected:+ --- > PTMControl: Enabled:- RootSelected:- 272c272 < Capabilities: [90] Subsystem: Acer Incorporated [ALI] Device [1025:1422] --- > Capabilities: [90] Subsystem: Device [0000:0000] 280c280 < CESta: RxErr+ BadTLP- BadDLLP+ Rollover- Timeout- AdvNonFatalErr- --- > CESta: RxErr+ BadTLP- BadDLLP- Rollover- Timeout- > AdvNonFatalErr- 295c295 < PTMControl: Enabled:+ RootSelected:+ --- > PTMControl: Enabled:- RootSelected:- 355c355 < Capabilities: [90] Subsystem: Acer Incorporated [ALI] Device [1025:1422] --- > Capabilities: [90] Subsystem: Device [0000:0000] 378c378 < PTMControl: Enabled:+ RootSelected:+ --- > PTMControl: Enabled:- RootSelected:- 407c407 < Interrupt: pin A routed to IRQ 140 --- > Interrupt: pin A routed to IRQ 141 415c415 < Address: 00000000fee00438 Data: 0000 --- > Address: 00000000fee00458 Data: 0000 514c514 < Interrupt: pin A routed to IRQ 141 --- > Interrupt: pin A routed to IRQ 140 520c520 < Address: fee00458 Data: 0000 --- > Address: fee00438 Data: 0000 635c635 < LaneErrStat: 0 --- > LaneErrStat: LaneErr at lane: 0 1 2 3
Created attachment 292791 [details] lspci -vvnn before sleep
Created attachment 292793 [details] lspci -vvnn after resume
** More Analysis Acer Incorporated [ALI] Device [1025:1422] is used everywhere in lots of devices but it changes to Device [0000:0000] only for the components given below. Secondly, PTMControl is '-' after resume. Also, RootSelected is also '-' after resume. Before sleep, both are positive. Before sleep: 00:1d.1 PCI bridge [0604]: Intel Corporation Device [8086:34b1] (rev 30) (prog-if 00 [Normal decode]) Capabilities: [90] Subsystem: Acer Incorporated [ALI] Device [1025:1422] PTMControl: Enabled:+ RootSelected:+ After Resuming: 00:1d.1 PCI bridge [0604]: Intel Corporation Device [8086:34b1] (rev 30) (prog-if 00 [Normal decode]) Capabilities: [90] Subsystem: Device [0000:0000] PTMControl: Enabled:- RootSelected:- Before Sleep: 00:1d.0 PCI bridge [0604]: Intel Corporation Ice Lake-LP PCI Express Root Port #9 [8086:34b0] (rev 30) (prog-if 00 [Normal decode]) Capabilities: [90] Subsystem: Acer Incorporated [ALI] Device [1025:1422] PTMControl: Enabled:+ RootSelected:+ After Resuming: 00:1d.0 PCI bridge [0604]: Intel Corporation Ice Lake-LP PCI Express Root Port #9 [8086:34b0] (rev 30) (prog-if 00 [Normal decode]) Capabilities: [90] Subsystem: Device [0000:0000] PTMControl: Enabled:- RootSelected:-
Could you attach: sudo dmidecode > dmidecode.txt
Created attachment 292803 [details] dmidecode before sleep sudo dmidecode before sleep
Created attachment 292805 [details] dmidecode after resuming dmidecode after resuming is the same before sleep
Could you boot once with the noapic kernel parameter? https://wiki.ubuntu.com/Kernel/KernelBootParameters Temporarily Add a Kernel Boot Parameter for Testing It should be very similar with other distros, even with live USB.
Tried these parameters: noapic acpi=off Same result!! 2.5" SSD does not show up on boot but does show up upon resuming the system.
Could you boot once with pci=routeirq boot parameter? Is "sudo lsusb -v" different after suspend? This doesn't need any kernel parameters.
1) The pci=routeirq didn't effected anything. 2.5" SSD shows up only after resuming. 2) lsusb -v shows difference. Upon boot port 10 is 0000.0103 powr enable connect. After resuming it changes to 0000.0123 power L1 enable connect as given below. [root@localhost Desktop] # diff lsusb-pre.txt lsusb-post.txt 1153c1153 < Port 10: 0000.0103 power enable connect --- > Port 10: 0000.0123 power L1 enable connect
Created attachment 293029 [details] lsusb -v before sleep lsusb -v before sleep
Created attachment 293031 [details] lsusb -v after resuming lsusb -v after resuming when 2.5" SSD shows up. There's slight difference in port 10.
Is there any other info I can provide?
Are you able to install it on your NVME drive and use Linux from NVME?
Yes, Linus is able to detect NVMe and on it, Linux works perfectly.
I also have Acer a315-56 and I am also facing the same issue. I was able to install Manjaro on HDD, after suspending and resuming HDD was showing as Removable drive. After Installation, I am unable to boot in Manjaro from Grub as it gives hibernation device cannot found you are now dropped into an emergency shell. The issue is not with HDD as I replaced it with SSD to cross check and still linux doesnt detects it. Windows Installer detects HDD successfully.
After suspend there is pci-id change. It seems some fortunate fallback driver works then.
There must be a way to force the driver to work from the grub bootloader itself.
Is there any way to know which driver has problems and who is maintaining it? Is Intel maintaining it? Or is it some generic driver? If it's intel, then I can probably chase them on emails and forums and everywhere else. :)
Created attachment 294235 [details] attachment-2815-0.html I am trying to write a driver myself for this issue. On Sat, 19 Dec, 2020, 8:45 pm , <bugzilla-daemon@bugzilla.kernel.org> wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=209419 > > --- Comment #30 from rohit.suman@yahoo.com --- > Is there any way to know which driver has problems and who is maintaining > it? > Is Intel maintaining it? Or is it some generic driver? If it's intel, then > I > can probably chase them on emails and forums and everywhere else. :) > > -- > You may reply to this email to add a comment. > > You are receiving this mail because: > You are on the CC list for the bug.
Hello, I also have an Acer a315-56, and am having the same problem. The laptop doesn't have an SSD - just a 1 TB HDD. I have managed to install Ubuntu Studio 20.10 as a dual-boot with Windows 10, by: - Disabling Fast Boot and Secure Boot - Booting into a live USB - Closing and re-opening the laptop lid (to make Linux see the HDD). - Proceeding with the usual installation steps. - Running Boot-Repair from the Live USB session (as the GRUB bootloader didn't show up at first). However I can't actually boot into Ubuntu because after I select it, it gets stuck and reverts to BusyBox (saying that my HDD doesn't exist). And of course I can't just close/open the lid before the OS has even booted. Has anyone made any progress on this? I don't really want to fork out for an NVME SSD when I've just spent so much on a computer with a perfectly good hard drive.
Hello, For information, I have the same problem on an Acer Aspire A317-52. As a workaround to make the hard disk detected, I was able to use the following command successfully: rtcwake -u -m mem --date +2s It basically puts the system on sleep for 2s then wakes it up. Adding this command to initramfs to have it automatically executed on boot should even allow booting from the previously undetected hard disk. Of course, it is only a workaround, and I am waiting for the proper fix in the kernel driver, but I thought I would mention it here to help anyone who is waiting for the fix.
Do you know how to add this command "rtcwake -u -m mem --date +2s" to initramfs on Fedora 33? I tried to find it out, asked Reddit, but couldn't get it done.
Archlinux, Acer Extensa 15 - the same problem with Samsung-Evo SSD (and other HDD..SSD)... Update BIOS with no results. :-( At present, I am using from time-to-time "suspend-sleep"... but its not good... During research I find the next info: "The Intel® Memory and Storage Tool (Intel® MAS) is a drive management tool for Intel® SSDs and Intel®" https://downloadcenter.intel.com/download/30509/Intel-Memory-and-Storage-Tool-CLI-Command-Line-Interface- Is it can help? May be some professionals here can advise - how we can use it to solve our problem? like its solved in Windows when we use a driver for removable ssd? Its work for me using Samsung EVO SSD - but in windows...
I have also same issue with Acer Extensa 15
I had this problem with a 2T WD Sata SSD. I solved it by passing the following parameters to the kernel: "libata.force=1.5,udma7" Check the following url (https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html) to tune the parameters to match your hardware.