] Express Legacy Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Kernel driver in use: ahci
Kernel modules: ahci
>From my point of view at least the AHCI mode should be driven by the
mvsas driver.
Please add it to the marvell list of devices.
Thanks.
--
*Wolfg
] Express Legacy Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Kernel driver in use: ahci
Kernel modules: ahci
From my point of view at least the AHCI mode should be driven by the
mvsas driver.
Please add it to the marvell list of devices.
Thanks.
--
*Wolfgang
Additional information:
Just checked this:
setserial -g /dev/ttyS*
/dev/ttyS0, UART: unknown, Port: 0x03f8, IRQ: 4
/dev/ttyS1, UART: 16550A, Port: 0xcc00, IRQ: 17
/dev/ttyS2, UART: 16550A, Port: 0xc880, IRQ: 17
/dev/ttyS3, UART: 16550A, Port: 0x02e8, IRQ: 3
Are we opening a non exsisting port?
Dear serial developers,
my suggestion is now following:
My box has 3 physical serial IO ports, 1 on MB and 2 on PCI IO board.
dmesg | grep ttyS shows this:
(rmmod parport_serial and modprobe it again)
[0.833923] 00:00: ttyS3 at I/O 0x2e8 (irq = 3, base_baud = 115200)
is a 16550A
[9.498
Rest of Message:
-- Package-specific info:
** Version:
Linux version 4.9.0-0.bpo.1-amd64 (debian-kernel@lists.debian.org) (gcc
version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.9.2-2~bpo8+1 (2017-01-26)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-0.bpo.1-amd64
root=UUID=808992a4-a439-4c52-8f4
while booting with
4.9.0, bpo kernel)
Datum: Sat, 04 Feb 2017 12:54:01 +
Von:Debian Bug Tracking System
An: Wolfgang Schnitker
Your message didn't have a Package: line at the very first line of the
mail body (part of the pseudo-header), or didn't have a Package: l
Dear Maintainer,
I just did a housecleaning in my box. Must be a USB misconnect due to dust.
dmesg now looks like this:
[0.697141] usbcore: registered new interface driver usbfs
[0.697171] usbcore: registered new interface driver hub
[0.700570] usbcore: registered new device driver u
Additional Information:
To make the mouse/keyb work you can simply switch them off at the
keyboard switch.
Switch on after a few seconds is like an newly plugged in device, then
mouse/keyborad are working.
Same behaviour if you start up and do nothing for about half an hour.
(Self-healing)
--
Package: src:linux
Version: 3.2.65-1
Severity: normal
Dear Maintainer,
after last update in wheezy to actual linux-image the detection does not work
correctly for my logitech keyboard and mice
wireless devices.
This behaviour looks like an old kernel issue for usb/hid logitech devices.
See: h
Package: linux-2.6
Version: 2.6.32-5
Severity: normal
Hello, I am using virtualbox-ose on my machine, therefore I have to build the
vbox module every time, a kernel update comes up.
Because DKMS is early loaded at system startup and after update no Module is
present, booting slowes down until m
Package: linux-headers-2.6.30-2-amd64
Version: 2.6.30-8
Severity: normal
this bug is coming out of bug # 550595
alsa-source does not compile against patched headers.
See BTS for above mentioned bug.
I tried to build the modules via m-a.
m-a buildlog attached to #550595
-- System Information:
11 matches
Mail list logo
