Problem building modules in kernel-2.6.29.6-rt

Hi, im trying to compile 2.6.29.6 rt patched, and when i type
make modules
and i get this:
CC [M] drivers/staging/agnx/pci.o
drivers/staging/agnx/pci.c:426: aviso: inicialización desde un tipo de puntero incompatible
CC [M] drivers/staging/agnx/xmit.o
CC [M] drivers/staging/agnx/table.o
CC [M] drivers/staging/agnx/sta.o
CC [M] drivers/staging/agnx/phy.o
drivers/staging/agnx/phy.c: En la función 'card_interface_init':
drivers/staging/agnx/phy.c:936: aviso: el tamaño de marco de 4124 bytes es mayor que 1024 bytes
LD [M] drivers/staging/agnx/agnx.o
CC [M] drivers/staging/asus_oled/asus_oled.o
CC [M] drivers/staging/at76_usb/at76_usb.o
CC [M] drivers/staging/comedi/comedi_fops.o
In file included from drivers/staging/comedi/comedidev.h:40,
from drivers/staging/comedi/comedi_fops.c:45:
drivers/staging/comedi/interrupt.h:27: error: tipos en conflicto para 'irqreturn_t'
include/linux/irqreturn.h:14: nota: la declaración previa de 'irqreturn_t' estaba aquí
En el fichero incluído de drivers/staging/comedi/comedidev.h:40,
de drivers/staging/comedi/comedi_fops.c:45:
drivers/staging/comedi/interrupt.h:30:1: aviso: se redefinió "IRQ_RETVAL"
En el fichero incluído de include/linux/interrupt.h:10,
de drivers/staging/comedi/interrupt.h:22,
de drivers/staging/comedi/comedidev.h:40,
de drivers/staging/comedi/comedi_fops.c:45:
include/linux/irqreturn.h:15:1: aviso: esta es la ubicación de la definición previa
make[3]: *** [drivers/staging/comedi/comedi_fops.o] Error 1
make[2]: *** [drivers/staging/comedi] Error 2
make[1]: *** [drivers/staging] Error 2
make: *** [drivers] Error 2
bash-4.0#
Any idea?
Last edited by B4RR13N705 (2009-07-16 16:46:46)

It should not (depends how far you want to go). I just did a search and it seems that bug was introduced ~.5
You can always try to build or disable this option from kernel config file.
I don't use rt kernels and in -rc staging drivers just appeared. Because I don't use them, I de-select whole branch, so I don't have your problem. However even if I would enble this, I might not see your error as it seems related to other rt stuff.
sorry that I can't help more.

Similar Messages

How to install tools to build a standard kernel module?

Hello!
I am a long time Fedora user trying to switch over to Arch for the ease of customization.
I am trying to build the hybrid_wl driver for my broadcom wireless card, and the requirements section says I need to have "the proper tools, packages, header files and libraries to build a standard kernel module. This is usually done by installing the kernel developer of kernel source package and caries from distro to distro."
I have never messed around with the kernel in Arch (or Fedora, for that matter) so I really have no clue what a standard module even is. What do I need to install to get this driver working?
Any help is welcome!
Thanks,
Jim

that is in aur.
http://aur.archlinux.org/packages.php?ID=19514
read about what is aur here: http://wiki.archlinux.org/index.php/AUR_User_Guidelines

Automatically build kernel module after kernel update

Hello. Everytime kernel is updated, my wifi drivers don't work. I need to use this to get my adapter working: https://aur.archlinux.org/packages/8192cu-dkms/ .
After kernel update, I have to manually reinstall the package, so the kernel module gets rebuilt. Is there any way to make it automatic?

I noticed it, but your script doesn't run at all when I type `mkinitcpio -p linux`. And wifi still works after reboot. Same for graphics driver, it has a hook at shutdown, that rebuilds its module after kernel update, it haven't run too and graphics driver works. It's like 'mkinitcpio -p linux' does nothing to the system.
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 4.0.4-2-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 4.0.4-2-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
Last edited by kox (2015-06-02 07:18:24)

Script to easily build modules for custom kernels

I got bored, and thought of this ages ago. I have no use for it now, but i'm sure someone else will.
run:
abs-module $modulename $kernel
$modulename is any kernel module that's available in /var/abs, so if you have some that arent in a default abs, put em in /var/abs/local and they will be spotted by this.
$kernel is the name of the kernel that you want to compile for. this can be found with 'uname -r'. If $kernel is not specified, then it will default to what you are running now.
this will only work for module packages that have a variable called _kernver which sets the kernel it will be compiled for. I know all the winmodems, ATi and drivers I maintain do, not sure about some of the others. nvidia won't work.
#! /bin/bash
# Set the variables up
module="$1"
kernel="$2"
pacman="1"
current="`uname -r`"
# Check things
if [ -z "$module" ]; then
echo "No module specified"
return 1
fi
if [ -z "$kernel" ]; then
echo "No kernel specified, building for: $current"
kernel="$current"
fi
if [ ! -e "/lib/modules/$kernel/build" ]; then
echo "Specified kernel is not installed"
return 1
fi
# Check if module exists
origdir="`find /var/abs -type d -name $module`"
if [ -z "$origdir" ]; then
echo "Specified module does not exist"
return 1
fi
# Prepare to build
newdir="/var/abs/local/$module-$kernel"
if [ -d "$newdir" ]; then
rm -rf "$newdir"
fi
cp -R $origdir $newdir
cd $newdir
source PKGBUILD
if [ -z "$_kernver" ]; then
echo "PKGBUILD does not have $_kernver."
return 1
fi
sed "s/$_kernver/$kernel/g" -i PKGBUILD
sed "s/pkgname=$pkgname/pkgname=$pkgname-$kernel/g" -i PKGBUILD
# Build!
makepkg
# Post build messages/install
if [ $? = 0 ]; then
package="`find $newdir -name *pkg.tar.gz`"
# variable is at top
if [ "$pacman" = "1" ]; then
pacman -U $package
else
echo "Package is ready to install: $package"
fi
else
echo "Build failed"
fi
sorry if there's any stupid bash in there, i'm tired. and yeah, I know it's a tad verbose and spacy, but it seems to works fine.
James

Iphitus > I'm looking 4 something like your script that will allow me to load spca5xx when running my custom kernelbeyond
Unfortunetely spca5xx seems not to be manageable by your abs-module script, as its PKGBUILD doesn't have a variable called _kernver.
Log :
/usr/bin/abs-make-module spca5xx
No kernel specified, building for: 2.6.17-beyond-LLEWELLYN
PKGBUILD does not have .
/usr/bin/abs-make-module: line 52: return: can only `return' from a function or sourced script
sed: -e expression #1, char 0: no previous regular expression
==> Making package: spca5xx-2.6.17-beyond-LLEWELLYN 0.60.00-2 (Sun Jul 23 11:44:52 CEST 2006)
==> Validating source files with MD5sums
spca5xx-20060501.tar.gz ... Passed
==> Extracting Sources...
==> tar --use-compress-program=gzip -xf spca5xx-20060501.tar.gz
tar: spca5xx-20060501/drivers: implausibly old time stamp 1970-01-01 01:00:00
==> Starting build()...
./PKGBUILD: line 13: cd: /var/abs/local/spca5xx-2.6.17-beyond-LLEWELLYN/src/spca5xx-2.6.17-beyond-LLEWELLYN-20060501: No such file or directory
make: *** No targets specified and no makefile found. Stop.
==> ERROR: Build Failed. Aborting...
Build failed

Problem inserting module for my dvb-s2 card on any kernel after 2.6.35

Firstly these drivers contain some proprietary bits so I have to download them from here. Basically it's some modified version of the cx23885 module from the mainline kernel.
Secondly here is a 10 page discussion on the TBS forums about this driver and getting it to work with kernels after 2.6.35.
Card is TBS 6891.
These proprietary drivers seem to be working with other distros such as Fedora and Ubuntu as witnessed in the previously linked thread, but, for some reason when I try and insert the module on my Arch Linux x86_64 box I get the following error.
# modprobe cx23885
FATAL: Error inserting cx23885 (/lib/modules/2.6.38-ARCH/kernel/drivers/media/video/cx23885/cx23885.ko): Unknown symbol in module, or unknown parameter (see dmesg)
# dmesg|tail -n1
[ 2373.648484] cx23885: Unknown symbol v4l2_i2c_new_subdev_cfg (err 0)
So I was wondering if anyone might be able to help with this. Maybe Fedora or Ubuntu have kernel config options different to Arch that I could try. Or kernel/v4l patches I could try.
Last edited by frontwheelskid (2011-06-08 10:48:01)

"cody" has replied in the tbs forums with information to get this compiled and working with arch linux:
it seems though on ArchLinux you need to do one extra step before 'make install':
# rm -rf /lib/modules/<kernel_version>/kernel/drivers/media/
for example:
# rm -rf /lib/modules/2.6.39-ARCH/kernel/drivers/media/
because otherwise the existing V4L modules in ArchLinux mixed up in a wrong way with the one installed by TBS Linux driver package.
I hope this info shortens other peoples searches!
Ali.

[SOLVED]problem with Bumblebee and Kernel 3.11-1-2

Hi!
I'm having problems with Bumblebee from Kernel 3.10 but I read that Kernel 3.11 solved the problem, I searched and tried possible solutions to my problem unsuccessfully
The message shows me when I run "optirun":
[ 5454.262739] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) No devices detected.
[ 5454.262776] [ERROR]Aborting because fallback start is disabled.
I've tried with wiki's solutions, forums solutions...
Configurations files:
/etc/bumblebee/bumblebee.conf:
# Configuration file for Bumblebee. Values should **not** be put between quotes
## Server options. Any change made in this section will need a server restart
# to take effect.
[bumblebeed]
# The secondary Xorg server DISPLAY number
VirtualDisplay=:8
# Should the unused Xorg server be kept running? Set this to true if waiting
# for X to be ready is too long and don't need power management at all.
KeepUnusedXServer=false
# The name of the Bumbleblee server group name (GID name)
ServerGroup=bumblebee
# Card power state at exit. Set to false if the card shoud be ON when Bumblebee
# server exits.
TurnCardOffAtExit=false
# The default behavior of '-f' option on optirun. If set to "true", '-f' will
# be ignored.
NoEcoModeOverride=false
# The Driver used by Bumblebee server. If this value is not set (or empty),
# auto-detection is performed. The available drivers are nvidia and nouveau
# (See also the driver-specific sections below)
Driver=
# Directory with a dummy config file to pass as a -configdir to secondary X
XorgConfDir=/etc/bumblebee/xorg.conf.d
## Client options. Will take effect on the next optirun executed.
[optirun]
# Acceleration/ rendering bridge, possible values are auto, virtualgl and
# primus.
Bridge=virtualgl
# The method used for VirtualGL to transport frames between X servers.
# Possible values are proxy, jpeg, rgb, xv and yuv.
VGLTransport=proxy
# List of paths which are searched for the primus libGL.so.1 when using
# the primus bridge
PrimusLibraryPath=/usr/lib/primus:/usr/lib32/primus
# Should the program run under optirun even if Bumblebee server or nvidia card
# is not available?
AllowFallbackToIGC=false
# Driver-specific settings are grouped under [driver-NAME]. The sections are
# parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
# detection resolves to NAME).
# PMMethod: method to use for saving power by disabling the nvidia card, valid
# values are: auto - automatically detect which PM method to use
# bbswitch - new in BB 3, recommended if available
# switcheroo - vga_switcheroo method, use at your own risk
# none - disable PM completely
# https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods
## Section with nvidia driver specific options, only parsed if Driver=nvidia
[driver-nvidia]
# Module name to load, defaults to Driver if empty or unset
KernelDriver=nvidia
PMMethod=auto
# colon-separated path to the nvidia libraries
LibraryPath=/usr/lib/nvidia:/usr/lib32/nvidia
# comma-separated path of the directory containing nvidia_drv.so and the
# default Xorg modules path
XorgModulePath=/usr/lib/nvidia/xorg/,/usr/lib/xorg/modules
XorgConfFile=/etc/bumblebee/xorg.conf.nvidia
## Section with nouveau driver specific options, only parsed if Driver=nouveau
[driver-nouveau]
KernelDriver=nouveau
PMMethod=auto
XorgConfFile=/etc/bumblebee/xorg.conf.nouveau
/etc/bumblebee/xorg.conf.nvidia
Section "ServerLayout"
Identifier "Layout0"
Option "AutoAddDevices" "false"
Option "AutoAddGPU" "false"
EndSection
Section "Device"
Identifier "DiscreteNvidia"
Driver "nvidia"
VendorName "NVIDIA Corporation"
# If the X server does not automatically detect your VGA device,
# you can manually set it here.
# To get the BusID prop, run `lspci | egrep 'VGA|3D'` and input the data
# as you see in the commented example.
# This Setting may be needed in some platforms with more than one
# nvidia card, which may confuse the proprietary driver (e.g.,
# trying to take ownership of the wrong device). Also needed on Ubuntu 13.04.
BusID "PCI:01:00.0"
# Setting ProbeAllGpus to false prevents the new proprietary driver
# instance spawned to try to control the integrated graphics card,
# which is already being managed outside bumblebee.
# This option doesn't hurt and it is required on platforms running
# more than one nvidia graphics card with the proprietary driver.
# (E.g. Macbook Pro pre-2010 with nVidia 9400M + 9600M GT).
# If this option is not set, the new Xorg may blacken the screen and
# render it unusable (unless you have some way to run killall Xorg).
Option "ProbeAllGpus" "false"
Option "NoLogo" "true"
Option "UseEDID" "false"
Option "UseDisplayDevice" "none"
EndSection
lspci |grep NVIDIA:
01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 640M] (rev a1)
I hope can help me
Thanks!
Last edited by surrealistic (2013-11-04 18:46:35)

My /var/log/Xorg.8.log:
[ 337.161]
X.Org X Server 1.14.4
Release Date: 2013-10-31
[ 337.161] X Protocol Version 11, Revision 0
[ 337.161] Build Operating System: Linux 3.11.6-1-ARCH x86_64
[ 337.161] Current Operating System: Linux h131h-laptop 3.11.6-1-ARCH #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013 x86_64
[ 337.161] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=4eb69984-2228-4aba-9863-28a7fa854e51 rw quiet
[ 337.161] Build Date: 01 November 2013 05:10:48PM
[ 337.161]
[ 337.161] Current version of pixman: 0.30.2
[ 337.161] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 337.161] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 337.161] (==) Log file: "/var/log/Xorg.8.log", Time: Mon Nov 4 14:20:04 2013
[ 337.161] (++) Using config file: "/etc/bumblebee/xorg.conf.nvidia"
[ 337.161] (++) Using config directory: "/etc/bumblebee/xorg.conf.d"
[ 337.161] (==) ServerLayout "Layout0"
[ 337.161] (==) No screen section available. Using defaults.
[ 337.161] (**) |-->Screen "Default Screen Section" (0)
[ 337.161] (**) | |-->Monitor "<default monitor>"
[ 337.161] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 337.161] (**) | |-->Device "DiscreteNvidia"
[ 337.161] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 337.161] (**) Option "AutoAddDevices" "false"
[ 337.161] (**) Option "AutoAddGPU" "false"
[ 337.161] (**) Not automatically adding devices
[ 337.161] (==) Automatically enabling devices
[ 337.161] (**) Not automatically adding GPU devices
[ 337.161] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 337.162] Entry deleted from font path.
[ 337.162] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 337.162] Entry deleted from font path.
[ 337.162] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 337.162] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 337.162] Entry deleted from font path.
[ 337.162] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 337.162] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 337.162] (++) ModulePath set to "/usr/lib/nvidia/xorg/,/usr/lib/xorg/modules"
[ 337.162] (==) |-->Input Device "<default pointer>"
[ 337.162] (==) |-->Input Device "<default keyboard>"
[ 337.162] (==) The core pointer device wasn't specified explicitly in the layout.
Using the default mouse configuration.
[ 337.162] (==) The core keyboard device wasn't specified explicitly in the layout.
Using the default keyboard configuration.
[ 337.162] (II) Loader magic: 0x7fdc20
[ 337.162] (II) Module ABI versions:
[ 337.162] X.Org ANSI C Emulation: 0.4
[ 337.162] X.Org Video Driver: 14.1
[ 337.162] X.Org XInput driver : 19.1
[ 337.162] X.Org Server Extension : 7.0
[ 337.162] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 337.162] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 337.162] setversion 1.4 failed
[ 337.163] (--) PCI:*(0:1:0:0) 10de:0fd2:1025:0648 rev 161, Mem @ 0xb2000000/16777216, 0xa0000000/268435456, 0xb0000000/33554432, I/O @ 0x00002000/128
[ 337.163] Initializing built-in extension Generic Event Extension
[ 337.163] Initializing built-in extension SHAPE
[ 337.163] Initializing built-in extension MIT-SHM
[ 337.163] Initializing built-in extension XInputExtension
[ 337.163] Initializing built-in extension XTEST
[ 337.163] Initializing built-in extension BIG-REQUESTS
[ 337.163] Initializing built-in extension SYNC
[ 337.163] Initializing built-in extension XKEYBOARD
[ 337.163] Initializing built-in extension XC-MISC
[ 337.163] Initializing built-in extension SECURITY
[ 337.163] Initializing built-in extension XINERAMA
[ 337.163] Initializing built-in extension XFIXES
[ 337.163] Initializing built-in extension RENDER
[ 337.163] Initializing built-in extension RANDR
[ 337.164] Initializing built-in extension COMPOSITE
[ 337.164] Initializing built-in extension DAMAGE
[ 337.164] Initializing built-in extension MIT-SCREEN-SAVER
[ 337.164] Initializing built-in extension DOUBLE-BUFFER
[ 337.164] Initializing built-in extension RECORD
[ 337.164] Initializing built-in extension DPMS
[ 337.164] Initializing built-in extension X-Resource
[ 337.164] Initializing built-in extension XVideo
[ 337.164] Initializing built-in extension XVideo-MotionCompensation
[ 337.164] Initializing built-in extension XFree86-VidModeExtension
[ 337.164] Initializing built-in extension XFree86-DGA
[ 337.164] Initializing built-in extension XFree86-DRI
[ 337.164] Initializing built-in extension DRI2
[ 337.164] (II) LoadModule: "glx"
[ 337.164] (II) Loading /usr/lib/nvidia/xorg/modules/extensions/libglx.so
[ 337.172] (II) Module glx: vendor="NVIDIA Corporation"
[ 337.172] compiled for 4.0.2, module version = 1.0.0
[ 337.172] Module class: X.Org Server Extension
[ 337.172] (II) NVIDIA GLX Module 325.15 Wed Jul 31 18:12:00 PDT 2013
[ 337.172] Loading extension GLX
[ 337.172] (II) LoadModule: "nvidia"
[ 337.172] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 337.172] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 337.172] compiled for 4.0.2, module version = 1.0.0
[ 337.172] Module class: X.Org Video Driver
[ 337.172] (II) LoadModule: "mouse"
[ 337.172] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
[ 337.172] (II) Module mouse: vendor="X.Org Foundation"
[ 337.172] compiled for 1.14.0, module version = 1.9.0
[ 337.172] Module class: X.Org XInput Driver
[ 337.172] ABI class: X.Org XInput driver, version 19.1
[ 337.172] (II) LoadModule: "kbd"
[ 337.173] (WW) Warning, couldn't open module kbd
[ 337.173] (II) UnloadModule: "kbd"
[ 337.173] (II) Unloading kbd
[ 337.173] (EE) Failed to load module "kbd" (module does not exist, 0)
[ 337.173] (II) NVIDIA dlloader X Driver 325.15 Wed Jul 31 17:50:57 PDT 2013
[ 337.173] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 337.173] (--) using VT number 1
[ 337.173] (II) Loading sub module "fb"
[ 337.173] (II) LoadModule: "fb"
[ 337.173] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 337.173] (II) Module fb: vendor="X.Org Foundation"
[ 337.173] compiled for 1.14.4, module version = 1.0.0
[ 337.173] ABI class: X.Org ANSI C Emulation, version 0.4
[ 337.173] (WW) Unresolved symbol: fbGetGCPrivateKey
[ 337.173] (II) Loading sub module "wfb"
[ 337.173] (II) LoadModule: "wfb"
[ 337.173] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 337.173] (II) Module wfb: vendor="X.Org Foundation"
[ 337.173] compiled for 1.14.4, module version = 1.0.0
[ 337.173] ABI class: X.Org ANSI C Emulation, version 0.4
[ 337.173] (II) Loading sub module "shadow"
[ 337.173] (II) LoadModule: "shadow"
[ 337.173] (II) Loading /usr/lib/xorg/modules/libshadow.so
[ 337.173] (II) Module shadow: vendor="X.Org Foundation"
[ 337.173] compiled for 1.14.4, module version = 1.1.0
[ 337.173] ABI class: X.Org ANSI C Emulation, version 0.4
[ 337.173] (II) Loading sub module "ramdac"
[ 337.173] (II) LoadModule: "ramdac"
[ 337.173] (II) Module "ramdac" already built-in
[ 337.174] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 337.174] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 337.174] (==) NVIDIA(0): RGB weight 888
[ 337.174] (==) NVIDIA(0): Default visual is TrueColor
[ 337.174] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 337.174] (**) NVIDIA(0): Option "NoLogo" "true"
[ 337.174] (**) NVIDIA(0): Option "ProbeAllGpus" "false"
[ 337.174] (**) NVIDIA(0): Option "UseEDID" "false"
[ 337.174] (**) NVIDIA(0): Option "UseDisplayDevice" "none"
[ 337.174] (**) NVIDIA(0): Enabling 2D acceleration
[ 337.174] (**) NVIDIA(0): Ignoring EDIDs
[ 337.174] (**) NVIDIA(0): Option "UseDisplayDevice" set to "none"; enabling NoScanout
[ 337.174] (**) NVIDIA(0): mode
[ 341.309] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
[ 341.309] (EE) NVIDIA(0): check your system's kernel log for additional error
[ 341.309] (EE) NVIDIA(0): messages and refer to Chapter 8: Common Problems in the
[ 341.309] (EE) NVIDIA(0): README for additional information.
[ 341.309] (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
[ 341.309] (EE) NVIDIA(0): Failing initialization of X screen 0
[ 341.309] (II) UnloadModule: "nvidia"
[ 341.309] (II) UnloadSubModule: "shadow"
[ 341.309] (II) UnloadSubModule: "wfb"
[ 341.309] (II) UnloadSubModule: "fb"
[ 341.309] (EE) Screen(s) found, but none have a usable configuration.
[ 341.309] (EE)
Fatal server error:
[ 341.309] (EE) no screens found(EE)
[ 341.309] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 341.309] (EE) Please also check the log file at "/var/log/Xorg.8.log" for additional information.
[ 341.309] (EE)
[ 341.309] (EE) Server terminated with error (1). Closing log file.
dmesg |grep bbswitch:
[ 13.570577] bbswitch: version 0.7
[ 13.570585] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
[ 13.570591] bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP
[ 13.570687] bbswitch: detected an Optimus _DSM function
[ 13.570741] bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on
[ 13.572354] bbswitch: disabling discrete graphics
[ 261.419114] bbswitch: enabling discrete graphics
[ 278.445698] bbswitch: disabling discrete graphics
[ 279.055257] bbswitch: enabling discrete graphics
[ 286.292315] bbswitch: disabling discrete graphics
[ 291.911052] bbswitch: enabling discrete graphics
[ 310.011289] bbswitch: disabling discrete graphics
[ 336.982794] bbswitch: enabling discrete graphics
[ 349.526470] bbswitch: enabling discrete graphics
I used "rcutree" option as shown in the post that you put, but I've deleted all changes made to use default configurations, because the solution of the post didn't work

Build a custom kernel

can i have a step by step on how to easily build a custom kernel with abs or whatever. ty

Well, I created this thread because most of the udev talks at this board referred to a custom kernel to speedup the udev events which some have suggested is a bug. With fast computers the udev events loads in a few seconds while slower computers such as a p2 could take perhaps up to a minute to load just the udev events. That issue has been posted at the bugs and such talks about it have been posted at this board going back a few years now.
I have also read at other boards the kernel 2.4 is still very supported. The software that needs the 2.6 kernel is fixed for the 2.4 kernel. So in these regards, the 2.4 kernel can be an important factor for slower computers.
I have tested many distros. Damn small linux (DSL) being the fastest to boot to root with the 2.4 kernel. On my computer it only takes DSL about 20 seconds, slackware-8 about 40 second while arch linux takes 60 seconds with the modified start_udev file and about 90 seconds normally. These three distrols detect the same modules and everything seems to be working fine except the sound card where I have to set it up for each of the distros.
I like this arch linux because I am able to learn linux from the groundup. Such as installing by unetbootin, Packman, modifying a file, and anything else to get to startx, but for the members that have an old computer, there seems to be an ongoing issue of udev. If this udev bug could be fixed, a boot to root would take only about 35 seconds.
It seems to address this udev events issue, a custom kernel is needed. one that does not take 10+ hours to build. a precompiled kernel could addrees this issus until the bug is fixed.
Last edited by windoze (2008-01-16 01:17:20)

Vmware-server-modules and kernel 2.6.19 [solved]

I'm trying to rebuild the vmware server modules from AUR for the new kernel. After adjusting the files for the kernel version and doing makepkg I get the following:
==> Validating source files with MD5sums
VMware-server-1.0.1-29996.tar.gz ... Passed
==> Extracting Sources...
==> tar --use-compress-program=gzip -xf VMware-server-1.0.1-29996.tar.gz
==> Starting build()...
Using 2.6.x kernel build system.
make: Entering directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only'
make -C /lib/modules/2.6.19-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.19-ARCH'
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/linux/hostif.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/cpuid.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/hash.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/memtrack.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/phystrack.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/task.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/vmx86.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmcore/moduleloop.o
LD [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmmon.mod.o
LD [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-2.6.19-ARCH'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only'
Using 2.6.x kernel build system.
make: Entering directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only'
make -C /lib/modules/2.6.19-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.19-ARCH'
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/driver.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/hub.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.o
/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c: In function 'VNetCopyDatagramToUser':
/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c:629: error: 'CHECKSUM_HW' undeclared (first use in this function)
/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c:629: error: (Each undeclared identifier is reported only once
/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c:629: error: for each function it appears in.)
make[2]: *** [/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.o] Error 1
make[1]: *** [_module_/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.19-ARCH'
make: *** [vmnet.ko] Error 2
make: Leaving directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only'
==> ERROR: Build Failed. Aborting...
It seems the userif module breaks. I haven't a clue how to solve this. :?

Progress:
AUR
which leads to
http://www.vmware.com/community/thread. … 4&tstart=0
EDIT: package in AUR has been updated. Thnx pizzapunk.

[SOLVED] Building flashcache - need kernel source?

Sorry for noob question, but..
Trying to build flashcache, and it seems that kernel source is required. How do I obtain the source?
Last edited by asg1448 (2014-07-07 22:51:15)

Trilby wrote:No, 3.15.2-1
I upgraded to 3.15.2-1-ARCH and have exactly the same issue
Note, that building of flashcache itself completes fine, the issue happens when I install the built module:
loading packages...
warning: flashcache-dkms-git-1.0.r223.g304bbc1-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Packages (1): flashcache-dkms-git-1.0.r223.g304bbc1-1
Total Installed Size: 0.54 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [##########################################] 100%
(1/1) checking package integrity [##########################################] 100%
(1/1) loading package files [##########################################] 100%
(1/1) checking for file conflicts [##########################################] 100%
(1/1) checking available disk space [##########################################] 100%
flashcache, 1.0.r223.g304bbc1: added
Deleting module version: 1.0.r223.g304bbc1
completely from the DKMS tree.
Done.
(1/1) reinstalling flashcache-dkms-git [##########################################] 100%
>>> DKMS: Module install
dkms install -m flashcache -v 1.0.r223.g304bbc1
Creating symlink /var/lib/dkms/flashcache/1.0.r223.g304bbc1/source ->
/usr/src/flashcache-1.0.r223.g304bbc1
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area....
KERNEL_TREE=/usr/lib/modules/3.15.2-1-ARCH/build make modules....(bad exit status: 2)
Error! Bad return status for module build on kernel: 3.15.2-1-ARCH (x86_64)
Consult /var/lib/dkms/flashcache/1.0.r223.g304bbc1/build/make.log for more information.
modprobe: FATAL: Module flashcache not found.

[2.6.37] Problems with module compression

Hello,
during the last days I had problems installing carl9170-driver package from the aur. It is a package based on compat-wireless.
Some other people had similar problems with other compat-wireless aur packages
All the packages that are based on compat-wireless provide new versions of already existing kernel modules. They put those modules under /lib/modules/kernel-version/updates.
After installing depmod -a should find the new modules in the /updates folder and after a reboot you can use the updated wireless drivers.
This does not work for kernel 2.6.37 because all the in-kernel modules are .gz compressed but the carl9170-driver package produces uncompressed modules.
I guess that depmod is not able to work correctly if you mix compressed modules with uncompressed ones.
I found this https://patchwork.kernel.org/patch/4039/ and it seems that there are configuration options wheter you get a compressed or uncompressed module when you run "make install_modules" in a PKGBUILD.
These configuration is made in "Makefile.modinst"
So the question is: Is this a problem with arch's kernel? I think when compressed in-kernel-modules are used, then external modules should compile in the same way.

Thanks for your post. I've been reporting this problem for weeks:
https://aur.archlinux.org/packages.php?ID=41472
https://aur.archlinux.org/packages.php?ID=41485
https://bugs.archlinux.org/task/22633
I solved the problem by going to /lib/modules/kernel2.6.37ARCH/updates...iwlwifi and then ran:
cd /lib/modules/2.6.37ARCH/update
gzip -r *
depmod
Then I reloaded the modules and finally depmod would report that the compat-wireless one was loaded.
The above instructions only worked with compat-wireless-patched from AUR. I'm still unable to use compat-wireless-patched-daily even with the above trick (no module get loaded at all).
Last edited by alphazo (2011-02-20 19:54:59)

Problem with firewire (since kernel-update?) [solved]

Hi,
since i have updated my system, i am unable to connect my dv-camcorder to my firewire-card.
when i power on my dv-camcorder dmesg says:
firewire_core: phy config: card 0, new root=ffc1, gap_count=5
firewire_core: phy config: card 0, new root=ffc1, gap_count=5
firewire_core: created new fw device fw1 (0 config rom retries, S100)
ieee1394: raw1394: /dev/raw1394 device initialized
NOTE: The dv1394 driver is unsupported and may be removed in a future Linux rele
ase. Use raw1394 instead.
firewire_core: giving up on config rom for node id ffc1
If i then disconnect and reconnect it, dmesg says the following:
firewire_core: BM lock failed, making local node (ffc0) root.
firewire_core: phy config: card 0, new root=ffc0, gap_count=5
firewire_core: phy config: card 0, new root=ffc1, gap_count=5
firewire_core: phy config: card 0, new root=ffc1, gap_count=5
firewire_core: phy config: card 0, new root=ffc1, gap_count=5
firewire_core: created new fw device fw1 (0 config rom retries, S100)
I have tried a canon mv700 as well as a canon xm1, both lead to the same problem. I have tried to connect my camcorder also to my notebook which also runs the latest version of arch, but leads to the same problem too.
I think there is a problem with the new kernel or something. Two weeks ago, before updating my system, everything works well.
Any suggestions or ideas?
Anyone with similar problems?
Greets,
smove
Last edited by smove (2008-05-06 19:32:14)

I solved this problem. Since kernel 2.6.22 there is a new firewire-stack available called 'juju'. Because of it´s experimental state it is not recommend to use it. In the current kernel-package the old and the new firewire-modules are included but the new instable ones are used by default. To fix the problem you have to blacklist the new firewire-modules.
Create the following file:
/etc/modprobe.d/newfw_blacklist:
blacklist firewire-ohci
blacklist firewire-sbp2
Reboot your system and try to use your firewire again. Look if the old modules are loaded instead of the new firewire-* ones. I dont understand why the new firewire-modules are used by default in the new kernel-packages. Refering to http://wiki.linux1394.org/JujuMigration … 857ee71b93 it is not recommended to use the new modules yet.

Build modules for Virtualbox 4.2 guest

I expected to see packages for virtualbox 4.2 guest additions in package lists. Is there some reason why there aren't any?
Also, is there some reason why installing kernel source has to be such a PITA?
Building modules against installed kernel source is so easy --like with virtualbox guest additions.

yug wrote:
I expected to see packages for virtualbox 4.2 guest additions in package lists. Is there some reason why there aren't any?
Also, is there some reason why installing kernel source has to be such a PITA?
Building modules against installed kernel source is so easy --like with virtualbox guest additions.
I dunno, version 4.1 works fine enough. Do you need version 4.2 for a particular usage-type-thing?
community/virtualbox-additions 4.1.22-1 [installed]
The official all-in-one VirtualBox Guest Additions ISO/CD image
community/virtualbox-archlinux-additions 4.1.22-1
Additions only for Arch Linux guests (userspace tools)

Building module fails - vmlinux is truncated [solved]

Hello guys,
I cannot build the lenovo-sl-laptop-fan-control module anymore.
See the pkgbuild here: http://aur.archlinux.org/packages/le/le … l/PKGBUILD
All I get is this error message:
==> Starting make...
make -C /lib/modules/3.1.9-1-ARCH/build M=/tmp/packerbuild-1000/lenovo-sl-laptop/lenovo-sl-laptop/src/lenovo-sl-laptop-build modules
make[1]: Entering directory `/usr/src/linux-3.1.9-1-ARCH'
CC [M] /tmp/packerbuild-1000/lenovo-sl-laptop/lenovo-sl-laptop/src/lenovo-sl-laptop-build/lenovo-sl-laptop.o
Building modules, stage 2.
MODPOST 1 modules
FATAL: vmlinux is truncated. sechdrs[i].sh_offset=18446744071588955904 > sizeof(*hrd)=64
make[2]: *** [__modpost] Error 1
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/linux-3.1.9-1-ARCH'
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
The build failed.
Kernel version is linux-3.1.9-1-ARCH on a 64bit system.
Any ideas?
Regards,
Robert
Last edited by orschiro (2012-01-15 04:56:59)

I'm getting the same error message, this time from building the fglrx module on the 3.1.9 x86_64 kernel
2012-01-14 08:20:45
Building fglrx module for 3.1.9-1-ARCH kernel ...
patching file Makefile
Hunk #1 succeeded at 68 (offset 2 lines).
OsVersion says: SMP=1
file /proc/kallsyms says: SMP=1
file /lib/modules/3.1.9-1-ARCH/build/include/generated/autoconf.h says: SMP=1
1
0
file /lib/modules/3.1.9-1-ARCH/build/include/generated/autoconf.h says: MODVERSIONS=1
1
0
file /lib/modules/3.1.9-1-ARCH/build/arch/x86/include/asm/compat.h says: COMPAT_ALLOC_USER_SPACE=arch_compat_alloc_user_space
make: Entering directory `/usr/src/linux-3.1.9-1-ARCH'
CC [M] /tmp/catalyst.tZIAzG/firegl_public.o
In file included from /tmp/catalyst.tZIAzG/firegl_public.c:192:0:
/tmp/catalyst.tZIAzG/kcl_debug.h:202:5: warning: "_DEBUG" is not defined [-Wundef]
/tmp/catalyst.tZIAzG/kcl_debug.h:162:16: warning: ‘module_log_map’ defined but not used [-Wunused-variable]
/tmp/catalyst.tZIAzG/kcl_debug.h:175:19: warning: ‘module_type_map’ defined but not used [-Wunused-variable]
CC [M] /tmp/catalyst.tZIAzG/kcl_acpi.o
In file included from /tmp/catalyst.tZIAzG/kcl_acpi.c:33:0:
/tmp/catalyst.tZIAzG/kcl_debug.h:202:5: warning: "_DEBUG" is not defined [-Wundef]
/tmp/catalyst.tZIAzG/kcl_debug.h:162:16: warning: ‘module_log_map’ defined but not used [-Wunused-variable]
/tmp/catalyst.tZIAzG/kcl_debug.h:175:19: warning: ‘module_type_map’ defined but not used [-Wunused-variable]
CC [M] /tmp/catalyst.tZIAzG/kcl_agp.o
In file included from /tmp/catalyst.tZIAzG/kcl_agp.c:47:0:
/tmp/catalyst.tZIAzG/kcl_debug.h:202:5: warning: "_DEBUG" is not defined [-Wundef]
/tmp/catalyst.tZIAzG/kcl_debug.h:162:16: warning: ‘module_log_map’ defined but not used [-Wunused-variable]
/tmp/catalyst.tZIAzG/kcl_debug.h:175:19: warning: ‘module_type_map’ defined but not used [-Wunused-variable]
CC [M] /tmp/catalyst.tZIAzG/kcl_debug.o
In file included from /tmp/catalyst.tZIAzG/kcl_debug.c:39:0:
/tmp/catalyst.tZIAzG/kcl_debug.h:202:5: warning: "_DEBUG" is not defined [-Wundef]
/tmp/catalyst.tZIAzG/kcl_debug.c:45:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes]
/tmp/catalyst.tZIAzG/kcl_debug.c:65:14: warning: function declaration isn’t a prototype [-Wstrict-prototypes]
/tmp/catalyst.tZIAzG/kcl_debug.c: In function ‘prvGetCpuId’:
/tmp/catalyst.tZIAzG/kcl_debug.c:72:18: warning: unused variable ‘Mode’ [-Wunused-variable]
/tmp/catalyst.tZIAzG/kcl_debug.c: At top level:
/tmp/catalyst.tZIAzG/kcl_debug.h:162:16: warning: ‘module_log_map’ defined but not used [-Wunused-variable]
/tmp/catalyst.tZIAzG/kcl_debug.h:175:19: warning: ‘module_type_map’ defined but not used [-Wunused-variable]
CC [M] /tmp/catalyst.tZIAzG/kcl_ioctl.o
/tmp/catalyst.tZIAzG/kcl_ioctl.c: In function ‘KCL_IOCTL_RegisterConversion32’:
/tmp/catalyst.tZIAzG/kcl_ioctl.c:171:27: warning: extra tokens at end of #ifdef directive [enabled by default]
/tmp/catalyst.tZIAzG/kcl_ioctl.c: In function ‘KCL_IOCTL_UnregisterConversion32’:
/tmp/catalyst.tZIAzG/kcl_ioctl.c:183:27: warning: extra tokens at end of #ifdef directive [enabled by default]
CC [M] /tmp/catalyst.tZIAzG/kcl_io.o
CC [M] /tmp/catalyst.tZIAzG/kcl_pci.o
CC [M] /tmp/catalyst.tZIAzG/kcl_str.o
CC [M] /tmp/catalyst.tZIAzG/kcl_iommu.o
In file included from /tmp/catalyst.tZIAzG/kcl_iommu.c:45:0:
/tmp/catalyst.tZIAzG/kcl_debug.h:202:5: warning: "_DEBUG" is not defined [-Wundef]
/tmp/catalyst.tZIAzG/kcl_debug.h:162:16: warning: ‘module_log_map’ defined but not used [-Wunused-variable]
/tmp/catalyst.tZIAzG/kcl_debug.h:175:19: warning: ‘module_type_map’ defined but not used [-Wunused-variable]
CC [M] /tmp/catalyst.tZIAzG/kcl.o
CC [M] /tmp/catalyst.tZIAzG/kcl_wait.o
LD [M] /tmp/catalyst.tZIAzG/fglrx.o
Building modules, stage 2.
MODPOST 1 modules
FATAL: vmlinux is truncated. sechdrs[i].sh_offset=18446744071588955904 > sizeof(*hrd)=64
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
make: Leaving directory `/usr/src/linux-3.1.9-1-ARCH'
EDIT: didn't see the previous post ^^;;
Last edited by tuldok89 (2012-01-14 01:06:11)

Problem with modules and ModuleLoader

Hi everybody,
i'm facing a real funny problem with modules and
moduleLoader, i hope
it's not (only) my fault anyway...
If i create a normal flex project with fBuilder, i'm able to
use
modules in a lot of different ways (as mxml, as as in a
function etc..)...
but if i try to use them in my fds application (created with
fds
eclipse plugin or as a dataServices project) i can't use
modules. The compile-time error message is
always the same:
Could not resolve <mx:ModuleLoader> to a component
implementation
I tried a lot of solutions, paying attention to import all
the classes, to declaration, naming, positioning
etc...but nothing changes, this thing is drivining me
crazy!!!.
I will appreciate anykind of help.
TIA
Fabio

Any idea?

Problems building a stand alone application with LV 8.6.1.

I'm having problems building a stand alone application with LV8.6.1. I'm using a USB- 6008 DAQ and USB-6501 Digital device in the application. I already have an simple executable on the machine so the Run time Engine is already installed. For the USB DAQ device, I assume I need to include the DAQmx8.8 as one of the installers. When I attempt to build the application, I'm prompted for several disk, one being a distribuition disk 1. I have the installation disk for the developer package. I did not see a distribuiton disk as one of the installation disks. When I insert disk 1 I get an error that another application is trying to run. Could someone tell me which installers I need to include and where do I find the "distributor" disk.
Thank you,

are you building installer for the first time on this PC?...It usually asks for the drivers CDs and some toolkits if required.
you just need to use drivers CDs (comes with LabVIEW) from which you installed on this PC. If you have ever upgraded drivers, then you have to use the latest CDs only.......
another issue may be ...when u insert the driver disk, it has autorun, it will launch drivers installation wizard....close that and then try to build distribution.........
Message Edited by Anil Reddy on 09-25-2009 01:22 PM
Anil Punnam
CLD
LV 2012, TestStand 4.2..........

Problem building modules in kernel-2.6.29.6-rt

Similar Messages

Maybe you are looking for