SlackwareThis Forum is for the discussion of Slackware Linux.
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.
note: suse has a setting in yast to do networking "by traditional ifup" or "by network manager" and if you chose "by network manager in suse that will mess you up, especially on wireless, or it did for me at least.
also in yast/suse in netowork devices, you;ll find a little drop down box for dhcp options, make sure "change hostname by dhcp is off".
but you're better off here in slackware, it listens to what you tell it too
i tried root@slackw:~$ lspci | grep Realtek
but nothing happens
new line appears
i tried netconfig and configured my network but it said it couldn't know the lan card
i tried ifconfig (lo) and ip appears
when i install the driver on slack and typed if config (eth0)and ip appears then
did any body know a solution for my card i think it is in lo and eth0
please, as root, type the command "lspci" (without quotes) and post the result of this. also, add the result of "ifconfig -a".
look man
i have configured my network with
>>netconfig
and my ip 196.168.1.123
mask 255.255.255.0
gateway 196.168.1.1
>>lspci
alot of things but what i think u want to know is
00:0b.0 ethernet:unknown device 1904:8139 (rev 01)
>>ifconfig -a
lo
link encap :local loopback
inet addr:127.0.0.1 mask:255.0.0.0
uploopback running MTU :16436 Metric:1
Rx packets=0 errors=0 dropped=0 overruns:0 frame:0
TX packets=0 errors=0 dropped=0 overruns:0 carrier:0
then can u solve my problem??????????
remmber that when i used my installation filies lo->eth0,ip and mask and
gateway are written correctly
I agree with you. Infact, I do have a LAN card which I have driver for 2.4.x and 2.5.x only. The driver doesn;t exist in any of the linux distributions out of the box. I have to manually compile it. The card seems to be RTC8139d by Intex and driver is provided by Silan. The module name is sc92031
Here's info about my card
So, after trying many other kernel 2.6.x based distributions with no luck, I am back using Slackware 10.2 with kernel 2.4.31 and it works fine. If anyone could help me make some changes to the source file of the driver inorder to make it work under kernel 2.6.x, I would feel blessed.
Last edited by manishsingh4u; 07-14-2006 at 02:19 PM.
look man
i have configured my network with
>>netconfig
and my ip 196.168.1.123
mask 255.255.255.0
gateway 196.168.1.1
>>lspci
alot of things but what i think u want to know is
00:0b.0 ethernet:unknown device 1904:8139 (rev 01)
>>ifconfig -a
lo
link encap :local loopback
inet addr:127.0.0.1 mask:255.0.0.0
uploopback running MTU :16436 Metric:1
Rx packets=0 errors=0 dropped=0 overruns:0 frame:0
TX packets=0 errors=0 dropped=0 overruns:0 carrier:0
then can u solve my problem??????????
remmber that when i used my installation filies lo->eth0,ip and mask and
gateway are written correctly
why doesn't the company of my card relase a driver for kernal 2.6 or 2.x kernal
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.