Slackware V12.1 Problem installing older Kernel
I've searched the Internet and the Forum for my problem but I couldn't find it yet. If there is something already I've missed, I'm sorry to bother you.
I'm doing a commissioning of a forging line and there is a Siemens IPC which should run on a Slackware V12.1.
We're using a Comsoft Profibus Card for Communication. That's where the problems started. The Driver for our current Kernel (188.8.131.52) will be finished until next week. It's not good to stay nearly one week without beeing able to work so we decided to compile an old Kernel for which we have a driver to already test the Signals. (184.108.40.206)
I'm not that deep into Linux and so I've done it step by step with a linux advanced user of our company via telephone.
He did the same operations on his Computer. His installation worked, mine didn't.
When I try to start the old Kernel I get this Error while booting:
So I think that isn't the Problem, but I'm also affraid of deleting or overwriting stuff of the running Kernel.
With the new Kernel ther is also a Problem. I'm not able to switch from the X-Server to the Command Line anymore. I only get blackscreens when I use [ctrl]+[alt]+[f?] , [ctrl]+[alt]+[backspace] , "shutdown -r/h now" or just when exiting it. So my only chance to shutdown is to cut the Power supply. Slackware V12.0 worked flawlessly until I've installed V12.1 then it used to recognize my tiping twice. For example if I wrote "root" it actually became "rroooott". Even if I start it from the DVD. But later we need V12.1 anyway so V12.0 would just be an option for testing until other software parts ar finished.
I hope someone could help me.
Thanks in advance,
Welcome to LQ!
You should build test kernels under /home/username/ so that
you don't mess up /usr/src. This guide will help with that.
As for your error message:
the root filesystem, or the hard drive controller, or both.
You've left a lot out of your post that we'd have to guess
about, such as hardware specs, actually commands, etc.
Not to be rude, but you can Google and find these answers.
Thanks for the reply.
I've searched quite a lot, but I think I probably used the wrong terms.
But i knew it had to do something with the HD. But that the filesystem could be a problem didn't come to my mind.
I'm using ext3 right now. Yesterday I did all step by step like in the guide in this section and somehow it worked to get to 220.127.116.11.
But only when I choose the Kernel 18.104.22.168. It welcomes me to 22.214.171.124 and also "uname -r" returns 126.96.36.199.
If I use the real LILO entry for 188.8.131.52, the error still appears.
The really weird thing is, the driver isn't recognized as the correct version.
So I think I'm still not finished with the Kernel and instead I have some mix of the Kernels.
The Blackscreen problem was discussed quite often but with nvida and ati drivers. This was my fault not to mention what HW Specs this PC has, but I wasn't sure myself, since it isn't that easy to get to the IPC through the cables which are under voltage. Indian wiring some kind of different. ^^
Yesterday evening we had some time without power so I finally was able to get to it.
So these are the Specs:
Simatic Box PC 840 V2
Intel Pentium 4 Mobile 2,2 GHz,
400 MHz FSB, 512 Kbyte L2-Cache
1x 1GB DDR SDRAM
2 x PCI: 1 x short, 1 x long,
2x PCI/ISA (shared) long, 1x ISA long
Graphic is Onboard wasn't able to identify it probably within VIA VT8235M Southbridge (it's using the VESA driver)
160GB HDD EIDE
I'll reinstall the whole Slackware an then log everything during the kernel compiling the way we did it first.
Also I'll try with ext2.
Btw. your link didn't work, but if I mess up my src directory, I'll just install slackware again from the beginning. ;)
Another link to my Kernel Rebuild Guide
Now I've done it completely like in your guide.
With the initrd file I've made, following appeared:
The exported log files are here, including the commands above:
Maybe also necessary:
hda1: linux partition, bootable and formated as ext2, ~158GB
hda2: linux swap partition, ~2GB
I hope now I've made it better than on my first attempt. :)
€dit: Read the reason is a problem with the initrd file and also found somewhere a little bit different code for building it.
Sry for asking some stuff before searching. Normally that's not me, but it just takes so much nerves here. I'd really like to apologise for that.
It works! I added lba32 and append="APCI=off" to the lilo.conf.
Now only my graphic problem is remaining.
Thanks for the Guide Bruce Hill, there is also well explained why some things shouldn't be done, which isn't in many other I've read.
|All times are GMT -5. The time now is 12:03 AM.|