Re: Kernel Panic - Unix socket communication in kernel module
On Monday, July 29, 2013 3:31:49 am varanasi sainath wrote: Hello, I am writing a kernel module in which I am trying to connect to a UNIX socket (UNIX domain sockets use the file system as their address name space). Kernel module (loadable) acts as a client and User mode program acts as server, I have loaded the module using kldload and communication between user and kernel module works fine, when I try to load the kernel module from loader.conf - auto load the kernel module at boot up leads to kernel panic as the file system is not ready and kern_connect fails. How to notify kernel module that File system is ready? (any specific event flags) Is there any specific location for Unix domain socket files? (currently created it under /root/soc/socket ) Using MODULE_DEPEND Can I make the module dependent of file system? You can register a hook for the 'mountroot' EVENTHANDLER event which will fire after / is mounted. (You could compare rootvnode against NULL during module startup to determine if you should defer your work to the EVENTHANDLER vs doing it right away.) If you need to wait for all local filesystems to be mounted, then you will need to have some userland utility poke your module via a sysctl/ioctl/etc. after the filesystems are mounted (you could use a custom rc.d script for this). -- John Baldwin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Kernel Panic - Unix socket communication in kernel module
Hello, I am writing a kernel module in which I am trying to connect to a UNIX socket (UNIX domain sockets use the file system as their address name space). Kernel module (loadable) acts as a client and User mode program acts as server, I have loaded the module using kldload and communication between user and kernel module works fine, when I try to load the kernel module from loader.conf - auto load the kernel module at boot up leads to kernel panic as the file system is not ready and kern_connect fails. How to notify kernel module that File system is ready? (any specific event flags) Is there any specific location for Unix domain socket files? (currently created it under /root/soc/socket ) Using MODULE_DEPEND Can I make the module dependent of file system? Thanks. * * ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Kernel Panic - Unix socket communication in kernel module
On 29/07/2013 08:31, varanasi sainath wrote: Hello, I am writing a kernel module in which I am trying to connect to a UNIX socket (UNIX domain sockets use the file system as their address name space). Kernel module (loadable) acts as a client and User mode program acts as server, I have loaded the module using kldload and communication between user and kernel module works fine, when I try to load the kernel module from loader.conf - auto load the kernel module at boot up leads to kernel panic as the file system is not ready and kern_connect fails. How to notify kernel module that File system is ready? (any specific event flags) Is there any specific location for Unix domain socket files? (currently created it under /root/soc/socket ) Using MODULE_DEPEND Can I make the module dependent of file system? I shall resist the obvious why question. I'm assuming you're talking about a fifo here (aka named pipe, and occasionally called UNIX socket) rather than the BSD network socket interface. IIRC since 4.3BSD fifos have been implemented using sockets internally anyway. Where to put it? I tend to go for /tmp but somewhere in /var might make more sense for something that's always supposed to be there. I don't know how to tell when the FS is ready but it will be when init runs, so you might like to try the sysctl variables. Knowing that init is always PID 1, the value of kern.lastpid should give a hint. There may be an official way of doing this properly. You could always load the module from rc.local instead. Regards, Frank. P.S. You do know that an fd only relates to the kernel thread it's currently running in? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: linux program with kernel module
On Thu, Mar 14, 2013 at 10:42:41PM +0100, Ralf Mardorf typed: On Thu, 2013-03-14 at 21:43 +0100, Istvan Gabor wrote: Can it run linux programs that have their own (linux) kernel module? If yes, how can I install such program, and how can I load the kernel module? (If I know correctly nvidia drivers have their own kernel modules, and FreeBSD can run linux nvidia drivers). Yesno. You need to compile kernel modules to fit to the version of FreeBSD or Linux. I also call user space FreeBSD and Linux, but it's _not_ correct to do it. FreeBSD is a kernel and Linux is a kernel, not the whole system is called Linux or FreeBSD and both kernels are available in different versions. You're right about Linux (being only a kernel). Not so for FreeBSD. FreeBSD is the name of the OS,, kernel plus userland. You can compare it to debian, another (linux based) OS. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: linux program with kernel module
On Fri, 2013-03-15 at 15:03 +, Ruben de Groot wrote: On Thu, Mar 14, 2013 at 10:42:41PM +0100, Ralf Mardorf typed: On Thu, 2013-03-14 at 21:43 +0100, Istvan Gabor wrote: Can it run linux programs that have their own (linux) kernel module? If yes, how can I install such program, and how can I load the kernel module? (If I know correctly nvidia drivers have their own kernel modules, and FreeBSD can run linux nvidia drivers). Yesno. You need to compile kernel modules to fit to the version of FreeBSD or Linux. I also call user space FreeBSD and Linux, but it's _not_ correct to do it. FreeBSD is a kernel and Linux is a kernel, not the whole system is called Linux or FreeBSD and both kernels are available in different versions. You're right about Linux (being only a kernel). Not so for FreeBSD. FreeBSD is the name of the OS,, kernel plus userland. You can compare it to debian, another (linux based) OS. Ok, thanks :). However, I also should be more precise about compiling modules. It might be that somebody did build a package, that does provide a kernel module for a special kernel version. I don't have experiences with FreeBSD and for FreeBSD I anyway build from the ports tree, so I have no idea about packages for FreeBSD, but I suspect that it's as it is for most Linux distros. Sometimes packages do provide modules for the current default kernel. So on major Linux distros you usually can install VBox from a package and it will come with the kernel modules for the packaged default kernel of the distro. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
linux program with kernel module
Hello: This might be a silly question but I would like to be sure. FreeBSD can run linux programs with its linux compatibility module (linuxulator). Can it run linux programs that have their own (linux) kernel module? If yes, how can I install such program, and how can I load the kernel module? (If I know correctly nvidia drivers have their own kernel modules, and FreeBSD can run linux nvidia drivers). Thanks, Istvan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: linux program with kernel module
On Thu, 2013-03-14 at 21:43 +0100, Istvan Gabor wrote: Can it run linux programs that have their own (linux) kernel module? If yes, how can I install such program, and how can I load the kernel module? (If I know correctly nvidia drivers have their own kernel modules, and FreeBSD can run linux nvidia drivers). Yesno. You need to compile kernel modules to fit to the version of FreeBSD or Linux. I also call user space FreeBSD and Linux, but it's _not_ correct to do it. FreeBSD is a kernel and Linux is a kernel, not the whole system is called Linux or FreeBSD and both kernels are available in different versions. To compile a module you need to install the kernel headers of the same version as the kernel. The module quasi is the driver. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Build linux,ko kernel module standalone
Hello, if I wanna build a kernel module standalone (without the kernel e.g. for testing) I do it the following way (wlan in this example): cd /usr/src/sys/modules/wlan make all maybe make install if I wanna install it. Now I want do build the linux.ko module with the symbol DEBUG defined and tried the following: cd /usr/src/sys/modules/linux make -DDEBUG all but unfortunately this ends up with: cc -c -O2 -pipe -march=athlon64 -DCOMPAT_FREEBSD32 -DCOMPAT_LINUX32 -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mno-sse -mcmodel=kernel -mno-red-zone -mno-mmx -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option /usr/src/sys/modules/linux/../../amd64/linux32/linux32_genassym.c In file included from ./machine/param.h:46, from @/sys/param.h:115, from /usr/src/sys/modules/linux/../../amd64/linux32/linux32_genassym.c:4: ./machine/_align.h:6:24: error: x86/_align.h: No such file or directory Building the module insinde a make buildkernel works fine - so there are actually no missing files. Do you have any ideas what I'am missing? Thank you, Martin Laabs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Build linux,ko kernel module standalone
On 01/03/2013 06:57 AM, Martin Laabs wrote: Hello, if I wanna build a kernel module standalone (without the kernel e.g. for testing) I do it the following way (wlan in this example): cd /usr/src/sys/modules/wlan make all maybe make install if I wanna install it. Now I want do build the linux.ko module with the symbol DEBUG defined and tried the following: cd /usr/src/sys/modules/linux make depend make -DDEBUG all Be wary of changing compile options for only certain parts of the kernel, as this may lead to problems with mismatching code. -- Fuzzy love, -CyberLeo Furry Peace! - http://www.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Carp kernel module missing from FreeNAS?
Guys Im looking to have a failover for my FreeNAS systsem. Im folllowing this, example ( http://qq929962616.72pines.com/2012/03/configure-highly-available-storage-on-freenas/ ), but is doesnt look like the Carp module is available. If that is true, anyone know how I can go about adding / enabling carp on FreeNAS. Someone made a suggestion of: FreeNAS uses a standard FreeBSD Kernel, so you can simply download the module from the FreeBSD FTP site and it will work. You have to have the right version however. How can or woulld I go about that? Your help would be most appreciated. Regards Brent Clark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: replacing a kernel module located in installation Dvd
Found answer to my own question http://www.cyclecide.com/~rudy/example/custom-freebsd.html is the link that i was looking for this is to replace a precompiled file (such as adding a kernel module or changing default kernel) Regards. On Sat, Feb 11, 2012 at 8:20 PM, Omer Faruk SEN omerf...@gmail.com wrote: Hi, I am looking for a way to replace a kernel module on installation DVD and rebuild it so i can use it. I have made one about 2-3 years ago based on a script that i have found on internet but now i couldn't able to find it. Can someone direct me to the right place or suggest a way to do so since I absolutely remember nothing on how it was done.. Thanks in advance. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: replacing a kernel module located in installation Dvd
Or to use a patch file (my friend send this to me) which is a better method if you can apply patch http://romana.now.ie/writing/customfreebsdiso.html On Mon, Feb 13, 2012 at 2:13 PM, Omer Faruk SEN omerf...@gmail.com wrote: Found answer to my own question http://www.cyclecide.com/~rudy/example/custom-freebsd.html is the link that i was looking for this is to replace a precompiled file (such as adding a kernel module or changing default kernel) Regards. On Sat, Feb 11, 2012 at 8:20 PM, Omer Faruk SEN omerf...@gmail.comwrote: Hi, I am looking for a way to replace a kernel module on installation DVD and rebuild it so i can use it. I have made one about 2-3 years ago based on a script that i have found on internet but now i couldn't able to find it. Can someone direct me to the right place or suggest a way to do so since I absolutely remember nothing on how it was done.. Thanks in advance. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
replacing a kernel module located in installation Dvd
Hi, I am looking for a way to replace a kernel module on installation DVD and rebuild it so i can use it. I have made one about 2-3 years ago based on a script that i have found on internet but now i couldn't able to find it. Can someone direct me to the right place or suggest a way to do so since I absolutely remember nothing on how it was done.. Thanks in advance. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: acroread9 - kernel module load error
On Fri, Jun 03, 2011 at 12:14:36AM +0200, Polytropon wrote: On Thu, 2 Jun 2011 23:43:51 +0200, Patrick Lamaiziere patf...@davenulle.org wrote: We need a kernel module to see some pdf with acrobat now? I was thinking exactly the same (without further investigation). Luckily xpdf and gv, as well as Gnome's and KDE's PDF viewer don't need kernel modules. :-) Which is exactly the way i've headed. It's just not worth the hassle. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
acroread9 - kernel module load error
Hello Installed this port but the kernel won't load and produces the following error: think# /usr/local/etc/rc.d/linux_adobe start kldload: can't load /usr/local/libexec/linux_adobe/linux_adobe.ko: Exec format error /usr/local/etc/rc.d/linux_adobe: WARNING: Unable to load kernel module /usr/local/libexec/linux_adobe/linux_adobe.ko Has anyone else experienced this? Does anyone have any suggestions to fix it? best wishes jamie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
acroread9 - kernel module load error
Jamie Paul Griffin writes: Installed this port but the kernel won't load and produces the following error: think# /usr/local/etc/rc.d/linux_adobe start kldload: can't load /usr/local/libexec/linux_adobe/linux_adobe.ko: Exec format error /usr/local/etc/rc.d/linux_adobe: WARNING: Unable to load kernel module /usr/local/libexec/linux_adobe/linux_adobe.ko Has anyone else experienced this? Does anyone have any suggestions to fix it? It means your kernel and kernel sources are not in sync. The solution is to (re-)build the kernel and program using the same source tree. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: acroread9 - kernel module load error
On Thu, Jun 02, 2011 at 08:23:22AM -0400, Robert Huff wrote: Jamie Paul Griffin writes: Installed this port but the kernel won't load and produces the following error: think# /usr/local/etc/rc.d/linux_adobe start kldload: can't load /usr/local/libexec/linux_adobe/linux_adobe.ko: Exec format error /usr/local/etc/rc.d/linux_adobe: WARNING: Unable to load kernel module /usr/local/libexec/linux_adobe/linux_adobe.ko Has anyone else experienced this? Does anyone have any suggestions to fix it? It means your kernel and kernel sources are not in sync. The solution is to (re-)build the kernel and program using the same source tree. ok, thanks for the info. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: acroread9 - kernel module load error
On Thu, Jun 02, 2011 at 08:23:22AM -0400, Robert Huff wrote: Jamie Paul Griffin writes: Installed this port but the kernel won't load and produces the following error: think# /usr/local/etc/rc.d/linux_adobe start kldload: can't load /usr/local/libexec/linux_adobe/linux_adobe.ko: Exec format error /usr/local/etc/rc.d/linux_adobe: WARNING: Unable to load kernel module /usr/local/libexec/linux_adobe/linux_adobe.ko Has anyone else experienced this? Does anyone have any suggestions to fix it? It means your kernel and kernel sources are not in sync. The solution is to (re-)build the kernel and program using the same source tree. ok, i've just been through make buildworld, etc. and rebuilt the port but still the same problem? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: acroread9 - kernel module load error
On Thu, 2 Jun 2011 23:43:51 +0200, Patrick Lamaiziere patf...@davenulle.org wrote: We need a kernel module to see some pdf with acrobat now? I was thinking exactly the same (without further investigation). Luckily xpdf and gv, as well as Gnome's and KDE's PDF viewer don't need kernel modules. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: acroread9 - kernel module load error
Polytropon free...@edvax.de wrote: On Thu, 2 Jun 2011 23:43:51 +0200, Patrick Lamaiziere patf...@davenulle.org wrote: We need a kernel module to see some pdf with acrobat now? I was thinking exactly the same (without further investigation). I suspect it's because FreeBSD uses Linux Acroread, so we need the Linuxulator, plus (I suppose) an additional API or 3. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
using openssl in kernel module that are loaded at runtime
I've got a quick question about using openssl within custom kernel modules that are loaded at runtime. Is openssl designed to be used within kernel modules? Specifically I want to use some the des and aes encryption routines. I have a kernel module (for an embedded system) that includes openssl/des.h. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Custom Kernel -- Module exclusion by association
My meaning in the 'subject' is: Currently we want to: 'options QUOTA' in the kernel. We do not want to compile any modules that we don't have to (effort to save time). If adding support for 'QUOTA' doesn't require any module rebuilding, how do we specify/exclude 'all' module building using 'WITHOUT_MODULES' in the /etc/make.conf? In addition, if there are modules that need to be rebuilt in 'association' with the 'options QUOTA', or any other kernel addition, how are we to tell 'what is' needed and/or what 'is not' needed before blindly omitting modules from the kernel build process? 2) The man make.conf shows a listing for 'KERNCONF', the installed (7.3) file: /usr/share/examples/etc/make.conf makes no mention of this. Should we decide to employ the use of 'KERNCONF' within our /etc/make.conf, does this get auto-magically read if we only type: env -i make buildkernel KERNCONF --without typing a configuration filename? Assuming of course we saved the named file in /usr/src/sys/arch/conf. Thanks for taking the time to read my msg. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
kernel module krpc required for zfs on amd64, but not needed on ia64?
On ia64 to get zfs I only need to have makeoptions MODULES_OVERRIDE=opensolaris zfs in the kernel config: # kldstat Id Refs AddressSize Name 19 0xe400 cc6688 kernel 21 0xe4cc8000 1ff4a8 zfs.ko 32 0xe4ec8000 14b60opensolaris.ko On amd64 it seems one also needs krpc kernel module: KLD zfs.ko: depends on krpc - not available or version mismatch Is this expected? Perhaps on ia64 krpc is included via some other kernel config option? many thanks -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
can't load smbfs kernel module
This is on FreeBSD 9.0-CURRENT #0 r202964M ia64 I've built a kernel with smbfs module: # ls -al /boot/kernel/smb* -r-xr-xr-x 1 root wheel 265579 25 Jan 13:36 /boot/kernel/smbfs.ko -r-xr-xr-x 1 root wheel 680186 25 Jan 13:36 /boot/kernel/smbfs.ko.symbols but can't load it: # kldload smbfs kldload: can't load smbfs: No such file or directory Other modules load fine with kldload, e.g.: # ls -al /boot/kernel/geom_part_apm* -r-xr-xr-x 1 root wheel 21320 25 Jan 13:36 /boot/kernel/geom_part_apm.ko -r-xr-xr-x 1 root wheel 51141 25 Jan 13:36 /boot/kernel/geom_part_apm.ko.symbols # kldload geom_part_apm # kldstat Id Refs AddressSize Name 15 0xe400 b69e60 kernel 21 0xe4b6a000 3d268geom_mirror.ko 31 0xa0646000 14000geom_part_apm.ko # All I need is to mount an MS WIndows partition to my fbsd box. Please advise many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: can't load smbfs kernel module
Anton Shterenlikht wrote: This is on FreeBSD 9.0-CURRENT #0 r202964M ia64 I've built a kernel with smbfs module: # ls -al /boot/kernel/smb* -r-xr-xr-x 1 root wheel 265579 25 Jan 13:36 /boot/kernel/smbfs.ko -r-xr-xr-x 1 root wheel 680186 25 Jan 13:36 /boot/kernel/smbfs.ko.symbols but can't load it: # kldload smbfs kldload: can't load smbfs: No such file or directory Other modules load fine with kldload, e.g.: Does it make any difference to use the .ko extension, to call it by absolute path, or to use -v for more information, per The Friendly Manual? Certainly no expert. Wondering tho, as I don't know if the kernel maintains a list of new objects if they've been recently added. Hate to ask if you've done a reboot :-) Also, for curiosity, `file /boot/kernel/smbfs.ko`? All I need is to mount an MS WIndows partition to my fbsd box. Please advise many thanks anton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: can't load smbfs kernel module
On Mon, Jan 25, 2010 at 10:38:47AM -0600, Kevin Kinsey wrote: Anton Shterenlikht wrote: This is on FreeBSD 9.0-CURRENT #0 r202964M ia64 I've built a kernel with smbfs module: # ls -al /boot/kernel/smb* -r-xr-xr-x 1 root wheel 265579 25 Jan 13:36 /boot/kernel/smbfs.ko -r-xr-xr-x 1 root wheel 680186 25 Jan 13:36 /boot/kernel/smbfs.ko.symbols but can't load it: # kldload smbfs kldload: can't load smbfs: No such file or directory Other modules load fine with kldload, e.g.: Does it make any difference to use the .ko extension, to call it by absolute path, or to use -v for more information, per The Friendly Manual? no, doesn't make any difference: # kldload -v /boot/kernel/smbfs.ko kldload: can't load /boot/kernel/smbfs.ko: No such file or directory # but I see in /var/log/messages: kernel: KLD smbfs.ko: depends on libiconv - not available or version mismatch I've rebuilt world, rebuilt and reinstalled kernel, installed world, and merged, etc., including rm -rf /usr/obj/* , so there shouldn't be any version mismatch. Is there a way to debug this further? Also, for curiosity, `file /boot/kernel/smbfs.ko`? seems to be the same as other modules: # file /boot/kernel/smbfs.ko /boot/kernel/smbfs.ko: ELF 64-bit LSB shared object, IA-64, version 1 (FreeBSD), dynamically linked, not stripped # file /boot/kernel/geom_mirror.ko /boot/kernel/geom_mirror.ko: ELF 64-bit LSB shared object, IA-64, version 1 (FreeBSD), dynamically linked, not stripped # many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: can't load smbfs kernel module
On Mon, Jan 25, 2010 at 09:56:54PM +, Anton Shterenlikht wrote: On Mon, Jan 25, 2010 at 10:38:47AM -0600, Kevin Kinsey wrote: Anton Shterenlikht wrote: This is on FreeBSD 9.0-CURRENT #0 r202964M ia64 I've built a kernel with smbfs module: # ls -al /boot/kernel/smb* -r-xr-xr-x 1 root wheel 265579 25 Jan 13:36 /boot/kernel/smbfs.ko -r-xr-xr-x 1 root wheel 680186 25 Jan 13:36 /boot/kernel/smbfs.ko.symbols but can't load it: # kldload smbfs kldload: can't load smbfs: No such file or directory Other modules load fine with kldload, e.g.: Does it make any difference to use the .ko extension, to call it by absolute path, or to use -v for more information, per The Friendly Manual? no, doesn't make any difference: # kldload -v /boot/kernel/smbfs.ko kldload: can't load /boot/kernel/smbfs.ko: No such file or directory # but I see in /var/log/messages: kernel: KLD smbfs.ko: depends on libiconv - not available or version mismatch I've rebuilt world, rebuilt and reinstalled kernel, installed world, and merged, etc., including rm -rf /usr/obj/* , so there shouldn't be any version mismatch. Is there a way to debug this further? well.. maybe this is irrelevant, but I disovered that there is actually a module libiconv, despite the fact that there are already libiconv lib built with the base OS: ls -al /usr/local/lib/libiconv.* -rw-r--r-- 1 root wheel 1113476 4 Aug 22:40 /usr/local/lib/libiconv.a -r--r--r-- 1 root wheel 920 4 Aug 22:40 /usr/local/lib/libiconv.la lrwxr-xr-x 1 root wheel 13 4 Aug 22:40 /usr/local/lib/libiconv.so - libiconv.so.3 -r--r--r-- 1 root wheel 1102764 4 Aug 22:40 /usr/local/lib/libiconv.so.3 Anyway, I've built the libiconv module, and loaded it to the kernel, but still get the same error trying to load smbfs. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
VirtualBox kernel module messages
For the first time so far, I managed to get emulators/virtualbox to compile and install from ports a few hours ago. Following the pkg-messages, I attempted to kldload vboxdrv or whatever it was called, which resulted in an immediate crash and automatic system reboot. :-( However, I had already added vboxdrv_load=YES vboxnetflt_load=YES to /boot/loader.conf and so was expecting it to fail, but it didn't. I even started up VirtualBox and looked at a couple of things, then looked around in it for a few minutes. Aside from the fact that the help subsystem was MIA, I didn't notice anything untoward. Except for the recurring console messages, which began during system startup and have continued ever since. Here's what a few of them look like. Oct 28 17:00:00 hellas newsyslog[1939]: logfile turned over due to size100K Oct 28 17:02:03 hellas kernel: VBoxDrvFreeBSDClone: pszName=pts ppDev=0xe84bea14 Oct 28 17:02:36 hellas kernel: VBoxDrvFreeBSDClone: pszName=input ppDev=0xe84e2948 Oct 28 17:02:36 hellas kernel: VBoxDrvFreeBSDClone: pszName=dsp ppDev=0xe84e2948 Oct 28 17:02:47 hellas kernel: VBoxDrvFreeBSDClone: pszName=pts ppDev=0xe84e5a14 Oct 28 17:03:27 hellas kernel: VBoxDrvFreeBSDClone: pszName=dsp ppDev=0xe84e2948 Oct 28 17:03:51 hellas kernel: VBoxDrvFreeBSDClone: pszName=tty ppDev=0xe84af948 Oct 28 17:06:04 hellas kernel: VBoxDrvFreeBSDClone: pszName=crypto ppDev=0xe84a3948 Oct 28 17:06:04 hellas kernel: VBoxDrvFreeBSDClone: pszName=crypto ppDev=0xe84a3948 Oct 28 17:06:13 hellas kernel: VBoxDrvFreeBSDClone: pszName=pts ppDev=0xe84c4a14 Oct 28 17:13:58 hellas kernel: VBoxDrvFreeBSDClone: pszName=pts ppDev=0xe84b2a14 Oct 28 17:22:52 hellas kernel: VBoxDrvFreeBSDClone: pszName=devfs ppDev=0xe84cda14 Oct 28 17:22:52 hellas kernel: VBoxDrvFreeBSDClone: pszName=procfs ppDev=0xe84cda14 Oct 28 17:22:52 hellas kernel: VBoxDrvFreeBSDClone: pszName=linprocfs ppDev=0xe84cda14 Oct 28 17:23:02 hellas kernel: VBoxDrvFreeBSDClone: pszName=devfs ppDev=0xe8518a14 Oct 28 17:23:02 hellas kernel: VBoxDrvFreeBSDClone: pszName=procfs ppDev=0xe8518a14 Oct 28 17:23:02 hellas kernel: VBoxDrvFreeBSDClone: pszName=linprocfs ppDev=0xe8518a14 Oct 28 17:23:02 hellas kernel: VBoxDrvFreeBSDClone: pszName=ufsid/4a6c36ef155b511e ppDev=0xc56d3a14 Oct 28 17:23:02 hellas kernel: VBoxDrvFreeBSDClone: pszName=ufsid/4a6c36ef155b511e ppDev=0xe852a948 Oct 28 17:23:10 hellas kernel: VBoxDrvFreeBSDClone: pszName=devfs ppDev=0xe8521a14 Oct 28 17:23:10 hellas kernel: VBoxDrvFreeBSDClone: pszName=procfs ppDev=0xe8521a14 Oct 28 17:23:10 hellas kernel: VBoxDrvFreeBSDClone: pszName=linprocfs ppDev=0xe8521a14 Oct 28 17:23:10 hellas kernel: VBoxDrvFreeBSDClone: pszName=ufsid/49a51b513d5a2f23 ppDev=0xc56d3a14 Oct 28 17:23:10 hellas kernel: VBoxDrvFreeBSDClone: pszName=ufsid/49a51b513d5a2f23 ppDev=0xe851b948 Oct 28 17:23:12 hellas kernel: VBoxDrvFreeBSDClone: pszName=devfs ppDev=0xc57baa14 Oct 28 17:23:12 hellas kernel: VBoxDrvFreeBSDClone: pszName=procfs ppDev=0xc57baa14 Oct 28 17:23:12 hellas kernel: VBoxDrvFreeBSDClone: pszName=linprocfs ppDev=0xc57baa14 Oct 28 17:23:21 hellas kernel: VBoxDrvFreeBSDClone: pszName=devfs ppDev=0xe848aa14 Oct 28 17:23:21 hellas kernel: VBoxDrvFreeBSDClone: pszName=procfs ppDev=0xe848aa14 Oct 28 17:23:21 hellas kernel: VBoxDrvFreeBSDClone: pszName=linprocfs ppDev=0xe848aa14 Oct 28 17:23:23 hellas kernel: VBoxDrvFreeBSDClone: pszName=devfs ppDev=0xe8518a14 Oct 28 17:23:23 hellas kernel: VBoxDrvFreeBSDClone: pszName=procfs ppDev=0xe8518a14 Oct 28 17:23:23 hellas kernel: VBoxDrvFreeBSDClone: pszName=linprocfs ppDev=0xe8518a14 Oct 28 17:23:23 hellas kernel: VBoxDrvFreeBSDClone: pszName=ufsid/4a1a6000244a7cbf ppDev=0xc56d3a14 Oct 28 17:23:23 hellas kernel: VBoxDrvFreeBSDClone: pszName=ufsid/4a1a6000244a7cbf ppDev=0xc57ba948 Oct 28 17:23:57 hellas kernel: VBoxDrvFreeBSDClone: pszName=devfs ppDev=0xe8494a14 Oct 28 17:23:57 hellas kernel: VBoxDrvFreeBSDClone: pszName=procfs ppDev=0xe8494a14 Oct 28 17:23:57 hellas kernel: VBoxDrvFreeBSDClone: pszName=linprocfs ppDev=0xe8494a14 Oct 28 17:23:57 hellas kernel: VBoxDrvFreeBSDClone: pszName=devfs ppDev=0xe84dca14 Oct 28 17:23:57 hellas kernel: VBoxDrvFreeBSDClone: pszName=procfs ppDev=0xe84dca14 Oct 28 17:23:57 hellas kernel: VBoxDrvFreeBSDClone: pszName=linprocfs ppDev=0xe84dca14 Oct 28 17:26:53 hellas kernel: VBoxDrvFreeBSDClone: pszName=devfs ppDev=0xe849fa14 Oct 28 17:26:53 hellas kernel: VBoxDrvFreeBSDClone: pszName=procfs ppDev=0xe849fa14 Oct 28 17:26:53 hellas kernel: VBoxDrvFreeBSDClone: pszName=linprocfs ppDev=0xe849fa14 Oct 28 17:27:05 hellas kernel: VBoxDrvFreeBSDClone: pszName=devfs ppDev=0xe84d9a14 Oct 28 17:27:05 hellas kernel: VBoxDrvFreeBSDClone: pszName=procfs ppDev=0xe84d9a14 Oct 28 17:27:05 hellas kernel: VBoxDrvFreeBSDClone: pszName=linprocfs ppDev=0xe84d9a14 Oct 28 17:27:06 hellas kernel: VBoxDrvFreeBSDClone: pszName=ufsid/490d7606153c869c ppDev=0xc56d3a14 Oct 28 17:27:06 hellas kernel: VBoxDrvFreeBSDClone:
Re: VirtualBox kernel module messages
Scott Bennett wrote: For the first time so far, I managed to get emulators/virtualbox to compile and install from ports a few hours ago. Following the pkg-messages, I attempted to kldload vboxdrv or whatever it was called, which resulted in an immediate crash and automatic system reboot. :-( This is a known problem and documented on the wiki page: http://wiki.freebsd.org/VirtualBox However, I had already added vboxdrv_load=YES vboxnetflt_load=YES to /boot/loader.conf and so was expecting it to fail, but it didn't. I even started up VirtualBox and looked at a couple of things, then looked around in it for a few minutes. Aside from the fact that the help subsystem was MIA, I didn't notice anything untoward. Except for the recurring console messages, which began during system startup and have continued ever since. Here's what a few of them look like. Oct 28 17:00:00 hellas newsyslog[1939]: logfile turned over due to size100K Oct 28 17:02:03 hellas kernel: VBoxDrvFreeBSDClone: pszName=pts ppDev=0xe84bea14 Oct 28 17:02:36 hellas kernel: VBoxDrvFreeBSDClone: pszName=input ppDev=0xe84e2948 Oct 28 17:02:36 hellas kernel: VBoxDrvFreeBSDClone: pszName=dsp ppDev=0xe84e2948 Do you have build VirtualBox with debug option? Beat ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD kernel module and sending udp packets
Hello everyone. I need help with documentation concerning how to send a udp or tcp packet from a kernel module. I have found this information for Linux but not for FreeBSD. Please help me. Thank you :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD kernel module and sending udp packets
On Sun, Dec 7, 2008 at 6:30 PM, Ferner Cilloniz [EMAIL PROTECTED] wrote: Hello everyone. I need help with documentation concerning how to send a udp or tcp packet from a kernel module. I have found this information for Linux but not for FreeBSD. Please help me. Thank you :) I think that you should send this question to freebsd-net list (Networking and TCP/IP with FreeBSD) this is its url http://lists.freebsd.org/mailman/listinfo/freebsd-net -- Linux is for people who hate Windows, BSD is for people who love UNIX. Social Engineer - Because there is no patch for human stupidity The Unix Guru's View of Sex unzip ; strip ; touch ; grep ; finger ; mount ; fsck ; more ; yes ; umount ; sleep. Documentation is like sex: when it is good, it is very, very good; and when it is bad, it is better than nothing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Linksys wpc100 kernel module
Is there a Linksys wpc100 (802.11) kernel module? The card is not detected in: FreeBSD 6.3-RELEASE-p3 #2 TIA T.B. -- During times of universal deceit, telling the truth becomes a revolutionary act. - George Orwell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: difference between loading kernel module during boot and after boot manually?
On Mon, Jul 14, 2008 at 10:58 PM, Mel [EMAIL PROTECTED] wrote: On Monday 14 July 2008 20:29:07 Vincent Barus wrote: On Tue, Jul 8, 2008 at 8:11 PM, Mel [EMAIL PROTECTED] wrote: On Tuesday 08 July 2008 16:48:26 Vincent Barus wrote: does anyone have an idea what's the difference or what _could_ be the difference on loading a kernel module during boot or manually? There's one major difference. File systems aren't mounted at loader stage, so any reference to modules/libraries that exist on a different partition, will fail. Right now i have only one partition and the same problem occurs. Other modules e.g. for sound or the nvidia module work as a charm. So I think that's not the only difference. I can live with a module loaded at the end of the boot process/after login but I don't think that's the real solution. Hmm, I can only guess here. Is the machine booting to xorg? As in, is the nvidia card actually initialized, not just in VGA mode? If so, does it work when it stays in console mode and/or when nvidia.ko is removed from the loaded modules? -- Mel Problem with today's modular software: they start with the modules and never get to the software part. I start X manually after login. You want me to unload nvidia.ko while on console? I never tried it -- have to try it. The card gets initialized during boot as it should instead of the nic which causes: re0: RealTek 8168/8111B PCIe Gigabit Ethernet port 0xd800-0xd8ff mem 0xfebff000-0xfebf irq 17 at device 0.0 on pci4 re0: couldn't map ports/memory device_attach: re0 attach returned 6 as described in kern/123563 How do I track down mapping problems on boot time? Regards, Vince ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: difference between loading kernel module during boot and after boot manually?
On Tuesday 15 July 2008 15:20:19 Vincent Barus wrote: On Mon, Jul 14, 2008 at 10:58 PM, Mel [EMAIL PROTECTED] wrote: On Monday 14 July 2008 20:29:07 Vincent Barus wrote: On Tue, Jul 8, 2008 at 8:11 PM, Mel [EMAIL PROTECTED] wrote: On Tuesday 08 July 2008 16:48:26 Vincent Barus wrote: does anyone have an idea what's the difference or what _could_ be the difference on loading a kernel module during boot or manually? There's one major difference. File systems aren't mounted at loader stage, so any reference to modules/libraries that exist on a different partition, will fail. Right now i have only one partition and the same problem occurs. Other modules e.g. for sound or the nvidia module work as a charm. So I think that's not the only difference. I can live with a module loaded at the end of the boot process/after login but I don't think that's the real solution. Hmm, I can only guess here. Is the machine booting to xorg? As in, is the nvidia card actually initialized, not just in VGA mode? If so, does it work when it stays in console mode and/or when nvidia.ko is removed from the loaded modules? -- Mel Problem with today's modular software: they start with the modules and never get to the software part. I start X manually after login. Which comes first? Your own script that loads if_re or Xorg being loaded. The possibility I'm trying to rule out, is that the nvidia module loading it's agp driver and nvidiactl module, fixes your if_re issues, because they take up that memory space. So, to (dis)prove this: * in /boot/loader.conf and/or kernel config, no mention of if_re * in /boot/loader.conf load nvidia.ko * wait till machine boots * do not start X, instead from root console kldload if_re * Expected result: failing to load * start X * kldload if_re * Expected result: successful load -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: difference between loading kernel module during boot and after boot manually?
On Tue, Jul 8, 2008 at 8:11 PM, Mel [EMAIL PROTECTED] wrote: On Tuesday 08 July 2008 16:48:26 Vincent Barus wrote: does anyone have an idea what's the difference or what _could_ be the difference on loading a kernel module during boot or manually? There's one major difference. File systems aren't mounted at loader stage, so any reference to modules/libraries that exist on a different partition, will fail. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. Right now i have only one partition and the same problem occurs. Other modules e.g. for sound or the nvidia module work as a charm. So I think that's not the only difference. I can live with a module loaded at the end of the boot process/after login but I don't think that's the real solution. Regards, Vincent ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: difference between loading kernel module during boot and after boot manually?
On Monday 14 July 2008 20:29:07 Vincent Barus wrote: On Tue, Jul 8, 2008 at 8:11 PM, Mel [EMAIL PROTECTED] wrote: On Tuesday 08 July 2008 16:48:26 Vincent Barus wrote: does anyone have an idea what's the difference or what _could_ be the difference on loading a kernel module during boot or manually? There's one major difference. File systems aren't mounted at loader stage, so any reference to modules/libraries that exist on a different partition, will fail. Right now i have only one partition and the same problem occurs. Other modules e.g. for sound or the nvidia module work as a charm. So I think that's not the only difference. I can live with a module loaded at the end of the boot process/after login but I don't think that's the real solution. Hmm, I can only guess here. Is the machine booting to xorg? As in, is the nvidia card actually initialized, not just in VGA mode? If so, does it work when it stays in console mode and/or when nvidia.ko is removed from the loaded modules? -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: difference between loading kernel module during boot and after boot manually?
On Sun, Jun 22, 2008 at 11:29 PM, Vincent Barus [EMAIL PROTECTED] wrote: Hi everybody, is there a difference between loading a kernel module during the boot process and loading a module manually after the login? I'm asking this on a general basis and because of pr: kern/123563. I don't know if it's a problem with if_re because I can't find someone out on the net having the same problem. The driver if_re works after laoding it manually after the login and I have no problems with it after this manual kldload if_re. Can you guys give me a hint how to get further with the troubleshooting because I can't find any difference with pciconf or the boot -v messages. Pyun did a nice job with if_re and shame on me for making his driver responsible at first but that's the only driver I can reproduce this problem with so I don't know if there's a hardware / driver / base issue. The facts about my configuration etc. is in http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/123563 If you want more information please write me. Thanks and kind regards, Vincent Hi all, does anyone have an idea what's the difference or what _could_ be the difference on loading a kernel module during boot or manually? Regards, Vincent ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: difference between loading kernel module during boot and after boot manually?
I don't know what the difference is, but there is one. I have a system that automatically reboots if nvidia is added to /boot/loader.conf on FreeBSD7. If the module is loaded from the loader prompt the system boots and xorg works. I now use solaris on that system as FreeBSD had all sorts of issues, but I recall adding a kldload statement to a startup script. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: difference between loading kernel module during boot and after boot manually?
On Tuesday 08 July 2008 16:48:26 Vincent Barus wrote: does anyone have an idea what's the difference or what _could_ be the difference on loading a kernel module during boot or manually? There's one major difference. File systems aren't mounted at loader stage, so any reference to modules/libraries that exist on a different partition, will fail. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
difference between loading kernel module during boot and after boot manually?
Hi everybody, is there a difference between loading a kernel module during the boot process and loading a module manually after the login? I'm asking this on a general basis and because of pr: kern/123563. I don't know if it's a problem with if_re because I can't find someone out on the net having the same problem. The driver if_re works after laoding it manually after the login and I have no problems with it after this manual kldload if_re. Can you guys give me a hint how to get further with the troubleshooting because I can't find any difference with pciconf or the boot -v messages. Pyun did a nice job with if_re and shame on me for making his driver responsible at first but that's the only driver I can reproduce this problem with so I don't know if there's a hardware / driver / base issue. The facts about my configuration etc. is in http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/123563 If you want more information please write me. Thanks and kind regards, Vincent ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Off topic: Online article DIY - kernel module
Dear newsgroup, I accidentally stumbled over an article that allegedly describes how to make your own kernel module for FreeBSD7 and felt an urge to share this. The article can be found and downloaded at www.freesoftwaremagazine.com. /Roger ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Off topic: Online article DIY - kernel module
Hi there, Roger Olofsson: Dear newsgroup, I accidentally stumbled over an article that allegedly describes how to make your own kernel module for FreeBSD7 and felt an urge to share this. The article talks about ULE scheduler. Would you recommend using it against SCHED_4BSD in this context: CPU: Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz (2400.01-MHz 686-class CPU) Jun 17 17:22:38 relay kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs Many thanks! Zbigniew Szalbot smime.p7s Description: S/MIME Cryptographic Signature
Re: Off topic: Online article DIY - kernel module
Zbigniew Szalbot skrev: Hi there, Roger Olofsson: Dear newsgroup, I accidentally stumbled over an article that allegedly describes how to make your own kernel module for FreeBSD7 and felt an urge to share this. The article talks about ULE scheduler. Would you recommend using it against SCHED_4BSD in this context: CPU: Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz (2400.01-MHz 686-class CPU) Jun 17 17:22:38 relay kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs Many thanks! Zbigniew Szalbot Dear Zbigniew, May I suggest that you direct your question to the author of the article? /Roger ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Build a single kernel module?
today. The new card is a D-link DGE-530T which shall work with the 'sk' driver. My custom kernel does not have this driver. I wonder if I can build this single driver as a module to use with my already cd /usr/src/sys/modules/whatyouwant make ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Build a single kernel module?
quoth the Wojciech Puchar: today. The new card is a D-link DGE-530T which shall work with the 'sk' driver. My custom kernel does not have this driver. I wonder if I can build this single driver as a module to use with my already cd /usr/src/sys/modules/whatyouwant make Thanks, I will remember this for the future. -d -- darren kirby :: Part of the problem since 1976 :: http://badcomputer.org ...the number of UNIX installations has grown to 10, with more expected... - Dennis Ritchie and Ken Thompson, June 1972 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Build a single kernel module?
Hi all, I recently built a custom kernel for my new FreeBSD 7.0-RELEASE system, and it is working well. Sadly, I had to purchase and swap out a nic on this machine today. The new card is a D-link DGE-530T which shall work with the 'sk' driver. My custom kernel does not have this driver. I wonder if I can build this single driver as a module to use with my already built custom kernel. The handbook mentions using MODULES_OVERRIDE: If you want to update a kernel faster or to build only custom modules, you should edit /etc/make.conf before starting to build the kernel So as I understand it, if I add MODULES_OVERRIDE = sk to make.conf then it will build only the sk module? The page [0] is light on details so I am unsure hoe to proceed with this, ie: I just do a normal 'make installkernel' or some other way? Also, I did look around, but if there are some docs that speak more clearly to this issue a pointer would be great. Thanks for consideration, -d [0] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html -- darren kirby :: Part of the problem since 1976 :: http://badcomputer.org ...the number of UNIX installations has grown to 10, with more expected... - Dennis Ritchie and Ken Thompson, June 1972 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[solved] Re: Build a single kernel module?
quoth the darren kirby: Please disregard. I have realized the module is called if_sk.ko, not sk.ko, so it is in fact built... -d -- darren kirby :: Part of the problem since 1976 :: http://badcomputer.org ...the number of UNIX installations has grown to 10, with more expected... - Dennis Ritchie and Ken Thompson, June 1972 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel module error
Hi all, Trying to build kernel and I get the following error: /usr/src/sys/modules/acpi/acpi/../../../contrib/dev/acpica/exmutex.c:373:10: invalid preprocessing directive #return_AGPI_STATUS mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/modules/acpi/acpi. *** Error code 1 Stop in /usr/src/sys/modules/acpi. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Never had this error before and I just cvsup latest stable-supfile FreeBSD 6.3-PRERELEASE Thank you BSD Networking, Microsoft Notworking ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bpf kernel module
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vlad GURDIGA wrote: On 12/11/06, Vlad GURDIGA [EMAIL PROTECTED] wrote: On 12/11/06, Garrett Cooper [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vlad GURDIGA wrote: Hello, I'm trying to keep very close touch with 6.1_STABLE cvsupping sources once a week or even more often. I'm thinking of removing as much as possible devices from the kernel loading them from /boot/loader.conf instead, so I could rebuild and install them without a whole kernel/world rebuild and reboot when sources change. I'm not sure this is a correct way, any piece of advice regarding this would be highly appreciated. :) So, I've successfully done that with sound and network card drivers, but did not succeed with removing bpf from the kernel. Booting a kernel with no bpf support, and with ng_bpf_load=YES in my loader.conf, the pflogd fails to start with this error: Nov 11 20:22:33 uxterm pflogd[10251]: Failed to initialize: (no devices found) /dev/bpf0: No such file or directory Nov 11 20:22:33 uxterm pflogd[10251]: Exiting, init failure And, tcpdump also fails saying that no suitable device found. Of course there is no /dev/bpf0. Is there any way to have the bpf0 device without booting a kernel with bpf device included? Berkeley packet filter (bpf) is required for a lot of net related things, such as dhcpcd, tcpdump (as you've discovered), amongst many other things. Don't know if you want to go disabling that... I do not intend to disable it, just have it apart, so I could update it easyer. So, is it possible to have bpf apart from kernel? Not sure if it's possible or not, but someone is bound to know on one of the freebsd lists.. - -Garrett -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFWDwF6CkrZkzMC68RAmaJAJ43une+fFzquDmpVUkxCRwPvnv2gQCZARJr BqgPcyUDJyA1Uk4dlaXxJIs= =TU5H -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
IPMI kernel module errors on 6.x
Hi Everyone, I purchased a new Supermicro Superserver SS6015B-T (motherboard is X7DBR-E) about 3 weeks ago with the IPMI module (part called SIMSO) and have had a hard time getting the IPMI functionality to work in RELENG_6. Particularly, when I attempt to 'kldload ipmi' I get the following output in dmesg: ipmi0: IPMI System Interface on isa0 ipmi0: KCS mode found at mem 0xca2 alignment 0x4 on isa ipmi0: KCS: Failed to start write ipmi0: KCS Error retry exhausted ipmi0: KCS: Failed to start write ipmi0: KCS Error retry exhausted ipmi0: KCS: Failed to start write ipmi0: KCS Error retry exhausted ipmi0: Timed out waiting for GET_DEVICE_ID From the dmesg, it appears it's finding the IPMI device, but unable to interact with it. Meanwhile, no device shows up in /dev so ipmitool does not work, either. For reference, here is my uname: FreeBSD exodus 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #9: Fri Nov 10 10:56:39 PST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/EXODUS amd64 This is a RELENG_6 build with a CVSUP done just before the compile date of the kernel. The SIMSO IPMI card itself works, I can access it via the web management console, I just can not get the kernel driver to work with it. Any help and/or references would be greatly appreciated. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bpf kernel module
Garrett Cooper [EMAIL PROTECTED] writes: Vlad GURDIGA wrote: So, is it possible to have bpf apart from kernel? Not sure if it's possible or not, but someone is bound to know on one of the freebsd lists.. Does look possible to me... -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bpf kernel module
On 12/11/06, Lowell Gilbert [EMAIL PROTECTED] wrote: Vlad GURDIGA [EMAIL PROTECTED] writes: I'm trying to keep very close touch with 6.1_STABLE cvsupping sources once a week or even more often. I'm thinking of removing as much as possible devices from the kernel loading them from /boot/loader.conf instead, so I could rebuild and install them without a whole kernel/world rebuild and reboot when sources change. I'm not sure this is a correct way, any piece of advice regarding this would be highly appreciated. :) So, I've successfully done that with sound and network card drivers, but did not succeed with removing bpf from the kernel. Booting a kernel with no bpf support, and with ng_bpf_load=YES in my loader.conf, the pflogd fails to start with this error: Nov 11 20:22:33 uxterm pflogd[10251]: Failed to initialize: (no devices found) /dev/bpf0: No such file or directory Nov 11 20:22:33 uxterm pflogd[10251]: Exiting, init failure And, tcpdump also fails saying that no suitable device found. Of course there is no /dev/bpf0. Is there any way to have the bpf0 device without booting a kernel with bpf device included? The kernel module *should* work. I suspect that there is an error message when it tries to load the module and fails. You could check for that error message, or try to load the module by hand and see if you get a clue to the problem. Here is how I did: commented out the device bpf line in the kernel, built and installed the kernel, and added ng_bpf_load=YES in loader.conf. I guess this is the module for the bpf (is this correct? I'm not 100% sure). So, booting with the new kernel, and the module being loaded from the loader.conf, the pflogd fails to start with this error: Nov 11 20:22:33 uxterm pflogd[10251]: Failed to initialize: (no devices found) /dev/bpf0: No such file or directory Nov 11 20:22:33 uxterm pflogd[10251]: Exiting, init failure And, tcpdump also fails saying that no suitable device found. Of course there is no /dev/bpf0. Unfortunately, I do not have enough experience to figure out how to load this device at runtime. Is there any solution to this situation? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bpf kernel module
On Sun, Nov 12, 2006 at 05:29:23PM +0200, Vlad GURDIGA wrote: On 12/11/06, Lowell Gilbert [EMAIL PROTECTED] wrote: Vlad GURDIGA [EMAIL PROTECTED] writes: I'm trying to keep very close touch with 6.1_STABLE cvsupping sources once a week or even more often. I'm thinking of removing as much as possible devices from the kernel loading them from /boot/loader.conf instead, so I could rebuild and install them without a whole kernel/world rebuild and reboot when sources change. I'm not sure this is a correct way, any piece of advice regarding this would be highly appreciated. :) So, I've successfully done that with sound and network card drivers, but did not succeed with removing bpf from the kernel. Booting a kernel with no bpf support, and with ng_bpf_load=YES in my loader.conf, the pflogd fails to start with this error: Nov 11 20:22:33 uxterm pflogd[10251]: Failed to initialize: (no devices found) /dev/bpf0: No such file or directory Nov 11 20:22:33 uxterm pflogd[10251]: Exiting, init failure And, tcpdump also fails saying that no suitable device found. Of course there is no /dev/bpf0. Is there any way to have the bpf0 device without booting a kernel with bpf device included? The kernel module *should* work. I suspect that there is an error message when it tries to load the module and fails. You could check for that error message, or try to load the module by hand and see if you get a clue to the problem. Here is how I did: commented out the device bpf line in the kernel, built and installed the kernel, and added ng_bpf_load=YES in loader.conf. I guess this is the module for the bpf (is this correct? I'm not 100% sure). So, booting with the new kernel, and the module being loaded from the loader.conf, the pflogd fails to start with this error: ng_bpf(4) and bpf(4) are *not* the same thing. ng_bpf is a netgraph interface to bpf. For some reason bpf(4) does not seem to be available as a module, so if you want to use it then it has to be included in your kernel config. Nov 11 20:22:33 uxterm pflogd[10251]: Failed to initialize: (no devices found) /dev/bpf0: No such file or directory Nov 11 20:22:33 uxterm pflogd[10251]: Exiting, init failure And, tcpdump also fails saying that no suitable device found. Of course there is no /dev/bpf0. Unfortunately, I do not have enough experience to figure out how to load this device at runtime. Is there any solution to this situation? No, it does not seem to be possible to load bpf at runtime. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
bpf kernel module
Hello, I'm trying to keep very close touch with 6.1_STABLE cvsupping sources once a week or even more often. I'm thinking of removing as much as possible devices from the kernel loading them from /boot/loader.conf instead, so I could rebuild and install them without a whole kernel/world rebuild and reboot when sources change. I'm not sure this is a correct way, any piece of advice regarding this would be highly appreciated. :) So, I've successfully done that with sound and network card drivers, but did not succeed with removing bpf from the kernel. Booting a kernel with no bpf support, and with ng_bpf_load=YES in my loader.conf, the pflogd fails to start with this error: Nov 11 20:22:33 uxterm pflogd[10251]: Failed to initialize: (no devices found) /dev/bpf0: No such file or directory Nov 11 20:22:33 uxterm pflogd[10251]: Exiting, init failure And, tcpdump also fails saying that no suitable device found. Of course there is no /dev/bpf0. Is there any way to have the bpf0 device without booting a kernel with bpf device included? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bpf kernel module
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vlad GURDIGA wrote: Hello, I'm trying to keep very close touch with 6.1_STABLE cvsupping sources once a week or even more often. I'm thinking of removing as much as possible devices from the kernel loading them from /boot/loader.conf instead, so I could rebuild and install them without a whole kernel/world rebuild and reboot when sources change. I'm not sure this is a correct way, any piece of advice regarding this would be highly appreciated. :) So, I've successfully done that with sound and network card drivers, but did not succeed with removing bpf from the kernel. Booting a kernel with no bpf support, and with ng_bpf_load=YES in my loader.conf, the pflogd fails to start with this error: Nov 11 20:22:33 uxterm pflogd[10251]: Failed to initialize: (no devices found) /dev/bpf0: No such file or directory Nov 11 20:22:33 uxterm pflogd[10251]: Exiting, init failure And, tcpdump also fails saying that no suitable device found. Of course there is no /dev/bpf0. Is there any way to have the bpf0 device without booting a kernel with bpf device included? Berkeley packet filter (bpf) is required for a lot of net related things, such as dhcpcd, tcpdump (as you've discovered), amongst many other things. Don't know if you want to go disabling that... - -Garrett -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFVk8v6CkrZkzMC68RAmxpAJ9V9Rlz5fCW190FSoWYB8ZjRtBYawCfVG6s QbadL9e1NLAbhtOunZLwrt0= =VYKr -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs LIBSMBCRYPTO [was Re: Kernel module path]
On Wed, 7 Jun 2006 12:28:46 -0500 Nikolas Britton [EMAIL PROTECTED] wrote: (snip) Do you know if they ever fix crypto bug in mount_smbfs in FreeBSD 6.1? Yeah, they did... Assuming you're thinking of the same thing I am, whereby attempting to authenticate to a server for SMB access resulted in being told that cryptography wasn't availabl e (or some such). I think it had something to do with a LIBSMBCRYPTO setting, or similar, but can't recall. -- Nick Withers email: [EMAIL PROTECTED] Web: http://www.nickwithers.com Mobile: +61 414 397 446 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel module path
On Wed, Jun 07, 2006 at 11:28:09AM +0100, Richard Jones wrote: Hi, I'm having trouble loading kernel modules. Put simply make installkernel seems install native kernel modules into /boot/kernel/, but kldload seems to want to load them from /boot/modules. Obviously I can load modules by hand and/or copy the modules into /boot/modules, but surely there's a better way - either by modifying the installkernel behaviour or kldload. And in answer to my own question, I've found the answer. Despite the man page suggesting the default value for module_path being /boot/kernel;/boot/modules, my /boot/defaults/loader.conf had just /boot/modules. I've checked in /usr/src/sys/boot and this seems to be system default, does anyone know why this is? Regards, Richard -- Richard Jones MSN: [EMAIL PROTECTED] Y!M: rwkjones http://www.jonze.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel module path
Hi, I'm having trouble loading kernel modules. Put simply make installkernel seems install native kernel modules into /boot/kernel/, but kldload seems to want to load them from /boot/modules. Obviously I can load modules by hand and/or copy the modules into /boot/modules, but surely there's a better way - either by modifying the installkernel behaviour or kldload. R -- Richard Jones MSN: [EMAIL PROTECTED] Y!M: rwkjones http://www.jonze.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel module path
On Wed, 7 Jun 2006 11:28:09 +0100 Richard Jones [EMAIL PROTECTED] wrote: Hi, I'm having trouble loading kernel modules. Put simply make installkernel seems install native kernel modules into /boot/kernel/, but kldload seems to want to load them from /boot/modules. From kldload's man page: FILES /boot/kernel directory containing loadable modules. Modules must have an extension of .ko. This having been said, it _does_ look in /boot/modules as well. I'm able to load a module from either directory without specifying the full path and / or extension and without either directory being my current working directory on 6.1-RELEASE. What's the problem you're actually having? What version of FreeBSD are you running? Obviously I can load modules by hand and/or copy the modules into /boot/modules, but surely there's a better way - either by modifying the installkernel behaviour or kldload. I believe that base system kernel modules for the currently installed kernel should be installed to /boot/kernel and that kernel modules from outside FreeBSD (e.g.: nvidia.ko) are installed to /boot/modules. R -- Richard Jones MSN: [EMAIL PROTECTED] Y!M: rwkjones http://www.jonze.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Nick Withers email: [EMAIL PROTECTED] Web: http://www.nickwithers.com Mobile: +61 414 397 446 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel module path
On Wed, Jun 07, 2006 at 11:28:09AM +0100, Richard Jones wrote: Hi, I'm having trouble loading kernel modules. Put simply make installkernel seems install native kernel modules into /boot/kernel/, but kldload seems to want to load them from /boot/modules. Obviously I can load modules by hand and/or copy the modules into /boot/modules, but surely there's a better way - either by modifying the installkernel behaviour or kldload. kldconfig(8) might be of help here. Dan -- Daniel Bye PGP Key: http://www.slightlystrange.org/pgpkey-dan.asc PGP Key fingerprint: D349 B109 0EB8 2554 4D75 B79A 8B17 F97C 1622 166A _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgp2oiJytjsnL.pgp Description: PGP signature
Re: Kernel module path
On Wed, Jun 07, 2006 at 10:40:54PM +1000, Nick Withers wrote:
On Wed, 7 Jun 2006 11:28:09 +0100
Richard Jones [EMAIL PROTECTED] wrote:
Hi,
I'm having trouble loading kernel modules. Put simply make
installkernel seems install native kernel modules into /boot/kernel/,
but kldload seems to want to load them from /boot/modules.
From kldload's man page:
FILES
/boot/kernel directory containing loadable modules.
Modules must have an extension of .ko.
This having been said, it _does_ look in /boot/modules as well.
I'm able to load a module from either directory without
specifying the full path and / or extension and without either
directory being my current working directory on 6.1-RELEASE.
What's the problem you're actually having? What version of
FreeBSD are you running?
Yes, sorry, that wasn't the most infomational email.
FreeBSD-6.1-RELEASE.
me ~ # ls -1 /boot/kernel
fire_saver.ko
if_tun.ko
ipfw.ko
kernel
libiconv.ko
libmchain.ko
linker.hints
linux.ko
smbfs.ko
me ~ # ls -1 /boot/kernel
nvidia.ko
linker.hints
me ~ # kldload smbfs
kldload: can't load smbfs: No such file or directory
me ~ # cp /boot/kernel/{smbfs.ko,libiconv.ko,libmchain.ko} /boot/modules/
me ~ # kldload smbfs
short pause
me ~ # kldstat
Id Refs AddressSize Name
1 12 0xc040 3c68c4 kernel
22 0xc07c7000 1f280linux.ko
31 0xc07e7000 3f2e00 nvidia.ko
61 0xc50e 2smbfs.ko
72 0xc4f51000 4000 libiconv.ko
82 0xc4154000 3000 libmchain.ko
--
Richard Jones
MSN: [EMAIL PROTECTED]
Y!M: rwkjones
http://www.jonze.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel module path
On 6/7/06, Richard Jones [EMAIL PROTECTED] wrote: Hi, I'm having trouble loading kernel modules. Put simply make installkernel seems install native kernel modules into /boot/kernel/, but kldload seems to want to load them from /boot/modules. 3rd party kernel modules go in /boot/modules and /boot/kernel is for FreeBSD only. Obviously I can load modules by hand and/or copy the modules into /boot/modules, but surely there's a better way - either by modifying the installkernel behaviour or kldload. Yes, this drives me nuts too. For example the kqemu port gets installed in /boot/kernel and highpoint's manuals tell you to install drivers there too. The problem is that if you rebuild your kernel or do a buildworld et. al. it will wipeout everything in /boot/kernel... This is why we have /boot/modules, everything in here will survive a kernel rebuild, buildworld, etc... From the loader man page (FreeBSD 6.1): module_path Sets the list of directories which will be searched for modules named in a load command or implicitly required by a dependency. The default value for this variable is ``/boot/kernel;/boot/modules''. From the hier man page (FreeBSD 6.1): /boot/ programs and configuration files used during operating system bootstrap defaults/ default bootstrapping configuration files; see loader.conf(5) kernel/pure kernel executable (the operating system loaded into memory at boot time). modules/ third-party loadable kernel modules; see kldstat(8) -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel module path
On Wednesday 07 June 2006 12:22, John Nielsen wrote: On Wednesday 07 June 2006 08:41, Daniel Bye wrote: On Wed, Jun 07, 2006 at 11:28:09AM +0100, Richard Jones wrote: Hi, I'm having trouble loading kernel modules. Put simply make installkernel seems install native kernel modules into /boot/kernel/, but kldload seems to want to load them from /boot/modules. Obviously I can load modules by hand and/or copy the modules into /boot/modules, but surely there's a better way - either by modifying the installkernel behaviour or kldload. kldconfig(8) might be of help here. There is a sysctl that controls this. By default on my 6-STABLE it is: %sysctl kern.module_path kern.module_path: /boot/kernel;/boot/modules;/usr/local/modules So the FreeBSD 5.x and newer default of putting kernel modules in /boot/kernel is covered. Check the output of the above command on your system and check /etc/sysctl.conf for any overrides. Oh, I don't think /usr/local/modules is there by default. It was added on my system by one of the FUSE ports I'm using. The first two are definitely there by default, though. Sorry for the misinformation. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel module path
On Wednesday 07 June 2006 08:41, Daniel Bye wrote: On Wed, Jun 07, 2006 at 11:28:09AM +0100, Richard Jones wrote: Hi, I'm having trouble loading kernel modules. Put simply make installkernel seems install native kernel modules into /boot/kernel/, but kldload seems to want to load them from /boot/modules. Obviously I can load modules by hand and/or copy the modules into /boot/modules, but surely there's a better way - either by modifying the installkernel behaviour or kldload. kldconfig(8) might be of help here. There is a sysctl that controls this. By default on my 6-STABLE it is: %sysctl kern.module_path kern.module_path: /boot/kernel;/boot/modules;/usr/local/modules So the FreeBSD 5.x and newer default of putting kernel modules in /boot/kernel is covered. Check the output of the above command on your system and check /etc/sysctl.conf for any overrides. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel module path
On 6/7/06, Richard Jones [EMAIL PROTECTED] wrote:
On Wed, Jun 07, 2006 at 10:40:54PM +1000, Nick Withers wrote:
On Wed, 7 Jun 2006 11:28:09 +0100
Richard Jones [EMAIL PROTECTED] wrote:
Hi,
I'm having trouble loading kernel modules. Put simply make
installkernel seems install native kernel modules into /boot/kernel/,
but kldload seems to want to load them from /boot/modules.
From kldload's man page:
FILES
/boot/kernel directory containing loadable modules.
Modules must have an extension of .ko.
This having been said, it _does_ look in /boot/modules as well.
I'm able to load a module from either directory without
specifying the full path and / or extension and without either
directory being my current working directory on 6.1-RELEASE.
What's the problem you're actually having? What version of
FreeBSD are you running?
Yes, sorry, that wasn't the most infomational email.
FreeBSD-6.1-RELEASE.
me ~ # ls -1 /boot/kernel
fire_saver.ko
if_tun.ko
ipfw.ko
kernel
libiconv.ko
libmchain.ko
linker.hints
linux.ko
smbfs.ko
me ~ # ls -1 /boot/kernel
nvidia.ko
linker.hints
me ~ # kldload smbfs
kldload: can't load smbfs: No such file or directory
me ~ # cp /boot/kernel/{smbfs.ko,libiconv.ko,libmchain.ko} /boot/modules/
me ~ # kldload smbfs
short pause
me ~ # kldstat
Id Refs AddressSize Name
1 12 0xc040 3c68c4 kernel
22 0xc07c7000 1f280linux.ko
31 0xc07e7000 3f2e00 nvidia.ko
61 0xc50e 2smbfs.ko
72 0xc4f51000 4000 libiconv.ko
82 0xc4154000 3000 libmchain.ko
Do you know if they ever fix crypto bug in mount_smbfs in FreeBSD 6.1?
--
BSD Podcasts @:
http://bsdtalk.blogspot.com/
http://freebsdforall.blogspot.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ipfw Kernel Module - Default to Accept?
On 5/30/2006 9:45 AM Toni Schmidbauer wrote: At Tue, 30 May 2006 09:04:09 -0700, Drew Tomlinson wrote: I'm using FBSD 6.1. When using the ipfw kernel module, is it possible to get ipfw loaded in a default to accept mode? I've seen the kernel option to enable this when compiling statically but nothing specific to the kernel module. Maybe there's a way to compile the kernel module with some entry in /etc/make.conf? I've Googled but have not been able to turn up anything. you can recompile the module, uncomment the line #CFLAGS+= -DIPFIREWALL_DEFAULT_TO_ACCEPT in /usr/src/sys/modules/ipfw/Makefile. next call make in the same directory and copy the compiled module to /boot/kernel. i've done that in the past, works like a charm. Thank you. I'll try it. Drew -- Be a Great Magician! Visit The Alchemist's Warehouse http://www.alchemistswarehouse.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ipfw Kernel Module - Default to Accept?
I'm using FBSD 6.1. When using the ipfw kernel module, is it possible to get ipfw loaded in a default to accept mode? I've seen the kernel option to enable this when compiling statically but nothing specific to the kernel module. Maybe there's a way to compile the kernel module with some entry in /etc/make.conf? I've Googled but have not been able to turn up anything. Thanks, Drew -- Be a Great Magician! Visit The Alchemist's Warehouse http://www.alchemistswarehouse.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ipfw Kernel Module - Default to Accept?
At Tue, 30 May 2006 09:04:09 -0700, Drew Tomlinson wrote: I'm using FBSD 6.1. When using the ipfw kernel module, is it possible to get ipfw loaded in a default to accept mode? I've seen the kernel option to enable this when compiling statically but nothing specific to the kernel module. Maybe there's a way to compile the kernel module with some entry in /etc/make.conf? I've Googled but have not been able to turn up anything. you can recompile the module, uncomment the line #CFLAGS+= -DIPFIREWALL_DEFAULT_TO_ACCEPT in /usr/src/sys/modules/ipfw/Makefile. next call make in the same directory and copy the compiled module to /boot/kernel. i've done that in the past, works like a charm. hth, toni ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel module for ipf
On 5/18/06, Giorgos Keramidas [EMAIL PROTECTED] wrote: Yes, this should be in the handbook. I'll try to add it :) Let me know if you want a hand. I'm happy to help with that. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel module for ipf
Hello, The handbook mentions that ipf should work out of the box in FreeBSD thanks to a kernel module, but it doesn't say which one. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls-ipf.html IPF is included in the basic FreeBSD install as a separate run time loadable module. The system will dynamically load the IPF kernel loadable module when the rc.conf statement ipfilter_enable=YES is used. The loadable module was created with logging enabled and the default pass all options. You do not need to compile IPF into the FreeBSD kernel just to change the default to block all, you can do that by just coding a block all rule at the end of your rule set. I don't see anything under /boot/kernel that looks like a likely candidate. There's an ipfw.ko, but no ipf or ipfilter. I'd prefer to not reboot my system just to find out, so could someone point me to the correct module? I'm running FreeBSD 5.4 with the GENERIC kernel. Thanks, Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel module for ipf
On 2006-05-18 12:05, Michael P. Soulier [EMAIL PROTECTED] wrote: Hello, The handbook mentions that ipf should work out of the box in FreeBSD thanks to a kernel module, but it doesn't say which one. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls-ipf.html IPF is included in the basic FreeBSD install as a separate run time loadable module. The system will dynamically load the IPF kernel loadable module when the rc.conf statement ipfilter_enable=YES is used. The loadable module was created with logging enabled and the default pass all options. You do not need to compile IPF into the FreeBSD kernel just to change the default to block all, you can do that by just coding a block all rule at the end of your rule set. I don't see anything under /boot/kernel that looks like a likely candidate. There's an ipfw.ko, but no ipf or ipfilter. I'd prefer to not reboot my system just to find out, so could someone point me to the correct module? I'm running FreeBSD 5.4 with the GENERIC kernel. The module is called ipl.ko: # ls -l /boot/kernel/ipl.* -r-xr-xr-x 1 root wheel - 171625 May 16 16:05 /boot/kernel/ipl.ko -r-xr-xr-x 1 root wheel - 371887 May 16 16:05 /boot/kernel/ipl.ko.symbols # Strange and weird, but this is the name the IP Filter kernel module has had for years, so it's not easy to change it now without breaking all the scripts around the world that assume its name is ipl. - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel module for ipf
On 5/18/06, Scott Mitchell [EMAIL PROTECTED] wrote: You want the ipl.ko module. No, I have no idea why it's called ipl not ipf either... [EMAIL PROTECTED] ~]# ls /boot/kernel/ipl* /boot/kernel/ipl.ko* Ah. Cool. Thanks. Yes, this should be in the handbook. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel module for ipf
On Thu, May 18, 2006 at 12:05:00PM -0400, Michael P. Soulier wrote: Hello, The handbook mentions that ipf should work out of the box in FreeBSD thanks to a kernel module, but it doesn't say which one. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls-ipf.html IPF is included in the basic FreeBSD install as a separate run time loadable module. The system will dynamically load the IPF kernel loadable module when the rc.conf statement ipfilter_enable=YES is used. The loadable module was created with logging enabled and the default pass all options. You do not need to compile IPF into the FreeBSD kernel just to change the default to block all, you can do that by just coding a block all rule at the end of your rule set. I don't see anything under /boot/kernel that looks like a likely candidate. There's an ipfw.ko, but no ipf or ipfilter. I'd prefer to not reboot my system just to find out, so could someone point me to the correct module? I'm running FreeBSD 5.4 with the GENERIC kernel. Hi Mike, You want the ipl.ko module. No, I have no idea why it's called ipl not ipf either... Cheers, Scott -- === Scott Mitchell | PGP Key ID | Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines scott at fishballoon.org | 0xAA775B8B | -- Anon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel module for ipf
On 2006-05-18 12:52, Michael P. Soulier [EMAIL PROTECTED] wrote: On 5/18/06, Scott Mitchell [EMAIL PROTECTED] wrote: You want the ipl.ko module. No, I have no idea why it's called ipl not ipf either... [EMAIL PROTECTED] ~]# ls /boot/kernel/ipl* /boot/kernel/ipl.ko* Ah. Cool. Thanks. Yes, this should be in the handbook. I'll try to add it :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 Kernel module with 6.0
On Tue, Jan 10, 2006 at 11:10:21PM +0100, Rainer Hungershausen wrote: Hi there! I've got a Highpoint RocketRAID 454 Controller running under FreeBSD 5.3. It needs a binary only driver (hpt374.ko) to run. I'd like to upgrade to 6.0 for several reasons, but the latest driver module from highpoint is for 5.3. So here's my question: Is it possible to simply run the 5.3 kernel module under 6.x? In theory this could work if the kernel interfaces haven't changed, right? Yes, but they did, so you can't. Kris pgpU0GluTWbuQ.pgp Description: PGP signature
5.3 Kernel module with 6.0
Hi there! I've got a Highpoint RocketRAID 454 Controller running under FreeBSD 5.3. It needs a binary only driver (hpt374.ko) to run. I'd like to upgrade to 6.0 for several reasons, but the latest driver module from highpoint is for 5.3. So here's my question: Is it possible to simply run the 5.3 kernel module under 6.x? In theory this could work if the kernel interfaces haven't changed, right? Please also respond directly to me since I am not subscribed to this list. Thanks for your help, Rainer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X error: [drm] failed to load kernel module i915
On Wed, 2005-12-07 at 20:46 +0200, [EMAIL PROTECTED] wrote: Hello I have problem with running X. I have tried to run it on FreeBSD 6.0 with LG 1730s and intel integrated card 82865G. after I had read previous posts I have tried to change the Xorg.conf.new and test it but I still getting the errors: [drm] failed to load kernel module i915 (EE) I810(0): [DRI] DRIScreenInit failed. Disabling DRI. FreeFontPath: FPE /usr/X11R6/lib/X11/Fonts/misc/ refcount is 2, should be 1:, fixing also I have seen this warning on the log file: (WW) I810(0): Bad V_BIOS checksum Does anyone know how to solve it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] You need to update your xorg driver. Let me know if you need it ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
X error: [drm] failed to load kernel module i915
Hello I have problem with running X. I have tried to run it on FreeBSD 6.0 with LG 1730s and intel integrated card 82865G. after I had read previous posts I have tried to change the Xorg.conf.new and test it but I still getting the errors: [drm] failed to load kernel module i915 (EE) I810(0): [DRI] DRIScreenInit failed. Disabling DRI. FreeFontPath: FPE /usr/X11R6/lib/X11/Fonts/misc/ refcount is 2, should be 1:, fixing also I have seen this warning on the log file: (WW) I810(0): Bad V_BIOS checksum Does anyone know how to solve it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel module configuration
Hi, Is there a way to compile only kernel modules that one needs like with Linux's configuration file? I included only the drivers I need in the kernel config file, but all the modules got compiled anyway. :( I looked around both in the kernel config dir and google, but didn't find anything that would allow me to select which kernel modules to compile. Thanks! Cheng -- Lab # 626 395 8820 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel module configuration
On Sat, May 14, 2005 at 03:23:53PM -0700, Cheng Jin wrote: Hi, Is there a way to compile only kernel modules that one needs like with Linux's configuration file? I included only the drivers I need in the kernel config file, but all the modules got compiled anyway. :( I looked around both in the kernel config dir and google, but didn't find anything that would allow me to select which kernel modules to compile. See the make.conf manpage. Kris pgp71eR5VJrDi.pgp Description: PGP signature
Problem loading a NDIS kernel module.
Hello, Trying to get wireless networking on my notebook, i tried the NDISulator. After copying the configuration and binary files to the corresponding path at /usr/src/sys/modules/if_ndis, i created the driver definition header using ndiscvt(8). Then, i have build and install the driver module without problem: if_ndis.ko is copied to /boot/kernel and kldxref -v seems happy (kldxref: /boot/kernel/if_ndis.ko: 488 REL entries). But, if i can load the NDIS driver wrapper correctly (using kldload ndis), loading the network interface seems more problematic: # kldload if_ndis kldload: can't load if_ndis: No such file or directory Here is the kernel message: # tail -1 /var/log/messages Apr 16 15:05:46 boboche kernel: link_elf: symbol windrv_load undefined I tried this with the two available Windows versions for this wireless network module: win98/2k and winxp... without much success. Any clue or advice to get it loading/working? Thanks. -- -jpeg. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Xorg Config Problem-[drm] failed to load kernel module i915
I've just installed FreeBSD 5.3-RELEASE #0 and ran into a problem configuring X Window System Version 6.8.2. I have an ASUS P4P800 motherboard with a built-in graphic card (Intel 865G GMCH I believe). I receive the following error message when running the configuration test: [drm] failed to load kernel module i915 (EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI. This seems similar to the problem you had with the Intel chipset 945. I read your comment (below) but don't fully understand what steps were required. Could you provide more detail? I solved this problem by using the text configuration tool via the xorgconfig command. I picked the i810 chipset driver and Xorg started up just fine. Thank you, Bob Perry -- I've learned that whatever hits the fan will not be evenly distributed. FreeBSD 4.9-RELEASE-p2 #0 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: [drm] failed to load kernel module i915
I solved this problem by using the text configuration tool via the xorgconfig command. I picked the i810 chipset driver and Xorg started up just fine. Thanks for your assistance. From: GRF . [EMAIL PROTECTED] To: freebsd-questions@FreeBSD.ORG Subject: [drm] failed to load kernel module i915 Date: Thu, 03 Feb 2005 22:27:09 -0500 I have installed 5.3 and am trying to set up xorg on an Intel motherboard with a build in 945 chipset graphic card. 4.10 was a breeze to set up for X but so far I receive what I believe is the following error: -snip- from Xorg.0.log drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed [drm] failed to load kernel module i915 (II) I810(0): [drm] drmOpen failed (EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI. -snip- The complete Xorg.0.log can be seen here: http://www.dawgeestyle.com/Xorg.0.log The xorg.conf.new can be seen here: http://www.dawgeestyle.com/xorg.conf.new Where do I go from here? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[drm] failed to load kernel module i915
I have installed 5.3 and am trying to set up xorg on an Intel motherboard with a build in 945 chipset graphic card. 4.10 was a breeze to set up for X but so far I receive what I believe is the following error: -snip- from Xorg.0.log drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed [drm] failed to load kernel module i915 (II) I810(0): [drm] drmOpen failed (EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI. -snip- The complete Xorg.0.log can be seen here: http://www.dawgeestyle.com/Xorg.0.log The xorg.conf.new can be seen here: http://www.dawgeestyle.com/xorg.conf.new Where do I go from here? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [drm] failed to load kernel module i915
On Thu, Feb 03, 2005 at 10:27:09PM -0500, GRF . wrote: I have installed 5.3 and am trying to set up xorg on an Intel motherboard with a build in 945 chipset graphic card. 4.10 was a breeze to set up for X but so far I receive what I believe is the following error: -snip- from Xorg.0.log drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed [drm] failed to load kernel module i915 (II) I810(0): [drm] drmOpen failed (EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI. -snip- The complete Xorg.0.log can be seen here: http://www.dawgeestyle.com/Xorg.0.log The xorg.conf.new can be seen here: http://www.dawgeestyle.com/xorg.conf.new Where do I go from here? Try adding the following section to xorg.conf: Section DRI Mode0666 EndSection Roland -- R.F. Smith /\ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ /No HTML/RTF in e-mail http://www.xs4all.nl/~rsmith/ X No Word docs in e-mail public key: http://www.keyserver.net / \Respect for open standards pgpbOSzBHQ9nZ.pgp Description: PGP signature
Re: Persistent kernel module?
On Tue, Jan 25, 2005 at 10:45:31AM -0500, Tim Buck wrote: Is there a way to make a kernel module persistent between kernel builds? I'm using a HighPoint SATA RAID controller on FreeBSD 5.3. HighPoint provides a driver for this controller in the form of a kernel module (hpt374.ko). Their instructions say to put the module in /boot/kernel, and add 'hpt374_load=YES' to the file /boot/defaults/loader.conf. This works, but when I build a new kernel the /boot/kernel dir gets renamed and recreated, and the hpt374.ko module doesn't get copied to the new dir. I have to copy it manually each time I build the kernel. So is there a way to make the kernel build process know about third party kernel modules and copy it over to the new /boot/kernel automatically? This is somewhat intentional; if you update your kernel source and recompile the kernel without recompiling the module, there's a good chance your kernel will panic when you try and use it. If you're not planning to update your kernel sources but just want to recompile the kernel with different options, there are other directories that are checked for module loading - see the loader.conf manpage. Kris pgp6KN3XGP6sZ.pgp Description: PGP signature
Persistent kernel module?
Is there a way to make a kernel module persistent between kernel builds? I'm using a HighPoint SATA RAID controller on FreeBSD 5.3. HighPoint provides a driver for this controller in the form of a kernel module (hpt374.ko). Their instructions say to put the module in /boot/kernel, and add 'hpt374_load=YES' to the file /boot/defaults/loader.conf. This works, but when I build a new kernel the /boot/kernel dir gets renamed and recreated, and the hpt374.ko module doesn't get copied to the new dir. I have to copy it manually each time I build the kernel. So is there a way to make the kernel build process know about third party kernel modules and copy it over to the new /boot/kernel automatically? Tim Buck * Information Technology Manager * Recognition Research, Inc. PHONE +1 540 961-6500 * FAX +1 540 961-3568 * EMAIL [EMAIL PROTECTED] No one ever went broke underestimating the intelligence of the American People -- P. T. Barnum ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel module configuration
On 2004-08-15 18:04, Hanspeter Roth [EMAIL PROTECTED] wrote: in the kernel configuration one can enable various devices by the respective 'device' statement. It seems that most drivers go into the kernel directly. Some drivers such as 'acpi' produce a kernel module. How is determined which modules become built in and which become modules? If you don't include something in the kernel it's built as a module. Can I have 'ohci' as a kernel module? I haven't tried. I don't know for sure. - Giorgos ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel module configuration
Hello, in the kernel configuration one can enable various devices by the respective 'device' statement. It seems that most drivers go into the kernel directly. Some drivers such as 'acpi' produce a kernel module. How is determined which modules become built in and which become modules? Can I have 'ohci' as a kernel module? -Hanspeter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel module configuration
Hanspeter Roth [EMAIL PROTECTED] wrote: Hello, in the kernel configuration one can enable various devices by the respective 'device' statement. It seems that most drivers go into the kernel directly. Some drivers such as 'acpi' produce a kernel module. How is determined which modules become built in and which become modules? By the config file. If you enable the module in the config, it is built into the kernel, otherwise a kld is generated. Can I have 'ohci' as a kernel module? Whether or not a specific feature is capable of operating as a kernel module or built in is specific to that feature. Some work very well in either capacity (the FAT filesystem drivers for example) others don't really work compiled into the kernel (vinum) and many others _must_ be compiled into the kernel for them to work correctly (ISA and PCI support, I believe) I don't know specifically about ohci, but the man page for ohci would be the first place to check. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Error With Kernel Module IPFILTER
I've found out from two different kernel configs that after properly compling kernel with IPFILTER support it causes the system not to boot. Its hard to say, what exactly it does, cause its not a local system. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
loading kernel module from floppy?
I'm trying to install FreeBSD 4.10 on a raid set using a RocketRaid 1640. In order to do so, I need to load the driver as a kernel module at boot time, but nowhere is it documented (that I can find) how to specify the device. I can lsdev and see disk0a: ffs and disk0c: ffs, but if I try to load disk0a:filename, it's not found. neither is /disk0a/filename or /dev/disk0a/filename. Neither does the odd syntax the earlier stage uses of 0:fd(0,a)/filename. My next step is to head for the source I guess... -- Alan Batie __alan.batie.orgMe alan at batie.org\/www.qrd.org The Triangle PGPFP DE 3C 29 17 C0 49 7A\ / www.pgpi.com The Weird Numbers 27 40 A5 3C 37 4A DA 52 B9 \/ spamassassin.taint.org NO SPAM! The true danger is when liberty is nibbled away, for expedients, and by parts. -Edmund Burke, statesman and writer (1729-1797) pgpI3GyW89zkd.pgp Description: PGP signature
Re: find symbols in loadable kernel module
On Mon, May 03, 2004 at 09:40:05PM +0200, elmar gerdes wrote: I'm looking for a mechanism that allows one loadable kernel module to find the symbols of another module, i.e. find a function 'foo' by its name and get the address of it, so I can call it. sorry, i can't help you with that, but i would recommend asking this question in [EMAIL PROTECTED] hth, toni -- Wer es einmal so weit gebracht hat, dass er nicht | toni at stderror dot at mehr irrt, der hat auch zu arbeiten aufgehoert| Toni Schmidbauer -- Max Planck | pgp0.pgp Description: PGP signature
find symbols in loadable kernel module
Hi, I'm looking for a mechanism that allows one loadable kernel module to find the symbols of another module, i.e. find a function 'foo' by its name and get the address of it, so I can call it. I've stumbled across kernel objects which should allow me to do this using kobj_lookup_method(), but I haven't found a call to this function anywhere except where it's defined. kernel objects are used for parallel port drivers and sound drivers which use some kind of bus architecture with calls like BUS_ADD_CHILD() et.al.? do I also have to use/implement such a bus architecture just to find some functions by their names? Is there a simpler method to just find the functions, or is there some more information on kernel objects (tutorial, simple example ...)? Any help is welcome. Thanx. elmar ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel module
Greetings: Could someone explain howto move something that is part of the kernel and make it a kernel module? for example the pcm, /modules/pcm.ko thanks, Brian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel module
On Tuesday, 23 March 2004 at 13:26:32 -0600, Brian Henning wrote: Greetings: Could someone explain howto move something that is part of the kernel and make it a kernel module? for example the pcm, /modules/pcm.ko This is probably something for the -hackers list, though you're likely to get an answer like read the code of an existing module and figure it out for yourself. Unfortunately, I don't know of any documentation, though there could be some. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html Note: I discard all HTML mail unseen. Finger [EMAIL PROTECTED] for PGP public key. See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
Re: kernel module
On Wed, 24 Mar 2004 11:34:47 +1030 Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Tuesday, 23 March 2004 at 13:26:32 -0600, Brian Henning wrote: Greetings: Could someone explain howto move something that is part of the kernel and make it a kernel module? for example the pcm, /modules/pcm.ko This is probably something for the -hackers list, though you're likely to get an answer like read the code of an existing module and figure it out for yourself. Unfortunately, I don't know of any documentation, though there could be some. Although I can't answer the question (as it's fairly general and I'm sure it varies depending on exactly what part of the kernel you want to move into a kernel module), these docs may help: http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/ http://ezine.daemonnews.org/200010/blueprints.html http://www.itsx.com/hal2001/fbsdfun.html -Chris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel module programming
Hello everyone! In my localized version of FreeBSD developer's handbook (russian) I have found a skeleton example for writing custom kernel modules. But I can not find it's analog in original english version of the handbook. And if I do compile example given, computer stops responding immediately as soon as I do kldload skeleton.ko, so I wanted to see original english version, for may be something changed in there, but cannot find it anywhere. Please advise! Cheers, Sch. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel module programming
Hey dude, looked at /usr/share/examples/kld/ yet? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
trying to compile my kernel module...
Today I started to write a sound driver kernel module. All have yet is a skeleton, and I cannot get it to compile. I am building the module in my home directory. I set up my Makefile as described in the developer handbook: SRCS=mykmod.c KMOD=mykmod .include bsd.kmod.mk When I run make however, I get this error (the output is from make depend): rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/dev -I/usr/include mymod.c In file included from @/dev/sound/pcm/sound.h:54, from mymod.c:29: @/sys/bus.h:381:23: device_if.h: No such file or directory @/sys/bus.h:382:20: bus_if.h: No such file or directory In file included from @/dev/sound/pcm/sound.h:98, from mymod.c:29: @/dev/sound/pcm/channel.h:69:24: channel_if.h: No such file or directory In file included from mymod.c:30: @/dev/sound/pcm/ac97.h:90:21: ac97_if.h: No such file or directory In file included from mymod.c:33: @/dev/pci/pcivar.h:156:20: pci_if.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/home/stsp/mymod. The headers are not present in the @ tree, but there are a couple of *.m files with the same basenames. The handbook says that such files were interface templates and should be processed by a perl script called something like makeobjops.pl. I am using the 5.1 release, and I cannot find makeobjops.pl on my system. Could it be that the developer handbook is only referring to FreeBSD 4.x? Compiling a custom kernel works fine though, the headers are properly generated. Am I missing something obvious? regards stefan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
