Re: Replacing tape changer with USB disk drives.
and six incremental backups. I have had no problems with reliability. I /do/ have problems with speed. The fast recorded throughput was aroud 3.5 bytes/second; faster than the SCSI-1 DLT it replaces, you must have something wrong. my USB drive gets 27MB/s. yes this 480Mbit/s is USB isn't real, but half of it is. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Replacing tape changer with USB disk drives.
Do the tapes get taken off-site, or do they sit in the same location that the servers will burn when a fire breaks out? probably sits on place, if not he wouldn't need tape changer, but would change manually :) Once the network backup is complete, cycle this complete backup to tape which can be taken off site for longer term storage (after the network backup to 'hot' storage is done, the tape backup time becomes irrelevant). today tapes are so expensive (not just drives, but tapes) that it's better to just have many disks and swap them. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Replacing tape changer with USB disk drives.
Wojciech Puchar wrote: Do the tapes get taken off-site, or do they sit in the same location that the servers will burn when a fire breaks out? probably sits on place, if not he wouldn't need tape changer, but would change manually :) ...not always. A tape changer in some cases is the difference between someone getting off of their a**, and not. Once the network backup is complete, cycle this complete backup to tape which can be taken off site for longer term storage (after the network backup to 'hot' storage is done, the tape backup time becomes irrelevant). today tapes are so expensive (not just drives, but tapes) that it's better to just have many disks and swap them. Expensive is in the eye of the beholder. I have DDS-1 tapes, in the drawer above my head that are from pre-2001 that I can still pull data from. As a matter of fact, I've never (knock on wood) experienced a bad tape (numerous types). In that meantime, I've electro-magnetized dozens of platter-based hard disk drives that just went 'bad' (and subsequently recovered/restored servers from live, and tape-based backup for). I personally don't think that swapping hard-disks (one, or many per day) is a viable, feasible or cost effective approach as a backup solution for long-term data storage, especially if you prefer to be able to recover the data. Here: - network to live storage (hourly perhaps) - live storage to tape - daily - weekly - monthly - yearly ...cycle them in that manner. No matter what anyone says, experience states that I will bet on my monthly and yearly tapes as opposed to hard disk every time when the CFO is under pressure to get that directory that was 'overlooked' at last fiscal tax time. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Replacing tape changer with USB disk drives.
Steve Bertrand wrote: Wojciech Puchar wrote: - monthly - yearly ...cycle them in that manner. No matter what anyone says, experience states that I will bet on my monthly and yearly tapes as opposed to hard disk every time when the CFO is under pressure to get that directory that was 'overlooked' at last fiscal tax time. I've just realized that after being awake for far too long, some people may be reconsidering their use of tapes and replacing them with hard disks now ;) Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to reach hosts outside my subnet after initial installation
Thank you everyone for the assistance. The problem turned out to be with the gateway rather than a freeBSD problem. I did not have access to the gateway but was able to change the IP address, after which everything worked ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Enforce minimal file/ dir permissions
hi Am Montag, den 16.06.2008, 08:51 -0500 schrieb Jeffrey Goldberg: On Jun 16, 2008, at 7:21 AM, Bill Moran wrote: Look at MAC and the bsdextended module (filesystem firewall): http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mac.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mac-bsdextended.html I've recently been looking at those myself, and while I think that I have developed some limited understanding in principle about how MAC works, I need a great deal more practical guidance. Is there some extended tutorial with cookbook or other resource that will actually help someone who doesn't fully grok this work out a policy and rules that will do more good than harm? Yeah, I'm currently in the same need of some documentation. Do you have any hints on that? I would be happy to extend some, if it exists. or even upload some of my own documentation/ knowledge to the web ;-)) oh, and does anybody of you know how to express a file mode of 660 (unix) with the 'ugidfw' utility within a rule? greetz, olli ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ImageMagick 6.4.1.5 tests fail on FBSD-7.0
I sent a query to ImageMagick port maintainers about this. I'm getting errors while trying to upgrade to ImageMagick 6.4.1.5 on FreeBSD 7.0-release. Below are the error messages and my ImageMagick configuration. Please advise many thanks anton [skip] PASS: utilities/tests/wave.sh PASS: utilities/tests/montage.sh All 697 tests passed cd PerlMagick make CC='cc' test /bin/sh ../magick.sh PERL_DL_NONLAZY=1 /usr/local/bin/perl5.8.8 -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t t/bzlib/*.t t/fpx/*.t t/jbig/*.t t/jpeg/*.t t/jp2/*.t t/png/*.t t/tiff/*.t t/wmf/*.t t/zlib/*.t t/blobdubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED test 1 Failed 1/1 tests, 0.00% okay t/bzlib/read..dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED test 1 Failed 1/1 tests, 0.00% okay t/bzlib/write.dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED test 1 Failed 1/1 tests, 0.00% okay t/composite...dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-18 Failed 18/18 tests, 0.00% okay t/filter..dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-58 Failed 58/58 tests, 0.00% okay t/fpx/readdubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-5 Failed 5/5 tests, 0.00% okay t/fpx/write...dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-4 Failed 4/4 tests, 0.00% okay t/getattributedubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-25 Failed 25/25 tests, 0.00% okay t/jbig/read...dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED test 1 Failed 1/1 tests, 0.00% okay t/jbig/write..dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED test 1 Failed 1/1 tests, 0.00% okay t/jp2/readdubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-3 Failed 3/3 tests, 0.00% okay t/jpeg/read...dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-2 Failed 2/2 tests, 0.00% okay t/jpeg/write..dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-2 Failed 2/2 tests, 0.00% okay t/montage.dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-19 Failed 19/19 tests, 0.00% okay t/png/read-16.dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-5 Failed 5/5 tests, 0.00% okay t/png/readdubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-6 Failed 6/6 tests, 0.00% okay t/png/write-16dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-5 Failed 5/5 tests, 0.00% okay t/png/write...dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-6 Failed 6/6 tests, 0.00% okay t/readdubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-47 Failed 47/47 tests, 0.00% okay t/setattributedubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-71 Failed 71/71 tests, 0.00% okay t/tiff/read...dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-16 Failed 16/16 tests, 0.00% okay t/tiff/write..dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-10 Failed 10/10 tests, 0.00% okay t/wmf/readdubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-2 Failed 2/2 tests, 0.00% okay t/write...dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED tests 1-32 Failed 32/32 tests, 0.00% okay t/zlib/read...dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED test 1 Failed 1/1 tests, 0.00% okay t/zlib/write..dubious Test returned status 0 (wstat 139, 0x8b) DIED. FAILED test 1 Failed 1/1 tests, 0.00% okay Failed Test Stat Wstat Total Fail Failed List of Failed --- t/blob.t0 139 12 200.00% 1 t/bzlib/read.t 0 139 12 200.00% 1 t/bzlib/write.t 0 139 12 200.00% 1 t/composite.t 0 13918 36 200.00% 1-18 t/filter.t 0 13958 116 200.00% 1-58 t/fpx/read.t0 139 5 10 200.00% 1-5 t/fpx/write.t 0 139 48 200.00% 1-4 t/getattribute.t0 13925 50 200.00% 1-25 t/jbig/read.t 0 139 12 200.00% 1 t/jbig/write.t 0 139 12 200.00% 1 t/jp2/read.t0 139 36 200.00% 1-3 t/jpeg/read.t 0 139 24 200.00% 1-2 t/jpeg/write.t 0 139 24 200.00% 1-2 t/montage.t
What would it take to be mentored here?
Hello, I was intrigued by this statement on the FreeBSD News Flash page: The FreeBSD Project is always willing to help mentor students learn more about operating system development through our normal community mailing lists and development forums. Contributing to an open source software project is a valuable component of a computer science education and great preparation for a career in software development. Presently, I'm quite unqualified to contribute to an open-source project, but I definitely want to make this a goal. I'm currently in my first year of studies in Computer Science and Programming. After acquiring an Associate's Degree from a technical school, I intend to transfer to a traditional university. I self-learned C++ starting at about age 15 but left off for a little while until finally starting college (later than most). My knowledge of C++ programming is probably on the high end of intermediate (my high school programming class was a joke, and I was able to complete the final projects for college Introduction to Programming before even starting the course), although I have little experience doing practical programming work. I was attracted to free/open-source software because of its quality and the high technical competence of its users. I started learning Linux, but after some research I quickly realized that FreeBSD is probably a much technically superior operating system (although all OSes have their use). I have a basic knowledge of Unix-like operating systems in general. I've been learning about FreeBSD by lurking on a few of the mailing lists, but haven't yet had the courage to subscribe to the hackers list. Since I'm still such a beginner and experienced developers probably don't want to mentor the basic programming skills learned in school, I'm not looking to contribute to a project anytime soon. (For example, I saw Gabor Kovesdan's student project posted to the wip-status list. I'm familiar with regular expressions, but I can safely say that I have no idea how I would implement even a basic grep program.) But since I enjoy computers both as a hobby and an intended profession, my goal is to be eventually skilled enough to make valuable contributions to the free software community. I'm intelligent, a good learner, and I certainly won't limit my knowledge to what they teach in school. I would like to know what specific skill sets the developers here want to see in a student to be mentored, as well as some more specific examples of the kind of work performed by mentored students, in order to have more crystallized goals towards which to focus my effort and studies. Thanks a lot, Jonathan Curtis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What would it take to be mentored here?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Jonathan Curtis wrote: | Hello, Hi Jonathan, great to see you interested in FreeBSD :) While I have no recipe for you, I would like to share my experience, since when I started using FreeBSD I was exactly in the same situation your're finding yourself right now: I was very enthusiastic and willing to lear, help and contribute but couldn't event understand most messages being post on technical mailing lists (you mentioned hackers@, did you? ;P ). I started using FreeBSD for my daily tasks and realized that the infamous man pages (yep, TFM pages) was a great source of knowledge. I started following questions@, hackers@, current@ and stable@ and tried to get useful information out of those. Most messages were rather cryptic at first, but as the time passed I was able to sometimes answer to other users' questions (although most times wrongly...). After a while, let's say 1 year or so, I began to read through the source code when I couldn't find the information I was looking for in the man pages or on the mailing lists. This lead me to produce the first ~ small patches (ranging from documentation clean-ups to feature additions to nonsense). I got the opportunity to begin contributing more on a regular basis when the infamous transition GCC 3.4 - GCC 4.2 began. I happened to be quite familiar with the C standard and GCC and I found myself interested in fixing port which didn't build anymore because of GCC problems. That's the field where I actually submitted most of my PRs to date. After a few dozens PRs I was caught by the eye of a committer (miwi@, tnx!) who just began taking care of me and my PRs. I began a ports committer a few months later. Now I mainly contribute in fixing (old, broken, unmaintained, unwanted, nobody-cares, crap) ports and trying to resuscitate some interest in sparc64. As you can see, there is no wanted skill or preferred goals. The project is large enough that your interests can probably match some FreeBSD need. The only advice I can give you is, don't give up. As time passes you will realize how beautiful this OS is, well structured, well documented, with nice people working at/with it. As an end note, please keep an eye to the project ideas for volunteers, at http://www.freebsd.org/projects/ideas/ , you'll likely find something catching your attention and matching your interests there sooner or later! Thanks, keep on! | | I was intrigued by this statement on the FreeBSD News Flash page: The | FreeBSD Project is always willing to help mentor students learn more | about operating system development through our normal community | mailing lists and development forums. Contributing to an open source | software project is a valuable component of a computer science | education and great preparation for a career in software development. | | Presently, I'm quite unqualified to contribute to an open-source | project, but I definitely want to make this a goal. | | I'm currently in my first year of studies in Computer Science and | Programming. After acquiring an Associate's Degree from a technical | school, I intend to transfer to a traditional university. I | self-learned C++ starting at about age 15 but left off for a little | while until finally starting college (later than most). My knowledge | of C++ programming is probably on the high end of intermediate (my | high school programming class was a joke, and I was able to complete | the final projects for college Introduction to Programming before even | starting the course), although I have little experience doing | practical programming work. | | I was attracted to free/open-source software because of its quality | and the high technical competence of its users. I started learning | Linux, but after some research I quickly realized that FreeBSD is | probably a much technically superior operating system (although all | OSes have their use). I have a basic knowledge of Unix-like operating | systems in general. I've been learning about FreeBSD by lurking on a | few of the mailing lists, but haven't yet had the courage to subscribe | to the hackers list. | | Since I'm still such a beginner and experienced developers probably | don't want to mentor the basic programming skills learned in school, | I'm not looking to contribute to a project anytime soon. (For example, | I saw Gabor Kovesdan's student project posted to the wip-status list. | I'm familiar with regular expressions, but I can safely say that I | have no idea how I would implement even a basic grep program.) But | since I enjoy computers both as a hobby and an intended profession, my | goal is to be eventually skilled enough to make valuable contributions | to the free software community. I'm intelligent, a good learner, and I | certainly won't limit my knowledge to what they teach in school. | | I would like to know what specific skill sets the developers here want | to see in a student to be mentored, as well as some more
Live 4 Soul Newsletter: Events for those in the know!
LIVE 4 SOUL PARTY INFORMATION FOR THOSE IN THE KNOW! Wednesday 18th June: Atmosphere Kidz In The Hall Wednesday 18th June @ Koko, Camden High St London NW1 £15.50 Atmosphere perform live alonside Brother Ali with support from Kids In The Hall. 3 great indie hip-hop acts in one night can't be bad! [http://www.soundcrashmusic.com/shop/product.php?productid=16157cat=0page=1featured] Info Tickets Friday 4th July: The Doctor's Orders 3rd Birthday 9pm-3am Friday 4th July @ Herbal, Kingsland Rd, London E2 £5 IN ADVANCE £10 ON DOOR London's premier Hip-Hop night celebrates it's 3rd Birthday ( American Independance day) with a brillinant line up of US and UK indie Hip-Hop talent. J-ZONE, LOUIS LOGIC BENJI B, STIG, NONAMES, DR SYNTAX, SPIN DOCTOR MR THING [http://www.thedoctorsorders.com/] THE DOCTOR'S ORDERS.COM [http://www.facebook.com/event.php?eid=13807804926] Facebook Event Fridayday 18th July: On The Real 8pm-3am Friday 18th July 2008 @ Bar Rumba 36 Shafstesbury Avenue London W2 Free B4 9.30pm £5 B4 10.30pm £10 after London's premier party providers The Doctor's Orders launch this new night bringing real Hip-Hop Soul back to the west end. Residents Shortee Blitz, DJ MK, Spin Doctor, Skeg, Hooch Guests play Prince to Premier Mos Def to Motown [http://www.facebook.com/group.php?gid=1531891] Facebook Group 29th - 31st August: Outlook Festival Thursday 29th August- Sunday 31th August @ a beautiful peninsular in Croatia £50 in advance This new festival in Croatia boasts the very best in Hip-Hop, Grime, DB soul talent from the UK including Gilles Peterson, Foreign Beggars, Jehst, Stig Dr Syntax, Spin Doctor, Irartion Steppas many more [http://www.facebook.com/group.php?gid=13673732223] Facebook Group This message was sent by: Rod Gilmore, unit 8 14-16 meredith st , london, london ec1r 0ab, United Kingdom Powered by iContact: http://freetrial.icontact.com Manage your subscription: http://app.icontact.com/icp/mmail-mprofile.pl?r=23331904l=46506s=58K0m=307422c=271502 Forward to a friend: http://app.icontact.com/icp/sub/forward?m=307422s=23331904c=58K0cid=271502 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Replacing tape changer with USB disk drives.
Wojciech Puchar writes: Wojciech Puchar writes: Do the tapes get taken off-site, or do they sit in the same location that the servers will burn when a fire breaks out? probably sits on place, if not he wouldn't need tape changer, but would change manually :) The backup system previously mentioned stores the data four feet from the machine serviced. It is - explicitly - designed to protect against catastrophic disk failure, not conflagration. And the backup job runs at 01:59:00, when all operators are happily asleep. The other advantage to this system is the cost. A (new) SCSI LTO-2 and 35 tapes runs US $2000 and up; the same four week's capacity is less than $400, maybe less than $300. 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: Replacing tape changer with USB disk drives.
Wojciech Puchar writes: I /do/ have problems with speed. The fast recorded throughput was aroud 3.5 bytes/second; faster than the SCSI-1 DLT it replaces, you must have something wrong. my USB drive gets 27MB/s. yes this 480Mbit/s is USB isn't real, but half of it is. I agree. Want to take this private and help figure out what's wrong? :-) 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: Replacing tape changer with USB disk drives.
you must have something wrong. my USB drive gets 27MB/s. yes this 480Mbit/s is USB isn't real, but half of it is. I agree. Want to take this private and help figure out what's wrong? :-) i simply have no idea why it could work so slow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
re0 in HP dx2400 not useable.
Hello all I have a new HP dx2400 Desktop PC. It has a Realtek network interface but FreeBSD does not get it going. This is what I get with dmesg re0 RealTek 8168/8111B PCIe Gigabit Ethernet port 0xe800-0xe8ff mem 0xfebff000-0xfebf,0fdff-0fdff irq18 at device 0.0 on pci2 re0 Unknown H/W revision: 3c00 device attach: re0 attach returned 6 pciconf -lv [EMAIL PROTECTED]:2:0:0: class=0x02 card=0x2a73103c chip=0x816810ec rev=0x02 hdr-0x00 vendor = 'Realtek Semiconducter' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC class = network subclass = Ethernet This is on the last snapshots from both 7 and 8 (amd64) I do not know if the messages are the same on 7 or 8 FreeBSD 7 release does not detect the device at all regards, Johan Hendriks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: re0 in HP dx2400 not useable.
On 6/17/08, Johan Hendriks [EMAIL PROTECTED] wrote: Hello all Hi, I have the same problem with a Compaq computer. Maybe you want to have a look at this thread: http://www.mail-archive.com/[EMAIL PROTECTED]/msg64307.html Best regards I have a new HP dx2400 Desktop PC. It has a Realtek network interface but FreeBSD does not get it going. This is what I get with dmesg re0 RealTek 8168/8111B PCIe Gigabit Ethernet port 0xe800-0xe8ff mem 0xfebff000-0xfebf,0fdff-0fdff irq18 at device 0.0 on pci2 re0 Unknown H/W revision: 3c00 device attach: re0 attach returned 6 pciconf -lv [EMAIL PROTECTED]:2:0:0: class=0x02 card=0x2a73103c chip=0x816810ec rev=0x02 hdr-0x00 vendor = 'Realtek Semiconducter' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC class = network subclass = Ethernet This is on the last snapshots from both 7 and 8 (amd64) I do not know if the messages are the same on 7 or 8 FreeBSD 7 release does not detect the device at all regards, Johan Hendriks ___ 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]
Atheros (ath) MSI wireless embedded chipset fails to attach on 7.0-STABLE
Hello: I have installed FreeBSD-7.0-amd64 stable on my new AMD X2 Turon based notebook, a MSI-1710A (GX710Ax) which has a generic embedded controller. During boot up I notice that ATH complains with: ath_rate: version 1.2 SampleRate bit-rate selection algorithm ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: Atheros 5424/2424 mem 0xfd7f-0xfd7f irq 16 at device 0.0 on pci2 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xfd7f ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 HAL status 13 from the header file seems to indicate that the 7.0-STABLE driver doesn't support my hardware revision. Here is my pciconf -l output: [EMAIL PROTECTED]:0:0:0:class=0x06 card=0x42cd1462 chip=0x79101002 rev=0x00 hdr=0x00 [EMAIL PROTECTED]:0:2:0:class=0x060400 card=0x42cd1462 chip=0x79131002 rev=0x00 hdr=0x01 [EMAIL PROTECTED]:0:4:0:class=0x060400 card=0x42cd1462 chip=0x79141002 rev=0x00 hdr=0x01 [EMAIL PROTECTED]:0:6:0:class=0x060400 card=0x42cd1462 chip=0x79161002 rev=0x00 hdr=0x01 [EMAIL PROTECTED]:0:7:0:class=0x060400 card=0x42cd1462 chip=0x79171002 rev=0x00 hdr=0x01 [EMAIL PROTECTED]:0:18:0: class=0x01018f card=0x42cd1462 chip=0x43801002 rev=0x00 hdr=0x00 [EMAIL PROTECTED]:0:19:0: class=0x0c0310 card=0x42cd1462 chip=0x43871002 rev=0x00 hdr=0x00 [EMAIL PROTECTED]:0:19:1: class=0x0c0310 card=0x42cd1462 chip=0x43881002 rev=0x00 hdr=0x00 [EMAIL PROTECTED]:0:19:2: class=0x0c0310 card=0x42cd1462 chip=0x43891002 rev=0x00 hdr=0x00 [EMAIL PROTECTED]:0:19:3: class=0x0c0310 card=0x42cd1462 chip=0x438a1002 rev=0x00 hdr=0x00 [EMAIL PROTECTED]:0:19:4: class=0x0c0310 card=0x42cd1462 chip=0x438b1002 rev=0x00 hdr=0x00 [EMAIL PROTECTED]:0:19:5: class=0x0c0320 card=0x42cd1462 chip=0x43861002 rev=0x00 hdr=0x00 [EMAIL PROTECTED]:0:20:0: class=0x0c0500 card=0x42cd1462 chip=0x43851002 rev=0x14 hdr=0x00 [EMAIL PROTECTED]:0:20:1: class=0x01018a card=0x42cd1462 chip=0x438c1002 rev=0x00 hdr=0x00 [EMAIL PROTECTED]:0:20:2: class=0x040300 card=0x42cd1462 chip=0x43831002 rev=0x00 hdr=0x00 [EMAIL PROTECTED]:0:20:3: class=0x060100 card=0x42cd1462 chip=0x438d1002 rev=0x00 hdr=0x00 [EMAIL PROTECTED]:0:20:4: class=0x060401 card=0x chip=0x43841002 rev=0x00 hdr=0x01 [EMAIL PROTECTED]:0:24:0: class=0x06 card=0x chip=0x11001022 rev=0x00 hdr=0x00 [EMAIL PROTECTED]:0:24:1: class=0x06 card=0x chip=0x11011022 rev=0x00 hdr=0x00 [EMAIL PROTECTED]:0:24:2: class=0x06 card=0x chip=0x11021022 rev=0x00 hdr=0x00 [EMAIL PROTECTED]:0:24:3: class=0x06 card=0x chip=0x11031022 rev=0x00 hdr=0x00 [EMAIL PROTECTED]:1:0:0:class=0x03 card=0x42cd1462 chip=0x95811002 rev=0x00 hdr=0x00 [EMAIL PROTECTED]:1:0:1:class=0x040300 card=0xaa081462 chip=0xaa081002 rev=0x00 hdr=0x00 [EMAIL PROTECTED]:2:0:0:class=0x02 card=0x10261a3b chip=0x001c168c rev=0x01 hdr=0x00 [EMAIL PROTECTED]:5:0:0:class=0x02 card=0x42cd1462 chip=0x816810ec rev=0x01 hdr=0x00 [EMAIL PROTECTED]:6:4:0:class=0x060700 card=0x42cd1462 chip=0x71341217 rev=0x21 hdr=0x02 [EMAIL PROTECTED]:6:4:2:class=0x080500 card=0x42cd1462 chip=0x71201217 rev=0x01 hdr=0x00 [EMAIL PROTECTED]:6:4:3:class=0x068000 card=0x42cd1462 chip=0x71301217 rev=0x01 hdr=0x00 [EMAIL PROTECTED]:6:4:4:class=0x0c0010 card=0x42cd1462 chip=0x00f71217 rev=0x02 hdr=0x00 ath0 is listed as rev=0x01 so I'm a little confused why I got HAL status 13. Does anyone know if this chipset is supported in 7.0-STABLE? If not, is it possible to try CURRENT on 7.0 which may fix it? I've attached my complete dmesg output. Again, any feedback would be much appreciated! -aps unity-dmesg Description: Binary data ___ 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) MSI wireless embedded chipset fails to attach on 7.0-STABLE
Alexander Sack wrote: Hello: I have installed FreeBSD-7.0-amd64 stable on my new AMD X2 Turon based notebook, a MSI-1710A (GX710Ax) which has a generic embedded controller. During boot up I notice that ATH complains with: ath_rate: version 1.2 SampleRate bit-rate selection algorithm ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: Atheros 5424/2424 mem 0xfd7f-0xfd7f irq 16 at device 0.0 on pci2 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xfd7f ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 HAL status 13 from the header file seems to indicate that the 7.0-STABLE driver doesn't support my hardware revision. Here is my pciconf -l output: Maybe you could try compiling a kernel with a newer hal. This is the kind of hack we use on the eeepc. Have a look at this: http://nighthack.org/wiki/EeeBSD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Replacing tape changer with USB disk drives.
Wojciech Puchar [EMAIL PROTECTED] wrote: you must have something wrong. my USB drive gets 27MB/s. yes this 480Mbit/s is USB isn't real, but half of it is. I agree. Want to take this private and help figure out what's wrong? :-) i simply have no idea why it could work so slow. Cheap controller in the USB enclosure. I've used quite a few USB enclosures in the past years, and there are significant performance differences. As a rule of thumb, the cheaper the box, the slower it is. Of course there are exceptions to that rule. By the way, for backup purposes I use a hot-swappable IDE drive frame. The one I use is PATA (UDMA-133), but there are also ones for SATA. It's much faster than USB and more reliable. You can use atacontrol(8) to attach and detach the drive while the system is running. (For that to work reliably, the frame must be the only device on its channel, i.e. no slave, in the PATA case.) Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd It combines all the worst aspects of C and Lisp: a billion different sublanguages in one monolithic executable. It combines the power of C with the readability of PostScript. -- Jamie Zawinski, when asked: What's wrong with perl? ___ 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) MSI wireless embedded chipset fails to attach on 7.0-STABLE
On Tue, Jun 17, 2008 at 11:31 AM, Manolis Kiagias [EMAIL PROTECTED] wrote: Alexander Sack wrote: Hello: I have installed FreeBSD-7.0-amd64 stable on my new AMD X2 Turon based notebook, a MSI-1710A (GX710Ax) which has a generic embedded controller. During boot up I notice that ATH complains with: ath_rate: version 1.2 SampleRate bit-rate selection algorithm ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: Atheros 5424/2424 mem 0xfd7f-0xfd7f irq 16 at device 0.0 on pci2 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xfd7f ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 HAL status 13 from the header file seems to indicate that the 7.0-STABLE driver doesn't support my hardware revision. Here is my pciconf -l output: Maybe you could try compiling a kernel with a newer hal. This is the kind of hack we use on the eeepc. Have a look at this: http://nighthack.org/wiki/EeeBSD Thank you SO much for this link. That's EXACTLY what I want to do because I realize that this is a HAL problem. I've been searching like MAD where I could get an updated binary HAL for this chipset (PCIe based). Let me give this a try, -aps ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Replacing tape changer with USB disk drives.
Cheap controller in the USB enclosure. I've used quite a few USB enclosures in the past years, and there are significant performance differences. As a rule of thumb, the cheaper the box, the slower it is. Of course there are exceptions to that rule. actually - firewire enclosures are not much more expensive, but you always get at least 40MB/s ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Replacing tape changer with USB disk drives.
Oliver Fromme writes: you must have something wrong. my USB drive gets 27MB/s. yes this 480Mbit/s is USB isn't real, but half of it is. i simply have no idea why it could work so slow. Cheap controller in the USB enclosure. I've used quite a few USB enclosures in the past years, and there are significant performance differences. As a rule of thumb, the cheaper the box, the slower it is. Of course there are exceptions to that rule. Would you care to offer experiences and recomendations? 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: Replacing tape changer with USB disk drives.
Wojciech Puchar [EMAIL PROTECTED] wrote: Cheap controller in the USB enclosure. I've used quite a few USB enclosures in the past years, and there are significant performance differences. As a rule of thumb, the cheaper the box, the slower it is. Of course there are exceptions to that rule. actually - firewire enclosures are not much more expensive, but you always get at least 40MB/s Actually they are much more expensive. And more difficult to buy. Most shops here don't have them at all, they only have USB and eSATA, because most people want USB or eSATA. I just looked at one of the most popular online shops around here. They have about 50 different USB enclosures; prices start at 10 EUR. But they have only six Firewire enclosures (and none of them is 2.5!), the cheapest one is 34 EUR. However, they do have a larger number of eSATA enclosures, about 30 different ones. But I don't know how well FreeBSD copes with hot-plugging of eSATA devices; I've never tried one of these. I'm not aware of any specific support yet, but it might work just as well as hot-plug IDE frames. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd [...] one observation we can make here is that Python makes an excellent pseudocoding language, with the wonderful attribute that it can actually be executed. -- Bruce Eckel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Milter-roundhouse
Just curious if anyone has built milter-roundhouse on FreeBSD. We have run milter-ahead on 4.10 through 6.2 (we currently have it running on multiple servers) so I know libsnert builds. I started reading the archives at milter.info but the site has gone away. Thanks, DAve -- Don't tell me I am driving the cart! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: re0 in HP dx2400 not useable.
Johan Hendriks wrote: Hello all I have a new HP dx2400 Desktop PC. It has a Realtek network interface but FreeBSD does not get it going. This is what I get with dmesg re0 RealTek 8168/8111B PCIe Gigabit Ethernet port 0xe800-0xe8ff mem 0xfebff000-0xfebf,0fdff-0fdff irq18 at device 0.0 on pci2 re0 Unknown H/W revision: 3c00 device attach: re0 attach returned 6 pciconf -lv [EMAIL PROTECTED]:2:0:0: class=0x02 card=0x2a73103c chip=0x816810ec rev=0x02 hdr-0x00 vendor = 'Realtek Semiconducter' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC class = network subclass = Ethernet This is on the last snapshots from both 7 and 8 (amd64) I do not know if the messages are the same on 7 or 8 FreeBSD 7 release does not detect the device at all regards, Johan Hendriks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Aloha, On my FreeBSD 8 boxes re0 is for RealTech nic card 8169 SB Pci0 1000 TX Works flawlessly. These are add in cards not on mobo. I recall that 8111 has problems reported in the list months ago. -- ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + email: [EMAIL PROTECTED] All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Replacing tape changer with USB disk drives.
On Jun 17, 2008, at 11:40 AM, Oliver Fromme wrote: Wojciech Puchar [EMAIL PROTECTED] wrote: you must have something wrong. my USB drive gets 27MB/s. yes this 480Mbit/s is USB isn't real, but half of it is. I agree. Want to take this private and help figure out what's wrong? :-) i simply have no idea why it could work so slow. Cheap controller in the USB enclosure. I've used quite a few USB enclosures in the past years, and there are significant performance differences. As a rule of thumb, the cheaper the box, the slower it is. Of course there are exceptions to that rule. By the way, for backup purposes I use a hot-swappable IDE drive frame. The one I use is PATA (UDMA-133), but there are also ones for SATA. It's much faster than USB and more reliable. You can use atacontrol(8) to attach and detach the drive while the system is running. (For that to work reliably, the frame must be the only device on its channel, i.e. no slave, in the PATA case.) Best regards Oliver I get good speeds from USB but they are bursty. I have a pair of identical controllers and both are USB/Firewire. Both have different brands and sizes of disk drive. Could the drive be part of the problem? One is connected via Firewire and doesn't have the bursty speed issue. I've only got it with USB. The poster who mentioned that I'm only looking for a backup against catastrophic disk failure is spot on. Offsite backup is something I'll work out down the road. Chris Hilton e: chris|at|vindaloo| dot|com The pattern juggler lifts his hand; The orchestra begin. As slowly turns the grinding wheel in the court of the crimson king. -- Ian McDonald / Peter Sinfield ___ 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) MSI wireless embedded chipset fails to attach on 7.0-STABLE
On Tue, Jun 17, 2008 at 11:52 AM, Alexander Sack [EMAIL PROTECTED] wrote: On Tue, Jun 17, 2008 at 11:31 AM, Manolis Kiagias [EMAIL PROTECTED] wrote: Alexander Sack wrote: Hello: I have installed FreeBSD-7.0-amd64 stable on my new AMD X2 Turon based notebook, a MSI-1710A (GX710Ax) which has a generic embedded controller. During boot up I notice that ATH complains with: ath_rate: version 1.2 SampleRate bit-rate selection algorithm ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: Atheros 5424/2424 mem 0xfd7f-0xfd7f irq 16 at device 0.0 on pci2 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xfd7f ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 HAL status 13 from the header file seems to indicate that the 7.0-STABLE driver doesn't support my hardware revision. Here is my pciconf -l output: Maybe you could try compiling a kernel with a newer hal. This is the kind of hack we use on the eeepc. Have a look at this: http://nighthack.org/wiki/EeeBSD Thank you SO much for this link. That's EXACTLY what I want to do because I realize that this is a HAL problem. I've been searching like MAD where I could get an updated binary HAL for this chipset (PCIe based). Btw, is there any particular reason you chose the version you linked against what's the current stable release? Also is this the only place to get updated ath HAL's? -aps ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Replacing tape changer with USB disk drives.
I just looked at one of the most popular online shops around here. They have about 50 different USB enclosures; prices start at 10 EUR. But they have only six Firewire enclosures (and none of them is 2.5!), the cheapest one is 34 EUR. i think this 24 EUR it's worth of. However, they do have a larger number of eSATA enclosures, SATA works fine too. ___ 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) MSI wireless embedded chipset fails to attach on 7.0-STABLE
Alexander Sack wrote: On Tue, Jun 17, 2008 at 11:52 AM, Alexander Sack [EMAIL PROTECTED] wrote: On Tue, Jun 17, 2008 at 11:31 AM, Manolis Kiagias [EMAIL PROTECTED] wrote: Alexander Sack wrote: Hello: I have installed FreeBSD-7.0-amd64 stable on my new AMD X2 Turon based notebook, a MSI-1710A (GX710Ax) which has a generic embedded controller. During boot up I notice that ATH complains with: ath_rate: version 1.2 SampleRate bit-rate selection algorithm ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: Atheros 5424/2424 mem 0xfd7f-0xfd7f irq 16 at device 0.0 on pci2 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xfd7f ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 HAL status 13 from the header file seems to indicate that the 7.0-STABLE driver doesn't support my hardware revision. Here is my pciconf -l output: Maybe you could try compiling a kernel with a newer hal. This is the kind of hack we use on the eeepc. Have a look at this: http://nighthack.org/wiki/EeeBSD Thank you SO much for this link. That's EXACTLY what I want to do because I realize that this is a HAL problem. I've been searching like MAD where I could get an updated binary HAL for this chipset (PCIe based). Btw, is there any particular reason you chose the version you linked against what's the current stable release? Also is this the only place to get updated ath HAL's? -aps Well, the linked page is not mine ;) but I have successfully used newer editions of the madwifi driver on the eeepc, so don't let this stop you! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Vsftpd rotate logs with newsyslog...
Hi fellows... I am wanting to rotate logs for vsftpd using newsyslog...My question is, does vsftpd needs to get the HUP or any signal after rotation? I run it from inetd so i guess the HUP should be sent to inetd.pid right? Well, i take this opportunity also to ask about Apache toowhich signal should i send? Thank guys in advance, Agustin ___ 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) MSI wireless embedded chipset fails to attach on 7.0-STABLE
Alexander Sack [EMAIL PROTECTED] escribió: On Tue, Jun 17, 2008 at 11:31 AM, Manolis Kiagias [EMAIL PROTECTED] wrote: Alexander Sack wrote: Hello: I have installed FreeBSD-7.0-amd64 stable on my new AMD X2 Turon based notebook, a MSI-1710A (GX710Ax) which has a generic embedded controller. During boot up I notice that ATH complains with: ath_rate: version 1.2 SampleRate bit-rate selection algorithm ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: Atheros 5424/2424 mem 0xfd7f-0xfd7f irq 16 at device 0.0 on pci2 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xfd7f ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 HAL status 13 from the header file seems to indicate that the 7.0-STABLE driver doesn't support my hardware revision. Here is my pciconf -l output: Maybe you could try compiling a kernel with a newer hal. This is the kind of hack we use on the eeepc. Have a look at this: http://nighthack.org/wiki/EeeBSD Thank you SO much for this link. That's EXACTLY what I want to do because I realize that this is a HAL problem. I've been searching like MAD where I could get an updated binary HAL for this chipset (PCIe based). That makes two of us ;) My dmesg is very, very similar to yours and hoped that this would work. ath0: Atheros 5424/2424 mem 0xf220-0xf220 irq 19 at device 0.0 on pci5 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xf220 ioapic0: routing intpin 19 (PCI IRQ 19) to vector 64 ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 I followed the instructions from the web page, recompiled and it made no difference which really worries me that I must have done something wrong. cd madwifi-ng-r2756+ar5007/hal cp -R * /usr/src/sys/contrib/dev/ath/ I did not erase it previously but am going to try that. I made no kern configuration changes to find that the hal is from contrib. Is there nothing else I should do? Thanks, ed P.S. Some additional info: # uname -a FreeBSD ed.local.net.mx 8.0-CURRENT FreeBSD 8.0-CURRENT #123: Tue Jun 17 12:48:19 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ENCONTACTO amd64 from my kernel conf. device ath # Atheros pci/cardbus NIC's device ath_hal # Atheros HAL (Hardware Access Layer) device ath_rate_sample # SampleRate tx rate control for ath ___ 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) MSI wireless embedded chipset fails to attach on 7.0-STABLE
Edwin L. Culp wrote: Alexander Sack [EMAIL PROTECTED] escribió: On Tue, Jun 17, 2008 at 11:31 AM, Manolis Kiagias [EMAIL PROTECTED] wrote: Alexander Sack wrote: Hello: I have installed FreeBSD-7.0-amd64 stable on my new AMD X2 Turon based notebook, a MSI-1710A (GX710Ax) which has a generic embedded controller. During boot up I notice that ATH complains with: ath_rate: version 1.2 SampleRate bit-rate selection algorithm ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: Atheros 5424/2424 mem 0xfd7f-0xfd7f irq 16 at device 0.0 on pci2 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xfd7f ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 HAL status 13 from the header file seems to indicate that the 7.0-STABLE driver doesn't support my hardware revision. Here is my pciconf -l output: Maybe you could try compiling a kernel with a newer hal. This is the kind of hack we use on the eeepc. Have a look at this: http://nighthack.org/wiki/EeeBSD Thank you SO much for this link. That's EXACTLY what I want to do because I realize that this is a HAL problem. I've been searching like MAD where I could get an updated binary HAL for this chipset (PCIe based). That makes two of us ;) My dmesg is very, very similar to yours and hoped that this would work. ath0: Atheros 5424/2424 mem 0xf220-0xf220 irq 19 at device 0.0 on pci5 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xf220 ioapic0: routing intpin 19 (PCI IRQ 19) to vector 64 ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 I followed the instructions from the web page, recompiled and it made no difference which really worries me that I must have done something wrong. cd madwifi-ng-r2756+ar5007/hal cp -R * /usr/src/sys/contrib/dev/ath/ I did not erase it previously but am going to try that. I made no kern configuration changes to find that the hal is from contrib. Is there nothing else I should do? Thanks, Well, I have only tested this on the eeepc and can confirm it works. Maybe different atheros chipset have other problems not directly related to the hal version. You do not need to do anything more that what is shown in the page: untar, replace the existing files, recompile / install kernel, reboot. If you got no errors during the kernel compilation phase, you can safely assume you did everything correctly, and the problem lies elsewhere. ___ 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) MSI wireless embedded chipset fails to attach on 7.0-STABLE
Manolis Kiagias [EMAIL PROTECTED] escribió: Edwin L. Culp wrote: Alexander Sack [EMAIL PROTECTED] escribió: On Tue, Jun 17, 2008 at 11:31 AM, Manolis Kiagias [EMAIL PROTECTED] wrote: Alexander Sack wrote: Hello: I have installed FreeBSD-7.0-amd64 stable on my new AMD X2 Turon based notebook, a MSI-1710A (GX710Ax) which has a generic embedded controller. During boot up I notice that ATH complains with: ath_rate: version 1.2 SampleRate bit-rate selection algorithm ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: Atheros 5424/2424 mem 0xfd7f-0xfd7f irq 16 at device 0.0 on pci2 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xfd7f ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 HAL status 13 from the header file seems to indicate that the 7.0-STABLE driver doesn't support my hardware revision. Here is my pciconf -l output: Maybe you could try compiling a kernel with a newer hal. This is the kind of hack we use on the eeepc. Have a look at this: http://nighthack.org/wiki/EeeBSD Thank you SO much for this link. That's EXACTLY what I want to do because I realize that this is a HAL problem. I've been searching like MAD where I could get an updated binary HAL for this chipset (PCIe based). That makes two of us ;) My dmesg is very, very similar to yours and hoped that this would work. ath0: Atheros 5424/2424 mem 0xf220-0xf220 irq 19 at device 0.0 on pci5 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xf220 ioapic0: routing intpin 19 (PCI IRQ 19) to vector 64 ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 I followed the instructions from the web page, recompiled and it made no difference which really worries me that I must have done something wrong. cd madwifi-ng-r2756+ar5007/hal cp -R * /usr/src/sys/contrib/dev/ath/ I did not erase it previously but am going to try that. I made no kern configuration changes to find that the hal is from contrib. Is there nothing else I should do? Thanks, Well, I have only tested this on the eeepc and can confirm it works. Maybe different atheros chipset have other problems not directly related to the hal version. You do not need to do anything more that what is shown in the page: untar, replace the existing files, recompile / install kernel, reboot. If you got no errors during the kernel compilation phase, you can safely assume you did everything correctly, and the problem lies elsewhere. At least there was a ray of hope for the time it took to compile the kernel. Thanks, ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Dual NIC routing (?) problem
List, I'm having a problem with a dual-homed host running 7.0-RELEASE with regards to traffic on one of the interfaces that I'm hoping someone knows something about. The goal of this box is to run Nessus on bge0 only (which is plugged into a trunk port on a switch), keeping fxp0 free as the admin interface and for serving web pages on my LAN. Here's ifconfig: bge0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM ether 00:19:b9:22:a8:22 inet 0.0.0.0 netmask 0xff00 broadcast 0.0.0.255 media: Ethernet autoselect (100baseTX full-duplex) status: active fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=bRXCSUM,TXCSUM,VLAN_MTU ether 00:02:b3:bb:59:17 inet 10.20.10.24 netmask 0xff00 broadcast 172.20.10.255 inet 10.20.10.28 netmask 0x broadcast 172.20.10.28 inet 10.20.10.29 netmask 0x broadcast 172.20.10.29 media: Ethernet autoselect (100baseTX full-duplex) status: active /etc/rc.conf section: # Created: Mon Jun 9 09:32:52 2008 defaultrouter=10.20.10.254 hostname=darkhorse.mydomain.local ifconfig_fxp0=inet 10.20.10.24 netmask 255.255.255.0 ifconfig_fxp0_alias0=inet 10.20.10.28 netmask 255.255.255.255 ifconfig_fxp0_alias1=inet 10.20.10.29 netmask 255.255.255.255 ifconfig_bge0=inet 0.0.0.0 netmask 255.255.255.0 I'm not sure what other changes need to be made or where, but when I assign an IP/netmask to bge0, bring up the interface, and try to ping the gateway (or anything else), I get 100% packet loss. I've even tried to assign a new default route, but I get an error stating there's already a default route. I know I'm completely missing something here, but I just can't figure out *what*. Any help would be most appreciated. -MD -- It said use Linux 2.4 kernel or better so I installed FreeBSD. Now everything runs better. Why didn't they just tell me to do that to begin with? ___ 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) MSI wireless embedded chipset fails to attach on 7.0-STABLE
On Tue, Jun 17, 2008 at 3:35 PM, Edwin L. Culp [EMAIL PROTECTED] wrote: Manolis Kiagias [EMAIL PROTECTED] escribió: Edwin L. Culp wrote: Alexander Sack [EMAIL PROTECTED] escribió: On Tue, Jun 17, 2008 at 11:31 AM, Manolis Kiagias [EMAIL PROTECTED] wrote: Alexander Sack wrote: Hello: I have installed FreeBSD-7.0-amd64 stable on my new AMD X2 Turon based notebook, a MSI-1710A (GX710Ax) which has a generic embedded controller. During boot up I notice that ATH complains with: ath_rate: version 1.2 SampleRate bit-rate selection algorithm ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: Atheros 5424/2424 mem 0xfd7f-0xfd7f irq 16 at device 0.0 on pci2 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xfd7f ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 HAL status 13 from the header file seems to indicate that the 7.0-STABLE driver doesn't support my hardware revision. Here is my pciconf -l output: Maybe you could try compiling a kernel with a newer hal. This is the kind of hack we use on the eeepc. Have a look at this: http://nighthack.org/wiki/EeeBSD Thank you SO much for this link. That's EXACTLY what I want to do because I realize that this is a HAL problem. I've been searching like MAD where I could get an updated binary HAL for this chipset (PCIe based). That makes two of us ;) My dmesg is very, very similar to yours and hoped that this would work. ath0: Atheros 5424/2424 mem 0xf220-0xf220 irq 19 at device 0.0 on pci5 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xf220 ioapic0: routing intpin 19 (PCI IRQ 19) to vector 64 ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 I followed the instructions from the web page, recompiled and it made no difference which really worries me that I must have done something wrong. cd madwifi-ng-r2756+ar5007/hal cp -R * /usr/src/sys/contrib/dev/ath/ I did not erase it previously but am going to try that. I made no kern configuration changes to find that the hal is from contrib. Is there nothing else I should do? Thanks, Well, I have only tested this on the eeepc and can confirm it works. Maybe different atheros chipset have other problems not directly related to the hal version. You do not need to do anything more that what is shown in the page: untar, replace the existing files, recompile / install kernel, reboot. If you got no errors during the kernel compilation phase, you can safely assume you did everything correctly, and the problem lies elsewhere. At least there was a ray of hope for the time it took to compile the kernel. Ed: I took recompiled and got the same issue. If I use the LATEST mad distro I get some compile bugs (ath_desc_status was moved into ath_desc structure in ah_desc.h) which I can't completely work around (apparently the API into the HAL has changed as well). What I'm trying to do is look at the Linux driver and understand the newer API in order to get past this compile issue and see if this works. Otherwise I believe we are SOL. Does anyone know if the CURRENT contains an updated ath HAL AND driver for support of newer PCIe based chipsets? If I get it to work I will let you know... -aps ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual NIC routing (?) problem
The MadDaemon wrote: List, I'm having a problem with a dual-homed host running 7.0-RELEASE with regards to traffic on one of the interfaces that I'm hoping someone knows something about. The goal of this box is to run Nessus on bge0 only (which is plugged into a trunk port on a switch), keeping fxp0 free as the admin interface and for serving web pages on my LAN. Here's ifconfig: bge0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM ether 00:19:b9:22:a8:22 inet 0.0.0.0 netmask 0xff00 broadcast 0.0.0.255 media: Ethernet autoselect (100baseTX full-duplex) status: active fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=bRXCSUM,TXCSUM,VLAN_MTU ether 00:02:b3:bb:59:17 inet 10.20.10.24 netmask 0xff00 broadcast 172.20.10.255 inet 10.20.10.28 netmask 0x broadcast 172.20.10.28 inet 10.20.10.29 netmask 0x broadcast 172.20.10.29 media: Ethernet autoselect (100baseTX full-duplex) status: active /etc/rc.conf section: # Created: Mon Jun 9 09:32:52 2008 defaultrouter=10.20.10.254 hostname=darkhorse.mydomain.local ifconfig_fxp0=inet 10.20.10.24 netmask 255.255.255.0 ifconfig_fxp0_alias0=inet 10.20.10.28 netmask 255.255.255.255 ifconfig_fxp0_alias1=inet 10.20.10.29 netmask 255.255.255.255 ifconfig_bge0=inet 0.0.0.0 netmask 255.255.255.0 Try using ifconfig_bge0=up in /etc/rc.conf instead of assigning bogus (probably) address. I'm not sure what other changes need to be made or where, but when I assign an IP/netmask to bge0, bring up the interface, and try to ping the gateway (or anything else), I get 100% packet loss. I've even tried to assign a new default route, but I get an error stating there's already a default route. I know I'm completely missing something here, but I just can't figure out *what*. Any help would be most appreciated. -MD HTH, Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Keyboard repetition under X11
Hi all, this is probably a silly question, but I can't find what I'm doing wrong, so I need help. I just re-installed my FreeBSD box from 6.0 to 7.0 and suddenly I can't get my keyboard to repeat when keeping a key pressed, which has always worked immediately on all my previous installs. This is what I have in my xorg.conf (added last line just to try to force repeat) Section InputDevice Identifier Keyboard0 Driver kbd Option CoreKeyBoard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout se Option AutoRepeat 400 30 EndSection xset q tells me the following: Keyboard Control: auto repeat: onkey click percent: 0LED mask: auto repeat delay: 660repeat rate: 25 auto repeating keys: 00ffdbbf fadfffdfffdfe5ef bell percent: 50bell pitch: 400bell duration: 100 So, as far as I understand, I should have repetition enabled, but the keyboard isn't responding as expected. It's not a hardware problem as it still works on an older FreeBSD machine. The keyboard in question is a cheap USB keyboard identified as follows in dmesg in case that is any help: ukbd0: Ezkey Ezkey USB Keyboard, class 0/0, rev 1.10/1.00, addr 4 on uhub5 Any help appreciated, as I suspect I've done some really basic stupidity, but I can't see it. BR, Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Using gjournal + gmirror on 7.0-RELEASE-p1 (amd64) server
Hi list, I've two Intel Xeon dual core-based servers running 7.0-RELEASE-p1 (amd64). Those servers are running a software raid-1 using geom_gmirror. Today, when I rebooted them twice with 'reboot' command, raid-1 running on both servers got degraded to 0% + filesystem check resulted in 4-5 lost non-critical files. Later I found out that 'reboot' is not a recommended way to reboot a system, and I should use 'shutdown -r now'. Anyways, I'm thinking to use gjournal (in addition to gmirror) on both servers to avoid such situation in future. I'm already using gjournal on my desktop (with no gmirror) running FreeBSD 7.0-RELEASE-p1 (amd64), with no issues. So, I wanted to know if gjournal + gmirror combo is stable enough to be used on a servers. And, if I go for gjournal, since I've an existing filesystem, I've to create a separate gjournal slice, so is it okay to create that gjournal slice on a non-gmirror backed storage, hmm...? TIA -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- pgpj6V55JmrrZ.pgp Description: PGP signature
Kismet Intel 3945abg
Good Day, I have an HP dv9347cl with a built-in Intel 3945abg card. I am utilizing the wpi/wpifw module/driver to run my wireless card. I would like to run kismet without having to use the NDIS wrapper/ipw3945 and have not found any documentation on google/bsdforums for this. Has anyone managed to run Kismet without utilizing the NDIS wrapper and is this a Kismet support issue? Thank you in advanced! David A. This message was sent using IMP, the Internet Messaging Program. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using gjournal + gmirror on 7.0-RELEASE-p1 (amd64) server
Ashish Shukla आशीष शुक्ल wrote: Hi list, I've two Intel Xeon dual core-based servers running 7.0-RELEASE-p1 (amd64). Those servers are running a software raid-1 using geom_gmirror. Today, when I rebooted them twice with 'reboot' command, raid-1 running on both servers got degraded to 0% + filesystem check resulted in 4-5 lost non-critical files. Later I found out that 'reboot' is not a recommended way to reboot a system, and I should use 'shutdown -r now'. Anyways, I'm thinking to use gjournal (in addition to gmirror) on both servers to avoid such situation in future. I'm already using gjournal on my desktop (with no gmirror) running FreeBSD 7.0-RELEASE-p1 (amd64), with no issues. So, I wanted to know if gjournal + gmirror combo is stable enough to be used on a servers. And, if I go for gjournal, since I've an existing filesystem, I've to create a separate gjournal slice, so is it okay to create that gjournal slice on a non-gmirror backed storage, hmm...? TIA You should keep in mind that the space required for the journal depends on the usage load and not the size of the data provider. In other words, if you are using the default 1Gb journal size on your desktop, it may not be enough for a busy server. I've used gjournal+gmirror on a machine - not anything really heavy loaded, but it has given me no problems. I first created the journals, and the gmirror-ed the entire disk. It works as you should expect. I have not tried creating the journal on a non-mirrored storage. I suppose this would work too, but I have no idea how safe it would be. ___ 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) MSI wireless embedded chipset fails to attach on 7.0-STABLE
On Tue, Jun 17, 2008 at 3:44 PM, Alexander Sack [EMAIL PROTECTED] wrote: On Tue, Jun 17, 2008 at 3:35 PM, Edwin L. Culp [EMAIL PROTECTED] wrote: Manolis Kiagias [EMAIL PROTECTED] escribió: Edwin L. Culp wrote: Alexander Sack [EMAIL PROTECTED] escribió: On Tue, Jun 17, 2008 at 11:31 AM, Manolis Kiagias [EMAIL PROTECTED] wrote: Alexander Sack wrote: Hello: I have installed FreeBSD-7.0-amd64 stable on my new AMD X2 Turon based notebook, a MSI-1710A (GX710Ax) which has a generic embedded controller. During boot up I notice that ATH complains with: ath_rate: version 1.2 SampleRate bit-rate selection algorithm ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: Atheros 5424/2424 mem 0xfd7f-0xfd7f irq 16 at device 0.0 on pci2 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xfd7f ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 HAL status 13 from the header file seems to indicate that the 7.0-STABLE driver doesn't support my hardware revision. Here is my pciconf -l output: Maybe you could try compiling a kernel with a newer hal. This is the kind of hack we use on the eeepc. Have a look at this: http://nighthack.org/wiki/EeeBSD Thank you SO much for this link. That's EXACTLY what I want to do because I realize that this is a HAL problem. I've been searching like MAD where I could get an updated binary HAL for this chipset (PCIe based). That makes two of us ;) My dmesg is very, very similar to yours and hoped that this would work. ath0: Atheros 5424/2424 mem 0xf220-0xf220 irq 19 at device 0.0 on pci5 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xf220 ioapic0: routing intpin 19 (PCI IRQ 19) to vector 64 ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 I followed the instructions from the web page, recompiled and it made no difference which really worries me that I must have done something wrong. cd madwifi-ng-r2756+ar5007/hal cp -R * /usr/src/sys/contrib/dev/ath/ I did not erase it previously but am going to try that. I made no kern configuration changes to find that the hal is from contrib. Is there nothing else I should do? Thanks, Well, I have only tested this on the eeepc and can confirm it works. Maybe different atheros chipset have other problems not directly related to the hal version. You do not need to do anything more that what is shown in the page: untar, replace the existing files, recompile / install kernel, reboot. If you got no errors during the kernel compilation phase, you can safely assume you did everything correctly, and the problem lies elsewhere. At least there was a ray of hope for the time it took to compile the kernel. Ed: I took recompiled and got the same issue. If I use the LATEST mad distro I get some compile bugs (ath_desc_status was moved into ath_desc structure in ah_desc.h) which I can't completely work around (apparently the API into the HAL has changed as well). What I'm trying to do is look at the Linux driver and understand the newer API in order to get past this compile issue and see if this works. Otherwise I believe we are SOL. Does anyone know if the CURRENT contains an updated ath HAL AND driver for support of newer PCIe based chipsets? If I get it to work I will let you know... Ok the trick is not to get it from the madfi project. Get it from the author directly! If you grab: http://people.freebsd.org/~sam/ath_hal-20080528.tgz Copy the contents into the src/sys/contrib/dev/ath/* and recompile, you should now see ath attach properly to the your NIC card. Thanks go to my friend jkim for pointing this out since he has a similar notebook/chipset and runs CURRENT successfully. I tried using CURRENT ath but there is to much vap support in it and it turned out the 7.0-RELEASE driver works. Now ath attaches properly and I'm going to test it out! (this is at least much further than a bad attach status code from the HAL). Let me know how it goes, -aps ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Openvpn on FreeBSD 7
Steve Quinn letter2steve at yahoo.com writes: I forgot to stress how important the sysctl setting is for net.inet.ip.forwarding The default is disabled (0) and I to could not connect beyond the OpenVPN server I'm editing the page now to include something like this Make sure IP Forwarding is enabled Check it with sysctl -a |grep net.inet.ip.f Set it with sysctl inet.inet.ip.forwarding=1 or Alternatively set it by adding this to /etc/sysctl.conf net.inet.ip.forwarding=1 Take care Steve I also upgraded from 6.2-RELEASE to 7.0-RELEASE a while back, recompiled my installed ports, and since then I have problems with OpenVPN. I have a laptop (Windows XP SP2) at home and a desktop (FreeBSD 7.0-RELEASE) at my office in the university. I have installed Samba 3.0.28,1 on my desktop and created a share. I can access the share from anywhere within the university network. But our university network is behind a firewall which blocks all incoming connections except SSH, so I cannot access my Samba share from home. What I did was to use Putty to SSH to my desktop at office, setup and OpenVPN client/server on my laptop/desktop computers, and forward all OpenVPN connections to my desktop through the SSH connection using Putty. Then I could connect to my Samba server. It used to work before upgrading to 7.0-RELEASE, but after that I can't access my shares from home. I have confirmed that my Samba share is working fine by accessing it from another computer in the university network, so the only culprit is OpenVPN. It connects, but apparently something is wrong and I can't access my data. I tried setting sysctl inet.inet.ip.forwarding=1 , but that didn't help either. The last lines of my /var/log/openvpn.log is below: Jun 16 11:39:37 rsx4 openvpn[660]: laptop/127.0.0.1:49937 MULTI: bad source address from client [192.168.2.100], packet dropped Jun 16 11:39:37 rsx4 openvpn[660]: laptop/127.0.0.1:49937 MULTI: bad source address from client [192.168.3.1], packet dropped Jun 16 11:41:38 rsx4 openvpn[660]: laptop/127.0.0.1:49937 Connection reset, restarting [0] Jun 16 11:41:38 rsx4 openvpn[660]: laptop/127.0.0.1:49937 SIGUSR1[soft,connection-reset] received, client-instance restarting Jun 16 11:41:38 rsx4 openvpn[660]: TCP/UDP: Closing socket I'd appreciate any help... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
6.3 SMP but only one CPU detected
We have some systems we are upgrading from FreeBSD 6.1 to FreeBSD 6.3. These are Dell PowerEdge servers. The one I'm working on now is a 1950. Under 6.1 it booted into SMP mode no problem. Under 6.3, with no changes made in the BIOS settings, it does not. Here is the start of the dmesg: Jun 17 11:03:26 master1 kernel: Copyright (c) 1992-2008 The FreeBSD Project. Jun 17 11:03:26 master1 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jun 17 11:03:26 master1 kernel: The Regents of the University of California. All rights reserved. Jun 17 11:03:26 master1 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Jun 17 11:03:26 master1 kernel: FreeBSD 6.3-RELEASE-p1 #0: Tue Jun 17 10:27:52 EDT 2008 Jun 17 11:03:26 master1 kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMPKERNEL Jun 17 11:03:26 master1 kernel: Timecounter i8254 frequency 1193182 Hz quality 0 Jun 17 11:03:26 master1 kernel: CPU: Intel(R) Xeon(TM) CPU 3.00GHz (2995.51-MHz 686-class CPU) Jun 17 11:03:26 master1 kernel: Origin = GenuineIntel Id = 0xf64 Stepping = 4 Jun 17 11:03:26 master1 kernel: 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 Jun 17 11:03:26 master1 kernel: Features2=0xe4bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,CNXT-ID,CX16,xTPR,PDCM Jun 17 11:03:26 master1 kernel: AMD Features=0x2010NX,LM Jun 17 11:03:26 master1 kernel: AMD Features2=0x1LAHF Jun 17 11:03:26 master1 kernel: Cores per package: 2 Jun 17 11:03:26 master1 kernel: Logical CPUs per core: 2 Jun 17 11:03:26 master1 kernel: real memory = 2147123200 (2047 MB) Jun 17 11:03:26 master1 kernel: avail memory = 2096021504 (1998 MB) Jun 17 11:03:26 master1 kernel: kbd1 at kbdmux0 Jun 17 11:03:26 master1 kernel: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) Jun 17 11:03:26 master1 kernel: hptrr: HPT RocketRAID controller driver v1.1 (Jun 17 2008 10:27:34) Jun 17 11:03:26 master1 kernel: cpu0 on motherboard Jun 17 11:03:26 master1 kernel: pcib0: Host to PCI bridge pcibus 0 on motherboard Jun 17 11:03:26 master1 kernel: pir0: PCI Interrupt Routing Table: 21 Entries on motherboard Jun 17 11:03:26 master1 kernel: pci0: PCI bus on pcib0 And here's mptable up to the end of the CPU report: === MPTable --- MP Floating Pointer Structure: location: BIOS physical address: 0x000fe710 signature:'_MP_' length: 16 bytes version: 1.4 checksum: 0x91 mode: Virtual Wire --- MP Config Table Header: physical address: 0x000f signature:'PCMP' base table length:796 version: 1.4 checksum: 0x7b OEM ID: 'DELL' Product ID: 'PE 01B3 ' OEM table pointer:0x OEM table size: 0 entry count: 88 local APIC address: 0xfee0 extended table length:0 extended table checksum: 0 --- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model StepFlags 0 0x14BSP, usable 15 6 4 0xbfebfbff 2 0x14AP, usable 15 6 4 0xbfebfbff 6 0x14AP, usable 15 6 4 0xbfebfbff 4 0x14AP, usable 15 6 4 0xbfebfbff After boot we have this: kern.smp.maxcpus: 16 kern.smp.active: 0 kern.smp.disabled: 0 kern.smp.cpus: 1 kern.smp.forward_signal_enabled: 1 kern.smp.forward_roundrobin_enabled: 1 Any clues as to why SMP isn't starting? We've double checked that we have both 'options SMP' and 'device apic' in the running kernel. I've done a lot of googling, and have come up with nothing that seems relevant to our situation. The most puzzling thing is that this worked fine under 6.1 on these same machines --David ___ 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) MSI wireless embedded chipset fails to attach on 7.0-STABLE
Final update, I got everything working! I came home and connected by new notebook using the latest PCIe Atheros chipset to a WPA2 network using wpa_supplicant! Yippie! Hope this thread helps someone else, -aps On Tue, Jun 17, 2008 at 5:17 PM, Alexander Sack [EMAIL PROTECTED] wrote: On Tue, Jun 17, 2008 at 3:44 PM, Alexander Sack [EMAIL PROTECTED] wrote: On Tue, Jun 17, 2008 at 3:35 PM, Edwin L. Culp [EMAIL PROTECTED] wrote: Manolis Kiagias [EMAIL PROTECTED] escribió: Edwin L. Culp wrote: Alexander Sack [EMAIL PROTECTED] escribió: On Tue, Jun 17, 2008 at 11:31 AM, Manolis Kiagias [EMAIL PROTECTED] wrote: Alexander Sack wrote: Hello: I have installed FreeBSD-7.0-amd64 stable on my new AMD X2 Turon based notebook, a MSI-1710A (GX710Ax) which has a generic embedded controller. During boot up I notice that ATH complains with: ath_rate: version 1.2 SampleRate bit-rate selection algorithm ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: Atheros 5424/2424 mem 0xfd7f-0xfd7f irq 16 at device 0.0 on pci2 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xfd7f ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 HAL status 13 from the header file seems to indicate that the 7.0-STABLE driver doesn't support my hardware revision. Here is my pciconf -l output: Maybe you could try compiling a kernel with a newer hal. This is the kind of hack we use on the eeepc. Have a look at this: http://nighthack.org/wiki/EeeBSD Thank you SO much for this link. That's EXACTLY what I want to do because I realize that this is a HAL problem. I've been searching like MAD where I could get an updated binary HAL for this chipset (PCIe based). That makes two of us ;) My dmesg is very, very similar to yours and hoped that this would work. ath0: Atheros 5424/2424 mem 0xf220-0xf220 irq 19 at device 0.0 on pci5 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xf220 ioapic0: routing intpin 19 (PCI IRQ 19) to vector 64 ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 I followed the instructions from the web page, recompiled and it made no difference which really worries me that I must have done something wrong. cd madwifi-ng-r2756+ar5007/hal cp -R * /usr/src/sys/contrib/dev/ath/ I did not erase it previously but am going to try that. I made no kern configuration changes to find that the hal is from contrib. Is there nothing else I should do? Thanks, Well, I have only tested this on the eeepc and can confirm it works. Maybe different atheros chipset have other problems not directly related to the hal version. You do not need to do anything more that what is shown in the page: untar, replace the existing files, recompile / install kernel, reboot. If you got no errors during the kernel compilation phase, you can safely assume you did everything correctly, and the problem lies elsewhere. At least there was a ray of hope for the time it took to compile the kernel. Ed: I took recompiled and got the same issue. If I use the LATEST mad distro I get some compile bugs (ath_desc_status was moved into ath_desc structure in ah_desc.h) which I can't completely work around (apparently the API into the HAL has changed as well). What I'm trying to do is look at the Linux driver and understand the newer API in order to get past this compile issue and see if this works. Otherwise I believe we are SOL. Does anyone know if the CURRENT contains an updated ath HAL AND driver for support of newer PCIe based chipsets? If I get it to work I will let you know... Ok the trick is not to get it from the madfi project. Get it from the author directly! If you grab: http://people.freebsd.org/~sam/ath_hal-20080528.tgz Copy the contents into the src/sys/contrib/dev/ath/* and recompile, you should now see ath attach properly to the your NIC card. Thanks go to my friend jkim for pointing this out since he has a similar notebook/chipset and runs CURRENT successfully. I tried using CURRENT ath but there is to much vap support in it and it turned out the 7.0-RELEASE driver works. Now ath attaches properly and I'm going to test it out! (this is at least much further than a bad attach status code from the HAL). Let me know how it goes, -aps ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wireless net work set up
Hello Jeff Thanks for your repply yes I noticed that and I tried what you suggested as well before but nada I tried a couple of things that may give somebody clues of what is going on 1. I use the sysintall utility and went to configure-networking-interfaces and noted the following regarding my interfaces: ndis0 unknown network interface type rl0RealTek 8129/8139 PCI ethernet card (this is the ethernet that I am using rigth now) so the kernel on boot recognices the hardware but seems like later does not have a clue about it. Is there a config file where I should specify this? 2. I tried what jeff sugested in the following manner typig from root: Pavilion# ifconfig ndis0 inet 192.168.1.5/24 Pavilion# dhclient ndis0 DHCPDISCOVER on ndis0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on ndis0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on ndis0 to 255.255.255.255 port 67 interval 21 DHCPDISCOVER on ndis0 to 255.255.255.255 port 67 interval 14 DHCPDISCOVER on ndis0 to 255.255.255.255 port 67 interval 10 No DHCPOFFERS received. No working leases in persistent database - sleeping. # This seems to be common theme all the time, I get the same thing # during boot process # Later I tried: Pavilion# ifconfig ndis0 up scan SSIDBSSID CHAN RATE S:N INT CAPS BELL455 00:1b:5b:6b:04:31 11 54M 139:0 100 EP ??? ??? ??? ??? ??? ??? LFnet 00:13:46:cd:8e:9a6 54M 151:0 100 EP ??? ??? ??? ??? ??? WPA ATH VEN VEN WME isaac 00:1c:10:24:c9:f66 54M 115:0 100 EP ??? ??? ??? ??? ??? ??? VEN WPA Pavilion# ifconfig ndis0 ndis0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 ether 00:90:4b:f3:6e:44 media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier ssid channel 1 authmode OPEN privacy OFF txpowmax 100 bmiss 7 protmode CTS # Later I tried a manual connection Pavilion# wpa_supplicant -i ndis0 -c /etc/wpa_supplicant.conf Trying to associate with 00:13:46:cd:8e:9a (SSID='LFnet' freq=2437 MHz) WPA: Key negotiation completed with 00:13:46:cd:8e:9a [PTK=TKIP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed (auth) # here the terminal just hangs and noting happens, have to hit ^+C to terminate although while this was happening I open another window and run ifconfig ndis0 to see the status of the device $ ifconfig ndis0 ndis0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 ether 00:90:4b:f3:6e:44 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps) status: associated ssid LFnet channel 6 bssid 00:13:46:cd:8e:9a authmode WPA privacy OFF TKIP 2:128-bit txpowmax 100 bmiss 7 protmode CTS so the darn thing is getting connected but again no transfer of information. Something that puzzle me is that the inet and the broadcast were reset does this give any additional clues of what may be the problem? I have a question about this: should I be telling freebsd wich interface should be use? rl0 is up and running at the same time will it conflict with ndis0? Thanks Luis --- El mar 17-jun-08, [EMAIL PROTECTED] [EMAIL PROTECTED] escribió: De: [EMAIL PROTECTED] [EMAIL PROTECTED] Asunto: Re: Wireless net work set up A: Luis Trimiÿf1o [EMAIL PROTECTED] Fecha: martes, 17 junio, 2008, 9:56 am Luis, Take a look at your ifconfig output. You'll notice that ndis0 has an ip of 0.0.0.0 with a broadcast of 255.255.255.255. Either set this with: ifconfig ndis0 inet 192.168.1.5/24 or if your router assigns dhcp leases: dhclient ndis0 HTH, Jeff Hello I had been trying to set up a wireless connection for my laptop but nothing seems to work What I am using: FreeBSD 6.2 release p3 Architecture amd 64 hardware: HP pavilion zv6000 so far what I had done: 1. Use the ndisgen to make kernel modules from wireless broadcom windows drivers. 2. verify that the drivers actualy work with the kernel by checking dmesg here is my dmesg: FreeBSD 6.2-RELEASE-p3 #3: Sat Mar 24 14:24:31 EST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KERNEL2 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3800+ (2387.79-MHz K8-class CPU) Origin = AuthenticAMD Id = 0xff0 Stepping = 0 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 AMD Features=0xe0500800SYSCALL,NX,MMX+,LM,3DNow+,3DNow real memory = 1072627712 (1022 MB) avail memory = 1023938560 (976 MB) kbd0 at kbdmux0 cpu0 on motherboard pcib0: Host to PCI bridge pcibus 0 on motherboard pci0: PCI bus on pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display,
Hylafax config and Windows clients
Hi,
I'm configuring new Hylafax fax server on FreeBSD 7 with Conexant chip
modem. Something not working right on server, because I can't send any
faxes, no matter what client I use. Modem is working in Windows, but I
want to use it in a networked environment with Sane backend to replace
broken Brother FAX machine. Fax machine was very busy, recieving around
150 faxes/day, so I don't want to throw for another Fax machine that will
be broken after few months. So I've added user fax, configured settings
with 'faxsetup' and 'faxaddmodem'and I hoped everything should work. Here
are conf files in hylafax/etc directory. I don't know where to look at?
Can anyone help me?
fax# cat config
LogFacility:daemon
CountryCode:359
AreaCode: 84
LongDistancePrefix: 0
InternationalPrefix:00
DialStringRules:etc/dialrules
ServerTracing: 1
fax# cat hosts.hfaxd
localhost
127.0.0.1
192.168.1.*
^fax@
fax# cat setup.cache
# Warning, this file was automatically generated by faxsetup
# on Wed Jun 18 00:06:50 EEST 2008 for fax
AWK='/usr/bin/nawk'
BASE64ENCODE='/usr/bin/uuencode -m | /usr/bin/grep -v '
BIN='/usr/local/bin'
CAT='/bin/cat'
CHGRP='/usr/bin/chgrp'
CHMOD='/bin/chmod'
CHOWN='/usr/sbin/chown'
CP='/bin/cp'
DPSRIP='/usr/local/sbin/ps2fax.exe'
ECHO='/bin/echo'
ENCODING='base64'
FAXQ_SERVER='yes'
FONTPATH='/usr/local/share/ghostscript/8.62/lib:/usr/local/share/ghostscript/8.62/Resource:/usr/local/share/ghostscript/fonts:/usr/local/share/fonts/default/ghostscript:/usr/local/share/fonts/default/Type1:/usr/local/share/fonts/default/TrueType:/usr/lib/DPS/outline/base:/usr/openwin/lib/X11/fonts/Type1:/usr/openwin/lib/X11/fonts/TrueType'
FUSER='fuser'
GREP='/usr/bin/grep'
GSRIP='/usr/local/bin/gs'
HFAXD_OLD_PROTOCOL='no'
HFAXD_SERVER='yes'
HFAXD_SNPP_SERVER='no'
IMPRIP='/usr/lib/print/psrip'
LIBDATA='/usr/local/lib/fax'
LIBEXEC='/usr/local/sbin'
LN='/bin/ln'
MANDIR='/usr/local/man'
MIMENCODE='mimencode'
MKFIFO='/usr/bin/mkfifo'
MV='/bin/mv'
PATH='/usr/sbin:/bin:/usr/bin:/etc:/usr/local/bin'
PATHEGETTY='/bin/egetty'
PATHGETTY='/usr/libexec/getty'
PATHVGETTY='/bin/vgetty'
PSPACKAGE='gs'
QPENCODE='qp-encode'
RM='/bin/rm'
SBIN='/usr/local/sbin'
SCRIPT_SH='/bin/sh'
SED='/usr/bin/sed'
SENDMAIL='/usr/sbin/sendmail'
SPOOL='/var/spool/hylafax'
SYSVINIT=''
TARGET='i386-unknown-freebsd7.0'
TIFF2PDF='/usr/local/bin/tiff2pdf'
TIFFBIN='/usr/local/bin'
TTYCMD='/usr/bin/tty'
UUCP_LOCKDIR='/var/spool/lock'
UUCP_LOCKTYPE='ascii'
UUENCODE='/usr/bin/uuencode'
fax# cat setup.modem
# Warning, this file was automatically generated by faxsetup
# on Wed Jun 18 00:06:42 EEST 2008 for fax
prompt()
{
echo -n $*
}
ttyPort()
{
expr $1 : 'tty\(.*\)'
}
ttyLocks()
{
echo $UUCP_LOCKDIR/LCK..`expr /$1 : '.*/\(.*\)'`
}
ttyAliases()
{
echo /dev/$1
}
ttyDev()
{
echo /dev/$1
}
checkPort()
{
return
}
ttyStty()
{
echo /bin/stty -f $tdev
}
ttySpeeds()
{
speeds=
if [ -z $SPEED ]; then
for s in 38400 19200 9600 4800 2400 1200; do
/bin/stty -f $tdev $s /dev/null /dev/null 21
speeds=$speeds $s
done
fi
echo $speeds
}
--
Windows: Where do you want to go today?
Linux: Where do you want to go tomorrow?
FreeBSD: Are you guys coming, or what?
___
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) MSI wireless embedded chipset fails to attach on 7.0-STABLE
Alexander Sack [EMAIL PROTECTED] escribió: Final update, I got everything working! I came home and connected by new notebook using the latest PCIe Atheros chipset to a WPA2 network using wpa_supplicant! Yippie! Hope this thread helps someone else, -aps On Tue, Jun 17, 2008 at 5:17 PM, Alexander Sack [EMAIL PROTECTED] wrote: On Tue, Jun 17, 2008 at 3:44 PM, Alexander Sack [EMAIL PROTECTED] wrote: On Tue, Jun 17, 2008 at 3:35 PM, Edwin L. Culp [EMAIL PROTECTED] wrote: Manolis Kiagias [EMAIL PROTECTED] escribió: Edwin L. Culp wrote: Alexander Sack [EMAIL PROTECTED] escribió: On Tue, Jun 17, 2008 at 11:31 AM, Manolis Kiagias [EMAIL PROTECTED] wrote: Alexander Sack wrote: Hello: I have installed FreeBSD-7.0-amd64 stable on my new AMD X2 Turon based notebook, a MSI-1710A (GX710Ax) which has a generic embedded controller. During boot up I notice that ATH complains with: ath_rate: version 1.2 SampleRate bit-rate selection algorithm ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: Atheros 5424/2424 mem 0xfd7f-0xfd7f irq 16 at device 0.0 on pci2 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xfd7f ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 HAL status 13 from the header file seems to indicate that the 7.0-STABLE driver doesn't support my hardware revision. Here is my pciconf -l output: Maybe you could try compiling a kernel with a newer hal. This is the kind of hack we use on the eeepc. Have a look at this: http://nighthack.org/wiki/EeeBSD Thank you SO much for this link. That's EXACTLY what I want to do because I realize that this is a HAL problem. I've been searching like MAD where I could get an updated binary HAL for this chipset (PCIe based). That makes two of us ;) My dmesg is very, very similar to yours and hoped that this would work. ath0: Atheros 5424/2424 mem 0xf220-0xf220 irq 19 at device 0.0 on pci5 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xf220 ioapic0: routing intpin 19 (PCI IRQ 19) to vector 64 ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 I followed the instructions from the web page, recompiled and it made no difference which really worries me that I must have done something wrong. cd madwifi-ng-r2756+ar5007/hal cp -R * /usr/src/sys/contrib/dev/ath/ I did not erase it previously but am going to try that. I made no kern configuration changes to find that the hal is from contrib. Is there nothing else I should do? Thanks, Well, I have only tested this on the eeepc and can confirm it works. Maybe different atheros chipset have other problems not directly related to the hal version. You do not need to do anything more that what is shown in the page: untar, replace the existing files, recompile / install kernel, reboot. If you got no errors during the kernel compilation phase, you can safely assume you did everything correctly, and the problem lies elsewhere. At least there was a ray of hope for the time it took to compile the kernel. Ed: I took recompiled and got the same issue. If I use the LATEST mad distro I get some compile bugs (ath_desc_status was moved into ath_desc structure in ah_desc.h) which I can't completely work around (apparently the API into the HAL has changed as well). What I'm trying to do is look at the Linux driver and understand the newer API in order to get past this compile issue and see if this works. Otherwise I believe we are SOL. Does anyone know if the CURRENT contains an updated ath HAL AND driver for support of newer PCIe based chipsets? If I get it to work I will let you know... Ok the trick is not to get it from the madfi project. Get it from the author directly! If you grab: http://people.freebsd.org/~sam/ath_hal-20080528.tgz Copy the contents into the src/sys/contrib/dev/ath/* and recompile, you should now see ath attach properly to the your NIC card. Thanks go to my friend jkim for pointing this out since he has a similar notebook/chipset and runs CURRENT successfully. I tried using CURRENT ath but there is to much vap support in it and it turned out the 7.0-RELEASE driver works. Now ath attaches properly and I'm going to test it out! (this is at least much further than a bad attach status code from the HAL). Let me know how it goes, Going G R E A T for the first time I see: ath_hal: 0.10.5.6 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417) ath0: Atheros 5424/2424 mem 0xf220-0xf220 irq 19 at device 0.0 on pci5 ath0: [ITHREAD] ath0: WARNING: using obsoleted if_watchdog interface ath0: mac 14.2 phy 7.0 radio 10.2 and an ifconfig ath0 shows: ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:1d:d9:27:5c:e5 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
Re: Using gjournal + gmirror on 7.0-RELEASE-p1 (amd64) server
Manolis == Manolis Kiagias [EMAIL PROTECTED] writes: Manolis Ashish Shukla आशीष शुक्ल wrote: [snip] And, if I go for gjournal, since I've an existing filesystem, I've to create a separate gjournal slice, so is it okay to create that gjournal slice on a non-gmirror backed storage, hmm...? Manolis You should keep in mind that the space required for the journal Manolis depends on the usage load and not the size of the data provider. In Manolis other words, if you are using the default 1Gb journal size on your Manolis desktop, it may not be enough for a busy server. Okay. Manolis I've used gjournal+gmirror on a machine - not anything really heavy Manolis loaded, but it has given me no problems. I first created the journals, Manolis and the gmirror-ed the entire disk. It works as you should expect. I Manolis have not tried creating the journal on a non-mirrored storage. I Manolis suppose this would work too, but I have no idea how safe it would be. I'll also opt for journal on mirrored storage, which is the same storage device as data provider. Thanks for the reply -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- pgp9kFB64l6qz.pgp Description: PGP signature
Re: internet slowdown
On Mon, 16 Jun 2008 08:23:32 -0400 Bill Moran [EMAIL PROTECTED] wrote: Is the console responsive when this happens? when it bogs it takes ages to even ssh into the server. It doesn't sound like a CPU issue to me -- ICMP messages are low enough CPU overhead that the system would have to be pretty badly bogged for CPU starvation to cause problems. agreed - otherwise why would the cpu be idle. What do your network traffic graphs show during the slowdowns? Perhaps some sort of network flood occurring? we are looking at flow-tools unless you have any other suggestions. there has been no problems for 2+ days, but we are going to follow through on this anyways and be prepared. thank you for your ideas bill and i'll let you know if we learn anything. -- In friendship, prad ... with you on your journey Towards Freedom http://www.towardsfreedom.com (website) Information, Inspiration, Imagination - truly a site for soaring I's ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
