HA!! SUCCESS!!
I upgraded to Netbsd-HEAD, and compiled a new kernel.
I found this in dmesg:
[ 1.013220] usb0 at xhci0: USB revision 3.1
[ 1.013220] usb1 at xhci0: USB revision 2.0
USB 3.1 is the USB socket with the red tongue. I have not used that
because NetBSD didnt
support USB 3.1
WOW! That will 'splain a lot.
On Thu, Jun 17, 2021 at 7:13 AM Simon Burge wrote:
>
> Todd Gruhn wrote:
>
> > Thanks. NetBSD has a config file for the boot sequence?
> > That sounds like a major change from v 5.x ...
>
> Look at boot.cfg(5). The man page says it appeared in NetBSD 5.0.
>
> Cheer
Todd Gruhn wrote:
> Thanks. NetBSD has a config file for the boot sequence?
> That sounds like a major change from v 5.x ...
Look at boot.cfg(5). The man page says it appeared in NetBSD 5.0.
Cheers,
Simon.
Thanks. NetBSD has a config file for the boot sequence?
That sounds like a major change from v 5.x ...
On Thu, Jun 17, 2021 at 12:04 AM Simon Burge wrote:
>
> Todd Gruhn wrote:
>
> > I found the 'Utility' option and chose each color option. ALL are very
> > difficult to read.
> > Its like the po
Todd Gruhn wrote:
> I found the 'Utility' option and chose each color option. ALL are very
> difficult to read.
> Its like the power has been cut to both fg and bg.
I have the dark-on-dark thing on a HP N40L here, and use this in my
boot.cfg:
userconf=disable radeon*
You should be to pr
I found the 'Utility' option and chose each color option. ALL are very
difficult to read.
Its like the power has been cut to both fg and bg.
Is there a way to work around this? Is there a way to catch this and
pass it along?
(like a log file?)
On Wed, Jun 16, 2021 at 9:15 PM Todd Gruhn wrote:
>
On Wed, 16 Jun 2021, Todd Gruhn wrote:
S, just download the tar files, and upgrade to HEAD ?
That sounds like a simple fix.
Rather, install from the image.
-RVP
Thanks for the idea. I will check it out tomorrow.
That will prob fix the prob I had last time .
On Wed, Jun 16, 2021 at 8:28 PM RVP wrote:
>
> On Wed, 16 Jun 2021, Todd Gruhn wrote:
>
> > When I run the INSTALL/UPGRADE utility I get a dark-blue screen that
> > is very hard to read.
> > This is w
On Wed, 16 Jun 2021, Todd Gruhn wrote:
When I run the INSTALL/UPGRADE utility I get a dark-blue screen that
is very hard to read.
This is why I used the sysupgrade script last time.
Is there a way to break the NetBSD boot sequence, and reset the
back-ground color?
There is a menu item to cha
I got the NetBSD*HEAD stuff download and on CDs.
When I run the INSTALL/UPGRADE utility I get a dark-blue screen that
is very hard to read.
This is why I used the sysupgrade script last time.
Is there a way to break the NetBSD boot sequence, and reset the
back-ground color?
On Wed, Jun 16, 2021
On Wed, 16 Jun 2021, Todd Gruhn wrote:
Here are the results from the new kernel:
dmesg
...
[ 3.322560] uvideo0 at uhub1 port 6 configuration 1 interface 0:
vendor 046d (0x46d) product 0807 (0x807), rev 2.00/0.09, addr 1
[ 3.322560] video0 at uvideo0: vendor 046d (0x46d) product 0807
(0x
Thanks. I will try that then...
On Wed, Jun 16, 2021 at 9:56 PM RVP wrote:
>
> On Wed, 16 Jun 2021, Todd Gruhn wrote:
>
> > S, just download the tar files, and upgrade to HEAD ?
> >
> > That sounds like a simple fix.
> >
>
> Rather, install from the image.
>
> -RVP
S, just download the tar files, and upgrade to HEAD ?
That sounds like a simple fix.
On Wed, Jun 16, 2021 at 8:59 PM RVP wrote:
>
> On Wed, 16 Jun 2021, Todd Gruhn wrote:
>
> > drvctl -l -t
> > ...
> > It is USB-3.0 .
> >
>
> That's fine. External USB ports are usually connected to the XHCI
On Wed, 16 Jun 2021, Todd Gruhn wrote:
drvctl -l -t
...
It is USB-3.0 .
That's fine. External USB ports are usually connected to the XHCI
controller. Built-in USB devices (like my laptop's webcam and
touchscreen) are connected to EHCI.
I got it for 2 USD.
:) Maybe that explains everythin
I just discovered something:
drvctl -l -t
gives a list of devices in tree format. Here is the relevant part.
xhci0
usb0
uhub0
usb1
uhub1
uhub2
uhidev0
ukbd0
wskbd1
uhidev1
ums0
Here are the results from the new kernel:
dmesg
[ 1.00] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001,
2002, 2003, 2004, 2005,
[ 1.00] 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013,
2014, 2015, 2016, 2017,
[ 1.00] 2018, 2019, 2020 The NetBSD Foundation, Inc. Al
On Tue, 15 Jun 2021, Todd Gruhn wrote:
[ 3.281559] uaudio0: Logitech (0x46d) product 0807 (0x807), rev
2.00/0.09, addr 1
My line, [ 3.281559]. It says "product 0807". We have 2 different cameras?
Of course. Different models will have different product IDs.
[ 2404.381560] audio1(uaudio0
I dont have a usb-hub -- it goes straight into the back of my computer.
'drvctl -d uaudio0 ' gives no results, so I am compiling a new kernel.
On Wed, Jun 16, 2021 at 9:43 AM RVP wrote:
>
> On Tue, 15 Jun 2021, Todd Gruhn wrote:
>
> > [ 3.281559] uaudio0: Logitech (0x46d) product 0807 (0x807),
Here. I saw something interesting. ALSO, I apparently have something
to fix on the
kernel level.
[ 3.281559] uvideo0 at uhub1 port 6 configuration 1 interface 0:
Logitech (0x46d) product 0807 (0x807), rev 2.00/0.09, addr 1
[ 3.281559] video0 at uvideo0: Logitech (0x46d) product 0807
(0x807
On Tue, 15 Jun 2021, Todd Gruhn wrote:
I got pkgsrc-wip installed. Ideas here?
Assuming we're still discussing your webcam woes:
I tried out 2 USB webcams (the built-in one and a very old Logitech
that I had lying around) and both worked fine on 9.99.82:
$ dmesg | tail
[20.157756] cpu 0
I got pkgsrc-wip installed. Ideas here?
On Tue, Jun 15, 2021 at 8:10 PM Chavdar Ivanov wrote:
>
> On Mon, 14 Jun 2021 at 21:12, Rhialto wrote:
> >
> > On Sun 13 Jun 2021 at 20:03:14 +0100, Chavdar Ivanov wrote:
> > > I tested ffplay4 on a -current system, which is a VirtualBox guest
> > > (W10
On Mon, 14 Jun 2021 at 21:12, Rhialto wrote:
>
> On Sun 13 Jun 2021 at 20:03:14 +0100, Chavdar Ivanov wrote:
> > I tested ffplay4 on a -current system, which is a VirtualBox guest
> > (W10 client) and has an Intel F200 camera, it worked fine, up until I
> > tried to stop it - I got a core dump (no
On Sun 13 Jun 2021 at 20:03:14 +0100, Chavdar Ivanov wrote:
> I tested ffplay4 on a -current system, which is a VirtualBox guest
> (W10 client) and has an Intel F200 camera, it worked fine, up until I
> tried to stop it - I got a core dump (not much info, it happened in
> __cxa_finalize () from /u
That looks like what I get. I remember the
[video4linux2...] part
On Sun, Jun 13, 2021 at 6:40 PM Chavdar Ivanov wrote:
>
>
> On 6/13/21 5:00 PM, Todd Gruhn wrote:
> > "libc.so.12" isnt that a C-programming lib?
> >
> > On Sun, Jun 13, 2021 at 7:03 PM Chavdar Ivanov wrote:
> >> On Sun, 13 Jun 2
On 6/13/21 5:00 PM, Todd Gruhn wrote:
"libc.so.12" isnt that a C-programming lib?
On Sun, Jun 13, 2021 at 7:03 PM Chavdar Ivanov wrote:
On Sun, 13 Jun 2021 at 12:15, Todd Gruhn wrote:
Is there a nice way to collect it? I get stuff about a linux device.
I dont understand why...
On Sun,
"libc.so.12" isnt that a C-programming lib?
On Sun, Jun 13, 2021 at 7:03 PM Chavdar Ivanov wrote:
>
> On Sun, 13 Jun 2021 at 12:15, Todd Gruhn wrote:
> >
> > Is there a nice way to collect it? I get stuff about a linux device.
> > I dont understand why...
> >
> > On Sun, Jun 13, 2021 at 7:12
On Sun, 13 Jun 2021 at 12:15, Todd Gruhn wrote:
>
> Is there a nice way to collect it? I get stuff about a linux device.
> I dont understand why...
>
> On Sun, Jun 13, 2021 at 7:12 AM nia wrote:
> >
> > On Sun, Jun 13, 2021 at 07:11:47AM -0400, Todd Gruhn wrote:
> > > I built ffplay4 from the
Is there a nice way to collect it? I get stuff about a linux device.
I dont understand why...
On Sun, Jun 13, 2021 at 7:12 AM nia wrote:
>
> On Sun, Jun 13, 2021 at 07:11:47AM -0400, Todd Gruhn wrote:
> > I built ffplay4 from the current pkgsrc tree. It compiled completely, but
> > I get an er
On Sun, Jun 13, 2021 at 07:11:47AM -0400, Todd Gruhn wrote:
> I built ffplay4 from the current pkgsrc tree. It compiled completely, but
> I get an error when I execute the command
>
> ffplay4 /dev/video0
OK, what error...?
I built ffplay4 from the current pkgsrc tree. It compiled completely, but
I get an error when I execute the command
ffplay4 /dev/video0
On Sun, Jun 13, 2021 at 6:58 AM nia wrote:
>
> On Sun, Jun 13, 2021 at 10:27:06AM +0100, Chavdar Ivanov wrote:
> > On Sat, 12 Jun 2021 at 22:06, nia wrote:
>
On Sun, 13 Jun 2021 at 11:58, nia wrote:
>
> On Sun, Jun 13, 2021 at 10:27:06AM +0100, Chavdar Ivanov wrote:
> > On Sat, 12 Jun 2021 at 22:06, nia wrote:
> > >
> > > On Sat, Jun 12, 2021 at 04:12:32PM +, Todd Gruhn wrote:
> > > > I dont have a camera in my screen (like a laptop would). I have
On Sun, Jun 13, 2021 at 10:27:06AM +0100, Chavdar Ivanov wrote:
> On Sat, 12 Jun 2021 at 22:06, nia wrote:
> >
> > On Sat, Jun 12, 2021 at 04:12:32PM +, Todd Gruhn wrote:
> > > I dont have a camera in my screen (like a laptop would). I have a LogiTech
> > > web-cam hooked to my flat-screen, an
On Sat, 12 Jun 2021 at 22:06, nia wrote:
>
> On Sat, Jun 12, 2021 at 04:12:32PM +, Todd Gruhn wrote:
> > I dont have a camera in my screen (like a laptop would). I have a LogiTech
> > web-cam hooked to my flat-screen, and plugged into a USB port.
> > Would this make a difference?
> >
> > On Sa
Thanks
On Sat, Jun 12, 2021 at 9:05 PM nia wrote:
>
> On Sat, Jun 12, 2021 at 04:12:32PM +, Todd Gruhn wrote:
> > I dont have a camera in my screen (like a laptop would). I have a LogiTech
> > web-cam hooked to my flat-screen, and plugged into a USB port.
> > Would this make a difference?
> >
On Sat, Jun 12, 2021 at 04:12:32PM +, Todd Gruhn wrote:
> I dont have a camera in my screen (like a laptop would). I have a LogiTech
> web-cam hooked to my flat-screen, and plugged into a USB port.
> Would this make a difference?
>
> On Sat, Jun 12, 2021 at 4:09 PM nia wrote:
> >
> > On Sat,
I dont have a camera in my screen (like a laptop would). I have a LogiTech
web-cam hooked to my flat-screen, and plugged into a USB port.
Would this make a difference?
On Sat, Jun 12, 2021 at 4:09 PM nia wrote:
>
> On Sat, Jun 12, 2021 at 11:07:26AM +, Todd Gruhn wrote:
> > I installed Cheese
Todd Gruhn wrote:
>
>I installed Cheese. It does not work on my system.
It would help to know what version of NetBSD you are running.
Part of the interface between libv4l and the camera driver is only
in -current.
On Sat, Jun 12, 2021 at 11:07:26AM +, Todd Gruhn wrote:
> I installed Cheese. It does not work on my system.
> Any other options for web-cameras?
I use ffplay (playing)/ffmpeg (recording).
Hi Todd,
You could try fswebcam from pkgsrc-wip. This is a command line tool that
can record from the v4l devices. It works out of the box with the
built-in webcam on my Thinkpad x230.
Many greetings
Matthias
Am 12.06.21 um 13:07 schrieb Todd Gruhn:
I installed Cheese. It does not work on m
39 matches
Mail list logo
