WARNING: Driver mistake: destroy_dev on 154/0

2001-10-30 Thread Jan Stocker
Ive updated the first time my system to current (Oct-28, with cvsup). After a make buildword and installworld, i made a new GENERIC kernel and copied the file GENERIC.hints to /boot/device.hints and installed the new kernel. I ve updated all files in /etc and remade all devices. Now a bootup

Re: WARNING: Driver mistake: destroy_dev on 154/0

2001-10-30 Thread Poul-Henning Kamp
In message 000801c1617c$9599ad00$[EMAIL PROTECTED], Jan Stocker writes: Ive updated the first time my system to current (Oct-28, with cvsup). After a make buildword and installworld, i made a new GENERIC kernel and copied the file GENERIC.hints to /boot/device.hints and installed the new kernel.

Re: WARNING: Driver mistake: destroy_dev on 154/0

2001-10-30 Thread John Baldwin
On 30-Oct-01 Poul-Henning Kamp wrote: In message 000801c1617c$9599ad00$[EMAIL PROTECTED], Jan Stocker writes: Ive updated the first time my system to current (Oct-28, with cvsup). After a make buildword and installworld, i made a new GENERIC kernel and copied the file GENERIC.hints to

Re: WARNING: Driver mistake: destroy_dev on 154/0

2001-10-30 Thread Warner Losh
In message [EMAIL PROTECTED] John Baldwin writes: : : On 30-Oct-01 Poul-Henning Kamp wrote: : In message 000801c1617c$9599ad00$[EMAIL PROTECTED], Jan : Stocker : writes: : Ive updated the first time my system to current (Oct-28, with cvsup). After : a make : buildword and installworld, i

Re: WARNING: Driver mistake: destroy_dev on 154/0

2001-10-30 Thread Scott Long
On Tue, Oct 30, 2001 at 03:58:39PM -0700, Warner Losh wrote: In message [EMAIL PROTECTED] John Baldwin writes: : : On 30-Oct-01 Poul-Henning Kamp wrote: : In message 000801c1617c$9599ad00$[EMAIL PROTECTED], Jan : Stocker : writes: : Ive updated the first time my system to current

Re: WARNING: Driver mistake: destroy_dev on 154/0

2001-10-30 Thread Nick Hibma
Yes. I have no idea why phk has not done this. As this is a purposeful panicing of systems that worked fine before, I presume that someone is keeping track of the problems that are occurring and going to do something about it? Or is this a bad case of 'someone else's problem'? Nick On Tue, 30

Re: WARNING: Driver mistake: destroy_dev on 154/0

2001-10-30 Thread Scott Long
On Wed, Oct 31, 2001 at 12:10:14AM +, Nick Hibma wrote: Yes. I have no idea why phk has not done this. As this is a purposeful panicing of systems that worked fine before, I presume that someone is keeping track of the problems that are occurring and going to do something about it? Or

Clock Drift

2001-10-30 Thread Dreamtime.net Inc.
A while back I read a thread regarding clock drift. We are now having the same problem. Does anyone know what the remedy is for this? Thanks. Sincerely, Stephen H. Kapit To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

Re: ouch -- the second controller on Promise-66 is not detected!

2001-10-30 Thread Mikhail Teterin
On 31 Oct, Andrey A. Chernov wrote: On Tue, Oct 30, 2001 at 19:37:27 -0500, Mikhail Teterin wrote: Alright, alright, what do I do now? I did NOT wire any ata devices, Ask Soren to fix ATA driver in the way I describe below: Giving more details: ATA code must test wired slot, and, if

Re: ouch -- the second controller on Promise-66 is not detected!

2001-10-30 Thread Andrey A. Chernov
On Tue, Oct 30, 2001 at 22:41:41 -0500, Mikhail Teterin wrote: Perfect, and how would I do that? You saw the ata-part of my hints file. How do I modify it? Try patch from N. Dudorov posted to -current. I can't come with patches here since have no hardware to reproduce this bug. -- Andrey

Re: PCMCIA modem is detected/attached only on second insertion

2001-10-30 Thread Maxim Sobolev
Konstantin Chuguev wrote: Hi All, FYI: Maxim Sobolev wrote: I had started observing this problem about a 1.5 months ago - my PCMCIA modem (EigerCom 33.6) is detected/attached only on second insertion, i.e. if I'm booting with the card inserted I have to manually eject it and

Re: high-density floppies

2001-10-30 Thread Joerg Wunsch
Joel Wilsson [EMAIL PROTECTED] wrote: fd0: hard error reading fsbn 0 (ST0 40abnrml ST1 1no_am ST2 0 cyl 0 hd 0 sec 1) So, I thought I'd try using a raw device configured for higher density disks. That wouldn't help you. It's already failing at the very first sector, by not finding

Re: WARNING: Driver mistake: destroy_dev on 154/0

2001-10-30 Thread Dag-Erling Smorgrav
[EMAIL PROTECTED] (Jan Stocker) writes: So whats on? Please refer to the Handbook, section 19.2.1.4, first paragraph. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

Re: ouch -- the second controller on Promise-66 is not detected!

2001-10-30 Thread Andrey A. Chernov
On Tue, Oct 30, 2001 at 14:57:17 -0800, Peter Wemm wrote: date: 2000/05/26 13:59:05; author: sos; state: Exp; lines: +8 -13 If devclass_alloc_unit() is called with a wired unit #, and this is buzy, only search upwards for a free slot to use.. This broke unit numbering on ATA systems

Re: ouch -- the second controller on Promise-66 is not detected!

2001-10-30 Thread Andrey A. Chernov
On Wed, Oct 31, 2001 at 02:57:42 +0300, Andrey A. Chernov wrote: On Tue, Oct 30, 2001 at 14:57:17 -0800, Peter Wemm wrote: date: 2000/05/26 13:59:05; author: sos; state: Exp; lines: +8 -13 If devclass_alloc_unit() is called with a wired unit #, and this is buzy, only search upwards

Re: ouch -- the second controller on Promise-66 is not detected!

2001-10-30 Thread Mikhail Teterin
Alright, alright, what do I do now? I did NOT wire any ata devices, and hints only list the on-motherboard ata controllers (one of them has a CD drive attached to it, that's it): hint.ata.0.at=isa hint.ata.0.port=0x1F0 hint.ata.0.irq=14 hint.ata.1.at=isa

Re: ouch -- the second controller on Promise-66 is not detected!

2001-10-30 Thread Andrey A. Chernov
On Tue, Oct 30, 2001 at 19:37:27 -0500, Mikhail Teterin wrote: Alright, alright, what do I do now? I did NOT wire any ata devices, and Ask Soren to fix ATA driver in the way I describe below: Giving more details: ATA code must test wired slot, and, if it is busy, increase number to

Re: ouch -- the second controller on Promise-66 is not detected!

2001-10-30 Thread
On Wed, Oct 31, 2001 at 08:54:35 +0600, Nickolay Dudorov wrote: With the following patch I can now use all the channels on the HPT366 controller in my ABIT's BP6 mobo. else { - if (!(child = device_add_child(dev, ata, 2))) + if (!(child = device_add_child(dev, ata, -1)))