john stultz wrote: > Hmmm. Just to make sure I understand the situation: If you log in via > ssh, and run dmesg, you do see your driver's output, but that output > just doesn't get to syslog until you press a key on your keyboard? Exactly. Thanks, Tilman -- Tilman Schmidt E-Mail: [email protected] Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeoeffnet mindestens haltbar bis: (siehe Rueckseite)
Attachment:
signature.asc
Description: OpenPGP digital signature
- Follow-Ups:
- Re: Linux v2.6.18-rc1: printk delays
- From: Tilman Schmidt <[email protected]>
- Re: Linux v2.6.18-rc1: printk delays
- References:
- Re: Linux v2.6.18-rc1: printk delays
- From: Tilman Schmidt <[email protected]>
- Re: Linux v2.6.18-rc1: printk delays
- From: john stultz <[email protected]>
- Re: Linux v2.6.18-rc1: printk delays
- From: Tilman Schmidt <[email protected]>
- Re: Linux v2.6.18-rc1: printk delays
- From: john stultz <[email protected]>
- Re: Linux v2.6.18-rc1: printk delays
- Prev by Date: Re: [Suspend2-devel] Re: swsusp / suspend2 reliability
- Next by Date: Re: AVR32 architecture patch against Linux 2.6.18-rc1 available
- Previous by thread: Re: Linux v2.6.18-rc1: printk delays
- Next by thread: Re: Linux v2.6.18-rc1: printk delays
- Index(es):
 |