Prev: 13.1 feature set. No wireless improvement?
Next: Interview with Robby Workman
From: Res on 29 May 2010 20:16
On Sun, 30 May 2010 09:18:04 +1000, Grant wrote:

> On Sat, 29 May 2010 10:34:52 -0400, Paul <pminottawa(a)yahoo.ca> wrote:
>
>>I am trying to compile a leaner kernel than the huge kernel default. I
>>am using kernel 2.6.33.5 (using 2.6.33.4 causes kernel even if I don't
>>boot with the new kernel).
>>
>>I am using the same .config settings that I have used in the past. From
>>the error message I would assume that the problem is with the reiserfs
>>file system, but that should work as configured (it has for years now).
>
> Problem is not due to reiserfs filesystem.
>>
>>I think the problem may be with the SATA drivers.
>
> Yes. The .config needs changes as kernel version jumps, so you can't
> rely on a .config from too many versions behind latest kernel. Did you
> run: 'make oldconfig; make menuconfig' after copying old .config to
> kernel source tree?

It is not entirely true that when copying .config one needs to run
oldconfig, I stopped doing that years ago, when it was clear it wasn't
needed, and I've done that on private and all production
boxes for a very, very long time now.

Cheers

--
/home/noel/.pan2/.sig1
From: Grant on 29 May 2010 22:25
On Sat, 29 May 2010 19:16:27 -0500, Res <res(a)ausics.net> wrote:

>On Sun, 30 May 2010 09:18:04 +1000, Grant wrote:
>
>> On Sat, 29 May 2010 10:34:52 -0400, Paul <pminottawa(a)yahoo.ca> wrote:
>>
>>>I am trying to compile a leaner kernel than the huge kernel default. I
>>>am using kernel 2.6.33.5 (using 2.6.33.4 causes kernel even if I don't
>>>boot with the new kernel).
>>>
>>>I am using the same .config settings that I have used in the past. From
>>>the error message I would assume that the problem is with the reiserfs
>>>file system, but that should work as configured (it has for years now).
>>
>> Problem is not due to reiserfs filesystem.
>>>
>>>I think the problem may be with the SATA drivers.
>>
>> Yes. The .config needs changes as kernel version jumps, so you can't
>> rely on a .config from too many versions behind latest kernel. Did you
>> run: 'make oldconfig; make menuconfig' after copying old .config to
>> kernel source tree?
>
>It is not entirely true that when copying .config one needs to run
>oldconfig, I stopped doing that years ago, when it was clear it wasn't
>needed, and I've done that on private and all production
>boxes for a very, very long time now.

Does the 'make' ask for the new options present in a later kernel?

I do this stuff on auto-pilot ;) I don't use oldconfig when updating
-stable within a release, only when bringing an old .config to a new
release kernel. Old habits...

Grant.
--
http://bugs.id.au/
From: Thomas Overgaard on 1 Jun 2010 10:09
Paul wrote:

> I think the problem may be with the SATA drivers.
>
Just had the same issue, looks like Slackware 13.1 64-bit isn't to happy
about being installed at the second SATA drive.

Got around it this time by pressing the <TAB> key at the boot screen and
wrote:
Linux raid=noautodetect

I've added this line to /etc/lilo.conf and hopes it helps:
append="raid=noautodetect"
--
Thomas O.

This area is designed to become quite warm during normal operation.
From: Thomas Overgaard on 2 Jun 2010 14:48
Thomas Overgaard wrote:

> I've added this line to /etc/lilo.conf and hopes it helps:
> append="raid=noautodetect"

And then LILO decided that the drive was /dev/sdf, I had to rearrange
cables at the MOBO to get it going.
--
Thomas O.

This area is designed to become quite warm during normal operation.
First  |  Prev  | 
Pages: 1 2
Prev: 13.1 feature set. No wireless improvement?
Next: Interview with Robby Workman