Mailinglist Archive: opensuse (516 mails)
| < Previous | Next > |
Re: [opensuse] Upgrading KDE 4.4 > 4.5 -- was: Graduated from "Absent trash icon" to disaster
- From: Stan Goodman <stan.goodman@xxxxxxxxxxxxx>
- Date: Sun, 6 Feb 2011 17:23:48 +0200
- Message-id: <201102061723.48942.stan.goodman@hashkedim.com>
On Sunday 06 February 2011 01:40:20 Stan Goodman wrote:
Now I have booted the system to runlevel 3 again, and I observe several
facts that eluded me when I was drowsy last night, or that I failed to
interpret properly. I think I see now what has happened and why.
When I booted last night, I saw that, even in runlevel 3, the boot process
froze at a point; the log stopped scrolling. While I was writing about
that on the laptop, I happened to glance at the "stalled" desktop screen,
and noticed that it had started again and run to completion, but I didn't
inspect adequately what was on the screen. Having repeated this exercise
now, I see that the last line before the freeze is:
Starting NFS clent services:sm-notify ldmapdStarting kernel based NFS
server: lpmapd mountd statd nfsd sm-notify
which seems clearly to show that something in NFS has stuck in its throat.
So I put the laptop into Suspect, which caused the desktop's boot process
to restart at once and run to completion.
That reminded me that, a while before I accepted the hour-long automatic
upgrade, I had installed an NFS client in the desktop to communicate with
the laptop, and had partially installed also an NFS server (I didn't
finish that chore because I didn't have the time just then, and it has to
be done on the CLI because The Powers That Be, in their great wisdom, have
removed that facility from YaST).
I haven't continued with the suggestions of Felix, because I am pretty
sure that all will be welll if I kill the NFS client (and maybe the sever)
in the desktop machine. How can I do that most easily, without losing
whatever has already been done there?
Aside from the above, I note some other remarks at the end of the log:
1) "Mount CIFS File Systems unused"
2) "Starting RNG daemon No hardware support availablee skipped"
--
Stan Goodman
Qiryat Tiv'on
Israel
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
On Saturday 05 February 2011 22:25:07 Felix Miata wrote:
On 2011/02/05 21:44 (GMT+0200) Stan Goodman composed:
After the<space> 3 to get into text mode, the system returned to
the chameleon screen, moved the progress gauge a bit, and froze for
about five
Get 'quiet' off the line where you type the 3 and change
'splash=silent' to 'splash=verbose' and you'll boot without the
graphics, instead getting all available boot messages, which will
scroll by faster than they can be read.
If you want it like that always, make those changes in
/boot/grub/menu.lst and /etc/sysconfig/bootloader on the
"DEFAULT_APPEND=" line.
I have made the changes in the two files (replaced 'silent' with
'verbose' and deleted 'quiet'), and rebooted to runlevel 3. At the
bottom of display is exactly the same report as before, including 0
errors, but now only 1 skipped probe.
But further up there is a report of:
-----
Error while executing:
Command 'ip route replace to 192.168.1.1/24 via 192.168.1.1 dev
eth0' returned: RTNETLINKS answers: Invalid argument
Configuration line: 192.168.1.1 192.168.1.1 255.255.255.0 eth0
eth0
-----
which looks like it fixed an error. I'm not sure what the error was,
because I was able to access websites through this installation.
Starting Firewall Initialization (phase 2 of 2)
Master Resource Control: runlevel 3 has been<--sic
Failed services in runlevel 3:
Skipped services in runlevel 3:
Welcome to openSUSE 11.3 "Teal" - Kernel 2.6.34.7-0.7-desktop
(tty1). poblano2 login: WARNING: Number of errors: 0, skipped
probes:57 -----
Now I have booted the system to runlevel 3 again, and I observe several
facts that eluded me when I was drowsy last night, or that I failed to
interpret properly. I think I see now what has happened and why.
When I booted last night, I saw that, even in runlevel 3, the boot process
froze at a point; the log stopped scrolling. While I was writing about
that on the laptop, I happened to glance at the "stalled" desktop screen,
and noticed that it had started again and run to completion, but I didn't
inspect adequately what was on the screen. Having repeated this exercise
now, I see that the last line before the freeze is:
Starting NFS clent services:sm-notify ldmapdStarting kernel based NFS
server: lpmapd mountd statd nfsd sm-notify
which seems clearly to show that something in NFS has stuck in its throat.
So I put the laptop into Suspect, which caused the desktop's boot process
to restart at once and run to completion.
That reminded me that, a while before I accepted the hour-long automatic
upgrade, I had installed an NFS client in the desktop to communicate with
the laptop, and had partially installed also an NFS server (I didn't
finish that chore because I didn't have the time just then, and it has to
be done on the CLI because The Powers That Be, in their great wisdom, have
removed that facility from YaST).
I haven't continued with the suggestions of Felix, because I am pretty
sure that all will be welll if I kill the NFS client (and maybe the sever)
in the desktop machine. How can I do that most easily, without losing
whatever has already been done there?
Aside from the above, I note some other remarks at the end of the log:
1) "Mount CIFS File Systems unused"
2) "Starting RNG daemon No hardware support availablee skipped"
--
Stan Goodman
Qiryat Tiv'on
Israel
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |