-   Linux - Newbie (
-   -   modprobe error in dmesg under slackware 9.0 (

rnf 09-10-2003 07:15 AM

modprobe error in dmesg under slackware 9.0
i am rather new to linux so do not really understand the error with modprobe that appears in the output of dmesg. could anybody explain this? here is my dmesg (i did not truncate it much as i was not sure what was important). thanks a lot.

Linux version 2.4.20 (root@midas) (gcc version 3.2.2) #2 Mon Mar 17 22:02:15 PST 2003
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000018000000 (usable)
BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
384MB LOWMEM available.
On node 0 totalpages: 98304
zone(0): 4096 pages.
zone(1): 94208 pages.
zone(2): 0 pages.
Kernel command line: BOOT_IMAGE=Slackware ro root=345 hdc=ide-scsi hdd=ide-scsi
ide_setup: hdc=ide-scsi
ide_setup: hdd=ide-scsi
Initializing CPU#0
Detected 498.757 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 996.14 BogoMIPS
Memory: 385904k/393216k available (1733k kernel code, 6928k reserved, 568k data, 112k init, 0k highmem)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU: After generic, caps: 0383f9ff 00000000 00000000 00000000
CPU: Common caps: 0383f9ff 00000000 00000000 00000000
CPU: Intel Pentium III (Katmai) stepping 03
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xfcaee, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router PIIX [8086/7110] at 00:07.0
Limiting direct PCI/PCI transfers.
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Diskquotas version dquot_6.4.0 initialized
Journalled Block Device driver loaded
pty: 512 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10e
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA
hda: WDC WD800BB-00CAA1, ATA DISK drive
hdb: WDC WD1200BB-60CJA1, ATA DISK drive
hdc: LITE-ON LTR-52327S, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
blk: queue c0388784, I/O limit 4095Mb (mask 0xffffffff)
hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63, UDMA(33)
blk: queue c03888c0, I/O limit 4095Mb (mask 0xffffffff)
hdb: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=14593/255/63, UDMA(33)
ide-floppy driver 0.99.newide
Partition check:
hda: hda1 hda2
hdb: hdb1 hdb2 < hdb5 hdb6 hdb7 > hdb4
hdb4: <openbsd: hdb8 hdb9 hdb10 hdb11 hdb12 hdb13 >
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
RAMDISK driver initialized: 16 RAM disks of 7777K size 1024 blocksize
loop: loaded (max 8 devices)
ide-floppy driver 0.99.newide
SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
raid5: measuring checksumming speed
8regs : 825.200 MB/sec
32regs : 497.600 MB/sec
pIII_sse : 1002.400 MB/sec
pII_mmx : 1116.000 MB/sec
p5_mmx : 1148.400 MB/sec
raid5: using function: pIII_sse (1002.400 MB/sec)
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
LVM version 1.0.5+(22/07/2002)
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 112k freed
Adding Swap: 755012k swap-space (priority -1)
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,69), internal journal
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: LITE-ON Model: LTR-52327S Rev: QS06
Type: CD-ROM ANSI SCSI revision: 02
Vendor: LITEON Model: DVD-ROM LTD163D Rev: GHR3
Type: CD-ROM ANSI SCSI revision: 02
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
Attached scsi CD-ROM sr1 at scsi0, channel 0, id 1, lun 0
sr0: scsi3-mmc drive: 52x/52x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12
sr1: scsi3-mmc drive: 4x/48x cd/rw xa/form2 cdda tray

Lenny 09-10-2003 08:57 AM

You mean these?
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2

Scsi is used for expensive hard drives and cd-roms. If you have a "normal" computer you won't need this. *Unless* you've been trying to emulate an scsi interface to be able to use a cd-writer?

Anyway, if your hard drives and cd-roms work, you have nothing to worry about.

320mb 09-10-2003 09:16 AM

/sbin/modprobe scsi------is enabled by default on Slackware install. goto /etc/rc.d/ an open rc.modules up in text editor and comment that particular line out, an Slack won't look for these devices when it boots up.

rnf 09-11-2003 06:34 PM

Thanks for the replies. The strange thing is that the command 'mount /dev/cdrom /mnt/cdrom' does not work. I have to type 'mount /dev/sr0 /mnt/cdrom' I am not sure if my burner will work properly as it claims that it is mounted read-only. I don't remember running into this problem before. Does anybody have any ideas? Here is my fstab file :

/dev/hdb7 swap swap defaults 0 0
/dev/hdb10 swap swap defaults 0 0
/dev/hdb9 / ext3 defaults 1 1
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0

Do I just need to change the 'ro' in '/dev/cdrom' to 'rw'?

Looking_Lost 09-11-2003 07:14 PM

if you've only one cd device just change the




my line is

/dev/sr0 /mnt/cdwriter iso9660 noauto,user,rw 0 0

and for my dvd just the normal

/dev/cdrom /mnt/cdrom iso9660 noauto,user,ro 0 0

venyin 10-08-2003 09:15 PM

>Thanks for the replies. The strange thing is that the
>command 'mount /dev/cdrom /mnt/cdrom' does not work. I have >to type 'mount /dev/sr0 /mnt/cdrom' I am not sure if my burner >will work properly as it claims that it is mounted read-only. I >don't remember running into this problem before. Does anybody
>have any ideas? Here is my fstab file

well remember that /dev/cdrom it is usually the symlink for the real device, could be /dev/hdc... etc... so the common thing to do it is just ck if it that's a symlink with a simple
$: ls -al /dev/cdrom
so if it is just do make a symlink

about the burner... i recommend you to compile the scsi emulation support (under IDE ATA and ATAPI block devices) module, then under SCSI support the modules SCSI CD-ROM Support and SCSI generic support (could be as a module), and this one (SCSI generic support) will load the module called sg.o, when you are going to burn something... and your cdrw will usually be /dev/sg0, but the /dev/sr0 will work cuz it is the scsi emulation for the cdrom (to use it as the burner)... and if you want to probe the cdrw to work just do a simple

$: cdrecord -scanbus

anyway i recommend you to read the CDRW How To.

good luck,

All times are GMT -5. The time now is 03:19 AM.