+ Responder ao Tópico



  1. eu uso linux e windows em uma mesma maquina, em dois HDs diferentes, o primario com linux e secundario com windows, porem na hora de iniciar, aperto para entrar no lilo, e da o seguinte erro....

    error 0x10

    então fica fazendo uma contagem de 5 segundos e não sai disso, se tento entrar no windows, a tela fica preta e não ocorre mais nada!

    a distro é um slack 10, com kernel série 2.4(infelizmente não sei a release), também não sei a versão do lilo!

    alguém tem uma solução?

    valeu!

  2. #2
    Gente, eu tenho este problema! Adicionando as opções "map" e "to" na parte do Windows ele aceita o boot! Alguém sabe me explicar que opções são estas?

    Abaixo o que eu encontrei no google, mas não me ajudou muito não, se alguém puder ajudar... Em negrito está o erro 0x10

    ---------------------------------------------------------------------------
    Disk error codes
    - - - - - - - -


    If the BIOS signals an error when LILO is trying to load a boot image,
    the
    respective error code is displayed. The following BIOS error codes are
    known:


    0x00 "Internal error". This code is generated by the sector read routine of the LILO boot loader whenever an internal inconsistency is detected. This might be caused by corrupt files. Try re-building the map file. Another possible cause for this error are attempts to access cylinders beyond 1024 while using the LINEAR option. See section "BIOS
    restrictions" for more details and for how to solve the problem.
    0x01 "Illegal command". This shouldn't happen, but if it does, it
    may
    indicate an attempt to access a disk which is not supported by the
    BIOS. See also "Warning: BIOS drive 0x<number> may not be
    accessible"
    in section "Warnings".
    0x02 "Address mark not found". This usually indicates a media
    problem.
    Try again several times.
    0x03 "Write-protected disk". This should only occur on write
    operations.
    0x04 "Sector not found". This typically indicates a geometry
    mismatch.
    If you're booting a raw-written disk image, verify whether it was
    created for disks with the same geometry as the one you're using. If
    you're booting from a SCSI disk or a large IDE disk, you should
    check,
    whether LILO has obtained correct geometry data from the kernel or
    whether the geometry definition corresponds to the real disk
    geometry.
    (See section "Disk geometry".) Removing COMPACT may help too. So may
    adding LINEAR.
    0x06 "Change line active". This should be a transient error. Try
    booting a second time.
    0x07 "Invalid initialization". The BIOS failed to properly
    initialize
    the disk controller. You should control the BIOS setup parameters. A
    warm boot might help too.
    0x08 "DMA overrun". This shouldn't happen. Try booting again.
    0x09 "DMA attempt across 64k boundary". This shouldn't happen. Try
    omitting the COMPACT option and report this problem to the author.
    0x0C "Invalid media". This shouldn't happen and might be caused by
    a
    media error. Try booting again.
    0x10 "CRC error". A media error has been detected. Try booting
    several
    times, running the map installer a second time (to put the map file
    at
    some other physical location or to write "good data" over the bad
    spot), mapping out the bad sectors/tracks and, if all else fails,
    replacing the media.
    0x11 "ECC correction successful". A read error occurred, but was
    corrected. LILO does not recognize this condition and aborts the
    load
    process anyway. A second load attempt should succeed.
    0x20 "Controller error". This shouldn't happen.
    0x40 "Seek failure". This might be a media problem. Try booting
    again.
    0x80 "Disk timeout". The disk or the drive isn't ready. Either the
    media is bad or the disk isn't spinning. If you're booting from a
    floppy, you might not have closed the drive door. Otherwise, trying
    to
    boot again might help.
    0xBB "BIOS error". This shouldn't happen. Try booting again. If the
    problem persists, removing the COMPACT option or adding/removing
    LINEAR
    might help.


    If the error occurred during a write operation, the error code (two hex
    digits) is prefixed with a "W". Although write errors don't affect the
    boot
    process, they might indicate a severe problem, because they usually
    imply
    that LILO has tried to write to an invalid location. If spurious write
    errors occur on a system, it might be a good idea to configure LILO to
    run
    read-only (see section "Build-time configuration").


    Generally, invalid geometry and attempts to use more than two disks
    without
    a very modern BIOS may yield misleading error codes. Please check
    carefully
    if /sbin/lilo doesn't emit any warnings. Then try using the LINEAR
    option
    (see section "Global options").
    -----------------------------------------------------------------------------



  3. #3
    staroffire
    Pelo que eu sei, geralmete o lilo dá pau quando ocorre erro na tabela de particionamento da MBR, por algum motivo o programa q fez o particionamento da unidade tá dando pau, aqui deu isso uma vez,foi só recriar as partićões com o CFDISK, e pronto, o lilo rodou tranquilo.....
    claro que quando eu recriei as particões eu formatei tudo.....






Tópicos Similares

  1. KERNEL PANIC no 2.6.12 "uname to mount root fs...."
    Por perilampo no fórum Servidores de Rede
    Respostas: 4
    Último Post: 14-07-2005, 19:11
  2. Servidor SAMBA - "Existe um nome duplicado na rede"
    Por Gustavo_DF no fórum Servidores de Rede
    Respostas: 1
    Último Post: 12-05-2005, 12:13
  3. quote site exec xxxx
    Por papaleguas no fórum Servidores de Rede
    Respostas: 0
    Último Post: 13-04-2004, 17:27
  4. quote / antivirus / spam / webmail
    Por no fórum Servidores de Rede
    Respostas: 1
    Último Post: 04-12-2003, 19:38
  5. Respostas: 0
    Último Post: 05-08-2003, 20:47

Visite: BR-Linux ·  VivaOLinux ·  Dicas-L