Similar Threads
1. problem with initialization while accessing NFS mounted root file system during the Linux 2.6 boot - Linux
2. problem with initialization while accessing NFS mounted root file system during the Linux 2.6 boot
> Hi,
>
> I've managed to program U-boot bootloader and now am trying to boot my
> PQ2FADS-VR board " vanilla" with Linux 2.6.8-rc4 ...but I have problem
> with the initialization while accessing NFS mounted root file system ...
> .
>
> I have NFS server running on my Windows XP Laptop (that is all I am
> allowed to have, no Linux hosts machine available to me ...). I copied
> entire "fadsroot" directory from Arabella's CD-ROM into my "fadsroot"
> directory on my D-drive and made this directory nfs-shared-mountable (I
> have propagated permissions from "fadsroot" down to all subfolders within
> "fadsroot" ...).
>
> I noticed several errors during the copy process - complaining that I am
> over-writing the files being already copied - is it an issue with "letter
> case" ? - are there files on the Arabella's CD-ROM "fadsroot", which have
> same names but differ just in the letter case used ?
>
What file system support I need to configure while bulding the kernel for
such case ?
> Anyway I am getting the following error during the end of the boot:
> ......
> device=eth0, addr=192.168.1.103, mask=255.255.255.0, gw=255.255.255.255,
> host=192.168.1.103, domain=, nis-domain=(none),
> bootserver=255.255.255.255, rootserver=192.168.1.100, rootpath=
> Looking up port of RPC 100003/2 on 192.168.1.100
> Looking up port of RPC 100005/1 on 192.168.1.100
> VFS: Mounted root (nfs filesystem).
> Freeing unused kernel memory: 272k init
> Warning: unable to open an initial console.
> Kernel panic: No init found. Try passing init= option to kernel.
> <0>Rebooting in 180 seconds..
>
> My U-boot environment is:
> => printenv
> bootdelay=5
> bootcmd=bootm 200000
> ipaddr=192.168.1.103
> serverip=192.168.1.100
> ethaddr=08:00:17:00:00:03
> bootargs=root /dev/nfs rw nfsroot=192.168.1.100:/home/apovolot/fadsroot
> baudrate=19200
> stdin=serial
> stdout=serial
> stderr=serial
>
> Any ideas ?
> Thanks,
> Alex
>
--
To UNSUBSCRIBE, email to XXXX@XXXXX.COM
with a subject of "unsubscribe". Trouble? Contact XXXX@XXXXX.COM
3. system without RAM on node0 boot fail - Linux
4. Make changes to read-only file system using RAM
5. DVD-RAM errors (was: DVD-RAM crashing system) - Linux
6. redhat enterprise linux 4 boots up slow with 2 GB RAM , boots fast with 512MB
Machine Configuration:
I have assembled a new machine. Its Intel P4 3.0E Ghz HT enabled
processor on ASUS P4P800-MX motherboard. I am using onboard graphics
and sound. [Motherboard Spec]
----------------------------------------------------
Socket 478, Intel865GV, Hyperthreading ready, integrated intel
graphics, dualchannel DDR400, 10/100Mbps LAN, Serial ATA
----------------------------------------------------
I have put in two 1 GB dual-channel RAM chips (OCZ technologies) in it.
Problem
I installed "Redhat Enterprise Linux 4 WS" on it (installation went
super slow..took around 3 hours to complete). Now, it takes RHELv4 a
whopping 18 MINUTES to boot up. WindowsXP pro (the other OS on this
dual boot machine) boots up in less than 30 secs.
Solutions tried
1)
Since my ASUS motherboard is SMP-enabled and my processor is HT
enabled, RHELv4 installed an SML kernel and a normal kernel. But I get
the same (very poor) performance from RHELv4, no matter which one (of
the two kernels) I use to boot it up.
In SMP-kernel case, I confirmed that cat /proc/cpuinfo shows
2 processors being recognized by RHELv4 (even then the bootup takes
18-20 mins.)
2)
I read online about RHEL issues with 1GB+ memory.
So, just to narrow down the issue, I took out these two 1 GB
dual-channel RAM chips and put in a regular Kingston 512MB RAM chip
and RHELv4 started booting up in less than a minute. So now I know the
problem is with using 1 GB + RAM.
3)
I confirmed (2) by putting back only one 1GB RAM dual-channel RAM chip,
and it started super slow (took around 18-20 mins to bootup again). I
also tried passing in mem=1024M kernel parameter, but that did not help
either. Even though the cat /proc/meminfo shows 1024MB of RAM being
recogized by RHELv4.
I did some search online and found some mixed opinions (which I havent
tried yet..since I am not sure about them ,
just listing them here and asking for more suggestions..
a)
Should I recompile my kernel with highmem support -
Isn't highmem only suppposed to be used with 4 GB+ ram machines.?
b)Is this slow bootup being caused by the onboard Integrated Intel
graphics ?
Any ideas which one of the above two or (any other alternatives) should
i try... ? please help as I am running out of my options now.. Thanks
in advance for any helpful tips..
7. more than 2GB of RAM ( problems if more than 2GB RAM )
8. Problems moving files to trash when on different file systems
I seem to have discovered a problem that prohibits deleting and editing
files on a FreeBSD 5.2.1 NFS share from a Solaris 10 client running Xsun
and GNOME desktop.
I'm using the file "foobar" as the test subject and it lives on the NFS
server. All commands are being executed from the client unless otherwise
specified. I've already verified that my UID/GIDs match on both hosts
and that my NFS settings are configured properly.
$ls -n
-rw-r--r-- 1 500 500 0 Apr 11 2005 foobar
The Symptoms:
1) I can't delete "foobar" while in nautilus, but I can delete "foobar"
when in the shell (bash).
2) When I try to delete "foobar" while in nautilus, I get the following
message:
Error "Not on the same file system" while deleting
"/export/home...iles/foobar".
The Analysis:
"...this is simply a problem with nautilus that can be reproduced
whenever the "trash" isn't on the same fs as the file being deleted."
***Thanks to Robert Lawhead for identifying the source of this problem
The Resolution:
Presently, I have not found a proper solution to the problem. For a
quick and dirty band-aid however, nautilus can be confiured to bypass
the trash when deleting files.
I'm still looking for a way to fix this issue as I do not have to deal
with it when using a Fedora Core 2 client. I also believe it to be
stopping me from using my Evolution client over NFS (or somehow related,
at least).
Any help or advice would be most appreciated.
Thanks,
Oliver