Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]tlug: New Kernel + XEmacs = BAD medicine (sound-related?)
- To: tlug@example.com
- Subject: tlug: New Kernel + XEmacs = BAD medicine (sound-related?)
- From: Matt Gushee <matt@example.com>
- Date: Tue, 21 Jul 1998 17:36:19 +0900
- Content-Type: text/plain; charset=US-ASCII
- In-Reply-To: <13748.15776.258635.849234@example.com>
- References: <199807210750.QAA04176@example.com><13748.15776.258635.849234@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
Stephen J. Turnbull writes: > >>>>> "Matt" == Matt Gushee <matt@example.com> writes: > > Matt> As part of my never-ending quest to get my sound card > Matt> working, I compiled a new 2.0.34 kernel yesterday. It seems > Matt> to work, and I finally have sound (hallelujah!), but there's > Matt> a serious catch. Twice yesterday, I booted up with the new > Matt> kernel, started up XEmacs, and was typing away when -- POOF! > Matt> The system was hung ... couldn't do anything with the > Matt> keyboard or mouse. So I had to do a hard reset. Ouch. > > Version of XEmacs? Oh, that was dumb of me. 20.3, home-built w/ glibc 2.0.5 (now using 2.0.7). > Did you try switching virtual consoles? Yes, I tried that, tried killing X with Ctrl-Alt-Backspace, tried rebooting with Ctrl-Alt-Del ... the keyboard was completely dead. No Caps Lock, no Num Lock, no nothing. All I could do was turn off the power. > Did you try telneting in over the net? I don't run telnetd. I suppose I could, if that would be a good test strategy. > Matt> My system is RedHat 5.0, or was. Actually, I've updated so > Matt> many packages it's probably closer to 5.1. > > But with Red Hat, who knows what that means.... :-( Indeed. > I've had luck with > > make modules; make modules; make modules_install I'll try that. > Matt> Maybe related to the above: at boot time, there were several > Matt> 'undefined kernel symbol' error messages, all involving > Matt> sound drivers. > > I'd fix that before worrying about XEmacs or any other applications. > Any X program is capable of hanging your system if it grabs the X > server, but Emacsen are pretty polite. Yeah, that's what I thought. Actually, I tried another build today, and this time the crash came when I tried to start X Windows. So I guess I better do something about the undefined kernel symbols, once I figure out how ... I've read and followed all the instructions I've found so far, so I'm sort of mystified, but I'll keep looking, I guess. Matt Gushee Oshamanbe, Hokkaido -------------------------------------------------------------- Next Meeting: 8 August, Tokyo Station Yaesu central gate 12:30 featuring Linux on multiple platforms: i386, Sparc, PA-Risc, Amiga, SGI, Alpha, PalmPilot, ... Next Nomikai: September, 19:30 Tengu TokyoEkiMae 03-3275-3691 -------------------------------------------------------------- Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp
- Follow-Ups:
- tlug: New Kernel + XEmacs = BAD medicine (sound-related?)
- From: "Stephen J. Turnbull" <turnbull@example.com>
- References:
- tlug: New Kernel + XEmacs = BAD medicine (sound-related?)
- From: Matt Gushee <matt@example.com>
- tlug: New Kernel + XEmacs = BAD medicine (sound-related?)
- From: "Stephen J. Turnbull" <turnbull@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: tlug: Re: Xemacs
- Next by Date: tlug: New Kernel + XEmacs = BAD medicine (sound-related?)
- Prev by thread: tlug: New Kernel + XEmacs = BAD medicine (sound-related?)
- Next by thread: tlug: New Kernel + XEmacs = BAD medicine (sound-related?)
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links