[opensuse] I am most puzzled....
....which is an understatement :-) . My puzzlement comes in 2 parts. Part #1. Last November I bought a Thinkpad that came with Windows 8 pre-installed and I promptly upgraded that to 8.1. I then installed 13.1 and had both systems running -- until a couple of weeks ago when some upgrades/updates were done using zypper and suddenly I could not boot into any of the systems - the system would freeze as soon as the word "grub" appeared (ie, the grub menu did not appear). I check all the partitions using SystemRescueCD and everything looked fine. I got tired of not getting anywhere so formatted the whole HDD and installed only 13.1. All worked fine until a couple of days ago when once again when zypper did some upgrades/updates and I then discovered that I had no wi-fi or cable access to the internet. I looked in YaST and found that the oS was using Network Manager so I tried to change that to 'ifup' but this cannot be done because YaST is 'telling' me that it smpppd first needs to be installed - but I have no access to the 'net. I am now trying to work thru this by using the installation CD which I will do in the next several minutes. But the real puzzlement in this Part #2. Remember I said that I had formatted the whole HDD and installed 13.1 only? Well, in trying to resolve the above hassle I used 'fdisk -l' to see if the CD I had in the sr0 was being recognised by 13.1 (it wasn't) but what I saw made my jaw drop: fdisk - was showing that the HDD still had all the partitions in their original positions when Windows 8/8.1 was installed as well as the new installation of 13.1. But looking at the Partitioner in YaST showed the new partitioning scheme after I had formatted the HDD and installed 13.1 the second time. How can this be? If anybody can throw some light on either or both of the above I would be most grateful. BC PS BTW, the Thinkpad has an Intel cpu and also NVIDIA NVS 5400M Graphics with Optimus Technology. -- A civilisation is judged by how it treats the most vulnerable. Lauren Smith - 30 January 2014 -- 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 2014-02-11 05:31, Basil Chupin wrote:
Remember I said that I had formatted the whole HDD and installed 13.1 only?
Well, in trying to resolve the above hassle I used 'fdisk -l' to see if the CD I had in the sr0 was being recognised by 13.1 (it wasn't) but what I saw made my jaw drop: fdisk - was showing that the HDD still had all the partitions in their original positions when Windows 8/8.1 was installed as well as the new installation of 13.1.
But looking at the Partitioner in YaST showed the new partitioning scheme after I had formatted the HDD and installed 13.1 the second time.
You may have both a GPT table and an MBR table, instead of a protective MBR. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlL5rM8ACgkQja8UbcUWM1yUzQD+MvljSCPL6/TGiejvaQJdrB0P lqS/qdX1Z0ACGLDHqxkA/2EFQFugJ1cY9gOfnGrcp+ik6tlC8eZ2lWX2s6yIpVzT =eKOL -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/02/14 15:53, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Remember I said that I had formatted the whole HDD and installed 13.1 only?
Well, in trying to resolve the above hassle I used 'fdisk -l' to see if the CD I had in the sr0 was being recognised by 13.1 (it wasn't) but what I saw made my jaw drop: fdisk - was showing that the HDD still had all the partitions in their original positions when Windows 8/8.1 was installed as well as the new installation of 13.1.
But looking at the Partitioner in YaST showed the new partitioning scheme after I had formatted the HDD and installed 13.1 the second time. You may have both a GPT table and an MBR table, instead of a
On 2014-02-11 05:31, Basil Chupin wrote: protective MBR.
Ce`? Explain please :-) . BC -- A civilisation is judged by how it treats the most vulnerable. Lauren Smith - 30 January 2014 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/11/2014 04:49 AM, Basil Chupin wrote:
On 11/02/14 15:53, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Remember I said that I had formatted the whole HDD and installed 13.1 only?
Well, in trying to resolve the above hassle I used 'fdisk -l' to see if the CD I had in the sr0 was being recognised by 13.1 (it wasn't) but what I saw made my jaw drop: fdisk - was showing that the HDD still had all the partitions in their original positions when Windows 8/8.1 was installed as well as the new installation of 13.1.
But looking at the Partitioner in YaST showed the new partitioning scheme after I had formatted the HDD and installed 13.1 the second time. You may have both a GPT table and an MBR table, instead of a
On 2014-02-11 05:31, Basil Chupin wrote: protective MBR.
Ce`?
Explain please :-) .
Yes, please do. I'm sure this will impact many of us, if not now then eventually. -- There are still places where people think that the function of the media is to supply information -- Donn Rottenburg -- 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 2014-02-11 13:49, Anton Aylward wrote:
On 02/11/2014 04:49 AM, Basil Chupin wrote:
You may have both a GPT table and an MBR table, instead of a protective MBR.
Ce`?
Explain please :-) .
Yes, please do. I'm sure this will impact many of us, if not now then eventually.
I already did on another post :-) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlL6IJcACgkQja8UbcUWM1xVZAD/b/oacm84mWSUKq5OVrPtJsG8 lxRy+t+Ax+96ohbhWMMA/3eiexSIvSbAxnxam/OASyGE7eOwwtArgpE/PNHozREv =BJJ8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/10/2014 11:31 PM, Basil Chupin wrote:
....which is an understatement :-) . My puzzlement comes in 2 parts.
Part #1.
Last November I bought a Thinkpad that came with Windows 8 pre-installed and I promptly upgraded that to 8.1.
I then installed 13.1 and had both systems running -- until a couple of weeks ago when some upgrades/updates were done using zypper and suddenly I could not boot into any of the systems - the system would freeze as soon as the word "grub" appeared (ie, the grub menu did not appear). I check all the partitions using SystemRescueCD and everything looked fine. I got tired of not getting anywhere so formatted the whole HDD and installed only 13.1.
All worked fine until a couple of days ago when once again when zypper did some upgrades/updates and I then discovered that I had no wi-fi or cable access to the internet. I looked in YaST and found that the oS was using Network Manager so I tried to change that to 'ifup' but this cannot be done because YaST is 'telling' me that it smpppd first needs to be installed - but I have no access to the 'net. I am now trying to work thru this by using the installation CD which I will do in the next several minutes.
But the real puzzlement in this Part #2.
Remember I said that I had formatted the whole HDD and installed 13.1 only?
Well, in trying to resolve the above hassle I used 'fdisk -l' to see if the CD I had in the sr0 was being recognised by 13.1 (it wasn't) but what I saw made my jaw drop: fdisk - was showing that the HDD still had all the partitions in their original positions when Windows 8/8.1 was installed as well as the new installation of 13.1.
But looking at the Partitioner in YaST showed the new partitioning scheme after I had formatted the HDD and installed 13.1 the second time.
How can this be?
If anybody can throw some light on either or both of the above I would be most grateful.
BC
PS BTW, the Thinkpad has an Intel cpu and also NVIDIA NVS 5400M Graphics with Optimus Technology.
I would use a Live GParted disk and see what that says. Or a system disk that has GParted on it would be even better, because then you could use the file manager to actually look at the partition(s) and see what's on them, if anything. --doug -- Blessed are the peacemakers...for they shall be shot at from both sides. --A. M. Greeley -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/02/14 16:03, doug wrote:
On 02/10/2014 11:31 PM, Basil Chupin wrote:
....which is an understatement :-) . My puzzlement comes in 2 parts.
Part #1.
Last November I bought a Thinkpad that came with Windows 8 pre-installed and I promptly upgraded that to 8.1.
I then installed 13.1 and had both systems running -- until a couple of weeks ago when some upgrades/updates were done using zypper and suddenly I could not boot into any of the systems - the system would freeze as soon as the word "grub" appeared (ie, the grub menu did not appear). I check all the partitions using SystemRescueCD and everything looked fine. I got tired of not getting anywhere so formatted the whole HDD and installed only 13.1.
All worked fine until a couple of days ago when once again when zypper did some upgrades/updates and I then discovered that I had no wi-fi or cable access to the internet. I looked in YaST and found that the oS was using Network Manager so I tried to change that to 'ifup' but this cannot be done because YaST is 'telling' me that it smpppd first needs to be installed - but I have no access to the 'net. I am now trying to work thru this by using the installation CD which I will do in the next several minutes.
But the real puzzlement in this Part #2.
Remember I said that I had formatted the whole HDD and installed 13.1 only?
Well, in trying to resolve the above hassle I used 'fdisk -l' to see if the CD I had in the sr0 was being recognised by 13.1 (it wasn't) but what I saw made my jaw drop: fdisk - was showing that the HDD still had all the partitions in their original positions when Windows 8/8.1 was installed as well as the new installation of 13.1.
But looking at the Partitioner in YaST showed the new partitioning scheme after I had formatted the HDD and installed 13.1 the second time.
How can this be?
If anybody can throw some light on either or both of the above I would be most grateful.
BC
PS BTW, the Thinkpad has an Intel cpu and also NVIDIA NVS 5400M Graphics with Optimus Technology.
I would use a Live GParted disk and see what that says. Or a system disk that has GParted on it would be even better, because then you could use the file manager to actually look at the partition(s) and see what's on them, if anything.
--doug
SystemRescueCD contains GParted and this is what I used to reformat and partition the HDD when wiping out Windows to install 13.1. BC -- A civilisation is judged by how it treats the most vulnerable. Lauren Smith - 30 January 2014 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 11/02/2014 05:31, Basil Chupin a écrit :
Well, in trying to resolve the above hassle I used 'fdisk -l' to see if the CD
if ever your disk use GPT, which is usual with your configurationj, the true command to use is gdisk (fdisk do no read GPT) and the syntax is not totally identical jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/02/14 18:50, jdd wrote:
Le 11/02/2014 05:31, Basil Chupin a �crit :
Well, in trying to resolve the above hassle I used 'fdisk -l' to see if the CD
if ever your disk use GPT, which is usual with your configurationj, the true command to use is gdisk (fdisk do no read GPT) and the syntax is not totally identical
jdd
Ce`? If fdisk cannot read GPT then why is it coming up with the wrong partitioning info? But I will try this gdisk you mention. BC -- A civilisation is judged by how it treats the most vulnerable. Lauren Smith - 30 January 2014 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 11/02/2014 10:55, Basil Chupin a écrit :
If fdisk cannot read GPT then why is it coming up with the wrong partitioning info?
it reads the mbr that do not hold the correct info, so fdisk read wrong data you may be able in the bios to choose between mbr and gpt (if yous disk/partition is smaller than 2To, which is likely), but probably losing your data. GPT is a linear partitionning system, no more "extended" system, only primary and as many as you want jdd -- http://www.dodin.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 On 2014-02-11 10:55, Basil Chupin wrote:
On 11/02/14 18:50, jdd wrote:
Le 11/02/2014 05:31, Basil Chupin a �crit :
Ce`?
If fdisk cannot read GPT then why is it coming up with the wrong partitioning info?
The GPT partition table contains an MBR table at the start, at the place that fdisk expects it. It is made such that programs that do not understand GPT think there is an MBR. This is called "protective MBR". Se the wikipedia article http://en.wikipedia.org/wiki/GUID_Partition_Table +++··········· Traditionally, in IBM PC compatible systems the first sector of the disk holds the Master Boot Record (MBR), containing the drive's partitioning information and the code of the first stage boot loader for BIOS-based systems. For limited backward compatibility, this sector is still reserved for a MBR in the GPT specification, but it is now used in a way that prevents MBR-based disk utilities from mis-recognizing, and possibly over-writing, GPT disks. This is referred to as a "protective MBR". A single partition type of EEh, encompassing the entire GPT drive (where "entire" actually means as much of the drive as can be represented in an MBR), is indicated and identifies it as GPT. Operating systems and tools which cannot read GPT disks will generally recognize the disk as containing one partition of unknown type and no empty space, and will typically refuse to modify the disk unless the user explicitly requests and confirms the deletion of this partition. This minimizes accidental erasures. Furthermore, GPT-aware OSes will check the protective MBR and if the enclosed partition type is not of type EEh or if there are multiple partitions defined on the target device, the device should not be manipulated. ···········++- However, you probably used a disk partitioning tool too old to recognize the situation and bail out. It did wrote partition data on that MBR, having now GPT partition data and MBR data, and even worst, they do not match. Please post the output of "fdisk -l" from an openSUSE system, even a rescue system. I do not trust that SystemRescueCD of yours. And the ouput of "parted -l". - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlL6CIsACgkQja8UbcUWM1x5sAEAg86W9g+58VPZUPZEQgKNwQt6 ZnTxbB3CgYRXIxo7JjsA/i2TYHX9+uVX9jzPUDmFIE2ocL8xkFNw4rhhs/KFQh5p =Wodl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 11/02/2014 12:24, Carlos E. R. a écrit :
Please post the output of "fdisk -l" from an openSUSE system, even a rescue system. I do not trust that SystemRescueCD of yours. And the ouput of "parted -l".
by the way gdisk -l /dev/sda is better don't forget neither -l nor /dev/sdxxx jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/02/14 22:24, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2014-02-11 10:55, Basil Chupin wrote:
On 11/02/14 18:50, jdd wrote:
Le 11/02/2014 05:31, Basil Chupin a �crit :
Ce`?
If fdisk cannot read GPT then why is it coming up with the wrong partitioning info? The GPT partition table contains an MBR table at the start, at the place that fdisk expects it. It is made such that programs that do not understand GPT think there is an MBR. This is called "protective MBR".
Se the wikipedia article http://en.wikipedia.org/wiki/GUID_Partition_Table
+++··········· Traditionally, in IBM PC compatible systems the first sector of the disk holds the Master Boot Record (MBR), containing the drive's partitioning information and the code of the first stage boot loader for BIOS-based systems. For limited backward compatibility, this sector is still reserved for a MBR in the GPT specification, but it is now used in a way that prevents MBR-based disk utilities from mis-recognizing, and possibly over-writing, GPT disks. This is referred to as a "protective MBR".
A single partition type of EEh, encompassing the entire GPT drive (where "entire" actually means as much of the drive as can be represented in an MBR), is indicated and identifies it as GPT. Operating systems and tools which cannot read GPT disks will generally recognize the disk as containing one partition of unknown type and no empty space, and will typically refuse to modify the disk unless the user explicitly requests and confirms the deletion of this partition. This minimizes accidental erasures. Furthermore, GPT-aware OSes will check the protective MBR and if the enclosed partition type is not of type EEh or if there are multiple partitions defined on the target device, the device should not be manipulated. ···········++-
However, you probably used a disk partitioning tool too old to recognize the situation and bail out. It did wrote partition data on that MBR, having now GPT partition data and MBR data, and even worst, they do not match.
Please post the output of "fdisk -l" from an openSUSE system, even a rescue system. I do not trust that SystemRescueCD of yours. And the ouput of "parted -l".
Thanks for the above - I will study it more closely later. In answer to your last para, the fdisk -l info I provided comes from openSUSE 13.1 :-) , as did the YaST info. I would need to get at the laptop to be able to post here the exact output of fdisk but believe me it gives exactly what I mentioned - the partitions as they were before I formatted the HDD. BTW, when I installed 13.1 after formatting the HDD I had YaST replace the MBR during the installation process. BC -- A civilisation is judged by how it treats the most vulnerable. Lauren Smith - 30 January 2014 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 11/02/2014 12:45, Basil Chupin a écrit :
Thanks for the above - I will study it more closely later.
man gdisk is very informative jdd -- http://www.dodin.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 On 2014-02-11 12:45, Basil Chupin wrote:
On 11/02/14 22:24, Carlos E. R. wrote:
In answer to your last para, the fdisk -l info I provided comes from openSUSE 13.1 :-) , as did the YaST info. I would need to get at the laptop to be able to post here the exact output of fdisk but believe me it gives exactly what I mentioned - the partitions as they were before I formatted the HDD.
It may have a line about GPT being present, or some other error.
BTW, when I installed 13.1 after formatting the HDD I had YaST replace the MBR during the installation process.
I think that at some point something ignored there was a GPT table and wrote data to the MBR instead. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlL6GCIACgkQja8UbcUWM1zjnQD/Zkq6hmhRHFjcYrIxs6r7mhBz cCG4c/bV+dq1/1q+12cA+wSiDIuN1WSs/tEJwwHtSiUorqqRfFHNoS/JufvxvV/X =V9mV -----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: SHA1 On 2/11/2014 3:24 AM, Carlos E. R. wrote:
However, you probably used a disk partitioning tool too old to recognize the situation and bail out. It did wrote partition data on that MBR, having now GPT partition data and MBR data, and even worst, they do not match.
Wow, what a trap. So the "Protective" measures built into the MBR fails to offer any real protection? - -- _____________________________________ - ---This space for rent--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAlL6caUACgkQv7M3G5+2DLLjBgCfSOfQbxKF+gSlzL3xtvhgMLcs OwMAn0BmM9wvmNRPC7uoOQBTAJT5tDRo =mtp1 -----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 2014-02-11 19:53, John Andersen wrote:
On 2/11/2014 3:24 AM, Carlos E. R. wrote:
However, you probably used a disk partitioning tool too old to recognize the situation and bail out. It did wrote partition data on that MBR, having now GPT partition data and MBR data, and even worst, they do not match.
Wow, what a trap.
So the "Protective" measures built into the MBR fails to offer any real protection?
It appears so. But my hunch has yet to be proved... In a GPT partitioned disk, there is an MBR table. Nothing impedes you from entering partition data on that MBR, if you wish or insist. The wikipedia article says: "Operating systems and tools which cannot read GPT disks will generally recognize the disk as containing one partition of unknown type and no empty space, and will typically refuse to modify the disk unless the user explicitly requests and confirms the deletion of this partition." If the partitioning tool is reasonably recent, it will recognize the presence of a GPT table and stop or give a warning. If it is too old or daft, it will just see an MBR with a huge partition. My guess is that he used some such software. If this is true, the entire disk should be erased and repartitioned, with GPT aware software. Another possibility, mind, is that GPT disks store a backup copy of the table at the end of the disk. The disk might be properly partitioned now as MBR, but that second copy of the GPT table, which is placed at the end of the disk, was probably not erased. And some software is still reading it, and thus saying this is a GPT disk with such and such partitions... If you tell such software to repair the missing main GPT table, then the real and actual MBR will be destroyed! If this is the case, the solution instead is to erase (fill with zeros) the area of the second table. This actually happened to a chap on the forums. There is a CLI command sequence to find out if this is happening, and to erase that second table. But I don't have a link to that thread in this laptop. And it doesn't occur to me a good string to do a search with. I think Andrey Borzenkov was involved in that one. If it was him, he will remember. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlL6eSgACgkQja8UbcUWM1zPmAD/RSKg6qRGSU2bcKRnaTLtTmK7 Hc/1Vmy0Sq+esWnq4fwA/RIrT/Wwh8OgCOjQyWs9UcZEjZKgy4RJKHVU819pa9i7 =SIWc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/02/14 15:31, Basil Chupin wrote:
....which is an understatement :-) . My puzzlement comes in 2 parts.
Part #1.
Last November I bought a Thinkpad that came with Windows 8 pre-installed and I promptly upgraded that to 8.1.
I then installed 13.1 and had both systems running -- until a couple of weeks ago when some upgrades/updates were done using zypper and suddenly I could not boot into any of the systems - the system would freeze as soon as the word "grub" appeared (ie, the grub menu did not appear). I check all the partitions using SystemRescueCD and everything looked fine. I got tired of not getting anywhere so formatted the whole HDD and installed only 13.1.
All worked fine until a couple of days ago when once again when zypper did some upgrades/updates and I then discovered that I had no wi-fi or cable access to the internet. I looked in YaST and found that the oS was using Network Manager so I tried to change that to 'ifup' but this cannot be done because YaST is 'telling' me that it smpppd first needs to be installed - but I have no access to the 'net. I am now trying to work thru this by using the installation CD which I will do in the next several minutes.
But the real puzzlement in this Part #2.
Remember I said that I had formatted the whole HDD and installed 13.1 only?
Well, in trying to resolve the above hassle I used 'fdisk -l' to see if the CD I had in the sr0 was being recognised by 13.1 (it wasn't) but what I saw made my jaw drop: fdisk - was showing that the HDD still had all the partitions in their original positions when Windows 8/8.1 was installed as well as the new installation of 13.1.
But looking at the Partitioner in YaST showed the new partitioning scheme after I had formatted the HDD and installed 13.1 the second time.
How can this be?
If anybody can throw some light on either or both of the above I would be most grateful.
BC
PS BTW, the Thinkpad has an Intel cpu and also NVIDIA NVS 5400M Graphics with Optimus Technology.
A big Thanks to everybody who contributed to the discussion on this quest for help. I solved the whole thing by zapping everything and re-installing 13.1. And I am grateful to jdd for having learnt about using gdisk instead of fdisk. (I mentioned in my PS above that the Thinkpad and my wife's computer is Intel based - for a reason. I simply cannot put my finger on it but while I myself have, and always had, an AMD system, and 99.999% trouble free, I have had hassles when it comes to my wife's computer, and now the Thinkpad. As I said, I cannot put my finger on it but there is something about Intel + oS........ My imagination? Perhaps.....) BC -- A civilisation is judged by how it treats the most vulnerable. Lauren Smith - 30 January 2014 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Anton Aylward -
Basil Chupin -
Carlos E. R. -
Carlos E. R. -
doug -
jdd -
John Andersen