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
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 your kernel needs. Your config uses some of em. Y
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 Mon, 27 Aug 2007, Francois Duranleau wrote:
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
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
>
Francois Duranleau([EMAIL PROTECTED]) is reported to have said:
> 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
Francois Duranleau([EMAIL PROTECTED]) is reported to have said:
> 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
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
> > computer in december 2000. The
Francois Duranleau([EMAIL PROTECTED]) is reported to have said:
> On 8/24/07, Douglas A. Tutty <[EMAIL PROTECTED]> wrote:
> > On Thu, Aug 23, 2007 at 09:49:52PM -0400, Francois Duranleau wrote:
> > >
<>
> > Is the disk really a PATA or is it SATA? 2.4 kernels will see them as
> > /dev/hd* wher
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:
> >
> > VFS: Cannot open root device "
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:
>
> VFS: Cannot open root device "hda1" or unknown-block(0,0)
> Please append a correct "root=" boot
On 24 Aug., 04:00, "Francois Duranleau" <[EMAIL PROTECTED]>
wrote:
> 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=" b
Interesting that I think I might have found the real source of my build
problem.
I was able to retain a config file from a working 2.6.8 kernel build,
and used it as the basis of my further builds by loading that config
file while in "make config" mode. I then recompiled a new kernel,
adding onl
Ok. This is now starting to seriously irritate me. I can no longer
build kernels anymore. Even blowing away the source tree directory and
re-expanding the tarball gets me nowhere. Thankfully I retained a
"safe" kernel which boots (but doesn't give me the functionality I'm
after, namely Macinto
Andrea, Alvin, and Reiner (and the rest of Debian-User):
Thank you for your assistance. It turns out that there was something
scrod in my source tree. After multiple attempts (including a "make
mrproper") I finally blew away the source directory and re-extracted
from the tarball.
My builds hav
lspci reports I'm using the Sym53C859 (which agrees with the POST
messages my SCSI controller gives me...).
However, I still can not seem to boot anything other than the
2.2.20-compact-ide Debian 3.0 kernel. I am going to attempt to pull my
lilo.conf and .config file to post.
On Thu, 2004-12-30
On Thu, 30 Dec 2004 00:01:15 -0800, Eric N. Valor <[EMAIL PROTECTED]> wrote:
>
> I don't know because I'm not using the Debian image (I like to compile
> my own kernels, and have only started running into these problems using
> 2.6.x kernels). Does the Debian 2.6.8 binary image contain support fo
On Thu, 30 Dec 2004, Eric N. Valor wrote:
> I don't know because I'm not using the Debian image (I like to compile
> my own kernels, and have only started running into these problems using
> 2.6.x kernels). Does the Debian 2.6.8 binary image contain support for
> the Sym53C8XXX SCSI controller?
Hi,
Am Mittwoch, den 29.12.2004, 12:45 -0800 schrieb Eric N. Valor:
> The only change I
> made was to enable HFS filesystem (so I can play with my new iPod).
This is no solution for your problem, but maybe a useful workaround:
I work for a company that uses Macs, and we all got an iPod for
chris
I don't know because I'm not using the Debian image (I like to compile
my own kernels, and have only started running into these problems using
2.6.x kernels). Does the Debian 2.6.8 binary image contain support for
the Sym53C8XXX SCSI controller?
Beyond this problem with HFS, I'm concerned that a
On Wed, 29 Dec 2004 12:45:27 -0800, Eric N. Valor <[EMAIL PROTECTED]> wrote:
>
> Hello.
>
> I recently recompiled my 2.6.8 kernel. Now I can no longer boot my
> system. It fails with the message "cannot open root device "801" or
> unknown-block(8,1)".
>
> I am using a Symbios SCSI card without
Hello
JAMES MERRITT (<[EMAIL PROTECTED]>) wrote:
> I tried typing linux root=/dev/hdb1 at the lilo prompt and it says
> something about that not being one of the choices.
Try "Linux root=/dev/hdb1" (note the capital letter).
> The lilo menu I see is:
> Linux WinNT (hda1)
> WinNT or DOS (hdb6) <
: Fri, 23 Jan 2004 17:18:14 -0600
To: [EMAIL PROTECTED]
Subject: Re: Cannot Open Root Device - Was: Unidentified subject!
> JAMES MERRITT wrote:
>
>
> >I am having a little problem with my Debian Woody. The other day when I tried to
> >boot into Woody,
> >it started
Hello
JAMES MERRITT (<[EMAIL PROTECTED]>) wrote:
> Also to Andreas, I am sorry I responded to your response and my email
> package uses the poster, not the newsgroup, as it's TO: address. I
> try never to respond directly unless the poster requests it. Also, by
> responding back to the newsgrou
JAMES MERRITT wrote:
I am having a little problem with my Debian Woody. The other day when I tried to boot into Woody,
it started the normal text bootup screen before it goes into to KDE graphical login screen.
But, during the text portion of the boot up process, it stopped and gave this messa
Hi,
Hi Kent, sorry for not using a meaningful subject, often time I overlook those emails
without a useful subject myself, never know what you will get with all these crazy
viruses, etc. going around...smile. I hit SEND before checking my email more
carefully.
Also to Andreas, I am sorry I re
Petteri Heinonen wrote:
> I've compiled kernel (2.2.15), succesfully. But when I try to boot with it,
> I get message during boot:
>
> VFS: cannot open root device 03:02
> Kernel Panic: VFS: Unable to mount root fs on 03:02
Do run 'lilo' after installing the new kernel?
Rüdiger
27 matches
Mail list logo
