Language Selection

English French German Italian Portuguese Spanish

The Heat Is On

Filed under
Hardware

The deadline for the European Union’s Restriction of Hazardous Substances (RoHS) now looms less than a year away. Meanwhile, the EU has put an Aug. 13, 2005 deadline on registering for its Waste Electrical and Electronic Equipment (WEEE) directive. Aside from the EU’s 25 member states, both China and California have their own set of rules in the works that will force suppliers to provide more environmental sound products, with the common factor to all countries being a push toward lead-free electronics.

Is the industry ready for RoHS, which is set to hit first with a July 1, 2006 deadline marked on supply-chain calendars? The answer, according to Fern Abrams, director of environmental policy at IPC – Association Connecting Electronics Industries, is a resounding “No.”

“They [suppliers] may very well be ready in a year – there’s a lot of resources and talent and energy being put to this – but it’s an uphill battle.

“A year ago we really thought most of the problems were of a technical nature. What we are finding this year is companies that addressed those early on are in good shape, but they are still working to flush out their supply chain and in places where they have a critical component that they can’t find in lead-free or they can’t get information on their supplier’s compliance plans. So it’s a management data/flow type of problem,” she said.

Abrams doesn’t necessarily put the blame on companies, however. She notes that the EU hasn’t been crystal clear on its interpretations.

She further noted that not all 25 EU countries have yet passed their own regulations to implement RoHS, so specific laws are not set. And, on the WEEE end, a registration deadline is set for next month with only a small handful of countries establishing registries and rules for procedures, IPC noted.

Despite its obstacles, those who did move ahead on RoHS could have a significant advantage. Advanced Micro Devices, for one, this month announced several of its processors and chipsets, including the Opteron, Athlon 64, AMD-8111 and AMD-8151, are compliant to the RoHS directive. In its efforts, AMD began the move to reduced lead back in 2001.

“We’re in a very complex industry where, for example, a PC has many different parts. Our customers have been involved in supply-chain management processes to make sure their suppliers are ready, and clearly, suppliers to maintain that business are going to have to demonstrate they are ready. That’s one of the reasons we started as early as we did,” Reed Content, senior EHS manager, in AMD's global EHS department, said.

Based on the fact that it took AMD, well-known for its green efforts and one of the industries most advanced companies, four years to reach RoHS compliance for reduced lead in its technologies, many other members of the supply chain that have not advanced as far – or not even started on their RoHS efforts – could be facing some tough hurdles in the months to come.

Full Story.

More in Tux Machines

15 books for kids who (you want to) love Linux and open source

In my job I've heard professionals in tech, from C-level executives to everyone in between, say they want their own kids to learn more about Linux and open source. Some of them seem to have an easy time with their kids following closely in their footsteps. And some have a tough time getting their kids to see what makes Linux and open source so cool. Maybe their time will come, maybe it won't. There's a lot of interesting, valuable stuff out there in this big world. Read more

Security: VPNFilter, Encryption in GNU/Linux, Intel CPU Bug Affecting rr Watchpoints

  • [Crackers] infect 500,000 consumer routers all over the world with malware

    VPNFilter—as the modular, multi-stage malware has been dubbed—works on consumer-grade routers made by Linksys, MikroTik, Netgear, TP-Link, and on network-attached storage devices from QNAP, Cisco researchers said in an advisory. It’s one of the few pieces of Internet-of-things malware that can survive a reboot. Infections in at least 54 countries have been slowly building since at least 2016, and Cisco researchers have been monitoring them for several months. The attacks drastically ramped up during the past three weeks, including two major assaults on devices located in Ukraine. The spike, combined with the advanced capabilities of the malware, prompted Cisco to release Wednesday’s report before the research is completed.

  • Do Not Use sha256crypt / sha512crypt - They're Dangerous

    I'd like to demonstrate why I think using sha256crypt or sha512crypt on current GNU/Linux operating systems is dangerous, and why I think the developers of GLIBC should move to scrypt or Argon2, or at least bcrypt or PBKDF2.

  • Intel CPU Bug Affecting rr Watchpoints
    I investigated an rr bug report and discovered an annoying Intel CPU bug that affects rr replay using data watchpoints. It doesn't seem to be hit very often in practice, which is good because I don't know any way to work around it. It turns out that the bug is probably covered by an existing Intel erratum for Skylake and Kaby Lake (and probably later generations, but I'm not sure), which I even blogged about previously! However, the erratum does not mention watchpoints and the bug I've found definitely depends on data watchpoints being set. I was able to write a stand-alone testcase to characterize the bug. The issue seems to be that if a rep stos (and probably rep movs) instruction writes between 1 and 64 bytes (inclusive), and you have a read or write watchpoint in the range [64, 128) bytes from the start of the writes (i.e., not triggered by the instruction), then one spurious retired conditional branch is (usually) counted. The alignment of the writes does not matter, and it's not related to speculative execution.

In Memoriam: Robin "Roblimo" Miller, a Videographer and Free Software Champion

Videographer Robin Roblimo Miller

Robin "Roblimo" Miller was a clever, friendly, and very amicable individual who everyone I know has plenty of positive things to say about. I had the pleasure of speaking to him for several hours about anything from personal life and professional views. Miller was a very knowledgeable person whose trade as a journalist and video producer I often envied. I have seen him facing his critics in his capacity as a journalist over a decade ago when he arranged a debate about OOXML (on live radio). Miller, to me, will always be remembered as a strong-minded and investigative journalist who "did the right thing" as the cliché goes, irrespective of financial gain -- something which can sometimes be detrimental to one's longterm health. Miller sacrificed many of his later years to a cause worth fighting for. This is what we ought to remember him for. Miller was - and always will be - a FOSS hero.

May everything you fought for be fulfilled, Mr. Miller. I already miss you.

Today in Techrights