Kernel compile probs again

[windoze killa]

Could someone give me an idea as to why I am getting these errors.



Sep 8 20:16:11 linuxbox syslog: syslogd startup succeeded
Sep 8 20:16:11 linuxbox syslog: klogd startup succeeded
Sep 8 20:16:11 linuxbox portmap: portmap startup succeeded
Sep 8 20:16:11 linuxbox nfslock: rpc.statd startup succeeded
Sep 8 20:16:12 linuxbox keytable: Loading keymap: succeeded
Sep 8 20:16:12 linuxbox keytable: Loading system font: succeeded
Sep 8 20:16:12 linuxbox rc: Starting pcmcia: succeeded
Sep 8 20:16:12 linuxbox random: Initializing random number generator: succeeded
Sep 8 20:16:13 linuxbox netfs: Mounting other filesystems: succeeded
Sep 8 20:16:13 linuxbox apmd: apmd startup succeeded
Sep 8 20:15:53 linuxbox rc.sysinit: Mounting proc filesystem: succeeded
Sep 8 20:15:53 linuxbox sysctl: net.ipv4.ip_forward = 0
Sep 8 20:15:53 linuxbox sysctl: net.ipv4.conf.default.rp_filter = 1
Sep 8 20:15:53 linuxbox rc.sysinit: Configuring kernel parameters: succeeded
Sep 8 20:15:53 linuxbox date: Sun Sep 8 20:15:47 EST 2002
Sep 8 20:15:53 linuxbox rc.sysinit: Setting clock (localtime): Sun Sep 8 20:15:47 EST 2002 succeeded
Sep 8 20:16:14 linuxbox identd: identd startup succeeded
Sep 8 20:15:53 linuxbox rc.sysinit: Loading default keymap succeeded
Sep 8 20:15:53 linuxbox rc.sysinit: Activating swap partitions: succeeded
Sep 8 20:15:53 linuxbox rc.sysinit: Setting hostname linuxbox.home: succeeded
Sep 8 20:15:53 linuxbox fsck: /dev/hdb6: clean, 187835/515072 files, 828452/1020127 blocks
Sep 8 20:15:53 linuxbox rc.sysinit: Checking root filesystem succeeded
Sep 8 20:16:14 linuxbox atd: atd startup succeeded
Sep 8 20:15:53 linuxbox rc.sysinit: Remounting root filesystem in read-write mode: succeeded
Sep 8 20:15:53 linuxbox rc.sysinit: Finding module dependencies: succeeded
Sep 8 20:15:53 linuxbox modprobe: modprobe: Can't locate module snd-card-via8233
Sep 8 20:15:53 linuxbox rc.sysinit: Loading sound module (snd-card-via8233): failed
Sep 8 20:15:53 linuxbox fsck: /dev/hdb1: clean, 49/6024 files, 8026/24066 blocks
Sep 8 20:15:53 linuxbox rc.sysinit: Checking filesystems succeeded
Sep 8 20:15:53 linuxbox rc.sysinit: Mounting local filesystems: succeeded
Sep 8 20:15:53 linuxbox rc.sysinit: Enabling local filesystem quotas: succeeded
Sep 8 20:15:54 linuxbox rc.sysinit: Enabling swap space: succeeded
Sep 8 20:15:57 linuxbox kudzu: Updating /etc/fstab succeeded
Sep 8 20:16:08 linuxbox kudzu: succeeded
Sep 8 20:16:08 linuxbox sysctl: net.ipv4.ip_forward = 0
Sep 8 20:16:08 linuxbox sysctl: net.ipv4.conf.default.rp_filter = 1
Sep 8 20:16:08 linuxbox network: Setting network parameters: succeeded
Sep 8 20:16:08 linuxbox ifup: ./ifup: /etc/sysconfig/network-scripts/ifup-ipx: No such file or directory
Sep 8 20:16:08 linuxbox network: Bringing up interface lo: succeeded
Sep 8 20:16:11 linuxbox ifup: ./ifup: /etc/sysconfig/network-scripts/ifup-ipx: No such file or directory
Sep 8 20:16:11 linuxbox network: Bringing up interface eth0: succeeded
Sep 8 20:16:18 linuxbox xinetd: xinetd startup succeeded
Sep 8 20:16:20 linuxbox lpd: lpd startup succeeded
Sep 8 20:16:21 linuxbox sendmail: sendmail startup succeeded
Sep 8 20:16:21 linuxbox gpm: gpm startup succeeded
Sep 8 20:16:22 linuxbox crond: crond startup succeeded
Sep 8 20:16:23 linuxbox xfs: xfs startup succeeded
Sep 8 20:16:24 linuxbox smb: smbd startup succeeded
Sep 8 20:16:24 linuxbox smb: nmbd startup succeeded
Sep 8 20:16:24 linuxbox anacron: anacron startup succeeded
Sep 8 20:16:26 linuxbox linuxconf: Running Linuxconf hooks: succeeded

In particular the sound module and the IPX. I have checked the kernel config file but can't work it out.

Please help with any suggestions.

[Icarus]

You might be able to insert the sound as a module, you did say yes to modules right?

Why you need IPX? The only thing that uses IPX anymore are old Novell networks, maybe that needs to be a module also?

modprobe and see if you can get locate the modules...if not maybe you forgot to compile the modules? Minor step I always overlook ;)

[bwkaz]

snd-card-<anything> is an Alsa module, and Alsa modules don't get compiled with the kernel. You need to get and install the alsa-driver tarball from www.alsa-project.org for that one. Read what ./configure --help tells you, and you can cut the compile time in half (by only building support for the card you use).

The other error (on ifup-ipx) looks like it's trying to find a sub-script that doesn't exist. You didn't touch anything in /etc when you recompiled (well... except your bootloader config file), did you? I don't know where you'd get it from if you deleted it... maybe off one of the distro CDs (actually it has to be there, but I have no idea what it'd be called...)?

[windoze killa]

The alsa modules were (and still are) being loaded under the original kernel so does that mean I have to reinstall them so they can be loaded again.

The IPX problem isn't really a problem other than it is annoying. I haven't changed anything in /etc. I can't remember selecting it when I did xconfig. (can't even remember seeing it)

And I might give alsa another compile and see how it goes.

[mdwatts]

Have a look at

#
# Networking options
#
# CONFIG_IPX is not set *** THIS ONE ***
# CONFIG_ATALK is not set

AND

#
# Network File Systems
#
....
CONFIG_NCP_FS=m
CONFIG_NCPFS_PACKET_SIGNING=y
CONFIG_NCPFS_IOCTL_LOCKING=y
CONFIG_NCPFS_STRONG=y
CONFIG_NCPFS_NFS_NS=y
CONFIG_NCPFS_OS2_NS=y
CONFIG_NCPFS_SMALLDOS=y
CONFIG_NCPFS_NLS=y
CONFIG_NCPFS_EXTRAS=y

[windoze killa]

I will give it a go tonight. The first bit makes sense but I will have to have a think about the second bit. My head hurts at the moment.

[bwkaz]

Each version of the kernel has its own module directory under /lib/modules, and Alsa will only install its modules into one of them at a time.

If you upgrade kernels (say from 2.4.18 to 2.4.19), then your old Alsa modules will (still) be in /lib/modules/2.4.18/misc, but your kernel will be looking in /lib/modules/2.4.19/ and subdirectories for them. You do have to reinstall the Alsa driver, and if you've upgraded from a distribution kernel, you'll have to do it from source. Don't worry, it's not hard. Just make sure you're running the new kernel when you do it, and make sure the source in /usr/src/linux matches the running kernel, and you'll be fine.

[windoze killa]

For some strange reason that makes sense. Not very logical in my mind but it makes sense. Why can't there be a global modules directory that doesn't care what kernel you are running?

[bwkaz]

Because modules load into kernel memory, and need to know where other things in the kernel are at. These other things change every kernel build (if you add code or data in one place, it will move everything else down... ;) ), so they can't be hardcoded. It's also hard to find what the address of these things is at runtime (you could check /boot/System.map, assuming it's accurate, but it'd take a while), and when you can just have separate module directories to not have to do it, it's better. Simplicity...

On a better note, in kernel 2.5, Alsa is integrated into it, so there's no separate compilation anymore. It had better also be in 2.6, but the feature freeze for that isn't until Halloween, let alone the bugs-worked-out part.

[windoze killa]

Another quick question on the module subject. Would it be ok just to copy that required module from one kernel directory to the other? Or is there something done to the module when it is installed when installing alsa?

[bwkaz]

It most likely won't work. When the modules were compiled the first time, they took the addresses of different kernel symbols (functions and pieces of data) from the version of the kernel they were compiled against.

These symbols are almost guaranteed to be in different places now, if they even exist. At best (if you've turned module symbol versioning on, CONFIG_MODVERSIONS), you'll get an "undefined symbol: xxxxxxxx" message. At worst, the modules will just assume the symbols are where they used to be, and will jump off into never-never land. This causes fun things like kernel oopses. ;) Probably not very good.

[windoze killa]

You are right. Copying caused a few problems but a reinstall worked fine. Just now all my mixers crash. Will start a new thread for that one.

[windoze killa]

Originally posted by mdwatts
Have a look at

#
# Networking options
#
# CONFIG_IPX is not set *** THIS ONE ***
# CONFIG_ATALK is not set

AND

#
# Network File Systems
#
....
CONFIG_NCP_FS=m
CONFIG_NCPFS_PACKET_SIGNING=y
CONFIG_NCPFS_IOCTL_LOCKING=y
CONFIG_NCPFS_STRONG=y
CONFIG_NCPFS_NFS_NS=y
CONFIG_NCPFS_OS2_NS=y
CONFIG_NCPFS_SMALLDOS=y
CONFIG_NCPFS_NLS=y
CONFIG_NCPFS_EXTRAS=y


Are you saying that this is what I should have in my ./config file? If so then the first bit is what I had but none of the second bit was.

Does CONFIG_NCP_FS=m have to be loaded as a module or can it be compiled in the kernel?

[slapNUT]

Does CONFIG_NCP_FS=m have to be loaded as a module or can it be compiled in the kernel?
If you put it in the kernel then it's ok to leave it there, no need to rebuild a kernel and a hundred modules over that.

[windoze killa]

I will probably leave it there but I am going to rebuild anyway just to play around a bit more and it only takes 30 minutes. I am slowly getting a grasp of this whole kernel compiling thing.

I saw it as a very daunting proccess before I started because I kept seeing all these linux gurus talking about typing this and typing that in languages I had no idea what they were saying. Then I saw make xconfig mentioned and wow, what a breeze that makes it. Just have to read the help box next to each item and bingo, it works. (well the second time it did, the first time I didn't read the help boxes real well.)