Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Weird behavior while building Kernel Objects



On 6/7/07, Vinay Perneti <vinay.perneti-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:
> I did reboot, I didn't rmmod though, cuz, the kernel object generated is
> nfs4xdr.ko is not in the /proc/modules list. so when i do rmmod or modprobe
> it gives me a FATAL error saying module does not exist!

Right, so it is built-in, not a module.  OK.

As to why your printk's don't output anything, make sure klogd and
syslogd are both running.  Also, you can try to set the highest
possible level for printk output...

$ echo 8 | sudo tee /proc/sys/kernel/printk

You should ensure that your kernel object was properly modified.
sha1sum it before and after your changes...
-- 
Kristian Hermansen

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.







BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org