Re: Meaning of file flags

On mag 23 7:56, Greg Troxel wrote: > I just pulled out "The Design and Implementation of the 4.4BSD Operating > System". It talks about immutable, append-only, and nodump on page 263. > There is no mention of "archive". [...] I can not give much contribution to this, but thank you so much for yo

Re: Meaning of file flags

First of all, thanks to both for your help. The meaning of nodump is clear now. On mag 22 18:45, Jan Schaumann wrote: > > Does the attached diff help? Yes! I still have a couple of doubts. The difference between "system flag" and "user flag". The former can be applied by the super-user and the l

Meaning of file flags

Hello! In a recent and very interesting thread here, file flags are mentioned. Manpage chflags(1) shows their list. But what about their meaning? I've found this old message: where short descriptions of flags are shown. However,

Re: Assembly example (nasm) for amd64 in NetBSD

On apr 14 12:10, RVP wrote: [...] > > No, the stuff in /usr/pkg/share/doc/nasm. > > HTH, Thank you so much for all the clarifications: they solved my doubts and they definitely have been a huge help. Rocky

Re: Assembly example (nasm) for amd64 in NetBSD

On apr 14 8:40, RVP wrote: > > Ah, the `version' should be int32 not int64. Even if this is intended to be amd64 code, built as `nasm -f elf64'? IIUC, you replaced `db' (``define byte'') and `dq' (``define quadword'', that should be 8 bytes) with `dd' (``define double word'', that is 4 bytes, 32

Re: Assembly example (nasm) for amd64 in NetBSD

On apr 13 21:25, Jason Mitchell wrote: > Rocky, > > The error means that the executable can't run on the CPU you have. Definitely > NOT bad code. Running "ldd testcpu.o" might give you more of a idea of what's > wrong. > > HTH, > > Jason M. The error it gives is $ ldd testcpu.o ldd: testcpu.

Re: Assembly example (nasm) for amd64 in NetBSD

On apr 14 1:46, RVP wrote: > > Try adding a ".note.netbsd.ident" section: > > ``` > $ diff -u testcpu.s.orig testcpu.s > --- testcpu.s.orig2023-04-14 01:42:08.984238899 + > +++ testcpu.s 2023-04-14 01:41:06.204866303 + > @@ -23,3 +23,11 @@ > mov rax, 1 > mov rbx, 0 > s

Assembly example (nasm) for amd64 in NetBSD

Hello! I was looking for a simple assembly code, a `Hello world' for example, which runs on NetBSD, written and compiled with nasm. I tried a code to print the CPU vendor string through cpuid: the entire code is copied after the text of this e-mail. It works on FreeBSD. On NetBSD 9.0 I built it wit

Re: Option -p in apropos(1)

On giu 03 21:35, David H. Gutteridge wrote: > This (along with other fixes) has now been pulled up to the netbsd-9 > branch, so the next releng build of 9.2_STABLE will include it. Great! Thank you :) Rocky

Re: Option -p in apropos(1)

On mag 16 21:51, David H. Gutteridge wrote: > It does accept $PAGER as a definition of what tool to use for the > purpose, though that wasn't documented in the apropos(1) man page. I > just added it. FTR, for some reason in my default env(1) variable PAGER is not set: it is empty. However, if (for

Re: Option -p in apropos(1)

On mag 16 20:33, RVP wrote: > > apropos should call pclose(). Please try this patch below: > I added the line in my repository sourcecode. Building a kernel is straightforward, but what about this case? How to build and use apropos from the sourcecode? Rocky

Re: Option -p in apropos(1)

On mag 16 21:05, Steffen Nurpmeso wrote: > > I have no idea but does the program combo honour $LESS Sorry, I can understand what you are meaning. Variable $LESS in my shell appears to be empty. > does it contain use of alternate screen and quit-at-eof? I don't know how to verify this. > What d

Re: Option -p in apropos(1)

On mag 16 18:11, Rocky Hotas wrote: > > Am I doing something wrong? Some very funny updates. First, I'm on NetBSD 9.2 amd64 (but I also tested the same things in another machine with NetBSD 9.0 amd64). The first time I run `apropos' with option `-p', it doesn't work (

Option -p in apropos(1)

Hello! I was trying to run apropos(1) with option -p. According to the man page, it should -p Turn on pager formatting, and pipe the results through a pager (defaulting to more(1)). Pager formatting is enabled by default (so, it doesn't need neither option -p, nor option -

Re: Documentation portal schedule

On dic 11 11:03, Sergio Carlavilla wrote: > Hi again, > > Sorry, I used my personal account instead of the FreeBSD account. > > Finally I made only one commit with all the new documentation portal. > > So the new schedule it's: > > 1º 11:00 am - Spanish time. Make the commit with the new Docum

Re: FreeBSD Documentation Portal status and review request

On dic 04 0:30, Sergio Carlavilla wrote: > Hi to all and thanks for your feedback :) Hi :)! > Rocky Hotas: > > > - A dark theme would be very useful (and also very cool!). > > Just uploaded, also a high contrast theme too. Take a look and let me > know your toughts :)

Re: FreeBSD Documentation Portal status and review request

On nov 23 1:07, Pau Amma wrote: [...] > I haven't looked at it yet, but I need high-contrast and I'm sure others do. > If you or someone need lower contrast (see above, photophobia), maybe a > separate theme for that? (I have no idea how much work goes into creating > one, so feel free to ignore

Re: FreeBSD Documentation Portal status and review request

On nov 21 17:31, Sergio Carlavilla wrote: [...] > For example a local search using Algolia[2] as Hugo[3] or > AsciiDoctor[4] does. Algolia provides a free version for Open Source > projects[5]. > And the dark theme. > > Apart from that, you can see the new Documentation Portal here[6]. First, t

mdoc macro to mention packages in manpages

Hello! It seems that the current manpages do not use a standard, uniform way to mention a package/port name. I'm not very skilled about mdoc(7), but after some `zgrep' in /usr/share/man/man* (as suggested in par. `10.3.5. Important Macros' in the Handbook), I found several different solutions. De

Re: Use make to only build new files in the documentation

On nov 14 16:14, Jindong Li wrote: > hmm guys i'm kind of new to this, if I was going to apply this change > (since it appears already committed?), what would I need to do? :) I'm not sure I understood what you mean. Did you modify a file of the documentation in your local repository? If this is t

Re: Use make to only build new files in the documentation

On nov 14 19:46, Sergio Carlavilla wrote: > > Hi Rocky, > > You have two options here. > > First option is to build the documentation only with one language. > For example, to build only the english language use: > > make run DOC_LANG="en" > > In the second option you can go to the folder of t

Use make to only build new files in the documentation

Hello! Chapter 5 of the ``FreeBSD Documentation Project Primer for New Contributors'' shows how to build documentation: I tried several consecutive times to run `make' for the `documentation' (not the `website'), but each time it builds a

Re: sysctl and screen brightness

On set 10 10:39, Benny Siegert wrote: > It depends on what the exact machine is. Try looking through the > output of "sysctl hw" or "sysctl machdep" for options with > "brightness", "backlight", or similar in their names. I have (in a laptop) 000:02:0: Intel Sandy Bridge (mobile) GT2 Integrated G

A proposal for code explanation sessions

Hello! During this year's NetBSD Annual General Meeting on IRC (May 22nd), several participants suggested the activation of some code tutorial sessions performed by the developers. NetBSD sourcecode is in fact still a mysterious place for the new users, or just for those who read it for the first

System bootstrap and process with pid 0

Hello! In this book (Sec. 11.1, p. 239) it is stated that ``After bootstrap, the system initialization is started in main function of sys/kern/init_main.c'', which creates a process with pid 0 (as specified in the comments at the beginning of the function

Re: Some questions about build.sh, machine, -u and tools

Sorry if you are receiving this message for the second time. I can't see it in the ML, so I'm resending it. On mag 05 13:21, Martin Husemann wrote: > No, but you may have the choice wich kernel/userland you want to run > on the same physical hardware. An example is my cubietruck: > I run it big-e

Re: Some questions about build.sh, machine, -u and tools

Sorry if you are receiving this message for the second time. I can't see it in the ML, so I'm resending it. On mag 05 15:34, Valery Ushakov wrote: > Yes. It's just formatted using mdoc, but is not installed as part of > system manual pages. Ok! This is what produced that header. > I think Mart

Re: Some questions about build.sh, machine, -u and tools

On mag 05 13:21, Martin Husemann wrote: > No, but you may have the choice wich kernel/userland you want to run > on the same physical hardware. An example is my cubietruck: > I run it big-endian as: > > [~] martin@space-truckin > uname -p -m > evbarm earmv7hfeb > > but most people use exactly th

Re: Some questions about build.sh, machine, -u and tools

On mag 05 15:34, Valery Ushakov wrote: > Yes. It's just formatted using mdoc, but is not installed as part of > system manual pages. Ok! This is what produced that header. > I think Martin explained it pretty well in another followup. Yes, it was very useful :) > If by the "directory tools" y

Re: Some questions about build.sh, machine, -u and tools

For some reason, my messages are not delivered to this ML. I try to merge them into a single reply both for Martin and Valery, from another address. I apologize for any inconvenience and/or double messages you may have received. Part 1 On mag 05 13:21, Martin Husemann wrote: > No, but you may h

Re: Some questions about build.sh, machine, -u and tools

On mag 05 11:13, Martin Husemann wrote: > A MACHINE is a concrete thing, it belongs to a broader group of similar > (but not identical) other machines of the same MACHINE_ARCH. Ok! So, the reference and the "glue" is not MACHINE (as I thought), but MACHINE_ARCH. This also explains what Greg was w

Re: Some questions about build.sh, machine, -u and tools

On mag 05 10:57, Rocky Hotas wrote: > There are two different kinds of tools: > > 1. > The ones in obj_dir/tools, which are the result of the building of > /usr/src/tools. [...] > 2. > The ones in obj_dir/tooldir.NetBSD-9.99.81-amd64, which are the actual > toolcha

Re: Some questions about build.sh, machine, -u and tools

th lower keys). Is this normal? > On Mon, May 03, 2021 at 12:18:54 +0200, Rocky Hotas wrote: > Roughly speaking MACHINE determines with kernel, bootloader, etc the > system uses. You can have multiple MACHINE_ARCH for the same MACHINE > when the machine can have different ABIs (e

Re: Some questions about build.sh, machine, -u and tools

According to the paper let's use the terms `build host', `host' and `target'. On mag 03 8:30, Greg Troxel wrote: > I keep forgetting this and having to page it in, but a big concept is > that you can share userland among systems built for the

Re: Possible incorrect observation in Chapter 32 of The NetBSD Guide

On mag 04 18:22, Christos Zoulas wrote: > > I just tried it and it rebuilt the tools for me... > > christos Yes, exactly. I've also found in /usr/src/BUILDING, as regards `kernel=kconf', that: ``This command does not imply the tools command; run the tools command first unless it is certain that

Possible incorrect observation in Chapter 32 of The NetBSD Guide

Hi again! In Section 32.4 of The NetBSD Guide, the following line is used for build.sh: ./build.sh -U -u -j2 -O ~/obj -m evbarm -a aarch64 kernel=MYKERNEL Then, it is explicitly mentioned: ``Notice that update

Some questions about build.sh, machine, -u and tools

Hello! Chapter 32 of The NetBSD Guide deals with Crosscompiling NetBSD with build.sh. 1. With `list-arch' the full list of the available machines and CPU types is shown, named respectively MACHINE and MACHINE_ARCH. Correct me if I'm wrong, MACHINE_ARCH represents the CPU with its specific instruct

Typo(s) in Chapter 32 of The NetBSD Guide

Hello! In Section 32.1 of The NetBSD Guide, consider the sentence: ``The "-a evbarm -m aarch64" options indicate we are building for a machine type of evbarm with a CPU type of aarch64''. `-m' and `-a' swapped. It should be

Again, gpio(4) error in GPIOREAD

Hello! I would also like to signal again this error, which has not been fixed yet. gpio(4), when dealing with GPIOREAD, states: ``Returns the input pin value in the gpio_pin_op structure'' but then it specifies the structure gpio_req. In src/sys/sys/gpio.h, in the comments to gpio_pin_op, it is

Re: skills to document the netbsd kernel?

> Sent: Tuesday, April 13, 2021 at 9:31 AM > From: "Mayuresh Kathe" > To: netbsd-users@netbsd.org > Subject: skills to document the netbsd kernel? Hello! > while i possess decent technical skills, i lack knowledge of > ansi-c which i believe would be a must to read the source of > the netbsd ker

Editors configuration with AsciiDoc?

Hello! In the current Documentation primer, the suggested configuration for Emacs seems to be still related to DocBook. The same for vim. I understand that this is a work-in-progress and that the transition to AsciiDoc is maybe

Re: libusb not working properly on 9.0/9.1

On gen 20 18:44, Greg Troxel wrote: > > I think libusb on NetBSD does not do async IO. Could that be it? Unfortunately I am not able to determine if this is relevant.

Re: libusb not working properly on 9.0/9.1

On gen 20 13:25, Craig Kulesa wrote: > > Hi Rocky, Hi Craig :)! I share the quotes from you message here, hoping that this does not bother you: I think it could be very useful for anyone interested. > I'm using libusb in NetBSD 9 and am not having trouble with it. But as > Manuel points out, I

libusb not working properly on 9.0/9.1

Hello! I would like to run this executable on NetBSD, but even on a supported hardware platform (Raspberry Pi 3 B+) it is unusable, due to libusb not properly working. I was using libusb1-1.0.24 from pkgsrc 2020Q4. As suggested here:

gpio(4), error in GPIOREAD

Hello! gpio(4), when dealing with GPIOREAD, states: ``Returns the input pin value in the gpio_pin_op structure'' but then it specifies the structure gpio_req. In src/sys/sys/gpio.h, in the comments to gpio_pin_op, it is considered as ``(old API)'' and, if just declared in a test C source file, t

Error in dmesg(8) for USB hub in Raspberry Pi 3 B+

Hello! In the dmesg, after the configuration of the on-board USB hubs, this line is printed in NetBSD 9.1: uhub0: autoconfiguration error: illegal enable change, port 1 The relevant parts of the dmesg are: [ 1.00] NetBSD 9.1 (GENERIC64) #0: Sun Oct 18 19:24:30 UTC 2020 [ 1.00] m

Re: GPIO programs for Raspberry Pi in Python and C

On gen 14 22:30, Rocky Hotas wrote: > > I never used ioctl(2) and maybe it's not immediate to integrate it with > gpio(4). If you have some piece of code performing even a trivial > operation like turning ON a pin, and you are OK with sharing it, it > would be welcome. It

Re: GPIO programs for Raspberry Pi in Python and C

Thanks to all for your very useful hints and suggestions. On gen 14 12:12, Greg Troxel wrote: > > Benny Siegert writes: > > > NetBSD uses the gpio(4) device to talk to the GPIO pins: > > http://man.netbsd.org/gpio.4 > > > It is really straightforward in C. I wrote a program to watch a pin and

GPIO programs for Raspberry Pi in Python and C

Hello! I successfully installed NetBSD 9.1 evbarm (arm64.img) on a Raspberry Pi 3 B+. In the Raspberry documentation, several example regarding the handling of GPIO pins are available as Python programs: https://www.raspberrypi.org/documentation/usage/gpio/python/README.md They use a module named

Re: Convention in the output of service rcvar

On dic 20 21:32, Valery Ushakov wrote: > I have committed the change (revision 1.106). We still refer to rc > variables with the dollar prefix in errors/warnings, but there the > context actually warrants it, kinda, so I decided to leave those > alone. It is reasonable and I definitely agree. T

Re: Convention in the output of service rcvar

On dic 17 21:12, David Holland wrote: > My guess: someone was thinking in perl by accident and nobody's > noticed it since, so it hasn't been fixed. It's probable, then. Thanks for your feedback, David and Jeremy. I would suggest, if possible and if you agree, to remove that extra `$' (hoping th

Re: Convention in the output of service rcvar

On dic 16 19:43, Rocky Hotas wrote: > > In FreeBSD, for example, the trailing `$' is absent. [...] > The trailing character `$' appears since the first revision where such a Sorry, I used the word "trailing", but I was meaning the opposite: the `$' at the beginning of the variable. Rocky

Convention in the output of service rcvar

Hello! Consider a service whose start-up is controlled by a variable in /etc/rc.conf: food=YES Then, the output of `service food rcvar' is: # food $food=YES I wonder why this choice has been made, instead of # food food=YES This second version would also reproduce the shell syntax. I do not k

Re: Block a single connection with npf

On dic 12 12:48, Greg Troxel wrote: > First, you are talking about "gateway" so I am guessing you have the > usual computer with two interfaces, one to your ISP with a single IPv4 > address and one that is your home LAN, where is is .1, does dhcp, and is > running npf. If not please explain. You

Re: Block a single connection with npf

On dic 12 17:13, Rocky Hotas wrote: > > group "internal" on $if_mylan { > pass in all > pass out all > > block stateful out family inet4 proto tcp from to > port 443 > } [... ] > Is the order of the rules wrong? Or something else?

Block a single connection with npf

Hello! In npf.conf(5), the group defining the rules for the LAN interface $if_mylan of my gateway is as follows: group "internal" on $if_mylan { pass in all pass out all block stateful out family inet4 proto tcp from to port 443 } I would like $if_mylan to be essential

Re: npf syntax: port ranges, negation of a condition, and map rules

On ott 29 10:16, Michael van Elst wrote: > The "port forwarding case" only handles single ports. You need > separate map commands for each port. After several errors, I was wondering in fact if this was the reason. Thanks for clarifying this! Rocky

Re: npf syntax: port ranges, negation of a condition, and map rules

On ott 28 12:22, Martin Husemann wrote: > There is an example in /usr/share/examples/npf/host-npf.conf: > > # Allow being tracerouted > pass in proto udp to any port 33434-33600 This is a single use (but thanks! I forgot this example file). My case is double, because I would like to map

npf syntax: port ranges, negation of a condition, and map rules

Hello! After browsing the available documentation for npf, I did not find any hints about some issues. 1) How to represent port ranges? I tried with beginning_port:end_port (which for example is used in OpenBSD's pf) beginning_port,end_port beginning_port-end_port $port_range = { beginning_port,

Re: altq filter acts before or after npf NAPT?

On ott 23 15:47, BERTRAND Joël wrote: > and altqd runs as expected. Only a few bugs. Don't try to launch > /etc/rc.d/altqd reload, altqd will take 100% of a CPU. Don't try to stop > altqd, you will obtain a kernel panic. Some updates: if altqd.conf has only a queing discipline per each interface,

Re: Use of disklabel, MBR and GPT

On ott 23 16:12, Bruce Lilly wrote: > On Fri, Oct 23, 2020 at 3:34 PM Martin Husemann wrote: > > > There is no point in ever using a disklabel on a disk that has a GPT. This is so important to know. The first time I used GPT I tried in any way to install a disklabel, too. Then, it became clear i

Re: Use of disklabel, MBR and GPT

On ott 22 11:48, Bruce Lilly wrote: > A few additional points: > > "disklabel" is a term used by all 3 of the major BSD variants > (FreeBSd, NetBSd, and OpenBSD), but > with signific

Re: altq filter acts before or after npf NAPT?

On ott 23 15:47, BERTRAND Joël wrote: > If I remember, altq is applied after npf. > My /etc/altqd.conf contains : > > legendre:[~] > cat /etc/altq.conf > #tbrconfig > interface wm0 bandwidth 8M priq > > class priq wm0 high_class NULL priority 1 > class priq wm0 low_class NULL priority 0 de

Re: altq filter acts before or after npf NAPT?

On ott 23 8:19, Greg Troxel wrote: > You should be aware that not that many people use altq. Yes, I was guessing this. > (I used to use > it heavily, even adding new queueing disciplines, but that was a very > long time ago.) The only important thing is if it's still a good tool for traffic sh

Re: 9.0/9.1 packages symlink for amd64/aarch64/i386 updated to 2020Q3

On ott 22 22:54, nia wrote: > hi, > > if you run pkgin upgrade and were using the standard set of 9.0 packages, > you will now be on 2020Q3 > > thanks, and sorry for the delay Thanks to you for this info. It's great! I'm upgrading. Rocky

altq filter acts before or after npf NAPT?

Hello! Consider a NetBSD 9.0 (release) system using both npf and altqd. This machine has two NICs and it is a gateway. First NIC is connected to a LAN, with multiple hosts, and second NIC is connected to the modem. With npf, the following is applied: map $if_second_nic dynamic $internal_lan -> $se

Re: npf, map and pass stateful out all

On ott 20 9:03, Greg Troxel wrote: > I am not an pf expert, but... Don't worry, me neither :). > > As it is written here, and exactly as Martin said in a previous > > thread, `pass stateful out all' ``allows the packet to go out, and > > also creates a NAT state entry so any answers are allowed

npf, map and pass stateful out all

Hello! Between the documentation about npf, another very useful document is: As it is written here, and exactly as Martin said in a previous thread, `pass stateful out all' ``allows the packet to go out, and also creates a NAT state entr

Re: Configure NetBSD as a gateway for LAN hosts

On ott 13 12:08, Martin Husemann wrote: > With above routing table this should already happen - no concrete local subnet > matching, so it will pick "default". Yes, I tried and it does! > > With a routing table > > entry, or with a rule (the `pass stateful out all' in soho_gw-npf.conf) > > in npf

Re: Use of disklabel, MBR and GPT

On ott 16 12:47, Greg Troxel wrote: > > - if you need the disk to be accessible from other systems, you need to > >use a partitioning scheme they understand. MBR works for DOS and older > >windows, GPT works for nearly everything newer. Disklabel only works > >for older Unix systems o

Re: Use of disklabel, MBR and GPT

On ott 16 12:52, Greg Troxel wrote: > > Obviously, disklabel creates custom partitions only in the portion of > > the disk which is related to NetBSD, the only one where it is intended [...] > This isn't really true. While the installer might only create > partitions within the NetBSD MBR partit

Re: Use of disklabel, MBR and GPT

On ott 16 19:44, Robert Elz wrote: > | Obviously, disklabel creates custom partitions only in the portion of > | the disk which is related to NetBSD, > > That's not correct, though if written as a "should create" it would > perhaps be good advice for most people. > > In NetBSD, the MBR is use

Re: Use of disklabel, MBR and GPT

On ott 16 12:03, Rocky Hotas wrote: > When the machine is booted with NetBSD, disklabel is the only way NetBSD > looks at the disk, the *entire* disk; MBR in this case is not considered > at all.

Re: Use of disklabel, MBR and GPT

On ott 16 12:25, Martin Husemann wrote: > I have a few clarifications... Thanks for writing them. > > Maybe this is trivial, but during the installation of NetBSD a > > disklabel is actually nested inside a primary MBR partition. > > This is true for some architectures (like amd64), but others d

Use of disklabel, MBR and GPT

Hello! After partitioning a new disk with MBR, creating two primary partitions, I was trying to define a disklabel in each of them. Quite soon I realized it was not possible. After an IRC conversation, which was very instructive yesterday, here are some considerations. An important premise is that

Re: Configure NetBSD as a gateway for LAN hosts

On ott 12 13:55, John Nemeth wrote: > This is a very common configuration, so there is lots of > documentation on the Internet about how to do it. For NetBSD in > particular, take a look at the Guide: > > http://www.netbsd.org/docs/guide/en/ > http://www.netbsd.org/docs/guide/en/part-net.ht

Re: Configure NetBSD as a gateway for LAN hosts

On ott 12 14:55, Jason Mitchell wrote: > You have a choice between routing and bridging. [...] > b) Do NAT/PAT so that the modem only sees traffic coming from the NIC > 2 network In case of routing, I would prefer this solution, because I would like the modem only sees traffic coming from the N

Configure NetBSD as a gateway for LAN hosts

Hello! Thanks to your suggestions for a NIC (in particular, thanks to Martin: Realtek worked), I configured a second NIC in a NetBSD 9.0 (release) machine. I would like to use it as a 1) gateway and 2) DHCP server, but didn't find much documentation as regards problem 1). Assume that the machine's

Re: Suggestions for a discrete NIC compatible with NetBSD 9.0

On ott 09 16:29, Martin Husemann wrote: > [...] > The others are all -current: > re0 at pci2 dev 0 function 0: RealTek 8168/8111 PCIe Gigabit Ethernet (rev. > 0x15) > re0: interrupting at msix3 vec 0 > re0: RTL8168H/8111H (0x5400) > re0: Ethernet address 70:4d:7b:66:23:a2 > re0: using 256 tx desc

Re: Suggestions for a discrete NIC compatible with NetBSD 9.0

On ott 08 12:59, Martin Husemann wrote: > Most random cheap PCIe cards that you can get are re(4) using a realtek > chipset and work well with NetBSD (in my experience). Thanks! I found almost only cards with some flavours of chip RTL8111: RTL8111E, RTL8111G, RTL8111H. re(4) mentions only 8111 (wi

Re: Suggestions for a discrete NIC compatible with NetBSD 9.0

On ott 08 13:40, Brad Spencer wrote: > > They were faster for gig than the Realtek stuff I tried. (To be fair, > > probably going back 10+ years though). > Yes, I agree the Intel Pro cards work pretty well.. I tend to pick up > used "Intel PRO/1000 PT (82571EB)", which are dual nics (probably se

Suggestions for a discrete NIC compatible with NetBSD 9.0

Hello! I am running NetBSD 9.0 (release) on a system with an integrated NIC, which is, from pcictl(8): Intel PCH LAN (82578DM) Controller (ethernet network, revision 0x05) It works. But I would like to add a network interface. Maybe some of you remember my recent issues with NICs: therefore, befo

Re: Unusable Realtek NIC after upgrading to NetBSD 9

Hi! Sorry for the huge delay. On set 18 15:48, Vincent DEFERT wrote: > Engrampa is the archive manager of MATE. Oh, ok, I used MATE only a couple of times and didn't remeber it. > The files besides the .bin have .exe, .dll and .sys suffixes, likely the > firmware update utility for Windows users

Re: Unusable Realtek NIC after upgrading to NetBSD 9

On set 17 13:13, Vincent DEFERT wrote: > I have extracted it using Engrampa and made a tgz archive with the files in > it. > You can download it here: http://defert.com/tmp/sp66770.tgz > > There's a .bin file in it, I think it's all you need on your USB stick. Thanks, I didn't know Engrampa. I'm

Re: Unusable Realtek NIC after upgrading to NetBSD 9

On set 17 11:19, Martin Husemann wrote: > The ACPI component in the kernel is newer, so it might trigger different > bugs in the ACPI parts of your firmware. Got it (and it absolutely makes sense). Is sounds like something which is difficult to isolate and identify.

Re: Unusable Realtek NIC after upgrading to NetBSD 9

On set 17 19:03, SAITOH Masanobu wrote: > I think it would be worth to try the following change: I tried. Modified src/sys/dev/ic/rtl8169.c as suggested, then rebuilt the 9.0-RELEASE kernel. Unfortunately the problem is still the same. Here is the new dmesg: https://termbin.com/qszzr Thank you

Re: Unusable Realtek NIC after upgrading to NetBSD 9

On set 16 22:50, Rocky Hotas wrote: > Full dmesg from current (9.99.72) kernel: > > https://termbin.com/uhaa Sorry, of course this was from 9.0 (formal release) kernel. If you also need dmesg from 9.99.72, let me know. Rocky

Re: Unusable Realtek NIC after upgrading to NetBSD 9

On set 17 8:55, Vincent DEFERT wrote: > You could try opening the firmware update's executable as an archive > (they are often SFX - self-extracting ZIP archives), > extract its contents to a FAT-formatted USB pen drive, > reboot the laptop with the pen drive attached > and enter the BIOS firmware

Re: Unusable Realtek NIC after upgrading to NetBSD 9

On set 16 12:22, Martin Husemann wrote: > Can you please provide full dmesg, and output and from > > pcictl dump -b 3 -d 0 -f 0 Full dmesg from 8.1 kernel: https://termbin.com/t57g Full dmesg from current (9.99.72) kernel: https://termbin.com/uhaa Output of `pcictl pci0 dump -b 3 -d 0 -

Re: Unusable Realtek NIC after upgrading to NetBSD 9

On set 15 14:18, Greg Troxel wrote: > > I suspect MSI vs MSI-X is the big deal. As in the message to Martin, yes, I have the same suspect.

Re: Unusable Realtek NIC after upgrading to NetBSD 9

On set 15 17:37, Martin Husemann wrote: > Good point, can you try disabling rlphy in your kernel config? As in my first message: [With 9.0] ``I also tried to boot disabling rlphy(4) (`userconf disable rlphy' from the boot prompt), and ukphy(4) is used instead, but nothing changed. The same happe

Re: Unusable Realtek NIC after upgrading to NetBSD 9

Hello! Sorry, I wasn't able to read this message till now, for some (recurring) issues with this e-mail address (this is why I sometimes use rockyho...@post.com instead). On set 11 9:33, Greg Troxel wrote: > It sounds like the only issue is the re0 card, and everything else is > ok. If that's n

Re: Unusable Realtek NIC after upgrading to NetBSD 9

Hi! > Sent: Sunday, September 13, 2020 at 8:28 PM > From: "Martin Husemann" > To: "Rocky Hotas" > Cc: "Valery Ushakov" , "NetBSD Users Mailing List" > > Subject: Re: Unusable Realtek NIC after upgrading to NetBSD 9 ... > With the

Re: Unusable Realtek NIC after upgrading to NetBSD 9

Hello!  Sent: Sunday, September 13, 2020 at 8:50 AM From: "Clay Daniels" To: "Valery Ushakov" Cc: netbsd-users@netbsd.org Subject: Re: Unusable Realtek NIC after upgrading to NetBSD 9 > I would highly recommend the 9.0 Stable snapshot at: > http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/late

Re: Unusable Realtek NIC after upgrading to NetBSD 9

Hello Valery, > Sent: Friday, September 11, 2020 at 9:37 PM > From: "Valery Ushakov" > To: netbsd-users@netbsd.org > Subject: Re: Unusable Realtek NIC after upgrading to NetBSD 9 ... > Data point. I had something that looked similar enough to this with > my USL-5p (landisk) > > re0 at pci0 dev 0

Unusable Realtek NIC after upgrading to NetBSD 9

Hello! Using NetBSD 8.1 in a laptop, both its Ethernet and WiFi NICs worked. Then, I made a NetBSD 9 (formal release) fresh install and the Ethernet NIC is almost unusable. Here, the relevant dmesg part: [ 1.055234] re0 at pci3 dev 0 function 0: RealTek 8100E/8101E/8102E/8102EL PCIe 10/100Bas

Re: Use network printer from NetBSD

On giu 27 9:02, Brett Lymn wrote: > what if you try: > > telnet printerip 9100 > > then enter > > test > > followed by control-m control-j control-l > > that should do a carriage return, newline, new page resulting in a page > coming out > of the printer. It does! A new blank page is "pr

Re: Use network printer from NetBSD

Hi! I'm really sorry for the delay. Partly because of work, partly because I got lost between the messages and the suggested tests. Apparently printers are still an unexplored world for me! On lug 04 12:33, MLH wrote: > https://support.brother.com/g/s/id/htmldoc/mfc/cv_mfc9120cn/us/html/sug/chapte

Re: Use network printer from NetBSD

Hi! As in my reply a couple of minutes ago, sorry for the huge delay. On lug 04 13:35, Greg A. Woods wrote: > There's one other way to possibly find out at least what command > languages your printer understands (besides obviously understanding > Brother's variant of PJL): > >snmpwalk -c publ

Re: Use network printer from NetBSD

(re-send attempt after network fail) On lug 03 15:45, Johnny Billquist wrote: > I think Brett was also hoping that the page that came out would have the > text "test" written on it. Probably in the top left corner, with some > reasonable size and font. > > But it sounds as if you did not get suc

  1   2   3   >