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