Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
I've had this happen when I didn't correctly configure the SCSI setup in the kernel configuration. It eventually completed the boot, allowing me to telnet in. After checking the boot logs, I found massive SCSI errors (which I didn't understand any more than that they were in fact SCSI errors). Not sure if this is the same thing, but it might be a clue. Brian Conway dogbert at clue4all.net ----- Original Message ----- From: Anthony J. Gabrielson <agabriel at coe.neu.edu> To: <discuss at Blu.Org> Cc: <comp.os.linux.alpha at coe.neu.edu> Sent: Thursday, May 13, 1999 8:11 PM Subject: An alpha question. > Hello, > I just compiled 2.2.8 on my alpha multia - here comes the fun > part. When it boots I don't get any text after it gunzip's the kernel. > the old text does not clear, but the typical messages don't come up. Here > comes the great part - I can telnet in to the box. don't understand it - > but the box actually comes up, I can telnet in fronm manother box. > > If you understand - please share with me - I would like to understand, > Anthony > > > - > Subcription/unsubscription/info requests: send e-mail with > "subscribe", "unsubscribe", or "info" on the first line of the > message body to discuss-request at blu.org (Subject line is ignored). > - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |