Debian GNU/Linux Sensing Δ 8th of September 2014 Ω 11:37 AM


ΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞ
yourDragonXi~ General About Debian
yourDragonXi~ Ports
yourDragonXi~ Downloading
yourDragonXi~ Downloading and Installing md5sum-32 for checksum
yourDragonXi~ Checking checksums for Debian AMD64
yourDragonXi~ Checking checksums for Debian i386
yourDragonXi~ Burning DVDs
yourDragonXi~ Verifying the GnuPG signature
yourDragonXi~ Starting with Debian GNU/Linux 4.0 r3 "Etch"
yourDragonXi~ Debian GNU/Linux Installation Guides
yourDragonXi~ History of Debian
yourDragonXi~ Developers of Debian
yourDragonXi~ Debian Policy Manual
yourDragonXi~ System Requirements
yourDragonXi~ Before Installing Debian GNU/Linux
yourDragonXi~ Booting from a CD-ROM
yourDragonXi~ Debian Installer Parameters
yourDragonXi~ Interpreting the Kernel Startup Messages
yourDragonXi~ Reporting Installation Problems
yourDragonXi~ Submitting Installation Reports
yourDragonXi~ Using the Debian Installer
yourDragonXi~ Introduction of Installer Components
yourDragonXi~ Using Individual Components
yourDragonXi~ Partitioning Your Disks
yourDragonXi~ Setting up the System
yourDragonXi~ Selecting and Installing Software
yourDragonXi~ Making Your System Bootable
yourDragonXi~ Finishing the Installation
yourDragonXi~ Booting Into Your New Debian System
yourDragonXi~ Shutting down the system
yourDragonXi~ Debian Packaging System
yourDragonXi~ Cron Job Management
yourDragonXi~ Further Reading and Information
yourDragonXi~ Desktop for Debian
yourDragonXi~ Package: pyqt-tools
yourDragonXi~ ASUS Motherboard
yourDragonXi~ BIOS Information
yourDragonXi~ Versions and Challenges (Linux Kernel etc)
yourDragonXi~ Hardware-summary of Installer
yourDragonXi~ Syslog of Installer
yourDragonXi~ Status of Installer
yourDragonXi~ Lsb-release of installer
yourDragonXi~ Install Report Template
yourDragonXi~ Windows XP Install in the same PC
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
yourDragonXi~ sense for Ξ
ξ
ξ
«Software Sensing
Θ

Θ
ΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞ
































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ General About Debian

»Debian

What is Debian?
ξ a free operating system (OS) for your computer
ξ is the set of basic programs and utilities that make your computer run
ξ uses the Linux kernel (the core of an operating system)
ξ most of the basic OS tools come from the GNU project; hence the name GNU/Linux

Debian GNU/Linux
ξ provides more than a pure OS: it comes with over 18733 packages,
ξ precompiled software bundled up in a nice format for easy installation on your machine.

Getting Started
ξ The latest stable release of Debian is 4.0.
ξ The last update to this release was made on February 17th, 2008.
ξ If you'd like to start using Debian, you can easily obtain a copy, and then follow the installation instructions to install it.
ξ To get help in using or setting up Debian, see our documentation and support pages.
ξ Users that speak languages other than English should check the international section.
ξ People who use systems other than Intel x86 should check the ports section.



select: ~[Σ] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Ports

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ports
»Debian Ports

ξ AMD64 has been an officially supported Debian architecture since the release of Debian 4.0 (etch).
ξ The port consists of a kernel for all AMD 64bit CPUs with AMD64 extension and all Intel CPUs with EM64T extension,
ξ and a common 64bit userspace.
ξ A complete 64bit userland
ξ The AMD64 port is thoroughly 64bit, allowing the user to benefit from all advantages this architecture has compared to i386:
* no memory segmentation in low and high memory
* up to 128TiB virtual address space per process (instead of 2GiB)
* 64TiB physical memory support instead of 4GiB (or 64GiB with the PAE extension)
* 16 general purpose registers in the CPU instead of 8
* gcc defaults to SSE2 math instead of 387 FPU »SSE2
* gcc omits frame-pointers by default at -O2
* compilation time optimization uses a common base for AMD64/EM64T instead of legacy i386 cruft
* memory pages are not executable by default


Native execution of legacy 32bit binaries is supported by the kernel, and core libraries are provided by the ia32-libs package.

Minimalistic AMD64 runtime support for i386
ξ The official i386 distribution actually includes minimalistic AMD64 support,
ξ consisting of a 64bit kernel, a toolchain able to create 64bit binaries and
ξ the amd64-libs package to run third-party amd64 binaries with native shared libraries.




select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Downloading

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Downloading AMD64
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ for processor AMD Athlon 64 Dual Core 4600 MHz

http://cdimage.debian.org/debian-cd/4.0_r3/amd64/iso-dvd/MD5SUMS
c711a394157b4f757ce8b7b00febe290 debian-40r3-amd64-DVD-1.iso
3e198ceb260f85ca62ec5264fa81ffe7 debian-40r3-amd64-DVD-2.iso
681917c695a421a0681a4dc209955e3d debian-40r3-amd64-DVD-3.iso
dbeb85916014f93e6f79fcb6ee31c2a9 debian-update-4.0r3-amd64-DVD-1.iso

http://cdimage.debian.org/debian-cd/4.0_r3/amd64/iso-dvd/MD5SUMS.sign
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBHufDefDt5cIjHwfcRAgxUAJ0cmlouobAOkHoLZj+S2r8JIkghrgCfW9n+
8MKXxwHzXvRgxez1QH0xbaU=
=oP8h
-----END PGP SIGNATURE-----

http://cdimage.debian.org/debian-cd/4.0_r3/amd64/iso-dvd/SHA1SUMS
de7adc961dfef93c7af717e89b3f22071dc4c798 debian-40r3-amd64-DVD-1.iso
bfc93c6e7769d05dd03ca106f0ca44aad18cf661 debian-40r3-amd64-DVD-2.iso
d28e1f5ab587498a8aa1886b5a79cc44d1d276a0 debian-40r3-amd64-DVD-3.iso
4366a04178dd5a6d367d755a32fc530aba13c85a debian-update-4.0r3-amd64-DVD-1.iso

http://cdimage.debian.org/debian-cd/4.0_r3/amd64/iso-dvd/SHA1SUMS.sign
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBHufDefDt5cIjHwfcRAnkUAKCLoFuLwN2DPp678XdgXg5jP7U7eQCeN6bf
bx0WKu02sCaOvHTjPT/l8e0=
=/RLE
-----END PGP SIGNATURE-----

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Downloading i386
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

http://cdimage.debian.org/debian-cd/4.0_r3/i386/iso-dvd/MD5SUMS
01b00aa7f59e680f68d5ae3e9b37b2b1 debian-40r3-i386-DVD-1.iso
24000b3a84e724f829f4ccf93643eb2b debian-40r3-i386-DVD-2.iso
d7f7a4f07c3d03ec08d2bbb6f0112a98 debian-40r3-i386-DVD-3.iso
efafb5df5315525a138f528082a63ff5 debian-update-4.0r3-i386-DVD-1.iso

http://cdimage.debian.org/debian-cd/4.0_r3/i386/iso-dvd/MD5SUMS.sign
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBHufDqfDt5cIjHwfcRAnhGAJ9dtI9QqjMg0+U8ofFBcQHG4zcQQQCeOknj
3ACgehCRfHA3F6o5pEw9hB0=
=OWpk
-----END PGP SIGNATURE-----

http://cdimage.debian.org/debian-cd/4.0_r3/i386/iso-dvd/SHA1SUMS
cf80686fe573524d4cf9980097a7ec482fb233cd debian-40r3-i386-DVD-1.iso
7649f04903695cb8db16dd89e91e22b43f42b779 debian-40r3-i386-DVD-2.iso
e7e7e079fdbc76926668f2eafb3fd84aaf903add debian-40r3-i386-DVD-3.iso
dfbdd8facad57b82b231ffaf495a4d291605ee21 debian-update-4.0r3-i386-DVD-1.iso

http://cdimage.debian.org/debian-cd/4.0_r3/i386/iso-dvd/SHA1SUMS.sign
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBHufDrfDt5cIjHwfcRAqSTAJ4ipZK6/i/8Vw2eCxG4dRFjC+a1oQCeModW
C1nxsOsdToZI0iZdYZd9kB4=
=ZCUz
-----END PGP SIGNATURE-----

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Miscellaneus for installation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

SATA
ξ SATA is fully supported in Etch, with the possible exception of the very latest hardware.

i386
ξ The netinst CD image includes only the generic i386 kernel

CD/DVD
ξ First of all, check that the MD5-sum of the ISO file you downloaded is correct;
ξ the md5sum for each of the ISOs is available in the same directory as the ISO download
ξ After booting the installer you can also check the CD-ROM:
ξ use the button to back up to the main menu and select the option to check the CD-ROM's integrity.

ξ If you are positive that the CD is correct, it could be that the CD-ROM is old and/or flaky when using DMA.
ξ You can try disabling DMA for the CD-ROM (by booting with "linux ide=nodma");
ξ unfortunately this boot option is currently broken (see bug 226057).

You can also disable DMA using the following procedure.
* switch to VT2 (using alt-F2)
*

cd /proc/ide/hdX (X varies depending on where your CD drive is connected)
*

cat settings
* check the current setting for using_dma
*

change it using the command echo "using_dma:0" >settings (or ":1")
* switch back to VT1 (using alt-F1)

A tightly folded IDE cable can also cause read errors, try repositioning the cable.

What do I do if I can no longer boot Windows after installing Debian?

amd64 CD does not boot
ξ The ia64 architecture is not the same as the amd64 architecture and you downloaded the wrong CD image




select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Downloading and Installing md5sum-32 for checksum

»Downloading and Installing md5sum-32
ξ downloaded to I:\Download\md5sum
ξ unzipped to K:\sw\md5sum




select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Checking checksums for Debian AMD64

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Checking checksums for Debian AMD64
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
working folder: K:\Download\DebianAMD64DVD
how to get there: k:\dvd.bat

ξ k:\dvd.bat takes to working folder and sets path to K:\sw\md5sum
ξ t1-t4.bat create checksums to a corresponding text files
ξ t(x) > dvd(x)_checksum.txt, where (x) = 1,2,3,4

ISO1: OK
ξ K:\Download\DebianAMD64DVD>md5sum -b debian-40r3-amd64-DVD-1.iso
ξ c711a394157b4f757ce8b7b00febe290 *debian-40r3-amd64-DVD-1.iso <--- dvd1_checksum.txt
ξ c711a394157b4f757ce8b7b00febe290 debian-40r3-amd64-DVD-1.iso <--- dvd1_serversum.txt

ISO2: OK
ξ 3e198ceb260f85ca62ec5264fa81ffe7 *debian-40r3-amd64-DVD-2.iso <--- dvd2_checksum.txt
ξ 3e198ceb260f85ca62ec5264fa81ffe7 debian-40r3-amd64-DVD-2.iso <--- dvd2_serversum.txt
ξ

ISO3: OK
ξ 681917c695a421a0681a4dc209955e3d *debian-40r3-amd64-DVD-3.iso <--- dvd3_checksum.txt
ξ 681917c695a421a0681a4dc209955e3d debian-40r3-amd64-DVD-3.iso <--- dvd3_serversum.txt

ISO4: OK
ξ dbeb85916014f93e6f79fcb6ee31c2a9 *debian-update-4.0r3-amd64-DVD-1.iso <--- dvd4_checksum.txt
ξ dbeb85916014f93e6f79fcb6ee31c2a9 debian-update-4.0r3-amd64-DVD-1.iso <--- dvd4_servesum.txt




select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Checking checksums for Debian i386

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Checking checksums for Debian i386
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
working folder: I:\Download\Debian

ξ k:\dvd.bat takes to working folder and sets path to K:\sw\md5sum
ξ t1-t4.bat create checksums to a corresponding text file
ξ t(x) > dvd(x)_checksum.txt, where (x) = 1,2,3,4

ISO1: OK
ξ 01b00aa7f59e680f68d5ae3e9b37b2b1 debian-40r3-i386-DVD-1.iso <--- dvd1_serversum.txt
ξ 01b00aa7f59e680f68d5ae3e9b37b2b1 *debian-40r3-i386-DVD-1.iso <--- dvd1_checksum.txt

ISO2: OK
ξ 24000b3a84e724f829f4ccf93643eb2b debian-40r3-i386-DVD-2.iso <--- dvd2_serversum.txt
ξ 24000b3a84e724f829f4ccf93643eb2b *debian-40r3-i386-DVD-2.iso <--- dvd2_checksum.txt

ISO3: OK
ξ d7f7a4f07c3d03ec08d2bbb6f0112a98 debian-40r3-i386-DVD-3.iso <--- dvd3_serversum.txt
ξ d7f7a4f07c3d03ec08d2bbb6f0112a98 *debian-40r3-i386-DVD-3.iso <--- dvd3_checksum.txt

ISO4: OK
ξ efafb5df5315525a138f528082a63ff5 debian-update-4.0r3-i386-DVD-1.iso <--- dvd4_serversum.txt
ξ efafb5df5315525a138f528082a63ff5 *debian-update-4.0r3-i386-DVD-1.iso <--- dvd41_checksum.txt




select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Burning DVDs

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Burning DVDs
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Nero
ξ just select image and there .iso format

Notes with Nero when tried a wrong path i.e. to burn an .iso as a file:
ξ you have to configure Nero and be careful NOT to ruin your DVD/RW device !!!
ξ debian-40r3-amd64-DVD-1: size 4.34 GB (4,666,236,928 bytes) <--- Windows XP
ξ Nero Express informs 4,450mb for file size
ξ Configure NERO / Expert Features / Enable DVD overburning / Maximum DVD size /4500mb < 4600 = NERO's maximum
ξ 1024 MB=GB, 1024 KB=1MB, 1024 * 1024 KB=GB
ξ Enable all supported recorder formats for the Image Recorder

Failed:
"C:\Program Files\NCH Swift Sound\ExpressBurn\expressburn.exe"
ξ Blu-ray disks = (ISO)
ξ ~Fully ISO compliant data CDs, DVDs, HD DVDs and Blu-ray disks with Joliet extension.
ξ *** error *** can NOT burn bigger than 4.00gb single files !!!!
ξ uninstalled and used Nero



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Verifying the GnuPG signature

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Verifying the GnuPG signature - Skipped
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ To ensure that the images were not only downloaded correctly, but are indeed official images,
ξ you also have to verify the GnuPG signature on the MD5SUMS files using the Debian GPG keyring.
ξ CD vendors are encouraged to do this.
»Index of /debian/doc




select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Starting with Debian GNU/Linux 4.0 r3 "Etch"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Starting with Debian GNU/Linux 4.0 r3 "Etch" - Official amd64 DVD Binary-1 20080217-12:13
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ plugin DVD #1



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Debian GNU/Linux Installation Guides

Getting the Newest Versions
»Debian “etch” Release Information



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ History of Debian

History of Debian /ref: the Debian pdf manual in K:\Download\DebianAMD64DVD\doc\manual\en /
ξ the Debian Project began in 1993
ξ Ian Murdock issued an open invitation to software developers to contribute to a complete and coherent software distribution based on the relatively new Linux kernel
ξ originally funded by the Free Software Foundation and
ξ influenced by the »GNU philosophy
ξ has grown over the years into an organization of around 1010 Debian Developers



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Developers of Debian

Developers of Debian
»Debian Social Contract
»http://www.debian.org/

»The Debian Free Software Guidelines (DFSG)

Free Redistribution
ξ the license of a Debian component may not restrict any party from selling or
ξ giving away the software as a component of an aggregate software distribution containing programs from several different sources
ξ the license may not require a royalty or other fee for such sale

Source Code
ξ the program must include source code, and
ξ must allow distribution in source code as well as compiled form

Derived Works
ξ the license must allow modifications and derived works, and
ξ must allow them to be distributed under the same terms as the license of the original software

Integrity of The Author's Source Code
ξ the license may restrict source-code from being distributed in modified form _only_
ξ if the license allows the distribution of patch files with the source code for the purpose of modifying the program at build time
ξ the license must explicitly permit distribution of software built from modified source code
ξ the license may require derived works to carry a different name or version number from the original software
ξ (This is a compromise. The Debian group encourages all authors not to restrict any files, source or binary, from being modified.)

No Discrimination Against Persons or Groups
ξ the license must not discriminate against any person or group of persons

No Discrimination Against Fields of Endeavor
ξ the license must not restrict anyone from making use of the program in a specific field of endeavor
ξ for example, it may not restrict the program from being used in a business, or from being used for genetic research

Distribution of License
ξ the rights attached to the program must apply to all to whom the program is redistributed
ξ without the need for execution of an additional license by those parties

License Must Not Be Specific to Debian
ξ the rights attached to the program must not depend on the program's being part of a Debian system
ξ if the program is extracted from Debian and used or distributed without Debian but otherwise within the terms of the program's license,
ξ all parties to whom the program is redistributed should have the same rights
ξ as those that are granted in conjunction with the Debian system

License Must Not Contaminate Other Software
ξ the license must not place restrictions on other software that is distributed along with the licensed software
ξ for example, the license must not insist that all other programs distributed on the same medium must be free software

Example Licenses
ξ GPL
ξ BSD
ξ Artistic



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Debian Policy Manual

»Debian Policy Manual
ξ describes the policy requirements for the Debian GNU/Linux distribution
ξ includes the structure and contents of the Debian archive and several design issues of the operating system, as well as
ξ technical requirements that each package must satisfy to be included in the distribution



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ System Requirements

System Requirements

Supported Hardware
ξ Debian does not impose hardware requirements beyond the requirements of the Linux kernel and the GNU tool-sets
ξ any architecture or platform to which the Linux kernel, libc, gcc, etc. have been ported, and
ξ for which a Debian port exists,
ξ can run Debian
»AMD64 architecture systems tested

Supported Architectures
ξ AMD64 & Intel EM64T / amd64 = Debian Designation

»Linux Hardware Compatibility HOWTO

»AMD Processors

Graphics Card Support
ξ Debian 4.0 ships with X.Org version 7.1

Multiple Cores and Processors
ξ multiprocessor support—also called “symmetric multiprocessing” or SMP—is available for this architecture
ξ the standard Debian 4.0 kernel image was compiled with SMP-alternatives support
ξ this means that the kernel will detect the number of processors or processor cores and
ξ will automatically deactivate SMP on uniprocessor systems

DVD
ξ ok; booting from DVD ok
»The Linux CD-ROM HOWTO; applies to DVD

Hard Disk
ξ Booting the installation system directly from a hard disk is another option (to DVD) for many architectures
ξ this will require some other operating system to load the installer onto the hard disk

USB Memory Stick
ξ using an USB memory stick for installing and (when necessary) for recovering the system
ξ this is also useful for small systems which have no room for unnecessary drives

Network
ξ can be used during the installation to retrieve files needed for the installation
ξ whether the network is used or not depends on the installation method you choose and your answers to certain questions
ξ that will be asked during the installation
ξ the installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP
ξ after the installation is completed, you can also configure your system to use ISDN and PPP
ξ you can also boot the installation system over the network
ξ diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option

Un*x or GNU system
ξ if you are running another Unix-like system, you could use it to install Debian GNU/Linux without using the debian-installer described in the rest of this manual
ξ this kind of install may be useful for users with otherwise unsupported hardware or on hosts which can’t afford downtime

Supported Storage Systems
ξ the Debian installation system includes support for floppies, IDE drives, IDE floppies,
ξ parallel port IDE devices, SCSI controllers and drives, USB, and FireWire
ξ the supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS

Peripherals and Other Hardware
ξ USB hardware generally works fine, only some USB keyboards may require additional configuration
»Linux Hardware Compatibility HOWTO

Windows-specific Hardware
ξ the manufacturers do not generally make the resources available to write a Linux driver
ξ devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors,
ξ often at real-time priority, and thus the CPU is not available to run your programs while it is driving these devices

Memory and Disk Space Requirements
ξ at least 48MB of memory and 500MB of hard disk space




select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Before Installing Debian GNU/Linux

Before Installing Debian GNU/Linux

About re-installations
ξ with Debian, a circumstance that will require a complete reinstallation of your system is very rare;
ξ perhaps mechanical failure of the hard disk would be the most common case
ξ under Debian GNU/Linux, it is much more likely that your OS can be repaired rather than replaced if things go wrong
ξ upgrades never require a wholesale installation; you can always upgrade in-place
ξ the programs are almost always compatible with successive OS releases
ξ if a new program version requires newer supporting software,
ξ the Debian packaging system ensures that all the necessary software is automatically identified and installed
ξ the point is, much effort has been put into avoiding the need for re-installation, so think of it as your very last option
ξ the installer is not designed to re-install over an existing system

A road map for the steps you will take during the installation process

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
01. Back up any existing data or documents on the hard disk where you plan to install
ξ motherboard ASUS DVD backed up
ξ boot floppy created

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
02. Gather information about your computer and any needed documentation, before starting the installation.
ξ using BIOS
ξ reading ASUS manuals
ξ analyzing hardware

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
03. Create partition-able space for Debian on your hard disk.
ξ use FreeDOS for this (strange that Linux as an OS can't do this) ?
ξ because it looks like Debian Linux can't handle nothing with this hardware, multi-boot considered !

»Pre-Partitioning for Multi-Boot Systems

Partitioning your disk
ξ simply refers to the act of breaking up your disk into sections
ξ each section is then independent of the others
ξ It's roughly equivalent to putting up walls inside a house; if you add furniture to one room it doesn't affect any other room.

If you already have an operating system on your system and want to stick Linux on the same disk
ξ you will need to repartition the disk
ξ Debian requires its own hard disk partitions
ξ It cannot be installed on Windows or MacOS partitions
ξ It may be able to share some partitions with other Linux systems
ξ At the very least you will need a dedicated partition for the Debian root

You can find information about your current partition setup
ξ by using a partitioning tool for your current operating system, such as Drive Setup, HD Toolkit, or MacTools or FreeDOS which comes with ASUS
ξ partitioning tools always provide a way to show existing partitions without making changes

In general
ξ changing a partition with a file system already on it will destroy any information there
ξ thus you should always make backups before doing any repartitioning
ξ Using the analogy of the house, you would probably want to move all the furniture out of the way before moving a wall or you risk destroying it.

If your computer has more than one hard disk
ξ you may want to dedicate one of the hard disks completely to Debian
ξ If so, you don't need to partition that disk before booting the installation system;
ξ the installer's included partitioning program can handle the job nicely <--- where is this installer ???

If your machine has only one hard disk
ξ and you would like to completely replace the current operating system with Debian GNU/Linux
ξ you also can wait to partition as part of the installation process (Section 6.3.2.1, “Partitioning Your Disks”),
ξ after you have booted the installation system
ξ However this only works if you plan to boot the installer system from tapes, CD-ROM or files on a connected machine <--- DVD here

Consider:
ξ if you boot from files placed on the hard disk <--- not this situation; Debian is in DVD
ξ and then partition that same hard disk within the installation system
ξ thus erasing the boot files, you'd better hope the installation is successful the first time around
ξ At the least in this case, you should have some alternate means of reviving your machine
ξ like the original system's installation tapes or CDs.

If your machine already has multiple partitions
ξ and enough space can be provided by deleting and replacing one or more of them,
ξ then you too can wait and use the Debian installer's partitioning program
ξ You should still read through the material below,
ξ because there may be special circumstances like the order of the existing partitions within the partition map,
ξ that force you to partition before installing anyway.

If none of the above apply
ξ you'll need to partition your hard disk before starting the installation to create partition-able space for Debian
ξ If some of the partitions will be owned by other operating systems,
ξ you should create those partitions using native operating system partitioning programs
ξ We recommend that you do not attempt to create partitions for Debian GNU/Linux using another operating system's tools <--- * warning *
ξ Instead, you should just create the native operating system's partitions you will want to retain <--- Debian

If you are going to install more than one operating system on the same machine
ξ you should install all other system(s) before proceeding with Linux installation
ξ Windows and other OS installations may destroy your ability to start Linux, or encourage you to reformat non-native partitions.
ξ You can recover from these actions or avoid them, but installing the native system first saves you trouble.

In order for OpenFirmware to automatically boot Debian GNU/Linux
ξ the Linux partitions should appear before all other partitions on the disk, especially MacOS boot partitions.
ξ This should be kept in mind when pre-partitioning;
ξ you should create a Linux placeholder partition to come before the other bootable partitions on the disk.
ξ (The small partitions dedicated to Apple disk drivers are not bootable.)
ξ You can delete the placeholder with the Linux partition tools later during the actual install, and replace it with Linux partitions.

If you currently have one hard disk with one partition (a common setup for desktop computers), and
you want to multi-boot the native operating system and Debian, you will need to:
1. Back up everything on the computer.
2. Boot from the native operating system installer media such as CD-ROM or tapes.
ξ When booting from a MacOS CD, hold the c key while booting to force the CD to become the active MacOS system.
3. Use the native partitioning tools to create native system partition(s).
ξ Leave either a place holder partition or free space for Debian GNU/Linux.
4. Install the native operating system on its new partition.
5. Boot back into the native system to verify everything's OK, and to download the Debian installer boot files.
6.
Boot the Debian installer to continue installing Debian.

»6.3.2.1. Partitioning Your Disks

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
C.1. Deciding on Debian Partitions and Sizes

At a bare minimum
ξ GNU/Linux needs one partition for itself.
ξ You can have a single partition containing the entire operating system, applications, and your personal files.

Swap
ξ Most people feel that a separate swap partition is also a necessity, although it's not strictly true.
ξ “Swap” is scratch space for an operating system, which allows the system to use disk storage as “virtual memory”.
ξ By putting swap on a separate partition, Linux can make much more efficient use of it.
ξ It is possible to force Linux to use a regular file as swap, but it is not recommended.

Most people choose to give GNU/Linux more than the minimum number of partitions, however.
ξ There are two reasons you might want to break up the file system into a number of smaller partitions.
ξ The first is for safety.
ξ If something happens to corrupt the file system, generally only one partition is affected.
ξ Thus, you only have to replace (from the backups you've been carefully keeping) a portion of your system.

At a bare minimum, you should consider creating what is commonly called a “root partition”
ξ this contains the most essential components of the system
ξ If any other partitions get corrupted, you can still boot into GNU/Linux to fix the system.
ξ This can save you the trouble of having to reinstall the system from scratch.

The second reason is generally more important in a business setting, but it really depends on your use of the machine
ξ For example, a mail server getting spammed with e-mail can easily fill a partition.
ξ If you made /var/mail a separate partition on the mail server, most of the system will remain working even if you get spammed.

The only real drawback to using more partitions
ξ is that it is often difficult to know in advance what your needs will be.
ξ If you make a partition too small then you will either have to reinstall the system or
ξ you will be constantly moving things around to make room in the undersized partition.
ξ On the other hand, if you make the partition too big, you will be wasting space that could be used elsewhere.
ξ Disk space is cheap nowadays, but why throw your money away?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
C.2. The Directory Tree

Debian GNU/Linux adheres to the Filesystem Hierarchy Standard for directory and file naming.
This standard allows users and software programs to predict the location of files and directories.

The root level directory
ξ is represented simply by the slash /

At the root level, all Debian systems include these directories:
bin Essential command binaries
boot Static files of the boot loader
dev Device files
etc Host-specific system configuration
home User home directories
lib Essential shared libraries and kernel modules
media Contains mount points for replaceable media
mnt Mount point for mounting a file system temporarily
proc Virtual directory for system information (2.4 and 2.6 kernels)
root Home directory for the root user
sbin Essential system binaries
sys Virtual directory for system information (2.6 kernels)
tmp Temporary files
usr Secondary hierarchy
var Variable data
srv Data for services provided by the system
opt Add-on application software packages

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
»C.3. Recommended Partitioning Scheme

For new users, personal Debian boxes, home systems, and other single-user setups
ξ a single / partition (plus swap) is probably the easiest, simplest way to go

However, if your partition is larger than around 6GB,
ξ choose ext3 as your partition type
ξ Ext2 partitions need periodic file system integrity checking, and this can cause delays during booting when the partition is large.

For multi-user systems or systems with lots of disk space
ξ it's best to put /usr, /var, /tmp, and /home each on their own partitions separate from the / partition
ξ You might need a separate /usr/local partition if you plan to install many programs that are not part of the Debian distribution.

If your machine will be a mail server
ξ you might need to make /var/mail a separate partition

Often, putting /tmp on its own partition
ξ for instance 20–50MB
ξ is a good idea

If you are setting up a server with lots of user accounts
ξ it's generally good to have a separate, large /home partition

In general
ξ the partitioning situation varies from computer to computer depending on its uses.

»HOWTO: Multi Disk System Tuning

With respect to the issue of swap partition size
ξ there are many views
ξ One rule of thumb which works well is to use as much swap as you have system memory.
ξ It also shouldn't be smaller than 16MB, in most cases
ξ Of course, there are exceptions to these rules.
ξ If you are trying to solve 10000 simultaneous equations on a machine with 256MB of memory, you may need a gigabyte (or more) of swap.

On 32-bit architectures (i386, m68k, 32-bit SPARC, and PowerPC)
ξ the maximum size of a swap partition is 2GB
ξ That should be enough for nearly any installation.
ξ However, if your swap requirements are this high,
ξ you should probably try to spread the swap across different disks (also called “spindles”) and,
ξ if possible, different SCSI or IDE channels
ξ The kernel will balance swap usage between multiple swap partitions, giving better performance.

As an example
ξ an older home machine might have 32MB of RAM and a 1.7GB IDE drive on /dev/hda.
ξ There might be a 500MB partition for another operating system on /dev/hda1,
ξ a 32MB swap partition on /dev/hda3 and
ξ about 1.2GB on /dev/hda2 as the Linux partition.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
»C.4. Device Names in Linux

Linux disks and partition names may be different from other operating systems.
You need to know the names that Linux uses when you create and mount partitions.
Here's the basic naming scheme:

The first floppy drive is named /dev/fd0

The second floppy drive is named /dev/fd1

The first SCSI disk (SCSI ID address-wise) is named /dev/sda

The second SCSI disk (address-wise) is named /dev/sdb etc

The first SCSI CD-ROM is named /dev/scd0, also known as /dev/sr0

The master disk on IDE primary controller is named /dev/hda

The slave disk on IDE primary controller is named /dev/hdb

The master and slave disks of the secondary controller can be called /dev/hdc and /dev/hdd, respectively
ξ newer IDE controllers can actually have two channels, effectively acting like two controllers.

The partitions on each disk are represented by appending a decimal number to the disk name:
ξ sda1 and sda2 represent the first and second partitions of the first SCSI disk drive in your system

Here is a real-life example
ξ Let's assume you have a system with
ξ 2 SCSI disks,
ξ one at SCSI address 2 and
ξ the other at SCSI address 4
ξ The first disk (at address 2) is then named sda, and the second sdb.
ξ If the sda drive has 3 partitions on it, these will be named sda1, sda2, and sda3.

The same applies to the sdb disk and its partitions.

Note that if you have two SCSI host bus adapters (i.e., controllers), the order of the drives can get confusing.
The best solution in this case is to watch the boot messages, assuming you know the drive models and/or capacities.

Unresolved
ξ how is SATA named by Linux ?
ξ BIOS IDE Master is DVD at the moment !
ξ BIOS SATA1 = WDC WD3200AAJS-22V
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Googling Linux SATA device names
»SATA by Linux Mafia
»Serial ATA (SATA) Linux hardware/driver status report
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
»Western Digital

Inside PC
ξ WD3200AAJS WD Caviar SE
ξ Model: WD3200AJS-22VWA0
ξ Date: 18 Mar 2008
ξ DCM: HHRNHT2MHN
ξ note: master7slave jumper not required for SATA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Inside ASUS DVD
ξ C:/NVIDIA/AHCI/XP/DISK1 and DISK2 <--- it looks like NVIDIA makes AHCI drivers for ASUS !
»inux-ata.org/driver-status.html#nvidia
Driver name: sata_nv
Summary:
ξ No TCQ/NCQ in early chipsets.
ξ NCQ support added in later chipsets.
ξ Looks like a PATA controller, but with full SATA control including hotplug and PM.

Update:
ξ NVIDIA has provided information (under NDA) that permits implementation of NCQ support, and
ξ a sample Linux implementation (patch) as well.
ξ Unfortunately, the patch needs debugging, and no one seems to have the time or motivation.

NOTE:
ξ Newer NVIDIA chipsets are AHCI, and use the ahci driver rather than the sata_nv driver !
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
»C.5. Debian Partitioning Programs

partman
ξ Recommended partitioning tool in Debian.
ξ This Swiss army knife can also resize partitions, create filesystems and assign them to the mountpoints.

cfdisk
ξ A simple-to-use, full-screen disk partitioner for the rest of us.
ξ Note that cfdisk doesn't understand FreeBSD partitions at all, and, again, device names may differ as a result.

mac-fdisk
ξ Mac-aware version of fdisk.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Locating above partitioning porgrams in Debian DVD
ξ E:\pool\main\p\partman-auto\partman-auto_68etch1_amd64.udeb
ξ Some core Debian packages are available as udebs (“micro debs”), and are typically used only for bootstrapping a Debian installation.
ξ Although these files use the “udeb” filename extension, they adhere to the same structure specification as ordinary deb files.
ξ However, unlike their deb counterparts, udeb packages contain only essential functional files.
ξ In particular, documentation files are normally omitted. udeb packages are not installable on a standard Debian system.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Googling Debian 4.0 r3 etch partitioning SATA

Status: install ok installed
Priority: standard
Section: debian-installer
Installed-Size: 672
Maintainer: Debian Install System Team
Version: 68etch1
Depends: cdebconf-udeb, di-utils, partman-base (>= 99), partman-basicfilesystems, partman-ext3
Description: Automatically partition storage devices (partman)
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

»A Debian Headache

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
»Just Linux Forum

happybunny
ξ the basic basic debian install is about 250megs
ξ but I would suggest 6-10gigs of space for the OS, etc, weather it be 1 partition or several.

My suggestion for a multi-boot system are
ξ 1 partition for OS1,
ξ 1 partition for OS2 (not really OS2, but you know what i mean),
ξ 1 swap partition (for both to share) plus
ξ a large partition that all OS's can read/write to share as data.
ξ That way, no matter what OS you boot, you can still access your data files.

Since the swap partition doesn't contain any data and will only be accessed by 1 OS at a time, all OS's can share the same swap partition.

I think people can get crazy with partitions at times.
On our major servers at work
ξ we seperate /home and /tmp and /var as needed

On a single user home machine, one partition per OS seems plenty to me.

A swap partition
ξ is as needed in a VMWare install as it is in the real world.
ξ Always remember that VMWare cannot break the rules of the OS.
ξ If you need a swap, you need a swap.
ξ However, you don't "NEED" a swap, which may explain why you don't see one.

The debian install
ξ will detect the existing partitions <--- mine did NOT detect !0
ξ and allow you to create new partitions on the free space !
ξ If you want a seperate partition for /tmp, you willl need to tell it so.

Also remember that you can only have 4 primary partitions.
ξ If you need more, you will need to make one of them extended.
ξ Most people use partition 4 to hold any additional extended partitions.
ξ Know that partition 4 will then not be usable as a partition in your system.
ξ Just something to keep in mind when mapping things out.

________________
m1ke_l
Desktop/XP1330m Laptop
Debian/Hardy
AMD 64bit dual core 4800+/Dual Core Intel
NVIDIA/NVIDIA
1.5Gig RAM/2Gig RAM
Boston, MA USA/Wondering
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
»Serial ATA Advanced Host Controller Interface (AHCI)
ξ Intel's manual
ξ does AMD/ASUS support this ok ?
ξ C:/NVIDIA/AHCI/XP/ <--- ASUS DVD <=> for XP ok, but how about Linux ?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Debian Lunux and SATA Drives
»debian-install-sata-disk
ξ XP SATA drives used !
ξ BIOS sata support is set to "enhanced", not "legacy"
ξ no problems with new kernel
ξ the debian linux kernel 2.4 installer detects my sata drive
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ Hard disk = 300GB <=> 10 drives, each ca. 30Gb C,D,E,F,G,H,I,J,K,L plus DVD
ξ C = Celsius
ξ D = Diesel
ξ E = Energy
ξ F = Fusion
ξ G = Gas
ξ H = Hydrogen
ξ I = Inertia
ξ J = Joule
ξ K = Kilowatt
ξ L = Lithium

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
04. Locate and/or download the installer software and any specialized driver files your machine requires
ξ except Debian CD users <--- this is strange; Debian itself detected NONE of the hardware !!!
ξ ASUS home page info refers to the fact that ASUS does NOT support Linux at all !
ξ ASUS BIOS gives possibility to make drive floppies to Windows XP and Vista, NOT to Linux !

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
05. Set up boot tapes/floppies/USB sticks, or place boot files (most Debian CD users can boot from one of the CDs.
ξ boot floppy created with FreeDOS which becomes with Debian DVD
ξ Debian DVD itself boots

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
06. Boot the installation system.
ξ ok with Debian DVD
ξ ok with boot floppy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
07. Select the installation language.
ξ ok

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
08. Activate the ethernet network connection, if available.
ξ Debian did NOT find LAN integrated on motherboard

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
09. Create and mount the partitions on which Debian will be installed.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10. Watch the automatic download/install/setup of the base system.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
11. Install a boot loader which can start up Debian GNU/Linux and/or your existing system.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
12. Load the newly installed system for the first time.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For AMD64 you have the option of using a graphical version of the installation system <--- where in DVD ?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The installer software
ξ detects hardware and loads appropriate drivers <--- NOT true with ASUS motherboard !
ξ uses dhcp-client to set up the network connection,
ξ runs debootstrap to install the base system packages, and
ξ runs tasksel to allow you to install certain additional software
ξ many more actors play smaller parts in this process
ξ debian-installer has completed its task when you load the new system for the first time

Back Up Your Existing Data!
ξ Before you start, make sure to back up every file that is now on your system.
ξ If this is the first time a non-native operating system has been installed on your computer,
ξ it’s quite likely you will need to re-partition your disk to make room for Debian GNU/Linux.
ξ Anytime you partition your disk, you run a risk of losing everything on the disk, no matter what program you use to do it !!!
ξ the programs used in installation are quite reliable and most have seen years of use;
ξ but they are also quite powerful and a false move can cost you
ξ even after backing up, be careful and think about your answers and actions
ξ two minutes of thinking can save hours of unnecessary work

If you are creating a multi-boot system
ξ make sure that you have the distribution media of any other present operating systems on hand
ξ especially if you repartition your boot drive,
ξ you might find that you have to reinstall your operating system’s boot loader, or
ξ in many cases the whole operating system itself and all files on the affected partitions !!!

Installation Manual
ξ installation document in plain ASCII, HTML or PDF format
ξ copied into another working PC to be used during installation

Linux Hardware Compatibility
»Linux Hardware Compatibility

BIOS setup
ξ the BIOS setup screens of your computer
ξ start your computer by pressing a combination of keys; often, it is the Delete key

Hard Drives
ξ how many
ξ their order on the system
ξ whether IDE or SCSI (SATA?)
ξ available free space
ξ partitions
ξ partitions where other operating systems are installed

Monitor
ξ Model and manufacturer
ξ Resolutions supported.
ξ Horizontal refresh rate.
ξ Vertical refresh rate.
ξ Color depth (number of colors) supported.
ξ Screen size.

Mouse
ξ Type: serial, PS/2, or USB
ξ Port
ξ Manufacturer
ξ Number of buttons

Network
ξ Model and manufacturer
ξ Type of adapter

Printer
ξ Model and manufacturer
ξ Printing resolutions supported

Video Card
ξ Model and manufacturer
ξ Video RAM available
ξ Resolutions and color depths supported (these should be checked against your monitor’s capabilities)

Hardware Compatibility
ξ Many brand name products work without trouble on Linux.
ξ Moreover, hardware support in Linux is improving daily.
ξ However, Linux still does not run as many different types of hardware as some operating systems.
ξ In particular, Linux usually cannot run hardware that requires a running version of Windows to work.

ξ Although some Windows-specific hardware can be made to run on Linux, doing so usually requires extra effort.
ξ In addition, Linux drivers for Windows-specific hardware are usually specific to one Linux kernel.
ξ Therefore, they can quickly become obsolete.
ξ So called win-modems are the most common type of this hardware.
ξ However, printers and other equipment may also be Windows-specific.

You can check hardware compatibility by:
• Checking manufacturers’ web sites for new drivers.
• Looking at web sites or manuals for information about emulation. Lesser known brands can sometimes
use the drivers or settings for better-known ones.
• Checking hardware compatibility lists for Linux on web sites dedicated to your architecture.
• Searching the Internet for other users’ experiences.

Network Settings

TCP/IP Properties Example
ξ obtain an IP address automatically
ξ obtain DNS server address automatically

Example of ADSL Modem ZyXEL P-660HW-D1
»ZyXEL

Pre-Partitioning for Multi-Boot Systems

If you already have an operating system on your system (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, . . . )
ξ and want to stick Linux on the same disk
ξ you will need to repartition the disk
ξ Debian requires its own hard disk partitions
ξ it cannot be installed on Windows or MacOS partitions
ξ it may be able to share some partitions with other Linux systems
ξ at the very least you will need a dedicated partition for the Debian root
ξ you can find information about your current partition setup by using a partitioning tool for your current operating system, such as fdisk or PartitionMagic
ξ partitioning tools always provide a way to show existing partitions without making changes

If your computer has more than one hard disk
ξ you may want to dedicate one of the hard disks completely to Debian
ξ if so, you don’t need to partition that disk before booting the installation system;
ξ the installer’s included partitioning program can handle the job nicely



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Booting from a CD-ROM

Booting from a CD-ROM
ξ The easiest route for most people will be to use a set of Debian CDs.
ξ If you have a CD set, and if your machine supports booting directly off the CD, great!
ξ Simply configure your system for booting off a CD with BIOS
ξ insert your CD
ξ reboot

The Boot Prompt
ξ When the installer boots, you should be presented with a friendly graphical screen showing the Debian logo and the boot prompt:
ξ Press F1 for help, or ENTER to boot:
ξ At the boot prompt you can either just press Enter to boot the installer with default options or enter a specific boot method and, optionally, boot parameters.
ξ Information on available boot methods and on boot parameters which might be useful can be found by pressing F2 through F8.

Boot Parameters
ξ Linux kernel parameters which are generally used to make sure that peripherals are dealt with properly
ξ for the most part, the kernel can auto-detect information about your peripherals
ξ however, in some cases you’ll have to help the kernel a bit
ξ if this is the first time you’re booting the system, try the default boot parameters (i.e., don’t try setting parameters) and see if it works correctly
ξ It probably will.
ξ If not, you can reboot later and look for any special parameters that inform the system about your hardware.

»Information on boot parameters
ξ this section contains only a sketch of the most salient parameters
ξ some common gotchas are included below in Section 5.3
ξ when the kernel boots, a message
ξ Memory:availk/totalk available
ξ should be emitted early in the process
ξ total should match the total amount of RAM, in kilobytes.

If this doesn’t match the actual amount of RAM you have installed
ξ you need to use the mem=ram parameter, where ram is set to the amount of memory, suffixed with “k” for kilobytes, or “m” for megabytes
ξ for example, both mem=65536k and mem=64m mean 64MB of RAM
ξ If you are booting with a serial console, generally the kernel will autodetect this
ξ If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console,
ξ you may have to pass the console=device argument to the kernel, where device is your serial device, which is usually something like ttyS0



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Debian Installer Parameters

Debian Installer Parameters

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
debconf/priority (priority)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The default installation uses priority=high
ξ both high and critical priority messages are shown, but medium and low priority messages are skipped
ξ If problems are encountered, the installer adjusts the priority as needed

If you add priority=medium as boot parameter
ξ you will be shown the installation menu and gain more control over the installation

When priority=low is used
ξ all messages are shown
ξ this is equivalent to the expert boot method

With priority=critical,
ξ the installation system will display only critical messages and try to do the right thing without fuss


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DEBIAN_FRONTEND
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ controls the type of user interface used for the installer
ξ the current possible parameter settings are:
• DEBIAN_FRONTEND=noninteractive
• DEBIAN_FRONTEND=text
• DEBIAN_FRONTEND=newt
• DEBIAN_FRONTEND=gtk

The default frontend is DEBIAN_FRONTEND=newt.

DEBIAN_FRONTEND=text may be preferable for serial console installs.

Generally, only the newt frontend is available on default install media.
On architectures that support it, the graphical installer uses the gtk frontend.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BOOT_DEBUG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ Setting this boot parameter to 2 will cause the installer’s boot process to be verbosely logged.
ξ Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)

BOOT_DEBUG=0
ξ This is the default.

BOOT_DEBUG=1
ξ More verbose than usual.

BOOT_DEBUG=2
ξ Lots of debugging information.

BOOT_DEBUG=3
ξ Shells are run at various points in the boot process to allow detailed debugging.
ξ Exit the shell to continue the boot

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
INSTALL_MEDIA_DEV
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ The value of the parameter is the path to the device to load the Debian installer from
ξ for example, INSTALL_MEDIA_DEV=/dev/floppy/0
ξ The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
debian-installer/framebuffer (fb)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ Some architectures use the kernel framebuffer to offer installation in a number of languages.
ξ If framebuffer causes a problem on your system you can disable the feature by the parameter fb=false.
ξ Problem symptoms are error messages about bterm or bogl, a blank screen,
ξ or a freeze within a few minutes after starting the install
ξ The video=vga16:off argument may also be used to disable the kernel’s use of the framebuffer.
ξ Such problems have been reported on a Dell Inspiron with Mobile Radeon card.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
debian-installer/theme (theme)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ A theme determines how the user interface of the installer looks (colors, icons, etc.).
ξ What themes are available differs per frontend.
ξ Currently both the newt and gtk frontends only have a “dark” theme that was designed for visually impaired users.
ξ Set the theme by booting with theme=dark.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
debian-installer/probe/usb
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ Set to false to prevent probing for USB on boot, if that causes problems.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
netcfg/disable_dhcp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ By default, the debian-installer automatically probes for network configuration via DHCP.
ξ If the probe succeeds, you won’t have a chance to review and change the obtained settings.
ξ You can get to the manual network setup only in case the DHCP probe fails.
ξ If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers,
ξ you can use the parameter netcfg/disable_dhcp=true to prevent configuring the network with DHCP and to enter the information manually.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
hw-detect/start_pcmcia
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ Set to false to prevent starting PCMCIA services, if that causes problems.
ξ Some laptops are well known for this misbehavior.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
preseed/url (url)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ Specify the url to a preconfiguration file to download and use for automating the install

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
preseed/file (file)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ Specify the path to a preconfiguration file to load for automating the install.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
preseed/interactive
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ Set to true to display questions even if they have been preseeded.
ξ Can be useful for testing or debugging a preconfiguration file.
ξ Note that this will have no effect on parameters that are passed as boot parameters, but for those a special syntax can be used.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
auto-install/enable (auto)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ Delay questions that are normally asked before preseeding is possible until after the network is configured

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cdrom-detect/eject
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ By default, before rebooting, debian-installer automatically ejects the optical media used during the installation.
ξ This can be unnecessary if the system does not automatically boot off the CD.
ξ In some cases it may even be undesirable, for example if the optical drive cannot reinsert the media itself and
ξ the user is not there to do it manually.
ξ Many slot loading, slim-line, and caddy style drives cannot reload media automatically.
ξ Set to false to disable automatic ejection, and be aware that you may need to ensure
ξ that the system does not automatically boot from the optical drive after the initial installation.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
debian-installer/allow_unauthenticated
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ By default the installer requires that repositories be authenticated using a known gpg key
ξ Set to true to disable that authentication.
ξ Warning: insecure, not recommended.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mouse/left
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ For the gtk frontend (graphical installer), users can switch the mouse to left-handed operation by setting this parameter to true.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
directfb/hw-accel
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ For the gtk frontend (graphical installer), hardware acceleration in directfb is disabled by default.
ξ To enable it, set this parameter to true when booting the installer.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
rescue/enable
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ξ Set to true to enter rescue mode rather than performing a normal installation



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Interpreting the Kernel Startup Messages

Interpreting the Kernel Startup Messages
ξ During the boot sequence, you may see many messages in the form can’t find something, or
ξ something not present, can’t initialize something, or even this driver release depends on something
ξ Most of these messages are harmless.
ξ You see them because the kernel for the installation system is built to run on computers with many different peripheral devices.
ξ Obviously, no one computer will have every possible peripheral device,
ξ so the operating system may emit a few complaints while it looks for peripherals you don’t own.
ξ You may also see the system pause for a while.
ξ This happens when it is waiting for a device to respond, and that device is not present on your system.
ξ If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Reporting Installation Problems

Reporting Installation Problems
ξ If you get through the initial boot phase but cannot complete the install,
ξ the menu option Save debug logs may be helpful
ξ It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser.
ξ This information may provide clues as to what went wrong and how to fix it.
ξ If you are submitting a bug report, you may want to attach this information to the bug report.
ξ Other pertinent installation messages may be found in /var/log/ during the installation, and
ξ /var/log/installer/ after the computer has been booted into the installed system.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Googling problem reading data from the CD-ROM Debian 4.0 r3 etch

»having problems installing Etch



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Submitting Installation Reports

Submitting Installation Reports
ξ If you still have problems, submit an installation report
ξ Note that installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list.
ξ Make sure that you use an e-mail address that you do not mind being made public.

If you have a working Debian system
ξ the easiest way to send an installation report is to install the installation-report and reportbug packages
ξ (aptitude install installation-report reportbug),
ξ configure reportbug as explained in Section 8.5.2, and
ξ run the command reportbug installation-reports

Alternatively
ξ you can use this template when filling out installation reports, and
ξ file the report as a bug report against the installation-reports pseudo package,
ξ by sending it to

Package:
ξ installation-reports

Boot method:
ξ

Image version:
ξ

Date:
ξ

Machine:
ξ

Processor:
ξ

Memory:
ξ

Partitions:
ξ

Output of lspci -nn and lspci -vnn:

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn’t try it
Initial boot: [ ]
Detect network card: [ ]
Configure network: [ ]
Detect CD: [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Install base system: [ ]
Clock/timezone setup: [ ]
User/password setup: [ ]
Install tasks: [ ]
Install boot loader: [ ]
Overall install: [ ]

Comments/Problems:
ξ ξ and ideas you had during the initial install.>



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Using the Debian Installer

Using the Debian Installer

How the Installer Works
ξ The Debian Installer consists of a number of special-purpose components to perform each installation task.
ξ Each component performs its task, asking the user questions as necessary to do its job.
ξ The questions themselves are given priorities, and the priority of questions to be asked is set when the installer is started.

ξ When a default installation is performed, only essential (high priority) questions will be asked.
ξ This results in a highly automated installation process with little user interaction.
ξ Components are automatically run in sequence; which components are run depends mainly on the installation method you use and on your hardware.
ξ The installer will use default values for questions that are not asked.

If there is a problem,
ξ the user will see an error screen, and the installer menu may be shown in order to select some alternative action.

If there are no problems,
ξ the user will never see the installer menu, but will simply answer questions for each component in turn.

Serious error notifications
ξ are set to priority “critical” so the user will always be notified.

Some of the defaults that the installer uses can be influenced
ξ by passing boot arguments when debian-installer is started
ξ If, for example, you wish to force static network configuration (DHCP is used by default if available),
ξ you could add the boot parameter netcfg/disable_dhcp=true
ξ See Section 5.2.1 for available options.

Power users
ξ may be more comfortable with a menu-driven interface,
ξ where each step is controlled by the user rather than the installer performing each step automatically in sequence.
ξ To use the installer in a manual, menu-driven way, add the boot argument priority=medium

If your hardware requires you to pass options to kernel modules as they are installed,
ξ you will need to start the installer in “expert” mode
ξ this can be done by either using the expert command to start the installer or by adding the boot argument priority=low
ξ Expert mode gives you full control over debian-installer.

The normal installer display
ξ is character-based (as opposed to the now more familiar graphical interface).
ξ The mouse is not operational in this environment.
ξ Here are the keys you can use to navigate within the various dialogs.
ξ The Tab or right arrow keys move “forward”,
ξ the Shift-Tab or left arrow keys move “backward” between displayed buttons and selections
ξ The up and down arrow select different items within a scrollable list, and also scroll the list itself
ξ In addition, in long lists, you can type a letter to cause the list to scroll directly to the section with items starting with the letter you typed and
ξ use Pg-Up and Pg-Down to scroll the list in sections
ξ The space bar selects an item such as a checkbox
ξ Use Enter to activate choices.

Error messages and logs are redirected to the fourth console
ξ You can access this console by pressing Left Alt-F4 (hold the left Alt key while pressing the F4 function key);
ξ get back to the main installer process with Left Alt-F1.
ξ These messages can also be found in /var/log/syslog.
ξ After installation, this log is copied to /var/log/installer/syslog on your new system.
ξ Other installation messages may be found in /var/log/ during the installation, and
ξ /var/log/installer/ after the computer has been booted into the installed system



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Introduction of Installer Components

Introduction of Installer Components

main-menu
ξ shows the list of components to the user during installer operation
ξ starts a component when it is selected
ξ Main-menu’s questions are set to priority medium
ξ if your priority is set to high or critical (high is the default), you will not see the menu
ξ if there is an error which requires your intervention, the question priority may be downgraded temporarily
ξ to allow you to resolve the problem, and in that case the menu may appear
ξ You can get to the main menu by selecting the “Back” button repeatedly to back all the way out of the currently running component.

localechooser
ξ Allows the user to select localization options for the installation and the installed system: language, country and locales.
ξ The installer will display messages in the selected language,
ξ unless the translation for that language is not complete in which case some messages may be shown in English.

kbd-chooser
ξ Shows a list of keyboards, from which the user chooses the model which matches his own.

hw-detect
ξ Automatically detects most of the system’s hardware, including network cards, disk drives, and PCMCIA.

cdrom-detect
ξ Looks for and mounts a Debian installation CD.

netcfg
ξ Configures the computer’s network connections so it can communicate over the internet.

iso-scan
ξ Looks for ISO file systems, which may be on a CD-ROM or on the hard drive.

choose-mirror
ξ Presents a list of Debian archive mirrors. The user may choose the source of his installation packages

cdrom-checker
ξ Checks integrity of a CD-ROM.
ξ This way, the user may assure him/herself that the installation CD-ROM was not corrupted.

lowmem
ξ Lowmem tries to detect systems with low memory and
ξ then does various tricks to remove unnecessary parts of debian-installer from the memory (at the cost of some features).

anna
ξ Anna’s Not Nearly APT. Installs packages which have been retrieved from the chosen mirror or CD.

partman
ξ Allows the user to partition disks attached to the system,
ξ create file systems on the selected partitions, and attach them to the mountpoints.
ξ Included are also interesting features like a fully automatic mode or LVM support.
ξ This is the preferred partitioning tool in Debian.

autopartkit
ξ Automatically partitions an entire disk according to preset user preferences.

partitioner
ξ Allows the user to partition disks attached to the system.
ξ A partitioning program appropriate to your computer’s architecture is chosen.

partconf
ξ Displays a list of partitions, and creates file systems on the selected partitions according to user instructions.

lvmcfg
ξ Helps the user with the configuration of the LVM (Logical Volume Manager).

mdcfg
ξ Allows the user to setup Software RAID (Redundant Array of Inexpensive Disks).
ξ This Software RAID is usually superior to the cheap IDE (pseudo hardware) RAID controllers found on newer motherboards.

tzsetup
ξ Selects the time zone, based on the location selected earlier

clock-setup
ξ Determines whether the clock is set to UTC or not.

user-setup
ξ Sets up the root password, and adds a non-root user.

base-installer
ξ Installs the most basic set of packages which would allow the computer to operate under Linux when rebooted.

apt-setup
ξ Configures apt, mostly automatically, based on what media the installer is running from.

pkgsel
ξ Uses tasksel to select and install additional software.

os-prober
ξ Detects currently installed operating systems on the computer
ξ passes this information to the bootloader-installer,
ξ which may offer you an ability to add discovered operating systems to the bootloader’s start menu
ξ This way the user could easily choose at the boot time which operating system to start.

bootloader-installer
ξ The various bootloader installers each install a boot loader program on the hard disk,
ξ which is necessary for the computer to start up using Linux without using a floppy or CD-ROM.
ξ Many boot loaders allow the user to choose an alternate operating system each time the computer boots.

shell
ξ Allows the user to execute a shell from the menu, or in the second console.

save-logs
ξ Provides a way for the user to record information on a floppy disk, network, hard disk,
ξ or other media when trouble is encountered, in order to accurately report installer software problems to Debian developers later.



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ Using Individual Components

Using Individual Components

Setting up Debian Installer and Hardware Configuration
ξ Let’s assume the Debian Installer has booted and you are facing its first screen.
ξ At this time, the capabilities of debian-installer are still quite limited.
ξ It doesn’t know much about your hardware, preferred language, or even the task it should perform.

Because debian-installer is quite clever,
ξ it can automatically probe your hardware,
ξ locate the rest of its components and
ξ upgrade itself to a capable installation system

However,
ξ you still need to help debian-installer with some information it can’t determine automatically
ξ like selecting your preferred language, keyboard layout or desired network mirror

Debian-installer performs hardware detection several times during this stage
ξ The first time is targeted specifically at the hardware needed to load installer components (e.g. your CD-ROM or network card)
ξ As not all drivers may be available during this first run, hardware detection needs to be repeated later in the process

Check available memory / low memory mode
ξ One of the first things debian-installer does, is to check available memory.
ξ If the available memory is limited, this component will make some changes in the installation process
ξ which hopefully will allow you to install Debian GNU/Linux on your system.

ξ The first measure taken to reduce memory consumption by the installer is to disable translations,
ξ which means that the installation can only be done in English
ξ you can still localize the installed system after the installation has completed

If that is not sufficient,
ξ the installer will further reduce memory consumption by loading only those components essential to complete a basic installation.
ξ This reduces the functionality of the installation system
ξ You will be given the opportunity to load additional components manually,
ξ but you should be aware that each component you select will use additional memory and thus may cause the installation to fail.

If the installer runs in low memory mode,
ξ it is recommended to create a relatively large swap partition (64–128MB)
ξ The swap partition will be used as virtual memory and thus increases the amount of memory available to the system.
ξ The installer will activate the swap partition as early as possible in the installation process.
ξ Note that heavy use of swap will reduce performance of your system and may lead to high disk activity.

Despite these measures
ξ it is still possible that your system freezes,
ξ that unexpected errors occur or
ξ that processes are killed by the kernel because the system runs out of memory (which will result in “Out of memory” messages on VT4 and in the syslog).
ξ For example, it has been reported that creating a big ext3 file system fails in low memory mode when there is insufficient swap space.
ξ If a larger swap doesn’t help, try creating the file system as ext2 (which is an essential component of the installer) instead.
ξ It is possible to change an ext2 partition to ext3 after the installation.

Selecting Localization Options
ξ installer will default to English
ξ the selected country will be used later in the installation process to pick the default timezone
ξ and a Debian mirror appropriate for your geographic location

Choosing a Keyboard
ξ Keyboards are often tailored to the characters used in a language.
ξ Select a layout that conforms to the keyboard you are using,
ξ or select something close if the keyboard layout you want isn’t represented.
ξ Once the system installation is complete, you’ll be able to select a keyboard layout from a wider range of choices
ξ running kbdconfig as root after you have completed the installation
ξ An ’extended’ keyboard is one with F1 through F10 keys along the top row.

Looking for the Debian Installer ISO Image
ξ when installing via the hd-media method

Configuring Network
ξ By default, debian-installer tries to configure your computer’s network automatically via DHCP



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Partitioning Your Disks

Partitioning Your Disks
ξ If you choose guided partitioning for a whole disk, you will first be asked to select the disk you want to use

“Guided” partitioning
ξ you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive

Schemes:
ξ All files in one partition: min 600MB, created partitions: /, swap
ξ Separate /home partition: min 500MB, created partitions: /, /home, swap
ξ Separate /home, /usr, /var and /tmp partitions: min 1GB /, created partitions:/home, /usr, /var, /tmp, swap

1. Creating partitions directly on the hard disk (classic method)
ξ If you have selected the classic method of partitioning, you will be able to undo any changes right until the end

2. Creating partitions using Logical Volume Management (LVM)
ξ the installer will create most partitions inside one big partition;
ξ the advantage of this method is that partitions inside this big partition can be resized relatively easily later

3. Creating partitions using encrypted LVM
ξ the installer will create most partitions inside one big partition;
ξ the advantage of this method is that partitions inside this big partition can be resized relatively easily later
ξ the big partition will not be readable without knowing a special key phrase, thus providing extra security of your (personal) data.
ξ the installer will also automatically erase the disk by writing random data to it
ξ this further improves security (as it makes it impossible to tell which parts of the disk are in use and also makes sure that any traces of previous installations are erased
ξ this may take some time depending on the size of your disk
ξ If you choose guided partitioning using encrypted LVM for a whole disk, you will first be asked to select the disk you want to use.
ξ you will NOT be able to undo any changes right until the end

Schemes in 1 and 3:
ξ All files in one partition: min 600MB, created partitions: /, swap
ξ Separate /home partition: min 500MB, created partitions: /, /home, swap
ξ Separate /home, /usr, /var and /tmp partitions: min 1GB /, created partitions:/home, /usr, /var, /tmp, swap
ξ If you choose guided partitioning using (encrypted) LVM, the installer will also create a separate /boot partition.
ξ The other partitions, including the swap partition, will be created inside the LVM partition.

After selecting a scheme, the next screen will show your new partition table,
including information on whether and how partitions will be formatted and where they will be mounted.
The list of partitions might look like this:

IDE1 master (hda) - 6.4 GB WDC AC36400L
#1 primary 16.4 MB B f ext2 /boot
#2 primary 551.0 MB swap swap
#3 primary 5.8 GB ntfs
pri/log 8.2 MB FREE SPACE <--- the first disk has some free space

IDE1 slave (hdb) - 80.0 GB ST380021A
#1 primary 15.9 MB ext3
#2 primary 996.0 MB fat16
#3 primary 3.9 GB xfs /home
#5 logical 6.0 GB f ext3 /
#6 logical 1.0 GB f ext3 /var
#7 logical 498.8 MB ext3
#8 logical 551.5 MB swap swap
#9 logical 65.8 GB ext2

If you are satisfied with the generated partition table,
ξ you can choose Finish partitioning and write changes to disk from the menu to implement the new partition table as described at the end of this section
ξ if you are not happy, you can choose to Undo changes

If you select a pristine disk which has neither partitions nor free space on it
ξ you will be asked if a new partition table should be created (this is needed so you can create new partitions)
ξ after this, a new line entitled “FREE SPACE” should appear in the table under the selected disk
ξ if you select some free space, you will have the opportunity to create a new partition
ξ you will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space)
ξ after this, you will be presented with a detailed overview of your new partition
ξ The main setting is Use as:
ξ which determines if the partition will have a file system on it,
ξ or be used for swap, software RAID, LVM, an encrypted file system, or not be used at all
ξ Other settings include mountpoint, mount options, and bootable flag;
ξ which settings are shown depends on how the partition is to be used
ξ If you don’t like the preselected defaults, feel free to change them to your liking
ξ E.g. by selecting the option Use as:
ξ you can choose a different filesystem for this partition,
ξ including options to use the partition for swap, software RAID, LVM, or not use it at all
ξ Another nice feature is the ability to copy data from an existing partition onto this one
ξ When you are satisfied with your new partition, select Done setting up the partition and you will return to partman’s main screen.

ξ If you decide you want to change something about your partition, simply select the partition,
ξ which will bring you to the partition configuration menu
ξ This is the same screen as is used when creating a new partition, so you can change the same settings
ξ One thing that may not be very obvious at a first glance is that you can resize the partition
ξ by selecting the item displaying the size of the partition
ξ Filesystems known to work are at least fat16, fat32, ext2, ext3 and swap
ξ This menu also allows you to delete a partition
ξ Be sure to create at least two partitions:
ξ one for the root filesystem (which must be mounted as /) and
ξ one for swap
ξ If you forget to mount the root filesystem, partman won’t let you continue until you correct this issue !

ξ Capabilities of partman can be extended with installer modules, but are dependent on your system’s architecture.
ξ So if you can’t see all promised goodies, check if you have loaded all required modules (e.g. partman-ext3, partman-xfs, or partman-lvm).
ξ After you are satisfied with partitioning, select Finish partitioning and write changes to disk from the partitioning menu.
ξ You will be presented with a summary of changes made to the disks and asked to confirm that the filesystems should be created as requested

Configuring the Logical Volume Manager (LVM)
ξ If you are working with computers at the level of system administrator or “advanced” user,
ξ you have surely seen the situation where some disk partition (usually the most important one) was short on space,
ξ while some other partition was grossly underused and you had to manage this situation with moving stuff around, symlinking, etc.
ξ To avoid the described situation you can use Logical Volume Manager (LVM).
ξ Simply said, with LVM you can combine your partitions (physical volumes in LVM lingo) to form a virtual disk (so called volume group),
ξ which can then be divided into virtual partitions (logical volumes)
ξ The point is that logical volumes (and of course underlying volume groups) can span across several physical disks.
ξ Now when you realize you need more space for your old 160GB /home partition,
ξ you can simply add a new 300GB disk to the computer, join it with your existing volume group and
ξ then resize the logical volume which holds your /home filesystem and voila — your users have some room again on their renewed 460GB partition.
»LVM-HOWTO
ξ LVM setup in debian-installer is quite simple and completely supported inside partman.
ξ First, you have to mark the partition(s) to be used as physical volumes for LVM.
ξ This is done in the Partition settings menu where you should select Use as:-!physical volume for LVM.
ξ When you return to the main partman screen, you will see a new option Configure the Logical Volume Manager.
ξ When you select that, you will first be asked to confirm pending changes to the partition table (if any) and
ξ after that the LVM configuration menu will be shown.
ξ Above the menu a summary of the LVM configuration is shown.
ξ The menu itself is context sensitive and only shows valid actions.
ξ The possible actions are:
• Display configuration details: shows LVM device structure, names and sizes of logical volumes and more
• Create volume group
• Create logical volume
• Delete volume group
• Delete logical volume
• Extend volume group
• Reduce volume group
• Finish: return to the main partman screen
ξ Use the options in that menu to first create a volume group and then create your logical volumes inside it.
After you return to the main partman screen, any created logical volumes will be displayed in the
same way as ordinary partitions (and you should treat them as such).



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Setting up the System

Setting up the System

Configuring Your Time Zone
ξ Depending on the location selected at the beginning of the installation process, you might be shown a list of timezones relevant for that location.
ξ If your location has only one time zone, you will not be asked anything and the system will assume that time zone

Configuring the Clock
ξ The installer might ask you if the computer’s clock is set to UTC.
ξ Normally this question is avoided if possible and the installer tries to work out whether the clock is set
ξ In expert mode you will always be able to choose whether or not the clock is set to UTC.
ξ Systems that (also) run Dos or Windows are normally set to local time.
ξ If you want to dual-boot, select local time instead of GMT.
ξ Note that the installer does not currently allow you to actually set the time in the computer’s clock.
ξ You can set the clock to the current time after you have installed, if it is incorrect or if it was previously not set to UTC.

Set the Root Password
ξ The root account is also called the super-user;
ξ it is a login that bypasses all security protection on your system
ξ The root account should only be used to perform system administration, and only used for as short a time as possible.
ξ Any password you create should contain at least 6 characters, and
ξ should contain both upper- and lower-case characters, as well as punctuation characters
ξ Take extra care when setting your root password, since it is such a powerful account
ξ Avoid dictionary words or use of any personal information which could be guessed
ξ If anyone ever tells you they need your root password, be extremely wary
ξ You should normally never give your root password out, unless you are administering a machine with more than one system administrator

Create an Ordinary User
ξ The system will ask you whether you wish to create an ordinary user account at this point.
ξ This account should be your main personal log-in.
ξ You should NOT use the root account for daily use or as your personal login !

Why not root account?
ξ one reason to avoid using root’s privileges is that it is very easy to do irreparable damage as root
ξ you might be tricked into running a Trojan-horse program
ξ that is a program that takes advantage of your super-user powers to compromise the security of your system behind your back
ξ any good book on Unix system administration will cover this topic in more detail — consider reading one if it is new to you
ξ you will first be prompted for the user’s full name
ξ then you’ll be asked for a name for the user account
ξ generally your first name or something similar will suffice and indeed will be the default
ξ Finally, you will be prompted for a password for this account

Adding users
ξ if at any point after installation you would like to create another account, use the adduser command

Installing the Base System
ξ this stage is the least problematic
ξ it consumes a significant fraction of the install because it downloads, verifies and unpacks the whole base system
ξ during installation of the base system, package unpacking and setup messages are redirected to tty4
ξ you can access this terminal by pressing Left Alt-F4; get back to the main installer process with Left Alt-F1
ξ the unpack/setup messages generated during this phase are also saved in /var/log/syslog
ξ You can check them there if the installation is performed over a serial console
ξ As part of the installation, a Linux kernel will be installed
ξ At the default priority, the installer will choose one for you that best matches your hardware
ξ In lower priority modes, you will be able to choose from a list of available kernels.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Installing Additional Software
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Configuring apt
ξ One of the tools used to install packages on a Debian GNU/Linux system is a program called apt-get from the apt package
ξ aptitude is now the recommended utility for package management

apt must be configured so that it knows where to retrieve packages from.
The installer largely takes care of this automatically based on what it knows about your installation medium.
The results of this configuration are written to the file /etc/apt/sources.list, and
you can examine and edit it to your liking after the install is complete



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Selecting and Installing Software

Selecting and Installing Software
ξ During the installation process, you are given the opportunity to select additional software to install.
ξ Rather than picking individual software packages from the 17850 available packages,
ξ this stage of the installation process focuses on selecting and installing predefined collections of software
ξ to quickly set up your computer to perform various tasks.
ξ So, you have the ability to choose tasks first, and then add on more individual packages later.

Desktop environment
ξ this task will install the GNOME desktop environment
ξ the options offered by the installer currently do NOT allow to select a different desktop environment such as for example KDE
ξ it is possible to get the installer to install KDE by using preseeding (see Section B.4.11) or
ξ by adding tasks="standard, kde-desktop" at the boot prompt when starting the installer
ξ However, this will only work if the packages needed for KDE are actually available.
ξ If you are installing using a full CD image, they will need to be downloaded from a mirror !
ξ as KDE packages are NOT included on the first full CD
ξ installing KDE this way should work fine if you are using a DVD image or any other installation method

DNS server
ξ bind9

File server
ξ samba, nfs

Mail server
ξ exim4, spamassassin, uw-imap

Print server
ξ cups

SQL database:
ξ postgresql

Web server
ξ apache

Once you’ve selected your tasks, select OK
ξ at this point, aptitude will install the packages that are part of the tasks you’ve selected
ξ Note: In the standard user interface of the installer, you can use the space bar to toggle selection of a task
ξ Each package you selected with tasksel is downloaded, unpacked and then installed in turn by the apt-get and dpkg programs
ξ If a particular program needs more information from the user, it will prompt you during this process



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Making Your System Bootable

Making Your System Bootable

Detecting other operating systems
ξ before a boot loader is installed,
ξ the installer will attempt to probe for other operating systems which are installed on the machine
ξ If it finds a supported operating system, you will be informed of this during the boot loader installation step, and
ξ the computer will be configured to boot this other operating system in addition to Debian

*** Warning ***
ξ multiple operating systems booting on a single machine is still something of a black art
ξ the automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture
ξ if it does not work you should consult your boot manager’s documentation for more information

Installing the Grub Boot Loader on a Hard Disk (amd64 default)
ξ The main amd64 boot loader is called “grub”
ξ Grub is a flexible and robust boot loader and a good default choice for newbies and old hands alike
ξ by default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process
ξ If you prefer, you can install it elsewhere
ξ see the grub manual for complete information
ξ If you do not want to install grub at all, use the Back button to get to the main menu,
ξ and from there select whatever bootloader you would like to use.

Install the LILO Boot Loader on a Hard Disk (alternative)
ξ The second amd64 boot loader is called “LILO”
ξ It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management
ξ carefully read the instructions in the directory /usr/share/doc/lilo/ if you have special needs
ξ »LILO




select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Finishing the Installation

Finishing the Installation

Finish the Installation and Reboot
ξ This is the last step in the initial Debian installation process
ξ You will be prompted to remove the boot media that you used to boot the installer
ξ The installer will do any last minute tasks, and then reboot into your new Debian system

Miscellaneous
ξ The components listed in this section are usually not involved in the installation process, but
ξ are waiting in the background to help the user in case something goes wrong

Saving the installation logs
ξ If the installation is successful, the logfiles created during the installation process will be automatically saved to /var/log/installer/ on your new Debian system.
ξ Choosing Save debug logs from the main menu allows you to save the log files to hard disk, or other media
ξ This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report

Using the Shell and Viewing the Logs while running an installation
ξ switch to the second virtual console by pressing Left Alt-F28
ξ Use Left Alt-F1 to switch back to installer itself

If you cannot switch consoles
ξ there is also an Execute a Shell item on the main menu that can be used to start a shell
ξ to get back to the installer itself, type exit to close the shell

At this point you are booted from the RAMdisk, and there is a limited set of Unix utilities available for your use
ξ You can see what programs are available with the command ls /bin /sbin /usr/bin /usr/sbin and by typing help
ξ the shell is a Bourne shell clone called ash and has some nice features like autocompletion and history
ξ To edit and view files, use the text editor nano
ξ Log files for the installation system can be found in the /var/log directory

*** Warning ***
ξ Although you can do basically anything in a shell that the available commands allow you to do,
ξ the option to use a shell is really only there in case something goes wrong and for debugging
ξ Doing things manually from the shell may interfere with the installation process and
ξ result in errors or an incomplete installation
ξ In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Booting Into Your New Debian System

Booting Into Your New Debian System

The Moment of Truth
ξ Your system’s first boot on its own power is what electrical engineers call the “smoke test”.
ξ If you did a default installation, the first thing you should see when you boot the system is the menu of the grub or possibly the lilo bootloader.
ξ The first choices in the menu will be for your new Debian system.
ξ If you had any other operating systems on your computer (like Windows) that were detected by the installation system,
ξ those will be listed lower down in the menu.
ξ If the system fails to start up correctly, don’t panic.
ξ If the installation was successful, chances are good that there is only a relatively minor problem that is preventing the system from booting Debian.
ξ In most cases such problems can be fixed without having to repeat the installation.
ξ One available option to fix boot problems is to use the installer’s built-in rescue mode (see Section 8.7).

ξ If you are new to Debian and Linux, you may need some help from more experienced users.
ξ For direct on-line help you can try the IRC channels #debian or #debian-boot on the OFTC network.
ξ Alternatively you can contact the debian-user mailing list »debian-user mailing list
ξ You can also file an installation report as described in Section 5.3.6.
ξ Please make sure that you describe your problem clearly and include any messages that are displayed and may help others to diagnose the issue.
ξ If you had any other operating systems on your computer that were not detected or not detected correctly, please file an installation report.

Log In
ξ Once your system boots, you’ll be presented with the login prompt.
ξ Log in using the personal login and password you selected during the installation process.
ξ Your system is now ready for use.

If you are a new user
ξ you may want to explore the documentation which is already installed on your system as you start to use it
ξ there are currently several documentation systems, work is proceeding on integrating the different types of documentation
ξ Here are a few starting points

Documentation accompanying programs you have installed
ξ can be found in /usr/share/doc/,
ξ under a subdirectory named after the program (or, more precise, the Debian package that contains the program)

More extensive documentation is often packaged separately in special documentation packages that are mostly not installed by default
ξ for example, documentation about the package management tool apt can be found in the packages apt-doc or apt-howto

In addition, there are some special folders within the /usr/share/doc/ hierarchy
ξ Linux HOWTOs are installed in .gz (compressed) format, in /usr/share/doc/HOWTO/en-txt/

After installing dhelp
ξ you will find a browse-able index of documentation in /usr/share/doc/HTML/index.html

One easy way to view these documents using a text based browser is to enter the following commands:
$ cd /usr/share/doc/
$ w3c .
ξ The dot after the w3c command tells it to show the contents of the current directory.

If you have a graphical desktop environment installed
ξ you can also use its web browser
ξ start the web browser from the application menu and enter /usr/share/doc/ in the address bar

You can also type info command or man command to see documentation on most commands available at the command prompt
ξ typing help will display help on shell commands
ξ yping a command followed by --help will usually display a short summary of the command’s usage
ξ If a command’s results scroll past the top of the screen, type | more after the command to cause the results to pause before scrolling past the top of the screen
ξ to see a list of all commands available which begin with a certain letter, type the letter and then two tabs



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Shutting down the system

Shutting down the system
ξ to shut down a running Linux system, you must NOT reboot with the reset switch on the front
ξ NOT back of your computer NOR just turn off the computer

ξ Linux should be shut down in a controlled manner !
ξ otherwise files might get lost and/or disk damage might occur!

If you run a desktop environment
ξ there is usually an option to “log out” available from the application menu that allows you to shutdown (or reboot) the system

Alternatively you can press the key combination Ctrl-Alt-Del.

A last option is to log in as root
ξ and type one of the commands poweroff, halt or shutdown -h now
ξ if either of the key combinations do not work or you prefer to type commands; use reboot to reboot the system



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Debian Packaging System

Debian Packaging System
ξ The most important concept to grasp is the Debian packaging system
ξ In essence, large parts of your system should be considered under the control of the packaging system.

These include:
• /usr (excluding /usr/local)
• /var (you could make /var/local and be safe in there)
• /bin
• /sbin
69
Chapter 8. Next Steps and Where to Go From Here
• /lib

For instance
ξ if you replace /usr/bin/perl, that will work,
ξ but then if you upgrade your perl package, the file you put there will be replaced
ξ Experts can get around this by putting packages on “hold” in aptitude.

One of the best installation methods is apt
ξ You can use the command line version apt-get or fullscreen text version aptitude
ξ Note apt will also let you merge main, contrib, and non-free so you can have export-restricted packages as well as standard versions.



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Cron Job Management

Cron Job Management
ξ Any jobs under the purview of the system administrator should be in /etc, since they are configuration files.
ξ If you have a root cron job for daily, weekly, or monthly runs, put them in /etc/cron.{daily,weekly,monthly}.
ξ These are invoked from /etc/crontab, and will run in alphabetic order, which serializes them.

ξ On the other hand, if you have a cron job that (a) needs to run as a special user, or
ξ (b) needs to run at a special time or frequency, you can use either /etc/crontab,
ξ or, better yet, /etc/cron.d/whatever

ξ These particular files also have an extra field that allows you to stipulate the user account under which the cron job runs.
ξ In either case, you just edit the files and cron will notice them automatically.
ξ There is no need to run a special command
ξ For more information see cron(8), crontab(5), and /usr/share/doc/cron/README.Debian.



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Further Reading and Information

Further Reading and Information
ξ If you need information about a particular program, you should first try man program, or info program
ξ There is lots of useful documentation in /usr/share/doc as well.
ξ In particular, /usr/share/doc/HOWTO and /usr/share/doc/FAQ contain lots of interesting information.
ξ To submit bugs, look at /usr/share/doc/debian/bug*.
ξ To read about Debian-specific issues for particular programs, look at /usr/share/doc/(package name)/README.Debian.

ξ »Debian web site
ξ contains a large quantity of documentation about Debian



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Desktop for Debian

»Debian on the Desktop

1. »Gnome

2. »KDE

3. »GNUstep
ξ GNUstep is a cross-platform, object-oriented framework for desktop application development. Based on the OpenStep specification originally created by NeXT (now Apple)



~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Package: pyqt-tools

Package: pyqt-tools
ξ pyuic is the PyQt counterpart for Qt's uic
ξ It takes an XML qt-designer compliant file and generates Python/PyQt code
ξ pylupdate is the counterpart for Qt's lupdate. It updates Qt Linguist translation files from Python code.
ξ downloadable packet for amd64



~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~ASUS Motherboard

ASUS Motherboard Specifications Document

M3N78-EMH HDMI

CPU
ξ ok = supports AMD Athlon 64X2 Dual Core Processor 4600+

Chipset
ξ NVIDIA GeForce 8200 (MCP785)

System Bus
ξ up to 5200 MT/s HyperTransport 3.0 interface for Am2+ CPU

Memory <--- ok for one 2GB DIMM
ξ dual-channel memory architecture
ξ 4 x 240 pin DIMM
ξ sockets support up to 8GB of unbuffered ECC and non-ECC 1066/800/667/533 MHz
ξ DDR memory modules
ξ only AMD2+ CPU supports DDR2 1066
ξ good for 3G graphics

Expansion Slots <--- none used because LAN, SATA etc integrated on motherboard
ξ 1 x PCI Express x 16 slot (new)
ξ 1 x PCI Express x 16 slot (new)
ξ 2 x PCI slots

Graphics <--- ok for ViewSonic P225f
ξ integrated NVIDIA GeForce Series DirectX10 grpahics processor
ξ hybrid SLI support (only for Windows Vista)
ξ supports HDMI interface with HDCP compliant with max resolution up to 1920 x 1200
ξ supports HD reso of 720p and 1080p
ξ supports D-Sub with max reso up to 1920 x 1440 @75Hz

Storage <--- for Western Digital WD3200AAJS WD Caviar 300gb hd
ξ Southbridge
ξ 1 x Ultra DMA 133 / 100 interface
ξ 6 x Serial ATA 3 Gb7s hard disk drives supporting RAID 0, RAID 1, RAID 5, RAID 0+1 and JBOD configuration

High Definiton Audio
ξ Realtek ALC883 High Def. Audio 8-channel CODEC
ξ supports S/PDIF out interface, Jack-detected and multistreaming

USB
ξ 12 USB 2.0 / 1.1. ports
ξ 8 ports at mid-board, 4 ports at rear pane

LAN <--- no LAN card needed !
ξ NVIDIA nForce built-in Gigabit MAC with external Atheros PHY


Links:
»ASUS.com
ξ AMD Socket Am2+
ξ M3N-HD/HDMI
ξ - Support latest AMD Phenom ™ Quad-Core Processor
ξ VERY difficult and frustrating page !
ξ it looks like ASUS supports only Windows and NOT Linux !!!



~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~BIOS Information

BIOS Information

Primary IDE Master
ξ BENQ DVD DD DW1

Primary IDE Slave
ξ not detected

SATA1
ξ WDC WD3200AAJS-22V <--- »Western Digital 300gb hard disk
ξ SATA2...4 not detected

IDE Configuration
ξ on board PCI IDE Controller [Enabled]
ξ on board SATA Controller [Enabled]
ξ SATA Mode select [SATA Model] <--- must be analyzed; propably better to change to AHCI !
ξ not RAID
ξ not AHCI »Advanced Host Controller Interface
ξ note with ASUS DVD you can make AHCI driver floppies for Windows XP, which might work with Linux too

ξ AHCI controller does not work on AMD/ATI RS400-200 and RS480 HBA when MSI is enabled due to a hardware error.
ξ In order for AHCI to work users must provide the "pci=nomsi" kernel boot parameter.
ξ With MSI disabled in this way, the PCIe bus can only act as a faster PCI bus with hotplug capabilities.
ξ This is also true of the Nvidia nForce 560 chipset.

System Information

AMIBIOS
ξ Version: 0222
ξ Build date: 03/11/08

Processor
ξ Type: AMD Athlon 64 X2 Dual Core Processor 4600+
ξ Speed: 24000 Hhz
ξ Count: 2

System Memory
ξ Installed: 2048 MB
ξ Usable: 1920 MB

Advanced

Jump free configuration
ξ AI overclocking [Auto]
ξ Memory voltage [Auto]

CPU Configuration
ξ Module version: 13.24
ξ AGESA version: 3.1.6.0
ξ Physical count: 1
ξ Logical count: 2

AMD Athlon 64 X2 Dual Core Processo 4600+
ξ Revision: F3
ξ Cache L1: 256 kb
ξ Cache L2: 1024 kb
ξ Cache L3: N/A
ξ Speed: 2400 MHz, NB Clk: N/A
ξ Current FSB Multiplier: 12X
ξ Max FSB Multiplier: 12X
ξ Able to change frequency: Yes
ξ uCode Patch Level: None Required
ξ GART Error Reporting [Disabled]
ξ Microcode Updating [Enabled]
ξ Secure Virtual machine mode[Enabled]
ξ Cool'n' Quiet [Enabled]

Power
ξ Suspended Mode [Auto]
ξ ACPI 2.0 Support [Disabled]
ξ ACPI APIC Support [Enabled]

APM Configuration
ξ Return on AC Power Loss [Power Off]
ξ Power on By PCI Device [Disabled]
ξ Power on By Ring [Disabled]
ξ Power on By PS72 KB/MS [Disabled]
ξ Power on By RTS Alarm [Disabled]

Boot
ξ First boot device: Floppy
ξ Second boot device: DVD
ξ Third boot device SATA: 3M-WDC WD3200 <--- Western Digital 300Gb SATA hard disk

Boot Settings Configuration
ξ Quick Boot [Enabled]
ξ Full Screen Logo [Enabled]
ξ Boot up Num-Lock [Enabled]
ξ PS/2 Mouse Support [Auto]
ξ Wait for F1 if Error [Enabled]
ξ Hit 'DEL' Message Display [Enabled]
ξ Interrupt 19 Capture [Disabled]

Security Settings
ξ Supervisor Password: fast
ξ User Password: black

note: press enter twice to disable

User Access Level
ξ [Full Access]

Tools
ξ ASUS EZ Flash 2
ξ not run; it updates BIOS

Exit
ξ exit and save changes if any



~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Versions and Challenges (Linux Kernel etc)

Versions and Challenges

Debian GNU/Linux 4.0 r3 "Etch"
ξ amd64 DVD Binary-1 20080217-12:13
ξ this the one burned in four DVDs
»Debian GNU/Linux 4.0 updated
ξ note Plone and Zope versions !
ξ The latest stable release of Debian is 4.0.
ξ The last update to this release was made on July 26th, 2008
ξ the next release codename is "lenny"

Linux Kernel 2.6.18
ξ does NOT support AHCI
ξ Debian GNU/Linux "etc" 4.0 is delivered with the kernel version 2.6.18 to all arhitectures !

Linux Kernel 2.6.19
ξ supports AHCI
ξ not with Debian GNU/Linux "etc" 4.0 !!!



~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Hardware-summary of Install

Hardware-summary of Install
umame -a: Linux (none) 2.6.18-6-amd64 #1 SMP Sat Jan 26 08:39:14 UTC 2008 x86_64 unknown
lspci -nn: 00:00.0 RAM memory [0500]: nVidia Corporation Unknown device [10de:0754] (rev a2)
lspci -nn: 00:01.0 ISA bridge [0601]: nVidia Corporation Unknown device [10de:075c] (rev a2)
lspci -nn: 00:01.1 SMBus [0c05]: nVidia Corporation Unknown device [10de:0752] (rev a1)
lspci -nn: 00:01.2 RAM memory [0500]: nVidia Corporation Unknown device [10de:0751] (rev a1)
lspci -nn: 00:01.3 Co-processor [0b40]: nVidia Corporation Unknown device [10de:0753] (rev a2)
lspci -nn: 00:01.4 RAM memory [0500]: nVidia Corporation Unknown device [10de:0568] (rev a1)
lspci -nn: 00:02.0 USB Controller [0c03]: nVidia Corporation Unknown device [10de:077b] (rev a1)
lspci -nn: 00:02.1 USB Controller [0c03]: nVidia Corporation Unknown device [10de:077c] (rev a1)
lspci -nn: 00:04.0 USB Controller [0c03]: nVidia Corporation Unknown device [10de:077d] (rev a1)
lspci -nn: 00:04.1 USB Controller [0c03]: nVidia Corporation Unknown device [10de:077e] (rev a1)
lspci -nn: 00:06.0 IDE interface [0101]: nVidia Corporation Unknown device [10de:0759] (rev a1)
lspci -nn: 00:07.0 Audio device [0403]: nVidia Corporation Unknown device [10de:0774] (rev a1)
lspci -nn: 00:08.0 PCI bridge [0604]: nVidia Corporation Unknown device [10de:075a] (rev a1)
lspci -nn: 00:09.0 IDE interface [0101]: nVidia Corporation Unknown device [10de:0ad0] (rev a2)
lspci -nn: 00:0a.0 Ethernet controller [0200]: nVidia Corporation Unknown device [10de:0760] (rev a2)
lspci -nn: 00:0b.0 PCI bridge [0604]: nVidia Corporation Unknown device [10de:0569] (rev a1)
lspci -nn: 00:10.0 PCI bridge [0604]: nVidia Corporation Unknown device [10de:0778] (rev a1)
lspci -nn: 00:12.0 PCI bridge [0604]: nVidia Corporation Unknown device [10de:075b] (rev a1)
lspci -nn: 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
lspci -nn: 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101]
lspci -nn: 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102]
lspci -nn: 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103]
lspci -nn: 02:00.0 VGA compatible controller [0300]: nVidia Corporation Unknown device [10de:0849] (rev a2)
lspci -vnn: 00:00.0 RAM memory [0500]: nVidia Corporation Unknown device [10de:0754] (rev a2)
lspci -vnn: Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Flags: bus master, 66MHz, fast devsel, latency 0
lspci -vnn: Capabilities: [94] HyperTransport: #1a
lspci -vnn: Capabilities: [60] HyperTransport: Retry Mode
lspci -vnn: Capabilities: [44] HyperTransport: Slave or Primary Interface
lspci -vnn: Capabilities: [d0] HyperTransport: #1c
lspci -vnn:
lspci -vnn: 00:01.0 ISA bridge [0601]: nVidia Corporation Unknown device [10de:075c] (rev a2)
lspci -vnn: Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Flags: bus master, 66MHz, fast devsel, latency 0
lspci -vnn: I/O ports at 0900 [size=256]
lspci -vnn:
lspci -vnn: 00:01.1 SMBus [0c05]: nVidia Corporation Unknown device [10de:0752] (rev a1)
lspci -vnn: Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Flags: 66MHz, fast devsel, IRQ 11
lspci -vnn: I/O ports at 0e00 [size=64]
lspci -vnn: I/O ports at 0600 [size=64]
lspci -vnn: I/O ports at 0700 [size=64]
lspci -vnn: Capabilities: [44] Power Management version 2
lspci -vnn:
lspci -vnn: 00:01.2 RAM memory [0500]: nVidia Corporation Unknown device [10de:0751] (rev a1)
lspci -vnn: Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Flags: 66MHz, fast devsel
lspci -vnn:
lspci -vnn: 00:01.3 Co-processor [0b40]: nVidia Corporation Unknown device [10de:0753] (rev a2)
lspci -vnn: Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 10
lspci -vnn: Memory at fcf80000 (32-bit, non-prefetchable) [size=512K]
lspci -vnn:
lspci -vnn: 00:01.4 RAM memory [0500]: nVidia Corporation Unknown device [10de:0568] (rev a1)
lspci -vnn: Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Flags: 66MHz, fast devsel
lspci -vnn:
lspci -vnn: 00:02.0 USB Controller [0c03]: nVidia Corporation Unknown device [10de:077b] (rev a1) (prog-if 10)
lspci -vnn: Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 233
lspci -vnn: Memory at fcf7e000 (32-bit, non-prefetchable) [size=4K]
lspci -vnn: Capabilities: [44] Power Management version 2
lspci -vnn:
lspci -vnn: 00:02.1 USB Controller [0c03]: nVidia Corporation Unknown device [10de:077c] (rev a1) (prog-if 20)
lspci -vnn: Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 217
lspci -vnn: Memory at fcf7fc00 (32-bit, non-prefetchable) [size=256]
lspci -vnn: Capabilities: [44] Debug port
lspci -vnn: Capabilities: [80] Power Management version 2
lspci -vnn:
lspci -vnn: 00:04.0 USB Controller [0c03]: nVidia Corporation Unknown device [10de:077d] (rev a1) (prog-if 10)
lspci -vnn: Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 209
lspci -vnn: Memory at fcf7d000 (32-bit, non-prefetchable) [size=4K]
lspci -vnn: Capabilities: [44] Power Management version 2
lspci -vnn:
lspci -vnn: 00:04.1 USB Controller [0c03]: nVidia Corporation Unknown device [10de:077e] (rev a1) (prog-if 20)
lspci -vnn: Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 225
lspci -vnn: Memory at fcf7f800 (32-bit, non-prefetchable) [size=256]
lspci -vnn: Capabilities: [44] Debug port
lspci -vnn: Capabilities: [80] Power Management version 2
lspci -vnn:
lspci -vnn: 00:06.0 IDE interface [0101]: nVidia Corporation Unknown device [10de:0759] (rev a1) (prog-if 8a [Master SecP PriP])
lspci -vnn: Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Flags: bus master, 66MHz, fast devsel, latency 0
lspci -vnn: I/O ports at ffa0 [size=16]
lspci -vnn: Capabilities: [44] Power Management version 2
lspci -vnn:
lspci -vnn: 00:07.0 Audio device [0403]: nVidia Corporation Unknown device [10de:0774] (rev a1)
lspci -vnn: Subsystem: ASUSTeK Computer Inc. Unknown device [1043:829f]
lspci -vnn: Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 15
lspci -vnn: Memory at fcf78000 (32-bit, non-prefetchable) [size=16K]
lspci -vnn: Capabilities: [44] Power Management version 2
lspci -vnn: Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/0 Enable-
lspci -vnn: Capabilities: [6c] HyperTransport: MSI Mapping
lspci -vnn:
lspci -vnn: 00:08.0 PCI bridge [0604]: nVidia Corporation Unknown device [10de:075a] (rev a1) (prog-if 01)
lspci -vnn: Flags: bus master, 66MHz, fast devsel, latency 0
lspci -vnn: Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
lspci -vnn: Capabilities: [b8] Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Capabilities: [8c] HyperTransport: MSI Mapping
lspci -vnn:
lspci -vnn: 00:09.0 IDE interface [0101]: nVidia Corporation Unknown device [10de:0ad0] (rev a2) (prog-if 85 [Master SecO PriO])
lspci -vnn: Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 209
lspci -vnn: I/O ports at d480 [size=8]
lspci -vnn: I/O ports at d400 [size=4]
lspci -vnn: I/O ports at d080 [size=8]
lspci -vnn: I/O ports at d000 [size=4]
lspci -vnn: I/O ports at cc00 [size=16]
lspci -vnn: Memory at fcf76000 (32-bit, non-prefetchable) [size=8K]
lspci -vnn: Capabilities: [44] Power Management version 2
lspci -vnn: Capabilities: [8c] #12 [0010]
lspci -vnn: Capabilities: [b0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/3 Enable-
lspci -vnn: Capabilities: [ec] HyperTransport: MSI Mapping
lspci -vnn:
lspci -vnn: 00:0a.0 Ethernet controller [0200]: nVidia Corporation Unknown device [10de:0760] (rev a2)
lspci -vnn: Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 10
lspci -vnn: Memory at fcf7c000 (32-bit, non-prefetchable) [size=4K]
lspci -vnn: I/O ports at c880 [size=8]
lspci -vnn: Memory at fcf7f400 (32-bit, non-prefetchable) [size=256]
lspci -vnn: Memory at fcf7f000 (32-bit, non-prefetchable) [size=16]
lspci -vnn: Capabilities: [44] Power Management version 2
lspci -vnn: Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/4 Enable-
lspci -vnn: Capabilities: [6c] HyperTransport: MSI Mapping
lspci -vnn:
lspci -vnn: 00:0b.0 PCI bridge [0604]: nVidia Corporation Unknown device [10de:0569] (rev a1)
lspci -vnn: Flags: bus master, fast devsel, latency 0
lspci -vnn: Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
lspci -vnn: I/O behind bridge: 0000e000-0000efff
lspci -vnn: Memory behind bridge: fd000000-febfffff
lspci -vnn: Prefetchable memory behind bridge: 00000000ce000000-00000000dfffffff
lspci -vnn: Capabilities: [40] Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Capabilities: [48] Power Management version 2
lspci -vnn: Capabilities: [60] HyperTransport: MSI Mapping
lspci -vnn:
lspci -vnn: 00:10.0 PCI bridge [0604]: nVidia Corporation Unknown device [10de:0778] (rev a1)
lspci -vnn: Flags: bus master, fast devsel, latency 0
lspci -vnn: Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
lspci -vnn: Capabilities: [40] Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Capabilities: [48] Power Management version 3
lspci -vnn: Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable+
lspci -vnn: Capabilities: [60] HyperTransport: MSI Mapping
lspci -vnn: Capabilities: [80] Express Root Port (Slot+) IRQ 0
lspci -vnn:
lspci -vnn: 00:12.0 PCI bridge [0604]: nVidia Corporation Unknown device [10de:075b] (rev a1)
lspci -vnn: Flags: bus master, fast devsel, latency 0
lspci -vnn: Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
lspci -vnn: Capabilities: [40] Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Capabilities: [48] Power Management version 3
lspci -vnn: Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable+
lspci -vnn: Capabilities: [60] HyperTransport: MSI Mapping
lspci -vnn: Capabilities: [80] Express Root Port (Slot+) IRQ 0
lspci -vnn:
lspci -vnn: 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
lspci -vnn: Flags: fast devsel
lspci -vnn: Capabilities: [80] HyperTransport: Host or Secondary Interface
lspci -vnn:
lspci -vnn: 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101]
lspci -vnn: Flags: fast devsel
lspci -vnn:
lspci -vnn: 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102]
lspci -vnn: Flags: fast devsel
lspci -vnn:
lspci -vnn: 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103]
lspci -vnn: Flags: fast devsel
lspci -vnn: Capabilities: [f0] #0f [0010]
lspci -vnn:
lspci -vnn: 02:00.0 VGA compatible controller [0300]: nVidia Corporation Unknown device [10de:0849] (rev a2)
lspci -vnn: Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82f2]
lspci -vnn: Flags: bus master, fast devsel, latency 0, IRQ 15
lspci -vnn: Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
lspci -vnn: Memory at d0000000 (64-bit, prefetchable) [size=256M]
lspci -vnn: Memory at ce000000 (64-bit, prefetchable) [size=32M]
lspci -vnn: I/O ports at ec00 [size=128]
lspci -vnn: Expansion ROM at febe0000 [disabled] [size=128K]
lspci -vnn: Capabilities: [60] Power Management version 2
lspci -vnn: Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
lspci -vnn:
modulemap: 10de:077b ohci_hcd
modulemap: 10de:077c ehci_hcd
modulemap: 10de:077d ohci_hcd
modulemap: 10de:077e ehci_hcd
modulemap: 10de:0ad0 sata_nv
lsmod: Module Size Used by
lsmod: nls_iso8859_1 9472 1
lsmod: isofs 39396 1
lsmod: ide_disk 20352 0
lsmod: ide_cd 44704 1
lsmod: cdrom 40104 1 ide_cd
lsmod: ide_generic 5632 0 [permanent]
lsmod: pdc202xx_new 13312 0 [permanent]
lsmod: sc1200 11520 0 [permanent]
lsmod: sis5513 18192 0 [permanent]
lsmod: opti621 9220 0 [permanent]
lsmod: amd74xx 19248 0 [permanent]
lsmod: piix 15236 0 [permanent]
lsmod: pdc202xx_old 14848 0 [permanent]
lsmod: it821x 12932 0 [permanent]
lsmod: siimage 16640 0 [permanent]
lsmod: atiixp 11024 0 [permanent]
lsmod: cy82c693 9096 0 [permanent]
lsmod: trm290 8836 0 [permanent]
lsmod: alim15x3 16152 0 [permanent]
lsmod: via82cxxx 13188 0 [permanent]
lsmod: hpt34x 9856 0 [permanent]
lsmod: ns87415 8904 0 [permanent]
lsmod: rz1000 7296 0 [permanent]
lsmod: cs5520 9472 0 [permanent]
lsmod: serverworks 13456 0 [permanent]
lsmod: jmicron 9088 0 [permanent]
lsmod: cs5530 9984 0 [permanent]
lsmod: triflex 8448 0 [permanent]
lsmod: slc90e66 10112 0 [permanent]
lsmod: aec62xx 12288 0 [permanent]
lsmod: cmd64x 15308 0 [permanent]
lsmod: usb_storage 87104 0
lsmod: vga16fb 16280 2
lsmod: vgastate 12416 1 vga16fb
lsmod: usbserial 38640 0
lsmod: usbkbd 11776 0
lsmod: usbhid 44704 0
lsmod: thermal 19984 0
lsmod: processor 37608 1 thermal
lsmod: fan 9608 0
lsmod: generic 10244 0 [permanent]
lsmod: ide_core 146816 30 ide_disk,ide_cd,ide_generic,pdc202xx_new,sc1200,sis5513,opti621,amd74xx,piix,pdc202xx_old,it821x,siimage,atiixp,cy82c693,trm290,alim15x3,via82cxxx,hpt34x,ns87415,rz1000,cs5520,serverworks,jmicron,cs5530,triflex,slc90e66,aec62xx,cmd64x,usb_storage,generic
lsmod: parport_pc 41256 0
lsmod: parport 44044 1 parport_pc
lsmod: floppy 66728 0
lsmod: ehci_hcd 35720 0
lsmod: ohci_hcd 24452 0
lsmod: sata_nv 17028 0
lsmod: libata 106272 1 sata_nv
lsmod: scsi_mod 151984 2 usb_storage,libata
df: Filesystem 1k-blocks Used Available Use% Mounted on
df: tmpfs 965844 400 965444 0% /dev
df: tmpfs 965844 400 965444 0% /dev
df: tmpfs 965844 400 965444 0% /.dev
df: /dev/ide/host0/bus0/target0/lun0/cd 4556872 4556872 0 100% /cdrom
free: total used free shared buffers
free: Mem: 1931688 52100 1879588 0 6772
free: Swap: 0 0 0
free: Total: 1931688 52100 1879588
cardctl status: /usr/bin/report-hw: /usr/bin/report-hw: 50: cardctl: not found
cardctl ident: /usr/bin/report-hw: /usr/bin/report-hw: 51: cardctl: not found
/proc/cpuinfo: processor : 0
/proc/cpuinfo: vendor_id : AuthenticAMD
/proc/cpuinfo: cpu family : 15
/proc/cpuinfo: model : 67
/proc/cpuinfo: model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4600+
/proc/cpuinfo: stepping : 3
/proc/cpuinfo: cpu MHz : 2400.389
/proc/cpuinfo: cache size : 512 KB
/proc/cpuinfo: physical id : 0
/proc/cpuinfo: siblings : 2
/proc/cpuinfo: core id : 0
/proc/cpuinfo: cpu cores : 2
/proc/cpuinfo: fpu : yes
/proc/cpuinfo: fpu_exception : yes
/proc/cpuinfo: cpuid level : 1
/proc/cpuinfo: wp : yes
/proc/cpuinfo: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm cr8_legacy
/proc/cpuinfo: bogomips : 4806.40
/proc/cpuinfo: TLB size : 1024 4K pages
/proc/cpuinfo: clflush size : 64
/proc/cpuinfo: cache_alignment : 64
/proc/cpuinfo: address sizes : 40 bits physical, 48 bits virtual
/proc/cpuinfo: power management: ts fid vid ttp tm stc
/proc/cpuinfo:
/proc/cpuinfo: processor : 1
/proc/cpuinfo: vendor_id : AuthenticAMD
/proc/cpuinfo: cpu family : 15
/proc/cpuinfo: model : 67
/proc/cpuinfo: model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4600+
/proc/cpuinfo: stepping : 3
/proc/cpuinfo: cpu MHz : 2400.389
/proc/cpuinfo: cache size : 512 KB
/proc/cpuinfo: physical id : 0
/proc/cpuinfo: siblings : 2
/proc/cpuinfo: core id : 1
/proc/cpuinfo: cpu cores : 2
/proc/cpuinfo: fpu : yes
/proc/cpuinfo: fpu_exception : yes
/proc/cpuinfo: cpuid level : 1
/proc/cpuinfo: wp : yes
/proc/cpuinfo: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm cr8_legacy
/proc/cpuinfo: bogomips : 4800.27
/proc/cpuinfo: TLB size : 1024 4K pages
/proc/cpuinfo: clflush size : 64
/proc/cpuinfo: cache_alignment : 64
/proc/cpuinfo: address sizes : 40 bits physical, 48 bits virtual
/proc/cpuinfo: power management: ts fid vid ttp tm stc
/proc/cpuinfo:
/proc/ioports: 0000-001f : dma1
/proc/ioports: 0020-0021 : pic1
/proc/ioports: 0040-0043 : timer0
/proc/ioports: 0050-0053 : timer1
/proc/ioports: 0060-006f : keyboard
/proc/ioports: 0070-0077 : rtc
/proc/ioports: 0080-008f : dma page reg
/proc/ioports: 00a0-00a1 : pic2
/proc/ioports: 00c0-00df : dma2
/proc/ioports: 00f0-00ff : fpu
/proc/ioports: 01f0-01f7 : ide0
/proc/ioports: 0230-023f : pnp 00:0b
/proc/ioports: 0290-029f : pnp 00:0b
/proc/ioports: 0378-037a : parport0
/proc/ioports: 03c0-03df : vga+
/proc/ioports: 03f2-03f5 : floppy
/proc/ioports: 03f6-03f6 : ide0
/proc/ioports: 03f7-03f7 : floppy DIR
/proc/ioports: 03f8-03ff : serial
/proc/ioports: 0500-0503 : ACPI PM1a_EVT_BLK
/proc/ioports: 0504-0505 : ACPI PM1a_CNT_BLK
/proc/ioports: 0508-050b : ACPI PM_TMR
/proc/ioports: 0510-0515 : ACPI CPU throttle
/proc/ioports: 0520-0527 : ACPI GPE0_BLK
/proc/ioports: 0600-063f : 0000:00:01.1
/proc/ioports: 0700-073f : 0000:00:01.1
/proc/ioports: 08a0-08af : ACPI GPE1_BLK
/proc/ioports: 0900-09ff : 0000:00:01.0
/proc/ioports: 0a00-0a0f : pnp 00:0b
/proc/ioports: 0a10-0a1f : pnp 00:0b
/proc/ioports: 0cf8-0cff : PCI conf1
/proc/ioports: 0e00-0e3f : 0000:00:01.1
/proc/ioports: c880-c887 : 0000:00:0a.0
/proc/ioports: cc00-cc0f : 0000:00:09.0
/proc/ioports: cc00-cc0f : sata_nv
/proc/ioports: d000-d003 : 0000:00:09.0
/proc/ioports: d000-d003 : sata_nv
/proc/ioports: d080-d087 : 0000:00:09.0
/proc/ioports: d080-d087 : sata_nv
/proc/ioports: d400-d403 : 0000:00:09.0
/proc/ioports: d400-d403 : sata_nv
/proc/ioports: d480-d487 : 0000:00:09.0
/proc/ioports: d480-d487 : sata_nv
/proc/ioports: e000-efff : PCI Bus #02
/proc/ioports: ec00-ec7f : 0000:02:00.0
/proc/ioports: ffa0-ffaf : 0000:00:06.0
/proc/iomem: 00000000-0009ebff : System RAM
/proc/iomem: 00000000-00000000 : Crash kernel
/proc/iomem: 0009ec00-0009ffff : reserved
/proc/iomem: 000a0000-000bffff : Video RAM area
/proc/iomem: 000c0000-000ccfff : Video ROM
/proc/iomem: 000f0000-000fffff : System ROM
/proc/iomem: 00100000-77f8ffff : System RAM
/proc/iomem: 00200000-003e1f6e : Kernel code
/proc/iomem: 003e1f6f-004bafe7 : Kernel data
/proc/iomem: 77f90000-77f9dfff : ACPI Tables
/proc/iomem: 77f9e000-77fdffff : ACPI Non-volatile Storage
/proc/iomem: 77fe0000-77fedfff : reserved
/proc/iomem: 77ff0000-77ffffff : reserved
/proc/iomem: ce000000-dfffffff : PCI Bus #02
/proc/iomem: ce000000-cfffffff : 0000:02:00.0
/proc/iomem: d0000000-dfffffff : 0000:02:00.0
/proc/iomem: fcf76000-fcf77fff : 0000:00:09.0
/proc/iomem: fcf76000-fcf77fff : sata_nv
/proc/iomem: fcf78000-fcf7bfff : 0000:00:07.0
/proc/iomem: fcf7c000-fcf7cfff : 0000:00:0a.0
/proc/iomem: fcf7d000-fcf7dfff : 0000:00:04.0
/proc/iomem: fcf7d000-fcf7dfff : ohci_hcd
/proc/iomem: fcf7e000-fcf7efff : 0000:00:02.0
/proc/iomem: fcf7e000-fcf7efff : ohci_hcd
/proc/iomem: fcf7f000-fcf7f00f : 0000:00:0a.0
/proc/iomem: fcf7f400-fcf7f4ff : 0000:00:0a.0
/proc/iomem: fcf7f800-fcf7f8ff : 0000:00:04.1
/proc/iomem: fcf7f800-fcf7f8ff : ehci_hcd
/proc/iomem: fcf7fc00-fcf7fcff : 0000:00:02.1
/proc/iomem: fcf7fc00-fcf7fcff : ehci_hcd
/proc/iomem: fcf80000-fcffffff : 0000:00:01.3
/proc/iomem: fd000000-febfffff : PCI Bus #02
/proc/iomem: fd000000-fdffffff : 0000:02:00.0
/proc/iomem: febe0000-febfffff : 0000:02:00.0
/proc/iomem: fec00000-fec00fff : reserved
/proc/iomem: fee00000-feefffff : reserved
/proc/iomem: fff00000-ffffffff : reserved
/proc/interrupts: CPU0 CPU1
/proc/interrupts: 0: 46686 0 IO-APIC-edge timer
/proc/interrupts: 1: 49 0 IO-APIC-edge i8042
/proc/interrupts: 6: 3 0 IO-APIC-edge floppy
/proc/interrupts: 7: 0 0 IO-APIC-edge parport0
/proc/interrupts: 8: 1 0 IO-APIC-edge rtc
/proc/interrupts: 9: 0 0 IO-APIC-level acpi
/proc/interrupts: 14: 6846 0 IO-APIC-edge ide0
/proc/interrupts: 209: 0 0 IO-APIC-level libata, ohci_hcd:usb4
/proc/interrupts: 217: 2 0 IO-APIC-level ehci_hcd:usb1
/proc/interrupts: 225: 1 0 IO-APIC-level ehci_hcd:usb2
/proc/interrupts: 233: 22 0 IO-APIC-level ohci_hcd:usb3
/proc/interrupts: NMI: 60 34
/proc/interrupts: LOC: 46640 46626
/proc/interrupts: ERR: 0
/proc/interrupts: MIS: 0
/proc/meminfo: MemTotal: 1931688 kB
/proc/meminfo: MemFree: 1879420 kB
/proc/meminfo: Buffers: 6772 kB
/proc/meminfo: Cached: 15064 kB
/proc/meminfo: SwapCached: 0 kB
/proc/meminfo: Active: 16328 kB
/proc/meminfo: Inactive: 11236 kB
/proc/meminfo: HighTotal: 0 kB
/proc/meminfo: HighFree: 0 kB
/proc/meminfo: LowTotal: 1931688 kB
/proc/meminfo: LowFree: 1879420 kB
/proc/meminfo: SwapTotal: 0 kB
/proc/meminfo: SwapFree: 0 kB
/proc/meminfo: Dirty: 0 kB
/proc/meminfo: Writeback: 0 kB
/proc/meminfo: AnonPages: 5708 kB
/proc/meminfo: Mapped: 1508 kB
/proc/meminfo: Slab: 14712 kB
/proc/meminfo: PageTables: 280 kB
/proc/meminfo: NFS_Unstable: 0 kB
/proc/meminfo: Bounce: 0 kB
/proc/meminfo: CommitLimit: 965844 kB
/proc/meminfo: Committed_AS: 9624 kB
/proc/meminfo: VmallocTotal: 34359738367 kB
/proc/meminfo: VmallocUsed: 368 kB
/proc/meminfo: VmallocChunk: 34359737959 kB
/proc/bus/input/devices: I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
/proc/bus/input/devices: N: Name="AT Translated Set 2 keyboard"
/proc/bus/input/devices: P: Phys=isa0060/serio0/input0
/proc/bus/input/devices: S: Sysfs=/class/input/input0
/proc/bus/input/devices: H: Handlers=kbd
/proc/bus/input/devices: B: EV=120013
/proc/bus/input/devices: B: KEY=402000000 3802078f840d001 feffffdfffefffff fffffffffffffffe
/proc/bus/input/devices: B: MSC=10
/proc/bus/input/devices: B: LED=7
/proc/bus/input/devices:
/proc/bus/input/devices: I: Bus=0003 Vendor=046d Product=c002 Version=0120
/proc/bus/input/devices: N: Name="Logitech USB-PS/2 Mouse M-BA47"
/proc/bus/input/devices: P: Phys=usb-0000:00:02.0-1/input0
/proc/bus/input/devices: S: Sysfs=/class/input/input1
/proc/bus/input/devices: H: Handlers=mouse0
/proc/bus/input/devices: B: EV=7
/proc/bus/input/devices: B: KEY=f0000 0 0 0 0
/proc/bus/input/devices: B: REL=103
/proc/bus/input/devices:
dmidecode: /usr/bin/report-hw: /usr/bin/report-hw: 57: dmidecode: not found



~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Syslog of Installer

Syslog of Installer
Aug 8 14:23:42 syslogd started: BusyBox v1.1.3
Aug 8 14:23:42 kernel: klogd started: BusyBox v1.1.3 (Debian 1:1.1.3-4)
Aug 8 14:23:42 kernel: Bootdata ok (command line is vga=normal initrd=/install.amd/initrd.gz -- BOOT_IMAGE=/install.amd/vmlinuz )
Aug 8 14:23:42 kernel: Linux version 2.6.18-6-amd64 (Debian 2.6.18.dfsg.1-18) (dannf@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Sat Jan 26 08:39:14 UTC 2008
Aug 8 14:23:42 kernel: BIOS-provided physical RAM map:
Aug 8 14:23:42 kernel: BIOS-e820: 0000000000000000 - 000000000009ec00 (usable)
Aug 8 14:23:42 kernel: BIOS-e820: 000000000009ec00 - 00000000000a0000 (reserved)
Aug 8 14:23:42 kernel: BIOS-e820: 00000000000e3000 - 0000000000100000 (reserved)
Aug 8 14:23:42 kernel: BIOS-e820: 0000000000100000 - 0000000077f90000 (usable)
Aug 8 14:23:42 kernel: BIOS-e820: 0000000077f90000 - 0000000077f9e000 (ACPI data)
Aug 8 14:23:42 kernel: BIOS-e820: 0000000077f9e000 - 0000000077fe0000 (ACPI NVS)
Aug 8 14:23:42 kernel: BIOS-e820: 0000000077fe0000 - 0000000077fee000 (reserved)
Aug 8 14:23:42 kernel: BIOS-e820: 0000000077ff0000 - 0000000078000000 (reserved)
Aug 8 14:23:42 kernel: BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
Aug 8 14:23:42 kernel: BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
Aug 8 14:23:42 kernel: BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
Aug 8 14:23:42 kernel: DMI present.
Aug 8 14:23:42 kernel: ACPI: RSDP (v000 ACPIAM ) @ 0x00000000000fb6c0
Aug 8 14:23:42 kernel: ACPI: RSDT (v001 031108 RSDT0941 0x20080311 MSFT 0x00000097) @ 0x0000000077f90000
Aug 8 14:23:42 kernel: ACPI: FADT (v001 031108 FACP0941 0x20080311 MSFT 0x00000097) @ 0x0000000077f90200
Aug 8 14:23:42 kernel: ACPI: MADT (v001 031108 APIC0941 0x20080311 MSFT 0x00000097) @ 0x0000000077f90390
Aug 8 14:23:42 kernel: ACPI: MCFG (v001 031108 OEMMCFG 0x20080311 MSFT 0x00000097) @ 0x0000000077f90410
Aug 8 14:23:42 kernel: ACPI: OEMB (v001 031108 OEMB0941 0x20080311 MSFT 0x00000097) @ 0x0000000077f9e040
Aug 8 14:23:42 kernel: ACPI: HPET (v001 031108 OEMHPET0 0x20080311 MSFT 0x00000097) @ 0x0000000077f990c0
Aug 8 14:23:42 kernel: ACPI: NVHD (v001 031108 NVHDCP 0x20080311 MSFT 0x00000097) @ 0x0000000077f9e0c0
Aug 8 14:23:42 kernel: ACPI: SSDT (v001 A_M_I_ POWERNOW 0x00000001 AMD 0x00000001) @ 0x0000000077f99100
Aug 8 14:23:42 kernel: ACPI: DSDT (v001 A0931 A0931000 0x00000000 INTL 0x20051117) @ 0x0000000000000000
Aug 8 14:23:42 kernel: Scanning NUMA topology in Northbridge 24
Aug 8 14:23:42 kernel: Number of nodes 1
Aug 8 14:23:42 kernel: Node 0 MemBase 0000000000000000 Limit 0000000077f90000
Aug 8 14:23:42 kernel: NUMA: Using 63 for the hash shift.
Aug 8 14:23:42 kernel: Using node hash shift of 63
Aug 8 14:23:42 kernel: Bootmem setup node 0 0000000000000000-0000000077f90000
Aug 8 14:23:42 kernel: On node 0 totalpages: 483707
Aug 8 14:23:42 kernel: DMA zone: 3057 pages, LIFO batch:0
Aug 8 14:23:42 kernel: DMA32 zone: 480650 pages, LIFO batch:31
Aug 8 14:23:42 kernel: ACPI: PM-Timer IO Port: 0x508
Aug 8 14:23:42 kernel: ACPI: Local APIC address 0xfee00000
Aug 8 14:23:42 kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Aug 8 14:23:42 kernel: Processor #0 15:3 APIC version 16
Aug 8 14:23:42 kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Aug 8 14:23:42 kernel: Processor #1 15:3 APIC version 16
Aug 8 14:23:42 kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
Aug 8 14:23:42 kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
Aug 8 14:23:42 kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
Aug 8 14:23:42 kernel: IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
Aug 8 14:23:42 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Aug 8 14:23:42 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Aug 8 14:23:42 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
Aug 8 14:23:42 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
Aug 8 14:23:42 kernel: ACPI: IRQ0 used by override.
Aug 8 14:23:42 kernel: ACPI: IRQ2 used by override.
Aug 8 14:23:42 kernel: ACPI: IRQ9 used by override.
Aug 8 14:23:42 kernel: ACPI: IRQ14 used by override.
Aug 8 14:23:42 kernel: ACPI: IRQ15 used by override.
Aug 8 14:23:42 kernel: Setting APIC routing to physical flat
Aug 8 14:23:42 kernel: ACPI: HPET id: 0x10de8201 base: 0xfed00000
Aug 8 14:23:42 kernel: Using ACPI (MADT) for SMP configuration information
Aug 8 14:23:42 kernel: Allocating PCI resources starting at 80000000 (gap: 78000000:86c00000)
Aug 8 14:23:42 kernel: SMP: Allowing 4 CPUs, 2 hotplug CPUs
Aug 8 14:23:42 kernel: Built 1 zonelists. Total pages: 483707
Aug 8 14:23:42 kernel: Kernel command line: vga=normal initrd=/install.amd/initrd.gz -- BOOT_IMAGE=/install.amd/vmlinuz
Aug 8 14:23:42 kernel: Initializing CPU#0
Aug 8 14:23:42 kernel: PID hash table entries: 4096 (order: 12, 32768 bytes)
Aug 8 14:23:42 kernel: time.c: Using 25.000000 MHz WALL HPET GTOD HPET timer.
Aug 8 14:23:42 kernel: time.c: Detected 2400.389 MHz processor.
Aug 8 14:23:42 kernel: Console: colour VGA+ 80x25
Aug 8 14:23:42 kernel: Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Aug 8 14:23:42 kernel: Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Aug 8 14:23:42 kernel: Checking aperture...
Aug 8 14:23:42 kernel: CPU 0: aperture @ a02c000000 size 32 MB
Aug 8 14:23:42 kernel: Aperture too small (32 MB)
Aug 8 14:23:42 kernel: No AGP bridge found
Aug 8 14:23:42 kernel: Memory: 1927760k/1965632k available (1927k kernel code, 37480k reserved, 868k data, 176k init)
Aug 8 14:23:42 kernel: >Calibrating delay using timer specific routine.. 4806.40 BogoMIPS (lpj=9612805)
Aug 8 14:23:42 kernel: Security Framework v1.0.0 initialized
Aug 8 14:23:42 kernel: SELinux: Disabled at boot.
Aug 8 14:23:42 kernel: Capability LSM initialized
Aug 8 14:23:42 kernel: Mount-cache hash table entries: 256
Aug 8 14:23:42 kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
Aug 8 14:23:42 kernel: CPU: L2 Cache: 512K (64 bytes/line)
Aug 8 14:23:42 kernel: CPU 0/0 -> Node 0
Aug 8 14:23:42 kernel: CPU: Physical Processor ID: 0
Aug 8 14:23:42 kernel: CPU: Processor Core ID: 0
Aug 8 14:23:42 kernel: SMP alternatives: switching to UP code
Aug 8 14:23:42 kernel: ACPI: Core revision 20060707
Aug 8 14:23:42 kernel: Using local APIC timer interrupts.
Aug 8 14:23:42 kernel: result 12502038
Aug 8 14:23:42 kernel: Detected 12.502 MHz APIC timer.
Aug 8 14:23:42 kernel: SMP alternatives: switching to SMP code
Aug 8 14:23:42 kernel: Booting processor 1/2 APIC 0x1
Aug 8 14:23:42 kernel: Initializing CPU#1
Aug 8 14:23:42 kernel: Calibrating delay using timer specific routine.. 4800.27 BogoMIPS (lpj=9600548)
Aug 8 14:23:42 kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
Aug 8 14:23:42 kernel: CPU: L2 Cache: 512K (64 bytes/line)
Aug 8 14:23:42 kernel: CPU 1/1 -> Node 0
Aug 8 14:23:42 kernel: CPU: Physical Processor ID: 0
Aug 8 14:23:42 kernel: CPU: Processor Core ID: 1
Aug 8 14:23:42 kernel: AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ stepping 03
Aug 8 14:23:42 kernel: CPU 1: Syncing TSC to CPU 0.
Aug 8 14:23:42 kernel: CPU 1: synchronized TSC with CPU 0 (last diff 0 cycles, maxerr 518 cycles)
Aug 8 14:23:42 kernel: Brought up 2 CPUs
Aug 8 14:23:42 kernel: testing NMI watchdog ... OK.
Aug 8 14:23:42 kernel: migration_cost=232
Aug 8 14:23:42 kernel: checking if image is initramfs... it is
Aug 8 14:23:42 kernel: Freeing initrd memory: 3749k freed
Aug 8 14:23:42 kernel: NET: Registered protocol family 16
Aug 8 14:23:42 kernel: ACPI: bus type pci registered
Aug 8 14:23:42 kernel: PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
Aug 8 14:23:42 kernel: PCI: Not using MMCONFIG.
Aug 8 14:23:42 kernel: PCI: Using configuration type 1
Aug 8 14:23:42 kernel: ACPI: Interpreter enabled
Aug 8 14:23:42 kernel: ACPI: Using IOAPIC for interrupt routing
Aug 8 14:23:42 kernel: Error attaching device data
Aug 8 14:23:42 kernel: Error attaching device data
Aug 8 14:23:42 kernel: Error attaching device data
Aug 8 14:23:42 kernel: Error attaching device data
Aug 8 14:23:42 kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
Aug 8 14:23:42 kernel: PCI: Probing PCI hardware (bus 00)
Aug 8 14:23:42 kernel: PCI: Transparent bridge - 0000:00:08.0
Aug 8 14:23:42 kernel: Boot video device is 0000:02:00.0
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.IXVE._PRT]
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.BR10._PRT]
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.BR12._PRT]
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN0A] (IRQs 16 17 18 19) *10
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN0B] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN0C] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN0D] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN1A] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN1B] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN1C] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN1D] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN2A] (IRQs 16 17 18 19) *11
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN2B] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN2C] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN2D] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN3A] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN3B] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN3C] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN3D] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN4A] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN4B] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN4C] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN4D] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN5A] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN5B] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN5C] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN5D] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN6A] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: rupt Link [LN6B] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN6C] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN6D] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN7A] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN7B] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN7C] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN7D] (IRQs 16 17 18 19) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LUB0] (IRQs 20 21 22 23) *10
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LUB2] (IRQs 20 21 22 23) *15
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LMAC] (IRQs 20 21 22 23) *10
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LAZA] (IRQs 20 21 22 23) *15
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [SGRU] (IRQs 20 21 22 23) *15
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LSMB] (IRQs 20 21 22 23) *11
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LPMU] (IRQs 20 21 22 23) *10
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LSA0] (IRQs 20 21 22 23) *5
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LATA] (IRQs 20 21 22 23) *0, disabled.
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [UB11] (IRQs 20 21 22 23) *11
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [UB12] (IRQs 20 21 22 23) *10
Aug 8 14:23:42 kernel: Linux Plug and Play Support v0.97 (c) Adam Belay
Aug 8 14:23:42 kernel: pnp: PnP ACPI init
Aug 8 14:23:42 kernel: pnp: ACPI device : hid PNP0A03
Aug 8 14:23:42 kernel: pnp: ACPI device : hid PNP0200
Aug 8 14:23:42 kernel: pnp: ACPI device : hid PNP0800
Aug 8 14:23:42 kernel: pnp: ACPI device : hid PNP0C04
Aug 8 14:23:42 kernel: pnp: ACPI device : hid PNP0700
Aug 8 14:23:42 kernel: pnp: ACPI device : hid PNP0400
Aug 8 14:23:42 kernel: pnp: ACPI device : hid PNP0C02
Aug 8 14:23:42 kernel: pnp: ACPI device : hid PNP0103
Aug 8 14:23:42 kernel: pnp: ACPI device : hid PNP0B00
Aug 8 14:23:42 kernel: pnp: ACPI device : hid PNP0C02
Aug 8 14:23:42 kernel: pnp: ACPI device : hid PNP0303
Aug 8 14:23:42 kernel: pnp: ACPI device : hid PNP0C02
Aug 8 14:23:42 kernel: pnp: ACPI device : hid PNP0501
Aug 8 14:23:42 kernel: pnp: ACPI device : hid PNP0C02
Aug 8 14:23:42 kernel: pnp: ACPI device : hid PNP0C01
Aug 8 14:23:42 kernel: pnp: PnP ACPI: found 15 devices
Aug 8 14:23:42 kernel: usbcore: registered new driver usbfs
Aug 8 14:23:42 kernel: usbcore: registered new driver hub
Aug 8 14:23:42 kernel: PCI: Using ACPI for IRQ routing
Aug 8 14:23:42 kernel: PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
Aug 8 14:23:42 kernel: hpet0: at MMIO 0xfed00000 (virtual 0xffffffffff5fe000), IRQs 2, 8, 31
Aug 8 14:23:42 kernel: hpet0: 3 32-bit timers, 25000000 Hz
Aug 8 14:23:42 kernel: PCI-DMA: Disabling IOMMU.
Aug 8 14:23:42 kernel: pnp: the driver 'system' has been registered
Aug 8 14:23:42 kernel: pnp: match found with the PnP device '00:06' and the driver 'system'
Aug 8 14:23:42 kernel: pnp: match found with the PnP device '00:09' and the driver 'system'
Aug 8 14:23:42 kernel: pnp: match found with the PnP device '00:0b' and the driver 'system'
Aug 8 14:23:42 kernel: pnp: 00:0b: ioport range 0x230-0x23f has been reserved
Aug 8 14:23:42 kernel: pnp: 00:0b: ioport range 0x290-0x29f has been reserved
Aug 8 14:23:42 kernel: pnp: 00:0b: ioport range 0xa00-0xa0f has been reserved
Aug 8 14:23:42 kernel: pnp: 00:0b: ioport range 0xa10-0xa1f has been reserved
Aug 8 14:23:42 kernel: pnp: match found with the PnP device '00:0d' and the driver 'system'
Aug 8 14:23:42 kernel: pnp: match found with the PnP device '00:0e' and the driver 'system'
Aug 8 14:23:42 kernel: PCI: Bridge: 0000:00:08.0
Aug 8 14:23:42 kernel: IO window: disabled.
Aug 8 14:23:42 kernel: MEM window: disabled.
Aug 8 14:23:42 kernel: PREFETCH window: disabled.
Aug 8 14:23:42 kernel: PCI: Bridge: 0000:00:0b.0
Aug 8 14:23:42 kernel: IO window: e000-efff
Aug 8 14:23:42 kernel: MEM window: fd000000-febfffff
Aug 8 14:23:42 kernel: PREFETCH window: ce000000-dfffffff
Aug 8 14:23:42 kernel: PCI: Bridge: 0000:00:10.0
Aug 8 14:23:42 kernel: IO window: disabled.
Aug 8 14:23:42 kernel: MEM window: disabled.
Aug 8 14:23:42 kernel: PREFETCH window: disabled.
Aug 8 14:23:42 kernel: PCI: Bridge: 0000:00:12.0
Aug 8 14:23:42 kernel: IO window: disabled.
Aug 8 14:23:42 kernel: MEM window: disabled.
Aug 8 14:23:42 kernel: PREFETCH window: disabled.
Aug 8 14:23:42 kernel: PCI: Setting latency timer of device 0000:00:08.0 to 64
Aug 8 14:23:42 kernel: PCI: Setting latency timer of device 0000:00:0b.0 to 64
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN0A] enabled at IRQ 19
Aug 8 14:23:42 kernel: GSI 16 sharing vector 0xA9 and IRQ 16
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [LN0A] -> GSI 19 (level, low) -> IRQ 169
Aug 8 14:23:42 kernel: PCI: Setting latency timer of device 0000:00:10.0 to 64
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LN2A] enabled at IRQ 18
Aug 8 14:23:42 kernel: GSI 17 sharing vector 0xB1 and IRQ 17
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt 0000:00:12.0[A] -> Link [LN2A] -> GSI 18 (level, low) -> IRQ 177
Aug 8 14:23:42 kernel: PCI: Setting latency timer of device 0000:00:12.0 to 64
Aug 8 14:23:42 kernel: NET: Registered protocol family 2
Aug 8 14:23:42 kernel: IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
Aug 8 14:23:42 kernel: TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
Aug 8 14:23:42 kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Aug 8 14:23:42 kernel: TCP: Hash tables configured (established 262144 bind 65536)
Aug 8 14:23:42 kernel: ered
Aug 8 14:23:42 kernel: audit: initializing netlink socket (disabled)
Aug 8 14:23:42 kernel: audit(1218205421.480:1): initialized
Aug 8 14:23:42 kernel: VFS: Disk quotas dquot_6.5.1
Aug 8 14:23:42 kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Aug 8 14:23:42 kernel: Initializing Cryptographic API
Aug 8 14:23:42 kernel: io scheduler noop registered
Aug 8 14:23:42 kernel: io scheduler anticipatory registered
Aug 8 14:23:42 kernel: io scheduler deadline registered
Aug 8 14:23:42 kernel: io scheduler cfq registered (default)
Aug 8 14:23:42 kernel: PCI: Setting latency timer of device 0000:00:10.0 to 64
Aug 8 14:23:42 kernel: assign_interrupt_mode Found MSI capability
Aug 8 14:23:42 kernel: Allocate Port Service[0000:00:10.0:pcie00]
Aug 8 14:23:42 kernel: PCI: Setting latency timer of device 0000:00:12.0 to 64
Aug 8 14:23:42 kernel: assign_interrupt_mode Found MSI capability
Aug 8 14:23:42 kernel: Allocate Port Service[0000:00:12.0:pcie00]
Aug 8 14:23:42 kernel: Real Time Clock Driver v1.12ac
Aug 8 14:23:42 kernel: hpet_resources: 0xfed00000 is busy
Aug 8 14:23:42 kernel: Linux agpgart interface v0.101 (c) Dave Jones
Aug 8 14:23:42 kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
Aug 8 14:23:42 kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Aug 8 14:23:42 kernel: pnp: the driver 'serial' has been registered
Aug 8 14:23:42 kernel: pnp: match found with the PnP device '00:0c' and the driver 'serial'
Aug 8 14:23:42 kernel: 00:0c: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Aug 8 14:23:42 kernel: RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize
Aug 8 14:23:42 kernel: pnp: the driver 'i8042 kbd' has been registered
Aug 8 14:23:42 kernel: pnp: match found with the PnP device '00:0a' and the driver 'i8042 kbd'
Aug 8 14:23:42 kernel: pnp: the driver 'i8042 aux' has been registered
Aug 8 14:23:42 kernel: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
Aug 8 14:23:42 kernel: PNP: PS/2 controller doesn't have AUX irq; using default 12
Aug 8 14:23:42 kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Aug 8 14:23:42 kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Aug 8 14:23:42 kernel: mice: PS/2 mouse device common for all mice
Aug 8 14:23:42 kernel: TCP bic registered
Aug 8 14:23:42 kernel: NET: Registered protocol family 1
Aug 8 14:23:42 kernel: NET: Registered protocol family 17
Aug 8 14:23:42 kernel: NET: Registered protocol family 8
Aug 8 14:23:42 kernel: NET: Registered protocol family 20
Aug 8 14:23:42 kernel: ACPI: (supports S0 S1 S3 S4 S5)
Aug 8 14:23:42 kernel: Freeing unused kernel memory: 176k freed
Aug 8 14:23:42 kernel: input: AT Translated Set 2 keyboard as /class/input/input0
Aug 8 14:23:42 kernel: SCSI subsystem initialized
Aug 8 14:23:42 kernel: libata version 2.00 loaded.
Aug 8 14:23:42 kernel: sata_nv 0000:00:09.0: version 2.0
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 23
Aug 8 14:23:42 kernel: GSI 18 sharing vector 0xD1 and IRQ 18
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LSA0] -> GSI 23 (level, low) -> IRQ 209
Aug 8 14:23:42 kernel: PCI: Setting latency timer of device 0000:00:09.0 to 64
Aug 8 14:23:42 kernel: ata1: SATA max UDMA/133 cmd 0xD480 ctl 0xD402 bmdma 0xCC00 irq 209
Aug 8 14:23:42 kernel: ata2: SATA max UDMA/133 cmd 0xD080 ctl 0xD002 bmdma 0xCC08 irq 209
Aug 8 14:23:42 kernel: scsi0 : sata_nv
Aug 8 14:23:42 kernel: ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
Aug 8 14:23:42 kernel: Floppy drive(s): fd0 is 1.44M
Aug 8 14:23:42 kernel: pnp: the driver 'parport_pc' has been registered
Aug 8 14:23:42 kernel: pnp: match found with the PnP device '00:05' and the driver 'parport_pc'
Aug 8 14:23:42 kernel: parport: PnPBIOS parport detected.
Aug 8 14:23:42 kernel: parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
Aug 8 14:23:42 kernel: FDC 0 is a post-1991 82077
Aug 8 14:23:42 kernel: ata1: SATA link down (SStatus E3229F05 SControl 0)
Aug 8 14:23:42 kernel: scsi1 : sata_nv
Aug 8 14:23:42 kernel: ata2: SATA link down (SStatus 0 SControl 0)
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LUB2] enabled at IRQ 22
Aug 8 14:23:42 kernel: GSI 19 sharing vector 0xD9 and IRQ 19
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [LUB2] -> GSI 22 (level, low) -> IRQ 217
Aug 8 14:23:42 kernel: PCI: Setting latency timer of device 0000:00:02.1 to 64
Aug 8 14:23:42 kernel: ehci_hcd 0000:00:02.1: EHCI Host Controller
Aug 8 14:23:42 kernel: ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
Aug 8 14:23:42 kernel: ehci_hcd 0000:00:02.1: debug port 1
Aug 8 14:23:42 kernel: PCI: cache line size of 64 is not supported by device 0000:00:02.1
Aug 8 14:23:42 kernel: ehci_hcd 0000:00:02.1: irq 217, io mem 0xfcf7fc00
Aug 8 14:23:42 kernel: ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
Aug 8 14:23:42 kernel: usb usb1: configuration #1 chosen from 1 choice
Aug 8 14:23:42 kernel: hub 1-0:1.0: USB hub found
Aug 8 14:23:42 kernel: hub 1-0:1.0: 6 ports detected
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [UB12] enabled at IRQ 21
Aug 8 14:23:42 kernel: GSI 20 sharing vector 0xE1 and IRQ 20
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt 0000:00:04.1[B] -> Link [UB12] -> GSI 21 (level, low) -> IRQ 225
Aug 8 14:23:42 kernel: PCI: Setting latency timer of device 0000:00:04.1 to 64
Aug 8 14:23:42 kernel: ehci_hcd 0000:00:04.1: EHCI Host Controller
Aug 8 14:23:42 kernel: ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 2
Aug 8 14:23:42 kernel: ehci_hcd 0000:00:04.1: debug port 1
Aug 8 14:23:42 kernel: PCI: cache line size of 64 is not supported by device 0000:00:04.1
Aug 8 14:23:42 kernel: 4.1: irq 225, io mem 0xfcf7f800
Aug 8 14:23:42 kernel: ehci_hcd 0000:00:04.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
Aug 8 14:23:42 kernel: usb usb2: configuration #1 chosen from 1 choice
Aug 8 14:23:42 kernel: hub 2-0:1.0: USB hub found
Aug 8 14:23:42 kernel: hub 2-0:1.0: 6 ports detected
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [LUB0] enabled at IRQ 20
Aug 8 14:23:42 kernel: GSI 21 sharing vector 0xE9 and IRQ 21
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LUB0] -> GSI 20 (level, low) -> IRQ 233
Aug 8 14:23:42 kernel: PCI: Setting latency timer of device 0000:00:02.0 to 64
Aug 8 14:23:42 kernel: ohci_hcd 0000:00:02.0: OHCI Host Controller
Aug 8 14:23:42 kernel: ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 3
Aug 8 14:23:42 kernel: ohci_hcd 0000:00:02.0: irq 233, io mem 0xfcf7e000
Aug 8 14:23:42 kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Aug 8 14:23:42 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Aug 8 14:23:42 kernel: usb usb3: configuration #1 chosen from 1 choice
Aug 8 14:23:42 kernel: hub 3-0:1.0: USB hub found
Aug 8 14:23:42 kernel: hub 3-0:1.0: 6 ports detected
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt Link [UB11] enabled at IRQ 23
Aug 8 14:23:42 kernel: ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [UB11] -> GSI 23 (level, low) -> IRQ 209
Aug 8 14:23:42 kernel: PCI: Setting latency timer of device 0000:00:04.0 to 64
Aug 8 14:23:42 kernel: ohci_hcd 0000:00:04.0: OHCI Host Controller
Aug 8 14:23:42 kernel: ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 4
Aug 8 14:23:42 kernel: ohci_hcd 0000:00:04.0: irq 209, io mem 0xfcf7d000
Aug 8 14:23:42 kernel: usb usb4: configuration #1 chosen from 1 choice
Aug 8 14:23:42 kernel: hub 4-0:1.0: USB hub found
Aug 8 14:23:42 kernel: hub 4-0:1.0: 6 ports detected
Aug 8 14:23:42 kernel: ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707]
Aug 8 14:23:42 kernel: ACPI: Getting cpuindex for acpiid 0x3
Aug 8 14:23:42 kernel: ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707]
Aug 8 14:23:42 kernel: ACPI: Getting cpuindex for acpiid 0x4
Aug 8 14:23:42 kernel: usb 3-1: new low speed USB device using ohci_hcd and address 2
Aug 8 14:23:43 kernel: usb 3-1: configuration #1 chosen from 1 choice
Aug 8 14:23:43 kernel: usbcore: registered new driver hiddev
Aug 8 14:23:43 kernel: input: Logitech USB-PS/2 Mouse M-BA47 as /class/input/input1
Aug 8 14:23:43 kernel: input: USB HID v1.00 Mouse [Logitech USB-PS/2 Mouse M-BA47] on usb-0000:00:02.0-1
Aug 8 14:23:43 kernel: usbcore: registered new driver usbhid
Aug 8 14:23:43 kernel: drivers/usb/input/hid-core.c: v2.6:USB HID core driver
Aug 8 14:23:43 kernel: usbcore: registered new driver usbkbd
Aug 8 14:23:43 kernel: drivers/usb/input/usbkbd.c: :USB HID Boot Protocol keyboard driver
Aug 8 14:23:43 kernel: usbcore: registered new driver usbserial
Aug 8 14:23:43 kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
Aug 8 14:23:43 kernel: usbcore: registered new driver usbserial_generic
Aug 8 14:23:43 kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core
Aug 8 14:23:43 kernel: vga16fb: initializing
Aug 8 14:23:43 kernel: vga16fb: mapped to 0xffff8100000a0000
Aug 8 14:23:43 kernel: Console: switching to colour frame buffer device 80x30
Aug 8 14:23:43 kernel: fb0: VGA16 VGA frame buffer device
Aug 8 14:23:43 init: Starting pid 1222, console /dev/vc/1: '/sbin/debian-installer'
Aug 8 14:23:43 init: Starting pid 1230, console /dev/vc/4: '/usr/bin/tail'
Aug 8 14:23:43 debconf: Setting debconf/language to en
Aug 8 14:23:43 main-menu[1269]: DEBUG: resolver (libc6): package doesn't exist (ignored)
Aug 8 14:23:43 main-menu[1269]: DEBUG: resolver (dhcp-client-udeb): package doesn't exist (ignored)
Aug 8 14:23:43 main-menu[1269]: INFO: Menu item 'localechooser' selected
Aug 8 14:23:43 debconf: Setting debconf/language to en
Aug 8 14:23:53 localechooser: info: LANGNAME=English
Aug 8 14:23:53 localechooser: info: line=English;0;en;US;en_US.UTF-8;;kbd=lat0-sun16(utf8)
Aug 8 14:23:53 localechooser: info: Set debian-installer/language = 'en'
Aug 8 14:23:53 localechooser: info: Set debian-installer/locale = 'en_US.UTF-8'
Aug 8 14:23:53 localechooser: info: Set debian-installer/fallbacklocale = 'en_US.UTF-8'
Aug 8 14:23:53 localechooser: info: Set debian-installer/country = 'US'
Aug 8 14:23:53 localechooser: info: Set debian-installer/consoledisplay = 'kbd=lat0-sun16(utf8)'
Aug 8 14:23:53 debconf: Setting debconf/language to en
Aug 8 14:23:53 localechooser: info: Set debconf/language = 'en'
Aug 8 14:23:53 localechooser: info: Set countrychooser/country-name = 'United States'
Aug 8 14:23:55 localechooser: info: Set debian-installer/country = 'US'
Aug 8 14:23:55 localechooser: info: Set debian-installer/locale = 'en_US.UTF-8'
Aug 8 14:23:55 main-menu[1269]: DEBUG: resolver (libc6): package doesn't exist (ignored)
Aug 8 14:23:55 main-menu[1269]: DEBUG: resolver (dhcp-client-udeb): package doesn't exist (ignored)
Aug 8 14:23:55 main-menu[1269]: INFO: Menu item 'kbd-chooser' selected
Aug 8 14:23:55 main-menu[1269]: INFO: Falling back to the package description for console-keymaps-at
Aug 8 14:23:55 main-menu[1269]: INFO: Falling back to the package description for console-keymaps-at
Aug 8 14:23:55 kbd-chooser[1828]: DEBUG: Mounting usbdevfs to look for kbd
Aug 8 14:23:55 kbd-chooser[1828]: DEBUG: Parsing /proc/bus/usb/devices
Aug 8 14:23:55 kbd-chooser[1828]: DEBUG: Adding generic entry for AT keymaps
Aug 8 14:23:55 kbd-chooser[1828]: INFO: keyboard type at: present: true:
Aug 8 14:23:55 kbd-chooser[1828]: INFO: keyboard type at: present: unknown
Aug 8 14:23:55 kbd-chooser[1828]: INFO: Setting debian-installer/serial-console to false
Aug 8 14:23:55 kbd-chooser[1828]: INFO: Setting debian-installer/uml-console to false
Aug 8 14:23:55 kbd-chooser[1828]: INFO: kbd-chooser: arch at selected
Aug 8 14:23:56 kbd-chooser[1828]: INFO: choose_keymap: keymap = us
Aug 8 14:23:56 kbd-chooser[1828]: INFO: kbd_chooser: setting keymap us
Aug 8 14:23:56 main-menu[1269]: DEBUG: resolver (libc6): package doesn't exist (ignored)
Aug 8 14:23:56 main-menu[1269]: DEBUG: resolver (dhcp-client-udeb): package doesn't exist (ignored)
Aug 8 14:23:56 main-menu[1269]: INFO: Menu item 'cdrom-detect' selected
Aug 8 14:23:57 net/hw-detect.hotplug: Detected hotpluggable network interface lo
Aug 8 14:23:57 hw-detect: Detected module 'usb-storage' for 'USB storage'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/usb/storage/usb-storage.ko
Aug 8 14:23:57 kernel: Initializing USB Mass Storage driver...
Aug 8 14:23:57 kernel: usbcore: registered new driver usb-storage
Aug 8 14:23:57 kernel: USB Mass Storage support registered.
Aug 8 14:23:57 hw-detect: Detected module 'cmd64x' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/cmd64x.ko
Aug 8 14:23:57 hw-detect: Detected module 'aec62xx' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/aec62xx.ko
Aug 8 14:23:57 hw-detect: Detected module 'slc90e66' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/slc90e66.ko
Aug 8 14:23:57 hw-detect: Detected module 'triflex' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/triflex.ko
Aug 8 14:23:57 hw-detect: Detected module 'cs5530' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/cs5530.ko
Aug 8 14:23:57 hw-detect: Detected module 'jmicron' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/jmicron.ko
Aug 8 14:23:57 hw-detect: Detected module 'serverworks' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/serverworks.ko
Aug 8 14:23:57 hw-detect: Detected module 'cs5520' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/cs5520.ko
Aug 8 14:23:57 hw-detect: Detected module 'rz1000' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/rz1000.ko
Aug 8 14:23:57 hw-detect: Detected module 'ns87415' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/ns87415.ko
Aug 8 14:23:57 hw-detect: Detected module 'hpt34x' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/hpt34x.ko
Aug 8 14:23:57 hw-detect: Detected module 'via82cxxx' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/via82cxxx.ko
Aug 8 14:23:57 hw-detect: Detected module 'alim15x3' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/alim15x3.ko
Aug 8 14:23:57 hw-detect: Detected module 'trm290' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/trm290.ko
Aug 8 14:23:57 hw-detect: Detected module 'cy82c693' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/cy82c693.ko
Aug 8 14:23:57 hw-detect: Detected module 'atiixp' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/atiixp.ko
Aug 8 14:23:57 hw-detect: Detected module 'siimage' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/siimage.ko
Aug 8 14:23:57 hw-detect: Detected module 'it821x' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/it821x.ko
Aug 8 14:23:57 hw-detect: Detected module 'pdc202xx_old' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/pdc202xx_old.ko
Aug 8 14:23:57 hw-detect: Detected module 'piix' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/piix.ko
Aug 8 14:23:57 hw-detect: Detected module 'amd74xx' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/amd74xx.ko
Aug 8 14:23:57 hw-detect: Detected module 'opti621' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/opti621.ko
Aug 8 14:23:57 hw-detect: Detected module 'sis5513' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/sis5513.ko
Aug 8 14:23:57 hw-detect: Detected module 'sc1200' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/sc1200.ko
Aug 8 14:23:57 hw-detect: Detected module 'pdc202xx_new' for 'IDE chipset support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/pci/pdc202xx_new.ko
Aug 8 14:23:57 hw-detect: Detected module 'ide-generic' for 'Linux IDE support'
Aug 8 14:23:57 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/ide-generic.ko
Aug 8 14:23:57 kernel: Probing IDE interface ide0...
Aug 8 14:23:58 kernel: hda: BENQ DVD DD DW1640, ATAPI CD/DVD-ROM drive
Aug 8 14:23:59 kernel: Probing IDE interface ide1...
Aug 8 14:24:00 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Aug 8 14:24:00 hw-detect: Detected module 'ide-disk' for 'Linux ATA DISK'
Aug 8 14:24:00 kernel: hda: ATAPI 94X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache
Aug 8 14:24:00 kernel: Uniform CD-ROM driver Revision: 3.20
Aug 8 14:24:00 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/drivers/ide/ide-disk.ko
Aug 8 14:24:00 hw-detect: Detected module 'ide-cd' for 'Linux ATAPI CD-ROM'
Aug 8 14:24:00 hw-detect: Detected module 'isofs' for 'Linux ISO 9660 filesystem'
Aug 8 14:24:00 hw-detect: insmod /lib/modules/2.6.18-6-amd64/kernel/fs/isofs/isofs.ko
Aug 8 14:24:00 hw-detect: Loading PCMCIA bridge driver module: i82365
Aug 8 14:24:00 hw-detect: FATAL: Module i82365 not found.
Aug 8 14:24:00 apt-install: Queueing package udev for later installation
Aug 8 14:24:00 apt-install: Queueing package usbutils for later installation
Aug 8 14:24:00 apt-install: Queueing package acpi for later installation
Aug 8 14:24:00 apt-install: Queueing package acpid for later installation
Aug 8 14:24:00 hw-detect: Missing modules 'ide-mod (Linux IDE driver), ide-probe-mod (Linux IDE probe driver), ide-detect (Linux IDE detection), ide-floppy (Linux IDE floppy)
Aug 8 14:24:00 net/hw-detect.hotplug: Detected hotpluggable network interface lo
Aug 8 14:24:00 cdrom-detect: Searching for Debian installation media...
Aug 8 14:24:00 kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Aug 8 14:24:00 kernel: ISO 9660 Extensions: RRIP_1991A
Aug 8 14:24:00 cdrom-detect: CD-ROM mount succeeded: device=/dev/ide/host0/bus0/target0/lun0/cd
Aug 8 14:24:00 cdrom-detect: Detected CD 'Debian GNU/Linux 4.0 r3 "Etch" - Official amd64 DVD Binary-1 20080217-12:13'
Aug 8 14:25:19 cdrom-detect: Detected CD with 'stable' (etch) distribution
Aug 8 14:25:19 apt-install: Queueing package eject for later installation
Aug 8 14:25:19 anna-install: Queueing udeb apt-mirror-setup for later installation
Aug 8 14:25:19 anna-install: Queueing udeb apt-cdrom-setup for later installation
Aug 8 14:25:19 main-menu[1269]: DEBUG: resolver (libc6): package doesn't exist (ignored)
Aug 8 14:25:19 main-menu[1269]: DEBUG: resolver (dhcp-client-udeb): package doesn't exist (ignored)
Aug 8 14:25:19 main-menu[1269]: INFO: Menu item 'load-cdrom' selected
Aug 8 14:25:19 cdrom-retriever: warning: Unable to find contrib/debian-installer/binary-amd64/Packages in /cdrom/dists/etch/Release.
Aug 8 14:25:19 cdrom-retriever: warning: Unable to find contrib/debian-installer/binary-amd64/Packages.gz in /cdrom/dists/etch/Release.
Aug 8 14:25:20 anna[5022]: DEBUG: install hw-detect, enhances installed packages hw-detect
Aug 8 14:25:20 anna[5022]: DEBUG: install apt-cdrom-setup, queued by anna-install
Aug 8 14:25:20 anna[5022]: DEBUG: install apt-mirror-setup, queued by anna-install
Aug 8 14:25:20 anna[5022]: DEBUG: install apt-setup-udeb, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install base-installer, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for choose-mirror, is menu item
Aug 8 14:25:20 anna[5022]: DEBUG: install clock-setup, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for crc-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: ask for crypto-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: install di-utils-mapdevfs, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for disk-detect, is menu item
Aug 8 14:25:20 anna[5022]: DEBUG: ask for eject-udeb, is menu item
Aug 8 14:25:20 anna[5022]: DEBUG: ask for ext2-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: install ext2-modules-2.6.18-6-amd64-di, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for ext3-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: install ext3-modules-2.6.18-6-amd64-di, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install finish-install, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install grub-installer, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for ipv6-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: ask for irda-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: ask for jfs-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: install jfs-modules-2.6.18-6-amd64-di, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install lilo-installer, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for loop-aes-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: ask for loop-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: install loop-modules-2.6.18-6-amd64-di, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for lowmem, is menu item
Aug 8 14:25:20 anna[5022]: DEBUG: ask for md-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: install mkreiserfs-udeb, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for network-console, is menu item
Aug 8 14:25:20 anna[5022]: DEBUG: install network-preseed, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for nic-extra-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: install nic-extra-modules-2.6.18-6-amd64-di, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for nic-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: install nic-modules-2.6.18-6-amd64-di, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for nic-pcmcia-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: install nic-pcmcia-modules-2.6.18-6-amd64-di, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for nic-shared-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: install nic-shared-modules-2.6.18-6-amd64-di, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for nic-usb-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: install nic-usb-modules-2.6.18-6-amd64-di, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install nobootloader, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for ntfs-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: ask for openssh-client-udeb, is menu item
Aug 8 14:25:20 anna[5022]: DEBUG: install partman-auto, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install partman-auto-crypto, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install partman-auto-lvm, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install partman-auto-raid, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install partman-base, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install partman-basicfilesystems, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install partman-crypto, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install partman-ext3, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install partman-jfs, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install partman-lvm, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install partman-md, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install partman-reiserfs, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install partman-target, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install partman-xfs, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install pkgsel, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for plip-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: ask for ppp-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: ask for ppp-udeb, is menu item
Aug 8 14:25:20 anna[5022]: DEBUG: ask for qnx4-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: ask for reiserfs-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: install reiserfs-modules-2.6.18-6-amd64-di, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for rescue-mode, is menu item
Aug 8 14:25:20 anna[5022]: DEBUG: ask for scsi-extra-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: install scsi-extra-modules-2.6.18-6-amd64-di, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: install tzsetup-udeb, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for ufs-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: install user-setup-udeb, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: ask for xfs-modules-2.6.18-6-amd64-di, matches kernel
Aug 8 14:25:20 anna[5022]: DEBUG: install xfs-modules-2.6.18-6-amd64-di, priority >= standard
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (apt-cdrom-setup): accept cdrom-detect, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (apt-cdrom-setup): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (choose-mirror-bin): accept libdebconfclient0-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (choose-mirror-bin): accept libdebian-installer4-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (choose-mirror-bin): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (apt-mirror-setup): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (base-installer): accept libdebconfclient0-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (base-installer): accept libdebian-installer4-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-base): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-partitioning): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-target): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-basicfilesystems): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (ext2-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (ext2-modules-2.6.18-6-amd64-di): accept core-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (fat-modules): package doesn't exist (ignored)
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-basicfilesystems): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-basicmethods): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (di-utils-mapdevfs): accept libdebian-installer4-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-base): accept archdetect, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (disk-detect): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (disk-detect): accept hw-detect, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (disk-detect): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-base): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (base-installer): accept archdetect, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (base-installer): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (base-installer): accept rootskel, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (apt-setup-udeb): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (clock-setup): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (os-prober-udeb): accept anna, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (tzsetup-udeb): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (tzsetup-udeb): accept localechooser, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (ethdetect): accept rootskel, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (ethdetect): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (ethdetect): accept hw-detect, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (ethdetect): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (ext3-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (ext3-modules-2.6.18-6-amd64-di): accept core-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (finish-install): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (finish-install): accept archdetect, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (grub-installer): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (grub-installer): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (jfs-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (lilo-installer): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (lilo-installer): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (loop-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (netcfg): accept libdebconfclient0-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (netcfg): accept libdebian-installer4-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (netcfg): accept libiw28-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (netcfg): accept ethdetect, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (network-preseed): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (network-preseed): accept netcfg, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (network-preseed): accept preseed-common, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-extra-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-shared-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-extra-modules-2.6.18-6-amd64-di): accept core-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (crc-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-modules-2.6.18-6-amd64-di): accept core-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-modules-2.6.18-6-amd64-di): accept firewire-core-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-pcmcia-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-pcmcia-modules-2.6.18-6-amd64-di): accept pcmcia-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-usb-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-usb-modules-2.6.18-6-amd64-di): accept usb-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-usb-modules-2.6.18-6-amd64-di): accept core-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nobootloader): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-auto): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-auto): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-ext3): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-ext3): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-auto-crypto): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-auto-lvm): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-lvm): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-lvm): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (md-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-auto-lvm): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-crypto): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-auto-raid): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-md): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (mdcfg-utils): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (mdcfg-utils): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partconf-find-partitions): accept libdebian-installer4-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-jfs): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-jfs): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-reiserfs): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (reiserfs-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-reiserfs): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-xfs): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (xfs-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-xfs): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (pcmciautils-udeb): accept udev-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (pcmciautils-udeb): accept libsysfs2-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (pkgsel): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (pkgsel): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (scsi-extra-modules-2.6.18-6-amd64-di): accept scsi-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (scsi-extra-modules-2.6.18-6-amd64-di): accept scsi-core-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (user-setup-udeb): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (wireless-tools-udeb): accept libiw28-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (apt-cdrom-setup): accept cdrom-detect, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (apt-cdrom-setup): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (choose-mirror-bin): accept libdebconfclient0-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (choose-mirror-bin): accept libdebian-installer4-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (choose-mirror-bin): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (apt-mirror-setup): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (base-installer): accept libdebconfclient0-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (base-installer): accept libdebian-installer4-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-base): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-partitioning): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-target): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-basicfilesystems): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (ext2-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (ext2-modules-2.6.18-6-amd64-di): accept core-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (fat-modules): package doesn't exist (ignored)
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-basicfilesystems): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-basicmethods): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (di-utils-mapdevfs): accept libdebian-installer4-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-base): accept archdetect, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (disk-detect): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (disk-detect): accept hw-detect, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (disk-detect): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-base): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (base-installer): accept archdetect, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (base-installer): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (base-installer): accept rootskel, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (apt-setup-udeb): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (clock-setup): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (os-prober-udeb): accept anna, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (tzsetup-udeb): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (tzsetup-udeb): accept localechooser, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (crc-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (ethdetect): accept rootskel, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (ethdetect): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (ethdetect): accept hw-detect, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (ethdetect): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (ext3-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (ext3-modules-2.6.18-6-amd64-di): accept core-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (finish-install): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (finish-install): accept archdetect, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (grub-installer): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (grub-installer): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (jfs-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (lilo-installer): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (lilo-installer): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (loop-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (md-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (mdcfg-utils): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (mdcfg-utils): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partconf-find-partitions): accept libdebian-installer4-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (netcfg): accept libdebconfclient0-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (netcfg): accept libdebian-installer4-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (netcfg): accept libiw28-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (netcfg): accept ethdetect, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (network-preseed): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (network-preseed): accept netcfg, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (network-preseed): accept preseed-common, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-extra-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-shared-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-extra-modules-2.6.18-6-amd64-di): accept core-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-modules-2.6.18-6-amd64-di): accept core-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-modules-2.6.18-6-amd64-di): accept firewire-core-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-pcmcia-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-pcmcia-modules-2.6.18-6-amd64-di): accept pcmcia-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-usb-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-usb-modules-2.6.18-6-amd64-di): accept usb-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nic-usb-modules-2.6.18-6-amd64-di): accept core-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (nobootloader): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-auto): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-auto): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-ext3): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-ext3): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-auto-crypto): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-auto-lvm): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-lvm): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-lvm): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-auto-lvm): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-crypto): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-auto-raid): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-md): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-jfs): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-jfs): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-reiserfs): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (reiserfs-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-reiserfs): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-xfs): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (xfs-modules-2.6.18-6-amd64-di): accept kernel-image-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (partman-xfs): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (pcmciautils-udeb): accept udev-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (pcmciautils-udeb): accept libsysfs2-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (pkgsel): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (pkgsel): accept di-utils, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (scsi-extra-modules-2.6.18-6-amd64-di): accept scsi-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (scsi-extra-modules-2.6.18-6-amd64-di): accept scsi-core-modules-2.6.18-6-amd64-di, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (user-setup-udeb): accept cdebconf-udeb, already installed
Aug 8 14:25:20 anna[5022]: DEBUG: resolver (wireless-tools-udeb): accept libiw28-udeb, already installed
Aug 8 14:25:20 kernel: hda: cdrom_read_intr: Bad transfer size 65534
Aug 8 14:25:20 kernel: Trying to limit transfer sizes
Aug 8 14:25:20 kernel: end_request: I/O error, dev hda, sector 6744124
Aug 8 14:25:20 kernel: Buffer I/O error on device hda, logical block 1686031
Aug 8 14:25:20 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:20 kernel: ide: failed opcode was: unknown
Aug 8 14:25:20 kernel: hda: drive not ready for command
Aug 8 14:25:20 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:20 kernel: ide: failed opcode was: unknown
Aug 8 14:25:20 kernel: hda: drive not ready for command
Aug 8 14:25:20 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:20 kernel: ide: failed opcode was: unknown
Aug 8 14:25:20 kernel: hda: drive not ready for command
Aug 8 14:25:20 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:20 kernel: ide: failed opcode was: unknown
Aug 8 14:25:20 kernel: hda: drive not ready for command
Aug 8 14:25:20 kernel: hda: ATAPI reset complete
Aug 8 14:25:20 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:20 kernel: ide: failed opcode was: unknown
Aug 8 14:25:20 kernel: hda: drive not ready for command
Aug 8 14:25:20 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:20 kernel: ide: failed opcode was: unknown
Aug 8 14:25:20 kernel: hda: drive not ready for command
Aug 8 14:25:20 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:20 kernel: ide: failed opcode was: unknown
Aug 8 14:25:20 kernel: hda: drive not ready for command
Aug 8 14:25:20 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:20 kernel: ide: failed opcode was: unknown
Aug 8 14:25:20 kernel: hda: drive not ready for command
Aug 8 14:25:20 kernel: hda: ATAPI reset complete
Aug 8 14:25:20 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:20 kernel: ide: failed opcode was: unknown
Aug 8 14:25:20 kernel: end_request: I/O error, dev hda, sector 6744128
Aug 8 14:25:20 kernel: Buffer I/O error on device hda, logical block 1686032
Aug 8 14:25:20 kernel: hda: drive not ready for command
Aug 8 14:25:20 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:20 kernel: ide: failed opcode was: unknown
Aug 8 14:25:20 kernel: hda: drive not ready for command
Aug 8 14:25:20 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:20 kernel: ide: failed opcode was: unknown
Aug 8 14:25:20 kernel: hda: drive not ready for command
Aug 8 14:25:20 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:20 kernel: ide: failed opcode was: unknown
Aug 8 14:25:20 kernel: hda: drive not ready for command
Aug 8 14:25:20 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:20 kernel: ide: failed opcode was: unknown
Aug 8 14:25:20 kernel: hda: drive not ready for command
Aug 8 14:25:20 kernel: hda: ATAPI reset complete
Aug 8 14:25:20 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:20 kernel: ide: failed opcode was: unknown
Aug 8 14:25:20 kernel: hda: drive not ready for command
Aug 8 14:25:20 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:20 kernel: ide: failed opcode was: unknown
Aug 8 14:25:20 kernel: hda: drive not ready for command
Aug 8 14:25:20 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:20 kernel: ide: failed opcode was: unknown
Aug 8 14:25:20 kernel: hda: drive not ready for command
Aug 8 14:25:20 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:20 kernel: ide: failed opcode was: unknown
Aug 8 14:25:20 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: end_request: I/O error, dev hda, sector 6744132
Aug 8 14:25:21 kernel: Buffer I/O error on device hda, logical block 1686033
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: end_request: I/O error, dev hda, sector 6744136
Aug 8 14:25:21 kernel: Buffer I/O error on device hda, logical block 1686034
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: end_request: I/O error, dev hda, sector 6744140
Aug 8 14:25:21 kernel: Buffer I/O error on device hda, logical block 1686035
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: end_request: I/O error, dev hda, sector 6744144
Aug 8 14:25:21 kernel: Buffer I/O error on device hda, logical block 1686036
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: end_request: I/O error, dev hda, sector 6744148
Aug 8 14:25:21 kernel: Buffer I/O error on device hda, logical block 1686037
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: end_request: I/O error, dev hda, sector 6744152
Aug 8 14:25:21 kernel: Buffer I/O error on device hda, logical block 1686038
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: end_request: I/O error, dev hda, sector 6744156
Aug 8 14:25:21 kernel: Buffer I/O error on device hda, logical block 1686039
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: end_request: I/O error, dev hda, sector 6744160
Aug 8 14:25:21 kernel: Buffer I/O error on device hda, logical block 1686040
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: end_request: I/O error, dev hda, sector 6744164
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: end_request: I/O error, dev hda, sector 6744168
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: ATAPI reset complete
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: end_request: I/O error, dev hda, sector 6744172
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:21 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:21 kernel: ide: failed opcode was: unknown
Aug 8 14:25:21 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: end_request: I/O error, dev hda, sector 6744176
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: end_request: I/O error, dev hda, sector 6744180
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: end_request: I/O error, dev hda, sector 6744184
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: end_request: I/O error, dev hda, sector 6744188
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: end_request: I/O error, dev hda, sector 6744192
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: end_request: I/O error, dev hda, sector 6744196
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: end_request: I/O error, dev hda, sector 6744200
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: end_request: I/O error, dev hda, sector 6744204
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: end_request: I/O error, dev hda, sector 6744208
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: end_request: I/O error, dev hda, sector 6744212
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: ATAPI reset complete
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:22 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:22 kernel: ide: failed opcode was: unknown
Aug 8 14:25:22 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: end_request: I/O error, dev hda, sector 6744216
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: end_request: I/O error, dev hda, sector 6744220
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: end_request: I/O error, dev hda, sector 6744224
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: end_request: I/O error, dev hda, sector 6744228
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: end_request: I/O error, dev hda, sector 6744232
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: end_request: I/O error, dev hda, sector 6744236
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: end_request: I/O error, dev hda, sector 6744240
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: end_request: I/O error, dev hda, sector 6744244
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: end_request: I/O error, dev hda, sector 6744248
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: end_request: I/O error, dev hda, sector 6744252
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: ATAPI reset complete
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: end_request: I/O error, dev hda, sector 6744256
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:23 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:23 kernel: ide: failed opcode was: unknown
Aug 8 14:25:23 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: end_request: I/O error, dev hda, sector 6744260
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: end_request: I/O error, dev hda, sector 6744264
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: end_request: I/O error, dev hda, sector 6744268
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: end_request: I/O error, dev hda, sector 6744272
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: end_request: I/O error, dev hda, sector 6744276
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: end_request: I/O error, dev hda, sector 6744280
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: end_request: I/O error, dev hda, sector 6744284
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: end_request: I/O error, dev hda, sector 6744288
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: end_request: I/O error, dev hda, sector 6744292
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: ATAPI reset complete
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: end_request: I/O error, dev hda, sector 6744296
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:24 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:24 kernel: ide: failed opcode was: unknown
Aug 8 14:25:24 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: end_request: I/O error, dev hda, sector 6744300
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: end_request: I/O error, dev hda, sector 6744304
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: end_request: I/O error, dev hda, sector 6744308
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: end_request: I/O error, dev hda, sector 6744312
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: end_request: I/O error, dev hda, sector 6744316
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: end_request: I/O error, dev hda, sector 6744320
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: end_request: I/O error, dev hda, sector 6744324
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: end_request: I/O error, dev hda, sector 6744328
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: end_request: I/O error, dev hda, sector 6744332
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: end_request: I/O error, dev hda, sector 6744336
Aug 8 14:25:25 kernel: printk: 43 messages suppressed.
Aug 8 14:25:25 kernel: Buffer I/O error on device hda, logical block 1686084
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: ATAPI reset complete
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:25 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:25 kernel: ide: failed opcode was: unknown
Aug 8 14:25:25 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: ATAPI reset complete
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: end_request: I/O error, dev hda, sector 6744340
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: ATAPI reset complete
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: ATAPI reset complete
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: end_request: I/O error, dev hda, sector 6744344
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: ATAPI reset complete
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: ATAPI reset complete
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: end_request: I/O error, dev hda, sector 6744348
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: ATAPI reset complete
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: ATAPI reset complete
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: end_request: I/O error, dev hda, sector 6744352
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: ATAPI reset complete
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: ATAPI reset complete
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: end_request: I/O error, dev hda, sector 6744124
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: ATAPI reset complete
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 kernel: hda: ATAPI reset complete
Aug 8 14:25:26 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 8 14:25:26 kernel: ide: failed opcode was: unknown
Aug 8 14:25:26 kernel: end_request: I/O error, dev hda, sector 6744128
Aug 8 14:25:26 kernel: hda: drive not ready for command
Aug 8 14:25:26 anna[5022]: WARNING **: bad md5sum
Aug 8 14:25:40 main-menu[1269]: WARNING **: Configuring 'load-cdrom' failed with error code 7
Aug 8 14:25:40 main-menu[1269]: WARNING **: Menu item 'load-cdrom' failed.
Aug 8 14:25:44 main-menu[1269]: INFO: Modifying debconf priority limit from 'high' to 'medium'
Aug 8 14:25:44 debconf: Setting debconf/priority to medium
Aug 8 14:25:44 main-menu[1269]: DEBUG: resolver (libc6): package doesn't exist (ignored)
Aug 8 14:25:44 main-menu[1269]: DEBUG: resolver (dhcp-client-udeb): package doesn't exist (ignored)
Aug 8 14:25:44 main-menu[1269]: DEBUG: resolver (choose-mirror-bin): package doesn't exist (ignored)
Aug 8 14:25:44 main-menu[1269]: DEBUG: resolver (base-installer): package doesn't exist (ignored)
Aug 8 14:26:19 main-menu[1269]: INFO: Falling back to the package description for auto-install
Aug 8 14:26:19 main-menu[1269]: INFO: Falling back to the package description for ai-choosers
Aug 8 14:26:19 main-menu[1269]: INFO: Menu item 'save-logs' selected



~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Status of Installer

Status of Installer
Package: preseed-common
Status: install ok unpacked
Version: 1.28
Depends: cdebconf-udeb, di-utils (>= 1.14)
Description: common files for preseeding

Package: udpkg
Status: install ok unpacked
Version: 1.04
Depends: libc6 (>= 2.3.5-1), libdebian-installer4-udeb (>= 0.41)
Description: tiny dpkg clone

Package: localechooser
Status: install ok installed
Version: 1.37
Depends: cdebconf-udeb, iso-3166-udeb, di-utils (>= 1.15)
Description: choose language/country/locale
Installer-Menu-Item: 10

Package: libnss-dns-udeb
Status: install ok unpacked
Version: 2.3.6.ds1-13etch5
Description: GNU C Library: NSS helper for DNS - udeb

Package: cdrom-checker
Status: install ok unpacked
Version: 1.11
Depends: cdrom-detect, cdebconf-udeb (>= 0.31)
Description: Verify the cd contents
Installer-Menu-Item: 940

Package: lowmemcheck
Status: install ok unpacked
Version: 1.25
Depends: cdebconf-udeb (>= 0.75), main-menu (>= 1.03)
Description: detect low-memory systems and enter lowmem mode

Package: cdrom-retriever
Status: install ok installed
Version: 1.14
Provides: retriever
Depends: cdebconf-udeb, cdrom-detect
Description: Fetch modules from a CDROM

Package: main-menu
Status: install ok unpacked
Version: 1.18
Depends: libc6 (>= 2.3.5-1), libdebconfclient0-udeb, libdebian-installer4-udeb (>= 0.49), cdebconf-udeb
Description: Debian installer main menu

Package: di-utils-shell
Status: install ok unpacked
Version: 1.45etch1
Depends: cdebconf-udeb, di-utils (>= 1.18)
Description: Execute a shell
Installer-Menu-Item: 950

Package: usb-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: usb-modules
Depends: kernel-image-2.6.18-6-amd64-di
Description: USB support

Package: di-utils
Status: install ok installed
Version: 1.45etch1
Depends: libc6 (>= 2.3.5-1), libdebian-installer4-udeb (>= 0.50), cdebconf-udeb
Description: Miscellaneous utilities for the debian installer

Package: input-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: input-modules
Depends: kernel-image-2.6.18-6-amd64-di, usb-modules-2.6.18-6-amd64-di
Description: Input devices support

Package: fb-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: fb-modules
Depends: kernel-image-2.6.18-6-amd64-di
Description: Frame buffer support

Package: cdebconf-newt-udeb
Status: install ok unpacked
Version: 0.114etch1
Depends: cdebconf-udeb, di-utils-terminfo, libc6 (>= 2.3.5-1), libnewt0.52
Description: Newt frontend for Debian Configuration Management System

Package: pcmcia-storage-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: pcmcia-storage-modules
Depends: kernel-image-2.6.18-6-amd64-di, ide-core-modules-2.6.18-6-amd64-di, cdrom-core-modules-2.6.18-6-amd64-di, pcmcia-modules-2.6.18-6-amd64-di
Description: PCMCIA storage drivers

Package: parport-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: parport-modules
Depends: kernel-image-2.6.18-6-amd64-di
Description: Parallel port support

Package: module-init-tools-udeb
Status: install ok unpacked
Version: 3.3-pre4-2
Depends: libc6 (>= 2.3.5-1)
Description: tools for managing Linux kernel modules

Package: rootskel
Status: install ok installed
Version: 1.50+b1
Depends: di-utils (>= 1.43), cdebconf-udeb
Description: Skeleton root filesystem used by debian-installer

Package: ide-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: ide-modules
Depends: kernel-image-2.6.18-6-amd64-di, ide-core-modules-2.6.18-6-amd64-di
Description: IDE drivers

Package: udev-udeb
Status: install ok unpacked
Version: 0.105-4
Depends: libc6 (>= 2.3.5-1)
Description: /dev/ and hotplug management daemon

Package: acpi-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: acpi-modules
Depends: kernel-image-2.6.18-6-amd64-di
Description: ACPI support modules

Package: cdrom-core-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: cdrom-core-modules
Depends: kernel-image-2.6.18-6-amd64-di, scsi-core-modules-2.6.18-6-amd64-di, ide-modules-2.6.18-6-amd64-di
Description: CDROM support

Package: core-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: core-modules
Depends: kernel-image-2.6.18-6-amd64-di
Description: Core modules

Package: brltty-udeb
Status: install ok unpacked
Version: 3.7.2-7.1
Depends: libc6 (>= 2.3.5-1)
Description: Access software for a blind person using a soft braille terminal

Package: kernel-image-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: kernel-image
Description: Linux kernel binary image for the Debian installer

Package: libfribidi0-udeb
Status: install ok unpacked
Version: 0.10.7-4
Depends: libc6 (>= 2.3.5-1)
Description: Free Implementation of the Unicode BiDi algorithm

Package: libtextwrap1-udeb
Status: install ok installed
Version: 0.1-5
Depends: libc6 (>= 2.3.5-1)
Description: text-wrapping library with i18n - runtime udeb

Package: auto-install
Status: install ok unpacked
Version: 0.03
Depends: cdebconf-udeb, netcfg, preseed-common (>= 1.18)
Description: Support for automatic installs
Installer-Menu-Item: 19

Package: usb-discover
Status: install ok unpacked
Version: 1.06
Depends: cdebconf-udeb
Description: Discover USB and load kernel modules

Package: ide-core-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: ide-core-modules
Depends: kernel-image-2.6.18-6-amd64-di
Description: IDE support

Package: rescue-check
Status: install ok unpacked
Version: 1.9
Depends: cdebconf-udeb (>= 0.75), main-menu (>= 1.03), di-utils (>= 1.18)
Description: enter d-i rescue mode if requested

Package: nano-udeb
Status: install ok unpacked
Version: 2.0.2-1etch1
Provides: editor
Depends: libc6 (>= 2.3.5-1), libslang2-udeb (>= 2.0.6-3)
Description: free Pico clone with some new features - tiny build

Package: cdebconf-udeb
Status: install ok installed
Version: 0.114etch1
Provides: debconf-2.0
Depends: libc6 (>= 2.3.5-1), libdebian-installer4-udeb (>= 0.50), libtextwrap1-udeb
Description: Debian Configuration Management System (C-implementation)

Package: floppy-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: floppy-modules
Depends: kernel-image-2.6.18-6-amd64-di
Description: Floppy driver

Package: ai-choosers
Status: install ok unpacked
Version: 0.03
Depends: kbd-chooser (>= 1.30), localechooser (>= 1.23)
Description: Delayed configuration of locale and keyboard for auto-install
Installer-Menu-Item: 22

Package: libiw28-udeb
Status: install ok unpacked
Version: 28-1
Depends: libc6 (>= 2.3.5-1)
Description: Tools for manipulating Linux Wireless Extensions

Package: load-cdrom
Status: install ok half-configured
Version: 1.14
Depends: cdebconf-udeb, cdrom-retriever, anna (>= 1.07)
Description: Load installer components from CD
Installer-Menu-Item: 16

Package: cdebconf-text-udeb
Status: install ok unpacked
Version: 0.114etch1
Depends: cdebconf-udeb, libc6 (>= 2.3.5-1)
Description: Plain text frontend for Debian Configuration Management System

Package: iso-3166-udeb
Status: install ok installed
Version: 1.0a-1
Description: provides iso_3166.tab file

Package: fat-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: fat-modules
Depends: kernel-image-2.6.18-6-amd64-di
Description: FAT filesystem support

Package: floppy-retriever
Status: install ok unpacked
Version: 1.14
Provides: retriever
Depends: cdebconf-udeb, mountfloppy
Description: Fetches modules from a floppy

Package: ethdetect
Status: install ok unpacked
Version: 1.50
Provides: ethernet-card-detection
Depends: rootskel (>= 1.30), cdebconf-udeb (>= 0.38), hw-detect, di-utils (>= 1.13)
Description: Detect network hardware and load kernel drivers for it
Installer-Menu-Item: 17

Package: serial-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: serial-modules
Depends: kernel-image-2.6.18-6-amd64-di, pcmcia-modules-2.6.18-6-amd64-di
Description: Serial drivers

Package: busybox-udeb
Status: install ok unpacked
Version: 1:1.1.3-4
Depends: libc6 (>= 2.3.5-1)
Description: Tiny utilities for the debian-installer

Package: initrd-preseed
Status: install ok unpacked
Version: 1.28
Depends: preseed-common
Description: load debconf preseed file from /preseed.cfg on the initrd

Package: firewire-core-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: firewire-core-modules
Depends: scsi-core-modules-2.6.18-6-amd64-di, kernel-image-2.6.18-6-amd64-di
Description: Core FireWire drivers

Package: archdetect
Status: install ok installed
Version: 1.50
Depends: libc6 (>= 2.3.5-1), libdebian-installer4-udeb (>= 0.49)
Description: Hardware architecture detector

Package: sata-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: sata-modules
Depends: kernel-image-2.6.18-6-amd64-di, scsi-core-modules-2.6.18-6-amd64-di
Description: SATA drivers

Package: save-logs
Status: install ok unpacked
Version: 2.29
Depends: cdebconf-udeb
Description: save logs and configuration for debug purposes
Installer-Menu-Item: 940

Package: scsi-common-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: scsi-common-modules
Depends: kernel-image-2.6.18-6-amd64-di, scsi-core-modules-2.6.18-6-amd64-di, cdrom-core-modules-2.6.18-6-amd64-di
Description: Very common SCSI drivers

Package: di-utils-reboot
Status: install ok unpacked
Version: 1.45etch1
Depends: cdebconf-udeb
Description: Reboot
Installer-Menu-Item: 995

Package: anna
Status: install ok installed
Version: 1.27
Depends: libc6 (>= 2.3.5-1), libdebconfclient0-udeb, libdebian-installer4-udeb (>= 0.49), cdebconf-udeb
Description: anna's not nearly apt, but for the Debian installer, it will do

Package: libsysfs2-udeb
Status: install ok unpacked
Version: 2.1.0-1
Provides: libsysfs2
Depends: libc6 (>= 2.3.5-1)
Description: interface library to sysfs

Package: pcmciautils-udeb
Status: install ok unpacked
Version: 014-3
Depends: udev-udeb, libc6 (>= 2.3.5-1), libsysfs2-udeb
Description: PCMCIA utilities for Linux 2.6

Package: pciutils-udeb
Status: install ok unpacked
Version: 1:2.2.4~pre4-1
Depends: libc6 (>= 2.3.5-1)
Description: Linux PCI Utilities (udeb)

Package: console-keymaps-at
Status: install ok installed
Version: 2:1.01-7
Provides: console-keymaps
Depends: cdebconf-udeb
Description: Keymaps for PC-style (PS/2 and AT) keyboards

Package: di-utils-terminfo
Status: install ok unpacked
Version: 1.45etch1
Description: Terminfo entries needed by newt/slang in debian installer

Package: hw-detect
Status: install ok installed
Version: 1.50
Depends: rootskel (>= 1.30), archdetect, cdebconf-udeb (>= 0.75), di-utils (>= 1.26)
Description: Detect hardware and load kernel drivers for it

Package: kbd-chooser
Status: install ok installed
Version: 1.34
Depends: libc6 (>= 2.3.5-1), libdebconfclient0-udeb, libdebian-installer4-udeb (>= 0.49), cdebconf-udeb, console-keymaps
Description: Detect a keyboard and select layout
Installer-Menu-Item: 12

Package: libdebian-installer4-udeb
Status: install ok installed
Version: 0.50etch1
Depends: libc6 (>= 2.3.5-1)
Description: Library of common debian-installer functions

Package: usb-storage-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: usb-storage-modules
Depends: ide-core-modules-2.6.18-6-amd64-di, scsi-core-modules-2.6.18-6-amd64-di, usb-modules-2.6.18-6-amd64-di
Description: USB storage support

Package: installation-locale
Status: install ok unpacked
Version: 1.1
Depends: rootskel
Description: UTF-8 C locale

Package: env-preseed
Status: install ok unpacked
Version: 1.28
Description: debconf preseeding via environment variables

Package: mountfloppy
Status: install ok unpacked
Version: 0.11
Depends: cdebconf-udeb, di-utils (>= 1.15)
Description: Mounts a floppy

Package: cdebconf-priority
Status: install ok unpacked
Version: 0.114etch1
Depends: cdebconf-udeb
Description: Change debconf priority
Installer-Menu-Item: 930

Package: netcfg
Status: install ok unpacked
Version: 1.36
Provides: configured-network
Depends: libc6 (>= 2.3.5-1), libdebconfclient0-udeb, libdebian-installer4-udeb (>= 0.49), libiw28-udeb (>= 28), dhcp-client-udeb | dhcp3-client-udeb | pump-udeb, ethernet-card-detection
Description: Configure the network
Installer-Menu-Item: 18

Package: file-preseed
Status: install ok unpacked
Version: 1.28
Depends: cdebconf-udeb, di-utils, preseed-common
Description: load debconf preseed file
Installer-Menu-Item: 14

Package: usb-serial-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: usb-serial-modules
Depends: kernel-image-2.6.18-6-amd64-di, usb-modules-2.6.18-6-amd64-di
Description: USB serial drivers

Package: pcmcia-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: pcmcia-modules
Depends: kernel-image-2.6.18-6-amd64-di, core-modules-2.6.18-6-amd64-di
Description: Common PCMCIA drivers

Package: scsi-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: scsi-modules
Depends: kernel-image-2.6.18-6-amd64-di, scsi-core-modules-2.6.18-6-amd64-di, scsi-common-modules-2.6.18-6-amd64-di, parport-modules-2.6.18-6-amd64-di, cdrom-core-modules-2.6.18-6-amd64-di, core-modules-2.6.18-6-amd64-di
Description: SCSI drivers

Package: libdebconfclient0-udeb
Status: install ok installed
Version: 0.114etch1
Depends: libc6 (>= 2.3.5-1), cdebconf-udeb
Description: Debian Configuration Management System (C-implementation)

Package: bogl-bterm-udeb
Status: install ok unpacked
Version: 0.1.18-1.5
Provides: editor
Depends: libc-udeb
Description: Ben's Own Graphics Library - graphical terminal

Package: cdrom-detect
Status: install ok installed
Version: 1.20etch1
Depends: cdebconf-udeb, hw-detect, di-utils (>= 1.45etch1)
Description: Detect CDROM devices and mount the CD
Installer-Menu-Item: 13

Package: scsi-core-modules-2.6.18-6-amd64-di
Status: install ok unpacked
Version: 1.21etch3
Provides: scsi-core-modules
Depends: kernel-image-2.6.18-6-amd64-di
Description: Core SCSI subsystem

Package: debian-installer
Status: install ok installed
Version: cdrom-isolinux-20070308etch2
Description: debian installation image

Package: zlib1g-udeb
Status: install ok installed
Priority: optional
Section: debian-installer
Installed-Size: 108
Maintainer: Mark Brown
Version: 1:1.2.3-13
Provides: zlib1g
Description: compression library - runtime for Debian installer
zlib is a library implementing the deflate compression method found
in gzip and PKZIP. This minimal package includes the shared library
for use with the Debian installer.

Package: apt-cdrom-setup
Status: install ok installed
Priority: extra
Section: debian-installer
Installed-Size: 44
Maintainer: Debian Install System Team
Version: 1:0.20etch1
Depends: cdrom-detect, cdebconf-udeb
Provides: apt-mirror-setup
Description: set up a CD in sources.list

Package: apt-mirror-setup
Status: install ok installed
Priority: extra
Section: debian-installer
Installed-Size: 160
Maintainer: Debian Install System Team
Version: 1:0.20etch1
Depends: choose-mirror-bin, cdebconf-udeb
Description: set up a mirror in sources.list

Package: apt-setup-udeb
Status: install ok unpacked
Priority: standard
Section: debian-installer
Installed-Size: 104
Maintainer: Debian Install System Team
Version: 1:0.20etch1
Depends: apt-mirror-setup, base-installer (>= 1.49), cdebconf-udeb
Description: Configure apt
Installer-Menu-Item: 70



~[Σ] ~[Ω] ~[Δ]!
































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Lsb-release of installer

Lsb-release of installer
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="4.0 (installer build 20070308etch2)"
X_INSTALLATION_MEDIUM=cdrom



~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Install Report Template

Install Report Template
Package: installation-reports

Boot method:
Image version:
Date:

Machine:
Partitions:


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot: [ ]
Detect network card: [ ]
Configure network: [ ]
Detect CD: [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Install base system: [ ]
Clock/timezone setup: [ ]
User/password setup: [ ]
Install tasks: [ ]
Install boot loader: [ ]
Overall install: [ ]

Comments/Problems:

and ideas you had during the initial install.>


--

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to submit@bugs.debian.org.



~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~Windows XP Install in the same PC

Windows XP Install in the same PC
ξ detected hardware ok
ξ detected LAN ok
ξ connected to Internet ok
ξ handled CD-ROM ok
ξ easy to install with user friendly GUI
ξ both XP 1 and XP2 ok
ξ


~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yourDragonXi ~




~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Small & Smart Inc reserves rights to change this document without any notice
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~