Re: i915drm
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gianmarco wrote: HI all, I am running FreeBSD 6.0-STABLE (of today) on a HP Pavillon (centrino based notebook with i915 graphic chipset). I am trying to use the latest drm hook for i915, but I get this error: drmsub0: Intel i915GM port 0x1800-0x1807 mem 0xb008-0xb00f,0xc000-0xcfff,0xb000-0xb003 irq 16 at device 2.0 on pci0 error: [drm:pid0:drm_load] *ERROR* Card isn't AGP, or couldn't initialize AGP. device_attach: drmsub0 attach returned 12 pci0: display at device 2.1 (no driver attached) Any idea ? I have added to my kernel: device agp # support several AGP chipsets device drm # DRM core module required by DRM drivers device i915drm # Intel i830 through i915 and my pciconf -vl shows: [EMAIL PROTECTED]:2:0: class=0x03 card=0x3080103c chip=0x25928086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82915GM/GMS, 82910GML Integrated Graphics Device' class= display subclass = VGA [EMAIL PROTECTED]:2:1: class=0x038000 card=0x3080103c chip=0x27928086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82915GM/GMS,82910GML Mobile Express Family Graphics Controller (??)' class= display Do I miss something ? Thanks ... I have the same experience. But note that i915 (both agp and drm) is still in beta stage. Check this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=80396 (Problem Report kern/80396 : [agp] i915 AGP not supported). Best, Laci - -- László Károly [EMAIL PROTECTED] Department of Altaic StudiesEgyetem str. 2. University of Szeged H-6722 Szeged, Hungary PGP/GnuPG key: 1024D/869D81C5 Fingerprint: 1E61 3205 8F5A 87E7 1269 3396 1C63 F9FF 869D 81C5 Encrypted e-mail preferred. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDpSuiHGP5/4adgcURAvMGAJ9xH4eVDTi9diO0EFL6P46nA/T4gACfdzDG Zbmfn16b72QAyMhqk6kRt2g= =ebZC -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fast releases demand binary updates.. (Was: Release schedule for 2006)
Chuck Swiger wrote: Upgrading the ports from there was somewhat annoying, as this guy's machine had ~400 or so, but deleting them all, and then using pkg_add -r works just fine if you want to grab the latest current binaries. From there you can portupgrade as usual. Now, if you want to talk about upgrading to intermediate patch releases, you've got a valid point there. :-) Doesn't creating a binary updates system that's going to be practical to use require implementation of that old and exceedingly bikesheddable subject: packaging up the base system? After all, you're going to need some mechanism for auditing servers down the line (yes, this machine has had the vital fix to the foo daemon applied), and while bumping the patch level on the release sorta works to do that, it implies a new kernel and a reboot for each patch applied if it's going to be visible. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: NFS UDP mounts on RELENG_6?
Hi. On Fri, Dec 16, 2005 at 04:30:31PM +0100, Fabian Keil wrote: Oliver Brandmueller [EMAIL PROTECTED] wrote: I'm experiencing problems when trying to mount NFS filesystems from a RELENG_6 server (FreeBSD hudson 6.0-STABLE FreeBSD 6.0-STABLE #0: Wed Dec 14 16:59:55 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NFS-32-FBSD6 i386) to either 5.4-STABLE or 6-STABLE clients. mounting works fine, but afterwards the access to the filesystem on the client stalls. As soon as I mount the FS with a TCP mount everything works as expected. The mounts worked fine on UDP when the server was 5.4-STABLE. There is just a plain GigE switch involved, no firewalls or routing. Anyone else experiencing those problems or having an idea? I just copied some files (200 MB) from a NFS Server running FreeBSD africanqueen.local 6.0-STABLE FreeBSD 6.0-STABLE #5: Thu Dec 15 19:31:12 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AFRICANQUEEN i386 without problems. My client runs FreeBSD 5.4, I use GigE as well, but no switch. Which kind GigE Interface do you use? I'm currently checking different things. I have another RELENG_6 machine where everything works fine, which has a slightly older system at the moment. Luckily it's still in the testing phase, so I'm currently updating and see if everything is still working after update. This one has bge interfaces (and is amd64). The machine with the problem has em interfaces and I've got the feeling the problem is related to the interface. When doing a tcpdump at the time the mount stalls there's an interesting effect: On the client I see outgoing NFS requests only. The tcpdump on the server shows the incoming requests from the client AND outgoing answers from the server, which don't show up at the client then. I have no other GigE NIC around to put into the original server and it will take some time to do the patching in the datacenter and set up a monitoring port (dunno if the switch is smart enough after all to do that) to sniff from an independent machine. I'll keep you posted. - Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | pgpUbyUO2tENa.pgp Description: PGP signature
Re: Release Schedule for 2006
On Sat, Dec 17, 2005 at 06:44:48PM -0500, Kris Kennaway wrote: It looks like in the course of writing your long email you forgot to describe any of the problems you are having. I don't know his exact problems either, but I could name you a few examples that currently reduce the fun of using FreeBSD: - The sound sytem is broken in FreeBSD in all 5.x and 6 versions, and I would like to listen to a few mp3-files from time to time. - To my surprise it's almost impossible to use the parallel port with interrupts (interrupt storms), polling mode works... - wlan is broken, my Thinkpad keeps losing WPA-PSK connection very often (probably kern/88793). - Keeping the system and the ports up to date gets more and more time consuming and risky (especially when compared to an apt-get update apt-get upgrade). For example, the last devel/pear update in the ports crashed my PHP installations on 2 development machines (still no clue how to fix this). Don't get me wrong, I certainly don't want to complain, I just wanted to give you some examples. Uwe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS UDP mounts on RELENG_6?
Hi. On Sun, Dec 18, 2005 at 01:45:37PM +0100, Oliver Brandmueller wrote: Which kind GigE Interface do you use? I'm currently checking different things. I have another RELENG_6 machine where everything works fine, which has a slightly older system at the moment. Luckily it's still in the testing phase, so I'm currently updating and see if everything is still working after update. This one has bge interfaces (and is amd64). OK. UDP NFS works as expected with amd64/bge on RELENG_6 of today. It does not work in the same network on i386/em for me. Still investigating. - Olli -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | pgpButOTw5FWE.pgp Description: PGP signature
Re: Release Schedule for 2006
Uwe, On Sun, 18 Dec 2005, Uwe Laverenz wrote: On Sat, Dec 17, 2005 at 06:44:48PM -0500, Kris Kennaway wrote: It looks like in the course of writing your long email you forgot to describe any of the problems you are having. I don't know his exact problems either, but I could name you a few examples that currently reduce the fun of using FreeBSD: - The sound sytem is broken in FreeBSD in all 5.x and 6 versions, and I would like to listen to a few mp3-files from time to time. If I was at work and I got a comment or a phone call like this, I would usually sigh heavily and, in a voice dripping with sarcasm, ask the exact same question that I'm going to ask you: How exactly is it broken? Actually, you should probably take it to -questions. snip other fairly vague descriptions - Keeping the system and the ports up to date gets more and more time consuming and risky (especially when compared to an apt-get update apt-get upgrade). For example, the last devel/pear update in the ports crashed my PHP installations on 2 development machines (still no clue how to fix this). I don't use PEAR, but wasn't there something in UPDATING about it? David Adam [EMAIL PROTECTED] UCC Wheel Member (who does plenty with apt, too, and will stick with the ports system thank you very much.) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Release Schedule for 2006
On Sunday 18 December 2005 15:02, Uwe Laverenz wrote: On Sat, Dec 17, 2005 at 06:44:48PM -0500, Kris Kennaway wrote: It looks like in the course of writing your long email you forgot to describe any of the problems you are having. I don't know his exact problems either, but I could name you a few examples that currently reduce the fun of using FreeBSD: - The sound sytem is broken in FreeBSD in all 5.x and 6 versions, and I would like to listen to a few mp3-files from time to time. Define broken? I put snd_ich_load=YES into /boot/loader.conf, nothing in the kernel and it just works. Listening to SomaFM's Groovesalad via mpg123 as I type. - Keeping the system and the ports up to date gets more and more time consuming and risky (especially when compared to an apt-get update apt-get upgrade). For example, the last devel/pear update in the ports crashed my PHP installations on 2 development machines (still no clue how to fix this). That's independant of -stable/-current or any FreeBSD release for that matter, but if you have a PR to look at... -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS UDP mounts on RELENG_6?
On Sunday 18 December 2005 15:12, Oliver Brandmueller wrote: Hi. On Sun, Dec 18, 2005 at 01:45:37PM +0100, Oliver Brandmueller wrote: Which kind GigE Interface do you use? I'm currently checking different things. I have another RELENG_6 machine where everything works fine, which has a slightly older system at the moment. Luckily it's still in the testing phase, so I'm currently updating and see if everything is still working after update. This one has bge interfaces (and is amd64). OK. UDP NFS works as expected with amd64/bge on RELENG_6 of today. It does not work in the same network on i386/em for me. Still investigating. To rule out NFS, do something like syslogging remotely (also UDP). -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
DLT Tape Read errors on aac0
Hi, I am using an Adaptec SCSI RAID 2120S Card with 5 SCSI Seagate drives as a RAID-5 without any probelms for almost two years now. Last week I attached to the aac0 controller a Tandberg DLT Drive QUANTUM DLT VS160 2500 Removable Sequential Access SCSI-2 device for large backup purposes. We decided to use dump/restore for our backup strategy but unfortunately we can only make backups and no restores. E.g dumping a filesystem works great: [EMAIL PROTECTED] ~ dump -0aLf /dev/sa0 /var DUMP: Date of this level 0 dump: Tue Dec 20 15:44:05 2005 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping snapshot of /dev/aacd0s1f (/var) to /dev/sa0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 63220 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 64341 tape blocks on 1 volume DUMP: finished in 15 seconds, throughput 4289 KBytes/sec DUMP: Closing /dev/sa0 DUMP: DUMP IS DONE [EMAIL PROTECTED] ~ I guess the backup has been successfully finished. But when I try a access the backup ether via the interactive console or by trying to extract the data directly I get the follwing errors in /var/log/messages [EMAIL PROTECTED] /var restore -i -f /dev/sa0 tape read error: Input/output error Dec 20 15:49:22 hercules kernel: (sa0:aacp0:0:5:0): READ(06). CDB: 8 0 0 80 0 0 Dec 20 15:49:22 hercules kernel: (sa0:aacp0:0:5:0): NO SENSE ILI (length mismatch): 22528 csi:e0,40,0,20 asc:0,0 Dec 20 15:49:22 hercules kernel: (sa0:aacp0:0:5:0): No additional sense information Sometimes I often get some Timeouts (only using restore). Dec 19 11:34:27 hercules kernel: aac0: COMMAND 0xc1fdf750 TIMEOUT AFTER 51 SECONDS Kernel config: - # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers device aac # Adaptec FSA RAID device aacp# SCSI passthrough for aac (requires CAM) - dmesg (cutted): -- hercules kernel: CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2399.33-MHz 686-class CPU) hercules kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs hercules kernel: cpu0 (BSP): APIC ID: 0 hercules kernel: cpu1 (AP): APIC ID: 1 hercules kernel: cpu2 (AP): APIC ID: 6 hercules kernel: cpu3 (AP): APIC ID: 7 aac0: Adaptec SCSI RAID 2120S mem 0xd000-0xd3ff irq 52 at device 2.0 on pci4 aac0: [FAST] aac0: Unknown processor 100MHz, 48MB cache memory, optional battery not installed aac0: Kernel 4.1-0, Build 7244, S/N bd10c2 aac0: Supported Options=11d7eCLUSTERS,WCACHE,DATA64,HOSTTIME,RAID50,WINDOW4GB,SOFTERR,SGMAP64,ALARM,NONDASD aacp0: SCSI Passthrough Bus on aac0 acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% (probe5:aacp0:0:5:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe5:aacp0:0:5:0): NOT READY csi:e0,40,0,1c asc:4,1 (probe5:aacp0:0:5:0): Logical unit is in process of becoming ready sa0 at aacp0 bus 0 target 5 lun 0 sa0: QUANTUM DLT VS160 2500 Removable Sequential Access SCSI-2 device sa0: 160.000MB/s transfers (80.000MHz, offset 96, 16bit) -- Does anybody maybe have an idea why I can use dump but not restore ? This doesn't make sense to me. And I should mention that tar works great! I can write and read from the tape, even with filemarks. Thanks for your help! Christian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DLT Tape Read errors on aac0
Waah, I forgot the most important information. Its an 5.3-STABLE FreeBSD Operating System. :-) Christian Christian Gründemann schrieb: Hi, I am using an Adaptec SCSI RAID 2120S Card with 5 SCSI Seagate drives as a RAID-5 without any probelms for almost two years now. Last week I attached to the aac0 controller a Tandberg DLT Drive QUANTUM DLT VS160 2500 Removable Sequential Access SCSI-2 device for large backup purposes. We decided to use dump/restore for our backup strategy but unfortunately we can only make backups and no restores. E.g dumping a filesystem works great: [EMAIL PROTECTED] ~ dump -0aLf /dev/sa0 /var DUMP: Date of this level 0 dump: Tue Dec 20 15:44:05 2005 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping snapshot of /dev/aacd0s1f (/var) to /dev/sa0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 63220 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 64341 tape blocks on 1 volume DUMP: finished in 15 seconds, throughput 4289 KBytes/sec DUMP: Closing /dev/sa0 DUMP: DUMP IS DONE [EMAIL PROTECTED] ~ I guess the backup has been successfully finished. But when I try a access the backup ether via the interactive console or by trying to extract the data directly I get the follwing errors in /var/log/messages [EMAIL PROTECTED] /var restore -i -f /dev/sa0 tape read error: Input/output error Dec 20 15:49:22 hercules kernel: (sa0:aacp0:0:5:0): READ(06). CDB: 8 0 0 80 0 0 Dec 20 15:49:22 hercules kernel: (sa0:aacp0:0:5:0): NO SENSE ILI (length mismatch): 22528 csi:e0,40,0,20 asc:0,0 Dec 20 15:49:22 hercules kernel: (sa0:aacp0:0:5:0): No additional sense information Sometimes I often get some Timeouts (only using restore). Dec 19 11:34:27 hercules kernel: aac0: COMMAND 0xc1fdf750 TIMEOUT AFTER 51 SECONDS Kernel config: - # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers device aac # Adaptec FSA RAID device aacp# SCSI passthrough for aac (requires CAM) - dmesg (cutted): -- hercules kernel: CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2399.33-MHz 686-class CPU) hercules kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs hercules kernel: cpu0 (BSP): APIC ID: 0 hercules kernel: cpu1 (AP): APIC ID: 1 hercules kernel: cpu2 (AP): APIC ID: 6 hercules kernel: cpu3 (AP): APIC ID: 7 aac0: Adaptec SCSI RAID 2120S mem 0xd000-0xd3ff irq 52 at device 2.0 on pci4 aac0: [FAST] aac0: Unknown processor 100MHz, 48MB cache memory, optional battery not installed aac0: Kernel 4.1-0, Build 7244, S/N bd10c2 aac0: Supported Options=11d7eCLUSTERS,WCACHE,DATA64,HOSTTIME,RAID50,WINDOW4GB,SOFTERR,SGMAP64,ALARM,NONDASD aacp0: SCSI Passthrough Bus on aac0 acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% (probe5:aacp0:0:5:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe5:aacp0:0:5:0): NOT READY csi:e0,40,0,1c asc:4,1 (probe5:aacp0:0:5:0): Logical unit is in process of becoming ready sa0 at aacp0 bus 0 target 5 lun 0 sa0: QUANTUM DLT VS160 2500 Removable Sequential Access SCSI-2 device sa0: 160.000MB/s transfers (80.000MHz, offset 96, 16bit) -- Does anybody maybe have an idea why I can use dump but not restore ? This doesn't make sense to me. And I should mention that tar works great! I can write and read from the tape, even with filemarks. Thanks for your help! Christian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS UDP mounts on RELENG_6?
Oliver Brandmueller [EMAIL PROTECTED] wrote: On Fri, Dec 16, 2005 at 04:30:31PM +0100, Fabian Keil wrote: Oliver Brandmueller [EMAIL PROTECTED] wrote: I'm experiencing problems when trying to mount NFS filesystems from a RELENG_6 server (FreeBSD hudson 6.0-STABLE FreeBSD 6.0-STABLE #0: Wed Dec 14 16:59:55 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NFS-32-FBSD6 i386) to either 5.4-STABLE or 6-STABLE clients. mounting works fine, but afterwards the access to the filesystem on the client stalls. As soon as I mount the FS with a TCP mount everything works as expected. The mounts worked fine on UDP when the server was 5.4-STABLE. There is just a plain GigE switch involved, no firewalls or routing. Anyone else experiencing those problems or having an idea? I just copied some files (200 MB) from a NFS Server running FreeBSD africanqueen.local 6.0-STABLE FreeBSD 6.0-STABLE #5: Thu Dec 15 19:31:12 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AFRICANQUEEN i386 without problems. My client runs FreeBSD 5.4, I use GigE as well, but no switch. Which kind GigE Interface do you use? Client: [EMAIL PROTECTED] ~ $pciconf -lv| grep em0 -A 2 [EMAIL PROTECTED]:1:0: class=0x02 card=0x05491014 chip=0x101e8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82540EP Gigabit Ethernet Controller (Mobile)' Server: [EMAIL PROTECTED] ~ $pciconf -lv| grep re[01] -A 2 [EMAIL PROTECTED]:9:0: class=0x02 card=0x816910ec chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' -- [EMAIL PROTECTED]:10:0: class=0x02 card=0x601b182d chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' re0 is made by Vivanco, re1 is a Sitecom card. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Re: Release Schedule for 2006
On Sun, Dec 18, 2005 at 03:02:58PM +0100, Uwe Laverenz wrote: On Sat, Dec 17, 2005 at 06:44:48PM -0500, Kris Kennaway wrote: It looks like in the course of writing your long email you forgot to describe any of the problems you are having. I don't know his exact problems either, but I could name you a few examples that currently reduce the fun of using FreeBSD: - The sound sytem is broken in FreeBSD in all 5.x and 6 versions, and I would like to listen to a few mp3-files from time to time. Well, no, the sound system is not broken, perhaps a driver just doesn't work on your hardware (or you're using the wrong driver). You also forgot to describe your system. - Keeping the system and the ports up to date gets more and more time consuming and risky (especially when compared to an apt-get update apt-get upgrade). For example, the last devel/pear update in the ports crashed my PHP installations on 2 development machines (still no clue how to fix this). As far as I can tell nothing has changed here except for random timing of updates. Yes, sometimes when an update it committed it is broken at first or requires extra work on your part to adapt. This has always been true, except thesedays we make a lot more effort to test for problems and describe any additional upgrade steps (see UPDATING). When you encounter a problem, as you apparently did, you need to inform the appropriate people (e.g. port maintainer), otherwise there's no way they can help you to resolve it. Kris pgpGQeOvrmqaH.pgp Description: PGP signature
Re: Fast releases demand binary updates.. (Was: Release schedule for 2006)
On Sun, Dec 18, 2005 at 09:55:33AM +, Matthew Seaman wrote: Chuck Swiger wrote: Upgrading the ports from there was somewhat annoying, as this guy's machine had ~400 or so, but deleting them all, and then using pkg_add -r works just fine if you want to grab the latest current binaries. From there you can portupgrade as usual. Now, if you want to talk about upgrading to intermediate patch releases, you've got a valid point there. :-) Doesn't creating a binary updates system that's going to be practical to use require implementation of that old and exceedingly bikesheddable subject: packaging up the base system? No, after all the *existing* binary update systems don't require packaging of the base system. Kris pgpaf2O2IcxGV.pgp Description: PGP signature
Re: Release Schedule for 2006
Thanks to the email from some kind members here, it is likely that my problems are not fatal, just temporarily blocking me. I plan to do another attempt on Mt 6.0, with proper planning, base and upper camps, and of course, porter support. Thanks to those who wrote. BillN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DLT Tape Read errors on aac0
First of all, let me apologize for the mess that is the aac passthrough driver. I wrote it in hopes that it would be useful, but the support needed for it in the aac firmware simply isn't robust enough for the kind of SCSI stuff that FreeBSD does. In other words, it's a hack from top to bottom, and really is little more than a novelty at this point. See below... Christian Gründemann wrote: Waah, I forgot the most important information. Its an 5.3-STABLE FreeBSD Operating System. :-) Christian Christian Gründemann schrieb: Hi, I am using an Adaptec SCSI RAID 2120S Card with 5 SCSI Seagate drives as a RAID-5 without any probelms for almost two years now. Last week I attached to the aac0 controller a Tandberg DLT Drive QUANTUM DLT VS160 2500 Removable Sequential Access SCSI-2 device for large backup purposes. We decided to use dump/restore for our backup strategy but unfortunately we can only make backups and no restores. E.g dumping a filesystem works great: [EMAIL PROTECTED] ~ dump -0aLf /dev/sa0 /var DUMP: Date of this level 0 dump: Tue Dec 20 15:44:05 2005 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping snapshot of /dev/aacd0s1f (/var) to /dev/sa0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 63220 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 64341 tape blocks on 1 volume DUMP: finished in 15 seconds, throughput 4289 KBytes/sec DUMP: Closing /dev/sa0 DUMP: DUMP IS DONE [EMAIL PROTECTED] ~ I guess the backup has been successfully finished. But when I try a access the backup ether via the interactive console or by trying to extract the data directly I get the follwing errors in /var/log/messages [EMAIL PROTECTED] /var restore -i -f /dev/sa0 tape read error: Input/output error Dec 20 15:49:22 hercules kernel: (sa0:aacp0:0:5:0): READ(06). CDB: 8 0 0 80 0 0 Dec 20 15:49:22 hercules kernel: (sa0:aacp0:0:5:0): NO SENSE ILI (length mismatch): 22528 csi:e0,40,0,20 asc:0,0 Dec 20 15:49:22 hercules kernel: (sa0:aacp0:0:5:0): No additional sense information This is very very strange, and I don't even know where to start guessing. It could be either a fairly minor bug in the driver, or a major bug/lack of support in the firmware. Sometimes I often get some Timeouts (only using restore). Dec 19 11:34:27 hercules kernel: aac0: COMMAND 0xc1fdf750 TIMEOUT AFTER 51 SECONDS This is usually a sign that the firmware either lost a command, or paniced all together. Both conditions are fatal =-( Kernel config: - # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers device aac # Adaptec FSA RAID device aacp# SCSI passthrough for aac (requires CAM) - dmesg (cutted): -- hercules kernel: CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2399.33-MHz 686-class CPU) hercules kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs hercules kernel: cpu0 (BSP): APIC ID: 0 hercules kernel: cpu1 (AP): APIC ID: 1 hercules kernel: cpu2 (AP): APIC ID: 6 hercules kernel: cpu3 (AP): APIC ID: 7 aac0: Adaptec SCSI RAID 2120S mem 0xd000-0xd3ff irq 52 at device 2.0 on pci4 aac0: [FAST] aac0: Unknown processor 100MHz, 48MB cache memory, optional battery not installed aac0: Kernel 4.1-0, Build 7244, S/N bd10c2 aac0: Supported Options=11d7eCLUSTERS,WCACHE,DATA64,HOSTTIME,RAID50,WINDOW4GB,SOFTERR,SGMAP64,ALARM,NONDASD aacp0: SCSI Passthrough Bus on aac0 acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% (probe5:aacp0:0:5:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe5:aacp0:0:5:0): NOT READY csi:e0,40,0,1c asc:4,1 (probe5:aacp0:0:5:0): Logical unit is in process of becoming ready sa0 at aacp0 bus 0 target 5 lun 0 sa0: QUANTUM DLT VS160 2500 Removable Sequential Access SCSI-2 device sa0: 160.000MB/s transfers (80.000MHz, offset 96, 16bit) -- Does anybody maybe have an idea why I can use dump but not restore ? This doesn't make sense to me. And I should mention that tar works great! I can write and read from the tape, even with filemarks. Thanks for your help! Christian I have a DLT drive here that I could probably hook up and start debugging with, but there are a lot of other things on my plate with higher priority, unfortunately. Your best bet for now is to put the tape drive onto a real Symbios or Adaptec SCSI card. Scott ___ freebsd-stable@freebsd.org mailing list
Re: HEADS UP: Release schedule for 2006
Kevin Oberman wrote: Date: Sat, 17 Dec 2005 18:14:01 +0100 From: martinko [EMAIL PROTECTED] Kevin Oberman wrote: Date: Fri, 16 Dec 2005 14:29:39 -0600 From: Craig Boston [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] -cpu0: ACPI CPU (4 Cx states) on acpi0 +cpu0: ACPI CPU on acpi0 Q: Guessing that's a formatting difference, rather then 6.x not recognizing the states (sysctl hw.acpi.cpu.cx_supported confirms 4 states) Not sure on this, but you're probably better off using EST anyway as I think it gives you more control over the processor frequency. No. There is no conflict between Cx states and EST. Cx states specifies how deeply the CPU will sleep when idle. EST controls processor speed and voltage. In most cases, your REALLY want to use both of these. They are very significant in saving power. (Of course, USB tends to limit the effectiveness of Cx states. I need to run without USB to get really good battery life and to make suspend (S3) really ut power drain. Kevin, I used to have 3 Cx states supported when I started with FreeBSD on version 5.3. Since I upgraded to 5.4 and recently to 6.0, all I can see is just one supported Cx state. I much wonder why. (?) What value do you have in /etc/rc.conf (if any) for performance_cx_lowest? It defaults to HIGH which will limit you to only the most power hungry sleep state (simple halt). This was made the default because some hardware was breaking when this was defaulted to LOW. T0 get other Cx states to be utilized, add 'performance_cx_lowest=LOW' to /etc/rc.conf. i see. anyway: # grep cx /etc/rc.conf.local economy_cx_lowest=LOW performance_cx_lowest=LOW still: # sysctl hw.acpi.cpu hw.acpi.cpu.cx_supported: C1/1 hw.acpi.cpu.cx_lowest: C1 hw.acpi.cpu.cx_usage: 100.00% and, imho, cx_supported should list all available states, doesn't matter what is in rc.conf. (well, at least i reckon it's supposed to work that way.) but: i already had 3 Cx states back on 5.3. and when i had them, C2 was used most often (and C3 wasn't at all iirc). so what has changed in the system please and how am i to get back my states please ?? many thanks, martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: Release schedule for 2006
On Sunday 18 December 2005 20:46, martinko wrote: # sysctl hw.acpi.cpu hw.acpi.cpu.cx_supported: C1/1 hw.acpi.cpu.cx_lowest: C1 hw.acpi.cpu.cx_usage: 100.00% and, imho, cx_supported should list all available states, doesn't matter what is in rc.conf. (well, at least i reckon it's supposed to work that way.) but: i already had 3 Cx states back on 5.3. and when i had them, C2 was used most often (and C3 wasn't at all iirc). so what has changed in the system please and how am i to get back my states please ?? This is exactly the thing you need to report via send-pr. Developers won't be aware of regression errors if they don't get reported. Cx states are configured via acpi, so I'd visit the acpi list and prepare a dump of your acpicode for the developers to look at. See acpidump(8) for details. -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Release Schedule for 2006
Uwe Laverenz wrote: On Sat, Dec 17, 2005 at 06:44:48PM -0500, Kris Kennaway wrote: It looks like in the course of writing your long email you forgot to describe any of the problems you are having. I don't know his exact problems either, but I could name you a few examples that currently reduce the fun of using FreeBSD: - To my surprise it's almost impossible to use the parallel port with interrupts (interrupt storms), polling mode works... It doesn't surprise me, as most printer hardware is USB nowadays, so I'm sure that these bits haven't been well exercised lately. If there is a regression in this area in RELENG_6, it would be worth reporting to this list, hopefully with enough detail that a developer could help you troubleshoot the problem. - wlan is broken, my Thinkpad keeps losing WPA-PSK connection very often (probably kern/88793). Two things, first I seem to recall someone saying that the ral hardware is not all that hot to begin with, and you'd be better off with another wifi card. If that's not possible, have you tried upgrading to the latest 6-stable? If it's still not working after that, please report it to the list. Also, it's worth noting that if you're trying WPA on 5-stable, you're not likely to succeed. The infrastructure was greatly improved for 6-release. Don't get me wrong, I certainly don't want to complain, I just wanted to give you some examples. Ok, assuming we can take you at face value here, please note the consistent item in both of my responses above. The only way we can fix problems is if we know they exist, and the users experiencing the problems are willing to help with details, and testing solutions. The nature of PC hardware is such that no matter how much a developer tests on what they have (and some of our developers have extensive hardware testing facilities, often purchased with their own money), there will always be corner cases. FreeBSD got to the state that it is in right now (good or bad) because the community of its users helped make it that way. The only way it gets better is if people help make it better. Relying on them to do it for you is not the FreeBSD way. Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need help with crash analysis
I had another crash and this time ran kgdb and typed bt full with the
following output. As a last resort I rebuilt the kernel with HZ=2000,
instead of 1000 and haven't had a crash since. My wireless card seems
more responsive under load too. Ping times are lower when I'm
transferring large files across the network.
[GDB will not be able to debug user-mode
threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for
details.
This GDB was configured as i386-marcel-freebsd.
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x10
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc066ccec
stack pointer = 0x28:0xe36198bc
frame pointer = 0x28:0x0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 38 (swi1: net)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 3m17s
Dumping 1023 MB (2 chunks)
chunk 0: 1MB (158 pages)
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x1c
fault code = supervisor write, page not present
instruction pointer = 0x20:0xc0549f20
stack pointer = 0x28:0xe5084c8c
frame pointer = 0x28:0xe5084ccc
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 36 (swi4: clock)
trap number = 12
... ok
chunk 1: 1023MB (261802 pages) 1007 991 975 959 943 927 911 895 879
863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591
575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303
287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt full
#0 doadump () at pcpu.h:165
No locals.
#1 0xc053b467 in boot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:399
first_buf_printf = 1
#2 0xc053b818 in panic (fmt=0xc06dc865 %s)
at /usr/src/sys/kern/kern_shutdown.c:555
td = (struct thread *) 0xc22ec4b0
bootopt = 260
newpanic = 0
ap = 0xc22ec4b0
buf = page fault, '\0' repeats 245 times
#3 0xc06b4b14 in trap_fatal (frame=0xe361987c, eva=0)
at /usr/src/sys/i386/i386/trap.c:831
code = 40
type = 12
ss = 40
esp = 0
softseg = {ssd_base = 0, ssd_limit = 1048575, ssd_type = 27, ssd_dpl =
0, ssd_p = 1, ssd_xx = 0, ssd_xx1 = 0, ssd_def32 = 1, ssd_gran = 1}
#4 0xc06b480d in trap_pfault (frame=0xe361987c, usermode=0, eva=16)
at /usr/src/sys/i386/i386/trap.c:742
va = 0
vm = (struct vmspace *) 0x0
map = 0xc073d820
rv = 1
ftype = 1 '\001'
td = (struct thread *) 0xc22ec4b0
p = (struct proc *) 0xc234b000
#5 0xc06b43f3 in trap (frame=
{tf_fs = -480182264, tf_es = 40, tf_ds = 40, tf_edi = 0, tf_esi =
-315641204, tf_ebp = 0, tf_isp = -480143192, tf_ebx = -315638608, tf_edx
= 791735, tf_ecx = -1073475471, tf_eax = 1, tf_trapno = 12, tf_err = 0,
tf_eip = -1067004692, tf_cs = 32, tf_eflags = 66050, tf_esp = 16777216,
tf_ss = 0})
at /usr/src/sys/i386/i386/trap.c:432
td = (struct thread *) 0xc22ec4b0
p = (struct proc *) 0xc234b000
sticks = 3814824188
i = 0
ucode = 0
type = 12
code = 0
eva = 16
#6 0xc06a041a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
No locals.
#7 0xc066ccec in zz0e373a4d ()
No symbol table info available.
(kgdb) quit
On Fri, 2005-12-16 at 18:17 -0500, Peter D. Quilty wrote:
I have a Dell Inspiron 9100 laptop that has been crashing lately. It
seems to happen when there is a moderate disk load and the network load
is 6 Mbits/sec. I can usually replicate it by running portsdb -fUu
while downloading or copying large files across the network. I have
tried the following in an attempt to isolate the problem, but nothing
has worked.
* disabling ACPI
* disabling hyperthreading
* disabling SMP
* switching back to the 4BSD scheduler from ULE
I ran kgdb against kernel.debug and the crash dump, but don't quite know
how to interpret it or where to go from here. I've attached my kernel
config file, dmesg.boot, and the outputs from kldstat and kgdb.
I recently upgraded my router/access point at home from
Re: HEADS UP: Release schedule for 2006
Date: Sun, 18 Dec 2005 20:46:49 +0100 From: martinko [EMAIL PROTECTED] Kevin Oberman wrote: Date: Sat, 17 Dec 2005 18:14:01 +0100 From: martinko [EMAIL PROTECTED] Kevin Oberman wrote: Date: Fri, 16 Dec 2005 14:29:39 -0600 From: Craig Boston [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] -cpu0: ACPI CPU (4 Cx states) on acpi0 +cpu0: ACPI CPU on acpi0 Q: Guessing that's a formatting difference, rather then 6.x not recognizing the states (sysctl hw.acpi.cpu.cx_supported confirms 4 states) Not sure on this, but you're probably better off using EST anyway as I think it gives you more control over the processor frequency. No. There is no conflict between Cx states and EST. Cx states specifies how deeply the CPU will sleep when idle. EST controls processor speed and voltage. In most cases, your REALLY want to use both of these. They are very significant in saving power. (Of course, USB tends to limit the effectiveness of Cx states. I need to run without USB to get really good battery life and to make suspend (S3) really ut power drain. Kevin, I used to have 3 Cx states supported when I started with FreeBSD on version 5.3. Since I upgraded to 5.4 and recently to 6.0, all I can see is just one supported Cx state. I much wonder why. (?) What value do you have in /etc/rc.conf (if any) for performance_cx_lowest? It defaults to HIGH which will limit you to only the most power hungry sleep state (simple halt). This was made the default because some hardware was breaking when this was defaulted to LOW. T0 get other Cx states to be utilized, add 'performance_cx_lowest=LOW' to /etc/rc.conf. i see. anyway: # grep cx /etc/rc.conf.local economy_cx_lowest=LOW performance_cx_lowest=LOW still: # sysctl hw.acpi.cpu hw.acpi.cpu.cx_supported: C1/1 hw.acpi.cpu.cx_lowest: C1 hw.acpi.cpu.cx_usage: 100.00% and, imho, cx_supported should list all available states, doesn't matter what is in rc.conf. (well, at least i reckon it's supposed to work that way.) but: i already had 3 Cx states back on 5.3. and when i had them, C2 was used most often (and C3 wasn't at all iirc). so what has changed in the system please and how am i to get back my states please ?? This is a totally different problem. I thought that the problem was simply not using all of the states. Instead, you are not even showing the states as available. Looks like the kernel is not reading the capabilities of your system correctly. This seems to coincide with the new ACPI code import. Sounds like something is not being handled properly and it is likely beyond my capability to track it down. I would suggest posting your the output of 'acpidump -t -d' on a web site and then sending a report with a pointer to that ASL to [EMAIL PROTECTED] There it will be seen by the folks who really know the ACPI stuff. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Release Schedule for 2006
On Mon, 19 Dec 2005 00:32, Uwe Laverenz wrote: On Sat, Dec 17, 2005 at 06:44:48PM -0500, Kris Kennaway wrote: I don't know his exact problems either, but I could name you a few examples that currently reduce the fun of using FreeBSD: If you're going to do this, please write a GOOD bug report. Yes it is more time consuming, but your actually likely to get the problem fixed. - The sound sytem is broken in FreeBSD in all 5.x and 6 versions, and I would like to listen to a few mp3-files from time to time. This is a non bug report. Sound works perfectly on the various pieces of hardware I have (snd_vt8233, snd_ich, snd_t4dwave). - To my surprise it's almost impossible to use the parallel port with interrupts (interrupt storms), polling mode works... This is a fixable side effect of the interrupt storm detector being implemented. Arguably the default limit should be bumped up, but I don't know what the cons are. In your case you can do.. sysctl hw.intr_storm_threshold=5 and all should be well again. - wlan is broken, my Thinkpad keeps losing WPA-PSK connection very often (probably kern/88793). Works for me (tm). Although I have an ath card. Perhaps you should take it up with the ipw(4) driver maintainer? - Keeping the system and the ports up to date gets more and more time consuming and risky (especially when compared to an apt-get update apt-get upgrade). For example, the last devel/pear update in the ports crashed my PHP installations on 2 development machines (still no clue how to fix this). Bit of a hammer, but you could try rebuilding php.. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgp3MUBrdruLO.pgp Description: PGP signature
Re: Release Schedule for 2006
On Dec 18, 2005, at 8:01 , Daniel O'Connor wrote: On Mon, 19 Dec 2005 00:32, Uwe Laverenz wrote: - wlan is broken, my Thinkpad keeps losing WPA-PSK connection very often (probably kern/88793). Works for me (tm). Although I have an ath card. Perhaps you should take it up with the ipw(4) driver maintainer? Last I heard, *only* ath and maybe the ndisulator worked reliably. : ( I don't know if anyone has stepped forward to maintain any of the other drivers. -- brandon s. allbery [linux,solaris,freebsd,perl] [EMAIL PROTECTED] system administrator [openafs,heimdal,too many hats] [EMAIL PROTECTED] electrical and computer engineering, carnegie mellon university KF8NH ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS UDP mounts on RELENG_6?
Hi Melvyn. On Sun, Dec 18, 2005 at 03:28:21PM +0100, Melvyn Sopacua wrote: OK. UDP NFS works as expected with amd64/bge on RELENG_6 of today. It does not work in the same network on i386/em for me. Still investigating. To rule out NFS, do something like syslogging remotely (also UDP). While NFS stalls at the same time ntp to the same host works without problems. So it's not a comüplete stall of all UDP traffic.I guess there's something that's only triggered by a certain combination of things. At the moment I'm building RELENG_6_0 on the server to find out, if the regression was from 5 to 6 or from 6.0 to 6-STABLE. - Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | pgpKA3JTVoc4P.pgp Description: PGP signature
Re: NFS UDP mounts on RELENG_6?
Hi. On Sun, Dec 18, 2005 at 04:50:29PM +0100, Fabian Keil wrote: Which kind GigE Interface do you use? Client: [EMAIL PROTECTED] ~ $pciconf -lv| grep em0 -A 2 [EMAIL PROTECTED]:1:0: class=0x02 card=0x05491014 chip=0x101e8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82540EP Gigabit Ethernet Controller (Mobile)' Server: [EMAIL PROTECTED] ~ $pciconf -lv| grep re[01] -A 2 [EMAIL PROTECTED]:9:0: class=0x02 card=0x816910ec chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' -- [EMAIL PROTECTED]:10:0: class=0x02 card=0x601b182d chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' re0 is made by Vivanco, re1 is a Sitecom card. So at least the server does not have an em interface in your case. I have an i386 RELENG_6 client running (on a 5.4 server) with an em interface for NFS and don't have any problems with this one. Also my em interface is a different chip: [EMAIL PROTECTED]:2:0: class=0x02 card=0x10768086 chip=0x10768086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82547EI Gigabit Ethernet Controller' class= network subclass = ethernet em1: Intel(R) PRO/1000 Network Connection, Version - 2.1.7 port 0xc400-0xc43f mem 0xf202-0xf203 ,0xf200-0xf201 irq 17 at device 2.0 on pci3 It's actually mentioned in CVS log for src/sys/dev/em/if_em_hw.c in the last commit: --- cut here --- revision 1.89 date: 2005/11/24 01:44:48; author: glebius; state: Exp; lines: +131 -77 Merge in new driver version from Intel - 3.2.18. The most important change is support for adapters based on 82571 and 82572 chips. Tested on: 82547EI on i386 Tested on: 82540EM on sparc64 Everything has been fine on 5.4, though. - Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | pgp1702kOLLs9.pgp Description: PGP signature
