Samsung P35 and S3 suspend

Samsung P35 and S3 suspend

[Carl-Daniel Hailfinger]

Hi,

after having read what I believe to be all available information
about getting my Samsung P35 to resume properly from S3, having
tried dozens of patches, recompiled the kernel at least 20 times,
I hope that someone can shed some light on my failure to resume.

Every time I resume from S3 everything is dead. Keyboard, network,
serial port, you name it. Unloading modules doesn't help. Booting
with init=/bin/bash (to avoid loading any modules) doesn't help.
Booting a kernel without framebuffer support doesn't help.
Applying pci-resume-2.6.9.patch doesn't help. Loading a fixed
DSDT doesn't help. Combinations of all of the above don't work
either.

Right now I would be happy if at least the keyboard or network
would work, giving me a chance to shutdown the machine properly.

I'm not demanding a howto or something like that, only a few
hints where to look for improvement. For example, I could not
find the "old style resume" patch Oliver mentioned.

My current base is 2.6.10-rc3-bk8, but I'm willing to test any
2.6.x kernel with any patches and any .config you throw at me.

Thanks for your help!
Carl-Daniel


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Samsung P35 and S3 suspend

[Matthias Hentges]

Am Mittwoch, den 15.12.2004, 05:55 +0100 schrieb Carl-Daniel Hailfinger:
> Hi,
> 
> after having read what I believe to be all available information
> about getting my Samsung P35 to resume properly from S3, having
> tried dozens of patches, recompiled the kernel at least 20 times,
> I hope that someone can shed some light on my failure to resume.
> 
> Every time I resume from S3 everything is dead. Keyboard, network,
> serial port, you name it. Unloading modules doesn't help. Booting
> with init=/bin/bash (to avoid loading any modules) doesn't help.
> Booting a kernel without framebuffer support doesn't help.
> Applying pci-resume-2.6.9.patch doesn't help. Loading a fixed
> DSDT doesn't help. Combinations of all of the above don't work
> either.
> 
> Right now I would be happy if at least the keyboard or network
> would work, giving me a chance to shutdown the machine properly.
> 
> I'm not demanding a howto or something like that, only a few
> hints where to look for improvement. For example, I could not
> find the "old style resume" patch Oliver mentioned.
> 
> My current base is 2.6.10-rc3-bk8, but I'm willing to test any
> 2.6.x kernel with any patches and any .config you throw at me.

I haven't had any luck with resume on any kernel > 2.6.9 so far.
So, I suggest you try 2.6.9 and apply the patches from here:
http://www.hentges.net/misc/howtos/samsung_p30_s3.shtml

HTH

-- 
Matthias Hentges 
Cologne / Germany

[www.hentges.net] -> PGP welcome, HTML tolerated
ICQ: 97 26 97 4   -> No files, no URL's

My OS: Debian SID. Geek by Nature, Linux by Choice



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Samsung P35 and S3 suspend

[Carl-Daniel Hailfinger]

Matthias Hentges schrieb:
> Am Mittwoch, den 15.12.2004, 05:55 +0100 schrieb Carl-Daniel Hailfinger:
> 
>>[...]
>>Every time I resume from S3 everything is dead. Keyboard, network,
>>serial port, you name it. Unloading modules doesn't help. Booting
>>with init=/bin/bash (to avoid loading any modules) doesn't help.
>>Booting a kernel without framebuffer support doesn't help.
>>Applying pci-resume-2.6.9.patch doesn't help. Loading a fixed
>>DSDT doesn't help. Combinations of all of the above don't work
>>either.
>>[...]
>>My current base is 2.6.10-rc3-bk8, but I'm willing to test any
>>2.6.x kernel with any patches and any .config you throw at me.
> 
> 
> I haven't had any luck with resume on any kernel > 2.6.9 so far.
> So, I suggest you try 2.6.9 and apply the patches from here:
> http://www.hentges.net/misc/howtos/samsung_p30_s3.shtml

Do you have any hints what to exclude in the .config? The .config
which was once available in your forum is marked as "deleted
attachment" and cannot be downloaded.

Oh, and once I get S3 working with 2.6.9 I'll do a binary search
to find the changeset that is causing the problems after 2.6.9
and report back.

Thanks,
Carl-Daniel


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Samsung P35 and S3 suspend

[Matthias Hentges]

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

Am Mittwoch, den 15.12.2004, 18:59 +0100 schrieb Carl-Daniel Hailfinger:
> Matthias Hentges schrieb:

[...]

> > I haven't had any luck with resume on any kernel > 2.6.9 so far.
> > So, I suggest you try 2.6.9 and apply the patches from here:
> > http://www.hentges.net/misc/howtos/samsung_p30_s3.shtml
> 
> Do you have any hints what to exclude in the .config? The .config
> which was once available in your forum is marked as "deleted
> attachment" and cannot be downloaded.

Do not use any framebuffer, be it radeonfb or vesafb, it will freeze
your machine on resume. USB drivers should be built as modules and need
to be unloaded before suspending or USB might become FUBAR after a
resume. Besides that, I don't remember anything which I haven't noted on
my page (see above).

My currently loaded modules are:
+mhentges@mhcln03:..me/mhentges/opie-cvs/txt >lsmod
Module                  Size  Used by
ipw2100               142020  0 
ehci_hcd               29316  0 
usbhid                 30272  0 
uhci_hcd               30096  0 
usbcore               104804  5 ehci_hcd,usbhid,uhci_hcd
radeon                131044  2 
ieee80211_crypt_wep     4292  1 
firmware_class          7936  1 ipw2100
ieee80211              34980  1 ipw2100
ieee80211_crypt         4936  3 ipw2100,ieee80211_crypt_wep,ieee80211
intel_agp              19872  1 
agpgart                28712  2 intel_agp

+mhentges@mhcln03:..me/mhentges/opie-cvs/txt >uname -a
Linux mhcln03 2.6.9 #7 Sat Dec 11 01:00:41 CET 2004 i686 GNU/Linux

I've attached my current kernel .config for 2.6.9 and the suspend script
I'm using. 
It looks like an ugly hack but it is working very well for me
> 
> Oh, and once I get S3 working with 2.6.9 I'll do a binary search
> to find the changeset that is causing the problems after 2.6.9
> and report back.

That would be most appreciated. I still haven't fully recovered from
trying 30+ kernels / configurations to find the borked patch ;)

HTH & GL
-- 
Matthias Hentges 
Cologne / Germany

[www.hentges.net] -> PGP welcome, HTML tolerated
ICQ: 97 26 97 4   -> No files, no URL's

My OS: Debian SID. Geek by Nature, Linux by Choice

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

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.9
# Sat Dec 11 00:59:35 2004
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_POSIX_MQUEUE is not set
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_LOG_BUF_SHIFT=14
CONFIG_HOTPLUG=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=y
# CONFIG_TINY_SHMEM is not set

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

#
# Processor type and features
#
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_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_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_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
CONFIG_X86_GENERIC=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_HPET_TIMER=y
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
# CONFIG_X86_UP_APIC is not set
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_MICROCODE=m
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=m

#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y
# CONFIG_REGPARM is not set

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
CONFIG_PM_DEBUG=y
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_PM_STD_PARTITION="/dev/hda3"

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_ASUS=y
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_CUSTOM_DSDT=y
CONFIG_ACPI_CUSTOM_DSDT_FILE="/usr/src/dsdt2.hex"
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y

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

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_PROC_INTF=y
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=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_24_API is not set
CONFIG_CPU_FREQ_TABLE=y

#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=y
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF 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=y
CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y
CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y
# CONFIG_X86_SPEEDSTEP_ICH is not set
# CONFIG_X86_SPEEDSTEP_SMI is not set
# CONFIG_X86_P4_CLOCKMOD is not set
# CONFIG_X86_LONGRUN is not set
# CONFIG_X86_LONGHAUL 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_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# PCMCIA/CardBus support
#
CONFIG_PCMCIA=y
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_YENTA=y
CONFIG_CARDBUS=y
# CONFIG_PD6729 is not set
# CONFIG_I82092 is not set
# CONFIG_I82365 is not set
# CONFIG_TCIC is not set
CONFIG_PCMCIA_PROBE=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

#
# Device Drivers
#

#
# Generic Driver Options
#
# CONFIG_STANDALONE is not set
# CONFIG_PREVENT_FIRMWARE_BUILD is not set
CONFIG_FW_LOADER=m
# CONFIG_DEBUG_DRIVER is not set

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

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

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

#
# Protocols
#
# CONFIG_ISAPNP is not set
CONFIG_PNPBIOS=y
CONFIG_PNPBIOS_PROC_FS=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_LOOP=y
CONFIG_BLK_DEV_CRYPTOLOOP=y
# 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=m
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_LBD=y

#
# 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=m
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEFLOPPY=m
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_IDE_TASKFILE_IO is not set

#
# IDE chipset support/bugfixes
#
# CONFIG_IDE_GENERIC is not set
# CONFIG_BLK_DEV_CMD640 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 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
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_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# 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_SCSI=y
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=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y

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

#
# SCSI Transport Attributes
#
CONFIG_SCSI_SPI_ATTRS=y
# CONFIG_SCSI_FC_ATTRS is not set

#
# SCSI low-level drivers
#
# 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_DPT_I2O is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_SCSI_SATA 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_EATA_PIO 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_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR 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_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA6322 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

#
# 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

#
# 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

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

#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
CONFIG_IEEE1394_OUI_DB=y
CONFIG_IEEE1394_EXTRA_CONFIG_ROMS=y
CONFIG_IEEE1394_CONFIG_ROM_IP1394=y

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

#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_SBP2=m
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set
# CONFIG_IEEE1394_ETH1394 is not set
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_IEEE1394_CMP=m
CONFIG_IEEE1394_AMDTP=m

#
# I2O device support
#
CONFIG_I2O=y
CONFIG_I2O_CONFIG=m
CONFIG_I2O_BLOCK=m
CONFIG_I2O_SCSI=m
CONFIG_I2O_PROC=y

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
CONFIG_NET_KEY=m
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_ARPD=y
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_TUNNEL=m

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

#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=y
CONFIG_IP_NF_CT_ACCT=y
CONFIG_IP_NF_CT_PROTO_SCTP=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
CONFIG_IP_NF_TFTP=m
CONFIG_IP_NF_AMANDA=m
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_IPRANGE=y
CONFIG_IP_NF_MATCH_MAC=y
CONFIG_IP_NF_MATCH_PKTTYPE=y
CONFIG_IP_NF_MATCH_MARK=y
CONFIG_IP_NF_MATCH_MULTIPORT=y
CONFIG_IP_NF_MATCH_TOS=y
CONFIG_IP_NF_MATCH_RECENT=y
CONFIG_IP_NF_MATCH_ECN=y
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=y
CONFIG_IP_NF_MATCH_CONNTRACK=y
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_MATCH_ADDRTYPE=y
CONFIG_IP_NF_MATCH_REALM=m
CONFIG_IP_NF_MATCH_SCTP=m
CONFIG_IP_NF_MATCH_COMMENT=m
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_LOG=y
CONFIG_IP_NF_TARGET_ULOG=y
CONFIG_IP_NF_TARGET_TCPMSS=y
CONFIG_IP_NF_NAT=y
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=y
CONFIG_IP_NF_TARGET_REDIRECT=y
CONFIG_IP_NF_TARGET_NETMAP=y
CONFIG_IP_NF_TARGET_SAME=y
# CONFIG_IP_NF_NAT_LOCAL is not set
CONFIG_IP_NF_NAT_SNMP_BASIC=m
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_NAT_TFTP=m
CONFIG_IP_NF_NAT_AMANDA=m
CONFIG_IP_NF_MANGLE=y
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_CLASSIFY=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_TARGET_NOTRACK=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
CONFIG_XFRM=y
CONFIG_XFRM_USER=m

#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP 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_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
CONFIG_NET_CLS_ROUTE=y

#
# Network testing
#
CONFIG_NET_PKTGEN=m
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
CONFIG_IRDA=y

#
# IrDA protocols
#
CONFIG_IRLAN=m
# CONFIG_IRNET is not set
CONFIG_IRCOMM=m
CONFIG_IRDA_ULTRA=y

#
# IrDA options
#
CONFIG_IRDA_CACHE_LAST_LSAP=y
CONFIG_IRDA_FAST_RR=y
# CONFIG_IRDA_DEBUG is not set

#
# Infrared-port device drivers
#

#
# SIR device drivers
#
CONFIG_IRTTY_SIR=y

#
# Dongle support
#
# CONFIG_DONGLE is not set

#
# Old SIR device drivers
#
CONFIG_IRPORT_SIR=m

#
# Old Serial dongle support
#
# CONFIG_DONGLE_OLD is not set

#
# FIR device drivers
#
# CONFIG_USB_IRDA is not set
CONFIG_SIGMATEL_FIR=m
CONFIG_NSC_FIR=m
CONFIG_WINBOND_FIR=m
CONFIG_TOSHIBA_FIR=m
CONFIG_SMC_IRCC_FIR=m
CONFIG_ALI_FIR=m
CONFIG_VLSI_FIR=m
CONFIG_VIA_FIR=m
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=m

#
# Bluetooth device drivers
#
# CONFIG_BT_HCIUSB is not set
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
# CONFIG_BT_HCIUART_BCSP_TXCRC is not set
# CONFIG_BT_HCIBCM203X is not set
# CONFIG_BT_HCIBFUSB is not set
CONFIG_BT_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIBTUART=m
CONFIG_BT_HCIVHCI=m
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

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM 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 is not set
# 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 is not set
CONFIG_8139TOO_TUNE_TWISTER=y
CONFIG_8139TOO_8129=y
CONFIG_8139_OLD_RX_RESET=y
# 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_VIA_VELOCITY 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_SK98LIN is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set

#
# Wireless LAN (non-hamradio)
#
CONFIG_NET_RADIO=y

#
# 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_AIRO=m
CONFIG_HERMES=m
CONFIG_PLX_HERMES=m
CONFIG_TMD_HERMES=m
CONFIG_PCI_HERMES=m
CONFIG_ATMEL=m
CONFIG_PCI_ATMEL=m

#
# Wireless 802.11b Pcmcia/Cardbus cards support
#
CONFIG_PCMCIA_HERMES=m
CONFIG_AIRO_CS=m
CONFIG_PCMCIA_ATMEL=m
CONFIG_PCMCIA_WL3501=m

#
# Prism GT/Duette 802.11(a/b/g) PCI/Cardbus support
#
CONFIG_PRISM54=m
CONFIG_NET_WIRELESS=y

#
# PCMCIA network device support
#
CONFIG_NET_PCMCIA=y
CONFIG_PCMCIA_3C589=m
CONFIG_PCMCIA_3C574=m
CONFIG_PCMCIA_FMVJ18X=m
CONFIG_PCMCIA_PCNET=m
CONFIG_PCMCIA_NMCLAN=m
CONFIG_PCMCIA_SMC91C92=m
CONFIG_PCMCIA_XIRC2PS=m
CONFIG_PCMCIA_AXNET=m

#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPPOE=m
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLIP_SMART=y
# CONFIG_SLIP_MODE_SLIP6 is not set
# CONFIG_NET_FC is not set
CONFIG_SHAPER=m
# CONFIG_NETCONSOLE is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# 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=y
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
CONFIG_SERIO_PCIPS2=m
# CONFIG_SERIO_RAW 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_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_SERIAL=m
# 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=y
CONFIG_INPUT_PCSPKR=y
CONFIG_INPUT_UINPUT=y

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

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
# CONFIG_SERIAL_8250_CS is not set
CONFIG_SERIAL_8250_ACPI=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
# CONFIG_SERIAL_8250_MANY_PORTS is not set
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
# CONFIG_SERIAL_8250_MULTIPORT is not set
# CONFIG_SERIAL_8250_RSA is not set

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

#
# IPMI
#
CONFIG_IPMI_HANDLER=m
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
CONFIG_NVRAM=m
# 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

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=m
# 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=m
# CONFIG_AGP_INTEL_MCH is not set
# 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=m
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_I915 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set

#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
CONFIG_HPET_MMAP=y
# CONFIG_HANGCHECK_TIMER is not set

#
# I2C support
#
CONFIG_I2C=m
CONFIG_I2C_CHARDEV=m

#
# 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_ISA is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PIIX4 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_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set
# CONFIG_I2C_PCA_ISA is not set

#
# Hardware Sensors Chip support
#
# CONFIG_I2C_SENSOR is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_IT87 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_LM90 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83627HF is not set

#
# Other I2C Chip support
#
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_RTC8564 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

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

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

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

#
# Graphics support
#
CONFIG_FB=y
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_DEBUG=y
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY 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_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_FONT_6x11=y
CONFIG_FONT_PEARL_8x8=y
CONFIG_FONT_ACORN_8x8=y
CONFIG_FONT_MINI_4x6=y
CONFIG_FONT_SUN8x16=y
CONFIG_FONT_SUN12x22=y

#
# Logo configuration
#
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y

#
# Bootsplash configuration
#

#
# Sound
#
CONFIG_SOUND=y

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_RAWMIDI=y
CONFIG_SND_SEQUENCER=y
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
CONFIG_SND_MPU401_UART=y
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# ISA devices
#
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_WAVEFRONT is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set

#
# PCI devices
#
CONFIG_SND_AC97_CODEC=y
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=y
CONFIG_SND_INTEL8X0M=y
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set

#
# ALSA USB devices
#
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set

#
# PCMCIA devices
#
# CONFIG_SND_VXPOCKET is not set
# CONFIG_SND_VXP440 is not set
# CONFIG_SND_PDAUDIOCF is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
CONFIG_USB=m
# 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=m
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=m

#
# USB Device Class drivers
#
CONFIG_USB_AUDIO=m

#
# USB Bluetooth TTY can only be used with disabled Bluetooth subsystem
#
# CONFIG_USB_MIDI is not set
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_RW_DETECT is not set
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_HP8200e=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y

#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y

#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_MTOUCH is not set
# CONFIG_USB_EGALAX is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set

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

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set

#
# Video4Linux support is needed for USB Multimedia device support
#

#
# USB Network adaptors
#
CONFIG_USB_CATC=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_USBNET=m

#
# USB Host-to-Host Cables
#
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_GENESYS=y
CONFIG_USB_NET1080=y
CONFIG_USB_PL2301=y

#
# Intelligent USB Devices/Gadgets
#
CONFIG_USB_ARMLINUX=y
CONFIG_USB_EPSON2888=y
CONFIG_USB_ZAURUS=y
CONFIG_USB_CDCETHER=y

#
# USB Network Adapters
#
CONFIG_USB_AX8817X=y

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set

#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
# CONFIG_USB_SERIAL_BELKIN is not set
# CONFIG_USB_SERIAL_WHITEHEAT is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
# CONFIG_USB_SERIAL_EMPEG is not set
# CONFIG_USB_SERIAL_FTDI_SIO is not set
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_EDGEPORT_TI is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_KOBIL_SCT is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_PL2303 is not set
# CONFIG_USB_SERIAL_SAFE is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_XIRCOM is not set
# CONFIG_USB_SERIAL_OMNINET is not set

#
# USB Miscellaneous drivers
#
CONFIG_USB_EMI62=m
CONFIG_USB_EMI26=m
# CONFIG_USB_TIGL 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_CYTHERM is not set
# CONFIG_USB_PHIDGETSERVO is not set
# CONFIG_USB_TEST is not set

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR 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_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
CONFIG_JFS_FS=m
# CONFIG_JFS_POSIX_ACL is not set
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
# CONFIG_XFS_RT is not set
# CONFIG_XFS_QUOTA is not set
# CONFIG_XFS_SECURITY is not set
# CONFIG_XFS_POSIX_ACL is not set
CONFIG_MINIX_FS=m
CONFIG_ROMFS_FS=m
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
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-15"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# 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=m
# 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=y
CONFIG_NFS_V4=y
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
CONFIG_RPCSEC_GSS_KRB5=y
# CONFIG_RPCSEC_GSS_SPKM3 is not set
CONFIG_SMB_FS=m
# CONFIG_SMB_NLS_DEFAULT is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
CONFIG_LDM_PARTITION=y
CONFIG_LDM_DEBUG=y
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_EFI_PARTITION is not set

#
# 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=y
# 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 is not set
# 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 is not set
# 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=y
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_INFO is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_KPROBES is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_4KSTACKS is not set
# CONFIG_SCHEDSTATS is not set

#
# Security options
#
CONFIG_SECURITY=y
# CONFIG_SECURITY_NETWORK is not set
CONFIG_SECURITY_CAPABILITIES=m
# CONFIG_SECURITY_ROOTPLUG is not set
# CONFIG_SECURITY_SELINUX is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=y
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_SHA512=y
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES_586=y
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=y
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=y
# CONFIG_CRYPTO_TEST is not set

#
# Library routines
#
CONFIG_CRC_CCITT=y
CONFIG_CRC32=y
CONFIG_LIBCRC32C=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y

[-- Attachment #3: s3_sleep --]
[-- Type: application/x-shellscript, Size: 2906 bytes --]

Re: Re: Samsung P35 and S3 suspend

[Carl-Daniel Hailfinger]

Matthias Hentges schrieb:
> 
>> Matthias Hentges schrieb:
>> 
>>>I haven't had any luck with resume on any kernel > 2.6.9 so far.
>>>So, I suggest you try 2.6.9 and apply the patches from here:
>>>http://www.hentges.net/misc/howtos/samsung_p30_s3.shtml

> Am Mittwoch, den 15.12.2004, 18:59 +0100 schrieb Carl-Daniel Hailfinger:
> 
>>Do you have any hints what to exclude in the .config? The .config
>>which was once available in your forum is marked as "deleted
>>attachment" and cannot be downloaded.
> 
> Do not use any framebuffer, be it radeonfb or vesafb, it will freeze
> your machine on resume. USB drivers should be built as modules and need
> to be unloaded before suspending or USB might become FUBAR after a
> resume. Besides that, I don't remember anything which I haven't noted on
> my page (see above).
> [...]
> 
> I've attached my current kernel .config for 2.6.9 and the suspend script
> I'm using. 
> It looks like an ugly hack but it is working very well for me

Thanks! While you wrote your mail, I got S3 working here, but your suspend
script is very appreciated.


>>Oh, and once I get S3 working with 2.6.9 I'll do a binary search
>>to find the changeset that is causing the problems after 2.6.9
>>and report back.
> 
> That would be most appreciated. I still haven't fully recovered from
> trying 30+ kernels / configurations to find the borked patch ;)

A first hint: CONFIG_REGPARM killed swsusp in some kernels before
2.6.10-rc3, it could also be the culprit for S3.

Besides that, I think we could convince the X.Org developers that
the "get display working" bug is their problem ;-)
It seems they have merged some suspend/resume bugfixes for Radeon and
will merge at least one more bugfix in the next few days. Basically,
it should be possible that the normal Radeon Xserver rePOSTs the card
itself once it detects a resume event. If that is done properly, we
could get rid of the hack completely and would only have to live with
the text console.

Once these patches are merged completely, I'll try a current X.Org
build and open a bug with X.Org if the situation isn't better.


Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Carl-Daniel Hailfinger]

Carl-Daniel Hailfinger schrieb:
> Matthias Hentges schrieb:
> 
>>Am Mittwoch, den 15.12.2004, 18:59 +0100 schrieb Carl-Daniel Hailfinger:
>>
>>>Oh, and once I get S3 working with 2.6.9 I'll do a binary search
>>>to find the changeset that is causing the problems after 2.6.9
>>>and report back.
>>
>>That would be most appreciated. I still haven't fully recovered from
>>trying 30+ kernels / configurations to find the borked patch ;)
> 
> A first hint: CONFIG_REGPARM killed swsusp in some kernels before
> 2.6.10-rc3, it could also be the culprit for S3.

OK, I got S3 working with all kernels since 2.6.9 (well, your patches
had to be modified slightly). Right now I'm running on the latest
Linus -bk tree.

I will now try other configurations and a full bootup.

Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Stefan Dösinger]

> OK, I got S3 working with all kernels since 2.6.9 (well, your patches
> had to be modified slightly). Right now I'm running on the latest
> Linus -bk tree.
>
> I will now try other configurations and a full bootup.
Just a note about 2.6.10-rc2/3 kernels: I also had some Problems with them. 
snd-Intel8x0 needs an update concerning PCI config save/restore and ehci-hcd 
causes problems after resume. uhci-hcd suspend/resume works for me, except 
that I must not plug or unplug usb devices while the system is supended.

> Besides that, I think we could convince the X.Org developers that
> the "get display working" bug is their problem ;-)
> It seems they have merged some suspend/resume bugfixes for Radeon and
> will merge at least one more bugfix in the next few days. Basically,
> it should be possible that the normal Radeon Xserver rePOSTs the card
> itself once it detects a resume event. If that is done properly, we
> could get rid of the hack completely and would only have to live with
> the text console.
No, I think it's the kernels problem. The various framebuffer drivers should 
know how to wake up the card.
There were some discussions on the linux-fbdev-devel list about writing a 
lightwhight(20-30k) 8086 emulator for the kernel to avoid real mode hacks.
As far as I know, this should be based on the 8086 emulator XFree/X.org uses.

Cheers,
Stefan


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Carl-Daniel Hailfinger]

Stefan Dösinger schrieb:
>>OK, I got S3 working with all kernels since 2.6.9 (well, your patches
>>had to be modified slightly). Right now I'm running on the latest
>>Linus -bk tree.
>>
>>I will now try other configurations and a full bootup.
> 
> Just a note about 2.6.10-rc2/3 kernels: I also had some Problems with them. 
> snd-Intel8x0 needs an update concerning PCI config save/restore and ehci-hcd 
> causes problems after resume. uhci-hcd suspend/resume works for me, except 
> that I must not plug or unplug usb devices while the system is supended.

Could you go into more detail? Changing the hardware config while suspended
is obviously not recommended, but what are the exact problems occuring
besides that?


>>Besides that, I think we could convince the X.Org developers that
>>the "get display working" bug is their problem ;-)
>>It seems they have merged some suspend/resume bugfixes for Radeon and
>>will merge at least one more bugfix in the next few days. Basically,
>>it should be possible that the normal Radeon Xserver rePOSTs the card
>>itself once it detects a resume event. If that is done properly, we
>>could get rid of the hack completely and would only have to live with
>>the text console.
> 
> No, I think it's the kernels problem. The various framebuffer drivers should 
> know how to wake up the card.
> There were some discussions on the linux-fbdev-devel list about writing a 
> lightwhight(20-30k) 8086 emulator for the kernel to avoid real mode hacks.
> As far as I know, this should be based on the 8086 emulator XFree/X.org uses.

Yes, but for that to work we should have a procedure in place which allows
us to get the card working again without having to crash a secondary vesa
xserver. If boot-radeon could be extended to do the things the crashing
vesa xserver does, we would be much better off. That could be folded
a) into the kernel framebuffer drivers
b) into the radeon xserver.


Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Stefan Dösinger]

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


> > Just a note about 2.6.10-rc2/3 kernels: I also had some Problems with
> > them. snd-Intel8x0 needs an update concerning PCI config save/restore and
> > ehci-hcd causes problems after resume. uhci-hcd suspend/resume works for
> > me, except that I must not plug or unplug usb devices while the system is
> > supended.
>
> Could you go into more detail? Changing the hardware config while suspended
> is obviously not recommended, but what are the exact problems occuring
> besides that?
I get a kernel panic at resume if I plugged in a device while suspended 
(Capslock led blinking, screen stays black)
The system locks during resume up if I unplug a device while in S3(capslock 
led not blinking, screen stays black too.)

> > No, I think it's the kernels problem. The various framebuffer drivers 
should 
> > know how to wake up the card.
> > There were some discussions on the linux-fbdev-devel list about writing a 
> > lightwhight(20-30k) 8086 emulator for the kernel to avoid real mode hacks.
> > As far as I know, this should be based on the 8086 emulator XFree/X.org 
uses.

> Yes, but for that to work we should have a procedure in place which allows
> us to get the card working again without having to crash a secondary vesa
> xserver. If boot-radeon could be extended to do the things the crashing
> vesa xserver does, we would be much better off. That could be folded
> a) into the kernel framebuffer drivers
> b) into the radeon xserver.
In the ideal case the frame buffer driver would run the VGA Rom post 
routine($0xc000:$3) in an X86 emulator(or in vm86 mode if it works), set up 
the frame buffer and at the end of the resume function the device is in the 
same state where it was before suspend and user mode programs like the 
X-Server won't recognise that the system was suspended.
That's at least my opinion.

Boot-radeon and the others are supposed to do that(in User mode), but the 
80x86 environment they set up seems to be incorrect in some way so they crash 
before they finish their task on some systems. If it works, the display comes 
back without any Vesa X11 server.

Attached is a patch against Xorg-6.8.0 which makes the radeon X11 driver call 
the reset routine if it notices that the system was in S3. This patch is 
quite uncomfortable because it's necessary to recompile X11. It is from 
Gentoo where it is compiled by default.

Stefan

[-- Attachment #2: 9375_all_6.7.0-radeon-resume-from-S3-suspend.patch --]
[-- Type: text/x-diff, Size: 1508 bytes --]

This enables resume from suspend level S3 by asking the Radeon chip if it
thinks it has no memory.  If so, the card is re-POSTed via the int10
interface.  Reportedly enables the driver to work for this type of
suspend/resume cycle on Dell D600 laptops (Dell D800s as well, if the video
BIOS is patched to 4.28.20.31.C1 or later). See Gentoo bug #48095 or Debian bug
#234575. This patch by Emmanuel Thome and Ole Rohne, and this info borrowed from
Debian.

--- xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c	2003-10-25 00:10:20.000000000 +0200
+++ xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c.new	2003-11-22 17:20:14.000000000 +0100
@@ -345,6 +345,7 @@
     "xf86InitInt10",
     "xf86FreeInt10",
     "xf86int10Addr",
+    "xf86ExecX86int10",
     NULL
 };
 
@@ -6409,9 +6410,22 @@
 {
     ScrnInfoPtr    pScrn = xf86Screens[scrnIndex];
     RADEONInfoPtr  info  = RADEONPTR(pScrn);
+    unsigned char * RADEONMMIO = info->MMIO;
 
     RADEONTRACE(("RADEONEnterVT\n"));
 
+    if (INREG(RADEON_CONFIG_MEMSIZE) == 0) { /* Softboot V_BIOS */
+      xf86Int10InfoPtr pInt;
+	xf86DrvMsg(pScrn->scrnIndex, X_WARNING,
+	       "zero MEMSIZE, probably at D3cold. Re-POSTing via int10.\n");
+      pInt = xf86InitInt10 (info->pEnt->index);
+      if (pInt) {
+        pInt->num = 0xe6;
+        xf86ExecX86int10 (pInt);
+        xf86FreeInt10 (pInt);
+      }
+    }
+
     if (info->FBDev) {
 	unsigned char *RADEONMMIO = info->MMIO;
 	if (!fbdevHWEnterVT(scrnIndex,flags)) return FALSE;

Re: Re: Samsung P35 and S3 suspend

[Matthew Garrett]

On Thu, 2004-12-16 at 21:57 +0100, Stefan Dösinger wrote:

> In the ideal case the frame buffer driver would run the VGA Rom post 
> routine($0xc000:$3) in an X86 emulator(or in vm86 mode if it works), set up 
> the frame buffer and at the end of the resume function the device is in the 
> same state where it was before suspend and user mode programs like the 
> X-Server won't recognise that the system was suspended.
> That's at least my opinion.

It turns out that this works badly. A large number of machines have code
at c000:0003 that jumps to somewhere else in the video ROM - this
executes a small amount of code (normally turning off the screen) and
then jumps elsewhere. In laptop hardware, this second jump is often to
code that is no longer mapped into address space. I've seen several
machines where trying to run POST code under XFree's x86 emulator fails
because it suddenly hits a pile of binary that looks nothing like the
x86 instruction set.

(This is fairly easy to test, by the way - you can generally dump the
video rom by dding out of /dev/kmem. Disassemble it and work out where
it jumps to, and then disassemble that. Keep following it and you may
well end up discovering that it jumps out to code that you're not able
to get hold of)

POSTing will help in some cases (it seems to work well on Thinkpads),
but it's not a universal cure. I've had more joy with saving and
restoring the VBE state.

-- 
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Stefan Dösinger]

> It turns out that this works badly. A large number of machines have code
> at c000:0003 that jumps to somewhere else in the video ROM - this
> executes a small amount of code (normally turning off the screen) and
> then jumps elsewhere. In laptop hardware, this second jump is often to
> code that is no longer mapped into address space. I've seen several
> machines where trying to run POST code under XFree's x86 emulator fails
> because it suddenly hits a pile of binary that looks nothing like the
> x86 instruction set.
This is partially true for my system. The instruction at c000:0003 is a JMP. 
But the code seems to remain in the area around 0xc0000. A jump somewhere 
else is a good explanation for the crashes on some machines.

Is this code used by the system bios to boot the VGA card when powering on the 
machine?

> POSTing will help in some cases (it seems to work well on Thinkpads),
> but it's not a universal cure. I've had more joy with saving and
> restoring the VBE state.
Is this the vbestate utility? I'll have a look at it. What does 
vm86_video_post do? It looks like another lrmi based "call c000:0003 
utility". Can only saving and restoring the VBE state bring the card back to 
live or do I need to call the reset routine in any case?

Stefan


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Matthew Garrett]

On Thu, 2004-12-16 at 22:26 +0100, Stefan Dösinger wrote:

> This is partially true for my system. The instruction at c000:0003 is a JMP. 
> But the code seems to remain in the area around 0xc0000. A jump somewhere 
> else is a good explanation for the crashes on some machines.
> 
> Is this code used by the system bios to boot the VGA card when powering on the 
> machine?

Yup. However, bear in mind that a typical laptop BIOS is about 512K.
There's a lot of code that's used during boot, but then unmapped again
because it shouldn't be needed by any user application. Depending on
your machine, this may include stuff that's used for video POSTing.

> > POSTing will help in some cases (it seems to work well on Thinkpads),
> > but it's not a universal cure. I've had more joy with saving and
> > restoring the VBE state.
> Is this the vbestate utility? I'll have a look at it. What does 
> vm86_video_post do? It looks like another lrmi based "call c000:0003 
> utility". Can only saving and restoring the VBE state bring the card back to 
> live or do I need to call the reset routine in any case?

vm86_video_post is just an lrmi-based POST tool, yeah - I hacked it
together after speaking to some of the X.org people and discovering that
they don't have too much faith in the correctness of the x86emu code.
One advantage it does have over most of the POST tools is that it puts
the device it's initialising in ax, which seems to make a difference in
some hardware. On the Dell X300, just calling the POST code results in
nasty screen effects. Having the PCI ID in ax seems to avoid this.

I'm not sure whether saving and restoring VBE state is sufficient. It
seems quite effective in combination with POSTing.
-- 
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Carl-Daniel Hailfinger]

Stefan Dösinger schrieb:
> Attached is a patch against Xorg-6.8.0 which makes the radeon X11 driver call 
> the reset routine if it notices that the system was in S3. This patch is 
> quite uncomfortable because it's necessary to recompile X11. It is from 
> Gentoo where it is compiled by default.

That patch has been merged into the 6.8.x tree at X.Org three minutes ago,
so it will be in the 6.8.2 release.

Did I understand correctly that with this patch should make POSTing the card
with boot-radeon unnecessary? Current 6_8_BRANCH X.Org is building here at
the moment, will report back when it is installed.

Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Stefan Dösinger]

> That patch has been merged into the 6.8.x tree at X.Org three minutes ago,
> so it will be in the 6.8.2 release.
>
> Did I understand correctly that with this patch should make POSTing the
> card with boot-radeon unnecessary? Current 6_8_BRANCH X.Org is building
> here at the moment, will report back when it is installed.
Yes, that's correct.

It was AFAIK the first way to wake up the radeon card. boot-radeon was written 
based on the X11 patch.

Stefan


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Carl-Daniel Hailfinger]

Stefan Dösinger schrieb:
>>That patch has been merged into the 6.8.x tree at X.Org three minutes ago,
>>so it will be in the 6.8.2 release.
>>
>>Did I understand correctly that with this patch should make POSTing the
>>card with boot-radeon unnecessary? Current 6_8_BRANCH X.Org is building
>>here at the moment, will report back when it is installed.

(I built X.Org CVS HEAD, but it has the same patch.)


> Yes, that's correct.
> 
> It was AFAIK the first way to wake up the radeon card. boot-radeon was written 
> based on the X11 patch.

Unfortunately, that fails on my Samsung P35. (Well, at least the display
backlight comes back and the machine doesn't crash.)

Messages by the X server after resume:

(WW) RADEON(0): zero MEMSIZE, probably at D3cold. Re-POSTing via int10.
(II) RADEON(0): Primary V_BIOS segment is: 0xc000
(EE) RADEON(0): unknown reason for exception
(II) RADEON(0): EAX=0x00004e08, EBX=0x00000106, ECX=0x00000000, EDX=0x000030fa
(II) RADEON(0): ESP=0x00000fb2, EBP=0x00000fba, ESI=0x00003d17, EDI=0x00000000
(II) RADEON(0): CS=0x5110, SS=0x0100, DS=0x0040, ES=0x0000, FS=0x0000, GS=0x0000
(II) RADEON(0): EIP=0x0000ffff, EFLAGS=0x00033206
(II) stack at 0x00001fb2:
 aa 3d 00 f0 52 3d 18 f9 00 c0 00 00 00 00 f9 01
 00 00 ce 0f 06 01 fa 30 00 00 08 4e f9 95 00 c0
 46 32 ad 08 56 08 00 00 00 00 00 00 00 00 00 00
 00 00 f8 0f 00 00 00 00 00 00 00 00 00 00 00 00
 00 00 00 01 00 00 00 00 40 00 00 06 00 00
(II) RADEON(0): code at 0x000610ff:
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
(EE) RADEON(0): cannot continue
(II) RADEON(0): BIOS HotKeys Disabled
(II) Mouse[1]: ps2EnableDataReporting: succeeded

Especially CS:EIP looks suspicious.

So what step would be next? IIRC on the P35 needed a crashing VESA server
in addition to boot-radeon. Can that step be added somehow to the Radeon
X server?


Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Carl-Daniel Hailfinger]

Carl-Daniel Hailfinger schrieb:
> Carl-Daniel Hailfinger schrieb:
> 
>>Matthias Hentges schrieb:
>>
>>
>>>Am Mittwoch, den 15.12.2004, 18:59 +0100 schrieb Carl-Daniel Hailfinger:
>>>
>>>
>>>>Oh, and once I get S3 working with 2.6.9 I'll do a binary search
>>>>to find the changeset that is causing the problems after 2.6.9
>>>>and report back.
>>>
>>>That would be most appreciated. I still haven't fully recovered from
>>>trying 30+ kernels / configurations to find the borked patch ;)
>>
>>A first hint: CONFIG_REGPARM killed swsusp in some kernels before
>>2.6.10-rc3, it could also be the culprit for S3.
> 
> OK, I got S3 working with all kernels since 2.6.9 (well, your patches
> had to be modified slightly). Right now I'm running on the latest
> Linus -bk tree.
> 
> I will now try other configurations and a full bootup.

OK, it is working perfectly with the latest Linus -bk tree and
everything configured in (SuSE .config, comparable to allmodconfig).
The only things which are NOT enabled are:
-CONFIG_REGPARM
-CONFIG_HIGHMEM
-CONFIG_EFI
-CONFIG_FB
-CONFIG_VIDEO_SELECT

Before suspending, I start both X-Servers (like you) and then
chvt 1
modprobe -r uhci_hcd ehci_hcd ohci1394 snd_intel8x0
sleep 5
echo 3 >/proc/acpi/sleep

Resume procedure is the same as yours.

I'm still trying to figure out what the Vesa X-Server does what
can't be done with vbetest or similar.

Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Matthias Hentges]

Am Donnerstag, den 16.12.2004, 19:10 +0100 schrieb Carl-Daniel
Hailfinger:
> Carl-Daniel Hailfinger schrieb:

[...]

> OK, it is working perfectly with the latest Linus -bk tree and
> everything configured in (SuSE .config, comparable to allmodconfig).
> The only things which are NOT enabled are:
> -CONFIG_REGPARM
> -CONFIG_HIGHMEM
> -CONFIG_EFI
> -CONFIG_FB
> -CONFIG_VIDEO_SELECT

I'll try that, thanks :)

> Before suspending, I start both X-Servers (like you) and then
> chvt 1
> modprobe -r uhci_hcd ehci_hcd ohci1394 snd_intel8x0
> sleep 5
> echo 3 >/proc/acpi/sleep

Basically the same here.

> Resume procedure is the same as yours.
> 
> I'm still trying to figure out what the Vesa X-Server does what
> can't be done with vbetest or similar.

Here's my theory:

All that is needed to bring back our card is:
1: VGA POST
2. VESA reset

The kernel parameter "acpi_sleep=s3_bios,s3_mode" would do just that.
But for some retarded reason, any kernel access to the card freezes the
machine.

Find the reason, and the kernel parameter should work perfectly.
Maybe even framebuffer could be used (and hence, bootsplash).


-- 
Matthias Hentges 
Cologne / Germany

[www.hentges.net] -> PGP welcome, HTML tolerated
ICQ: 97 26 97 4   -> No files, no URL's

My OS: Debian SID. Geek by Nature, Linux by Choice



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Matthew Garrett]

On Thu, 2004-12-16 at 19:41 +0100, Matthias Hentges wrote:

> 1: VGA POST
> 2. VESA reset

Can you try the vm86_video_post and vbestate programs from
http://www.srcf.ucam.org/~mjg59/laptops/ ? You want to do something like
this:

1) chvt away from X on suspend
2) vbestate save >/tmp/state
3) suspend
4) resume
5) vm86_video_post
6) vbestate restore </tmp/state
7) chvt back to X

This sequence (possibly with a dpms on in there somewhere) seems to work
on a fairly large number of machines.

-- 
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Carl-Daniel Hailfinger]

Matthew Garrett schrieb:
> On Thu, 2004-12-16 at 19:41 +0100, Matthias Hentges wrote:
> 
> 
>>1: VGA POST
>>2. VESA reset
> 
> 
> Can you try the vm86_video_post and vbestate programs from
> http://www.srcf.ucam.org/~mjg59/laptops/ ? You want to do something like
> this:
> 
> 1) chvt away from X on suspend
> 2) vbestate save >/tmp/state
> 3) suspend
> 4) resume
> 5) vm86_video_post
> 6) vbestate restore </tmp/state
> 7) chvt back to X
> 
> This sequence (possibly with a dpms on in there somewhere) seems to work
> on a fairly large number of machines.

It sort of works. Before step 7, the (text mode) display contains garbage.
But it is much more comfortable than starting a second X server.
Any chance to get the functionality into
- the X.Org Radeon server and
- the kernel to make suspend work with framebuffer console?

Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Carl-Daniel Hailfinger]

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

PROBLEM SOLVED COMPLETELY! Read on for details (and excuse the yelling)
;-)

Search engine hint: Samsung P30 P35 S3 suspend resume

Carl-Daniel Hailfinger schrieb:
> Matthew Garrett schrieb:
> 
>>On Thu, 2004-12-16 at 19:41 +0100, Matthias Hentges wrote:
>>
>>
>>
>>>1: VGA POST
>>>2. VESA reset
>>
>>
>>Can you try the vm86_video_post and vbestate programs from
>>http://www.srcf.ucam.org/~mjg59/laptops/ ? You want to do something like
>>this:
>>
>>1) chvt away from X on suspend
>>2) vbestate save >/tmp/state
>>3) suspend
>>4) resume
>>5) vm86_video_post
>>6) vbestate restore </tmp/state
>>7) chvt back to X
>>
>>This sequence (possibly with a dpms on in there somewhere) seems to work
>>on a fairly large number of machines.
> 
> 
> It sort of works. Before step 7, the (text mode) display contains garbage.

OK, I have a patch for vbestate which allows resume back to a text console
(no X server involved at all) and you should have clean fonts and usable
text console afterwards. The screen needs to be redrawn and Unicode fonts
have to be reloaded, but that can be handled, too.

The following script makes S3 from text console and/or X a breeze:

#!/bin/bash
statedir=/root/s3/state
curcons=`fgconsole`
fuser /dev/tty$curcons 2>/dev/null|xargs ps -o comm= -p|grep -q X && chvt 2
cat /dev/vcsa >$statedir/vcsa
sync
echo 3 >/proc/acpi/sleep
sync
vm86_video_post
vbestate restore <$statedir/vbe.5
cat $statedir/vcsa >/dev/vcsa
rckbd restart
chvt $[curcons%6+1]
chvt $curcons

IMPORTANT NOTES:
$statedir/vbe should be saved directly after bootup before entering X. It
only has to be saved once, you can use it for every situation afterwards.
That includes new boots, having switched from X to console, etc.
vbestate has to be patched with my patch to work correctly.
The script assumes that no harmful modules are loaded.
The kernel was 2.6.10-rc3 or later and had to be patched with
pci-resume-2.6.10.patch and resume-finish-split.patch.
.config available on request (see earlier in this thread for details).
You don't need a patched X for this to work.

With the above script my machine survived 32 iterations of S3 suspend
without any visible problems (no screen corruption, no freezes, even
umlauts are preserved). Sometimes I was in X, sometimes working on the
text console and it came back every time to the console I had used,
screen contents exactly the same as before.

Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/

[-- Attachment #2: vbestate-s3.diff --]
[-- Type: text/plain, Size: 778 bytes --]

diff -urN vbestate-0.1/vbestate.c vbestate-0.1-s3/vbestate.c
--- vbestate-0.1/vbestate.c	2004-12-09 00:42:51.000000000 +0100
+++ vbestate-0.1-s3/vbestate.c	2004-12-21 01:37:06.132044112 +0100
@@ -119,6 +119,9 @@
 		short tmpbuffer[524288];
 		size_t i,length=0;
 		
+		/* The loop below doesn't make any sense unless we think our
+		input data contains length/sizeof(tmpbuffer)*sizeof(tmpbuffer)
+		bytes of leading garbage */
 		while (i=read(0, tmpbuffer, sizeof(tmpbuffer))) {
 			length+=i;
 		}
@@ -127,6 +130,12 @@
 		memcpy(data,tmpbuffer,length);
 
 		restore_state(data);
+		text_mode();
+
+		data = LRMI_alloc_real(length);
+		memcpy(data,tmpbuffer,length);
+
+		restore_state(data);
 	} else {
 		fprintf(stderr,"%s: Usage %s [save|restore]\n",
 			argv[0],argv[0]);

Re: Re: Samsung P35 and S3 suspend

[Carl-Daniel Hailfinger]

Carl-Daniel Hailfinger wrote:

> OK, I got S3 working with all kernels since 2.6.9 (well, your
> patches had to be modified slightly). Right now I'm running on the
> latest Linus -bk tree.
>
> I will now try other configurations and a full bootup.
>
> OK, it is working perfectly with the latest Linus -bk tree and
> everything configured in (SuSE .config, comparable to allmodconfig).

It turns out that (at least for 2.6.10-rc3 and later) the kernel
resumes from S3 perfectly regardless of .config as long as
- no framebuffer console is activated (kernel param video=vesa:off )
- pci-resume-2.6.10.patch and resume-finish-split-2.6.10.patch
  are applied
- suspend and resume happen with an active TEXT console (chvt 2)
- VESA registers are saved before suspend
- the radeon card is POSTed after resume
- the VESA registers are restored after that
- now you are free to change back to X if you want.

You do NOT need
- a patched X server
- a special kernel .config
- sacrifices of any kind.

See my other mail to acpi-devel for details about how to save/restore
the VESA registers and POST the card.

Question for the framebuffer experts: Is it possible to forbid access
to the video card after resume until the card has been POSTed and all
registers are restored? Any access to the card before that will freeze
the machine.

Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: [ACPI] Re: Samsung P35 and S3 suspend

[Carl-Daniel Hailfinger]

Carl-Daniel Hailfinger wrote:

> OK, I got S3 working with all kernels since 2.6.9 (well, your
> patches had to be modified slightly). Right now I'm running on the
> latest Linus -bk tree.
>
> I will now try other configurations and a full bootup.
>
> OK, it is working perfectly with the latest Linus -bk tree and
> everything configured in (SuSE .config, comparable to allmodconfig).

It turns out that (at least for 2.6.10-rc3 and later) the kernel
resumes from S3 perfectly regardless of .config as long as
- no framebuffer console is activated (kernel param video=vesa:off )
- pci-resume-2.6.10.patch and resume-finish-split-2.6.10.patch
  are applied
- suspend and resume happen with an active TEXT console (chvt 2)
- VESA registers are saved before suspend
- the radeon card is POSTed after resume
- the VESA registers are restored after that
- now you are free to change back to X if you want.

You do NOT need
- a patched X server
- a special kernel .config
- sacrifices of any kind.

See my other mail to acpi-devel for details about how to save/restore
the VESA registers and POST the card.

Question for the framebuffer experts: Is it possible to forbid access
to the video card after resume until the card has been POSTed and all
registers are restored? Any access to the card before that will freeze
the machine.

Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/

Re: Samsung P35 and S3 suspend

[Johan Vromans]

Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004-hi6Y0CQ0nG0@public.gmane.org> writes:

> - pci-resume-2.6.10.patch and resume-finish-split-2.6.10.patch
>   are applied

Excuse my ignorance, but where can I get these patches?

-- Johan


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Samsung P35 and S3 suspend

[Carl-Daniel Hailfinger]

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

Johan Vromans schrieb:
> Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004-hi6Y0CQ0nG0@public.gmane.org> writes:
> 
> 
>>- pci-resume-2.6.10.patch and resume-finish-split-2.6.10.patch
>>  are applied
> 
> 
> Excuse my ignorance, but where can I get these patches?

>From my local harddisk ;-)
Actually, you only need resume-finish-split-2.6.10.patch, the other
patch did not have any effect in my testing. Patch attached.

Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/

[-- Attachment #2: resume-finish-split-2.6.10.patch --]
[-- Type: text/plain, Size: 1864 bytes --]

--- linux-2.6.8-rc2/include/linux/pm.h	2004-08-04 20:36:48.044455680 +0200
+++ include/linux/pm.h	2004-08-04 19:50:07.000000000 +0200
@@ -208,6 +208,7 @@
 	suspend_disk_method_t pm_disk_mode;
 	int (*prepare)(suspend_state_t state);
 	int (*enter)(suspend_state_t state);
+	int (*leave)(suspend_state_t state);
 	int (*finish)(suspend_state_t state);
 };
 
--- linux-2.6.8-rc2/kernel/power/main.c	2004-08-04 20:36:17.755060368 +0200
+++ kernel/power/main.c	2004-08-04 19:52:26.000000000 +0200
@@ -104,6 +104,8 @@
 
 static void suspend_finish(suspend_state_t state)
 {
+	if (pm_ops && pm_ops->leave)
+		pm_ops->leave(state);
 	device_resume();
 	if (pm_ops && pm_ops->finish)
 		pm_ops->finish(state);
--- linux-2.6.8-rc2/drivers/acpi/sleep/main.c	2004-08-04 20:29:23.863981376 +0200
+++ drivers/acpi/sleep/main.c	2004-08-04 20:33:41.348837728 +0200
@@ -130,7 +130,23 @@
 	return ACPI_SUCCESS(status) ? 0 : -EFAULT;
 }
 
+/**
+ *	acpi_pm_leave - Make system ready to resume devices.
+ *	@pm_state:		State we're coming out of.
+ *
+ *	This is called after we wake back up and before device
+ *	resume methods are called.
+ */
+
+static int acpi_pm_leave(suspend_state_t pm_state)
+{
+	u32 acpi_state = acpi_suspend_states[pm_state];
 
+	acpi_leave_sleep_state(acpi_state);
+	acpi_disable_wakeup_device(acpi_state);
+	
+	return 0;
+}
 /**
  *	acpi_pm_finish - Finish up suspend sequence.
  *	@pm_state:		State we're coming out of.
@@ -143,9 +159,6 @@
 {
 	u32 acpi_state = acpi_suspend_states[pm_state];
 
-	acpi_leave_sleep_state(acpi_state);
-	acpi_disable_wakeup_device(acpi_state);
-
 	/* reset firmware waking vector */
 	acpi_set_firmware_waking_vector((acpi_physical_address) 0);
 
@@ -173,6 +186,7 @@
 static struct pm_ops acpi_pm_ops = {
 	.prepare	= acpi_pm_prepare,
 	.enter		= acpi_pm_enter,
+	.leave		= acpi_pm_leave,
 	.finish		= acpi_pm_finish,
 };
 

Re: Re: Samsung P35 and S3 suspend

[Pavel Machek]

Hi!

> >>- pci-resume-2.6.10.patch and resume-finish-split-2.6.10.patch
> >>  are applied
> > 
> > 
> > Excuse my ignorance, but where can I get these patches?
> 
> >From my local harddisk ;-)
> Actually, you only need resume-finish-split-2.6.10.patch, the other
> patch did not have any effect in my testing. Patch attached.

The patch actually looks good, are you going to submit it?
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Stefan Dösinger]

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


> > >>- pci-resume-2.6.10.patch and resume-finish-split-2.6.10.patch
> > >>  are applied
> > >
> > > Excuse my ignorance, but where can I get these patches?
> > >
> > >From my local harddisk ;-)
> >
> > Actually, you only need resume-finish-split-2.6.10.patch, the other
> > patch did not have any effect in my testing. Patch attached.
>
> The patch actually looks good, are you going to submit it?
>         Pavel

I think this is the patch I sent to this list a few months ago. Here the 
archive linksfor reference: 

http://sourceforge.net/mailarchive/message.php?msg_id=9091506

The background is that any write access to the pci config registers of some 
devices(sound card, usb 2.0 controler, and modem) cause a system lockup if 
they are called before acpi_leave_sleep_state and acpi_disable_wakeup_device 
were called. This is on an Acer Travelmate 803 Notebook, and it seems to be 
the same on other systems.

I sent the patch to the list, but it seems that nobody noticed it and I forgot 
to send it again. Here is an updated patch against 2.6.10. I can't promise 
that it doesn't break other systems. Someone should make sure that 
pm_ops->leave is set to NULL for apm. I haven't found this in the apm code 
yet.

Stefan Dösinger

[-- Attachment #2: resume-finish-split.patch --]
[-- Type: text/x-diff, Size: 1855 bytes --]

--- linux-2.6.10/include/linux/pm.h	2004-12-26 15:25:39.639998872 +0100
+++ include/linux/pm.h	2004-12-26 15:27:10.885127504 +0100
@@ -208,6 +208,7 @@
 	suspend_disk_method_t pm_disk_mode;
 	int (*prepare)(suspend_state_t state);
 	int (*enter)(suspend_state_t state);
+	int (*leave)(suspend_state_t state);
 	int (*finish)(suspend_state_t state);
 };
 
--- linux-2.6.10/kernel/power/main.c	2004-12-26 15:25:54.377758392 +0100
+++ kernel/power/main.c	2004-12-26 15:26:31.472119192 +0100
@@ -104,6 +104,8 @@
 
 static void suspend_finish(suspend_state_t state)
 {
+	if (pm_ops && pm_ops->leave)
+		pm_ops->leave(state);
 	device_resume();
 	if (pm_ops && pm_ops->finish)
 		pm_ops->finish(state);
--- linux-2.6.10/drivers/acpi/sleep/main.c	2004-12-26 15:25:20.314936728 +0100
+++ drivers/acpi/sleep/main.c	2004-12-26 15:28:49.253173288 +0100
@@ -130,7 +130,23 @@
 	return ACPI_SUCCESS(status) ? 0 : -EFAULT;
 }
 
+/**
+ *	acpi_pm_leave - Make system ready to resume devices.
+ *	@pm_state:		State we're coming out of.
+ *
+ *	This is called after we wake back up and before device
+ *	resume methods are called.
+ */
+
+static int acpi_pm_leave(suspend_state_t pm_state)
+{
+	u32 acpi_state = acpi_suspend_states[pm_state];
 
+	acpi_leave_sleep_state(acpi_state);
+	acpi_disable_wakeup_device(acpi_state);
+	
+	return 0;
+}
 /**
  *	acpi_pm_finish - Finish up suspend sequence.
  *	@pm_state:		State we're coming out of.
@@ -143,9 +159,6 @@
 {
 	u32 acpi_state = acpi_suspend_states[pm_state];
 
-	acpi_leave_sleep_state(acpi_state);
-	acpi_disable_wakeup_device(acpi_state);
-
 	/* reset firmware waking vector */
 	acpi_set_firmware_waking_vector((acpi_physical_address) 0);
 
@@ -173,6 +186,7 @@
 static struct pm_ops acpi_pm_ops = {
 	.prepare	= acpi_pm_prepare,
 	.enter		= acpi_pm_enter,
+	.leave		= acpi_pm_leave,
 	.finish		= acpi_pm_finish,
 };
 

PATCH: Call acpi_leave_sleep_state before resuming devices

[Stefan Dösinger]

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

Hello,

Here's again the resume-finish-split patch, this time CC-ed to Len.

This patch splits up acpi_pm_leave. It introduces acpi_pm_leave which calls 
acpi_leave_sleep_state and acpi_disable_wakeup_device before resuming the 
devices. This improves S3 resume on an Acer Travelmate 800 and on the Samsung 
P3 notebook.

Some archive references:
http://sourceforge.net/mailarchive/message.php?msg_id=9091506
http://sourceforge.net/mailarchive/message.php?msg_id=10315947

The background is that any write access to the pci config registers of some 
devices(sound card, usb 2.0 controler, and modem) cause a system lockup if 
they are called before acpi_leave_sleep_state and acpi_disable_wakeup_device 
were called. This is on an Acer Travelmate 803 Notebook, and it seems to be 
the same on other systems.

I sent the patch to the list, but it seems that nobody noticed it and I forgot 
to send it again. Here is an updated patch against 2.6.10. I can't promise 
that it doesn't break other systems. Someone should make sure that 
pm_ops->leave is set to NULL for apm. I haven't found this in the apm code 
yet.

Cheers,
Stefan Dösinger

[-- Attachment #2: resume-finish-split.patch --]
[-- Type: text/x-diff, Size: 1855 bytes --]

--- linux-2.6.10/include/linux/pm.h	2004-12-26 15:25:39.639998872 +0100
+++ include/linux/pm.h	2004-12-26 15:27:10.885127504 +0100
@@ -208,6 +208,7 @@
 	suspend_disk_method_t pm_disk_mode;
 	int (*prepare)(suspend_state_t state);
 	int (*enter)(suspend_state_t state);
+	int (*leave)(suspend_state_t state);
 	int (*finish)(suspend_state_t state);
 };
 
--- linux-2.6.10/kernel/power/main.c	2004-12-26 15:25:54.377758392 +0100
+++ kernel/power/main.c	2004-12-26 15:26:31.472119192 +0100
@@ -104,6 +104,8 @@
 
 static void suspend_finish(suspend_state_t state)
 {
+	if (pm_ops && pm_ops->leave)
+		pm_ops->leave(state);
 	device_resume();
 	if (pm_ops && pm_ops->finish)
 		pm_ops->finish(state);
--- linux-2.6.10/drivers/acpi/sleep/main.c	2004-12-26 15:25:20.314936728 +0100
+++ drivers/acpi/sleep/main.c	2004-12-26 15:28:49.253173288 +0100
@@ -130,7 +130,23 @@
 	return ACPI_SUCCESS(status) ? 0 : -EFAULT;
 }
 
+/**
+ *	acpi_pm_leave - Make system ready to resume devices.
+ *	@pm_state:		State we're coming out of.
+ *
+ *	This is called after we wake back up and before device
+ *	resume methods are called.
+ */
+
+static int acpi_pm_leave(suspend_state_t pm_state)
+{
+	u32 acpi_state = acpi_suspend_states[pm_state];
 
+	acpi_leave_sleep_state(acpi_state);
+	acpi_disable_wakeup_device(acpi_state);
+	
+	return 0;
+}
 /**
  *	acpi_pm_finish - Finish up suspend sequence.
  *	@pm_state:		State we're coming out of.
@@ -143,9 +159,6 @@
 {
 	u32 acpi_state = acpi_suspend_states[pm_state];
 
-	acpi_leave_sleep_state(acpi_state);
-	acpi_disable_wakeup_device(acpi_state);
-
 	/* reset firmware waking vector */
 	acpi_set_firmware_waking_vector((acpi_physical_address) 0);
 
@@ -173,6 +186,7 @@
 static struct pm_ops acpi_pm_ops = {
 	.prepare	= acpi_pm_prepare,
 	.enter		= acpi_pm_enter,
+	.leave		= acpi_pm_leave,
 	.finish		= acpi_pm_finish,
 };
 

RE: Re: Samsung P35 and S3 suspend

[Li, Shaohua]

>The background is that any write access to the pci config registers of
some
>devices(sound card, usb 2.0 controler, and modem) cause a system lockup
if
>they are called before acpi_leave_sleep_state and
>acpi_disable_wakeup_device
>were called. This is on an Acer Travelmate 803 Notebook, and it seems
to be
>the same on other systems.
>
>I sent the patch to the list, but it seems that nobody noticed it and I
>forgot
>to send it again. Here is an updated patch against 2.6.10. I can't
promise
>that it doesn't break other systems. Someone should make sure that
>pm_ops->leave is set to NULL for apm. I haven't found this in the apm
code
>yet.
This patch is quite interesting. If you just move '
acpi_leave_sleep_state(acpi_state)' to acpi_pm_leave, what's the result?
And please send me a copy of your acpidmp, I'd like look at it.

Thanks,
Shaohua


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Stefan Dösinger]

> This patch is quite interesting. If you just move '
> acpi_leave_sleep_state(acpi_state)' to acpi_pm_leave, what's the result?
> And please send me a copy of your acpidmp, I'd like look at it.
Works too with 2.6.10. Strange, AFAIK this didn't work with 2.6.7.
I sent the output of acpidump in a private mail(File fize)

stefan


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Li Shaohua]

On Mon, 2004-12-27 at 20:18, stefandoesinger-RbZlAiThDcE@public.gmane.org wrote:
> > This patch is quite interesting. If you just move '
> > acpi_leave_sleep_state(acpi_state)' to acpi_pm_leave, what's the
> result?
> > And please send me a copy of your acpidmp, I'd like look at it.
> Works too with 2.6.10. Strange, AFAIK this didn't work with 2.6.7.
> I sent the output of acpidump in a private mail(File fize)
Your original patch (move 'acpi_leave_sleep_state' and
'acpi_disable_wakeup_device' to 'acpi_pm_leave') seems safer (in case
resumed devices generate unexpected wakeup interrupts), please submit a
patch to Len.

Though I wonder if 'acpi_pm_leave' should be called before
'device_power_up' (ACPI spec said _WAK should be called before device
resume, which possibly includes system devices). There isn't a
straightforward fix for this, acpi_leave_sleep_state is designed being
called with interrupt enabled. But anyway, we can fix it till we
actually find one real bug.

Thanks,
Shaohua



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

RE: Re: Samsung P35 and S3 suspend

[Li, Shaohua]

>I think this is the patch I sent to this list a few months ago. Here
the
>archive linksfor reference:
>
>http://sourceforge.net/mailarchive/message.php?msg_id=9091506
>
>The background is that any write access to the pci config registers of
some
>devices(sound card, usb 2.0 controler, and modem) cause a system lockup
if
>they are called before acpi_leave_sleep_state and
>acpi_disable_wakeup_device
>were called. This is on an Acer Travelmate 803 Notebook, and it seems
to be
>the same on other systems.
>
>I sent the patch to the list, but it seems that nobody noticed it and I
>forgot
>to send it again. Here is an updated patch against 2.6.10. I can't
promise
>that it doesn't break other systems. Someone should make sure that
>pm_ops->leave is set to NULL for apm. I haven't found this in the apm
code
>yet.
>
And also please try this one (in kernel/power/main.c):
static void suspend_finish(suspend_state_t state)
{
-	device_resume();
	if (pm_ops && pm_ops->finish)
		pm_ops->finish(state);
+	device_resume();
	thaw_processes();
	pm_restore_console();
}
According to ACPI spec, device resume should be after _WAK method (in
acpi_leave_sleep_state)

Thanks,
Shaohua


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/

Re: Re: Samsung P35 and S3 suspend

[Stefan Dösinger]

> And also please try this one (in kernel/power/main.c):
> static void suspend_finish(suspend_state_t state)
> {
> - device_resume();
>  if (pm_ops && pm_ops->finish)
>   pm_ops->finish(state);
> + device_resume();
>  thaw_processes();
>  pm_restore_console();
> }
> According to ACPI spec, device resume should be after _WAK method (in
> acpi_leave_sleep_state)
This is the first thing I've done, it also works(See the archives), but 
Luca<kronos@pe...> told me that it's not correct:

>  Well, it may work but it"s not correct. ->finish is meant to be called
> to finalize the wakeup procedure *after* devices are waked up.
 
> ACPI finish calls acpi_leave_sleep_state() and restore the waking
> vectore. I"m not an ACPI guru but my guess is that what you need is
> in acpi_leave_sleep_state().
 
> If that"s the case we may want to split the finish callback (say
> prepare_wake and finish_wake).
This is what I did.

Stefan


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/