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

Re: Debian4 network install woes [WAS: problems installing with 'writemaster' CDROM]



michael wrote:
On Sat, 2007-07-28 at 18:01 +0100, michael wrote:
On Sat, 2007-07-28 at 14:47 +0100, Wackojacko wrote:
michael wrote:
Folks, I've a new machine
Its likely that the machine has more bearing on this problem than the CDROM itself. We need more information regarding the Motherboard and in particular the IDE or SATA chip the drive is connected to.

with a "writemaster" CDROM drive. When trying
to install Debian 4.0 from iso image burnt to CD, it initially
recognises the CD and starts the installation but fails at the screen
where the CD drive is to be recognised (for continuing the
installation). I've tried various module/device combos but all to no
avail. I've looked about on Google but not come up with a working
solution.

Has anybody else successfully uses this CDROM drive to install Debian,
or have suggestions on how I can determine a working module/device
combo. Please let me know if you need any further information.
here's some more info (snippets from 'dmesg'):
sd 1:0:0:0: [sdb] Attached SCSI disk
ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ]
ACPI: PCI Interrupt 0000:00:1f.5[A] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1f.5 to 64
scsi2 : ata_piix
scsi3 : ata_piix
ata3: SATA max UDMA/133 cmd 0x0000000000012128 ctl 0x000000000001214e
bmdma 0x00000000000120f0 irq 19
ata4: SATA max UDMA/133 cmd 0x0000000000012120 ctl 0x000000000001214a
bmdma 0x00000000000120f8 irq 19
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:02:00.0 to 64
scsi4 : pata_marvell
scsi5 : pata_marvell
ata5: PATA max UDMA/100 cmd 0x0000000000011018 ctl 0x0000000000011026
bmdma 0x0000000000011000 irq 17
ata6: DUMMY
BAR5:00:00 01:7F 02:22 03:CA 04:00 05:00 06:00 07:00 08:00 09:00 0A:00
0B:00 0C:01 0D:00 0E:00 0F:00 ata5.00: ATAPI: TSSTcorpCD/DVDW SH-S182M, SB03, max UDMA/33
ata5.00: configured for UDMA/33
scsi 4:0:0:0: CD-ROM            TSSTcorp CD/DVDW SH-S182M SB03 PQ: 0
ANSI: 5
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised:
dm-devel@redhat.com
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.

sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: Attached scsi generic sg1 type 0
scsi 4:0:0:0: Attached scsi generic sg2 type 5
sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 4:0:0:0: Attached scsi CD-ROM sr0
rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month
iTCO_vendor_support: vendor-support=0
ACPI: PCI Interrupt 0000:06:03.0[A] -> GSI 19 (level, low) -> IRQ 19
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.01 (21-Jan-2007)
iTCO_wdt: Found a ICH8DO TCO device (Version=2, TCOBASE=0x0460)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
Copyright (c) 1999-2006 Intel Corporation.
ACPI: PCI Interrupt 0000:00:19.0[A] -> GSI 20 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:19.0 to 64
Floppy drive(s): fd0 is 1.44M
parport_pc 00:09: reported by Plug and Play ACPI
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
FDC 0 is a National Semiconductor PC87306

cdrom: sr0: mrw address space DMA selected
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
SELinux: initialized (dev sr0, type iso9660), uses genfs_contexts


As W-J, suggested, I've tried a Ubuntu installation CD which does indeed
detect and use the CDROM okay. Here's a snippet of the syslog:
Jul 30 14:05:42 kernel: [    3.554527] scsi 4:0:0:0: CD-ROM
TSSTcorp CD/DVDW SH-S182M SB03 PQ: 0 ANSI: 5
Jul 30 14:05:42 kernel: [    3.562154] SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
Jul 30 14:05:42 kernel: [    3.562163] sda: Write Protect is off
Jul 30 14:05:42 kernel: [    3.562165] sda: Mode Sense: 00 3a 00 00
Jul 30 14:05:42 kernel: [    3.562174] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jul 30 14:05:42 kernel: ce sda: 976773168 512-byte hdwr sectors (500108 MB)
Jul 30 14:05:42 kernel: [    3.562208] sda: Write Protect is off
Jul 30 14:05:42 kernel: [    3.562209] sda: Mode Sense: 00 3a 00 00
Jul 30 14:05:42 kernel: [    3.562217] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jul 30 14:05:42 kernel: [    3.562220]  sda: sda1 sda2
Jul 30 14:05:42 kernel: [    3.581569] sd 0:0:0:0: Attached scsi disk sda
Jul 30 14:05:42 kernel: [    3.581647] SCSI device sdb: 1465149168 512-byte hdwr sectors (750156 MB)
Jul 30 14:05:42 kernel: [    3.581653] sdb: Write Protect is off
Jul 30 14:05:42 kernel: [    3.581654] sdb: Mode Sense: 00 3a 00 00
Jul 30 14:05:42 kernel: [    3.581663] SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jul 30 14:05:42 kernel: [    3.581685] SCSI device sdb: 1465149168 512-byte hdwr sectors (750156 MB)
Jul 30 14:05:42 kernel: [    3.581690] sdb: Write Protect is off
Jul 30 14:05:42 kernel: [    3.581692] sdb: Mode Sense: 00 3a 00 00
Jul 30 14:05:42 kernel: [    3.581700] SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jul 30 14:05:42 kernel: [    3.581702]  sdb: sdb1
Jul 30 14:05:42 kernel: [    3.598588] sd 1:0:0:0: Attached scsi disk sdb
Jul 30 14:05:42 kernel: [    3.600403] sd 0:0:0:0: Attached scsi generic sg0 type 0
Jul 30 14:05:42 kernel: [    3.600470] sd 1:0:0:0: Attached scsi generic sg1 type 0
Jul 30 14:05:42 kernel: [    3.600539] sr 4:0:0:0: Attached scsi generic sg2 type 5
Jul 30 14:05:42 kernel: [    3.604923] sr0: scsi3-mmc drive: 32x/40x writer dvd-ram cd/rw xa/form2 cdda tray
Jul 30 14:05:42 kernel: [    3.604925] Uniform CD-ROM driver Revision: 3.20
Jul 30 14:05:42 kernel: [    3.605010] sr 4:0:0:0: Attached scsi CD-ROM sr0


(not 100% sure that's all the relevant info...)

any ideas? I've tried all I can think of and Googled endlessly...

Thanks
Michael


What kernel?

OK another option is to debootstrap (google for more info). You can boot Ubuntu (maybe even from FC I'm not sure) and install debian etch then update the kernel (if this is what's causing the problem) with one from backports (www.backports.org?) or compiling from sources. You can use debian sources from sid and kernel-package (make-kpkg command).

HTH

Wackojacko



Reply to: