pemasu wrote:Upup Precise-5.3.3.3 has been uploaded.
- updated broadcom wl - b43 - b43legacy detection
Broadcom/Dell wireless adapter not detected by Network Wizard on Dell D430 (works fine in Racy 5.3 and latest slacko beta)
Hi zekebaby
Is there any reason why you do not use Frisbee? Precise sort of comes with Frisbee "pre-selected" - you just right click on the wifi aerial in the tray to connect. Could you try it?
What mode are you running Precise? If frugal, have you created a savefile and rebooted a couple of times?
Is wlan0 being created? Do you know which driver is being used? (NetWiz will tell you this)? What encryption scheme is being used?
Could you post the output of lsproc and dmesg? Does dmesg show any errors?
Or pm me the output of pmodemdiag (ignore any error messages it might throw).
Cheers
peebee
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
With Python people are very much on their own. I try to avoid Python like plague. I did have Python apps in Snow Puppy....since then I have tried to avoid them as much as I can...
I did need pygtk for my experiments with wireless apple airport dongle for wireless music streaming to my stereos...in Lucid 5.1 time.
I compiled it and...
I got it working but I also decided not to like Python at all...Python seems to conflict how I hope apps to work. Sorry.
Installwatch is in checkinstall deb. Activate ubuntu-precise-universe repo and install it. I have added it to the distro pkgs specs...
zekebaby wrote:Broadcom/Dell wireless adapter not detected by Network Wizard on Dell D430 (works fine in Racy 5.3 and latest slacko beta)
The "updated broadcom detection" may require a second boot-up to have a device be detected by the b43 (open-source) driver. The first boot uses the proprietary (wl) driver if it claims to support a particular device. But sometimes it lies! In that case, an error message is detected and changes are made so that the next boot-up will use b43. So, before concluding that a broadcom wifi device is not detected, try a reboot. If that still fails to detect, then we have a problem to work.
Richard
Pemasu,
Could You please explain why the last image is 30 MB smaller then the previous once's. Is it something not included in the latest image. I did not notice ext4 saving option for the save file. Just I am curious and want only confirmation everything is right. Also to install bleachbit probably I just need pygtk not whole phyton, can You also confirm that. Ubuntu Precise has add on tool called ubuntu tweak, that probably can eliminate bleachbit and is also created specifically for Ubuntu, this package includes distro cleanup and works well on Ubuntu, can it be adopted to puppy. I've got a filling that previous version, I mean 5.3.3.2 worked better than the last one. It works kind of slow.
The smaller iso size has been explained in release statement. I used xz compression instead of default gzip. It makes the sfs file smaller. I used the most efficient method for it also...
About ext4 savefile. I havent made savefile yet...so I dont know if the implementation works. And I cant test it now....I have started my other projects already....and I have several scientific documents open and under work. Probably will be couple of days....
I will post what I know when I can....
I cant contribute much now....but I try to give feedback in the form which is possible for me....
About bleachit...and ubuntu tweak. I know nothing about them. Yet....
zekebaby wrote:Broadcom/Dell wireless adapter not detected by Network Wizard on Dell D430 (works fine in Racy 5.3 and latest slacko beta)
The "updated broadcom detection" may require a second boot-up to have a device be detected by the b43 (open-source) driver. The first boot uses the proprietary (wl) driver if it claims to support a particular device. But sometimes it lies! In that case, an error message is detected and changes are made so that the next boot-up will use b43. So, before concluding that a broadcom wifi device is not detected, try a reboot. If that still fails to detect, then we have a problem to work.
Richard
Hi Richard
I think we do have a problem as:
no wlan0 is created on initial boot - neither by wl or b43
if wl is blacklisted then b43 does load - I suggest this is the short term fix for people to try
if b43 is blacklisted then wl does not create wlan0 - but dmesg does not show errors and modprobe wl does not give any errors
if I load the pet I sent to pemasu into Precise 5.3.3.3 then wl does work as expected.
I suggest the best course of action is for me to send you a PM with pmodemdiag info so hopefully you can see what has gone wrong in building the pet into the iso.
Cheers
peebee
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Re. ext4 save file on shutdown. There was no option to create an ext4 save file when shutting down the two desktops that I tried Precise on. Hopefully Barry's implementation in Woof will work. In the meantime, I used shinobar's pupsaveconfig-2.1.2 which is excellent.
My oldest computer with an intel P4 processor would not shutdown at all, it hung at the shutdown message so I had to manually shut power down. My other desktop with an intel i7 processor shuts down fine.
It's still looking good.
Cheers,
Jim
Last edited by Jim1911 on Sat 28 Apr 2012, 18:13, edited 1 time in total.
pemasu wrote:Or...I did put in MODULESCONFIG the preferences in wrong order, I put it ssb:wl...maybe it should have been wl:ssb ?
pemasu,
The preference is correct. However, the association between the wl module and its "firmware" is omitted from /etc/modules/firmware.dep.3.3.2-upup. It needs the entry, "wl:wl.ko". The attached fix package inserts it just before the entry, "zd1201_firmware:zd1201.ko". It contains only the pinstall-script command: