I’ve had 13.1 running for several months with out much problem. Recently I noticed that I had 130+ updates pending, so I started the update. The updates never complete because it hangs on “remove ucode-amd” . I have tried it in the Updater and in Yast2 and I have had to close the system down in order to exit either of these.
Then I noticed that at boot time Grub no longer offers my WinXP boot option.
I tried to run Yast2 and edit the Bootloader and it hangs.
I then tried to run Gparted from within 13.1 and it just hangs while scanning all devices.
And now I have no network access, either locally or the internet.
Please let me know what further info you need to provide assistance, and how to get it.
> Please let me know what further info you need to provide assistance, and
> how to get it.
Please run this command in a terminal:
zypper lr --details
and paste it all here, from initial command prompt, to last command
prompt, in a single mouse sweep, and please do so inside code tags (the
‘#’ button in the forum editor). http://susepaste.org/images/15093674.jpg
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 2014-09-28 00:56, cgarai wrote:
>
> I piped it to a file and then had to move that file to a mounted network
> drive (so my network partially works, perhaps it is my browser
> (Firefox)).
On Sat 27 Sep 2014 11:53:07 PM CDT, Carlos E. R. wrote:
On 2014-09-28 00:56, cgarai wrote:
>
> I piped it to a file and then had to move that file to a mounted
> network drive (so my network partially works, perhaps it is my browser
> (Firefox)).
<snip>
Beyond that, your list seems normal, nothing to cause the problems you
describe. :-?
What are your current symptoms? No internet?
Hi
Also what packages are you using from repo #2, if it’s the r8168 kmp
for your network card, then that would cause an issue if the kernel has
upgraded…
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-21-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
You can always inspect your command line options by using help, eg
zypper --help
In your case, I happen to know “rr” removes the repo. You can identify the repo by typing out the whole repo name or if you know its enumeration, simply by the number, eg the repo to be removed is listed as the third
zypper rr 3
First, considering how your machine is progressing (or regressing), you might want to copy your /home directory to an external drive or otherwise save anything you feel is valuable in case things get much worse.
Regarding your more broad problems, I’d recommend doing a repair using the standard 13.1 DVD (Do you have it downloaded?). If you had network access, you might have more options.
After doing a repair, you should have networking again. Run update to install latest packages from the Internet
zypper update
Also, for future reference if you have various issues like the graphics issues you describe, you should be able to boot into “Rescue Mode” (your Grub Menu selection) for troubleshooting. You wouldn’t want to operate permanently in that mode, but it should be enough to fix your problems before they get worse.
Re-building your Grub Menu entry pointing to Windows requires some additional work, but do the above first.
In your case, I happen to know “rr” removes the repo. You can identify
the repo by typing out the whole repo name or if you know its
enumeration, simply by the number, eg the repo to be removed is listed
as the third
zypper rr 3
Hi
Just a word of caution with using zypper rr N, that N changes… for
example if you wanted to delete some repo 3 and some repo 4, always use
the highest number first else if you removed some repo 3, then some
repo 4 becomes some repo 3…
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-21-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
On 2014-09-30 00:46, deano ferrari wrote:
>
> malcolmlewis;2667128 Wrote:
>> Hi
>> Just a word of caution with using zypper rr N, that N changes… for
>> example if you wanted to delete some repo 3 and some repo 4, always use
>> the highest number first else if you removed some repo 3, then some
>> repo 4 becomes some repo 3…
>
> Yes, and so to avoid confusion, it may be prudent to list the repos
> again between repo removals to make sure you get the next target
> correct.
I do it like “zypper rr NUMBER && zyper lr --details”. In fact, any repo
manipulation with zypper I do it that way.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
SInce my network connection was working, running “zypper update” worked, mostly. Occasionally some object would get to 100%, but hang and never move on. After several Ctrl-c ignore then retry the update it made it through with a few exceptions. The Software Updater “bug” icon on the tray said I have 7 packages that need updating. However it now hangs at the point where it is “Removing packages: lvm2”
At least my browser is working again.
Am I correct in thinking that “Software Updater”, Yast2:Online Update and “zypper update” all attempt to do the same thing? zypper at least allowed me to abort the process and retry which the others did not.
As for fixing Grub, I have tried “boot-repair-disk”, gparted, Yast2:bootloader and they all hang while “scanning system”. I read somewhere that this may be due to a non-existent floppy drive that is enabled in the cmos hardware setup or a windows NTFS ddrive that needs a chkdsk.
Any further clues?
Thank you very much for your help so far!
Chris
After doing a repair, you should have networking again. Run update to install latest packages from the Internet
zypper update
Also, for future reference if you have various issues like the graphics issues you describe, you should be able to boot into “Rescue Mode” (your Grub Menu selection) for troubleshooting. You wouldn’t want to operate permanently in that mode, but it should be enough to fix your problems before they get worse.
Re-building your Grub Menu entry pointing to Windows requires some additional work, but do the above first.
On 2014-10-02 07:56, cgarai wrote:
>
> zypper list-updates --all returns “No updates found.”
>
> Ran “rpm --rebuilddb”
>
> It ran OK, but still same problems.
“rpm --rebuilddb” itself had problems?
> Next I ran “zypper verify”
>
> It wanted to remove lvm2 as well, and it hung there. This added the
> following to the log file:
>
>
> Code:
> --------------------
>
> # 2014-10-01 22:42:58 lvm2-2.02.98-0.28.14.1.x86_64 remove failed
> # rpm output:
> # warning: waiting for transaction lock on /var/lib/rpm/.rpm.lock
> #
>
> --------------------
>
>
> Does that provide a useflul clue?
Yes, it does indeed.
Check the date of that file (/var/lib/rpm/.rpm.lock). If it is old,
delete it. If recent, check that rpm is not running - or rather, check
no matter the date:
ps afxu | grep -i rpm
lsof /var/lib/rpm/.rpm.lock
If something has the file, kill it. Then delete the lock file.
After deletion, make sure to run “rpm --rebuilddb” again.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
