On 11/29/09, linux fan wrote:
> The "VFS can't find ..." suggests that the boot loader (grub/lilo)
> done its job and the kernel was loading until it choked on the
> filesystem fstab told it,
If the message is exactly:
Kernel panic -not syncing VFS: unable to mount root fs on unknown-block(0,0)
Alberto Hernando wrote:
> Hi.
>
> I've tried it, and:
>
> root:/boot/grub# grub-setup -r '(hd0,8)'
> No device is specified.
I gave incorrect advice before. Try:
grub-setup '(hd0)'
or
grub-setup /dev/sda
The -r should not be there. The syntax is:
grub-setup [OPTION]... DEVICE
If
On 11/29/09, Alberto Hernando wrote:
> ... The error is the same, VFS
> can't find a valid root system, "please add a valid root option". I
> .. and /etc/fstab is as the book says.
If /etc/fstab is as the book says (verbatim), it won't work.
You must interpolate
/dev/ / defaults
knothea...@gmail.com wrote:
>> I assume you mean Chapter 5.6, but we don't really reference the pdf
>> pages.
>
> sorry -- > i meant when i try to install (in section) 6.7.
> Linux-2.6.30.2 API Headers
> i get the errors.
>>
>>> root:/sources/linux-2.6.30.2# make headers_check
>>> CHK includ
> I assume you mean Chapter 5.6, but we don't really reference the pdf
> pages.
sorry -- > i meant when i try to install (in section) 6.7.
Linux-2.6.30.2 API Headers
i get the errors.
>
>
>> root:/sources/linux-2.6.30.2# make headers_check
>> CHK include/linux/version.h
>> UPD include/
linux fan wrote:
> On 11/28/09, Baho Utot wrote:
>
>
>> make test | tee $CURRDIR/06.58.Check.log
>> make install | tee $CURRDIR/06.58.Install.log
>>
> Logging helps so much when things go wrong.
>
> As already mentioned
>
>
>> Scripting an LFS build is *hard*
>>
>
> [putolin]
> I on
2009/11/29 Alberto Hernando :
> Hi.
>
> I'm building LFS-6.5 (-svn, actually), and I can't make it boot. I've done
> the same in two machines, an old athlon amd and a pentium-iv. Kernel builds
> fine in both systems, but none of them can boot. The error is the same, VFS
> can't find a valid root sy
Alberto Hernando wrote:
> Hi.
>
> I've tried it, and:
>
> root:/boot/grub# grub-setup -r '(hd0,8)'
> No device is specified.
>
> The same. I've also tried several things using slashes and still the same.
> Is there really something wrong with using lilo? I mean, how can I be sure
> that grub wil
Hi.
I've tried it, and:
root:/boot/grub# grub-setup -r '(hd0,8)'
No device is specified.
The same. I've also tried several things using slashes and still the same.
Is there really something wrong with using lilo? I mean, how can I be sure
that grub will be able to boot a kernel that lilo can't?
Alberto Hernando wrote:
>> Make shure that your IDE/PATA/SATA drivers are built right in the
>> kernel.
> All these drivers are built in the kernel.
> Now I'm trying to use GRUB following the book and I get this:
>
> root:/# grub-setup
> No device is specified.
>
> root:/# grub-setup -r (hd0,8
> Honestly, unless you are using pure64, you should use GRUB instead.
> Make shure that your IDE/PATA/SATA drivers are built right in the
> kernel. Just so you know.
>
>
Hi.
All these drivers are built in the kernel.
Now I'm trying to use GRUB following the book and I get this:
root:/# grub-set
knothea...@gmail.com wrote:
> I am getting the error as follows @ pg 85 in the 6.5 book:
I assume you mean Chapter 5.6, but we don't really reference the pdf
pages.
> root:/sources/linux-2.6.30.2# make headers_check
> CHK include/linux/version.h
> UPD include/linux/version.h
> HOS
On Sun, Nov 29, 2009 at 1:16 PM, Alberto Hernando wrote:
> I'm building LFS-6.5 (-svn, actually), and I can't make it boot. I've done
> the same in two machines, an old athlon amd and a pentium-iv. Kernel builds
> fine in both systems, but none of them can boot. The error is the same, VFS
> can't
I am getting the error as follows @ pg 85 in the 6.5 book:
root:/sources/linux-2.6.30.2# make headers_check
CHK include/linux/version.h
UPD include/linux/version.h
HOSTCC scripts/basic/fixdep
scripts/basic/fixdep.c: In function 'traps':
scripts/basic/fixdep.c:377: warning: derefere
Hi.
I'm building LFS-6.5 (-svn, actually), and I can't make it boot. I've done
the same in two machines, an old athlon amd and a pentium-iv. Kernel builds
fine in both systems, but none of them can boot. The error is the same, VFS
can't find a valid root system, "please add a valid root option". I
On Sun, Nov 29, 2009 at 1:54 AM, Simon Geard wrote:
> Not an expert on VirtualBox, but if udev is incorrectly identifying a
> device, that normally suggests the the hardware is providing incorrect
> information to it. In this case, that hardware would be VirtualBox, so
> perhaps there's something
16 matches
Mail list logo
