On Wednesday 28 October 2009 20:10:52 Maxim Wexler wrote:
Not sure this is related with the OP's problem, I have noticed that
on my
system I can scroll up in a console if it displays the output of a
command, e.g. ls, but I cannot scroll up on the boot messages. Also, I
cannot scroll up
On Monday 09 November 2009 11:07:15 Amit Dor-Shifer wrote:
On Wednesday 28 October 2009 20:10:52 Maxim Wexler wrote:
Not sure this is related with the OP's problem, I have noticed that
on my
system I can scroll up in a console if it displays the output of a
command, e.g. ls, but
On Tuesday 27 October 2009 09:10:13 Alan McKinnon wrote:
You enabled scrollback so now the console has retained enough of the kernel
console output that you can scroll back to the beginning without using all
128K.
Symbol: VGACON_SOFT_SCROLLBACK_SIZE [=256]
Prompt: Scrollback Buffer
On Wednesday 28 October 2009 03:50:56 Maxim Wexler wrote:
So, since in the digital world, things don't just happen, can
someone enlighten me, or anyone else who's interested, in the
connection between the scrollback buffer and usb-storage, if any?
There isn't a connection. Why do you
Not sure this is related with the OP's problem, I have noticed that on my
system I can scroll up in a console if it displays the output of a command,
e.g. ls, but I cannot scroll up on the boot messages. Also, I cannot scroll
up on the log messages on VT12. Is there something that I need to
On Wednesday 28 October 2009 20:10:52 Maxim Wexler wrote:
Not sure this is related with the OP's problem, I have noticed that on my
system I can scroll up in a console if it displays the output of a
command, e.g. ls, but I cannot scroll up on the boot messages. Also, I
cannot scroll up on
On Tuesday 27 October 2009 03:38:53 Maxim Wexler wrote:
Ok, this is too weird. While mucking around in the kernel I noticed
that the scroll back buffer wasn't set. So I configured it and gave it
128 bytes to play with.
It's 128 kilo bytes just btw :-)
Sez I, well at least I'll be able to
So, since in the digital world, things don't just happen, can
someone enlighten me, or anyone else who's interested, in the
connection between the scrollback buffer and usb-storage, if any?
There isn't a connection. Why do you think there is one?
Because, before the scrollback buffer was
On 10/25/09, Keith Dart ke...@dartworks.biz wrote:
=== On Sun, 10/25, Maxim Wexler wrote: ===
Did I leave something out of the kernel? I can't think what.
===
It looks like you have USB debug turned on. I remember there was a
kernel that was released that had that. Normally it's off, but
#CONFIG_USB_DEBUG is not set
[edit]
CONFIG_USB_STORAGE_DEBUG = y
I turned it off, recompiled, copied the kernel over and rebooted.
$dmesg still displays the verbose 'usb-storage' lines and excludes
everything else
here's a long thread on this same subject
Ok, this is too weird. While mucking around in the kernel I noticed
that the scroll back buffer wasn't set. So I configured it and gave it
128 bytes to play with. Sez I, well at least I'll be able to scroll
back to the start of all that verbiage. That's the only change I've
made since turning
Hi group,
Still sorting out the glitches in the new 2.6.30-r7 kernel.
eg the strange output of dmesg:
...
age: 1e 00 00 00 01 00
usb-storage: Bulk Command S 0x43425355 T 0x8 L 0 F 0 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred
=== On Sun, 10/25, Maxim Wexler wrote: ===
Did I leave something out of the kernel? I can't think what.
===
It looks like you have USB debug turned on. I remember there was a
kernel that was released that had that. Normally it's off, but you
should turn it off if it's on.
-- Keith Dart
--
13 matches
Mail list logo
