]
[ 231626.968453] iwm0: autoconfiguration error: unhandled firmware
response 0x93d7 0xd7/0x250ac7a3 rx ring 45[159]
[ 231636.088445] iwm0: autoconfiguration error: unhandled firmware
response 0x 0xff/0x80 rx ring 127[255]
they seem to be related to network activity.
Any ideas?
--
Brett Lymn
--
Sent from
=5, smaxy=0, smaxx=78)
> at /usr/src/lib/libcurses/refresh.c:511
> 511 pad->pbegy = pbegy;
> (gdb) bt
> #0 prefresh (pad=0x0, pbegy=0, pbegx=0, sbegy=1, sbegx=5, smaxy=0, smaxx=78)
> at /usr/src/lib/libcurses/refresh.c:511
Pad being NULL is a Bad Thing. That
On Wed, Nov 29, 2023 at 09:25:31AM +0100, Frank Kardel wrote:
>
> As you said a "couple of years ago" I assume those CPUs where not
> Zen4-architecture.
>
Ah, yes, I should have checked better, it would have been a milan cpu so
a Zen3.
--
Brett Lymn
--
Sent from
ne, the only bummer is the
server I had contained an unsupported raid controller so I couldn't see
the disks at all.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
On Fri, Jul 07, 2023 at 04:37:12PM +0930, Brett Lymn wrote:
>
>
> I updated to -current a couple of weeks ago and I am now having issues with
> the builtin X.
>
I dove into trying to work out what was wrong head first. I dug around and
found an intel
document that lis
e a bunch of ascii
sucrad or usrcda if the bytes are swapped.
It may be nothing though...
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
lipped through the cracks, there do seem to be quite
a few work arounds for gpu hangs.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
/pub/NetBSD/misc/blymn/dmesg.capture-errors
Has anyone any hints I can try?
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
On Sun, Mar 05, 2023 at 03:01:02PM -, Michael van Elst wrote:
>
> - if (guid != NULL && len == 16)
> + if (guid == NULL || len == 16)
> +
Shouldn't that be "len != 16"?
--
Brett Lymn
--
Sent from my NetBSD device.
"We are
d
provide the output. If the trackpad is probed then what does does not work
mean?
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
On Wed, May 11, 2022 at 04:45:06PM -0700, Greywolf wrote:
>
> cvs up -AdP in my source tree yields the message
>
> cvs [update aborted]: permission denied for src
>
> What's up?
>
Does the user doing the cvs update have permission to write to src on
your machine?
--
Br
.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
inter may skip. These numbers
are mostly only used for the boundary checking so they don't have to be
absolutely accurate. You can make the changes apply on reboot by adding
the settings to /etc/sysctl.conf.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You
e first line you will see is a
comment that tells you what terminfo database was read to reconstruct
the entry, the system one is in /usr/share/misc, if you get anything
else you may need to correct the rogue terminfo database.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were w
my
> laptop in -current!
>
Thanks for the feedback. Hacking on the touchpad driver is always fraught
because
breaking it can mean no mouse for some so it is great to hear that it works
well for others.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean
until after the NetBSD
10 branch just in case there are unforeseen consequences.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
Case B input processing (with MIN set to 1
> and ICRNL cleared) as specified in the XBD specification.
>
Our cbreak clears ICANON which, if I read the termios man page correctly,
disables ICRNL.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
n curses code was running with onlcr and was compensating
> for its own bug?
>
It would appear so and has been doing this since before NetbSD which is
not a justification, just an observation.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
n with onlcr on always moved the cursor to the first
column of the next line. Window(1) doesn't use ^J for cursor down so
the output was stair-stepping.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
ning of the next line.
It took me ages to believe that was the issue.
I am working on something else at the moment but get to this next.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
On Thu, Jun 24, 2021 at 12:23:26AM +0200, Martin Husemann wrote:
>
> Yes, Brett was going to look at it (latest libcurses changes caused it).
>
Hopefully it is fixed now.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?"
On Fri, Jun 11, 2021 at 10:55:29PM -, Michael van Elst wrote:
> mlel...@serpens.de (Michael van Elst) writes:
>
> >I'm currently testing
> >http://ftp.netbsd.org/pub/NetBSD/misc/mlelstv/st.diff
>
> Works for me:
>
works for me too, thanks.
--
Brett Lymn
--
On Fri, Jun 11, 2021 at 07:10:16PM -, Michael van Elst wrote:
> bl...@internode.on.net (Brett Lymn) writes:
>
> >Here is the patch that makes multi-tape dumps work for me:
>
> I'm currently testing
>
> http://ftp.netbsd.org/pub/NetBSD/misc/mlelstv/st.diff
>
Tha
bp->b_resid = bp->b_bcount;
biodone(bp);
}
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
On Thu, Jun 10, 2021 at 11:10:23AM +0200, Frank Kardel wrote:
>
> I meant the section in ststart1 where error is set to zero followed by goto
> out inf the fixed blocksize part.
>
Sorry, yes you are correct. I ignored that because I am using variable
blocks...oops.
--
Brett
to work for me. From what the code
used to do and
the description Frank posted EOM is indicated by a 0 length write with no error
iff the
early warning flag is set. I haven't checked but I ASSuME that ST_EOM_PENDING
will only be
set if the early warning flag is on.
--
Brett Lymn
--
Sent from m
dump perform as
expected and
prompt for a new tape.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
rming anything, the machine the
tape drive is attached to has to be booted to windows for $WORK during
the day so my testing window is limited :)
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
that change. My backup script
does set the early warning flag. I will have a stab at fixing this
later today, I think if I just avoid returning EIO in the ST_EOM_PENDING
case inside ststart it should be good.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean
ndling. I will try a kernel that
incorporates v1.237 of st.c and see what happens. Unfortunately,
testing is a very slow process as it takes about 3 hours to fill a tape
though I may be able to reduce that by using a lto-1 tape instead which
should halve the time taken to fill a tape.
--
Brett Ly
> "it doesn't work".
>
If you have the space, a tcpdump from both sides of your firewall may provide a
clue.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
On Mon, Feb 01, 2021 at 02:28:08PM +, Roy Marples wrote:
> On 01/02/2021 09:53, Brett Lymn wrote:
> > The TERMCAP variable has some severe liitations, the worst being it can
> > only be 256bytes in size which was more than adequate for a vt100
> > definition but
ottom of why the lynx/window combination is misbehaving.
The TERMCAP variable has some severe liitations, the worst being it can
only be 256bytes in size which was more than adequate for a vt100
definition but a modern colour xterm definition simply won't fit in that
space, terminfo does not have
t, in this case,
it appears that it is missing in the GSoC source tree too. I have
commented out the test for the moment and will chase up the student
about it, perhaps he forgot it in an import.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves
es for the breakage...I missed that when I imported the GSoC project
code.
Thanks for the fixes.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
the unpack that
way.
If you haven't put much work into the system it may be easier to just do
a clean install but practicing recoveries can be useful :)
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
sed.
>
I have only used zfs on solaris and, to me, this sounds wrong. To my way of
thinking the zfs.cache should simply be a source of hints as to where a zfs was
seen
last, look there first and if it is not found the do a possibly expensive scan
to
find it.
--
Brett Lymn
--
Sent from my N
the end of I2C? I vaguely recall
> > that there is an ability to connect via I2C but I may be
> > mis-remembering.
>
> It's likely. Unfortunately this pad also needs fixing, the button is
> physically disconnected...
Oh - that is challenging...
--
Brett Lymn
--
Sent from my Net
re layer :) We are talking about a kernel driver in this
instance.
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
s overloaded and the numbers can mean different things
depending on what mode the trackpad is in and, even worse, the trackpad
won't tell you what mode it is in so you can't just test this.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
I say? It worked for me. One thing I have learnt is there is a
massive variation between laptop trackpads when it comes to reporting
the W value so values that work on one laptop are bad on others, I am
surprised that you were unable to get a fscroll_min that would work for
you.
--
Brett Lymn
--
Sent from m
can update if I
really need to (I lag behind because this laptop is the machine I use
most so I like it stable...)
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
s will cause the trackpad driver to ignore
touches on the trackpad.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
On Wed, Jun 19, 2019 at 07:36:37AM +0200, Michael van Elst wrote:
>
> The only way to identify a device is its driver name. So it is pretty
> trivial to identify mice (ums), keyboards (ukbd) or flash drives (umass).
>
Ah, ok. That should do the trick then.
> But what if you have two mice and
suitable. I guess I could grep the dmesg for the attach but that
feels a bit sub-optimal...
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
e cannot extend it to be more generic...
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
at does just this, they
even had an example of disabling a synaptics touchpad when a usb mouse
is plugged in. Now all we need is this facility in NetBSD
I don't think the wsmouse approaches would work reliably because the
identity of the device is hidden by wsmouse.
--
Brett Lymn
--
Sent from my NetBSD
where the events are coming from hence why I was thinking that the usb
mouse driver could do something to tell the synaptics driver to disable
sending events until futher notice.
Thoughts?
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves
n for
you. Thanks.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
confused. I
need to put a better fix in place to repair the damage. The issue is
purely a display positioning issue as has been noted so, yes, the
underlying selection will work, just the display is mangled. I will get
this fixed ASAP.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are
th the debug options and all modules plus ncurses unstripped.
> Now to build the OS debug sets.
>
Oh ncurses I was going to mention that some time ago I did link our
native curses against libefence which caught a few memory issues.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are
On Fri, Dec 07, 2018 at 01:04:02PM +1030, Brett Lymn wrote:
>
> Yes, horizontal scroll was a thing once upon a time. I don't think I
> have seen any recent mice that offer it as a feature, probably too hard
> to use sanely.
>
After a moment of research - windows does horizontal
ent mice that offer it as a feature, probably too hard
to use sanely.
--
Brett Lymn
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"
think it would be wise to leave the defaults as they are on
the basis it is better to have a slow mouse initially and give people
the control to increase the speed rather than have a cursor zipping all
over the screen making it impossible to use.
--
Brett Lymn
"We are were wolves",
"You mean
Yes, they are ps/2. The pckbc1 is the i8042 keyboard controller
device which handles both keyboard and mouse for ps/2.
The trackpoint should show up as a separate pointing device but it
seems a lot of people are not seeing it show up, there must be
something in the driver that is stopping it
t test that but I am thinking that I
need to rework the handling of the two finger scroll, it is very
sensitive - I am thinking I should change the scaling on it to be a
divisor instead of a multiplier so that large movements don't produce
too many scroll events - the X server really doesn't like lot
On Thu, Nov 29, 2018 at 03:15:31PM +0900, Masanobu SAITOH wrote:
> On 2018/11/28 22:12, SAITOH Masanobu wrote:
>
> But, my X61 survived from suspend with this patch!
>
My fujitsu lifebook S904 came back from suspend with this patch too!
Thank you very much for this.
--
Brett
thing better...
--
Brett Lymn
Let go, or be dragged - Zen proverb.
rders
echo "forward only;" >> /etc/namedb/forwarders
pkill -HUP named
return 0
}
and have a named configured to use the forwarders in
/etc/namedb/forwarders. Whatever the ISP dhcp gives me is stuffed into
the forwarders and used as last resort. This has been
springs:
>
Ah silly me - I thought they were the same. Yes Das use cherry
mechanical switches.
--
Brett Lymn
Let go, or be dragged - Zen proverb.
e with NetBSD (well, apart from the
mouse not being detected *sometimes* when it is plugged into the
in-built usb hub on the keyboard). The keys are the buckling spring
design.
--
Brett Lymn
Let go, or be dragged - Zen proverb.
UEFI because that was what the manufacturers
windows recovery disk insisted on). I will try and find my notes on how
I put this together.
--
Brett Lymn
Let go, or be dragged - Zen proverb.
pad it
used. I suspect it won't.
I will try to have a bit more of a dig at this when I get a bit of time.
--
Brett Lymn
Let go, or be dragged - Zen proverb.
l provide more information. It sounds
like the pckbc driver is getting confused somehow. Is the machine
otherwise operational when the keyboard freezes (i.e. can you ping it or
remotely log in?)
--
Brett Lymn
Let go, or be dragged - Zen proverb.
ext);
+printf("filt_sowdetach: remove done\n");
if (SLIST_EMPTY(>so_snd.sb_sel.sel_klist))
so->so_snd.sb_flags &= ~SB_KNOTE;
sounlock(so);
--
Brett Lymn
ave a look at the libcurses handling of non-spacing characters,
that tried to balance memory consumption against implementation
complexity.
--
Brett Lymn
Let go, or be dragged - Zen proverb.
t should push the pages
out to disk.
--
Brett Lymn
Let go, or be dragged - Zen proverb.
ot/src/sys/dev/pckbport/synapticsvar.h,v
retrieving revision 1.6
diff -u -r1.6 synapticsvar.h
--- synapticsvar.h 23 May 2014 01:11:29 - 1.6
+++ synapticsvar.h 5 Dec 2015 06:35:33 -
@@ -55,10 +55,10 @@
#defineSYN_FLAG_HAS_TWO_BUTTON_CLICKPAD(1 << 10)
#defineSYN_FLAG_HAS_EXTENDED_WMODE (1 << 11)
- u_int total_packets; /* Total number of packets received */
-#defineSYN_TIME(sc,c) (((sc)->total_packets >= (c)) ? \
- ((sc)->total_packets - (c)) : \
- ((c) - (sc)->total_packets))
+ u_int total_packets[2]; /* Total number of packets received */
+#defineSYN_TIME(sc,c,n)(((sc)->total_packets[(n)] >= (c)) ?
\
+ ((sc)->total_packets[(n)] - (c)) : \
+ ((c) - (sc)->total_packets[(n)]))
int up_down;
int prev_fingers;
@@ -78,9 +78,10 @@
#defineSYN_IS_DRAG(t) ((t) & SYN_GESTURE_DRAG)
#defineSYN_HIST_SIZE 4
- int rem_x, rem_y;
- u_int movement_history;
- int history_x[SYN_HIST_SIZE], history_y[SYN_HIST_SIZE];
+ charbutton_history;
+ int rem_x[2], rem_y[2];
+ u_int movement_history[2];
+ int history_x[2][SYN_HIST_SIZE], history_y[2][SYN_HIST_SIZE];
};
int pms_synaptics_probe_init(void *vsc);
--
Brett Lymn
Let go, or be dragged - Zen proverb.
they are devices. You could possibly get an implementation of MTP
(media transfer protocol) up and going to write out a file, most phones
support MTP I believe but it does mean doing the usb protocol and then
layering the mtp over the top. First step would be to get a polled mode
USB transfer
linux
reports and if I decode them then, yes, I have a one button click pad
but somehow linux does two buttons, though I can't work out how from
their driver. Anyone have any ideas?
--
Brett Lymn
Let go, or be dragged - Zen proverb.
ftp.netbsd.org.
--
Brett Lymn
to my home
router. I know my ipv6 set up is ok because a laptop I configure using
dhcp works fine with ipv6 so it must be something I am not doing on the
wired machine. Any suggestions? Thanks.
--
Brett Lymn
I am using a recent current and trying to get grub2 to multiboot the
kernel but grub2 keeps telling me that it cannot find the multiboot
header even though the kernel is built with options MULTIBOOT, on amd64.
Some googling indicates it used to work, has it been broken?
--
Brett Lymn
.
--
Brett Lymn
an EFI
bootloader it can load and execute... hence the reason for this email,
is anyone working on an EFI bootloader for NetBSD? I would love to get
rid of the grub hoops if I can.
--
Brett Lymn
there is an interrupt pipe on
interface 0. I believe that would be used to report line status changes
- things like DCD asserted, that sort of thing. The concern I have with
your code is that it may appear to work in that you get a com interface
but you may be missing the control lines.
--
Brett Lymn
of this
that know the code well.
--
Brett Lymn
Staple Guns: because duct tape doesn't make that KerCHUNK sound - xkcd.com
.
--
Brett Lymn
Staple Guns: because duct tape doesn't make that KerCHUNK sound - xkcd.com
and if that doesn't work then use brute force. IIRC the
rest of the driver should be fine with that because the data interface
is referenced separately to the control interface.
--
Brett Lymn
Staple Guns: because duct tape doesn't make that KerCHUNK sound - xkcd.com
are the class and subclass values?
The attach process should step through all the interfaces declared on
the device and only attach to the one that has the ACM_CDC class. Hard
to say what the other interface is for - perhaps proprietry call
monitoring or something.
--
Brett Lymn
Staple Guns: because duct
print out a bunch of information about the device. Post the
output here and we can work out what it claims to be.
--
Brett Lymn
Staple Guns: because duct tape doesn't make that KerCHUNK sound - xkcd.com
#include stdio.h
#include stdlib.h
#include fcntl.h
#include errno.h
#include sys/ioctl.h
to
have a lid switch device but it disappeared in an update, I have had a
look at the history of acpi_lid.c and don't see any changes in the probe
string for the device. I tried dumping the aml but can't see any
reference to PNP0C0D there. Any things on how I can debug this?
--
Brett Lymn
Warning
82 matches
Mail list logo
