Problem with Slackware installation!
Hello folks.
I recently install slackware on my hd. Is my first instal, so probably i am doing something wrong. I boot the slackware 14 from my pendriver. # Huge.s. # Map keyboard - ok. # root Pendriver - /dev/sdb HD - /dev/sda # cfdisk /dev/sda1 - 1 swap (82), 2 Linux (83)bootable - write on disk # Setup # Format 1 Swap # Format 2 Linux # Instal from a harddriver # /dev/sdb1 # /slackware # Full # All config was norma except lilo. Lilo # Install lilo automaticaly # Install on MBR # Trying to instal Lilo - Error. Try FIX MBR OR IGNORE PARTITION TABLE. # Continue to configure the default values. # Exit # Ctrl + Alt + Delete After remove the pendriver and try to boot from Hd, the pc kepps restarting. Important: After the BEEP and MB Bios Screen, the vídeo shutdown. Can some one help? |
There appears to be a problem with your LILO installation. Try booting from your install media and then rerunning 'liloconfig' to write the lilo boot loader to the MBR on /dev/sda1.
You can get more information on LILO here. http://docs.slackware.com/slackbook:booting#lilo |
Did you succeed in installing LiLo. From the sequence you give
Quote:
For a first shot at fixing this, I would suggest booting to the pendrive, running the setup routine again, then cursoring down to the "Configure Your New System" (I think that's the wording) and rerunning it, this time choosing the "expert" or "manual" Lilo install. Do not skip a step, especially the one about adding a Linux partition to Lilo. The "expert install" throws you back to the menu about a third of the way through, so that one can conclude (as I have done) that it is complete, when it is not. As a footnote, I normally install to the MBR and it works without issue. I have never had the automatic Lilo install work for me. |
Quote:
|
Quote:
Everything went well until I went to LILO the MBR. I kept getting messages about DOS partitions (which I definitely did'nt have) and the system eventually told me that the only way I could boot was from an external drive. It turned out that the DOS partition on the USB was confusing liloconfig. The solution was to reboot from the USB drive, chroot /dev/sda2 and edit the lilo.conf file manually. After running lilo again, everything was fine. Hope this helps. |
Quote:
The others solutions above dosent help. |
Quote:
Quote:
|
Quote:
# mkdir /mymnt # mount /dev/sda2 /mymnt # chroot /mymnt # vi /etc/lilo.conf (if you are unfamiliar with vi you can use nano /etc/lilo.conf instead) # lilo You should then be able to remove your installation media and boot normally. Assuming you have installed Slackware 64-bit, the relevant section of the lilo.conf file (towards the end of the file) should read as follows: Code:
# # Linux bootable partition config begins Make sure you have deleted all other partition config references - especially those relating to windows partitions from lilo.conf. |
It Works, but i am having new problems!
Quote:
Tanks mate. Your solution works. Slack was installed and booted! The problem was the lilo.conf. I used expert mode at setup, then edited the lilo.conf manualy correcting the errors. Startx works fine. Bu i'm having other problems. The linux HD is an IDE. After trying the slackware, i tryed to shut down and connect my 3 other HDs (sata) NTFS where i put music, videos, etc..., then i have a stop error when huge.s is loading. Here is the photo i made. I hope it helps to see the error. http://arymaynart.xpg.com.br/IMG_20130205_231338.jpg I realize that the wireless network is not working. The Wireles manager dont find conections. Semms the driver is not loading. How can i fix that too! |
It appears that Linux is suddenly not seeing sda2 or sda3. That suggests that the way you connected the HDs is in error in which case I am out of my depth here. Maybe another Slacker knows the correct solution but some of the things I would try are as follows:
Can you still boot normally if you disconnect the other drives? If not then you might have corrupted sda. Can you boot from the original installation media with the other HDs connected? If so you could possibly do something like ls /dev/sd* to see what partitions are there. Each one has to be mount-ed before you can view the files. Can you boot from the original installation media if you disconnect the other drives? (I hope so). If nobody comes up with a better answer then try the 3 things I suggested and let me know the results. |
Answers for your questions!
Quote:
|
Quote:
One thing you could do is run fdisk -l and see how many partitions are bootable. If sdb1 is bootable and you only want sda1 to be bootable then run fdisk /dev/sdb and toggle the bootable partition. Assuming you have that right, it might be possible that when you added the other HDs, the lettering changed (sda became sdb or sdc or something). You could easily check that out by running ls /dev/sd* and for each partition you see, mount it on its own root partition. eg if you see /dev/sdb1 then issue the commands, mkdir /sdb1 and mount /dev/sdb1 /sdb1 etc. You can then see which partition you installed the Slackware on. If it turns out that your Slackware files are now on /sdc1 then the solution is to run chroot /sdc1, edit /etc/lilo.conf, change all references from sda to sdc then run lilo again. You will also need to edit /etc/fstab and change the root partition name there as well. (You can also assign each HD partition to somewhere in the directory-tree so that they will be mounted on bootup). |
Quote:
I will try fix the fstab today at nigth and will post the result here. |
Still with problem!
Quote:
Doesen't work. Its every thing ok with the fstab and lilo.conf. Let me put here more information. My Config. MB: M2N68-AM PLUS Proc: Phenom X3 720 BE MEM: 4 GB Kingston HD1: Samsung IDE 40 GB - Linux # /etc/sdd HD2: Samsung SATA 80 GB - Windows 8 /etc/sdc HD3: Samsung SATA 500 GB - No Sistem /etc/sda HD4: Samsung SATA 500 GB - No Sistem /etc/sdb Pendrv: Kingston 4 GB - Slackware Setup /etc/sde Just to clear: The slackware is installed on IDE 40 GB /etc/sdd. I instaled slackware with the other drivers disconected. If I connect the drivers, slack returns a stop error just like you see on the image. If I do not connect the drivers, slack boots fine. C'mon guys!!! I know there is somebare else here that knows how to fix!! |
Quote:
Just to double check everything, you should have done mount /dev/sdd1 /sdd1 chroot /sdd1 vi /etc/lilo.conf vi /etc/fstab lilo The relevant section of your lilo.conf should now read as Code:
# LILO configuration file Code:
/dev/sdd1 swap swap defaults 0 0 |
I was having a similar problem the other day. I got a new hdd to use as a backup and unplugged my main hdd to install slackware on the new backup hdd.
I could start my main hdd just fine and be in slackware and online like normal *IF* my new backup hdd was unplugged. If the new hdd was plugged in, I would get the same kernel panic you are getting. Look on the back of each hdd and remove the little jumper that used to be necessary on the old ide setups on MoBo's. Then make sure that each sata cable from the hdd's are plugged into the corresponding sata on the MoBo in order...for example: sda is plugged into sata1 on the mobo sdb into sata2 sdc into sata3 etc The combination (or maybe just one of those things I did) made it so I could plug the two hdd's in like I wanted and get back to my main hdd like normal. I then had a problem where the MoBo(?) was making my main hdd sdb and the backup hdd sda, so I booted into my main hdd and changed the fstab on the backup hdd to sdb. Next, when I was doing fdisk with the backup hdd I forgot to make the / partition bootable, so remember to toggle that too on each hdd. Lastly, I booted into my backup hdd and had to adduser...I'd forgotten that also and could see / from my main hdd but couldn't see /home because I kept forgetting to add a user, heh. Hopefully this is sorta kinda clear and maybe will help some. Your problem really is similar to the one I had the other day, you just have more hdd's. |
Solved at easy ways
Quote:
Here I am to put a end at this. I was weak and chose to solve the problem at the easiest way. I thought that i have knowledge enough to install slackware with my other drivers connected. At the end occurred every thing fine. The disk are mounted and i can see them at terminal and at Xfce. After look around about the network i put my wireless to work. I am having an other problem with my sound card. I have two of them, onboard and a cmedia pci. Slack is setting the onboard card to default one. I want to change this. I google it, but the solutions i have found does not work. I think is because of slack version. Look what I have here!! Code:
root@Ary-PC:/proc/asound# cat /proc/asound/cards How can i do that? PS. Sorry about that, but, on windows I can use one card for songs and the other one for mic. I do this because i have 2 huge speakers (20'' each), and if i put the mic at the same card i have feedback even with the mic volume lowest. Can i have the resource with slack? Well, I will put this problem in other post. Thanks everyone for help. I learn a lot. |
All times are GMT -5. The time now is 08:11 PM. |