@10wt3ch
Thanks for the lead.
alsa-base-conf shows 2 kernel modules loaded from previous computer!!
Seems Puppy Studio updated a previous .sfs file on its initial run.
Will try starting again tomorow with pfix=ram. (Now after midnight in Sydney!)
Search found 10 matches
- Sat 30 Oct 2010, 13:04
- Forum: Puppy Derivatives
- Topic: Puppy Studio: A Superior Technology
- Replies: 28
- Views: 23957
- Sat 30 Oct 2010, 12:18
- Forum: Puppy Derivatives
- Topic: Puppy Studio: A Superior Technology
- Replies: 28
- Views: 23957
No sound on Puppy Studio
Having used Ubuntu Studio for some years and Puppy ever since Puppy 1xx, I am excited about Puppy Studio. Great distro! But no sound! I can get sound on Windows and Ubuntu 10.10 but not on Puppy Studio or on Wary 092. Printout of audio devices (onboard audio + Creative sound card) from lspci: Onboar...
- Fri 25 Sep 2009, 05:58
- Forum: Misc
- Topic: Highly exploitable Linux kernel bug found
- Replies: 8
- Views: 2935
- Fri 25 Sep 2009, 05:41
- Forum: Misc
- Topic: Highly exploitable Linux kernel bug found
- Replies: 8
- Views: 2935
sunburst, thx for the clarification. I'm running Puppy 4.2.1 live and the attached file is the output from lsmod. Only 52 modules loaded? Is that correct? Of the 52 entries, 32 relate to the sound system. So it is no wonder that Puppy manages sound files and codecs better than others. One entry (snd...
- Fri 25 Sep 2009, 00:08
- Forum: Misc
- Topic: Highly exploitable Linux kernel bug found
- Replies: 8
- Views: 2935
OK so how does Barry (or yourself in the case of Pizzapup) decide which drivers to include in the kernel (or rather which to leave out), seeing that Puppy manages to find all my hardware and provide drivers out of the box. Puppy does this better than Ubuntu, especially with sound cards. BTW I checke...
- Thu 24 Sep 2009, 14:25
- Forum: Misc
- Topic: Highly exploitable Linux kernel bug found
- Replies: 8
- Views: 2935
Linus:"Kernel is bloated, huge"
http://www.linux-mag.com/cache/7536/1.html Article is optimistic about the kernel developers' ability to trim the kernel when size affects performance more obviously. How does Puppy manage to keep small when the kernel has almost doubled from 2.6.11 to 2.6.30? (Even 2.6.30 has 20,000 more lines of ...
- Mon 23 Jul 2007, 00:40
- Forum: Users ( For the regulars )
- Topic: X doesn't staart after upgrade to 2.16.0 (from 212)
- Replies: 6
- Views: 2792
Problem solved!
Hairy Will,
After trying unsuccessfully to sort out what was happening to xorg.conf, I upgraded further to 2.16.1 and had no problem.
Thanks again for your feedback and help.
Regards
Adrian
After trying unsuccessfully to sort out what was happening to xorg.conf, I upgraded further to 2.16.1 and had no problem.
Thanks again for your feedback and help.
Regards
Adrian
- Tue 26 Jun 2007, 14:06
- Forum: Users ( For the regulars )
- Topic: X doesn't staart after upgrade to 2.16.0 (from 212)
- Replies: 6
- Views: 2792
Checking xorg.conf
Will I booted the new 216 DVD using the boot instruction puppy pfix=nox then checked xorg.conf before it tried to start X and got the following (snippets) Section "Server Layout" Identifier "X.org Configured" Screen 0 "Screen0" 00 (not sure why the zeros are there) Sect...
- Mon 25 Jun 2007, 23:48
- Forum: Users ( For the regulars )
- Topic: X doesn't staart after upgrade to 2.16.0 (from 212)
- Replies: 6
- Views: 2792
Thanks for the feedback
Will, .xnitrc has the lines as you posted them for rox1 and rox2. "rox -v .....Filer 1" gives no output. "rox -v .....Filer 2" gives "ROX-Filer 2.5" Where do I find the rox configuration file which might have a clue as to the crash? What about the other error message ab...
- Mon 25 Jun 2007, 14:00
- Forum: Users ( For the regulars )
- Topic: X doesn't staart after upgrade to 2.16.0 (from 212)
- Replies: 6
- Views: 2792
X doesn't staart after upgrade to 2.16.0 (from 212)
I am having the same problem that aggie2015 had last Tuesday with X not starting. Burnt the iso to DVD and upgrade went well until it came to setting up xwin. xorgwizard goes OK but after a flash of the X window graphics it reverts to error messages. xerrs.log: (EE) failed to load module "glx&q...