OpenBSD and FreeBSD resources » FAQ http://purebsd.com Tue, 01 Jun 2010 06:01:11 +0000 en hourly 1 http://wordpress.org/?v=3.1 Frequently Asked Questions http://purebsd.com/frequently-asked-questions-2.html http://purebsd.com/frequently-asked-questions-2.html#comments Tue, 01 Jun 2010 05:57:15 +0000 admin http://purebsd.com/?p=79
  • /kernel: ad1s1e: UDMA ICRC error..
    If you see stuff like this:
    May 5 22:05:00 antarctica /kernel: ad1s1e: UDMA ICRC error writing fsbn 4159 of 2048-2063 (ad1s1 bn 4159; cn 0 tn 66 sn 1) retrying
    May 5 22:05:00 antarctica /kernel: ad1s1e: UDMA ICRC error writing fsbn 4159 of 2048-2063 (ad1s1 bn 4159; cn 0 tn 66 sn 1) falling back to PIO mode
    Chances are, you’re not too happy with this.

    Solution: You might have an Athlon system with a VIA chipset with your ATA/66 IDE harddisks connected to the controller with a 40 ribbon IDE cable. Try connecting them with an ATA/66 80 ribbon cable. In my case, it solved the problem. And I have made sure it was the 80 ribbon cable that caused the problem to stop.

    Though this is was seen on a FreeBSD system, other BSD flavors could report something similar. Certainly my ex-Linux workstation had a similar problem. Though not until 2.2.19 did the kernel report something on it. Before that, the system just went instable and reported _nothing_ (-:

  • More to come.. if you just ask me (-:
    • ]]>     http://purebsd.com/frequently-asked-questions-2.html/feed 0     Frequently Asked Questions http://purebsd.com/frequently-asked-questions.html http://purebsd.com/frequently-asked-questions.html#comments Tue, 01 Jun 2010 05:43:11 +0000 admin http://purebsd.com/?p=76
  • Error: specified device does not match mounted device
    Installing OpenBSD on a SPARC Classic went fine but while booting it wouldn’t change the root partition to read-write mode, because «specified device does not match mounted device» (mount shows it as «root_device», not something like /dev/sd0a)

    Solution: Both boot-device and nvramrc variables in the PROM of the machine could be set to Linux (or an other OS) specific settings. After you clean and/or reconfigure the PROM settings, the system will boot correctly. Probably (-:
    How to clean-up? Type «STOP-A» on your keyboard and enter the «new command mode» of the SUN boot PROM. Type «set-defaults». That will set everything at default. Type «printenv» to review the current settings.

  • Error: strange pciide timeouts
    If this kernel message shows up on the console and in the log files
    May 29 16:04:25 server /bsd: pciide0:1:0: device timeout, c_bcount=0, c_skip=0
    you will certainly not like it. But there is hope!

    Solution: If you have a CDROM connected to the same IDE ribbon cable as the harddisk, chances are that’s causing the trouble. Try if removing the CDROM off the IDE cable works. If there is a CDROM, but not on the same cable as a harddisk, try to disconnect the CDROM device completely of the IDE subsystem. In other words, pull the cable out of the CDROM.

  • More to come.. if you just ask me (-:
    • ]]>     http://purebsd.com/frequently-asked-questions.html/feed 0