Arch Linux

bwat47

Member

Registered: 2009-10-07

Posts: 638

i2400m_usb boot errors after today's updates

Since today's updates to initscripts, kmod, udev and mkinitcpio I've gotten a significant delay in boot time and these errors:

[brandon@brandon-arch ~]$ dmesg | grep 2400
[    6.937508] i2400m_usb 1-1.1:1.0: WiMAX interface wmx0 (64:d4:da:04:85:0c) ready
[   38.161789] i2400m_usb 1-1.1:1.0: boot-mode cmd -1: error waiting for an ack: -4
[   38.161828] i2400m_usb 1-1.1:1.0: bootrom init failed: -4
[   38.161850] i2400m_usb 1-1.1:1.0: i6050-fw-usb-1.5.sbcf: cannot use: -4, skipping
[   38.161942] i2400m_usb 1-1.1:1.0: Could not find a usable firmware image
[   38.161971] i2400m_usb 1-1.1:1.0: cannot bootstrap device: -4
[   38.208629] i2400m_usb 1-1.1:1.0: cannot setup device: -4
[   38.208685] i2400m_usb: probe of 1-1.1:1.0 failed with error -4
[   38.208733] usbcore: registered new interface driver i2400m_usb

Anyone else getting this? Anyway around it? Its adding like 15 seconds to my boot time.

Last edited by bwat47 (2012-01-21 06:40:17)

invented

Member

Registered: 2009-01-11

Posts: 10

Re: i2400m_usb boot errors after today's updates

Have the same issue

sleekslush

Member

Registered: 2012-01-15

Posts: 10

Re: i2400m_usb boot errors after today's updates

I can also say that I have the exact issue. I got these messages on a recently upgraded machine as well as a completely fresh install. Adds a nice 30s of boot time.

[    4.234295] i2400m_usb 2-1.3:1.0: WiMAX interface wmx0 (64:d4:da:13:95:de) ready
[   35.846242] i2400m_usb 2-1.3:1.0: boot-mode cmd -1: error waiting for an ack: -4
[   35.846316] i2400m_usb 2-1.3:1.0: bootrom init failed: -4
[   35.846364] i2400m_usb 2-1.3:1.0: i6050-fw-usb-1.5.sbcf: cannot use: -4, skipping
[   35.846519] i2400m_usb 2-1.3:1.0: Could not find a usable firmware image
[   35.846576] i2400m_usb 2-1.3:1.0: cannot bootstrap device: -4
[   35.885550] i2400m_usb 2-1.3:1.0: cannot setup device: -4
[   35.885607] i2400m_usb: probe of 2-1.3:1.0 failed with error -4
[   35.885656] usbcore: registered new interface driver i2400m_usb

bwat47

Member

Registered: 2009-10-07

Posts: 638

Re: i2400m_usb boot errors after today's updates

went ahead and reported a bug since it doesn't seem to just me me:
https://bugs.archlinux.org/task/28030?p … &sort=desc

In the meantime downgrading udev and mkinitcpio fixed this for me.

Last edited by bwat47 (2012-01-21 16:33:27)

hunterthomson

Member

Registered: 2008-06-22

Posts: 794

Website

Re: i2400m_usb boot errors after today's updates

I have the same problem. I'll try downgrading udev and mkinitcpio for now

---

OpenBSD-current Thinkpad X230, i7-3520M, 16GB CL9 Kingston, Samsung 830 256GB
Contributor: linux-grsec

hunterthomson

Member

Registered: 2008-06-22

Posts: 794

Website

Re: i2400m_usb boot errors after today's updates

Hum, downgrading udev-177-3-x86_64.pkg.tar.xz and mkinitcpio-0.8.0-3-any.pkg.tar.xz did not work.

What vertions are you running to make it work?

---

OpenBSD-current Thinkpad X230, i7-3520M, 16GB CL9 Kingston, Samsung 830 256GB
Contributor: linux-grsec

hunterthomson

Member

Registered: 2008-06-22

Posts: 794

Website

Re: i2400m_usb boot errors after today's updates

Okay, This is how I fixed it.

I created /etc/modprobe.d/modprobe.conf and added
blacklist i2400m_usb

Then I added this to /etc/rc.local
/sbin/modprobe i2400m_usb

I get fast boot now and the module is loading.... now I need to fix the watchdog error thing

---

OpenBSD-current Thinkpad X230, i7-3520M, 16GB CL9 Kingston, Samsung 830 256GB
Contributor: linux-grsec

bluej774

Member

Registered: 2011-04-15

Posts: 8

Re: i2400m_usb boot errors after today's updates

[deleted]

Last edited by bluej774 (2021-05-26 03:09:49)

sleekslush

Member

Registered: 2012-01-15

Posts: 10

Re: i2400m_usb boot errors after today's updates

I'm running a new install of Arch and I'm having this problem, too.  Unless I misinterpreted something, it looks like FS#28030 was closed as a duplicate of FS#27938.  Now, FS#27938 is closed saying it's fixed and in testing.  I've currently got my box running the latest versions of udev and mkinitpcio from testing and I've remade my boot image via mkinitcpio -p linux and I'm still getting those same errors on boot.  Since blacklisting and then modprobing is more of a workaround and not a solution, what's going on with this?

+1 .. I have a laptop and generally just suspend to disk, but if I do reboot, I also still experience the issue. I'm using latest and greatest as well.