IDE Drives re-ordered after Kernel upgrade? - Forums Linux |
- IDE Drives re-ordered after Kernel upgrade?
- can't install RedHat 9 / my WD disk is not recognized
- can not access cd-rom
- confused:root
- Booting TWO win partition with DIRECTLY with GRUB
- CDROM mounting problem please help!
- lilo, ldm, sata, raid won't boot...
- can't login as user account
- Apache/PHP
- Repeatable FC3 meltdown after a week... Disk? Heat?
- Fedora Core 2 wont detect modem.
- FEDORA CORE2- eth0 goes "inactive" after reboot-HELP!
- Mp3 support under Fedora Core 2.44 (using XMMS or any other app)
- Stop looking for my hde and hdg drives during boot!
- Redhat vs Slackware?
- Firewall for Linux
- Root Partition
- sd_mod spinning up empty removable drive... forever!
- Xbox linux site
- How to write on a NTFS partition
- Linux's HPFS Support
- Compilation of (NIC) Module Parameters
- rpm does not work
| IDE Drives re-ordered after Kernel upgrade? Posted: 15 Feb 2005 05:06 AM PST "pmp" <cjb.net> wrote in message news:1gs2er2.gyu7t1f83h2jN%cjb.net... It does mean the IDE code has been poked around. Since 2.6 is coming into major use, you may just want to leapfrog the issues of playing with 2.4. Alternatively, what about upgrading 4 revisions at a time, instead of 11? And try a 2.4.23 kernel, which I believe was pretty good? |
| can't install RedHat 9 / my WD disk is not recognized Posted: 14 Feb 2005 03:54 PM PST <com> wrote in message news:googlegroups.com... Recent releases of Linux can resize NTFS. It's much safer than attempting to write files inside NTFS, for a stack of technical reasons. The commonly used tool for this is "parted", and I just stood amazed as a SuSE 9.2 intalltion DVD did it automatically to a Windows XP Home box I thought would first have to be scrubbed. |
| Posted: 14 Feb 2005 01:52 PM PST OK, figured out, but still have question. I add ide=nodma to the grub init script, now the CD-ROM works great! My question: from the name of this configuration, it seems I turns off DMA on IDE bus, then isn't that data access to both CD-ROM and harddisc will be slowed down? Is there any way I can only turn off DMA to CD-ROM, but not other devices? My guess is my Samsung CD drive is of old type, it is not working very well with the 2.4.22 kernel. But this kernle is the one I need to use. Google returns a page saying same problem as mine, that person says RedHat 7.3 works fine with his/her CD-drive. I wornder what kernel version of 7.3 is? I am using Fedora core - 1 and its kernel version is 2.4.22. I am wondering if I should uninstall my current Fedora and install RedHat 7.3. |
| Posted: 14 Feb 2005 12:43 PM PST Sorry for my curiosity, I know it does not matter, but just want to know... " password entered at the screen is encrypted and compared to the encrypted password stored in the system." -- when you say "stored in the system", it must be some file on the harddisck, right? Actually I my system is RedHat and see a file /etc/shadow, as root I open the file, and I see something looks like root encrypted password, they are ascII characters, but not the one I input on the screen, anyway is it the encrypted password for root? Thanks. |
| Booting TWO win partition with DIRECTLY with GRUB Posted: 14 Feb 2005 02:09 AM PST I found out that the XP registry holds information about mounted disks (it suffices that the XP sees these disks once) and then even if you hide them with grub, XP still knows about them. What I did was erase the mounted disks entries from the registry. guy |
| CDROM mounting problem please help! Posted: 13 Feb 2005 10:57 PM PST "Peter T. Breuer" <it.uc3m.es> wrote in message news:it.uc3m.es... And once again Peter spends his day yanking the chains of newbies and leaving out the important bits, just to pretend that his opinion is somehow useful. /dev/cdrom is often, not always, set up as a symbolic link to the "real" CD device. Different software has different conventions about this, and various things can change what your CD device actually shows up as. For example, older versions of the "cdrecord" software cannot handle CD devices with write capability as IDE devices, so older versions of cdrecord and the 2.4 kernel require you to load the ide-scsi module to do any CD writing. This can confuse the heck out of various auto-probing software, and when you later load the modules or decide not to load them, you wind up with a link from /dev/scd0 to /dev/cdrom, or from /dev/hdd to /dev/cdrom, and it may not do what you expect. In general, don't use /dev/cdrom because of exactly this sort of confusion. The idea of using symlinks to give devices easily understand names is common, but fragile, Instead use the IDE device directly (which you can check for by looking in /proc/ide and checking which /proc/ide/*/media file has "cdrom" in it), or use the SCSI device directly (usually /dev/scd0 if your CD drive is showing up as SCSI). Most Linux installations try to do this for you, but they're not consistent or reliable about it. RedHat, for example, tries to auto-detect the CD drive and set the symlink /dev/cdrom to something usable. SuSE tries to auto-detect such devices and access them as mountable locations /media/cdrom but shows the same device as /media/cdrecorder, for example. |
| lilo, ldm, sata, raid won't boot... Posted: 13 Feb 2005 06:38 PM PST "Michael Buchenrieder" <muc.de> wrote in message news:muc.de... Never put your bare bones OS on software RAID, because when it gets screwed up for whatever reason, it can be exceptionally difficult to repair. SuSE is especailly bad for this, since their "rescue" setups seem to lack most of the important drivers and tools that the "installation" setups provide form the same installation media. |
| Posted: 13 Feb 2005 02:12 PM PST fchiausa wrote: I had the same problem with an account and the only way I got round it was this. backup the users home folder to /home/dan.bak delete the user and recreate it. copy over only the essential dot files from the backup folder to the new one. i copied back the .bash* and .mozilla and .wine i just left everything else out. there are so many possible files that could be causing this problem that is your best approach. |
| Posted: 13 Feb 2005 11:42 AM PST "Charles" <edu> wrote in message news:cuoaj0$5vk$unix.fas.harvard.edu... First, use "yum" to do a full update of *everything*. Yum is available for RedHat 9 from the www.fedoralegacy.org website and works quite well for working out all the dependencies. Second, consider updating from RedHat 9, which has been unsupported and deprecated for at least a year now. Third, what are you trying to build in PHP and Apache that is not in the standard or updated releases for RedHat 9? |
| Repeatable FC3 meltdown after a week... Disk? Heat? Posted: 13 Feb 2005 02:50 AM PST Well, anything's possible, but it doesn't sound like hardware. I'd bet you are updating from a questionable source and installing the same bad package. Care to give us more info on how you have "done lots of updates"? Tom F. |
| Fedora Core 2 wont detect modem. Posted: 12 Feb 2005 07:05 PM PST Nico Kadel-Garcia wrote: It is a winmodem more than likely. If the following doesnt work buy a "real" hardware based external modem. http://www.linuxvoodoo.com/resources/howtos/dell_2650_modem/ Most Dell Inspiron 2650 laptops come with the Actiontec 560RD based winmodem which requires the drivers available below. This is one of those cases where you do actually need a seperate download. Installation is fairly straightforward as the driver's installation script is pretty smart at configuring your modem. Requirements * A Dell Inspiron 2650 with the Actiontec modem (or any other system with a supported HSF modem) * Linux drivers for Conexant (formerly Rockwell) Softmodem HSF modem family. * At least a 2.4 (stable) kernel (source installed and previously compiled. Installation Start with the download (see resources below). The following instructions are from the INSTALL file included with the tar.gz package. Since not everyone is using a Red Hat based system, I'll use instructions for the source package. 1. Extract the package with "tar -xzf hsflinmodem-{version}.tar.gz" 2. Change to the package directory with "cd hsflinmodem-{version}" 3. Run "make install" from the top of the package directory. 4. Run "hsfconfig" to complete the installation and configure your modem. 5. Follow the on-screen instructions - usually selecting the default for this modem works fine (if you are in the USA). Installation Notes Debian users might need to change the KERNELSRC definition in modules/common.mak before running the make install command. An example is included on how to change that KERNELSRC line on the top of the modules/common.make file included in the source tree of the drivers. Red Hat and similar users can generate RPMS from the tar package using "rpm -ta hsflinmodem-{version}.tar.gz". Post-installation At this point the modem is installed and configured and you can access it through /dev/ttySHSF0 or /dev/cuaHSF0 (call-out device). Additionally, you can use it via the symbolic link /dev/modem (equivalent to ttySHSF0) which is usually automatically created during the installation process. User access To allow non-root users to access this device you can create a new group with for example "groupadd modem" and change the permissions on the /dev/ttySHSF0 device to modem with "chown root.modem /dev/ttySHSF0". Simply add the users to the /etc/group file under the modem group so it looks like this: modem:x:1004:user1,user2,user3,freddy. Note that the group id (1004) will vary from system to system. Double check the permissions on the device nodes with "ls -l /dev/ttySHSF0" to ensure that they are adequate for your system. Alternatively, you can set the same permissions used above to the /dev/modem symbolic link for easier access to the modem. Using the modem You can now use any dialup tool you wish, such as wvdial, the Red Hat dialup tool, KPPP etc. These are standard tools on most distributions. When asked to specifiy the port or modem device to use simple specify /dev/modem or /dev/ttySHSF0 which ever is convenient. Making changes later The "hsfconfig" command can be used to change certain modem configuration options or recompile (generic packages only) the kernel modules after installation. Run "hsfconfig --help" for usage information. Questions? Use our support resources (forums, live chat, e-mail forms etc). Resources * http://www.mbsi.ca/cnxtlindrv * The README and INSTALL files included in the Conexant HSF package * Current Conexant HSF package driver download * Supported modem/controller list: HSFi, HSF, Intel MC97 Controller (ICH), VIA MC97 Controller, ALI MC97 Controller, Basic2 / SmartDAA, Athens (Yukon) (Complete list) |
| FEDORA CORE2- eth0 goes "inactive" after reboot-HELP! Posted: 12 Feb 2005 08:39 AM PST The system is using static IPs not DHCP I originally was using FC3 but uninstalled it because they removed support for the mega raid driver. So I went back to FC2. I had this same problem in FC3. This is running on brand new hardware. On Sat, 12 Feb 2005 22:06:00 -0500, "Nico Kadel-Garcia" <net> wrote: |
| Mp3 support under Fedora Core 2.44 (using XMMS or any other app) Posted: 12 Feb 2005 06:15 AM PST Thanks! Downloading and installing xmms-mp3 from rpmfind.net did the trick. - yvan Jose Maria Lopez Hernandez wrote: how that already the system packaged live, time, burn |
| Stop looking for my hde and hdg drives during boot! Posted: 12 Feb 2005 06:04 AM PST "Bill Unruh" <physics.ubc.ca> wrote in message news:cumlqr$1pu$itservices.ubc.ca... I am going to be *REALLY* surprised if a motherboard recent enough to have built-in SATA controllers does not have an option to disable it in the BIOS. |
| Posted: 12 Feb 2005 04:02 AM PST On Sat, 12 Feb 2005 04:02:45 -0800, Yef wrote: Yes, you would be wrong. there are many other differences... This is basically true. Although Slackware can use rpm to some degree. And nothing is stopping you from using tar'ed packages on RH. I suppose this is true. RH does seem to have more gui config tools. I think you got this backwards. To quote from Slackware documentation : "Slackware uses the BSD-style layout for its initialization files. Each task or runlevel is given its own rc file. This provides an organized structure that is easy to maintain. There are several categories of initialization files. These are system startup, runlevels, network initilization, and System V compatibility. As per tradition, we'll lump everything else into an "other" category." Info on RH's init setup can be found here : http://squidward.mit.edu/rhel-doc/RH-DOCS/rhel-rg-en-3/s1-boot-init-shutdown-sysv.html -- - Matt - |
| Posted: 12 Feb 2005 12:12 AM PST On 2005-02-12, Jack// ani <com> wrote: Linux has a built-in, kernel level firewall that can be configured using iptables. The defaut settings are usually pretty restricitve, so unless you have specific requirements (running various servers, etc.) you probably don't have to do much with it. You can see what rules are being used by running "iptables -L" at a command prompt. Pop-ups, ads, and cookies are application level annoyances, and need to be dealt with at that level. FireFox and Mozilla both have excellent pop-up and cookie control built in, and the AdBlock extension can be installed to block ads as well. -- John (dhs.org) |
| Posted: 11 Feb 2005 09:58 PM PST Jumbo wrote: You better just resize the windows partition, leaving unpartitioned "free space" on the drive, and let the linux installer do the remainder of the job (which will be creating a swap and at least a / partition, with /home recommended to be a separate one). -- Longhorn error#4711: TCPA / NGSCP VIOLATION: Microsoft optical mouse detected penguin patterns on mousepad. Partition scan in progress *to*remove*offending*incompatible*products.**React ivate*MS*software. Linux woodpecker.homnet.at 2.6.10-mm1[LinuxCounter#295241,ICQ#4918962] |
| sd_mod spinning up empty removable drive... forever! Posted: 11 Feb 2005 03:07 PM PST kermit wrote: [...] Hm, this might be the problem. My regular Debian based 2.4 setup without initrd recognises the Vendor: SyQuest, Model: SQ3270S, Rev: 1_27 etc. The 2.6.9 Fedoraalike gets only the Rev: 1_27 field while having both VENDOR:MODEL empty! I have a gut feeling that this might be tightly connected to the problem I experience. Yes, that might be the case. I immediately found and tried modprobe.conf but with no apparent results. Then i tried to blame the "hotplug" stuff but blacklisting the module(s) didn't help either. OK. Going to check what I can do with the initrd. I may probably need to change the "aic" driver module too... Thank you for the good pointers. |
| Posted: 11 Feb 2005 10:14 AM PST mjt wrote: install them <snip> Thanks. This is the one I go to. Totally broken. Every other site I use is perfect. Guess I'll not look at FC3 then !! |
| How to write on a NTFS partition Posted: 11 Feb 2005 10:06 AM PST "Michael Heiming" <michael+heiming.de> wrote in message news:heiming.de... OK, good point. Or you'd need to add an external drive. Do you have the space to install wienie partitions? This can actually work, as long as you haven't over-partitioned and stripped down the available space for /home due to allocating space for /usr/src, /usr/local/, /var/tmp, /var/tmp, /var/spool, /etc., etc., etc.. In the last 5 years, I've done this *once*, with someone who really liked having really old (for speed) distros along with really new (for performance) distros. There are some potential issues. #1. Not all distros create compatible file systems, even the same type of file system. The 7.x RedHat release, for example, used a mkfs that made the ext2 partitions unreadable to 6.x. I ran headlong into that one: you had to use the mkfs binary from RedHat 6.x #2: You probably want to keep the entirety of both file systems available to the other OS installations. Let's say that "/" from one OS becomes "/diska/" when mounted on the other, and "/" from the other becomes "/diskb" when mounted on the first. If you leave the /home still as part of the first OS and mounted there, it can be accessed by a symlink to /home -> /diska/home. Workable, but graceless. #3: HOWEVER! Different OS's often have rather different ideas about user configuration files, and therein lies the rub of maintaining the identical user account across multiple OS's. The associated .X configuration files, ..gnome, .mozilla, etc. can and do interfere with each other. I've seen systems destabilize wildly because the .cshrc written for one system caused utter chaos when implemented on the other. (Admittedly, it was a terrible ..cshrc, but still, it wasted quite a lot of my time getting the person to let me fix it for them.) So that's actually a reason *against* sharing /home's between OS's, even on the same laptop. In such a situation, I can certainly see using a shared partition. But I wouldn't make it /home. |
| Posted: 11 Feb 2005 06:08 AM PST Alex Taylor wrote: I agree it's not hard and it is a fairly simple concept, but that wasn't really what I was getting at. I've been compiling Linux kernels for the past seven years or so. As a systems manager for many years before that I also had to regularly squeeze every bit of performance I could from HP minicomputers and so on, quarter ton things with architectures that made anything smaller seem like toys to me - OS/2 and Linux made me change my view there! So as an ex tech-head, I still have a tweaking urge for any PC operating system operating that's worth it. In recent years though, I've been on the other side of the fence, with a business as well as technology focus. I've got a keen interest in doing my little bit, as many others around the world are also, to make Linux a serious desktop alternative for government use in particular. I'd argue that a "serious Linux user" in this wider context is not about compiling kernels, it's about business users, open standards, interoperability and being able to get the job done better with a lower TCO and good support. So on my home setup, I prefer to get things up and running smoothly so I can start being productive, the tweaking should come later. That for me means having at least one partition that any modern Linux flavour should be able to see out of the box, so that I have instant access to drivers and configuration notes I may need straight away. FAT32 seems to be the pragmatic choice for that these days. Another consideration is that the modern Linux distributions are becoming more sophisticated in the way of scripting and configuration. Poking around in Xandros reveals some very fancy stuff that needs some study first. I did a quick kernel recompile the other night with no errors but quite a few module warnings which I'd prefer to look closely at later rather than installation time. Now that I have everything operational, I'll probably revisit Xandros & HPFS when I get some spare time. |
| Compilation of (NIC) Module Parameters Posted: 10 Feb 2005 12:37 PM PST Norm Dresner wrote: Try: modinfo path_to_the_module, e.g. modinfo /lib/modules/2.4.27/kernel/drivers/net/3c59x.o -- Tauno Voipio tauno voipio (at) iki fi |
| Posted: 10 Feb 2005 09:10 AM PST "David Dorward" <com> wrote in message news:cug9tp$hcs$2$demon.co.uk... This can happen when the RPM database is locked. Check if any other RPM processes are running with "ps auxwww", make sure they're all dead, and try again with "-v -v" added. If it's still hanging, you need to delete the lock files at /var/lib/rpm/_*, maybe use "rpm --rebuilddb" to clean up any debris, then try again. Your system could also be overwhelmed and swapping like crazy.... |
| You are subscribed to email updates from TextNData Forums - Linux To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google Inc., 20 West Kinzie, Chicago IL USA 60610 | |
