bin/139146 still not right in FreeBSD 8.2 (-m32 on amd64)?
Just installed a fresh 8.2-stable on a brand-spanking-new 64-bit
machine...
But, when I try to build 32-bit programs I get problems linking,
and I stumbled onto PR bin/139146.
The PR mentions this quick test:
uname -sr && echo "int main () { }" > t.c && gcc -v --help 2>&1 | grep m32 &&
gcc -m32 t.c
which I try to get this output:
FreeBSD 8.2-RELEASE
-m32Generate 32bit i386 code
/usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when searching for -lgcc
/usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when searching for -lgcc
/usr/bin/ld: cannot find -lgcc
So - I'm wondering what the proper approach is on amd64 to build
32-bit applications?
- Thanks! -
- Dave Rivers -
--
riv...@dignus.comWork: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: bin/139146 still not right in FreeBSD 8.2 (-m32 on amd64)?
Thanks everyone! -B/usr/lib32 worked around the issue... - Dave Rivers - -- riv...@dignus.comWork: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Why Are You NOT Using FreeBSD ?
We used to have FreeBSD exclusively on desktops... Now, we have migrated to other desktops (mac) with FreeBSD running the build and file server... Why? Because - the mac updates itself! No pain, no installation, no keeping-up with mailing lists/announcements, just and its done. Mac OS has a nice X11 server, the Mac UI is good enough, you don't have to install/update anything, the "app store" is perfect for downloading/installing whatever a desktop user might need. It was just too alluring... So, FreeBSD runs our NFS file server, and we log into a larger FreeBSD machine to do builds, etc... but, the desktop has moved. One developer here uses Linux Debian for about the same reason, it's trivial to update (via the network) to new versions, etc... Our web site used to be FreeBSD-based, but it was just too cost-effective to get a virtual Linux box on the backbone and move everything to that. Our requirements aren't too big, so that works beautifully. There _are_ people doing virtual FreeBSD boxes in a similar fashion, but they were quote a lot more for the annual fee.. so, Linux it was... I suppose, in some sense, you could argue that MacOS is FreeBSD... - Dave Rivers - -- rivers Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Torrent clients bring pf-based firewall to its knees...?
Is there a main() function in your program? Are you building this for LE operation, or with the Systems/C runtime? If it's Systems/C, are you using the RENT library (and the -frent option on the compilation?) If you want to build a non-RENT program for USS, you can, but you have to set the appropriate environment varible under USS to execute it; as a USS program is executed with the code sections marked READ-ONLY. - Dave Rivers - -- riv...@dignus.comWork: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Torrent clients bring pf-based firewall to its knees...?
My apologies all, This was clearly not intended for this list :-) - Thanks - - Dave Rivers - > > Is there a main() function in your program? > > Are you building this for LE operation, or with the Systems/C runtime? > > If it's Systems/C, are you using the RENT library (and the -frent > option on the compilation?) If you want to build a non-RENT program > for USS, you can, but you have to set the appropriate environment > varible under USS to execute it; as a USS program is executed > with the code sections marked READ-ONLY. > > - Dave Rivers - > > -- > riv...@dignus.comWork: (919) 676-0847 > Get your mainframe programming tools at http://www.dignus.com -- riv...@dignus.comWork: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: setlocale howto
Dmitry Morozovsky <[EMAIL PROTECTED]> wrote:
>
> On Sat, 12 Aug 2006, Andrey V. Elsukov wrote:
>
> AVE> >On Sat, Aug 12, 2006 at 05:51:01PM +0400, Andrey V. Elsukov wrote:
> AVE> >> for(i = 0; i < sizeof(buf); i++)
> AVE> >> buf[i] = (char)toupper(buf[i]);
> AVE> >
> AVE> > buf[i] = (char)toupper((unsigned char)buf[i]);
> AVE> >Standard integer promotion promotes KOI8-R char codes like 0xd4 into
> 0xffd4.
> AVE> >Since such codepoints are not defined for KOI8-R, toupper returns them
> AVE> >unchaged, as specified in documentation.
> AVE>
> AVE> Thanks, this works! But why this example works on Linux without type
> conversions?
>
> Linux has unsigned chars by default, while FreeBSD (and other current *BSDs)
> signed.
>
> Even large projects like PostgreSQL stepped into this trap at least once ;-)
>
> Sincerely,
> D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
"Linux" does not have unsigned char by default.
This is a log from an x86 LINUX machine:
[linux]$ cat c.c
main()
{
char c;
unsigned char uc;
c = -1;
uc = -1;
printf("c is %d\n", c);
printf("uc is %d\n", uc);
}
[linux]$ uname
Linux
[linux]$ ./a.out
c is -1
uc is 255
The signedness of char is usually a hardware-related issue. If the
hardware provides a single instruction to load-and-sign-extend a
character, then char will typically be signed; if the hardware's
instruction to load a char (or a byte) does not sign-extend, then
the char will be unsigned.
For example, Linux on an IBM mainframe uses unsigned as the default
for 'char', while x86 Linux uses signed.
So, it could easily be that your particular Linux (on a particular
hardware implementation) uses unsigned as the default signedness for
char.
- Dave Rivers -
--
[EMAIL PROTECTED]Work: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sed and comma-delimited file
"SigmaX asdf" <[EMAIL PROTECTED]> wrote: > Yo; > > I have a series of comma-delimited text files with fourteen columns of > data and several hundred rows. I want to use a short shell script to > strip them of the last 9 columns, leaving the same file but with just > five of its columns. I can do it in C++, but that seems like > overkill. How would I go about doing it with sed or a similar > utility? Uh.. is there no reason the cut(1) program doesn't do this? #!/bin/sh cat file | cut -d',' -f1-5 > /tmp/t.$$ rm -f file mv /tmp/t.$$ file This doesn't preserve permissions, etc... but - it's pretty straight-forward. - Dave Rivers - -- [EMAIL PROTECTED]Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS == lock && reboot
I have found that if I kill rpc.lockd on the NFS server, most of the NFS issues I have (including a similar lock-up on 6.1-RELEASE) go away. Just wanted to throw that "out there". - Dave Rivers - > > Greetings, > Does anyone know when NFS and friends will be working again? I haven't > been able > to /safely/ use it from 4.8 on. I remember some talk on the list > sometime ago and > then it seemed to be resolved, as the discussion ended. So I thought it was > fixed. Seems not. :( > > My scenario; > mount host off root: > mount script exec'd follows... > > #!/bin/sh - > mount -t nfs host.domain.tld:/ /host > mount -t nfs host.domain.tld:/var /host/var > > confirm mount... > > # ls /host > .snapCOPYRIGHTbin > ... > usrvartmp > > OK looks good... > > # cp /path/to/approx/10Mb/file /host/path/to/dest/dir/ > > Fatal double fault > eis 0x0blah > eiblah blah0x > panic double fault > no dump device defined > rebooting in 15sec... > > Hmmm... that's not good. :( > > I can't remember all the "ei*" numbers between the Fatal and panic lines, > BUT I /can/ reproduce this at will - I simply need to copy a file larger > than a few k to a mounted host. Yes, this /does/ happen /every/ time. > > Any and all help with this will be /GREATLY/ appreciated. > > Thank you for all your time and consideration in this matter. > > --Chris > > > -- > panic: kernel trap (ignored) > > > > - > FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 > / ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS == lock && reboot
Hi Chris, Well - the NFS server is 4.5-RELEASE - a rather old box. Everything worked fine when the shop was all 4.x boxes, but as soon as we put in a 5.x or 6.x box - the NFS clients on those (5.x/6.x) boxes locked up hard if rpc.lockd was running on the 4.5-RELEASE server. On 4.x, rpc.lockd doesn't start automatically - since, as I understand it, rpc.lockd had "issues" in that timeframe. But, one of the developers here turned it on hoping to get real locking for /var/mail. So - I thought my problem might simply be the old rpc.lockd implementation in 4.x, and I didn't worry about it (since 4.x is out-of-service anyway.) However, this sounded _so_ familiar - I thought I would pop-up and mumble something like a "me too." rpc.statd isn't running on the 4.5 NFS server. - Dave Rivers - > > Quoting Thomas David Rivers <[EMAIL PROTECTED]>: > > > I have found that if I kill rpc.lockd on the NFS server, > > most of the NFS issues I have (including a similar lock-up on > > 6.1-RELEASE) go away. > > Ah hah! I wondered about this. Funny you mention it. The interesting > thing was that my most problem boxen is this one here, and it is the > /only/ one with: > > rpc_lockd_enable="YES" > rpc_statd_enable="YES" > > in rc.conf I simply chose these in an effort to keep everything current > and accurate. You don't happen to have any experiences keeping rpc.statd > running? > > Thank you for taking the time to reply. > > --Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Updated 6.1 schedule?
I've been watching the 6.1-RC1 web pages, etc... following the wonderful progress. However, the dates on the schedule page seem to be a little off now. I was wondering if anyone had some idea of what the new dates might be... if there's no idea; then I will patiently wait. I've got a few 4.10 machines that could do with an upgrade, and I don't think moving to 5.4 is the way to go... So, I'm pending waiting on 6.1. I'm not meaning to pressure or anything, beggars can't be choosers... just wondering if anyone has an idea... - Thanks! - - Dave Rivers - -- [EMAIL PROTECTED]Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Updating ncurses in base
Unfortunately, I won't be able to test the newer curses anytime soon... But - I did report some years ago that c3270 doesn't build with the current ncurses because of a name clash. If someone gets a chance, it might be a good idea to test that port with the newer ncurses. - Thanks - - Dave Rivers - > Hi, > > [I'm also CC'ed peter@ since he is the maintainer of ncurses in base] > > As you may know, the current ncurses in the base system is rather old > (it is 4 years old). I have been working on updating ncurses to the latest > version 5.5 and enable wide character as default. I have put the description, > goal, issues, current status, and tarball for test at the following URL: ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gcc profiling support?
I've tried FreeBSD 3.1 and a 4.2 snapshot.. But, when I use a small "hello world" program, and compile it with: gcc -pg hello.c and run the resulting a.out, I don't get the expected gmon.out. Is there some other magic that is needed? Is -pg not supported on -stable? - Thanks - - Dave Rivers - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: gcc profiling support?
David Malone <[EMAIL PROTECTED]> writes: > On Fri, Dec 22, 2000 at 08:51:14AM -0500, Thomas David Rivers wrote: > > > But, when I use a small "hello world" program, and compile > > it with: > > > >gcc -pg hello.c > > > > and run the resulting a.out, I don't get the expected > > gmon.out. > > It should be called a.out.gmon I think. > > David. > Ah... so it is... (makes sense - sorta analagous to core dumps) Well then, the `bug' is in gprof - it expects to see gmon.out. Perhaps just a note in the gprof man page would be enough? - Dave Rivers - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.3-STABLE panics while mounting CD-R
> > Is it an audio cd? I've experienced the instant panic when mistakenly > trying to mount such as a cd9660 fs. Of course it shouldn't panic, > but the workaround is not to do that. I get similar situations when mounting the 4.2-RELEASE 3rd CD for reading packages... This is with a 4.2-RELEASE system... From the boot messages: atapci0: port 0xd8 00-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 acd0: CDROM at ata1-master using PIO4 And here's an example: May 3 09:13:18 fjord /kernel: cd9660: RockRidge Extension May 3 09:14:02 fjord /kernel: acd0: READ_BIG - NO SENSE asc=00 ascq=00 error=00 May 3 09:14:12 fjord /kernel: acd0: READ_BIG - NO SENSE asc=00 ascq=00 error=00 May 3 09:15:00 fjord /kernel: acd0: READ_BIG command timeout - resetting May 3 09:15:00 fjord /kernel: ata1: resetting devices .. done May 3 09:15:30 fjord /kernel: acd0: READ_BIG command timeout - resetting May 3 09:15:30 fjord /kernel: ata1: resetting devices .. ata1-master: timeout w aiting for command=ef s=00 e=50 May 3 09:15:30 fjord /kernel: done May 3 09:15:56 fjord su: rivers to root on /dev/ttyp1 May 3 09:16:00 fjord /kernel: acd0: READ_BIG command timeout - resetting May 3 09:16:00 fjord /kernel: ata1: resetting devices .. ata1-master: timeout w aiting for command=ef s=00 e=50 May 3 09:16:00 fjord /kernel: done May 3 09:16:30 fjord /kernel: acd0: READ_BIG command timeout - resetting May 3 09:16:30 fjord /kernel: ata1: resetting devices .. ata1-master: timeout w aiting for command=ef s=00 e=50 May 3 09:16:30 fjord /kernel: done At which point the cdrom was hung and a reboot was needed... I can reproduce this when I NFS mount the CDROM with the 4.2-RELEASE Disk #2 in the drive. - Dave Rivers - -- [EMAIL PROTECTED]Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Headsup: Tcp ISN generation changes from 4.2 to 4.3
> > > > However, your patches do not apply cleanly to a 4.3-RELEASE > > system... are these meant for 4.3-STABLE only? > > Use this on 4.3-RELEASE only: > That's great! Thanks for taking the time to make a 4.3-RELEASE patch... it's much appreciated. Hopefully, this will happen to be the cause of my strange problems... - Dave Rivers - -- [EMAIL PROTECTED]Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Yamaha YMF744 sound is "clipped off"
I've discovered that (with 4.9-RELEASE), the snd_ds1.ko module is the appropriate one for my Sony VAIO PCG-F480. However, it seems the sound is "clipped off" at the end... it starts just fine, but then simply stops before it should. Anyone else seen (well heard) of something like this with 4.9-RELEASE? - Thanks! - - Dave Rivers - -- [EMAIL PROTECTED]Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: -stable (in)stability (was Re: Best version of FBSD for INN ?)
And - to add to this - I still can freeze up my pentium laptop rather quickly (3.2-RELEASE, 40meg memory, P90) running setiathome. And - I've got DDB in the kernel, and ensured it's not overheating (it will freeze up in less than a minute from a _very_ cold start.) I don't get a panic, ddb prompt or anything - just a locked up machine. - Dave Rivers - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
I've got a CD that can "lock up" the SCSI CD driver...
I'm using 3.3-RELEASE. And, I've got one CD that I can put in the drive. When I do so (if it's the first CD used since booting), I get the following message: Oct 1 09:31:02 lakes su: rivers to root on /dev/ttyp0 Oct 1 09:31:08 lakes /kernel: cd0 at ahc0 bus 0 target 4 lun 0 Oct 1 09:31:08 lakes /kernel: cd0: Removable CD-ROM SC SI-2 device Oct 1 09:31:08 lakes /kernel: cd0: 3.300MB/s transfers Oct 1 09:31:08 lakes /kernel: cd0: Attempt to query device size failed: NOT REA DY, Vendor Specific ASC The mount command will not complete. The CD drive is locked up, as it believes the CD-ROM is in-use. If you cntrl-C to interrupt the mount command, you do get a prompt; but you can't umount the CD (it didn't successfully mount) to clear up the in-use bit... So, you can't get the CD-ROM out of the drive. The only option is to reboot the machine. What's odd about this - is I can use just about any other CD-ROM, it just so happens this one particular one (the clip-art CD from WordPerfect) does this. I don't seem to be able to find another CD-ROM that causes the problem. As you can see - this is an HP 6020i. I'm also using an aha2940uw. It's possible this CD has problems (but it works fine in other machines.) It's possible that an HP 6020 has problems that this CD "tickles" - but, that should not "lock up" the driver. So, my issue is this - how do you clear a "partial mount" without rebooting? - Dave Rivers - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3.3 Stable Performance Monitoring
It turns out one of the principles at Empire Technologies is a friend of mine. I'll send him a note regarding a FreeBSD version and see what comes out of it. - Dave Rivers - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Solution to my 3.3-RELEASE panics!
> Thomas David Rivers wrote: > > > I'll have to attribute this to the "nut behind > > the wheel." Apparently, I must have done a > > config with some option (likely DDB) on and not > > done a clean build... (i.e. didn't do a `make clean; make') > > You shouldn't need to make clean... make depend; make should be enough. > > -- > Ben Smithurst| PGP: 0x99392F7D > [EMAIL PROTECTED] | key available from keyservers and > | [EMAIL PROTECTED] > I'm not sure. I'm _guessing_ this is what happened. config a brand kernel without options DDB. do a make - boot and run that kernel - all is fine. then, change the config file and add options DDB. Then, do make depend; make (which I believe is what I did.) But - some of the files that need to know that DDB is now defined are not recompiled (I'm guessing, I haven't checked on this.) - Dave Rivers - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
ASUS P2B-S and FreeBSD 3.3-RELEASE
Is anyone using FreeBSD 3.3 with an ASUS P2B SCSI? I believe this is an AHA 2940U2W "clone" - is that right? If you have been successful with a P2B-DS or P2B-LS, let me know, I _think_ I'm having a difficult time getting SCSI termination correct (but...) I didn't think 3.3-RELEASE had any problems with a aha2940u2w... Have people been successful with it? - Thanks - - Dave Rivers - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ASUS P2B-S and FreeBSD 3.3-RELEASE
> On Tue, 16-Nov-1999 at 09:19:48 -0500, Thomas David Rivers wrote: > > > > Is anyone using FreeBSD 3.3 with an ASUS P2B SCSI? > > I believe this is an AHA 2940U2W "clone" - is that right? > > > > If you have been successful with a P2B-DS or P2B-LS, let > > me know, I _think_ I'm having a difficult time getting > > SCSI termination correct (but...) > > I got a P2B-LS. Had lot of problems (kernel stopped booting > when it came to the SCSI controller) until I upgraded the > BIOS. > Sounds interesting - what version of the BIOS did you upgrade to? - Dave R. - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
XF86 sources?
I did a 3.3-RELEASE install from the CDROM, and asked for XF86 sources (all of them, actually.) After the install is finished, I don't seem to be able to locate the XF86 sources on the installed machine. Furthermore, looking over CDROM #1 - I don't seem to be able to find the sources there... (which may explain why they didn't get installed.) Perhaps the install needs to be updated? - Dave Rivers - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Don't use the "custom" install option for 3.4
Jordan wrote: > > Yes, there was a big rush with christmas this year or I would > not have released at all. Ah well, it's not like it leaves one > with no way to install FreeBSD at all. Is it safe to assume some new floppies will be built, and made available, with this bug corrected? Then, a safe way to install 3.4 is to download the floppies, and _then_ use the CD-ROM distribution (which is how I tend to go anyway...) - Dave R. - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Netscape/Linux on FreeBSD an other horrors ...
Just F.Y.I. I have found that the same Netscape binary running on FreeBSD 4.1 is much more reliable than that binary running on FreeBSD 3.x. I attribute this to the change in how FPU exceptions are handled. That is, Netscape is probably getting floating pt. underflows/overflows which it does not handle. In FreeBSD 3.x, this dumped core, in 4.1 it is ignored. This may "improve" FreeBSD's reliability. [Of course, it raises a question regarding 2.x compatibility; shouldn't a 2.x binary continue to dump core on FPU exceptions, even on a later system?] - Dave Rivers - -- [EMAIL PROTECTED] Work: (919) 676-0847 Get your mainframe (370) `C' compiler at http://www.dignus.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.1-RELEASE pccard?
Warner Losh <[EMAIL PROTECTED]> wrote: > > In message <[EMAIL PROTECTED]> Thomas David Rivers writes: > : Nope - I have a "SmartLink" NE2000 clone card; that does to > : 10/100 mbits/second... This is actually a re-labeled Archtek card. > > Ah. The light goes on. Does your config file look something like: > card "PCMCIA" "FastEthernet" > config auto "ed" ? 0x3 Warner, You asked that as if you had some info about this issue? [mine looks exactly like that.] Anything I can do here to get closer to working? - Thanks - - Dave R. - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.1-RELEASE pccard?
Just to add to this thread a little. I put the card in a 3.4-RELEASE machine (which works.) It seems to acquire a different MAC address than the 4.1.1 code does. In 3.4 PAO I get: Card inserted, slot 0 card0: assign ed0 iobase 0x300 irq 9 flags 0x3 ed0: address 00:10:60:38:3b:b7, type NE2000 (16 bit) I 4.1(.1) I get: ed1 at port 0x300-0x31f ir1 3 slot 1 on pccard1 ed1: address 01:02:00:ff:15:1d, type NE2000 (16 bit) it seems the MAC address on 4.1(.1) isn't working... (perhaps I will be hard-coding the MAC address after all.) - Dave Rivers - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
