Re: 2. Try Kernel compiling..makefile stops because of some warnings
On Saturday 26 June 2004 02:19, Bill Moran wrote: Karim Forsthofer [EMAIL PROTECTED] wrote: Hello I tried to compile a new kernel from my 5.1 bsd cd. 5.1 is an obsolete, experimental version. If you're new to FreeBSD, you should be using 4.10. If you want to experiment with the 5.x branch, you should be using 5.2.1. Many problems that existed in 5.1 have been fixed in 5.2.1. You're unlikely to get any support for 5.1. That's true. But it supported building my kernels. 5.1 was not unstable or broken. It was less broken than 5.2-REL. Building kernel from cd src should always be supported. This is probably user error. Config and make depend worked well, but make stops and print out some warnings about unused functions in npx.c (or something else). This is the old way of building a kernel. You should use make buildkernel as described in the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html No. If you have a release from CD with src-sys installed and haven't cvsup'ed anything or don't have src-all fully installed than this *is* the proper way to build a kernel. In fact, it's the only way. There is no such thing as an old or a new way. These have IMHO unfortunately become the de facto terms but they're not accurate. On my -CURRENT box, when not updating world but merely rebuilding kernel, I normally use the old way because it's more straightforward then, starting from editing the conf file. Using make kernel would in that case produce the same of course. For future reference, it's very difficult to help when problems are described as print out some warnings about unused functions in npx.c (or something else). If you have questions in the future, you'll get more helpful answers if you provide the exact error messages. This document describes how to ask good questions: http://www.lemis.com/questions.html Yes. Without the actual output all we can do is guess. I searched in the newsgroup and found some similar postings to this subject It seems to me, that the problem appears when the RealTek pci NIC device is included in the config file. Someone wrote in the newsgroup, that gcc works with the wrong compiler flags, that means that the compiler stops at warnings, but he didn`t mention how the solve this problem or how to change the flags. Any suggestions? With the output we might be able to see if its a warning or an error. My Hardware is a d-link nic and the ensoniq 1370 soundcard, the other stuff is very common. The MYKERNEL configfile is attached to this email. I don't see anything wrong with it. How about if you load GENERIC and then kldload your NIC and 137x drivers, does everything work then? It's worth while to note that FreeBSD 5.x generally much more encourages the use of modules rather than compiling in drivers. Hope you can help me. Reinstalling to 5.2.1 is a good idea anyhow in the longer run. Greetings Karim Cheers, Dan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
can not make ltmdm ports
hi sirs, my laptop is dell inspiron 1100 with Conexant D480 MDC modem controller. i tried to compile ltmdm from ports but strange enough, it failed. i spent about 2 months in looking or searching from internet if there were any one else can use that modem in that machin with freebsd. finally, i have to come back to my box and decide to make from ports. as mentioned above, make failed. can any one please helps me or explains me why do make failed ? other informations about dell inspiron 1100 are attached. thanks in advanced fro any helps and hints. -- with best regards, psr http://www.thai-aec.org http://www.thai.net/makham From [EMAIL PROTECTED] Sat Jun 26 08:13:35 2004 Return-Path: [EMAIL PROTECTED] Received: from inspiron.thai-aec.org (inspiron.thai-aec.org [192.168.1.70]) by firak.thai-aec.org (8.12.11/8.12.11) with ESMTP id i5Q1DZmA022143 for [EMAIL PROTECTED]; Sat, 26 Jun 2004 08:13:35 +0700 (ICT) (envelope-from [EMAIL PROTECTED]) Received: from inspiron.thai-aec.org (localhost [127.0.0.1]) by inspiron.thai-aec.org (8.12.11/8.12.11) with ESMTP id i5Q17ZHP001148 for [EMAIL PROTECTED]; Sat, 26 Jun 2004 08:07:35 +0700 (ICT) (envelope-from [EMAIL PROTECTED]) Received: (from [EMAIL PROTECTED]) by inspiron.thai-aec.org (8.12.11/8.12.11/Submit) id i5Q17Y9b001147 for [EMAIL PROTECTED]; Sat, 26 Jun 2004 08:07:34 +0700 (ICT) (envelope-from root) Date: Sat, 26 Jun 2004 08:07:34 +0700 (ICT) From: Charlie Root [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Status: RO Content-Length: 2910 Lines: 64 [EMAIL PROTECTED]:0:0: class=0x06 card=0x chip=0x25608086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82845G/GL/GV/GE/PE DRAM Controller / Host-Hub I/F Bridge' class= bridge subclass = HOST-PCI [EMAIL PROTECTED]:2:0: class=0x03 card=0x01491028 chip=0x25628086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82845G/GL/GV/GE/PE Integrated Graphics Device' class= display subclass = VGA [EMAIL PROTECTED]:29:0: class=0x0c0300 card=0x24c08086 chip=0x24c28086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBM (ICH4/M) USB UHCI Controller #1' class= serial bus subclass = USB [EMAIL PROTECTED]:29:1: class=0x0c0300 card=0x24c08086 chip=0x24c48086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBM (ICH4/M) USB UHCI Controller #2' class= serial bus subclass = USB [EMAIL PROTECTED]:29:2: class=0x0c0300 card=0x24c08086 chip=0x24c78086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBM (ICH4/M) USB UHCI Controller #3' class= serial bus subclass = USB [EMAIL PROTECTED]:29:7: class=0x0c0320 card=0x24c08086 chip=0x24cd8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBM (ICH4/M) USB EHCI Controller' class= serial bus subclass = USB [EMAIL PROTECTED]:30:0: class=0x060400 card=0x chip=0x244e8086 rev=0x82 hdr=0x01 vendor = 'Intel Corporation' device = '82801BA/CA/DB/EB/ER (ICH2/3/4/5/5R) Hub Interface to PCI Bridge' class= bridge subclass = PCI-PCI [EMAIL PROTECTED]:31:0: class=0x060100 card=0x chip=0x24c08086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB (ICH4) LPC Interface Bridge' class= bridge subclass = PCI-ISA [EMAIL PROTECTED]:31:1: class=0x01018a card=0x24c08086 chip=0x24cb8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB (ICH4) UltraATA/100 EIDE Controller' class= mass storage subclass = ATA [EMAIL PROTECTED]:31:5: class=0x040100 card=0x01491028 chip=0x24c58086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBM (ICH4/M) AC'97 Audio Controller' class= multimedia subclass = audio [EMAIL PROTECTED]:31:6: class=0x070300 card=0x542214f1 chip=0x24c68086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBM (ICH4/M) AC'97 Modem Controller' class= simple comms [EMAIL PROTECTED]:1:0: class=0x02 card=0x10284401 chip=0x440114e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM440x 10/100 Integrated Ethernet Controller' class= network subclass = ethernet [EMAIL PROTECTED]:4:0: class=0x060700 card=0x01491028 chip=0xac56104c rev=0x00 hdr=0x02 vendor = 'Texas Instruments (TI)' device = 'PCI1510 PC card CardBus Controller' class= bridge subclass = PCI-CardBus From [EMAIL PROTECTED] Sat Jun 26 08:17:43 2004 Return-Path: [EMAIL PROTECTED] Received: from inspiron.thai-aec.org (inspiron.thai-aec.org [192.168.1.70]) by firak.thai-aec.org (8.12.11/8.12.11) with ESMTP id i5Q1HhTK022167 for [EMAIL PROTECTED]; Sat, 26 Jun 2004 08:17:43 +0700 (ICT) (envelope-from [EMAIL PROTECTED]) Received:
fsck'ing a Vinum RAID5 volume (and a stale drive)
This is a good one. $ uname -a FreeBSD 4.7-RELEASE FreeBSD 4.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 First I'll explain the stale/degraded issue. Then ask about fsck on a raid5 vinum. My goal is to have the vinum volume check out OK with fsck and to do a 'vinum list' and have 'State: up' all the way down the list. This is a RAID5 holding backup copies of other servers. $ vinum list 7 drives: D a State: up Device /dev/ad4s1f Avail: 0/114473 MB (0%) D b State: up Device /dev/ad6s1f Avail: 0/114473 MB (0%) D c State: up Device /dev/ad8s1f Avail: 0/114473 MB (0%) D d State: up Device /dev/ad10s1f Avail: 0/114473 MB (0%) D e State: up Device /dev/ad12s1f Avail: 0/114473 MB (0%) D f State: up Device /dev/ad14s1f Avail: 0/114473 MB (0%) D g State: up Device /dev/ad16s1f Avail: 0/114473 MB (0%) 1 volumes: V backupState: up Plexes: 1 Size:670 GB 1 plexes: P backup.p0 R5 State: degraded Subdisks: 7 Size: 670 GB 7 subdisks: S backup.p0.s0 State: up PO:0 B Size:111 GB S backup.p0.s1 State: up PO: 384 kB Size:111 GB S backup.p0.s2 State: up PO: 768 kB Size:111 GB S backup.p0.s3 State: stale PO: 1152 kB Size:111 GB S backup.p0.s4 State: up PO: 1536 kB Size:111 GB S backup.p0.s5 State: up PO: 1920 kB Size:111 GB S backup.p0.s6 State: up PO: 2304 kB Size:111 GB I've found on the net that I can switch the state by doing: $ vinum setstate up backup.p0 backup.p0.s3 and it does indeed bring the state back up so then it was recommneded to $ vinum saveconfig I rebooted, the state is up so I unmounted the volume to fsck it. Is this approach correct? does this do anything productive or just forces the state label to change and do nothing to the drives? I don't feel confident that it did anything and Im having a VERY hard time finding documentation on this. the vinum vol is unmounted, so now I do a : $ fsck -n /dev/vinum/backup and get tons of bad news scrolling up the screen. Lots of this: %--- bigbang:root fsck -n /dev/vinum/backup ** /dev/vinum/backup (NO WRITE) ** Last Mounted on /backup ** Phase 1 - Check Blocks and Sizes 529516494 BAD I=12 31580655 BAD I=12 -588350257 BAD I=12 1849227449 BAD I=12 490256604 BAD I=12 1896046100 BAD I=12 1065221887 BAD I=12 422657855 BAD I=12 156800 BAD I=12 1663396533 BAD I=12 -13685115 BAD I=12 EXCESSIVE BAD BLKS I=12 CONTINUE? yes INCORRECT BLOCK COUNT I=12 (80557504 should be 262656) CORRECT? no INCORRECT BLOCK COUNT I=76903513 (416 should be 228) CORRECT? no PARTIALLY TRUNCATED INODE I=76903514 SALVAGE? no PARTIALLY TRUNCATED INODE I=76903515 SALVAGE? no -116589821 BAD I=76903515 -112723056 BAD I=76903515 -98501815 BAD I=76903515 -99813036 BAD I=76903515 -131467519 BAD I=76903515 -168168055 BAD I=76903515 -189794987 BAD I=76903515 -189532554 BAD I=76903515 -169084920 BAD I=76903515 -143787653 BAD I=76903515 -122160433 BAD I=76903515 EXCESSIVE BAD BLKS I=76903515 CONTINUE? yes INCORRECT BLOCK COUNT I=76903515 (1056 should be 368) CORRECT? no PARTIALLY TRUNCATED INODE I=76903516 SALVAGE? no %--- Im assuming I'll want to answer yes to at least some of those. Can I say yes to all of them? What errors should I say no to? I have no idea whats bad bad and whats correctable. Now. because this is a raid5 volume, are some of these fsck prompts false positives? ie; fsck is giving a error but really it's fine as it's raid5? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: command-line calculator?
On Fri, Jun 25, 2004 at 01:31:33PM -0600, Warren Block probably wrote: On Fri, 25 Jun 2004, Parv wrote: Perl: perl -e 'print +(17 * 36)' Or just perl -e 'print 17 * 36' but for neatness perl -e 'print 17 * 36, \n' Or just $ sh -c 'echo $((17*36))' 612 or $ echo $((17*36)) if you use sh as your interactive shell. -- DoubleF The first time, it's a KLUDGE! The second, a trick. Later, it's a well-established technique! -- Mike Broido, Intermetrics pgp0FFui5t4Nb.pgp Description: PGP signature
Re: BSD ?
On Saturday 26 June 2004 04:56, James W. Thompson, II wrote: On Fri, 25 Jun 2004 12:18:57 -0700, Gill Elmgren [EMAIL PROTECTED] wrote: I have a Kayak XU800 dual processor computer and I'm confused as to which version of FreeBSD I sould download for installation on this machine. Thanks ... Somebody else can tell me if I'm wrong, but I believe that you would just use the x86 version from what I have googled it looks like it is a Pentium class machine so the x86 version should do the trick. If the OP means which Release, then, as the he seems to be new to Freebsd, I would suggest a production version 4.9 or 4.10 rather then the developmental relaeases 5.x. Malcolm ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: fsck'ing a Vinum RAID5 volume (and a stale drive)
Benjamin P. Keating wrote: I've found on the net that I can switch the state by doing: $ vinum setstate up backup.p0 backup.p0.s3 Ouch, this is a bad move. You just told vinum to start using the stale (=out of date data) disc as if it was up to date and nothing was wrong with it. Basically you have trashed your data, possibly beyond repair. Why was the disc in a stale state? If it developed bad blocks that could not be remapped, then vinum marked it as stale and continued to use the other discs in degraded mode (just as it should). Even if the disc did not break (maybe just connection problems or something), once vinum marked it as stale any further writing to the array would immediately invalidate the data on the disc; which means the only way to bring it back up would be to go throug a proper rebuild of the data. I rebooted, the state is up so I unmounted the volume to fsck it. Is this approach correct? does this do anything productive or just forces the state label to change and do nothing to the drives? I don't feel confident that it did anything and Im having a VERY hard time finding documentation on this. Your approach is not correct. You should have paid attention to the vinum manpage which says this about setstate: This bypasses the usual consistency mechanism of vinum and should be used only for recovery purposes. It is possible to crash the system by incorrect use of this command. It is unfortunate that the manpage says for recovery, since people can misunderstand and think you can recover from a crashed disc. setstate should not need to be used during normal operation, even if a disc in a RAID-5 array crashes. Im assuming I'll want to answer yes to at least some of those. Can I say yes to all of them? What errors should I say no to? I have no idea whats bad bad and whats correctable. An fsck of a degraded RAID-5 array should not normally have any errors. The errors you are seeing is because you have forced out-of-date (stale) data into the middle of the filesystem, messing up pretty much the entire filesystem. Now. because this is a raid5 volume, are some of these fsck prompts false positives? ie; fsck is giving a error but really it's fine as it's raid5? No, that is not how RAID-5 works. RAID-5 protects the integrity of the filesystem by ensuring that the stored data can be read/written even if one disc fails. RAID arrays work at a level below the filesystem, and they generally don't know anything about the actual filesystem. Your only hope now is if you haven't actually allowed anything to be written to the array. If fsck changed things around then you are probably out of luck. IF nothing has been written, then reset the failed disc to the stale/down state (which should put the array in degraded mode hopefully) and then try fsck again. If you are lucky you should see no errors at all. If the disc isn't physically broken, then the proper way to get your array back to the original all up state, you should run a vinum start backup.p0.s3. I'm not sure if this will rebuild all the data automatically (it does for RAID-1 arrays), but if it doesn't then I guess you also need to run a vinum rebuildparity backup.p0. /Daniel Eriksson ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Does Zoom 3075 PCMCIA modem work on FreeBSD ?
Hi: I am contemplating buying a Zoom Model 3075 56K V.92 Modem for my FreeBSD laptop. Have any of you folks used this card? I looked at the FreeBSD laptop compatibility site but saw no mention of it. The manufacturer says it works in Linux. I wonder if it will work in FreeBSD too? TIA Jonathan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A few X questions (small X load for small drive needed)
On Saturday 26 June 2004 06:51, Joe Schmoe wrote: Hi, I just loaded XFree86-4 from the ports tree on my laptop, running 5.2.1-RELEASE. It took about 2.5 gigs of space to compile and add it all. Let's say I have a small hard drive in an old laptop, and let's also assume that I am just loading X to just have a simple GUI to run opera and terminal windows on, and don't need a big fancy X server or whatever ... What are some options I can add to the standard `make install` command for that port to significantly reduce the size of X ? After it is installed you can remove all the .../work directories in the ports tree. Or just start by installing from packages. X itself is not all that big -- but beware the fancy(=bloated) window-managers/desktops such as kde and gnome. If you want something better than twm while remaing compact then blackbox and fluxbox are often mentioned -- I use lesser known ctwm. Malcolm ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: fsck'ing a Vinum RAID5 volume (and a stale drive)
Benjamin P. Keating wrote: Is this approach correct? does this do anything productive or just forces the state label to change and do nothing to the drives? I don't feel confident that it did anything and Im having a VERY hard time finding documentation on this. Let me give you an example of a valid setstate use case: One of my servers has a LOT of discs. For some reason I suffer from interrupt storms during device probing (started after I added a second Highpoint RocketRAID 454 to the machine). These storms sometime prevent the ata code from detecting all the discs. If this happens to be a disc that is part of a RAID-0 array, then when vinum starts up it detects that one of the discs have disappeared and (correctly) marks the array as crashed. There is no proper way to recover from a crashed RAID-0 array - your data is normally lost forever. However, in this specific case I _know_ that nothing has been written to the discs, so once I get the missing disc back online I can use setstate to change the array status from crashed to up, confident that no data has actually been lost. There are a few other use cases for setstate, but they are all (?) outside of the normal procedures for using and maintaining RAID arrays. /Daniel Eriksson ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Intel Anypoint PCMCIA ethernet card-- adding entry to pccard.conf didn't work
I am trying to get my pcmcia ethernet card working on my laptop. It is the Intel Anypoint card and I know that it uses the wi driver, which is compiled into my kernel. I am running 4.10-PRERELEASE. I saw on the list that people have gotten this card to work by adding an entry for it to the /etc/defaults/pccard.conf file. I tried adding the following entry which did not help: card Intel AnyPoint(TM) Wireless II PC Card config auto wi ? insert /etc/pccard_ether $device start remove /etc/pccard_ether $device stop I know that the system recognizes that a card has been added. When I insert it, the following is reported: Jun 26 04:33:53 bird /kernel: pccard: card inserted, slot 1 It doesn't mention anything about the card in particluar, which seems weird to me - I expected it to say that the card was unrecognized or something like that. I don't know if this helps but I got this card to work on the same laptop under netbsd according to a doc on the netbsd site. Doing that required adding entries to 2 or 3 kernel files and recompiling. I tried mimicing that procedure but ran into problems since the kernel files are layed out differently on freebsd. Please let me know if you have any ideas. It is possible that I have forgotten something obvious. Thanks! -Adam __ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[no subject]
i really interested with this OS but i can't get it for free. so where i can get freebsd OS for free? in south east asia region? - Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Getting FreeBSD
On Friday 25 June 2004 08:55 pm, asrul yusuf syahroni wrote: i really interested with this OS but i can't get it for free. so where i can get freebsd OS for free? in south east asia region? Go to this link: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors.htm FreeBSD is available from several sources including a net install. You should be able to find a mirror close to you. Read the handbook on www.freebsd.org especially the sections dealing with getting and installing. Good luck, Beech -- --- Beech Rintoul - System Administrator - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | NorthWind Communications \ / - NO HTML/RTF in e-mail | 201 East 9th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ --- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
