lots of brokenness (was: Re: module-init-tools-3.0-2.i386.rpm)

[Paul Iadonisi]

On Wed, 2004-09-01 at 19:55, Paul wrote:

[snip]

>  Now, the question which needs to be asked is how did something as
> bust
>  as module-init-tools and the current xorg manage to escape? 
  A lot seems busted lately.  Kernels 532, 533, and 535 all paniced on
me eventually, but I've had no chance to bugzilla anything due some
other busy-ness (fighting the good fight against the whole Sender-ID
patent crap).
  Seems that udev isn't starting in the right place, or something
related to that.  I'm getting permission errors on /dev/null (!),
non-existant /dev/microcode and other madness.  I think I finally have a
stable kernel, but I'll need to let it run (really, limp along with the
other problems it has) for a while to see how stable the kernel is.
  I downgraded initscripts and it didn't solve my (seemingly) udev
problems.  Anyone know if installing module-init-tools-3.0-2 will fix
this?  If so, I guess I'll have to hunt down a copy.
  As an upside, once I get X up and running on my i810, it seems to work
just fine.
-- 
-Paul Iadonisi
 Senior System Administrator
 Red Hat Certified Engineer / Local Linux Lobbyist
 Ever see a penguin fly?  --  Try Linux.
 GPL all the way: Sell services, don't lease secrets

[Thomas J. Baker]

On Thu, 2004-09-02 at 02:05 -0400, Paul Iadonisi wrote:
>  On Wed, 2004-09-01 at 19:55, Paul wrote:
>  
>  [snip]
>  
>  > Now, the question which needs to be asked is how did something as bust
>  > as module-init-tools and the current xorg manage to escape?
>  
>    A lot seems busted lately.  Kernels 532, 533, and 535 all paniced on
>  me eventually, but I've had no chance to bugzilla anything due some
>  other busy-ness (fighting the good fight against the whole Sender-ID
>  patent crap).
>    Seems that udev isn't starting in the right place, or something
>  related to that.  I'm getting permission errors on /dev/null (!),
>  non-existant /dev/microcode and other madness.  I think I finally have a
>  stable kernel, but I'll need to let it run (really, limp along with the
>  other problems it has) for a while to see how stable the kernel is.
>    I downgraded initscripts and it didn't solve my (seemingly) udev
>  problems.  Anyone know if installing module-init-tools-3.0-2 will fix
>  this?  If so, I guess I'll have to hunt down a copy.
>    As an upside, once I get X up and running on my i810, it seems to work
>  just fine.
>  -- 
>  -Paul Iadonisi
>   Senior System Administrator
>   Red Hat Certified Engineer / Local Linux Lobbyist
>   Ever see a penguin fly?  --  Try Linux.
>   GPL all the way: Sell services, don't lease secrets
>  
>   
Keeping/downgrading-to/or-other-wise-somehow-installing udev-030-10 and
module-init-tools-3.0-2 did the trick for me. My system booted and seems
to be running normally.

tjb
-- 
=======================================================================
| Thomas Baker                                  email: tjb(a)unh.edu    |
| Systems Programmer                                                  |
| Research Computing Center                     voice: [phone] |
| University of New Hampshire                     fax: [phone] |
| 332 Morse Hall                                                      |
| Durham, NH 03824 USA              http://wintermute.sr.unh.edu/~tjb |
=======================================================================

[Steve G]

> Seems that udev isn't starting in the right place, or something
> related to that.  I'm getting permission errors on /dev/null (!),
> non-existant /dev/microcode and other madness. 
What errors are you seeing? On the screen or the logs? SE Linux related? This is
too vague to go looking through the code for.

Thanks,
-Steve Grubb


		
_______________________________
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.
http://promotions.yahoo.com/goldrush

[Paul Iadonisi]

On Thu, 2004-09-02 at 08:05, Steve G wrote:
>  >Seems that udev isn't starting in the right place, or
> something
>  >related to that.  I'm getting permission errors on /dev/null (!),
>  >non-existant /dev/microcode and other madness.
>  
>  What errors are you seeing? On the screen or the logs? SE Linux related? This is
>  too vague to go looking through the code for. 
  Apologies.  I'm well aware the my post was vague.  I haven't had a
chance to get the details.  But one of significance is several lines
printed of the form (not exact):

Permission denied: "/dev/null"

  I'll try to get better details to the list later today.
-- 
-Paul Iadonisi
 Senior System Administrator
 Red Hat Certified Engineer / Local Linux Lobbyist
 Ever see a penguin fly?  --  Try Linux.
 GPL all the way: Sell services, don't lease secrets

[Paul Iadonisi]

On Thu, 2004-09-02 at 10:07, Paul Iadonisi wrote:

[snip]

>  > 
>  > What errors are you seeing? On the screen or the logs? SE Linux related? This is
>  > too vague to go looking through the code for.
>  
>    Apologies.  I'm well aware the my post was vague.  I haven't had a
>  chance to get the details.  But one of significance is several lines
>  printed of the form (not exact):
>  
>  Permission denied: "/dev/null"
>  
>    I'll try to get better details to the list later today. 
  Well, I guess it's all moot, now.  The latest update fixed all the
problems I was having.  Additionally, I'm not getting an kernel panics. 
Looks like it was mostly related to mismatched initscripts/udev
versions.  Might be a dependency problem, but I wouldn't say that it
really matters, since it's mid release.  Seems (according to Jeremy
Katz's response to my original message) that initscripts-7.76 is needed
for udev-030-11.


-- 
-Paul Iadonisi
 Senior System Administrator
 Red Hat Certified Engineer / Local Linux Lobbyist
 Ever see a penguin fly?  --  Try Linux.
 GPL all the way: Sell services, don't lease secrets

[Jeremy Katz]

On Thu, 2004-09-02 at 02:05 -0400, Paul Iadonisi wrote:
>  On Wed, 2004-09-01 at 19:55, Paul wrote:
>    Seems that udev isn't starting in the right place, or something
>  related to that.  I'm getting permission errors on /dev/null (!),
>  non-existant /dev/microcode and other madness.  I think I finally have a
>  stable kernel, but I'll need to let it run (really, limp along with the
>  other problems it has) for a while to see how stable the kernel is.
>    I downgraded initscripts and it didn't solve my (seemingly) udev
>  problems.  Anyone know if installing module-init-tools-3.0-2 will fix
>  this?  If so, I guess I'll have to hunt down a copy. 
initscripts 7.76 is needed for udev-030-11 or later or so

Jeremy