9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Adriano Verardo <adriano.verardo@mail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Dell 3010 install problems - all tested kits
Date: Mon, 17 Feb 2014 16:35:10 +0100	[thread overview]
Message-ID: <53022C2E.9080003@mail.com> (raw)
In-Reply-To: <c959cb513a0457f09c2b8052463ca3b7@mikro.quanstro.net>

[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]

erik quanstrom ha scritto:
>> A fresh Dell 3010, AHCI, several fresh USB keys. Bell's, 9Atom and
>> 9Front don'install.
>>
>> usbinstamd64: several issues, as already documented in another thread.
>> An additional note: a persistent "addpart: #S/sdE0: i/o error" message.
>>
>> 9Atom cd downloaded on February, 5: rio install starts as usual, all ok
>> till the fdisk-w .
>> No useful messages. Only a generic warn (on rio window) and a console
>> display
>> of the disk identification data. Then all stops having no Plan9
>> partition to install on.
>> Trying on an pre-partitioned disk (by 9Front) the same problem arises in
>> prepdisk,
>> after the q cmd (not w+q). Same messages.
>> So 9Atom seems to have problems with usb and AHCI, but only in writing
>> the partion. VGA ok.
>>
>> Bell's usbdisk download yesterday: hangs after a few messages. I can
>> send video snapshots
>> to anyone interested. Let me know.
>>
>> Bell's cd downloaded on Feb, 5: rio install starts as usual but the disk
>> is not detected at all.
>>
>> 9Front cd downloaded on Feb, 9: boots ok but doesn'configure the VGA.
>> So text mode, all default choices. I/O error(s) when reaming the filesystem.
>> Partisk and prepdisk ok. Video snapshots available, let me know.
> okay.  if you have a chance, with the 9atom cd that boots to rio,
> can you try dd'ing from the /dev/sdE? you can just open a new window
> in the installer.
>
> 	; ramfs
> 	; dd -if /dev/sdE?/data -of /tmp -count 100 &&
> 		dd -if /tmp -of /dev/sdE?/data -count 100
>
> also the output of
>
> 	; cat /dev/sdE?/ctl
>
> and
> 	; pci
>
> and
> 	; cat /dev/irqalloc
>
> would be helpful.
>
> - erik
>
> Done


[-- Attachment #2: IMG_20140217_233219.jpg --]
[-- Type: image/jpeg, Size: 197347 bytes --]

  reply	other threads:[~2014-02-17 15:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17 14:19 Adriano Verardo
2014-02-17 14:33 ` Adriano Verardo
2014-02-17 14:43 ` erik quanstrom
2014-02-17 15:35   ` Adriano Verardo [this message]
2014-02-17 19:08     ` erik quanstrom
2014-02-17 20:34       ` Adriano Verardo
2014-02-17 15:43   ` Adriano Verardo
2014-02-17 15:51   ` Adriano Verardo
2014-02-17 15:52 ` Adriano Verardo
2014-02-17 18:02 ` Adriano Verardo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53022C2E.9080003@mail.com \
    --to=adriano.verardo@mail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).