Guest GorGor Posted June 18, 2003 Report Share Posted June 18, 2003 Hi mdk 9.1 I was able to run make menuconfig ok, so I tried to do it with a new kernel. after su, cd /usr/src/linux make mrproper rm linux I then copied linux-2.5.65 to /usr/src/ and deleted old kernel then ln -s (new kernel) linux make menuconfig then gave 2 errors 1. Makefile 237 arch/i386/Makefile no such file or directory 2. make no such rule to make target arch etc. Can anyone spot and correct my errors? cheerio Quote Link to comment Share on other sites More sharing options...
tyme Posted June 18, 2003 Report Share Posted June 18, 2003 did you check to see if Makefile exists in /usr/src/linux/arch/i386 ? if not, then there may have been an issue with copying, extracting, or symlinking. most likely copying or extracting. Quote Link to comment Share on other sites More sharing options...
sarah31 Posted June 18, 2003 Report Share Posted June 18, 2003 after su, cd /usr/src/linux make mrproper rm linux I then copied linux-2.5.65 to /usr/src/ and deleted old kernel then ln -s (new kernel) linux if these are the steps you did this would be your problem. you should have (and feel free to correct me if i interpretted your post incorrectly) cd /usr/src mv linux linux-old mv whereeveryournewkernelsoureceis /usr/src tar -zxvf (or jxvf) linux-x.x.xx ln -s linux-x.x.xx linux cd linux make menuconfig Quote Link to comment Share on other sites More sharing options...
Steve Scrimpshire Posted June 18, 2003 Report Share Posted June 18, 2003 Also, I don't know how experienced you are, but odd numbered kernel releases (the number after the first decimal point) like 2.5.65 are devlopment kernels and you'll have lots of problems that you'll have to solve. If you are not comfortable troubleshooting problems like that, stick with 2.4.x kernels until 2.6.x kernels come out. Quote Link to comment Share on other sites More sharing options...
sarah31 Posted June 18, 2003 Report Share Posted June 18, 2003 Also, I don't know how experienced you are, but odd numbered kernel releases (the number after the first decimal point) like 2.5.65 are devlopment kernels and you'll have lots of problems that you'll have to solve. If you are not comfortable troubleshooting problems like that, stick with 2.4.x kernels until 2.6.x kernels come out. sorry but i must disagree a bit with this. while it is not uncommon to have some problems it is not a given that you will have problems. you do have to install a app called modutils or something like that that accounts for change to module management in the new kernel. btw the most current 2.5 kernel is 2.5.72 i believe. Quote Link to comment Share on other sites More sharing options...
Steve Scrimpshire Posted June 18, 2003 Report Share Posted June 18, 2003 Respectfully, here is a small excerpt from a dialogue going back and forth about 2.5.70 from a LUG where i used to live: Ok.. got 2.5.70 running. Had to make a change in rc.sysinit to get module loading working (ignore the line breaks.. you get the picture). $ diff /etc/rc.d/rc.sysinit /x//etc/rc.d/rc.sysinit 337c337 < if ! grep -iq nomodules /proc/cmdline 2>/dev/null && [ -f /proc/ksyms ]; then --- > if ! grep -iq nomodules /proc/cmdline 2>/dev/null && [ -f /proc/modules ]; then Also, had to add two lines to /etc/modules.conf to get the USB subsystem working: alias usb-controller usb-ohci alias usb-controller ohci-hcd The first line is for when it's booted under 2.4.x, the second for 2.5.x. I also had to update mkinitrd and the module-utils and e2fsprogs. That's a lot of core stuff, so I just make a copy of my / partition onto another partition and used it as 2.5.x scratchpad. The only thing left to get working is ALSA and cd ripping with the new high performance cdrtools. One strange thing I did note is that under burst I/O (like untarring a large file), the system would seem to hang briefly (2-3 seconds) while data was being flushed to the disk - usually after the tar command had already completed and the shell prompt was returned. I'm running /home on a reiserfs partition so I haven't narrowed it down to if it's the reiserfs, or file I/O in general. Quote Link to comment Share on other sites More sharing options...
tyme Posted June 18, 2003 Report Share Posted June 18, 2003 deleted a section, as i didn't come across the way i intended to come across. anyways. so GorGor, did any of the suggestions help you? if you have more problems, feel free to post them and we'll do what we can to help :-) Quote Link to comment Share on other sites More sharing options...
Steve Scrimpshire Posted June 18, 2003 Report Share Posted June 18, 2003 Uh, I thought that was what I was doing? I would want someone to warn me if I didn't know what 'Alpha' meant for some base component of my system. Edit: Also, the excerpt I posted would be useful in this situation. Quote Link to comment Share on other sites More sharing options...
Guest GorGor Posted June 19, 2003 Report Share Posted June 19, 2003 Hi all I have never had so many robust replies so thankyou all for speedy replies. I am trying the 2.5 as I had one handy on a cd but will grab a 2.4 after I re-try the other suggestions. I am not very experienced, but I figure my partimage images will get me out of trouble if I have any. I won't post again until I try out both if you don't mind. Quote Link to comment Share on other sites More sharing options...
Guest GorGor Posted June 22, 2003 Report Share Posted June 22, 2003 Hi I found two problems with what I posted above. 1) I used Konqueror to open and copy my linuxformat cd for my new kernel. I did not run konq in terminal mode so never got any errors. 2) linuxformat magazine regular as clockwork claims that the command to decompress a tar.bz2 file is TAR XVF --BZIP2 (FILE).tar bz2 and my file is linux-2.5.65.tar.bz2 (my capitals) and I have never got this command to work so I always used konq. silly me. So, Tyme was right,....no such file because konq did not decompress it and copy it correctly and I was none the wiser until I went looking at the size of my old kernel and the new. Sarah was right with my poor typing and once I used the command line to cp and tar the new kernel even xconfig worked , heh heh. And I took Steve's advice cos I have one other issue and decided not to pursue 2.5 series. MY new issue is all this time I have thrown away a number of linuxformat cd s as I could not get the darn things to always work. I now realise I may have to become a command line advocate which is just what you gals and boys want, I supppose. end of my rant. I am sorry I did not find the error in my ways earlier and hope you will still help me in the future. Quote Link to comment Share on other sites More sharing options...
Steve Scrimpshire Posted June 22, 2003 Report Share Posted June 22, 2003 No problem. For future reference, this is easier: tar jvxf <file>.tar.bz2 or tar zxvf <file>.tar.gz tar xvf --bzip <file>.tar bz2 is the same as tar jvxf <file>.tar.bz2 Note that you don't put the < > or the ( ) in the actual command, just the name of the file like: tar xvf --bzip linux-2.5.65.tar.bz2 Notice also that they say --bzip2, when it's actually supposed to be --bzip Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.