two messages on boot-up

crumbly · 2013-11-21 18:14:30

Hey,
hope somebody can help me. I'm getting these two messages everytime I boot my Acer Aspire One.

[    2.089253] usb 1-1.1: string descriptor 0 read error: -22
systemd-fsck[115]: /dev/sda1: clean, 158760/19415040 files, 4799383/77642137 blo

How can I get rid of these messages?
Thanks. :]

WonderWoofy · 2013-11-21 18:33:55

The systemd-fsck is normal. It is just doing a consistency check on /dev/sda1 as you have instructed it to do in your fstab.

ewaller · 2013-11-21 18:36:38

The second message is normal.

The first message says that the kernel cannot enumerate the USB device that is plugged into USB port 1-1.
What USB devices are attached, and what do you see in the output of lsusb

As to the messages in general, you should see many more messages than that. Especially if you do not have the -quiet switch on the kernel command line in your boot loader. Is the complaint that these messages show up late, perhaps after the login prompt?

brain0 · 2013-11-21 18:38:16

ewaller wrote:

The first message says that the kernel cannot enumerate the USB device that is plugged into USB port 1-1.

It doesn't even say that. It only says there was a read error, which could mean about anything and is likely not critical at all.

crumbly · 2013-11-21 18:50:32

ewaller wrote:

The second message is normal.
The first message says that the kernel cannot enumerate the USB device that is plugged into USB port 1-1.
What USB devices are attached, and what do you see in the output of lsusb
As to the messages in general, you should see many more messages than that. Especially if you do not have the -quiet switch on the kernel command line in your boot loader. Is the complaint that these messages show up late, perhaps after the login prompt?

Ok good, the second message just came up because I had this Warning and I just followed this instruction: https://bbs.archlinux.org/viewtopic.php … 1#p1308951

First Message:
I do not have an USB device plugged in. And these two messages are coming up before login.

Output of lsusb:

Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 064e:e330 Suyin Corp. 
Bus 001 Device 003: ID 0489:e04e Foxconn / Hon Hai 
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ewaller · 2013-11-21 20:36:02

brain0 wrote:

ewaller wrote:
The first message says that the kernel cannot enumerate the USB device that is plugged into USB port 1-1.
It doesn't even say that. It only says there was a read error, which could mean about anything and is likely not critical at all.

Perhaps. And, having seen his lsusb output, I agree. I am involved in the development of USB client devices. I see that class of error often; usually when I've a hardware or firmware problem in my device. In my case it usually happens when the device is using the default address, after which the kernel never assigns a unique address to my device. I confess, my perspective is from that of the USB client rather than from the point of view of the kernel.

ewaller · 2013-11-21 20:39:34

crumbly wrote:

I do not have an USB device plugged in. And these two messages are coming up before login.
Output of lsusb:
...
Bus 001 Device 004: ID 064e:e330 Suyin Corp. 
Bus 001 Device 003: ID 0489:e04e Foxconn / Hon Hai 
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

But, you do. You've a camera, and a Bluetooth Adapter. Both on bus 1. They are just internal.
Do they both function?

crumbly · 2013-11-29 23:15:19

Hey i'm back. Sry had no time to look at my issue but now I have time again.
So my webcam is working. Im using wxCam. But my bluetooth is kind of strange. I'm able to start the bluetooth service with "systemctl start bluetooth.service" but I cant really find my devices. Do u think that this could cause the problem? But the service is off on default.

Last edited by crumbly (2013-11-29 23:20:12)

hydn · 2014-09-18 17:33:50

Hi Crumbly,

I had the same error. What I did was use a different USB ti install Arch. Copied the iso again to that USB using DD but with bs=512 (previously bs=4M) the error disappeared, not sure if coincidence.

jasonwryan · 2014-09-18 17:48:35

This is your final warning: stop necrobumping https://wiki.archlinux.org/index.php/Fo … Bumping.27

Closing

Arch Linux

#1 2013-11-21 18:14:30

two messages on boot-up

#2 2013-11-21 18:33:55

Re: two messages on boot-up

#3 2013-11-21 18:36:38

Re: two messages on boot-up

#4 2013-11-21 18:38:16

Re: two messages on boot-up

#5 2013-11-21 18:50:32

Re: two messages on boot-up

#6 2013-11-21 20:36:02

Re: two messages on boot-up

#7 2013-11-21 20:39:34

Re: two messages on boot-up

#8 2013-11-29 23:15:19

Re: two messages on boot-up

#9 2014-09-18 17:33:50

Re: two messages on boot-up

#10 2014-09-18 17:48:35

Re: two messages on boot-up

Board footer