Re: openFPGAloader successfully built, but can't flash with ftdi error

2023-10-05 Thread misc
This subject interests me a lot. Can you tell us which model of FPGA 
have you bought / are you using?


On 10/5/23 21:01, S V wrote:

Good Day, List!

This mail is call for help, advice and to stir interest.

While playing with open source workflow for FPGA chips
I found with pleasure that not only GoWin FPGAs supported by open
source tools, but also all needed tools easily built on OpenBSD
(working on ports now). yosys, project apycula, nextpnr-gowin,
openFPGAloader all successfully build.

But I can't flash "compiled" bitstream to hardware device with
openFPGAloader.

Here is description of problem:

After building software and attaching HW I can successfully scan usb

found 10 USB device
Bus device vid:pid probe type manufacturer serial product
000 001 0x:0x xvc-client Generic none xHCI root hub
001 001 0x:0x xvc-client Generic none xHCI root hub
001 005 0x0403:0x6010 FTDI2232 SIPEED FactoryAIOT Pro JTAG Debugger

but cant detect or flash bitstream with next error

doas openFPGALoader -b tangnano9k pack.fs --verbose-level=3
try to open 403 6010 0 0
iProduct : JTAG Debugger
8
b
8
b
fail to read data usb bulk read failed
JTAG init failed with: low level FTDI init failed


here dmesg

 uftdi0 at uhub3 port 3 configuration 1 interface 0 "SIPEED JTAG
Debugger" rev 2.00/5.00 addr 5 ucom0 at uftdi0 portno 1
 uftdi1 at uhub3 port 3 configuration 1 interface 1 "SIPEED JTAG
Debugger" rev 2.00/5.00 addr 5 ucom1 at uftdi1 portno 2

and also usbdevs outputs

 addr 05: 0403:6010 SIPEED, JTAG Debugger
 full speed, power 90 mA, config 1, rev 5.00, iSerial FactoryAIOT Pro
 driver: uftdi0
 driver: uftdi1


I also posted issue to original github
https://github.com/trabucayre/openFPGALoader/issues/382

Any tips and tricks on how to debug it? Any interest in helping?





Re: Problems with HD

2023-10-05 Thread Bryan Steele
On Thu, Oct 05, 2023 at 05:41:28AM +, Maria Morisot wrote:
> > On Thu, Oct 05, 2023 at 04:08:34AM +, Maria Morisot wrote:
> > 
> > > I have an Asus Vivobook (1400EA),
> > > and the hard drive is not recognized
> > > by OpenBSD. I have the same problem
> > > on some distros of Linux, but on others
> > > it shows up fine.
> > 
> > 
> > My Asus ZenBook had a similar issue, which was resolved
> > by diving into the BIOS "Advanced" section and setting the
> > storage controller to something other than the pseudo-RAID
> > mode. It may we worth checking whether there is such an option
> > available.
> 
> I went into the BIOS and can't see anything about disabling RAID; and the 
> disk itself says there is no RAID on the drive. But I did get into the BIOS 
> info for the drive itself so I'll post that in case someone finds it useful.
> 
> Port: 1.0
> Model Number: Micron_2450_MTFDKBA256
> Serial Number: 214532CBCA77
> Size 238.4GB
> Controller Type: NVMe
> Controller Interface: PCIe

The option may be called "Intel Volume Management Device" (VMD), if you
don't see anything about RAID or Intel Rapid Storage RST.

It would be helpful to see a dmesg to confirm that this is the problem
you're having though.

-Bryan.
(VMD)



openFPGAloader successfully built, but can't flash with ftdi error

2023-10-05 Thread S V
Good Day, List!

This mail is call for help, advice and to stir interest.

While playing with open source workflow for FPGA chips
I found with pleasure that not only GoWin FPGAs supported by open
source tools, but also all needed tools easily built on OpenBSD
(working on ports now). yosys, project apycula, nextpnr-gowin,
openFPGAloader all successfully build.

But I can't flash "compiled" bitstream to hardware device with
openFPGAloader.

Here is description of problem:

After building software and attaching HW I can successfully scan usb

found 10 USB device
Bus device vid:pid probe type manufacturer serial product
000 001 0x:0x xvc-client Generic none xHCI root hub
001 001 0x:0x xvc-client Generic none xHCI root hub
001 005 0x0403:0x6010 FTDI2232 SIPEED FactoryAIOT Pro JTAG Debugger

but cant detect or flash bitstream with next error

doas openFPGALoader -b tangnano9k pack.fs --verbose-level=3
try to open 403 6010 0 0
iProduct : JTAG Debugger
8
b
8
b
fail to read data usb bulk read failed
JTAG init failed with: low level FTDI init failed


here dmesg

uftdi0 at uhub3 port 3 configuration 1 interface 0 "SIPEED JTAG
Debugger" rev 2.00/5.00 addr 5 ucom0 at uftdi0 portno 1
uftdi1 at uhub3 port 3 configuration 1 interface 1 "SIPEED JTAG
Debugger" rev 2.00/5.00 addr 5 ucom1 at uftdi1 portno 2

and also usbdevs outputs

addr 05: 0403:6010 SIPEED, JTAG Debugger
full speed, power 90 mA, config 1, rev 5.00, iSerial FactoryAIOT Pro
driver: uftdi0
driver: uftdi1


I also posted issue to original github
https://github.com/trabucayre/openFPGALoader/issues/382

Any tips and tricks on how to debug it? Any interest in helping?

-- 
Nerfur Dragon
-==(UDIC)==-



Re: Bridging em and vlan

2023-10-05 Thread David Gwynne



> On 6 Oct 2023, at 01:50, David Higgs  wrote:
> 
> Logically, I wanted three hosts in the same broadcast domain (ISP CPE, IoT 
> device, OpenBSD router), so tpmr(4) didn't seem appropriate - was I missing 
> something?

No, you were right to reach for veb in your setup.



Re: Understanding -current as 7.4 is released

2023-10-05 Thread 0x1eef
> Also be aware that no security fixes will be released for 7.4-stable
> before 7.4-release is officially released.  That means if you
> run 7.4-release before it is officially released, you need to pay
> attention to any security issues that might affect you - but that's
> just the same that always applies when running -current.

Can you clarify what you mean by that ? 

One of the reasons I moved to snapshots is that a release is close, 
and another is that 7.3-STABLE has not seen a package update for 
chromium in quite a while. 

I believe it is still at v111. There's been a few important updates 
since then, and the easiest way to get them is to stay on -current. 




Re: Understanding -current as 7.4 is released

2023-10-05 Thread Ingo Schwarze
Hi Ronald,

Ronald Dahlgren wrote on Thu, Oct 05, 2023 at 12:45:56PM -0400:

> I’ve been running -current for several months now. Recently I started
> using “-D snap” when updating packages with pkg_add.

If you install a snapshot right now, what you actually get is
extremely close to what will be released as 7.4-release, though
there is no guarantee that it will be identical.  A small number
of bugs may still get fixed before release, if they are important
enough to justify adding additional work to the release process.

Also be aware that no security fixes will be released for 7.4-stable
before 7.4-release is officially released.  That means if you
run 7.4-release before it is officially released, you need to pay
attention to any security issues that might affect you - but that's
just the same that always applies when running -current.

> I ask the list to help me understand what, if anything, I need to
> do with my machines that run snapshots when 7.4 is released.

If you want to continue running -current, then you can run

  # sysupgrade -s

once post-release snapshots become available, or equivalently
manually upgrade to such a snaphot.

> Will I need to perform the upgrade procedures differently?

Except for potentially needing the -s flag as shown above above, no.
That flag may be needed because probably, your machines currently think
they are running 7.4-release, so sysupgrade(8) without arguments will
wait for 7.5 to appear.

> Is the release just a blessed snapshot and everything will continue
> to work as-is?

Mostly, yes.  It receives more testing than ordinary snapshots
and we are extra careful to avoid breaking stuff right before it.

The command "sysctl -n kern.version" tells you what a machine
is currently running:

OpenBSD X.Y-beta   = ongoing development *before* X.Y
OpenBSD X.Y with no suffix = release
OpenBSD X.Y-stable = stable branch based on the X.Y release
OpenBSD X.Y-current= ongoing development *after* X.Y

Yours,
  Ingo



Keyboard/trackpad issues on HP Chromebook 11 G5 Setzer

2023-10-05 Thread jrmu
>Synopsis:  Keyboard/trackpad issues on HP Chromebook 11 G5 Setzer
>Category:  amd64
>Environment:
System  : OpenBSD 7.4
Details : OpenBSD 7.4 (GENERIC.MP) #1382: Wed Sep 27 10:51:31 MDT 
2023
 
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

Architecture: OpenBSD.amd64
Machine : amd64
>Description:

I installed MrChromebox firmware
(https://mrchromebox.tech/static/fwscript.html) on an HP Chromebook 11
G5 Setzer, then proceeded to install OpenBSD 7.4 snapshots. I was able
to get OpenBSD to boot, built-in wifi is working but trackpad and
keyboard are malfunctional.

The trackpad itself is not detected at all. It neither senses clicks nor
mouse movements.

The keyboard does sense keypresses but each keypress is interpreted as
several presses (typing the letter 'a' once results in a string of 6
'a's). When the BSD bootloader is first started, the built-in keyboard
works fine. Only after OpenBSD has finished loading does the keyboard
start to duplicate keypresses. To install the system, I attached an
external USB keyboard, which works perfectly with no duplicate
keypresses.

Thanks in advance for the help, I'm delighted to have OpenBSD booting on
a chromebook.

dmesg:
OpenBSD 7.4 (GENERIC.MP) #1382: Wed Sep 27 10:51:31 MDT 2023
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2068180992 (1972MB)
avail mem = 1985830912 (1893MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x1fee8000 (17 entries)
bios0: vendor coreboot version "MrChromebox-4.20.1" date 07/21/2023
bios0: GOOGLE Setzer
efi0 at bios0: UEFI 2.7
efi0: EDK II rev 0x1
acpi0 at bios0: ACPI 6.0
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP SSDT MCFG TCPA APIC HPET TCPA BGRT
acpi0: wakeup devices XHCI(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Celeron(R) CPU N3060 @ 1.60GHz, 2480.53 MHz, 06-4c-04, patch 
0411
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu0: 24KB 64b/line 6-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 
16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 79MHz
cpu0: mwait min=64, max=64, C-substates=0.2, IBE
cpu1 at mainbus0: apid 4 (application processor)
cpu1: Intel(R) Celeron(R) CPU N3060 @ 1.60GHz, 2481.05 MHz, 06-4c-04, patch 
0411
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu1: 24KB 64b/line 6-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 
16-way L2 cache
cpu1: smt 0, core 2, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 115 pins
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiec0 at acpi0
acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
acpibtn0 at acpi0: LID0
acpiac0 at acpi0: AC unit online
acpibat0 at acpi0: BAT0 model "DR02043" serial 150F type LION oem "333-42-"
"GOOG0004" at acpi0 not configured
acpicmos0 at acpi0
"GOOG000A" at acpi0 not configured
"INTL9C60" at acpi0 not configured
"INTL9C60" at acpi0 not configured
dwiic0 at acpi0 I2C1 addr 0x9132/0x1000 irq 32
iic0 at dwiic0
ihidev0 at iic0 addr 0x20dwiic0: timed out reading remaining 30
, failed fetching initial HID descriptor
dwiic1 at acpi0 I2C5 addr 0x91324000/0x1000 irq 36
iic1 at dwiic1
"10EC5650" at iic1 addr 0x1a not configured
dwiic2 at acpi0 I2C6 addr 0x91326000/0x1000 irq 37
iic2 at dwiic2
ietp0 at iic2 addr 0x15 , can't establish interrupt
"808622A8" at acpi0 not configured
tpm0 at acpi0 TPM_ 1.2 (TIS) addr 0xfed4/0x5000, Infineon SLB9635 1.2 rev 
0x10
chvgpio0 at acpi0 GPSW uid 1 addr 0xfed8/0x8000 irq 49, 56 pins
chvgpio1 at acpi0 GPNC uid 2 addr 0xfed88000/0x8000 irq 48, 59 pins
chvgpio2 at acpi0 GPEC uid 3 addr 0xfed9/0x8000 irq 50, 24 pins
chvgpio3 at acpi0 GPSE uid 4 addr 0xfed98000/0x8000 irq 91, 55 pins
"INT3400" at acpi0 not configured
"INT3403" at acpi0 not configured
"INT3403" at acpi0 not configured
"INT3403" at acpi0 not configured
"INT3403" at acpi0 not configured
acpicpu0 at acpi0: C2 bad (state 6 has no substates): C3 bad (state 6 has no 
substates): C1(1000@1 mwait.1), PSS
acpicpu1 at 

Re: Newbie question

2023-10-05 Thread Ronny Machado
On Thu, Oct 05, 2023 at 10:44:06AM -0600, Todd C. Miller wrote:
> On Thu, 05 Oct 2023 13:07:02 -0300, Ronny Machado wrote:
> 
> > Every mail I post, Majordomo asks for a confirmation...Is this normal?
> > Am I doing something wrong???
> 
> Non-subscribers must confirm their posts.  This has almost entirely
> removed spam from the lists.
> 
> If you don't want to confirm each post, just subscribe to the list.
> You can disable message delivery in your majordomo settings if you
> don't actually want to receive any messages.
> 
>  - todd

Oops!! I thought I was :D

Thanks!!
R.



Understanding -current as 7.4 is released

2023-10-05 Thread Ronald Dahlgren
Hello friends,

I’ve been running -current for several months now. Recently I started using
“-D snap” when updating packages with pkg_add.

I ask the list to help me understand what, if anything, I need to do with
my machines that run snapshots when 7.4 is released. Will I need to perform
the upgrade procedures differently? Is the release just a blessed snapshot
and everything will continue to work as-is?

Thank you,
Ron


Re: Newbie question

2023-10-05 Thread Todd C . Miller
On Thu, 05 Oct 2023 13:07:02 -0300, Ronny Machado wrote:

> Every mail I post, Majordomo asks for a confirmation...Is this normal?
> Am I doing something wrong???

Non-subscribers must confirm their posts.  This has almost entirely
removed spam from the lists.

If you don't want to confirm each post, just subscribe to the list.
You can disable message delivery in your majordomo settings if you
don't actually want to receive any messages.

 - todd



Newbie question

2023-10-05 Thread Ronny Machado
Hi ppl...

Every mail I post, Majordomo asks for a confirmation...Is this normal?
Am I doing something wrong???


Thanks.

R.



Re: Touchpad not working

2023-10-05 Thread Ronny Machado


-- 
Ronny Machado
IT Consultant
+56 9 7519 9262

On Thu, Oct 05, 2023 at 03:48:25PM +, 0x1eef wrote:
> > Hi list, my first post ever...
> > 
> > I'm a *BSD user since 98 I think, mostly freebsd...now I'm totally
> > hooked on OpenBSD for a couple years now, not in my servers yet,
> > but in my office pc and my laptop...that's my question, this laptop
> > is a little Lenovo IdeaPad 14w, which I use mainly for pentesting...
> > or VkQuake once in a while :D
> > 
> > Ok...let's get serious...I've no real problem with this thing, works
> > almost everything out of the box, except the Wifi (Atheros QCA6174
> > 802.11ac), which doesn't work on FreeBSD either...so I don't really
> > care, I can connect to my cell phone or an USB wifi...the only thing
> > that I miss is the touchpad, can not getiing that thing working...
> > 
> > I suppose "synaptics" is loaded by X, at least under xorg.conf.d a
> > 70-synaptics.conf exist (dunno if that's the right driver anyway).
> > 
> > Attached Xorg.0.log and dmesg.out
> > 
> > I'd much appreciate any clues...
> > 
> > Thanx and hugs from Chile.
> > 
> > PD: "Everything works in linux" (I don't give a shit 'coz I don't use
> > linux :P )
> 
> I had an Lenovo IdeaPad that was shipped with Linux pre-installed.
> Must have been a different model. The trackpad did not ever work 
> except on Windows. I tried Linux, and (Free|Net|Open)BSD. IIRC 
> OpenBSD was diffilcult to get past post-install boot, and when 
> it did there were so many CPU interrupts it was impossible to use. 
> 
> I don't think it is the best Lenovo laptop to run BSD (or even Linux),
> but maybe you will get lucky. 
> 
> 
> 
Let's agree to disagree :) Laptop works nice with a little or mostly
no extra config...little slower than FBSD, but absolutely
capable...except for the touchpad ;)



Re: Bridging em and vlan

2023-10-05 Thread David Higgs
On Thu, Oct 5, 2023 at 9:04 AM David Gwynne  wrote:

>
>
> > On 5 Oct 2023, at 11:17, David Higgs  wrote:
> >
> > On Tue, Oct 3, 2023 at 10:10 AM David Higgs  wrote:
> >
> >> On Mon, Oct 2, 2023 at 9:26 AM David Higgs  wrote:
> >>
> >>> On Sun, Oct 1, 2023 at 9:13 AM Zé Loff  wrote:
> >>>
>  On Sat, Sep 30, 2023 at 11:39:36AM -0400, David Higgs wrote:
> > All of my devices until now have been behind my OpenBSD NAT router,
>  but I
> > recently acquired a Internet of Trash device that I would like to be
> > accessible to the internet (yes, I know).
> >
> > My home configuration uses a Unifi AP to translate my various SSIDs
>  into
> > VLANs which plug into one of my APU em(4) ports.  The IoT thing
>  already has
> > its own dedicated SSID/VLAN, but doesn't enjoy living behind my NAT.
> 
>  Define "doesn't enjoy".  It absolutely requires a public IP?  It needs
>  some ports to be forwarded?  Has some sort of network connection
>  detection that fails because some ports are blocked for outgoing
>  traffic?
> 
> >>>
> >>> I'm still trying to determine ground truth with manufacturer support.
> >>> Port forwarding doesn't seem sufficient.  The device can reach out just
> >>> fine but is not remotely controllable as advertised.
> >>>
>  Is there a way for me to bridge just one of the vlan(4) logical
>  interfaces
> > with my other em(4) uplink, so that my IoT item can speak DHCP
> directly
> > with my internet provider?
> 
> >>>
>  Can this be done with veb/vport or bridge, or will I need to use
>  something
> > more exotic to strip the 802.1q tags before they are sent to my ISP?
> 
> >>>
> >>> Self-replying here: I don't see many examples of veb(4) use online, but
> >>> it seems as if I can add my physical uplink and the IoT VLAN both to a
> >>> veb and attach a vport to become my new uplink.  That should be
> logically
> >>> equivalent to putting a three-port switch between my router and my ISP
> CPE,
> >>> with the third port for the IoT device.  Is anyone able to shoot holes
> in
> >>> this or suggest a superior alternative, before I attempt the
> configuration
> >>> later this week?
> >>>
> >>
> >> I appreciate the previous replies/cluebats, but my initial attempt was
> >> rushed and unsuccessful.
> >>
> >> In broad strokes, I created veb0 and added em0, vlan222, and vport0 to
> >> it.  Then I tried getting vport0 to speak DHCP with my upstream, but
> >> nothing seemed to happen or appear in logs.
> >>
> >> I will have to spend more time on this to eliminate the possibility of
> >> fat-fingering, remove various confounding variables, and produce a
> better
> >> result/report.
> >>
> >
> > For the archives, this worked swimmingly once I paid closer attention to
> > what I was doing.  Based on my second attempt, I hadn't put my vport0
> > interface up.
> >
> > Of course, my ISP isn't handing out more than a single IPv4 address by
> > default, so all this has been simply a good learning experience.
>
> For future reference, if you just want to join two ethernet interfaces on
> an openbsd box together you can use tpmr(4). It was almost called xcon(4),
> short for cross-connect.
>
> It's also worth noting the steps taken by the Ethernet stack when it
> processes packets and which drivers can take packets at which point. Let's
> assume an ethernet packet is coming in on a physical interface, em0 in this
> case.
>
> 1: trunk/aggr processing
>
> If em0 is part of trunk/aggr, then those drivers will steal the packet and
> start processing it again as if it was received on the relevant trunk/aggr
> interface.
>
> 2. service delimited packet filtering, ie, vlan/svlan handling
>
> If em0 is a parent interface to vlan or svlan interfaces, this is when
> they get taken and processing starts again as if they were received on the
> virtual interfaces.
>
> If no vlan/svlan interface is configured, the packets are marked as now
> marked as "service delimited".
>
> 3. bridge processing
>
> This is where bridge/veb/tpmr can take a packet.
>
> 4. dropping service delimited packets
>
> This is where vlan/svlan tagged packets are dropped that all the preceding
> aggr/trunk/vlan/svlan/bridge/veb/tpmr drivers declined. The exception is
> packets send to vlan 0, because vlan 0 isn't real and is only used to carry
> priority information on the wire for the native vlan.
>
> This means that you can set up a bridge/veb/tpmr that forwards vlan tagged
> packets, but optionally slice specific vlans off for other processing by
> configuring a vlan interface with em0 as a parent to take those packets
> away first.
>
> 5. carp
>
> If the destination address is for a carp interface on em0, it's at this
> point it's taken away.
>
> 6. Ethernet procotol handling
>
> This is when the arp/ipv4/ipv6 protocols are checked and the packets are
> fed into the layer 3 stacks.
>

Logically, I wanted three hosts in the same broadcast domain (ISP CPE, 

Re: Touchpad not working

2023-10-05 Thread 0x1eef
> Hi list, my first post ever...
> 
> I'm a *BSD user since 98 I think, mostly freebsd...now I'm totally
> hooked on OpenBSD for a couple years now, not in my servers yet,
> but in my office pc and my laptop...that's my question, this laptop
> is a little Lenovo IdeaPad 14w, which I use mainly for pentesting...
> or VkQuake once in a while :D
> 
> Ok...let's get serious...I've no real problem with this thing, works
> almost everything out of the box, except the Wifi (Atheros QCA6174
> 802.11ac), which doesn't work on FreeBSD either...so I don't really
> care, I can connect to my cell phone or an USB wifi...the only thing
> that I miss is the touchpad, can not getiing that thing working...
> 
> I suppose "synaptics" is loaded by X, at least under xorg.conf.d a
> 70-synaptics.conf exist (dunno if that's the right driver anyway).
> 
> Attached Xorg.0.log and dmesg.out
> 
> I'd much appreciate any clues...
> 
> Thanx and hugs from Chile.
> 
> PD: "Everything works in linux" (I don't give a shit 'coz I don't use
> linux :P )

I had an Lenovo IdeaPad that was shipped with Linux pre-installed.
Must have been a different model. The trackpad did not ever work 
except on Windows. I tried Linux, and (Free|Net|Open)BSD. IIRC 
OpenBSD was diffilcult to get past post-install boot, and when 
it did there were so many CPU interrupts it was impossible to use. 

I don't think it is the best Lenovo laptop to run BSD (or even Linux),
but maybe you will get lucky. 





Touchpad not working

2023-10-05 Thread Ronny Machado
Hi list, my first post ever...

I'm a *BSD user since 98 I think, mostly freebsd...now I'm totally
hooked on OpenBSD for a couple years now, not in my servers yet, 
but in my office pc and my laptop...that's my question, this laptop 
is a little Lenovo IdeaPad 14w, which I use mainly for pentesting...
or VkQuake once in a while :D

Ok...let's get serious...I've no real problem with this thing, works
almost everything out of the box, except the Wifi (Atheros QCA6174
802.11ac), which doesn't work on FreeBSD either...so I don't really
care, I can connect to my cell phone or an USB wifi...the only thing
that  I miss is the touchpad, can not getiing that thing working...

I suppose "synaptics" is loaded by X, at least under xorg.conf.d a
70-synaptics.conf exist (dunno if that's the right driver anyway).

Attached Xorg.0.log and dmesg.out

I'd much appreciate any clues...

Thanx and hugs from Chile.

PD: "Everything works in linux" (I don't give a shit 'coz I don't use
linux :P )

-- 
Ronny Machado
IT Consultant
+56 9 7519 9262

[   258.028] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
(Operation not permitted)
Check that you have set 'machdep.allowaperture=1'
in /etc/sysctl.conf and reboot your machine
refer to xf86(4) for details
[   258.028]linear framebuffer access unavailable
[   258.039] (--) Using wscons driver on /dev/ttyC4
[   258.057] 
X.Org X Server 1.21.1.6
X Protocol Version 11, Revision 0
[   258.058] Current Operating System: OpenBSD nostromo.my.domain 7.3 
GENERIC.MP#3 amd64
[   258.058]  
[   258.058] Current version of pixman: 0.40.0
[   258.058]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   258.058] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   258.058] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct  5 05:14:06 
2023
[   258.059] (==) Using system config directory 
"/usr/X11R6/share/X11/xorg.conf.d"
[   258.062] (==) No Layout section.  Using the first Screen section.
[   258.062] (==) No screen section available. Using defaults.
[   258.062] (**) |-->Screen "Default Screen Section" (0)
[   258.062] (**) |   |-->Monitor ""
[   258.063] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   258.063] (==) Automatically adding devices
[   258.063] (==) Automatically enabling devices
[   258.063] (==) Not automatically adding GPU devices
[   258.063] (==) Automatically binding GPU devices
[   258.063] (==) Max clients allowed: 256, resource mask: 0x1f
[   258.063] (==) FontPath set to:
/usr/X11R6/lib/X11/fonts/misc/,
/usr/X11R6/lib/X11/fonts/TTF/,
/usr/X11R6/lib/X11/fonts/OTF/,
/usr/X11R6/lib/X11/fonts/Type1/,
/usr/X11R6/lib/X11/fonts/100dpi/,
/usr/X11R6/lib/X11/fonts/75dpi/
[   258.063] (==) ModulePath set to "/usr/X11R6/lib/modules"
[   258.063] (II) The server relies on wscons to provide the list of input 
devices.
If no devices become available, reconfigure wscons or disable 
AutoAddDevices.
[   258.063] (II) Loader magic: 0xa49800a2e90
[   258.063] (II) Module ABI versions:
[   258.063]X.Org ANSI C Emulation: 0.4
[   258.063]X.Org Video Driver: 25.2
[   258.063]X.Org XInput driver : 24.4
[   258.063]X.Org Server Extension : 10.0
[   258.063] (--) PCI:*(0@0:1:0) 1002:98e4:17aa:39ea rev 202, Mem @ 
0xe800/134217728, 0xf080/8388608, 0xf050/262144, I/O @ 
0x3000/256
[   258.063] (II) LoadModule: "glx"
[   258.064] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
[   258.073] (II) Module glx: vendor="X.Org Foundation"
[   258.073]compiled for 1.21.1.6, module version = 1.0.0
[   258.073]ABI class: X.Org Server Extension, version 10.0
[   258.073] (==) Matched ati as autoconfigured driver 0
[   258.073] (==) Matched modesetting as autoconfigured driver 1
[   258.073] (==) Assigned the driver to the xf86ConfigLayout
[   258.073] (II) LoadModule: "ati"
[   258.074] (II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.so
[   258.074] (II) Module ati: vendor="X.Org Foundation"
[   258.075]compiled for 1.21.1.6, module version = 19.1.0
[   258.075]Module class: X.Org Video Driver
[   258.075]ABI class: X.Org Video Driver, version 25.2
[   258.104] (II) LoadModule: "amdgpu"
[   258.105] (II) Loading /usr/X11R6/lib/modules/drivers/amdgpu_drv.so
[   258.106] (II) Module amdgpu: vendor="X.Org Foundation"
[   258.106]compiled for 1.21.1.6, module version = 23.0.0
[   258.106]Module class: X.Org Video Driver
[   258.106]ABI class: X.Org Video Driver, version 25.2
[   258.106] (II) LoadModule: "modesetting"
[   258.107] (II) Loading /usr/X11R6/lib/modules/drivers/modesetting_drv.so
[   258.107] (II) Module modesetting: vendor="X.Org Foundation"
[   

Re: X11 crashing

2023-10-05 Thread Theo de Raadt
Maria Morisot  wrote:

> I installed the patch for X11 (October 3rd), then rebooted,
> now X is crashing every time I log in on xenodm,
> sometimes I get a blue screen with debug messages,
> other times I get a square on my screen with a black background,
> and it is otherwise completely frozen, and I can't ctrl-alt-Fn
> into a terminal. I can do this before I try logging in though,
> and I tried reverting the patch but to no avail.
> 
> My wm is xfce, and when I remove my .xsession
> everything works normal without crashing.
> 
> I'm far from a novice user but I don't know much about
> how to properly report issues or what steps I need to take
> to isolate where the problem is.

Your bug report is too precise and detailed.

For example you say "blue screen with debug messages".

Amazing.  By not providing information, it's like you don't want
any help!  OK. In that case, I'm replying to give you no help.



Re: X11 crashing

2023-10-05 Thread Thomas Frohwein
On Thu, Oct 05, 2023 at 06:23:36AM +, Maria Morisot wrote:
> I installed the patch for X11 (October 3rd), then rebooted,
> now X is crashing every time I log in on xenodm,
> sometimes I get a blue screen with debug messages,
> other times I get a square on my screen with a black background,
> and it is otherwise completely frozen, and I can't ctrl-alt-Fn
> into a terminal. I can do this before I try logging in though,
> and I tried reverting the patch but to no avail.
> 
> My wm is xfce, and when I remove my .xsession
> everything works normal without crashing.

The obvious question that I have right off the bat is what is in your
.xsession... Sharing that file or clarifying if anything other than
xfce is in there would be a start.

> 
> I'm far from a novice user but I don't know much about
> how to properly report issues or what steps I need to take
> to isolate where the problem is.

There is some useful information on making useful bug reports here:
https://www.openbsd.org/report.html



Re: Bridging em and vlan

2023-10-05 Thread David Gwynne



> On 5 Oct 2023, at 11:17, David Higgs  wrote:
> 
> On Tue, Oct 3, 2023 at 10:10 AM David Higgs  wrote:
> 
>> On Mon, Oct 2, 2023 at 9:26 AM David Higgs  wrote:
>> 
>>> On Sun, Oct 1, 2023 at 9:13 AM Zé Loff  wrote:
>>> 
 On Sat, Sep 30, 2023 at 11:39:36AM -0400, David Higgs wrote:
> All of my devices until now have been behind my OpenBSD NAT router,
 but I
> recently acquired a Internet of Trash device that I would like to be
> accessible to the internet (yes, I know).
> 
> My home configuration uses a Unifi AP to translate my various SSIDs
 into
> VLANs which plug into one of my APU em(4) ports.  The IoT thing
 already has
> its own dedicated SSID/VLAN, but doesn't enjoy living behind my NAT.
 
 Define "doesn't enjoy".  It absolutely requires a public IP?  It needs
 some ports to be forwarded?  Has some sort of network connection
 detection that fails because some ports are blocked for outgoing
 traffic?
 
>>> 
>>> I'm still trying to determine ground truth with manufacturer support.
>>> Port forwarding doesn't seem sufficient.  The device can reach out just
>>> fine but is not remotely controllable as advertised.
>>> 
 Is there a way for me to bridge just one of the vlan(4) logical
 interfaces
> with my other em(4) uplink, so that my IoT item can speak DHCP directly
> with my internet provider?
 
>>> 
 Can this be done with veb/vport or bridge, or will I need to use
 something
> more exotic to strip the 802.1q tags before they are sent to my ISP?
 
>>> 
>>> Self-replying here: I don't see many examples of veb(4) use online, but
>>> it seems as if I can add my physical uplink and the IoT VLAN both to a
>>> veb and attach a vport to become my new uplink.  That should be logically
>>> equivalent to putting a three-port switch between my router and my ISP CPE,
>>> with the third port for the IoT device.  Is anyone able to shoot holes in
>>> this or suggest a superior alternative, before I attempt the configuration
>>> later this week?
>>> 
>> 
>> I appreciate the previous replies/cluebats, but my initial attempt was
>> rushed and unsuccessful.
>> 
>> In broad strokes, I created veb0 and added em0, vlan222, and vport0 to
>> it.  Then I tried getting vport0 to speak DHCP with my upstream, but
>> nothing seemed to happen or appear in logs.
>> 
>> I will have to spend more time on this to eliminate the possibility of
>> fat-fingering, remove various confounding variables, and produce a better
>> result/report.
>> 
> 
> For the archives, this worked swimmingly once I paid closer attention to
> what I was doing.  Based on my second attempt, I hadn't put my vport0
> interface up.
> 
> Of course, my ISP isn't handing out more than a single IPv4 address by
> default, so all this has been simply a good learning experience.

For future reference, if you just want to join two ethernet interfaces on an 
openbsd box together you can use tpmr(4). It was almost called xcon(4), short 
for cross-connect.

It's also worth noting the steps taken by the Ethernet stack when it processes 
packets and which drivers can take packets at which point. Let's assume an 
ethernet packet is coming in on a physical interface, em0 in this case.

1: trunk/aggr processing

If em0 is part of trunk/aggr, then those drivers will steal the packet and 
start processing it again as if it was received on the relevant trunk/aggr 
interface.

2. service delimited packet filtering, ie, vlan/svlan handling

If em0 is a parent interface to vlan or svlan interfaces, this is when they get 
taken and processing starts again as if they were received on the virtual 
interfaces.

If no vlan/svlan interface is configured, the packets are marked as now marked 
as "service delimited".

3. bridge processing

This is where bridge/veb/tpmr can take a packet.

4. dropping service delimited packets

This is where vlan/svlan tagged packets are dropped that all the preceding 
aggr/trunk/vlan/svlan/bridge/veb/tpmr drivers declined. The exception is 
packets send to vlan 0, because vlan 0 isn't real and is only used to carry 
priority information on the wire for the native vlan.

This means that you can set up a bridge/veb/tpmr that forwards vlan tagged 
packets, but optionally slice specific vlans off for other processing by 
configuring a vlan interface with em0 as a parent to take those packets away 
first.

5. carp

If the destination address is for a carp interface on em0, it's at this point 
it's taken away.

6. Ethernet procotol handling

This is when the arp/ipv4/ipv6 protocols are checked and the packets are fed 
into the layer 3 stacks.




Re: X11 crashing

2023-10-05 Thread Ampie Niemand
On Thu, Oct 05, 2023 at 10:58:31AM -, Stuart Henderson wrote:
> On 2023-10-05, Maria Morisot  wrote:
> > I installed the patch for X11 (October 3rd), then rebooted,
> > now X is crashing every time I log in on xenodm,
> > sometimes I get a blue screen with debug messages,

Were you on the 7.3 Release? And did you patch with syspatch?

>
> If you show what those debug messages are (copy them down and type into
> an email), also collect dmesg - obviously you'll need to run without
> xfce to do that - that might give some clues. As things stand there is
> no information in this report that will help anyone figure it out.
>
> > other times I get a square on my screen with a black background,
> > and it is otherwise completely frozen, and I can't ctrl-alt-Fn
> > into a terminal. I can do this before I try logging in though,
> > and I tried reverting the patch but to no avail.
>
> At that point you're probably in ddb (kernel debugger).
> You can try blindly typing "boot r" and see if the system reboots.
> If so, you can try booting without X and see if the dmesg shows anything
> from the previous boot (which might include kernel error messages) above
> your normal boot dmesg.
>
>
> --
> Please keep replies on the mailing list.
>

At the bootprompt do "boot -s"
Enter on the "Enter pathname of shell or RETURN for sh" prompt
mount /
mount -a
swapon -a
rcctl disable xenodm
exit

Now log in and get the dmesg and the error that happens when you "rcctl -f 
start xenodm"

Regards
Ampie



Re: Registration

2023-10-05 Thread Ingo Schwarze
Hi Matti,

Matti Viljamaa wrote on Thu, Oct 05, 2023 at 03:05:37PM +0300:

> I mailed the MARC admins though.

I would like to kindly ask you to not cause extra work for people
who are providing a free public service.

> That is extremely bad design, because it's
> in essence a data mining resource for ad bots.

No.  In essence, that's a service that has been highly useful for
many *BSD projects and many other free software projects for a
very long time.

Yours,
  Ingo



Re: Registration

2023-10-05 Thread Ingo Schwarze
Hi Matti,

Matti Viljamaa wrote on Thu, Oct 05, 2023 at 02:46:54PM +0300:

> I got an answer to the query though in another mail.

Ah, OK.

> However, now I am concerned that I didn't want my email visible there.
> How can I delete that message?

You cannot.  When you post information to a public mailing list,
that information typically remains publicly visible for an indefinite
time.  That applies to most public mailing lists and is not specific
to OpenBSD.

Yours,
  Ingo



Re: Registration

2023-10-05 Thread Ingo Schwarze
Hi Matti,

Matti Viljamaa wrote on Thu, Oct 05, 2023 at 10:26:57AM +0300:

> I think I sent an user group registration request some time ago.
> I have not heard anything since.

The following search makes it seem likely that maybe you only intended
to send some information but actually didn't:

  https://marc.info/?a=16964913341=1

Perhaps resend your information to this list now?

Yours,
  Ingo



Re: rdiff-backup remotely

2023-10-05 Thread Daniele B.


Thanks Crystal,

I'm trying to use "rdiff-backup" saying to it please take my data on the
remote location via ssh and backup it on my local destination.

Preamble from the man:
rdiff-backup requires that the remote system accept ssh connections,
and that rdiff-backup is installed in the user's PATH on the remote
system.  For information on other options, see the section on REMOTE
OPERATION

Preamble from the web doc:
https://rdiff-backup.net/examples.html

I get that what I need to do is possible by this command:

rdiff-backup r...@microsoft.com::/home/bill/trojan/ /home/bill-backup

Established this the problem I got is a mismatch between
software versions, locally on 7.3 I own ver 2.0.5 and on the cloud
(linuz) I own a 2.2.2 (I'm talking of rdiff-backup).
The funny stuff is if I decided to install prev version of Linuz on my
cloud server I could get a match of versions... (2.2.2)

rdiff-backup reply me with with Pyhton error:
"Local version 2.0.5 does not match remote version 2.2.2"

Two doubts pop up:
1) Have I to always couple rdiff-backup versions between OpenBSD and
  Linuz ever also after system upgrades?
2) I see on 7.4 you are on rdiff-backup vers 2.2.5, this permit me
to remote my backup with ver 2.2.2 on the cloud? 
Eh-Eh-Eh.. (there is to laugh and lolly here..)

And, to reply you, rdiff-backup let me do incremental backups of data
with a certain gain in "network traffic" output along the way..
Almost this should be what promised..

Indeed I'm very happy with rdiff-backup locally since years, a little
surprised of this endeavor going remotely.. 

-- Daniele Bonini


Crystal Kolipe  wrote:

> It's not really clear what you are talking about.
> 
> I think what you are saying is that you usually use rdiff for backup,
> but you want to perform an additional backup to local media because
> you are moving from one hosting provider to another and there is a
> possiblilty that something might go wrong.
> 
> In that case, since you'll be doing a full, (non-incremental), backup
> anyway, just do it the simple way - use /bin/pax, and download the
> archive your local machine over sftp afterwards.
> 
> On Thu, Oct 05, 2023 at 05:42:35AM +0200, Daniele B. wrote:
> > 
> > I found the fact that I'm running different versions between
> > localhost and remote host (2.2.2) gives some deep scratches to
> > rdiff-backup that stops to run almost immediately.
> > 
> > Do you suggest to wait for 7.4 and retry? other thoughts?
> > 
> > 
> > "Daniele B."  wrote:
> > 
> > > Hello,
> > > 
> > > I moving on the cloud between providers and I have been suggested
> > > maybe correctly to backup my little cloud stuff also manually.
> > > 
> > > I'm stick on rdiff-backup and I would like to try it also
> > > remotely via ssh. I have not clue how to do it yet so I'm here to
> > > ask if anyone has already experienced the thing, if it is secure
> > > ( I see from the man that there are some concerns ) and
> > > eventually practicable via.
> > > 
> > > Thanks!
> > > 
> > > -- Daniele Bonini 
> > 



Re: X11 crashing

2023-10-05 Thread Stuart Henderson
On 2023-10-05, Maria Morisot  wrote:
> I installed the patch for X11 (October 3rd), then rebooted,
> now X is crashing every time I log in on xenodm,
> sometimes I get a blue screen with debug messages,

If you show what those debug messages are (copy them down and type into
an email), also collect dmesg - obviously you'll need to run without
xfce to do that - that might give some clues. As things stand there is
no information in this report that will help anyone figure it out.

> other times I get a square on my screen with a black background,
> and it is otherwise completely frozen, and I can't ctrl-alt-Fn
> into a terminal. I can do this before I try logging in though,
> and I tried reverting the patch but to no avail.

At that point you're probably in ddb (kernel debugger).
You can try blindly typing "boot r" and see if the system reboots.
If so, you can try booting without X and see if the dmesg shows anything
from the previous boot (which might include kernel error messages) above
your normal boot dmesg.


-- 
Please keep replies on the mailing list.



Re: rdiff-backup remotely

2023-10-05 Thread Crystal Kolipe
It's not really clear what you are talking about.

I think what you are saying is that you usually use rdiff for backup, but
you want to perform an additional backup to local media because you are
moving from one hosting provider to another and there is a possiblilty that
something might go wrong.

In that case, since you'll be doing a full, (non-incremental), backup
anyway, just do it the simple way - use /bin/pax, and download the archive
your local machine over sftp afterwards.

On Thu, Oct 05, 2023 at 05:42:35AM +0200, Daniele B. wrote:
> 
> I found the fact that I'm running different versions between localhost
> and remote host (2.2.2) gives some deep scratches to rdiff-backup that
> stops to run almost immediately.
> 
> Do you suggest to wait for 7.4 and retry? other thoughts?
> 
> 
> "Daniele B."  wrote:
> 
> > Hello,
> > 
> > I moving on the cloud between providers and I have been suggested
> > maybe correctly to backup my little cloud stuff also manually.
> > 
> > I'm stick on rdiff-backup and I would like to try it also remotely via
> > ssh. I have not clue how to do it yet so I'm here to ask if anyone has
> > already experienced the thing, if it is secure ( I see from the man
> > that there are some concerns ) and eventually practicable via.
> > 
> > Thanks!
> > 
> > -- Daniele Bonini 
> 



Re: groups new

2023-10-05 Thread Matti
Okay, thank you for your suggestion.

-M

to 5. lokak. 2023 klo 10.49 Janne Johansson (icepic...@gmail.com) kirjoitti:

> Den tors 5 okt. 2023 kl 09:43 skrev Matti :
>
>> It's not official, and I am trying to gain visibility by having it on the
>> openbsd site. I am the first member.
>>
>
> Perhaps try to help getting the HelBUG restarted again, there should be
> some people there who like BSD.
>
> http://helbug.fi/
> https://twitter.com/helbsdusergroup
>
> --
> May the most significant bit of your life be positive.
>


Re: groups new

2023-10-05 Thread Janne Johansson
Den tors 5 okt. 2023 kl 09:43 skrev Matti :

> It's not official, and I am trying to gain visibility by having it on the
> openbsd site. I am the first member.
>

Perhaps try to help getting the HelBUG restarted again, there should be
some people there who like BSD.

http://helbug.fi/
https://twitter.com/helbsdusergroup

-- 
May the most significant bit of your life be positive.


Re: groups new

2023-10-05 Thread Matti
It's not official, and I am trying to gain visibility by having it on the
openbsd site. I am the first member.

BR,

Matti

pe 22. syysk. 2023 klo 15.29 Ingo Schwarze (schwa...@usta.de) kirjoitti:

> Hi Matti,
>
> Matti wrote on Sun, Sep 17, 2023 at 04:14:55PM +0100:
>
> > 0
> > C Finland
> > P Uusimaa
> > T Helsinki
> > F None
> > O Finnish OpenBSD Users Group
> > I None
> > M membership.f...@gmail.com
> > U None
> > N *BSD
>
> so far, i failed to find any evidence that such a group actually exists.
> Can anybody provide pointers to such evidence?
>
> Thanks,
>   Ingo
>


Registration

2023-10-05 Thread Matti Viljamaa
Dear Recipient,

I think I sent an user group registration request some time ago. I have not
heard anything since.

Best Regards,

Matti


X11 crashing

2023-10-05 Thread Maria Morisot
I installed the patch for X11 (October 3rd), then rebooted,
now X is crashing every time I log in on xenodm,
sometimes I get a blue screen with debug messages,
other times I get a square on my screen with a black background,
and it is otherwise completely frozen, and I can't ctrl-alt-Fn
into a terminal. I can do this before I try logging in though,
and I tried reverting the patch but to no avail.

My wm is xfce, and when I remove my .xsession
everything works normal without crashing.

I'm far from a novice user but I don't know much about
how to properly report issues or what steps I need to take
to isolate where the problem is.