Hi!
I have a somewhat strange problem at home. Lately, I decided to
finally update my kernel from 2.4.27 to 2.6.18 (actually now it
would be 2.6.21, but when I tried it was 2.6.18). I installed the
source package, compiled the kernel as I used to with the previous
one (didn't change much the confi
On 8/3/07, Brad Sawatzky <[EMAIL PROTECTED]> wrote:
>
> Perhaps I misunderstood, but I thought he got the errors with the old
> kernel (and had for a long time) but they did not trigger a filesystem
> check. My hunch was that the 2.6.x IDE driver (or ext3 driver) is handling
> the error condition
On 8/3/07, Brad Sawatzky <[EMAIL PROTECTED]> wrote:
> Hi Francois,
>
> I agree with Doug: CRC errors shouldn't be ignored. At _best_ they are a
> sign that something in your system is marginal. At worst you end up
> reading and/or writing bogus data. The fact that the errors persisted
> after y
On 8/4/07, Francois Duranleau <[EMAIL PROTECTED]> wrote:
> On 8/3/07, Brad Sawatzky <[EMAIL PROTECTED]> wrote:
> > Hi Francois,
> >
> > I agree with Doug: CRC errors shouldn't be ignored. At _best_ they are a
> > sign that something in your system i
On 8/4/07, Wayne Topa <[EMAIL PROTECTED]> wrote:
>
> I also have the ABIT KT7 and it has gone from kernels 2.4.27 ->
> 2.6.18-4 with no CRC errors showing up at all. It's only been running
> for 5-6 years. CPU Fan has been changed twice but other then that,
> its fine.
I have mine since december
Some updates: recompiled the kernels without the VIA driver (actually,
compiled as a module but not loaded).
With 2.4.27, I don't have the CRC errors anymore, though I can't get
DMA to work (is because I load the generic PCI driver afterwards?).
With 2.6.18, I get this:
VFS: Cannot open root dev
Hi!
Trying to upgrade to kernel 2.6 (actually, 2.6.18) from 2.4.27, when I
boot my system with 2.6, I get the following error:
VFS: Cannot open root device "hda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
On 8/24/07, Douglas A. Tutty <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 23, 2007 at 09:49:52PM -0400, Francois Duranleau wrote:
> >
> > Trying to upgrade to kernel 2.6 (actually, 2.6.18) from 2.4.27, when I
> > boot my system with 2.6, I get the following error:
> >
On 8/24/07, Wayne Topa <[EMAIL PROTECTED]> wrote:
> Francois Duranleau([EMAIL PROTECTED]) is reported to have said:
[snip]
> > It's an old system: AMD Athlon Thunderbird 1.1GHz with 1.25GB RAM and
> > an 80GB Western Digital drive, for sur not SATA, I bought this
> >
On 8/25/07, Wayne Topa <[EMAIL PROTECTED]> wrote:
> Francois
>
> Just looked at the config file you listed for the 2.1.18 kernel.
> It looks different then mine in the Block Device section.
>
> # Block devices
> #
> CONFIG_BLK_DEV_FD=m
> # CONFIG_BLK_DEV_XD is not set
> # CONFIG_PARIDE is not set
>
On 8/24/07, Bert Schulze <[EMAIL PROTECTED]> wrote:
> Hi
>
> I took a look at your config and menu.lst
> So whats missing seems to be an initrd image which holds all the
> modules your kernel needs. Your config uses some of em. You should
> build the initrd
> mkinitramfs -o /boot/initrd.img-2.6.1
On 8/27/07, Jeff D <[EMAIL PROTECTED]> wrote:
>
> One thing that kinda stands out to me in the 2.6 config are:
> CONFIG_IDE_GENERIC=m
> CONFIG_BLK_DEV_VIA82CXXX=m
>
> I'd change those to be compiled in rather than modules.
Yes. There were set as modules for some experiments regarding
CRC errors (s
On 8/27/07, Francois Duranleau <[EMAIL PROTECTED]> wrote:
> On 8/24/07, Bert Schulze <[EMAIL PROTECTED]> wrote:
> > Hi
> >
> > I took a look at your config and menu.lst
> > So whats missing seems to be an initrd image which holds all the
> > modules y
On 8/28/07, Richard Thompson <[EMAIL PROTECTED]> wrote:
>
> I don't get why your building you own intird?, if your using the kernel
> provided it already has it's own initrd and if your building the kernel
> yourself why are you using initrd at all?
Good question. I am building my own kernel (usin
14 matches
Mail list logo
