[lkml]   [2008]   [Jan]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Problem with ata layer in 2.6.24
On Monday 28 January 2008, Daniel Barkalow wrote:
>On Mon, 28 Jan 2008, Gene Heskett wrote:
>> On Monday 28 January 2008, Daniel Barkalow wrote:
>> >Building this and installing it along with the appropriate initrd (which
>> >might be handled by Fedora's install scripts)
>> Or mine, which I've been using for years.
>You're ahead of a surprising number of people, including me, if you
>understand making initrds.

In my script, its one line:
mkinitrd -f initrd-$VER.img $VER && \

where $VER is the shell variable I edit to = the version number, located at
the top of the script.

Unforch, its failing:
No module pata_amd found for kernel 2.6.24, aborting.

This is with pata_amd turned off and its counterpart under ATA/RLL/etc turned
on. So something is still dependent on it. I do have one sata drive, on an
accessory card in the box, so I need the rest of the sata_sil and friends
stuff. Its my virtual tapes for amanda. Also home built, the amanda
security model cannot be successfully bent into the shape of an rpm. They
BTW are #2 on coverity's list of most secure software.

So I've rebuilt 2.6.24 as it originally was, and added the acpi timer line to
the 2.6.24-rc8 stanza's kernel argument list. It will boot one or the other
when I next reboot. Its been about 8 hours since the last error was logged,
which is totally weirdsville to this old fart. Phase of the moon maybe? The
visit to the sawbones to see about my heart? They are going to fit me with a
30 day recorder tomorrow, my skip a beat problem is getting worse. The sort
of stuff that goes with the 7nth decade I guess. Officially, I'm wearing out
me, too much sugar, too many times nearly electrocuted=shingles yadda
yadda. :-) Oh, and don't forget Arther, he moved in uninvited about 25 years
ago too. Those people that talk about the golden years? They're full of

>> >will either get you back to
>> >old IDE or will make your kernel panic on boot, depending on whether you
>> >got it right (so make sure you can still boot the kernel you're sure of
>> > or something from a boot disk). This will also cause your hard drives to
>> > show up as different device nodes, so if your boot process doesn't mount
>> > by disk uuid but by some other feature (and I don't know what Fedora
>> > does), you'll also need to change it to something either stable across
>> > access methods or which works for the one you're now using.
>> It mounts by LABEL=. All of it.
>That'll save a huge amount of hassle. So long as you manage to get the
>right drivers included and the wrong drivers not included, you should be
>pretty much set.
>> Fedora is not the only people having trouble, name a distro, its probably
>> someplace in that 14,800 hit google returns.
>Yeah, but they each may need different instructions, particularly if
>they're not mounting by label in general, or not mounting the root
>partition by label. That was the big hassle going the opposite direction.
>And the procedure is 4 lines to describe to somebody who knows how to
>build and install a new kernel for the distro, which is much shorter than
>the explanation of how you generally build and install a kernel. A real
>howto would have to explain where to get the distro's kernel sources and
>default configuration, for example.
> -Daniel
>*This .sig left intentionally blank*

Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Never drink from your finger bowl -- it contains only water.

 \ /
  Last update: 2008-01-29 02:35    [W:0.054 / U:65.648 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site