Industrial Engineer - Foundry Strategic Capacity

Intel said Wednesday it has installed the first major structural truss at its Ohio chip factory, a construction milestone for a project years behind schedule. The Ohio project, with planned investments above $28 billion, was first expected to produce chips in late 2025. Intel now expects to finish the first Ohio factory in 2030, with operations starting between 2030 and 2031. The second factory should be complete in 2031, with operations starting in 2032. The company has slowed construction to match spending with customer demand. At its Fab 62 site in Arizona, construction and equipment installation are underway, with operations due by the end of 2028. Intel Foundry posted second-quarter revenue of $5.8 billion, up 31%, and an operating loss of about $2.1 billion. Most of that revenue came from within Intel.

Two Intel workers die in gas explosion at Kiryat Gat fab in Israel. Ilya Chechulin, 49, and Yakir Kosashvili, 35, died after an NF3 tank failed during unloading at Intel's Fab 28; a third worker remains on a ventilator as the company stays silent on output. A suspected tank failure during unloading at one of Intel's most important chip plants killed two workers days before the company has to explain its production numbers to Wall Street. Intel's Kiryat Gat facility in southern Israel was the backdrop for a visit by Prime Minister Benjamin Netanyahu on October 14 when an explosion tore through the site's gas delivery area. Police said a gas cylinder appeared to have malfunctioned during unloading, and Israel's Fire and Rescue Services later confirmed the incident involved nitrogen trifluoride, or NF3, a toxic but non-flammable compound used in semiconductor manufacturing. Two workers are dead. A third remains in critical condition. According to the Times of Israel, the first victim, Ilya Chechulin, 49, died of his wounds a day after the blast. Ynet identified the second man who died as Yakir Kosashvili, 35. Both suffered severe burns in the explosion and fire that followed. A third worker, a man in his 20s, remains sedated and on a ventilator in intensive care, according to Ynet's reporting. Calcalistech reported that preliminary findings point to a technical failure in the neck of a tank holding roughly 8 tons of NF3 at the time of the incident. Police said there was no indication the blast was an attack and that investigators suspected a technical malfunction during the transfer of material into the factory's tanks. The explosion happened on a day the country's prime minister was touring the city. Kiryat Gat isn't a minor node in Intel's network. Fab 28 there makes processors along with 5G and AI-related components, and it's one of the sites Intel has pointed to as it tries to rebuild manufacturing credibility after years of delays and cost overruns. Intel has also been expanding a second plant on the same campus, Fab 38, though construction was paused in 2024. A facility already carrying extra weight in Intel's turnaround story just became the site of a fatal industrial accident. Commerce Secretary Howard Lutnick has asked a Delaware court to dismiss a lawsuit alleging the US government's 9.9% stake in Intel amounted to an illegal seizure. He's defending the deal as vital to national security, and hinting defense contractors could be next. - how to dismiss lawsuit over government Intel stake - Commerce Secretary Lutnick fights Delaware corruption charges Intel Here's the uncomfortable part for investors: Intel hasn't said whether Kiryat Gat's output was affected, or for how long. On October 19, the company said its monitoring systems detected another NF3 leak during preparations to remove gas tanks from the site; no injuries were reported, but Intel still provided no production-impact figures. Gotrade reported that Intel shares fell 2.8% to $95.37 on October 15, one day after the explosion, amid concern about the blast and a broader chip selloff. The stock fell another 5.8% to $89.85 on October 16 before closing at $92.03 on October 19. Intel reports third-quarter results on October 29, according to the company's own investor relations announcement, with a call scheduled for 2 p.m. Pacific that day. That's fifteen days after the explosion and still no public word on whether wafer output, yield, or shipment timelines out of Kiryat Gat took a hit. Executives will have to address it on the call whether they want to or not, and investors will be listening for a number, not a sentiment. A single accident, a jittery sector. The timing is rough beyond Intel's own balance sheet. Chip stocks have been skittish for weeks on memory shortages and swings in AI infrastructure spending, and a fatal accident at a facility that makes both consumer processors and AI-adjacent components lands right in that nervousness. Everyone talks about the AI hardware buildout in abstractions, capacity, yield, roadmap. But it still runs through physical buildings where tanks of toxic gas are unloaded, and where a suspected tank failure can kill two people and rattle investors. Frankly, the most telling fact right now isn't the stock move. It's that a company sophisticated enough to run earnings calls down to the minute hasn't managed one sentence on whether its chips are still coming out of Kiryat Gat on schedule. Grief and operational disclosure aren't the same thing, and Intel owes its workforce one and its shareholders the other. On October 29, it runs out of room to give neither. Join the discussion. No replies yet. Start the discussion. Julian Lim is an entrepreneur, technology writer, and a researcher. He started JL Data Analysis after graduating from NUS in Intelligent Systems. Julian writes about technology innovations and entrepreneurship on Business Times, Asia Pacific Magazine and occasionally contributes to Startup Fortune.

Intel XeSS could soon deliver better performance on Linux as Intel works to enable XMX acceleration through Valve's Proton. Intel is working on improving XeSS (Xe Super Sampling) support on Linux, with a new series of patches aiming to enable hardware-accelerated XeSS upscaling through Valve's Proton compatibility layer. The proposed changes would allow supported Intel Arc GPUs to take advantage of their dedicated XMX (Xe Matrix eXtensions) engines when running Windows games on Linux, potentially delivering substantially better upscaling performance. As reported by Phoronix, Intel engineer Damian Tomczak has submitted four interconnected pull requests targeting Proton, Wine, VKD3D-Proton, and DXVK. Together, these changes address a longstanding limitation that has prevented XeSS from fully utilizing Intel's dedicated AI acceleration hardware in Windows games running through Proton. Currently, XeSS can operate through a slower fallback path under Proton, meaning Intel GPU owners may not benefit from the more efficient XMX-accelerated implementation available on Windows. The proposed solution introduces a built-in libxess.dll runtime within Wine that forwards Direct3D12 XeSS calls to the native Linux XeSS library (libxess.so), allowing workloads to execute through the accelerated path. The Wine pull request explains that Direct3D 12 objects are translated into Vulkan objects through VKD3D-Proton's interoperability interface, enabling the native XeSS implementation to operate within Proton's existing graphics translation infrastructure. Accompanying changes to VKD3D-Proton ensure that the necessary Vulkan extensions and device features are enabled, while DXVK receives adjustments to prevent Intel GPUs from being incorrectly hidden from games when Proton supplies its own XeSS library. Meanwhile, the Proton-specific implementation handles library selection and compatibility. Proton will search for a suitable native Linux XeSS library, including user-specified locations, and only use it when its version meets or exceeds the version required by the game. Otherwise, the game will continue using its existing Windows XeSS DLL. This approach should preserve compatibility while unlocking the faster hardware-accelerated XeSS implementation wherever the necessary Intel hardware and software support are available. It's worth emphasizing that this development concerns XeSS Super Resolution's XMX acceleration, rather than introducing the entire XeSS feature suite to Linux. It also primarily benefits compatible Intel Arc GPUs equipped with XMX engines, rather than GPUs from AMD or NVIDIA. The four pull requests remain under review and have not yet been merged, so there is currently no confirmed release date for the improvements. Nevertheless, this is a welcome development for Intel Arc owners gaming on Linux, particularly as Proton continues to narrow the compatibility and performance gaps between Windows and Linux gaming. If successfully implemented, the changes could finally allow Intel's dedicated XMX hardware to deliver its intended XeSS performance advantages in Windows games running through Proton. About the author: Sebastian Castellanos is a data scientist by education and training. He's also deeply passionate about PC gaming hardware and software. He has recently started writing technical articles and guides on Wccftech about PC hardware, games and mods. Follow Wccftech on Google to get more of its news coverage in your feeds.