Re: Favorite configuration and system replication tools?
On 5/7/24 1:09 PM, Страхиња Радић wrote:
Дана 24/05/07 04:08PM, Martin Kjær Jørgensen написа:
I was wondering which programs you use for
replicating/copying/syncing environments/configs on your openbsd
systems with between your desktops (home or work) and laptops?
git(1), rsync(1).
git push and git pull.
I keep important dotfiles (.profile etc) in an own rep, and in there
somewhere is a list of packages I want on {all,desktop,server}-type
machines. In my scripts repo is a script that installs them based on an
arg to say which kind of system it is. So:
new machine?
pkg_add git
git pull various repos
make -C dotfiles install
run "mystdpkgs" with -d for desktop, -s for server
Done!
(I think I have another script that runs all these).
Re: Howto do "a detailed cleanup with the aid of the sysclean package"?
On Wed, Apr 20, 2022 at 08:39:09PM +0200, Harald Dunkel wrote: > Hi folks, > > the upgrade guide claims > > A detailed cleanup can be done with the aid of the sysclean package. > > sysclean lists 4180 files and directories on my home server, including mail > directories, config files of various external packages, generated files, .git > directories, etc. A lot of stuff I wouldn't like to lose. Apparently it also > lists a lot of old crap, but since it lists *so many* important files I don't > trust it at all. > > Could you please elaborate how sysclean is going to help me to keep my openbsd > hosts clean? How is the usage model of this tool? Like any base tool, start with its man page: man sysclean Add any directories you want to keep into /etc/sysclean.ignore (start with the sample provided to ensure you keep the include at the end).
Re: How to track system changes?
On Mon, Apr 04, 2022 at 08:32:01AM -0700, Eric Thomas wrote: > I want to have a high degree of confidence in my system's state > (packages that have been added, configs that have changed, permissions > changed, etc). I've read about "read only filesystems" and the > pro's/con's [here](http://geodsoft.com/howto/harden/OpenBSD/no_changes.htm). > > Aside from that, is there a way to... > > 1. ...hash the file system in some way and monitor for changes? OR > 2. ...somehow review changes that have taken place (a log somewhere)? > > The goal is to concretely know whether the state of the system has > changed, then point to what EXACTLY has changed. > > Anyone doing something similar? Yes, in fact, *everyone* else is. /etc/changelist lists files that are monitored. You will get an email if they change, e.g., if a program surprisingly becomes setuid. I imagine that this is documented someplace.
Re: Please put vi in base
> Could we please get vi into base? Even the most basic version would do. um, vi has been in base for years. It has not been in the install media, which are chronically short out of room. I would not advise you to hold your breath for vi to appear there in the next week or so. It doesn't take that long to learn ed from the "bottom line" of vi, and the man pages are online if you have another computer (or even a phone) with internet access. Learn it in the good times, for use in the bad.
Re: Install latest package without prompts on OpenBSD 7.0
On Mon, Jan 10, 2022 at 06:28:38PM -0300, Crystal Kolipe wrote: > On Mon, Jan 10, 2022 at 07:15:25PM +0100, Andreas Kusalananda Khri wrote: > > Which one is the "latest" here? > > > > $ doas pkg_add bogofilter > > doas (kk@box) password: > > quirks-4.92 signed on 2022-01-07T13:45:06Z > > Ambiguous: choose package for bogofilter > > a 0: > > 1: bogofilter-1.2.5 > > 2: bogofilter-1.2.5-db4 > > 3: bogofilter-1.2.5-lmdb > > 4: bogofilter-1.2.5-qdbm > > 5: bogofilter-1.2.5-sqlite3 > > Your choice: > > None of them is the 'latest', those are just different 'flavors' of the port. Agreed. The discussion was about different numbered versions, but has been hijacked to be about flavors. If a "simple automated scripted" pkg_add were desired, it would take choice #1 in this case or any where there are flavors AND where no flavor was specified.
Re: Install latest package without prompts on OpenBSD 7.0
> > > I am working on OpenBSD 7.0, x86_64. I'm trying to script an install > > > of developer tools I use, like GCC and Git. When I attempt to install > > > GCC I am prompted: > > > > > > $ sudo pkg_add gcc g++ > > > quirks-4.54 signed on 2022-01-09T19:08:35Z > > > Ambiguous: choose package for gcc > > > a0: > > > 1: gcc-8.4.0p9 > > > 2: gcc-11.2.0p0 > > > > > > I've looked over the man page at https://man.openbsd.org/pkg_add, but > > > I don't see an option to tell pkg_add to install the latest version of > > > the package. > > > > Sure there is. > > > > Quoting the manpage: > > There is also an ambiguity related to ports with multiple branches. For > > instance ‘pkg_add python’ is ambiguous, as there are several versions of > > python in the ports tree. So is ‘pkg_add postfix’. The special form > > ‘pkgname%branch’ can be used to restrict matches to a branch matching > > the > > pkgpath(7). > > > > pkg_add gcc%11 g++%11 > > will do the trick In the context of the original post, I think he meant a way to invoke "pkg_add" and have it just install whatever the latest is, without having to know a priori that there is a version 11. "Just install gcc, dammit". There are many ports that have version choices and in the context of installing the latest of everything in a "scripted install", having to either stop mid-install and answer such a prompt, or sort out in advance what ports exist in multiple versions, is not what's wanted. It may be unwise, but it's what some people that do scripted installs want. I have wished for this too, but it never bothered me enough to send a query. :-)
Re: how to recover a corrupted disk
On Wed, Dec 01, 2021 at 01:39:39PM +0530, Sandeep Gupta wrote: > Hello, > All partitions except for /dev/rsd1c and /dev/rsd1i are clean. > For /dev/rsd1c , I get "BAD SUPER BLOCK: MAGIC NUMBER WRONG". > For /dev/rsd1i, I get "UNEXPECTED INCONSISTENCY". If that's the case, you are probably done! You could mount your 'a' partition manually on /mnt, look in /mnt/etc/fstab, and see which letter partitions belong where; use that info to make sure you have "found" all your partitions. BTW, in addition to scan_ffs in base, there is testdisk in ports, which I think does a better job ATM of finding FFS2 filesystems. As mentioned, DO NOT do anything with 'c' partition (be glad, be very glad, that it didn't find anything resembling a superblock when fsck'ing 'c'!). It's not a mountable partition but a 'wrapper' for the whole disk.
Re: nvme boot
On Fri, Oct 15, 2021 at 05:05:01PM +0200, Jan Stary wrote: > Does any of the OpenSBD-supported platforms boot off nvme storage? > So far, I have been able to use nvme storage as a disk, > but not boot from it; but my HW is far from recent. The Framework laptop (https://frame.work) boots fine off an internal NVME, so I suspect other modern laptops do too. Also the SiFive HiFive boots off NVME. So, yes.
Re: Are there any protection againts heisting the "shell builtin"s?
On Wed, Sep 08, 2021 at 11:24:18AM +0200, jim hook wrote:
> test$ cd
> rmplayer
> test$
> test$ type cd
> cd is a function
> test$
> test$ tail -4 .profile
> cd()
> {
> echo rmplayer
> }
> test$
> test$ uname -mrs
> OpenBSD 6.9 amd64
> test$
>
> Thinking of that home dirs could be on a shared storage, that can be accessed
> by others and maliciously modify the ".profile", etc. files of the targeted
> user.
>
> ex.: "unset cd" would help, but any solution in general?
If your $HOME is on a shared drive that can be written by others, then
blocking people from redefining shell builtins would be like throwing
deck chairs off the Titanic, i.e., you have no security whatsoever.
The only general solution is to have your home directory under better control.
Re: chroot x11 via Xephyr
On Mon, May 03, 2021 at 08:51:51PM +, Karsten Pedersen wrote: > It is worth noting that you can move (not copy) UNIX sockets (again, > so long as they are on the same filesystem). > > So, once Xephyr has started up, you can move the socket from > "/tmp/.X11-unix/X1" into "$CHROOT/tmp/.X11-unix/X1" and then your > chroot application can access it. Assuming root permissions, the above will "succeed" even if $CHROOT is not on the same filesystem as /tmp. Then fail to connect at runtime. Using ln (not ln -s) instead of mv will fail faster if the same-filesystem requirement is not met.
Re: 6.9 Current amd64 xfce seems to freeze and not respond to mouse clicks or keystrokes
On Sat, Apr 10, 2021 at 10:22:17PM +0100, Tom Smyth wrote: > Hello, > > 1) issue does not occur with fvwm or with chrome running in fvwm > > so the issue seems to be confined to xfce, and I was running just 1 > xfce terminal session > 2) (so the issue is not related to chromium) > > > > I'm running OpenBSD on an Oracle Virtualbox VM I run xfce all the time on -current on amd64 on real hardware and do not have any such issue.
Re: vmm/vmd disk issue
On Tue, Mar 09, 2021 at 09:52:03AM +0100, Jan Johansson wrote: > If I try to cp or dd the disk image on the host it fails > > dd if=disk.raw.old of=disk.raw.bak bs=1m > dd: disk.raw.old: Input/output error > 8858+0 records in > 8858+0 records out > 9288286208 bytes transferred in 102.048 secs (91018010 bytes/sec) > > The host show no other signs of failing hardware. > > Is this a software or a hardware error? Given that it gives an error outside the VM, it's likely hardware. > Is there some way to recover the guest disk image without a > complete reinstall? Depending on where the error is, you might get away with dd'ing with conv=noerror,sync, changing vm.conf to point to the new copy, and run fsck in the vm. And buy a new hard disk or SDD. Probably cheaper than your time to further diagnose it?
Re: Installation overwritten... Accidental disklabel and newfs
> The device nodes don't exist until the install or upgrade program detects > the disk and creates them. > > Likewise for wd0 as although outdated for ahci disks. > > Dmesg identifies the disk as: > sd0 at scsibus0 targ0 lun0 ATA ST1000DM003... > sd0 953869mb > > This is why I had to run the install program and accidentally went too far. > > It would be helpful to be able to use disklabel and other tools such as > newfs, growfs without running through the installer. When booted into the installer, just do CTRL/C to kill the install script Then do: cd /dev; sh MAKEDEV sd0 wd0 sd1 # or whatever devices you need Porblem solved: you can now do "disklabel and other tools" without risk of destroying your filesystesms. At least, not having the installer do it. With these tools most people are quite capable of destroying filesystems.
Re: adding user to a group
On Fri, Jan 08, 2021 at 05:20:36PM +0100, Rudolf Sykora wrote: > > Todd C. Miller writes: > > > You need to login in again. Logging in via ssh, a virtual console, > > X11 or running su will set the groups list. Setting groups is a > > privileged operation so simply starting a new shell or opening a > > new xterm is not sufficient. > > Thanks, su helped. > (Although I do not understand the reasoning behind the need to log > out/in, i.e., why isn't the group membership just updated after the > usermod command...) Todd's message contains the explanation. If you did not understand it, please do some homework, like, read up on and understand how processes work on Unix.
Re: i386 "panic: pci_make_tag: bad request" after acpi sleep states
On Tue, Dec 29, 2020 at 09:42:59AM -0500, Bryan Steele wrote:
> On Mon, Dec 28, 2020 at 01:20:29PM -0500, Ian Darwin wrote:
> > Kernel is OpenBSD 6.8-current (GENERIC) #561: Sun Dec 27 18:29:43 MST 2020
> >
> > Machine is a Wyse C90 - orignially sold as a "thin client" - tiny machine,
> > no serial port (ps and trace typed in).
> > HW Info at https://www.parkytowers.me.uk/thin/wyse/cx0/
> > Was planning to use it as a wifi bridge, so tiny is fine.
> >
> > "Latest" BIOS (2012 edition). "BIOS reset" did not help.
> > cpu info: VIA Eden Processor 1000MHz ("CentaurHauls" 686-class) 1.01 GHz,
> > 06-0d-00
> > RAM: 1GB (despite reported as 3/4 of that)
>
> Long shot, but could you maybe show the output of "machine memory" for
> both boot/pxeboot? I'm curious if the memory map is reportedly
> differently between a working boot and a bad one.
Good suggestion, and indeed, it differs a little:
Using pxeboot:
CLIENT MAC ADDR: 00 80 64 xx xx xx GUID: C2020018-0403-0920-EE9A-0080648793AD
CLIENT IP: 192.168.42.245 MASK: 255.255.255.0 DHCP IP: 192.168.42.254
GATEWAY IP: 192.168.42.254
probing: pc0 pci pxe![2.1] mem[546K 765M a20-on]
disk: hd0+
net: nac 00:80:64:xx:xx:xx, ip 192.168.42.245, server 192.168.42.254
>> OpenBSD, i386 PXEBOOT 3.43 boot> machine mem
Region 0: type 1 at 0x0 for 546KB
Region 1: type 2 at 0x88800 for 94KB
Region 2: type 2 at Oxe for 128KB
Region 3: type 1 at 0x10 for 784192KB
Region 4: type 3 at Ox2fed for 28KB
Region 5: type 4 at 0x2fed7000 for 4KB
Region 6: type 2 at Ox2fed8000 for 160KB
Region 7: type 2 at Ox2ff0 for 1024KB
Region 8: type 2 at Ox3000 for 262144KB
Region 9: type 2 at Oxe000 for 262144KB
Region 10: type 2 at Oxfec0 for 64KB
Region 11: type 2 at Oxfee0 for 4KB
Region 12: type 2 at Oxfff0 for 1024KB
Low ram: 546KB High ram: 784192KB Total free nemory: 784738KB
boot>
Using /boot:
>> OpenBSD/i386 BOOT 3.44
boot> machine mem
Region 0: Type 1 at 0x0x for 631KB
Region 1: Type 2 at 0x9dc99 for 9KB
Region 2: type 2 at 0xe for 128kb
(remainder the same)
Could Region 1 being so microscopic cause problems? If it got used for anything?
Thx for looking.
> > Full dmesg below; full ACPI attached.
> >
> > Boot used Kernel FromResult
> > pxeboot bsd.rd tftpOK
> > pxeboot bsd hd0aOK (via
> > tftpboot/etc/conf)
> > bootbsd hd0apanic
> >
> > I.e., Boots fine with pxeboot "set device hd0a", but booting exact same
> > kernel off same disk via /boot causes panic.
> >
> > It's an older machine so it's likely a buggy acpi, not worth massive
> > investment of time, just wonder if there's an easy workaround.
> > Presume it's getting something different in some AML, based on where boot
> > code loaded from,
> > or else pxeboot vs boot setting environment slightly differently?
> >
> > On screen after panic:
> >
> > bios0: WYSE C CLASS
> > acpi0 at bios0: ACPI 3.0
> > acpi0: sleep states S0 S1 S3 s4 S5panic: pci_make_tag: bad request
> > Stopped at db_enter+0x4: popl %eb
> >
> > trace:
> >
> > db_enter(d0e5e189,d10f6704,2,0,0) at db_enter+0x4
> > panic(d0c3d47d,1,d10f6750,d0854f11,0) at panic+0xd3
> > pci_make_tag(0,0,11,0) at pci_make_tag+0x95
> > acpi_gasio(d2b1b400,0,2,6e,11,1,1,d10f67d8) at acpi_gasio+0x1f1
> > aml_opreg_pcicfg_handler(0,0,6e,11,1,d10f67d8) at
> > aml_opreg_pcicfg_handler+0x21
> > aml_rwgen(d2b338c4,373,1,d2b3f304,0,1) at aml_rwgen+0x571
> > aml_rwfield(d2b2bc04,0,1,d2b3f304,0) at aml_rwfield+0x37a
> > aml_eval(d2b40704,d2b2bc04,74,d10f692c,0) at aml_eval+0x17a
> > aml_parse(d2b40704,74,d2b2f804) at aml_parse+0x2b15
> > aml_parse(d2b40704,69,38) at aml_parse+0x351
> > aml_parse(d2b40704,54,9,d2b36518,d2b40704) at aml_parse+0x351
> > aml_eval(0,d2b36544,74,0,0) at aml_eval+0x277
> > aml_evalnode(d10f6b10,d2b36504,0,0,d10f6ac0) at aml_evalnode+0xae
> > aml_evalinteger(d1b1b400,d2b36a84,d0c17e38,0,0,d10f6b30) at
> > aml_evalinteger+0xae
> > acpi_foundprw(d2b36d04,d2b1b400) at acpi_foundprw+0x2f
> > aml_find_node(d2b36a84,d0b9299b,d0859b90,d2b1b400) at aml_find node+0x?2
> > aml_find_node(d2b336c4,d0b9299b,d0859b90,d2b1b400) at aml_find node+0x9b
> > aml_find_node(d2b296c4,d0b9299b,d0859b90,d2b1b400) at aml_find node+0x9b
> > aml_find_node(d2b31484,d0b9299b,d0859b90,d2b1b400) at aml_find node+0x9b
> > aml_find_node(d0eba1a8,d0b9299b,d0859b90,d2b1b400) at aml_find_node+0x9b
> > acpi_init_gpes (d2b1b400) at acpi_init_gpes+0x195
> > acpi_attach_common(d
i386 "panic: pci_make_tag: bad request" after acpi sleep states
Kernel is OpenBSD 6.8-current (GENERIC) #561: Sun Dec 27 18:29:43 MST 2020
Machine is a Wyse C90 - orignially sold as a "thin client" - tiny machine, no
serial port (ps and trace typed in).
HW Info at https://www.parkytowers.me.uk/thin/wyse/cx0/
Was planning to use it as a wifi bridge, so tiny is fine.
"Latest" BIOS (2012 edition). "BIOS reset" did not help.
cpu info: VIA Eden Processor 1000MHz ("CentaurHauls" 686-class) 1.01 GHz,
06-0d-00
RAM: 1GB (despite reported as 3/4 of that)
Full dmesg below; full ACPI attached.
Boot used Kernel FromResult
pxeboot bsd.rd tftpOK
pxeboot bsd hd0aOK (via tftpboot/etc/conf)
bootbsd hd0apanic
I.e., Boots fine with pxeboot "set device hd0a", but booting exact same kernel
off same disk via /boot causes panic.
It's an older machine so it's likely a buggy acpi, not worth massive investment
of time, just wonder if there's an easy workaround.
Presume it's getting something different in some AML, based on where boot code
loaded from,
or else pxeboot vs boot setting environment slightly differently?
On screen after panic:
bios0: WYSE C CLASS
acpi0 at bios0: ACPI 3.0
acpi0: sleep states S0 S1 S3 s4 S5panic: pci_make_tag: bad request
Stopped at db_enter+0x4: popl %eb
trace:
db_enter(d0e5e189,d10f6704,2,0,0) at db_enter+0x4
panic(d0c3d47d,1,d10f6750,d0854f11,0) at panic+0xd3
pci_make_tag(0,0,11,0) at pci_make_tag+0x95
acpi_gasio(d2b1b400,0,2,6e,11,1,1,d10f67d8) at acpi_gasio+0x1f1
aml_opreg_pcicfg_handler(0,0,6e,11,1,d10f67d8) at aml_opreg_pcicfg_handler+0x21
aml_rwgen(d2b338c4,373,1,d2b3f304,0,1) at aml_rwgen+0x571
aml_rwfield(d2b2bc04,0,1,d2b3f304,0) at aml_rwfield+0x37a
aml_eval(d2b40704,d2b2bc04,74,d10f692c,0) at aml_eval+0x17a
aml_parse(d2b40704,74,d2b2f804) at aml_parse+0x2b15
aml_parse(d2b40704,69,38) at aml_parse+0x351
aml_parse(d2b40704,54,9,d2b36518,d2b40704) at aml_parse+0x351
aml_eval(0,d2b36544,74,0,0) at aml_eval+0x277
aml_evalnode(d10f6b10,d2b36504,0,0,d10f6ac0) at aml_evalnode+0xae
aml_evalinteger(d1b1b400,d2b36a84,d0c17e38,0,0,d10f6b30) at aml_evalinteger+0xae
acpi_foundprw(d2b36d04,d2b1b400) at acpi_foundprw+0x2f
aml_find_node(d2b36a84,d0b9299b,d0859b90,d2b1b400) at aml_find node+0x?2
aml_find_node(d2b336c4,d0b9299b,d0859b90,d2b1b400) at aml_find node+0x9b
aml_find_node(d2b296c4,d0b9299b,d0859b90,d2b1b400) at aml_find node+0x9b
aml_find_node(d2b31484,d0b9299b,d0859b90,d2b1b400) at aml_find node+0x9b
aml_find_node(d0eba1a8,d0b9299b,d0859b90,d2b1b400) at aml_find_node+0x9b
acpi_init_gpes (d2b1b400) at acpi_init_gpes+0x195
acpi_attach_common(d2b1b400,f67a0) at acpi_attach_common+0x355
acpi_attach(d2b210c0,d2b1b400,d10f6db8) at acpi_attach+0xZc
config attach(d2b210c0,d0df60d4,d10f6db8,d0928b30) at config attach+0x18a
config_found_sm(d2b210c0,d10f6db8,d0928630,0) at config_found_sm+0x29
biosattach(d2b21080, d2b210c0,d10f6eb8) at biosattach+0x19a
config attach (d2b21080, d0df 4c94,d10f6eb8, d02431f0) at config_attach+0x18a
config_found_sm(dZbZ1080, d10f beb8, d02431f0,0) at config_found_sm+0x29
mainbus_attach(0,d2b21080,0) at mainbus attach_0x5c
config_attach(0,d0df 2614,0,0) at config_attach+0x18a
cpu_configure(lie340b7,10f 4000, 1103000, 10 7000,0) at cpu_configure+0x24
main(0,0,0,0,0) at main+0x311
ddb>
ps:
TID PID UID PRFLAGS PFLAGS CPU COMMAND
*0 00 0x1 0x200 0 swapper
Dmesg:
ssh wyse cat /var/run/dmesg.boot
OpenBSD 6.8-current (GENERIC) #561: Sun Dec 27 18:29:43 MST 2020
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
real mem = 803459072 (766MB)
avail mem = 772513792 (736MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 01/16/12, BIOS32 rev. 0 @ 0xfdd30, SMBIOS rev. 2.6 @
0x2fed8000 (48 entries)
bios0: vendor Phoenix Technologies version "1.0G" date 01/16/2012
bios0: WYSE C CLASS
acpi0 at bios0: ACPI 3.0
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP SSDT APIC MCFG HPET
acpi0: wakeup devices PWRB(S4) PCI0(S5) PS2M(S3) PS2K(S3) USB1(S4) USB2(S4)
USB3(S4) USB4(S4) USB5(S4) HDAC(S5) SP2P(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: VIA Eden Processor 1000MHz ("CentaurHauls" 686-class) 1.01 GHz, 06-0d-00
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE,SSE3,EST,TM2,xTPR,NXE
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: RNG AES AES-CTR SHA1 SHA256 RSA
cpu0: apic clock running at 100MHz
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 3, 24 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-0
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (SP2P)
acpibtn0 at acpi0: PWRB
"PNP0A03" at acpi0 not configured
acpicmos0 at acpi0
acpicpu0 at acpi0: !C3(@800 io@0x4015), !C2(@80
Re: Programmed wakeup from suspend/hibernate
On Thu, Dec 24, 2020 at 11:51:26AM +0100, Gabriel Hondet wrote: > Hi, > > How can I program my computer to automatically wake from suspend to ram > or suspend to disk at a certain time? > > My goal is to suspend a server every day from, say, 11 pm to 7am. For suspending at night, use see the cron man page. For waking up in the morning, of course, the OS isn't running so there is nothing it can do. Some but not all PC BIOSes have a scheduling feature. Otherwise a $10 mechanical timer to cut the power (well after the suspend is finished!) and turn it back on in the morning.
Wyse C90 (i386) early panic 'pci_make_tag bad request' after "acpi0: sleep states"
When trying to boot -current i386 from a clean install on the internal flash drive, this thing panics on the same line as the 'acpi sleep states' after 'S5'. As a workaround, I can load pxeboot with a boot.conf to boot bsd. My guess would be that pxeboot passes control to the kernel with some trivial and other"wyse" irrelevant bit or bits different. I made no changes in BIOS between the working and non-working boots, just unplugged the network cable. No serial cable, but pictures, full dmesg from booted with pxeboot, and acpidump, all stored at https://darwinsys.com/tmp/wyse. TIA for any help.
Re: sysupgrade with latest snapshot: The directory '/home/_sysupgrade/' does not exist.
On Sun, Sep 27, 2020 at 08:14:13PM +0200, Why 42? The lists account. wrote: > > I am running: > kern.version=OpenBSD 6.8-beta (GENERIC.MP) #69: Tue Sep 15 12:34:41 MDT 2020 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > I just tried to use sysupgrade and I notice that its behaviour has > changed a bit since my last upgrade. Previously (last six months or so) > after the download of the new sets and the reboot, I would have been > prompted as to what to do i.e. Install, Upgrade, or Shell. Then for a > keyboard layout (e.g. de) and for the name of the disk containing OpenBSD > (i.e. the system root partition) or "/"). Something is wwrong here. That is not how sysupgrade works. Probably you didn't install updated boot blocks and it has been failing to "switch to bsd.upgrade" when rebooting after the download, and your latest change installed the updated boot blocks, and now it is working. > 1. Now on the console I see (post reboot): Here you describe how sysupgrade normally works. > 2. The upgrade then proceeds, however it fails to identify the location > of the newly downloaded sets. The error is: > "The directory '/home/_sysupgrade/' does not exist." > > 3. It then seems to abort the upgrade and reboot the system. Thus > leaving me back where I started. I've never tried using a symlink to /home. Can you mount /home properly and see if that works?
Re: home printer
On Thu, Sep 17, 2020 at 03:07:19PM -0700, Sean Kamath wrote: > > > > On Sep 17, 2020, at 09:48, Ingo Schwarze wrote: > > That answer [HP] used to be spot on until about the year 2000. > > I concur. I used to work at a printer company that competed directly with > them. Was that Imagen, by any chance? Anyway, I concur too. I have a mid-1990's HP6MP with 75,000 pages on its ticker (would be more but it was in storage for several years) and it still prints beautifully. The manual for it proudly talks about their BBS and how to set your comm sofware to 8-N-1; their internet site (FTP only) is mentioned (by IP address) almost as an afterthought.
Re: Can I boot without GPU ("headless")?
On Sat, Aug 29, 2020 at 03:56:29PM +, Henry W. Peterson wrote: > It is not a problem for me to write commands on the boot prompt after every > turning on, that would eliminate the need to modify /etc/boot.conf, right? > Althogh I didn't know modifying that file affected the boot prompt itself. > Noted. > > I do have another computer, the one I planned to use to connect by ssh, but I > do not have COM port cards (only pins on the motherboard) nor the cables. > > It starts to feel pretty clear that I should try the following: > > After correctly typing the decryption password, type: > set tty com0 > stty com0 9600 > boot -c > disable vga > quit > > Would this be enough to boot, to then connect by ssh (without modifying > /etc/ttys or having even a COM port card connected to the motherboard's pins)? It should get you booted. In fact, it would probably work without the boot -c/disable vga/quit parts. Setting the baud rate to 115200 might save a few seconds, too. But then, if you have FDE, the mount will hang, as there's no way to enter the password, without a serial cable. "set tty com0" will tell init to read from the serial, not the physical keyboard When you say "pins", is that a double row of pins sticking up? There are somewhat standard cables you can buy that will plug into that and terminate in a DB9 male socket. On the other computer, you can buy a USB-to-serial adapter/cable that will plug into the DB9 socket. This is what I use, for example.
Re: Can I boot without GPU ("headless")?
On Sat, Aug 29, 2020 at 01:37:35PM +, Henry W. Peterson wrote: > But then I would need to have every computer's serial port connected > the whole time, right? As far as I know serial ports are not > hot-swappable. Nope. I have two APUs and only one is ever connected, since I have only one USB-to-serial. I move it back and forth as needed (which isn't very often).
Re: Microsoft's war on plain text email in open source
On Wed, Aug 26, 2020 at 02:37:24AM -0700, Greg Thomas wrote: > "... he had to set up an entirely new mail client which didn’t mangle his > email message to HTML-ise... That’s a barrier to entry that’s pretty > high..." > > Wow. Life's rough. Surely easier than RTFMing to find out how to send plain-text email in the existing client. > On Wed, Aug 26, 2020 at 2:31 AM Frank Beuth wrote: > > > "Linux kernel development which is driven by plain-text email > > discussion needs better or alternative collaborative tooling "to bring > > in new contributors and maintain and sustain Linux in the future," says > > Sarah Novotny, Microsoft's representative on the Linux Foundation board. > > > > Said tooling could be "a text-based, email-based patch system that can > > then also be represented in a way that developers who have grown up in > > the last five or ten years are more familiar with," she added. > > > > ... > > > > Should it migrate toward something more like, say, issues and pull > > requests on the Microsoft-owned GitHub? “I’m not saying that there will > > be a move in any time that I can see my crystal ball’s broken but I do > > think there needs to be expansions in the way people can enter that > > workflow,” said Novotny. > > > > “It is a fairly specific workflow that is a challenge for some newer > > developers to engage with. As an example, my partner submitted a patch > > to OpenBSD a few weeks ago, and he had to set up an entirely new mail > > client which didn’t mangle his email message to HTML-ise or do other > > things to it, so he could even make that one patch. That’s a barrier to > > entry that’s pretty high for somebody who may want to be a first-time > > contributor.”" > > > > https://www.theregister.com/2020/08/25/linux_kernel_email/ > > > >
Re: nsd Will Not Start At Boot
On Mon, Jul 06, 2020 at 04:57:20AM +, ken.hendrick...@l3harris.com wrote: > I have tried putting "rcctl enable nsd" in the /etc/rc.conf.local file. > That did not help. I presume you meant "using rcctl enable nsd to update /etc/rc.conf.local", not actually what you wrote. > If I try to start nsd the same way the scripts do, I get nsd(failed). > $ /etc/rc.d/nsd start > nsd(failed) Try doing it by the book, i.e., rcctl start nsd If it fails silently, try rcctl -d start nsd
armv7 on Asus Chromebook C100P
Has anybody installed OpenBSD on these chromebooks? Asus sold a lot of them, and they are losing Google's support next month so there should be a lot available cheaply if you just want something to travel with for email/web/chat.
Re: Filling a 4TB Disk with Random Data
On Fri, Jun 05, 2020 at 12:49:41PM -0500, Ed Ahlsen-Girard wrote: > On Mon, 01 Jun 2020 13:38:55 -0400 > "Eric Furman" wrote: > > > On Mon, Jun 1, 2020, at 10:28 AM, Paul de Weerd wrote: > > [...] > > > > This is why if you are serious you use a degausser. > > > > The truly serious use a smelter. I am not making a joke. And, to reduce the impact of their being intercepted on the way to the smelter: https://prodevice.eu/media-destroyers-shredders/data-media-shredder/
Re: Article OpenBSD: Not Free Not Fuctional and Definetly Not Secure and BSD, the truth blog
On Thu, May 28, 2020 at 02:21:49PM +1000, Aaron Mason wrote: > On Thu, May 28, 2020 at 2:20 PM Quantum Robin > wrote: > > While surfing on the Google to learn more about OpenBSD, I encountered this > > one: "OpenBSD: Not Free Not Fuctional and Definetly Not Secure ( > > https://aboutthebsds.wordpress.com/2013/01/25/20/) > > > > Is the author telling the truth? Or just yet another anti-BSD thing? > > If it has to tell you it's "the truth" in its title, it probably isn't. If it can't spell "Functional", it probably isn't.
Re: More than 16 partitions
On Thu, Apr 23, 2020 at 04:42:53PM -0400, Allan Streib wrote: > > So, can I setup openBSD labels on x86_64 without legacy/GPT partition > > first ? > > IIRC yes you can, as long as you don't need to boot from that disk. Easily confirmed (a few false starts deleted from this transcript): $ uname -a OpenBSD foo.darwinsys.com 6.7 GENERIC.MP#145 amd64 # Here I plugged in a cheap USB device $ dmesg | tail -4 umass0: using SCSI over Bulk-Only scsibus4 at umass0: 2 targets, initiator 0 sd2 at scsibus4 targ 1 lun 0: removable serial.18a5023805270130 sd2: 3750MB, 512 bytes/sector, 768 sectors # Trash any existing fdisk and disklabel info # dd if=/dev/random of=/dev/rsd2c bs=512 count=100 100+0 records in 100+0 records out 51200 bytes transferred in 0.068 secs (742845 bytes/sec) # disklabel sd2 # /dev/rsd2c: type: SCSI disk: SCSI disk label: Store n Go Drive duid: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 478 total sectors: 768 boundstart: 0 boundend: 768 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] c: 7680 unused i: 7679944 56 MSDOS # fdisk sd2 # confirm there is no fdisk table, just random rubbish Disk: sd2 geometry: 478/255/63 [768 Sectors] Offset: 0 Signature: 0x111 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 82 77157 27 55 - 172421 98 24 [ 1239528960: 1530420603 ] Linux swap 1: 64 10096 3 23 - 176047 141 26 [ 162192451: 2666011513 ] NetWare 2.xx 2: 6E 252409 74 42 - 209458 117 56 [ 4054955288: 3604962205 ] 3: A9 19978 12 42 - 22375 228 62 [ 320947367:38521434 ] NetBSD # disklabel -E sd2 Label editor (enter '?' for help at any prompt) sd2> p OpenBSD area: 0-768; size: 768; free: 768 #size offset fstype [fsize bsize cpg] c: 7680 unused sd2> a partition: [a] offset: [0] 64 size: [7679936] 100M FS type: [4.2BSD] sd2*> w sd2> q No label changes. # newfs /dev/rsd2a /dev/rsd2a: 101.9MB in 208768 sectors of 512 bytes 4 cylinder groups of 25.48MB, 1631 blocks, 3328 inodes each super-block backups (for fsck -b #) at: 32, 52224, 104416, 156608, # mount /dev/sd2a /mnt $ ls /mnt $ date | doas dd of=/mnt/date.txt 0+1 records in 0+1 records out 29 bytes transferred in 0.000 secs (322584 bytes/sec) $ ls /mnt date.txt $ cat /mnt/date.txt Thu Apr 23 18:55:35 EDT 2020 # fdisk sd2 # still no fdisk table Disk: sd2 geometry: 478/255/63 [768 Sectors] Offset: 0 Signature: 0x111 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 82 77157 27 55 - 172421 98 24 [ 1239528960: 1530420603 ] Linux swap 1: 64 10096 3 23 - 176047 141 26 [ 162192451: 2666011513 ] NetWare 2.xx 2: 6E 252409 74 42 - 209458 117 56 [ 4054955288: 3604962205 ] 3: A9 19978 12 42 - 22375 228 62 [ 320947367:38521434 ] NetBSD # So: I was able to newfs, mount, and use an OpenBSD partition which disklabel called 'a' and which had no trace of an fdisk partition around it. As Allan pointed out, this is not for booting from - none of those fdisk partitions looks very healthy.
Re: Web documentation available offline by default?
On Mon, Mar 02, 2020 at 12:28:25PM +0100, Wolfgang Pfeiffer wrote: > > It's also a pity the the faq are not available in a single html or pdf > > format. This would be handy for those who, like me, are studying for > > the BSD Specialist certification. Having a single document makes it > > easier to search for a specific command. > > Seems to work on Linux at least: to "wget" the pages one needs, and > then "wkhtmltopdf" them to a pdf file. > > Takes time to get it done nicely with the correct flags for > wkhtmltopdf - and the wget procedure might not get all pages needed, > so intervening manually might be an option to get those, too ... > > On OBSD ports there's textproc/wkhtmltopdf. Didn't test the latter > tho'. > How about if the people who want this would, instead of pitying the fact that it's not available in the format you want, create a port (with a build depends on wkthmltopdf) to generate the files. And keep the port updated regularly or it would be deleted.
Re: Low throughput with 1 GigE interface
Peter wrote: > chi# iperf -c beta.internal.centroid.eu > > Client connecting to beta.internal.centroid.eu, TCP port 5001 > TCP window size: 17.0 KByte (default) > > [ 3] local 192.168.177.40 port 13242 connected with 192.168.177.2 port 5001 > [ ID] Interval Transfer Bandwidth > [ 3] 0.0-10.0 sec 536 MBytes 449 Mbits/sec > > ... on an APU1C4, could it be you have a slow switch or router? Any other > hardware that could slow yours down? > > I'm happy with this result, the APU1 is not really a powerhorse. That is pretty normal. From an older Intel-cpu laptop with a bge interface, to my APU2, both on a TP-Link gig switch, I get $ iperf -c gw-int Client connecting to gw-int, TCP port 5001 TCP window size: 32.5 KByte (default) [ 3] local 192.168.42.46 port 21653 connected with 192.168.42.254 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 502 MBytes 421 Mbits/sec $ Again, that's with no tuning. Did you try a different cable?
Awaiting a diff [was: Re: File systems...]
> - If we could clean-room implement a BSD-licensed > EXT3/EXT4/BTRFS/XFS/JFS/whatever, following style(8), would there be > interest in supporting that in OpenBSD? And which "we" are you referring to here? Did you mean yourself, or are you hoping that "somebody" will do it? > There's merit in the third option, OpenBSD already supports EXT2 (which > is also 90's vintage like ffs) as there are some platforms (e.g. > loongson) that require it. >... > EXT4 is also very widespread and stable, and seems to offer decent > performance. So send a diff that upgrades the code to ext3 and 4. > ZFS and BTRFS are much newer, and more complicated with software RAID > functionality built in. I think these would be harder to implement from > scratch. Persuade the owners to release under an ISC license. Then send a diff.
Re: Hyperbola Gnu Linux changing to Bsd
On Mon, 30 Dec 2019 at 19:57, Nick Holland wrote: most of them are stupid words. I just spot checked one of the "license problems" they think they spotted in the OpenBSD tree. http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/sys/arch/landisk/include/endian.h?rev=1.2 What exactly are they planning on licensing in that? I think they've scheduled a half-day committee meeting about that one file next week :-) Remember the history of /bin/false. History can repeat itself.
Re: Hyperbola Gnu Linux changing to Bsd
On 12/30/19 15:02, Peter Nicolai Mathias Hansteen wrote: The TL;DR version is that taking code or any other body of work that is offered to you under a permissive license and making your changes to it available only under a more restrictive one may be legal in some or all jurisdictions, but it is most certainly a sign of an almost total lack of respect for the people who did the original work. Not to mention: putting code under a more restrictive license than previously, while calling it "more free", is hypocrisy, pure and simple. Nothing gnu here, folks.
Re: vi in ramdisk?
On Fri, Nov 15, 2019 at 10:08:26AM -0700, Theo de Raadt wrote: > Christian Weisgerber wrote: > > > > I think, for editing config files, there are sure editors that > > > are simpler, smaller, not so powerful, but easier to use than ed. > > > > By all means, do not keep us in suspense and tell us the names of > > these editors. > > > > How large is a C implementation of TECO? > > he probably means cat plus the shell's redirection capability. > Who needs cat when you have echo?
Re: urtwn(4) gets wedged periodically
On Wed, Nov 13, 2019 at 01:25:46PM -0500, Ted Unangst wrote: > > Can you give me the exact model of the one you bought recently? I have > > half a mind to just write > > off mine as a loss and buy something else. > > I am using this one: (the TL-WN725N N150 single band one) > > https://www.amazon.com/TP-Link-wireless-network-Adapter-SoftAP/dp/B008IFXQFU/ I have that one and it wedges occasionally (on a MacBook Pro with 6.6-current), though infrequently.
Re: acme-client issue with domain w/ alternative name
On Thu, Nov 07, 2019 at 11:34:48PM +, Mik J wrote: > Hello, > What this does mean ?> Just to follow up: Of my two problem domains, one was > caused by pebkac pebkac = problem exists between keyboard and chair. In other words, user error
Re: Tools for writers
On Mon, Nov 04, 2019 at 02:06:35AM -0500, Steve Litt wrote: > > I know what you mean and you're right to a degree, but I'm currently > writing a couple of books with AsciiDoctor edited in Vim. And I use > VimOutliner for outlining. I'll try to remember and let you know when I > actually finish one of the books. I've used AsciiDoc and AsciiDoctor for two large O'Reilly Cookbooks which I proof locally in PDF. Their publishing sofware puts it through some arcane toolchain which formats to their house style , and generateds PDF, EPub, HTML, etc. But all the editing work is done, like Steve's, in vi and asciidoctor. I've also used adoc for magazine articles where the publisher "needs" the file in MS-Word format. For that I use pandoc (on another box) to convert adoc into docx.
Re: acme-client issue with domain w/ alternative name
On 10/21/19 19:38, Ian Darwin wrote: Today acme-client renewed all but 2 of my domains; the two that have "alternative names" in the certificates. I cannot get it to renew those two. This is on amd64 on 6.6-current, updated today. Just to follow up: Of my two problem domains, one was caused by pebkac (sorry) and the other, which I tried 5 or 6 times last night, worked like a charm this morning, with no config changes. I'll just blame transient network conditions for that one.
acme-client issue with domain w/ alternative name
Today acme-client renewed all but 2 of my domains; the two that have
"alternative names"
in the certificates. I cannot get it to renew those two. This is on amd64 on
6.6-current,
updated today.
My acme-config.conf is the latest example version, with the v2 URLs and with
example.com replaced by
my domains.
#
# $OpenBSD: acme-client.conf,v 1.2 2019/06/07 08:08:30 florian Exp $
#
authority letsencrypt {
api url "https://acme-v02.api.letsencrypt.org/directory;
account key "/etc/acme/letsencrypt-privkey.pem"
}
authority letsencrypt-staging {
api url "https://acme-staging-v02.api.letsencrypt.org/directory;
account key "/etc/acme/letsencrypt-staging-privkey.pem"
}
domain androidcookbook.com {
alternative names { androidcookbook.net }
domain key "/etc/ssl/private/androidcookbook.com.key"
domain certificate "/etc/ssl/androidcookbook.com.crt"
domain full chain certificate
"/etc/ssl/androidcookbook.com.fullchain.pem"
sign with letsencrypt
}
domain annabot.org {
domain key "/etc/ssl/private/annabot.org.key"
domain certificate "/etc/ssl/annabot.org.crt"
domain full chain certificate
"/etc/ssl/annabot.org.fullchain.pem"
sign with letsencrypt
}
...
The first domain fails, the second one succeeded.
$ doas acme-client androidcookbook.com
acme-client: 172.65.32.248: tls_close: EOF without close notify
acme-client: 172.65.32.248: tls_close: EOF without close notify
acme-client: 172.65.32.248: tls_close: EOF without close notify
acme-client: 172.65.32.248: tls_close: EOF without close notify
acme-client: 172.65.32.248: tls_close: EOF without close notify
acme-client: 172.65.32.248: tls_close: EOF without close notify
acme-client: 172.65.32.248: tls_close: EOF without close notify
$ echo $?
1
$
IDK what those EOF w/o notify are caused by, but the domains that worked
also gave a similar bunch of that message.
Running with -v does not give any useful info except it ends with -1:
$ doas acme-client -v -F androidcookbook.com
acme-client: /etc/ssl/androidcookbook.com.crt: certificate renewable: 29 days
left
acme-client: https://acme-v02.api.letsencrypt.org/directory: directories
acme-client: acme-v02.api.letsencrypt.org: DNS: 172.65.32.248
acme-client: 172.65.32.248: tls_close: EOF without close notify
acme-client: 172.65.32.248: tls_close: EOF without close notify
acme-client: dochngreq:
https://acme-v02.api.letsencrypt.org/acme/authz-v3/882690343
acme-client: 172.65.32.248: tls_close: EOF without close notify
acme-client: challenge, token: 22zE2mRAquYtRmY0lMxiCVfYXcTLEUEm78rRa6Nt0So,
uri: https://acme-v02.api.letsencrypt.org/acme/chall-v3/882690343/im5q-Q,
status: 0
acme-client: /var/www/acme/22zE2mRAquYtRmY0lMxiCVfYXcTLEUEm78rRa6Nt0So: created
acme-client:
https://acme-v02.api.letsencrypt.org/acme/chall-v3/882690343/im5q-Q: challenge
acme-client: 172.65.32.248: tls_close: EOF without close notify
acme-client: dochngreq:
https://acme-v02.api.letsencrypt.org/acme/authz-v3/882690357
acme-client: 172.65.32.248: tls_close: EOF without close notify
acme-client: challenge, token: XQm6jdVi6yzlFJHP8ucI8d3AenQFl81KqfC4tNlaDsU,
uri: https://acme-v02.api.letsencrypt.org/acme/chall-v3/882690357/7cuNOw,
status: 0
acme-client: /var/www/acme/XQm6jdVi6yzlFJHP8ucI8d3AenQFl81KqfC4tNlaDsU: created
acme-client:
https://acme-v02.api.letsencrypt.org/acme/chall-v3/882690357/7cuNOw: challenge
acme-client: 172.65.32.248: tls_close: EOF without close notify
acme-client: 172.65.32.248: tls_close: EOF without close notify
acme-client: order.status -1
acme-client: bad exit: netproc(82984): 1
$
Any thoughts or more info? Thx.
Re: handling snapshot installation in production environment
> The sysupgrade tool is a nice way to install the newest snapshot, never > had a problem. But what is the correct way to install a stable release > on snapshot? Using the standard bsd.rd upgrade way? >From man sysupgrade: -r Upgrade to the next release. The default is to find out if the system is running a release or a snapshot. In case of release sysupgrade downloads the next release. So when 6.6 is announced as released # sysupgrade -r
Re: Reboot and re-link (fwd) Maxim Bourmistrov: Re: Reboot and re-link (fwd) Maxim Bourmistrov: Re: Reboot and re-link (fwd) Maxim Bourmistrov: Re: Reboot and re-link
On 6/20/19 5:31 PM, Theo de Raadt wrote: It just doesn't stop. Maxim Bourmistrov wrote: I'd say this whole project is your milking cow.(Having a good times biking??) You really don't move froward much. Except poor guy trying to fix net stack. You move around vars, back and forward. But really - no progress. Community thinks their push money to dev stuff, in real - their push Theos bills forward. Nice illusion. I'm yet another one in this line. Disappointed, seen to much AND been rejected by Theos. One in line. This is why kill files were invented.
Re: Installer sucks ! (Re: OpenBSD on VMware ESXi)
On 5/23/19 7:51 AM, Roderick wrote: I wonder that no one noted this bugs before: are there no new people installing OpenBSD? Or it is a problem only with VMWare? Yes, the fact that nobody else has run into your problem suggest that it might in fact be your problem. Or your provider may be doing something strange. It's great that you are exploring this, and may yet find an actual issue, but if you just wanted hosting in a hurry and cheap, vultr.com offers an entry-level vhost with OpenBSD 6.5 (or half a dozen others including BSDs and Linuxes) already installed (or you can use any ISO to install from) for US$2.50/month, with console access. I'm hosting my secondary DNS there and have had zero issues so far, though I didn't do a full reinstall.
Re: [PATCH] Remove "Multibooting" in FAQ
On 4/6/19 1:45 PM, tfrohw...@fastmail.com wrote: I run a dual-boot with Windows 10 on the same partition and the section that you want removed was extremely helpful at the time. That is_with_ softraid encryption of the OpenBSD partition. Setting this up is not for the faint of heart and you have to have backups and a restore strategy before tinkering with multi-booting. Very true. Your removal request rests on the assumption that because you didn't managed to configure dual-booting nobody can (or should). How about instead you reach out to compare yours to other people's experience? Who knows, maybe a_useful_ addition to the FAQ might come out of it that can help reduce the risk of similar problems for others in the future? Most operating systems are not "designed" for multi-booting; they assume that they have the whole system. Yet somehow almost all of them can be made to work in a multi-booted environment. So that section of the doc is not going away just because one person wasn't careful enough in following it and lost their windows partition. That said, if you can find out exactly what he did wrong and it's not in the doc, as tfrowhwein said, send a patch to improve the document.
Anybody got an Acer Aspire One AOD250 running OpenBSD? Does suspend/resume work?
I just inherited this AOD250 and put 6.4 up on it. Got it to the point
where it mostly works, except suspend (zzz or lid close) doesn't resume
- it reboots instead when you press a keyboard key.
I'm unable to tell if the problem is hardware (eg specific to this one
unit) or software (old ACPI?). But there was at least one (years old)
report of issues with resume (lockup not reboot) on this same type model
(AOD250).
Battery is fine. CMOS battery appears OK, at least it holds the date
setting without main battery. Swapping RAM DIMMs doesn't help.
Running last available BIOS. Dmesg below for 6.4 stable, patched, but
-current behaves the same way. Tried a 6.2 kernel and it fails too. No
diagnostic info in dmesg.
Any similar reports (working or not working, preferably on 6.{4,3,2}),
but ONLY for AO D250, or suggestions to diagnose, would be appreciated.
Thanks for listening.
OpenBSD 6.4 (GENERIC.MP) #3: Thu Dec 20 18:20:58 CET 2018
r...@syspatch-64-i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
RTC BIOS diagnostic error 80
real mem = 1062182912 (1012MB)
avail mem = 1027678208 (980MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 12/18/10, SMBIOS rev. 2.4 @ 0xe8240 (31 entries)
bios0: vendor Acer version "V1.29" date 12/18/2010
bios0: Acer Aspire one
acpi0 at bios0: rev 2
acpi0: sleep states S3 S4 S5
acpi0: tables DSDT FACP SSDT HPET APIC MCFG ASF! SLIC BOOT
acpi0: wakeup devices UHC1(S3) UHC2(S3) UHC3(S3) UHC4(S3) ECHI(S3)
EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) AZAL(S0) MODM(S0)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz ("GenuineIntel" 686-class)
1.60 GHz, 06-1c-02
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,LAHF,PERF,SENSOR,MELTDOWN
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 133MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.0.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Atom(TM) CPU N270 @ 1.60GHz ("GenuineIntel" 686-class)
1.60 GHz, 06-1c-02
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,LAHF,PERF,SENSOR,MELTDOWN
ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins, remapped
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (EXP1)
acpiprt2 at acpi0: bus 2 (EXP2)
acpiprt3 at acpi0: bus 3 (EXP3)
acpiprt4 at acpi0: bus 4 (EXP4)
acpiec0 at acpi0
acpicpu0 at acpi0: !C3(100@57 io@0x416), !C2(500@1 io@0x414), C1(1000@1
halt), PSS
acpicpu1 at acpi0: !C3(100@57 io@0x416), !C2(500@1 io@0x414), C1(1000@1
halt), PSS
acpipwrres0 at acpi0: FN00, resource for FAN_
acpitz0 at acpi0: critical temperature is 100 degC
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: LID0
acpibtn2 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model "13850828090658133" type Lion oem "PANASONIC "
acpiac0 at acpi0: AC unit online
acpicmos0 at acpi0
"SYN1B1C" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
acpivideo0 at acpi0: OVGA
acpivout0 at acpivideo0: LCD_
bios0: ROM list: 0xc/0xec00!
cpu0: Enhanced SpeedStep 1597 MHz: speeds: 1600, 1333, 1066, 800 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GME Host" rev 0x03
inteldrm0 at pci0 dev 2 function 0 "Intel 82945GME Video" rev 0x03
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp0: aperture at 0x4000, size 0x1000
inteldrm0: apic 4 int 16
inteldrm0: 1024x600, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel 82945GM Video" rev 0x03 at pci0 dev 2 function 1 not configured
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi
azalia0: codecs: Realtek ALC272
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: apic 4 int 16
pci1 at ppb0 bus 1
ath0 at pci1 dev 0 function 0 "Atheros AR5424" rev 0x01: apic 4 int 16
ath0: AR5424 14.2 phy 7.0 rf 10.2 eeprom 5.4, WOR5_ETSIC, address
00:24:2c:xx:xx:xx
ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: apic 4 int 17
pci2 at ppb1 bus 2
ppb2 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x02: apic 4 int 18
pci3 at ppb2 bus 3
alc0 at pci3 dev 0 function 0 "Attansic Technology L2C" rev 0xc0: msi,
address 00:23:5a:xx:xx:xx
atphy0 at alc0 phy 0: F1 10/100/1000 PHY, rev. 11
ppb3 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x02: apic 4 int 19
pci4 at ppb3 bus 4
iwn0 at pci4 dev 0 function 0 "Intel WiFi Link 5100" rev 0x00: msi, MIMO
1T2R, MoW, address 00:21:5d:xx:xx:xx
Re: [PATCH] Fix interrupt handling in ral(4) for RT2661 under load
On Nov 23 Roland Dreir sent a patch for interrupt handling, but it
doesn't apply on -current since the file rt2661.c changed slightly
a few weeks earlier (1.51, date: 2009/11/01).
This patch just changes Roland's patch to update against rt2661.c
r1.51 from the OpenBSD repository instead of Roland's patch which
is against his private GIT repo.
I've been running with this for just over a day, including some
time copying kernels and snaps both ways non-stop (after removing
the ifconfig down/up from crontab). It has locked up only twice in
24 hrs, a definite improvement.
Index: rt2661.c
===
RCS file: /cvs/src/sys/dev/ic/rt2661.c,v
retrieving revision 1.51
diff -N -u -p rt2661.c
--- rt2661.c1 Nov 2009 12:08:36 - 1.51
+++ rt2661.c28 Dec 2009 21:16:06 -
@@ -97,9 +97,8 @@ void rt2661_newassoc(struct ieee80211com *, struct ie
intrt2661_newstate(struct ieee80211com *, enum ieee80211_state,
int);
uint16_t rt2661_eeprom_read(struct rt2661_softc *, uint8_t);
+void rt2661_free_tx_desc(struct rt2661_softc *, struct
rt2661_tx_ring *);
void rt2661_tx_intr(struct rt2661_softc *);
-void rt2661_tx_dma_intr(struct rt2661_softc *,
- struct rt2661_tx_ring *);
void rt2661_rx_intr(struct rt2661_softc *);
#ifndef IEEE80211_STA_ONLY
void rt2661_mcu_beacon_expire(struct rt2661_softc *);
@@ -115,7 +114,7 @@ uint16_trt2661_txtime(int, int, uint32_t);
uint8_trt2661_plcp_signal(int);
void rt2661_setup_tx_desc(struct rt2661_softc *,
struct rt2661_tx_desc *, uint32_t, uint16_t, int, int,
- const bus_dma_segment_t *, int, int);
+ const bus_dma_segment_t *, int, int, int);
intrt2661_tx_mgt(struct rt2661_softc *, struct mbuf *,
struct ieee80211_node *);
intrt2661_tx_data(struct rt2661_softc *, struct mbuf *,
@@ -376,7 +375,7 @@ rt2661_alloc_tx_ring(struct rt2661_softc *sc, struct r
ring-count = count;
ring-queued = 0;
- ring-cur = ring-next = ring-stat = 0;
+ ring-cur = ring-stat = 0;
error = bus_dmamap_create(sc-sc_dmat, count * RT2661_TX_DESC_SIZE, 1,
count * RT2661_TX_DESC_SIZE, 0, BUS_DMA_NOWAIT, ring-map);
@@ -470,7 +469,7 @@ rt2661_reset_tx_ring(struct rt2661_softc *sc, struct r
BUS_DMASYNC_PREWRITE);
ring-queued = 0;
- ring-cur = ring-next = ring-stat = 0;
+ ring-cur = ring-stat = 0;
}
void
@@ -881,6 +880,36 @@ rt2661_eeprom_read(struct rt2661_softc *sc, uint8_t ad
}
void
+rt2661_free_tx_desc(struct rt2661_softc *sc, struct rt2661_tx_ring *txq)
+{
+ struct rt2661_tx_desc *desc = txq-desc[txq-stat];
+ struct rt2661_tx_data *data = txq-data[txq-stat];
+ struct ieee80211com *ic = sc-sc_ic;
+
+ bus_dmamap_sync(sc-sc_dmat, data-map, 0,
+ data-map-dm_mapsize, BUS_DMASYNC_POSTWRITE);
+ bus_dmamap_unload(sc-sc_dmat, data-map);
+ m_freem(data-m);
+ data-m = NULL;
+
+ /* descriptor is no longer valid */
+ desc-flags = ~htole32(RT2661_TX_VALID);
+
+ bus_dmamap_sync(sc-sc_dmat, txq-map,
+ txq-stat * RT2661_TX_DESC_SIZE, RT2661_TX_DESC_SIZE,
+ BUS_DMASYNC_PREWRITE);
+
+ if (data-ni) {
+ ieee80211_release_node(ic, data-ni);
+ data-ni = NULL;
+ }
+
+ txq-queued--;
+ if (++txq-stat = txq-count) /* faster than % count */
+ txq-stat = 0;
+}
+
+void
rt2661_tx_intr(struct rt2661_softc *sc)
{
struct ieee80211com *ic = sc-sc_ic;
@@ -888,7 +917,7 @@ rt2661_tx_intr(struct rt2661_softc *sc)
struct rt2661_tx_ring *txq;
struct rt2661_tx_data *data;
struct rt2661_node *rn;
- int qid, retrycnt;
+ int qid, ind, retrycnt;
for (;;) {
const uint32_t val = RAL_READ(sc, RT2661_STA_CSR4);
@@ -898,7 +927,14 @@ rt2661_tx_intr(struct rt2661_softc *sc)
/* retrieve the queue in which this frame was sent */
qid = RT2661_TX_QID(val);
txq = (qid = 3) ? sc-txq[qid] : sc-mgtq;
+ ind = RT2661_TX_INDEX(val);
+ if (txq-stat != ind)
+ DPRINTFN(10, (missed TX interrupt, catching up
+stat %d to index %d\n, txq-stat, ind, qid));
+ while (txq-stat != ind)
+ rt2661_free_tx_desc(sc, txq);
+
/* retrieve rate control algorithm context */
data = txq-data[txq-stat];
rn = (struct rt2661_node *)data-ni;
@@ -934,14 +970,9 @@ rt2661_tx_intr(struct rt2661_softc *sc)
ifp-if_oerrors++;
}
- ieee80211_release_node(ic, data-ni);
-
Re: tried 3.0 not 3.7 and still can't get very far
You should find somebody local that has a bit of experience, as you are having problems that others do not have. btinternet.com is in the UK, so you might try our two UK user groups, at http://www.openbsd.org/groups.html#United (If you're in another country, go to the top of the page and find the country link.) See also the PC notebooks page, http://www.openbsd.org/i386-laptop.html P.S. ports@ is the wrong list for that type of query, so I'm redirecting to [EMAIL PROTECTED] when I purchsed 3 there were all kinds of problems with loading on a laptop Now I purchsed 3.7 and it looks like this is the final end of the road for openbsd and me I tolerated figuring out the wireless settings and even though there is some reason for a huge time lag installing packages my main concern is there is NO flexibility in getting it setup 1. every other download has some kind of 'serious' error yet the package loads 2. OK finally fed up with instaling upteen seperate packages to get something to work i.e. gnome then atttempted to dowload everything and install what I want. Well the ftp blows up. 3. just have no sure way of knowing when this system will start doing some real work. spending all my time with problems and have no single docuement to help Just pissed off that I blew my money on an impossible system to get running right
