@Marv - thanks - sorry I've only just seen your edits - there have been changes to .xinitrc which I haven't tracked...doh! Attached there is a replacement .xinitrc with dummy .gz rename to .xinitrc before copying into /root - I have reuploaded the 14.01 pre-release with this change. Please report if it solves your problem.

@Marv - thanks - sorry I've only just seen your edits - there have been changes to .xinitrc which I haven't tracked...doh! Attached there is a replacement .xinitrc with dummy .gz rename to .xinitrc before copying into /root - I have reuploaded the 14.01 pre-release with this change. Please report if it solves your problem.

Thanks, I have the download. At first blush, it doesn't seem to fix. Stripped my intel directory out of /lib/firmware, substituted the new .xinitrc, reboot and get the same dmesg re not finding firmware. Pretty rushed this AM, will take a better look at it this afternoon._________________Pups currently in kennel X-slacko 4.2 and X-tahr 2.0 for my users; LxPupSc, LxPupXenial and X-slacko 4.2 for me. All good pups indeed.

@Marv - thanks - sorry I've only just seen your edits - there have been changes to .xinitrc which I haven't tracked...doh! Attached there is a replacement .xinitrc with dummy .gz rename to .xinitrc before copying into /root - I have reuploaded the 14.01 pre-release with this change. Please report if it solves your problem.

Thanks, I have the download. At first blush, it doesn't seem to fix. Stripped my intel directory out of /lib/firmware, substituted the new .xinitrc, reboot and get the same dmesg re not finding firmware. Pretty rushed this AM, will take a better look at it this afternoon.

Hi Marv

I did some tests with my b43 wifi - had to first blacklist the wl driver which is chosen first for my b43 variant but once I'd done that and rebooted the firmware mechanism had worked correctly and the firmware was copied to /lib/firmware/b43 and the b43 driver was working correctly.

The only difference I note between b43 and iwlwifi is the presence of /etc/modprobe.d/b43.conf in /lib/modules/all-firmware/b43 which has a delay in it (part of managing the wl/b43 race to claim the chip).

So I think the basic firmware mechanism is working correctly but there may be some timing differences between basic Slacko and LxPup on your processor with your wifi chip which are stopping it working? If it persists we may need to seek assistance from an expert like Rerwin or Technosaurus to suggest a solution....

or you can do a manual copy of the firmware from /lib/modules/all-firmware/iwlwifi/lib/firmware to /lib/firmware/iwlwifi

So I think the basic firmware mechanism is working correctly but there may be some timing differences between basic Slacko and LxPup on your processor with your wifi chip which are stopping it working? If it persists we may need to seek assistance from an expert like Rerwin or Technosaurus to suggest a solution....

or you can do a manual copy of the firmware from /lib/modules/all-firmware/iwlwifi/lib/firmware to /lib/firmware/iwlwifi

Cheers
PeeBee

Thanks, the manual copy scheme has been working for me. All the intel firmware in a directory named intel in /lib/firmware. I'll continue to nibble on this bit as I have time. Everything else in 14.01 is working fine for me at this point.

Edit: SOLVED I looked in dmesg for wl and saw an error message for it 'tainting the kernel'. NOTHING broadcom on this box. Blacklisted wl and the correct iwlwifi firmware is found and loaded from all-firmware and wireless is fine. I'll check the ip2200 laptop next but so far so good._________________Pups currently in kennel X-slacko 4.2 and X-tahr 2.0 for my users; LxPupSc, LxPupXenial and X-slacko 4.2 for me. All good pups indeed.

Confirmed. Exact same behavior on intel ipw2200 wireless. Blacklist wl, reboot, ipw2200 wireless active, networks seen and connection (using frisbee) without a hitch. Let me know exactly what you would like in terms of diagnostics and I can run them on either machine._________________Pups currently in kennel X-slacko 4.2 and X-tahr 2.0 for my users; LxPupSc, LxPupXenial and X-slacko 4.2 for me. All good pups indeed.

Includes fix by rerwin (many thanks) to solve Marv's problem with the new 6.30.223.141 wl driver interfering with iwlwifi / iwp2000

Looks good from here. Just to double check, downloaded the iso above, pristine frugal boot on my iwlwifi laptop, iwlwifi firmware loaded, wlan0 associated, connected correctly. Then added in my customizations so I'm up and running. Noted that the package manager is now double click internally.

Thanks _________________Pups currently in kennel X-slacko 4.2 and X-tahr 2.0 for my users; LxPupSc, LxPupXenial and X-slacko 4.2 for me. All good pups indeed.

First tried a fresh boot into RAM. All went nice, tried a few of the apps... nice to see the apps I tried are the latest updates!

After running for about an hour using a Frisbee setup for WiFi I shutdown without making a savefile.

Booted up again... WiFi config'd itself... some more testing on the Internet at various places, youtube, some short video clips etc., all seemed fine. Shut down again not creating a savefile.

Booted up again only this time I went for the option to UPGRADE LxPup-13.10.1 Upgrade went fine with no issues... WiFi auto connected. Shutdown again and rebooted.

Everything went well and WiFi auto connected again but... after about 20-minutes on the Internet, WiFi 'DROPPED'. Plugged in the modem cable and eth0 auto connected and took over quickly. But... after about 10-minutes on the Internet etho 'DROPPED'. After trying many various configs, eth0 and wlan0 could NOT be started by anything available in LxPup, its like your whole Ethernet system went dead.

This is happening in the latest NEW puppys of, Slacko, SuperLupu, and various Precise's builds. The 'ONLY' puppy (tested several weeks so far) that HOLDS WiFi is 'the latest 'WHEEZY' build... it has never dropped on me!

My take is that most of the newer puppy builds must be using the SAME Frisbee module (with slight variations) but... I do believe there is a major problem with Frisbee not holding up or reconfiguring itself after a drop. I've used other Linux distro's where WiFi would drop but it would clear itself and auto restart again without and user intervention, I doubt they were using Frisbee.

Frisbee has come a long long ways recently with easy setup but I believe it has some more 'fixing' in order or, maybe there is a better WiFi setup available for puppy???

Thanks for the feedback - LxPup-13.11 is a derivative of Slacko5.6 so all findings should also apply to Slacko5.6 (especially your compliment about the latest applications).

I use Frisbee all the time on both my laptop and desktop and never have the problems you describe (but I don't have ethernet connections, only wifi on both) - what I would suggest is that when your problem manifests itself you should run pdiag in a terminal and then send the file produced by pm to rerwin - Richard has done all the recent work on Frisbee and is a whiz at analyzing the pdiag output. Your problems may be unique to the particular combination of chips in your pc.....

It's worth pursuing your Frisbee problem if you are able - best to post any further results/queries on the Frisbee thread.

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