Re: Problems loading NetBSD on an ANTSLE box
I’ve got one of those boxes and I did have NetBSD loaded on it not long after I got it. I bought one with the minimal internal disk setup, two 120G Kingston SSDs, and installed my own additional disk drives for more storage. I was using an earlier version of NetBSD and bought it to set up some xen images, but then found out the SOC Antsle uses doesn’t support everything needed to run all the modes xen is capable of. Had the same problem with trying to install FreeBSD on it and ended up just putting MintLinux on it instead. I think it works better with MintLinux than the OS they shipped with it, but it still isn’t what I thought when I bought it. It sounds to me like you’ve got a HW problem though. You didn’t by chance open the box to do any upgrades did you? When you pull it apart you have to be very careful of some of the springs, screws and make sure you replace the thermal paste for the CPU. -bob
Re: Problems loading NetBSD on an ANTSLE box
So are you trying to install NetBSD as an Antlet or trying to install to the bare metal? In my installs I totally wiped out AntOS and installed to bare metal. If you’re installing to bare metal have you tried installing to each of the SSDs? AntOS makes the two SSDs look like a single disk using ZFS, but if you install over the top of AntOS then you’ll have two disks and can choose either one to install to. BTW, I found Antsle support to be pretty much useless. They wouldn’t give me any details on almost anything. They really don’t want their customers opening the box, installing their own upgrades or removing AntOS from the box. They’d like to keep you boxed into just using the system the way they intended which is to run everything under AntOS and have them do any HW upgrades for you. On Dec 14, 2018, at 11:44 AM, Palmer, John wrote: > No - I didn't do anything like that (open it up). I have one Linux instance > running on it and its fine. I've installed NetBSD versions 3.0, 4.0.1, 5.0, > 7.0 and 8.0 and they all have the same issue with the file systems. > > I'm not using Xen - just the standard install. > > -Original Message- > From: Robert Nestor > Sent: Friday, December 14, 2018 11:28 > To: Palmer, John ; NetBSD Users > Subject: Re: Problems loading NetBSD on an ANTSLE box > > I've got one of those boxes and I did have NetBSD loaded on it not long after > I got it. I bought one with the minimal internal disk setup, two 120G > Kingston SSDs, and installed my own additional disk drives for more storage. > > I was using an earlier version of NetBSD and bought it to set up some xen > images, but then found out the SOC Antsle uses doesn't support everything > needed to run all the modes xen is capable of. Had the same problem with > trying to install FreeBSD on it and ended up just putting MintLinux on it > instead. I think it works better with MintLinux than the OS they shipped > with it, but it still isn't what I thought when I bought it. > > It sounds to me like you've got a HW problem though. You didn't by chance > open the box to do any upgrades did you? When you pull it apart you have to > be very careful of some of the springs, screws and make sure you replace the > thermal paste for the CPU. > > -bob
Problems loading NetBSD on an ANTSLE box
I'm trying out one of those Antsle virtual server boxes with NetBSD and am getting issues with file system becoming corrupt almost immediately. When I attach the standard .ISO as the boot device and run the standard sysinst scripts, it cannot even unpack and install the system before freezing up. A reboot and fsck show thousands of file system errors. I've been attempting to get assistance from the Antsle tech support for months but they have not provided a solution. Has anyone had any luck loading NetBSD on an Antsle box? John
Re: wscons.conf ledstate and screen issues
Rocky Hotas wrote: > Second issue is about the creation of new screens. I modified from default > the wscons.conf file as follows: > > #screen 0 - vt100 > screen 1- vt100 > screen 2- vt100 > screen 3- vt100 > screen 4- vt100 > screen 5- vt100 > screen 6- vt100 > screen 7- vt100 > screen 8- - > > in order to have not only 4, but 8 available screens at boot, which can be > accessed through Ctrl+Alt+Fn. However, this generated a > > wsconscfg: WSDISPLAYIO_ADDSCREEN > > error. It was impossible to create them. The above is 9 screens, not 8. -uwe
Re: wscons.conf ledstate and screen issues
> Sent: Wednesday, December 12, 2018 at 9:04 PM > From: "Valery Ushakov" > To: netbsd-users@netbsd.org > Subject: Re: wscons.conf ledstate and screen issues [...] > From a quick look - ledstate only controls the lights, not the > internal state of the keyboard driver (that handles numlock ). Yes, you are right. So, this is an "appearance" issue. As regards the numlock instead, is there a way to set it, in particular at boot? As regards the additional screens, I followed The NetBSD Guide here http://www.netbsd.org/docs/guide/en/chap-cons.html#chap-cons-wscons-wsdisplay Not only /etc/wscons.conf must be modified, but also (and accordingly) /etc/ttys. I obtained the 8 screens and they are ok, but the kernel still prints an error: wsconscfg: WSDISPLAYIO_ADDSCREEN Invalid argument Bye! Rocky > > -uwe > >
