On September 14, 2005 09:55 am, antgel wrote:
> Jon Roed wrote:
> > I can't find a driver for my chipset in the kernel options. I have an
> > AMD Athlon 64 2800+. The chipset according to the manual that came with
> > the motherboard is a SiS746 Northbridge and SiS963 Southbridge. I can't
> > f
hi ya
On Wed, 14 Sep 2005, Jon Roed wrote:
> I can't find a driver for my chipset in the kernel options.
the chipset you care about is the output of "lspci"
- you'd want to make sure you can find all the drivers
for each of the hardware controllers listed in the output of
Alvin Oga a écrit :
On Wed, 14 Sep 2005, [ISO-8859-1] Aurélien Campéas wrote:
a "mkinitrd for the dummies", riddled with examples, would be neat
but for a costom kernel without initrd, also don't forget to disable
initrd support (in the kernel) (it sits near the RAM fs section)
do you man
Jon Roed a écrit :
I can't find a driver for my chipset in the kernel options. I have an AMD
Athlon 64 2800+. The chipset according to the manual that came with the
motherboard is a SiS746 Northbridge and SiS963 Southbridge. I can't find an
option for either of those. Also, which IDE drive
I can't find a driver for my chipset in the kernel options. I have an AMD
Athlon 64 2800+. The chipset according to the manual that came with the
motherboard is a SiS746 Northbridge and SiS963 Southbridge. I can't find an
option for either of those. Also, which IDE drivers should i make sur
On Wed, 14 Sep 2005, [ISO-8859-1] Aurélien Campéas wrote:
> a "mkinitrd for the dummies", riddled with examples, would be neat
>
> but for a costom kernel without initrd, also don't forget to disable
> initrd support (in the kernel) (it sits near the RAM fs section)
do you man disable or enabl
Alvin Oga a écrit :
On Wed, 14 Sep 2005, [ISO-8859-1] Aurélien Campéas wrote:
VFS: Cannot open root device "301" or unknown block (3,1)
Please append a correct "root= " boot option
kernel panic: not syncing : VFS cannot open root device
i am wondering what to add as a boot option (i am runnin
On Wed, 14 Sep 2005, [ISO-8859-1] Aurélien Campéas wrote:
> > VFS: Cannot open root device "301" or unknown block (3,1)
> > Please append a correct "root= " boot option
> > kernel panic: not syncing : VFS cannot open root device
> >
> > i am wondering what to add as a boot option (i am running L
Jon Roed a écrit :
I have just compiled a new kernel (2.6.13) and i cannot get it too boot. When
i select my new kernel from the boot loader i get the following error:
VFS: Cannot open root device "301" or unknown block (3,1)
Please append a correct "root= " boot option
kernel panic: not synci
On 9/14/05, Nelson Castillo <[EMAIL PROTECTED]> wrote:
> How to find out svga, dma chipset
"lspci -v" and/or "lspci -vv"
I couldn't make out anything from the output for svga or dma. It will be nice if you can be more explicit.
>> and all the cpu flags it uses
>How to know?
cat /proc/cpuinfo
>I got the source from stable(sarge)repository
>which says 2.6.8. But my sarge default kernel
>is 2.6.8-2-386.--
Hi.
I think you should use --initrd unless you
make sure you have all you need to boot
built in (and not as a module).
> How to find out svga, dma chipset
"lspci -v" and/or "lspc
On 9/13/05, Alvin Oga <[EMAIL PROTECTED]> wrote:
- when you build a kernel:- why ??- where did you get the kernel source code from
I got the source from stable(sarge)repository which says 2.6.8. But my sarge default kernel is 2.6.8-2-386.
- where did you get the *.h ( header
On Tue, 13 Sep 2005, Jon Roed wrote:
> > Did you compile your kernel using make-kpkg? Using --initrd or
> > without? Does the /etc/lilo.conf file match your initrd? That is,
> > if you build an initrd did you specify it in yoiur /etc/lilo.conf
> > file? I am guessing not as that would match t
> Did you compile your kernel using make-kpkg? Using --initrd or
> without? Does the /etc/lilo.conf file match your initrd? That is,
> if you build an initrd did you specify it in yoiur /etc/lilo.conf
> file? I am guessing not as that would match the symptoms so far.
>
> Bob
I compiled my kern
Jon Roed wrote:
> I have just compiled a new kernel (2.6.13) and i cannot get it too boot.
> When
> i select my new kernel from the boot loader i get the following error:
>
> VFS: Cannot open root device "301" or unknown block (3,1)
> Please append a correct "root= " boot option
> kernel panic:
On Mon, 2005-09-12 at 21:16 -0500, Jon Roed wrote:
> I have just compiled a new kernel (2.6.13) and i cannot get it too boot.
> When
> i select my new kernel from the boot loader i get the following error:
>
> VFS: Cannot open root device "301" or unknown block (3,1)
> Please append a correct "
I have just compiled a new kernel (2.6.13) and i cannot get it too boot. When
i select my new kernel from the boot loader i get the following error:
VFS: Cannot open root device "301" or unknown block (3,1)
Please append a correct "root= " boot option
kernel panic: not syncing : VFS cannot open
On Tue, Jun 26, 2001 at 03:06:23PM -0500, Dave Sherohman wrote:
> On Tue, Jun 26, 2001 at 10:01:39PM +0200, Joost Kooij wrote:
> > My guess is that your kernel does not know what a "scsi disk" is.
> >
> > Can you grep for CONFIG_BLK_DEV_SD in the config for your kernel (if
> > you used make-kpkg a
On Tue, Jun 26, 2001 at 10:01:39PM +0200, Joost Kooij wrote:
> On Tue, Jun 26, 2001 at 02:07:55PM -0500, Dave Sherohman wrote:
> $ modprobe -c | grep ' block-major-8 '
> alias block-major-8 sd_mod
Both SCSI support and SCSI disk support are built into the kernel, according
to make menuconfig. T
On Tue, Jun 26, 2001 at 02:07:55PM -0500, Dave Sherohman wrote:
> I've got a SCSI-based quad P3 system which starts up just fine off the stock
> 2.2.19pre17 kernel from potato, but refuses to boot the 2.4.5 kernel that
> I've built for it. It dies just after initializing the NET4 subsystem,
> sayi
On Tue, Jun 26, 2001 at 02:07:55PM -0500, Dave Sherohman wrote:
> There's obviously something that I need to include in my kernel, but I've
> double- and triple-checked menuconfig and there's nothing which obviously
> should be required that isn't included. What am I missing?
OK, I guess there's
I've got a SCSI-based quad P3 system which starts up just fine off the stock
2.2.19pre17 kernel from potato, but refuses to boot the 2.4.5 kernel that
I've built for it. It dies just after initializing the NET4 subsystem,
saying:
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
request_module[
Quoting Michael C. Yoon ([EMAIL PROTECTED]):
> Well, I got it to boot by running LILO again. The reason I didn't in
> the first place is because of this line in the installation
> instructions:
>
> "Your new kernel-image-2.0.36 package is also clever enough to
> automatically use lilo to update th
Well, I got it to boot by running LILO again. The reason I didn't in
the first place is because of this line in the installation
instructions:
"Your new kernel-image-2.0.36 package is also clever enough to
automatically use lilo to update the kernel image information allowing
you to boot, so there
Hi,
I just compiled my first custom kernel last night. Now, when I reboot,
my computer freezes after LILO (I assume) prints out "Loading Linux" It
never gets to "Uncompressing kernel"
Originally, I installed Debian 2.1-stable, kernel 2.0.36, from CD.
Then, in order to g
25 matches
Mail list logo
