I just finished installing a new kernel, 2.6.7 to get the nvidia driver working. details are here: http://www.linuxquestions.org/questi...5&pagenumber=3

anyways, the new kernel works fine with the nvidia driver, but my mouse doesn't work at all!
It's NOT a driver issue like I originally thought because I went back to the nv driver with kernel 2.6.7 and still the mouse refuses to work. I thought maybe I had compiled the kernel wrong, but I can't tell for sure because KDE won't let me configure a kernel >=2.5.
also, for the /boot/config* files:
After I installed the new kernel, /boot/config was a link to /boot/config-2.4.26 At first I thought this might be the problem but `diff config-2.4.26 config-2.6.7` returned nothing. So then I copied /usr/src/linux/.config (where linux -> linux-2.6.7) to /boot and renamed it config-2.6.7, since this was the config file i used to compile the kernel, does this make sense to do? then I linked /boot/config to the new /boot/config-2.6.7.
STILL THE MOUSE DOES NOT WORK!!!!

How can I configure the kernel, or check how it is currently configured? I tried running `make menuconfig` in /usr/src/linux but it prompted me to run make. I didn't want to compile a whole new kernel, just to see what was in my cuirrent one!

you should be able to run make menuconfig without running make... is it telling you to run make before the menuconfig comes up? if so... /usr/src/linux is probably a symlink to the 2.4.26 sources since you built the new one in /usr/src/linux-2.6.7 right?


Also, make install would have copied over a new config, System.map, and vmlinuz if you edited the Makefile in /usr/src/linux-2.6.7.

I'm willing to keep helping though...

ls -l /usr/src/linux
lrwxrwxrwx 1 root root 11 2004-09-08 20:50 /usr/src/linux -> linux-2.6.7

When I use `make menuconfig` it really wants me to rebuild the kernel:

/usr/src/linux# make menuconfig
scripts/kconfig/mconf arch/i386/Kconfig
#
# using defaults found in .config
#


*** End of Linux kernel configuration.
*** Execute 'make' to build the kernel or try 'make help'.

weird... try copying /boot/config-2.6.7 back to /usr/src/linux/.config and run make menuconfig...

OK... everything (almost) seems to be working. The mouse problem was fixed. turns out I needed to add `/sbin/modprobe psmouse` to /etc/rc.d/rc.modules
When I tried to do this under 2.4.26, I got an error that the module could not be found, but I think this was probably because it was built into tha kernel. This time I think i made it a module. What also threw me was that this line did not appear in the modules file (it wasn't already yhere, but commented out) I had to add it myself. well, it seems to be working now, except for the dreaded

# cdrecord -scanbus
Cdrecord 2.00.3 (i686-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.

headache. but I do remember hearing there was a patch to fix that, so I should probably go look that up before I post again.
thanks, all!

you can still use append="hdc=ide-scsi" and use scsi emulation (which is what I do even though it is officially frowned on) or use ide-cd...

also, if you're using 2.6.7 now I'd look into udev... (/etc/rc.d/rc.udev) and see if it is starting at boot... if it isn't chmod 0755 rc.udev so that it will...

then, you need to write some rules for udev to set up symlinks for you. Here are some for ide and scsi cdroms (you can have both it will create symlinks for whichever one you're using:"

create a file called /etc/udev/rules.d/10-local.rules

-----10-local.rules-----
BUS="ide", KERNEL="hdc", NAME="%k", GROUP="cdrom", SYMLINK="cdrom dvd cdrw"

BUS="scsi", KERNEL="sr0", NAME="%k", GROUP="cdrom", SYMLINK="cdrom dvd cdrw"

-----END-----

Using udev with ide-scsi should fix your cdrecord error... or you can use this in the meantime:

cdrecord dev=ATAPI -scanbus

"Using udev with ide-scsi"... do you mean i should continue to have append="hdc=ide-scsi" in lilo.conf? I don't have it for my 2.6.7 image. I did everything else, though, and nothing seems to have changed.

also, video playback (mpg, haven't tried any others yet.) is completely screwed up. frame rate drops way low, tons of artifacting.

It's a personal choice to continue to use scsi emulation... I'm still using it... but it should fix the cdrecord error... as for the choppy video... not sure... do you have dma enabled on your drives?

I'm getting quite confused here...
Was your post completely about scsi emulation? how would I use the device normally (without scsi emulation)?

tunrs out only mpg is choppy. avi is fine. haven't tried wmv yet

try :
append="hdc=ide-cd"
with kernel 2.6.x

and :
cdrecord dev=ATAPI:/dev/hdc -scanbus

burn cd image with (example with 16x speed) :
cdrecord -v dev=ATAPI:/dev/hdc -speed 16 <file.iso>

My post was about using scsi emulation with kernel 2.6 (which is officially deprecated but works)... Cedrick posted how to use cdrecord w/o scsi emulation ----> this was to address your cdrecord issue.


The udev part is about device loading with kernel 2.6... you can use devfs (which is the standard, old way with 2.4 kernels) or use udev (which I described how to set up by creating a 10-local.rules file in /etc/udev/rules.d). This won't do you any good though if udev isn't loading at boot, hence the:

chmod 0755 /etc/rc.d/rc.udev

Sorry if my responses don't make any sense...

/etc/rc.d/rc.udev has permission set so that everyone can execute. and I did the whole 10-local.rules thingy just like you said. I'm not using the scsi emu if it's not considered the proper thing for this kernel.
Cedric's tip seemed to work:

# cdrecord dev=ATAPI:/dev/hdc -scanbus
Cdrecord 2.00.3 (i686-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling
scsidev: 'ATAPI:/dev/hdc'
devname: 'ATAPI:/dev/hdc'
scsibus: -2 target: -2 lun: -2
Warning: Using ATA Packet interface.
Warning: The related libscg interface code is in pre alpha.
Warning: There may be fatal problems.
Using libscg version 'schily-0.7'
scsibus0:
0,0,0 0) 'HL-DT-ST' 'CD-RW GCE-8523B ' '1.01' Removable CD-ROM
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *

only those warnings are kinda troubling... had anyone really had problems with it? and is there an easier way to get it working? it's quite a mouthful to remember

You don't have to use scanbus with kernel 2.6 and ide-cd driver anyway.

Just make your iso file and burn cd like that :
mkisofs -o file.iso /directory/to/burn
cdrecord -v -speed 16 dev=/dev/hdc file.iso

or :
mkisofs -R /directory/to/burn | cdrecord -v fs=6m speed=16 dev=/dev/hdc -

You can try -dummy option to simulate a burn command (won't burn the CD)
cdrecord -dummy -speed 16 dev=/dev/hdc file.iso

[edit]
For each example the speed is 16x, up to you to set it