Re: Linksys LNE100TX
Hmmm...I believe mine is s LNE100TX...I know it's a Linksys, and it's a 10/100 PCI..and it's runnin fine under Current (last make world was about a week ago), as pn0 in my config: device pn0 # Lite-On 82c168/82c169 (``PNIC'') and from dmesg | grep pn0 : pn0: 82c169 PNIC 10/100BaseTX irq 10 at device 12.0 on pci0 pn0: Ethernet address: 00:a0:cc:22:dd:4f pn0: autoneg complete, link status good (full-duplex, 100Mbps) Is it possible that the card you bought could be defective? (have you tried under a release or stable build?). Douglas Kuntz Systems Administrator PC Tech Reports http://www.pctechreports.com ---FreeBSD... The choice of the smart generation--- - Original Message - From: Edwin Culp [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, September 30, 1999 11:07 AM Subject: Linksys LNE100TX | Fry´s was out of Intel 100/10 ethernet cards, so I bought a Linksys | LNE100TX remembering that I there was a driver for it. | | I added | device pn0 | to my kernel configuration and compiled the kernel. It was not detected | during boot. I added the mii_bus0 controller just in case. Recompiled | and still not detected. | | Does anyone have the LNE100TX working in current? | | Thanks, | | ed | | | | To Unsubscribe: send mail to [EMAIL PROTECTED] | with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Iomega Ditto Max Parallel
Has anyone had any success using the parallel version of the Iomega Ditto Max with current, or is there any support for it? Douglas Kuntz To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Ditto Max
Since I dont think my other mail made it through...(since I didnt see it, or any replys) Has anyone gotten an Iomega Ditto Max drive to work on 4.0? I have both types, Floppy/ditto dash card and Parallel port, and would like to use it to back up my drive every week or so. Thanks Douglas Kuntz To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
oops
ok..disregard my 2nd mail...damn @home takes forever to send out mail *goes to a corner* To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Boot error
Ok...for hardware, all I have in the machine is: A Linksys 10/100 ethernet (uses pn0) A SCSI card (uses bt0) A S3 Virge video card A FIC VA-503+ motherboard w/ 32meg PC66 sdram and a K6-2 400 the only thing changed between the 2 machines was the other was a Shuttle Socket 370 motherboard, and a Celeron 366 cpu. Everything was moved from one case/motherboard to the other case/motherboard. The kernel had "ata" compiled in, the options for my hardware, and the basic floppy and video, nothing that I though was unusual. Sorrry about the way I typed before...I actually talk like that (or worse) half the time, and I have to remember when to talk/type normally. Doug - Original Message - From: "Mike Smith" [EMAIL PROTECTED] To: "Douglas Kuntz" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, November 26, 1999 3:32 AM Subject: Re: Boot error First things first; try using English for your problem reports. A large slice of the community that might be able to answer your questions don't use it as their first language, and by using leet-speek you immediately eliminate them as a source of help. Before I go do a fresh SNAP install, I wanted to see if there was an easier way to fix this problem... My -current box was a celeron...I had to switch the celeron and mboard to my windoze machine to get a vidcard werkin...I recompiled the kernel to 486, 586, and 686, and moved the HD, the cards, etc, over to the K6-2 400 I had...now, everytime at boot, before it even prompts for which OS to start, it has a bootloader problem...if I recall it was something like: BTX 1.0.0 BTX Loader 1.0.1 then "System Halted" I tried the fixit floppy, etc, and that partially worked, but locked when it was mounting the filesystem. I'm sorry that I cant provide any more info...I only have 1 monitor and cant copy/paste between 2 pcs. I'm sorry, but without a lot more information all I can say is "you done something wrong". You might start with an exhaustive list of the relevant hardware in the actual system in question, followed by the actual set of physical changes which took it from "working" to "not working". We're not telepathic, and we don't have the time to hunt you down and steal all your hardware to solve your own problems, so you're going to have to help us out here. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Old Libs...?
The way I worked around the libs problem was: instead of installing through /stand/sysinstall, I installed through /usr/ports, as that rebuilds the binary using the libs that 4.0 comes with. So far, everything's worked semi-perfectly (well, bash and samba work fine..as do the rest of the ports I've installed) Douglas Kuntz Editor PC Tech Reports - Original Message - From: "Dieter Rothacker" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, December 06, 1999 6:22 AM Subject: Old Libs...? Hi, I have just installed 4.0-SNAP-19991203. I noticed that some packages (e.g. samba, bash2) complain about missing shared libs (e.g. libreadline.so.3 needed and .4 is installed). Reading similar things in the mailing list archive, I assume that I have to install the old libs from a 3.3-stable BIN. Correct? How do I find out which bin-archives I really need to download? I looked at the mtree-file, but did not find the exact arc files mentioned. I do not want to download all bin.* files. Please forgive me if the solution should be obvious, it is my first try at FreeBSD. -- Dieter Rothacker To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Intel 810?
As others have stated, Socket370 boards arent all 810/810c...my 4.0-Current machine was, until last week, a Celeron 366 Socket370 on a Shuttle 440LX board. Though, as far as I can tell, if you're going to use a Celeron PPGA chip, save money and go with the LX or Via chipset based boards, and use the saved money on ram or a larger harddrive. Celerons are all 66mhz bus speed...though, Intel has said they plan on releasing Socket370 Pentium IIIs in 2000. Though, on a sidenote, I really see no reason on getting a 100mhz Socket370 board to run a Pentium III on later, when, except for the clock speed increase, a P3 is the same as a P2 with just the addition of SIMD extensions, which I dont think FreeBSD uses yet. Douglas Kuntz Editor PC Tech Reports http://www.pctechreports.com - Original Message - From: "Garrett Wollman" [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, December 06, 1999 2:23 PM Subject: Intel 810? I recently got a quote from a hardware vendor which made the following claim: All Socket 370PGA Motherboards use either the 810 or [the] 810c chip set which does not support FreeBSD because 16MB of the motherboard memory is used for the display controller. There is no way to tell the FreeBSD kernel not to use this memory so it will corrupt data. I find this statement rather dubious. Can anyone out there say with more certainty? -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Intel 810?
By 66mhz, thats what Intel rates them at...I'm runnin my 366 at 75mhz (412.5mhz)...but they're only designed for 66mhz. Plus, you cant OC the Socket370 chips the same as with the older 300/300a and most of the Slot1 chips. The Socket370 CPUs dont have clock multiplier options, only bus speed options. But as for Micro-ATX, Shuttle makes several Socket370 440BX boards in Micro-ATX, and FIC sells a LX based Micro-ATX board (never used a FIC board w/ a Pentium, however, only AMD). But, I'm willing to guess most board manufacturers sell MicroATX boards for the Socket370...and if not, and you really like the board, and it's a P2/P3 board, you can always get a Socket370 to Slot1 converter card ("slocket") Douglas Kuntz Editor PC Tech Reports http://www.pctechreports.com - Original Message - From: "Sean Jensen-Grey" [EMAIL PROTECTED] To: "Douglas Kuntz" [EMAIL PROTECTED] Cc: "Garrett Wollman" [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, December 06, 1999 7:46 PM Subject: Re: Intel 810? whoa. Celerons are whatever bus speed you set them to (not 66). I see no reason to buy a PIII when I can very reliably over clock a celeron processor. I have 5 Celeron SMP machines all running FreeBSD. They are celeron 300a OCd to 450 running on the Abit BP6 MB. Never a problem. I even have a pair of 366 Mhz chips overclocked to 550. My 4.0 Current machine is a dual celeron 450. please reference http://www.sharkyextreme.com http://www.arstechnica.com for info on overclocking. Abit boards are the defacto standard for over clocking. Sean. On Mon, 6 Dec 1999, Douglas Kuntz wrote: As others have stated, Socket370 boards arent all 810/810c...my 4.0-Current machine was, until last week, a Celeron 366 Socket370 on a Shuttle 440LX board. Though, as far as I can tell, if you're going to use a Celeron PPGA chip, save money and go with the LX or Via chipset based boards, and use the saved money on ram or a larger harddrive. Celerons are all 66mhz bus speed...though, Intel has said they plan on releasing Socket370 Pentium IIIs in 2000. Though, on a sidenote, I really see no reason on getting a 100mhz Socket370 board to run a Pentium III on later, when, except for the clock speed increase, a P3 is the same as a P2 with just the addition of SIMD extensions, which I dont think FreeBSD uses yet. Douglas Kuntz Editor PC Tech Reports http://www.pctechreports.com - Original Message - From: "Garrett Wollman" [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, December 06, 1999 2:23 PM Subject: Intel 810? I recently got a quote from a hardware vendor which made the following claim: All Socket 370PGA Motherboards use either the 810 or [the] 810c chip set which does not support FreeBSD because 16MB of the motherboard memory is used for the display controller. There is no way to tell the FreeBSD kernel not to use this memory so it will corrupt data. I find this statement rather dubious. Can anyone out there say with more certainty? -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
mcrypt
While trying to compile the Apache13-php3 port, with mod_ssl, and encryption, I get the following error: -c functions/mcrypt.c -o functions/mcrypt.o functions/mcrypt.c:172: #error Please update your mcrypt library *** Error code 1 Is this a ports problem, or a current problem? Thanks in advance. Douglas Kuntz - Original Message - From: "John Polstra" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, January 23, 2000 2:27 PM Subject: Re: rtld-elf, java + tya ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 If any of you can reproduce this problem fairly reliably, please try the appended patch for "src/libexec/rtld-elf/lockdflt.c" and let me know if it solves the problem. Thanks, John Index: lockdflt.c === RCS file: /home/ncvs/src/libexec/rtld-elf/lockdflt.c,v retrieving revision 1.3 diff -u -r1.3 lockdflt.c --- lockdflt.c 2000/01/09 21:13:48 1.3 +++ lockdflt.c 2000/01/23 19:03:26 @@ -28,10 +28,9 @@ /* * Default thread locking implementation for the dynamic linker. It * is used until the client registers a different implementation with - * dllockinit(). The default implementation does mutual exclusion - * by blocking the SIGVTALRM, SIGPROF, and SIGALRM signals. This is - * based on the observation that most userland thread packages use one - * of these signals to support preemption. + * dllockinit(). The default implementation does mutual exclusion by + * blocking almost all signals. This is based on the observation that + * most userland thread packages use signals to support preemption. */ #include dlfcn.h @@ -63,10 +62,13 @@ l = NEW(LockDflt); l-depth = 0; -sigemptyset(l-lock_mask); -sigaddset(l-lock_mask, SIGVTALRM); -sigaddset(l-lock_mask, SIGPROF); -sigaddset(l-lock_mask, SIGALRM); +sigfillset(l-lock_mask); +sigdelset(l-lock_mask, SIGTRAP); +sigdelset(l-lock_mask, SIGABRT); +sigdelset(l-lock_mask, SIGBUS); +sigdelset(l-lock_mask, SIGSEGV); +sigdelset(l-lock_mask, SIGKILL); +sigdelset(l-lock_mask, SIGSTOP); return l; } To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message