Fedora 11 (Leonidas) was released today. I installed it on PS3 without trouble, and it works OK. Below are a few notes from my install.
Please report any Fedora installer or Fedora package bugs here:
I put a new release of the PS3 petitboot bootloader that I tested with Fedora 11 here:
http://www.kernel.org/pub/linux/kernel/people/geoff/cell/ps3-petitboot/
** F11 Installer Startup Notes
* Most users can just use Fedora-11-ppc-netinst.iso or Fedora-11-ppc-DVD.iso and the default startup options.
* Petitboot doesn't yet support removable media notifications, so to boot the installer, insert the CD or DVD into the drive on startup before petitboot starts.
* The PS3 is a 64 bit machine, so choose the linux64 bootloader menu item.
* The 'text' mode of the installer has changed in Fedora-11, and now only installs a very minimal system. It is recommended to not use text install.
* When using the askmethod option, do to the limited memory of the PS3 anaconda's stage2 image cannot be loaded using http (the URL method). Only Local CD/DVD, Hard drive, or NFS directory will work.
** F11 Installer Partitioning Notes
* The default partition option 'Replace existing Linux system' works OK.
* The PS3 must have a swap partition setup during install. Otherwise, there will be an installer out of memory error. 'Replace existing Linux system' will create a swap partition for you.
* The partition option 'Create Custom Layout' works OK. Use this if you want a two partition system with ps3da1 as / and ps3da2 as swap.
Recent petitboot releases support booting from ext3 and ext4 filesystems, so the root filesystem can be either. A separate ext3 /boot partition is not needed.
* The partition option 'Encrypt system' currently does not work on PS3 (installer out of memory error).
* Other partition options should work.
-Geoff
Geoff Levand wrote:
Fedora 11 (Leonidas) was released today. I installed it on PS3 without trouble, and it works OK. Below are a few notes from my install.
Please report any Fedora installer or Fedora package bugs here:
I put a new release of the PS3 petitboot bootloader that I tested with Fedora 11 here:
http://www.kernel.org/pub/linux/kernel/people/geoff/cell/ps3-petitboot/
Hi,
I've just tried this version of petitboot and I've noticed that my wireless USB keyboard does not work (I had to use the PS3 controller). This is the first time I've tried petitboot. Before I was using kboot (I think) and the keyboard has always worked.
Does it make sense to you?
Andrea
On 06/12/2009 11:31 AM, Andrea wrote:
Geoff Levand wrote:
Fedora 11 (Leonidas) was released today. I installed it on PS3 without trouble, and it works OK. Below are a few notes from my install.
Please report any Fedora installer or Fedora package bugs here:
I put a new release of the PS3 petitboot bootloader that I tested with Fedora 11 here:
http://www.kernel.org/pub/linux/kernel/people/geoff/cell/ps3-petitboot/
Hi,
I've just tried this version of petitboot and I've noticed that my wireless USB keyboard does not work (I had to use the PS3 controller). This is the first time I've tried petitboot. Before I was using kboot (I think) and the keyboard has always worked.
What is the make and model of that keyboard? What is the output of lsusb? What is the output of /ver/log/messages when it is plugged in to petitboot? What is the output of /ver/log/messages when it is plugged in to a working system?
-Geoff
Geoff Levand wrote:
What is the make and model of that keyboard?
I guess it is Bus 003 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
What is the output of lsusb?
This is the output when connected to my Linux laptop (working)
Bus 003 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046d Logitech, Inc. idProduct 0xc517 LX710 Cordless Desktop Laser bcdDevice 38.10 iManufacturer 1 Logitech iProduct 2 USB Receiver iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 59 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 98mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 59 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 177 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Device Status: 0x0000 (Bus Powered)
What is the output of /ver/log/messages when it is plugged in to petitboot?
How do I do that? How do I control the PS3 without keyboard?
What is the output of /ver/log/messages when it is plugged in to a working system?
Jun 12 20:54:26 thinkpad kernel: usb 3-2: new low speed USB device using uhci_hcd and address 3 Jun 12 20:54:26 thinkpad kernel: usb 3-2: New USB device found, idVendor=046d, idProduct=c517 Jun 12 20:54:26 thinkpad kernel: usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 12 20:54:26 thinkpad kernel: usb 3-2: Product: USB Receiver Jun 12 20:54:26 thinkpad kernel: usb 3-2: Manufacturer: Logitech Jun 12 20:54:26 thinkpad kernel: usb 3-2: configuration #1 chosen from 1 choice Jun 12 20:54:26 thinkpad kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input9 Jun 12 20:54:26 thinkpad kernel: logitech 0003:046D:C517.0002: input,hidraw1: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:1d.1-2/input0 Jun 12 20:54:26 thinkpad kernel: logitech 0003:046D:C517.0003: fixing up Logitech keyboard report descriptor Jun 12 20:54:26 thinkpad kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.1/input/input10 Jun 12 20:54:26 thinkpad kernel: logitech 0003:046D:C517.0003: input,hiddev96,hidraw2: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:1d.1-2/input1
-Geoff
On 06/12/2009 12:58 PM, Andrea wrote:
Geoff Levand wrote:
What is the make and model of that keyboard?
I guess it is Bus 003 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
What is the output of /ver/log/messages when it is plugged in to petitboot?
How do I do that? How do I control the PS3 without keyboard?
You can use telnet. You'll need to set the bootloader telnet enabled flag, which is not set by default. You can do that by booting into petitboot with a working keyboard and use:
ps3-bl-option --set-telnet-enabled 1
or boot into a distro and use:
ps3-flash-util --db-write-half 3 3 1
What is the output of /ver/log/messages when it is plugged in to a working system?
Jun 12 20:54:26 thinkpad kernel: usb 3-2: new low speed USB device using uhci_hcd and address 3 Jun 12 20:54:26 thinkpad kernel: usb 3-2: New USB device found, idVendor=046d, idProduct=c517 Jun 12 20:54:26 thinkpad kernel: usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 12 20:54:26 thinkpad kernel: usb 3-2: Product: USB Receiver Jun 12 20:54:26 thinkpad kernel: usb 3-2: Manufacturer: Logitech Jun 12 20:54:26 thinkpad kernel: usb 3-2: configuration #1 chosen from 1 choice Jun 12 20:54:26 thinkpad kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input9 Jun 12 20:54:26 thinkpad kernel: logitech 0003:046D:C517.0002: input,hidraw1: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:1d.1-2/input0 Jun 12 20:54:26 thinkpad kernel: logitech 0003:046D:C517.0003: fixing up Logitech keyboard report descriptor Jun 12 20:54:26 thinkpad kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.1/input/input10 Jun 12 20:54:26 thinkpad kernel: logitech 0003:046D:C517.0003: input,hiddev96,hidraw2: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:1d.1-2/input1
-Geoff
On 06/12/2009 12:58 PM, Andrea wrote:
Geoff Levand wrote:
What is the make and model of that keyboard?
I guess it is Bus 003 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
After looking into it, it seems this keyboard needs CONFIG_HID_LOGITECH set. The current petitboot kernel does not have this.
I made a test build (rotated only). Please try it and report.
http://www.kernel.org/pub/linux/kernel/people/geoff/cell/ps3-petitboot/testi...
-Geoff
Geoff Levand wrote:
On 06/12/2009 12:58 PM, Andrea wrote:
Geoff Levand wrote:
What is the make and model of that keyboard?
I guess it is Bus 003 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
After looking into it, it seems this keyboard needs CONFIG_HID_LOGITECH set. The current petitboot kernel does not have this.
I made a test build (rotated only). Please try it and report.
http://www.kernel.org/pub/linux/kernel/people/geoff/cell/ps3-petitboot/testi...
-Geoff
You were right. I tested it and it works.
Thanks
Andrea
Geoff Levand wrote:
On 06/12/2009 11:31 AM, Andrea wrote:
Geoff Levand wrote:
Fedora 11 (Leonidas) was released today. I installed it on PS3 without trouble, and it works OK. Below are a few notes from my install.
Please report any Fedora installer or Fedora package bugs here:
I put a new release of the PS3 petitboot bootloader that I tested with Fedora 11 here:
http://www.kernel.org/pub/linux/kernel/people/geoff/cell/ps3-petitboot/
Hi,
I've just tried this version of petitboot and I've noticed that my wireless USB keyboard does not work (I had to use the PS3 controller). This is the first time I've tried petitboot. Before I was using kboot (I think) and the keyboard has always worked.
What is the make and model of that keyboard? What is the output of lsusb? What is the output of /ver/log/messages when it is plugged in to petitboot? What is the output of /ver/log/messages when it is plugged in to a working system?
-Geoff
Did anybody have time to read the output I sent earlier? I guess that for the time being I will revert to kboot.
Let me know if I can provide extra info.
Andrea
Geoff Levand wrote:
On 06/12/2009 11:31 AM, Andrea wrote:
Geoff Levand wrote:
What is the make and model of that keyboard? What is the output of lsusb? What is the output of /ver/log/messages when it is plugged in to petitboot?
root@ps3-linux:/# cat /var/log/messages
Jun 23 20:32:55 ps3-linux user.info kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Jun 23 20:32:55 ps3-linux user.info kernel: dma_sb_region_create_linear:984: forcing 16M pages for linear map Jun 23 20:32:55 ps3-linux user.info kernel: ps3-ehci-driver sb_05: new USB bus registered, assigned bus number 1 Jun 23 20:32:55 ps3-linux user.info kernel: usb usb1: configuration #1 chosen from 1 choice
Jun 23 20:32:55 ps3-linux user.info kernel: ps3-ehci-driver sb_07: irq 32, io mem 0x400000070000
Jun 23 20:32:55 ps3-linux user.info kernel: hub 2-0:1.0: 2 ports detected
Jun 23 20:32:55 ps3-linux user.info kernel: ps3_system_bus_match:360: dev=2.0(sb_06), drv=2.0(ps3-ohci-driver): match Jun 23 20:32:55 ps3-linux user.info kernel: ps3-ohci-driver sb_06: PS3 OHCI Host Controller
Jun 23 20:32:55 ps3-linux user.info kernel: usb usb3: configuration #1 chosen from 1 choice
Jun 23 20:32:55 ps3-linux user.info kernel: ps3_system_bus_match:360: dev=2.0(sb_08), drv=2.0(ps3-ohci-driver): match Jun 23 20:32:55 ps3-linux user.info kernel: -> dma_sb_region_create:652:
Jun 23 20:32:55 ps3-linux user.info sysinit: udhcpc (v1.13.4) started
Jun 23 20:32:56 ps3-linux user.info sysinit: pb-event: waiting for server 10
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop2 (2 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: EXT3-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop2 (2 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: EXT4-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop2 (2 > 0)
Jun 23 20:32:56 ps3-linux user.warn kernel: EXT2-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop2 (1 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: FAT: unable to read boot sector
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop2 (1 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: FAT: unable to read boot sector
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop2 (2 > 0)
Jun 23 20:32:56 ps3-linux user.warn kernel: isofs_fill_super: bread failed, dev=loop2, iso_blknum=16, block=32 Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop1 (2 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: EXT3-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop1 (2 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: EXT4-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop1 (2 > 0)
Jun 23 20:32:56 ps3-linux user.warn kernel: EXT2-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop1 (1 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: FAT: unable to read boot sector
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop1 (1 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: FAT: unable to read boot sector
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop1 (2 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop3 (2 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: EXT3-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop3 (2 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: EXT4-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop3 (2 > 0)
Jun 23 20:32:56 ps3-linux user.warn kernel: EXT2-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop3 (1 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: FAT: unable to read boot sector
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop3 (1 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: FAT: unable to read boot sector
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop3 (2 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop0 (2 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: EXT3-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop0 (2 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: EXT4-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop0 (2 > 0)
Jun 23 20:32:56 ps3-linux user.warn kernel: EXT2-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop0 (1 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: FAT: unable to read boot sector
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop0 (1 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: FAT: unable to read boot sector
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop0 (2 > 0)
Jun 23 20:32:56 ps3-linux user.info kernel: kjournald starting. Commit interval 5 seconds
Jun 23 20:32:56 ps3-linux user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop5 (2 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: EXT3-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop5 (2 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: EXT4-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop5 (2 > 0)
Jun 23 20:32:56 ps3-linux user.warn kernel: EXT2-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop5 (1 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: FAT: unable to read boot sector
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop5 (1 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: FAT: unable to read boot sector
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop5 (2 > 0)
Jun 23 20:32:56 ps3-linux user.warn kernel: isofs_fill_super: bread failed, dev=loop5, iso_blknum=16, block=32 Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop4 (2 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: EXT3-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop4 (2 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: EXT4-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop4 (2 > 0)
Jun 23 20:32:56 ps3-linux user.warn kernel: EXT2-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop4 (1 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: FAT: unable to read boot sector
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop4 (1 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: FAT: unable to read boot sector
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop4 (2 > 0)
Jun 23 20:32:56 ps3-linux user.warn kernel: isofs_fill_super: bread failed, dev=loop4, iso_blknum=16, block=32 Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop6 (2 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: EXT3-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop6 (2 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: EXT4-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop6 (2 > 0)
Jun 23 20:32:56 ps3-linux user.warn kernel: EXT2-fs: unable to read superblock
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop6 (1 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: FAT: unable to read boot sector
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop6 (1 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: FAT: unable to read boot sector
Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop6 (2 > 0)
Jun 23 20:32:56 ps3-linux user.warn kernel: isofs_fill_super: bread failed, dev=loop6, iso_blknum=16, block=32 Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop7 (2 > 0)
Jun 23 20:32:56 ps3-linux user.err kernel: EXT3-fs: unable to read superblock Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop7 (2 > 0) Jun 23 20:32:56 ps3-linux user.err kernel: EXT4-fs: unable to read superblock Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop7 (2 > 0) Jun 23 20:32:56 ps3-linux user.warn kernel: EXT2-fs: unable to read superblock Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop7 (1 > 0) Jun 23 20:32:56 ps3-linux user.err kernel: FAT: unable to read boot sector Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop7 (1 > 0) Jun 23 20:32:56 ps3-linux user.err kernel: FAT: unable to read boot sector Jun 23 20:32:56 ps3-linux user.err kernel: bio too big device loop7 (2 > 0) Jun 23 20:32:56 ps3-linux user.warn kernel: isofs_fill_super: bread failed, dev=loop7, iso_blknum=16, block=32 Jun 23 20:32:57 ps3-linux user.info sysinit: pb-event: wrote 30 bytes Jun 23 20:32:57 ps3-linux user.info sysinit: Sending discover... Jun 23 20:32:57 ps3-linux authpriv.info dropbear[1163]: Running in background Jun 23 20:33:00 ps3-linux user.info sysinit: Sending discover... Jun 23 20:33:00 ps3-linux user.info sysinit: Sending select for 192.168.3.14... Jun 23 20:33:00 ps3-linux user.info sysinit: Lease of 192.168.3.14 obtained, lease time 43200 Jun 23 20:33:00 ps3-linux user.info sysinit: udhcpc: ifconfig eth0 192.168.3.14 netmask 255.255.255.0 broadcast 192.168.3.255 Jun 23 20:33:00 ps3-linux user.info sysinit: udhcpc: setting default routers: 192.168.3.1 Jun 23 20:33:00 ps3-linux user.info sysinit: udhcpc: setting dns servers: 192.168.3.1 Jun 23 20:33:00 ps3-linux user.info sysinit: pb-event: wrote 88 bytes Jun 23 20:33:00 ps3-linux user.err kernel: ps3av_do_pkt: ps3av_send_cmd_pkt() failed (result=-11) Jun 23 20:33:00 ps3-linux user.err kernel: ps3av_do_pkt: failed cid:10003 res:-11
and this is dmesg
root@ps3-linux:/# dmesg
Using PS3 machine description
Page orders: linear mapping = 24, virtual = 12, io = 12
CPU maps initialized for 2 threads per core
(thread shift is 1)
Starting Linux PPC64 #3 SMP Tue Jun 9 11:59:58 PDT 2009
-----------------------------------------------------
ppc64_pft_size = 0x14
physicalMemorySize = 0x8000000
htab_hash_mask = 0x1fff
-----------------------------------------------------
Linux version 2.6.28.10 (geoff@white) (gcc version 4.3.3 (GCC) ) #3 SMP Tue Jun 9 11:59:58 PDT 2009
*** 0000 : CF000012
*** 0000 : Setup Arch [boot]0012 Setup Arch PS3 firmware version 2.7.6 ps3fb videomemory: 9437184 bytes at c000000001100000 ps3flash bounce buffer: 262144 bytes at c000000001a00000 Top of RAM: 0x8000000, Total RAM: 0x8000000 Memory hole size: 0MB Zone PFN ranges: DMA 0x00000000 -> 0x00008000 Normal 0x00008000 -> 0x00008000 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0: 0x00000000 -> 0x00008000 On node 0 totalpages: 32768 DMA zone: 448 pages used for memmap DMA zone: 0 pages reserved DMA zone: 32320 pages, LIFO batch:7 Normal zone: 0 pages used for memmap Movable zone: 0 pages used for memmap *** 0000 : CF000015
*** 0000 : Setup Done [boot]0015 Setup Done Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32320 Kernel command line: PID hash table entries: 512 (order: 9, 4096 bytes) time_init: decrementer frequency = 79.800000 MHz time_init: processor frequency = 3192.000000 MHz clocksource: timebase mult[3220149] shift[22] registered clockevent: decrementer mult[146d] shift[16] cpu[0] Console: colour dummy device 80x25 console [tty0] enabled Dentry cache hash table entries: 16384 (order: 5, 131072 bytes) Inode-cache hash table entries: 8192 (order: 4, 65536 bytes) Memory: 112316k/131072k available (5960k kernel code, 18612k reserved, 632k data, 228k bss, 1656k init) Calibrating delay loop... 159.23 BogoMIPS (lpj=318464) Mount-cache hash table entries: 256 clockevent: decrementer mult[146d] shift[16] cpu[1] Processor 1 found. Brought up 2 CPUs net_namespace: 552 bytes NET: Registered protocol family 16 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb Bluetooth: Core ver 2.13 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized cfg80211: Using static regulatory domain info cfg80211: Regulatory domain: US (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm) (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm) cfg80211: Calling CRDA for country: US NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 1, 8192 bytes) TCP established hash table entries: 4096 (order: 4, 65536 bytes) TCP bind hash table entries: 4096 (order: 4, 65536 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP reno registered NET: Registered protocol family 1 ps3_system_bus_match:360: dev=4.0(vuart_01), drv=4.0(ps3_av): match msgmni has been set to 443 alg: No test for stdrng (krng) io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered ps3_system_bus_match:360: dev=10.1(ioc0_01), drv=10.1(ps3fb): match ps3_system_bus_match:360: dev=10.1(ioc0_01), drv=10.1(ps3fb): match Console: switching to colour frame buffer device 140x40 ps3fb ioc0_01: graphics fb0, using 9152 KiB of video memory ps3_system_bus_match:360: dev=8.0(sb_01), drv=8.0(ps3flash): match ps3_system_bus_match:360: dev=8.0(sb_01), drv=8.0(ps3flash): match -> dma_sb_region_create:652: ps3flash sb_01: First accessible region has index 5 start 473600 size 8192 ps3flash sb_01: ps3flash_probe:388: registered misc device 63 ps3disk_init:585: registered block device major 254 ps3_system_bus_match:360: dev=6.0(sb_03), drv=6.0(ps3disk): match ps3_system_bus_match:360: dev=6.0(sb_03), drv=6.0(ps3disk): match -> dma_sb_region_create:652: ps3disk sb_03: First accessible region has index 3 start 25165848 size 52974312 ps3disk sb_03: ps3da is a ST9402115AS (38154 MiB total, 25866 MiB for OtherOS) ps3da: ps3da1 ps3da2 brd: module loaded loop: module loaded ps3_system_bus_match:360: dev=3.0(sb_04), drv=3.0(ps3_gelic_driver): match ps3_system_bus_match:360: dev=3.0(sb_04), drv=3.0(ps3_gelic_driver): match dma_sb_region_create_linear:984: forcing 16M pages for linear map -> dma_sb_region_create:652: ps3_gelic_driver sb_04: internal vlan enabled ps3_gelic_driver sb_04: eth0: MAC addr 00:19:c5:f3:2f:d2 ps3_system_bus_match:360: dev=7.0(sb_02), drv=7.0(ps3rom): match ps3_system_bus_match:360: dev=7.0(sb_02), drv=7.0(ps3rom): match -> dma_sb_region_create:652: scsi0 : ps3rom scsi 0:0:0:0: CD-ROM SONY PS-SYSTEM 302R 4109 PQ: 0 ANSI: 0 Driver 'sd' needs updating - please use bus_type methods Driver 'sr' needs updating - please use bus_type methods sr0: scsi3-mmc drive: 0x/0x cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 0:0:0:0: Attached scsi CD-ROM sr0 ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ps3_system_bus_match:360: dev=1.0(sb_05), drv=1.0(ps3-ehci-driver): match ps3_system_bus_match:360: dev=1.0(sb_05), drv=1.0(ps3-ehci-driver): match dma_sb_region_create_linear:984: forcing 16M pages for linear map -> dma_sb_region_create:652: ps3-ehci-driver sb_05: PS3 EHCI Host Controller ps3-ehci-driver sb_05: new USB bus registered, assigned bus number 1 ps3-ehci-driver sb_05: irq 31, io mem 0x400000060000 ps3-ehci-driver sb_05: USB 0.0 started, EHCI 1.00 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected ps3_system_bus_match:360: dev=1.0(sb_07), drv=1.0(ps3-ehci-driver): match ps3_system_bus_match:360: dev=1.0(sb_07), drv=1.0(ps3-ehci-driver): match dma_sb_region_create_linear:984: forcing 16M pages for linear map -> dma_sb_region_create:652: ps3-ehci-driver sb_07: PS3 EHCI Host Controller ps3-ehci-driver sb_07: new USB bus registered, assigned bus number 2 ps3-ehci-driver sb_07: irq 32, io mem 0x400000070000 ps3-ehci-driver sb_07: USB 0.0 started, EHCI 1.00 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver ps3_system_bus_match:360: dev=2.0(sb_06), drv=2.0(ps3-ohci-driver): match ps3_system_bus_match:360: dev=2.0(sb_06), drv=2.0(ps3-ohci-driver): match dma_sb_region_create_linear:984: forcing 16M pages for linear map -> dma_sb_region_create:652: ps3-ohci-driver sb_06: PS3 OHCI Host Controller ps3-ohci-driver sb_06: new USB bus registered, assigned bus number 3 ps3-ohci-driver sb_06: irq 33, io mem 0x400000080000 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected ps3_system_bus_match:360: dev=2.0(sb_08), drv=2.0(ps3-ohci-driver): match ps3_system_bus_match:360: dev=2.0(sb_08), drv=2.0(ps3-ohci-driver): match dma_sb_region_create_linear:984: forcing 16M pages for linear map -> dma_sb_region_create:652: ps3-ohci-driver sb_08: PS3 OHCI Host Controller ps3-ohci-driver sb_08: new USB bus registered, assigned bus number 4 ps3-ohci-driver sb_08: irq 34, io mem 0x400000090000 usb 1-2: new high speed USB device using ps3-ehci-driver and address 2 usb 1-2: configuration #1 chosen from 1 choice hub 1-2:1.0: USB hub found hub 1-2:1.0: 4 ports detected usb usb4: configuration #1 chosen from 1 choice hub 4-0:1.0: USB hub found hub 4-0:1.0: 2 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mice: PS/2 mouse device common for all mice Bluetooth: Generic Bluetooth USB driver ver 0.3 usbcore: registered new interface driver btusb usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver ps3_system_bus_match:360: dev=5.0(vuart_02), drv=5.0(ps3_sys_manager): match ps3_system_bus_match:360: dev=5.0(vuart_02), drv=5.0(ps3_sys_manager): match TCP westwood registered NET: Registered protocol family 17 Bluetooth: L2CAP ver 2.11 Bluetooth: L2CAP socket layer initialized Bluetooth: SCO (Voice Link) ver 0.6 Bluetooth: SCO socket layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.10 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: HIDP (Human Interface Emulation) ver 1.2 RPC: Registered udp transport module. RPC: Registered tcp transport module. Freeing unused kernel memory: 1656k freed usb 2-2: new high speed USB device using ps3-ehci-driver and address 2 usb 2-2: configuration #1 chosen from 1 choice usb 1-2.1: new low speed USB device using ps3-ehci-driver and address 3 usb 1-2.1: configuration #1 chosen from 1 choice bio too big device loop2 (2 > 0) EXT3-fs: unable to read superblock bio too big device loop2 (2 > 0) EXT4-fs: unable to read superblock bio too big device loop2 (2 > 0) EXT2-fs: unable to read superblock bio too big device loop2 (1 > 0) FAT: unable to read boot sector bio too big device loop2 (1 > 0) FAT: unable to read boot sector bio too big device loop2 (2 > 0) isofs_fill_super: bread failed, dev=loop2, iso_blknum=16, block=32 bio too big device loop1 (2 > 0) EXT3-fs: unable to read superblock bio too big device loop1 (2 > 0) EXT4-fs: unable to read superblock bio too big device loop1 (2 > 0) EXT2-fs: unable to read superblock bio too big device loop1 (1 > 0) FAT: unable to read boot sector bio too big device loop1 (1 > 0) FAT: unable to read boot sector bio too big device loop1 (2 > 0) isofs_fill_super: bread failed, dev=loop1, iso_blknum=16, block=32 bio too big device loop3 (2 > 0) EXT3-fs: unable to read superblock bio too big device loop3 (2 > 0) EXT4-fs: unable to read superblock bio too big device loop3 (2 > 0) EXT2-fs: unable to read superblock bio too big device loop3 (1 > 0) FAT: unable to read boot sector bio too big device loop3 (1 > 0) FAT: unable to read boot sector bio too big device loop3 (2 > 0) isofs_fill_super: bread failed, dev=loop3, iso_blknum=16, block=32 bio too big device loop0 (2 > 0) EXT3-fs: unable to read superblock bio too big device loop0 (2 > 0) EXT4-fs: unable to read superblock bio too big device loop0 (2 > 0) EXT2-fs: unable to read superblock bio too big device loop0 (1 > 0) FAT: unable to read boot sector bio too big device loop0 (1 > 0) FAT: unable to read boot sector bio too big device loop0 (2 > 0) isofs_fill_super: bread failed, dev=loop0, iso_blknum=16, block=32 kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. bio too big device loop5 (2 > 0) EXT3-fs: unable to read superblock bio too big device loop5 (2 > 0) EXT4-fs: unable to read superblock bio too big device loop5 (2 > 0) EXT2-fs: unable to read superblock bio too big device loop5 (1 > 0) FAT: unable to read boot sector bio too big device loop5 (1 > 0) FAT: unable to read boot sector bio too big device loop5 (2 > 0) isofs_fill_super: bread failed, dev=loop5, iso_blknum=16, block=32 bio too big device loop4 (2 > 0) EXT3-fs: unable to read superblock bio too big device loop4 (2 > 0) EXT4-fs: unable to read superblock bio too big device loop4 (2 > 0) EXT2-fs: unable to read superblock bio too big device loop4 (1 > 0) FAT: unable to read boot sector bio too big device loop4 (1 > 0) FAT: unable to read boot sector bio too big device loop4 (2 > 0) isofs_fill_super: bread failed, dev=loop4, iso_blknum=16, block=32 bio too big device loop6 (2 > 0) EXT3-fs: unable to read superblock bio too big device loop6 (2 > 0) EXT4-fs: unable to read superblock bio too big device loop6 (2 > 0) EXT2-fs: unable to read superblock bio too big device loop6 (1 > 0) FAT: unable to read boot sector bio too big device loop6 (1 > 0) FAT: unable to read boot sector bio too big device loop6 (2 > 0) isofs_fill_super: bread failed, dev=loop6, iso_blknum=16, block=32 bio too big device loop7 (2 > 0) EXT3-fs: unable to read superblock bio too big device loop7 (2 > 0) EXT4-fs: unable to read superblock bio too big device loop7 (2 > 0) EXT2-fs: unable to read superblock bio too big device loop7 (1 > 0) FAT: unable to read boot sector bio too big device loop7 (1 > 0) FAT: unable to read boot sector bio too big device loop7 (2 > 0) isofs_fill_super: bread failed, dev=loop7, iso_blknum=16, block=32 ps3av_do_pkt: ps3av_send_cmd_pkt() failed (result=-11) ps3av_do_pkt: failed cid:10003 res:-11
What is the output of /ver/log/messages when it is plugged in to a working system?
-Geoff
On 06/23/2009 01:46 PM, Andrea wrote:
Geoff Levand wrote:
What is the output of /ver/log/messages when it is plugged in to petitboot?
root@ps3-linux:/# cat /var/log/messages
Jun 23 20:32:55 ps3-linux user.info kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
I don't see any mention of your keyboard in there...
Sorry I wasn't clear, but what I wanted was for you to do this:
1) start the system without the keyboard plugged in 2) log in with telnet 3) type 'tail -f /var/log/messages' 4) make a note where the output is, maybe type '---------' 5) plug in the keyboard 6) cut and past the output since the --------- mark
-Geoff
-
Andrea -
Geoff Levand