LinuxQuestions.org - mount trouble after kernel upgrade

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - mount trouble after kernel upgrade (https://www.linuxquestions.org/questions/slackware-14/mount-trouble-after-kernel-upgrade-504705/)

mount trouble after kernel upgrade

Hi folks,

Hardware - Dell C600 laptop, 1GHz, 512MHz.
CDRom module.

I recently installed the 2.6.17.13 Kernel from /extra. Everything looked fine until I tried to mount a cd. After trying different options it still wont mount. The thing that gets me is that when I boot into the 2.4.33.3 Kernel I can mount a cdrom with no problems with the same fstab file and permissions in /dev/hdc.

Anybody have any idea why I can mount a cdrom with the 2.4 kernel but not with the 2.6.:scratch:

problem with modules???
have you instaled the modules of 2.6 kernels?/
http://rkrishna.tp.googlepages.com/slackerbasics#alt

Quote:

upgrade kernel...not compulsory...maybe

you will learn more if you compile a kernel, first time it will take some time
infact i have a short into to kernel compile, in my signature

Yes I have modules installed. I also have a usb iomega zip cdrw hooked up which I can mount.

may be errors, along with commands can help will you please post it(just select it from the terminal, place the mouse cursor on reply box, click on the "mouse scroll button", whatever is previously selected will be pasted)

Commands? Using the interface, click on hdc in system:/media. Mount window opens and just hangs. Relevant output of dmesg...

Quote:

ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
ide-cd: cmd 0x28 timed out
hdc: DMA interrupt recovery
hdc: lost interrupt
ide-cd: cmd 0x28 timed out
hdc: DMA interrupt recovery
hdc: lost interrupt
ide-cd: cmd 0x28 timed out
hdc: DMA interrupt recovery
hdc: lost interrupt

lost here....

output of lsmod...

Quote:

Module Size Used by
nls_utf8 1792 1
isofs 31160 1
zlib_inflate 16128 1 isofs
snd_seq_dummy 2820 0
snd_seq_oss 28928 0
snd_seq_midi_event 5888 1 snd_seq_oss
snd_seq 43984 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 6284 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 38048 0
snd_mixer_oss 15616 1 snd_pcm_oss
ipv6 223584 10
sg 26524 0
capability 3336 0
commoncap 5376 1 capability
lp 9800 0
parport_pc 24132 1
parport 30024 2 lp,parport_pc
pcspkr 2432 0
psmouse 34952 0
usb_storage 78528 1
pcmcia 30116 0
firmware_class 7424 1 pcmcia
shpchp 33816 0
evdev 8064 1
serio_raw 5252 0
snd_maestro3 20900 1
uhci_hcd 19724 0
snd_ac97_codec 86304 1 snd_maestro3
snd_ac97_bus 2048 1 snd_ac97_codec
snd_pcm 73736 3 snd_pcm_oss,snd_maestro3,snd_ac97_codec
snd_timer 19332 2 snd_seq,snd_pcm
snd_page_alloc 7560 1 snd_pcm
yenta_socket 23436 2
snd 43364 11 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_maestro3,snd_ac97_codec,snd_pcm,snd _timer
rsrc_nonstatic 10752 1 yenta_socket
i2c_piix4 7696 0
soundcore 7136 1 snd
pcmcia_core 34192 3 pcmcia,yenta_socket,rsrc_nonstatic
i2c_core 16528 1 i2c_piix4
intel_agp 19612 1
3c59x 38056 0
agpgart 28080 1 intel_agp
mii 4864 1 3c59x
reiserfs 239088 2

Try mounting it manually in a terminal and report any errors you get.

output of dmesg now...after attempting to open drive...

Quote:

dmesg
0: 0000000000100000 - 000000001ffdb000 (usable)
BIOS-e820: 000000001ffdb000 - 0000000020000000 (reserved)
BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
511MB LOWMEM available.
On node 0 totalpages: 131035
DMA zone: 4096 pages, LIFO batch:0
Normal zone: 126939 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP (v000 DELL ) @ 0x000f42f0
ACPI: RSDT (v001 DELL CPi R 0x27d20107 ASL 0x00000061) @ 0x1fff0000
ACPI: FADT (v001 DELL CPi R 0x27d20107 ASL 0x00000061) @ 0x1fff0400
ACPI: DSDT (v001 INT430 SYSFexxx 0x00001001 MSFT 0x0100000d) @ 0x00000000
ACPI: PM-Timer IO Port: 0x808
Allocating PCI resources starting at 30000000 (gap: 20000000:dfe00000)
Built 1 zonelists
Kernel command line: BOOT_IMAGE=Linux261713 ro root=302
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Detected 1002.446 MHz processor.
Using pmtmr for high-res timesource
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 515268k/524140k available (2201k kernel code, 8276k reserved, 764k data, 184k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 2006.14 BogoMIPS (lpj=4012297)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 0383f9ff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel Pentium III (Coppermine) stepping 0a
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 0k freed
ACPI: setting ELCR to 0200 (from 0820)
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 406k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfc13e, last bus=1
Setting up standard PCI resources
ACPI: Subsystem revision 20060127
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
PCI quirk: region 0800-083f claimed by PIIX4 ACPI
PCI quirk: region 0840-084f claimed by PIIX4 SMB
PIIX4 devres B PIO at 00e0-00e7
PIIX4 devres C PIO at 0850-085f
Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
ACPI: Power Resource [PADA] (on)
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
PCI: Bridge: 0000:00:01.0
IO window: e000-efff
MEM window: fd000000-feffffff
PREFETCH window: f8000000-fbffffff
PCI: Bus 2, cardbus bridge: 0000:00:03.0
IO window: 00001000-000010ff
IO window: 00001400-000014ff
PREFETCH window: 30000000-31ffffff
MEM window: 32000000-33ffffff
PCI: Bus 6, cardbus bridge: 0000:00:03.1
IO window: 00001800-000018ff
IO window: 00001c00-00001cff
PREFETCH window: 34000000-35ffffff
MEM window: 36000000-37ffffff
PCI: Enabling device 0000:00:03.0 (0000 -> 0003)
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:03.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
PCI: Enabling device 0000:00:03.1 (0000 -> 0003)
ACPI: PCI Interrupt 0000:00:03.1[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
Dell Latitude C600 machine detected. Mousepad Resume Bug workaround hopefully not needed.
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Limiting direct PCI/PCI transfers.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
vesafb: framebuffer at 0xf8000000, mapped to 0xe0880000, using 1536k, total 8192k
vesafb: mode is 1024x768x8, linelength=1024, pages=9
vesafb: protected mode interface info at c000:6240
vesafb: scrolling: redraw
vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 0000:00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x0860-0x0867, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x0868-0x086f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: IC25N020ATDA04-0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: CD-ROM CDR_U200, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 39070080 sectors (20003 MB) w/1806KiB Cache, CHS=38760/16/63, UDMA(33)
hda: cache flushes not supported
hda: hda1 hda2 hda3
hdc: ATAPI 16X CD-ROM drive, 128kB Cache, DMA
Uniform CD-ROM driver Revision: 3.20
ide-floppy driver 0.99.newide
libata version 1.20 loaded.
usbmon: debugfs is not available
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: automatically using best checksumming function: pIII_sse
pIII_sse : 2020.000 MB/sec
raid5: using function: pIII_sse (2020.000 MB/sec)
raid6: int32x1 339 MB/s
raid6: int32x2 406 MB/s
raid6: int32x4 279 MB/s
raid6: int32x8 269 MB/s
raid6: mmxx1 1000 MB/s
raid6: mmxx2 1233 MB/s
raid6: sse1x1 984 MB/s
raid6: sse1x2 1229 MB/s
raid6: using algorithm sse1x2 (1229 MB/s)
md: raid6 personality registered for level 6
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
ACPI wakeup devices:
LID PBTN PCI0 UAR1 USB0 MPCI
ACPI: (supports S0 S1 S3 S4 S5)
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
input: AT Translated Set 2 keyboard as /class/input/input0
ReiserFS: hda2: found reiserfs format "3.6" with standard journal
ReiserFS: hda2: using ordered data mode
ReiserFS: hda2: journal params: device hda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda2: checking transaction log (hda2)
ReiserFS: hda2: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Trying to move old root to /initrd ... okay
Freeing unused kernel memory: 184k freed
Adding 779112k swap on /dev/hda1. Priority:-1 extents:1 across:779112k
Linux agpgart interface v0.101 (c) Dave Jones
ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:00:10.0: 3Com PCI 3c556 Laptop Tornado at e082cc00.
agpgart: Detected an Intel 440BX Chipset.
agpgart: AGP aperture is 64M @ 0xf4000000
piix4_smbus 0000:00:07.3: Found 0000:00:07.3 device
ACPI: PCI Interrupt 0000:00:03.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
Yenta: CardBus bridge found at 0000:00:03.0 [1028:00b1]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:03.0, mfunc 0x01261222, devctl 0x64
USB Universal Host Controller Interface driver v3.0
Yenta: ISA IRQ mask 0x04b8, PCI irq 11
Socket status: 30000006
ACPI: PCI Interrupt 0000:00:03.1[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
Yenta: CardBus bridge found at 0000:00:03.1 [1028:00b1]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:03.1, mfunc 0x01261222, devctl 0x64
Yenta: ISA IRQ mask 0x04b8, PCI irq 11
Socket status: 30000006
ACPI: PCI Interrupt 0000:00:07.2[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
uhci_hcd 0000:00:07.2: UHCI Host Controller
uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:07.2: irq 11, io base 0x0000dce0
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
usb 1-1: new full speed USB device using uhci_hcd and address 2
usb 1-1: configuration #1 chosen from 1 choice
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
cs: IO port probe 0xc00-0xcff: excluding 0xcf8-0xcff
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0x800-0x80f: clean.
cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x100-0x3af: excluding 0x200-0x207 0x378-0x37f
cs: IO port probe 0xa00-0xaff: clean.
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
cs: IO port probe 0xc00-0xcff: excluding 0xcf8-0xcff
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0x800-0x80f: clean.
cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x100-0x3af: excluding 0x200-0x207 0x378-0x37f
cs: IO port probe 0xa00-0xaff: clean.
input: PC Speaker as /class/input/input1
input: ImPS/2 Generic Wheel Mouse as /class/input/input2
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
lp0: using parport0 (polling).
lp0: console ready
Capability LSM initialized
Vendor: IOMEGA Model: ZIPCD 650 USB Rev: I1.1
Type: CD-ROM ANSI SCSI revision: 00
sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
sr 0:0:0:0: Attached scsi CD-ROM sr0
usb-storage: device scan complete
sr 0:0:0:0: Attached scsi generic sg0 type 5
ReiserFS: hda3: found reiserfs format "3.6" with standard journal
ReiserFS: hda3: using ordered data mode
ReiserFS: hda3: journal params: device hda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda3: checking transaction log (hda3)
ReiserFS: hda3: Using r5 hash to sort names
ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
eth0: setting full-duplex.
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
eth0: no IPv6 routers present
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
ide-cd: cmd 0x28 timed out
hdc: DMA interrupt recovery
hdc: lost interrupt
ide-cd: cmd 0x28 timed out
hdc: DMA interrupt recovery
hdc: lost interrupt
ide-cd: cmd 0x28 timed out
hdc: DMA interrupt recovery
hdc: lost interrupt
ide-cd: cmd 0x28 timed out
hdc: DMA interrupt recovery
hdc: lost interrupt
ide-cd: cmd 0x28 timed out
hdc: DMA interrupt recovery
hdc: lost interrupt
ide-cd: cmd 0x28 timed out
hdc: DMA interrupt recovery
hdc: lost interrupt
ide-cd: cmd 0x28 timed out
hdc: DMA interrupt recovery
hdc: lost interrupt
ide-cd: cmd 0x28 timed out
hdc: DMA interrupt recovery
hdc: lost interrupt
ide-cd: cmd 0x28 timed out
hdc: DMA interrupt recovery
hdc: lost interrupt
ide-cd: cmd 0x28 timed out
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
end_request: I/O error, dev hdc, sector 56
Buffer I/O error on device hdc, logical block 7
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
end_request: I/O error, dev hdc, sector 56
Buffer I/O error on device hdc, logical block 7
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
end_request: I/O error, dev hdc, sector 56
Buffer I/O error on device hdc, logical block 7
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
end_request: I/O error, dev hdc, sector 120
Buffer I/O error on device hdc, logical block 15
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
end_request: I/O error, dev hdc, sector 120
Buffer I/O error on device hdc, logical block 15
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
end_request: I/O error, dev hdc, sector 120
Buffer I/O error on device hdc, logical block 15
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
ide-cd: cmd 0x28 timed out
hdc: DMA interrupt recovery
hdc: lost interrupt
ide-cd: cmd 0x28 timed out
hdc: DMA interrupt recovery
hdc: lost interrupt

Quote:

Try mounting it manually in a terminal and report any errors you get

Please remind me of the exact command, that used to mounting using the desktop interface.

"mnt /dev/hdc /media/fstab-assigned-directory-name"

or

"mnt /media/fstab-assigned-directory-name"

man mnt

okay tried it and got...

Quote:

:~$ mnt /dev/hdc /mnt/cdrom
-bash: mnt: command not found
:~$ man mnt
No manual entry for mnt

Now trying with the command...
mount /dev/hdc /mnt/cdrom

and it is hanging...

After ten minutes trying to mount this is the output...

Quote:

mount /dev/hdc /mnt/cdrom
mount: you must specify the filesystem type

oops, sorry about that. Still half asleep here. Yeah the command is mount.

Quote:

Originally Posted by tamtam

After ten minutes trying to mount this is the output...

What does your fstab look like? (A little more awake now after some much needed coffee)

fstab is the same as the one which mounts hdc successfully with the 2.4 kernel...

Quote:

/dev/hda1 swap swap defaults 0 0
/dev/hda2 / reiserfs defaults 1 1
/dev/hda3 /home reiserfs defaults 1 2
/dev/hdc /mnt/cdrom auto noauto,user,ro 0 0
/dev/sr0 /mnt/cdrecorder auto noauto,user 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0

Quote:

Originally Posted by tamtam

fstab is the same as the one which mounts hdc successfully with the 2.4 kernel...

Looks ok to me.

Try the command "mount /mnt/cdrom" and see what happens.

BTW, what kind of disk do you have in the CDROM?

Within slack disk 2 /extras is the directory /udev-alternate-versions...

the answer maybe within the README file...

Quote:

From the desk of Patrick Volkerding, Mon Aug 7 16:08:08 CDT 2006.

Hello,

Some people have reported problems with the newer style udev, and I've seen
some myself. However, newer kernels are about to require a very recent udev
so it was time to upgrade to the latest, in spite of the possible pain.

One issue that's being reported is that udev sometimes chooses a different
module that would be desired. In those cases, add the module that you don't
want to the blacklist (with udev-096 or higher this would be
/etc/modprobe.d/blacklist), and then edit /etc/rc.d/rc.modules to load the
module that you want.

In some cases where you want to run udev it might be easier to run one of
these old versions than to fight with it. Feel free to try them if you run
into problems with the latest. Just "upgrade" to one of these with
upgradepkg, copy rc.S and rc.M over the ones in /etc/rc.d/, and finally
go into /etc/rc.d and move rc.udev.new to rc.udev (and make sure that it
is executable). Also, check to make sure that there aren't new config or
rules files that need to be moved into place. You can find these with:

find /etc -name "*.new"

Good luck! :-)

Pat

I was thinking of copying the appropriate module for the cdrom drive from the 2.4 kernel to the 2.6. Any thoughts anyone...

It's the same no matter what cdrom I have in the drive...at the moment it's slack disk 2.

Since I can mount the drive with the 2.4 kernel, I think it maybe using the wrong driver for 2.6. I have no idea as yet on how to rectify this or where to begin.

Did you try the command "mount /mnt/cdrom"?

One way to determine if the wrong module is being loaded is to boot the working kernel and do a lsmod and then the nonworking one and compare it's lsmod to the original to spot any differences.

You seem to be getting nowhere fast, so I will offer up a wild-ass guess.

One difference between 2.4 and 2.6 kernels in slackware 11.0 is that hotplug runs with 2.4 and not with 2.6 kernels (udev only). I suggest booting with 2.4.33.3 and print out the output of lsmod. Then boot with 2.6 and compare loaded modules. You may note a difference that you can create a work around for when booting with a 2.6 kernel and no hotplug.

Along these lines:

Quote:

One issue that's being reported is that udev sometimes chooses a different
module that would be desired. In those cases, add the module that you don't
want to the blacklist (with udev-096 or higher this would be
/etc/modprobe.d/blacklist), and then edit /etc/rc.d/rc.modules to load the
module that you want.

I do not think that copying a module as you seem to be suggesting will work.

will have a go tomorrow, been all day trying to find a solution to this.

Okay, still trying to resolve this problem with my cdrom drive and mounting.

Quote:

lsmod on the 2.4.33.3 kernel

Module Size Used by Not tainted
snd-seq-oss 23104 0 (unused)
snd-seq-midi-event 3208 0 [snd-seq-oss]
snd-seq 33552 2 [snd-seq-oss snd-seq-midi-event]
snd-seq-device 3716 0 [snd-seq-oss snd-seq]
snd-pcm-oss 28928 0 (unused)
snd-mixer-oss 11928 0 [snd-pcm-oss]
usb-storage 63520 0
uhci 23804 0 (unused)
usbcore 56812 1 [usb-storage uhci]
snd-maestro3 14052 0
snd-ac97-codec 68160 0 [snd-maestro3]
snd-pcm 52804 0 [snd-pcm-oss snd-maestro3 snd-ac97-codec]
snd-timer 13168 0 [snd-seq snd-pcm]
snd 34304 0 [snd-seq-oss snd-seq-midi-event snd-seq snd-seq-device snd-pcm-oss snd-mixer-oss snd-maestro3 snd-ac97-codec snd-pcm snd-timer]
snd-page-alloc 4980 0 [snd-seq-oss snd-seq snd-seq-device snd-mixer-oss snd-pcm snd-timer snd]
soundcore 3300 5 [snd]
3c59x 25520 0
ds 6612 2
yenta_socket 10532 2
pcmcia_core 39492 0 [ds yenta_socket]
ide-scsi 9392 0
agpgart 45092 0 (unused)

Quote:

lsmod on the 2.6.17.13 kernel

Module Size Used by
nls_iso8859_1 3968 1
nls_cp437 5632 1
vfat 10112 1
fat 45980 1 vfat
snd_seq_dummy 2820 0
snd_seq_oss 28928 0
snd_seq_midi_event 5888 1 snd_seq_oss
snd_seq 43984 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 6284 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 38048 0
snd_mixer_oss 15616 1 snd_pcm_oss
ipv6 223584 10
sg 26524 0
capability 3336 0
commoncap 5376 1 capability
lp 9800 0
parport_pc 24132 1
parport 30024 2 lp,parport_pc
pcspkr 2432 0
psmouse 34952 0
snd_maestro3 20900 0
pcmcia 30116 0
evdev 8064 1
usb_storage 78528 1
shpchp 33816 0
snd_ac97_codec 86304 1 snd_maestro3
firmware_class 7424 1 pcmcia
snd_ac97_bus 2048 1 snd_ac97_codec
serio_raw 5252 0
snd_pcm 73736 3 snd_pcm_oss,snd_maestro3,snd_ac97_codec
snd_timer 19332 2 snd_seq,snd_pcm
snd_page_alloc 7560 1 snd_pcm
snd 43364 9 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_maestro3,snd_ac97_codec,snd_pcm,snd _timer
uhci_hcd 19724 0
soundcore 7136 1 snd
i2c_piix4 7696 0
i2c_core 16528 1 i2c_piix4
intel_agp 19612 1
3c59x 38056 0
mii 4864 1 3c59x
agpgart 28080 1 intel_agp
yenta_socket 23436 2
rsrc_nonstatic 10752 1 yenta_socket
pcmcia_core 34192 3 pcmcia,yenta_socket,rsrc_nonstatic
reiserfs 239088 2

Needing a experts help here to dicipher the above. I am looking for the module used in conjunction with my cdrom drive, bearing in mind this is a laptop. Any help will be welcomed.

Anybody? Been at this for 3 days now.

Nothing jumps out there. shpchp can sometime be problem. I had to blacklist it on a Compaq laptop I used to have.

Just a thought, but is your user in the cdrom group?

i got you.

Quote:

/dev/hdc /mnt/cdrom auto noauto,user,ro 0 0
/dev/sr0 /mnt/cdrecorder auto noauto,user 0 0

where is ro in the /dev/sr0 line??

do you have 2 seperate cd drives???
IF U HAVE 1 CD DRIVE
scsi emulation made /dev/sr0 and the corresponding divice is changed. so you need to mount /mnt/cdrecorder, not /mntcdrom
(always remove unwanted links in /dev)
when you were using 2.4 kernel u need scsi emu and your devices has to be changed, if there is only one drive tehn, do
rm -rf /dev/cdrom
ln -sf /dev/sr0 /dev/cdrom
(this has to be done in 2.4 kernel, if you have a single cd drive)

also while using a 2.6 kernel, you dont need append line in lilo remove that for 2.6 kernel section

IF U HAVE 2 CD DRIVES
do $ls -al /dev |grep -i cd
$ls -al /dev |grep -i dvd
remove all unwanted links, make new links there.
http://rkrishna.tp.googlepages.com/slackerbasics#cd

http://rkrishna.tp.googlepages.com/s...basics#scsiemu

rkrishna says...

i got you.
/dev/hdc /mnt/cdrom auto noauto,user,ro 0 0
/dev/sr0 /mnt/cdrecorder auto noauto,user 0 0
where is ro in the /dev/sr0 line??
dev/sr0 is a cdrw drive...it is the one that works okay in both 2.4 and 2.6

do you have 2 seperate cd drives???
YES...
I have a laptop, with a cdrom drive module in place, this works in 2.4, but not in 2.6.
I also have a usb iomegaZIP cdrw drive attached, which works in both 2.4 and 2.6.

rkrishna says

Quote:

IF U HAVE 2 CD DRIVES
do $ls -al /dev |grep -i cd
$ls -al /dev |grep -i dvd
remove all unwanted links, make new links there.

All very well, but this would have to be repeated every time I boot into 2.6.

Tried it once, and guess what it made no difference. Still unable to mount a cdrom in 2.6 which I can mount easily enough in 2.4 kernel.

5 days at this now and still cant figure out the solution.

How do you blacklist a module like masonm suggested.

sorry i cant help more but some suggestions, actually i didnt ment the earlier commands . really it was"$ls -al /dev |grep -i hdc"
do "$dmesg |grep -i hdc" without any cd inserted.
do "$dmesg |grep -i cd" that msut endup within 2-3 lines as it is for sr0

Quote:

All very well, but this would have to be repeated every time I boot into 2.6.

when i install slackware there were many simlinks pointing towards teh drive,(it was causing problems) so i removed all simlinks, created new, editted fstab.

Quote:

Tried it once, and guess what it made no difference.

it is because your fstab has correct device entry not simlinks.
ur problem is not that. i went through yur dmesg, and i hope u were trying to mount a cd made from windows.
is there any append line in lilo. like append "hdc = ide-scsi"?? i dont think so.

try some more and i am givenup
1.try mount as root
2.put your slack cd and try!!
mount -t iso9660 /dev/hdc /mnt/cdrom
3.try oounting to some other moutn point like /home/name/mycd
mount -t iso9660 /dev/hdc /home/name/mycd
4.try mountin /dev/sr0 to /mnt/cdrom manually(just to check the permission)
i think $dmesg |grep -i hdc without any cd must give some info

sorry tht i couldnt help regards

rkrishna says...

Quote:

when i install slackware there were many simlinks pointing towards teh drive,(it was causing problems) so i removed all simlinks, created new, editted fstab.

I also edited /dev by deleting all symlinks pointing to hdc and sr0, I then added my own links to the appropriate drives. Unfortunately, after a reboot, the new kernel recreates the old symlinks and permissions, so therefore I have to go through the whole process again.

Quote:

I do not know exactly what you mean here. fstab points to the correct symlinks I created in dev. More than likely the cd I am trying to mount will have been burned using software running under windows, including the slack install disks. There is no append line in lilo.

rkrishna says...

Quote:

Results:

Quote:

1. Cannot mount a cdrom in hdc as root.
2. Comment mount: block device /dev/hdc is write protected, mounting read-only and cursor sat below this comment for an eternity, eventually had to eject the cdrom after 20 minutes of the device whirling.
3. Comment mount: block device /dev/hdc is write protected, mounting read-only and cursor sat below this comment for an eternity, eventually had to eject the cdrom after 20 minutes of the device whirling.
4. Mounts cdrom in device sr0 correctly.

Output of dmesg | grep -i hdc

Quote:

ide1: BM-DMA at 0x0868-0x086f, BIOS settings: hdc:DMA, hdd:pio
hdc: CD-ROM CDR_U200, ATAPI CD/DVD-ROM drive
hdc: ATAPI 16X CD-ROM drive, 128kB Cache, DMA
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
end_request: I/O error, dev hdc, sector 120
isofs_fill_super: bread failed, dev=hdc, iso_blknum=30, block=30
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
end_request: I/O error, dev hdc, sector 84
isofs_fill_super: bread failed, dev=hdc, iso_blknum=21, block=21
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
end_request: I/O error, dev hdc, sector 76
isofs_fill_super: bread failed, dev=hdc, iso_blknum=19, block=19

Does anyone think installing a newer 2.18 kernel would fix this. I seem to be getting nowhere fast. A definite fix would be installing a different distro of course :)

Quote:

Does anyone think installing a newer 2.18 kernel would fix this.

no idea, whether it is something to do with acpi.

instead you can try test26.s kernel, rather going for huge

1.disable dma support, i think u can do it by hdparm(hdparm -d0 /dev/hdc)check this, i am not sure

dont go for someother linux that wont help, if slackware cant, others cant.

Are you sure its an issure only in Slack? I mean did you try using it in Windows or something? cos maybe after you installed 2.6 kernel, by some freak chance, some wires of your drive might have gone loose.

Yes it's only in slack and specifically the 2.6.17.13 kernel as I still have the 2.4.33.3 kernel and it still mounts no problem there. I previously had Suse and a 2.6 kernel on the same machine and it worked okay.

did you try disable dma, as i suggested?

sorry rkrishna, at work at the moment, try it when I get home.

rkrishna you are the man....

Quote:

1.disable dma support, i think u can do it by hdparm(hdparm -d0 /dev/hdc)check this, i am not sure

At last YOU have the cdrom drive working.

Thanks for your patience.

One quick question, will have to run this command every time I boot into the 2.16 kernel.

This is a CRC error:
DriveReady SeekComplete Error
Try 'modprobe crc' before mounting

What exactly is a CRC error and what is the fix.

result of...

Quote:

modprobe crc
FATAL: Module crc not found.

The significance?