slacky.eu

I have a simple question, here... I want to use 2.6.14.2 kernel.
But I want to ask something...
First of all I want to tell you that I know how to compile a kernel by myself. I have to do that just because my ISP uses an encrypted connection. So I need MPPE/MPPC support in my kernel. And there is a patch for it. I know how to patch the source, and to do "make menuconfig", "make", "make modules_install" and "make install"...
The problem is that I am doing this with the kernel from /testing... (2.6.13 is the latest there)
So I am installing all those .tgz files via "installpkg" and then patch the source and compile the new kernel.
Now I want to compile the latest one, but with the archive from http://kernel.org/
"What's the difference?", you'll ask...
Well, I just want to know... In /testing we have:
alsa-driver-1.0.9b_2.6.13-i486-1.tgz
kernel-headers-2.6.13-i386-1.tgz
kernel-modules-2.6.13-i486-1.tgz

So I will extract the 2.6.14.2 archive in usr/src/linux... Will compile it then.
But what about those packages?
Will I have alsa-driver-1.0.9b for 2.6.14.2? Or headers for it?
I mean I have those from /testing installed. Will they work with the new kernel? OR will they be replaced after compiling?
I am using the command "make modules_install", so I suppose kernel-modules-2.6.13 will be replaced with kernel-modules-2.6.14.2
But what about the headers and the alsa-driver?

These questions may sound stupid for you, but I really want to know...

Basically the packages from the Slackware /testing directory install headers, modules, alsa and the kernel for those people who don't want/need to recompile them by themselves.
Regarding alsa, I compiled the kernel with alsa support built-in, it works fine on my Gentoo machine. In Slackware I still have alsa compiled as runtime module.

By the way, you cannot recompile the kernel from the tgz packages in /testing/packages, since they're not sources, so you will definitely have to get sources either from kernel.org or /testing/source.

I hope this will answer your question.

It may sound stupid for you, but I am compiling it
Well first I am installing all the tgz packages, including kernel-source-2.6.13-noarch-1.tgz
And compiling it to enable MPPE/MPPC support...
Well for modules I have my own answer, just because I am using "make modules_install" comand...
For ALSA... You're right. I am also compiling the kernel with ALSA suport... So now I think I even don't have to install alsa-driver-1.0.9b_2.6.13-i486-1.tgz

And finally... What about the kernel-headers? The last thing I have no answer for...

Sure, I forgot about the kernel-source tgz package
I have no clue about kernel-headers, sorry. But I would be glad if somebody else could answer this question, because I am interested in it as well.

No so easy job, MAT... At least for me

Well I recompiled it and it worked... for a day. Now I have "kernel panic".
And I expected that just because I recompiled it more than 10 times. Just because my network just dissappeared. I have a 3Com lan, build-in my motherboard /ASUS P4C800/
And I coulndn't make it to work... After ifconfig I am only having lo
eth0 is gone
I have no idea why... But I just haven't such a device...
That was the first major problem.
The other one is that I still have no idea what should I do with the headers...
And finally - one small issue. Well after compiling it works, but during the boot time I've lost the specific font and the tux in my upper-left corner /The typical boot screen for Slackware/... Now my boot looks more like a Debian's one... Normal bigger font and no tux.

Well it's not a big deal but I was wondering... in the kernel-source-2.6.13-noarch-1.tgz's description is written:

This is the complete and unmodified source code for the Linux kernel.

So it means that it should be the same like the one which I downloaded from http://kernel.org/
Then why when I recompile a kernel, using this .tgz, it keeps the font and the tux logo, but when I compile it from here:
ftp://ftp.kernel.org/pub/linux/kernel/v ... .2.tar.bz2
The logo and the font goes away...

Please, any help or ideas?

Join #slackware on irc.syrolnet.org, we'll make it work!

victorche ha scritto: And I coulndn't make it to work... After ifconfig I am only having lo
eth0 is gone

you give "ifconfig" or "ifconfig -a" ?

MAT ha scritto:Join #slackware on irc.syrolnet.org, we'll make it work!

You'll have to wait until I reinstall it. I told you - no booting at all I have kernel panic and now I am using Ubuntu 5.10 Live CD to post here...

evaimitico ha scritto: you give "ifconfig" or "ifconfig -a" ?

ifconfig only... But there is not a device /dev/eth0
I have no idea why...

ifconfig shows only active interfaces...

ifconfig -a shows all interfaces, both active and passive.

So try ifconfig -a

if there is eth0 now, you can active it with

evaimitico ha scritto:ifconfig shows only active interfaces...

ifconfig -a shows all interfaces, both active and passive.

So try ifconfig -a

if there is eth0 now, you can active it with

Codice: Seleziona tutto

ifconfig eth0 up

Well I will try after reinstall. But I am affraid, I tried to make
ifconfig eth0 up
And it said that there is not such device... And if I browse the /dev/ directory manually with Konqueror I can't see dev0 too

I have no idea why, but it may be connected with this topic:
Niente eth0
But it is in Italian, so I can't understand the exact problem there...

also in my dev list there isn't any ethX.. it's normal.

ethX is a name referring to a kernel driver (static or modular).

so if modular you must load the module of your network card.

I compiled it in a statica way because i always use networks, and i'll never upgrade it since
it's a part of my laptop mother board.

i hope this can help you

evaimitico ha scritto:also in my dev list there isn't any ethX.. it's normal.

ethX is a name referring to a kernel driver (static or modular).

so if modular you must load the module of your network card.

I compiled it in a statica way because i always use networks, and i'll never upgrade it since
it's a part of my laptop mother board.

i hope this can help you

Thank you for your help... I hope I will fix it... So you're saying that there is no matter if I use (*) or (M) for my 3Com card?
It will be the same?

And what about kernel-headers? Should I use 2.4.31 or 2.6.13? Or how can I have kernel-header 2.6.14.2 ?

victorche ha scritto:Thank you for your help... I hope I will fix it... So you're saying that there is no matter if I use (*) or (M) for my 3Com card?
It will be the same?

I suggest to compile the module built into the kernel, otherwise you'll have to load it every time you want to use the network card.. /me always uses network card, so mine is built-in

victorche ha scritto:And what about kernel-headers? Should I use 2.4.31 or 2.6.13? Or how can I have kernel-header 2.6.14.2 ?

Don't know about this. Kernel headers are in /usr/include/linux, right? How can I find out the version?

victorche ha scritto:And finally - one small issue. Well after compiling it works, but during the boot time I've lost the specific font and the tux in my upper-left corner /The typical boot screen for Slackware/... Now my boot looks more like a Debian's one... Normal bigger font and no tux.

In the menuconfig, go to Device Drivers -> Graphics Support, enable ``Support for framebuffer devices'', then enable ``VESA VGS graphis support'' and select the resolution in ``VESA default mode''. Go to ``Console display driver support'', enable ``Framebuffer console support'' and compiled-in fonts (I also selected VGA 8x16 font. Then go back one level and enter ``Logo configuration'', enable ``Bootup logo'' and ``Standard 224-color Linux logo''.

You should now be able to see Tux while starting up the system and with a nicer resolution as well

Well, sorry... But I made a clean install... Since I am with this lan card, there isn't internet connection with the clean install /kernel 2.4.31/ also

I had a Realtek lan card and it worked fine... But it was damaged after a power loss...
So I had to enable the built-in 3Com card to use it...
Well I enabled all the 3Com options with (*)... Still no eth0
After
ifconfig -a
I have lo only...
And after
ifconfig eth0 up
The answer is that there is not such device...
The funny thing is that in my KDE => Info Center (Kinfocenter)
In the "PCI" section I can see my lan card
The name, the model, the speed... IT says even that it is on Asus P4C800 motherboard...

So how can I see it in Kinfocenter and with
ifconfig -a
It says lo only

Try this If still it ain't working try running again the hotplug check, but I'm not sure whether this can help or not.