* Re: isochronous mode of USB audio device on MPC5200
From: Sylvain Munaut @ 2005-01-01 22:19 UTC (permalink / raw)
To: Benny Liu; +Cc: linuxppc-dev
In-Reply-To: <008c01c4f005$bc1e94c0$1100a8c0@BENNY>
Hi Benny
What version of the kernel ?
In the last 2.4 I built ( quite a while ago ... ) there was a flaw
in the handling of the hwPSW field in the OHCI driver when on big-endian
platform. Since this field is only used fot Isochronous the problem
didn't show up before.
The fields were assume by the kernel to be in this order
hwPSW[0]
hwPSW[1]
hwPSW[2]
hwPSW[3]
...
But in fact since the figure in ohci spec shows this array not as an
array of 16bits fields but as an array of 32bits integer, each containing
two hwPSW[] in little endian order, they ended up implemented in the order
hwPSW[1]
hwPSW[0]
hwPSW[3]
hwPSW[2]
...
(fscked up isn't it ? ;)
And that was not taken into account ...
I notified W.Denk about the problem a while ago, don't know if any
action has been taken.
Sylvain Munaut
Benny Liu wrote:
> Hi, everyone, happy new year!
> Did anyone try usb audio device or other isochronous mode usb devices
> on Icecube board(Motorola MPC5200)?
> I tried, but it reports the following message:
> /"host/usb-ohci.c: OHCI Unrecoverable Error, controller usb-0 disabled"/
> After this message, the host controller is disabled.
> Thanks a lot.
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Linuxppc-dev mailing list
>Linuxppc-dev@ozlabs.org
>https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
^ permalink raw reply
* Re: MPC5200 PCI byte-swapping
From: Sylvain Munaut @ 2005-01-01 22:39 UTC (permalink / raw)
To: Mark Chambers; +Cc: linuxppc-embedded
In-Reply-To: <061001c4eeaf$0b5e1860$0301a8c0@chuck2>
Mark Chambers wrote:
>I've just realized that the 5200 does byte-lane swapping
>on all PCI accesses. That is, if you write a 32 bit word
>0x12345678, 0x12 will go out on byte 0, 0x34 on byte 1,
>etc. Unfortunately, my target, a T.I. DM642, does not
>do this, so I've got a big/little endian mismatch. A couple
>of questions if anybody knows:
>
>- Do all MPC8xxx processors do this - byte swap on
>all PCI accesses, not just configuration space?
>
>- Is there an elegant (simple) way to re-swap the bytes?
>It's not a big problem really, but if there were a way to
>set LE mode on a particular page or something like that
>it might be worth it.
>
>
>
I'm not sure of what you mean but look at the mapping
aroung pdf page 337 of the user manual. It's not configurable
as far as I can see.
Sylvain
^ permalink raw reply
* Re: [FYI] linux 2.6 still not working with PReP (ppc32)
From: Sebastian Heutling @ 2005-01-01 23:56 UTC (permalink / raw)
To: Sven Luther; +Cc: linuxppc-dev, Marc Dietrich
In-Reply-To: <20041231222808.GB8078@pegasos>
On Fri, 2004-12-31 at 23:28 +0100, Sven Luther wrote:
> On Fri, Dec 31, 2004 at 04:00:49PM +0100, Sebastian Heutling wrote:
> > On Fri, 2004-12-31 at 10:55 +0100, Sven Luther wrote:
> > > On Mon, Dec 27, 2004 at 03:47:05AM +0100, Christian wrote:
> > > > Marc Dietrich schrieb:
> > > > >Hi all,
> > > > >
> > > > >I read this thread about booting a PowerStack with newer kernels.
> > > > >Motivated by this, I tried to compile a 2.6.10 kernel on my machine (with
> > > > >sym53c825a onboard). Sadly, the scsi controller always timeouts during
> > > > >initialisation. I
> > >
> > > I also have some strange issues with network support using the standard debian
> > > 2.6.8 kernel. ifconfig upping the decchip ethernet on the powerstack freezes
> > > the kernel, and i hear reports of problems on IBM PReP hardware too with not
> > > working ethernet, altough there is no freeze.
> > >
> > > Any idea on this ?
> >
> > Does it contain the IRQ patch? Where does it boot from SCSI or net? What
> > PCI-Devices are installed?
>
> Probably not, just the standard debian kernel, i donÃ't remember any irq
> patches, but there where a bunch of patches from leighbb. it is done
The patch is the one that is included in 2.6.10 which is mentioned above
and this thread already has somewhere in the beginning. I attached it
below.
I haven't had the time yet to test the 2.6.10 kernel. Maybe there is
another problem now ...
> netbooting, and the only pci device installed is the cirruss logic graphic
> card.
If you use the standard debian kernel - ok, it doesn't work because of
wrong IRQs on the PowerstackII (Utah).
BTW: The onboard Winbond IDE chip works as well although no connector is
provided. You only need a little bit of soldering and adjusting the IRQ
of Slot 1 from 0 to 4. :-)
Sebastian Heutling
--
diff -puN
arch/ppc/platforms/prep_pci.c~ppc32-fix-motorola-prep-powerstackii-utah-pci-irq-map arch/ppc/platforms/prep_pci.c
---
25/arch/ppc/platforms/prep_pci.c~ppc32-fix-motorola-prep-powerstackii-utah-pci-irq-map 2004-12-07 01:01:16.000000000 -0800
+++ 25-akpm/arch/ppc/platforms/prep_pci.c 2004-12-07
01:01:16.000000000 -0800
@@ -49,10 +49,10 @@ static char Utah_pci_IRQ_map[23] __prepd
0, /* Slot 1 - unused */
5, /* Slot 2 - SCSI - NCR825A */
0, /* Slot 3 - unused */
- 1, /* Slot 4 - Ethernet - DEC2114x */
+ 3, /* Slot 4 - Ethernet - DEC2114x */
0, /* Slot 5 - unused */
- 3, /* Slot 6 - PCI Card slot #1 */
- 4, /* Slot 7 - PCI Card slot #2 */
+ 2, /* Slot 6 - PCI Card slot #1 */
+ 3, /* Slot 7 - PCI Card slot #2 */
5, /* Slot 8 - PCI Card slot #3 */
5, /* Slot 9 - PCI Bridge */
/* added here in case we ever support PCI bridges */
^ permalink raw reply
* Re: [FYI] linux 2.6 still not working with PReP (ppc32)
From: Sebastian Heutling @ 2005-01-02 0:31 UTC (permalink / raw)
To: Marc Dietrich; +Cc: linuxppc-dev
In-Reply-To: <200412272237.57241.marc.dietrich@ap.physik.uni-giessen.de>
[-- Attachment #1: Type: text/plain, Size: 4438 bytes --]
Hi Marc,
On Mon, 2004-12-27 at 22:37 +0100, Marc Dietrich wrote:
> Hallo Christian,
>
> Am Montag, 27. Dezember 2004 03:47 schrieben Sie:
> > Marc Dietrich schrieb:
> >
> > > I also tried to change the irq routings in prep_pci.c like in the latest
> > > patch with the sym53c8xx_2 driver,
> > > Slot 12 -> IRQ 15 (sym53c825)
> > > Slot 15 -> IRQ 11 (dec 21140)
> > > but this didn't helped.
> >
> > i'm still working these out too, gotta find some time...
>
> maybe this helps:
>
> I used the config file you sent me (and added serial console).
>
> when booting a working 2.4.24-pre1 I get:
>
> [...]
> PCI: Probing PCI hardware
> Setting PCI interrupts for a "Utah (Powerstack II Pro4000)"
> PCI: moved device 00:0b.1 resource 4 (101) to 1480
> PCI: moved device 00:0b.1 resource 5 (101) to 1490
> PCI: moved device 00:11.0 resource 0 (1208) to 0
> [...]
> SCSI subsystem driver Revision: 1.00
> new devtbl [4096] @c049e000.
> PCI: Enabling device 00:0c.0 (0000 -> 0003)
> sym53c8xx: at PCI bus 0, device 12, function 0
> sym53c8xx: setting PCI_COMMAND_MASTER PCI_COMMAND_PARITY...(fix-up)
> sym53c8xx: changing PCI_LATENCY_TIMER from 0 to 80.
> sym53c8xx: 53c825a detected
> sym53c825a-0: rev 0x13 on pci bus 0 device 12 function 0 irq 15
> new MPOOL [ 188] @c049f000.
> new VTOB [ 12] @c049f100.
> new NCB [2408] @c049c000.
> new SQUEUE [2336] @c049d000.
> new VTOB [ 12] @c049f110.
> new DQUEUE [2336] @c049a000.
> new TARGTBL [ 256] @c049b000.
> new VTOB [ 12] @c049f120.
> new SCRIPT [3504] @c0498000.
> new SCRIPTH [1504] @c049b800.
> new CCB [1300] @c0499000.
> sym53c825a-0: ID 7, Fast-10, Parity Checking
>
>
> while booting a non working 2.6.10 I get:
>
> I already changed the irq of slot 12 to 15 and slot 14 to irq 11.
You don't really need to change any IRQ above slot 9 on a 2.6.? kernel
because the slot is 2 (while it was on 12 in 2.4 kernels).
>
> [...]
> PCI: Probing PCI hardware
> Setting PCI interrupts for a "Utah (Powerstack II Pro4000)"
> PCI: Cannot allocate resource region 5 of device 0000:00:01.1
This is the IDE chip which gets IRQ 0 and therefore results in an error.
Try changing the value of Slot 1 from 0 to 4 (which is IRQ 14). I don't
really think it changes the SCSI timeouts maybe it helps - no one knows
for sure ;).
> SCSI subsystem initialized
> [...]
> PCI: Enabling device 0000:00:02.0 (0000 -> 0003)
> sym0: <825a> rev 0x13 at pci 0000:00:02.0 irq 15
> new MPOOL [ 180] @c7d99000.
> new VTOB [ 12] @c7d99100.
> new HCB [1784] @c7d9a000.
> sym0: No NVRAM, ID 7, Fast-10, SE, parity checking
> new VTOB [ 12] @c7d99110.
> new SQUEUE [3600] @c7d9b000.
> new VTOB [ 12] @c7d99120.
> new DQUEUE [3600] @c7d9c000.
> new TARGTBL [ 256] @c7d9a800.
> new VTOB [ 12] @c7d99130.
> new SCRIPTA0 [3024] @c7d9d000.
> new VTOB [ 12] @c7d99140.
> new SCRIPTB0 [1324] @c7d9e000.
> new SCRIPTZ0 [ 32] @c7d9a900.
> new CCBH [1024] @c7d99400.
> new CCB [ 988] @c7d9ac00.
> new SNS_BBUF [ 32] @c7d9a920.
> [...]
> new BADLUNTBL [ 256] @c7d9aa00.
> sym0: SCSI BUS has been reset.
> scsi0 : sym-2.1.18m
> elevator: using anticipatory as default io scheduler
> sym0:0:0:ccb @c7d9ac00 using tag 256.
> sym0: queuepos=2.
> sym0:0:0: ABORT operation started.
> sym0:0:0: ABORT operation timed-out.
> sym0:0:0: DEVICE RESET operation started.
> sym0:0:0: DEVICE RESET operation timed-out.
> sym0:0:0: BUS RESET operation started.
> sym0:0:0: BUS RESET operation timed-out.
> sym0:0:0: HOST RESET operation started.
> sym0:0:0:ccb @c7d9ac00 freeing tag 256.
> sym0: SCSI BUS has been reset.
> [ hangs here ]
Hmmm strange ... is there anything attached on scsi?
> Indeed, there seems to be something wrong with the pci resources - but I can't
> say what. I attached the compete boot logs. I also attached the lspci -v
> output.
... wait a second ... looking at the lspci output ... you use a USB PCI
card? The IRQ-sharing doesn't work well and the USB PCI card is on the
same slot as the SCSI controller resulting in both using the same IRQ.
Remove the USB card and check wether it changes anything. If it does
work now: Did it ever work with USB using another kernel? If so maybe
there is something else wrong, if not it's a HW Problem.
I also attached a config file from my powerstack (which I use as a
router and runs a 2.6 kernel since june last year or so)
Sebastian Heutling
[-- Attachment #2: config-powerstack --]
[-- Type: text/plain, Size: 27391 bytes --]
#
# Automatically generated make config: don't edit
#
CONFIG_MMU=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_HAVE_DEC_LOCK=y
CONFIG_PPC=y
CONFIG_PPC32=y
CONFIG_GENERIC_NVRAM=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
# CONFIG_CLEAN_COMPILE is not set
CONFIG_BROKEN=y
CONFIG_BROKEN_ON_SMP=y
#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT 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
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y
#
# Processor
#
CONFIG_6xx=y
# CONFIG_40x is not set
# CONFIG_44x is not set
# CONFIG_POWER3 is not set
# CONFIG_POWER4 is not set
# CONFIG_8xx is not set
# CONFIG_E500 is not set
# CONFIG_ALTIVEC is not set
# CONFIG_TAU is not set
# CONFIG_CPU_FREQ is not set
# CONFIG_PPC601_SYNC_FIX is not set
CONFIG_PPC_STD_MMU=y
#
# Platform options
#
CONFIG_PPC_MULTIPLATFORM=y
# CONFIG_APUS is not set
# CONFIG_WILLOW is not set
# CONFIG_PCORE is not set
# CONFIG_POWERPMC250 is not set
# CONFIG_EV64260 is not set
# CONFIG_SPRUCE is not set
# CONFIG_LOPEC is not set
# CONFIG_MCPN765 is not set
# CONFIG_MVME5100 is not set
# CONFIG_PPLUS is not set
# CONFIG_PRPMC750 is not set
# CONFIG_PRPMC800 is not set
# CONFIG_SANDPOINT is not set
# CONFIG_ADIR is not set
# CONFIG_K2 is not set
# CONFIG_PAL4 is not set
# CONFIG_GEMINI is not set
# CONFIG_EST8260 is not set
# CONFIG_SBC82xx is not set
# CONFIG_SBS8260 is not set
# CONFIG_RPX8260 is not set
# CONFIG_TQM8260 is not set
# CONFIG_ADS8272 is not set
# CONFIG_LITE5200 is not set
CONFIG_PPC_CHRP=y
CONFIG_PPC_PMAC=y
CONFIG_PPC_PREP=y
CONFIG_PPC_OF=y
CONFIG_PPCBUG_NVRAM=y
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
# CONFIG_HIGHMEM is not set
CONFIG_KERNEL_ELF=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m
CONFIG_PROC_DEVICETREE=y
CONFIG_PREP_RESIDUAL=y
CONFIG_PROC_PREPRESIDUAL=y
CONFIG_CMDLINE_BOOL=y
CONFIG_CMDLINE="root=/dev/sda2 console=ttyS0"
#
# Bus options
#
CONFIG_ISA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_PCI=y
CONFIG_PCI_DOMAINS=y
# CONFIG_PCI_LEGACY_PROC is not set
CONFIG_PCI_NAMES=y
#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
CONFIG_PCMCIA_PROBE=y
#
# Advanced setup
#
CONFIG_ADVANCED_OPTIONS=y
CONFIG_HIGHMEM_START=0xfe000000
# CONFIG_LOWMEM_SIZE_BOOL is not set
CONFIG_LOWMEM_SIZE=0x30000000
# CONFIG_KERNEL_START_BOOL is not set
CONFIG_KERNEL_START=0xc0000000
# CONFIG_TASK_SIZE_BOOL is not set
CONFIG_TASK_SIZE=0x80000000
CONFIG_BOOT_LOAD=0x00800000
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_STANDALONE=y
# CONFIG_PREVENT_FIRMWARE_BUILD is not set
# CONFIG_FW_LOADER is not set
# CONFIG_DEBUG_DRIVER is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_CML1=m
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO 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=y
#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# CONFIG_MAC_FLOPPY is not set
# 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 is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
# CONFIG_LBD is not set
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_IDE_TASKFILE_IO is not set
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
CONFIG_BLK_DEV_SL82C105=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX 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 is not set
# CONFIG_BLK_DEV_NS87415 is not set
CONFIG_BLK_DEV_PDC202XX_OLD=m
# CONFIG_PDC202XX_BURST is not set
CONFIG_BLK_DEV_PDC202XX_NEW=m
# CONFIG_PDC202XX_FORCE is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE 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_BLK_DEV_IDE_PMAC 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=y
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
CONFIG_SCSI_CONSTANTS=y
# 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_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS 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_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
CONFIG_SCSI_SYM53C8XX_2=y
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=0
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
# CONFIG_SCSI_SYM53C8XX_IOMAPPED is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I 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_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_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_MESH is not set
# CONFIG_SCSI_MAC53C94 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 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Macintosh device drivers
#
# CONFIG_ADB is not set
# CONFIG_ADB_CUDA is not set
# CONFIG_ADB_PMU is not set
# CONFIG_MAC_SERIAL is not set
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_FWMARK=y
CONFIG_IP_ROUTE_NAT=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_TOS=y
# CONFIG_IP_ROUTE_VERBOSE is not set
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
#
# 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=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
# CONFIG_IP_NF_TFTP is not set
# CONFIG_IP_NF_AMANDA is not set
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
# CONFIG_IP_NF_MATCH_IPRANGE is not set
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
# CONFIG_IP_NF_MATCH_RECENT is not set
CONFIG_IP_NF_MATCH_ECN=m
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=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
# CONFIG_IP_NF_TARGET_NETMAP is not set
# CONFIG_IP_NF_TARGET_SAME is not set
# 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_MANGLE=m
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 is not set
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
# CONFIG_IP_NF_ARP_MANGLE is not set
# CONFIG_IP_NF_COMPAT_IPCHAINS is not set
# CONFIG_IP_NF_COMPAT_IPFWADM is not set
# CONFIG_IP_NF_RAW is not set
# CONFIG_IP_NF_MATCH_ADDRTYPE is not set
# CONFIG_IP_NF_MATCH_REALM is not set
#
# 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_LLC=m
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
CONFIG_ATALK=m
# CONFIG_DEV_APPLETALK 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=y
CONFIG_NET_SCH_CLK_JIFFIES=y
# CONFIG_NET_SCH_CLK_GETTIMEOFDAY is not set
# CONFIG_NET_SCH_CLK_CPU is not set
# CONFIG_NET_SCH_CBQ is not set
# CONFIG_NET_SCH_HTB is not set
# CONFIG_NET_SCH_HFSC is not set
# CONFIG_NET_SCH_PRIO is not set
# CONFIG_NET_SCH_RED is not set
# CONFIG_NET_SCH_SFQ is not set
# CONFIG_NET_SCH_TEQL is not set
# CONFIG_NET_SCH_TBF is not set
# CONFIG_NET_SCH_GRED is not set
# CONFIG_NET_SCH_DSMARK is not set
# CONFIG_NET_SCH_NETEM is not set
# CONFIG_NET_SCH_INGRESS is not set
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
# CONFIG_NET_CLS is not set
# CONFIG_NET_CLS_ROUTE is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
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=m
# CONFIG_MACE is not set
# CONFIG_BMAC is not set
# CONFIG_OAKNET is not set
# 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=y
CONFIG_DE2104X=m
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_TULIP_NAPI is not set
# CONFIG_DE4X5 is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_DM9102 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_EEPRO100=m
# CONFIG_EEPRO100_PIO is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
CONFIG_NE2K_PCI=m
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
CONFIG_EPIC100=m
# 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_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
# CONFIG_MV64340_ETH 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 is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
CONFIG_PPP=m
# CONFIG_PPP_MULTILINK is not set
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 is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# 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_MOUSEDEV_PSAUX_ENABLE=y
# 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 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 is not set
#
# 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_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_PMACZILOG is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
# CONFIG_PRINTER is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set
# CONFIG_QIC02_TAPE is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_NVRAM=y
CONFIG_GEN_RTC=m
CONFIG_GEN_RTC_X=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_RAW_DRIVER is not set
#
# I2C support
#
# CONFIG_I2C is not set
#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set
#
# Misc devices
#
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
CONFIG_FB=y
CONFIG_FB_CIRRUS=y
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_OF is not set
# CONFIG_FB_CONTROL is not set
# CONFIG_FB_PLATINUM is not set
# CONFIG_FB_VALKYRIE is not set
# CONFIG_FB_CT65550 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_S3TRIO is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_RIVA is not set
CONFIG_FB_MATROX=y
CONFIG_FB_MATROX_MILLENIUM=y
# CONFIG_FB_MATROX_MYSTIQUE is not set
# CONFIG_FB_MATROX_G450 is not set
# CONFIG_FB_MATROX_G100A is not set
# CONFIG_FB_MATROX_MULTIHEAD is not set
# CONFIG_FB_RADEON_OLD is not set
# CONFIG_FB_RADEON is not set
# 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_PM3 is not set
# CONFIG_FB_VIRTUAL is not set
#
# Console display driver support
#
# CONFIG_VGA_CONSOLE is not set
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
#
# Sound
#
CONFIG_SOUND=m
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
# CONFIG_SND_SEQUENCER_OSS is not set
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
#
# Generic devices
#
CONFIG_SND_MPU401_UART=m
CONFIG_SND_OPL3_LIB=m
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
CONFIG_SND_SERIAL_U16550=m
CONFIG_SND_MPU401=m
#
# ISA devices
#
# CONFIG_SND_AD1816A is not set
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_CS4231 is not set
CONFIG_SND_CS4232=m
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_ES968 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_ALS100 is not set
# CONFIG_SND_AZT2320 is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_DT019X 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=m
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP 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=m
# 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 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set
#
# ALSA PowerMac devices
#
#
# ALSA PowerMac requires I2C
#
#
# Open Sound System
#
CONFIG_SOUND_PRIME=m
# CONFIG_SOUND_BT878 is not set
# CONFIG_SOUND_CMPCI is not set
# CONFIG_SOUND_EMU10K1 is not set
# CONFIG_SOUND_FUSION is not set
# CONFIG_SOUND_CS4281 is not set
# CONFIG_SOUND_ES1370 is not set
# CONFIG_SOUND_ES1371 is not set
# CONFIG_SOUND_ESSSOLO1 is not set
# CONFIG_SOUND_MAESTRO is not set
# CONFIG_SOUND_MAESTRO3 is not set
# CONFIG_SOUND_ICH is not set
# CONFIG_SOUND_SONICVIBES is not set
# CONFIG_SOUND_TRIDENT is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
# CONFIG_SOUND_VIA82CXXX is not set
CONFIG_SOUND_OSS=m
# CONFIG_SOUND_TRACEINIT is not set
# CONFIG_SOUND_DMAP is not set
# CONFIG_SOUND_AD1816 is not set
# CONFIG_SOUND_AD1889 is not set
# CONFIG_SOUND_SGALAXY is not set
# CONFIG_SOUND_ADLIB is not set
# CONFIG_SOUND_ACI_MIXER is not set
CONFIG_SOUND_CS4232=m
# CONFIG_SOUND_SSCAPE is not set
# CONFIG_SOUND_GUS is not set
# CONFIG_SOUND_VMIDI is not set
# CONFIG_SOUND_TRIX is not set
# CONFIG_SOUND_MSS is not set
# CONFIG_SOUND_MPU401 is not set
# CONFIG_SOUND_NM256 is not set
# CONFIG_SOUND_MAD16 is not set
# CONFIG_SOUND_PAS is not set
# CONFIG_SOUND_PSS is not set
# CONFIG_SOUND_SB is not set
# CONFIG_SOUND_AWE32_SYNTH is not set
# CONFIG_SOUND_WAVEFRONT is not set
# CONFIG_SOUND_MAUI is not set
# CONFIG_SOUND_YM3812 is not set
# CONFIG_SOUND_OPL3SA1 is not set
# CONFIG_SOUND_OPL3SA2 is not set
# CONFIG_SOUND_YMFPCI is not set
# CONFIG_SOUND_UART6850 is not set
# CONFIG_SOUND_AEDSP16 is not set
# CONFIG_SOUND_ALI5455 is not set
# CONFIG_SOUND_FORTE is not set
# CONFIG_SOUND_RME96XX is not set
# CONFIG_SOUND_AD1980 is not set
#
# USB support
#
# CONFIG_USB 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 is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
CONFIG_ROMFS_FS=y
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_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_ASFS_FS is not set
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
# 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=m
# CONFIG_UFS_FS_WRITE is not set
#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V4 is not set
# CONFIG_NFSD_TCP is not set
# CONFIG_ROOT_NFS is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_SUNRPC=y
# CONFIG_RPCSEC_GSS_KRB5 is not set
CONFIG_SMB_FS=m
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="iso8859-15"
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
CONFIG_CODA_FS=m
# CONFIG_CODA_FS_OLD_API 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=y
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 is not set
# 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=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=m
# 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=m
# 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=m
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
#
# Library routines
#
CONFIG_CRC_CCITT=m
CONFIG_CRC32=m
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
#
# Profiling support
#
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SLAB is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_KGDB is not set
CONFIG_XMON=y
# CONFIG_BDI_SWITCH is not set
# CONFIG_DEBUG_INFO is not set
CONFIG_BOOTX_TEXT=y
#
# Security options
#
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
^ permalink raw reply
* Re: 43p-140 install issues
From: Mike Martin @ 2005-01-02 1:15 UTC (permalink / raw)
To: Sven Luther; +Cc: Ulrich Teichert, linuxppc-dev, debian-powerpc
In-Reply-To: <20050101165758.GA18559@pegasos>
I can boot with this image:
http://debian.yorku.ca/debian/dists/testing/main/installer-powerpc/current/images/powerpc/netboot/vmlinuz-prep.initrd
And things seems to go very well. Network configures, hard drives
partition, it dies at "Install the base system" with "The debootstrap
program exited with an error (return value 255)." It instructs me to
check /var/log/messages which now contains: "execv: No such file or
directory"
The previous step, partitioning, added:
"No matching physical volumes found
No volume groups found
Reading all physical volumes. This may take a while..."
Anyone?
MikeMartin
On Sat, 1 Jan 2005 17:57:58 +0100, Sven Luther <sven.luther@wanadoo.fr> wrote:
> On Sat, Jan 01, 2005 at 05:30:25PM +0100, Ulrich Teichert wrote:
> > Hi,
> >
> > [del]
> > >I would prefer that we fix the debian kernels for them to work correctly
> > >though. More on this on monday.
> >
> > I failed to configure a stock 2.4.28 kernel to detect the SCSI controler.
> > I think some of Leigh patches for this must be applied, but I haven't
> > gone any further.
>
> I had some report on a power3 box, that only the SMP sym53c8xx driver worked.
> When configuring in UP mode,
>
> > [del]
> > >Do the debian 2.4.27 kernel work on it ? I was unable to boot the 2.4.27 d-i
> > >kernel on my powerstack, but this is a different machine, so the issues may be
> > >a bit different.
> >
> > I've only tried the Woody PREP kernel, which failed in a way which I can't
> > remember, but I'll give it a try.
>
> Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel too.
> Let' try to get this fixed before the sarge release, which is not so far off
> now.
>
> Friendly,
>
> Sven Luther
>
>
^ permalink raw reply
* Re: isochronous mode of USB audio device on MPC5200
From: Benny Liu @ 2005-01-02 4:20 UTC (permalink / raw)
To: Sylvain Munaut; +Cc: linuxppc-dev
In-Reply-To: <41D721E1.8000007@246tNt.com>
SGkgU3lsdmFpbiwNCg0KICAgIFlvdSBhcmUgcmlnaHQuDQoNCiAgICBJIGFtIHVzaW5nIHRoZSBs
YXN0ZWQga2VybmVsIHNvdXJjZSBmcm9tIERlbnggd2ViIHNpdGUsIGtlcm5lbCB2ZXJzaW9uIGlz
IDIuNC4yNSwgYnV0IHRoZSB0ZCBkZWZpbml0aW9uIGluIHVzYi1vaGNpLmggaXMgc3RpbGwgd3Jv
bmcuIEkgbW9kaWZpZWQgdGhlIGh3UFNXIGRlZmluaXRpb24sIG5vdyB0aGUgaXNvY2hyb25vdXMg
bW9kZSBpcyBvay4NCg0KICAgIFRoYW5rIHlvdSB2ZXJ5IG11Y2guDQoNCkJlc3QgUmVnYXJkcywN
CkJlbm55DQoNCg0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206ICJTeWx2YWlu
IE11bmF1dCIgPHRudEAyNDZ0TnQuY29tPg0KVG86ICJCZW5ueSBMaXUiIDxiZW5ueUBjZWxsdmlz
aW9uLmNvbS5jbj4NCkNjOiA8bGludXhwcGMtZGV2QG96bGFicy5vcmc+DQpTZW50OiBTdW5kYXks
IEphbnVhcnkgMDIsIDIwMDUgNjoxOSBBTQ0KU3ViamVjdDogUmU6IGlzb2Nocm9ub3VzIG1vZGUg
b2YgVVNCIGF1ZGlvIGRldmljZSBvbiBNUEM1MjAwDQoNCg0KPiBIaSBCZW5ueQ0KPiANCj4gDQo+
IFdoYXQgdmVyc2lvbiBvZiB0aGUga2VybmVsID8NCj4gDQo+IA0KPiBJbiB0aGUgbGFzdCAyLjQg
SSBidWlsdCAoIHF1aXRlIGEgd2hpbGUgYWdvIC4uLiApIHRoZXJlIHdhcyBhIGZsYXcNCj4gaW4g
dGhlIGhhbmRsaW5nIG9mIHRoZSBod1BTVyBmaWVsZCBpbiB0aGUgT0hDSSBkcml2ZXIgd2hlbiBv
biBiaWctZW5kaWFuDQo+IHBsYXRmb3JtLiBTaW5jZSB0aGlzIGZpZWxkIGlzIG9ubHkgdXNlZCBm
b3QgSXNvY2hyb25vdXMgdGhlIHByb2JsZW0NCj4gZGlkbid0IHNob3cgdXAgYmVmb3JlLg0KPiAN
Cj4gVGhlIGZpZWxkcyB3ZXJlIGFzc3VtZSBieSB0aGUga2VybmVsIHRvIGJlIGluIHRoaXMgb3Jk
ZXINCj4gDQo+IGh3UFNXWzBdDQo+IGh3UFNXWzFdDQo+IGh3UFNXWzJdDQo+IGh3UFNXWzNdDQo+
IC4uLg0KPiANCj4gQnV0IGluIGZhY3Qgc2luY2UgdGhlIGZpZ3VyZSBpbiBvaGNpIHNwZWMgc2hv
d3MgdGhpcyBhcnJheSBub3QgYXMgYW4NCj4gYXJyYXkgb2YgMTZiaXRzIGZpZWxkcyBidXQgYXMg
YW4gYXJyYXkgb2YgMzJiaXRzIGludGVnZXIsIGVhY2ggY29udGFpbmluZw0KPiB0d28gaHdQU1db
XSBpbiBsaXR0bGUgZW5kaWFuIG9yZGVyLCB0aGV5IGVuZGVkIHVwIGltcGxlbWVudGVkIGluIHRo
ZSBvcmRlcg0KPiANCj4gaHdQU1dbMV0NCj4gaHdQU1dbMF0NCj4gaHdQU1dbM10NCj4gaHdQU1db
Ml0NCj4gLi4uDQo+IA0KPiAoZnNja2VkIHVwIGlzbid0IGl0ID8gOykNCj4gDQo+IA0KPiBBbmQg
dGhhdCB3YXMgbm90IHRha2VuIGludG8gYWNjb3VudCAuLi4NCj4gDQo+IA0KPiBJIG5vdGlmaWVk
IFcuRGVuayBhYm91dCB0aGUgcHJvYmxlbSBhIHdoaWxlIGFnbywgZG9uJ3Qga25vdyBpZiBhbnkN
Cj4gYWN0aW9uIGhhcyBiZWVuIHRha2VuLg0KPiANCj4gDQo+IA0KPiANCj4gU3lsdmFpbiBNdW5h
dXQNCj4gDQo+IA0KPiBCZW5ueSBMaXUgd3JvdGU6DQo+IA0KPj4gSGksIGV2ZXJ5b25lLCBoYXBw
eSBuZXcgeWVhciENCj4+IERpZCBhbnlvbmUgdHJ5IHVzYiBhdWRpbyBkZXZpY2Ugb3Igb3RoZXIg
aXNvY2hyb25vdXMgbW9kZSB1c2IgZGV2aWNlcw0KPj4gb24gSWNlY3ViZSBib2FyZChNb3Rvcm9s
YSBNUEM1MjAwKT8NCj4+IEkgdHJpZWQsIGJ1dCBpdCByZXBvcnRzIHRoZSBmb2xsb3dpbmcgbWVz
c2FnZToNCj4+IC8iaG9zdC91c2Itb2hjaS5jOiBPSENJIFVucmVjb3ZlcmFibGUgRXJyb3IsIGNv
bnRyb2xsZXIgdXNiLTAgZGlzYWJsZWQiLw0KPj4gQWZ0ZXIgdGhpcyBtZXNzYWdlLCB0aGUgaG9z
dCBjb250cm9sbGVyIGlzIGRpc2FibGVkLg0KPj4gVGhhbmtzIGEgbG90Lg0KPj4NCj4+LS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tDQo+Pg0KPj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KPj5MaW51eHBwYy1kZXYgbWFpbGluZyBsaXN0DQo+PkxpbnV4cHBjLWRldkBvemxh
YnMub3JnDQo+Pmh0dHBzOi8vb3psYWJzLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2xpbnV4cHBjLWRl
dg0KPj4NCj4gDQo+
^ permalink raw reply
* Re: isochronous mode of USB audio device on MPC5200
From: Benny Liu @ 2005-01-02 4:21 UTC (permalink / raw)
To: Sylvain Munaut; +Cc: linuxppc-dev
In-Reply-To: <41D721E1.8000007@246tNt.com>
SGkgU3lsdmFpbiwNCg0KICAgIFlvdSBhcmUgcmlnaHQuDQoNCiAgICBJIGFtIHVzaW5nIHRoZSBs
YXN0ZWQga2VybmVsIHNvdXJjZSBmcm9tIERlbnggd2ViIHNpdGUsIGtlcm5lbCB2ZXJzaW9uIGlz
IDIuNC4yNSwgYnV0IHRoZSB0ZCBkZWZpbml0aW9uIGluIHVzYi1vaGNpLmggaXMgc3RpbGwgd3Jv
bmcuIEkgbW9kaWZpZWQgdGhlIGh3UFNXIGRlZmluaXRpb24sIG5vdyB0aGUgaXNvY2hyb25vdXMg
bW9kZSBpcyBvay4NCg0KICAgIFRoYW5rIHlvdSB2ZXJ5IG11Y2guDQoNCkJlc3QgUmVnYXJkcywN
CkJlbm55DQoNCg0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206ICJTeWx2YWlu
IE11bmF1dCIgPHRudEAyNDZ0TnQuY29tPg0KVG86ICJCZW5ueSBMaXUiIDxiZW5ueUBjZWxsdmlz
aW9uLmNvbS5jbj4NCkNjOiA8bGludXhwcGMtZGV2QG96bGFicy5vcmc+DQpTZW50OiBTdW5kYXks
IEphbnVhcnkgMDIsIDIwMDUgNjoxOSBBTQ0KU3ViamVjdDogUmU6IGlzb2Nocm9ub3VzIG1vZGUg
b2YgVVNCIGF1ZGlvIGRldmljZSBvbiBNUEM1MjAwDQoNCg0KPiBIaSBCZW5ueQ0KPiANCj4gDQo+
IFdoYXQgdmVyc2lvbiBvZiB0aGUga2VybmVsID8NCj4gDQo+IA0KPiBJbiB0aGUgbGFzdCAyLjQg
SSBidWlsdCAoIHF1aXRlIGEgd2hpbGUgYWdvIC4uLiApIHRoZXJlIHdhcyBhIGZsYXcNCj4gaW4g
dGhlIGhhbmRsaW5nIG9mIHRoZSBod1BTVyBmaWVsZCBpbiB0aGUgT0hDSSBkcml2ZXIgd2hlbiBv
biBiaWctZW5kaWFuDQo+IHBsYXRmb3JtLiBTaW5jZSB0aGlzIGZpZWxkIGlzIG9ubHkgdXNlZCBm
b3QgSXNvY2hyb25vdXMgdGhlIHByb2JsZW0NCj4gZGlkbid0IHNob3cgdXAgYmVmb3JlLg0KPiAN
Cj4gVGhlIGZpZWxkcyB3ZXJlIGFzc3VtZSBieSB0aGUga2VybmVsIHRvIGJlIGluIHRoaXMgb3Jk
ZXINCj4gDQo+IGh3UFNXWzBdDQo+IGh3UFNXWzFdDQo+IGh3UFNXWzJdDQo+IGh3UFNXWzNdDQo+
IC4uLg0KPiANCj4gQnV0IGluIGZhY3Qgc2luY2UgdGhlIGZpZ3VyZSBpbiBvaGNpIHNwZWMgc2hv
d3MgdGhpcyBhcnJheSBub3QgYXMgYW4NCj4gYXJyYXkgb2YgMTZiaXRzIGZpZWxkcyBidXQgYXMg
YW4gYXJyYXkgb2YgMzJiaXRzIGludGVnZXIsIGVhY2ggY29udGFpbmluZw0KPiB0d28gaHdQU1db
XSBpbiBsaXR0bGUgZW5kaWFuIG9yZGVyLCB0aGV5IGVuZGVkIHVwIGltcGxlbWVudGVkIGluIHRo
ZSBvcmRlcg0KPiANCj4gaHdQU1dbMV0NCj4gaHdQU1dbMF0NCj4gaHdQU1dbM10NCj4gaHdQU1db
Ml0NCj4gLi4uDQo+IA0KPiAoZnNja2VkIHVwIGlzbid0IGl0ID8gOykNCj4gDQo+IA0KPiBBbmQg
dGhhdCB3YXMgbm90IHRha2VuIGludG8gYWNjb3VudCAuLi4NCj4gDQo+IA0KPiBJIG5vdGlmaWVk
IFcuRGVuayBhYm91dCB0aGUgcHJvYmxlbSBhIHdoaWxlIGFnbywgZG9uJ3Qga25vdyBpZiBhbnkN
Cj4gYWN0aW9uIGhhcyBiZWVuIHRha2VuLg0KPiANCj4gDQo+IA0KPiANCj4gU3lsdmFpbiBNdW5h
dXQNCj4gDQo+IA0KPiBCZW5ueSBMaXUgd3JvdGU6DQo+IA0KPj4gSGksIGV2ZXJ5b25lLCBoYXBw
eSBuZXcgeWVhciENCj4+IERpZCBhbnlvbmUgdHJ5IHVzYiBhdWRpbyBkZXZpY2Ugb3Igb3RoZXIg
aXNvY2hyb25vdXMgbW9kZSB1c2IgZGV2aWNlcw0KPj4gb24gSWNlY3ViZSBib2FyZChNb3Rvcm9s
YSBNUEM1MjAwKT8NCj4+IEkgdHJpZWQsIGJ1dCBpdCByZXBvcnRzIHRoZSBmb2xsb3dpbmcgbWVz
c2FnZToNCj4+IC8iaG9zdC91c2Itb2hjaS5jOiBPSENJIFVucmVjb3ZlcmFibGUgRXJyb3IsIGNv
bnRyb2xsZXIgdXNiLTAgZGlzYWJsZWQiLw0KPj4gQWZ0ZXIgdGhpcyBtZXNzYWdlLCB0aGUgaG9z
dCBjb250cm9sbGVyIGlzIGRpc2FibGVkLg0KPj4gVGhhbmtzIGEgbG90Lg0KPj4NCj4+LS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tDQo+Pg0KPj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KPj5MaW51eHBwYy1kZXYgbWFpbGluZyBsaXN0DQo+PkxpbnV4cHBjLWRldkBvemxh
YnMub3JnDQo+Pmh0dHBzOi8vb3psYWJzLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2xpbnV4cHBjLWRl
dg0KPj4NCj4gDQo+
^ permalink raw reply
* RE: inflate returned FFFFFFFD - what does this error exactly mean ?
From: Povolotsky, Alexander @ 2005-01-02 5:58 UTC (permalink / raw)
To: 'wd@denx.de', 'Jeff Angielski'; +Cc: linuxppc-embedded
>Try storing the compressed image at a higher address
>(like 0x400000 or so).
Originally I had relocation address be 0x00400000;
I also tried 0x00500000 and finally 0x00600000 (shown below)
- all 3 cases give the same error.
loaded at: 00180000 00268160
relocated to: 00600000 006E8160
board data at: 006E6124 006E6140
relocated to: 0060509C 006050B8
zimage at: 0060587D 006E5F82
avail ram: 006E9000 02000000
Linux/PPC load: console=ttyCPM0 panic=3 root=/dev/ram
Uncompressing Linux...
in gzip
after zalloc
after zlib_inflateInit2
after zlib_inflate
inflate returned FFFFFFFD
exit
-----Original Message-----
From: wd@denx.de [mailto:wd@denx.de]
Sent: Thursday, December 30, 2004 6:09 PM
To: Povolotsky, Alexander
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: inflate returned FFFFFFFD - what does this error exactly
mean ?
Hi Alex,
in message
<313680C9A886D511A06000204840E1CF0A647439@whq-msgusr-02.pit.comms.marconi.co
m> you wrote:
>
> After few days of wondering through debugging (and with
> great help) I fixed (by inserting watch dog resets into
> beginning of while loops in zlib functions) my first problem > - strange
reboot failures during decompression of
You know why I recommended U-Boot :-)
> Now I am getting "controlled" failure (during the same
> decompression as described above):
>
> I_BAD
> return Z_DATA_ERROR
> after zlib_inflate
> inflate returned FFFFFFFD
> exit
>
> what does this error exactly mean ?
Most probably it means that the areas where the compressed image is stored
and to where you copy the uncompressed code to are over-lapping.
Try storing the compressed image at a higher address
(like 0x400000 or so).
Best regards,
Wolfgang Denk
-----Original Message-----
From: Nigel Cunningham [mailto:Nigel.Cunningham@cyclades.com]
Sent: Thursday, December 30, 2004 5:45 PM
To: Povolotsky, Alexander
Cc: linuxppc-embedded@ozlabs.org; linuxppc-embedded-bounces@ozlabs.org
Subject: Re: inflate returned FFFFFFFD - what does this error exactly mean ?
Hi.
linuxppc-embedded-bounces@ozlabs.org wrote on 31/12/2004 09:27:53:
> Hi,
>
> After few days of wondering through debugging (and with
> great help) I fixed (by inserting watch dog resets into
> beginning of while loops in zlib functions) my first
> problem -strange reboot failures during decompression of
> the kernel image by the bootloader.
> However my luck expired beyond this fix so far ... ;-).
> Now I am getting "controlled" failure (during the same
> decompression as described above):
>
> I_BAD
> return Z_DATA_ERROR
> after zlib_inflate
> inflate returned FFFFFFFD
> exit
>
> what does this error exactly mean ?
Going from include/linux/zlib.h, it is a data error: your compressed stream
has somehow been corrupted?
Regards,
Nigel
--
^ permalink raw reply
* Re: [FYI] linux 2.6 still not working with PReP (ppc32)
From: Sven Luther @ 2005-01-02 9:39 UTC (permalink / raw)
To: Sebastian Heutling; +Cc: linuxppc-dev, Marc Dietrich
In-Reply-To: <1104623790.10369.14.camel@weizen.left.earth>
On Sun, Jan 02, 2005 at 12:56:29AM +0100, Sebastian Heutling wrote:
> On Fri, 2004-12-31 at 23:28 +0100, Sven Luther wrote:
> > On Fri, Dec 31, 2004 at 04:00:49PM +0100, Sebastian Heutling wrote:
> > > On Fri, 2004-12-31 at 10:55 +0100, Sven Luther wrote:
> > > > On Mon, Dec 27, 2004 at 03:47:05AM +0100, Christian wrote:
> > > > > Marc Dietrich schrieb:
> > > > > >Hi all,
> > > > > >
> > > > > >I read this thread about booting a PowerStack with newer kernels.
> > > > > >Motivated by this, I tried to compile a 2.6.10 kernel on my machine (with
> > > > > >sym53c825a onboard). Sadly, the scsi controller always timeouts during
> > > > > >initialisation. I
> > > >
> > > > I also have some strange issues with network support using the standard debian
> > > > 2.6.8 kernel. ifconfig upping the decchip ethernet on the powerstack freezes
> > > > the kernel, and i hear reports of problems on IBM PReP hardware too with not
> > > > working ethernet, altough there is no freeze.
> > > >
> > > > Any idea on this ?
> > >
> > > Does it contain the IRQ patch? Where does it boot from SCSI or net? What
> > > PCI-Devices are installed?
> >
> > Probably not, just the standard debian kernel, i donÃ't remember any irq
> > patches, but there where a bunch of patches from leighbb. it is done
>
> The patch is the one that is included in 2.6.10 which is mentioned above
> and this thread already has somewhere in the beginning. I attached it
> below.
> I haven't had the time yet to test the 2.6.10 kernel. Maybe there is
> another problem now ...
The one with three lines of modified irq lines from tom rini ? I found it in
google, but i also saw another bunch of prep changes which got in 2.6.9 i
think. Since debian is still using 2.6.8 and a bunch of backports, these may
be relevant, i think.
Also, i think for some reason i was unsubscribed while the list moved to
ozlab, and lost maybe the start of the thread, thanks for the attachement.
> > netbooting, and the only pci device installed is the cirruss logic graphic
> > card.
>
> If you use the standard debian kernel - ok, it doesn't work because of
> wrong IRQs on the PowerstackII (Utah).
Which i will now fix now that i am aware of the problem. There seem to be also
a problem on IBM prep hardware, may it be related ?
> BTW: The onboard Winbond IDE chip works as well although no connector is
> provided. You only need a little bit of soldering and adjusting the IRQ
> of Slot 1 from 0 to 4. :-)
Ah, wondered about that, and saw the slots are not soldered. I wonder why go
to all the trouble including a IDE chip, but not solder the connectors. Seems
to me like peanut savings or something.
Friendly,
Sven Luther
>
>
> Sebastian Heutling
>
> --
> diff -puN
> arch/ppc/platforms/prep_pci.c~ppc32-fix-motorola-prep-powerstackii-utah-pci-irq-map arch/ppc/platforms/prep_pci.c
> ---
> 25/arch/ppc/platforms/prep_pci.c~ppc32-fix-motorola-prep-powerstackii-utah-pci-irq-map 2004-12-07 01:01:16.000000000 -0800
> +++ 25-akpm/arch/ppc/platforms/prep_pci.c 2004-12-07
> 01:01:16.000000000 -0800
> @@ -49,10 +49,10 @@ static char Utah_pci_IRQ_map[23] __prepd
> 0, /* Slot 1 - unused */
> 5, /* Slot 2 - SCSI - NCR825A */
> 0, /* Slot 3 - unused */
> - 1, /* Slot 4 - Ethernet - DEC2114x */
> + 3, /* Slot 4 - Ethernet - DEC2114x */
> 0, /* Slot 5 - unused */
> - 3, /* Slot 6 - PCI Card slot #1 */
> - 4, /* Slot 7 - PCI Card slot #2 */
> + 2, /* Slot 6 - PCI Card slot #1 */
> + 3, /* Slot 7 - PCI Card slot #2 */
> 5, /* Slot 8 - PCI Card slot #3 */
> 5, /* Slot 9 - PCI Bridge */
> /* added here in case we ever support PCI bridges */
>
>
>
^ permalink raw reply
* Re: 43p-140 install issues
From: Sven Luther @ 2005-01-02 9:43 UTC (permalink / raw)
To: mikemartin; +Cc: Ulrich Teichert, linuxppc-dev, debian-powerpc, debian-boot
In-Reply-To: <855e88d00501011715633922b2@mail.gmail.com>
On Sat, Jan 01, 2005 at 08:15:13PM -0500, Mike Martin wrote:
> I can boot with this image:
> http://debian.yorku.ca/debian/dists/testing/main/installer-powerpc/current/images/powerpc/netboot/vmlinuz-prep.initrd
Cool.
> And things seems to go very well. Network configures, hard drives
> partition, it dies at "Install the base system" with "The debootstrap
> program exited with an error (return value 255)." It instructs me to
> check /var/log/messages which now contains: "execv: No such file or
> directory"
Strange, can you check at what percentage of "install base system" this error
happned ? can you attach the full /var/log/messages and /var/log/syslog ?
Mmm, CCing debian-boot as this seems more relevant there.@
> The previous step, partitioning, added:
> "No matching physical volumes found
> No volume groups found
> Reading all physical volumes. This may take a while..."
>
> Anyone?
>
> MikeMartin
>
> On Sat, 1 Jan 2005 17:57:58 +0100, Sven Luther <sven.luther@wanadoo.fr> wrote:
> > On Sat, Jan 01, 2005 at 05:30:25PM +0100, Ulrich Teichert wrote:
> > > Hi,
> > >
> > > [del]
> > > >I would prefer that we fix the debian kernels for them to work correctly
> > > >though. More on this on monday.
> > >
> > > I failed to configure a stock 2.4.28 kernel to detect the SCSI controler.
> > > I think some of Leigh patches for this must be applied, but I haven't
> > > gone any further.
> >
> > I had some report on a power3 box, that only the SMP sym53c8xx driver worked.
> > When configuring in UP mode,
> >
> > > [del]
> > > >Do the debian 2.4.27 kernel work on it ? I was unable to boot the 2.4.27 d-i
> > > >kernel on my powerstack, but this is a different machine, so the issues may be
> > > >a bit different.
> > >
> > > I've only tried the Woody PREP kernel, which failed in a way which I can't
> > > remember, but I'll give it a try.
> >
> > Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel too.
> > Let' try to get this fixed before the sarge release, which is not so far off
> > now.
Friendly,
Sven Luther
^ permalink raw reply
* Re: inflate returned FFFFFFFD - what does this error exactly mean ?
From: Dan Malek @ 2005-01-02 15:32 UTC (permalink / raw)
To: Povolotsky, Alexander; +Cc: 'Jeff Angielski', linuxppc-embedded
In-Reply-To: <313680C9A886D511A06000204840E1CF0A64743E@whq-msgusr-02.pit.comms.marconi.com>
On Jan 2, 2005, at 12:58 AM, Povolotsky, Alexander wrote:
> Originally I had relocation address be 0x00400000;
> I also tried 0x00500000 and finally 0x00600000 (shown below)
> - all 3 cases give the same error.
>
>
> loaded at: 00180000 00268160
> relocated to: 00600000 006E8160
You are doing this backward. You need to load the
image into memory at a higher address like 0x400000.
According to this message, you are loading at 0x180000.
Don't change the relocation address for the build, just
the address where you initially load it into memory.
-- Dan
^ permalink raw reply
* Re: 43p-140 install issues
From: Ulrich Teichert @ 2005-01-02 15:38 UTC (permalink / raw)
To: Sven Luther; +Cc: Ulrich Teichert, linuxppc-dev, mikemartin, debian-powerpc
In-Reply-To: <20050101165758.GA18559@pegasos>
Hi,
[del]
>Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel too.
>Let' try to get this fixed before the sarge release, which is not so far off
>now.
OK, 9 hours later I had a current sarge buisnesscard CD image, with
interesting results. I booted the standard kernel from the cdrom
with `boot cdrom:`, it came up and failed to load the initrd, so it died
on the spot as nothing could be mounted. It was detecting that I was using
a serial console.
Of course, I forgot to capture that session, so I did it again with logging
on in kermit. Then I could not boot anything from the CD, but I can still
boot fine from disk, so it's not a hardware problem. The LED displays F05
after reading something from the CDROM in this case and the machine hangs.
Strange.
I will try to boot via tftp, the firmware seems to be unable to boot
a specific file from CDROM,
CU,
Uli
--
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24 |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)
^ permalink raw reply
* CPU15 errata workaround for 8xx by WD
From: Joakim Tjernlund @ 2005-01-02 14:12 UTC (permalink / raw)
To: Wolfgang Denk, linuxppc-embedded
Hi Wolfgang
Had a look at your CPU15 errata workaround for 8xx and I have a comment
or two:
1) I think you should make the sysctl support a compile time option
as the overhead for sysctl support in the TLB handler is 6 instr. when
the fix itself is only 4 instr.
2) You placed the workaround in the middle of the CPU6 workaround which will
disable the CPU6 workaround(I think). Move it before the #ifdef CONFIG_8xx_CPU6
and you should be fine.
3) Your test program uses the dcbst and dcbi instr. and these are buggy as they do not
update the DAR register in the TLB exceptions. I guess you made sure that such errors
will not happen?
4) The CPU15 bug has been around for years I think, what made it show up now? New toolchains?
Jocke
^ permalink raw reply
* RE: inflate returned FFFFFFFD - what does this error exactly mean ?
From: Povolotsky, Alexander @ 2005-01-02 16:07 UTC (permalink / raw)
To: 'Dan Malek'; +Cc: 'Jeff Angielski', linuxppc-embedded
>You need to load the
>image into memory at a higher address like 0x400000.
Where the initial load address is getting set ?
-----Original Message-----
From: Dan Malek [mailto:dan@embeddededge.com]
Sent: Sunday, January 02, 2005 10:33 AM
To: Povolotsky, Alexander
Cc: 'Jeff Angielski'; 'wd@denx.de'; linuxppc-embedded@ozlabs.org
Subject: Re: inflate returned FFFFFFFD - what does this error exactly mean ?
On Jan 2, 2005, at 12:58 AM, Povolotsky, Alexander wrote:
> Originally I had relocation address be 0x00400000;
> I also tried 0x00500000 and finally 0x00600000 (shown below)
> - all 3 cases give the same error.
>
>
> loaded at: 00180000 00268160
> relocated to: 00600000 006E8160
You are doing this backward. You need to load the
image into memory at a higher address like 0x400000.
According to this message, you are loading at 0x180000.
Don't change the relocation address for the build, just
the address where you initially load it into memory.
-- Dan
-----Original Message-----
From: Povolotsky, Alexander
Sent: Sunday, January 02, 2005 12:58 AM
To: 'wd@denx.de'; 'Jeff Angielski'
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: inflate returned FFFFFFFD - what does this error exactly
mean ?
>Try storing the compressed image at a higher address
>(like 0x400000 or so).
Originally I had relocation address be 0x00400000;
I also tried 0x00500000 and finally 0x00600000 (shown below)
- all 3 cases give the same error.
loaded at: 00180000 00268160
relocated to: 00600000 006E8160
board data at: 006E6124 006E6140
relocated to: 0060509C 006050B8
zimage at: 0060587D 006E5F82
avail ram: 006E9000 02000000
Linux/PPC load: console=ttyCPM0 panic=3 root=/dev/ram
Uncompressing Linux...
in gzip
after zalloc
after zlib_inflateInit2
after zlib_inflate
inflate returned FFFFFFFD
exit
--
^ permalink raw reply
* Re: 43p-140 install issues
From: Sven Luther @ 2005-01-02 16:41 UTC (permalink / raw)
To: Ulrich Teichert; +Cc: linuxppc-dev, mikemartin, debian-powerpc
In-Reply-To: <200501021538.j02Fc0Ld013444@arbas.nms.ulrich-teichert.org>
On Sun, Jan 02, 2005 at 04:38:00PM +0100, Ulrich Teichert wrote:
> Hi,
>
> [del]
> >Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel too.
> >Let' try to get this fixed before the sarge release, which is not so far off
> >now.
>
> OK, 9 hours later I had a current sarge buisnesscard CD image, with
> interesting results. I booted the standard kernel from the cdrom
> with `boot cdrom:`, it came up and failed to load the initrd, so it died
> on the spot as nothing could be mounted. It was detecting that I was using
> a serial console.
You need to boot install/powerpc/vmlinuz-prep.initrd, not the vmlinux one.
> Of course, I forgot to capture that session, so I did it again with logging
> on in kermit. Then I could not boot anything from the CD, but I can still
> boot fine from disk, so it's not a hardware problem. The LED displays F05
> after reading something from the CDROM in this case and the machine hangs.
> Strange.
>
> I will try to boot via tftp, the firmware seems to be unable to boot
> a specific file from CDROM,
Ah, strange. That said, tftp is the prefered boot method for prep hardware.
Friendly,
Sven Luther
^ permalink raw reply
* clarification to the previous post question - RE: inflate returne d FFFFFFFD - what does this error exactly
From: Povolotsky, Alexander @ 2005-01-02 18:00 UTC (permalink / raw)
To: 'Dan Malek'
Cc: 'Jeff Angielski', 'linuxppc-embedded@ozlabs.org'
I am using the bootloader from Integrated Systems, Inc (former maker of the
PSOS").
Does anyone else on this list use this bootloader for loading Linux?
Where the initial load address is getting set there ?
Thanks,
Alex
^ permalink raw reply
* Re: CPU15 errata workaround for 8xx by WD
From: Wolfgang Denk @ 2005-01-02 20:54 UTC (permalink / raw)
To: Joakim.Tjernlund; +Cc: linuxppc-embedded
In-Reply-To: <BCEFJBPJCGFCNMMMIDBHOEPBCJAA.Joakim.Tjernlund@lumentis.se>
Dear Joakim,
in message <BCEFJBPJCGFCNMMMIDBHOEPBCJAA.Joakim.Tjernlund@lumentis.se> you wrote:
>
> Had a look at your CPU15 errata workaround for 8xx and I have a comment
> or two:
>
> 1) I think you should make the sysctl support a compile time option
> as the overhead for sysctl support in the TLB handler is 6 instr. when
> the fix itself is only 4 instr.
You are right. For a permanent patch that would be better - in our
case it was important to be able to turn on and off this workaround
dynamically with exactly the same kernel binary. We wanted to have
real proof that the effects we saw were caused by CPU15 erratum, and
that the workaround fixes these problems.
> 2) You placed the workaround in the middle of the CPU6 workaround which will
> disable the CPU6 workaround(I think). Move it before the #ifdef CONFIG_8xx_CPU6
> and you should be fine.
I think you are right.
> 3) Your test program uses the dcbst and dcbi instr. and these are buggy as they do not
> update the DAR register in the TLB exceptions. I guess you made sure that such errors
> will not happen?
Ummm... I think so.
> 4) The CPU15 bug has been around for years I think, what made it show up now? New toolchains?
No, this is not a toolchain issue. It's a processor problem.
I have to admit that I didn't believe our customer when he reported
that he has problems that were caused by the CPU15 bug - I never saw
this on any other 8xx processor before, and as you say it has been
mentioned in all errata sheets I can remember. As far as I can tell
it is only the MPC870/885 duet family of processors where this CPU15
bug actually hits. I have no idea why.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Brain: an apparatus with which we think we think. - Ambrose Bierce
^ permalink raw reply
* Re: [FYI] linux 2.6 still not working with PReP (ppc32)
From: Sebastian Heutling @ 2005-01-02 21:33 UTC (permalink / raw)
To: Sven Luther; +Cc: linuxppc-dev, Marc Dietrich
In-Reply-To: <20050102093908.GA25739@pegasos>
On Sun, 2005-01-02 at 10:39 +0100, Sven Luther wrote:
> On Sun, Jan 02, 2005 at 12:56:29AM +0100, Sebastian Heutling wrote:
> > On Fri, 2004-12-31 at 23:28 +0100, Sven Luther wrote:
> > > On Fri, Dec 31, 2004 at 04:00:49PM +0100, Sebastian Heutling wrote:
> > > > On Fri, 2004-12-31 at 10:55 +0100, Sven Luther wrote:
> > > > > On Mon, Dec 27, 2004 at 03:47:05AM +0100, Christian wrote:
> > > > > > Marc Dietrich schrieb:
> > > > > > >Hi all,
> > > > > > >
> > > > > > >I read this thread about booting a PowerStack with newer kernels.
> > > > > > >Motivated by this, I tried to compile a 2.6.10 kernel on my machine (with
> > > > > > >sym53c825a onboard). Sadly, the scsi controller always timeouts during
> > > > > > >initialisation. I
> > > > >
> > > > > I also have some strange issues with network support using the standard debian
> > > > > 2.6.8 kernel. ifconfig upping the decchip ethernet on the powerstack freezes
> > > > > the kernel, and i hear reports of problems on IBM PReP hardware too with not
> > > > > working ethernet, altough there is no freeze.
> > > > >
> > > > > Any idea on this ?
> > > >
> > > > Does it contain the IRQ patch? Where does it boot from SCSI or net? What
> > > > PCI-Devices are installed?
> > >
> > > Probably not, just the standard debian kernel, i donÃ't remember any irq
> > > patches, but there where a bunch of patches from leighbb. it is done
> >
> > The patch is the one that is included in 2.6.10 which is mentioned above
> > and this thread already has somewhere in the beginning. I attached it
> > below.
> > I haven't had the time yet to test the 2.6.10 kernel. Maybe there is
> > another problem now ...
>
> The one with three lines of modified irq lines from tom rini ? I found it in
> google, but i also saw another bunch of prep changes which got in 2.6.9 i
Hmmm ... I didn't realise any other prep changes in 2.6.9
> think. Since debian is still using 2.6.8 and a bunch of backports, these may
> be relevant, i think.
You mean debian/testing?
>
> Also, i think for some reason i was unsubscribed while the list moved to
> ozlab, and lost maybe the start of the thread, thanks for the attachement.
That explains a lot ;-)
>
> > > netbooting, and the only pci device installed is the cirruss logic graphic
> > > card.
> >
> > If you use the standard debian kernel - ok, it doesn't work because of
> > wrong IRQs on the PowerstackII (Utah).
>
> Which i will now fix now that i am aware of the problem. There seem to be also
> a problem on IBM prep hardware, may it be related ?
Looking at the IRQ tables in prep_pci.c it very possible. There are a
lot structures which have a lot of low numbered slots initialised to 0.
Might be that its the same problem: PCI slotnumbering has changed
resulting in wrong used entries in this tables. People should look at
this particular place if they have problems like lost interrupts, kernel
output saying that a device got IRQ 0, timeouts or something like that.
>
> > BTW: The onboard Winbond IDE chip works as well although no connector is
> > provided. You only need a little bit of soldering and adjusting the IRQ
> > of Slot 1 from 0 to 4. :-)
>
> Ah, wondered about that, and saw the slots are not soldered. I wonder why go
> to all the trouble including a IDE chip, but not solder the connectors. Seems
> to me like peanut savings or something.
I am not sure but I think there are two versions of this machine: One
with only IDE connectors and one with only SCSI connector.
But to be honest: I don't know as well why they didn't solder all
connectors.
Sebastian Heutling
^ permalink raw reply
* RE: CPU15 errata workaround for 8xx by WD
From: Joakim Tjernlund @ 2005-01-02 21:58 UTC (permalink / raw)
To: wd; +Cc: linuxppc-embedded
In-Reply-To: <20050102205429.8F01DC14DD@atlas.denx.de>
> Dear Joakim,
>
> in message <BCEFJBPJCGFCNMMMIDBHOEPBCJAA.Joakim.Tjernlund@lumentis.se> you wrote:
> >
> > Had a look at your CPU15 errata workaround for 8xx and I have a comment
> > or two:
> >
> > 1) I think you should make the sysctl support a compile time option
> > as the overhead for sysctl support in the TLB handler is 6 instr. when
> > the fix itself is only 4 instr.
>
> You are right. For a permanent patch that would be better - in our
> case it was important to be able to turn on and off this workaround
> dynamically with exactly the same kernel binary. We wanted to have
> real proof that the effects we saw were caused by CPU15 erratum, and
> that the workaround fixes these problems.
Have you done any performance measurements with with/without the CPU15
patch? To always invalidate the previous and the next TLB(plus the extra code in the
TLB handler) seems expensive.
>
> > 2) You placed the workaround in the middle of the CPU6 workaround which will
> > disable the CPU6 workaround(I think). Move it before the #ifdef CONFIG_8xx_CPU6
> > and you should be fine.
>
> I think you are right.
>
> > 3) Your test program uses the dcbst and dcbi instr. and these are buggy as they do not
> > update the DAR register in the TLB exceptions. I guess you made sure that such errors
> > will not happen?
>
> Ummm... I think so.
Me too, but I only had a quick look.
>
> > 4) The CPU15 bug has been around for years I think, what made it show up now? New toolchains?
>
> No, this is not a toolchain issue. It's a processor problem.
>
> I have to admit that I didn't believe our customer when he reported
> that he has problems that were caused by the CPU15 bug - I never saw
> this on any other 8xx processor before, and as you say it has been
> mentioned in all errata sheets I can remember. As far as I can tell
> it is only the MPC870/885 duet family of processors where this CPU15
> bug actually hits. I have no idea why.
That explains why I never seen this before, thanks.
A better fix would be to make the toolchain insert an extra NOP if
the last instr. in a page is a branch, but that will take some time.
Any GCC people on this list?
Regards
Joakim
>
> Best regards,
>
> Wolfgang Denk
^ permalink raw reply
* Re: 43p-140 install issues
From: Mike Martin @ 2005-01-03 4:15 UTC (permalink / raw)
To: Sven Luther; +Cc: Ulrich Teichert, linuxppc-dev, debian-powerpc
In-Reply-To: <855e88d00501011715633922b2@mail.gmail.com>
Now I'm very confused .... on my next reboot ... the network wouldn't
work. After much trial and error, I got the current unstable d-i image
to work. It did it all right up to the reboot (where is warns you that
it doesn't have a boot loader installed).
Now what!
I have an installed system, but I can't figure out how to boot it! I
have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
write a boot sector or tell OpenFirmware to boot from this file? I
tried to netboot and set root=/dev/sdb1 - but without the scsi modules
loaded it fails to read the drives and panics.
I think I neet to create a type 41 PReP boot partition and get the
kernel onto it. I've found this thread:
http://lists.gnu.org/archive/html/bug-parted/2002-09/msg00016.html
and this:
http://www.yellowdoglinux.com/support/solutions/champion_server/rs6k.shtml
I tried booting up with the installer, going to a shell after the scsi
was active and the installed system was mounted. I used sfdisk from
/target/sbin to create a 10 Meg type 41 partition on the first HD
(/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
partition. But it still won't boot.
I'm very close. If I can get the system to boot (really it needs to
boot itself - not netboot) I'd call this a success.
Thanks!
MikeM
On Sat, 1 Jan 2005 20:15:13 -0500, Mike Martin <sydneymartin@gmail.com> wrote:
> I can boot with this image:
> http://debian.yorku.ca/debian/dists/testing/main/installer-powerpc/current/images/powerpc/netboot/vmlinuz-prep.initrd
>
> And things seems to go very well. Network configures, hard drives
> partition, it dies at "Install the base system" with "The debootstrap
> program exited with an error (return value 255)." It instructs me to
> check /var/log/messages which now contains: "execv: No such file or
> directory"
>
> The previous step, partitioning, added:
> "No matching physical volumes found
> No volume groups found
> Reading all physical volumes. This may take a while..."
>
> Anyone?
>
> MikeMartin
>
> On Sat, 1 Jan 2005 17:57:58 +0100, Sven Luther <sven.luther@wanadoo.fr> wrote:
> > On Sat, Jan 01, 2005 at 05:30:25PM +0100, Ulrich Teichert wrote:
> > > Hi,
> > >
> > > [del]
> > > >I would prefer that we fix the debian kernels for them to work correctly
> > > >though. More on this on monday.
> > >
> > > I failed to configure a stock 2.4.28 kernel to detect the SCSI controler.
> > > I think some of Leigh patches for this must be applied, but I haven't
> > > gone any further.
> >
> > I had some report on a power3 box, that only the SMP sym53c8xx driver worked.
> > When configuring in UP mode,
> >
> > > [del]
> > > >Do the debian 2.4.27 kernel work on it ? I was unable to boot the 2.4.27 d-i
> > > >kernel on my powerstack, but this is a different machine, so the issues may be
> > > >a bit different.
> > >
> > > I've only tried the Woody PREP kernel, which failed in a way which I can't
> > > remember, but I'll give it a try.
> >
> > Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel too.
> > Let' try to get this fixed before the sarge release, which is not so far off
> > now.
> >
> > Friendly,
> >
> > Sven Luther
> >
> >
>
^ permalink raw reply
* Re: 43p-140 install issues
From: Sven Luther @ 2005-01-03 7:05 UTC (permalink / raw)
To: mikemartin; +Cc: Ulrich Teichert, linuxppc-dev, debian-powerpc
In-Reply-To: <855e88d0050102201540148511@mail.gmail.com>
On Sun, Jan 02, 2005 at 11:15:35PM -0500, Mike Martin wrote:
> Now I'm very confused .... on my next reboot ... the network wouldn't
> work. After much trial and error, I got the current unstable d-i image
> to work. It did it all right up to the reboot (where is warns you that
> it doesn't have a boot loader installed).
There may be some problems with 2.6 kernels and pci irqs on prep. I will
investigate this shortly.
There is indeed no prep boot-loader installer available. I hear there is a
partman-prep prepared, but not yet part of d-i. more to this below.
> Now what!
>
> I have an installed system, but I can't figure out how to boot it! I
> have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
> write a boot sector or tell OpenFirmware to boot from this file? I
> tried to netboot and set root=/dev/sdb1 - but without the scsi modules
> loaded it fails to read the drives and panics.
You need to install mkvmlinuz, i think it is already, but not use
/boot/vmlinux-2.6.8-powerpc, but /boot/vmlinuz-2.6.8-powerpc, which is the
result of mkvmlinuz adding the initrd containing the modules onto the kernel,
and then adding the prep simple bootloader. Check if you have the
vmlinuz-2.6.8-powerpc, which should have been generated at install time, and
copy it to your netboot tftp server, and try again. It should even recognize
the root= partition automatically.
> I think I neet to create a type 41 PReP boot partition and get the
> kernel onto it. I've found this thread:
> http://lists.gnu.org/archive/html/bug-parted/2002-09/msg00016.html
>
> and this:
> http://www.yellowdoglinux.com/support/solutions/champion_server/rs6k.shtml
Yep. Until partman-prep is ready, you should simply try to add the prep flag
to the a small partition. I think the normal scheme is to create /dev/sdb1 as
a small (8MB ?) prep partition, /dev/sdb2 as swap, and /dev/sdb3 as /. If
partman is not able to do it, jump to console 2, and launch parted directly,
and do a set 1 prep on.
Then i suppose that copying the kernel is just a matter of :
dd if=/boot/vmlinuz-2.6.8-powerpc of=/dev/sdb1
but you have to have a small prep partition as /dev/sdb1, or the above will
erase whatever you have on /dev/sdb1.
> I tried booting up with the installer, going to a shell after the scsi
> was active and the installed system was mounted. I used sfdisk from
> /target/sbin to create a 10 Meg type 41 partition on the first HD
> (/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
> partition. But it still won't boot.
Ah, no sure what is wrong. I don't think /dev/sdb0 exists. Not sure really.
> I'm very close. If I can get the system to boot (really it needs to
> boot itself - not netboot) I'd call this a success.
Friendly,
Sven Luther
^ permalink raw reply
* Re: 43p-140 install issues
From: Sven Luther @ 2005-01-03 10:48 UTC (permalink / raw)
To: Philippe Guyot
Cc: Ulrich Teichert, Mike Martin, linuxppc-dev, debian-powerpc,
mikemartin
In-Reply-To: <200501031056.30775.pguyot@cvf.fr>
On Mon, Jan 03, 2005 at 10:56:30AM +0100, Philippe Guyot wrote:
> On Monday 03 January 2005 05:15, Mike Martin wrote:
> > Now I'm very confused .... on my next reboot ... the network wouldn't
> > work. After much trial and error, I got the current unstable d-i image
> > to work. It did it all right up to the reboot (where is warns you that
> > it doesn't have a boot loader installed).
> >
> > Now what!
> >
> > I have an installed system, but I can't figure out how to boot it! I
> > have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
> > write a boot sector or tell OpenFirmware to boot from this file? I
> > tried to netboot and set root=/dev/sdb1 - but without the scsi modules
> > loaded it fails to read the drives and panics.
> >
> > I think I neet to create a type 41 PReP boot partition and get the
> > kernel onto it. I've found this thread:
> > http://lists.gnu.org/archive/html/bug-parted/2002-09/msg00016.html
> >
> > and this:
> > http://www.yellowdoglinux.com/support/solutions/champion_server/rs6k.shtml
> >
> > I tried booting up with the installer, going to a shell after the scsi
> > was active and the installed system was mounted. I used sfdisk from
> > /target/sbin to create a 10 Meg type 41 partition on the first HD
> > (/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
> > partition. But it still won't boot.
>
>
> I succeeded last year to install a woody on a 143P-140 whith the help of Leigh
> Brown (thanks to him again). And two 150 whit sarge also.
>
> I'm not sure, but I have the feeling that your image on the prep partition
> (should be type 0x41) is not able to determine where the root is, so Leigh
> did a piece of code named "preptools" in order to patch the image with the
> location of root.
Hey, cool, where is this tool ? We need to package it for debian if it is not
already, and use it in d-i, and maybe even mkvmlinuz directly.
Friendly,
Sven Luther
^ permalink raw reply
* Re: 43p-140 install issues
From: Philippe Guyot @ 2005-01-03 9:56 UTC (permalink / raw)
To: mikemartin, Mike Martin, Sven Luther
Cc: Ulrich Teichert, linuxppc-dev, debian-powerpc
In-Reply-To: <855e88d0050102201540148511@mail.gmail.com>
On Monday 03 January 2005 05:15, Mike Martin wrote:
> Now I'm very confused .... on my next reboot ... the network wouldn't
> work. After much trial and error, I got the current unstable d-i image
> to work. It did it all right up to the reboot (where is warns you that
> it doesn't have a boot loader installed).
>
> Now what!
>
> I have an installed system, but I can't figure out how to boot it! I
> have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
> write a boot sector or tell OpenFirmware to boot from this file? I
> tried to netboot and set root=/dev/sdb1 - but without the scsi modules
> loaded it fails to read the drives and panics.
>
> I think I neet to create a type 41 PReP boot partition and get the
> kernel onto it. I've found this thread:
> http://lists.gnu.org/archive/html/bug-parted/2002-09/msg00016.html
>
> and this:
> http://www.yellowdoglinux.com/support/solutions/champion_server/rs6k.shtml
>
> I tried booting up with the installer, going to a shell after the scsi
> was active and the installed system was mounted. I used sfdisk from
> /target/sbin to create a 10 Meg type 41 partition on the first HD
> (/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
> partition. But it still won't boot.
I succeeded last year to install a woody on a 143P-140 whith the help of Leigh
Brown (thanks to him again). And two 150 whit sarge also.
I'm not sure, but I have the feeling that your image on the prep partition
(should be type 0x41) is not able to determine where the root is, so Leigh
did a piece of code named "preptools" in order to patch the image with the
location of root.
To see if this can help, can you boot from openfirmware (BTW, is it the last
version? and have you updated the load_base and real-base values?) with this
parameter ?
boot disk root=/dev/whatever_root_sda_is
Hope this helps.
>
> I'm very close. If I can get the system to boot (really it needs to
> boot itself - not netboot) I'd call this a success.
>
> Thanks!
> MikeM
>
> On Sat, 1 Jan 2005 20:15:13 -0500, Mike Martin <sydneymartin@gmail.com>
wrote:
> > I can boot with this image:
> > http://debian.yorku.ca/debian/dists/testing/main/installer-powerpc/curren
> >t/images/powerpc/netboot/vmlinuz-prep.initrd
> >
> > And things seems to go very well. Network configures, hard drives
> > partition, it dies at "Install the base system" with "The debootstrap
> > program exited with an error (return value 255)." It instructs me to
> > check /var/log/messages which now contains: "execv: No such file or
> > directory"
> >
> > The previous step, partitioning, added:
> > "No matching physical volumes found
> > No volume groups found
> > Reading all physical volumes. This may take a while..."
> >
> > Anyone?
> >
> > MikeMartin
> >
> > On Sat, 1 Jan 2005 17:57:58 +0100, Sven Luther <sven.luther@wanadoo.fr>
wrote:
> > > On Sat, Jan 01, 2005 at 05:30:25PM +0100, Ulrich Teichert wrote:
> > > > Hi,
> > > >
> > > > [del]
> > > >
> > > > >I would prefer that we fix the debian kernels for them to work
> > > > > correctly though. More on this on monday.
> > > >
> > > > I failed to configure a stock 2.4.28 kernel to detect the SCSI
> > > > controler. I think some of Leigh patches for this must be applied,
> > > > but I haven't gone any further.
> > >
> > > I had some report on a power3 box, that only the SMP sym53c8xx driver
> > > worked. When configuring in UP mode,
> > >
> > > > [del]
> > > >
> > > > >Do the debian 2.4.27 kernel work on it ? I was unable to boot the
> > > > > 2.4.27 d-i kernel on my powerstack, but this is a different
> > > > > machine, so the issues may be a bit different.
> > > >
> > > > I've only tried the Woody PREP kernel, which failed in a way which I
> > > > can't remember, but I'll give it a try.
> > >
> > > Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel
> > > too. Let' try to get this fixed before the sarge release, which is not
> > > so far off now.
> > >
> > > Friendly,
> > >
> > > Sven Luther
^ permalink raw reply
* Re: 43p-140 install issues
From: Philippe Guyot @ 2005-01-03 10:56 UTC (permalink / raw)
To: Sven Luther
Cc: Ulrich Teichert, Mike Martin, linuxppc-dev, debian-powerpc,
mikemartin
In-Reply-To: <20050103104848.GA14682@pegasos>
On Monday 03 January 2005 11:48, Sven Luther wrote:
> On Mon, Jan 03, 2005 at 10:56:30AM +0100, Philippe Guyot wrote:
> > On Monday 03 January 2005 05:15, Mike Martin wrote:
> > > Now I'm very confused .... on my next reboot ... the network wouldn't
> > > work. After much trial and error, I got the current unstable d-i image
> > > to work. It did it all right up to the reboot (where is warns you that
> > > it doesn't have a boot loader installed).
> > >
> > > Now what!
> > >
> > > I have an installed system, but I can't figure out how to boot it! I
> > > have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
> > > write a boot sector or tell OpenFirmware to boot from this file? I
> > > tried to netboot and set root=/dev/sdb1 - but without the scsi modules
> > > loaded it fails to read the drives and panics.
> > >
> > > I think I neet to create a type 41 PReP boot partition and get the
> > > kernel onto it. I've found this thread:
> > > http://lists.gnu.org/archive/html/bug-parted/2002-09/msg00016.html
> > >
> > > and this:
> > > http://www.yellowdoglinux.com/support/solutions/champion_server/rs6k.sh
> > >tml
> > >
> > > I tried booting up with the installer, going to a shell after the scsi
> > > was active and the installed system was mounted. I used sfdisk from
> > > /target/sbin to create a 10 Meg type 41 partition on the first HD
> > > (/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
> > > partition. But it still won't boot.
> >
> > I succeeded last year to install a woody on a 143P-140 whith the help of
> > Leigh Brown (thanks to him again). And two 150 whit sarge also.
> >
> > I'm not sure, but I have the feeling that your image on the prep
> > partition (should be type 0x41) is not able to determine where the root
> > is, so Leigh did a piece of code named "preptools" in order to patch the
> > image with the location of root.
>
> Hey, cool, where is this tool ? We need to package it for debian if it is
> not already, and use it in d-i, and maybe even mkvmlinuz directly.
>
Just over there....
http://www.solinno.co.uk/7043-140/downloads.php
But ask Leigh for details.
Friendly.
Felipe
^ permalink raw reply
* Re: 43p-140 install issues
From: Sven Luther @ 2005-01-03 11:17 UTC (permalink / raw)
To: Philippe Guyot
Cc: Ulrich Teichert, Mike Martin, linuxppc-dev, debian-powerpc,
mikemartin
In-Reply-To: <200501031156.07353.pguyot@cvf.fr>
On Mon, Jan 03, 2005 at 11:56:07AM +0100, Philippe Guyot wrote:
> On Monday 03 January 2005 11:48, Sven Luther wrote:
> > On Mon, Jan 03, 2005 at 10:56:30AM +0100, Philippe Guyot wrote:
> > > On Monday 03 January 2005 05:15, Mike Martin wrote:
> > > > Now I'm very confused .... on my next reboot ... the network wouldn't
> > > > work. After much trial and error, I got the current unstable d-i image
> > > > to work. It did it all right up to the reboot (where is warns you that
> > > > it doesn't have a boot loader installed).
> > > >
> > > > Now what!
> > > >
> > > > I have an installed system, but I can't figure out how to boot it! I
> > > > have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
> > > > write a boot sector or tell OpenFirmware to boot from this file? I
> > > > tried to netboot and set root=/dev/sdb1 - but without the scsi modules
> > > > loaded it fails to read the drives and panics.
> > > >
> > > > I think I neet to create a type 41 PReP boot partition and get the
> > > > kernel onto it. I've found this thread:
> > > > http://lists.gnu.org/archive/html/bug-parted/2002-09/msg00016.html
> > > >
> > > > and this:
> > > > http://www.yellowdoglinux.com/support/solutions/champion_server/rs6k.sh
> > > >tml
> > > >
> > > > I tried booting up with the installer, going to a shell after the scsi
> > > > was active and the installed system was mounted. I used sfdisk from
> > > > /target/sbin to create a 10 Meg type 41 partition on the first HD
> > > > (/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
> > > > partition. But it still won't boot.
> > >
> > > I succeeded last year to install a woody on a 143P-140 whith the help of
> > > Leigh Brown (thanks to him again). And two 150 whit sarge also.
> > >
> > > I'm not sure, but I have the feeling that your image on the prep
> > > partition (should be type 0x41) is not able to determine where the root
> > > is, so Leigh did a piece of code named "preptools" in order to patch the
> > > image with the location of root.
> >
> > Hey, cool, where is this tool ? We need to package it for debian if it is
> > not already, and use it in d-i, and maybe even mkvmlinuz directly.
> >
>
> Just over there....
>
> http://www.solinno.co.uk/7043-140/downloads.php
> But ask Leigh for details.
Ok, thanks. ...
Friendly,
Sven Luther
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox