Click to See Complete Forum and Search --> : [SOLVED] kernel 2.6 and ide-scsi
jerryvb
05-14-2005, 12:48 PM
Does anybody know if the broken ide-scsi issue has been fixed in the 2.6 kernel series? I am currently running 2.6.10 on Slackware 10.1 and ide-scsi is not working. From what I've been able to find out on the web, it still isn't fixed, but I was just wondering if anybody knew for sure.
Thanks
je_fro
05-14-2005, 02:52 PM
I don't think it will ever be fixed. We burn our cd's with /dev/hdc or whatever now.
phlipant
05-14-2005, 04:45 PM
2.6 was never broken, it used a different format. Instead of
cdrecord -v -force -eject dev=0,0,0 /isos/damnsmall-0.4.4.iso
it uses
cdrecord -v -force -eject dev=/dev/hdc /isos/damnsmall-0.4.4.iso
phlipant
05-14-2005, 04:48 PM
P.S. ide-scsi does not exist anymore, it is all done in the kernel now.
jerryvb
05-14-2005, 07:59 PM
Aha, okay. So how do I get my kernel to see my LiteOn cd writer at hdd? My cd writer is connected to ide channel 1 as a slave. Here's my ide setup:
ide 0,0 = 80GB hard drive
ide 0,1 = 80GB hard drive
ide 1,0 = cd/dvd drive
ide 1,1 = cd writer
I checked /dev and I don't have an hdd device. Can I create one?
I just recently upgraded the kernel from 2.4.29 to 2.6.10. With 2.4.29 I had an hdd device and cd burning with k3b worked fine.
I would go beck to 2.4.29, but I need the 2.6 kernel for the new motherboard that I just recently got.
je_fro
05-14-2005, 08:41 PM
make sure you don't have hdd=ide-scsi in grub.conf or lilo.conf, then post back with the output from:
cdrecord -scanbus dev=ATAPI
mine gives this:
je_fro@speedy je_fro $ cdrecord -scanbus dev=ATAPI
Cdrecord-Clone 2.01 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
on-the-fly encryption (version 1.0-rc1) built-in, (C) 2004,2005 Maximilian Decker
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 <burbon04 at gmx.de>.
For more information please see http://burbon04.gmxhome.de/linux/CDREncryption.html.
The original author should not be bothered with problems of this version.
cdrecord: Warning: Running on Linux-2.6.11-gentoo-r7
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
scsidev: 'ATAPI'
devname: 'ATAPI'
scsibus: -2 target: -2 lun: -2
Warning: Using ATA Packet interface.
Warning: The related Linux kernel interface code seems to be unmaintained.
Warning: There is absolutely NO DMA, operations thus are slow.
Using libscg version 'schily-0.8'.
scsibus0:
0,0,0 0) 'LITE-ON ' 'DVDRW SOHW-1633S' 'BS0C' Removable CD-ROM
0,1,0 1) 'LITE-ON ' 'COMBO SOHC-5232K' 'NK0G' Removable CD-ROM
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
jerryvb
05-14-2005, 10:35 PM
Thanks je_fro. I already found this:
http://www.linuxsa.org.au/pipermail/linuxsa/2004-March/066290.html
I did:
1) in lilo.conf replaced hdd=ide-scsi with hdd=ide-cd
2) reran lilo
3) rebooted
4) ran cdrecord dev=ATA -scanbus and got this:
bash-3.00# cdrecord dev=ATA -scanbus
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
cdrecord: Warning: Running on Linux-2.6.10
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
scsidev: 'ATA'
devname: 'ATA'
scsibus: -2 target: -2 lun: -2
Warning: Using badly designed ATAPI via /dev/hd* interface.
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
scsibus1:
1,0,0 100) 'TOSHIBA ' 'DVD-ROM SD-M1502' '1012' Removable CD-ROM
1,1,0 101) 'LITE-ON ' 'LTR-52246S ' '6S0D' Removable CD-ROM
1,2,0 102) *
1,3,0 103) *
1,4,0 104) *
1,5,0 105) *
1,6,0 106) *
1,7,0 107) *
bash-3.00# cdrecord dev=ATA -scanbus
4) Brought up k3b and now it recognized hdd, the LiteOn cdrw drive
5) burnt a few files to a cd-rw disc in tao mode
The burning process seemed to be successful. At least k3b said it was. But, now I cannot get the newly burned cdrw disc to mount. I have added this line in fstab:
/dev/hdd /mnt/cdrw iso9660 noauto/owner/users/ro/exec 0 0
So, now what's wrong? I cannot get the newly burnt cdrw disc to mount, even as root???
When I try to mount hdd I get this:
bash-3.00# mount /dev/hdd
mount: block device /dev/hdd is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/hdd,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
bash-3.00#
Thanks
jerryvb
05-14-2005, 10:39 PM
Okay, my bad. If I do:
#mount /dev/hdd /mnt/cdrw
it mounts the newly burnt cdrw disc just fine.
Thanks for your help je_fro!!!
Hope this helps someone else.
jerry