Slackware as 2nd os on 2nd hdd

chd_lad · 04-02-2008, 12:43 AM

hi
i have xp on a samsubg 160gb sata hdd
i am trying to install slackware 12 on my 2nd hdd. this is samsumg 80gb ide.
if i try to load the hugesmp.s kernel without all-generic-ide option, the 80gb hdd is not detected. however if i do use it the setup proceeds a little but when it reaches reading all physical media, it just sits there.

i installed slackware by removing my sata hdd and using all-generic-ide option.Now when i reconnect my sata hdd there is an warning dma interrupt timed out or something like that and the os starts.the boot is however very slow.

my sys config is
intel 965ry
core2 duo 2.4ghz
2gb ddr2 667mhz ram

please help.

onebuck · 04-02-2008, 08:55 AM

Hi,

Did you read the Slackware 12.0 CHANGES_AND_HINTS.TXT, UPGRADE.TXT and RELEASE_NOTES?

Quote:

excerpt form CHANGES_AND_HINTS.TXT;

It is recommended that you use one of the generic kernels (either the plain
kernel-generic or kernel-generic-smp) for daily use. For most systems,
you should use the generic SMP kernel if it will run, even if your system
is not SMP-capable. Some newer hardware needs the local APIC enabled in
the SMP kernel, and theoretically there should not be a performance penalty
with using the SMP-capable kernel on a uniprocessor machine, as the SMP
kernel tests for this and makes necessary adjustments. Furthermore, the
kernel sources shipped with Slackware 12.0 are configured for SMP usage,
so you won't have to modify those to build external out-of-tree modules
(such as NVidia or ATI proprietary drivers) if you use the SMP kernel.

If you are using one of the non-SMP kernels (huge.s or generic.s) and need
to compile third-party modules (such as the proprietary NVidia driver),
have a look in /extra/linux-2.6.21.5-nosmp-sdk/ for information on what
is needed to build them.

As stated earlier, it is recommended that you use one of the generic kernels
rather than the huge kernels; the huge kernel is primarily intended as
an "installer" and "emergency" kernel in case you forget to make an initrd.
However, if you do use one of the huge kernels, you will likely encounter
errors like this:
kobject_add failed for uhci_hcd with -EEXIST, don't try to register
These occur because the respective drivers are compiled statically into the
huge kernels but udev tries to load them anyway. These errors should be safe
to ignore, but if you really don't want them to appear, you can blacklist the
modules that try to load in /etc/modprobe.d/blacklist. However, make sure you
remove them from the blacklist if you ever decide to use the (recommended)
generic kernels.

chd_lad · 04-02-2008, 10:15 AM

hi onebuck,
i could not get what u were trying to suggest
the links u gave were about upgrading and i am not upgrading i am doing a fresh install.
i have never used linux before and this is my first attempt at installation of a distro
so could you please be more specific as to what i should do to solve this issue?
thanks

ps: i have tried huge.s and hugesmp.s without all-generic-ide option and none detect my ide hdd

onebuck · 04-02-2008, 02:19 PM

Hi,

Quote:

Originally Posted by chd_lad

hi onebuck,
i could not get what u were trying to suggest
the links u gave were about upgrading and i am not upgrading i am doing a fresh install.
i have never used linux before and this is my first attempt at installation of a distro
so could you please be more specific as to what i should do to solve this issue?
thanks

ps: i have tried huge.s and hugesmp.s without all-generic-ide option and none detect my ide hdd

The links to Slackware 12 reference text(s) are not just for upgrade. Read them again. The first part of the 'CHANGES AND Hints.txt' is specific to the upgrade from Slackware 11 with the rest of the information providing good hints. All three links that I provided give you valid information that can be used for a Slackware 12 install.

How do you have the 'IDE' drive configured? Do have space available to create the Linux partition?

After you boot the Slackware install cd1 do a 'Dmesg |grep -i IDE' and a 'lspci -vv'. Post the output in vbcode tags either code (#) or Quote that are at the top of a reply window.

If the IDE is recognized at boot then you should be able to create the Linux partition(s) that you need with 'fdisk /dev/hda'. You can use 'fdisk -l' to see the disk(s). If you have already shrunk the M$ XP partition on the drive then you should be good to go with the before mention 'fdisk /dev/hda'. Else you will have to use a partition tool to reduce the M$ Win/xp partition.

You should use one of the 'generic kernels'. Either the plain
kernel-generic or kernel-generic-smp for daily use. The kernel is selected during the 'setup' for Slackware install. If at boot you are having problems then try the other kernel.

Quote:

excerpt from CHANGES AND HINTS;

As stated earlier, it is recommended that you use one of the generic kernels
rather than the huge kernels; the huge kernel is primarily intended as
an "installer" and "emergency" kernel in case you forget to make an initrd.
However, if you do use one of the huge kernels, you will likely encounter
errors like this:
kobject_add failed for uhci_hcd with -EEXIST, don't try to register
These occur because the respective drivers are compiled statically into the
huge kernels but udev tries to load them anyway. These errors should be safe
to ignore, but if you really don't want them to appear, you can blacklist the
modules that try to load in /etc/modprobe.d/blacklist.

Note the underlined comments.

Provide a detail of the problems you are experiencing, Dmesg output relative to the problem and other error messages that you are getting. An exact system hardware configuration for the install.

I would suggest that you do get your system up and running before you add additional hardware. That way you don't have a lot to work out at once. Just handle the problems one at a time.

chd_lad · 04-03-2008, 09:12 AM

hi,
thanks for your quick reply.
i tried generic.s but kernel not found error
i cannot find the generic kernel u are talking about.
i tried looking for it in the dvd but its not present in the kernels directory.
am i doing something wrong here?
could you please tell me the command to use at the
boot:
prompt to start installation using the generic kernel?
yes my ide hdd has space,its a blank hdd without any partitions.
the xp installation is on sata hdd so do i need to compress that partition even if i want to install slackware on ide one?

onebuck · 04-03-2008, 02:26 PM

Hi,

The huge kernels are the Slackware 12.0 install kernels. You can use the default 'huge-smp' installer by pressing return. The other installer kernel is the 'huge'.

You still have not posted any real information as to the errors that you are experiencing. Post the un-edited error messages.

As for the kernel packages, look in '/slackware/a'.

You need to create the Linux partitions before the install. You can use 'fdisk /dev/hda' or 'cfdisk /dev/hda'. Change the device to your device if it is not '/dev/hda'. You will need to create a '/' and a 'swap'. For the '/' 5GB should be enough for a full install. The 'swap' should be at least equal or 2X the RAM.

If the XP is on the sda device then leave it alone. Btw, you would be shrinking the size of the 'XP' partition to allow the creation of another partition. You can have four primary partitions. But you can have one of the primaries as a extended partition then within the extended partition you can create additional partition.

Answer the query about the location during the 'setup'. If you don't answer properly then you will need to edit the '/etc/lilo.conf' after the install and then re-run 'lilo' as root to write the 'MBR' again.

You could reference 'Slackware® Basics' or 'Slackware® Essentials' to get some good help and background.

chd_lad · 04-04-2008, 03:08 PM

Quote:

Originally Posted by onebuck

Hi,

The huge kernels are the Slackware 12.0 install kernels. You can use the default 'huge-smp' installer by pressing return. The other installer kernel is the 'huge'.

You still have not posted any real information as to the errors that you are experiencing. Post the un-edited error messages.

As for the kernel packages, look in '/slackware/a'.

You need to create the Linux partitions before the install. You can use 'fdisk /dev/hda' or 'cfdisk /dev/hda'. Change the device to your device if it is not '/dev/hda'. You will need to create a '/' and a 'swap'. For the '/' 5GB should be enough for a full install. The 'swap' should be at least equal or 2X the RAM.

If the XP is on the sda device then leave it alone. Btw, you would be shrinking the size of the 'XP' partition to allow the creation of another partition. You can have four primary partitions. But you can have one of the primaries as a extended partition then within the extended partition you can create additional partition.

Answer the query about the location during the 'setup'. If you don't answer properly then you will need to edit the '/etc/lilo.conf' after the install and then re-run 'lilo' as root to write the 'MBR' again.

You could reference 'Slackware® Basics' or 'Slackware® Essentials' to get some good help and background.

there are no defined error messages. slackware wont detect my ide hdd without the all-generic-ide and when i use this option the boot process freezes at
Reading all physical volumes. This may take a minute or so.

or it boot after a long time and freezes when i type setup and press enter.

the pc does not hang as if i press any key it is typed on the screen but the installation does not proceed it just sits there.

and if this makes any difference:
is i use the normal hugesmp.s kernel the only problem is that my ide hdd is not detected the rest boot and setup work fine.

ps:
i read somewhere that it is the issue of the 965 chipset and is resolved using ide0=0x1018,0x1010 option but this does not seem to work for me

chd_lad · 04-05-2008, 03:43 PM

could not get it to work
read somewhere that this is a kernel issue with Jmicron ide
so installed ubuntu 7.10 without any problems
ll have wait till slack uses new kernel

anyways thanks for ur suggestions