Forum List Message List New Topic
Jxjhheric
Help Pogoplug e02 and V4 won't boot
June 25, 2018 07:36PM
here is console ： 
U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700)
Pogo E02
SoC:   Kirkwood 88F6281_A0
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Using egiga0 device
host 192.168.1.105 is alive
Using egiga0 device
ARP Retry count exceeded; starting again
ping failed; host 192.168.1.105 is not alive
Using egiga0 device
ARP Retry count exceeded; starting again
ping failed; host 192.168.1.105 is not alive
Using egiga0 device
ARP Retry count exceeded; starting again
ping failed; host 192.168.1.105 is not alive
Using egiga0 device
host 192.168.1.105 is alive



Edited 1 time(s). Last edit at 06/30/2018 09:23AM by Jxjhheric.
Reply Quote
bodhi
Re: Help Pogoplug e02 uboot won't boot
June 25, 2018 07:52PM
Jxjhheric Wrote:
-------------------------------------------------------
> here is console ：
> 
> U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18
> -0700)
> Pogo E02
> SoC:   Kirkwood 88F6281_A0
> DRAM:  256 MiB
> WARNING: Caches not enabled
> NAND:  128 MiB
> In:    serial
> Out:   serial
> Err:   serial
> Net:   egiga0
> Using egiga0 device
> host 192.168.1.105 is alive
> Using egiga0 device
> ARP Retry count exceeded; starting again
> ping failed; host 192.168.1.105 is not alive
> Using egiga0 device
> ARP Retry count exceeded; starting again
> ping failed; host 192.168.1.105 is not alive
> Using egiga0 device
> ARP Retry count exceeded; starting again
> ping failed; host 192.168.1.105 is not alive
> Using egiga0 device
> host 192.168.1.105 is alive
>

That was all you see on serial console terminal?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
Jxjhheric
Re: Help Pogoplug e02 uboot won't boot
June 25, 2018 08:44PM
yes Then it continues like this 
>Using egiga0 device
> host 192.168.1.105 is alive

and the led blink always
Reply Quote
bodhi
Re: Help Pogoplug e02 uboot won't boot
June 25, 2018 09:18PM
Jxjhheric,

The reason you can't see anything after this was because you have netconsole activated at the same time you're connecting with serial console. 

> host 192.168.1.105 is alive

So what you can do to fix this quiclky: change the IP address of the box that you have serial console module plugged in to other number, eg. 192.168.1.106.

If you'd rather not doing that, then you need a second terminal on that box 192.168.1.105, where you run nc to activate netconsole server and can see the rest of the output and can interact with this Pogo E02.

After you've fixed that configuration problem, capture the log and post here. We''ll figure out why it did not complete booting.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
Jxjhheric
Re: Help Pogoplug e02 uboot won't boot
June 25, 2018 09:30PM
thanks for your quick reply i will do this later
then post logs here
Reply Quote
Jxjhheric
Re: Help Pogoplug e02 uboot won't boot
June 27, 2018 07:40PM
change the IP address works thanks
Reply Quote
Jxjhheric
Re: Help Pogoplug e02 uboot won't boot
June 30, 2018 08:56AM
sorry about another problem after upgrade the lastest kernel on pogo v4

here is the log： 
U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   kwsdio: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
No link on egiga0
ping failed; host 192.168.1.157 is not alive
Hit any key to stop autoboot:  0

MMC rescan: current device # 0 initialized OK
3831876 bytes read in 1545 ms (2.4 MiB/s)
7245696 bytes read in 1700 ms (4.1 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.12.1-kirkwood-tld-1
   Created:      2018-06-30  12:44:32 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3831812 Bytes = 3.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.12.1-kirkwood-tld-1
   Created:      2017-07-24   0:18:23 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7245632 Bytes = 6.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
Using machid 0xf78 from environment

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

can't boot
Reply Quote
bodhi
Re: Help Pogoplug e02 uboot won't boot
June 30, 2018 04:19PM
Jxjhheric Wrote:
-------------------------------------------------------
> sorry about another problem after upgrade the
> lastest kernel on pogo v4
>
> here is the log：
> 
> U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
> Pogoplug V4
> 
> SoC:   Kirkwood 88F6192_A1
> DRAM:  128 MiB
> WARNING: Caches not enabled
> NAND:  128 MiB
> MMC:   kwsdio: 0
> In:    serial
> Out:   serial
> Err:   serial
> Net:   egiga0
> No link on egiga0
> ping failed; host 192.168.1.157 is not alive
> Hit any key to stop autoboot:  0
> 
> MMC rescan: current device # 0 initialized OK
> 3831876 bytes read in 1545 ms (2.4 MiB/s)
> 7245696 bytes read in 1700 ms (4.1 MiB/s)
> ## Booting kernel from Legacy Image at 00800000
> ...
>    Image Name:   Linux-4.12.1-kirkwood-tld-1
>    Created:      2018-06-30  12:44:32 UTC
>    Image Type:   ARM Linux Kernel Image
> (uncompressed)
>    Data Size:    3831812 Bytes = 3.7 MiB
>    Load Address: 00008000
>    Entry Point:  00008000
>    Verifying Checksum ... OK
> ## Loading init Ramdisk from Legacy Image at
> 01100000 ...
>    Image Name:   initramfs-4.12.1-kirkwood-tld-1
>    Created:      2017-07-24   0:18:23 UTC
>    Image Type:   ARM Linux RAMDisk Image (gzip
> compressed)
>    Data Size:    7245632 Bytes = 6.9 MiB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> Using machid 0xf78 from environment
> 
> Starting kernel ...
> 
> Uncompressing Linux... done, booting the kernel.
> 
>
>
> can't boot

If the log stops here then, you have missed the default env image intsallation:

Quote

8. Flashing default u-boot envs image (if you are upgrading from 2016.05-tld-1 u-boot, you can skip this step 8).

Or if you did, somehow your envs are messed up.


Power up, interrupt serial console at countdown and: 

printenv
See what you have have and we go from there.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
Jxjhheric
Re: Help Pogoplug e02 and V4 won't boot
June 30, 2018 06:14PM 
Pogov4> printenv
arcNumber=3960
baudrate=115200
bootcmd=run bootcmd_mmc; run bootcmd_usb; run bootcmd_sata; run bootcmd_pogo; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_pogo=if ubi part root 2048 && ubifsmount ubi:rootfs && ubifsload 0x800000 uboot.mtd0.dockstar.original.kwb ; then go 0x800200; fi
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=00:25:31:05:f3:a8
if_netconsole=ping $serverip
ipaddr=192.168.1.204
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-pogoplug_v4.dtb
load_initrd=ext2load usb 0:1 0x1100000 /boot/uInitrd
load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
machid=F78
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
partition=nand0,2
preboot=run if_netconsole start_netconsole
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext3
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
serverip=192.168.1.157
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
usb_boot=run load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi
usb_custom_params=usb-storage.quirks=0x0bc2:0x3321:u
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1
usb_rootfstype=ext3

Environment size: 2706/131068 bytes
Reply Quote
bodhi
Re: Help Pogoplug e02 and V4 won't boot
June 30, 2018 06:48PM
Yep. Looks like you did not flash the new default envs image. These current envs are back in the days of u-boot 2012.

See here for how to load the new default envs:

https://forum.doozan.com/read.php?3,29362,29390#msg-29390

Since your box is Pogo V4, instead of 
setenv dtb_file '/boot/dts/kirkwood-goflexnet.dtb'

You need 
setenv dtb_file '/boot/dts/kirkwood-pogoplug_v4.dtb'

And no need to do kwboot, just power up the box, interrupt console, and then run the script as described in that post.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 06/30/2018 06:50PM by bodhi.
Reply Quote
bodhi
Re: Help Pogoplug e02 and V4 won't boot
June 30, 2018 06:52PM
Hold on, you had an older u-boot? 

U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)

It's OK. Try the script anyway. It should would with u-boot-2014.07-tld-1.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
Jxjhheric
Re: Help Pogoplug e02 and V4 won't boot
June 30, 2018 07:30PM
bodhi Wrote:
-------------------------------------------------------
> Yep. Looks like you did not flash the new default
> envs image. These current envs are back in the
> days of u-boot 2012.
>
> See here for how to load the new default envs:
>
> https://forum.doozan.com/read.php?3,29362,29390#msg-29390
>
> Since your box is Pogo V4, instead of
> 
> setenv dtb_file
> '/boot/dts/kirkwood-goflexnet.dtb'
>
>
> You need
> 
> setenv dtb_file
> '/boot/dts/kirkwood-pogoplug_v4.dtb'
>
>
> And no need to do kwboot, just power up the box,
> interrupt console, and then run the script as
> described in that post.

the printenv now： 
Pogov4> printenv
arcNumber=2097
baudrate=115200
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_pogo=if ubi part root 2048 && ubifsmount ubi:rootfs && ubifsload 0x800000 uboot.mtd0.dockstar.original.kwb ; then go 0x800200; fi
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
bootdev=usb
console=ttyS0,115200
device=0:1
devices=usb ide
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb
ethact=egiga0
ethaddr=00:25:31:05:f3:a8
filesize=ca0
if_netconsole=ping $serverip
init_ide=ide reset
init_mmc=mmc rescan
init_usb=usb start
ipaddr=192.168.0.231
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
machid=0x831
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot=run if_netconsole start_netconsole
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext3
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
scan_ide=ide reset
scan_mmc=mmc rescan
scan_usb=usb start
serverip=192.168.0.220
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_loaded=0
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_boot=run load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi
usb_custom_params=usb-storage.quirks=0x0bc2:0x3321:u
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_ready_retry=15
usb_root=/dev/sda1
usb_rootfstype=ext3


get this output： 
 boot
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices...
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found

Reset IDE: ide_preinit failed

Partition Map for USB device 0  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     2048            15997953        f481f54b-01     83
loading envs from usb 0 ...
Unknown command 'load' - try 'help'

no IDE devices available
running scan_disk ...
Scan device usb
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices...
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found
device usb 0:1
Unknown command 'load' - try 'help'
device usb 1:1
Unknown command 'load' - try 'help'
device usb 2:1
Unknown command 'load' - try 'help'
device usb 3:1
Unknown command 'load' - try 'help'
Scan device ide

Reset IDE: ide_preinit failed
device ide 0:1
Unknown command 'load' - try 'help'
device ide 1:1
Unknown command 'load' - try 'help'
device ide 2:1
Unknown command 'load' - try 'help'
device ide 3:1
Unknown command 'load' - try 'help'
loading uImage ...
Unknown command 'load' - try 'help'
loading uInitrd ...
Unknown command 'load' - try 'help'
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
Unknown command 'load' - try 'help'
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   uboot.2016.05-tld-1.environment.
   Created:      2016-08-07  22:21:47 UTC
   Image Type:   ARM Linux Script (uncompressed)
   Data Size:    3168 Bytes = 3.1 KiB
   Load Address: 00000000
   Entry Point:  00000000
   Contents:
      Image 0: 3160 Bytes = 3.1 KiB
   Verifying Checksum ... OK
Wrong Image Type for bootm command
ERROR: can't get kernel image!
Pogov4>



Edited 1 time(s). Last edit at 06/30/2018 07:33PM by Jxjhheric.
Reply Quote
bodhi
Re: Help Pogoplug e02 and V4 won't boot
June 30, 2018 10:21PM
Jxjhheric,

Ah! u-boot 2014.07-tld-1 is a little old for this 2016-5 script.

Try its matching script uboot.2014.07-tld-1.environment.scr in this post:

https://forum.doozan.com/read.php?3,9810,23956#msg-23956

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
Jxjhheric
Re: Help Pogoplug e02 and V4 won't boot
June 30, 2018 11:23PM
bodhi Wrote:
-------------------------------------------------------
> Jxjhheric,
>
> Ah! u-boot 2014.07-tld-1 is a little old for this
> 2016-5 script.
>
> Try its matching script
> uboot.2014.07-tld-1.environment.scr in this post:
>
> https://forum.doozan.com/read.php?3,9810,23956#msg-23956

OK I'll try this
Can I updated to the latest uboot then ?

bodhi

My current uboot can boot with the Debian 4.4 rootfs?



Edited 1 time(s). Last edit at 06/30/2018 11:37PM by Jxjhheric.
Reply Quote
Jxjhheric
Re: Help Pogoplug e02 and V4 won't boot
July 01, 2018 02:21AM
bodhi Wrote:
-------------------------------------------------------
> Jxjhheric,
>
> Ah! u-boot 2014.07-tld-1 is a little old for this
> 2016-5 script.
>
> Try its matching script
> uboot.2014.07-tld-1.environment.scr in this post:
>
> https://forum.doozan.com/read.php?3,9810,23956#msg-23956


the same as first 

 Name:   Linux-4.12.1-kirkwood-tld-1
   Created:      2018-06-30  12:44:32 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3831812 Bytes = 3.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.12.1-kirkwood-tld-1
   Created:      2017-07-24   0:18:23 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7245632 Bytes = 6.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
Using machid 0x831 from environment

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Reply Quote
bodhi
Re: Help Pogoplug e02 and V4 won't boot
July 01, 2018 02:43AM
Try the same procedure, with with the script attached in this post.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
Attachments:
open | download - uboot.2014.07-tld-3.environment.scr (2.8 KB)
Jxjhheric
Re: Help Pogoplug e02 and V4 won't boot
July 01, 2018 06:49AM
use the Debian 4.4 rootfs to boot successful and update the lastest uboot and roofs ！

now working well

Thanks bodhi！！

but another problem appear：

i want to use a usb audio card on usb，

when a usb harddisk is plugging at the top usb port , i plug the audio card on back usb port

and get this log from dmesg 


usb 2-2: new full-speed USB device number 2 using xhci_hcd
[  370.022730] usb 2-2: New USB device found, idVendor=08bb, idProduct=2704
[  370.029416] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  370.036560] usb 2-2: Product: USB Audio DAC   
[  370.040989] usb 2-2: Manufacturer: Burr-Brown from TI              
[  370.555274] input: Burr-Brown from TI               USB Audio DAC    as /devices/platform/mbus@f1000000/mbus@f1000000:pcie-controller@82000000/pci0000:00/0000:00:01.0/0000:01:00.0/usb2/2-2/2-2:1.2/0003:08BB:2704.0001/input/input1
[  370.652180] hid-generic 0003:08BB:2704.0001: input,hidraw0: USB HID v1.00 Device [Burr-Brown from TI               USB Audio DAC   ] on usb-0000:01:00.0-2/input2
[  370.674189] usbcore: registered new interface driver usbhid
[  370.679946] usbhid: USB HID core driver
[  370.688571] usbcore: registered new interface driver snd-usb-audio
[  465.981450] usb 2-2: timeout: still 3 active urbs on EP #2
[  466.981454] usb 2-2: timeout: still 3 active urbs on EP #2
[  470.001426] xhci_hcd 0000:01:00.0: xHCI host not responding to stop endpoint command.
[  470.009246] xhci_hcd 0000:01:00.0: xHCI host controller not responding, assume dead
[  470.016912] xhci_hcd 0000:01:00.0: HC died; cleaning up
[  470.022793] usb 2-2: USB disconnect, device number 2
[  470.027932] xhci_hcd 0000:01:00.0: Timeout while waiting for configure endpoint command
[  470.036718] usb 2-2: Not enough bandwidth for altsetting 0
Reply Quote
bodhi
Re: Help Pogoplug e02 and V4 won't boot
July 01, 2018 04:36PM
Jxjhheric,

> i want to use a usb audio card on usb，
>
> when a usb harddisk is plugging at the top usb
> port , i plug the audio card on back usb port
>

The USB 3.0 ports in the back should work fine. Perhaps it got something to do with your gadget. Try plug it in after the system has booted.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
Newer Topic Older Topic
Author:

Your Email:


Subject:
Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: