Re: CFT: ath hal src switchover
On Fri, Jan 9, 2009 at 5:32 AM, Sean C. Farley wrote: > On Thu, 8 Jan 2009, Sam Leffler wrote: > >> I've brought the hal source code back to RELENG_7 but not connected it to >> the build and/or driver. I want folks to test this before I commit those >> changes. To do this you must have an up to date RELENG_7 code base and then >> apply this patch: >> >> http://people.freebsd.org/~sam/ath_hal-releng7.patch > > *snip* > >> Please report any issues to this mailing list. > > No problems for my Netgear WPN511. It works well at home. > > Now, if I just could figure out why the recent Aruba update at work is > preventing me from authenticating with it, I would be happy. This is not > related to the MFC of the code. iPhones and MacOSX 10.4 (but not 10.5) are > also having problems. Windows works. > > Sean > -- > s...@freebsd.org > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > Hi, today I tried to get a (samsung nc10 ath) nic working. The patch failed to edit this three files: sys/modules/ath_rate_onoe/Makefile sys/modules/ath_rate_sample/Makefile sys/modules/ath_rate_amrr/Makefile I emptied them manually and ran a buildworld/kernel/etc on a clean 7.1 stable but i get a error message while booting: ath0: unable to attach hardware; HAL status 13 After that I csuped the latest stable srcs, applied hal-20081015-sanitized.tgz and run the complete buildprocess again. The same error Message occurs. Is there any trick to get the samsungs ath card running? regards, Vincent Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-STABLE #0: Tue Jan 13 21:21:53 CET 2009 root@:/usr/obj/usr/src/sys/BOOKLI Preloaded elf kernel "/boot/kernel/kernel" at 0xc0a99000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0a99250. Calibrating clock(s) ... i8254 clock: 1193244 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1595994372 Hz CPU: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (1595.99-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x106c2 Stepping = 2 Features=0xbfe9fbff Features2=0x40c39d> AMD Features2=0x1 Logical CPUs per core: 2 1st-level instruction cache: 32 KB, 8-way set associative, 64 byte line size L2 cache: 512 kbytes, 16-way associative, 64 bytes/line real memory = 1064108032 (1014 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00c25000 - 0x3e4b0fff, 1032372224 bytes (252044 pages) avail memory = 1031852032 (984 MB) Table 'FACP' at 0x3f6e1bd2 Table 'APIC' at 0x3f6e1cc6 MADT: Found table at 0x3f6e1cc6 MP Configuration Table version 1.4 found at 0xc009fc71 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 0: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 1 ACPI ID 1: enabled SMP: Added CPU 1 (AP) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 bios32: Found BIOS32 Service Directory header at 0xc00f7150 bios32: Entry = 0xfd5f0 (c00fd5f0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd5f0+0x275 pnpbios: Found PnP BIOS data at 0xc00f71f0 pnpbios: Entry = f:b8d8 Rev = 1.0 Other BIOS signatures found: APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 1 ULE: setup cpu group 0 ULE: setup cpu 0 ULE: adding cpu 0 to group 0: cpus 1 mask 0x1 ULE: setup cpu 1 ULE: adding cpu 1 to group 0: cpus 2 mask 0x3 ACPI: RSDP @ 0x0xf71a0/0x0024 (v 2 PTLTD ) ACPI: XSDT @ 0x0x3f6db94a/0x0084 (v 1 SECCSD LH43STAR 0x0604 LTP 0x) ACPI: FACP @ 0x0x3f6e1bd2/0x00F4 (v 3 INTEL CALISTGA 0x0604 ALAN 0x0001) ACPI: DSDT @ 0x0x3f6dd5f2/0x456C (v 1 INTEL CALISTGA 0x0604 INTL 0x20050624) ACPI: FACS @ 0x0x3f6e2fc0/0x0040 ACPI: APIC @ 0x0x3f6e1cc6/0x0068 (v 1 INTEL CALISTGA 0x0604 LOHR 0x005A) ACPI: HPET @ 0x0x3f6e1d2e/0x0038 (v 1 INTEL CALISTGA 0x0604 LOHR 0x005A) ACPI: MCFG @ 0x0x3f6e1d66/0x003C (v 1 INTEL CALISTGA 0x0604 LOHR 0x005A) ACPI: TCPA @ 0x0x3f6e1da2/0x0032 (v 1 PTLTD CALISTGA 0x0604 PTL 0x0001) ACPI: TMOR @ 0x0x3f6e1dd4/0x0026 (v 1 PTLTD 0x0604 PTL 0x0003) ACPI: APIC @ 0x0x3f6e1dfa/0x0068 (v 1 PTLTD APIC 0x0604 LTP 0x) ACPI: BOOT @ 0x0x3f6e1e62/0x0028 (v 1 PTLTD $SBFTBL$ 0x0604 LTP 0x0001) ACPI: SLIC @ 0x0x3f6e1e8a/0x0176 (v 1 SECCSD LH43STAR 0x0604 LTP 0x) ACPI: SSDT @ 0x0x3f6dcfa3/0x064F (v 1 SataRe SataPri 0x1000 INTL 0x20050624) ACPI: SSDT @ 0x0x3f6dc
Re: more marvell marvels
On Fri, Jan 9, 2009 at 1:19 PM, Pyun YongHyeon wrote: > On Fri, Jan 09, 2009 at 01:48:24PM +0200, Danny Braniss wrote: > > hi, the mb is asus P5K-VM, the onboard nic is, acccording to pciconf: > > > > ms...@pci0:1:0:0: class=0x02 card=0x81f81043 chip=0x436411ab > > rev=0x12 hdr=0x00 > > vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' > > device = '88E8056 Yukon PCI-E Gigabit Ethernet Controller' > > class = network > > subclass = ethernet > > cap 01[48] = powerspec 3 supports D0 D1 D2 D3 current D0 > > cap 03[50] = VPD > > cap 05[5c] = MSI supports 1 message, 64 bit > > cap 10[e0] = PCI-Express 1 legacy endpoint > > > > nothing new here, problems have been reported before, but: > > > > my very first attempt - after a very long time - of booting 7.1-stable, > > produced > > a panic because msk could not find its physio, by the time i had the serial > > console > > attached and working, that problem disappeared :-( > > now, after reboot, it sometimes hangs - because the net is not working, and > > only if > > I unplug the ethernet, (no signs of the driver seeing this), and replug > things > > begin > > to work. btw, i had to set > > hw.msk.legacy_intr="1" > > to get things working. > > > > any patches for 7.1-stable to test? > > > > If memory serve me right you have Yukon EC Ultra with 88E1149 PHY, > right? CURRENT has some stability fixes but the source wouldn't be > compiled on stable/7 yet due to KPI differences. I have plan to add > some features in next week which make it possible to use HEAD > version on stable/7. > > I'm not sure the patch for 88E8040 could be applied to stable/7 > but the patch has some fixes for link state handling. Would you > give it try? > http://people.freebsd.org/~yongari/msk/msk.88E8040.patch14 > Note, the 88E8040 patch is not complete yet and may cause other > problems too. > > -- > Regards, > Pyun YongHyeon > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > Hi Pyun, are if_msk.c and if_mskreg.h from http://people.freebsd.org/~yongari/msk/ the patched version? With this files I get an error Message regarding MEXTADD(m, buf, MSK_JLEN, msk_jfree, buf, (struct msk_if_softc *)sc_if, 0, EXT_NET_DRV); Is there a "buf," too much? I deleted the second "buf," and I was able to compile the Kernel. But I can't assign an IP with dhcp because msk0 always goes up and down. This is my nic: pci3: domain=0, physical bus=3 found-> vendor=0x11ab, dev=0x4354, revid=0x13 domain=0, bus=3, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 powerspec 3 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 64, base 0xf020, size 14, enabled no...@pci0:3:0:0: class=0x02 card=0xca00144d chip=0x435411ab rev=0x13 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' class = network subclass = ethernet cap 01[48] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 05[5c] = MSI supports 1 message, 64 bit cap 10[c0] = PCI-Express 2 legacy endpoint Regards, ~ vb ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Upgrading to 7.0 - stupid requirements
On Tue, Mar 18, 2008 at 8:21 PM, Marko Lerota <[EMAIL PROTECTED]> wrote: > Kris Kennaway <[EMAIL PROTECTED]> writes: > > >> Then the servers. Why should I reinstall all my databases and such? > >> I always > >> liked that FreeBSD base (OS) is separated from packages. And no > >> matter what I do with the packages, my OS will always work. I don't > >> want dependency > >> hell like in Linux. Now you are telling me that my database might not work > >> after upgrade to a new version. Is that it? > > > > First, try to relax. > > Sorry, but I'm pissed off now, not relax any more. > > > > portupgrade -faP requests to reinstall everything from precompiled > > packages. It will only fall back to compiling them locally if the > > package is unavailable (e.g. for legal reasons). > > It passed two days from portupgrade -faP, and it didn't finished yet. > To be worse, I have to do it again because the PC had to be rebooted. > So in the next 2-3 days I can sit with my PC and wait with him to > finish the upgrade. It will be three days because of [EMAIL > PROTECTED]@[EMAIL PROTECTED] > And I have to pray the god that I don't have the power loss. > Now apache and acroread doesn't work any more and I'm afraid that > I'll find some other stuff that don't work too. > > So can anyone tell me this is not stupid??? Reinstalling all > applications because of upgrade? This can be called new > installation. Not upgrade. > > Now I'm thinking that It would be much easier that I backup my files, > databases and other stuff and do fresh installation. But why > So I can do the same thing when 8_0 comes out? > > This is the worst thing that I found about FreeBSD for now. > This have to be changed or fixed somehow, because the upgrade > is not possible if you have lots of ports installed, and > certainly can't be called upgrade! > > > -- > One cannot sell the earth upon which the people walk > Tacunka Witco > ___ > > > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > Hi Marko, you can always use the -w flag of portupgrade if interrupted it while upgrading the installed ports: w --noclean Do not "make clean" before each build. See the -c option above. If you start the portupgrade again without -w then it will use -c by default which means all your "inbuildproccess" ports are gone. I don't know if -w is the clean way to resume from an interrupted portupgrade, but i never had problems with it. Well, ok you mustn't install any other port before you resume your portupgrade that could confuse your system :) The more clean and easy way to do a upgrade of your ports after switching to another major release (I do it this way everytime): #pkg_delete -fa <--- is much faster than pkg_deinstall Then i get my Ports with the -P flag of portinstall. A few days ago I did it this way after I jumped from 7 Release to 7 Stable. It took me about three hours to get my x11-wm/xfce4, x11/xorg (yes the complete xorg) and some other tools I need to work because the biggest part of this ports were available as prebuild pkgs. Try it this way, Vincent ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
