32 Replies Latest reply on Apr 14, 2016 6:25 PM by icepuck

    RPI 3 nousb

    icepuck

      I recently got a pi 3 with the 7" touch screen. I set it up with berryboot and installed jessie. I got to were I needed to use a keyboard and that is when I found out the usb ports didn't work.

      I went through the following link to try to fix it but nothing there helped.

      https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=53832

       

      I've tried keyboards and mice from working linux computers, I even tried a powered usb hub and nothing. I've tried running without the touch screen(via ssh) nothing is recognized.

      I've tried power supplies from my other pi's with change. Do I need to post dmesg output? Is it possible I got a bum Pi?

      -dan

        • Re: RPI 3 nousb
          icepuck

          Here's the dmesg output. I couldn't figure out how to copy just the errors but I managed to copy the whole listing.

           

          pi@raspberrypi:~ $ dmesg

          [    0.000000] Booting Linux on physical CPU 0x0

          [    0.000000] Initializing cgroup subsys cpuset

          [    0.000000] Initializing cgroup subsys cpu

          [    0.000000] Initializing cgroup subsys cpuacct

          [    0.000000] Linux version 4.1.19-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #858 SMP Tue Mar 15 15:56:00 GMT 2016

          [    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d

          [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache

          [    0.000000] Machine model: Raspberry Pi 3 Model B Rev 1.2

          [    0.000000] cma: Reserved 8 MiB at 0x3a400000

          [    0.000000] Memory policy: Data cache writealloc

          [    0.000000] On node 0 totalpages: 241664

          [    0.000000] free_area_init_node: node 0, pgdat 80880fc0, node_mem_map b9bb4000

          [    0.000000]   Normal zone: 2124 pages used for memmap

          [    0.000000]   Normal zone: 0 pages reserved

          [    0.000000]   Normal zone: 241664 pages, LIFO batch:31

          [    0.000000] [bcm2709_smp_init_cpus] enter (9420->f3003010)

          [    0.000000] [bcm2709_smp_init_cpus] ncores=4

          [    0.000000] PERCPU: Embedded 12 pages/cpu @bafb0000 s20416 r8192 d20544 u49152

          [    0.000000] pcpu-alloc: s20416 r8192 d20544 u49152 alloc=12*4096

          [    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3

          [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 239540

          [    0.000000] Kernel command line: 8250.nr_uarts=1 dma.dmachans=0x7f35 bcm2708_fb.fbwidth=800 bcm2708_fb.fbheight=480 bcm2709.boardrev=0xa22082 bcm2709.serial=0x10b7a724 smsc95xx.macaddr=B8:27:EB:B7:A7:24 bcm2708_fb.fbswap=1 bcm2709.uart_clock=48000000 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p7 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait

          [    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)

          [    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)

          [    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)

          [    0.000000] Memory: 939376K/966656K available (6064K kernel code, 534K rwdata, 1664K rodata, 444K init, 757K bss, 19088K reserved, 8192K cma-reserved)

          [    0.000000] Virtual kernel memory layout:

              vector  : 0xffff0000 - 0xffff1000   (   4 kB)

              fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)

              vmalloc : 0xbb800000 - 0xff000000   (1080 MB)

              lowmem  : 0x80000000 - 0xbb000000   ( 944 MB)

              modules : 0x7f000000 - 0x80000000   (  16 MB)

                .text : 0x80008000 - 0x807945f0   (7730 kB)

                .init : 0x80795000 - 0x80804000   ( 444 kB)

                .data : 0x80804000 - 0x80889b10   ( 535 kB)

                 .bss : 0x8088c000 - 0x809497dc   ( 758 kB)

          [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1

          [    0.000000] Hierarchical RCU implementation.

          [    0.000000] Additional per-CPU info printed with stalls.

          [    0.000000] NR_IRQS:608

          [    0.000000] Architected cp15 timer(s) running at 19.20MHz (phys).

          [    0.000000] clocksource arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns

          [    0.000009] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns

          [    0.000026] Switching to timer-based delay loop, resolution 52ns

          [    0.000248] Console: colour dummy device 80x30

          [    0.001292] console [tty1] enabled

          [    0.001346] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)

          [    0.001413] pid_max: default: 32768 minimum: 301

          [    0.001734] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)

          [    0.001777] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)

          [    0.002764] Initializing cgroup subsys blkio

          [    0.002813] Initializing cgroup subsys memory

          [    0.002860] Initializing cgroup subsys devices

          [    0.002904] Initializing cgroup subsys freezer

          [    0.002954] Initializing cgroup subsys net_cls

          [    0.003023] CPU: Testing write buffer coherency: ok

          [    0.003112] ftrace: allocating 20313 entries in 60 pages

          [    0.048751] CPU0: update cpu_capacity 1024

          [    0.048816] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000

          [    0.048851] [bcm2709_smp_prepare_cpus] enter

          [    0.049005] Setting up static identity map for 0x8240 - 0x8274

          [    0.050782] [bcm2709_boot_secondary] cpu:1 started (0) 17

          [    0.050986] [bcm2709_secondary_init] enter cpu:1

          [    0.051028] CPU1: update cpu_capacity 1024

          [    0.051034] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001

          [    0.051420] [bcm2709_boot_secondary] cpu:2 started (0) 17

          [    0.051586] [bcm2709_secondary_init] enter cpu:2

          [    0.051607] CPU2: update cpu_capacity 1024

          [    0.051613] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002

          [    0.051980] [bcm2709_boot_secondary] cpu:3 started (0) 18

          [    0.052111] [bcm2709_secondary_init] enter cpu:3

          [    0.052132] CPU3: update cpu_capacity 1024

          [    0.052138] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003

          [    0.052201] Brought up 4 CPUs

          [    0.052299] SMP: Total of 4 processors activated (153.60 BogoMIPS).

          [    0.052329] CPU: All CPU(s) started in HYP mode.

          [    0.052355] CPU: Virtualization extensions available.

          [    0.053044] devtmpfs: initialized

          [    0.071862] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4

          [    0.072130] clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns

          [    0.072982] pinctrl core: initialized pinctrl subsystem

          [    0.073532] NET: Registered protocol family 16

          [    0.078653] DMA: preallocated 4096 KiB pool for atomic coherent allocations

          [    0.079626] bcm2709.uart_clock = 48000000

          [    0.083898] bcm2709: Mini UART enabled

          [    0.083965] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.

          [    0.084012] hw-breakpoint: maximum watchpoint size is 8 bytes.

          [    0.084188] Serial: AMBA PL011 UART driver

          [    0.084258] uart-pl011 3f201000.uart: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe

          [    0.084458] bcm2835-mbox 3f00b880.mailbox: mailbox enabled

          [    0.149483] bcm2708-dmaengine 3f007000.dma: DMA legacy API manager at f3007000, dmachans=0xf35

          [    0.149554] bcm2708-dmaengine 3f007000.dma: Initialized 7 DMA channels (+ 1 legacy)

          [    0.150142] bcm2708-dmaengine 3f007000.dma: Load BCM2835 DMA engine driver

          [    0.150178] bcm2708-dmaengine 3f007000.dma: dma_debug:0

          [    0.150761] SCSI subsystem initialized

          [    0.150964] usbcore: registered new interface driver usbfs

          [    0.151071] usbcore: registered new interface driver hub

          [    0.151189] usbcore: registered new device driver usb

          [    0.151750] raspberrypi-firmware soc:firmware: Attached to firmware from 2016-03-15 14:47

          [    0.178847] Switched to clocksource arch_sys_counter

          [    0.220293] FS-Cache: Loaded

          [    0.220575] CacheFiles: Loaded

          [    0.229919] NET: Registered protocol family 2

          [    0.230881] TCP established hash table entries: 8192 (order: 3, 32768 bytes)

          [    0.231022] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)

          [    0.231232] TCP: Hash tables configured (established 8192 bind 8192)

          [    0.231347] UDP hash table entries: 512 (order: 2, 16384 bytes)

          [    0.231416] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)

          [    0.231740] NET: Registered protocol family 1

          [    0.232071] RPC: Registered named UNIX socket transport module.

          [    0.232104] RPC: Registered udp transport module.

          [    0.232132] RPC: Registered tcp transport module.

          [    0.232159] RPC: Registered tcp NFSv4.1 backchannel transport module.

          [    0.233139] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available

          [    0.234210] futex hash table entries: 1024 (order: 4, 65536 bytes)

          [    0.247619] VFS: Disk quotas dquot_6.6.0

          [    0.247952] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

          [    0.250054] FS-Cache: Netfs 'nfs' registered for caching

          [    0.250984] NFS: Registering the id_resolver key type

          [    0.251051] Key type id_resolver registered

          [    0.251080] Key type id_legacy registered

          [    0.253141] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)

          [    0.253301] io scheduler noop registered

          [    0.253341] io scheduler deadline registered (default)

          [    0.253636] io scheduler cfq registered

          [    0.255931] BCM2708FB: allocated DMA memory fa800000

          [    0.255978] BCM2708FB: allocated DMA channel 0 @ f3007000

          [    0.262569] Console: switching to colour frame buffer device 100x30

          [    0.268097] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled

          [    0.271309] console [ttyS0] disabled

          [    0.272996] 3f215040.uart: ttyS0 at MMIO 0x3f215040 (irq = 29, base_baud = 50000000) is a 16550

          [    1.471429] console [ttyS0] enabled

          [    1.479713] vc-cma: Videocore CMA driver

          [    1.487782] vc-cma: vc_cma_base      = 0x00000000

          [    1.497193] vc-cma: vc_cma_size      = 0x00000000 (0 MiB)

          [    1.507700] vc-cma: vc_cma_initial   = 0x00000000 (0 MiB)

          [    1.518296] vc-mem: phys_addr:0x00000000 mem_base=0x3dc00000 mem_size:0x3f000000(1008 MiB)

          [    1.544732] brd: module loaded

          [    1.558270] loop: module loaded

          [    1.565835] vchiq: vchiq_init_state: slot_zero = 0xba880000, is_master = 0

          [    1.580203] Loading iSCSI transport class v2.0-870.

          [    1.590457] usbcore: registered new interface driver smsc95xx

          [    1.601518] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)

          [    1.812823] Core Release: 2.80a

          [    1.819620] Setting default values for core params

          [    1.829093] Finished setting default values for core params

          [    2.040132] Using Buffer DMA mode

          [    2.047135] Periodic Transfer Interrupt Enhancement - disabled

          [    2.058301] Multiprocessor Interrupt Enhancement - disabled

          [    2.069060] OTG VER PARAM: 0, OTG VER FLAG: 0

          [    2.077859] Dedicated Tx FIFOs mode

          [    2.085582] WARN::dwc_otg_hcd_init:1047: FIQ DMA bounce buffers: virt = 0xba814000 dma = 0xfa814000 len=9024

          [    2.105141] FIQ FSM acceleration enabled for :

          Non-periodic Split Transactions

          Periodic Split Transactions

          High-Speed Isochronous Endpoints

          [    2.139039] dwc_otg: Microframe scheduler enabled

          [    2.139093] WARN::hcd_init_fiq:412: FIQ on core 1 at 0x80417288

          [    2.150401] WARN::hcd_init_fiq:413: FIQ ASM at 0x804175f8 length 36

          [    2.162292] WARN::hcd_init_fiq:438: MPHI regs_base at 0xbb89c000

          [    2.173802] dwc_otg 3f980000.usb: DWC OTG Controller

          [    2.183605] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1

          [    2.197206] dwc_otg 3f980000.usb: irq 32, io mem 0x00000000

          [    2.208010] Init: Port Power? op_state=1

          [    2.216063] Init: Power Port (0)

          [    2.223115] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

          [    2.235827] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

          [    2.249236] usb usb1: Product: DWC OTG Controller

          [    2.258512] usb usb1: Manufacturer: Linux 4.1.19-v7+ dwc_otg_hcd

          [    2.269934] usb usb1: SerialNumber: 3f980000.usb

          [    2.279745] hub 1-0:1.0: USB hub found

          [    2.287470] hub 1-0:1.0: 1 port detected

          [    2.295822] dwc_otg: FIQ enabled

          [    2.295832] dwc_otg: NAK holdoff enabled

          [    2.295840] dwc_otg: FIQ split-transaction FSM enabled

          [    2.295871] Module dwc_common_port init

          [    2.296130] usbcore: registered new interface driver usb-storage

          [    2.307677] mousedev: PS/2 mouse device common for all mice

          [    2.319021] bcm2835-cpufreq: min=600000 max=1200000

          [    2.328814] sdhci: Secure Digital Host Controller Interface driver

          [    2.340458] sdhci: Copyright(c) Pierre Ossman

          [    2.349336] sdhost: log_buf @ ba813000 (fa813000)

          [    2.428878] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)

          [    2.461683] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0

          [    2.472738] mmc-bcm2835 3f300000.mmc: DMA channel allocated

          [    2.488932] Indeed it is in host mode hprt0 = 00021501

          [    2.499746] mmc0: host does not support reading read-only switch, assuming write-enable

          [    2.517253] mmc0: new high speed SDHC card at address 59b4

          [    2.518964] sdhci-pltfm: SDHCI platform and OF driver helper

          [    2.519332] ledtrig-cpu: registered to indicate activity on CPUs

          [    2.519454] hidraw: raw HID events driver (C) Jiri Kosina

          [    2.519642] usbcore: registered new interface driver usbhid

          [    2.519645] usbhid: USB HID core driver

          [    2.520049] Initializing XFRM netlink socket

          [    2.520074] NET: Registered protocol family 17

          [    2.520182] Key type dns_resolver registered

          [    2.520610] Registering SWP/SWPB emulation handler

          [    2.559401] registered taskstats version 1

          [    2.559581] vc-sm: Videocore shared memory driver

          [    2.559590] [vc_sm_connected_init]: start

          [    2.560770] [vc_sm_connected_init]: end - returning 0

          [    2.562088] 3f201000.uart: ttyAMA0 at MMIO 0x3f201000 (irq = 83, base_baud = 0) is a PL011 rev2

          [    2.665718] Waiting for root device /dev/mmcblk0p7...

          [    2.665935] mmcblk0: mmc0:59b4 NCard 7.48 GiB

          [    2.669939]  mmcblk0: p1 p2 < p5 p6 p7 >

          [    2.687522] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)

          [    2.688871] usb 1-1: new high-speed USB device number 2 using dwc_otg

          [    2.689002] Indeed it is in host mode hprt0 = 00001101

          [    2.689082] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)

          [    2.690629] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)

          [    2.693407] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)

          [    2.758741] EXT4-fs (mmcblk0p7): INFO: recovery required on readonly filesystem

          [    2.772173] EXT4-fs (mmcblk0p7): write access will be enabled during recovery

          [    2.783770] mmc1: new high speed SDIO card at address 0001

          [    2.889145] usb 1-1: New USB device found, idVendor=0424, idProduct=9514

          [    2.901639] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0

          [    2.915491] hub 1-1:1.0: USB hub found

          [    2.923240] hub 1-1:1.0: 5 ports detected

          [    3.208885] usb 1-1.1: new high-speed USB device number 3 using dwc_otg

          [    3.319124] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00

          [    3.331945] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0

          [    3.348188] smsc95xx v1.0.4

          [    3.411904] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:b7:a7:24

          [    5.170328] EXT4-fs (mmcblk0p7): orphan cleanup on readonly fs

          [    5.181938] EXT4-fs (mmcblk0p7): 1 orphan inode deleted

          [    5.192195] EXT4-fs (mmcblk0p7): recovery complete

          [    5.513869] EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: (null)

          [    5.528810] VFS: Mounted root (ext4 filesystem) readonly on device 179:7.

          [    5.553300] devtmpfs: mounted

          [    5.560555] Freeing unused kernel memory: 444K (80795000 - 80804000)

          [    5.908700] random: systemd urandom read with 68 bits of entropy available

          [    5.925167] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)

          [    5.950989] systemd[1]: Detected architecture 'arm'.

          [    6.121309] NET: Registered protocol family 10

          [    6.131734] systemd[1]: Inserted module 'ipv6'

          [    6.143814] systemd[1]: Set hostname to <raspberrypi>.

          [    6.531286] systemd[1]: Expecting device dev-ttyS0.device...

          [    6.544947] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.

          [    6.559596] systemd[1]: Started Forward Password Requests to Wall Directory Watch.

          [    6.573933] systemd[1]: Starting Remote File Systems (Pre).

          [    6.587167] systemd[1]: Reached target Remote File Systems (Pre).

          [    6.599102] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.

          [    6.617868] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.

          [    6.637245] systemd[1]: Starting Encrypted Volumes.

          [    6.649601] systemd[1]: Reached target Encrypted Volumes.

          [    6.660454] systemd[1]: Starting Swap.

          [    6.670729] systemd[1]: Reached target Swap.

          [    6.679588] systemd[1]: Expecting device dev-mmcblk0p6.device...

          [    6.693376] systemd[1]: Starting Root Slice.

          [    6.704429] systemd[1]: Created slice Root Slice.

          [    6.714012] systemd[1]: Starting User and Session Slice.

          [    6.726927] systemd[1]: Created slice User and Session Slice.

          [    6.738268] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.

          [    6.753344] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.

          [    6.766675] systemd[1]: Starting Delayed Shutdown Socket.

          [    6.779758] systemd[1]: Listening on Delayed Shutdown Socket.

          [    6.791082] systemd[1]: Starting Journal Socket (/dev/log).

          [    6.804300] systemd[1]: Listening on Journal Socket (/dev/log).

          [    6.815824] systemd[1]: Starting udev Control Socket.

          [    6.827925] systemd[1]: Listening on udev Control Socket.

          [    6.838533] systemd[1]: Starting udev Kernel Socket.

          [    6.850492] systemd[1]: Listening on udev Kernel Socket.

          [    6.860986] systemd[1]: Starting Journal Socket.

          [    6.872437] systemd[1]: Listening on Journal Socket.

          [    6.882399] systemd[1]: Starting System Slice.

          [    6.893583] systemd[1]: Created slice System Slice.

          [    6.903385] systemd[1]: Starting File System Check on Root Device...

          [    6.919901] systemd[1]: Starting system-systemd\x2dfsck.slice.

          [    6.934115] systemd[1]: Created slice system-systemd\x2dfsck.slice.

          [    6.946302] systemd[1]: Starting system-autologin.slice.

          [    6.959356] systemd[1]: Created slice system-autologin.slice.

          [    6.970620] systemd[1]: Starting system-serial\x2dgetty.slice.

          [    6.984340] systemd[1]: Created slice system-serial\x2dgetty.slice.

          [    6.996516] systemd[1]: Starting Increase datagram queue length...

          [    7.012732] systemd[1]: Starting Restore / save the current clock...

          [    7.033046] systemd[1]: Mounting POSIX Message Queue File System...

          [    7.050265] systemd[1]: Starting Create list of required static device nodes for the current kernel...

          [    7.074139] systemd[1]: Starting udev Coldplug all Devices...

          [    7.131285] systemd[1]: Started Set Up Additional Binary Formats.

          [    7.144193] systemd[1]: Mounting Debug File System...

          [    7.189375] systemd[1]: Starting Load Kernel Modules...

          [    7.208235] systemd[1]: Mounted Huge Pages File System.

          [    7.219177] systemd[1]: Starting Slices.

          [    7.230021] systemd[1]: Reached target Slices.

          [    7.243491] systemd[1]: Mounted Debug File System.

          [    7.255679] systemd[1]: Mounted POSIX Message Queue File System.

          [    7.270713] systemd[1]: Started Increase datagram queue length.

          [    7.311306] fuse init (API version 7.23)

          [    7.321986] systemd[1]: Started Restore / save the current clock.

          [    7.337691] systemd[1]: Started Create list of required static device nodes for the current kernel.

          [    7.361974] systemd[1]: Time has been changed

          [    7.378156] i2c /dev entries driver

          [    7.388297] systemd[1]: Started File System Check on Root Device.

          [    7.403977] systemd[1]: Started Load Kernel Modules.

          [    7.417519] systemd[1]: Started udev Coldplug all Devices.

          [    7.567132] systemd[1]: Starting Apply Kernel Variables...

          [    7.583270] systemd[1]: Mounting Configuration File System...

          [    7.599531] systemd[1]: Mounting FUSE Control File System...

          [    7.605008] systemd[1]: Starting Create Static Device Nodes in /dev...

          [    7.610628] systemd[1]: Starting Syslog Socket.

          [    7.613885] systemd[1]: Listening on Syslog Socket.

          [    7.614051] systemd[1]: Starting Journal Service...

          [    7.621762] systemd[1]: Started Journal Service.

          [    7.773163] systemd-udevd[111]: starting version 215

          [    8.142179] rpi-ft5406 rpi_ft5406: Probing device

          [    8.142600] input: FT5406 memory based driver as /devices/virtual/input/input0

          [    8.469205] EXT4-fs (mmcblk0p7): re-mounted. Opts: (null)

          [    8.628099] cfg80211: Calling CRDA to update world regulatory domain

          [    8.719024] brcmfmac: brcmf_sdio_drivestrengthinit: No SDIO Drive strength init done for chip 43430 rev 1 pmurev 24

          [    8.719885] usbcore: registered new interface driver brcmfmac

          [    8.966409] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Dec 15 2015 18:10:45 version 7.45.41.23 (r606571) FWID 01-cc4eda9c

          [    8.992664] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code

          [    9.093632] bcm2835-rng 3f104000.rng: hwrng registered

          [    9.094189] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000

          [    9.392909] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code

          [    9.392935] cfg80211: World regulatory domain updated:

          [    9.392944] cfg80211:  DFS Master region: unset

          [    9.392953] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)

          [    9.392967] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)

          [    9.392980] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)

          [    9.392992] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)

          9.393007 cfg80211(5170000 KHz 5250000 KHz 80000 KHz  160000160000 KHz AUTO(N/A 2000 mBm(N/A

          9.393021 cfg80211(5250000 KHz 5330000 KHz 80000 KHz  160000160000 KHz AUTO(N/A 2000 mBm(0 s

          9.393034 cfg80211(5490000 KHz 5730000 KHz  160000160000 KHz(N/A 2000 mBm(0 s

          [    9.393046] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)

          [    9.393058] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)

          [    9.518076] systemd-journald[108]: Received request to flush runtime journal from PID 1

          [    9.868407] brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists

          [    9.868430] brcmfmac: brcmf_add_if: ignore IF event

          [    9.873886] brcmfmac: power management disabled

          [   10.606396] uart-pl011 3f201000.uart: no DMA platform data

          [   10.994626] Adding 102396k swap on /var/swap.  Priority:-1 extents:1 across:102396k SSFS

          [   11.319062] random: nonblocking pool is initialized

          [   11.630989] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup

          [   11.631218] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

          [   13.250045] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

          [   13.253814] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1

          [   15.197767] Bluetooth: Core ver 2.20

          [   15.197851] NET: Registered protocol family 31

          [   15.197861] Bluetooth: HCI device and connection manager initialized

          [   15.197884] Bluetooth: HCI socket layer initialized

          [   15.197901] Bluetooth: L2CAP socket layer initialized

          [   15.197939] Bluetooth: SCO socket layer initialized

          [   15.214699] Bluetooth: HCI UART driver ver 2.3

          [   15.214720] Bluetooth: HCI UART protocol H4 registered

          [   15.214730] Bluetooth: HCI UART protocol Three-wire (H5) registered

          [   15.214740] Bluetooth: HCI UART protocol BCM registered

          [   15.553447] Bluetooth: BNEP (Ethernet Emulation) ver 1.3

          [   15.553466] Bluetooth: BNEP filters: protocol multicast

          [   15.553489] Bluetooth: BNEP socket layer initialized

          [   25.129810] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: (null)

          pi@raspberrypi:~ $

          • Re: RPI 3 nousb
            shabaz

            Hi Dan,

             

            How did you get the OS installed without using the keyboard? Could you try downloading Raspbian Jessie (you didn't specify if it was Raspbian or not) and installing that? (For transferring the file onto the microSD card, use Win32DiskImager on a Windows PC or the appropriate software and procedure as described in the getting started section at raspberrypi.org - Apple Mac is probably described there too).

            For the install, ensure there are no ancillary bits like the touch screen connected, just a wired keyboard and mouse (not all wireless ones work) and HDMI and power of course. If you see any rainbow squares on the display, or the red LED on the Pi turning off briefly then these symptoms will mean a better power supply (and/or USB cable with internal heavier gauge wire for power) is needed.

             

            I've tried running without the touch screen(via ssh) nothing is recognized.

             

            This part I didn't understand - SSH doesn't use USB. It isn't related, so perhaps it is an install related issue if multiple things are at fault.

             

            Are you by any chance using the console (serial) connection from the 40-pin header to access your Pi? That has (severe) issues although there are workarounds of sorts.

            Google 'raspberry pi 3 uart baud issue' to see detail about this - in short, the baud rate is unpredictable. Leaving you with no access whenever a clock inside the Pi's BCM.. chip changes frequency. The couple of workarounds address this in a few different ways.

            • Re: RPI 3 nousb
              clem57

              Please paste the output of the following

              lsusb -v

                • Re: RPI 3 nousb
                  icepuck

                  I'll try that once I have jessie installed on the new card.

                  • Re: RPI 3 nousb
                    icepuck

                    pi@raspberrypi:~ $ lsusb -v

                     

                     

                    Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter

                    Couldn't open device, some information will be missing

                    Device Descriptor:

                      bLength                18

                      bDescriptorType         1

                      bcdUSB               2.00

                      bDeviceClass          255 Vendor Specific Class

                      bDeviceSubClass         0

                      bDeviceProtocol         1

                      bMaxPacketSize0        64

                      idVendor           0x0424 Standard Microsystems Corp.

                      idProduct          0xec00 SMSC9512/9514 Fast Ethernet Adapter

                      bcdDevice            2.00

                      iManufacturer           0

                      iProduct                0

                      iSerial                 0

                      bNumConfigurations      1

                      Configuration Descriptor:

                        bLength                 9

                        bDescriptorType         2

                        wTotalLength           39

                        bNumInterfaces          1

                        bConfigurationValue     1

                        iConfiguration          0

                        bmAttributes         0xe0

                          Self Powered

                          Remote Wakeup

                        MaxPower                2mA

                        Interface Descriptor:

                          bLength                 9

                          bDescriptorType         4

                          bInterfaceNumber        0

                          bAlternateSetting       0

                          bNumEndpoints           3

                          bInterfaceClass       255 Vendor Specific Class

                          bInterfaceSubClass      0

                          bInterfaceProtocol    255

                          iInterface              0

                          Endpoint Descriptor:

                            bLength                 7

                            bDescriptorType         5

                            bEndpointAddress     0x81  EP 1 IN

                            bmAttributes            2

                              Transfer Type            Bulk

                              Synch Type               None

                              Usage Type               Data

                            wMaxPacketSize     0x0200  1x 512 bytes

                            bInterval               0

                          Endpoint Descriptor:

                            bLength                 7

                            bDescriptorType         5

                            bEndpointAddress     0x02  EP 2 OUT

                            bmAttributes            2

                              Transfer Type            Bulk

                              Synch Type               None

                              Usage Type               Data

                            wMaxPacketSize     0x0200  1x 512 bytes

                            bInterval               0

                          Endpoint Descriptor:

                            bLength                 7

                            bDescriptorType         5

                            bEndpointAddress     0x83  EP 3 IN

                            bmAttributes            3

                              Transfer Type            Interrupt

                              Synch Type               None

                              Usage Type               Data

                            wMaxPacketSize     0x0010  1x 16 bytes

                            bInterval               4

                     

                     

                    Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.

                    Couldn't open device, some information will be missing

                    Device Descriptor:

                      bLength                18

                      bDescriptorType         1

                      bcdUSB               2.00

                      bDeviceClass            9 Hub

                      bDeviceSubClass         0 Unused

                      bDeviceProtocol         2 TT per port

                      bMaxPacketSize0        64

                      idVendor           0x0424 Standard Microsystems Corp.

                      idProduct          0x9514

                      bcdDevice            2.00

                      iManufacturer           0

                      iProduct                0

                      iSerial                 0

                      bNumConfigurations      1

                      Configuration Descriptor:

                        bLength                 9

                        bDescriptorType         2

                        wTotalLength           41

                        bNumInterfaces          1

                        bConfigurationValue     1

                        iConfiguration          0

                        bmAttributes         0xe0

                          Self Powered

                          Remote Wakeup

                        MaxPower                2mA

                        Interface Descriptor:

                          bLength                 9

                          bDescriptorType         4

                          bInterfaceNumber        0

                          bAlternateSetting       0

                          bNumEndpoints           1

                          bInterfaceClass         9 Hub

                          bInterfaceSubClass      0 Unused

                          bInterfaceProtocol      1 Single TT

                          iInterface              0

                          Endpoint Descriptor:

                            bLength                 7

                            bDescriptorType         5

                            bEndpointAddress     0x81  EP 1 IN

                            bmAttributes            3

                              Transfer Type            Interrupt

                              Synch Type               None

                              Usage Type               Data

                            wMaxPacketSize     0x0001  1x 1 bytes

                            bInterval              12

                        Interface Descriptor:

                          bLength                 9

                          bDescriptorType         4

                          bInterfaceNumber        0

                          bAlternateSetting       1

                          bNumEndpoints           1

                          bInterfaceClass         9 Hub

                          bInterfaceSubClass      0 Unused

                          bInterfaceProtocol      2 TT per port

                          iInterface              0

                          Endpoint Descriptor:

                            bLength                 7

                            bDescriptorType         5

                            bEndpointAddress     0x81  EP 1 IN

                            bmAttributes            3

                              Transfer Type            Interrupt

                              Synch Type               None

                              Usage Type               Data

                            wMaxPacketSize     0x0001  1x 1 bytes

                            bInterval              12

                     

                     

                    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

                    Couldn't open device, some information will be missing

                    Device Descriptor:

                      bLength                18

                      bDescriptorType         1

                      bcdUSB               2.00

                      bDeviceClass            9 Hub

                      bDeviceSubClass         0 Unused

                      bDeviceProtocol         1 Single TT

                      bMaxPacketSize0        64

                      idVendor           0x1d6b Linux Foundation

                      idProduct          0x0002 2.0 root hub

                      bcdDevice            4.01

                      iManufacturer           3

                      iProduct                2

                      iSerial                 1

                      bNumConfigurations      1

                      Configuration Descriptor:

                        bLength                 9

                        bDescriptorType         2

                        wTotalLength           25

                        bNumInterfaces          1

                        bConfigurationValue     1

                        iConfiguration          0

                        bmAttributes         0xe0

                          Self Powered

                          Remote Wakeup

                        MaxPower                0mA

                        Interface Descriptor:

                          bLength                 9

                          bDescriptorType         4

                          bInterfaceNumber        0

                          bAlternateSetting       0

                          bNumEndpoints           1

                          bInterfaceClass         9 Hub

                          bInterfaceSubClass      0 Unused

                          bInterfaceProtocol      0 Full speed (or root) hub

                          iInterface              0

                          Endpoint Descriptor:

                            bLength                 7

                            bDescriptorType         5

                            bEndpointAddress     0x81  EP 1 IN

                            bmAttributes            3

                              Transfer Type            Interrupt

                              Synch Type               None

                              Usage Type               Data

                            wMaxPacketSize     0x0004  1x 4 bytes

                            bInterval              12

                    pi@raspberrypi:~ $

                      • Re: RPI 3 nousb
                        clem57

                        Please remove fast Ethernet adapter and try again with same display.

                        Clem

                          • Re: RPI 3 nousb
                            icepuck

                            pi@raspberrypi:~ $ sudo apt search fast ethernet

                            Sorting... Done

                            Full Text Search... Done

                            vde2/stable 2.3.2+r586-1 armhf

                              Virtual Distributed Ethernet

                             

                            pi@raspberrypi:~ $ sudo apt-get remove vde2

                            Reading package lists... Done

                            Building dependency tree      

                            Reading state information... Done

                            Package 'vde2' is not installed, so not removed

                            0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

                             

                             

                            How do I remove it?

                              • Re: RPI 3 nousb
                                clem57

                                Sorry unplug it to see how the hub gets affected.

                                  • Re: RPI 3 nousb
                                    icepuck

                                    There wasn't anything else plugged in. So, I'm starting to think I got a bad pi. I tried Ubuntu mate and the usb ports didn't work with either.

                                      • Re: RPI 3 nousb
                                        Roger Wolff

                                        The Sony  factory in England builds the raspberry pi's. They test all the pi's before they ship. They have a low "bad device" percentage at testing in the fatory, as well as a low percentage of devices that come back (and turn out to be actually bad). So, chances are high that your raspberry is in good working order. But never say never.

                                         

                                        That said. the symptoms you seem to be having could for instance be that your powersupply is not adequate. Where I say powersupply that includes the cable to the pi.

                                         

                                        I have an USB hub here that occasionally delivers only 4V on its output. While "out of spec" for the 'pi, it WILL work. But (some) USB devices won't. (Newer pi's run down to below 3V, while the older ones stop working around 4.0V)

                                         

                                        So: Check your power-supply-setup. What voltage do you measure on the 5V GPIO pin? Does the red powerled turn on? Does it blink?

                            • Re: RPI 3 nousb
                              peteroakes

                              If the PI thinks the volts is too low it will normally put up a small square rainbow icon in the top right corner of the screen. Are you getting this ??

                                • Re: RPI 3 nousb
                                  icepuck

                                  The first picture show the load of my pi 3 with touch screen and no usb or Ethernet hooked up. And the rainbow colored square showed up during this test.

                                  This was a quick test I did right after I got home from work so I may not be thinking clearly.So...now what else should I test?

                                  BTW that was a usb 2.1amp battery pack.

                                   

                                  20160325_161945.jpg

                                  20160325_162116.jpg

                                    • Re: RPI 3 nousb
                                      icepuck

                                      I tested my power supplies they all ranged from 4.98-5.12 volts and I was still getting the rainbow square in upper right corner. I also found out that rebooting doesn't work when attached to the touch screen, shutting down and removing power is what it takes for updates to work.

                                       

                                      I checked 5v at the gpio header and found that I had 3.8 volts coming out of the lcd powering the pi.

                                       

                                      Next I'll test the pi 3 with a monitor and maybe test my other pi's with the touch screen.

                                        • Re: RPI 3 nousb
                                          Roger Wolff

                                          Glad to hear that my hunch at what was wrong was correct. :-) 

                                           

                                          Your "3.8V" measurement clearly indicates that your pi is not getting enough power.

                                          The rainbow square is clear indication that your pi is not getting enough power.

                                           

                                          Now there is only one "odd" measurement: You claim to have measured 4.98-5.12V on the power supplies. My guess is that you measured that without any load. Once the pi is connected, the voltage drops. With good power supplies only a little, with a bad power supply it might be a lot. Or you measured at the power supply side of the cable, and not at the pi-side of the cable. Actually measuring at the GPIO is a reasonable way of going about measuring the power supply voltage "under load of a pi". So IMHO the 3.8V is authoritative: there is something wrong with your power supply.

                                           

                                          And again: Double check the cable. For a lot of applications you can get away with very thin conductors in an USB cable. So many cables are manufactured with the cheapest/thinnest wires they can find. Those are not suitable for powering a 'pi.

                                            • Re: RPI 3 nousb
                                              clem57

                                              Roger Wolff

                                              You are correct. I will add, I bet the current is the key and is less than 2A. He should check the output rating on the device. It may be only 500 mA.

                                              Clem

                                                • Re: RPI 3 nousb
                                                  icepuck

                                                  The psu's I use for my pi's are 2.1amp. The voltage drop was from bad cables. I found one good cable that only dropped 0.05 volt. I also figured out that if voltage drops lower than 4.98 volts the usb ports shut off and don't work even if the voltage increases after the drop.

                                                  I'm going to retest the pi 3 and lcd once my pi B is done reinstalling with the good cable. It's running at 428 mA while downloading.

                                                  1 of 1 people found this helpful
                                                    • Re: RPI 3 nousb
                                                      icepuck

                                                      Testing the pi 3 with a monitor with what I thought was a good cable that worked with my other pi's dose not work with the pi 3.

                                                      Voltage at the psu was 5.12 volts while voltage at the 5v on the gpoi was dropping down to 4.90 volts which is of course enough of a drop to kill the usb.

                                                      My logitech wireless keyboard works with the others pi's with no problems.

                                                    • Re: RPI 3 nousb
                                                      Roger Wolff

                                                      He should check the output rating on the device

                                                       

                                                      In an ideal world,... yes.

                                                       

                                                      I tend to buy cheap-ass 5V USB charger devices from China. Some "claims 2A" devices will deliver over 1.5A before dropping significantly below 5V. However, some "labeled as 2A" will only deliver 300mA, just like their "claims 500mA" brothers.


                                                      The opposite is the "motorola charger". It claims something like 800mA, but happily delivers 900mA when you connect the matching motorola cellphone.

                                                       

                                                      So  I'm not putting in too much weight on what the label says....

                                            • Re: RPI 3 nousb
                                              royleith

                                              It's usually the USB cable that is to blame. My Raspi 1 with USB wireless mouse, keyboard and WiFi dongle worked fine with a 1m cable. The Raspi 2 takes more power and will only work with a 1/2m cable. The Raspi 3 takes even more because of the on-board BlueTooth. It's all laid out in the specifications.

                                               

                                              A Comprehensive Raspberry Pi 3 Benchmark

                                               

                                              Even if the PSU produces bang on 5v, the Raspi 3 will still not work with a 2m cable because of the resistance.

                                               

                                              I tried to find my measurements, but cannot. I measured the voltage at a USB port by connecting it via a cable to a PCB USB through-hole socket and using a meter on the unsoldered pins. However, here is an excellent post on element14 that covers the issue and gives measurements (you may need to convert from feet to metres).

                                               

                                              Raspberry PI:- USB power cables, crashing and other problems

                                               

                                              The cables measured in the above link were around 0.3 Ohms to 1.2 Ohms per metre.

                                               

                                              I seem to remember that my cables were all around 0.6 Ohms per metre including those sold as 'charging' cables. If a PSU is delivering 5V at 1 Amp via a 1m USB cable of 0.6 Ohms resistance, then the voltage at the Pi is 5V - (0.6 x 1A) = 4.3V.

                                               

                                              The maximum power draw from the Pi 1 and the Pi 2 is 1.8A. The maximum power draw from the Pi3 is 2.5A.

                                               

                                              For a 5Volt PSU that can actually deliver 2.5A at 5V, the voltage drop across a typical (28AWG thickness) cable - often with 28AWG printed on the side - of one metre in length is 2.5 x 0.6 = 1.5V. The voltage at the Raspberry Pi 3 is 5V -1.5V = 3.5V. This is the worst case at the maximum power draw, but it is a problem even at the minimum power draw for a RPi 3 because of the extra on-board components.

                                               

                                              The official power supply is rated at 5.1V which helps to reduce the problem. Don't use a PSU with a higher rated voltage because the Raspi might pop if the connected devices stop taking their normal power draw. The obvious way to solve the problem is to use 25cm cables rather than the typical 180cm cables or the shorter 100cm cables. Always buy cables rated as 'charging' cables, but don't try to use anything longer than 50cm because they are typically still only 28AWG in thickness and have relatively high resistance. 

                                                • Re: RPI 3 nousb
                                                  icepuck

                                                  I got some 20 AWG charging usb cables from amazon and tried again(without the lcd) with the 2.1a psu, usb works until I try to use Bluetooth which drops the voltage enough to kill the usb ports. Which means I cannot finish setting up Bluetooth.

                                                   

                                                  So, I tried a 2.4a and a 3.4a usb psu and those turned out to be worse than the 2.1a psu. The 2.4a psu was 4.88 volts while the 3.4a psu was 4.91 volts. It looks like the oddball voltage requirements is the problem and not the amperage requirements.

                                                  Trying to find a quality psu for the pi 3 is getting to be a real PITA. Element14 has 872 while MCM has 0.

                                                  I have a 8a 5 volt psu that's running my RGB leds. 5.09 volts with a 3 amp load, 5.14 volts no load. I'll be trying that next when I have the time. If that doesn't work I'll send my pi 3 back to MCM.

                                                  BTW my other pi's say made in the UK while my pi 3 says made in PRC. WTH is that?

                                                    • Re: RPI 3 nousb
                                                      clem57

                                                      Dan,

                                                           No way? That may be part of the problem and I would get an RMA based on the information you put forth here. Mine was UK made from Microcenter since on line was hard to get.

                                                      Clem

                                                      • Re: RPI 3 nousb
                                                        royleith

                                                        How long were the cables you used? Try using one that is only a quarter of a meter long.

                                                         

                                                        A 1.8 meter cable can easily lose 1 volt.

                                                         

                                                        If your 20 AWG cable was 0.3 Ohms per meter and (a typical) 1.8 meters long, then, at the full current rating of your 2.1A PSU and an output of 5Volts, the voltage loss along the cable will be:

                                                         

                                                        2.1 x 1.8 x 0.3 Volts

                                                         

                                                        = 1.134 Volts

                                                         

                                                        Even though the PSU is producing 5 Volts @ 2.1 Amps, the Pi will see 5 Volts - 1.134 Volts =  3.866 Volts.

                                                         

                                                        With a quarter of a meter cable the voltage at the Pi would be 4.842 Volts. Even with a good 28 AWG cable it only drops to 4.7 Volts.

                                                         

                                                        The approved PSU produces 5.1 Volts which makes the loss at high currents even more acceptable.

                                                         

                                                        Bear in mind that the maximum power draw from the Pi 1 and the Pi 2 is 1.8A. The maximum power draw from the Pi3 is 2.5A.