Kernel Ring Message Bothering

CptCharis · Apr 28, 2018

Hello Guys!!!

I recently download an Arch .ISO for studying purposes.
I run it from USB and everything goes well till prompt open.
A message from buffer that, there is a problem with a USB cable appear.

Code:

[45219.238505] usb 1-1-port5: unable to enumerate USB device
[45223.022174] usb 1-1-port5: Cannot enable. Maybe the USB cable is bad?
[45223.874172] usb 1-1-port5: Cannot enable. Maybe the USB cable is bad?
[45224.726138] usb 1-1-port5: Cannot enable. Maybe the USB cable is bad?
[45225.578163] usb 1-1-port5: Cannot enable. Maybe the USB cable is bad?
[45225.578324] usb 1-1-port5: unable to enumerate USB device
[45227.306156] usb 1-1-port5: Cannot enable. Maybe the USB cable is

(I know what is the problem with the msg.
The example is picked up by Mint Terminal.)

My problem is that with Arch tty, I can't type at all bcz the above msg coming non stop.
Any suggestion to stop it and so I can use the prompt ?

atanere · Apr 28, 2018

Hi Captain! Digging around a bit indicates that you can still type commands, but you won't realize it due to the constant scrolling of the messages... so you'll need to type carefully since you can't see the feedback. One site suggests that it may be interrupted by just typing:

Code:

help  #Enter

Another site suggests this instead:

Code:

sudo dmesg -n 1  #followed by your root password, or not needed if logged in as root

You might want to give a brief delay before typing your root password so that the dmesg command gets recognized. This dmesg command suppresses kernel reporting to the console, but logging to file is still ongoing.

Hope that helps.

CptCharis · Apr 29, 2018

Thanks @atanere

The same says at dmesg man pages.

Code:

 -n, --console-level level
              Set  the level at which printing of messages is done to the con‐
              sole.  The level is a level number or abbreviation of the  level
              name.  For all supported levels see the --help output.

              For  example,  -n  1  or  -n alert prevents all messages, except
              emergency (panic) messages, from appearing on the console.   All
              levels  of  messages  are  still  written to /proc/kmsg, so sys‐
              logd(8) can still be used to control exactly where  kernel  mes‐
              sages  appear.  When the -n option is used, dmesg will not print
              or clear the kernel ring buffer.

I will try & let you know.

CptCharis · Apr 30, 2018

Unfortunately I should type faster than Flash.
I will google it , if there is another way to interrupt buffer mesgs.

atanere · Apr 30, 2018

Okay. I suppose you've tried the standard "keyboard interrupt" command, CNTRL-C, right? Another possible keyboard interrupt could be the PAUSE/BREAK key. If neither stops the kernel messages, the next question is: Can you fix the USB condition that is generating the error? If that is also not possible or desirable... then you may have to hard code a fix that will take effect at boot time. There's a couple of ways, it seems, though Arch may need something different.

1. Add sudo dmesg -n 1 or dmesg -D to your /etc/rc.local file. More details here.

2. Modify the /etc/sysctl.conf file by uncommenting and changing the values of the kernel.printk line. More details here.

I hope one of these will work for you!

Cheers

CptCharis · Apr 30, 2018

atanere said:
Can you fix the USB condition that is generating the error?

Unfortunately, @atanere, problem most probably occur due to non working internal web cam.

I found the same sites & same commands like you during digging in web.

I need something to work during booting & before pass to me the prompt.

CptCharis · May 1, 2018

Dear @atanere

Kindly be informed that I can run it normally in the VM

wizardfromoz · May 1, 2018

Morning Capta

Are you able to give us an output from

Code:

xinput

?

Mine looks like this, and note the reference to my webcam.

[[email protected] ~]$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Lite-On Technology Corp. Wireless Device id=11 [slave pointer (2)]
⎜ ↳ Lite-On Technology Corp. Wireless Device id=12 [slave pointer (2)]
⎜ ↳ ETPS/2 Elantech Touchpad id=15 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ Power Button id=9 [slave keyboard (3)]
↳ Lite-On Technology Corp. Wireless Device id=10 [slave keyboard (3)]
↳ TOSHIBA Web Camera - HD: TOSHIB id=13 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)]
↳ Toshiba input device id=16 [slave keyboard (3)]
↳ Lite-On Technology Corp. Wireless Device id=17 [slave keyboard (3)]
[[email protected] ~]$

Cheers

Wizard

CptCharis · May 2, 2018

Sure @wizardfromoz

Here you are.

Code:

[email protected] ~ $ xinput
⎡ Virtual core pointer                        id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                  id=4    [slave  pointer  (2)]
⎜   ↳ AlpsPS/2 ALPS GlidePoint                    id=12    [slave  pointer  (2)]
⎣ Virtual core keyboard                       id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard                 id=5    [slave  keyboard (3)]
    ↳ Power Button                                id=6    [slave  keyboard (3)]
    ↳ Video Bus                                   id=7    [slave  keyboard (3)]
    ↳ Power Button                                id=8    [slave  keyboard (3)]
    ↳ Sleep Button                                id=9    [slave  keyboard (3)]
    ↳ Dell WMI hotkeys                            id=10    [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard                id=11    [slave  keyboard (3)]

atanere · May 2, 2018

CptCharis said:
Unfortunately, @atanere, problem most probably occur due to non working internal web cam.

I found the same sites & same commands like you during digging in web.

I need something to work during booting & before pass to me the prompt.

Ah, okay. I wonder if blacklisting the webcam module in the kernel would stop this? It might become necessary to recompile the kernel... except for your report that it works okay in a VM!?!?!? Don't want to recompile a kernel if it is not necessary. Maybe Wizard is onto a better idea, so I'll just watch for a bit. (Sorry for the delay.... working midnights shifts this week. Ugh.)

Cheers

wizardfromoz · May 3, 2018

atanere said:
Maybe Wizard is onto a better idea,

Yeah, I wish

, having it show in xinput output (that sounds funny) would have made it easy-peasy.

Capta, if you want to determine more about your webcam, the outputs of the following can provide an insight:

Code:

sudo hwinfo | grep -i "cam"

Check for the presence of "uvcvideo" and "v4l" and "v4l2".

Code:

ls -ltrh /dev/video*

Look for an output eg /dev/video0

Code:

lspci

will tell you if anything for it is attached to PCI, but I think that less likely, than

Code:

lsusb

Now, subject to the above results, you can check for the presence of a file for blacklisting in /etc/modprobe.d

My output shows as

[[email protected] ~]$ ls /etc/modprobe.d
bumblebee.conf mhwd-bbswitch.conf mhwd-nouveau.conf

so I do not have one yet. But we can create one and have you try it.

Cheers

Wizard

atanere · May 3, 2018

CptCharis said:
Dear @atanere

Kindly be informed that I can run it normally in the VM

Just to make sure... your VM is running the exact same Arch as the one that is full-installed and giving you the trouble, right? If they are different versions, you may be running different kernels which might be an easy explanation why one works and the other doesn't.

CptCharis · May 3, 2018

atanere said:
Just to make sure... your VM is running the exact same Arch as the one that is full-installed and giving you the trouble, right? If they are different versions, you may be running different kernels which might be an easy explanation why one works and the other doesn't.

At first I boot Arch Linux from USB and I have this issue .
When i run it, exactly the same through VM , buffer mesgs appeared at the beginning but stop right after, so I can use the prompt.

CptCharis · May 3, 2018

Code:

sudo hwinfo | grep -i "cam"

[email protected] ~ $ sudo hwinfo | grep -i "cam"
sudo: hwinfo: command not found

Code:

ls -ltrh /dev/video*

[email protected] ~ $ ls -ltrh /dev/video*
ls: cannot access '/dev/video*': No such file or directory

Code:

lspci

lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.4 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
01:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)
02:00.0 Ethernet controller: Qualcomm Atheros AR8162 Fast Ethernet (rev 10)

Code:

lsusb

[email protected] ~ $ lsusb
Bus 002 Device 003: ID 8087:07da Intel Corp.
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 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
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
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Wizard[/QUOTE]

As can you see @wizardfromoz I can't find relevant to web camera.

wizardfromoz · May 3, 2018

Thanks for trying, Capta. With hwinfo, my bad, it was on Manjaro, so I assumed. I checked Bluestar Linux and it wasn't, now is.

Code:

sudo pacman -S hwinfo

- should work for Arch.

Can you try again?

Cheers

Wizard

CptCharis · May 4, 2018

I can't download something within VM & actually I want to ask you about.
Can you? I can't with any distro.

wizardfromoz · May 4, 2018

Try first
.

Code:

sudo pacman -Syy

That should co-ordinate/sync your repositories.

And the "git clove..." should be "git clone".

Bed for me, later

Chris
BTW Sorry, I haven't got any further with VMs than last we spoke

CptCharis · May 4, 2018

Hahahaha @wizardfromoz , I'm so newbie !!!

Thanks.

by the way

Code:

hwinfo | grep -i "cam"

no returns results.

no such file or directory

wizardfromoz · May 5, 2018

CptCharis said:
Hahahaha @wizardfromoz , I'm so newbie !!!

Mate I am 4 years in and I still regard myself as a Newbie

I am brainstorming here because I don't have Arch:

could it be the card reader, rather than the webcam? Does it work elsewhere (other Linux)?
USB 3.0 devices can have problems with VMs, I have read

I'll keep an eye out for other ideas.

Avagudweegend

Wiz

CptCharis · May 5, 2018

@wizardfromoz , I suppose to be web cam
Bcz is the only one hdw piece that is not working properly and didn’t work also defore during windows.

Kernel Ring Message Bothering

Well-Known Member

Moderator

Well-Known Member

Well-Known Member

Moderator

Well-Known Member

Well-Known Member

Super Moderator

Well-Known Member

Moderator

Super Moderator

Moderator

Well-Known Member

Well-Known Member

Super Moderator

Well-Known Member

Super Moderator

Well-Known Member

Super Moderator

Well-Known Member