From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Issues with USB mouse in 9atom
Date: Tue, 22 Sep 2015 19:23:00 -0700 [thread overview]
Message-ID: <fa54522c9a244aab376c25275f9834b5@brasstown.quanstro.net> (raw)
In-Reply-To: <1ab59aa9-531a-4830-9f29-deed55a3e2eb@email.android.com>
On Tue Sep 22 17:47:17 PDT 2015, quanstro@quanstro.net wrote:
> I mentioned booted.
>
> - erik
>
>
> On Sep 22, 2015 2:58 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> >
> > > Yeah, I installed from the CD. But that image is for amd64, correct? a 64
> > > bit processor? My junk computer is an old gateway, with a celeron D, a
> > > whopping 256 MB of ram, and a full 100 GB hard disk space. But since this
> > > is 32 bit to my knowledge, would a possible solution involve making a
> > > bootable flash disk from this distribution within my installation?
> > >
> > > > i don't see any confirmation, but it looks like the install was from the
> > > > cd image?
> > > > if so, i recommend using the usb install image instead
> > > >
> > > > http://ftp.9atom.org/other/usbinstamd64.bz2
> > > >
> > > > this *should* fix all those issues. posting a few details on the
> > > > processor might
> > > > be helpful in figuring out any issues.
> >
> > either 32 or 64 bit kernels can be built from the usb image.
well, autocorrect ftw! that was supposed to say, both the 32- and 64-bit
kernels can be /booted/ from the usb image, so your hardware should be
fine.
- erik
next prev parent reply other threads:[~2015-09-23 2:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 20:38 Roswell Grey
2015-09-22 21:58 ` erik quanstrom
2015-09-23 0:44 ` erik quanstrom
2015-09-23 2:23 ` erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-21 22:38 Roswell Grey
2015-09-22 0:04 ` erik quanstrom
2015-09-22 11:21 ` cinap_lenrek
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=fa54522c9a244aab376c25275f9834b5@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--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).