.:Slackel - Hellenic Linux Distribution::.

djemos wrote:I think i found what is the problem. Stop the standard single network wifi startup script ( wireless) run

Code: Select all

sudo servicesetup

and hit spacebar key to uncheck wireless ( can do the same from menus- > system -> system services)
Then from wicd do a refresh and click on wired network to connect

Code: Select all

sudo service restart inet1

or reboot

Maybe I should mention that the motherboard came with 2 RealTek ethernet connections but I added added a third (by installing an internal card) from Intel.

So if the command inet1 refers to the connection, on Sparky the active connection is eth2 (eth0 and eth1 are inactive).

(I'm going to wait until you confirm that detail before attempting it).

As I said, the Slackel live session finds the active connection automatically (and I think Salix did too but I don't remember for sure. There were other problems as I recall and the Slackel installation application is much better also).

Sparky Multimedia uses Openbox although it's fundamentally LXDE (to which I added some Xfce applications).

or
from wicd click on preferences and where is eth0 change it to eth2

OK, I'll try that. Thanks for the help, djemos.

Following your instructions I was able to configure Slackel to connect to the Internet via eth2 using wicd (which I had make full screen in order to see to preferences menu). However: Although the correct IP address was shown, Midori continued to tell me that I was not connected to the internet and failed to navigate to any website. (Which was disappointing).

On initiating the live session via the DVD I noticed that Slackel loaded the correct driver and consequently navigated just fine, meaning that I can still use Slackel as a portable live system with persistence from a usb flash drive, for now.

Be sure that wicd is not connected with any other connection like wnal0, eth1 etc If so click on disconnect and click on connect to eth2 to connect.
if you mean that after installation the correct driver is not loaded?
Then you can load the driver manually.
sudo modprobe dervider_name
type lsmod to see if driver is loaded.

also can put in /etc/rc.d/rc.local file at the end
modprobe driver_name to load on every boot
what is the driver name shown in lsmod

what is the output of ifconfig ?
and cat /etc/resolv.conf ?
Is there a nameserver line ? e.g. nameserver 192.168.1.254 as in mine system.

can also use sudo dhcpcd eth2 and write here the output

Thanks for the constructive response. I'll try to log back into Slackel over the weekend, to try that.