RE: New Freebsd Install Guide Available
Many people who are involved in FreeBSD are not programmers. The Project includes documentation writers, Web designers, and support people. All that these people need to contribute is an investment of time and a willingness to learn. 1. Read through the FAQ and Handbook periodically. If anything is badly explained, out of date or even just completely wrong, let us know. Even better, send us a fix (SGML is not difficult to learn, but there is no objection to ASCII submissions). http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/index.html -- I think this is great, but there should be a project leader to regulate overall structure of the Handbook and other documents as that is perhaps where the greatest amount of work is needed. Could we at least have a mailing list for writers? Date: Mon, 4 Apr 2005 01:03:24 -0400 From: [EMAIL PROTECTED] Subject: RE: New Freebsd Install Guide Available To: Chris Hill [EMAIL PROTECTED] Cc: Randy Pratt [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii As stated in the content displayed by those URL's the Install guide is free to anyone to download and very plainly states the content is contributed to public domain. So why are so many people asking the same question when the answer is so self evident? And this writer takes offence to anybody calling the promoting of this Install guide as verbally trashing the handbook. I don't need to do that. Many others have done that over the years. Any regular reader of the list will know that the handbook content has had many people voicing concern over its less than basic ability to convey meaningful instructions. No need to open that flame war again. The bottom line is the firewall section of this Install guide has been lifted and used to replace the FreeBSD official handbook's complete firewall section all ready. Any body can lift any part of the install guide and put forth their own effort to use it as source to replace other sections of the official handbook. There is nothing stopping you so go for it. This Install guide has a much more meaningful index which is right there all the time helping the reader to navigate the guides different subjects. The presentation method of the index and content on split screen is more in line with modern web content that every ones sees these days. Plus the install Guide progresses in an step by step manner from installing the base default system all the way up to configurating a private LAN which can masquerade as a commercial user. This address the desired server configuration most often wanted by the majority the first time posters to this questions list. Another important niche this FreeBSD Install Guide covers is that it is downloadable direct to ms/window boxes and can be viewed using the ms/explorer browser. You UNIX purists have to accept the fact that there are many ms/win users who want to be FreeBSD users and dual win/FreeBSD users out there and this Install guide opens up a bridge to the FreeBSD operating system to service this untapped potential user group. Just watch the posts on the list for the magnitude of ms/office top posters to bear out that truth. The official handbook in its current format does not address this. Since its 3/1//05 public domain release this install guide has been visited 1500 times and downloaded 216 times. This was mostly from people who responded from the UNIX news groups postings. The best thing for the FreeBSD doc group to do is request to be an official mirror of the Install guide. Hay the Doc group will have the best win win situation here. They get an alternate view of the install process that is maintained outside of the FreeBSD project. Much like the pf firewall has its own self maintained user guide. Now this is something to think about. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NDIS installation problem with WMP54G v4 wireless card
Thank you for the excellent advice. I converted the .INF file to ASCII from UTF-8 (no error was given), re-ndiscvt'd and it works. Very happy now! From: Fabian Keil [EMAIL PROTECTED] To: Texas Consultant [EMAIL PROTECTED] CC: freebsd-questions@freebsd.org Subject: Re: NDIS installation problem with WMP54G v4 wireless card Date: Fri, 25 Mar 2005 17:18:48 +0100 Texas Consultant [EMAIL PROTECTED] wrote: Just put together a new BSD 5.3 machine, and compiled NDIS for use with a Linksys WMP54g v4 card; it's a wireless card that uses the Ralink RT2500 chipset. Everything works so far; major steps are: 1. make ndis 2. copy over NDIS driver files 3. make if_ndis 4. kldload ndis However, kldload if_ndis returns an error: /sbin/kldload -v /usr/src/sys/modules/if_ndis/if_ndis.ko kldload: can't load link_elf: symbol rt2500_sys_drv_data_start undefined /usr/src/sys/modules/if_ndis/if_ndis.ko: No such file or directory *** Error code 1 Stop in /usr/src/sys/modules/if_ndis. I had a similar problem after updating from 5.3 to 5.4-PRERELEASE. I rebuilded if_ndis, but forgot to first recreate ndis_driver_data.h. After rebuilding ndis_driver_data.h with the right sources it worked again. Could your sources by out of sync with the system? Fabian -- http://www.fabiankeil.de ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NDIS installation problem with WMP54G v4 wireless card
Just put together a new BSD 5.3 machine, and compiled NDIS for use with a Linksys WMP54g v4 card; it's a wireless card that uses the Ralink RT2500 chipset. Everything works so far; major steps are: 1. make ndis 2. copy over NDIS driver files 3. make if_ndis 4. kldload ndis However, kldload if_ndis returns an error: /sbin/kldload -v /usr/src/sys/modules/if_ndis/if_ndis.ko kldload: can't load link_elf: symbol rt2500_sys_drv_data_start undefined /usr/src/sys/modules/if_ndis/if_ndis.ko: No such file or directory *** Error code 1 Stop in /usr/src/sys/modules/if_ndis. DMESG follows: Copyright (c) 1992-2004 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 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2405.46-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf33 Stepping = 3 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE real memory = 268369920 (255 MB) avail memory = 252960768 (241 MB) ACPI APIC Table: IntelR AWRDACPI ioapic0 Version 2.0 irqs 0-23 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: IntelR AWRDACPI on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 acpi_tz0: Thermal Zone on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82875P host to AGP bridge mem 0xf000-0xf7ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0xbc00-0xbc1f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0xb000-0xb01f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: Intel 82801EB (ICH5) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0xb400-0xb41f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: Intel 82801EB (ICH5) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: Intel 82801EB (ICH5) USB controller USB-D port 0xb800-0xb81f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: Intel 82801EB (ICH5) USB controller USB-D on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: serial bus, USB at device 29.7 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 fwohci0: Texas Instruments TSB43AB23 mem 0xfb00-0xfb003fff,0xfb006000-0xfb0067ff irq 18 at device 2.0 on pci2 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:50:8d:00:00:5e:04:ce fwohci0: Phy 1394a available S400, 3 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:50:8d:5e:04:ce fwe0: Ethernet address: 02:50:8d:5e:04:ce 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 firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) dc0: ADMtek AN985 10/100BaseTX port 0xa000-0xa0ff mem 0xfb007000-0xfb0073ff irq 21 at device 5.0 on pci2 miibus0: MII bus on dc0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:04:5a:68:c1:82 dc0: if_start running deferred for Giant dc0: [GIANT-LOCKED] pci2: network at device 9.0 (no driver attached) isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH5 UDMA100 controller port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 atapci1: Intel ICH5 SATA150 controller port 0xd000-0xd00f,0xcc00-0xcc03,0xc800-0xc807,0xc400-0xc403,0xc000-0xc007 irq 18 at device 31.2 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 pci0: serial bus, SMBus at device 31.3 (no driver attached) pci0:
