public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kevin N. Carpenter" <kevinc@seaplace.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] hardened-sources
Date: Mon, 24 Oct 2005 19:26:53 -0500	[thread overview]
Message-ID: <435D7BCD.70608@seaplace.org> (raw)
In-Reply-To: <200510241657.06034.kkrizka@gmail.com>

Hi all -

Got a funny one that has cost me a few hours of wondering, followed by 
enlightenment, followed by more wondering...  Not sure this is an AMD64 
issue or a kernel issue, but since I'm subscribed here, thought I'd 
start here.

I started my newly rebuilt system on gentoo-sources 2.6.13, but since 
this is a firewall machine, I opted to go with hardened-sources 2.6.11.  
Quickly found out that GRSecurity level "high" caused startup errors 
with INIT, but "medium" seemed to work fine.  However, for the life of 
me, I couldn't get DHCPD to respond to request for IP addressed.  No 
dmesg complaint, nothing in the log files, no network activity... the 
last was the key.  I'm using the builtin Marvel gigabit on my Asus 
motherboard.  Eventually I realized I couldn't do anything out that 
port, although ifconfig showed it up.  A bit more looking showed the 
lack of a link-light.  Tried swapping cables, ports, etc. - no go.  
Eventually booted back to 2.6.13 (non-hardened source tree) and the port 
works fine!  I noticed the LiveCD is 2.6.12, and the port works there as 
well (which kept me from going completely insane and replacing the 
motherboard.  Once it worked on LiveCD I realized I had a kernel problem.)

So... does anyone know if this is a 2.6.11 issue, and AMD-64 issue, or a 
general hardened-sources issues?

Thanks!

Kevin (running unhardened 2.6.13 for now...)
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2005-10-25  0:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-24 17:55 [gentoo-amd64] jvm package in Gentoo Mark Haney
2005-10-24 18:09 ` Craig Webster
2005-10-24 18:25   ` Mark Haney
2005-10-24 21:20 ` [gentoo-amd64] sys-kernel/ck-sources tomas
2005-10-24 19:19   ` [gentoo-amd64] sys-kernel/ck-sources Duncan
2005-10-24 19:49   ` [gentoo-amd64] sys-kernel/ck-sources Craig Webster
2005-10-24 20:42   ` Luis Medinas
2005-10-24 19:53     ` Billy Holmes
2005-10-24 23:56       ` Karol Krizka
2005-10-25  0:26         ` Kevin N. Carpenter [this message]
2005-10-25  1:16           ` [gentoo-amd64] hardened-sources Barry.SCHWARTZ
2005-10-25  2:01             ` Kevin N. Carpenter
2005-10-25  2:22               ` Barry.SCHWARTZ
2005-10-25  3:51           ` Drake Donahue
2005-10-25  4:04             ` Kevin N. Carpenter
2005-10-25  0:35         ` [gentoo-amd64] sys-kernel/ck-sources Daniel Gryniewicz
2005-10-25 11:17           ` José Carlos Cruz Costa
2005-10-25 11:36             ` [gentoo-amd64] setiathome errors Kevin N. Carpenter
2005-10-25 15:55               ` Simon Stelling
2005-10-25 11:56             ` [gentoo-amd64] sys-kernel/ck-sources Simon Strandman
2005-10-25 12:57             ` Luis Medinas
2005-10-26 13:44               ` Billy Holmes
2005-10-25 14:59             ` Daniel Gryniewicz
2005-10-26 13:40         ` Billy Holmes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=435D7BCD.70608@seaplace.org \
    --to=kevinc@seaplace.org \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox