xptioctl pass driver usb scsi driver problem (solved)
Hello, Just wanted to share with the list that I solved this problem today, and looking at the recent archives this has come up recently without any solutions so here it is. FYI, there was an answer by Andrew Thompson in the thread USB2 vs SCSI pass-through? of Feb 25th 2010 which hinted at the solution but the OP never manifested if he had actually solved the problem. If you get this in dmesg when you plug in your usb mass storage device: xptioctl: pass driver is not in the kernel xptioctl: put device pass in your kernel config file It probably means that HAL (you are probably running Gnome) has interfered with the assigning if dev by the kernel. All you have to do is disable hal for a moment, unplug and replug and voila! it' s fixed. Then you safely start HAL back up again. There is no doubt, a better solution, like fixing the root of the HAL problem but this simple workaround will avoid ruining your day. 1) /usr/local/etc/rc.d/hald stop 2) unplug and re-plug the device 3) dmesg, camcontrol, mount, etc. 4) /usr/local/etc/rc.d/hald stop Best, Alejandro Imass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Driver Problem: Broadcom NetXtreme Gigabit Ethernet
Hello again. Can anybody help? Or no one? 2009/4/9 Alexander Tarasov mr.ta...@gmail.com With GENERIC I have same problem. My network card is Broadcom NetXtreme Gigabit Ethernet.. (14e4:1684 subsystem 1025:014b). I think, it's BCM5764. 2009/4/9, Chris Rees utis...@googlemail.com: 2009/4/9 Alexander Tarasov mr.ta...@gmail.com: Hi, All! After installing FreeBSD 7.1 I've got problem with my network card. [root ~]# uname -a FreeBSD 7.1-RELEASE FreeBSD 7.1-RELEASE #1: Thu Apr 9 13:34:46 NOVST 2009 root@:/usr/obj/usr/src/sys/LAPTOP i386 [root ~]# pciconf -lv ... cut ... no...@pci0:6:0:0:class=0x02 card=0x014b1025 chip=0x168414e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' class = newtwork subclass = ethernet [root ~]# dmesg | grep bge [root ~]# ifconfig -a lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 inet 127.0.0.1 netmask 0xff00 I've compiled my kernel with device miibus and device bge (my kernel config is GENERIC without FireWare RAIDs). What does it mean? Is somethere driver for this card? Sorry for my terrible English =) Alexander V Tarasov ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Are you sure you didn't comment out any miibus lines or anything like that? Try with the GENERIC kernel, and kldload bge to see what happens. Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Driver Problem: Broadcom NetXtreme Gigabit Ethernet
On Tue, 21 Apr 2009 16:41:24 +0700 Alexander Tarasov wrote: Hello again. Can anybody help? Or no one? Please, don't top-post, do what you were recommended and show the results. 2009/4/9 Alexander Tarasov mr.ta...@gmail.com With GENERIC I have same problem. My network card is Broadcom NetXtreme Gigabit Ethernet.. (14e4:1684 subsystem 1025:014b). I think, it's BCM5764. 2009/4/9, Chris Rees utis...@googlemail.com: 2009/4/9 Alexander Tarasov mr.ta...@gmail.com: Hi, All! After installing FreeBSD 7.1 I've got problem with my network card. [root ~]# uname -a FreeBSD 7.1-RELEASE FreeBSD 7.1-RELEASE #1: Thu Apr 9 13:34:46 NOVST 2009 root@:/usr/obj/usr/src/sys/LAPTOP i386 [root ~]# pciconf -lv ... cut ... no...@pci0:6:0:0:class=0x02 card=0x014b1025 chip=0x168414e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' class = newtwork subclass = ethernet [root ~]# dmesg | grep bge [root ~]# ifconfig -a lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 inet 127.0.0.1 netmask 0xff00 I've compiled my kernel with device miibus and device bge (my kernel config is GENERIC without FireWare RAIDs). What does it mean? Is somethere driver for this card? Sorry for my terrible English =) Alexander V Tarasov ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Are you sure you didn't comment out any miibus lines or anything like that? Try with the GENERIC kernel, and kldload bge to see what happens. Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org WBR -- bsam ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Driver Problem: Broadcom NetXtreme Gigabit Ethernet
Hi, All! After installing FreeBSD 7.1 I've got problem with my network card. [root ~]# uname -a FreeBSD 7.1-RELEASE FreeBSD 7.1-RELEASE #1: Thu Apr 9 13:34:46 NOVST 2009 root@:/usr/obj/usr/src/sys/LAPTOP i386 [root ~]# pciconf -lv ... cut ... no...@pci0:6:0:0:class=0x02 card=0x014b1025 chip=0x168414e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' class = newtwork subclass = ethernet [root ~]# dmesg | grep bge [root ~]# ifconfig -a lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 inet 127.0.0.1 netmask 0xff00 I've compiled my kernel with device miibus and device bge (my kernel config is GENERIC without FireWare RAIDs). What does it mean? Is somethere driver for this card? Sorry for my terrible English =) Alexander V Tarasov ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Driver Problem: Broadcom NetXtreme Gigabit Ethernet
2009/4/9 Alexander Tarasov mr.ta...@gmail.com: Hi, All! After installing FreeBSD 7.1 I've got problem with my network card. [root ~]# uname -a FreeBSD 7.1-RELEASE FreeBSD 7.1-RELEASE #1: Thu Apr 9 13:34:46 NOVST 2009 root@:/usr/obj/usr/src/sys/LAPTOP i386 [root ~]# pciconf -lv ... cut ... no...@pci0:6:0:0: class=0x02 card=0x014b1025 chip=0x168414e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' class = newtwork subclass = ethernet [root ~]# dmesg | grep bge [root ~]# ifconfig -a lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 inet 127.0.0.1 netmask 0xff00 I've compiled my kernel with device miibus and device bge (my kernel config is GENERIC without FireWare RAIDs). What does it mean? Is somethere driver for this card? Sorry for my terrible English =) Alexander V Tarasov ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Are you sure you didn't comment out any miibus lines or anything like that? Try with the GENERIC kernel, and kldload bge to see what happens. Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Ответ: Driver Problem: Broadcom Ne tXtreme Gigabit Ethernet
With GENERIC I have same problem. My network card is Broadcom NetXtreme Gigabit Ethernet.. (14e4:1684 subsystem 1025:014b). I think, it's BCM5764. 2009/4/9, Chris Rees utis...@googlemail.com: 2009/4/9 Alexander Tarasov mr.ta...@gmail.com: Hi, All! After installing FreeBSD 7.1 I've got problem with my network card. [root ~]# uname -a FreeBSD 7.1-RELEASE FreeBSD 7.1-RELEASE #1: Thu Apr 9 13:34:46 NOVST 2009 root@:/usr/obj/usr/src/sys/LAPTOP i386 [root ~]# pciconf -lv ... cut ... no...@pci0:6:0:0: class=0x02 card=0x014b1025 chip=0x168414e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' class = newtwork subclass = ethernet [root ~]# dmesg | grep bge [root ~]# ifconfig -a lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 inet 127.0.0.1 netmask 0xff00 I've compiled my kernel with device miibus and device bge (my kernel config is GENERIC without FireWare RAIDs). What does it mean? Is somethere driver for this card? Sorry for my terrible English =) Alexander V Tarasov ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Are you sure you didn't comment out any miibus lines or anything like that? Try with the GENERIC kernel, and kldload bge to see what happens. Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: i810 driver problem SOLVED
Predrag Punosevac wrote: I was wondering if anybody encountered any problems with i810 video driver on 7.0Beta15 current. Namely I did yesterday a fresh installation of an older Pentium III machine and was unable to get X going. I got Xorg as pkg_add -r by the way and the rest of the system was installed from ISO image. Yes, I did have Section ServerFlags Option IgnoreAbi on EndSection I looked carefully xorg.conf.new and the listed video driver was i810. I did not manually compile that driver as I thought that was included into XOrg( at least on two other new computers I use i810 driver and it was included into XOrg). I tried though to load it manually into kernel by editing load.conf file. Sorry I am not enclosing log file as I wiped installation. It was very late last night and I thought it will take me half an hour to get things working. I end up spending 3 hours. Then I tried PC-BSD 1.4 which is 6.2 stable from July and everything went without a hitch. I checked xorg.conf and I saw that the listed driver is Xf86-video-intel-2.1.1 Should I try to install Xf86-video-intel-2.1.1 and then just try to hand configure xorg.conf file. I did notice some discussion yesterday about i810 but I thought it was relevant just for upgrading not for the new installation. Any input or suggestion will be appreciated. Predrag Punosevac I solved the problem after careful examination of .log file. The default color depth of the xorg.conf file is 32 which is unsupported by i810 driver according to xorg message. Setting up DefaultDepth 16 in the section Screen will take care of the problem. Changing syn vertical and horizontal syn rates is not enough. Old DeLL dimension with FreeBSD 7.0 beta 1.5 looks to me like new:-) I thank to all of you who tried to help me out. Cheers Predrag Punosevac ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: i810 driver problem
I was monkeying around with the xorg.conf.new file and I was able to get going X -config /root/xorg.conf.new. However when I cp /root/xorg.conf.new /etc/X11/xorg.conf.new and startx the X would start without clients and then would crush within a second. I could just see various colors all over the place. I assume you did #cp /root/xorg.conf.new /etc/xorg.conf? (not /etc/xorg.conf.new) Best regards, Tino Engel pgp5xZ3CRCvVv.pgp Description: PGP signature
Re: i810 driver problem
Predrag Punosevac wrote: I was wondering if anybody encountered any problems with i810 video driver on 7.0Beta15 current. Namely I did yesterday a fresh installation of an older Pentium III machine and was unable to get X going. I got Xorg as pkg_add -r by the way and the rest of the system was installed from ISO image. Yes, I did have Section ServerFlags Option IgnoreAbi on EndSection I looked carefully xorg.conf.new and the listed video driver was i810. I did not manually compile that driver as I thought that was included into XOrg( at least on two other new computers I use i810 driver and it was included into XOrg). I tried though to load it manually into kernel by editing load.conf file. Sorry I am not enclosing log file as I wiped installation. It was very late last night and I thought it will take me half an hour to get things working. I end up spending 3 hours. Stupid question (especially since I dunno much about 7.0 yet), but you did have agp_load=YES in loader.conf, and /dev/agpgart was created successfully? Note that I suppose it's possible this isn't necessary in 7.x, but it has been in the other branches for a Long Time Now(tm). Then I tried PC-BSD 1.4 which is 6.2 stable from July and everything went without a hitch. I checked xorg.conf and I saw that the listed driver is Xf86-video-intel-2.1.1 Should I try to install Xf86-video-intel-2.1.1 and then just try to hand configure xorg.conf file. I did notice some discussion yesterday about i810 but I thought it was relevant just for upgrading not for the new installation. Any input or suggestion will be appreciated. Predrag Punosevac Hoping it helps, Kevin Kinsey -- Your computer account is overdrawn. Please reauthorize. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: i810 driver problem
Kevin Kinsey wrote: Predrag Punosevac wrote: I was wondering if anybody encountered any problems with i810 video driver on 7.0Beta15 current. Namely I did yesterday a fresh installation of an older Pentium III machine and was unable to get X going. I got Xorg as pkg_add -r by the way and the rest of the system was installed from ISO image. Yes, I did have Section ServerFlags Option IgnoreAbi on EndSection I looked carefully xorg.conf.new and the listed video driver was i810. I did not manually compile that driver as I thought that was included into XOrg( at least on two other new computers I use i810 driver and it was included into XOrg). I tried though to load it manually into kernel by editing load.conf file. Sorry I am not enclosing log file as I wiped installation. It was very late last night and I thought it will take me half an hour to get things working. I end up spending 3 hours. Stupid question (especially since I dunno much about 7.0 yet), but you did have agp_load=YES in loader.conf, and /dev/agpgart was created successfully? Note that I suppose it's possible this isn't necessary in 7.x, but it has been in the other branches for a Long Time Now(tm). Yes I did have agp_load=YES. I have done some additional testing last night on that machine. First of all I tried OpenBSD 4.1 and I could start x even without xorg.conf file which is usually true in OpenBSD but the XOrg version is 6.9. Then I did fresh installation of 7.0 and and did pkg_add -r Xorg. I was monkeying around with the xorg.conf.new file and I was able to get going X -config /root/xorg.conf.new. However when I cp /root/xorg.conf.new /etc/X11/xorg.conf.new and startx the X would start without clients and then would crush within a second. I could just see various colors all over the place. Then I tried to use xorgconfig utility and created xorg.conf file with very conservative options ( I decreased the number of colors) This time when I started x everything was fine for about 3 seconds and then crash again and colors all over the place. (kernel is also frozen) I think I am getting somewhere but I need to play with this thing longer. For some reason when I xorgcfg -textmode I would get reply that the command is not recognized. I will check this again. I will try couple other things. I will also try to install 6.2 stable and see if I can get Xorg going. This is an old DeLL dimension computer and the monitor I was using is Sony trinitron 15in. I will try with my 17in DeLL monitor to see if that makes any difference. Then I tried PC-BSD 1.4 which is 6.2 stable from July and everything went without a hitch. I checked xorg.conf and I saw that the listed driver is Xf86-video-intel-2.1.1 Should I try to install Xf86-video-intel-2.1.1 and then just try to hand configure xorg.conf file. I did notice some discussion yesterday about i810 but I thought it was relevant just for upgrading not for the new installation. Any input or suggestion will be appreciated. Predrag Punosevac Hoping it helps, Kevin Kinsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
i810 driver problem
I was wondering if anybody encountered any problems with i810 video driver on 7.0Beta15 current. Namely I did yesterday a fresh installation of an older Pentium III machine and was unable to get X going. I got Xorg as pkg_add -r by the way and the rest of the system was installed from ISO image. Yes, I did have Section ServerFlags Option IgnoreAbi on EndSection I looked carefully xorg.conf.new and the listed video driver was i810. I did not manually compile that driver as I thought that was included into XOrg( at least on two other new computers I use i810 driver and it was included into XOrg). I tried though to load it manually into kernel by editing load.conf file. Sorry I am not enclosing log file as I wiped installation. It was very late last night and I thought it will take me half an hour to get things working. I end up spending 3 hours. Then I tried PC-BSD 1.4 which is 6.2 stable from July and everything went without a hitch. I checked xorg.conf and I saw that the listed driver is Xf86-video-intel-2.1.1 Should I try to install Xf86-video-intel-2.1.1 and then just try to hand configure xorg.conf file. I did notice some discussion yesterday about i810 but I thought it was relevant just for upgrading not for the new installation. Any input or suggestion will be appreciated. Predrag Punosevac ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mplayer / snd_hda / Xorg; intel driver problem
Not so long ago I aquired a new laptop. Appart from some issues which were to be expected everything works fine; appart from one thing: When playing videos with mplayer it hangs up my system at random times( Mostly within half an hour of videplayback though ) . The video-playback stops, sound blocks and I can't acces my laptop anymore; not even switch to tty0 to check for debug messages. My guess is it has something to do with either the audio or the videodriver, respectively snd_hda and the intel driver in Xorg. So I did 2 tests, without gaining any additional knowlege however: I tried unloading the snd_hda module and sound modules and play the video to see if there was a problem with the video-part. I let it ran for a couple of hours and everything seemed to be fine The second thing I tried was just using mplayer -vo null and playing the video. Same as the above test; it ran fine for a couple of hours straight. So no I have no Idea anymore what I could do to determine whatever is going wrong. I hope someone else has an idea or might have a pointer to what I could do to gain more information about this. The relevant system data: [EMAIL PROTECTED] uname -a FreeBSD Rena.FStaals.net 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sat Oct 13 12:59:51 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 [EMAIL PROTECTED] kldstat Id Refs AddressSize Name 1 15 0xc040 923830 kernel 21 0xc0d24000 14e24snd_hda.ko 32 0xc0d39000 52a08sound.ko 41 0xc0d8c000 6b270acpi.ko 51 0xc5672000 11000ext2fs.ko 61 0xc592a000 22000linux.ko 71 0xc5a2d000 6000 i915.ko 81 0xc5a33000 f000 drm.ko [EMAIL PROTECTED] mplayer --version MPlayer dev-SVN-r24813-4.2.1 (C) 2000-2007 MPlayer Team CPU: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz (Family: 6, Model: 15, Stepping: 10) CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1 Compiled for x86 CPU with extensions: MMX MMX2 SSE SSE2 [EMAIL PROTECTED] dmesg -a | grep pcm pcm0: Intel 82801H High Definition Audio Controller mem 0xfe9fc000-0xfe9f irq 21 at device 27.0 on pci0 pcm0: [ITHREAD] pcm0: HDA Codec: Sigmatel (Unknown) pcm0: HDA Driver Revision: 20070710_0047 [EMAIL PROTECTED] dmesg -a | grep agp agp0: Intel GM965 SVGA controller on vgapci0 agp0: detected 7676k stolen memory agp0: aperture size is 256M my xorg config; ( which is just basically what X --configure generated ) : http://fstaals.net/junk/xorg.conf Regards, -- -Frank Staals ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Sound driver problem
Hello, I have a problem running sound, I followed the guide but it doesn't work. I am using a Compaq Prescario v6000 with a AMD sempron and Nvidia go 6150. I ran: #kldload snd_driver and it gave this # cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: also dmesg gave this: # dmesg Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-RELEASE #0: Fri Jan 12 10:40:27 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC ACPI APIC Table: HP APIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Mobile AMD Sempron(tm) Processor 3500+ (1808.24-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x40fc2 Stepping = 2 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 Features2=0x2001SSE3,CX16 AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow+,3DNow AMD Features2=0x19LAHF,b3,CR8 real memory = 938475520 (895 MB) avail memory = 900784128 (859 MB) MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 1.1 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: HPQOEM SLIC-MPC on motherboard acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 acpi_ec0: Embedded Controller: GPE 0x10 port 0x62,0x66 on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 acpi_acad0: AC Adapter on acpi0 battery0: ACPI Control Method Battery on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci_link9: BIOS IRQ 10 for 0.10.INTB is invalid pci0: ACPI PCI bus on pcib0 pci0: memory, RAM at device 0.0 (no driver attached) pci0: memory, RAM at device 0.1 (no driver attached) pci0: memory, RAM at device 0.2 (no driver attached) pci0: memory, RAM at device 0.3 (no driver attached) pci0: memory, RAM at device 0.4 (no driver attached) pci0: memory, RAM at device 0.5 (no driver attached) pci0: memory, RAM at device 0.6 (no driver attached) pci0: memory, RAM at device 0.7 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 3.0 on pci0 pci3: ACPI PCI bus on pcib2 pci3: network at device 0.0 (no driver attached) nvidia0: GeForce Go 6150 mem 0xb200-0xb2ff,0xc000-0xcfff,0xb100-0xb1ff irq 18 at device 5.0 on pci0 nvidia0: [GIANT-LOCKED] pci0: memory, RAM at device 9.0 (no driver attached) isab0: PCI-ISA bridge port 0x1d00-0x1d7f at device 10.0 on pci0 isa0: ISA bus on isab0 pci0: serial bus, SMBus at device 10.1 (no driver attached) pci0: processor at device 10.3 (no driver attached) ohci0: OHCI (generic) USB controller mem 0xb0004000-0xb0004fff irq 22 at device 11.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 8 ports with 8 removable, self powered ehci0: EHCI (generic) USB 2.0 controller mem 0xb0005000-0xb00050ff irq 22 at device 11.1 on pci0 ehci0: [GIANT-LOCKED] usb1: EHCI version 1.0 usb1: companion controller, 8 ports each: usb0 usb1: EHCI (generic) USB 2.0 controller on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 8 ports with 8 removable, self powered atapci0: nVidia nForce MCP51 UDMA133 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x3080-0x308f at device 13.0 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 atapci1: nVidia nForce MCP51 SATA300 controller port 0x30c0-0x30c7,0x30b4-0x30b7,0x30b8-0x30bf,0x30b0-0x30b3,0x3090-0x309f mem 0xb0006000-0xb0006fff irq 23 at device 14.0 on pci0 ata2: ATA channel 0 on atapci1 ata3: ATA channel 1 on atapci1 pcib3: ACPI PCI-PCI bridge at device 16.0 on pci0 pci_link0: BIOS IRQ 11 for 7.5.INTA is invalid pci_link1: BIOS IRQ 11 for 7.5.INTB is invalid pci7: ACPI PCI bus on pcib3 fwohci0: 1394 Open Host Controller Interface mem 0xbc00-0xbc0007ff irq 9 at device 5.0 on pci7 fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:24:1b:00:b7:bb:0b:00 fwohci0: Phy 1394a available S400, 1 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: IEEE1394(FireWire) bus on fwohci0 fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:24:1b:bb:0b:00 fwe0: Ethernet address: 02:24:1b:bb:0b:00 fwe0: if_start running deferred for Giant sbp0: SBP-2/SCSI over FireWire on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode
cardbus card driver problem
Hallo everybody, I have a problem with a ComBlock COM1300 cardbus card http://www.comblock.com/com1300.htm I need to get this card working on my laptop since I need to work on it for my thesis project. I wrote a driver for this card but I don't know if it works or not becouse a I get a cardbus detection error on booting. Dmesg with all hw.cbb and hw.cardbus debug options enabled gives me this output: cbb0: card inserted: event=0x, state=3821 cbb0: cbb_power: 3V TUPLE: LINKTARGET [3]: 43 49 53 Product version: 5.2 Product name: MSS | COM 1300 | Manufacturer ID: feff0101 TUPLE: Unknown(0x04) [6]: 03 01 00 00 00 00 TUPLE: Unknown(0x05) [11]: c1 39 71 b5 1e 66 76 54 02 a1 03 cardbus0: Opening BAR: type=IO, bar=10, len=0100 cardbus0: Opening BAR: type=MEM, bar=14, len=10 CIS reading done cardbus0: Non-prefetchable memory at 9000-900f cardbus0: IO port at 4000-40ff cardbus0: old, non-VGA display device at device 0.0 (no driver attached) cbb0: cbb_power: 0V Is this problem related to my laptop hardware configuration or is it a driver problem?? other?? What is TUPLE (0x04 o 0x05) problem?? Any suggestion?? Tanks in advance. Michele -- Michele Endrici Via carraia 4 - Don - TN tel: 348-7295670 [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G driver problem
I had the same issue when installing fuse-fs the first time - I just ran sysinstall again, went to distributions, then choose the source dist, installed that, rebooted, and fusefs built and installed fine. Steve On 2/21/07, Jason Gretz [EMAIL PROTECTED] wrote: Hey guys, I got a prob here, I am trying to install the new NTFS-3G driver, which just went 1.0, and This is what the output of make install make clean got me: === Installing for fusefs-ntfs-0.20070207RC1 === fusefs-ntfs-0.20070207RC1 depends on file: /usr/local/modules/fuse.ko - not found ===Verifying reinstall for /usr/local/modules/fuse.ko in /usr/ports/sysutils/fusefs-kmod === fusefs-kmod-0.3.0_4 requires the Kernel source to be installed. Set SRC_BASE if it is not in /usr/src. Thanks! Jason -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.441 / Virus Database: 268.18.3/696 - Release Date: 2/21/2007 3:19 PM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Steve Franks, KE7BTE Staff Engineer La Palma Devices, LLC http://www.lapalmadevices.com (520) 312-0089 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NTFS-3G driver problem
Hey guys, I got a prob here, I am trying to install the new NTFS-3G driver, which just went 1.0, and This is what the output of make install make clean got me: === Installing for fusefs-ntfs-0.20070207RC1 === fusefs-ntfs-0.20070207RC1 depends on file: /usr/local/modules/fuse.ko - not found ===Verifying reinstall for /usr/local/modules/fuse.ko in /usr/ports/sysutils/fusefs-kmod === fusefs-kmod-0.3.0_4 requires the Kernel source to be installed. Set SRC_BASE if it is not in /usr/src. Thanks! Jason -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.441 / Virus Database: 268.18.3/696 - Release Date: 2/21/2007 3:19 PM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G driver problem
Jason Gretz wrote: Hey guys, I got a prob here, I am trying to install the new NTFS-3G driver, which just went 1.0, and This is what the output of make install make clean got me: === Installing for fusefs-ntfs-0.20070207RC1 === fusefs-ntfs-0.20070207RC1 depends on file: /usr/local/modules/fuse.ko - not found ===Verifying reinstall for /usr/local/modules/fuse.ko in /usr/ports/sysutils/fusefs-kmod === fusefs-kmod-0.3.0_4 requires the Kernel source to be installed. Set SRC_BASE if it is not in /usr/src. Well, do you have the source distribution installed in the usual place? It would appear not Kevin Kinsey -- Each of us bears his own Hell. -- Publius Vergilius Maro (Virgil) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Driver Problem
Hi I'm a FreeBSD 5.3 user. Lately I tried to upgrade to FreeBSD 6.2 but it was not able to detect my SATA hard disk ( with FreeBSD 5.3 installed ), why? - 8:00? 8:25? 8:40? Find a flick in no time with theYahoo! Search movie showtime shortcut. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NGE Network Driver Problem.
On 25-Aug-06, at 14:37, Robert Huff wrote: After doing some digging, I've found that there was a patch applied to RELENG_6, modifying the sk driver to ignore my revision of card, and instructing the re driver to attach. This is probably why it works for Robert and not for me; he's probably running 6 something, while I'm still on 5 STABLE. That machine is -CURRENT, and was at the time of the hardware change. NB: at the time this happened, the pci scan code did not automagically connect the card to the re driver; however, forcing the loading of if_re.ko did the trick. Just for archival purposes, in case others need this; I solved my problem by pulling the modifications from RELENG_6 into my local source, and recompiling my kernel with the drivers included. I don't seem to require the kernel module like Robert does, as the driver attaches and initializes when compiled right in. The files to look at are: if_re.c, if_sk.c, if_skreg,h, and if_rlreg.h. Thanks for your help Robert. -- Jeremy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NGE Network Driver Problem.
On 24-Aug-06, at 22:17, Robert Huff wrote: Probably. The chip name means a Realtek ptui! 8169, and that takes the re() driver. That's pretty much the same way I feel about 'em. Shouldn't hurt. I fixed mine by a) removing both re and skc from the kernel config file and b) adding if_re_load=YES to /boot/loader.conf. Your mileage may vary. Unfortunately, this didn't work out for me. I tried a bit of other fiddling as well and didn't get any change in behaviour. I'll just take the card back and maybe try a D-Link ptui! one with a different chipset. Thanks a lot for your suggestions. -- Jeremy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NGE Network Driver Problem.
On 24-Aug-06, at 22:17, Robert Huff wrote: Probably. The chip name means a Realtek ptui! 8169, and that takes the re() driver. Unfortunately, this didn't work out for me. I tried a bit of other fiddling as well and didn't get any change in behaviour. I'll just take the card back and maybe try a D-Link ptui! one with a different chipset. After doing some digging, I've found that there was a patch applied to RELENG_6, modifying the sk driver to ignore my revision of card, and instructing the re driver to attach. This is probably why it works for Robert and not for me; he's probably running 6 something, while I'm still on 5 STABLE. Applying the patch to these drivers myself is not a problem, but I'm just wondering if this can / will / will ever be pushed into the RELENG_5 branch. Does anyone know, or at the very least, who I should be talking to? Thanks. -- Jeremy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NGE Network Driver Problem.
Jeremy Karlson writes: After doing some digging, I've found that there was a patch applied to RELENG_6, modifying the sk driver to ignore my revision of card, and instructing the re driver to attach. This is probably why it works for Robert and not for me; he's probably running 6 something, while I'm still on 5 STABLE. That machine is -CURRENT, and was at the time of the hardware change. NB: at the time this happened, the pci scan code did not automagically connect the card to the re driver; however, forcing the loading of if_re.ko did the trick. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NGE Network Driver Problem.
I'm having difficulty getting a new Linksys EG1032 gigabit network card to work on FreeBSD 5.5-STABLE. I get the following relevant messages on boot: skc0: Linksys EG1032 Gigabit Ethernet port 0xe800-0xe8ff mem 0xd8002000-0xd80020ff irq 11 at device 15.0 on pci0 skc0: failed: rid 0x10 is ioport, requested 3 sk0: couldn't map ports/memory device_attach: skc0 attach returned 6 For some background: - device miibus and device sk are compiled into the kernel. - I've looked at the man page sk(4), which doesn't provide any insight. - Google brings up a few hits on this problem, but no apparent solutions. Ideas? Thanks, -- Jeremy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NGE Network Driver Problem.
Jeremy Karlson writes: I'm having difficulty getting a new Linksys EG1032 gigabit network card to work on FreeBSD 5.5-STABLE. I get the following relevant messages on boot: skc0: Linksys EG1032 Gigabit Ethernet port 0xe800-0xe8ff mem 0xd8002000-0xd80020ff irq 11 at device 15.0 on pci0 skc0: failed: rid 0x10 is ioport, requested 3 sk0: couldn't map ports/memory device_attach: skc0 attach returned 6 Depending on when you bought the card, the correct driver may be re(4), not skc. Check the output of pciconf -l -v; mine shows: [EMAIL PROTECTED]:12:0: class=0x02 card=0x00241737 chip=0x10321737 rev=0x10 hdr=0x00 vendor = 'Linksys' device = 'EG1032 Gigabit Ethernet' class= network subclass = ethernet Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NGE Network Driver Problem.
On 24-Aug-06, at 21:04, Robert Huff wrote: Depending on when you bought the card, the correct driver may be re(4), not skc. Check the output of pciconf -l -v; mine shows: [EMAIL PROTECTED]:12:0: class=0x02 card=0x00241737 chip=0x10321737 rev=0x10 hdr=0x00 vendor = 'Linksys' device = 'EG1032 Gigabit Ethernet' class= network subclass = ethernet I bought the card two hours hours ago. :-P pciconf -l -v shows: [EMAIL PROTECTED]:9:0: class=0x02 card=0x00241737 chip=0x10321737 rev=0x10 hdr=0x00 vendor='Linksys' device='EG1032 Gigabit Ethernet' class=network subclass=ethernet Looks the same as yours. Looking at the physical card directly, I see Model No: EG1032 ver.3, and the chip says RTL8169S-32. Is yours the same too? The re driver is already compiled into the kernel as well. Maybe removing the sk driver would make a difference? -- Jeremy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
driver problem or HD dying /dead?
Hey List- running: FreeBSD 6.1-pre hardware: 3ware 9550SX using the pre- twa driver in a RAID5 (3 drives + 1 standby) My logs starting filling up with this and I noticed the server rebooted itelf a few days back. Is this a driver issue or is one of the drives going south? It looks to me to be the da0 drive (ie: the first one in the array), but I just wanted to make sure I'm reading this correctly. It spits a group of these out about every 20 seconds. Thanks :) Apr 26 23:34:37 kern.crit skie kernel: twa0: ERROR: (0x03: 0x0202): Drive ECC error: port=0 Apr 26 23:34:37 kern.crit skie kernel: (da0:twa0:0:0:0): WRITE(10). CDB: 2a 0 9 2e 4f 5f 0 0 40 0 Apr 26 23:34:37 kern.crit skie kernel: (da0:twa0:0:0:0): CAM Status: SCSI Status Error Apr 26 23:34:37 kern.crit skie kernel: (da0:twa0:0:0:0): SCSI Status: Check Condition Apr 26 23:34:37 kern.crit skie kernel: (da0:twa0:0:0:0): MEDIUM ERROR asc:11,0 Apr 26 23:34:37 kern.crit skie kernel: (da0:twa0:0:0:0): Unrecovered read error Apr 26 23:34:37 kern.crit skie kernel: (da0:twa0:0:0:0): Retrying Command (per Sense Data) Apr 26 23:34:54 kern.crit skie kernel: twa0: ERROR: (0x03: 0x0202): Drive ECC error: port=0 Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): WRITE(10). CDB: 2a 0 9 2e 4f 5f 0 0 40 0 Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): CAM Status: SCSI Status Error Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): SCSI Status: Check Condition Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): MEDIUM ERROR asc:11,0 Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): Unrecovered read error Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): Retrying Command (per Sense Data) Apr 26 23:34:54 kern.crit skie kernel: twa0: ERROR: (0x03: 0x0202): Drive ECC error: port=0 Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): WRITE(10). CDB: 2a 0 9 2e 4f 5f 0 0 40 0 Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): CAM Status: SCSI Status Error Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): SCSI Status: Check Condition Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): MEDIUM ERROR asc:11,0 Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): Unrecovered read error Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): Retrying Command (per Sense Data) Apr 26 23:34:54 kern.crit skie kernel: twa0: ERROR: (0x03: 0x0202): Drive ECC error: port=0 Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): WRITE(10). CDB: 2a 0 9 2e 4f 5f 0 0 40 0 Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): CAM Status: SCSI Status Error Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): SCSI Status: Check Condition Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): MEDIUM ERROR asc:11,0 Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): Unrecovered read error Apr 26 23:34:54 kern.crit skie kernel: (da0:twa0:0:0:0): Retrying Command (per Sense Data) -- Henrik Hudson [EMAIL PROTECTED] -- There are 10 kinds of people in the world: Those who understand binary and those who don't... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sangoma s518 adsl card sppp driver problem.
Hi, I have a problem with s518 sangoma adsl card. I have FreeBSD-5.4 Release installed and installed wanpipe driver and software. Card has been detected perfectly that I can see on dmesg output. I have created a conf file using wancfg command and after running wanrouter start I get following error: wanpipe: S518-PCI ADSL card found, cpu(s) 1, bus #0, slot #19, irq #10 WANPIPE: Allocating maximum 1 devices: WANPIPE: wanpipe1-wanpipe1. WANPIPE(tm) L.I.P Network Layer Beta5-2.8.2 (c) 1995-2004 Sangoma Technologies I nc. WanpipeLIP: Protocols: FR PPP CHDLC Registering Wanpipe Lip protocol Processing WAN device wanpipe1... wanpipe1: Locating: ADSL card, CPU , PciSlot=19, PciBus=0 wanpipe1: Found: ADSL card, CPU A, PciSlot=19, PciBus=0 wanpipe1: Starting hardware setup... wanpipe1: ADSL PCI memory at 0xe800 wanpipe1: IRQ 10 allocated to the ADSL card wanpipe1: Set interrupt handler... wanpipe1: Starting ADSL device. wanpipe1: Initializing S518 ADSL card... wanpipe1: Initializing LAN Interface wanpipe1: Enabling ADSL (ATM OAM) Watchdog wanpipe1: ADSL HW Addr: 00:77:77:77:7a:db wanpipe1: Creating new WAN interface waad0... wanpipe1: Please verify that SPPP is enabled in your kernel! wanpipe1: Failed to create new interface (-22)! wanpipe1: Device already configured! # wanrouter debug Wanpipe environment/utilites/modules/operation OK I have compiled sppp in to the kernel but no luck again. I take wanpipe1: Please verify that SPPP is enabled in your kernel! message. Has anyone has a solution for that? --- Omer Faruk Sen http://www.EnderUNIX.ORG Software Development Team @ Turkey http://www.Faruk.NET For Public key: http://www.enderunix.org/ofsen/ofsen.asc *** AcikAcademy published a Turkish TCP/IP Book Acik Akademi'nin yeni kitabini duydunuz mu? http://www.acikakademi.com/catalog/tcpip/ Life is trouble.. Only Death is not! -Alexis Zorba ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Nvidia driver problem: video ram not detected
I'm using the latest nvidia driver with the FreeBSD AGP and it only detects 32meg of video ram even though the card has 128meg. I have the line VideoRam131072 in xorg.conf, but it has no effect. Any advice? Thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nvidia driver problem: video ram not detected
Justin R. Smith wrote: I'm using the latest nvidia driver with the FreeBSD AGP and it only detects 32meg of video ram even though the card has 128meg. If you mean the nvidia driver from the ports, then my 128Mb card detects just fine. If you mean the nv driver which comes with xorg, then try the nvidia driver from ports. If it is the nvidia driver then you could try the nvidia forum here: http://www.nvnews.net/vbulletin/forumdisplay.php?f=14 And I'm sure that more detail would help, like *which* nvidia card. At least then there would be some basis for comparison with others. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia driver problem
craig wrote: first off, the colour depth issue is resolved. once restarted, x loads the nvidia driver with the full 24bit colour depth. thanks for that. (II) NVIDIA(0): Connected display device(s): CRT-1, DFP-0 (WW) NVIDIA(0): Multiple displays connected, but only one display allowed; (WW) NVIDIA(0): using first display You have 2 monitors? If so, I recommend the TwinView config. It's tricky, but works well. no, i dont - i have a single samsung syncmaster 213t - but it has both analog and digital cables, as does the graphics cards. so i plugged them both in. this is where things are not perfect now. the nvidia drivers select the first of the two cables, ie. analog. whereas i would like to to take the digital. i cannot quite explain it, but the analog view is not as 'crisp' as the digital. how can i specify to use the 'second' monitor? i'll help where i can - this is a very fresh install of 5.3, and onto an empty disk - so no upgrades or changes, just a straight install. and i can pretty much remember most of what i've done to get here - if it helps i can certainly note the steps. perhaps you could see something in the sequence? gl seems to work fine - cracking render rates too! so...how can i be sure out the linux compatibitily answer? thanks, -- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia driver problem
craig wrote: this is where things are not perfect now. the nvidia drivers select the first of the two cables, ie. analog. whereas i would like to to take the digital. i cannot quite explain it, but the analog view is not as 'crisp' as the digital. how can i specify to use the 'second' monitor? a quick r through nvidia's tfm indicates a very simple solution. by adding Option IgnoreDisplayDevices CRT i get exactly what i am looking for. sorry for abusing your time... -- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
nvidia driver problem
hi all, i am having a problem getting the nvidia-provided freebsd drivers to work correctly. specifically, although the bsd-provided nv drivers work (albeit without any accel), when i switch to the nvidia-provided nvidia drivers, xorg loads into 8bit colour mode - which looks terrible! looking in /var/log/Xorg.0.log doesnt provide any clues (to me, at least!). there are no terrible errors or dire warnings that seem related. (find attached) and, as best as i can tell, my /etc/X11/xorg.conf seems just fine. (also find attached) what else would be useful to tell... i have an Intel 2.4Ghz on a Gigabyte GT motherboard, with 1GB ram. the card is an nVidia GeForce4Ti with 128MB also, i have removed agp from my kernel. and i have also attached sysctl -a hw.nvidia output any help would be greatly appreciated! much ta, -- [EMAIL PROTECTED] Release Date: 18 December 2003 X Protocol Version 11, Revision 0, Release 6.7 Build Operating System: FreeBSD 5.3 i386 [ELF] Current Operating System: FreeBSD jupiter.small-pla.net 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #2: Mon Jan 10 10:53:39 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/JUPITER i386 Build Date: 16 October 2004 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Mon Jan 10 11:40:06 2005 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout X.org Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (==) Keyboard: CustomKeycode disabled (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/Speedo/. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/Speedo/). (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/CID/. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/CID/). (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ (**) RgbPath set to /usr/X11R6/lib/X11/rgb (**) ModulePath set to /usr/X11R6/lib/modules (II) Module ABI versions: X.Org ANSI C Emulation: 0.2 X.Org Video Driver: 0.7 X.Org XInput driver : 0.4 X.Org Server Extension : 0.2 X.Org Font Renderer : 0.4 (II) Loader running on freebsd (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=X.Org Foundation compiled for 6.7.0, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=X.Org Foundation compiled for 6.7.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.7 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2570 card 1458,2570 rev 02 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2571 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 00:1d:0: chip 8086,24d2 card 1458,24d2 rev 02 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,24d4 card 1458,24d2 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,24d7 card 1458,24d2 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:3: chip 8086,24de card 1458,24d2 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,24dd card 1458,5006 rev 02 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card , rev c2 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,24d0 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,24db card 1458,24d2 rev 02 class 01,01,8a hdr 00 (II) PCI: 00:1f:3: chip 8086,24d3 card 1458,24d2 rev 02 class 0c,05,00 hdr 00 (II) PCI: 01:00:0: chip 10de,0281 card , rev a1 class 03,00,00 hdr 00 (II) PCI: 02:02:0: chip 1102,0002 card 1102,8061 rev 07 class 04,01,00 hdr 80 (II) PCI: 02:02:1: chip 1102,7002 card 1102,0020 rev 07 class 09,80,00 hdr 80 (II) PCI: 02:03:0: chip 1033,0035 card 1735,0035 rev 41 class 0c,03,10 hdr 80 (II) PCI: 02:03:1: chip 1033,0035 card 1735,0035 rev 41 class 0c,03,10 hdr 00 (II) PCI: 02:03:2: chip 1033,00e0 card 1735,00e0 rev 01 class 0c,03,20 hdr 00 (II) PCI: 02:04:0: chip 1106,3044 card 1106,3044 rev 43 class 0c,00,10 hdr 00 (II) PCI: 02:09:0: chip 11ab,4320 card 1458,e000 rev 13 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI
Re: nvidia driver problem
On Mon, Jan 10, 2005 at 12:07:21PM +0100, craig wrote: hi all, i am having a problem getting the nvidia-provided freebsd drivers to work correctly. specifically, although the bsd-provided nv drivers work (albeit without any accel), when i switch to the nvidia-provided nvidia drivers, xorg loads into 8bit colour mode - which looks terrible! looking in /var/log/Xorg.0.log doesnt provide any clues (to me, at least!). there are no terrible errors or dire warnings that seem related. (find attached) and, as best as i can tell, my /etc/X11/xorg.conf seems just fine. (also find attached) Not sure if it helps, but try adding the line DefaultDepth 24 to the Screen section: Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 24 SubSection Display Viewport 0 0 Depth 24 Modes 1600x1200 EndSubSection EndSection Good luck, Karel. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia driver problem
On Mon, 10 Jan 2005 12:07:21 +0100, craig wrote hi all, i am having a problem getting the nvidia-provided freebsd drivers to work correctly. specifically, although the bsd-provided nv drivers work (albeit without any accel), when i switch to the nvidia-provided nvidia drivers, xorg loads into 8bit colour mode - which looks terrible! looking in /var/log/Xorg.0.log doesnt provide any clues (to me, at least!). there are no terrible errors or dire warnings that seem related. (find attached) and, as best as i can tell, my /etc/X11/xorg.conf seems just fine. (also find attached) what else would be useful to tell... i have an Intel 2.4Ghz on a Gigabyte GT motherboard, with 1GB ram. the card is an nVidia GeForce4Ti with 128MB also, i have removed agp from my kernel. and i have also attached sysctl -a hw.nvidia output Adding the following in the screen section of xorg.conf might do the trick: DefaultDepth 24 any help would be greatly appreciated! much ta, -- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia driver problem
On 01/10/05 12:07 PM, craig sat at the `puter and typed: hi all, i am having a problem getting the nvidia-provided freebsd drivers to work correctly. specifically, although the bsd-provided nv drivers work (albeit without any accel), when i switch to the nvidia-provided nvidia drivers, xorg loads into 8bit colour mode - which looks terrible! looking in /var/log/Xorg.0.log doesnt provide any clues (to me, at least!). there are no terrible errors or dire warnings that seem related. (find attached) and, as best as i can tell, my /etc/X11/xorg.conf seems just fine. (also find attached) what else would be useful to tell... i have an Intel 2.4Ghz on a Gigabyte GT motherboard, with 1GB ram. the card is an nVidia GeForce4Ti with 128MB also, i have removed agp from my kernel. and i have also attached sysctl -a hw.nvidia output any help would be greatly appreciated! much ta, A few things: (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/Speedo/. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/Speedo/). (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/CID/. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/CID/). These are worth fixing, though minor - the entries tell you how. (--) NVIDIA(0): VideoRAM: 131072 kBytes (II) NVIDIA(0): Connected display device(s): CRT-1, DFP-0 (WW) NVIDIA(0): Multiple displays connected, but only one display allowed; (WW) NVIDIA(0): using first display (--) NVIDIA(0): Display device CRT-1: maximum pixel clock at 8 bpp: 350 MHz (--) NVIDIA(0): Display device CRT-1: maximum pixel clock at 16 bpp: 350 MHz (--) NVIDIA(0): Display device CRT-1: maximum pixel clock at 32 bpp: 350 MHz You have 2 monitors? If so, I recommend the TwinView config. It's tricky, but works well. Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option SWcursor# [bool] #Option HWcursor# [bool] #Option NoAccel # [bool] #Option ShadowFB# [bool] #Option UseFBDev# [bool] #Option Rotate # [str] #Option VideoKey# i #Option FlatPanel # [bool] #Option FPDither# [bool] #Option CrtcNumber # i # Option NoLogoTrue # Option RenderAccel True You might want to uncomment RenderAccel - try it both ways once you get your color depth right. # Option HWCursor 1 # Option CursorShadow True Option NvAGP 1 Identifier Card0 Driver nvidia VendorName nVidia Corporation BoardName NV28 [GeForce4 Ti 4200 AGP 8x] BusID PCI:1:0:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Viewport 0 0 Depth 24 Modes 1600x1200 EndSubSection EndSection As mentioned by the other posters, put the default depth speck in your screen section. hw.nvidia.agp.card.rates: 8x 4x hw.nvidia.agp.card.fw: supported hw.nvidia.agp.card.sba: supported hw.nvidia.agp.card.registers: 0x1f000e1b:0x1f004302 hw.nvidia.agp.status.status: enabled hw.nvidia.agp.status.driver: nvidia hw.nvidia.agp.status.rate: 8x hw.nvidia.agp.status.fw: disabled hw.nvidia.agp.status.sba: enabled hw.nvidia.version: NVIDIA FreeBSD x86 NVIDIA Kernel Module 1.0-6113 Mon Aug 2 16:08:32 PDT 2004 hw.nvidia.registry.EnableVia4x: 0 hw.nvidia.registry.EnableALiAGP: 0 hw.nvidia.registry.NvAGP: 1 hw.nvidia.registry.EnableAGPSBA: 0 hw.nvidia.registry.EnableAGPFW: 0 hw.nvidia.registry.SoftEDIDs: 1 hw.nvidia.registry.Mobile: 4294967295 hw.nvidia.registry.ResmanDebugLevel: 4294967295 hw.nvidia.registry.FlatPanelMode: 0 hw.nvidia.cards.0.model: GeForce4 Ti 4200 with AGP8X hw.nvidia.cards.0.irq: 16 hw.nvidia.cards.0.vbios: 04.28.20.05.00 hw.nvidia.cards.0.type: AGP Looks like you've got the NVidia AGP working, can I ask whether you compiled it with Linux support? Did you get it from the ports or as a package from NVidia? And I assume you have Xorg installed from the ports? The AGP feature has been an issue for several people, and it's been tricky nailing down the tipping point that will make it work for some and not others. I've got it working (very nicely with two monitors) and it's bugging me that another person with the same card and FreeBSD version can't get it working. Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :)
Re: nvidia driver problem
Louis LeBlanc wrote: (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/Speedo/. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/Speedo/). (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/CID/. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/CID/). These are worth fixing, though minor - the entries tell you how. corrected - thanks, i should have done that sooner. (--) NVIDIA(0): VideoRAM: 131072 kBytes (II) NVIDIA(0): Connected display device(s): CRT-1, DFP-0 (WW) NVIDIA(0): Multiple displays connected, but only one display allowed; (WW) NVIDIA(0): using first display (--) NVIDIA(0): Display device CRT-1: maximum pixel clock at 8 bpp: 350 MHz (--) NVIDIA(0): Display device CRT-1: maximum pixel clock at 16 bpp: 350 MHz (--) NVIDIA(0): Display device CRT-1: maximum pixel clock at 32 bpp: 350 MHz You have 2 monitors? If so, I recommend the TwinView config. It's tricky, but works well. no, i dont - i have a single samsung syncmaster 213t - but it has both analog and digital cables, as does the graphics cards. so i plugged them both in. winxp has no trouble switching between the two modes, and although i need to manually switch with freebsd - it still makes a reasonable difference. x is only visible on digital, while console looks terrible unless in analog. strange, but true. # Option NoLogo True # Option RenderAccel True You might want to uncomment RenderAccel - try it both ways once you get your color depth right. will try that. As mentioned by the other posters, put the default depth speck in your screen section. i hope this is the key - once the current bout of compiling is complete, i will exit x and try again. Looks like you've got the NVidia AGP working, can I ask whether you compiled it with Linux support? Did you get it from the ports or as a package from NVidia? yes, the agp does seem to be working fine. the nvidia package i downloaded direct from nvidia, and followed their instructions. was easy enough - except for the colour depth. i am not sure, however, if the nvidia driver was compiled with linux support. i did not do anything specific to make it so. i'm not sure if it helps, but my kernel is compiled with linux abi compatibility. and although the directory /compat/linux/usr/lib does exist, it is difficult to tell exactly which libraries nvidia are refering to in their documentation. i guess the tester will be running a gl app. i will test one of the screen savers when i switch over. And I assume you have Xorg installed from the ports? yes, installed from the ports. works like a dream. The AGP feature has been an issue for several people, and it's been tricky nailing down the tipping point that will make it work for some and not others. I've got it working (very nicely with two monitors) and it's bugging me that another person with the same card and FreeBSD version can't get it working. i'll help where i can - this is a very fresh install of 5.3, and onto an empty disk - so no upgrades or changes, just a straight install. and i can pretty much remember most of what i've done to get here - if it helps i can certainly note the steps. perhaps you could see something in the sequence? Lou thanks for your help, as well as jo and karel. -- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sk0 driver problem and (with luck) approach to a fix
On Sat, 8 Jan 2005, Chris Landauer wrote: Hi, ... Marvell Yukon 88E8050 PCI Express Gigabit Ethernet Adapter ... relevant output from pciconf -l -v: [EMAIL PROTECTED]:0:0: class=0x02 card=0x3032107b chip=0x436111ab rev=0x17 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' class= network subclass = ethernet relevant output from dmesg: skc0: Marvell Gigabit Ethernet port 0x2000-0x20ff mem 0xc810-0xc8103fff irq 17 at device 0.0 on pci3 skc0: unknown device! device_attach: skc0 attach returned 6 ... I have added following patch http://sources.zabbadoz.net/freebsd/patchset/EXPERIMENTAL/if_sk-marvell-88e8050-id.diff with the contents on what you already (should) have done/described. It's pretty much straight forward. Changing more logic (switch case,..) is not done because of other changes going on there atm. If the driver will work for your card with the above patch is unknown because nobody tested and noone I know has specs from Marvell. But you might be quite lucky with it. Please let me know the results of your tests and I will continue to handle this. -- Greetings Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sk0 driver problem and (with luck) approach to a fix
On Sun, 9 Jan 2005, Bjoern A. Zeeb wrote: On Sat, 8 Jan 2005, Chris Landauer wrote: ... Marvell Yukon 88E8050 PCI Express Gigabit Ethernet Adapter ... relevant output from pciconf -l -v: [EMAIL PROTECTED]:0:0: class=0x02 card=0x3032107b chip=0x436111ab rev=0x17 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' class= network subclass = ethernet relevant output from dmesg: skc0: Marvell Gigabit Ethernet port 0x2000-0x20ff mem 0xc810-0xc8103fff irq 17 at device 0.0 on pci3 skc0: unknown device! device_attach: skc0 attach returned 6 ... I have added following patch http://sources.zabbadoz.net/freebsd/patchset/EXPERIMENTAL/if_sk-marvell-88e8050-id.diff had been told that this will only make the phy 'work' but there are other problems. Someone else seems to work on it but I don't know anything more beyond that yet. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sk0 driver problem and (with luck) approach to a fix
hihi, all - i have a specific problem with a network interface, and i'm wondering what is the right venue for my question i have recently bought two new intel pentium 4 pcs (with hyperthreading, so that the SMP kernel works on them) and installed 5.3-RELEASE on them both, and the gigabit ethernet interfaces that came with the machines do not work (fast ethernet pci cards that i installed do work) - they both are: Marvell Yukon 88E8050 PCI Express Gigabit Ethernet Adapter (at least that is what i assume PCIe means) relevant output from pciconf -l -v: [EMAIL PROTECTED]:0:0: class=0x02 card=0x3032107b chip=0x436111ab rev=0x17 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' class= network subclass = ethernet relevant output from dmesg: skc0: Marvell Gigabit Ethernet port 0x2000-0x20ff mem 0xc810-0xc8103fff irq 17 at device 0.0 on pci3 skc0: unknown device! device_attach: skc0 attach returned 6 i snooped through some mailing lists about drivers (much thanx to zabbadoz) and read the code a few times and here is what i think is the problem: the chip ID (0x4361 above, the first half of chip=) is not in the array sk_devs[] (though two other, presumably older, Marvell IDs are, and my two belkin gigabit ethernet pci cards, with the same sk driver, have codes that are in the array and do both work) i tried just adding the appropriate entry to the array, but that didn't work (i think i know why now - see below) i was pleasantly surprised to see a timely message on freebsd-annnounce (Subject FreeBSD 5.3-RELEASE Errata Notice: FreeBSD-EN-05:02.sk) discussing a number of changes that were needed in the sk driver to fix other known problems, and eagerly looked at the new source code but the new ID is still not there i am in the process of upgrading from 5.3-RELEASE to 5.3-STABLE, which will take some time (this is the first time i've tried to use a -STABLE branch, though I've been using freebsd from CDs since 2.1.5-RELEASE), and then i will make the same array addition and try that - what else should i be trying (to make my results most useful to the community)? i now see (in lines 1537-1554 of file if_sk.c v.1.83.2.2) that i missed one other place to add the new id (which like many things is quite obvious in retrospect): the switch in which the driver compares what it gets from the device to the array entries (that is also where it prints the unknown device! shown above, when it doesn't find the one it is looking for) - so i will try that (an dlook for other instances of the #define'd ID codes) and see if it works - if so, where should i distribute the results? it seems that the switch could be changed into a loop through the defined array entries, rendering its code independent of the specific array contents (and making the array the ONLY place new IDs need to go, unless there is changed functionality) - what considerations made that impractical (was it just the amount of time a loop takes? or what else?)? more soon, cal Dr. Christopher Landauer Aerospace Integration Science Center The Aerospace Corporation, Mail Stop M6/214 P.O.Box 92957 Los Angeles, California 90009-2957, USA [EMAIL PROTECTED] +1 (310) 336-1361 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atheros (ath) wifi driver problem
On Thu, 2005-01-06 at 18:18 -0800, Mo Po wrote:
Hello,
I installed FreeBSD 5.3 today (coming from linux/debian).
I need to use the atheros wifi driver (man page ATH(4)), which is
included in 5.3. (I have an atheros based PCI card in an athlon xp based
system).
I get the following error when loading the module ('kldload if_ath'
command):
...
ath0: could not map interrupt
device_attach: ath0 attach returned 6
I've never tried to load this as a kernel module. It's probably better
to recompile the kernel with the right support. The ath driver also
requires ath_hal, which might be your problem.
You're obviously an old hand with un*x, but new to FreeBSD so in case it
helps:
#cd /usr/src/sys/i386/conf
#cp GENERIC MYKERNEL (or whatever name you want to use)
#vi MYKERNEL
add the lines:
device ath
device ath_hal
Make sure the following line is uncommented:
device wlan
#cd /usr/src
#make buildkernel KERNCONF=MYKERNEL (or whatever you called it)
#make installkernel KERNCONF=MYKERNEL
#reboot
This assumes you have the sources installed.
Peter.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
atheros (ath) wifi driver problem
Hello,
I installed FreeBSD 5.3 today (coming from linux/debian).
I need to use the atheros wifi driver (man page ATH(4)), which is
included in 5.3. (I have an atheros based PCI card in an athlon xp based
system).
I get the following error when loading the module ('kldload if_ath'
command):
...
ath0: could not map interrupt
device_attach: ath0 attach returned 6
After that ifconfig fails tp 'up' the ath0 i/f ('does not exists').
The ATH(4) lists this error but just says it should never happen ;-)
The same card/madwifi driver works under linux.
Any help appreciated a lot - otherwise my FreeBSD venture will be rather
short lived.
Thanks a lot!
--
Mo Po
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atheros (ath) wifi driver problem
Mo Po wrote:
Hello,
I installed FreeBSD 5.3 today (coming from linux/debian).
I need to use the atheros wifi driver (man page ATH(4)), which is
included in 5.3. (I have an atheros based PCI card in an athlon xp based
system).
I get the following error when loading the module ('kldload if_ath'
command):
...
ath0: could not map interrupt
device_attach: ath0 attach returned 6
After that ifconfig fails tp 'up' the ath0 i/f ('does not exists').
The ATH(4) lists this error but just says it should never happen ;-)
The same card/madwifi driver works under linux.
Any help appreciated a lot - otherwise my FreeBSD venture will be rather
short lived.
I think this problem or related has been noted before, but please submit
some more info of what you do - copy/paste the command/output if you can.
Try doing it all when the system is freshly booted, I wrote about some
memory problems about a month ago if I tried to insert/configure my ath
based card after starting memory heavy programs like mozilla. That
problem has been resolved in 6.0 but the code may not yet have been
merged into -STABLE.
Cheers, Erik
--
Ph: +34.666334818 web: www.locolomo.org
S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt
Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9
Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atheros (ath) wifi driver problem
On Thu, Jan 06, 2005 at 06:18:38PM -0800, Mo Po wrote:
Hello,
I installed FreeBSD 5.3 today (coming from linux/debian).
I need to use the atheros wifi driver (man page ATH(4)), which is
included in 5.3. (I have an atheros based PCI card in an athlon xp based
system).
I get the following error when loading the module ('kldload if_ath'
command):
...
ath0: could not map interrupt
device_attach: ath0 attach returned 6
After that ifconfig fails tp 'up' the ath0 i/f ('does not exists').
You may have already checked this, but be sure that Plug and Play OS
is NO in your BIOS. I've seen weird things happen w/PCI cards
when this BIOS setting is on. HTH
--
Regards,
Doug
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atheros (ath) wifi driver problem
Doug,
Thanks - I tried but did not help. The mobo is AN35N Ultra.
The exact error is:
kldload if_ath
ath0: Atheros 5212 mem 0xe700-0xe700 irq 7 at device 8.0 on pci1
ath0: could not map interrupt
device_attach: ath0 attach returned 6
I upgraded to something called RELENG_5 but it did not help (but now the
onboard NVIDIA ether driver does not build ;-)
I am running no GUI but command line only (yes I go back that long
ago:-)
On Thu, 2005-01-06 at 23:36 -0600, Doug Poland wrote:
On Thu, Jan 06, 2005 at 06:18:38PM -0800, Mo Po wrote:
Hello,
I installed FreeBSD 5.3 today (coming from linux/debian).
I need to use the atheros wifi driver (man page ATH(4)), which is
included in 5.3. (I have an atheros based PCI card in an athlon xp based
system).
I get the following error when loading the module ('kldload if_ath'
command):
...
ath0: could not map interrupt
device_attach: ath0 attach returned 6
After that ifconfig fails tp 'up' the ath0 i/f ('does not exists').
You may have already checked this, but be sure that Plug and Play OS
is NO in your BIOS. I've seen weird things happen w/PCI cards
when this BIOS setting is on. HTH
--
Mo Po [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia display driver problem
On Fri, Dec 31, 2004 at 03:42:24PM -0500, Louis LeBlanc wrote: This actually goes much better if you just install from the ports. That's what I'm using and other than the configuration hoops, it works perfectly. Have you verified that the GeForce4 is supported? My GeForce 440 MX runs great in Freebsd. To install the port just do: cd /usr/ports/x11/nvidia-driver make install Lou On 12/31/04 08:29 PM, Emon sat at the `puter and typed: Hello every one I am a nwebie and I am trying to install the nvidia driver for my (GeForce4 MX 440) display card. I running Freebsd 4.10 I have downloaded the driver from nvidia website but i am unable to install it, I am pasting the output after I tried to make install. *** Magic-Box# make install === src install -o root -g wheel -m 555 nvidia.ko /modules === lib find: /compat/linux/lib: No such file or directory find: /compat/linux/usr/lib: No such file or directory find: /compat/linux/usr/X11R6/lib: No such file or directory === lib/libGL === lib/libnvidia-tls === lib/libGLcore === lib/libXvMCNVIDIA === lib/compat === lib/compat/libGL install: /compat/linux/usr/lib: No such file or directory *** Error code 71 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113/lib/compat/libGL. *** Error code 1 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113/lib/compat. *** Error code 1 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113/lib. *** Error code 1 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113. Magic-Box# ** I hardly have any clue to what the above lines mean Any sugession or pointer will be welcome - Free POP3 Email from www.Gawab.com Sign up NOW and get your account @gawab.com!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org Statistics means never having to say you're certain. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
nvidia display driver problem
Hello every one I am a nwebie and I am trying to install the nvidia driver for my (GeForce4 MX 440) display card. I running Freebsd 4.10 I have downloaded the driver from nvidia website but i am unable to install it, I am pasting the output after I tried to make install. *** Magic-Box# make install === src install -o root -g wheel -m 555 nvidia.ko /modules === lib find: /compat/linux/lib: No such file or directory find: /compat/linux/usr/lib: No such file or directory find: /compat/linux/usr/X11R6/lib: No such file or directory === lib/libGL === lib/libnvidia-tls === lib/libGLcore === lib/libXvMCNVIDIA === lib/compat === lib/compat/libGL install: /compat/linux/usr/lib: No such file or directory *** Error code 71 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113/lib/compat/libGL. *** Error code 1 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113/lib/compat. *** Error code 1 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113/lib. *** Error code 1 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113. Magic-Box# ** I hardly have any clue to what the above lines mean Any sugession or pointer will be welcome - Free POP3 Email from www.Gawab.com Sign up NOW and get your account @gawab.com!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: nvidia display driver problem
You need to hav the linux comptibility layer instyalled before you try make install. Regards S. Indian Institute of Information Technology Subhro Sankha Kar Block AQ-13/1, Sector V Salt Lake City PIN 700091 India -Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Emon Sent: Saturday, January 01, 2005 1:59 To: freebsd-questions@freebsd.org Subject: nvidia display driver problem Hello every one I am a nwebie and I am trying to install the nvidia driver for my (GeForce4 MX 440) display card. I running Freebsd 4.10 I have downloaded the driver from nvidia website but i am unable to install it, I am pasting the output after I tried to make install. *** Magic-Box# make install === src install -o root -g wheel -m 555 nvidia.ko /modules === lib find: /compat/linux/lib: No such file or directory find: /compat/linux/usr/lib: No such file or directory find: /compat/linux/usr/X11R6/lib: No such file or directory === lib/libGL === lib/libnvidia-tls === lib/libGLcore === lib/libXvMCNVIDIA === lib/compat === lib/compat/libGL install: /compat/linux/usr/lib: No such file or directory *** Error code 71 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113/lib/compat/libGL. *** Error code 1 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113/lib/compat. *** Error code 1 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113/lib. *** Error code 1 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113. Magic-Box# ** I hardly have any clue to what the above lines mean Any sugession or pointer will be welcome - Free POP3 Email from www.Gawab.com Sign up NOW and get your account @gawab.com!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] smime.p7s Description: S/MIME cryptographic signature
Re: nvidia display driver problem
Hi, Make sure you have the linux compatibility on. If not, you can install the package with pkg_add -r linux_base, then, everything should be O.K. On Fri, 31 Dec 2004 20:29:03 GMT, Emon [EMAIL PROTECTED] wrote: Hello every one I am a nwebie and I am trying to install the nvidia driver for my (GeForce4 MX 440) display card. I running Freebsd 4.10 I have downloaded the driver from nvidia website but i am unable to install it, I am pasting the output after I tried to make install. *** Magic-Box# make install === src install -o root -g wheel -m 555 nvidia.ko /modules === lib find: /compat/linux/lib: No such file or directory find: /compat/linux/usr/lib: No such file or directory find: /compat/linux/usr/X11R6/lib: No such file or directory === lib/libGL === lib/libnvidia-tls === lib/libGLcore === lib/libXvMCNVIDIA === lib/compat === lib/compat/libGL install: /compat/linux/usr/lib: No such file or directory *** Error code 71 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113/lib/compat/libGL. *** Error code 1 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113/lib/compat. *** Error code 1 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113/lib. *** Error code 1 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113. Magic-Box# ** I hardly have any clue to what the above lines mean Any sugession or pointer will be welcome - Free POP3 Email from www.Gawab.com Sign up NOW and get your account @gawab.com!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia display driver problem
This actually goes much better if you just install from the ports. That's what I'm using and other than the configuration hoops, it works perfectly. Have you verified that the GeForce4 is supported? Lou On 12/31/04 08:29 PM, Emon sat at the `puter and typed: Hello every one I am a nwebie and I am trying to install the nvidia driver for my (GeForce4 MX 440) display card. I running Freebsd 4.10 I have downloaded the driver from nvidia website but i am unable to install it, I am pasting the output after I tried to make install. *** Magic-Box# make install === src install -o root -g wheel -m 555 nvidia.ko /modules === lib find: /compat/linux/lib: No such file or directory find: /compat/linux/usr/lib: No such file or directory find: /compat/linux/usr/X11R6/lib: No such file or directory === lib/libGL === lib/libnvidia-tls === lib/libGLcore === lib/libXvMCNVIDIA === lib/compat === lib/compat/libGL install: /compat/linux/usr/lib: No such file or directory *** Error code 71 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113/lib/compat/libGL. *** Error code 1 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113/lib/compat. *** Error code 1 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113/lib. *** Error code 1 Stop in /root/NVIDIA-FreeBSD-x86-1.0-6113. Magic-Box# ** I hardly have any clue to what the above lines mean Any sugession or pointer will be welcome - Free POP3 Email from www.Gawab.com Sign up NOW and get your account @gawab.com!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ Statistics means never having to say you're certain. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nVidia driver problem w/ FreeBSD 5.2.1-RELEASE + mplayer
On Thu, 27 May 2004, Senandung Mendonan wrote: On Thu, 27 May 2004, Gautham Ganapathy wrote: I have installed 5.2.1-RELEASE on my system (Athlon XP/nForce 2 Ultra/GeForce 3). Unfortunately, I am not able to use nVidia's fbsd drivers. I saw a few posts that mentioned it would work under fbsd-5 although it was written for 4. Any idea on what might be the problem? Did you install the driver via ports ( /usr/ports/x11/nvidia-driver ), or did you compile yourself? The ports version have some tweaks for you to try. I've been using the ports version (default install, no tweaking) in FreeBSD 5.2.1 on my Dell Latitude D800 (GeForce4 4200 Go), with no problems so far: ran mplayer occasionally with the some mpeg, avi, etc. Got one minor gripe though: Can't get the Twinview feature working -- how to get the display on both the laptop and a projector. (anybody got this one working?) Ok. I was building it from source. I'll try it from ports. Thanx. Not sure about Twinview, but I found the following http://lists.freebsd.org/pipermail/freebsd-questions/2003-June/010814.html There seems to be a few options that have to be setup for enabling Twinview and configuring the second monitor. Hope it works Regards Gautham ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
nVidia driver problem w/ FreeBSD 5.2.1-RELEASE + mplayer
Hi, I have installed 5.2.1-RELEASE on my system (Athlon XP/nForce 2 Ultra/GeForce 3). Unfortunately, I am not able to use nVidia's fbsd drivers. I saw a few posts that mentioned it would work under fbsd-5 although it was written for 4. Any idea on what might be the problem? The initial bootup gives messages saying 'PCI bus mastering disabled' and 'Unable to access memory ...'. Loading this driver also prevents it from detecting other PCI devices such as my Netgear FA311 and 3Com (integrated, 3c509, i think) NICs. Is there any workaround for this? I have not specified a chipset as mentioned in http://docs.freebsd.org/cgi/mid.cgi?B06CC0370BBC0F4EA588FD6952A9392502293A Also, when I install the mplayer package as well as apache 1.3, it halts with the error code -1. How do I get around this? I am installing them from the main FTP site. Thanks Regards Gautham ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nVidia driver problem w/ FreeBSD 5.2.1-RELEASE + mplayer
On Thu, 27 May 2004, Gautham Ganapathy wrote: I have installed 5.2.1-RELEASE on my system (Athlon XP/nForce 2 Ultra/GeForce 3). Unfortunately, I am not able to use nVidia's fbsd drivers. I saw a few posts that mentioned it would work under fbsd-5 although it was written for 4. Any idea on what might be the problem? Did you install the driver via ports ( /usr/ports/x11/nvidia-driver ), or did you compile yourself? The ports version have some tweaks for you to try. I've been using the ports version (default install, no tweaking) in FreeBSD 5.2.1 on my Dell Latitude D800 (GeForce4 4200 Go), with no problems so far: ran mplayer occasionally with the some mpeg, avi, etc. Got one minor gripe though: Can't get the Twinview feature working -- how to get the display on both the laptop and a projector. (anybody got this one working?) Thanks. --mendonan Yang mimpikan secangkir kopi panas dengan selimut.. (Dreaming of a cup of hot coffee, and a blanket..) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ep driver problem in 5.2?
Today I installed FBSD 5.2 on my main notebook because I want to make the switch from 4.7. I have a 3Com Megahertz 10/100 LAN PC Card Model 3CCFE574BT. ep0: 3Com Megahertz 574B at port 0x100-0x11f irq 11 function 0 config 1 on pccard0 Unknown ID: 0x201 ep0: Ethernet address 00:50:da:d3:6b:22 The default kernel is being used, no changes made. This card was working flawlessly all the time with FBSD 4.5/4.7, did autonegotiation perfectly, no problem at all, not even plugging the cable out on my 100 Mb switch and plugging it in on a 10 Mb hub or vice versa. With 5.2, however, the card works fine right right after ifconfig ep0 up, but: - it stops working if there has not been any traffic through the card for a while (have not yet been able to determine the exact time) - if there is traffic through the card all the time (eg pinging another host continuously) it does not stop working - broadcasts, arp requests and other packets going to all nodes on the network seem to do the trick as well as a constant ping - the autonegotiating switch, to which it is connected, still shows the card is there and in 100 MB full duplex mode - ifconfig ep0 down followed by ifconfig ep0 up brings the card back to life again - if connecting the card to a 10 MB hub, there are no problems, it continues to work properly, even if there is no traffic through it for some time Unfortunately the ep driver does not support setting the media, otherwise it might be possible to work around the problem. At the moment I'm at a loss, not knowing how to get this to work. Writing a startup script which does not return and pings another host on the network all the time is not quite the solution I'd be happy to implement... Kurt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NVIDIA Driver problem solved, but now cannot mount MSDOSFS?
To the people who made the suggestion that solved my problem, I offer my gratitude and thanks. My goal is to be able to play Neverwinter Nights on FreeBSD, so I don't need Linux or Windows anymore. That problem has been solved. Now I have attempted to mount my Windows partition, FAT32, so I could copy across the game files, and I get this message when I boot: mount: exec mount_msdosfs not found in /sbin, /usr/sbin: no such file or directory. Then it drops me to sh, where I must 'edit /etc/fstab' and comment that line out to boot. Here is my fstab: # See the fstab(5) manual page for important information on automatic mounts # of network filesystems before modifying this file. # # DeviceMountpoint FStype Options DumpPass# /dev/ad2s1b noneswap sw 0 0 /dev/ad2s1a / ufs rw 1 1 /dev/ad2s1f /tmpufs rw 2 2 /dev/ad2s1g /usrufs rw 2 2 /dev/ad2s1e /varufs rw 2 2 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 /dev/acd1c /cdrom1 cd9660 ro,noauto 0 0 proc/proc procfs rw 0 0 #/dev/ad0s1 /mnt/windowsmsdosfs rw 0 0 The only thing I can think of is that somehow something went wrong when I built world from 4.7 to 4.8. Just to clear up this possible suggestion, Windows 2000 is installed on the first partition of the first hard disk. /dev/ad0s1 worked before I CVSUPped and built world. Once again... thank you all for your help. I hope I have not forgotten any information to include in my tiredness. Shannon __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NVIDIA Driver problem solved, but now cannot mount MSDOSFS?
On Wed, Jul 30, 2003 at 02:52:09PM -0700 or thereabouts, RexFelis wrote: To the people who made the suggestion that solved my problem, I offer my gratitude and thanks. My goal is to be able to play Neverwinter Nights on FreeBSD, so I don't need Linux or Windows anymore. That problem has been solved. Now I have attempted to mount my Windows partition, FAT32, so I could copy across the game files, and I get this message when I boot: mount: exec mount_msdosfs not found in /sbin, /usr/sbin: no such file or directory. [ ... ] Just to clear up this possible suggestion, Windows 2000 is installed on the first partition of the first hard disk. /dev/ad0s1 worked before I CVSUPped and built world. Once again... thank you all for your help. I hope I have not forgotten any information to include in my tiredness. Try replacing `msdosfs' with just `msdos' and uncomment the line. Reboot or `mount -a'. -- Josh Shannon __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NVIDIA Driver problem solved, but now cannot mount MSDOSFS?
I can't believe I misread that and made such a silly mistake. Thanks, Josh. I appreciate your help. You just saved me a weeks worth of time downloading the game. :) Shannon __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
pst driver problem?
Everything seemed to be working properly with my promise sx6000 card. It has 6 120GB drives attached in raid 0+1 configuration. While running an rsync to the machine, I get the following rsync error in rsyncd.log: 2003/03/20 04:15:52 [987] rsync: error writing 71 unbuffered bytes - exiting: Broken pipe 2003/03/20 04:15:52 [987] rsync error: error in rsync protocol data stream (code 12) at io.c(463) I also get these in /var/log/messages: /kernel: pst: timeout mfa=0x003286f0 cmd=WRITE This box is running 4.7 Chris McGee 301-682-9972 Xecunet, LLCwww.xecu.net Dialup * Webhosting * E-Commerce * High-Speed Access To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
