iwi0 and spontaneous reboot on /etc/rc.d/netif restart
Hi, over the last 6 months or so, I have been so unfortunate to experience spontaneous reboots when I restart netif. Most of the time it leaves no trace in logs, but this time I was fortunate enough to be able to scrible down something while in console. I hope someone can shed some light on this - and I will be happy to provide a config files if necessary - it's basicly a standard setup with iwi0, wpa_supplicant connecting via wpa. It is a T42 with a Intel 2200BG. There is no issues in other OSes, so I figure this to be a driver specific problem. This is from handwritten notes, so there may be some inaccuracies. It is FreeBSD 8.0-release. wlan0: ieee80211_new_state_locked: pending SCAN - AUTH transition lost Fata trap 12: page fault while in kernel mode cpuid=0; apic id=00 fault virtual adress = 0xc4bd71b4 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0f78867 stack pointer = 0x28:0xc439ab7c frame pointer = 0x28:0xc439ac34 code seqment= base 0x0, limit 0xf, type 0x16 = DPL 0, pres 1, def 32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 (iwi0 taskq) trap number = 12 panic: page fault cpuid = 0 Uptime 13m9s Cannot dump. Device not defined or unavailable Automatic reboot in 15 seconds - press a key on the console to abort. Best Regards, Torgeir ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: can I do away with most things-java?
Hi Gary, On 23 February 2010 23:28, Gary Kline kl...@thought.org wrote: Some years ago I thought that future java tools would have BSD ports that did not demand that we fetch them ourselves? Now, among the few things left to rebuild/update is diablo-jdk16. The makefile sez to fetch tzupdater-1_3_25-2009u.zip. Can somebody please give me the exact URL that points to this file? More to the point, will a java port like openjdk free me from any Sun ports? Right now, a test pkg_delete of d-jdk16 gave me: t...@tao:/var/db/pkg# pkg_delete diablo-jdk-1.6.0.07.02_7/ pkg_delete: package 'diablo-jdk-1.6.0.07.02_7' is required by these other packages and may not be deinstalled: apache-ant-1.7.1 freemind-0.8.1_1,1 swt-3.5.1 Anybody? I simply use the package for 7 with compatibility. I have no idea what is going on with FreeBSD Foundation and why no new packages for 8-RELEASE have been built. OpenJDK will partially free you. I tried it too, but I recall correctly you cannot build it without bootstrapping it with the Diablo the first time (subsequently, it can be built with the old version of OpenJDK on each update - please correct me if this is wrong). However, I never succeeded in making any browser plugin for openjdk work. If you have a problem with 'tzupdater', download the latest one from Sun's site and alter the checksums in /usr/ports/java/diablo-jdk16/distinfo with the correct checksums and size. Hope this helps, Regards, //T ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
iwi and wlan-cloning
Hi all, After installing 8.0-release I followed all the howtos on cloning my iwi0 device to wlan0 to setup the wireless. The manual configuration: ifconfig wlan create wlandev iwi0 wpa_supplicant -c /etc/wpa_supplicant -i wlan0 dhclient wlan0 works well. However, trying to get this done automatically seems not to work: wlans_iwi0: not found ifconfig_wlan0: not found if I have rc.conf entries: wlans_iwi0 = wlan0 ifconfig_wlan0 = WPA DHCP wpa_supplicant_enable=YES Hope somebody has had more luck than I :) //T ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: iwi and wlan-cloning
On 31 January 2010 22:51, Brandon Gooch jamesbrandongo...@gmail.com wrote: On Sun, Jan 31, 2010 at 8:14 PM, Torgeir Hoffmann twhof...@gmail.com wrote: However, trying to get this done automatically seems not to work: wlans_iwi0: not found ifconfig_wlan0: not found if I have rc.conf entries: wlans_iwi0 = wlan0 ifconfig_wlan0 = WPA DHCP wpa_supplicant_enable=YES Do you actually have spaces between the names and values? Try wlans_iwi0=wlan0 ifconfig_wlan0=WPA DHCP I don't think this is required due to the 'WPA' in the ifconfig parameters: wpa_supplicant_enable=YES Thanks! I must admit I'm ashamed not to have seen this. Clearly I needed a fresh pair of eyes. Thanks for all replies! //T ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: X.org-update - screen garbled / settings for xorg.conf?
Hi, On Mon, Feb 2, 2009 at 5:36 PM, Ewald Jenisch a...@jenisch.at wrote: On Fri, Jan 30, 2009 at 11:30:02AM -0800, Luke Dean wrote: Me too. I started a thread a few days ago titled Restarting new Xorg freezes system. My symptoms are the same as yours. I'm not running hald at all. I'm not using full-blown gnome, just windowmaker. I'm using the radeon driver on an ATI HD 4350 I just tried switching to the vesa driver, and now I can stop and start X as much as I want with no problems whatsoever. I know that this was not a problem with the radeon driver prior to the Xorg update. Hi, Did a few tests more: 1) Section ServerLayout Option AllowEmptyInput false Section Device Driver radeon moused running hald running Result: X (gnome in my case) starts, mouse moves. Upon leaving X the console is to something different than 80x25 lines - at least I can't see about 2-3 lines on the bottom of the screen. However - as soon as a start X again I get graphical junk on the display, mouse keyboard frozen, no switching of consoles nor can I log in via the net (ssh) Just for the record, this used to happen in Linux (Fedora 9) but it's working since some time ago (sorry, I don't remember when this was fixed) radeon now works and doesn't freeze if you try to bring the X Server up again. I'm using Xorg 7.4 too Just wanted to say that I experienced similar problems quite some months ago, and posted under the title: Re: [FreeBSD 7] Radeon Mobility M10/9600 + xorg 7.3 + ati/radeon driver causes complete system hang/freeze. I never got it to work, and that was with xorg 7.3. Also, everything worked with vesa. I tried everything from disabling most things in rc.conf, most modules, dri in xorg.conf. I tried deleting the renaming the log for xorg, and then you could most of the times start xorg once, but not twice. The second time would result in a black screen. (of course removing the log and the following effect is most likely random). I had an idea that it might be that the drm-implementation wasn't able to load the microcode (?) for the r300 correctly sometimes, but this is guesswork at best. Is it possible that this is a bug partly related to xorg, but more related to the radeon driver and freebsd that slipped through in the last bug-hunting? However, I experience the same problems in my system (ATI RadeonHD 2400 with FreeBSD 7.1-RELEASE-p2) 2) Same as 1) above however this time with Driver radeonhd Result: Almost the same as 1) above - only difference: When I leave X the console comes back again to 80x25 lines. Hoever - like in 1) above - the second attempt to start X ends in a machine completely frozen :-( 3) Same as 1) - this time with Driver vesa Result: Everything works - i.e. back and forth between X and console. Sure enough working with Vesa is a workaround only given the huge difference in speed between the Vesa- and radeon drivers. 4) Option AutoAddDevices Off under 'Section ServerLayout' with Driver radeonhd Result: X works only once (as in Tests 12 above). Second attempt to start X gives a frozen box again. As you already mentioned o) no problem with VESA-Driver o) no problems with radeon-driver prior to the Upgrade to X 7.4 Hope this helps someone out there to track things down. //Torgeir ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7-stable packages on 7.0-release system?
Hi again! I assume that it is not advisable, but what can I expect to happen if I try to use packages for 7-stable on a 7.0-release system? No, it is not advisable. I tried: http://lists.freebsd.org/pipermail/freebsd-questions/2008-June/177553.html Thanks for pointing this out! Not having newer binary packages for the latest RELEASE is a shortcoming on FreeBSD, but you will find many references that there are simply not enough resources. Please excuse me for branching this thread off into another loosely related question. But then, if I am to use this laptop of mine for work (nothing critical): How stable is 7-stable? Can I upgrade to 7-stable via freebsd-update? Best Regards, //Torgeir ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
7-stable packages on 7.0-release system?
Hi all, I assume that it is not advisable, but what can I expect to happen if I try to use packages for 7-stable on a 7.0-release system? The reason is simple: I have a low-end laptop, so I want to avoid building as much as possible. However, the packages from release are rarely, if ever, updated and therefore very quickly becomes out of date, or they don't exist (e.g. openoffice). I often run into trouble when I need something that depends upon something that often affects many ports is updated, say gettext. Are packages for 7-stable mostly binary compatible with 7.0-release? Or should I just upgrade to 7-stable? Can 7-stable be trusted to run smoothly in most cases? I saw in one thread on the freebsd-stable list that 7-stable was more like current, only a bit cleaner. What do other 7-release users do in cases such as these? Best Regards, Torgeir ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Installing jdk on 7-Release: Has known vulnerabilities from 2005?
Hi, when I try to install linux-sun-jdk16 from ports I get: === linux-sun-jdk-1.6.0.07 has known vulnerabilities: = jdk -- jar directory traversal vulnerability. Reference: http://www.FreeBSD.org/ports/portaudit/18e5428f-ae7c-11d9-837d-000e0c2e438a.html = Please update your ports tree and try again. *** Error code 1 This refers to a vulnerability from 2005 (!). I get the same thing with the 1.5 port. I desperately want to avoid building the native version due to the fact that I have a not that sporty laptop, and the packages from the freebsd foundation is not available yet. I have the latest portsnap port snapshot. Hope somebody can help me. Is there any other way I can get the jdk without building it? Hope for quick reply, Torgeir ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing jdk on 7-Release: Has known vulnerabilities from 2005?
Hi again! when I try to install linux-sun-jdk16 from ports I get: === linux-sun-jdk-1.6.0.07 has known vulnerabilities: = jdk -- jar directory traversal vulnerability. Reference: http://www.FreeBSD.org/ports/portaudit/18e5428f-ae7c-11d9-837d-000e0c2e438a.html = Please update your ports tree and try again. *** Error code 1 This refers to a vulnerability from 2005 (!). I get the same thing with the 1.5 port. I desperately want to avoid building the native version due to the fact that I have a not that sporty laptop, and the packages from the freebsd foundation is not available yet. I have the latest portsnap port snapshot. Update your portaudit database. I did that. portaudit -Fda Still, same thing. Thought this was very strange as well. Anything else that I should have done? (It's probably right in front of me!) Many thanks, Torgeir ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[FreeBSD 7] Radeon Mobility M10/9600 + xorg 7.3 + ati/radeon driver causes complete system hang/freeze
On beforehand, I appologize for sending a rather incomplete mail regarding this last week, I hope with this new information that I can find a clue on how to debug or solve this problem. I have the following problems with my xorg 7.3 installation, even after I have pkg_delete -a, and reinstalled all with packages. The system was updated with freebsd-update from 6.3-release to 7.0-release. My problem has the following characteristics: * Whenever I start xorg with startx and the radeon/ati-driver, the system will become unresponsive, and cold reboot is the only way to escape the lock. * xorg will start fine using the 'vesa' driver. * On a system-freeze, there is no logging - at all. Nothing in dmesg/messages or in Xorg.0.log. * I had no problems with xorg 7.2/7.3 on my 6.3-release system. * dmesg report: drm0 - Is it normal that it reports 256 MB, when I have a 64MB graphics card? For you convenience, the config-/log-files can be found at: * dmesg: http://pastebin.com/m47427876 * Xorg.0.log: http://pastebin.com/m13673d99 * xorg.conf: http://pastebin.com/m52dab34b any help will be greatly appreciated! Best Regards, //Torgeir ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[7.0] xorg 7.3 and ati/radeon 6.8.0 woes
Hi, after upgrading my IBM T42 with ati radeon M10/9700) to 7-release via freebsd-update (which went very well), and running portsnap+portupgrade -afP, I tried starting xorg. This results in a complete freeze of the machine, no Ctrl-Alt-Backspace, Ctrl-Alt-Delete, changing terminals or anything else works. I can start xorg as root with the 'vesa' driver. However, any config in xorg.conf with the 'ati'/'radeon' driver causes a freeze. Mostly, it will freeze with either a black screen (backlight on), or simply freeze after printing (==) Using config file: /etc/X11/xorg.conf. I have tried disabling glx, dri, setting NoAccel and AGPMode to 1. Nothing seems to work. The funny thing is that neither /var/log/messages or /var/log/Xorg.0.log has any mention at all of any problems, let alone that I even started Xorg. Also, using xorg 7.2/7.3 in 6.2-release and 6.3-release did not seem to cause any problems. I am at loss to what would be the cause. Will gladly post xorg.conf (generated by Xorg -configure, changed keyboard), and any logs necessary. Hope for quick reply, Best Regards, //Torgeir ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade 5.4 - 6.0
Hi there! Can someone tell me the proper steps for upgrading from 5.4 - 6.0? I have also stuff installed from the ports collection, eg. cyrus-imapd, clamav, etc. First follow the handbook for rebuilding world and kernel. The first thing you should do is cvsup your source. As far as I've understood, it's recommended to upgrade to 6.0-release first, and then to 6.0-stable if you want that. When you've upgraded the base and kernel, you can sync your portstree with portsnap or cvsup, and use either portsupgrade or portmanager to upgrade all extra packages that you have installed. If you don't have a quick machine, you might want to use the package-switch to make it check for precompiled packages before building from source. Relevant handbook refs. I think would be: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/synching.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/portsnap.html //Torgeir ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot boot with newly compiled kernel, or kernel.old after upgrading to RELENG_6
--On Monday, December 05, 2005 01:06:09 AM +0100 Torgeir Hoffmann [EMAIL PROTECTED] wrote: AFAIK If the nvidia-driver is from the ports you will need to disable it so you can later rebuild it in 6.0. You will probably find all the details you need with a search. Ok, thanks. I'll try it as soon as I get back home. Of some reason, I assumed that the nvidia module was recompiled in the process :-p Well, thanks again. //Torgeir Hoffmann ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Cannot boot with newly compiled kernel, or kernel.old after upgrading to RELENG_6
Hi, I have been so unfortunate to be left with a completely unusable system after updating to RELENG_6 from RELENG_5. I am quite sure that I followed the step from the handbook correctly, but as mentioned the system is unbootable. The error when trying to boot the new kernel makes the system reboots after 15 seconds, so I haven't had the opportunity to write that one down. However, the error message from when trying: unload, boot /boot/kernel.old/kernel I was able to copy down in full (see bottom). If I try to unload linux.ko by ' set linux_load=NO ', it goes a bit further. I can only see acpi.ko: could not finalize loading flash by, and several PNP0303 can't assign... error messages before it mounts, it finishes to load ipfw2 and then suddenly it says 'Warning: Device driver ' then nothing more on the line, then a similar error message to the one at bottom follows. (page fault). Reboots after 15 seconds. I really hope someone knows what this is all about - I have no idea why this is happening. Further I cannot understand why kernel.old doesn't work - after all I've used that kernel for 6 months without any issues. Mind that this is the GENERIC kernel, and it was compiled with unmodified conf. Hope for quick reply, Best regards, Torgeir Hoffmann -- Error message -- link_elf: symbol VOP_READDIR_APV undefined KLD file linux.ko - could not finalize loading. kernel trap 12 with interups disabled Fatal trap 12: page fault while in kernel mode. fault virtual address = 0x8 fault code = supervisor read, page not present instruction pointer = 0x8:0xc060bdff stack pointer = 0x10:0xc1020d24 frame pointer = 0x10:0xc1020d24 code segment = base 0x0, limit 0xf, type x1b = DPL 0, pres 1, def32 1, gran 1 processlr elfags = resume, IOPL = 0 current process = 0 () trap number = 12 panic: page fault uptime: 1s ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot boot with newly compiled kernel, or kernel.old after upgrading to RELENG_6
Hi, thanks a lot for quick reply. Did you copy the 6.0 GENERIC config file into the one your buildkernel make uses? No, actually I didn't. From what I could see on http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html, I didn't think it was necessary. The error when trying to boot the new kernel makes the system reboots after 15 seconds, so I haven't had the opportunity to write that one down. However, the error message from when trying: unload, boot /boot/kernel.old/kernel I was able to copy down in full (see bottom). You should only load the 5-stable kernel and the boot -s. You have a mixed kernel and userland. You can't expect kernel.old and your 6-stable userland to work. If I understand you correctly, that would mean that even if I haven't yet done installworld, my userland is still 6.0? I'm terribly sorry if I wasn't clear on that point. Thanks for the boot command - it worked very well. I thought I'd try to cvsup the sourcetree to RELENG_6_0 instead now, and then try to recompile. Is that a good idea? I was thinking, since installworld hasn't been done yet? Many thanks, Torgeir Hoffmann ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot boot with newly compiled kernel, or kernel.old after upgrading to RELENG_6
On Sunday 04 December 2005 12:56 pm, Torgeir Hoffmann wrote: Hi again, tried to rebuild the base once more, after syncing up with RELENG_6_0, and as far as I can see it worked like a charm. However, I still can't boot the system after building a new kernel. Even when booting the system with boot -s, the new kernel throws a page fault, and reboots after 15 seconds. I tried to follow the other lead concerning ACPI, although I haven't had time to search thoroughly through lists. I tried using unset acpi_load before boot -s, but it still produces the same result. I'm starting suspect that it might have something to do with the nvidia, as it is the last thing I see before the error occurs. I see: output nvidia0 //some stuff I didn't catch in time - I assume hardware details Warning: Device driver /output (page fault error similar to the one posted earlier) Also, I have no idea why it produces a single double-dash ( ). Did you copy the 6.0 GENERIC config file into the one your buildkernel make uses? Probably GENERIC. I use the equivalent of make buildkernel KERNCONF=RUBY make installkernel KERNCONF=RUBY but I have then built into scripts. yes, I've had most things I needed in GENERIC, and loaded modules for the sound - that's it. If you have a KERNCONF entry in /etc/make.conf, it uses that. If it was your 5-stable config file, it used it. Everytime they do an upgrade, you need to check it. Options come and go. I didn't have a make.conf entry with KERNCONF - so I can only assume that it uses GENERIC, and further I'd assume that I'd use the one that came with the source checkout. Afterall, the world and kernel compiled fine, the kernel does not, however, seem to be happy to boot. If you haven't done an installworld, you shouldn't do anything but boot -s. You have to finish the install and then you can use the full boot. Unfortunately, the bottleneck still persists - and I have a gut feeling that I won't get anywhere booting the RELENG_5 kernel and installing the base. I guess that'd would only make it more of a mess, than what'd I've already made it... I have had kernels that would immediately panic and the boot to single user mode is to catch them. You have a new user called _dhcp that needs to be added to group and master.passwd. Then, you have what seems like 100's of files that need to be updated using mergemaster. Thanks for the tip - I ran mergemaster -p before buildworld, and that _dhcp user was added. Thanks for all help so far. Best Regards, Torgeir Hoffmann ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
