FreeBSD 4.0 installation for Laptops ??
I tried to Install the 4.0 on my laptop but it dosent seem to find the ethernet card ? I have a Sager NP8620 Cirrus Logic CL-PD6729-QC-B its on 0x3000 and irq 7 Now when it boots the kernel it finds the controller and initializes it, the link light comes on and I hear a beep but when I try to select a device installation it does not list my ethernet ? It was supported under 3.3 and 3.2 (with PAO) has thier been changes ? or is thier something special i need to do ? Please any help ? Sorry for spelling thank you nathan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
FreeBSD-4.0 PCMCIA broken ?
Does FreeBSD-4.0 support IRQ sharing ? Or rather, does pccardd support
configuring devices in such a manner ?
I suspect that part of my problem with getting my 3c589D to work under
4.0 is related to this. (It has so far refused to work). For example,
under NetBSD:
...
pciide0: primary channel interrupting at irq 14
pciide0: secondary channel interrupting at irq 15
uhci0: interrupting at irq 10
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
pckbc0: using irq 1 for kbd slot
pckbc0: using irq 12 for aux slot
sb0 at isa0 port 0x220-0x237 irq 5 drq 1: dsp v3.01
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
cbb0: interrupting at irq 10
cbb1: interrupting at irq 10
...
- three different devices use irq 10 (this includes ep0, which is
at pcmcia1/cardslot1/cbb1). If I try to put it at IRQ 10 with
"device ep0 at isa? ... irq 10", it fails. If I try to make it
go to another IRQ, it fails.
If I look at dmesg from FreeBSD (sorry, cut-n-paste doesn't work
across an air gap) I see:
ata0: irq 14
ata1: irq 15
uhci0: irq 10 on pci0
pcic-pci0: irq 10 at device 10.0 on pci0
pcic-pci1: irq 10 at device 10.1 on pci0
fdc0: irq 6
atkbd0: irq 1
psm0: rq 12
pcic0: at port 0x3e0 iomem 0xd irq 10 on isa0
pcic0: management irq 11
sio0 .. irq 4 ...
sio1 .. irq 3 ...
I've also got a 3Com 3CCM156B (modem) which pccardd shows as ""("")
when I insert it, never mind that it fails to notice any pcmcia
events after popping it out and then puttint it back in.
It would also appear that pccardd fails to notice the 3c589D at boot
time if the 3CCM156B is inserted.
Darren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: lock-ups due to the scheduler
There may be additional issues with the scheduler, though they may not be related to the issue you have. Check www.freebsd.org/~dick/sched.descr I was under the impression that Peter Dufault had re-assumed this matter, but not much has happened on most of the issues. -- Richard Seaman, Jr.email: [EMAIL PROTECTED] 5182 N. Maple Lane phone:262-367-5450 Chenequa WI 53058fax:262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: lock-ups due to the scheduler
> There may be additional issues with the scheduler, though they may not > be related to the issue you have. Check www.freebsd.org/~dick/sched.descr > I was under the impression that Peter Dufault had re-assumed this matter, > but not much has happened on most of the issues. > Could you add the this problem to your list: p_rqindex does not encode which queue a process is on? Consider this scenario, we are lowering a process' priority from realtime to normal. This process is in runnable state on one of the run queues while another process is changing its p_rtprio, after it's done, a clock intr comes and the scheduler decides the process should go to another run queue, so it tries to remove process on the p_rqindex'th normal priority run queue and results in data corruption. When changing a process from one scheduling class to another, we should also move it to the apprioriate run queue (if it's in runnable state). When that's done, we will start getting reports about corrupted run queues... -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
lpr: order of print requests
I have the following problem using lpr: when the number of consecutive requests grow, they are not printed in the same order. This happens on several versions from 2.2.7 to 3.4. All the requests are printed, but the order is not the same of the requests. Effectively the order is initially right, but then it fails and skips a number of requests that are printer later. Why this happens? What can I do? Any suggestions?? Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Asus K7V boot failure
On Fri, 28 Apr 2000 23:15:55 +0200, Jeroen Hogeveen <[EMAIL PROTECTED]> said: Jeroen> Hey Chris and Jordan, I've got one too, you should however Jeroen> disable your boot virus protection in the bios setup! Jeroen> This will fix the problem you described. Jeroen> Maybe something to mention in the FAQ, if it is not yet there. Yup, fixed here, and something definetely for an FAQ. Many thanks! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Cross building freebsd?
I've searched through the mailing list archives and otherwise searched around, but haven't found any real solid information, so... I'm looking for any and all information about for cross-building Freebsd for embedded Powerpc platforms. (The powerpc porting project is just getting started and this info isn't available there.) [Background: I've ported Chorus and Linux to this platform. So I pretty well understand the generic process. I just need freebsd-specific info.] Specifically, I need to know: 1. Exactly what FreeBSD-specific things need to be done to a GCC-2.95.2 compilation system to get cross builds to work? a. What headers should be used? (Not newlib, right?) b. What as and ld should be used. c. What kind of abi options are necessary? Like stack frames, -f, etc... d. etc I've scanned through the GCC and Binutils stuff and I have a rough idea, but I'd appreciate advice from someone who's actually been there and done that! (Maybe one of the original Alpha porters?) 2. What are the mechanical steps needed to insert a new port? a. I plan to scan for "[Aa]lpha" in the entire source tree and do what they did, but perhaps there is an easier way? Like, where are architecture-specific things hiding? 3. How do you actually cross-build FreeBSD? Is there a FAQ? a. Again, I plan on scanning for alpha, but a cookbook would be easier. Thanks! -- Robert Withrow -- (+1 978 288 8256) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Cancun,Mexico-Orlando,Florida-Maui,Hawii
Call NOW: 1-407-645-1232 KIDS STAY FREE Accomodations include: 5 days and 4 nights in a FIVE STAR RESORT or GOLD CROWN HOTEL. and admission to any of the major Theme Parks including Magic Kingdo, MGM Studios, Epcot Center and Animal Kingdom. KIDS STAY FREE Call Now and receive your choice of a FREE 3 day, 2 night BONUS GETAWAY to Hawaii, Mexico or Las Vegas! Over 50 Locations to choose from. KIDS STAY FREE Call now and receive a free upgrade to a fully furnished 2 bedroom, 2.5bath villa at no extra charge. Not enough? Receive a free Casino Cruise! This is the last week. CALL NOW: 1-407-461-2456 To be removed from this mailing list please reply to: [EMAIL PROTECTED] 1stUp.com - Free the Web® Get your free Internet access at http://www.1stUp.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Cross building freebsd?
Robert Withrow wrote: > > I've searched through the mailing list archives and otherwise > searched around, but haven't found any real solid information, > so... > BEWARE: I have never done this, but I probably have a reasonable guess since I wrote the basic "crosskit" ports we carry. > > Specifically, I need to know: > > 1. Exactly what FreeBSD-specific things need to be done to a > GCC-2.95.2 compilation system to get cross builds to work? > Take a look at Jerry Hicks' crossm68k ports, there is everything you need to start with a cross binutils and a crossgcc. You should only have to change the TARGET, but it would be good to check the crossgcc FAQ at cygnus, JIC there is something special about the powerpc crosscompiler. > a. What headers should be used? (Not newlib, right?) > b. What as and ld should be used. > c. What kind of abi options are necessary? Like stack >frames, -f, etc... > d. etc > WRT (b) the crossbinutils will produce the as and ld you need. There are two possible paths: 1) building FreeBSD from the start (probably the hardest). - Since you are building for an embedded system you don't need any OS on your target. Something like powerpc-elf should work (look in the crossgcc FAQ for the supported targets). - You should then start porting FreeBSD's libc with this compiler; newlib is probably a good reference. - The rest of the userland has to be built, but I wouldn't bet on the resulting kernel booting due to problems while crossbuilding from 32 to 64 bits. 2) Using another target (probably the path used by FreeBSD-Alpha) -If you have access to the platform in question but just want the crossutils to help, you could use the equivalent NetBSD target (powerpc-netbsd-elf ?). -In this case you can also use NetBSD's headers and libraries while you get started, and get the FreeBSD userland (booter, etc) ported. - Eventually you can get a working kernel and some drivers. All more easily said than done... cheers, Pedro. > I've scanned through the GCC and Binutils stuff and I have a rough > idea, but I'd appreciate advice from someone who's actually been > there and done that! (Maybe one of the original Alpha porters?) > > 2. What are the mechanical steps needed to insert a new port? > > a. I plan to scan for "[Aa]lpha" in the entire source tree and > do what they did, but perhaps there is an easier way? Like, where > are architecture-specific things hiding? > > 3. How do you actually cross-build FreeBSD? Is there a FAQ? > > a. Again, I plan on scanning for alpha, but a cookbook would > be easier. > > Thanks! > > -- > Robert Withrow -- (+1 978 288 8256) > [EMAIL PROTECTED] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: lock-ups due to the scheduler
On Fri, 28 Apr 2000, Richard Seaman, Jr. wrote: > There may be additional issues with the scheduler, though they may not > be related to the issue you have. Check www.freebsd.org/~dick/sched.descr > I was under the impression that Peter Dufault had re-assumed this matter, > but not much has happened on most of the issues. Why don't we do a investigation (reinvestigation for you, of course), evaluation of solutions, implementation of the best solution, and review between all of us, and get Bruce or Peter Dufault to review them as well? We could do this for each scheduler problem you have listed, and get them all fixed within a month's time, if we just handle them all as the individual cases, and work on each one serially? I'm quite willing to do everything I can to help, including the evaluation, solving, and testing of each problem separately. > -- > Richard Seaman, Jr.email: [EMAIL PROTECTED] > 5182 N. Maple Lane phone:262-367-5450 > Chenequa WI 53058fax:262-367-5852 -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: lock-ups due to the scheduler
On Fri, Apr 28, 2000 at 06:13:32PM -0400, Brian Fundakowski Feldman wrote: > On Fri, 28 Apr 2000, Richard Seaman, Jr. wrote: > > > There may be additional issues with the scheduler, though they may not > > be related to the issue you have. Check www.freebsd.org/~dick/sched.descr > > I was under the impression that Peter Dufault had re-assumed this matter, > > but not much has happened on most of the issues. > > Why don't we do a investigation (reinvestigation for you, of course), > evaluation of solutions, implementation of the best solution, and > review between all of us, and get Bruce or Peter Dufault to review > them as well? We could do this for each scheduler problem you have > listed, and get them all fixed within a month's time, if we just > handle them all as the individual cases, and work on each one > serially? > > I'm quite willing to do everything I can to help, including the > evaluation, solving, and testing of each problem separately. Be my guest. There is a patch set, now about a year old at the same site as the description. I held up working on this because no one else seemed interested (I got no comments to a posting about a year ago), plus I wasn't sure my solution (an adaptation of Peter Dufault's solution) was right for SMP. In fact, I think it wasn't. Also, I wanted to give some of the other issues more study and got sidetracked on other things. Feel free to pick up any of this. I seem to remember that Bruce had some problems with Peter Dufault's original verion of the patch set, and I'm not aware that he ever looked at my modified version. In any event, the patch set is now out of date. -- Richard Seaman, Jr.email: [EMAIL PROTECTED] 5182 N. Maple Lane phone:262-367-5450 Chenequa WI 53058fax:262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
swapinfo typo?
# swapinfo Device 1K-blocks UsedAvail Capacity Type /dev/rad0s1b 1022720 102272 0%Interleaved /dev/rad1s1b 2558720 255872 0%Interleaved Total 3581440 358144 0% # I'm probably misunderstanding something, but... should this just be reporting '/dev/ad' and not '/dev/rad'? -Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Adding -maxdepth and -mindepth options to find(1)
Hi,
A request came up on the FreeBSD-questions list earlier for the
-maxdepth option as found in GNU find to work in FreeBSD's find. It
turns out that -prune will do what this guy wanted, but would it be a
good idea to add -maxdepth (and -mindepth just to be consistent) for
any other people who might want it? I've attached a patch to implement
this, if I don't get any feedback I'll send-pr it instead, I thought I
might get a few opinions here first.
--
Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D
Index: extern.h
===
RCS file: /usr/cvs/src/usr.bin/find/extern.h,v
retrieving revision 1.9
diff -u -r1.9 extern.h
--- extern.h1999/12/19 15:43:18 1.9
+++ extern.h2000/04/28 19:42:08
@@ -80,6 +80,8 @@
PLAN *c_xdev __P((void));
PLAN *c_openparen __P((void));
PLAN *c_closeparen __P((void));
+PLAN *c_maxdepth __P((char *));
+PLAN *c_mindepth __P((char *));
PLAN *c_mmin __P((char *));
PLAN *c_mtime __P((char *));
PLAN *c_not __P((void));
Index: find.1
===
RCS file: /usr/cvs/src/usr.bin/find/find.1,v
retrieving revision 1.23
diff -u -r1.23 find.1
--- find.1 2000/03/01 10:48:32 1.23
+++ find.1 2000/04/28 19:48:12
@@ -245,6 +245,12 @@
If the file is a symbolic link, the pathname of the linked\-to file will be
displayed preceded by ``\->''.
The format is identical to that produced by ``ls \-dgils''.
+.It Ic -maxdepth Ar n
+True if the depth of the current file into the tree is less than or equal to
+.Ar n .
+.It Ic -mindepth Ar n
+True if the depth of the current file into the tree is greater than or equal to
+.Ar n .
.It Ic -mmin Ar n
True if the difference between the file last modification time and the time
.Nm find
Index: find.h
===
RCS file: /usr/cvs/src/usr.bin/find/find.h,v
retrieving revision 1.6
diff -u -r1.6 find.h
--- find.h 1999/12/19 15:43:18 1.6
+++ find.h 2000/04/28 19:44:31
@@ -46,7 +46,7 @@
N_MTIME, N_NAME,
N_NEWER, N_NOGROUP, N_NOT, N_NOUSER, N_OK, N_OPENPAREN, N_OR, N_PATH,
N_PERM, N_PRINT, N_PRUNE, N_SIZE, N_TYPE, N_USER, N_XDEV,
- N_PRINT0, N_DELETE
+ N_PRINT0, N_DELETE, N_MAXDEPTH, N_MINDEPTH
};
/* node definition */
Index: function.c
===
RCS file: /usr/cvs/src/usr.bin/find/function.c,v
retrieving revision 1.22
diff -u -r1.22 function.c
--- function.c 2000/02/05 18:42:34 1.22
+++ function.c 2000/04/28 22:42:14
@@ -717,6 +717,66 @@
}
/*
+ * -maxdepth n functions --
+ *
+ * Does the same as -prune if the level of the current file is greater
+ * than the specified maximum depth.
+ */
+int
+f_maxdepth(plan, entry)
+ PLAN *plan;
+ FTSENT *entry;
+{
+ extern FTS *tree;
+
+ if (entry->fts_level >= plan->t_data && fts_set(tree, entry, FTS_SKIP))
+ err(1, "%s", entry->fts_path);
+ return (1);
+}
+
+PLAN *
+c_maxdepth(arg)
+ char *arg;
+{
+ PLAN *new;
+
+ if (*arg == '-')
+ /* all other errors handled by find_parsenum() */
+ errx(1, "-maxdepth: %s: value must be positive", arg);
+
+ new = palloc(N_MAXDEPTH, f_maxdepth);
+ new->t_data = find_parsenum(new, "-maxdepth", arg, NULL);
+ return (new);
+
+}
+
+/*
+ * -mindepth n functions --
+ *
+ * True if the current file is at or deeper than the specified minimum
+ * depth.
+ */
+int
+f_mindepth(plan, entry)
+ PLAN *plan;
+ FTSENT *entry;
+{
+
+ return (entry->fts_level >= plan->t_data);
+}
+
+PLAN *
+c_mindepth(arg)
+ char *arg;
+{
+ PLAN *new;
+
+ new = palloc(N_MINDEPTH, f_mindepth);
+ new->t_data = find_parsenum(new, "-mindepth", arg, NULL);
+ return (new);
+}
+
+/*
* -mtime n functions --
*
* True if the difference between the file modification time and the
Index: option.c
===
RCS file: /usr/cvs/src/usr.bin/find/option.c,v
retrieving revision 1.9
diff -u -r1.9 option.c
--- option.c1999/12/19 15:43:19 1.9
+++ option.c2000/04/28 19:41:56
@@ -84,6 +84,8 @@
{ "-inum", N_INUM, c_inum, O_ARGV },
{ "-links", N_LINKS,c_links,O_ARGV },
{ "-ls",N_LS, c_ls, O_ZERO },
+ { "-maxdepth", N_MAXDEPTH, c_maxdepth, O_ARGV },
+ { "-mindepth", N_MINDEPTH, c_mindepth, O_ARGV },
{ "-mmin", N_MMIN, c_mmin, O_ARGV },
{ "-mtime", N_MTIME,c_mtime,O_ARGV },
{ "-name", N_NAME, c_name, O_ARGV },
Re: lpr: order of print requests
At 4:40 PM +0200 4/28/00, Lorenzo Iania wrote: >I have the following problem using lpr: >when the number of consecutive requests grow, they are not printed in the >same order. This happens on several versions from 2.2.7 to 3.4. All the >requests are printed, but the order is not the same of the requests. >Effectively the order is initially right, but then it fails and skips a >number of requests that are printer later. > >Why this happens? What can I do? Any suggestions?? I am not sure what you mean by "requests". Do you mean many 'lpr' commands from different users/hosts, or do you mean many files on a single 'lpr' command? If you mean many 'lpr' commands, are they coming in from many different hosts to some central print server? --- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Yamaha DS-XG Sound Card or Chip?
Have anyone successfully configured this card on FreeBSD? I think it is an on board sound chip in my Dell desktop. -- Behcet Sarikaya Computer Communications Lab. The University of Aizu Tsuruga, Ikki-machi, Aizu-wakamatsu City Fukushima, 965-8580 Japan Tel. +81-242-37-2559 Fax. +81-242-37-2742 Home page: http://www.u-aizu.ac.jp/~sarikaya/ email: [EMAIL PROTECTED]
