Re: [OpenIndiana-discuss] ask for a small contribution related Pulseaudio,
On Sat, Feb 10, 2024 at 09:16:53AM +0100, Carsten Grzemba via openindiana-discuss wrote: > For do some preliminary testing on update Pulseaudio I am interested in a > small contribution. > > If anyone has more then one audio device, I am interested in the output of: > > $ ls -l /dev/audio* > > $ ls -l /dev/sound* > > > $ ls -l /dev/dsp* My ryzen system has two: $ cat /dev/mixer SunOS Audio Framework Audio Devices: 0: audiohd#0 onboard1, a (DUPLEX) 1: audiohd#1 onboard1, a (DUPLEX) Mixers: 0: audiohd#0 onboard1, a HD codec: ATI R600 HDMI 1: audiohd#1 onboard1, a Unknown HD codec: 0x10ec0887 $ ll /dev/audio* /dev/sound* /dev/dsp* /dev/mixer* lrwxrwxrwx 1 root root 7 Jul 10 2018 /dev/audio -> sound/0 lrwxrwxrwx 1 root root 7 Jul 8 2018 /dev/audio0 -> sound/0 lrwxrwxrwx 1 root root 7 Jul 10 2018 /dev/audio1 -> sound/1 lrwxrwxrwx 1 root root 10 Jul 10 2018 /dev/audioctl -> sound/0ctl lrwxrwxrwx 1 root root 10 Jul 8 2018 /dev/audioctl0 -> sound/0ctl lrwxrwxrwx 1 root root 10 Jul 10 2018 /dev/audioctl1 -> sound/1ctl lrwxrwxrwx 1 root root 4 Jul 10 2018 /dev/dsp -> dsp0 lrwxrwxrwx 1 root root 18 Sep 20 2017 /dev/dsp0 -> sound/audiohd:0dsp lrwxrwxrwx 1 root root 18 Sep 20 2017 /dev/dsp1 -> sound/audiohd:1dsp lrwxrwxrwx 1 root root 7 Sep 20 2017 /dev/mixer -> sndstat lrwxrwxrwx 1 root root 20 Sep 20 2017 /dev/mixer0 -> sound/audiohd:0mixer lrwxrwxrwx 1 root root 20 Sep 20 2017 /dev/mixer1 -> sound/audiohd:1mixer /dev/sound: total 12 lrwxrwxrwx 1 root root 9 Sep 20 2017 0 -> audiohd:0 lrwxrwxrwx 1 root root 12 Sep 20 2017 0ctl -> audiohd:0ctl lrwxrwxrwx 1 root root 9 Sep 20 2017 1 -> audiohd:1 lrwxrwxrwx 1 root root 12 Sep 20 2017 1ctl -> audiohd:1ctl lrwxrwxrwx 1 root root 68 Sep 20 2017 audiohd:0 -> ../../devices/pci@0,0/pci1022,1453@3,1/pci1043,aa98@0,1:sound,audio0 lrwxrwxrwx 1 root root 71 Sep 20 2017 audiohd:0ctl -> ../../devices/pci@0,0/pci1022,1453@3,1/pci1043,aa98@0,1:sound,audioctl0 lrwxrwxrwx 1 root root 66 Sep 20 2017 audiohd:0dsp -> ../../devices/pci@0,0/pci1022,1453@3,1/pci1043,aa98@0,1:sound,dsp0 lrwxrwxrwx 1 root root 68 Sep 20 2017 audiohd:0mixer -> ../../devices/pci@0,0/pci1022,1453@3,1/pci1043,aa98@0,1:sound,mixer0 lrwxrwxrwx 1 root root 68 Sep 20 2017 audiohd:1 -> ../../devices/pci@0,0/pci1022,1454@8,1/pci1043,86c7@0,3:sound,audio1 lrwxrwxrwx 1 root root 71 Sep 20 2017 audiohd:1ctl -> ../../devices/pci@0,0/pci1022,1454@8,1/pci1043,86c7@0,3:sound,audioctl1 lrwxrwxrwx 1 root root 66 Sep 20 2017 audiohd:1dsp -> ../../devices/pci@0,0/pci1022,1454@8,1/pci1043,86c7@0,3:sound,dsp1 lrwxrwxrwx 1 root root 68 Sep 20 2017 audiohd:1mixer -> ../../devices/pci@0,0/pci1022,1454@8,1/pci1043,86c7@0,3:sound,mixer1 -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Replace xscreensaver with mate-screensaver
On Sun, Jan 21, 2024 at 09:50:24PM +0100, Marcel Telka wrote: > Yes, I see that too. It apparently uses UTC time instead of local time. > Not sure it is MATE bug or OI bug. I do not see this on a Linux box > with older MATE. So it is possibly OI issue. Fee free to file a bug > report. I've just filed Bug #16205 for the mate-screensaver time issue. I'm not going to work on it, because I'm old and retired. Perhaps a younger person could fix the bug. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Replace xscreensaver with mate-screensaver
On Sun, Jan 21, 2024 at 05:14:08PM +0100, Marcel Telka wrote: > The above comes from desktop/mate/control-center package and is default > in the C locale, so it seems okay for American English. > > Please see: > https://github.com/mate-desktop/mate-control-center/blob/master/mate-control-center.pot#L4725 > > I assume you use the en_CA locale. For this locale the string in > question is not "translated", see: > https://github.com/mate-desktop/mate-control-center/blob/master/po/en_CA.po#L4717 > so you see the default "untranslated" version of the string. Actually, this particular system uses the en_US locale. I don't know why that is. Clearly, that is part of the problem. Next time I'll check the locale, instead of just assuming it. > If you want to see this fixed, then the best way would be either report > this or maybe create a PR for the upstream mate-control-center project > https://github.com/mate-desktop/mate-control-center or reach the en_CA > translation team at https://www.transifex.com/mate/teams/13566/en_CA/ . > > The other possibility to have it fixed ASAP is to create a patch for our > (OpenIndiana) desktop/mate/mate-control-center component at > https://github.com/OpenIndiana/oi-userland and propose it as a PR. The word in question is spelled "center" in American English, and "centre" in British English. Canada's spelling is somewhere in between, if that is posible. I don't know if there is an official spelling in Canada, or in anyplace for that matter. I certainly don't want to impose my personal views on other people. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Replace xscreensaver with mate-screensaver
I recently posted a bug report describing my bad experience with xscreensaver. The report can be seen here: https://www.illumos.org/issues/16185 It contains a suggestion from Marcel Telka that I try replacing xscreensaver with mate-screensaver. Indeed, his PR at: https://github.com/OpenIndiana/oi-userland/pull/15702 suggests that OI change mate_install to install mate-screensaver instead of xscreensaver. Well, changing from xscreensaver to mate-screensaver is one way to get rid of faulty software. To be fair, I did try the replacement on one of my systems. Here is my experience with mate-screensaver. It was easy to remove xscreensaver, although I had to kill the xscreensaver daemon manually. It was easy to install mate-screensaver, but it also didn't start its daemon after the install. I noticed the System menu now had an item called "Control Center". In this country, we spell the second word "centre". This brings up a new utility, that has an icon called "Screensaver". This, in turn, brings up the mate-screensaver configuration utility. I found it easy to use. To start the mate-screensaver daemon without rebooting or restarting X11, I used the command: $ mate-screensaver & The query command then succeeded: $ mate-screensaver-command -q The screensaver is inactive The screensaver is not inhibited I found that mate-screensaver does blank the screen and does lock the screen with a password box. In fact, it has all of the features I require in a screensaver. I'm going to keep it. The password box does show the wrong time, six hours fast in my case, but I'm willing to ignore that error. It's not a problem for me, but the package contain only four themes, with no easy way to add more. In short, mate-screensaver is a good basic screensaver. People who want to use xscreensaver will have to install it themselves, if the change suggested in the PR takes place. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] DNS server and domain from DHCP?
On Tue, Dec 19, 2023 at 06:32:13PM +, Philip Kime wrote: > * Where can I find the dns server and domain settings in SMF? I >tried looking in dns/client but I can't see config/nameserver >property in there. You first have to decide if you want the domain name mapping to IP address to be externally visible, like ibm.com or cbc.ca, or if you do not. In the first case, you need to purchase a domain (actually rent) unless you have already done that. In the second case, the easiest thing is to use the domain name that your ISP's DHCP server has assigned to your computer. If you are unable to do that, the whole thing becomes more complicated. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI without a console?
On Mon, May 08, 2023 at 10:31:09AM -0500, Gary Mills wrote: > Is anybody running OI on a computer that does not have a console? > I have a system that I installed with the GUI image, and with an > HDMI console and USB keyboard and mouse. Now I'd like to use this > system without all of them. I have another question. Will it help to have OI boot without the X11 screen? How do I accomplish that? The text screen will be adequate for most of what I need to do. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI without a console?
On Tue, May 09, 2023 at 02:55:56AM -0400, Richard L. Hamilton wrote: > Given motherboard serial ports (like on a desktop, but very few > laptops anymore), can OpenIndiana handle a serial console? What > about a serial console on a PCIe card, or worse, on a USB port? I have used serial consoles in the past. Working with serial cables is a frustrating experience, especially if you don't have a breakout box. Ethernet is much better: you just connect it, and it works. I have two systems, one with a Supermicro motherboard, and one with a Tyan motherboard. Both have an IC that looks like VGA video to the OS, but converts VGA text to a serial stream that goes to a dedicated ethernet port. They work nicely for me with OI and IPMI. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI without a console?
On Tue, May 09, 2023 at 03:52:25PM +1000, Carl Brewer wrote: > > Quite annoying! Maybe someone on this list knows what sort of KVM switch > might provide enough for a HDMI card to behave at boot time? I don't know > the terminology, so search engines are not being kind! I'd really like to be > able to use one. I recently converted from a VGA/USB KVM to an HDMI/USB KVM switch. The new one works with Winows 10 and OI. My three OI systems already had HDMI ports. The Windows system had only VGA and DP ports. I had to obtain a DP to HDMI adapter for that one. You need some sort of digital video port for all systems. I use this KVM now: https://www.newegg.ca/p/1DJ-00Z4-00038?Item=9SIAKFBJRX0258 Beware that you need to boot OI systems twice before the keyboard and mouse will work. Alternatively, you can replace the second boot with just temporarly switching the KVM to a different system. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI without a console?
On Tue, May 09, 2023 at 08:17:42AM +1000, Carl Brewer wrote: > > Three of them. Have been running OI since it was OS, oh, almost 20 years > now? One of my three is about that old too. Rock solid. > > I found I had to use an HDMI "dummy" to get the newer ones to boot. I wondered if an HDMI console was somehow special. The system I'm using has only HDMI and Display Port connectors for a monitor. It has no VGA connector. > One of these : > https://core-electronics.com.au/hdmi-dummy-plug.html > > Otherwise it would lock up OI at boot-time. YMMV. Thanks for the page. I'll make sure I get one or two of those plugs. I expect I'll need them. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI without a console?
On Mon, May 08, 2023 at 05:37:00PM +0200, Stephan Althaus wrote: > > As I can tell from history, you should set the BIOS to ignore these errors > on boot like "no keyboard attached". Try this with only the monitor > attached, no keyboard/mouse.. That's good to know. I have a duplicate system on order. I can use that to experiment on. > I have a Backup server without keyboard/mouse/monitor attached that i power > up from remote via IPMI, > that boots into OI just perfextly. How do you use IPMI? I've only used it with systems that have video emulator hardware installed, with a dedicated ethernet port. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] OI without a console?
Is anybody running OI on a computer that does not have a console? I have a system that I installed with the GUI image, and with an HDMI console and USB keyboard and mouse. Now I'd like to use this system without all of them. Can I just disconnect them? Will OI boot fully without a console? Can I attach a console later, if I happen to need it? -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] OI on a fanless mini-PC
This must be one of the smallest and quietest computers to run OI. It's a Partaker Fanless Mini PC. It's quite small, but has an Intel Celeron J4125 Quad Core CPU. It also has built-in Intel graphics, with an HDMI and display port video ports. This machine also has two ethernet ports, both of which I wanted since I intended it as a NAT router. When I first tried it, I got no output on a VGA monitor, even though I used two different VGA adaptors. When I switched to an HDMI monitor, I got immediate output. It seemed to boot freebsd, not the windows 10 that was advertized, and have no BIOS. I was wrong there: it does have a BIOS. Pressing the DEL key at the right time does display the BIOS setup screen. You have to press DEL as soon as the keyboard becomes active. The first thing to change is the boot delay. Setting it to 10, from 1, will give you lots of time to press DEL, and will display a message telling you what key to press. There's no boot menu in the BIOS setup, and no USB stick entry in the boot priorities. Nevertheless, it is possible to boot it from a USB stick. Magically, a USB stick will appear in the list of priorities once you insert a USB stick. All you have to do is to move it to the top of the list. This process must be re-done on each reboot. I did this to boot memtest86, the OI-gui stick, and the OI-text USB stick. There were no significant missing drivers. Ultimately, I installed the OI-gui distribution, and upgraded it to the latest OI. That's what the system is running now. I used the gui version mainly because I only know how to use the Network GUI to configure the network. I won't need a console once the configuration is complete. I certainly will never need the web browser. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [oi-dev] libpulsecore error
On Thu, Mar 09, 2023 at 12:30:21PM -0600, Tim Mooney via openindiana-discuss wrote: > Based on your subsequent email, though, it looks like you found the > issue and it was with the binary cache file. Yes, rebuilding the gschemas.compiled file gave me a normal graphic session. Thanks for all the help. I have only left now to determine the origin of that file in OI to know why it was incorrect. The good one looks like this: -rw-r--r-- 1 root root 184871 Mar 9 11:00 gschemas.compiled Here's the bad one: -rw-r--r-- 1 root root 183112 Mar 4 18:30 gschemas.compiled-old According to the date, it came from an old BE, and was not rebuilt or installed in two updates. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] My Firefox tab has crashed
On Fri, Feb 17, 2023 at 07:07:38PM -0600, Gary Mills wrote: > Whenever I tell Firefox to show me www.royalbank.com, and click on the > Sign In box, it tells me that my tab just crashed. This behavior just > started happening today. It happens before I get an opportunity to > authenticate. I get the same thing on a newly-upgraded BE as I do > from one that's about a year old. The curious thing is that Firefox > on Linux works perfectly with this same URL. That's the only way I > can access my bank now. Thanks to private e-mail from Geoff Weiss, I learned a few things and found the solution. The underlying cause is a Firefox bug that only shows up on systems that use VESA graphics. All of my OI systems use VESA graphics because OI does not have a kernel driver for Radeon video cards. Firefox is testing for Webgl graphics, and doing it badly. The solution for VESA graphics is: go to about:config set webgl.disabled to true Both recent versions of Firefox on OI, that I tested, seem to have the bug. Newer versions of Firefox will be better. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] My Firefox tab has crashed
On Sat, Feb 18, 2023 at 09:20:57AM +0100, Carsten Grzemba via openindiana-discuss wrote: > > So far I can test it it works with the current firefox 102.7.0esr > for me (and also 109, 91.2.0esr) . Again, thanks for the response. That's both curious and helpful. Apparently, there's something different between my systems and yours that is causing the tab crash. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] My Firefox tab has crashed
On Sat, Feb 18, 2023 at 08:53:06AM +0100, Carsten Grzemba via openindiana-discuss wrote: > > Have you attempt use of website with new profile also? Perhaps there > are some confusing things like cookies stored in the profile which > let the tab crash. Thanks for the response. The new and old BEs are on different systems, with quite different browser profiles. It's unlikely that the profile is the cause. I'll try to use "truss -f" to see what happens just before the tab crash. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] My Firefox tab has crashed
Whenever I tell Firefox to show me www.royalbank.com, and click on the Sign In box, it tells me that my tab just crashed. This behavior just started happening today. It happens before I get an opportunity to authenticate. I get the same thing on a newly-upgraded BE as I do from one that's about a year old. The curious thing is that Firefox on Linux works perfectly with this same URL. That's the only way I can access my bank now. I assume that the bank's web site is doing something that does not work on OI. Could it be something simple, like a missing library? Is there any way to get a traceback of that tab crash or to send one to a developer? -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] image-update fails with python mediator errors
On Tue, Jul 05, 2022 at 01:10:09PM -0500, Gary Mills wrote: > > What's the exact command? I recall I had this problem after an > update. The boot stopped in single-user mode. I logged in and > deleted the bad service. Then I shut down the system and rebooted > it. I got a normal boot. Ah, I found it in my console log: # /usr/sbin/svccfg delete svc:/system/metainit:default # /usr/sbin/init 0 The service was present but disabled. > This is a well-known problem with OI. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] image-update fails with python mediator errors
On Tue, Jul 05, 2022 at 07:25:01PM +0300, Toomas Soome via openindiana-discuss wrote: > Different issue. You have svm (solaris volume manager) service to > be removed…. What's the exact command? I recall I had this problem after an update. The boot stopped in single-user mode. I logged in and deleted the bad service. Then I shut down the system and rebooted it. I got a normal boot. This is a well-known problem with OI. The command probably came from a web page, but I can no longer find it. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] problem replacing a disk by a bigger one
On Mon, Jun 27, 2022 at 05:33:45PM +0200, Marc Lobelle wrote: > > My current situation is thus that I booted from the internal disk, attached > the external one and detached the internal one (at this point everything > runs fine) > > My two questions are thus: > > 1. Now that I have detached the disk inside the computer, can I still >reboot with only this disk ? > 2. Do I have to change something in the new disk to connect it as sata >drive rather than as usb drive and boot the system from it ? > > Thanks, I wait for your advice before risking to turn off the notebook What does "zpool status" show? -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] problem replacing a disk by a bigger one
On Sun, Jun 26, 2022 at 11:46:25PM +0200, Marc Lobelle wrote: > > In tried to replace the ssd of my notebook running openindiana (120G) by a > bigger one (1T). > > I first copied the small ssd on the big one: I connected the big disk on a > usb adapter, ran format to identify the two devices then > > dd if=/dev/rdsk/c6t0d0p0 of=/dev/rdsk/c4t0d0p0 bs=2048K A much better way is to use the ZFS mirroring capability. The command is: # zpool attach -f ... ... ... You could also use: # zpool replace [-f] pool device [new_device] Wait for the resilver to complete. The result will be a two-way mirror, in the case of the first command. Then, detach the small SSD and try booting from the big one, again for the first command. The second command does it all in one operation. The manual will tell you more than I can. Note that I've only done this with both disks permanently installed on a desktop. I don't know if it even works with USB disks. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] dell 15810 bricked after latest update
On Tue, Jun 14, 2022 at 06:15:28PM -0700, irixuzer wrote: > I’ve been updating and going since 2019 *I think*. Now after the > latest update, my Dell t5810 is bricked I cannot go past the dell > screen, What did you update, OI or the BIOS? > I’ve tried to downgrade the bios, Many systems no longer support BIOS downgrades. > no luck cannot go past the > dell screen no matter which f key I push, Rescatux is useless. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] services dependency cycle
On Thu, May 05, 2022 at 09:43:40PM +0200, Stephan Althaus wrote: > > Sorry, i don't have a system with a BE that contains the service metainit, i > tried several.. i looked into some snapshots where i did find a log but not > the manifest.. > > Maybe someone else has a system with the service metainit present. It think > was disabled on my broken setup btw. I have one: $ svcs -a | grep meta disabled Apr_23 svc:/system/metainit:default I'm running a BE dated 2021-08-30 . The only dependency seems to be svc:/system/identity:node . -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI Hipster becomes unreachable over network after a certain length of uptime
On Wed, Apr 13, 2022 at 08:04:40PM +0200, s...@pandora.be wrote: > The documentation > http://docs.openindiana.org/handbook/systems-administration/#configuring-networking > writes: > "While usually server and desktop installations tend to use default > network configurations, laptop users can leverage nwam network > configuations." That really means: "in an envionment where the network configuration changes frequently". > So that doc positions NWAM as a solution for 'laptop users'. > Opinions may differ ... NWAM actually works well in many situations. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI Hipster becomes unreachable over network after a certain length of uptime
On Tue, Apr 12, 2022 at 10:42:53PM -0700, Joshua M. Clulow via openindiana-discuss wrote: > > As suggested in the ticket, I would: > > # routeadm -d ipv4-routing -u > > The "svc:/network/routing/route:default" instance should then be > disabled, unlike in your output above. I have two different routing configurations. The first is for a system that acts as a NAT router using ipfilter. /etc/defaultrouter does not exist. It has two ethernet interfaces. One connects to my cable modem. The other goes to my private network, through a switch: $ routeadm Configuration Current Current Option ConfigurationSystem State --- IPv4 routing disabled disabled IPv6 routing disabled disabled IPv4 forwarding enabled enabled IPv6 forwarding disabled disabled ... The "IPv4 forwarding" setting is required by ipfilter. The other configuration is for a typical system on my private network, using all the defaults, with a single ethernet: $ routeadm Configuration Current Current Option ConfigurationSystem State --- IPv4 routing enabled enabled IPv6 routing disabled disabled IPv4 forwarding disabled disabled IPv6 forwarding disabled disabled ... -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Heads up: SSH has been updated to 8.9p1
On Sun, Apr 10, 2022 at 09:15:00PM +0200, Andreas Wacknitz wrote: > Am 10.04.22 um 20:53 schrieb Gary Mills: > > Isn't there something in the P5M file that says that the > > svc:/network/ssh:default service needs to be restarted after the > > update? > > > No, not yet. Feel free to add something. I'll leave that change to somebody that actually uses ssh. I don't. I see plenty of examples. Some of them add an attribute to a file, like these: database/couchdb-31/couchdb-service.p5m:file files/couchdb-31.xml path=lib/svc/manifest/application/couchdb-31.xml restart_fmri=svc:/system/manifest-import:default database/pgadmin/pgadmin.p5m:file files/pgadmin3.desktop path=usr/share/applications/pgadmin3.desktop restart_fmri=svc:/application/desktop-cache/desktop-mime-cache:default I suppose that if the P5M file updates the XML file, it must also import it, and if the P5M file updates a cached file, it must also re-cache it. Some of them use a transform, which you might do if you needed to add the attribute to multiple files. Here are several examples, including one that seems to have a typo: desktop/compiz/compiz.p5m: default restart_fmri svc:/application/desktop-cache/gconf-cache:default> desktop/compiz/compiz.p5m: default restart_fmri svc:/application/desktop-cache/desktop-mime-cache:default> virtualbox/virtualbox.p5m: default restart_fmri svc:/application/virtualbox/run-once:defaul> -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Heads up: SSH has been updated to 8.9p1
On Sun, Apr 10, 2022 at 08:10:56PM +0200, Andreas Wacknitz wrote: > As the subject says, I have recently integrated a new version of > openssh. You may need to reboot your machine in order to make the update > work. Isn't there something in the P5M file that says that the svc:/network/ssh:default service needs to be restarted after the update? -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Backup for ZFS filesystems
On Wed, Mar 30, 2022 at 10:21:11AM -0500, Judah Richardson wrote: > Ironically, zrepl <https://repology.org/project/zrepl/versions> has more > distro repo packages than znapzend > <https://repology.org/project/znapzend/versions> has ;) Some of the files that appear to be zrepl packages are not packages at all. For example, the solaris and illumos downloads are just single binaries that run on those platforms. They are components of packages, not complete packages. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Backup for ZFS filesystems
On Sat, Mar 26, 2022 at 02:57:13PM -0700, Joshua M. Clulow via openindiana-discuss wrote: > > You may wish to investigate "zrepl" as well, which has some neat features: > > https://zrepl.github.io/ ZnapZend and zrepl are actually very similar in function: they both do replication of ZFS filesystems. I wondered at first that these two backup systems had no facilites for restores, like you get with a traditional backup system. However, I soon realized that if you had a replica, you could just copy a file to restore it. Alternatively, you could recreate an entire filesystem from a replica. The system I used formerly, zetaback, only stored "zfs send" streams on the backup device. That's something that's failure-prone, according to all the ZFS documents I've read. The only disadvantage of zrepl that I've encountered so far is that it does not have an OI package. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Backup for ZFS filesystems
On Sat, Mar 12, 2022 at 05:28:35PM -0600, Judah Richardson wrote: > I assume you know there are gazillion ways to implement this, but if you > want an out of the box ZFS solution I'd say the *easiest* (note the > emphasis) option is either a TrueNAS Server > <https://www.truenas.com/systems-overview/> or a BYOD/DIY TrueNAS Core > <https://www.truenas.com/truenas-core/> system. Thanks for the response, and sorry for the delay in my response. That may be easy, but it's not really what I wanted. I'd prefer something that ran on my existing backup server. > znapzend <https://www.znapzend.org/>, using this guide > <https://dev.to/jdrch/how-to-setup-znapzend-with-local-backup-on-openindiana-1f0p>. Ah, that sounds promising. I'll investigate further, but it may be exactly what I wanted. I see that ZnapZend already has an OI package, making it easy to install. I had been using zetaback, from OmniTI. It also has an OI package. I may continue to use that product. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Backup for ZFS filesystems
I'm looking for a backup system that uses ZFS facilities to integrate backup with ZFS. Is there such a thing? In addition, I'm looking for something that stores the backups on a single backup server, with network connections to multiple backup clients. Of course, I would also like easy restores to ZFS filesystems. What are you using to backup ZFS files? -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] SSDs for OI hipster ZFS root mirror?
On Sat, Aug 14, 2021 at 02:35:12PM +1000, Carl Brewer wrote: > > Rather than use a couple of 1TB WD red pros or Blacks, is it a good choice > to run a ZFS root mirror on a couple of SSDs? I figure I'd only need 250MB > or so, all the data etc will be on spinning drives in a raidZ-something > array, the root system - apart from swap, will be pretty static read-mostly That's my usual configuration. I use a pair of SSDs in a ZFS mirror for the root filesystem, with the data on a separate ZFS filesystem. That way you can replace the OS but retain the data if necessary. It's never been necessary for me. > So I'm considering running a couple of Samsung 250GB SSDs, any thoughts or > war stories before I go and buy them? Is it better to stagger them in terms > of age, or different brands/models so they don't both run out of writes at > the same time? Is this setting me up for a disaster in 3 years, or will it > be predictable and easy to maintain? I usually get the smallest SSDs that I can find. The OS is not very large. Depending on the amount of memory the system has, you may need a large amount of swap space on the SSDs. Don't skimp. Using different brands of SSDs is a good idea too, but I've never been able to do that. You can get brackets that hold two SSDs but fit into one slot on the case. That's a good idea if the case is short of slots. > I don't think there's any status monitoring software for them that would run > on OI? It might already be ported to OI but just not on the USB image. I don't know. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] More 2021.04.30 strangeness
On Mon, Jun 21, 2021 at 08:17:57PM +, Reginald Beardsley via openindiana-discuss wrote: > At this point, the only means I can think of to find the source of > the message is to run ldd(1) across all the executables and grep out > anything that links libcaja-gksu.so. dump -Lv ... | grep NEEDED works better than ldd. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] automount does not work!
On Sat, Jun 19, 2021 at 08:03:12PM -0700, Alan Coopersmith wrote: > On Solaris & OI, the Xorg server relies on hal to let it know when USB > input devices have been hotplugged so it can attach to mice, keyboards, > tablets, etc. It should not interfere with the mounting of USB storage > devices. I'm focusing on a child process called hald-addon-storage now. There are four of them on a BE where automount works, and none of them on a current BE where it doesn't work. The process has a socket to hald and a door to syseventd. Each hald-addon-storage process also monitors a storage device. I don't know the plumbing in detail, but I assume that without the process, hald will not be aware of changes to USB devices. That is the problem I'm seeing. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] automount does not work!
On Sat, Jun 19, 2021 at 08:03:12PM -0700, Alan Coopersmith wrote: > > On Solaris & OI, the Xorg server relies on hal to let it know when USB > input devices have been hotplugged so it can attach to mice, keyboards, > tablets, etc. Yes, that mechanism breaks down for me in the current version of OI. > It should not interfere with the mounting of USB storage > devices. Yes, I agree. Nevertheless, something also prevents automounting of USB sticks. I assume there's something in common behind the two symptoms. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] automount does not work!
On Sat, Jun 19, 2021 at 07:18:27PM +, Apostolos Syropoulos wrote: > > I have also noticed that > > # svccfg > svc:> select hal > svc:/system/hal> listprop hal/* > svc:/system/hal> exit > > which is very strange! The man page gives the following example The error seems to be in the man page. The method script svc-hal does not use any SMF properties. It only runs: /usr/lib/hal/hald --daemon=yes About all you can do to run the daemon with different options is to disable the service and then run it manually. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] automount does not work!
On Sat, Jun 19, 2021 at 06:59:34PM +, Apostolos Syropoulos wrote: > Well if your machine has a DVD drive you will notice that DVDs/CDs > are automounted. This probably means that something is wrong with > the part that mounts USB thumb sticks. Yes, I just tried that. A DVD is indeed automounted. As far as I can tell, hal does not notice changes since boot in any USB devices. It must be something in hal that is missing or changed. I've ruled out the nvidia driver or the modesetting driver. X11 is still involved somehow. Restarting the display manager does allow you to recover a USB keyboard if you happen to change it. Of course, doing that is just about as drastic as rebooting. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] automount does not work!
On Fri, Jun 18, 2021 at 04:48:56PM +, Apostolos Syropoulos via openindiana-discuss wrote: > Today I installed OI using the latest DVD on 4 different > machines. One machine had an old nvidia card and I had to create a > new BE. By entering the command to uninstall the driver, I noticed > that pkg command installed the 340.XX driver at the end. This is > just great! However, I have noticed that USB thumb disks cannot be > automounted. Yes I can manually mount a USB thumb disk but that is > all. This means something is broken in the distribution. That's an interesting finding. I checked two of my systems that have the automount problem: Both have the nvidia-390 package. None of my systems use Nvidia graphics. I'll try removing that package from one of them to see what happens to USB stick mounting. There does appear to be some interaction between hal (supplied by illumos) and X11 (supplied by OI). -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] OS update works nicely
This is a good news story. Yesterday and today, I updated three of my systems with excellent results. All were previously updated around the end of November 2020. About 500 packages were modified or replaced during the update. None of the systems had Nvidia graphics. One was an HP Z400 with an Intel Xeon CPU. It used a Radeon HD 2400 PRO/XT video card with the radeon driver. Another more modern system had an Intel Core i3-9100 CPU with built-in UHD 630 graphics. It used the vesa driver. The third system had an AMD Ryzen 5 2600 CPU. It used a Radeon HD 7450 video card with the vesa driver. I'm impressed, and also pleased. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] The kiss of death
On Thu, Apr 22, 2021 at 12:48:26AM +, Reginald Beardsley wrote: >I am doing a UEFI boot as it is a 4x 4 TB RAIDZ2 pool. The UEFI vs SMI >boot would make a lot of sense. However, it still leaves the problem of >2020.10 crashing before reaching the desktop. This is a known broken configuration of OI. It cannot work. The VESA driver is a fall-back driver in Xorg. It only runs if the other drivers all fail. Unfortunately, the VESA driver does not work with a UEFI boot. As long as the nvidia driver succeeds, it will be selected by Xorg, and VESA will never be used. The Xorg log will contain this information. My AMD systems all use the Radeon HD 7450 video card, which requires the VESA driver on OI. They all use a BIOS boot. OI is installed on a mirrored pair of small SSD disks. They also use a mirrored pair of large mechanical disks for the data pool. This configuration does work. Other people use different configurations that also works. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] The kiss of death
On Wed, Apr 21, 2021 at 11:29:55PM +, Reginald Beardsley via openindiana-discuss wrote: > I'm trying to bring up OI on Oracle Solaris 11 certified hardware. > 2020.10 crashes booting the Desktop Live Image. The 2021.04_rc1 > Live Image works fine, but the installed image crashes on reboot. I've seen this behavior before: you can boot from the install media and even do an install with no problems, but the installed image fails to boot fully. It's caused by the VESA video driver, which will only run correctly with a BIOS boot, not with a UEFI boot. The installer itself can be booted either way. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] timezone
On Tue, Mar 30, 2021 at 08:51:55PM -0700, irixuzer wrote: > I'll bet this is a real classic question. How Do I get OI and dos clocks > to agree? I sort of remember how to configure it in solaris 7 and 8. I'm > on the US West coast. and OI is telling me it's 8:33PM and it really is > around 1:33 PM. Please dont think i'm sending this to only toomas, gmail > is stupid. To set the DOS clock, you have to be in DOS or in the BIOS setup or in OI. To set the OI clock, you have to be in OI. However, it sounds as if only your timezone is wrong. What does the date command, with no options, say for your time zone? The hardware clock does not have a time zone. You can set it to anything you like in OI. This is normally done during installation. The easy way to change the OI time zone is with the rtc command, like this: # rtc -z zone-name Check the man page for rtc for details. You can also look at the file /etc/rtc_config for current time zone settings. If you change the time zone with rtc, you should reboot immediately. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to mount usb devices?
On Mon, Mar 29, 2021 at 04:17:23PM +0200, Jean-Pierre André wrote: > And why is it restricted to vfat ? External usb disks are factory > formatted as ntfs, which is more suitable for OS-agnostics > backups. Automatic mounting Exfat devices would also be useful. Probably because of Microsoft patents and licence costs, I would suspect. You have to reformat those USB devices. The FAT filesystem is the only portable filesystem between OI and Windows. You can reformat them on Windows or OI. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to mount usb devices?
On Sun, Mar 28, 2021 at 04:24:58PM -0500, Gary Mills wrote: > On Sun, Mar 28, 2021 at 08:38:33PM -0700, irixuzer wrote: > > I'm new to the list. Ive been trying to mount usb devices. After the first > > time, which was successful, I've been getting the following: > > If you are using the dbus service, the usual case with OI, USB devices > get mounted automatically. You don't have to do anything. The FMRI > of that service is svc:/system/dbus:default . I see I made a mistake in this message. It's the hal service that mounts USB devices automatically. The FMRI is: svc:/system/hal:default This service is present on all my OI systems, but then I installed them initially with the GUI installer. I don't know if the hal service is installed by the text installer. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to mount usb devices?
On Sun, Mar 28, 2021 at 08:38:33PM -0700, irixuzer wrote: > I'm new to the list. Ive been trying to mount usb devices. After the first > time, which was successful, I've been getting the following: > > > $ sudo rmformat -l > ... > 6. Logical Node: /dev/rdsk/c8t0d0p0 > Physical Node: /pci@0,0/pci1028,617@14/storage@5/disk@0,0 > Connected Device: SanDisk Cruzer Glide 1.27 > Device Type: Removable > Bus: USB > Size: 29.8 GB > Label: > Access permissions: Medium is not write protected. If rmformat shows the device, it's already mounted. I just plugged a USB stick into one of the USB ports on my system. Here's what it showed: $ rmformat -l Looking for devices... ... 2. Logical Node: /dev/rdsk/c7t0d0p0 Physical Node: /pci@0,0/pci1022,1453@1,3/pci1b21,1142@0/storage@7/disk@0,0 Connected Device: Verbatim STORE N GO 5.00 Device Type: Removable Bus: USB Size: 3.8 GB Label: Access permissions: Medium is not write protected. $ mount | grep media /media/STORE N GO on /dev/dsk/c7t0d0p0:1 read/write/nosetuid/nodevices/hidden/nofoldcase/clamptime/noatime/timezone=21600/dev=3701190 on Sun Mar 28 21:20:50 2021 USB devices are automatically mounted under /media . You can access them there. To unmount them, I use the right-click menu of the icon on the desktop. There are other ways. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to mount usb devices?
On Sun, Mar 28, 2021 at 08:38:33PM -0700, irixuzer wrote: > I'm new to the list. Ive been trying to mount usb devices. After the first > time, which was successful, I've been getting the following: If you are using the dbus service, the usual case with OI, USB devices get mounted automatically. You don't have to do anything. The FMRI of that service is svc:/system/dbus:default . -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Firefox68esr for testing
On Tue, Mar 16, 2021 at 04:27:31PM +0100, Carsten Grzemba via openindiana-discuss wrote: > I made available a firefox package 68esr for testing > > Unfortunately for the moment there is a restriction! > There is a setting in /etc/system necessary: > > set _userlimit=0x7fffc000 > > whithout this, FF will raise a assertion in JS code. It sounds as if we need the illumos developers to make the appropriate change to the illumos kernel or to the linker so that this setting will not be necessary. An illumos bug report would be a good starting point. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Hipster 2020.10 text installer ISO Wow!!!!
On Wed, Mar 03, 2021 at 07:57:39AM -0600, Gary Mills wrote: > > I looked around for my notes on the first install of OI on my Z400, > but couldn't find anything. Maybe it was that easy that I didn't > bother making notes. I do recall that only needed to follow the first > part of the instructions. The main thing is the add_drv and rebuilding > the boot archive. There was only one BE, of course. I found my notes. They were from Febuary 2018. Here they are, in point form: o Changed controller to AHCI+RAID in BIOS o Booted OI hipster-20171031 USB stick o Started a shell window o Got a root shell with `sudo ksh' o Found `RAID controller' in `prtconf -v' output o Ran: update_drv -a -i 'pci8086,2822.103c.1309.0' ahci o Added line to driver_aliases: ahci "pci8086,2822.103c.1309.0" o Ran the installer o Checked new BE: # mkdir /tmp/a # beadm mount openindiana /tmp/a # wc -l /tmp/a/etc/driver_aliases /etc/driver_aliases 1772 /tmp/a/etc/driver_aliases 1772 /etc/driver_aliases o Files were the same o Rebuild the boot archive: # bootadm update-archive -v -R /tmp/a o No output o Umount: # beadm unmount openindiana o Rebooted from the installer GUI o Normal boot of new BE -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] More information on my HP Z400
This is the offending disk controller, as shown by scanpci -v: pci bus 0x cardnum 0x1f function 0x02: vendor 0x8086 device 0x2822 Intel Corporation SATA Controller [RAID mode] CardVendor 0x103c card 0x1309 (Hewlett-Packard Company, Card unknown) STATUS0x02b0 COMMAND 0x0047 CLASS 0x01 0x04 0x00 REVISION 0x00 BIST 0x00 HEADER 0x00 LATENCY 0x00 CACHE 0x00 BASE0 0xd100 SIZE 8 I/O BASE1 0xd110 SIZE 4 I/O BASE2 0xd108 SIZE 8 I/O BASE3 0xd114 SIZE 4 I/O BASE4 0xd0c0 SIZE 32 I/O BASE5 0xf6004000 SIZE 2048 MEM MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x02 INT_LINE 0x07 Here's part of the corresponding configuration, as shown by prtconf -v: value='pci8086,2822.103c.1309.0' + 'pci8086,2822.103c.1309' + 'pci103c,1309,s' + 'pci103c,1309' + 'pci8086,2822.0' + 'pci8086,2822,p' + 'pci8086,2822' + 'pciclass,010400' + 'pciclass,0104' I see that the most specific value includes both sets of vendor and device codes. Not all HP Z400 computers will have this disk controller card. The addition to /etc/driver_aliases that I made by add_drv long ago is this line: ahci "pci8086,2822.103c.1309.0" It probably can be less specific. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Hipster 2020.10 text installer ISO Wow!!!!
On Tue, Mar 02, 2021 at 08:40:51PM -0800, Joshua M. Clulow via openindiana-discuss wrote: > > If ahci(7D) does indeed support this controller, and it's just that > the association with the specific PCI ID is missing, that's incredibly > easy to fix in illumos and then nobody needs to do the manual > update_drv dance ever again. At present, it's just attaching to the > AHCI 1.0 PCI device class, 01:06:01: > > > http://src.illumos.org/source/xref/illumos-gate/usr/src/pkg/manifests/driver-storage-ahci.mf?r=fd6d41c5#46-47 The only permanent change to OI on my Z400 is this addition to /etc/driver_aliases: ahci "pci8086,2822.103c.1309.0" I've since done many OS upgrades to the system, but never needed to make that change again. Mostly, I forgot that I had done it. > But if we need to bind it to more specific devices that do not > advertise the class, it would just mean more aliases in the package > manifest. It'd help to collect the data from prtconf and file a bug > report to start with, and then making the actual change is not likely > to be a great deal more work after that. > > It's always best to file and fix the underlying bug where we can, > rather than propagate workarounds like this. I looked around for my notes on the first install of OI on my Z400, but couldn't find anything. Maybe it was that easy that I didn't bother making notes. I do recall that only needed to follow the first part of the instructions. The main thing is the add_drv and rebuilding the boot archive. There was only one BE, of course. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Hipster 2020.10 text installer ISO Wow!!!!
On Tue, Mar 02, 2021 at 09:42:45PM +, Reginald Beardsley wrote: > Does *not* work on my Z400 machine. I reset the BIOS to "AHCI+RAID" >and the 2020.10 GUI installer enters maintenance mode. prtconf -v won't >even run. I wonder if you made the change too late in the boot process? When the loader is running, you can interrupt the automatic boot by pressing the space bar. Then, you can enter commands to the loader. Selecting the single-user boot may be sufficient. You may need to use the text installer instead. As well, you may need to enter the fully-qualified path of prtconf, like this: /usr/sbin/prtconf -v | less I know that it's complicated, but it's the only way to accomodate a broken disk controller. Also, you only have to do this once. Most systems do not have this problem. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Hipster 2020.10 text installer FAIL #3
On Tue, Mar 02, 2021 at 09:17:31AM -0500, John D Groenveld wrote: > In message <20210302014545.ga6...@imap.fastmail.com>, Gary Mills writes: > >These are Solaris partions, now called slices. They are within a > >single FDISK partition. You can use the partition command within > >format to see the slices. You can use the fdisk command within format > >to see the FDISK partitions. > > They are GPT partitions, not Solaris slices within a legacy MBR fdisk > partition. Sorry. I should not have replied. I've never used GPT disks, although ZFS offers to use the whole disk, whatever that means. I only know about FDISK partitions and Solaris slices. There was once one type of partition, then there were two, and now there is three. > There may be nomenclature byg here: > # zpool create -f -B -d weetest c4t0d0 > # fdisk /dev/rdsk/c4t0d0 > If you run fdisk /dev/rdsk/c4t0d0, you will see a single EFI partition, > but fdisk is just reporting that its a GPT labeled disk. > format -e /dev/rdsk/c4t0d0 -> partition will allow to create GPT > partitions, including the EFI GPT partition type only required if > booting UEFI, though I find FreeBSD's gpart(8) easier for the OP's use > case of multiple pools and filesystems on a single disk. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Hipster 2020.10 text installer ISO Wow!!!!
On Tue, Mar 02, 2021 at 03:37:23PM +, Reginald Beardsley via oi-dev wrote: >Thank you again. Very helpful. The Z400 will only support IDE mode. >ACHI+RAID is the other option which I think only works with Windows. I >know it will not work with Solaris and feel fairly certain it doesn't >work with Linux or *BSD either. ACHI+RAID does work with Solaris and OI, but you have to do some preparation first. I know because I have done that with my Z400 and installed OI on it. The instructions are here: https://superuser.com/questions/635829/how-do-i-install-solaris-on-a-fake-raid-a-k-a-ahciraid-sata-sas-controller/635830#635830 -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Hipster 2020.10 text installer FAIL #3
On Mon, Mar 01, 2021 at 05:44:59PM +, Reginald Beardsley via openindiana-discuss wrote: > FWIW I created a series of slices using "format -e" with an EFI > label. No issues encountered, nor did I encounter any issues with > creating pools on them as can be seen from the console output. [...] > > root@openindiana:~# prtvtoc /dev/rdsk/c4d0 > * /dev/rdsk/c4d0 partition map This output indicates that you do not have the disk controller in AHCI mode. If you did, the device name would have a target in it, making it something like /dev/rdsk/c4t0d0 . > * Dimensions: > * 512 bytes/sector > * 9767374848 sectors > * 9767541095 accessible sectors > * > * Flags: > * 1: unmountable > * 10: read-only > * > *First Sector Last > * Partition Tag Flags Sector Count Sector Mount Directory >0 400 40 4194304 4194343 >1 400 4194344 2147483648 2151677991 >2 400 2151677992 209715200 2361393191 >3 400 2361393192 2147483648 4508876839 >4 400 4508876840 209715200 4718592039 >5 400 4718592040 2147483648 6866075687 >6 400 6866075688 2901465447 9767541134 These are Solaris partions, now called slices. They are within a single FDISK partition. You can use the partition command within format to see the slices. You can use the fdisk command within format to see the FDISK partitions. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] "format -e" segmentation fault attempting to label a 5 TB disk in Hipster 2017.10
On Mon, Feb 22, 2021 at 01:14:26AM +, Jim Klimov wrote: > The cmdk (and pci-ide) in device paths suggest IDE (emulated?) disk > access; I am not sure the protocol supported more than some limit > that was infinite-like in 90's or so. If there is really such a limit for IDE emulation, then format should describe the limit in an error message, instead of terminating with a segmentation fault. > Can you place it to SATA (possibly changing BIOS settings, and at a > risk of loading with live media to export-import rpool with new > device paths)? The usual setting is AHCI on the disk controller. My HP z400 had no AHCI setting, but did have an AHCI+RAID setting. This is known as a fake raid controller. This web page helped me install OI on it: https://superuser.com/questions/635829/how-do-i-install-solaris-on-a-fake-raid-a-k-a-ahciraid-sata-sas-controller/635830#635830 -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] DNS problem
On Sat, Feb 20, 2021 at 03:28:32PM +, Reginald Beardsley via openindiana-discuss wrote: > I'd been using a Linksys WRT54GL and DD-WRT for 12 years without > any problems. A few days ago I started having issues of not being > able to properly making connections. It might work fine for an hour > and then web sites would time out on access attempts. > I have replaced it with a Linksys N600. That is working fine from > Debian 9.3, but not with Hipster 2017.10. > If I do "nslookup login.yahoo.com" I get the usual response from > the N600. But if I attempt "traceroute login.yahoo.com" I get an > "unknown host login.yahoo.com" . Here's what I get on OI: $ host login.yahoo.com login.yahoo.com is an alias for ds-ats.member.g02.yahoodns.net. ds-ats.member.g02.yahoodns.net has address 67.195.204.151 ds-ats.member.g02.yahoodns.net has address 98.137.156.136 ds-ats.member.g02.yahoodns.net has IPv6 address 2001:4998:58:304::2000 ds-ats.member.g02.yahoodns.net has IPv6 address 2001:4998:44:3304::2000 Do you get that? The login server does not exist. The DNS server does exist, but has several IP addresses. On OI, some ethernet devices do not have a driver. That may be your problem with the Linksys N600. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] catching hell getting booted
On Wed, Feb 03, 2021 at 01:06:12PM -0500, Harry Putnam wrote: > I've been running an hp xw8600 for several years and for about 5-6 of > those yrs running openindiana OS. > > A month ago or so I shutdown OI to change out a couple of disks. > > Once I did that I have not been able to use any of the oi installation > media I've made up. Both usb stick and DVD fails to boot, No matter > how I set the boot order. And even though those same stick media will > boot my HP Z800 to live media for OI install. > > I've tried all I can think, changing usb ports, Trying ISO from CD. > The xw8600 has two of those, I set the boot order to CDrom first but it > goes right buy with out a response and tries to boot from disk. It sounds as if you are not really setting the boot order in the BIOS. Could it really that simple? HP does do some funny things with their BIOS. Are you saving your changes after you make them? Does the BIOS show the new boot order after the boot fails? Some systems will not boot from USB, but in that case they will still boot from a CD reader. I don't think that's your problem. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OpenIndiana as a server.
On Sat, Jan 30, 2021 at 11:48:35PM -0600, Judah Richardson wrote: > Just a small question: are we being attacked by chatbots? > > There seems to be a spate of users recently posting rapid fire questions > and topics combined with relatively few statements and English that leaves > a few things to be desired. We also should welcome new people, not drive them away. People learn by making mistakes. That's quite normal and usual. In fact, we need new people. If somebody asks a question, refer them to a place where they can find the answer. Please be tolerant. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ~6 minutes to OI banner/boot options in text install
On Sat, Jan 30, 2021 at 06:33:37PM +0200, Toomas Soome wrote: > > oh, well, in that case, the issue is not about OI not working in > UEFI mode (because it does), but the issue is that Xorg can not use > vesa driver when there is no vesa bios (which is perfectly good > reason). Also, having to run OI in BIOS mode because you need to run > Xorg, is also good reason, but you can not tell that OI does not > work with UEFI, because that is not true:) Well, that was my first impression. I agree now that OI itself is not at fault. > Of course the root cause is about missing DRM driver and thats the > reason why you need to use vesa in first place…. Also correct. I believe that Aurélien is working on the DRM driver. I will be happier when that is ported and working. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ~6 minutes to OI banner/boot options in text install
On Sat, Jan 30, 2021 at 08:19:16AM +0200, Toomas Soome via openindiana-discuss wrote: > > > On 30. Jan 2021, at 03:57, Gary Mills wrote: > > > > The loader works in UEFI mode, but OI does not. Usually you are > > offered a choice at boot time. Chose BIOS mode. > > What you mean by “OI does not”? In my experience with the OI live USB image, it would run in either mode. Even the installer worked correctly. However, when I tried to boot the disk where I just installed, it failed in UEFI mode. It worked in BIOS mode. The problem was likely with the VESA video driver, which is run as a last resort by Xorg. The VESA driver makes BIOS calls that fail when there is no BIOS. I'm using the Radeon HD 7450 video card that only works with the VESA driver. Hence OI boot only works in BIOS mode. /var/log/Xorg.0.log tells the tale. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ~6 minutes to OI banner/boot options in text install
On Fri, Jan 29, 2021 at 05:02:21PM -0800, Chris wrote: > OK just dragged a Dell Optiplex 790 off the shelf > with a 4 core 8 thread i5 CPU in it, and as much RAM > as I could jam in it. > BIOS: > boot UEFI You can't do that. You have to boot OI in BIOS mode. The loader works in UEFI mode, but OI does not. Usually you are offered a choice at boot time. Chose BIOS mode. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What's HASWELL support like on OI?
On Thu, Jan 28, 2021 at 05:35:38PM -0800, Chris wrote: > I'm trying to find some combination of hardware that will > produce reasonable performance at the console. By console, do you mean the raw console without a window manager? If that's the case, it's no wonder that you are finding it slow. Most people never see this, except during boot. The raw console is known to be quite slow. It's never been a problem because the terminal windows you get with a window manager are quite fast. I have five low-end systems with a variety of video cards all running OI here. All I ever did was to do the initial install from the live USB image, and do updates afterwards with the pkg command. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] When will AMD XIII CPUs be supported
On Sat, Jan 23, 2021 at 04:44:21PM +, Peter Tribble wrote: > On Sat, Jan 23, 2021 at 2:22 AM Gary Mills wrote: > > > That's peculiar: there are two drivers attached to the same hardware > > device. I've never seen that before. > > That's normal. pci1462,7309 is the MCP61 PCI bridge that multiple devices > are connected to. Thanks for the correction. I'd never seen it, but obviously you have. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] When will AMD XIII CPUs be supported
On Fri, Jan 22, 2021 at 11:39:20AM -0800, Chris wrote: > I don't have a specific setting for ahci. As a rule, when available, > I choose that. But it's simply not available. > > Here's the output for mine > > ~ > 11:35am Fri, 22 > OIDEV# prtconf -D [...] > pci1462,7309, instance #0 (driver name: nge) > pci1462,7309, instance #0 (driver name: nv_sata) > disk, instance #2 (driver name: sd) > pci1462,7309, instance #1 (driver name: nv_sata) That's peculiar: there are two drivers attached to the same hardware device. I've never seen that before. The first is an ethernet driver. The second is the SATA controller driver. It has one disk. Can you disable the ethernet in the BIOS? -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ZFS Error
On Sat, Jan 23, 2021 at 08:29:21AM +0700, Hung Nguyen Gia via openindiana-discuss wrote: > Hi. Try importing your pool on FreeBSD or Linux. The usual way is to boot the install medium on your OI system, and then import the pool there. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] When will AMD XIII CPUs be supported
On Fri, Jan 22, 2021 at 01:14:05AM -0800, Chris wrote: > > OK here's a nice picture (screenshot) I was able to capture that > pretty well sums it up. > > Driver is NOT the problem. > I think the only way I'm going to be able to install OI on this, is > by plugging my sata drive into a USB adapter, and install it there. > Then after installation. Plug the drive back into the sata port on > the MB. I thought OI had better sata support. It clearly understands > the controller. > > Well. They say a Picture paints a thousand words: > https://bsdos.info/OI/Screenshot-2021-01-22-00-12-55.png Your picture shows that it's using the nv_sata driver for the disk controller, not the ahci driver. Are you able to configure the disk controllers into AHCI mode? Doing that might fix your problem. Most systems use the ahci driver now. Here's how mine looks in OI: $ prtconf -D ... pci1b21,1062, instance #0 (driver name: ahci) disk, instance #2 (driver name: sd) disk, instance #5 (driver name: sd) disk, instance #3 (driver name: sd) disk, instance #4 (driver name: sd) As you can see, it uses two drivers, one for the controller and one for the disks. Here's how my disks look in OI: # format ... 0. c5t0d0 /pci@0,0/pci1022,1453@1,3/pci1b21,1062@0,1/disk@0,0 1. c5t1d0 /pci@0,0/pci1022,1453@1,3/pci1b21,1062@0,1/disk@1,0 2. c5t2d0 /pci@0,0/pci1022,1453@1,3/pci1b21,1062@0,1/disk@2,0 3. c5t3d0 /pci@0,0/pci1022,1453@1,3/pci1b21,1062@0,1/disk@3,0 Specify disk (enter its number): ^D -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] When will AMD XIII CPUs be supported
On Thu, Jan 21, 2021 at 04:10:40PM -0800, Chris wrote: > Thank you *very* much for the reply. > It's an AMD Athlon II X3 @3Ghz w/*Gb RAM > It's on an AM2+ board -- I know. But still... > Anyway. I used to have one of those. > The failures I indicated here turned out to be a bad PSU. I've had PSU failures too. > I've since replaced it, and I get to the color Welcome screen. I assume that's in the loader, after it's booted the copy of OI that's on the DVD or USB image. > But, a couple things; the (onboard) Nivdia Gigabit port (nge0) > causes OI all kinds of grief -- loop message regarding ipsec, followed > by dhcpd error(s). Finding that, I simply unplugged it, and shoved > an Atheros WiFi card in it. I've had bad luck with nge devices too, but never that bad. > Restarted the install, and got No disk > drives found. Well, the BIOS finds and confirms it's in good shape. > Will allow me to boot from it. But not OI. Oh it's sata (II). Anyway; > I replace the drive, and boot the OI install. Same problem -- No > drive found. That sounds like a missing driver for your disk controller. It will be included with the full OI kernel, but perhaps not with the loader. Selecting AHCI mode in the BIOS for the disk controller may fix the problem. I notice when I run: $ prtconf -D on my system, it shows ahci as the disk controller driver. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] When will AMD XIII CPUs be supported
On Thu, Jan 21, 2021 at 12:56:51PM -0800, Chris wrote: > Or, why does the 20201031 usb image text install crash > on my AMD XIII @3Ghz && 8GB RAM? What is AMD XIII? I have three AMD Ryzen systems. None of them behave that way. This is the one I use most often: $ psrinfo -vp The physical processor has 8 cores and 16 virtual processors (0-15) ... x86 (AuthenticAMD 800F82 family 23 model 8 step 2 clock 3200 MHz) AMD Ryzen 7 2700 Eight-Core Processor > The install is slow as a dog in graphics or text modes. That may not be a problem. After all, you only install once. > It either bootloops just after > zfs0 /pseudo/zfs@0 > > or it dumps core at the first language choice screen. > Any thoughts/suggestions? That certainly could be a problem. Did you capture the core file or record the traceback? -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to replace failed rpool mirror disk?
On Sun, Jan 17, 2021 at 02:11:18PM -0600, Bob Friesenhahn wrote: > I assume your replacement succeeded. > So now (trusting that we should use modern documented methods rather than > the antique methods described by the Wiki) I used > > /sbin/bootadm install-bootloader > > and no errors were reported. Adding the '-v' option also does not reveal > significant issues and I see it referring to both disks. I did that a year ago. Here's my transcript: # /sbin/bootadm install-bootloader -Mfv -P rpool be_do_installboot: device mirror-0 be_do_installboot: device c5t0d0s0 Command: "/usr/sbin/installboot -F -m -f //boot/pmbr //boot/gptzfsboot /dev/rdsk/c5t0d0s0" Output: bootblock written for /dev/rdsk/c5t0d0s0, 323 sectors starting at 1024 (abs 26112) stage1 written to slice 1 sector 0 (abs 12544) stage1 written to master boot sector be_do_installboot: device c5t1d0s0 Command: "/usr/sbin/installboot -F -m -f //boot/pmbr //boot/gptzfsboot /dev/rdsk/c5t1d0s0" Output: bootblock written for /dev/rdsk/c5t1d0s0, 323 sectors starting at 1024 (abs 26112) stage1 written to slice 1 sector 0 (abs 12544) stage1 written to master boot sector My root mirror looks like this: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror-0ONLINE 0 0 0 c5t0d0s0 ONLINE 0 0 0 c5t1d0s0 ONLINE 0 0 0 > This is the > relevant high-level description of the bootadm install-bootloader option: > >This subcommand can be used to install, update, and repair the boot >loader on a ZFS pool intended for booting. When disks in the ZFS pool >used for booting the system have been replaced, one should run bootadm >install-bootloader to ensure that all disks in that pool have the >system boot loader installed. > > There are more details in the detail section, but perhaps I must assume that > all is ok with the boot loader. It is even possible that zfs arranged to > install the boot loader on the disk automatically. To be sure all is okay, try booting from one disk and then the other. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to replace failed rpool mirror disk?
On Sun, Jan 17, 2021 at 10:56:58AM -0600, Bob Friesenhahn wrote: > One of my root pool mirror disks (c5t1d0) on an Intel system failed but it > is currently booted using the other disk (c5t0d0). This happened to me many > years before on the same system and I did successfully replace the disk. The zpool man page should be helpful to you, in particular the `zpool replace' command, if the failed disk is still installed. Otherwise, you may have to use a different command or a combination of commands. The disk may not need to be initialized with fdisk or format or some other command if you are using the whole disk. You can tell that from `zpool status'. If you are using slices, you will need to use format to make it the same as the other disk. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Microphone and pulseaudio
On Tue, Jan 12, 2021 at 09:34:47AM -0600, Gary Mills wrote: > The volume on illumos-based systems is always quite low. Here's the bug report: https://www.illumos.org/issues/13098 -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Microphone and pulseaudio
On Tue, Jan 12, 2021 at 03:10:03PM +, Tony Brian Albers wrote: > I'm having issues getting an analogue (using a 3,5mm jack connector) > microphone to work properly. I've never tried a microphone so I'm of no help there. Audio devices usually have two inputs (line and microphone) and one output (line). I wonder if it's listening on the wrong input? > It shows up in the mate-volume-control window, but even when it's at > 100% volume, there's no sound level indication. The mic works, because > when I test it with > $ cat >/tmp/foo.au > $ cat /tmp/foo.au >>/dev/audio Pulseaudio is not involved here, since you are accessing raw devices. You could use the audioplay command to replace the second command. I'd expect the same result, but it's worth trying. The volume on illumos-based systems is always quite low. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] New SPARC ISO for testing
This ISO is the same as the previous 2018 ISO except for two bug
fixes. If the last one didn't work for you, this one might.
One of the fixes is for one of disk drivers, one that's only used on
newer systems. It happens because driver is in two parts, causing the
boot to fail. It stops with this error:
undefined symbol 'sata_split_model'
The other is for the bash shell. The problem in this case, is that
it needs a library. If it's missing, the single-user console fails,
resulting in this error:
bash: fatal: libncurses.so.5: open failed
To use the new ISO, first download it from this location:
https://apt.dilos.org/oi-sparc/OI_2018_02_Text_SPARC.iso.gz
Then, check it's integrity like this:
$ digest -a sha256 OI_2018_02_Text_SPARC.iso.gz
9ea289ef064e320200ae979dae25e0c2aa8846fa57f033d742c0612cd654397f
Next, uncompress it with a command like this:
$ gunzip OI_2018_02_Text_SPARC.iso.gz
Then, burn it to a DVD. Note that the file OI_2018_02_Text_SPARC.iso
is a bootable DVD image. There's no known way to transfer it to a USB
stick. You must create and boot a DVD. As well, only the text DVD
image is available for the SPARC platform.
Next, boot the DVD on your SPARC machine. This OBP command worked for
me, although I had to do it twice:
{0} ok boot cdrom
When the text boot is successful, it will guide you through the
process of configuring and installing OI. Near the end, it will ask
you to select a disk to receive the OI installation.
Finally, boot the disk that contains the newly-installed copy of OI.
It can be used with the original repository to install new packages.
I'd like to get your reports on this new ISO. Both it and the
original ISO boot and run correctly on my T2000 system. However, it
may not run on different SPARC systems. In particular, I'd like to
know if the new ISO boots and runs on newer hardware. Please report
your hardware, and whether it succeeded or failed. If it failed, I'd
like to see the error messages. If the new ISO is successful, I will
be uploading a newer matching repository.
--
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Determine path to usb stick frm `rmformt -l' output
On Fri, Dec 18, 2020 at 10:39:38AM -0500, Harry Putnam wrote: > I have the output of rmformat -l to guide me but I'm not sure what is > the correct path. There are two shown. In order to write to USB I > need to be exact with path. > > Tail of rmformat -l output: > > [...] > 3. Logical Node: /dev/rdsk/c8t0d0p0 > Physical Node: /pci@0,0/pci103c,1306@1d,7/storage@7/disk@0,0 > Connected Device: TOSHIBA TransMemory 1.00 > Device Type: Removable > Bus: USB > Size: 14.8 GB > Label: > Access permissions: Medium is not write protected. > > I suspect it is the rdsk address shown: /dev/rdsk/c8t0d0p0 > > Can anyone confirm that I can use usbcopy in this way: > >usbcopy OI-2020.10.iso /dev/rdsk/c8t0d0p0 The usbcopy command may not work anymore. Here's what I usually do, starting with the usb image: # ll Downloads/OI-hipster-gui-20201031.usb -rw-r--r-- 1 millsstaff2052153856 Dec 12 20:14 Downloads/OI-hipster-gui-20201031.usb # mount | grep media /* Plug in the USB stick */ # mount | grep media /media/NO NAME on /dev/dsk/c7t0d0p0 read/write/nosetuid/nodevices/hidden/nofoldcase/clamptime/noatime/timezone=21600/dev=3700190 on Sat Dec 12 21:01:58 2020 # rmumount -l /dev/dsk/c7t0d0p0rmdisk,rmdisk0,NO NAME,/media/NO NAME # rmumount rmdisk0 rmdisk0 /dev/dsk/c7t0d0p0 unmounted # mount | grep media # dd if=Downloads/OI-hipster-gui-20201031.usb of=/dev/dsk/c7t0d0p0 bs=4194304 489+1 records in 489+1 records out 2052153856 bytes transferred in 404.551998 secs (4.84MB/sec) # mount | grep media /* Remove the USB stick */ -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
On Mon, Dec 14, 2020 at 04:20:49PM +, Kalle Anka via openindiana-discuss wrote: > > @Gary Mills, > the "hal service" has started and runs fine. I get the same output as you. Okay, hal is running. That is good to know. > However, there are several posts from Linux users, having the same > problems as I do. For instance: > https://unix.stackexchange.com/questions/152418/x-server-started-by-kdm-dies-during-startup-because-of-keymap-couldnt-be-loaded > http://forums.debian.net/viewtopic.php?f=10=107337 > https://bbs.archlinux.org/viewtopic.php?id=54015=2 > It seems that this problem can be fixed by reinstalling > "x11-xkb-utils" or "xkbcomp " if you read the threads. So I dont > really understand how to do that on OI? That solution is too magical for me. The OI USB image should have everything that it needs. > I also tried to dabble with BIOS settings > EHCI > XHCI > Legacy USB > ... > but I still get the same Xorg error messages as usual. How can I > fix the xkbcomp software on OI? You may be chasing the wrong fox. It seems to me that the real problem is that something is telling Xorg not to use hal. You can't do that. Near the beginning of the Xorg log is the statement: [44.620] (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AutoAddDevices. Your Xorg seems to search for the keyboard without the aid of hal. It should not be compiling a keymap at all. Perhaps the command does not exist. Perhaps it's looking in the wrong place. In any case, the error is here. > BTW, I dont use the integrated graphics of Intel HD4600, I have > shut it off. I only use the Geforce GTX 1070 Ti. And Vesa driver. How do you specify the VESA driver? Xorg does that itself if it finds that the other drivers don't work. Could you try not specifying the VESA driver for a test? In fact, try booting the OI USB image without making any changes. It should be a BIOS boot. Maybe you've already tried that. You could even try enabling the built-in Intel video and disabling the external video in the BIOS setup. Maybe the OI boot will work correctly then. The video output will be on a different connector, of course. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
On Thu, Dec 10, 2020 at 10:56:42PM +, Kalle Anka via openindiana-discuss wrote: > [ 137.882] (EE) Error compiling keymap (server-0) executing > '"/usr/bin/xkbcomp" -w 1 "-R/usr/share/X11/xkb" -xkm "-" -em1 "The XKEYBOARD > keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are > not fatal to the X server" "/var/run/xkb/server-0.xkm"' > [ 137.882] (EE) XKB: Couldn't compile keymap > [ 137.882] (EE) XKB: Failed to load keymap. Loading default keymap instead. > [ 137.903] (EE) Error compiling keymap (server-0) executing > '"/usr/bin/xkbcomp" -w 1 "-R/usr/share/X11/xkb" -xkm "-" -em1 "The XKEYBOARD > keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are > not fatal to the X server" "/var/run/xkb/server-0.xkm"' > [ 137.904] (EE) XKB: Couldn't compile keymap > [ 137.904] XKB: Failed to compile keymap > [ 137.904] Keyboard initialization failed. This could be a missing or > incorrect setup of xkeyboard-config. > [ 137.904] (EE) > Fatal server error: > [ 137.904] (EE) Failed to activate virtual core keyboard: 2(EE) > [ 137.904] (EE) > Please consult the Project OpenIndiana support > at http://openindiana.org > for help. > [ 137.904] (EE) Please also check the log file at "/var/log/Xorg.0.log" for > additional information. > [ 137.904] (EE) > [ 141.548] (EE) Server terminated with error (1). Closing log file. I did some testing with the OI-hipster-gui-20201031.usb USB image on one of my systems. It uses an Intel CPU with built-in Intel graphics. It booted the image's copy of OI to produce the usual desktop with a few additional icons. The portion of the /var/log/Xorg.0.log file that shows the keyboard configuration was like this: [ 141.103] (II) config/hal: Adding input device hotkey [ 141.104] (II) LoadModule: "hotkey" [ 141.104] (II) Loading /usr/lib/xorg/modules/input/amd64/hotkey_drv.so [ 141.108] (II) Module hotkey: vendor="X.Org Foundation" [ 141.108]compiled for 1.19.5, module version = 1.0.0 [ 141.108]Module class: X.Org XInput Driver [ 141.108]ABI class: X.Org XInput driver, version 24.1 [ 141.108] (II) Using input driver 'hotkey' for 'hotkey' [ 141.108] (**) hotkey: always reports core events [ 141.108] (II) XINPUT: Adding extended input device "hotkey" (type: KEYBOARD, id 6) [ 141.109] (**) hotkey_events_init and pipe open succeeded [ 141.110] (II) config/hal: Adding input device keyboard [ 141.111] (II) LoadModule: "kbd" [ 141.111] (II) Loading /usr/lib/xorg/modules/input/amd64/kbd_drv.so [ 141.111] (II) Module kbd: vendor="X.Org Foundation" [ 141.111]compiled for 1.19.5, module version = 1.9.0 [ 141.111]Module class: X.Org XInput Driver [ 141.111]ABI class: X.Org XInput driver, version 24.1 [ 141.111] (II) Using input driver 'kbd' for 'keyboard' [ 141.112] (**) keyboard: always reports core events [ 141.112] (**) keyboard: always reports core events [ 141.112] (**) Option "Device" "/dev/usb/hid1" [ 141.112] (II) keyboard: Opened device "/dev/usb/hid1" [ 141.112] (**) Option "XkbRules" "base" [ 141.112] (**) Option "XkbModel" "sun_type6_usb" [ 141.112] (**) Option "XkbLayout" "us" [ 141.112] (WW) Option "XkbVariant" requires a string value [ 141.112] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/pci1043_8694_14/device_8/keyboard_0_if0_1_logicaldev_input" [ 141.112] (II) XINPUT: Adding extended input device "keyboard" (type: KEYBOARD, id 7) [ 141.112] (**) Option "StreamsModule" "usbkbm" [ 141.112] (--) keyboard: Keyboard type: USB (6) [ 141.112] (--) keyboard: Keyboard layout: 0 Note that hal is used to obtain the keyboard device in my case. I wonder if the hal service has failed in your case. Here's how it looks to me: jack@openindiana:/jack$ svcs -l svc:/system/hal:default fmri svc:/system/hal:default name Hardware Abstraction Layer daemon enabled true stateonline next_state none state_time Sun Dec 13 10:38:42 2020 logfile /var/svc/log/system-hal:default.log restartersvc:/system/svc/restarter:default contract_id 41 dependency require_all/none svc:/system/filesystem/minimal (online) dependency require_all/none svc:/system/device/local (online) dependency require_all/none svc:/system/dbus (online) dependency require_all/none svc:/system/sysevent (online) dependency optional_all/none svc:/system/keymap (online) -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
On Thu, Dec 10, 2020 at 10:56:42PM +, Kalle Anka via openindiana-discuss wrote: > Gary Mills,How far the boot process goes? Well, I booted into BIOS > and it boots until X11, which will not start. At that point, it is actually running a version of OI, coming from the USB image. > Here is the Xorg.0.log > file. I tried another keyboard, and also I tried it in USB2 and USB3 > ports. But still it doesnt work to boot X11. It seems to be an error > with the keyboard? I dont get it, I have a Sun keyboard. And I tried > another cheap keyboard. I have two systems with Sun keyboards running OI. They are both USB keyboards. Something is wrong with your keyboard, though. The log file below indicates that. Do you have a BIOS setting that says something about a legacy keyboard? You may have to change that. > I have a Geforce GTX 1070 Ti gpu, so I instead used VESA driver. > And ACPI. According to the log file below, it is an NVIDIA card. That should be supported. Normally you are better off not to specify the VESA driver, but let Xorg figure it out. > X.Org X Server 1.19.7 [...] > [ 137.678] (II) VESA(0): VESA VBE OEM Vendor: NVIDIA Corporation > [ 137.678] (II) VESA(0): VESA VBE OEM Product: GP104 Board > [ 137.678] (II) VESA(0): VESA VBE OEM Product Rev: Chip Rev > [ 137.678] (II) VESA(0): virtual address = fc7fea80, VGAbase = > fc7feed6 > physical address = 0xd100, size = 16777216 > [ 137.691] (II) VESA(0): Setting up VESA Mode 0x118 (1024x768) > [ 137.834] (==) VESA(0): Default visual is TrueColor > [ 137.834] (==) VESA(0): Backing store enabled > [ 137.834] (==) VESA(0): DPMS enabled > [ 137.834] (==) RandR enabled > [ 137.837] (II) AIGLX: Screen 0 is not DRI2 capable > [ 137.837] (EE) AIGLX: reverting to software rendering > [ 137.849] (II) IGLX: enabled GLX_MESA_copy_sub_buffer > [ 137.850] (II) IGLX: Loaded and initialized swrast > [ 137.850] (II) GLX: Initialized DRISWRAST GL provider for screen 0 > [ 137.882] (EE) Error compiling keymap (server-0) executing > '"/usr/bin/xkbcomp" -w 1 "-R/usr/share/X11/xkb" -xkm "-" -em1 "The XKEYBOARD > keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are > not fatal to the X server" "/var/run/xkb/server-0.xkm"' > [ 137.882] (EE) XKB: Couldn't compile keymap > [ 137.882] (EE) XKB: Failed to load keymap. Loading default keymap instead. > [ 137.903] (EE) Error compiling keymap (server-0) executing > '"/usr/bin/xkbcomp" -w 1 "-R/usr/share/X11/xkb" -xkm "-" -em1 "The XKEYBOARD > keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are > not fatal to the X server" "/var/run/xkb/server-0.xkm"' > [ 137.904] (EE) XKB: Couldn't compile keymap > [ 137.904] XKB: Failed to compile keymap > [ 137.904] Keyboard initialization failed. This could be a missing or > incorrect setup of xkeyboard-config. > [ 137.904] (EE) > Fatal server error: > [ 137.904] (EE) Failed to activate virtual core keyboard: 2(EE) > [ 137.904] (EE) > Please consult the Project OpenIndiana support > at http://openindiana.org > for help. > [ 137.904] (EE) Please also check the log file at "/var/log/Xorg.0.log" for > additional information. > [ 137.904] (EE) > [ 141.548] (EE) Server terminated with error (1). Closing log file. I left the portion of the X11 server log file that shows the errors. Mine is quite different. Here's the keyboard portion: [43.648] (II) Using input driver 'kbd' for 'keyboard' [43.648] (**) keyboard: always reports core events [43.648] (**) keyboard: always reports core events [43.648] (**) Option "Device" "/dev/usb/hid1" [43.648] (II) keyboard: Opened device "/dev/usb/hid1" [43.648] (**) Option "XkbRules" "base" [43.648] (**) Option "XkbModel" "sun_type6_usb" [43.648] (**) Option "XkbLayout" "us" [43.648] (WW) Option "XkbVariant" requires a string value [43.648] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/pci1043_8694_14/device_8/keyboard_0_if0_4_logicaldev_input" [43.648] (II) XINPUT: Adding extended input device "keyboard" (type: KEYBOARD, id 7) [43.648] (**) Option "StreamsModule" "usbkbm" [43.648] (--) keyboard: Keyboard type: USB (6) [43.648] (--) keyboard: Keyboard layout: 0 -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
On Thu, Dec 10, 2020 at 05:54:12PM +, Kalle Anka via openindiana-discuss wrote: > Yes I tried to boot the usb stick both in UEFI and BIOS mode. Both > fail. In what way? I see some error messages in the dmesg output. I > have pasted that long dmesg output in a reply here with date: Wed > Dec 9 20:47:35 UTC 2020, you can read that mail for more > information. But it seems that X11 does not start. The screen > flickers thrice and then exits to command line. OI only works in BIOS mode, although the OI loader works in both. I was confused by that difference. So, use BIOS mode. How far does the boot get? Do you get the countdown from the loader? I assume the loader worked but when it attempted to boot openindiana, X11 failed. In that case, the file /var/log/Xorg.0.log should tell you why it failed. You should be able to log in on the command line to see that file. What graphics adapter are you using? -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions
On Sat, Dec 05, 2020 at 04:02:24PM +, Kalle Anka via openindiana-discuss wrote: > So I should not install BIOS OI and UEFI W10 for dualbooting on the > same disk. I learned this the hard way. I had a Win10 and Solaris > 11.2 dual booting install, on the same disk using BIOS, i.e. MBR > disk. Then an W10 update silently changed the disk to UEFI (GPT > disk), and Solaris 11.2 was still on MBR. So I could boot W10, but > not boot Solaris. It took me a long time to figure out why Solaris > would not boot. I had to reinstall Solaris using UEFI. I've used dual booting of Windows and openindiana on a laptop that only had one disk. It works, but is annoying. The laptop is 64-bit x86. It came with Windows 7 installed on FDISK partitions. I later upgraded it to Windows 10. I booted a live DVD and used it to shrink the large NTFS partition. Then I created an empty FDISK partition that used all of the newly-freed space. I installed OI on that new FDISK partition. At that point, it booted into OI. Once I configured the OI loader to chainload the Windows boot partition, I could select the new entry in the OI loader menu to boot Windows. Both Windows and OI were installed for BIOS boot, of course. The problem I had was entirely with Windows. Windows updates would fail with a mysterious error message because it was unable to mount the boot partition. The only solution I found was to make the Windows partition the active partition. After that, it booted directly into Windows and the update succeeded. To get back to dual booting, I had to make the OI partition the active one. After a while, I grew tired of switching active partions, and left it in Windows. > To solve my problem of BIOS os and UEFI os, I wonder if this might > work: I remove all disks except one, and install Win10 using > UEFI. Then I remove all disks, and insert another disk to which I > install BIOS OpenIndiana. Then I insert all disks, and when I boot > my PC, I choose which OS to boot from the disk boot menu by pressing > F11. Do you think this could be a way to have both BIOS OpenIndiana > and UEFI Win10 on my PC, but on different disks? I have read that > you should not install BIOS and UEFI oses on the same PC, even on > the different disks - but I dont know why. I cannot find information > on this. But if I choose the different disks to boot in the boot > menu, this could work? Anyone know? Yes, that should work. I do exactly that on my T2000 (SPARC) system. You may not even need to remove disks, although that's the safest thing. On x86, you can choose the disk to boot from the BIOS boot menu. If you want Windows and an illumos distribution to run simultaneously, you will have to use some form of virtualization. That's the only way. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Security alert: important fix for illumos-gate has been integrated
On Fri, Oct 23, 2020 at 05:11:29PM +0200, Andreas Wacknitz wrote: > > illumos-gate had an important fix for a PAM vulnerability (pre-auth > remote root exploit as described here: CVE-2020-14871 > <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14871>) yesterday. > This change has been integrated in our package repository last night. > Please update your OpenIndiana Hipster installations (pfexec pkg update > -v ) and reboot in order to close that gap. This is a positive response, for a change. I've just updated OI on two of my test systems, one Intel and the other AMD Ryzen. Both updates were successful. I was able to log in on the console and remotely for both systems. Everything appeared quite normal. Everything seemed to work. I'm pleased with the updates. The first was from an update done on 2020-10-05. The second was from an older update, done on 2020-07-05. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Xorg missing privileges
On Fri, Oct 23, 2020 at 11:37:02AM +0200, Predrag Zecevic - Unix Systems
Administrator wrote:
>
> This is pretty annoying: Xorg fills in syslog with messages like:
>
> [2020-10-23 10:15:03] solarix genunix: [ID 864859 kern.notice] NOTICE:
> Xorg[1075]: missing privilege "sys_devices" (euid = 2903, syscall = 54)
> needed at drv_priv+0x1d#012
I don't get those messages, either in /var/adm/messages or
/var/log/syslog . What are you doing that I'm not?
> euid is my UID:
> :; id
> uid=2903(predrag_zecevic) gid=1961(admin) groups=1961(admin),1962(vboxuser)
The parent process of Xorg is lightdm . It runs as root, but Xorg
runs as the console user. That will be you. You may need to grant
yourself more privileges.
> For today only:
>
> :; grep -E "2020-10-23.*Xorg.*missing privilege" /var/adm/messages | awk
> '{printf("%s\n", $12)}' | sort | uniq -c | sort -rn
> 75750 "sys_devices"
> 173 "file_dac_search"
> 4 "proc_owner"
> 2 "file_dac_read"
>
> What has to be added to /etc/security/exec_attr.d/SOME_FILE to prevent this?
It's possible that nobody on this mailing list understands illumos
privileges. Maybe try an illumos mailing list.
--
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Qt5 and libgcc_s
On Sun, Oct 18, 2020 at 05:24:29PM +, Apostolos Syropoulos via openindiana-discuss wrote: > > I tried to compile a Qt5 application and during the last stage What was the application? Is it already available from OI? As far as I can tell, only desktop/fbreader, media/vlc, and system/virtualbox are available from OI? > I got the following error: > > apostolo@adalind>> make > g++ -m32 -Wl,-R,/usr/lib/qt/5.8/lib -Wl,-R,/usr/gcc/7/lib/ -o > LANShare main.o settings.o util.o singleinstance.o mainwindow.o > receiverselectordialog.o aboutdialog.o settingsdialog.o > devicebroadcaster.o receiver.o sender.o transfer.o transferserver.o > device.o devicelistmodel.o transferinfo.o transfertablemodel.o > qrc_res.o moc_singleinstance.o moc_mainwindow.o > moc_receiverselectordialog.o moc_aboutdialog.o moc_settingsdialog.o > moc_devicebroadcaster.o moc_transfer.o moc_transferserver.o > moc_transferinfo.o moc_transfertablemodel.o -L/usr/lib > -L/usr/X11/lib -L/usr/lib/qt/5.8/lib -lQt5Widgets -lQt5Gui > -lQt5Network -lresolv -lsocket -lxnet -lnsl -lQt5Core -lGL -lpthread > -lrt > ld: fatal: file /usr/gcc/6/lib/libgcc_s.so: version 'GCC_7.0.0' does not > exist: > required by file /usr/lib/qt/5.8/lib/libQt5Gui.so > ld: fatal: file /usr/gcc/6/lib/libgcc_s.so: version 'GCC_7.0.0' does not > exist: > required by file /usr/lib/libicui18n.so.66 > ld: fatal: file processing errors. No output written to LANShare > collect2: error: ld returned 1 exit status > make: *** [Makefile:303: LANShare] Error 1 It sounds as if the application requires gcc-6, but you tried to build it with gcc-7. Can you try gcc-6 instead? -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Printing from Firefox does not work
On Thu, Oct 15, 2020 at 10:35:37AM -0400, John D Groenveld wrote: > > root@openindiana:~# pkg search -l > depend::library/desktop/gtk3/gtk-backend-cups > INDEX ACTION VALUE > PACKAGE > incorporate depend library/desktop/gtk3/gtk-backend-cups@3.24.23-2020.0.1.0 > pkg:/consolidation/userland/userland-incorporation@0.5.11-2020.0.1.13521 > require depend library/desktop/gtk3/gtk-backend-cups > pkg:/mate_install@0.1-2020.0.1.42 > > I installed my test Hipster VM via the text ISO and then installed > mate_install to get the GUI. > Does the GUI ISO installer not include mate_install? I found the cause. `pkg update' can only update the installed packages. mate_install is not installed. Therefore, the dependancy on that package is not consulted. mate_install is installed by the live image, but it is removed again when the install completes. mate_install is a list of packages that make up a Mate installations, but it gets removed again, making it a special case. Because of this special treatment for mate_install, that package doesn't really work. If you have done the install some time ago, `pkg update' will not observe changes to mate_install . The only solution is to make mate_install something that can be installed permanently. At the very least, the gtk-backend-cups dependancies should be attached to real packages. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Printing from Firefox does not work
On Thu, Oct 15, 2020 at 10:35:37AM -0400, John D Groenveld wrote: > In message <20201015140917.ga18...@imap.fastmail.com>, Gary Mills writes: > >library/desktop/gtk2/gtk-backend-cups > >library/desktop/gtk3/gtk-backend-cups > > > >were not installed. These packages deliver libprintbackend-cups.so . > >Once I installed these two packages, the firefox print dialogue showed > >my CUPS print queue. [...] > > root@openindiana:~# pkg search -l > depend::library/desktop/gtk3/gtk-backend-cups > INDEX ACTION VALUE > PACKAGE > incorporate depend library/desktop/gtk3/gtk-backend-cups@3.24.23-2020.0.1.0 > pkg:/consolidation/userland/userland-incorporation@0.5.11-2020.0.1.13521 > require depend library/desktop/gtk3/gtk-backend-cups > pkg:/mate_install@0.1-2020.0.1.42 > > I installed my test Hipster VM via the text ISO and then installed > mate_install to get the GUI. > Does the GUI ISO installer not include mate_install? I don't know, but then I do it differently. I did the install a long time ago. Since then, I've been doing updates. The second last update was from hipster-20180701 to hipster-20200802 . With that one, the dialogue box within firefox did not show my CUPS queue. Before that, it had `print to lpr', which I now understand got removed. My last update was from hipster-20200802 to hipster-20201012 . Nothing changed in firefox with that one. Since I installed those two packages, the print dialogue showed my CUPS printer and pre-selected it. In any case, the update did not install those packages. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Printing from Firefox does not work
On Wed, Oct 14, 2020 at 02:42:21PM -0500, Tim Mooney via openindiana-discuss wrote: > > What does > > pkg list | egrep -i print > > output? Your suggestion gave me a clue. I did some reading to fill in the blanks. The print dialogue window in firefox, and in a few other applications, is actually produced by GTK. What it displays is controlled by shared libraries in: /usr/lib/amd64/gtk-*/*/printbackends /usr/lib/gtk-*/*/printbackends This directory only contained libprintbackend-file.so . The packages: library/desktop/gtk2/gtk-backend-cups library/desktop/gtk3/gtk-backend-cups were not installed. These packages deliver libprintbackend-cups.so . Once I installed these two packages, the firefox print dialogue showed my CUPS print queue. I expect that other people will encounter this same problem. To prevent that, these two packages should be installed with GTK or CUPS, probably with CUPS. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Printing from Firefox does not work
On Wed, Oct 14, 2020 at 08:09:03PM +0200, Andreas Wacknitz wrote: > I have configured cups for my network printer and that one is available > in firefox. Thanks. I now understand that it's possible. I only need to know what I have to do to make it work for me. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Printing from Firefox does not work
On Wed, Oct 14, 2020 at 02:42:21PM -0500, Tim Mooney via openindiana-discuss wrote: > > I don't think you need to share it, but I'm not certain. I didn't think so either, but there's not much left to do. > It's been a long > time since I set up printing on my hipster workstation and I don't > remember if I had to do anything special to get firefox to see the queues. > > What does > > pkg list | egrep -i print > > output? A long list: $ pkg list '*print*' NAME (PUBLISHER) VERSION IFO library/print/cups-libs 1.7.5-2020.0.1.3 i-- print/cups1.7.5-2020.0.1.3 i-- print/cups-filters1.11.2-2020.0.1.4i-- print/cups/system-config-printer 2.30.0-2020.0.1.3i-- print/filter/a2ps 4.14-2020.0.1.2 i-- print/filter/ghostscript 9.26-2020.0.1.0 i-- print/filter/ghostscript/fonts/gnu-gs-fonts-other 6.0-2020.0.1.0 i-- print/filter/ghostscript/fonts/gnu-gs-fonts-std 6.0-2020.0.1.0 i-- print/filter/gutenprint 5.2.14-2020.0.1.1i-- print/filter/hplip3.19.12-2020.0.1.0 i-- print/lp/print-client-commands0.5.11-2020.0.1.20084i-- print/psutils 1.17-2020.0.1.2 i-- print/qpdf6.0.0-2020.0.1.0 i-- x11/keyboard/xkbprint 1.0.5-2020.0.1.0 i-- Have I omitted a package? -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Printing from Firefox does not work
I have the print queue `xerox' defined in CUPS. PRINTER=xerox is in the environment in every terminal window and in Firefox. I can display this queue with `lpq' and print to it with `lpr ...'. It does appear in /etc/printers.conf . Still, in Firefox, the print dialog box only gives me one option: print to file. How do I get Firefox to give me another option for printing to the `xerox' queue? I only have the one printer. Do I need to share this printer in CUPS? Is that it? Something else? -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Xerox B215 printer with CUPS
On Tue, Sep 29, 2020 at 06:02:52AM +, Tony Brian Albers wrote: > Have you tried talking to Xerox support? AFAIK something called "Xerox > Printer Manager" should be supported on Solaris, and with a little luck > it might run on OI. That sounds complicated, especially since we alread have CUPS on OI. I did find a ppd file that works nicely with CUPS on OI. It was on the CD that came with the printer. It was called xpb215.ppd . -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Xerox B215 printer with CUPS
On Mon, Sep 28, 2020 at 08:56:27PM -0500, Gary Mills wrote: > > Does anyone have a ppd file for this printer that works on OI? I found one. It was on the CD that comes with the printer, in the PS directory. The name is xpb215.ppd . It's clearly Postscript, but that's fine. CUPS is happy with this file, and so am I. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Xerox B215 printer with CUPS
On Thu, Aug 27, 2020 at 02:27:03PM -0500, Tim Mooney via openindiana-discuss wrote: > In regard to: [OpenIndiana-discuss] Xerox B215 printer with CUPS, Gary...: > > > I do have a PPD file, Xerox_B215_Series.ppd, that I downloaded from > > the Xerox site. The file does say that it's for linux only, but I > > assume it will work with OI. > > It should, but it depends somewhat on how the PPD was generated and > what assumptions were made. Sometimes PPDs that assume Linux have > embedded paths to commands (filters) they expect to be present on the > Linux system. OI may not have the same filter installed, or it may be > a different version. I just tried it, and got this error from CUPS: E [28/Sep/2020:15:43:22 +0600] xerox: File "/usr/lib/cups/filter/rastertospl" not available: No such file or directory > I would definitely try use the PPD from Linux, but I would also examine it > to see if you spot any places where it's assuming paths or filters from > an environment that may not quite match OI. The beginning of the ppd file is like this: *FormatVersion: "4.3" *FileVersion: "1.0" *LanguageVersion: English *LanguageEncoding: ISOLatin1 *PCFileName: "B215.ppd" *Manufacturer: "Xerox" *Product: "(LaserMFP)" *cupsVersion: 1.1 *cupsManualCopies: False *cupsModelNumber: 196 *cupsFilter: "application/vnd.cups-raster 0 rastertospl" *ModelName: "Xerox B215 Series" *ShortNickName: "B215" *NickName: "Xerox B215 Series" *1284DeviceID: "MFG:Xerox;CMD:SPL;MDL:B215 Series" *PSVersion: "(3010.000) 550" *LanguageLevel: "3" *ColorDevice: False *DefaultColorSpace: Gray *FileSystem:False *Throughput:"21" The rastertospl filter does not exist on OI. I understand that it's a proprietary filter without source. [...] > > Are you actually using this printer model? > > What PDL method does CUPS use for this printer? > > I'm not using an Xerox printers current, so I don't know. You can > probably tell what CUPS will send to the printer by looking at the PPD, > though. I can't tell from the ppd file. I see `setpagedevice' all over the place. That sounds like Postscript to me. I also see `@PJL' all over the place. That's HP printer talk to me. I don't know what it's doing. Does anyone have a ppd file for this printer that works on OI? -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Xerox B215 printer with CUPS
On Sun, Aug 30, 2020 at 07:28:46PM +0100, Jonathan Adams wrote: > late to the game here, but if your PPD file from Xerox doesn't work very > well, it's sometimes worth downloading the one from OpenPrinting.org, but > only if the one direct from Xerox doesn't work well for you. Not too late. I haven't tried that PPD file yet. I've been working on something else, and also trying to limit my time sitting in front of my computer screens. So far, I'm only collecting suggestions about my new printer. Your suggestion is valuable. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Xerox B215 printer with CUPS
I just acquired a Xerox B215 printer and connected it to OI. It's a laser multi-function printer with a control panel for local configuration. It has three PDL methods: PCL Postscript XPS . The CUPS web page displayed a list of Xerox printer models. None of them matched my printer. I chose the first one. The printer does work with CUPS, but I'm left with questions. I do have a PPD file, Xerox_B215_Series.ppd, that I downloaded from the Xerox site. The file does say that it's for linux only, but I assume it will work with OI. The CUPS web page will accept a PPD file, but I'd like to know what it will do with this file. Will CUPS copy this file from anywhere, even from a temporary location? Have you done this? Did the PPD file improve the printing? Are you actually using this printer model? What PDL method does CUPS use for this printer? -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] System unstable after pkg update Aug 6 and 8
On Mon, Aug 10, 2020 at 12:37:02PM -0500, Tim Mooney wrote: > > I have seen boot messages about a device having been retired, but I > haven't tracked down which device is being referenced. The stuff I use > regularly is still working, so it unfortunately hasn't been a priority. That message seems very familiar, except in my case the device was needed. I have an open illumos bug report that may be related to this problem: https://www.illumos.org/issues/12387 My workaround was to disable the fault manager, the service that retired the device. Of course, you need to be able to boot the BE concerned to disable the service. You do it like this: # svcadm disable svc:/system/fmd:default If you can't boot that BE, you can rename the executable instead. It's called: /usr/lib/fm/fmd/fmd . You need to boot another BE first. I renamed it to fmd- and then was able boot the BE. You have to mount the BE in question first, of course, and unmount it afterwards. `beadm' will do that for you. You can also do it from the install media, usually the USB image. That's what I did, logging remotely as jack/jack. I used sudo to get root. Here's a transcript: root@openindiana:/jack# cd / root@openindiana:/# mkdir /a root@openindiana:/# zpool import -f -R /a rpool root@openindiana:/# beadm mount hipster-20200705-02 /b Mounted successfully on: '/b' root@openindiana:/# cd /b/a/usr/lib/fm/fmd root@openindiana:/b/a/usr/lib/fm/fmd# mv fmd fmd- root@openindiana:/b/a/usr/lib/fm/fmd# cd / root@openindiana:/# bootadm update-archive -R /b/a Creating boot_archive for /b/a updating /b/a/platform/i86pc/amd64/boot_archive (CPIO) root@openindiana:/# beadm unmount hipster-20200705-02 Unmounted successfully root@openindiana:/# zpool export rpool root@openindiana:/# zpool list no pools available root@openindiana:/# : init 5 -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Mate constrains window size
On Thu, Aug 06, 2020 at 04:53:34PM +0200, Andreas Wacknitz wrote: > Your code should work but ~/.emacs is not the only possible init file. > Emacs looks for your init file using the filenames ~/.emacs, > ~/.emacs.el, or ~/.emacs.d/init.el. The only one I have is .emacs . > I suggest to make sure you have only one file and then create an .emacs > file with only > your two lines > > (add-to-list 'default-frame-alist '(height . 36)) > (add-to-list 'default-frame-alist '(width . 80)) > > and see what happens. I tried that, and the same thing with the --no-init-file option. The two windows are identical, with 79x35 geometry. By the way, I get those numbers by a left mouse click on the border of the window. When I change the values in .emacs to 37 and 81, I still get the 79x35 geometry. Something is constraining the window size. It's the smaller font that allows the width to increase to 79. When I press the Maximize Window button in the title bar, the geometry does increase in both dimensions. Maybe this is how Mate is supposed to work. > If it works you can add your other settings peu à peu. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Mate constrains window size
On Wed, Aug 05, 2020 at 09:37:11PM +0200, Andreas Wacknitz wrote: > > I'd check .Xresources and .Xdefaults first for any geometry settings. I don't have either of those files. From what I've read, the first step in debugging is to run emacs without the .emacs file. I did this with: $ emacs --no-init-file The editing area changed from 63x31 to 79x35, much closer to what I wanted. Emacs also had a smaller font but a brighter background. The conclusion is inescapable: something in my .emacs file was making those changes. I removed these lines: (custom-set-variables ;; custom-set-variables was added by Custom. ;; If you edit it by hand, you could mess it up, so be careful. ;; Your init file should contain only one such instance. ;; If there is more than one, they won't work right. ) (custom-set-faces ;; custom-set-faces was added by Custom. ;; If you edit it by hand, you could mess it up, so be careful. ;; Your init file should contain only one such instance. ;; If there is more than one, they won't work right. '(default ((t (:inherit nil :stipple nil :background "#AE00B200C300" :foreground "#" :inverse-video nil :box nil :strike-through nil :overline nil :underline nil :slant normal :weight normal :height 120 :width normal :foundry "unknown" :family "DejaVu Sans Mono") After that, the screen looked the same as with --no-init-file . I suspect that what I'm seeing now are built-in emacs defaults. This is a great improvement. > Then maybe there is something beneath .config/, perhaps marco has some > geometry settings stored for emacs sessions. There are many things below .config . The ones from August will be after the update. The ones from 2017 and 2018 will be from my previous OI version. The ones from 2010 will be from an even older version: drwxr-xr-x 2 millsstaff 3 Aug 5 07:34 dconf drwxr-xr-x 3 millsstaff 5 Aug 4 20:46 caja -rw-r--r-- 1 millsstaff 1613 Aug 3 08:27 mimeapps.list drwx-- 3 millsroot 6 Aug 2 19:29 menus drwx-- 2 millsother 3 Jul 13 13:12 gtk-2.0 drwxr-xr-x 3 millsstaff 3 Sep 3 2018 libreoffice drwxr-xr-x 3 millsstaff 3 Jul 28 2018 mate-session drwx-- 3 millsstaff 3 Jul 10 2018 mate drwxr-xr-x 2 millsstaff 2 Jul 7 2018 yelp drwxr-xr-x 2 millsstaff 3 Jul 3 2018 gtk-3.0 drwx-- 2 millsstaff 3 Jul 3 2018 pulse drwx-- 2 millsstaff 3 Apr 1 2018 brasero drwx-- 2 millsstaff 3 Dec 14 2017 totem drwxr-xr-x 3 millsstaff 3 Aug 22 2017 gnome-session drwxr-xr-x 2 millsstaff 5 Aug 22 2017 session-state drwx-- 3 millsstaff 3 Dec 3 2010 metacity drwx-- 2 millsstaff 4 Dec 3 2010 tracker -rw-r--r-- 1 millsstaff 11 Dec 3 2010 user-dirs.locale -rw--- 1 millsstaff672 Dec 3 2010 user-dirs.dirs > You can try this: > Enter the following line in a buffer (eg. scratch), position the cursor > at the end: > (setq default-frame-alist '((left . 0) (top . 0) (width . 80) (height . > 30))) > > Then press C-x X-e (eval-last-sexp) followed by C-x 5 2 > (make-frame-command). This should open a new frame with the given width > and height. That seemed to work. Thanks for the help. I appreciate it. > Alternatively, you can change the actual frame: > (set-frame-width (selected-frame) 80) > (set-frame-height (selected-frame) 30) > and press C-x C-e (for each line). That works too. In fact, by making them 81 and 37, I can enlarge the screen to 80x36 like I want it. When I put those two lines in my .emacs file, nothing happens. I assume they are not being executed. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Mate constrains window size
On Tue, Aug 04, 2020 at 08:02:23AM +0200, Andreas Wacknitz wrote: > > I am also using emacs quite heavily and I can definitely say that > resizing emacs' frame works for me on OI. I'm happy to meet another emacs user. Of course, this problem may not be specific to emacs. Does Mate have a default window size? Does emacs appear in the Applications/Programming menu on your desktop, like it does in mine? Does emacs have a blue-grey background? > So it must be your configuration that prevents the resizing. That was my conclusion, and also my question. Maybe this behavior is caused by something left over from the Gnome desktop. Where should I look? -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Mate constrains window size
I just updated a system from hipster-20180701 to hipster-20200802 . I assume it changed from gnome to mate in the update. Almost everything worked afterwards. I was quite impressed. One thing that fails to work now is the window size for emacs. Emacs is the only text editor that I use. The size now is 63 x 31. I know I can resize it by pulling on the window frame with my mouse, but I'd like it to start out at 80 x 36. This used to happen with gnome when I added these lines to my .emacs file: (add-to-list 'default-frame-alist '(height . 36)) (add-to-list 'default-frame-alist '(width . 80)) I've tried many things. I tried the command-line option -geometry, setting geometry in my .Xdefaults, and adding this line to my .emacs file: (when window-system (set-frame-size (selected-frame) 80 36)) All of these attempts have failed. I conclude that the mate window manager is constraining the window size. Is there some way I can tell the window manager to set the default size the way I want it? -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What's the easiest, straight-shot way to upgrade to a new boot SSD?
On Fri, Jun 19, 2020 at 01:23:35PM -0500, Judah Richardson wrote: > > I currently run OpenIndiana Hipster on a 32 GB SSD. I'd like move that > installation to a 128 GB SSD. What's the easiest way to do this? The easiest way is to use zpool commands. First, add the large SSD as half a mirror to the smaller one. Then, detach the smaller one. These options are all described in the zpool man page. You will likely need to use the installboot command on the large SSD to make it bootable before you do the detach. This operation is described in the installboot man page. > I was thinking of using Clonezilla, but I'm not sure if that's the way to > go here. I'd recommend using native illumos commands instead. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Error updating from hipster-202000504
On Sat, Jun 06, 2020 at 07:37:02PM +0200, Aurélien Larcher wrote: > Usually this happens when the repository is being refreshed or rebuilt. I retried the upgrade this morning. It was successful, with no errors. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
