[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: SATA+ IDE DVD-Writer crash, and missing /dev/fd0



[please include my email address in any replies]

Hi,
Thanks for your help, its working, read on for the details and one final question.

testing, and unstable both have the same kernel in "stable" which am
already running:

http://packages.debian.org/unstable/base/kernel-image-2.6-k7

would a newer kernel use something other than ide-scsi for SATA drive
access?  I am not sure how my root would be mountable if I remove
ide-scsi from initrd, or if etch/sid remove ide-scsi from their initrd.

SATA never used ide-scsi.

ok, I will try and remove it.  initrd.img-2.6.8-2-k7 contains:

# cat  loadmodules
modprobe -k  vesafb > /dev/null 2>&1
modprobe -k  fbcon 2> /dev/null
modprobe -k  unix 2> /dev/null
modprobe -k  sata_via
modprobe -k  sg
modprobe -k  sd_mod
modprobe -k  ide-scsi
modprobe -k  sr_mod


What is the -k mode? This is not listed on any man page.  or is the
initrd modprobe a different program?

are sg, sd_mod and sr_mod not also for scsi?  What do they do in
particular please? I see details of sr_mod and sg being used for "cdrom"
when booting up, whereas sd_mod is used for "disc".

This is how I mounted it, but I could not write to it, it said the
cramfs file was read-only.  Is there a doc on how I can modify the initrd?

I decided just to copy the files out, and make a new cramfs archive.

# mount -o loop,rw initrd.img-2.6.8-2-k7 i

# cp -dpR * ~/initrd/
cp: will not create hard link `/root/initrd/devfs' to directory
`/root/initrd/dev2'
cp: will not create hard link `/root/initrd/keyscripts' to directory
`/root/initrd/dev2'
cp: will not create hard link `/root/initrd/mnt' to directory
`/root/initrd/dev2'
cp: will not create hard link `/root/initrd/proc' to directory
`/root/initrd/dev2'
cp: will not create hard link `/root/initrd/sys' to directory
`/root/initrd/dev2'
cp: will not create hard link `/root/initrd/tmp' to directory
`/root/initrd/dev2'
cp: will not create hard link `/root/initrd/var' to directory
`/root/initrd/dev2'

I dont see what the problem is, there is no link or hardlink in the
package, and why is it compared with dev2?

These are what I need, and it appears this cp has lost some of them now:

bin   dev   devfs  keyscripts  linuxrc       loadmodules  proc  script
 sys  usr
bin2  dev2  etc    lib         linuxrc.conf  mnt          sbin  scripts
 tmp  var

# mkdir devfs keyscripts mnt proc sys tmp var


I removed sr_mod and ide_scsi from loadmodules

#cd ..
# mkcramfs initrd initrd.img-2.6.8-2-k7_no_ide_scsi_2


ok, that worked. I now have /dev/hda and can read CD-ROMs and DVD-ROMs


# cdrecord dev=ATA: -scanbus
Cdrecord-Clone 2.01.01a01 (i686-pc-linux-gnu) Copyright (C) 1995-2004
J�g Schilling
NOTE: this version of cdrecord is an inofficial (modified) release of
cdrecord
      and thus may have bugs that are not present in the original version.
      Please send bug reports and support requests to
<cdrtools@packages.debian.org>.
      The original author should not be bothered with problems of this
version.

cdrecord: Warning: Running on Linux-2.6.8-2-k7
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
cdrecord: Warning: Linux-2.6.8 introduced incompatible interface changes.
cdrecord: Warning: SCSI transport does no longer work for suid root
programs.
cdrecord: Warning: if cdrecord fails, try to run it from a root account.
scsidev: 'ATA:'
devname: 'ATA'
scsibus: -1 target: -1 lun: -1
Warning: Using badly designed ATAPI via /dev/hd* interface.
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
scsibus0:
        0,0,0     0) '_NEC    ' 'DVD_RW ND-2500A ' '1.06' Removable CD-ROM
        0,1,0     1) *
        0,2,0     2) *
        0,3,0     3) *
        0,4,0     4) *
        0,5,0     5) *
        0,6,0     6) *
        0,7,0     7) *


Is there a fix which will work as a normal user?

I used growisofs and that burned fine! :)

btw, is there a way I can burn in "verified" mode? I would like the
program to read back each sector at the end and check it matches what
was burnt etc.

Kind regards
JG



Reply to: