Ok for some reason it's not finding my ethernet card. In windows it's a "1394 net adapter" so i have no internet. and also i want to hook up a DLT Drive,it found it but i can only access my scsi /dev/sda if anyone knows how to hook that up would be greate but i need a internet connction :S
and the raid too but that's not nessary.
Thanks again guys
here's the syslog
Mar 16 18:04:39 super kernel: Linux version 2.4.29 (root@midas) (gcc version 3.3.4) #2 Thu Jan 20 16:20:24 PST 2005
Mar 16 18:04:39 super kernel: BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
Mar 16 18:04:39 super kernel: BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
Mar 16 18:04:39 super kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Mar 16 18:04:39 super kernel: BIOS-e820: 0000000000100000 - 000000005fff0000 (usable)
Mar 16 18:04:39 super kernel: BIOS-e820: 000000005fff0000 - 000000005fff3000 (ACPI NVS)
Mar 16 18:04:39 super kernel: BIOS-e820: 000000005fff3000 - 0000000060000000 (ACPI data)
Mar 16 18:04:39 super kernel: BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
Mar 16 18:04:39 super kernel: BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
Mar 16 18:04:39 super kernel: BIOS-e820: 00000000fefffc00 - 00000000ff000000 (reserved)
Mar 16 18:04:39 super kernel: BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
Mar 16 18:04:39 super kernel: Warning only 896MB will be used.
Mar 16 18:04:39 super kernel: Use a HIGHMEM enabled kernel.
Mar 16 18:04:39 super kernel: On node 0 totalpages: 229376
Mar 16 18:04:39 super kernel: zone(0): 4096 pages.
Mar 16 18:04:39 super kernel: zone(1): 225280 pages.
Mar 16 18:04:39 super kernel: zone(2): 0 pages.
Mar 16 18:04:39 super kernel: Kernel command line: BOOT_IMAGE=Linux ro root=346
Mar 16 18:04:39 super kernel: Detected 1994.852 MHz processor.
Mar 16 18:04:39 super kernel: Console: colour VGA+ 80x25
Mar 16 18:04:39 super kernel: Calibrating delay loop... 3984.58 BogoMIPS
Mar 16 18:04:39 super kernel: Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
Mar 16 18:04:39 super kernel: CPU: AMD Athlon(tm) 64 Processor 3200+ stepping 0a
Mar 16 18:04:39 super kernel: POSIX conformance testing by UNIFIX
Mar 16 18:04:39 super kernel: mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
Mar 16 18:04:39 super kernel: mtrr: detected mtrr type: Intel
Mar 16 18:04:39 super kernel: PCI: Probing PCI hardware (bus 00)
Mar 16 18:04:39 super kernel: Initializing RT netlink socket
Mar 16 18:04:39 super kernel: Starting kswapd
Mar 16 18:04:39 super kernel: pty: 512 Unix98 ptys configured
Mar 16 18:04:39 super kernel: RAMDISK driver initialized: 16 RAM disks of 7777K size 1024 blocksize
Mar 16 18:04:39 super kernel: hdb: C/H/S=20510/81/84 from BIOS ignored
Mar 16 18:04:39 super kernel: hda: TOSHIBA DVD-ROM SD-R1002, ATAPI CD/DVD-ROM drive
Mar 16 18:04:39 super kernel: hdb: WDC WD1200JB-00GVA0, ATA DISK drive
Mar 16 18:04:39 super kernel: blk: queue c040c59c, I/O limit 4095Mb (mask 0xffffffff)
Mar 16 18:04:39 super kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Mar 16 18:04:39 super kernel: hdb: attached ide-disk driver.
Mar 16 18:04:39 super kernel: hdb: host protected area => 1
Mar 16 18:04:39 super kernel: hda: attached ide-cdrom driver.
Mar 16 18:04:39 super kernel: <Adaptec 29160 Ultra160 SCSI adapter>
Mar 16 18:04:39 super kernel: aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
Mar 16 18:04:39 super kernel:
Mar 16 18:04:39 super kernel: (scsi1:A:1): 160.000MB/s transfers (80.000MHz DT, offset 62, 16bit)
Mar 16 18:04:39 super kernel: (scsi1:A:2): 20.000MB/s transfers (20.000MHz, offset 15)
Mar 16 18:04:39 super kernel: (scsi1:A:3): 10.000MB/s transfers (10.000MHz, offset 15)
Mar 16 18:04:39 super kernel: (scsi1:A:5): 20.000MB/s transfers (10.000MHz, offset 15, 16bit)
Mar 16 18:04:39 super kernel: Vendor: Promise Model: 8 Disk RAID5 Rev: 1.10
Mar 16 18:04:39 super kernel: Type: Direct-Access ANSI SCSI revision: 03
Mar 16 18:04:39 super kernel: Vendor: iomega Model: jaz 2GB Rev: E.17
Mar 16 18:04:39 super kernel: Type: Direct-Access ANSI SCSI revision: 02
Mar 16 18:04:39 super kernel: Vendor: ARCHIVE Model: Python 04106-XXX Rev: 7550
Mar 16 18:04:39 super kernel: Type: Sequential-Access ANSI SCSI revision: 02
Mar 16 18:04:39 super kernel: Vendor: BNCHMARK Model: DLT1 Rev: 5E40
Mar 16 18:04:39 super kernel: Type: Sequential-Access ANSI SCSI revision: 02
Mar 16 18:04:39 super kernel: scsi1:A:1:0: Tagged Queuing enabled. Depth 8
Mar 16 18:04:39 super kernel: Attached scsi disk sda at scsi1, channel 0, id 1, lun 0
Mar 16 18:04:39 super kernel: Attached scsi removable disk sdb at scsi1, channel 0, id 2, lun 0
Mar 16 18:04:39 super kernel: SCSI device sda: 2734374272 512-byte hdwr sectors (1400000 MB)
Mar 16 18:04:39 super kernel: Current 00:00: sns = 70 2
Mar 16 18:04:39 super kernel: ASC=3a ASCQ= 0
Mar 16 18:04:39 super kernel: Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x11 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00 0xff 0xfe 0x01 0xff 0xfe 0x00 0x00
Mar 16 18:04:39 super kernel: sdb : READ CAPACITY failed.
Mar 16 18:04:39 super kernel: sdb : status = 1, message = 00, host = 0, driver = 08
Mar 16 18:04:39 super kernel: Current sd00:00: sns = 70 2
Mar 16 18:04:39 super kernel: ASC=3a ASCQ= 0
Mar 16 18:04:39 super kernel: Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x11 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00 0xff 0xfe 0x01 0xff 0xfe 0x00 0x00
Mar 16 18:04:39 super kernel: sdb : block size assumed to be 512 bytes, disk size 1GB.
Mar 16 18:04:39 super kernel: I/O error: dev 08:10, sector 0
Mar 16 18:04:39 super kernel: unable to read partition table
Mar 16 18:04:39 super kernel: 8regs : 3050.000 MB/sec
Mar 16 18:04:39 super kernel: 32regs : 1894.800 MB/sec
Mar 16 18:04:39 super kernel: pIII_sse : 6378.400 MB/sec
Mar 16 18:04:39 super kernel: pII_mmx : 4517.200 MB/sec
Mar 16 18:04:39 super kernel: p5_mmx : 5674.800 MB/sec
Mar 16 18:04:39 super kernel: raid5: using function: pIII_sse (6378.400 MB/sec)
Mar 16 18:04:39 super kernel: FAT: bogus logical sector size 19205
Mar 16 18:04:39 super last message repeated 2 times
Mar 16 18:04:39 super kernel: reiserfs: found format "3.6" with standard journal
Mar 16 18:04:39 super kernel: reiserfs: checking transaction log (device ide0(3,70)) ...
Mar 16 18:04:39 super kernel: for (ide0(3,70))
Mar 16 18:04:39 super kernel: ide0(3,70):Using r5 hash to sort names
Mar 16 18:04:39 super kernel: VFS: Mounted root (reiserfs filesystem) readonly.
Mar 16 18:04:39 super cardmgr[75]: no pcmcia driver in /proc/devices
Mar 16 18:04:40 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:40 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:40 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Mar 16 18:04:40 super 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
Mar 16 18:04:40 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Mar 16 18:04:40 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Mar 16 18:04:40 super 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
Mar 16 18:04:40 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Mar 16 18:04:40 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:40 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:40 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Mar 16 18:04:40 super 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
Mar 16 18:04:40 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Mar 16 18:04:40 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Mar 16 18:04:40 super 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
Mar 16 18:04:40 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Mar 16 18:04:42 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:42 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Mar 16 18:04:42 super 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
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Mar 16 18:04:42 super 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
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Mar 16 18:04:42 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:42 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Mar 16 18:04:42 super 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
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Mar 16 18:04:42 super 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
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Mar 16 18:04:42 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:42 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Mar 16 18:04:42 super 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
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Mar 16 18:04:42 super 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
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Mar 16 18:04:42 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:42 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Mar 16 18:04:42 super 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
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Mar 16 18:04:42 super 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
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Mar 16 18:04:42 super kernel: usb.c: USB device not accepting new address=2 (error=-71)
Mar 16 18:04:42 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:42 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Mar 16 18:04:42 super 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
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Mar 16 18:04:42 super 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
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Mar 16 18:04:42 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:42 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Mar 16 18:04:42 super 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
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Mar 16 18:04:42 super 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
Mar 16 18:04:42 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Mar 16 18:04:42 super kernel: usb.c: USB device not accepting new address=3 (error=-71)
Mar 16 18:04:43 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:43 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:43 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Mar 16 18:04:43 super 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
Mar 16 18:04:43 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Mar 16 18:04:43 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Mar 16 18:04:43 super 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
Mar 16 18:04:43 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Mar 16 18:04:43 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:43 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:43 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Mar 16 18:04:43 super 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
Mar 16 18:04:43 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Mar 16 18:04:43 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Mar 16 18:04:43 super 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
Mar 16 18:04:43 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
/* note */ had to take out some stuff because post was too long /* note */
insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Mar 16 18:04:43 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:43 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:43 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Mar 16 18:04:43 super 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
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
Mar 16 18:04:48 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Mar 16 18:04:48 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Mar 16 18:04:48 super 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
Mar 16 18:04:48 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Mar 16 18:04:48 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:48 super kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 18:04:48 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Mar 16 18:04:48 super 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
Mar 16 18:04:48 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Mar 16 18:04:48 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Mar 16 18:04:48 super 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
Mar 16 18:04:48 super insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Mar 16 18:04:50 super dhcpcd[290]: timed out waiting for a valid DHCP server response
Mar 16 18:04:50 super dhcpcd[350]: recvfrom: Network is down
Mar 16 18:08:53 super kernel: Did not find a Sony CDU-535 drive
Mar 16 18:08:53 super insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.o.gz: init_module: Input/output error
Mar 16 18:08:53 super insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.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
Mar 16 18:08:53 super insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.o.gz: insmod block-major-24 failed
Mar 16 18:09:58 super insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: init_module: Input/output error
Mar 16 18:09:58 super insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.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
Mar 16 18:09:58 super insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
