January 2008 - Grml - lists.mur.at

X-server start wothout fluxbox/grml-medium
by Lars Schimmer 11 Feb '08

11 Feb '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Snapped grml-medium 0.1rc today and installed onto a HD. Fine solution, works fine with all needed stuff and without the unneeded parts. But I want to start the Xserver and just display a picture, I don't want to start fluxbox. If I type "startx" it starts fluxbox, even with a ssh login and /usr/bin/xinit and /usr/bin/X it starts fluxbox. Where do I have to look to disable fluxbox and all parts? And: has anyone a xv replacement for displaying a picture in background on pure X server (with hiding mousepointer)? MfG, Lars Schimmer - -- - ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHnf8/mWhuE0qbFyMRAhKoAJ9irQMiycsjA+05n/foOs6XE7mGRQCfdDfz G6cm24UtQGpIwxjSlRA6ByA= =kH4v -----END PGP SIGNATURE-----

3 2

GRML netboot packages for 0.1 x64
by Laurent CARON 31 Jan '08

31 Jan '08

Hi, Do anyone know if the netboot packages are availables for x64 grml ? I'd like to be able to boot it from the net as I'm currently doing for x32 ones . Thanks Laurent

2 2

Problem installing Gnome and Orca on GRML
by Jerry Matheny 30 Jan '08

30 Jan '08

I've tried apt-get update && apt-get install gnome-orca on the latest grml 1.1, and it comes to packages with bug reports and saying it needs to install those versions, and I try that and it eventually dies. I forget the error, but anyone have any ideas if there's a different way to go about this? Thanks in advance, Jerry

2 1

grml 1.1 does not recognize vmware disks anymore
by Peter 30 Jan '08

30 Jan '08

Hi I was just trying to install the new 1.1 release grml 1.1 rc iso inside VMware workstation 6. I have already done this successfully with grml 1.0. However, when I do : # fisk /dev/sda I get : Error: Unable to open /dev/sda : Unrecognized disk label This did not happen in grml 1.0 where I was able to create a partition with fdisk on /dev/sda Any ideas ? Thanks Peter

3 2

Problem with swspeak in GRML 1.1rc1
by Jerry Matheny 29 Jan '08

29 Jan '08

I did a grml2hd with the new GRML 1.1rc1 version and it doesn't work, and to top it off the sound is all crackily very bad to the point where I can't even understand what the speech is saying. But it's acting like something pertaining to speakup isn't being loaded properly, and something gets messed with sound in the grml2hd script. Not sure what the deal is, any help would be very much appreciated. And the Speakup spelling everything is kinda annoying too. lol, but I understand that's a Kernel issue. Thanks in advance, Jerry

1 0

a couple of questions, please.
by Doug Smith 29 Jan '08

29 Jan '08

Ok, I have a few questions here I want answers for. I have been using the new release candidate for GRML and I really like it. I just have a couple of problems I wish to know if anyone else has had with this version, and I would like to know something about the apt-get install grml process. First of all, has anyone had this problem with the installation of packages? I ask the system to add on some packages, primarily some languages I want to use in programming. This is what happens. The first time, right after you install the system to the hard disc from a cd you get this: wajig installrs bwbasic There is only one package to go and get, and everything works exactly like it should. Fine and well, but not really the problem. Now, when you go to install even more, you get this: wajig installrs gobjc This time, we need lots of c libraries and the search is on. The process of acquiring the deb files is perfect, but, after the programs says that it has fetched so many bytes of archives in so many seconds, and asks if you want to continue, the thing just stops. You tell it you do with the y and there is just a blank line at the bottom of the screen. No matter how many times you hit the return key after entering the y, you are just hung there, blocked forever in a failed function call until you control-c your way out and have to manually call dpkg to install the files you know you have. Now, there is no way that I can see to fix this. I have done everything from reinstalls of dpkg, debconf, apt, wajig and apt itself. This does nothing for the problem. I have even had the system reconfigure everything it has in order to make sure that all the programs know that everything is there. Now, I have another problem. What is wrong with cdtool? Each time I try to play a cd, I get this: cdplay: can't play no disc This is not true, as I have just inserted a professionally produced cd into the drive before doing this. Why will cdplay not play? Why will wajig installrs package-name not actually install the recommended and suggested packages? Now, I need to know about the wajig installrs grml or apt-get install grml, whichever you wish to call it. If you do this, for instance from the 1.0 nstable version, why do you not get the new kernel, the new speakup, the new configuration files and more that the new version has in it? It seems that then entire thing would be upgraded and you would just need to reboot in order to get it all. What actually happens here? I am sorry to just keep writing in with problems. As I stated some time ago, I intend to stay with grml. It is a very good distro, and, thanks for the speech. If anyone could tell me how to fix these problems, and about the upgrade process, I would be glad to learn more. I can also read the upgrading page on the wiki. Thanks. Doug Smith. -- I use grml (http://grml.org/)

3 2

Re: Grml Digest, Vol 33, Issue 7
by Kevin Jones 23 Jan '08

23 Jan '08

Hello, Has anyone experimented with grml in colinux? I would think that would be a great idea like grml2hd but in colinux colinux.org grml-request(a)mur.at wrote: > Send Grml mailing list submissions to > grml(a)mur.at > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.mur.at/mailman/listinfo/grml > or, via email, send a message with subject or body 'help' to > grml-request(a)mur.at > > You can reach the person managing the list at > grml-owner(a)mur.at > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Grml digest..." > > > Today's Topics: > > 1. Re: RC 1.1 troubles (ignore last post) (C.M. Brannon) > 2. Re: RC 1.1 troubles (ignore last post) (Michael Prokop) > 3. Re: Hi again - here's some more stuff for you... :-) (Andy Elvey) > 4. Re: RC 1.1 troubles (ignore last post) (C.M. Brannon) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 07 Jan 2008 14:27:26 -0600 > From: cmbrannon(a)cox.net (C.M. Brannon) > Subject: Re: [Grml] RC 1.1 troubles (ignore last post) > To: grml(a)mur.at > Message-ID: <87ir25nzyp.fsf(a)cox.net> > Content-Type: text/plain; charset=us-ascii > > Michael Prokop <mika(a)grml.org> writes: > >> Are you sure the ISO on your CD is *really* OK? Any chance to test >> it on another system to check whether it basically works at all? > > Well, all of the MD5 digests were verified. I even did > md5sum -c /mnt/cdrom/grml/md5sums > and all files were OK. > I tried it on another machine, and it wouldn't boot. So it seems that > my disk must be defective, even though the contents of the filesystem > are OK according to md5sum. I can think of several culprits. For > one, I use cheap generic CD-R media. I'll try this process again, > with some higher-quality disks. > > Have a great day, > -- Chris > > > ------------------------------ > > Message: 2 > Date: Mon, 7 Jan 2008 21:47:25 +0100 > From: Michael Prokop <mika(a)grml.org> > Subject: Re: [Grml] RC 1.1 troubles (ignore last post) > To: grml(a)mur.at > Message-ID: <2008-01-07T21-39-48(a)devnull.michael-prokop.at> > Content-Type: text/plain; charset="us-ascii" > > * C.M. Brannon <cmbrannon(a)cox.net> [20080107 21:31]: >> Michael Prokop <mika(a)grml.org> writes: > >>> Are you sure the ISO on your CD is *really* OK? Any chance to test >>> it on another system to check whether it basically works at all? > >> Well, all of the MD5 digests were verified. I even did >> md5sum -c /mnt/cdrom/grml/md5sums >> and all files were OK. >> I tried it on another machine, and it wouldn't boot. So it seems that >> my disk must be defective, even though the contents of the filesystem >> are OK according to md5sum. I can think of several culprits. For >> one, I use cheap generic CD-R media. I'll try this process again, >> with some higher-quality disks. > > Use readcd (something like "readcd -c2scan dev=/dev/cdrom") for > checking the CD. md5sums sadly just aren't enough. :(( > > I strongly recommend the use of USB pens instead of CD-Rs if > possible, otherwise fall back to higher quality CDs which are known > to work fine with your CD burner. That's what we as grml developers > do as well. :) > > regards, > -mika-

1 0

RC 1.1 troubles (ignore last post)
by cmbrannon＠cox.net 08 Jan '08

08 Jan '08

Hi all, Sorry for that last post. I accidentally sent it before it was complete! Anyway, I burned the 1.1 RC1 ISO to a blank medium with cdrecord -data dev=/dev/hdc grml_1.1-rc1.iso The MD5 checksum on the ISO is correct, and the recording process finished successfully. I can mount the CD-ROM, and all the requisite files are present. I booted the system, with the command-line grml swspeak But instead of booting the CD, I was presented with my hard-disk installation of grml. It was as though I did not have a bootable disk in the drive. So I found my grml 1.0 medium, and rebooted. That time, I booted into the live CD, as expected. I tried burning the 1.1 RC1 ISO to a second medium, just in case the first was damaged. That didn't work. It seems unusual that the 1.1 RC1 disk won't boot, while the 1.0 CD will boot. I'm running without a monitor, so the boot sequence isn't visible. I should probably ask someone to connect a monitor and read the boot sequence to me, but that's a big hastle. Am I missing something here? Is anyone else booting the 1.1 RC1 live CD with speech? -- Chris

3 9

Re: Hi again - here's some more stuff for you... :-)
by Andy Elvey 07 Jan '08

07 Jan '08

( snip ) > We don't use the resolutions by default since a long time but leave > the decision to the X server because this usually works better than > the other way around. If someone wants to force usage of a special > resolution just provide it on the grml-x commandline or activate the > (by defaut) deactivated Modelines in xorg.conf. > > Thanks for assisting, Michael. Does anyone of you care to send a > short summary back to the mailinglist so that people have the chance > to find the solution for the problem in the archive? > > regards, > -mika- > Sure! Here you go. This isn't actually very short, but it's thorough.... :-) To recap - My problem was that I was getting a "bouncing window" ( which said "Attention: Input not supported" ) going around the screen when I went into X. I have an AOC LCD monitor (model AOC LM925 ). Here's the URL for the manual ( very kindly given to me by Michael Schierl ) - http://www.aocmonitor-anz.com/support/manuals/LM925usermanual8ms.pdf I use Linux Mint 4 as my default distro. My Linux Mint monitor settings are - 1280x1024 H: 64kHz V: 60Hz Analog input My grml settings were - 1024x768 H: 48kHz V: 60 Hz Analog input The above settings correspond to SXGA for Linux Mint, and XGA for grml. I found that out from the table at the end of the monitor documentation. The first thing that got rid of the window was that I went into Linux Mint and got a copy of my xorg.conf file. I copied that onto a USB key. Went back into grml, made a backup copy of the grml xorg.conf, and then (as su) copied my Linux Mint file into /etc/X11/xorg.conf. ( The bouncy window was still around while I did this ). Went out of X to the command-line. Went back into X and the bouncing window had gone. The second thing that worked was that I went back into grml ( this was a new session - I didn't save my xorg.conf settings ). I ran this suggested command to start X - grml-x -mode 1280x1024 -hsync 64 -vsync 60 fluxbox It worked perfectly - No bouncing window appeared. Bye for now - - Andy

1 0

Re: [Grml] 1.1 rc1 - a small problem with "bouncing window"...
by Michael Schierl 02 Jan '08

02 Jan '08

[adding cc to mailing list again] Andy Elvey wrote: > The window appears just before X starts. You're > correct in that the mouse pointer moves "below" the window. The monitor > is an "AOC LM925" - AOC is the manufacturer. It is a VGA one. Okay. After figuring out that "AOC Monitor Australia/New Zealand" sells different monitors than "AOC Europe", it was easy to get to the manual: http://www.aocmonitor-anz.com/support/manuals/LM925usermanual8ms.pdf Okay. Now boot your Linux that works. Then press the rightmost button on your monitor (MENU) to get into the OSD menu (if this does not work, someone locked the OSD menu. Read page 8 of the manual - OSD Lock function - on how to unlock it). Use Left and Right (the keys left and right from the power button) to move to the "Information" icon (that looks like a "i" in a circle) and press MENU again. It will show screen resolution and horizontal and vertical refresh rate (i.e. three values). Exit from the OSD with the EXIT button (leftmost button). Post them here :) If you want, you can repeat this inside GRML. Page 18 of the manual lists "suggested refresh rates", but it does not list all supported ones. For 1280x1024 it suggests 60Hz or 75Hz. > < rant directed at the bouncy window's designer - not directed at you or > grml... > Drop your rant here: http://www.aocmonitor-anz.com/contact.php :) > Very poorly-thought-out by the bios people or whoever..... </rant> It's not the BIOS. In fact, it is not inside your PC at all. VGA signals are designed for CRT monitors. So, your LCD panel needs a microcontroller chip that converts the signal so that it can be used on the LCD. That microcontroller will display OSD error messages on the screen - they are *not* present in the signal that goes from PC to monitor. Buy a monitor from a different manufacturer next time *g*. (By the way, it sounds a bit silly that the RAMDAC chip on your graphics card converts the image in the frame buffer to analog signals and your LCD panel convert them back to digital. But that is how it works if you use a VGA connector). Michael

1 0