Re: bash2 linked dynamically
On Mon, 1 Dec 2003, Leo Bicknell wrote: >In a message written on Sun, Nov 30, 2003 at 09:48:45PM -0800, David O'Brien wrote: >> Lucky for me (who wants a static Bash), I don't have to make the >> decission -- ports are frozen and have been for a while. > >This line of thinking seems a bit silly to me. We have a long >discussion documenting the dynamic root concept, and how it was >deemed important that /bin/sh be dynamic to support NSS and other >reasons. > >Now someone wants the same thing in bash, and commit-freeze is going >to stop it from happening? > >Sounds like the core team, or re, or someone needs to decide which >is more important. If NSS is so important redoing the whole root >is important, then I sure think any and all shells installed by >ports should support the same features. If, on the other hand it's >not important for Bash then why in the heck are we doing it for the >root? > >I'm done arguing for either side of this issue, but I will argue for >consistency until I'm blue in the face. > >-- > Leo Bicknell - [EMAIL PROTECTED] - CCIE 3440 >PGP keys at http://www.ufp.org/~bicknell/ >Read TMBG List - [EMAIL PROTECTED], www.tmbg.org > Don't bother about it. There was a discussion, and some people thinks that if something isn't broken (static linking), thne no one should fix it (dynamic linking). Perhaps they thinks that Billy will test dynamic linking in CURRENT and the performance will be OK... Maybe he will... But OS will became Microsoft (R) FreeBSD (TM) then... IMHO... If we want to reduce dynamic linking penalty - we MUST to do it... Go forward, testing and fixing things, that gives us performance loss... But static is a cure for these penalties... Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports startup scripts in /etc/rc.d (Re: 5.2-BETA and related ports issues)
On Sun, 30 Nov 2003, Richard Coleman wrote: >Andreas Klemm wrote: > >>>I guess I don't see the problem. What is wrong with ports adding >>>startup scripts to /etc/rc.d? For certain ports, that is the only way >>>to get the startup dependencies right (like making sure openldap or >>>postgresql starts before your mail system). This will become more >>>important as more of the base system moves to ports/packages. >>> >>>Just refine the note in UPDATING to specifically state which startup >>>scripts to remove, rather than "rm -rf /etc/rc.d/*". >> >> >> As I wrote im my previous mail we could import wrapper scripts >> for such basic services, since there are only few services >> that are so generic, that they have to be available so early >> in boot order. >> >> I strongly would dislike creating ports to install stuff under >> /etc/. >> >> This would start to violate things for what I liked FreeBSD for >> all these many years and I hope/think other have the same feeling >> concerning this. >> >> Andreas /// >> > >But that kinda defeats the purpose of RCNG. One of the best features of >RCNG is that it makes it easier to add/delete applications from the >system. Not using it for this purpose reduces its utility. > >Let's not let the typical BSD traditionalism get in the way of using >RCNG for what it's designed. Don't get me wrong. I'm not advocating >Linux-style integration of packages/ports. But this seems fairly harmless. > >Richard Coleman >[EMAIL PROTECTED] > > >___ >[EMAIL PROTECTED] mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "[EMAIL PROTECTED]" > Perhaps we just need to place "wrapper" startup script, that will try to start "real" startup script in /usr/local/etc/rc.d if it exist? Most of ports are installed into /usr/local, so, lets don't use hierarchy above that. Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 40% slowdown with dynamic /bin/sh
On Mon, 24 Nov 2003, Andrew Gallatin wrote: > >Daniel O'Connor writes: > > > > It is _trivial_ to buildworld with a static root. > >Then its equally trivial to build with a dynamic root. Please do so, >and don't wreck the performance of the OS I've used since 1994. Then just use OS from 1994 and don't bother about NEW features that may appear in dumb, slow, dynamically linked OS. Just put your head in the sand and say "I'm pretty happy with old statically linked OS and I never need new features in it"... World is going forward, and the payment of new features is awesome performance of OLD, not so good profiled (due statical linking) dynamic linking functions. "if it isn't broken - don't fix it". But if you don't use dynamic linking - it's DEFINITELY NOT broken. And will never be fixed. Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: /bin and /sbin are now dynamically linked
>[ From: set to /dev/null as too many can't follow the Reply-To: ]
>
>On Mon, Nov 24, 2003 at 11:00:24AM -0500, Rahul Siddharthan wrote:
>> > NO. /rescue was allowed in the system to handle the case of a trashed
>> > file in /lib[exec]. To allow a sysadmin to recover a system from the
>> > same type of mishaps they could before we went to a dynamic /.
>>
>> Ie, let's do things the same way we did in 1994? Other things have
>> changed since then, hard drives and typical root partitions are much
>> bigger, and Tim estimated the total bloat from this as 64k. Maybe
>> earlier, pre-/rescue, you couldn't recover from damaged files in the
>> root partition without a CD/floppy/NFS, it doesn't mean you should not
>> have that capability in /rescue.
>
>Lets have /rescue/{[s]bin,usr/[s]bin}. Install static copies of every
>thing in /[s]bin and /usr/[s]bin today. That will let you recover in
>even more ways.
>
>Where does it end if we don't go full-out and install a 2nd copy of every
>binary?
>
>
>> For a *lot* of people today (like home users), an up-to-date FreeBSD
>> CD or floppy or a second machine to create the disk on may not be
>> handy (and forget about NFS), but a network connection may still be
>> available.
>
>That network connection would most likely be a M$-Win box in that case,
>which doesn't have an FTP server. Samba, not an FTP client should be in
>/rescue then.
There are a lot of FTP servers for M$ Windows... At least
IIS/PWS... :-) IMHO, Microsoft gives it to all, neglecting whether they
need it or not. :-) So, FTP server is not concern. /rescue/fetch MAY help
to recover RUINED FreeBSD from ashes... As /rescue/mount_cd9660, or
mount_msdosfs... In other words we can drom mount_msdosfs from /rescue
just because almost everybody can burn CD... We will save a few KBytes of
space (that isn't really needed on modern disks), but we will loose
functionality... For me, having /rescue/fetch is a good thing, just
because it can REALLY help me to recover fallen system.
Sincerely, Maxim M. Kazachek
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: /bin and /sbin are now dynamically linked
On Sun, 23 Nov 2003, Bruce M Simpson wrote: >On Sun, Nov 23, 2003 at 02:42:58AM +0100, Brad Knowles wrote: >> At 5:22 PM -0800 2003/11/22, David O'Brien wrote: >> >> > Please, NO. There wasn't an FTP client available for this type of >> > recovery pre-/rescue, there shouldn't be one now. >> >> Why? Why cut your nose off to spite your face? Even though this >> capability may not have existed before, why shouldn't we have it now? > >I think David has valid concerns here about feeping creaturism. fetch >has a whole load of library dependencies which go with it, making it >unsuitable for inclusion in /rescue in the base system. > >If you want access to fetch early on in this way, you could make a local >branch and maintain the change for your own site, or you could boot from >a FreeBSD live CD, or use sysinstall from the installation CD to install >a package. I don't see fetch as a requirement for diskless clients. > Not diskless clients, but ruined FreeBSD installation. IMHO /rescue is created for it. We shouldn't put fetch into /bin, but placing fetch into crunched executable may be helpful in case of system restore. Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unfortunate dynamic linking for everything
On Sun, 23 Nov 2003, David Wolfskill wrote: >>Date: Mon, 24 Nov 2003 09:34:08 +0600 (NOVT) >>From: "Maxim M. Kazachek" <[EMAIL PROTECTED]> > >> So, imagine, i'm accidentally deleted /bin with your most wanted >>static sh... And, of course, due to static nature of /bin/sh it was >>removed from /rescue? Nothing will protect you from shooting in the leg, >>neither static linking, nor assumption that /lib is OK. > >So go ahead and make /bin/sh also have a (hard) link to /rescue/sh. >Then the referenced action merely decrements the link count, and the >executable itself doesn't go away. > >Sure, you could be more imaginative with foot-shooting, but the stated >problem is really easy to avoid. > >Peace, >david (reluctant to contribute to this thread) >-- >David H. Wolfskill [EMAIL PROTECTED] >If you want true virus-protection for your PC, install a non-Microsoft OS >on it. Plausible candidates include FreeBSD, Linux, NetBSD, OpenBSD, and >Solaris (in alphabetical order). I'm a real masochist, and removed /rescue/sh /sbin/sh whatsoever. And after that will begin complain, that FreeBSD is ugly, non bullet-proof operating system... :-) But, in fact, as I can remember, all /rescue stuff is one hadlinked executable. I don't think that hardlinking /bin/sh into /rescue would be nice idea... IMHO it's not clear. Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unfortunate dynamic linking for everything
On Mon, 24 Nov 2003, Duncan Barclay wrote: > >From: "David O'Brien" <[EMAIL PROTECTED]> > >> I'll seriously argue against the 2nd point above. I don't know of a >> SINGLE person that uses /bin/sh as their interactive shell when >> multi-user. Not ONE. Every Bourne shell'ish user I've ever met uses >> Bash, AT&T ksh, pdksh, zsh. > >I don't know anyone that farms lama's, so there cannot be any lama farmers. > >computer$ grep dmlb /etc/passwd >dmlb:*:1166:1166:Duncan Barclay:/home/dmlb:/bin/sh > >Duncan So, imagine, i'm accidentally deleted /bin with your most wanted static sh... And, of course, due to static nature of /bin/sh it was removed from /rescue? Nothing will protect you from shooting in the leg, neither static linking, nor assumption that /lib is OK. MOST people uses /bin/sh only for rc scripts (to be correct, their system uses it). David O'Brien just tried to told, that NOBODY he knows will be REALLY impacted by performance loss, caused due dynamic /bin/sh linking. You will... So, because Duncan Barclay is impacted by performance loss due dynamic /bin/sh linking, ENTIRE FreeBSD community will have troubles (at least with NSS) due to static linking... Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Nforce 2 Audio driver
>hi andrew, > My name is rubin. i read your reply at nvidia.ko freezes system >in -current. you seem to know alot about computer and i was wondering if you >could help me. I have a abit nf7 mobo with the nforce2 MCP southbridge. >The nf7 has an APU(Audio processing unit); this is evident when >running the nvidia drivers and hence producing impressive 2.1 sounds ( APU >provides features like 256 voice, 64 3d voice, DX8 submixer and bla bla bla >). Both the nf7 and nf7-S (MCP-T southbridge) have the realtek DAC( Digital >Anolog Converter). This changes the digital signals from the APU to anolog >signals used by the speakers. > Unfortunately they have disabled the nForce MCP Audio >Processing Unit (Dolby Digital) driver on the mobo and this is only enabled >on the nf7-s mobos running MCP-T. As a result i only get 2 channel sound. >now if i'd know about this i wouldn't have bought it, but even the damn abit >nf7 box had the word Soundstorm on it. I just want 6 channel audio that >works all the time with my games and music(realtek drivers don't have EAX >and doesn't give 6 channel with winamp). I'm a student an on a very tight >budget. Could you pls teach me to hack the Nvidia unified audio drivers so i >can get it to install the MCP-T Audio Processing Unit (Dolby Digital) driver >and hence get 6 channel audio. If that won't work could you tell me what i >need to do to get 6 channel audio without resorting to realtek drivers. >Please i'm really disappointed that abit and nvidia aren't helping and i >invested alot of money on decent speakers. Please help. You do not have SoundStorm technology on your motherboard. NF7-S uses MCP-T, while NF7 and NF7-M (with integrated video) uses MCP, which, in oppose to MCP-T have no interface to second network card (based on 3COM's chip), have no IEEE-1394A (aka Firewire) and have no SoundStorm Technology. Realtek's ALC650, that is used on that motherboards is capable to switch to 6 channel mode in Windows driver... Have no any idea how to do that in FreeBSD. Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i386_set_ldt warnings
On Wed, 22 Oct 2003, C. Kukulies wrote: >Some (kde) applications now have a warning appear in xconsole: > >Warning: pid 595 used static ldt allocation. >See the i386_set_ldt man page for more info >Warning: pid 596 used static ldt allocation. >See the i386_set_ldt man page for more info > >Should I worry about that? Rebuild KDE? > >-- >Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de I have similar message with licq-qt-gui, so I suspect qt-3.2.1 library. I use GNOME 2.4, so licq-qt-gui is just one thing that uses qt. qt is used by KDE mostly Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problem updating from 4.7 Stable do 5.0 Current
What your server do when it panics? It tries to detect disks? Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Mon, 31 Mar 2003, Ventsislav Velkov wrote: >I could not boot in single user mode with the 5.0 kernel because it brokes. >Do you mean I should boot in single user with the 4.7 kernel in there installworld >and to mergemaster ? > >regards, >Veno > - Original Message - > From: CARTER Anthony > To: [EMAIL PROTECTED] > Sent: Monday, March 31, 2003 3:15 PM > Subject: Re: problem updating from 4.7 Stable do 5.0 Current > > > Have you installed the world? I don't know if just rebuilding it is > sufficient > > To install the world you have to go to single user mode and run mergemaster to > update any changes in configuration files (take a backup of your current > files as it overwrites them). > > Anthony > > On Monday 31 March 2003 13:15, Ventsislav Velkov wrote: > > Hello all, > > > > I have a problem updating one of our servers from 4.7Stable to 5.0Current. > > It is a Compaq Proliant 7000 Server with 4 Xeons @500Mhz with 2MB L2 cache > > each. I has a 4200 Compaq Smart Raid Controler with attached 3 U1 Storages. > > I update the src rebuild the world from updated src to 5.0Current, build a > > GENERIC kernel and installed it. But after I boot it brokes up during the > > booting process with the following error: > > > > //strip > > > > Fatal trap 12: page fault while in kernel mode cpuid=0; lapic.id= 0100 > > fault virtual address = 0x54 > > fault code = supervisor read, page not present > > > > > > > > process eflags = interrupt enabled, resume, IOPL=0 > > current process = 4(g_down) > > kernel: type12trap, code=0 > > Stopped at ida_construct_qcb+0xe3: movzbl 0x54(%eax),%eax > > > > //strip > > > > It may have some punctual mistakes because it is not a copy/paste. > > > > Will appreciate any advices where could be the problem. > > > > Best regards, > > > > Veno > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" >___ >[EMAIL PROTECTED] mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HELP GDM XFree86
It depends on GNOME version... GNOME-1.4.something installs gdm that is started by init... GNOME-2.2.0 installs gdm that is supposed to start via /usr/X11R6/etc/rc.d/gdm.sh... Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Thu, 20 Mar 2003 [EMAIL PROTECTED] wrote: >On 20-Mar-2003 CARTER Anthony wrote: >> One more thing...I am running gdm as such from my /etc/ttys file: >> >> ttyv8 "/usr/X11R6/bin/gdm -nodaemon" xterm on secure > >I think the GDM documentation says, that you should start it via the supplied >rc.d autostart script in order to avoid certain problems. HTH > >Regards, >Julian Stecklina > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4.3.0,1 +wrapper-1.0_2
You can forcibly delete wrapper package, and the do pkgdb -F and delete dependency on it... Only XFree metaport is depends on it. Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Thu, 20 Mar 2003, CARTER Anthony wrote: >I realise what wrapper is for, but if I type pkg_delete wrappe-1.0_2 at >the command line, I get: > >pkg_delete: package 'wrapper-1.0_2' is required by these other packages >and may not be deinstalled: >XFree86-4.3.0,1 > >I never installed wrapper, but when I did a portupgrade to the latest >XFree, I guess it installed wrapper as a dependency... > >I will forcably delete wrapper to see if that fixes the problem >(although I will try your solution first...I don't like deleting >dependencies)... > >Thanks, > >Anthony Carter > >On Thu, 2003-03-20 at 00:17, walt wrote: >> CARTER Anthony wrote: >> > Xfree requires wrapper but seems to break GDM for user logins. Is this >> > normal, and can I force un-install wrapper without breaking anything? >> >> Excuse me, I'm a bonehead. You don't need to uninstall wrapper, just >> change this symbolic link: >> >> /usr/X11R6/bin/X@ -> Xwrapper-4 >> >> to this: >> >> /usr/X11R6/bin/X@ -> XFree86 >> >> This *will* break 'startx' for ordinary users. 'Wrapper' is intended >> to replace xdm and friends to create the .Xauthority in your home >> directory. >> >> If xdm/gdm/kdm don't create the .Xauthority file then something else >> must do it -- that something else is 'wrapper'. >> >> You don't need to use both gdm and wrapper. >> >> >> To Unsubscribe: send mail to [EMAIL PROTECTED] >> with "unsubscribe freebsd-current" in the body of the message > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4.3.0,1 +wrapper-1.0_2
wrapper is needed to run script startx by ordinary user, not root... Seems like gdm works well for me without wrapper. Shall we need to make XFree86-4.3.0,1 an option to install without wrapper package? Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Wed, 19 Mar 2003, CARTER Anthony wrote: >Xfree requires wrapper but seems to break GDM for user logins. Is this >normal, and can I force un-install wrapper without breaking anything? > >Anthony > >XFreeOn Wed, 2003-03-19 at 14:43, walt wrote: >> CARTER Anthony wrote: >> > Hi, >> > >> > I updated XFree86 this morning after a cvsup using portupgrade -r...did >> > all packages for XFree86 (Server, libraries etc. etc.) >> > >> > I now have a problem with GDM... >> > >> > I can log in as root using the GDM, but if I log in as another user, it >> > pops a message up about my session not lasting longer than 10 seconds >> > and dumping me back to login. I get a "client 5 rejected from local >> > host" in my logs, and I get a "run_session_chiled: Could not open >> > ~/.xsession-errors" on the console (even though it exists)... >> >> I have vague recollections that your ~/.xsession should be marked >> executable for xdm/gdm/kdm to work properly. Is it? I can't >> recall if there is a special group added to /etc/group for the >> xsession manager but if there is one your users may need to belong >> to that group. Does gdm run SUID? Can't recall, but it may need to. >> If 'startx' works then I assume you have 'wrapper' installed. I'm >> not sure about the interaction of wrapper with gdm but you could >> try de-installing it. Only takes a second to re-install it. >> >> >> >> To Unsubscribe: send mail to [EMAIL PROTECTED] >> with "unsubscribe freebsd-current" in the body of the message > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: LAN support for nVidia nForce2
Windows XP says that it's NVIDIA nForce MCP Networking Controller, if it can help. Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Mon, 24 Feb 2003, David O'Brien wrote: >On Mon, Feb 24, 2003 at 04:09:11PM +0600, Maxim M. Kazachek wrote: >> Is there any support of nVidia's nForce2 integrated LAN >> controller? >> Also I have following message during device probe: >> pcm0: measured ac97 link rate at 292571428 Hz > >Should be -- I committed some support for it. >rev 1.123 src/sys/pci/if_xl.c > >What sources are you using? > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: LAN support for nVidia nForce2
if_xl.c is 1.129 Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Mon, 24 Feb 2003, David O'Brien wrote: >On Mon, Feb 24, 2003 at 04:09:11PM +0600, Maxim M. Kazachek wrote: >> Is there any support of nVidia's nForce2 integrated LAN >> controller? >> Also I have following message during device probe: >> pcm0: measured ac97 link rate at 292571428 Hz > >Should be -- I committed some support for it. >rev 1.123 src/sys/pci/if_xl.c > >What sources are you using? > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: LAN support for nVidia nForce2
I CVSup'd February 24... In addition I want to say that measured ac97 link rate may be 51200 or more that 6 (about 69300 as I can remember) Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Mon, 24 Feb 2003, David O'Brien wrote: >On Mon, Feb 24, 2003 at 04:09:11PM +0600, Maxim M. Kazachek wrote: >> Is there any support of nVidia's nForce2 integrated LAN >> controller? >> Also I have following message during device probe: >> pcm0: measured ac97 link rate at 292571428 Hz > >Should be -- I committed some support for it. >rev 1.123 src/sys/pci/if_xl.c > >What sources are you using? > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
LAN support for nVidia nForce2
Is there any support of nVidia's nForce2 integrated LAN controller? Also I have following message during device probe: pcm0: measured ac97 link rate at 292571428 Hz mpg123 appears to play MP3s correctly. Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]:0:0: class=0x06 card=0x chip=0x01e010de rev=0xa2 hdr=0x00 [EMAIL PROTECTED]:0:1: class=0x05 card=0x10001695 chip=0x01eb10de rev=0xa2 hdr=0x00 [EMAIL PROTECTED]:0:2: class=0x05 card=0x10001695 chip=0x01ee10de rev=0xa2 hdr=0x00 [EMAIL PROTECTED]:0:3: class=0x05 card=0x10001695 chip=0x01ed10de rev=0xa2 hdr=0x00 [EMAIL PROTECTED]:0:4: class=0x05 card=0x10001695 chip=0x01ec10de rev=0xa2 hdr=0x00 [EMAIL PROTECTED]:0:5: class=0x05 card=0x10001695 chip=0x01ef10de rev=0xa2 hdr=0x00 [EMAIL PROTECTED]:1:0: class=0x060100 card=0x10001695 chip=0x006010de rev=0xa3 hdr=0x00 [EMAIL PROTECTED]:1:1: class=0x0c0500 card=0x10001695 chip=0x006410de rev=0xa2 hdr=0x00 [EMAIL PROTECTED]:2:0: class=0x0c0310 card=0x10001695 chip=0x006710de rev=0xa3 hdr=0x00 [EMAIL PROTECTED]:2:1: class=0x0c0310 card=0x10001695 chip=0x006710de rev=0xa3 hdr=0x00 [EMAIL PROTECTED]:2:2: class=0x0c0320 card=0x10001695 chip=0x006810de rev=0xa3 hdr=0x00 [EMAIL PROTECTED]:4:0: class=0x02 card=0x10001695 chip=0x006610de rev=0xa1 hdr=0x00 [EMAIL PROTECTED]:5:0: class=0x040100 card=0x10001695 chip=0x006b10de rev=0xa2 hdr=0x00 [EMAIL PROTECTED]:6:0: class=0x040100 card=0x10001695 chip=0x006a10de rev=0xa1 hdr=0x00 [EMAIL PROTECTED]:8:0: class=0x060400 card=0x chip=0x006c10de rev=0xa3 hdr=0x01 [EMAIL PROTECTED]:9:0: class=0x01018a card=0x10001695 chip=0x006510de rev=0xa2 hdr=0x00 [EMAIL PROTECTED]:13:0: class=0x0c0010 card=0x10001695 chip=0x006e10de rev=0xa3 hdr=0x00 [EMAIL PROTECTED]:30:0: class=0x060400 card=0x chip=0x01e810de rev=0xa2 hdr=0x01 [EMAIL PROTECTED]:9:0: class=0x01 card=0x10001000 chip=0x000f1000 rev=0x26 hdr=0x00 [EMAIL PROTECTED]:0:0: class=0x03 card=0x chip=0x011010de rev=0xb2 hdr=0x00
Re: SCSI Bios complaints and Disk Slices
Tekram DC 390 works under sym(4)... Except 390T which is powered by AMD... Cliff Sarginson: Perhaps you need try to play with disk geometry in fdisk... Try to see what geometry is 1st disk and try set something same on 2nd. Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Tue, 17 Dec 2002, Nate Lawson wrote: >On Tue, 17 Dec 2002, Cliff Sarginson wrote: >> Windows .. fine, I installed Linux .. fine. Then I installed >> FreeBSD...fine *but* the SCSI BIOS on bootup complains that the disk >> geometry is all cockeyed, and it looks that way from what it says. >> It warns any non-DOS O/S may have problems using it. >> Well I have had no problems, and fdisk makes no complaints. What has >> happened to upset the SCSI BIOS ? The thing it seems to hate is that it >> is getting 63 heads reported instead of 64. >> It is a Tekram 390 U/W controller, with an IBM 18MB U160 disk. >> There have never been any other complaints about the 1st SCSI disk. >> Diagnostics show no problems. > >One thing to check is that you should have ">1GB drive support" enabled. >This needs to be done before installing. See the archives for >freebsd-scsi list. I am not familiar with trm(4) so perhaps Oliver can >fill in more. > >-Nate > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: port upgrade problem
Looks like nobody else expirienced this problem Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Wed, 21 Aug 2002, Maxim M. Kazachek wrote: > portupgrade fails with reason (Makefile broken) on print/jadetex >and x11-fonts/webfonts due to make warning: > >"/usr/ports/Mk/bsd.port.mk", line 2580: warning: duplicate script for >target "patch-message" ignored > >When I try to make/install documentation make also shows a lot of >warnings about duplicates. > >This only affects -CURRENT, -STABLE doesn't have this error message. So >I'm afraid that it's related to -CURRENT... > > Sincerely, Maxim M. Kazachek > mailto:[EMAIL PROTECTED] > mailto:[EMAIL PROTECTED] > > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
port upgrade problem
portupgrade fails with reason (Makefile broken) on print/jadetex and x11-fonts/webfonts due to make warning: "/usr/ports/Mk/bsd.port.mk", line 2580: warning: duplicate script for target "patch-message" ignored When I try to make/install documentation make also shows a lot of warnings about duplicates. This only affects -CURRENT, -STABLE doesn't have this error message. So I'm afraid that it's related to -CURRENT... Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make warning at /usr/ports/Mk/bsd.port.mk
make warning "/usr/ports/Mk/bsd.port.mk", line 2580: warning: duplicate script for target "patch-message" ignored breaks portupgrade of several ports portupgrade says that Makefile broken on these ports (I'm not subscribed to freebsd-ports so reply direct, please) Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
opt_mac.h is missing
/sys/modules/ibsc2 wants opt_mac.h which isn't in the tree... Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
Building of x11-fonts/webfonts gives this message: "/usr/ports/Mk/bsd.port.mk", line 2580: warning: duplicate script for target "patch-message" ignored Which breaks portupgrade Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Is pcm broken?
Looks like someone broke AC97 rate measurement in -CURRENT -STABLE measures AC97 rate well (about 55900). Current gives about 41000... Hardware is Compaq EXD C600 (-STABLE) and Compaq iPAQ C700 (-CURRENT) Both are i815 equipped with SoundMAX AC97 codec... Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
nVidia nForce 420
Does nVidia nForce 420D chipset is supported by FreeBSD? I'm looking for motherboard upgrade and trying to choose chipset... I've booted my 2 week old FreeBSD on a Gigabyte 7ZXE motherboard... I don't like messages I saw... I'm thinked about Irongate+VIA686B soutbridge... But it seems that it have same problems... And looks that there are no true AMD chipset motherboard... Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.x packages and request for help.
I've recompiled kernet right before building qt... And have great prob with compiling -CURRENT right before Mar 8... I've installed -CURRENT SNAP on 20020219 which seems have broken binutils... Because xv and some other my packages coredumped with bus error (libpng issue, seemed to be solved Feb 22th) So, I was unable to compile -CURRENT after CVSup at Mar 6th (libpam issue), then was unable to run it (crypt_md5 bug). I was able to make -CURRENT up multiuser at Mar 11th, then deleted ALL packages and rebuilded from scratch... Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Thu, 14 Mar 2002, Kris Kennaway wrote: >On Fri, Mar 15, 2002 at 08:36:29AM +0600, Maxim M. Kazachek wrote: >> I've installed qt23 from ports painlessly > >Fine, I'm glad to hear it :) > >The compile problems seem to be related to recent compiler toolchain >changes, which you might not see unless you recompiled everything qt23 >depends on from scratch (which the package cluster does). > >Kris > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.x packages and request for help.
I've installed qt23 from ports painlessly Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV - Installation fails - 20020312
5.0-CURRENT have no MAKEDEV shell script anymore. Instead it have working devfs... Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5-CURRENT, make buildworld break?
It dies on the depend stage, if -DNOPROFILE is used... It needs pam_misc.h on usr.bin/su then. Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
