running antiX-pt1, used smxi to antiX sid sidux using apt, installed newest kernel, dist-upgrade all installed ok, however when I go to boot the new kernel, after typing username and then password, I get login failed, then back to login screen, ctr-alt-f1 to root, then reboot only way to restart.

If i use the 2.6.27-1-mepis-smp everything works as it should.

any ideas?

oldhoghead wrote:running antiX-pt1, used smxi to antiX sid sidux using apt, installed newest kernel, dist-upgrade all installed ok, however when I go to boot the new kernel, after typing username and then password, I get login failed, then back to login screen, ctr-alt-f1 to root, then reboot only way to restart.

If i use the 2.6.27-1-mepis-smp everything works as it should.

any ideas?

Check to make sure that the devices used with the sidux kernel are consistent with the ones used by the MEPIS kernel. Also, look at the old dmesg log if it is still out there and see if there are any messages that may provide specific clues on what the problems are.

If you have ati/nvidia drivers, you'll need to re-install them.

Also, check the boot options at menu. The sidux kernel should be at the bottom. You may need to add/type some parameters such as vga=791 etc.

Well after some investigation, think I have narrowed down the problem,
booting from laptop, hit f12 for boot menu (dell 700m)
boot menu comes up, I choose usb hd
if I select antiX pt1 mepis kernel, boots fine using this fstab entry:

Pluggable devices are handled by uDev, they are not in fstab
/dev/sda1 / ext3 defaults,noatime 1 1
/dev/sda2 swap swap sw,pri=1 0 0
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs devmode=0666 0 0
devpts /dev/pts devpts mode=0622 0 0
sysfs /sys sysfs defaults 0 0
/dev/sda3 /home ext3 defaults,noatime 1 2
# Dynamic entries below
/dev/hda2 /mnt/hda2 ntfs-3g noauto,users,gid=users,dmask=002,fmask=113,relatime 0 0
/dev/hda3 /mnt/hda3 ext3 noauto,users,exec,relatime 0 0
/dev/hda4 /mnt/hda4 ext3 noauto,users,exec,relatime 0 0
/dev/hda5 /mnt/hda5 ext3 noauto,users,exec,relatime 0 0
/dev/hda6 /mnt/hda6 ext3 noauto,users,exec,relatime 0 0
/dev/hda7 swap swap sw,pri=1 0 0
/dev/hda8 /mnt/hda8 vfat noauto,users,gid=users,dmask=002,fmask=113,relatime 0 0
/dev/cdrom /media/cdrom udf,iso9660 noauto,users,exec,ro 0 0
/dev/hdc /media/cdrom udf,iso9660 noauto,users,exec,ro 0 0

in reality, my laptop is sda, and the usb hd is sbd however when booting from the usb hd it will show hd 0,0 thus the sda naming scheme.
However when I boot the same way only choosing the sidux kernel, sda3 is being seen by the sidux kernel as /home except that sda3 is Mepis 7.0 on the laptop, not the usb hd.

ls -l /dev/disk/by-uuid on the laptop gives this:

lrwxrwxrwx 1 root root 10 2008-12-31 10:13 0f4d3b7a-387d-416c-b51f-8b8d7ba025df -> ../../sda5
lrwxrwxrwx 1 root root 10 2008-12-31 10:13 3b9ede5d-beb7-4458-9cc4-7ea614dd43ef -> ../../sda3
lrwxrwxrwx 1 root root 10 2008-12-31 10:13 4512-AEBB -> ../../sda8
lrwxrwxrwx 1 root root 10 2008-12-31 10:13 503C4C9E3C4C8148 -> ../../sda2
lrwxrwxrwx 1 root root 10 2008-12-31 10:13 8ad758ab-e856-4689-863f-763c365d999f -> ../../sda7
lrwxrwxrwx 1 root root 10 2008-12-31 10:13 9d85db6f-3229-4c40-a8f2-b46e9953651d -> ../../sdb2
lrwxrwxrwx 1 root root 10 2008-12-31 10:13 c0b10eef-40bd-4ecf-90ac-ac572bda610d -> ../../sdb1
lrwxrwxrwx 1 root root 10 2008-12-31 10:13 cbc9301e-3163-47d2-93b1-4957c1ac8a45 -> ../../sda4
lrwxrwxrwx 1 root root 10 2008-12-31 10:13 e6194247-f23e-447b-b3fa-377310a13618 -> ../../sdb3
lrwxrwxrwx 1 root root 10 2008-12-31 10:13 fe082cf2-70db-404d-aba1-4dc81b417b9d -> ../../sda6

while using the usb hd gives this:
bobbylee@mepis1:~$ ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 10 Dec 31 10:52 0f4d3b7a-387d-416c-b51f-8b8d7ba025df -> ../../hda5
lrwxrwxrwx 1 root root 10 Dec 31 10:52 3b9ede5d-beb7-4458-9cc4-7ea614dd43ef -> ../../hda3
lrwxrwxrwx 1 root root 10 Dec 31 10:52 4512-AEBB -> ../../hda8
lrwxrwxrwx 1 root root 10 Dec 31 10:52 503C4C9E3C4C8148 -> ../../hda2
lrwxrwxrwx 1 root root 10 Dec 31 10:52 8ad758ab-e856-4689-863f-763c365d999f -> ../../hda7
lrwxrwxrwx 1 root root 10 Dec 31 10:52 9d85db6f-3229-4c40-a8f2-b46e9953651d -> ../../sda2
lrwxrwxrwx 1 root root 10 Dec 31 10:52 c0b10eef-40bd-4ecf-90ac-ac572bda610d -> ../../sda1
lrwxrwxrwx 1 root root 10 Dec 31 10:52 cbc9301e-3163-47d2-93b1-4957c1ac8a45 -> ../../hda4
lrwxrwxrwx 1 root root 10 Dec 31 10:52 e6194247-f23e-447b-b3fa-377310a13618 -> ../../sda3
lrwxrwxrwx 1 root root 10 Dec 31 10:52 fe082cf2-70db-404d-aba1-4dc81b417b9d -> ../../hda6

So, I guess the naming convention is handled differently by the mepis kernel and the sidux kernel, I made a backup copy of my fstab, commented out the sda entry's, copied them and change sda to sdb, then rebooted using the sidux kernel and it booted ok, login ok. So, I will have to choose which kernel I want to use and alter fstab to reflect the proper name,
So problem solved sort of!!

cheers
oldhoghead

Change the grub/menu.lst to reflect the uuid's instead of /dev/s?? This will remove any confusion because they don't change. Also make use of the kopt line in the menu.lst. If you put all your boot parameters there everytime you install/upgrade to a different kernel they will be automagically added.

Here is a link of how to do what erie suggets.


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"antix.freeforu ms.org/how-to-set-up-boot-grub-menu-lst-for-automatic-updates-t1244.html"
linktext was:"antix.freeforu ms.org/how-to-set- ... t1244.html"
====================================
" onclick="window.open(this.href);return false

Thank you erie and anti, will check this out, knew there was an eaiser way!! Will update when I get caught up,

cheers
oldhoghead