Via EPIA C3

brain:proxy · 06-11-2008, 08:55 PM

I did some searches, but was unable to find my exact issue.

This I believe is 586 Processor, 600 MHz.

However, this is the message I recieve upon bootup, Using 12.1 install disk:

This kernel requires the following features not present on this CPU

0:15

Is there a kernel for this CPU or perhaps my issue is elsewhere.

Thanks!

MS3FGX · 06-11-2008, 09:23 PM

You should have better luck with the non-SMP kernel, which you can boot by typing "huge.s" at the "boot:" prompt when the install CD loads up. This kernel should work on any 486 or better processor.

brain:proxy · 06-11-2008, 09:47 PM

Quote:

Originally Posted by MS3FGX

You should have better luck with the non-SMP kernel, which you can boot by typing "huge.s" at the "boot:" prompt when the install CD loads up. This kernel should work on any 486 or better processor.

I am an idiot.

I swear I tried that, but I think I got confused with a VMWare install of slack I did today.

Thanks!

SCerovec · 06-24-2008, 06:09 PM

the wrong questions are those not asked
IMHO

leiyoswoeirvn · 06-28-2008, 02:02 PM

Quote:

Originally Posted by MS3FGX

You should have better luck with the non-SMP kernel, which you can boot by typing "huge.s" at the "boot:" prompt when the install CD loads up. This kernel should work on any 486 or better processor.

i completed setup with "huge.s", but this time during log on it gives the same error...
("This kernel requires the following features not present on the CPU:
0:15
Unable to boot - please use a kernel appropriate for your CPU")
what can i do?

MS3FGX · 06-28-2008, 04:18 PM

Sorry, perhaps I should have specified.

You booted the installer with the proper kernel this time (huge.s), but you also need to tell the installer that is the kernel you want to install into the final system. The installation process should have asked you which kernel you want to install, the default being the SMP kernel which doesn't work on your board.

leiyoswoeirvn · 06-28-2008, 04:42 PM

thank you very much..
but in which part of the installation is asking me ? in this part? "CHOOSE LINUX KERNEL" old_cd.i, lowmem.i, bare.i..
which one should i choose?
do i have to make an extra processing?
besides, is it proper to choose the speakup.s choice in the begining?
thank you again..

SCerovec · 06-30-2008, 01:27 PM

Quote:

Originally Posted by leiyoswoeirvn

thank you very much..
but in which part of the installation is asking me ? in this part? "CHOOSE LINUX KERNEL" old_cd.i, lowmem.i, bare.i..
which one should i choose?

huge.s if it's offered.

Quote:

do i have to make an extra processing?
besides, is it proper to choose the speakup.s choice in the begining?

only if You need a hardware speech synthesizer to work during install.

Quote:

thank you again..

Bruce Hill · 06-30-2008, 06:28 PM

I don't know which one you are ... brain:proxy or leiyoswoeirvn;
Perhaps "the names were changed to protect the innocent."

You can boot with the Slackware CD1 and at the boot prompt type:

Code:

huge.s root=/dev/hda1 rdinit= ro

changing /dev/hda1 to your root partition. Then once back in your
shiny new Slackware system, you can edit /etc/lilo.conf and choose
the proper kernel. The choices are (drum roll)

Code:

root@james:/home/mingdao# ls -l /boot/
<snip>
-rw-r--r--  1 root    root  2055544 2008-05-01 03:02 vmlinuz-generic-2.6.24.5
-rw-r--r--  1 root    root  2167384 2008-05-01 02:19 vmlinuz-generic-smp-2.6.24.5-smp
-rw-r--r--  1 root    root  4205208 2008-05-01 03:15 vmlinuz-huge-2.6.24.5
-rw-r--r--  1 root    root  4369880 2008-05-01 02:42 vmlinuz-huge-smp-2.6.24.5-smp

so you can change this section to use the huge (non-smp) kernel like this:

Code:

# Linux bootable partition config begins
image = /boot/vmlinuz-huge-2.6.24.5
root = /dev/hda1
label = Slack-12.1
read-only # Partitions should be mounted read-only for checking

Change all the appropriate fields from my example to your machine's proper
entries, of course.

Afterwards, run "lilo" as root to write the changes to your bootloader.

brain:proxy · 07-01-2008, 12:57 AM

Quote:

Originally Posted by leiyoswoeirvn

thank you very much..
but in which part of the installation is asking me ? in this part? "CHOOSE LINUX KERNEL" old_cd.i, lowmem.i, bare.i..
which one should i choose?
do i have to make an extra processing?
besides, is it proper to choose the speakup.s choice in the begining?
thank you again..

What I did was this:

During the install, when is asks you what kind of prompts you want, "complete", "menu" etc., I chose "menu", so it prompted me what packages to install.

In the very first group of packages, you'll see the listed the various kernels, I unselected all but the "huge" - this only leave the huge kernel in the lilo menu after the install.

You could also select the huge.s kernel from the lilo menu if its installed, then follow Bruce's instructions.

Let us know if you still need help =)

leiyoswoeirvn · 07-01-2008, 10:44 PM

Quote:

Originally Posted by Bruce Hill

I don't know which one you are ... brain

roxy or leiyoswoeirvn;
Perhaps "the names were changed to protect the innocent."

You can boot with the Slackware CD1 and at the boot prompt type:

Code:

huge.s root=/dev/hda1 rdinit= ro

changing /dev/hda1 to your root partition. Then once back in your
shiny new Slackware system, you can edit /etc/lilo.conf and choose
the proper kernel. The choices are (drum roll)

Code:

root@james:/home/mingdao# ls -l /boot/
<snip>
-rw-r--r--  1 root    root  2055544 2008-05-01 03:02 vmlinuz-generic-2.6.24.5
-rw-r--r--  1 root    root  2167384 2008-05-01 02:19 vmlinuz-generic-smp-2.6.24.5-smp
-rw-r--r--  1 root    root  4205208 2008-05-01 03:15 vmlinuz-huge-2.6.24.5
-rw-r--r--  1 root    root  4369880 2008-05-01 02:42 vmlinuz-huge-smp-2.6.24.5-smp

so you can change this section to use the huge (non-smp) kernel like this:

Code:

# Linux bootable partition config begins
image = /boot/vmlinuz-huge-2.6.24.5
root = /dev/hda1
label = Slack-12.1
read-only # Partitions should be mounted read-only for checking

Change all the appropriate fields from my example to your machine's proper
entries, of course.

Afterwards, run "lilo" as root to write the changes to your bootloader.

thank you for all.. but my problem is going on..

my /etc/lilo.conf

Code:

append=" vt.default_utf8=1"
boot = /dev/hda
bitmap = /boot/slack.bmp
bmp-colors = 255,0,255,0,255,0
bmp-table = 60,6,1,16
prompt
timeout = 1200
change-rules
reset
vga = 773
image = /boot/vmlinuz-huge-2.6.24.5 (i looked at ls -l /boot/)
root = /dev/hda2
label = Slack-12.1
read-only

Bruce Hill · 07-01-2008, 11:28 PM

leiyoswoeirvn,

Please boot with the Slackware CD1 as I previously suggested, and then change
/etc/lilo.conf to use "/boot/vmlinuz-generic-2.6.24.5". You will need to make
an initial RAM disk image to use this kernel. To help ease your pain in setting
that up, download Alien Bob's mkinitrd_command_generator.sh and run it for help
in which options to choose for your mkinitrd. So add this line to /etc/lilo.conf:

Code:

image = /boot/vmlinuz-generic-2.6.24.5  <--- change huge to generic
root = /dev/hda2
initrd = /boot/initrd.gz  <--- new line
root = /dev/hda2
label = Slack-12.1
read-only

After you change /etc/lilo.conf, issue "sh mkinitrd_command_generator.sh" and
it will give you suggestions for your initrd image. It will output something like:

Code:

root@silas:/home/mingdao# sh mkinitrd_command_generator.sh
#
# mkinitrd_command_generator.sh revision 1.37
#
# This script will now make a recommendation about the command to use
# in case you require an initrd image to boot a kernel that does not
# have support for your storage or root filesystem built in
# (such as the Slackware 'generic' kernels').
# A suitable 'mkinitrd' command will be:

mkinitrd -c -k 2.6.24.5-smp -f jfs -r /dev/cryptvg/root -m pata_acpi:ata_generic:usbhid:ehci-hcd:ohci-hcd:jfs -C /dev/md/2 -L -o /boot/initrd.gz

Copy and paste that line into your terminal, then press Enter. You MUST
issue "lilo" after doing all the above steps, to write this to your bootloader.

Bruce Hill · 07-02-2008, 12:17 AM

I looked in our HCL ... do any of these entries look like your board there?

It might be worth checking online, especially Google, to find more information.

Maybe even building a custom kernel for that board might be necessary.

Wekker · 07-12-2008, 11:36 AM

FYI, some interesting EPIA links
EPIA Howto radagast.bglug.ca/epia/epia_howto/

freepia livecd open source applications optimized for the VIA EPIA. Freepia turns your epia in a low noise media box.
freepia.shaibn.com

?xunil · 08-19-2008, 11:20 PM

i ran into the exact same problem... the above process worked for me (via c3 chip on a pcchips mobo).

thanks,
j