00 sks=0x48 0x00
>> 0x01
>> And writing by k3b freeze ALL system, not only k3b.
>
> Beni confirmed that he could use command line and write a cd. That
> post to mean that the problem is in k3b itself. Or not?
>
As for me, this is a atapi-cam problem, not k3b.
(kern/11211
Mark Linimon said the following on 26.04.2007 10:56:
--
> I believe that this problem is now in kern/112119, which I am trying to
> attract developer attention to.
Yes, thanks, Mark.
--
Best regards,
Simon Phoenix (Phoen
orks
fine without any error messages or freezes. K3B, cdrecord, hal and
others works without any visible problems.
--
Best regards,
Simon Phoenix (Phoenix Lab.)
---
KeyID: 0x2569D30B
should have been fixed a while ago by jylefort when he set the
>>>> default device for ATAPI access to be the ATAPICAM device (as
>>>> opposed to
>>>> the ATA device). Assuming you have not undone that change, and are
>>>> running th
rticular ATAPI
>> function (long reads comes to mind). ASC 0x24 ASCQ 0x00 is "Illegal
>> field in CDB" for most ATAPI operatons...
>
>
> Kernel from March works normally...
>
I have the same problem on my 6.2-STABLE box
1:
>
> To start k3b with a disk in the device of reading/record. A start takes a
> place normally.
>
> Test 2:
>
> To start k3b without a disk in the device of reading/record. At a start the
> k3b system hangs up and overloaded.
>
After writing a
O. Hartmann wrote:
> > I need to be able to get the cpu and fan information from my
> > motherboard, however none of the monitoring utilities in the ports
> > seems to support my motherboard (Supermicro PDSMi, Intel E7230
> > (Mukilteo) Chipset). On my older VIA based motherboards and some
> > Nvid
