Help please!
Running Fedora Core3 on a Satellite Toshiba 5205-s505
spec: P4 M 2 GHz
512 MB Ram
nVidia Ge Force 32Mb graphics
60 Gb hard drive with a 20Gb partition running Fedora (dual boot XP Home)
Kernel: 2.6.10 1.770
Kino installed
cannot get it to recognise my Sony DV handycam
Plugged into the laptop thro a minifirewire port (Texas OHCI ieee1394 controller)
raw1394 compiled and installed; make dev command done but can do it only as root

Kino error: raw1394 module not loaded
modprobe raw1394/ohci1394: bash command not found (even as root)

what can i do next to make the kernel recognise the camera; camera is switched on and in player mode at boot up.
thanks in advance for any help

lightchain

Check to see which firewire controller you have. If it's this one:

# lspci | grep 1394
02:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)

then you need to patch and rebuild your kernel. I have the 5105-s607, and this patch did the trick for me. Also, let rob at janerob dot com know the results of the patch, so that this can eventually be added to the standard kernel.

thank you macemonta
excuse my ignorance; i am a complete newbie with no IT exposure whatsoever; exactly how does one go abt building a kernel or patching it? I went to taht link (Ta!) but cannot make any sense out of it
can you take me thro some command line stuff to apply the patch
thanks very much
lightchain

1. Install new kernel source

* Download the latest kernel source from:
http://download.fedora.redhat.com/pu...ore/updates/3/
* rpm -Uvh kernel-x.y.z-abc.src.rpm
* cd /usr/src/redhat/SPECS/
* rpmbuild -bp --target=i686 kernel-2.6.spec

2. Build kernel

* cd /usr/src/redhat/BUILD/kernel-x.y.z/linux-x.y.z
* cp configs/kernel-2.6.xx-i686.config ./.config
* update Makefile kernel id to uniquely identify the build:
EXTRAVERSION = -x.yyy_FC3aa
* make oldconfig && make clean
* cd drivers/ieee1394/
* patch < /usr/local/src/tosh-1394.patch
* cd ../../
* make rpm
(this will take about 30 minutes)
* rpm -ivh /usr/src/redhat/RPMS/i386/kernel-2.6.xxx.yyy.zzz_FC3aa.rpm
* mkinitrd /boot/initrd-2.6.xxx.yyy.zzz_FC3aa 2.6.xxx.yyy.zzz_FC3aa
* Update:
/boot/grub/grub.conf

If you are using the Nvidia binary driver, reboot and install them as usual after a new kernel.

lightchain

Don't think you need to compile a Kernel FC3 recognized my Canon camcorder after a little playing

First thing for some reason even as root you have to use sbin/modprobe on Fedora this is also true of Redhat, something to do with "Path" never bothered to sort it out just used the command as above

On Suse at the moment will do a little digging to find out exactly how I did it, be back soon

Pete

Pete- The problem on this Toshiba series is that the Firewire interface is non-standard. A pci quirks fix is in progress, but until then the patch is needed (if the machine has the TSB43AB22/A controller).

Mace

macemoneta

Sorry my ignorance

Just for reference on FC3 using a desktop, laptops aside

As root
mknod –m 666 /dev/raw1394 c 171 0
/sbin/modprobe raw1394
/sbin/modprobe ohci1394
/sbin/modprobe video1394

This worked for me but obviously lightchain has bigger problems

Pete

macemoneta wrote
2. Build kernel

* cd /usr/src/redhat/BUILD/kernel-x.y.z/linux-x.y.z
* cp configs/kernel-2.6.xx-i686.config ./.config
* update Makefile kernel id to uniquely identify the build:
EXTRAVERSION = -x.yyy_FC3aa

thank you Pete M and Macemoneta,
I have downloaded the kernel src as you had said (2.6.10-1.770)
I am stuck at the Build kernel part; I can copy configs/kernel-2.6.10-i686.config; it asks whether it is allright to overwrite and i said yes
the next command
EXTRAVERSION = -x.yyy_FC3aa
excuse my ignorance: what shd be x.yyy and FC3aa?
After this I patched and tried make rpm and it said

[root@localhost linux-2.6.10]# make clean
CLEAN usr
[root@localhost linux-2.6.10]# cd drivers/ieee1394/
[root@localhost ieee1394]# patch < /usr/local/src/tosh-1394.patch
-bash: /usr/local/src/tosh-1394.patch: No such file or directory
[root@localhost ieee1394]# patch < /usr/local/src/tosh-1394.patch
-bash: /usr/local/src/tosh-1394.patch: No such file or directory
[root@localhost ieee1394]# cd /home/msuresh/Desktop
[root@localhost Desktop]# cp tosh-1394.patch /usr/local/src/
[root@localhost Desktop]# cd /usr/local/src/
[root@localhost src]# ls -a
. .. tosh-1394.patch
[root@localhost src]# cd drivers/ieee1394/
-bash: cd: drivers/ieee1394/: No such file or directory
[root@localhost src]# cd /usr/src/redhat/BUILD/kernel-2.6.10/linux-2.6.10
[root@localhost linux-2.6.10]# cd drivers/ieee1394
[root@localhost ieee1394]# patch < /usr/local/src/tosh-1394.patch
patching file ohci1394.c
[root@localhost ieee1394]# cd ../ ../
[root@localhost drivers]# make rpm
make: *** No rule to make target `rpm'. Stop.
[root@localhost drivers]# cd /usr/src/redhat/BUILD/kernel-2.6.10/linux-2.6.10
[root@localhost linux-2.6.10]# cp configs/kernel-2.6.10-i686.config ./ .config
cp: copying multiple files, but last argument `.config' is not a directory
Try `cp --help' for more information.
[root@localhost linux-2.6.10]# cp configs/kernel-2.6.10-i686.config ./.config
cp: overwrite `./.config'? y
[root@localhost linux-2.6.10]# update Makefile
-bash: update: command not found
[root@localhost linux-2.6.10]# Makefile
-bash: Makefile: command not found
[root@localhost linux-2.6.10]# Makefile kernel id
-bash: Makefile: command not found
[root@localhost linux-2.6.10]# update
-bash: update: command not found
[root@localhost linux-2.6.10]#

Help please

OK, you downloaded 2.6.10-1.770_FC3. The header in the Makefile says:

VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 10

That where the 2.6.10 comes from. The EXTRAVERSION in the Fedora name would be "-1.770_FC3". You could use that, but then how would you tell your kernel from a Fedora kernel? What I suggest is that you add your initials. For example, my initials are "mm", so EXTRAVERSION becomes:

EXTRAVERSION = -1.770_FC3mm

You're getting confused as to where you are in the file hierarchy - a very common problem. If you get lost, use the 'pwd' command to see where you currently are.

When I wrote "update Makefile", I meant use an editor (whatever your favorite is; I use "vi") to change the content of the file "Makefile". For example:

vi Makefile

If you're not familiar with vi, you can also use gedit (the same editor in the Accessories in the main menu):

gedit Makefile

hi macemoneta
thanks for clearing the extraversion and Makefile commands
I did as you suggested and tried to name the custom kernel as 2.6.10-1.770_FC3sm; but it has named it as 2.6.101.770_FC3sm-1 for some reason and has created a rpm of the same name. (see below)
I have installed the rpm with the rpm -ivh command
The next step mkinitrd /boot/blah..blah is returned with a mkinitrd command not found error. Any advice please...!!!!

[msuresh@localhost ~]$ su
Password:
[root@localhost msuresh]# cd /usr/src/redhat/RPMS/i386
[root@localhost i386]# ls
kernel-2.6.101.770_FC3sm-1.i386.rpm
[root@localhost i386]# rpm -ivh *.rpm
Preparing... ########################################### [100%]
1:kernel ########################################### [100%]
[root@localhost i386]# mkinitrd /boot/initrd-2.6.101.770_FC3sm-1 2.6.101.770_FC3 sm-1
bash: mkinitrd: command not found
[root@localhost i386]# cd /usr/src
[root@localhost src]# ls
debug linux linux-2.6.10 linux-2.6.9 redhat
[root@localhost src]# cd /usr/src/linux-2.6.10
[root@localhost linux-2.6.10]# mkinitrd /boot/initrd-2.6.101.770_FC3sm-1 2.6.101.770_FC3sm-1 bash: mkinitrd: command not found
[root@localhost linux-2.6.10]#

thanks
lightchain

That is the name of the rpm file, not the name of the kernel. Issue this command to confirm the name of the kernel:

rpm -q kernel

Hi mm
this is what I got, no joy still

[msuresh@localhost ~]$ su
Password:
[root@localhost msuresh]# cd /usr/src/linux-2.6.10
[root@localhost linux-2.6.10]# pwd
/usr/src/linux-2.6.10
[root@localhost linux-2.6.10]# rpm -q kernel
kernel-2.6.9-1.667
kernel-2.6.10-1.770_FC3
kernel-2.6.101.770_FC3sm-1
[root@localhost linux-2.6.10]# mkinitrd /boot/initrd-2.6.101.770_FC3sm-1 2.6.101.770_FC3sm-1 bash: mkinitrd: command not found
[root@localhost linux-2.6.10]#

my grub looks like this (no entry of the new kernel)

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,5)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/hda
default=4
timeout=10
splashimage=(hd0,5)/grub/splash.xpm.gz
#hiddenmenu
title Fedora Core (2.6.10)
root (hd0,5)
kernel /vmlinuz-2.6.10 ro root=/dev/VolGroup00/LogVol00 3
initrd /initrd-2.6.10.img
title Fedora Core (2.6.10-1.770_FC3)
root (hd0,5)
kernel /vmlinuz-2.6.10-1.770_FC3 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.10-1.770_FC3.img
title Memtest86+ v1.50
kernel /memtest86+-1.50
title Fedora Core (2.6.9-1.667)
root (hd0,5)
kernel /vmlinuz-2.6.9-1.667 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.9-1.667.img
title windows xp home
rootnoverify (hd0,0)
chainloader +1

what shd I do next?
thank you
lightchain

lightchain

Try

[root@localhost linux-2.6.10]# sbin/mkinitrd /boot/initrd-2.6.101.770_FC3sm-1

Add sbin as above, just a guess

If specifying the full path doesn't work, you'll need to install it:

yum -y install mkinitrd

When building a custom kernel, you will need to update the /etc/grub.conf manually.

Duplicate the previous entry, and update the version information on the files. For example, for your new kernel name, add the following to the grub.conf, just after the "#hiddenmenu":

Correction to my last port: The rpm file name will NOT match the new kernel name. You need to:

ls -ltr /boot/vmlinuz*

In your case the last kernel will probably be called vmlinuz-2.6.10-1.770_FC3sm, so your mkinitrd command and /etc/grub.conf entries will be:

mkinitrd /boot/initrd-2.6.10-1.770_FC3sm 2.6.10-1.770_FC3sm