Re: Updated Driver for 3945ABG ...
Gilbert Cao wrote: > > I have put a custom version of mine from your last package here: > http://www.bsdmon.com/download/20070121-wpi-freebsd.tar.gz > > What I have mainly done is to make the package compile and work (for me > a least) on 6.2-RELEASE (and possibly other 6.x ?). This is to confirm that for me this above 20070121 driver works, while the driver from B. Close 20070125 does *not* work. In fact i have downloaded a lot of things using this driver, so in my experience it works *very* well. It even associates better with the access point than the Linux driver, which loses connection from time to time. My laptop is a Vaio VGN C1, and for reference i have added some dmesg stuff with the above two drivers. Both produce error messages, but one definitely works. This is with 20070121-wpi-freebsd on a Sony Vaio VGN-C1S (note that 20070125-wpi-freebsd does not work for me) rose# kldload if_wpi rose# dmesg . wpi0: mem 0xcc00-0xcc000fff irq 18 at device 0.0 on pci6 bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. pi0: Ethernet address: 00:18:de:ad:78:b1 wpi0: [GIANT-LOCKED] wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps rose# ifconfig wpi0 up rose# ifconfig ... wpi0: flags=8802 mtu 1500 ether 00:18:de:ad:78:b1 media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier ssid "" channel 1 authmode OPEN privacy OFF txpowmax 100 bmiss 7 protmode CTS rose# dmesg ... pi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps wpi0: fatal firmware error wpi0: configure command failed wpi0: could not configure device still running dhclient rose# dhclient wpi0 DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 3 DHCPOFFER from 192.168.1.1 DHCPREQUEST on wpi0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.1 bound to 192.168.1.107 -- renewal in 43200 seconds. and it works perfectly OK for me. This is what 20070125-wpi-freebsd gives: an 28 00:47:49 kernel: wpi0: mem 0xcc00-0xcc000fff irq 18 at device 0.0 on pci6 Jan 28 00:47:49 kernel: bus_dmamem_alloc failed to align memory properly. Jan 28 00:47:49 last message repeated 6 times Jan 28 00:47:49 kernel: wpi0: Ethernet address: 00:18:de:ad:78:b1 Jan 28 00:47:49 kernel: wpi0: 11a rates: Jan 28 00:47:49 kernel: wpi0: 11b rates: Jan 28 00:48:19 kernel: firmware_get: failed to load firmware image wpi_fw Jan 28 00:48:19 kernel: wpi0: could not load firmware image 'wpi_fw' Jan 28 00:49:12 kernel: firmware_get: failed to load firmware image wpi_fw Jan 28 00:49:12 kernel: wpi0: could not load firmware image 'wpi_fw' Jan 28 00:49:12 dhclient[1351]: send_packet: Network is down Jan 28 00:49:15 dhclient[1351]: send_packet: Network is down -- Michel TALON ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freebsd-hackers Digest, Vol 200, Issue 7
Hugo Alfredo Cano Bravo wrote: I want to be a member. What can I do.? http://lists.freebsd.org and please, don't top post! -- Thanks, Joe Holden Telephone: +44 (0) 207 100 9593 Email: [EMAIL PROTECTED] Website: http://www.joeholden.co.uk IRC: [EMAIL PROTECTED]/#FreeBSD ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: freebsd-hackers Digest, Vol 200, Issue 7
I want to be a member. What can I do.? From: [EMAIL PROTECTED] Reply-To: freebsd-hackers@freebsd.org To: freebsd-hackers@freebsd.org Subject: freebsd-hackers Digest, Vol 200, Issue 7 Date: Sun, 28 Jan 2007 12:00:39 + (UTC) Send freebsd-hackers mailing list submissions to freebsd-hackers@freebsd.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.freebsd.org/mailman/listinfo/freebsd-hackers or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of freebsd-hackers digest..." Today's Topics: 1. Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller (Gilbert Cao) 2. Review request: new OMNIKEY CardMan 4040 driver (Daniel Roethlisberger) 3. sysctl(3) interface (Daniel Rudy) 4. how to determine if we are building lib32 in Makefile? (Rong-en Fan) 5. Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller (Sam Fourman Jr.) 6. Re: atacontrol kernel crash (atausb?) (M. Warner Losh) 7. Re: unique hardware identification (Daniel Rudy) -- Message: 1 Date: Sat, 27 Jan 2007 11:19:00 +0100 From: Gilbert Cao <[EMAIL PROTECTED]> Subject: Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller To: Benjamin Close <[EMAIL PROTECTED]> Cc: Massimo Lusetti <[EMAIL PROTECTED]>, Florent Thoumie <[EMAIL PROTECTED]>, freebsd-hackers@freebsd.org, [EMAIL PROTECTED], Attilio Rao <[EMAIL PROTECTED]>, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], Max Laier <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii" On Fri, Jan 26, 2007 at 11:09:51PM +1030, Benjamin Close wrote: > Hi Gilbert, >Thanks for the custom version. I've integrated the changes into the > driver I'm working on. > For those wanting to test out the driver which is now fully up to date > with all change from NetBSD & OpenBSD - and has a few minor improvements > over them, grab it from: > > http://www.clearchain.com/~benjsc/download/ > > File is: 20070125-wpi-freebsd.tar.gz > > Full instructions on how to build / install the driver are in the README > in the tar file. > > This should work both under -current and 6.2-Stable now. > > Info about the driver and what's working/broken can be found at: > > http://www.clearchain.com/wiki/wpi > > Cheers, >Benjamin I have tried the new 20070125 version. However, I did not manage to make work. At least, it compiles. I have installed, both wpi_fw.ko and the if_wpi.ko, as the README said. wpi_fw.ko lies in /boot/modules and if_wpi.ko in /boot/kernel. When, I "kldload if_wpi", here is a small sample of /var/log/messages Jan 27 10:30:39 vaio kernel: wpi0: mem 0xcc00-0xcc000fff irq 18 at device 0.0 on pci6 Jan 27 10:30:39 vaio kernel: bus_dmamem_alloc failed to align memory properly. Jan 27 10:30:39 vaio last message repeated 6 times Jan 27 10:30:39 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a Jan 27 10:30:39 vaio kernel: wpi0: [GIANT-LOCKED] Jan 27 10:30:39 vaio kernel: wpi0: 11a rates: Jan 27 10:30:39 vaio kernel: wpi0: 11b rates: Jan 27 10:30:40 vaio kernel: firmware_get: failed to load firmware image wpi_fw Jan 27 10:30:40 vaio kernel: wpi0: could not load firmware image 'wpi_fw' Jan 27 10:30:40 vaio kernel: firmware_get: failed to load firmware image wpi_fw Jan 27 10:30:40 vaio kernel: wpi0: could not load firmware image 'wpi_fw' Jan 27 10:32:19 vaio kernel: firmware_get: failed to load firmware image wpi_fw Jan 27 10:32:19 vaio kernel: wpi0: could not load firmware image 'wpi_fw' In kldstat, both modules are loaded. Then, I have "kldunload if_wpi" (and if_wpi seems to be reload, automatically, I don't know why). Same problem, it seems that wpi_fw could not be load (found ?). As a result, no AP is "associated". After a fresh reboot, I have reinstall the custom 20070121 version of mine, and all returns OK. Another strange thing: when "kldload if_wpi" with 20070121 version, and then kldstat, I don't see "wpi_ucode". It seems that wpi_ucode.ko does not need to be loaded, in my case. My wpi_ucode.ko lies in /boot/modules After another fresh reboot, I first moved wpi_ucode.ko to another place. When I "kldload if_wpi", I got the following message: Jan 27 09:47:16 vaio kernel: wpi0: mem 0xcc00-0xcc000fff irq 18 at device 0.0 on pci6 Jan 27 09:47:16 vaio kernel: bus_dmamem_alloc failed to align memory properly. Jan 27 09:47:16 vaio last message repeated 6 times Jan 27 09:47:16 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a Jan 27 09:47:16 vaio kernel: wpi0: [GIANT-LOCKED] Jan 27 09:47:16 vaio kernel: wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Jan 27 09:4
Re: installing fbsd from foreign system
Le Sunday 28 January 2007 16:22, Oliver Fromme a écrit :
> Another possibility is to prepare a boot image, i.e. a file
> containing boot sector and a UFS root partition with
> wverything needed for bootstrapping (/boot/loader etc.,
> kernel, base system). It doesn't have to cover the whole
> disk, it should be just large enough for a base system and
> some support software. It should contain a script which
> configures the rest of the disk when it's booted (e.g.
> set up remaining disk space, fetch packages from the net,
> whatever).
>
> >From within your Linux deployment process, simply copy
>
> the image to the beginning of the hard disk, then reboot.
>
Oone good *starting point* is the depenguinator
(http://www.daemonology.net/depenguinator/), which I used some time ago.
There are rough edges, but at least, it gives a way to convert a PC running
some version of Linux to FreeBSD. (in my experience, I had to resort to
manual tweakings to get the final BSD to run).
TfH
--
Internet users, on the other hand, are perhaps not dealt
with harshly enough; ultimately, the only way to secure the
Internet is to ensure that these users secure their systems.
Harvard Law Review, june06 ("immunizing the internet")
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: unique hardware identification
On Sun, 2007-Jan-28 10:39:36 -0600, Jon Passki wrote: >If the machine is a PXE-compliant device [2], it should have a GUID/ >UUID [1] available. This can be exposed by sysutil/hal [3] via the >smbios.system.uuid field. You can also get it via kenv(8) without needing any ports: # kenv smbios.system.uuid 9F345F4F-BEFC-D431-1340-61235A56DEF9 -- Peter Jeremy pgpYtgc8mneB0.pgp Description: PGP signature
Re: installing fbsd from foreign system
* Volker <[EMAIL PROTECTED]> [20070128 14:03]: > I need to find a way to integrate the FreeBSD install process into > their current deployment system. Currently their install process is > running from a Linux install system which does the partitioning, > make_fs etc. Sounds like you could use a depenguinator... http://www.daemonology.net/depenguinator/ qvb -- pica ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: unique hardware identification
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 27, 2007, at 23:35 , Daniel Rudy wrote: At about the time of 12/19/2006 7:19 AM, Devon H. O'Dell stated the following: 2006/12/19, Koen Martens <[EMAIL PROTECTED]>: Hi All, I was wondering, if something like a unique hardware identification would be possible on FreeBSD. [snip] If the machine is a PXE-compliant device [2], it should have a GUID/ UUID [1] available. This can be exposed by sysutil/hal [3] via the smbios.system.uuid field. The sysutil/hal port, though, requires a decent amount of dependencies. You might want to give the pkg install a try first. (I happened to have a lot of those ports installed, so it was not an issue for me.) # dbus-daemon --system # hald --verbose=yes 16:39:24.418 [I] hald.c:469: hal 0.5.8 16:39:24.418 [I] hald.c:478: Will daemonize 16:39:24.418 [I] hald.c:479: Becoming a daemon # hal-get-property --udi /org/freedesktop/Hal/devices/computer --key smbios.system.uuid 64837263-8462-7493-1212- Cheers, Jon [1] http://en.wikipedia.org/wiki/Globally_Unique_Identifier [2] http://en.wikipedia.org/wiki/Preboot_Execution_Environment [3] http://www.freshports.org/sysutils/hal/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFvNHRZpJsLIS+QSIRAvygAJwMqBHhdPhCwkaAnEo/MSBsbeig+QCeMc+c HR4Wcvmt4kcZyaD1S76Hby4= =YQQw -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: installing fbsd from foreign system
Volker wrote: > Probably I will be proud to have the chance to support one of > Europe's major players in root server hosting for deploying FreeBSD > as a target platform for their customers. We've done things like that before, too. > I need to find a way to integrate the FreeBSD install process into > their current deployment system. Currently their install process is > running from a Linux install system which does the partitioning, > make_fs etc. > > I found several options to integrate: > > 1) install a FAT partition, copy a bootable install system in it, > boot (bsdboot) an install kernel from FAT partition and begin > (unattended) installation (including fdisk, labeling, make_fs'ing). > > Any thoughts on that? I think this might be the best option. I don't think you can boot a FreeBSD system from a FAT file system. > 2) fdisk'ing, labeling and make fs from the Linux system if there > are any ported label + fs tools for Linux available - are they? No. > 3) create an ext2 partition and copy the fbsd install system into it > and boot from there to begin install process (same as 1 except > running from ext2fs). Does a FreeBSD kernel support booting from > ext2fs (using mdfs for root-fs)? If so, how? That _might_ work, but I haven't tried it myself. > Any better thoughts? Any hints on how to proceed with one of the 3 > options? PXE or anything else is not an option. I need to integrate > the install process into an existing deployment system. PXE would really be the cleanest and easiest way, and it's also very easy to maintain. If you can't do that, maybe you need to re-think your existing deplayment process and make it more flexible ...? Another possibility is to prepare a boot image, i.e. a file containing boot sector and a UFS root partition with wverything needed for bootstrapping (/boot/loader etc., kernel, base system). It doesn't have to cover the whole disk, it should be just large enough for a base system and some support software. It should contain a script which configures the rest of the disk when it's booted (e.g. set up remaining disk space, fetch packages from the net, whatever). >From within your Linux deployment process, simply copy the image to the beginning of the hard disk, then reboot. > I suspect to be the UFS problem to be the biggest one when it comes > to deal with that from a running Linux system. Right, Linux support for UFS is weak, not to mention UFS2. > Also as anything needs to run unattended, how do I set FreeBSD to > try DHCP on any local interface the kernel can find? The FreeBSD Handbook covers that topic (chapter 25.5). Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783 Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH & Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "We, the unwilling, led by the unknowing, are doing the impossible for the ungrateful. We have done so much, for so long, with so little, we are now qualified to do anything with nothing." -- Mother Teresa ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how to determine if we are building lib32 in Makefile?
On 1/28/07, Rong-en Fan <[EMAIL PROTECTED]> wrote:
I'm working on wide character support in base's ncurses. For some
reason, I have to make lib/ncurses/ncursesw to include ncurses.h from
its object directory. However, current lib32 uses something like
cc ... -I${LIB32TMP}/usr/includes ... -IFROM_NCURSES_MAKEFILE ...
Right now, I have the following:
.if ${.TARGET} == "installincludes" && !empty(${DESTDIR:M*/lib32/*})
INCS= ${HEADERS} ${SRCHDRS}
INCSLINKS= curses.h ${INCLUDEDIR}/ncurses.h
.endif
It works, but it's really ugly. Is there any other way to do this?
Oops, it's wrong. Now I have "-DWORLD32" in LIB32MAKE and
the following lines in lib/ncurses/Makefile
.if !defined(WORLD32)
INCS= ${HEADERS} ${SRCHDRS}
INCSLINKS= curses.h ${INCLUDEDIR}/ncurses.h
.endif
While make universe is still running, but I have amd64, i386, pc98
work and on my -current i386 box. The resulting world works well
(tested by mutt).
I'm not sure if this is the best way to handle this. I noticed that
Dragonfly has something like
# include files are not installed when building bootstrap programs
.if !defined(BOOTSTRAPPING)
realinstall: installincludes
.ORDER: beforeinstall installincludes
.endif
in bsd.incs.mk.
For ncurses, since the include path for 32-bit includes are specified
in LIB32POSTFLAGS, which is part of ${CC}. When building ncurses +
ncursesw, I need different versions of ncurses.h (for runtime, it is not
the case).The only way to get them build in lib32 is NOT to install ncurses.h
in lib32/usr/include.
Any comments or suggestions are welcome :)
Regards,
Rong-En Fan
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
installing fbsd from foreign system
Hi hackers! Probably I will be proud to have the chance to support one of Europe's major players in root server hosting for deploying FreeBSD as a target platform for their customers. I need to find a way to integrate the FreeBSD install process into their current deployment system. Currently their install process is running from a Linux install system which does the partitioning, make_fs etc. I found several options to integrate: 1) install a FAT partition, copy a bootable install system in it, boot (bsdboot) an install kernel from FAT partition and begin (unattended) installation (including fdisk, labeling, make_fs'ing). Any thoughts on that? I think this might be the best option. 2) fdisk'ing, labeling and make fs from the Linux system if there are any ported label + fs tools for Linux available - are they? 3) create an ext2 partition and copy the fbsd install system into it and boot from there to begin install process (same as 1 except running from ext2fs). Does a FreeBSD kernel support booting from ext2fs (using mdfs for root-fs)? If so, how? Any better thoughts? Any hints on how to proceed with one of the 3 options? PXE or anything else is not an option. I need to integrate the install process into an existing deployment system. I suspect to be the UFS problem to be the biggest one when it comes to deal with that from a running Linux system. Also as anything needs to run unattended, how do I set FreeBSD to try DHCP on any local interface the kernel can find? Greetings, Volker ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Local mirror
Hi the list,
I post this in questions@ without result :( Maybe here ? :)
For 3 box I want make a "little" FTP mirror :
I have activate anonymous account behind a NAT, in private adress so ..
No problem about secu
All the 2 hours I running a little script for synch this directory :
ROOT=/var/ftp/pub/FreeBSD
$ROOT/tools (for installation)
$ROOT/ports/distfiles/ (53Go All the last ports
sources ?)
$ROOT/ports/i386/packages-6.2-release/ (15Go All the last package for
6.2-RELEASE ?)
$ROOT/ports/i386/packages-6-stable/ (20Go All the last packages for
6-STABLE)
$ROOT/releases/i386/6.2-RELEASE (282Mo For make installation about
this server)
$ROOT/releases/i386/ISO-IMAGES/6.2 (1,4Go To have some my hands :)
My questions is for mirror-master :)
What's your politic about distfiles/ packages*/ directory ?
How many time about retention ?
We're ok if my 3 boxes are in /etc/make.conf :
MASTER_SITE_BACKUP?=
ftp://localserver/pub/FreeBSD/ports/distfiles/${DIST_SUBDIR}/
Re: atacontrol kernel crash (atausb?)
* M. Warner Losh <[EMAIL PROTECTED]> wrote: > In message: <[EMAIL PROTECTED]> > Hans Petter Selasky <[EMAIL PROTECTED]> writes: > : Instead of having all these quirks, isn't it possible that the SCSI layer > can > : auto-probe this? > > The short answer is no. There's no reliable way to tell if a device > supports a given scsi command, and some devices freak out (lock up) > when sent one. Well, in one of the scenario's there is. USB UFI devices never support synchronize. -- Ed Schouten <[EMAIL PROTECTED]> WWW: http://g-rave.nl/ pgpLVAqP4Lhxd.pgp Description: PGP signature
