Re: Serious Network Troubles (with vx driver?)
On Wed, 19 Apr 2000, Oliver Schonefeld wrote: i recently updated my -current system from -current as of about mid-march to lest sundays's -current (jep, from 4.0 to 5.0) due to the work done to the ida driver. well, the ida driver seems to work, but the network hast complety stopped working. with sunday's -current, after about 2-5 minutes uptime i want not able to even ping machines on my local network. i cvsu'ed to tuesday's -current and pinging of machines some how worked. but resolving of hostname does not work properly. i added "options debug" to my /etc/resolv.conf and i get a lot of "server timeout" messages. after 3-6 failures i get an anwser. i know for sure, that the name servers are ok and i can also ping them, so it must have to do with my system. well, also all tcp/ip connections fail. cvsup failes with a connection timeout and connecting with ssh fails also with the same message. netstat -i shows nothing unusual (no tx/rx errors) and netstat -a shows just an "ESTABLISHED" and the rx/tq queues are empty. i have the bad feeling something is broke with the vx driver, since no one else is having such problems. any suggestions? any ideas? the machine is a compaq prosignia 486 _eisa only_, the boards are 3com 3c597 eisa. the machine worked very well and stable under 4.0 -current. northing unusual is shown, when booting the 5.0 -current kernel and all hardware is detected normally. unfortunalty i am not having a dmesg output here, since i am not home. i am currently building world cvsup'ed as of 7:20 GMT+1 and will see, what happens but i have the bad feeling my network will still be broken ... regards, oliver Its happening for me with the xl driver. With a 3COM 905B-TX card running at 10Base-T/UTP on a PII-266 running -CURRENT as of about 12 hours ago (from ctm-cvs-cur updates). I cant startx the X server because it crashes with signal 10 or 6 (Cirrus Logic GD5465 AGP card) but I don't know if thats -CURRENT related because its the first time I've tried XFree86-4 on this card (XFree86 3.3.5 had some problems and I haven't tried 3.3.6). So... I've been running Netscape 4.72 on it and displaying it on my Sparc Station 10 running Solaris 7 but I've been getting weird networking problems with intermitant inability to resolve hosts. Netscape seems to come up fine but I didn't do any browsing, just reading email. Popping my email down seemed to take a very long time. Kshisen took forever to come up (I didn't think it was going to) and it played so badly that I quit from it straight away. The network is fine as the Sun is fine at talking to other hosts and resolving (and the 2000 people using the network are not having problems.). It feels like TCP/IP is broken. I didn't look at any stats cos I didn't know what to look at. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: error reports by rshd in /var/log/messages
On Sun, 9 Apr 2000, John Polstra wrote: In article [EMAIL PROTECTED], Matthew Sean Thyer [EMAIL PROTECTED] wrote: I stopped the messages by adding the following line below the rshd line in /etc/pam.conf rshdauthrequiredpam_permit.so The way PAM works, that will let _anybody_ login via rsh without a password. I don't think it's what you want. John Wont this only happen when rshd becomes PAMerised ? or has that happened already ? If its already been done, why the console messages ? If it hasn't been done yet I suppose I wont notice when it gets done and then I'll be open. So whats the situation and what should people have in their pam.conf to eliminate these messages ? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: error reports by rshd in /var/log/messages
On Fri, 7 Apr 2000, Mohit Aron wrote: Hi, I'm using FreeBSD-4.0-RELEASE on a Xeon processor. The following messages have been appearing in my /var/log/messages file apparently upon an rlogin to the machine: Apr 7 00:23:16 idli rshd[236]: no modules loaded for `rshd' service Apr 7 00:23:16 idli rshd[236]: auth_pam: Permission denied Apr 7 00:23:16 idli rshd[236]: PAM authentication failed Can someone suggest if there's anything that needs fixing in the system. Thanks, I gather that these messages occur because rshd has not been PAMerised yet. I stopped the messages by adding the following line below the rshd line in /etc/pam.conf rshdauthrequiredpam_permit.so To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0(current) on a 486SLC2 ?
You'll need to make custom install disks with the floating point emulator in the kernel since you dont have a FPU with that processor. On Fri, 18 Feb 2000, Kelvin Farmer wrote: Hi, I was wondering if its possible to run FreeBSD-4.0 on a 486 SLC2 66mhz. (win95 runs on this computer ok) I downloaded the floppies from Feb.14th, and disabled the hardware I don't have but the boot panics at: ... npx0:math processor on motherboard npx0:Using IRQ 13 interface Fatal trap 12: page fault while in kernel mode ... (if useful I can copy down the rest of this panic) It doesn't have a pci bus, so my guess is that it dies probing the isa bus ??? Thanks, Kelvin [EMAIL PROTECTED] 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: Mylex Support
Are there any particular preparation processes one should go through when setting up a Mylex DAC960 RAID array ? (if so give me a pointer to the docs) Can I just purchase all the hardware, plug in the disks and boot the FreeBSD-4 install floppies ? (for a system to be booting from the array with no internal ATA devices) or Should I have an internal ATA hard disk with some evil OS on it such as Lose 9X or NT so as to run any kind of Mylex DOS/Windows preparation utilities ? On Fri, 10 Mar 2000, Mike Smith wrote: I have 4 different Mylex DAC960 controllers that I cannot install Current onto. (Tried from Late December to 2307). Sysinstall seems to get the geometry wrong, and even telling sysinstall the "correct" geometry, it gives a "tied to write beyond end of drive" error. Booting from a running -current and formatting does the same. They all have the latest BIOS, and they have been tried with various drive combinations. Has anyone else got this to work successfully or is it just me?. Obviously; you're actually the _only_ person I've heard from with this problem. And if it is just me, anyone got any ideas? I have been pestering Mike Smith about this for ages, and have probably driven him mad! More or less. As I've said - I have no idea what's going on for you at the moment; everything here "just works" like it should. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! old wd driver going away
Please leave the wd driver for those who cannot use the ATA driver. At least until the ATA driver gets support for more older disks. I cant be the only person using an old 80 MB IDE drive as / with another drive as /usr (a 400 MB SCSI). I haven't tried for a couple of months but the ATA driver didn't work over several different world builds back then and I haven't seen commits to indicate it will work now. dmesg from a less than a week old -CURRENT says the disk is: wdc0: unit 0 (wd0): Maxtor 7080 AT-TTT, 32-bit, multi-block-16 wd0: 77MB (158440 sectors), 932 cyls, 10 heads, 17 S/T, 512 B/S wdc0: driver is using old-style compatability shims Lots of people may say "buy new hardware" but the fact is that my 486DX4-100 with these crappy old disks does extremely well as my user-mode ppp connection to the net using NAT. It also runs a DHCP server, Squid proxy server, name server, and IMAP server very nicely. I also have no money for my FreeBSD hobby. Some of you will say "stick with 4.0-RELEASE or earlier" and thats what I'll have to do if wd goes but I do prefer to keep all 3 of my machines running -CURRENT so I can easily recover from bad -CURRENT experiences by grabbing binaries from another machine etc... (Of course I build world on the Celeron 300a and install it on the others). On Tue, 14 Mar 2000, Soren Schmidt wrote: It seems Bruce Evans wrote: On Tue, 14 Mar 2000, Jeroen Ruigrok van der Werven wrote: Yes... That's right. Use ata and related stuff instead. No. Yes. -Søren 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: current lockups
I'll second this email... My computer had been stable all winter (with setiathome runnning full time) but suddenly come the Australian summer it started freezing. Not panicing, just totally freezing under load. I could reproduce it by trying to build the whole of KDE and each time it was a freeze, never a panic. Windows 98 was freezing too but I didn't think that was abormal ;/ It turned out to be heat related as the machine is now stable after I installed a case fan (before I only had the power supply fan and CPU fan). I see that the internal case temperature still gets up to about 50 or 51 degrees celcius whereas it was getting to 52 degrees before. Note that I AM overclocking a Celeron 300a to 450 MHz by running with a 100 MHz FSB instead of 66 MHz so I suppose I shouldn't be surprised at the need for better cooling. As I'd prefer better CPU cooling to the case fan on the grounds of noise, can people recommend good CPU fans (over the standard Intel retail version Celeron 300a fan) ? How about these Peltier (sp ?) cooling devices I have heard about ? On Sun, 5 Mar 2000, Dan Papasian wrote: 1. Is your computer overclocked? 2. Is the computer totally frozen? (i.e. scroll lock doesn't turn the light on) 3. Does similar load crash the box as well? (try make -j2 world) 4. Does it freeze in the same spot? 5. Is the computer not responding to pings? If you've answered yes to a good amount of these questions, there is a good chance that your processor(s) are overheating. Try improving the airflow to the case (But using a household fan isn't recommended due to EMI) -Dan Papasian [EMAIL PROTECTED] On Sat, Mar 04, 2000 at 11:50:10PM -0800, Arun Sharma wrote: Compiling Mozilla with make -j 2 got -current to lock up, twice in succession. I'm running a fairly recent snapshot (a week or two old) on a Dual celeron box (BP6) with UDMA66 enabled. The kernel had DDB enabled. I was running X, but I didn't see any signs of the kernel attempting to get into the debugger. Has this been fixed ? Is anyone interested in investigating ? I'll post more info if I find anything. -Arun 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
Re: Hardwiring SCSI device ID broken?
Barry, I think I know the problem you have. When "device scbus0" changed to "device scbus" in LINT and I applied that to my config file I found I could no longer wire down my disks to scbus0 unless I changed the base SCSI code line back to "device scbus0". This is what I have: device scbus0 # Base SCSI code device da0 at scbus0 target 0 device da1 at scbus0 target 1 device da2 at scbus0 target 2 device da3 at scbus0 target 3 device da4 at scbus0 target 4 device da5 at scbus0 target 5 device da6 at scbus0 target 6 And it works fine. On Mon, 7 Feb 2000, tele danmarQ kvindeservice wrote: On Mon, 7 Feb 1900, Noted Usenet Pedophile Barry Bouwsma wrote: More about this later. Here's more now: Here is FreeBSD-*STABLE* as it properly wires the devices to where I want them to be (highlighted by ^) The kernel configuration looks like this (meat stripped away) machine "i386" cpu "I586_CPU" ident FLUFFY controllerahc0# AHA2940 and onboard AIC7xxx devices controllerscbus0 # SCSI bus (required) deviceda0 # Direct Access (disks) devicecd0 # CD devicepass0 # Passthrough device (direct SCSI) devicewt0 at isa? port 0x308 bio irq 3 drq 3 disk da0 at scbus0 target 1 Feb 6 18:30:22 netscum syslogd: exiting on signal 15 Feb 6 20:25:42 netscum /kernel: Copyright (c) 1992-1999 FreeBSD Inc. Feb 6 20:25:42 netscum /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Feb 6 20:25:42 netscum /kernel: The Regents of the University of California. All rights reserved. Feb 6 20:25:42 netscum /kernel: FreeBSD 3.4-STABLE #5: Sat Jan 29 03:35:23 CET 2000 Feb 6 20:25:42 netscum /kernel: [EMAIL PROTECTED]:/usr/src/sys/compile/FLUFFY Feb 6 20:25:42 netscum /kernel: Timecounter "i8254" frequency 1193182 Hz Feb 6 20:25:42 netscum /kernel: CPU: Pentium/P55C (167.05-MHz 586-class CPU) Feb 6 20:25:42 netscum /kernel: Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Feb 6 20:25:42 netscum /kernel: Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX Feb 6 20:25:43 netscum /kernel: real memory = 67108864 (65536K bytes) Feb 6 20:25:43 netscum /kernel: config di wdc1 Feb 6 20:25:43 netscum /kernel: config q Feb 6 20:25:43 netscum /kernel: avail memory = 61956096 (60504K bytes) Feb 6 20:25:43 netscum /kernel: Preloaded elf kernel "kernel" at 0xc031c000. Feb 6 20:25:43 netscum /kernel: Preloaded userconfig_script "/boot/kernel.conf" at 0xc031c09c. [...] Feb 6 20:25:43 netscum /kernel: ide_pci0: Intel PIIX3 Bus-master IDE controller rev 0x00 on pci0.7.1 Feb 6 20:25:43 netscum /kernel: ahc0: Adaptec 2940 Ultra SCSI adapter rev 0x00 int a irq 11 on pci0.10.0 Feb 6 20:25:43 netscum /kernel: ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs [...] Feb 6 20:25:43 netscum /kernel: wt0 not probed due to drq conflict with pcm1 at 1 Feb 6 20:25:44 netscum /kernel: ppc0 at 0x378 irq 7 flags 0x40 on isa Feb 6 20:25:44 netscum /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Feb 6 20:25:44 netscum /kernel: ppc0: FIFO with 16/16/16 bytes threshold Feb 6 20:25:44 netscum /kernel: lnc0 not found at 0x280 Feb 6 20:25:44 netscum /kernel: vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa Feb 6 20:25:44 netscum /kernel: npx0 on motherboard Feb 6 20:25:44 netscum /kernel: npx0: INT 16 interface Feb 6 20:25:44 netscum /kernel: Intel Pentium detected, installing workaround for F00F bug Feb 6 20:25:44 netscum /kernel: IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry by default Feb 6 20:25:44 netscum /kernel: ccd0-3: Concatenated disk drivers Feb 6 20:25:44 netscum /kernel: changing root device to da0s3a Feb 6 20:25:44 netscum /kernel: da1 at ahc0 bus 0 target 0 lun 0 Feb 6 20:25:44 netscum /kernel: da1: IBM DPES-31080 S31Q Fixed Direct Access SCSI-2 device Feb 6 20:25:44 netscum /kernel: da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled Feb 6 20:25:44 netscum /kernel: da1: 1034MB (2118144 512 byte sectors: 255H 63S/T 131C) Feb 6 20:25:44 netscum /kernel: cd0 at ahc0 bus 0 target 6 lun 0 Feb 6 20:25:44 netscum /kernel: cd0: SONY CD-ROM CDU-561 1.9i Removable CD-ROM SCSI-2 device Feb 6 20:25:44 netscum /kernel: cd0: 4.032MB/s transfers (4.032MHz, offset 15) Feb 6 20:25:44 netscum /kernel: cd0: cd present [328664 x 2048 byte records] Feb 6 20:25:44 netscum /kernel: da0 at ahc0 bus 0 target 1 lun 0 Feb 6 20:25:44 netscum /kernel: da0: IBM DCAS-34330 S65A Fixed Direct
Re: Make world problems
On Tue, 1 Feb 2000, Edwin Culp wrote: Marc Schneiders wrote: Some problems have disappeared, some remain, to wit: /kernel: cmd ntpd pid 86 tried to use non-present sched_get_priority_max /kernel: cmd ntpd pid 86 tried to use non-present sched_setscheduler ntpd [86]: sched_setscheduler(): Function not implemented (I've checked, ntpd was built.) And when doing startx: /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol "_vt$9exception" You need to rebuild all libraries built from C++ source and all programs that use such libraries due to the recent changes with the way we use gcc 2.95.2. Now which programs and libraries use C++ ? I dont know, I found it easiest to uninstall all packages by repeatedly running: "pkg_delete `pkg_info | cut -d\ -f1`" until there was only XFree86 left and then forceably deleting that and then rebuild everything. (better build your shell real quick!). Its not too bad now that a Celeron 450 with an IBM UDMA33 disk can build XFree86 (only SVGA server + a.out,staticdynamic,PAM) and windowmaker in less than 50 minutes. I'm sure you could examine all your binaries for which libraries they use and then pkg_delete the appropriate packages but I thought I might as well update the whole system since its so easy with the FreeBSD ports collection (I could do with a DSL link though ;). (Why do some (or all?) packages fail to de-register themselves as being dependent on XFree86 ?... I only have to use pkg_delete -f with XFree86). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
