[gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[David Harel]

Greetings,


After installing gentoo-source-2.6.20-r8 I copied my current .config 
file to the new kernel and did make oldconfig. I had to do define only 
new properties of the new kernel and the rest was taken from the 
original config file however, at boot time I got panic halt on root 
mount stating that ext3 is not supported. Double check on support for 
ext3 is OK.


Any idea?

-- 
Regards.

David Harel,

==================================

Home office +972 77 7657645
Fax:        +972 77 7657645
Cellular:   +972 54 4534502
Snail Mail: Amuka
            D.N Merom Hagalil
            13802
            Israel
Email:      hareldvd@ergolight-sw.com


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Alan McKinnon]

On Friday 11 May 2007, David Harel wrote:
> Greetings,
>
>
> After installing gentoo-source-2.6.20-r8 I copied my current .config
> file to the new kernel and did make oldconfig. I had to do define
> only new properties of the new kernel and the rest was taken from the
> original config file however, at boot time I got panic halt on root
> mount stating that ext3 is not supported. Double check on support for
> ext3 is OK.

> Any idea?

Given the actual information you posted above, none whatsoever.

Please post your .config and the version number of the kernel you were 
upgrading from and we'll all take a look-see

alan

-- 
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?

Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Dirk Heinrichs]

[-- Attachment #1: Type: text/plain, Size: 861 bytes --]

Am Freitag, 11. Mai 2007 schrieb ext David Harel:

> After installing gentoo-source-2.6.20-r8 I copied my current .config
> file to the new kernel and did make oldconfig. I had to do define only
> new properties of the new kernel and the rest was taken from the
> original config file however, at boot time I got panic halt on root
> mount stating that ext3 is not supported. Double check on support for
> ext3 is OK.

Could you please, in addition to what Alan requested, post the _exact_ 
message?

Bye...

	Dirk
-- 
Dirk Heinrichs          | Tel:  +49 (0)162 234 3408
Configuration Manager   | Fax:  +49 (0)211 47068 111
Capgemini Deutschland   | Mail: dirk.heinrichs@capgemini.com
Wanheimerstraße 68      | Web:  http://www.capgemini.com
D-40468 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[David Harel]

[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]

Sorry for not providing details (was sure people will identify the 
problem in a glance).


Upgrade is from 2.6.17-r8

Attached the panic message:


VFS: cannot open root  device sda1 or unknown block (0,0)

please append a correct "root=" boot option.

Kernel panic - not syncing: VFS: unable to mount root fs on unknown - 
block (0,0)


Attached the .config file (after converted to 2.6.20-r8 - make oldconfig 
- just hit the enter key)

lilo is double checked. Below the relevant section.


boot=/dev/sda
root=/dev/sda1
read-only


image=/boot/vmlinuz-2.6.20-r8.v0

  label=SDA1-20-r8.v0
  append="root=/dev/sda1"



Alan McKinnon wrote:

> On Friday 11 May 2007, David Harel wrote:
>   
>> Greetings,
>>
>>
>> After installing gentoo-source-2.6.20-r8 I copied my current .config
>> file to the new kernel and did make oldconfig. I had to do define
>> only new properties of the new kernel and the rest was taken from the
>> original config file however, at boot time I got panic halt on root
>> mount stating that ext3 is not supported. Double check on support for
>> ext3 is OK.
>>     
>
>   
>> Any idea?
>>     
>
> Given the actual information you posted above, none whatsoever.
>
> Please post your .config and the version number of the kernel you were 
> upgrading from and we'll all take a look-see
>
> alan
>
>   

-- 
Regards.

David Harel,

==================================

Home office +972 77 7657645
Fax:        +972 77 7657645
Cellular:   +972 54 4534502
Snail Mail: Amuka
            D.N Merom Hagalil
            13802
            Israel
Email:      hareldvd@ergolight-sw.com



[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 38695 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.20-gentoo-r8
# Fri May 11 16:54:29 2007
#
CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_IPC_NS is not set
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_UTS_NS is not set
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_SYSFS_DEPRECATED=y
# CONFIG_RELAY is not set
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_SLAB=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_SLOB is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y

#
# Block layer
#
CONFIG_BLOCK=y
CONFIG_LBD=y
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_DEFAULT_AS=y
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="anticipatory"

#
# Processor type and features
#
# CONFIG_SMP is not set
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_PARAVIRT is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
CONFIG_MPENTIUMM=y
# CONFIG_MCORE2 is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_HPET_TIMER=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
CONFIG_X86_MCE_P4THERMAL=y
CONFIG_VM86=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_X86_REBOOTFIXUPS is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set

#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_RESOURCES_64BIT is not set
# CONFIG_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_SECCOMP=y
CONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=100
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
CONFIG_COMPAT_VDSO=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
CONFIG_PM_LEGACY=y
# CONFIG_PM_DEBUG is not set
# CONFIG_PM_SYSFS_DEPRECATED is not set
# CONFIG_SOFTWARE_SUSPEND is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
# CONFIG_ACPI_SLEEP_PROC_SLEEP is not set
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=y
# CONFIG_ACPI_HOTKEY is not set
CONFIG_ACPI_FAN=y
# CONFIG_ACPI_DOCK is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not set
# CONFIG_ACPI_SBS is not set

#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_GOV_USERSPACE=y
# CONFIG_CPU_FREQ_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set

#
# CPUFreq processor drivers
#
# CONFIG_X86_ACPI_CPUFREQ is not set
# CONFIG_X86_POWERNOW_K6 is not set
# CONFIG_X86_POWERNOW_K7 is not set
# CONFIG_X86_POWERNOW_K8 is not set
# CONFIG_X86_GX_SUSPMOD is not set
CONFIG_X86_SPEEDSTEP_CENTRINO=m
CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y
CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y
# CONFIG_X86_SPEEDSTEP_ICH is not set
# CONFIG_X86_SPEEDSTEP_SMI is not set
# CONFIG_X86_P4_CLOCKMOD is not set
# CONFIG_X86_CPUFREQ_NFORCE2 is not set
# CONFIG_X86_LONGRUN is not set
# CONFIG_X86_LONGHAUL is not set

#
# shared options
#
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
# CONFIG_X86_SPEEDSTEP_LIB is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_PCIEPORTBUS is not set
# CONFIG_PCI_MSI is not set
CONFIG_HT_IRQ=y
CONFIG_ISA_DMA_API=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# PCCARD (PCMCIA/CardBus) support
#
CONFIG_PCCARD=y
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=y
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y

#
# PC-card bridges
#
CONFIG_YENTA=y
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
CONFIG_PD6729=y
CONFIG_I82092=y
CONFIG_I82365=y
CONFIG_TCIC=y
CONFIG_PCMCIA_PROBE=y
CONFIG_PCCARD_NONSTATIC=y

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
# CONFIG_NETDEBUG is not set
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set

#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_NETWORK_SECMARK is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set

#
# Core Netfilter Configuration
#
# CONFIG_NETFILTER_NETLINK is not set
# CONFIG_NF_CONNTRACK_ENABLED is not set
# CONFIG_NETFILTER_XTABLES is not set

#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_QUEUE=y

#
# DCCP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_DCCP is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set

#
# TIPC Configuration (EXPERIMENTAL)
#
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_IEEE80211 is not set
CONFIG_WIRELESS_EXT=y

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_SYS_HYPERVISOR is not set

#
# Connector - unified userspace <-> kernelspace linker
#
# CONFIG_CONNECTOR is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_PC_PCMCIA is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_AX88796 is not set
# CONFIG_PARPORT_1284 is not set

#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
# CONFIG_ISAPNP is not set
# CONFIG_PNPBIOS is not set
CONFIG_PNPACPI=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_CDROM_PKTCDVD=y
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
# CONFIG_ATA_OVER_ETH is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_CS5535 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_JMICRON is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
# CONFIG_SCSI_TGT is not set
# CONFIG_SCSI_NETLINK is not set
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set

#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set

#
# SCSI low-level drivers
#
# CONFIG_ISCSI_TCP is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_SEAGATE is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set

#
# PCMCIA SCSI adapter support
#
# CONFIG_PCMCIA_AHA152X is not set
# CONFIG_PCMCIA_FDOMAIN is not set
# CONFIG_PCMCIA_NINJA_SCSI is not set
# CONFIG_PCMCIA_QLOGIC is not set
# CONFIG_PCMCIA_SYM53C500 is not set

#
# Serial ATA (prod) and Parallel ATA (experimental) drivers
#
# CONFIG_ATA is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_SPI is not set
# CONFIG_FUSION_FC is not set
# CONFIG_FUSION_SAS is not set

#
# IEEE 1394 (FireWire) support
#
CONFIG_IEEE1394=y

#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
# CONFIG_IEEE1394_OUI_DB is not set
# CONFIG_IEEE1394_EXTRA_CONFIG_ROMS is not set
# CONFIG_IEEE1394_EXPORT_FULL_API is not set

#
# Device Drivers
#
# CONFIG_IEEE1394_PCILYNX is not set
CONFIG_IEEE1394_OHCI1394=y

#
# Protocol Drivers
#
# CONFIG_IEEE1394_VIDEO1394 is not set
# CONFIG_IEEE1394_SBP2 is not set
# CONFIG_IEEE1394_ETH1394 is not set
# CONFIG_IEEE1394_DV1394 is not set
CONFIG_IEEE1394_RAWIO=y

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Macintosh device drivers
#
# CONFIG_MAC_EMUMOUSEBTN is not set

#
# Network device support
#
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 is not set

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# PHY device support
#
# CONFIG_PHYLIB is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
CONFIG_B44=y
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
CONFIG_8139TOO=y
CONFIG_8139TOO_PIO=y
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_SK98LIN is not set
# CONFIG_VIA_VELOCITY is not set
CONFIG_TIGON3=y
CONFIG_BNX2=y
# CONFIG_QLA3XXX is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_CHELSIO_T1 is not set
# CONFIG_IXGB is not set
CONFIG_S2IO=m
# CONFIG_S2IO_NAPI is not set
# CONFIG_MYRI10GE is not set
# CONFIG_NETXEN_NIC is not set

#
# Token Ring devices
#
# CONFIG_TR is not set

#
# Wireless LAN (non-hamradio)
#
CONFIG_NET_RADIO=y
# CONFIG_NET_WIRELESS_RTNETLINK is not set

#
# Obsolete Wireless cards support (pre-802.11)
#
# CONFIG_STRIP is not set
# CONFIG_ARLAN is not set
# CONFIG_WAVELAN is not set
# CONFIG_PCMCIA_WAVELAN is not set
# CONFIG_PCMCIA_NETWAVE is not set

#
# Wireless 802.11 Frequency Hopping cards support
#
# CONFIG_PCMCIA_RAYCS is not set

#
# Wireless 802.11b ISA/PCI cards support
#
# CONFIG_IPW2100 is not set
# CONFIG_IPW2200 is not set
# CONFIG_AIRO is not set
# CONFIG_HERMES is not set
# CONFIG_ATMEL is not set

#
# Wireless 802.11b Pcmcia/Cardbus cards support
#
# CONFIG_AIRO_CS is not set
# CONFIG_PCMCIA_WL3501 is not set

#
# Prism GT/Duette 802.11(a/b/g) PCI/Cardbus support
#
# CONFIG_PRISM54 is not set
# CONFIG_USB_ZD1201 is not set
# CONFIG_HOSTAP is not set
CONFIG_NET_WIRELESS=y

#
# PCMCIA network device support
#
# CONFIG_NET_PCMCIA is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
# CONFIG_SERIAL_8250_CS is not set
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_PRINTER=y
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=y
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
CONFIG_DRM_I810=y
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_I915 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set

#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_CARDMAN_4000 is not set
# CONFIG_CARDMAN_4040 is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_NSC_GPIO is not set
# CONFIG_CS5535_GPIO is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# TPM devices
#
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set

#
# I2C support
#
CONFIG_I2C=m
# CONFIG_I2C_CHARDEV is not set

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set

#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_ELEKTOR is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set
# CONFIG_I2C_PCA_ISA is not set

#
# Miscellaneous I2C Chip support
#
# CONFIG_SENSORS_DS1337 is not set
# CONFIG_SENSORS_DS1374 is not set
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_MAX6875 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

#
# SPI support
#
# CONFIG_SPI is not set
# CONFIG_SPI_MASTER is not set

#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set

#
# Hardware Monitoring support
#
CONFIG_HWMON=y
# CONFIG_HWMON_VID is not set
# CONFIG_SENSORS_ABITUGURU is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_K8TEMP is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_FSCPOS is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
# CONFIG_USB_DABUSB is not set

#
# Graphics support
#
CONFIG_FIRMWARE_EDID=y
CONFIG_FB=y
# CONFIG_FB_DDC is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
# CONFIG_VIDEO_SELECT is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
CONFIG_FB_I810=y
# CONFIG_FB_I810_GTF is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_CYBLA is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE is not set

#
# Logo configuration
#
# CONFIG_LOGO is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Speakup console speech
#
# CONFIG_SPEAKUP is not set

#
# Sound
#
CONFIG_SOUND=y

#
# Advanced Linux Sound Architecture
#
# CONFIG_SND is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# HID Devices
#
CONFIG_HID=y

#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=y

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#

#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_LIBUSUAL is not set

#
# USB Input Devices
#
CONFIG_USB_HID=y
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_ACECAD is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_TOUCHSCREEN is not set
# CONFIG_USB_YEALINK is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set
# CONFIG_USB_ATI_REMOTE2 is not set
# CONFIG_USB_KEYSPAN_REMOTE is not set
# CONFIG_USB_APPLETOUCH is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set

#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET_MII is not set
# CONFIG_USB_USBNET is not set
CONFIG_USB_MON=y

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGET is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_TEST is not set

#
# USB DSL modem support
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# MMC/SD Card support
#
# CONFIG_MMC is not set

#
# LED devices
#
# CONFIG_NEW_LEDS is not set

#
# LED drivers
#

#
# LED Triggers
#

#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set

#
# EDAC - error detection and reporting (RAS) (EXPERIMENTAL)
#
# CONFIG_EDAC is not set

#
# Real Time Clock
#
# CONFIG_RTC_CLASS is not set

#
# DMA Engine support
#
# CONFIG_DMA_ENGINE is not set

#
# DMA Clients
#

#
# DMA Devices
#

#
# Virtualization
#
# CONFIG_KVM is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
# CONFIG_EXT4DEV_FS is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_FS_POSIX_ACL is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
# CONFIG_FUSE_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
# CONFIG_CONFIGFS_FS is not set

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_SQUASHFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=y
# CONFIG_NFS_V3 is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
# CONFIG_NFSD_V3 is not set
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=y
CONFIG_EXPORTFS=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
CONFIG_SMB_FS=y
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp437"
CONFIG_CIFS=y
CONFIG_CIFS_STATS=y
# CONFIG_CIFS_STATS2 is not set
# CONFIG_CIFS_WEAK_PW_HASH is not set
# CONFIG_CIFS_XATTR is not set
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
# CONFIG_9P_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
CONFIG_NLS_CODEPAGE_862=y
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
CONFIG_NLS_ISO8859_8=y
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y

#
# Distributed Lock Manager
#
# CONFIG_DLM is not set

#
# Instrumentation Support
#
CONFIG_PROFILING=y
CONFIG_OPROFILE=y
# CONFIG_KPROBES is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_MUST_CHECK=y
# CONFIG_MAGIC_SYSRQ is not set
CONFIG_UNUSED_SYMBOLS=y
# CONFIG_DEBUG_FS is not set
# CONFIG_HEADERS_CHECK is not set
# CONFIG_DEBUG_KERNEL is not set
CONFIG_LOG_BUF_SHIFT=14
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_EARLY_PRINTK=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=m
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_MANAGER=m
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
# CONFIG_CRYPTO_MD5 is not set
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_GF128MUL is not set
CONFIG_CRYPTO_ECB=m
CONFIG_CRYPTO_CBC=m
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_586 is not set
# CONFIG_CRYPTO_SERPENT is not set
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_586=m
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
CONFIG_CRYPTO_ARC4=m
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_DEFLATE is not set
CONFIG_CRYPTO_MICHAEL_MIC=m
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_TEST is not set

#
# Hardware crypto devices
#
# CONFIG_CRYPTO_DEV_PADLOCK is not set
CONFIG_CRYPTO_DEV_GEODE=m

#
# Library routines
#
CONFIG_BITREVERSE=y
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not set
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_AUDIT_GENERIC=y
CONFIG_ZLIB_INFLATE=y
CONFIG_PLIST=y
CONFIG_IOMAP_COPY=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_KTIME_SCALAR=y

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 694 bytes --]

On Fri, 11 May 2007 17:39:57 +0300, David Harel wrote:

> Upgrade is from 2.6.17-r8
> 
> Attached the panic message:
> 
> 
> VFS: cannot open root  device sda1 or unknown block (0,0)
> 
> please append a correct "root=" boot option.
> 
> Kernel panic - not syncing: VFS: unable to mount root fs on unknown - 
> block (0,0)

You've been bitten by the same thing that hit most other SATA users. The
SATA config options moved between 2.6.18 and 2.6.19 so your SATA chipset
driver is no longer compiled in to the kernel. Do a make menuconfig,
hit / and search for your SATA driver and enable it.


-- 
Neil Bothwick

If a parsley farmer is sued, can they garnish his wages?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Alan McKinnon]

On Friday 11 May 2007, David Harel wrote:
> Sorry for not providing details (was sure people will identify the
> problem in a glance).
>
>
> Upgrade is from 2.6.17-r8

OK, you seem to have run into the "Lets rip IDE out of the kernel and 
replace it with ATA" thing that happened in 2.6.18...

In menuconfig , under Drivers, there's a menu a little bit below the 
IDE?MFM stuff. It's called SATA/PATA or similar. You will find 
appropriate settings for your hardware there. I can't elabortae as I 
don't know what you have, but you disk settings seem to be IDE


> Attached the panic message:
>
>
> VFS: cannot open root  device sda1 or unknown block (0,0)
>
> please append a correct "root=" boot option.
>
> Kernel panic - not syncing: VFS: unable to mount root fs on unknown -
> block (0,0)

Please, please, please always quote the correct error messages and leave 
your personal evaluation out of it. See how the above says absolutely 
nothing about ext3? But your original post was all about that, and 
without the actual error and .config, we would have spent hours trying 
to get your fs working, when in fault it is not faulty...



-- 
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?

Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Etaoin Shrdlu]

On Friday 11 May 2007 16:39, David Harel wrote:

> lilo is double checked. Below the relevant section.
>
>
> boot=/dev/sda
> root=/dev/sda1
> read-only
>
>
> image=/boot/vmlinuz-2.6.20-r8.v0
>
>   label=SDA1-20-r8.v0
>   append="root=/dev/sda1"

This last line, written this way, looks wrong or at least useless to me.
Try to change it into the simpler

  root = /dev/sda1

or remove it altogether, since you already specified the root device in 
the global section.

Also, you seem to have a SCSI or SATA drive (the output of lspci would 
help here). All SCSI low-level drivers are disabled in your config, so I 
guess you have a SATA drive. But, you have also disabled all the SATA 
drivers (it's the "Serial ATA (prod) and Parallel ATA (experimental) 
drivers" section). This could happen if you did "make oldconfig" using a 
pre-2.6.19 config file, because SATA drivers moved under CONFIG_ATA 
starting from 2.6.19. If so, do a "make menuconfig" and double check 
that all the drivers you need are compiled into your kernel.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[David Harel]

Thank you both Neil Bothwick andAlan McKinnon for the great help.


Got this one working now. Still many features arn't working yet such as 
alsa and wifi but I think I will make it now.

The driver I needed seem to be AHCI SATA.  Was rather difficult to 
identify that that is the right driver because lspci states:

00:1f.2 SATA controller: Intel Corporation 82801FBM (ICH6M) SATA 
Controller (rev 04)

and you can't find 82801 in .config
Also it seems to me that the driver should be statically loaded and not 
as a module (which now makes sense unless I could have changed things in 
modules.conf or similar).


May I suggest/encourage people to write summaries (such as was a custom 
in sun managers mailing list (sun.unc.edu?) so other people can learn 
and save time?




Alan McKinnon wrote:

> On Friday 11 May 2007, David Harel wrote:
>   
>> Sorry for not providing details (was sure people will identify the
>> problem in a glance).
>>
>>
>> Upgrade is from 2.6.17-r8
>>     
>
> OK, you seem to have run into the "Lets rip IDE out of the kernel and 
> replace it with ATA" thing that happened in 2.6.18...
>
> In menuconfig , under Drivers, there's a menu a little bit below the 
> IDE?MFM stuff. It's called SATA/PATA or similar. You will find 
> appropriate settings for your hardware there. I can't elabortae as I 
> don't know what you have, but you disk settings seem to be IDE
>
>
>   
>> Attached the panic message:
>>
>>
>> VFS: cannot open root  device sda1 or unknown block (0,0)
>>
>> please append a correct "root=" boot option.
>>
>> Kernel panic - not syncing: VFS: unable to mount root fs on unknown -
>> block (0,0)
>>     
>
> Please, please, please always quote the correct error messages and leave 
> your personal evaluation out of it. See how the above says absolutely 
> nothing about ext3? But your original post was all about that, and 
> without the actual error and .config, we would have spent hours trying 
> to get your fs working, when in fault it is not faulty...
>
>
>
>   

-- 
Regards.

David Harel,

==================================

Home office +972 77 7657645
Fax:        +972 77 7657645
Cellular:   +972 54 4534502
Snail Mail: Amuka
            D.N Merom Hagalil
            13802
            Israel
Email:      hareldvd@ergolight-sw.com


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Neil Walker]

David Harel wrote:
> The driver I needed seem to be AHCI SATA.  

What makes you think that?

> Was rather difficult to identify that that is the right driver because 
> lspci states:
>
> 00:1f.2 SATA controller: Intel Corporation 82801FBM (ICH6M) SATA 
> Controller (rev 04)
>
> and you can't find 82801 in .config

It's the Intel PIIX driver for the Intel ICH family, etc. You didn't 
look for Intel or ICH?



Be lucky,

Neil

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[David Harel]

I read this: 
http://www.uwsg.iu.edu/hypermail/linux/kernel/0510.3/2003.html and 
figured out the driver name. Are they compatible? cos that's the one 
setup and I am up and running. I'll try the driver you suggested and see 
if it works.

Neil Walker wrote:

> David Harel wrote:
>> The driver I needed seem to be AHCI SATA.  
>
> What makes you think that?
>
>> Was rather difficult to identify that that is the right driver 
>> because lspci states:
>>
>> 00:1f.2 SATA controller: Intel Corporation 82801FBM (ICH6M) SATA 
>> Controller (rev 04)
>>
>> and you can't find 82801 in .config
>
> It's the Intel PIIX driver for the Intel ICH family, etc. You didn't 
> look for Intel or ICH?
>
>
>
> Be lucky,
>
> Neil
>

-- 
Regards.

David Harel,

==================================

Home office +972 77 7657645
Fax:        +972 77 7657645
Cellular:   +972 54 4534502
Snail Mail: Amuka
            D.N Merom Hagalil
            13802
            Israel
Email:      hareldvd@ergolight-sw.com


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Graham Murray]

Neil Walker <neil@ep.mine.nu> writes:

> It's the Intel PIIX driver for the Intel ICH family, etc. You didn't
> look for Intel or ICH?

For the ICH6 and later, I think that the AHCI driver is better than
PIIX_ATA. 
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Graham Murray]

David Harel <hareldvd@ergolight-sw.com> writes:

> Graham Murray wrote:
>> For the ICH6 and later, I think that the AHCI driver is better than
>> PIIX_ATA.   
> How can I evaluate the different solutions (They both work)?

According to the Linux sata site
(http://linux-ata.org/driver-status.html) the AHCI driver supports all
the SATA features such as NCQ (Native Command Queueing) and hotplug but
the PIIX module does not support these.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Neil Walker]

Graham Murray wrote:
> According to the Linux sata site
> (http://linux-ata.org/driver-status.html) the AHCI driver supports all
> the SATA features such as NCQ (Native Command Queueing) and hotplug but
> the PIIX module does not support these.
>   

I've been running the PIIX driver for quite some time and everything 
appears to work OK so it hadn't occurred to me to go looking at other 
drivers. ;) Maybe I should take a closer look at AHCI - especially as it 
seems Intel are listed as a sponsor, so it must have their approval. :)


Be lucky,

Neil

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Neil Walker]

Neil Walker wrote:
> Maybe I should take a closer look at AHCI - especially as it seems 
> Intel are listed as a sponsor, so it must have their approval. :)

Well, it didn't work - just resulted in a kernel panic. It seems AHCI is 
only supported by SOME  ICH6,7,8  interfaces. :(


Be lucky,


Neil

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Graham Murray]

Neil Walker <neil@ep.mine.nu> writes:

> Well, it didn't work - just resulted in a kernel panic. It seems AHCI
> is only supported by SOME  ICH6,7,8  interfaces. :(

Did you select AHCI mode in the BIOS? On my motherboard (with
ICH6R/IC6RW) there is an option to set SATA mode to IDE, RAID or AHCI.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Neil Walker]

Graham Murray wrote:
> Did you select AHCI mode in the BIOS? On my motherboard (with
> ICH6R/IC6RW) there is an option to set SATA mode to IDE, RAID or AHCI.
>   

The item is there in the BIOS but only has one setting available - IDE. 
:( Seems my chipset is one of those that doesn't support AHCI. lspci 
reports this:


00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE 
Controller (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) 
Serial ATA Storage Controller IDE (rev 01)

The motherboard is an Asus P5LD2-VM.


Be lucky,

Neil


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Roman Zimmermann]

[-- Attachment #1: Type: text/plain, Size: 690 bytes --]

Am Montag 14 Mai 2007 09:19 schrieb Neil Walker:
> :( Seems my chipset is one of those that doesn't support AHCI.

Hi! 

I have a similar controller to yours and did some research recently. It seems 
that (allmost) all ICH7 controllers do support AHCI [1]. But I cannot 
activate AHCI anywhere in the BIOS. It seems this is due to some limitations 
of the BIOS.
There was also a thread on another mailing list where it was suggested to 
update the BIOS. I'm currently pondering to do so but I'm not sure about how 
safe it is without having a winxp installation... Besides I'm not sure 
whether it would help.

[1] http://www.intel.com/support/chipsets/imst/sb/CS-012304.htm

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Neil Walker]

Roman Zimmermann wrote:
> I have a similar controller to yours and did some research recently. It seems 
> that (allmost) all ICH7 controllers do support AHCI [1]. But I cannot 
> activate AHCI anywhere in the BIOS. It seems this is due to some limitations 
> of the BIOS.
> There was also a thread on another mailing list where it was suggested to 
> update the BIOS. I'm currently pondering to do so but I'm not sure about how 
> safe it is without having a winxp installation... Besides I'm not sure 
> whether it would help.
>
> [1] http://www.intel.com/support/chipsets/imst/sb/CS-012304.htm
>   


I checked the FAQ on the Asus website and that states that my 
motherboard doesn't support AHCI. :(


Be lucky,

Neil

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Karl Haines]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Neil Walker wrote:
> Roman Zimmermann wrote:
>> I have a similar controller to yours and did some research recently.
>> It seems that (allmost) all ICH7 controllers do support AHCI [1]. But
>> I cannot activate AHCI anywhere in the BIOS. It seems this is due to
>> some limitations of the BIOS.
>> There was also a thread on another mailing list where it was suggested
>> to update the BIOS. I'm currently pondering to do so but I'm not sure
>> about how safe it is without having a winxp installation... Besides
>> I'm not sure whether it would help.
>>
>> [1] http://www.intel.com/support/chipsets/imst/sb/CS-012304.htm
>>   
> 
> 
> I checked the FAQ on the Asus website and that states that my
> motherboard doesn't support AHCI. :(
> 
> 
> Be lucky,
> 
> Neil
> 

Actually, updating the BIOS to the newest version is almost ALWAYS a
good thing. If the vendor has heard about such problems, they should
almost always do something to fix it, and apply such fixes to their next
BIOS update. I have fixed many problems (i'm a computer technician) with
BIOS updates. Having XP installed makes no difference, except that you
can (with some MBs) update from within windows. They ALL, however,
support a BIOS update from a bootable DOS floppy. Hope this helps!

Karl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGSkTzJEKtOLl2EkMRAv/sAKCgCz5B5DbxHSBy45Z7FsyvZm7wFgCfcp0w
UXOvGzTtR8ybjYXV+Erxo9U=
=YEYS
-----END PGP SIGNATURE-----
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Roman Zimmermann]

[-- Attachment #1: Type: text/plain, Size: 476 bytes --]

Am Mittwoch 16 Mai 2007 01:40 schrieb Karl Haines:
>.... I have fixed many problems (i'm a computer technician) with
> BIOS updates. Having XP installed makes no difference, except that you
> can (with some MBs) update from within windows. They ALL, however,
> support a BIOS update from a bootable DOS floppy. Hope this helps!

Hi!

Probably I was just frightened by some horror stories about BIOS flashing. 
I'll give it a shot in the next days.

thanks.
Roman

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Neil Walker]

Karl Haines wrote:
> Actually, updating the BIOS to the newest version is almost ALWAYS a
> good thing.

I keep all the BIOSs im my machines uptodate (8 at the moment, building 
another tomorrow). ;)

> Having XP installed makes no difference, except that you
> can (with some MBs) update from within windows. They ALL, however,
> support a BIOS update from a bootable DOS floppy. Hope this helps!
>   

I haven't owned a floppy drive in years so I have to be a bit more 
devious. ;)

Anyway, thanks for your advice. :)


Be lucky,

Neil


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Dale]

Neil Walker wrote:
> Karl Haines wrote:
>> Actually, updating the BIOS to the newest version is almost ALWAYS a
>> good thing.
>
> I keep all the BIOSs im my machines uptodate (8 at the moment,
> building another tomorrow). ;)
>
>> Having XP installed makes no difference, except that you
>> can (with some MBs) update from within windows. They ALL, however,
>> support a BIOS update from a bootable DOS floppy. Hope this helps!
>>   
>
> I haven't owned a floppy drive in years so I have to be a bit more
> devious. ;)
>
> Anyway, thanks for your advice. :)
>
>
> Be lucky,
>
> Neil
>
>

Now that most puters don't have a floppy, how will people update the
BIOS??  I don't have windoze at all and my next rig may not have a
floppy either.

Will there be a way to do it from a CD/DVD?

Curious.

Dale

:-)  :-)  :-)

-- 
www.myspace.com/-remove-me-dalek1967

Copy n paste then remove the -remove-me- part.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 325 bytes --]

On Wed, 16 May 2007 09:21:41 -0500, Dale wrote:

> Now that most puters don't have a floppy, how will people update the
> BIOS??  I don't have windoze at all and my next rig may not have a
> floppy either.

My new Asus motherboard updates from a USB stick.


-- 
Neil Bothwick

Portable: Survives system reboot.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Dale]

[-- Attachment #1: Type: text/plain, Size: 513 bytes --]

Neil Bothwick wrote:
> On Wed, 16 May 2007 09:21:41 -0500, Dale wrote:
>
>   
>> Now that most puters don't have a floppy, how will people update the
>> BIOS??  I don't have windoze at all and my next rig may not have a
>> floppy either.
>>     
>
> My new Asus motherboard updates from a USB stick.
>
>
>   

LOL  I don't have one of those either.  Just my luck.  At least they are
looking ahead though. 

Dale

:-)  :-)

-- 
www.myspace.com/-remove-me-dalek1967

Copy n paste then remove the -remove-me- part.


[-- Attachment #2: Type: text/html, Size: 1103 bytes --]

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Neil Walker]

Dale wrote:
> Will there be a way to do it from a CD/DVD?
>
> Curious.
>   

In many cases, yes. I updated one just last week using a CD. That BIOS 
had an update utilty built in to which you could boot. It looks first 
for a floppy then, if not found, a CD.  :)


Be lucky,

Neil

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Dale]

Neil Walker wrote:
> Dale wrote:
>> Will there be a way to do it from a CD/DVD?
>>
>> Curious.
>>   
>
> In many cases, yes. I updated one just last week using a CD. That BIOS
> had an update utilty built in to which you could boot. It looks first
> for a floppy then, if not found, a CD.  :)
>
>
> Be lucky,
>
> Neil
>

Cool.  I'm a Linux only person here so this is something that I am
curious about.  That wouldn't happen to have been a Abit mobo would it?

I may need to update mine.  My mouse has acted funny ever since I had
it.  It's like it has a bounce problem.  A single click acts as two
clicks sometimes.

Thanks for the info.

Dale

:-)  :-)

-- 
www.myspace.com/-remove-me-dalek1967

Copy n paste then remove the -remove-me- part.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Neil Walker]

Dale wrote:
> Cool.  I'm a Linux only person here so this is something that I am
> curious about.  That wouldn't happen to have been a Abit mobo would it?
>   

No, sorry. It was an Asus - which is mostly what I buy. However, the one 
arriving tomorrow is an Abit so I might know a bit more about them by 
then. My previous Abit was a PII-400 machine. ;) FWIW, my next one will 
be a Tyan dual socket F in a few weeks time. ;)

Be lucky,

Neil

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Dan Farrell]

On Wed, 16 May 2007 09:54:09 -0500
Dale <dalek@exceedtech.net> wrote:

> Neil Bothwick wrote:
> > On Wed, 16 May 2007 09:21:41 -0500, Dale wrote:
> >> Now that most puters don't have a floppy, how will people update
> >> the BIOS??  I don't have windoze at all and my next rig may not
> >> have a floppy either.
> > My new Asus motherboard updates from a USB stick.

> LOL  I don't have one of those either.  Just my luck.  At least they
> are looking ahead though. 

> Dale

USB sticks are virtually worthless nowadays, for a couple tens of
dollars you should be able to get one with a capacity of a few gigs.  

There's also the possibility of writing directly to the cmos
with /dev/nvram, isn't there?  It's a character device driver in the
kernel.  
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Dale]

[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]

Dan Farrell wrote:
> On Wed, 16 May 2007 09:54:09 -0500
> Dale <dalek@exceedtech.net> wrote:
>
>   
>> Neil Bothwick wrote:
>>     
>>> On Wed, 16 May 2007 09:21:41 -0500, Dale wrote:
>>>       
>>>> Now that most puters don't have a floppy, how will people update
>>>> the BIOS??  I don't have windoze at all and my next rig may not
>>>> have a floppy either.
>>>>         
>>> My new Asus motherboard updates from a USB stick.
>>>       
>
>   
>> LOL  I don't have one of those either.  Just my luck.  At least they
>> are looking ahead though. 
>>     
>
>   
>> Dale
>>     
>
> USB sticks are virtually worthless nowadays, for a couple tens of
> dollars you should be able to get one with a capacity of a few gigs.  
>
> There's also the possibility of writing directly to the cmos
> with /dev/nvram, isn't there?  It's a character device driver in the
> kernel.  
>   

I didn't know they were that cheap.  Don't they require a OS though?  I
don't have windoze around here.  ;-)

Dale

:-)  :-)  :-)

-- 
www.myspace.com/-remove-me-dalek1967

Copy n paste then remove the -remove-me- part.


[-- Attachment #2: Type: text/html, Size: 2085 bytes --]

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Dale]

Neil Walker wrote:
> Dale wrote:
>> Cool.  I'm a Linux only person here so this is something that I am
>> curious about.  That wouldn't happen to have been a Abit mobo would it?
>>   
>
> No, sorry. It was an Asus - which is mostly what I buy. However, the
> one arriving tomorrow is an Abit so I might know a bit more about them
> by then. My previous Abit was a PII-400 machine. ;) FWIW, my next one
> will be a Tyan dual socket F in a few weeks time. ;)
>
> Be lucky,
>
> Neil
>


I'm planning to try to build me a new rig soon, I hope.  I wouldn't mind
if you emailed me off list with how that went.  I run folding here so I
need all the cores I can get.  :-)

Dale

:-)  :-)  :-)

-- 
www.myspace.com/-remove-me-dalek1967

Copy n paste then remove the -remove-me- part.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Randy Barlow]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dale wrote:
>> USB sticks are virtually worthless nowadays, for a couple tens of
>> dollars you should be able to get one with a capacity of a few gigs.  
>>
>> There's also the possibility of writing directly to the cmos
>> with /dev/nvram, isn't there?  It's a character device driver in the
>> kernel.    

> I didn't know they were that cheap.  Don't they require a OS though?  I
> don't have windoze around here.  ;-)

They work just fine in Linux!

R

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGS38t7So1xaF/eR8RAkzEAKC3qHBpobIzFpZ5q8ZOCwGnJAbr1gCeKZsN
4OvwZ/dh/g0Wx6UT3CR3Rf0=
=cqFs
-----END PGP SIGNATURE-----
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Dale]

Randy Barlow wrote:
> Dale wrote:
> >> USB sticks are virtually worthless nowadays, for a couple tens of
> >> dollars you should be able to get one with a capacity of a few gigs.  
> >>
> >> There's also the possibility of writing directly to the cmos
> >> with /dev/nvram, isn't there?  It's a character device driver in the
> >> kernel.    
>
> > I didn't know they were that cheap.  Don't they require a OS though?  I
> > don't have windoze around here.  ;-)
>
> They work just fine in Linux!
>
> R
>

Oooops, let me rephrase that.  To update the BIOS, does it have to have
a OS on that stick?

On the other thingy:

> root@smoker / # ls -al /dev/nv*
> crw-rw-rw- 1 root root 195,   0 Apr 10 02:17 /dev/nvidia0
> crw-rw-rw- 1 root root 195, 255 Apr 10 02:17 /dev/nvidiactl
> root@smoker / # 

That's all the nvidia stuff I saw.  Maybe I need to check on that kernel
or a newer one may help.

Dale

:-)  :-)  :-)


-- 
www.myspace.com/-remove-me-dalek1967

Copy n paste then remove the -remove-me- part.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 347 bytes --]

On Wed, 16 May 2007 17:36:47 -0500, Dale wrote:

> Oooops, let me rephrase that.  To update the BIOS, does it have to have
> a OS on that stick?

No. The update code is built into the hardware now, if just needs a FAT
partition it can read the new firmware file from.


-- 
Neil Bothwick

I'm not broke, I'm `financially challenged'.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Dale]

[-- Attachment #1: Type: text/plain, Size: 545 bytes --]

Neil Bothwick wrote:
> On Wed, 16 May 2007 17:36:47 -0500, Dale wrote:
>
>   
>> Oooops, let me rephrase that.  To update the BIOS, does it have to have
>> a OS on that stick?
>>     
>
> No. The update code is built into the hardware now, if just needs a FAT
> partition it can read the new firmware file from.
>
>
>   

Now that is kewl!!  I need to make sure the next mobo I buy has that
feature.  ;-) 

Thanks for the info.

Dale

:-)  :-)  :-)  :-)

-- 
www.myspace.com/-remove-me-dalek1967

Copy n paste then remove the -remove-me- part.


[-- Attachment #2: Type: text/html, Size: 1149 bytes --]

Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8.

[Neil Walker]

Dale wrote:
>> No. The update code is built into the hardware now, if just needs a FAT
>> partition it can read the new firmware file from.
>>   
>
> Now that is kewl!!  I need to make sure the next mobo I buy has that 
> feature.  ;-) 

Or you can just emerge syslinux and boot a floppy image on your hd from 
grub - as I just did with my new Abit. ;)


Be lucky,

Neil

-- 
gentoo-user@gentoo.org mailing list