Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
well this will not work here, the package is for kernel 2.6.38 and earlier, I have only 3.xxx on all my computers. Which kernel do you have? please post the output of
kernel-devel was not installed - it was not part of the default installation - but it is now. Whether or not it will work I don't know, as installation of two of the dependency packages (xen and desktop) failed.
The significance of knudfl's contribution on this last passed me by (my limited knowledge; no offence to knudfl intended). Apologies for not following up on this before.
Well, can you tell us why the installation of the dependency packages failed?
The problem is that after all the installation of the driver should work. If it doesn't there are three possible reasons, 1. you made a mistake, 2. OpenSuse doesn't work as expected or 3. the edimax-package doesn't work.
Since I tried to build the driver with Archlinux and it did as well not work, I'd suspect (and I think this is what knudfl meant) that the package is not in a proper state.
Well, the last thing you can do is install the devel-package, and if then you can still not build the driver, you should contact the support of Edimax (or the firm who contribute the package). You've paid for the device, they provide a package for Linux, so they should help you.
The two dependency packages were kernel-desktop-develop and kernel-xen-develop. The messages generated in each case respectively were:
Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /lib/modules/2.6.37.1-1.2-desktop/build: cpio: rename failed - Is a directory
Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /lib/modules/2.6.37.1-1.2-xen/build: cpio: rename failed - Is a directory
Having installed kernel-develop, running make again produced the same output. I would agree with you that it seems the driver files do not work. It seems to me that it is the makefile that is at fault, for the reason I gave in an ealier post:
Quote:
Looking at the response to make:
make ARCH=i386 CROSS_COMPILE= -C /lib/modules/2.6.37.1-1.2-desktop/build M=/root/workspace/Linux_Driver/rtl8192CU_8188CU_linux_v2.0.939.20100726/driver/rtl8192CU_linux_v2.0.939.20100726 modules
make[1]: Entering directory `/lib/modules/2.6.37.1-1.2-desktop/build'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory `/lib/modules/2.6.37.1-1.2-desktop/build'
make: *** [modules] Error 2
and the following line in the makefile (see attachment for the full context; it's line 262 or thereabouts, I think):
it appears to be an apparent recursion on 'modules' that is causing the problem.
So it looks as if I am going to have to fall back on ndiswrapper again, unless and until someone can come up with an explanation of how to correct the makefile or some other solution. I'll see if I can get anything out of Realtek.
The two dependency packages were kernel-desktop-develop and kernel-xen-develop. The messages generated in each case respectively were:
Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /lib/modules/2.6.37.1-1.2-desktop/build: cpio: rename failed - Is a directory
Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /lib/modules/2.6.37.1-1.2-xen/build: cpio: rename failed - Is a directory
Having installed kernel-develop, running make again produced the same output. I would agree with you that it seems the driver files do not work. It seems to me that it is the makefile that is at fault, for the reason I gave in an ealier post:
Quote:
Looking at the response to make:
make ARCH=i386 CROSS_COMPILE= -C /lib/modules/2.6.37.1-1.2-desktop/build M=/root/workspace/Linux_Driver/rtl8192CU_8188CU_linux_v2.0.939.20100726/driver/rtl8192CU_linux_v2.0.939.20100726 modules
make[1]: Entering directory `/lib/modules/2.6.37.1-1.2-desktop/build'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory `/lib/modules/2.6.37.1-1.2-desktop/build'
make: *** [modules] Error 2
and the following line in the makefile (see attachment for the full context; it's line 262 or thereabouts, I think):
it appears to be an apparent recursion on 'modules' that is causing the problem.
So it looks as if I am going to have to fall back on ndiswrapper again, unless and until someone can come up with an explanation of how to correct the makefile or some other solution. I'll see if I can get anything out of Realtek.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
