search for: memstick

Hi list, I am trying to install FreeBSD 9.1-Release amd64 on a Supermicro server: SuperStorage Server 6027R-E1R12N with Intel Xeon E5-2640 CPU and 32 GB (4 x 8 ) KVR16R11D4/8HC installed Currently I have only 2 SSD Kingston drives (working in mirror) installed on that server. during booting installer from the ISO CD (amd64), the boot process fails with message: Mounting from

...S == - 10.0-RC1 amd64: SHA256 (FreeBSD-10.0-RC1-amd64-bootonly.iso) = c640ac78fee2cbc411b701ecc028286c7514fe324ce5ba57176edc42fa143d85 SHA256 (FreeBSD-10.0-RC1-amd64-disc1.iso) = f41c8d4b78cfb6ec0cca4ad21f937fe1e6a65e7b61167467860110c3290d650e SHA256 (FreeBSD-10.0-RC1-amd64-memstick.img) = 9015c7cb025bc9d62eb989b22a172a756a6fb53646bad9fa83ee6e53358737f8 MD5 (FreeBSD-10.0-RC1-amd64-bootonly.iso) = f183fe88ed81d2cebef7fed42084d62b MD5 (FreeBSD-10.0-RC1-amd64-disc1.iso) = dd2b48fbe752a78d6e002abbd1a04bc6 MD5 (FreeBSD-10.0-RC1-amd64-memstick.img) = 54d1c86...

...bel) ISO Checksums: amd64: SHA256 (FreeBSD-10.0-BETA3-amd64-bootonly.iso) = 2fd1c59c94f0e30a8a23cf5a8b2b6caa565e45fc2c97dd5d831d38bf60db47e8 SHA256 (FreeBSD-10.0-BETA3-amd64-disc1.iso) = ffae9adf91e6030e0f83fecb4fe1a1cc3e8478efddbd0e2cfa5457b3e01a5134 SHA256 (FreeBSD-10.0-BETA3-amd64-memstick.img) = a9484f2f36746e5087cc2b1538a2e541f567a236f26a945d3560e473fa1655f4 MD5 (FreeBSD-10.0-BETA3-amd64-bootonly.iso) = 068262b2bbdb207b8d85e80772e6d868 MD5 (FreeBSD-10.0-BETA3-amd64-disc1.iso) = 371d2cef545029a56c4601c9c84bc464 MD5 (FreeBSD-10.0-BETA3-amd64-memstick.img) = 30878cfa7928b...

...9;ve got a new supermicro server I'm trying to get FreeBSD on. It uses the Intel c602 chipset, and it's my understanding that support for that chipset (c60X) was recently added via the isci driver. Ok, great, that explains why 8.2-R and 9.0-R didn't see the drives. So, I grabbed the memstick image of 8.3-RELEASE that is on the ftp server, booted it up, and sure enough, as the dmesg scrolls I see it now properly recognizes da0 and da1, as it should (the memstick is da2). It sees the disks fine at this point, everything looks good. However, once the system finishes booting and loads...

...74c6119c68cf0263cf6fbebc67c SHA256 (FreeBSD-10.0-RC2-amd64-disc1.iso) = 6525da2d1feddb1f16d615d76e5a4662c6fdd9a34869ce355c604f5ff147773d SHA256 (FreeBSD-10.0-RC2-amd64-dvd1.iso) = c467000b653d2f41021493f45303951ec37cf90b3b9df90df64e0e6a882a7484 SHA256 (FreeBSD-10.0-RC2-amd64-memstick.img) = f5175f1767e89826517431beae7b4dd6f3d0ff4b60a0846bf85e9871fbba2201 MD5 (FreeBSD-10.0-RC2-amd64-bootonly.iso) = 41410074f07103e2cb80bd671f1f936e MD5 (FreeBSD-10.0-RC2-amd64-disc1.iso) = 0724d22eb851c5fb4dae755dff23cb87 MD5 (FreeBSD-10.0-RC2-amd64-dvd1.iso) = b2186621073...

...6cfd7d46e2e1492ce62ec4343ab6d09bb96a6b4f4aa8dd20cd2dd SHA256 (FreeBSD-8.4-RC2-amd64-dvd1.iso) = c3216a36bca571500eb62a317a5ee114fe4f85418fa624efca93bf9fde53f2d9 SHA256 (FreeBSD-8.4-RC2-amd64-livefs.iso) = 746668b1a751a6006c8840a71656dc7a01cac524b4a023e65615cf53f561d7c0 SHA256 (FreeBSD-8.4-RC2-amd64-memstick.img) = c11dabf314c146213a8dca5b37ea6e5a67b32734d2a4958d684e27205fdc7e6a MD5 (FreeBSD-8.4-RC2-amd64-bootonly.iso) = 84b4f256fec8268adcc9b02dc2b571bb MD5 (FreeBSD-8.4-RC2-amd64-disc1.iso) = 35d6cd6b8e851e0f2bc309a165479e0f MD5 (FreeBSD-8.4-RC2-amd64-disc2.iso) = 245d2a1c9975b72a0e6a0b6e2c9cbbce MD5 (...

..."isohybrid" images, USB flash drives, and older computers for many years. So long as the computer had an optical drive, I had a work-around. Now I have a computer without an optical drive, and I decided to try to get to the bottom of the problem. I have had better luck using "memstick.bin", etc., images produced by other projects (Memtest86+, FreeBSD). If someone knows of a Debian 8.7.1 i386 Xfce installer "memstick.bin" image, please provide a URL. If someone knows of a document that explains how to build a "memstick.bin" image with the Debian 8....

...rom/gdrom.c | 1 + drivers/ide/ide-cd.c | 1 + drivers/ide/ide-gd.c | 1 + drivers/lightnvm/gennvm.c | 1 + drivers/md/bcache/super.c | 2 ++ drivers/md/dm.c | 1 + drivers/md/md.c | 1 + drivers/memstick/core/ms_block.c | 1 + drivers/memstick/core/mspro_block.c | 1 + drivers/mmc/card/block.c | 1 + drivers/mtd/mtd_blkdevs.c | 1 + drivers/mtd/ubi/block.c | 1 + drivers/nvdimm/blk.c | 1 + drivers/nvdimm/btt.c | 1 + drivers/nvdimm/...

> Hi, > > Ady wrote: > > http://repo.or.cz/syslinux.git/tree/HEAD:/diag > > "handoff.bin > > This does not look like it would tell much of the properties in question. > Nevertheless its print functions might be of interest for an isohybrid > diagnostic MBR. > > > > and at least 2 geodsp*.{bin,img(gz)} > > I am now reading >

Hi all again, I must add, there are no log entries after June 9, 2004. "LKM" message first apeared June 8, 2004, after this day, there is nothing in /var/messages, /var/security ..... How could I look for suspicious LKM module ? How could I find it, if the machine is hacked and I can not believe "ls", "find" etc. commands ? Peter Rosa

...| 2 +- drivers/ide/ide-gd.c | 2 +- drivers/lightnvm/core.c | 2 +- drivers/md/bcache/super.c | 4 ++-- drivers/md/dm.c | 2 +- drivers/md/md.c | 3 ++- drivers/memstick/core/ms_block.c | 2 +- drivers/memstick/core/mspro_block.c | 2 +- drivers/mmc/card/block.c | 3 ++- drivers/mtd/mtd_blkdevs.c | 3 ++- drivers/mtd/ubi/block.c | 2 +- drivers/nvdimm/blk.c | 2...

...| 2 +- drivers/ide/ide-gd.c | 2 +- drivers/lightnvm/core.c | 2 +- drivers/md/bcache/super.c | 4 ++-- drivers/md/dm.c | 2 +- drivers/md/md.c | 3 ++- drivers/memstick/core/ms_block.c | 2 +- drivers/memstick/core/mspro_block.c | 2 +- drivers/mmc/card/block.c | 3 ++- drivers/mtd/mtd_blkdevs.c | 3 ++- drivers/mtd/ubi/block.c | 2 +- drivers/nvdimm/blk.c | 2...

...2 PID: 55 at drivers/gpu/drm/nouveau/nvkm/subdev/secboot/ls_ucode_msgqueue.c:183 acr_ls_sec2_post_run+0x139/0x190 [nouveau] [ 1102.004949] Modules linked in: rfcomm af_packet bnep btusb uvcvideo btrtl btbcm rtsx_usb_sdmmc btintel videobuf2_vmalloc rtsx_usb_ms videobuf2_memops mmc_core bluetooth memstick videobuf2_v4l2 videodev videobuf2_common ecdh_generic rtsx_usb snd_hda_codec_hdmi usbhid snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio nouveau arc4 nls_iso8859_1 nls_cp437 i915 vfat fat intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel ath10k_pci msr kvm ath10k_cor...

Hi all, Over the last month or so I've installed FreeBSD 9 (-stable) on several Mac Minis via the memstick image; they seem to be pretty good little boxes for things like offsite secondary nameservers, for example, and they're easily replaced in case of problems. However, the newest minis have slightly different hardware, and FreeBSD can't find the built-in NIC. pciconf -lv on the new mini show...

...| 3 +- drivers/ide/ide-cd.c | 3 +- drivers/ide/ide-gd.c | 3 +- drivers/lightnvm/gennvm.c | 3 +- drivers/md/bcache/super.c | 6 +- drivers/md/dm.c | 3 +- drivers/md/md.c | 5 +- drivers/memstick/core/ms_block.c | 3 +- drivers/memstick/core/mspro_block.c | 3 +- drivers/mmc/card/block.c | 3 +- drivers/mtd/mtd_blkdevs.c | 9 +-- drivers/mtd/ubi/block.c | 3 +- drivers/nvdimm/blk.c | 3 +- drivers/nvdimm/btt.c |...

...| 3 +- drivers/ide/ide-cd.c | 3 +- drivers/ide/ide-gd.c | 3 +- drivers/lightnvm/gennvm.c | 3 +- drivers/md/bcache/super.c | 6 +- drivers/md/dm.c | 3 +- drivers/md/md.c | 5 +- drivers/memstick/core/ms_block.c | 3 +- drivers/memstick/core/mspro_block.c | 3 +- drivers/mmc/card/block.c | 3 +- drivers/mtd/mtd_blkdevs.c | 9 +-- drivers/mtd/ubi/block.c | 3 +- drivers/nvdimm/blk.c | 3 +- drivers/nvdimm/btt.c |...

...wipes the ZFS metadata. zpool labelclear [-f] device Removes ZFS label information from the specified device. The device must not be part of an active pool configuration. -v Treat exported or foreign devices as inactive. This is on FreeBSD 9.1 stable r251213 memstick install. regards Johan Hendriks Neuteboom Automatisering

...codec_hdmi snd_hda_codec_idt videobuf2_vmalloc snd_hda_intel videobuf2_memops snd_hda_codec videobuf2_core videodev media snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm joydev r592 arc4 snd_page_alloc iwlegacy mac80211 snd_seq_midi snd_seq_midi_event snd_rawmidi i915 drm_kms_helper snd_seq psmouse memstick snd_seq_device snd_timer battery cfg80211 dell_wmi acpi_cpufreq dell_laptop r852 sparse_keymap mperf drm i2c_algo_bit evdev snd wmi ac iTCO_wdt power_supply iTCO_vendor_support dcdbas processor video button coretemp microcode sm_common nand nand_ecc nand_ids mtd i2c_i801 serio_raw i2c_core rfki...

...P servers, so I cannot direct the installer to a different location very easily. The URL for the snapshots is: https://snapshots.glenbarber.us/Latest/ The SHA256 of the xz(1)-compressed install medium follows, and is also included in a plain-text file on the site. FreeBSD-10.0-CURRENT-amd64-memstick.xz = 8779f5925cb903c64d647392f6af825d5e74019d6d13222045d69091b03a81ff FreeBSD-10.0-CURRENT-amd64-release.iso.xz = cc3934c947563c23f92ba1cd8ca7ded3999dfbc050e2b2647c294e442f267040 FreeBSD-10.0-CURRENT-i386-memstick.xz = 9eb7ff8e28c0c524d2794828acb601b9b7079c1d00017e3bf84b974ff4412e42 FreeBSD-10.0-CU...

...ank on a not connected display: > > [ 12.768079] WARNING: CPU: 0 PID: 274 at drivers/gpu/drm/drm_vblank.c:609 drm_calc_vbltimestamp_from_scanoutpos+0x296/0x320 [drm] > [ 12.768080] Modules linked in: bnep snd_hda_codec_hdmi rtsx_usb_sdmmc uvcvideo rtsx_usb_ms mmc_core videobuf2_vmalloc memstick videobuf2_memops videobuf2_v4l2 videobuf2_core rtsx_usb videodev btusb btrtl arc4 snd_hda_codec_realtek snd_hda_codec_generic joydev nls_iso8859_1 hid_multitouch nls_cp437 intel_rapl x86_pkg_temp_thermal intel_powerclamp vfat coretemp fat kvm_intel iTCO_wdt iTCO_vendor_support kvm irqbypass crct10d...