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!
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm running SuSE 9.1 personal and am trying to upgrade ndiswrapper from 0.06 to 0.10 to try and fix a wireless problem. First I uninstall 0.06 in YAST. Then, having untarred 0.10 I try make install but get the following error messages:
make: `arch/i386/kernel/asm-offsets.s' is up to date.
CC [M] /usr/src/packages/SOURCES/ndiswrapper-0.10/driver/wrapper.o
CC [M] /usr/src/packages/SOURCES/ndiswrapper-0.10/driver/iw_ndis.o
CC [M] /usr/src/packages/SOURCES/ndiswrapper-0.10/driver/loader.o
CC [M] /usr/src/packages/SOURCES/ndiswrapper-0.10/driver/ntoskernel.o
CC [M] /usr/src/packages/SOURCES/ndiswrapper-0.10/driver/ndis.o
CC [M] /usr/src/packages/SOURCES/ndiswrapper-0.10/driver/misc_funcs.o
CC [M] /usr/src/packages/SOURCES/ndiswrapper-0.10/driver/proc.o
CC [M] /usr/src/packages/SOURCES/ndiswrapper-0.10/driver/divdi3.o
CC [M] /usr/src/packages/SOURCES/ndiswrapper-0.10/driver/hal.o
CC [M] /usr/src/packages/SOURCES/ndiswrapper-0.10/driver/usb.o
/usr/src/packages/SOURCES/ndiswrapper-0.10/driver/usb.c: In function `usb_submit_nt_urb':
/usr/src/packages/SOURCES/ndiswrapper-0.10/driver/usb.c:337: error: structure has no member named `act_altsetting'
/usr/src/packages/SOURCES/ndiswrapper-0.10/driver/usb.c:340: error: structure has no member named `act_altsetting'
make: *** [/usr/src/packages/SOURCES/ndiswrapper-0.10/driver/usb.o] Error 1
make: *** [/usr/src/packages/SOURCES/ndiswrapper-0.10/driver] Error 2
make: Leaving directory `/usr/src/linux-2.6.4-52'
make: *** [default] Error 2
make: Leaving directory `/usr/src/packages/SOURCES/ndiswrapper-0.10/driver'
make: *** [install] Error 2
I have no idea what this means or how to fix it so any clues would be very welcome.
I am trying to compile and install the ndiswrapper-0.10 module. The folder ndiswrapper-10 contains various files including a Makefile and an Install file. The Install file simply says "As root run make install . This should compile both the kernel module and the userspace utilities." So, I cd to the appropriate directory, su, make install and get the error shown above.
I have removed the old ndiswrapper using the YAST rmp tool - give the same error. I don't know about building rpms - from what I've read it doesn't look too easy and I'm not confident about going down that route. That leaves dependencies. How can I check for dependencies?
Turns out my adaptor - Edimax EW-7126, (Realtek chip) - plus ndiswrapper plus Win driver is an unholy combination. Lights will blink but mode cannot be set to Managed, only ad-hoc. There's probably a way around this but life is short so... I yanked the card and swapped it with a smc2662w usb device from a win box and, (short firmware upgrade later), hey presto, connection.