hey all, i have a couple of systems running redhat 6.2 and now finally got around to installing suse 7.0 on my laptop (dell latitude cpi-a, 366mhz, 256mb, 10Gb). when 2.4.0 came out, i took a redhat 6.2 test system and splashed the kernel on there, compiled, rebooted - and everything was set. modules load on demand, kwintv works, cdburning works, the system seems perfect. so then i decided to give it a shot on my laptop simply because i like having the latest stuff around (even if it's not entirely safe). as i said, the laptop runs suse 7.0 and uses reiserfs on everything but /boot (/dev/hda1). logically, i patched 2.4.0 with reiserfs 3.6.25 and built reiserfs straight into the kernel, since my root partition is reiserfs. furthermore, because of some of my pcmcia cards, and my failure to get my 3c575_cb card to be loaded as 3c59x (vortex) - a change in 2.4.0 -, i disabled pcmcia in the kernel and built pcmcia_cs-3.1.23. and it boots fine. but there are no modules loaded except for the hierarchy required by 3c575_cb - which consists of pcmcia_core, i82365, ds, cb_enabler, and 3c575_cb. but no other modules are loaded or will load automatically. take apm, when i run apm without the module apm in the kernel, i will get "No APM support in kernel." doing a modprobe apm correctly adds it to the kernel and then apm works. or nm256_audio: doing a play somewave.wav results in "unknown device: /dev/dsp" but after the module is added with modprobe, sound works. now, my question is - what happened to kmod? it seems that the redhat dist works fine, but something about suse screws up. since kmod is a kernel thread, i assume it's loaded, so my first guess would be /etc/modules.conf - which suse fills up with 2 billion lines of useless junk. YaST? ACK! do i need one of those "alias char_major_XX apm" lines in modules.conf for the apm.o module to be loaded automatically upon request? who else has been experiencing this with 2.4.0 and what are your workarounds? any clues? martin [greetings from the heart of the sun]# echo madduck@!#:1:s@\@@@.net -- "it is the mark of an educated mind to be able to entertain a thought without accepting it." -- aristoteles
MaD dUCK wrote:
hey all, i have a couple of systems running redhat 6.2 and now finally got around to installing suse 7.0 on my laptop (dell latitude cpi-a, 366mhz, 256mb, 10Gb). when 2.4.0 came out, i took a redhat 6.2 test system and splashed the kernel on there, compiled, rebooted - and everything was set. modules load on demand, kwintv works, cdburning works, the system seems perfect.
so then i decided to give it a shot on my laptop simply because i like having the latest stuff around (even if it's not entirely safe). as i said, the laptop runs suse 7.0 and uses reiserfs on everything but /boot (/dev/hda1). logically, i patched 2.4.0 with reiserfs 3.6.25 and built reiserfs straight into the kernel, since my root partition is reiserfs.
furthermore, because of some of my pcmcia cards, and my failure to get my 3c575_cb card to be loaded as 3c59x (vortex) - a change in 2.4.0 -, i disabled pcmcia in the kernel and built pcmcia_cs-3.1.23.
and it boots fine. but there are no modules loaded except for the hierarchy required by 3c575_cb - which consists of pcmcia_core, i82365, ds, cb_enabler, and 3c575_cb. but no other modules are loaded or will load automatically.
take apm, when i run apm without the module apm in the kernel, i will get "No APM support in kernel." doing a modprobe apm correctly adds it to the kernel and then apm works.
or nm256_audio: doing a play somewave.wav results in "unknown device: /dev/dsp" but after the module is added with modprobe, sound works.
now, my question is - what happened to kmod? it seems that the redhat dist works fine, but something about suse screws up. since kmod is a kernel thread, i assume it's loaded, so my first guess would be /etc/modules.conf - which suse fills up with 2 billion lines of useless junk. YaST?
ACK! do i need one of those "alias char_major_XX apm" lines in modules.conf for the apm.o module to be loaded automatically upon request?
Did you download and compile the modutils for kernel 2.4.0? This may have been installed automatically on RedHat if you used RPM. Do a 'insmod -V' to find out what version of modutils you have. Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
also sprach Chris Reeves (on Mon, 08 Jan 2001 02:19:27PM +0000):
Did you download and compile the modutils for kernel 2.4.0? This may have been installed automatically on RedHat if you used RPM. Do a 'insmod -V' to find out what version of modutils you have.
sure thing. sorry i did not mention this obvious detail: %> modprobe --version modprobe version 2.4.0 [...] martin [greetings from the heart of the sun]# echo madduck@!#:1:s@\@@@.net -- nobody expects the spanish inquisition.
On Monday 08 January 2001 08:22, MaD dUCK wrote:
also sprach Chris Reeves (on Mon, 08 Jan 2001 02:19:27PM +0000):
Did you download and compile the modutils for kernel 2.4.0? This may have been installed automatically on RedHat if you used RPM. Do a 'insmod -V' to find out what version of modutils you have.
sure thing. sorry i did not mention this obvious detail:
%> modprobe --version modprobe version 2.4.0 [...]
I also downloaded, compiled and installed modutils-2.4. I don't understand how modutils is supposed to work, but it looks messed up to me. jerry@JLKreps:~ > /sbin/modprobe -c # Generated by modprobe -c (2.4.0) path[boot]=/lib/modules/boot <--- doesn't exist path[toplevel]=/lib/modules/2.4.0 <--- correct path[toplevel]=/lib/modules/2.4 <--- doesn't exist path[kernel]=/lib/modules/kernel <-- s/b /lib/modules/2.4.0/kernel ??? path[fs]=/lib/modules/fs <-- s/b /lib/modules/2.4.0/fs ??? path[net]=/lib/modules/net <-- s/b /lib/modules/2.4.0/net ??? path[scsi]=/lib/modules/scsi --- same for the rest. ??? path[block]=/lib/modules/block path[cdrom]=/lib/modules/cdrom path[ipv4]=/lib/modules/ipv4 path[ipv6]=/lib/modules/ipv6 path[sound]=/lib/modules/sound path[fc4]=/lib/modules/fc4 path[video]=/lib/modules/video path[misc]=/lib/modules/misc path[pcmcia]=/lib/modules/pcmcia path[atm]=/lib/modules/atm path[usb]=/lib/modules/usb path[ide]=/lib/modules/ide path[ieee1394]=/lib/modules/ieee1394 path[mtd]=/lib/modules/mtd Currently, though, everything is running fine except for the OSS sound software, which won't install. JLK -- Scientific theories, according to Sir Karl Popper, can be "falsified," or proven wrong, by experiment. Unscientific theories -Marxist dialectical history and Freudian psychology were Popper's favorites- are formed in such a way that they cannot be falsified by data.
Jerry Kreps wrote:
sure thing. sorry i did not mention this obvious detail:
%> modprobe --version modprobe version 2.4.0
I also downloaded, compiled and installed modutils-2.4. I don't understand how modutils is supposed to work, but it looks messed up to me. jerry@JLKreps:~ > /sbin/modprobe -c # Generated by modprobe -c (2.4.0) path[boot]=/lib/modules/boot <--- doesn't exist path[toplevel]=/lib/modules/2.4.0 <--- correct path[toplevel]=/lib/modules/2.4 <--- doesn't exist path[kernel]=/lib/modules/kernel <-- s/b /lib/modules/2.4.0/kernel ??? path[fs]=/lib/modules/fs <-- s/b /lib/modules/2.4.0/fs ??? path[net]=/lib/modules/net <-- s/b /lib/modules/2.4.0/net ??? path[scsi]=/lib/modules/scsi --- same for the rest. ???
Don't worry about it, my 2.4.0 modprobe does this as well, as does my 2.2.2-pre6 and 2.3.11 modprobes. I don't understand it either, but I think it's meant to be like that. Presumably in case someone doesn't keep their modules in the 'standard' place. Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
participants (3)
-
Chris Reeves -
Jerry Kreps -
MaD dUCK