ral

Thanks DOlsen. But I guess I'll try to borrow a copy of AVP first before buying one. "If I ever find out a better way of compiling stuff, then I'll remake the RPMs sometime and they would prolly work on most systems." No problem. Your doing enough. Me I am just a leech living of other people work :D

Any chance there RPM's will work with RH8? Also, can you use AVP or do you need to use AVP Gold? Thanks DOlsen.

Here is another one: http://news.zdnet.co.uk/story/0,,t269-s2127602,00.html

Found this message here: http://www.mail-archive.com/linux-hardware...u/msg03196.html "From: Chetan Ahuja <ahujache@cse.msu.edu> Crossposted-To: alt.os.linux.mandrake,comp.os.linux.setup Subject: Strange bootup problem with Mandrak 7.1 (maybe UDMA related) Date: 19 Jul 2000 18:46:52 GMT Hi, I have installed Mandrake 7.1 on a computer consisting of an Asus ME 99B motherboard (which contains an on-board UDMA66 port), a Celeron 500, and a Western digital WCD 102 AA ( UDMA66) hard drive. The problem, which is rather wierd, is this-- After the install, I can boot into the system just fine... Once. The system comes up properly... starts all the services etc. Then halt and reboot the system. That's it. No more booting!!! I get a "kernel panic. Unable to mount root file system on IDE 3:05" ( or something similar. I'm away from the machines in question right now). Amazing thing is, I reinstalled the whole system, it booted properly exactly once and then refused to boot again. What's going on here? I'm completely baffled. I understand that a lot of people have had problems with Mandrake 7.1 and UDMA 66 devices. But why would it boot ONCE and not again. I don't know what IDE chipset is on the board. (I did see a winbond chip on the board which is usually the IDE controller... is that it?). Has anybody encountered this combination of MB and hard disk. If yes," how did you get around this problem. Do I have to disable the UDMA mode in the the BIOS? But the question remains, if the problem was with the UDMA driver, why would it boot even once. Could somebody please throw some light on this. Thanks a lot Chetan Ahuja" Information is dated and probably irrelevant by now though. What bother me most is that the MB appears to be an AT board and the HD is refurbished. On the other hand the price is reasonable, expecially since it looksl like those Lindows Microtel boxes are going for $298 now.

Thanks Motts, I was typing my last message before seeing yours. Sounds like you got it right. At least that is what I am going to try as soon as I get the new kernel source which I need to rebuild the src.rpm. Thanks. And thanks for the thorough explanation and detailed instructions.

Okay so I am a dummy... Nvidia Kernel drivers (?) are kernel specific. Manage to get X working on the new kernel by unisntalling the Nvidia drivers from the old kernel. To get 3D working on the new kernel I would have to download a Nvidia Kernel which is built for my kernel or rebuild one. Sorry if this sounds a bit confused. But its 6:16 am :) Got plenty of help from a fellow with the handle Sharaz: http://www.linuxiso.org/forums/viewtopic.p...p?p=11679#11679 I'd like to see MS do this for a home office user with a single install.

I will have to continue later... I appreciate all the help and will try what you suggested, but am having some major linux problems right now which I need to resolve first. I just wnated to say that people like you make Linux support the best in the world (I have about 40 pieces of licensed proprietary software so I really know what I am talking about). Thanks.

This is a long one. Updated my RH8 through the RedHat Network up2date utility (Kernel 2.4.18-19.8.0). However, I was not able to start x. The configuration wizard was not able to fix the problem either. RedHat 8 default install desktop install (Gnome)/2.4.18-14 GeForce 2MX Set Vsync and Hsync rates as per monitor specs (MAG770FS) Added NVidia 3123 drivers Added KPPP Added Xine When I booted with the original RH8 Kernel everything went fine. I figured that my inability to Start X could be becuase of the NVidia 3123 drivers to I tried to disable them by changing "nvidia" back to "nv" (in oding so destorying my pre-nvidia XF86Config). The result was I could not startx with either kernel. Well I am still a newbie and an impatient one at that. To fix the problem I tired using vi, but I could not figure out how to use it, so intead, I restored my backup XF86COnfig: rm XF86Config mv XF86Config.backup XF86Config Now I got the original RH8 Kernel working again...whew... Would be grateful for any advice on how to get Gnome working with the new kernel. Thanks.

I think I would rather get the Microtel box and dump Lindows :) Wait a minute...am at Walmart right now (online)...and can't find the old 1$199 box anymore...hhhmmm.

Sorry, edited my message while you were posting your reply. Yes, that sounds very reasonable. I guess I use them becasue they are they default choices in my distro...but I think I will try to get ssmpt. Did some reading. I understand one difference is that Sendmail runs as root, while postfix does not have to. Not sure if this is correct though/

Nothing really, I was just poking around Linux and realized I had two options. Not really sure which one is better. Used both and they both seem to work fine. But anyway, my use is mainly as a personal desktop, and I only use ot it to check a single account.

Which is the better mail transport agent ot use - Sendmail or postfix? Thanks.

"I have a big heatsink and plan on disconnecting the fan on it to cut down on the noise"... I don't think that would be too advisable. I have a PIII 700E. The fan died two nights ago and the thing went past 72 degrees celcius in the the minute or so it took me to discover what the problem was (granted it had the Intel heatsink). If you want a fanless CPU, your best bet is to go with a VIA C3 processor.

Might be obvious...but just in case...have you already formatted drive C: to be a FAT32 partition?

If I remember correctly, lm_sensors is part of the RH8 default install. Okay apparently with RH8 you need to log on as root in the X WIndow and can't just do it in the console :?: "[root@localhost root]# sensors Can't access /proc file /proc/sys/dev/sensors/chips or /proc/bus/i2c unreadable; Make sure you have done 'modprobe i2c-proc'! [root@localhost root]# sensors-detect This program will help you to determine which I2C/SMBus modules you need to load to use lm_sensors most effectively. You need to have done a `make install', issued a `depmod -a' and made sure `/etc/conf.modules' (or `/etc/modules.conf') contains the appropriate module path before you can use some functions of this utility. Read doc/modules for more information. Also, you need to be `root', or at least have access to the /dev/i2c[-/]* files for some things. You can use prog/mkdev/mkdev.sh to create these /dev files if you do not have them already. If you have patched your kernel and have some drivers built-in you can safely answer NO if asked to load some modules. In this case, things may seem a bit confusing, but they will still work. IF THIS IS AN IBM THINKPAD, PRESS CTRL-C NOW! IBM Thinkpads have a severely broken i2c/SMBus implementation, just scanning the bus will break your thinkpad forever! We can start with probing for (PCI) I2C or SMBus adapters. You do not need any special privileges for this. Do you want to probe now? (YES/no): Probing for PCI bus adapters... Use driver `i2c-sis5595' for device 00:02.0: Silicon Integrated Systems SIS5595 Use driver `i2c-riva' for device 01:00.0: GeForce2 MX Probe succesfully concluded. We will now try to load each adapter module in turn. Load `i2c-sis5595' (say NO if built into your kernel)? (YES/no): /lib/modules/2.4.18-14/kernel/drivers/i2c/i2c-sis5595.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.18-14/kernel/drivers/i2c/i2c-sis5595.o: insmod /lib/modules/2.4.18-14/kernel/drivers/i2c/i2c-sis5595.o failed /lib/modules/2.4.18-14/kernel/drivers/i2c/i2c-sis5595.o: insmod i2c-sis5595 failed Loading failed ()... skipping. Load `i2c-riva' (say NO if built into your kernel)? (YES/no): modprobe: Can't locate module i2c-riva Loading failed ()... skipping. ** Note: i2c-riva module is available at ** http://drama.obuda.kando.hu/~fero/cgi-bin/rivatv.shtml Do you now want to be prompted for non-detectable adapters? (yes/NO): To continue, we need module `i2c-dev' to be loaded. If it is built-in into your kernel, you can safely skip this. i2c-dev is not loaded. Do you want to load it now? (YES/no): Module loaded succesfully. We are now going to do the adapter probings. Some adapters may hang halfway through; we can't really help that. Also, some chips will be double detected; we choose the one with the highest confidence value in that case. If you found that the adapter hung after probing a certain address, you can specify that address to remain unprobed. That often includes address 0x69 (clock chip). Some chips are also accessible through the ISA bus. ISA probes are typically a bit more dangerous, as we have to write to I/O ports to do this. Do you want to scan the ISA bus? (YES/no): Probing for `National Semiconductor LM78' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `National Semiconductor LM78-J' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `National Semiconductor LM79' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `Winbond W83781D' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `Winbond W83782D' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `Winbond W83627HF' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `Winbond W83697HF' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `Silicon Integrated Systems SIS5595' Trying general detect... Success! (confidence 9, driver `sis5595') Probing for `VIA Technologies VT82C686 Integrated Sensors' Trying general detect... Failed! Probing for `ITE IT8705F / IT8712F / SiS 950' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `IPMI BMC KCS' Trying address 0x0ca0... Failed! Probing for `IPMI BMC SMIC' Trying address 0x0ca8... Failed! Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `sis5595' (should be inserted): Detects correctly: * ISA bus, undetermined address (Busdriver `i2c-isa') Chip `Silicon Integrated Systems SIS5595' (confidence: 9) I will now generate the commands needed to load the I2C modules. Sometimes, a chip is available both through the ISA bus and an I2C bus. ISA bus access is faster, but you need to load an additional driver module for it. If you have the choice, do you want to use the ISA bus or the I2C/SMBus (ISA/smbus)? WARNING! If you have some things built into your kernel, the below list will contain too many modules. Skip the appropriate ones! To load everything that is needed, add this to some /etc/rc* file: #----cut here---- # I2C adapter drivers modprobe i2c-isa # I2C chip drivers modprobe sis5595 #----cut here---- To make the sensors modules behave correctly, add these lines to either /etc/modules.conf or /etc/conf.modules: #----cut here---- # I2C module options alias char-major-89 i2c-dev #----cut here---- [root@localhost root]#" It does not seem to work too well though: "[ral@localhost ral]$ sensors sis5595-isa-8008 Adapter: ISA adapter Algorithm: ISA algorithm VCore 1: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM VCore 2: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM +3.3V: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM +5V: +6.85 V (min = +6.85 V, max = +6.85 V) ALARM fan1: 0 RPM (min = 0 RPM, div = 8 ) ALARM fan2: 0 RPM (min = 0 RPM, div = 8 ) ALARM temp: +51?C (limit = +51?C, hysteresis = +51?C) ALARM alarms: Board temperature input (usually LM75 chips) ALARM [ral@localhost ral]$"

According to http://mbm.livewiredev.com/comp/elite.html I have the following sensors: K7S6A Sensors Chip: SIS950/ITE705 Case Sensor: SIS950/ITE705 1 CPU Sensor: SIS950/ITE705 2 From the posts I tried the following: [ral@localhost ral]$ su Password: [root@localhost ral]# sensors Can't access /proc file /proc/sys/dev/sensors/chips or /proc/bus/i2c unreadable; Make sure you have done 'modprobe i2c-proc'! [root@localhost ral]# sensors-detect bash: sensors-detect: command not found Will keep trying.

I tried running "modprobe i2c-proc", but I got a command not found message. Thanks for the links... will go thorugh them in a bit and see what if I can find a soluction. Thanks.

When I run "sensors" in the console I get this message: "[ral@localhost ral]$ sensors Can't access /proc file /proc/sys/dev/sensors/chips or /proc/bus/i2c unreadable; Make sure you have done 'modprobe i2c-proc'! [ral@localhost ral]$" Relevant system specs: RedHat 8.0/Gnome ECS K7S6A Motherboard (SiS 745 Chipset) Checked out the help file, but still don't have a clue as to how to get it going. Only reading I care about really is tempreature. Motherboard has sensors which can be view in Windows. Thanks in advance.

Thanks. Great link. What is plugger?

Could it be a hardware thing? I used KDE and ML8.2 and ML9.0 in three different machines, and they have all been rock stable. Run RTCW and Quake II without a hitch. It never crashed on me. In seven months I only used XKill once (other than the times when I was just testing it).

Well...it works for me...and it work well enough for the SysAdmin of the Law School to decide to deploy ML9 instead of RH8 for desktop duty... altough RH will occupy Servers and Workstations.

I have participated to a greater or lesser extent in the deployment of Linux (RH 7.3. RH 8 and ML 9) in two places. An Internet Cafe (2 of 11 PC's) and a Law School Library (approx 180 of 200 PC's). The problem with having to explain things to people is that works when you are dealing with a few people. Having to explain things to 600 students and 300 staff, with 200 new students every year is a bit of a difficult task. Similarly, having to give people a short course before renting out a machine would also be difficult. In the case of the Internet Cafe, its now back to all Windows for now (it was more conveneient to acquire 2 more XP licenses especialy since they sell Windows OEM licenses here so long as you buy any piece of hardware like a screw and not necesarilly bundled with a new unit --- this also makes going to Xandros more expensive). Mozilla integration though, went well witout much causing problems. OpenOffice causes a few problems but has now also been successfully integrated. So now we have 98/2k/XP boxes running either OOo or Office 2000 and Mozilla and looks like we will be getting a few more XO's in the next few months to replace the remaining Win95 licenses. Its still on testing in the Law School for another 5 months, but there have been plenty of complaints so far. I love Linux, but I have to admit, migrating to Linux in a environment where you have multiple and changing users has proven more difficult than expected, Nos. 1 & 2 being the main problems. By the way, the Law School was using RH only until I showed them Supermount. As problematic as it may seem for some people, it actually got ML in the door

I am not surprised they are in financial trouble. http://www.mandrakeusers.org/viewtopic.php...der=asc&start=0 "For $60 a year, you don't get much at all. Really, its just a way of supporting the MDK distro BTW Im a member icon_smile.gif" Look at what the competition is offering. Red Hat Network Basic service level: $60/year per system subscription Red Hat Network Basic service provides software management, priority service, and access to Instant ISOs (full versions of Red Hat Linux) for individuals with one or more systems. A Basic subscription is required for each system supported on Red Hat Network. A Basic subscription to Red Hat Network provides: * Email notifications of available updates (errata) * Flexible scheduling of updates * Delivery of the actual updated files (packages) * Summaries of update results "Email notifications of available updates (errata)" I get for free, which is good marketing. The number of fixes they have posted in the past two months alone led me to conclude that the $60 would probably be worth it. Without paying the $60 I know what I would be getting if I did. Mandrakesoft offers the following: What are the Club priviledges? At the time of this writing (last updated in Nov. 2002), the following "Club privileges" are available: * Access to MandrakeClub.com -- a place where your voice will be heard, and that in many different languages! * The ability to download commercial software normally only available in retail packs. These applications include software drivers, commercial applications, freeware, and demo versions.* * Right to vote and propose new software in volunteers-run RPM voting system. Note: Club downloads work with urpmi/rpmdrake! :-)) * Special discounts for products and services on MandrakeStore. * Special MandrakeOnline offers for MandrakeClub members: no advertising, discounts, additional free account for gold (and higher) level members! * StarOffice 6.0 is available to Silver members and above. StarOffice download comes with complete OEM license, and entitles you to "one tech-support question to SUN per email or telephone". Standard members may elect to upgrade to Silver status. * Direct-trading program for MandrakeSoft stock, and access to real time trading information about MandrakeStock. * Better mirror list, exclusively for Club members. "Mirrors" script will not only help you to find servers with various types of RPMs for your Mandrake-Linux system, but also tell you how to set up Software manager (rpmdrake/urpmi) to use these mirrors. Noticeably missing are any mention of updates or bug fixes.

Here is a list: 1. With a Floppy and CD/DVD-ROM icon's on the KDE desktop, it is not too hard to figure out how to access these devices. Windows users in particular get thrown off though when trying to browse through the Linux directory to attach files to an email. If Floppy's and CD-ROM's could access from /home/user/device than /mnt/device this would be easier to understand. 2. Similary, they also find the need to mount and unmount devices confusing. 3. Flash, java and 3D drivers should be installed by default or available through the package manager, although I understand that pro versions do have there plugins in the CD's. 4. Different installers for different distro's will be a problem for the typical user. 5. Installers that don't create icons on the desktop or "Start" menu. 6. Too many configuration options. The ones least used ones should be hidden in a separate "Advanced" tab or button.

Am a flight sim fanatic myself...but honestly never heard of this one. Doubt it is any good.