I compiled a new kernel using my last menuconfig for 2.6.10-rc2, in order to use new VDR software with my DVB card. The new 2.6.14-rc2 kernel boots up fine, and everything except VDR seems to be OK, but VDR won't start.

I see a flash on the TV sreen early in the boot process, which seems to indicate the new DVB drivers loaded OK, but then I get a flickering TV screen on which I can just make out the message: /dev/input/event0 "No such device".

I checked and "event interface" is selected to load as a module. I rebooted into the old 2.6.10-rc2 kernel, and VDR stilll loads fine there.

In the new kernel running dmesg after trying to start VDR produces about 50 lines of:

end_request: I/O error, dev fd0, sector 0

The floppy drive works fine: mounts, reads the disc etc. But the pc does seem to be searching for it all the time. (I hear the telll=tale clunk clunk clunk).

I don't see anything like evdev in the lsmod output, below.

odule Size Used by
nls_cp437 5696 0
snd_pcm_oss 52896 0
snd_mixer_oss 19392 3 snd_pcm_oss
thermal 13576 0
fan 4548 0
button 6544 0
processor 18156 1 thermal
ac 4804 0
uhci_hcd 33936 0
dvb_ttpci 336160 0
dvb_core 83496 1 dvb_ttpci
l64781 7812 1 dvb_ttpci
saa7146_vv 50112 1 dvb_ttpci
video_buf 22148 1 saa7146_vv
saa7146 18504 2 dvb_ttpci,saa7146_vv
v4l1_compat 14468 1 saa7146_vv
v4l2_common 5824 1 saa7146_vv
videodev 9600 1 saa7146_vv
ves1820 6212 1 dvb_ttpci
stv0299 11784 1 dvb_ttpci
tda8083 6532 1 dvb_ttpci
stv0297 8896 1 dvb_ttpci
sp8870 8012 1 dvb_ttpci
firmware_class 10688 2 dvb_ttpci,sp8870
ves1x93 7108 1 dvb_ttpci
ttpci_eeprom 2688 1 dvb_ttpci
nls_iso8859_1 4032 1
dm_mod 59004 0
parport_pc 36420 1
lp 11588 0
parport 37320 2 parport_pc,lp
unix 28652 598

I changed my /etc/fstab to comment out both floppy and NTFS lines and rebooted with no change to this behavior:

etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda3 / ext3 defaults,errors=remount-ro 0 1
/dev/hda2 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 ro,user,noauto 0 0
/dev/hdd /media/cdrom1 udf,iso9660 ro,user,noauto 0 0
# /dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
# /dev/hda1 /mnt/winxp ntfs ro,auto,uid=1000,gid=1000 0 0


When I look into /dev/input with the file browser, all the icons (including event0) have a red "X" next to them. If these are symlinks, they must be broken.

The system is definately looking for something on the floppy. When a disc is inserted, the green light is on continuously. Take the disc out, and it clunks away with each clunk adding another line of: "end_request: I/O error, dev fd0, sector 0" to dmesg.

I checked my menuconfig again and it's built like this:

--- Generic input layer (needed for keyboard, mouse, ...) │ │
│ │ --- Userland interfaces │ │
│ │ --- Mouse interface │ │
│ │[*] Provide legacy /dev/psaux device │ │
│ │ (1024) Horizontal screen resolution │ │
│ │ (76 Vertical screen resolution │ │
│ │ < > Joystick interface │ │
│ │ < > Touchscreen interface │ │
│ │ <M> Event interface │ │
│ │ < > Event debugging │ │
│ │ --- Input Device Drivers │ │
│ │ --- Keyboards ---> │ │
│ │[*] Mouse ---> │ │
│ │ [ ] Joysticks ---> │ │
│ │ [ ] Touchscreens ---> │ │
│ │ [ ] Miscellaneous devices ---> │ │
│ │ Hardware I/O ports --->

I'm at my wit's end here!