Carolina: Vanguard Edition Release 2 December 2014

[musher0]

Yoo-hoo, guys!

I'm still here waiting for a solution or at least an explanation to my
Carolina Vanguard boot problem!

Thanks in advance.

musher0

[ally]

hey battleshooter

finally got around to taking vanguard for a spin, looks good, quick Q, how would I get chrome running?

[Marv]

i915.modeset=0 as a kernel parameter does get vlina running on the Bay Trail box with the correct.. and visible resolution, albeit with the vesa driver, software rasterizing and a glacial 25 FPS glxgears (glxgears on the same box with the intel driver etc in LxPupTahr is 2915 FPS). This should make troubleshooting a bit easier now.

[Geoffrey]

fix for Skype is spitting something out about QT incompatibility -

Code: Select all

# skype
Fatal: Cannot mix incompatible Qt library (version 0x40800) with this library (version 0x40802)
/usr/bin/skype: line 6: 26375 Aborted                 /usr/share/skype/skype
# 

It appears you are using a skype package other than the Carolina one, which has a different version of QT included.

There is no need to install skype as vlina-1.3 has skype included and only the changes I mentioned need to be done,
even though it works without the change it's just to remove unneeded elements.

[Geoffrey]

hey battleshooter

finally got around to taking vanguard for a spin, looks good, quick Q, how would I get chrome running?

I have kost@s's chromium package installed and working chromium-37.0.2062.94.pet

[ally]

thanks

[Minnesota]

Thank you , Master PDF Editor, fix in, and running.

Had to use Vesa to make video card run, but you know that.

Strange happenings when using a usb stick, removing it then putting it back to same usb port after transferring data to a different computer. Would not recognize the reinsertion, and yes I had ejected the stick before removal.


Needs more testing from others to verify.

Thanks again for a very nice looking and fast Puppy. NO problem on size!

PDF edit is an interesting program. Bringing modified saved file to a different Firefox gave some strange results. Either my learning curve or?

[battleshooter]

Everyone banding together to bring me the answers to my questions ... brings tears to my eyes But seriously, thanks guys

Carolina 1.3 works on the ivybridge computer

It's using the vesa driver on bootup,

i915.modeset=0 as a kernel parameter does get vlina running on the Bay Trail box with the correct.. and visible resolution, albeit with the vesa driver, software rasterizing and a glacial 25 FPS glxgears (glxgears on the same box with the intel driver etc in LxPupTahr is 2915 FPS)

So looks like we have Vesa going, but optimally we want the actual Intel driver going from Marv's dismal comparison. From what I read the Intel drivers require modeset=1, but it looks like to get Vesa going modeset needs to be off?

Tried, but in tar.gz format the answers plus four relevant screencaps are 335K and this forum only allows 256K upload attachments. PM me your email addy and I'll send it that way.

Done.

Yoo-hoo, guys!

I'm still here waiting for a solution or at least an explanation to my
Carolina Vanguard boot problem!

Whoa, give me a chance to wake up Way too early in the morning for "Yoo-hoo" greetings. I'd never greet someone like that till the afternoon

You did get me "sold" on your product .

Cool, let's hope I didn't sell you a lemon

However, your new Carolina girl leaves me out in the cold after (giving
me the) boot-up, exactly at

Code: Select all

root login on "tty1"

I mean: the boot process goes well and then the computer freezes badly
at that point.

I don't know that I've ever seen that before. Geoff? Help? I'll look it up, but might want to check the md5sum, and maybe retransfer adrv, zdrv, initrd.gz, etc again. I've had weird errors just poor transfers before so just suggesting.

finally got around to taking vanguard for a spin, looks good, quick Q, how would I get chrome running?

Yeah, I know that's a popular browser, need to get on to putting a link on the top posts. Also need to get on to adding credits to Geoff and the Carolina team. That's been bugging me for days now Such a slacker

[battleshooter]

Strange happenings when using a usb stick, removing it then putting it back to same usb port after transferring data to a different computer. Would not recognize the reinsertion, and yes I had ejected the stick before removal.

Needs more testing from others to verify.

Strange, haven't had that issue before. MD5sum check out?

PDF edit is an interesting program. Bringing modified saved file to a different Firefox gave some strange results. Either my learning curve or?

More of Geoff's department than mine.

[Geoffrey]

Image list problem as reported by Terry H on the Carolina thread.

Problem when attempting to set Desktop Wallpaper to 'Image List'.

I'm not sure what is supposed to happen with this option. The Radio Button is only highlighted without the button actually being selected. The desktop seems to freeze for 30 seconds or so, followed by choppy cursor movement. Eventually the window closes and correct cursor function returns.

I just noticed this using Carolina Vanguard, so checked on Carolina 1.3 and the same issue occurred. I am using Dell D620 laptop Core Duo 2.16 GHz, with Intel graphics.

The 'None' option works correctly.

Yeah, weird, fixed if you delete /root/.config/xfce4/desktop/backdrop.list then the list works and you can create a new list,
that's strange, seems to be a miss match of image files or something Phew.. easy peasy.

[Marv]

@battleshooter

As long as we're drowning you

Code: Select all

                  Scribbled notes Bay Trail mobo summary (has intel HD 4000 video, j1900 processor)

Carolina 1.2 with 3.14.20, 3.15.4, 3.17.x, and vlina
	Xorg version:						1.11.0
	Intel driver version:				2.15.0 (compiled for 1.11.0)
	Mesa version:						7.10.3 
	Maximum driver (i915.modeset=0):	'vesa'
	glxgears (vblank_mode=0):			25 FPS
	
X-slacko 2.3 non-PAE with 3.14.20 kernel
	Xorg version:						1.12.4
	Intel driver version:				2.19.0  (compiled for 1.12.4)
	Mesa version:						8.04
	maximum driver (set in xorg.conf):	'modesetting'
	glxgears (vblank_mode=0)			412 FPS 
	
LxPupTahr 14.10.1 non-PAE with std 3.14.20 kernel
	Xorg version:						1.15.1
	Intel driver version:				2.99.910  (compiled for 1.15.1)
	Mesa version:						10.1.3
	maximum driver:						'intel'
	glxgears (vblank_mode=0)			2915 FPS
	
For comparison, on the 1.6 GHz Pentium M 855GM laptop, vlina uses the 'intel' driver and produces a respectable 590 FPS in glxgears.

From my fiddling with X-slacko, where I had matched kernels to work with, I believe for full support of the newer bridges and intel HD videos both the newest of the above intel drivers , Mesa, and a matched set of Xorg stuff is probably required. Ugh.

[Moat]

It appears you are using a skype package other than the Carolina one, which has a different version of QT included.

Hi Geoffrey -

As I never installed Skype (no need/interest/use), I'll hazard a guess that this might actually be a result of my (imprudent) re-use of my old savefile (created originally on 1.2).

Suppose I'd better keep quiet until I delete this old savefile and re-build from scratch!

Bob

[battleshooter]

Image list problem as reported by Terry H on the Carolina thread.

Haha. I answered this on the Carolina thread, didn't know you posted the solution here

As long as we're drowning you

Glug glug glug

I asked for it though didn't I?

I believe for full support of the newer bridges and intel HD videos both the newest of the above intel drivers , Mesa, and a matched set of Xorg stuff is probably required. Ugh.

I'm still not utterly convinced a newer Xorg is needed, but I guess I don't mind reopening that can of worms.

If you don't mind testing an utterly buggy Xorg, I suppose I could even throw a link up for you. The main issue I have with it is actually not graphically related but rather the input drivers don't seem right. They work, but they should really be using the new drivers (evdev) not the old drivers (kbd and mouse). Hmm. I might try nicking the Tahr or another modern Puppy's XorgWizard and see if they will allow evdev. Hmm.

[Marv]

I'm still not utterly convinced a newer Xorg is needed, but I guess I don't mind reopening that can of worms.

If you don't mind testing an utterly buggy Xorg, I suppose I could even throw a link up for you. The main issue I have with it is actually not graphically related but rather the input drivers don't seem right. They work, but they should really be using the new drivers (evdev) not the old drivers (kbd and mouse). Hmm. I might try nicking the Tahr or another modern Puppy's XorgWizard and see if they will allow evdev. Hmm.

Can't be much buggier than the one I cobbled together for X-slacko 2.3 and the Bay trail. I am pretty sure I did use the wizard from Tahr. It did load and boot to X but the graphics performance was poorer than the stock X-slacko running with the modesetting driver and I veered off course. Never checked the mouse driver etc.

Edit: vlina just flies on the 1.6GHz Pentium M laptop. I've been using it steadily and it is as quick and light as it gets. A little more panel fiddling and CPU use at idle is down to 2%. Standard governor setup with ondemand/80% and no fan talk at all.

[battleshooter]

Can't be much buggier than the one I cobbled together for X-slacko 2.3 and the Bay trail. I am pretty sure I did use the wizard from Tahr. It did load and boot to X but the graphics performance was poorer than the stock X-slacko running with the modesetting driver and I veered off course. Never checked the mouse driver etc.

I'll take that as a yes then

Just need to test it before upload, I've remade the package so many times I can't remember if the last was a working build or not!

[battleshooter]

Tahr's Xorgwizard didn't appear to make a difference in regards to setting the correct input drivers. Must be something else then.

Here's the Xorg pet.

md5sum:dc52d915cb6d00b91566807014bf5a06

Everything is mushed into it. Very large. Very work in progress, use at your own risk, rah-de-rah.

128 MB because everything is in there. Non stripped too I think should have done that before uploading. Oops. Oh well. Pretend I didn't for bug testing reasons

Roughly this pet is a conglomerate of the following packages:

• elfutils-0.160.pet
  libXdmcp-1.1.1.pet
  xcb-proto-1.11.pet
  llvm-3.5.0.src.pet
  xkeyboard-config-2.13.pet
  libepoxy-1.2.pet
  Mesa-10.3.2.pet
  xorg_app.pet
  libevdev-1.3.1.pet
  xorg_drivers.pet
  libffi-3.2.1.pet
  xorg_libraries.pet
  libvdpau-0.8.pet
  util-macros-1.19.0.pet
  xorg_proto.pet
  libXau-1.0.8.pet
  xbitmaps-1.1.1.pet
  xorg-server-1.16.1.pet
  libxcb-1.11.pet
  xcb.pet

Oh darn it. I just remembered I didn't compile the Intel Xorg drivers. I'll be off to compile those and put them here as soon as this is done uploading.

Edit:
xf86-video-intel-2.99.916.pet
pixman-0.32.6.pet (Is needed)
libva-1.4.1.pet
libva-intel-driver-1.4.1.pet

[James C]

Just to add to the display woes.......

On the box with an old Nvidia GT210 card,boots to an incorrect 1600x1200 resolution using "vesa". Any attempt to use Xorgwizard,using "vesa" or the desired "nouveau", results in X refusing to start.

Previous version with k-3.17.0 works fine.

Downloading the above pet to see if it makes any difference.

Code: Select all

# report-video
VIDEO REPORT: tahrpup, version 6.0

Chip description:
VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)

Requested by /etc/X11/xorg.conf:
  Resolution (widthxheight, in pixels): 1024x768x16
  Depth (bits, or planes):              24
  Modules requested to be loaded:       dbe 

Probing Xorg startup log file (/var/log/Xorg.0.log):
  Driver loaded (and currently in use): nvidia
  Loaded modules: dbe dri2 extmod fb glx kbd mouse ramdac wfb

Actual rendering on monitor:
  Resolution:  1440x900 pixels (411x263 millimeters)
  Depth:       24 planes

...the above also recorded in /tmp/report-video
#

[James C]

For informational purposes.....

Code: Select all

# report-video
Carolina-k3.17, version 1.2 on Tue 16 Dec 2014

Chip description:
 0.0 VGA compatible controller
 nVidia Corporation GT218 [GeForce 210] (rev a2)  
oem: NVIDIA
product: GT218 Board - 08720002 Chip Rev
 
X Server: Xorg
Driver used: nouveau

X.Org version: 1.11.0
  dimensions:    1440x900 pixels (380x238 millimeters)
  depth of root window:    16 planes 

   ...the above also recorded in /tmp/root/ as report-video,
and archived with xorg.conf and Xorg.0.log as report-video-full.gz
# 

[Billtoo]

Tahr's Xorgwizard didn't appear to make a difference in regards to setting the correct input drivers. Must be something else then.

Here's the Xorg pet.

md5sum:dc52d915cb6d00b91566807014bf5a06

Everything is mushed into it. Very large. Very work in progress, use at your own risk, rah-de-rah.

128 MB because everything is in there. Non stripped too I think should have done that before uploading. Oops. Oh well. Pretend I didn't for bug testing reasons

Roughly this pet is a conglomerate of the following packages:

• elfutils-0.160.pet
  libXdmcp-1.1.1.pet
  xcb-proto-1.11.pet
  llvm-3.5.0.src.pet
  xkeyboard-config-2.13.pet
  libepoxy-1.2.pet
  Mesa-10.3.2.pet
  xorg_app.pet
  libevdev-1.3.1.pet
  xorg_drivers.pet
  libffi-3.2.1.pet
  xorg_libraries.pet
  libvdpau-0.8.pet
  util-macros-1.19.0.pet
  xorg_proto.pet
  libXau-1.0.8.pet
  xbitmaps-1.1.1.pet
  xorg-server-1.16.1.pet
  libxcb-1.11.pet
  xcb.pet

Oh darn it. I just remembered I didn't compile the Intel Xorg drivers. I'll be off to compile those and put them here as soon as this is done uploading.

Edit:
xf86-video-intel-2.99.916.pet
pixman-0.32.6.pet (Is needed)

I booted up my Carolina Vanguard usb install on the Acer pc which has the
intel ironlake, downloaded the and installed the 2 pets then shutdown.

Plugged the drive into the ivybridge pc and it started to boot, just at
the point where it goes to the desktop the pc locked up, did a hard
reset.
Booted a second time with "puppy pfix=nox", at the prompt ran xorgwizard
and chose the intel driver, did xwin to get to the desktop, the pc
locked up again.
I'm pretty sure the larger pet had installed okay, I waited long
enough I think, so no luck with the new pets here.

EDIT: I just noticed there was the 3rd pet to install, pixman..., I downloaded that and couldn,t install it with "puppy pfix=nox" petget and booting the flash drive on the ironlake pc locks it up too.
Damn

[James C]

What I get on boot is all I can get.....any attempt to use xorgwizard results in X refusing to start completely.

Just for fun,tried the above main pet, froze up my computer too.

Code: Select all

# report-video
Vanguard-Carolina, version 1.3 on Tue 16 Dec 2014

Chip description:
 0.0 VGA compatible controller
 nVidia Corporation GT218 [GeForce 210] (rev a2)  
oem: NVIDIA
product: GT218 Board - 08720002 Chip Rev
 
X Server: Xorg
Driver used: # vesa

X.Org version: 1.11.0
  dimensions:    1600x1200 pixels (423x318 millimeters)
  depth of root window:    24 planes 

   ...the above also recorded in /tmp/root/ as report-video,
and archived with xorg.conf and Xorg.0.log as report-video-full.gz
#