Sir Ariz,

Thanks!

I disabled SELinux and my new kernel work. The ethernet port is now detected.

Well, I have to learn writing SELinux policy thought. It's one security feature I don't want to miss.

Again, thank you.

On 5/16/06, Ariz Jacinto <[EMAIL PROTECTED]> wrote:
it's caused by SELinux. you either disable it or create an SELinux Policy.  :)
then recompile the kernel.

hth,
Ariz




On 5/15/06, Martin Acupanda <[EMAIL PROTECTED]> wrote:
Hello PLUG,

I compiled linux kernel 2.6.16.16 for my White Box. I compiled ext2 and ext3 not as a module. My White Box is using kernel 2.6.9-5.ELsmp.
My grub boot menu.lst contain the lines:

kernel /vmlinuz-2.6.16.16 ro root=LABEL=/
initrd /initrd-2.6.16.16.img

When I boot using the new kernel, I get this message:

<snip>
Switching to new root
Enforcing mode requested but no policy loaded. Halting now.
Kernel panic - not syncing: Attempted to kill init.

The reason I decided to use a new kernel is because the ethernet port is not "seen" in the the old kernel. Anything I miss?


_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph




--

Regards,

Martin Acupanda
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph

Reply via email to