Porteus/Arch aka Sensei (Porteus w/pacman package manager)

[deadsocket]

Sorry, if I do not follow you. On my side, I have the impression that you do not follow me. Please give the requested information.
What is the result of:

You can also pick it up thru porteus panel menu > internet > wicd. You can also pick it up thru porteus panel menu > internet > wicd. Left click on it you should see your wifi network.

? Do you see your network?

There is no icon in the panel. Going in to the application menu > internet > wicd, does nothing at all.

And if you do not see your network, what is the output of:

give us the output in terminal mode of iwconfig and of rfkill list commands.

Example of output:

Code: Select all

root@porteus:~# iwconfig
wlan0     IEEE 802.11bgn  ESSID:"Cherrier"  
          Mode:Managed  Frequency:2.462 GHz  Access Point: E0:91:F5:A0:AC:B1   
          Bit Rate=48 Mb/s   Tx-Power=16 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=30/70  Signal level=-80 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:221   Missed beacon:0

lo        no wireless extensions.

eth0      no wireless extensions.

root@porteus:~# rfkill list
...
root@porteus:~#

I can tell you that lsmod tells me the 'wl' module is loaded (which is what I need). I'll report back when I do iwconfig and rfkill, but I don't think I can copy all the output on a piece of paper.

[francois]

Ok I see. In cli mode try wicd two times, if there is no results its really not there. Then two things could be done.
1) waiting for stiffling. He is the one who provides the iso file for porteus/arch, he should provide some solution.
2) try to sort it out with the following threads with command line options:
http://old.slax.org/forum.php?action=vi ... ntID=16234
http://old.slax.org/forum.php?action=vi ... ntID=21156

Essentially you have to know what is the identity of your wifi: wlan0 or other. This is what you get with iwconfig command alone as I gave you in the previous post. If there is none, it might be not active. You have to set your router to wep encryption, as wpa will not work, with the following commands. Then try:

Code: Select all

root@porteus:~# iwlist scanning
wlan0     Scan completed :
 ...
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Quality=70/70  Signal level=-31 dBm  
                    Encryption key:on
                    ESSID:"p4rc"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=000000a6321e419b
                    Extra: Last beacon: 2899ms ago
                    IE: Unknown: 000470347263
                    IE: Unknown: 010882840B162430486C
                    IE: Unknown: 03010B
                    IE: Unknown: 2A0100
                    IE: Unknown: 2F0100
                    IE: IEEE 802.11i/WEP
                  ...

          Cell 03 - Address: 84:C9:B2:D3:67:C5

Then pass the following commands with your exact parameters, with mine we get:
root@porteus:~# iwconfig wlan0 mode managed channel 11 key open 6BEXXXXXXXXXXE63XXXXX9B45 essid p4rc
root@porteus:~# iwconfig wlan0 ap any
root@porteus:~# ifconfig wlan0 up
root@porteus:~# dhcpcd wlan0

Then with your wifi installed you might install the missing wifi manager:

Code: Select all

root@porteus:~# pacman -S wicd
warning: wicd-1.7.2.4-7 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts..
...

Here in my case, it says it is already installed.

[stifiling]

thanks for the assistance francois...definitely appreciated.

deadsocket,

you say there is no wicd icon in the notification area? try running the command

Code: Select all

wicd-gtk

and see if there's an error of some sort.

you say your wireless card uses the driver wl? try this:

Code: Select all

iwconfig

and see if you see either wlan0 or eth1, if not try this:

Code: Select all

rmmod wl
rmmod b43
rmmod ssb
modprobe wl

and see if you now see wlan0 or eth1....

[ncmprhnsbl]

we be affected by this?
http://www.murga-linux.com/puppy/viewto ... 144#720144
https://bbs.archlinux.org/viewtopic.php ... 8#p1313328

[stifiling]

we be affected by this?
http://www.murga-linux.com/puppy/viewto ... 144#720144
https://bbs.archlinux.org/viewtopic.php ... 8#p1313328

yes it has...and this has put a crater sized hole in my way of computing. i'm wondering if it'll ever be as good again. not only could u use it to freeze arch linux's rolling distro....but u could also downgrade packages to older, better liked versions. xorg-server for instance. u need v1.10 or less for the non-free nvidia 96xx driver to work. downgrading to that version of xorg-server won't be as easy now.

Fingers crossed that an equivalent solution is put together.

[francois]

At least they give some kind of fix on puppy linux.

[ncmprhnsbl]

it seems the Chinese Arch community is providing a replacement,(for Arch Rollback Machine)
not sure it will go far enough back in time for stifiling......
but i'm fairly sure that syncing with the official (rolling) repo would lead to breakage?

[ncmprhnsbl]

successfully installed kde from http://repo-arm-download.archlinuxcn.org which equals the main repo at this stage

here is another http://seblu.net/a/arm/
it has similar structure to old arm, start date 2013.08.31
edit /etc/pacman.d/mirrorlist

Code: Select all

# WARNING! Do not edit this file if you want stable system!
#Server = http://arm.konnichi.com/2013/06/26/$repo/os/$arch
Server = http://seblu.net/a/arm/2013/09/05/$repo/os/$arch

pick your date and stick with it..
seems to be a fair bit of interest in this, which may result in more repos/mirrors and possibly the older archives..

[stifiling]

successfully installed kde from http://repo-arm-download.archlinuxcn.org which equals the main repo at this stage

here is another http://seblu.net/a/arm/
it has similar structure to old arm, start date 2013.08.31
edit /etc/pacman.d/mirrorlist

Code: Select all

# WARNING! Do not edit this file if you want stable system!
#Server = http://arm.konnichi.com/2013/06/26/$repo/os/$arch
Server = http://seblu.net/a/arm/2013/09/05/$repo/os/$arch

pick your date and stick with it..
seems to be a fair bit of interest in this, which may result in more repos/mirrors and possibly the older archives..

Thanks for the heads up on that. definitely a nice head start as a replacement ARM. i loved the capability install the even older packages, though i rarely did...knowing that i could when 'needed' was a great sense of comfort. hopefully those will be added as well. like i said before...downgrading xorg-server, depending on the situation/machine, is sometimes necessary.

[ViktorNova]

Wow! I'm shocked to have just found out about this, as I have been working on something similar for the last few months, although with a different spin.

I've been using the Arch tools abs and aur.sh (unofficial AUR bash script that is like 3 lines long and perfect) to automatically download and compile Arch/AUR packages on Porteus, only my approach has been to make them true Porteus-compatible packages with no Arch dependencies, except for when a dependency doesn't exist in Porteus/Slackware/Slacky/Salix/Alien/Slackbuilds (or when the slackbuild pisses me off or is old)

I've been doing it using -d, so dependencies are not taken into account, but it usually tells you if there's a missing dependency during the config, and from there it's easy enough to go get it and then try again. This make a slight bit more work, but is still 1000% faster and more awesome than attempting to use Slackbuilds, and I've had very few things not work. I've had to edit a few PKGBUILDs here and there, but it's been rad. Once it's slightly less hacky I'll release it! this could be kinda huge for Porteus

I was wondering - do you have any precious tidbits of wisdom to aid me in this quest, having gone this far with it in your direction?

How different and similar is this from what you're doing?

I've got a flow going, but it's kinda janky, I haven't figured out a way yet to automatically create .xzm packages at the end yet, so been doing it by hand. The work with the package manager gui you're using is especially intriguing!

Can't wait to check out your distro, I know what I'm doing at work tomorrow 8)

[ViktorNova]

Also I'm a huge fan of not reinventing the wheel, is there an easy way to use your tools to create new packages from Arch sources that are still 100% Porteus compatible? (providing of course that any non-Porteus dependency would be included along with said new package)

FYI I'm working towards a pre release of a multimedia performance touch appliance built on Porteus (audio/MIDI looping/sequencing, DMX, OSC, etc), which is how I got here, so I wanna keep the more stable Porteus base

[francois]

Hello, VicktorNova:

I've been using the Arch tools abs and aur.sh (unofficial AUR bash script that is like 3 lines long and perfect) to automatically download and compile Arch/AUR packages on Porteus, only my approach has been to make them true Porteus-compatible packages with no Arch dependencies, except for when a dependency doesn't exist in Porteus/Slackware/Slacky/Salix/Alien/Slackbuilds (or when the slackbuild pisses me off or is old)

It seems that stiffling has been working the other way around, that is he used porteus as a base to a 100% compatible archlinus system, whereas you have been going some other way around, that is using some archlinux packages and adapting them to porteus, to be solved by porteus dependencies. Thus opening a incommensurable number of package to be available on porteus.

Quoting stiffling:

francois wrote:

From what I understand, porteus-arch could function both thru porteus modules or packages provided by pacman. Isn't it or I am wrong?

Concerning package management thru pacman, is the pacman -S --force strategy a robust one or could it break the system?

No, the original porteus .xzm modules created by the community, are not compatible with this porteus-arch. if you happen to try one and it works, you just happened to get lucky that time. this is another reason why 'pacman -S --force' is safe. if your package won't install it's because one of the slackware files from the original porteus is already present. so technically, it's more broke before you use the '--force' than it is afterwards. using the '--force' is helping to completely fix the system by overwriting the previous slackware files, wit the correct arch linux ones.

Keep us informed of your research results. If you get it straight, this might be a great addition to porteus and maybe to PPM

[ViktorNova]

Will do! =D I hope to get it cleaned up slightly and throw it up on Github within the next week or so

[francois]

Arch tools abs and aur.sh (unofficial AUR bash script that is like 3 lines long and perfect) to automatically download and compile Arch/AUR packages on Porteus, only my approach has been to make them true Porteus-compatible packages with no Arch dependencies, except for when a dependency doesn't exist in Porteus/Slackware/Slacky/Salix/Alien/Slackbuilds (or when the slackbuild pisses me off or is old)

This strategy of yours would really be a winner. I do not find sbo that easy to use. Src2pkg might help building from source, but having access to archlinux community pastures would be really great. In addition, you might surprise brokenman. 8)

As soon as you can open a thread on your method. I imagine that a few of us on the forum would like to test your strategy.

[stifiling]

Thanks for giving him that accurate information francois. i wouldn't be of much help presently with that goal, as it is a totally different direction from this.

I did piece together another version with Porteus 2.1 32-bit as the base. Pretty much the same as the first but with the newer kernel and the arch packages updated as of 12/05. Link is in first post...