From jhs at berklix.org Sun Feb 1 05:01:09 2009 From: jhs at berklix.org (Julian Stacey) Date: Sun Feb 1 05:01:17 2009 Subject: Suggestion for "moderation" In-Reply-To: Your message "Fri, 30 Jan 2009 01:22:16 +0100." <436c7eda0901291622v35f9d80ewb778d8ca7efb114e@mail.gmail.com> Message-ID: <200902011235.n11CZaHR090343@fire.js.berklix.net> Hi, Reference: > From: Jonas Lund > Date: Fri, 30 Jan 2009 01:22:16 +0100 > Message-id: <436c7eda0901291622v35f9d80ewb778d8ca7efb114e@mail.gmail.com> Jonas Lund wrote: > I've had enough of spam and crackpot-newsletters now. And i'm on the > verge of unsubscribing as i guess instituting full moderation wouldn't > be very practical (i'm sure most people don't get paid for sitting > here) > > Altho just leaving and complaining won't help anybody (and i do love freebsd). > > So.... > Isn't there some kind of auto-moderation system that could be placed > in (Plugin or whatever)? Like delaying the mails for an hour for all > newly subscribed users (so kicking people off the list will force them > to re-list) and then just sending the mail in advance to "moderators" NO. No human censors Please, Latin approx: Quis Custodes Custodiensis. English: Who guards us from the guardians "Power corrupts, absolute power corrupts absolutely" (I have observed such corruption on a non BSD list) > that would have simple link that would remove the mail from the queue. > (Maybe one hit on the link would delay the mail futher and several > clicks within the timespan would kill it). > > This way message will get through by default but annoying stuff > wouldn't affect everybody. > > Just another 2C Best thing is to first look at which tools & config freebsd.org currently use for their lists. Then look at what other full automatic anti spam tools are ready & available to integrate. ie this whol topic does not belong on hardware@, its a generic background to all lists, so should be discussed with the FreeBSD postmaster team. Cheers, Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com Mail plain ASCII text. HTML & Base64 text are spam. www.asciiribbon.org From rsk at gsp.org Sun Feb 1 05:37:31 2009 From: rsk at gsp.org (Rich Kulawiec) Date: Sun Feb 1 05:37:37 2009 Subject: Suggestion for "moderation" In-Reply-To: <436c7eda0901291622v35f9d80ewb778d8ca7efb114e@mail.gmail.com> References: <436c7eda0901291622v35f9d80ewb778d8ca7efb114e@mail.gmail.com> Message-ID: <20090201131515.GA10277@gsp.org> On Fri, Jan 30, 2009 at 01:22:16AM +0100, Jonas Lund wrote: > Isn't there some kind of auto-moderation system that could be placed > in (Plugin or whatever)? It's much simpler than that. This list is run by Mailman. It's a matter of a couple of clicks in a web interface to change the list settings so that (a) mail from known subscribers is passed through and (b) mail from everyone else is held for moderator attention. This is by no means a panacea, but it does cut out a great deal of the noise, thereby allow more focused attention on whatever manages to escape this measure. ---Rsk From pyunyh at gmail.com Sun Feb 1 20:51:03 2009 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Sun Feb 1 20:51:33 2009 Subject: Atheros AR821 (Asus P5Q Pro) and 'ale' driver In-Reply-To: <92056ebc0901231336x188b4d81l9c6d804e8aa437de@mail.gmail.com> References: <92056ebc0901231336x188b4d81l9c6d804e8aa437de@mail.gmail.com> Message-ID: <20090202045129.GD43513@michelle.cdnetworks.co.kr> On Fri, Jan 23, 2009 at 10:36:34PM +0100, Giuseppe Pagnoni wrote: > Dear all, > > I am running freebsd 7.1 rel on an Asus p5q pro motherboard with an > onboard ethernet chip Atheros AR8121. I am using the "ale" driver, > which generally seems to work, although I noticed that when connecting > via ssh to the machine, I get disconnected with "corrupted MAC on > input" a little too often. > > Does anybody know if this may be an issue related to the ethernet > driver, or is it likely to be something totally unrelated? (I don't > get the same behavior, though, when the machine is booted in Ubuntu). > AR8121/AR8113/AR8114 are known to have Rx checksum offloading bug and ale(4) have a workaround for the bug. I'm not sure whether you're seeing the same bug not handled in the workaround code, though. If you disable Rx checksum offloading(e.g. ifconfig ale0 -rxcsum) does ssh still complain 'corrupted MAC'? Since you seem to have a way to reproduce the issue, would you show me the way to trigger the issue? > thank you very much for any suggestions > > giuseppe From kayve at sfsu.edu Sun Feb 1 23:00:04 2009 From: kayve at sfsu.edu (Kayven Riese) Date: Sun Feb 1 23:00:12 2009 Subject: Suggestion for In-Reply-To: <200902011235.n11CZaHR090343@fire.js.berklix.net> References: <200902011235.n11CZaHR090343@fire.js.berklix.net> Message-ID: -----owner-freebsd-hardware@fre To: freebsd-hardware@freebsd.org From: "Julian Stacey" & Sent by: owner-freebsd-hardware@freebsd.org Da Subject: Re: Suggestion for "moderation" < Reference: > From: &n > Date: > Message-id: <436c7eda0901291622v35f9d80ewb778d8ca7efb114e@mail.gmail.com> Jonas Lund wrote: > I've had enough of spam and crackpot-newsle on the > verge of unsubscribing as i guess institu wouldn't > be very practical (i'm sure most peop sitting > here) > > Altho just lea love freebsd). > > So.... > Isn't there some kind of auto-moderation system that placed > in (Plugin or whatever)? Like delaying the mails fo for all > newly subscribed users (so kicking people off the force them > to re-list) and then just sending the mail in "moderators" NO. No human censors Please, &nbs [DEL: :DEL] English: Who guards us from the guardia "Power corrupts, absolute power (I have obse > that would have simple queue. > (Maybe one hit on t several > clicks within the t > > This way message will get through > wouldn't affect everybody. > > Just another 2C Best thing is to first look at which tools &a freebsd.org currently use for their lists. Then look at automatic anti spam tools are ready & available to topic does not belong on hardware@, its a all lists, so should be discussed with the FreeBSD Cheers, Julian IMHO, FreeBSD does a -- Julian Stacey: BSDUnixLinux C Prog Admin Sy www.berklix.com Mail plain ASCII text. www.asciiribbon.org ______ ______________________ 5F__ freebsd-hardware@freebs [1]http://lists.freebsd.org/mailman/listinfo/freebsd-hardwar To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@fre ebsd.org" References 1. 3D"http://lists.freebsd.org/mailman/listinfo/ From freebsd at sopwith.solgatos.com Mon Feb 2 21:08:34 2009 From: freebsd at sopwith.solgatos.com (Dieter) Date: Mon Feb 2 21:08:50 2009 Subject: JMB363 and hotplugging? Message-ID: <200902030357.DAA03859@sopwith.solgatos.com> SATA is supposed to support hotplugging, but I tried it with the nforce4-ultra and the kernel (FreeBSD 7.0 amd64) hung. :-( Does hotplugging work properly with the JMB363 SATA controller? From pluknet at gmail.com Tue Feb 3 07:24:36 2009 From: pluknet at gmail.com (pluknet) Date: Tue Feb 3 07:24:42 2009 Subject: JMB363 and hotplugging? In-Reply-To: <200902030357.DAA03859@sopwith.solgatos.com> References: <200902030357.DAA03859@sopwith.solgatos.com> Message-ID: 2009/2/2 Dieter : > SATA is supposed to support hotplugging, but I tried it with > the nforce4-ultra and the kernel (FreeBSD 7.0 amd64) hung. :-( Of course you connected disks through a SATA backplane, which performs all the management.. -- wbr, pluknet From won.derick at yahoo.com Tue Feb 3 19:49:31 2009 From: won.derick at yahoo.com (Won De Erick) Date: Tue Feb 3 19:49:37 2009 Subject: acpi_alloc_wakeup_handler: can't alloc wake memory and ACPI's *** Warning Message-ID: <85591.73784.qm@web45808.mail.sp1.yahoo.com> Hello All, I just observed the following messages, and attracted my attention. I've seen the following link, but I'm confused how to start with. http://lists.freebsd.org/pipermail/freebsd-acpi/2006-June/002903.html # uname FreeBSD # uname -r 6.2-RELEASE-p11 #dmesg .... acpi_alloc_wakeup_handler: can't alloc wake memory .... ACPI-0698: *** Warning: Type override - [DEB_] had invalid type (Integer) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [MLIB] had invalid type (Integer) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [DATA] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [SIO_] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [LEDP] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [GPEN] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [GPST] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [WUES] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [WUSE] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [SBID] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [SWCE] had invalid type (String) for Scope operator, changed to (Scope) I should want to begin understanding why these had occurred. My box is an IBM x343, with 2G memory. The FreeBSD is just installed in a 512MB-compact flash card with no SWAP partition in it. Are those harmful? Any explanation and help pls. to solve this? Other usefull info: # sysctl -a | grep hyper machdep.hyperthreading_allowed: 0 # sysctl -a | grep hw.acpi hw.acpi.supported_sleep_state: S1 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 0 hw.acpi.verbose: 0 hw.acpi.disable_on_reboot: 0 hw.acpi.handle_reboot: 0 hw.acpi.reset_video: 0 hw.acpi.cpu.cx_supported: C1/0 hw.acpi.cpu.cx_lowest: C1 hw.acpi.cpu.cx_usage: 100.00% Thanks! From freebsd at sopwith.solgatos.com Wed Feb 4 00:07:54 2009 From: freebsd at sopwith.solgatos.com (Dieter) Date: Wed Feb 4 00:08:00 2009 Subject: JMB363 and hotplugging? In-Reply-To: Your message of "Tue, 03 Feb 2009 17:51:42 +0300." Message-ID: <200902040717.HAA25762@sopwith.solgatos.com> > > SATA is supposed to support hotplugging, but I tried it with > > the nforce4-ultra and the kernel (FreeBSD 7.0 amd64) hung. :-( > > Of course you connected disks through a SATA backplane, > which performs all the management.. Management? What management? umount swapoff (and allow time for i/o) atacontrol detach pull sata data cable observe hung kernel :-( press reset button :-( From andrnils at gmail.com Wed Feb 4 14:16:18 2009 From: andrnils at gmail.com (Andreas Nilsson) Date: Wed Feb 4 14:16:25 2009 Subject: ipw3945 problems Message-ID: Hi, I've been experiencing some weird behavior with the ipw3945 on my laptop running FreeBSD 7.1-RELEASE. When running on AC the card works as expected, but when running unplugged the interface keeps going down and up and down. I get ~10 consecutive pings before it goes down. The networks I have tested are encrypted with some WPA protocol. When starting on battery there are also some other strange behavior, there are some lock-ups in the gui and xorg uses some 14% cpu @1.2GHz doing nothing, When the mouse has been idle for some seconds it takes a bit of movement to activate again. After a plug and unplug of the AC everything seems to work as it is supposed to. I realize this isn't very much to go on... Any logs that would help? The laptop in question is a Lenovo Thinkpad t61p. Best regards Andreas Nilsson From lawrence.auster at att.net Thu Feb 5 09:25:55 2009 From: lawrence.auster at att.net (Lawrence Auster) Date: Thu Feb 5 09:26:11 2009 Subject: Wealth of U.S.A. Plundered by Jews -- The Holocaust is Now Catholic Dogma -- Why No Neocon Assassinations? Message-ID: <20090205172553.MJQD23750.eastrmmtao107.cox.net@eastrmimpo03.cox.net> Wealth of U.S.A. Plundered by Jews Thursday, 05 February 2009 By Texe Marrs It's all over the media, how one Wall Street crook, Bernie Madoff, masterminded the greatest Ponzi scheme in history. Bernie ripped off investors to the tune of $50 billion, and they're still counting. Fifty billion! That's more than the current market value of General Motors, Disney, Boeing, and Anheuser-Busch combined. And just one solitary individual—a corrupt, money-grabbing Jew named "Madoff"—is the culprit. But, wait...hold on. Is this one crime the whole picture, the full extent of Wall Street's monumental scam and robbery extravaganza? Not by a long shot! Yes Virginia, There is a Santa Claus Citibank's Jewish money-shovelers stole some $200 billion—and then got the idiots at the U.S. Treasury to dole out some $160 billion of our—the suffering taxpayers—hard-earned money into their coffers. Yes, Virginia, there is a Santa Claus and his name is "Uncle Sam." America's banking industry is exclusively Jewish-run. The same goes for Wall Street brokerage and investment houses. Investigate for yourself and you'll discover that the New York-Chicago money crowd is nearly 100 percent Jews. They're the ones—these bamboozling and crafty, satanic Jews—who greedily have broken the backs of millions of bedraggled and unsuspecting American workers through their unparalleled lust for filthy lucre. Jesus told us this would be the case. He warned us in advance. He gave the Jews a choice: God or Mammon. They chose Mammon (i.e., money) and then added icing to their cake on earth by torturing, mocking, then finally nailing our Lord and Savior to a wooden cross. Oh, excuse me. The Jews didn't do it themselves. They never do. They got the Romans to do their dirty work. Pilate at first refused, until the Jews made it clear to the Roman Governor he better do their bidding, or else. Like today's miserly and cowardly politicians, Pilate caved in. Crucified on a Cross of Gold Now, it's America's turn to be crucified, on a cross of Jewish-owned gold. The Jews of Wall Street are the perps of this crucifixion. They run Wall Street, have their grimy hands all over our U.S. Treasury, force Congress to bow down and worship their murderous idol, "Israel," and then lie and cast blame elsewhere. Now Bernie Madoff, former chairman of the NASDAQ Stock Exchange, is only one of thousands of money manipulating Jewish thugs running loose in these 50 states—and they all have Gentile lackeys kissing their feet and mopping floors for them—men like George W. ("McMoron") Bush, Bill ("Bimbo") Clinton, and Vice President Joe ("Big Mouth Clown") Biden, just to name a few. But consider the damage that this one scheming Jew, Madoff, did and multiply that times, say, 100,000. Writing in the Business section of the Austin American-Statesman (December 28, 2008), news reporter Scott Burns commented on the Madoff robbery: "The loss is mind-boggling...One way to measure the extent of the damage is to compare the $50 billion to measures of loss in the FBI Uniform Crime Reports. In 2007 there were 9.8 million crimes against property in the United States. This included about 2.2 million burglaries, 6.6 million thefts, and 1.1 million car thefts. I think you'll agree that 9.8 million crimes represent a veritable army of miscreants. In spite of that, our total losses to such property crimes in 2007 throughout the entire United States were a mere $17.6 billion... But when you add up all the losses in 9.8 million common property crimes, it's just a fraction of the estimated $50 billion loss attributed to Madoff. Jews Also Behind the Most Inhumane, Bloody Crime in History Think of it. One evil Jew, Madoff, made off with a staggering total equal to somewhere near the losses of about 30 million crimes. There's more, of course. It's not just the money. The Jews are also behind the most sinister and bloody inhuman crime ever committed in the annals of human history—the Soviet Communist Holocaust. The late Aleksandr Solzhenitsyn, the 20th century's most acclaimed literary figure and historian, reported in his final book, Two Hundred Years Together, that the Jews were the revolutionary conspirators and mass murderers responsible for the Communist holocaust in which a mind-warping 66 million innocent victims were tortured, imprisoned in filthy, gruesome gulag camps and, finally, unmercifully executed. Lenin, Trotsky, Kaganovich—all these Communist monsters were Jews and their talmudic goal was a global Communist "Utopia," led, of course, exclusively by Zionist Jews. Allegedly—and I use that word advisedly—the Jews accuse Hitler and his Nazis of the murder of six million in the misnamed German "holocaust." Modern-day researchers, however, are discovering that this figure, six million, is grossly exaggerated so that Jews can appear as "victims" and thus continue incessantly to demand money and reparations from a clueless and guilt-filled Gentile world. 66 Million Butchered by Jews! Nevertheless, contrast this six million Jewish dead number to Solzhenitsyn's very accurate statistic of 66 million slain by the psychopathic Jewish Communists in the former Soviet Union. Many, if not most, of these victims were Christians. (Note: Jews were favored in the U.S.S.R. and synagogues were protected. Anti-Semitic "crimes"—even thought crimes—were met with death sentences by Jewish courts in the Soviet justice system). Tally it up: 66 million Christians slaughtered by the Jews, 6 million (allegedly) by the Nazis. That's eleven dead Christians for each and every Jew. The world has no sorrow for these 66 million dead, their survivors get no reparations, and their Jewish tormentors—including scores of Jewish Gulag Commandants—today remain free. Some live in luxury in Israel and pleasurably enjoy fat bank accounts, money plundered from hapless Christian victims. Barack Obama, America's First Jewish President The Jews did it to Russia, Ukraine, Georgia, Estonia, Kazakhstan, and all the other Communist prison nations. Now, in 2009, they're scheduled to do the same thing to the once, great U.S.A. Barack Obama—whom Chicago's wealthiest Jews boast is America's "First Jewish President"—is their chosen instrument. Wily, cunning, handsome, Obama has a cohort Jew to assist him in this assigned mission of human and national destruction. That would be Rahm "The Cruel" Emanuel, the Enforcer, the new White House Chief of Staff. Just for writing this article, I expect to be placed near the top of this wicked man's "Hit List." And I suspect there will be so many on this list that the White House and its Homeland Security Department will need a whole warehouse full of computers just to store all the millions of names. FDR had his "New Deal;" today, in 2009, Barack Hussein Obama and his Trotskyite, left-hand lieutenant, the beady-eyed Israeli dual citizen, "Rahm the Cruel," have in mind the "Jew Deal." The goal: The Sovietization of America, the extinguishing of our historic Bill of Rights, the end of U.S. sovereignty, and the death of multitudes who will refuse to bow down to the ruthless tyrants who wear the six-pointed Red Star in their hearts like a dagger. "If You Can, Come and Take It" Our enemies, regrettably, occupy the highest offices in the land. But they don't have everything they desire and lust for. They don't have the fawning allegiance and docile service of you, me, and thousands of other patriots who bravely oppose their black-hearted plot. I am not, by nature, a violent man, and I pray fervently for peace and harmony to prevail. I pray, too, that the schemes of the Zionist Jews plotting against America will fail, that our Constitution will be respected and that the corrupt money-thieves on Wall Street and elsewhere will soon be outed and put in prisons, where they belong. But if not, then I say, let us fight for the right. Here we stand, by virtue of Truth and Justice, and I say to Obama, Emanuel, and the other Zionist traitors: "Here we are; if you can, come and take it, but know this: You have a fight on your hands, because we will not go quietly out into that soft, sweet night. And believe me, you can take that, along with your ill-begotten gains, to the bank." Source : http://ziopedia.org/articles/jewry/wealth_of_u.s.a._plundered_by_jews/ ----<>---- The Holocaust is Now Catholic Dogma Thursday, 05 February 2009 By Mark Glenn The last time a Pope of the Catholic Church defined an infallible dogma was in the year 1950. Pope Pius XII used this power reserved for the Vicar of Christ when speaking ex cathedra to define the Dogma of the Assumption of Mary. It was an extraordinary event because a pope using the power of infallibly to define a dogma is done so rarely, and most popes have never used this power. Before Pius XII, the last pope to invoke papal infallibly to define a dogma was Pius IX in 1854, when he defined the Dogma of the Immaculate Conception. Both of these dogmas referred to events that had occurred 19 centuries before , and that had been studied by the best minds of the Church for almost as long. That’s because when making an infallible statement - it goes without saying - it can’t contain any errors! Fast forward to 2009 and Pope Benedict XVI has just defined a new dogma regarding a secular event that has nothing to do with the Faith. Moreover, this ‘dogmatic event’ only occurred in the middle of the 20th Century- and no one is allowed to investigate to see if it contains any errors! A dogma is an infallible teaching of the Catholic Church that must be believed by every Catholic or they’re not in communion with the Church. In the past, a dogma referred only to a matter of Christian faith, and Catholics could believe whatever they wanted about historical events. But today’s remarks from the Vatican make it clear that the Jewish version of the Holocaust, in which 6 million Jews were killed in gas chambers, must be believed by every Catholic or they’re not in communion with the Church. That makes the Holocaust an official ‘dogma’ of the Catholic Faith (*sarcasm*). Here’s the news out of the Vatican. On Jan. 28, the pope said he felt “full and indisputable solidarity” with Jews, and warned against any denial of the full horror of the Nazi genocide. Bishop Williamson, in order to be admitted to episcopal functions within the church, will have to take his distance, in an absolutely unequivocal and public fashion, from his position on the Shoah, which the Holy Father was not aware of when the excommunication was lifted,” the statement said. The Shoah is the Hebrew term for the Holocaust. Jewish groups welcomed the Vatican statement, saying it satisfied their key demand. “This was the sign the Jewish world has been waiting for,” said Ronald Lauder, president of the World Jewish Congress. Yes, this is the sign the Jewish world has been waiting for, but what exactly does this “sign” really mean? It means that in the post-Vatican II Church, the “Shoah” has replaced the Crucifixion as the central event in history. And do you notice the subtle switcheroo here? Now, instead of the central tenet of the Christian faith pertaining to the murder of the Christ by Jews, the new central tenet refers to the murder of Jews by Christians! This should come as no surprise to those who understand what really lies at the heart of the problem. At its core, this is a spiritual battle that’s being waged above our heads. It’s Christ vs. anti-Christ, and each of us must choose a side. Lucifer wanted to be equal to God and out of pride refused to accept being a servant. When he uttered his famous “non servium” he took a third of the angels with him and set about waging war against God. When God sent His Son to redeem the world, Lucifer tried to prevent it. He took Jesus to the mountain top and tempted Him, saying “if you just bow down and worship me, I will give you all these things.” Jesus told the devil to buzz off. The Jews who rejected Jesus as the Messiah did so out of racial pride and ambition. They wanted an earthly kingdom where they would always be the ‘Chosen Ones’ and did not want to share a kingdom with the gentiles. But Jesus emphatically said that His kingdom was not of this world and to share the good news with the gentiles. The Jews who accepted the Messiah became the first Christians, and those who rejected Him fell into spiritual blindness. Satan takes advantage of Jewish hatred of Jesus and uses them to battle against the Church of Christ. The Jews continue to wait for a wordly Messiah, but the Messiah they await is known to us as the anti-Christ. Therefore, all Christians must love and pray for the Jewish people to accept Christ as the Messiah, thereby snatching them from the jaws of Satan, whom they don’t realize they are serving. This battle between Christ and anti-Christ is 2,000 years old and all popes throughout history have waged it (at least until 1958). That’s what makes the Church’s post-Vatican II attitude toward the Jews so perplexing, since it enables them to continue in spiritual blindness and sets the stage for the coming of the anti-Christ. Pope Leo XIII had a vision at the end of the 19th Century in which he forsaw that the devil had been given extra powers for 100 years to try to destroy the Church. This seems to coincide with the shift in power that took place in the 20th Century when after two world wars, the Jews took Palestine and solidified their control over the West. This was also the century in which the Jews unleashed their most deadly weapon, Communism, which caused the deaths of millions of people. But these people’s genocides go unnoticed and certainly have not been declared ”dogma” by a pope of the Catholic Church. Another clue that something is amiss inside the Church is that the Second Vatican Council refused to condemn Communism, but declared that anti-Semitism was a sin (without defining what constitutes anti-Semitism). Enter Archbishop Marcel Lefebvre, the Society of St. Pius X (SSPX), and the man who’s currently being crucified, Bishop Richard Williamson. Archbishop Lefebvre himself had fought inside the Second Vatican Council to prevent the coup of the liberals. He also stated that the mere fact that the Council refused to condemn Communism was enough to call the Council into question. The Archbishop knew that something nefarious had happened inside the Church and sensed that he was waging a battle against powers and principalities. In terms of his plans to restore Tradition, in the Biography of Marcel Lefebvre by Bishop Tissier de Mallerais, he quotes the Archbishop as saying (pp. 500-501): The Council is a non-infallible act of the Magisterium and, therefore, it is open to being influenced by a bad spirit … Therefore, we need to apply the criterion of Tradition to the various Council documents to see what we can keep, what needs clarifying, and what should be rejected. And that’s exactly the whole point of the negotiations between the SSPX and the Vatican that have been going on for almost 40 years. After the release of the Latin Mass and the lifting of the excommunications, the next phase is doctrinal discussions. But somebody doesn’t want that to happen. Archbishop Lefebvre founded the SSPX in 1970 in order to train priests in Tradition and not in the confusing, untraditional, Judeo-Masonic manner of the post-Conciliar era. The greatest threat to Revolutionaries is those who are not afraid to resist them to the face, i.e., the Counter-Revolutionaries. That is why Pope John Paul II would not allow Archbishop Lefebvre to consecrecate bishops, something that is usually rubber-stamped for every other order. John Paul II wanted the SSPX to go extinct after the death of its founder and put a stop to the Counter-Revolution. And if the Council really was influenced by a “bad spirit” as the Archbishop said, then certainly any attempt to exorcise this bad spirit would be met with the fiercest resistance by those who work for the anti-Christ. This is where the controversy over Bishop Williamson’s remarks about the actual number of Jews killed in the Holocaust comes into the scenario. If the Jews are (wittingly or unwittingly) working to bring about the reign of the anti-Christ, then part of their strategy has to be to neutralize the Church. In their effort to overturn the crucifixion and replace it with the “Shoah,” they’re trying to utilize the Church to bring this about. And any force that appears to provide resistance to this switcheroo will be seen as the gravest possible threat. Because truly, it wouldn’t have mattered if Bishop Williamson had not said a word about the Shoah, they would have found something else to try to impede the Church’s return to Tradition. Because Christ and anti-Christ cannot co-exist on equal terms - one must naturally dominate the other. And the Church returning to Tradition and her normal role as the Church Militant is the one monkey wrench that could be thrown into the plans of the anti- Christ. No other challenger intimidates them, absolutely no one else causes them to tremble. But a fully traditional Church Militant with a billion souls in her army is the one thing that could defeat their plans. And that’s what this is really all about. Bishop Williamson now finds himself in the center of a controvery that has been coming to a head for a very long time. In perusing the Catholic blogosphere, it appears that most Catholics (even trads) wish that he had just kept his mouth shut. But they would probably have said the same thing to Jesus, so as not to annoy the Pharisees. But I’m convinced Our Lord Jesus Christ knows what he is doing. Because it is time to confront the truth, as the the hour glass of time winds down, and get ready for the final conflagration. But it appears most Christians would rather retreat to the hills, rather than risk not being popular with the world. Thankfully, for the sake of our salvation, Jesus Himself was not so pusillanimous. And hopefully Bishop Williamson won’t be so pusillanimous either, since his founder, Archbishop Marcel Lefebvre, most assuredly was not. The Archbishop personally chose Richard Williamson to carry on his work after his death, to be a successor to the apostles. The only question that remains is: will he be like St. John or like the others who abandoned Jesus ”for fear of the Jews.’ The Church and the Jews have been locked in this battle for 2,000 years, so this latest controversy is nothing to be surprised about. Satan uses the poor, blinded Jews to attack the Lord’s Church because he doesn’t want us or them to be saved. But at least in the past, it used to be clear which side the popes were on! The Pope and SSPX bishops need all our prayers and support right now, because they are going through a trial by fire. And, at least in this early stage, it appears Bishop Fellay is starting to get cold feet. Every day for the past several days he has issued a denunciation of his colleague, Bishop Williamson, each one more hysterical than the last. He even went so far as to refer to the Jews as our “elder brothers in the faith,” as though the Talmud has anything to do with our Faith. When I said last week that I wished Bishop Fellay would one day be pope, I didn’t mean in the mold of John Paul II! Let us pray especially for Pope Benedict XVI, the keeper of the keys to heaven, that he prove himself a worthy successor of St. Peter, and that he not imitate Peter in his denial of Jesus Christ. Archbishop Lefebvre recognized that the day would come when the SSPX would be called on to save the Church. And judging by the howls and screams from the satanic press, that day might be just around the corner. Let us hope that we also have the courage to stand beside them, no matter how much the media attack and lambaste us. It’s for the Jews’ own good after all, for they know not whom they are serving. As the Archbishop wrote in 1966 (ibid, pp. 382-83): When the Holy Father realizes that those whom he trusted are leading the Church to her ruin, he will find himself a group of bishops … who are ready to rebuild. Unfortunately, the time has not yet come, because the Holy Father himself must change what he is doing, and that conversion will be painful. Let us hope that the time has come and that Pope Benedict will accept the help of the SSPX. It is time for the Holy Father to stop taking sides with the enemies of the Church and stop defining secular events as “dogma,” especially ones so riddled through with holes. May God save the Church through His servant, Pope Benedict, although the Pope’s conversion will be painful. Source : http://ziopedia.org/articles/holocaust/the_holocaust_is_now_catholic_dogma/ ----<>---- Why No Neocon Assassinations? Because The War On Terror Is A Hoax February 03, 2009 By Paul Craig Roberts According to US government propaganda, terrorist cells are spread throughout America, making it necessary for the government to spy on all Americans and violate most other constitutional protections. Among President Bush’s last words as he left office was the warning that America would soon be struck again by Muslim terrorists. If America were infected with terrorists, we would not need the government to tell us. We would know it from events. As there are no events, the US government substitutes warnings in order to keep alive the fear that causes the public to accept pointless wars, the infringement of civil liberty, national ID cards, and inconveniences and harassments when they fly. The most obvious indication that there are no terrorist cells is that not a single neocon has been assassinated. I do not approve of assassinations, and am ashamed of my country’s government for engaging in political assassination. The US and Israel have set a very bad example for al Qaeda to follow. The US deals with al Qaeda and Taliban by assassinating their leaders, and Israel deals with Hamas by assassinating its leaders. It is reasonable to assume that al Qaeda would deal with the instigators and leaders of America’s wars in the Middle East in the same way. Today every al Qaeda member is aware of the complicity of neoconservatives in the death and devastation inflicted on Muslims in Iraq, Afghanistan, Lebanon and Gaza. Moreover, neocons are highly visible and are soft targets compared to Hamas and Hezbollah leaders. Neocons have been identified in the media for years, and as everyone knows, multiple listings of their names are available online. Neocons do not have Secret Service protection. Dreadful to contemplate, but it would be child’s play for al Qaeda to assassinate any and every neocon. Yet, neocons move around freely, a good indication that the US does not have a terrorist problem. If, as neocons constantly allege, terrorists can smuggle nuclear weapons or dirty bombs into the US with which to wreak havoc upon our cities, terrorists can acquire weapons with which to assassinate any neocon or former government official. Yet, the neocons, who are the Americans most hated by Muslims, remain unscathed. The "war on terror" is a hoax that fronts for American control of oil pipelines, the profits of the military-security complex, the assault on civil liberty by fomenters of a police state, and Israel’s territorial expansion. There were no al Qaeda in Iraq until the Americans brought them there by invading and overthrowing Saddam Hussein, who kept al Qaeda out of Iraq. The Taliban is not a terrorist organization, but a movement attempting to unify Afghanistan under Muslim law. The only Americans threatened by the Taliban are the Americans Bush sent to Afghanistan to kill Taliban and to impose a puppet state on the Afghan people. Hamas is the democratically elected government of Palestine, or what little remains of Palestine after Israel’s illegal annexations. Hamas is a terrorist organization in the same sense that the Israeli government and the US government are terrorist organizations. In an effort to bring Hamas under Israeli hegemony, Israel employs terror bombing and assassinations against Palestinians. Hamas replies to the Israeli terror with homemade and ineffectual rockets. Hezbollah represents the Shi’ites of southern Lebanon, another area in the Middle East that Israel seeks for its territorial expansion. The US brands Hamas and Hezbollah "terrorist organizations" for no other reason than the US is on Israel’s side of the conflict. There is no objective basis for the US Department of State’s "finding" that Hamas and Hezbollah are terrorist organizations. It is merely a propagandistic declaration. Americans and Israelis do not call their bombings of civilians terror. What Americans and Israelis call terror is the response of oppressed people who are stateless because their countries are ruled by puppets loyal to the oppressors. These people, dispossessed of their own countries, have no State Departments, Defense Departments, seats in the United Nations, or voices in the mainstream media. They can submit to foreign hegemony or resist by the limited means available to them. The fact that Israel and the United States carry on endless propaganda to prevent this fundamental truth from being realized indicates that it is Israel and the US that are in the wrong and the Palestinians, Lebanese, Iraqis, and Afghans who are being wronged. The retired American generals who serve as war propagandists for Fox "News" are forever claiming that Iran arms the Iraqi and Afghan insurgents and Hamas. But where are the arms? To deal with American tanks, insurgents have to construct homemade explosive devices out of artillery shells. After six years of conflict the insurgents still have no weapon against the American helicopter gunships. Contrast this "arming" with the weaponry the US supplied to the Afghans three decades ago when they were fighting to drive out the Soviets. The films of Israel’s murderous assault on Gaza show large numbers of Gazans fleeing from Israeli bombs or digging out the dead and maimed, and none of these people are armed. A person would think that by now every Palestinian would be armed, every man, woman, and child. Yet, all the films of the Israeli attack show an unarmed population. Hamas has to construct homemade rockets that are little more than a sign of defiance. If Hamas were armed by Iran, Israel’s assault on Gaza would have cost Israel its helicopter gunships, its tanks, and hundreds of lives of its soldiers. Hamas is a small organization armed with small caliber rifles incapable of penetrating body armor. Hamas is unable to stop small bands of Israeli settlers from descending on West Bank Palestinian villages, driving out the Palestinians, and appropriating their land. The great mystery is: why after 60 years of oppression are the Palestinians still an unarmed people? Clearly, the Muslim countries are complicit with Israel and the US in keeping the Palestinians unarmed. The unsupported assertion that Iran supplies sophisticated arms to the Palestinians is like the unsupported assertion that Saddam Hussein had weapons of mass destruction. These assertions are propagandistic justifications for killing Arab civilians and destroying civilian infrastructure in order to secure US and Israeli hegemony in the Middle East. Source : http://vdare.com/roberts/090203_terror.htm ------------------------------------- You or someone using your email adress is currently subscribed to the Lawrence Auster Newletter. If you wish to unsubscribe from our mailing list, please let us know by calling "to 1 212 865 1284 Thanks, Lawrence Auster, 238 W 101 St Apt. 3B New York, NY 10025 Contact: lawrence.auster@att.net ------------------------------------- From hselasky at c2i.net Thu Feb 5 10:25:43 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Feb 5 10:25:49 2009 Subject: [WAS: Spam from Lawrence Auster] In-Reply-To: <20090205172553.MJQD23750.eastrmmtao107.cox.net@eastrmimpo03.cox.net> References: <20090205172553.MJQD23750.eastrmmtao107.cox.net@eastrmimpo03.cox.net> Message-ID: <200902051928.04920.hselasky@c2i.net> Hi, Has someone tried calling this guy? I "think" his Microsoft Server might be hacked or someone has put freebsd lists up there for fun? Am I right that this is the originating IP: telnet ip72-196-247-230.dc.dc.cox.net 23 +Phone: "1 212 865 1284" seems valid. Maybe some new-yorkers should call this guy and ask if he wants to pay for a FreeBSD server and write articles about Operating systems instead :-) That would be really cool :-) --HPS PS: http://www.nycbug.org/ From hselasky at c2i.net Thu Feb 5 14:16:44 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Feb 5 14:16:51 2009 Subject: [WAS: Spam from Lawrence Auster] In-Reply-To: <200902051928.04920.hselasky@c2i.net> References: <20090205172553.MJQD23750.eastrmmtao107.cox.net@eastrmimpo03.cox.net> <200902051928.04920.hselasky@c2i.net> Message-ID: <200902052319.03526.hselasky@c2i.net> Sorry about the previous e-mail. --HPS From a182ot at gmail.com Thu Feb 5 21:46:24 2009 From: a182ot at gmail.com (Alexander Usov) Date: Thu Feb 5 21:46:30 2009 Subject: bge0 performance and bge1 media problem on Asus RS100-E5-PI2 Message-ID: <303e29800902052130j52680d6ep56ce67f0a27ce257@mail.gmail.com> $uname -a FreeBSD DHCP10 7.1-STABLE FreeBSD 7.1-STABLE #1: Tue Jan 20 12:59:59 UTC 2009 root@dhcp10:/usr/obj/usr/src/sys/DHCP amd64 $ pciconf -lv | grep -A 3 bge bge0@pci0:3:0:0: class=0x020000 card=0x81491043 chip=0x165914e4 rev=0x21 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5721 NetXtreme Gigabit Ethernet PCI Express' class = network -- bge1@pci0:2:0:0: class=0x020000 card=0x81491043 chip=0x165914e4 rev=0x21 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5721 NetXtreme Gigabit Ethernet PCI Express' class = network # iperf -s -p 1111 ------------------------------------------------------------ Server listening on TCP port 1111 TCP window size: 64.0 KByte (default) ------------------------------------------------------------ [ 4] local 10.100.30.7 port 1111 connected with 10.100.30.8 port 58205 [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.2 sec 622 MBytes 509 Mbits/sec [ 5] local 10.100.30.7 port 1111 connected with 10.100.30.8 port 52206 [ ID] Interval Transfer Bandwidth [ 5] 0.0-18.1 sec 1.07 GBytes 509 Mbits/sec [ 4] local 10.100.30.7 port 1111 connected with 10.100.30.8 port 62863 [ ID] Interval Transfer Bandwidth [ 4] 0.0-184.4 sec 10.9 GBytes 509 Mbits/sec I use ULE and BSD with/without polling, but i can transmit at ~509 Mbits/sec bge1 forced only 100baseTX duplex-full... bge1 forced 1000baseTX duplex-full From sepherosa at gmail.com Thu Feb 5 23:20:06 2009 From: sepherosa at gmail.com (Sepherosa Ziehau) Date: Thu Feb 5 23:20:12 2009 Subject: bge0 performance and bge1 media problem on Asus RS100-E5-PI2 In-Reply-To: <303e29800902052130j52680d6ep56ce67f0a27ce257@mail.gmail.com> References: <303e29800902052130j52680d6ep56ce67f0a27ce257@mail.gmail.com> Message-ID: On Fri, Feb 6, 2009 at 1:30 PM, Alexander Usov wrote: > $uname -a > FreeBSD DHCP10 7.1-STABLE FreeBSD 7.1-STABLE #1: Tue Jan 20 12:59:59 UTC > 2009 root@dhcp10:/usr/obj/usr/src/sys/DHCP amd64 > > $ pciconf -lv | grep -A 3 bge > bge0@pci0:3:0:0: class=0x020000 card=0x81491043 chip=0x165914e4 rev=0x21 > hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM5721 NetXtreme Gigabit Ethernet PCI Express' > class = network > -- > bge1@pci0:2:0:0: class=0x020000 card=0x81491043 chip=0x165914e4 rev=0x21 > hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM5721 NetXtreme Gigabit Ethernet PCI Express' > class = network > > # iperf -s -p 1111 > ------------------------------------------------------------ > Server listening on TCP port 1111 > TCP window size: 64.0 KByte (default) > ------------------------------------------------------------ > [ 4] local 10.100.30.7 port 1111 connected with 10.100.30.8 port 58205 > [ ID] Interval Transfer Bandwidth > [ 4] 0.0-10.2 sec 622 MBytes 509 Mbits/sec > [ 5] local 10.100.30.7 port 1111 connected with 10.100.30.8 port 52206 > [ ID] Interval Transfer Bandwidth > [ 5] 0.0-18.1 sec 1.07 GBytes 509 Mbits/sec > [ 4] local 10.100.30.7 port 1111 connected with 10.100.30.8 port 62863 > [ ID] Interval Transfer Bandwidth > [ 4] 0.0-184.4 sec 10.9 GBytes 509 Mbits/sec > > I use ULE and BSD with/without polling, but i can transmit at ~509 Mbits/sec > > bge1 forced only 100baseTX duplex-full... bge1 forced 1000baseTX duplex-full I had a patch for PCIE bge(4) to improve TX performance, you could give it a try (you may need to hand patch it, since the patch itself is quite old, back to mid 2008) http://people.freebsd.org/~sephe/bge.diff Best Regards, sephe -- Live Free or Die From todorov at paladin.bulgarpress.com Fri Feb 6 15:59:01 2009 From: todorov at paladin.bulgarpress.com (Todorov) Date: Fri Feb 6 15:59:19 2009 Subject: Opteron Quad vs Xeon Quad Message-ID: <498CCAE8.3090504@paladin.bulgarpress.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, I'm planning to buy two servers running FBSD AMD64, PostgreSQL, Diablo Java, Tomcat. 3Ware SAS RAID + Supermicro mainboards 1.Opteron 2354 2.2GHz + Supermicro AS-2021M-UR+, MB H8DMU+ nVidia MCP55 Pro Chipset 2.Xeon E5420 2.5 GHz + Supermicro X7DWU, Dual Intel Xeon1600 MHz FSB; Intel Seaburg chipset I have few questions - are the NVidia chipsets stable enough and performance good? In the internet I've read a lot of opinions that Java+Opteron and PGSQL+Opteron goes together :) I will appreciate opinions - no flame to start - I've said what is my target as usage. So I asked specific question.. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmMyucACgkQibJkIG65HMcf4wCggY5SS0MtmQjPiwv9aqHIpwkO G64AnjxDZCH2xD4pyB1wPw9m8bkr1JG4 =WYmr -----END PGP SIGNATURE----- From terbut at sprint.net.au Fri Feb 6 23:35:50 2009 From: terbut at sprint.net.au (Andrew and Faye Butler) Date: Fri Feb 6 23:35:57 2009 Subject: Compaq evo "BTX Halted" error solution Message-ID: <61167.138.217.111.221.1233990447.squirrel@webmail.eftel.com.au> Hi Omar Revueltas, Thank you for the solution to the: Compaq evo "BTX Halted" error. It worked for me 100% Just: - [F10] to get in to the BIOS then select - Storage - Device Configuration - CD-ROM - Transfer Mode and change setting to = Max PIO Save and Reboot the machine and I was cooking. Thanks again. Andrew Butler -- "you always have to start with the ambition of winning" From onemda at gmail.com Mon Feb 9 15:43:28 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Mon Feb 9 15:50:56 2009 Subject: ipw3945 problems In-Reply-To: References: Message-ID: <3a142e750902091513h745bf9ah7b33f456a8580b95@mail.gmail.com> On 2/4/09, Andreas Nilsson wrote: > Hi, > > I've been experiencing some weird behavior with the ipw3945 on my laptop > running FreeBSD 7.1-RELEASE. When running on AC the card works as expected, > but when running unplugged the interface keeps going down and up and down. I > get ~10 consecutive pings before it goes down. > > The networks I have tested are encrypted with some WPA protocol. > > When starting on battery there are also some other strange behavior, there > are some lock-ups in the gui and xorg uses some 14% cpu @1.2GHz doing > nothing, When the mouse has been idle for some seconds it takes a bit of > movement to activate again. After a plug and unplug of the AC everything > seems to work as it is supposed to. > > I realize this isn't very much to go on... Any logs that would help? > > The laptop in question is a Lenovo Thinkpad t61p. > > Best regards > Andreas Nilsson > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > Are you using powerd? Perhaps CPU cx states are changed? -- Paul From andrnils at gmail.com Tue Feb 10 00:40:44 2009 From: andrnils at gmail.com (Andreas Nilsson) Date: Tue Feb 10 00:40:51 2009 Subject: ipw3945 problems In-Reply-To: <3a142e750902091513h745bf9ah7b33f456a8580b95@mail.gmail.com> References: <3a142e750902091513h745bf9ah7b33f456a8580b95@mail.gmail.com> Message-ID: On Tue, Feb 10, 2009 at 12:13 AM, Paul B. Mahol wrote: > On 2/4/09, Andreas Nilsson wrote: > > Hi, > > > > I've been experiencing some weird behavior with the ipw3945 on my laptop > > running FreeBSD 7.1-RELEASE. When running on AC the card works as > expected, > > but when running unplugged the interface keeps going down and up and > down. I > > get ~10 consecutive pings before it goes down. > > > > The networks I have tested are encrypted with some WPA protocol. > > > > When starting on battery there are also some other strange behavior, > there > > are some lock-ups in the gui and xorg uses some 14% cpu @1.2GHz doing > > nothing, When the mouse has been idle for some seconds it takes a bit of > > movement to activate again. After a plug and unplug of the AC everything > > seems to work as it is supposed to. > > > > I realize this isn't very much to go on... Any logs that would help? > > > > The laptop in question is a Lenovo Thinkpad t61p. > > > > Best regards > > Andreas Nilsson > > _______________________________________________ > > freebsd-hardware@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > > To unsubscribe, send any mail to " > freebsd-hardware-unsubscribe@freebsd.org" > > > > Are you using powerd? Perhaps CPU cx states are changed? > > -- > Paul > I am using powerd, and CPU cx states are probably beeing changed. I set the corresponding tunables to allow the CPUs (cores) to reach C3. Before I started using C3 on a regular basis I did some tesing and I didn't notice any difference in connectivity. When running on AC the connection works for a while ( a random amount of time ) , but then the carrier is lost. When running in school I get really low transfer speed, somewhere around 200Kb/s from a computer in a room next door. When running on linux I get around 1+Mb/s from the same computer. Best regards Andreas Nilsson From nicolas at goralski.fr Tue Feb 10 01:01:03 2009 From: nicolas at goralski.fr (Nicolas GORALSKI) Date: Tue Feb 10 01:01:10 2009 Subject: Looking for ethernet expresscard Message-ID: Hi everybody I've a laptop with a sis191 ethernet card and it doesn't work. NDIS with (XP|2K|98) drivers make my kernel crash. So i was thinking about an network expresscard. Does anybody know about a model that will work ? From olli at lurza.secnetix.de Wed Feb 11 00:33:40 2009 From: olli at lurza.secnetix.de (Oliver Fromme) Date: Wed Feb 11 00:33:47 2009 Subject: SATA PCI adapter recommendation Message-ID: <200902110833.n1B8XbLo096837@lurza.secnetix.de> Hi, I plan to put a SATA drive in an old PATA-only PC, so I'm looking for an appropriate adapter card. A cheap card should suffice, I do not need RAID, and it does not have to be SATA-300. (This machine has only standard PCI slots anyway, so it wouldn't be able to saturate SATA-300.) I'm currently looking at these, all of which are about 20 Euro around here: 1. Based on Silicon Image Sil-3x12 chip: http://www.digital-data.de/download/datasheets/111816_Datasheet.pdf 2. Based on Initio INIC1620 chip: http://www.digital-data.de/download/datasheets/111817_Datasheet.pdf 3. Some VIA chip (probably VT6421A, but not 100% clear): http://www.delock.de/view/pdf/70156/A/1943/ I've read a few scary things about SIL chips on the lists, so I guess I'd better try to avoid that one. But how about the Initio and VIA ones? Do they work well with FreeBSD? Any good or bad experiences? Finally, a small question: I assume that all of those SATA controllers do have their own BIOS, so I can boot from them, right? It would be annoying to have to keep an old PATA disk in that box just to be able to boot. Thanks! 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 "Perl will consistently give you what you want, unless what you want is consistency." -- Larry Wall From ricardo.meb.jesus at gmail.com Wed Feb 11 02:15:12 2009 From: ricardo.meb.jesus at gmail.com (Ricardo Jesus) Date: Wed Feb 11 02:15:19 2009 Subject: SATA PCI adapter recommendation In-Reply-To: <200902110833.n1B8XbLo096837@lurza.secnetix.de> References: <200902110833.n1B8XbLo096837@lurza.secnetix.de> Message-ID: <49929DE2.6070200@gmail.com> Oliver Fromme wrote: > Hi, > > I plan to put a SATA drive in an old PATA-only PC, so I'm > looking for an appropriate adapter card. A cheap card > should suffice, I do not need RAID, and it does not have > to be SATA-300. (This machine has only standard PCI slots > anyway, so it wouldn't be able to saturate SATA-300.) > > I'm currently looking at these, all of which are about > 20 Euro around here: > > 1. Based on Silicon Image Sil-3x12 chip: > http://www.digital-data.de/download/datasheets/111816_Datasheet.pdf > > 2. Based on Initio INIC1620 chip: > http://www.digital-data.de/download/datasheets/111817_Datasheet.pdf > > 3. Some VIA chip (probably VT6421A, but not 100% clear): > http://www.delock.de/view/pdf/70156/A/1943/ > > I've read a few scary things about SIL chips on the lists, > so I guess I'd better try to avoid that one. > But how about the Initio and VIA ones? Do they work well > with FreeBSD? Any good or bad experiences? > > Finally, a small question: I assume that all of those > SATA controllers do have their own BIOS, so I can boot > from them, right? It would be annoying to have to keep > an old PATA disk in that box just to be able to boot. > > Thanks! > > Best regards > Oliver > I have a SATA card with the Initio1662 chip and it isn't supported, which is a shame :( From markir at paradise.net.nz Wed Feb 11 02:47:15 2009 From: markir at paradise.net.nz (Mark Kirkwood) Date: Wed Feb 11 02:47:22 2009 Subject: SATA PCI adapter recommendation In-Reply-To: <200902110833.n1B8XbLo096837@lurza.secnetix.de> References: <200902110833.n1B8XbLo096837@lurza.secnetix.de> Message-ID: <4992A928.6080308@paradise.net.nz> Oliver Fromme wrote: > Hi, > > I plan to put a SATA drive in an old PATA-only PC, so I'm > looking for an appropriate adapter card. A cheap card > should suffice, I do not need RAID, and it does not have > to be SATA-300. (This machine has only standard PCI slots > anyway, so it wouldn't be able to saturate SATA-300.) > > I'm currently looking at these, all of which are about > 20 Euro around here: > > 1. Based on Silicon Image Sil-3x12 chip: > http://www.digital-data.de/download/datasheets/111816_Datasheet.pdf > > 2. Based on Initio INIC1620 chip: > http://www.digital-data.de/download/datasheets/111817_Datasheet.pdf > > 3. Some VIA chip (probably VT6421A, but not 100% clear): > http://www.delock.de/view/pdf/70156/A/1943/ > > I've read a few scary things about SIL chips on the lists, > so I guess I'd better try to avoid that one. > But how about the Initio and VIA ones? Do they work well > with FreeBSD? Any good or bad experiences? > > Finally, a small question: I assume that all of those > SATA controllers do have their own BIOS, so I can boot > from them, right? It would be annoying to have to keep > an old PATA disk in that box just to be able to boot. > > I'd forget those and buy a 3ware card - supported and reliable. Possibly a little more expensive... but they are available 2nd hand on ebay, which should help: http://cgi.ebay.com/hardware-raid-card-3ware-8006-2LP-2-port-SATA-RAID_W0QQitemZ140300178432QQcmdZViewItemQQptZPCC_Drives_Storage_Internal?hash=item140300178432&_trksid=p3286.c0.m14&_trkparms=72%3A1234|66%3A2|65%3A12|39%3A1|240%3A1318|301%3A0|293%3A1|294%3A50 regards Mark From om-lists-bsd at omx.ch Wed Feb 11 07:18:15 2009 From: om-lists-bsd at omx.ch (Olivier Mueller) Date: Wed Feb 11 07:18:23 2009 Subject: poweredge 1850 won't boot 7.1? maybe LSI-related : amr0: adapter is busy Message-ID: <1234363891.15909.35.camel@ompc.insign.local> Hello, This afternoon I wanted to upgrade to 7.1 two good old dell PowerEdge servers which were running FreeBSD 6.x. It went fine and quickly on the poweredge 1950, but it failed completely on the poweredge 1850. Facts: - boot cd and setup / operation of freebsd 6.x or 7.0 is fine Message log abstract: $ uname -v FreeBSD 7.0-RELEASE-p7 #0: Sun Dec 21 08:31:52 UTC 2008 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC $ dmesg|grep amr amr0: mem 0xd80f0000-0xd80fffff,0xdfde0000-0xdfdfffff irq 46 at device 14.0 on pci2 amr0: Using 64-bit DMA amr0: [ITHREAD] amr0: delete logical drives supported by controller amr0: Firmware 521X, BIOS H430, 256MB RAM amr0: delete logical drives supported by controller amrd0: on amr0 amrd0: 69880MB (143114240 sectors) RAID 1 (optimal) Trying to mount root from ufs:/dev/amrd0s1a - boot cd of 7.1 fails because the installed doesn't see any harddisk. Message log abstract: amr0: adapter is busy amr0: adapter is busy amr0: delete logical drives supported by controller I also tried to setup 7.0, and then upgrade to 7.1 with freebsd-update, but then it fails exactly like with the 7.1 boot CD (7.1-RELEASE-amd64-disc1.iso). Screenshot: http://omx.ch/om/stuff/pe1850bsd71error.jpg BIOS Message about the Controller on system startup: PowerEdge Expandable RAID COntroller BIOS, (c) 2006 LSI Logic Corporation I'm not sure what I can try next... I'd still like to be able to run 7.1 on this host as well as on several other old but still fine 1850. Is my system simply too old? Why is my adapter "busy" under 7.1? What would you try? I checked the relnotes as well, but saw nothing helpful about my problem there. regards & thanks in advance for any feedback, Olivier From lavalamp at spiritual-machines.org Wed Feb 11 07:54:08 2009 From: lavalamp at spiritual-machines.org (Brian A. Seklecki) Date: Wed Feb 11 07:54:15 2009 Subject: poweredge 1850 won't boot 7.1? maybe LSI-related : amr0: adapter is busy In-Reply-To: <1234363891.15909.35.camel@ompc.insign.local> References: <1234363891.15909.35.camel@ompc.insign.local> Message-ID: <1234366709.3500.62.camel@ingress.ws.pitbpa0.priv.collaborativefusion.com> On Wed, 2009-02-11 at 15:51 +0100, Olivier Mueller wrote: > Hello, > This afternoon I wanted to upgrade to 7.1 two good old dell PowerEdge > servers which were running FreeBSD 6.x. It went fine and quickly on the There's already discussion about this in the archives. We're aware and working on it. Set: /boo/loader.conf kern.cam.scsi_delay=20000 As a work-around for now. Tracking the megarc memory corruption (and general amr(4) problems with the PERC4) at: http://www.freebsd.org/cgi/query-pr.cgi?pr=128082 ~BAS > poweredge 1950, but it failed completely on the poweredge 1850. > > Facts: > > - boot cd and setup / operation of freebsd 6.x or 7.0 is fine > Message log abstract: > $ uname -v > FreeBSD 7.0-RELEASE-p7 #0: Sun Dec 21 08:31:52 UTC 2008 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC > $ dmesg|grep amr > amr0: mem 0xd80f0000-0xd80fffff,0xdfde0000-0xdfdfffff irq 46 at device 14.0 on pci2 > amr0: Using 64-bit DMA > amr0: [ITHREAD] > amr0: delete logical drives supported by controller > amr0: Firmware 521X, BIOS H430, 256MB RAM > amr0: delete logical drives supported by controller > amrd0: on amr0 > amrd0: 69880MB (143114240 sectors) RAID 1 (optimal) > Trying to mount root from ufs:/dev/amrd0s1a > > - boot cd of 7.1 fails because the installed doesn't see any harddisk. > Message log abstract: > amr0: adapter is busy > amr0: adapter is busy > amr0: delete logical drives supported by controller > > > I also tried to setup 7.0, and then upgrade to 7.1 with freebsd-update, > but then it fails exactly like with the 7.1 boot CD > (7.1-RELEASE-amd64-disc1.iso). Screenshot: > http://omx.ch/om/stuff/pe1850bsd71error.jpg > > BIOS Message about the Controller on system startup: > PowerEdge Expandable RAID COntroller BIOS, (c) 2006 LSI Logic > Corporation > > I'm not sure what I can try next... I'd still like to be able to run > 7.1 on this host as well as on several other old but still fine 1850. Is > my system simply too old? Why is my adapter "busy" under 7.1? What > would you try? I checked the relnotes as well, but saw nothing helpful > about my problem there. > > regards & thanks in advance for any feedback, > Olivier > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From freebsd at sopwith.solgatos.com Wed Feb 11 21:09:10 2009 From: freebsd at sopwith.solgatos.com (Dieter) Date: Wed Feb 11 21:09:17 2009 Subject: SATA PCI adapter recommendation In-Reply-To: Your message of "Wed, 11 Feb 2009 09:33:37 +0100." <200902110833.n1B8XbLo096837@lurza.secnetix.de> Message-ID: <200902111859.SAA18166@sopwith.solgatos.com> > I plan to put a SATA drive in an old PATA-only PC, so I'm > looking for an appropriate adapter card. A cheap card > should suffice, I do not need RAID, and it does not have > to be SATA-300. > 1. Based on Silicon Image Sil-3x12 chip: > http://www.digital-data.de/download/datasheets/111816_Datasheet.pdf > I've read a few scary things about SIL chips on the lists, > so I guess I'd better try to avoid that one. The bad things I've read are all regarding the first generation SIL chips with FreeBSD. They work fine with NetBSD (and other OSes) so the problem is with the FreeBSD device driver. I haven't seen anything (pro or con) about the 2nd generation chips e.g. Sil 3124 with FreeBSD. The 2nd gen chips are supposed to be much better and faster than the 1st gen chips. Does anyone have experience to report with the Sil 3124 (PCI), Sil 3132 (PCIe) or other 2nd generation Sil chip with FreeBSD? > Finally, a small question: I assume that all of those > SATA controllers do have their own BIOS, so I can boot > from them, right? It would be annoying to have to keep > an old PATA disk in that box just to be able to boot. This may depend on the firmware on the mainboard? From pyunyh at gmail.com Thu Feb 12 00:53:30 2009 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Thu Feb 12 00:53:36 2009 Subject: Looking for ethernet expresscard In-Reply-To: References: Message-ID: <20090212085607.GE6313@michelle.cdnetworks.co.kr> On Tue, Feb 10, 2009 at 09:49:10AM +0100, Nicolas GORALSKI wrote: > Hi everybody > > I've a laptop with a sis191 ethernet card and it doesn't work. > NDIS with (XP|2K|98) drivers make my kernel crash. > See http://lists.freebsd.org/pipermail/freebsd-drivers/2008-April/000685.html I don't know whether it supports SiS191 or not. From won.derick at yahoo.com Thu Feb 12 05:52:24 2009 From: won.derick at yahoo.com (Won De Erick) Date: Thu Feb 12 05:52:30 2009 Subject: Hardware clock is not SYNC'ed with kernel clock by ntpdate? Message-ID: <243201.37742.qm@web45806.mail.sp1.yahoo.com> Hi All, I've done the following procedure to verify the unstable date/time being recorded in the hardware clock. I'm using IBM x343 with FreeBSD 6.2: 1. Rebooted the box. Entered a wrong date/time as: Date: December 1, 2008 Time: 12:00:00 2. When the box was UP'ed, displayed the date (the box is sync'ed with an NTP server during start-up). #date Thu Feb 12 15:37:57 PHT 2009 It seems correct. 3. Change with a wrong date/time again, then displayed. # date 0812301200 Tue Dec 30 12:00:00 PHT 2008 # date Tue Dec 30 12:00:14 PHT 2008 It seems correct. 4. Synchronized the date/time with an NTP Server. Then, displayed the date. # ntpdate ph.pool.ntp.org 12 Feb 15:40:59 ntpdate[3094]: step time server 202.92.128.201 offset 3814728.167216 sec # date Thu Feb 12 15:41:33 PHT 2009 It seems correct. 5. Rebooted the box, then verified the system date/time at the BIOS config. System Time 07:43:50 System Date Thu 02/12/2009 Wrong TIME? I think the hardware clock was not properly SYNCed with the kernel clock. I've verified this with other box, and same thing happened. Is there any issues on using date and ntpdate? Thanks, Won From guy at crossflight.co.uk Thu Feb 12 06:34:43 2009 From: guy at crossflight.co.uk (Guy Dawson) Date: Thu Feb 12 06:34:50 2009 Subject: Hardware clock is not SYNC'ed with kernel clock by ntpdate? In-Reply-To: <243201.37742.qm@web45806.mail.sp1.yahoo.com> References: <243201.37742.qm@web45806.mail.sp1.yahoo.com> Message-ID: <49942F54.4040201@crossflight.co.uk> Does the hardware clock show the correct UTC time? Your time zone appears to be PHT but the harware clock should be keeping UTC time. Guy Won De Erick wrote: > Hi All, > > I've done the following procedure to verify the unstable date/time being recorded in the hardware clock. > > I'm using IBM x343 with FreeBSD 6.2: > > 1. Rebooted the box. Entered a wrong date/time as: > Date: December 1, 2008 > Time: 12:00:00 > > 2. When the box was UP'ed, displayed the date (the box is sync'ed with an > NTP server during start-up). > > #date > Thu Feb 12 15:37:57 PHT 2009 > > It seems correct. > > 3. Change with a wrong date/time again, then displayed. > # date 0812301200 > Tue Dec 30 12:00:00 PHT 2008 > > # date > Tue Dec 30 12:00:14 PHT 2008 > > It seems correct. > > 4. Synchronized the date/time with an NTP Server. Then, displayed the date. > > # ntpdate ph.pool.ntp.org > 12 Feb 15:40:59 ntpdate[3094]: step time server 202.92.128.201 > offset 3814728.167216 sec > > # date > Thu Feb 12 15:41:33 PHT 2009 > > It seems correct. > > 5. Rebooted the box, then verified the system date/time at the BIOS config. > > System Time 07:43:50 > System Date Thu 02/12/2009 > > > Wrong TIME? I think the hardware clock was not properly SYNCed with the kernel clock. I've verified this with other box, and same thing happened. > > Is there any issues on using date and ntpdate? > > Thanks, > > Won > > > > > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" -- Guy -- -------------------------------------------------------------------- Guy Dawson I.T. Systems Manager Crossflight Ltd guy@crossflight.co.uk 07973 797819 01753 776104 ******************************************************************* This message contains the views and opinions of a Crossflight Limited employee and at this stage are in no way a direct representation of Crossflight Limited. Crossflight Limited is an international express courier, mailing and logistics service provider, and is authorised and regulated by the Financial Services Authority to conduct General Insurance Business. This communication and any attachments are confidential and may be protected from disclosure. We endorse no advice or opinion contained in this communication that is not the subject of a contract between the recipient and ourselves. If you have received it in error please notify us immediately and note that any storage, use or disclosure is strictly prohibited and may be unlawful. Those communicating with us by electronic mail will be deemed to have accepted the risks associated with interception, amendment, loss and late or incomplete delivery. They will also be deemed to have consented to our intercepting and monitoring such communications. This footnote also confirms that this message has been checked for the presence of computer viruses. We strongly recommend that you check this email with your own virus software as Crossflight Limited will not be held responsible for any damage caused by viruses as a result of opening this email. ******************************************************************* From won.derick at yahoo.com Thu Feb 12 06:37:17 2009 From: won.derick at yahoo.com (Won De Erick) Date: Thu Feb 12 06:37:23 2009 Subject: Hardware clock is not SYNC'ed with kernel clock by ntpdate? In-Reply-To: <49942F54.4040201@crossflight.co.uk> Message-ID: <167460.20536.qm@web45809.mail.sp1.yahoo.com> --- On Thu, 2/12/09, Guy Dawson wrote: > Does the hardware clock show the correct UTC time? > > Your time zone appears to be PHT but the harware clock > should be keeping UTC time. This is what I only saw in the BIOS config: System Time 07:43:50 System Date Thu 02/12/2009 No setting for time zone. > > Guy > > Won De Erick wrote: > > Hi All, > > > > I've done the following procedure to verify the > unstable date/time being recorded in the hardware clock. > > > > I'm using IBM x343 with FreeBSD 6.2: > > > > 1. Rebooted the box. Entered a wrong date/time as: > > Date: December 1, 2008 > > Time: 12:00:00 > > > > 2. When the box was UP'ed, displayed the date (the > box is sync'ed with an NTP server during start-up). > > #date > > Thu Feb 12 15:37:57 PHT 2009 > > > > It seems correct. > > > > 3. Change with a wrong date/time again, then > displayed. # date 0812301200 > > Tue Dec 30 12:00:00 PHT 2008 > > # date > > Tue Dec 30 12:00:14 PHT 2008 > > > > It seems correct. > > > > 4. Synchronized the date/time with an NTP Server. > Then, displayed the date. > > # ntpdate ph.pool.ntp.org > > 12 Feb 15:40:59 ntpdate[3094]: step time server > 202.92.128.201 offset 3814728.167216 sec > > # date > > Thu Feb 12 15:41:33 PHT 2009 > > > > It seems correct. > > > > 5. Rebooted the box, then verified the system > date/time at the BIOS config. System Time 07:43:50 > > System Date Thu 02/12/2009 > > > > Wrong TIME? I think the hardware clock was not > properly SYNCed with the kernel clock. I've verified > this with other box, and same thing happened. > > > > Is there any issues on using date and ntpdate? > > > > Thanks, > > > > Won > > > > > > > > > > > > _______________________________________________ > > freebsd-hardware@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > > To unsubscribe, send any mail to > "freebsd-hardware-unsubscribe@freebsd.org" > > > -- Guy > -- > -------------------------------------------------------------------- > Guy Dawson I.T. Systems Manager > Crossflight Ltd > guy@crossflight.co.uk 07973 797819 > 01753 776104 > > > ******************************************************************* > This message contains the views and opinions of a > Crossflight > Limited employee and at this stage are in no way a direct > representation of Crossflight Limited. > > Crossflight Limited is an international express courier, > mailing > and logistics service provider, and is authorised and > regulated by > the Financial Services Authority to conduct General > Insurance > Business. This communication and any attachments are > confidential > and may be protected from disclosure. We endorse no advice > or > opinion contained in this communication that is not the > subject of > a contract between the recipient and ourselves. > > If you have received it in error please notify us > immediately and > note that any storage, use or disclosure is strictly > prohibited and > may be unlawful. Those communicating with us by electronic > mail > will be deemed to have accepted the risks associated with > interception, amendment, loss and late or incomplete > delivery. > They will also be deemed to have consented to our > intercepting and > monitoring such communications. > > This footnote also confirms that this message has been > checked for > the presence of computer viruses. We strongly recommend > that you > check this email with your own virus software as > Crossflight > Limited will not be held responsible for any damage caused > by > viruses as a result of opening this email. > ******************************************************************* From won.derick at yahoo.com Thu Feb 12 17:50:39 2009 From: won.derick at yahoo.com (Won De Erick) Date: Thu Feb 12 17:50:51 2009 Subject: Hardware clock is not SYNC'ed with kernel clock by ntpdate? Message-ID: <752190.34892.qm@web45815.mail.sp1.yahoo.com> Does anyone know what is going on with my system? --- On Thu, 2/12/09, Won De Erick wrote: > From: Won De Erick > --- On Thu, 2/12/09, Guy Dawson wrote: > > Does the hardware clock show the correct UTC time? > > > > Your time zone appears to be PHT but the harware clock > > should be keeping UTC time. > > This is what I only saw in the BIOS config: > > System Time 07:43:50 > System Date Thu 02/12/2009 > > No setting for time zone. > > > > > Guy > > > > Won De Erick wrote: > > > Hi All, > > > > > > I've done the following procedure to verify the > > > unstable date/time being recorded in the hardware clock. > > > > > > I'm using IBM x343 with FreeBSD 6.2: > > > > > > 1. Rebooted the box. Entered a wrong date/time as: > > > Date: December 1, 2008 > > > Time: 12:00:00 > > > > > > 2. When the box was UP'ed, displayed the date (the > > > box is sync'ed with an NTP server during > > > start-up). > > > #date > > > Thu Feb 12 15:37:57 PHT 2009 > > > > > > It seems correct. > > > > > > 3. Change with a wrong date/time again, then > > > displayed. # date 0812301200 > > > Tue Dec 30 12:00:00 PHT 2008 > > > # date > > > Tue Dec 30 12:00:14 PHT 2008 > > > > > > It seems correct. > > > > > > 4. Synchronized the date/time with an NTP Server. > > > Then, displayed the date. > > > # ntpdate ph.pool.ntp.org > > > 12 Feb 15:40:59 ntpdate[3094]: step time > > > server > > > 202.92.128.201 offset 3814728.167216 sec > > > # date > > > Thu Feb 12 15:41:33 PHT 2009 > > > > > > It seems correct. > > > > > > 5. Rebooted the box, then verified the system > > > date/time at the BIOS config. System Time > > > 07:43:50 > > > System Date Thu 02/12/2009 > > > > > > Wrong TIME? I think the hardware clock was not > > > properly SYNCed with the kernel clock. I've > > > verified > > > this with other box, and same thing happened. > > > > > > Is there any issues on using date and ntpdate? > > > > > > Thanks, > > > > > > Won > > > > > > > > > > > > > > > > > > _______________________________________________ > > > freebsd-hardware@freebsd.org mailing list > > > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > > > To unsubscribe, send any mail to > > "freebsd-hardware-unsubscribe@freebsd.org" > > > > > > -- Guy > > -- > > > -------------------------------------------------------------------- > > Guy Dawson I.T. Systems Manager > > > Crossflight Ltd > > guy@crossflight.co.uk 07973 797819 > > > 01753 776104 > > > > > > From olivier at gautherot.net Thu Feb 12 19:04:28 2009 From: olivier at gautherot.net (Olivier Gautherot) Date: Thu Feb 12 19:04:35 2009 Subject: Hardware clock is not SYNC'ed with kernel clock by ntpdate? In-Reply-To: <752190.34892.qm@web45815.mail.sp1.yahoo.com> References: <752190.34892.qm@web45815.mail.sp1.yahoo.com> Message-ID: Hi Won, On Thu, Feb 12, 2009 at 10:50 PM, Won De Erick wrote: > Does anyone know what is going on with my system? > > > --- On Thu, 2/12/09, Guy Dawson wrote: > > > Does the hardware clock show the correct UTC time? > > > > > > Your time zone appears to be PHT but the harware clock > > > should be keeping UTC time. I back Guy's comment: the difference you see is indeed the time difference between UTC and PHT. If both your systems reboot in UTC, I would bet on the timezone you set in sysinstall more than the RTC. Please refer to section 2.10.8 in this (RTC in UTC - answer "yes" to the second question): http://www.freebsd.org/doc/en/books/handbook/install-post.html It may solve your problems. > > > > This is what I only saw in the BIOS config: > > > > System Time 07:43:50 > > System Date Thu 02/12/2009 > > > > No setting for time zone. BIOS generally do not have timezone setting . Hope it helps Cheers -- Olivier Gautherot olivier@gautherot.net Cel:+56 98 730 9361 www.gautherot.net http://www.linkedin.com/in/ogautherot From won.derick at yahoo.com Fri Feb 13 01:15:47 2009 From: won.derick at yahoo.com (Won De Erick) Date: Fri Feb 13 01:15:53 2009 Subject: Hardware clock is not SYNC'ed with kernel clock by ntpdate? In-Reply-To: Message-ID: <228216.40672.qm@web45805.mail.sp1.yahoo.com> --- On Fri, 2/13/09, Olivier Gautherot wrote: > Hi Won, > > On Thu, Feb 12, 2009 at 10:50 PM, Won De Erick > wrote: > > > Does anyone know what is going on with my system? > > > > > --- On Thu, 2/12/09, Guy Dawson > > > wrote: > > > > Does the hardware clock show the correct UTC > > > > Dtime? > > > > > > > > Your time zone appears to be PHT but the > > > > harware clock > > > > should be keeping UTC time. > > > I back Guy's comment: the difference you see is indeed > the time difference > between UTC and PHT. I understand this. > If both your systems reboot in UTC, I would bet on the > timezone you set in > sysinstall more than the RTC. > Can you elaborate more on this? I was expecting that when I did the ff: # ntpdate ph.pool.ntp.org 12 Feb 15:40:59 ntpdate[3094]: step time server 202.92.128.201 offset 3814728.167216 sec # date Thu Feb 12 15:41:33 PHT 2009 the time displayed will be reflected on the hardware. However, what I've got is the UTC-based. System Time 07:43:50 System Date Thu 02/12/2009 > Please refer to section 2.10.8 in this (RTC in UTC - answer > "yes" to the > second question): > http://www.freebsd.org/doc/en/books/handbook/install-post.html > It may solve your problems. > > > > > > > > > This is what I only saw in the BIOS config: > > > > > > System Time 07:43:50 > > > System Date Thu 02/12/2009 > > > > > > No setting for time zone. > > > BIOS generally do not have timezone setting . > > Hope it helps > Cheers > -- > Olivier Gautherot > olivier@gautherot.net > Cel:+56 98 730 9361 > www.gautherot.net > http://www.linkedin.com/in/ogautherot > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to > "freebsd-hardware-unsubscribe@freebsd.org" From olli at lurza.secnetix.de Fri Feb 13 02:45:59 2009 From: olli at lurza.secnetix.de (Oliver Fromme) Date: Fri Feb 13 02:46:07 2009 Subject: Hardware clock is not SYNC'ed with kernel clock by ntpdate? In-Reply-To: <243201.37742.qm@web45806.mail.sp1.yahoo.com> Message-ID: <200902131045.n1DAjtxw031128@lurza.secnetix.de> Hello, Do you have a file /etc/wall_cmos_clock on your system? If so, that would explain the behaviour very well. If you want your CMOS clock run at UTC instead of local time, you have to remove that file. Apart from the Handbook you might also have a look at the adjkerntz(8) manual page. It explains the mechanism used to maintain the time zone difference (if any) between FreeBSD and the CMOS clock. 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 "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." -- Doug Gwyn From roy.badami at globalgraphics.com Fri Feb 13 07:47:01 2009 From: roy.badami at globalgraphics.com (Roy Badami) Date: Fri Feb 13 07:47:07 2009 Subject: SIIG Cyber Serial 4S and system hang Message-ID: <18837.37036.643000.795911@erbium.cam.harlequin.co.uk> Can't find anyone else having the same problem as me, so I'm hoping this is the right place to post... The short version: I have a FreeBSD 7.1-RELEASE-p2 machine with a SIIG CyberSerial 4S card (one of the ones with the 10x clock) and I can fairly consistently make the machine hang by accessing the serial port. The long version: The machine is an Intel D815EEA ('Easton') motherboard with an 866 MHz Pentium III processor, and is running FreeBSD 7.1-RELEASE-p2. The kernel configuration is identical to GENERIC except that device puc has been uncommented. The machine has one serial port on the back (not sure if there's a second on the motherboard which isn't brought out) and I've installed a SIIG CyberSerial 4S card which identifies itself as: puc0: port 0xcf20-0xcf3f,0xcf00-0xcf1f mem 0xfc9fc000-0xfc9fcfff,0xfc9fb000-0xfc9fbfff irq 11 at device 11.0 on pci1 I believe this is one of the cards with the 10x clock, the patches for which finally made it to prime time in 7.1 (this card didn't work at all for me in 7.0). Initially I had smstools-3.1.3_1 running on cuad0 (m/b serial port) talking to an external GSM terminal for sending SMS messages and this worked fine. I then attached a serial-attached thermometer (that we built ourselves) to cuau0 (the first port on the CyberSerial) and started the temperature monitoring daemon, thermd (a perl script we wrote ourselves). When I started the temperature monitoring daemon from the command line, the system pretty consistently immediately locked up - both my ssh session and the physical console stopped responding - the Caps Lock light wouldn't even toggle. The really odd thing though is that now I swapped the two applications round, so the thermometer is on cuad0 and the GSM terminal is on cuau0 then everything is working fine. I've attached the thermd script in case the way it accesses the tty sheds any light as to what was going on, but unfortunately it's not possible to reproduce the hang without the (custom built) thermometer attached to the serial port. Although things seem to be working, I'd like to get to the bottom of this so that I can be confident that the machine won't freeze again in the future - and I have more serial applications I need to run on this server. Any suggestions as to how to proceed - short of changing to a different model of serial card? Thanks, -roy -------------------- #!/usr/local/bin/perl5 $ALERT_TEMP = 26; #$ALERT_TEMP = 32; $ALERT_INTERVAL = 60*20; $ALERT_THRESHOLD_FALLING = 2; $ALERT_THRESHOLD_RISING = 2; $ALERT = 'alert_hall'; $tempfile = '/usr/local/etc/temperature'; $pager = '/usr/local/bin/pager'; $debug = 0; use POSIX; use Fcntl; die "No tty specified" unless $ARGV[0]; $tty=$ARGV[0]; $tty = "/dev/$tty" unless $tty =~ m'/'; &open_tty(\*TTY, $tty); open TEMP, "+> $tempfile" or die "Can't open $tempfile"; &daemon unless $debug; for (;;) { until (&check_thermometer(\*TTY)) { print STDERR "Error communicating with thermometer" unless $error; $error = 1; #No need to wait, since there's a wait in check_thermometer } print STDERR "Communication established" if $error; $error = 0; for (;;) { $temp = &read_thermometer(\*TTY); if (!defined($temp)) { print STDERR "Error reading thermometer"; $error = 1; last; } &process_temp($temp); sleep 10; } } exit; sub open_tty { my ($FILE, $tty) = @_; my ($termios,$iflag,$oflag,$cflag,$lflag); open $FILE, "+> $tty" or die "Can't open $tty"; $termios = POSIX::Termios->new; $termios->getattr(fileno $FILE); #iflag $iflag = $termios->getiflag; $iflag &= ~(BRKINT|PARMRK|ISTRIP|INLCR|IGNCR|ICRNL|IXON|IXOFF|IXANY|IMAXBEL); $iflag |= (IGNBRK|IGNPAR|INPCK); $termios->setiflag($iflag); #oflag $oflag = $termios->getoflag; $oflag &= ~OPOST; $termios->setoflag($oflag); #cflag $cflag = $termios->getcflag; $cflag = ($cflag & ~CSIZE) | CS8; $cflag &= ~(CSTOPB|PARENB|HUPCL|CCTR_OFLOW|CRTS_IFLOW|MDMBUF); $cflag |= (CREAD|CLOCAL); $termios->setcflag($cflag); #lflag $lflag = $termios->getlflag; $lflag &= ~(ECHO|ECHOCTL|ISIG|ICANON|IEXTEN); $termios->setlflag($lflag); #reads time out after 2 seconds $termios->setcc(VMIN, 0); $termios->setcc(VTIME, 20); #baud rate $termios->setispeed(B9600); $termios->setospeed(B9600); #doit! $termios->setattr(fileno $FILE, TCSANOW); } sub check_thermometer { my ($TTY) = @_; my ($fl, $buffer, $result); $fl = fcntl $TTY, &F_GETFL, 0; $fl |= &O_NONBLOCK; fcntl $TTY, &F_SETFL, $fl; sysread $TTY, $buffer, 8192; $fl &= ~&O_NONBLOCK; fcntl $TTY, &F_SETFL, $fl; defined(syswrite $TTY, 'S', 1) or die "Error writing to tty"; defined(sysread $TTY, $buffer, 1) or die "Error reading from tty"; #Allow thermometer to recover sleep 1; $result = ($buffer eq 'S'); if ($debug) { print 'check_thermometer: ', ($result?'OK':'Failed'), "\n"; } $result; } sub read_thermometer { my ($TTY) = @_; my ($buffer, $res_string); defined(syswrite $TTY, 'T', 1) or die "Error writing to tty"; defined(sysread $TTY, $buffer, 1) or die "Error reading from tty"; sleep 1; $res_string = ($buffer?sprintf("%03d",ord($buffer)):'ERR'); lseek (fileno TEMP, 0, &SEEK_SET); syswrite (TEMP, $res_string, 3); if ($debug) { print "read_thermometer: $res_string\n" } $buffer ? ord($buffer) : undef; } sub process_temp { my ($temp) = @_; my ($time); $time = time; if ($temp >= $ALERT_TEMP && (!$alert || ($temp >= $last_alert_temp + $ALERT_THRESHOLD_RISING && $time-$last_alert_time > $ALERT_INTERVAL))) { if ($alert) { &alert("Temperature rising, now ${temp}C"); } else { &alert("Over temperature alarm: ${temp}C"); } $alert = 1; $last_alert_temp = $temp; $last_alert_time = $time; } elsif ($alert && $temp <= ($last_alert_temp - $ALERT_THRESHOLD_FALLING)) { if ($temp < $ALERT_TEMP) { &alert("Temperature now normal at ${temp}C"); $alert = 0; } elsif ($time-$last_alert_time > $ALERT_INTERVAL) { &alert("Temperature dropping, now ${temp}C"); $last_alert_temp = $temp; $last_alert_time = $time; } } } sub alert { my ($msg) = @_; print STDERR "thermometer: $msg\n"; system ("$pager -p $ALERT $msg"); } sub daemon { my ($pid); if ($daemon) { return } $daemon = 1; open NULL, "/dev/null" or die "Can't open /dev/null"; open CONSOLE, "/dev/console" or die "Can't open /dev/console"; $pid = fork; die "Can't fork" unless defined $pid; exit if $pid; # Parent setsid(); close STDIN; close STDOUT; close STDERR; open STDIN, "<&NULL"; open STDOUT, ">&NULL"; open STDERR, ">&CONSOLE"; close NULL; close CONSOLE; } From amijaresp at gmail.com Fri Feb 13 08:30:18 2009 From: amijaresp at gmail.com (Alberto Mijares) Date: Fri Feb 13 08:30:30 2009 Subject: Modem GSM/GPRS Message-ID: <286906750902130802q2ec86267ye5ae0832ab9a3aa4@mail.gmail.com> Hello everybody, I have an Enfora EDG1228 GSM/GPRM modem, which should be used to send SMS. Seems not to be natively supported by FreeBSD 7.0: #dmesg [...] ugen0: on uhub0 #usbdevs [...] addr 3: SA-EL USB, Silicon Labs [...] Can't find any successful history of anyone getting it to work... Any suggestion? Thanks in advance. Regards Alberto Mijares Any suggestion about it? From hselasky at c2i.net Fri Feb 13 10:04:27 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Feb 13 10:04:34 2009 Subject: Modem GSM/GPRS In-Reply-To: <286906750902130802q2ec86267ye5ae0832ab9a3aa4@mail.gmail.com> References: <286906750902130802q2ec86267ye5ae0832ab9a3aa4@mail.gmail.com> Message-ID: <200902131906.51725.hselasky@c2i.net> On Friday 13 February 2009, Alberto Mijares wrote: > Hello everybody, > > I have an Enfora EDG1228 GSM/GPRM modem, which should be used to send > SMS. Seems not to be natively supported by FreeBSD 7.0: > > #dmesg > [...] > ugen0: on uhub0 > > > Alberto Mijares > > Any suggestion about it? Can you dump the USB descriptors with /usr/ports/sysutils/udesc_dump ? --HPS From won.derick at yahoo.com Fri Feb 13 23:06:09 2009 From: won.derick at yahoo.com (Won De Erick) Date: Fri Feb 13 23:06:16 2009 Subject: Hardware clock is not SYNC'ed with kernel clock by ntpdate? In-Reply-To: <200902131045.n1DAjtxw031128@lurza.secnetix.de> Message-ID: <800496.48763.qm@web45816.mail.sp1.yahoo.com> Hi Oliver, Thanks for the help. This file /etc/wall_cmos_clock was missing, so I created an empty one. The CMOS clock was successfully updated when I invoked 'adjkerntz -a'. However, how should I make this automatic, something that will update the CMOS clock everytime the kernel clock is syncronized with a NTP server? Do I need to make changes on the variables below? # sysctl -a machdep machdep.adjkerntz: 0 machdep.disable_rtc_set: 0 machdep.wall_cmos_clock: 0 machdep.conrclk: 1843200 machdep.gdbspeed: 9600 machdep.conspeed: 9600 .... --- On Fri, 2/13/09, Oliver Fromme wrote: > Hello, > > Do you have a file /etc/wall_cmos_clock on your system? > If so, that would explain the behaviour very well. > If you want your CMOS clock run at UTC instead of local > time, you have to remove that file. > > Apart from the Handbook you might also have a look at > the adjkerntz(8) manual page. It explains the mechanism > used to maintain the time zone difference (if any) > between FreeBSD and the CMOS clock. > > 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 > > "UNIX was not designed to stop you from doing stupid > things, > because that would also stop you from doing clever > things." > -- Doug Gwyn > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to > "freebsd-hardware-unsubscribe@freebsd.org" From amijaresp at gmail.com Sat Feb 14 01:11:33 2009 From: amijaresp at gmail.com (Alberto Mijares) Date: Sat Feb 14 01:11:42 2009 Subject: Modem GSM/GPRS In-Reply-To: <200902132209.52793.hselasky@c2i.net> References: <286906750902130802q2ec86267ye5ae0832ab9a3aa4@mail.gmail.com> <200902131906.51725.hselasky@c2i.net> <286906750902131226y22605e4ag41dcab90a6f7cf57@mail.gmail.com> <200902132209.52793.hselasky@c2i.net> Message-ID: <286906750902140111i62d94f78w3921951f072cb930@mail.gmail.com> [...] > Your device seems to use a propritary protocol and is not supported by FreeBSD > out of the Box. But it might be a very simple one. In FreeBSD-7-current you > can try adding the idVendor and idProduct to the ID-table > in /sys/dev/usb/u3g.c . I've been trying and found this -> http://people.freebsd.org/~n_hibma/u3g.html So, I updated my system (I'm on 7.1 now) and followed instructions. now dmesg says: ucom0: on uhub0 ucom0: configured 1 serial ports (U0.%d) (much better, doesn't it) and /dev/cuaU0.0 is created when it is plugged in. However, I can't stablish comunication with the modem. I tried with screen and minicom, but nothing happens. Even stty reports: #stty -f /dev/cuaU0.0 -a speed 9600 baud; 0 rows; 0 columns; lflags: icanon isig iexten -echo -echoe -echok -echoke -echonl -echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo -extproc iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk brkint -inpck -ignpar -parmrk oflags: opost onlcr -ocrnl -oxtabs -onocr -onlret cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow -dtrflow -mdmbuf cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = ; eol2 = ; erase = ^?; erase2 = ^H; intr = ^C; kill = ^U; lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W; This is what I did: $ diff u3g.c original 195,196d194 < /* PRUEBA SILABS */ < {{ USB_VENDOR_SILABS, USB_PRODUCT_SILABS_SAEL }, U3GSP_GPRS, U3GFL_NONE }, and $ tail -1 usbdevs product SILABS SAEL 0x8053 SA-EL USB Is there anything else should I try? Any clue is good for me. Thank you Alberto Mijares From admin at vfemail.net Sat Feb 14 08:08:20 2009 From: admin at vfemail.net (Rick Romero) Date: Sat Feb 14 08:08:27 2009 Subject: Areca 1200 controller panics 7.1 Message-ID: <1234626078.5736.121.camel@rickxp> Me Too! I have TWO identical systems with Asus M3A78-CM Motherboards, and an ARC-1200 in each that is having this problem. Removing that controller allows the install CD to boot. Merely removing the drives from the controller does not. I've upgraded the BIOS, moved the controller to another slot, futzed in the BIOS (disabling/enabling,etc) - to no avail. I also upgraded the controller BIOS. I've booted 7.0R, 7.1R, 8.0Current(12/08), and 6.4R. 6.4R just 'hangs' at 'Waiting 5 seconds for SCSI devices to settle' (which is just before the kernel dump on 7 and 8), the rest crash with the below error. Obviously 8.0 has more data, but the jist is the same. I also found this link from 2007 which seems similar: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2007-04/msg00237.html Thoughts? suggestions? If you would like more info, I'd be happy to provide it. The controller has worked fine in OpenSolaris 2008.11, and I booted Ubuntu 8.10 for giggles and it worked there as well. Should I install onto a MotherBoard connected disk, then plug in the areca? Would that provide a dump point to get you guys more data? I want the areca as RAID 1 boot, and the SATA connected to the motherboard as JBOD for ZFS (hence the OpenSolaris above). Rick ---------------------------------------------- Attachment not getting throuh. Panic transcribed below. /Eirik On Jan 21, 2009, at 20:53, Eirik ?verby wrote: > Hi folks, > > see attached screenshot for panic screen. This happens when booting > from 7.1-release CD. The box is a Sun X2200 M2, the controller is a > 2-port SATA-II controller with 128mb cache memory. One drive is set > as single drive (RAID-0), another as passthrough (to get hold of > some data from pre-areca times). > > Another Areca controller in another box (different controller model > (4-chan sata) and box (tyan transport)) works just fine. > > Input welcome. > > /Eirik (probe16:arcmsr0:0:16:0): inquiry data fails comparison at DV1 step arcmsr0: isr get an illegal srb command doneacb=?0xffffffff8124e000? srb=0xffff ffffaeb6c420? srbacb=?0xffffffff8124e000? startdone=0x3c3csrboutstandingcount=-1 Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x34be2988 fault code = supervisor read data, page not present instruction pointer = 0x8:0xffffffff807914c3 stack pointer = 0x10:0xffffffffaecaab60 frame pointer = 0x10:0xffffffff8124e000 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 36 (irq17: arcmsr0) trap number = 12 panic: page fault From olli at lurza.secnetix.de Sat Feb 14 10:39:01 2009 From: olli at lurza.secnetix.de (Oliver Fromme) Date: Sat Feb 14 10:39:07 2009 Subject: Hardware clock is not SYNC'ed with kernel clock by ntpdate? In-Reply-To: <800496.48763.qm@web45816.mail.sp1.yahoo.com> Message-ID: <200902141838.n1EIcwQX009259@lurza.secnetix.de> Won De Erick wrote: > This file /etc/wall_cmos_clock was missing, so I created an empty one. So you _do_ want to run your CMOS clock at local time instead of UTC? That is only required if you run a different OS on the same machine (dual-boot), because Windows expects the CMOS clock to run at local time. Otherwise, if FreeBSD is the only OS on that machine, it's better to let the CMOS clock run at UTC (i.e. do not create /etc/wall_cmos_clock), because it avoids all the switching back and forth between time zones, and adjkerntz(8) doesn't have to run all the time. As far as ntpd is concerned, it doesn't matter. ntpd doesn't care about time zones. It always works on UTC internally and synchronizes the time that way (otherwise there would be additional complexities using NTP servers in different time zones). Even the kernel doesn't care about time zones. Handling time zones is done in the libc (userland). So, basically, if a program like date(1) displays the time, it converts UTC to your local time zone for you. > However, how should I make this automatic, something that will update > the CMOS clock everytime the kernel clock is syncronized with a NTP > server? Do I need to make changes on the variables below? You seem to misunderstand. The CMOS clock _is_ always updated when you run ntpd. You do not have to change anything. The only question is at which time zone the CMOS clock runs, as I've explained above. If your CMOS clock runs at UTC (recommended if FreeBSD is the only OS on that machine), then the BIOS will always display a wrong time, because the BIOS doesn't know your time zone, so it can't convert from UTC to your time zone. But that's purely a cosmetical issue. You can ignore that. Your CMOS clock _is_ synchronized and runs correctly. Only your BIOS doesn't know how to display it correctly. 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 "The ITU has offered the IETF formal alignment with its corresponding technology, Penguins, but that won't fly." -- RFC 2549 From dadans at gmail.com Sun Feb 15 07:28:40 2009 From: dadans at gmail.com (DadAN) Date: Sun Feb 15 07:28:46 2009 Subject: Hardware clock is not SYNC'ed with kernel clock by ntpdate? In-Reply-To: <800496.48763.qm@web45816.mail.sp1.yahoo.com> References: <200902131045.n1DAjtxw031128@lurza.secnetix.de> <800496.48763.qm@web45816.mail.sp1.yahoo.com> Message-ID: Hello, > However, how should I make this automatic, something that will update the CMOS clock everytime the kernel clock is syncronized > with a NTP server? Do I need to make changes on the variables below? You can run it as cron job, for example 1,31 0-5 * * * root adjkerntz -a here is my # sysctl -a machdep machdep.enable_panic_key: 0 machdep.adjkerntz: -3600 machdep.wall_cmos_clock: 1 machdep.disable_rtc_set: 0 machdep.conspeed: 115200 machdep.gdbspeed: 9600 machdep.conrclk: 1843200 machdep.disable_mtrrs: 0 machdep.guessed_bootdev: 2686451712 machdep.cpu_idle_hlt: 1 machdep.hlt_cpus: 0 machdep.prot_fault_translation: 0 machdep.panic_on_nmi: 1 machdep.tsc_freq: 514994590 machdep.i8254_freq: 1193182 machdep.acpi_timer_freq: 3579545 machdep.acpi_root: 1016224 -- DadAN From won.derick at yahoo.com Sun Feb 15 17:35:32 2009 From: won.derick at yahoo.com (Won De Erick) Date: Sun Feb 15 17:35:38 2009 Subject: Hardware clock is not SYNC'ed with kernel clock by ntpdate? In-Reply-To: <200902141838.n1EIcwQX009259@lurza.secnetix.de> Message-ID: <529764.94153.qm@web45808.mail.sp1.yahoo.com> Thank you very much for the clear explanation. --- On Sat, 2/14/09, Oliver Fromme wrote: > Won De Erick wrote: > > This file /etc/wall_cmos_clock was missing, so I > created an empty one. > > So you _do_ want to run your CMOS clock at local time > instead of UTC? That is only required if you run a > different OS on the same machine (dual-boot), because > Windows expects the CMOS clock to run at local time. > 'Not that I want to run at UTC. I wanted to find out how the BMC system event log (SEL) timestamps are done by the BMC firmware. The IBM x343 box is an IPMI v1.5 compliant, and FreeBSD is the only OS installed. I wondered why I got late datestamps on SEL. > Otherwise, if FreeBSD is the only OS on that machine, > it's better to let the CMOS clock run at UTC (i.e. do > not create /etc/wall_cmos_clock), because it avoids > all the switching back and forth between time zones, > and adjkerntz(8) doesn't have to run all the time. > > As far as ntpd is concerned, it doesn't matter. ntpd > doesn't care about time zones. It always works on UTC > internally and synchronizes the time that way (otherwise > there would be additional complexities using NTP servers > in different time zones). Even the kernel doesn't care > about time zones. Handling time zones is done in the > libc (userland). So, basically, if a program like > date(1) displays the time, it converts UTC to your local > time zone for you. > > > However, how should I make this automatic, something > > that will update > > the CMOS clock everytime the kernel clock is > > syncronized with a NTP > > server? Do I need to make changes on the variables > > below? > > You seem to misunderstand. The CMOS clock _is_ always > updated when you run ntpd. You do not have to change > anything. > > The only question is at which time zone the CMOS clock > runs, as I've explained above. > > If your CMOS clock runs at UTC (recommended if FreeBSD > is the only OS on that machine), then the BIOS will > always display a wrong time, because the BIOS doesn't > know your time zone, so it can't convert from UTC to > your time zone. But that's purely a cosmetical issue. > You can ignore that. Your CMOS clock _is_ synchronized > and runs correctly. Only your BIOS doesn't know how > to display it correctly. > This is a cool explanation. This has cleared my assumption that the CMOS clocked is not updated whenever the system is sync'ed with an NTP server. I think this has narrow down the issue. Let me share you the problem that I encountered, which had led me to suspect before that CMOS clock was not properly sync'ed. I hope you can give me more hints/explanations for me to come up with a conclusive findings. 1. Get the date/time in shell # date Fri Feb 13 14:20:20 PHT 2009 2. Rebooted the box, then entered BIOS config to verify date/time System Time : 06:25:29 # seems correct, it runs at UTC System Date : Fri 02/13/2009 3. Let the system up. 4. Unplugged the power cord to come up with a new event in SEL. I am using FreeIPMI v0.7.1 to retrieve the logs. 1724:01-Jan-1970 08:00:12:Power Supply Power Supply 2:Presence detected 1744:01-Jan-1970 08:00:12:Power Supply Power Supply 2:Power Supply input lost (AC/DC) -------------------> uplug the power. 1764:01-Jan-1970 08:00:12:Power Unit Power Redundancy:Entered from Non-redundant:Insufficient Resources 1784:01-Jan-1970 08:00:41:System Event System Event:Timestamp Clock Synch 1804:12-Feb-2009 14:27:50:System Event System Event:Timestamp Clock Synch 1824:12-Feb-2009 14:28:15:System Event System Event:OEM System Boot Event 1844:12-Feb-2009 14:29:53:System Event System Event:Timestamp Clock Synch 1864:12-Feb-2009 14:29:53:System Event System Event:Timestamp Clock Synch 1884:12-Feb-2009 14:31:55:System Event System Event:OEM System Boot Event -------------------> datestamp incorrect Is the datestamp '01-Jan-1970' a sign of a defective CMOS battery? Does the datestamp '12-Feb-2009' being not updated to the correct date (13-Feb-2009) is a sign of a defective battery too? or other issues like firmware bug? I would be grateful to receive more tips from you. > 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 > > "The ITU has offered the IETF formal alignment with > its > corresponding technology, Penguins, but that won't > fly." > -- RFC 2549 > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to > "freebsd-hardware-unsubscribe@freebsd.org" From om-lists-bsd at omx.ch Mon Feb 16 06:22:08 2009 From: om-lists-bsd at omx.ch (Olivier Mueller) Date: Mon Feb 16 06:22:22 2009 Subject: poweredge 1850 won't boot 7.1? maybe LSI-related : amr0: adapter is busy In-Reply-To: <1234366709.3500.62.camel@ingress.ws.pitbpa0.priv.collaborativefusion.com> References: <1234363891.15909.35.camel@ompc.insign.local> <1234366709.3500.62.camel@ingress.ws.pitbpa0.priv.collaborativefusion.com> Message-ID: <1234794122.22023.76.camel@ompc.insign.local> On Wed, 2009-02-11 at 10:38 -0500, Brian A. Seklecki wrote: > There's already discussion about this in the archives. We're aware and > working on it. > > Set: > /boo/loader.conf > kern.cam.scsi_delay=20000 > As a work-around for now. Many thanks for your answer, it fixed the problem for now. Now it looks like that: amr0: mem 0xd80f0000-0xd80fffff,0xdfde0000-0xdfdfffff irq 46 at device 14.0 on pci2 amr0: Using 64-bit DMA amr0: [ITHREAD] amr0: delete logical drives supported by controller amr0: Firmware 521X, BIOS H430, 256MB RAM amr0: delete logical drives supported by controller amrd0: on amr0 amrd0: 69880MB (143114240 sectors) RAID 1 (optimal) ses0 at amr0 bus 0 target 6 lun 0 Trying to mount root from ufs:/dev/amrd0s1a Regards & a nice week to you and the other readers, Olivier From lavalamp at spiritual-machines.org Mon Feb 16 07:51:34 2009 From: lavalamp at spiritual-machines.org (Brian A. Seklecki) Date: Mon Feb 16 07:51:46 2009 Subject: poweredge 1850 won't boot 7.1? maybe LSI-related : amr0: adapter is busy In-Reply-To: <1234794122.22023.76.camel@ompc.insign.local> References: <1234363891.15909.35.camel@ompc.insign.local> <1234366709.3500.62.camel@ingress.ws.pitbpa0.priv.collaborativefusion.com> <1234794122.22023.76.camel@ompc.insign.local> Message-ID: > amr0: Firmware 521X, BIOS H430, 256MB RAM > amr0: delete logical drives supported by controller Any time! NOTE: You're using the 4e/Si, which we have as well. We're experiencing random crashes on the 1850/8th gen, as a result of a (believed) DMA bug introduced into 7.x Please let us know if you see kernel panics or unexpected behavior (sig11s) The developer we're working with cannot re-create the problem on the PERC4/Di. ~BAS > amrd0: on amr0 > amrd0: 69880MB (143114240 sectors) RAID 1 (optimal) > ses0 at amr0 bus 0 target 6 lun 0 > Trying to mount root from ufs:/dev/amrd0s1a > > Regards & a nice week to you and the other readers, > Olivier From korvus at comcast.net Mon Feb 16 09:27:22 2009 From: korvus at comcast.net (Steve Polyack) Date: Mon Feb 16 09:27:29 2009 Subject: poweredge 1850 won't boot 7.1? maybe LSI-related : amr0: adapter is busy In-Reply-To: References: <1234363891.15909.35.camel@ompc.insign.local> <1234366709.3500.62.camel@ingress.ws.pitbpa0.priv.collaborativefusion.com> <1234794122.22023.76.camel@ompc.insign.local> Message-ID: <49999672.6020801@comcast.net> Brian A. Seklecki wrote: > NOTE: You're using the 4e/Si, which we have as well. We're experiencing > random crashes on the 1850/8th gen, as a result of a (believed) DMA bug > introduced into 7.x > > Just to note, we are only seeing these issues in combination with megarc (/usr/ports/sysutils/megarc) monitoring. From rick at havokmon.com Mon Feb 16 10:41:19 2009 From: rick at havokmon.com (Rick Romero) Date: Mon Feb 16 10:41:25 2009 Subject: Areca 1200 controller panics 7.1 In-Reply-To: <1234626078.5736.121.camel@rickxp> References: <1234626078.5736.121.camel@rickxp> Message-ID: <1234808053.5736.157.camel@rickxp> According to: ftp://ftp.areca.com.tw/RaidCards/AP_Drivers/FreeBSD/DRIVER/SourceCode/ There is a driver released 12/10/08. According to SVN for FreeBSD 8.0, the current driver was committed 3 years ago. Unless someone would like to step up and 'pop in' the new version to the current kernel and save me some effort, I will be attempting my first FreeBSD kernel compile after a good 8 years of use. :/ Procedure: 1. Install FreeBSD 7.1 to a system without the Areca 1200 installed. 2. Verify it's still not working after reboot and hardware install. 3. Compile the new kernel with new driver 4. Reboot using new kernel to verify build 5. Reinstall ARC1200 6. Watch what happens. Report back here. Rick > (probe16:arcmsr0:0:16:0): inquiry data fails comparison at DV1 step > arcmsr0: isr get an illegal srb command doneacb=?0xffffffff8124e000? > srb=0xffff > ffffaeb6c420? srbacb=?0xffffffff8124e000? > startdone=0x3c3csrboutstandingcount=-1 > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x34be2988 > fault code = supervisor read data, page not present > instruction pointer = 0x8:0xffffffff807914c3 > stack pointer = 0x10:0xffffffffaecaab60 > frame pointer = 0x10:0xffffffff8124e000 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 36 (irq17: arcmsr0) > trap number = 12 > panic: page fault > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From rick at havokmon.com Mon Feb 16 16:53:33 2009 From: rick at havokmon.com (Rick Romero) Date: Mon Feb 16 16:53:40 2009 Subject: Areca 1200 controller panics 7.1 In-Reply-To: <1234808053.5736.157.camel@rickxp> References: <1234626078.5736.121.camel@rickxp> <1234808053.5736.157.camel@rickxp> Message-ID: <1234831988.5736.191.camel@rickxp> On Mon, 2009-02-16 at 12:14 -0600, Rick Romero wrote: > According to: > ftp://ftp.areca.com.tw/RaidCards/AP_Drivers/FreeBSD/DRIVER/SourceCode/ > > There is a driver released 12/10/08. > > According to SVN for FreeBSD 8.0, the current driver was committed 3 > years ago. False alarm, The latest version in FreeBSD is from 2007, and is numbered higher than the website version. Rick From won.derick at yahoo.com Tue Feb 17 08:32:42 2009 From: won.derick at yahoo.com (Won De Erick) Date: Tue Feb 17 08:32:48 2009 Subject: Hardware clock is not SYNC'ed with kernel clock by ntpdate? Message-ID: <538199.46897.qm@web45808.mail.sp1.yahoo.com> Hi All, Is this firmware-related bug? tool log parsing error? Thanks in advance. --- On Mon, 2/16/09, Won De Erick wrote: > Thank you very much for the clear explanation. > > --- On Sat, 2/14/09, Oliver Fromme > wrote: > > Won De Erick wrote: > > > This file /etc/wall_cmos_clock was missing, so I > > created an empty one. > > > > So you _do_ want to run your CMOS clock at local time > > instead of UTC? That is only required if you run a > > different OS on the same machine (dual-boot), because > > Windows expects the CMOS clock to run at local time. > > > > 'Not that I want to run at UTC. I wanted to find out > how the BMC system event log (SEL) timestamps are done by > the BMC firmware. The IBM x343 box is an IPMI v1.5 > compliant, and FreeBSD is the only OS installed. I wondered > why I got late datestamps on SEL. > > > Otherwise, if FreeBSD is the only OS on that machine, > > it's better to let the CMOS clock run at UTC (i.e. > do > > not create /etc/wall_cmos_clock), because it avoids > > all the switching back and forth between time zones, > > and adjkerntz(8) doesn't have to run all the time. > > > > As far as ntpd is concerned, it doesn't matter. > ntpd > > doesn't care about time zones. It always works on > UTC > > internally and synchronizes the time that way > (otherwise > > there would be additional complexities using NTP > servers > > in different time zones). Even the kernel doesn't > care > > about time zones. Handling time zones is done in the > > libc (userland). So, basically, if a program like > > date(1) displays the time, it converts UTC to your > local > > time zone for you. > > > > > However, how should I make this automatic, > something > > > that will update > > > the CMOS clock everytime the kernel clock is > > > syncronized with a NTP > > > server? Do I need to make changes on the > variables > > > below? > > > > You seem to misunderstand. The CMOS clock _is_ always > > updated when you run ntpd. You do not have to change > > anything. > > > > The only question is at which time zone the CMOS clock > > runs, as I've explained above. > > > > If your CMOS clock runs at UTC (recommended if FreeBSD > > is the only OS on that machine), then the BIOS will > > always display a wrong time, because the BIOS > doesn't > > know your time zone, so it can't convert from UTC > to > > your time zone. But that's purely a cosmetical > issue. > > You can ignore that. Your CMOS clock _is_ > synchronized > > and runs correctly. Only your BIOS doesn't know > how > > to display it correctly. > > > > > This is a cool explanation. This has cleared my assumption > that the CMOS clocked is not updated whenever the system is > sync'ed with an NTP server. > I think this has narrow down the issue. > > Let me share you the problem that I encountered, which had > led me to suspect before that CMOS clock was not properly > sync'ed. I hope you can give me more hints/explanations > for me to come up with a conclusive findings. > > 1. Get the date/time in shell > # date > Fri Feb 13 14:20:20 PHT 2009 > > 2. Rebooted the box, then entered BIOS config to verify > date/time > > System Time : 06:25:29 # seems correct, it runs > at UTC > System Date : Fri 02/13/2009 > > 3. Let the system up. > 4. Unplugged the power cord to come up with a new event in > SEL. I am using FreeIPMI v0.7.1 to retrieve the logs. > > 1724:01-Jan-1970 08:00:12:Power Supply Power Supply > 2:Presence detected > 1744:01-Jan-1970 08:00:12:Power Supply Power Supply 2:Power > Supply input lost (AC/DC) -------------------> uplug the > power. > 1764:01-Jan-1970 08:00:12:Power Unit Power > Redundancy:Entered from Non-redundant:Insufficient Resources > 1784:01-Jan-1970 08:00:41:System Event System > Event:Timestamp Clock Synch > 1804:12-Feb-2009 14:27:50:System Event System > Event:Timestamp Clock Synch > 1824:12-Feb-2009 14:28:15:System Event System Event:OEM > System Boot Event > 1844:12-Feb-2009 14:29:53:System Event System > Event:Timestamp Clock Synch > 1864:12-Feb-2009 14:29:53:System Event System > Event:Timestamp Clock Synch > 1884:12-Feb-2009 14:31:55:System Event System Event:OEM > System Boot Event -------------------> datestamp > incorrect > > Is the datestamp '01-Jan-1970' a sign of a > defective CMOS battery? > Does the datestamp '12-Feb-2009' being not updated > to the correct date (13-Feb-2009) is a sign of a defective > battery too? or other issues like firmware bug? I would be > grateful to receive more tips from you. > > > > 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 > > > > "The ITU has offered the IETF formal alignment > with > > its > > corresponding technology, Penguins, but that won't > > fly." > > -- RFC 2549 > > _______________________________________________ > > freebsd-hardware@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > > To unsubscribe, send any mail to > > "freebsd-hardware-unsubscribe@freebsd.org" From olli at lurza.secnetix.de Tue Feb 17 09:50:20 2009 From: olli at lurza.secnetix.de (Oliver Fromme) Date: Tue Feb 17 09:50:27 2009 Subject: Hardware clock is not SYNC'ed with kernel clock by ntpdate? In-Reply-To: <538199.46897.qm@web45808.mail.sp1.yahoo.com> Message-ID: <200902171750.n1HHoHYG080381@lurza.secnetix.de> Won De Erick wrote: > Is this firmware-related bug? tool log parsing error? I'm sorry, I don't know for sure. But it looks like a firmware problem. 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 "Whatever happened to the days when hacking started at the cerebral cortex, and not at the keyboard?" -- Sid on userfriendly.org by Illiad, 2007-06-20 From nick at van-laarhoven.org Tue Feb 17 13:15:30 2009 From: nick at van-laarhoven.org (Nick Hibma) Date: Tue Feb 17 13:15:37 2009 Subject: Modem GSM/GPRS In-Reply-To: <286906750902140111i62d94f78w3921951f072cb930@mail.gmail.com> References: <286906750902130802q2ec86267ye5ae0832ab9a3aa4@mail.gmail.com> <200902132209.52793.hselasky@c2i.net> <286906750902140111i62d94f78w3921951f072cb930@mail.gmail.com> Message-ID: <200902172203.19534.nick@van-laarhoven.org> Alberto, Could you remove u3g again from your kernel, so the device attaches to ugen and then dump its descriptors using usbgen? usbgen -f /dev/ugen0 -D where ugen0 is the device mentioned in the dmesg. Thanks. Nick > [...] > > > Your device seems to use a propritary protocol and is not supported by > > FreeBSD out of the Box. But it might be a very simple one. In > > FreeBSD-7-current you can try adding the idVendor and idProduct to the > > ID-table > > in /sys/dev/usb/u3g.c . > > I've been trying and found this -> > http://people.freebsd.org/~n_hibma/u3g.html > > So, I updated my system (I'm on 7.1 now) and followed instructions. > > now dmesg says: > ucom0: on > uhub0 ucom0: configured 1 serial ports (U0.%d) > (much better, doesn't it) > > and /dev/cuaU0.0 is created when it is plugged in. However, I can't > stablish comunication with the modem. I tried with screen and minicom, > but nothing happens. Even stty reports: > > #stty -f /dev/cuaU0.0 -a > speed 9600 baud; 0 rows; 0 columns; > lflags: icanon isig iexten -echo -echoe -echok -echoke -echonl -echoctl > -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo > -extproc > iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk > brkint -inpck -ignpar -parmrk > oflags: opost onlcr -ocrnl -oxtabs -onocr -onlret > cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow > -dtrflow -mdmbuf > cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = ; > eol2 = ; erase = ^?; erase2 = ^H; intr = ^C; kill = ^U; > lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; > status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W; > > > > This is what I did: > > $ diff u3g.c original > 195,196d194 > < /* PRUEBA SILABS */ > < {{ USB_VENDOR_SILABS, USB_PRODUCT_SILABS_SAEL }, > U3GSP_GPRS, U3GFL_NONE }, > > and > > $ tail -1 usbdevs > product SILABS SAEL 0x8053 SA-EL USB > > > Is there anything else should I try? Any clue is good for me. > > Thank you > > Alberto Mijares > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to > "freebsd-hardware-unsubscribe@freebsd.org" From amijaresp at gmail.com Tue Feb 17 14:20:57 2009 From: amijaresp at gmail.com (Alberto Mijares) Date: Tue Feb 17 14:21:03 2009 Subject: Modem GSM/GPRS In-Reply-To: <200902172203.19534.nick@van-laarhoven.org> References: <286906750902130802q2ec86267ye5ae0832ab9a3aa4@mail.gmail.com> <200902132209.52793.hselasky@c2i.net> <286906750902140111i62d94f78w3921951f072cb930@mail.gmail.com> <200902172203.19534.nick@van-laarhoven.org> Message-ID: <286906750902171420h5815eaccp60e20abb0d097c21@mail.gmail.com> On Wed, Feb 18, 2009 at 4:33 PM, Nick Hibma wrote: > Alberto, > > Could you remove u3g again from your kernel, so the device attaches to ugen > and then dump its descriptors using usbgen? > > usbgen -f /dev/ugen0 -D > > where ugen0 is the device mentioned in the dmesg. > > Thanks. > > Nick > There is no such usbgen command in my system nor the ports tree (Am I lost in the moon?). Where can I find it? Is the following info useful to you? # udesc_dump /dev/ugen0 Standard Device Descriptor: bLength 18 bDescriptorType 01 bcdUSB 0110 bDeviceClass 00 bDeviceSubClass 00 bDeviceProtocol 00 bMaxPacketSize 64 idVendor 10c4 idProduct 8053 bcdDevice 0100 iManufacturer 1 iProduct 2 iSerialNumber 3 bNumConfigurations 1 Configuration 0: Standard Configuration Descriptor: bLength 9 bDescriptorType 02 wTotalLength 32 bNumInterface 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 80 bMaxPower 250 (500 mA) Standard Interface Descriptor: bLength 9 bDescriptorType 04 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass ff bInterfaceSubClass 00 bInterfaceProtocol 00 iInterface 2 Standard Endpoint Descriptor: bLength 7 bDescriptorType 05 bEndpointAddress 81 (in) bmAttributes 02 (Bulk) wMaxPacketSize 64 bInterval 0 Standard Endpoint Descriptor: bLength 7 bDescriptorType 05 bEndpointAddress 01 (out) bmAttributes 02 (Bulk) wMaxPacketSize 64 bInterval 0 Codes Representing Languages by the Device: bLength 4 bDescriptorType 03 wLANGID[0] 0409 String (index 1): Silicon Labs String (index 2): SA-EL USB String (index 3): 280RH70230396 Thank you. Alberto Mijares From amijaresp at gmail.com Tue Feb 17 14:45:20 2009 From: amijaresp at gmail.com (Alberto Mijares) Date: Tue Feb 17 14:45:27 2009 Subject: Modem GSM/GPRS In-Reply-To: <286906750902171420h5815eaccp60e20abb0d097c21@mail.gmail.com> References: <286906750902130802q2ec86267ye5ae0832ab9a3aa4@mail.gmail.com> <200902132209.52793.hselasky@c2i.net> <286906750902140111i62d94f78w3921951f072cb930@mail.gmail.com> <200902172203.19534.nick@van-laarhoven.org> <286906750902171420h5815eaccp60e20abb0d097c21@mail.gmail.com> Message-ID: <286906750902171445s24ab7d29s7cf8f2eedf0fa376@mail.gmail.com> On Wed, Feb 18, 2009 at 5:50 PM, Alberto Mijares wrote: > On Wed, Feb 18, 2009 at 4:33 PM, Nick Hibma wrote: >> Alberto, >> >> Could you remove u3g again from your kernel, so the device attaches to ugen >> and then dump its descriptors using usbgen? >> >> usbgen -f /dev/ugen0 -D >> >> where ugen0 is the device mentioned in the dmesg. >> >> Thanks. >> >> Nick >> > > There is no such usbgen command in my system nor the ports tree (Am I > lost in the moon?). Where can I find it? I'm sorry. I've been too lazy last days. I found it already (sysutils/usbutil). Here goes: # usbgen -f /dev/ugen0 -D DEVICE descriptor: bLength=18 bDescriptorType=1 bcdUSB=1.10 bDeviceClass=0 bDeviceSubClass=0 bDeviceProtocol=0 bMaxPacketSize=64 idVendor=0x10c4 idProduct=0x8053 bcdDevice=100 iManufacturer=1 iProduct=2 iSerialNumber=3 bNumConfigurations=1 Current configuration is number 1 CONFIGURATION descriptor index 0: bLength=9 bDescriptorType=2 wTotalLength=32 bNumInterface=1 bConfigurationValue=1 iConfiguration=0 bmAttributes=80 bMaxPower=500 mA INTERFACE descriptor index 0, alt index 0: bLength=9 bDescriptorType=4 bInterfaceNumber=0 bAlternateSetting=0 bNumEndpoints=2 bInterfaceClass=255 bInterfaceSubClass=0 bInterfaceProtocol=0 iInterface=2 ENDPOINT descriptor index 0: bLength=7 bDescriptorType=5 bEndpointAddress=1-in bmAttributes=2 wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor index 1: bLength=7 bDescriptorType=5 bEndpointAddress=1-out bmAttributes=2 wMaxPacketSize=64 bInterval=0 Seems the same info... Regards. Alberto Mijares From lawrence.auster at att.net Thu Feb 19 10:54:51 2009 From: lawrence.auster at att.net (Lawrence Auster) Date: Thu Feb 19 10:55:06 2009 Subject: "My race is just nothing": Some thoughts on the political psychology of women Message-ID: <20090219185445.XLRD4162.cdptpa-omta04.mail.rr.com@k4k6l> "My race is just nothing": Some thoughts on the political psychology of women By Kevin MacDonald February 19, 2009 It seems that the signs of white dispossession are everywhere these days. Edmund Connelly describes how non-Jewish whites are being pushed out of elite institutions like Harvard. An article titled “The end of white America” catalogues the lack of cultural confidence of whites these days. It quotes a student who says “To be white is to be culturally broke." Writing in vdare.com, David A. Yeagley quotes one of his female students saying “Look ... I don’t see anything about my culture to be proud of. It’s all nothing. My race is just nothing.” Yeagley notes the Cheyenne saying, “A nation is never defeated until the hearts of its women are on the ground.” And he places this in the context of the recent election in which 46% of white women voted for Obama compared to 41% of white men. These percentages are somewhat inflated because they include Jews and immigrants, such as South Asians, who are classified as white but do not identify with the European-American majority. Nevertheless, they do point to a significant gender gap. While it is certainly true that voting for McCain-Palin is not a sign of white consciousness — even implicitly, it is also the case that voting for Obama is a good sign of a lack of racial consciousness for European Americans. The good news, of course, is that a majority of white women did not vote for Obama. And, as Steve Sailer has shown for the 2004 election, if one separated out women who are married and have children, the results would show an even greater tendency to vote against Obama. Nevertheless, there is a real problem. Those of us with some acquaintance with European-Americans who do have an explicit ethnic identity and a sense of their ethnic interests are quite aware that there is a very large sex ratio imbalance at gatherings of like-minded people. The attendees are almost all male — an exception being the redoubtable Virginia Abernethy. And there are stories of men who have stopped attending meetings or who provide support only in the most furtive manner, mainly because their wives are afraid that the attitudes of their husbands could become public and ruin their social life. Making such things public is just the sort of thing that organizations like the SPLC and the ADL love to do. Judith Warner of the New York Times describes the result of an informal "email inquiry" on women's reactions to Obama. Some imagined having sex with Obama and replacing Michelle Obama as First Lady. Others imagined themselves at social engagements with Obama. All wanted deeply to have some of the Obama aura rub off on them. Warner's email contacts doubtless reflect her liberal readership, but I wouldn't be at all surprised if they are quite general, especially among white women who voted for Obama. What does an evolutionary psychologist say about all this? Parenthetically, I realize that the great majority of Americans do not believe in evolution. Nevertheless, evolutionary theory is a very powerful and scientifically credible way of looking at human behavior. It is no accident that one of the main strands of Jewish intellectual activism over the last century has been to oppose evolutionary theory as an explanatory tool in the social sciences. Darwin did indeed have a dangerous idea — dangerous to Jews because it provides a rational grounding for the ethnic identity and interests of European-derived people. The evolutionary theory of sex is one of the bedrocks of evolutionary psychology — probably accounting for half of all the research in the field. The basic idea is simple: Females invest a relatively large amount of time and energy in reproduction. In the world we evolved in, the only way for women to reproduce was to endure a 38-week pregnancy and then nurse the child for an even longer period. Even after nursing, child care was mainly a female responsibility. Because women are committed to this very large investment, they become very valuable in the mating game. And because they are valuable, they become discriminating maters: Just as a worker who puts in more time and energy is in a better bargaining position than one who puts in little time and energy, women become the choosers in the mating game. And what do women want? Women are expected to want men who have high social status. From an evolutionary perspective, such men are attractive because they may be willing to provide valuable resources that would help in supporting the mother and raising the children. (When men do contribute resources, they also become choosy, but that's another story.) And even if a wealthy man does not provide resources, he is likely to have good genes — genes that predispose his children to be successful. In any case, women do indeed prefer wealthy, high-status men. For example, a recent study found that wealthy men give women more orgasms: "The pleasure women get from making love is directly linked to the size of their partner’s bank balance." Other research shows that women are likely to choose higher status men than their husbands when they have affairs, resulting in the possibility of a lower status male helping to raise the children of a higher-status male. What about the idea that evolutionary theory implies that people should be attracted to people who are genetically like themselves? Evolutionary theory predicts that women will be attracted to men who are genetically similar to themselves compared to men who are from a different race or ethnic group. For one thing, this makes them more closely related to their own children. The problem is that this attraction to genetically similar mates is only part of the story. It must compete with the tendency to be attracted to wealthy, powerful men. And quite clearly, the phenomenon where large numbers of white women fantasize about having a relationship with Obama reflects his power and social status, not attraction to a genetically similar person. The media is a major part of the hostile elite, so it is not surprising that it has played a leading role in the idolization of Obama — the slobbering love affair between the mainstream media and Obama. It's the same role that Edmund Connelly has called attention to in his writing on the images of blacks created by Hollywood in recent decades. Black action heroes are now household names, and more than one commentator has pointed out that there were several black presidents in the movies and on television long before Obama was elected. These images from the media tap into women's psychological attraction to high-status males. It was probably fairly common for white women to fantasize about having sex with Will Smith or Denzel Washington or even the "wise and saintly" Morgan Freeman long before the world had ever heard of Barack Obama. Another sex difference that contributes to women's political behavior is that women are generally more nurturant, affectionate, empathic, and caring than men. This is another aspect of female psychology that can easily be derived from evolutionary thinking — the vital importance of nurturing children and developing close family relationships in our evolutionary past. Thus it is not surprising that many of Judith Warner's women not only fantasize about having sex with Obama, they see themselves married to him and becoming first lady. They develop a close and caring relationship with him, or they see him as a good friend. I suppose this is also the reason why women are more likely than men to support social programs that promise to aid children and poor people. This relatively greater empathy and nurturance was certainly adaptive in a world of family groups and close relatives. But in the modern world, it can easily lead to maladaptive altruism and ignoring real dangers. For example, white women enamored of images of sexy, high-status black males are not informed by the mainstream media of the very large racial imbalance in crime, particularly black men raping white women. Another problem with women being relatively high in nurturance and empathy is that these traits are linked to greater compliance and greater inclination to seek the approval and affection of others. Again, these are very adaptive traits in the world of small groups and close relatives. But in a world dominated by elites that are hostile to the interests of whites, these traits can lead to mindless acceptance of anti-white cultural norms. Challenging social norms — even ones that are obviously against one's interests — carries a very high psychological cost to people who seek the approval and affection of others. This implies that once the intellectual and political movements described in The Culture of Critique had seized the intellectual and moral high ground, they became difficult indeed to dislodge. Challenging these norms brings accusations of moral turpitude ringing down from the most prestigious political, media and academic institutions of the society. People who seek the approval and affection of others are definitely not inclined to go there. This in turn may well be a large part of the explanation for why there are so few women at gatherings of European-Americans concerned about the future of their people and culture. This paints a fairly bleak picture. But there are some rays of hope. It is likely that at some point the gap between rhetoric and reality in American life will be so large that no one will believe what they are hearing from the hostile elites that dominate public discourse — much like the Soviet Union in the decades before its fall. When that happens, the cultural icons promoted by the media will lose their credibility and allure as well. And because of the internet, the opportunity to hear divergent opinions and become aware of information that is suppressed by the mainstream media has never been better. All around us we can see the collapse and increasing irrelevance of the old media. The internet has already created communities where prestige and social approval can be obtained completely outside the norms created by our hostile elites. And at least some of these communities are dedicated to transforming America by asserting the legitimacy of white identities and interests. The dispossession of whites is already substantial, but it promises to be a whole lot more obvious as time goes on. As whites become a minority, it is difficult to imagine that they won't develop more of a group consciousness and challenge the prevailing anti-white norms. And that includes even the more nurturant and empathic among us. Source with hyperlinks : http://www.theoccidentalobserver.net/articles/MacDonald-Women.html ------------------------------------- You or someone using your email adress is currently subscribed to Lawrence Auster's Newletter. If you wish to unsubscribe from our mailing list, please let us know by calling to 1 212 865 1284 Thanks, Lawrence Auster, 238 W 101 St Apt. 3B New York, NY 10025 Contact : lawrence.auster@att.net ------------------------------------- From freebsd at sopwith.solgatos.com Tue Feb 24 21:08:17 2009 From: freebsd at sopwith.solgatos.com (Dieter) Date: Tue Feb 24 21:08:24 2009 Subject: Inexpensive, low power, "wall wart" computer Message-ID: <200902250014.AAA10463@sopwith.solgatos.com> http://linuxdevices.com/news/NS9634061300.html This looks promising: a $100 ($50 in volume) 5 Watt computer. 1.2GHz CPU, 512MB each of RAM and Flash Marvell 88F6281 "Kirkwood" SoC gigabit Ethernet and USB 2.0 ports Looks like the SoC also has a 2nd Ethernet port, 2 SATA parts, PCIe and other stuff that isn't brought out for some reason. http://linuxdevices.com/files/misc/marvell_88F6000_diagram.gif Anyone have an idea how much work it would take to get BSD running on this thing? Get the 2nd Ethernet working and have a 5 Watt firewall for personal and SOHO use. (Obviously you aren't going to run a Fortune-500 company through this thing.) Or use it as a USB device server. Bring the SATA ports out and make a small NAS. And so on. Unfortunately I don't see firewire listed. :-( From rb at gid.co.uk Wed Feb 25 00:11:10 2009 From: rb at gid.co.uk (Bob Bishop) Date: Wed Feb 25 00:11:26 2009 Subject: Inexpensive, low power, "wall wart" computer In-Reply-To: <200902250014.AAA10463@sopwith.solgatos.com> References: <200902250014.AAA10463@sopwith.solgatos.com> Message-ID: <8ED9DBAC-B393-4856-861B-CB48E58E62CC@gid.co.uk> Hi, On 24 Feb 2009, at 16:14, Dieter wrote: > http://linuxdevices.com/news/NS9634061300.html > [...] > Anyone have an idea how much work it would take to get > BSD running on this thing? [etc] Looks like there is work in progress, see: http://www.bsdcan.org/2008/schedule/attachments/50_2008_marvell_freebsd.pdf -- Bob Bishop rb@gid.co.uk From bsdgroup.md at gmail.com Thu Feb 26 09:20:06 2009 From: bsdgroup.md at gmail.com (Rusu Silviu) Date: Thu Feb 26 09:20:16 2009 Subject: Extremely slow read/write speed, 7.1 Release on Intel ICH9 SATA Message-ID: Extremely slow read/write speed, 7.1 Release on Intel ICH9 SATA Should i send this to freebsd-fs list? Have 3 HDDs - 160G Seagate Serial ATA v1.0, 3 partitions: 1 - system, 2 - data, 3 - storage, soft updates on for all partitions - 750G Samsung Serial ATA II, 1 partition, soft updates on - 1000G Samsung Serial ATA II, 1 partition, soft updates on hw.ata.wc=1 Mobo is an ASUS P5KR, P35/ICH9 Buyed it cause `man ata' says ICH9 is supported There are also Jmicron eSATA/PATA controller, that i actually disabled No overclocking dd if=/dev/ad4 of=/dev/null iostat -w1 ad4 tty ad4 cpu tin tout KB/t tps MB/s us ni sy in id 47 48 1.65 252 0.40 6 0 1 1 92 1 251 0.50 12650 6.18 2 0 15 14 69 0 88 0.50 12583 6.15 3 0 18 12 67 0 87 0.50 12641 6.17 3 0 18 12 68 0 87 0.51 12614 6.23 2 0 19 12 67 0 87 0.50 12619 6.16 3 0 16 13 68 0 87 0.50 12634 6.17 2 0 18 11 70 0 87 0.50 12644 6.17 4 0 16 13 67 0 87 0.52 12545 6.39 3 0 19 12 67 0 87 0.50 12612 6.16 3 0 15 12 70 0 87 0.50 12578 6.14 2 0 14 14 71 dd if=/dev/ad6 of=/dev/null iostat -w1 ad6 tty ad6 cpu tin tout KB/t tps MB/s us ni sy in id 48 47 7.58 15 0.11 6 0 1 1 92 1 251 0.52 7777 3.93 3 0 12 8 77 0 86 0.52 7779 3.95 3 0 9 10 79 0 86 0.51 7786 3.91 0 0 9 7 84 0 86 0.52 7842 3.98 3 0 11 7 79 0 86 0.51 8084 4.05 2 0 9 7 82 0 86 0.52 7395 3.74 2 0 12 9 77 0 86 0.51 7735 3.88 3 0 11 7 79 1 86 0.52 7810 3.95 2 0 11 10 77 dd if=/dev/ad12 of=/dev/null iostat -w1 ad12 tty ad12 cpu tin tout KB/t tps MB/s us ni sy in id 48 47 0.68 12 0.01 5 0 2 1 92 1 253 0.50 7694 3.76 3 0 9 9 79 0 85 0.50 7642 3.73 2 0 9 8 81 0 85 0.50 7575 3.70 1 0 10 6 83 0 85 0.50 7598 3.71 2 0 10 11 77 0 86 0.50 7577 3.70 3 0 11 8 79 0 85 0.50 7606 3.71 3 0 6 9 83 1 85 0.50 7620 3.72 2 0 9 8 81 df -h Filesystem Size Used Avail Capacity Mounted on /dev/ad4s1a 2.1G 139M 1.8G 7% / devfs 1.0K 1.0K 0B 100% /dev /dev/ad4s1e 2.1G 1.8M 2.0G 0% /tmp /dev/ad4s1f 32G 3.6G 26G 12% /usr /dev/ad4s1d 2.1G 212M 1.7G 11% /var /dev/ad4s2 21G 1.7G 18G 8% /data /dev/ad4s3 82G 29G 47G 38% /storage /dev/ufs/hdd1 677G 498G 124G 80% /hdd1 /dev/ufs/hdd2 902G 445G 385G 54% /hdd2 ========dmesg========= CPU: Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz (2208.29-MHz 686-class CPU) ... real memory = 2146959360 (2047 MB) ... atapci0: port 0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xb480-0xb483,0xb400-0xb41f mem 0xfe8fe800-0xfe8fefff irq 22 at device 31.2 on pci0 atapci0: [ITHREAD] atapci0: AHCI Version 01.20 controller with 6 ports detected ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] ata5: on atapci0 ata5: [ITHREAD] ata6: on atapci0 ata6: [ITHREAD] ata7: on atapci0 ata7: executing CLO failed ata7: [ITHREAD] ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata0: [ITHREAD] ata1 at port 0x170-0x177,0x376 irq 15 on isa0 ata1: [ITHREAD] ad4: 152626MB at ata2-master SATA150 ad6: 715404MB at ata3-master SATA300 ad12: 953869MB at ata6-master SATA300 =========pciconf=========== atapci0@pci0:0:31:2: class=0x010601 card=0x82771043 chip=0x29228086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801IB/IR/IH (ICH9 Family) 6 port SATA AHCI Controller' class = mass storage cap 05[80] = MSI supports 16 messages cap 01[70] = powerspec 3 supports D0 D3 current D0 cap 12[a8] = unknown cap 09[b0] = vendor (length 6) Intel cap 2 version 0 ============atacontrol============= atacontrol cap ad4 Protocol Serial ATA v1.0 device model ST3160815AS serial number 5RA737SD firmware revision 4.AAB cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 312579695 sectors dma supported overlap not supported Feature Support Enable Value Vendor write cache yes yes read ahead yes yes Native Command Queuing (NCQ) yes - 31/0x1F Tagged Command Queuing (TCQ) no no 31/0x1F SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management no no 65278/0xFEFE automatic acoustic management no no 0/0x00 208/0xD0 atacontrol cap ad6 Protocol Serial ATA II device model SAMSUNG HD753LJ serial number S13UJ1BQ802853 firmware revision 1AA01113 cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 1465149168 sectors dma supported overlap not supported Feature Support Enable Value Vendor write cache yes yes read ahead yes yes Native Command Queuing (NCQ) yes - 31/0x1F Tagged Command Queuing (TCQ) no no 31/0x1F SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management yes no 0/0x00 automatic acoustic management yes yes 254/0xFE 254/0xFE atacontrol cap ad12 Protocol Serial ATA II device model SAMSUNG HD103UJ serial number S13PJ1NQA01054 firmware revision 1AA01113 cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 1953525168 sectors dma supported overlap not supported Feature Support Enable Value Vendor write cache yes yes read ahead yes yes Native Command Queuing (NCQ) yes - 31/0x1F Tagged Command Queuing (TCQ) no no 31/0x1F SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management yes no 0/0x00 automatic acoustic management yes yes 254/0xFE 254/0xFE atacontrol list ATA channel 0: Master: no device present Slave: no device present ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: ad4 Serial ATA v1.0 Slave: no device present ATA channel 3: Master: ad6 Serial ATA II Slave: no device present ATA channel 4: Master: no device present Slave: no device present ATA channel 5: Master: no device present Slave: no device present ATA channel 6: Master: ad12 Serial ATA II Slave: no device present ATA channel 7: Master: acd0 Serial ATA v1.0 Slave: no device present Thank you. From bosbsd at hotmail.com Sat Feb 28 18:23:00 2009 From: bosbsd at hotmail.com (not avail) Date: Sat Feb 28 18:23:06 2009 Subject: Sony Optiarc CD/DVD Drive problem Message-ID: Hello FreeBSD Hardware, I have a dell studio hybrid that I've been trying to set up for someone with FBSD 7.1. The Problem: The install disk would hang during a probe of the CD/DVD drive with that repeated message about ' x seconds waiting for xpt_config,' and would have to be powered off manually. The Solution: Installing FBSD 7.1 to a usb flash drive, and recompiling the kernel without the ATAPI line got the flash drive system fully functional. What I'm Hoping For: To understand the problem more clearly. Ideally I'd like to help to debug the problem between the freebsd component and this particular drive. I know access to hardware can be a limitation for project developers, but I'm willing to conduct any tests, and provide any information I can. I hate to see something as critical for installation as a CD drive failing for new hardware. The problem CD/DVD drive: Sony Optiarc DVDRW / BDROM BC-5600S 104B (no firmware updates available as of today at sony's website.) Error Codes: The error code that would get printed twice was asc=0x64 ascq=0x00. _________________________________________________________________ Hotmail? is up to 70% faster. Now good news travels really fast. http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_70faster_032009