Jan, Ted, List,
This has been an interesting project. I needed to build a new image for
my 4801 with limited interruptions of server. That did not happen, it
would have been quicker to that the server offline and use it to rebuild
the system. The process was a learning experience and something I will
use in the future.
To start with I used this link:
http://www.linuxvillage.ca/support/soekris4801.html
It worked to a point. The drivers for the Soekris did not get installed.
I found that I needed to install x11-common to get them, that worked.
Now to the Udev stuff. Have not yet figured it out, I will post the
fix when I get it.
Another problem I am seeing is a very annoying message taht make the
serial console useless. Over and over:
tail /var/log/kern.log
Feb 20 18:00:01 server kernel: [ 949.541144] Info fld=0x0
Feb 20 18:00:01 server kernel: [ 949.541145] sd 0:0:0:0: [sda] Add.
Sense: No additional sense information
Feb 20 18:00:01 server kernel: [ 949.555006] sd 0:0:0:0: [sda] Sense
Key : No Sense [current]
Feb 20 18:00:01 server kernel: [ 949.555010] Info fld=0x0
Feb 20 18:00:01 server kernel: [ 949.555012] sd 0:0:0:0: [sda] Add.
Sense: No additional sense information
Feb 20 18:00:07 server kernel: [ 955.007900] sd 0:0:0:0: [sda] Sense
Key : No Sense [current]
I think this is be cause I am booting from a USB HDD and maybe fixable
with a kernel option?
All in all, it is mostly there.
Thanks again to all for your time.
Jan Ceuleers wrote:
> William Estrada wrote:
>> I'm new to Debian, how do I install this driver??
>
> William,
>
> (Re-posting to the list as well. Can the list owner please automatically add
> an appropriate Reply-To header?).
>
> I agree with Andy, you may have been bitten by the persistent net rules (put
> in place by udev and then applied from then on).
>
> A few things to do:
>
> 1. find out which ethernet interfaces you have and which drivers are attached
> to them as follows:
>
> # ls -l /sys/class/net/eth*/device/driver
>
> 2. if, as Andy and I suspect, you can find all three of your interfaces but
> with unexpected names (such as eth{345}), then you indeed have the udev
> problem described above. The idea of these udev rules is to guarantee that
> the names of your network interfaces will always be the same, regardless of
> boot order (particularly, regardless of the order in which network device
> drivers are loaded, as this is where races might occur or changes might be
> made from one kernel release to the next).
>
> Inspect the file /etc/udev/rules.d/70-persistent-net.rules . You will find,
> for each of the network interfaces that this disk image has ever seen, a
> binding of the MAC address to a device name. You can either manually edit
> this (so that the rule for your eth0's MAC address actually maps it to eth0
> rather than to eth3 or whatever), or just delete all of the rules that are
> currently wrong.
>
> Just deleting the rules works, because those rules are automatically
> generated upon boot, when the system finds a network interface with a MAC
> address for which no rule exists yet.
>
> 3. if in fact you don't find any network interfaces then you may indeed have
> a driver problem. Find out whether the driver exists on your system as
> follows:
>
> # find /lib/modules/`uname -r` -name natsemi.ko
>
> Also verify that it's not blacklisted:
>
> # cd /etc/modprobe.d
> # fgrep -r natsemi *
>
> Hope this helps.
>
> Jan
>
--
William Estrada
Mt Umunhum, CA, USA
HTTP://64.124.13.3 ( Mt-Umunhum-Wireless.net )
_______________________________________________
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech
