Has anyone done a successful upgrade from Loongson 5.2 to 5.3? I've done
upgrades on numerous platforms and this is the only one I've ever had
problems with. The upgrade seemed to go fine and finish normally. After the
reboot it goes from the Lemote Dragon screen to a black screen and stops
A fresh install also doesn't boot and using PMON to boot into it fails the
same way as on the old install. Well crap. That was unexpected.
PMON boot -k /dev/fs/ext2@wd0/boot/boot
Loading file: /dev/fs/ext2@wd0/boot/boot (elf)
(elf)
0x81e2/44368 + 0x81e2ad50/4400(z) +
OpenBSD/loongson BOOT
Sorry if this is duplicated. Been a few hours since I sent it and did not
see it hit the list. Also did not find it on marc or gmane.
Has anyone done a successful upgrade from Loongson 5.2 to 5.3? I've done
upgrades on numerous platforms and this is the only one I've ever had
problems
but it booted and ran the installer?
On Wed, Jun 19, 2013 at 8:00 AM, John Long codeb...@inbox.lv wrote:
A fresh install also doesn't boot and using PMON to boot into it fails the
same way as on the old install. Well crap. That was unexpected.
PMON boot -k /dev/fs/ext2@wd0/boot/boot
Did not upgrade mine yet.
Wait for Miod's answer. He's the best person for knowledge on this platform.
Message du 19/06/13 17:09
De : John Long
A : misc@openbsd.org
Copie à :
Objet : Can't boot Loongson after upgrade from 5.2 - 5.3
Sorry if this is duplicated. Been a few hours since
An update...the bsd.rd kernel boots from / but not bsd. bsd from snapshots
also boots. Looks like there is some problem with bsd in loongson 5.3
release.
/jl
--
ASCII ribbon campaign ( ) Powered by Lemote Fuloong
against HTML e-mail X Loongson MIPS and OpenBSD
and proprietary/ \
Has anyone done a successful upgrade from Loongson 5.2 to 5.3? I've done
upgrades on numerous platforms and this is the only one I've ever had
problems with. The upgrade seemed to go fine and finish normally. After the
reboot it goes from the Lemote Dragon screen to a black screen and stops
A fresh install also doesn't boot and using PMON to boot into it fails the
same way as on the old install. Well crap. That was unexpected.
If a new install fails, now that's something unexpected. Will installing
5.2 (which used to work) boot again?
Miod
On Wed, Jun 19, 2013 at 07:53:30PM +, Miod Vallat wrote:
A fresh install also doesn't boot and using PMON to boot into it fails the
same way as on the old install. Well crap. That was unexpected.
If a new install fails, now that's something unexpected. Will installing
5.2 (which used
An update...the bsd.rd kernel boots from / but not bsd. bsd from snapshots
also boots. Looks like there is some problem with bsd in loongson 5.3
release.
Where did you get your 5.3 release from? Did you check its md5?
Miod
On Wed, Jun 19, 2013 at 08:10:17PM +, Miod Vallat wrote:
An update...the bsd.rd kernel boots from / but not bsd. bsd from snapshots
also boots. Looks like there is some problem with bsd in loongson 5.3
release.
Where did you get your 5.3 release from? Did you check its md5?
That's
On Wed, Jun 19, 2013 at 11:17:57AM -0700, Bryan Irvine wrote:
but it booted and ran the installer?
Yes. There appears to be a problem with the kernel.
I just tried something interesting. I booted the installer and used the
shell to save bsd as obsd on the installed system and then ln -s bsd.rd
Where did you get your 5.3 release from? Did you check its md5?
That's it! Thank you.
I got release from ftp.openbsd.org. But the sha256 for bsd doesn't match
what's in SHA256. I'm used to ignoring those messages from snapshots so I
didn't catch it.
Cluebatting myself...apparently it was
Hi,
I'm using Lenovo Thinkpad X200. Previously installed 5.0amd64 using CD
then used bsd.rd method to upgrade to 5.1, 5.2 and finally 5.3. My 5.2 was
dandy and all, until I upgraded to 5.3 last night. bsd.rd upgrade went
smoothly, until rebooted the machine. Then the machine just stuck
On 2013-05-04, Zulkarnain als...@gmail.com wrote:
Hi,
I'm using Lenovo Thinkpad X200. Previously installed 5.0amd64 using CD
then used bsd.rd method to upgrade to 5.1, 5.2 and finally 5.3. My 5.2 was
dandy and all, until I upgraded to 5.3 last night. bsd.rd upgrade went
smoothly, until
On Sat, 4 May 2013, Dawe wrote:
On May 04, 2013 19:14, Zulkarnain wrote:
Hi,
I'm using Lenovo Thinkpad X200. Previously installed 5.0amd64 using CD
then used bsd.rd method to upgrade to 5.1, 5.2 and finally 5.3. My 5.2 was
dandy and all, until I upgraded to 5.3 last night. bsd.rd
russ...@dotplan.dyndns.org (russell), 2012.11.01 (Thu) 21:59 (CET):
On 11/01/2012 07:04 AM, Kurt Mosiejczuk wrote:
Otto Moerbeek wrote:
untarring the sets and copying the kernel by hand is not recommended.
I used the perfect phrase for this in a presentation on PF a week ago:
You
On 2012-11-02, Andrew Klettke aklet...@opticfusion.net wrote:
Just upgraded to 5.2 on one of our backup firewalls, and we are having
issues with hosts that are being checked with ICMP:
This should have been fixed post-5.2, please try this diff against
/usr/src/usr.sbin/relayd and let me know
Applied the patch, compiled and installed the new version of relayd, and
everything looks good again. Thanks much!
Thanks,
Andrew Klettke
Systems Admin
Optic Fusion
On 11/05/2012 09:20 AM, Stuart Henderson wrote:
On 2012-11-02, Andrew Klettke aklet...@opticfusion.net wrote:
Just upgraded to
On 11/01/2012 07:04 AM, Kurt Mosiejczuk wrote:
Otto Moerbeek wrote:
untarring the sets and copying the kernel by hand is not recommended.
I used the perfect phrase for this in a presentation on PF a week ago:
You wouldn't ever do this... unless maybe you hate yourself.
--Kurt
Err, I do
Just upgraded to 5.2 on one of our backup firewalls, and we are having
issues with hosts that are being checked with ICMP:
Nov 2 14:58:38 fw02 relayd[30621]: table radius: 1 added, 1 deleted, 0
changed, 0 killed
Nov 2 14:58:38 fw02 relayd[5280]: recv_icmp: forged icmp packet?
Nov 2
/ Tyler Morgan wrote on Wed 31.Oct'12 at 20:04:11 -0700 /
Don't do it! Seriously, the upgrade process is easy, and is worth
becoming familiar with. At least give it a shot since you're
planning on reinstalling anyway. I think you'll be pleasantly
surprised!
For a long time I did fresh
/ Tyler Morgan wrote on Wed 31.Oct'12 at 20:04:11 -0700 /
Don't do it! Seriously, the upgrade process is easy, and is worth
becoming familiar with. At least give it a shot since you're
planning on reinstalling anyway. I think you'll be pleasantly
surprised!
Just out of curiosity, do you
Den Thu, 1 Nov 2012 08:11:26 +
skrev Jamie Paul Griffin ja...@kode5.net:
/ Tyler Morgan wrote on Wed 31.Oct'12 at 20:04:11 -0700 /
Don't do it! Seriously, the upgrade process is easy, and is worth
becoming familiar with. At least give it a shot since you're
planning on reinstalling
Den Thu, 1 Nov 2012 09:34:50 +0100
skrev Anders Trobäck b...@troback.com:
Den Thu, 1 Nov 2012 08:11:26 +
skrev Jamie Paul Griffin ja...@kode5.net:
/ Tyler Morgan wrote on Wed 31.Oct'12 at 20:04:11 -0700 /
Don't do it! Seriously, the upgrade process is easy, and is worth
On Thu, Nov 01, 2012 at 09:34:50AM +0100, Anders Trob?ck wrote:
Den Thu, 1 Nov 2012 08:11:26 +
skrev Jamie Paul Griffin ja...@kode5.net:
/ Tyler Morgan wrote on Wed 31.Oct'12 at 20:04:11 -0700 /
Don't do it! Seriously, the upgrade process is easy, and is worth
becoming familiar
Don't do it! Seriously, the upgrade process is easy, and is worth
becoming familiar with. At least give it a shot since you're
planning on reinstalling anyway. I think you'll be pleasantly
surprised!
Just out of curiosity, do you think the easiest method is to use the
bds.rd
/ Anders Trobäck wrote on Thu 1.Nov'12 at 9:40:43 +0100 /
Den Thu, 1 Nov 2012 09:34:50 +0100
skrev Anders Trobäck b...@troback.com:
Den Thu, 1 Nov 2012 08:11:26 +
skrev Jamie Paul Griffin ja...@kode5.net:
/ Tyler Morgan wrote on Wed 31.Oct'12 at 20:04:11 -0700 /
Don't
Otto Moerbeek wrote:
untarring the sets and copying the kernel by hand is not recommended.
I used the perfect phrase for this in a presentation on PF a week ago:
You wouldn't ever do this... unless maybe you hate yourself.
--Kurt
On Thu, Nov 01, 2012 at 08:11:26AM +, Jamie Paul Griffin wrote:
/ Tyler Morgan wrote on Wed 31.Oct'12 at 20:04:11 -0700 /
Don't do it! Seriously, the upgrade process is easy, and is worth
becoming familiar with. At least give it a shot since you're
planning on reinstalling anyway. I
On Thu, Nov 01, 2012 at 09:34:50AM +0100, Anders Trob?ck wrote:
Den Thu, 1 Nov 2012 08:11:26 +
skrev Jamie Paul Griffin ja...@kode5.net:
/ Tyler Morgan wrote on Wed 31.Oct'12 at 20:04:11 -0700 /
Don't do it! Seriously, the upgrade process is easy, and is worth
becoming familiar
On 10/31/12 00:13, Daniel Melameth wrote:
On Tue, Oct 30, 2012 at 8:55 PM, Matt M. cmorrow...@gmail.com wrote:
Yesterday I upgraded from 5.1-release to -current. Is there any need to
upgrade to 5.2-release? Could this cause issues since -current is really
newer than what's on the 5.2 media
/ Nick Holland wrote on Wed 31.Oct'12 at 7:03:48 -0400 /
On 10/31/12 00:13, Daniel Melameth wrote:
On Tue, Oct 30, 2012 at 8:55 PM, Matt M. cmorrow...@gmail.com wrote:
Yesterday I upgraded from 5.1-release to -current. Is there any need to
upgrade to 5.2-release? Could this cause issues
to upgrade to 5.2-release? Could this cause issues since
-current is really newer than what's on the 5.2 media?
You are now running bleeding edge software/what will evolve and
become 5.3. Upgrading this machine to 5.2 will actually be a
downgrade and this is unsupported.
exactly. Please read
On 2012-10-31, Jamie Paul Griffin ja...@kode5.net wrote:
Is it best to
remove all packages prior to upgrade and then reinstall them or
should we simply upgrade the packges using pkg_add -i once the
upgrade has been completed?
pkg_add -u -
/ Stuart Henderson wrote on Wed 31.Oct'12 at 15:56:31 + /
On 2012-10-31, Jamie Paul Griffin ja...@kode5.net wrote:
Is it best to
remove all packages prior to upgrade and then reinstall them or
should we simply upgrade the packges using
On 10/31/2012 9:48 AM, Jamie Paul Griffin wrote:
/ Stuart Henderson wrote on Wed 31.Oct'12 at 15:56:31 + /
On 2012-10-31, Jamie Paul Griffin ja...@kode5.net wrote:
Is it best to
remove all packages prior to upgrade and then reinstall them
Yesterday I upgraded from 5.1-release to -current. Is there any need to
upgrade to 5.2-release? Could this cause issues since -current is really
newer than what's on the 5.2 media?
On Tue, Oct 30, 2012 at 8:55 PM, Matt M. cmorrow...@gmail.com wrote:
Yesterday I upgraded from 5.1-release to -current. Is there any need to
upgrade to 5.2-release? Could this cause issues since -current is really
newer than what's on the 5.2 media?
You are now running bleeding edge software
On Sat, 20 Oct 2012 23:05:20 -0400
Nick Holland n...@holland-consulting.net wrote:
On 10/19/12 23:25, Matt Morrow wrote:
Does anyone know when the upgrade guides are usually posted? I know
we're a couple of weeks away from the release, but I also thought I
read that 5.2 cds had already
On 10/21/12 07:29, Rares Aioanei wrote:
On Sat, 20 Oct 2012 23:05:20 -0400
Nick Holland n...@holland-consulting.net wrote:
On 10/19/12 23:25, Matt Morrow wrote:
Does anyone know when the upgrade guides are usually posted? I know
we're a couple of weeks away from the release, but I also
On 10/19/12 23:25, Matt Morrow wrote:
Does anyone know when the upgrade guides are usually posted? I know we're a
couple of weeks away from the release, but I also thought I read that 5.2
cds had already been shipped to some locations, which would imply that it's
pretty much ready for release?
Does anyone know when the upgrade guides are usually posted? I know we're a
couple of weeks away from the release, but I also thought I read that 5.2
cds had already been shipped to some locations, which would imply that it's
pretty much ready for release? I figured I'd take some time to look over
43 matches
Mail list logo
