Re: Lemote Fuloong

2012-07-06 Thread Code Blue
 iirc one reason the EINVAL on mount can occur is with an unclean
 ext2/3 filesystem. Could that be the case here?

Yes, but it should only have been the case on the 2nd install (2 of 3).

After I copied the boot file from the installation directory to the ext2
partition I had created for booting from, I neglected to unmount the
partition since I ASSumed OBSD would unmount all mounted filesystems during
a halt. I forgot that iirc OpenBSD only unmounts mounted filesystems that
are in fstab. I did remember to unmount it by the time the 3rd installation
ran and perhaps that is why it didn't give me that message when I installed
the same snapshot again. I don't know why it happened the first two times.

Running on snapshot, I built a package for Mutt from ports and it took a
very long time. I'd like to know how much of that is due to the slow
console. Are you building with output redirection? At the end the package
failed to install with the same library errors I listed before. However,
make install seems to have worked. I haven't verified Mutt is working
100%, I'll do that later (now I am posting from another system). I'm
building Emacs now and when it finishes I'll be able to verify Mutt works as
it did on 5.1.

Given there aren't too many Fuloongs around and we all have to build
packages for the apps we want, is there any way to contribute packages we
have built?

-- 
   _
ASCII ribbon campaign ( ) Please follow up to the mailing list
 against HTML e-mail   X   
   and proprietary/ \  Mutt.org
 attachmentsCode Blue or Go Home!



Re: Lemote Fuloong

2012-07-05 Thread Code Blue
On Wed, Jul 04, 2012 at 10:07:52PM +0200, Tomas Bodzar wrote:
 On Wed, Jul 4, 2012 at 7:59 PM, Code Blue codeb...@inbox.lv wrote:
  Thanks to the OpenBSD team and Miod Vallat for the Loongson port.
 
  I am trying to put together a MIPS development machine and I installed
  OpenBSD 5.1. I didn't see a change log for the Loongson snapshot referenced
  from the OpenBSD Loongson page so I don't know if there are any relevant
  changes for my intended use or whether the snapshots are supposed to be
  experimental. Which version should I use and should I be tracking current
  for this machine? Thanks.
 
 For sure better to use snapshots/current.

Thanks, I'll reinstall then. Should I track current on this? I don't have
any idea how many changes are being done on it.

 And I think it's valid for any similar experimental port.

Is Loongson an experimental port? The OpenBSD page lists it under the
officially support platforms...I realize it's a work in progress, but I
didn't think it was experimental. Aside from the bootblocks not installing
from either 5.1 release or the 5.2. snapshot, everything seems to be working.

 BTW this one http://lemote.kd85.com/ will work with Loongson port as well?
 Seems like it's slightly different CPU.

Good question and I have no idea. Yes, it's a different CPU. The 2E and 2F
are uniprocessors. The 3A is a quard.  Maybe the port maintainer will chime
in. Many patches are hitting the Linux kernel and binutils from Lemote and
MIPS people so I believe there are significant differences.

-- 
   _
ASCII ribbon campaign ( ) Powered by Lemote Fuloong
 against HTML e-mail   X  MIPS Loongson and OpenBSD
   and proprietary/ \ Mutt.org
 attachmentsCode Blue or Go Home!



[codeb...@inbox.lv: Re: Lemote Fuloong]

2012-07-05 Thread Code Blue
  For sure better to use snapshots/current.

 Thanks, I'll reinstall then. Should I track current on this?

DOH! Sorry, I see you answered this already.



Re: Lemote Fuloong

2012-07-05 Thread Code Blue
On Thu, Jul 05, 2012 at 12:17:27PM +0200, Otto Moerbeek wrote:

 Loongson is not experimental. There are less users using it compared
 to some other platforms, but the port is certainly stable enough to be
 used for real stuff. I'm running a Fuloong as my general purpose
 mai/file/dns/web server at home and i have had zero trouble with it.
 In fact I'm typing this mail on it ... 

I was running fine on 5.1 but based on the comment from the previous poster
I reinstalled the snapshot (5.2). I was then unable to install any packages
from snapshots because of library errors. For example:

# pkg_add mutt-1.5.21p0v0-sasl

Can't install libiconv-1.14 because of libraries
|library c.64.1 not found
| /usr/lib/libc.so.65.0 (system): bad major
Can't install qdbm-1.8.78: can't resolve libiconv-1.14
Can't install cyrus-sasl-2.1.25p3 because of libraries
Can't install gettext-0.18.1p1: can't resolve libiconv-1.14
Can't install lmutt-1.5.21p0v0-sasl: can't resolve 
cyrus-sasl-2.1.25p3,libiconv-1.14,qdbm-1.8.78,gettext-0.18.1p1

I don't know whether I should reinstall 5.1 and use it until 5.2 comes out
or whether I should continue and try to track -current and see if the issues
are resolved, but I am not looking forward to compiling much source given
the lack of framebuffer acceleration! I used to track -stable on i386 but I
have been away from OpenBSD for a while so I am a little rusty on all
this.

Are you running -current or 5.1 and since you are using it for a server and
it is working fine for you, what would you recommend? 

Thanks.

-- 
   _
ASCII ribbon campaign ( )   
 against HTML e-mail   X 
   and proprietary/ \  Mutt.org
 attachmentsCode Blue or Go Home!



Re: Lemote Fuloong

2012-07-05 Thread Code Blue
On Thu, Jul 05, 2012 at 06:53:29AM -0700, James Hartley wrote:
 On Thu, Jul 5, 2012 at 5:12 AM, Code Blue codeb...@inbox.lv wrote:
 
  I was running fine on 5.1 but based on the comment from the previous poster
  I reinstalled the snapshot (5.2). I was then unable to install any packages
  from snapshots because of library errors.
 
 
 What is the value of PKG_PATH?  Now that you have moved from 5.1-release to
 -current,  you will also have to change the location where packages are
 downloaded in order to keep both OS  packages synchronized.  See FAQ
 15.4.1.

Thanks, I am aware of it. I changed it to point to the snapshots directory
of packages rather than 5.1 as shown in FAQ 15.2.2. The errors were as shown
in the previous post. I am not using ports at this time, only the
pregenerated packages.

-- 
   _
ASCII ribbon campaign ( )   Please follow up to the newsgroup
 against HTML e-mail   X  
   and proprietary/ \  Mutt.org
 attachmentsCode Blue or Go Home!



Re: Lemote Fuloong

2012-07-05 Thread Code Blue
On Thu, Jul 05, 2012 at 10:59:54AM -0300, Daniel Bolgheroni wrote:
 On Thu, Jul 05, 2012 at 12:12:43PM +, Code Blue wrote:
  
  |library c.64.1 not found
  | /usr/lib/libc.so.65.0 (system): bad major
 
 Your mirror is probably not so current. Try using another mirror.

I tried 2 so far but I will try another one. Do you happen to know one that
is surely current? Thanks.

-- 
   _
ASCII ribbon campaign ( ) Please follow up to the mailing list
 against HTML e-mail   X   
   and proprietary/ \  Mutt.org
 attachmentsCode Blue or Go Home!



Re: Lemote Fuloong

2012-07-05 Thread Code Blue
On Thu, Jul 05, 2012 at 02:15:06PM +, Code Blue wrote:
 On Thu, Jul 05, 2012 at 10:59:54AM -0300, Daniel Bolgheroni wrote:
  On Thu, Jul 05, 2012 at 12:12:43PM +, Code Blue wrote:
   
   |library c.64.1 not found
   | /usr/lib/libc.so.65.0 (system): bad major
  
  Your mirror is probably not so current. Try using another mirror.
 
 I tried 2 so far but I will try another one. Do you happen to know one that
 is surely current? Thanks.

I tried downloading from 
ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/`machine -a`/

and I am still getting the same errors. 

-- 
   _
ASCII ribbon campaign ( ) Please follow up to the mailing list
 against HTML e-mail   X   
   and proprietary/ \  Mutt.org
 attachmentsCode Blue or Go Home!



Re: Lemote Fuloong

2012-07-05 Thread Code Blue
   I was running fine on 5.1 but based on the comment from the previous 
   poster
   I reinstalled the snapshot (5.2). I was then unable to install any 
   packages
   from snapshots because of library errors. For example:
  
   # pkg_add mutt-1.5.21p0v0-sasl
  
   Can't install libiconv-1.14 because of libraries
   |library c.64.1 not found
   | /usr/lib/libc.so.65.0 (system): bad major
   Can't install qdbm-1.8.78: can't resolve libiconv-1.14
   Can't install cyrus-sasl-2.1.25p3 because of libraries
   Can't install gettext-0.18.1p1: can't resolve libiconv-1.14
   Can't install lmutt-1.5.21p0v0-sasl: can't resolve 
   cyrus-sasl-2.1.25p3,libiconv-1.14,qdbm-1.8.78,gettext-0.18.1p1
  
   I don't know whether I should reinstall 5.1 and use it until 5.2 comes out
   or whether I should continue and try to track -current and see if the 
   issues
   are resolved, but I am not looking forward to compiling much source given
   the lack of framebuffer acceleration! I used to track -stable on i386 but 
   I
   have been away from OpenBSD for a while so I am a little rusty on all
   this.
  
   Are you running -current or 5.1 and since you are using it for a server 
   and
   it is working fine for you, what would you recommend?
  

 This is mostly caused by the relatively slow hardware. Packages take
 time to build. In almost all cases, the old packges you have installed
 continue to work fine. Patience is a virtue ;-)

Yes but since I installed from the snapshot I have no old packages! This
was a clean install on new hardware and now I cannot install any packages at
least not any I have tried. 

Are you running -current or 5.1? Do you happen to know if -current has any
advantages over 5.1 for a development machine? Thanks.

-- 
   _
ASCII ribbon campaign ( ) Please follow up to the mailing list
 against HTML e-mail   X   
   and proprietary/ \  Mutt.org
 attachmentsCode Blue or Go Home!



Re: Lemote Fuloong

2012-07-05 Thread Code Blue
  Are you running -current or 5.1? Do you happen to know if -current has any
  advantages over 5.1 for a development machine? Thanks.
 
 Yes, you get rthreads for example.

Thanks.



Re: Lemote Fuloong

2012-07-05 Thread Code Blue
On Thu, Jul 05, 2012 at 06:05:48PM +0200, Tomas Bodzar wrote:
 On Thu, Jul 5, 2012 at 5:40 PM, Code Blue codeb...@inbox.lv wrote:
  On Thu, Jul 05, 2012 at 02:15:06PM +, Code Blue wrote:
  On Thu, Jul 05, 2012 at 10:59:54AM -0300, Daniel Bolgheroni wrote:
   On Thu, Jul 05, 2012 at 12:12:43PM +, Code Blue wrote:
   
|library c.64.1 not found
| /usr/lib/libc.so.65.0 (system): bad major
  
   Your mirror is probably not so current. Try using another mirror.
 
  I tried 2 so far but I will try another one. Do you happen to know one that
  is surely current? Thanks.
 
  I tried downloading from 
  ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/`machine -a`/
 
  and I am still getting the same errors.
 
 It may mean as now it's Beta phase that packages are not yet build
 (can be confirmed only by devs) or are in process of build for your
 platform so the question is if you can wait. If not you can build them
 on your system. Result will be package anyway.

Ok I don't mind trying to build from ports if there are ports for the few
apps I want at this point. If that doesn't work I will go back to
5.1. Thanks for the help, guys.



Re: Lemote Fuloong

2012-07-05 Thread Code Blue
On Thu, Jul 05, 2012 at 05:45:55PM +0200, Tomas Bodzar wrote:

 It shows that your system is newer then package you want to install.
 So look arround mirrors where is actual file/packages. It takes some
 time to distribute packages to all mirrors and build of packages for
 all platforms take some time as well.

Sounds reasonable but I have tried 4 different mirrors now including
ftp.openbsd.org. I am starting to wonder if there is something else wrong
and not sure what else to check. 

 Using snapshots is fine as you are doing just binary upgrades of
 system and packages and it's really very easy. In your case you can
 try compile from ports, but set FETCH_PACKAGES=Yes in /etc/mk.conf to
 avoid compilation of packages which are available as binary. Don't
 forget on http://www.openbsd.org/faq/faq15.html#PortsConfig

Thanks. 

-- 
   _
ASCII ribbon campaign ( ) Please follow up to the mailing list
 against HTML e-mail   X   
   and proprietary/ \  Mutt.org
 attachmentsCode Blue or Go Home!



Re: Lemote Fuloong

2012-07-05 Thread Code Blue
On Thu, Jul 05, 2012 at 05:26:54PM +, Miod Vallat wrote:
 
Aside from the bootblocks not installing
  from either 5.1 release or the 5.2. snapshot, everything seems to be 
  working.
 
 Care to share details about this?

In my first couple of installs on this new machine using 5.1 release and the
current snapshot I got the following messages at the end of the
installation:

Making all device nodes...done
mkdir: /mnt2/boot: Invalid argument
cp: /mnt2/boot/bsd: Invalid argument
Failed to install bootblocks.
You will not be able to boot OpenBSD from wd0

I fixed this by copying boot to the boot partition and PMON has no trouble
booting it.

The second install of the snapshot ended normally.

  Good question and I have no idea. Yes, it's a different CPU. The 2E and 2F
  are uniprocessors. The 3A is a quard.  Maybe the port maintainer will chime
  in.
 
 That would be me.

Yes I know. I thanked you in my first post. Thanks for porting this.

 The 3A systems are a completely different design. In addition to the
 CPU being multicore and using a completely different crossbar, the
 northbridge is now an AMD chip. A lot of work is needed to run on it,
 which is not worth starting until these systems are readily available.
 
 Unfortunately it seems Lemote can not produce enough of them for the
 foreign market, and I am told the ATX motherboard flavour (which would
 be much more interesting for server systems, or simply to use better
 disks than 2.5 ones) is not intended to be sold outside China.

Thanks for the update.



Re: Lemote Fuloong

2012-07-05 Thread Code Blue
On Thu, Jul 05, 2012 at 08:59:50PM +0200, Otto Moerbeek wrote:
 On Thu, Jul 05, 2012 at 05:50:02PM +, Code Blue wrote:
 
  On Thu, Jul 05, 2012 at 05:26:54PM +, Miod Vallat wrote:
   
  Aside from the bootblocks not 
installing
from either 5.1 release or the 5.2. snapshot, everything seems to be 
working.
   
   Care to share details about this?
  
  In my first couple of installs on this new machine using 5.1 release and the
  current snapshot I got the following messages at the end of the
  installation:
  
  Making all device nodes...done
  mkdir: /mnt2/boot: Invalid argument
  cp: /mnt2/boot/bsd: Invalid argument
  Failed to install bootblocks.
  You will not be able to boot OpenBSD from wd0
 
 Were this whole disk installs? Please share some more details.

No, as you probably know the disk is now 160G on the Fuloong. I couldn't
imagine needing so much space for my intended use of OpenBSD so I decided to
dual boot OpenBSD and some flavor of Linux. While I still had the original
preinstalled Linux available I partitioned the drive for my OpenBSD and
future Linux install and then did the OpenBSD installation in the OpenBSD
partition. Custom layout.

  I fixed this by copying boot to the boot partition and PMON has no trouble
  booting it.
  
  The second install of the snapshot ended normally.
 
 Second install of the same snap?

Yes, and I wondered if somehow the installer detected I had boot saved in an
ext2 partition (which was not true of the first two installs but was by the
third install, which was the second snapshot install), but I really can't
imagine how it would know.

-- 
   _
ASCII ribbon campaign ( ) Please follow up to the mailing list
 against HTML e-mail   X   
   and proprietary/ \  Mutt.org
 attachmentsCode Blue or Go Home!



Lemote Fuloong

2012-07-04 Thread Code Blue
Thanks to the OpenBSD team and Miod Vallat for the Loongson port.

I am trying to put together a MIPS development machine and I installed
OpenBSD 5.1. I didn't see a change log for the Loongson snapshot referenced
from the OpenBSD Loongson page so I don't know if there are any relevant
changes for my intended use or whether the snapshots are supposed to be
experimental. Which version should I use and should I be tracking current
for this machine? Thanks.

-- 
   _
ASCII ribbon campaign ( ) Powered by Lemote Fuloong
 against HTML e-mail   X   MIPS and OpenBSD
   and proprietary/ \  Mutt.org
 attachmentsCode Blue or Go Home!