Icebooks
Before I go and do something stupid, does any one have any particular (dis)recommendations about using the newer iBooks with Debian? Looking at the spec and grovelling around on the web it seems they do reasonably well. -- "You grabbed my hand and we fell into it, like a daydream - or a fever."
Re: airport eth1, onboard eth0 & eth1 Tx error, status 1
On Fri, May 17, 2002 at 06:46:50PM -0500, [EMAIL PROTECTED] wrote: > The eth1: timeout messages seem to be a bug in the airport driver. > Mine spits them out all the time (and others when it resets the card) > but still seems to work. I've been able to eliminate them almost IME these messages happen when the signal is weaker than the card would like - try taking a look at the signal strengths you're seeing. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpIbjxFGhCYx.pgp Description: PGP signature
Re: Bug#155095: libmm11 1.1.3-7 broken on PowerPC
On Thu, Aug 01, 2002 at 02:48:34PM +0200, Rubin wrote: > I've seen this workaround being tried on the alpha platform but as far > as I can see this does not work for powerpc. What changed between > 1.1.3-6 and 1.1.3-7 that breaks php in this case? Maybe a /usr/doc/libmm Nothing. PHP keeps on randomly breaking, even with only rebuilds rather than code changes for the shared library - the same thing happened between -4 and -6 on alpha with no code changes involved. There's a potential issue with the choice of shared memory type but that wouldn't affect PowerPC. > in the future releases of libmm might be a good idea (didn't I see a > bugreport for that somewhere? ;-). There shouldn't be. The /usr/share/doc transition is moving to the next stage. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgp96TiElMBzP.pgp Description: PGP signature
Re: Bug#155095: libmm11 1.1.3-7 broken on PowerPC
On Thu, Aug 01, 2002 at 11:07:02AM -0400, Christopher C. Chimelis wrote: > I just posted a follow-up to that bug report, complete with some > experimentation results. To summarise, either double your shmmax or > recompile libmm11 with --with-shm=MMFILE. Looks like there's a bug > somewhere WRT IPCSHM (could be kernel, could be libmm...dunno yet..hell, > it could be PHP). I'm going to rebuild forcing shm to MMFILE anyway since it'll avoid problems with the shm method randomly changing depending on which buildd it gets built on. > I am going to try libmm12 to see if that helps (not looking forward to > recompiling php4, but I might as well). I wouldn't bother, it doesn't achieve much and since this bug keeps appearing and disappearing it needn't prove anything. I did try this already but since I can't reproduce on this PowerPC machine in the first place I'm not sure it's achieved anything. > Mark, anything else that you'd like me to try? Adding diagnostics to php4 so it'd actually say what went wrong (MM provides mm_error() giving a text-form error) might be helpful. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpCbNYAirQjb.pgp Description: PGP signature
Re: Bug#155095: libmm11 1.1.3-7 broken on PowerPC
On Thu, Aug 01, 2002 at 11:43:23AM -0400, Christopher C. Chimelis wrote: > Good idea. MMFILE is probably the safest, although I'm still puzzled as > to why IPCSHM seems to be so flaky. > It proved one thing: that compiling against libmm12 didn't make a > difference :-P I still get the same problems with the IPCSHM-configured > libmm12. I've got an MMFILE-forced package ready for upload - should be in incoming tomorrow. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpwIx2F4DhP9.pgp Description: PGP signature
Re: Bug#155095: libmm11 1.1.3-7 broken on PowerPC
On Thursday, August 1, 2002, at 06:43 PM, Christopher C. Chimelis wrote: I'm a bit tied up with other work now, but I'll see if I can find out what path has assigned to it. I wouldn't worry about it so much if the problem goes away with MMFILE - I do have an upload forcing the shm type to that, so if SysV shared memory isn't working I'm not so bothered. -- "You grabbed my hand and we fell into it, like a daydream - or a fever"
Re: Bug#155095: libmm11 1.1.3-7 broken on PowerPC
On Thursday, August 1, 2002, at 07:14 PM, Christopher C. Chimelis wrote: The only thing that I can think of is that there is or was a toolchain bug on the powerpc that built the last libmm debs (and the libmm12 deb). If you built them, what versions of the toolchain packages are you running? If it's the buildd's, then they should be checked out as well. Which kernel version are you running? The results of configure depend on that (this is one of the things that will be fixed with forcing MMFILE). -- "You grabbed my hand and we fell into it, like a daydream - or a fever"
Re: tiBook CPU speed
On Tue, Aug 06, 2002 at 10:50:43AM -0400, Michael Furr wrote: > Do you have any plans to try to integrate this with the cpu temperature > detection so that it would automagically downclock when it runs too hot > for too long? Surely that's something that should be done in user space? -- "You grabbed my hand and we fell into it, like a daydream - or a fever."
Re: Please test 2.4.20 packages
On Wed, Mar 26, 2003 at 03:15:09PM -0500, Daniel Jacobowitz wrote: > Before I prepare a 2.4.20 update for stable, I'd like some people to try > them out and report success. So if you have hardware that plain old 2.4.20 > can handle and don't need -benh9johnhQac37 to get your foobar to baz > properly, please give them a try and let the list know if they work. kernel-image-2.4.20-powerpc seems to work OK with my Cube. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpkBDAE8KJcs.pgp Description: PGP signature
Re: debian-powerpc: configuring the airport
On Mon, Nov 12, 2001 at 07:49:55PM +1100, Brendan J Simon wrote: > basestation and/or vice-versa. I would like something a bit more secure. As someone else said, you can have a Linux PC do NAT for you. As far as the security bit goes, you might wish to consider running IPsec over the wireless network since there's no effective security in the protocol.
X on the new TiBooks
I've been trying to get my new TiBook set up for Debian. So far (thanks to the guide Branden provided) the only real sticking point is X. Has anyone got any suggestions on how to get the server running? Rather than try building and installing the CVS X server I've been attempting to use the framebuffer X server together with a current rsynced copy of benh's kernel. With any actual resolution an unviewable image is produced (full screen 1152x768 appears not to be supported by the framebuffer device). With 1152x864 X displays a recognisable image but seriously distorted and with areas of black on the screen. I don't seem to have seen any discussion of this on this list since the initial thread last week - is there anywhere else I should be looking? -- "You grabbed my hand and we fell into it, like a daydream - or a fever."
Re: X on the new TiBooks
On Sun, Nov 18, 2001 at 06:31:19PM +, Mark Brown wrote: > I've been trying to get my new TiBook set up for Debian. So far (thanks > to the guide Branden provided) the only real sticking point is X. Has > anyone got any suggestions on how to get the server running? Just to clarify - this is one of the new TiBooks not one of the old ones with a Rage 128. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpwJ46YcUPzD.pgp Description: PGP signature
Re: X on the new TiBooks
On Mon, Nov 19, 2001 at 12:27:03AM +0100, Michel Dänzer wrote: > The framebuffer device should display any mode passed to it by the X > server. Do you have an 1152x768 mode definition in your XF86Config > (there is no such mode built into the server yet) and use that? I didn't - a couple people sent me appropriate bits of configuration privately. However, that hasn't completely cured the problem - the colours are all wrong (it looks for all the world as if everything's in 16 colours, though as far as I can tell from the X server output that's news to it). It's bad enough to still be hard to look at, though I suspect that if I fell back onto something like twm that might not be such a problem. I've also had one hard lockup of the machine while running the X server like this, though I'm not entirely convinced that wasn't kernel related rather than the X server. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgp2yzmJeYUNC.pgp Description: PGP signature
Re: X on the new TiBooks
On Sun, Nov 18, 2001 at 08:36:03PM -0500, Christopher C. Chimelis wrote: > I've got X semi-working on my new TiBook using the fb driver, but the > colourmap is really screwed up. I'm working on extracting the Radeon M6 Sounds like about where I am. Wierd thing is the colourmap was fine when using the (obviously very broken in other ways) 1172x864 configuration. As I said in my previous e-mail, it looks kind of like the sort of colour scheme you oftne get if you force something to display on a display with far fewer colours than it was designed to cope with. Looking at a stripped down session with twm the effect for things not in black and white is almost reverse video. > support out of XFree86's CVS tree, but it's slow going so far (their > changelog leaves alot to be desired in terms of helpfulness). If I get > anything soon, I'll send it to you to test. In the meantime, would you Please. > like my XF86Config-4? It's very ugly, but X does work. I suspect it's not going to be too different to what I've got. I could take a look and start trying to do a contrast & compare with the other configurations. I'd been going with the framebuffer stuff since it seems safer and half my use of X is as a mechanism for switching so I'm not particularly concerned about performance. > Oh, also, I've had a lockup once or twice while testing X, but it was > always after I had killed the Xserver a few times and was working on the > console again. So far, no concrete way of reproducing that behaviour... I've had one of those and a very hard lock where I lost the network too. Something tells me that it could be related to the power management but I can't think of anything concrete I'm basing that on. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpU7TKoFDzOW.pgp Description: PGP signature
Re: Mac-On-Linux?
On Tue, Nov 20, 2001 at 11:02:33PM +0100, Nik wrote: > perhaps mol-modules-source should also provide "mol-modules"? Have you taken a look at the result of using mol-modules-source? The package produced is what's needed to satisfy the dependancy, not the sources for the modules. I'd question having the dependancy in the first place, though - nothing else with similar needs (lm-sensors for example) does that and it is unhelpful if one doesn't wish to use kernel-package. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpRvHVoAWstC.pgp Description: PGP signature
Re: Mac-On-Linux?
On Wed, Nov 21, 2001 at 01:29:39AM +, Jens Schmalzing wrote: > Mark Brown writes: > > I'd question having the dependancy in the first place, though - > > nothing else with similar needs (lm-sensors for example) does that > > and it is unhelpful if one doesn't wish to use kernel-package. > You have a point there that I first overlooked. Still, I would like > to keep a dependency expressing that mol needs its kernel modules to > function. This does come at a price (namely, installing three > unnecessary kernel modules) for users who decide to bypass the package There's been some discussion on the topic on -devel in the past. Not only might the modules be unneeded, they might collide with the user installed one. > system. But I think it is preferrable to leaving out vital components > of a piece of software by default. I can quite happily have the modules installed and either not load them or run a completely different kernel (perhaps a packaged one) for which they are not applicable. Having the dependancy doesn't provide a full solution for the problem. -- "You grabbed my hand and we fell into it, like a daydream - or a fever."
Re: X on the new TiBooks
On Fri, Nov 23, 2001 at 12:21:03AM -0500, Christopher C. Chimelis wrote: > work on it some more. In the meantime, I've discovered that the only > reason that my colourmap was screwed up under X using the framebuffer > Xserver was because of the default fb depth (which is 8). When I did > 'fbset -depth 16' and then started X with the config below, KDE popped That works for me too. Thanks! I wonder why the X server doesn't manage to do that for itself. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpZratBmzfwK.pgp Description: PGP signature
Re: X on the new TiBooks
On Fri, Nov 23, 2001 at 11:30:10AM +0100, Michel D?nzer wrote: > DefaultDepth depth > specifies which color depth the server should use by default. > The -depth command line option can be used to override this. If > neither is specified, the default depth is driver-specific, but in > most cases is 8. Yes, I've got that set. It doesn't appear to be causing the framebuffer to get configured appropriately (or at least, it gives a very screwy colourmap unless I do what Chris suggested and use fbset before starting the server). -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgp2zATZEU3T7.pgp Description: PGP signature
Re: X on the new TiBooks
On Fri, Nov 23, 2001 at 07:50:28AM -0500, Christopher C. Chimelis wrote: > At any rate, I'm just happy to have X running at all, even if it's using > the FB driver :-) The performance is certainly more than adequate for what I use X for :-) -- "You grabbed my hand and we fell into it, like a daydream - or a fever."
Installation on a Cube
I'm trying to get Debian up and running on a Cube. So far I've been unable to find an installation system which will run on the machine. With both potato and current woody installers I find that the kernel doesn't succeed in displaying anything on the framebuffer which makes the installer kind of hard to use. If I take a woody installer and replace the kernel with one built from benh's rsync tree I get a visible console and the installer runs but denies the existence of the hard disk. The kernel is able to see the disk quite happily and if I exit to a shell I can run mac-fdisk and mkfs successfully. Any suggestions? If there's any more diagnostic information that would be useful I'd be happy to provide this. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpOITBgsHnt0.pgp Description: PGP signature
Re: Installation on a Cube
On Sun, Dec 02, 2001 at 12:14:18PM -0700, Derrik Pates wrote: > When booting, the system should come to a 'boot:' prompt. Type 'debian > video=ofonly' at the prompt, this should force the (admittedly aging) > kernel to use the OpenFirmware console device, which won't be fast, but > will be enough to get you booted and interacting with the console. I've been running with video=ofonly in my yaboot.conf for the woody installer (booting from a HFS partition on the hard disk). Specifying it explicitly for the potato CDs I have didn't seem entirely succesful - instead of hanging with no output the machine was powered down very rapidly after system startup. Removing the USB speakers didn't seem to have much effect on anything. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgp0XqjSWmUx7.pgp Description: PGP signature
Re: Installation on a Cube
On Sun, Dec 02, 2001 at 12:49:59PM -0800, ozymandias G desiderata wrote: > There is, however, a workaround, grotty thought it may be. I forked a > shell and created, initialized, and mounted all of the partitions on > the disk by hand. I also had to run mkofboot / ybin by hand from the > shell, as well as hand-crafting a yaboot.conf. So, basically, all the > installer did was give me enough of an environment to get busybox > working, and install the base distribution. OK, that seems doable. I had thought I must be missing something - the Cube isn't all that bleeding edge and I was expecting it to work reasonably well out of the box. > I also configured networking from the shell, but that may have just > been due to my own impatience -- try it from the installer and see > what happens. DHCP works fine from the installer. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpIxd3Hgvfio.pgp Description: PGP signature
Re: Installation on a Cube
On Sun, Dec 02, 2001 at 10:06:14PM +, Mark Brown wrote: > On Sun, Dec 02, 2001 at 12:49:59PM -0800, ozymandias G desiderata wrote: > > There is, however, a workaround, grotty thought it may be. I forked a > > shell and created, initialized, and mounted all of the partitions on > > the disk by hand. I also had to run mkofboot / ybin by hand from the > > shell, as well as hand-crafting a yaboot.conf. So, basically, all the > > installer did was give me enough of an environment to get busybox > > working, and install the base distribution. > OK, that seems doable. I had thought I must be missing something - the > Cube isn't all that bleeding edge and I was expecting it to work > reasonably well out of the box. I'm typing this from the console on my cube while base-config completes, so I guess that worked. Not really what I'd hope for from the woody installer, though. I'm not sure where to direct a bug report? -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgp7tyXxZ5xjs.pgp Description: PGP signature
Re: misc. woes
On Tue, Dec 04, 2001 at 04:45:31PM +0100, Michel Dänzer wrote: > In my experience, the Cube doesn't compare too badly with an Athlon 800. > YMMV. It's certainly an awful lot faster than a K6-II/500. I wonder if Albert's running with an OpenFirmware framebuffer only? That would make everything appear much slower interactively than it really is. > IMHO most of your problems you should be able to resolve yourself easily > if you really want though, or failing that maybe by asking politely. Having just installed on a Cube coming from a "little PPC experience" perspective I have to agree with this. Branden's iBook page would make a very good addition to the installation manual - there's a bunch of stuff I wouldn't have picked up from the manual as it stands in there. The page: http://people.debian.org/~branden/ibook.html -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpJW7YzBtbED.pgp Description: PGP signature
Re: Buildd Failures Update
On Wed, Dec 05, 2001 at 01:37:49PM -0600, Stephen R Marenka wrote: > Requeue Needed (builds fine for me) > -- > scsitools - wish should be installed properly. > netdude - no failure log for latest version. > netcfg - no failure log (old - 2001 Jun 18) When I asked about working on stuff I was told to just upload stuff if it built. What's the party line? -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpxRhJYrLwDJ.pgp Description: PGP signature
Re: Buildd Failures Update
On Wed, Dec 05, 2001 at 08:28:55PM +, James Troup wrote: > Mark Brown <[EMAIL PROTECTED]> writes: > > When I asked about working on stuff I was told to just upload stuff if > > it built. What's the party line? > I can't/don't/won't speak for Dan, but in general, uploading stuff > because it `works for you' (aka 'human auto-building') is, IMNSHO, bad > practice. If something doesn't auto-build cleanly, it should be That had been my original thought. > fixed. If it was cosmic rays, it should be retried (or whatever). If > you fix it by building it by hand, that's okay now, but when the next > upload comes along (and assuming it wasn't cosmic rays (which it rarely > is)), it's simply going to fail again and you may not be around to > play human auto-builder that time round. It would also be useful to have a more general way of attaching notes to the buildd logs. Something like what QA has at standard.debian.net might not go amiss. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgp22qWBYy9cZ.pgp Description: PGP signature
Re: Potato 2.2_rev4 cd iso not bootable?
On Thu, Dec 13, 2001 at 12:27:29AM +0100, Florian Friesdorf wrote: > On Wed, Dec 12, 2001 at 04:05:20PM -0500, Colin Walters wrote: > > http://cdimage.debian.org/cd-images/2.2_rev4.1/powerpc/ > That sounds really good. It's a pity the server wants a username and > password. > Are there any openly available 4.1 images? Take a look at the http://cdimage.debian.org/ root page. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpBeN1GqNAtb.pgp Description: PGP signature
Re: iBook2 keyboard ...
On Sun, Dec 16, 2001 at 06:03:00PM +0100, Michel Dänzer wrote: > > Additionally, this machine seems to periodically time-warp to 1904 -- I > > assume > > that it has no internal battery to power the RTC when the battery and mains > > power is disconnected? > Bingo. Something like ntp is your friend. The time also seems to reset when the hardware reset switch is used. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpiliivwsYNz.pgp Description: PGP signature
Re: cooledit segfault on powerpc (was Re: Help with #123015 on cooledit)
On Sat, Dec 29, 2001 at 04:03:52AM -0600, Aaron Schrab wrote: > Another occurrence of reusing a va_list variable. Although in this > case, it looks like it was just an oversight. In addition to fixing That worked. I'm uploading just now. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpqGxPWHlu6K.pgp Description: PGP signature
Bug#122283: ilu build failure on PowerPC
I've just tried to reproduce this bug on PowerPC and failed. I'm guessing that the failure must have been caused by some failure in some other part of the system (possibly autoconf) which has since been resolved. The referenced build log[1] shows the failure apparently being due to the absence of access() which seems rather bogus. A requeue of the package might be in order. [1] http://buildd.debian.org/fetch.php?&pkg=ilu&ver=2.0.0.91-4&arch=powerpc&stamp=1005515260&file=log&as=raw -- "You grabbed my hand and we fell into it, like a daydream - or a fever."
Re: PowerBook G4
On Thu, Jan 03, 2002 at 07:22:44PM +0100, Michel Dänzer wrote: > By then it will be perfect. ;) Seriously, XFree86 4.2.0 will be out > which offers very decent support for the graphics chip. The rest of the As it stands, it's pretty darn fast with just the framebuffer driver - unless I try to run something that uses OpenGL I have completely failed to notice that it's unaccelerated. > hardware will also hopefully be supported in the mainline kernel by > then, and if not it will certainly be in the PPC specific kernels. Aside from the 3D acceleration and the modem most stuff is already supported to at least a reasonable. I think the only things I've not tried are PCMCIA (I'm pretty sure that's supported), IR and the video out. Basically, you'd be pretty much OK if you had one now and things are likely to get better. -- "You grabbed my hand and we fell into it, like a daydream - or a fever."
Re: PowerBook G4
On Thu, Jan 03, 2002 at 11:14:18PM +0100, Michel Dänzer wrote: > On Thu, 2002-01-03 at 19:35, Mark Brown wrote: > > As it stands, it's pretty darn fast with just the framebuffer driver - > > unless I try to run something that uses OpenGL I have completely failed > > to notice that it's unaccelerated. > You obviously don't move windows opaquely or scroll their contents. ;) > Of course, depending on what you used before, you won't notice before > using the accelerated driver. I do do things like that - it's snappy enough for me not to notice. Perhaps with different programs, though. > Absolutely. When I'll become the proud owner of such a machine at last, > I won't be able to live without 3D acceleration for a long time - all > those games are just no fun without. So I'm rather confident that it'll I always found 3D acceleration made remarkably little difference to my enjoyment of nethack :-) . -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpLI6MZGIuCo.pgp Description: PGP signature
Re: microwindows build status
On Thu, Jan 03, 2002 at 07:10:58PM -0800, Thomas Bushnell, BSG wrote: > I would like to close bug 121459, and rely on powerpc to attempt a > build by the normal process and report a new bug against the current Please don't. I just tried to build it and got exactly the same error as in the build report. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgprs1RPC77f1.pgp Description: PGP signature
Re: microwindows build status
On Fri, Jan 04, 2002 at 07:21:52PM +0100, Michael Schmitz wrote: > > Please don't. I just tried to build it and got exactly the same error > > as in the build report. > What version of apt do you have installed? 0.5.4. Why? -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgphDcX7Hq6gu.pgp Description: PGP signature
Re: microwindows build status
On Fri, Jan 04, 2002 at 07:21:16PM +0100, Michael Schmitz wrote: > Please note that I haven't filed any bug of that sort (I rarely do these > days, rather rely on the maintainer to check build status and logs). FYI: It's worth telling to maintainers - a huge proportion won't pay any attention unless information is pushed at them, particularly given that the porting process is normally so transparent. (actually, there seem to be a couple of people looking at the buildd stats pages for PowerPC so you probably don't need to bother). -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpY8nWndBkvU.pgp Description: PGP signature
Re: microwindows build status
On Fri, Jan 04, 2002 at 08:18:59PM -0800, Thomas Bushnell, BSG wrote: > What do you mean by "the build report"? Do you mean bug report > 121459? The bug, sorry. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgppEauWGvXT6.pgp Description: PGP signature
Re: microwindows build status
On Sat, Jan 05, 2002 at 01:33:25PM -0500, Daniel Jacobowitz wrote: > I think that's a drastically unfair judgement. I would rather ask > every maintainer to do a few extra steps for the quality of their > packages (or better yet, to improve automated systems to notify > (opt-in) maintainers about such problems). The port maintainers > already have a significant amount of work to do on this front, and are > generally package maintainers themselves also. The automated notification thing is key, I think. The porting process is generally so painless that there's no need to check on stuff and with the large time lags sometimes involved it's very easy to not notice if something goes wrong. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpNhYZt5gTOg.pgp Description: PGP signature
Re: microwindows build status
On Sun, Jan 06, 2002 at 01:42:41PM -0800, Thomas Bushnell, BSG wrote: > libmwdrivers.before it's used, and without someone giving me a log of > the actual failure (which will require dropping that silly redirection > from debian/rules), you're just guessing. Sent by private mail. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgp0QUYVG9GGw.pgp Description: PGP signature
Re: Dmasound
On Sat, Jan 19, 2002 at 05:44:01PM +, rod brookes wrote: > insmod dmasound sound on...reboot sound is off > modprobe dmasound esd sound on...reboot sound is off! > Can anyone tell me what I am doing wrong please? Loading a module isn't quite the same as installing a device driver under other operating systems. It only installs it into the running kernel, it doesn't cause the module to be reloaded every time you reboot. Adding dmasound to /etc/modules would cause it to be reloaded every time you reboot. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpJe3XOfj1ih.pgp Description: PGP signature
