Find the answer to your Linux question:
Results 1 to 6 of 6
Hi folks, Mobo - ASUS A8N-VM AMD - Athlon64 3000+ HD - ATA 40G Installer - F8 dvd 86_64 Fresh installation Tried 2 days to install F8 w/o result. The ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux Guru
    Join Date
    Sep 2004
    Posts
    1,763

    F8 New Installation - Driver problem


    Hi folks,


    Mobo - ASUS A8N-VM
    AMD - Athlon64 3000+
    HD - ATA 40G
    Installer - F8 dvd 86_64
    Fresh installation


    Tried 2 days to install F8 w/o result. The PC hung on "load amd pata driver".


    So I "boot: linux noprobe" instead. But unable to find the driver for the ATA HD. On "Select driver" having tried follows;

    low-level driver for AMD PATA IDE (pata_amd)
    low-level driver for the Highpoint HPT366/368 (pata_htp3x3)

    Library module for ATA device (libata)
    low-level driver for Ali PATA (pata_ali)

    All w/o results. Please advise where can I download the appropriate driver? TIA


    B.R.
    satimis

  2. #2
    Administrator MikeTbob's Avatar
    Join Date
    Apr 2006
    Location
    Texas
    Posts
    7,864
    HIya satimis,
    Try using other boot options like
    Code:
    linux ide=nodma
    I do not respond to private messages asking for Linux help, Please keep it on the forums only.
    All new users please read this.** Forum FAQS. ** Adopt an unanswered post.

    I'd rather be lost at the lake than found at home.

  3. #3
    Linux Guru
    Join Date
    Sep 2004
    Posts
    1,763
    Quote Originally Posted by MikeTbob View Post
    HIya satimis,
    Try using other boot options like
    Code:
    linux ide=nodma
    Thanks for your advice.


    Sorry it doesn't work. Still the same, hangs on;
    Code:
    Loading SCSI driver
    
    Loading pata_amd driver...
    I can't find this option on F2


    satimis

  4. #4
    Linux Guru
    Join Date
    Sep 2004
    Posts
    1,763
    Hi folks,


    Finally I have F8 x86_64 installed on a SATA HD on the same box. "F8 x86_64" and "F8 i386" encountered the same problem unable to find the driver for ATA HD resulting in NO DRIVE found.

    I'm now updating F8. On booting the text scrolling shows a RED warning about ata driver. I try to search this warning on boot.log. But it is an empty file.

    # ls /var/log/
    Code:
    anaconda.log     boot.log  faillog  mcelog    samba           wtmp
    anaconda.syslog  btmp      gdm      messages  secure          Xorg.0.log
    anaconda.xlog    cron      httpd    ntpstats  setroubleshoot  Xorg.0.log.old
    audit            cups      lastlog  ppp       spooler         yum.log
    BackupPC         dirmngr   mail     prelink   tallylog
    bittorrent       dmesg     maillog  rpmpkgs   vbox

    Please advise which file I need to refer to? TIA


    B.R.
    satimis

  5. #5
    Administrator MikeTbob's Avatar
    Join Date
    Apr 2006
    Location
    Texas
    Posts
    7,864
    Quote Originally Posted by satimis View Post
    Hi folks,


    Finally I have F8 x86_64 installed on a SATA HD on the same box. "F8 x86_64" and "F8 i386" encountered the same problem unable to find the driver for ATA HD resulting in NO DRIVE found.

    I'm now updating F8. On booting the text scrolling shows a RED warning about ata driver. I try to search this warning on boot.log. But it is an empty file.

    # ls /var/log/
    Code:
    anaconda.log     boot.log  faillog  mcelog    samba           wtmp
    anaconda.syslog  btmp      gdm      messages  secure          Xorg.0.log
    anaconda.xlog    cron      httpd    ntpstats  setroubleshoot  Xorg.0.log.old
    audit            cups      lastlog  ppp       spooler         yum.log
    BackupPC         dirmngr   mail     prelink   tallylog
    bittorrent       dmesg     maillog  rpmpkgs   vbox

    Please advise which file I need to refer to? TIA


    B.R.
    satimis

    Glad you got it installed finally, sorry I couldn't be more helpful. You should be able to see your error messages in /vat/log/messages. Try using cat and grep
    And don't forget to login as root first.
    Code:
    cat /var/log/messages | grep ata
    If that doesn't produce any results then just try
    Code:
    cat /var/log/messages
    You'll have to scroll up to see all the messages
    You could also check the output of the dmesg command
    Code:
    dmesg
    I do not respond to private messages asking for Linux help, Please keep it on the forums only.
    All new users please read this.** Forum FAQS. ** Adopt an unanswered post.

    I'd rather be lost at the lake than found at home.

  6. #6
    Linux Guru
    Join Date
    Sep 2004
    Posts
    1,763
    Quote Originally Posted by MikeTbob View Post
    Glad you got it installed finally, sorry I couldn't be more helpful. You should be able to see your error messages in /vat/log/messages. Try using cat and grep
    And don't forget to login as root first.
    Code:
    cat /var/log/messages | grep ata
    If that doesn't produce any results then just try
    Code:
    cat /var/log/messages
    You'll have to scroll up to see all the messages
    You could also check the output of the dmesg command
    Code:
    dmesg
    Thanks for your advice.


    $ sudo cat /var/log/messages | grep ata
    Code:
    ....
    Jan 28 07:57:22 localhost kernel: scsi2 : pata_amd
    Jan 28 07:57:22 localhost kernel: scsi3 : pata_amd
    Jan 28 07:57:22 localhost kernel: ata3: PATA max UDMA/133 cmd 0x00000000000101f0 ctl 0x00000000000103f6 bmdma 0x000000000001ffa0 irq 14
    Jan 28 07:57:22 localhost kernel: ata4: PATA max UDMA/133 cmd 0x0000000000010170 ctl 0x0000000000010376 bmdma 0x000000000001ffa8 irq 15
    Jan 28 07:57:22 localhost kernel: ata4.00: ATAPI: _NEC DVD_RW ND-3570A, 1.11, max UDMA/33
    Jan 28 07:57:22 localhost kernel: ata4.01: ATAPI: SONY CD-ROM CDU5221,  0.35, ma
    .....
    I think the problem is here.

    $ dmesg
    Code:
    ......
    No NUMA configuration found
    Faking a node at 0000000000000000-000000003ffc0000
    Entering add_active_range(0, 0, 159) 0 entries of 3200 used
    Entering add_active_range(0, 256, 262080) 1 entries of 3200 used
    Bootmem setup node 0 0000000000000000-000000003ffc0000
    .....
    .....
    scsi0 : sata_nv
    scsi1 : sata_nv
    ata1: SATA max UDMA/133 cmd 0x000000000001e800 ctl 0x000000000001e482 bmdma 0x000000000001e000 irq 21
    ata2: SATA max UDMA/133 cmd 0x000000000001e400 ctl 0x000000000001e082 bmdma 0x000000000001e008 irq 21
    usb 2-3: new low speed USB device using ohci_hcd and address 2
    usb 2-3: configuration #1 chosen from 1 choice
    .....
    Now I don't have the ATA 133 HD connected on the PC. Won't it be the problem originating on the F8 DVD installer? Any idea to come this problem to install F8 on ATA 133 HD?


    A side question, Why boot.log is an empty file? TIA


    B.R.
    satimis
    Last edited by satimis; 01-28-2008 at 02:57 AM. Reason: correction

Posting Permissions

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