Author |
Message |
cfreeland
|
Posted: Fri Nov 19, 2004 4:25 pm |
|
Joined: Fri Oct 29, 2004 9:01 pm
Posts: 4
Location:
Palo Alto, CA
|
So as I understand it, the blinking lights are essentially "fatal errors", so this solution mostly refers to people hitting blinking lights due to power management problems, such as were addressed in the setterm solution provided earlier in this thread.
My steps to reach the same goal...
1) disabled APM in my bios
2) commented out the contents of /etc/modutils/apm
3) ran update-modules
4) rmmod apm or reboot, your choice
When I was first getting started, I used to get blinking lights and hanging on boot, but I believe this to have been a conflict between my usb mouse and some other device. I fixed this by using a PS/2 mouse.
_________________ --------------------
KnoppMyth r4v5
Asus A7V mobo with 1.4GHz Athlon TBird
512 MB ram
Hauppauge PVR-350
ATI Radeon 9800
Phillips PCRW804 CD/RW
Seagate 7200 Barracuda 120 GB
|
|
Top |
|
 |
Xsecrets
|
Posted: Fri Nov 19, 2004 11:03 pm |
|
Joined: Mon Oct 06, 2003 10:38 am
Posts: 4978
Location:
Nashville, TN
|
In my opinion, and no hard testing to back this up the blinky keyboard lights problem has to do with acpi as this is removed from the later R4 kernels.
_________________ Have a question search the forum and have a look at the KnoppMythWiki.
Xsecrets
|
|
Top |
|
 |
alien
|
Posted: Sat Nov 20, 2004 8:56 am |
|
Joined: Mon Jun 21, 2004 5:28 am
Posts: 700
Location:
Germany
|
Just to update on my previous post. I re-built the kernel with preempt disabled and that didn't fix my blinky lights problem. I couldn't find how to disable lockbreak, so I wasn't able to test that...
Allen
_________________ ASUS AT3N7A-I (Atom 330) TBS 8922 PCI (DVB-S2)
|
|
Top |
|
 |
Liv2Cod
|
Posted: Sat Nov 20, 2004 12:21 pm |
|
Joined: Fri May 21, 2004 11:55 pm
Posts: 1206
Location:
Silicon Valley, CA
|
Yes, the "blinky lights" are the way the computer notifies you of a "kernel panic", i.e. the Linux kernel throwing up its hands (flippers?) and giving up.
From my observations, it can be caused by a number of things, which is why the symptoms seem to change from post to post. There are at least four kernel panics I'm aware of:
1. ACPI enabled in the kernel.
2. Display timing out and going to sleep -- wakeup causes panic.
3. Using USB mouse instead of PS/2.
4. Some networking cards fail during installation.
I've personally experienced #2 on an Athlon nForce2 box running R4V4.1 and #3 on R4V4.1 and R4V5.
Solutions:
1. Disable ACPI in the kernel -- done already by cesman
2. Don't let your display ever turn off to begin with.
3. Don't use a USB mouse or keyboard.
4. Leave networking unconnected at installation and set it up afterwards.
_________________ Do you code to live, or live to code? Search LinHES forum through Google
|
|
Top |
|
 |
Xsecrets
|
Posted: Sat Nov 20, 2004 12:49 pm |
|
Joined: Mon Oct 06, 2003 10:38 am
Posts: 4978
Location:
Nashville, TN
|
I believe however that many of the problems stem specifically because acpi is disabled in the kernel, because they showed up in the first version where cesman disabled acpi in the kernel. It is my belief (like I said not tested) that recompiling the kernel with acpi enabled would solve most if not all causes of this at least on the pundit cases, because they had none of these problems before it was removed.
_________________ Have a question search the forum and have a look at the KnoppMythWiki.
Xsecrets
|
|
Top |
|
 |
tjimenez87
|
Posted: Thu Jan 06, 2005 11:51 am |
|
Joined: Thu Dec 30, 2004 2:12 am
Posts: 108
|
Is there any update to a solution to this problem?
I just bought a wireless USB mouse and keyboard, and now realize that my knoppmyth box won't boot without a PS2 keyboard plugged in.
I'm debating between returning the wireless keyboard and just plugging in a PS2 keyboard anytime I need to reboot.
|
|
Top |
|
 |
Xsecrets
|
Posted: Thu Jan 06, 2005 2:13 pm |
|
Joined: Mon Oct 06, 2003 10:38 am
Posts: 4978
Location:
Nashville, TN
|
There won't be a solution to this problem before R5, and before you ask it will be released "when it is done"
_________________ Have a question search the forum and have a look at the KnoppMythWiki.
Xsecrets
|
|
Top |
|
 |
Gromit
|
Posted: Wed Jan 12, 2005 4:26 am |
|
Joined: Tue Jan 11, 2005 10:23 am
Posts: 4
Location:
Switzerland
|
Hello
I got blinky keyboards with R4V5.
MB: ASUS A7N8X-X (nvidia chipset)
Grabber: Pinnacle PCTV (bt878 based)
After a while I had blinky keyboards with a SCERR error from the bttv driver.
This dissapeared when I manually set up at least one valid channel for watching tv...
Hope this is of help for someone
|
|
Top |
|
 |
RustySawDust
|
Posted: Fri Jan 14, 2005 11:19 pm |
|
Joined: Fri Nov 14, 2003 8:57 pm
Posts: 26
|
This problem also affects the onboard NIC of the Asus P4P800-VM. I threw in an old 3Com card, ran modconf, and now I'm back in business.
My fortune cookie last week said
Quote: Patience is the key to joy
|
|
Top |
|
 |
Greg Frost
|
Posted: Fri Jan 14, 2005 11:35 pm |
|
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location:
Adelaide, Australia
|
RustySawDust wrote: My fortune cookie last week said Quote: Patience is the key to joy
One of the curious thinks about fortune cookies is that just about all fortunes can be improved by appending the words "in bed" to the end. Next time you are at a chinese restraunt with some friends, try it. It makes the reading of the fortunes much more amusing.
|
|
Top |
|
 |
meanjeans
|
Posted: Tue Jan 18, 2005 6:55 pm |
|
Joined: Fri Jan 09, 2004 12:25 pm
Posts: 21
|
My system was slightly overclocked when I installed R4V5 and I had blinky lights and DMA errors and the whole thing (it all worked fine with pre V3 knoppmyth).
I clocked back to stock and no problems.
|
|
Top |
|
 |
Gromit
|
Posted: Mon Jan 24, 2005 9:52 am |
|
Joined: Tue Jan 11, 2005 10:23 am
Posts: 4
Location:
Switzerland
|
Gromit wrote: Hello
I got blinky keyboards with R4V5. MB: ASUS A7N8X-X (nvidia chipset) Grabber: Pinnacle PCTV (bt878 based)
After a while I had blinky keyboards with a SCERR error from the bttv driver. This dissapeared when I manually set up at least one valid channel for watching tv...
Hope this is of help for someone
This only helped me to increase system stability but it turned out that this was not a 100% solution.
Finally I installed Fedora Core 3 and used the http://wilsonet.com/mythtv/ guide to install mythtv-suite. This solved my problems. The guide is excellent...
The Fedora 2.6.10 Kernel complained about resource conflicts in my system which I had to solve first. The knopmyth 2.4.x kernel did not detect the conflict. This was the reason for my problems but I did not go back to knopmyth to verify it.. Never change a running system!!!
Regards
Gromit
|
|
Top |
|
 |
bshroyer
|
Posted: Wed Mar 02, 2005 3:49 pm |
|
Joined: Wed Feb 18, 2004 9:07 pm
Posts: 89
|
Do you recall if the "resource conflicts" you had to resolve were IRQ related? I'm having (I think) some IRQ problems, and I've got:
Code: root@mythbox:/proc# cat pci PCI devices found: Bus 0, device 0, function 0: Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge (rev 128). Master Capable. Latency=8. Prefetchable 32 bit memory at 0xe0000000 [0xe3ffffff]. Bus 0, device 1, function 0: PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge (rev 0). Master Capable. No bursts. Min Gnt=12. Bus 0, device 10, function 0: Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 10). IRQ 18. Master Capable. Latency=32. Min Gnt=2.Max Lat=20. I/O at 0xd000 [0xd01f]. Bus 0, device 10, function 1: Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 10). Master Capable. Latency=32. I/O at 0xec00 [0xec07]. Bus 0, device 12, function 0: Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 17). IRQ 16. Master Capable. Latency=32. Min Gnt=16.Max Lat=40. Prefetchable 32 bit memory at 0xdddfe000 [0xdddfefff]. Bus 0, device 12, function 1: Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 17). IRQ 16. Master Capable. Latency=32. Min Gnt=4.Max Lat=255. Prefetchable 32 bit memory at 0xdddff000 [0xdddfffff]. Bus 0, device 15, function 0: RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 128). IRQ 20. Master Capable. Latency=32. I/O at 0xe800 [0xe807]. I/O at 0xe400 [0xe403]. I/O at 0xe000 [0xe007]. I/O at 0xdc00 [0xdc03]. I/O at 0xd800 [0xd80f]. I/O at 0xd400 [0xd4ff]. Bus 0, device 15, function 1: IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 6). IRQ 20. Master Capable. Latency=32. I/O at 0xfc00 [0xfc0f]. Bus 0, device 16, function 3: USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#4) (rev 129). IRQ 21. Master Capable. Latency=32. I/O at 0xcc00 [0xcc1f]. Bus 0, device 16, function 2: USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#3) (rev 129). IRQ 21. Master Capable. Latency=32. I/O at 0xc800 [0xc81f]. Bus 0, device 16, function 1: USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#2) (rev 129). IRQ 21. Master Capable. Latency=32. I/O at 0xc400 [0xc41f]. Bus 0, device 16, function 0: USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 129). IRQ 21. Master Capable. Latency=32. I/O at 0xc000 [0xc01f]. Bus 0, device 16, function 4: USB Controller: VIA Technologies, Inc. USB 2.0 (rev 134). IRQ 21. Master Capable. Latency=32. Non-prefetchable 32 bit memory at 0xdfffbe00 [0xdfffbeff]. Bus 0, device 17, function 0: ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [K8T800 South] (rev 0). Bus 0, device 18, function 0: Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 120). IRQ 23. Master Capable. Latency=32. Min Gnt=3.Max Lat=8. I/O at 0xbc00 [0xbcff]. Non-prefetchable 32 bit memory at 0xdfffbd00 [0xdfffbdff]. Bus 1, device 0, function 0: VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 440] (rev 163). IRQ 16. Master Capable. Latency=248. Min Gnt=5.Max Lat=1. Non-prefetchable 32 bit memory at 0xde000000 [0xdeffffff]. Prefetchable 32 bit memory at 0xd0000000 [0xd7ffffff]. Prefetchable 32 bit memory at 0xddc80000 [0xddcfffff].
root@mythbox:/proc# cat /proc/interrupts CPU0 0: 29254134 IO-APIC-edge timer 1: 477 IO-APIC-edge i8042 8: 1 IO-APIC-edge rtc 9: 0 IO-APIC-level acpi 12: 111 IO-APIC-edge i8042 14: 40976 IO-APIC-edge ide0 15: 32392 IO-APIC-edge ide1 16: 3482068 IO-APIC-level bttv0, Bt87x audio, nvidia 18: 1798920 IO-APIC-level EMU10K1 20: 0 IO-APIC-level libata 21: 0 IO-APIC-level uhci_hcd, uhci_hcd, uhci_hcd, uhci_hcd, ehci_hcd 23: 9191 IO-APIC-level eth0 NMI: 0 LOC: 29257182 ERR: 0 MIS: 0 root@mythbox:/proc#
So it appears that bttv and nvidia (which is AGP) may be clashing.
_________________ R5Fxx
Home-Brewed Mythic Dragon Clone
200GB WD IDE /myth
2x250GB WD IDE (lvm) /myth/tv
|
|
Top |
|
 |
RustySawDust
|
Posted: Thu Apr 14, 2005 11:05 pm |
|
Joined: Fri Nov 14, 2003 8:57 pm
Posts: 26
|
Just upgraded to R5A12 & wanted to confirm that this is no longer a problem & thank everyone for this great release!!
|
|
Top |
|
 |