Puppy Linux Discussion Forum

[Bruce B]

[shroomy_bee]

re: going ahead & crashing your system.

How are you meant to get back into your OS to try compiling it again, if it hasn't recompiled correctly?

[shroomy_bee]

re: this link from the link in alcy's post -

http://www.digitalhermit.com/linux/Kernel-Build-HOWTO.html

What is the Puppy equivalent command to see hw info? The various switches for lspci do not give the info as the link shows.

[alcy]

[alcy]

[shroomy_bee]

The Hardware Info on the GUI doesn't do all that info either, was why I asked. I thought it would have, cause I was trying to get it to display info on my motherboard here and the likes of graphics chipsets.
It doesn't show anything on the USBs, nor the PCI cards (in the format in the example).

With the other question I was more meaning that there's more to it than just going ahead; like you say, you'd need to be aware of things like editing the boot menu, as well as,

http://www.digitalhermit.com/linux/Kernel-Build-HOWTO.html#CHANGE-PATCHLEVEL

http://www.digitalhermit.com/linux/Kernel-Build-HOWTO.html#BACKUP-CONFIG

It's not much use to find all that out only after you try a failed recompile.

[alcy]

I wonder if I have been too lucky then.

No.

According to the original link I posted, I compile the new kernel in my home directory rather than /usr/src. Also, I have never had to work with patches et al., since I didn't require them (my system worked without them). Backing up .config files can be useful, but hey, I never said I was a pro at this, so use your own discretion too.

Also, HardInfo has been pretty useful to me, since I can already see all the modules that are loaded along with other needed data, including scsi modules et al.

[Bruce B]

alcy,

Did you succeed? What Puppy version?

As far as modules loaded, I think a lot of modules are internal and you don't seem them loaded, that Barry (or whoever is compiling these days) used a combination of internal modules and external ones.

A modular - monolithic build combination. I've been lucky also, I think it mainly has to do with recognizing what the words mean.

Bruce

[alcy]

@Bruce

Yes, as far as I know, I did succeed in compiling the kernel for Puppy 4.

Talking of modules, I can tell you what I did, or actually what I think I did.

There were options for building the components into the kernel itself or to compile them as separate modules which could be loaded or unloaded. I went with the former. Also, I should mention that in Puppy actually, I didn't see the options for compiling the components as modules (except a few, like scsi_wait_scan), whereas in Ubuntu I saw the option for compiling as modules in every component.

[Bruce B]

alcy

Did you recompile it to make if more efficient and refine for your hardware, to get support that wasn't supported, I curious about why, if you wouldn't mind a brief answer.

If you are up to it, I very interested in the details on this offer to explain what you did and etc.

Bruce

[alcy]

@Bruce

I'd be happy to share.

I had been wanting to do it just for fun, but there were technical reasons too:

1. Puppy 4, with the default kernel was unable to detect my external usb cd drive.

2. I wanted to optimize for the hardware to increase the boot speed.
I got it down from 38.87 seconds to around 30 seconds, which I think is not bad. But, it can be worked on.

3. I am a student and I NEED to know the way around my kernel !

4. The OLPC support in the new kernel was an attraction too.

[MU]

I would like to build a new Kernel for Muppy, but I am a newbee in this concern.

So I also would appreciate, if someone writes a howto for the current kernel.

Thanks, Mark

[alcy]

[MU]

ok, I will have a closer look in some days, thanks

Mark

[erikson]