Re: [SLE] kernel update version 2.6.16.21-0.13-default
Joe Morris (NTM) wrote:
Ed McCanless wrote:
Joe Morris (NTM) wrote:
Carl Hartung wrote:
One more thing: Before attempting this procedure, you might want to first boot the system using your installation media (DVD/CD) and select 'Boot installed system' to ensure the appropriate environment has been established for installing the updates.
If that would work then I believe it indicates a grub problem and not a kernel problem.
Thanks for the input, Joe; Booting as Carl suggested did work. I had lucked into that solution before contacting the list. But how would that apply to all the missing modules (I got a message saying there might be some missing) and the "FATAL:"messages in the message log?
There are many possibilities. You could try running as root depmod -a and see if there is any errors. This is normally checked and run if needed in the boot scripts. Maybe it modified your modprobe.conf or associated config files to start some bogus hardware. What does uname -r give you? That would tell you which kernel you are booting with. Maybe it did not replace the old kernel, or maybe it goofed up on installing the delta and only part of the kernel was installed. I would need more info to nail it down to something more specific.
Ran depmod -a WARNING: Couldn't open directory /lib/modules/2.6.16.13-4-default: No such file or directory FATAL: Could not open /lib/modules/2.6.16.13-4-default/modules.dep.temp for writing: No such file or directory Ran uname -r 2.6.16.13-4-default Will wait for more input, before trying "repair installed system" --ED--
Ed McCanless wrote:
Ran depmod -a WARNING: Couldn't open directory /lib/modules/2.6.16.13-4-default: No such file or directory FATAL: Could not open /lib/modules/2.6.16.13-4-default/modules.dep.temp for writing: No such file or directory
Ran uname -r 2.6.16.13-4-default
Will wait for more input, before trying "repair installed system" Did you run depmod -a as root as instructed? if so, run ls -l /boot, and ls /lib/modules, followed by rpm -qa | grep kernel and send us the output.
-- Joe Morris Registered Linux user 231871
Joe Morris (NTM) wrote:
Ed McCanless wrote:
Ran depmod -a WARNING: Couldn't open directory /lib/modules/2.6.16.13-4-default: No such file or directory FATAL: Could not open /lib/modules/2.6.16.13-4-default/modules.dep.temp for writing: No such file or directory
Ran uname -r 2.6.16.13-4-default
Will wait for more input, before trying "repair installed system"
Did you run depmod -a as root as instructed? if so, run ls -l /boot, and ls /lib/modules, followed by rpm -qa | grep kernel and send us the output.
Yes, I am running all commands as root unless otherwise instructed. # ls -l /boot total 6938 -rw-r--r-- 1 root root 865822 Aug 31 12:23 System.map-2.6.16.21-0.21-default -rw------- 1 root root 512 Aug 9 13:02 backup_mbr lrwxrwxrwx 1 root root 1 Aug 9 12:57 boot -> . -rw-r--r-- 1 root root 58614 Aug 31 12:29 config-2.6.16.21-0.21-default drwxr-xr-x 2 root root 512 Sep 15 13:11 grub lrwxrwxrwx 1 root root 29 Sep 15 13:09 initrd -> initrd-2.6.16.21-0.21-default -rw-r--r-- 1 root root 2552567 Sep 15 13:09 initrd-2.6.16.21-0.21-default -rw-r--r-- 1 root root 134144 Aug 9 13:02 message -rw-r--r-- 1 root root 100440 Aug 31 12:30 symsets-2.6.16.21-0.21-default.tar.gz -rw-r--r-- 1 root root 326492 Aug 31 12:30 symtypes-2.6.16.21-0.21-default.gz -rw-r--r-- 1 root root 89098 Aug 31 12:30 symvers-2.6.16.21-0.21-default.gz -rwxr-xr-x 1 root root 1609084 Aug 31 12:28 vmlinux-2.6.16.21-0.21-default.gz lrwxrwxrwx 1 root root 30 Sep 15 13:09 vmlinuz -> vmlinuz-2.6.16.21-0.21-default -rw-r--r-- 1 root root 1341380 Aug 31 12:23 vmlinuz-2.6.16.21-0.21-default # ls /lib/modules 2.6.16.21-0.13-default 2.6.16.21-0.21-default # rpm -qa | grep kernel kernel-default-2.6.16.21-0.21 kernel-docs-2.6.16.13-4
Ed McCanless wrote:
Yes, I am running all commands as root unless otherwise instructed.
OK, thanks. Just checking.
# ls -l /boot total 6938 -rw-r--r-- 1 root root 865822 Aug 31 12:23 System.map-2.6.16.21-0.21-default -rw------- 1 root root 512 Aug 9 13:02 backup_mbr lrwxrwxrwx 1 root root 1 Aug 9 12:57 boot -> . -rw-r--r-- 1 root root 58614 Aug 31 12:29 config-2.6.16.21-0.21-default drwxr-xr-x 2 root root 512 Sep 15 13:11 grub lrwxrwxrwx 1 root root 29 Sep 15 13:09 initrd -> initrd-2.6.16.21-0.21-default -rw-r--r-- 1 root root 2552567 Sep 15 13:09 initrd-2.6.16.21-0.21-default -rw-r--r-- 1 root root 134144 Aug 9 13:02 message -rw-r--r-- 1 root root 100440 Aug 31 12:30 symsets-2.6.16.21-0.21-default.tar.gz -rw-r--r-- 1 root root 326492 Aug 31 12:30 symtypes-2.6.16.21-0.21-default.gz -rw-r--r-- 1 root root 89098 Aug 31 12:30 symvers-2.6.16.21-0.21-default.gz -rwxr-xr-x 1 root root 1609084 Aug 31 12:28 vmlinux-2.6.16.21-0.21-default.gz lrwxrwxrwx 1 root root 30 Sep 15 13:09 vmlinuz -> vmlinuz-2.6.16.21-0.21-default -rw-r--r-- 1 root root 1341380 Aug 31 12:23 vmlinuz-2.6.16.21-0.21-default
OK, good. This looks like it is all correct. It is set to start the 2.6.16-0.21-default kernel.
# ls /lib/modules 2.6.16.21-0.13-default 2.6.16.21-0.21-default
# rpm -qa | grep kernel kernel-default-2.6.16.21-0.21 kernel-docs-2.6.16.13-4 It looks like to me the upgrade of the kernel went OK. Something else is amiss. Since you mentioned uname -r gave you a different kernel, your problem must be in grub's menu.lst. Based on what you wrote above, I don't see how you can boot into a 2.6.16.13-4-default, since there is none in /boot. Could you send us your menu.lst.
-- Joe Morris Registered Linux user 231871
Joe Morris (NTM) wrote:
It looks like to me the upgrade of the kernel went OK. Something else is amiss. Since you mentioned uname -r gave you a different kernel, your problem must be in grub's menu.lst. Based on what you wrote above, I don't see how you can boot into a 2.6.16.13-4-default, since there is none in /boot. Could you send us your menu.lst.
Here's what I tried: # ls -l /boot/grub/menu.lst -rw------- 1 root root 755 Sept 15 13:11 /boot/grub/menu.lst So, it looks like I either need more help with commands, or there's nothing there. Sorry, I haven't done command line much since the 80's, and that was DOS. --ED--
Ed McCanless wrote:
Here's what I tried: # ls -l /boot/grub/menu.lst -rw------- 1 root root 755 Sept 15 13:11 /boot/grub/menu.lst
So, it looks like I either need more help with commands, or there's nothing there. Sorry, I haven't done command line much since the 80's, and that was DOS. --ED--
Can you copy and paste the file contents into an email? I see you are sending this with Thunderbird in Windows. Maybe copy the file to where you can get to it in Windows, and copy paste the contents to an email. That should get us much closer to getting this fixed. -- Joe Morris Registered Linux user 231871
Joe Morris (NTM) wrote:
Ed McCanless wrote:
Here's what I tried: # ls -l /boot/grub/menu.lst -rw------- 1 root root 755 Sept 15 13:11 /boot/grub/menu.lst
So, it looks like I either need more help with commands, or there's nothing there. Sorry, I haven't done command line much since the 80's, and that was DOS. --ED--
Can you copy and paste the file contents into an email? I see you are sending this with Thunderbird in Windows. Maybe copy the file to where you can get to it in Windows, and copy paste the contents to an email. That should get us much closer to getting this fixed.
I guess I didn't explain well enough. I can transfer the file from one computer to the other, but I could not find anything but the info above(the file name.) I don't know if the file is empty, or if I just don't know how to retrieve it. I need more command line help. --ED--
On Sunday 17 September 2006 11:23, Ed McCanless wrote:
Joe Morris (NTM) wrote:
Ed McCanless wrote:
Here's what I tried: # ls -l /boot/grub/menu.lst -rw------- 1 root root 755 Sept 15 13:11 /boot/grub/menu.lst
So, it looks like I either need more help with commands, or there's nothing there. Sorry, I haven't done command line much since the 80's, and that was DOS. --ED--
Can you copy and paste the file contents into an email? I see you are sending this with Thunderbird in Windows. Maybe copy the file to where you can get to it in Windows, and copy paste the contents to an email. That should get us much closer to getting this fixed.
I guess I didn't explain well enough. I can transfer the file from one computer to the other, but I could not find anything but the info above(the file name.) I don't know if the file is empty, or if I just don't know how to retrieve it. I need more command line help. --ED--
You can use cat /boot/grub/menu.lst to output the file content in your console terminal, similar to "type" from DOS. The command "less" lets you visualize a long file, paging up and down, but the contents disappear when you exit with "q". Joe's suggestion implies that you can copy the file to your Windows partition: cp /boot/grub/menu.lst /windows/C/ and then open the file with notepad and copy it into your Thunderbird email. Carlos FL --
Carlos F Lange wrote:
On Sunday 17 September 2006 11:23, Ed McCanless wrote:
Joe Morris (NTM) wrote:
Ed McCanless wrote:
Here's what I tried: # ls -l /boot/grub/menu.lst -rw------- 1 root root 755 Sept 15 13:11 /boot/grub/menu.lst
So, it looks like I either need more help with commands, or there's nothing there. Sorry, I haven't done command line much since the 80's, and that was DOS. --ED--
Can you copy and paste the file contents into an email? I see you are sending this with Thunderbird in Windows. Maybe copy the file to where you can get to it in Windows, and copy paste the contents to an email. That should get us much closer to getting this fixed.
I guess I didn't explain well enough. I can transfer the file from one computer to the other, but I could not find anything but the info above(the file name.) I don't know if the file is empty, or if I just don't know how to retrieve it. I need more command line help. --ED--
You can use cat /boot/grub/menu.lst to output the file content in your console terminal, similar to "type" from DOS. The command "less" lets you visualize a long file, paging up and down, but the contents disappear when you exit with "q".
Joe's suggestion implies that you can copy the file to your Windows partition: cp /boot/grub/menu.lst /windows/C/ and then open the file with notepad and copy it into your Thunderbird email.
Carlos FL
Thanks,Carlos: I knew I was probably doing something wrong. I need a good book on Linux commands. Will have to use a disc. I have two separate computers. --ED--
Joe Morris (NTM) wrote:
Can you copy and paste the file contents into an email? I see you are sending this with Thunderbird in Windows. Maybe copy the file to where you can get to it in Windows, and copy paste the contents to an email. That should get us much closer to getting this fixed.
I believe this is right: # cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Fri Sep 15 13:11:18 EDT 2006 color white/blue black/light-gray default 0 timeout 8 gfxmenu (hd0,1)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE Linux 10.1 root (hd0,1) kernel /boot/vmlinuz root=/dev/hda2 vga=0x314 resume=/dev/hda1 splash=silent showopts initrd /boot/initrd ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy chainloader (fd0)+1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- SUSE Linux 10.1 root (hd0,1) kernel /boot/vmlinuz root=/dev/hda2 vga=normal showopts ide=nodma apm=off acpi=off noresume edd=off 3 initrd /boot/initrd Thanks to Carlos F Lange for helping me get this. --ED--
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-09-17 at 14:31 -0400, Ed McCanless wrote:
I believe this is right:
# cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Fri Sep 15 13:11:18 EDT 2006 color white/blue black/light-gray default 0 timeout 8 gfxmenu (hd0,1)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE Linux 10.1 root (hd0,1) kernel /boot/vmlinuz root=/dev/hda2 vga=0x314 resume=/dev/hda1 splash=silent showopts initrd /boot/initrd
Nothing wrong there. It wasn't touched. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFDZg7tTMYHG2NR9URArg2AJ9xkvXFnPy1pA9fLvVFafyaqn7ixgCdGTSH SMJNLD5yPVWev12WhvxnsxI= =BRgq -----END PGP SIGNATURE-----
I believe this is right:
# cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Fri Sep 15 13:11:18 EDT 2006 color white/blue black/light-gray default 0 So this means the entry auto chosen is the first one timeout 8 gfxmenu (hd0,1)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE Linux 10.1 root (hd0,1) kernel /boot/vmlinuz root=/dev/hda2 vga=0x314 resume=/dev/hda1 splash=silent showopts initrd /boot/initrd This all looks correct. So, it is not your menu.lst, and if it tries to boot, it is not grub. Your kernel images look fine in boot. That comes down to a possibility
Ed McCanless wrote: the kernel module tree is messed up, if I still remember the problem correctly. Try rpm -V kernel-default, and/or ls -R /lib/modules/2.6.16.21-0.21-default/ which will be long, to long to transcribe to a different computer. If the first comes back clean, transcribe that one, if the second is short, then that one. If the first comes back clean, your kernel (according to rpm) is OK. If the second is long, it confirms what rpm is saying. If your kernel tree looks good, your machine should be working. BTW, how are you booting to get this info from your system? I am still confused by the uname -r output compared to ls /lib/modules. -- Joe Morris Registered Linux user 231871
Joe Morris (NTM) wrote:
This all looks correct. So, it is not your menu.lst, and if it tries to boot, it is not grub. Your kernel images look fine in boot. That comes down to a possibility the kernel module tree is messed up, if I still remember the problem correctly. Try rpm -V kernel-default, and/or ls -R /lib/modules/2.6.16.21-0.21-default/ which will be long, to long to transcribe to a different computer. If the first comes back clean, transcribe that one, if the second is short, then that one. If the first comes back clean, your kernel (according to rpm) is OK. If the second is long, it confirms what rpm is saying. If your kernel tree looks good, your machine should be working. BTW, how are you booting to get this info from your system? I am still confused by the uname -r output compared to ls /lib/modules.
I will try all the above. I am not re-booting. As stated in my 1st mailing "Finally got the system running by going into install and then backing out to "boot from hard drive." " I got lucky, and I left the machine running so I could supply all the files I knew I was going to be asked for. Thanks again for helping, --ED--
Joe Morris (NTM) wrote:
That comes down to a possibility the kernel module tree is messed up, if I still remember the problem correctly. Try rpm -V kernel-default, and/or ls -R /lib/modules/2.6.16.21-0.21-default/ which will be long, to long to transcribe to a different computer. If the first comes back clean, transcribe that one, if the second is short, then that one. If the first comes back clean, your kernel (according to rpm) is OK. If the second is long, it confirms what rpm is saying. If your kernel tree looks good, your machine should be working. BTW, how are you booting to get this info from your system? I am still confused by the uname -r output compared to ls /lib/modules.
OK, the command "rpm -V kernel-default" gives me nothing -- just returns to the command prompt. That's shorter than I expected. ls -R /lib/modules/2.6.16.21-0.21-default/ gives me a 36.7 KB file that looks complete, which I can send if it's not too large for the list. My CD burner is still working. Is this the kernel tree you referred to, or is that something else I need to know how to access? Also, my machine is working, partly. Just wont boot on its own, play sound, recognize my Ethernet card, and I don't know how many other things. This thread is getting pretty long. Should I go back thru all this mail and try to compile a short summary? --ED--
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-09-17 at 22:11 -0400, Ed McCanless wrote:
OK, the command "rpm -V kernel-default" gives me nothing -- just returns to the command prompt. That's shorter than I expected.
That's standard *nix behaviour, it means Ok.
ls -R /lib/modules/2.6.16.21-0.21-default/ gives me a 36.7 KB file that looks complete, which I can send if it's not too large for the list.
No, better email it off list. Try this: cer@nimrodel:~> ls -R /lib/modules/2.6.16.21-0.21-default | wc -l 2688 That's about the number of files there I have. Another idea; compare this one to your's: cer@nimrodel:~> ls -l /lib/modules/2.6.16.21-0.21-default total 1400 lrwxrwxrwx 1 root root 46 2006-09-16 01:28 build -> /usr/src/linux-2.6.16.21-0.21-obj/i386/default drwxr-xr-x 11 root root 4096 2006-09-16 01:29 kernel -rw-r--r-- 1 root root 288969 2006-09-16 01:29 modules.alias -rw-r--r-- 1 root root 69 2006-09-16 01:29 modules.ccwmap -rw-r--r-- 1 root root 361618 2006-09-16 01:29 modules.dep -rw-r--r-- 1 root root 813 2006-09-16 01:29 modules.ieee1394map -rw-r--r-- 1 root root 654 2006-09-16 01:29 modules.inputmap -rw-r--r-- 1 root root 21839 2006-09-16 01:29 modules.isapnpmap -rw-r--r-- 1 root root 74 2006-09-16 01:29 modules.ofmap -rw-r--r-- 1 root root 234424 2006-09-16 01:29 modules.pcimap -rw-r--r-- 1 root root 967 2006-09-16 01:29 modules.seriomap -rw-r--r-- 1 root root 137628 2006-09-16 01:29 modules.symbols -rw-r--r-- 1 root root 9586 2006-09-16 01:29 modules.unsupported -rw-r--r-- 1 root root 313862 2006-09-16 01:29 modules.usbmap lrwxrwxrwx 1 root root 29 2006-09-16 01:29 source -> /usr/src/linux-2.6.16.21-0.21 drwxr-xr-x 2 root root 4096 2006-09-16 01:29 weak-updates
This thread is getting pretty long. Should I go back thru all this mail and try to compile a short summary?
No need, I think... - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFDgSUtTMYHG2NR9URAsn3AJ9z4BJxqsWngT3o/vR5vMquHOlIXACggREg GtyjtVpStWFQrseWfQASokM= =X9Jz -----END PGP SIGNATURE-----
Ed McCanless wrote:
OK, the command "rpm -V kernel-default" gives me nothing -- just returns to the command prompt. That's shorter than I expected. But very good news. Rpm says the kernel upgrade worked.
ls -R /lib/modules/2.6.16.21-0.21-default/ gives me a 36.7 KB file that looks complete, which I can send if it's not too large for the list. Not necessary. I think that conforms rpm is correct. Given this, I don't believe reinstalling the kernel will help, but I think you are very close. My CD burner is still working. Is this the kernel tree you referred to, or is that something else I need to know how to access? That is it. I called it a tree because of its directory structure containing the modules. Also, my machine is working, partly. Just wont boot on its own, play sound, recognize my Ethernet card, and I don't know how many other things.
OK, so since your kernel is ok, /boot looks good, and your menu.lst is good, it must have messed up installing grub. Why the kernel rpm thinks it needs to mess with grubs installation is beside me, but I have seen this in 10.1 and yet do not understand it. I believe you will be working again by reinstalling grub through grub. Do the following as root at the cli. grub (this will enter a grub prompt, like grub>) From the grub prompt, enter root (hd0,1) this will give info about the filesystem. then, after this setup (hd0) it should check on stage 1, 2, and the filesystems 1.5, then embed stage1.5 and install stage 1 and 2 quit this will leave grub now you should be able to reboot.
This thread is getting pretty long. Should I go back thru all this mail and try to compile a short summary?
You just did, when you said it just won't boot on its own. Hope that gets it. -- Joe Morris Registered Linux user 231871
Joe Morris (NTM) wrote:
I believe you will be working again by reinstalling grub through grub. Do the following as root at the cli.
grub (this will enter a grub prompt, like grub>) From the grub prompt, enter root (hd0,1) this will give info about the filesystem. then, after this setup (hd0) it should check on stage 1, 2, and the filesystems 1.5, then embed stage1.5 and install stage 1 and 2 quit this will leave grub
now you should be able to reboot.
Just to make clear in my mind, is everything needed for this install on the hd already, or will I need the installation media? Thanks, --ED--
Joe Morris (NTM) wrote:
now you should be able to reboot.
Almost forgot to make sure you have noticed what Anders Johansson brought up about another system on hdb. Sorry I failed to mention that at the beginning. Please forgive my ignorance. --ED--
Ed McCanless wrote:
Almost forgot to make sure you have noticed what Anders Johansson brought up about another system on hdb. Sorry I failed to mention that at the beginning. Learning is a life long process that begins when we are born. Anyway, your other system was not in your menu.lst IIRC. How do you boot into it? Do you manually change the boot order in BIOS? I think you mentioned it is Debian. You could easily add it to your SUSE menu.lst (no need to reinstall grub) to gracefully boot into either system. HTH
-- Joe Morris Registered Linux user 231871
Joe Morris (NTM) wrote:
Ed McCanless wrote:
Almost forgot to make sure you have noticed what Anders Johansson brought up about another system on hdb. Sorry I failed to mention that at the beginning.
Learning is a life long process that begins when we are born. Anyway, your other system was not in your menu.lst IIRC. How do you boot into it? Do you manually change the boot order in BIOS? I think you mentioned it is Debian. You could easily add it to your SUSE menu.lst (no need to reinstall grub) to gracefully boot into either system. HTH
The Debian install set up a "select" screen where I can choose the system to boot into, much as SuSE does if it is the second sys to be installed. This all works, and Debian boots fine, although I felt I was getting in over my head at the point where the gui was to be installed, and between doing research before proceeding and trying to get the most out of SuSE 10.1 I haven't found time to get back to it yet. Their documentation seems to be much more extensive, and as I soon found, much more necessary. Any way, I was in grub on the other computer when this mail came in. All set to try out your instructions and send you a success report. --ED--
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-09-18 at 20:02 -0400, Ed McCanless wrote:
The Debian install set up a "select" screen where I can choose the system to boot into, much as SuSE does if it is the second sys to be installed. This all works, and Debian boots fine, although I felt I was getting in over my head at
You mean it still works, no problem there? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFDzqHtTMYHG2NR9URAtKsAJ9o5+ZcFoky6tiFaa/vcqZHw4tuOACdEimi FUR6pcr5B4PJb6PYi5pxvW0= =/rQi -----END PGP SIGNATURE-----
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Monday 2006-09-18 at 20:02 -0400, Ed McCanless wrote:
The Debian install set up a "select" screen where I can choose the system to boot into, much as SuSE does if it is the second sys to be installed. This all works, and Debian boots fine, although I felt I was getting in over my head at
You mean it still works, no problem there?
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFFDzqHtTMYHG2NR9URAtKsAJ9o5+ZcFoky6tiFaa/vcqZHw4tuOACdEimi FUR6pcr5B4PJb6PYi5pxvW0= =/rQi -----END PGP SIGNATURE-----
That's right. Only the SuSE system would not boot except through use of the installation media. --ED--
Ed McCanless wrote:
Carlos E. R. wrote:
The Monday 2006-09-18 at 20:02 -0400, Ed McCanless wrote:
The Debian install set up a "select" screen where I can choose the system to boot into, much as SuSE does if it is the second sys to be installed. This all works, and Debian boots fine, although I felt I was getting in over my head at
You mean it still works, no problem there?
That's right. Only the SuSE system would not boot except through use of the installation media. --ED--
If Debian still boots, then whichever drive you have set in your BIOS to boot from, Debian has installed grub there and pointed it to its install, and should have made an entry in its menu.lst for Suse. My instructions will overwrite Debian's grub, and SUSE will work, but you will need to add a menu option for Debian to boot it. Grub only needs to be on there once, pointing to a menu.lst to know where everything is to be able to boot. Booting multiple systems is grubs strength. -- Joe Morris Registered Linux user 231871
Joe Morris (NTM) wrote:
Learning is a life long process that begins when we are born. Anyway, your other system was not in your menu.lst IIRC. How do you boot into it? Do you manually change the boot order in BIOS? I think you mentioned it is Debian. You could easily add it to your SUSE menu.lst (no need to reinstall grub) to gracefully boot into either system. HTH
System boots normally now. Many thanks to Joe,Carlos E. R., Carlos F. Lange, Carl, John Perry, John Andersen, and Anders Johansson. Joe, I know you and others probably know this solution didn' offer me the option of booting Debian, but that's not a problem. I had about decided to back out of that project anyway. Thanks again to everyone, --ED--
System boots normally now. Many thanks to Joe,Carlos E. R., Carlos F. Lange, Carl, John Perry, John Andersen, and Anders Johansson. Joe, I know you and others probably know this solution didn' offer me the option of booting Debian, but that's not a problem. I had about decided to back out of that project anyway. Just add the pertinent info to your menu.lst. You could always mount
Ed McCanless wrote: the Debian partition to /mnt to look at what they did. Glad you got your SUSE going anyway. -- Joe Morris Registered Linux user 231871
Joe Morris (NTM) wrote:
Ed McCanless wrote:
System boots normally now. Many thanks to Joe,Carlos E. R., Carlos F. Lange, Carl, John Perry, John Andersen, and Anders Johansson. Joe, I know you and others probably know this solution didn' offer me the option of booting Debian, but that's not a problem. I had about decided to back out of that project anyway.
Just add the pertinent info to your menu.lst. You could always mount the Debian partition to /mnt to look at what they did. Glad you got your SUSE going anyway.
Thanks, I'm not quite sure what I'll do, but I'm leaning more toward installing a second SuSE system on the other drive, now. That way I could use one to test new things on. Someone helping on this update problem suggested something like that, but just glancing through all this mail, I couldn't find the reference. Anyway I'm sure I'll probably need more help along the way. I believe I was working on sound fonts when this all started. Many thanks to all, --ED--
Joe Morris (NTM) wrote:
Ed McCanless wrote:
Ran depmod -a WARNING: Couldn't open directory /lib/modules/2.6.16.13-4-default: No such file or directory FATAL: Could not open /lib/modules/2.6.16.13-4-default/modules.dep.temp for writing: No such file or directory
Ran uname -r 2.6.16.13-4-default
I got an error like this when I updated the kernel and forgot to reboot. You did reboot after the update, right? -- John Perry
John E. Perry wrote:
Joe Morris (NTM) wrote:
Ed McCanless wrote:
Ran depmod -a WARNING: Couldn't open directory /lib/modules/2.6.16.13-4-default: No such file or directory FATAL: Could not open /lib/modules/2.6.16.13-4-default/modules.dep.temp for writing: No such file or directory
Ran uname -r 2.6.16.13-4-default
I got an error like this when I updated the kernel and forgot to reboot. You did reboot after the update, right?
Yes, that's where it all started. --ED--
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2006-09-16 at 16:00 -0400, Ed McCanless wrote:
Ran depmod -a WARNING: Couldn't open directory /lib/modules/2.6.16.13-4-default: No such file or directory FATAL: Could not open /lib/modules/2.6.16.13-4-default/modules.dep.temp for writing: No such file or directory
Ran uname -r 2.6.16.13-4-default
- From the above we have two things. First, the installed kernel is not the one you updated to, notice the different numbers. Second, the modules are probably missing, a bad install/update. Either that, or you are posting the results from the rescue kernel. I think you'd be better by reinstalling the kernel as I said yesterday. It should be faster.IMO. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFDImutTMYHG2NR9URAg/vAJ9a6uffUT0eCw4M39FgETAAzqFtMwCdFVsK ocKlFKH48NSeF6MjM5VRklU= =Fwz7 -----END PGP SIGNATURE-----
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Saturday 2006-09-16 at 16:00 -0400, Ed McCanless wrote:
Ran depmod -a WARNING: Couldn't open directory /lib/modules/2.6.16.13-4-default: No such file or directory FATAL: Could not open /lib/modules/2.6.16.13-4-default/modules.dep.temp for writing: No such file or directory
Ran uname -r 2.6.16.13-4-default
- From the above we have two things. First, the installed kernel is not the one you updated to, notice the different numbers. Second, the modules are probably missing, a bad install/update.
Either that, or you are posting the results from the rescue kernel.
I think you'd be better by reinstalling the kernel as I said yesterday. It should be faster.IMO.
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFFDImutTMYHG2NR9URAg/vAJ9a6uffUT0eCw4M39FgETAAzqFtMwCdFVsK ocKlFKH48NSeF6MjM5VRklU= =Fwz7 -----END PGP SIGNATURE-----
This is along the lines I was thinking, but the checks Joe requested seem to indicate that the new kernel is there. --ED--
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2006-09-16 at 20:35 -0400, Ed McCanless wrote:
I think you'd be better by reinstalling the kernel as I said yesterday. It should be faster.IMO.
This is along the lines I was thinking, but the checks Joe requested seem to indicate that the new kernel is there.
Maybe it is incomplete; not the /boot image, but the modules, that are many and use quite some space. Youd don't happen to have a nearly full disk, per chance? That happened to me once, the update could not complete. Something there did not update correctly who knows why. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFDLMptTMYHG2NR9URAgn1AJ9Hj/SP4S2n3vUkfLiZjoykLuhmYQCdG04w 93NUH7QFRPPQnxym3IilQCQ= =gv8d -----END PGP SIGNATURE-----
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Saturday 2006-09-16 at 20:35 -0400, Ed McCanless wrote:
I think you'd be better by reinstalling the kernel as I said yesterday. It should be faster.IMO.
This is along the lines I was thinking, but the checks Joe requested seem to indicate that the new kernel is there.
Maybe it is incomplete; not the /boot image, but the modules, that are many and use quite some space. Youd don't happen to have a nearly full disk, per chance? That happened to me once, the update could not complete. Something there did not update correctly who knows why.
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFFDLMptTMYHG2NR9URAgn1AJ9Hj/SP4S2n3vUkfLiZjoykLuhmYQCdG04w 93NUH7QFRPPQnxym3IilQCQ= =gv8d -----END PGP SIGNATURE-----
I have plenty of space left. Usage on hda2 is only 26% of 20GB. The larger partition, hda3, is 14.5% of 89.8GB. According to the files Joe Morris advised me to check, it looks like modules for both kernels are there somewhere: # ls /lib/modules 2.6.16.21-0.13-default 2.6.16.21-0.21-default # rpm -qa | grep kernel kernel-default-2.6.16.21-0.21 kernel-docs-2.6.16.13-4 The kernel-docs don't match, but I'm used to seeing out of date docs. Then there is the check you had me run: Ran uname -r
2.6.16.13-4-default
It seems the system is giving conflicting reports depending on where the info is drawn from. As to the re-install you advised, I'm sure that would be fastest, but if proceeding another way will provide useful info for anyone I am willing. I'm sure I would learn from the experience.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-09-17 at 00:10 -0400, Ed McCanless wrote:
Maybe it is incomplete; not the /boot image, but the modules, that are many and use quite some space. Youd don't happen to have a nearly full disk, per chance? That happened to me once, the update could not complete. Something there did not update correctly who knows why.
I have plenty of space left. Usage on hda2 is only 26% of 20GB. The larger partition, hda3, is 14.5% of 89.8GB.
Good.
According to the files Joe Morris advised me to check, it looks like modules for both kernels are there somewhere:
# ls /lib/modules 2.6.16.21-0.13-default 2.6.16.21-0.21-default
That's true, they are there, but they might be incomplete. Notice that they are some 1703 files (in my system) plus depmod info - have you checked them all? No? Then reinstall the rpm.
# rpm -qa | grep kernel kernel-default-2.6.16.21-0.21 kernel-docs-2.6.16.13-4
The kernel-docs don't match, but I'm used to seeing out of date docs.
They don't match here either.
Then there is the check you had me run:
Ran uname -r
2.6.16.13-4-default
It seems the system is giving conflicting reports depending on where the info is drawn from.
You would see that number if you were running the rescue system from the CD. If not, and that is what you see on you real system, you have a really hosed update! So, redo it!
As to the re-install you advised, I'm sure that would be fastest, but if proceeding another way will provide useful info for anyone I am willing. I'm sure I would learn from the experience.
Well... as you like. I'll stay listening, but I don't hope much that way. I could be mistaken, of course, but my intuition/experience tells me otherwise. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFDZXjtTMYHG2NR9URAr1NAJ9AK8kcx8v3BfUQ2hxoJJ2kYqKunACeLq6e 8glKX2esbt0Fu78rbyqhYEc= =UKOM -----END PGP SIGNATURE-----
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2006-09-17 at 00:10 -0400, Ed McCanless wrote:
Maybe it is incomplete; not the /boot image, but the modules, that are many and use quite some space. Youd don't happen to have a nearly full disk, per chance? That happened to me once, the update could not complete. Something there did not update correctly who knows why.
I have plenty of space left. Usage on hda2 is only 26% of 20GB. The larger partition, hda3, is 14.5% of 89.8GB.
Good.
According to the files Joe Morris advised me to check, it looks like modules for both kernels are there somewhere:
# ls /lib/modules 2.6.16.21-0.13-default 2.6.16.21-0.21-default
That's true, they are there, but they might be incomplete. Notice that they are some 1703 files (in my system) plus depmod info - have you checked them all? No? Then reinstall the rpm.
# rpm -qa | grep kernel kernel-default-2.6.16.21-0.21 kernel-docs-2.6.16.13-4
The kernel-docs don't match, but I'm used to seeing out of date docs.
They don't match here either.
Then there is the check you had me run:
Ran uname -r
2.6.16.13-4-default
It seems the system is giving conflicting reports depending on where the info is drawn from.
You would see that number if you were running the rescue system from the CD. If not, and that is what you see on you real system, you have a really hosed update! So, redo it!
As to the re-install you advised, I'm sure that would be fastest, but if proceeding another way will provide useful info for anyone I am willing. I'm sure I would learn from the experience.
Well... as you like. I'll stay listening, but I don't hope much that way. I could be mistaken, of course, but my intuition/experience tells me otherwise.
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFFDZXjtTMYHG2NR9URAr1NAJ9AK8kcx8v3BfUQ2hxoJJ2kYqKunACeLq6e 8glKX2esbt0Fu78rbyqhYEc= =UKOM -----END PGP SIGNATURE-----
Thanks Carlos, This is what I was afraid of from the first, but I don't have the rpm's. I didn't think to uncheck the delete box. I'm not sure if I can get the system back on line to download them. I may have to find a source and transfer the rpm's to disc to do a manual install. That or re-install from my installation CD and start over. Before doing that I wanted to learn as much as I could about the situation, and make sure there wasn't a bug that needed reporting. --ED-- P.S. Also I am trying to learn 3Ghz technology here with a 100mgz brain.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-09-17 at 16:04 -0400, Ed McCanless wrote:
This is what I was afraid of from the first, but I don't have the rpm's. I didn't think to uncheck the delete box.
10.1 does not save the rpms, regardless of the ticked state of that box. I'd be happy if somebody can demonstrate the contrary by telling me where they are saved (no, they are not under /var/lib/YaST2/you/i386/update/ nor in any place under /var). Quite some people have asked here where they are and nobody has solved the question. :-(
I'm not sure if I can get the system back on line to download them. I may have to find a source and transfer the rpm's to disc to do a manual install. That or re-install from my installation CD and start over. Before doing that I wanted to learn as much as I could about the situation, and make sure there wasn't a bug that needed reporting.
You can, of course, download the kernel rpms them manually (on another system), or install the original one from the dvd. That doesn't mean reinstalling the whole system, just the kernel. The procedure I already explained the other day.
--ED-- P.S. Also I am trying to learn 3Ghz technology here with a 100mgz brain.
X-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFDbfctTMYHG2NR9URAp+6AJ9rUFesYapWm+/TArA7IeERitw4NgCeNkyz X8qJCDD6Na84AvZJsIGxXUo= =HTfb -----END PGP SIGNATURE-----
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2006-09-17 at 16:04 -0400, Ed McCanless wrote:
This is what I was afraid of from the first, but I don't have the rpm's. I didn't think to uncheck the delete box.
10.1 does not save the rpms, regardless of the ticked state of that box. I'd be happy if somebody can demonstrate the contrary by telling me where they are saved (no, they are not under /var/lib/YaST2/you/i386/update/ nor in any place under /var). Quite some people have asked here where they are and nobody has solved the question. :-(
I'm not sure if I can get the system back on line to download them. I may have to find a source and transfer the rpm's to disc to do a manual install. That or re-install from my installation CD and start over. Before doing that I wanted to learn as much as I could about the situation, and make sure there wasn't a bug that needed reporting.
You can, of course, download the kernel rpms them manually (on another system), or install the original one from the dvd. That doesn't mean reinstalling the whole system, just the kernel. The procedure I already explained the other day.
--ED-- P.S. Also I am trying to learn 3Ghz technology here with a 100mgz brain.
X-)
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFFDbfctTMYHG2NR9URAp+6AJ9rUFesYapWm+/TArA7IeERitw4NgCeNkyz X8qJCDD6Na84AvZJsIGxXUo= =HTfb -----END PGP SIGNATURE-----
I still have your instructions, I am saving all comments on this issue, and plan to put them on a permanent disc for future reference. The installation media I have is the iso CD set which I downloaded in July and installed about the 1st of Aug. If I understand correctly, I can re-install the old kernel and then try the update again, possibly from source other than on line update, so I can have a saved rpm source to work from. But, I do want to give Joe a chance to help me learn as much as possible about what has happened. I really appreciate all the help, --ED--
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-09-17 at 20:35 -0400, Ed McCanless wrote:
I still have your instructions, I am saving all comments on this issue, and plan to put them on a permanent disc for future reference. The installation media I have is the iso CD set which I downloaded in July and installed about the 1st of Aug.
If I understand correctly, I can re-install the old kernel and then try the update again, possibly from source other than on line update, so I can have a saved rpm source to work from.
There are many ways to skin a cat :-) You may reinstall the kernel from the CD, boot the system and finally, fire up YOU again to try the update. You shouldn't have problems, these things are rare, but cross your fingers (it did happen to me once, and here I am ;-) ) Or, using another computer, you may download the kernel rpms and install it directly. In my system, YOU installed these this time: kernel-source 2.6.16.21 0.21 udev 085 30.13 mkinitrd 1.2 106.18 kernel-default 2.6.16.21 0.21 kernel-syms 2.6.16.21 0.21 I got the list from the command: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} %{BUILDTIME:day}%-30{NAME}\t%{VERSION} %{RELEASE} %35{PACKAGER}\n" | sort | less -S Yours might be slightly different. By the way, I like to have another small linux system in the same computer to use in these occasions. More comfortable than using the rescue system on CD, more powerful.
But, I do want to give Joe a chance to help me learn as much as possible about what has happened.
Ok :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFDgCCtTMYHG2NR9URAnCwAKCRS7e2NwEZXfRpeNv/BzN4UzxImACfV536 D9u++fbPWyzCX5VeTngWMHs= =yvuG -----END PGP SIGNATURE-----
participants (5)
-
Carlos E. R. -
Carlos F Lange -
Ed McCanless -
Joe Morris (NTM) -
John E. Perry