No video: typical

[kbunt]

I tried to boot up Intrepid Ibex or whatever Ubuntu is calling it and I could not boot up. I burned a copy of the Ubuntu version (thus, Gnome) and it booted fine. Um....

So, it does suggest to me that the Ubuntu developers don't care about Kubuntu or KDE. The hardware is the same yet the one desktop version will boot up fine while the other one doesn't come close.

Why doesn't Ubuntu just drop Kubuntu and be done with it. Admit it, you don't care...

[3vi1]

Re: No video: typical

1) It's possible you just had a bad burn of the Kubuntu CD.

2) KDM is an entirely different program than GDM. Just because one works for you is not a guarantee that the other will.

3) Intrepid is still in the alpha releases. This means it's not finished and you should EXPECT problems.

4) KDE 4 is still very new. Expect problems.

5) You're very confused about who's responsible for the Kubuntu images.

[claydoh]

Re: No video: typical

hehe I think kbunt has calmed down a little since last Sunday

[Detonate]

Re: No video: typical

hehe I think kbunt has calmed down a little since last Sunday

I got so frustrated I installed xubuntu-desktop Sunday!

[3vi1]

Re: No video: typical

On a related note, when I got my power back yesterday, my system failed to start KDM. Probably due to problems with the scripts in the updates I had installed a day or so before the hurricane took everything down (I typically only reboot every week or two).

The system was complaining that it couldn't find the nvidia module during the Xorg startup. So, I just did:

sudo rm -rf /var/lib/dkms/nvidia/17*
sudo apt-get install --reinstall nvidia-177-kernel-source

This rebuilt the proper module and it came up fine after that.

[kbunt]

Re: No video: typical

So, when the video doesn't show in the boot up, it's due to KDE 4?

I tried to boot it up in another computer that had an older video card in it, Nvidia GeForce 4 series video card. But, Kubuntu 8.10 Intrepid Ibex Alpha 6 would not boot up. The screen went haywire and went a pretty pink colour. I had an Ubuntu 8.10 Intrepid Ibex Alpha 5 disc with me and we tried that. It DID boot up fine.

Both discs would boot up on my more modern computer with a GeForce 7950GT video card.

C'mon, Kubuntu, what is this?!?

I think my original post stands as I suspected. That's evidence right there UNLESS it's a KDE 4 problem.

[srelysian]

Re: No video: typical

So, when the video doesn't show in the boot up, it's due to KDE 4?

I tried to boot it up in another computer that had an older video card in it, Nvidia GeForce 4 series video card. But, Kubuntu 8.10 Intrepid Ibex Alpha 6 would not boot up. The screen went haywire and went a pretty pink colour. I had an Ubuntu 8.10 Intrepid Ibex Alpha 5 disc with me and we tried that. It DID boot up fine.

Both discs would boot up on my more modern computer with a GeForce 7950GT video card.

C'mon, Kubuntu, what is this?!?

I think my original post stands as I suspected. That's evidence right there UNLESS it's a KDE 4 problem.

LoL. First off, I am not sure where you come from, but I've never actually found a forum where throwing out insults left and right got you anything but ignored/mocked/banned. Secondly, there's a reason they call it "beta", it took me an hour to get 8.10 installed properly on my own laptop and I still have a few misc problems.

That aside, I've had similar problems and they had nothing to do with the distro. It usually had to do with nvidia and their refusal to release open-source accelerator drivers. What you could try doing, just to get it installed. Is when it is booting and comes to where your screen goes wonky, hit ctrl-alt-F1 to open another console. login from there, then go and edit your /etc/X11/xorg.conf file.

There should be a section like:

Section "Device"
Identifier "Device0"
VendorName ""
EndSection

Then you generally want to change this to look like:

Section "Device"
Identifier "Device0"
VendorName "Vesa"
Driver "vesa"
EndSection

then do /etc/init.d/kdm restart which should boot KDE into the crappy vesa driver which again usually works. This will allow you to install kubuntu and during the install will actually copy the xorg.conf file to the hard-drive allowing you to again, boot into KDE. Then you get yourself over to NVIDIA and get the newest drivers.

http://www.nvidia.com/object/unix.html

You probably want -> Linux IA32 Latest Version: 177.80 unless you are using the 64bit ver, than obviously grab the IA64 version. You can install it by running it from a pure shell, via:

ctrl-alt-f1

sudo /etc/init.d/kdm stop

run the install .. allow it to make the necessary changes to your xorg.conf file when it asks at the end. Then try rebooting. That's the best I can offer you.. like I stated earlier.. nvidia has been rather nazi-ish with their drivers and for that reason alot of distros no matter who makes them, will have random problems with nvidia cards. And next time, try asking for help rather than spitting insults.

[aged hippy]

Re: No video: typical

*** IMPORTANT NOTICE FOR DEVELOPMENT VERSIONS ***
« on: 04 July 2008, 15:48:58 »
As usual with Kubuntu early alpha testing releases, please do remember the very early stage of Intrepid's development means there will be massive system , kernel and library changes on a daily basis.

With this in mind, users must expect breakages and instability on a regular, almost daily basis. Usually, major problems such as video problems, etc are fixed rather quickly but it may take a day or longer for the fixes to be released.

it is a good idea to check here, or over at ubuntuforums' Intrepid forum regularly for information on how each days' updates are working before updating your system.

http://kubuntuforums.net/forums/inde...opic=3095914.0
Emphases original.

Beta:

In computer science

* A development stage of software wherein the software application is released to an enthusiastic public for large-scale testing and bug discovery

http://en.wikipedia.org/wiki/Beta

Beta: Public Test

Betaware is a nickname for software which has passed the alpha testing stage of development and has been released to a limited number of users for software testing before its official release. Beta testing allows the software to undergo usability testing with users who provide feedback, so that any malfunctions these users find in the software can be reported to the developers and fixed. Beta software can be unstable and could cause crashes or data loss.

A beta version is the first version released outside the organization or community that develops the software, for the purpose of evaluation or real-world black/grey-box testing. The process of delivering a beta version to the users is called beta release. Beta level software generally includes all features, but may also include known issues and bugs of a less serious variety.

The users of a beta version are called beta testers. They are usually customers or prospective customers of the organization that develops the software. They receive the software for free or for a reduced price, but act as free testers.

Beta versions test the supportability of the product, the go-to-market messaging (while recruiting Beta customers), the manufacturability of the product, and the overall channel flow or channel reach.

Beta version software is likely to be useful for internal demonstrations and previews to select customers, but unstable and not yet ready for release. Some developers refer to this stage as a preview, a prototype, a technical preview (TP) or as an early access. As the second major stage in the release lifecycle, following the alpha stage, it is named after the Greek letter beta, the second letter in the Greek alphabet.

Often this stage begins when the developers announce a feature freeze on the product, indicating that no more feature requirements will be accepted for this version of the product. Only software issues, or bugs and unimplemented features will be addressed.

Developers release either a closed beta or an open beta; closed beta versions are released to a select group of individuals for a user test, while open betas are to a larger community group, usually the general public. The testers report any bugs that they found and sometimes minor features they would like to see in the final version.

An example of a major public beta test was when Microsoft started releasing regular Windows Vista Community Technology Previews (CTP) to beta testers starting in January 2005. The first of these was build 5219. Subsequent CTPs introduced most of the planned features, as well as a number of changes to the user interface, based in large part on feedback from beta testers. Windows Vista was deemed feature complete with the release of build 5308 CTP, released on February 22, 2006, and much of the remainder of work between that build and the final release of the product focused on stability, performance, application and driver compatibility, and documentation.

When a beta becomes available to the general public it is often widely used by the technologically savvy and those familiar with previous versions as though it were the finished product. Usually developers of freeware or open-source betas release them to the general public while proprietary betas go to a relatively small group of testers. Recipients of highly proprietary betas may have to sign a non-disclosure agreement. A release is called feature complete when the product team agrees that functional requirements of the system are met and no new features will be put into the release, but significant software bugs may still exist. Companies with a formal software process will tend to enter the beta period with a list of known bugs that must be fixed to exit the beta period, and some companies make this list available to customers and testers.

As the Internet has allowed for rapid and inexpensive distribution of software, companies have begun to take a more flexible approach to use of the word "beta". [1] Netscape Communications was infamous for releasing alpha level versions of its Netscape web browser to the public and calling them “beta” releases. In February 2005, ZDNet published an article about the recent phenomenon of a beta version often staying for years and being used as if it were in production-level [2]. It noted that Gmail and Google News, for example, had been in beta for a long period of time and were not expected to drop the beta status despite the fact that they were widely used; however, Google News did leave beta in January 2006. This technique may also allow a developer to delay offering full support and/or responsibility for remaining issues. In the context of Web 2.0, people even talk of perpetual betas to signify that some software is meant to stay in beta state. Also, "beta" is sometimes used to indicate something more like a release candidate such as the Halo 3 public beta.

http://en.wikipedia.org/wiki/Development_stage#Beta

Intrepid Ibex ia a Beta version, not a Release Candidate. It says so, plainly,on the download page.
claydoh outlined the risks perfectly clearly.

I don't think there is anything more to say, is there? 8)

... although i freely admit to doing a bit of grumbling myself.

[smeghead67]

Re: No video: typical

I had to get a newer video card to make II run off the live cd.

Ted