Network manager doesn't work correctly after testing ceni

[uncle mark]

I'm not trying to be difficult--I really am struggling to understand.

This is the first beta of a community project. It's not complete, is rough, has bugs, and will be replaced with more refined versions several times. You should not expect it to work all that well out of the box. If you've been reading closely, you'll see that even the gurus here are having trouble beating it into submission. Me, I finally got it to boot to the live environment, but I've not installed and probably won't for at least another version or two when things start to settle down. Perhaps you might consider backing off and waiting a bit as well.

[lucky9]

Just enter (as root) apt-get update (hit the Enter key)
then enter apt-get install wicd (hit the Enter key)

Getting the right stuff is APT's job. Or you can use aptitude. Just stay with what you decide. Personally I think Synaptic is all that's needed.

[anticapitalista]

I did a little research and it looks like you need the broadcom-sta driver (aka the wl module)
go to http://teharris.net/mepiscr/xfce/pool/m ... adcom-sta/
and download the broadcom-sta-dkms _6.30.223.141-1_all.deb file

Boot into MX-14 and click on that file to install the driver. Reboot and the wireless should be recognized.

Does this conflict with any existing broadcom firmware already included in MX-14? If not, then we should include it in the iso, right?

[Stevo]

OK.

There are 6 WiCd entries listed.
The first one appears to be the one; however, how do I know?

Jerry

Edit: what about the one listed as WiCd-kde--looks like a kde version to me

2nd edit: I'm not trying to be difficult--I really am struggling to understand.

In most cases, the package that matches the program name the closest is what you want; so in this case, "wicd".
The same holds for something like vlc or gimp, where you'll see many related packages, but you want just "vlc" or "gimp"

Wicd will install the gtk frontend, which will run on any desktop. If you happen to be running KDE, then wicd-kde is a special frontend that only runs on KDE--you can have that plus the regular wicd on KDE, though I can't imagine why.

[timkb4cq]

Yes we should, but you couldn't get the install to finish in your chroot when you tried during the alpha 2 cycle. The -dkms package does an update-initramfs that I think was the issue.

[anticapitalista]

Yes we should, but you couldn't get the install to finish in your chroot when you tried during the alpha 2 cycle. The -dkms package does an update-initramfs that I think was the issue.

Yes, same again. It looks for fd (floppy drive?) and then complains.

Code: Select all

apt-get install broadcom-sta-dkms 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  broadcom-sta-dkms
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 3,394 kB of archives.
After this operation, 10.1 MB of additional disk space will be used.
Get:1 http://main.mepis-deb.org/mepiscr/xfce/ xfce-4.10/main broadcom-sta-dkms all 6.30.223.141-1 [3,394 kB]
Fetched 3,394 kB in 11s (301 kB/s)                                                                                                                            
dpkg-preconfigure: unable to re-open stdin: No such file or directory
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously unselected package broadcom-sta-dkms.
(Reading database ... 94607 files and directories currently installed.)
Unpacking broadcom-sta-dkms (from .../broadcom-sta-dkms_6.30.223.141-1_all.deb) ...
Can not write log, openpty() failed (/dev/pts not mounted?)
Setting up broadcom-sta-dkms (6.30.223.141-1) ...
Removing old broadcom-sta-6.30.223.141 DKMS files...
/usr/sbin/dkms: line 179: /dev/fd/62: No such file or directory

------------------------------
Deleting module version: 6.30.223.141
completely from the DKMS tree.
------------------------------
Done.
Loading new broadcom-sta-6.30.223.141 DKMS files...
First Installation: checking all kernels...
It is likely that 3.12.6-antix.1-amd64-smp belongs to a chroot's host
/usr/sbin/dkms: line 1868: /dev/fd/62: No such file or directory
/usr/sbin/dkms: line 1799: /dev/fd/62: No such file or directory
dpkg: error processing broadcom-sta-dkms (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 broadcom-sta-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

[muskt]

In most cases, the package that matches the program name the closest is what you want; so in this case, "wicd".
The same holds for something like vlc or gimp, where you'll see many related packages, but you want just "vlc" or "gimp"

Wicd will install the gtk frontend, which will run on any desktop. If you happen to be running KDE, then wicd-kde is a special frontend that only runs on KDE--you can have that plus the regular wicd on KDE, though I can't imagine why.

Thanks Stevo.

Each little tidbit helps.

Jerry in Anchorage

[kmathern]

Yes we should, but you couldn't get the install to finish in your chroot when you tried during the alpha 2 cycle. The -dkms package does an update-initramfs that I think was the issue.

Yes, same again. It looks for fd (floppy drive?) and then complains.

Code: Select all

...Setting up broadcom-sta-dkms (6.30.223.141-1) ...
Removing old broadcom-sta-6.30.223.141 DKMS files...
/usr/sbin/dkms: line 179: /dev/fd/62: No such file or directory

------------------------------
Deleting module version: 6.30.223.141
completely from the DKMS tree.
------------------------------
Done.
Loading new broadcom-sta-6.30.223.141 DKMS files...
First Installation: checking all kernels...
It is likely that 3.12.6-antix.1-amd64-smp belongs to a chroot's host
/usr/sbin/dkms: line 1868: /dev/fd/62: No such file or directory
/usr/sbin/dkms: line 1799: /dev/fd/62: No such file or directory
dpkg: error processing broadcom-sta-dkms (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 broadcom-sta-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

I think the "fd" in /dev/fd/62 stands for 'file descriptor', I don't know what you need to do to get it to work.

[anticapitalista]

ln -s /proc/self/fd /dev/fd seems to have fixed it.

http://www.ducea.com/2009/02/18/linux-t ... directory/

[anticapitalista]

Including broadcom-sta-dkms adds c17MB

Ah wait, maybe not.

No, it takes the iso to 703MB.

Good.