Re: 4.4 RC4 ISO packages?
| - www/netscape47-{communicator,navigator} are forbidden, so add
What does this mean, they are 'forbidden' ? Crypto issues?
jm
--
My other computer is your windows box.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Realtek 8100
Anyone set up FreeBSD on a motherboard with a Realtek 8100 Ethernet controller on it? Just wondering what it takes. I am looking to buy some mobos with everything I need on board for some low profile systems, and several have the Realtek 8100's on them. Since the systems will be light duty servers, no X, the onboard video will not be an issue. The cases I plan on using do not have the height for standard cards, so I just need to make sure what I get will work well with FreeBSD. --Eric To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: UDMA ICRC error reading fsb (?)
Dave Uhring wrote: > > On Saturday 08 September 2001 08:32 am, ian j hart wrote: > > Dave Uhring wrote: > > > On Friday 07 September 2001 11:48 pm, Marius Strom wrote: > > > > FWIW, I had this error and assumed it was cabling. I've spent > > > > the last few hours copying data of what is now a dead disk and > > > > putting it back on a new disk. YMMV. > > > > > > > > On Fri, Sep 07, 2001 at 11:45:28PM +0100, ian j hart wrote: > > > > > Dave Uhring wrote: > > > > > > On Friday 07 September 2001 17:04, Randall Hopper wrote: > > > > > > > Dave Uhring: > > > > > > > |On Thursday 06 September 2001 07:43 pm, Randall Hopper > wrote: > > > > > > > |> What do these messages mean? Are CRCs done by the > > > > > > > |> IDE controller on DMA transfers and they're coming up > > > > > > > |> wrong? > > > > > > > |> > > > > > > > |> ad0s2a: UDMA ICRC error writing fsbn 3283483 of > > > > > > > |> 396704-396713 (ad0s2 bn 3283483; cn 204 tn 98 sn 49) > > > > > > > |> retrying > > > > > > > | > > > > > > > |Your drive is dying. Back it up and replace it. > > > > > > > > > > I think you are being a tad premature. > > > > > > > > > > There have been plenty of posts on this subject, both on stable > > > > > and hardware. IIRC none of them were bad disks. > > > > > > > > > > Randall, > > > > > 1) post a copy of dmesg so we can see what hardware you have. > > > > > 2) measure the cable - M/B to drive. > > > > > > > > > > > > Ok, thanks. But what do these messages "mean" on a > > > > > > > technical level? > > > > > > > > > > > > > > And could these just as well indicate a marginal cable, bad > > > > > > > connector, loose connector, or the other hard drive on the > > > > > > > controller being a bit flakey? > > > > > > > > > > > > > > Randall > > > > > > > > > > > > CRC's (16 bit cyclic redundancy check characters) have been > > > > > > done on controllers since we had to use floppies. The first > > > > > > Winchester drive interface I ever designed back in 1979 had a > > > > > > Fairchild 9401 (IIRC) CRC generator chip on it. The writes > > > > > > are failing. You "may" have marginal cabling or loose or > > > > > > corroded connectors. > > > > > > > > > > > > If you wish to keep using the drive, replace the cable and in > > > > > > doing so your contacts will also wipe clean. > > > > > > > > > > -- > > > > > ian j hart > > > > > > IDE cables which are somewhat too long can cause many problems with > > > data transfer. However, the cable certainly didn't grow in length > > > overnight. > > > > It's a new disk, which may be the problem as some hardware > > combinations have problems. It's also possible the cable was replaced > > at the same time. > > I found the problem was load related (at least at first). Maybe the > > system is now under a heavier load. > > > > >Sudden onset of the described problems "may" be due to > > > corrosion of the cable contacts, but it is most likely due to a > > > drive failure. Most modern drives support S.M.A.R.T. and it would > > > be nice if FreeBSD had a utility to detect the drive's complaints. > > > Perhaps it is in the ports, but my weak eyes have failed to see it. > > > > "most likely": Would your opinion change if it turns out to be a VIA > > chipset M/B? > > > > See also the Lazarus like Re: ad2s1e: UDMA ICRC error reading fsbn... > > "most likely"? No, I use one myself (MSI K7T Pro2 A) with no problems > whatsoever. Both IDE drives are IBM-DTLA. But I don't use a SB Live, > either ;) IIRC that's an 82C686 - different bug to the 82C586B. There seems to be a reluctance to provide dmesg output, which doesn't help. Off on a tangent here - does tagged queuing work? -- ian j hart To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: nfs installworld failure
Dan Pelleg wrote: > > ian j hart <[EMAIL PROTECTED]> writes: > > > horio shoichi wrote: > > > > > > ian j hart wrote: > > > > > > > > > > > > > > > > usr.sbin/stallion/bootcode > > > > install -c -o root -g wheel -m 444 2681.sys cdk.sys > > > > /usr/libdata/stallion > > > > install 2681.sys: Permission denied > > > > ***Error code 71 > > > > > > > > > > > > > > > > mounting src and obj -maproot=0 "fixes" > > > > > > > > stable cvsup'd this morning (UK mirror) > > > > > > > > -- > > > > ian j hart > > > > > > > > > > A Good Thing has happened for you. The deafult NFS server > > > behavior relieves filesystems from many errors by ubiquitous > > > roots on the lan. > > > > I think you miss the point - although it is rather a subtle > > usage of the English language. maproot fixes the problem > > in the same way that amputation fixes gangrene. That's what > > the quotes imply. ie. I shouldn't need to do this. > > > > As a point of order, can anyone confirm this behavior? > > > > My 0.02 euro - this breaks the release. > > > > Confirmed; this happens here too. Chmod-ing the > usr.sbin/stallion/bootcode/*.sys files to 444 (as root on the NFS > server) fixes this. They were 400 for some reason a quick look at the > source and cvs log did not reveal. The commits on 2001/08/30 are probably responsible. Taking a guess at the culprits email address. > > -- > > Dan Pelleg -- ian j hart To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Getting [alt] key working on console
Hi all, I've been looking trought the mail archives and found some information about how to write a keymap to get the [alt] key working. (My keyboard is an spanish one). What I've found is this: I've to get my current keymap (i.e. spanish.iso.acc) and copy it to spanish.emacs.acc, for example. Then I've to go trought each letter, get its ascii(7) value and at to it the 0x80 hex number. Well, done it, but some times it works and some others it doesn't. I usually get weird characters when pressing alt+key. I think there is some error when doing this +0x80 in one of the keys, but I don't know... (I get this same, weird, behavivour when trying the us.emacs keymap that comes with freebsd). Any idea? I want to use readline's keybinding on the console! And emacs... Why FreeBSD's console is so problematic?... Other problems that I have are these: - The backspace key does not work as expected in emacs. I've tried the us.emacs hack, and works fine with emacs, but then, other programs like BitchX, do not get the backspace key properly. - It can't distinguish between Alt and AltGr (spanish key)... Any ideas? Sorry for this so long message, but I'm getting crazy. Thanks in advance. PGP signature
Reading 720kb floppies
Hi all, I'm getting errors when trying to read 720kb floppies under FreeBSD. This hapens either with mtools or with mount_msdos (all 720kb floppies fail). Is this a kernel issue? How can I access them? Thanks. -- FreeBSD is the power-- Julio Merino <[EMAIL PROTECTED]> ICQ: 18961975 PGP signature
Re: UDMA ICRC error reading fsb (?)
Marius Strom wrote: Appologies if I'm telling you what you already know, but for the benefit of the thread, and because this comes up regularly... > > By dead I mean rapidly increasing numbers of bad sectors on the drive > with every write. I replaced the cable to no avail. The hard drive had > otherwise functioned well for ~7-8 months. UDMA ICRC errors started > popping up ~2 months after installation, and then last night suddenly I > was unable to hit a slew of sectors. > > HD was a WD Caviar 30 Gig. That's not enough info. The interaction between the controller and the HDD is important. Send a dmesg with this drive attached. Unfortunately this is exactly the symptom you get when you have either a cable length or a controller/HDD miss-match. Do the problems go away when you disable UDMA with sysctl? This looks like the same time frame as my problems at home. I suspect that changes to the ata code (ie better UDMA support) tickled a hardware bug. (This is on the VIA UDMA33 chipset). When I replaced these drives the situation got WORSE because the new drives were faster than the old. This eventually lead me to fit very short cables - which fixed the problem. Don't make the mistake of thinking you have fixed your problem untill you verify that the old drive really is scrap. Even then new drives can give you a new set of problems. Assuming you now have the drive copied try #dd if=/dev/zero ... with and without UDMA. Verify the block numbers are the same each time. Make sure you zero the right drive ;) If Maxtor have a test utility you could try that. I had 4 Seagate drives (at work) which were apparently scrap. Two failed the Seagate diagnostic and hit the bin at 9.8m/s/s. Two were OK and worked fine when dropped to pio mode. Cheap and nasty M/B, with early UDMA66 controller! > > On Sat, Sep 08, 2001 at 02:15:52PM +0100, ian j hart wrote: > > Marius Strom wrote: > > > > > > FWIW, I had this error and assumed it was cabling. I've spent the last > > > few hours copying data of what is now a dead disk and putting it back on > > > a new disk. YMMV. > > > > What do you mean by "dead"? The way I describe "dead" being able to copy > > data off it is a neat trick. eg drive doesn't spin. > > > > What did you do about the cabling problem? > > What hardware do you have? > > > > > > > > On Fri, Sep 07, 2001 at 11:45:28PM +0100, ian j hart wrote: > > > > Dave Uhring wrote: > > > > > > > > > > On Friday 07 September 2001 17:04, Randall Hopper wrote: > > > > > > Dave Uhring: > > > > > > |On Thursday 06 September 2001 07:43 pm, Randall Hopper wrote: > > > > > > |> What do these messages mean? Are CRCs done by the IDE > > > > > > |> controller on DMA transfers and they're coming up wrong? > > > > > > |> > > > > > > |> ad0s2a: UDMA ICRC error writing fsbn 3283483 of 396704-396713 > > > > > > |> (ad0s2 bn 3283483; cn 204 tn 98 sn 49) retrying > > > > > > | > > > > > > |Your drive is dying. Back it up and replace it. > > > > > > > > I think you are being a tad premature. > > > > > > > > There have been plenty of posts on this subject, both on stable and > > > > hardware. IIRC none of them were bad disks. > > > > > > > > Randall, > > > > 1) post a copy of dmesg so we can see what hardware you have. > > > > 2) measure the cable - M/B to drive. > > > > > > > > > > > > > > > > Ok, thanks. But what do these messages "mean" on a technical level? > > > > > > > > > > > > And could these just as well indicate a marginal cable, bad > > > > > > connector, loose connector, or the other hard drive on the controller > > > > > > being a bit flakey? > > > > > > > > > > > > Randall > > > > > > > > > > CRC's (16 bit cyclic redundancy check characters) have been done on > > > > > controllers since we had to use floppies. The first Winchester drive > > > > > interface I ever designed back in 1979 had a Fairchild 9401 (IIRC) CRC > > > > > generator chip on it. The writes are failing. You "may" have marginal > > > > > cabling or loose or corroded connectors. > > > > > > > > > > If you wish to keep using the drive, replace the cable and in doing so > > > > > your contacts will also wipe clean. > > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > > > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > > > -- > > > > ian j hart > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > -- > > > Marius Strom <[EMAIL PROTECTED]> > > > Professional Geek/Unix System Administrator > > > URL: http://www.marius.org/ > > > http://www.marius.org/marius.pgp 0xF5D89089 *updated 2001-02-26* > > > > > > It is a natural law. Physics tells us that for every action, there must be an > > > equal and opposite reaction. They hate us, we hate them, they hate us back and > > > so, here we are, victims of mathematics. > > > -- Londo, "A Voice in the Wilderness I" > > > > -- > > ian j hart > > -- > Marius Strom
XFree86 4.1 crashing
Hi, I have cvsup the ports tree as of Friday 7th, CET, and built XFree86-4 from scratch on a 4.3 box. I am runing the VESA driver, and the thing shuts down every now and then with SIGSEGV. The time for these crahes is rather random. For instance, it happens happens during device initialization in KDE2 when I have "extmod"in /etc/X11/XF86Config. If I remove "extmod", the crashes persist, but happen later on. Has anybody else experienced these symptoms? Are they related to FreeBSD or should I look for help on the XFree86 side? Juanjo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: UDMA ICRC error reading fsb (?)
By dead I mean rapidly increasing numbers of bad sectors on the drive with every write. I replaced the cable to no avail. The hard drive had otherwise functioned well for ~7-8 months. UDMA ICRC errors started popping up ~2 months after installation, and then last night suddenly I was unable to hit a slew of sectors. HD was a WD Caviar 30 Gig. On Sat, Sep 08, 2001 at 02:15:52PM +0100, ian j hart wrote: > Marius Strom wrote: > > > > FWIW, I had this error and assumed it was cabling. I've spent the last > > few hours copying data of what is now a dead disk and putting it back on > > a new disk. YMMV. > > What do you mean by "dead"? The way I describe "dead" being able to copy > data off it is a neat trick. eg drive doesn't spin. > > What did you do about the cabling problem? > What hardware do you have? > > > > > On Fri, Sep 07, 2001 at 11:45:28PM +0100, ian j hart wrote: > > > Dave Uhring wrote: > > > > > > > > On Friday 07 September 2001 17:04, Randall Hopper wrote: > > > > > Dave Uhring: > > > > > |On Thursday 06 September 2001 07:43 pm, Randall Hopper wrote: > > > > > |> What do these messages mean? Are CRCs done by the IDE > > > > > |> controller on DMA transfers and they're coming up wrong? > > > > > |> > > > > > |> ad0s2a: UDMA ICRC error writing fsbn 3283483 of 396704-396713 > > > > > |> (ad0s2 bn 3283483; cn 204 tn 98 sn 49) retrying > > > > > | > > > > > |Your drive is dying. Back it up and replace it. > > > > > > I think you are being a tad premature. > > > > > > There have been plenty of posts on this subject, both on stable and > > > hardware. IIRC none of them were bad disks. > > > > > > Randall, > > > 1) post a copy of dmesg so we can see what hardware you have. > > > 2) measure the cable - M/B to drive. > > > > > > > > > > > > > Ok, thanks. But what do these messages "mean" on a technical level? > > > > > > > > > > And could these just as well indicate a marginal cable, bad > > > > > connector, loose connector, or the other hard drive on the controller > > > > > being a bit flakey? > > > > > > > > > > Randall > > > > > > > > CRC's (16 bit cyclic redundancy check characters) have been done on > > > > controllers since we had to use floppies. The first Winchester drive > > > > interface I ever designed back in 1979 had a Fairchild 9401 (IIRC) CRC > > > > generator chip on it. The writes are failing. You "may" have marginal > > > > cabling or loose or corroded connectors. > > > > > > > > If you wish to keep using the drive, replace the cable and in doing so > > > > your contacts will also wipe clean. > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > -- > > > ian j hart > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > > with "unsubscribe freebsd-stable" in the body of the message > > > > -- > > Marius Strom <[EMAIL PROTECTED]> > > Professional Geek/Unix System Administrator > > URL: http://www.marius.org/ > > http://www.marius.org/marius.pgp 0xF5D89089 *updated 2001-02-26* > > > > It is a natural law. Physics tells us that for every action, there must be an > > equal and opposite reaction. They hate us, we hate them, they hate us back and > > so, here we are, victims of mathematics. > > -- Londo, "A Voice in the Wilderness I" > > -- > ian j hart -- Marius Strom <[EMAIL PROTECTED]> Professional Geek/Unix System Administrator URL: http://www.marius.org/ http://www.marius.org/marius.pgp 0xF5D89089 *updated 2001-02-26* It is a natural law. Physics tells us that for every action, there must be an equal and opposite reaction. They hate us, we hate them, they hate us back and so, here we are, victims of mathematics. -- Londo, "A Voice in the Wilderness I" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
4.4-RELEASE
Does anyone know when 4.4 will be released? I have seen discussion that it would be pushed back to the 14th of this month but I do not recall seeing any official statement to that effect. AFAIK it should be released today.. right? Personally it makes not much different but ive alerted clients of upgrades to 4.4 and i have to keep them up to par on whats going on also. Any ideas? TIA Holt __ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
