Dpup Wheezy. Woof-CE built debian wheezy 7.2 packages used

Message

pemasu · #586 Post by **pemasu** » Mon 09 Dec 2013, 18:00

Mavrothal. I like the idea. I have even had manually created Dpup Exprimo which had a lot firmwares translocated to the /lib/firmware. It was at that b43 firmware loading error time. Before Barry Kauler fixed the problem in some system script.

Is is good intention. Just dont put semi-working stuff to the master branch before someone has tested the testing branch or firmware branch version first.

Otherwise...well....read previous ten posts...you get the idea.

mavrothal · #587 Post by **mavrothal** » Mon 09 Dec 2013, 18:04

pemasu wrote: Edit. Ooops. I noticed just now that Mavrothal confirmed my suspicion. Thank you of confirmation. Well...I did the practical test anyway. Lol.

Please see if the pet resolves the issue.
If it does (it should) you may want to respin 3.5.2.11 soon

If you rather woof it is also fixed there, but the latest zigbert's additions are currently in the "testing" branch only.

mavrothal · #588 Post by **mavrothal** » Mon 09 Dec 2013, 18:08

pemasu wrote: Is is good intention. Just dont put semi-working stuff to the master branch before someone has tested the testing branch or firmware branch version first.

I can not argue with that

All I can say is that as with your laptop I did not have an issue. But then again my wireless firmware was already in /lib/firmware ...

pemasu · #589 Post by **pemasu** » Mon 09 Dec 2013, 18:30

Good thing would be: Placing the firmwares to the standard location would be soon learned and utilized. Hey...I have whole bunch of dvb-tuner firmwares in archive. Just install this pet...extract this tar.gz to the /lib/firmware...and no need to think more.

Puppy style mechanism is...laborious...arduous...troublesome...even painful to maintain.

Updating the /lib/firmware will be easier. There can even be ready made different sets of firmwares. For example b43 needs different sets before - after 3.X and so on.

The problem. Downloading firmwares from the .git. They have all firmwares included, and the kernel you have under work, does not use or need all of them. Brcmfmac is good example. There are newer ones and older ones, and you dont need all of them for spesific kernel.

Just brainstorming. Ignore if you dont like firmwares. Cake tastes better.

But having Tempestuous included it is better that I dont say more...I will soon show my ignorance of the universe....

mavrothal · #590 Post by **mavrothal** » Mon 09 Dec 2013, 19:06

pemasu wrote: Puppy style mechanism is...laborious...arduous...troublesome...even painful to maintain.

Updating the /lib/firmware will be easier.

The only valid reason I see for the old firmware installation mechanism to still be in place, is the need for some analog modems that also still need an init.d entry to start at stratup and a desktop entry to manage them.
Ideally every firmware pet could do it on its own if you could download just what you need and install it in your system. But for this you need the network access that the pet will provide.

So if you include them in the build you need a mechanism to install only what you need in the specific system. Otherwise you end up starting up all the (useless) modem firmware and have a dozen of entries in your network menu.

For all other firmware the kernel and udev manage just fine.
So currently in the "firmware" branch I just move everything to /lib/firmware but the scripts for the modems, and try to hunt down firmware pets to remake them to use /lib/firmware.
If you have a list of firmware pets included in the build(s) will make my life easier as they are all over the place.

BTW, could you (or anybody else) verify that the pet I put up, fixes the problem?

gcmartin · #591 Post by **gcmartin** » Mon 09 Dec 2013, 19:10

@Pemasu, et.al.

This is a good find. Now that this is known by several/many of the WOOF/WOOF-CE distro builders, what is the chance that this can be document and presented so that it is followed by those who would build PUPs.

Question

Is there a formal process to strive to consistency in system builds?
And, can/does the formal process guide exception handling when older/newer firmware needs?

Karl Godt · #592 Post by **Karl Godt** » Mon 09 Dec 2013, 20:05

pemasu wrote:Puppy style mechanism is...laborious...arduous...troublesome...even painful to maintain.

Hmmm ... I think it is more a LICENSE file issue ..

If the LICENSE-driver file is in it's own "tarball", then this issue would be easier to maintain - theoretically .
Theoretically, since it is no tarball anymore and no-one looks into the expanded tarball ( if the LICENSE file is missing ) .

Terry H · #593 Post by **Terry H** » Mon 09 Dec 2013, 21:03

Satori wrote:...
the wireless module 'iwl4965', which is my intel wifi card, was not found and was not on the list of available modules that could be loaded for wifi connections.

Same here on new frugal install.

peebee · #594 Post by **peebee** » Mon 09 Dec 2013, 21:15

mavrothal wrote:Thx for brining this up. Should be fixed in a couple of hours.
Till then please install the attached pet and see if this fixes it.

On my laptop----

- without the fix pet b43 firmware cannot be found / loaded

- with the fix pet the b43 firmware was loaded and established a connection

and Frisbee was installed by pet and worked as expected.

Cheers
peebee

pemasu · #595 Post by **pemasu** » Mon 09 Dec 2013, 22:18

Dpup Wheezy 3.5.2.11 is out !

Firmware loading failure bug fix release. Read latest couple of pages if you are interested.
Also new .svg icons and handling of them has been updated. Zigbert`s new design.

Otherwise same as previous announcement.

Download link: http://www.smokey01.com/pemasu/DpupWhee ... eezy35211/

mikeslr · #596 Post by **mikeslr** » Tue 10 Dec 2013, 00:08

Thanks pemasu and especially mavrothal. The firmware pet worked. I'm posting from wheezy (previous version now). But as pemasu has built a new pup, I'll wipe this version and start from scratch. Hopefully, it will also have solved a new problem I've just experienced
Hopeful of a solution, but before the pet was published, I created a SaveFile. Seeing its publication I booted into wheezy 3.5.2.10. Mid-boot, it stopped with instructions to run xorgwizard. That done I reached desktop, installed the pet and --uncertain if just re-starting X would suffice-- rebooted. Again, booting stalled before desktop was reached.

I'll d/l & unpack wheezy 3.5.2.11 and report back.

Edit: Now posting from wheezy 3.5.2.11. I was able to get online without a hitch. However, even though I created a SaveFile and rebooted, booting stopped at line something like "blah, blah, blah apps in /root/xinitrc" then instructions to run xorgwizard. But just typing xwin got to desktop with wireless immediately working.

p.s. downloading ISO took a long time. But that could be that my wife was also online and two floors closer to the router.

mikesLr

koulaxizis · #597 Post by **koulaxizis** » Tue 10 Dec 2013, 14:24

pemasu wrote:Dpup Wheezy 3.5.2.11 is out !

Firmware loading failure bug fix release. Read latest couple of pages if you are interested.
Also new .svg icons and handling of them has been updated. Zigbert`s new design.

Otherwise same as previous announcement.

Download link: http://www.smokey01.com/pemasu/DpupWhee ... eezy35211/

Downloading now! Thanks!

I only hope not to have the same weird problem!

dejan555 · #598 Post by **dejan555** » Tue 10 Dec 2013, 16:53

Hey pemasu, glad that someone still maintains dpup branch, I booted latest woof-CE built iso on fujitsu siemens laptop (celeron 1.86Ghz, 446Mb ram + 512 swap) 1280x768 automatically set , frugal install straight from iso, booted fast, seems to work OK so far, like the first visual impression.

Satori · #599 Post by **Satori** » Tue 10 Dec 2013, 17:24

Hiyas...

Installed a fresh 3.5.2.11 onto a flash drive and created a fresh savefile, the wifi module
for my intel was now found and was able to connect to the 'net.

However the "dbus" and 'Description' device fields on the wifi connection pages were blanked out.
Does not affect the actual connection tho.

Updating an existing 3.5.2.10, which was updated from a working 3.5.2.8, caused the
'iwl4965' module to be lost and wifi's auto-find failed to find any appropriate driver.

Will now try to find the iwl4965 module files on a working 3.5.2.8 system and try to install
onto a 3.5.2.11 savefile... unless you can tell me where they're usually located.

pemasu · #600 Post by **pemasu** » Tue 10 Dec 2013, 18:01

Satori. Easiest solution.
Copy below shown firmware to the savefile. I think that updating firmwareless 3.5.2.10 causes problem so...safest bet is to put firmware where Puppy`s firmware translocation system is not needed...ie /lib/firmware.
There is nothing wrong with kernel module...I believe...it is the firmware what the device needs.

You find the firmware from fresh 3.5.2.11. If the update loses it...that is the main problem. And you need replace it to the /lib/firmware.

modinfo iwl4965
filename: /lib/modules/3.5.2-dpup/kernel/drivers/net/wireless/iwlegacy/iwl4965.ko
firmware: iwlwifi-4965-2.ucode

Location to the firmware in 3.5.2.11:
/lib/firmware/iwlegacy/iwlwifi-4965-2.ucode

Satori · #601 Post by **Satori** » Tue 10 Dec 2013, 21:06

Hiyas...

An updated 3.5.2.11, from a working 3.5.2.8, shows no wifi device available under the
network setup.. shows only the ethernet port.

Manually loading the iwl4965 module (under 'More') loads the module but reports back
that no new interfaces were found. So it loads the module but never inits the device.

Hardware shows the intel wifi is out there but network setup fails to find or use it.

On a fresh savefile, if I unload the wifi module it's currently using, setup is unable to reload
the wifi device and remains MIA, even with a manual reload of the module.

pemasu · #602 Post by **pemasu** » Tue 10 Dec 2013, 21:29

Satori. I think you should test how things go with fresh 3.5.2.11 install. Without using previous update or transferred savefile. I am interested how fresh 3.5.2.11 works.
Updates and transferred savefiles does not always work.

If fresh 3.5.2.11 works okay. I am happy. You have to remember these builds have been testing and experimental ones so far. I have hoped that 3.5.2.11 would be the first more mature one with Woof-CE.

I dont use Puppy Network Wizard at all. I cant comment problems with it. I use Simple Network Setup. It is the one Barry Kauler has designed. Puppy Network Wizard is included for ndiswrapper usage. Otherwise...I havent used it for years...
Frisbee is not included intentionally. I dont want more confusion of error feedback. If there would be 3 network tools, I couldnt track the problems at all.
I can count to one...

Generic advice for all networking problems:
In console: pdiag
Post the the created tar ball as attachment. It has been useful tool, when there is problem with missing stuff.

Satori · #603 Post by **Satori** » Tue 10 Dec 2013, 22:13

On a fresh 3.5.2.11 savefile, using Simple Network:

1) wifi connects using the iwl4965 module
2) text fields for 'bus' and 'description' on the module shows as blank... no info
3) under 'load module', the iwl4965 does not show up, iwl3945 appears tho.

If I unload the iwl4965 module and do a manual reload, the module loads but reports
that no new interfaces were found and wifi disappears from the network devices list.

Using the same flash drive on another Dell D830 that uses a Broadcom wifi device
instead of an Intel 'N' device, the wifi network sets up correctly using module 'wl' and
it's displayed info description shows up. This is using the custom savefile that was
failing on the D830/Intel wifi laptop. The fresh savefile also starts the wifi correcty.

On a Dell C640 (old pentium laptop), 3.5.2.11 fails to start xwindow when it boots.
However, an 'xwin' continues the start up correctly... probably a timing thing. The wifi
network sets up correctly using an Intel 2200BG wifi card.

In either case, the problem is iwl4965 specific to a previous savefile built under 3.5.2.8,
trying to copy iwl4965 driver files from 3.5.2.8 to 3.5.2.11 has no effect.

--------

Final Solution:

Mounted the bad 3.5.2.11 savefile under another running system and deleted all iwl4965
driver files from /lib/firmware and /lib/modules.

Once this savefile was used as a running system, wifi started correctly with no problems
using the files from the Wheezy SFS.

OscarTalks · #604 Post by **OscarTalks** » Tue 10 Dec 2013, 22:48

Hi Pemasu,

3.5.2.11 is looking good, but I notice we have lost the icon from the menu button. Looks like you have been tinkering with the jwm config files including adding of /usr/share/pixmaps/puppy to the icon paths for those .svg icons. I was wondering about upgrading the jwmconfig2 package, but discovered that if I install the 01micko's files I lose some of those icons from the menu because that path is lost. Some of the .desktop files have the full path to those icons so still work, but for example boot manager, IP info and font manager don't. Just an observation really and not a problem if I don't change anything. Easy to put the menu button icon back too of course.

mavrothal · #605 Post by **mavrothal** » Wed 11 Dec 2013, 05:24

OscarTalks wrote:Looks like you have been tinkering with the jwm config files including adding of /usr/share/pixmaps/puppy to the icon paths for those .svg icons. I was wondering about upgrading the jwmconfig2 package

All gtkdialogs in woof and many icons are under heavy development by zigbert (he is making 10-20 changes/additions a day!!!).
Several pets may also need to be updated to match the new puppy look

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Dpup Wheezy. Woof-CE built debian wheezy 7.2 packages used

Firmware pet worked in wheezy 3.5.2.10