NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-sparc64/57290
Thanks. I actually didn't have any luck with the -STABLE iso, NetBSD
reported
[ 1.0000000] virtio0 at pci2 dev 1 function 0
[ 1.0000000] virtio0: block device (id 2, rev. 0x01)
[ 1.0000000] ld0 at virtio0virtio0: feature negotiation failed
[ 1.0000000] : features: 0
[ 1.0000000] virtio0: virtio configuration failed
So I re-downloaded the NetBSD-daily/HEAD/latest one, and with a qemu
compiled freshly from git today, and reinstalled. For the record build
date was
NetBSD 10.99.12 (GENERIC) #0: Sun Dec 8 07:53:18 UTC 2024
The following are the http site, directory, user, and password that
will be
used. If "user" is "ftp", then the password is not needed.
a: Host nycdn.NetBSD.org
>b: Base directory pub/NetBSD-daily/HEAD/latest
c: Binary set directory /sparc64/binary/sets
d: Source set directory /source/sets
e: File extension .tgz
f: User ftp
g: Password
h: Proxy
i: Transfer directory /usr/INSTALL
j: Delete after install No
k: Configure network
l: Exit
x: Get Distribution
It went well, I still had the issue where it reports
4.2949196] WARNING: 1 error while detecting hardware; check system
log.
[ 4.3045692] FATAL: boot device not found, check your firmware
settings!
but now I just typed ld0 at the "root device:" prompt (I don't think I
even realized it was a prompt, lol) and accept the other defaults and it
worked and booted fine.
WRT to 57289, I was dubious at first that it might need support in
qemu's OpenBIOS because it now says it can't manage this device before
we even try to boot NetBSD:
~/qemu qemu-system-sparc64 -cdrom ./NetBSD-10.99.12-sparc64.iso -m
2048 -net nic,model=virtio-net-pci -net user -nographic -boot d
OpenBIOS for Sparc64
Cannot manage 'ethernet controller' PCI device type 'network':
1af4 1041 (2 0 0)
BUT the latest 10.99.12 ISO works - I am able to ifconfig it and ping
host.
# ifconfig vioif0 10.0.2.15/24
#
#
# ifconfig -a
vioif0: flags=0x8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ec_capabilities=0x1<VLAN_MTU>
ec_enabled=0
address: 52:54:00:12:34:56
status: active
inet6 fe80::5054:ff:fe12:3456%vioif0/64 flags 0 scopeid 0x1
inet 10.0.2.15/24 broadcast 10.0.2.255 flags 0
lo0: flags=0x8048<LOOPBACK,RUNNING,MULTICAST> mtu 33112
status: active
# ping 10.0.2.2
PING 10.0.2.2 (10.0.2.2): 56 data bytes
64 bytes from 10.0.2.2: icmp_seq=0 ttl=255 time=15.117060 ms
64 bytes from 10.0.2.2: icmp_seq=1 ttl=255 time=2.456240 ms
64 bytes from 10.0.2.2: icmp_seq=2 ttl=255 time=1.559070 ms
So that is great news!
--
Michael Russo | Systems Engineer | PaperSolve, Inc.
office (718) 477 8906 | direct (332) 228 1817
Your random quote for today:
Non-Determinism is not meant to be reasonable.
-- M. J. 0'Donnell
-----Original Message-----
From: George Matsumura via gnats <gnats-admin%NetBSD.org@localhost>
Reply-To: gnats-bugs%netbsd.org@localhost
To: port-sparc64-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-
bugs%netbsd.org@localhost, mike%papersolve.com@localhost
Subject: Re: port-sparc64/57290
Date: 12/07/2024 07:35:01 PM
The following reply was made to PR port-sparc64/57290; it has been noted
by GNATS.
From: George Matsumura <gorg%gorgnet.net@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc:
Subject: Re: port-sparc64/57290
Date: Sat, 7 Dec 2024 17:30:51 -0700
Greetings,
I apologize for the late reply.
The changes in question seem to have now been integrated into the
netbsd-10
branch. Therefore, you should be able to use this image instead now:
https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-10/202412041400Z/images/NetBSD-10.0_STABLE-sparc64.iso
As for the issues you have been having most recently, I would just want
to make
sure that you were downloading the binary sets from the netbsd-10
branch in
addition to just the install image.
For example, I think you would use:
nycdn.netbsd.org
for "Host"
pub/NetBSD-daily/netbsd-10/202412041400Z
for "Base Directory"
/sparc64/binary/sets
for "Binary set directory"
and
/source/sets/
for "Source set directory"
in sysinst to use a fixed revision on the netbsd-10 branch if you are
installing via http.
If using new sets does not help with root device detection, I would
think you
could type something like "ld0" at the "root device:" prompt, although
I am not
sure this would address the other issues.
Also, would the discussion in this issue also apply to your PR #57289?:
https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=57289
I hope this is useful. Please let me know if the issues persist.
Regards,
George
Home |
Main Index |
Thread Index |
Old Index