Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 14
Hello - Way too many posts for this same thing but this one should solve my problem. I have an INTEL 845PE BASED motherboard (It's in a Dell 4550 purchased ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux Newbie
    Join Date
    Jun 2003
    Posts
    160

    Linux and montherboard


    Hello -
    Way too many posts for this same thing but this one should solve my problem. I have an INTEL 845PE BASED motherboard (It's in a Dell 4550 purchased last May). I am having some IDE troubles with lagging communication between the drives and even across the same drive (i.e. burning a CD takes WAY TOO LONG and watching a movie from the cdROM skips and gets out of synch, copying data from CD to HD takes what seems like an eternity and you can actuall watch the drive work and then it pauses (so does the HD))

    It's NOT DMA - supposedly it's turned on - actually I turned it off and it was even worse!

    I've been told to recompile my kernel with support for my chipset but after searching around a bit - I can't seem to find a hardware compatability list that says this system or chipset is compatible... It seems odd to me that my chipset would'nt be supported but my TV card would...

    Intel 845PE 3.06G P4 533FSB 512MM RAM (2 DIMMS)

    Any help on this matter would be appreciated!

    Cole

  2. #2
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    Are you sure that it is the IDE controller chip that is called 845PE? Run /sbin/lspci and check for an IDE Interface.

  3. #3
    Linux Newbie
    Join Date
    Jun 2003
    Posts
    160

    /sbin/lspci readout

    cole@DrSpin:~> /sbin/lspci
    00:00.0 Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host Bridge (rev 11)
    00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP Bridge (rev 11)
    00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 01)
    00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 01)
    00:1d.2 USB Controller: Intel Corp. 82801DB USB (Hub #3) (rev 01)
    00:1d.7 USB Controller: Intel Corp. 82801DB USB EHCI Controller (rev 01)
    00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev 81)
    00:1f.0 ISA bridge: Intel Corp. 82801DB ISA Bridge (LPC) (rev 01)

    00:1f.1 IDE interface: Intel Corp. 82801DB ICH4 IDE (rev 01)

    00:1f.3 SMBus: Intel Corp. 82801DB SMBus (rev 01)
    01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX420] (rev a3)
    02:00.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
    02:00.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
    02:01.0 Communication controller: Conexant HSF 56k Data/Fax/Voice/Spkp Modem (rev 01)
    02:02.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a)
    02:02.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 0a)
    02:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

    apparently it's not 845 as I had thought - although that is the model of the host bridge... the 845 PE is the chipset which includes the above IDE controller...

    So where should I go to find a decent hardware database to search through???

    I've checked the SuSE database but I can't ever find a damn thing in there and with this one I had no luck also.

    Cole

  4. $spacer_open
    $spacer_close
  5. #4
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    From what I can see on google, there seems to be s ome trouble with that IDE interface. Do a "dmesg | grep -i ide" and see what it says.

  6. #5
    Linux Newbie
    Join Date
    Jun 2003
    Posts
    160

    dmesg

    dmesg | grep -i ide

    It returns NOTHING!! After checking a bit on Intel's website regarding the chipset all the numbers check out -

    00:1f.1 IDE interface: Intel Corp. 82801DB ICH4 IDE (rev 01)

    It seems that the key to this isn't so much the 82801DB, rather the ICH4 -> at least tht's what I gathered from reading on Intel's website regarding the chipset.... I couldn't, however, find a damn thing relating to compatibility...

    I also ran a dmesg by itself and it returned only a bunch of stuff relating to VMWARE's vmnet1 interface...SuSE-FW-ILLEGAL - TARGET but that wouldn't yield anything relating to the IDE chain

    PS - not sure if it matters but I did run the commands as root

  7. #6
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    dmesg can be run as any user, so that didn't really matter. The reason you don't get anything related to IDE is probably because of VMWARE. dmesg returns the kernel's log ring buffer, which is only 16 kB. Normal systems take a long time to fill that space, but if there is anything spitting out messages, then it will become full after a while. Try rebooting and check it as soon as it's done.
    By the way, what are you doing with VMWARE? You're not running Linux inside it, are you?

  8. #7
    Linux Newbie
    Join Date
    Jun 2003
    Posts
    160

    vmware

    I'm running VMWARE inside of LINUX so that I can run Windows... .I'm a graphic designer and web developer and LINUX just doesn't cut it when it comes to production. Crossover Office runs Photoshop well but there's still very minimal functionality with Dreamweaver and Flash seems to run OK... until these applications run more smoothly...

    LINUX is my native OS and Windows XP is installed inside VMWARE

    Cole

  9. #8
    Linux Newbie
    Join Date
    Jun 2003
    Posts
    160

    DMESG part 2

    cole@DrSpin:~> dmesg |grep ide
    ide-floppy driver 0.99.newide
    reiserfs: checking transaction log (ide0(3,1)) for (ide0(3,1))
    ide-scsi: hdd: unsupported command in request queue (0)
    ide-scsi: hdd: unsupported command in request queue (0)
    ide-scsi: hdd: unsupported command in request queue (0)
    ide-scsi: hdd: unsupported command in request queue (0)
    ide-scsi: hdd: unsupported command in request queue (0)
    ide-scsi: hdd: unsupported command in request queue (0)
    ide-scsi: hdd: unsupported command in request queue (0)
    ide-scsi: hdd: unsupported command in request queue (0)
    Linux video capture interface: v1.00
    bttv0: registered device video0


    now that could be a problem...

    Here's just a dmesg ->
    .
    .
    .
    ide-scsi: hdd: unsupported command in request queue (0)
    end_request: I/O error, dev 16:40 (hdd), sector 64
    ide-scsi: hdd: unsupported command in request queue (0)
    end_request: I/O error, dev 16:40 (hdd), sector 66
    ide-scsi: hdd: unsupported command in request queue (0)
    end_request: I/O error, dev 16:40 (hdd), sector 68
    ide-scsi: hdd: unsupported command in request queue (0)
    end_request: I/O error, dev 16:40 (hdd), sector 70
    ide-scsi: hdd: unsupported command in request queue (0)
    end_request: I/O error, dev 16:40 (hdd), sector 72
    ide-scsi: hdd: unsupported command in request queue (0)
    end_request: I/O error, dev 16:40 (hdd), sector 74
    ide-scsi: hdd: unsupported command in request queue (0)
    end_request: I/O error, dev 16:40 (hdd), sector 76
    ide-scsi: hdd: unsupported command in request queue (0)
    end_request: I/O error, dev 16:40 (hdd), sector 78
    .
    .
    .

  10. #9
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    That could indeed be a problem, but it doesn't seem like the entire problem, since it's only for SCSI emulation driver. It also seems as if these ide-scsi messages are already clogging the beginning of the log.
    Let's hope SuSE dumps the klog buffer to the syslog at boot. Run this and see what it says:
    Code:
    grep -i 'kernel:.*ide' /var/log/messages
    Does SuSE log kernel messages to /var/log/messages, btw.?

  11. #10
    Linux Newbie
    Join Date
    Jun 2003
    Posts
    160

    grep -i

    cole@DrSpin:~> grep -i 'kernel':.*ide /var/log/messages
    Jul 4 23:02:39 DrSpin kernel: eth0: Identified 8139 chip type 'RTL-8139C'
    Jul 4 23:04:29 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 4 23:04:29 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 4 23:04:29 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 4 23:04:29 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 4 23:04:29 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 4 23:04:29 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 4 23:04:29 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 4 23:04:29 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 4 23:04:33 DrSpin kernel: Linux video capture interface: v1.00
    Jul 4 23:04:33 DrSpin kernel: bttv0: registered device video0
    Jul 4 23:07:01 DrSpin kernel: eth0: Identified 8139 chip type 'RTL-8139C'
    Jul 4 23:07:44 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 4 23:07:44 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 4 23:07:44 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 4 23:07:44 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 4 23:07:44 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 4 23:07:44 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 4 23:07:44 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 4 23:07:44 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 4 23:07:47 DrSpin kernel: Linux video capture interface: v1.00
    Jul 4 23:07:48 DrSpin kernel: bttv0: registered device video0
    Jul 8 21:00:24 DrSpin kernel: eth0: Identified 8139 chip type 'RTL-8139C'
    Jul 8 21:01:38 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 8 21:01:38 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 8 21:01:38 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 8 21:01:38 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 8 21:01:38 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 8 21:01:38 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 8 21:01:38 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 8 21:01:38 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 8 21:01:42 DrSpin kernel: Linux video capture interface: v1.00
    Jul 8 21:01:42 DrSpin kernel: bttv0: registered device video0
    Jul 8 21:03:28 DrSpin kernel: eth0: Identified 8139 chip type 'RTL-8139C'
    Jul 8 21:04:13 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 8 21:04:13 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 8 21:04:13 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 8 21:04:13 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 8 21:04:13 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 8 21:04:13 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 8 21:04:13 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 8 21:04:13 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 8 21:04:16 DrSpin kernel: Linux video capture interface: v1.00
    Jul 8 21:04:16 DrSpin kernel: bttv0: registered device video0
    Jul 9 09:53:46 DrSpin kernel: eth0: Identified 8139 chip type 'RTL-8139C'
    Jul 9 09:54:33 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 9 09:54:33 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 9 09:54:33 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 9 09:54:33 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 9 09:54:33 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 9 09:54:33 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 9 09:54:33 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 9 09:54:33 DrSpin kernel: ide-scsi: hdd: unsupported command in request queue (0)
    Jul 9 09:54:36 DrSpin kernel: Linux video capture interface: v1.00
    Jul 9 09:54:37 DrSpin kernel: bttv0: registered device video0
    cole@DrSpin:~>

    Yes, If I remember correctly, SuSE does log to /var/log/messages

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •