Printable View
Hi,Quote:
Originally Posted by Neo-Rio
for the first problem:
- knoppix alsa will do
For the second one:
You can be the first one that can try the new "nofstab" cheatcode ;-).
You can also boot with "knoppix26 modules-disk" to just choose your SCSI-controller... (the name is misleading)
cu
Fabian
PS: If this information is helpful to you, please add it to somewhere in the docs (!).
hi;
i just d/led it from the knoppix site and 2.6 doesn't get past scsi prob
said failed ????(i forget then went on to st100 and just sat there.
I didn't wait long though may not be stuck.
2.4 still works with my hardware useing it now to write this.
my hardware is:
ecs k7s5a
amd 1400 cpu
nvidia geforce 2 mx 64meg
ms optical mouse
gerneric keyboard
lg combo dvd/cdrw drive
maxtor 40 gig
256 sdram
Well I hope despite to the bugs you guys are satisfied with the release anyway :-)
cu
Fabian
hi Fabian,Quote:
Originally Posted by Fabianx
I think I just found that I have to use the "noscsi" boot parameter on any PC (no metter AMD or intel, new or old, event inside the latest vmware 4.5.1) to boot with kernel 2.6
and as reported by someone on the Knoppix taiwan branch, and tested by my self the cdrom automount feature didn't work with kernel 2.6 (but floppy was fine)
anyway I think most of us still enjoy the latest 2.4.x kernel and KDE 3.2.2 and other new features :D
I too have not been able to load the 2.6 kernel on the live cd boot I get the megaraid segmentation fault and then it freezes. On the hd install I can boot 2.4 flawlessly and 2.6 fails to load the scsi drivers. Otherwise it works ok. I do the expert26 boot option and the ncr53c8xx.o driver is not an option. However 2.4 loads this for my card.
Now for the good news...... my 5 button mouse works now.
Now off to get the realtek 8180 wlan card working.
I'm sure this SCSI issue will be fixed in the updated 3.4. Thanks for all the hard work getting the eagerly awaited 3.4 release out to the masses.
rob
net problem ended up posting twice, sorry.
RU Kidding??? This thing is AWESOME. You guys outdid yourselves this time. I set Linux aside until I could check out 2.6.Quote:
Originally Posted by Fabianx
I've seen four major accomplishments in Linux that will pave the path toward more widespread desktop acceptance: GUI (KDE), a competitive office suite (OpenOffice), Live disk implementation to serve as a transition (Knoppix), and NTFS compatibility. Linux is almost a viable desktop option for non-geeks now.
This is so cool.
yes knoppix 3.4 is great ~!
and dear all, if you see "megaraid segmentation fault" message and stop when booting kernel 2.6, try using boot parameter "noscsi" :D
*well sorry for those who want to try it with an SCSI connected PC..
and Fabian, trust me we all love this new Knoppix 3.4 :-D if we don't we won' t spend our time testing it.. :P
we just want things to became better and better
*(actually I guess some bugs are from the new 5 months old kernel it self, also do you think the hardware detection program also needs to adapt to the newer kernel and new C++ compiler ??)
best regards to you all
here from charles :lol:
HI there,
3.4 works fine on cd, i've just have to add noscsi with linux26.
When i install to hd in begginer mode, i get no network card(PCMCIA) working with kernel 2.6.5
If i install in Knoppix mode, everything works fine...
How can i solve this problem????
Tks
hi idiot ;-)Quote:
Originally Posted by vulcanidiot
you have hdinstalled as debian, i guess? now you have a debian GNU/Linux system. this means you can get info about installation and upgrading your system everywhere. to start, I'd suggest you read about apt-get (the advanced packet manager) which can be used to upgrade your system. on this site is alot info available.
good luck...
I fear I just reinstalled my system for naught! Is there no loop-aes support in the 2.6 kernel?
I did. And it worked. Maybe it was just plain luck. It was a PC with fairly standard hardware (and an Adaptec SCSI controller).Quote:
Originally Posted by charlesfan
Anyway, at home I had no option but to use 'noscsi'.
Cheers...
Knoppix 3.4 rocks, Thanks !
How can I add the gigabit Realtek 8169 in the network bootstrap process ?
I can boot knoppix from the network (pxe, tftp, nfs, ...) using other network cards but this one. I suppose I have to recompile the miniroot.gz ... Thanks for any help, Gilles
PS: Sorry, stupid question, I didn't read the manual...
I just had to enable the right network modules when starting the Knoppix Terminal server to compile the right miniroot.gz and it works just great.
Thanks Klaus !
Funny, I have the same exact hardware that you have there:-) Well ok, got a different cd writer and harddisk. The "noscsi" cheatcode did the job for me, so you might wanna try again with the 2.6 kernel!Quote:
Originally Posted by amigaman2
As a newbie that fell in Love with Knoppix 3.3, I can only say that over all IM tickled Pink--))))Quote:
Originally Posted by Fabianx
IM running a P-4 2.6 Gig, over 700 Meg of RAM, nVida GeForce TI 4200 and I have installed 3.4 to a 80 Gig Drive that I use just for Linux.
Both kernel's boot fine.
I have had very monior problems and they are:
Over all sound notifications in 2.4 will not work, yet sound in individual apps function fine--)))
In 2.6 I have the known mouse wheel problem where it just don't function.
My Nvidia card isn't recoganized for driver installation, which I beleive is due to Nvidia not being open source. I have d/l the latest install pkg from Nvidia. Have not installed it yet. IM chicken--)))) I dont want to hose all the work I have done so far. So that should be a good indication how much I like and value the 3.4 distro--)))) I don't understand enough to attempt to install yet, but will soon--)))
Shockwave/Flash, no plugins by default for cruising the web with either Mozilla or Konqueror.
IM reading my butt off try to learn debian and Linux overall. My goal is to migrate completey off of windows. Im loving this open source software.--)))
This to me would not be in my forecast if it were not for Knoppix! So a Big Thanks to You and Klauss for making this possible!
I just can't express enough my appreciation to ALL involved in creating Knoppix and this latest Distro!--)))
Finally in closing, I got my Net Gear PS101 Wireless Printserver working via Cups and my HP Laserjet workhorse 6p prints like a charm!
Thanks again!!!!!!!!
Hi team!
I bumped into a most bizzare issue with the 3.4. release...
I tried installing 3.4 on to a Compaq DeskproEN (1Ghz PIII, 256 RAM, ATI AiW 128 Rage Pro 32 MB). After trying the
linux26 option,
it didn't work until I added
linux26 noscsi.
So far - so good.
What I did next was to launch #knoppix-installer. Weird thing is that I DID enter passwords for both root + user (regardless of how nagging the full name request is), and as soon as I rebooted, I could NOT login to the system neither through kdm, nor through tty1 console. Regardless of how I tried, I never got to enter the system :( KDM does display the root and user accounts, but does NOT accept passwords. At first I thought I had the CAPS on during install or something, but after trying virtually all possible combinations (caps on/off), gave up.
I am pretty sure it is my fault. I mean it is my first time trying the knoppix-installer. Any idea?
Smith
p.s. where did the good-ol' knx-hdinstall go???
try knoppix single or linux single at boot time.
If it works then
passwd (to choose a new password))
I think that depends upon the VMWare version. Doing what you suggested I was also able to install the version 4.0.5 but not the newer 4.5.1 which gave me an error:Quote:
Originally Posted by scottknl
make: Entering directory `/tmp/vmware-config0/vmnet-only'
bridge.c: In function `VNetBridgeReceiveFromVNet':
bridge.c:346: structure has no member named `sk_wmem_alloc'
make: *** [bridge.o] Error 1
make: Leaving directory `/tmp/vmware-config0/vmnet-only'
Unable to build the vmnet module.
Never mind ... the version 4.0.5 works fine.
Thanks,
Tim
Thanks for the tips. I'll report back when I've tried it out.Quote:
Originally Posted by Fabianx
OK, here's the deal.Quote:
Originally Posted by Neo-Rio
My cheatcode line was'-
linux26 knoppix alsa noscsi nofstab
Everything went to plan on bootup.... 2.6 kernel, alsa detected, scsi and fstab skipped completely.
On booting, KDE threw up an error though: Kmix crashed and threw the signal 8 (SIGFPE)
And sound still doesn't work
Even in Linux2.4, sound doesn't work. I'm laying the blame on the shoddy SiI SATA RAID drivers and my mobo. Any chance of a "nosata" cheat code?
Also, some of the games that require full screen, like enigma and the nethack Falcon's eye are completely borking my display. I'm running at 1280x1024, and the screen is turning into a pile of lines, all out of sync.
Suggestions for 3.4 5-10 HD Install issue?
Here's the output after a restart into a HD beginner install:
root@knoppixlt:/home/jack# netcardconfig
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Xdialog: Error initializing the GUI...
Do you run under X11 with GTK+ v1.2.0+ installed ?
Any ideas never had an issue with 3.3?
Heres another, it only happens with root , not my user id?
root@knoppixlt:/home/jack# glxinfo
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Error: unable to open display (null)
Ideas?
Try pushing the key to activate the numbers at the alphanumeric keys.Quote:
I DID enter passwords for both root + user (regardless of how nagging the full name request is), and as soon as I rebooted, I could NOT login to the system neither through kdm, nor through tty1 console. Regardless of how I tried, I never got to enter the system KDM does display the root and user accounts, but does NOT accept passwords.
It happend something similar to me with a compaq notebook.
Regards
I always use the Debian hdinstall. Could someone please explain the differences between that and the beginner/knoppix way?
TIA,
AJG
Let me know if the following is covered somewhere else, but...
The 3.4 May 10th release does not recognize my Linksys WUSB V2.8 wireless device. Since it is hooked up to a desktop, and the system is upstairs, I'd like to avoid having to carry everything up and down to get Knoppix going.
I installed to the HD using the recommended option, thinking that I could then build the Atmel Drivers from the Belios site, and got a nice Debian system. However, the source for the kernel is mislinked (everything points to the 2.4 stuff even though booting into 2.6), and so I am unable to compile the Atmel drivers to enable the network card.
Any way to setup the proper 2.6 directories and links? I assume I need to DL some headers and other files? Seems like I have a bit of a catch-22 here and would appreciate some help.
Thanks in advance!
Yeah Where are the kernel headers for the 2.6 kernel?
Anyone????
Which manual are we talking about? I haven't found one yet, and it seems anything but simple. I am having a heck of a time trying to get a 3.4 terminal server working. The newly booted machine is not getting its interface together, which prevents it from mounting the KNOPPIX. It appears that it is trying to use the af_packet module to get the nic, but there doesn't seem to be anything binding it to eth0. What I see first is that the ifconfig eth0 in linuxrc fails, first because there is no /sbin/modprobe; and if I remaster the miniroot to get one, then it can't find an eth0. Then, ignoring that, linuxrc appears to ignore the nodhcp option that is given in the pxelinux.cfg/default file, and tries to dhcp.Quote:
Knoppix 3.4 rocks, Thanks !
How can I add the gigabit Realtek 8169 in the network bootstrap process ?
I can boot knoppix from the network (pxe, tftp, nfs, ...) using other network cards but this one. I suppose I have to recompile the miniroot.gz ... Thanks for any help, Gilles
PS: Sorry, stupid question, I didn't read the manual...
I just had to enable the right network modules when starting the Knoppix Terminal server to compile the right miniroot.gz and it works just great.
I'd like to think that I'm blind and have just missed the doc that explains
how one needs to reconfigure the miniroot so that you get the right network drivers, but I haven't found it yet. The <a href=http://www.knoppix.net/docs/index.php/FaqPXE> FaqPXE </a> page doesn't seem to touch on this. I don't want a floppy at all, or have to configure the miniroot -- I'd like it to pick up the UNDI PXE driver for the initial NFS mount, then if needed discover the better driver once more of the system is up. Perhaps this is implausible?
thanks,
-dB
[/quote]
[/quote]Quote:
Originally Posted by dbrower
Well, by manual, I meant selecting the right network cards AND deselecting the unused ones to avoid any conflict during the Knoppix Terminal server script which creates the miniroot.gz. I got it working with both the Realtek 8169 and Intel E1000 gigabits cards. I used grub and/or grub4dos to load the pxe module of the non pxe 8169 card. The intel includes the pxe rom. I noticed that the Terminal server script works better when using 2 network adapters (wan+lan) and then knoppix works also as a router and do the nat on the lan. After running the script you may need to reenable the card(s) using "ifconfig eth0(1) up" or reconfigure the adapter using the knoppix menu. You can verify that knoppix recognized your card by using "ifconfig -a" and check if the card is up with the right ip. I actually transferred the cd content and the boot files on my OpenBSD server with nfs and tftp running to boot knoppix from it. I hope this will help and that you can get your config up and running.
Cheers, Gilles
:wink:
I understand now. I had not run through the complete server config,
and when I copied the /tftpboot stuff to the actual machine that is my
dhcp/pxe server, it was unconfigured with the unmodified contents of
/tftpboot, which would not work.
I do not like having to pre-configure the network drivers. I think it would
be better to have a bigger miniroot that contained all the net drivers
and did its own detection, as the cdrom version does. I may whack
that together. Since we're going to end up copying 100 MB of stuff
eventually, copying the additional 6M of more network modules in
the miniroot doesn't seem like much of a burden.
thanks,
-dB
I agree, but when trying to get a miniroot including all the network drivers, the system locked up in some driver (which obviously I didn't need) and I couldn't get the system to boot. I had to go back to a "raisonnable" set of drivers to get a "working" config. So I understand Klaus wich allow each one of us to customize his miniroot according to his needs. But it would be good to have a default which includes all the drivers mostly used and known to work well together with a good and fast auto-detection and without any lock up.Quote:
Originally Posted by dbrower
Gilles
I don't mean to put all the drivers into the kernel, which would be the result of including them all at the moment. What I mean is to include them all in the miniroot, and then change the linuxrc script to do real detection of them and only install the correct one(s). What is does now is load everything you have in the miniroot, which is why it is awkward to include them all. Since the good autodetection is already around, the terminal server should use it as well as the CD system. This is what I'm thinking about putting together -- a changed linuxrc that will autodetect the net driver needed to nfs mount the KNOPPIX.Quote:
when trying to get a miniroot including all the network drivers, the system locked up in some driver (which obviously I didn't need) and I couldn't get the system to boot. I had to go back to a "raisonnable" set of drivers to get a "working" config.
-dB
[/quote]
I am 100% with you then.Quote:
Originally Posted by dbrower
BTW, I have trouble accessing page 11 of this news/topic. Page 10 is the last one I can access from the top of the page (Goto page ...). Is there a limitation to 10 pages in this forum ?
GvR
I installed K 3.4 on my hard disk the day it came out and have been using it since then. I have, however, encountered three problems which I would like to know if anyone else has had, and know if anyone knows how to solve them?
1. Even though I have run the network card configuration script and successfully configured the card, every time I restart the computer the network doesn't work. On the startup screen I can see it backgrounding the DHCP server (which I do not need because I have a fixed IP). When I re-run the script, all my values are there, and I just click on OK, and then the card works fine. But I have to do it by hand every time...
2. By default cupsd doesn't start. I have to su to root and start it by hand. I have tried dkpg-reconfigure cupsys but the daemon will not start automatically.
3. The strangest of all. When I first did the installation, K 3.4 put a load of icons on my desktop that I did not need, so I deleted some of them and changed the name of others to more meaningful names, and everything is fine, but when I reboot (or plug in my USB pendrive), I loose all the changes I have made and get all the original icons? Strange.
Any suggestions would, as usual, be very well received.
Tim
No bug.Quote:
Originally Posted by Jack_
Please add it to Bugs/Installer-Bugs though ...
I'll explain:
Root is no longer allowed to access the users display due to security reasons.
Just do:
su - # creates new environment for root
and use netcardconfig in text modus.
Or:
use:
kdesu netcardconfig
cu
Fabian
Hi,Quote:
Originally Posted by timread
please add al bugs to the bugs-page / knoppix-installer
1. is a bug. I added some code to make sure this won't happen. Obviously it did not work.
2. fixed in new version and same as 1). "Workaround" for now: as root do:
update-rc.d cupsys defaults
3. Hm, well you need to change mkdesktophdicons and disable it somehow ...
Its a feature not a bug ...
I don't know how to fix that yet though ...
cu
Fabian
Hi Fabian:
I'd just like to take the opportunity to thank you for the good work on Knoppix, I would support the idea of paying you guys for your work, but that is another thread.
I would love to, but when I connect to the Bugs section I am asked for another login and password - is their a FAQ about how to use the Bugs mechanism? It would be useful to know so that we can all help make Knoppix better.Quote:
Originally Posted by Fabianx
Ok, it's not the end of the world to re-run the script when I reboot the machine, since K 3.4 is so stable, I don't do it that often :wink:Quote:
Originally Posted by Fabianx
Worked like a charm...Quote:
Originally Posted by Fabianx
Well, maybe it is a bit ugly but I found that:Quote:
Originally Posted by Fabianx
chmod 0 /usr/bin/mkdesktophdicons
Seems to have done the trick, at least my desktop does not change without me asking it to do so.
Thanks.
Tim
To add anything to the WIKI, scroll to the bottom, type your forum username in the box, and click Edit, which should be just above and to the left of that name box. If the screen is asking for both a login and password, back up to the previous screen. No password is necessary - just name and Edit.
Klaus, Fabian and everybody else responsible for Knoppix, in one word:
BRILLIANT :D :D
Boot with kernel 2.6 and toram (1Gb Ram), it's fantastic. In 5 minutes listening to music, browsing Internet and chatting. Installed the Flash plugin and looked at the flash page of my club 8)
Vielen dank fur dieser Knoppix 3.4.
;-)Quote:
Originally Posted by timread
Not realy a clean way to do it, you just made it impossible to run the script at all. you should try to find out where it is started, and remove that line. but I dunnow where its started, it must be some knoppix-script somewhere maybe in init.d or init.rc.