Hi, I'm having an issue with my Thinkpad P70 laptop/workstation. This system is a dual boot, windows 10 pro and centos 7. I have not needed to use the cdrom until now, however the system does not see it in /dev. I know the cdrom works as I can use it in windows 10 and when initially installing centos 7, I installed from dvd media. I'm not sure what to check. I do not see anything related in dmesg. I have previous copies of kernel on the system and tried booting with 3.10.0-957.el7.x86_64 but I'm seeing the same.
---------- # uname -r 3.10.0-957.21.3.el7.x86_64
# lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics P530 (rev 06) 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31) 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) 00:16.3 Serial controller: Intel Corporation 100 Series/C230 Series Chipset Family KT Redirection (rev 31) 00:17.0 RAID bus controller: Intel Corporation SATA Controller [RAID mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1) 00:1c.2 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 (rev f1) 00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1) 00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #13 (rev f1) 00:1f.0 ISA bridge: Intel Corporation CM236 Chipset LPC/eSPI Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31) 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM (rev 31) 01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M600M] (rev a2) 04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) 05:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 06:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 06:01.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 06:02.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 06:04.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 07:00.0 System peripheral: Intel Corporation DSL6540 Thunderbolt 3 NHI [Alpine Ridge 4C 2015] (rev ff) 3b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine Ridge] 70:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
# hwinfo --block --short disk: /dev/sda Samsung Portable SSD T5 /dev/sdb Samsung Portable SSD T5 Samsung Electronics Portable SSD T5 Samsung Electronics Portable SSD T5 partition: /dev/sda1 Partition /dev/sda2 Partition /dev/sda3 Partition /dev/sda4 Partition /dev/sdb1 Partition /dev/sdb2 Partition /dev/sdb3 Partition
Any suggestions? thanks ~d
On Sun, 2019-06-23 at 22:13 -0400, doug schmidt wrote:
Hi, I'm having an issue with my Thinkpad P70 laptop/workstation. This system is a dual boot, windows 10 pro and centos 7. I have not needed to use the cdrom until now, however the system does not see it in /dev. I know the cdrom works as I can use it in windows 10 and when initially installing centos 7, I installed from dvd media. I'm not sure what to check.
By default CDROM drives are usually /dev/sr*
# hwinfo --block --short
CD drives are not block devices. Why not use 'hwinfo --cdrom'?
# hwinfo --cdrom --short cdrom: /dev/sr0 TSSTcorp DVD+-RW TS-H653H
P.
On Mon, Jun 24, 2019 at 3:35 AM Pete Biggs pete@biggs.org.uk wrote:
On Sun, 2019-06-23 at 22:13 -0400, doug schmidt wrote:
Hi, I'm having an issue with my Thinkpad P70 laptop/workstation. This system
is
a dual boot, windows 10 pro and centos 7. I have not needed to use the cdrom until
now,
however the system does not see it in /dev. I know the cdrom works as I
can
use it in windows 10 and when initially installing centos 7, I installed from dvd media. I'm not sure what to check.
By default CDROM drives are usually /dev/sr*
# hwinfo --block --short
CD drives are not block devices. Why not use 'hwinfo --cdrom'?
# hwinfo --cdrom --short cdrom: /dev/sr0 TSSTcorp DVD+-RW TS-H653H
Hi Pete, I tried --cdrom, just forgot to include in original post; While searching google, I saw a post where --block --short included cdrom output.
[root@darkness ~]# ls -al /dev/sr* ls: cannot access /dev/sr*: No such file or directory [root@darkness ~]# ls /dev/s* /dev/sda /dev/sda3 /dev/sdb1 /dev/sg0 /dev/stderr /dev/sda1 /dev/sda4 /dev/sdb2 /dev/sg1 /dev/stdin /dev/sda2 /dev/sdb /dev/sdb3 /dev/snapshot /dev/stdout [root@darkness ~]# hwinfo --cdrom [root@darkness ~]#
thanks ~d
[root@darkness ~]# ls -al /dev/sr* ls: cannot access /dev/sr*: No such file or directory [root@darkness ~]# ls /dev/s* /dev/sda /dev/sda3 /dev/sdb1 /dev/sg0 /dev/stderr /dev/sda1 /dev/sda4 /dev/sdb2 /dev/sg1 /dev/stdin /dev/sda2 /dev/sdb /dev/sdb3 /dev/snapshot /dev/stdout [root@darkness ~]# hwinfo --cdrom [root@darkness ~]#
Presumably it is a SATA CD/DVD - if so you need to go through the output of dmesg to see if it is detected on one of the SATA lines - possibly grepping for 'ata' should show something. If it's not even seeing it on a SATA line, then there is something strange with the hardware or bios configuration.
P.
[root@darkness ~]# ls -al /dev/sr* ls: cannot access /dev/sr*: No such file or directory [root@darkness ~]# ls /dev/s* /dev/sda /dev/sda3 /dev/sdb1 /dev/sg0 /dev/stderr /dev/sda1 /dev/sda4 /dev/sdb2 /dev/sg1 /dev/stdin /dev/sda2 /dev/sdb /dev/sdb3 /dev/snapshot /dev/stdout [root@darkness ~]# hwinfo --cdrom [root@darkness ~]#
Presumably it is a SATA CD/DVD - if so you need to go through the output of dmesg to see if it is detected on one of the SATA lines - possibly grepping for 'ata' should show something. If it's not even seeing it on a SATA line, then there is something strange with the hardware or bios configuration.
windows 10 is listing device as; PLDS DVD-RW DU8A6SH
google search is showing spec is SATA (the cdrom can also be swapped out/replaced with a second SATA HDD)
this is what I see in dmesg;
[ 1.835374] libata version 3.00 loaded. [ 1.879093] ata1: DUMMY [ 1.879096] ata2: DUMMY [ 1.879099] ata3: SATA max UDMA/133 abar m524288@0xc5700000 port 0xc5700200 irq 136 [ 1.879102] ata4: SATA max UDMA/133 abar m524288@0xc5700000 port 0xc5700280 irq 137 [ 2.183682] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 2.183825] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 7.183893] ata3.00: qc timeout (cmd 0xec) [ 7.183908] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 7.183960] ata4.00: qc timeout (cmd 0xa1) [ 7.183974] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 7.488894] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 7.488931] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 17.488919] ata3.00: qc timeout (cmd 0xec) [ 17.488934] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 17.488942] ata3: limiting SATA link speed to 3.0 Gbps [ 17.488964] ata4.00: qc timeout (cmd 0xa1) [ 17.488979] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 17.793923] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 17.794894] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 47.794008] ata3.00: qc timeout (cmd 0xec) [ 47.794023] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 47.794880] ata4.00: qc timeout (cmd 0xa1) [ 47.794897] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 48.099012] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 48.099884] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
I'm seeing this from dmidecode; (I'll reboot and look over the BIOS settings) Last I remember being in the BIOS, I don't recall seeing anything that may be an issue.
BIOS Information Vendor: LENOVO Version: N1DETA4W (2.30 ) Release Date: 05/09/2019 Address: 0xE0000 Runtime Size: 128 kB ROM Size: 16 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 3.5"/720 kB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 2.30 Firmware Revision: 1.18
Handle 0x000F, DMI type 1, 27 bytes
thanks ~d
[ 2.183682] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 2.183825] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 7.183893] ata3.00: qc timeout (cmd 0xec) [ 7.183908] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 7.183960] ata4.00: qc timeout (cmd 0xa1) [ 7.183974] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 7.488894] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 7.488931] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 17.488919] ata3.00: qc timeout (cmd 0xec) [ 17.488934] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 17.488942] ata3: limiting SATA link speed to 3.0 Gbps [ 17.488964] ata4.00: qc timeout (cmd 0xa1) [ 17.488979] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 17.793923] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 17.794894] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 47.794008] ata3.00: qc timeout (cmd 0xec) [ 47.794023] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 47.794880] ata4.00: qc timeout (cmd 0xa1) [ 47.794897] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 48.099012] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 48.099884] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
So lots of errors there - the "failed to IDENTIFY" means there is something present but it's not responding to the commands. These sorts of things are almost always down to the SATA BIOS settings or buggy SATA hardware. Make sure the BIOS has the SATA settings as AHCI and if that doesn't improve things then set "noapic" and/or "acpi=off" on the kernel command line.
Googling for "qc timeout (cmd 0xec)" gives lots of hits.
Be warned though, changing the SATA BIOS settings may have an adverse affect on the Windows install - it may fail to recognise your disks.
P.
Also, make sure your BIOS is the latest version for your motherboard!
Jay
[ 2.183682] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 2.183825] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 7.183893] ata3.00: qc timeout (cmd 0xec) [ 7.183908] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 7.183960] ata4.00: qc timeout (cmd 0xa1) [ 7.183974] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 7.488894] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 7.488931] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 17.488919] ata3.00: qc timeout (cmd 0xec) [ 17.488934] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 17.488942] ata3: limiting SATA link speed to 3.0 Gbps [ 17.488964] ata4.00: qc timeout (cmd 0xa1) [ 17.488979] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 17.793923] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 17.794894] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 47.794008] ata3.00: qc timeout (cmd 0xec) [ 47.794023] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 47.794880] ata4.00: qc timeout (cmd 0xa1) [ 47.794897] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 48.099012] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 48.099884] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
So lots of errors there - the "failed to IDENTIFY" means there is something present but it's not responding to the commands. These sorts of things are almost always down to the SATA BIOS settings or buggy SATA hardware. Make sure the BIOS has the SATA settings as AHCI and if that doesn't improve things then set "noapic" and/or "acpi=off" on the kernel command line.
Googling for "qc timeout (cmd 0xec)" gives lots of hits.
Be warned though, changing the SATA BIOS settings may have an adverse affect on the Windows install - it may fail to recognise your disks.
P.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
-
doug schmidt -
Jay Hart -
Pete Biggs