[SOLVED] latest slackware version supporting old i386?

NightHorse · 06-22-2009, 03:11 AM

Quote:

Ordering Information
Product Name Description
VSX-6154-V2 Vortex86SX PC/104 CPU Module with 128MB DDR2
VSX-6154-V2-PLUS Vortex86SX PC/104+ CPU Module with 128MB DDR2

Seems like am gonna have to ask my manager which one they ordered. I will see what they say. Sorry I didn't notice that part earlier.

NightHorse · 06-23-2009, 05:31 AM

Hello again. I installed slackware 12.0 and got my driver compiled but i had a problem with getting it work. I have started a separate thread but I thought I would leave the link to keep you updated.

lavoie.alexandre · 06-23-2009, 06:45 PM

Hi guys,

First, i'm glad to know other people using PC/104 technology! I'm using the VTX104 board from Tri-M Systems, same processor, same problem with Slackware 12.2. I'll probably compile the 12.2 kernel with different processor settings and try that in some days.

I was using for 4 years Slackware on many PC/104's with Transmetta Crusoe processor, TMZ104, never had problems!

Alex.

NightHorse · 06-24-2009, 12:39 AM

Hey lavoie.alexandre,

You have been using slackware with pc/104 for too long. !! Do u know how can I make it more optimized??? Cause life is so slow on it. specially on loading. !! I think I installed many not needed modules. I stripped all I know and don't need. Left all that I don't know. lol.. Any tips would be appreciated.

NightHorse · 06-24-2009, 12:40 AM

btw my board is pc/104 not pc/104-plus. My manager confirmed it for me.

onebuck · 06-24-2009, 08:15 AM

Hi,

Quote:

Originally Posted by NightHorse

btw my board is pc/104 not pc/104-plus. My manager confirmed it for me.

Now that you which board that you are using then the kernel to use or configure will be easier. Boot with the default kernel and use the parameters to pass to the kernel that may be need to get the install. 'ipic', 'noipic' or even 'noipci' may be some of the parameters you may try. Read the text files for more information;
RELEASE_NOTES
CHANGES_AND_HINTS.TXT
UPGRADE.TXT

Note that the above is on your install cd/dvd.

'Slackware® Essentials' and 'Slackware® Basics' are two good references.

'Linux Documentation Project' is another good source for reference.
'Rute Tutorial & Exposition' is another.

A good admin guide to reference is 'Linux Newbie Admin Guide'.

These links and others can be found at 'Slackware-Links'. More than just Slackware® links!

lavoie.alexandre · 06-25-2009, 12:13 AM

Hi NightHorse,

Yes I'm still having slow booting too. I've made some change some years ago and normally I use a Slackware of 256-300MB including Java JDK, Web server and every c/c++ libs. I'll try to post informations about packages I use normally etc.

For the kernel, I saw a PDF http://www.compactpc.com.tw/drivers/...inux_HowTo.pdf and it is telling us to compile the kernel not for Pentium-Pro but for 486 and add the Math Emulation. I don't have time for now but I'll still try this maybe tomorrow.

Alex.

H_TeXMeX_H · 06-25-2009, 02:18 AM

Slow booting, at what point does it hang most ?

NightHorse · 06-25-2009, 02:02 PM

Thanks onebuck for the links. I have going throw them. I am happy getting a distro like slackware. It makes me understand many different stuff. Unfortunately I am having trouble with my wifi module. LoL.. I am reinstalling slackware stripping more apps to get it lighter cause it's so slow on that machine. Especially on loading.

Yeah TeXMeX, it's so slow. I will write the lines where it's hang up the most on my loading but may be that would change after the reinstall but let me post anyway and I will update if i noticed a difference:

1.

Quote:

Loading Linux

Just after Lilo boots up and it start booting the kernel, it takes so long loading till it shows BIOS CHECK SUCCESS.

2.

Quote:

Triggering udev events: /sbin/udevtrigger

It takes so long hanging at this point and I get an error after that. *I forgot to copy the error, sorry for that*

3.

Quote:

rc6040: RDC r6040 net driver
rc6040: RDC r6040 net driver

Well, that's my ethernet driver module. I installed the module from source and that message is showed twice like up there. Have no clue why. !!

4.

Quote:

Updating shared library links

Again it hangs for quiet a bit here.

5.

Quote:

Starting pcmcia

I haven't installed pcmcia on my new installation so that should not be a problem. right??

6.

Quote:

Triggering udev events: /sbin/udevtrigger

Yes same message again and still takes too long here with something like retry fails. :s

7.

Quote:

Starting HAL daemon

It hangs here for quiet a bit too but I haven't installed HAL. I have no clue what is it there for anyway. That should not get me in troubles. right??

The output of dmesg on my machine at earlier point is in here. Was having a problem with my ethernet so I posted it there.

Also if someone could help me with my wifi module problem, that would be much appreciated. It's posted here

btw lavoie.alexandre, There is a configuration file for x-linux as well. you can use them to clone the x-linux configuration and tweak what u want. It's here.

Also my last question. I was trying to compile the kernel on my laptop. Core2 Duo processor. I didn't find Math emulation, neither i486 architecture. It doesn't show cause my machine running ubuntu 64 bit, right???

Thanks everyone and sorry for my long post. :$

H_TeXMeX_H · 06-25-2009, 03:11 PM

Ok, so here are some possible fixes:

1) Edit '/etc/lilo.conf', and add the word 'compact' in there somewhere, uncommented. Then as root run 'lilo' to update the config.

3) Not sure why that would happen, hopefully it isn't trying to load it twice.

4) First make a backup of '/etc/rc.d/rc.M', then edit it. Change a line in there, basically add an '&' as follows after /sbin/ldconfig:

Code:

# Update all the shared library links:
if [ -x /sbin/ldconfig ]; then
  echo "Updating shared library links:  /sbin/ldconfig &"
  /sbin/ldconfig &
fi

5) If you don't need pcmcia make '/etc/rc.d/rc.pcmcia' unexecutable. 'chmod a-x /etc/rc.d/rc.pcmcia'

2, 6) Make a backup of '/etc/rc.d/rc.udev' and edit it. You'll see a line like this:

Code:

	echo "Triggering udev events:  /sbin/udevtrigger $OPT"	
	# Call udevtrigger and udevsettle to do the device configuration:
	/sbin/udevtrigger $OPT && /sbin/udevsettle --timeout=120

In many cases you can safely lower the timeout value so it times out faster and you boot faster. It's not good to put it too low as it may cause problems.

7) If you don't want hal, then just make '/etc/rc.d/rc.hald' unexecutable. 'chmod a-x /etc/rc.d/rc.hald'. HAL is not necessary, but it can be useful for a few things.

Quote:

Also my last question. I was trying to compile the kernel on my laptop. Core2 Duo processor. I didn't find Math emulation, neither i486 architecture. It doesn't show cause my machine running ubuntu 64 bit, right???

Yeah, there's no way x86_64 kernel could have those options.

onebuck · 06-25-2009, 06:36 PM

Hi,

Quote:

Originally Posted by NightHorse

<snip>
Also my last question. I was trying to compile the kernel on my laptop. Core2 Duo processor. I didn't find Math emulation, neither i486 architecture. It doesn't show cause my machine running ubuntu 64 bit, right???

Thanks everyone and sorry for my long post. :$

I think somewhere in our communications I suggested that you look into using VirtualBox. If you use the 'VM' and install a Slackware version then you could do your compiles or builds on that with your *buntu laptop. You would then copy/move the build to your pc104. So I don't have to explain 'build' you can take a look at a old but useful thread on how to use the 'build' technique.

If you choose to use this technique then I feel that things will be a lot easier for you.

As for the modules issue that you state that you are experiencing. The modules in the '/lib/modules/version_modules' are static and for the availability to load when the hardware is detected so just using space until installed. No way that you would have all the hardware that have modules.

One other thought, I think you stated that you are using the 'huge' kernel. That's a installer kernel with everything but the kitchen sink. As the text files that were suggested that you read. You will find that the 'generic' kernels are recommended.

'H' gave you some useful information on speeding up your boot. You should also look at the 'udev' rules. You can disable 'HAL' and the 'pcmcia' with no harm since you state that you won't use them.

'HAL' and 'pcmcia' are default. If you did a full install then at the last user input you had options to turn on/off the listed services.

You should also turn of any other services that you won't be using, look at '/etc/services'.

NightHorse · 07-14-2009, 04:50 AM

Hi and sorry for the long absense. I have done everything that H_TeXMeX_H said and things got better except for tip #4 i found it already done. Boot still slow tho but i guess that's the machine...

onebuck: I have been using VBox and turned to chroot now as I find out I could get full x32 chroot by using "linux32 chroot /path/to/chroot" and i could get the x32 options on compiling kernel like i386, i486, ....

I have to use the huge kernel cause slackware stating at boot that if the processor is less than i686 then i have to use the huge kernel. Also tried the generic but kernel panic. I think the huge kernel is compiled with Math Emulation on.

Now am closing all daemons i am not using. I still couldn't solve the wifi problem tho and i have been compiling so many kernels during last couple of week. it might be the driver is not mature yet or so...

Thanks everyone who helped me and sorry again for the late post.

P.S. onebuck: I keep reading the documents you pointed me to and I learn more and more from them. Thanks again.

onebuck · 07-14-2009, 08:32 AM

Hi,

I suspect that you did not create a 'initrd' for the generic kernel;

Quote:

excerpt from 'CHANGES_AND_HINTS.TXT';

As stated earlier, it is recommended that you use one of the generic kernels
rather than the huge kernels; the huge kernels are primarily intended as
"installer" and "emergency" kernels in case you forget to make an initrd.
For most systems, you should use the generic SMP kernel if it will run,
even if your system is not SMP-capable. Some newer hardware needs the
local APIC enabled in the SMP kernel, and theoretically there should not be
a performance penalty with using the SMP-capable kernel on a uniprocessor
machine, as the SMP kernel tests for this and makes necessary adjustments.
Furthermore, the kernel sources shipped with Slackware are configured for
SMP usage, so you won't have to modify those to build external modules
(such as NVidia or ATI proprietary drivers) if you use the SMP kernel.

If you decide to use one of the non-SMP kernels, you will need to follow the
instructions in /extra/linux-2.6.24.5-nosmp-sdk/README.TXT to modify your
kernel sources for non-SMP usage. Note that this only applies if you are
using the Slackware-provided non-SMP kernel - if you build a custom kernel,
the symlinks at /lib/modules/$(uname -r)/{build,source} will point to the
correct kernel source so long as you don't (re)move it.

If you decide to use one of the huge kernels anyway, you will encounter
errors like this:
kobject_add failed for uhci_hcd with -EEXIST, don't try to register
These occur because the respective drivers are compiled statically into the
huge kernels but udev tries to load them anyway. These errors should be safe
to ignore, but if you really don't want them to appear, you can blacklist the
modules that try to load in /etc/modprobe.d/blacklist. However, make sure you
remove them from the blacklist if you ever decide to use the (recommended)
generic kernels.

Both generic & huge kernels are compiled for x86;

Quote:

~# cat /boot/config-generic-2.6.27.7 |grep -i 86
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_VSMP is not set
# CONFIG_X86_RDC321X is not set
# CONFIG_M386 is not set
CONFIG_M486=y
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
CONFIG_X86_GENERIC=y
CONFIG_X86_CPU=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=7

~# cat /boot/config-huge-2.6.27.7 |grep -i 86
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_VSMP is not set
# CONFIG_X86_RDC321X is not set
# CONFIG_M386 is not set
CONFIG_M486=y
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
CONFIG_X86_GENERIC=y

The above is part of the x86 settings for the generic & huge kernels.

If you don't want the 'initrd' you could just boot into the 'generic' with the install cd/dvd. Then just compile in your filesystem. At this time you could remove anything else that you find is not necessary.

NightHorse · 07-22-2009, 07:42 AM

Here is a link for the boot message that state that any hardware older than pentium-pro have to use huge.s kernel.

I have checked the configuration of both huge kernel and hugesmp one. Math_Emulation is turned on in the huge kernel and not set on the hugesmp one.

huge configuration:

Code:

#
# Firmware Drivers
#
CONFIG_EDD=m
CONFIG_DELL_RBU=m
CONFIG_DCDBAS=m
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_RESOURCES_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_HIGHPTE=y
CONFIG_MATH_EMULATION=y
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
CONFIG_COMPAT_VDSO=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

in hugesmp
# CONFIG_MATH_EMULATION is not set

My CPU doesn't have FPU so Math Emulation has to be turned on in any kernel. But even with that the 12.2 huge kernel doesn't boot but it gives a message say "Error parsing ELF"

I apologize for my late replies but my connection at home has been down for more than a week now.

onebuck · 07-22-2009, 08:27 AM

Hi,

That message is for the install kernel that must be used for the installation of the system.