problems installing with 'writemaster' CDROM
Folks, I've a new machine 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. Thanks, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems installing with 'writemaster' CDROM
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. Have you tried to boot a live CD like Knoppix or Ubuntu? If this boots OK the output of lspci -vv lsmod would help identify the correct modules to load. Thanks, Michael HTH Wackojacko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems installing with 'writemaster' CDROM
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. Okay, there's more info below > > 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. > > Have you tried to boot a live CD like Knoppix or Ubuntu? If this boots > OK the output of > > lspci -vv > lsmod > > would help identify the correct modules to load. > > I've not had the opportunity to boot from a live CD but it came with Fedora installed so here's output of those commands plus stuff about CDROM from the fedora boot/dmesg: Script started on Sat 28 Jul 2007 04:20:34 PM BST ]0;[EMAIL PROTECTED]:[EMAIL PROTECTED] ~]$ su Password: ]0;[EMAIL PROTECTED]:/home/[EMAIL PROTECTED] chris]# ls [Kpci 0[K0[K-vv bash: lspci: command not found ]0;[EMAIL PROTECTED]:/home/[EMAIL PROTECTED] chris]# /sbub[K[Kin/lspci -cc[K[Kvv 00:00.0 Host bridge: Intel Corporation 82Q963/Q965 Memory Controller Hub (rev 02) Subsystem: Intel Corporation Unknown device 4f43 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- Capabilities: [40] Express Root Port (Slot+) IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s unlimited, L1 unlimited Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- Device: MaxPayload 128 bytes, MaxReadReq 128 bytes Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 1 Link: Latency L0s <1us, L1 <4us Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch- Link: Speed 2.5Gb/s, Width x0 Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug+ Surpise+ Slot: Number 1, PowerLimit 10.00 Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- Slot: AttnInd Unknown, PwrInd Unknown, Power- Root: Correctable- Non-Fatal- Fatal- PME- Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+ Address: fee0300c Data: 4169 Capabilities: [90] Subsystem: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 Capabilities: [a0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot +,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- Capabilities: [40] Express Root Port (Slot+) IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s unlimited, L1 unlimited Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- Device: MaxPayload 128 bytes, MaxReadReq 128 bytes Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 2 Link: Latency L0s <256ns, L1 <4us Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch- Link: Speed 2.5Gb/s, Width x1 Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug+ Surpise+ Slot: Number 2, PowerLimit 10.00 Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- Slot: AttnInd Unknown, PwrInd Unknown, Power- Root: Correctable- Non-Fatal- Fatal- PME- Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+ Address: fee0300c Data: 4171 Capabilities: [90] Subsystem: Intel Corporation 82801H (ICH
Re: problems installing with 'writemaster' CDROM
On Sat, 2007-07-28 at 15:55 +0100, Peter Hillier-Brook wrote: > michael wrote: > > Folks, I've a new machine 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. > > It may not be relevant, but I've had installation problems in the past with > Etch, where the CD-ROM I booted from was not the first in the system. It > booted > fine, but then the installer later went looking for its disk in the first > drive. > If you now have 2 CD drives??? Peter, thanks for the thought but only 1 CD drive... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems installing with 'writemaster' CDROM
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 :00:1f.5: MAP [ P0 P2 P1 P3 ] ACPI: PCI Interrupt :00:1f.5[A] -> GSI 19 (level, low) -> IRQ 19 PCI: Setting latency timer of device :00:1f.5 to 64 scsi2 : ata_piix scsi3 : ata_piix ata3: SATA max UDMA/133 cmd 0x00012128 ctl 0x0001214e bmdma 0x000120f0 irq 19 ata4: SATA max UDMA/133 cmd 0x00012120 ctl 0x0001214a bmdma 0x000120f8 irq 19 ACPI: PCI Interrupt :02:00.0[A] -> GSI 17 (level, low) -> IRQ 17 PCI: Setting latency timer of device :02:00.0 to 64 scsi4 : pata_marvell scsi5 : pata_marvell ata5: PATA max UDMA/100 cmd 0x00011018 ctl 0x00011026 bmdma 0x00011000 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-ROMTSSTcorp CD/DVDW SH-S182M SB03 PQ: 0 ANSI: 5 device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED] 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 :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 :00:19.0[A] -> GSI 20 (level, low) -> IRQ 20 PCI: Setting latency timer of device :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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems installing with 'writemaster' CDROM
michael wrote: iTCO_wdt 20625 0 iTCO_vendor_support12741 1 iTCO_wdt snd_page_alloc 19025 2 snd_hda_intel,snd_pcm i2c_core 35777 1 i2c_i801 rtc_cmos 17017 0 sr_mod 26853 0 cdrom 44009 1 sr_mod sg 45673 0 dm_snapshot25609 0 dm_zero10817 0 dm_mirror 30785 0 dm_mod 68785 9 dm_multipath,dm_snapshot,dm_zero,dm_mirror pata_marvell 16449 0 ata_piix 25413 3 ata_generic17221 0 libata137201 3 pata_marvell,ata_piix,ata_generic sd_mod 37441 5 scsi_mod 168697 4 sr_mod,sg,libata,sd_mod ext3 141905 2 jbd73009 1 ext3 mbcache18249 1 ext3 ehci_hcd 42957 0 ohci_hcd 30405 0 uhci_hcd 34401 0 It would appear from this, and other info in subsequent e-mails, that you need to load the 'ata_piix' module. When the install stalls do Ctrl+Alt+F2 to get to another terminal and 'modprobe ata_piix'. Apologies if you have already tried this. There is a possibility that the etch kernel is not new enough for this MB, what kernel does fedora run on? If this is the case you may need a custom installer, google is your friend here. HTH Wackojacko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems installing with 'writemaster' CDROM
On Sat, 2007-07-28 at 18:03 +0100, Wackojacko wrote: > michael wrote: > > > > iTCO_wdt 20625 0 > > iTCO_vendor_support12741 1 iTCO_wdt > > snd_page_alloc 19025 2 snd_hda_intel,snd_pcm > > i2c_core 35777 1 i2c_i801 > > rtc_cmos 17017 0 > > sr_mod 26853 0 > > cdrom 44009 1 sr_mod > > sg 45673 0 > > dm_snapshot25609 0 > > dm_zero10817 0 > > dm_mirror 30785 0 > > dm_mod 68785 9 > > dm_multipath,dm_snapshot,dm_zero,dm_mirror > > pata_marvell 16449 0 > > ata_piix 25413 3 > > ata_generic17221 0 > > libata137201 3 pata_marvell,ata_piix,ata_generic > > sd_mod 37441 5 > > scsi_mod 168697 4 sr_mod,sg,libata,sd_mod > > ext3 141905 2 > > jbd73009 1 ext3 > > mbcache18249 1 ext3 > > ehci_hcd 42957 0 > > ohci_hcd 30405 0 > > uhci_hcd 34401 0 > > It would appear from this, and other info in subsequent e-mails, that > you need to load the 'ata_piix' module. When the install stalls do > Ctrl+Alt+F2 to get to another terminal and 'modprobe ata_piix'. > Apologies if you have already tried this. I hadn't tried that particular module, but doesn't help :( > There is a possibility that the etch kernel is not new enough for this > MB, what kernel does fedora run on? If this is the case you may need a > custom installer, google is your friend here. 2.6.22.1-33.fc7 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems installing with 'writemaster' CDROM
michael wrote: On Sat, 2007-07-28 at 18:03 +0100, Wackojacko wrote: michael wrote: iTCO_wdt 20625 0 iTCO_vendor_support12741 1 iTCO_wdt snd_page_alloc 19025 2 snd_hda_intel,snd_pcm i2c_core 35777 1 i2c_i801 rtc_cmos 17017 0 sr_mod 26853 0 cdrom 44009 1 sr_mod sg 45673 0 dm_snapshot25609 0 dm_zero10817 0 dm_mirror 30785 0 dm_mod 68785 9 dm_multipath,dm_snapshot,dm_zero,dm_mirror pata_marvell 16449 0 ata_piix 25413 3 ata_generic17221 0 libata137201 3 pata_marvell,ata_piix,ata_generic sd_mod 37441 5 scsi_mod 168697 4 sr_mod,sg,libata,sd_mod ext3 141905 2 jbd73009 1 ext3 mbcache18249 1 ext3 ehci_hcd 42957 0 ohci_hcd 30405 0 uhci_hcd 34401 0 It would appear from this, and other info in subsequent e-mails, that you need to load the 'ata_piix' module. When the install stalls do Ctrl+Alt+F2 to get to another terminal and 'modprobe ata_piix'. Apologies if you have already tried this. I hadn't tried that particular module, but doesn't help :( There is a possibility that the etch kernel is not new enough for this MB, what kernel does fedora run on? If this is the case you may need a custom installer, google is your friend here. 2.6.22.1-33.fc7 That's probably the reason then if the box is very new. Look for a custom installer or, if the box is not mission critical, try the testing installer which should have a newer kernel. HTH Wackojacko. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems installing with 'writemaster' CDROM
On Mon, 2007-07-30 at 19:50 +0100, Wackojacko wrote: > michael wrote: > > On Sat, 2007-07-28 at 18:03 +0100, Wackojacko wrote: > >> michael wrote: > >> > >> > >>> iTCO_wdt 20625 0 > >>> iTCO_vendor_support12741 1 iTCO_wdt > >>> snd_page_alloc 19025 2 snd_hda_intel,snd_pcm > >>> i2c_core 35777 1 i2c_i801 > >>> rtc_cmos 17017 0 > >>> sr_mod 26853 0 > >>> cdrom 44009 1 sr_mod > >>> sg 45673 0 > >>> dm_snapshot25609 0 > >>> dm_zero10817 0 > >>> dm_mirror 30785 0 > >>> dm_mod 68785 9 > >>> dm_multipath,dm_snapshot,dm_zero,dm_mirror > >>> pata_marvell 16449 0 > >>> ata_piix 25413 3 > >>> ata_generic17221 0 > >>> libata137201 3 pata_marvell,ata_piix,ata_generic > >>> sd_mod 37441 5 > >>> scsi_mod 168697 4 sr_mod,sg,libata,sd_mod > >>> ext3 141905 2 > >>> jbd73009 1 ext3 > >>> mbcache18249 1 ext3 > >>> ehci_hcd 42957 0 > >>> ohci_hcd 30405 0 > >>> uhci_hcd 34401 0 > >> It would appear from this, and other info in subsequent e-mails, that > >> you need to load the 'ata_piix' module. When the install stalls do > >> Ctrl+Alt+F2 to get to another terminal and 'modprobe ata_piix'. > >> Apologies if you have already tried this. > > > > I hadn't tried that particular module, but doesn't help :( > > > > > >> There is a possibility that the etch kernel is not new enough for this > >> MB, what kernel does fedora run on? If this is the case you may need a > >> custom installer, google is your friend here. > > > > 2.6.22.1-33.fc7 > > > > > That's probably the reason then if the box is very new. Look for a > custom installer or, if the box is not mission critical, try the testing > installer which should have a newer kernel. It's been a while, but I've now used debootstrap to get 2.6 onto said box and can boot into Debain - hooray! However, it doesn't seem to be recognising the CD drive... [EMAIL PROTECTED]:~$ lsscsi [0:0:0:0]diskATA ST3500630NS 3.AE /dev/sda [1:0:0:0]diskATA ST3750640NS 3.AE /dev/sdb Under Fedora, sr_mod was giving /dev/sr0 as the drive but there's no such device under Debian (I modprobe sr_mod after booting...) Any ideas? Thanks, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Debian4 network install woes [WAS: problems installing with 'writemaster' CDROM]
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 :00:1f.5: MAP [ P0 P2 P1 P3 ] ACPI: PCI Interrupt :00:1f.5[A] -> GSI 19 (level, low) -> IRQ 19 PCI: Setting latency timer of device :00:1f.5 to 64 scsi2 : ata_piix scsi3 : ata_piix ata3: SATA max UDMA/133 cmd 0x00012128 ctl 0x0001214e bmdma 0x000120f0 irq 19 ata4: SATA max UDMA/133 cmd 0x00012120 ctl 0x0001214a bmdma 0x000120f8 irq 19 ACPI: PCI Interrupt :02:00.0[A] -> GSI 17 (level, low) -> IRQ 17 PCI: Setting latency timer of device :02:00.0 to 64 scsi4 : pata_marvell scsi5 : pata_marvell ata5: PATA max UDMA/100 cmd 0x00011018 ctl 0x00011026 bmdma 0x00011000 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-ROMTSSTcorp CD/DVDW SH-S182M SB03 PQ: 0 ANSI: 5 device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED] 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 :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 :00:19.0[A] -> GSI 20 (level, low) -> IRQ 20 PCI: Setting latency timer of device :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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian4 network install woes [WAS: problems installing with 'writemaster' CDROM]
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 :00:1f.5: MAP [ P0 P2 P1 P3 ] > ACPI: PCI Interrupt :00:1f.5[A] -> GSI 19 (level, low) -> IRQ 19 > PCI: Setting latency timer of device :00:1f.5 to 64 > scsi2 : ata_piix > scsi3 : ata_piix > ata3: SATA max UDMA/133 cmd 0x00012128 ctl 0x0001214e > bmdma 0x000120f0 irq 19 > ata4: SATA max UDMA/133 cmd 0x00012120 ctl 0x0001214a > bmdma 0x000120f8 irq 19 > ACPI: PCI Interrupt :02:00.0[A] -> GSI 17 (level, low) -> IRQ 17 > PCI: Setting latency timer of device :02:00.0 to 64 > scsi4 : pata_marvell > scsi5 : pata_marvell > ata5: PATA max UDMA/100 cmd 0x00011018 ctl 0x00011026 > bmdma 0x00011000 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-ROMTSSTcorp CD/DVDW SH-S182M SB03 PQ: 0 > ANSI: 5 > device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: > [EMAIL PROTECTED] > 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 :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 :00:19.0[A] -> GSI 20 (level, low) -> IRQ 20 > PCI: Setting latency timer of device :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, r
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 :00:1f.5: MAP [ P0 P2 P1 P3 ] ACPI: PCI Interrupt :00:1f.5[A] -> GSI 19 (level, low) -> IRQ 19 PCI: Setting latency timer of device :00:1f.5 to 64 scsi2 : ata_piix scsi3 : ata_piix ata3: SATA max UDMA/133 cmd 0x00012128 ctl 0x0001214e bmdma 0x000120f0 irq 19 ata4: SATA max UDMA/133 cmd 0x00012120 ctl 0x0001214a bmdma 0x000120f8 irq 19 ACPI: PCI Interrupt :02:00.0[A] -> GSI 17 (level, low) -> IRQ 17 PCI: Setting latency timer of device :02:00.0 to 64 scsi4 : pata_marvell scsi5 : pata_marvell ata5: PATA max UDMA/100 cmd 0x00011018 ctl 0x00011026 bmdma 0x00011000 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-ROMTSSTcorp CD/DVDW SH-S182M SB03 PQ: 0 ANSI: 5 device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED] 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 :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 :00:19.0[A] -> GSI 20 (level, low) -> IRQ 20 PCI: Setting latency timer of device :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] sd