Slackware 14.0 64 bit install problems on HP DL380 G5
I'm trying to install slack 14.0 64 on an HP DL380 G5 with no success.
Problem is getting cciss module to load. Also some issues with GPT partition table on internal usb boot drive but have worked through most of those.
I've tried to install either cciss.ko or hpsa.ko on an existing i686 box with a full slack 14.0 64 install and get the same errors, depmod wont add them because they have no symbols. How do I fix these modules or where can I get new ones?
thanks, - dr -
Edit: Module issues were red herring. Problem was complicated due to previous VMWare ESXi install. Explained below.
- dr -
I don't know anything about this, but could you post the specific error?
According to the link above (the man for depmod)
As for the GPT partition problem, I had a lot of issues installing Slackware on my new laptop with a GPT partition, using gdisk finally got everything working for me without errors. Although I suggested this to someone else and they said it did not work for them. cgdisk is another GPT partitioning tool. Try them both if you still need to partition your drive.
The output of depmod -vvv 2>&1 | less provides amongst the pages of info, the following:
DEBUG: try kernel/drivers/block/cciss.ko (cciss)
DEBUG: add 0x8340730 kmod=0x83406f0, path=/lib/modules/3.2.29-smp/kernel/drivers/block/cciss.ko
DEBUG: ignoring /lib/modules/3.2.29-smp/kernel/drivers/block/cciss.ko: no symbols
DEBUG: ignoring /lib/modules/3.2.29-smp/kernel/drivers/block/DAC960.ko: no symbols
DEBUG: ignoring /lib/modules/3.2.29-smp/kernel/drivers/block/pktcdvd.ko: no symbols
DEBUG: ignoring /lib/modules/3.2.29-smp/kernel/drivers/block/osdblk.ko: no symbols
DEBUG: ignoring /lib/modules/3.2.29-smp/kernel/drivers/block/umem.ko: no symbols
DEBUG: ignoring /lib/modules/3.2.29-smp/kernel/drivers/block/nbd.ko: no symbols
DEBUG: ignoring /lib/modules/3.2.29-smp/kernel/drivers/block/cryptoloop.ko: no symbols
DEBUG: ignoring /lib/modules/3.2.29-smp/kernel/drivers/block/virtio_blk.ko: no symbols
DEBUG: ignoring /lib/modules/3.2.29-smp/kernel/drivers/block/sx8.ko: no symbols
It then proceeds to list all the missing symbols for each of the above modules, the list is too long to post here but here's a sample:
DEBUG: do dependencies of /lib/modules/3.2.29-smp/kernel/drivers/block/cciss.ko
DEBUG: /lib/modules/3.2.29-smp/kernel/drivers/block/cciss.ko depends on scsi_dma_map (unknown)
DEBUG: /lib/modules/3.2.29-smp/kernel/drivers/block/cciss.ko depends on pci_save_state (unknown)
DEBUG: /lib/modules/3.2.29-smp/kernel/drivers/block/cciss.ko depends on free_irq (unknown)
DEBUG: /lib/modules/3.2.29-smp/kernel/drivers/block/cciss.ko depends on dma_ops (unknown)
DEBUG: /lib/modules/3.2.29-smp/kernel/drivers/block/cciss.ko depends on blk_start_request (unknown)
DEBUG: /lib/modules/3.2.29-smp/kernel/drivers/block/cciss.ko depends on reset_devices (unknown)
So, it appears to me that all those modules in the module tree that are "ignored" due to lack of symbols, weren't compiled correctly for this kernel.
So far, everything I've found via google on compiling a kernel module is way more complicated than it was a number of kernels ago.
Would appreciate any help.
Thanks - dr -
So, I pull down the latest cciss tarball from http://cciss.sourceforge.net/ (version 4.6.28), build the module, exact same problem.
depmod 2>&1 | grep cciss | less still gives the same missing symbols.
modinfo shows pretty much the same stuff except the version is newer and the "in tree: y" is missing because I built it as an external module.
It just doesn't pickup the symbols.
- dr -
After a complete slack 14.0 64 install omitting lilo, and then boot up from the install dvd and attempting to mount /dev/cciss/c0d0p1 /mp (just a mount point in ramdisk) I get mount: unknown filesystem type 'VMFS_volume_member'. Initially (a year ago or so) I installed VMWare ESXi on this box. I thought I had completely removed it by repartitioning and reformatting the logical drive in the HP P400 Smart RAID.
So, I discovered here: http://serverfault.com/questions/372...ct-information
"For this case you need to erase more than 1 MiB to kill the old VMFS superblock:
dd if=/dev/zero of=/dev/sdb1 bs=4M count=1
According to the blkid sources, the VMFS volume member superblock is located at the 1024 KiB offset from the start of partition, and the VMFS filesystem superblock is at the 2048 KiB offset, so erase 4 MiB just to be sure."
So, I followed the instructions, went through repartitioning and reformatting the logical drive again and the install again.
When finished, I rebooted the install dvd and attempted to mount /dev/cciss/c0d0p1 on /mp and it mounted. Unfortunately, ... there was nothing on it except the directory "/lost+found".
So, I ran setup again and noticed that the partitions it found were /dev/cciss/c0d01 through /dev/cciss/c0d04 NOT /dev/cciss/c0d0p1 through /dev/cciss/c0d0p4.
Also, setup detected /dev/cciss/c0d02 as linux type (not swap type which it was) and informed me that I didn't create an fdisk swap partition.
I then looked at /dev/block or /dev/cciss (can't remember now where I found them) after booting again from the dvd and found that all the c0d0's were missing the "p" before the partition number.
I made symlinks from the c0d0's w/o the p's to c0d0's with the p's and for the first time setup saw the swap partition and actually installed everything on the drive.
Unfortunately, it listed all the partitions in fstab without the p's, so I had to edit that.
Anyway, I finally have it booting via the internal usb drive that is now using syslinux and mounting root=/dev/cciss/c0d0p1.
So, ... SOLVED! :)
- dr -
Here (14.0 32), 'modprobe cciss' and 'modprobe hpsa' give no warning though 'lsmod' don't show them. I guess this doesn't help you anyway as I don't have a HP Smart Array Controller :(
FYI though if you want to check that you get same output:
|All times are GMT -5. The time now is 09:47 PM.|