Unnamed pupplet (puppy411 kernel-2.6.27.5 Xorg-7.4 LXDE)
- battleshooter
- Posts: 1378
- Joined: Wed 14 May 2008, 05:10
- Location: Australia
hm, you can reboot again.
X should recognize that it did not exit properly, and drop you to console.
There you could try again, or type:
rm -f /usr/X11R7/lib/xorg/modules/extensions/libglx.so
xwin
This would delete it.
I actually have no idea, why it fails.
Just to be certain, do you have this folder?
/usr/X11R7/lib/dri/
It should contain:
i810_dri.so
i915_dri.so
i965_dri.so
When X started, type:
lsmod
Look, if that shows a module loaded, like "i915".
For now, I must say goodnight, but will try to help you again tomorrow evening.
Mark
X should recognize that it did not exit properly, and drop you to console.
There you could try again, or type:
rm -f /usr/X11R7/lib/xorg/modules/extensions/libglx.so
xwin
This would delete it.
I actually have no idea, why it fails.
Just to be certain, do you have this folder?
/usr/X11R7/lib/dri/
It should contain:
i810_dri.so
i915_dri.so
i965_dri.so
When X started, type:
lsmod
Look, if that shows a module loaded, like "i915".
For now, I must say goodnight, but will try to help you again tomorrow evening.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
- battleshooter
- Posts: 1378
- Joined: Wed 14 May 2008, 05:10
- Location: Australia
- battleshooter
- Posts: 1378
- Joined: Wed 14 May 2008, 05:10
- Location: Australia
Oddly enough X didn't seem aware it didn't exit correctly. Skipping the console it led me directly to the black screen.
Typing lsmod, I couldn't seem to find i915.
I attached a screen shot of the modules loaded. I can't seem to copy and paste urxvt.
Battleshooter
Typing lsmod, I couldn't seem to find i915.
I attached a screen shot of the modules loaded. I can't seem to copy and paste urxvt.
Battleshooter
- Attachments
-
- lsmod.jpg
- (114.98 KiB) Downloaded 1161 times
what really makes me wonder is, that libglx.so from the original xorg gives a black screen.
I had a similar issue yesterday in Puppy 4.12, creating Ati drivers.
The problem was, that there was missing a symlink
/usr/X11R7/lib/dri
In this puplet here, it is a folder.
Maybe you miss
/usr/X11R7/lib/modules/dri
If that does not exist, type:
------------
Else, I could imagine a conflict with one of the files installed from the nvidia sfs.
I would try to boot from CD, create a savefile.
Then add in /mnt/home these files:
Xorg-7.4-video-input-apps-i686-wow_411.sfs
Mesa-7.2-i686-wow_411.sfs
Then add them in the bootmanager and reboot, so that they get mounted.
If it works, you know, that something is wrong with your full installation.
---------------------
One other idea:
When X gives a black screen with the original libglx.so in your full installation, power off the computer.
Boot from CD, and look, if a /var/log/xorg.0.log was created on your harddrive.
Attach it here, also /var/log/messages and /tmp/xerrs.txt.
All from the harddrive, not from the current CD system.
Maybe they include a hint.
Mark
I had a similar issue yesterday in Puppy 4.12, creating Ati drivers.
The problem was, that there was missing a symlink
/usr/X11R7/lib/dri
In this puplet here, it is a folder.
Maybe you miss
/usr/X11R7/lib/modules/dri
If that does not exist, type:
Code: Select all
ln -s /usr/X11R7/lib/dri /usr/X11R7/lib/modules/dri
Else, I could imagine a conflict with one of the files installed from the nvidia sfs.
I would try to boot from CD, create a savefile.
Then add in /mnt/home these files:
Xorg-7.4-video-input-apps-i686-wow_411.sfs
Mesa-7.2-i686-wow_411.sfs
Then add them in the bootmanager and reboot, so that they get mounted.
If it works, you know, that something is wrong with your full installation.
---------------------
One other idea:
When X gives a black screen with the original libglx.so in your full installation, power off the computer.
Boot from CD, and look, if a /var/log/xorg.0.log was created on your harddrive.
Attach it here, also /var/log/messages and /tmp/xerrs.txt.
All from the harddrive, not from the current CD system.
Maybe they include a hint.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
battleshooter wrote:I'm not sure what's wrong but I can't seem to get glxgears working. I get the message:Code: Select all
Xlib: extension "GLX" missing on display ":0.0" Error: couldn't get an RGB, Double-buffered visual
Ok, I google it and found that it would be a problem with the xf86-video-intel driver. So I need to update xf86-video-intel, libdrm, drm kernel modules and Mesa to their latest stable versions or download everything from git (bleeding edge, unstable) make some .pets or an ISO (plus bugfixes and few goodies).Xorg.0.log wrote:(EE) intel(0): [dri] I830CheckDRIAvailable failed: glx not loaded
If you have the knowledge, please go ahead and install those packages from source.
I configured X with
Code: Select all
./configure --build=i686-pc-linux-gnu --prefix=/usr/X11R7 --libdir=/usr/X11R7/lib --includedir=/usr/X11R7/include --sysconfdir=/etc --localstatedir=/var
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
- battleshooter
- Posts: 1378
- Joined: Wed 14 May 2008, 05:10
- Location: Australia
So, I guess that's the final diagnosis and there's nothing to be done except compile the new packages from source.Ok, I google it and found that it would be a problem with the xf86-video-intel driver.
I've done some compiling before, but doing Xorg is way over my head. Rather intimidating I guess I'll just wait till the next ISO update or whatever comes. It's not like I'll die not being able to play Paintball I might consider having ago one day, but it'll be a steep learning curve.If you have the knowledge
@ Mark
Actually, I completely forgot about that. A while back I tested the official Puppy 4 with my laptop and I was given completely screwed graphics. So that would explain why the original libglx was so disastrous. Sorry I didn't bring it up, I forgot.what really makes me wonder is, that libglx.so from the original xorg gives a black screen.
Battleshooter
-
- Posts: 632
- Joined: Tue 02 Oct 2007, 07:39
Do these drivers (9.1) work at all in Puppy? I run the official installer,the driver installs OK,then an aticonfig --initial -f and restart X. After that, I get a black screen and I'm forced to do a soft system reboot to get to the commandline.MU wrote:I actually tried the new Ati catalyst driver 9.1.
It compiled, but the fglrx kernelmodule would not load.
dmesg and googe told be, that this is, because in the kernels .config this must be set:Unfortunately, this seems to make it incompatible with wows kernel.Code: Select all
# # Bus options (PCI etc.) # CONFIG_PCI_MSI=y
I had to replace the modules in intrd.gz with the recompiled ones.
There are several complains about this in the phoronix forum, so I hope, they will release a version without this option.
I have not yet decided, which kernel I'll use for newyearspup final tomorrow.
If I succeed to compile a patched wine that supports pixelshaders with that catalyst driver, I would use the new kernel.
If not, this had to wait for newyearspup03 in 3 months.
I would not like, to break compatibility with wows kernel...
Wine anyway seems not to compile with the typedefs I had to add.
Mark
Catalyst 8.11 produces the same issue. (8.12 works)
I downloaded drm-2.4.4 from git, xf86-video-intel-2.6.1 and Mesa-7.3 (libs, glut, demos).
libdrm and xf86-video-intel configured with:
Mesa 7.3:
Mesa asks for dri2proto, downloading it right now, I'll try to test this new intel driver today (I don't have the hardware to, but some friends have it) and make dotpets later.
libdrm and xf86-video-intel configured with:
Code: Select all
./configure --build=i686-pc-linux-gnu --prefix=/usr/X11R7 --libdir=/usr/X11R7/lib --includedir=/usr/X11R7/include --localstatedir=/var --sysconfdir=/etc --disable-static --disable-maintainer-mode --enable-shared
Code: Select all
./configure --build=i686-pc-linux-gnu --prefix=/usr/X11R7 --libdir=/usr/X11R7/lib --includedir=/usr/X11R7/include --localstatedir=/var --sysconfdir=/etc --disable-static --disable-maintainer-mode --enable-shared --with-dri-driverdir=/usr/X11R7/lib/dri
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
techtype
you'll find it here:
http://puppyisos.org/isos/2008-07-to-12 ... .5/iso-01/
user: puppy
password: linux
Mark
you'll find it here:
http://puppyisos.org/isos/2008-07-to-12 ... .5/iso-01/
user: puppy
password: linux
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
- battleshooter
- Posts: 1378
- Joined: Wed 14 May 2008, 05:10
- Location: Australia
Ah, thanks Mark!MU wrote:techtype
you'll find it here:
http://puppyisos.org/isos/2008-07-to-12 ... .5/iso-01/
user: puppy
password: linux
Mark
wow,wow wrote:Unnamed pupplet (puppy411 kernel-2.6.27.5 Xorg-7.4 LXDE)
Subject description: just another puppy derivate
...
Default encoding for filenames in vfat partitions is UTF-8 (kernel module nls_utf8 by default)
...
From my experience the Unnamed-pupplet-puppy411-kernel-2.6.27.5 Xorg-7.4-LXDE is the only Puppy that properly displays sl_SI locale special characters in Rox. I noticed that sl_SI locale special characters in Rox are shown properly even if locale is set to en_US.
Would you be willing to explain what have you done to set this option to work?
We discussed this issue on Barry's blog.
Details:
http://puppylinux.com/blog/?viewDetailed=00556
Easy: Full installLeon wrote:I noticed that sl_SI locale special characters in Rox are shown properly even if locale is set to en_US.
Would you be willing to explain what have you done to set this option to work?
- You have to compile your own kernel with these options in "DOS/FAT/NT Filesystems"(kernel's .config file):
Install and boot your kernel.
Code: Select all
CONFIG_FAT_DEFAULT_CODEPAGE=850 CONFIG_FAT_DEFAULT_IOCHARSET="utf8"
- Compile linux kernel with these options in "DOS/FAT/NT Filesystems"(kernel's .config file):
Install and boot your kernel.
Code: Select all
CONFIG_FAT_DEFAULT_CODEPAGE=850 CONFIG_FAT_DEFAULT_IOCHARSET="utf8"
Extract contents of initrd.gz and replace every kernel module in initrd/kernel/
Add nls_utf8.ko and nls_cp850.ko files to initrd/kernel/fs/nls/
Replace names(nls_cp850 and nls_utf8) in initrd/init (text file)
Instructions to edit the initrd.gz file, patch the linux kernel, make an iso with your new kernel and more help [here], [here], [and here]
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
Many thanks for the instructions.wow wrote:Easy: Full installLeon wrote:I noticed that sl_SI locale special characters in Rox are shown properly even if locale is set to en_US.
Would you be willing to explain what have you done to set this option to work?Hard: Full install, initrd.gz and pup_4xx.sfs edit, remaster LiveCD.
- You have to compile your own kernel with these options in "DOS/FAT/NT Filesystems"(kernel's .config file):
Install and boot your kernel.Code: Select all
CONFIG_FAT_DEFAULT_CODEPAGE=850 CONFIG_FAT_DEFAULT_IOCHARSET="utf8"
- Compile linux kernel with these options in "DOS/FAT/NT Filesystems"(kernel's .config file):
Install and boot your kernel.Code: Select all
CONFIG_FAT_DEFAULT_CODEPAGE=850 CONFIG_FAT_DEFAULT_IOCHARSET="utf8"
Extract contents of initrd.gz and replace every kernel module in initrd/kernel/
Add nls_utf8.ko and nls_cp850.ko files to initrd/kernel/fs/nls/
Replace names(nls_cp850 and nls_utf8) in initrd/init (text file)
Instructions to edit the initrd.gz file, patch the linux kernel, make an iso with your new kernel and more help [here], [here], [and here]
Leon
I spoken too soon... I missed something...battleshooter wrote:Yippee! Thanks so much WowI'll try to test this new intel driver today (I don't have the hardware to, but some friends have it) and make dotpets later.
So I have to download and compile drm-intel. Anyway, I have packaged everything else, download these files if you want [download from filefront]:http://cgit.freedesktop.org/mesa/drm/tree/README wrote:The kernel device modules are not shipped with libdrm releases and should only
be built from the git tree by developers and bleeding-edge testers of
non-Intel hardware. The Intel kernel modules are developed in the Linux
kernel tree.
- libdrm-2.4.4git-i686.pet
mesa-7.3-i686.pet
drm-2.4.4-k2.6.27.5.tar.bz2
xf86-video-intel-2.6.1-i686.pet (attached below)
1. Switch to Xvesa (exit X and run xorgwizard)
2. Once in Xvesa, install: libdrm-2.4.4git-i686.pet; mesa-7.3-i686.pet; xf86-video-intel-2.6.1-i686.pet
3. Extract drm-2.4.4-k2.6.27.5.tar.bz2 to any folder (example: /root)
4. Exit X, go to the drm-2.4.4.-k2.6.27.5/ folder and run install.sh. Example:
Code: Select all
cd /root/drm-2.4.4.-k2.6.27.5/
./install.sh
Screenshot: Mesa-7.3, vesa xorg video driver, software rasterizer (vesa has no hardware acceleration)
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
iscraigh also will post a kernel request soon (I asked him to post it here, after he wrote a pm).
This should force us to overthink, if we should go for a new kernel, with all the new settings we need.
I would need for the new Ati catalyst driver:
If we decide to compile such a kernel, and build new isos then, we also might switch to a newer kernel release?
Or should we stay with the current one?
I was planning to try 2.6.29 in april, because it includes some new stuff for next xorg releases (dri2 I think, but I'm not certain, if it was called different).
Apart from that, I have no need of a new kernel release yet.
We also had to test, if the Ati and Nvidia drivers compile with it, especially nvidia 96 and 173.
What do you think?
Mark
This should force us to overthink, if we should go for a new kernel, with all the new settings we need.
I would need for the new Ati catalyst driver:
Code: Select all
#
# Bus options (PCI etc.)
#
CONFIG_PCI_MSI=y
Or should we stay with the current one?
I was planning to try 2.6.29 in april, because it includes some new stuff for next xorg releases (dri2 I think, but I'm not certain, if it was called different).
Apart from that, I have no need of a new kernel release yet.
We also had to test, if the Ati and Nvidia drivers compile with it, especially nvidia 96 and 173.
What do you think?
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
iscraigh seems to be offline, so here I quote his request, before I go asleep:
--------------------------------------------------------------------------------
Mark
I have cobbled together a puplet based on the unamed pup for the Aspire one netbook. I still have a hardware issue with the sd card slots being recognized. Using some advice from other posting on the aspire one I was able to get the left card hotplugging but found I did not have the pciehp module.
Tempestuous suggested I ask you "very nicely" to enable it in the kernel.
On that note assuming you are able to do this would I have to do the whole remaster again or could I mount the sfs file (is mounting an sfs rw possible) and swap in your kernel?
I am finding myself a little over my head I just made this for my kids and now people are using it so I feel I should try to keep it up.
As log as I am harrasing you one more thing
Boot speed is slower on puppy than a full ubuntu install.
I see that sickboy from the kuki linux project has a kernel just for the aspire that is supposed to be fast, could I substitute that kernel? (It can't be that easy I am sure)
Puppy seems to take forever at
Craig
--------------------------------------------------------------------------------
Mark
I have cobbled together a puplet based on the unamed pup for the Aspire one netbook. I still have a hardware issue with the sd card slots being recognized. Using some advice from other posting on the aspire one I was able to get the left card hotplugging but found I did not have the pciehp module.
Tempestuous suggested I ask you "very nicely" to enable it in the kernel.
If this is not to much trouble I would appreciate it.I suggest you ask MU nicely to enable this module in the 2.6.27 kernel configuration. It's at:
"Bus options (PCI etc.)" > "Support for PCI Hotplug"
this will then reveal an additional option above it called "PCI Express Hotplug driver"
This driver will not load automatically. The best way to load it at each bootup is by adding it to Puppy's "ADDLIST".
On that note assuming you are able to do this would I have to do the whole remaster again or could I mount the sfs file (is mounting an sfs rw possible) and swap in your kernel?
I am finding myself a little over my head I just made this for my kids and now people are using it so I feel I should try to keep it up.
As log as I am harrasing you one more thing
Boot speed is slower on puppy than a full ubuntu install.
I see that sickboy from the kuki linux project has a kernel just for the aspire that is supposed to be fast, could I substitute that kernel? (It can't be that easy I am sure)
Puppy seems to take forever at
Any help appreciated.loading kernel drivers to access disk drives
Craig
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
I just have a rough idea:Puppy seems to take forever at Quote:
loading kernel drivers to access disk drives
At startup, use the option:
pdev1=sda1
If you boot from CD, type at the bootscreen:
puppy pdev1=sda1
If you boot frugal, add in the end of the line that loads the kernel:
pdev1=sda1
Instead of sda1, use the name of the drive, where your savefile is located.
This avoids, that Puppy scans ALL partitions for a savefile.
If the delay happens BEFORE this part already, we had to look closer at initrd.gz.
We must look, if that part can be optimized.
I hope I have time for this at weekend.
In "init", there is a part, that greps dmesg for loaded drivers. If I remember well, this uses a delay/timeout.
Maybe this can be enhanced.
I boot some files from an external USB-harddisk, so maybe, this is faster that on computers without USB-drives, as they write different messages to dmesg.
I could setup a testsystem, that will completely load from my internal drive (a CF card replacing a harddisk), without other drives attached.
-----------------
Simply replacing a kernel is not that simple.
The problem is, that also the modules in initrd.gz must be replaced, and some files in /etc/modules.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]