On Tue, 5 Jul 2005 [EMAIL PROTECTED] wrote:
(There are really only two AML interpreters and compilers:
the one found in Windows and the one from Intel (ACPICA) which
is used in Solaris, Linux and others.
Does Linux actually uses Intel's one or is that written from scratch? If
the question is
On Tue, 5 Jul 2005, James Lick wrote:
Dragan Cvetkovic wrote:
dd: /dev/rdiskette: open: No such file or directory
So, as far as Solaris is concerned, there is no floppy drive at all. It has
worked fine before switching to new ACPI architecture.
I see you've already fixed your problem, but
>I see you've already fixed your problem, but just wanted to add that I
>had a similiar problem with the floppy controller not showing up also.
>I fiddled around with a bunch of BIOS settings so I can't be sure which
>one fixed things, but one of them was to enable acpi in the BIOS. My
>Open
James Lick wrote:
I see you've already fixed your problem, but just wanted to add that I
had a similiar problem with the floppy controller not showing up
also. I fiddled around with a bunch of BIOS settings so I can't be
sure which one fixed things, but one of them was to enable acpi in the
Dragan Cvetkovic wrote:
dd: /dev/rdiskette: open: No such file or directory
So, as far as Solaris is concerned, there is no floppy drive at all.
It has worked fine before switching to new ACPI architecture.
I see you've already fixed your problem, but just wanted to add that I
had a simili
On Mon, 4 Jul 2005 [EMAIL PROTECTED] wrote:
I see quite a few acpica related messages (this is nevada b17) at boot
time, here they are:
Jun 30 12:18:31 lokrum acpica: [ID 972481 kern.warning] WARNING:
AcpiOsWritePort: 70 8 not permitt
ed
Jun 30 12:18:31 lokrum acpica: [ID 815887 kern.noti
>I see quite a few acpica related messages (this is nevada b17) at boot
>time, here they are:
>
>Jun 30 12:18:31 lokrum acpica: [ID 972481 kern.warning] WARNING:
>AcpiOsWritePort: 70 8 not permitt
ed
>Jun 30 12:18:31 lokrum acpica: [ID 815887 kern.notice] ACPI-0519: *** Error:
>Jun 30 12:18:31 l
On Mon, 4 Jul 2005 [EMAIL PROTECTED] wrote:
What happens when you stop vold, and try to read from the PS/2 floppy
using dd?
# /etc/init.d/volmgt stop
# dd if=/dev/rdiskette of=/dev/null bs=18k
Does that report I/O errors?
It does, sort of.
bash-3.00# dd if=/dev/rdiskette of=/dev/null
>> What happens when you stop vold, and try to read from the PS/2 flop=
>py=20
>> using dd?
>>
>># /etc/init.d/volmgt stop
>># dd if=3D/dev/rdiskette of=3D/dev/null bs=3D18k
>>
>> Does that report I/O errors?
>
>It does, sort of.
>
>bash-3.00# dd if=3D/dev/rdiskette of=3D/dev/null bs=3D18
On Fri, 1 Jul 2005, [UTF-8] Jürgen Keil wrote:
(btw, volcheck didn't react to floppies on my machine here)
What happens when you stop vold, and try to read from the PS/2 floppy
using dd?
# /etc/init.d/volmgt stop
# dd if=/dev/rdiskette of=/dev/null bs=18k
Does that report I/O errors?
On Fri, 1 Jul 2005, [UTF-8] Jürgen Keil wrote:
(btw, volcheck didn't react to floppies on my machine here)
What happens when you stop vold, and try to read from the PS/2 floppy
using dd?
# /etc/init.d/volmgt stop
# dd if=/dev/rdiskette of=/dev/null bs=18k
Does that report I/O errors?
> (btw, volcheck didn't react to floppies on my machine here)
What happens when you stop vold, and try to read from the PS/2 floppy using dd?
# /etc/init.d/volmgt stop
# dd if=/dev/rdiskette of=/dev/null bs=18k
Does that report I/O errors?
For Solaris 8 x86 .. Solaris 10 x86, most users
12 matches
Mail list logo
