;ve worked with the Linux patches (ugg...I miss running
FreeBSD and not having to manually patch my kernel) and they're amazingly
simple, given their function.
How hard do y'all think this would be? Is anyone else interested in this? In
Linux it basically lets us work around brok
ere's a
very slight possibility that some of the utilities intended for other Compal
distributors (Compaq, HP, Toshiba) might work. (The Linux omnibook kernel
module works on two of my machines, both Compals, only one an HP.)
You might get more information on this from the freebsd-mobile list
ct the problem here is with moused, but
haven't had time to tear it open (I suddenly got employed).
Not sure if David's seeing the same symptoms, exactly.
-Cliff L. Biffle
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/lis
connected; the interesting debug output
only appears once it's disconnected. Not disconnecting it doesn't fix
anything.
Is there a more specific mailing list I could target this to?
-Cliff L. Biffle
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
instead of
working for a while and then going insane. Again, ports work fine under
Linux. I suspect it may be unrelated.)
What should I instrument? Any debug flags I can turn on?
-Cliff L. Biffle
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I've been having a reliable USB issue on my 5-current box (3 Mar, 23:58:25
MST). It's been happening since I upgraded to -current in the DP2 days, and
has happened on two completely independent motherboards. On the more recent
of the two (the previous died) I've enabled USB_DEBUG. Here's the
7;t think it's a hardware issue.
Help!
-Cliff L. Biffle
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
to do it for
'performance' reasons -- getting the graphics working was an unexpected
boon.)
I can get you the kernel config, or make it available to the list if anyone's
interested in this fleeting heisenbug.
-Cliff L. Biffle
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &qu
marks (primarily of KDE and my own applications).
I'm willing to trade some time on the compile (which, with any luck, happens
only once) in exchange for speed in the application (which I may use every
day)! :-)
-Cliff L. Biffle
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "uns
On Wednesday 11 December 2002 10:49 pm, Mike Makonnen wrote:
> man 8 rc
> man 8 rc.subr
I was really hoping for documentation on how the PROVIDES/REQUIRES stuff was
handled and calculated. I'm familiar with the rc scripts in general.
I suppose I can read the code. :-)
-Cliff L.
inister FreeBSD
workstations (running KDE 3.1 on 5.0-DP2 here), and I like the way rcng works
and would like to see about integrating a configurator.
Thanks!
-Cliff L. Biffle
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
x27;s just been so
wonderfully stable...I'm so used to using -stable that this feels like
pushing my luck. :-)
Thanks!
-Cliff L. Biffle
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
SDRAM would be nice
(since I have 768MB here) but not necessary.
Suggestions?
(Don't want to repeat the KT133 fiasco. :-)
-Cliff L. Biffle
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ned potentially-buggy Apollo KT133 chipset, but it's
never reported these errors on my hard disk (knock on wood), only the CD
drive. They -are- on separate channels.
I'll see what information I can collect here, but suggestions on where to look
are appreciated.
-Cliff L. Biffle
To
nting out
DEBUG=-g?
Thanks!
-Cliff L. Biffle
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
27;s not on the list,
since he's still having trouble admitting to running anything other than
Gentoo. :-) (Yes, 5.0-DP2 is bringing in converts from the cold left and
right here in Tempe!)
-Cliff L. Biffle
--- src/nv-freebsd.h Wed Oct 30 07:30:58 2002
+++ src/nv-freebsd.h
) eliminates the current-draw question.
If (2) is true, that points to hardware problems with the primary controller.
(Forgot I had two. *grin*)
-Cliff L. Biffle
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
r mobo is a very early Athlon board, and the chipset may
be buggy.
-Cliff L. Biffle
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ld I just
sup to -current?
Thanks!
-Cliff L. Biffle
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
is fully capable of saturating a 100mbps
link. It's an 8139; the only thing I did that might have been unusual was
forcing the media/mediaopts after bad experiences with rl's autodetect in the
past. Perhaps if you give me more information about your setup I could
better reproduce
r to 800kBps. I'm trying to find a
patch cable (or a crimper) to try 100mbps.
-Cliff L. Biffle
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
n. We've got a whole scad of 8139s, 8129s, 3c905s, and some
old Davicom-based cards that gave me endless trouble under 4.x. I'll let you
know what I find.
For reference, the 8139 in my 5-current box here works at full speed, but I'm
on 10mbps; we have more 100baseT equipment at wor
22 matches
Mail list logo
