Bug#341035: kernel-source-2.6.8: [PATCH] CH Products USB yoke and pedals recognized but frozen by SET_IDLE
I am sorry to have never gotten back to you on this. Unfortunately, the hardware (yoke/pedals) was taken back by whoever lent it to me (I did too good a job of the linux+flightgear combo active demo :-) ), so I was never able to retest this scenario. --vassilii -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341035: kernel-source-2.6.8: [PATCH] CH Products USB yoke and pedals recognized but frozen by SET_IDLE
I have changed my pinning policy to prefer testing over stable: APT policy: (950, 'testing'), (500, 'stable'), (300, 'unstable') and ran a full apt-get dist-upgrade. Having then downgraded freeglut back to the stable's 2.2.0 version and forbidding the current testing release of the 2.4.0 one, I recompiled flightgear, and it worked on Debian testing as well, also seeing the joystick, with the 2.6.14 kernel (sorry for my previous ignorance on this bug thread about the new kernel packaging scheme that had lead me to miss the post 2.6.8 kernel packages in the Debian archive). The funny thing is that (just for fun) I have retested the older (2.6.8) kernel, even after complete power down (with the power cord removed to make sure), and now I see that the CH Products yoke and pedals DO work with my computer (/dev/input/js[01]). Perhaps some change was introduced in the user-level USB utilities (and/or hotplug) that masked (or augmented, if you prefer it this way) the default kernel behaviour. You may reassign the present bug to some other package if you know to which one :-) Hence, I didn't work any further on the issue (my plan was to hunt down if an equivalent patch was needed to a later kernel, and creating a kernel config option to mask this patch for those who are afraid of it). Fly safe (even if in the virtual reality), Vassilii -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341035: kernel-source-2.6.8: [PATCH] CH Products USB yoke and pedals recognized but frozen by SET_IDLE
Package: kernel-source-2.6.8 Version: 2.6.8-16 Severity: normal Tags: patch The devices Bus 004 Device 003: ID 068e:00ff CH Products, Inc. Flight Sim Yoke Bus 004 Device 002: ID 068e:00f2 CH Products, Inc. Flight Sim Pedals on my machine get recognized but they don't work. cat'ting the relevant /dev/input/js* devices reports some initial data, but no axis or button input on any of them produces any change. flightgear/fgjs/js_demo don't show any input either. Following the tip at http://www.qbik.ch/usb/devices/showdev.php?id=587 by Alex Perry, I made the following patch that works perfectly on my system. A better approach would probably be a configure option if somebody does need that extra SET_IDLE call. I'm not x-posting to lkml since 2.6.8 is an ancient source (2.6.14 exists today), but since we only have 2.6.8 in debian archive as of today, I want it available for other Debian users that might want to solve the same problem. --- drivers/usb/input/hid-core.c.orig 2005-11-27 23:53:11.838499336 +0200 +++ drivers/usb/input/hid-core.c2005-11-27 23:53:05.533457848 +0200 @@ -1309,9 +1309,14 @@ void hid_init_reports(struct hid_device * bugfree devices and will cause a worst-case extra delay of * 1ms for buggy ones. */ +#if 0 /* vassilii: disabled tipped by Alex Perry's report for an equivalent + * change of older (2001) source. This allows the USB CH Products + * yoke and pedals to work correctly. + */ usb_control_msg(hid->dev, usb_sndctrlpipe(hid->dev, 0), HID_REQ_SET_IDLE, USB_TYPE_CLASS | USB_RECIP_INTERFACE, (1 << 8), hid->ifnum, NULL, 0, HZ * USB_CTRL_SET_TIMEOUT); +#endif report_enum = hid->report_enum + HID_INPUT_REPORT; list = report_enum->report_list.next; -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (400, 'testing'), (300, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8-ilmarinen Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Versions of packages kernel-source-2.6.8 depends on: ii binutils 2.15-6 The GNU assembler, linker and bina ii bzip2 1.0.2-7high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#290474: sarge r0a i386 netinst partial success, IBM ThinkCentre 8189LDG
Package: installation-reports INSTALL REPORT Debian-installer-version: sarge stable 3.1 r0a netinst i386 CD. Tue Jul 13, 2005 got it from an admin in the BGU CS computing services lab, who downloaded it from an official Debian mirror. uname -a: Linux ilmarinen 2.6.8-2-686 #1 Thu May 19 17:53:30 JST 2005 i686 GNU/Linux Date: Finished circa Wed Jul 13 early A.M., IDT 2005 Method: * Manual installation, at the console. Had a working laptop plugged in as well to talk to the #debian-boot on the irc.freenode.net when problems started happening. * Booted off the ATAPI CD-ROM. Network install from the official Israeli HTTP mirror at deb http://mirror.hamakor.org.il/pub/mirrors/debian/ stable * This happens at home, in a private LAN 10, which is routed (via NAT) to the internet by an Alcatel Speedtouch 510 ADSL modem. Machine: IBM ThinkCentre As per the BIOS machine info screen: * Machine Type/Model: 8189LDG * Flash EEPROM Revision Level: 2AKT48AUS (November 2004, there's a March 2005 version available at the time of writing) * CPU Bus Speed: 800MHz * Memory Speed: 400MHz Processor: processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Intel(R) Pentium(R) 4 CPU 2.60GHz stepping: 9 cpu MHz : 2593.784 cache size : 512 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid bogomips: 5144.57 Memory: total used free sharedbuffers cached Mem:515900 59044 456856 0 26568 10784 -/+ buffers/cache: 21692 494208 Swap: 1373548 01373548 Root Device: SATA WDC 80G drive, sda. discover output from hardware-summary: WDC WD800JD-22JN;/dev/sda Root Size/partition table: Feel free to paste the full partition table, with notes on which partitions are mounted where. * /proc/partitions: major minor #blocks name 8 0 78150744 sda 8 1 128488 sda1 8 21373557 sda2 8 3 498015 sda3 8 4 76148100 sda4 254 05242880 dm-0 254 13145728 dm-1 254 22097152 dm-2 254 37864320 dm-3 * /proc/mounts rootfs / rootfs rw 0 0 /dev2/root2 / ext3 rw 0 0 proc /proc proc rw,nodiratime 0 0 sysfs /sys sysfs rw 0 0 devpts /dev/pts devpts rw 0 0 tmpfs /dev/shm tmpfs rw 0 0 usbfs /proc/bus/usb usbfs rw 0 0 /dev/sda1 /boot ext3 rw 0 0 /dev/mapper/sys-home /home reiserfs rw,noatime 0 0 /dev/mapper/sys-tmp /tmp reiserfs rw 0 0 /dev/mapper/sys-usr /usr reiserfs rw,noatime 0 0 /dev/mapper/sys-var /var reiserfs rw 0 0 Output of lspci and lspci -n: :00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02) :00:01.0 PCI bridge: Intel Corp. 82865G/PE/P PCI to AGP Controller (rev 02) :00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02) :00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 (rev 02) :00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02) :00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 (rev 02) :00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2) :00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02) :00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) Serial ATA 150 Storage Controller (rev 02) :00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) :00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) :01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev a1) :03:08.0 Ethernet controller: Intel Corp. 82562EZ 10/100 Ethernet Controller (rev 02) :03:09.0 Communication controller: PCTel Inc HSP MicroModem 56 (rev 01) :03:0c.0 SCSI storage controller: Advanced System Products, Inc ABP940-U / ABP960-U (rev 03) :00:00.0 0600: 8086:2570 (rev 02) :00:01.0 0604: 8086:2571 (rev 02) :00:1d.0 0c03: 8086:24d2 (rev 02) :00:1d.1 0c03: 8086:24d4 (rev 02) :00:1d.2 0c03: 8086:24d7 (rev 02) :00:1d.3 0c03: 8086:24de (rev 02) :00:1d.7 0c03: 8086:24dd (rev 02) :00:1e.0 0604: 8086:244e (rev c2) :00:1f.0 0601: 8086:24d0 (rev 02) :00:1f.2 0101: 8086:24d1 (rev 02) :00:1f.3 0c05: 8086:24d3 (rev 02) :00:1f.5 0401: 8086:24d5 (rev 02) :01:00.0 0300: 10de:0110 (rev a1) :03:08.0 0200: 8086:1050 (rev 02) :03:09.0 0780: 134d:7891 (rev 01) :03:0c.0 0100: 10cd:1300 (rev 03) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't
Bug#286515: are you sure swap can be labeled?
> > I know that the scsi emulation for cdrw is obsolete, > > but I was asking how to make sure that it doesn't happen in 2.6, > > even when the SATA hard drive forces the SCSI storage drivers into > > existence. > > I cannot verify the module load sequence from here. If you > do 'cat /proc/modules' then you get a list of modules as they > were loaded (with the most recent module on the top). On > my system lsmod returns the same module sequence. Maybe ide-scsi > is loaded much more early than you expected? > > Is it an option to build a kernel without any ide-scsi > support? Indeed, when I built the kernel without the ide-scsi support, the SATA hard drive did work nevertheless, yet the CD-ROM and the CD-RW stayed under the pure IDE drivers control. Unfortunately, though, in this case, despite the docs to the countrary, I had experienced the same long timeouts during the media check and errors on the write when trying to record anything on the CDRW, so I reverted back to the ide-scsi emulation nevertheless. In any case, I was unable to achieve one of them (the CD-ROM) under the ATAPI IDE CD driver control, and the other (the CD-RW) under the SCSI emulation control --- once the ide-scsi was there, the option to ignore the emulation (via the "options ide-scsi hdc=ignore" line in the modprobe.d tree) was itself ignored. Since it all works under 2.6 with the scsi emulation anyway, I don't think it is worth the bother, i.e., at least for me, this is not a big deal. Of course, if somebody wants do debug it, I'll be happy to test things here. And here's the lsmod output: Module Size Used by nvidia 3923228 12 apm21100 1 parport_pc 36900 0 lp 11176 0 parport41800 2 parport_pc,lp binfmt_misc11688 1 ipv6 264644 22 af_packet 22568 2 sr_mod 17316 0 floppy 61200 0 pcspkr 3592 0 snd_intel8x0 34076 1 snd_ac97_codec 78744 1 snd_intel8x0 snd_pcm_oss53768 0 snd_mixer_oss 20032 1 snd_pcm_oss snd_pcm95496 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_timer 25924 1 snd_pcm snd59076 8 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 10336 1 snd snd_page_alloc 10120 2 snd_intel8x0,snd_pcm ehci_hcd 32004 0 usblp 13088 0 tsdev 7392 0 mousedev 10476 1 ov511 99392 0 ovcamchip 26248 0 joydev 9984 0 evdev 9600 0 usbhid 32224 0 videodev 10016 1 ov511 i2c_core 24176 2 ov511,ovcamchip v4l2_common 6144 1 ov511 uhci_hcd 33136 0 usbcore 119012 7 ehci_hcd,usblp,ov511,usbhid,uhci_hcd pci_hotplug34640 0 intel_agp 22816 0 intel_mch_agp 10608 1 agpgart34664 3 nvidia,intel_agp,intel_mch_agp dm_mod 59804 0 capability 4520 0 commoncap 7232 1 capability advansys 82528 0 e100 32608 0 mii 5120 1 e100 ide_cd 42656 0 cdrom 40732 2 sr_mod,ide_cd genrtc 9588 0 ext3 127240 7 jbd62616 1 ext3 mbcache 9348 1 ext3 ide_scsi 17412 0 sg 39168 0 unix 28756 304 font8320 0 vesafb 6656 0 cfbcopyarea 3872 1 vesafb cfbimgblt 3040 1 vesafb cfbfillrect 3776 1 vesafb sd_mod 21728 9 ata_piix8132 8 libata 41700 1 ata_piix scsi_mod 125228 6 sr_mod,advansys,ide_scsi,sg,sd_mod,libata ide_generic 1408 0 ide_core 139940 3 ide_cd,ide_scsi,ide_generic V. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#286515: are you sure swap can be labeled?
On Tue, 29 Mar 2005, Harald Dunkel wrote: > Vassilii Khachaturov wrote: > >>You could use something like > >> > >>LABEL=root / ext2defaults0 1 > >>LABEL=swap none swapsw 0 0 > >>LABEL=home /home ext2defaults0 1 > >> > >>in your /etc/fstab, instead of /dev/hda1 or /dev/sda1. > > > > > > Is your fstab example a real life one, or fictional? in the 1st case, > > how did you manage to have the swap labeled?? > > > > mkswap -L myswap /dev/sda2 -L doesn't work here: travel:/home/vassilii# mkswap -L swap /dev/hda8 Usage: mkswap [-c] [-v0|-v1] [-pPAGESZ] /dev/name [blocks] travel:/home/vassilii# mkswap --version mkswap from util-linux-2.12 travel:/home/vassilii# dlocate /sbin/mkswap util-linux: /sbin/mkswap travel:/home/vassilii# dpkg --status util-linux Package: util-linux Essential: yes Status: install ok installed Priority: required Section: base Installed-Size: 976 Maintainer: LaMont Jones <[EMAIL PROTECTED]> Architecture: i386 Version: 2.12-10 [snip] What version are you using? > > options ide-scsi ignore=hdd > > > > added to the modules.conf (via update-modutils), the scsi > > emulation still grabs hdd (somehow pulled in by the sata_sil?) > > > This is obsolete. What is obsolete? I know that the scsi emulation for cdrw is obsolete, but I was asking how to make sure that it doesn't happen in 2.6, even when the SATA hard drive forces the SCSI storage drivers into existence. > Try something like > > cdrecord /dev/cdrom my.iso > > for writing CDs, regardless whether it is SCSI or IDE. Yeah, and if /dev/cdrom (/dev/cdrw in my case; the cdrom is another - R/O - device) is mapped to a scsi emulation device, I get an error. If I force a link cdrw -> hdd, it doesn't work at all because of the conflict with the scsi emulation layer (AFAIU you may not use an IDE device directly once it's grabbed by the scsi emulation). (I'm away from the PC in question at this time, otherwise I would have cited the precise error msgs. If you need additional input, please tell me.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#286515: are you sure swap can be labeled?
> You could use something like > > LABEL=root / ext2defaults0 1 > LABEL=swap none swapsw 0 0 > LABEL=home /home ext2defaults0 1 > > in your /etc/fstab, instead of /dev/hda1 or /dev/sda1. Is your fstab example a real life one, or fictional? in the 1st case, how did you manage to have the swap labeled?? I don't know how can one label a swap partition, if at all. mkswap/swapon/swapoff don't seem to be providing such an option. I know I can remove the swap partition and create another one with one big file on it to hold the swap, but I suspect from the architectural reasons this will be worse than using a dedicated partition. I have suffered my share of problems with trying to keep 2.4 and 2.6 going together smoothly on the same machine (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=286515 ) and came up with nothing better than going single and moving the appropriate fstab (sda flavoured for 2.6 and hda for 2.4) in place. BTW, I have never figured how to force the cdrw not to work in the ide-scsi emulation mode in 2.6; even with the ide-cd driver preloaded by /etc/modules and an option options ide-scsi ignore=hdd added to the modules.conf (via update-modutils), the scsi emulation still grabs hdd (somehow pulled in by the sata_sil?) Regards, vassilii -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#288812: kernel-image-2.4.27-1-686: upgrade from v2 to v6 breaks nvidia-kernel-2.4.27-1-686
> The unresolved sumbols log would be useful, I am sad to say that an attempt to collect more info resulted in me wasting about 3 hours without a decent result. For some reason, when I rebooted into 2.6 (an attempt to avoid the "you need to reboot soon"), and did dpkg -i kernel-image-2.4.27-1-686_2.4.27-6_i386.deb the resulting kernel didn't want to boot. During the boot log it complained about being unable to load sg.o; I looked at the initrd image and found that sg.o wasn't there indeed. So I added a script /usr/share/initrd-tools/scripts/sg-module, containing the following: #!/bin/sh case "$VERSION" in 2.4.*) cp /lib/modules/$VERSION/kernel/drivers/scsi/sg.o \ $INITRDDIR/lib/modules/$VERSION/kernel/drivers/scsi/ ;; esac and manually re-created the 2.4 initrd. The kernel still refuses to boot, while no longer complaining about the absent sg.o; the last messages it spits out are pivot_root: No such file or directory /sbin/init: 425: could not open dev/console: No such file Kernel panic: Attempted to kill init! An attempt to downgrade back to -2 did not help this time, the results didn't change. Is something broken with my initrd-tools? Was it a stupid idea to do it under 2.6 rather than under 2.4 (the previous upgrades of 2.4 were done while running 2.4)? If you have any ideas what to do, I'll be happy to try them out to collect further info for you. > plus something like lspci that shows what > nvida board you have. So I installed module-assistant, and (under 2.6) did the following: module-assistant prepare module-assistant auto-install nvidia-kernel-source and now I have nvidia acceleration working under my 2.6. Here's the lspci output (collected under 2.6): :00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02) :00:01.0 PCI bridge: Intel Corp. 82865G/PE/P PCI to AGP Controller (rev 02) :00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02) :00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 (rev 02) :00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02) :00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 (rev 02) :00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2) :00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02) :00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) Serial ATA 150 Storage Controller (rev 02) :00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) :00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) :01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1) :03:08.0 Ethernet controller: Intel Corp. 82562EZ 10/100 Ethernet Controller (rev 02) :03:09.0 Communication controller: PCTel Inc HSP MicroModem 56 (rev 01) :03:0c.0 SCSI storage controller: Advanced System Products, Inc ABP940-U / ABP960-U (rev 03) Kind regards, Vassilii
Bug#288812: kernel-image-2.4.27-1-686: upgrade from v2 to v6 breaks nvidia-kernel-2.4.27-1-686
Package: kernel-image-2.4.27-1-686 Version: 2.4.27-6 Severity: normal Following an upgrade from 2.4.27-2 to -6, the nvidia module from nvidia-kernel-2.4.27-1-686 stopped being able to be loaded, reporting unresolved symbols even to an explicit "modprobe nvidia". Forcible downgrade of the kernel back to 2.4.27-2 solved the problem, thanks go to those on #debian that told me about the snapshots server where I could get the old .deb. I have preserved the aptitude log documenting the upgrade, and the XFree86.0.log and kern.log with both sane pre-upgrade and failing post-upgrade traces. Unfortunately, I didn't preserve the exact unresolved symbols info; but, if needed, can re-create the problem and get a log of that as well. If any of the above logs or the unresolved symbols log is needed, please tell, and I'll be happy to send it as well. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.27-1-686 Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Versions of packages kernel-image-2.4.27-1-686 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.74 tools to create initrd image for p ii modutils 2.4.26-1.2 Linux module utilities -- no debconf information
Bug#286515: Workaround: blacklist ehci-hcd
Call this black magic, but when I added ehci-hcd to the top of /etc/hotplug/blacklist, everything started working O.K. I think I can tolerate slightly lower data exchange rate with my USB drives I occasionally plug, much more so than having the computer not booting in a working X with a mouse and printer as it was before I applied the workaround. (The way I got on this was comparing the discover-era boot logs with the present ones and seeing that ehci-hcd is a new thing by hotplug). FYI: in 2.6, without the above hack (but, of course, with the modified fstab to use sda instead of hda), the USB problems do not happen (but a lot of other stuff to configure there remains). V.
Re: Bug#286515: hotplug: Iiyama USB monitor hub unrecognized until re-plugged
> This looks like a kernel problem to me. If your devices do not appear in > the lsusb output, then there is nothing hotplug can do about it. Thanks. Indeed, the same upgrade pulled in the 2.4.27-1-686 update. Would you like me to attempt installing an earlier 2.4 version to check if it is indeed the case? which one? > BTW, you probably want to run a 2.6 kernel. I have just spent a couple of hours trying to do it in a way that would allow me to select between the 2 kernels, and the results are as follows. 1) Just attempting to install it out of the box and booting resulted in a panic. Here are the messages it says before the panic: pivot_root: no such file or directory /sbin/init: 426: cannot open dev/console: no such file Kernel panic: Attempted to kill init! 2) the reason turns out that my IDE drive is a SATA controller :00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) Serial ATA 150 Storage Controller (rev 02) which is treated differently by 2.6 as opposed to 2.4, so that the drive becomes sda as opposed hda. This requires manual setting of the kernel options in /etc/grub/menu.lst to select the appropriate root device, but I have not figured a clean way what to do with /etc/fstab ! Here's what I have there at 2.4: /dev/hda1 / ext3defaults,errors=remount-ro 0 1 /dev/hda4 /LOCAL ext3defaults0 2 /dev/hda5 /boot ext3defaults0 2 /dev/hda9 /home ext3defaults0 2 /dev/hda8 /tmpext3defaults0 2 /dev/hda6 /usrext3defaults0 2 /dev/hda7 /varext3defaults0 2 /dev/hda2 noneswapsw 0 0 /dev/fd0/floppy auto rw,user,noauto,umask=077,shortname=winnt,showexec=no0 0 /dev/cdrom /cdrom autoro,user,noauto 0 0 proc/proc procdefaults0 0 /dev/sda1 /memory_cardvfat rw,user,noauto,umask=077,shortname=winnt,showexec=no 0 0 /dev/sda2 /keycardext2rw,user,noauto,nosuid 0 0 /dev/sdb1 /olymp vfat rw,user,noauto,noexec,umask=022,shortname=winnt,showexec=no 0 0 3) When I solve that, I will have to solve another issue which is the CD-R. Currently, under 2.4, I am using scsi emulation for both the IDE CD-ROM and the CD-RW device: /proc/cmdline: ... hdc=ide-scsi hdd=ide-scsi and in /etc/modules: sg ide-scsi Also I have the corresponding links established from /dev/cdrom and /dev/cdrw As far as I understand, I have to remove all this under 2.6, so there's quite a bit of work left. Any link on setting up the 2 kernels in parallel on the same machines are appreciated (this is a family desktop machine and I am unsure I am willing to make the wife and the kids suffer a kernel I haven't tried out here myself yet). Kind regards, v.
