HPT366 still linked to HPT374 after blacklist

[n3m3sis]

Binary package hint: hal-device-manager

I have a highpoint rocketraid 1540 card to which I have a 200gb seagate drive attached. Under the feisty livecd this drive is mounted like all the rest in my pc and I can access it normally. Under feisty and now under gutsy, I have to disconnect the drive or put it on port 3 or 4 for the pc to get past the ubuntu splash screen or else, the machine hangs at that point. Upon further investigation, by booting up from the fiesty cd again I have found that in the hardware manager there, there is only one instance of the module hpt374 with no reference to hpt366. In my gutsy installation however, there are two
instances of hpt374 in the hardware manager list, one of which resembles the same entry from the list when the feisty Livecd is loaded and another which makes reference to the linux driver hpt366. I have blacklisted this module and it is no longer loading, however I am still getting two hpt374 modules loading(as opposed to the single one in feisty) and one the modules has this reference to the hpt366 module which is not the one for my interface card.
Since this drive holds a lot of my data I have only two options at present (that I know of) if I wish to access that drive. One, on a temporary basis, is to boot up from the feisty cd again and again anytime I wish to access it, as it works perfectly from the live cd. The other is to change my motherboard to one that has more "native" sata ports as this current one has only two and this I am loathe to do at this present time.
Since the drive works on the feisty Livecd and only loads one HPT374 module, with no reference anywhere to the malfunctioning HPT366 module; I can only assume that there must be some bug in the system that is loading the hpt374 module twice! and linking it to the hpt366 driver in one instance.
below is the output from when I type dmesg in the terminal.......
  48.698824] NFORCE2: IDE controller at PCI slot 0000:00:09.0
[ 48.698849] NFORCE2: chipset revision 162
[ 48.698851] NFORCE2: not 100% native mode: will probe irqs later
[ 48.698855] NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround.
[ 48.698857] NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround.
[ 48.698863] NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
[ 48.698873] ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
[ 48.698885] ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
[ 48.698893] Probing IDE interface ide0...
[ 48.986396] hda: MAXTOR STM3160215A, ATA DISK drive
[ 49.210085] usb 2-2: new low speed USB device using ohci_hcd and address 2
[ 49.266156] hdb: IBM-DTLA-307030, ATA DISK drive
[ 49.322735] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[ 49.325552] Probing IDE interface ide1...
[ 49.428852] usb 2-2: configuration #1 chosen from 1 choice
[ 49.443924] usbcore: registered new interface driver hiddev
[ 49.450083] input: Dell Dell USB Mouse as /class/input/input2
[ 49.450209] input: USB HID v1.10 Mouse [Dell Dell USB Mouse] on usb-0000:00:02.1-2
[ 49.450223] usbcore: registered new interface driver usbhid
[ 49.450227] /build/buildd/linux-source-2.6.22-2.6.22/drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[ 50.061481] hdc: ASUS DRW-1608P3S, ATAPI CD/DVD-ROM drive
[ 50.733032] ide1 at 0x170-0x177,0x376 on irq 15
[ 50.737788] HPT374: IDE controller at PCI slot 0000:01:09.0
[ 50.737994] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
[ 50.738002] ACPI: PCI Interrupt 0000:01:09.0[A] -> Link [APC2] -> GSI 17 (level, high) -> IRQ 19
[ 50.738014] HPT374: chipset revision 7
[ 50.738029] HPT374: DPLL base: 48 MHz, f_CNT: 127, assuming 33 MHz PCI
[ 50.742964] HPT374: using 50 MHz DPLL clock
[ 50.743071] HPT374: 100% native mode on irq 19
[ 50.743083] ide2: BM-DMA at 0xa000-0xa007, BIOS settings: hde:pio, hdf:pio
[ 50.743106] ide3: BM-DMA at 0xa008-0xa00f, BIOS settings: hdg:pio, hdh:pio
[ 50.743153] ACPI: PCI Interrupt 0000:01:09.1[A] -> Link [APC2] -> GSI 17 (level, high) -> IRQ 19
[ 50.743171] HPT374: no clock data saved by BIOS
[ 50.870303] HPT374: DPLL base: 48 MHz, f_CNT: 122, assuming 33 MHz PCI
[ 50.875222] HPT374: using 50 MHz DPLL clock
[ 50.875329] HPT374: too many IDE interfaces, no room in table
[ 50.875333] HPT374: too many IDE interfaces, no room in table
[ 50.875335] HPT374: neither IDE port enabled (BIOS)
[ 50.875340] Probing IDE interface ide2...
[ 50.890030] hda: max request size: 512KiB
[ 50.934236] hda: 312581808 sectors (160041 MB) w/2048KiB Cache, CHS=19457/255/63, UDMA(100)
[ 50.958593] hda: cache flushes supported
[ 50.958645] hda: hda1 hda2 < hda5 >
[ 50.995248] hdb: max request size: 128KiB
[ 51.023211] hdb: 60036480 sectors (30738 MB) w/1916KiB Cache, CHS=59560/16/63, UDMA(100)
[ 51.023216] hdb: cache flushes not supported
[ 51.023237] hdb: hdb1 < hdb5 hdb6 hdb7 hdb8 hdb9 hdb10 >
[ 51.110502] hdc: ATAPI 40X DVD-ROM DVD-R-RAM CD-R/RW drive, 2000kB Cache, UDMA(66)
[ 51.110512] Uniform CD-ROM driver Revision: 3.20
[ 51.440193] Probing IDE interface ide3...
[ 52.008120] ACPI: PCI Interrupt Link [AP3C] enabled at IRQ 22
[ 52.008127] ACPI: PCI Interrupt 0000:02:01.0[A] -> Link [AP3C] -> GSI 22 (level, high) -> IRQ 16
[ 52.008134] 3c59x: Donald Becker and others.
[ 52.008140] 0000:02:01.0: 3Com PCI 3c920 Tornado at f883a000.
[ 52.031428] ACPI: PCI Interrupt Link [APCM] enabled at IRQ 21
[ 52.031434] ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [APCM] -> GSI 21 (level, high) -> IRQ 17
[ 52.031441] PCI: Setting latency timer of device 0000:00:0d.0 to 64
[ 52.083524] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17] MMIO=[e6082000-e60827ff] Max Packet=[2048] IR/IT contexts=[4/4]
[ 52.090025] sata_sil 0000:01:0b.0: version 2.2
[ 52.090266] ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
[ 52.090275] ACPI: PCI Interrupt 0000:01:0b.0[A] -> Link [APC3] -> GSI 18 (level, high) -> IRQ 20
[ 52.090731] scsi0 : sata_sil
[ 52.090939] scsi1 : sata_sil
[ 52.091077] ata1: SATA max UDMA/100 cmd 0xf884c080 ctl 0xf884c08a bmdma 0xf884c000 irq 20
[ 52.091082] ata2: SATA max UDMA/100 cmd 0xf884c0c0 ctl 0xf884c0ca bmdma 0xf884c008 irq 20
[ 52.611208] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 52.619757] ata1.00: ATA-6: ST3120023AS, 3.01, max UDMA/133
[ 52.619760] ata1.00: 234441648 sectors, multi 16: LBA
[ 52.619762] ata1.00: applying bridge limits
[ 52.619768] ata1.00: applying Seagate errata fix (mod15write workaround)
[ 52.635733] ata1.00: configured for UDMA/100
[ 53.102788] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 53.112526] ata2.00: ATA-6: WDC WD2000JD-00GBB0, 02.05D02, max UDMA/100
[ 53.112529] ata2.00: 390721968 sectors, multi 16: LBA48
[ 53.112531] ata2.00: applying bridge limits
[ 53.128533] ata2.00: configured for UDMA/100
[ 53.128649] scsi 0:0:0:0: Direct-Access ATA ST3120023AS 3.01 PQ: 0 ANSI: 5
[ 53.129003] scsi 1:0:0:0: Direct-Access ATA WDC WD2000JD-00G 02.0 PQ: 0 ANSI: 5
[ 53.139444] sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
[ 53.139460] sd 0:0:0:0: [sda] Write Protect is off
[ 53.139463] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 53.139478] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 53.139539] sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
[ 53.139548] sd 0:0:0:0: [sda] Write Protect is off
[ 53.139551] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 53.139564] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 53.139570] sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 >
[ 53.220523] sd 0:0:0:0: [sda] Attached SCSI disk
[ 53.220676] sd 1:0:0:0: [sdb] 390721968 512-byte hardware sectors (200050 MB)
[ 53.220686] sd 1:0:0:0: [sdb] Write Protect is off
[ 53.220689] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 53.220703] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 53.220743] sd 1:0:0:0: [sdb] 390721968 512-byte hardware sectors (200050 MB)
[ 53.220752] sd 1:0:0:0: [sdb] Write Protect is off
[ 53.220754] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 53.220769] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 53.220771] sdb: sdb1 < sdb5 sdb6 >
[ 53.264134] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 53.268378] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 53.268399] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 53.735118] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: <email address hidden>
[ 54.135075] Attempting manual resume
[ 54.135079] swsusp: Resume From Partition 3:5
[ 54.135081] PM: Checking swsusp image.
[ 54.162428] PM: Resume from disk failed.
[ 54.202654] kjournald starting. Commit interval 5 seconds
[ 54.202665] EXT3-fs: mounted filesystem with ordered data mode.
[ 60.721593] Linux agpgart interface v0.102 (c) Dave Jones
[ 60.722893] agpgart: Detected NVIDIA nForce2 chipset
[ 60.738652] agpgart: AGP aperture is 256M @ 0xc0000000
[ 61.463578] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 61.474099] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 61.502998] i2c-adapter i2c-0: nForce2 SMBus adapter at 0x5000
[ 61.503035] i2c-adapter i2c-1: nForce2 SMBus adapter at 0x5500
[ 62.065391] input: PC Speaker as /class/input/input3
[ 62.384989] parport_pc 00:09: reported by Plug and Play ACPI
[ 62.385050] parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
[ 62.617915] nvidia: module license 'NVIDIA' taints kernel.
[ 62.880182] ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
[ 62.880191] ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [APC4] -> GSI 19 (level, high) -> IRQ 21
[ 62.880599] NVRM: loading NVIDIA UNIX x86 Kernel Module 100.14.19 Wed Sep 12 14:12:24 PDT 2007
[ 63.126312] ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 20
[ 63.126318] ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [APCJ] -> GSI 20 (level, high) -> IRQ 18
[ 63.126342] PCI: Setting latency timer of device 0000:00:06.0 to 64
[ 63.449943] intel8x0_measure_ac97_clock: measured 52839 usecs
[ 63.449947] intel8x0: clocking to 47407
[ 63.987830] lp0: using parport0 (interrupt-driven).
[ 64.032214] Adding 3943916k swap on /dev/hda5. Priority:-1 extents:1 across:3943916k
[ 64.744389] EXT3 FS on hda1, internal journal

ProblemType: Bug
Architecture: i386
Date: Thu Nov 1 22:57:45 2007
DistroRelease: Ubuntu 7.10
NonfreeKernelModules: nvidia
Package: hal 0.5.9.1-6ubuntu5
PackageArchitecture: i386
SourcePackage: hal
Uname: Linux n3m3sis1-desktop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

[n3m3sis (nem2killu2)]

Ok, some additional information. It seems that I got it wrong in the previous post. The feisty live(DvD) does indeed have two entries for the HPT374 module, one of which is linked to the HPT366 driver. What is curious (not to mention damn infuriating as well), is that I can see the drive connected when I boot up from the Feisty Live(DvD) and I can access all the content. However, today I booted up from a Gutsy Live (CD) and although I can still see the drive, it would not mount. It gave me some error about improper shutdown or it still being in use. Also something about ntfs and a very concise option on how to force mount it (at my own risk) if I so wished.
So, in conclusion for this post.....
1.) The drive mounts and is able to be accessed normally from a Feisty Live (DvD).
2.)The drive is visible but is not mounted, neither can it be accessed on the Gutsy Live (Cd) without forcing (something I am not prepared to do at this juncture as the data held on it is to important to me to risk corruption). 3.)The drive causes a virgin Feisty installation to a IDE hard drive to freeze at the Ubuntu splash window, if it is connected to the Highpoint RocketRaid 1540 interface card at boot up (* please note that it will only cause a boot freeze if connected to ports 1 or 2 on the interface card - If connected to ports 3 or 4 it will boot normally, however the drive is not visible inside either ubuntu Feisty or Gutsy if the the OS is installed on a hard drive).

Has anyone got any idea why I can see and use the drive connected to port 1 or 2 on the Highpoint Rocket Raid 1540 SATA , when using the Feisty Live (DvD) but it will not work on either the Gutsy Live (Cd) or either Feisty or Gutsy installed on an IDE hard drive?

Please help me someone as this is causing me sleepless nights and I dont know enough about linux or Ubuntu yet to try compiling the source HPT374 driver from Highpoint, yet.

Nuff respect to all the good work all of you do both here and elsewhere, in promoting this wonderful (if sometimes frustrating) OS.

[Joel Oliver (joelol75)]

My bet would be on the fact that IDE devices are mapped as SATA and the kernel is compiled with CONFIG_IDE_MAX_HWIFS=4 and your card has 4 ports + the IDE hard drive and this might explain why you cannot see your first 2 ports (mapped over by the IDE channel?) I would place a good bet on it that if you change the value of CONFIG_IDE_MAX_HWIFS to "8" and recompile your kernel all your problems would automagically dissappear. This low value is a joke with todays hardware and even the server install, where you would expect to find a large # of drives installed in a single computer, defaults to only 4.

[Joel Oliver (joelol75)]

BTW, I have the exact same setup with some exceptions:

-- I use 4 SATA hard drives on my RocketRAID controller. (Same as yours) and yes.... It is normal for the HPT366 module to load. And yes, it is normal for 2 instances of this to load (1 for channels 1&2 and the 2nd for 3&4)

-- I use a regular ATA hard drive to boot from 80GB Maxtor (grub&os) and use EXT3 on this drive, the other hard drives use REISERFS (2 SATA Maxtors and 2 SATA Western Digital)

-- I use Dapper and that's why it still works, because my regular OS recognizes the 1st hard drive as HDA, my CDROM as HDC and my SATA's as HDE,HDG,HDK,HDI respectively. Gutsy would break this setup and I hope they fix it by Hardy! This is a "Mission Critical" box and I won't update it in a random fasion (I will dual boot or replace the primary hard drive on the regular IDE bus to check)

-- The above setting/recompile of the kernel should fix this. I would even consider raising this number. What harm would 12 be? Since all drives are SDA/SDxxx anymore.\

-- This may be a bug with some 'new' 374 trickery in gutsy, which this may not work? I know I use the same card as you in Dapper there's no reference to 374 at all, only 366.

-- If you use the above fix, lock (PIN in Debian terms) your kernel so it doesn't get updated!!! Or it will re-break your system on an update, unless they change/fix this by default.

-- They should change this by default.

-- If this doesn't help, please tell me, I am as interested in this problem as you.

It's not the easiest thing to recompile the kernel. And most debian/ubuntu instructions work using 'kpkg' not make/make install should work and should update the grub menu. The thing is pointing to the proper kernel image and initrd image in the grub menu. It could be tricky, just remember, you don't need to do the menuconfig or xconfig step, just edit the config.sys file, copy it to your usr/src dir and make sure it's used in your compile instructions (Which I believe needs a good symlink named 'linux' pointed to the the kernel source (All in /usr/src BTW)

Hope this helps.

[Joel Oliver (joelol75)]

I had just upgraded my server at my house with 2 more hard drives and my older desktop mobo that has 2 SATA plugs (NVIDIA chipset). Now with 7 hard drives I had to move the 4 SATAs on the RocketRAID 1640 out of the case and onto a diff power supply. All partitions are Reiserfs.

OK, so hda is an 80GB IDE drive that is only used for booting the OS (Dapper LTS up-to-date) with hda1 as /boot hda2 as / hda3 as /usr and hda4 as swap. So I added 2 more drives, 1 ATA and 1 SATA. The ATA drive was as slave on IDE#0 so it became hdb as it should. The SATA I plugged into the mobo's SATA was reconized as sda (So I figure if I add 1 more to the other plug it will be sdc). hde, hdg, hdk, and hdi are on the RocketRAID... For some reason they are not mapped to sd(x). I figure that when I upgrade to anythinhg later than Dapper everything will be a sd(x) drive and am not sure how it's going to map out. I will install Gutsy in hdb for testing to find out and post back. I jut think the Rocketraid is a poor choice for this stuff because of 2 BUGS or problems... Namely:

I don't need all this storage 'instant and always' so some sort of power saving is in order, but...

- hdparm -y /dev/hde (or any drive on the RocketRAID controller) I beleive puts it to sleep, but I can't always wake it back up with an access. I get timeout errors in dmesg. This will hang a reboot or shutdown even.

- sudo smartctl -d ata -a /dev/hde (or g,k,i) on RocketRAID drives report nothing. I see the latest smartmontools package supports the RocketRAID controllers with commands such as:
$ sudo smartctl -a -d hpt,1/1 /dev/hde

So I compiled them and... nope.... still doesn't work....

I will install a Gutsy instance somewhere on hdb and test it out and post back, but what I'm finding is that the RocketRAID may not be the best choice for what I need, namely getting these drives to sleep and not make the electric company happy.

I believe I will need to recompile Gutsy's kernel to make all these drives reconizable

I may have to just bite the bullet and purchase a different SATA card. I don't need any of this RAID stuff or SATA 2 (3.0Gb/sec) and even the RocketRAID is software RAID anyway. These cheap cards I see all over eBay with the Silicon Image 3114 chipset may work better. I'll post back with my Gutsy experiments.

# cat /etc/fstab

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda2 / reiserfs noatime 0 1
/dev/hdb1 /big/hdb1 reiserfs noatime 0 2
/dev/sda1 /big/sda1 reiserfs noatime 0 2
/dev/hde1 /big/hde1 reiserfs noatime 0 2
/dev/hdg1 /big/hdg1 reiserfs noatime 0 2
/dev/hdi1 /big/hdi1 reiserfs noatime 0 2
/dev/hdk1 /big/hdk1 reiserfs noatime 0 2
/dev/hda1 /boot ext2 noatime 0 2
/dev/hda3 /usr reiserfs noatime 0 2
/dev/hda4 none swap sw 0 ...