Sybren Stuvel wrote:
> Alessandro Gabriele Isidoro Lo-Presti enlightened us with:
>
>>Yes, I'm 100% sure I have proper support for my IDE chipset. I've
>>used this kernel configuration since 2.6.5.
>
>
> My point was: kernel configuration options change. If you're only sure
> because it worked in previous versions, you're *not* sure.

First of all, I ran the 2.6.7 kernel fine, for about a week.
After I then re-compiled with the current and working 2.6.7
configuration, minus the 'rivafb' module, it gave me that error.

Otherwise, how can I be sure?
I have no idea what to do next because I have nothing to work with.
The error message itself is vague as it is, because hda3 is my root fs. :\

>
>>And, yeah, I was wondering that myself, but it's teh only thing that
>>seems off.
>
>
> What are you referring to? You're top-posting, which makes it very
> difficult to keep track of what you are replying to. Next time, remove
> the unwanted quited text, and reply in-line, as I'm doing now.

I'm referring to the fact that the only thing that seems off that could
possibly cause this (after a day of trouble-shooting and kernel
switches), is the disk boundary being off.
I don't know what else it could be.

>
>>I've checked to see if deleting it and re-adding the swap partition
>>would correct that error, and it did.
>
>
> Ok, that's good.
>
>
>>Though I have not yet written the partition table to the harddisk
>
>
> Then how can you be certain it corrected the error? You must be
> talking about a different error than the kernel panic, which is the
> subject of this entire thread. Wat are you talking about?

I'm talking about me trying to fix the disk boundary, because I thought
that was causing the kernel panic.
After I deleted the swap partition, and re-added it, I checked with 'p',
to print out the current partition table.
And the error message was gone after doing so.
But I didn't actually write to the disk yet.

>
>>because I'm not too convinced it won't touch the rest of the harddisk
>>(will it?).
>
>
> Don't know. You haven't told us *exactly* what you did, so how can we
> answer?
>
> Please, next time, think about the way you post. Many people don't
> think about this and put their reply at the top of their post, quoting
> all of the original post below it. Now take a look at this:
>
> {...}

Okay, okay, I understand, I'm sorry.
I'm doing it the way it's preferred, look. ^



So, what could it possibly be?
I've tried configuring the kernel from the grounds up, without importing
the old configuration file.
I've tried a LOT of kernel switches, and rebooted a few dozen times.
All to no avail.


Regards,
Alessandro Lo-Presti