Pwireless still not connecting to my wlan... It find my wpa wlan but after press connect, nothing happens. Can some one share a wpa_config file?

But then again... savefile also don't work... during boot, after found savefile gives kernel panic..._________________T_Hobbit
Rebuilding old DOS Machine for Wing Commander Privateer and Puppy Old spare parts to give away - anyone interested

Up and running with wifi now. Had to edit the sfs though and add b43 firmware, and a script to get it all running - pwireless2 is not showing anything for me. I cheated and put an already configured wpa_supplicant.conf into etc/.

How do you "add b43 firmware"? please. And any chance of posting your wpa_supplicant? I'm still struggling. cheers.

But then again... savefile also don't work... during boot, after found savefile gives kernel panic...

Is your save file in a usb?
If not in usb, in which disk and partition is it at?

On an USB. Inside archpup folder. FAT filesystem.
Installed thru FlashPup install process from Slacko.
I tryed to move savepup to the USB root - no go.
I erased savepup and it boots fine... but still no wifi connection.

Do I need to have devx and kernel sfs on the USB stick?
Make no sense since sfs are only installed on boot after save file is make..._________________T_Hobbit
Rebuilding old DOS Machine for Wing Commander Privateer and Puppy Old spare parts to give away - anyone interested Last edited by T_Hobbit on Sat 08 Dec 2012, 08:21; edited 1 time in total

Up and running with wifi now. Had to edit the sfs though and add b43 firmware, and a script to get it all running - pwireless2 is not showing anything for me. I cheated and put an already configured wpa_supplicant.conf into etc/.

How do you "add b43 firmware"? please. And any chance of posting your wpa_supplicant? I'm still struggling. cheers.

i copied and pasted /lib/firmware from out of the saluki sfs and added 'modprobe b43 &' to the top of /root/.xinitrc

i still couldn't get pwireless2 working after that so installed wicd using pacman. it took a nice meat of mbs installing it but i don't mind giving the space, for the stability.

Seems so... Posting from a running Archpup installed on an internal HD at my father in law desktop computer with savefile OK.
Checked the size of both savefiles: on this desktop it has 262.1 MB, on my USB only 220MB.
Maybe the savefile script didn't finish saving all savefile to the USB? Too slow compared to an HD?

Just need to find out how to solve the wifi problem... maybe it's related?_________________T_Hobbit
Rebuilding old DOS Machine for Wing Commander Privateer and Puppy Old spare parts to give away - anyone interested

I just run some tests with booting from usb device. USB is formated as FAT32 and I used
unetbootin in windows to create bootable Live USB. It works if you don't have savefile
or if savefile is on hard disk partition. But if you create savefile on USB after reboot it gives
kernel panic !? I don't know why would empty savefile make that problem.

the keymaps seem don't to be from puppy and we have now different results and in this details, they are not better, for me in all cases: I write with the us_intl from Puppy and have a great choice of char including some chars for slave and north European languages (and all chars for west European languages completely correct).

in ArchPup, it is different, the same map code produces that what in Debian or Slax etc. would be named us_accentos, a very reduced choice of chars only for south European languages...

b/ Browser comportment

I did try divers browsers and no one will proceed to connect with

localhost:631 (tragic... Cups!)
localhost:8000 (only didiwiki but it would be better to be able!)

what experience did have other users with this important detail concerning directly the ability or not to print in ArchPup?

Use a Puppy that your wifi is working on.
Look in lib/firmware and copy the folder corresponding to your driver (in my case 'b43')
Copy it to lib/firmware in Archpup - if 'firmware' doesn't exist, then create it.
In Archpup you will also probably have to create a file called 'firmware.dep.3.8.6' in etc/modules/
This needs to refer to your module, and in my case the line needed is just 'b43:b43.ko'
(I can't profess to understand this fully, I've arrived at it by trial and error, mainly the latter...)

wpa_supplicant.conf is specific to your own connection (contains your SSID and password etc) so again, copy a working one from somewhere else. It is in etc/.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum