Puppy Linux Discussion Forum

[alec78]

Hi all,
Further to my post above, to see if I had made an error I did a pfix=ram boot from the CD. Again at the video set up screen I hit the choose button and then OK. When the desktop came up I ran report-video. It was the same as previous i.e. showing the vesa driver.
I then did my normal boot from the CD to a save file on an USB dongle. I intended to follow the instructions given by BarryK in the Quirky 013 Bugs Feedback thread on the 31/3/10.
When I looked in /usr/X11R7/lib/xorg/modules/drivers there was no intel driver, there were i810 and vesa drivers. I deleted the vesa driver, exited to the promp and ran xorgwizard. Hitting the chose button brought up a box saying something like not implemented yet, so I hit the probe button, I then had to manually select the resolution and depth. The installation then went to completion with a black screen. I killed that with the power button and rebooted. The desktop came up and report-video showed the vesa driver.
It seems the original xorg wizard is deleting the intel driver but not selecting the i810 driver and deferring to the vesa driver.
Cheers

[Fishy]

Hi Barry, tried your new Wary puplet and Xconfig worked properly unlike quirky.

Cheers

ATI HD 3300 integrated graphics, ASUS M4A78T-E MB
AMD Phenom 2 Dual Core

[rjbrewer]

Wary 019 will boot to desktop using xorg with my intel855gm
graphics.........no black screen at laptop native (1280x800)
resolution.

[Billtoo]

I get a black screen no matter which I choose, probe,choose,or vesa.

At one point it said it was just going to use the 810 driver, my pc has the Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02) so a black screen was what I got.

I posted the above from quirky 018 which works fine and I've rebooted to puppy 3.01 and it works fine too (although it takes about 10 minutes to boot up 3.01).

The pc is a "Linux puppypc 2.6.21.7 #1 Sun Sep 9 02:29:54 GMT-8 2007 i686 Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz GenuineIntel GNU/Linux"

[JustGreg]

Thanks for site rjbrewer. I did try the location:
mms://wtju-r.eservices.virginia.edu/WTJU-test
It did work in both mplayer and pupradio. However, the locations for the Gulch receiver and pupradio CFGP, still do not. It is clear that Sea Monkey, latest version has a problem. I am still a bit confused why Puppy 4.3.1 Gxine does not have a problem, but, mplayer of Quirky 018 does have one. I am waiting until the next version of Quirky.

[BarryK]

Might as well use this thread also for feedback on Wary 019, as announced here:

http://bkhome.org/blog/?viewDetailed=01504

I'm very interested to know if testers having trouble with video in Quirky 018, find Wary 019 fixes it (or is worse).

[BarryK]

Wary 019:

Intel video has problems. I will have to rollback the Intel video driver for next Wary:

http://bkhome.org/blog/?viewDetailed=01506

[rjbrewer]

[ecube]

Everything works fine. The only (cosmetic) problem is a open box error message (a buglet residue?)

To keep track of my IP-address, I added a file

[Sit Heel Speak]

(deleted by poster)
(always rtfm first..).

[Sit Heel Speak]

oops

[tlchost]

[tlchost]

Installation of Pidgin-2.6.5_pup431.pet reports

error while loading shared libraries: libXss.o.1: cannot open shared object file" No such file or directory.

Pet installed correctly in 431 and 432

[tlchost]

In 19 audio feeds from shoutcast.net will not play. Player loads file partially and then reports stopped.

Occurs with SeaMonkey and Firefox.

[BarryK]

Wary 019:

I have rolled-back Xorg Intel and Ati PET packages, if anyone wants to try them. This is for Wary 019 only:

http://bkhome.org/blog/?viewDetailed=01509