LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation
User Name
Password
Slackware - Installation This forum is for the discussion of installation issues with Slackware.

Notices


Reply
  Search this Thread
Old 06-20-2004, 11:23 AM   #31
Keytwo
LQ Newbie
 
Registered: Jun 2004
Location: Italy
Distribution: Slackware
Posts: 3

Rep: Reputation: 0

Quote:
don't give up though!
No, no, i won't ^^

I know that free software community is the best programmers community, so I only have to wait (i'm not a good programmer).

Thank you bone
 
Old 06-20-2004, 07:00 PM   #32
mono
LQ Newbie
 
Registered: Jul 2002
Distribution: SuSE 9.0 and Slackware 9.1
Posts: 22

Rep: Reputation: 15
I don't have a floppy drive ATM. If I find some ISO editor, do you think I could add the satabare.i or the satavia.i kernels linked here, on to the Slack 10 RC1 CD and it would work?

This would be an interesting project as I've never tried to make a custom ISO. Ideas, pointers?
 
Old 06-20-2004, 10:53 PM   #33
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,899

Rep: Reputation: 579Reputation: 579Reputation: 579Reputation: 579Reputation: 579Reputation: 579
You should be able to mount the image and change what's in there. this should do it:
mount -o loop -t iso9660 /path/to/isoimage /some/mount/point
 
Old 06-21-2004, 06:58 AM   #34
mono
LQ Newbie
 
Registered: Jul 2002
Distribution: SuSE 9.0 and Slackware 9.1
Posts: 22

Rep: Reputation: 15
gnashley,

I know how to edit an ISO, but its the fact that I'm a noob when it comes to a custom ISO. What do I need to put on the new ISO, and where? The slack 10 CD has folders for each kernel so I can't merely copy the satabare.i disk image to the ISO's kernel folder. Need some pointers here.

Also, in the past, when I tried to add some things to the ISO, Slack install wouldn't boot because the checksum value was different. How can I tell it to skip checksum verification.

I think I need some help from some folks who have made their own custom ISO's in the past
 
Old 06-21-2004, 07:33 AM   #35
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,899

Rep: Reputation: 579Reputation: 579Reputation: 579Reputation: 579Reputation: 579Reputation: 579
if you want setup to find it copy the new kernel over bare.i/bzImage
 
Old 06-25-2004, 06:42 PM   #36
joef
Member
 
Registered: Jul 2003
Location: Bel Air, MD
Distribution: Slackware
Posts: 35

Rep: Reputation: 16
SDA vs HDE for SATA disks

Hi all. The 2.4 series kernels show SATA drives as sdX, but the 2.6 kernel shows those sames drives as hdX. My Seagate on a Via chipset shows up as /dev/sda under 2.4 kernels, but /dev/hde under 2.6 kernels (/dev/hda is a regular ata drive, and /dev/hdc is my ata DVD burner). It's because the 2.6 kernels apparently finally see things correctly and they don't have to hide SATA under SCSI (although the driver might still be under there when you're compiling). I think it's related to the way you don't have to use SCSI emulation with CD-RW drives and other ATA changes. In any event, it can be a bit confusing at first, but it's all the same in the end.

If anybody figures out that custom ISO thing, I'd be interested in it. I've been waiting since November to do a clean install of a new Slackware system on my SATA drive, and I still can't do it. I can install to the ATA drive and then do a dd of the whole drive, but that leaves me with funky formatting (and once it messed up lilo for some reason).

Thanks,

joe f.
 
Old 06-26-2004, 06:02 AM   #37
bonecrusher
Member
 
Registered: Mar 2004
Location: St. Louis, MO
Distribution: Ubuntu, Debian, Slack, RH, Gentoo
Posts: 207

Rep: Reputation: 30
Re: SDA vs HDE for SATA disks

Quote:
Originally posted by joef
Hi all. The 2.4 series kernels show SATA drives as sdX, but the 2.6 kernel shows those sames drives as hdX. My Seagate on a Via chipset shows up as /dev/sda under 2.4 kernels, but /dev/hde under 2.6 kernels (/dev/hda is a regular ata drive, and /dev/hdc is my ata DVD burner). It's because the 2.6 kernels apparently finally see things correctly and they don't have to hide SATA under SCSI (although the driver might still be under there when you're compiling). I think it's related to the way you don't have to use SCSI emulation with CD-RW drives and other ATA changes. In any event, it can be a bit confusing at first, but it's all the same in the end.

If anybody figures out that custom ISO thing, I'd be interested in it. I've been waiting since November to do a clean install of a new Slackware system on my SATA drive, and I still can't do it. I can install to the ATA drive and then do a dd of the whole drive, but that leaves me with funky formatting (and once it messed up lilo for some reason).

Thanks,

joe f.
Strange but it still boots up as SCSI on the 2.6.6 kernel I have. And doing a cursory look-over at the lib-ata code for the 2.4 kernel, your right, it would appear that it is SUPPOSE to use scsi. On the other hand, why would they do that and then change it in 2.6 kernel? I dunno for sure, but it seems like it should be scsi....and like I said it comes up scsi on my box...and I know for a fact that VIA compiles up as HDx on kernels when using the sata drivers. But you will have nothing but trouble with this if it comes up like that (or so I have read..see below). You may have forgotten to add 'scsi drive support' or do the thing (i forgot too in my kernel - satabare.i) under device drivers 'VIA82xxxxx' <---(I forget the rest but...) it needs to be compiled in for you to be able to use sata correctly. (At least I am guessing this..makes sense right?) You need to read the posts on http://www.linuxiso.org/ ...they talk about via chipsets and how they are screwed up on there...(In regards to trying to compile them for slackware/linux).... well it's 5:50am.. I gotta get busy with the day...uggg

-bc
 
Old 06-30-2004, 08:19 AM   #38
Slugg0
LQ Newbie
 
Registered: Jun 2004
Distribution: Slackware
Posts: 9

Rep: Reputation: 0
More SATAn drive woes!

I've found this thread to be very interesting, enough so to actually get me to try it one more time. So I got the 3 floppy files and used rawrite to prepare them. A bit of background first though. I use Boot It NG on my P4 2.8 Ghz 512 Mb RAM machine with the Promise SATA 150 controller and a Seagate 80 Gb SATA drive. I currently have several OSes installed and I'm writing this via MDK 9.1, which btw recognized my SATA setup and installed without so much as a hiccup. Hell even XP had to have drivers installed before it would recognize SATA! I also managed to get Fedora Core 2 installed, a bit more trouble than MDK, but it works okay with SATA. My old Multi-OS machine had Slack 9.1 installed on it and that is the distro I used the most. So I took the plunge, followed BC's excellent instruction and finally got CFDISK to recognize my SATA drive as SDA. I had previously used Boot It NG to setup the partitions and saw that CFDISK had my planned install drive recognized as SDA1 and the swap as SDA2. SDA1 was set to boot and so off we went. Did the complete install and things were fine. That is far as I got. Naturally when I rebooted it could not find LILO and it would not boot. Now I plan to completely reinstall Slackware 10 again, want to increase the partition size to 5 Gb instead of 3 Gb, but this time I want to do it right. Having used Linux for about 6 months, I know a lot about it, but I've still never compiled a kernel. I guess my question is, once I reinstall Slack 10 and get it to the point of a reboot, how do I go about recompiling the kernel so that it will recognize my SATA drive properly? BTW, I read the thread on recompiling a kernel for newbies, seems to be a fairly easy task. I just don't understand how to include the things I need such as networking and such. I welcome any and all comments...
 
Old 06-30-2004, 09:15 AM   #39
joef
Member
 
Registered: Jul 2003
Location: Bel Air, MD
Distribution: Slackware
Posts: 35

Rep: Reputation: 16
Getting the SATA drive to boot

Slugg0:

It's interesting that you got a version to install that won't even recognize the drive. I guess I should try what you did, because I have a good kernel compiled and if I could get to the installer I should be able to have it install my kernel instead of one of the ones on the installation disk.

Something you might want to try is to boot with another distro (rescue disk, Knoppix, whatever will let you see the SATA drive), then mount the SATA disk with Slackware still installed. Then you would do a chroot over to the SATA drive and compile and install the kernel from there. Then rerun lilo and make sure it sees your new kernel. Then it would be there upon reboot and you'd be golden.

I'm sure you'd like some more specific instructions, and I know where you can find them: www.crux.nu. I installed crux recently, and that's the installation process. You install the software and the kernel source from the CD, then chroot from the CD to the drive you just installed on, compile your kernel (it doesn't come with a compiled kernel), install lilo and reboot. You'll have to make a few mental changes as you go, but it should work. I know the latest Knoppix sees my SATA drive (seagate drive on a via chipset), and that CD is always nice to have around.

As for making sure you get a compile that will recognize your hardware, you just have to know what you have. Try to run lspci and that will report on all your PCI hardware. Then try an lsmod and that should tell you what modules you're running, which will tell you which ones you'll need to compile in. Knoppix also does excellent hardware detection. In my experience, it's best to comile all that stuff directly into the kernel, and not as modules (especially the SATA driver, which you'll probably find under the low-level scsi drivers section). Anyway, I have compiled probably 20 or 30 kernels, but I don't claim any expertise there. I get them to work, but still have occasional problems with modules.

Now that you've got me thinking along these lines, I might try something like that, but using using an iso/loopback installation, which I've read about somewhere.

Good luck.

joe f.
 
Old 06-30-2004, 09:39 AM   #40
Slugg0
LQ Newbie
 
Registered: Jun 2004
Distribution: Slackware
Posts: 9

Rep: Reputation: 0
Thanks for the info Joe, you've given me some things to think about and try. I know I can get to the currently installed Slack 10 partition from MDK 9.2 as I have been working on my fc2 partition this morning trying to get it working again. Seems after my Slack adventures yesterday, fc2 will not boot now! But anyway, I've never tried the chroot command so I'll have to read the site you suggested. If I can get that working I will probably still reinstall as I didn't realize that the full install of Slack 10 would take up the entire 3 Gb! BTW, if you have any ideas on why my fc2 won't boot I would certainly be interested to hear those. Here is what my grub.conf looks like from the fc2 partition just in case:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,0)
# kernel /boot/vmlinuz-version ro root=/dev/sda1
# initrd /boot/initrd-version.img
#boot=/dev/sda1
default=4
timeout=5
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title Fedora Core (2.6.6-1.435)
root (hd0,0)
kernel /boot/vmlinuz-2.6.6-1.435 ro root=LABEL=/ rhgb quiet
initrd /boot/initrd-2.6.6-1.435.img
title Fedora Core (2.6.6-1.427)
root (hd0,0)
kernel /boot/vmlinuz-2.6.6-1.427 ro root=LABEL=/ rhgb quiet
initrd /boot/initrd-2.6.6-1.427.img
title Fedora Core (2.6.5-1.358)
root (hd0,0)
kernel /boot/vmlinuz-2.6.5-1.358 ro root=/dev/sda1 rhgb quiet
initrd /boot/initrd-2.6.5-1.358.img
title Other
rootnoverify (hd0,3)
chainloader +1

Thanks much for your suggestions and help.
 
Old 07-06-2004, 02:40 PM   #41
cruzer
LQ Newbie
 
Registered: Jul 2004
Posts: 6

Rep: Reputation: 0
install bootdisks

This is for the person who posted the satabare.i bootdisk. I tried to contact you through pm and tried to send an email but none of that worked, so here is my question.

What did you mean by install.1 and install.2 bootdisks to be downloaded from the slackware website? Under the slackware 10 tree, I cannot find any such disks under /bootdisks.

Please advice.

Thanks.
 
Old 07-06-2004, 02:58 PM   #42
bonecrusher
Member
 
Registered: Mar 2004
Location: St. Louis, MO
Distribution: Ubuntu, Debian, Slack, RH, Gentoo
Posts: 207

Rep: Reputation: 30
Re: install bootdisks

Quote:
Originally posted by cruzer
This is for the person who posted the satabare.i bootdisk. I tried to contact you through pm and tried to send an email but none of that worked, so here is my question.

What did you mean by install.1 and install.2 bootdisks to be downloaded from the slackware website? Under the slackware 10 tree, I cannot find any such disks under /bootdisks.

Please advice.

Thanks.
I think you have to be a contributing member to use Private Messaging,, I could be wrong.. but anyway on to your question:


Go here for the install.1 and install .2 disk (use rawrite for these too!) :



Install.1 (rootdisk directory)
Install.2 (rootdisk directory)

These are located in any mirror site (I used Oregon State University's Slackware site..), the install disks are located in the 'rootdisk' directory. The kernels (bootdisk variety) are located in the bootdisk directory. But of course since you are probably using satabare.i that I compiled, you would opt for that instead and use the install.1 and 2 to get setup going. Anymore questions feel free to ask me on this thread.

-bc
 
Old 07-06-2004, 03:11 PM   #43
cruzer
LQ Newbie
 
Registered: Jul 2004
Posts: 6

Rep: Reputation: 0
Thanks for the reply bonecrusher.

So is the sequence like this?

Insert floppy 1 (install.1 disk)
Power up the computer

Swap floppy 3 (baresata.i)
boot prompt: baresata.i , HIT ENTER

If this is correct then you need the install.1 floppy disk only to get to the boot prompt of the installation. My cdrom boots just fine, so I guess I would not need it then. If I am wrong, please correct me.

Thanks a lot again.
 
Old 07-06-2004, 05:17 PM   #44
bonecrusher
Member
 
Registered: Mar 2004
Location: St. Louis, MO
Distribution: Ubuntu, Debian, Slack, RH, Gentoo
Posts: 207

Rep: Reputation: 30
Quote:
Originally posted by cruzer
Thanks for the reply bonecrusher.
So is the sequence like this?
Insert floppy 1 (install.1 disk)
Power up the computer
Swap floppy 3 (baresata.i)
boot prompt: baresata.i , HIT ENTER
If this is correct then you need the install.1 floppy disk only to get to the boot prompt of the installation. My cdrom boots just fine, so I guess I would not need it then. If I am wrong, please correct me.
Thanks a lot again.
Nope.

Ok. do this:

Turn on your computer. Before anything has time to boot pop the boot disk (satabare.i) into the floppy drive. You really aren't suppose to turn the computer on with a floppy already in the drive, but then again this probably is my old school thinking (think IBM XT '86 machines) and this was how I was taught back years ago. (A power surge could screw your floppy when you turn the computer on) Anyway boot up with the satabare.i disk (That you 'rawrited' ). Kind of watch as your boot disks prints all that info to the screen. (Once it prompts for a disk you can scroll back using the SHIFT-PG-UP/PG-DN key combo's...) You should see it recognize your Hard drive as a scsi device (/dev/sda) <- possibly...
If you don't get it finding your drive you may be doing something wrong or the chipset is one that it isn't recognizing correctly. Read through the threads that have been posted on here about SATA HD device problems.

When it asks you for the Install Disk #1 put it in. (Install.1 - which was written with rawrite also)

After it loads, it will then prompt you for the 3rd and last disk (install.2).
When this is done, you can then log into the system as 'root'.

At this point you will then partition your hard drive. It should be coming up as an SDx device. So run:

Code:
cfdisk /dev/sda
sda or whatever drive your using that is. (!)

If your not sure on how to use cfdisk, that is a whole other topic. Search around for info on it. I think you can proabbly find info on that on the slackware site??
Once your drive is partitioned and you have created a swap and got your swap turned on, you can then run "setup"
Setup presumes you have the slackware CD #1 in the drive. So you should have already inserted it.

Good luck!

-bc
 
Old 07-13-2004, 09:43 AM   #45
bonecrusher
Member
 
Registered: Mar 2004
Location: St. Louis, MO
Distribution: Ubuntu, Debian, Slack, RH, Gentoo
Posts: 207

Rep: Reputation: 30
SATA serial ata slackware ISO - INSTALL

Okay here is a link to the torrent:

(Same place the sata.i image is that is.. )

My folder with the torrent for the ISO

Ok.
Download the .torrent and then use it to connect to me (or others.. ) there are currently 3 leechers and just me seeding... So if you d/load this iso please please PLEASE stay on and upload (when it is done d/loading) at least 100MB . This would help us tremendously to get this iso out there and well seeded...

Thanks to everyone I am not able to thank personally for helping me out. This will help new users of slackware out quite a bit hopefully as more and more ppl are buying new computers with SATA drives installed!


Sincerely,

Brady Shea

(bc)

PS:
If you are not familar with what this is, it is the Slackware v10 CD-1 disk in ISO format. Use your favorite cd burner to burn it. (Use the option which 'burns image'. This CD should allow an install to any SATA hard drive as the original CD will not normally install to one of these drives. If you are a newbie and not familar with how to install slackware, I would recommend this CD if and only if you have (1) a sata hard drive, and (2) you are not familiar with how to use a boot disk. Speaking of boot disks, I have a boot disk at the link above, also. (sata.i) This is a much smaller download and would be much kinder to bandwidth. Anyway any questions address to me!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware 10.1 sata.i dosn't support my sata controller kryptobs2000 Slackware 7 12-05-2007 06:25 PM
slackware 10.0 -> sata cb951303 Slackware 3 09-07-2005 07:28 AM
slackware and sata.i muddlnx Slackware 33 10-18-2004 07:45 AM
Slackware and SATA Colosis Slackware - Installation 6 03-12-2004 11:02 AM
slackware 9.1 and SATA atarimike Slackware 4 02-26-2004 08:24 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation

All times are GMT -5. The time now is 02:17 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration