Get it from here:
I'm uploading from the Telecentre at Dalwallinu, and have been here almost two hours, and the 2.6.25 build is taking too long -- I don't want to go over two hours as I'll have to pay for another half hour.
But, I see onlne that my motel has Internet access, so I'll back there soon and try again. For uploading the 2.6.25 build that is, the 188.8.131.52 build has uploaded successfully.
A few upgrades from zigbert and plinej missed out, but can probably put those in the final.
Comments:Posted on 2 May 2008, 15:34 by GeoW
I guess you showed them! Nobody is going to
force you to rest!
Posted on 2 May 2008, 16:42 by GeoW
21.7 Up & Running
Puppy 4.00 SC on 21.7 kernel is up and seems
to be running well. The 25 kernel gave me a
bad MD5 check so I will DL again. Devx passed
Posted on 2 May 2008, 17:06 by tempestuous
Last minute fix - I just discovered that the new b43 module in the 2.6.25 kernel requires different firmware than we had for the earlier bcm43xx module.
Instructions to build the "b43-fwcutter" utility and extract the firmware are here -
under "You are using the b43 driver from linux-2.6.25 or newer"
The firmware should ultimately be located in /lib/firmware/b43
Or if you prefer, I just attached the firmware to the main forum as a dotpet
Posted on 2 May 2008, 17:18 by GeoW
25 kern bad md5
2 tries now - the 25 kernel version does not pass
Posted on 2 May 2008, 21:21 by tempestuous
firmware fix cont.
Oops, more reading reveals that different firmware again is required for older "legacy" bcm chipsets.
I just attached this extra firmware to the same forum thread as before.
The firmware.dep script should list both sets of firmware for installation when the b43 module is first loaded. Then the b43 module will automatically choose which firmware to use when it detects the exact chipset in use.
Posted on 2 May 2008, 21:24 by GeorgR
46 MByte for 25 kernel?
File size of the 25 kernel is under 46 MBytes?
21 kernel is running very well.
Posted on 2 May 2008, 22:26 by pakt
Any chance of a k184.108.40.206 'retro' version? Would be great as we have so many modules for it ;-)
Posted on 2 May 2008, 22:38 by tempestuous
Sorry, another error: I thought there was only a single module, but I see now that there is a separate module called b43legacy.
Obviously there's a different set of firmware for each module.
Good to see you back on the forum pakt. And good to see you're still using the old 220.127.116.11 kernel!
Posted on 2 May 2008, 24:19 by samdude9
Bad MD5 on 2.6.25
Third attempt at downloading the .25 version - fails md5 everytime so far :/
UPDATE: While I was writing this the next download finished, still wrong md5 it has:
Posted on 2 May 2008, 24:38 by Prit1
I have the same issue with .25 downloads as mentioned by samdude9. MD5 is incorrect. I also get the second MD5 mentioned by samdude9.
I tried booting my Averatec 3200 with .21.7 kernel dingo, wireless is not detected (similar to 3.99 - not even in Pwireless). 3.98 could however detect wireless.
Posted on 2 May 2008, 24:47 by happypuppy
WARNING: Incomplete file
Don't bother (re)downloading that file again. The upload is definitely incomplete (only 48MB in size). What a shame.I just wanted to test that new cutting-edge 2.6.25 build.I'm not interested in any of the older kernel builds :(
Posted on 3 May 2008, 2:00 by GeoW
The icons: floppy, home, ... ,cdrom no longer
appear art the bottom of the screen. I don't
remember you saying you were going to leave them
Posted on 3 May 2008, 4:49 by Prit1
Re: Missing Icons
@GeoW: I think Barry has disabled the Hotpup daemon by default. This is the one that puts out the floppy, home,...,cdrom on the desktop. You can enable it by going to "Hotpup drive icon settings" under the Desktop in Menu.
Posted on 3 May 2008, 4:57 by Bosco Bearbank
Prit1: 3.99 worked for me with my Averatec 3250, which uses the rt2500 wireless driver. If I recall correctly, Averatec used a couple of different wireless chips in the 3200 series laptops; not sure if yours is the same as mine. Will check out 4.00sc as soon as I get it burned to a cd
Posted on 3 May 2008, 5:34 by Bosco Bearbank
Wireless works on the Averatec in Dingo 4.00sc - I'm posting from it
Posted on 3 May 2008, 5:38 by Prit1
Re: Averatec 32xx
@Bosco Bearbank: I rebooted the 4.00SC and wireless started working. This is still intermittent. Mine uses the rt2500 driver too.
Posted on 3 May 2008, 5:48 by GeoW
You are exactly right. My icons are back. Now I
will read back to find out why they were off.
Posted on 3 May 2008, 7:19 by samdude9
Hi, I was just checking to see if .25 was has been reuploaded? As I saw on the ftp it's size changed from exactly 47,000KB to 48xxxKB, any word? Thanks all
Posted on 3 May 2008, 11:04 by wolf_pup
Barry, could you change the http: to ftp: for the reason that the http: one gives garbled letters on download.
Posted on 3 May 2008, 14:37 by firstname.lastname@example.org
Awaiting the complete later kernel (many thanks for doing that Barry)
Wanted also to say that release "SC" Sanity check is much better than RC2, RC3 etc for the final beta, nice one!
Posted on 3 May 2008, 15:20 by Lobster
Dingo Download news
Will Barry get to Perth? Will the new kernel be available?
News of Dingo as it happens . . .
Posted on 3 May 2008, 16:36 by samdude9
...Find out next week on... The Puppy Release Show! ;P
Posted on 3 May 2008, 16:39 by samdude9
...Find out next week on... The Puppy Release Show! ;P
Posted on 3 May 2008, 20:54 by BarryK
Re: the .25 build
Well, my latest post explains all. Big delay, but it's uploading right now.
Tempestuous, yes I know all about the firmware for b43 and b43legacy. The .25 build has it all.
Yes, HotPup is off by default. The reason for this is that it has many unresolved issues. Not sure if I can think of them all right now....
1. Mounts ntfs r.o.
2. If unmount a partition with anything else, such as Pmount, HotPup continues to show it as mounted.
3. text hidden in some resolutions.
Posted on 3 May 2008, 20:59 by BarryK
There are two different modules, b43.ko and b43legacy.ko.
Posted on 3 May 2008, 21:47 by tempestuous
b43 & b34legacy
Sorry. The new firmware was a surprise to me and I hastily assumed you may have missed this as well.