Mepis 3.4.3-4 Driver Install

Save file on Desktop (or wherever you want) -> right click on it -> Extract -> Extract here. That should take care of unziping.

To install read the "README" and the "INSTALL" files that usually came with tarballs, I can't tell you what to do because I don't know what's in the tarball. To open the console in that directory, open it in Konqueror then press F4 than you'll be able to type the commands that are detailed in "INSTALL".

--
Post questions on www.mepislovers.org too.
Check out our wiki: www.mepislovers-wiki.org

The following is what the readme for the e1000-7.0.33 driver install instructions states:

Building and Installation
=========================

To build a binary RPM* package of this driver, run 'rpmbuild -tb
'. Replace with the specific filename
of the driver.

NOTE: For the build to work properly, the currently running kernel MUST
match the version and configuration of the installed kernel sources.
If you have just recompiled the kernel reboot the system now.

RPM functionality has only been tested in Red Hat distributions.

1. Move the base driver tar file to the directory of your choice. For
example, use /home/username/e1000 or /usr/local/src/e1000.

2. Untar/unzip archive:

tar zxf e1000-x.x.x.tar.gz

3. Change to the driver src directory:

cd e1000-x.x.x/src/

4. Compile the driver module:

make install

The binary will be installed as:

/lib/modules//kernel/drivers/net/e1000/e1000.[k]o

The install locations listed above are the default locations. They
might not be correct for certain Linux distributions. For more
information, see the ldistrib.txt file included in the driver tar.

5. Load the module using either the insmod or modprobe command:

modprobe e1000

insmod e1000

Note that for 2.6 kernels the insmod command can be used if the full
path to the driver module is specified. For example:

insmod /lib/modules//kernel/drivers/net/e1000/e1000.ko

6. Assign an IP address to the interface by entering the following, where
x is the interface number:

ifconfig ethx

7. Verify that the interface works. Enter the following, where
is the IP address for another machine on the same subnet as the
interface that is being tested:

ping

I am confused by the bianary RPM package build and do not fully understand how to do all the other steps. I thought Mepis was based on Debian. I think I understand how to do steps 1-4, but get lost in steps 5-7. If I just did steps 1-4 without the upfront RPM step, would this work in Mepis? I don't want to do anything to damage my entire OS. The ldistrib.txt file does not address issues related specifically to Mepis.

Can anyone give me some insight and specific details on how to solve my problem. Thanks.

Hermie

Are you sure you need to compile that module? I think e1000 is present in mepis.

Go to konsole, type "su" and type the root password to get the root prompt then type "modprobe e1000". If you don't get any error message it means that the driver loaded OK. Then try the command "ifconfig eth0 up" and then "dhclient".

So in summary:
su (and root password)
modprobe e1000
ifconfig eth0
dhclient

If that works and gives you a working card add "e1000" without the quotes in /etc/modules (at the end of file) You need to edit the file as root, like this:
su
kedit /etc/modules

--
Post questions on www.mepislovers.org too.
Check out our wiki: www.mepislovers-wiki.org

Adrian TM,

The following was obtained per your instructions in the lst konsole:

Password:
root@1[Wolff007]# modprobe e1000
root@1[Wolff007]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:15:F2:54:02:4A
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4939 errors:0 dropped:0 overruns:0 frame:0
TX packets:3370 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:854526 (834.4 KiB) TX bytes:1166020 (1.1 MiB)
Base address:0xd800 Memory:cffe0000-d0000000

root@1[Wolff007]# dhclient
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth0/00:15:f2:54:02:4a
Sending on LPF/eth0/00:15:f2:54:02:4a
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
root@1[Wolff007]#

In the 2nd konsole I get the following:

Wolff007@2[~]$ su
Password:
root@2[Wolff007]# kedit /etc/modules
kbuildsycoca running...
KWrited - Listening on Device /dev/pts/3
libhal.c 911 : Error sending msg: No property info.category on device with id /org/freedesktop/Hal/devices/computer
libhal.c 911 : Error sending msg: No property info.category on device with id /org/freedesktop/Hal/devices/scsi_0_0_0_0
libhal.c 911 : Error sending msg: No property info.category on device with id /org/freedesktop/Hal/devices/scsi_0_0_0_0
libhal.c 911 : Error sending msg: No property info.category on device with id /org/freedesktop/Hal/devices/scsi_0_0_0_0

In kedit I added # e1000 and hit the save button with the following result:

# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a `#', and everything on the line after them are ignored.
# e1000

In spite of following your instructions ( I am not sure I did the Kedit right), I still don't connect to the internet via DSL. Have I done something wrong. I don't know enough to completely interpret the information that I have obtained. Is there still hope? If so, what do I do next?

I greatly appreciate your interest in trying to help me.

Hermie

e1000 might even been loaded, Mepis usually does that automatically, you can run "lsmod | grep e1000" to see if it's loaded, if it's not loaded then look in /etc/modules, as you can read anything with a "#" sign in front is ignored -- I said "add e1000" not "add # e1000"

# a `#', and everything on the line after them are ignored.
# e1000

As I said that might be not needed, check with "lsmod | grep e1000"

I think that your Ethernet is working, the problem is otherwhere, probably your modem is not connect to Internet and doesn't provide an IP address "No DHCPOFFERS received."

Sorry I don't know much about your ADSL and how it's connection should be set up, most likely you can go to see your modem config if you go in a browser and type something like "http://dslrouter" (read the manual).

--
Post questions on www.mepislovers.org too.
Check out our wiki: www.mepislovers-wiki.org

Adrian TM:

In Kedit I changed # e1000 to just "el000", hit save, restarted my computer and still no connect. Kedit now shows:

# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a `#', and everything on the line after them are ignored.
e1000

When I try "Ismod | grep e1000", I get:

Wolff007@3[~]$ su
Password:
root@3[Wolff007]# Ismod | grep e1000
bash: Ismod: command not found
root@3[Wolff007]#

When I try "/etc/modules", I get:

Wolff007@4[~]$ su
Password:
root@4[Wolff007]# /etc/modules
bash: /etc/modules: Permission denied
root@4[Wolff007]#

I am conneted to the ADSL line because the router light for this computer is on and the light at the ethernet connection at the computer end is also on. Other computers that I have connected to this router and DSL modem work fine. I have two other computers using the same router, one also with Mepis 3.4.3 and the other with Win98SE. The only difference is that these two computers have a different Network card. The problem computer has motherboard based network interface. Since I can"t get the problem computer to connect, perhaps I can install in it the same network card as the two other computers. I believe I have an extra PCI slot in it.

It is a shame that I can't get the problem computer to connect as it is configured. If you have any other suggestions, I am willing to try them. It looks like I am over my head in trying to get this problem computers network interface to work. A reply will be appreciated.

Hermie

If you put e1000 in /etc/modules than it should be loaded, I don't know why lsmod command didn't work for you. (by the way in lsmod the first leter is "L" small case not "1" one -- just to make sure...)

Also you cannot run /etc/modules files since it's a text file not an executable one.

If the router works file than go to Mepis Center and configure the connection for eth0.

--
Post questions on www.mepislovers.org too.
Check out our wiki: www.mepislovers-wiki.org

Adrian TM;

Now that I got lsmod right, I get:

Wolff007@1[~]$ su
Password:
root@1[Wolff007]# lsmod | grep e1000
e1000 105012 0
root@1[Wolff007]#

I still don't understand how to look in /etc/modules.

When I click "start eth0" in Mepis Os Center, I get "eth0: not running and no Ip address shows up under the Status tab.

I get more confused as we go along, because so far nothing has gotten me connected. What about my idea of bypassing the on-board LAN interface with a network card known to work with Mepis 3.4.3 and Win98SE and my router and ADSL modem?

I know your patience is running out and I am frustrated, but any other suggestions you might have will be helpful. I am learning as I go along.

Hermie

I forgot to say if you get "e1000" when you do "lsmod" it means the driver is installed, it looks that your driver is installed, the problem is probably in other part.

You'd probably need to play with these commands:
ifconfig
dhclient

try: ifconfig eth0 up and then dhclient. If dhclient doesn't give you an IP address try to configure it with ifconfig (look in "man ifconfig" for more details, I don't know it very well).

Mepis Config System is supposed to do that in a painless way, I have no idea why is not working for you.

So, in short, you have e1000 driver installed and loaded, you need to configure the Internet settings (with ipconfig and dhclient).

Good luck!

--
Post questions on www.mepislovers.org too.
Check out our wiki: www.mepislovers-wiki.org

Hermie,

Make sure your eth0 interface is configured correctly (DHCP/Static IP) for your router in the eth0 tab under Network Interfaces in Mepis OS Center. This should match the configuration you have on the other Mepis computer. (EDIT: If you're using static IP, the IP address assigned to this interface would be different.) If everything looks good and you still can't connect, try plugging the cable into another port on the router and maybe try using another cable between the router and the computer. "ethtool eth0" will give you some more information about that controller. Check out the man page for ethtool (#ethtool in konqueror) for more information.

Alex

you'll have to adjust this to match your routers (modem) gateway address etc, but for this example, I'll use my setup

First as root in a console, type ifconfig and take note of the addresses (if any) of eth0. You're looking for the inet address.

Here's a line from mine, I'm using a D-link router
inet addr:10.1.1.5 Bcast:10.255.255.255 Mask:255.0.0.0

My computers address is 10.1.1.5, which tells me that my routers gateway address is the first available address in 10.1.1.X range, 10.1.1.1

If your machine returns 192.168.1.4, then your gateway address will probably be 192.168.1.1, though I have seen a few rare cases where the opposite end of the address range is used, 192.168.1.254

If the ifconfig results don't return any line like my example above, move on to the following, but if you do have one, try pinging the gateway address to see if you get a response.

e.g.
root@2[michael]# ping -c4 10.1.1.1
PING 10.1.1.1 (10.1.1.1): 56 data bytes
64 bytes from 10.1.1.1: icmp_seq=0 ttl=255 time=2.9 ms
64 bytes from 10.1.1.1: icmp_seq=1 ttl=255 time=4.0 ms
64 bytes from 10.1.1.1: icmp_seq=2 ttl=255 time=2.7 ms
64 bytes from 10.1.1.1: icmp_seq=3 ttl=255 time=3.6 ms

--- 10.1.1.1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 2.7/3.3/4.0 ms

The above is healthy and the network is up.

No if you had no results from the ifconfig, type

ifconfig eth0 10.1.1.5 inet up
then try the ifconfig and the ping command again.

If you can ping and get a healthy response, your network works, but it will be lost when you reboot and internet access may not yet be possible, even though you have a connection to your router.

Let us know how you get on. I'll be out of touch for the next 2 days, so I hope somebody can carry you on from here, but the answer is in the os centre under network from here if you have a positive response. You may have to set a static address.

m_pav;

In Mepis OS Center I get:

Under STATUS TAB:
eth0: can/t connect stop eth0
eth0: not running start eth0
(no ip given)
Under DNS TAB:
Primary DNS Server 206.13.28.12
Secondary DNS Server 205.152.0.20
Under eth0 TAB:
Ip address 192.168.79.1
Netmask 255.255.255.0
Gateway address 192.168.79.1
Broadcast address 192.168.79.255

When I enter command ifconfig, I get:

root@3[Wolff007]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:15:F2:54:02:4A
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1458 errors:0 dropped:0 overruns:0 frame:0
TX packets:383 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:252657 (246.7 KiB) TX bytes:132518 (129.4 KiB)
Base address:0xd800 Memory:cffe0000-d0000000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:327 errors:0 dropped:0 overruns:0 frame:0
TX packets:327 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:64666 (63.1 KiB) TX bytes:64666 (63.1 KiB)

From your instructions, I don't understand what address to ping.

I compared the Mepis OS center on my working Mepis computer to what I outlined above and the only essential difference is under the STATUS TAB-eth0: gave an ip address (192.168.1.100). I also checked my cable as suggested by Alex. What other steps can I take now? Thanks.

Hermie

Somehow your Mepis box doesn't get an IP address. I don't know where is the problem, maybe somebody else more knowledgeable in the networking fild will response.

You could also try, just for the heck of it to connect Mepis directly to modem (or without the other devices connected) just to see if it gets an IP address when you run dhclient
--
Post questions on www.mepislovers.org too.
Check out our wiki: www.mepislovers-wiki.org

your mepis system is not getting an ip address from the router/modem.

I had this mid last year when my router would not issue an address to a Marvel Gigabit Lan card. My only workaround was to set the card with a static address until I got a better router/modem.

In your case, your router/modem will probably have a gateway address of 192.168.1.1, but you can easily discover exactly what it is by using the other computer and observing what the gateway address is underneath the ip address and netmask.

It should show something like this
ip address = 192.168.1.100
Netmask = 255.255.255.0 (or something like that)
Gateway = 192.168.1.1

What you really need to know is the gateway address here, so take note of whatever yours is as you'll need it for pinging.

It would appear your router is set to start all ip addresses from 192.168.1.100 and it will probably have an end address of 192.168.1.254, which means that a maximum of 154 individual computers can use this router, whereas normally, the range starts from 192.168.1.2 and finishes at 192.168.1.254 Are you getting the picture now? I hope so.

OK, now type the following on the "broken" machine as root to set your cards ip address for your current session

ifconfig eth0 192.168.1.101 inet up

Then try ifconfig by itself. It should return the same address in the output.

Next try the ping command
ping -c4 (your routers gateway address)

If you get 4 good responses, your network is up. If not, change the last number to 102 in the ifconfig command above and try again. If still no good, I'd try just one more time with 103 or a higher number, then if no good, get another router or check your cables, but I assume they're good becasue other computers work on the same cable.

Providing all is well, set the card to have a static address using the os centre and use the parameters (ip, netmask, gateway) that worked when you successfully pinged.

Good luck

Great answers by m_pav. I myself have a situation where I can't make wired connections to any of the 4 ports of my router from any computer currently, only wireless. I also have on-board lan on a new board and to check it I finally connected it directly to the DSL modem, as Adrian was suggesting here, which worked fine. My current diagnosis of my situation is that the wired functionality on the router (D-link DI-614+) is dead. But in Hermie's case he has other computers that are connecting fine through wires. There isn't much chance the cable is the problem but I assume these computers may be connecting through different cables.

That might offer a solution as well, but m_pav's solution of using static IP settings might be worth checking out first. On my primary box I'm currently bypassing the on-board LAN with a wireless PCI card.

m-pav;

Lo and behold! I started my computer this am after an apparent overnight power failure and I am connected via DSL. There are only three things that I have done differently since I last tried to connect.
(1) restarted my computer, as noted: (2) unpluged and repluged the Cat cable from my router to the computer before the restart (3) in Mepis OS Center, before the restart, in networking under the STATUS Tab: eth0: I set it to "stop eth0". I had always before had it set to "start eth0". Previously I got the note "can't connect" or "not running".

I don't know which of the three did the trick since I had done (1) and manipulated (3) multiple times. In (2) I had "jiggled" the Cat cable at the router and computer end, but had never physically unplugged and replugged them. Do you think physically unplugging and plugging corrected things. I might cut my throat if the consensus is that a simple physical problem was my nemesis. Thanks to all for your persistent and kind support. You are some outstanding people.

Hermie

Computers are a wonder and I've had similar experiences before with things not working....and then hey presto all is well.

Glad you got it sorted but I guess you might never know.....

Roll on automated linux installations......

Online Backup, Virtual Switchboards & Virtual Call Centres

Howdy,

I have an HP Pavilion dv1000. I have now installed the newest MEPIS 3.4-3 and I am unable to connect to my wireless network anywhere (home, work, hotel, etc...). However, I have the machine dual booting. So I CAN boot up into windows and connect to all of the above mentioned wireless networks. However, when I boot into MEPIS Linux I cannot. So I know the problem is not the wireless networks or routers. It IS something to do with Linux.

I receive the message "no DHCPOFFERS received" and the next line is something about the datbase sleeping.

In MEPIS OS Center the wlan0 says can't connect.

In KwifiManager - the laptop sees the proper wireless networks available but I just can't connect to them.

I have verified that I have my e1000 driver installed and loaded properly (as directed in this forum thread earlier).

When I do try to use dhclient to get an ip address it just keeps doing

DHCPDISCOVER 255.255.255.255 port 67 interval 5
DHCPDISCOVER 255.255.255.255 port 67 interval 5
DHCPDISCOVER 255.255.255.255 port 67 interval 6
DHCPDISCOVER 255.255.255.255 port 67 interval 5
DHCPDISCOVER 255.255.255.255 port 67 interval 10
DHCPDISCOVER 255.255.255.255 port 67 interval 11

no DHCPOFFERS received
No working leases in persistent database - sleeping.

Does anyone have any ideas as to how I can get this version of MEPIS 3.4-3 working on wlan0?

Thanks,

Cowboy

I decided to go with the new MEPIS 6.0 rc2. Now my wireless won't even turn on. MEPIS 3.3 worked fine with my HP Pavilion dv1000 but now it is not working at all. So I am assuming something is missing.

Can anyone help?

Cowboy

I've found that when KWiFiManager can see the networks but can't connect, it's usually because the eth0 connection is still trying to run. When that is the problem, the solution is to open the Mepis OS Center, stop eth0, then stop and start wlan0 again and Mepis will connect.
To keep it from happening every boot, go to the eth0 tab and uncheck the start on boot box and then apply.