Skip to contentSkip to conversation

Console on USB

DISCUSSION Pete Zaitcev 3 participants 4 messages Aug 20, 2003 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 3 lines

So I ordered a USB to serial converter, configured a 2.6.0-test3
kernel, added a console=/dev/ttyUSB0 to the kernel command line and connected this to my desktop with a null modem adapter.

What made you think this will work?!

Quoted 1 line

Is there any advice I might be able to use to get this going?

You'd have to write it. Grep for register_console for starters. But I do not advise it, see below.

Quoted 1 line

I really want to be able to catch some oops output.

If oops happens with interrupts closed, forget about it. USB needs interrupts to work. This is one of the reasons nobody bothered to implement console over USB serial.

You will have a better chance using Ingo's netconsole, if a patch for your Ethernet driver exists.

-- Pete

#2 lore raw
Quoted 5 lines
Quoted 3 lines

So I ordered a USB to serial converter, configured a 2.6.0-test3
kernel, added a console=/dev/ttyUSB0 to the kernel command line and connected this to my desktop with a null modem adapter.

What made you think this will work?!

Maybe the drivers/usb/serial/Kconfig file?

config USB_SERIAL_CONSOLE
bool "USB Serial Console device support (EXPERIMENTAL)" depends on USB_SERIAL=y && EXPERIMENTAL

Quoted 4 lines
Quoted 1 line

Is there any advice I might be able to use to get this going?

You'd have to write it. Grep for register_console for starters. But I do not advise it, see below.

usb/serial/console.c:255: register_console(&usbcons);

Quoted 5 lines
Quoted 1 line

I really want to be able to catch some oops output.

If oops happens with interrupts closed, forget about it. USB needs interrupts to work. This is one of the reasons nobody bothered to implement console over USB serial.

The call to register_console() also happens very late in the boot sequence, so if your oops is early, USB console won't help.

Quoted 2 lines

You will have a better chance using Ingo's netconsole, if a patch for your Ethernet driver exists.

Certainly, I agree.

~Randy

#3 lore raw
Quoted 8 lines

Date: Tue, 19 Aug 2003 21:58:45 -0700 (PDT)
From: "Randy.Dunlap" <[email protected]>

Quoted 3 lines
Quoted 1 line

Is there any advice I might be able to use to get this going?

You'd have to write it. Grep for register_console for starters.

usb/serial/console.c:255: register_console(&usbcons);

Eeek, eating a crow now.

Quoted 8 lines
Quoted 5 lines
Quoted 1 line

I really want to be able to catch some oops output.

If oops happens with interrupts closed, forget about it. USB needs interrupts to work. This is one of the reasons nobody bothered to implement console over USB serial.

The call to register_console() also happens very late in the boot sequence, so if your oops is early, USB console won't help.

It's true for many consoles, that's why sparc allows "-p" in SILO options, for instance. I think either wli or willy did "early VGA printk" patch.

Interrupts are a major problem. Also, the USB stack is pretty thick.

-- Pete

#4 lore raw
In reply to Randy.Dunlap
Quoted 4 lines · Randy.Dunlap
Quoted 2 lines

You will have a better chance using Ingo's netconsole, if a patch for your Ethernet driver exists.

Certainly, I agree.

I think Matt Mackall has an updated patch which looks frightfully easy to add device support to, i think he may have even made it generic (he basically just calls netdriver isrs)