From owner-freebsd-hardware Sun Jan 19 8:51: 3 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F95337B401; Sun, 19 Jan 2003 08:51:00 -0800 (PST) Received: from ua.fm (smtpav.ua.fm [195.248.190.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id C43F043ED8; Sun, 19 Jan 2003 08:50:56 -0800 (PST) (envelope-from slavex@ua.fm) Received: from [195.248.191.44] (account ) by ua.fm (CommuniGate Pro WebUser 3.5.9) with HTTP id 21066749; Sun, 19 Jan 2003 19:50:54 +0200 From: Subject: Troubles with isdnd To: freebsd-hardware@FreeBSD.ORG Cc: freebsd-isdn@FreeBSD.ORG X-Mailer: CommuniGate Pro Web Mailer v.3.5.9 Date: Sun, 19 Jan 2003 19:50:54 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="KOI8-R"; format="flowed" Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I`ve just istalled 4.7 with Fritz 2 PCI internal ISDN Card. Problem is that I cant establish Internet connection with my provider under freebsd :( When I try to up isp0 interface I get this: Dec 23 15:29:42 server isdnd[310]: DMN i4b isdn daemon started (pid = 310) Dec 23 15:29:43 server /kernel: i4b-L1 ifpi2_ph_data_req: No Space in TX FIFO, state = F4 Awaiting Signal Dec 23 15:29:45 server /kernel: i4b-L1 timer3_expired: state = F4 Awaiting Signal Dec 23 15:29:45 server /kernel: ifpi2_recover 0 Dec 23 15:29:45 server /kernel: i4b-L2 i4b_T202_timeout: unit 0, N202 = 3 Dec 23 15:29:45 server /kernel: i4b-L1 ifpi2_ph_data_req: still in state F3! Dec 23 15:29:45 server /kernel: i4b-L1 ifpi2_ph_data_req: No Space in TX FIFO, state = F4 Awaiting Signal Dec 23 15:29:47 server /kernel: i4b-L3 T303_timeout: SETUP not answered, cr = 122 Dec 23 15:29:47 server /kernel: i4b-L3 next_l3state: FSM illegal state, state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout! Dec 23 15:29:47 server /kernel: i4b-L1 timer3_expired: state = F4 Awaiting Signal Dec 23 15:29:47 server /kernel: ifpi2_recover 0 or this: Dec 23 15:24:18 server /kernel: i4b-L2 F_ILL: FSM function F_ILL executing Dec 23 15:24:18 server /kernel: i4b-L2 i4b_next_l2state: FSM illegal state, state = ST_EST_AW_TEI, event = EV_DLESTRQ! Dec 23 15:24:18 server isdnd[55]: ERR decr_free_channels: controller [0] already 0 free chans! Dec 23 15:24:20 server /kernel: i4b-L1 timer3_expired: state = F4 Awaiting Signal Dec 23 15:24:20 server /kernel: ifpi2_recover 0 Dec 23 15:24:22 server /kernel: i4b-L3 T303_timeout: SETUP not answered, cr = 63 Dec 23 15:24:22 server /kernel: i4b-L3 next_l3state: FSM illegal state, state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout! after that isdnd do nothing on any other attempt to up isp0 and have to be restarted / re-read its config Seems like hardware problem? ( I tried to change not only slots, bios`s irq & pnp, but even changed motheboards ) I really cant establish connection on my isdn line for 5-15 redial under windows, but isdnd doesnt redial at all, it hangs up on first attempt, flooding the console with above messages and have to be restarted. How may it be solved if isdnd doesn`t act on any redial attempt after the errors? I have found similiar problem in isdn FAQ (#9), but answers doesnt really help: >Even when the testsoftware under DOS is working, don't be shure, that >your hw-setup is correct for xxx(x)BSD. Triplecheck all your IRQ and >enable and disable PNP to triple-verify. Even unconfigured devices can >block your card. ..... >And that took me more than 2 months to discover :-(((( May it be a problem with mycard driver in 4.7 or i4b ? Sory for long text, but I decided to write some lines from configs: isdnd.rc name = ALKAR usrdevicename = isp usrdeviceunit = 0 isdncontroller = 0 isdnchannel = -1 local-phone-dialout = 111 remote-phone-dialout = 7111111 remdial-handling = first dialin-reaction = ignore dialout-type = normal dialretries = 10 b1protocol = hdlc idletime-incoming = 1 idletime-outgoing = 5 ratetype = 0 unitlength = 90 unitlengthsrc = rate dialrandincr = off direction = out rc.conf ... ifconfig_isp0="inet 0.0.0.0 0.0.0.1 netmask 255.255.255.255 link1" # get from DHCP sppp_interfaces="isp0" # example: sppp over ISDN spppconfig_isp0="authproto=pap myauthname=optima myauthsecret='optima' hisauthproto=none" defaultrouter="0.0.0.1" # Get from DHCP isdn_enable="YES" # Enable the ISDN subsystem (or NO). isdn_fsdev="/dev/ttyv4" # Output device for fullscreen mode isdn_flags="NO" # Flags for isdnd isdn_trace="NO" # Enable the ISDN trace subsystem (or NO). isdn_traceflags="-f /var/tmp/isdntrace0" # Flags for isdntrace kernel is compiled to use "ifpi2" Thanks in advance ---- HOBOCTI ABTO http://auto.alkar.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jan 19 9:30:24 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 257DB37B415; Sun, 19 Jan 2003 09:30:22 -0800 (PST) Received: from www.raditex.se (www.raditex.se [192.5.36.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57B4D441AC; Sun, 19 Jan 2003 09:27:31 -0800 (PST) (envelope-from gh@raditex.se) Received: from gandalf.sickla.raditex.se (gandalf.raditex.se [192.5.36.18]) by www.raditex.se (8.12.6/8.12.6) with ESMTP id h0JHQEeh022929; Sun, 19 Jan 2003 17:26:14 GMT (envelope-from gh@raditex.se) Date: Sun, 19 Jan 2003 19:39:59 +0000 (GMT) From: G Hasse To: Cc: , Subject: Re: Troubles with isdnd In-Reply-To: Message-ID: <20030119193925.S64257-100000@gandalf.raditex.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I had a lot of problem with small variables like ispppcontrol isp1 lcp-timeout=3D1000 Try different values with those. G=F6ran ---------------------------------------------------------------- G=F6ran Hasse email: gh@raditex.se Tel: 08-6949270 Raditex AB http://www.raditex.se Fax: 08-4420570 Sickla Alle 7, 1tr Mob: 070-5530148 131 34 NACKA, SWEDEN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jan 19 16:37:16 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B82937B401; Sun, 19 Jan 2003 16:37:14 -0800 (PST) Received: from emerald.crystal.com.au (emerald.crystal.com.au [203.21.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9228643ED8; Sun, 19 Jan 2003 16:37:12 -0800 (PST) (envelope-from shaun@crystal.com.au) Received: from crystal.com.au ([202.165.76.30]) by emerald.crystal.com.au (8.12.0.Beta19/8.12.0.Beta19) with ESMTP id h0K0dBVw005916; Mon, 20 Jan 2003 08:39:12 +0800 Message-ID: <3E2B4432.3080705@crystal.com.au> Date: Mon, 20 Jan 2003 08:34:58 +0800 From: Shaun Dwyer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lanny Baron Cc: Soeren Schmidt , Keith Mitchell , "randall s. ehren" , freebsd-hardware , freebsd-stable@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: ATA problems (still) References: <200301151238.h0FCcD5e025929@spider.deepcore.dk> <1042677925.19537.42.camel@panda.FreeBSDsystems.COM> In-Reply-To: <1042677925.19537.42.camel@panda.FreeBSDsystems.COM> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all... This might be completely un-related... I have a box with 6 WD 80Gb BB series drives on a 3ware Escalade raid controller doing raid 5. Every now and then a drives seem to drop from the array for no reason. Its always a different drive, on a different port. Mabye the later WD drives have some issues. Perhaps overly aggressive timing? --Shaun Lanny Baron wrote: > Hi, > For what it's worth here is some info we rely on. In Servers, most wd > hard drives will -not- run and in some cases, not even be seen by > FreeBSD with our systems.When speaking to Engineers in Oregon, they have > simply said to stay away from them with Servers. Most Intel Server > boards are picky with hardware and, when using the correct combination > of hardware, run flawlessly. > > Of course, it is not in my right, nor am I suggesting that anyone not > use Western Digital. But, I did test it out some time ago and lo and > behold, it was true. > Below is an example from one of our Server Board's tested and passed > list of hdds (ata and scsi). Note there are no WD drives. > > > Manufacturer Model Number Product Family Interface RPM > > IBM* IC35L120AVVA07 Deskstar ATA 7,200 123 1, 2, 3, 4 > Maxtor* 4G160J8 Neptune D540DX ATA 5,400 160 1, 2, 3, 4 > Maxtor MX 6L080J4 Viper D740-6L ATA 7,200 80 1, 2, 3, 4 > Maxtor KU73J01703B Atlas III SCA-320 10,000 73 1, 2, 3, 4 > Maxtor KW18J01E-030Z Atlas III SCA-160 10,000 18 1, 2, 3, 4 > Samsung* SP4004H ATA100 SpinPoint P20 ATA 7,200 40 1, 2, 3, 4 > Seagate* ST318406LC Cheetah 36ES U160 10,000 18 1, 2, 3, 4 > Seagate ST318406LC Cheetah 36ES U160 10,000 18 1, 2, 3, 4 > Seagate ST380021A Barracuda 4 ATA 7,200 80 1, 2, 3, 4 > > Regards, > Lanny > > On Wed, 2003-01-15 at 07:38, Soeren Schmidt wrote: > >>It seems Keith Mitchell wrote: >> >>>I just tried swapping one of the seagate drives with the WD ATA6 drive >>>so that the WD was aatached to the same motherboard and cable where the >>>segate was happily working and the segate was attached to the same >>>motherboard and cable where the WD wasn't happily working. >>> >>>And the result was the same... the seagte is still happily working and >>>the WD drive is crashing the same as it was before. >> >>Hmm so the conclusion seems to be that the WD drive has problems, since >>we know the controller works and other large drives works. >>I have no idea why it would fail, could be subtle timing I guess ... >> >>If I win the lottery I'll buy one and hack at it :) >> >>-Søren >> >>To Unsubscribe: send mail to majordomo@FreeBSD.org >>with "unsubscribe freebsd-hardware" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jan 20 11:12:50 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67EF137B401; Mon, 20 Jan 2003 11:12:49 -0800 (PST) Received: from agena.meridian-enviro.com (thunder.meridian-enviro.com [207.109.234.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CDD343F3F; Mon, 20 Jan 2003 11:12:48 -0800 (PST) (envelope-from rand@meridian-enviro.com) Received: from delta.meridian-enviro.com (delta.meridian-enviro.com [10.10.10.43]) by agena.meridian-enviro.com (8.11.6/8.11.6) with ESMTP id h0KJCHf47066; Mon, 20 Jan 2003 13:12:17 -0600 (CST) (envelope-from rand@meridian-enviro.com) Received: (from rand@localhost) by delta.meridian-enviro.com (8.12.3/8.12.3/Submit) id h0KJCB3a074182; Mon, 20 Jan 2003 13:12:11 -0600 (CST) (envelope-from rand@meridian-enviro.com) X-Authentication-Warning: delta.meridian-enviro.com: rand set sender to rand@meridian-enviro.com using -f To: Shaun Dwyer Cc: Lanny Baron , Soeren Schmidt , Keith Mitchell , "randall s. ehren" , freebsd-hardware , freebsd-stable@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: ATA problems (still) References: <200301151238.h0FCcD5e025929@spider.deepcore.dk> <1042677925.19537.42.camel@panda.FreeBSDsystems.COM> <3E2B4432.3080705@crystal.com.au> From: rand@meridian-enviro.com (Douglas K. Rand) Date: 20 Jan 2003 13:12:10 -0600 In-Reply-To: <3E2B4432.3080705@crystal.com.au> Message-ID: <874r83zldh.fsf@delta.meridian-enviro.com> Lines: 22 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Shaun> Hi all... Hi! Shaun> I have a box with 6 WD 80Gb BB series drives on a 3ware Shaun> Escalade raid controller doing raid 5. Every now and then a Shaun> drives seem to drop from the array for no reason. Its always a Shaun> different drive, on a different port. Mabye the later WD drives Shaun> have some issues. Perhaps overly aggressive timing? We had very similiar problems with WD 100 GB (WD1000BB) disks on a 3ware controller. We'd get this error for no apparent reason: twe0: AEN: It turns out that there is some bios incompatability between the 3ware controller and these WD disks. Once I found the right person at 3ware and described my problem, he said that its the disks. We switched to IBM disks and the problem went away. I have NO IDEA if the problem is the same on the WD800BB disks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jan 20 11:19:57 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01FB037B401; Mon, 20 Jan 2003 11:19:56 -0800 (PST) Received: from weenix.guru.org (weenix.guru.org [24.199.153.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19F5E43E4A; Mon, 20 Jan 2003 11:19:55 -0800 (PST) (envelope-from kmitch@guru.org) Received: from guru.org (dhcp-64-102-83-151.cisco.com [64.102.83.151]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by weenix.guru.org (Postfix) with ESMTP id C7FEEACABE; Mon, 20 Jan 2003 14:19:42 -0500 (EST) Message-ID: <3E2C4BCD.7090604@guru.org> Date: Mon, 20 Jan 2003 14:19:41 -0500 From: Keith Mitchell User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Douglas K. Rand" Cc: Shaun Dwyer , Lanny Baron , Soeren Schmidt , "randall s. ehren" , freebsd-hardware , freebsd-stable@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: ATA problems (still) References: <200301151238.h0FCcD5e025929@spider.deepcore.dk> <1042677925.19537.42.camel@panda.FreeBSDsystems.COM> <3E2B4432.3080705@crystal.com.au> <874r83zldh.fsf@delta.meridian-enviro.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Douglas K. Rand wrote: >Shaun> Hi all... > >Hi! > >Shaun> I have a box with 6 WD 80Gb BB series drives on a 3ware >Shaun> Escalade raid controller doing raid 5. Every now and then a >Shaun> drives seem to drop from the array for no reason. Its always a >Shaun> different drive, on a different port. Mabye the later WD drives >Shaun> have some issues. Perhaps overly aggressive timing? > >We had very similiar problems with WD 100 GB (WD1000BB) disks on a >3ware controller. We'd get this error for no apparent reason: > > twe0: AEN: > >It turns out that there is some bios incompatability between the 3ware >controller and these WD disks. Once I found the right person at 3ware >and described my problem, he said that its the disks. We switched to >IBM disks and the problem went away. > >I have NO IDEA if the problem is the same on the WD800BB disks. > It sounds like it may be the same problem. Apparently at least several people have been having problems with the newer western digital drives. I just swapped mine out for a Maxtor and so far so good. My system has been up for three days without a problem. Hopefully that switch will get rid of that annoyance for me :-) -- Keith Mitchell Email: kmitch@guru.org PGP key available upon request To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jan 20 11:20: 7 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 552F437B401; Mon, 20 Jan 2003 11:20:06 -0800 (PST) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B07043EB2; Mon, 20 Jan 2003 11:20:05 -0800 (PST) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.6/8.12.6) with ESMTP id h0KJKDfc089338; Mon, 20 Jan 2003 14:20:14 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.2.0.9.0.20030120141925.03f35e10@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Mon, 20 Jan 2003 14:22:51 -0500 To: rand@meridian-enviro.com (Douglas K. Rand), Shaun Dwyer From: Mike Tancsa Subject: Re: ATA problems (still) Cc: freebsd-hardware@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <874r83zldh.fsf@delta.meridian-enviro.com> References: <3E2B4432.3080705@crystal.com.au> <200301151238.h0FCcD5e025929@spider.deepcore.dk> <1042677925.19537.42.camel@panda.FreeBSDsystems.COM> <3E2B4432.3080705@crystal.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: By Sentex Communications (lava/20020517) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 01:12 PM 20/01/2003 -0600, Douglas K. Rand wrote: >I have NO IDEA if the problem is the same on the WD800BB disks. I have a pair of WDC WD800BB-00CAA1, (ser # WD-WMADS1002605,WD-WMADS1002603) on a 2 port 3ware 7000 running in RAID one. FE7X 1.05.00.023 BIOS version: BE7X 1.08.00.036 that work really well to date. Its a rather busy server as well (dual MP2000) that gets brutalized on the CPU and disk. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jan 20 17: 7:16 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51F3B37B405 for ; Mon, 20 Jan 2003 17:07:15 -0800 (PST) Received: from pochacco.ex.dreamhost.com (pochacco.ex.dreamhost.com [66.33.206.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id B42BD43ED8 for ; Mon, 20 Jan 2003 17:07:14 -0800 (PST) (envelope-from jarod@haxial.com) Received: from haxial.com (localhost [127.0.0.1]) by pochacco.ex.dreamhost.com (Postfix) with SMTP id 6F0A890039 for ; Mon, 20 Jan 2003 17:07:14 -0800 (PST) Received: from 66.56.211.148 (SquirrelMail authenticated user jarod@haxial.com) by webmail.haxial.com with HTTP; Mon, 20 Jan 2003 17:07:14 -0800 (PST) Message-ID: <4830.66.56.211.148.1043111234.squirrel@webmail.haxial.com> Date: Mon, 20 Jan 2003 17:07:14 -0800 (PST) Subject: ACPI From: To: User-Agent: DreamHost Webmail MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Why is it when I try booting my 5.0 box without ACPI, I get a Fatal Trap 9? Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x58:0x3238 stack pointer = 0x10:0xed6 frame pointer = 0x10:0xf16 code segment = base 0xc00f0000, limit 0xffff, type 0x1b = DPL 0, pres 1, def32 0, gran 0 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) trap number = 9 panic: general protection fault Uptime: 1s I booted 4.7 fine without ACPI, so I don't see why I can't do the same in 5.x. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 21 12:48:32 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5057037B405 for ; Tue, 21 Jan 2003 12:48:30 -0800 (PST) Received: from web21507.mail.yahoo.com (web21507.mail.yahoo.com [66.163.169.18]) by mx1.FreeBSD.org (Postfix) with SMTP id AF35643E4A for ; Tue, 21 Jan 2003 12:48:29 -0800 (PST) (envelope-from nmblookup@yahoo.com) Message-ID: <20030121204829.27820.qmail@web21507.mail.yahoo.com> Received: from [213.169.51.2] by web21507.mail.yahoo.com via HTTP; Tue, 21 Jan 2003 12:48:29 PST Date: Tue, 21 Jan 2003 12:48:29 -0800 (PST) From: device timeout Subject: RZ1000 IDE controller problems To: freebsd-hardware@freebsd.org Cc: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org hi, I've been using freebsd for a while and I've had no problems right until 4.6-RELEASE, when after the installation, the machine wouldn't boot, because the ata driver could not attach my RZ1000 IDE controller. To be exact, it would detect ata1 (second IDE channel) as ata0 and try to boot off the CD-ROM drive attached there as master. What I did then was switch the cables around, so that my two hard drives are attached to ata1 (ata0, as detected by freebsd) and it would boot fine. Also, when booting off the kern.flp floppy, the ata driver attaches fine, finding every drive I have. After a while (and a lot of kernel recompiling) I switched to the wd driver, which I use now. Now, I'm trying to upgrade to 5.0R, but the wd is not present there. So my questions are: did anyone experience the same problems? Also, is there any way I could obtain the kernel configuration file for the boot floppy (kern.flp)? Here are some of the messages I get when trying to boot 5.0-RELEASE: ... atapci0: Busmastering DMA not supported atapci0: Busmastering DMA disabled ata2: at 0x1f0 on atapci0 (I have only one 2-channel IDE controller) device_probe_and_attach: ata2 attach returned 6 ... ata1 at port 0x376,0x170-0x177 irq 15 on isa0 ... acd0: failure to execute ATAPI packet command acd0: CDROM at ata1-master BIOSPIO after this, I get the prompt to input the root device manually. any ideas? ps: for direct replies, please write to maznio@krypton.wox.org best regards, anton __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 21 18:29:20 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AECF37B401 for ; Tue, 21 Jan 2003 18:29:19 -0800 (PST) Received: from mail.via.net (mail.via.net [209.81.9.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA5A243E4A for ; Tue, 21 Jan 2003 18:29:18 -0800 (PST) (envelope-from joe@via.net) Received: from [209.81.2.100] (HELO [209.81.2.100]) by mail.via.net (8.11.3/8.11.4) via ESMTP id for ; Tue, 21 Jan 2003 18:28:33 -0800 (PST) User-Agent: Microsoft-Entourage/10.1.0.2006 Date: Tue, 21 Jan 2003 18:29:18 -0800 Subject: Can some recommend a good raid controller? From: joe mcguckin To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I looking for a good (high performance & reliable) scsi-to-scsi standalone raid controller. It would be nice is there was a freebsd port of the config & control software also. Any suggestions? Thanks, Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 21 18:44:39 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A2FB37B401 for ; Tue, 21 Jan 2003 18:44:37 -0800 (PST) Received: from apnic.net (cumin.apnic.net [202.12.29.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id D097E43F1E for ; Tue, 21 Jan 2003 18:44:35 -0800 (PST) (envelope-from ggm@durian.apnic.net) Received: from durian.apnic.net (durian.apnic.net [202.12.29.252]) by apnic.net (8.12.1/8.12.1) with ESMTP id h0M2iWu3026538; Wed, 22 Jan 2003 12:44:33 +1000 Received: (from ggm@localhost) by durian.apnic.net (8.11.6/8.11.6) id h0M2iW520352; Wed, 22 Jan 2003 12:44:32 +1000 Date: Wed, 22 Jan 2003 12:44:32 +1000 From: George Michaelson Message-Id: <200301220244.h0M2iW520352@durian.apnic.net> To: netbsd-help@netbsd.org Subject: how to enable a new cardbus/pccard device? (ATEN USB 2.0 card) Cc: freebsd-hardware@freebsd.org X-AP-Spam-Status: No, hits=-98.9 required=5 X-AP-Spam-Score: -98.9 (notspam) CARRIAGE_RETURNS,SPAM_PHRASE_00_01,USER_IN_WHITELIST X-Scanned-By: MIMEDefang 2.15 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I bought an ATEN USB2.0 32bit cardbus card, model PU-212. when inserted into my NetBSD-current host with cardbus enabled in the kernel, it hangs, both for cold-boot inserted, and a hot insert into a running system. no messages. In FreeBSD 5.0, the device is safe, but not recognized. the probe details in dmesg are: cardbus0: Resource not specified in CIS: id=10, size=1000 cardbus0: (vendor=0x1033, dev=0x0035) at 0.0 irq 10 cardbus0: Resource not specified in CIS: id=10, size=1000 cardbus0: (vendor=0x1033, dev=0x0035) at 0.1 irq 10 cardbus0: Resource not specified in CIS: id=10, size=100 cardbus0: (vendor=0x1033, dev=0x00e0) at 0.2 irq 10 cbb0: CardBus card activation failed so I know its vendor:device 0x1033:0035 with a second sub-device instance at 0x00e0 (two USB ports, so two sub devices I guess) In RedHat 8.0, the device is fully recognized and functional. I am able to use a USB devs checker to see its an NEC chipset (unknown details) driving the USB component. the dmesg probe in this case is: cs: cb_alloc(bus 2): vendor 0x1033, device 0x0035 PCI: Enabling device 02:00.0 (0000 -> 0002) PCI: Enabling device 02:00.1 (0000 -> 0002) PCI: Enabling device 02:00.2 (0000 -> 0002) PCI: Setting latency timer of device 02:00.0 to 64 usb-ohci.c: USB OHCI at membase 0xd09ab000, IRQ 10 usb-ohci.c: usb-02:00.0, PCI device 1033:0035 usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found hub.c: 3 ports detected PCI: Setting latency timer of device 02:00.1 to 64 usb-ohci.c: USB OHCI at membase 0xd09b3000, IRQ 10 usb-ohci.c: usb-02:00.1, PCI device 1033:0035 usb.c: new USB bus registered, assigned bus number 3 hub.c: USB hub found hub.c: 2 ports detected hcd.c: ehci-hcd @ 02:00.2, PCI device 1033:00e0 hcd.c: irq 10, pci mem d09c6000 usb.c: new USB bus registered, assigned bus number 4 ehci-hcd.c: USB 2.0 support enabled, EHCI rev 0.95 hub.c: USB hub found hub.c: 5 ports detected (actually, removal can hang Linux, but insertion and cold boot is safe) Can somebody explain to me how I can go about constructing a valid cardbus/pccard entry for this device? cheers -George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jan 22 12:32:36 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C8DC37B401; Wed, 22 Jan 2003 12:32:31 -0800 (PST) Received: from isy.liu.se (isy.liu.se [130.236.48.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C104D43F1E; Wed, 22 Jan 2003 12:32:29 -0800 (PST) (envelope-from Kent.Palmkvist@home.se) Received: from kentspc.home.se (mail.isy.liu.se [130.236.48.3]) by isy.liu.se (8.11.4/8.11.4) with ESMTP id h0MKW7K21077; Wed, 22 Jan 2003 21:32:07 +0100 (MET) Message-Id: <5.2.0.9.0.20030122211513.032e5210@garm.isy.liu.se> X-Sender: kentp@garm.isy.liu.se X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Wed, 22 Jan 2003 21:29:36 +0100 To: device timeout , freebsd-hardware@FreeBSD.ORG, maznio@krypton.wox.org From: Kent Palmkvist Subject: Re: RZ1000 IDE controller problems Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <20030121204829.27820.qmail@web21507.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, Please take a look at the gnats database, especially the two entries http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/42228 http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/43222 which both discusses this problem, with one quick and dirty solution (my), and one more elaborate version. The quick and dirty solution does not work on 4.7-RELEASE and 5.0. Please be advised that my tests with 4.7-RELEASE indicates that it does not even recognize the RZ1000 controller when booting the floppy (which 4.6-RELEASE obviously does). I have a Plato board, which is set to disable the pci ata controller. This board runs both 4.7-STABLE and 5.0-STABLE with the ata driver without problems (but not using the RZ1000 chip). Maybe you can disable the RZ1000 in the same way. best regards /Kent At 12:48 2003-01-21 -0800, device timeout wrote: >hi, > >I've been using freebsd for a while and I've had no >problems >right until 4.6-RELEASE, when after the installation, >the machine >wouldn't boot, because the ata driver could not attach >my RZ1000 >IDE controller. > >To be exact, it would detect ata1 (second IDE channel) >as ata0 >and try to boot off the CD-ROM drive attached there as >master. >What I did then was switch the cables around, so that >my two hard >drives are attached to ata1 (ata0, as detected by >freebsd) and >it would boot fine. Also, when booting off the >kern.flp floppy, >the ata driver attaches fine, finding every drive I >have. > >: >So my questions are: did anyone experience the same >problems? >Also, is there any way I could obtain the kernel >configuration file >for the boot floppy (kern.flp)? > >Here are some of the messages I get when trying to >boot 5.0-RELEASE: > ... > atapci0: Busmastering DMA not supported > atapci0: Busmastering DMA disabled > ata2: at 0x1f0 on atapci0 (I have only one >2-channel IDE controller) > device_probe_and_attach: ata2 attach returned 6 > ... > ata1 at port 0x376,0x170-0x177 irq 15 on isa0 > ... > acd0: failure to execute ATAPI packet command > acd0: CDROM at ata1-master >BIOSPIO >after this, I get the prompt to input the root device >manually. > >any ideas? > >ps: for direct replies, please write to >maznio@krypton.wox.org > >best regards, anton > >__________________________________________________ >Do you Yahoo!? >Yahoo! Mail Plus - Powerful. Affordable. Sign up now. >http://mailplus.yahoo.com > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jan 23 6:53:22 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB89D37B401 for ; Thu, 23 Jan 2003 06:53:20 -0800 (PST) Received: from mailer.berkom.de (mailer.berkom.de [141.39.13.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B94CD43F13 for ; Thu, 23 Jan 2003 06:53:17 -0800 (PST) (envelope-from wjontofs@berkom.de) Received: from karma (karma.t33.berkom.de [141.39.27.116]) by mailer.berkom.de (8.12.6/8.12.6) with ESMTP id h0NErCK8012147; Thu, 23 Jan 2003 15:53:14 +0100 (MET) Content-Type: text/plain; charset="iso-8859-1" From: Walter Jontofsohn Organization: T-Systems NovaGmbH To: Bruce Evans Subject: Re: can't boot/install freebsd from cdrom/floppy - serverworks g Date: Thu, 23 Jan 2003 17:58:02 +0100 User-Agent: KMail/1.4.3 References: <20030114080356.J14218-100000@gamplex.bde.org> In-Reply-To: <20030114080356.J14218-100000@gamplex.bde.org> Cc: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200301231758.02390.wjontofs@berkom.de> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > On Mon, 13 Jan 2003, John Baldwin wrote: > > On 13-Jan-2003 Walter wrote: > > > i've problems installing freebsd on System with ServerWorks GC SL > > > -Chipset, Pentium 4, LSI Logic MPT (53c1030) SCSI-Controller > > > > > > Booting with floppy kern.flp from 4.7-release, not even the bootstr= ap > > > loader works, then i tried from 5.0rc3 - i got > > > > > > fatal trap 10: trace trap while in vm86 mode > > > instruction pointer=3D0xf000:0xf842 > > > stack pointer =3D 0x0:0xff8 > > > frame pointer =3D 0x0:0x0 > > > code segment =3D base 0x0, linit 0x0, type 0x0 > > > =3D DPL 0, pres 0, def32 0, gran 0 > > > processor eflags =3D interupt enabled, vm86 IOPL =3D 0 > > > current process =3D 0 () > > > trap number =3D 10 > > > panic: trace trap > > > Uptime: 1s > > > > > > I thought probably a hardware failure, > > > but i tried to install Linux Redhat 8.0, without problems ?! > > > > > > Any hints ? > > Try setting hw.hasbrokenint12 in the loader. this means 'set hw.hasbrokenint12' ? if yes, the result is unfortunately= the=20 same as above, if no, how should i do this ? Further down you write, that the loader doesen't get the correct memsize,= is=20 it possible/useful to hand over the memory size (or is this for vm86=20 special?) best regards, Walter Jontofsohn > > > You have a buggy BIOS it seems. I'm not sure why you are getting > > that kernel trap though. That is a really weird trap. > > int 0x12 is reported to be broken for some new BIOSes. I think the > bug is just that getmemsize() uses vm86_intcall(0x12, ...) before > enough is initialized for vm86_intcall(0x12, ...) to work. It's not > clear what is needed for it to work, but getmemsize() clearly doesn't > do enough in RELENG_4 -- it doesn't map pages into the vm86 page table. > Old BIOSes implement int 0x12 by just returning the result of reading > the word at 0x40:0x13 or thereabouts. I'm not sure how even that much > worked (do we map the first page specially?). Newer BIOSes may well > do much more complicated things. Hopefully there is a standard that > prevents them arbitrarily using things that don't work in vm86 mode. > > Rev.1.544 has some too-large changes which attempt to fix this > automatically, but it caused panics and was replaced by simpler changes > and a non-automatically set loader flag in rev.1.549. > > Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jan 23 7:59: 4 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F4C337B401 for ; Thu, 23 Jan 2003 07:59:03 -0800 (PST) Received: from gicco.homeip.net (dclient80-218-75-162.hispeed.ch [80.218.75.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2C5B43F13 for ; Thu, 23 Jan 2003 07:58:56 -0800 (PST) (envelope-from hampi@rootshell.be) Received: from localhost.here (idefix@gicco.homeip.net [127.0.0.1]) by gicco.homeip.net (8.12.6/8.12.6) with ESMTP id h0NFwtQm001148 for ; Thu, 23 Jan 2003 16:58:55 +0100 (CET) (envelope-from hampi@rootshell.be) Received: (from idefix@localhost) by localhost.here (8.12.6/8.12.6/Submit) id h0NFwsjk001147 for freebsd-hardware@freebsd.org; Thu, 23 Jan 2003 16:58:54 +0100 (CET) X-Authentication-Warning: localhost.here: idefix set sender to hampi@rootshell.be using -f Date: Thu, 23 Jan 2003 16:58:54 +0100 From: Hanspeter Roth To: freebsd-hardware@freebsd.org Subject: accessing second mouse in application Message-ID: <20030123155854.GA1094@gicco.homeip.net> Reply-To: freebsd-hardware@freebsd.org Mail-Followup-To: freebsd-hardware@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, I have a PS/2 mouse which is used by X11. Now I'd like to connect a serial mouse of which I'd like to receive just left and right button activation in an application. The mouse should be ignored by X11. How is this best achieved? I think any moused is connected to /dev/sysmouse. So this will probably also go to X11. Should I take a part of moused and rearrange it somehow? Or should I directly access /dev/cuaa1? -Hanspeter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jan 23 20:21:20 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5503137B401 for ; Thu, 23 Jan 2003 20:21:18 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB1DF43F18 for ; Thu, 23 Jan 2003 20:21:16 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id PAA18617; Fri, 24 Jan 2003 15:21:02 +1100 Date: Fri, 24 Jan 2003 15:22:50 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Walter Jontofsohn Cc: freebsd-hardware@freebsd.org Subject: Re: can't boot/install freebsd from cdrom/floppy - serverworks g In-Reply-To: <200301231758.02390.wjontofs@berkom.de> Message-ID: <20030124150506.P4290-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 23 Jan 2003, Walter Jontofsohn wrote: > > On Mon, 13 Jan 2003, John Baldwin wrote: > > > On 13-Jan-2003 Walter wrote: > > > > i've problems installing freebsd on System with ServerWorks GC SL > > > > -Chipset, Pentium 4, LSI Logic MPT (53c1030) SCSI-Controller > > > > > > > > Booting with floppy kern.flp from 4.7-release, not even the bootstrap > > > > loader works, then i tried from 5.0rc3 - i got > > > > > > > > fatal trap 10: trace trap while in vm86 mode > > > > instruction pointer=0xf000:0xf842 > > > > stack pointer = 0x0:0xff8 > > > > frame pointer = 0x0:0x0 > > > > code segment = base 0x0, linit 0x0, type 0x0 > > > > = DPL 0, pres 0, def32 0, gran 0 > > > > processor eflags = interupt enabled, vm86 IOPL = 0 > > > > current process = 0 () > > > > trap number = 10 > > > > panic: trace trap > > > > Uptime: 1s > > > > > > > > I thought probably a hardware failure, > > > > but i tried to install Linux Redhat 8.0, without problems ?! > > > > > > > > Any hints ? > > > > Try setting hw.hasbrokenint12 in the loader. > > this means 'set hw.hasbrokenint12' ? if yes, the result is unfortunately the > same as above, if no, how should i do this ? Er, set it to 1? I'm not sure what the loader does for null set commands since I don't use it myself, but I guess it would set the variable to "" if anything. The kernel would then misparse "" as the number 0 (boolean false), so thenull set command would have no effect except possubly to turn off any previous setting. > Further down you write, that the loader doesen't get the correct memsize, is This doesn't seem to be in the quoted mail and I don't remember saying it in this thread. > it possible/useful to hand over the memory size (or is this for vm86 > special?) One possible fix is doing it all in the loader. I prefer to do it only in the kernel, since vm86 calls need to work for other reasons. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jan 24 5:50:35 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F4E637B401 for ; Fri, 24 Jan 2003 05:50:33 -0800 (PST) Received: from mailer.berkom.de (mailer.berkom.de [141.39.13.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D94F243F3F for ; Fri, 24 Jan 2003 05:50:31 -0800 (PST) (envelope-from wjontofs@berkom.de) Received: from karma (karma.t33.berkom.de [141.39.27.116]) by mailer.berkom.de (8.12.6/8.12.6) with ESMTP id h0ODoSK8005849; Fri, 24 Jan 2003 14:50:29 +0100 (MET) Content-Type: text/plain; charset="iso-8859-1" From: Walter Jontofsohn Organization: T-Systems NovaGmbH To: Bruce Evans Subject: Re: can't boot/install freebsd from cdrom/floppy - serverworks g Date: Fri, 24 Jan 2003 16:55:18 +0100 User-Agent: KMail/1.4.3 References: <20030124150506.P4290-100000@gamplex.bde.org> In-Reply-To: <20030124150506.P4290-100000@gamplex.bde.org> Cc: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200301241655.18648.wjontofs@berkom.de> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Am Freitag, 24. Januar 2003 05:22 schrieben Sie: > On Thu, 23 Jan 2003, Walter Jontofsohn wrote: > > > On Mon, 13 Jan 2003, John Baldwin wrote: > > > > On 13-Jan-2003 Walter wrote: > > > > > i've problems installing freebsd on System with ServerWorks GC = SL > > > > > -Chipset, Pentium 4, LSI Logic MPT (53c1030) SCSI-Controller > > > > > > > > > > Booting with floppy kern.flp from 4.7-release, not even the > > > > > bootstrap loader works, then i tried from 5.0rc3 - i got > > > > > > > > > > fatal trap 10: trace trap while in vm86 mode > > > > > instruction pointer=3D0xf000:0xf842 > > > > > stack pointer =3D 0x0:0xff8 > > > > > frame pointer =3D 0x0:0x0 > > > > > code segment =3D base 0x0, linit 0x0, type 0x0 > > > > > =3D DPL 0, pres 0, def32 0, gran 0 > > > > > processor eflags =3D interupt enabled, vm86 IOPL =3D 0 > > > > > current process =3D 0 () > > > > > trap number =3D 10 > > > > > panic: trace trap > > > > > Uptime: 1s > > > > > > > > > > I thought probably a hardware failure, > > > > > but i tried to install Linux Redhat 8.0, without problems ?! > > > > > > > > > > Any hints ? > > > > > > Try setting hw.hasbrokenint12 in the loader. > > > > this means 'set hw.hasbrokenint12' ? if yes, the result is unfortuna= tely > > the same as above, if no, how should i do this ? > > Er, set it to 1? I'm not sure what the loader does for null set comman= ds > since I don't use it myself, but I guess it would set the, that a haven= 't to=20 do it as a boot option variable to "" if > anything. The kernel would then misparse "" as the number 0 (boolean > false), so thenull set command would have no effect except possubly to = turn > off any previous setting. Thank you very much for the help, the installation was now possible! =2E.... > > it possible/useful to hand over the memory size (or is this for vm86 > > special?) > > One possible fix is doing it all in the loader. I prefer to do it only= in > the kernel, since vm86 calls need to work for other reasons. By now,i put the option into /boot/loader.conf, but, can i fix it in the=20 kernel too ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jan 24 10:38:31 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D35A37B401 for ; Fri, 24 Jan 2003 10:38:30 -0800 (PST) Received: from kurush.osdn.org.ua (external.osdn.org.ua [212.40.34.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id B075F43F1E for ; Fri, 24 Jan 2003 10:38:28 -0800 (PST) (envelope-from never@kurush.osdn.org.ua) Received: from kurush.osdn.org.ua (never@localhost [127.0.0.1]) by kurush.osdn.org.ua (8.12.6/8.12.6) with ESMTP id h0OIcRWK063216 for ; Fri, 24 Jan 2003 20:38:27 +0200 (EET) (envelope-from never@kurush.osdn.org.ua) Received: (from never@localhost) by kurush.osdn.org.ua (8.12.6/8.12.6/Submit) id h0OIcRqv063215 for freebsd-hardware@FreeBSD.org; Fri, 24 Jan 2003 20:38:27 +0200 (EET) Date: Fri, 24 Jan 2003 20:36:49 +0200 From: Alexandr Kovalenko To: freebsd-hardware@FreeBSD.org Cc: freebsd-stable@FreeBSD.org Subject: Tamarack Gigabit Ethernet driver needed (v_id=0x13f0, d_id=0x1021) Message-ID: <20030124183649.GA61762@nevermind.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.5.1i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [Excuse me for such huge crosspost, I just don't know which list is more appropriate for this question] I'm running FreeBSD 4.7-RELEASE-p3 I need driver for ${Subject} ethernet controller. I have found one: http://www.icplus.com.tw/Data/driver/TC902X_FreeBSD.zip (you have to do little trick to get the actual driver: download .zip file, extract it, rename Readme.txt to rio.tgz, then extract it. Only then you will get actual driver source). It does not work, it says: rio0: port 0x3000-0x30ff mem 0xf5021000-0xf50211ff irq 11 at device 11.0 on pci2 rio0: Ethernet address: 00:50:fc:48:9b:da rio0: MII without any phy! device_probe_and_attach: rio0 attach returned 6 Could it be fixed and if yes, then how? Thank you! -- NEVE-RIPE, will build world for food Ukrainian FreeBSD User Group http://uafug.org.ua/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jan 25 12:26:25 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29AA837B401 for ; Sat, 25 Jan 2003 12:26:25 -0800 (PST) Received: from gicco.homeip.net (dclient80-218-75-162.hispeed.ch [80.218.75.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B0C943F13 for ; Sat, 25 Jan 2003 12:26:13 -0800 (PST) (envelope-from hampi@rootshell.be) Received: from localhost.here (idefix@gicco.homeip.net [127.0.0.1]) by gicco.homeip.net (8.12.6/8.12.6) with ESMTP id h0PKQBXv000986 for ; Sat, 25 Jan 2003 21:26:11 +0100 (CET) (envelope-from hampi@rootshell.be) Received: (from idefix@localhost) by localhost.here (8.12.6/8.12.6/Submit) id h0PKQ7uc000985 for freebsd-hardware@freebsd.org; Sat, 25 Jan 2003 21:26:07 +0100 (CET) X-Authentication-Warning: localhost.here: idefix set sender to hampi@rootshell.be using -f Date: Sat, 25 Jan 2003 21:26:07 +0100 From: Hanspeter Roth To: freebsd-hardware@freebsd.org Subject: receiving via parallel port Message-ID: <20030125202607.GA963@gicco.homeip.net> Reply-To: freebsd-hardware@freebsd.org Mail-Followup-To: freebsd-hardware@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, can I receive data via the parallel port? Are there some examples? -Hanspeter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message