Re: kernel upgrade to 2.6.15 and now no keyboard or mouse.- Resolved! Gigabyte GA-7DPXDWP motherboard
I have resolved this issue. The problem is discussed on the Linux Kernel mailing list. It is a problem with conflicts with USB subsystem. I am using the Gigabyte GA-7DPXDWP dual AMD motherboard with dual athlon MP 2400+ processors. If you turn off USB keyboard and USB mouse support in the Mtherboard BIOS then PS2 mice and keyboards will be recognized by both the 2.6.15 Linux kernels as well as the new etch installer. Otherwise the 2.6.15 kernel will not recognize the keyboard or mice during bootup. Here is a kernel mailing list thread reference. http://www.ussg.iu.edu/hypermail/linux/kernel/0601.1/1433.html Re: PROBLEM: PS/2 keyboard does not work with 2.6.15 From: Alan Stern read the whole thread. Thanks, Mitchell Laks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel upgrade to 2.6.15 and now no keyboard or mouse.
I install latest linux-image-2.6.15-1-k7-smp (or linux-image-2.6.15-1-k7 or linux-image-2.6.15-1-486) on my system and now input devices keyboard and mouse do not work. dmesg|grep input iput: PC Speaker as /class/input/input0 cat /proc/bus/input/devices I: Bus=0010 Vendor=001f Product=0001 Version=0100 N: Name=PC Speaker P: Phys=isa0061/input0 S: Sysfs=/class/input/input0 H: Handlers=kbd event0 B: EV=40001 B: SND=6 of course on my other systems - same keyboard and mouse it says input: AT Translated Set 2 keyboard as /class/input/input0 input: PC Speaker as /class/input/input1 input: ImPS/2 Generic Wheel Mouse as /class/input/input2 cat /proc/bus/input/devices I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name=AT Translated Set 2 keyboard P: Phys=isa0060/serio0/input0 S: Sysfs=/class/input/input0 H: Handlers=kbd event0 B: EV=120013 B: KEY=4 200 3802078 f840d001 f2df ffef fffe B: MSC=10 B: LED=7 I: Bus=0010 Vendor=001f Product=0001 Version=0100 N: Name=PC Speaker P: Phys=isa0061/input0 S: Sysfs=/class/input/input1 H: Handlers=kbd event1 B: EV=40001 B: SND=6 I: Bus=0011 Vendor=0002 Product=0005 Version= N: Name=ImPS/2 Generic Wheel Mouse P: Phys=isa0060/serio1/input0 S: Sysfs=/class/input/input2 H: Handlers=mouse0 event2 B: EV=7 B: KEY=7 0 0 0 0 0 0 0 0 B: REL=103 I first did a fresh debian sarge install, chose desktop. and then change to sid in apt/sources.lst then did apt-get dist-upgrade. Went fine. Then upgraded to latest linux-image-2.6.15-1-k7-smp. Had some messy fight with udev (wanted a kernel 2.6.12 initially)and finally got the new kernel installed with udev. Now the system thinks the only input device is a speaker. No mouse or keyboard. I can only ssh into the system. kind of sad. Any ideas. Mitchell Laks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgrade to 2.6.15-1-k7 kernel -- eth0: Corrupted packet received... in syslog.
On 2006-02-27, Adam Funk [EMAIL PROTECTED] wrote: Last night I upgraded from 2.6.8-2-k7 to 2.6.15-1-k7. Now I'm getting the following about 24 times an hour in /var/log/syslog: kernel: eth0: Corrupted packet received, buffer status = 0x90c005ee. Now I'm convinced this is connected with the problems I've been having (on and off) with fetchnews, since the Corrupted packet messages are interspersed with fetchnews messages, for example: Feb 28 12:53:01 garcia fetchnews[25101]: leafnode 1.11.4: verbosity level is 0, debugmode is 0 Feb 28 12:53:08 garcia kernel: eth0: Corrupted packet received, buffer status = 0x90c005ee. Feb 28 12:53:46 garcia kernel: eth0: Corrupted packet received, buffer status = 0x90c005ee. Feb 28 12:54:27 garcia kernel: eth0: Corrupted packet received, buffer status = 0x90c005ee. Feb 28 12:54:48 garcia fetchnews[25101]: (ERROR: timeout - no response in 100 s) Feb 28 12:54:48 garcia fetchnews[25101]: Server disconnection or timeout before article could be retrieved #2 Feb 28 12:54:48 garcia fetchnews[25101]: Warning: aborting fetch from news.individual.net due to previous condition. Feb 28 12:54:49 garcia kernel: eth0: Corrupted packet received, buffer status = 0x90c005ee. Feb 28 12:56:29 garcia fetchnews[25101]: (ERROR: timeout - no response in 100 s) Feb 28 12:56:29 garcia fetchnews[25101]: Server disconnection or timeout before article could be retrieved #1 Feb 28 12:56:29 garcia fetchnews[25101]: Warning: aborting fetch from text.news.blueyonder.co.uk due to previous condition. Any ideas? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Upgrade to 2.6.15-1-k7 kernel -- eth0: Corrupted packet received... in syslog.
Last night I upgraded from 2.6.8-2-k7 to 2.6.15-1-k7. Now I'm getting the following about 24 times an hour in /var/log/syslog: kernel: eth0: Corrupted packet received, buffer status = 0x90c005ee. Is this anything to be concerned about, or just I should suppress it in logcheck's ignore files? Thanks, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Acpi problems after upgrade to 2.6.15: computer doesn't poweroff anymore.
Hello everybody, I have recently updated my kernel building a 2.6.15 one from debian sources, and I ran into troubles. First problem I had was that battery was not anymore detected (/proc/acpi/battery was empty). I googled around and I found a solution adding ec_burst=1 to boot parameters. The second one is that my laptop doesn't poweroff: the shutdown process seems to be completed, and the screen goes off, but the power led stays on, and I have to manually press power button for several seconds to shut down it completely. I have all support for acpi built into my kernel: # Power management options # CONFIG_PM=y CONFIG_PM_LEGACY=y CONFIG_PM_DEBUG=y CONFIG_SOFTWARE_SUSPEND=y CONFIG_PM_STD_PARTITION=/dev/hda5 # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y # CONFIG_ACPI_SLEEP_PROC_SLEEP is not set CONFIG_ACPI_AC=y CONFIG_ACPI_BATTERY=y CONFIG_ACPI_BUTTON=y CONFIG_ACPI_VIDEO=y CONFIG_ACPI_HOTKEY=y CONFIG_ACPI_FAN=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_IBM is not set # CONFIG_ACPI_TOSHIBA is not set CONFIG_ACPI_CUSTOM_DSDT=y CONFIG_ACPI_CUSTOM_DSDT_FILE=/opt/acpi/dsdt.hex CONFIG_ACPI_BLACKLIST_YEAR=0 CONFIG_ACPI_DEBUG=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_SYSTEM=y # CONFIG_ACPI_CONTAINER is not set and this are my boot parameters: # kopt=root=/dev/hda2 ro console=tty0 no_timer_check noapic nolapic i8042.nomux noapictimer acpi_os_name=Microsoft Windows XP disable_timer_pin_1 ec_burst=1 Any help will be appreciated.
Re: Upgrade to 2.6.15
On Tuesday 21 February 2006 02:41, Hal Vaughan wrote: On Tuesday 21 February 2006 02:07, John Talbut wrote: I am using etch and it is up to date apart from the kernel. When I wanted to recompile the kernel I found information that suggested that I would need to upgrade to the 2.6.12 kernel. So I duly went looking for the kernel-source-2.6.12 package, only to find it nowhere in testing. Instead it seemed I needed to be using the linux-source-2.6.15 package. Is this the right package for me to use? Why the change from kernel-source to linux-source? The plan is to eventually include other kernels. This was just discussed here a few days ago. By not using kernel-source or kernel-image that leaves room open for other kernels, like Gnu's Hurd or other non-Linux kernels. Why is 2.6.15 the current stable kernel when only even numbered releases were supposed to be stable? The 'even' requirement hasn't changed, it refers to the 6 in any event. Linus changed the kernel version numbering system. Hal -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Upgrade to 2.6.15
I am using etch and it is up to date apart from the kernel. When I wanted to recompile the kernel I found information that suggested that I would need to upgrade to the 2.6.12 kernel. So I duly went looking for the kernel-source-2.6.12 package, only to find it nowhere in testing. Instead it seemed I needed to be using the linux-source-2.6.15 package. Is this the right package for me to use? Why the change from kernel-source to linux-source? Why is 2.6.15 the current stable kernel when only even numbered releases were supposed to be stable? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgrade to 2.6.15
On Tuesday 21 February 2006 02:07, John Talbut wrote: I am using etch and it is up to date apart from the kernel. When I wanted to recompile the kernel I found information that suggested that I would need to upgrade to the 2.6.12 kernel. So I duly went looking for the kernel-source-2.6.12 package, only to find it nowhere in testing. Instead it seemed I needed to be using the linux-source-2.6.15 package. Is this the right package for me to use? Why the change from kernel-source to linux-source? The plan is to eventually include other kernels. This was just discussed here a few days ago. By not using kernel-source or kernel-image that leaves room open for other kernels, like Gnu's Hurd or other non-Linux kernels. Why is 2.6.15 the current stable kernel when only even numbered releases were supposed to be stable? Linus changed the kernel version numbering system. Hal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgrade to 2.6.15
Hello John Talbut ([EMAIL PROTECTED]) wrote: I am using etch and it is up to date apart from the kernel. When I wanted to recompile the kernel I found information that suggested that I would need to upgrade to the 2.6.12 kernel. So I duly went looking for the kernel-source-2.6.12 package, only to find it nowhere in testing. Instead it seemed I needed to be using the linux-source-2.6.15 package. Yes. You need packages for 2.6.12 or newer. Older versions don't work with udev in etch, for example. Is this the right package for me to use? Yes. Why the change from kernel-source to linux-source? Probably because there are ports of debian that use other kernels, e.g. The Hurd and FreeBSD. Why is 2.6.15 the current stable kernel when only even numbered releases were supposed to be stable? The even number is the second number. 2.4 kernels are stable, 2.5 was a developement branch, 2.6 is stable (more or less ;-)) best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 ICQ #17079270 Registered Linux User #267976 http://www.andreas-janssen.de/debian-tipps-sarge.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
