you need to do to enable/power up the
on-board NIC that we're not doing
This is something you should be asking the PCI gurus about,
not the networking gurus.
-Bill
--
=
-Bill Paul(510) 749-2329 | Senio
> >>>>> "Bill" == Bill Paul <[EMAIL PROTECTED]> writes:
>
> >> I'm somewhat confused.
> Bill> So am I: where were you when I asked sent e-mail to this list
> Bill> asking for people to test the 5705 changes before I committed
> B
y to experiment is compile your kernel _WITHOUT_ bge support,
and then build if_bge.ko as a module:
# cd /sys/modules/bge
# make; make load
-Bill
--
k, though my test for the
geteuid() == 0 case was a bit of a kludge since I don't actually
have root on the test box.
-Bill
--
=====
-Bill Paul(510) 749-2329 | Senior Engineer, Master o
rning NS_SUCCESS all the time.
I uploaded a new diff, please test this instead:
http://www.freebsd.org/~wpaul/getpwent.diff
Thanks for providing me access to this machine, it helped me realize
where I'd gone wrong in my patch. If this works for you, and if nobody
objects, I will check it in.
/sys/dev/mii
- Rebuild your kernel and/or if_bge.ko and miibus.ko modules
-Bill
--
=====
-Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu
[EMAIL PROTECTED] | Wind River Sy
ist. The fact that it fails for root means it
must have something to do with probing for the master.passwd.by* maps,
but I'm not sure what yet.
-Bill
--
gt; > just hides the bug again. As a work-around, we could try yp_order
> > first, and if that fails, try yp_master.
It's not a bug in our implementation, it's implementation weirdness
in the server. :)
-Bill
--
and miidevs into /sys/dev/mii
- Recompile your kernel and/or if_bge.ko and miibus.ko modules.
-Bill
--
=
-Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu
[EMAIL PROTECTED] | Wind
y help anyone is able to provide.
-Bill
--
=====
-Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu
[EMAIL PROTECTED] | Wind River Systems
=
"If stupidity were
fact say 8139C+.) I hope RealTek
has actually sold this chip well, because it actually seems to perform
really well.
-Bill
--
=
-Bill Paul(510) 749-23
re otherwise not working,
> so it should be fairly safe.
This patch also tests good with my drive.
-Bill
--
=
-Bill Paul(510) 749-23
aid: "Bill! Your
driver hasn't worked right on in months! I'm at wit's end! You leave me *NO* alternative!
I'm just going to have to fix it for you! At gunpoint! No no, don't
try and stop me! This is for your own good!" well, then, gosh, I'd
let 'em.
B
you all for your attention. Don't
forget to tip the waitress.
-Bill
P.S.: Be sure to join us next time when I ream out whoever it was that
broke support for my 3Com 3c575C cardbus ethernet NIC.
--
=
-Bil
ng in the USB code is re-using a
free()ed memory buffer. Unfortunately, I don't have this particular
hardware available to me, and I don't know how much debugging support
the individual at Transmeta will be able to offer. (He has his own
problems.) Hopefully this will at least help spur some
me know how this works.
-Bill
--
=====
-Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu
[EMAIL PROTECTED] | Wind River Systems
=
ot works.
I don't know if this is still a problem or not. At the moment, I have
no easy way to test it.
> There are more verbose details on these lists too.
> Are there any chances to get these fixed?
Like I said, it depends on time and availability of resources.
-Bill
--
===
0x9 is
an 82557/8/9, which won't gain anything from these mods, I'm sorry to
say.
-Bill
--
=
-Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu
[EMAIL PROTECTED] | Wind River Systems
ike to commit this soon. I'm
fairly confident that (at the very least) it doesn't break any existing
functionality. Unfortunately, I'm not in a position to do in-depth
performance tests right now.
-Bill
--
=
-Bill
>
> After the last cvsup (changes from 29 of september) i've got dead
> dc (21143 based NIC).
You have to tell us _exactly_ what card you have. Find the manufacturer
and model info. Look on the box the card came in. Look at the card itself.
Show us the output from pciconf -l so we can see the PC
them to the map list for later use. It isn't
until the driver calls bus_dmamap_list_destroy() that the dmamaps
are actually released and the list free()ed.
-Bill
--
=
-Bill Pau
ing the
head of the list, then it hands it to bus_dmamap_list_alloc() along
with the required dma tag. bus_dmamap_list_alloc() then calls
bus_dmapap_create() to populate the list. The driver doesn't have
to manipulate the list itself, until time comes to destroy it.
-Bill
--
to the
list when the transaction is completed.
- Updated the modified if_sf driver to use the new code.
Again, I've got this code running on the test box in the lab, so it's
correct inasmuch as it compiles and runs, even though it may not be
aesthetically pleasing.
-Bill
sed. It's right
where I need it. Why not take advantage of it?
> > Finally- why not make this an inline?
Er... because that idea offended my delicate sensibilities? :)
-Bill
--
=
-Bill Paul(510) 749-2329 | Senior Engineer, Master o
a test box in the lab right now.
-Bill
--
=====
-Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu
[EMAIL PROTECTED] | Wind River Systems
=
"I like zees g
this
code ASAP (the last test I really need to do is make sure it works
correctly on an alpha).
-Bill
=
-Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu
[EMAIL PROTECTED] | Win
> >
> > Why can't you just enable sigio on the reply socket, send all the
> > requests with a 0 timeout and then wait for a signal to either
> > interrupt the sending or to notify you when you complete sending?
> >
> > Your solution seems awfully complex for what seems to be a simple
> > problem
Ok. Friday I sat down and tried to make the -m option to ypbind work
correctly using the new TI-RPC code. Unfortunately, my test machine
chose that day to eat itself. Even more unfortunately, it was an AMD
900Mhz Thunderbird. Today, I started working on another box and managed
to get things to wor
>
> That's a bit ugly.
>
> > xl0: <3Com 3c575C Fast Etherlink XL> port 0x3000-0x307f mem
> > 0x4402-0x4403,0x44002480-0x440024ff,0x44002400-0x4400247f irq 10 at
> > device 0.0 on cardbus1
> > xl0: chip is in D6 power mode -- setting to D0
>
> I'm a bit worried about this; "D6" doesn't r
3Com has yet another revision of the Tornado chipset floating around out
there on newer 3c905C adapters. Supposedly, these are marked as 3c905CX
and have become available within the last couple of months. I've seen
some noise on the Linux mailing lists that seems to indicate that some
driver mods
Okay. Recently, David O'Brien handed me an Intel 10/100 Cardbus NIC,
which uses the 21143-PB chip. It's a non-MII card (has a Quality Semi
symbol PHY). Unfortunately, it looks like Intel has taken a few shortcuts
with this card: the serial EEPROM doesn't contain any useful information.
Instead, th
> Someone (I can't find who in my records, please let me know if it was
> you so I can credit you in the commit message) sent out patches to
> make the vx driver not use the pci compat shims. I just found it in
> my home directory, applied it, tweaked things very minorly and it
> builds and boots
> Hi,
>
> I have a realtek ethernet card. The normal dmesg is this:
>
> rl0: port 0xb400-0xb4ff mem 0xd900-0xd9ff irq 10
>at device 11.0 on pci0
> rl0: Ethernet address: 00:e0:7d:7d:cd:35
> miibus0: on rl0
> rlphy0: on miibus0
> rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX
>I'm not sure whether the problem of loading secondary usb modules is a
>problem in 4.x but it is easy to try.
>Boot a machine without usb support compiled in. after login, kldload
>usb, then the miibus and then the if_aue modules. If that works, you
>should be ok.
>I cannot test this as at the
> Hello Bill,
>
> I'm sorry about that. Here's some information that I can gather:
> 1. The Intel 21143 chips is intergrated in NEC VersaPro NoteBook PC.
>No LED to indicate the network activity are available.
>
> 2. It is connected to 10BaseT Hub (HP 28688B) at half duplex.
Ok, two more th
> Hello Bill,
>
> After the following commit, my system fail to connect to network.
> If I backout, seems to work again. Any comments appreciated.
No no no. *You* are the one who's supposed to make the comments.
Like exactly what card do you have (make/model)? Exactly what speed
and duplex mode
>
> For reference the ID reported is:
>
> de0@pci0:3:0: class=0x02 card=0x chip=0x00191011 rev=0x11 hdr=0x00
Hm, ok. First of all, I made a mistake in what I told you. The code in
dcphy.c checks the subsystem ID, not the device ID. The device ID is always
the same, since that ident
> > - There's one interface involved here
>
> Correct.
>
> > - It has a 21143 chip
>
> Well, the de driver says 21142. The dc driver says 21143.
It's just a difference in chip revision, really.
> This one does not have AUI so that is not going to be a problem. What I do
> wonder, though, is
> Hi Bill,
>
> I applied your patches to -current without incidents.
>
> I have a testbox (Digital dual P6) that gives:
>
> May 31 10:56:38 p6 /kernel: dc0: port
[...]
> May 31 11:03:27 p6 /kernel: dc0: watchdog timeout
>
> This box can also house an Alpha Miata MX5 mainboard, the Intel & A
> On Tue, May 30, 2000 at 12:28:25AM -0700, Bill Paul wrote:
> > Several people have reported problems with if_dc botching autonegotiation
> > on 21143 NICs with non-MII media, such as the DEC/Compaq DE500-BA and
> > the built-in 10/100 ethernet on some alphas. As my first
Several people have reported problems with if_dc botching autonegotiation
on 21143 NICs with non-MII media, such as the DEC/Compaq DE500-BA and
the built-in 10/100 ethernet on some alphas. As my first official act
as a BSDi/WC employee, I sat down and tried to fix this. I produced
some patches for
Of all the gin joints in all the towns in all the world, Gary Jennejohn
had to walk into mine and say:
[...]
> Yes, this patch fixes the problem. Thank you, Bill Paul !
*sigh* It figures. Ok, I applied the patch to -current and -stable.
We now return you to your regularly scheduled prog
ss, somebody should fix gdb.
--
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home: [EMAIL PROTECTED] | Columbi
"go into the computer's BIOS setup screen
and turn the parallel port off."
-Bill
--
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Cen
G boot floppy and run the diagnostics on the diskette supplied
with the card. If the vendor-supplied diags also wedge the system during
a transmission, then you need to check your hardware.
-Bill
--
=
-Bill Paul
t you can modify the
> firmware, and so header splitting is an option there. It would even be
> possible to split the headers off of IPv6 packets, or any other protocol
> that you have knowlege of.
If you can actually modify the firmware to do this then you have a lot
more guru
f
the XMACs and performance on that port would get spotty. I think the total
TX FIFO memory on the XMAC II is 2K.
-Bill
--
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home: [EMAIL PROTECTED] |
pport
> zero copy TCP receive.
>
> The Alteon boards, on the other hand, have most of the features necessary,
> and if I get some time, I may add the last feature (header splitting) to
> the firmware.
>
> The other alternative is SysKonnect, and that might actually be a goo
Of all the gin joints in all the towns in all the world, Paul Reece had
to walk into mine and say:
> On Thu, 20 Jan 2000, Bill Paul wrote:
>
>
>
> > Back up. You're leaving out some info.
> >
> > - When did you buy these cards? (The firmware rev may
sd.org/~wpaul/PNIC. You have the driver source.
Somebody *else* try and figure it out, and then tell me then answer when
you have it.
That said, if you have overclocked this machine, then un-overclock it *right*
*now* and never, ever do it again! PCI bus master DMA is goofy enough without
pe
operly for address 0x100.
>
> Cheers.
>
>
> Regards,
> Paul.
>
> (replies to me direct please - not on list)
I'm doing both. Deal with it.
-Bill
--
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for
antly
better than with the UHCI controller. Just my rotten luck I'm stuck
with a UHCI one in my laptop.
-Bill
--
=====
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PRO
g MAKEDEV snd0.
-Bill
--
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home: [EMAIL PROTECTED] | Columbia University, New York City
===
Length), USBD_SHORT_XFER_OK, 0);
to this:
usbd_setup_default_xfer(xfer, dev, 0, 100, req,
data, UGETW(req->wLength), USBD_SHORT_XFER_OK, 0);
Then recompile your kernel/module/whatever and try again. (And let
me know what happens, of course.)
-Bill
--
====
ted rev=3D0x00. And it is working perfectly well in
> another machine.
Again, there is a distinct lack of details. You can't just say it
doesn't work. You have to describe the failure.
>
> Ok. Tell me what info to gather. Any preferred benchmarks?
Again, you didn't sho
; liked taking a closer look at it I could provide them with access to the
> machine (and its console). I ran out of clues...
Hard to tell really without more info. We don't know what your test
programs do, so it's impossible to predict what their behavior
should or shouldn&#
get a src/sys/modules/an/Makefile for compiling
the Aironet driver module.
-Bill
--
=====
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecom
contents of the mbuf!! Show is what it thinks the real
length is!
-Bill
--
=====
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home: [EMAIL PROTECTED] | Columbia University, New York City
=
DB, but *WITHOUT* USB support.
- Boot this kernel.
- Type kldload usb
- See if the system crashes.
- If it does, it will drop into the debugger.
- Type 'trace'
- Report what it says.
-Bill
--
=
-Bill Paul
that. Some don't, which can make your life tough.
I'm pretty sure the speed and duplex setting don't really have anything
to do with this particular problem though. I was just wondering why
renegotiating the media would have any effect. It's possible that
dc_init() may be cal
eople are having the same
problem and simply never bothered to tell me.
> And watch what happens after I managed to 'ifconfig dc0 media auto',
> it goes back to normal... suddenly everything is working properly
> again.
And what happens if instead of auto, you u
sure I want to waste a whole
cluster just for that case.
-Bill
--
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home: [
wrong. You could
calculate it from the data buffer length, but I suck at math; I find it's
easier just to monitor the offending frames.
-Bill
=
-Bill Paul(212) 854-6020 | System Manager, Master of U
Of all the gin joints in all the towns in all the world, Matthew Dillon
had to walk into mine and say:
> I'm adding Bill Paul to the list specifically.
>
> Hmm. Now this is odd! I think I may have found something!
>
> All of my 'rl' driver cards
y insights, please feel free to share
them.
-Bill
--
=====
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home: [EMA
t uses a
Macronix chip, however it was never sold in the U.S., only in Asia.
-Bill
--
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telec
s are 10Mbps only versions. If
you have a NIC that doesn't work, please show me the output of
pciconf -l from your system when reporting a problem.
As usual, the place to complain is: [EMAIL PROTECTED]
-Bill
--
=====
ee, I intend to remove the
al, ax, dm, pn and mx drivers and man pages since they should no
longer be needed. Please remember to update your rc.conf files
accordingly! I will post an additional heads up when I finally do
the deed.
-Bill
--
======
es anybody have
anything against me transfering support for the 21143 from if_de to
if_dc? Does anybody have a better idea? I'm open to suggestions.
-Bill
--
=====
-Bill Paul(212) 854-6020 | System Manager, Master o
Of all the gin joints in all the towns in all the world, Boris Popov had
to walk into mine and say:
> On Wed, 20 Oct 1999, Bill Paul wrote:
>
> > install -c -s -o root -g wheel -m 555 mount_nwfs /vol2/release/sbin
> > install: mount_nwfs: No such file or directory
>
e for those who do! :)
You work for Intel yet claim technical ignorance? I dunno man... :)
-Bill
--
=====
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for
idn't it stop at the compilation failure?
I suspect the answer has to do with some sort of obj directory problem,
but it's impossible to tell that based on the build report.
-Bill
--
=====
-Bill Paul(212) 854
you run the comparison on the same hardware. Comparing
a PIII 600Mhz host running Linux to a PII 300Mhz host running
FreeBSD is not a fair comparison. Unless FreeBSD ends up being
faster. :)
-Bill
--
=
-Bill P
funny.
I know what you're thinking: "why is he being so nasty?" Because I can't
stand it when people expect me to play the "minimum information" game,
and you are by no means the first. Some people may be able to read a
chewing gum wrapper and divine the secre
n, make sure the link light is lit. Try to ping somebody
on the network (or run tcpdump on the interface). You can't just
sit there and look at it: you have to experiment.
-Bill
--
=
-Bill Paul(212) 854-602
anymore.
Specifying media 100baseTX without mediaopt full-duplex implies
half-duplex. Leave off the mediaopt half-duplex part and it will work.
-Bill
--
=====
-Bill Paul(212) 854-6020 | System Manage
can't actually get my hands on.
> Thanks for the help. I seem to be over the hump on the wb interface
> anyway.
I trust this means it's actually passing traffic.
-Bill
--
=====
-Bill Paul(212)
t. I would suggest a similar punishment for those who
break our own build, except that I suspect many of you are wearing
viking hats already.
-Bill
--
=====
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
.
Dammit. You didn't even tell me what kind of card you have. Do you
really need me to ask you for this? Go back and boot the kernel in
verbose mode and show me *EXACTLY* what it says.
-Bill
--
=
-Bill Paul
omebody notices a problem, please let me know immediately. For
that matter, if you notice an improvement, let me know as well.
-Bill
--
=====
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work
y
is with the embedded 3c905B NIC in some of the Dell machines in the
lab, which aren't currently running FreeBSD.
Don't you just love hardware programming?
-Bill
--
=
-Bill Paul(212) 854-6020 | System
ad xl
Or you can include the following in /boot/loader.conf and reboot:
mii_load="YES"
xl_load="YES"
-Bill
--
=====
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work:
ed by
ifconfig (active or no carrier).
-Bill
--
=====
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home: [EMAIL PR
don't want to find out
what first prize is.
-Bill
--
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home: [EMAIL PROTECTED] | Columbia University, New York City
==
.
-Bill
--
=====
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home: [EMAIL PROTECTED] | Columbia University, New York City
=
&quo
the ISA graphics
adapter for some reason.
Anybody have any bright ideas where I can start looking for the problem?
-Bill
--
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EM
rface description file escaped before I
could commit it with the rest of the miibus code. Okay, I just fixed
it. Thanks for the heads up and sorry for the trouble. My turn to
wear the pointy hat again.
-Bill
--
=====
-Bill Pa
y have any bright
ideas?
-Bill
--
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home: [EMAIL PROTECTED] | Col
y curious to see what effect it has.
If you notice any improvements (or not), please let me know at
[EMAIL PROTECTED]
-Bill
--
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home: [EMAIL PROTECTED] | C
g different, I'll be happy
to try it out.
Not a bad day's work. :)
-Bill
--
=====
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Tele
with the FreeBSD server). I think this
was just a consequence of the filesystems being laid out differently.
The patched FreeBSD client works fine now with the SGI server.
-Bill
--
=
-Bill Paul(212)
if (newvp == vp)
> + vrele(newvp);
> + else
> + vput(newvp);
> newvp = NULLVP;
> }
> nfsm_dissect(tl, u_int32_t *, NFSX_UNSIGNED);
>
--
=
not related to the transport.
Anybody have any ideas? I did my good deed for the day.
-Bill
--
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center fo
rade the other SGIs without
worrying about them clobbering my FreeBSD machines.
Hm. I wonder what would happen if the FreeBSD host was the client
and the SGI was the server.
-Bill
--
=
-Bill Paul(212) 854-6020 | Sys
SIGNED + nlen + rem);
Should this be 7 * NFSX_UNSIGNED or is it correct as it is. I don't
know how dirlen relates to the entryplus3 structure.
-Bill
--
=
-Bill Paul(212) 854-6020 | System Manager, Master
a string bytes, plus padding to a longword
boundary, *plus* a longword length value. Some comments would have been
useful here. (Hint, hint.)
What I don't know is whether or not the calculation for dirlen is
wrong or not. Hopefully now that I've shown everyone the light, maybe
somebody can tell
le to do is snoop the requests
coming from the SGI but that's hard since they're encapsulated in a TCP
stream.
-Bill
--
=====
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL
d you elaborate
a *lot*. A whole lot.
>We need to fix that panic to have it simply drop the packet, I guess.
No, we need to fix the code so it handles 32K "packets" (datagrams)
correctly.
-Bill
--
=====
-Bil
EST i386
Should be in there. I don't think that's it.
Note that the 'mbuf siz' value that gets printed is the exactly the
same every time.
-Bill
--
=
-Bill Paul(212) 854-6020 | System Man
ection would be useful.
-Bill
--
=====
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home: [EMAIL PROTECTED] | Colu
1 - 100 of 139 matches
Mail list logo
