On Mon, 7 Feb 19100, Martin Cracauer wrote: > > > > > It seem hardwiring SCSI devices is broken in -current: > > dmesg would be useful, otherwise we can't even begin to guess what happened. > > I can't provide it now. I don't have it in /var/log/messages, but I can reboot my machine (that has this problem) and copy down what I see. I have an error in the successful attempts, but that could also be my error, I need to recheck my config file. I'll get back to you with the important parts of dmesg... I really need this to work to be able to use the -stable machine as -current to test and see if my problems are fixed... :-/ barry bouws,a, tele danmork internet To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Hardwiring SCSI device ID broken? Martin Cracauer
- Re: Hardwiring SCSI device ID broken? Peter Wemm
- Re: Hardwiring SCSI device ID broken? Igor Timkin
- Re: Hardwiring SCSI device ID brok... Peter Wemm
- Re: Hardwiring SCSI device ID ... Martin Cracauer
- Re: Hardwiring SCSI device ID ... Igor Timkin
- Re: Hardwiring SCSI device ID broken? tele danmarQ kvindeservice
- Re: Hardwiring SCSI device ID broken? Martin Cracauer
- Re: Hardwiring SCSI device ID brok... Barry Bouwsma
- Re: Hardwiring SCSI device ID brok... Barry Bouwsma
- Re: Hardwiring SCSI device ID ... Peter Wemm
- Re: Hardwiring SCSI devic... Barry Bouwsma
- Re: Hardwiring SCSI device ID broken? tele danmarQ kvindeservice
- Re: Hardwiring SCSI device ID broken? Matthew Sean Thyer
- Re: Hardwiring SCSI device ID broken? Kun Limfjordsporter