update - now won't reboot
Box specs
Dell Dimension 3000 P4 2.8 / 1G RAM / 2 x 80 G HD Dual boot Win XP home (original installation) / Linux Suse 9.2 (from cover disk Linux Format magazine) Initial install fit 2nd brand new HD boot windows boot with DVD in place and accept the defaults to install suse. Works very well with the exception of BT Voyager 1040 WIFI card. (Cant get wifi to work but can use good old copper as a back up in the meantime another problem for another day) Has been happily working away for the past couple of months. Suse looks for updates. On the latest update at the weekend, I accepted the recommendations and I believe the kernel was updated (not sure I am very new to Linux and not much cop with any other actually) At the end of this there was a comment about doing something (updating) the sbin/lilo. This was not done and the PC would then not boot. I still do not know what I have to do. I can find files etc but when I look at the contents / settings I do not really want to go changing anything as I do not have any real idea of what it is that I am changing and what the consequences could be. I have tried recovering and reinstalling. This has gotten me to the point where it shall boot but when I try to restart it falls over. Error message has been different one refers to an error in the kernel and the other is in the text check list on start up that goes along fine then scrolls a screed of numbers very fast, then refers to a null pointer in 000 (forget how many 0s)20. At this point it is a full stop, kick the plug out of the wall socket. I tried the update for the kernel again but it would not do it. This is my first foray into using Linux and I am impressed. I want to recover this PC to work with Linux. Please dont send me back to Windows. |
Can you tell me exactly what the screen says when it stops booting?
Can you get me a copy of your /boot/grub/menu.lst file? And finally, a list of your mount points (/etc/fstab)? |
Something else that might be useful is a listing (ls -l) of the /boot directory - SuSE work using links in there to point to the kernel and initrd files so they need to be accurate.
|
Thanks for offering assistance
Last night I had 7 attempts before successfully booting. 1st attempt error Segmentation fault System boot control: the system has been set up system boot control: running /etc/init.d/boot.local Segmentation fault - failed 2nd attempt Kde light blue screen appeared with "X" for cursor - frozen no further activity. 3rd attempt continuously scrolling text [<c0------>] more text all moving to fast to read 4th attempt <1> unable to handle kernel null pointer dereference at virtual address 00000020 printing eip: C011ad61 *pde = 5th attempt Segmentation fault master resource control: run level 5 has been reached failed services in run level 5: network skipped services in run level 5: nfs 6th attempt <0> kernel panic - not syncing: attempting to kill init! /etc/fstab /dev/hdb2 / reiserfs acl,user_xattr 1 1 /dev/hda2 /windows/C ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0 /dev/hda3 /windows/D vfat users,gid=users,umask=0002,iocharset=utf8 0 0 /dev/hdb1 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 sysfs /sys sysfs noauto 0 0 /dev/dvd /media/dvd subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 601vd1j:/ # ls . bin dev home media opt root srv tmp var .. boot etc lib mnt proc sbin sys usr windows 601vd1j:/ # cd boot 601vd1j:/boot # ls -l total 5430 drwxr-xr-x 3 root root 496 2005-03-28 18:05 . drwxr-xr-x 22 root root 512 2005-03-28 18:55 .. -rw-r--r-- 1 root root 512 2005-03-28 18:05 backup_mbr lrwxrwxrwx 1 root root 1 2005-03-05 15:00 boot -> . -rw-r--r-- 1 root root 57530 2005-03-18 12:58 config-2.6.8-24.13-default drwxr-xr-x 2 root root 544 2005-03-28 18:03 grub lrwxrwxrwx 1 root root 26 2005-03-27 22:37 initrd -> initrd-2.6.8-24.13-default -rw-r--r-- 1 root root 1134604 2005-03-27 22:37 initrd-2.6.8-24.13-default -rw-r--r-- 1 root root 107520 2005-03-28 18:05 message -rw-r--r-- 1 root root 79222 2005-03-18 12:59 symvers-2.6.8-24.13-i386-default.gz -rw-r--r-- 1 root root 739797 2005-03-18 12:38 System.map-2.6.8-24.13-default -rw-r--r-- 1 root root 1857351 2005-03-18 12:58 vmlinux-2.6.8-24.13-default.gz lrwxrwxrwx 1 root root 27 2005-03-27 22:37 vmlinuz -> vmlinuz-2.6.8-24.13-default -rw-r--r-- 1 root root 1555703 2005-03-18 12:38 vmlinuz-2.6.8-24.13-default 601vd1j:/boot # I am having difficulty getting at the /boot/grub/menu.lst file. I can locate it but I cannot access as it is locked to me as a user. When I tried to switch user and log in as root everything froze again. on reboot I tried to copy the file to a USB flash memory stick. this resulted in the the following error when I tried to open konqueror Opened kwrited listening on device /dev/pts/0 message from syslogd@601vd1J at ---- 601vd1j kernel: flags: 0x20020068 mapping: f2585118 mapcount:0 count:1 601vd1j kernel: backtrace 601vd1j kernel:trying to fix it up, but reboot is needed 601vd1j kernel:bad page state at prep_new_page(in process 'syslogd'.page c16103a0) Looking at YAST - bootloader configuration I appear to have lilo as the bootloader I will try again to log in as root and copy the /grub/menu.lst but I think this is enough for one posting Thanks again for assistance |
managed to copy the /boot/grub/menu.lst
# Modified by YaST2. Last modification on Mon Mar 28 18:03:24 2005 color white/blue black/light-gray default 0 timeout 8 gfxmenu (hd1,1)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE LINUX 9.2 kernel (hd1,1)/boot/vmlinuz root=/dev/hdb2 selinux=0 resume=/dev/hdb1 showopts splash=silent desktop elevator=as initrd (hd1,1)/boot/initrd title windows 1 root (hd0,1) chainloader +1 title windows 2 root (hd0,2) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- SUSE LINUX 9.2 kernel (hd1,1)/boot/vmlinuz root=/dev/hdb2 showopts ide=nodma apm=off acpi=off vga=normal noresume selinux=0 barrier=off nosmp noapic maxcpus=0 3 initrd (hd1,1)/boot/initrd |
I'm not an expert on these things (still a newbie myself to be honest), but the kernel module doesn't seem to be following SuSE's normal naming convention. I thought they changed the build version at the end (on SuSE 9.0 the kernel went 2.4.21-99 to 2.4.21.199 to 2.4.21.273 - on my install anyway) - yours seems to have an additional .13. Can you do an ls -l on the /usr/src directory and /lib/modules directory?
|
Thanks Brundles
/usr/src 601vd1j:/usr/src # ls -l total 0 drwxr-xr-x 4 root root 112 2004-10-14 16:48 . drwxr-xr-x 12 root root 344 2005-03-28 00:18 .. drwxr-xr-x 3 root root 72 2005-03-27 22:37 linux-2.6.8-24.13-obj drwxr-xr-x 7 root root 168 2004-10-14 16:48 packages 601vd1j:/usr/src # /lib/modules 601vd1j:/lib/modules # ls -l total 4 drwxr-xr-x 8 root root 256 2004-10-14 16:48 . drwxr-xr-x 13 root root 3280 2005-03-28 18:46 .. drwxr-xr-x 4 root root 96 2005-03-27 22:37 2.6.8-24.11-default drwxr-xr-x 4 root root 504 2005-03-27 22:37 2.6.8-24.13-default drwxr-xr-x 4 root root 400 2005-03-28 00:05 2.6.8-24-default drwxr-xr-x 2 root root 48 2005-03-18 12:59 2.6.8-override-default drwxr-xr-x 3 root root 88 2005-03-27 22:37 precompiled drwxr-xr-x 3 root root 104 2005-03-18 12:59 scripts 601vd1j:/lib/modules # The PC is actually behaving itself reasonably well over the past few days, but I haven't changes anything so I suspect that the root of the problem still exists. Thanks again for assisting. |
All times are GMT -5. The time now is 11:14 AM. |