ude <...> search starts here:
/usr/lib/gcc/x86_64-unknown-linux-gnu/4.7.2/include
/usr/local/include
/usr/lib/gcc/x86_64-unknown-linux-gnu/4.7.2/include-fixed
/usr/include
root:/sources/gcc-build:$ grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'
SEARCH_DIR("
Armin K. email.com> writes:
>
> On 07/19/2013 01:54 AM, Kevin Abraham wrote:
> > Hello,
> >
> > When I boot my LFS 7.3 system, I get a "VFS: Cannot open root device
> > "/dev/sda4" or unknown-block(0,0)" error. I have traced the problem do
On Jul 18, 2013, at 18:54, Kevin Abraham wrote:
> What would the right driver be?
Perhaps AHCI?
Sincerely,
William Harrington
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
On 07/19/2013 01:54 AM, Kevin Abraham wrote:
> Hello,
>
> When I boot my LFS 7.3 system, I get a "VFS: Cannot open root device
> "/dev/sda4" or unknown-block(0,0)" error. I have traced the problem down
> to a driver missing from the kernel, but can't
Hello,
When I boot my LFS 7.3 system, I get a "VFS: Cannot open root device
"/dev/sda4" or unknown-block(0,0)" error. I have traced the problem down to a
driver missing from the kernel, but can't figure out which one. I have tried
the SATA_NV driver and the SATA_SIL
On Wed, 2013-04-10 at 17:15 -0500, William Harrington wrote:
*snip*
> > What went wrong in my build of coreutils?
> >
>
> This has been reported a bug a while ago:
> http://lists.gnu.org/archive/html/bug-coreutils/2012-11/msg00172.html
>
> Sincerely,
>
> William Harrington
>
Ah, thanks, OK -
On Apr 10, 2013, at 4:45 PM, Alice Wonder wrote:
> Hi, lfs 7.3
>
> uname -i and uname -p both return "unknown" which is causing some
> issues
> on software I'm trying to build.
>
> On other distributions - that return x86_64
>
> uname -m however do
Hi, lfs 7.3
uname -i and uname -p both return "unknown" which is causing some issues
on software I'm trying to build.
On other distributions - that return x86_64
uname -m however does return x86_64
What went wrong in my build of coreutils?
--
http://linuxfromscratch.org/mailm
On Dec 26, 2012, at 2:09 AM, JIA Pei wrote:
Kernel panic - not syncing: VFS: unable to mount root fs on unknown
block(0,0)
http://www.linuxfromscratch.org/lfs/faq.html#unable-to-mount-root
0,0 means no block devices were detected which means:
1) No hard drive controller enabled in the
Hi, all:
Sorry that I started another new topic. BTW, thanks Bruce, thank you for
your answer to my former question, which makes me much clearer already.
However, I still keeps receiving the following error message.
*Kernel panic - not syncing: VFS: unable to mount root fs on unknown
block(0,0
, mostly cosmetic, but, That
"MACHTYPE=x86_64-unknown-linux-gnu" keeps sneeking into the build, and I
was looking for it while building, but it still got by me. First place
found was a reference in BASH thru the SET command.
Where does that 'default' get injected into the bu
From: "Michael"
To: "LFS Support List"
Sent: Friday, November 11, 2011 2:26:55 PM
Subject: Re: Kernel panic - not syncing: VFS; Unable to mount root fs on
unknown-block(2.0)
Am Freitag 11 November 2011 20:11:05 schrieb Danny Vukobratovich:
> I saw this thread tha
Am Freitag 11 November 2011 20:11:05 schrieb Danny Vukobratovich:
> I saw this thread that I thought was related but is addressing the issue in
> LFS 6.6
>
> http://www.linuxfromscratch.org/pipermail/lfs-support/2010-April/038457.htm
> l
>
> I'm setting up LFS 7.0. I am doing this in a VMworkstat
I saw this thread that I thought was related but is addressing the issue in LFS
6.6
http://www.linuxfromscratch.org/pipermail/lfs-support/2010-April/038457.html
I'm setting up LFS 7.0. I am doing this in a VMworkstation 8 environment with
the GRML Live CD as my host. The default setup for the
Tony Hartzell wrote:
> VFS: Cannot open root device "hda2" or unknown-block(2,0)
> Please append a correct "root=" boot option; here are the available
> partitions:
> Kernel panic - not syncing: VFS: unable to mount root fs on
> unknown-block(2,0)
Usually a res
On Sun, 17 Jul 2011 17:08:18 -0700
Tony Hartzell wrote:
> The kernel command line is in grub.cfg (attached - as is the lspci listing)
> I know my post was sparse...I've tried several different approaches, and I
> tend to go in several different directions at once, when I explain what I've
> tried
Tony Hartzell wrote:
> The kernel command line is in grub.cfg (attached - as is the lspci listing)
It's easier with just the appropriate info, e.g.:
menuentry "GNU/Linux, with Linux 2.6.37-lfs-6.8" --class gnu-linux
--class gnu --class os {
insmod ext2
set root=/dev/hda2
ernel panic) that they'd "Oh, silly boy, you forgot
to..."
Thanks,
Tony Hartzell
On Sun, Jul 17, 2011 at 3:44 PM, Bruce Dubbs wrote:
> Tony Hartzell wrote:
> > VFS: Cannot open root device "hda2" or unknown-block(2,0)
> > Please append a correct "r
Tony Hartzell wrote:
> VFS: Cannot open root device "hda2" or unknown-block(2,0)
> Please append a correct "root=" boot option; here are the available
> partitions:
> Kernel panic - not syncing: VFS: unable to mount root fs on
> unknown-block(2,0)
>
> I
VFS: Cannot open root device "hda2" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available
partitions:
Kernel panic - not syncing: VFS: unable to mount root fs on
unknown-block(2,0)
I think my problem is that /dev isn't being populated.
d
> this, so I'm certainly using the correct partition
>
> grub> boot ... produces some sweet whirring and then:
>
> VFS: cannot open a root device "(null)" or unknown block
> Please append a correct "root=" boot option
> ...
> Kernel panic -
oduces some sweet whirring and then:
VFS: cannot open a root device "(null)" or unknown block
Please append a correct "root=" boot option
...
Kernel panic - not syncing VFS: Unable to mount root fs on unknown block
then solid halt ...
--
http://linuxfromscratch.org/m
: /boot/vmlinuz-2.6.32-26-generic
Found initrd image: /boot/initrd.img-2.6.32-26-generic
Found memtest86+ image: /boot/memtest86+.bin
Found unknown Linux distribution on /dev/sdb4
/etc/grub.d/README: 2: All: not found
/etc/grub.d/README: 4: 00_*:: not found
/etc/grub.d/README: 5: 10_*:: not found
/et
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
mas...@mail.com wrote:
> LFS system dmesg | grep IDE:
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> PIIX4: IDE controller at PCI slot :00:07.1
> Probing IDE interface ide0...
> Probing IDE interface ide1...
> hdc: VMware Virtual IDE CDROM Drive, ATAPI CD/DVD-ROM drive
> target0
Hi i tried installing a huge bunch of unnecessary drivers and stuff
into the kernel to see if it would get me through the problem.
Now i get VFS: Cannot open device "" or unknown-block(8.2)
Please append a correct "root=" boot option; here are the availab
ernel and took every driver for SATA and SCSI just to
> be sure that wont be an issue.
*snip*
> Kernel panic - not syncing: VFS; Unable to mount root fs on
> unknown-block(2.0)
> VFS: Cannot open root device "sda2" or unknown-block(2.0)
*snip*
> linux /vmlinux-2
ologies Inc RS690 PCI to PCI Bridge
(Internal gfx)
00:04.0 PCI bridge: ATI Technologies Inc Unknown device 7914
00:05.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI
Express Port 1)
00:06.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI
Express Port 2)
00:12.0 SA
### END /etc/grub.d/10_linux ###
>
> ### BEGIN /etc/grub.d/30_os-prober ###
> ### END /etc/grub.d/30_os-prober ###
>
> ### BEGIN /etc/grub.d/40_custom ###
> # This file provides an easy way to add custom menu entries. Simply
> type the
> # menu entries you want to add after
FS, but I
agree that it would be clearer if they were removed. Otherwise, the
entry looks correct.
>> Kernel panic - not syncing: VFS; Unable to mount root fs on
>> unknown-block(2.0)
>> VFS: Cannot open root device "sda2" or unknown-block(2.0)
> My guess is that you
ode)" {
> insmod ext2
> set root=(hd0,1)
> search --no-floppy --fs-uuid --set
> dd263110-8c28-48f1-bb0e-5c779c97e9ac
Are these search lines needed? I don't put them in my grub.cfg
> when i reboot i get:
> Kernel panic - not syncing: VFS; Un
tail' line above.
### END /etc/grub.d/40_custom ###
i set the grub MBR to /dev/sda
when i reboot i get:
Kernel panic - not syncing: VFS; Unable to mount root fs on
unknown-block(2.0)
VFS: Cannot open root device "sda2" or unknown-block(2.0)
Please append a correct "root="
which will be useful for someone who use VMware
to build LFS.
AjSi
> Subject: Re: VFS: Cannot open root device "sdd2" or unknown-block(0,0)
> From: delga...@ihug.co.nz
> To: lfs-support@linuxfromscratch.org
> Date: Wed, 17 Jun 2009 22:50:33 +1200
>
> On Tue, 20
On Tue, 2009-06-16 at 19:41 +0100, Ken Moffat wrote:
> For a normal (native) system I would say that you either failed to
> compile the filesystem or the correct disk driver (or both!) into the
> kernel.
Probably the latter, since no partitions were listed as being
available...
Simon.
signatur
(warning: first reply from my googlemail a/c, sorry if this is screwed up)
On 16/06/2009, ajith silva wrote:
> I have completed my LFS 6.4 build, but during booting it gives following
> error message:
>
>
> VFS: Cannot open root device "sdd2" or unknown-block(0,0)
> P
Dear all,
I have completed my LFS 6.4 build, but during booting it gives following error
message:
VFS: Cannot open root device "sdd2" or unknown-block(0,0)
Please append a correct "root=" boot option: here are the available partitions:
Kernel panic - not sysncing:
Am Sonntag, 25. Mai 2008 17:03:18 schrieb Dan Nicholson:
> On Sun, May 25, 2008 at 7:34 AM, Mag. Leonhard Landrock
>
> <[EMAIL PROTECTED]> wrote:
> > So I believe to have
> >
> > 1.) 00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet
> > Controller (rev a1)
> > 2.) 01:04.0 Ethernet co
On Sun, May 25, 2008 at 7:34 AM, Mag. Leonhard Landrock
<[EMAIL PROTECTED]> wrote:
>
> So I believe to have
>
> 1.) 00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet
> Controller (rev a1)
> 2.) 01:04.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit
> Ethernet Cont
Hello!
When starting my LFS I have the problem, that I have no eth0 or eth1.
Yes, I took a look at the FAQ. :-)
I have started my LFS from Debian Lenny. So I tried to get the necessary
information for the device drivers there.
Here is what lspci from Debian says:
[EMAIL PROTECTED]:~$ lspci
0
Jeremy Henty wrote:
> I upgraded my LFS 6.1.1 from 2.6.23 to 2.6.24 and now all 8-bit
> characters appear as a reverse-video question mark in the terminal.
> At least this is true for the pound sign in emacs, and accented
> characters in mutt. If I run emacs in xterm the pound sig
On Saturday 10 February 2007 23:38, Steffen H. Larsen wrote:
> [...] but now I looked at the post above me and well I saw that
> he used
> the command like this
>
> root (hd0,0)
>
> and I tried that too and now it seem to work.
> I guess the last number was more
> important than what I thourght it
Dan Nicholson gmail.com> writes:
>
> Did you copy the necessary *stage1_5 files for your filesystem from
> /usr/lib/grub/i386-pc/ to /boot/grub/?
>
> --
> Dan
yea I did but now I looked at the post above me and well I saw that he used
the command like this
root (hd0,0)
and I tried that
On 2/10/07, Steffen H. Larsen <[EMAIL PROTECTED]> wrote:
> hi I'm allmost done with making a LFS system but now it create this error when
> trying to make it bootable in grub when using this command:
> root (hd0)
>
> Filesystem type unknown, using whole disk
>
> wh
Steffen H. Larsen wrote on 10-02-07 22:27:
> hi I'm allmost done with making a LFS system but now it create this error when
> trying to make it bootable in grub when using this command:
> root (hd0)
>
> Filesystem type unknown, using whole disk
>
> why does it do
hi I'm allmost done with making a LFS system but now it create this error when
trying to make it bootable in grub when using this command:
root (hd0)
Filesystem type unknown, using whole disk
why does it do that ? can any tell me any causes that normally does this ?
--
I kn
I'm running kernel version 2.6.11.12 compiled with "Loadable module support"
turned off. When I execute
iptables -t mangle -A PREROUTING -j TTL --ttl-set 128
I get this:
iptables: Unknown error 4294967295
I'm using iptables 1.3.5. What does this message mean?
P.
lp me troubleshoot my
problem.
Paul
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of William
Harrington
Sent: Thursday, February 09, 2006 3:01 PM
To: LFS Support List
Subject: Re: 2.6.14 kernel panic - Cannot open root device "sda1" or
unknown- block
On Feb
On Feb 9, 2006, at 11:23 AM, Paul wrote:
My 2.6.14 kernel won't boot. I have tried to document it as best I can
below. Any help or recommendation would be greatly appreciated
It boots
Errror Message:
Cannot open root device "sda1" or unknown-block(0,0)
Please append a corre
My 2.6.14 kernel won't boot. I have tried to document it as best I can
below. Any help or recommendation would be greatly appreciated
Errror Message:
Cannot open root device "sda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not sync
49 matches
Mail list logo
