Tiny Core Linux

Tiny Core Extensions => TCE Talk => Topic started by: Daniel on July 28, 2011, 04:21:37 AM

Title: Restore behind USB hub problem
Post by: Daniel on July 28, 2011, 04:21:37 AM

Hi all,

I am trying to use TCL 3.8rc2 on an usb key (with syslinux 4.04).
Boot perfectly :) on my machine (with backup configuration).

BUT if i put the usb key behind an usb hub, no restore is done at boot time!

I join /var/log/messages ... here : http://dl.free.fr/r7e3KNFJ9 (http://dl.free.fr/r7e3KNFJ9)

I don't know if it is a TCL problem or a maybe BIOS problem!

Thanks
Daniel.

[Edit]
I can't see usb boot device /dev/sdxx ... impossible to mount!

Title: Re: Restore behind USB hub problem
Post by: Juanito on July 28, 2011, 04:36:29 AM

perhaps you need to increase the usb boot delay when your stick is behind a hub?

boot code "waitusb=x" - try x=10 for 10 seconds

Title: Re: Restore behind USB hub problem
Post by: Daniel on July 28, 2011, 04:42:35 AM

I do test with x=10: same results :(

Thanks
Daniel.

Title: Re: Restore behind USB hub problem
Post by: Juanito on July 28, 2011, 04:45:55 AM

Did you try referring to your stick using uuid or a label - maybe its name changes behind a hub?

see:

http://wiki.tinycorelinux.net/wiki:uuid

Title: Re: Restore behind USB hub problem
Post by: Daniel on July 28, 2011, 05:25:05 AM

No.
the normal syslinux command is

Code: [Select]

append boot=/ initrd=/tinycore.gz vga=789 modeset=1 kmaps=fr-latin9  quiet splash
It runs perfectly without usb hub.


I don't see my usb key in /dev/sdx ( i see /dev/sda +1 to 9 and /dev/sdb +1 to 9 ) : i have only 2 partitions.

it is as the usb boot key device is not seen on usb.

[edit]
I can't mount the device!
and if i force it, there is no file!

If i put an other usb key in the hub, it is seen.


D.

Title: Re: Restore behind USB hub problem
Post by: Juanito on July 28, 2011, 05:43:03 AM

You could try something like this:

Code: [Select]

label microcore
kernel /boot/bzImage
append initrd=/boot/microcore.gz quiet noswap tce=UUID=aaab6273-4a6c-4118-8eb2-e31a9b31edb3 waitusb=20:UUID=aaab6273-4a6c-4118-8eb2-e31a9b31edb3

..substituting your usb stick uuid and where "waitusb=20:UUID=.." means wait 20s or until device UUID=.. shows up on the usb bus.

Other than this, you could boot "base norestore" with your usb stick plugged directly into you machine and, once booted, remove the stick and reconnect behind the hub to check that it is recognised.

Title: Re: Restore behind USB hub problem
Post by: Daniel on July 28, 2011, 08:14:56 AM

First test : same results.

Second test : usb key not seen under usb HUB.
More : /dev/sda, /dev/sda1 and /dev/sda2 are missing (not /dev/sda3 to 9). (under usb HUB)
And no other usb key plugged is seen under usb HUB.

Thanks,
D.

Title: Re: Restore behind USB hub problem
Post by: gerald_clark on July 28, 2011, 08:39:48 AM

Maybe it is not a usb 2.x hub.  Can yo try another one?

Title: Re: Restore behind USB hub problem
Post by: Juanito on July 28, 2011, 08:40:57 AM

Quote from: Daniel on July 28, 2011, 08:14:56 AM

First test : same results.

I take it you mean you tried identifying the usb stick with a UUID and this didn't work with the hub, but it did work when plugged directly?

Quote

Second test : usb key not seen under usb HUB.

This would seem to indicate that this particular usb stick and the hub don't seem to work together.

Quote

And no other usb key plugged is seen under usb HUB.

..but earlier on you said "If i put an other usb key in the hub, it is seen."??

Title: Re: Restore behind USB hub problem
Post by: Daniel on July 28, 2011, 09:11:24 AM

D-Link USB2 Hub.

Yes, it runs without usb HUB and with UUID.
But not under usb Hub.


No. It runs with ubuntu and the same key.


Yes. it was.
It was not seen when i boot without usb Hub, and when i plug the boot device behind the ush hub after.
Then no other usb key is seen.

D.

[Edit]
syslinux.cfg param:

Code: [Select]

append boot=/ initrd=/tinycore.gz tce=UUID=2EEC-4DCC waitusb=20:UUID=2EEC-4DCC  vga=789 modeset=1 kmaps=fr-latin9 quiet splash debug syslog


Title: Re: Restore behind USB hub problem
Post by: Daniel on July 28, 2011, 09:46:52 AM

Be carreful : the problem may come from the BIOS.

I know there is BIOS problem with to many usb devices plugged!

But in this case, i don't know if it is that (after boot).

D.

Title: Re: Restore behind USB hub problem
Post by: Rich on July 28, 2011, 02:53:28 PM

Hi Daniel
What is the result of entering the following at the command line?
blkid -U 2EEC-4DCC

Title: Re: Restore behind USB hub problem
Post by: maro on July 28, 2011, 05:47:05 PM

Maybe it would help if we would know the fuller picture by having the complete 'dmesg' output for both boot scenarios (i.e. directly connected USB device and connected "behind" a USB bus). Something unexpected seems to happen here, so a bit more visibility might be helpful.

Daniel, would you please produce those two files and attach them here.

Title: Re: Restore behind USB hub problem
Post by: Daniel on July 29, 2011, 03:09:57 AM

Quote from: Rich on July 28, 2011, 02:53:28 PM

blkid -U 2EEC-4DCC

result :

Code: [Select]

/dev/sda1

Title: Re: Restore behind USB hub problem
Post by: Daniel on July 29, 2011, 04:03:56 AM

Quote from: maro on July 28, 2011, 05:47:05 PM

directly connected USB device

http://dl.free.fr/vRO2ct2uF
 (http://dl.free.fr/vRO2ct2uF)

Quote from: maro on July 28, 2011, 05:47:05 PM

connected "behind" a USB bus

http://dl.free.fr/h92iYKznR (http://dl.free.fr/h92iYKznR)

D.

Title: Re: Restore behind USB hub problem
Post by: Daniel on August 04, 2011, 04:23:05 AM

In fact, there is realy a bios problem (in my case) AND a tcl on USB behind hub problem.
The hadware manufacturer is on the bios problem (in contact with haward).

I won't use a hub for tcl booting! (used for bios analyse).
But in case of problem, if i can help to remove it... :)
(i don't think it is only a TCL problem!!!)

Thanks,
Daniel.

Title: Re: Restore behind USB hub problem
Post by: Daniel on August 04, 2011, 10:38:42 AM

Does anyone know what happend during disk formating (and mount) in relation with Bios?


In fact, i've got a specific modified BIOS version for USB-DOM key identification.
But i tried without and i've got the "missing codepage..." message when i tried to mount the key on an other machine.

Then, i think the mkfs function may use Bios informations.
If i'm right, all my USB problems can be solved with a good Bios version. :)

I know, it is not a specific TCL question.
But ...  ;D

Thanks
Daniel.