[opensuse] Disastrous 11.2 installation
The installation is for the 64 bit system. K3b reported md5 identical to that given at the distribution site. I installed to formatted partitions (ext4). During the installation process errors appeared telling me of I/O errors preventing the installation of the following packaged: yast2-themes-opensuse-2.18.10.1.1.1 (twice) xorg-x11-fonts-core (twice) yast2-nfs-client yast2-iscsi-client yast2-repair Since I do not find on the forum messages from others about similar experience, I have to guess that it has happened only here, but I can't explain to myself why, since the burned disk seems to be good. Has anyone else had this? Assuming that there is enough left of YaST to get and install packages, I would hope to be able to make the missing packages good, but that is impossible because of the other disaster, which is that the mouse cursor is erratic and uncontrollable, so that there is no way to operate the system. The cursor is not visible except sometimes after the mouse is moved, but its invisible movements seem to be clicking (without any action from me) on whatever it passes on the desktop. Fortunately, I still have v11.1 operational on the same system, so I am not without a working machine, but I would like to understand why I have these problems, and what to do about them, so I can move on to the new release. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Nov 13, 2009 at 11:09 AM, Stan Goodman
The installation is for the 64 bit system. K3b reported md5 identical to that given at the distribution site. I installed to formatted partitions (ext4).
During the installation process errors appeared telling me of I/O errors preventing the installation of the following packaged:
yast2-themes-opensuse-2.18.10.1.1.1 (twice) xorg-x11-fonts-core (twice) yast2-nfs-client yast2-iscsi-client yast2-repair
Since I do not find on the forum messages from others about similar experience, I have to guess that it has happened only here, but I can't explain to myself why, since the burned disk seems to be good. Has anyone else had this?
Assuming that there is enough left of YaST to get and install packages, I would hope to be able to make the missing packages good, but that is impossible because of the other disaster, which is that the mouse cursor is erratic and uncontrollable, so that there is no way to operate the system. The cursor is not visible except sometimes after the mouse is moved, but its invisible movements seem to be clicking (without any action from me) on whatever it passes on the desktop.
Stan, If this is a new install, just starting over is almost certainly your best solution. I would also not be surprised if you have a hardware problem. At a minimum I would run memtest from the install cd. If you do want to recover your partially installed system, then the most reliable solution is zypper. It is a pure command line solution, so if you can get to a terminal / console login, you have a good chance of fixing this. If you are on the X screen, then control-alt-F1 should take you to the console. Hit return a couple times and you should be prompted for a login. Once you login, verify you have the right repos installed and refresh them. Then run zypper dup to finish your install. See http://en.opensuse.org/Upgrade for details about the above steps. You won't need to do the full upgrade process, but it should not hurt either. If you have a lot of missing packages, they still may not come in but I would expect zypper dup to at least get yast functional. And once yast is functional, you can start pulling in whole patterns. (ie. from within yast, select the patterns view and click on the ones you want to have installed.) If not, these are the yast packages I have on my 11.2 system. Use zypper to ensure you have them all installed.
rpm -qa | grep -i yast
yast2-core-2.18.19-2.3.x86_64 autoyast2-installation-2.18.14-1.1.3.noarch yast2-backup-2.18.4-3.2.noarch yast2-storage-2.18.19-2.3.x86_64 yast2-control-center-gnome-2.13.4-2.3.x86_64 autoyast2-2.18.14-1.1.3.noarch yast2-wagon-2.18.1-2.1.noarch yast2-trans-en_US-2.18.1-16.18.1.noarch yast2-kerberos-client-2.18.3-2.2.noarch yast2-qt-2.18.7-2.1.x86_64 yast2-qt-graph-2.18.4-4.1.x86_64 yast2-control-center-2.18.12-1.1.1.x86_64 yast2-bootloader-2.18.17-2.5.x86_64 yast2-online-update-2.18.5-2.2.noarch yast2-runlevel-2.17.4-2.2.noarch yast2-xml-2.16.1-56.1.x86_64 yast2-pam-2.17.1-2.1.noarch yast2-control-center-qt-2.18.12-1.1.1.x86_64 yast2-registration-branding-openSUSE-2.18.0-2.4.noarch yast2-samba-server-2.18.2-2.1.noarch yast2-ntp-client-2.18.0-3.2.noarch yast2-x11-2.18.0-2.1.noarch yast2-packager-2.18.13-1.1.3.x86_64 yast2-iscsi-client-2.18.6-2.2.noarch yast2-repair-2.18.3-2.4.noarch yast2-sudo-2.18.2-2.2.noarch yast2-mouse-2.18.2-2.1.x86_64 yast2-sound-2.18.4-1.1.2.1.x86_64 yast2-sshd-2.18.0-2.5.noarch yast2-scanner-2.18.0-2.2.x86_64 yast2-ncurses-2.18.10-2.1.x86_64 yast2-printer-2.18.19-2.2.x86_64 yast2-security-2.18.3-2.2.noarch yast2-samba-client-2.18.3-2.2.noarch yast2-network-2.18.51-1.1.2.x86_64 yast2-tune-2.18.1-2.2.x86_64 yast2-inetd-2.17.3-3.3.noarch yast2-installation-2.18.33-1.1.2.noarch yast2-irda-2.18.1-2.2.noarch yast2-libyui-2.18.8-2.1.x86_64 yast2-ycp-ui-bindings-2.18.5-2.1.x86_64 yast2-theme-openSUSE-Oxygen-2.18.10-1.1.1.noarch yast2-ldap-client-2.18.5-2.6.noarch yast2-users-2.18.13-2.1.x86_64 yast2-online-update-frontend-2.18.5-2.2.noarch yast2-mail-2.18.2-2.2.noarch yast2-pkg-bindings-2.18.11-1.1.4.x86_64 yast2-2.18.25-2.5.x86_64 yast2-vm-2.16.10-3.1.x86_64 yast2-trans-stats-2.15.0-122.2.noarch yast2-sysconfig-2.17.0-56.2.noarch yast2-nis-client-2.18.2-2.2.x86_64 yast2-country-2.18.20-2.2.x86_64 yast2-registration-2.18.0-2.4.noarch yast2-profile-manager-2.18.2-2.2.x86_64 yast2-fingerprint-reader-2.18.1-2.1.x86_64 yast2-hardware-detection-2.17.1-2.3.x86_64 yast2-add-on-2.18.3-2.1.noarch yast2-schema-2.18.2-2.4.noarch yast2-slp-2.16.0-83.1.x86_64 yast2-branding-openSUSE-2.18.0-2.1.noarch yast2-nfs-common-2.18.1-2.2.noarch yast2-dbus-client-2.18.0-2.1.x86_64 yast2-ncurses-pkg-2.18.4-2.9.x86_64 yast2-update-2.18.6-2.3.x86_64 yast2-firewall-2.18.1-1.1.2.noarch yast2-apparmor-2.18.4-1.1.1.noarch yast2-transfer-2.18.0-3.1.x86_64 yast2-metapackage-handler-0.8.9-2.2.noarch yast2-restore-2.18.1-3.1.noarch yast2-country-data-2.18.20-2.2.x86_64 yast2-theme-openSUSE-2.18.10-1.1.1.noarch yast2-perl-bindings-2.18.0-2.1.x86_64 yast2-nfs-client-2.18.0-2.2.noarch yast2-tv-2.18.4-2.8.noarch yast2-ldap-2.17.3-9.1.x86_64 yast2-qt-pkg-2.18.18-1.1.2.x86_64 When you invoke zypper, just give it the base package name. ie. "zypper in yast2-qt-pkg" will cause the last package in the above list to be installed. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Nov 13, 2009 at 11:34:50AM -0500, Greg Freemyer wrote: [ 8< ]
On Fri, Nov 13, 2009 at 11:09 AM, Stan Goodman
wrote: The installation is for the 64 bit system. K3b reported md5 identical to that given at the distribution site. I installed to formatted partitions (ext4).
During the installation process errors appeared telling me of I/O errors preventing the installation of the following packaged:
This sounds more like a hardware issue. Most likely the memory. Please give the "Memory Test" DVD/ CD boot option a try as Greg suggested. [ 8< ]
Assuming that there is enough left of YaST to get and install packages, I would hope to be able to make the missing packages good, but that is impossible because of the other disaster, which is that the mouse cursor is erratic and uncontrollable, so that there is no way to operate the system. The cursor is not visible except sometimes after the mouse is moved, but its invisible movements seem to be clicking (without any action from me) on whatever it passes on the desktop.
If this is a new install, just starting over is almost certainly your best solution. I would also not be surprised if you have a hardware problem. At a minimum I would run memtest from the install cd.
If you do want to recover your partially installed system, then the most reliable solution is zypper.
Or give the "Repair Installed System" DVD/ CD boot option a try. After one upgrade from openSUSE 11.1 to 11.2 I gave it a try and it had been able to get the system boot again. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
The installation is for the 64 bit system. K3b reported md5 identical to that given at the distribution site. I installed to formatted
(ext4).
During the installation process errors appeared telling me of I/O errors preventing the installation of the following packaged:
yast2-themes-opensuse-2.18.10.1.1.1 (twice) xorg-x11-fonts-core (twice) yast2-nfs-client yast2-iscsi-client yast2-repair
Since I do not find on the forum messages from others about similar experience, I have to guess that it has happened only here, but I can't explain to myself why, since the burned disk seems to be good. Has anyone else had this?
Assuming that there is enough left of YaST to get and install
On Fri, Nov 13, 2009 at 11:09 AM, Stan Goodman
wrote: partitions packages, I would hope to be able to make the missing packages good, but that is impossible because of the other disaster, which is that the mouse cursor is erratic and uncontrollable, so that there is no way to operate the system. The cursor is not visible except sometimes after the mouse is moved, but its invisible movements seem to be clicking (without any action from me) on whatever it passes on the desktop.
Stan,
If this is a new install, just starting over is almost certainly your best solution. I would also not be surprised if you have a hardware problem. At a minimum I would run memtest from the install cd.
If you do want to recover your partially installed system, then the most reliable solution is zypper.
It is a pure command line solution, so if you can get to a terminal / console login, you have a good chance of fixing this.
If you are on the X screen, then control-alt-F1 should take you to the console.
Hit return a couple times and you should be prompted for a login.
Once you login, verify you have the right repos installed and refresh them. Then run zypper dup to finish your install.
See http://en.opensuse.org/Upgrade for details about the above steps. You won't need to do the full upgrade process, but it should not hurt either.
If you have a lot of missing packages, they still may not come in but I would expect zypper dup to at least get yast functional. And once yast is functional, you can start pulling in whole patterns. (ie. from within yast, select the patterns view and click on the ones you want to have installed.)
[8<] I ran into the same problem, lots of packages couldn't be read from the DVD. So, I burned 2 new copies, verified them both via MD5 and via the installer program. All three DVD copies passed the tests. So, I swapped out the DVD reader, I tested with two other drives. Still problems with the very same packages, no matter what I tried. So I ended up doing a FTP installation instead. Unfortunately VMware Server 2.0.2 wouldn't install with kernel 2.6.31 so eventually I had to revert to 11.1 again.. Highly annoying. Anders. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I don't know if its the burner or the reader, but ... Why should I care if ... Since the ISO image on on a server here, surely I can do an 'network upgrade'? Surely? However I'm having trouble finding that info on the wiki. That's *UPGRADE* And yes I know about Wagon. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Anton Aylward
I don't know if its the burner or the reader, but ...
Why should I care if ...
Since the ISO image on on a server here, surely I can do an 'network upgrade'? Surely?
However I'm having trouble finding that info on the wiki.
That's *UPGRADE*
And yes I know about Wagon.
I beleve that it *has* been mentioned here once or twice that that process is: zypper dup of course the proper repos must be enabled, and that *is* mentioned in the wiki. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Patrick Shanahan said the following on 11/14/2009 10:16 AM:
* Anton Aylward
[11-14-09 10:11]: I don't know if its the burner or the reader, but ...
Why should I care if ...
Since the ISO image on on a server here, surely I can do an 'network upgrade'? Surely?
However I'm having trouble finding that info on the wiki.
That's *UPGRADE*
And yes I know about Wagon.
I beleve that it *has* been mentioned here once or twice that that process is: zypper dup
of course the proper repos must be enabled, and that *is* mentioned in the wiki.
No, Patrick, NOT that TYPE of network upgrade. I know about all that (manual) resetting of the repositories and then running 'zypper dup'. If I have the DVD I can upgrade from that, surely? Why should I need to **MANUALLY** reset all the repos when ... Look: If I could burn the DVD and my reader worked I cold just drop the DVD in, boot and do an upgrade. No need to edit repositories. So why can't I upgrade from the DVD **IMAGE** ?? Surely the DVD **IMAGE** contains what's in the repos? -- In times of profound change, the learners inherit the earth, while the learned find themselves beautifully equipped to deal with a world that no longer exists. - Eric Hoffer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/14/2009 04:43 PM, Anton Aylward wrote:
Look: If I could burn the DVD and my reader worked I cold just drop the DVD in, boot and do an upgrade. No need to edit repositories.
Yes, that's the "traditional" upgrade method.
So why can't I upgrade from the DVD **IMAGE** ??
Surely the DVD **IMAGE** contains what's in the repos?
I don't quite follow you here :-? You want, perhaps, put the image somewhere on a network server, and then do a network install using that image as source? I have done that time ago, but I had the image loop mounted, and I exported that. I'm not sure that exporting the iso directly works, but it might; it should be documented somewhere, in the wiki perhaps, or the netinstall image intructions. However, in any case, notice that the image contains quite less than the repos. - -- Cheers / Saludos, Carlos E. R. (from 11.2-ex-factory "Emerald" GM) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkr+7pgACgkQU92UU+smfQXNUACfT1ByRvadedTFRF4XXri2nb+k /bAAnRGJRnlxx5ZMb0zvbktXCOHo+rRT =zXda -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anton Aylward wrote:
I don't know if its the burner or the reader, but ...
Why should I care if ...
Since the ISO image on on a server here, surely I can do an 'network upgrade'? Surely?
However I'm having trouble finding that info on the wiki.
That's *UPGRADE*
And yes I know about Wagon.
Only way I ever found to do what I think you want to do in earlier versions was to upgrade via a network boot using PXE and this would only work from a network device that supports PXE or a boot configuration that provides a PXE boot. This former is documented for the earlier versions in the wiki, dunno about 11.2 (at some point will have to try this out but not just at this moment as I have no pressing need to move to 11.2). - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAksBMtQACgkQasN0sSnLmgJq+gCg14PU8S2L9wiEJa0zMDh0yGML 2yoAmwWhBNa/sNrAs+3aEJ3NjleAat0i =Vbdn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Anders Norrbring
-
Anton Aylward
-
Carlos E. R.
-
G T Smith
-
Greg Freemyer
-
Lars Müller
-
Patrick Shanahan
-
Stan Goodman