Forum Home
Press F1
Thread ID: 115055	2010-12-30 17:32:00	HD failure	sarel (2490)	Press F1

Post ID	Timestamp	Content	User
1165863	2011-01-21 22:37:00	I have to agree, unfortunately. Ubuntu is a nice OS overall but if you do get some weird problem it's often quite hard to find anyone to help you (my own experience). On most computers I have tried it, Ubuntu works just fine. On a few I have had weird problems and either gave up or used a different distribution (can be surprising how much difference that can make, actually) A big problem I find with Ubuntu is that as it's targeted to people who don't know much about Linux (like me!) it tries to do a lot of things automatically. That works great when it works, but if it doesn't work, you get really screwed, because then it's even harder to try to figure it out manually (that is the impression I get anyway) The other thing is that Linux can be a lot less forgiving than Windows for mis-configured hardware or badly written BIOSes etc. Whether you see this is a good thing or not depends on your point of view.Really hit the nail on the head there - x2 :thumbs:. Only exception is your last paragraph - Linux is generally more tolerant than Windows of funky hardware, but Linux tends to be where you notice the problems, because the hardware is generally built with Windows in mind from the start. As such, Windows has no need to be tolerant!	Erayd (23)
1165864	2011-01-21 23:02:00	Thanks for you input Erayd - I'm not going to to "quote" everything what you have written, and many points are valid - esp the one regarding the thread title. As for the long thread, most people would have a look, especially if its a long thread - normally a lengthy thread means its one hell of a fight :eek: Some real big problem - or heaven forbid, another Association game ( shudder) :D The one I will quote Haha, nice idea, but not quite. This looks more like a configuration error, which noting it's Ubuntu doesn't surprise me at all - Ubuntu has a very bad track record for shipping bugs, and introducing them with updates. Recent versions of Linux should have no trouble supporting the hardware on that board. At least its not just MS that ship out OS's / programs with bugs :lol: Maybe to help out Sarel,since its his thread -- SAREL -- make a new Post - head it up as Erayd suggested. "Ubuntu - no graphics at boot" Brief description, then link it to this thread. Linked to Page 7 post 61. That way others can see whats been tried /suggested. If you're not to sure ask and someone will make it for you. Maybe then the Linux experts will answer -- no excuses this time Or is it simply in the too hard basket ? I dont mean any disrespect - Erayd - any suggestions / ideas as to how to fix the problem as nothing really in the reply suggested anything only the cause?	wainuitech (129)
1165865	2011-01-21 23:08:00	Logically, if the drive is accessable by GRUB at boot time, then the SATA controller / drive connection *cannot* be the problem. I know this is probably a terribly bad comparison but if you were to install Windows XP on a SATA drive in IDE mode, then switch to AHCI mode, Windows would attempt to load but BSOD halfway through. Is it possible that a similar problem could happen with Linux related to the JMicron controller? (eg: you can install, load GRUB, but not actually boot) Note: I don't think that is the problem here, you'd get an error message rather than a no signal problem At the moment all I can think of is that BIOS update with new VGA ROM. I would put that as first on the list of things to try next as it seems the only thing related. Also, HP make hideous BIOS sometimes. Really hit the nail on the head there - x2 :thumbs:. Only exception is your last paragraph - Linux is generally more tolerant than Windows of funky hardware, but Linux tends to be where you notice the problems, because the hardware is generally built with Windows in mind from the start. As such, Windows has no need to be tolerant! True, I don't really have much experience with that. I only take it from what I read (people saying that you could configure both drives on an IDE cable as master, they'd work in Windows but Linux would complain) - in that case I would consider it a good thing - the user might learn something on how to properly configure his drives. The only real thing I had was when I tried to boot a CD on a certain computer and it came back with an error saying "Extremely broken BIOS detected" and wouldn't load. I think I just tried a different loader (Syslinux instead of ISOlinux etc) and it worked OK then.	Agent_24 (57)
1165866	2011-01-22 01:53:00	As for the long thread, most people would have a look, especially if its a long thread - normally a lengthy thread means its one hell of a fight :eek: Some real big problem - or heaven forbid, another Association game ( shudder) :DThat's a great point - I hadn't considered that, even though it's the very reason I decided to check out the thread again and see what was going on :rolleyes: . Long threads do indeed make people curious . Maybe then the Linux experts will answer -- no excuses this time Or is it simply in the too hard basket ?Nah, no excuses - if the thread is headed up properly, and is on-topic, there's no reason why the Linux people wouldn't be reading it . I dont mean any disrespect - Erayd - any suggestions / ideas as to how to fix the problem as nothing really in the reply suggested anything only the cause?No disrespect taken, it's a very reasonable question . I do have a few ideas, but didn't want to state them without more information (hence my question about the splash screen), as I figured I may simply confuse people by giving multiple solutions, some of which won't be applicable . Possible fixes: If the output vanishes before the splash screen and the kernel log isn't shown, then noting this is nvidia hardware, there are a few kernel options that affect the framebuffer in this way . Some of these can be fixed by blacklisting modules, and some require a kernel recompile, or installation of an alternative kernel with a valid config for the platform . Before trying this option, additional diagnostics should be performed (e . g . booting with a higher loglevel, posting kernel config etc), as it's not a trivial fix . If this is in fact the problem, it will be caused by Ubuntu's kernel configuration, and means the Ubuntu packagers either didn't think through the implications of their decisions, or didn't do proper testing . If the output vanishes after the splash screen, or the kernel log is displayed, then it'll almost certainly be a problem with X's configuration . Under Ubuntu, most X configuration is done automatically by X . When the autoconfig gets it wrong though, it can cause this kind of thing . The first step I'd recommend is to ensure the correct driver is available . If it is, then the correct video driver isn't being loaded, and will need to be forced . The approach to this depends on the type of card being used, so we'd really need more info before giving the necessary steps here . If forcing the driver fails, then I'd manually specify a full config (/etc/X11/xorg . conf) - this will almost always result in a working system, although it does sometimes require a bit of tweaking to get it behaving properly . I know this is probably a terribly bad comparison but if you were to install Windows XP on a SATA drive in IDE mode, then switch to AHCI mode, Windows would attempt to load but BSOD halfway through . This can't happen under Linux due to the way drivers are handled . Provided the relevant support is present in the kernel (and the required kernel modules are available if support isn't compiled in directly), then Linux will quite happily switch access methods to get at the drive, and will boot as if nothing had changed . Similar symptoms can occur (but for a different reason) if AHCI is missing from the kernel - and the kernels for every major distro have included AHCI support for many years . Anyone missing that almost certainly configured & compiled their own kernel, and should therefore be able to fix it themselves (or if they can't, they shouldn't have been messing with it in the first place, and should put their distro's standard kernel back) . This issue will generally manifest as an error message in the kernel log (and is usually displayed on screen too) that complains about the root filesystem being missing . This obviously isn't the case here, Sarel hasn't been messing around with recompiling his kernel, and Ubuntu definitely supports AHCI just fine . Is it possible that a similar problem could happen with Linux related to the JMicron controller?No . Due to the way Linux handles drivers, the controller will either work or it won't . The same access layer that is used for 'general' filesystem access is also used for booting, and if the controller is supported by the kernel, it can be booted from . (eg: you can install, load GRUB, but not actually boot)There are *many* issues that can cause GRUB to load, but prevent the system fropm booting properly - most (but not all) of which are related to the way GRUB is configured . Sometimes the initramfs and / or kernel arguments are also at fault .	Erayd (23)
1165867	2011-01-22 08:05:00	SAREl -- Try this (ubuntuforums.org) Been looking for a possible fix. When you hold down the shift key,and get to the menu that you had before , ( Various options-memtest etc) thats when you press E use the arrow keys and scroll down till you get to the line Linux /boot ------ Keep tapping the right arrow key, and it will move across and down to the next line, when it reaches the end of that line, hit the space bar type in the wording nomodeset then press ctrl X it will reboot ------hopefully you will have graphics.	wainuitech (129)
1165868	2011-01-22 08:18:00	Jeez, lots of questions. I am in awe of all you guys. Talking stuff I know b*ggerall about. WT - no booting with the new ISO. I changed the SATA's around - no change Agent/Erayd : the HD boots up and you get 3 choices at the bottom - Boot, setup or recovery and then it disappears and with Win7, the Win splash screen appears. With Ubuntu, nothing. Sometimes there will be a star indicating it's reading something, mostly not. Just the signal loss message going on and on. Makes me wonder if I shouldn't try another Linux variant just to see - Erayd which one do you suggest? Ahhhh WT I just wanted to try Linux - I did not intend to cause a fight between very good guys that I respect very much. I would rather just stop with this thread and my silly idea of trying Linux than cause any more harm. At the end of the day the new HD can be another external HD. Agent, you really want me to b*gger around with the Bios - with my level of relative stupidity? I run V3.7 Bios (a Compaq splash screen) and I do not have any Windows on the HD right now. I see the version in your link is 3.10. In any case, friends, romans and countrymen, I will be away for a bit for the next week or so and will not be able to get near any electronic device. If everything goes well and to plan I will talk again in a fortnight or so. If it doesn't go to plan, it will probably be a bit longer. sarel	sarel (2490)
1165869	2011-02-25 11:05:00	Did you get anywhere with this or still the same problem?	Agent_24 (57)
1165870	2011-02-25 11:47:00	This morning I got the message that a HD failure is imminent :crying and I wonder if that has been the problem with this piece of cr*p all the time. Making clicking noises as well. My question : how do I transfer my OEM XP from this HD to a new one, or is it better to perhaps get another cheapie tower? sarel Pull out your backup that you made and kept updated weekly and restore from that. Whoops!	veldthui (15543)
1165871	2011-02-25 23:12:00	Agent/Erayd : the HD boots up and you get 3 choices at the bottom - Boot, setup or recovery and then it disappears and with Win7, the Win splash screen appears. With Ubuntu, nothing. Sometimes there will be a star indicating it's reading something, mostly not. Just the signal loss message going on and on.Did you try the nomodeset boot parameter as suggested above? This will turn KMS off, and may result in usable video. Makes me wonder if I shouldn't try another Linux variant just to see - Erayd which one do you suggest?Depends what you want it for, and how steep a learning curve you're prepared to handle. Can you explain your needs / wants in a bit more depth? Ahhhh WT I just wanted to try Linux - I did not intend to cause a fight between very good guys that I respect very much. I would rather just stop with this thread and my silly idea of trying Linux than cause any more harm. At the end of the day the new HD can be another external HD.I don't think anyone was fighting ;). Agent, you really want me to b*gger around with the Bios - with my level of relative stupidity?Almost certainly not required at this point; leave it alone.	Erayd (23)
1 2 3 4 5 6 7 8 9 10 11