Re: ZFS on top of GELI / Intel Atom 330 system
Ulrich Spörlein wrote: 2GB CF card + CF to ATA adapter (today, I would use 2x8GB USB sticks, CF2ATA adapters suck, but then again, which Mobo has internal USB ports?) Many has internal USB header. http://www.logicsupply.com/products/afap_082usb ___ 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: PXE boot FreeBSD without need of NFS server
Mikael Bak wrote: Links to documentation, hints and advises are greatly appreciated. http://phaq.phunsites.net/2007/02/14/convert-freebsd-iso-image-for-pxe-bootstrap/ ___ 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: ZFS MFC heads down
Kirk Strauser wrote: So far so good here (amd64, Core2 Duo, ICH9 SATA) but I'm too chicken to upgrade the on-disk format yet. Me too, upgraded pool to v13 yesterday and everything still ok. Removed also all loader.conf tunables. Many thanks for FreeBSD team. (Tyan Tank GT20, 2GB memory, ICH7, amd64) ___ 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: ZFS MFC heads up
Kip Macy wrote: I will be MFC'ing the newer ZFS support some time this afternoon. Both world and kernel will need to be re-built. Existing pools will continue to work without upgrade. Mounting local file systems:. internal error: out of memory internal error: out of memory internal error: out of memory internal error: out of memory I get this in dmesg after make installkernel shutdown -r now, zfs pool is not mounted. /usr is on zfs so can't installworld. 2GB memory and 4x 1TB raid-z on amd64, / is 2x 2GB gmirror. ___ 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: ZFS MFC heads up
Goran Lowkrantz wrote: Ran into the same thing on -CURRENT when we went version 13. Some manual intervention fixed it. http://lists.freebsd.org/pipermail/freebsd-current/2008-November/000508.html mount -t zfs ... cd /usr/src make NO_FSCHG= installworld This did the job with new kernel. Recommend easier way without reboot.. ___ 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: calcru: time went backwards
Pertti Kosunen wrote: But i did have cpufreq compiled in kernel.. It seems to be working now when loaded as module from loader.conf. No it didn't help, calcru messages just came later. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: time went backwards
Larry Rosenman wrote: On Tue, 15 Apr 2008, Jeremy Chadwick wrote: And what the FAQ doesn't cover is here: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues * EIST (Intel SpeedStep) incompatibilities with Supermicro PDSMI+ motherboards (and possibly others) * Symptom: kernel outputs messages like kernel: calcru: negative runtime of -X usec for pid XX * Workaround: Disable the EIST feature in the BIOS. You can still achieve ACPI-based processor frequency throttling by using powerd(8). * Reference: http://lists.freebsd.org/pipermail/freebsd-questions/2006-October/133253.html What I find interesting is I hadn't seen these until this kernel update :( Same problem here with Tyan Toledo i3000R (S5191) motherboard if cpufreq module is loaded. 7.0-RELEASE (AMD64) didn't have this problem. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: time went backwards
Jeremy Chadwick wrote: 7.0-RELEASE (AMD64) didn't have this problem. Are you absolutely positive about this (re: amd64 not having the problem)? I can reproduce the issue documented in my Wiki page on i386 or amd64. The piece that seems to cause it, at least in the case of the PDSMI+, is EIST being enabled in the BIOS. Yes, with 7.0-RELEASE speedstep was working and there was no calcru: runtime went backwards... messages. But i did have cpufreq compiled in kernel.. It seems to be working now when loaded as module from loader.conf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rc.order wrong (ipfw)
JoaoBR wrote: I don't agree to what you say what sense does it make to have my forward rules up but natd still not? what sense does it makes logging while syslog is not up? What would it forward log when network isn't up? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portdowngrade/portupgrade question
Par Leijonhufvud wrote: Nope, that does not do it, what it did was remove the old (6.3.6) version and fail to install the new version. I also tried going to /usr/ports/mail/fetchmail and doing a make install. Pretty much same error (fetchmail -- TLS enforcement problem/MITM attack/password exposure[...] Please update your ports tree and try again). What have I missed? Update your ports tree, that version of fetchmail has vulnerabilities. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1-STABLE + devel/php5-pcre incompatible?
Dominic Marks wrote: Hello, Is the php5-pcre module really incompatible with FreeBSD 6.1? If so, is there a workaround or a version I can roll back to? Also, it is just me (:-)) or is the php5 port complaining about a checksum mismatch for everyone else? I had some problems yesterday. Had to remove mod_php5, config install lang/php5 and update php5*. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! (fixed?)
Pertti Kosunen wrote: Some change between Sun Nov 13 14:58:40 EET 2005 and Wed Jan 25 17:21:02 EET 2006 causes this message on boot: Jan 27 14:59:46 xx kernel: ad0: req=0xc306baf0 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! Jan 27 14:59:47 xx kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=66763511 Haven't seen these after i ran fsck. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !!
Some change between Sun Nov 13 14:58:40 EET 2005 and Wed Jan 25 17:21:02 EET 2006 causes this message on boot: Jan 27 14:59:46 xx kernel: ad0: req=0xc306baf0 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! Jan 27 14:59:47 xx kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=66763511 I have dma disabled on boot and /etc/rc.local enables it. Everything seem to be ok though, no problems with ad0 in DMA66. FreeBSD 6.0-STABLE (RELENG_6) [EMAIL PROTECTED]:4:0: class=0x0101fa card=0x80531043 chip=0x522910b9 rev=0xc4 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'M1543 Southbridge EIDE Controller' class= mass storage subclass = ATA ATA channel 0: Master: ad0 Maxtor 2F040L0/VAM51JJ0 ATA/ATAPI revision 7 Slave: no device present ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) support for 82573 1000/PRO nic on 5.x [was: Re: em on 5.x]
Mike Tancsa wrote: At 04:53 AM 21/09/2005, Pertti Kosunen wrote: Do i need to do something special with gstripe when upgrading to RELENG_6 from RELENG_5? Sorry, dont know, but a search through the archives might have the answer. I suspect it wont be an issue Everything went fine even without reboot after make installkernel. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) support for 82573 1000/PRO nic on 5.x [was: Re: em on 5.x]
Mike Tancsa wrote: Hi, The driver in RELENG_4 is essentially the same as in HEAD and RELENG_6. Someone backported the changes from the RELENG_6 version to 5.x and posted a link in the mailling list perhaps a month or so ago. Have a look through the archives for the patches. However, I would suggest you go to RELENG_6 from 5.x. 6.x is a bit faster on a number of counts and quite stable on the boxes we have it running on. Do i need to do something special with gstripe when upgrading to RELENG_6 from RELENG_5? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Slow internet browsing.
Sandro Noel wrote: thank you all for the ULTRA fast reply, i had an entry in the resolv.conf that did not belong there. problem solved. something is bothering me... the entry stated that it was the ip of my gateway 10.0.5.1 wich is the same address that the DHCP server gives out. why is it causing problems ? Do you have ADSL-box with Network Address Translation enabled? Sounds like ADSL-router (or firewall) is redirecting your DNS requests. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
Mark Kane wrote: I do have a tall Antec case, and have both 200's and the 160 in 5 1/4 inch trays so the cables for those are long (36 inches IIRC). Would it be OK to have that setup, or would it be better to isolate them all on their own cables/channels and get a Promise card or something for the other two? I'm not going to be doing huge file copying a whole lot, but I'd like the most performance I can get with no errors. You should not see any performance difference between 133 and 100. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient: send_packet: No buffer space available
Chuck Swiger wrote: Does the problem go away if you use a trivial permit all PF ruleset? When i took off scrub altq No buffer space available messages were gone, but dhclient did still renew the same address. Does the problem go away if you use a trivial IPFW permit all instead of PF? Old ipfw rules seem to be working ok. So it's probably something in my pf-rules, have to rewrite and test again. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient: send_packet: No buffer space available
Chuck Swiger wrote: Typically, that sort of message indicates that the firewall rules are preventing traffic from going out, or packets are getting stuck in a queue until it fills up, or maybe even a bug somewhere in the particular combination of kernel firewall options enabled, high optimization or CPUTYPE settings, and your particular hardware, depending on how lucky you are. :-) Does the problem go away if you use a trivial permit all PF ruleset? Does the problem go away if you use a trivial IPFW permit all instead of PF? Does the problem go away if you use a stock 5.4 release kernel? The 3Com 3c905B-TX is an OK NIC, apparently the later C revision or the 918/920's are pretty decent, but anyway-- ...does the problem go away if you switch to another (known good) NIC? System was ok with 5.3-RELEASE custom kernel with ipfw. PF logs all block rules and nothing gets to pflog on those dhclient errors. I try those tips you gave, thanks. Stuck in a queue sounds most likely to be the case. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient: send_packet: No buffer space available
Pertti Kosunen wrote: What could cause dhclient sometimes to fail renew the lease? I updated world and moved to pf from ipfw same time so i don't know which to blame. This happens from twice a day to every few days. Jul 21 03:44:55 myserver dhclient: send_packet: No buffer space available Jul 21 03:44:55 myserver dhclient: send_packet: No buffer space available Jul 21 03:45:02 myserver dhclient: New IP Address (xl0): x.x.x.x Jul 21 03:45:02 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 21 03:45:02 myserver dhclient: New Broadcast Address (xl0): x.x.x.x Jul 21 03:45:02 myserver dhclient: New Routers: x.x.x.x Pf.conf dmesg: http://www.saunalahti.fi/~pkosunen/pf.conf http://www.saunalahti.fi/~pkosunen/dmesg Anyone know what what could be the problem with dhclient? Some buffer is full but what? Nic is 3Com 3c905B-TX, FreeBSD 5.4-STABLE PF. vmstat -m output: http://www.saunalahti.fi/~pkosunen/vmstat.txt # grep dhclient /var/log/messages: Jul 25 20:46:55 myserver dhclient: New IP Address (xl0): 62.142.70.119 Jul 25 20:46:55 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 25 20:46:55 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Jul 25 20:46:56 myserver dhclient: New Routers: 62.142.70.1 Jul 25 20:51:28 myserver dhclient: New IP Address (xl0): 62.142.70.119 Jul 25 20:51:28 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 25 20:51:28 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Jul 25 20:51:28 myserver dhclient: New Routers: 62.142.70.1 Jul 26 21:59:20 myserver dhclient: send_packet: No buffer space available Jul 26 21:59:51 myserver dhclient: New IP Address (xl0): 62.142.70.200 Jul 26 21:59:51 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 26 21:59:51 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Jul 26 21:59:51 myserver dhclient: New Routers: 62.142.70.1 Jul 30 23:34:05 myserver dhclient: send_packet: No buffer space available Jul 30 23:34:05 myserver dhclient: send_packet: No buffer space available Jul 30 23:34:13 myserver dhclient: New IP Address (xl0): 62.142.70.200 Jul 30 23:34:13 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 30 23:34:13 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Jul 30 23:34:13 myserver dhclient: New Routers: 62.142.70.1 Jul 31 02:09:06 myserver dhclient: send_packet: No buffer space available Jul 31 02:09:06 myserver dhclient: send_packet: No buffer space available Jul 31 02:09:10 myserver dhclient: New IP Address (xl0): 62.142.70.200 Jul 31 02:09:10 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 31 02:09:10 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Jul 31 02:09:10 myserver dhclient: New Routers: 62.142.70.1 Aug 1 20:11:26 myserver dhclient: send_packet: No buffer space available Aug 1 20:11:26 myserver dhclient: send_packet: No buffer space available Aug 1 20:11:31 myserver dhclient: New IP Address (xl0): 62.142.70.200 Aug 1 20:11:31 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 1 20:11:31 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 1 20:11:31 myserver dhclient: New Routers: 62.142.70.1 Aug 2 23:03:11 myserver dhclient: send_packet: No buffer space available Aug 2 23:03:11 myserver dhclient: send_packet: No buffer space available Aug 2 23:03:19 myserver dhclient: New IP Address (xl0): 62.142.70.200 Aug 2 23:03:19 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 2 23:03:19 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 2 23:03:19 myserver dhclient: New Routers: 62.142.70.1 Aug 3 22:29:12 myserver dhclient: send_packet: No buffer space available Aug 3 22:29:12 myserver dhclient: send_packet: No buffer space available Aug 3 22:29:21 myserver dhclient: New IP Address (xl0): 62.142.70.113 Aug 3 22:29:21 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 3 22:29:21 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 3 22:29:21 myserver dhclient: New Routers: 62.142.70.1 Aug 4 01:05:46 myserver dhclient: send_packet: No buffer space available Aug 4 01:05:46 myserver dhclient: send_packet: No buffer space available Aug 4 01:05:55 myserver dhclient: New IP Address (xl0): 62.142.70.113 Aug 4 01:05:55 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 4 01:05:55 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 4 01:05:55 myserver dhclient: New Routers: 62.142.70.1 Aug 6 16:53:32 myserver dhclient: send_packet: No buffer space available Aug 6 16:53:32 myserver dhclient: send_packet: No buffer space available Aug 6 16:53:37 myserver dhclient: New IP Address (xl0): 62.142.70.113 Aug 6 16:53:37 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 6 16:53:37 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 6 16:53:37 myserver dhclient: New Routers: 62.142.70.1 Aug 7 06:49:07 myserver dhclient: send_packet: No buffer space available Aug
Re: READ_DMA, WRITE_DMA errors
Steve wrote: If anyone has that link handy, please post. (for the patch) http://people.freebsd.org/~sos/ATA/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
dhclient: send_packet: No buffer space available
What could cause dhclient sometimes to fail renew the lease? I updated world and moved to pf from ipfw same time so i don't know which to blame. This happens from twice a day to every few days. Jul 21 03:44:55 myserver dhclient: send_packet: No buffer space available Jul 21 03:44:55 myserver dhclient: send_packet: No buffer space available Jul 21 03:45:02 myserver dhclient: New IP Address (xl0): x.x.x.x Jul 21 03:45:02 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 21 03:45:02 myserver dhclient: New Broadcast Address (xl0): x.x.x.x Jul 21 03:45:02 myserver dhclient: New Routers: x.x.x.x Pf.conf dmesg: http://www.saunalahti.fi/~pkosunen/pf.conf http://www.saunalahti.fi/~pkosunen/dmesg ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GEOM_STRIPE Problems on Reboot
Drew Tomlinson wrote: So where in the boot sequence is GEOM_STRIPE loaded? I'm starting to suspect it's being loaded twice. I have it in /boot/loader.conf which is where I thought it should be. Is there anywhere else to check? If you have GEOM_STRIPE in kernel do you have to load it from loader.conf? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 STABLE to 5.4 buildkernel error
misael wrote: # Debugging for use in -current #optionsDDB #Enable the kernel debugger #optionsINVARIANTS #Enable calls of extra sanity checking options INVARIANT_SUPPORT #Extra sanity checks of internal structures, required by INVARIANTS #optionsWITNESS #Enable checks to detect deadlocks and cycles #optionsWITNESS_SKIPSPIN#Don't run witness on spinlocks for speed OT: Shouldn't you comment out the INVARIANT_SUPPORT too when INVARIANTS is out? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Poor network performance: a lot of timeouts
Imobach Gonzlez Sosa wrote: Ok, I think I have it correctly with this command: ifconfig rl0 media 100baseTX -mediaopt full-duplex (rl0 or dc0, I've used two different NICs). Moreover, I connected my FreeBSD box to the ADSL router (directly, no more machines connected) and forced the adapter to 10baseT/UTP and full-duplex but it didn't work. I also tried with 100baseTX, but then there was no carrier (the ADSL router is a bit old, and only support 10Mbps). Both sides must have same config, autosense should work if there is no config possibility in other end. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.3 freezes under heavy hdd load
James Seward wrote: I am also attempting to upgrade my system to a newer cvs but unfortunately I can't buildkernel on it - it'll either panic or generate enough timeouts to make make fail. If anyone could point me at a HOWTO or similar on cross-compiling then I'll compile it on my other machine instead (2xP3-1Ghz vs my desktop being an Athlon XP 1700+). Can PIO modes be used with SATA controller? It should compile in PIO mode if it's possible. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: need ISO-image for a new machine install
Emanuel Strobl wrote: Unfortunately there is no mini-inst anymore since install and fixit CD is combined now. You have to download the whole 780MB. Why 780MB? It doesn't fit on normal 700MB CD. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need really cheap IDE mirroring PCI controlled for FreebBSD 4.10
Artem Kuchin wrote: Well, i don't trust software raids. But 3ware is probably one of the most expensive raid 0,1 controllers. There must be something around 40$ which freebsd supports. Does anyone known any model? Those cheap hardware raid 0,1 controllers are all really software raids. Driver does the raid job on windows. IMHO FreeBSD soft-raid is at least as secure than those ms-driver ones. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA mkIII first official patches - please test!
Søren Schmidt wrote: ATA-mkIII first official snapshot. This is the much rumoured ATA update that I've been working on for some time. Is this coming in 5.4-RELEASE? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: poor sound quality in 5.3 stable
Charles Ulrich wrote: I too had problems with a SoundBlaster Live card on a workstation running 5.2.1. Sometimes the sound was nice and clean, but most of the time it was just horrible. Nothing I did had any noticable effect and the mailing lists unusually quiet on the issue, so I gave up. The emu10k1 cards are the best you can buy in their price range, and I didn't want to replace it. Since I needed the machine for sound work (recording and MIDI), I was forced to put Gentoo on it. YMMV. Could this be shared irq issue? Though, i have seen it only in windoze. Different pci-slot might help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 and re driver problem?
Karl M. Joch wrote: Hello, on a box with 3 re interfaces i get a lot of watchdog timeouts and stopping/clow connections. only found 1 or 2 postings with the same problem, but not much replys. the box worked great with 4.x. any suggestions would be very appreziated. I changed re nic to Intel gigE (em) and had no network problems since. Disabling ACPI might help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[Fwd: Re: ad2: FAILURE - READ_DMA, but CD on slave controller recognized?]
C. Fischer wrote: this has started bugging me ever since moving from 4-stable to 5-stable. ad2, which had been recognized no problem on the former, fails on the latter. since i have a multibooter, i can boot 4.10 residing on ad2 without trouble. 4.10 can access ad0 and ad1 fine (this is how i got the initial install in place), but i used ad2 for backups and this doesn't work anymore. the system otherwise works and there are no DMA related hardware errors ever reported except for ad2 not beeing recognized. this seems to indicate that the problem lies in the initial disk checking phase. It's pretty common problem with 5.3, one solution is to: Disable DMA for boot. cat /boot/loader.conf hw.ata.ata_dma=0 hw.ata.atapi_dma=0 And enable first channel DMA later. cat /etc/rc.local atacontrol mode 0 udma4 udma4 http://lists.freebsd.org/pipermail/freebsd-stable/ Searchs previous messages for other workarounds. Disabling APIC might help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TIMEOUT - WRITE_DMA - A possible FIX! turn off ACPI
Arno J. Klaassen wrote: dunno, I'd more suspect ACPI-APIC issues : untill now I only had problems on nForce based systems, but today I installed a brand new VIA based A7VT mini-server and re-voila les XXX_DMA errors (and accompanying severe system slow-down). (Disk swapped from the old PII-233 minimalist-server; worked OK there; disabling APIC (in BOIS and/or config and/or hints) made disappear the XXX_DMA messages (and gave me my network connexion back ;) ) whilst ACPI still enabled). No help here with ACPI or APIC disabled/enabled in any order. First ata-channel works ok with 40GB 120GB disks, but second channel with single 160GB disk has *_DMA issues. 160GB disk works ok at PIO4 mode. Asus A7A266 motherboard with ALI chipset Athlon 1333MHz processor. FreeBSD 5.3-STABLE (RELEASE) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with Intel(R) PRO/1000 card initialization
Android Andrew wrote: Hello! I have a problem with Intel(R) PRO/1000 card (Intel 82540) - it does not initialize properly during boot process. I've got these error messages in /var/log/messages: ... Dec 16 19:27:36 zahrouer kernel: pci2: PCI bus on pcib2 Dec 16 19:27:36 zahrouer kernel: em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0xb000-0xb03f mem 0xe200-0xe201 i rq 21 at device 5.0 on pci2 Dec 16 19:27:36 zahrouer kernel: em0: The EEPROM Checksum Is Not Valid Dec 16 19:27:36 zahrouer kernel: em0: Unable to initialize the hardware Dec 16 19:27:36 zahrouer kernel: device_attach: em0 attach returned 5 ... My system is 5.3-STABLE FreeBSD 5.3-STABLE #0: Thu Dec 16 15:10:36 CET 2004 i386 Motherboard is with i845 chipset. My kernel configuration file does not contain device cbb. I've tried to disable ACPI option in BIOS, but it does not solve this problem. How about also disabling ACPI from /boot/device.hints? (hint.acpi.0.disabled=1) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the best graphicscard for FreeBSD
Matthias Buelow wrote: The newer cards work very well. I have a X800se PCI-Express card and it works like a charm with X.org 6.8.1 on 5.3. The only thing that's missing in the newer Radeons under Xorg/XFree is 3d acceleration (which the OP might or might not need on FreeBSD, since it's mostly only useful for games, anyways). Isn't that pretty expencive for 2d use? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
