1 |
I thought comments should be posted at the top of the rply so users |
2 |
don't have to scroll thru' endless postings to reach the necessary |
3 |
'bit'. |
4 |
Also, No, I cannot ping this machine when it locks-up. I tried this |
5 |
first. |
6 |
I will build kernels with both kinds of board to see which works. |
7 |
|
8 |
|
9 |
|
10 |
On Mon, 2005-12-12 at 04:57 -0700, Duncan wrote: |
11 |
> Gavin Seddon posted <1134381056.10949.3.camel@linuxstation>, excerpted |
12 |
> below, on Mon, 12 Dec 2005 09:50:56 +0000: |
13 |
> |
14 |
> > Is there a way of determining the board type, other than opening the box |
15 |
> > and removing the card. I don't have it's original box. |
16 |
> > Thanks. |
17 |
> > |
18 |
> > |
19 |
> > On Sun, 2005-12-11 at 07:39 -0600, Brett Johnson wrote: |
20 |
> >> > |
21 |
> >> What model initio board do you have? There are two |
22 |
> >> different initio drivers, and the one called "initio" is for the 9100 |
23 |
> >> series chipset. It's possible loading the wrong chipset could lock up |
24 |
> >> the pc, or at least the console. When the console locks up, I like to go |
25 |
> >> to a different terminal (pc) and see if I can ping the frozen pc. If so, |
26 |
> >> then try to ssh in (assuming ssh is running) and see if I can shut it |
27 |
> >> down remotely. |
28 |
> |
29 |
> Annoying very. |
30 |
> Q: Top posting is...? |
31 |
> |
32 |
> (Of course, note that you should trim quotes to the context to which you |
33 |
> are replying as well, which top-quoting, as opposed to top-posting, |
34 |
> encourages. If you would have trimmed what you were quoting to the |
35 |
> above, sufficient to establish context, then I would not have needed to do |
36 |
> it for you, here, and the context would have been sufficiently established |
37 |
> so all I would have needed to do would have been to post my reply, plus |
38 |
> possibly trimming out deeper nested quoting, if you had included it, since |
39 |
> it's no longer necessary to establish the context to which I'm now |
40 |
> replying.) |
41 |
> |
42 |
> To answer your question, try lspci (ls for the PCI bus). If the output |
43 |
> isn't verbose enough to give you the detail you need, try lspci -v (for |
44 |
> verbose). It's a /very/ handy program to keep in your virtual toolbox, |
45 |
> particularly if you don't fancy opening up your box all the time to read |
46 |
> stuff off of the various chips and cards, let alone that even doing that |
47 |
> wouldn't directly give you the same level of detail that lspci -v does. |
48 |
> lspci is part of pciutils, in case you don't already have it merged, but |
49 |
> you likely do, at least if you have either alsa-utils or hotplug merged. |
50 |
> |
51 |
> FWIW, there's also a parallel lsusb, part of (no surprise) usbutils. =8^) |
52 |
> |
53 |
> -- |
54 |
> Duncan - List replies preferred. No HTML msgs. |
55 |
> "Every nonfree program has a lord, a master -- |
56 |
> and if you use the program, he is your master." Richard Stallman in |
57 |
> http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
58 |
> |
59 |
> |
60 |
-- |
61 |
Dr Gavin Seddon |
62 |
School of Pharmacy and Pharmaceutical Sciences |
63 |
University of Manchester |
64 |
Oxford Road, Manchester |
65 |
M13 9PL, U.K. |
66 |
|
67 |
-- |
68 |
gentoo-amd64@g.o mailing list |