Marc Chamberlin composed on 2016-12-16 19:06 (UTC-0800):

Felix Miata wrote:

...

Marc Chamberlin composed on 2016-12-16 18:40 (UTC-0800):

...

...

Hi - I downloaded the ISO image for Leap 42.2 to install it on my brand spanking new ASUS laptop

...

Start by giving us the model number of your Asus. It might be too new to be fully supported out of the box.

Oh sure - ASUS ROG G752VS OC Edition Not that I am advertising for ASUS but you can see more info about it on Amazon where I purchased it - https://www.amazon.com/gp/product/B01K1JW5DY/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1

That has Skylake-K and Nvidia "with the latest NVIDIA® GeForce® GTX™ 10 series graphics".[1] Did you Google before you bought it to see how new that hardware is? On October 18, 2016 http://www.laptopmag.com/reviews/laptops/asus-g752v wrote the GTX 1070 is "brand-new". This smells bad for 42.2, only just released last month with kernel 4.4, while Tumbleweed is up to 4.8.13. Maybe you can get TW to install? Is it too late to take it back? See: http://www.pcworld.com/article/2911459/why-nvidia-graphics-cards-are-the-wor... [1] https://www.asus.com/us/Notebooks/G752VS-OC-Edition/ -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/16/2016 11:31 PM, John Andersen wrote:

Kernel 4.9 is probably what you want to get the best out of Skylake.

I don't know where you get that for opensuse.

*sigh* Kernel Stable, of course! # zypper info kernel-default Information for package kernel-default: --------------------------------------- Repository: kernel_Stable Name: kernel-default Version: 4.9.0-1.1.g8c92422 Arch: x86_64 Vendor: obs://build.opensuse.org/Kernel Installed: Yes Status: up-to-date Installed Size: 240.0 MiB Summary: The Standard Kernel Description: The standard kernel for both uniprocessor and multiprocessor systems. Source Timestamp: 2016-12-12 16:54:28 +0100 GIT Revision: 8c92422210c5a088e1b7edb6ea27c8b951f564a4 GIT Branch: stable And, once again, that's at http://download.opensuse.org/repositories/Kernel:/stable/standard/ -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Marc Chamberlin composed on 2016-12-16 21:20 (UTC-0800):

I can give Tumbleweed a shot, but pushing back a bit, why are you assuming that nVidia is the cause of the problem I am experiencing?

The combination of Skylake together with "latest Nvidia" loudly suggests "too new for Linux". Skylake seems to have been taking a long time to get support right. IIRC, I've often seen trying a BIOS update to be the first course of action with Skylake trouble, closely followed by newer kernel, the latter often being a formidable obstacle at stable distro release installation time. If TW sounds too unstable to suit you, maybe give Fedora 25 a go until 42.3 is available. It was released with kernel 4.8.8 around the same time as 42.2, is already up to 4.8.14, and will be getting 4.9 automatically before long. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata composed on 2016-12-17 00:43 (UTC-0500):

I've often seen trying a BIOS update to be the first course of action with Skylake trouble

Did you ever check for a BIOS update? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

this looks like the same problem, seems to occur on all linux: https://rog.asus.com/forum/showthread.php?79205-Cannot-see-NVMe-M-2-Samsung-... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/18/2016 1:40 PM, nicholas cunliffe wrote:

this looks like the same problem, seems to occur on all linux: https://rog.asus.com/forum/showthread.php?79205-Cannot-see-NVMe-M-2-Samsung-...

Thanks Nicholas, you did some digging! Correct me though, if I am wrong and misunderstanding this thread... It appears that this is about how to make it possible to boot from an SSD, and the problem that is being addressed is the fact that the BIOS did not have a module for supporting AHCI, just for RAID. So the solution being presented was how to add the AHCI support to the BIOS. As I noted in my previous post, it appears that in my BIOS I do have the option to switch to AHCI, so apparently it seems this has been addressed by AMI and ASUS. And as I also mentioned, I tried to switch to AHCI but it gave the boot loader for Windows 10 troubles and I was no longer able to boot up Windows 10. So I am not sure how to make these two OS's play nice with each other, and still looking for a workaround... Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

sdm composed on 2016-12-18 14:24 (UTC-0800):

Marc Chamberlin wrote:

...

I also mentioned, I tried to switch to AHCI but it gave the boot loader for Windows 10 troubles and I was no longer able to boot up Windows 10. So I am not sure how to make these two OS's play nice with each other, and still looking for a workaround...

If Win 10 was installed at the factory in IDE mode and you switch to AHCI in the BIOS, the boot will fail. You have to dig into the registry and make some modifications of some values. The process for doing this is actually a little different on Windows 10 than 7, but it's quite simple. After you make the changes in the registry for AHCI booting, you go into the BIOS and switch to AHCI.

Or, change the BIOS first, then perform a Windows boot repair, then install openSUSE. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/18/2016 7:28 PM, Andrei Borzenkov wrote:

19.12.2016 01:36, Felix Miata пишет:

...

sdm composed on 2016-12-18 14:24 (UTC-0800):

...

Marc Chamberlin wrote:

...

I also mentioned, I tried to switch to AHCI but it gave the boot loader for Windows 10 troubles and I was no longer able to boot up Windows 10. So I am not sure how to make these two OS's play nice with each other, and still looking for a workaround... It is possible to fix Windows if changing mode proves to fix the issue with linux.

...

...

If Win 10 was installed at the factory in IDE mode and you switch to AHCI in the BIOS, the boot will fail. You have to dig into the registry and make some modifications of some values. The process for doing this is actually a little different on Windows 10 than 7, but it's quite simple. After you make the changes in the registry for AHCI booting, you go into the BIOS and switch to AHCI. Or, change the BIOS first, then perform a Windows boot repair, then install openSUSE. No. Change BIOS, test if it helps with Linux first, then fix Windows.

Note that using AHCI mode /may/ result in suboptimal power saving also under Windows.

Thanks Andre - I just responded to the same suggestions from Carlos and SDM but had a few more questions. I think the consensus is to go ahead and switch the BIOS to AHCI and then try to install Leap 42.2, which I will attempt as soon as someone can answer my questions about how to configure GRUB for this "test". And I am not worried about power savings, most of the time I use my laptop it is connected to one of our local dams anywise! Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 18 December 2016 at 23:11, Marc Chamberlin <marc@marcchamberlin.com> wrote:

On 12/18/2016 1:40 PM, nicholas cunliffe wrote:

...

this looks like the same problem, seems to occur on all linux:

https://rog.asus.com/forum/showthread.php?79205-Cannot-see-NVMe-M-2-Samsung-...

Thanks Nicholas, you did some digging! Correct me though, if I am wrong and misunderstanding this thread... It appears that this is about how to make it possible to boot from an SSD, and the problem that is being addressed is the fact that the BIOS did not have a module for supporting AHCI, just for RAID. So the solution being presented was how to add the AHCI support to the BIOS. As I noted in my previous post, it appears that in my BIOS I do have the option to switch to AHCI, so apparently it seems this has been addressed by AMI and ASUS.

And as I also mentioned, I tried to switch to AHCI but it gave the boot loader for Windows 10 troubles and I was no longer able to boot up Windows 10. So I am not sure how to make these two OS's play nice with each other, and still looking for a workaround...

Marc...

yes i did some more digging and found recent threads, confirming the bios update, and like you, cannot then boot win10 with AHCI. So this would now appear a windows/drive problem? maybe consult google again regarding nvme/ahci/raid/windows. If windows supports ahci then there will always be repair/reinstall if all else fails. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/18/2016 5:39 PM, sdm wrote:

On 12/18/2016 02:37 PM, nicholas cunliffe wrote:

...

On 18 December 2016 at 23:11, Marc Chamberlin <marc@marcchamberlin.com> wrote:

...

On 12/18/2016 1:40 PM, nicholas cunliffe wrote:

...

this looks like the same problem, seems to occur on all linux:

https://rog.asus.com/forum/showthread.php?79205-Cannot-see-NVMe-M-2-Samsung-...

Thanks Nicholas, you did some digging! Correct me though, if I am wrong and misunderstanding this thread... It appears that this is about how to make it possible to boot from an SSD, and the problem that is being addressed is the fact that the BIOS did not have a module for supporting AHCI, just for RAID. So the solution being presented was how to add the AHCI support to the BIOS. As I noted in my previous post, it appears that in my BIOS I do have the option to switch to AHCI, so apparently it seems this has been addressed by AMI and ASUS.

And as I also mentioned, I tried to switch to AHCI but it gave the boot loader for Windows 10 troubles and I was no longer able to boot up Windows 10. So I am not sure how to make these two OS's play nice with each other, and still looking for a workaround...

Marc... yes i did some more digging and found recent threads, confirming the bios update, and like you, cannot then boot win10 with AHCI. So this would now appear a windows/drive problem? maybe consult google again regarding nvme/ahci/raid/windows. If windows supports ahci then there will always be repair/reinstall if all else fails.

Windows doesn't boot in AHCI mode because Windows wasn't installed in AHCI mode, it was in IDE mode. If you switch, it won't boot. Instructions on how to do this are found by doing a Google search. So for testing I would take the Laptop out of RAID mode, forget about if Windows boots or not, switch to AHCI mode in the BIOS, and then see if the openSUSE installer loads.

Thanks Carlos, SDM for again responding... I did do a Google search, and am still looking for answers on this... I following one persons "cookbook" approach on how he solved this issue and ended up with an unbootable laptop! (He said to change the Storage Controller in the Device Manager from the Intel Chipset SATA Raid controller to the Microsoft Storage Spaces Controller which claims to be able to manage both RAID and AHCI.) That seemed reasonable, but it hosed the Windows 10 boot process so completely that even Microsoft's recovery/repair tools could not fix it. So now I am a bit leery... I managed to recover Windows 10 from the recovery partition but painful having to reinstall all my apps... (even the recovery disk I had made on a USB stick failed to get Windows back up an running) So my lesson is to be careful about changing Windows storage management drivers! I am confused about why ASUS is using a RAID controller setting in the BIOS for my laptop... I thought RAID was used with multiple drives to build in redundancy and recover-ability. But my laptop only has 2 drives, an SSD drive and a 7200RPM disk drive. So why is a RAID configuration being used? Is there something about SSD drives that I am missing? From my Google research it appears this is common on lots of different laptops that come with Windows pre-installed on systems with an SSD drive, but I can't find an explanation as to why.... I assume that a RAID controller still honors partition boundaries, so I will follow your advice tomorrow and try switching to the AHCI mode to see if Leap 42.2 installs that way.. I am kinda worried about what that means for the boot loader itself also. What do I tell YaST, when I get to the part, to do about creating and putting in a boot loader for openSuSE? I don't fully grok GRUB2 either, should I prevent it from creating a new MBR? Create a boot partition? Put it in the root partition? And I dunno what I will do to make this a dual boot laptop, if this works, other than perhaps have to make this change in the BIOS every time I want to switch OS's... Seems like a rather ugly solution... Forgive me if I am asking too many dumb questions, trying to grok all this is like drinking from a fire hose! Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov composed on 2016-12-19 10:57 (UTC+0300):

Marc Chamberlin wrote on 2016-12-18 23:22 (UTC-0500): ... This is the first time you mention that you have two drives.

??? Marc Chamberlin reported on 2016-12-17 12:04 (UTC-0800) having HD and SSD: https://lists.opensuse.org/opensuse/2016-12/msg00738.html -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov composed on 2016-12-19 10:57 (UTC+0300):

Marc Chamberlin wrote on 2016-12-18 20:22 (UTC-0800): ... This is the first time you mention that you have two drives.

??? Marc Chamberlin reported on 2016-12-17 12:04 (UTC-0800) (32 hours earlier) having HD and SSD: https://lists.opensuse.org/opensuse/2016-12/msg00738.html -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/19/2016 2:12 AM, nicholas cunliffe wrote:

taking one step back: are you tied to windows for gaming etc? dual boot i find an ugly solution anyway (its just painful), i use vbox for rare win10 uses. depending on your use case you could possibly go the linux on VM route and thereby no longer have a problem to solve. if your not into gaming do it the other way round.

Thanks Nicholas - You know that may not be a bad idea! While I won't be using Win10 for gaming (I am not much of a gamer) I will use it a lot for work related purposes. I will look into using a VM under Windows to run Leap42.2 in... I have heard about docker that sounds interesting, but don't know much about it yet... (I have also used Cygwin for some things but overall find it to be unsatisfactory for trying to do anything real like developing code to run on servers.) For now I will keep poking at a dual boot solution, since I am OK with using it, and am familiar with it, but I will try and learn about VM possibilities also... Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-12-19 18:04, Marc Chamberlin wrote:

On 12/18/2016 11:57 PM, Andrei Borzenkov wrote:

You know Andrie, I got to thinking about this in the middle of the night and yeah there is something that was puzzling me... When the BIOS presents me with boot order options, it is only showing me one disk to choose from ,unless I had a DVD drive with a bootable disk or a bootable USB stick also, then it will show me two options. However, Windows 10 does show both my hard drive and the SSD drive as separate drives... And when I switch the BIOS to AHCI mode, I still only see one drive option presented under both SATA drives and Boot Order options. That is confusing to me, is this what "IRST" is doing? I would think that one way or the other, RAID or AHCI modes, I would see either just one drive or two drives.....

Read my recent post, it explains what IRST is. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhYGA0ACgkQja8UbcUWM1wWfgEAj/mmmkECPxlYUi6UMVxMYOTD WGjSDW3wQdFqnIrBrnoA/jBhErVaqBpRSJs5/PGEQ8/wiE6MNHD4acwyzoWnfHTn =K/Kc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/19/2016 9:51 AM, Andrei Borzenkov wrote:

19.12.2016 20:04, Marc Chamberlin пишет:

...

...

Forgive me if I am asking too many dumb questions, Well, it is OK to ask dumb question but so far there is simply not enough information to answer them. Start with switching mode in BIOS, booting Linux and telling us "fdisk -l" output as well as "lspci -nnv" one. You can switch back and continue to use Windows for the time being.

I have already posted the output from these two commands in previous posting... Marc...

Unless I missed it you have posted output in RAID mode.

Hi Andrie - Yes you are correct, I was in RAID mode. So I switched the BIOS to AHCI mode and things look a whole lot more like I would expect. I am able to see both the SSD and the 7200RPM hard drive in the partitioning stage of the installer. Exiting at this point to a console I get the following from the fdisk -l and lspci -nnv utilities. (Note: I also had 2 USB sticks connected as well, one with Leap42.2 one it - sdb, and another that I could use to capture the output to an store in a file on it -sbc. ) fdisk -l Disk /dev/loop0: 50.3 MiB, 52690944 bytes, 102912 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop1: 9.4 MiB, 9895936 bytes, 19328 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop2: 41.7 MiB, 43712512 bytes, 85376 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop3: 69 MiB, 72286208 bytes, 141184 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop4: 4.1 MiB, 4325376 bytes, 8448 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop5: 1.6 MiB, 1703936 bytes, 3328 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop6: 128 KiB, 131072 bytes, 256 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: BBDDAEE1-18A2-4647-80A2-C8337801512B Device Start End Sectors Size Type /dev/nvme0n1p1 2048 534527 532480 260M EFI System /dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved /dev/nvme0n1p3 567296 253081599 252514304 120.4G Microsoft basic data /dev/nvme0n1p4 499095552 500117503 1021952 499M Windows recovery environment Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: C0CC86BB-7E5B-46CC-8EB4-26E1609F0C7D Device Start End Sectors Size Type /dev/sda1 2048 519923711 519921664 247.9G Microsoft basic data Disk /dev/sdb: 7.6 GiB, 8166703104 bytes, 15950592 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xc3072e18 Device Boot Start End Sectors Size Id Type /dev/sdb1 56 15950591 15950536 7.6G b W95 FAT32 Disk /dev/sdc: 57.7 GiB, 61933092864 bytes, 120963072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x135a2181 Device Boot Start End Sectors Size Id Type /dev/sdc1 4084 11643 7560 3.7M ef EFI (FAT-12/16/32) /dev/sdc2 * 11644 8562687 8551044 4.1G 17 Hidden HPFS/NTFS and this is the output from lspci -nnv 00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM Registers [8086:1910] (rev 07) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=10 <?> 00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 0000e000-0000efff Memory behind bridge: db000000-dc0fffff Prefetchable memory behind bridge: 00000000b0000000-00000000c1ffffff Capabilities: [88] Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Capabilities: [80] Power Management version 3 Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [a0] Express Root Port (Slot+), MSI 00 Capabilities: [100] Virtual Channel Capabilities: [140] Root Complex Link Capabilities: [d94] #19 Kernel driver in use: pcieport 00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 07) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at da120000 (64-bit, non-prefetchable) [size=32K] Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 3 Capabilities: [e0] Vendor Specific Information: Len=0c <?> 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:201f] Flags: bus master, medium devsel, latency 0, IRQ 126 Memory at da110000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at da138000 (64-bit, non-prefetchable) [size=4K] Capabilities: [50] Power Management version 3 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- 00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 [8086:a160] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at da137000 (64-bit, non-prefetchable) [size=4K] Capabilities: [80] Power Management version 3 Capabilities: [90] Vendor Specific Information: Len=14 <?> Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Serial IO I2C Controller #1 [8086:a161] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at da136000 (64-bit, non-prefetchable) [size=4K] Capabilities: [80] Power Management version 3 Capabilities: [90] Vendor Specific Information: Len=14 <?> Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: fast devsel, IRQ 255 Memory at da135000 (64-bit, non-prefetchable) [disabled] [size=4K] Capabilities: [50] Power Management version 3 Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+ 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] [8086:a102] (rev 31) (prog-if 01 [AHCI 1.0]) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 124 Memory at da130000 (32-bit, non-prefetchable) [size=8K] Memory at da134000 (32-bit, non-prefetchable) [size=256] I/O ports at f050 [size=8] I/O ports at f040 [size=4] I/O ports at f020 [size=32] Memory at da133000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [70] Power Management version 3 Capabilities: [a8] SATA HBA v1.0 Kernel driver in use: ahci Kernel modules: ahci 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #3 [8086:a112] (rev f1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 Memory behind bridge: dc400000-dc4fffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Capabilities: [a0] Power Management version 3 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Access Control Services Capabilities: [200] L1 PM Substates Capabilities: [220] #19 Kernel driver in use: pcieport 00:1c.3 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #4 [8086:a113] (rev f1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: 0000d000-0000dfff Memory behind bridge: dc300000-dc3fffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Capabilities: [a0] Power Management version 3 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Access Control Services Capabilities: [200] L1 PM Substates Capabilities: [220] #19 Kernel driver in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #5 [8086:a114] (rev f1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=04, subordinate=3c, sec-latency=0 I/O behind bridge: 00002000-00002fff Memory behind bridge: c4000000-da0fffff Prefetchable memory behind bridge: 0000000080000000-00000000a1ffffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Capabilities: [a0] Power Management version 3 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Access Control Services Capabilities: [220] #19 Kernel driver in use: pcieport 00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #9 [8086:a118] (rev f1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=3d, subordinate=3d, sec-latency=0 Memory behind bridge: dc200000-dc2fffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Capabilities: [a0] Power Management version 3 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Access Control Services Capabilities: [220] #19 Kernel driver in use: pcieport 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a150] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, medium devsel, latency 0 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, fast devsel, latency 0 Memory at da12c000 (32-bit, non-prefetchable) [size=16K] 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio [8086:a170] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, fast devsel, latency 32, IRQ 255 Memory at da128000 (64-bit, non-prefetchable) [size=16K] Memory at da100000 (64-bit, non-prefetchable) [size=64K] Capabilities: [50] Power Management version 3 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: medium devsel, IRQ 16 Memory at da132000 (64-bit, non-prefetchable) [size=256] I/O ports at f000 [size=32] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1be1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: fast devsel, IRQ 16 Memory at db000000 (32-bit, non-prefetchable) [size=16M] Memory at b0000000 (64-bit, prefetchable) [size=256M] Memory at c0000000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] Expansion ROM at dc000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Legacy Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [250] Latency Tolerance Reporting Capabilities: [258] L1 PM Substates Capabilities: [128] Power Budgeting <?> Capabilities: [420] Advanced Error Reporting Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900] #19 Kernel modules: nouveau 02:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:0010] Flags: fast devsel, IRQ 18 Memory at dc400000 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-a7-a0-ff-ff-46-83-e0 Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel modules: iwlwifi 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 10) Subsystem: ASUSTeK Computer Inc. Device [1043:200f] Flags: bus master, fast devsel, latency 0, IRQ 123 I/O ports at d000 [size=256] Memory at dc304000 (64-bit, non-prefetchable) [size=4K] Memory at dc300000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00 Capabilities: [170] Latency Tolerance Reporting Capabilities: [178] L1 PM Substates Kernel driver in use: r8169 Kernel modules: r8169 3d:00.0 Non-Volatile memory controller [0108]: Toshiba America Info Systems Device [1179:010f] (rev 01) (prog-if 02 [NVM Express]) Subsystem: Toshiba America Info Systems Device [1179:0001] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at dc200000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [b0] MSI-X: Enable+ Count=8 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [168] Alternative Routing-ID Interpretation (ARI) Capabilities: [178] #19 Capabilities: [198] Latency Tolerance Reporting Capabilities: [1a0] L1 PM Substates Kernel driver in use: nvme Kernel modules: nvme -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, Dec 20, 2016 at 7:41 AM, Marc Chamberlin <marc@marcchamberlin.com> wrote: ...

Hi Andrie - Yes you are correct, I was in RAID mode. So I switched the BIOS to AHCI mode and things look a whole lot more like I would expect. I am able to see both the SSD and the 7200RPM hard drive in the partitioning stage of the installer. Exiting at this point to a console I get the following from the fdisk -l and lspci -nnv utilities. (Note: I also had 2 USB sticks connected as well, one with Leap42.2 one it - sdb, and another that I could use to capture the output to an store in a file on it -sbc. )

fdisk -l

...

Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: BBDDAEE1-18A2-4647-80A2-C8337801512B

Device Start End Sectors Size Type /dev/nvme0n1p1 2048 534527 532480 260M EFI System /dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved /dev/nvme0n1p3 567296 253081599 252514304 120.4G Microsoft basic data /dev/nvme0n1p4 499095552 500117503 1021952 499M Windows recovery environment

So your SSD is true NVMe device, not hidden behind legacy AHCI, and now it is exposed as such. See also later.

Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: C0CC86BB-7E5B-46CC-8EB4-26E1609F0C7D

Device Start End Sectors Size Type /dev/sda1 2048 519923711 519921664 247.9G Microsoft basic data

I assume this is your second disk. This is the most puzzling bit here - while the problem with NVMe and RAID mode is well known (there are patches to fix it under Linux), I would not expect problems accessing *this* drive in RAID mode. If I had access to such hardware, I would definitely contact linux-ide list for ideas and may be patches. ...

00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] [8086:a102] (rev 31) (prog-if 01 [AHCI 1.0])

Yes, plain normal SATA controller ...

3d:00.0 Non-Volatile memory controller [0108]: Toshiba America Info Systems Device [1179:010f] (rev 01) (prog-if 02 [NVM Express])

And this is your SSD - as you see, it is full fledged PCIe device. At this point you have two possibilities. Pragmatic one is to reinstall Windows in this state. Challenging one is to find out how to switch to AHCI mode keeping Windows bootable. Judging by your partition table two disks are likely independent (you can confirm it by showing disk manager in Windows) so it should mostly amount to manually enabling standard NVMe driver in Windows (just like in usual case you would manually enable standard AHCI driver). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, Dec 20, 2016 at 4:55 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:

Otherwise, what use is the laptop making of the SSD? In Windows, I mean. :-?

The whole thread is mostly guesswork. To add at least some factual material I would love to see export of "System Information" tool from Windows (at least from the Storage subtree). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

20.12.2016 19:27, Marc Chamberlin пишет:

On 12/20/2016 6:06 AM, Andrei Borzenkov wrote: ...

[Disks]

Item Value Description Disk drive Manufacturer (Standard disk drives) Model HGST HTS721010A9E630 ...

Description Disk drive Manufacturer (Standard disk drives) Model NVMe THNSN5256GPU7 TO

That reinforces my guess that both drives are used independently. Then it may be possible to switch to AHCI mode without reinstall. I am a bit uneasy because NVMe is also your boot drive and most discussions seem to talk about SATA drives. But you can always make clone backup (you have enough space) if something goes wrong. There are several posts suggesting that something like descibed procedure may help: http://triplescomputers.com/blog/uncategorized/solution-switch-windows-10-fr... In principle, there should be no difference whether you use SATA or NVMe as in both cases it involves loading different drivers than current. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-12-21 21:10, Marc Chamberlin wrote:

On 12/20/2016 10:37 AM, Andrei Borzenkov wrote:

...

20.12.2016 19:27, Marc Chamberlin пишет:

...

On 12/20/2016 6:06 AM, Andrei Borzenkov wrote: ... [Disks]

Item Value Description Disk drive Manufacturer (Standard disk drives) Model HGST HTS721010A9E630 ... Description Disk drive Manufacturer (Standard disk drives) Model NVMe THNSN5256GPU7 TO That reinforces my guess that both drives are used independently. Then it may be possible to switch to AHCI mode without reinstall. I am a bit uneasy because NVMe is also your boot drive and most discussions seem to talk about SATA drives. But you can always make clone backup (you have enough space) if something goes wrong.

There are several posts suggesting that something like descibed procedure may help: http://triplescomputers.com/blog/uncategorized/solution-switch-windows-10-fr...

In principle, there should be no difference whether you use SATA or NVMe

...

as in both cases it involves loading different drivers than current.

Andrei - This worked!!! I now have Windows 10 booting up from the SSD disk in AHCI mode, and the Leap 42.2 installation process is happy to proceed also. Thanks so much for getting me over this hurdle. I like this particular approach as is seemed like a non-risky way to switch modes, from which I could easily recover had things not worked. Lot better than the procedure I previously found which had me change the Windows storage drivers and left my system in an unbootable state!

So this brings me to my next questions, getting back to setting up the bootloader, and where to put things.... The Leap42.2 installer wants to create and put partitions for /, /home, swap, and /boot/efi on the second 7200RPM disk drive. My instincts tell me to put the partitions for / and swap on the SSD drive since it will be faster. (I do have enough unallocated space on the SSD drive.) I would leave /home on my 7200 RPM drive since that is where most of my development work data would be stored and it has the most storage space.

I am not sure what to do about /boot/efi. Microsoft has already created an EFI boot partition in a 260MB FAT partition on the SSD drive. Again my instincts tell me to let the Leap42.2 installer install the /boot/efi partition on the second drive so as to keep the GRUB boot loader stuff separate from Microsoft's boot loading stuff,

No, /boot/efi is not grub. It is... well, UEFI things. I think both systems should share the same EFI partition, but I have very little experience in this. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhbI3AACgkQja8UbcUWM1yIcgEAnQKZ6wJD/Zdl1VNnmMzJEosK 9x4eUVCPUhcpNoWaMMsBAI5DAx9bHks3/fInd1PcmZ1PksTxHsSdNkp0hkqPOpfa =9L61 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2016-12-22 05:04, Marc Chamberlin wrote:

so I simply decided to try and reinstall Leap 42.2 again... (I did fool around with it a bit with a couple of innocuous looking GRUB commands and one thing I saw was that the ls command was listing fd0 but reporting some kind of error about fd1. I am guessing/suspect fd1 may be my 7200RPM drive so perhaps something is getting clobbered in the /boot/efi partition?)

No, fd0 is floppy. Make sure that the floppy is disabled in the BIOS. As it does not exist, the installed and the prober gets into trouble. -- Cheers/Saludos Carlos E. R. (testing openSUSE Leap 42.2, at Minas-Anor) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-12-22 23:30, Marc Chamberlin wrote:

On 12/22/2016 6:17 AM, Carlos E. R. wrote:

...

No, fd0 is floppy. Make sure that the floppy is disabled in the BIOS. As it does not exist, the installed and the prober gets into trouble.

Um there is no ability to disable a floppy disk in my BIOS.. (are such ancient medieval devices still supported? I wonder who still uses them and whether one can even get 3.5, 5 or 8 inch floppy disks any more... Gosh I might have a few buried around here somewhere but no way to use them. Looking at my motherboards around here I don't see any with an interface for em either, but maybe they are supported by USB or something else nowadays. WOW! I didn't expect this to be something I should have to even consider! LOL I am only teasing.... )

The bug/problem is not related to having really a floppy drive, but to the BIOS having one configured by default on this day and age... Yes, many BIOS are configured that way, a phantom floppy drive ;-P - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhcmBoACgkQja8UbcUWM1z4PAD+O/BNmW7tGUneDPlXvvXlYMtK 7x/0EiyALWGL35UGNEEA/2FnqP8KAFNsZFfTVQhwLUerW+R/o9bpBuEFcRO1+Xcl =KC7x -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/22/2016 6:19 AM, Carlos E. R. wrote:

On 2016-12-22 05:04, Marc Chamberlin wrote:

...

On my fourth attempt, thinking that the Nouveau driver might be the cause of this problem, when I reached the KDE desktop I added the NVidia repositories using YaST and had YaST again install all updates and recommended packages. That got the NVidia drivers loaded, but unfortunately I still get the ksmserver-logout-greeter crash and lose the GRUB menu of OS choices upon rebooting.

It is interesting that immediately after I complete the installation process and first boot up the laptop, the GRUB menu of OS choices does show up as one would expect. But when I reboot, AFTER running Leap 42.2 and the KDE desktop, I lose the GRUB menu and get dropped into the low level GRUB command line environment. I wonder if this is connected to the ksmserver-logout-greeter crash since that is the only other anomaly that I see happening.

Anyone got any ideas or suggestions, gosh I feel like I am awfully close to getting this working! Thanks again.... Marc..

Install XFCE as default X system, Also install KDE as secondary (via pattern selection).

I don't know about the grub trouble... something went wrong in the update.

Thanks Carlos, your suggestion got me a bit further along, but well...... Can't say I am really enamored with the XFCE desktop but installing it seems to have solved the ksmserver-logout-greeter crash issue. But another issue has surfaced, I cannot log in as me! (i.e. under my own user name) I CAN log in as root however! I double checked my user password and even tried to change it with YaST, but no joy. I did set up root with a different password than my personal user password but I can't imaging why that would make a difference.... As for the GRUB troubles, when booting up, I have discovered something bizarre is going on. If, I bring up the BIOS configuration menu and then simply save and exit it, then the GRUB OS selection menu does come up and I can select and boot up either Windows 10 or OpenSuSE. (I don't have to make any changes in the BIOS, just simply save and exit it!) But if I don't jump through this hoop of bringing up the BIOS configuration menu and saving/exiting it, then I get dumped into the GRUB low level console. Got any more good ideas? Getting closer inch by painful inch! LOL... Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/22/2016 7:22 PM, Andrei Borzenkov wrote:

23.12.2016 01:18, Marc Chamberlin пишет:

...

As for the GRUB troubles, when booting up, I have discovered something bizarre is going on. If, I bring up the BIOS configuration menu and then simply save and exit it, then the GRUB OS selection menu does come up and I can select and boot up either Windows 10 or OpenSuSE. (I don't have to make any changes in the BIOS, just simply save and exit it!) But if I don't jump through this hoop of bringing up the BIOS configuration menu and saving/exiting it, then I get dumped into the GRUB low level console.

Please show output of "efibootmgr -v" as well as "lsblk -o name,mountpoint,fstype,parttype,partuuid"

Here you go Andrie, hope this helps and makes more sense to you than it does me! ;-) Marc.. marcslaptop:/windows/data # efibootmgr -v BootCurrent: 0000 Timeout: 1 seconds BootOrder: 0000,0005 Boot0000* opensuse-secureboot HD(2,1efd6800,4f800,f9a159a5-e398-4280-be97-6859c38a0c2d)File(\EFI\opensuse\shim.efi) Boot0005* Windows Boot Manager HD(1,800,82000,cc93960b-1c40-4d95-9aed-52d2e0465a2c)File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................ marcslaptop:/windows/data # lsblk -o name,mountpoint,fstype,parttype,partuuid NAME MOUNTPOINT FSTYPE PARTTYPE PARTUUID sda ├─sda1 /windows/data ntfs ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 0ae765b7-4903-470a-aa62-132e701f7e7b ├─sda2 /boot/efi vfat c12a7328-f81f-11d2-ba4b-00a0c93ec93b f9a159a5-e398-4280-be97-6859c38a0c2d └─sda3 /home ext4 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 71d9db5f-f097-4812-83e3-37730585bf63 sr0 nvme0n1 ├─nvme0n1p1 vfat c12a7328-f81f-11d2-ba4b-00a0c93ec93b cc93960b-1c40-4d95-9aed-52d2e0465a2c ├─nvme0n1p2 e3c9e316-0b5c-4db8-817d-f92df00215ae 6d799220-2069-424e-9910-07c3f8dec121 ├─nvme0n1p3 /windows/win10 ntfs ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 9e97ca1f-1ca5-464c-b707-4d2287881877 ├─nvme0n1p4 ntfs de94bba4-06d1-4d40-a16a-bfd50179d6ac 85e2b99e-31eb-4810-a241-c82c6a7ecc4e ├─nvme0n1p5 / ext4 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 260219ab-d54d-4c0c-a579-96d0b2fbcc9d └─nvme0n1p6 [SWAP] swap ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 f7918a91-e5bd-4aea-b9f1-e7a3bdaa05bb -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/23/2016 11:19 AM, Andrei Borzenkov wrote:

23.12.2016 20:35, Marc Chamberlin пишет:

...

On 12/22/2016 7:22 PM, Andrei Borzenkov wrote:

...

23.12.2016 01:18, Marc Chamberlin пишет:

...

As for the GRUB troubles, when booting up, I have discovered something bizarre is going on. If, I bring up the BIOS configuration menu and then simply save and exit it, then the GRUB OS selection menu does come up and I can select and boot up either Windows 10 or OpenSuSE. (I don't have to make any changes in the BIOS, just simply save and exit it!) But if I don't jump through this hoop of bringing up the BIOS configuration menu and saving/exiting it, then I get dumped into the GRUB low level console.

Please show output of "efibootmgr -v" as well as "lsblk -o name,mountpoint,fstype,parttype,partuuid"

Here you go Andrie, hope this helps and makes more sense to you than it does me! ;-) Marc..

Everything looks pretty much normal. My best guess would be that your system defaults to legacy BIOS (CSM) boot but when you got through menu it jumps to UEFI boot. Could you run https://github.com/arvidjaar/bootinfoscript and send me privately? Also when you are in GRUB low level console, could you run "set" and send me photo of screen?

...

On 12/24/2016 12:57 AM, Andrei Borzenkov wrote:

...

24.12.2016 03:21, Marc Chamberlin пишет:

...

Also attached is the results from running your bootinfoscript. HTHs Marc..

Could you please test another branch that adds support for NVMe devices detection. Run it again and send me results. Note, this is different branch.

https://github.com/arvidjaar/bootinfoscript/tree/nvme

Hi Andrei, OpenSuSE again - (My apologies for taking up some bandwidth on this forum.) Andrei, I sent you the results of this script to your private gmail address, as you asked me to, and wonder if you got it? I haven't heard back from you, should I resend? Did it help enlighten you as to why my laptop is requiring me to re-save the BIOS each time I try to power it up? Thanks for helping, Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 1/10/2017 7:26 PM, Carlos E. R. wrote:

On 2017-01-09 23:53, Marc Chamberlin wrote:

...

On 12/23/2016 11:19 AM, Andrei Borzenkov wrote:

...

Did it help enlighten you as to why my laptop is requiring me to re-save the BIOS each time I try to power it up? Hi, I don't see the start of the thread, so apologies if this has already being said.

The first cause to have to re-save the bios is bad bios battery. Bad contact, dead battery, etc. Then there is software error: the bios calculates a checksum. If the checksum is invalid on boot, it assumes the contents of the config area are bad, and resets it (cmos bios memory).

Hi Carlos - This thread actually started just before Christmas, but I got diverted for awhile to other family issues so just trying to get back to solving this problem. (You have actually already responded to me on this thread also, thanks, btw.) Anywise, this is a brand new laptop so I kinda doubt the bios battery is dead. Andrie was helping me and had asked me to send him some data, privately to his personal email address, using a script to gather info about my configuration. I have been trying to send him emails directly, but have not heard back from him on it, so decided to try and reach him again here on the mail list. If I configure my BIOS to boot up Windows, using their boot loader, I have no problems with the BIOS. But if I boot up OpenSuSE using the GRUB boot loader then each time I power up my laptop, I have to go into the BIOS and simply re-save it, then the GRUB boot loader will let me use the menu to select which operating system I want to boot up and everything proceeds. But it is a PITA to have to jump through the hoops of getting BIOS to open up and then saving it each time before I can use the GRUB boot menu.... If I don't do this then I just get dumped into the low level GRUB console... Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

...

On 1/10/2017 7:26 PM, Carlos E. R. wrote:

...

On 2017-01-09 23:53, Marc Chamberlin wrote:

...

On 12/23/2016 11:19 AM, Andrei Borzenkov wrote: Did it help enlighten you as to why my laptop is requiring me to re-save the BIOS each time I try to power it up? Hi, I don't see the start of the thread, so apologies if this has already being said.

The first cause to have to re-save the bios is bad bios battery. Bad contact, dead battery, etc. Then there is software error: the bios calculates a checksum. If the checksum is invalid on boot, it assumes the contents of the config area are bad, and resets it (cmos bios memory).

Hi Carlos - This thread actually started just before Christmas, but I got diverted for awhile to other family issues so just trying to get back to solving this problem. (You have actually already responded to me on this thread also, thanks, btw.) I thought that might be so. I'm accessing the inbox at my ISP, not my local folder that has the historic data, so I can't see posts that long

On 2017-01-11 22:23, Marc Chamberlin wrote: this instant. Only those mails still at my ISP.

Ok, I see now the rest of the thread, quite a long one!

...

Anywise, this is a brand new laptop so I kinda doubt the bios battery is dead. You can see it in the output of "sensors" I think. Also somewhere under /proc or /sys, I don't remember where exactly, I'd have to search. Hmmm I give up, hunted around for it but no joy finding anything that tells me what the BIOS battery is doing. But I am not terribly worried about it, as I said this is a brand new laptop and when I just boot

On 01/11/2017 01:58 PM, Carlos E. R. wrote: directly to Windows using their boot loader directly, I don't have this issue.. It is only when I boot using the GRUB boot loader that this issue arises....

...

If I configure my BIOS to boot up Windows, using their boot loader, I have no problems with the BIOS. But if I boot up OpenSuSE using the GRUB boot loader then each time I power up my laptop, I have to go into the BIOS and simply re-save it, then the GRUB boot loader will let me use the menu to select which operating system I want to boot up and everything proceeds. But it is a PITA to have to jump through the hoops of getting BIOS to open up and then saving it each time before I can use the GRUB boot menu.... If I don't do this then I just get dumped into the low level GRUB console... This looks to me as a software error in the UEFI implementation on that machine. maybe a firmware update would help.

I made sure I have the latest BIOS firmware updates, I do... But you are right, it still could be a bug of some kind in their BIOS firmware. I could try an report it to ASUS but I would like to be on firmer grounds before I do so... Or it could be a bug in the GRUB boot loader and perhaps I should report it in the OpenSuSE/Novell Bugzilla? I will keep waiting/asking, hoping that Andrei (or anyone else with more insights) will get back to me soon and see if he or anyone else has any thing helpful to say... Marc.... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/22/2016 07:28 PM, Carlos E. R. wrote:

On 2016-12-22 23:18, Marc Chamberlin wrote:

...

But another issue has surfaced, I cannot log in as me! (i.e. under my own user name) I CAN log in as root however! I double checked my user password and even tried to change it with YaST, but no joy. I did set up root with a different password than my personal user password but I can't imaging why that would make a difference.... Oh, my. I can't imagine why. Yes, I heard of this trouble, but I do not remember the cause. Keyboard error? Try login in a text console (ctrl-alt-f1). Create another new user. Make sure to only use alphanumerical passwords, no symbols.

AH!! Check the free disk space of /home. Check also the permissions under it, /home/*

I have no idea if my experience is related to this issue, but I've seen permission issues when using "useradd" in Leap 42.x. It manifests by giving a black screen when trying to first-time login via the console. Root and users created by the install process are okay. I traced the problem to ~/.cache and ~/.dbus being owned by root.root instead of <username>.users. A chown -R on those two directories fixes the problem. I have no idea what's causing this, but I've seen it perhaps half a dozen times, and haven't been motivated enough to track it down. I know what to look for now. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/22/2016 8:24 PM, Lew Wolfgang wrote:

On 12/22/2016 07:28 PM, Carlos E. R. wrote:

...

On 2016-12-22 23:18, Marc Chamberlin wrote:

...

But another issue has surfaced, I cannot log in as me! (i.e. under my own user name) I CAN log in as root however! I double checked my user password and even tried to change it with YaST, but no joy. I did set up root with a different password than my personal user password but I can't imaging why that would make a difference.... Oh, my. I can't imagine why. Yes, I heard of this trouble, but I do not remember the cause. Keyboard error? Try login in a text console (ctrl-alt-f1). Create another new user. Make sure to only use alphanumerical passwords, no symbols.

AH!! Check the free disk space of /home. Check also the permissions under it, /home/*

I have no idea if my experience is related to this issue, but I've seen permission issues when using "useradd" in Leap 42.x. It manifests by giving a black screen when trying to first-time login via the console. Root and users created by the install process are okay. I traced the problem to ~/.cache and ~/.dbus being owned by root.root instead of <username>.users. A chown -R on those two directories fixes the problem. I have no idea what's causing this, but I've seen it perhaps half a dozen times, and haven't been motivated enough to track it down. I know what to look for now.

Regards, Lew

Thanks again Carlos, Lew - Well, got me beat! This morning I booted up Leap42.2 in order to get the info Andrie wanted about the configuration of my efi boot manager and disk partitions, and I will be twitched that Leap42.2 logged straight in to my own personal account without bellyaching about it! And I DIDN'T do anything or make any changes! So I experimented with it a bit, logged out and logged back in, this time having to give my password. No problem!! I am not imaging things, yesterday it wasn't gonna let me log in to my personal account come hell or high water! Today, no problem! WTF! Anywise I will let you know if this comes back to haunt me... Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-12-19 05:22, Marc Chamberlin wrote:

On 12/18/2016 5:39 PM, sdm wrote:

...

On 12/18/2016 02:37 PM, nicholas cunliffe wrote:

...

On 18 December 2016 at 23:11, Marc Chamberlin <marc@marcchamberlin.com> wrote:

...

On 12/18/2016 1:40 PM, nicholas cunliffe wrote:

...

this looks like the same problem, seems to occur on all linux:

https://rog.asus.com/forum/showthread.php?79205-Cannot-see-NVMe-M-2-Samsung-...

...

Thanks Nicholas, you did some digging! Correct me though, if I am

...

...

...

wrong and misunderstanding this thread... It appears that this is about how to make it possible to boot from an SSD, and the problem that is being addressed is the fact that the BIOS did not have a module for supporting AHCI, just for RAID. So the solution being presented was how to add the AHCI support to the BIOS. As I noted in my previous post, it appears that in my BIOS I do have the option to switch to AHCI, so apparently it seems this has been addressed by AMI and ASUS.

And as I also mentioned, I tried to switch to AHCI but it gave the boot loader for Windows 10 troubles and I was no longer able to boot up Windows 10. So I am not sure how to make these two OS's play nice with each other, and still looking for a workaround...

Marc... yes i did some more digging and found recent threads, confirming the bios update, and like you, cannot then boot win10 with AHCI. So this would now appear a windows/drive problem? maybe consult google again regarding nvme/ahci/raid/windows. If windows supports ahci then there will always be repair/reinstall if all else fails.

Windows doesn't boot in AHCI mode because Windows wasn't installed in AHCI mode, it was in IDE mode. If you switch, it won't boot. Instructions on how to do this are found by doing a Google search. So for testing I would take the Laptop out of RAID mode, forget about if Windows boots or not, switch to AHCI mode in the BIOS, and then see if the openSUSE installer loads.

Thanks Carlos, SDM for again responding... I did do a Google search, and am still looking for answers on this... I following one persons "cookbook" approach on how he solved this issue and ended up with an unbootable laptop! (He said to change the Storage Controller in the Device Manager from the Intel Chipset SATA Raid controller to the Microsoft Storage Spaces Controller which claims to be able to manage both RAID and AHCI.) That seemed reasonable, but it hosed the Windows 10 boot process so completely that even Microsoft's recovery/repair tools could not fix it. So now I am a bit leery... I managed to recover Windows 10 from the recovery partition but painful having to reinstall all my apps... (even the recovery disk I had made on a USB stick failed to get Windows back up an running) So my lesson is to be careful about changing Windows storage management drivers!

Oh :-(

I am confused about why ASUS is using a RAID controller setting in the BIOS for my laptop... I thought RAID was used with multiple drives to build in redundancy and recover-ability. But my laptop only has 2 drives, an SSD drive and a 7200RPM disk drive. So why is a RAID configuration being used? Is there something about SSD drives that I am missing? From my Google research it appears this is common on lots of different laptops that come with Windows pre-installed on systems with an SSD drive, but I can't find an explanation as to why....

I may have one. There is a methodology in which a fast SSD device is used in combination to a slow rotating rust hard disk, not to store part of the system, or store the system while data goes elsewhere, or any such combination, but to act as a huge read/write cache of any file or disk region that is used frequently. Ie, the OS reads something from the hard disk and stores it on the SSD, so the next time it is read faster. Similarly, writes go to the SSS first, then the system stores it on the HD when idling. I always forget the name of this technology, but it can be thought as a kind of raid. There are hard disks that are sold with an internal SSD disk, implementing this technology in firmware, transparently to the operating system. But this is not the case. If Windows is installed in this way, Linux can not make use of the hard disks at all. Maybe Linux detects the situation and bails out, I do not know. It should produce an error message that we would be able to recognize. And of course, it messes the booting. I Windows, you would see only one disk. Try to find out what Windows says about the hard disk Linux has a similar technology. I don't remember if it was dcache or mcache, searchs on wikipedia on those names do not succeed to find what I seek for. And one of those technologies on Linux appears to be abandoned. Of course, it does not work with Windows either. [...] Ah, it is bcache. https://en.wikipedia.org/wiki/Bcache bcache (abbreviated from block cache) is a cache in the Linux kernel's block layer, which is used for accessing secondary storage devices. It allows one or more fast storage devices, such as flash-based solid-state drives (SSDs), to act as a cache for one or more slower storage devices, such as hard disk drives (HDDs); this effectively creates hybrid volumes and provides performance improvements. Designed around the nature and performance characteristics of SSDs, bcache also minimizes write amplification by avoiding random writes and turning them into sequential writes instead. This merging of I/O operations is performed for both the cache and the primary storage, helping in extending the lifetime of flash-based devices used as caches, and in improving the performance of write-sensitive primary storages, such as RAID 5 sets. https://en.wikipedia.org/wiki/Flashcache Flashcache is a disk cache component for the Linux kernel, initially developed by Facebook since April 2010, and released as open source in 2011. Since January 2013, there is a fork of Flashcache, named EnhanceIO and developed by sTec, Inc.[1] Flashcache works by using flash memory, a USB flash drive, SD card, CompactFlash or any kind of portable flash mass storage system as a write-back persistent cache. An internal SSD can also be used for increasing performance. https://en.wikipedia.org/wiki/Dm-cache m-cache is a component (more specifically, a target) of the Linux kernel's device mapper, which is a framework for mapping block devices onto higher-level virtual block devices. It allows one or more fast storage devices, such as flash-based solid-state drives (SSDs), to act as a cache for one or more slower storage devices such as hard disk drives (HDDs); this effectively creates hybrid volumes and provides secondary storage performance improvements. The design of dm-cache requires three physical storage devices for the creation of a single hybrid volume; dm-cache uses those storage devices to separately store actual data, cache data, and required metadata. Configurable operating modes and cache policies, with the latter in the form of separate modules, determine the way data caching is actually performed. This is the one you may have, SRT: https://en.wikipedia.org/wiki/Smart_Response_Technology In computing, Smart Response Technology (SRT, also called SSD Caching before it was launched) is a proprietary caching mechanism introduced in 2011 by Intel for their Z68 chipset (for the Sandy Bridge–series processors), which allows a SATA solid-state drive (SSD) to function as cache for a (conventional, magnetic) hard disk drive (HDD).[1] SRT is managed by Intel Rapid Storage Technology software version 10.5 or later,[2] and implemented both in its device driver and in the Z68 motherboard's firmware (option ROM). It is available only when the (integrated) disk controller is configured in RAID mode (but not AHCI or IDE modes) by implementing a style of RAID 0 striping. The user can select write-back (so-called maximized mode) or write-through (so-called enhanced mode) caching strategy. The maximum utilizable cache size on the SSD is 64 GB. Caching is done at the logical block addressing (LBA) level, not the file level.[3] Shortly before the announcement of the new chipset, Intel also introduced the Intel 311 (Larson Creek), a 20 GB single-level cell (SLC) solid-state drive, which it markets as suitable for caching.[4][5] As of 2014, TRIM garbage collection is not supported for SRT caching devices, so the SSD's performance is solely maintained by its own firmware.[citation needed] With the release of Ivy Bridge chipsets, support for SRT was provided in a larger variety of desktop chipsets, including Z77, Q77 and H77 (but not Z75, Q75 or B75) as long as an "Intel Core Processor" is used.[6] The situation is similar for Haswell desktop chipsets, with Z87, Q87 and H87 listed as supported.[7] The Ivy Bridge-E chipset X79 did not officially support SRT at launch, but some companies like ASRock added support to their boards via BIOS updates.[8][9] The arrival of Ivy Bridge also saw SRT support added to mobile chipsets: QS77, QM77, UM77 and HM77 support SRT, while HM76 does not.[10] In 2012, Intel also introduced the 313 (Hawley Creek) caching SSD series (20 and 24 GB), advertised as also suitable for use in Ultrabooks.[11] As of 2012, SRT was limited to using at most 64 GB for caching, meaning that on larger SSDs the rest remains unused by the cache,[12] though it is available to be used for other purposes. General article: https://en.wikipedia.org/wiki/Hybrid_drive In computing, a hybrid drive is a logical or physical storage device that combines a fast storage medium such as NAND flash solid-state drive (SSD) with a hard disk drive (HDD), with the intent of adding some of the speed of flash storage to the cost-effective storage capacity of traditional HDDs. The purpose of the SSD in a hybrid drive is to act as a cache for the data stored on the HDD, improving the overall performance by keeping copies of the most frequently used data on the faster SSD. There are two main configurations for implementing hybrid drives: dual-drive hybrid systems and solid-state hybrid drives. In dual-drive hybrid systems, physically separate SSD and HDD devices are installed in the same computer, having the data placement optimization performed either manually by the end user, or automatically by the operating system through the creation of a "hybrid" logical device. In solid-state hybrid drives, SSD and HDD functionalities are built into a single piece of hardware, where data placement optimization is performed either entirely by the device (self-optimized mode), or through placement "hints" supplied by the operating system (host-hinted mode). - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhYDaUACgkQja8UbcUWM1wYoAD+L2OyQdVLVef67tu/HCyDDyQ3 6fsP9gnK+tMmmORJJ0cA/3IwTnIgilaiJqOLPI9Ynkw7r12RepJAmlgQ18O4rBu9 =UGmX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2016-12-20 05:24, Marc Chamberlin wrote:

On 12/19/2016 8:41 AM, Carlos E. R. wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2016-12-19 05:22, Marc Chamberlin wrote:

...

I am confused about why ASUS is using a RAID controller setting in the BIOS for my laptop... I thought RAID was used with multiple drives to build in redundancy and recover-ability. But my laptop only has 2 drives, an SSD drive and a 7200RPM disk drive. So why is a RAID configuration being used? Is there something about SSD drives that I am missing? From my Google research it appears this is common on lots of different laptops that come with Windows pre-installed on systems with an SSD drive, but I can't find an explanation as to why.... I may have one.

lots of technical info deleted...

Thanks so much (I think) Carlos for taking the time and going to the trouble of finding all this information about RAID controllers. It is a lot of information to grok but it helps to understand a bit more about why a RAID controller is being used.

But it appears your install is not using SRT, so I don't understand it. Unless Windows has been reinstalled :-?

I think it would be so much easier if I can figure out how to get rid of using this RAID controller for Windows 10 and simply reinstall Windows 10 under AHCI! I probably will have better luck asking ASUS for help or getting a Windows 10 reinstallation disk from them than I would in getting Linux/openSuSE to support a dual boot environment where a RAID controller for Windows 10 is being used..

See Andrei response about that.

I am still trying to grok how to best proceed and don't yet understand what to do about setting up GRUB to boot up Linux and yet retain the ability to boot up Windows also....

Well, that part is not that complicated. I hope. Your system is using UEFI. -- Cheers/Saludos Carlos E. R. (testing openSUSE Leap 42.2, at Minas-Anor) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Im running asus skylake on tumbleweed (without nvidia) and it works perfectly. On 17 December 2016 at 07:40, Andrei Borzenkov <arvidjaar@gmail.com> wrote:

17.12.2016 05:40, Marc Chamberlin пишет:

...

Hi - I downloaded the ISO image for Leap 42.2 to install it on my brand spanking new ASUS laptop and ran into an unexpected issue. (I did verify the MD5 checksum so suspect the DVD I put the image on is OK.) The installation starts up OK with a lot of text output and gets to the point where 3 overlapped green bars are showing progress and at that point it opens up a dialog box asking me what the URL is for the repository. It gives me 3 options for the CD, the hard drive, and the internet URL. I chose CD obviously but it acts like nothing is there and keeps asking. My guess is that something is wrong with the basic CD/DVD driver that is being installed? Funny that the installation started up OK from the DVD but then it appears to lose the ability to talk to it at some point...

Installation kernel and initrd are loaded by BIOS (or bootloader), no kernel is involved at this stage. As you see, as soon as kernel comes in picture it apparently fails ...

...

Do you want me to send any more info? How do I proceed? Thanks in advance, Marc...

Well, at the point where it asks for installation source you can go back until you come to the initial dialogue, select Expert and Shell. This allows you to poke around - e.g. whether kernel actually detected your BD drive or not.

Keep in mind that this is pretty basic environment lacking a lot of usual features and commands. E.g. it does not even have dmesg, you have to cat /proc/kmsg directly (and kill it with ^\).

Alternative is to try network install, install from USB flash or similar.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Thanks Nicholas for your response. I downloaded the ISO image for the full DVD installation, yeah all 3.7GBs) Burned it to a DVD, and verified the checksum before I installed it. I then put the DVD in the drive on my new laptop, changed the boot order in the BIOS to search the DVD drive first for a boot loader, and let er rip..... So no, I am not using a net installer... Marc... On 12/17/2016 12:17 AM, nicholas cunliffe wrote:

just to check - did you download the net installer or the full DVD (approx 3.7GB)? Since this is not a freeze or an error it sounds like you have downloaded the net installer -> if so use the full DVD.

-- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

The iso I have is 4.1 GiB, to be exact 4384096256 B its been a long time, data inflation, im out of touch...

On 17 December 2016 at 17:52, Freek de Kruijf <freek@opensuse.org> wrote:

Op zaterdag 17 december 2016 08:16:34 CET schreef Marc Chamberlin:

...

Thanks Nicholas for your response. I downloaded the ISO image for the full DVD installation, yeah all 3.7GBs)

The iso I have is 4.1 GiB, to be exact 4384096256 B

...

Burned it to a DVD, and verified the checksum before I installed it. I then put the DVD in the drive on my new laptop, changed the boot order in the BIOS to search the DVD drive first for a boot loader, and let er rip..... So no, I am not using a net installer...

Marc...

On 12/17/2016 12:17 AM, nicholas cunliffe wrote:

...

just to check - did you download the net installer or the full DVD (approx 3.7GB)? Since this is not a freeze or an error it sounds like you have downloaded the net installer -> if so use the full DVD.

-- fr.gr.

member openSUSE Freek de Kruijf

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

...

Hi - I downloaded the ISO image for Leap 42.2 to install it on my brand spanking new ASUS laptop and ran into an unexpected issue. (I did verify the MD5 checksum so suspect the DVD I put the image on is OK.) I would verify that the DVD is really OK. If the boot menu has the

On 2016-12-17 03:40, Marc Chamberlin wrote: option to verify DVD, do it. When I tried to verify the DVD from the boot menu I get exactly the same results as I get when trying to install openSuSE. In other words, the BIOS loads the initial boot code from the DVD (with a lot of text messages being displayed) then tries to start up the kernel. And at that

Thanks Carlos for your responses also... I will intersperse my replies to your comments... Marc... On 12/17/2016 5:11 AM, Carlos E. R. wrote: point system loses the ability to communicate with the DVD drive, so the verification of the DVD fails. Not because the image on the DVD is necessarily bad, but because apparently the kernel, once started, cannot communicate with the DVD drive at all...

...

The installation starts up OK with a lot of text output and gets to the point where 3 overlapped green bars are showing progress and at that You mean that the boot starts up OK. Not the installation really.

Correct, sorry I don't fully understand the nuances in the steps taken during an installation process, so I over-simplified my communication attempts in trying to explain what I observed.

...

point it opens up a dialog box asking me what the URL is for the repository. It gives me 3 options for the CD, the hard drive, and the internet URL. Are you really using the full DVD image? Not the network install image?

I am using a full DVD image.

...

I chose CD obviously but it acts like nothing is there and keeps asking. My guess is that something is wrong with the basic CD/DVD driver that is being installed? Funny that the installation started up OK from the DVD but then it appears to lose the ability to talk to it at some point... Make sure that you are using the full DVD image. If it is, then I would try using an USB stick instead.

I have never tried to do an installation from a USB stick before. Not sure I know how to A) put an image on a USB stick, and B) how to boot from a USB stick. (The BIOS did not present me with that option in setting up boot orders.) I guess I can try doing some internet searches to see if I can grok how to do this... In the meantime, I think I will download the Tumbleweed version and try that approach if doing the install from a USB stick proves to be too challenging... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-12-17 17:52, Per Jessen wrote:

Marc Chamberlin wrote:

...

...

Make sure that you are using the full DVD image. If it is, then I would try using an USB stick instead. I have never tried to do an installation from a USB stick before. Not sure I know how to A) put an image on a USB stick,

dd if=image of=usbstick bs=65536, for instance:

dd if=<isofile> of=/dev/sdb bs=65536 (if your USB stick sdb).

A plain copy works: cp isofile /dev/sdW replace sdW with whatever device the USB gets. There are instructions on the openSUSE download page. https://en.opensuse.org/Live_USB_stick

...

and B) how to boot from a USB stick. (The BIOS did not present me with that option in setting up boot orders.)

Try pressing F8 during bootup - that's often the boot menu.

Same thing as booting from a DVD, actually. But the BIOS will not present the option till there is a stick connected. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhViBAACgkQja8UbcUWM1xfkgD/bIAoCpS+Jbz+OLpY6eiGU9Z+ GZq6WI+NdVJU9tyfunMA/RzjCN3f1g/ZUgShxST/Yu++p0wIYB0EzpF0rpkoQfr7 =CgN0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-12-17 21:04, Marc Chamberlin wrote:

On 12/17/2016 10:46 AM, Carlos E. R. wrote:

Thanks again Carlos for responding! OK I got a bit further using a USB stick, following some other suggestions I installed ImageWriter on another openSuSE system and used it to put the ISO image onto a USB stick. Then yes I figured out that I had to have the USB stick connected before I could get the BIOS to recognize it as an option for configuring the boot order. I then configured the boot order to install first from the USB stick and proceeded with the installation.

Ok...

That actually got me a bit further along, and I did get pass the point where the kernel got installed and the graphical GUI's came up to handle the rest of the installation process. However I quickly hit the next snag, when asked where I want to install the new system, the partitioner is only seeing the USB stick. It does not see or present me with the ability to install the system on either the SSD drive or the hard drive that is in my laptop! So in addition to not being able to use the DVD drive, it appears the installer cannot work with either of the hard drives on my new laptop... Any suggestions on how to proceed? Thanks again in advance...

(This is really surprising! I don't see any reason why my DVD and disk drives on a new laptop should be causing such an issue, isn't there standard default drivers and a standard API for these things?)

I would drop to a text console (ctrl-alt-f2, f3, f4...) and run fdisk -l to find out what is in there. For instance, if the disk has a traditional partition table with four primaries already, then you can not install there, till you delete at least one. So take a photo of that screen and upload to susepaste.org, for instance. Or boot some live distro and then paste the text here. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhVrbEACgkQja8UbcUWM1w6qAD+P2YjEB1+Tq4xf38irTqkNhOe +G0PzYimoYSnqsLMb5QA/0tjZNJtwpRToKh03emuJbhdy1PR3ykf5pfWcwXLZTUN =gijU -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-12-18 02:12, Marc Chamberlin wrote:

On 12/17/2016 1:27 PM, Carlos E. R. wrote:

Carlos - I am not sure exactly what to show you so I will answer with a 2 part response.

First I tried to post an image on susepaste.org showing the output of fdisk -l obtained shortly after the installation process began on my laptop. However I was unsuccessful, susepaste.org seems to just hang when I tell it to create the paste...

Uff. You seem to be unlucky today. You should burn some incense or something. :-P Maybe the photo was too big ?

Sigh... But, as I mentioned, it only shows the USB stick, nada for the SSD and hard drive on my laptop.

Oh :-( That's too bad.

Second, under Windows 10 and using Cygwin to run /sbin/cfdisk.exe for each of the two drives I get the following output -

Ok! Well, there is something in your computer that Linux diskikes. Your only chance then is Tumbleweed, and report in Bugzilla, till support is added... - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhV5HoACgkQja8UbcUWM1wTDwD9Ednp8RG7VhDxaucK2JEng3/K iIDfo+MTg+TcbXC527EA/RPtFhA5UFfwTJCNZSSJMEeN61EDtHx8YbobnefUHQYY =UuCx -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

18.12.2016 12:17, Per Jessen пишет:

It really sounds like you have a hardware/driver issue - no DVD and no harddisks recognised -> some sort of SATA driver issue.

Yep.

Maybe try posting output of "lspci -v" (save it to the usb stick and post from another box).

"lspci -nnv" is generally more useful as it prints IDs in numerical form as well. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/18/2016 8:37 AM, Per Jessen wrote:

Andrei Borzenkov wrote:

...

18.12.2016 12:17, Per Jessen пишет:

...

It really sounds like you have a hardware/driver issue - no DVD and no harddisks recognised -> some sort of SATA driver issue. Yep.

...

Maybe try posting output of "lspci -v" (save it to the usb stick and post from another box).

"lspci -nnv" is generally more useful as it prints IDs in numerical form as well. I forgot that, yes, the numerical device IDs are needed. That way we can determine which driver module is meant to take care of your PCI devices.

Thanks Per, Andrei, Carlos for your responses. I exited out of the installation process at the point where it is asking me where I want to install Leap 42.2 and ran these commands as you all suggested. Here is the results.... fdisk -l Disk /dev/loop0: 50.3 MiB, 52690944 bytes, 102912 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop1: 9.4 MiB, 9895936 bytes, 19328 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop2: 41.7 MiB, 43712512 bytes, 85376 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop3: 69 MiB, 72286208 bytes, 141184 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop4: 4.1 MiB, 4325376 bytes, 8448 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop5: 1.6 MiB, 1703936 bytes, 3328 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop6: 128 KiB, 131072 bytes, 256 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sda: 57.7 GiB, 61933092864 bytes, 120963072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x135a2181 Device Boot Start End Sectors Size Id Type /dev/sda1 4084 11643 7560 3.7M ef EFI (FAT-12/16/32) /dev/sda2 * 11644 8562687 8551044 4.1G 17 Hidden HPFS/NTFS and lspci -nnv 00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM Registers [8086:1910] (rev 07) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=10 <?> 00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 0000e000-0000efff Memory behind bridge: db000000-dc0fffff Prefetchable memory behind bridge: 00000000b0000000-00000000c1ffffff Capabilities: [88] Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Capabilities: [80] Power Management version 3 Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [a0] Express Root Port (Slot+), MSI 00 Capabilities: [100] Virtual Channel Capabilities: [140] Root Complex Link Capabilities: [d94] #19 Kernel driver in use: pcieport 00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 07) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at da1a8000 (64-bit, non-prefetchable) [size=32K] Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 3 Capabilities: [e0] Vendor Specific Information: Len=0c <?> 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:201f] Flags: bus master, medium devsel, latency 0, IRQ 126 Memory at da190000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at da1bd000 (64-bit, non-prefetchable) [size=4K] Capabilities: [50] Power Management version 3 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- 00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 [8086:a160] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at da1bc000 (64-bit, non-prefetchable) [size=4K] Capabilities: [80] Power Management version 3 Capabilities: [90] Vendor Specific Information: Len=14 <?> Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Serial IO I2C Controller #1 [8086:a161] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at da1bb000 (64-bit, non-prefetchable) [size=4K] Capabilities: [80] Power Management version 3 Capabilities: [90] Vendor Specific Information: Len=14 <?> Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: fast devsel, IRQ 255 Memory at da1ba000 (64-bit, non-prefetchable) [disabled] [size=4K] Capabilities: [50] Power Management version 3 Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+ 00:17.0 RAID bus controller [0104]: Intel Corporation SATA Controller [RAID mode] [8086:2822] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 16 Memory at da1a0000 (32-bit, non-prefetchable) [size=32K] Memory at da1b9000 (32-bit, non-prefetchable) [size=256] I/O ports at f050 [size=8] I/O ports at f040 [size=4] I/O ports at f020 [size=32] Memory at da100000 (32-bit, non-prefetchable) [size=512K] Capabilities: [d0] MSI-X: Enable+ Count=9 Masked- Capabilities: [70] Power Management version 3 Capabilities: [a8] SATA HBA v1.0 Kernel driver in use: ahci Kernel modules: ahci 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #3 [8086:a112] (rev f1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 Memory behind bridge: dc300000-dc3fffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Capabilities: [a0] Power Management version 3 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Access Control Services Capabilities: [200] L1 PM Substates Capabilities: [220] #19 Kernel driver in use: pcieport 00:1c.3 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #4 [8086:a113] (rev f1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: 0000d000-0000dfff Memory behind bridge: dc200000-dc2fffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Capabilities: [a0] Power Management version 3 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Access Control Services Capabilities: [200] L1 PM Substates Capabilities: [220] #19 Kernel driver in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #5 [8086:a114] (rev f1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=04, subordinate=3c, sec-latency=0 I/O behind bridge: 00002000-00002fff Memory behind bridge: c4000000-da0fffff Prefetchable memory behind bridge: 0000000080000000-00000000a1ffffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Capabilities: [a0] Power Management version 3 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Access Control Services Capabilities: [220] #19 Kernel driver in use: pcieport 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a150] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, medium devsel, latency 0 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, fast devsel, latency 0 Memory at da1b4000 (32-bit, non-prefetchable) [size=16K] 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio [8086:a170] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, fast devsel, latency 32, IRQ 255 Memory at da1b0000 (64-bit, non-prefetchable) [size=16K] Memory at da180000 (64-bit, non-prefetchable) [size=64K] Capabilities: [50] Power Management version 3 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: medium devsel, IRQ 16 Memory at da1b8000 (64-bit, non-prefetchable) [size=256] I/O ports at f000 [size=32] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1be1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: fast devsel, IRQ 16 Memory at db000000 (32-bit, non-prefetchable) [size=16M] Memory at b0000000 (64-bit, prefetchable) [size=256M] Memory at c0000000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] Expansion ROM at dc000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Legacy Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [250] Latency Tolerance Reporting Capabilities: [258] L1 PM Substates Capabilities: [128] Power Budgeting <?> Capabilities: [420] Advanced Error Reporting Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900] #19 Kernel modules: nouveau 02:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:0010] Flags: fast devsel, IRQ 18 Memory at dc300000 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-a7-a0-ff-ff-46-83-e0 Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel modules: iwlwifi 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 10) Subsystem: ASUSTeK Computer Inc. Device [1043:200f] Flags: bus master, fast devsel, latency 0, IRQ 124 I/O ports at d000 [size=256] Memory at dc204000 (64-bit, non-prefetchable) [size=4K] Memory at dc200000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00 Capabilities: [170] Latency Tolerance Reporting Capabilities: [178] L1 PM Substates Kernel driver in use: r8169 Kernel modules: r8169 HTHs and many thanks again. Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/18/2016 12:39 PM, Andrei Borzenkov wrote:

18.12.2016 22:32, Marc Chamberlin пишет:

...

00:17.0 RAID bus controller [0104]: Intel Corporation SATA Controller [RAID mode] [8086:2822] (rev 31) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 16 Memory at da1a0000 (32-bit, non-prefetchable) [size=32K] Memory at da1b9000 (32-bit, non-prefetchable) [size=256] I/O ports at f050 [size=8] I/O ports at f040 [size=4] I/O ports at f020 [size=32] Memory at da100000 (32-bit, non-prefetchable) [size=512K] Capabilities: [d0] MSI-X: Enable+ Count=9 Masked- Capabilities: [70] Power Management version 3 Capabilities: [a8] SATA HBA v1.0 Kernel driver in use: ahci Kernel modules: ahci

Try disabling RAID mode in BIOS setup.

Hi Andrie - Before I go too far I want to ask a question first... I found the place in the the BIOS settings under SATA Configuration where it is currently set to RAID. I tentatively changed that to AHCI (the only other option) and then tried to reboot Windows 10 just to make sure I wasn't going to break it. It did break it, so I switched it back to RAID... So not knowing what I am doing here, if I make this change, and then manage to get Leap 42.2 installed, am I going to be making Win 10 unhappy? And more bad news, I tried Tumbleweed and it too failed in the same way as Leap 42.2 is... This is such a nice way to spend wintry days, getting recalcitrant computers to behave! ;-) Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, Dec 19, 2016 at 2:32 AM, Marc Chamberlin <marc@marcchamberlin.com> wrote:

lspci -nnv

00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM Registers [8086:1910] (rev 07) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=10 <?>

00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 0000e000-0000efff Memory behind bridge: db000000-dc0fffff Prefetchable memory behind bridge: 00000000b0000000-00000000c1ffffff Capabilities: [88] Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Capabilities: [80] Power Management version 3 Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [a0] Express Root Port (Slot+), MSI 00 Capabilities: [100] Virtual Channel Capabilities: [140] Root Complex Link Capabilities: [d94] #19 Kernel driver in use: pcieport

Hi, I have Mi Book 13" with Skylake and nvidia graphics. It runs Tumbleweed (never try it with 42.2 though). I don't use nvidia with TW also erizaverde:/home/medwinz # lspci -nnv 00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM Registers [8086:1904] (rev 08) Subsystem: Device [1d72:1602] Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=10 <?> 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Device [1d72:1602] Flags: bus master, fast devsel, latency 0, IRQ 125 Memory at a2000000 (64-bit, non-prefetchable) [size=16M] Memory at b0000000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: [40] Vendor Specific Information: Len=0c <?> Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [100] Process Address Space ID (PASID) Capabilities: [200] Address Translation Service (ATS) Capabilities: [300] Page Request Interface (PRI) Kernel driver in use: i915 Kernel modules: i915

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1be1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:13f0] Flags: fast devsel, IRQ 16 Memory at db000000 (32-bit, non-prefetchable) [size=16M] Memory at b0000000 (64-bit, prefetchable) [size=256M] Memory at c0000000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] Expansion ROM at dc000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Legacy Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [250] Latency Tolerance Reporting Capabilities: [258] L1 PM Substates Capabilities: [128] Power Budgeting <?> Capabilities: [420] Advanced Error Reporting Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900] #19 Kernel modules: nouveau

this is the nvidia in my laptop 01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:134b] (rev a2) Subsystem: Device [1d72:1602] Flags: fast devsel, IRQ 11 [virtual] Memory at a3000000 (32-bit, non-prefetchable) [size=16M] Memory at 90000000 (64-bit, prefetchable) [size=256M] Memory at a0000000 (64-bit, prefetchable) [size=32M] I/O ports at 4000 [size=128] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [250] Latency Tolerance Reporting Capabilities: [258] L1 PM Substates Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900] #19 Kernel modules: nouveau I think skylake is supported in kernel > 4.5 but you can install the intel firmware (off course until you successfully installed it with 42.2) see [1] or [2]. I remember when I first installed this Mi Book I should add in kernel boot line something like "nomodeset i915.modeset=0 nouveau.modeset=0" going to run level 3 (or whatever the name is), and blacklist "acer_wmi". I blacklist "acer_wmi" because it cause the wireless doesn't work. My laptop only run TW (single boot, no windows) and the bios is set to legacy. [1] https://01.org/linuxgraphics/intel-linux-graphics-firmwares [2] http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree... Hope that help. -- Edwin https://about.me/medwinz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-12-18 10:12, Per Jessen wrote:

Carlos E. R. wrote:

...

On 2016-12-17 17:52, Per Jessen wrote:

...

Marc Chamberlin wrote:

...

...

...

and B) how to boot from a USB stick. (The BIOS did not present me with that option in setting up boot orders.)

Try pressing F8 during bootup - that's often the boot menu.

Same thing as booting from a DVD, actually.

Yes, provided the USB interface is in the right place in the boot order.

I meant that it is configured or selected in the same menu - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhWZgIACgkQja8UbcUWM1yPlAEAgji/1iQctoHqB5fJ3UK6xbeD jy9SKDeS1iBDBNau8hwA/jTnRGICOkBbbK79VoR5zUgLG2b9VyJ915SAjWBjBJQ5 =78Gn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org