Hello,
I have several problems with my computer (running RedHat 6.2) under Linux
2.4.1 kernel. (See attached files for more information).
Here is a short summary:
1) Audio card (based on SiS chipset) does not work due to incorrect
initialization of PCI resources. It seems that this is not a problem of
audio driver, but may be I am wrong.
The kernel prints this message:
PCI: Cannot allocate resource region 0 of device 00:01.4
got res[1000:10ff] for resource 0 of Silicon Integrated Systems [SiS]
SiS PCI Audio Accelerator
2) Frame-buffer mode does not work with my video card SiS630.
But ok, frame-buffer mode is EXPERIMENTAL in linux.
Computer boots, but screen is blank. All messages are fine.
3) Kernel prints (working with DVD-ROM)
hdc: packet command error: status=0x51 { DriveReady SeekComplete Error}
I tried CONFIG_IDEDISK_MULTI_MODE to set NO and YES
but nothing helped. Well, this is a minor problem, because the device
works regardless of that message.
4) Sometimes computer hangs up. It does not happen too often
(it happend 2 times), but I am curious why? There is no OOPS, and log
files do not have any error messages... And I can not reproduce this
bug.
I spend already several days in attempts to configure all my hardware
(mainly audio card) under linux properly. Any help is greatly appreciated.
P.S. Please CC your answer to me because I am not member of your mail
list.
Thank you,
Alexander.
Hello,
I am experiencing a problem with both 2.4.0 and 2.4.1. The problem is that
at seemingly random times the console locks up. After the lockup I can no
longer type and the mouse is frozen. As far as I can tell, other systems
services are not affected, i.e. programs continue to run, music is being
played, I/O is fine. It looks like _only_ the console devices are locked
up.
I work under X most of the time, but this has happened on a bare VC once
also. The frequency of occurrence varies from 0 to a few times a day, with
an average about 1 time/day.
When it happens I use my UPS to power the machine down gracefully and then
reboot, however, it is a nuisance. After reboot the system log does not
have anything out of the ordinary in it. I think this might be related to
the other reports of lockups with 2.4.1 (by Ed Tomlinson and Alexander
Zvyagin).
The system specs are the following:
motherboard: ABIT BH6 rev 1.0
the BH6 is based on Intel's 440BX chipset
(chipset BIOS updated to the latest available one)
CPU: Pentium II (Deschutes) stepping 02 @ 400MHz
RAM: 256MB SDRAM
HDD: 3 hard drives:
hda: QUANTUM BIGFOOT TS8.4A, ATA DISK drive ( 8GB)
hdb: WDC WD205AA, ATA DISK drive (30GB)
hdc: WDC AC21200H, ATA DISK drive ( 1GB)
CD-ROM:
hdd: CR-801NP, ATAPI CD/DVD-ROM drive
FDC:
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
ttyS:
two serial ports on the motherboard
video:
Matrox Millenium G200 (8MB SDRAM)
eth:
Intel EtherExpressPro 10/100 (connected to DSL)
sound:
Creative SB AWE64 (ISA device)
modem:
USR3030/2729371324[0]{U.S. Robotics 56K FAX INT}
I also have a Hauppauge bt848-based TV tuner card but the driver for it
is compiled as a module and not loaded or used.
All hard drives use DMA by default but the kernel usually switches to PIO
for the CD-ROM after I start using it.
Any ideas as to the cause for the lockups would be greatly appreciated. I
am also willing to experiment/troubleshoot/test possible solutions, except
that I have no idea where to start from.
Cheers,
--Ivan
------------------------------------------------------------------------------
Ivan Ganev 327236 Georgia Tech Station
College of Computing Atlanta, GA 30332
Georgia Institute of Technology 1-(404)-365-8694
[email protected] http://www.cc.gatech.edu/~ganev
------------------------------------------------------------------------------
Learning is not compulsory. Neither is survival.
-- W. Edwards Deming
On 07 Feb 2001 02:27:57 +0000, Alexander Zvyagin wrote:
> 2) Frame-buffer mode does not work with my video card SiS630.
> But ok, frame-buffer mode is EXPERIMENTAL in linux.
> Computer boots, but screen is blank. All messages are fine.
> 01:00:0 VGA compatible controller: Silicon Integrated Systems [SiS]:
Unknown device 6300
> (rev 11)
Your particular chipset (actually, a 6300, which is different than the
630) is not supported by the SIS frame buffer. If this chipset is a
VESA 2.0+ compatible controller, then you will be able to use the VESA
frame buffer.
Brad Douglas
[email protected]
http://www.linux-fbdev.org
> 2) Frame-buffer mode does not work with my video card SiS630.
> But ok, frame-buffer mode is EXPERIMENTAL in linux.
> Computer boots, but screen is blank. All messages are fine.
You might want to try -ac that has specific rather than vesafb support
for the SIS framebuffers.
> 4) Sometimes computer hangs up. It does not happen too often
> (it happend 2 times), but I am curious why? There is no OOPS, and log
> files do not have any error messages... And I can not reproduce this
> bug.
2.4.1 has plenty of bugs, and it seems a lot of them show up best on sis
hardware 8(
Hi!
> I am experiencing a problem with both 2.4.0 and 2.4.1. The problem is that
> at seemingly random times the console locks up. After the lockup I can no
> longer type and the mouse is frozen. As far as I can tell, other systems
> services are not affected, i.e. programs continue to run, music is being
> played, I/O is fine. It looks like _only_ the console devices are locked
> up.
Login via network or serial cable, and see if /proc/interrupts entry
for keyboard/mouse changes as you type. Attempt to blink keyboard leds
with setleds.
Pavel
--
I'm [email protected]. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at [email protected]
On Sun, Feb 11, 2001 at 09:02:19PM +0100, you [Pavel Machek] claimed:
> Hi!
>
> > I am experiencing a problem with both 2.4.0 and 2.4.1. The problem is that
> > at seemingly random times the console locks up. After the lockup I can no
> > longer type and the mouse is frozen. As far as I can tell, other systems
> > services are not affected, i.e. programs continue to run, music is being
> > played, I/O is fine. It looks like _only_ the console devices are locked
> > up.
>
> Login via network or serial cable, and see if /proc/interrupts entry
> for keyboard/mouse changes as you type. Attempt to blink keyboard leds
> with setleds.
Also, try killing gpm.
-- v --
[email protected]
On Sun, 11 Feb 2001, Pavel Machek wrote:
> Login via network or serial cable, and see if /proc/interrupts entry
> for keyboard/mouse changes as you type. Attempt to blink keyboard leds
> with setleds.
> Pavel
On Mon, 12 Feb 2001, Ville Herva wrote:
> Also, try killing gpm.
> -- v --
Hello,
Thanks for the suggestions. Due to lack of a terminal or second computer
I've had no chance still to try the above suggestions. However, I have
tried many different versions of the 2.4.X series to no avail. I tried to
compile out APIC/IO-APIC stuff, I tried Alan's ac9 patches, etc.
However, I recently noticed that most times the console freezes when I am
doing a filename completion (which involves a beep when the completion is
not unique in KDE). I have changed the beep to be much shorter and with
much less annoying pitch from the KDE control panel.
I have found out that going in the control panel and just clicking the
"Test" button to test out the beep would freeze the console in less than
10-15 tries.
I got the sources for "kcontrol" and it seems the beeping is done from
some function of the keyboard driver, although I do not understand KDE
much and have no idea how to continue tracing the bug further.
Currently I have set the pitch to 0 Hz (no beeping) and have not had a
lockup yet. I will continue testing, however, if someone can give me a
suggestion how to go about tracing the code that actually does the
beeping (be it in KDE or the kernel) I'd be very grateful.
Cheers,
--Ivan
P.S. The relevant code from kdebase-2.0.1/kcontrol/bell/bell.cpp is:
void KBellConfig::ringBell()
{
// store the old state
XKeyboardState old_state;
XGetKeyboardControl(kapp->getDisplay(), &old_state);
// switch to the test state
XKeyboardControl kbd;
kbd.bell_percent = m_volume->value();
kbd.bell_pitch = m_pitch->value();
if (m_volume->value() > 0)
kbd.bell_duration = m_duration->value();
else
kbd.bell_duration = 0;
XChangeKeyboardControl(kapp->getDisplay(),
KBBellPercent | KBBellPitch | KBBellDuration,
&kbd);
// ring bell
XBell(kapp->getDisplay(),100);
// restore old state
kbd.bell_percent = old_state.bell_percent;
kbd.bell_pitch = old_state.bell_pitch;
kbd.bell_duration = old_state.bell_duration;
XChangeKeyboardControl(kapp->getDisplay(),
KBBellPercent | KBBellPitch | KBBellDuration,
&kbd);
}
------------------------------------------------------------------------------
Ivan Ganev 327236 Georgia Tech Station
College of Computing Atlanta, GA 30332
Georgia Institute of Technology 1-(404)-365-8694
[email protected] http://www.cc.gatech.edu/~ganev
------------------------------------------------------------------------------
Learning is not compulsory. Neither is survival.
-- W. Edwards Deming