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.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am trying to set up Debian Lenny on a laptop and it seams to be winning. I did get a successful install and all that and it runs fine. But on two fronts it seams to be winning.
The most annoying first. Disabling the touchtap thing.
I have edited xorg.conf to contain the same info that is in my laptop which has that tap thing disabled yet this laptop refuses to yield to my changes. When I run 'synclient -l' I get "Can't access shared memory area. SHMConfig disabled?"
I double double quad checked that entry in xorg.conf and it is correct.
Option "SHMConfig" "on"
Form what I have read I have come to two conclusions. 1 the touchpad in this laptop is not compatible with the synaptics driver. So how do I identify this touch pad. I have not found any commands to run via google. lspci and lsusb don't show it. If I could identify it I might be able to find more relevant instruction via google.
2. The touchpad is not assigned the standard /dev/psaux device file. If this is the case then SMHConfig could not find it to talk to it. Hench, how do I find out where the system sees the touchpad so that I can change xorg.conf to reflect where it really is.
Pointers and or links would be much appreciated.
On to the second problem.
This laptop does not have built in wireless and so uses a Trendnet TEW-421PC :B1 card. I have followed the directions and installed the ndiswrapper and driver with success. I can activate the card with 'modprobe ndiswrapper' and all seams to be fine with it, but I can't get it to connect to the wireless service. For some reason it will not pick up an ip. This card is working fine in xp. I have made an entry in /etc/network/interfaces for my local wireless with no success. I have setup a config in the kde control panel for my local network yet nothing seams to be working.
KWiFiManager will scan and report that my wireless service is available but I can't connect to it. I seam to be missing something.
I have done the whole un/reinstall thingy with the driver and wrapper. I did see at one point that there is a native driver, alpha I think, but have not been able to locate that page again.
If anyone could help me with either one of these problems I am sure the owner would be very thankful.
The area i live in is remote. In order for someone to piggy back onto me they would have to park out it the front yard where I could see them. On top of that at this time of the year with 2 feet of snow It would get quite cold for them.
So I have no need of encription. But thanks I hadn't thought of that. Any ideas are better than what I have at the moment.
OK I have the touch tap thingy fixed. It seams that logging out does not completely kill the gui somehow. I rebooted the machine and of course I had some errors in xorg.conf relating to the 'screen' identifier and when I got those fixed and the gui booted up the that tap thingy was disabled.
I still have the problem with the wireless card though.
OK I have the touch tap thingy fixed. It seams that logging out does not completely kill the gui somehow. I rebooted the machine and of course I had some errors in xorg.conf relating to the 'screen' identifier and when I got those fixed and the gui booted up the that tap thingy was disabled.
I still have the problem with the wireless card though.
If you still need help on your wireless maybe this link will help:
I think I have discovered the reason behind that problem too. It seams that my wireless access point has died. I set a static ip on the card and it seamed to connect. Then the boy got home and he was not able to connect with his vista and he has been having toruble for the past few days. I reset the router then there was no wireless at all. In fact the blue indicator light does not even light.
There is one issue with the wireless card yet. That is gettin it to auto load the driver when I plug in the card. I have tried 'modprobe -m' I think it is and that came back as a depriceated option and the driver does not load unless I run 'modprobe ndiswrapper'. (The commands may not be right as I am not looking at them at the moment.) I plan on taking the laptop to a place where I can check to see if the wireless is actually working tomorrow.
The touchtap thingy required a correct xorg.conf file and a complete reboot of the xserver. Somehow just logging out through the kde K button does not accomplish this and a ctrl+alt+backspace or comp restart will.
The wireless. I have the ndisswrapper installed and it is working mostly correctly. If I set the /etc/network/interfaces entry for this card to be something like
it appears to connects just fine. However I have no internet access. I am able to ping the router and other machines on my network.
If I set it to use dhcp I can't get it to connect to anything.
I still have two issues relating to the wireless.
1 I have to manually load the ndiswrapper. I need this to be automated
2 I have to use a static ip. This is beyond the owner and it to needs to be automated.
> modprobe ndiswrapper -m as instructed by the tutorial to auto-load the driver returns : invalid option -m
The file (both my laptop[using it for comparison using same os except 64] and the one I am working on) located in /etc/modporbe.d/ndiswrapper contains the line that the tutorial linked to above by marcia says that the 'modprobe ndiswrapper -m' command is suppose to put in it. However the dirver still does not autoload after a reboot
Don't know if it matters but this card is a removable pcmica card.
If I remove the card and reinsert it without a reboot this show up in dmesg | tail
(manually entered)
ADDRCONF(NETDEV_UP): wlan0: link is not ready
At the moment I am at a loss as to what to try next.
Make sure you have your default gateway set "route add default gw <address>" Then make sure you have your DNS servers set. (forget how to set them, sorry)
but it relates to FC3 and I don't have this in my file system. What is the Debian equivalent?
Scratch that above. All I had to do was add a line in /etc/modules that says ndiswrapper. Now the card is functioning automatically when plugged in, as far as the driver goes.
That leaves getting it to access my wireless network. I don't know if this is what is happening but this is how it appears to me. I am not a programmer so keep that in mind.
It seams to me that I have a package missing. What that package does is make the connection between the manual/auto configuration on the bottom and the gui on top.
Now I can't ping anything. I don't know what is different from before but...
So it seams that my manual config is not worth anything.
I connected a cable to it and yes it has access that way.
In your interfaces file, try putting auto wlan0 before the iface stanza and of course change static to dhcp - see if that helps. You'll to do an ifdown wlan0 and then ifup wlan0 to test it.
If that still doesn't work, try running dhclient from the command line (as root) after the ifup.
well the touch pad can be set in bios to use the pad or ps2 or usb. cursers. or it can be set to all. while you in there set bios to none operating system no windows or what ever the new bios ask for anyway none os controlled. this let.s linux read the bios and load the irq. as the super user make sure your /etc/rc.d/rc.inet1 is set to executable. if it is not kde will never get it set in the control sent a auto dhcpcd will not happen at but. or it will not know to load the device. this is the same for /etc/rc.d/rc.inet2. while your in there the /etc/rc.d/rcinit1.conf make sure
itIPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="yes" <----.
DHCP_HOSTNAME[0]=""
if you have a ether card built in. the eth0 will be the ether card.
the next one eth1 this invokes the /etc/rc.d/rc.inet2.
so if you go to your /etc/rc.d/rc.m and read down you will see how it loads. theses are all bugs I have found out of the box on many different distro's. last but not least make sure your /usr/sbin/network_manager is also set to executable..
here is why I have found that during some crashes. like ndiswrappers hanging up it corrupts the rc.m file. put a little dot. <-- in front of the scripts. do not ask me how this happens. but it does.
Now if all that checks out. ifconfig ethX or wlanX what ever you have mine is ifconfig eth0 up then go type dmesg and read the out put.
Last but not least if you can find a linux driver for the card uses it.Build etc.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.