Yes, I have never seen it either. It is fine under Fedora. I have been into the xorg.conf files and it may be that I have to uncomment the "pc102" for a European keyboard. It is a standard GB keyboard, only difference to US keyboard is the @ and " are switched and presence of the pound sign. This is acting really erratically. When the pipe key is pressed it returns ">". Strange.

Bob

Hi
This is the outut from the lspci -v about the missing eth device:


Subsystem: Giga-byte Technology Marvell 88E8001 Gigabit Ethernet Controller (Gigabyte)
Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 9
Memory at fb010000 (32-bit, non-prefetchable) [size=16K]
I/O ports at 7800 [size=256]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data

Not showing up anywhere else.

Bob

I think the | is where the # is, the # is where the £ is and the US don't have a £ or I haven't found it yet.

There are many differences between the US and UK layouts, but I can't remember most of them. Most of the differences aren't straight swaps like @ and "

Hi Again--

Once again, with your help, another problem solved. The dvd and cd writers are hda and hdb respectively. When I assign them fstab this way, they mount just fine.

Now if I can get the keyboard sorted..

I am also in the beginnings of studying how to recompile a new kernel (2.6.15.6). I believe that will solve a lot of my problems because I mostly have newer hardware. But, will I still have the 2.4.31 kernel to boot into in case I run into any trouble?

Bob

To get a UK keyboard map running (at least on the console), issue the command

I guess you could add that to your /etc/profile or .bashrc to make it a little more permanant.

phil,g,d

Thank you. You are correct, the | key is the shift # key. Not too much of an inconvenience to use it this way.

Thanks,

Bob

Sure you can keep your 2.4 kernel--in fact it's a good idea to do so as you'll probably screw up your first kernel compile (who didn't?). There are a myriad of tutorials on how to compile your kernel and everyone seems to have a slightly different way of doing it. So I see no reason not to further add to the confusion and post my method ;).

Clearly you've grabbed the source from kernel.org and unpacked it somewhere (you can compile the kernel in your home directory as a regular user, but you need to be root to install it).

A good place to start may be to grab Slackware's 2.6.13 "testing" kernel config file from ftp://ftp.slackware.com/pub/slackwar.../config-2.6.13

Here's what I'd do:
You can then use the "Load external config" option at the bottom of the menu and feed it the Slack config file from above.

Go through all the various submenus and see what you see. Items marked <*> are compiled into the kernel, items marked <M> are compiled as modules. Note that you'll need your root filesystem (ext2, ext3, reiserfs or whatever) and probably any disk controlers (SATA/SCSI etc.) compiled in otherwise you may run into trouble booting.

Once you're all done, exit and "Save your new .config"

Now the boring bit:
This is the bit where you go and make a sandwhich, pot of coffee etc.

When it's all done:
You can call the kernel whatever you want - it doesn't have to be 2.6.15.6-1

The last bit is to edit /etc/lilo.conf and add an entry for your new kernel. You'll see the orininal entry for /boot/vmlinuz, which points to the 2.4 kernel. Add these lines after that:

Obviously, change the image and root lines to reflect your situation. Then run /sbin/lilo to write these changes to disk, cross your fingers, make virgin sacrifices to apropriate deity/ies and reboot.

I know that's a bit quick & dirty explanation, but it should get you started (and I'm only on my 1st cup of coffee).

Thank you. I am compiling the new kernel now. I use grub, but I would assume since I changed the link in /usr/src for linux --> linux-2.6.15.6 from 2.4.31 that the grub entry already there would boot the new kernel. Is that correct? The grub entry is:

kernel /hd0,1) /boot/vmlinuz root=sda2 ro vga=788

Sorry - I should have remembered from your other posts that you're using grub.

Changing the symlink /usr/src/linux to point to /usr/src/2.6.15.6 won't affect the booting of your box - the kernels are stored in /boot.

I don't use grub, but I'd leave that line in the config file (and the symlink in the /boot directory that points to the 2.4 kernel) so you can boot it if your new 2.6 kernel fails, and duplicate the line, chaning the "/boot/vmlinuz" bit to "/boot/2.6.15.6" (or whatever you named your kernel).

Good luck! (Although it's not as painful as people make it out to be)

Thank you. It has finished compiling and I have rebooted and the 2.4.31 kernel still boots just fine. Whew!! a relief....

I will add another line to grub duplicating the first using the folder name from /usr/src of the new kernel. Wee'll see.

Once again, thank you for all your help. Noobs like me never become users like you without users like you!

Bob

Well, I guess I should expect not to be successful on my first try at recompiling the kernel. 2.6.15.6 would'nt boot. Just went to a black screen and stayed there. Looks like I have quite a bit of studying to do before I try it again.

Bob

You are right.
Lowmem < 1GB
Highmem 1GB<x<4GB
Upper limit is 64GB

may b. experience is the key thing and tht is what we want.
i posted tht since while compiling there was 3 options for highmemory section, off 4gb 64gb, so i thought till 4 gb it wasn't needed. but now i found u r correct, the help in kernel goes like this
this is how we are learing.. thnks "odevans", i am going to get a machine with 1gb ram so evenif i compile i would have missed this ;)
in the sence that security from the user/root. if by chance "chmod, rm-"these commands can spoil the thing why v are playing with devices..

from odevans postdo we need this this is for 2.4 kernel compilation (i think so), may b this wil work but i use this series
may b ur "frame buffer support" is the problem, enable FB, the same issue is discussed in many threads n the same forum

since u r using the grub i cant help on that
hope ur
1.cd/dvd problem over
2. memory pro 1.2 is also solved,
3.font pro is solved
4.cdrecord ( while compiling, enable scsi emulation-if ur drive is atapi)or else append line in lilo under the 2.4kernel section wil do it 4 u. if u want to try in 2.4 kernel
this is a small compilation guide " http://www.linuxquestions.org/questi...33#post2128933 "

Many apologies, rkrishna, but I still cannot make sense of this--I cannot understand how a symlink (with full permissions, I.E lrwxrwxrwx or 1777) can be something to do with security.

After doing the kernel config bit, one can always issue make help for advice on what's about to happen.

Like I said in a previous post, everyone seems to have their own method for compiling and installing a new kernel. Your series of commands are nearly analagous to mine, IE they achieve the same end.

I don't believe that newer kernels need the /boot/System.map link, in the same way that /usr/src/linux is no longer required to point to one's current kernel source.

I'll re-read all my notes for compiling the 2.4.n kernel and get back to you (it's approaching 2am and I've not slept for ninety something hours... ...)