USB CD-ROM Boot fails with TSST SE-S084D

[GoogleCodeExporter]

I just bought a Toshiba Samsung Storage Technology SE-S084D External DVD 
Writer. I can boot and run at least one Linux distro (Parted Magic) off of it, 
so I know it works and plays reasonably nicely with my BIOS and motherboard. 
However, when I try to boot 9front from a CD in this drive, the drive does not 
show up on the list of source devices to pick from--it does notice my hard 
drive and (broken) internal CD drive. I also get the following possibly 
relevant messages at startup:

usbehci: multiple controllers present
ehci 0xe000200: port1 didn't register after 500ms; sts0x1101
ehci 0xe000100: port1 didn't register after 500ms; sts0x1101

I've tried booting with *noehci=1, which seems to make no difference at all.

Original issue reported on code.google.com by Ansche...@gmail.com on 18 Sep 2011 at 12:56

[GoogleCodeExporter]

Please post brand and model information about your laptop.

Original comment by stanley....@gmail.com on 18 Sep 2011 at 2:02

[GoogleCodeExporter]

Laptop is a Lenovo IdeaPad V460.

Original comment by Ansche...@gmail.com on 18 Sep 2011 at 2:20

[GoogleCodeExporter]

do any usb devices work? on the root is from prompt, type !rc
on the rc shell, run: 

cat /dev/usbevent & 

then try to pull and plugin the usb cdrom. if nothing happens then
we have a problem with the usb controller or the hub.

if that seems to work, it might be the usb cdrom itself.

i suggest you go to #cat-v irc channel and we trouble shoot this.

Original comment by cinap_le...@felloff.net on 19 Sep 2011 at 6:08

[GoogleCodeExporter]

another idea: usb devices are enumerated in the background, so you might
not see them in the "devices found" list. theres a usbdelay= parameter
in plan9.ini but its not used by default. try waiting some time... 
then enter xxx or some other invalid bootline to let it rescan for
devices. or just run !rc and look for usb devices yourself. 
ls /shr ls /dev/sdU*

Original comment by cinap_le...@felloff.net on 19 Sep 2011 at 6:17

[GoogleCodeExporter]

Nothing happens when I cat /dev/usbevent and unplug and replug the drive. 
Waiting does not seem to be working either, unless I'm not waiting long enough.

Original comment by Ansche...@gmail.com on 20 Sep 2011 at 2:22

[GoogleCodeExporter]

ok, this is clearly a usb problem :/

Original comment by cinap_le...@felloff.net on 6 Oct 2011 at 11:44

[GoogleCodeExporter]

Let me know if there's any way I can help debug/fix this.

Original comment by Ansche...@gmail.com on 7 Oct 2011 at 3:55

[GoogleCodeExporter]

Original comment by cinap_le...@felloff.net on 4 Nov 2011 at 11:04

• Added labels: Subsystem-Drivers

[GoogleCodeExporter]

Anschelsc:

Try booting with the following:

*nousbehci=1

and/or

*nousbuhci=1

then follow the troubleshooting steps outlined above again.

Original comment by stanley....@gmail.com on 9 Nov 2011 at 5:28

[GoogleCodeExporter]

could you try the latest iso? there where some mp interrupt
problems that prevented usb from working on some thinkpads.

try booting in mp mode by removing the *nomp= kernel parameter.

Original comment by cinap_le...@felloff.net on 22 May 2012 at 5:24

• Changed state: BasiclySound

[GoogleCodeExporter]

As far as I can tell that still doesn't help; I assume that to "remove the 
*nomp= kernel parameter" I boot with "*nomp=0". Is there something else I 
should do? Should I combine this with one of the above options?

Original comment by Ansche...@gmail.com on 23 May 2012 at 12:41

[GoogleCodeExporter]

usualy, one omits the parameter completly to "disable" it
as most of the drivers just do a check like:

if(getconf(*foobar")) return;

and ignore its value. but *nomp is an exception doing
a strcmp() for "0" here.

too bad it didnt work. :( was just a guess as we recently
had a machine that just had fucked up mp tables causing
interrupts getting configured incorrectly.

grab usb spec and start experimenting / debugging? check
how far the driver gets... if we skip any steps mentioned
in the spec?

Original comment by cinap_le...@felloff.net on 23 May 2012 at 1:50

[GoogleCodeExporter]

this looks closely related to issue #101

Original comment by cinap_le...@felloff.net on 25 Nov 2012 at 3:12

[GoogleCodeExporter]

try latest iso, some usb issues have been fixed

Original comment by cinap_le...@felloff.net on 26 Nov 2012 at 8:53

[GoogleCodeExporter]

Original comment by cinap_le...@felloff.net on 2 Dec 2012 at 12:58

• Changed state: NeedsTesting

[GoogleCodeExporter]

I don't currently have the drive with me; I'll hopefully get my hands on it in 
a week or three.

Original comment by Ansche...@gmail.com on 3 Dec 2012 at 2:40

[GoogleCodeExporter]

still alive?

Original comment by cinap_le...@felloff.net on 28 Oct 2013 at 4:37

[GoogleCodeExporter]

Original comment by cinap_le...@felloff.net on 29 Nov 2013 at 4:07

• Changed state: Fixed