Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
10-24-2005, 11:04 PM
|
#1
|
Member
Registered: Aug 2004
Distribution: Slackware current
Posts: 250
Rep:
|
found problem now how to change from hda to sda
Ok i found the problem, under kernel 2.6 in order to get DMA i have to change everything from hd* to sd*. I know the option in the kernel, but what else needs to be changed, and how do i do it?
|
|
|
10-24-2005, 11:25 PM
|
#2
|
Senior Member
Registered: Oct 2005
Location: Horgau, Germany
Distribution: Manjaro KDE, Win 10
Posts: 2,199
Rep: 
|
Hello!
You have to change the mountpoints in /etc/fstab and /etc/mtab.
The path in the bootloader must be changed.
Greetings
Last edited by Keruskerfuerst; 10-24-2005 at 11:46 PM.
|
|
|
10-25-2005, 12:00 AM
|
#3
|
Member
Registered: Dec 2003
Distribution: Slackware
Posts: 325
Rep:
|
Since lilo won't boot unless it is also set to sda the best way would be to boot a 2.6 kernel live cd that has sata and then mount your hdd's and then chroot into it and update lilo. Slax is what I had to use for my laptop.
|
|
|
10-25-2005, 07:29 AM
|
#4
|
Member
Registered: Aug 2004
Distribution: Slackware current
Posts: 250
Original Poster
Rep:
|
ive never used slax, so what do i chroot to? And since you've done this before, could you give me a list of steps tp follow because i prefer that my laptop turns back on. It's my only computer. Thank you
|
|
|
10-25-2005, 07:41 AM
|
#5
|
Senior Member
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145
Rep:
|
Maybe it's supported by the sata.i kernel included with Slackware CD 1.
Boot with Slackware CD 1 and when you get the boot: prompt type: sata.i root=/dev/XXXX
Replace XXXX with either hdaX or sdaX where the X is the number of your root partition.
|
|
|
10-25-2005, 08:08 AM
|
#6
|
Member
Registered: Aug 2004
Distribution: Slackware current
Posts: 250
Original Poster
Rep:
|
I already have it install, and i dont want to reinstall it. I booted into slax and it does support it. I know what to compile into the kernel, i just dont know 100% what i'm supposed to do from there. And i will have to say that i hdparm -Tt /dev/sda and it was amazing i got over 15X speed boost
|
|
|
10-25-2005, 10:42 AM
|
#7
|
Member
Registered: Dec 2003
Distribution: Slackware
Posts: 325
Rep:
|
well actually you could use the slackware cd also. You just use the sata.i kernel as mentioned and when in the environment instead of installing you're going to create a mount point to mount your HDD. Whatever you call it, it doesn't matter. If you did multiple partitions don't worry, as long as you know the main partition its fine. If you don't remember a 'cat /proc/partitions' will list all HDD's and their partitions.
# mkdir /mnt/mount
# mount /dev/sda1 /mnt/mount
# mount -t proc proc /mnt/mount/proc
# chroot /mnt/mount
Now edit your /etc/fstab to reflect your correct partitions and edit /etc/lilo.conf changing ALL references to hda. If you use pico for your editor 'ctrl + w' will allow you to search for strings. After you edited those all you have to do now is update lilo.
# lilo
You should see no errors. If there is any warnings they usually don't mean anything as long as you see the Linux* or whatever your kernel name is show up in the output.
Another thing you might want to do just as a precautionary is run:
# lilo -M /dev/sda mbr
# lilo
All that first line does is reload lilo into the Master Boot Record. Just incase, you know.
After that just exit and reboot. Then you should see lilo come up all nice and pretty.
Chroot is your godsend if you screw up any type of configuration that causes the system not to boot. You chroot into the environment and it's just like you're in there so you can change and update anything necessary or revert to a working configuration.
Any problems just reply back. I work an odd shift so I might not reply quite immediately. Or someone else might be able to help, I'm sure.
|
|
|
10-25-2005, 01:26 PM
|
#8
|
Member
Registered: Aug 2004
Distribution: Slackware current
Posts: 250
Original Poster
Rep:
|
Thanks for all the help, but i did what you said and on the new boot, it says something about make a correct boot= and error somehting(8,3) and normally its (3,3)
|
|
|
10-25-2005, 01:39 PM
|
#9
|
Senior Member
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145
Rep:
|
Well, did you change the line that says boot=/dev/XXXX in lilo.conf?
|
|
|
10-25-2005, 03:33 PM
|
#10
|
Member
Registered: Aug 2004
Distribution: Slackware current
Posts: 250
Original Poster
Rep:
|
yep, it said hda i change it to sda. But the problem is that its looking for something(8,3) and it use to be something(3,3)
|
|
|
10-25-2005, 08:33 PM
|
#11
|
Member
Registered: Dec 2003
Distribution: Slackware
Posts: 325
Rep:
|
in your lilo.conf root = /dev/sda1 ?
for you kernel entry.
|
|
|
10-25-2005, 08:36 PM
|
#12
|
Member
Registered: Aug 2004
Distribution: Slackware current
Posts: 250
Original Poster
Rep:
|
no. it was hda so i made it sda. And it would be sda3 because sda1 is swap and sda2 is my spare partition
|
|
|
10-25-2005, 09:03 PM
|
#13
|
Member
Registered: Dec 2003
Distribution: Slackware
Posts: 325
Rep:
|
alright, sda3 then. I didn't know your partition table layout.
|
|
|
10-25-2005, 10:12 PM
|
#14
|
Member
Registered: Aug 2004
Distribution: Slackware current
Posts: 250
Original Poster
Rep:
|
why do i change it to sda3 when it use to be hda?
|
|
|
10-25-2005, 11:32 PM
|
#15
|
Member
Registered: Dec 2003
Distribution: Slackware
Posts: 325
Rep:
|
for the kernel entry?
image = /boot/2.6.13
root = /dev/sda1
label = 2.6.13-archck1
read-only
as the example from above shows root=/dev/sda1 because sda1 is my root partition that it will be booting off of.
|
|
|
All times are GMT -5. The time now is 09:03 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|