I know that setting up a disk with GPT partitions and UEFI booting isn’t
supported (yet) in NetBSD. But it seems close and I’d appreciate some hints.
Picked up a cheap laptop that only supports UEFI booting on the internal eMMC
disk. Although it has Legacy boot support, that only works on
inc...@free.fr> wrote:
>
> Hi,
>
> I have it working on two such laptops; here are a couple of comments
> which could help.
>
> Robert Nestor <rnes...@mac.com> writes:
>
>> newfs_msdos -F 16 /dev/rdk0
>
> I didn't specify -F 16 here and this partiti
I have to use an xorg.conf file on my AMD64 system to get my monitor working.
It works for my under 7.0.1. What I’ve discovered though is the BusID probing
for where things are attached seems to be different between different versions
of X, and not having it set correctly will cause my
resurfaces,
although it only happens about 10% of the time.
-bob
On Apr 16, 2017, at 9:10 PM, Kimihiro Nonaka <nona...@gmail.com> wrote:
> On Sun, Apr 16, 2017 at 9:03 PM, Robert Nestor <rnes...@mac.com> wrote:
>
>> I’ve been running -current on a new laptop and
Nonaka <nona...@gmail.com> wrote:
> On Wed, Apr 19, 2017 at 10:57 AM, Robert Nestor <rnes...@mac.com> wrote:
>
>> Have done 3 or 4 dozen reboots with this patch and no failures so far.
>> Without the patch I see the problem about 10% of the time. Will continue
>>
com> wrote:
> On Sun, Apr 16, 2017 at 9:03 PM, Robert Nestor <rnes...@mac.com> wrote:
>
>> I’ve been running -current on a new laptop and have installed a number of
>> snapshots since 7.99.59. With the 7.99.67 snapshot I’m seeing the message
>> “iwm0: fatal
I fought with this running -current a few months ago on an amd64 system. Never
did get it to work for me, but one suggestion I got that seemed like a
responsible explanation was it was the number of modules that were in the
object environment. Since people have different packages installed on
Not sure if this helps but noticed the user is using a cable modem connected to
Time Warner. I have the same type of connection on my amd64 system and I’ve
noticed similar issues of not always being able to get connected via dhcp. And
like the original poster I sometimes switch between
I’m running -current on a new laptop (it won’t run anything earlier), and now
trying to get X up and working. Tried “Xorg” and then looked at the Xorg.0.log
file and find “No screens”. So I cobbled together an xorg.conf file and then I
get a “No devices found” and with that I get a “No
Maybe slightly off-topic, but has anyone tried setting up their own personal
cloud and running NetBSD in it under the antsle device?
http://antsle.com
It claims to be designed for the developer but may not have the power to run
virtual machines for a production environment. But they’re
Trying to install NetBSD 8.0_RC1 on an HP 6200 system and ran into a problem
I’ve never seen before.
Got the system installed with XDM, but X didn’t find all the possible screen
resolutions. I’m used to that, so I edited an xorg.conf file and that solved
the problem. I then tried installing
I’m not convinced that booting in UEFI mode actually works in 8.0_RC1. The
uefi-install image is constructed with both UEFI and BIOS boot loaders so it
can boot in either mode. The system I’m testing on gives me the capability to
disable UEFI or Legacy/BIOS boot capability. When I disable
I was using gdb to debug a program on Linux and saw something similar. The
program has a large dynamically allocated data section. What I discovered is
there’s some internal buffer or storage constraint in gdb of about 350k. My
program has about 380K of data and with gdb running I was
Trying to install -current on an AMD64 system that has been running NetBSD for
years. Having problems with X. For some reason my setup never works correctly
without having to install a customized xorg.conf file, and every new release of
X acts differently. So it’s always a treasure hunt to
Update and new issues. Tried the install from the USB image and ran “sysinst”
from there and it worked for installing the base system.
Two issues though: 1) pkgin install reported an error - no libcrypt.so found,
and 2) pkgsrc install failed as it downloaded in “.tar.gz” format (I think),
but
This was on an amd64 system, but it may be a cockpit error on my part, although
I’ve been doing installs this way for some time.
I downloaded the CD image and transferred it to a USB stick Should have used
the USB image instead, but since I wasn’t booting it that didn’t seem to
matter. Then
.
-bob
On Nov 5, 2018, at 8:50 AM, Martin Husemann wrote:
> On Mon, Nov 05, 2018 at 08:36:37AM -0600, Robert Nestor wrote:
>> Two issues though: 1) pkgin install reported an error - no
>> libcrypt.so found, and 2) pkgsrc install failed as it downloaded in
>> ?.ta
Downloaded today’s -current install image for amd64 and tried booting it on my
HP 6200 MT. Booting the install image hangs on this system which has been
running NetBSD 7.0, 7.2, 8.0 and 8.0_STABLE just fine. The boot hangs right
after it reports finding “attimer0” or right after finding
Tried downloading and installing 8.99.25 this morning and noticed that it fails
because the installation utility (sysinst) doesn’t support the new tar.xz
extension. PR pkg/53697 seems to address this in the sysutil/sysupgrade
utility. Is another PR needed to get this addressed in the sysinst
Saw the traffic about doing an install on a GPT/UEFI system that referenced the
setup I’d used and posted about a year ago. It worked back then.
So I dug out my old script, updated it to do an install of NetBSD 8.0_RC1 on a
system with GPT disk layout and UEFI booting. The script put
While digging further into this I discovered that the UEFI install images boot
up in Legacy BIOS mode, not in UEFI mode. Disabling Legacy BIOS boot on my
system before trying to boot the install image resulted in not being able to
boot up at all. So even though the image contains and EFI
My system has multiple disks which allow me to install various versions of
NetBSD. The disks are large and the system supports EFI, so for some time I’ve
been doing installations with GPT wedges and using either BIOS or EFI setups to
boot with. Early on the EFI support didn’t work on this HW
As Matthew suggested here, replacing my 9.0_BETA kernel with one from the
-current distribution I was trying to install on a new disk worked perfectly.
Thanks!
-bob
On Nov 3, 2019, at 2:15 PM, matthew green wrote:
>> [1] Bad system call chroot /targetroot useradd -c
>>
>> Has
I tried enabling this option on my amd64 system running a fairly recent version
of -current off a new SSD. While building some packages I noticed a lot of
recoverable disk I/O errors (mainly on writes) on the SSD disk. After
disabling this option and doing a similar set of package build I
I’ve been doing some more testing of NVMM on a system running NetBSD-9.99.41.
Basically I’m trying to install a Mac OS-X 10.6 system. I’m doing this on a
Mac that I own with the retail distribution DVD that came with that Mac, so I
believe I’m compliant with Apple’s EULA. This installation
I seem to recall seeing this same problem on a LinuxMint 19.x system and it
popped up at the time of the Daylight Savings time switchover. I’m in the US
Central timezone.
:40 PM, Andrew Doran wrote:
> On Sun, Jan 19, 2020 at 12:21:06PM -0600, Robert Nestor wrote:
>
>> Thanks! I followed Andrew?s instructions and got a photo of the stack
>> trace and sent it to him directly. Hope it helps him figure out what?s
>> happening.
&
Thanks! I followed Andrew’s instructions and got a photo of the stack trace
and sent it to him directly. Hope it helps him figure out what’s happening.
-bob
On Jan 19, 2020, at 11:29 AM, Greg Troxel wrote:
> Robert Nestor writes:
>
>> Sorry for not being specific. When I do
, Greg Troxel wrote:
> Robert Nestor writes:
>
>> I’ve downloaded and installed 9.99.38 (Jan 17 build) and the original
>> problem I was seeing with “git” is gone. However, I’m now seeing a
>> new problem with file corruption, but it only seems to happen when I
>>
I’ve downloaded and installed 9.99.38 (Jan 17 build) and the original problem I
was seeing with “git” is gone. However, I’m now seeing a new problem with file
corruption, but it only seems to happen when I do a normal shutdown. If I do a
“shutdown -r now” to shutdown and reboot the system I
I’ve got NetBSD-9.99.17 (amd64) installed and it has been running without any
problems which i have been using to work with NVMM. I do package builds on it
using pkgsrc-current and also do the build of wip/qemu-nvmm.
This morning I installed NetBSD-9.99.38 (Jan 15th build) on another disk.
Thanks. Saw the response from Thomas this morning and I’m doing a new
installation now. Hope that’s the problem because I was really impressed with
the performance improvements.
-bob
On Jan 17, 2020, at 8:43 AM, m...@netbsd.org wrote:
> On Thu, Jan 16, 2020 at 07:03:14PM -0600, Rob
Yes, and it appears to be different from what Chavdar has on his slightly
earlier system.
Source Bits Type Flags
/dev/random 0 ??? estimate, collect, v
ums0 0 tty estimate, collect, v, t, dt
ukbd0 0 tty estimate,
Thanks! I’ll give your suggestions a try.
-bob
On May 15, 2020, at 7:27 AM, Martin Husemann wrote:
> On Fri, May 15, 2020 at 06:27:41AM -0500, Robert Nestor wrote:
>> Yes, and it appears to be different from what Chavdar has on his slightly
>> earlier system.
>> seed
Thu, May 14, 2020 at 11:53:04AM -0500, Robert Nestor wrote:
>> Ran into an interesting problem trying to build lang/rust from both -current
>> and 2020Q1 pkgsrc. On a NetBSD installation of 9.99.45 kernel and user
>> land, the builds succeed. Under 9.99.60 kernel and user lan
Ran into an interesting problem trying to build lang/rust from both -current
and 2020Q1 pkgsrc. On a NetBSD installation of 9.99.45 kernel and user land,
the builds succeed. Under 9.99.60 kernel and user land the builds fail.
The failure doesn’t give much of a clue about what’s happened. The
I’ve been running 9.99.72 on an amd64 system for since it was posted, and I
have my /home mounted on an NFS share. I’m not using sqlite3, just a pretty
basic installation. The disk I’m running from is an SSD. Just leaving the
system sit idle over a few days to week or so and doing nothing
I received a couple of messages off list that suggested a few things and it
prompted me to try investigating further with just components found in NetBSD.
This test was run on a fairly recent NetBSD build of 9.99.70. I downloaded the
amd64 images for 9.99.71 (the ISO and IMG files), and tried
On Aug 23, 2020, at 1:57 PM, Chavdar Ivanov wrote:
> On Sun, 23 Aug 2020 at 15:41, Robert Nestor wrote:
>>
>> I received a couple of messages off list that suggested a few things and it
>> prompted me to try investigating further with just components found in
>&g
Further adventures with QEMU booting of non-NetBSD CDs and virtual HDs.
I've had some success, but have also uncovered a couple of bugs, one minor and
two rather significant. To keep things simple here, I've only addressed the
problems I've seen in trying to boot the rEFInd CD and MSDOS image
On Aug 24, 2020, at 1:32 PM, Chavdar Ivanov wrote:
> On Mon, 24 Aug 2020 at 15:08, Robert Nestor wrote:
>>
>>
>> On Aug 23, 2020, at 1:57 PM, Chavdar Ivanov wrote:
>>
>>> On Sun, 23 Aug 2020 at 15:41, Robert Nestor wrote:
>>>>
>>>
On Aug 24, 2020, at 1:32 PM, Chavdar Ivanov wrote:
> On Mon, 24 Aug 2020 at 15:08, Robert Nestor wrote:
>>
>>
>> On Aug 23, 2020, at 1:57 PM, Chavdar Ivanov wrote:
>>
>>> On Sun, 23 Aug 2020 at 15:41, Robert Nestor wrote:
>>>>
>>>
Stumbled over this trying to check on the format of a NetBSD CD. This is a
newly installed system of 9.99.69 downloaded two days ago with all the
installed packages rebuilt and installed under it, so everything is pretty much
up to date.
vndconfig -c vnd0 NetBSD-9.99.69-amd64.iso
Done but I may have put it into the wrong category - PR kern/0
On Aug 8, 2020, at 8:55 AM, Paul Goyette wrote:
> On Sat, 8 Aug 2020, Robert Nestor wrote:
>
>> Stumbled over this trying to check on the format of a NetBSD CD. This
>> is a newly installed system of 9.99
on
someone’s NetBSD blog.
-bob
On Aug 8, 2020, at 11:44 AM, Chavdar Ivanov wrote:
> On Sat, 8 Aug 2020 at 18:07, Robert Nestor wrote:
>>
>> My NFS is on a DS218+ Synology NAS which I believe is based on a version of
>> Linux. FreeNAS is based on FreeBSD I think, if that
ert Nestor wrote:
>>
>> Done but I may have put it into the wrong category - PR kern/0
>>
>> On Aug 8, 2020, at 8:55 AM, Paul Goyette wrote:
>>
>>> On Sat, 8 Aug 2020, Robert Nestor wrote:
>>>
>>>> Stumbled over this trying to chec
where I have /home
mounted which works for accessing files from Mac, Linux and NetBSD.
-bo
On Aug 8, 2020, at 11:01 AM, Chavdar Ivanov wrote:
> On Sat, 8 Aug 2020 at 17:52, Robert Nestor wrote:
>>
>> I didn’t realize at the time that the iso file I was using for this was on
With the recent changes to the Web pages I noticed that the link to the mailing
lists is no longer present in the “Support” area shown on the left hand side of
the main page. To find the mailing lists now it seems one has to select the
“Community” link and then click on the “mailing lists”
When setting up a new system I’ve used a script to populate most of my user
accounts. This has always worked fine up to and including 9.2, but with
9.99.92 downloaded the other day I’m getting errors. An example that worked
previously is something like:
useradd -m -c “User test” -s
to switch
between booting Windows and NetBSD on this system.
-bob
On Mar 1, 2022, at 8:40 AM, Martin Husemann wrote:
> On Tue, Mar 01, 2022 at 06:59:46AM -0600, Robert Nestor wrote:
>> Any ideas?
>
> When it does not find the boot device, you should get a boot prompt
> like:
I’ve got a stock HP6200 MT that I’m using. It has Windows-10 on WD0 and I’ve
been trying to install NetBSD on WD1. NetBSD-9.2 installs on WD1 and runs just
fine on this system, but I’ve run into an interesting problem trying to install
either 9.99.92 or 9.99.93. I’ve been installing from an
’m occasionally seeing the WDCTL_RST on WD0 that there was some discussion
about last Oct/Nov involving an autoconfigure IDENTIFY failed. This is with a
9.99.93 system downloaded just the other day. After reading the message
traffic on this from last Oct I’m assuming the delays that were
The boot issue I’m seeing on a VM in Linux with 9.99.96 was with a build from
2022-05-11, so I need to download a new set of file and try again. May take me
a week or so to get some results but I’ll report back when I get them.
Thanks for the hint!
-bob
On May 25, 2022, at 2:44 PM, matthew
Well, test went quicker than I expected. I downloaded the amd64 image for
9.99.97 (assuming it had the fix since it was built 2022-05-25). When I tried
booting the CD in a new VM it shows the same issue - the log shows it found the
cd but then it claims it can’t find the root device.
I first saw this issue on a system trying to install and run 9.92, and adding
the suggested AHCISATA_EXTRA_DELAY and disabling TPM seemed to fix it for me.
But then I tried 9.99.96 and saw the same problems and the fixes had no effect.
However I may have stumbled onto something that could be
Working on getting the console output from a system that consistently fails to
boot amd64 -current (it boots and runs 9.2 without any issues). I’ve got a
serial (null modem) cable, but I need to go from a serial port (on the test
system) to a USB-Serial converted port (on the capture system).
The USB Serial cable I’m trying to use came from Amazon. According to their
description it uses the PL2303 chipset, so ...
Following Michael’s advice I added this line to sys/dev/usb/usbdevs where other
Prolific devices were defined:
product PROLIFIC PL2303Y 0x23c3 PL2303 Serial
First, I was mistaken about this Prolific PL2303 USB Serial Adapter cable being
a null modem. It’s just a straight turn cable but I have a null modem dongle
attached to it on the DB-9 end.
As for the USB port on the system it’s attached to, this port has been used for
various other devices
I’ve got two AMD systems that are similar in configuration. An HP Z230 running
NetBSD 9.3 and an HP-6200 running NetBSD 10.0_BETA. On the 9.3 system I
converted/encoded my video library containing some old movies and TV shows
using ffmpeg4 with libx264 compression. It all converted just
I’ve been doing some testing running NetBSD 9.x and 10.x in a VM environment
and have noticed some differences in booting that might be related. The
testing I’ve done was using a fairly recent version of 10.0_BETA so similar
results _might_ be present in -current as well.
#
# Install
60 matches
Mail list logo
