Everyone,
Thank you for your help and suggestions. I was able to add
rootdelay=5 to the kernel line and this resolved the issue for me.
Sincerely.
Shane
On Mon, Sep 30, 2013 at 8:51 AM, Chris Bannister
wrote:
> On Mon, Sep 30, 2013 at 05:16:38PM +0300, Georgi Naplatanov wrote:
>> I had impressi
Shane Johnson, 28.09.2013:
> I have been fighting this all night and was wondering if anyone else
> has been having problems as well?
>
> I am doing a new install via debootstrap to a lvm2 volume via the
> wheezy rescue disk.
>
> I got it running in wheezy then went to jessie and while I was runn
On Mon, Sep 30, 2013 at 05:16:38PM +0300, Georgi Naplatanov wrote:
> I had impression that 'rootdelay=5' had solved your problem and that
> is why I gave you that link.
If you read the thread, you will see it was not me. Also note, it was
another poster (Hugo) who suggested that the OP try 'rootde
Georgi Naplatanov wrote:
On 09/30/2013 02:03 AM, Hugo Vanwoerkom wrote:
Georgi Naplatanov wrote:
On 09/29/2013 05:24 PM, Chris Bannister wrote:
On Sat, Sep 28, 2013 at 11:52:00AM -0500, Hugo Vanwoerkom wrote:
Shane Johnson wrote:
I have been fighting this all night and was wondering if any
On 09/30/2013 04:31 PM, Chris Bannister wrote:
On Mon, Sep 30, 2013 at 02:57:54AM +0300, Georgi Naplatanov wrote:
On 09/30/2013 02:03 AM, Hugo Vanwoerkom wrote:
Georgi Naplatanov wrote:
On 09/29/2013 05:24 PM, Chris Bannister wrote:
On Sat, Sep 28, 2013 at 11:52:00AM -0500, Hugo Vanwoerkom
On Mon, Sep 30, 2013 at 02:57:54AM +0300, Georgi Naplatanov wrote:
> On 09/30/2013 02:03 AM, Hugo Vanwoerkom wrote:
> >Georgi Naplatanov wrote:
> >>On 09/29/2013 05:24 PM, Chris Bannister wrote:
> >>>On Sat, Sep 28, 2013 at 11:52:00AM -0500, Hugo Vanwoerkom wrote:
>
> add 'rootdelay=5'(w/o
On 09/30/2013 02:03 AM, Hugo Vanwoerkom wrote:
Georgi Naplatanov wrote:
On 09/29/2013 05:24 PM, Chris Bannister wrote:
On Sat, Sep 28, 2013 at 11:52:00AM -0500, Hugo Vanwoerkom wrote:
Shane Johnson wrote:
I have been fighting this all night and was wondering if anyone else
has been having p
Georgi Naplatanov wrote:
On 09/29/2013 05:24 PM, Chris Bannister wrote:
On Sat, Sep 28, 2013 at 11:52:00AM -0500, Hugo Vanwoerkom wrote:
Shane Johnson wrote:
I have been fighting this all night and was wondering if anyone else
has been having problems as well?
I am doing a new install via deb
On 09/29/2013 05:24 PM, Chris Bannister wrote:
On Sat, Sep 28, 2013 at 11:52:00AM -0500, Hugo Vanwoerkom wrote:
Shane Johnson wrote:
I have been fighting this all night and was wondering if anyone else
has been having problems as well?
I am doing a new install via debootstrap to a lvm2 volume
On Sat, Sep 28, 2013 at 11:52:00AM -0500, Hugo Vanwoerkom wrote:
> Shane Johnson wrote:
> >I have been fighting this all night and was wondering if anyone else
> >has been having problems as well?
> >
> >I am doing a new install via debootstrap to a lvm2 volume via the
> >wheezy rescue disk.
> >
>
Shane Johnson wrote:
I have been fighting this all night and was wondering if anyone else
has been having problems as well?
I am doing a new install via debootstrap to a lvm2 volume via the
wheezy rescue disk.
I got it running in wheezy then went to jessie and while I was running
the 3.2 kernel
On Sun, 03 Jun 2012 21:35:12 +0100, dobrima...@yahoo.pl wrote:
(please, no html formatted posts, thanks :-) )
> Hello, I have a problem with patching kernel 2.6-2.6.32.
>
> I'm trying to add PVUSB [1] support in Xen. According to [1] I should
> add a patch [2] to kernel. I was trying to do it wi
Scott Berry:
>
> I am using the kernel in my subject. It seems as though this kernel
> likes to lock up quite a bit when the CPu fan is at a higher rate of
> speed due to other tasks being done in the background. I am using Lenny
> and I never can remember before Debian being this unstable.
Sou
I have solved my problem. I installed fakeroot, then modified ~/.kernel-pkg.conf to use it (1). Kernel compiles successfully, and .debs are generated in the parent directory ("~/src" in my case.) I installed the linux-image .deb on the target machine successfully as well.
(1) I added a line: "ro
On (22/06/06 21:07), Kit Peters wrote:
> On 6/22/06, James Westby <[EMAIL PROTECTED]> wrote:
> >It is oft recommended to use fakeroot rather that a real root command
> >for compiling.
> Hm. I've never used fakeroot for anything. How would I compile a kernel in
> fakeroot?
aptitude install fakeroo
On 6/22/06, James Westby <[EMAIL PROTECTED]> wrote:
> I have configured the kernel via menuconfig. Kernel sources are at> $HOME/src/linux-2.6.17.1/. I execute 'CC=gcc-4.1 make-kpkg --pgpsign>
[EMAIL PROTECTED]> --rootcmd sudo --revision 1.0 --append-to-version "-pt5500" buildpackage'.It is oft r
On (22/06/06 20:42), Kit Peters wrote:
> I'm trying to compile kernel 2.6.17.1 from the vanilla sources at
> kernel.org.
> As this kernel is for a specific machine, I want to append a note to the
> kernel version to reflect that fact. Normally, I would do this from within
> $KERNEL_SOURCE_DIR/.co
On Thu, Jun 17, 2004 at 01:13:56AM -0800, Scott A. Henderson wrote:
> The following is how I compiled the kernel
>
>* tar jxf kernel-source-2.4.18.tar.bz2
>* ln -s /usr/src/kernel-source-2.4.18 linux
>* cd /usr/src/linux
>* cp /boot/config-2.4.18-bf2.4 ./.config
>* make-kpkg cl
The following is how I compiled the kernel
tar jxf kernel-source-2.4.18.tar.bz2
ln -s /usr/src/kernel-source-2.4.18 linux
cd /usr/src/linux
cp /boot/config-2.4.18-bf2.4 ./.config
make-kpkg clean
make-kpkg --config menuconfig kernel_image
I understand a little about
On Wednesday 16 June 2004 09:19 pm, Scott A. Henderson wrote:
> If I follow this you removed the initrd support from the "Block Devices"
> menu option. The default configuration is to have this "built-in"
>
> I am not sure I understand the second part o this referring to IDE and
> ext3 those from
If I follow this you removed the initrd support from the "Block
Devices" menu option. The default configuration is to have this
"built-in"
I am not sure I understand the second part o this referring to IDE and
ext3 those from what I can tell are part of the configuration already.
Can you cla
On Wed, Jun 16, 2004 at 01:39:54PM -0800, Scott A. Henderson wrote:
> I have have a problem with booting the kernel 2.4.25 and later on recent
> hardware I purchased
>
> The initial installation is a basic bf24 install no options were
> selected, I just followed the menus through the system. I
Upgrading alsa-modules caused an upgrade to kernel-image-2.4.16. I now boot
the 2.4.16 but have no access to net. ifconfig does not show eth0, and an
modprobe rtl* is installing an USB module and not the ethernet module. I
fallback on 2.2.20 which seem to have a net/ dir in
/lib/modules/2.2.20-
Jaroslaw Tabor <[EMAIL PROTECTED]> wrote:
>
>I was using kernel 2.4.20 compiled and installed by myself (without
> initrd). Everything was working fine.
> I've installed by apt kernel-image-2.4.20-686, updated lilo.conf to use
> initrd and executed lilo. After this when I'm trying to use t
"Jaroslaw" == Jaroslaw Tabor <[EMAIL PROTECTED]> writes:
Jaroslaw> Hello! I was using kernel 2.4.20 compiled and installed
Jaroslaw> by myself (without initrd). Everything was working fine.
Jaroslaw> I've installed by apt kernel-image-2.4.20-686, updated
Jaroslaw> lilo.conf to
Hi there,
check my earlier mails about this issue. :-)
Harry
--On Wednesday, February 26, 2003 03:56:30 PM + Jaroslaw Tabor
<[EMAIL PROTECTED]> wrote:
I was using kernel 2.4.20 compiled and installed by myself (without
initrd). Everything was working fine.
I've installed by apt kern
> From: Jaroslaw Tabor, Sent: Wednesday, February 26, 2003 10:11 AM
>
> Hello!
>
Hello!
>
> I was using kernel 2.4.20 compiled and installed by
> myself (without
> initrd). Everything was working fine.
> I've installed by apt kernel-image-2.4.20-686, updated
> lilo.conf to use
> initr
Hi there again,
--On Wednesday, February 26, 2003 07:44:48 PM +1100 Herbert Xu
<[EMAIL PROTECTED]> wrote:
On Wed, Feb 26, 2003 at 09:27:17AM +0100, Harry Brueckner wrote:
My initrd-tools are version 0.1.37 which seems to be the most current
version.
Any other ideas?
If you go to packages.debian.
On Wed, Feb 26, 2003 at 09:27:17AM +0100, Harry Brueckner wrote:
>
> My initrd-tools are version 0.1.37 which seems to be the most current
> version.
>
> Any other ideas?
If you go to packages.debian.org/initrd-tools you'll find that the
latest version is 0.1.38.
--
Debian GNU/Linux 3.0 is out
Hi there,
--On Wednesday, February 26, 2003 07:46:33 AM +1100 Herbert Xu
<[EMAIL PROTECTED]> wrote:
Any idea what could be wrong? I found several postings about this
problem but not a single useful reply to them. :-/
Upgrade your initrd-tools package and reinstall kernel-image.
I removed the pa
Harry Brueckner , Harry Brueckner <[EMAIL PROTECTED]> wrote:
>
> Any idea what could be wrong? I found several postings about this problem
> but not a single useful reply to them. :-/
Upgrade your initrd-tools package and reinstall kernel-image.
--
Debian GNU/Linux 3.0 is out! ( http://www.deb
On Fri, 2002-05-24 at 18:58, Petro wrote:
> On Fri, May 24, 2002 at 09:50:29AM -0500, Ken Causey wrote:
> > > On 05/24 05:07 Ken Causey wrote:
> > > > VFS: Cannot open root device "802" or 08:02
> > > > Please append a correct "root=" boot option
> > > > Kernel panic: VFS: Unable to mount root fs o
On Fri, May 24, 2002 at 09:47:52AM -0500, Ken Causey wrote:
> > Well, it makes sense to make the kernel executable, but
> > that doesn't seem to be the problem as the kernel seems to be
> > executing already (all that output is from the kernel, I think).
> >
> > It all looks normal until the end, w
> On 05/24 05:07 Ken Causey wrote:
> > ...
> > VFS: Cannot open root device "802" or 08:02
> > Please append a correct "root=" boot option
> > Kernel panic: VFS: Unable to mount root fs on 08:02
> >
> > I have a single SCSI drive (2 partitions, first is swap, second is
> root)
> > connected via a
> Well, it makes sense to make the kernel executable, but
> that doesn't seem to be the problem as the kernel seems to be
> executing already (all that output is from the kernel, I think).
>
> It all looks normal until the end, when the kernel can't mount>
> the root partition. You say you have a
>From /boot/config-2.4.18-686-smp
CONFIG_SCSI=m
CONFIG_SCSI_AIC7XXX=m
Should provide what's necessary for Adaptec 29160 no?
Ken
On Thu, 2002-05-23 at 23:16, Greg Madden wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Read the /boot/config-kernel-image-xxx file and see what scsi
On Thu, 2002-05-23 at 17:45, Robert Webb wrote:
> I am new to Linux but doesn't your /boot/initrd.img-2.4.18-686-smp file
> need to be -rwxr-xr-x
>
> This is the way mine is
>
My first inclination was to say "No." My second inclination was to give
it a try. Thanks for the suggestion but
On 05/24 05:07 Ken Causey wrote:
...
VFS: Cannot open root device "802" or 08:02
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 08:02
I have a single SCSI drive (2 partitions, first is swap, second is root)
connected via an Adaptec 29160.
I didn't see
Well, it makes sense to make the kernel executable, but
that doesn't seem to be the problem as the kernel seems to be
executing already (all that output is from the kernel, I think).
It all looks normal until the end, when the kernel can't mount
the root partition. You say you have a SCSI disk,
I am new to Linux but doesn't your /boot/initrd.img-2.4.18-686-smp file
need to be -rwxr-xr-x
This is the way mine is
Ken Causey wrote:
I'm running into trouble trying to boot using
kernel-image-2.4.18-686-smp_2.4.18-5_i386 from testing,
Linux version 2.4.18-686-smp ([EMAIL PROTECTED])
* Daniel Pecos ([EMAIL PROTECTED]) spake thusly:
> Hello!
>
> Time ago I compiled the 2.4.16 kernel version without any
> problem, but some days ago I had to modify the configuration
> and tried to recompile it. This is the output:
>
> (linking the kernel)...
>
I always set version info on all modules, which allows you to use old or
non-kernel modules with a new kernel. As a bit of housekeeping I also
rename the Debian modules dir before I "make modules modules_install".
Don't forget to clean out /etc/modules to stop the system trying to load
non-existant
"Aeschlimann Marc" <[EMAIL PROTECTED]> writes:
> I compiled my new kernel (2.2.17) with kernel-package. After that I
> tried the command depmod, the result was : Unresolved symbols in
> /lib/modules/2.2.17/xxx/xxx.o What is the problem ?
Did you have modules lying around in /lib/modules/2.2.1
"Aeschlimann Marc" <[EMAIL PROTECTED]> writes:
> I compiled my new kernel (2.2.17) with kernel-package. After that I
> tried the command depmod, the result was : Unresolved symbols in
> /lib/modules/2.2.17/xxx/xxx.o What is the problem ?
Did you have modules lying around in /lib/modules/2.2.17 be
This is a bug in the Configure script of the kernel package that has
been brought to the fore by the POSIXness of binutils/bash, as you
suspected.
The fix is to escape the POSIXly reserved characters in the script that
are used in 'expr' commands. The one you are tripping on checks for a
valid hex
45 matches
Mail list logo
