https://bugzilla.novell.com/show_bug.cgi?id=248860 imotgm@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|imotgm@yahoo.com | ------- Comment #17 from imotgm@yahoo.com 2007-04-06 02:34 MST ------- "All the standard tools including hdparm and smartmontools already work with /dev/sdX Oh, really? [From SUSE 10.1] fatman:~ # hdparm -c1 -d1 -u1 /dev/hde /dev/hde: setting 32-bit IO_support flag to 1 setting unmaskirq to 1 (on) setting using_dma to 1 (on) IO_support = 1 (32-bit) unmaskirq = 1 (on) using_dma = 1 (on) fatman:~ # fatman:~ # hdparm -c1 -d1 -u1 /dev/hdg /dev/hdg: setting 32-bit IO_support flag to 1 setting unmaskirq to 1 (on) setting using_dma to 1 (on) IO_support = 1 (32-bit) unmaskirq = 1 (on) using_dma = 1 (on) fatman:~ # [From SUSE 10.2] fatman:~ # hdparm -c1 -d1 -u1 /dev/sda /dev/sda: setting 32-bit IO_support flag to 1 HDIO_SET_32BIT failed: Invalid argument setting unmaskirq to 1 (on) HDIO_SET_UNMASKINTR failed: Inappropriate ioctl for device setting using_dma to 1 (on) HDIO_SET_DMA failed: Inappropriate ioctl for device IO_support = 0 (default 16-bit) HDIO_GET_UNMASKINTR failed: Inappropriate ioctl for device HDIO_GET_DMA failed: Inappropriate ioctl for device fatman:~ # fatman:~ # hdparm -c1 -d1 -u1 /dev/sdb /dev/sdb: setting 32-bit IO_support flag to 1 HDIO_SET_32BIT failed: Invalid argument setting unmaskirq to 1 (on) HDIO_SET_UNMASKINTR failed: Inappropriate ioctl for device setting using_dma to 1 (on) HDIO_SET_DMA failed: Inappropriate ioctl for device IO_support = 0 (default 16-bit) HDIO_GET_UNMASKINTR failed: Inappropriate ioctl for device HDIO_GET_DMA failed: Inappropriate ioctl for device fatman:~ # Doesn't look that way from here. As you can see, "brokenmodules=it821x irqpoll" actually got this puppy to install. That's the last of the good news. The install froze twice, and had to be completed with an upgrade repair. When it finally rebooted, using the install CD to boot, (grub never got installed) it rebooted into text mode, with a garbled Yast screen that was all but unreadable. I finished the install from that, but only my long history with SUSE got me through. If I was a total newbie, it would have been too much. This is the worst installation experience I've ever had, with any Linux OS. (7 years with SUSE, 20+ distros tried, unknown total number of installations, but it's a lot) While running from the installation, and after, that first reboot, using, I would guess, the kernel from the install CD, I got some of the things you asked for, which I'm sending as attachments. Once I was able to boot from grub, without the install CD, the brokenmodules trick didn't work, and SUSE 10.2 loads the it821x module, goes into a near panic, sees /dev/hdg, but not /dev/hde. Using Yast, I was able to switch to the pata_it821x module, but it does a bit of a panic also, and ends up seeing neither of the drives. I'm including, as attachments, "boot.msg" for both the it821x, and the pata_it821x bootups, as well as the "messages" from the only boot so far, with the pata_it821x. The 10.2 system locked up solid, when I tried to read the messages, to the point that I had to do a hard reset, and booted back to 10.1, to retreive it. FYI, I have seperate /home partitions for 10.2, and 10.1, so there is no cross contamination betweem messages. As you seemed to think there might be a physical problem with the drive on hde, I switched the drive with a new 300GB Seagate. Smartctl has the same problem with it when connected to the it8212, as seen by SUSE. SUSE 10.2's version of it821x, and pata_it821x, doesn't like it any better than the 160GB Seagate it replaced. Booting to Mandriva 2007 gets no panic type messages during the boot process, and once booted recognizes the drive just fine, as /dev/hde. Reads, and writes, are normal, without issue, as the are on SUSE 10.1. As it made no difference whatever, in solving this particular problem, I've re-installed the 160GB Seagate, as it has links to it from the other existing OSs, including SUSE 10.1. Now, my question is, being as I've actually gotten 10.2 to install, however crappy that installation process went, do we continue with the it8212 problem here, or do I have to file another bug report? Jus because a work-around is found, it doesn't change the fact that there's something wrong with SUSE's modules for this controller, that does not exist in the modules used by other distros. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.