To try and get a jump-start on testing 2.6.15, I've prepared packages for FC4 based on the current rawhide kernel.
These are likely to change almost daily, and there's no guarantee how much longer 2.6.15 is going to be in -rc stage, so I'm going to hold off pushing these out as an official updates-testing release until a final 2.6.15 has been released. (Should a security errata be needed before then, I'll push out another 2.6.14 based release)
http://people.redhat.com/davej/kernels/Fedora/FC4/
Please file bugs in bugzilla, rather than emailing me/this list about them.
Dave
On Fri, Dec 16, 2005 at 02:51:57AM -0500, Dave Jones wrote:
To try and get a jump-start on testing 2.6.15, I've prepared packages for FC4 based on the current rawhide kernel.
These are likely to change almost daily, and there's no guarantee how much longer 2.6.15 is going to be in -rc stage, so I'm going to hold off pushing these out as an official updates-testing release until a final 2.6.15 has been released. (Should a security errata be needed before then, I'll push out another 2.6.14 based release)
http://people.redhat.com/davej/kernels/Fedora/FC4/
Please file bugs in bugzilla, rather than emailing me/this list about them.
By popular demand, they're now yum-able too..
wget http://people.redhat.com/davej/kernels/Fedora/FC4/kernels.repo mv kernels.repo /etc/yum.repos.d/
Dave
On Friday 16 December 2005 08:44, Dave Jones wrote:
By popular demand, they're now yum-able too..
Thank you, it is a lot easier than to check your site every day. :o)
wget http://people.redhat.com/davej/kernels/Fedora/FC4/kernels.repo mv kernels.repo /etc/yum.repos.d/
Dave
Am Freitag, den 16.12.2005, 03:44 -0500 schrieb Dave Jones:
On Fri, Dec 16, 2005 at 02:51:57AM -0500, Dave Jones wrote:
To try and get a jump-start on testing 2.6.15, I've prepared packages for FC4 based on the current rawhide kernel.
These are likely to change almost daily, and there's no guarantee how much longer 2.6.15 is going to be in -rc stage, so I'm going to hold off pushing these out as an official updates-testing release until a final 2.6.15 has been released. (Should a security errata be needed before then, I'll push out another 2.6.14 based release)
http://people.redhat.com/davej/kernels/Fedora/FC4/
Please file bugs in bugzilla, rather than emailing me/this list about them.
By popular demand, they're now yum-able too..
Thanks for your work -- kernel is running fine here.
But according to http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;...
you need at least udev 071 to run 2.6.15 -- is that wrong or are we also getting a updated udev in time for FC4 (currently we are at udev-058-1.0.FC4.1)?
CU thl
Thorsten Leemhuis wrote:
Am Freitag, den 16.12.2005, 03:44 -0500 schrieb Dave Jones:
On Fri, Dec 16, 2005 at 02:51:57AM -0500, Dave Jones wrote:
To try and get a jump-start on testing 2.6.15, I've prepared packages for FC4 based on the current rawhide kernel.
These are likely to change almost daily, and there's no guarantee how much longer 2.6.15 is going to be in -rc stage, so I'm going to hold off pushing these out as an official updates-testing release until a final 2.6.15 has been released. (Should a security errata be needed before then, I'll push out another 2.6.14 based release)
http://people.redhat.com/davej/kernels/Fedora/FC4/
Please file bugs in bugzilla, rather than emailing me/this list about them.
By popular demand, they're now yum-able too..
Thanks for your work -- kernel is running fine here.
But according to http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;...
you need at least udev 071 to run 2.6.15 -- is that wrong or are we also getting a updated udev in time for FC4 (currently we are at udev-058-1.0.FC4.1)?
CU thl
Somehow the kernel guys do not care about the rest of the system with their updates :-/
So either I have to backport rawhide udev,hotplug,initscripts... or we will need more updated packages.. :-/
But according to http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;...
you need at least udev 071 to run 2.6.15 -- is that wrong or are we also getting a updated udev in time for FC4 (currently we are at udev-058-1.0.FC4.1)?
CU thl
Somehow the kernel guys do not care about the rest of the system with their updates :-/
So either I have to backport rawhide udev,hotplug,initscripts... or we will need more updated packages.. :-/
Have you tried the kernel yet? I installed it on my laptop running udev-058. No problems so far.
Josh
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Thank you! Thank you!
I tried it on my Acer Ferrari 4005 laptop and it recognized the Synaptics touchpad while the previous kernels didn't.
My ipw2200 adapter on the laptop also works out of the box with WPA due to the updated drivers :)
Dave, I had filed a bug for the Synaptics touchpad. Should that be closed?
Thanks
Dave Jones davej@redhat.com wrote: To try and get a jump-start on testing 2.6.15, I've prepared packages for FC4 based on the current rawhide kernel.
These are likely to change almost daily, and there's no guarantee how much longer 2.6.15 is going to be in -rc stage, so I'm going to hold off pushing these out as an official updates-testing release until a final 2.6.15 has been released. (Should a security errata be needed before then, I'll push out another 2.6.14 based release)
http://people.redhat.com/davej/kernels/Fedora/FC4/
Please file bugs in bugzilla, rather than emailing me/this list about them.
Dave
On Fri, Dec 16, 2005 at 09:25:20AM -0800, Josh wrote:
Thank you! Thank you!
I tried it on my Acer Ferrari 4005 laptop and it recognized the Synaptics touchpad while the previous kernels didn't.
My ipw2200 adapter on the laptop also works out of the box with WPA due to the updated drivers :)
Dave, I had filed a bug for the Synaptics touchpad. Should that be closed?
Wait until it gets pushed out as an update.
Dave
On Fri, 2005-12-16 at 09:25 -0800, Josh wrote:
Thank you! Thank you!
I tried it on my Acer Ferrari 4005 laptop and it recognized the Synaptics touchpad while the previous kernels didn't.
Strange, my Synaptics touchpad, which had been working just fine, isn't recognized by the test kernel. Dave, I suppose I should Bugzilla this?
On Fri, Dec 16, 2005 at 01:49:38PM -0800, Brian Gaynor wrote:
On Fri, 2005-12-16 at 09:25 -0800, Josh wrote:
Thank you! Thank you!
I tried it on my Acer Ferrari 4005 laptop and it recognized the Synaptics touchpad while the previous kernels didn't.
Strange, my Synaptics touchpad, which had been working just fine, isn't recognized by the test kernel. Dave, I suppose I should Bugzilla this?
Sure. That hardware has been a thorn in my side since I can remember. We've had "works/doesn't work" cycles of that way back into FC2 era.
I've no idea why it's so fragile.
Dave
On Fri, 2005-12-16 at 16:51 -0500, Dave Jones wrote:
Sure. That hardware has been a thorn in my side since I can remember. We've had "works/doesn't work" cycles of that way back into FC2 era.
I've no idea why it's so fragile.
Dave
#175993 created.
On Fri, 2005-12-16 at 15:51 -0800, Brian Gaynor wrote:
On Fri, 2005-12-16 at 16:51 -0500, Dave Jones wrote:
Sure. That hardware has been a thorn in my side since I can remember. We've had "works/doesn't work" cycles of that way back into FC2 era.
I've no idea why it's so fragile.
Dave
#175993 created.
Ah, the irony. For the first time since Synaptics has just worked for me (out of the box so to say) it doesn't with kernel-2.6.14-1.1767_FC4
I'll mark myself on the BZ.
Otherwise, everything looks good.
Rodd
On Mon, 2005-12-19 at 08:53 +1100, Rodd Clarkson wrote:
On Fri, 2005-12-16 at 15:51 -0800, Brian Gaynor wrote:
On Fri, 2005-12-16 at 16:51 -0500, Dave Jones wrote:
Sure. That hardware has been a thorn in my side since I can remember. We've had "works/doesn't work" cycles of that way back into FC2 era.
I've no idea why it's so fragile.
Dave
#175993 created.
Ah, the irony. For the first time since Synaptics has just worked for me (out of the box so to say) it doesn't with kernel-2.6.14-1.1767_FC4
kernel-2.6.14-1.1769_FC4 isn't working with regard to synaptics either.
R.
On Fri, 2005-12-16 at 16:51 -0500, Dave Jones wrote:
On Fri, Dec 16, 2005 at 01:49:38PM -0800, Brian Gaynor wrote:
On Fri, 2005-12-16 at 09:25 -0800, Josh wrote:
Thank you! Thank you!
I tried it on my Acer Ferrari 4005 laptop and it recognized the Synaptics touchpad while the previous kernels didn't.
Strange, my Synaptics touchpad, which had been working just fine, isn't recognized by the test kernel. Dave, I suppose I should Bugzilla this?
Sure. That hardware has been a thorn in my side since I can remember. We've had "works/doesn't work" cycles of that way back into FC2 era.
I've no idea why it's so fragile.
Dave,
Can't find the thread, so replying here, but you said something about the rc kernels needing HAL or DBUS from rawhide for the synaptics driver to work.
It there any intention of getting this ported (or solved)?
I'm happy to test these kernels, but until my mouse works properly it's a real hassle. The three things I use most on my laptop are the keyboard, the mouse and the screen. Without a well functioning mouse it's hard to get stuff done (or test things).
Rodd
Rodd Clarkson wrote:
On Fri, 2005-12-16 at 16:51 -0500, Dave Jones wrote:
On Fri, Dec 16, 2005 at 01:49:38PM -0800, Brian Gaynor wrote:
On Fri, 2005-12-16 at 09:25 -0800, Josh wrote:
Thank you! Thank you!
I tried it on my Acer Ferrari 4005 laptop and it recognized the Synaptics touchpad while the previous kernels didn't.
Strange, my Synaptics touchpad, which had been working just fine, isn't recognized by the test kernel. Dave, I suppose I should Bugzilla this?
Sure. That hardware has been a thorn in my side since I can remember. We've had "works/doesn't work" cycles of that way back into FC2 era.
I've no idea why it's so fragile.
Dave,
Can't find the thread, so replying here, but you said something about the rc kernels needing HAL or DBUS from rawhide for the synaptics driver to work.
It there any intention of getting this ported (or solved)?
I'm happy to test these kernels, but until my mouse works properly it's a real hassle. The three things I use most on my laptop are the keyboard, the mouse and the screen. Without a well functioning mouse it's hard to get stuff done (or test things).
Rodd
not hal or dbus, but udev
On Fri, 2005-12-16 at 09:25 -0800, Josh wrote:
Thank you! Thank you!
I tried it on my Acer Ferrari 4005 laptop and it recognized the Synaptics touchpad while the previous kernels didn't.
My ipw2200 adapter on the laptop also works out of the box with WPA due to the updated drivers :)
That's surprising since my Acer Ferrari 4005 never had a problem with the Synaptics touchpad on both FC4, FC5t1 and Rawhide. Did have to boot with i8042.nomux no_timer_check though. Maybe you could try that.
Ipw2200 on an Acer Ferrari 4005? Mine has a Broadcom chip and according to the Acer website all Ferrari 4005 models have that. Don't know how you got an Intel wireless chipset on an AMD motherbord :P
Regards, Patrick
Patrick fedora@puzzled.xs4all.nl wrote: On Fri, 2005-12-16 at 09:25 -0800, Josh wrote:
Thank you! Thank you!
I tried it on my Acer Ferrari 4005 laptop and it recognized the Synaptics touchpad while the previous kernels didn't.
My ipw2200 adapter on the laptop also works out of the box with WPA due to the updated drivers :)
That's surprising since my Acer Ferrari 4005 never had a problem with the Synaptics touchpad on both FC4, FC5t1 and Rawhide. Did have to boot with i8042.nomux no_timer_check though. Maybe you could try that.
Ipw2200 on an Acer Ferrari 4005? Mine has a Broadcom chip and according to the Acer website all Ferrari 4005 models have that. Don't know how you got an Intel wireless chipset on an AMD motherbord :P
I wasn't aware of the boot parameter to get synaptics touchpad. Does your touch pad work without the parameter?
I ditched the default broadcom wireless NIC and bought Intel 2915 ABG mini-pci adapter for $29. Works great ;-)
Josh
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Josh wrote:
That's surprising since my Acer Ferrari 4005 never had a problem with the Synaptics touchpad on both FC4, FC5t1 and Rawhide. Did have to boot with i8042.nomux no_timer_check though. Maybe you could try that. Ipw2200 on an Acer Ferrari 4005? Mine has a Broadcom chip and according to the Acer website all Ferrari 4005 models have that. Don't know how you got an Intel wireless chipset on an AMD motherbord :P
I wasn't aware of the boot parameter to get synaptics touchpad. Does your touch pad work without the parameter?
not for me it doesnt' - even with this new kernel, i need that i8042.nomux param to make it work properly.
I ditched the default broadcom wireless NIC and bought Intel 2915 ABG mini-pci adapter for $29. Works great ;-)
the internal WiFi works fine, even the front push button for radio on and radio off work fine with ndiswrapper and EL4 / FC4 / Rawhide kernels - I've not had a problem at all.
considering the bcm driver needs 2.6.15 - anyone tried it with these new kernels that dave is putting out there ?
Karanbir Singh wrote:
Josh wrote:
That's surprising since my Acer Ferrari 4005 never had a problem with the Synaptics touchpad on both FC4, FC5t1 and Rawhide. Did have to
boot with i8042.nomux no_timer_check though. Maybe you could try that.
Ipw2200 on an Acer Ferrari 4005? Mine has a Broadcom chip and
according to the Acer website all Ferrari 4005 models have that. Don't know how you got an Intel wireless chipset on an AMD motherbord :P
I wasn't aware of the boot parameter to get synaptics touchpad. Does your touch pad work without the parameter?
not for me it doesnt' - even with this new kernel, i need that i8042.nomux param to make it work properly.
I ditched the default broadcom wireless NIC and bought Intel 2915 ABG mini-pci adapter for $29. Works great ;-)
the internal WiFi works fine, even the front push button for radio on and radio off work fine with ndiswrapper and EL4 / FC4 / Rawhide kernels
- I've not had a problem at all.
considering the bcm driver needs 2.6.15 - anyone tried it with these new kernels that dave is putting out there ?
While we are on the subject of the Acer Ferrari 4005 - has anyone got the battery meter to work ?
On Sun, 2005-12-18 at 16:26 +0000, Karanbir Singh wrote:
While we are on the subject of the Acer Ferrari 4005 - has anyone got the battery meter to work ?
You need an updated DSDT for the kernel to do that, and some other power saving things.
It would be nice if Acer updated their BIOS to fix spelling errors in their DSDT, so that we could just install a plain kernel.
How does windows manage to work with buggy DSDTs anyway?
You need to recompile the kernel for the ACPI to work properly, as the FC4 kernels do not include the patch to enable loading a new DSDT via the initrd. (Which, in the long run is more than likely the right decision, so don't bug the RH guys ;) )
Phil
While we are on the subject of the Acer Ferrari 4005 - has anyone got the battery meter to work ? Battery does not work on Ferrari 4005 with FC4 x86_64. I have filed a bug. This seems to be due to ACPI error.
Josh
--------------------------------- Yahoo! for Good - Make a difference this year.
On Thu, 2005-12-22 at 15:10 -0800, Josh wrote:
While we are on the subject of the Acer Ferrari 4005 - has anyone got the battery meter to work ?
Battery does not work on Ferrari 4005 with FC4 x86_64. I have filed a bug. This seems to be due to ACPI error.
Yup it works for me but only after a kernel recompile with the DSDT patch added so that during boot the kernel looks for a new (fixed) DSDT in the initrd and loads that one. Iirc Dave was not interested in adding the patch to the kernel for support reasons so you will have to do the rebuild trick with each new released kernel.
My fixed dsdt for bios <something>A23 can be found here: http://www.xs4all.nl/~pjl/dsdt/dsdt.dsl
I got my crash course in how to fix this from: http://forums.gentoo.org/viewtopic.php?t=122145
The DSDT patch is here: http://gaugusch.at/ I used acpi-dsdt-initrd-v0.7e-2.6.14.patch On that page you can also find instructions how to apply the compiled dsdt to your initrd.
The Intel dsdt compiler stuff is here: http://developer.intel.com/technology/iapc/acpi/downloads.htm
Regards, Patrick
Am Donnerstag, den 29.12.2005, 17:25 +0100 schrieb Patrick:
Yup it works for me but only after a kernel recompile with the DSDT patch added so that during boot the kernel looks for a new (fixed) DSDT in the initrd and loads that one. Iirc Dave was not interested in adding the patch to the kernel for support reasons [...]
That's true afaik. But what IMHO is more important: Upstream doesn't want it, too. See: http://sourceforge.net/mailarchive/message.php?msg_id=9175150
Those that have problems with ACPI/DSDT IMHO should fill bugs in the kernel bugzilla to get the damn acpi interpreter fixed. Nothing is getting better in the long term if everybody privately works around problems and uses a patched firmware without fixing the underlying problems.
Or convince the kernel developers that patching the dsdt is the best solution and that the dsdt-in-initrd-patch needs to be merged into the kernel. Maybe then it's getting enabled in Fedora.
On Thu, 2005-12-29 at 18:31 +0100, Thorsten Leemhuis wrote:
Am Donnerstag, den 29.12.2005, 17:25 +0100 schrieb Patrick:
Yup it works for me but only after a kernel recompile with the DSDT patch added so that during boot the kernel looks for a new (fixed) DSDT in the initrd and loads that one. Iirc Dave was not interested in adding the patch to the kernel for support reasons [...]
That's true afaik. But what IMHO is more important: Upstream doesn't want it, too. See: http://sourceforge.net/mailarchive/message.php?msg_id=9175150
I respectfully disagree with Len Brown that "DSDT overrides are for developers, not end-users, not customers". I want all the stuff on my laptop to work and if it takes a DSDT override so be it. Pointless since he decided against it but nevertheless.
Those that have problems with ACPI/DSDT IMHO should fill bugs in the kernel bugzilla to get the damn acpi interpreter fixed. Nothing is getting better in the long term if everybody privately works around problems and uses a patched firmware without fixing the underlying problems.
I thought that the DSDT lives in the board's bios. How would a fix to an interpreter solve problems if the DSDT itself contains the error(s)? E.g. the DSDT on my Acer 4005 with bios 3a23 needs "Z00I" replaced with "Z001" in two places. Don't see how an interpreter-fix could solve this typo but maybe I totally misunderstand something.
Or convince the kernel developers that patching the dsdt is the best solution and that the dsdt-in-initrd-patch needs to be merged into the kernel. Maybe then it's getting enabled in Fedora.
No idea how to do that.
Regards, Patrick
Am Donnerstag, den 29.12.2005, 20:59 +0100 schrieb Patrick:
On Thu, 2005-12-29 at 18:31 +0100, Thorsten Leemhuis wrote:
Am Donnerstag, den 29.12.2005, 17:25 +0100 schrieb Patrick:
Yup it works for me but only after a kernel recompile with the DSDT patch added so that during boot the kernel looks for a new (fixed) DSDT in the initrd and loads that one. Iirc Dave was not interested in adding the patch to the kernel for support reasons [...]
That's true afaik. But what IMHO is more important: Upstream doesn't want it, too. See: http://sourceforge.net/mailarchive/message.php?msg_id=9175150
I respectfully disagree with Len Brown that "DSDT overrides are for developers, not end-users, not customers".
Tell him -- a lot of users whine on the fedora-lists that Fedora does not have the dsdt-in-initrd patch. But I see seldom someone whine ^w request the inclusion of that patch where it should be done: upstream, e.g. on acpi-devel and/or lkml.
[...]
Those that have problems with ACPI/DSDT IMHO should fill bugs in the kernel bugzilla to get the damn acpi interpreter fixed. Nothing is getting better in the long term if everybody privately works around problems and uses a patched firmware without fixing the underlying problems.
I thought that the DSDT lives in the board's bios. How would a fix to an interpreter solve problems if the DSDT itself contains the error(s)?
I thought this is pretty obvious: There is at least one Operating System out there that works perfectly with the hardware.
The acpi interpreter on that OS might be to lax and have lots of bugs, but at least it works (somehow). The acpi interpreter on linux probably needs to be as lax (with a special boot option if necessary) and probably even bug-to-bug compatible. That's not nice, but at least it gives all users (even newbies) working machines. And that should be the goal for the long term IMHO.
E.g. the DSDT on my Acer 4005 with bios 3a23 needs "Z00I" replaced with "Z001" in two places. Don't see how an interpreter-fix could solve this typo but maybe I totally misunderstand something.
Well, that seems stupid and something like this probably needs to be fixed by the hardware manufacturer. But the argument still holds: There is probably at least one Operating System out there that works perfectly with the hardware, even with this bug.
Or convince the kernel developers that patching the dsdt is the best solution and that the dsdt-in-initrd-patch needs to be merged into the kernel. Maybe then it's getting enabled in Fedora.
No idea how to do that.
Just use a different mailinglist (e.g. acpi-devel or lkml) and request the inclusion of that patch. But I doubt that you'll be successful. But maybe the right people will notice the problem behind your request and will try to solve it somehow.
CU thl
Hi Dave. Booting this kernel prevents X to start on my laptop.
It looks that /sys/class/input does not contain all the entries needed (the laptop is an ancient HP Omnibook equipped with a synaptics touchpad).
I I normally use a custom 2.6.15-rc5 kernel, with evdev compiled as module. That module is loaded _after_ udev has started and this way everithing works. Your kernel as evdev statically linked.
I know that to use a 2.6.15-rcx kernel you are supposed to upgrade udev (mine is udev-058-1.0.FC4.1) but you said that this kernel was intended to be used with FC4 and not with rawhide, so I assumed that it had to work with 0.58.
Please let me know if you need more test/details.
On 12/16/05, Dave Jones davej@redhat.com wrote:
To try and get a jump-start on testing 2.6.15, I've prepared packages for FC4 based on the current rawhide kernel.
These are likely to change almost daily, and there's no guarantee how much longer 2.6.15 is going to be in -rc stage, so I'm going to hold off pushing these out as an official updates-testing release until a final 2.6.15 has been released. (Should a security errata be needed before then, I'll push out another 2.6.14 based release)
http://people.redhat.com/davej/kernels/Fedora/FC4/
Please file bugs in bugzilla, rather than emailing me/this list about them.
Dave
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
Well, my report was not very accurate :-(
On 12/17/05, Fabio Comolli fabio.comolli@gmail.com wrote:
Hi Dave. Booting this kernel prevents X to start on my laptop.
It looks that /sys/class/input does not contain all the entries needed (the laptop is an ancient HP Omnibook equipped with a synaptics touchpad).
/sys/class/input is OK, the problem is in /dev/input.
With my 2.6.15-rc5 with evdev compiled as module /dev/input looks like:
[fcomolli@tycho ~]$ ls -l /dev/input/ total 0 crw-rw---- 1 root root 13, 64 Dec 17 2005 event0 crw-rw---- 1 root root 13, 65 Dec 17 2005 event1 crw-rw---- 1 root root 13, 63 Dec 17 2005 mice
with 2.6.14-1.1768_FC4 there is only the "mice" entry (and this is what pointed my to evdev).
BTW, there is another minor problem: kernel 2.6.14-1.1768_FC4 boots in verbose mode even with the "quiet" boot option set.
Regards, Fabio
I I normally use a custom 2.6.15-rc5 kernel, with evdev compiled as module.
That module is loaded _after_ udev has started and this way everithing works. Your kernel as evdev statically linked.
I know that to use a 2.6.15-rcx kernel you are supposed to upgrade udev (mine is udev-058-1.0.FC4.1) but you said that this kernel was intended to be used with FC4 and not with rawhide, so I assumed that it had to work with 0.58.
Please let me know if you need more test/details.
On 12/16/05, Dave Jones davej@redhat.com wrote:
To try and get a jump-start on testing 2.6.15, I've prepared packages for FC4 based on the current rawhide kernel.
These are likely to change almost daily, and there's no guarantee how much longer 2.6.15 is going to be in -rc stage, so I'm going to hold off pushing these out as an official updates-testing release until a final 2.6.15 has been released. (Should a security errata be needed before then, I'll push out another 2.6.14 based release)
http://people.redhat.com/davej/kernels/Fedora/FC4/
Please file bugs in bugzilla, rather than emailing me/this list about them.
Dave
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
Bugzilla 176011 and 176012
On 12/17/05, Fabio Comolli fabio.comolli@gmail.com wrote:
Well, my report was not very accurate :-(
On 12/17/05, Fabio Comolli fabio.comolli@gmail.com wrote:
Hi Dave. Booting this kernel prevents X to start on my laptop.
It looks that /sys/class/input does not contain all the entries needed (the laptop is an ancient HP Omnibook equipped with a synaptics touchpad).
/sys/class/input is OK, the problem is in /dev/input.
With my 2.6.15-rc5 with evdev compiled as module /dev/input looks like:
[fcomolli@tycho ~]$ ls -l /dev/input/ total 0 crw-rw---- 1 root root 13, 64 Dec 17 2005 event0 crw-rw---- 1 root root 13, 65 Dec 17 2005 event1 crw-rw---- 1 root root 13, 63 Dec 17 2005 mice
with 2.6.14-1.1768_FC4 there is only the "mice" entry (and this is what pointed my to evdev).
BTW, there is another minor problem: kernel 2.6.14-1.1768_FC4 boots in verbose mode even with the "quiet" boot option set.
Regards, Fabio
I I normally use a custom 2.6.15-rc5 kernel, with evdev compiled as
module. That module is loaded _after_ udev has started and this way everithing works. Your kernel as evdev statically linked.
I know that to use a 2.6.15-rcx kernel you are supposed to upgrade udev (mine is udev-058-1.0.FC4.1) but you said that this kernel was intended to be used with FC4 and not with rawhide, so I assumed that it had to work with 0.58.
Please let me know if you need more test/details.
On 12/16/05, Dave Jones <davej@redhat.com > wrote:
To try and get a jump-start on testing 2.6.15, I've prepared packages for FC4 based on the current rawhide kernel.
These are likely to change almost daily, and there's no guarantee how much longer 2.6.15 is going to be in -rc stage, so I'm going to hold off pushing these out as an official updates-testing release until a final 2.6.15 has been released. (Should a security errata be needed before then, I'll push out another 2.6.14 based release)
http://people.redhat.com/davej/kernels/Fedora/FC4/
Please file bugs in bugzilla, rather than emailing me/this list about them.
Dave
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list