My wifi dongle worked in Raspberrian so I did a lsmod from the command line to figure out which kernel module it was using.

Although it wasn't listed in Puppy's network module list I could load it by clicking on the "More" tab and then on the "Specify" button, but it still couldn't find any new interface.

I thought I saw some kind of error message during boot up before X came up so I exited X ( you could ctrl+alt+F1 to see the boot messages and ctrl+alt+F4 to go back to X ) and that was how I found out that the kernel module for my wifi dongle couldn't find one of its files in the /lib/firmware directory.

You copied the entire kernel? So not only the firmware in /lib/firmware. I can try that too but I would like to stick with the original 3.1.6-cutdown kernel from Barry.
Did he not use T2 source? I think I read something like that but can't remember where.
Thanks for the tips woodenshoe , I will give it a go, and if I can get my hands on the original kernel source from Barry I will try that too and see what happens.

Anyone out there knows where I can download the kernel source sfs for the squeezed arm puppy that Barry used? I would like to stick to the original source if possible.

The kernel that Barry used way back when is very obsolete from when they were first getting their feet on the ground. It has lots of problems that have been fixed along the way.

If you don't want to deal with the kernel yourself, you can use Berryboot, which will install Puppy along with several other distributions in a multiboot kind of situation sharing a fairly recent, good, kernel.

I am not 100% on how it works, but it uses squashfs files and layers like puppy. One layer a read only file system for the OS and then the changes (stuff that would go in the save file in a puppy frugal install) is just in a folder and layered on top of it.

Getflash does not work, the package manager has no flash under the arm6 section and adobe flash in the normal debian section does not want to install. I don't see any external flash file anywhere for Puppi.

Can somebody explain to me as if I was 90 years old how to install flash for chromium?.

3. Wheezy [on a separate 16GB card] boots OK on the same hardware setup, but I think I've corrupted it by a previous improper power-off when I couldn't see the password characters going up on screen as I typed them.
Duh!
I didn't know at that time that they are NEVER displayed, and that is by design.

3. Wheezy [on a separate 16GB card] boots OK on the same hardware setup, but I think I've corrupted it by a previous improper power-off when I couldn't see the password characters going up on screen as I typed them.
Duh!
I didn't know at that time that they are NEVER displayed, and that is by design.

WOOHOO!
Berryboot is brilliant!
So easy to do, and works really well.
I used it to install Puppy and 1 other OS.
Puppy runs just fine.
Fills the screen.
Icons are a good size [I'd like to be able to see stuff OK from the far side of my livingroom].
May need to increase the size of text.

Thanks guys.

BTW: How should I run Youtube videos on this Puppy?
Will Flashplayer install/run?

Edit: typing this from SAP for R-Pi...
Only some of the keys on the keyboard work [right-side keys don't]; don't know which keyboard to specify.
Flashplayer won't download/install using getflash...
Installed Gnash, but that seems to not work.
Iceweasel rather slow.
Zoom has enlarged Iceweasel display.
Global increase of text size has improved matters here and there.
Some text is tiny. e.g. In Xfe.

When I first tried to buy a RPi in February 2012 I was told that the device was temporarily unavailable. In April I was allowed to put my name on a waiting list and in June I was allowed to place an order. The device was finally dispatched to me in December.

I experimented with the 'official' Debian for RPi, but of course what I really wanted was Puppy. Over a period of time I made several attempts at getting Alpha 4 up and running without even the slightest success. In addition to Debian I've been running Fedora and openELEC on my RPi. Fedora is less awful than Debian and openELEC is actually quite good (it more or less turns the RPi into a worthwhile purchase). But none of them are Puppy.

Although I've dived into this thread several times, it wasn't until a few days ago that I found the post from woodenshoe on page 13 that explains how to get alpha 4 to boot on an RPi version 2.

So OK, I've now managed to get Alpha 4 to boot up. I'm online and I can browse the web.

The instructions that woodenshoe gave come in two parts. Making changes to the boot partition of Alpha 4 is easy. Even my Win2000 system can do it. But the changes to the puppy partition are a different matter.

My Lucid Puppy 525 system can't mount the puppy partition on the SD card. It gives an error. My Mandriva system can recognise the puppy partition as ext4 but can't mount it. I tried running SolusOS from a live CD. It can mount the partition but SolusOS is a Debian derivative. It won't give me write access.

So my first question is: Is there a Puppy version that can mount the Alpha 4 puppy partition? If there is, I will happily download the iso file.

The next issue is: woodenshoe talks about switching kernels to 3.2.27. But the world has moved on. If you now download the rpi-firmware-master from https://github.com/Hexxeh/rpi-firmware/archive/master.zip it does not contain the 3.2.27 kernel. It now seems to reference Kernel version 3.6.11.

My attempts at switching to Kernel version 3.6.11 have all collapsed ignominiously. Of course it's probably my fault. I'm not a Linux geek, just a hobbist who happens to love Puppy Linux.

So my second question is: Will there ever be a version 4.0.1 of the Alpha 4 img.xz file that incorporates the changes that woodenshoe described?. It would be a great help people like me who want to load Puppy on their version 2 RPi's.

I ran into the same problem with the second partition not mounting if I clicked on the drive icon, but strangely enough it would mount from the command line.

Code:

mount /dev/sdb2 /mnt/sdb2

Replace sdb2 with whatever is correct for you.

After mounting you can just click on the drive icon to look at the partition, and unmount it from the menu like normal, it is only mounting that doesn't work.

This worked for me in lupu 528. In racy 5.5.1 there was no problem in the first place, but you don't need to download a new version of puppy if the mount command above works.

Since it sounds like you can boot with the original kernel, you could try downloading or copying the rpi-firmware-master.zip from a usb stick to the Raspberry Pi and unpack the new kernel modules there. You can have several versions of kernel modules in /lib/modules (each in their own directory) but a new kernel won't boot without a matching set of it's own modules. (Actually I have booted a new kernel I had compiled for my laptop and loaded the wrong savefile that didn't have the new kernel modules in it and it booted up to the desktop just fine except that the mouse and keyboard didn't work... )

I did try the new kernel 3.6.11+ and it does work too. The second boot is faster than the first, for some reason it needed to look at my mouse and keyboard several times during the first boot. The pinboard didn't load on the first boot either, just a black screen with the task bar at the bottom. Simply rebooting fixed it though.

The file /tmp/bootkernel.log would give you an idea if any firmware is missing. Booting by itself my Raspberry Pi wasn't missing any, but depending on what kind of wifi dongle you attach you may need additional firmware to make it functional. As far as I know firmware files are architecture independent and could be copied from any distro that has the right ones.

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