Re: From Xfce to Mate
MATE in OpenBSD does have a display utility. Via the command line, it's called mate-display-properties. Launching from the MATE menu, it's in System --> Preferences --> Hardware --> Displays. You might have been missing some of the MATE packages. On Mon, Mar 18, 2024 at 11:48 AM Dan wrote: > > Hello, > > In these days searching to fix security details on my station, eg. reducing > the exposure to GUI programs, > etc. I tried to port my dev environment from Xfce to Mate and here some of my > thoughts: > > 1) Mate is much lighter, eg tcl/tk software go up like a twist; > 2) by multi screens the porting is a true adventure cause Mate doesn't come > with a > "Display utility", all the screen configuration happens by xrandr; > 3) the software that accompaign Mate is few or doesnt run, eg the power > management > utility doesnt function or I can't set my custom 5 Mode background (the > background utility > doesnt pop up); > 4) the context menu by right clicking anywhere on the desktop has no > application menu > apparently.. this the latest problem.. > > I passed a full night with Mate (..) but for now I was happy to come > back to my steps and restore Xfce, although performances seem very > interesting. > -Dan >
Re: Minimum viable HW for OpenBSD
Supported hardware information is listed here: https://www.openbsd.org/plat.html Each platform's link provides further information. On Fri, Mar 15, 2024 at 9:44 AM Mizsei Zoltán wrote: > > Hi, > > I'd like to build a small, portable system, not entirely different from a so > called "cyberdeck". For this project I am actively looking for the minimum > viable HW which supports OBSD. I would like to get some hints, as so far I > was unable to find the perfect hw (maybe it doesn't even exists). > > My requirements are: > - low power consumption (battery powered) > - small in sizez > - ARM / ARM64 / RISC-V or something else > - CLI > - UART > - USB > - WiFi (ideally integrated, but can be usb attached aswell) > - replaceable storage (SD card, or similar) > - ideally some onboard storage (eMMC?) > - and ideally some kind of supported display output > > I would like to either reuse the enclosure of a small handheld device which > have a display and a keyboard or print an own one and source some > off-the-shelf components and get them somehow working together. > > I was looking at minimum viable computing and found RetroBSD/DiscoBSD [1,2], > they are BSD 2.x ports for various microcontrollers (100+ Mhz, 1-2MB RAM), > but they can't realistically support me in the modern world (USB, WiFi). > > I have also considered the various SBCs in "Zero" and "Nano" form-factor, but > i was unable to find any which won't cause me headache with the > non-upstreamed FDT [3], or they aren't fully supported yet by OBSD, or it is > impossible to source them anymore, or the bootloader is some vendored fork, > which a burden to update, etc. > > I was looking at Crystal Kolipe's article-series [4] regarding the PinePhone, > but the screen is not yet usable AFAIK... > > Could you point out a hardware for this kind of use-case? I would liek to > have something smaller than a regular-Pi SBC. > > Thank You very much! > > [1] https://github.com/RetroBSD/retrobsd/ > [2] https://github.com/chettrick/discobsd/ > [3] https://www.geniatech.com/product/xpi-3566-zero/ > [4] https://research.exoticsilicon.com/series/pinephone_openbsd/part_1/ > > --Z-- >
Re: No internet even wifi is active
Greetings, You may want to provide your dmesg output as well, but I suspect your WiFi device might need firmware (assuming it's supported), so it's recommended you connect via Ethernet somehow, run "fw_update" as root, and then try again. -Claudio On Tue, Mar 12, 2024 at 12:32 PM Hari wrote: > > There is no internet connection with mobile hotspot even though ifconfig > shows that eifi is active. There is in destination or gateway in netstate > -rn. I suspect sonething is wrong with dhcp but I can't think of any > solution. Please look into this issue. > Thanks
Re: Automatic OS updates
I personally have this running on a desktop PC running OpenBSD 7.4-current since a few releases back. While it's been convenient, it has bitten me in the butt when something broke, since we are talking about -current. I wouldn't recommend this on anything you need in a functional state, but then you wouldn't be running -current unless you are aware of the risks. ;-) On Thu, Feb 15, 2024 at 1:16 PM wrote: > > So I was curious, am I the only one using automatic OS updates > in cron to keep the fish fresh and the bits dust free? > > I think I read somewhere that it's not recommended but I'm not > running a server so it seems like a good idea to me. > > /etc/crontab: > > # Example of job definition: > # . minute (0 - 59) > # | .- hour (0 - 23) > # | | .-- day of month (1 - 31) > # | | | .--- month (1 - 12) OR jan,feb,mar,apr ... > # | | | | . day of week (0 - 6) (Sunday=0 or 7) OR > sun,mon,tue,wed,thu,fri,sat > # | | | | | > # * * * * * user-name command to be executed > 0 3 * * * root sysupgrade > 30 3 * * * root pkg_add -u >
Re: X11 Configuration for AMD RX 6600
On Mon, Jan 22, 2024 at 9:23 AM wrote: > > Hi, I'm trying to get my RX 6600 to work under OpenBSD, and am failing > miserably. > No matter what I put into /etc/X11/xorg.conf, it always says "no devices > found" and "no screens found" > I don't see any GPU-related errors in dmesg, so am I just doing it wrong? > I've tried creating a Device, Screen, Monitor SubSection but nothing seemed > to work. > How am I supposed to do this? I usually use Xorg -configure, but it seems > that's not available on OpenBSD 7.4. > The only driver that seems to work is "modesetting", but I'd like to use > "amdgpu". > I have ran fw_update and it says that everything is already installed. > There's one strange line in my dmesg, but I'm not sure if it's important: > "drm:pid0:smu_v11_0_check_fw_version *WARNING* SMU driver if version not > matched" > I can upload my full dmesg if necessary, but I'd like to just know if I'm > even doing the Xorg configuration right. > Greetings, Have you tried running X11 without an xorg.conf? I've been running older AMD GPUs and haven't had to create a conf file for Xenocara (OpenBSD's Xorg) in a long time unless I need to specify a particular configuration command. Otherwise, it just works and the correct driver *should* be used. Regards, Claudio
Re: Firefox problem
On Wed, Dec 13, 2023 at 9:37 AM Gabriel Brito wrote: > > I have the same issue on 7.4 GENERIC.MP#1485 amd64. > > CCing ports and maintainer. > > On Wed, 13 Dec 2023 at 12:31, wrote: > > > Running OpenBSD -current. Trying to run Firefox results in: > > > > /home/oscar $ firefox > > XPCOMGlueLoad error for file /usr/local/lib/firefox/libmozwayland.so.132.0: > > File not found > > Couldn't load XPCOM. > > > > Any suggestions would be appreciated. > > > > There's already a thread on the issue. https://marc.info/?l=openbsd-ports=17022810948=2 Regards, - Claudio Miranda
Re: OpenBSD 7.4 released -- Oct 16, 2023
Congratulations to Theo and everyone involved in making OpenBSD 7.4 a reality and for this awesome project altogether! I also love the artwork (big thanks also to the artist that created it). so I'll be getting some 7.4 merch soon! Claudio Miranda On Mon, Oct 16, 2023 at 9:37 AM pela0 wrote: > > Upgrading... > > ;) > > > > > --- Original Message --- > On Monday, October 16th, 2023 at 09:53, Theo de Raadt > wrote: > > > > > > > > > > > > - OpenBSD 7.4 RELEASED - > > > > October 16, 2023. > > > > We are pleased to announce the official release of OpenBSD 7.4. > > This is our 55th release. We remain proud of OpenBSD's record of more > > than twenty years with only two remote holes in the default install. > > > > As in our previous releases, 7.4 provides significant improvements, > > including new features, in nearly all areas of the system: > > > > - Various kernel improvements: > > o On arm64, show BTI and SBSS features in dmesg(8). > > o New kqueue1(2) system call supporting the O_CLOEXEC flag. > > o Map device tree read/write to unbreak root on softraid(4). > > o Correctly recognize umass(4) floppy disk devices as floppy disks. > > o In wscons(4), catch up with box drawing characters which have been > > standardized in unicode after the original wscons code was written > > and chose placeholder values. > > o In wscons(4), make sure we do not increase the escape sequence > > argument count beyond usable bounds. > > o Implement dt(4) utrace(2) support on amd64 and i386. > > o Correct undefined behavior when using MS-DOS filesystems, fixes > > imported from FreeBSD. > > o Make the softdep mount(8) option a no-op. Softdep was a > > significant impediment to improving the vfs layer. > > o Allow unveil(2)ed programs to dump core(5) into the current > > working directory. > > o Address incomplete validation of ELF program headers in execve(2). > > o On arm64, use the deep idle state available on Apple M1/M2 cores > > in the idle loop and for suspend, resulting in power savings. > > o Update AMD CPU microcode if a newer patch is available. > > o Enable a workaround for the 'Zenbleed' AMD CPU bug. > > o Report speculation control bits in dmesg(8) CPU lines. > > o To give the primary CPU an opportunity to perform clock interrupt > > preparation in a machine-independent manner we need to separate > > the "initialization" parts of cpu_initclocks() from the "start the > > clock interrupt" parts. Separate cpu_initclocks() from > > cpu_startclock(). > > o Fix a problem where CPU time accounting and RLIMIT_CPU was > > unreliable on idle systems. > > o Improve the output of the "show proc" command of the kernel > > debugger ddb(4) and show both the PID and TID of the proc. > > > > - SMP Improvements > > o Rewrite pfsync(4), in particular to improve locking and to help > > with unlocking more of pf(4) and with parallelisation of the > > network stack in the future. The protocol remains compatible with > > the older version. > > o Remove kernel locks from the ARP input path. > > o Pull MP-safe arprequest() out of kernel lock. > > o Remove the kernel lock from IPv6 neighbor discovery. > > o Unlock more parts of ioctl(2) and the routing code in the network > > stack. > > > > - Direct Rendering Manager and graphics drivers > > o Update drm(4) to Linux 6.1.55. > > o Don't change end marker in sg_set_page(). Caused bad memory > > accesses when using page flipping on Alder Lake and Raptor Lake. > > > > - VMM/VMD improvements > > o Allowed vmm(4) guests to enable and use supervisor IBT. > > o Suppressed AMD hardware p-state visibility to vmm(4) guests. > > o Avoid use of uninitialised memory in vmd(8). > > o Migrate vmd_vm.vm_ttyname to char array allowing a vmd_vm object > > to be transmitted over an ipc channel. > > o Cleaned up file descriptor closing in vmd(8) vmm process. > > o Fixed vm send/receive, restoring device virtqueue addresses on > > receive. > > o Introduced execvp(3) after fork for child vm processes. > > o No longer generate an error in vmd(8) if vm.conf(5) is absent. > > o Split vmm(4) into MI/MD parts. > > o Introduced multi-process model for vmd(8) virtio block and network > > devices. > > o Allowed vm owners to override boot kernel when using vmctl(8) to > > start a vm. > > o Changed staggered start of vms to number of online CP
Re: MNT Pocket Reform - OpenBSD support "in development"
Same here! I just saw this today and it really piqued my interest. I have an old Asus Eee PC 901 netbook that's running OpenBSD/i386 quite well with the SSD mod I've added to it, but it's obviously showing its age at this point. I recently received my PinePhone keyboard to replace the Eee 901 with my PinePhone, but of course that won't run OpenBSD. Something like this with OpenBSD would be a dream come true for me if it lives up to its goals. -- Claudio On Tue, Jun 28, 2022 at 1:57 PM wrote: > > https://mntre.com/media/reform_md/2022-06-20-introducing-mnt-pocket-reform.html > > Looks like a fun little machine, and they claim OpenBSD support is "in > development." I'm curious, have they contributed any code or resources > to make OpenBSD run on this device? I'd be more inclined to buy one if > they are actually contributing to the project. > > Thanks, > > -- > Joe Gidi > j...@entropicblur.com > > "You cannot buy skill." -- Ross Seyfried >
