LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-01-2006, 02:18 PM   #1
ccoffee
Member
 
Registered: Mar 2003
Location: Lake City, South Carolina
Distribution: Slackware 15 and current
Posts: 58

Rep: Reputation: 7
Loaded Slackware 10.2 but can not access CD or SATA drives


I use Athlon XP2200 with 1Gb Ram, IDE and SATA hard drives with IDE CD-RW (Lite On). I upgraded from Slackware 10.1 to 10.2 but can not access my CD now and can not see the SATA drive(s).

""dmesg output for Slackware 10.2 -- 01016006""
Linux version 2.4.31 (root@tree) (gcc version 3.3.5) #6 Sun Jun 5 19:04:47
PDT 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003dff0000 (usable)
BIOS-e820: 000000003dff0000 - 000000003dff3000 (ACPI NVS)
BIOS-e820: 000000003dff3000 - 000000003e000000 (ACPI data)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
Warning only 896MB will be used.
Use a HIGHMEM enabled kernel.
896MB LOWMEM available.
On node 0 totalpages: 229376
zone(0): 4096 pages.
zone(1): 225280 pages.
zone(2): 0 pages.
Kernel command line: BOOT_IMAGE=Linux ro root=306 hdc=ide-scsi
ide_setup: hdc=ide-scsi
Initializing CPU#0
Detected 1788.454 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 3565.15 BogoMIPS
Memory: 904376k/917504k available (1832k kernel code, 12740k reserved, 607k data,
120k init, 0k highmem)
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode cache hash table entries: 65536 (order: 7, 524288 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 65536 (order: 6, 262144 bytes)
Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
CPU: CLK_CTL MSR was 6003d22f. Reprogramming to 2003d22f
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After generic, caps: 0383fbff c1c3fbff 00000000 00000000
CPU: Common caps: 0383fbff c1c3fbff 00000000 00000000
CPU: AMD Athlon(tm) XP 2200+ stepping 01
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 (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xfb4e0, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Via IRQ fixup
PCI: Using IRQ router VIA [1106/3177] at 00:11.0
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Disk quotas vdquot_6.5.1
Journalled Block Device driver loaded
vesafb: framebuffer at 0xe0000000, mapped to 0xf880d000, size 1536k
vesafb: mode is 1024x768x8, linelength=1024, pages=40
vesafb: protected mode interface info at c000:6f20
vesafb: scrolling: redraw
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
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
PCI: Found IRQ 5 for device 00:09.0
PCI: Sharing IRQ 5 with 00:10.1
PCI: Found IRQ 10 for device 00:0a.0
PCI: Sharing IRQ 10 with 00:0b.0
PCI: Sharing IRQ 10 with 00:10.2
PCI: Sharing IRQ 10 with 00:11.5
Redundant entry in serial pci_table. Please send the output of
lspci -vv, this message (10b9,5459,14fe,9100)
and the manufacturer and name of serial board or modem board
to serial-pci-info@lists.sourceforge.net.
register_serial(): autoconfig failed
Real Time Clock Driver v1.10f
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 7777K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
VP_IDE: IDE controller at PCI slot 00:11.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci00:11.1
ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hdaMA, hdbio
ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdcMA, hddio
hda: WDC WD400EB-00CPF0, ATA DISK drive
blk: queue c03af460, I/O limit 4095Mb (mask 0xffffffff)
hdc: LITE-ON LTR-48246S, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 78165360 sectors (40021 MB) w/2048KiB Cache, CHS=4865/255/63, UDMA(100)
Partition check:
hda: hda1 hda2 < hda5 hda6 >
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 : 2563.600 MB/sec
32regs : 1716.800 MB/sec
pIII_sse : 4856.400 MB/sec
pII_mmx : 4185.200 MB/sec
p5_mmx : 5347.200 MB/sec
raid5: using function: pIII_sse (4856.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.8(17/11/2003)
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
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: 120k freed
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,6), internal journal
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 816M
agpgart: Detected Via Apollo Pro KM266 / KL266 chipset
agpgart: AGP aperture is 64M @ 0xe8000000
8139too Fast Ethernet driver 0.9.26
PCI: Found IRQ 10 for device 00:0b.0
PCI: Sharing IRQ 10 with 00:0a.0
PCI: Sharing IRQ 10 with 00:10.2
PCI: Sharing IRQ 10 with 00:11.5
eth0: RealTek RTL8139 at 0xf89bc000, 00:40:ca:52:ae:08, IRQ 10
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
NTFS driver v1.1.22 [Flags: R/O MODULE]
eth0: link up, 100Mbps, half-duplex, lpa 0x40A1
Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Intel ISA PCIC probe: not found.
Databook TCIC-2 PCMCIA probe: not found.
ds: no socket drivers loaded!
via82xx: Assuming DXS channels with 48k fixed sample rate.
Please try dxs_support=1 or dxs_support=4 option
and report if it works on your machine.
PCI: Found IRQ 10 for device 00:11.5
PCI: Sharing IRQ 10 with 00:0a.0
PCI: Sharing IRQ 10 with 00:0b.0
PCI: Sharing IRQ 10 with 00:10.2
PCI: Setting latency timer of device 00:11.5 to 64
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
PCI: Found IRQ 3 for device 00:10.3
ehci_hcd 00:10.3: VIA Technologies, Inc. USB 2.0
ehci_hcd 00:10.3: irq 3, pci mem f8aa7000
usb.c: new USB bus registered, assigned bus number 1
ehci_hcd 00:10.3: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
hub.c: USB hub found
hub.c: 6 ports detected
uhci.c: USB Universal Host Controller Interface driver v1.1
PCI: Found IRQ 11 for device 00:10.0
PCI: Sharing IRQ 11 with 00:08.0
uhci.c: USB UHCI at I/O 0xd400, IRQ 11
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 5 for device 00:10.1
PCI: Sharing IRQ 5 with 00:09.0
uhci.c: USB UHCI at I/O 0xd800, IRQ 5
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 10 for device 00:10.2
PCI: Sharing IRQ 10 with 00:0a.0
PCI: Sharing IRQ 10 with 00:0b.0
PCI: Sharing IRQ 10 with 00:11.5
uhci.c: USB UHCI at I/O 0xdc00, IRQ 10
usb.c: new USB bus registered, assigned bus number 4
hub.c: USB hub found
hub.c: 2 ports detected
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
PCI: Found IRQ 5 for device 00:09.0
PCI: Sharing IRQ 5 with 00:10.1
PCI parallel port detected: 9710:9835, I/O at 0xbc00(0x0)
parport1: PC-style at 0xbc00 [PCSPP,TRISTATE,EPP]
ttyS04 at port 0xb400 (irq = 5) is a 16550A
ttyS05 at port 0xb800 (irq = 5) is a 16550A
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
hub.c: new USB device 00:10.1-1, assigned address 2
usb.c: USB device 2 (vend/prod 0x4a9/0x2206) is not claimed by any active driver.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
hub.c: new USB device 00:10.1-2, assigned address 3
usb.c: USB device 3 (vend/prod 0x4a9/0x1056) is not claimed by any active driver.
pci_hotplug: PCI Hot Plug PCI Core version:
0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
hub.c: new USB device 00:10.0-1, assigned address 2
usb.c: USB device 2 (vend/prod 0x59b/0x33) is not claimed by any active driver.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
usb.c: registered new driver usbscanner
scanner.c: USB scanner device (0x04a9/0x2206) now attached to scanner0
scanner.c: 0.4.16:USB Scanner Driver
usb.c: registered new driver usblp
printer.c: usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid
0x04A9 pid 0x1056
printer.c: v0.13: USB Printer Device Class driver
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: IOMEGA Model: ZIP 100 Rev: 27.O
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
sda: Unit Not Ready, sense:
Current 00:00: sns = 70 2
ASC=3a ASCQ= 0
Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x12 0x00 0x00 0x00 0x00 0x3a
0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
sda : READ CAPACITY
failed.
sda : status = 1, message = 00, host = 0, driver = 08
Current sd00:00: sns = 70 2
ASC=3a ASCQ= 0
Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x12 0x00 0x00 0x00 0x00 0x3a
0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
sda : block size assumed to be 512 bytes, disk size 1GB.
sda: I/O error: dev 08:00, sector 0
I/O error: dev 08:00, sector 0
unable to read partition table
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
lp0: using parport0 (polling).
lp1: using parport1 (polling).

Also the lspci output is:
""lspci from System 010106""
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:08.0 RAID bus controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA
Controller (rev 02)
00:09.0 Serial controller: NetMos Technology PCI 9835 Multi-I/O Controller (rev 01)
00:0a.0 Modem: ALi Corporation SmartLink SmartPCI561 56k Modem
00:0b.0 Ethernet controller: Realtek Semiconductor co., Ltd. RTL-8139/8139C/8139C+ (rev
10)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00.10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00.10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx 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)
01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266]

Any ideas on what I am missing? I am pretty sure that the
"hdc = ide-scsi" is what is causing my problem (this is
not being loaded from LILO). How would I kill this from
loading?

Thanks
Chuck
 
Old 01-01-2006, 04:38 PM   #2
Carpo
Member
 
Registered: Aug 2003
Location: Somewhere
Distribution: Gentoo (for now)
Posts: 364

Rep: Reputation: 30
look @ /etc/lilo.conf

in there look for append="hdx=ide-scsi" (x being the letter of the cdrom drive) remove it from lilo save the changes and then type lilo at the prompt to update the changes
 
Old 01-02-2006, 07:42 AM   #3
ccoffee
Member
 
Registered: Mar 2003
Location: Lake City, South Carolina
Distribution: Slackware 15 and current
Posts: 58

Original Poster
Rep: Reputation: 7
Thanks, but as I stated initially, the /etc/lilo.conf does not have
any statement "hdc=ide-scsi". I had tried adding that in Slack 10.1
but never got it to work, and now Slack 10.2 is adding it somewhere
that I can not find. I have checked the /etc/lilo.conf file several
time, unless there is another instance of the file where I do not
know of.

chuck
 
Old 01-02-2006, 10:37 AM   #4
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,922
Blog Entries: 44

Rep: Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158
Quote:
Kernel command line: BOOT_IMAGE=Linux ro root=306 hdc=ide-scsi
ide_setup: hdc=ide-scsi
Hi,

You have the hdc=ide-scsi shown in your dmesg output. You are passing the parameters from your lilo.conf. If you edit the lilo.conf file and save/write, then you must update the lilo by using the lilo command. I use # lilo -v -t -b /dev/hda to test my lilo.conf file then remove the -t and issue lilo -v -b /dev/hda to update my lilo for my mbr on /dev/hda. Of course you will have to change the /dev/hda to your local device that has the mbr that you use.

You could look at your /dev/cdrom by issuing ;

#s -al /dev/cdrom
the output for mine;
lrwxrwxrwx 1 root root 8 2004-12-06 10:27 /dev/cdrom -> /dev/sr0

This shows a link to /dev/sr0 which is as it should be when using the ide-scsi mode.

If memory serves me the /etc/rc.d/rc.modules also starts the ide-scsi emulation. But you are issuing from lilo (dmesg output).

As for the SATA support, You have chosen the stock/bare.i 2.4.31 kernel. You should either compile your own or use the sata.i kernel available on install.


HTH!
 
Old 01-02-2006, 11:35 AM   #5
ccoffee
Member
 
Registered: Mar 2003
Location: Lake City, South Carolina
Distribution: Slackware 15 and current
Posts: 58

Original Poster
Rep: Reputation: 7
Thank you for the response. I believe my problem is that dmesg does show
the "hdc=ide-scsi" however, I can not find that anywhere in my etc/lilo.conf

this is the lilo.conf and it is identical in the lilo.conf~ file:
""LILO.CONF from the Slackware 10.2 System""010206
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot="/dev/hda"
message = /boot/boot_message.txt
prompt
timeout="2400"
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga="773"
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Windows bootable partition config begins

other = /dev/hda1
label="Windows"
table = /dev/hda
# Windows bootable partition config ends
# Linux bootable partition config begins
# image="/dev/hda1"

image = /boot/vmlinuz
root = /dev/hda6
label = Linux 2.4.31
read-only
# Linux bootable partition config ends
==================

I did try the #ls -al command and came up with the following:

root@darkstar:~# ls -al /dev/cdrom
lrwxrwxrwx 1 root root 8 2005-06-23 12:43 /dev/cdrom -> /dev/hdc
root@darkstar:~#

=======================
When I try the normal mount for /dev/cdrom
I receive the error that "mount: /dev/cdrom is not a valid block device"
I am still at a loss as to why the "hdc=ide-scsi" is coming up when
I can not find it in lilo.conf.

Appreciate the data on the SATA, I will have to go back to the CDs I
received from Slackware, as I do not recall the sata.i being on
the set.

thanks again for the help.
chuck


=======

Last edited by ccoffee; 01-02-2006 at 11:36 AM.
 
Old 01-02-2006, 12:53 PM   #6
ramen
Member
 
Registered: Nov 2002
Location: Yorkshire,England
Distribution: Slackware, Slamd64
Posts: 47

Rep: Reputation: 15
You should also edit /etc/rc.d/rc.modules #/sbin/modprobe ide-scsi
 
Old 01-02-2006, 03:17 PM   #7
ccoffee
Member
 
Registered: Mar 2003
Location: Lake City, South Carolina
Distribution: Slackware 15 and current
Posts: 58

Original Poster
Rep: Reputation: 7
Thanks ramen, making progress I guess. I did go into /etc/rc.d/rc.modules and
I did find the "/sbin/modprobe ide-scsi" and I put the "#" sign in front of it
to make it a comment. However after rebooting I am still getting the following:
"
Kernel command line: BOOT_IMAGE=Linux ro root=306 hdc=ide-scsi
ide_setup: hdc=ide-scsi
"

I still do not know where this is coming from, but I am pretty sure it is not
from lilo.conf and/or the /etc/rc.d/rc.modules - unless of couse the "#" is
not commenting the line out.
thanks again
Chuck
 
Old 01-02-2006, 11:13 PM   #8
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,922
Blog Entries: 44

Rep: Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158
Hi,

Did you issue the lilo command to update the mbr? Just having the lilo.conf without updating the boot it will continue to use the last update.

Since the dmesg shows that the hdc=ide-scsi you need to issue a lilo command with you new lilo.conf.
 
Old 01-03-2006, 03:59 PM   #9
ccoffee
Member
 
Registered: Mar 2003
Location: Lake City, South Carolina
Distribution: Slackware 15 and current
Posts: 58

Original Poster
Rep: Reputation: 7
Yes, I have used the following:

# /etc/lilo -v -b /dev/hda6

I usually do this each time I change the lilo.conf file for
any reason. This has not changed what is displayed by the
dmesg output "hdc=ide-scsi".

I do not think this is coming from lilo.conf file.

chuck
 
Old 01-04-2006, 02:20 PM   #10
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,922
Blog Entries: 44

Rep: Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158
Quote:
Originally Posted by ccoffee
Yes, I have used the following:

# /etc/lilo -v -b /dev/hda6

I usually do this each time I change the lilo.conf file for
any reason. This has not changed what is displayed by the
dmesg output "hdc=ide-scsi".

I do not think this is coming from lilo.conf file.

chuck
Hi,
This is coming from lilo.conf that was written before your present lilo.conf.

Your mbr would be on /dev/hda not /dev/hda6 since it is a partition on the /dev/hda.

The reason you still get the append is that you are showing it in your old lilo.conf update.

Code:
# Start LILO global section
 boot="/dev/hda"
Therefore your boot device is /dev/hda. Then issue the command;

lilo -v -t -b /dev/hda # this will test the lilo

then;

edit:
lilo -v -b /dev/hda #this will update the command

If you want /dev/hda6 to be a boot partition you will need to indicate or tell it to be in a lilo.conf then update the mbr.

You might want to look at;

http://www.slackbook.org/html/book.html#BOOTING

The whole book;

http://www.slackbook.org/html/book.html

If you have the slackware 10.2 cd set then the slackware book is on cd3.

HTH!

Last edited by onebuck; 01-04-2006 at 10:32 PM.
 
Old 01-04-2006, 02:58 PM   #11
ccoffee
Member
 
Registered: Mar 2003
Location: Lake City, South Carolina
Distribution: Slackware 15 and current
Posts: 58

Original Poster
Rep: Reputation: 7
First off, sorry for the command typo, it should have read /dev/hda.

However, I have tried your suggestions/commands:

lilo -v -t -b /dev/hda and
lilo -v -b /dev/hda

I still have the same problem as before.
(which is what I should have typed yesterday)

Also tried your suggestion:

lilo -v -b /dev/lilo #for updating the command however, I received the
following:
-----------
LILO version 22.5.9, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2004 John Coffman
Released 08-Apr-2004 and compliles at 00:18:50 on May 21, 2004.

Ignoring entry 'boot'
Warning: LBA32 addressing assumed
Fatal: raid_setup: stat("/dev/lilo")
-----------------------------------------

If lilo.conf is coming from an old version, I can not find the file.
I have checked both lilo.conf and lilo.conf~ in the /etc directory
and both are identical without the "append hdc=ide-scsi".

Thanks for the book info and will check that out next, just can not
use the CD on this machine with Slackware.
 
Old 01-04-2006, 04:09 PM   #12
ccoffee
Member
 
Registered: Mar 2003
Location: Lake City, South Carolina
Distribution: Slackware 15 and current
Posts: 58

Original Poster
Rep: Reputation: 7
SUCCESS!!!!
The slackware book is on cd3 (pdf) is a real gift.

What does not work on the system.

/sbin/lilo.

Dont know what, but I have checked lilo.conf and lilo.conf~ till I turned blue,
but no luck.

Sooo then tried "liloconfig" and ran the expert mode and tried the "recycle"
option, then received an error message that the lilo.conf was not good (?)
which I dont understand as it has worked very well for some time under
10.1......

Anyway, finally tried "liloconfig" "simple" and followed all the prompts and
reloaded the MBR. It Works... I now have the /dev/hdc back without the
"hdc=ide-scsi" which never worked. Wish I knew what the real problem was,
because I can read CDs on Slack but will not be able to write..

Next will need to learn to compile the 2.6 kernel

Thanks again to everyone.
Chuck
 
Old 01-04-2006, 04:16 PM   #13
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,922
Blog Entries: 44

Rep: Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158
Quote:
Originally Posted by ccoffee
lilo -v -b /dev/lilo #for updating the command however, I received
Hi,

Typo on my part, it should have read as ;

lilo -v -b /dev/hda

What the first did was to test the lilo.conf with a lilo -v -t -b /dev/hda # the -t is for test

When you issue the lilo comannd,
Can you show me output for the result of the lilo -v -b /dev/hda.

My thought you were using /dev/hda6 as a seperate partition for your /.

You can do this but the mbr is on the ide0 device unless told otherwise. You can do a bios change to set boot device if your bios supports the option.

When you did a liloconfig what option was selected? Superblock or MBR?

You could try liloconfig and choose to boot to floppy to test?

HTH!
 
Old 01-04-2006, 10:43 PM   #14
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,922
Blog Entries: 44

Rep: Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158
Quote:
Originally Posted by ccoffee
SUCCESS!!!!
The slackware book is on cd3 (pdf) is a real gift.

What does not work on the system.

/sbin/lilo.

Dont know what, but I have checked lilo.conf and lilo.conf~ till I turned blue,
but no luck.

Sooo then tried "liloconfig" and ran the expert mode and tried the "recycle"
option, then received an error message that the lilo.conf was not good (?)
which I dont understand as it has worked very well for some time under
10.1......

Anyway, finally tried "liloconfig" "simple" and followed all the prompts and
reloaded the MBR. It Works... I now have the /dev/hdc back without the
"hdc=ide-scsi" which never worked. Wish I knew what the real problem was,
because I can read CDs on Slack but will not be able to write..

Next will need to learn to compile the 2.6 kernel

Thanks again to everyone.
Chuck
Hi,

Chuck, glad to hear you got it working. For some reason you were not writing your lilo to the MBR. liloconfig helped you, great. I just don't like not knowing what actually was going on..
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
ich6r sata. ata_piix needs to be loaded twice. Legend1222 Linux - Hardware 3 03-22-2005 06:32 AM
Slackware 10 doesn't see SATA drives jayhel Slackware 15 12-20-2004 06:14 PM
sil680 (cmd680) modules loaded, but drives not available. SerfurJ Linux - Hardware 7 08-22-2004 01:27 PM
Installed RedHat9 on new ATA drive but now can't access other 2 WinXP SATA drives andrew-zaf Linux - Newbie 3 03-30-2004 08:42 AM
raid modules loaded but no drives mountable KevinClarke Linux - Hardware 0 02-12-2004 06:33 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:00 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration