Internal Error 0x0b Interface Config Missing New Online
Some screenshots of what is possible today. Imagine the future.
The visualisation and simulation platform focused on what matters to you.
Geppetto is a web-based visualisation and simulation platform to build neuroscience software applications. Reuse best practices, best compomnents, best design. Don't reinvent the wheel.
Engineered together with scientists, Geppetto lets you integrate different data and models. A modular architecture allows the platform to easily support different standard formats for both experimental and computational data.
Geppetto is entirely open source and engineers, scientists and developers from different research groups are contributing to its development by adding functionality to visualize and simulate new data and models.
Few error messages are as frustrating—or as cryptic—as the one staring back at you from a black terminal or a frozen system dialog: "Internal Error 0x0b Interface Config Missing New."
At first glance, it reads like a fragment of a developer’s debugging note rather than a user-facing alert. The hexadecimal code 0x0b (which is decimal 11), the mention of an “interface config,” and the oddly placed word “new” at the end create a perfect storm of confusion. For system administrators, embedded engineers, and even seasoned Windows or Linux users, this error represents a breakdown in communication between software components.
This article will dissect the error from every angle. We will explore what 0x0b means in computing, why an interface configuration would be considered “missing,” what the word “new” signifies in this context, and—most importantly—how to diagnose and resolve the issue permanently.
Symptom: dmesg showed usb 1-2: configuration #1 chosen but interface config missing new (0x0b).
Solution: The power management script didn’t reset the USB bus properly. Fix:
sudo sh -c "echo on > /sys/bus/usb/devices/usb1/power/control"
Then disable USB autosuspend in tlp or powertop.
Let’s break the phrase down word by word:
In the USB specification, endpoint 0x0B is sometimes reserved for control or diagnostic pipes. In SCSI (used by storage devices), sense code 0x0B indicates “WARNING – reported errors may be inaccurate.” In many real-time OSes, error code 11 (0x0B decimal) is defined as ENOENT (Error NO ENTry). That strongly suggests the system looked for an interface configuration entry by name or ID and found nothing.
If you are the developer hitting this error:
Example pseudo-fix in C++ (Linux kernel style):
struct iface_config *cfg = kzalloc(sizeof(*cfg), GFP_KERNEL);
if (!cfg)
pr_err("0x0b interface config missing new - ENOMEM\n");
return -ENOMEM;
// Proceed with cfg
Some screenshots of what is possible today. Imagine the future.
Help us build the next generation simulation platform!
Geppetto is entirely open source and is being built by a growing community of talented engineers and scientists. Geppetto uses different languages to achieve different goals. Its core and back-end are built in Java to provide a solid and performant infrastructure. The front-end is built using the latest HTML5 and Javascript. Geppetto is being developed using the Eclipse platform and uses technologies like OSGi, Spring Framework, and Maven. Geppetto's model abstraction is defined using ecore and all the model code is generated using EMF. Geppetto's front-end is written using THREE.js, React and Backbone. The back-end and the front-end communicate by exchanging JSON messages through WebSocket. Geppetto runs on the Eclipse Virgo WebServer and can be deployed on different infrastructures including cloud-based ones like Amazon EC2. Anything sound familiar? internal error 0x0b interface config missing new
Geppetto is multi-platform and works on Linux, Mac OSX and Windows, so no matter on what platform you develop there is a way for you to run it and add fantastic contributions. Few error messages are as frustrating—or as cryptic—as
Show me the code!
Right! Geppetto is hosted on GitHub, every module has its own repository to provide flexible ways of branching individual components. For every module we have at least two branches, development and master. The development branch gets merged into master each monthly release. If you want to contribute you can either go straight to the code or reach out to us dropping an , we will show you around and help you contribute in your favorite way! Then disable USB autosuspend in tlp or powertop
Source code Docs Development boardFew error messages are as frustrating—or as cryptic—as the one staring back at you from a black terminal or a frozen system dialog: "Internal Error 0x0b Interface Config Missing New."
At first glance, it reads like a fragment of a developer’s debugging note rather than a user-facing alert. The hexadecimal code 0x0b (which is decimal 11), the mention of an “interface config,” and the oddly placed word “new” at the end create a perfect storm of confusion. For system administrators, embedded engineers, and even seasoned Windows or Linux users, this error represents a breakdown in communication between software components.
This article will dissect the error from every angle. We will explore what 0x0b means in computing, why an interface configuration would be considered “missing,” what the word “new” signifies in this context, and—most importantly—how to diagnose and resolve the issue permanently.
Symptom: dmesg showed usb 1-2: configuration #1 chosen but interface config missing new (0x0b).
Solution: The power management script didn’t reset the USB bus properly. Fix:
sudo sh -c "echo on > /sys/bus/usb/devices/usb1/power/control"
Then disable USB autosuspend in tlp or powertop.
Let’s break the phrase down word by word:
In the USB specification, endpoint 0x0B is sometimes reserved for control or diagnostic pipes. In SCSI (used by storage devices), sense code 0x0B indicates “WARNING – reported errors may be inaccurate.” In many real-time OSes, error code 11 (0x0B decimal) is defined as ENOENT (Error NO ENTry). That strongly suggests the system looked for an interface configuration entry by name or ID and found nothing.
If you are the developer hitting this error:
Example pseudo-fix in C++ (Linux kernel style):
struct iface_config *cfg = kzalloc(sizeof(*cfg), GFP_KERNEL);
if (!cfg)
pr_err("0x0b interface config missing new - ENOMEM\n");
return -ENOMEM;
// Proceed with cfg