Kernel Problems


 
Thread Tools Search this Thread
Operating Systems BSD Kernel Problems
# 8  
Old 06-11-2005
Hi !
Have you tried to compile a new version of the kernel ? Or the kernel that came with your install CD ? Anyway, the problem seems to be in one of the files... try to reinstall the sources from your install CD. If you are new and you don't want to do something complicate simply try the sysinstall command (as root). It's a very easy-to-use interface for installing packages. The same you used when you installed FreeBSD. You'll have the install menu and select from the packages the kernel sources to install.
Another option, fetching the source tree, it's a little more complicated and... not so good. At least, I don't like it This is how I'm doing this:

1. Create a "supfile" that contains something like this :
Code:

*default host=cvsup.ro.FreeBSD.org *default base=/usr *default prefix=/usr/ncvs *default compress *default release=cvs tag=. *default delete use-rel-suffix src-sys


2. Create the /usr/ncvs directory
3. Go into the directory where your supfle is and try : cvsup -g -L 2 supfile. This will download (fetch) the last kernel source tree to your computer and will put it in /usr/ncvs. After that, you have to do the normal compilation (config newKernel, make depend, make, make install clean) with your new fetched kernel source.
You should also take a look at this links:
http://www.freebsd.org/doc/en_US.IS...rnelconfig.html (for more details on kernel build)
http://www.freebsd.org/doc/en_US.IS...book/cvsup.html (for using cvsup)

Well... I hope this helps... sorry for my bad english, it's not my native language
Good luck !
Bye-Bye!
Reply With Quote


*default host=cvsup.ro.FreeBSD.org
*default base=/usr
*default prefix=/usr/ncvs
*default compress
*default release=cvs tag=.
*default delete use-rel-suffix

src-sys



I think you misadvice by asking the user to fetch the latest branch of development of FreeBSD who is not useable for production or for normal user.

I think what you wanted to do is to let him fetch the release version of FreeBSD or at least the stable release.

To achieve this just replace the following line :

(wrong line)
*default release=cvs tag=.

(good line)
*default release=cvs tag=RELENG_5_3 (if you would like by example for 5.4 you would put RELENG_5_4 and so one) if you want the latest releng of 5 you would put only 5 if you put . you will fetch the latest development release (last night workable build source)


usually people put as default prefix is in /usr/src instead of /usr/ncvs


cvs is as my opinion the best way to do update and keep your system accurate. If you follow and know what you are doing cvs is really a good tools. It's easy to use but have some pitfall like the default release tag.

you can update your ports with cvs too,

to install cvs just go in /usr/ports/net/cvsup-without-gui and make install && make clean
you will get cvsup working (take some time to compile need lot of dependancy)

after that in /usr/local/share/examples you will have some example config file, i suggest you to use the default example file like stable-supfile and ports-supfile as beginning config file.

you will only need to change the server to connect to fetch your source tree and the default release tag, you can put other options but just keep it simple for now after good reading on http://www.freebsd.org/handbook you will be enought confident to add some options at your convenience.

same thing for the ports supfile you only have to change the default server



after you could read about how to automate the whole system to auto upgrade using crontab (you will have to manually update the source system OS but for the ports it's easy to manage and can be fully automate).

to update yoru system you could go read teh handbook searching for makeworld

you can update the whole system by recompiling the fresh download source tree with cvs using makeworld.

usually it's 5 steps easy to follow

compile the source tree
compile the kernel
install the fresh compiled kernel
(reboot to load the new kernel)
install the fresh compiled source tree
merge your config file with the new from the source (to avoid delete all your config file you edited before the update) this way you can keep your config file up to date without having to reconfigure your whole setting.

it's all explain very well in the handbook.


I suggest you to read the whole handbook before asking, your question was fully detailed in the handbook and the handbook is maintain as it is really easy to read and understand same for newbie. I started reading the handbook few years ago and i continu to read it when i have problem it solves 90% of my problem. I ask only for particular project setting but never to maintain or administer my system Smilie

Feel free to ask if you are not certain how do do, i know how sometime we can feel unconfident when we are doing new thing and we are not sure if we follow exactly the doc or if we misunderstood something that put us in the wrong way. Smilie



ShadowLight
shadowlight@syrs.com
www.linu-z.net
# 9  
Old 06-11-2005
For the Kernel problem,

I invite you to read the handbook on http://www.freebsd.org/handbook

search for kernel

read the doc about how to compile your kernel, i suggest you to start with the generic just to understand how it works after you could easily edit the generic and compile it. if something goes wrong you know it's because of your change.

to fix your corruption problem i suggest you to do :

cd /usr/src
make clean

cd /usr/src/i386/sys/conf/
edit your kernel

mkdir /root/kernel
mv yourkernel /root/kernel/
ln -s /root/kernel/yourkernel /usr/src/i386/sys/conf/
(this will create a link to your kernel file this way you just have to edit the file in your root directory to get it edit in the src directory. The compile system will follow the symlink and all will be fine) (tricks to make administration easier).


after taht just compile your kernel.
i think it could be a good idea too to do a make clean in your /usr/src/i386/sys/conf/ just to be sure the clean will not affect only the os source but the kernel source too.

The make clean just clean up the compile process (it doesn't touch the source file) it just delete the last compile binary or what we name build source. You will just start again from scratch as if you never did a make buildkernel before Smilie



One more thing : when you begin do not try to delete anything from generic kernel file, you don't know what is necessary, just add don't delete stuff. You will get your life better. Deleting stuff doesn't get you any better performance anyway (or not anything that you can see or not enought for all the problem you will get trying to delete stuff). The generic is kinda already a minimal kernel for normal operation.



ShadowLight
Unix Administrator Syrius-Network
shadowlight@syrs.com
www.linu-z.net
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Red Hat

Problems with kernel patches

Three RH7 servers patched through a satellite and rebooted Sunday. Two of the three experienced issues with kernel 123.20.1 and were reporting logind and systemd errors, org.freedesktop subscription failure. Users ssh'ing into the two servers had to wait 30 seconds to get the password prompt.... (2 Replies)
Discussion started by: cjhilinski
2 Replies

2. Linux

Unload kernel module at boot time (Debian Wheezy 7.2, 3.2.0-4-686-pae kernel)

Hi everyone, I am trying to prevent the ehci_hcd kernel module to load at boot time. Here's what I've tried so far: 1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here): 2) Blacklisted the module by adding the following string to 3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies

3. SuSE

Problem compiling the kernel and linking problems in OpenSuse 12.3

Hi everyone I installed OpenSuse 12.3 and many development tools but when i propose build the kernel from the source (the first step make menuconfig) i saw this: HOSTLD scripts/kconfig/mconf /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld: warning: libdl.so.2,... (2 Replies)
Discussion started by: bacesado
2 Replies

4. Solaris

Which file is read by kernel to set its default system kernel parameters values?

Hi gurus Could anybody tell me which file is read by kernel to set its default system kernal parameters values in solaris. Here I am not taking about /etc/system file which is used to load kernal modules or to change any default system kernal parameter value Is it /dev/kmem file or something... (1 Reply)
Discussion started by: girish.batra
1 Replies

5. Linux

Supermicro(dual core) server getting rebooted after "decompressing the kernel;booting the kernel" me

supermicro(dual core) server getting rebooted after "decompressing the kernel;booting the kernel" message comes. I tried giving acpi=off to the kernel command line but same problem.It shows everything ok and no problem with memory and processors and power supplies.Wt could be the reason? It has... (1 Reply)
Discussion started by: pankajd
1 Replies

6. SuSE

max number of slabs per kernel module (kernel 2.6.17, suse)

Hi All, Is there a max number of slabs that can be used per kernel module? I'm having a tough time finding out that kind of information, but the array 'node_zonelists' (mmzone.h) has a size of 5. I just want to avoid buffer overruns and other bad stuff. Cheers, Brendan (4 Replies)
Discussion started by: Brendan Kennedy
4 Replies

7. Programming

kernel-kernel call communication

hi all! i have developed a mechanism in system.c to count how many times each kernel call is called. The results are held in an array in system.c . What i want to do is to create a new kernel call which will print this array. I need help in passing the array from system.c to the new kernel call. ... (5 Replies)
Discussion started by: aureliano
5 Replies

8. Linux

Kernel panic - not syncing: cannot execute a PAE-enabled kernel on PAE-less CPU

ok so I just installed fedora core 6 on my dell inspiron 700m and I go to boot into linux and I get this error. Has anyone seen this before? I also had XP Pro and Vista installed on this pc prior to putting fedora core 6 on the machine. I'm trying to setup a triple boot system. Please Help... (2 Replies)
Discussion started by: dave043
2 Replies

9. UNIX for Advanced & Expert Users

2.4.9 Linux Kernel & PCMCIA Wireless Problems

We are installing a PrismII chipset wireless PCMCIA card with a new 2.4.9 linux kernel. The card is a D-Link DWL-650. The 2.4.9 kernel uses the orinoco_cs.o driver. Anyone running this configuration? The 2.4.9 Linux kernel has built in PCMCIA support and the README says it supports the... (1 Reply)
Discussion started by: Neo
1 Replies
Login or Register to Ask a Question