DVD - failed to load monitor driver
Built 4 MSI systems using KN9neo motherboards and barton and pheno 1 processors - zero problems
Just built another system with phenom 2 processor and MSI NF750-G55 (MS-7578) motherboard
running XP fully patched
Everything works except the auto run on the lite-on cd/dvd writer
When i first booted xp with no graphics driver, the MSI drivers disk auto ran fine and I installed all the drivers
Now I can see the files on the utility disk but it wont auto run (or run the setup.exe file)
error is - 'failed to load monitor driver'
When I put the drivers disk in my phenom 1 machine it auto runs fine
I see the device manager shows 2 vga entries for dual screen use no doubt
Any ideas please - you might say why are you worried as all the drivers are on your machine - but i wonder if other dvd's might not auto run.
cd's auto run fine in the drive - its just the drivers DVD disk that will not auto run ...
I tried swapping the optical drive with my other machine which will auto run the disk, but it had the same problem - so the optical drive is ok but there is some incompatibility ?
Should on chip vga be enabled in BIOS - tried it on and off - no diff
thanks
alan
Quote from: Fredrik on 30-October-09, 06:09:07
Enter Device Manager and have a look at top of the list for 'Monitors', and then 'Graphics cards'. Don't know the titles in your lingua.
There seems to be something fishy with the drivers. I would restart the driver installation process, by uninstalling them. Don't think you are tempted to do so.
PSU too, please.
graphics card looks good and tried to update it via internet - it says present driver is ok
These two monitors showing are something I have never come across - they both say 'default monitor'
Yes i think i will acronis what i have and take the drivers out and reinstall
Two default monitors are weird or is it me that out of date as to how phenom 2's and fancy motherboards work... i will try it and report back !
thanks
alan
Similar Messages
-
[SOLVED] XOrg fails to load Nvidia driver on startup
Hi,
I'm having a fairly strange issue where XOrg is failing to load my driver when I start up my laptop. I'm using kdm, but this is causing it to fail. However, doing a simple
$sudo systemctl restart kdm
works, and everything starts up fine. When kdm is in the failed state, I see this:
$sudo systemctl status kdm
● kdm.service - K Display Manager
Loaded: loaded (/usr/lib/systemd/system/kdm.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2014-12-19 18:47:26 EST; 41s ago
Main PID: 247 (kdm)
CGroup: /system.slice/kdm.service
└─247 /usr/bin/kdm -nodaemon
Dec 19 18:47:26 laptop systemd[1]: Started K Display Manager.
Dec 19 18:47:27 laptop kdm[247]: X server died during startup
Dec 19 18:47:27 laptop kdm[247]: X server for display :0 cannot be started, session disabled
And in my XOrg log, I see:
[ 3.639]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 3.639]
X.Org X Server 1.16.2.901 (1.16.3 RC 1)
Release Date: 2014-12-09
[ 3.639] X Protocol Version 11, Revision 0
[ 3.639] Build Operating System: Linux 3.17.2-1-ARCH x86_64
[ 3.639] Current Operating System: Linux laptop 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC 2014 x86_64
[ 3.639] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw initrd=../initramfs-linux.img
[ 3.639] Build Date: 10 December 2014 02:34:24PM
[ 3.639]
[ 3.639] Current version of pixman: 0.32.6
[ 3.639] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 3.639] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 3.639] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 19 18:47:26 2014
[ 3.645] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 3.649] (==) No Layout section. Using the first Screen section.
[ 3.649] (==) No screen section available. Using defaults.
[ 3.649] (**) |-->Screen "Default Screen Section" (0)
[ 3.649] (**) | |-->Monitor "<default monitor>"
[ 3.650] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 3.650] (==) Automatically adding devices
[ 3.650] (==) Automatically enabling devices
[ 3.650] (==) Automatically adding GPU devices
[ 3.658] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 3.658] Entry deleted from font path.
[ 3.659] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 3.659] Entry deleted from font path.
[ 3.659] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 3.660] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 3.660] Entry deleted from font path.
[ 3.660] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 3.660] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 3.660] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 3.660] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 3.660] (II) Loader magic: 0x818d80
[ 3.660] (II) Module ABI versions:
[ 3.660] X.Org ANSI C Emulation: 0.4
[ 3.660] X.Org Video Driver: 18.0
[ 3.660] X.Org XInput driver : 21.0
[ 3.660] X.Org Server Extension : 8.0
[ 3.662] (EE) systemd-logind: failed to get session: PID 267 does not belong to any known session
[ 3.663] (--) PCI:*(0:1:0:0) 10de:11a1:1558:0371 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 3.663] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 3.664] (II) LoadModule: "glx"
[ 3.675] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 3.767] (II) Module glx: vendor="NVIDIA Corporation"
[ 3.767] compiled for 4.0.2, module version = 1.0.0
[ 3.767] Module class: X.Org Server Extension
[ 3.768] (II) NVIDIA GLX Module 343.36 Mon Dec 1 15:50:02 PST 2014
[ 3.769] (==) Matched nouveau as autoconfigured driver 0
[ 3.769] (==) Matched nv as autoconfigured driver 1
[ 3.769] (==) Matched modesetting as autoconfigured driver 2
[ 3.769] (==) Matched fbdev as autoconfigured driver 3
[ 3.769] (==) Matched vesa as autoconfigured driver 4
[ 3.769] (==) Assigned the driver to the xf86ConfigLayout
[ 3.769] (II) LoadModule: "nouveau"
[ 3.769] (WW) Warning, couldn't open module nouveau
[ 3.769] (II) UnloadModule: "nouveau"
[ 3.769] (II) Unloading nouveau
[ 3.769] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 3.769] (II) LoadModule: "nv"
[ 3.769] (WW) Warning, couldn't open module nv
[ 3.769] (II) UnloadModule: "nv"
[ 3.769] (II) Unloading nv
[ 3.769] (EE) Failed to load module "nv" (module does not exist, 0)
[ 3.769] (II) LoadModule: "modesetting"
[ 3.769] (WW) Warning, couldn't open module modesetting
[ 3.769] (II) UnloadModule: "modesetting"
[ 3.769] (II) Unloading modesetting
[ 3.769] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 3.769] (II) LoadModule: "fbdev"
[ 3.769] (WW) Warning, couldn't open module fbdev
[ 3.769] (II) UnloadModule: "fbdev"
[ 3.769] (II) Unloading fbdev
[ 3.769] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 3.769] (II) LoadModule: "vesa"
[ 3.770] (WW) Warning, couldn't open module vesa
[ 3.770] (II) UnloadModule: "vesa"
[ 3.770] (II) Unloading vesa
[ 3.770] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 3.770] (EE) No drivers available.
[ 3.770] (EE)
Fatal server error:
[ 3.770] (EE) no screens found(EE)
[ 3.770] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 3.770] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 3.770] (EE)
Which looks like it loads my nvidia driver, but then just decides not to use it for some reason... After I restart kdm, it seems to use the driver fine:
[ 78.897]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 78.897]
X.Org X Server 1.16.2.901 (1.16.3 RC 1)
Release Date: 2014-12-09
[ 78.897] X Protocol Version 11, Revision 0
[ 78.897] Build Operating System: Linux 3.17.2-1-ARCH x86_64
[ 78.897] Current Operating System: Linux laptop 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC 2014 x86_64
[ 78.897] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw initrd=../initramfs-linux.img
[ 78.897] Build Date: 10 December 2014 02:34:24PM
[ 78.897]
[ 78.897] Current version of pixman: 0.32.6
[ 78.897] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 78.897] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 78.897] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 19 18:48:38 2014
[ 78.897] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 78.897] (==) No Layout section. Using the first Screen section.
[ 78.897] (==) No screen section available. Using defaults.
[ 78.897] (**) |-->Screen "Default Screen Section" (0)
[ 78.897] (**) | |-->Monitor "<default monitor>"
[ 78.898] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 78.898] (==) Automatically adding devices
[ 78.898] (==) Automatically enabling devices
[ 78.898] (==) Automatically adding GPU devices
[ 78.898] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 78.898] Entry deleted from font path.
[ 78.898] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 78.898] Entry deleted from font path.
[ 78.898] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 78.898] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 78.898] Entry deleted from font path.
[ 78.898] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 78.898] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 78.898] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 78.898] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 78.898] (II) Loader magic: 0x818d80
[ 78.898] (II) Module ABI versions:
[ 78.898] X.Org ANSI C Emulation: 0.4
[ 78.898] X.Org Video Driver: 18.0
[ 78.898] X.Org XInput driver : 21.0
[ 78.898] X.Org Server Extension : 8.0
[ 78.900] (EE) systemd-logind: failed to get session: PID 542 does not belong to any known session
[ 78.900] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 78.901] (--) PCI:*(0:1:0:0) 10de:11a1:1558:0371 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 78.901] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 78.901] (II) LoadModule: "glx"
[ 78.902] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 78.913] (II) Module glx: vendor="NVIDIA Corporation"
[ 78.913] compiled for 4.0.2, module version = 1.0.0
[ 78.913] Module class: X.Org Server Extension
[ 78.913] (II) NVIDIA GLX Module 343.36 Mon Dec 1 15:50:02 PST 2014
[ 78.914] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[ 78.914] loading driver: nvidia
[ 78.914] (==) Matched nvidia as autoconfigured driver 0
[ 78.914] (==) Matched nouveau as autoconfigured driver 1
[ 78.914] (==) Matched nv as autoconfigured driver 2
[ 78.914] (==) Matched nouveau as autoconfigured driver 3
[ 78.914] (==) Matched nv as autoconfigured driver 4
[ 78.914] (==) Matched modesetting as autoconfigured driver 5
[ 78.914] (==) Matched fbdev as autoconfigured driver 6
[ 78.914] (==) Matched vesa as autoconfigured driver 7
[ 78.914] (==) Assigned the driver to the xf86ConfigLayout
[ 78.914] (II) LoadModule: "nvidia"
[ 78.914] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 78.920] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 78.920] compiled for 4.0.2, module version = 1.0.0
[ 78.920] Module class: X.Org Video Driver
[ 78.920] (II) LoadModule: "nouveau"
[ 78.921] (WW) Warning, couldn't open module nouveau
[ 78.921] (II) UnloadModule: "nouveau"
[ 78.921] (II) Unloading nouveau
[ 78.921] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 78.921] (II) LoadModule: "nv"
[ 78.921] (WW) Warning, couldn't open module nv
[ 78.921] (II) UnloadModule: "nv"
[ 78.921] (II) Unloading nv
[ 78.921] (EE) Failed to load module "nv" (module does not exist, 0)
[ 78.921] (II) LoadModule: "modesetting"
[ 78.921] (WW) Warning, couldn't open module modesetting
[ 78.921] (II) UnloadModule: "modesetting"
[ 78.921] (II) Unloading modesetting
[ 78.921] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 78.921] (II) LoadModule: "fbdev"
[ 78.922] (WW) Warning, couldn't open module fbdev
[ 78.922] (II) UnloadModule: "fbdev"
[ 78.922] (II) Unloading fbdev
[ 78.922] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 78.922] (II) LoadModule: "vesa"
[ 78.922] (WW) Warning, couldn't open module vesa
[ 78.922] (II) UnloadModule: "vesa"
[ 78.922] (II) Unloading vesa
[ 78.922] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 78.922] (II) NVIDIA dlloader X Driver 343.36 Mon Dec 1 15:28:39 PST 2014
[ 78.922] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 78.922] (++) using VT number 7
[ 78.935] (II) Loading sub module "fb"
[ 78.935] (II) LoadModule: "fb"
[ 78.935] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 78.936] (II) Module fb: vendor="X.Org Foundation"
[ 78.936] compiled for 1.16.2.901, module version = 1.0.0
[ 78.936] ABI class: X.Org ANSI C Emulation, version 0.4
[ 78.936] (II) Loading sub module "wfb"
[ 78.936] (II) LoadModule: "wfb"
[ 78.936] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 78.937] (II) Module wfb: vendor="X.Org Foundation"
[ 78.937] compiled for 1.16.2.901, module version = 1.0.0
[ 78.937] ABI class: X.Org ANSI C Emulation, version 0.4
[ 78.937] (II) Loading sub module "ramdac"
[ 78.937] (II) LoadModule: "ramdac"
[ 78.937] (II) Module "ramdac" already built-in
[ 78.939] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 78.939] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 78.939] (==) NVIDIA(0): RGB weight 888
[ 78.939] (==) NVIDIA(0): Default visual is TrueColor
[ 78.939] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 78.940] (**) NVIDIA(0): Enabling 2D acceleration
[ 79.610] (II) NVIDIA(0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 79.610] (II) NVIDIA(0): 3D Vision stereo.
[ 79.610] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
[ 79.612] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 670MX (GK104) at PCI:1:0:0 (GPU-0)
[ 79.612] (--) NVIDIA(0): Memory: 3145728 kBytes
[ 79.612] (--) NVIDIA(0): VideoBIOS: 80.04.67.00.06
[ 79.612] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 79.616] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 670MX at PCI:1:0:0
[ 79.616] (--) NVIDIA(0): Chi Mei Optoelectronics corp. (DFP-0) (boot, connected)
[ 79.616] (--) NVIDIA(0): Samsung SyncMaster (DFP-1) (connected)
[ 79.616] (--) NVIDIA(0): DFP-2
[ 79.616] (--) NVIDIA(0): DFP-3
[ 79.616] (--) NVIDIA(0): DFP-4
[ 79.616] (--) NVIDIA(0): Chi Mei Optoelectronics corp. (DFP-0): Internal LVDS
[ 79.616] (--) NVIDIA(GPU-0): Chi Mei Optoelectronics corp. (DFP-0): 330.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): Samsung SyncMaster (DFP-1): Internal TMDS
[ 79.616] (--) NVIDIA(GPU-0): Samsung SyncMaster (DFP-1): 165.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): DFP-2: Internal TMDS
[ 79.616] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): DFP-3: Internal DisplayPort
[ 79.616] (--) NVIDIA(GPU-0): DFP-3: 960.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[ 79.616] (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
[ 79.616] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 79.616] (**) NVIDIA(0): device Chi Mei Optoelectronics corp. (DFP-0) (Using EDID
[ 79.616] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
[ 79.616] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 79.616] (**) NVIDIA(0): device Samsung SyncMaster (DFP-1) (Using EDID frequencies
[ 79.616] (**) NVIDIA(0): has been enabled on all display devices.)
[ 79.618] (==) NVIDIA(0):
[ 79.618] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 79.618] (==) NVIDIA(0): will be used as the requested mode.
[ 79.618] (==) NVIDIA(0):
[ 79.619] (II) NVIDIA(0): Validated MetaModes:
[ 79.619] (II) NVIDIA(0): "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
[ 79.619] (II) NVIDIA(0): Virtual screen size determined to be 3600 x 1080
[ 80.144] (--) NVIDIA(0): DPI set to (128, 130); computed from "UseEdidDpi" X config
[ 80.144] (--) NVIDIA(0): option
[ 80.144] (--) Depth 24 pixmap format is 32 bpp
[ 80.144] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 80.144] (II) NVIDIA: access.
[ 80.150] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 80.150] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 80.150] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 80.150] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 80.150] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 80.150] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 80.150] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 80.150] (II) NVIDIA(0): Config Options in the README.
[ 80.155] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
[ 80.532] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 80.532] (==) NVIDIA(0): Backing store enabled
[ 80.532] (==) NVIDIA(0): Silken mouse enabled
[ 80.533] (==) NVIDIA(0): DPMS enabled
[ 80.533] (II) Loading sub module "dri2"
[ 80.533] (II) LoadModule: "dri2"
[ 80.533] (II) Module "dri2" already built-in
[ 80.533] (II) NVIDIA(0): [DRI2] Setup complete
[ 80.533] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 80.533] (--) RandR disabled
[ 80.539] (II) Initializing extension GLX
[ 80.605] (II) config/udev: Adding input device Power Button (/dev/input/event14)
[ 80.605] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 80.605] (II) LoadModule: "evdev"
[ 80.606] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 80.607] (II) Module evdev: vendor="X.Org Foundation"
[ 80.607] compiled for 1.16.2, module version = 2.9.1
[ 80.607] Module class: X.Org XInput Driver
[ 80.607] ABI class: X.Org XInput driver, version 21.0
[ 80.607] (II) Using input driver 'evdev' for 'Power Button'
[ 80.607] (**) Power Button: always reports core events
[ 80.607] (**) evdev: Power Button: Device: "/dev/input/event14"
[ 80.608] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 80.608] (--) evdev: Power Button: Found keys
[ 80.608] (II) evdev: Power Button: Configuring as keyboard
[ 80.608] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input18/event14"
[ 80.608] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 80.608] (**) Option "xkb_rules" "evdev"
[ 80.608] (**) Option "xkb_model" "pc104"
[ 80.608] (**) Option "xkb_layout" "us"
[ 80.635] (II) config/udev: Adding input device Video Bus (/dev/input/event15)
[ 80.635] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 80.635] (II) Using input driver 'evdev' for 'Video Bus'
[ 80.635] (**) Video Bus: always reports core events
[ 80.635] (**) evdev: Video Bus: Device: "/dev/input/event15"
[ 80.635] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 80.635] (--) evdev: Video Bus: Found keys
[ 80.635] (II) evdev: Video Bus: Configuring as keyboard
[ 80.635] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/LNXVIDEO:00/input/input19/event15"
[ 80.635] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 80.635] (**) Option "xkb_rules" "evdev"
[ 80.635] (**) Option "xkb_model" "pc104"
[ 80.635] (**) Option "xkb_layout" "us"
[ 80.636] (II) config/udev: Adding input device Power Button (/dev/input/event13)
[ 80.636] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 80.636] (II) Using input driver 'evdev' for 'Power Button'
[ 80.636] (**) Power Button: always reports core events
[ 80.636] (**) evdev: Power Button: Device: "/dev/input/event13"
[ 80.636] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 80.636] (--) evdev: Power Button: Found keys
[ 80.636] (II) evdev: Power Button: Configuring as keyboard
[ 80.636] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input17/event13"
[ 80.636] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 80.636] (**) Option "xkb_rules" "evdev"
[ 80.636] (**) Option "xkb_model" "pc104"
[ 80.636] (**) Option "xkb_layout" "us"
[ 80.637] (II) config/udev: Adding input device Lid Switch (/dev/input/event11)
[ 80.637] (II) No input driver specified, ignoring this device.
[ 80.637] (II) This device may have been added with another device file.
[ 80.637] (II) config/udev: Adding input device Sleep Button (/dev/input/event12)
[ 80.637] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 80.637] (II) Using input driver 'evdev' for 'Sleep Button'
[ 80.637] (**) Sleep Button: always reports core events
[ 80.637] (**) evdev: Sleep Button: Device: "/dev/input/event12"
[ 80.637] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 80.637] (--) evdev: Sleep Button: Found keys
[ 80.637] (II) evdev: Sleep Button: Configuring as keyboard
[ 80.637] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input16/event12"
[ 80.637] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[ 80.637] (**) Option "xkb_rules" "evdev"
[ 80.637] (**) Option "xkb_model" "pc104"
[ 80.637] (**) Option "xkb_layout" "us"
[ 80.638] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event18)
[ 80.638] (II) No input driver specified, ignoring this device.
[ 80.638] (II) This device may have been added with another device file.
[ 80.638] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event19)
[ 80.638] (II) No input driver specified, ignoring this device.
[ 80.638] (II) This device may have been added with another device file.
[ 80.639] (II) config/udev: Adding input device LOGITECH G110 G-keys (/dev/input/event3)
[ 80.639] (**) LOGITECH G110 G-keys: Applying InputClass "evdev keyboard catchall"
[ 80.639] (II) Using input driver 'evdev' for 'LOGITECH G110 G-keys'
[ 80.639] (**) LOGITECH G110 G-keys: always reports core events
[ 80.639] (**) evdev: LOGITECH G110 G-keys: Device: "/dev/input/event3"
[ 80.639] (--) evdev: LOGITECH G110 G-keys: Vendor 0x46d Product 0xc22b
[ 80.639] (--) evdev: LOGITECH G110 G-keys: Found keys
[ 80.639] (II) evdev: LOGITECH G110 G-keys: Configuring as keyboard
[ 80.639] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.1/3-4.1.1:1.0/0003:046D:C22B.0003/input/input7/event3"
[ 80.639] (II) XINPUT: Adding extended input device "LOGITECH G110 G-keys" (type: KEYBOARD, id 10)
[ 80.639] (**) Option "xkb_rules" "evdev"
[ 80.639] (**) Option "xkb_model" "pc104"
[ 80.639] (**) Option "xkb_layout" "us"
[ 80.639] (II) config/udev: Adding input device Gaming Keyboard G110 (/dev/input/event4)
[ 80.639] (**) Gaming Keyboard G110: Applying InputClass "evdev keyboard catchall"
[ 80.639] (II) Using input driver 'evdev' for 'Gaming Keyboard G110'
[ 80.639] (**) Gaming Keyboard G110: always reports core events
[ 80.639] (**) evdev: Gaming Keyboard G110: Device: "/dev/input/event4"
[ 80.640] (--) evdev: Gaming Keyboard G110: Vendor 0x46d Product 0xc22a
[ 80.640] (--) evdev: Gaming Keyboard G110: Found keys
[ 80.640] (II) evdev: Gaming Keyboard G110: Configuring as keyboard
[ 80.640] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.3/3-4.1.3:1.0/0003:046D:C22A.0004/input/input8/event4"
[ 80.640] (II) XINPUT: Adding extended input device "Gaming Keyboard G110" (type: KEYBOARD, id 11)
[ 80.640] (**) Option "xkb_rules" "evdev"
[ 80.640] (**) Option "xkb_model" "pc104"
[ 80.640] (**) Option "xkb_layout" "us"
[ 80.640] (II) config/udev: Adding input device Gaming Keyboard G110 (/dev/input/event5)
[ 80.640] (**) Gaming Keyboard G110: Applying InputClass "evdev keyboard catchall"
[ 80.640] (II) Using input driver 'evdev' for 'Gaming Keyboard G110'
[ 80.640] (**) Gaming Keyboard G110: always reports core events
[ 80.640] (**) evdev: Gaming Keyboard G110: Device: "/dev/input/event5"
[ 80.640] (--) evdev: Gaming Keyboard G110: Vendor 0x46d Product 0xc22a
[ 80.640] (--) evdev: Gaming Keyboard G110: Found keys
[ 80.640] (II) evdev: Gaming Keyboard G110: Configuring as keyboard
[ 80.640] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.3/3-4.1.3:1.1/0003:046D:C22A.0005/input/input9/event5"
[ 80.640] (II) XINPUT: Adding extended input device "Gaming Keyboard G110" (type: KEYBOARD, id 12)
[ 80.640] (**) Option "xkb_rules" "evdev"
[ 80.640] (**) Option "xkb_model" "pc104"
[ 80.641] (**) Option "xkb_layout" "us"
[ 80.641] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/event1)
[ 80.641] (**) Razer Razer Lachesis: Applying InputClass "evdev pointer catchall"
[ 80.641] (II) Using input driver 'evdev' for 'Razer Razer Lachesis'
[ 80.641] (**) Razer Razer Lachesis: always reports core events
[ 80.641] (**) evdev: Razer Razer Lachesis: Device: "/dev/input/event1"
[ 80.641] (--) evdev: Razer Razer Lachesis: Vendor 0x1532 Product 0xc
[ 80.641] (--) evdev: Razer Razer Lachesis: Found 12 mouse buttons
[ 80.641] (--) evdev: Razer Razer Lachesis: Found scroll wheel(s)
[ 80.641] (--) evdev: Razer Razer Lachesis: Found relative axes
[ 80.641] (--) evdev: Razer Razer Lachesis: Found x and y relative axes
[ 80.641] (II) evdev: Razer Razer Lachesis: Configuring as mouse
[ 80.641] (II) evdev: Razer Razer Lachesis: Adding scrollwheel support
[ 80.641] (**) evdev: Razer Razer Lachesis: YAxisMapping: buttons 4 and 5
[ 80.641] (**) evdev: Razer Razer Lachesis: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 80.641] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.2/3-4.2:1.0/0003:1532:000C.0001/input/input5/event1"
[ 80.641] (II) XINPUT: Adding extended input device "Razer Razer Lachesis" (type: MOUSE, id 13)
[ 80.642] (II) evdev: Razer Razer Lachesis: initialized for relative axes.
[ 80.642] (**) Razer Razer Lachesis: (accel) keeping acceleration scheme 1
[ 80.642] (**) Razer Razer Lachesis: (accel) acceleration profile 0
[ 80.642] (**) Razer Razer Lachesis: (accel) acceleration factor: 2.000
[ 80.642] (**) Razer Razer Lachesis: (accel) acceleration threshold: 4
[ 80.642] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/mouse0)
[ 80.642] (II) No input driver specified, ignoring this device.
[ 80.642] (II) This device may have been added with another device file.
[ 80.643] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/event2)
[ 80.643] (**) Razer Razer Lachesis: Applying InputClass "evdev keyboard catchall"
[ 80.643] (II) Using input driver 'evdev' for 'Razer Razer Lachesis'
[ 80.643] (**) Razer Razer Lachesis: always reports core events
[ 80.643] (**) evdev: Razer Razer Lachesis: Device: "/dev/input/event2"
[ 80.643] (--) evdev: Razer Razer Lachesis: Vendor 0x1532 Product 0xc
[ 80.643] (--) evdev: Razer Razer Lachesis: Found keys
[ 80.643] (II) evdev: Razer Razer Lachesis: Configuring as keyboard
[ 80.643] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.2/3-4.2:1.1/0003:1532:000C.0002/input/input6/event2"
[ 80.643] (II) XINPUT: Adding extended input device "Razer Razer Lachesis" (type: KEYBOARD, id 14)
[ 80.643] (**) Option "xkb_rules" "evdev"
[ 80.643] (**) Option "xkb_model" "pc104"
[ 80.643] (**) Option "xkb_layout" "us"
[ 80.643] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event6)
[ 80.643] (II) No input driver specified, ignoring this device.
[ 80.643] (II) This device may have been added with another device file.
[ 80.644] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event7)
[ 80.644] (II) No input driver specified, ignoring this device.
[ 80.644] (II) This device may have been added with another device file.
[ 80.644] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
[ 80.644] (II) No input driver specified, ignoring this device.
[ 80.644] (II) This device may have been added with another device file.
[ 80.644] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event9)
[ 80.644] (II) No input driver specified, ignoring this device.
[ 80.644] (II) This device may have been added with another device file.
[ 80.645] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event10)
[ 80.645] (II) No input driver specified, ignoring this device.
[ 80.645] (II) This device may have been added with another device file.
[ 80.645] (II) config/udev: Adding input device BisonCam, NB Pro (/dev/input/event17)
[ 80.645] (**) BisonCam, NB Pro: Applying InputClass "evdev keyboard catchall"
[ 80.645] (II) Using input driver 'evdev' for 'BisonCam, NB Pro'
[ 80.645] (**) BisonCam, NB Pro: always reports core events
[ 80.645] (**) evdev: BisonCam, NB Pro: Device: "/dev/input/event17"
[ 80.645] (--) evdev: BisonCam, NB Pro: Vendor 0x5986 Product 0x512
[ 80.645] (--) evdev: BisonCam, NB Pro: Found keys
[ 80.645] (II) evdev: BisonCam, NB Pro: Configuring as keyboard
[ 80.645] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/input/input23/event17"
[ 80.645] (II) XINPUT: Adding extended input device "BisonCam, NB Pro" (type: KEYBOARD, id 15)
[ 80.645] (**) Option "xkb_rules" "evdev"
[ 80.645] (**) Option "xkb_model" "pc104"
[ 80.645] (**) Option "xkb_layout" "us"
[ 80.646] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 80.646] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 80.646] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 80.646] (**) AT Translated Set 2 keyboard: always reports core events
[ 80.646] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 80.646] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 80.646] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 80.646] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 80.646] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 80.646] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 16)
[ 80.646] (**) Option "xkb_rules" "evdev"
[ 80.646] (**) Option "xkb_model" "pc104"
[ 80.646] (**) Option "xkb_layout" "us"
[ 80.646] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event20)
[ 80.646] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 80.647] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 80.647] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[ 80.647] (II) LoadModule: "synaptics"
[ 80.647] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 80.647] (II) Module synaptics: vendor="X.Org Foundation"
[ 80.647] compiled for 1.16.0, module version = 1.8.1
[ 80.647] Module class: X.Org XInput Driver
[ 80.647] ABI class: X.Org XInput driver, version 21.0
[ 80.647] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 80.647] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 80.647] (**) Option "Device" "/dev/input/event20"
[ 80.756] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5662 (res 42)
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4660 (res 47)
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 80.757] (**) Option "TapButton1" "1"
[ 80.757] (**) Option "TapButton2" "2"
[ 80.757] (**) Option "TapButton3" "3"
[ 80.757] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 80.757] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 80.810] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio2/input/input22/event20"
[ 80.810] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 17)
[ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.038
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 80.810] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 80.811] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
[ 80.811] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 80.811] (II) config/udev: Adding input device PC Speaker (/dev/input/event16)
[ 80.811] (II) No input driver specified, ignoring this device.
[ 80.811] (II) This device may have been added with another device file.
[ 88.265] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 88.265] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 88.282] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 88.282] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 88.291] (II) NVIDIA(0): Setting mode "LVDS-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, HDMI-0: 1680x1050_60_0 @1680x1050 +1920+0 {ViewPortIn=1680x1050, ViewPortOut=1680x1050+0+0}"
[ 89.221] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 89.221] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 90.639] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 90.639] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 93.745] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 93.745] (II) NVIDIA(GPU-0): 3D Vision stereo.
Notably, the following lines appear in the working case, but not the broken case:
[ 78.914] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[ 78.914] loading driver: nvidia
Does anyone know what might be going on here?
Last edited by straemer (2014-12-20 13:03:58)Hmmmm, that doesn't seem to be the issue. I have a nvidia geforce gtx 670mx. The nvidia website does link me to the 340xx driver for that card, but downgrading to that version still has the same issue. I suspect the issue is in Xorg, since it seems to load the module, but then decides it doesn't have a driver to run for some reason.
-
Sun IDM Repositor Configuration Error: Failed to load JDBC Driver
Hi Gurus,
I am new to Java IDM and predictably failed in my first attempt to install Java IDM in a Windows machine with SQL Server 2000 SP3.
I followed the Installation document step by step and I think I din' t miss any!!.. But still I got caught by an error, here it is:
I successfully installed IDM but failed while configuring Repository. I have downloaded the JDBC driver from Microsoft for SQL Server 2000, SP3. Then after that I copied the Jar from JDBC driver folder to
%WSHOME%/bin/lib folder. After this I launched the Repository configuration setup.
I got the following error while trying to connect the waveset database with Repository type as SQL Server (JDBC Driver)
com.waveset.util.ConfigurationError: Failed to load JDBC Driver 'com.microsoft.sqlserver.jdbc.SQLServerDriver':
==> java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
The Parameters that I have given for connection are:
URL: jdbc:sqlserver://127.0.0.1:1433;DatabaseName=waveset
JDBC Driver: com.microsoft.sqlserver.jdbc.SQLServerDriver
Connect as User: waveset
Connect Password: waveset
I have created the database and granted all access to user waveset.
Please help me come out of this. I tried dropping and recreating the database with a different name. Still it did not work, looks like it is a JDBC driver specific issue. Please guide me if I did anything wrong.
Appreciate any help
ThanksOpen your driver jar using winzip or something and check if the class: com.microsoft.sqlserver.jdbc.SQLServerDriver is present in the jar. I think you need to use a different class name. or your jar file is wrong. I think there are separate jars for SQL server 2000 and for SQL Server 2005.
-
VSphere 4 - Failed to load iommu driver
When I boot ESX 4 with the latest up on our UCS B class blades I get a:
"Failed to load iommu driver" and when it finally finishes booting on the first screen I have message in red:
cpu1 :4106)Mod: 2077: Initialization for vtd failed with -1"
I already have Intel Virtualization Technology enabled on all of them. This message wasn't showing last week but it started showing today.Strange, I rebooted the server 2 times and the error went away.
If anyone knows what might have caused this please let me know. Thanks. -
I am trying to run a program and keep getting the error Failed to load JDBC driver. java.lang.ClassNotFoundException
How can I correct this?I was just trying to execute this example from Deitel's Java book.
import java.awt.*;
import java.sql.*;
import java.util.*;
import javax.swing.*;
public class DisplayAuthors extends JFrame {
// JDBC driver name and database URL
static final String JDBC_DRIVER = "com.ibm.db2j.jdbc.DB2jDriver";
static final String DATABASE_URL = "jdbc:db2j:books";
// declare Connection and Statement for accessing
// and querying database
private Connection connection;
private Statement statement;
// constructor connects to database, queries database, processes
// results and displays results in window
public DisplayAuthors()
super( "Authors Table of Books Database" );
// connect to database books and query database
try {
// specify location of database on filesystem
System.setProperty( "db2j.system.home", "C:/Cloudscape_5.0" );
// load database driver class
Class.forName( JDBC_DRIVER );
// establish connection to database
connection = DriverManager.getConnection( DATABASE_URL );
// create Statement for querying database
statement = connection.createStatement();
// query database
ResultSet resultSet =
statement.executeQuery( "SELECT * FROM authors" );
// process query results
StringBuffer results = new StringBuffer();
ResultSetMetaData metaData = resultSet.getMetaData();
int numberOfColumns = metaData.getColumnCount();
for ( int i = 1; i <= numberOfColumns; i++ )
results.append( metaData.getColumnName( i ) + "\t" );
results.append( "\n" );
while ( resultSet.next() ) {
for ( int i = 1; i <= numberOfColumns; i++ )
results.append( resultSet.getObject( i ) + "\t" );
results.append( "\n" );
// set up GUI and display window
JTextArea textArea = new JTextArea( results.toString() );
Container container = getContentPane();
container.add( new JScrollPane( textArea ) );
setSize( 300, 100 ); // set window size
setVisible( true ); // display window
} // end try
// detect problems interacting with the database
catch ( SQLException sqlException ) {
JOptionPane.showMessageDialog( null, sqlException.getMessage(),
"Database Error", JOptionPane.ERROR_MESSAGE );
System.exit( 1 );
// detect problems loading database driver
catch ( ClassNotFoundException classNotFound ) {
JOptionPane.showMessageDialog( null, classNotFound.getMessage(),
"Driver Not Found", JOptionPane.ERROR_MESSAGE );
System.exit( 1 );
// ensure statement and connection are closed properly
finally {
try {
statement.close();
connection.close();
// handle exceptions closing statement and connection
catch ( SQLException sqlException ) {
JOptionPane.showMessageDialog( null,
sqlException.getMessage(), "Database Error",
JOptionPane.ERROR_MESSAGE );
System.exit( 1 );
} // end DisplayAuthors constructor
// launch the application
public static void main( String args[] )
DisplayAuthors window = new DisplayAuthors();
window.setDefaultCloseOperation( JFrame.EXIT_ON_CLOSE );
} // end class DisplayAuthors -
Failed to load Hardware monitor driver
I'm running XP and getting a "Failed to load Hardware monitor driver" message when I do the following. Log Off\Switch Users. When the new user comes up I get the error message along with a request that I send the following files to Microsoft. C:\WINDOWS\minidump\Mini042404-01.dmp and C:\DOCUME~1\HEIDIN~1\LOCALS~1\Temp\WER1.tmp. It then blue screens and reboots. I can boot up into all users without any problem. I only have the problem if I try to switch from one user to another withour rebooting first. Is this a problem with "Live Monitor" or is it a problem with my Samsung Monitor? I downloaded a Monitor Driver from Microsoft recently. This makes the one and only time I have ever seen a driver download on the Microsoft update page and it happened to be for my Monitor but it seemed to be the same version that came with it.
MSI 875P NEOR2 (bios 1.9)
Intel P4 3G 800FSB (HT enabled)
2x512MB dual Memory
FX 5900 256mb by Gainward
54xCD-ROM, DVD-Writer
Samsung 19" LCD Display SyncMaster 955DFIf you are running core centre on both profiles, this will happen. Fast user switching causes CC to load again, giving the message u have and will crash XP. U need to log off one user, then switch.
Alternativly make sure CC is not installed as a shortcut in all users. I place mine in my gaming profile only and dont use it in any other one.
If u r not running CC, mmmm, dunno -
"Booting from Boot Camp Assistant created USB Drive...Failed to load BOOTMGR"
Hi Apple Ppl of the Wrld: I need help I been working on installing windows 8 on my Mac.
Spec of equipment:
Mac Book Pro Mid 2012
Bootcamp Version: Version 5.0.4 (473)
Bootable USB Flash Drive: Type Scan disk 4 GB windows 8 pro iso image but without the driver and the 2nd Scan disk USB flash drive with 32 GB with the Bootcamp Drivers downloaded and saved to this drive.
Please Note: I also have the original back up installation disc for Microsoft 8 Prof 64 from Microsoft where I purchased it from.
1st Bootcamp is not recognizing the Original Microsoft 8 Pro backup disk from microsoft itself.
Solution: I created the New Image from the Original Microsoft installed disc in my desk top and changed the extension to .ISO then burned the ISO image into the newly purchased DVD+R. Then I ran Bootcamp Once again and it get the following error message "The installer disc could not be found -- Insert your Windows installer disc and wait a few seconds for the disc to be recognized. Solution
2: Created a bootable usb drive with bootcamp assistant successfully with bootcamp. Yes I close, ejected or un-mounted any image that was open or had been previously used then i restarted the Mac. Next, I start the bootcamp assistant tool once again then i get the same insert your windows installer disc message.
3: Then I try to resolve the installer disc not found issue: this are the steps i took: a). Lauch disc utilities
1. Selected the top most drive 750 GB Macintosh HDD
2. On the right you’ll see 5 tab buttons: First Aid | Erase | Partition | RAID | Restore.
3. Choose Partition. Then I clicked + to add another partition size of the partition was 222 GB
4. Change the Name of the Partition to BOOTCAMP
5. Change the Format to MS-DOS (FAT)
6. Click Apply to save the changes and then reboot your Mac and we’ll begin Windows installation.
7. During reboot, press and hold the alt/Option key and you’ll be presented with drives to boot from.
8. Use the arrow keys and return button to select the Windows yellow USB key drive containing your Windows 8 installation files.
9. This will begin the Windows install. --> then i get the following message: "Booting from Boot Camp Assistant created USB Drive...Failed to load BOOTMGR".
4: Take the Mac to best buy and let them resolve the issue and charge me like a million dollars for it :'( since i have no other idea who to get this bootcamp working at all. This has been a terribly lengthy issue and it is not as simple as it is claimed to be since i started with the Original Windows Disc Purchased from Microsoft and I have the Optical disc drive which it should be simpler from what I understand.
Please can you help It would be of great help.
<Email Edited by Host>from what i understand you are trying to install win 8 pro from a "backup disk" the one that you purchased from microsoft.
this will not work, it is not an installer disk.
you need to start the process again. erase the partition you made on your hdd. in disc utility click the minus button after selecting the bootcamp partition, then manually drag the divider down fully then apply.
next, erase your usb then format it.
download win 8 iso from here;
http://getintopc.com/softwares/operating-systems/download-windows-8-pro/
it is perfectly legal to use your purchased product key in this install.
in bootcamp select the iso image you just downloaded, select your preferred partition size, check all 3 options.
you have the support software on another usb but you wont need it so it can be discarded. the install will work far better with the iso and support on the same drive. -
E72 - The driver \Driver\WUDFRd failed to load for the device ROOT\SYSTEM\0001
I have a problem with my ThinkCentre E72 (Windows 8).
Suddenly, it shuts down with "shut-down" screen. Later, in my Event Viewer, I found the following System Warning:
"The driver \Driver\WUDFRd failed to load for the device ROOT\SYSTEM\0001" where the source of problem is Kernel-PnP.
Only thing that is plugged in my computer is mouse, keyboard and monitor.
Many thanks,
MatijaHi,
PNP0A0A is not a default pnp ID, you need go to the manufacturer websites to find the ACPI driver, download and install it.
Alex Zhao
TechNet Community Support -
IMac won't boot - Failed to load extension com.apple.driver.applemacriscAGP
Hello, so I have an iMac G4 17" (running 10.4) and it was unfortunately not connected to a very good surge protector. The power surged and a fuse blew and now when I try starting it up it chimes and then just sits at the gray screen with the apple logo. Here's what I've tried:
Booting into verbose and single-user modes, this is what happens:
Failed to load extension com.apple.driver.applemacriscPCI
Couldn't alloc class AGP
Still waiting for root device
Still waiting for root device
Still waiting for root device etc.
Booting into Open firmware mode:
I'm able to do everything just fine, including resetting the nvram
Resetting PRAM:
Works fine, chimes when appropriate
Starting from Tiger install DVD:
Works just fine, I'm able to access all the utilities and was able to copy files off to a flash drive with the terminal. I used Disk Utility to repair the drive and repair the permissions, both of which ran successfully. I did a clean install of Tiger and then repaired the drive and permissions. I selected the new install on the hard drive as the default start-up disk. Still it sits at the gray screen and I still get those same errors in Verbose and Single-User modes.
I found the source code (a cpp file) for the com.apple.driver.applemacriscPCI, but don't really know how to compile it and what headers are necessary etc, and even if I did I don't know where I would put it since the problem can't be on the hard drive after I did a clean install. I have not yet tried completely reformatting the drive before an install but doesn't the installer do that anyway?
Any help would be much appreciated.
Message was edited by: Yost SmithThere may be some circuit damage in the computer; due to the surge of power.
Sometimes, a computer and its owner get lucky and when a surge disables a
Macintosh, a reset of the Power Management Unit (PMU) can help restore the
normal functions. Often, when this works, the computer may not go past the
grey screen at all, until the PMU is reset.
Instead of a simple surge protector, my computers are powered through a
backup power supply; an uninterruptable power unit with battery backup.
These also have automatic voltage regulation. Forget common protectors!
On the iMac G4 series, the PMU reset button is under the metal plate on the
bottom and is hard to see. There may be instructions with images available
online, perhaps in Apple Support's knowledge-base. This would also be in
the official service manual in pdf electronic documentation, for a tech repair.
How to reset PMU in iMac G4:
http://support.apple.com/kb/HT1712
You may have to see if the Apple Hardware Test can show error codes and
other hints of hardware damages; and perhaps a tech visit is not far off...
Good luck & happy computing!
edited. -
HTTP.SYS fails to load after ProLiant NIC driver update on Server 2008 R2
Hi team,
This has been driving me crazy for a week and I can't find any reference to solving the problem in Technet or any forums...
I have a ProLiant ML350G5 server that I installed Server 2008 R2 on and migrated all my domain AD, DNS, File Services, Shares and files from SBS2003 (end of life, so let's take that out of the network) - Exchange and SharePoint were not being used so Standard
server 2008 was the choice seeing that the server hardware is 4 years old...
Everything went well, migration was successful, AD was primary and active.
Then (stupidly) I decided I'd better install all the updated drivers and management software from HP. The NIC is showing as an HP NC373i which is a Broadcom BCM5708C. I updated the FLASH in that card (HP utility) and updated the driver to the latest version
7.8.52.0 along with a bunch of other updates all handled by HP's Support Solutions Framework (msi).
After the reboot required, I noticed that the Print Spooler (set to Automatic) didn't start, neither did IIS or Web Services...
Trying to manually start them gives the error that a dependency failed. Now Print Spooler only uses HTTP (no longer a "service" but integrated into the kernel for multiple http connections on the same port and controlled using netsh http command
prompt...) DCOM and RPC. The last 2 are running, so that leaves HTTP as the culprit.
The Event Log shows that HTTP failed to load as "the services cannot be started. Either because it is disabled or because
it has no enabled devices associated with it"
From an administrator cmd prompt, net start http gives the same failure error.
netsh http show servicestate returns "The handle is invalid" - it's not seeing http at all...
OK. If you've read this far, thank you - keep going...
Here's my thinking... Updating the NIC driver has "broken" the association with HTTP.SYS - How to I get that association back?
I uninstalled anything http related, IIS, BITS, Web, Printing Services. Reboot after reboot and still no HTTP. I deleted http.sys from \windows\system32\drivers and did sfc to get windows to give me a clean one. Reboot, still doesn't load so it's not a damaged
http.sys.
I uninstalled EVERYTHING ProLiant, uninstalled the NIC, deleted the bxnd60a.sys driver so Windows would use it's own, rebooted, let it load NIC drivers, set the IP's up again, reboot - still no http.sys loading...
I've tried older versions of drivers from Broadcom, the latest version of drivers, still in the same hole...
Does anyone know how I can get HTTP.SYS to associate with the NIC? Can I do anything in the registry to achieve this? Do I have to do a System State Backup (is that the only way to preserve the AD and DNS?) scrub the server and start from scratch and then
restore the System State to get my AD and DNS back? If I do that will it bring the http.sys fault back?
I'm really at a loss - please, someone, please help...Hi team,
This has been driving me crazy for a week and I can't find any reference to solving the problem in Technet or any forums...
I have a ProLiant ML350G5 server that I installed Server 2008 R2 on and migrated all my domain AD, DNS, File Services, Shares and files from SBS2003 (end of life, so let's take that out of the network) - Exchange and SharePoint were not being used so Standard
server 2008 was the choice seeing that the server hardware is 4 years old...
Everything went well, migration was successful, AD was primary and active.
Then (stupidly) I decided I'd better install all the updated drivers and management software from HP. The NIC is showing as an HP NC373i which is a Broadcom BCM5708C. I updated the FLASH in that card (HP utility) and updated the driver to the latest version
7.8.52.0 along with a bunch of other updates all handled by HP's Support Solutions Framework (msi).
After the reboot required, I noticed that the Print Spooler (set to Automatic) didn't start, neither did IIS or Web Services...
Trying to manually start them gives the error that a dependency failed. Now Print Spooler only uses HTTP (no longer a "service" but integrated into the kernel for multiple http connections on the same port and controlled using netsh http command prompt...)
DCOM and RPC. The last 2 are running, so that leaves HTTP as the culprit.
The Event Log shows that HTTP failed to load as "the services cannot be started. Either because it is disabled or because it has no enabled devices
associated with it"
From an administrator cmd prompt, net start http gives the same failure error.
netsh http show servicestate returns "The handle is invalid" - it's not seeing http at all...
OK. If you've read this far, thank you - keep going...
Here's my thinking... Updating the NIC driver has "broken" the association with HTTP.SYS - How to I get that association back?
I uninstalled anything http related, IIS, BITS, Web, Printing Services. Reboot after reboot and still no HTTP. I deleted http.sys from \windows\system32\drivers and did sfc to get windows to give me a clean one. Reboot, still doesn't load so it's not a damaged
http.sys.
I uninstalled EVERYTHING ProLiant, uninstalled the NIC, deleted the bxnd60a.sys driver so Windows would use it's own, rebooted, let it load NIC drivers, set the IP's up again, reboot - still no http.sys loading...
I've tried older versions of drivers from Broadcom, the latest version of drivers, still in the same hole...
Does anyone know how I can get HTTP.SYS to associate with the NIC? Can I do anything in the registry to achieve this? Do I have to do a System State Backup (is that the only way to preserve the AD and DNS?) scrub the server and start from scratch and then restore
the System State to get my AD and DNS back? If I do that will it bring the http.sys fault back?
I'm really at a loss - please, someone, please help... -
Hello, has anyone had experience with dealing with this speciifc problem?
In short, upon rebooting, I am getting a black screen with a line of text that says, "Booting from Boot Camp Assistant created USB Drive...Failed to load BOOTMGR." Nothing happens after that.
I am using Mac OS X Lion 10.7.4. I have an ISO of Windows 7 Prof. along with an 8GB usb drive. I changed the coding in my bootcamp program to allow for the normally first invisible option that allows creation of a USB Installation program using an ISO that is normally only for computers without an optical drive.
I have that box checked, the check for new software box, and the install windows box checked. I went through the process of creating the USB, downloading the software, and partitioning the drive. Then on restart, I get the failed to load bootmgr error.
Some people have suggested using two usb drives for this. I am trying that method but it does not seem to help thus far.
Can anyone offer any help?
Thanks.from what i understand you are trying to install win 8 pro from a "backup disk" the one that you purchased from microsoft.
this will not work, it is not an installer disk.
you need to start the process again. erase the partition you made on your hdd. in disc utility click the minus button after selecting the bootcamp partition, then manually drag the divider down fully then apply.
next, erase your usb then format it.
download win 8 iso from here;
http://getintopc.com/softwares/operating-systems/download-windows-8-pro/
it is perfectly legal to use your purchased product key in this install.
in bootcamp select the iso image you just downloaded, select your preferred partition size, check all 3 options.
you have the support software on another usb but you wont need it so it can be discarded. the install will work far better with the iso and support on the same drive. -
Greetings Guys,
I have an issue on a client computer running windows 7 ultimate via bootcamp latest (5.0.5033): OS X 10.8.5.
Looking at the windows logs, I found that driver "WUDFRd" failed to load for peripheral ACPI.
The consequence of that driver not being loaded is the screen on windows black. When I plug the unit (MagSafe), I do have video.
When on windows for around 30 minutes with MagSafe connected, fan start to run high. I am assuming the driver not loaded (ACPI) is causing the issue.
I went to windows forum in search of a solution and they pointed to a potentially bad MLB. A bit drastic to my taste
I am pretty sure that the MLB on the MacBook Pro is OK.
I am wondering if anyone out there had the issue in the past and how to resolve it from an Apple perspective ?
Kind Regards,
zongo saibaHi Zuhl
Are you using a Logitech keyboard on that system?
The driver WUDFRd.sys is associated with Logitech keyboards and some of these are not compatible with Windows 7.
Check the following.
Go to the following website: Windows 7 Compatibility Center
You will see a Software and Hardware tab that you can use to locate the product you wish to check for compatibility.
Select the Compatibility FAQ that will explain how to use the compatibility website.
If you find an installed software/hardware item that does not appear on the compatibility list, go to the website of the maker of that product and check for any updates.
Let us know what you find.
Thank You for using Windows 7
Ronnie Vernon MVP -
USB CDC-ECM driver failed to load on 10.5 & 10.6
Hi,
I'm using a device with ECM.
On 10.7 and up the AppleUSBCDCECM driver loads automatically and I have tethering.
But on 10.5 & 10.6 the driver fails to load and the tetheing doesn't work.
Someone have an idea?
Thanks,
YanivHmmm, in 10.5.8 PPC Mac I have version 3.2.13 of /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBCDCECMData .kext
And the same version of /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBCDCECMCont rol.kext
Is that what you have in 10.5?
Open console in Applications>Utilities, check the system log for the date/time of the last problem & the Startup right after that for clues. -
How to resolve "Failed to load TTSQLDB JDBC driver" problem
Hi,
I installed timesten112140.sparc64.tar on solaris m/c.
Details of solaris m/c are
SunOS pun-ldom-rds70 5.10 Generic_139555-08 sun4v sparc SUNW,T5240
I am getting below mentioned error when trying connecting to the database through java process.
ERROR: failed to load TTSQLDB JDBC driver.
java.sql.SQLException: Problems with loading native library/missing methods: /op
t/TimesTen/ttsolaris21/lib/libttJdbc.so: ld.so.1: java: fatal: /opt/TimesTen/tts
olaris21/lib/libttJdbc.so: wrong ELF class: ELFCLASS64 (Possible cause: architec
ture word width mismatch)
at com.timesten.jdbc.JdbcOdbcConnection.connect(JdbcOdbcConnection.java:
1753)
at com.timesten.jdbc.TimesTenDriver.connect(TimesTenDriver.java:349)
at com.timesten.jdbc.TimesTenDriver.connect(TimesTenDriver.java:205)
at java.sql.DriverManager.getConnection(DriverManager.java:582)
at java.sql.DriverManager.getConnection(DriverManager.java:207)
at CreateConnectionDemo.createConnection(CreateConnectionDemo.java:43)
at CreateConnectionDemo.<clinit>(CreateConnectionDemo.java:26)
Exception in thread "main" java.lang.NullPointerException
at CreateConnectionDemo.closeConnection(CreateConnectionDemo.java:69)
at CreateConnectionDemo.main(CreateConnectionDemo.java:62)You are trying to open a direct mode connection to 64-bit TimesTen from a JVM running in 32-bit mode. This is not possible. Run the JVM in 64-bit mode instead and thsi issue will be resolved.
Chris -
The driver WUDFRd failed to load...
I'm getting a warning in the event log upon startup. Windows 8.1 Pro. This is a IdeaCenter B750 AIO.
I have no idea what driver this is so I need help fixing this error. What is WUDFRd ? All the information I can locate refers users to their OEM for a driver update.. Some mention a fingerprint reader but this system doesn't have one of those.
Thanks
Bryan
Log Name: System
Source: Microsoft-Windows-Kernel-PnP
Date: 2/10/2015 11:24:03 AM
Event ID: 219
Task Category: (212)
Level: Warning
Keywords:
User: MYPC
Description:
The driver \Driver\WUDFRd failed to load for the device ROOT\SYSTEM\0004.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
<EventID>219</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>212</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2015-02-10T16:24:03.240396600Z" />
<EventRecordID>22787</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="224" />
<Channel>System</Channel>
<Computer>MYPC</Computer>
<Security UserID="USERSID>
</System>
<EventData>
<Data Name="DriverNameLength">16</Data>
<Data Name="DriverName">ROOT\SYSTEM\0004</Data>
<Data Name="Status">3221226341</Data>
<Data Name="FailureNameLength">14</Data>
<Data Name="FailureName">\Driver\WUDFRd</Data>
<Data Name="Version">0</Data>
</EventData>
</Event>Apparently I've received a "private message" here about this topic but can't locate how to get to that message,,
Maybe you are looking for
-
After moving from my home country (Poland) to the Middle East (UAE) with the same computer I can not get connected to Apple Store and iTunes Store. Any clue why? Regards, Maciek
-
Excise rate are not coming in ARE1
Hi I have a problem here in ARE1 all figures are coming and thet are correct but excise rate fro BED,ECS and HSces not coming Regards sandeep
-
Who has the key for unlocking a 6280 ? the phone i...
If someone can help me..Message Edited by ajak on 07-Jul-2006 05:55 PM
-
An unknown error occurred (5002) and Connection timed out issue(s)
Next issue that I have since upgrading to Ver 8 of iTunes: When trying to make a purchase I get either one of two different problems/errors -- 1.) Following pop-up "Could not purchase song. An unknown error occurred (5002)" or 2.) I get a "connection
-
Module Pool+TOP+report prog,, Shuld I move to TEST individually?
Hi Experts, I enhanced one Module Pool Prog., which contains 3 parts i.e. 1 - Main Module Prog. 2- Top include 3- One error report prog. i.e. executable prog. So, Now, I need to move this main Module prog. to TEST box, So, 1) I guess I need to move t