Hello, For fun, this last weekend I decided to update from 3.4-STABLE to -CURRENT and try out some of the new features. I grabbed the sources (cvsup) and following the directions in UPDATING managed to build everything and install everything. Whew! I then compiled a new GENERIC kernel and rebooted. Eeek! Failure! The -CURRENT GENERIC kernel choked when it tried to access my SCSI drives. Here's the details: Machine: PII-350 2/64MB RAM Number9 Motion 771 PCI video card Tekram 390U2W PCI SCSI3 controller card 1 Seagate Cheetah 4 GB drive 1 IBM UltraStore 36GB 10KRPM drive PS/2 mouse & keyboard Kingston EtheRx KNE100TX PCI 10/100 NIC While 3.4-STABLE worked well with the Tekram SCSI card (during boot I seem to recall seeing a few errors that did not stop booting and no errors seemed to occur later at all even under heavy disk usage), when I attempted to boot the -CURRENT kernel, here's what I saw: sym0: <895> port 0xc800-0xc8ff mem 0xe7001000-0xe70010ff,0xe7000000-0xe70000ff irq 9 at device 15.0 on pci 0 sym0: Tekram NVRAM, ID 7, Fast-40, LVD, parity checking ... Then the following two errors would repeat endlessly, scrolling forever shortly after the "Waiting 15 seconds for SCSI devices to settle" message: sym0: SCSI parity error detected: SCR=1 DBC=72580000 SBCL=af (noperiph:sym0:0:-1:-1): SCSI BUS reset detected. Since my userland was now -CURRENT, I was unable to reboot using my old 3.X kernel since even /bin/sh from 4.X would core dump (signal changes, I expect). So I then endeavord to find a 4.X kernel I could use to boot. I grabbed the floppies from the January 25th -CURRENT snapshot from current.freebsd.org and booted. The -CURRENT kernel on the floppy was happy to boot my Tekram SCSI system just fine with no errors. So I mounted my disks, rearranged things, unmounted the fixit floppy once I could use the tools on my drives, mounted the snapshot kernel floppy and copied the kernel from it. Now I can boot my system okay using that kernel. So now for my SCSI question(s) since I'm a -CURRENT newbie: what might the problem be, and where would I look to discover what changes between 25 Jan. and Feb. 3 and 5 may have occured that would result in the problems I describe above? Now for another unrelated question: My Kingston EtheRX KNE100TX 100/10 PCI net card works perfectly when I boot to Win98. I use it with a crossover cable to talk to another Win98 workstation. But every time I boot to FreeBSD, both 3.4-STABLE and -CURRENT equally detect the Intel DEC-clone 21143 chipset, detect the ethernet address, detect the 100baseTX connection and enable the port. I ifconfig the de0/dc0 card and it happily accepts things. But from there on out, it does not work. It refuses to send or receive traffic. I know the card works (that other "evil" OS is happy with it) and the cabling is fine. I've also heard others mention using similar cards using the Intel 21143 chips just fine. I'm stumped why this isn't working under FreeBSD. Any and all pointers/tips/answers/help appreciated! Aaron out. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
