[Debian-ppc64-devel] Successful installation in an OpenPower 720 Express

martin at tuxedo.ag martin at tuxedo.ag
Wed Sep 14 11:09:51 UTC 2005


Hi Roberto,

On Wed, Sep 14, 2005 at 01:50:34PM +0200, Roberto Suarez Soto wrote:
> Hi,
> 
> 	after finishing with a pSeries 6E4 (Power4), we've been lucky to
> have an OpenPower 720 Express to test Debian on it. I'm attaching the dmesg
> output with this message (file "dmesg-marduk.txt"). Thanks to all involved
> for your efforts in making this work :-)

do you know the differences between OpenPower 720 and OpenPower720
Express? The Express is unknown to me.
> 
> 	Notes about the installation:
> 
> 	I used the ISO at
> http://ftp.uni-augsburg.de/pub/tuxppc/test/Debian-Installer-CD/. It
> installed correctly, but when I booted it crashed. I think it was the
> problem addressed by Harald G?rl (the creator of the CD) relative to Matrox
> support in the kernel (message of 09 Jun 2005). The installation kernel
> worked perfectly, but the kernel that is installed (though it has the
> option CONFIG_FB_MATROX=y, which IIRC was the issue) crashed. I'm attaching
> the output of the kernel until the crashing (file "dmesg-kaboom.txt").

On an OpenPower 720 the CD from Uni Augsburg worked fine.

> 
> 	I used the installation CD to mount the installed system and
> retrieve the latest kernel in Sven's website
> (http://people.debian.org/~luther/ppc64/),
> kernel-image-2.6.12-sven64_1_powerpc.deb. I installed it, and voila, it
> booted. The differences relative to Matrox between those two kernels are
> these ("diff 2.6.11-pseries 2.6.12-sven64"):
> 
> > CONFIG_W1_MATROX=m
> 4,6c5,8
> < # CONFIG_FB_MATROX_G is not set
> < # CONFIG_FB_MATROX_I2C is not set
> < # CONFIG_FB_MATROX_MULTIHEAD is not set
> ---
> > CONFIG_FB_MATROX_G=y
> > CONFIG_FB_MATROX_I2C=m
> > CONFIG_FB_MATROX_MAVEN=m
> > CONFIG_FB_MATROX_MULTIHEAD=y
> 
> 	So any of those options has something to do with the crash. I don't
> know if the difference between initrds is also implicated. You tell me :-)
> 
> 	I used Cajus' mirror. I don't know if I could have used the
> official one (I was in a hurry and wanted to play safe). Could I?  I'm
> willing to try another install, I've done nothing yet with this
> installation and  don't mind wiping it all now that I know it can be
> installed :-)

Which one is cajus' mirror? I used the packages from debian.gonicus.de.
Theese packages had a problem with the signatures. therefore some
tweaking to apt was necessary.
> 
> 	And in a slightly related note ... does anyone know how to
> configure the RAID controller in these things? I realized it had one when I
> did a dmesg (we didn't receive any tech specs with the OP), and I like to
> configure it properly. Any pointer to documentation will be greatly
> appreciated. Thanks in advance :-)

The raid is initialized via system boot cdrom.
AFAIK there is no other way to configure the raid.
When working with partitions one can assign two disks to a partition.
Further information on this hardware can be found in the Linux on Power
wiki: http://oss.gonicus.de/openpower/index.php/Main_Page

Regards,

Martin Alfke

> 
> -- 
> 	Roberto Suarez Soto				Allenta Consulting
> 	robe at allenta.com				   www.allenta.com

> Loading ramdisk...
> ramdisk loaded at 02200000, size: 1776 Kbytes
> OF stdout device is: /vdevice/vty at 30000000
> Hypertas detected, assuming LPAR !
> command line: root=/dev/sda2 ro ramdisk_size=8192
> memory layout at init:
>   alloc_bottom : 00000000023bc000
>   alloc_top    : 0000000008000000
>   alloc_top_hi : 00000000ef000000
>   rmo_top      : 0000000008000000
>   ram_top      : 00000000ef000000
> Looking for displays
> found display   : /pci at 800000020000002/pci at 2,6/pci at 1/display at 0, opening ... done
> instantiating rtas at 0x00000000077d7000... done
> 0000000000000000 : boot cpu     0000000000000000
> 0000000000000002 : starting cpu hw idx 0000000000000002... done
> Processor is not HMT capable
> copying OF device tree ...
> Building dt strings...
> Building dt structure...
> Device tree strings 0x00000000026bd000 -> 0x00000000026be297
> Device tree struct  0x00000000026bf000 -> 0x00000000026d7000
> Found initrd at 0xc000000002200000:0xc0000000023bc000
> firmware_features = 0x1ffd5f
> Partition configured for 4 cpus.
> Starting Linux PPC64 2.6.11-pseries
> -----------------------------------------------------
> ppc64_pft_size                = 0x1a
> ppc64_debug_switch            = 0x0
> ppc64_interrupt_controller    = 0x2
> systemcfg                     = 0xc000000000005000
> systemcfg->platform           = 0x101
> systemcfg->processorCount     = 0x4
> systemcfg->physicalMemorySize = 0xef000000
> ppc64_caches.dcache_line_size = 0x80
> ppc64_caches.icache_line_size = 0x80
> htab_address                  = 0x0000000000000000
> htab_hash_mask                = 0x7ffff
> -----------------------------------------------------
> [boot]0100 MM Init
> [boot]0100 MM Init Done
> Linux version 2.6.11-pseries (root at ppclinux) (gcc version 3.3.3 (Debian 20040401)) #1 SMP Thu Mar 10 15:36:53 CE5
> [boot]0012 Setup Arch
> Node 0 Memory: 0x0-0xef000000
> 0000000000000001 : starting thread
> 0000000000000003 : starting thread
> EEH: PCI Enhanced I/O Error Handling Enabled
> PPC64 nvram contains 7168 bytes
> Using dedicated idle loop
> [boot]0015 Setup Done
> Built 1 zonelists
> Kernel command line: root=/dev/sda2 ro ramdisk_size=8192
> [boot]0020 XICS Init
> xics: no ISA interrupt controller
> [boot]0021 XICS Done
> PID hash table entries: 4096 (order: 12, 131072 bytes)
> time_init: decrementer frequency = 188.045000 MHz
> time_init: processor frequency   = 1504.360000 MHz
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
> Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
> freeing bootmem node 0
> Memory: 3839232k/3915776k available (2576k kernel code, 76208k reserved, 1284k data, 253k bss, 216k init)
> Mount-cache hash table entries: 256 (order: 0, 4096 bytes)
> Processor 1 found.
> Processor 2 found.
> Processor 3 found.
> Brought up 4 CPUs
> checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd
> Freeing initrd memory: 1776k freed
> NET: Registered protocol family 16
> PCI: Probing PCI hardware
> IOMMU table initialized, virtual merging disabled
> mapping IO 3fe00200000 -> e000000000000000, size: 100000
> mapping IO 3fe00700000 -> e000000000100000, size: 100000
> PCI: Probing PCI hardware done
> usbcore: registered new driver hub
> TC classifier action (bugs to netdev at oss.sgi.com cc hadi at cyberus.ca)
> i/pSeries Real Time Clock Driver v1.1
> RTAS daemon started
> Total HugeTLB memory allocated, 0
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
> devfs: 2004-01-31 Richard Gooch (rgooch at atnf.csiro.au)
> devfs: boot_options: 0x0
> Initializing Cryptographic API
> Using unsupported 640x480 MTRX,G450 at c0000000, depth=8, pitch=640
> Oops: Kernel access of bad area, sig: 7 [#1]
> SMP NR_CPUS=32 NUMA PSERIES LPAR
> Modules linked in:
> NIP: C000000000171038 XER: 0000000D LR: C000000000165E70 CTR: C000000000170BC4
> REGS: c0000000023d2dc0 TRAP: 0300   Not tainted  (2.6.11-pseries)
> MSR: 8000000000009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11 CR: 24042044
> DAR: e000000080000000 DSISR: 0000000042000000
> TASK: c000000005b697e0[1] 'swapper' THREAD: c0000000023d0000 CPU: 1
> GPR00: 0000000000000000 C0000000023D3040 C0000000004673D8 000000000000000F
> GPR04: C0000000EEC90000 0000000000000000 C0000000EEC90000 E000000080000000
> GPR08: E000000080000004 0000000000000000 E000000080000000 0000000000000004
> GPR12: C000000002656280 C000000000374800 0000000000000000 0000000000000000
> GPR16: 0000000000000002 0000000000000000 0000000000000000 0000000000000000
> GPR20: 0000000000000000 0000000000000001 0000000000000000 0000000000000001
> GPR24: C0000000003C4E08 000000000000000F 0000000000000000 0000000000000004
> GPR28: C000000002664000 0000000000000000 C0000000003F66D8 C0000000023D3040
> NIP [c000000000171038] .cfb_imageblit+0x474/0x68c
> LR [c000000000165e70] .soft_cursor+0x1e0/0x270
> Call Trace:
> [c0000000023d3040] [c000000000375000] 0xc000000000375000 (unreliable)
> [c0000000023d3150] [c000000000165e70] .soft_cursor+0x1e0/0x270
> [c0000000023d3220] [c00000000015f99c] .bit_cursor+0x3b8/0x61c
> [c0000000023d3380] [c00000000015a6dc] .fbcon_cursor+0x220/0x30c
> [c0000000023d3440] [c00000000018957c] .hide_cursor+0x5c/0x8c
> [c0000000023d34d0] [c000000000189b3c] .redraw_screen+0x2e0/0x2e4
> [c0000000023d3580] [c000000000158ab0] .fbcon_prepare_logo+0x318/0x460
> [c0000000023d3670] [c000000000159e1c] .fbcon_init+0x338/0x3c8
> [c0000000023d3750] [c000000000189d64] .visual_init+0x1d8/0x27c
> [c0000000023d3800] [c00000000018f008] .take_over_console+0x448/0x668
> [c0000000023d38e0] [c00000000015872c] .fbcon_takeover+0xa4/0x110
> [c0000000023d3970] [c00000000015eae0] .fbcon_fb_registered+0xe8/0xf8
> [c0000000023d3a10] [c00000000015ec8c] .fbcon_event_notify+0xb8/0x110
> [c0000000023d3aa0] [c000000000065c8c] .notifier_call_chain+0x60/0xa4
> [c0000000023d3b30] [c0000000001619f4] .register_framebuffer+0x164/0x1f4
> [c0000000023d3c30] [c00000000030ecec] .offb_init_fb+0x2f8/0x584
> [c0000000023d3d20] [c00000000030e9bc] .offb_init_nodriver+0x1fc/0x234
> [c0000000023d3de0] [c00000000030e794] .offb_init+0xf4/0x120
> [c0000000023d3e70] [c0000000002eeb34] .do_initcalls+0x68/0x134
> [c0000000023d3f00] [c00000000000c378] .init+0x7c/0x1e0
> [c0000000023d3f90] [c000000000013750] .kernel_thread+0x4c/0x6c
> Instruction dump:
> 39080004 796b0020 2f00ffff 7c0507b4 7d295e30 2f8b0000 7f294838 79291764
> 7c09c02e 7c00d038 7c00ea78 78000020 <900a0000> 409e000c 39600008 38c60001
>  <0>Kernel panic - not syncing: Attempted to kill init!
> 

> Found initrd at 0xc000000002200000:0xc000000002404000
> firmware_features = 0x1ffd5f
> Partition configured for 4 cpus.
> Starting Linux PPC64 2.6.12-sven64
> -----------------------------------------------------
> ppc64_pft_size                = 0x1a
> ppc64_debug_switch            = 0x0
> ppc64_interrupt_controller    = 0x2
> systemcfg                     = 0xc000000000358000
> systemcfg->platform           = 0x101
> systemcfg->processorCount     = 0x4
> systemcfg->physicalMemorySize = 0xef000000
> ppc64_caches.dcache_line_size = 0x80
> ppc64_caches.icache_line_size = 0x80
> htab_address                  = 0x0000000000000000
> htab_hash_mask                = 0x7ffff
> -----------------------------------------------------
> [boot]0100 MM Init
> [boot]0100 MM Init Done
> Linux version 2.6.12-sven64 (sven at tael) (gcc version 4.0.1 (Debian 4.0.1-1ubuntu1)) #2 SMP Fri Jul 15 20:13:02 UTC 2005
> [boot]0012 Setup Arch
> Node 0 Memory: 0x0-0xef000000
> Syscall map setup, 242 32 bits and 220 64 bits syscalls
> EEH: PCI Enhanced I/O Error Handling Enabled
> PPC64 nvram contains 7168 bytes
> Using dedicated idle loop
> On node 0 totalpages: 978944
>   DMA zone: 978944 pages, LIFO batch:31
>   Normal zone: 0 pages, LIFO batch:1
>   HighMem zone: 0 pages, LIFO batch:1
> [boot]0015 Setup Done
> Built 1 zonelists
> Kernel command line: root=/dev/sda2 ro ramdisk_size=8192 
> [boot]0020 XICS Init
> xics: no ISA interrupt controller
> [boot]0021 XICS Done
> PID hash table entries: 4096 (order: 12, 131072 bytes)
> time_init: decrementer frequency = 188.047000 MHz
> time_init: processor frequency   = 1504.376000 MHz
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
> Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
> freeing bootmem node 0
> Memory: 3838332k/3915776k available (2852k kernel code, 76764k reserved, 1348k data, 268k bss, 236k init)
> Calibrating delay loop... 374.78 BogoMIPS (lpj=187392)
> Security Framework v1.0.0 initialized
> SELinux:  Disabled at boot.
> Capability LSM initialized
> Mount-cache hash table entries: 256
> Processor 1 found.
> Processor 2 found.
> Processor 3 found.
> Brought up 4 CPUs
> CPU0 attaching sched-domain:
>  domain 0: span 00000003
>   groups: 00000001 00000002
>   domain 1: span 0000000f
>    groups: 00000003 0000000c
>    domain 2: span 0000000f
>     groups: 0000000f
> CPU1 attaching sched-domain:
>  domain 0: span 00000003
>   groups: 00000002 00000001
>   domain 1: span 0000000f
>    groups: 00000003 0000000c
>    domain 2: span 0000000f
>     groups: 0000000f
> CPU2 attaching sched-domain:
>  domain 0: span 0000000c
>   groups: 00000004 00000008
>   domain 1: span 0000000f
>    groups: 0000000c 00000003
>    domain 2: span 0000000f
>     groups: 0000000f
> CPU3 attaching sched-domain:
>  domain 0: span 0000000c
>   groups: 00000008 00000004
>   domain 1: span 0000000f
>    groups: 0000000c 00000003
>    domain 2: span 0000000f
>     groups: 0000000f
> checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd
> Freeing initrd memory: 2064k freed
> NET: Registered protocol family 16
> PCI: Probing PCI hardware
> IOMMU table initialized, virtual merging enabled
> mapping IO 3fe00200000 -> e000000000000000, size: 100000
> mapping IO 3fe00700000 -> e000000000100000, size: 100000
> PCI: Probing PCI hardware done
> i/pSeries Real Time Clock Driver v1.1
> probe_bus_pseries: processing c0000000eeff78a0
> probe_bus_pseries: processing c0000000eeff7a88
> RTAS daemon started
> probe_bus_pseries: processing c0000000eeff7c70
> probe_bus_pseries: processing c0000000eeff7dd8
> probe_bus_pseries: processing c0000000eeff7f60
> RTAS: event: 13, Type: Dump Notification Event, Severity: 2
> audit: initializing netlink socket (disabled)
> audit(12601584.088:0): initialized
> devfs: 2004-01-31 Richard Gooch (rgooch at atnf.csiro.au)
> devfs: boot_options: 0x0
> Initializing Cryptographic API
> matroxfb: probe of 0000:d9:00.0 failed with error -1
> Using unsupported 640x480 display at 40080000000, depth=8, pitch=640
> Console: switching to colour frame buffer device 80x30
> fb0: Open Firmware frame buffer device on /pci at 800000020000002/pci at 2,6/pci at 1/display at 0
> vio_register_driver: driver hvc_console registering
> HVSI: registered 2 devices
> Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
> pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh at kernel.crashing.org>)
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> mice: PS/2 mouse device common for all mice
> NET: Registered protocol family 2
> IP: routing cache hash table of 16384 buckets, 256Kbytes
> TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
> TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
> TCP: Hash tables configured (established 524288 bind 65536)
> RAMDISK: cramfs filesystem found at block 0
> RAMDISK: Loading 2064KiB [1 disk] into ram disk... |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|done.
> VFS: Mounted root (cramfs filesystem) readonly.
> Freeing unused kernel memory: 236k freed
> NET: Registered protocol family 1
> usbcore: registered new driver usbfs
> usbcore: registered new driver hub
> ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
> ohci_hcd 0000:c8:01.0: NEC Corporation USB
> ohci_hcd 0000:c8:01.0: new USB bus registered, assigned bus number 1
> ohci_hcd 0000:c8:01.0: irq 133, io mem 0x400b8001000
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 3 ports detected
> hub 1-0:1.0: over-current change on port 1
> ohci_hcd 0000:c8:01.1: NEC Corporation USB (#2)
> ohci_hcd 0000:c8:01.1: new USB bus registered, assigned bus number 2
> ohci_hcd 0000:c8:01.1: irq 133, io mem 0x400b8000000
> hub 2-0:1.0: USB hub found
> hub 2-0:1.0: 2 ports detected
> PCI: Enabling device: (0000:c8:01.2), cmd 142
> ehci_hcd 0000:c8:01.2: NEC Corporation USB 2.0
> ehci_hcd 0000:c8:01.2: new USB bus registered, assigned bus number 3
> ehci_hcd 0000:c8:01.2: irq 133, io mem 0x400b8002000
> ehci_hcd 0000:c8:01.2: park 0
> ehci_hcd 0000:c8:01.2: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
> hub 3-0:1.0: USB hub found
> hub 3-0:1.0: 5 ports detected
> e100: Intel(R) PRO/100 Network Driver, 3.4.8-k2-NAPI
> e100: Copyright(c) 1999-2005 Intel Corporation
> PCI: Enabling device: (0001:c0:01.0), cmd 143
> e100: eth0: e100_probe: addr 0x401e8030000, irq 163, MAC addr 00:0D:60:0B:40:67
> PCI: Enabling device: (0001:d8:01.0), cmd 143
> e100: eth1: e100_probe: addr 0x401c0030000, irq 169, MAC addr 00:0D:60:0B:40:6A
> Intel(R) PRO/1000 Network Driver - version 6.0.54-k2
> Copyright (c) 1999-2004 Intel Corporation.
> PCI: Enabling device: (0001:c8:01.0), cmd 143
> usb 2-1: new low speed USB device using ohci_hcd and address 3
> e1000: eth2: e1000_probe: Intel(R) PRO/1000 Network Connection
> PCI: Enabling device: (0001:c8:01.1), cmd 143
> e1000: eth3: e1000_probe: Intel(R) PRO/1000 Network Connection
> SCSI subsystem initialized
> ipr: IBM Power RAID SCSI Device Driver version: 2.0.13 (February 21, 2005)
> ipr 0000:d0:01.0: Found IOA with IRQ: 135
> ipr 0000:d0:01.0: Starting IOA initialization sequence.
> ipr 0000:d0:01.0: Adapter firmware version: 03090061
> ipr 0000:d0:01.0: IOA initialized.
> scsi0 : IBM 5703 Storage Adapter
>   Vendor: IBM       Model: IC35L036UCDY10-0  Rev: S28G
>   Type:   Direct-Access                      ANSI SCSI revision: 03
>   Vendor: IBM       Model: IC35L036UCDY10-0  Rev: S28G
>   Type:   Direct-Access                      ANSI SCSI revision: 03
>   Vendor: IBM       Model: VSBPD4E2  U4SCSI  Rev: 5105
>   Type:   Enclosure                          ANSI SCSI revision: 02
> scsi: unknown device type 31
>   Vendor: IBM       Model: 5703001           Rev: 0150
>   Type:   Unknown                            ANSI SCSI revision: 00
> ipr 0001:d0:01.0: Found IOA with IRQ: 167
> ipr 0001:d0:01.0: Starting IOA initialization sequence.
> ipr 0001:d0:01.0: Adapter firmware version: 020A0057
> ipr 0001:d0:01.0: IOA initialized.
> scsi1 : IBM 570B Storage Adapter
>   Vendor: IBM       Model: DDS Gen5          Rev: V314
>   Type:   Sequential-Access                  ANSI SCSI revision: 02
>   Vendor: IBM       Model: IC35L036UCDY10-0  Rev: S28G
>   Type:   Direct-Access                      ANSI SCSI revision: 03
>   Vendor: IBM       Model: IC35L036UCDY10-0  Rev: S28G
>   Type:   Direct-Access                      ANSI SCSI revision: 03
>   Vendor: IBM       Model: VSBPD4E1  U4SCSI  Rev: 4770
>   Type:   Enclosure                          ANSI SCSI revision: 02
> scsi: unknown device type 31
>   Vendor: IBM       Model: 570B001           Rev: 0150
>   Type:   Unknown                            ANSI SCSI revision: 00
> SCSI device sda: 71096640 512-byte hdwr sectors (36401 MB)
> SCSI device sda: drive cache: write through
> SCSI device sda: 71096640 512-byte hdwr sectors (36401 MB)
> SCSI device sda: drive cache: write through
>  /dev/scsi/host0/bus0/target5/lun0: p1 p2 p3
> Attached scsi disk sda at scsi0, channel 0, id 5, lun 0
> SCSI device sdb: 71096640 512-byte hdwr sectors (36401 MB)
> SCSI device sdb: drive cache: write through
> SCSI device sdb: 71096640 512-byte hdwr sectors (36401 MB)
> SCSI device sdb: drive cache: write through
>  /dev/scsi/host0/bus0/target8/lun0:
> Attached scsi disk sdb at scsi0, channel 0, id 8, lun 0
> SCSI device sdc: 71096640 512-byte hdwr sectors (36401 MB)
> SCSI device sdc: drive cache: write through
> SCSI device sdc: 71096640 512-byte hdwr sectors (36401 MB)
> SCSI device sdc: drive cache: write through
>  /dev/scsi/host1/bus0/target5/lun0:
> Attached scsi disk sdc at scsi1, channel 0, id 5, lun 0
> SCSI device sdd: 71096640 512-byte hdwr sectors (36401 MB)
> SCSI device sdd: drive cache: write through
> SCSI device sdd: 71096640 512-byte hdwr sectors (36401 MB)
> SCSI device sdd: drive cache: write through
>  /dev/scsi/host1/bus0/target8/lun0:
> Attached scsi disk sdd at scsi1, channel 0, id 8, lun 0
> kjournald starting.  Commit interval 5 seconds
> EXT3-fs: mounted filesystem with ordered data mode.
> Adding 3905528k swap on /dev/sda3.  Priority:-1 extents:1
> EXT3 FS on sda2, internal journal
> PDC20275: IDE controller at PCI slot 0000:cc:01.0
> PCI: Enabling device: (0000:cc:01.0), cmd 3
> PDC20275: chipset revision 1
> PDC20275: 100% native mode on irq 134
>     ide2: BM-DMA at 0xeec00-0xeec07, BIOS settings: hde:pio, hdf:pio
>     ide3: BM-DMA at 0xeec08-0xeec0f, BIOS settings: hdg:pio, hdh:pio
> Probing IDE interface ide2...
> hde: IBM DROM00205, ATAPI CD/DVD-ROM drive
> ide2 at 0xee400-0xee407,0xedc02 on irq 134
> Probing IDE interface ide3...
> eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
> eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw at saw.sw.com.sg> and others
> usbcore: registered new driver hiddev
> input: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-0000:c8:01.1-1
> input,hiddev0: USB HID v1.10 Mouse [NOVATEK USB Keyboard] on usb-0000:c8:01.1-1
> usbcore: registered new driver usbhid
> drivers/usb/input/hid-core.c: v2.01:USB HID core driver
> ts: Compaq touchscreen protocol output
> e1000: eth2: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex
> NET: Registered protocol family 17
> RTAS: event: 14, Type: Dump Notification Event, Severity: 2
> NET: Registered protocol family 10
> Disabled Privacy Extensions on device c000000000431c50(lo)
> IPv6 over IPv4 tunneling driver
> eth2: no IPv6 routers present

> _______________________________________________
> Debian-ppc64-devel mailing list
> Debian-ppc64-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/debian-ppc64-devel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/debian-ppc64-devel/attachments/20050914/2b9bb6d1/attachment.pgp


More information about the Debian-ppc64-devel mailing list