Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Request for testing: CD/DVD writing on 2.6.9
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5, 6, 7  Next  
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
llsardonicll
Tux's lil' helper
Tux's lil' helper


Joined: 07 Oct 2004
Posts: 110

PostPosted: Fri Nov 19, 2004 9:36 pm    Post subject: Reply with quote

Seems i've figured out my xcdroast problem, i have to

Code:

chown root  /usr/lib/xcdroast-0.98/bin/xcdrwrap && chmod 4755 /usr/lib/xcdroast-0.98/bin/xcdrwrap


or xcdroast won't launch, once it's launced i can take off the suid bit and it runs perfectly


Last edited by llsardonicll on Sat Nov 20, 2004 9:43 pm; edited 1 time in total
Back to top
View user's profile Send private message
undrwater
Apprentice
Apprentice


Joined: 28 Jan 2003
Posts: 275
Location: Caucasia

PostPosted: Sat Nov 20, 2004 4:30 am    Post subject: Reply with quote

Tested burn...everything looked OK until the fixating process...

Code:
verify_command: rejected command e9
verify_command: rejected command e9
verify_command: rejected command ed
verify_command: rejected command e9
Info fld=0x3c72a4, Current sdb: sense key Recovered Error
ASC=18 ASCQ= a


I hear a clicking in the drive..and it doesn't stop.

Anything that I do that tries to access the drive will hang the system.

[EDIT]CD burned OK after reboot. Still a bit to pay for a successful burn... :roll: [/EDIT]
_________________
Open-mindedness is painful...


Last edited by undrwater on Sun Nov 21, 2004 5:15 am; edited 1 time in total
Back to top
View user's profile Send private message
serge
Apprentice
Apprentice


Joined: 05 Jan 2003
Posts: 177

PostPosted: Sat Nov 20, 2004 1:25 pm    Post subject: checking data Reply with quote

Hi

Using k3b-0.11.17, gentoo-dev-sources-2.6.9-r4, after burning the iso [the md5sum being correct], i always get an error at 99% when checking the data, no matter what length has the iso file. The burned iso file is always corrupted then.
I thought it came from my dvd burner so i tried a new one , and this problem still remains.

Any idea?

Thank you


Serge
Back to top
View user's profile Send private message
cbradney
Apprentice
Apprentice


Joined: 08 May 2003
Posts: 245
Location: Luxembourg

PostPosted: Mon Nov 22, 2004 11:38 am    Post subject: Reply with quote

On doing a test write to CDRW, 2 files, nothing special (2.6.9r4, k3b 0.11.17), fails as follows:

System
-----------------------
K3b Version:0.11.17
KDE Version: 3.3.1
QT Version: 3.3.3

cdrecord
-----------------------
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
TOC Type: 1 = CD-ROM
Using libscg version 'schily-0.8'.
Driveropts: 'burnfree'
/usr/bin/cdrecord: Warning: Running on Linux-2.6.9-gentoo-r4
/usr/bin/cdrecord: There are unsettled issues with Linux-2.5 and newer.
/usr/bin/cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
/usr/bin/cdrecord: Warning: Linux-2.6.8 introduced incompatible interface changes.
/usr/bin/cdrecord: Warning: SCSI transport does no longer work for suid root programs.
/usr/bin/cdrecord: Warning: if cdrecord fails, try to run it from a root account.
scsidev: '/dev/hdc'
devname: '/dev/hdc'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
SCSI buffer size: 64512
/usr/bin/cdrecord: Cannot allocate memory. Cannot get SCSI I/O buffer.

cdrecord comand:
-----------------------
/usr/bin/cdrecord -v gracetime=2 dev=/dev/hdc speed=24 -tao driveropts=burnfree -eject -data -tsize=7337s -

mkisofs
-----------------------
7337

mkisofs comand:
-----------------------
/usr/bin/mkisofs -gui -graft-points -volid K3b data project -volset -appid K3B THE CD KREATOR VERSION 0.11.17 (C) 2003 SEBASTIAN TRUEG AND THE K3B TEAM -publisher -preparer K3b - Version 0.11.17 -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-craig/k3bHIRvab.tmp -rational-rock -hide-list /tmp/kde-craig/k3bh0Mqoa.tmp -full-iso9660-filenames -iso-level 2 -path-list /tmp/kde-craig/k3bx4GGfc.tmp /home/craig/.kde3.3/share/apps/k3b/temp/dummydir0/
_________________
Scribus: Open Source Desktop Publishing http://www.scribus.net. Emerge it!
Back to top
View user's profile Send private message
Pylon
Retired Dev
Retired Dev


Joined: 17 Jan 2003
Posts: 279
Location: Cologne

PostPosted: Mon Nov 22, 2004 5:54 pm    Post subject: Reply with quote

Beside the usual rejected command 1e during fixating a DVD, I have no problems with my PowerPC and pegasos-dev-sources-2.6.9-r2.

Thanks a lot for leading out of the dark times for CD-writing. I nearly lost the interest for the media-optical herd and all the cd-writing-applications due to many bugs with problems that pointed to the changes in the kernel :roll:

I hope that this will get better now.
_________________
hacking is not a crime
Back to top
View user's profile Send private message
Thrain
Guru
Guru


Joined: 01 Sep 2003
Posts: 380

PostPosted: Mon Nov 22, 2004 8:23 pm    Post subject: Reply with quote

Excuse me, maybe I'm OT.
as long as I used gentoo-dev-sources-2.6.9-r3, I see that cdrecord switch down the writing speed from 40x (that's the maximum for my burner) to 12x, telling me that the selected speed (40x) is not supported by the burner.

I noticed that using either nitro-sources or development-sources (2.6.9) I don't have this problem.

Then... Is it possible that this problem is caused by your patch, dsd?

Thank you in advance.
_________________
Thrain

"...only astonishment knows..."
Back to top
View user's profile Send private message
Pylon
Retired Dev
Retired Dev


Joined: 17 Jan 2003
Posts: 279
Location: Cologne

PostPosted: Tue Nov 23, 2004 1:58 am    Post subject: Reply with quote

Thrain wrote:
as long as I used gentoo-dev-sources-2.6.9-r3, I see that cdrecord switch down the writing speed from 40x (that's the maximum for my burner) to 12x, telling me that the selected speed (40x) is not supported by the burner.


I can't confirm. Just tested to write a CD-R in k3b. Automatic speed detection switched to 40x (maximum speed). Everything went fine. Even the buffer is now shown :-)

Probably your CD-R tells the burner that it can only handle the maximum speed of 12x? I fall into this "trick" once, when I used an old blank CD-R...
_________________
hacking is not a crime
Back to top
View user's profile Send private message
bk0
Apprentice
Apprentice


Joined: 04 Jan 2004
Posts: 266

PostPosted: Tue Nov 23, 2004 2:14 am    Post subject: Reply with quote

Audio CD burning with cdrecord is extremely CPU intensive and results in literally dozens of buffer-underruns. This is on an Athlon XP 2600+, 768MB RAM and kernel 2.6.9-gentoo-r4.

Here's the bug report:
http://bugs.gentoo.org/show_bug.cgi?id=63040
Back to top
View user's profile Send private message
dsd
Developer
Developer


Joined: 30 Mar 2003
Posts: 2162
Location: nr London

PostPosted: Tue Nov 23, 2004 1:07 pm    Post subject: Reply with quote

cbradney wrote:
On doing a test write to CDRW, 2 files, nothing special (2.6.9r4, k3b 0.11.17), fails as follows:

please remove all suid bits (see the start of this thread)

Quote:
Excuse me, maybe I'm OT.
as long as I used gentoo-dev-sources-2.6.9-r3, I see that cdrecord switch down the writing speed from 40x (that's the maximum for my burner) to 12x, telling me that the selected speed (40x) is not supported by the burner.

I noticed that using either nitro-sources or development-sources (2.6.9) I don't have this problem.

Then... Is it possible that this problem is caused by your patch, dsd?

very unlikely. any rejected commands? could you please test with 2.6.9-r2 ?
_________________
http://dev.gentoo.org/~dsd
Back to top
View user's profile Send private message
cbradney
Apprentice
Apprentice


Joined: 08 May 2003
Posts: 245
Location: Luxembourg

PostPosted: Tue Nov 23, 2004 9:29 pm    Post subject: Reply with quote

dsd wrote:

please remove all suid bits (see the start of this thread)


Hey, cool. it works :) top stuff. Ok, It burnt at 4x, but it was a CDRW. Will try a real backup onto CDR tomorrow, hopefully at full speed.
_________________
Scribus: Open Source Desktop Publishing http://www.scribus.net. Emerge it!
Back to top
View user's profile Send private message
rapsure
Apprentice
Apprentice


Joined: 29 Apr 2004
Posts: 163
Location: Spanish Fork, Utah, U.S.

PostPosted: Wed Nov 24, 2004 7:40 pm    Post subject: SUID problems Reply with quote

I found that xcdwrap was set with the suid, and so I disabled that, and then I tried to burn a CD, and this is what I get with cdrecord.
Code:

brian@rapsure cdimage $ cdrecord dev=ATAPI:0,0,0 -sao -data SimCity3000_Unlimited.iso
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 J�rg Schilling
cdrecord: Warning: Running on Linux-2.6.10-rc2
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: Cannot allocate memory. WARNING: Cannot do mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: 'ATAPI:0,0,0'
devname: 'ATAPI'
scsibus: 0 target: 0 lun: 0
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'.
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   :
Vendor_info    : 'BENQ    '
Identifikation : 'DVD DD DW1620   '
Revision       : 'B7P9'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
cdrecord: This version of cdrecord does not include DVD-R/DVD-RW support code.
cdrecord: If you need DVD-R/DVD-RW support, ask the Author for cdrecord-ProDVD.
cdrecord: Free test versions and free keys for personal use are at ftp://ftp.berlios.de/pub/cdrecord/ProDVD/
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE
Supported modes:
cdrecord: Drive does not support SAO recording.
cdrecord: Illegal write mode for this drive.


This is the error message that I get regardless of what mode I put it in. From my previous post I reinstalled cdrtools so that it didn't have any patches. I get the same error message from cdrecord-ProDVD.
_________________
:) Hindi ko naintindihan, pakiulit.
Back to top
View user's profile Send private message
Thrain
Guru
Guru


Joined: 01 Sep 2003
Posts: 380

PostPosted: Wed Nov 24, 2004 7:54 pm    Post subject: Reply with quote

K3b tell me that "Medium or burner don't support 40x writing speed"... then maybe a medium-related problem: but the cdrs I bought are certified for burning at 52x speed! Can I bypass that limitation with some arguments to cdrecord (I checked the man page with no results) ?

Thank you
_________________
Thrain

"...only astonishment knows..."
Back to top
View user's profile Send private message
rapsure
Apprentice
Apprentice


Joined: 29 Apr 2004
Posts: 163
Location: Spanish Fork, Utah, U.S.

PostPosted: Wed Nov 24, 2004 8:26 pm    Post subject: kernel patch, and rejected command Reply with quote

I patched the kernel to report rejected commands, and so here it is:
Code:

Nov 24 13:23:07 [kernel] verify_command: rejected command 55


Now if I can just patch the kernel to allow that command I am pretty sure that it will allow me to burn cd's.
_________________
:) Hindi ko naintindihan, pakiulit.
Back to top
View user's profile Send private message
dsd
Developer
Developer


Joined: 30 Mar 2003
Posts: 2162
Location: nr London

PostPosted: Wed Nov 24, 2004 8:29 pm    Post subject: Reply with quote

it's not that simple.. 55 is already permitted by the kernel, but only for write access.

which software are you using? it needs to be patched to open the cdrom device node in O_RDWR mode... (most seemed to be using O_RDONLY before this situation came about)
_________________
http://dev.gentoo.org/~dsd
Back to top
View user's profile Send private message
rapsure
Apprentice
Apprentice


Joined: 29 Apr 2004
Posts: 163
Location: Spanish Fork, Utah, U.S.

PostPosted: Wed Nov 24, 2004 9:00 pm    Post subject: software used Reply with quote

I used cdrtools-2.01.
_________________
:) Hindi ko naintindihan, pakiulit.
Back to top
View user's profile Send private message
rapsure
Apprentice
Apprentice


Joined: 29 Apr 2004
Posts: 163
Location: Spanish Fork, Utah, U.S.

PostPosted: Thu Nov 25, 2004 12:10 am    Post subject: codes need to use burner Reply with quote

Code:

Nov 24 16:12:51 [kernel] scsi: unknown opcode 0x55
Nov 24 16:12:51 [kernel] scsi: unknown opcode 0x1e
Nov 24 16:12:51 [kernel] scsi: unknown opcode 0x01
Nov 24 16:12:51 [kernel] scsi: unknown opcode 0xbb
Nov 24 16:13:01 [kernel] scsi: unknown opcode 0x54
Nov 24 16:13:03 [kernel] scsi: unknown opcode 0x5d
Nov 24 16:13:03 [kernel] scsi: unknown opcode 0x2a
Nov 24 16:15:54 [kernel] scsi: unknown opcode 0x35


Those are the codes that are needed for my burner to burn. I modified the filter function so that I could get that information. I propose that instead of a list of allowed commands for writing in the kernel there should be a list of banned commands for writing. The list would most likely be shorter and more saner. From what I read Linus put the patch in so that a user couldn't flash the firmware on the drive.

I do agree with the security with the read though. I wouldn't want the read allowed commands changed.
_________________
:) Hindi ko naintindihan, pakiulit.
Back to top
View user's profile Send private message
dsd
Developer
Developer


Joined: 30 Mar 2003
Posts: 2162
Location: nr London

PostPosted: Thu Nov 25, 2004 8:57 am    Post subject: Re: software used Reply with quote

rapsure wrote:
I used cdrtools-2.01.

which actual binary though? cdrtools contains a few..
and please confirm that you have write access to your cd writer node - it may have dropped back to read only...
_________________
http://dev.gentoo.org/~dsd
Back to top
View user's profile Send private message
dsd
Developer
Developer


Joined: 30 Mar 2003
Posts: 2162
Location: nr London

PostPosted: Thu Nov 25, 2004 8:58 am    Post subject: Re: codes need to use burner Reply with quote

rapsure wrote:
Code:

Nov 24 16:12:51 [kernel] scsi: unknown opcode 0x55
Nov 24 16:12:51 [kernel] scsi: unknown opcode 0x1e
Nov 24 16:12:51 [kernel] scsi: unknown opcode 0x01
Nov 24 16:12:51 [kernel] scsi: unknown opcode 0xbb
Nov 24 16:13:01 [kernel] scsi: unknown opcode 0x54
Nov 24 16:13:03 [kernel] scsi: unknown opcode 0x5d
Nov 24 16:13:03 [kernel] scsi: unknown opcode 0x2a
Nov 24 16:15:54 [kernel] scsi: unknown opcode 0x35


did you modify it in the same way as i did? at least half of those are already permitted by the kernel (i havent checked the others, but i just recognise some..), *as long as you have write access to your cd writer node* (and the software must open the node for read+write)
_________________
http://dev.gentoo.org/~dsd
Back to top
View user's profile Send private message
rapsure
Apprentice
Apprentice


Joined: 29 Apr 2004
Posts: 163
Location: Spanish Fork, Utah, U.S.

PostPosted: Thu Nov 25, 2004 9:19 am    Post subject: I found the problem Reply with quote

Here is what was happening. I put a lot of debugging information into the command filter function to figure out what was going on there. The commands from cdrecord weren't being recognized as cmd_type CMD_WRITE_SAFE commands. I don't know why, but they weren't being recognized at all the the entire filter. If it was working I should have gotten debug information back from the (type & CMD_WARN) if statement, but I wasn't. So this is what I did.

scsi_ioctl.c
Code:

        /* Anybody who can open the device can do a read-safe command */
        if (type & CMD_READ_SAFE)
                return 0;

        cmd_type[cmd[0]] = CMD_WRITE_SAFE; /* Stupid filter below wasn't  working*/
        /* Write-safe commands just require a writable open.. */
        if (type & CMD_WRITE_SAFE) {
                if (file->f_mode & FMODE_WRITE)
                        return 0;
        }



Then I went and changed the O_RDONLY references in the cdrtools to O_RDWR to open the device for write mode. Then I compiled, and tested, and it worked. If cdrecord-proDVD was Open source I would get it working too.
_________________
:) Hindi ko naintindihan, pakiulit.
Back to top
View user's profile Send private message
rapsure
Apprentice
Apprentice


Joined: 29 Apr 2004
Posts: 163
Location: Spanish Fork, Utah, U.S.

PostPosted: Thu Nov 25, 2004 5:19 pm    Post subject: code fix Reply with quote

I took out the patch in the kernel, and now only cdrtools is patched. It does seem backwards that cdrecord was opening the device for read, and not write.
_________________
:) Hindi ko naintindihan, pakiulit.
Back to top
View user's profile Send private message
dsd
Developer
Developer


Joined: 30 Mar 2003
Posts: 2162
Location: nr London

PostPosted: Thu Nov 25, 2004 7:26 pm    Post subject: Reply with quote

opening cd nodes as O_RDRW fails on kernel 2.4 unless it is a DVD-RAM disc.
_________________
http://dev.gentoo.org/~dsd
Back to top
View user's profile Send private message
rapsure
Apprentice
Apprentice


Joined: 29 Apr 2004
Posts: 163
Location: Spanish Fork, Utah, U.S.

PostPosted: Fri Nov 26, 2004 2:02 am    Post subject: Another function to test write permissions Reply with quote

Is there another structure that can test for write capabilities, but with out the drive needing to be in write mode? The current
Code:

if (file->f_mode & MODE_WRITE)


is checking if the drive is in write mode, and if you have write permissions. I just want something to check if you have write permissions.
_________________
:) Hindi ko naintindihan, pakiulit.
Back to top
View user's profile Send private message
Herodot
Guru
Guru


Joined: 29 Jul 2002
Posts: 429
Location: Professor Xavier's school for gifted youngsters

PostPosted: Fri Nov 26, 2004 4:13 am    Post subject: Reply with quote

I'm using 2.6.9-gentoo-r4, Cdrecord 2.01 and K3b 0.11.17. I'v removed the suid from cdrecord and whatever else I could find. But I now have these problems:

1) When I try to burn a cd it fails, usually about halfway through. K3b complains about cdrecord not being suid. So I can't really burn anything.

2) When I erase a cdrw, the desktop stalls until the erase is finished.
_________________
Excelsior!
Back to top
View user's profile Send private message
MaxDamage
l33t
l33t


Joined: 03 Jan 2004
Posts: 650
Location: Oviedo, Spain

PostPosted: Sat Nov 27, 2004 10:04 am    Post subject: Reply with quote

I'm trying to blank a CDRW but it fails. That's what I get in /var/lo/messages:
Code:

Nov 27 10:59:07 Mutsumi verify_command: rejected command 55
Nov 27 10:59:07 Mutsumi verify_command: rejected command 55
Nov 27 10:59:07 Mutsumi verify_command: rejected command 55
Nov 27 10:59:07 Mutsumi verify_command: rejected command 55
Nov 27 10:59:07 Mutsumi verify_command: rejected command 55
Nov 27 10:59:07 Mutsumi verify_command: rejected command 55
Nov 27 10:59:07 Mutsumi verify_command: rejected command 55
Nov 27 10:59:07 Mutsumi verify_command: rejected command 55
Nov 27 10:59:07 Mutsumi verify_command: rejected command 55
Nov 27 10:59:07 Mutsumi verify_command: rejected command 55
Nov 27 10:59:08 Mutsumi verify_command: rejected command 1e
Nov 27 10:59:08 Mutsumi verify_command: rejected command 1
Nov 27 10:59:08 Mutsumi verify_command: rejected command 55
Nov 27 10:59:08 Mutsumi verify_command: rejected command 55
Nov 27 10:59:08 Mutsumi verify_command: rejected command 55
Nov 27 10:59:08 Mutsumi verify_command: rejected command 35
Nov 27 10:59:08 Mutsumi verify_command: rejected command 55
Nov 27 10:59:08 Mutsumi verify_command: rejected command 1e
Nov 27 10:59:09 Mutsumi verify_command: rejected command 55
Nov 27 10:59:09 Mutsumi verify_command: rejected command 55
Nov 27 10:59:09 Mutsumi verify_command: rejected command 55
Nov 27 10:59:09 Mutsumi verify_command: rejected command 55
Nov 27 10:59:09 Mutsumi verify_command: rejected command 55
Nov 27 10:59:09 Mutsumi verify_command: rejected command 55
Nov 27 10:59:09 Mutsumi verify_command: rejected command 55
Nov 27 10:59:09 Mutsumi verify_command: rejected command 55
Nov 27 10:59:09 Mutsumi verify_command: rejected command 55
Nov 27 10:59:09 Mutsumi verify_command: rejected command 55
Nov 27 10:59:10 Mutsumi verify_command: rejected command 1e

I'm using Gtoaster, that's the error message (in fact, the cdrecord one):
Code:

GnomeToaster Recording Terminal
blanking CDRW.
cdrecord: Warning: Running on Linux-2.6.9-gentoo-r6
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.
cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: 'ATAPI:0,0,0'
devname: 'ATAPI'
scsibus: 0 target: 0 lun: 0
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.
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
Using libscg version 'schily-0.8'.
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   :
Vendor_info    : 'SONY    '
Identifikation : 'CD-RW  CRX185E1 '
Revision       : 'XYS2'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE FORCESPEED
Supported modes:
cdrecord: Operation not permitted. prevent/allow medium removal: scsi sendcmd: no error
CDB:  1E 00 00 00 01 00
status: 0x0 (GOOD STATUS)
cmd finished after 0.000s timeout 40s
cdrecord: Cannot init drive.

_________________
La PDA de tungsteno
Back to top
View user's profile Send private message
dsd
Developer
Developer


Joined: 30 Mar 2003
Posts: 2162
Location: nr London

PostPosted: Sat Nov 27, 2004 1:00 pm    Post subject: Reply with quote

MaxDamage: you have to make sure that gtoaster uses device /dev/hdc (for example) as opposed to ATAPI:0,0,0
_________________
http://dev.gentoo.org/~dsd
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Goto page Previous  1, 2, 3, 4, 5, 6, 7  Next
Page 3 of 7

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum