FedoraForum.org - Fedora Support Forums and Community
Page 1 of 2 1 2 LastLast
Results 1 to 15 of 22
  1. #1
    Join Date
    May 2007
    Posts
    6

    Fedora 12 and a KVM Switch

    I have a very consistent problem that appeared when I upgraded
    to Fedora 12. I have 4 systems connected to my keyboard,
    mouse and monitor via a simple USB KVM switch. Up to F12
    I have never had a KVM related problem. After upgrading the
    first 2 machines, one 32-bit and one 64-bit I started having
    severe problems. When I switch away from a running, logged in
    system, and then switch back, the 32-bit system locks up, and
    GNOME logs out on the 64-bit system. I can ssh into the 32-bit
    system and shutdown. The other 2 systems are still F11 and
    never fail when switching.
    The 2 failing system are both AMD Phenom class systems, and have the latest updates applied.

    Any insight would be greatly appreciated. Thank You.

  2. #2
    Join Date
    Aug 2009
    Posts
    8,486
    I am having the same problem with F12 and a KVM.

    switch away from the F12 system, and it locks up. USB mouse and keyboard, and nvidia video card.

    did not have a single problem with my KVM in F11 on the same machine.

    last messages in the logs are where it disconnects the USB devices.

    Nov 28 00:04:15 laptop30 kernel: usb 3-2: USB disconnect, address 18
    Nov 28 00:04:15 laptop30 kernel: usb 3-2.1: USB disconnect, address 19
    Nov 28 00:04:15 laptop30 kernel: usb 3-2.3: USB disconnect, address 20
    Nov 28 00:04:15 laptop30 kernel: usb 3-2.4: USB disconnect, address 21
    Last edited by DBelton; 28th November 2009 at 07:05 AM.

  3. #3
    scottro's Avatar
    scottro is offline Retired Community Manager -- Banned from Texas by popular demand.
    Join Date
    Sep 2007
    Location
    NYC
    Posts
    8,120
    Hrrm, I'm running on a KVM USB switch without problem. Ahhh--wait, I just remembered, I did have problems at home (the F12 is at work), which apparently turned out to be due to my NVidia card. I wound up having to try a few different KVMs, but at home, they're PS/2.

    (It was seeing Dbelton's mention of NVidia that reminded me of it.)

    heavylight, are you also using NVidia?

    I haven't run F12 on a system with NVidia, but see around the forums that some NVidia cards are causing various issues. You might try looking at a few of those threads, and seeing if any are useful.

    For what it's worth, when I had my issues, it didn't matter whether I was using GUI mode or just console.

    I don't know if any of this helps, but perhaps one of the NVidia threads might.
    --
    http://srobb.net

  4. #4
    Join Date
    Aug 2009
    Posts
    8,486
    I am running an nvidia FX5200 with the nvidia drivers installed. I was also noticing the same thing with the nouveau drivers as well.

    And the screen comes back properly, it's just that I get no responses from the mouse or keyboard. Seems like the system is locked up. I haven't tried to ssh into it like the original poster did yet.

    Other than installing the nvidia drivers, and doing a yum update, this system is a fresh, clean install of Fedora 12.

    I will try booting it runlevel 3 and see if I still experience the same thing.

    I am wondering if they made some big changes to the usb stuff. in a terminal window, my keyboard response is very slow compared to a ps/2 keyboard (and the same usb keyboard in F11) , and I have also experienced my 3 external usb drives being detected 2 times each at boot. The drive problem doesn't happen every time I boot though.
    Last edited by DBelton; 28th November 2009 at 08:05 PM.

  5. #5
    Join Date
    May 2005
    Location
    Tragic City, Michigan USA
    Posts
    1,700
    Have IOGEAR usb kvm switch with wireless mouse and keyboard with GeForce 9500 GT cards in both machines, one a F11 and other F12.

    No problems noted with using nouveau or the nvidia driver from rpmfusion.

  6. #6
    Join Date
    Aug 2009
    Posts
    8,486
    my KVM is also an iogear 4 port usb.

    However, my problem seem to have gone away after I did my last update today. so whatever was updated in the past couple of days was what was causing the problems. I need to check to see what packages got updated on my system today.

  7. #7
    Join Date
    Jun 2008
    Posts
    38
    I still have problems, even though I am totally up to date (with yum). Using a remote terminal to log in it seems that Xorg crashes when the USB drivers are switched back in rather than when swiched out. Could it be the keyboard driver possibly? I just noticed this thread, but have posted on another thread which I thought was related but turned out to be a different problem.

    Subjectively it seems more common when the machine is switched back before the xscreensaver has cut-in, but this is not always the case. I would say that it happens about 70% of the times the KVM is used.

    I ought to add that I did post the problem on bugzilla but the fanatical politics of not using non-open binaries got the better of their common sense and they have refused to cooperate, even though I pointed out to them that the problem exists with the nouveau driver as well (as reported by others). If anyone here has the KVM problem with the nouveau driver, the link to the bugzilla entry is:

    https://bugzilla.redhat.com/show_bug.cgi?id=545231

    Here are the backtraces I have:

    Backtrace:
    0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x80e587c]
    1: /usr/bin/Xorg (0x8047000+0x5fb66) [0x80a6b66]
    2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]
    3: /lib/libc.so.6 (0x43020000+0x70ebd) [0x43090ebd]
    4: /lib/libc.so.6 (__libc_malloc+0x5e) [0x430921fe]
    5: /usr/bin/Xorg (Xalloc+0x2a) [0x80a770a]
    6: /usr/bin/Xorg (0x8047000+0xedb06) [0x8134b06]
    7: /usr/bin/Xorg (0x8047000+0xee40b) [0x813540b]
    8: /usr/bin/Xorg (0x8047000+0x271f7) [0x806e1f7]
    9: /usr/bin/Xorg (0x8047000+0x1b8c5) [0x80628c5]
    10: /lib/libc.so.6 (__libc_start_main+0xe6) [0x43036bb6]
    11: /usr/bin/Xorg (0x8047000+0x1b4b1) [0x80624b1]
    Segmentation fault at address 0x4000088

    Fatal server error:
    Caught signal 11 (Segmentation fault). Server aborting


    Please consult the The X.Org Foundation support
    at http://bodhi.fedoraproject.org/
    for help.
    Please also check the log file at "/var/log/Xorg.0.log" for additional information.

    [mi] EQ overflowing. The server is probably stuck in an infinite loop.

    Backtrace:
    0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x80e587c]
    1: /usr/bin/Xorg (mieqEnqueue+0x1b7) [0x80e51a7]
    2: /usr/bin/Xorg (xf86PostMotionEventP+0xd4) [0x80bf8a4]
    3: /usr/lib/xorg/modules/input/evdev_drv.so (0xb75f8000+0x4602) [0xb75fc602]
    4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb75f8000+0x48f6) [0xb75fc8f6]
    5: /usr/bin/Xorg (0x8047000+0x6b1f0) [0x80b21f0]
    6: /usr/bin/Xorg (0x8047000+0x11ed24) [0x8165d24]
    7: (vdso) (__kernel_sigreturn+0x0) [0xffffe400]
    8: (vdso) (__kernel_vsyscall+0x10) [0xffffe424]
    9: /lib/libc.so.6 (0x43020000+0xe9b83) [0x43109b83]
    10: /lib/libc.so.6 (0x43020000+0x740d4) [0x430940d4]
    11: /lib/libc.so.6 (0x43020000+0x70787) [0x43090787]
    12: /usr/bin/Xorg (Xfree+0x22) [0x80a7452]
    13: /usr/bin/Xorg (0x8047000+0x62b2a) [0x80a9b2a]
    14: /usr/bin/Xorg (0x8047000+0x62bb2) [0x80a9bb2]
    15: /usr/bin/Xorg (CloseWellKnownConnections+0x34) [0x80a3bf4]
    16: /usr/bin/Xorg (0x8047000+0x66ce8) [0x80adce8]
    17: /usr/bin/Xorg (0x8047000+0x6734e) [0x80ae34e]
    18: /usr/bin/Xorg (0x8047000+0x5fbc0) [0x80a6bc0]
    19: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]
    20: /lib/libc.so.6 (0x43020000+0x70ebd) [0x43090ebd]
    21: /lib/libc.so.6 (__libc_malloc+0x5e) [0x430921fe]
    22: /usr/bin/Xorg (Xalloc+0x2a) [0x80a770a]
    23: /usr/bin/Xorg (0x8047000+0xedb06) [0x8134b06]
    24: /usr/bin/Xorg (0x8047000+0xee40b) [0x813540b]
    25: /usr/bin/Xorg (0x8047000+0x271f7) [0x806e1f7]
    26: /usr/bin/Xorg (0x8047000+0x1b8c5) [0x80628c5]
    27: /lib/libc.so.6 (__libc_start_main+0xe6) [0x43036bb6]
    28: /usr/bin/Xorg (0x8047000+0x1b4b1) [0x80624b1]

    ===========================================

    Here is another:

    (II) UnloadModule: "evdev"
    (II) config/hal: Adding input device Logitech USB-PS/2 Optical Mouse
    (**) Logitech USB-PS/2 Optical Mouse: always reports core events
    (**) Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event3"
    (II) Logitech USB-PS/2 Optical Mouse: Found 3 mouse buttons
    (II) Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
    (II) Logitech USB-PS/2 Optical Mouse: Found relative axes
    (II) Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
    (II) Logitech USB-PS/2 Optical Mouse: Configuring as mouse
    (**) Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
    (**) Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE)
    (**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
    (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0
    (II) Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
    (II) config/hal: Adding input device Cypress PS/2 Keyboard & Mouse
    (**) Cypress PS/2 Keyboard & Mouse: always reports core events
    (**) Cypress PS/2 Keyboard & Mouse: Device: "/dev/input/event5"
    (II) Cypress PS/2 Keyboard & Mouse: Found 3 mouse buttons
    (II) Cypress PS/2 Keyboard & Mouse: Found scroll wheel(s)
    (II) Cypress PS/2 Keyboard & Mouse: Found relative axes
    (II) Cypress PS/2 Keyboard & Mouse: Found x and y relative axes
    (II) Cypress PS/2 Keyboard & Mouse: Configuring as mouse
    (**) Cypress PS/2 Keyboard & Mouse: YAxisMapping: buttons 4 and 5
    (**) Cypress PS/2 Keyboard & Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Cypress PS/2 Keyboard & Mouse" (type: MOUSE)
    (**) Cypress PS/2 Keyboard & Mouse: (accel) keeping acceleration scheme 1
    (**) Cypress PS/2 Keyboard & Mouse: (accel) acceleration profile 0
    (II) Cypress PS/2 Keyboard & Mouse: initialized for relative axes.
    (II) config/hal: Adding input device Cypress PS/2 Keyboard & Mouse
    (**) Cypress PS/2 Keyboard & Mouse: always reports core events
    (**) Cypress PS/2 Keyboard & Mouse: Device: "/dev/input/event4"
    (II) Cypress PS/2 Keyboard & Mouse: Found keys
    (II) Cypress PS/2 Keyboard & Mouse: Configuring as keyboard
    (II) XINPUT: Adding extended input device "Cypress PS/2 Keyboard & Mouse" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "evdev"
    (**) Option "xkb_layout" "us"
    (**) Option "xkb_options" "terminate:ctrl_alt_bksp"

    Backtrace:
    0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x80e587c]
    1: /usr/bin/Xorg (0x8047000+0x5fb66) [0x80a6b66]
    2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]
    3: /lib/libc.so.6 (0x43020000+0x71511) [0x43091511]
    4: /lib/libc.so.6 (0x43020000+0x73019) [0x43093019]
    5: /lib/libc.so.6 (realloc+0xe0) [0x430932d0]
    6: /usr/bin/Xorg (Xrealloc+0x34) [0x80a75a4]
    7: /usr/bin/Xorg (dixAllocatePrivate+0x10d) [0x8088e8d]
    8: /usr/bin/Xorg (dixLookupPrivateAddr+0x44) [0x8088fb4]
    9: /usr/bin/Xorg (0x8047000+0xd3a38) [0x811aa38]
    10: /usr/bin/Xorg (0x8047000+0xd5290) [0x811c290]
    11: /usr/bin/Xorg (miCreateAlphaPicture+0xdd) [0x81b6a1d]
    12: /usr/bin/Xorg (miTrapezoids+0x17e) [0x81b6c7e]
    13: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0xb7161000+0x3713b7) [0xb74d23b7]
    Segmentation fault at address 0x4000088

    Fatal server error:
    Caught signal 11 (Segmentation fault). Server aborting


    Please consult the The X.Org Foundation support
    at http://bodhi.fedoraproject.org/
    for help.
    Please also check the log file at "/var/log/Xorg.0.log" for additional information.

    [mi] EQ overflowing. The server is probably stuck in an infinite loop.

    Backtrace:
    0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x80e587c]
    1: /usr/bin/Xorg (mieqEnqueue+0x1b7) [0x80e51a7]
    2: /usr/bin/Xorg (xf86PostMotionEventP+0xd4) [0x80bf8a4]
    3: /usr/lib/xorg/modules/input/evdev_drv.so (0xb75a9000+0x4602) [0xb75ad602]
    4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb75a9000+0x48f6) [0xb75ad8f6]
    5: /usr/bin/Xorg (0x8047000+0x6b1f0) [0x80b21f0]
    6: /usr/bin/Xorg (0x8047000+0x11ed24) [0x8165d24]
    7: (vdso) (__kernel_sigreturn+0x0) [0xffffe400]
    8: (vdso) (__kernel_vsyscall+0x10) [0xffffe424]
    9: /lib/libc.so.6 (0x43020000+0xe9b83) [0x43109b83]
    10: /lib/libc.so.6 (0x43020000+0x740d4) [0x430940d4]
    11: /lib/libc.so.6 (0x43020000+0x70787) [0x43090787]
    12: /usr/bin/Xorg (Xfree+0x22) [0x80a7452]
    13: /usr/bin/Xorg (0x8047000+0x62b2a) [0x80a9b2a]
    14: /usr/bin/Xorg (0x8047000+0x62bb2) [0x80a9bb2]
    15: /usr/bin/Xorg (CloseWellKnownConnections+0x34) [0x80a3bf4]
    16: /usr/bin/Xorg (0x8047000+0x66ce8) [0x80adce8]
    17: /usr/bin/Xorg (0x8047000+0x6734e) [0x80ae34e]
    18: /usr/bin/Xorg (0x8047000+0x5fbc0) [0x80a6bc0]
    19: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]
    20: /lib/libc.so.6 (0x43020000+0x71511) [0x43091511]
    21: /lib/libc.so.6 (0x43020000+0x73019) [0x43093019]
    22: /lib/libc.so.6 (realloc+0xe0) [0x430932d0]
    23: /usr/bin/Xorg (Xrealloc+0x34) [0x80a75a4]
    24: /usr/bin/Xorg (dixAllocatePrivate+0x10d) [0x8088e8d]
    25: /usr/bin/Xorg (dixLookupPrivateAddr+0x44) [0x8088fb4]
    26: /usr/bin/Xorg (0x8047000+0xd3a38) [0x811aa38]
    27: /usr/bin/Xorg (0x8047000+0xd5290) [0x811c290]
    28: /usr/bin/Xorg (miCreateAlphaPicture+0xdd) [0x81b6a1d]
    29: /usr/bin/Xorg (miTrapezoids+0x17e) [0x81b6c7e]
    30: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0xb7161000+0x3713b7) [0xb74d23b7]
    Last edited by mikebg; 9th December 2009 at 08:36 AM.

  8. #8
    Join Date
    Aug 2009
    Posts
    8,486
    I posted too soon on it fixing my problem. I am still experiencing it myself.

  9. #9
    Join Date
    Jan 2010
    Posts
    2
    I'm kind of having a similar problem too except Fedora doesn't recognize the monitor unless I plug it directly into the PC instead of through the KVM switch. I'm using a Samsung 931BW 1440x900 monitor with an nVidia Geforce 5200 video card. While plugged into the KVM switch, I can only get 800 x 600 and if I use system-config-display to set it to the closest monitor driver or to a generic LCD driver, the system hangs up during boot. I think it might be X windows hanging up. I have to rename xorg.conf and then reboot to just get back into the system. I probably need to upgrade my KVM switch to one with a DVI connector. Any suggestions?

    Thanks

  10. #10
    Join Date
    Feb 2010
    Posts
    2
    I'm experiencing the same problem as ghendric.
    Same monitor (Samsung 931BW) and a GEforce 8400GS PCI-e video card. I use a KVM switch (PS2 ports for mouse and K/B) to switch the VGA port between several boxes. It appears with FC12 that the monitor capabilities are being scanned when attempting to adjust the resolution of the display. Having it plugged directly into the video card allowed selection of higher resolutions than 800x600, however going through the KVM would only allow a default 800x600 resolution to be selected and the monitor was 'unknown'. I have the nouveau driver loaded.

    Is there a way to manually configure the display parameters and resolutions (as I have always done previously) and disable this monitor scanning "intelligence"?

  11. #11
    Join Date
    Aug 2009
    Posts
    8,486
    geofswan, yes you can manually specify the display parameters as in previous versions. By default, FC12 does not create a /etc/X11/xorg.conf file for you, but you can create one either manually, or if you have the rpmfusion nvidia drivers installed, by running livna-config-display. Now if you are running the rpmfusion drivers, you need to tell livna-config-display to NOT change your /etc/X11/xorg.conf file every time you boot! it's a check box when you run livna-config-display.

    but you can put the modes in your /etc/X11/xorg.conf file like in previous versions and it will use them instead of scanning and automatically setting it for you.

    Edit: I noticed you said you have the nouveau drivers. You can still create your /etc/X11/xorg.conf file and it will use it. For me, the nouveau drivers worked good, but I needed the 3D rendering so I had to install the nvidia drivers.

    I have attached a bare /etc/X11/xorg conf file from my laptop to give you something to start from if you want to use it.
    Attached Files Attached Files
    Last edited by DBelton; 1st February 2010 at 07:49 PM.

  12. #12
    Join Date
    Feb 2010
    Posts
    2
    Thanks DBelton. I tried creating an xorg.conf, however it still appears to be ignored. The monitor is still 'undefined' and the settings revert to their default of 800x600. If I bypass the KVM switch the monitor is identified and the extra resolution settings are available. This would indicate that the monitor is still being scanned for its capabilities rather than relying on the defined contents of the xorg.conf file. I am running the nouveau driver as installed and updated from the FC12 distro:
    xorg-x11-drv-nouveau-0.0.15-19.20091105gite1c2efd.fc12.x86_64

    ---------- Post added at 12:20 PM CST ---------- Previous post was at 11:32 AM CST ----------

    Looking at the Xorg.0.log file, it appears that one monitor section is being attached to the DVI output and no monitor sections are being attached to the VGA output of teh video card.

    (II) NOUVEAU(0): Output DVI-I-0 using monitor section Monitor1
    (II) NOUVEAU(0): Output VGA-0 has no monitor section

    I have two monitor (0 and 1) and two screen (0 and 1) sections in the xorg.conf file, but am unsure how to attach a particular one to each output. I've tried the Screen options in the ServerLayout section, however they always allocate the DVI output to whatever screen is selected.
    either:
    Screen 0 "Screen0" 0 0
    Screen 1 "Screen1" 0 0
    produces the same results.

    ---------- Post added at 02:03 PM CST ---------- Previous post was at 12:20 PM CST ----------

    OK, solved it.

    A lot of editing to the xorg.conf file to associate monitors, devices and screens together for the two outputs of the video card and the setting of the Modeline and the PreferredMode option in the Monitor sections.

  13. #13
    Join Date
    Aug 2009
    Posts
    8,486
    yep.. it takes some playing around with it to get the correct settings for your particular hardware sometimes. the xorg.conf file I posted had the multiple monitor setup, but I think I went back and edited it and took out one of them because I use that laptop docked all of the time now.

    glad you got it figured out though

  14. #14
    Join Date
    Feb 2010
    Posts
    12

    IOGear USB KVM been using with Fedora since Fedora (Blag) 5 No problems till now...

    I have an IOGear MiniView USB (G-CS104U) 4-port KVM Switch that I have been using with Fedora, since Fedora (Blag) 5 and have never had any problems until now, with Fedora 12. This KVM Switch works well with every operating system I have Tried from Win 3.1, 95,98, Me, 2000, Win XP and Vista. Along with Other Linux Distro's such as DSL, Puppy, Dabian, Blag 5 to 9. Basically I have used this switch with over 20 different Linux Distro's for the last 5 years and never had any problems with the systems locking up because of the switch. I may have never even figured out what was locking up Fedora 12 if it weren't for these posts on the Fedora Forum Fedora 12 and a KVM Switch, http://forums.fedoraforum.org/showthread.php?t=235138 I am now running Fedora 12 Constantine on an Intel Core 2 1.8ghz with Intel On-board Video, with 1gb of System Memory (see attached screen shot for details at Bug*545231).


    The only problems related to the USB KVM I have ever experienced was on older machines. And I am able to fix this by just leaving a PS2 Mouse and or Keyboard Plugged into the machine as a backup way to control the machine. Usually if I leave the KVM set on the machine long enough, the USB hooks back up and starts working again. But this work around method Does Not work with Fedora 12. The problem even seemed to get worse. I tried both PS2 and USB Mouse and Keyboards as a Work around to no avail. I have only ever had this problem with Older Bios in machines pre year 2000. This machine has a brand new mother board, that I just put in last month. I also had Fedora 12 running on an Intel P4 machine with a 64mb Nvidia Video Card and 1gb of Ram. It had had the same locking up problem. Also, the P4 was logging out or crashing back into the log in screen (the Gateway GT5408 does this some to, but seems better after a few updates). Probably crashing, because all open windows are always lost and had to be recovered when the programs were reopened. This Problem makes Fedora 12 Unusable for me, since I use 3 to 4 computers at a time every day to do my work. I hope you guys can figure this one out... I read allot on the Fedora Forum about whether or not it is a problem with the Nvidia Drivers, which I haven't used on the Nvidia Card at all. After 2 months of building up that system and working with you guys on other ABRT and SElinux Bugs, that system crashed and the files on that HD are not accessible now. So I will have to reformat it. Even though I have worked on Operating Systems, fixing and testing them for the last 10 years.... I'm not a Coder so I can't figure this out for my self. But I think these guys are right about the problem being with the USB Code in Fedora 12. What else could it be? I love the new features in Fedora 12 and hate to go back wards. But I can't work with a system that constantly locks up. So, just to show MS, what were made of... lets fix this!

    Thanks,

    Don
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	Fedora-12-Gateway-GT5408-System-info-cropped.png 
Views:	1086 
Size:	46.4 KB 
ID:	19016  
    Last edited by dweb98; 6th February 2010 at 08:30 PM.

  15. #15
    Join Date
    Aug 2009
    Posts
    8,486
    dweb98, have you tried updating your xserver from the updates-testing repo? there were a few updates over there that seemed to improve the problem a lil for me. I don't know if those updates were pushed to the main update repo yet or not, though. The update did not completely fix my problem, but has made it where the system is a little more usable.

    I also heard that some people are having good luck by putting the mouse and keyboard entries back in the /etc/X11/xorg.conf file too.

Page 1 of 2 1 2 LastLast

Similar Threads

  1. Doing research to switch from Win XP to Fedora 9
    By pancakelizard in forum Using Fedora
    Replies: 17
    Last Post: 3rd June 2008, 09:01 PM
  2. I want to switch to Fedora but....
    By fudderduds in forum Using Fedora
    Replies: 2
    Last Post: 12th April 2008, 09:48 AM
  3. Is It possible - Fedora LAN Switch??
    By FreakyFulley in forum Installation, Upgrades and Live Media
    Replies: 2
    Last Post: 1st January 2008, 10:43 AM
  4. Should I switch from Red Hat 9 to Fedora 3?
    By Mr. Sulu in forum Fedora Focus
    Replies: 15
    Last Post: 13th August 2005, 12:42 AM
  5. switch from RH9 -> Fedora
    By Robca in forum Installation, Upgrades and Live Media
    Replies: 4
    Last Post: 14th September 2004, 08:41 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •