Re: Error in kernel source, possibly GCC related
driver, resembling an SCO console > device sc > > # Enable this for the pcvt (VT220 compatible) console driver > #device vt > #options XSERVER # support for X server on a vt console > #options FAT_CURSOR # start with block cursor > > device agp # support several AGP chipsets > > # Floating point support - do not disable. > device npx > > # Power management support (see NOTES for more options) > #device apm > # Add suspend/resume support for the i8254. > device pmtimer > > # PCCARD (PCMCIA) support > # PCMCIA and cardbus bridge support > > # Serial (COM) ports > > # Parallel port > # If you've got a "dumb" serial or parallel PCI card that is > # supported by the puc(4) glue driver, uncomment the following > # line to enable it (connects to the sio and/or ppc drivers): > #device puc > > # PCI Ethernet NICs. > # PCI Ethernet NICs that use the common MII bus controller code. > # NOTE: Be sure to keep the 'device miibus' line in order to use these > NICs! > device miibus # MII bus support > device rl # RealTek 8129/8139 > device sis # Silicon Integrated Systems SiS 900/SiS 7016 > device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') > > # ISA Ethernet NICs. pccard NICs included. > > # ISA devices that use the old ISA shims > #device le > > # Wireless NIC cards > > # Pseudo devices. > device loop # Network loopback > device mem # Memory and kernel memory devices > device io # I/O device > device random # Entropy device > device ether # Ethernet support > #device sl # Kernel SLIP > #device ppp # Kernel PPP > device tun # Packet tunnel. > device pty # Pseudo-ttys (telnet etc) > device md # Memory "disks" > device gif # IPv6 and IPv4 tunneling > #device faith # IPv6-to-IPv4 relaying (translation) > > # The `bpf' device enables the Berkeley Packet Filter. > # Be aware of the administrative consequences of enabling this! > # Note that 'bpf' is required for DHCP. > device bpf # Berkeley packet filter > > # USB support > device uhci # UHCI PCI->USB interface > device ohci # OHCI PCI->USB interface > device ehci # EHCI PCI->USB interface (USB 2.0) > device usb # USB Bus (required) > #device udbp # USB Double Bulk Pipe devices > device ugen # Generic > device uhid # "Human Interface Devices" > device umass # Disks/Mass storage - Requires scbus and da > # USB Ethernet, requires mii > > # FireWire support > device firewire # FireWire bus code > > device sound > device "snd_cmi" > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Phil Bowens He who is the greatest of warriors overcomes and subdues himself. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ndis no longer detects netgear wg311v2
FWIW, I am having the *exact* same problem starting today. I hadn't updated my STABLE machine since April. NDIS was working fine (save a frew crashes) before I updated last night.. and now NDIS will not even talk about the card. There is also a slight freeze on the machine after the if_ndis module is loaded. I will do some more investigating, but now there's at least two of us. Did you ever find a fix? On 6/19/05, Evan Dower <[EMAIL PROTECTED]> wrote: > I recently moved, and for some reason my computer started crashing > when I tried to make it associate with my new wireless network. (It > worked fine on the old wireless network.) I figured the first thing I > should do to fix the problem is update my sources, since it may have > already been fixed. Unfortunately the updated sources don't recognize > my wireless card at all. > > Before the update (hand-transcribed): > # uname -a > FreeBSD lojak.washington.edu 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #0: > Sat Apr 2 11:50:53 PST 2005 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM i386 > # kldload FwRad16.bin.ko > # kldload ndis > # kldload if_ndis > ndis0: mem > 0xfb02-0xfb03,0xfb04-0xfb041fff irq 16 at device 4.0 on pci2 > ndis0: NDIS API version: 5.1 > ndis0: Ethernet address: 00:09:5b:ba:da:ef > ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > # ifconfig ndis0 > ndis0: flags=8802 mtu 1500 > ether 00:09:5b:da:ef > media: IEEE 802.11 Wireless Ethernet autoselect > status: no carrier > ssid "" > channel -1 authmode OPEN powersavemode OFF powersavesleep 100 > rtsthreshold 2312 protmode CTS > wepmode OFF weptxkey 1 > # wicontrol ndis0 -l > 0 stations: > # ifconfig ndis0 ssid "The Penthouse" channel 11 up > ndis0: link up > # dhclient ndis0 > ndis0: link up > <<< I can't see the whole panic screen, but here's the bottom: >>> > panic: page fault > cpuid = 0 > boot() called on cpu#0 > Uptime: 11m20s > Dumping 1023 MB > > > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 01 > fault virtual address= 0x0 > fault code = supervisor read, page not present > intruction pointer = 0x8:0x0 > stack pointer= 0x10:0xe4e1fcec > frame pointer= 0x10:0xe4e1fd0c > code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 5 (thread taskq) > trap number = 12 > > > I can work on getting the crash dump if that's useful, but the > behavior seems to have changed in the last couple of months. Now I > get: > # uname -a > FreeBSD lojak.washington.edu 5.4-STABLE FreeBSD 5.4-STABLE #0: Sat Jun > 14:20:40 PDT 2005 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM i386 > # kldload FwRad16.bin.ko > # kldload ndis > warning: KLD '/boot/kernel/if_ndis.ko' is newer than the linker.hints > file > # kldload if_ndis > kldload: can't load if_ndis: File exists > # kldstat > Id Refs AddressSize Name > 1 10 0xc040 4a42f0 kernel > 2 14 0xc08a5000 56270acpi.ko > 31 0xc2e83000 14000FwRad16.bin.ko > 41 0xc2e97000 9000 if_ndis.ko > 51 0xc2ea 12000ndis.ko > 61 0xc2ec5000 b000 pccard.ko > # ifconfig ndis0 > ifconfig: interface ndis0 does not exist > # kldunload if_ndis > # kldload if_ndis > # ifconfig ndis0 > ifconfig: interface ndis0 does not exist > > > I haven't seen anything in UPDATING that accounts for this. Does > anyone have any idea of where to look for clues? > > Thanks very much, > -- > Evan Dower > Software Development Engineer > Amazon.com, Inc. > Public key: http://students.washington.edu/evantd/pgp-pub-key.txt > Key fingerprint = D321 FA24 4BDA F82D 53A9 5B27 7D15 5A4F 033F 887D > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Phil Bowens He who is the greatest of warriors overcomes and subdues himself. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: building good custom kernel
Consult the tuning(7) manual page. On 4/21/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > hi , > i tried building the freebsd 5.3 kernel and it works > fine, but can u people give me some tips regarding > optimizing kernel during build, even saving a single > cpu cycle would mean a lot. i would like to have a > kernel that is really optimized. And what do you > people do to fine tune the kernel? > > thanks, > ananth.g > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Phil Bowens He who is the greatest of warriors overcomes and subdues himself. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [HEADS UP] perl symlinks in /usr/bin will be gone
I think the color should be green. On Sat, 29 Jan 2005 21:24:25 +0100, Anton Berezin <[EMAIL PROTECTED]> wrote: > Unless I hear too many cries "don't do that" (with justification), I > plan to not create any perl symlinks in /usr/bin in the forthcoming > upgrade of both lang/perl5.8 (to 5.8.6) and lang/perl5 (to 5.6.2). This > will ONLY be true for FreeBSD 5.X and FreeBSD CURRENT; the existing > pollution of /usr/bin will still be performed for older versions of > FreeBSD, if requested via use.perl script. > > In practical terms this will mean a one-time sweep of your scripts in > order to convert them, in a typical case, from #! /usr/bin/perl to > #! /usr/local/bin/perl. > > CORRECT perl-dependant ports should not be affected. > > In order to keep pkg-install simple, no old symlink chasing and removal > will be done, although the detailed instructions will be posted in > ports/UPDATING and in pkg-message for the ports. > > Please respect Reply-To. > Thank you, > > \Anton. > -- > The moronity of the universe is a monotonically increasing function. -- > Jarkko Hietaniemi > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Phil Bowens He who is the greatest of warriors overcomes and subdues himself. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Where to get 5.3 Stable
You'll need to get the FreeBSD sources via CVSup or some other means and build 5.3-STABLE. Make sure and use the tag RELENG_5 (as of right now) when fetching via CVSup or anoncvs. You may also want to check ftp://current.freebsd.org/pub/FreeBSD/ See: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html As far as your errors are concerned, I am no expert at the internal workings of the ad driver.. so I'm not going to even try and venture to explain whats going on. However, I am sure that someone here who is more knowledgable may be able to offer an explanation and/or fix if you are able to provide more information (ie how often it occurs, your disk drive make, etc etc). [EMAIL PROTECTED] wrote: Everyone keep on saying they have problem running 5.3 stable. But is 5.3 stable really out? I can't find it anywhere. Only 5.3 I got is the RC1 version, but it always give me the ad0 Warning: DMA_READ and DMA_WRITE INTERRUPT ... message, so I installed 5.2.1 instead. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
