On Sat, 14 Jun 1997, Hamish Moffatt wrote:
:On Thu, Jun 12, 1997 at 04:39:53PM +0200, [EMAIL PROTECTED] wrote:
:> When I rebooted to linux I noticed several network error
[snip]
:> configuration tool (grrr...). The second case (1.2, Apr 97)
:
:> Am I the only one with such an expirience? I shoul
Joost writes:
> I think that it is however possible to fry hardware with linux: while
> trying 1.3 I inserted a wrong module for the cdrom interface and it fried
> the cdrom drive.
IMHO anything that can be truly "fried" in this way (that is, physically
damaged) is broken as designed.
John Hasler
On Fri, 13 Jun 1997, Jason Gunthorpe wrote:
> On Thu, 12 Jun 1997, Bruce Perens wrote:
>
> > fit in the kernel. If you can tell me about the I/O ports of your network
> > card we can give you magic words to put on the boot command line for that
> > device that reserve its ports and prevent othe
On Thu, Jun 12, 1997 at 04:39:53PM +0200, [EMAIL PROTECTED] wrote:
> When I rebooted to linux I noticed several network error
> messages, and ping showed "Network is unreachable".
> Apparently the rescue disk had confused my WD8013 ethernet
> card. Then I booted do DOS -- and it complety hang afte
The EEPROM getting scrambled is a result of drivers probing for devices
on the bus that don't happen to be there, and hitting the network card
instead. This happens more with the rescue disk than with a custom kernel
because the rescue disk is built for every scsi and ethernet card we could
fit in
On Thu, 12 Jun 1997, Bruce Perens wrote:
> The EEPROM getting scrambled is a result of drivers probing for devices
> on the bus that don't happen to be there, and hitting the network card
> instead. This happens more with the rescue disk than with a custom kernel
> because the rescue disk is bui
On Thu, 12 Jun 1997, Lee Bradshaw wrote:
> I had a similar problem with tcpdump. After I saw it referenced in a
> message here I decided to see what kind of info it would print out. The
> info on my card (3C509) looked correct, but after running tcpdump, I
> couldn't connect to any other machi
I had a similar problem with tcpdump. After I saw it referenced in a
message here I decided to see what kind of info it would print out. The
info on my card (3C509) looked correct, but after running tcpdump, I
couldn't connect to any other machines. The light on my hub indicated
the card wasn't
Hi,
after updating my Debian box at work from 1.2 to 1.3 (with
no problems) I accidently managed to lock as well my root
as my user account.
To repair I got the newest 1.3 Rescue Disk (resq1440.bin)
from my Debian mirror, rawrite2´ed it to a floppy, booted the
system using the floppy, mounted my
9 matches
Mail list logo
