Page 4 of 9
Posted: Fri 25 Oct 2013, 05:56
by James C
You can tell I haven't used 3.01 in a while........ forgot about the first run wallpaper.
Rebooted and everything appears to have saved including the internet connection.Hadn't seen Netsurf in a while either.
Code: Select all
# uname -a
Linux puppypc 2.6.25.16 #1 Tue Aug 26 10:45:53 GMT-8 2008 i686 AMD Athlon(tm) XP 2400+ AuthenticAMD GNU/Linux
# free
total used free shared buffers
Mem: 1035420 360432 674988 0 31736
Swap: 1228932 0 1228932
Total: 2264352 360432 1903920
#
EDIT:
First bug...... Pmount not working but MUT is working fine.
Posted: Sat 26 Oct 2013, 02:20
by Mercedes350se
James C wrote:Had a little free time..... I changed the sfs from pup_301.sfs to pup_412.sfs and it appears to boot fine (the initrd.gz hunts for the 412 sfs)
What did you do about the zdrv_301.sfs?
Which vmlinuz and initrd.gz?
Posted: Sat 26 Oct 2013, 02:52
by James C
Mercedes350se wrote:James C wrote:Had a little free time..... I changed the sfs from pup_301.sfs to pup_412.sfs and it appears to boot fine (the initrd.gz hunts for the 412 sfs)
What did you do about the zdrv_301.sfs?
Which vmlinuz and initrd.gz?
Quick answer...... not using it.Only using the main sfs.
The unchanged vmlinuz and initrd.gz from Puppy 412..
Unsquashed the 301 sfs, and copied in /etc/modules/ from 412 (instead of using the zdrv) then deleted /lib/modules/ and /lib/firmware/ from the 301 sfs and copied in /lib/modules/ and lib/firmware/ from 412. Resquashed the 301 sfs and used it and the vmlinuz and initrd.gz from 412 to do a quick frugal install.
Probably could get it to work without renaming the sfs but I just did it the quick way.
EDIT:
Almost forgot...... while the sfs is unsquashed edit /etc/puppyversion/ to "412" instead of "301". This version shows as 412 but its still 301 just with the newer kernel..... posting from it now.
Posted: Sat 26 Oct 2013, 03:35
by James C
Did a little more hacking around and I now have a version working still using a
pup_301.sfs. Other than Pmount not working (Mut still works fine) everything else looks good.
Still no zdrv......
Posted: Sat 26 Oct 2013, 04:11
by James C
For the version without renaming the sfs....
Unsquashed the 301 sfs, and copied in /etc/modules/ from 412 (instead of using the zdrv) then deleted /lib/modules/ and /lib/firmware/ from the 301 sfs and copied in /lib/modules/ and lib/firmware/ from 412.
Open the initrd.gz from Puppy 412 and replace the file "puppyversion" with the one from 301.Rebuild the initrd.gz.
Resquashed the 301 sfs and used it and the vmlinuz and initrd.gz from 412 to do a quick frugal install.
This works without renaming the pup_301.sfs.
EDIT:
I went ahead and uploaded pup 301-k-2.6.25.16.iso .......if interested I'll supply the link.
Posted: Tue 29 Oct 2013, 00:01
by Mercedes350se
James C wrote:I went ahead and uploaded pup 301-k-2.6.25.16.iso .......if interested I'll supply the link.
Yes please.
Posted: Tue 29 Oct 2013, 00:30
by James C
Mercedes350se wrote:James C wrote:I went ahead and uploaded pup 301-k-2.6.25.16.iso .......if interested I'll supply the link.
Yes please.
http://www.smokey01.com/JamesC/vintage/ ... .25.16.iso
http://www.smokey01.com/JamesC/vintage/ ... 5.16%20md5
As I noted, Pmount doesn't work and I honestly didn't try to fix it. Everything else appeared fine in some quick testing.
Posted: Wed 30 Oct 2013, 07:03
by Mercedes350se
James C wrote:EDIT:
Almost forgot...... while the sfs is unsquashed edit /etc/puppyversion/ to "412" instead of "301". This version shows as 412 but its still 301 just with the newer kernel..... posting from it now.
For the sake of discussion, "What is in the puppyversion file for 3.01retro - is it 301 or 301retro or ... ?"
Thank you for the upload info.
Posted: Mon 04 Nov 2013, 10:45
by nic007
nic007 wrote:Okay. Switched the puppy 5390 kernel to puppy 412 and then converted to 4sfs. Everything works fine except for the timezone, date and time. Wouldn't accept/save the customized correct settings, keep on changing after every reboot. Any ideas to fix it? Settings appear to be incorrect in the base file.
Still looking for an answer to this. If I change the timezone at bootup the screen flickers and the correct time appears. Is there a script that can run at start-up to set the clock correct automatically? I'm at GMT +2. Thanks
Someone?
Posted: Mon 04 Nov 2013, 11:51
by mikeb
Ok no idea nic007... all I have is that in puppy 4 I have /etc/localtime as a symlink to /usr/share/zoneinfo/Etc/GMT-0
in puppy 2 its
/usr/share/zoneinfo/GMT-0
gmt0 made the clock behave for me ...the path would be set by the version of???????? note the etc
might give a clue
mike
Polarpup now rides a Racy 5.3
Posted: Wed 27 Nov 2013, 06:01
by Pelo
Polarpup now rides a Racy 5.3
Wireless, sound, QT all good, nothing bad.
video of how-to
Posted: Sun 22 Dec 2013, 16:56
by Wognath
I couldn't resist any longer and tried jrb's kernel transplant method on pup-431bcm4312v3, which is approaching its 4th anniversary on my Lenovo S12. All goes well except that if I keep the savefile by renaming pupsave.2fs to warysave.2fs, I can't establish a wireless connection (Failed command: ifconfig wlan0 up). Wary and hybrid with no savefile connect immediately using b43. 431 used wl. In the end, I started over with a new savefile, which was probably a good thing anyway, and have had no further problems.
Can someone explain how something in my savefile would prevent the drivers in the new kernel from working properly?
P.S. The reason for kernel change was lack of a driver for my particular SD card reader in the 2.6.30.5 kernel; also gained the ability to mount late-model sfs files.
Posted: Sun 22 Dec 2013, 17:16
by mikeb
And patching the kernel caused indigestion
wl does not work so well in later kernels plus ssb may interfere as that's needed for usb1
b43 does work better in the later kernels anyway.
so your old wl config in the save would force a driver that would not work or may be absent.
mike
Posted: Sun 22 Dec 2013, 18:05
by Wognath
mikeb,
patching the kernel caused indigestion
Yeah, I forgot to mention my indigestion
All the later pups connect my broadcom wireless with b43, but jrb used wl in his custom 431. wl is not in the wary kernel. So where in the savefile is the wl module specified? I tried deleting the /etc/network-wizard folder. When I run the wizard and load b43, why doesn't that override whatever is in the savefile?
Posted: Sun 22 Dec 2013, 18:36
by mikeb
Hmm probably a black list of ssb which rerunning the network wizard would not alter....or perhaps wl is still loading.
all that comes to mind...the wl pets did make a couple of changes.
mike
Posted: Sun 22 Dec 2013, 21:07
by peebee
Wognath wrote: wl is not in the wary kernel.
Don't know if it helps - but wl is available for Wary5.5 at:
http://www.murga-linux.com/puppy/viewto ... 360#609360
wl works fine for all latest Puppies and latest kernels up to and including 3.10....for me
Posted: Mon 23 Dec 2013, 03:04
by Wognath
@mikeb,
I've tried a few more things with this, and I'm none the wiser. ssb is not blacklisted. I have removed from the old savefile everything that I thought related to networking, but I still get
Code: Select all
failed to raise interface wlan0
failed command was : ifconfig wlan0 up
Error returned was ifconfig: SIOCSIFFLAGS: No such file or directory
@peebee
Thanks. I found your awesome collection of wl pets and used several while I was fooling around with different kernels. My wireless connects with b43 in later kernels, but apparently something in the original 431 savefile is interfering, whether b43 or wl.
Ok, back to making tamales
Posted: Mon 23 Dec 2013, 07:22
by peebee
Wognath wrote: but I still get
Code: Select all
failed to raise interface wlan0
failed command was : ifconfig wlan0 up
Error returned was ifconfig: SIOCSIFFLAGS: No such file or directory
Hi Wognath
That error usually means firmware can't be found - and the firmware loading mechanism did change between Puppy editions and kernels - if you look in dmesg there may be missing firmware error messages?
You will need to make sure that the firmware is present and is located in the correct place.
Cheers
peebee
Posted: Mon 23 Dec 2013, 12:56
by mikeb
With kernel changes come mysteries beyond our comprehension.... saying from ancient greece....
mike
Posted: Mon 23 Dec 2013, 22:35
by Wognath
the firmware loading mechanism did change between Puppy editions and kernels - if you look in dmesg there may be missing firmware error messages?
peebee, you hit the nail on the head. dmesg output includes
Code: Select all
b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found
In Wary, this file is in /lib/modules/all-firmware/b43/lib/firmware/b43. Creating a symlink to that folder in /lib/firmware solves the problem and allows wireless to connect! I still don't understand what it is about the savefile that causes puppy to look in the wrong place...
With kernel changes come mysteries beyond our comprehension
Thanks to both of you for the help.