search for: hdx

Hello, I have a problem with older version of anaconda linux installer. I have upgraded kernel in my distro, but, when this anaconda boot with new 3.4.52 kernel, can NOT find cdrom. As far as I understand, this is because the new kernel recognize cd drive as srX, scdX instead of older hdX with 2.6.18. At the moment I can not upgrade anaconda and forced this kernel to recognize it as before. Are there any kernel command line argument, kernel config or something else for kernel 3.4.52 to recognize this cdrom as hdX? Best Regards, -- Oguz YILMAZ

hi, on centos 5.x and fedora 6 there are hdX and sdX while from fedora 7 (and probably centos 6.x) there will be only sdX. is it possible with the latest centos kernel to use the same ata_piix driver to handle all disk (ie. both pata and sata) so we've only sdX disk devices like it's the current setup on newer fedora release. we try t...

I have a 500GB Sata drive about 15% used I would like to make an exact copy of too another Sata 500GB drive as a spare. That way if something happens to the one in service I can plug in the spare quickly and restore one of the weekly backups without reinstalling the entire OS and all the little tweaks of setup on this mail/web server. How do I do this? That is make an exact bootable copy of a

Add code to create the device directory under sysfs. Signed-off-by: K. Y. Srinivasan <ksrinivasan at novell.com> --- drivers/staging/hv/blkvsc_drv.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/staging/hv/blkvsc_drv.c b/drivers/staging/hv/blkvsc_drv.c index b3d05fc..4fb8094 100644 --- a/drivers/staging/hv/blkvsc_drv.c +++

Add code to create the device directory under sysfs. Signed-off-by: K. Y. Srinivasan <ksrinivasan at novell.com> --- drivers/staging/hv/blkvsc_drv.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/staging/hv/blkvsc_drv.c b/drivers/staging/hv/blkvsc_drv.c index b3d05fc..4fb8094 100644 --- a/drivers/staging/hv/blkvsc_drv.c +++

...think about this change properly, and I'm pretty > sure it's not required. The reason is that the only place %idemap is > modified is in the section guarded: > > if ($libata) { > ... > } > > If the guest is using libata it will not have any references to > /dev/hdX devices, as IDE devices are presented as SCSI devices. That's > a NAK to this bit of the patch. Instead, you need to work out when SLES > switched to libata and set $libata accordingly above. If there are never any hdX devices in libata machines, why are they renamed in the first place?...

On 5/1/2017 11:04 ??, Nikolaos Milas wrote: > Can others please report the content of /boot/grub2/device.map on > their CentOS 7 (physical or virtual) installations? Thank you all for your reports. Since it seems this is generally the case with CentOS 7, does anyone also have access to RHEL 7 installations to verify if this is the case with these installations as well? > And can any

...uirements to escape the "=", or blowing the parameter separators (I tried both spaces and commas, and one long quoted string)? Steve Brown sbrown7 at umbc.edu P.S.: The particular parameters that I have tried passing in have been just about all permutations of pci=noprobe, idex=noprobe, hdx=noprobe, and hdx=none (with the proper replacements of "x", of course).

Hi, I don´t think that this is a ext3 Problem, since you have problems partitioning that disk. Perhaps a hdparm -i /dev/hdX could shine some light on this, also a fdisk -l /dev/hdX could be useful. For now - let me guess: <guess> To me, it seems, that the disk is clipped to 32GB, perhaps the mainboard bios can not cope with a disk >32GB - just a thought. Since the manufactorer knows that every customer woul...

...m pretty > > sure it's not required. The reason is that the only place %idemap is > > modified is in the section guarded: > > > > if ($libata) { > > ... > > } > > > > If the guest is using libata it will not have any references to > > /dev/hdX devices, as IDE devices are presented as SCSI devices. That's > > a NAK to this bit of the patch. Instead, you need to work out when SLES > > switched to libata and set $libata accordingly above. > > If there are never any hdX devices in libata machines, why are they renamed...

Hi, I'm running into issues receiving faxes which, from what I have read, may be caused by frame slips. While I can find many posts saying to investigate it, I can't find any that describe *how* to debug the problem. Tried searching this list as well to no avail. Any pointers would be greatly appreciated. FYI, I'm running wbel, AMP 1.04, spandsp 2pre4. Faxing to a pstn on a

I created on my 60Gb hdd (data=journal) journal with 16Mb size, i think it not enough. As it is possible to change size of journal ?

Hi, I installed a new kernel with ext3 support and I want to convert my ext2 partitions to ext3. I used to do tune2fs -j /dev/hdX I did this and it works. Now I converted one of my partitions, the other are system ones (/home, /boot, /) Do I have to do this command when these partitions umounted (the other was)? How do I do that, I cannot start this program if there are not mounted. Or do I think wrong? Another question....

> If I understand the syntax correct, it is: > (hdX,Y)/path/to/file", where X is disk number and Y is partition number. > As far as I understand X and Y are zero based. > > I've tested it with qemu and 2 disks: > - the first with bootloader > - the second with kernel+rootfs > > I've used the following configuratio...

Redhat 7.2 - ext3 filesystem. Is it possible to recover deleted files immediately after deleting them? I have found utilities for recovering data from ext2 filesystems... Help Regards Matt Cunningham Technology Manager Digital Post matt@digipost.co.nz

I successfully installed Xen 2.0.4 from source on a Slackware 10 system. I installed grub, got that working and all. But when I boot the dom0 kernel, I get: cmd 0x5a timed out hdc: lost interrupt My hdc is my dvd burner... when I applied a kernel option of "hdc=ide-scsi" it seemed to have skipped over it but recieved the same error on hdd ... I''ve tried recompiling with

...~ m{^/dev/(sd|hd)([a-z]+)}); - $guestif{$1} ||= {}; - $guestif{$1}->{$1.$2} = 1; + # Modern distros use libata, and IDE devices are presented as sdX + my $libata = 1; + + # RHEL 2, 3 and 4 didn't use libata + # RHEL 5 does use libata, but udev rules call IDE devices hdX anyway + if ($desc->{distro} eq 'rhel') { + if ($desc->{major_version} eq '2' || + $desc->{major_version} eq '3' || + $desc->{major_version} eq '4' || + $desc->{major_version} eq '5') + { +...

...ould > only ever use the major number that was actually allocated to us. We certainly should be pushing everyone toward using the 'xdX' etc devices that are allocated to us. However, the installers of certain older distros and other user space tools won't except anything other than hdX/sdX, so its useful from a compatibility POV even if it never goes into mainline, which I agree it probably shouldn't. Ian

...ould > only ever use the major number that was actually allocated to us. We certainly should be pushing everyone toward using the 'xdX' etc devices that are allocated to us. However, the installers of certain older distros and other user space tools won't except anything other than hdX/sdX, so its useful from a compatibility POV even if it never goes into mainline, which I agree it probably shouldn't. Ian

...s and get these spikes with either card in the system. This is an Athlon-64 3000+ CPU and Fedora Core 2. zaptel-1.0.2. Is there anyone who has a TDM card on a "quiet" system who can run System Monitor and observe CPU utilization? Thanks for your help. P.S. I do 'hdparm -u1 /dev/hdx' on the disks. -- Michael Welter Introspect Telephony Corp. Denver, Colorado US +1.303.674.2575 mike@introspect.com www.introspect.com