Public bug reported:
Hardware: Dell Latitude D610, ATI graphics
Symptoms:
Resume works perfectly after suspend and hibernate when I boot kernel
linux-image-2.6.15-26.44-i686
It fails when with linux-image-2.6.15-26.45-i686
(blank screen, error message once that HAL failed).
I didn't have time
** Description changed:
- Hardware: Dell Latitude D610, ATI graphics
+ Hardware: Dell Latitude D610, ATI graphics, fglrx driver
Symptoms:
Resume works perfectly after suspend and hibernate when I boot kernel
linux-image-2.6.15-26.44-i686
- It fails when with linux-image-2.6.15-26.45-i6
I resolved the problem by adding the following init script:
#!/bin/sh
echo -n "i8042" > /sys/bus/platform/drivers/i8042/unbind
echo -n "i8042" > /sys/bus/platform/drivers/i8042/bind
(linking it to /etc/rc2.d/S20rebind-keyboard worked for me.)
--
ps2 keyboard does not work on VIA chipse
image-2.6.20-16-generic_2.6.20-16.28_i386.deb does NOT solve PS2
Keyboard problem for VIA KT133-VT8363 (acpi=off works)
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108382
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
Some days ago I had a similar problem after an update:
Machine has two SATA drives.
I had /boot and swap on primary partitions /dev/sda1 and /dev/sda2,
/ and other filesystems on Software-RAID-1 and LVM.
After the issue neither /boot nor swap was recognized on /dev/sda*.
Instead it was mapped to
Booting the kernel with parameter acpi=off resolved the problem for me.
I had exactly the same problem as described above: Keyboard worked fine
with Edgy. After an upgrade to Feisty the keyboard worked in Grub, but
neither on the console nor in X.
I noticed that in /proc/bus/input/devices veraiou
BTW: I don't think this bug is related to "Macintosh mouse button
emulation" as suggested some posts above. Googling for this phrase
brings up lots of dmesg output indicating that thsi device is detected
frequently with recent kernels. Hower, no keyboard problems are reported
in the same context.
On Tuesday 26 June 2007 11:04:46 Jérôme Guelfucci wrote:
> Thank you for your bug report. Do you still have this issue with the
> latest release of Ubuntu ?
no, I don't.
As far as I remember, the issue was resolved with the next distribution kernel
after 2.6.15-26. I'm currently using Feisty wit
