On Wed, 2004-06-09 at 13:12, Arjan van de Ven wrote:
On Wed, 2004-06-09 at 14:02, D. D. Brierton wrote:
On Wed, 2004-06-09 at 08:28, Arjan van de Ven wrote:
Hi,
the plan is to do a kernel update friday or monday (depending on the amount of things that turn up in this testing). There is a 424 kernel in the testing dir on the ftp repository and on http://people.redhat.com/arjanv/2.6 One of the last minute changes is a series of patches to the input subsystem that are supposed to fix a lot of the "tapping my laptops touchpad doesn't work" bugs. So please beat hard on this kernel...
Does this kernel have FireWire re-enabled?
yes so if you have firewire hw, do beat on it too...
So, I finally installed FC2 yesterday, and immediately updated to 2.6.6-1.427. FireWire seems to be working absolutely fine: my external Iomega 120GB FireWire drive was detected and the nightly backup onto it seems to have gone without incident. I have copied large (~400MB) files to and from it without incident so far.
There was only one thing regarding this that struck me as not quite right, but it's not a problem with the kernel but rather with kudzu. When I first booted into 2.6.6-1.427 with the FireWire drive attached kudzu recognised the device and asked if I wanted to configure it to which I said yes. However, kudzu did not create a mount point for it like it does for CD drives and floppies which I think it should. I created an entry in fstab and a mount point in /mnt, but still no icon for the drive showed up on my GNOME desktop even when the device was mounted. I then added the option "users" to the fstab entry and an icon appeared on the desktop. None of that was really a problem for me, but a newbie would have just thought that FC2 was failing to see the external drive. Should I bugzilla this (against kudzu/updfstab)?
Best, Darren