How to raise iwm0?

2023-11-19 Thread Lizbeth Mutterhunt, Ph.D
As axen0 fails to connect, I want to try the wlan0, but  it won’t  be able to 
make a wlan0. I can’t find the iwm module in kernel config. Does it be named 
differently (I’ve got it from FreeBSD) or is just the hardware bad. I mean it’s 
unsupported, because I killed a Chromebook to an EFI machine. It’s a Gemini 
Lake.

Any ideas?

Lizbeth

Wenn einem gar niets  meer einfällt, schreit man auch nix. Mijn mute reminder!

Re: sys/dev/usb/if_axen.c

2023-11-13 Thread Lizbeth Mutterhunt, Ph.D
I have the same problem with this Ethernet adapter! Getting a buffer problem, 
as notebook doesn’t have ether, I use the axen0, but still no net!


Wenn einem gar niets  meer einfällt, schreit man auch nix. Mijn mute reminder!

> Op 13.11.2023 om 13:30 heeft Makoto Fujiwara  het volgende 
> geschreven:
> 
> Hi,
> I have following device:
>  -
>  axen0 at uhub3 port 1
>  axen0: ASIX (0x0b95) AX88179A (0x1790), rev 2.10/2.00, addr 3
>  axen0: AX88179
>  ukphy0 at axen0 phy 3: OUI 0x00e038, model 0x0006, rev. 1
>  ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto
>  axen0: Ethernet address 
>  -
> And running 10.99.10,
> it emits following lines
> 
>  Nov 13 20:24:54 beebox-03 /netbsd: [ 154.8236912] axen0: autoconfiguration 
> error: invalid buffer(pkt#1), continue
> 
> I put simple checking line as:
> 
> ---
> diff --git a/sys/dev/usb/if_axen.c b/sys/dev/usb/if_axen.c
> index 423a87e5c541..6215db354c90 100644
> --- a/sys/dev/usb/if_axen.c
> +++ b/sys/dev/usb/if_axen.c
> @@ -793,6 +793,8 @@ axen_uno_rx_loop(struct usbnet *un, struct usbnet_chain 
> *c, uint32_t total_len)
>if ((buf[0] != 0xee) || (buf[1] != 0xee)) {
>aprint_error_dev(un->un_dev,
>"invalid buffer(pkt#%d), continue\n", pkt_count);
> +aprint_error_dev(un->un_dev,
> +"%04d %02x %02x\n", __LINE__, buf[0], buf[1]);
>if_statadd(ifp, if_ierrors, pkt_count);
>return;
>}
> ---
> 
> and then the lines show:
> 
> Nov 13 20:25:03 beebox-03 /netbsd: [ 163.6740410] axen0: autoconfiguration 
> error: invalid buffer(pkt#1), continue
> Nov 13 20:25:03 beebox-03 /netbsd: [ 163.6740410] axen0: autoconfiguration 
> error: 0797 00 08
> 
> so buf[0]:buf[1] expected 0x is 0x0008.
> 
> I've compared to openbsd: if_axen.c
>   https://raw.githubusercontent.com/openbsd/src/master/sys/dev/usb/if_axen.c
> to N, and there are so many differencies.
> 
> Does this (N) if_axen.c works on any installation ?
> 
> Also, I've prepared GENERIC-axen with following conf:
>  ---
>  include "arch/amd64/conf/GENERIC"
>  options AXEN_DEBUG
>  options MSGBUFSIZE=131072
>  ---
> but No debug lines appears, please let me know what is wrong,
> thanks
> --
> Makoto Fujiwara
> m...@netbsd.org
> mak...@if.t.u-tokyo.ac.jp
> Key fingerprint = 0BFA FAEB EAD1 90BA 7498  8F85 6809 9E0B B7EF A12E
> 
> pkgsrc freshness:
> http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html


axen0 - invalid buffer(pkt#1), continue

2023-08-12 Thread Lizbeth Mutterhunt, Ph.D
…is what I get on a Gemini lake Chromebook, wlan is dead, no interfaces, so 
adapter eth0.

Results with dhcpcd axen0 in reference to beginning. Unsupported?

Chill on!

Lizbeth

Wenn einem gar niets  meer einfällt, schreit man auch nix. Mijn mute reminder! 

axen0 - invalid buffer(pkt#1), continue

2023-08-12 Thread Lizbeth Mutterhunt, Ph.D
…is what I get on a Gemini lake Chromebook, wlan is dead, no interfaces, so 
adapter eth0.

Results with dhcpcd axen0 in reference to beginning. Unsupported?

Chill on!

Lizbeth

Wenn einem gar niets  meer einfällt, schreit man auch nix. Mijn mute reminder!

Wenn einem gar niets  meer einfällt, schreit man auch nix. Mijn mute reminder!

axen0 - invalid buffer(pkt#1), continue

2023-08-12 Thread Lizbeth Mutterhunt, Ph.D
…is what I get on a Gemini lake Chromebook, wlan is dead, no interfaces, so 
adapter eth0.

Results with dhcpcd axen0 in reference to beginning. Unsupported?

Chill on!

Lizbeth

Wenn einem gar niets  meer einfällt, schreit man auch nix. Mijn mute reminder!

Wenn einem gar niets  meer einfällt, schreit man auch nix. Mijn mute reminder!

axen0 - invalid buffer(pkt#1), continue

2023-08-12 Thread Lizbeth Mutterhunt, Ph.D
…is what I get on a Gemini lake Chromebook, wlan is dead, no interfaces, so 
adapter eth0.

Results with dhcpcd axen0 in reference to beginning. Unsupported?

Chill on!

Lizbeth

Wenn einem gar niets  meer einfällt, schreit man auch nix. Mijn mute reminder!

axen0 - invalid buffer(pkt#1), continue

2023-08-11 Thread Lizbeth Mutterhunt, Ph.D
…is what I get on a Gemini lake Chromebook, wlan is dead, no interfaces, so 
adapter eth0.

Results with dhcpcd axen0 in reference to beginning. Unsupported? 

Chill on!

Lizbeth




Wenn einem gar niets  meer einfällt, schreit man auch nix. Mijn mute reminder!

Troubles makeing distribution

2022-11-27 Thread Lizbeth Mutterhunt, Ph.D
No matter I try, if I use ./build./sh I get a compile/install error at @ 
“liblua””

Are there any source upgrades necessary or some ports to be built in the 
beginning.


I use a virtual machine within a Hackintosh Ventura as building platform, 
anything to do with the script?


Liza, thx for help, 

Installation of liblua fails

2022-11-14 Thread Lizbeth Mutterhunt, Ph.D
Hi, 

My attempt: as NetBSD won’t boot from stick or even ISO (neauveu can’t 
initialise X server), I thought, I do a virtual machine distribution built and 
it ends up in install liblua {Error 1}; no hint, nothing. 

What to do?

Liz

Re: build-success/install-fault on i486 with xsrc

2020-11-01 Thread Lizbeth Mutterhunt, Ph.D
so!

sucess in the built! had a hung-up at the latest test:

_nv_cas.d.tmp atomic_or_64_nv_cas.d
: fatal error: when writing output to : No space left on device

but /tmp was empty and there were 4,5GB free. Damn old drag, did this
business! now gonna to do some emulation for rooting mobile.

thx and good luck in BSDing,

miranda




2020-10-29 0:56 GMT+01:00, m...@netbsd.org :
> On Wed, Oct 28, 2020 at 09:37:27PM +0100, Lizbeth Mutterhunt, Ph.D wrote:
>> On Wed, Oct 28, 2020, 21:15  wrote:
>>
>> > On Tue, Oct 27, 2020 at 10:57:28PM +0100, Miranda van den Breukelingen
>> > wrote:
>> > > as driving to current the dell vostro 14 compiled 22 hours on the
>> > userland and
>> > > 28 hours on the xsrc: no build-failure with the kernel, too.
>> > >
>> > > installed it with ./build.sh -u -U install=/ I get a fine install but
>> > > on
>> > > postinstall it tells me /usr/src/sbin/postinstall/postinstall is not
>> > > available. I checked and fixed it manually with the new build
>> > postinstall; so
>> > > no comment.
>> > >
>> > > after reboot with the new kernel I have problems with the X-driver;
>> > > Doing an X -configure brings me:
>> > >
>> > > libGL.so.3 text relocations
>> > > libGL.so3 cannot write enable text sements: permission deniend
>> > >
>> > > same with xinit and startx (exec xfce4-session in .xinitrc)
>> > >
>> > > it's llvm10; I 'chmod 777 /dev/dri/card*' and rebuild
>> > > xorg-server-libs;
>> > no
>> > > success. do I need compiler FLAGS for the xsrc with the
>> > postinstall-problem,
>> > > too? does compiling with CLANG help?
>> > >
>> > > miranda
>> > >
>> > >
>> >
>> > Hi miranda,
>> >
>> > You can revert this patch to avoid the problem:
>> > https://v4.freshbsd.org/commit/netbsd/src/MTYAsnu9Fcy3KioC
>> >
>> > I have reported a bug for this:
>> > http://gnats.netbsd.org/55762
>>
>>
>>
>>
>> Hi Maya,
>>
>> openBSD doesn't find root device at install,  so back to a fresh install.
>>
>> First: xsrc,  second src amd prop up the kernel.  Will take 2-3 days,
>> applying the patches and let X11_TYPE=modular in mk.conf.
>>
>> Will explain afterwards with bopefully not a bundge-eating CPU,  still
>> caughting,  so,  not so manx heating -costs here,  when you touch the
>> TAB-key,  you'll light up in a warm underground!  :-)
>>
>> Thx for help and report!
>>
>> Mirand
>>
>>
>> >
>
> This patch is only in netbsd-current, so if you use 9.1 and the binaries
> that came with it it won't have this problem. No need to build anything
> from scratch!
>
> X11_TYPE=modular will build a mesalib in pkgsrc that also has this
> problem.
>


build success / xsrc

2020-10-30 Thread Lizbeth Mutterhunt, Ph.D
after 27 hours of compiling (I call it bindge eating) I get after
'install=/' a full working system with the newest X-src! Was 3 times
at an free discspace of 0 and I had to delete the whole pkgsrc-tree
for writing down to ssd but no abort.

the problem with the 'sysctl -w security.pax.mprotect.enabled=0'
remains but I know thx to maya how to solve it. The patch has been
already given into the sources as well as in the pkgsrc xorg-modular.

The postinstall check/fix command had to be done manually here as well
as rm'ing the output after install and I avoid the etcupdate-command.

probs at startup: no dhcpcd although giving gateway and the 'dhcpcd
-qM iwn0' at /etc/rc.conf and this strange virecorver that gives me
'mail_queue_enter: maildrop/10091.577 no such file or directory and
the amd automounter doesn't as well.


X -version:

/usr/X11R7/lib/libGL.so.3: text relocations
/usr/X11R7/lib/libglapi.so.1: text relocations

X.Org X Server 1.20.6
X Protocol Version 11, Revision 0
Build Operating System: NetBSD/i386 9.99.74 - The NetBSD Foundation, Inc.
Current Operating System: NetBSD netBSD 9.99.74 NetBSD 9.99.74
(LIZBETH-$Revision: 1.1233 $) #2: Tue Oct 27 21:12:39 CET 2020
root@localhost:/usr/obj/sys/arch/i386/compile/MIRANDA i386
Build Date: 23 February 2020  07:11:23AM


Gotta do the src-build now! Cross fingers for success!

miranda