Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep:
That looks like a shell script. The first thing I would do is look for a readme or instructions where you downloaded the file. To execute shell scripts you can use these.
Code:
./scriptname.sh
or
sh scriptname.sh
Again, look for some instructions first, there may be more to this package than just running the script.
Good luck. ;-)
I am sorry for the late response but the pc apears to be more or less dead right now (from a hardware point of view). When it is repaired I will got back to you on this.
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep:
Quote:
Originally Posted by V!NCENT
I am sorry for the late response but the pc apears to be more or less dead right now (from a hardware point of view). When it is repaired I will got back to you on this.
Does it power up? Any other symptoms or error messages?
Good luck. ;-)
Does it power up? Any other symptoms or error messages?
Good luck. ;-)
We changed a lot of hardware. We slammed in a ATI 9600XT card to see what performance we could get with the new amazing 8.41 ATI drivers instead of the GeForce 4000 MX (GeForce 2 but hello marketing dep.). Changed to a 40GB Western Digital hdd. Putt in a Creative SB 5.1 Live!
We found out the SounbBlaster was dead. We removed it from the box and it booted the BIOS. Anything beyond the bios was pretty impossible so I changed the BIOS to safe defaults and we got... nothing. Probably nothing on the hdd? Wierd... So we slammed in the Ubuntu disk and it froze at the new ini screen.
Okay, maybe the latest Fedora then? "Block error" times infinity. So we removed the hdd and still it gives us block errors. "sr0" seems to refuse to work. What is sr?
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep:
Quote:
Changed to a 40GB Western Digital hdd.
Did you go through the bios detect to ensure the new drive had been recognized?
Quote:
"sr0" seems to refuse to work. What is sr?
Device srX is your cd/dvd-rom. The block error could be caused by the bios not recognizing the drives properly. It could also be a bad disk.
With all of that new hardware, I'd suggest going through the bios very carefully and ensuring all settings are correct, and all drives, devices are recognized.
Good luck. ;-)
Did you go through the bios detect to ensure the new drive had been recognized?
Not yet. It is all safe defaults. But at the post screen the BIOS does detect the names and under which configuration (primary, master, etc.) they reside.
Quote:
Device srX is your cd/dvd-rom. The block error could be caused by the bios not recognizing the drives properly. It could also be a bad disk.
I don't recal the disk brand but it had scored awesome tests in a few pc mags. Fedora could be a bad download but we had burned the Ubuntu disc with the same cd-writer before we changed hardware and it did just fine back then...
We had a lot of trouble with IDE cabel configuration. The cabels are like bended a thousand times and one of them is a very old cable that doesn't have as much wires as newer ones. For that reason we plugged the hdd to the cabel with more wires as primary master and the cd-drive to the cabel with fewer wires under secondary master (jumpers are set correctly to master).
Unfortunately the box is at a friend of mine and he has plans for the weekend so I have to wait at least for monday to work on the pc.
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep:
Old shoddy cables can cause the same types of problems, however, if everything is getting recognized in bios that suggests the cables are fine.
Whenever I make hardware changes, especially to the extent that you have, I (usually) go through all the components on the mobo and double check that everything is seated correctly and securely even things I haven't touched. I also walk through all of my bios settings to check that everything is good there.
Quote:
Unfortunately the box is at a friend of mine and he has plans for the weekend so I have to wait at least for monday to work on the pc.
I plugged in a new IDE cable for the cdrom and I still keep getting sr0 errors :S.
Update: Ubuntu however is now bootable. In Fedora I keep getting something like "Buffer I/O error block: xxxxxxx". The Fedora disk is probably just corrupted. When I select "Check disk integrity for errors" or something like that it boots the Linux kernel and right after that I get the block errors so the disk utility doesn't even have a chance to start.
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep:
Quote:
Update: Ubuntu however is now bootable. In Fedora I keep getting something like "Buffer I/O error block: xxxxxxx". The Fedora disk is probably just corrupted. When I select "Check disk integrity for errors" or something like that it boots the Linux kernel and right after that I get the block errors so the disk utility doesn't even have a chance to start.
If the Ubuntu disk is booting ok, then you've probably just got a bad fedora disk or image.
Good luck. ;-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.