The most recent commit to bktr completely breaks the driver for me.
When starting a tv application, I get
bktr0: tuner @ 0xc2
bktr0: MT2032 write failed (i2c addr 0xc0)
bktr0: MT2032 get register 0 failed
bktr0: MT2032 write failed (i2c addr 0xc0)
bktr0: MT2032 get register 1 failed
bktr0:
On Sunday, 2. January 2005 12:18, Michael Nottebrock wrote:
The most recent commit to bktr completely breaks the driver for me.
When starting a tv application, I get
bktr0: tuner @ 0xc2
bktr0: MT2032 write failed (i2c addr 0xc0)
Looking at the changes, it seems that my card is misidentified
On Sat, Jan 01, 2005 at 02:01:11AM +0100, Roland Smith wrote:
On Fri, Dec 31, 2004 at 04:07:12PM +0100, Harald Weis wrote:
On Thu, Dec 30, 2004 at 09:33:32AM +0100, Marc Fonvieille wrote:
On Wed, Dec 29, 2004 at 04:49:05PM +0100, Harald Weis wrote:
My scanner (EPSON PERFECTION 1650)
On Sat, 1 Jan 2005, [utf-8] Björn König wrote:
I wanted to use SLIP to connect two machines with a null-modem cable,
but I realize that all information concerning this topic seems to be out
of date. First of all the device sl0 doesn't exist in 5.3 although there
is a device sl in
On Sun, Jan 02, 2005 at 01:17:37PM +0100, Harald Weis wrote:
Harald, I think most of us understood what you mean.
But as I don't use the scanner every day I normally keep it
disconnected. Up to now I am obliged to reboot the system if I want to
use the scanner in the middle of the day. This
Michael Nottebrock wrote:
On Sunday, 2. January 2005 12:18, Michael Nottebrock wrote:
The most recent commit to bktr completely breaks the driver for me.
When starting a tv application, I get
bktr0: tuner @ 0xc2
bktr0: MT2032 write failed (i2c addr 0xc0)
Looking at the changes, it seems that my
On Sunday, 2. January 2005 22:44, Julian Elischer wrote:
Michael Nottebrock wrote:
On Sunday, 2. January 2005 12:18, Michael Nottebrock wrote:
The most recent commit to bktr completely breaks the driver for me.
When starting a tv application, I get
bktr0: tuner @ 0xc2
bktr0: MT2032
hi all-
so i'm attempting to tweak my kernel to eke out a bit more oomph from my
Gigabit interface, but i can't seem to set any of the
net.inet.tcp.inflight_* params with sysctl. i get:
sysctl: unknown oid 'net.inet.tcp.inflight_enable'
et al. all of the docs i've found seem to assume that
Hello,
thanks a lot for your hints. The null-modem cable connection is working now.
Anyway, it was surprisingly easy, but I'm totally inexperienced and the
neglected manpages and handbook discouraged me, because I didn't touch serial
ports since a decade ;-) Finally someone points me at [1].
In message: [EMAIL PROTECTED]
Brandon Fosdick [EMAIL PROTECTED] writes:
: Judging from the man page, ucom is limited to acting like a tty with no
: support for sio. Is this true? Is there some magic config bit somewhere
: that will enable hidden sio support?
Ummm, I don't know what
Announcement
The FreeBSD Release Engineering Team is pleased to announce the availability
of FreeBSD 4.11-RC2. This is the second of three scheduled Release
Candidates.
A schedule for the Release Cycle is available at:
http://www.freebsd.org/releases/4.11R/schedule.html
We
11 matches
Mail list logo
