Ubuntu failes to work with KVM switch

Bug #213895 reported by ronny
44
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

I am currently using Ubuntu 7.10 on two systems:
1) HP TC1100 (Tablet PC with docking station)
2) Desktop system with the mainboard "Asus P5W64 WS Professional" (output of lspci and lsusb is attached)

Until recently both system were connected to a 2-Port USB KVM switch "level one KVM-0221". Everything worked fine until I added another machine and replaced the 2-Port KVM switch with the 4-Port KVM switch "level one KVM-0421".
Now system (2) does not start up anymore. It boots up with the graphical splash screen and switches to text mode. The last line on the console is:

* Running local boot scripts (/etc/rc.local) [OK]

If I switch back and forth between both systems the following error message appears on the console:

/build/buildd/linux-2.6.24/drivers/hid/usbhid/hid-core.c: couldn't find an input interrupt endpoint

I downloaded and tried Ubuntu-8.04beta and the same problem persists. It is impossible to boot the live CD. Then I tried Knoppix-5.3.1 and Mandriva-2008-One on system (2) and both worked without any problem.

When I replace the 4-Port KVM switch with the old 2-Port switch, Ubuntu starts again. Unfortunately, I really need the 4-Port version. Because other Linux distributions work flawlessly, I assume that Ubuntu has a bug.

Tags: cft-2.6.27
Revision history for this message
ronny (ronny-standtke) wrote :
Revision history for this message
ronny (ronny-standtke) wrote :
Revision history for this message
ScottBla (sblachowicz+launchpad) wrote :

I've got what appears to be similar problems. I'm using a 4 port TrendNet TK-409 KVM (USB keyboard & mouse + sound switching that I'm not using). My problem box is currently a dual boot XP & Ubuntu 7.10 box (a Dell Vostro 200). I wanted to upgrade the 7.10 part to 8.04 (actually, just to a fresh install to replace the 7.10). I see the graphical splash screen, then it drops down to an "(initramfs)" ash prompt. Shortly after that I see a message about ".../hid-core.c: couldn't find an input interrupt endpoint"...that might have been in response to my hitting a key on the keyboard.

Later, I see a couple messages like this:

    ata1.00: revalidation failed (errno=-5)

plus some others that I don't have time to copy down before the box reboots. I would think that's unrelated to the initial HID/USB messages, but don't really know.

Attached are outputs of some commands booting to the 7.10 installation.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
ronny (ronny-standtke) wrote :

I just tried out Alpha5.
While it is now possible to boot up the installation CD, it is only possible to use a resolution of 800x600 instead of the 1280x1024 the display normally is able to show.
After installation the GUI does not show up. I am stuck in text mode...

Revision history for this message
ronny (ronny-standtke) wrote :

Now I tried 8.10 Beta and it became even worse...

X does not start up at all. The installation CD just gave me a text prompt after booting finished. I tried starting X manually but all I got was this error message:

X.Org X Server 1.5.1
Release Date: 23 September 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-16-server i686 Ubuntu
Current Operating System: Linux ubuntu 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC 2008 i686
Build Date: 24 September 2008 06:28:32PM
xorg-server 2:1.5.1-1ubuntu1 (<email address hidden>)
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Oct 14 13:37:52 2008
(==) Using config file: "/etc/X11/xorg.conf"
error setting MTRR (base = 0xd0000000, size = 0x10000000, type = 1) Invalid argument (22)

Backtrace:
0: X(xf86SigHandler+0x79) [0x80c3069]
1: [0xb8012400]
2: X(xf86InitialConfiguration+0x1269) [0x80ed659]
3: /usr/lib/xorg/modules/drivers//nv_drv.so [0xb7ad24a1]
4: X(InitOutput+0x96f) [0x80aacff]
5: X(main+0x279) [0x8071b89]
6: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7c1c685]
7: X [0x8071171]
Saw signal 11. Server aborting.

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest ubuntu release, Intrepid Ibex 8.10?

I have used a hardware 4-port KVM with all versions of Ubuntu and Xubuntu since 6.06 without these issues. It is not a USB-powered KVM, though, which does make it different. It draws the power through the PS2 ports instead.

Thanks in advance.

Changed in linux:
status: New → Incomplete
Revision history for this message
trentscott4 (trentscott4) wrote :

I can confirm this is still an issue on Ubuntu Server 8.10 (linux-2.6.27). I have a USB powered KVM switch and receive the following error on boot (same message on two different machines):

[ 55.498350 ] /build/buildd/linux-2.6.27/drivers/hid/usbhid/hid-core.c: couldn't find an input interrupt endpoint

[ 86.458358 ] /build/buildd/linux-2.6.27/drivers/hid/usbhid/hid-core.c: couldn't find an input interrupt endpoint

Any thoughts?

Revision history for this message
ronny (ronny-standtke) wrote :

I just tested with Ubuntu-8.10 final. The Installation CD boots but still ends up in text mode. When I execute startx manually I get the following error on the console:
Fatal server error:
no screens found

Please see the attached Xorg.0.log for details.

ronny (ronny-standtke)
Changed in linux:
status: Incomplete → Confirmed
Revision history for this message
ronny (ronny-standtke) wrote :

I just installed Debian Etch on the same hardware. Interestingly, this ancient system worked much better than current Ubuntu releases. Please see the attached Xorg.0.log for details.

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for helping improve Ubuntu. There should be enough information for the developers to begin work on this.

Changed in linux:
importance: Undecided → Medium
status: Confirmed → Triaged
Revision history for this message
Gary (garye3) wrote :

I've got two dfferent kvm switches & neither work very well with Ubuntu.
I've tried all the different versions from 9.10 going back to 7.04.
The monitor is only recognized if I boot from the first port so a live CD will only work if I'm connected to the first port. If I modify or as in 9.10 create an xorg.conf file I can make things work where Ubuntu can be used on a port other than the first one but it must be booted with that port active or else there will be a blank screen when I change to it.
Once Ubuntu recognizes the screen I can switch back & forth with the KVM with no problems.
Windows doesn't have that problem so I assume its a combination of the KVM switch & how Ubuntu recognizes the monitor. I'm using:
4-port Aluratek AKSP04
2-port Trendnet TK-200
both are for VGA monitor & ps2 mouse & keyboard

Revision history for this message
Jeffrey Walton (noloader) wrote :

Not a failure, but Ubuntu 9.10 only offers 800x600 with a D-Link 2 port KVM switch (model DKVM-2K). And if I use NVidia's driver, it gets worse - the best resolution is 640x480. In either case, my 22-inch CRT is not recognized. 800x600@56hz is kind of insulting to the monitor - it can be driven at almost twice the rate.

It sure would be nice if the display applet (System->Administration->Display) allowed me to specify a monitor.

Revision history for this message
wistle (charl-wentzel) wrote :

I'm using the Trendnet TK-407 4-port USB KVM with Ubuntu 10.04 Desktop and having the same problem. Booting with screen connected directly works fine, but booting via KVM results in a blank screen. Same occurs with Ubuntu 10.04 server edition running in frame-buffer mode, i.e. screen blanks as soon as it switches to frame buffer.

To use the KVM I boot the PC's with the monitor plugged in directly, then after booting I can connect the monitor via the KVM. From here on I can switch between PC's without issues using KVM.

I've attached the following files from the desktop:
- Xorg.0.log (successful boot with monitor connected directly)
- Xorg.0.log.old (unsuccessful boot with monitor connected via KVM)

I've attached the following files from the server (with frame buffer):
- syslog.2 (various successful and unsuccessful boots as per above)

Revision history for this message
wistle (charl-wentzel) wrote :
Revision history for this message
wistle (charl-wentzel) wrote :
Revision history for this message
wistle (charl-wentzel) wrote :
Revision history for this message
Wawrzyniec Niewodniczański (wawrzek) wrote :

I'm another affected user.

OS: Ubuntu 10.04.01 LTS.
KVM: KVM Switch is 4 Port and I cannot find any name... Supporting Resolution up to 1920x1440.

OS with monitor connected via KVM switch goes to 1024x768 rather then to 1280x1024.

I've tried to enforce right resolution, but obtaining monitor edid via get-edid|parse-edid to /etc/Xorg/xorg.conf.d/10-monitor.conf file when connected directly, but Xorg doesn't bother/cannot use them when connected to monitor via KVM.

Revision history for this message
Christian Blackburn (christian-blackburn) wrote :

I'm running the 32-bit desktop version of Ubuntu 10.04, I'm not failing to boot like the bug identifies. However, I get that interupt endpoint error. I too am using a bus powered (no ac adapter) 4-port USB KVM (LinksKey LKU-S04ASK). The boot process behaves normal enough, however if I switch back to the system after a certain amount of time I will see white and black flashing vertical bars occupying the upper 50% of the screen and am unable to resume using my system without a cold reboot (eMachines system is too crappy to have a reset button, so a warm reboot might be possible, but Ctrl+Alt+Del doesn't do anything). I have installed every OS level update and when I click on Hardware Drivers it reports that no closed source drivers are in use. Now that I know of this bug I reply back with a photo of the flashing screen I saw described earlier.

Revision history for this message
Christian Blackburn (christian-blackburn) wrote :

My usbhid interupt endpoint error is during boot however.

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

@Christian Blackburn:
Please file a new bug for your issue. You can do that by opening a terminal and typing
ubuntu-bug linux

That will allow the developers to see what is really happening with your issue. If it deteremined to be caused by the same issue, the bug can be made a duplicate of this one. You should mention in the description/comments that you believe the bug is related to bug 213895.

Thank you.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.