Hello:

I noticed that in the kernel portion of smxi, it says that a debian kernel can be installed using smxi. Yet, I don't see an option to do that.

Did I miss it somewhere?

thanks.

Pedro

smxi -K(uppercase) I think will offer other kernels.

Erie:
thanks for the suggestion. When I tried it, it still defaults to the sidux kernel (which btw, is hanging during boot, so that's why I wanted to try a debian one).

Maybe if I delete smxi.conf and retry smxi -K it will give me the debian option?

Pedro

I think the Debian kernel option in smxi only works if you already have an existing Debian kernel.

Anyhow, if you want to install a Debian kernel, search through synaptic for linux-image. There should be several to choose from.
I just installed the 486 Debian kernel, just to see how it runs, and it installed and booted fine.

This is the one I have

#apt-get update
#apt-get install linux-image-2.6.26-1-486
#update-grub

The update-grub should automatically add the Debian kernel to the grub menu.

(If you use nvidia/ati drivers you will need to re-install them)

Anti:

Thanks for the info. I'll try this tonight when I get home. I'm also dealing with a problem with a sidux kernel that hangs during boot. I'll try to put the exact point where it hangs to see if anyone can figure out what can be done about this.

Pedro

anticapitalista wrote:I think the Debian kernel option in smxi only works if you already have an existing Debian kernel.

Anyhow, if you want to install a Debian kernel, search through synaptic for linux-image. There should be several to choose from.
I just installed the 486 Debian kernel, just to see how it runs, and it installed and booted fine.

This is the one I have

#apt-get update
#apt-get install linux-image-2.6.26-1-486
#update-grub

The update-grub should automatically add the Debian kernel to the grub menu.

(If you use nvidia/ati drivers you will need to re-install them)

I'm pretty sure that you are right about this anti. Before h2 added code into smxi for additional systems, I was still able to hack an old MEPIS installation and get additional kernels, including sidux kernels. As far as getting regular Debian kernels, you are right; they are available from the standard Debian repos. If these are needed to"jump start" the addition of general purpose Debian kernels, I am sure that would work.

One thing to potentially be aware of, depending on which versions you are using, is that some of the older systems use the hda, hdb naming convention for IDE based disks, whereas most of the newer ones use the SCSI based sda, sdb naming convention. I had this trip me up a year or so ago, and got around it by changing my boot menu entries when using kernels that used different conventions.

You are right about the hdxx/sdxx possible hiccup.

If the menu.lst file has beed set up like here, then it should use UUID and boot ok.


========= 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?hilit=grub"
linktext was:"antix.freeforu ms.org/how-to-set- ... hilit=grub"
====================================
" onclick="window.open(this.href);return false menu

anticapitalista wrote:You are right about the hdxx/sdxx possible hiccup.

If the menu.lst file has beed set up like here, then it should use UUID and boot ok.

how-to-set-up-boot-grub-menu-lst-for-automatic-updates-t1244.html?hilit=grub menu

Yeah, I was lukewarm to the idea of UUID at first, but as long as the distro provides the blkid command, what I do is su to root, cd to the /root directory, then run blkid > blkid.txt. Then I can use an editor and toggle between blkid.txt and /boot/grub/menu.lst and make any UUID adjustments that may be required as I revamp what's on my systems. That has proven to be a workable approach - namely, changing the root=/dev/hdax argument in the kernel line to a root=UUID=<some-long-UUID-pasted-from-blkid.txt> and that works great.

Sure helps to know how to use command and edit mode in GRUB - helps find little quirks and get in if the menu entries are still messed up.

If you
#update-grub

once antiX is installed, it should give you the UUID of the partition where grub is installed to so there is no need to use the blkid command.
However, if you have multiple partitions, then things get a bit more complicated and masinick's advice is very good.

However, (there is always a but isn't there) if you resize or add new partitions, then the UUID's change. Now that is a pain in the ....

anticapitalista wrote:If you
#update-grub

once antiX is installed, it should give you the UUID of the partition where grub is installed to so there is no need to use the blkid command.
However, if you have multiple partitions, then things get a bit more complicated and masinick's advice is very good.

However, (there is always a but isn't there) if you resize or add new partitions, then the UUID's change. Now that is a pain in the ....

That is what I was referring to - when multiple UUIDs change. Be CAREFUL if you ever muck with SWAP - you will then have to change not only your boot menu entries, it gets ugly and you have to go in and change /etc/fstab entries. This is also true if you want to mount other distro file systems on your antiX system and you are using UUID device names in place of the traditional names. Ah, as we improve one thing, we complicate another. Such is the life of software!

masinick, I think I have found the solution.

Use one partition (and/or /home) and only install antiX on it __{{emoticon}}__
__{{emoticon}}__

Anti:

thanks for the info on the debian kernel. It seems to have installed fine. I am getting an error about samba, both in this kernel install (with synaptic) and smxi with this kernel and also with a sidux kernel.

The system is loading fine so I'm not sure what the error is about.

Pedro

WOW!! This works great.

Followed your guys tip and then swap hard drives with an pentium-mmx 233mhz laptop.
It shut down during boot--due to heat?
Added acpi=off to grub and it started up.

I get an wireless critical error -3 but i'll worry about that after a fresh install.

where can i find the current temperature? (no-- /pro/acpi//themal_zone/THRM) ?)
Should i use any other grub boot options?

the old junker is fast--compared to the 98 that was on it.

Added support in smxi for antix/mepis users who have manually updated their menu.lst to use # kopt=..... root=LABEL=... or root=UUID=... (using the sticky instructions in this forum for doing that)

If this is detected when smxi started, it will allow Debian kernel install to occur, which will appear in the advanced kernel install options as another kernel install option.

While the default is still to show no kernel pre dist-upgrade, users can now go to post upgrade options, kernel options, advanced kernel options, and install a debian kernel there.

You can also, if you want, set the default system kernel install option in misc tweaks, advanced tweaks, kernel options, to debian-kernel from no-kernel, and then you'll see the latest debian kernel offered when you start smxi, pre du.