Re: [gentoo-user] strange dmesg output - RESOLVED

2009-11-09 Thread Alan McKinnon
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 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 set up in the kernel? In the old days (perhaps different
>  > > machine?) I used to be able to
>  > > scroll up in both.
>  >
>  > Also note, if you migrate away from the boot console and then come
>  > back, it may not scrollback at all. If I want to see what boot is
>  > doing I scroll back immediately before running startx or moving to
>  > another console.
> 
> Maxim (or anyone else):
> do you know what causes scrollback to be disabled once you move to a
> different terminal?
> Amit
> 

The scrollback buffer is global, not per-VT

So when you change VT, the buffer must go away other wise you have wrong text 
on the wrong terminal.

-- 
alan dot mckinnon at gmail dot com



Re: [gentoo-user] strange dmesg output - RESOLVED

2009-11-09 Thread Amit Dor-Shifer

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 the log messages on VT12. Is there something that I
> > need to set up in the kernel? In the old days (perhaps different
> > machine?) I used to be able to
> > scroll up in both.

> Also note, if you migrate away from the boot console and then come
> back, it may not scrollback at all. If I want to see what boot is
> doing I scroll back immediately before running startx or moving to
> another console.

Maxim (or anyone else):
do you know what causes scrollback to be disabled once you move to a 
different terminal?

Amit



Re: [gentoo-user] strange dmesg output - RESOLVED

2009-10-28 Thread Mick
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 the log messages on VT12.  Is there something that I
> > need to set up in the kernel?  In the old days (perhaps different
> > machine?) I used to be able to
> > scroll up in both.

> Also note, if you migrate away from the boot console and then come
> back, it may not scrollback at all.  If I want to see what boot is
> doing I scroll back immediately before running startx or moving to
> another console.

I think that you may have put your finger on the problem here.  I used to run 
startx from the console - now run xdm.  So it may have been that it worked 
back then because I would scroll up before leaving the console.  However, I 
seem to recall that it also worked with VT12.  May be I'm wrong, not sure.
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] strange dmesg output - RESOLVED

2009-10-28 Thread Maxim Wexler
>
> 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 set up in
> the kernel?  In the old days (perhaps different machine?) I used to be able
> to
> scroll up in both.

On my unit, /var/log/messages re-iterates F12. If I want to read  it I
use less, tail, grep in a terminal as root.

Also note, if you migrate away from the boot console and then come
back, it may not scrollback at all.  If I want to see what boot is
doing I scroll back immediately before running startx or moving to
another console.

HTH



Re: [gentoo-user] strange dmesg output - RESOLVED

2009-10-28 Thread Alan McKinnon
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 think there is one?
> 
> Because, before the scrollback buffer was configured,  when I ran
> $dmesg|less the output, ie more that 2700 lines, that came up in the
> console, all started with 'usb-storage'. After configuring the
> scrollback buffer, there may have been a few usb-console lines but
> certainly not 2700, and nothing else, one right after another.
> 
> I understand it makes no sense to say there is a connection but that
> is what I saw.
> 
> It may have been intermittant. I notice with successive reboots of
> 2.6.30, /dev/sdb1,2, which contain /home and /var are sometimes not
> found and not mounted; sometimes not found but mounted anyways;
> sometimes found and mounted as per /etc/fstab. If it happens enough
> times, I suppose a pattern will emerge but I haven't seen it yet.

I think the presence or absence of your usb-storage debug output is related to 
stuff being found or not found, and has nothing whatsoever to do with 
scrollback.


-- 
alan dot mckinnon at gmail dot com



Re: [gentoo-user] strange dmesg output - RESOLVED

2009-10-27 Thread Mick
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 Size (in KB)
>   Defined at drivers/video/console/Kconfig:37
>   Depends on: HAS_IOMEM && VT && VGACON_SOFT_SCROLLBACK
> 
> Symbol: VGACON_SOFT_SCROLLBACK [=y]
> Prompt: Enable Scrollback Buffer in System RAM
>   Defined at drivers/video/console/Kconfig:22
>   Depends on: HAS_IOMEM && VT && VGA_CONSOLE

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 set up in 
the kernel?  In the old days (perhaps different machine?) I used to be able to 
scroll up in both.

$ cat /usr/src/linux/.config | grep SCROLLBACK
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=128
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] strange dmesg output - RESOLVED

2009-10-27 Thread Maxim Wexler
>> 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 configured,  when I ran
$dmesg|less the output, ie more that 2700 lines, that came up in the
console, all started with 'usb-storage'. After configuring the
scrollback buffer, there may have been a few usb-console lines but
certainly not 2700, and nothing else, one right after another.

I understand it makes no sense to say there is a connection but that
is what I saw.

It may have been intermittant. I notice with successive reboots of
2.6.30, /dev/sdb1,2, which contain /home and /var are sometimes not
found and not mounted; sometimes not found but mounted anyways;
sometimes found and mounted as per /etc/fstab. If it happens enough
times, I suppose a pattern will emerge but I haven't seen it yet.

mw



Re: [gentoo-user] strange dmesg output - RESOLVED

2009-10-27 Thread Alan McKinnon
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 scroll
> back to the start of all that verbiage. That's the only change I've
> made since turning USB_STORAGE debugging off.
> 
> After a reboot, dmesg behaved and gives me a complete rundown on
> startup all the way back to the prompt!
> 
> 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?

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 Size (in KB)
  Defined at drivers/video/console/Kconfig:37
  Depends on: HAS_IOMEM && VT && VGACON_SOFT_SCROLLBACK

Symbol: VGACON_SOFT_SCROLLBACK [=y]
Prompt: Enable Scrollback Buffer in System RAM
  Defined at drivers/video/console/Kconfig:22
  Depends on: HAS_IOMEM && VT && VGA_CONSOLE

Symbol: USB_STORAGE [=m]
Prompt: USB Mass Storage support
  Defined at drivers/usb/storage/Kconfig:9
  Depends on: USB_SUPPORT && USB && SCSI

Symbol: USB_STORAGE_DEBUG [=n]
Prompt: USB Mass Storage verbose debug
  Defined at drivers/usb/storage/Kconfig:27
  Depends on: USB_SUPPORT && USB_STORAGE

Symbol: USB_SUPPORT [=y]
Prompt: USB support
  Defined at drivers/usb/Kconfig:5 
  Depends on: HAS_IOMEM 


-- 
alan dot mckinnon at gmail dot com



Re: [gentoo-user] strange dmesg output - RESOLVED

2009-10-26 Thread Maxim Wexler
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 USB_STORAGE debugging off.

After a reboot, dmesg behaved and gives me a complete rundown on
startup all the way back to the prompt!

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?

mw



Re: [gentoo-user] strange dmesg output

2009-10-26 Thread Maxim Wexler
> #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

https://lists.one-eyed-alien.net/pipermail/usb-storage/2008-November/004121.html

I don't think he found a solution either.

The good news, the system can now see the soundcard. Before I had to
run alsaconf at every boot.  Is there a connection?

mw



Re: [gentoo-user] strange dmesg output

2009-10-26 Thread Maxim Wexler
On 10/25/09, Keith Dart  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 you
> should turn it off if it's on.

#CONFIG_USB_DEBUG is not set



Re: [gentoo-user] strange dmesg output

2009-10-25 Thread Keith Dart
=== 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

-- 

-- ~
   Keith Dart 
   public key: ID: 19017044
   
   =



[gentoo-user] strange dmesg output

2009-10-25 Thread Maxim Wexler
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 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x8 R 0 Stat 0x1
usb-storage: -- transport indicates command failure
usb-storage: Issuing auto-REQUEST_SENSE
usb-storage: Bulk Command S 0x43425355 T 0x9 L 18 F 128 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_sglist: xfer 18 bytes, 1 entries
usb-storage: Status code 0; transferred 18/18
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
...

and so on, for 2739 lines. Nothing about other drives, file sytems,
hardware, busses etc. When I plug in a usb key, for instance, dmesg
doesn't even notice although the log console(F12) makes a note of the
device. The earlier kernel acts "normally".

Did I leave something out of the kernel? I can't think what.

Maxim



Re: [gentoo-user] Strange dmesg

2005-07-03 Thread Jean Magnan de Bornier
Le 02 juillet à 00:40:14 Bryan Whitehead <[EMAIL PROTECTED]> écrit notamment:

| Disable legacy USB support ?
| 
| On Fri, 1 Jul 2005, Jean Magnan de Bornier wrote:
| 
| > Hi all,
| > I have a strange message at boot, appearing at various places; then typing
| > dmesg, I get the same message many times repeated, with nothing else:
| >
| > drivers/usb/input/hid-core.c: input irq status -75 received
| >
| > 261 lines of that in dmesg!
| >
| >
| > I switched kernel at least one time since it began some time ago.
| > Here is what I have in my kernel as far as HID goes:
| >
| > [EMAIL PROTECTED]:/home/jean# grep HID /usr/src/linux/.config
| > CONFIG_USB_HID=y
| > CONFIG_USB_HIDINPUT=y
| > # CONFIG_HID_FF is not set
| > # CONFIG_USB_HIDDEV is not set
| > # CONFIG_USB_PHIDGETKIT is not set
| > # CONFIG_USB_PHIDGETSERVO is not set

[...]
 
Hi all,
well I made some tests with usbhid, trying to put as module rather than
into the kernel, no change!

Bryan thanks but I'm sorry, I don't know what 'Disable legacy USB support'
refers to; is it an option in the kernel (saw nothing of that sort)?

any hint still welcome
-- 
Jean Magnan de Bornier  |   email: jean-at-bornier.net
 

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Strange dmesg

2005-07-01 Thread Bryan Whitehead

Disable legacy USB support ?

On Fri, 1 Jul 2005, Jean Magnan de Bornier wrote:


Hi all,
I have a strange message at boot, appearing at various places; then typing
dmesg, I get the same message many times repeated, with nothing else:

drivers/usb/input/hid-core.c: input irq status -75 received

261 lines of that in dmesg!


I switched kernel at least one time since it began some time ago.
Here is what I have in my kernel as far as HID goes:

[EMAIL PROTECTED]:/home/jean# grep HID /usr/src/linux/.config
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
# CONFIG_USB_PHIDGETKIT is not set
# CONFIG_USB_PHIDGETSERVO is not set

Nothing seems to be broken though; so I'm maybe just curious, but wtf does
that mean?
TIA



--
Bryan Whitehead
Email:[EMAIL PROTECTED]
--
gentoo-user@gentoo.org mailing list



[gentoo-user] Strange dmesg

2005-07-01 Thread Jean Magnan de Bornier
Hi all,
I have a strange message at boot, appearing at various places; then typing
dmesg, I get the same message many times repeated, with nothing else:

drivers/usb/input/hid-core.c: input irq status -75 received

261 lines of that in dmesg!


I switched kernel at least one time since it began some time ago.
Here is what I have in my kernel as far as HID goes:

[EMAIL PROTECTED]:/home/jean# grep HID /usr/src/linux/.config   
   
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
# CONFIG_USB_PHIDGETKIT is not set
# CONFIG_USB_PHIDGETSERVO is not set

Nothing seems to be broken though; so I'm maybe just curious, but wtf does
that mean?
TIA
-- 
Jean Magnan de Bornier  |   email: jean-at-bornier.net
 
-- 
gentoo-user@gentoo.org mailing list