(old)Puppy Linux Discussion Forum

I have Puppy 4.1.2 installed to a ext2 partition on my hard drive, but I cannot find a driver that will compile for the built-in broadcom wifi.
So I am trying to setup and install "puppy-4.2.1-k2.6.25.16-seamonkey"
It has the later kernel and there is a wifi driver compiled for this kernel that I want to use.
I checked the download with md5 and it is OK
I burned at 1/2 speed of my CD burner (8x)
I also tried using a program that puts the necessary files onto a USB stick. "unetbootin"
I used "unetbootin" to install my previous puppy 4.1.2 with a USB stick, and it seems fine.

Puppy 4.2.1 will not recognize my hard drive. It acts like it isn't there at all.
I have an empty 35GB ext2 partition waiting to install this on, but it doesn't detect it.
What can I do?
This is a new computer and I dual boot win xp and puppy 4.1.2 with no probs.
Thank you,
Jon

Sorry about the multiple postings, I couldn't get the page to load so I canceled and started it again.
Please delete the others.

Sorry again.

Jon_J wrote:I have Puppy 4.1.2 installed to a ext2 partition on my hard drive, but I cannot find a driver that will compile for the built-in broadcom wifi.
So I am trying to setup and install "puppy-4.2.1-k2.6.25.16-seamonkey"
It has the later kernel and there is a wifi driver compiled for this kernel that I want to use.
I checked the download with md5 and it is OK
I burned at 1/2 speed of my CD burner (8x)
I also tried using a program that puts the necessary files onto a USB stick. "unetbootin"
I used "unetbootin" to install my previous puppy 4.1.2 with a USB stick, and it seems fine.

Puppy 4.2.1 will not recognize my hard drive. It acts like it isn't there at all.
I have an empty 35GB ext2 partition waiting to install this on, but it doesn't detect it.
What can I do?
This is a new computer and I dual boot win xp and puppy 4.1.2 with no probs.
Thank you,
Jon

Boot to Puppy 4.1.2.
Mount the partition you created for Puppy 4.2.1
In the ROX window for it, create a new directory named Puppy421
You do that by leftclicking in the window and picking NEW Directory and typing the name for it.
Now click on the directory you just made to open a window for it.
Back on the desktop, click on FILE and navigate to your iso file for Puppy 4.2.1.
Click on it and it will mount and open a window
Make sure you can see the Puppy421 directory window and then drag and drop vmlinuz, initrd.gz, and pup_421.sfs to it.
Back at the window containing the puppy iso file, click on it and it will unmount.
Close all windows.
Now open your menu.lst file and add this

# Linux bootable partition config begins
title Puppy Linux 421 frugal
root (hd0,2)
kernel /puppy421/vmlinuz pmedia=atahd psubdir=puppy421 nosmp
initrd /puppy421/initrd.gz
# Linux bootable partition config ends

Save the menu.lst file and reboot.

I get "pup_421.sfs not found" when trying to boot puppy 421 frugal.
I entered everything into menu.lst just as above.
I have the necessary files in /puppy421
The only change I made is this, since I'm using /hda7 for puppy421
root (hd0,6)

I had the same error when trying to boot puppy 412 from an externel USB CD burner yesterday.
"pup_412.sfs not found"
This is why I used "unetbootin" on my other PC to copy puppy412 to a USB stick. Then it booted.

Puppy 4.1.2 and 4.2.1 use the same kernel; unless one of them
is a retro version.

Try using the puppy universal installer to install 4.2.1 to the
flash drive. Use the pc to do this.

rjbrewer wrote:Puppy 4.1.2 and 4.2.1 use the same kernel; unless one of them
is a retro version.

Try using the puppy universal installer to install 4.2.1 to the
flash drive. Use the pc to do this.

Sorry for not replying sooner, been on holiday.
My first post wasn't specific enough. The Puppy 412 that I have installed is retro and has the 2.6.21.7 kernel.
I tried using the above method to install Puppy 421 to my flash drive, using my desktop PC.
When I boot my Dell Mini 10 with Puppy 421 on the flash drive, I have 2 issues.
The main issue is the same as above. My internal SATA hard drive isn't detected.
Other issue is most of the graphical elements don't work in 'X'
Background, icons, and drop boxes are missing.
I can overlook this second issue, because my main issue with Puppy 421 is that it doesn't detect my hard drive.
In gparted, the only drive detected is the flash drive.

Is your aim to use the wl broadcom driver...if so having it compiled for the retro version should be possible since thats what appears to be working for you.
did 4.12 standard work?
I did have to use pmedia=scsihd for a frugal to work on a similar machine..illogical I know

mike

mikeb wrote:Is your aim to use the wl broadcom driver...if so having it compiled for the retro version should be possible since thats what appears to be working for you.
did 4.12 standard work?
I did have to use pmedia=scsihd for a frugal to work on a similar machine..illogical I know

mike

Yes, that's exactly what I need to do, but I have read somewhere this particular driver will only compile for 2.6.25.16 or 2.6.25.xx kernels.

I'm a complete newbie at compiling, and I set up "devx_412.sfs" for my Full install. I found a thread here that describes how to set it up in Full installs of Puppy.
Then I followed the instructions to "Make" the Broadcom driver into a usable module on this page: http://www.murga-linux.com/puppy/viewtopic.php?t=38527
Mine compiled without any errors, but when I tried to "insmod" it, I would get "unknown symbol" error.
Two more details below:
1. When I first compiled the driver, I'm not sure how I loaded it, but it appeared to be working, and I got the wireless interface up in the network wizard.
It seemed like it failed during the scanning. So I rebooted and tried to load the driver, and that's where I started getting the "unknown symbol" error.
2. During my search for info on this driver, I came across a site that described compiling the driver in "fedora"
http://djkaos.wordpress.com/2008/10/25/ ... ta-driver/
He recommended updating the kernel headers for your kernel. I'm kinda lost here, but I downloaded "kernel-src-2.6.21.7-patched-puppy4.1retro.sfs" (it is in same directory as "devx_412.sfs"). I installed this using the method described here to install devx_412.sfs to a full install.

I tried pmedia=scsihd (I still got the same error: "pup_421.sfs not found")
I'll try 412 standard later. I haven't downloaded it yet, and sometimes it takes me several attempts to get a "clean" download. (md5 matches)

I downloaded and burned puppy 412 standard, "puppy-4.1.2-k2.6.25.16-seamonkey.iso" to a CD.
It booted off my external CD drive on my Mini 10 with no problems but,
the hard drive isn't detected.
I tried universal installer-> to internal HDD - "no media detected"
Tried Gparted -> "detect all drives" - "no media detected"

I have read somewhere this particular driver will only compile for 2.6.25.16 or 2.6.25.xx kernels

the driver is a generic one so compiling it is really putting it in a wrapper that the kernel can work with.
Perhaps a request is needed in 'additional software' and someone like tempestous do it since he made the other one sucessfully...I'm sure there's a few who whould benefit from this.
I did try on nimblex and it would load but signal strength would vary wildly so I guess there's a trick or two to getting it right.

mike

Back to my original question.
Why doesn't puppy with the later 2.6.25.16 kernel detect my hard drive?
I am trying puppy-413-NOP-r1
It has also got the 2.6.25.16 kernel.
There is no hard drive detected.
How can the 2.6.21.7 kernel versions detect the HDD when 2.6.25.16 kernel versions cannot?
I have a 160 GB hard drive that is useless in these later kernels, what gives?
I gave up on wireless. I guess I'll just carry a cat5 cable with me or use windows xp for wireless.

How can the 2.6.21.7 kernel versions detect the HDD when 2.6.25.16 kernel versions cannot?

well that is something only barry can answer.

The slaxer pup will probably work but then there is no wl driver compiled for it...you could ask

mike