Bug#501007: 2.6.26-7 and keyboard
Package: linux-2.6 Version: 2.6.26-7 Severity: normal After 2.6.26-5 on tty starting appear; padlock: VIA PadLock Hash Engine not detected. padlock: VIA PadLock not detected. I'm using ATEN View switchs models; CS-1744 and CS-9138. This problem only started after 2.6.26-6 and 2.6.26-7 upgrade. Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#498021: linux-image-2.6.26-1-686: task blocked after connecting the SDHC memory card
/0x32a [scsi_mod] [ 544.390150] [c02b758d] wait_for_common+0xaf/0x10f [ 544.390172] [c011b61d] default_wake_function+0x0/0x8 [ 544.390217] [c01d49d0] blk_execute_rq+0x83/0x96 [ 544.390231] [c01d49e3] blk_end_sync_rq+0x0/0x25 [ 544.390245] [c0158911] mempool_alloc+0x1c/0xba [ 544.390264] [c01dba6f] cfq_set_request+0x0/0x269 [ 544.390285] [c01cfe40] elv_set_request+0x14/0x22 [ 544.390305] [c01d22e6] get_request+0x1e5/0x2c7 [ 544.390359] [c01d2874] get_request_wait+0x106/0x117 [ 544.390424] [f889cfc4] scsi_execute+0xc5/0x103 [scsi_mod] [ 544.390488] [f889d086] scsi_execute_req+0x84/0xa1 [scsi_mod] [ 544.390580] [f8effd7b] sd_revalidate_disk+0x175/0xd06 [sd_mod] [ 544.390713] [c0193d6e] check_disk_change+0x39/0x57 [ 544.390733] [f8f01838] sd_open+0xce/0x152 [sd_mod] [ 544.390767] [c019435c] do_open+0xb6/0x28f [ 544.391869] [c01946b0] blkdev_open+0x0/0x4d [ 544.391878] [c01946d5] blkdev_open+0x25/0x4d [ 544.391900] [c0172b77] __dentry_open+0x10d/0x1fc [ 544.391938] [c0172c82] nameidata_to_filp+0x1c/0x2c [ 544.391964] [c017d382] do_filp_open+0x34f/0x684 [ 544.392069] [c01dc96a] _atomic_dec_and_lock+0x2a/0x44 [ 544.392088] [c0182376] dput+0x25/0xbb [ 544.392154] [c0172994] do_sys_open+0x40/0xb0 [ 544.392192] [c0172a48] sys_open+0x1e/0x23 [ 544.392218] [c0103853] sysenter_past_esp+0x78/0xb1 [ 544.392272] [c02b] serial_pnp_probe+0xde/0x16b [ 544.392319] === [ 544.392325] INFO: task vol_id:4518 blocked for more than 120 seconds. [ 544.392329] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 544.392334] vol_idD f7713cac 0 4518 1 [ 544.392341]f5648ea0 0082 f889c9e7 f7713cac f6da0c00 f564902c c1ffbfa0 0001 [ 544.392356] 5e85 f8f0103c f564902c 00ff [ 544.392371]7fff 7fff f569bd14 0002 c02b7e69 0086 c0129a63 [ 544.392386] Call Trace: [ 544.392415] [f889c9e7] scsi_get_cmd_from_req+0x1b/0x41 [scsi_mod] [ 544.392505] [f8f0103c] sd_prep_fn+0x52/0x780 [sd_mod] [ 544.392589] [c02b7e69] schedule_timeout+0x13/0x86 [ 544.392608] [c0129a63] __mod_timer+0x99/0xa3 [ 544.392690] [f889dbb0] scsi_request_fn+0x2e6/0x32a [scsi_mod] [ 544.392729] [c02b758d] wait_for_common+0xaf/0x10f [ 544.392752] [c011b61d] default_wake_function+0x0/0x8 [ 544.392789] [c01d49d0] blk_execute_rq+0x83/0x96 [ 544.392802] [c01d49e3] blk_end_sync_rq+0x0/0x25 [ 544.392815] [c0158911] mempool_alloc+0x1c/0xba [ 544.392834] [c01dba6f] cfq_set_request+0x0/0x269 [ 544.392856] [c01cfe40] elv_set_request+0x14/0x22 [ 544.392874] [c01d22e6] get_request+0x1e5/0x2c7 [ 544.392925] [c01d2874] get_request_wait+0x106/0x117 [ 544.392992] [f889cfc4] scsi_execute+0xc5/0x103 [scsi_mod] [ 544.393051] [f889d086] scsi_execute_req+0x84/0xa1 [scsi_mod] [ 544.393136] [f8effd7b] sd_revalidate_disk+0x175/0xd06 [sd_mod] [ 544.393264] [c0193d6e] check_disk_change+0x39/0x57 [ 544.393284] [f8f01838] sd_open+0xce/0x152 [sd_mod] [ 544.393318] [c019435c] do_open+0xb6/0x28f [ 544.393365] [c01946b0] blkdev_open+0x0/0x4d [ 544.393373] [c01946d5] blkdev_open+0x25/0x4d [ 544.393396] [c0172b77] __dentry_open+0x10d/0x1fc [ 544.393433] [c0172c82] nameidata_to_filp+0x1c/0x2c [ 544.393460] [c017d382] do_filp_open+0x34f/0x684 [ 544.393565] [c01dc96a] _atomic_dec_and_lock+0x2a/0x44 [ 544.393584] [c0182376] dput+0x25/0xbb [ 544.393650] [c0172994] do_sys_open+0x40/0xb0 [ 544.393687] [c0172a48] sys_open+0x1e/0x23 [ 544.393714] [c0103853] sysenter_past_esp+0x78/0xb1 [ 544.393768] [c02b] serial_pnp_probe+0xde/0x16b [ 544.393815] === [ 563.703961] usb 5-5: reset high speed USB device using ehci_hcd and address 3 [ 594.057498] usb 5-5: reset high speed USB device using ehci_hcd and address 3 [ 626.104211] usb 5-5: reset high speed USB device using ehci_hcd and address 3 -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-3) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Aug 20 12:56:41 UTC 2008 ** Command line: root=/dev/hda1 ro ** Not tainted ** Kernel log: [ 1802.820595] === [ 1821.505370] usb 5-5: reset high speed USB device using ehci_hcd and address 3 [ 1851.805364] usb 5-5: reset high speed USB device using ehci_hcd and address 3 [ 1882.131627] usb 5-5: reset high speed USB device using ehci_hcd and address 3 [ 1912.998987] usb 5-5: reset high speed USB device using ehci_hcd and address 3 [ 1943.299712] usb 5-5: reset high speed USB device using ehci_hcd and address 3 [ 1973.600824] usb 5-5: reset high speed USB device using ehci_hcd and address 3 [ 1983.204856] INFO: task vol_id:4763 blocked for more than 120 seconds. [ 1983.204864] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 1983.204868] vol_idD f5b2d68c 0 4763 1 [ 1983.204874
Bug#482100: linux-image-2.6.25-3-686-bigmem : Complete system freeze
maximilian attems wrote : okay thanks for retesting. please checkout 2.6.26-rc8 from debian linux images, see apt trunk lines http://wiki.debian.org/DebianKernel if those are also freezing please send in the working config for 2.6.26-rc8. kind regards It's a bit too early to tell, but seems like 2.6.26-rc8-amd64 from Debian is working as fine as is the vanilla kernel. It's currently running on two clones of the problematic system and no freeze so far. One is stock kernel just installed from trunk repository, running in console mode without x started. The other one has been rebuilt (but with strictly the stock 2.6.26-rc8-amd64 configuration file) from trunk linux-source-2.6.26-rc8 with gcc 4.3 (Lenny default), and is running with x and nvidia's latest beta driver, doing equally good. Looks like the problem is strictly a 2.6.25 issue. I would really like to understand what's going wrong in the equation Debian Lenny - my hardware - 2.6.25 kernel ... I tried once again the 2.6.25 , using the working 2.6.26 config to build it, but only to freeze the system after a mere 30 minutes. The cpu seems to be idling even though there is activity on the box, and never coming up again. Nothing works, keyboard (ps2) and magic keys are useless, just a message telling cpu stuck for xx seconds for a while, then even this freezes and I have to hard-reboot. Exact same system and hardware, I really can't settle for a configuration problem or some weird cpufreq governor ill behavior since it's working perfectly with 2.6.24 and 2.6.26... and even the vanilla 2.6.25 is crashing the same way. Anyway, I can live with not knowing as long as my system works again and I am able to upgrade the kernel when needed. If you need anything else, or if there's a way I can rebuild a 2.6.25 with debug on to help gathering information I can do it, but I doubt it would be of any interest since we've already moved on to 2.6.26 . Of course if 2.6.25 is to be the next Stable default kernel you may come across weird problems like mine again... Best regards, Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457044:
Jonas Smedegaard a écrit : If you dislike the confusion of the many choices (and us package maintainers disagreeing of what's best), then use the same as gets installed by default using a recent debian-installer. On IBM-compatible x86 systems that means the bootloader grub, the ramdisk-generator initramfs-tools, a kernel compiled and packaged by the Debian kernel team, and devices handled by udev. My problem is that my box is running since March 2002 and the defaults weren't the same at this prehistorical time. It has been apt-get'ed daily and rebooted many times following the successive kernels (2.2, 2.4, 2.6) an releases (Potato, Woody, Sarge, Etch and now Lenny) , by the way this means that the debian upgrade system is working very well to get through all those evolutions ;) As there was no hardware changes since the start, this means that the reboot problem I recently met is strongly linked to the 2.6 kernel or at least to its install scripts which might have forgotten something in the upgrade process when Maximilian says most probably a missing lilo run. I answer if lilo hadn't run it would be the upgrade script fault. But as written in comment #10 lilo had run : You already have a LILO configuration in /etc/lilo.conf Running boot loader as requested Testing lilo.conf ... Testing successful. Installing the partition boot sector... Running /sbin/lilo ... Installation successful. using lilo is masochistic, grub is the default since some time. And as I just explained my box was running long before grub became the default. And I have enough problems for now without testing another boot manager -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457044: (pas de sujet)
I've found a work around :now I never reboot any distant machine, I never follow the stressing instructions provided : You are attempting to install a kernel version that is the same as the version you are currently running (version 2.6.18-4-686). The modules list is quite likely to have been changed, and the modules dependency file /lib/modules/2.6.18-4-686/modules.dep needs to be re-built. It can not be built correctly right now, since the module list for the running kernel are likely to be different from the kernel installed. I am creating a new modules.dep file, but that may not be correct. It shall be regenerated correctly at next reboot. I repeat: you have to reboot in order for the modules file to be created correctly. Until you reboot, it may be impossible to load some modules. Reboot as soon as this install is finished (Do not reboot right now, since you may not be able to boot back up until installation is over, but boot immediately after). I can not stress that too much. You need to reboot soon. There are so many bugs indicating boot problems for so much different reasons (394608,334831,327335,422217,462221...) that I can't take this risk on distant production servers until I get a solution to really double check the boot process before running it for true. I was unable to choose between yaird and kexec as the informations provided were contradictory... thanks for all anyway -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457044: (pas de sujet)
Jonas Smedegaard a écrit : Those tools are different approaches indeed. How do you find them contradictory? Please elaborate - I sincerely want to understand better. Sorry for being confusing. Saying contradictory I wasn't talking about the tools themselves, but about the comments #43, #48, #53 and #58. As I am myself a bit confused about how to do to ensure a correct reboot of my boxes, this friendly battle between developpers didn't help me very much. Anyway both of those tools seems very useful But my problem is still when a reboot is needed for distant machines, now I'm too afraid about that to take the risk. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#435983: mount: fails to detect LABEL=foo filesystems
Marco d'Itri wrote: On Mar 14, Holger Levsen [EMAIL PROTECTED] wrote: also sprach Marco d'Itri [EMAIL PROTECTED] [2007.09.10.1409 +0200]: I will do it ASAP. Please do not do this by yourself because the udev rules files need to be renamed first (or else I would need to add conflicts and you would need to move the file). Marco, any news on this? Yes, I still hold the same opinion and still plan to work on udev ASAP. Do not add these rules without my approval. This bug is causing trouble for more and more people. Please, Marco, if you do not have the time to fix it by adding these rules, at least let us know what are the changes you though to at least let anyone else work on them, even if you are the one approving them. Ahora también puedes acceder a tu correo Terra desde el móvil. Infórmate pinchando aquí. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482100: linux-image-2.6.25-3-686-bigmem : Complete system freeze
Package: linux-image-2.6.25-3-686-bigmem Version: 2.6.25-3-686-bigmem Severity: important I've tried building 2.6.25 Sid kernel from sources with my working .config, resulting in complete system freeze a few minutes or seconds after starting the new kernel. Same result with different config options. So, to rule out misconfiguration I installed the 2.6.25-3-686-bigmem from Sid, it leads to the same result : complete system freeze a few minutes after boot. To rule out alien module responsibility i let the computer run in console mode, no x-server running, no external module loaded (I usually use nvidia's blob and uvcvideo from svn). I got the same symptoms : computer totally non-responsive, keyboard frozen, no input possible. The only output I got before the freeze was : === BUG: soft lockup - cpu#0 stuck for 61s! [cc:6671] Pid:6671, comm: cc Not tainted (2.6.25-1-686-bigmem #1) EIP: 0060:[c010f82d] EFLAGS: 0202 CPU: 0 EIP is at native_flush_tlb_others+0x73/0x94 EAX: 0202 EBX: f6824900 ECX: b300 EDX: 08fd ESI: EDI: f6df2804 EBP: f64ea000 ESP: f64ebf40 DS: 007b ES: 007b FS: 00g8 GS: SS: 0068 CR0: 8005003b CR2: 400cfeb4 CR3: 0035e000 CR4: 06f0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 [c010f7b5] ? flush_tlb_mm+0x5b/0x60 [c0167657] ? exit_mmap+0x98/0xce [c0120d1e] ? mmput+0x20/0x75 [c01256c5] ? do_exit+0x1e5/0x5c9 [c0125b14] ? do_group_exit+0x6b/0x82 [c01047e4] ? sysenter_past_esp+0x6d/0xa5 === I could not find anything else outside of a few messages regarding lost interrupts, randomly appearing from boot time to the freeze. The same machine has been running Debian Lenny happily ever before, and still is on custom compiled 2.6.24 kernel. I've just tried compiling a vanilla kernel from kernel.org, with the same result, so it's most probably version related and not Debian only related, I'll file a report there too. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-speedy2 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.25-3-686-bigmem depends on: ii debconf [debconf-2.0] 1.5.21 Debian configuration management sy ii initramfs-tools [linux-initra 0.92a tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.25-3-686-bigmem recommends: ii libc6-i6862.7-10 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.25-3-686-bigmem/preinst/overwriting-modules-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/prerm/removing-running-kernel-2.6.25-3-686-bigmem: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.25-3-686-bigmem/postinst/depmod-error-2.6.25-3-686-bigmem: false linux-image-2.6.25-3-686-bigmem/postinst/old-dir-initrd-link-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/preinst/abort-overwrite-2.6.25-3-686-bigmem: linux-image-2.6.25-3-686-bigmem/preinst/lilo-has-ramdisk: linux-image-2.6.25-3-686-bigmem/preinst/bootloader-initrd-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/preinst/elilo-initrd-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/preinst/initrd-2.6.25-3-686-bigmem: linux-image-2.6.25-3-686-bigmem/postinst/old-initrd-link-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/postinst/bootloader-test-error-2.6.25-3-686-bigmem: linux-image-2.6.25-3-686-bigmem/postinst/create-kimage-link-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/postinst/old-system-map-link-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/prerm/would-invalidate-boot-loader-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/postinst/kimage-is-a-directory: linux-image-2.6.25-3-686-bigmem/preinst/lilo-initrd-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/postinst/depmod-error-initrd-2.6.25-3-686-bigmem: false linux-image-2.6.25-3-686-bigmem/preinst/abort-install-2.6.25-3-686-bigmem: linux-image-2.6.25-3-686-bigmem/preinst/failed-to-move-modules-2.6.25-3-686-bigmem: linux-image-2.6.25-3-686-bigmem/postinst/bootloader-error-2.6.25-3-686-bigmem: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libata PATA transition
Marco d'Itri wrote: On Mar 14, Holger Levsen [EMAIL PROTECTED] wrote: also sprach Marco d'Itri [EMAIL PROTECTED] [2007.09.10.1409 +0200]: I will do it ASAP. Please do not do this by yourself because the udev rules files need to be renamed first (or else I would need to add conflicts and you would need to move the file). Marco, any news on this? Yes, I still hold the same opinion and still plan to work on udev ASAP. Do not add these rules without my approval. Why do not just copy the rules from Ubuntu? Ahora también puedes acceder a tu correo Terra desde el móvil. Infórmate pinchando aquí.
Bug#457044: Can I upgrade without risk of hang up ?
Hello, As there is a new upgrade on package linux-image-2.6 I'm wondering if I can apply this upgrade without risk of hanging one more time my production server ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457044: test booting ability without actually booting
Hello Is there a way to test or check the boot process without actually booting ? Because rebooting a remotely hosted server without any garanty that it will be able to start, is a bit like russian roulet... one time it reboots one time it doesn't and if it doesn't nothing else can be done except starting the box with a floppy or a live cd to try to find the problem's cause which is rather difficult on a distant machine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457044: Same problem with the new security update to linux-image-2.6.22-3-686
Hello, this morning, I had exactly the same problem while installing linux-image-2.6.22-3-686 (2.6.22-6.lenny1 Debian-Security:None/testing) The box didn't reboot. The last time it happened, this is how our distant hostmaster managed to correcte the problem : The technician had to boot the server using a live CD Linux. Then he made a dpkg-reconfigures on the kernel package, this made it possible to rebuild the initrd and to repair Lilo. Reading the apt-get session I had before the reboot, I think the problem could be here : ? The kernel version running is the same as the one being installed ? ? ? ? You are attempting to install a kernel version that is the same as the version you are currently running (version 2.6.22-3-686). The modules list is quite ? ? likely to have been changed, and the modules dependency file /lib/modules/2.6.22-3-686/modules.dep needs to be re-built. It can not be built correctly right? ? now, since the module list for the running kernel are likely to be different from the kernel installed. I am creating a new modules.dep file, but that may ? ? not be correct. It shall be regenerated correctly at next reboot. ? ? ? ? I repeat: you have to reboot in order for the modules file to be created correctly. Until you reboot, it may be impossible to load some modules. Reboot as ? ? soon as this install is finished (Do not reboot right now, since you may not be able to boot back up until installation is over, but boot immediately ? ? after). I can not stress that too much. You need to reboot And here : Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. Not updating initrd symbolic links since we are being updated/reinstalled (2.6.22-6 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.22-6 was configured last, according to dpkg) It seems that in the case of the installation of a kernel with the same number, dpkg doesn't verify that initrd symbolic links really exists just because it consider that they should be correct in the case of an update. But if for some reason those links were broken they are not recreated and lilo isn't updated -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449526: linux-image: dpkg refuses to activate the last kernel version
Package: linux-image Version: impossible to activate the last version Severity: grave Justification: renders package unusable Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core) Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.22-2-686 depends on: ii initramfs-tools [linux-initr 0.90a tools for generating an initramfs ii module-init-tools3.3-pre11-4 tools for managing Linux kernel mo Versions of packages linux-image-2.6.22-2-686 recommends: pn libc6-i686none (no description available) -- debconf information: linux-image-2.6.22-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.22-2-686/prerm/would-invalidate-boot-loader-2.6.22-2-686: true linux-image-2.6.22-2-686/preinst/elilo-initrd-2.6.22-2-686: true linux-image-2.6.22-2-686/preinst/abort-overwrite-2.6.22-2-686: linux-image-2.6.22-2-686/preinst/lilo-initrd-2.6.22-2-686: true linux-image-2.6.22-2-686/postinst/depmod-error-initrd-2.6.22-2-686: false linux-image-2.6.22-2-686/preinst/overwriting-modules-2.6.22-2-686: true linux-image-2.6.22-2-686/preinst/failed-to-move-modules-2.6.22-2-686: * linux-image-2.6.22-2-686/preinst/bootloader-initrd-2.6.22-2-686: false linux-image-2.6.22-2-686/postinst/create-kimage-link-2.6.22-2-686: true linux-image-2.6.22-2-686/postinst/bootloader-error-2.6.22-2-686: shared/kernel-image/really-run-bootloader: true linux-image-2.6.22-2-686/postinst/kimage-is-a-directory: linux-image-2.6.22-2-686/postinst/old-dir-initrd-link-2.6.22-2-686: true linux-image-2.6.22-2-686/prerm/removing-running-kernel-2.6.22-2-686: true linux-image-2.6.22-2-686/preinst/initrd-2.6.22-2-686: linux-image-2.6.22-2-686/postinst/depmod-error-2.6.22-2-686: false linux-image-2.6.22-2-686/preinst/already-running-this-2.6.22-2-686: linux-image-2.6.22-2-686/postinst/old-initrd-link-2.6.22-2-686: true linux-image-2.6.22-2-686/postinst/bootloader-test-error-2.6.22-2-686 I've got four versions of linux-image installed on my box but I can't get the last one to be used. here are the different version installed : linux-image-2.6-686 2.6.22+10 linux-image-2.6.18-4-686 2.6.18.dfsg.1-12 linux-image-2.6.21-2-686 2.6.21-6 linux-image-2.6.22-2-686 2.6.22-4 the active one, (refering to the links in / path) is 2.6.18-4-686 and there's no way to force the use of 2.6.22, except modifying by hand the links when trying dpkg-reconfigure linux-image-2.6.22-2-686, I always get the messages : Not updating initrd symbolic links since we are being updated/reinstalled (2.6.22-4 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.22-4 was configured last, according to dpkg and the --force option doesn't force the configuration. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core) Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#362056: Esteemed Fellow,Please Get Back To Me
Esteemed Fellow, My name is Prince Udo Ogali the newly appointed chairman of the local and Foreign debt reconciliation panel (F.G.N) I want to seek your candid collaboration in handling a business venture that I feel it would be of mutual benefit to you and I. May I ask your permission to present you as a contractor to the federal government for this fund under my control custody at the moment. I am offering you this opportunity, believing that you will be capable of keeping the fund in safe custody when it hits your bank account, and you Will hand over my share of 60% on demand and keep 40% to yourself . I will love to invest my share in your Country.As such , I will also require your assistance on that note. On receipt of your response in affirmation of your willingness to work with me, I will send to you full details and more information about myself and the said funds for your better understanding. As I am yet to get your consent on this issue, I prefer not to divulge my full identity so as not to risk being publicized which consequence is detrimental.So if you are willing to make this deal with me, contact me with this my secured email: [EMAIL PROTECTED] Yours Truly, PRINCE UDO OGALI
Re: serial driver/irda conflict resolution?
Mikko Rapeli wrote: Etch kernels at least have serial 8250 built in, but it conflicts with the irda chip on a Thinkpad T20. With modular driver I can override this by adding the irda driver nsc-ircc to /etc/initramfs-tools/modules, but how do I tell the distro kernel not to give io 0x3f7, irq 4 and dma 3 to 8250? You may want to take a look at this bugs: http://bugzilla.kernel.org/show_bug.cgi?id=3575 http://bugzilla.kernel.org/show_bug.cgi?id=8991 There are people working to fix this problem for a long time. I load nsc-ircc irda with this script: setserial /dev/ttyS1 uart none modprobe nsc-ircc irq=3 io=0x02f8 dma=3 dongle_id=0x09 irattach irda0 -s MAKEDEV ircomm chmod 666 /dev/ircomm0 Ahora también puedes acceder a tu correo Terra desde el móvil. Infórmate pinchando aquí.
Bug#447337: sr_ioctl fail to send status TRAY_OPEN
Package: linux-source-2.6.22
Version: 2.6.22-4~bpo40+1
Severity: serious
Tags: patch
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.22-2-686
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2)
Versions of packages linux-source-2.6.22 depends on:
ii binutils 2.17-3 The GNU assembler, linker and bina
ii bzip2 1.0.3-6high-quality block-sorting file co
Versions of packages linux-source-2.6.22 recommends:
ii gcc4:4.1.1-15The GNU C compiler
ii libc6-dev [libc-dev] 2.3.6.ds1-13etch2 GNU C Library: Development Librari
ii make 3.81-2The GNU version of the make util
-- no debconf information
From David Martin
Subject [PATCH] SCSI not showing tray status correctly
Date Mon, 27 Dec 2004 06:26:32 +0100
Digg This When trying to get the drive status via ioctl CDROM_DRIVE_STATUS,
with no disk
it gives CDS_TRAY_OPEN even if the tray is closed.
ioctl works as expected with ide-cd driver. Here is the patch to get the same
behaviour on SCSI drives for kernel 2.6.10. 2.4 branch have same problem.
--- linux-2.6.10-orig/drivers/scsi/sr_ioctl.c2004-12-27
04:47:22.0 +0100
+++ linux-2.6.10/drivers/scsi/sr_ioctl.c 2004-12-27 05:54:08.0
+0100
@@ -216,14 +216,20 @@
int sr_drive_status(struct cdrom_device_info *cdi, int slot)
{
+ struct media_event_desc med;
+
if (CDSL_CURRENT != slot) {
/* we have no changer support */
return -EINVAL;
}
+
if (0 == test_unit_ready(cdi-handle))
return CDS_DISC_OK;
- return CDS_TRAY_OPEN;
+ if (!cdrom_get_media_event(cdi, med) med.door_open)
+ return CDS_TRAY_OPEN;
+
+ return CDS_NO_DISC;
}
int sr_disk_status(struct cdrom_device_info *cdi)
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445688: Info received (Bug cause identified)
Sorry, that information doesn't help since it doesn't fix anything when I fix this in /usr/share/initramfs-tools/scripts. The initramfs from yaird works, but can't load the usb driver. Pleas Reply. myhosting.com - Premium Microsoft® Windows® and Linux web and application hosting - http://link.myhosting.com/myhosting
Bug#406581: New message
Dear Value Partners Please find the our new RAID_PM Hardware RAID Port Multiplier bridge up to FIVE SATA ports - SiI-4723 Feature: - Hot Plug support; Compatible with NCQ drives - eSATA signal level support (1m and 2m PHY (compliant) - Supports PM aware hosts and non-PM aware - Less than 1% Host CPU loading during rebuild - Fast rebuild of 100GB/hour - Easy configuration using GUI applet - Drive Performance Aggregation (RAID 0) - Hardware RAID 0, 1, 10 with hot spare, Mirrored and spanning with spare, Spanning and JBOD http://www.datoptic.com/cgi-bin/web.cgi?search=yesexact_match=ondetail=trueproduct=RAID_PM Availability: Now shipping Please feel free to contact me Best Regards Sam Q 714 558 1808 www.datoptic.com = CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material of DATOptic for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient please contact the sender and delete all copies. Port Multiplier with hardware RAID subj -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#429625: linux-source-2.6.18 build fails on hppa - missing patch?
Package: linux-source-2.6.18 Version: 2.6.18.dfs Kernel source does not compile on parisc (HP 712/60). I am running kernel 2.6.8 libc version 2.3.6.ds1-13 gcc version 4:4.1.1-15 Should there not be a hppa/parisc-specific patch to apply to the standard debian kernel source package? No such patch appears to be available in etch. To reproduce error, unpack sources, copy .config from pre-packaged kernel image, and make-kpkg boris:/share/linux-source-2.6.18# cp /boot/config-2.6.18-4-parisc . config boris:/share/linux-source-2.6.18# make-kpkg --initrd linux-image ... CC arch/parisc/mm/init.o arch/parisc/mm/init.c:34: error: conflicting types for '_text' include/asm-generic/sections.h:6: error: previous declaration of '_text' was here arch/parisc/mm/init.c:36: error: conflicting types for '_end' include/asm-generic/sections.h:13: error: previous declaration of '_end' was here arch/parisc/mm/init.c:37: error: conflicting types for '__init_begin' include/asm-generic/sections.h:9: error: previous declaration of '__init_begin' was here arch/parisc/mm/init.c:37: error: conflicting types for '__init_end' include/asm-generic/sections.h:9: error: previous declaration of '__init_end' was here make[2]: *** [arch/parisc/mm/init.o] Error 1 make[1]: *** [arch/parisc/mm] Error 2 make[1]: Leaving directory `/share/linux-source-2.6.18' make: *** [debian/stamp-build-kernel] Error 2 _ Tiscali.Supermail: la tua email con 2GB di Spazio, Antivirus e Antispam http://vas.tiscali.it/supermail/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421870: opcode unknown on ide hard disk
I send files:
dmesg_2.6.18 complete dmesg with kernel 2.6.18
dmesg_2.6.18_nodma complete dmesg with kernel 2.6.18 and option
ide=nodma
With this option is removed the error
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=2122765,
sector=2122764
ide: failed opcode was: unknown
and only is show the error
hdc: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
Error }
hdc: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=2122765,
sector=2122765
ide: failed opcode was: unknown
dmesg_2.6.8 complete dmesg with kernel 2.6.8
Note: This kernel have been installed on debian etch and in boot show
the error
udev need the kernel 2.6.15 that not is show in dmesg.
The las error Losing some ticks... checking if CPU frequency
changed.
in Sarge was not show
The posibility of hardware fail because the diference between CHS y
LBA it not posible because
I have other hard disk and are diferents and not show any error.
The hard disk in BIOS is configured like LBA. If I change the config
also is show the error.
I find this error searching in google but it not solve. There is some
that think that is produced by
one thing name stroke that change from a kernel version, but this
option have been removed of the
kernel.
The hard disk work fine after boot and in sarge not showed any error
because I think that the error
is in the kernel.
The pristine kernel don't work fine (time and keyboard run vey fast)
whith patches this error is removed
for this reason I think that there is some change more in the kernel
than affect to my system. Perhapts
timing problems whit dma probe (for first error)
If I have to response to the email [EMAIL PROTECTED] please point
me.
Mensaje original
De: [EMAIL PROTECTED]
Recibido: 02/05/2007 10:48
Para: [EMAIL PROTECTED], [EMAIL PROTECTED]
Asunto: Re: Bug#421870: opcode unknown on ide hard disk
On Wed, May 02, 2007 at 09:20:09AM +0200, [EMAIL PROTECTED] wrote:
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=2122765,
sector=2122764
ide: failed opcode was: unknown
So it tries to access sector 2122765 which is denied with an error.
This error only is show in boot time with kernel 2.6.18 and later
and in the version 2.6.8
this error is not show.
Can you please provide the dmesg output of the working one?
hdc: max request size: 128KiB
hdc: 2122780 sectors (1086 MB) w/128KiB Cache, CHS=2105/16/63, DMA
hdc: hdc1 hdc2
The device describes itself as 2122780 sectors large.
CHS current addressable sectors:2121840
LBAuser addressable sectors:2122780
Again.
This looks like an hardware error. The failing sector is within the
annonced LBA adressable space but outside of the CHS adressable one.
Bastian
--
... The prejudices people feel about each other disappear when they
get
to know each other.
-- Kirk, Elaan of Troyius, stardate 4372.5
Ahora tambi�n puedes acceder a tu correo Terra desde el m�vil.
Inf�rmate pinchando aqu�.
Ahora también puedes acceder a tu correo Terra desde el móvil.
Infórmate pinchando aquí.
dmesg_2.6.8
Description: Binary data
dmesg_2.6.18
Description: Binary data
dmesg_2.6.18_nodma
Description: Binary data
Bug#421870: opcode unknown on ide hard disk
Package: linux-source
Version: 2.6.18
One of my disk when I boot the machine show the error (below one more complete
dmesg after boot and
hdparam -I of this
disk)
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=2122765, sector=2122764
ide: failed opcode was: unknown
hdd: DMA disabled
ide1: reset: success
hdc: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=2122765,
sector=2122765
ide: failed opcode was: unknown
Buffer I/O error on device hdc, logical block 530691
This error only is show in boot time with kernel 2.6.18 and later and in the
version 2.6.8
this error is not show.
In pristine kernel 2.6.18 and not in 2.6.8 the time clock and keyboard run very
fast this is solved
by the patches of debian etch (I think this would be realationated)
I probe the kernel param hdc=noprobe and hdc=head,cyl,sector and the message
error are not show but
after of boot I can not access to the hard disk.
I probe diferent patches and diferent compilation options but error has not
been solved
My system is debian etch and the kernel of installation have the same probem
and during the installation
system blocked several times by this probem having reboot the system.
dmesg
-
Linux version 2.6.18 (Version: custom.1.0) ([EMAIL PROTECTED]) (gcc version
4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 Thu Apr 26 21:05:20 CEST 2007
ACPI: RSDP (v000 ASUS ) @ 0x000f81e0
ACPI: RSDT (v001 ASUS P5A-B0x42302e31 MSFT 0x31313031) @ 0x17ffc000
ACPI: FADT (v001 ASUS P5A-B0x42302e31 MSFT 0x31313031) @ 0x17ffc080
ACPI: BOOT (v001 ASUS P5A-B0x42302e31 MSFT 0x31313031) @ 0x17ffc040
ACPI: DSDT (v001 ASUS P5A-B0x1000 MSFT 0x0101) @ 0x
ACPI: PM-Timer IO Port: 0xec08
Detected 501.111 MHz processor.
Kernel command line: root=/dev/hda2 ro
Calibrating delay using timer specific routine.. 1003.07 BogoMIPS (lpj=2006158)
CPU: AMD-K6(tm) 3D processor stepping 0c
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ALI15X3: IDE controller at PCI slot :00:0f.0
ACPI: Unable to derive IRQ for device :00:0f.0
ACPI: PCI Interrupt :00:0f.0[A]: no GSI
ALI15X3: chipset revision 193
ALI15X3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: ST320423A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: Maxtor 71084 AP, ATA DISK drive
hdd: IDE/ATAPI CD-ROM 44X, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 40011300 sectors (20485 MB) w/512KiB Cache, CHS=39693/16/63, UDMA(33)
hda: cache flushes not supported
hda: hda1 hda2
hdc: max request size: 128KiB
hdc: 2122780 sectors (1086 MB) w/128KiB Cache, CHS=2105/16/63, DMA
hdc: hdc1 hdc2
PM-Timer running at invalid rate: 199% of normal - aborting.
Time: tsc clocksource has been installed.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=2122765, sector=2122764
ide: failed opcode was: unknown
Real Time Clock Driver v1.12ac
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=2122765, sector=2122764
ide: failed opcode was: unknown
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=2122765, sector=2122764
ide: failed opcode was: unknown
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=2122765, sector=2122764
ide: failed opcode was: unknown
hdc: DMA disabled
hdd: DMA disabled
ide1: reset: success
hdc: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=2122765,
sector=2122765
ide: failed opcode was: unknown
hdc: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=2122765,
sector=2122765
ide: failed opcode was: unknown
hdc: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=2122765,
sector=2122765
ide
Bug#417172: linux-image-2.6.18-4-686: failure to mount root fs if usb drive plugged in (-486 not affected, tho)
Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-12 Severity: important If a usb drive is plugged in and operational during boot of the -686 kernel I get a failure to mount root filesystem. The usb drive becomes /dev/sda and the 3ware raid becomes /dev/sdb. Oddly enough, the -486 kernel does not have this problem. The 3ware module being used is 3w_ and the card is a 3ware 8006-2LP two channel sata. I tried configuring initramfs.conf to use MODULES=dep, then purged and reinstalled linux-image-2.6.18-4.686, but the behavior is still the same. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-4-686 depends on: ii coreutils 5.97-5.3 The GNU core utilities ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii initramfs-tools [linux-initra 0.85f tools for generating an initramfs ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-4-686 recommends: ii libc6-i686 2.3.6.ds1-13 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.18-4-686/preinst/failed-to-move-modules-2.6.18-4-686: linux-image-2.6.18-4-686/preinst/lilo-initrd-2.6.18-4-686: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-4-686/preinst/elilo-initrd-2.6.18-4-686: true linux-image-2.6.18-4-686/preinst/overwriting-modules-2.6.18-4-686: true linux-image-2.6.18-4-686/prerm/removing-running-kernel-2.6.18-4-686: true linux-image-2.6.18-4-686/prerm/would-invalidate-boot-loader-2.6.18-4-686: true linux-image-2.6.18-4-686/postinst/bootloader-test-error-2.6.18-4-686: linux-image-2.6.18-4-686/preinst/abort-overwrite-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/old-system-map-link-2.6.18-4-686: true linux-image-2.6.18-4-686/postinst/depmod-error-2.6.18-4-686: false linux-image-2.6.18-4-686/preinst/abort-install-2.6.18-4-686: linux-image-2.6.18-4-686/preinst/lilo-has-ramdisk: linux-image-2.6.18-4-686/postinst/bootloader-error-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/depmod-error-initrd-2.6.18-4-686: false linux-image-2.6.18-4-686/postinst/old-initrd-link-2.6.18-4-686: true linux-image-2.6.18-4-686/preinst/bootloader-initrd-2.6.18-4-686: true linux-image-2.6.18-4-686/preinst/already-running-this-2.6.18-4-686: linux-image-2.6.18-4-686/preinst/initrd-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/create-kimage-link-2.6.18-4-686: true linux-image-2.6.18-4-686/postinst/old-dir-initrd-link-2.6.18-4-686: true linux-image-2.6.18-4-686/postinst/kimage-is-a-directory: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410939: linux-image-2.6.18-3-686: capabilities as kernel module
Package: linux-image-2.6.18-3-686 Version: 2.6.18-7 Severity: wishlist I've installed clamav and I've wanted to enable dazuko module (this module is needed to scan your every file you open or use). I've downloaded the debian package from dazuko site and i've given the following input m-a a-i dazuko But i've got this message. error: capabilities are built-in to the kernel; you will need to recompile a kernel with capabilities as a kernel module Unless it create stability or security problems, for the next release can you compile capabilities as module? Thanks -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.18-3-686 depends on: ii coreutils 5.97-5 The GNU core utilities ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii initramfs-tools [linux-initra 0.85e tools for generating an initramfs ii module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-3-686 recommends: ii libc6-i686 2.3.6.ds1-10 GNU C Library: Shared libraries [i -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-3-686/postinst/bootloader-error-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/old-dir-initrd-link-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/kimage-is-a-directory: linux-image-2.6.18-3-686/preinst/elilo-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/old-system-map-link-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/lilo-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/depmod-error-initrd-2.6.18-3-686: false linux-image-2.6.18-3-686/preinst/bootloader-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/prerm/removing-running-kernel-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/create-kimage-link-2.6.18-3-686: true linux-image-2.6.18-3-686/prerm/would-invalidate-boot-loader-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/abort-install-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/overwriting-modules-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/initrd-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/lilo-has-ramdisk: linux-image-2.6.18-3-686/preinst/already-running-this-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/bootloader-test-error-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/abort-overwrite-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/old-initrd-link-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/depmod-error-2.6.18-3-686: false linux-image-2.6.18-3-686/preinst/failed-to-move-modules-2.6.18-3-686: -- Passa a Infostrada. ADSL e Telefono senza limiti e senza canone Telecom http://click.libero.it/infostrada14feb07
Bug#80878: (no subject)
by mail.te.com (IMP) with HTTP for [EMAIL PROTECTED]@localhost; Tue, 14 Nov 2006 17:31:07 -0500 To: [EMAIL PROTECTED] Subject: I got it Message-ID: [EMAIL PROTECTED] Date: Tue, 14 Nov 2006 17:31:07 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Disposition: inline User-Agent: Internet Messaging Program (IMP) 3.2.2 Dude I finally got it: http://te.comuqh2i3hl0nhauuc5huu5huuc.fourthac.com Horacio Get your free te.com email now! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385284: Serial controller Timedia stop work on new kernel
Package: linux-image-2.6.17-2 Version: 2.6.17-2 Severity: normal I have a serial controller Timedia, that works fine under 2.4.27-3-686 but not on kernel 2.6.16-2-686 and 2.6.17-2-686. thanks in advance, João Serrachinha Linux version 2.4.27-3-686 ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #1 Tue May 30 00:56:40 UTC 2006 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 0fff (usable) BIOS-e820: 0fff - 0fff3000 (ACPI NVS) BIOS-e820: 0fff3000 - 1000 (ACPI data) BIOS-e820: fec0 - 0001 (reserved) 0MB HIGHMEM available. 255MB LOWMEM available. found SMP MP-table at 000f5250 hm, page 000f5000 reserved twice. hm, page 000f6000 reserved twice. hm, page 000f1000 reserved twice. hm, page 000f2000 reserved twice. On node 0 totalpages: 65520 zone(0): 4096 pages. zone(1): 61424 pages. zone(2): 0 pages. ACPI: RSDP (v000 IntelR) @ 0x000f6d10 ACPI: RSDT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x) @ 0x0fff3000 ACPI: FADT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x) @ 0x0fff3040 ACPI: MADT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x) @ 0x0fff6c40 ACPI: DSDT (v001 INTELR AWRDACPI 0x1000 MSFT 0x010d) @ 0x ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 Pentium 4(tm) XEON(tm) APIC version 20 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) Processor #1 Pentium 4(tm) XEON(tm) APIC version 20 Using ACPI for processor (LAPIC) configuration information Intel MultiProcessor Specification v1.4 Virtual Wire compatibility mode. OEM ID: OEM0 Product ID: PROD APIC at: 0xFEE0 I/O APIC #2 Version 17 at 0xFEC0. Enabling APIC mode: Flat. Using 1 I/O APICs Processors: 2 Kernel command line: root=/dev/hda1 ro Initializing CPU#0 Detected 2794.865 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 5583.66 BogoMIPS Memory: 252336k/262080k available (1198k kernel code, 9356k reserved, 451k data, 116k init, 0k highmem) Dentry cache hash table entries: 32768 (order: 6, 262144 bytes) Inode cache hash table entries: 16384 (order: 5, 131072 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 16384 (order: 4, 65536 bytes) Page-cache hash table entries: 65536 (order: 6, 262144 bytes) CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: After generic, caps: bfebfbff CPU: Common caps: bfebfbff CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX enabled ExtINT on CPU#0 ESR value before enabling vector: ESR value after enabling vector: ENABLING IO-APIC IRQs Setting 2 in the phys_id_present_map ...changing IO-APIC physical APIC ID to 2 ... ok. init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-5, 2-9, 2-10, 2-11, 2-20, 2-21 not connected. ..TIMER: vector=0x31 pin1=2 pin2=0 number of MP IRQ sources: 22. number of IO-APIC #2 registers: 24. testing the IO APIC... IO APIC #2.. register #00: 0200 ...: physical APIC id: 02 ...: Delivery Type: 0 ...: LTS : 0 register #01: 00178020 ... : max redirection entries: 0017 ... : PRQ implemented: 1 ... : IO APIC version: 0020 register #02: ... : arbitration: 00 register #03: 0001 ... : Boot DT: 1 IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 100 0 00000 01 001 01 000 0 01139 02 001 01 000 0 01131 03 001 01 000 0 01141 04 001 01 000 0 01149 05 000 00 100 0 00000 06 001 01 000 0 01151 07 001 01 000 0 01159 08 001 01 000 0 01161 09 000 00 100 0 00000 0a 000 00 100 0 00000 0b 000 00 100 0 00000 0c 001 01 000 0 01169 0d 001 01 000 0 01171 0e 001 01 000 0 01179 0f 001 01 000 0 01181 10 001 01 110 1 01189 11 001 01 110 1 01191 12 001 01 110 1 01199 13 001 01 110 1 011A1 14 000 00 1
Bug#376925: initramfs-tools: init should say 'Will now load...'!
Package: initramfs-tools Version: 0.67 Severity: wishlist anything to say? said that, 'Loading, please wait...' does not make the hole bootup-process very round! :-) yes i might be considert a pedant or something the like! -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-tm40x Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages initramfs-tools depends on: ii busybox 1:1.1.3-2 Tiny utilities for small and embed ii cpio 2.6-15 GNU cpio -- a program to manage ar ii klibc-utils 1.4.8-1small statically-linked utilities ii module-init-tools 3.2.2-3tools for managing Linux kernel mo ii udev 0.093-1/dev/ and hotplug management daemo initramfs-tools recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#358617: linux-image-2.6.16-1-686: please enable CONFIG_IPW2200_MONITOR=y
I'm with Noèl on this one. Monitor mode should be enabled ASAP. I'm even getting firmware errors even not being able to enable monitor mode so I see no point on having it enabled. Prueba el correo Terra ( http://www.terra.es/correo ); Seguro, rápido, fiable.
Bug#357533: linux-image-2.6.15-1-k7: nforce4 driver (network, sata, usb2 ) don't work with 2.6.15-k7-4
Package: linux-image-2.6.15-1-k7 Version: 2.6.15-4 Severity: important After testing kernel update (2.6.12 to 2.6.15) network module (forcedepth) sata and usb2 don't work anymore I have a nvidia nforce4 chipset. Thanks dmesg : ... PCI: Setting latency timer of device :00:0a.0 to 64 forcedeth: Couldn't find register window for device :00:0a.0. ACPI: PCI interrupt for device :00:0a.0 disabled forcedeth: probe of :00:0a.0 failed with error -22 sata_sil :05:0a.0: version 0.9 ACPI: PCI Interrupt Link [APC4] BIOS reported IRQ 3, using IRQ 19 ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19 ACPI: PCI Interrupt :05:0a.0[A] - Link [APC4] - GSI 19 (level, low) - IRQ 50 ACPI: PCI interrupt for device :05:0a.0 disabled sata_sil: probe of :05:0a.0 failed with error -12 ... -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-386 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.15-1-k7 depends on: ii initramfs-tools [linux-initra 0.51 tools for generating an initramfs ii module-init-tools 3.2.2-1tools for managing Linux kernel mo Versions of packages linux-image-2.6.15-1-k7 recommends: ii libc6-i6862.3.5-13 GNU C Library: Shared libraries [i -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#287867: Can you confirm this bug please ?
Hi Sven, Sven Luther wrote: Hi Kevin, ... Can you confirm this bug (gdm cursor dissapearing) is still present in 2.6.15-2 kernels or not ? Unfortunately my iBook laptop had a hard disk failure several months ago, so I'm no longer able to make the test. :-( Maybe you could try contacting the fellow who reported the same problem in this message? http://lists.debian.org/debian-powerpc/2004/12/msg00494.html best regards, -- Kevin B. McCarty [EMAIL PROTECTED] Physics Department WWW: http://www.princeton.edu/~kmccarty/Princeton University GPG: public key ID 4F83C751 Princeton, NJ 08544 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346246: acknowledged by developer (Re: Bug#346246: Can't install nvidia drivers)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
#346246: Can't install nvidia drivers, which was filed against the
linux-source-2.6.15 package.
It has been closed by one of the developers, namely maximilian
attems [EMAIL PROTECTED].
Their explanation is attached below. If this explanation is
unsatisfactory and you have not received a better one in a separate
message then please contact the developer, by replying to this
email.
Debian bug tracking system administrator (administrator, Debian
Bugs database)
Received: (at 346246-done) by bugs.debian.org; 7 Jan 2006 10:52:35
+
From [EMAIL PROTECTED] Sat Jan 07 02:52:35 2006
Return-path: [EMAIL PROTECTED] Received: from baikonur.stro.at
([213.239.196.228]) by spohr.debian.org with esmtp (Exim 4.50) id
1EvBgY-0001J9-QK for [EMAIL PROTECTED]; Sat, 07 Jan 2006
02:52:34 -0800 Received: from nancy (stallburg.stro.at
[128.131.216.190]) by baikonur.stro.at (Postfix) with ESMTP id
8BF9B5C00B for [EMAIL PROTECTED]; Sat, 7 Jan 2006
11:53:10 +0100 (CET) Received: from max by nancy with local (Exim
4.60) (envelope-from [EMAIL PROTECTED]) id 1EvBgK-00035L-HG for
[EMAIL PROTECTED]; Sat, 07 Jan 2006 11:52:20 +0100 Date:
Sat, 7 Jan 2006 11:52:20 +0100 From: maximilian attems
[EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re:
Bug#346246: Can't install nvidia drivers Message-ID:
[EMAIL PROTECTED] References:
[EMAIL PROTECTED] MIME-Version: 1.0 Content-Type:
text/plain; charset=us-ascii Content-Disposition: inline
In-Reply-To: [EMAIL PROTECTED] User-Agent:
Mutt/1.5.11 X-Virus-Scanned: by Amavis (ClamAV) at stro.at
X-Spam-Checker-Version: SpamAssassin
2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on
spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-6.0
required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no
version=2.60-bugs.debian.org_2005_01_02
On Fri, 06 Jan 2006, [EMAIL PROTECTED] wrote:
Package: linux-source-2.6.15 Version: 2.6.15-1
Can't install nvidia drivers version 1.0-8178*:
*Using: nvidia-installer ncurses user interface - - License
accepted. - - There appears to already be a driver installed on
your system (version: 1.0- 7664). As part of installing this
driver (version: 1.0-8178), the existing driver will be
uninstalled. Are you sure you want to continue? ('no' will a
bort installation) (Answer: Yes) - - No precompiled kernel
interface was found to match your kernel; would you li ke the
installer to attempt to download a kernel interface for your
kernel f rom the NVIDIA ftp site (ftp://download.nvidia.com)?
(Answer: Yes) - - No matching precompiled kernel interface was
found on the NVIDIA ftp site; this means that the installer will
need to compile a kernel interface for your kernel. - -
Performing CC test with CC=cc. - - Kernel source path:
'/usr/src/linux' - - Kernel output path: '/usr/src/linux' - -
Performing rivafb check. ERROR: Your kernel was configured to
include rivafb support!
The rivafb driver conflicts with the NVIDIA driver, please
reconfigure your kernel and *disable* rivafb support, then try
installing the NVIDIA kernel module again. ERROR: Installation
has failed. Please see the file '/var/log/nvidia-installer.log'
for details. You may find suggestions on fixing installation
problems in the README available on the Linux driver download
page at www.nvidia.com.
beside the error message beeing *crystal* clear, we don't support
closed source binary drivers
closing
I know it's crystal, it's all about compiling for rivafb support! And
don't tell me that i can make my custom kernel!
This rivafb support on Debian kernel start on 2.6.14 and still exist
on 2.6.15.
For my servers boxes it's great, but for my desktop boxes no.
Is there a way that server boxes and game boxes are both happy!?
Many thanks.
João
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFDwi+Va72iljGeL5gRAu30AKDBfDILWsyD5g4MEEjN86u3srnrxgCgr5LN
etiB73KHo3cremzmm+ssZ5g=
=YYwI
-END PGP SIGNATURE-
Bug#346246: Can't install nvidia drivers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: linux-source-2.6.15
Version: 2.6.15-1
Can't install nvidia drivers version 1.0-8178*:
*Using: nvidia-installer ncurses user interface
- - License accepted.
- - There appears to already be a driver installed on your system
(version: 1.0-
7664). As part of installing this driver (version: 1.0-8178), the
existing
driver will be uninstalled. Are you sure you want to continue?
('no' will a
bort installation) (Answer: Yes)
- - No precompiled kernel interface was found to match your kernel;
would you li
ke the installer to attempt to download a kernel interface for your
kernel f
rom the NVIDIA ftp site (ftp://download.nvidia.com)? (Answer: Yes)
- - No matching precompiled kernel interface was found on the NVIDIA
ftp site;
this means that the installer will need to compile a kernel
interface for
your kernel.
- - Performing CC test with CC=cc.
- - Kernel source path: '/usr/src/linux'
- - Kernel output path: '/usr/src/linux'
- - Performing rivafb check.
ERROR: Your kernel was configured to include rivafb support!
The rivafb driver conflicts with the NVIDIA driver, please
reconfigure your kernel and *disable* rivafb support, then
try installing the NVIDIA kernel module again.
ERROR: Installation has failed. Please see the file
'/var/log/nvidia-installer.log' for details. You may find
suggestions
on fixing installation problems in the README available on the
Linux
driver download page at www.nvidia.com.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFDvpn1a72iljGeL5gRAt5sAJ9WNxZvIOkqgeTY7moILHK5uxa9owCgqSuf
0uy/LdKVNFeqyoUfeiin6zw=
=liG7
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#335229: udev: problems with firewire CDR hotplug
[EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: On Oct 22, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm having problems hotplugging my firewire CDR. I'm using linux-image-2.6.13-1-686_2.6.13-1 but it fails with any new kernel version. The error log is: ieee1394: Error parsing configrom for node 0-00:1023 ieee1394: Node changed: 0-00:1023 - 0-01:1023 ieee1394: Node added: ID:BUS[0-00:1023] GUID[001010030500] I can't see how this would be related to udev. I had no problems with previous udev and hotplug packages and linux-image-2.6.12-1-686. Notice that the firewire support is utterly broken in pre 2.6.14-rc4 kernels, and that many changes got into 2.6.14-rc4 which helped a lot. I got it working with previous kernels. I think with 2.6.11 and 2.6.12 but I can't anymore. Please try the 2.6.14-rc4 packages currently in experimental and confirm that it fixes this problem or not. I just tried a custom compiled 2.6.14-rc5 kernel without luck (just the same problem) I'll try the older udev + hotplug. I tried the older udev + hotplug with the same unsuccessful results. If someone got it working with current Debian unstable please let me know. I just found a workaround. If I do: rmmod sbp2 modprobe sbp2 the drive is recognized and the device node created. So this is probably a problem in sbp2. Sorry for filling it directly in udev. Prueba el Nuevo Correo Terra; Seguro, Rápido, Fiable.
Bug#335229: udev: problems with firewire CDR hotplug
[EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: On Oct 22, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm having problems hotplugging my firewire CDR. I'm using linux-image-2.6.13-1-686_2.6.13-1 but it fails with any new kernel version. The error log is: ieee1394: Error parsing configrom for node 0-00:1023 ieee1394: Node changed: 0-00:1023 - 0-01:1023 ieee1394: Node added: ID:BUS[0-00:1023] GUID[001010030500] I can't see how this would be related to udev. I had no problems with previous udev and hotplug packages and linux-image-2.6.12-1-686. Notice that the firewire support is utterly broken in pre 2.6.14-rc4 kernels, and that many changes got into 2.6.14-rc4 which helped a lot. I got it working with previous kernels. I think with 2.6.11 and 2.6.12 but I can't anymore. Please try the 2.6.14-rc4 packages currently in experimental and confirm that it fixes this problem or not. I just tried a custom compiled 2.6.14-rc5 kernel without luck (just the same problem) I'll try the older udev + hotplug. I tried the older udev + hotplug with the same unsuccessful results. If someone got it working with current Debian unstable please let me know. Prueba el Nuevo Correo Terra; Seguro, Rápido, Fiable.
Bug#335229: udev: problems with firewire CDR hotplug
On Oct 22, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm having problems hotplugging my firewire CDR. I'm using linux-image-2.6.13-1-686_2.6.13-1 but it fails with any new kernel version. The error log is: ieee1394: Error parsing configrom for node 0-00:1023 ieee1394: Node changed: 0-00:1023 - 0-01:1023 ieee1394: Node added: ID:BUS[0-00:1023] GUID[001010030500] I can't see how this would be related to udev. I had no problems with previous udev and hotplug packages and linux-image-2.6.12-1-686. Notice that the firewire support is utterly broken in pre 2.6.14-rc4 kernels, and that many changes got into 2.6.14-rc4 which helped a lot. I got it working with previous kernels. I think with 2.6.11 and 2.6.12 but I can't anymore. Please try the 2.6.14-rc4 packages currently in experimental and confirm that it fixes this problem or not. I can't find them. Where they are? Prueba el Nuevo Correo Terra; Seguro, Rápido, Fiable.
Bug#335229: udev: problems with firewire CDR hotplug
[EMAIL PROTECTED] wrote: On Oct 22, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm having problems hotplugging my firewire CDR. I'm using linux-image-2.6.13-1-686_2.6.13-1 but it fails with any new kernel version. The error log is: ieee1394: Error parsing configrom for node 0-00:1023 ieee1394: Node changed: 0-00:1023 - 0-01:1023 ieee1394: Node added: ID:BUS[0-00:1023] GUID[001010030500] I can't see how this would be related to udev. I had no problems with previous udev and hotplug packages and linux-image-2.6.12-1-686. Notice that the firewire support is utterly broken in pre 2.6.14-rc4 kernels, and that many changes got into 2.6.14-rc4 which helped a lot. I got it working with previous kernels. I think with 2.6.11 and 2.6.12 but I can't anymore. Please try the 2.6.14-rc4 packages currently in experimental and confirm that it fixes this problem or not. I just tried a custom compiled 2.6.14-rc5 kernel without luck (just the same problem) I'll try the older udev + hotplug. If someone got it working with current Debian unstable please let me know. Prueba el Nuevo Correo Terra; Seguro, Rápido, Fiable.
Re: [Crosspost] GNU/Linux userland?
John Lenz wrote: On 04/13/05 14:40:31, Oliver Korpilla wrote: You might also look at www.openembedded.org It has support for cross compiling, and with one command can build an entire userland. Not sure if it is exactly a fit for what you want to do, but it seems very close. Thanks, this sounds great, and together with the directions I got about Gentoo and Heretix/Rubyx seems to precisely match my request. Thanks to you, and thanks to all helpful replies! :) With kind regards, Oliver Korpilla -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272768: USB device detection broken in latest kernels version 2.4.26 and 2.4.27
Hi, thanks for your answer. The only kernel I had installed before the upgrade was 2.4.26-2 I've been using that kernel since may/june without problems. During upgrade, apt-get installed 2.4.26-6 and 2.4.27-2 Package: kernel-image-2.4.27-1-k7 Priority: optional Section: base Installed-Size: 30254 Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Architecture: i386 Source: kernel-image-2.4.27-i386 Version: 2.4.27-2 Package: kernel-image-2.4.26-1-k7 Priority: optional Section: base Installed-Size: 31860 Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Architecture: i386 Source: kernel-image-2.4.26-i386 Version: 2.4.26-6 When the camera didn't work after upgrade I suspected a bug in kernel 2.4.27 and rebooted to the new 2.4.26 with the same results. Output of lspci :00:00.0 Host bridge: VIA Technologies, Inc. VT8375 [KM266/KL266] Host Bridge :00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] :00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) :00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) :00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) :00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) :00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge :00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) :00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50) :00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) :01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266] Output of cat /proc/bus/usb/devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 2.04 S: Manufacturer=Linux 2.4.27-1-k7 ehci_hcd S: Product=VIA Technologies, Inc. USB 2.0 S: SerialNumber=00:10.3 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms If I'm not wrong, with 2.4.26-2 kernel, the output of cat /proc/bus/usb/devices was longer, something like entries for 2 or 3 devices (things like bus, controllers, ports if I remember correctly... ) intead of only 1. Thanks for your help.
Debian Installation
Hello All I am a recent convert to Debian. have installed Debian in my old machine i386 machine at 300 Mhz with 256 MB RAM.and 30GB HDD. It connects to the internet via a router. I would like to know if there is a way I can have this macine to identlify the network and the ip address. I have a mouse which connects to the USB Port - but its also not being identified by the X Window. Need some help. Thanks Regards, AARON ROY
