[Durham] Fwd: Checking mini pci board on old laptop

Oliver Burnett-Hall olly at burnett-hall.co.uk
Tue Aug 19 11:59:04 UTC 2014

I think this message was supposed to be sent to the mailing list...

On 15 August 2014 19:43, David Walland <davidwalland at googlemail.com> wrote:
> Dear Oliver,
> Many thanks for this.  This is what I need to know to learn more about
> Linux.
> Martin, Thanks for your thoughts...
> The board is a standard Intel chipped one which has Linux drivers available
> on their site.  I actually updated Xubuntu from an ancient Ubuntu using a
> wifi on the USB port (USB1! Paint dries quicker.)  I have these external
> methods of working but want to learn by working out why the board isn't
> working right.
> When I get the time, I'm going to update the cpu from a 600MHz Celeron to a
> Pentium III.  I will also put a bigger HDD in as 6GB is a bit limiting!
> Also I'll try if another CD drive will improve matters as the current one is
> very picky (hence the Ubuntu 5 initial load).  The whole of this will cost
> less than £10!  It's a cheap learning experience and how I've learnt most of
> what I know - working with old freebies and upgrading them as cheaply as I
> can.  It's great fun too!
> Does anyone know how I can find out how to address the video chip and how to
> pull data off?  I have a planned bit of programming that needs me to be able
> to do this to put together a decent user interface.  I used to program a
> fair bit in the 60s to the mid 80s.
> Regards
> David
> On 15 August 2014 16:28, Oliver Burnett-Hall <olly at burnett-hall.co.uk>
> wrote:
>> >> b)      I do not know how to check whether the system can even see
>> >the board and whether it is loading drivers for it.
>> If the card is connected correctly then it should show up when you run
>> 'lspci' from the command line (you may been to be root or use su/sudo for
>> this).
>> If it's connected and has the right driver available then by running
>> 'ifconfig -a' (again you might need to be root) you should be able to see
>> the interface, probably eth0.
>> Once you've confirmed that's all working then you should be able to find
>> out which way to connect the internal Ethernet cable by trial and error.
>> --
>> — olly

More information about the Durham mailing list