Welcome to Linux Forums! With a comprehensive Linux Forum, information on various types of Linux software and many Linux Reviews articles, we have all the knowledge you need a click away, or accessible via our knowledgeable members.
Write an article for LinuxForums Today! Win Great Prizes!
i compiled the (one of the) 2.6 kernels under slackware 10.1.
no issues found until i saw a weird error message when booting up. Later inverstigation found that the 2.6 kernel was using the 2.4 kernels modules.
here is /var/log/syslog:
Code:
Nov 12 22:56:13 toughbox kernel: Linux version 2.4.29 (root@midas) (gcc version 3.3.4) #6 Thu Jan 20 16:30:37 PST 2005
Nov 12 22:56:13 toughbox kernel: BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
Nov 12 22:56:13 toughbox kernel: BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
Nov 12 22:56:13 toughbox kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Nov 12 22:56:13 toughbox kernel: BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
Nov 12 22:56:13 toughbox kernel: BIOS-e820: 000000001fff0000 - 000000001fff3000 (ACPI NVS)
Nov 12 22:56:13 toughbox kernel: BIOS-e820: 000000001fff3000 - 0000000020000000 (ACPI data)
Nov 12 22:56:13 toughbox kernel: BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
Nov 12 22:56:13 toughbox kernel: On node 0 totalpages: 131056
Nov 12 22:56:13 toughbox kernel: zone(0): 4096 pages.
Nov 12 22:56:13 toughbox kernel: zone(1): 126960 pages.
Nov 12 22:56:13 toughbox kernel: zone(2): 0 pages.
Nov 12 22:56:13 toughbox kernel: Kernel command line: initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=6464 rw root=/dev/ram SLACK_KERNEL=bare.i BOOT_IMAGE=/kernels/bare.i/bzImage root=/dev/hdb6 noinitrd ro
Nov 12 22:56:13 toughbox kernel: Detected 2679.613 MHz processor.
Nov 12 22:56:13 toughbox kernel: Console: colour VGA+ 80x25
Nov 12 22:56:13 toughbox kernel: Calibrating delay loop... 5347.73 BogoMIPS
Nov 12 22:56:13 toughbox kernel: Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
Nov 12 22:56:13 toughbox kernel: CPU: Intel(R) Celeron(R) CPU 2.66GHz stepping 03
Nov 12 22:56:13 toughbox kernel: POSIX conformance testing by UNIFIX
Nov 12 22:56:13 toughbox kernel: mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
Nov 12 22:56:13 toughbox kernel: mtrr: detected mtrr type: Intel
Nov 12 22:56:13 toughbox kernel: PCI: Probing PCI hardware (bus 00)
Nov 12 22:56:13 toughbox kernel: Transparent bridge - Intel Corp. 82801BA/CA/DB/EB PCI Bridge
Nov 12 22:56:13 toughbox kernel: Initializing RT netlink socket
Nov 12 22:56:13 toughbox kernel: Starting kswapd
Nov 12 22:56:13 toughbox kernel: pty: 512 Unix98 ptys configured
Nov 12 22:56:13 toughbox kernel: RAMDISK driver initialized: 16 RAM disks of 6464K size 1024 blocksize
Nov 12 22:56:13 toughbox kernel: hda: Maxtor 6Y120P0, ATA DISK drive
Nov 12 22:56:13 toughbox kernel: hdb: ST38410A, ATA DISK drive
Nov 12 22:56:13 toughbox kernel: blk: queue c03ad460, I/O limit 4095Mb (mask 0xffffffff)
Nov 12 22:56:13 toughbox kernel: blk: queue c03ad59c, I/O limit 4095Mb (mask 0xffffffff)
Nov 12 22:56:13 toughbox kernel: hdc: SONY DVD RW DRU-710A, ATAPI CD/DVD-ROM drive
Nov 12 22:56:13 toughbox kernel: hdd: LITE-ON CD-RW SOHR-5238S, ATAPI CD/DVD-ROM drive
Nov 12 22:56:13 toughbox kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Nov 12 22:56:13 toughbox kernel: ide1 at 0x170-0x177,0x376 on irq 15
Nov 12 22:56:13 toughbox kernel: hda: attached ide-disk driver.
Nov 12 22:56:13 toughbox kernel: hda: host protected area => 1
Nov 12 22:56:13 toughbox kernel: hdb: attached ide-disk driver.
Nov 12 22:56:13 toughbox kernel: hdb: host protected area => 1
Nov 12 22:56:13 toughbox kernel: hdc: attached ide-cdrom driver.
Nov 12 22:56:13 toughbox kernel: hdd: attached ide-cdrom driver.
Nov 12 22:56:13 toughbox kernel: kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
Nov 12 22:56:13 toughbox last message repeated 2 times
Nov 12 22:56:13 toughbox kernel: 8regs : 2875.200 MB/sec
Nov 12 22:56:13 toughbox kernel: 32regs : 1930.400 MB/sec
Nov 12 22:56:13 toughbox kernel: pIII_sse : 4514.000 MB/sec
Nov 12 22:56:13 toughbox kernel: pII_mmx : 2856.800 MB/sec
Nov 12 22:56:13 toughbox kernel: p5_mmx : 2856.800 MB/sec
Nov 12 22:56:13 toughbox kernel: raid5: using function: pIII_sse (4514.000 MB/sec)
Nov 12 22:56:13 toughbox kernel: VFS: Mounted root (ext3 filesystem) readonly.
Nov 12 22:56:13 toughbox kernel: agpgart: Detected an Intel(R) 865G, but could not find the secondary device. Assuming a non-integrated video card.
Nov 12 22:56:14 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:14 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:14 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:14 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:14 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:14 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:14 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:14 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:14 toughbox kernel: i810_rng: cannot disable RNG, aborting
Nov 12 22:56:15 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:15 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:15 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:15 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:15 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:15 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:15 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:15 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:16 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:16 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:16 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:16 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:16 toughbox kernel: usb.c: USB device 2 (vend/prod 0x45e/0x8a) is not claimed by any active driver.
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:16 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:16 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:16 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:16 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:16 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:17 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:17 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:17 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:17 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:17 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:17 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:17 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:18 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:18 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:18 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:18 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:18 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:18 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:18 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:18 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:20 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:20 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:20 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:20 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:20 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:21 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:21 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:21 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:22 toughbox insmod: insmod: a module named input already exists
Nov 12 22:56:22 toughbox insmod: insmod: insmod usbkbd failed
Nov 12 22:56:23 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:23 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:23 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:23 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:23 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:23 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:23 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:24 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:24 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:24 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:24 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:24 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:24 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:24 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:24 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:24 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:25 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:25 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:25 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:25 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:25 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:25 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:25 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:26 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:26 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:26 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:26 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:26 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:26 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:26 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:27 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:27 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:27 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:27 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:27 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:27 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:27 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:28 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:28 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:28 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:28 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 22:56:28 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:28 toughbox kernel: shpchp: shpc_init : shpc_cap_offset == 0
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 12 22:56:28 toughbox insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 12 23:01:44 toughbox kernel: keyboard: Timeout - AT keyboard not present?(f4)
Nov 12 23:01:47 toughbox kernel: keyboard: Timeout - AT keyboard not present?(f3)
Nov 12 23:01:47 toughbox kernel: keyboard: Timeout - AT keyboard not present?(f4)
Nov 12 23:01:48 toughbox kernel: keyboard: Timeout - AT keyboard not present?(f4)
Nov 12 23:02:00 toughbox bonobo-activation-server (root-3793): iid OAFIID:BrokenNoType:20000808 has a NULL type
Nov 12 23:02:00 toughbox bonobo-activation-server (root-3793): invalid character '#' in iid 'OAFIID:This#!!%$iid%^$%_|~!OAFIID_ContainsBadChars'
Nov 12 23:02:31 toughbox bonobo-activation-server (root-3793): iid OAFIID:BrokenNoType:20000808 has a NULL type
Nov 12 23:02:31 toughbox bonobo-activation-server (root-3793): invalid character '#' in iid 'OAFIID:This#!!%$iid%^$%_|~!OAFIID_ContainsBadChars'
Nov 12 23:07:03 toughbox dialog: /dev/gpmctl: No such file or directory
Nov 12 23:07:05 toughbox dialog: /dev/gpmctl: No such file or directory
Nov 12 23:10:00 toughbox kernel: end_request: I/O error, dev 02:00 (floppy), sector 0
Nov 12 23:10:11 toughbox last message repeated 13 times
this also show that my keyboard is stuffed.
how do i fix this?
weed
__________________
"Time has more than one meaning, and is more than one dimension" - /.unknown
--Registered Linux user #396583--
There is a 2.6 kernel in the testing directory of your Slackware CD's. cd to the testing directory and installpkg *.tgz (as root). I know this doesn't really answer your question of how to fix your problem but for when you get it fixed, it is a nice easy way to get a 2.6 series kernel.
Bryan
__________________
Looking for a distro? Look here.
"There can be no doubt that all our knowledge begins with experience." - Immanuel Kant (Critique of Pure Reason)
Queen's University - Arts and Science 2008 (Sociology)
Registered Linux User #386147.
Open Source Security Myths Dispelled Dispel the five major myths surrounding Open Source Security and gain the tools necessary to make a truly informed decision for your IT organization subscribe
InformationWeek InformationWeek is the only newsweekly you'll need to stay on top of the latest developments in information technology. subscribe
The Linux Kernel Compiling, theory, programming or other discussion about the linux kernel
Submit Your Article
Latest Articles
Editor's Choice
Article Categories
Join Linux Forums Today
Win Great Prizes
Linear Mode
