headers
girish vg | 26 Jan 2013 13:09
Favicon

1 new photo on MyDailyFlog!


Hi!
I would like you to come and see my latest photos on MyDailyFlog. 

Check out: http://www.mydailyflog.com/go/invite_register/girishgulawani/48268548&stc=71

Thanks!
girish vg

~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
To unsubscribe of this type of email from MyDailyFlog in the future,
please click below:
http://www.mydailyflog.com/un/port-evbmips <at> netbsd.org&md5=6f0a8b90c8d9a86e&bl=16

Please do not reply directly to this email. Questions? Contact us - 
http://www.mydailyflog.com/go/contact_us

MyDailyFlog, Refriendz Ltd. PO BOX 1184, Luton, Bedfordshire, LU1 9AT.
Permalink | Reply | 0 comments |
headers
girish vg | 26 Jan 2013 13:09

Check out this photo on MyDailyFlog!


Hi!
I would like to invite you to visit MyDailyFlog and see my latest photos. 

Check out: http://www.mydailyflog.com/go/invite_register/girishgulawani/48268548&stc=16

Cheers!

girish vg

========================================
Got a digital camera?

MyDailyFlog is a personal photo-blogging space where you can easily post
your latest and greatest photos, and share them with your friends and family.

Create your own DailyFlog at www.MyDailyFlog.com

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Unsubscribe: to opt out of further invitations from your friends to see 
their DailyFlogs, please click below:
http://www.mydailyflog.com/un/port-evbmips <at> netbsd.org&md5=6f0a8b90c8d9a86e&bl=16

Please do not reply directly to this email. Questions? Contact us - 
http://www.mydailyflog.com/go/contact_us

MyDailyFlog, Refriendz Ltd. PO BOX 1184, Luton, Bedfordshire, LU1 9AT.
Permalink | Reply | 0 comments |
headers
mac c | 9 Dec 2012 04:59
Picon

Netbsd on Atheros AR71xx

Hi,
I would like to run NetBSD on cpu Atheros 7130,
Netbsd 6 has support for this soc?

Marcos
Permalink | Reply | 3 comments |
headers
Alexander Nasonov | 24 Nov 2012 15:22
Picon
Favicon

bpfjit

After a successful testing of bpfjit on an emulated MALTA board, I
committed sljit support to evbmips. It's disabled my default but you
can easily enable it. To reproduce my setup, you need to apply the patch
below and build with MKSLJIT=yes.
I followed an instruction on gxemul page to install and run my system
under gxemul emulator. I also added "net.bpf.jit=1" to sysctl.conf
while following an installation instruction.
All sljit and bpfjit userspace tests pass and the system can filter
packets using simple rules.

Alex

Enable bpfjit on MALTA ebvmips board.

Index: sys/arch/evbmips/conf/MALTA
===================================================================
RCS file: /cvsroot/src/sys/arch/evbmips/conf/MALTA,v
retrieving revision 1.69
diff -p -u -u -r1.69 MALTA
--- sys/arch/evbmips/conf/MALTA 17 Oct 2012 14:48:11 -0000      1.69
+++ sys/arch/evbmips/conf/MALTA 24 Nov 2012 14:05:30 -0000
 <at>  <at>  -307,6 +307,9  <at>  <at>  audio*              at clct?
 #pseudo-device md                              # memory disk device
(ramdisk)
 pseudo-device  vnd                             # disk-like interface to
files

+options SLJIT
+options BPFJIT
+
(Continue reading)

Permalink | Reply | 5 comments |
headers
Lloyd Parkes | 7 Oct 2012 00:08
Picon

How stable is the Atheros AR9344 support?

Hi all,
I'm looking at replacing my NetBSD based home router with a MikroTik RB2011UAS-2HnD because I need more
throughput and the routerboards are cheap. I'm sure the included RouterOS works fine, but I wouldn't mind
running NetBSD instead. I realise that NetBSD hasn't been ported to RB2011 devices, but they are cheap
enough that I'm willing to buy one to tinker with. 

So, how stable is the Atheros AR9344 support? 

Cheers,
Lloyd
Permalink | Reply | 0 comments |
headers
John D. Baker | 21 Jun 2012 09:04

System time and ToD clock?

Not having seen any documentation about this (and I'd not yet gotten to
UTSL), I was a bit surprised when gNewSense reported that my Yeeloong's
ToD clock was set to 1992, making the filesystems have dates in the
future.

Dropping into PMON at the next boot confirmed that the day/month/time
was correct, but was 20 years in the past.  I set it back to the current
year.

When I booted NetBSD again, it declared "Preposterous time in ToD clock"
and initialized system time from the filesystem timestamps.  Shortly
therafter 'ntpd' was started to keep time sane (thanks to now-working
ioctls).

When, after a panic (freeing free inode on an ext2fs filesystem), I
again booted gNewSense to clean up.  Once again it reported a year of
1992.  Returning to NetBSD once more elicited no warnings.

This is reminiscent of the mvme68k port where system ToD clock holds
only a 2-digit year taken as an offset from the epoch (1968 in the
case of NetBSD/mvme68k).

Is this also the case for the evbmips port?  While this might be fine
for hardware unlikely to share local filesystems with other OSes, it
makes multi-booting Lemote systems troublesome.

--

-- 
|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
(Continue reading)

Permalink | Reply | 1 comment |
headers
John D. Baker | 8 Jun 2012 21:30

sshd session hang, bad file descriptor data

Attempts to connect to my Yeeloong via ssh from an i386 client still
hang.  I'm not getting any console messages, but that may be a side
effect from my 'amd' investigation.

The symptoms from the client end remain the same.  The server prompts
for password and no further operations are possible on the client end.
the client terminal is locked into an unresponsive network connection.
The usual "~." doesn't work.  In a graphical environment, one must
destroy the window.  (I haven't tried from a non-graphical client, but
I expect one must log in to the client from elsewhere and kill the
frozen session.)

Below are what may be relevant snippets of ktruss output generated with
'sudo ktruss -i -p <pid> | tee sshd.ktruss'.  In this instance, the PID
of the master sshd process was 630.  There were no messages relevant
to this logged in /var/log/messages.

The output is some different than before.  Before, I saw a distinct
pattern of user-after-close.  This time, an attempt is made to close
a file descriptor of -1 (0xffffffff)

    630      1 sshd     __select50                  = 1
    630      1 sshd     emul(netbsd32)
    630      1 sshd     netbsd32_accept(0x4, 0x7fff67f8, 0x7fff6730) = 5
    630      1 sshd     netbsd32_fcntl(0x5, 0x3, 0) = 6
    630      1 sshd     netbsd32_fcntl(0x5, 0x4, 0x2) = 0, 2015257344
    630      1 sshd     pipe()                      = 7, 8
    630      1 sshd     netbsd32_socketpair(0x1, 0x1, 0, 0x7fff6738) = 0
    630      1 sshd     fork()                      = 1061
(Continue reading)

Permalink | Reply | 1 comment |
headers
John D. Baker | 8 Jun 2012 20:54

'amd' Invalid argument data

So, getting back to the problem with 'amd' failing to mount my
various automount points with "Invalid argument" reports, below
is the relevant excerpt from '/var/log/messages':

Jun  8 13:21:59 chalk amd[263]: '/home': mount: Invalid argument
Jun  8 13:21:59 chalk amd[685]: '/m': mount: Invalid argument
Jun  8 13:22:04 chalk /netbsd: ktrace timeout
Jun  8 13:22:04 chalk amd[264]: '/net': mount: Invalid argument
Jun  8 13:22:04 chalk amd[264]: '/net': mount: Invalid argument
Jun  8 13:22:05 chalk amd[264]: amfs_toplvl_mount: amfs_mount failed: Invalid argument
Jun  8 13:22:05 chalk amd[881]: /net: mount (amfs_cont): Invalid argument
Jun  8 13:22:10 chalk amd[263]: '/home': mount: Invalid argument
Jun  8 13:22:10 chalk amd[685]: '/m': mount: Invalid argument
Jun  8 13:22:10 chalk amd[685]: amfs_toplvl_mount: amfs_mount failed: Invalid argument
Jun  8 13:22:10 chalk amd[881]: /m: mount (amfs_cont): Invalid argument
Jun  8 13:22:10 chalk amd[263]: amfs_toplvl_mount: amfs_mount failed: Invalid argument
Jun  8 13:22:10 chalk amd[881]: /home: mount (amfs_cont): Invalid argument
Jun  8 13:22:46 chalk syslogd[381]: last message repeated 3 times

And here are what I hope are the relevant snippets of "ktruss" output
generated with 'ktruss -i /etc/rc.d/amd start | tee amd.ktruss'.  In
the first case, "netbsd32_bind()" on a socket fails.  After that, all
the failures are in "netbsd32___mount50()"

    881      1 amd      netbsd32___socket30(0x2, 0x2, 0) = 5, -53
    881      1 amd      netbsd32_bind(0x5, 0x7fff6980, 0x10) Err#48 EADDRINUSE
    881      1 amd      netbsd32_bind(0x5, 0x7fff6980, 0x10) Err#48 EADDRINUSE
    881      1 amd      netbsd32_bind(0x5, 0x7fff6980, 0x10) = 0, 64768
    881      1 amd      netbsd32_open("/etc/netconfig", 0x400000, 0x1b6) = 7
    881      1 amd      netbsd32___fstat50(0x7, 0x7fff6750) = 0, 2020703392
(Continue reading)

Permalink | Reply | 0 comments |
headers
John D. Baker | 3 May 2012 15:39

Lemote Yeeloong observations

Since the announcement of support for the Lemote Yeeloong netbook in
the evbmips port, I've returned to experimenting^Wplaying with it.

I'm booting via tftp and using NFS root from my (netbsd-i386) fileserver
and build host.

The first few times booting the machine and finishing configuration went
OK.  At some point I ran into a problem such that "/dev/console" was
left 'chown'ed to my unprivileged user after a forced power-cycle.  This
issue was recently corrected.

I'd been attempting to build a few packages, but have been having various
toolchain failures.  "digest" is usually the root dependency of everything
else, but it can't make it through the "configure" phase.  The machine
hangs or most recently, the assembler failed, claiming it didn't support
some feature that was expected.  (If I can get the system stabilized,
I'll try to collect the results).

Lately I've been having trouble with corrupted files.  What I mostly
see is that on some subsequent boot, 'init' fails because "/etc/rc" is
truncated and causes 'sh' to terminate with an error.  I re-ran 'etcupdate'
with the {,x}etc.tgz sets as source and found a number of
truncations/corruptions, typically:

   /etc/rc
   /etc/defaults/rc.conf
   /etc/rc.d/network
   /etc/pf.os
   /dev/MAKEDEV
   /etc/services
(Continue reading)

Permalink | Reply | 10 comments |
headers
NONAKA Kimihiro | 2 Mar 2012 14:50
Picon
Gravatar

Lemote Yeeloong Notebook support

Hi,

I've commited Lemote Yeeloong Notebook support.

Supported devices:
- Realtek 8139 100M LAN (rtk)
- Silicon Motion SM712 (lynxfb, tested console only)
- USB Host Controller (ohci, ehci)
- AMD CS5536 IDE Controller (viaide)
- AMD CS5536 Audio (gcscaudio, tested playback only)
- Keyboard (pckbd)
- Touch pad (pms)

Not Supported devices:
- Realtek RTL8187 WLAN
- KB3310 Embedded controller

dmesg: boot on sd1a(USB memory)
PMON boot command: boot -k /dev/fs/ext2 <at> usb0/netbsd
-----
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010, 2011, 2012
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 6.99.3 (LOONGSON) #3: Fri Mar  2 22:05:12 JST 2012
	nonaka <at> koharu.myhome.local:/usr/obj.evbmips/sys/arch/evbmips/compile/LOONGSON
total memory = 1024 MB
avail memory = 1008 MB
(Continue reading)

Permalink | Reply | 1 comment |
headers
John D. Baker | 16 Nov 2011 06:38

Which kernel for Lemote Yeeloong?

I have a Lemote Yeeloong 8101-B and have been following efforts to
support the offerings from Lemote.  The system currently dual-boots
gNewSense and OpenBSD 5.0-current from disk.

I built a recent release using "-m evbmips64el" since that seemed to
be equivalent to the OpenBSD architecture.

My usual practice for exploring new platforms or new software on familiar
platforms is to netboot and operate diskless/NFS-root.

I populated a root directory on my server using the kern-LOONGSON.tgz
kernel set, hardlinking it to my tftpboot directory.

On the Yeeloong, I dropped into PMON, set the address and booted
the kernel via tftp.

The LOONGSON kernel complained about a corrupted environment, that it
couldn't determine the platform and that it was unsupported hardware.

I next tried a GDIUM64 kernel and it seemed to go, but when it initialized
the framebuffer, I only saw about 2 lines of GALLANT12x22 displaying
memory statistics at the top of the screen (the rest of the screen was
in PMON text mode).  After this, the narrow strip across the top cleared
to white with no apparent further activity.

Sometimes it displays in white-on black and sometimes black-on-black.
(Maybe a small black light lights up black to let me know I've done
it, but can't really tell... ;)

I haven't tweaked any PMON settings (other than "moresz" to cope with
(Continue reading)

Permalink | Reply | 8 comments |

Gmane