From: "Juergen Sievers" <JSievers@NADINE-Software.com>
To: 'Abot Botbot' <dejanigma@hotmail.com>,
linux-omap-open-source@linux.omap.com
Subject: AW: Help: OMAP5912 RS232 dies after kernel uncompressing.
Date: Mon, 15 Jan 2007 21:50:22 +0100 [thread overview]
Message-ID: <001201c738e6$c7945890$0700a8c0@NADHHLT01> (raw)
In-Reply-To: <BAY102-F369B3C89BF75F87EB6E11DA9B50@phx.gbl>
Hi Andy.
Hem unbelievable.
But the omap mounts its nfs-root and I can login on the omap by using telnet
So I can not understand how a wrong configured nfs-server might stop the
ttyS0
Could it be that you did not read that the system boots completely or do I
not understand what you mean?
Mfg.
j.
-----Ursprüngliche Nachricht-----
Von: Abot Botbot [mailto:dejanigma@hotmail.com]
Gesendet: Montag, 15. Januar 2007 16:53
An: JSievers@nadine-software.com; linux-omap-open-source@linux.omap.com
Betreff: RE: Help: OMAP5912 RS232 dies after kernel uncompressing.
Juergen,
Perhaps your NFS Share isn't set up correctly? I had that problem before I
had set up my NFS share with the right perms and whatnot. Maybe look into
the particulars of the config file and make sure all is well. Try mounting
the target NFS with another machine other than the board.
Hope this helps,
Andy
>From: "Juergen Sievers" <JSievers@nadine-software.com>
>Reply-To: JSievers@nadine-software.com
>To: "'Linux OMAP List'" <linux-omap-open-source@linux.omap.com>
>Subject: Help: OMAP5912 RS232 dies after kernel uncompressing.
>Date: Mon, 15 Jan 2007 16:22:26 +0100
>
>
>Hello.
>
>After I modified the environment by using setenv/saveenv I got the
>following
>problem.
>
>The terminal connected to the OMAP5912 rs232 at 115200n8 is working as long
>as the kernel is uploaded and decompressing. The last message shown is
>".booting."
>
>After that message the rs232 line seems to be dead.
>
>The kernel is mounting its root from nfs-server and is running normally
>except the console device could be used.
>
>I tried several kernels (2.6.16/2.6.19) including the pre-build kernel 2.4
>from the distribution CD All the same, the rs232 line dies after
>uncompressing the kernel.
>
>My bootags setting are:
>
>Bootargs = "mem=32 console=ttyS0,115200n8 ip=dhcp root=/dev/nfs rw
>nfsroot=192.168.0.50:/nfsroot"
>
>Has anybody an idea what I could do to get back my rs232 console ?
>
>Regards
>
>Juergen
>
>
>_______________________________________________
>Linux-omap-open-source mailing list
>Linux-omap-open-source@linux.omap.com
>http://linux.omap.com/mailman/listinfo/linux-omap-open-source
_________________________________________________________________
Find sales, coupons, and free shipping, all in one place! MSN Shopping
Sales & Deals
http://shopping.msn.com/content/shp/?ctid=198,ptnrid=176,ptnrdata=200639
next prev parent reply other threads:[~2007-01-15 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 16:34 [Howto] 2430 kernel,uboot and filesystem Nishanth Menon
2007-01-15 15:22 ` Help: OMAP5912 RS232 dies after kernel uncompressing Juergen Sievers
2007-01-15 15:53 ` Abot Botbot
2007-01-15 20:50 ` Juergen Sievers [this message]
2007-01-16 0:58 ` AW: " Nishanth Menon
2007-01-16 12:01 ` AW: " Juergen Sievers
2007-01-15 16:05 ` Liem Pham Tan
2007-01-15 18:00 ` [Howto] 2430 kernel,uboot and filesystem Dirk Behme
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001201c738e6$c7945890$0700a8c0@NADHHLT01' \
--to=jsievers@nadine-software.com \
--cc=dejanigma@hotmail.com \
--cc=linux-omap-open-source@linux.omap.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox