smxi debian kernel option for antix

h2 · posted: 2008-07-28 19:19

To help with debugging, I added an option to let antix testers install debian kernels, but only if they start smxi with -T (testing) option.

-T enables a variety of behaviors in smxi, all variable depending on what I need to test at the time, but the core functionality doesn't change usually.

So for antix testers who want to see if they can get the straight debian kernel working: smxi -T
then, in advanced kernel install option, you'll see the option to install debian kernels. Don't try this on a production box, use virtualbox or vmware to test the thing, for me the debian kernel destroyed the system when I tested it, not sure why. Maybe it's fixed now?

eriefisher · posted: 2008-07-28 19:25

I have been upgrading to sidux kernels. Now at 2.6.25-12.slh.3-sidux-686. I also installed the 2.6.26 sidux kernel but it has some issues with acpi( have not looked into it yet) but overall they work real well.

anticapitalista · posted: 2008-07-28 19:28

I'll give the Debian kernels a test, though I have never managed to get one to work in antiX (nor Mepis). sidux kernels have always worked.
Any idea why that may be?

Do debian kernels work in sidux?

h2 · posted: 2008-07-28 20:10

I just got it working, the solution was: make kernel boot to UUID of root, and set /etc/fstab to use UIUD for /dev/sda1, /dev/sda2, and /dev/sda3 (root, home, and swap)

But there appears to be a mepis tool that automatically adds junk to /etc/fstab each time you boot. I'd give some serious long term thought to dumping these tools if you want the system to actually work with debian straight long term, but

h2 · posted: 2008-07-28 20:17

Code: Select all

 infobash -v
Host/Kernel/OS "antix-test" running Linux 2.6.25-2-686 i686 [ Unknown distro o_O ]
CPU Info        AMD Athlon 64 X2 Dual Core 3800+ clocked at [ 2010.287 MHz ]
Videocard       InnoTek Systemberatung GmbH VirtualBox Graphics Adapter  X.Org 1.4.0.90  [ 1024x768@71.0hz ]
Processes 63 | Uptime 2min | Memory 33.7/250.5MB | HDD Size 5GB (33%used) | Client Shell | Infobash v3.01

and after the edits:
/etc/fstab:

Code: Select all

 cat /etc/fstab
# Pluggable devices are handled by uDev, they are not in fstab
UUID=e16357e4-6122-46df-9098-d68055385d08 / ext3 defaults,noatime 1 1
UUID=1bab1f48-59c9-4853-8b36-2c7af28ee487 swap swap sw,pri=1 0 0
proc /proc proc defaults 0 0
procbususb /proc/bus/usb usbfs devmode=0666 0 0
devpts /dev/pts devpts mode=0622 0 0
sysfs /sys sysfs defaults 0 0
UUID=4c15128f-fc4a-4aa5-b3da-16c9b58b28b4 /home ext3 defaults,noatime 1 2
# Dynamic entries below
/dev/ram0 /mnt/ram0 auto noauto,users,exec 0 0
/dev/ram1 /mnt/ram1 auto noauto,users,exec 0 0
/dev/ram2 /mnt/ram2 auto noauto,users,exec 0 0
/dev/ram3 /mnt/ram3 auto noauto,users,exec 0 0
/dev/ram4 /mnt/ram4 auto noauto,users,exec 0 0
/dev/ram5 /mnt/ram5 auto noauto,users,exec 0 0
/dev/ram6 /mnt/ram6 auto noauto,users,exec 0 0
/dev/ram7 /mnt/ram7 auto noauto,users,exec 0 0
/dev/ram8 /mnt/ram8 auto noauto,users,exec 0 0
/dev/ram9 /mnt/ram9 auto noauto,users,exec 0 0
/dev/ram10 /mnt/ram10 auto noauto,users,exec 0 0
/dev/ram11 /mnt/ram11 auto noauto,users,exec 0 0
/dev/ram12 /mnt/ram12 auto noauto,users,exec 0 0
/dev/ram13 /mnt/ram13 auto noauto,users,exec 0 0
/dev/ram14 /mnt/ram14 auto noauto,users,exec 0 0
/dev/ram15 /mnt/ram15 auto noauto,users,exec 0 0
/dev/hda1 /mnt/hda1 ext3 noauto,users,exec 0 0
/dev/hda2 swap swap sw,pri=1 0 0
/dev/hda3 /mnt/hda3 ext3 noauto,users,exec 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

don't ask my what the the /dev/ram crud is. But at least after a reboot, there aren't any conflicting paths.

and /boot/grub/menu.lst

Code: Select all

timeout 15
color cyan/blue white/blue
foreground ffffff
background 0639a1

gfxmenu /boot/grub/message

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
##      kopt_2_6_8=root=/dev/hdc1 ro
##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=e16357e4-6122-46df-9098-d68055385d08  ro vga=791 nosplash

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=

## should update-grub lock old automagic boot options
## e.g. lockold=false
##      lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(single-user) single
# altoptions=(single-user mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title        Debian GNU/Linux, kernel 2.6.22-1-mepis-smp Previous
root        (hd0,0)
kernel        /boot/vmlinuz.old root=/dev/sda1 ro vga=791 nosplash 
initrd        /boot/initrd.img.old

title        Debian GNU/Linux, kernel 2.6.22-1-mepis-smp Previous (single-user mode)
root        (hd0,0)
kernel        /boot/vmlinuz.old root=/dev/sda1 ro vga=791 nosplash single
initrd        /boot/initrd.img.old

title        Debian GNU/Linux, kernel 2.6.25-11.slh.1-sidux-686
root        (hd0,0)
kernel        /boot/vmlinuz-2.6.25-11.slh.1-sidux-686 root=/dev/sda1 ro vga=791 nosplash 
initrd        /boot/initrd.img-2.6.25-11.slh.1-sidux-686

title        Debian GNU/Linux, kernel 2.6.25-11.slh.1-sidux-686 (single-user mode)
root        (hd0,0)
kernel        /boot/vmlinuz-2.6.25-11.slh.1-sidux-686 root=/dev/sda1 ro vga=791 nosplash single
initrd        /boot/initrd.img-2.6.25-11.slh.1-sidux-686

title        Debian GNU/Linux, kernel 2.6.25-7.slh.2-sidux-686
root        (hd0,0)
kernel        /boot/vmlinuz-2.6.25-7.slh.2-sidux-686 root=/dev/sda1 ro vga=791 nosplash 
initrd        /boot/initrd.img-2.6.25-7.slh.2-sidux-686

title        Debian GNU/Linux, kernel 2.6.25-7.slh.2-sidux-686 (single-user mode)
root        (hd0,0)
kernel        /boot/vmlinuz-2.6.25-7.slh.2-sidux-686 root=/dev/sda1 ro vga=791 nosplash single
initrd        /boot/initrd.img-2.6.25-7.slh.2-sidux-686

title        Debian GNU/Linux, kernel 2.6.25-2-686
root        (hd0,0)
kernel        /boot/vmlinuz-2.6.25-2-686 root=UUID=e16357e4-6122-46df-9098-d68055385d08 ro vga=791 nosplash 
initrd        /boot/initrd.img-2.6.25-2-686

title        Debian GNU/Linux, kernel 2.6.25-2-686 (single-user mode)
root        (hd0,0)
kernel        /boot/vmlinuz-2.6.25-2-686 root=/dev/sda1 ro vga=791 nosplash single
initrd        /boot/initrd.img-2.6.25-2-686

title        Debian GNU/Linux, kernel 2.6.22-1-mepis-smp
root        (hd0,0)
kernel        /boot/vmlinuz-2.6.22-1-mepis-smp root=/dev/sda1 ro vga=791 nosplash 
initrd        /boot/initrd.img-2.6.22-1-mepis-smp

title        Debian GNU/Linux, kernel 2.6.22-1-mepis-smp (single-user mode)
root        (hd0,0)
kernel        /boot/vmlinuz-2.6.22-1-mepis-smp root=/dev/sda1 ro vga=791 nosplash single
initrd        /boot/initrd.img-2.6.22-1-mepis-smp

title        Debian GNU/Linux, kernel memtest86+
root        (hd0,0)
kernel        /boot/memtest86+.bin

### END DEBIAN AUTOMAGIC KERNELS LIST

h2 · posted: 2008-07-28 20:20

As I noted, at some points systems have to handle uuid, they can't ignore it long term.

Yes, sidux handles debian kernels fine, sidux is largely fully debian compatible, that was the hint for me, plus the fact that the first debian install hung at finding root, a sure sign it needed uuid to find it, or label.

Then it was just a matter of trial and error, as soon as the full system is uuid set, there are no further issues, the kernel boots fine.

Also, because slh is using a certain kernel config flag that breaks fglrx drivers, the only current way users can install fglrx drives is to use debian kernels, so that makes the issue slightly relevant, and not just theoretical.

But it's not hard to get it all working, just change /etc/fstab, change to use UUID in #kopt.... root=UUID=.... then install the debian kernel using -T in smxi, and it should go fine.

h2 · posted: 2008-07-28 20:54

Hint, to avoid clutter, fully comment out this line:
# altoptions=(single-user mode) single
like so:
## altoptions=(single-user mode) single

anticapitalista · posted: 2008-07-28 22:43

Thanks for the help h2.

I should be in bed really, but I've been messing around with testing.

In virtualbox, successfully upgraded antiX-M7.01 (libnss3-1d problems to begin with, but finally fixed it).
Installed latest debian kernel in testing, made the changes beforehand to fstab, grub.menu and for the first time ever I boot into a debian kernel on antiX!

I'll look at this more tomorrow, but just to say that it is possible to install a debian kernel on antiX. I just need to make it more automatic.

Thanks again h2.

h2 · posted: 2008-07-28 22:49

It m ight work to simply change /dev/hdax to /dev/sdax in /etc/fstab, try it and see, that's easy to script.

sed -i 's|^/dev/hd|/dev/sd|' /etc/fstab

but that might break cdrom hard to say

masinick · posted: 2008-07-29 15:25

Nice work, h2! I have been working with smxi, not only in sidux, but also in antiX and SimplyMEPIS 7.0. Of course, the sidux version does exactly what I want. In the antiX version, the only thing I would like to see different is that I would like the GRUB menu for antiX kernels to update the first entries in the configuration instead of appending them at the end, but that is minor - I can always edit it manually myself. It just makes for extra steps when I update.

The SimplyMEPIS implementation of smxi works well enough to give me sidux kernels and allows me to run smxi updates, with the same restrictions as above. By default, I lose some of the SimplyMEPIS stuff, though on the MEPIS Lovers forum I did see a post about enabling and disabling MEPIS entries in the apt sources, then tweaking with apt-get -f install back and forth a few times to get a merged capability of SimplyMEPIS with Sid applications. I may be able to apply that trick to SimplyMEPIS, then use smxi to maintain it.

In any case, great job with what you are doing, I really appreciate it. I now have a couple of sidux-smxi-ified systems, thanks to your efforts!

anticapitalista · posted: 2008-07-29 17:12

h2 wrote:It m ight work to simply change /dev/hdax to /dev/sdax in /etc/fstab, try it and see, that's easy to script.

sed -i 's|^/dev/hd|/dev/sd|' /etc/fstab

but that might break cdrom hard to say

If menu.lst kernel option has /dev/hda1 , Debian kernel boots.
If menu.lst has UUID=... Debian kernel boots.
If menu has /dev/sda1, Debian kernel doesn't boot.

h2 · posted: 2008-07-29 18:13

masinick, the grub stuff is the result of mepis using a non debian standard grub updating method, that's out of my hands, long term hopefully mepis will abandon that idea and use update-grub compatible syntax.

I'm not going to try to work around what is essentially in my opinion an error, and not debian compatible, that's far too much work, so that's something mepis/antix users will have to resolve, probably by setting up a simple how to update /boot/grub/menu.lst page, the edits aren't that hard, and should be done after the first new kernel install.

Once you sync the stuff, it all works fine, and all future kernel updates will work as expected for sidux and debian kernels.

In general, if systems are going to use debian as their source, it's a fairly good idea to not drift very far from core debian methods, it's just harder to maintain longterm.

h2 · posted: 2008-07-29 18:15

anticapitalista, menu.lst and /etc/fstab must match I believe, try making menu.lst and fstab both use /dev/sdx and see how that works. The debian update-grub seems to create /dev/sdx by default, though I'm not certain about that.

anticapitalista · posted: 2008-07-29 18:38

h2, fstab points to sda, but debian kernel boots with hda in menu.lst

antiX, since M7.01 (I think, certainly M7.2) has been using a sidux grubgfx.

And, you are right about not finding a workaround s it is an antiX/Mepis problem. A note to edit menu.lst after first install is a good idea, until it gets fixed.

eriefisher · posted: 2008-07-29 20:42

Can I just manually change everything from /dev/xxx to UID......? The update-grub works fine. I just commented out all the entries at the top. They don't work anyway so I will eventually just delete them.