Hello SuSE people, Did an upgrade with apt on my 10.0 last night. Mostly KDE stuff but included a kernel upgrade. I watched as apt installed everything and saw the kernel installed mk_initrd and lilo called. It did a couple of SuSEconfigs during the process also. At the end I did another mk_initrd, lilo, and Suseconfig. Rebooted and it won't boot. Gets way into the boot process and then just hangs with a flashing cursor after either of these 3 following commands; starting powersaved (accessing ACPI events over acpid) starting SSH daemon starting SMPPPD I have no idea what to do about this. Don't even know if it was the kernel upgrade or the rpm upgrade. I booted to the DVD and tried a "Repair System" It complained about the package database, listed about 15 packages starting with /var/lib/rpm,offered to repair, said it did, gave me an error message,"Changing environment to target system was not successful", and then dumped me out of the repair process. Same condition. Then tried the "rescue" system from the cli but I couldn't mount my system. Probably don't remember how to do it and wasn't sure what I would do except to try and rebuild the rpm database. Can somebody give me a clue here? Please? Bob S.
B Stia wrote:
Hello SuSE people,
Did an upgrade with apt on my 10.0 last night. [...]
Rebooted and it won't boot. Gets way into the boot process and then just hangs with a flashing cursor after either of these 3 following commands;
starting powersaved (accessing ACPI events over acpid) starting SSH daemon starting SMPPPD
I think it's an already reported bug: https://bugzilla.novell.com/show_bug.cgi?id=153543 Roll back to a previous version of kdebase3-kdm and the problem will dissapear. -- Adi Pircalabu
Hello List How can I make my reply appear above the quoted message instead of the place where Kmail locates it. Yours Tommie -- ______________________________ msc. tomas alberto ramirez.andujar sistemas de informaci'on y redes departamento de tecnologia educativa iplac - cel - la habana - cuba +537 274 14 79 - www.iplac.rimed.cu
On Sunday 26 February 2006 16:11, tommie ramirez andujar wrote:
Hello List
How can I make my reply appear above the quoted message instead of the place where Kmail locates it.
Don't do that or you will run afoul of the 'top posting police' on this list.....
On Monday 27 February 2006 2:34 pm, Bruce Marshall wrote:
On Sunday 26 February 2006 16:11, tommie ramirez andujar wrote:
Hello List
How can I make my reply appear above the quoted message instead of the place where Kmail locates it.
Don't do that or you will run afoul of the 'top posting police' on this list.....
Hi, I hereby apologize for my lack of netiquette but it does make sense what you tell me, maybe it was just post-mswindows habit, i understand your point. Thanks tommie -- ______________________________ msc. tomas alberto ramirez andujar sistemas de informaci'on y redes departamento de tecnologia educativa iplac - cel - la habana - cuba +537 274 14 79 - www.iplac.rimed.cu
* tommie ramirez andujar
How can I make my reply appear above the quoted message instead of the place where Kmail locates it.
You do not want to do this, it's called top-posting and is impolite. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
Right here. On Sunday 26 February 2006 4:11 pm, tommie ramirez andujar wrote:
Hello List
How can I make my reply appear above the quoted message instead of the place where Kmail locates it. Kmail (on my SuSE 10.0 system) places the cursor at the top left. As you can see above, I top posted "Right Here". Normally, when replying to a SuSE list, the established protocol is to post at the bottom not the top.
AFAIK, there is no way in KMail to force KMail to place the initial cursor
at any other place.
--
Jerry Feldman
On Sunday 26 February 2006 17:42, B Stia wrote:
Hello SuSE people,
Did an upgrade with apt on my 10.0 last night.... Rebooted and it won't boot.
Hi Bob, There was a thread here in the last day on this exact problem... apparently there was a mixup causing a 10.1 component to be inadvertently installed during the update. From that thread: "... It has to do with the file /etc/init.d/earlykdm, installed by the new kdebase3 rpms, build -27. You can edit that file with the changes I'll indicate below to put things right using the -27 build rpms. Replace this: if test -z "$DISPLAYMANAGER_AUTOLOGIN"; then /sbin/preload /etc/preload.d/kdm else /usr/bin/ionice -n2 /sbin/preload /etc/preload.d/kdm.auto /usr/bin/ionice -n6 /sbin/preload /etc/preload.d/kde & echo $! > /var/run/preload-session.pid fi With this: if test -z "$DISPLAYMANAGER_AUTOLOGIN"; then /sbin/preload < /var/cache/preload/kdm.preload else /usr/bin/ionice -n2 /sbin/preload < /var/cache/preload/kdm.auto.preload /usr/bin/ionice -n6 /sbin/preload < /var/cache/preload/kde.preload & echo $! > /var/run/preload-session.pid fi If I were you, I'd boot into rescue mode, mount the partition and check this file out. If it matches the first section try editing it as indicated. BTW, the post I've quoted was Lee's (BandiPat's). hth & regards, Carl
Carl Hartung wrote:
On Sunday 26 February 2006 17:42, B Stia wrote:
Hello SuSE people,
Did an upgrade with apt on my 10.0 last night.... Rebooted and it won't
boot.
Hi Bob,
There was a thread here in the last day on this exact problem... apparently there was a mixup causing a 10.1 component to be inadvertently installed during the update. From that thread:
"... It has to do with the file /etc/init.d/earlykdm, installed by the new kdebase3 rpms, build -27. You can edit that file with the changes I'll indicate below to put things right using the -27 build rpms.
Replace this:
if test -z "$DISPLAYMANAGER_AUTOLOGIN"; then /sbin/preload /etc/preload.d/kdm else /usr/bin/ionice -n2 /sbin/preload /etc/preload.d/kdm.auto /usr/bin/ionice -n6 /sbin/preload /etc/preload.d/kde & echo $! > /var/run/preload-session.pid fi
With this:
if test -z "$DISPLAYMANAGER_AUTOLOGIN"; then /sbin/preload < /var/cache/preload/kdm.preload else /usr/bin/ionice -n2 /sbin/preload < /var/cache/preload/kdm.auto.preload /usr/bin/ionice -n6 /sbin/preload < /var/cache/preload/kde.preload & echo $! > /var/run/preload-session.pid fi
If I were you, I'd boot into rescue mode, mount the partition and check this file out. If it matches the first section try editing it as indicated. BTW, the post I've quoted was Lee's (BandiPat's).
hth & regards,
Carl
Hi Carl Yep, I remember seeing that and never thought anything of it. Now, I can't seem to mount my filesystem from the rescue prompt. Either I have an advanced case of dementia/alzheimers (possible) or it is something else. Possibly because some of my partitions except / are LVM's? A short refresher would certainly be appreciated. Of course I have lots of notes and stuff on how to do these things but they are all inaccessible right now. (On SuSE 10 that won't boot) Bob S.
On Sunday 26 February 2006 22:05, B Stia wrote: [...]
Yep, I remember seeing that and never thought anything of it.
Now, I can't seem to mount my filesystem from the rescue prompt. Either I have an advanced case of dementia/alzheimers (possible) or it is something else. Possibly because some of my partitions except / are LVM's?
A short refresher would certainly be appreciated. Of course I have lots of notes and stuff on how to do these things but they are all inaccessible right now. (On SuSE 10 that won't boot)
Bob S.
========= Bob, At the Loader (Grub) screen, press F2 to get options. Type "init 3", at the prompt. That will boot the computer to the tty1 screen safely. Type in your root name and password, then type "rcxdm start" at the prompt. That will take you into KDE once again. From there, correct the file that was mentioned and your booting problems should go away. regards, Lee
On Sunday 26 February 2006 23:41, BandiPat wrote:
On Sunday 26 February 2006 22:05, B Stia wrote: [...]
Yep, I remember seeing that and never thought anything of it.
Now, I can't seem to mount my filesystem from the rescue prompt. Either I have an advanced case of dementia/alzheimers (possible) or it is something else. Possibly because some of my partitions except / are LVM's?
A short refresher would certainly be appreciated. Of course I have lots of notes and stuff on how to do these things but they are all inaccessible right now. (On SuSE 10 that won't boot)
Bob S.
=========
Bob, At the Loader (Grub) screen, press F2 to get options. Type "init 3", at the prompt. That will boot the computer to the tty1 screen safely. Type in your root name and password, then type "rcxdm start" at the prompt. That will take you into KDE once again. From there, correct the file that was mentioned and your booting problems should go away.
Thanks Lee, I will be keeping this on file as well as a method suggested by Carl. As you will see from a later post I managed to mount and "VIM" the file. Wow, was that fun for the old guy. I especially thank you for the fix. Without it I would be sitting here in "darkness" with a Windoze blue screen staring at me. I hope others paid attention to your post about the fix. Would save them a lot of trouble. I hope they fix it soon. Bob S.
On Monday 27 February 2006 00:50, Bob S wrote: [...]
Thanks Lee,
I will be keeping this on file as well as a method suggested by Carl. As you will see from a later post I managed to mount and "VIM" the file. Wow, was that fun for the old guy.
I especially thank you for the fix. Without it I would be sitting here in "darkness" with a Windoze blue screen staring at me. I hope others paid attention to your post about the fix. Would save them a lot of trouble. I hope they fix it soon.
Bob S. ========
Glad to hear you got things fixed and all is back to normal. Sometimes these things happen when the SuSE guys are working on new stuff. We've actually experienced things like this before. That's why they call the Supplementary directories "experimental"! There is usually someone here that will run down the problem though, because there are many knowledgeable folks hanging out on this list. Also, thanks for the kind words, but I must admit I can't take all the credit. I had help also from a great Linux guy! regards, Lee
Carl Hartung wrote:
On Sunday 26 February 2006 17:42, B Stia wrote:
Hello SuSE people,
Did an upgrade with apt on my 10.0 last night.... Rebooted and it won't
boot.
Hi Bob,
There was a thread here in the last day on this exact problem... apparently there was a mixup causing a 10.1 component to be inadvertently installed during the update. From that thread:
"... It has to do with the file /etc/init.d/earlykdm, installed by the new kdebase3 rpms, build -27. You can edit that file with the changes I'll indicate below to put things right using the -27 build rpms.
Replace this:
if test -z "$DISPLAYMANAGER_AUTOLOGIN"; then /sbin/preload /etc/preload.d/kdm else /usr/bin/ionice -n2 /sbin/preload /etc/preload.d/kdm.auto /usr/bin/ionice -n6 /sbin/preload /etc/preload.d/kde & echo $! > /var/run/preload-session.pid fi
With this:
if test -z "$DISPLAYMANAGER_AUTOLOGIN"; then /sbin/preload < /var/cache/preload/kdm.preload else /usr/bin/ionice -n2 /sbin/preload < /var/cache/preload/kdm.auto.preload /usr/bin/ionice -n6 /sbin/preload < /var/cache/preload/kde.preload & echo $! > /var/run/preload-session.pid fi
If I were you, I'd boot into rescue mode, mount the partition and check this file out. If it matches the first section try editing it as indicated. BTW, the post I've quoted was Lee's (BandiPat's).
hth & regards,
Carl,
Well I finally remembered how to mount the system from the rescue mode. If that was something you should have seen all that old grey-matter churning while using VI.
Anyway after many hours I finally got it done and all is well again. You are all the greatest bunch of people I have ever run across with your help and suggestions. Bob S. PS How does stuff like this happen ??? All human and make mistakes like I always do, I guess
participants (9)
-
Adi Pircalabu -
B Stia -
BandiPat -
Bob S
-
Bruce Marshall -
Carl Hartung -
Jerry Feldman -
Patrick Shanahan -
tommie ramirez andujar