Re: Request for testers of new ATA driver patches
On Wed, Mar 06, 2002 at 11:06:48PM -0600, Ryan K. Losh wrote: > > Mine doesn't seem to be. I've got a HP Pavilion ZU-1175 laptop that > physically is two separate parts: a docking station with a dual > channel (ata2 and ata3) PCI IDE controller and 2 IDE drives (separate > DVD and CDRW drives). The only time FreeBSD recognizes these drives > is when I boot the computer ON THE DOCKING STATION. It looks like the > IDE controller is a separate PCI device which is "hot-plugged" > whenever docking/undocking the laptop. Any idea if hot-plug PCI > devices are supported in FreeBSD? This is entierly unrelated to the ATA patch. The problem in this case is that you need ACPI support in the OS (coming in 5.0) and support for docking within ACPI as well as better device removal support (I don't know if anyone is working on that or not.) The patch should allow you to add and remove the individual ATA devices using atacontrol so long as you are docked at boot. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 msg42174/pgp0.pgp Description: PGP signature
wi0 problems under latest STABLE
I've just updated a my 4.5-STABLE laptop to the latest RELENG_4. It contains a Lucent Orinoco card which turns up as wi0. It was working with a STABLE dated Jan 28 2002. With the build from this evening's cvsup, I'm getting time outs on wi0. This is the /etc/pccard.conf which I was using: [dan@laptop:~] $ less /etc/pccard.conf # Lucent WaveLAN/IEEE card "Lucent Technologies" "WaveLAN/IEEE" config 0x1 "wi" ? insert /etc/pccard_ether $device start remove /etc/pccard_ether $device stop insert wicontrol -i $device -p 3 insert wicontrol -i $device -k "4gRp1" What did I miss? Under the latest build, I get this: laptop /kernel: wi0: timeout in wi_cmd 11; event status 8000 If it's any help: wi0: at port 0x240-0x27f irq 3 slot 0 on pccard0 wi0: 802.11 address: 00:02:2d:0e:66:bd wi0: using Lucent chip or unknown chip It doesn't seem to be affecting the traffic, it's just a repeating message. If I don't use the above pccard.conf, the card doesn't seem to work very well at all. -- Dan Langille The FreeBSD Diary - http://freebsddiary.org/ - practical examples To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: wi0 problems under latest STABLE
On Thu, Mar 07, 2002 at 12:14:41AM -0500, Dan Langille wrote: > I've just updated a my 4.5-STABLE laptop to the latest RELENG_4. It > contains a Lucent Orinoco card which turns up as wi0. It was working with > a STABLE dated Jan 28 2002. With the build from this evening's cvsup, I'm > getting time outs on wi0. > > This is the /etc/pccard.conf which I was using: > > [dan@laptop:~] $ less /etc/pccard.conf > # Lucent WaveLAN/IEEE > card "Lucent Technologies" "WaveLAN/IEEE" > config 0x1 "wi" ? > insert /etc/pccard_ether $device start > remove /etc/pccard_ether $device stop > > insert wicontrol -i $device -p 3 > insert wicontrol -i $device -k "4gRp1" > > What did I miss? > > Under the latest build, I get this: > >laptop /kernel: wi0: timeout in wi_cmd 11; event status 8000 > > If it's any help: > > wi0: at port 0x240-0x27f irq 3 slot 0 on pccard0 > wi0: 802.11 address: 00:02:2d:0e:66:bd > wi0: using Lucent chip or unknown chip > > It doesn't seem to be affecting the traffic, it's just a repeating > message. If I don't use the above pccard.conf, the card doesn't seem to > work very well at all. It's fairly harmless (previously the command just failed without saying anything), it might be worth trying to raise the value of WI_DELAY in if_wireg.h. I'd suggest trying 100 and if that fixes it, lower it to see if you can find a better lower bound then 5. If that doesn't work, it might be worth trying to raise WI_TIMEOUT, but 500ms is a long time for a network adaptor. I'm not sure what you mean about not using the pccard.conf entry. The top part is exactly what is in /etc/defaults/pccard.conf and it won't work if you don't set your wep key and enable ad-hoc mode if that's how your network is configured. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 msg42176/pgp0.pgp Description: PGP signature
installworld is broken?
Hello I've installed FreeBSD 4.4-RELEASE and wanted to uprade to p8. buildworld, buildkernel and installkernel went just fine, but problem is when i try to installworld. It says (at various places, where some programs are needeed to run) that file not found. It's in groff's Makefile, because he can't find expr It's in fortunes Makefile, because he can't find cap_mkdb and ex. Of course this apss are in /bin, /sbin, usr/bin etc. And of course my PATH enviroment is set correctly. What's going on? I even deleted sources and tried to build 4.5 p1 and 4.5-STABLE (from that 4.4-RELEASE). I'm "worlding" since years and that's the first time when something doesn't work. Thanks in Advance and please answer directly to me, because i'm not subscriber or theese groups. Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: patch (was Re: reproducable panic with python)
> This should fix it. Included below is the test program to reproduce > the panic and the patch that will fix it. Yep - fixes the problem on -current anyway. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message